OO-LD/oold-schema: v1.0.0-rc.1

First release candidate for the v1.0 spec. A pre-release: /latest/ and the site default stay on v0.9.0; this candidate is served at /1.0.0-rc.1/.

Rolls up the term-mapping / type work (v0.9.0) plus the corrections from a spec review, each verified against a primary source (a live JSON-LD processor, the JSON Schema / JSON-LD 1.1 texts, SSSOM/SKOS).

Since v0.9.0

• xsd:float correctly reclassified - it is not JSON-native (only xsd:string/boolean/integer/double are elided on round-trip), so it is no longer forbidden; the datatype rule is reframed around default projections, with the useNativeTypes assumption stated.
• Compatibility claims corrected - JSON Schema 2020-12 treats unknown keywords as annotations, but strict-mode validators (Ajv) reject them; the "generic validators ignore" wording is fixed and separated from $vocabulary refusal.
• Composition - object-valued embeds (including array items) SHOULD be property-scoped; a cyclic scoped context is broken by inlining the remote context locally, not by moving it to the root. Removed the unfounded @propagate-array MUST; fixed the JSON-LD citation.
• Mapping machinery - SKOS mapping predicates kept (reasoner-safe, not owl:equivalent*); co-emission clarified as a pragmatic aid, not an entailment; x-oold-context/x-sssom CURIEs expand against a well-known prefix set the meta-schema defines (its @context), not the instance context; schema-level x-sssom subject is the schema $id; materialized @type aliasing follows term-vs-IRI semantics.

Remaining v1.0 gates

Not yet final: #25 (finalize edge cases) and #21 (backend impact review) are the outstanding gates before v1.0.0.

Full changelog: https://github.com/OO-LD/oold-schema/compare/v0.9.0...v1.0.0-rc.1