Repository navigation
The docs say constraints hold the document a write leaves, not the re… - #66
Merged
Merged
Conversation
…quest body. Since 6.0.1 every write is validated that way - PATCH on the graph its update produces, as since 5.10, POST merged with the triples the document already holds, PUT as the document the server types it - and imports inherit it, since they write through the same methods. The ontologies reference opened by saying constraints validate submitted data and treated SHACL as an aside; it now names SPIN constraints and SHACL shapes up front with both specs, says what each method is checked on, that a write is refused while any violation remains, including one that predates it, that the 422 describes only the violating resources, and that a constraint sees the written document's graph alone. The HTTP API table gives PATCH its constraint-violation 422 beside the one for an update of the wrong form, and the migration guide says what a 5.x client now meets on POST and on an untyped PUT. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
…were documented only as a package feature, and with the wrong trigger: the packages page said a view renders on resources that have the property, while the client renders an ldh:view on every resource typed with the property's rdfs:domain and an ldh:inverseView on every resource typed with its rdfs:range, subproperties included, whether or not the resource carries the property - so a property with no domain or range shows nothing, and Northwind's inverse views need ldh:showWhenEmpty false. A Views section under Properties says so, what $about is bound to, that the block is derived on each render and edited in the ontology, and that ns.ttl and package ontologies declare views alike, with Northwind's orders-from-this-customer as the example. The packages page states the rule and points there, and so does inline creation in the resources reference. Co-Authored-By: Claude Opus 5.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.
No description provided.