Follow LinkedDataHub off the LDT and apps namespaces - #27
Open
namedgraph wants to merge 1 commit into
Open
namedgraph wants to merge 1 commit into
namedgraph wants to merge 1 commit into
Conversation
LinkedDataHub 6.0.0 retires https://www.w3.org/ns/ldt and renames its deployment-configuration ontology (AtomGraph/LinkedDataHub#394). Both are breaking for data as well as for stylesheets, and this repo carries both: every document in app/ and datasets/ is typed dh:Container or dh:Item, and the dataspace descriptions in config/ are typed and wired with lapp: and ldt: terms. The document-hierarchy namespace moves host without changing shape - www.w3.org/ns/ldt/document-hierarchy# becomes w3id.org/atomgraph/linkeddatahub/document-hierarchy#. The dh: prefix and the Container, Item and slug local names are untouched, so in the 57 files that carry app data, ETL mappings and SHACL shapes only the namespace string differs. lapp: becomes lds: and .../linkeddatahub/apps# becomes .../linkeddatahub/dataspaces#, so config/dataspaces.trig and config/system.trig type their dataspaces lds:Dataspace, lds:EndUserDataspace and lds:AdminDataspace and wire them with lds:origin, lds:ontology and lds:service. ldt:ontology and ldt:service move into the same vocabulary, which leaves each config file with one prefix where it had two. files/layout.xsl follows the prefix: lapp:origin() is lds:origin(), and the footer's $ldt:base - a parameter LinkedDataHub retired before this - is lds:base(). The client SEF path from #26 is unchanged; only the function names move. Verified: layout.xsl compiles under Saxon-HE Java and client.xsl exports to SEF, both against a LinkedDataHub tree built from the rename, and all 58 Turtle, TriG and SPARQL files in this commit parse with riot and qparse. The compiled files/client.xsl.sef.json is untracked build output and still has to be rebuilt with `make sef` against a LinkedDataHub image carrying the rename. 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
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.
LinkedDataHub 6.0.0 retires
https://www.w3.org/ns/ldtand renames its deployment-configuration ontology — AtomGraph/LinkedDataHub#394. Both are breaking for stored data as well as for stylesheets, and this repo carries both: every document inapp/anddatasets/is typeddh:Containerordh:Item, and the dataspace descriptions inconfig/are typed and wired withlapp:andldt:terms.dh:moves host without changing shapehttps://www.w3.org/ns/ldt/document-hierarchy#→https://w3id.org/atomgraph/linkeddatahub/document-hierarchy#The
dh:prefix and theContainer,Itemandsluglocal names are untouched, so across the 57 files holding app data, ETL mappings and SHACL shapes only the namespace string differs — the diff is one line per prefix declaration, not one per term.lapp:becomeslds:https://w3id.org/atomgraph/linkeddatahub/apps#→https://w3id.org/atomgraph/linkeddatahub/dataspaces#config/dataspaces.trigandconfig/system.trigtype their dataspaceslds:Dataspace,lds:EndUserDataspace,lds:AdminDataspaceand wire them withlds:origin,lds:ontology,lds:serviceldt:ontologyandldt:servicemove into that same vocabulary, so each config file now needs one prefix where it needed twofiles/layout.xsl:lapp:origin()→lds:origin(), and the footer's$ldt:base— a parameter LinkedDataHub retired before this change — →lds:base()The client SEF path from #26 is untouched; this only moves the function names.
Verification
files/layout.xslcompiles under Saxon-HE Java andfiles/client.xslexports to SEF, both against a LinkedDataHub tree built from the rename. The SSR check has to go through Saxon-HE: SaxonJS cannot compile the server-side stylesheet, because theuse-whenduals leaveac:langs()undefined for it.riotandqparse.Not in this PR
files/client.xsl.sef.jsonstill needs rebuilding. It is untracked build output, andmake sefhas to run against a LinkedDataHub image that carries the rename — rebuilding it against the current published image would bake the old namespaces back in.CLAUDE.md,Makefile,README.md,app/.ldhignore,app/import-ns.sh,app/install.sh, theapp/update-folder.shdeletion,docker-compose.override.yml, and thebin/make-public.shcomment reword. Where the rename touched those files it touched text that is itself uncommitted —CLAUDE.md's$ldt:basegotcha, for instance — so those touch-ups will ride along when that work is committed.bin/make-public.shis the one exception: itsdh:prefix line is committed here, its comment reword is not.master(Serve the client SEF from static/lt/linkeddata/ instead of static/com/ltlod/ #26) is included — this branch is a fast-forward frombde764d.🤖 Generated with Claude Code