For each normative assertion, state how it is to be tested. This should include the tools used, and links to any test cases. An assertion may require more than one test for particular configurations or combinations of options. Ideally, for each test, if possible a counterexample that fails the test should also be provided.
This assertion will be considered satisfied if and only if all assertions that it is a parent of are
satisfied. These all have ID's of the form td-vocab-*
.
Perhaps should be checked as a JSON-LD file; it is not clear that is the intent. Assertion seems ambiguous.
Other assertions constrain the location and values associated with these keywords. In particular
td-context
restricts it, so this could be considered a parent of that assertion.
Can be checked with a JSON Schema. However, the actual assertion wording is ambiguous. Should probably be "Vocabulary terms that identify values that use simple types...". On the other hand, this rule may be included in more general rules that:
See comments under td-string-type.
See comments under td-string-type.
Assertion should be revised to say that if the @context is used, it MUST have the given value (or the primary, without a prefix). Assuming this is what is meant, it can be checked with a JSON Schema.
items
, and restriction on items MAY be wrong in
assertion.