Docs: single Fuseki with a dataset per dataspace, and the egress proxy - #61
Merged
Merged
Conversation
…tead of winning the walk. The platform split ldh:RenderRow into a sealed walk and the open leaf mode ldh:RowHook it asks at every element, so the rule that reveals the open concept moves to that mode and drops the priority it needed to outrank the walk. The README now describes where a package stylesheet is composed - right above hooks.xsl, the open modes' module, and below everything else - and what a rule in each open mode owes. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Person, Corporation, Order, OrderItem, ParcelDelivery, DeliveryEvent, Offer, the three price specifications, PostalAddress, ContactPoint, ProductGroup and Place join Product and City, each with the literal fields its instances carry — dates as xsd:date, quantities as xsd:integer, prices as xsd:float — and typed lookups for what they link to. DeliveryMethod is an enumeration and stays without one; enumerated values such as order status are set on the instance afterwards. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
…. One fuseki service holds an end-user and an admin dataset for every dataspace, named after the dataspace origin with the deployment host dropped and the role appended (northwind-traders.demo.end-user, and so on; the root dataspace keeps plain end-user and admin), declared in config/fuseki/config.ttl and stored one TDB2 directory per dataset under fuseki/. The configuration reference replaces the fuseki-admin and fuseki-end-user sections with the single fuseki service and documents the new egress forward proxy: outbound SPARQL SERVICE and LOAD from both Fuseki and the platform pass through it, public destinations allowed and loopback, private and link-local refused, so federation with public endpoints works while a query cannot reach another dataset, the cache or the platform. The dataspace reference's service example points at a per-dataspace dataset, the dataspace-management guide gains a step to declare the datasets and bind each application to its own service, the setup tree notes one TDB2 directory per dataset, and the triplestores reference's quad-store example follows the single-fuseki endpoint form. Co-Authored-By: Claude Opus 4.8 <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.
Updates the documentation for the single-Fuseki, dataset-per-dataspace deployment (with the egress proxy).
Changes
docs/reference/configuration.ttl— replaces thefuseki-admin/fuseki-end-usersections with the singlefusekiservice (one server, anend-userand anadmindataset per dataspace, one TDB2 directory each underfuseki/), and adds anegressservice section: the forward proxy that Fuseki's and the platform's outboundSERVICE/LOADrequests pass through — public destinations allowed, loopback/private/link-local refused, so public federation works while a query can't reach another dataset, the cache or the platform.docs/reference/dataspace.ttl— the service example now points at a per-dataspace dataset (northwind-traders.demo.end-user) and explains the naming rule (origin minus deployment host, role appended; root stays plainend-user/admin); notes services may still be shared where isolation isn't needed.docs/user-guide/manage-dataspaces.ttl— the "create a dataspace" steps gain declaring the dataset pair inconfig/fuseki/config.ttland binding each app to its own service; the services paragraph names the singlefusekiand theegressproxy.docs/get-started/setup.ttl— the folder tree notes one TDB2 directory per dataset.docs/reference/triplestores.ttl— thea:quadStoreexample uses the single-Fuseki endpoint form.Notes
riot) and everyrdf:XMLLiteralbody is well-formed;docs/html/regenerates cleanly throughmake ttl-to-html(it is gitignored, so not included).🤖 Generated with Claude Code