Extract the vocabularies and document shapes into linkeddatahub-rdf

[namedgraph]

Why

The RDF a client sends to create a container, add a chart or grant an authorization was described in static buildModel methods hanging off picocli @Command classes, reachable only by depending on the CLI. Web-Algebra's ldh-* operations build the same documents through REST-VKG's execution context rather than through Jersey, so they had no way to share those shapes and would have had to restate every one. A shape restated is a shape that drifts.

rdf/ now builds com.atomgraph:linkeddatahub-rdf with Jena as its only dependency. What is shared is the shape of the request body, not how it is sent, so neither consumer inherits the other's transport.

What moved

into rdf/	from
rdf.vocabulary.{A,AC,ACL,DH,LDH,NFO,SD,SP,SPIN}	cli.vocab.*
Slugs, SequenceNumbers, Digests, Updates	cli.util.*, cli.sparql.*
Subjects.of(...)	BaseCommand.createSubject

The eighteen builders come off the command classes into classes named for what they build — Documents (container, item), Blocks, Views, Queries, Services, Imports, Acl, Ontologies. Commands become argument parsing plus a call:

put(getClient(), doc, Documents.container(doc, title, description, block, mode, primaryTopic));

URIRewriter splits rather than moving whole. childURI, encodeSlug and adminBase are conventions the platform itself applies and become rdf.URIs; rewrite is the --proxy option sending a request somewhere other than where its URI says, which stays a CLI concern with origin now private.

What did not move

The platform keeps its own com.atomgraph.linkeddatahub.vocabulary, still duplicated with the library's. Collapsing them would make the platform depend on rdf/, and the Dockerfile builds the webapp from COPY src + COPY pom.xml alone — so the dependency has to point away from the platform rather than at it. Independently fixable later, once the artifact is published.

Build and release

cli/pom.xml resolves the library by ${project.version}, so the two move together or the CLI stops resolving. make cli installs rdf/ first; make cli-version and release.sh's sync_cli_version version both poms. release.sh also deploys the library right after release:perform, which carries reactor modules only — building from the release tag via git archive, since sync_cli_version has moved the working tree on to the next SNAPSHOT by then. Inside the irreversible block on purpose: a platform release whose pinned library is absent is a release whose clients cannot build.

Verification

• 40 tests in rdf/, including the 25 ModelBuildersTest cases, which assert the exact models and passed unchanged after the move
• 86 tests in cli/
• make cli end to end, the shaded jar carrying com/atomgraph/linkeddatahub/rdf/*.class, and ldh --version / ldh create container --help off the launcher
• mvn -Prelease clean verify builds the main, sources and javadoc jars

Not run: the tests/http suite. Every one of these builders is exercised by it, so that is the real check and it wants a dev stack on 4443. Worth running before this merges.

🤖 Generated with Claude Code