spec: catalogue seven indicative-mood requirements (band C) - #150
Merged
Conversation
- x-oold- keyword prefix, with @context and the enum keywords named as the two exemptions (#meta-schema contradicted #enum-names since #138) - x-oold-range takes one of three forms, and no other - x-oold-sssom must not be stamped onto exported instances - frame derivation, reverse-property read/write, multilang keywords not interpreted as JSON-LD - x-oold-reverse-default-properties deprecated as SHOULD NOT - protected-term redefinition attributed to JSON-LD 1.1 rather than read as an OO-LD rule
A keyword deprecated before v1.0 is not part of v1.0's vocabulary, so there is nothing for the catalogue to bind.
simontaurus
changed the title
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.
Continues the normativity audit. Seven requirements were stated in indicative mood, so the rule catalogue could not see them; each now carries an RFC 2119 keyword and a rule marker. 73 -> 80 rules.
New rules
OOLD-SCH-cfb8#meta-schemax-oold-prefixOOLD-EXT-c77a#range-of-propertiesx-oold-rangeMUST take one of the three listed forms, and no otherOOLD-VER-9846#ontology-mappingx-oold-sssomonto instancesOOLD-EXT-68fa#framingOOLD-EXT-eeda#reverse-propertiesOOLD-EXT-44bd#localizing-schema-annotationsOOLD-INS-770a#value-forms@type: "@id"on its termAlso fixed
#meta-schemaclaimed@contextwas the only unprefixed keyword. Require x-enum-varnames for value aliases #138 addedx-enum-varnames/x-enum-descriptions, and#enum-namescross-references#meta-schemafor the naming rule, so the two sections contradicted each other. Both exemptions are now named, on the shared ground that the name is not OO-LD's to choose.#protected-terms: "redefining a protected term to a different IRI is an error" is a [[JSON-LD11]] constraint, not an OO-LD one. Attributed rather than catalogued.OOLD-INS-2e5d,OOLD-INS-1df7,OOLD-INS-f010reworded so the keyword sits on the requirement its summary already claimed. Same obligations, re-accepted against the baseline.Not done
The
x-oold-reverse-default-propertiesdeprecation was catalogued in the first commit and then dropped: a keyword deprecated before v1.0 is not part of v1.0's vocabulary, so there is nothing to bind. It is removed from the spec, the meta-schema and the compliance fixtures in #152 instead.Verification
make checkexit 0 (53 sections, 80 rules, baseline matching, no drift).make validatepasses: 380 checks overexamples, 71 overexamples/compliance, 0 failed.OOLD-SCH-cfb8is machine-checkable and currently has no validator check.