Remove 'recognized datatype IRI' in favor of RDF Semantics definition and use #124
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.
Important:
RDF-Semantics has never referenced RDF-Concepts for "recognized datatypes".
It has its own definition dfn-recognized so no changes are necessary for RDF Semantics.
There are two places that cover accepting literals. One is for literals with unknown dataypes, section DatatypeIRIs and one is for known-to-be ill-typed literals. In RDF 1.1 they were MUST and SHOULD. In this PR, they are aligned as SHOULD. RDF Semantics provides further restrictions for D-entailment and it's definition of "recognized" datatype IRIs that has additional conditions.
This closes #122.
This closes #60.
Preview not depending on PR-Preview.
Preview | Diff