spec: a term mapped with @reverse is reference-valued - #181
Merged
Merged
Conversation
OOLD-EXT-6d10 listed three signals; a reverse term matched only when the author also wrote "@type": "@id", which JSON-LD makes redundant. Both implementations therefore embedded the targets of a bare @reverse term, the defect #160 closed. Also states plain @reverse itself: the specification used it in three worked examples but only ever defined x-oold-reverse-properties, so the distinction between a read projection and the editor affordance sat in a parenthetical.
simontaurus
added a commit
to OO-LD/oold-js
that referenced
this pull request
Sep 21, 2026
A reverse term's values are node references by definition, so "@type": "@id" beside it is redundant and authors omit it. Keying only on @type missed the idiomatic spelling, and framing embedded the targets. Refs OO-LD/oold-schema#181
simontaurus
added a commit
to OO-LD/oold-python
that referenced
this pull request
Sep 21, 2026
A reverse term's values are node references by definition, so "@type": "@id" beside it is redundant and authors omit it. Keying only on @type missed the idiomatic spelling, and framing embedded the targets. Refs OO-LD/oold-schema#181
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
OOLD-EXT-6d10listed three signals for a reference-valued property:x-oold-range, an IRI-familyformat, and a term mapped"@type": "@id".A term mapped with
@reverseis reference-valued too, but matched only if the author also wrote"@type": "@id"- which [[JSON-LD11]] §4.1.10 makes redundant, since a reverse term's values are node references by definition. Measured before the fix:So a schema using the idiomatic spelling got no
@embed: @never, and framing embedded the reverse targets: exactly the defect #160 closed, reachable again through the gap. Every fixture passed because the worked example in #framing writes both spellings.Changes
OOLD-EXT-6d10takes a fourth signal,@reverse, and says why it stands alone.#reverse-propertiesnow states the plain [[JSON-LD11]] mechanism. The specification used@reversein three worked examples but only ever definedx-oold-reverse-properties, leaving the distinction - read projection versus editor affordance - in a parenthetical. Prose rather than rules: the permission is aMAY, which the catalogue deliberately excludes, and the obligation already lives inOOLD-EXT-6d10.Implementations
OO-LD/oold-js#4 and OO-LD/oold-python#164, each with a test on the bare form.
Verified:
make spec,make validate(380 ok and 76 ok, 0 failed),rules_baseline.py(88 rules),check_spec.py(54 sections).