Drop the last three references to the LDT namespace - #95
Merged
Merged
Conversation
d7cac46 took the ldt: namespace out of the stylesheets and the writer, and 816f4ca deleted vocabulary/LDT.java, the bundled ldt.ttl and the prefix-mapping.n3 entry that resolved it. Three lines were left behind. ac:stylesheet carried rdfs:domain ldt:Application. With ldt.ttl gone and the namespace unmapped, that names a class nothing here defines and nothing can resolve - it is inert rather than wrong, since ns.ttl does not owl:imports the namespace, so no fetch is attempted and no error is raised. The domain is dropped rather than repointed: this project has no class of its own to name there, and it must not take a dependency on a LinkedDataHub namespace to borrow one. ProxyRequestFilterTest used two ldt: rel URIs to check that a comma-joined Link header comes back split into one value per link-value. ProxyRequestFilter does not inspect rel at all, so the URIs are arbitrary; they are now example.org. LinkedDataHub reads ns.ttl out of the published client jar, so this reaches it on the next release and dependency bump. Nothing waits on that: the reference is dangling, not dereferenced. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
namedgraph
added a commit
to AtomGraph/LinkedDataHub
that referenced
this pull request
Sep 25, 2026
…6.0.2. Web-Client 6.0.2 (AtomGraph/Web-Client#95) drops the rdfs:domain ldt:Application that ac:stylesheet still carried. The class had not been resolvable since Web-Client deleted its bundled ldt.ttl and the prefix-mapping entry for the namespace, and ns.ttl reaches this project from the published jar, so the reference sat in every ontology closure the platform built - inert, since nothing imports the namespace and no fetch is attempted, but there. Both client dependencies move: the classes artifact and the war overlay. Co-Authored-By: Claude Opus 5 (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.
Finishes what
d7cac463and816f4ca3started. Those two took theldt:namespace out of the stylesheets and the writer, and deletedvocabulary/LDT.java, the bundledldt.ttland theprefix-mapping.n3entry that resolved it. Three lines were left behind — the last mentions ofhttps://www.w3.org/ns/ldtanywhere in this repo.ns.ttlac:stylesheetcarriedrdfs:domain ldt:Application. Withldt.ttlgone and the namespace unmapped, that names a class nothing here defines and nothing can resolve. It is inert rather than broken —ns.ttlhas noowl:importsof the namespace, so nothing is fetched and nothing errors — but it is a dangling reference in a published ontology.Dropped rather than repointed. Web-Client has no class of its own to name there, and it must not take a dependency on a LinkedDataHub namespace to borrow one.
ac:stylesheetkeeps its label andrdfs:isDefinedBy; it simply no longer claims a domain.ProxyRequestFilterTestThe fixture used two
ldt:rel URIs to check that a comma-joinedLinkheader comes back split into one value per link-value.ProxyRequestFilter.overlayHeadersnever inspectsrel, so the URIs are arbitrary — they are nowexample.org. The assertions are unchanged in shape.Context
This is the Web-Client half of AtomGraph/LinkedDataHub#394, which retires
https://www.w3.org/ns/ldton the platform side and renames its deployment-configuration ontology.LinkedDataHub reads
ns.ttlout of the publishedclientjar, so this only reaches it on the next release plus a dependency bump — it currently pinsclient:6.0.1twice, asclassesand as the war overlay. Nothing waits on that: until then the platform simply carries one unresolvable URI in its ontology closure, exactly as it does today.ns.ttl'sowl:versionInfois left at2.1.0— dropping a dangling annotation did not seem worth a bump, but say the word and it can go up with the next release.Verification
mvn test-compileclean;ProxyRequestFilterTestpasses;ns.ttlvalidates withriot.grep -r 'ns/ldt\|ldt:\|LDT'over the repo now returns nothing but the false positivecheckLiteralDTinTokenizerText.java.🤖 Generated with Claude Code