Fix non-canonical XMLLiteral in dataspace.ttl#50
Merged
Merged
Conversation
Replace the numeric character reference → with the literal → so the rdf:XMLLiteral is canonical XML. Jena 6 rejects entity references in XMLLiteral lexical forms with "not valid for datatype XSD XMLLiteral". Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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.
Replaces the numeric character reference
→with the literal→in thedataspace.ttldocumentation, so therdf:XMLLiterallexical form is canonical XML.Jena 6 (the LinkedDataHub build) rejects entity references in XMLLiteral lexical forms with
not valid for datatype XSD XMLLiteral; the convention in these docs is to use literal Unicode characters (e.g.↔,—). Follow-up to the documentation updates merged in #49.🤖 Generated with Claude Code