diff --git a/specs/0-introduction.md b/specs/0-introduction.md index b60a9fe..9abc796 100644 --- a/specs/0-introduction.md +++ b/specs/0-introduction.md @@ -3,7 +3,7 @@ An overview of the TREE specification with the TREE collection, a reference to the first focus node of its members, and the relations to other nodes from the current node. The TREE specification introduces these core concepts: - * a tree:Collection is a subclass of dcat:Dataset. The specialization is that it is a collection of members that MAY adhere to a certain shape. It typically has these properties when described in a node: + * a tree:Collection is a subclass of dcat:Dataset ([[!DCAT]]). The specialization being that it is a DCAT dataset a collection of members. It typically has these properties when described in a node: - tree:member points at the first focus node from which to retrieve and extract all quads of a member. - tree:view points to a tree:Node from which all members can be reached. - tree:shape indicates the [[!SHACL]] shape to which each member in the collection adheres. @@ -162,4 +162,4 @@ In that case, the SHACL shape MUST be processed towards a Shape Template as foll - sh:and: all properties on that shape template MUST be merged with the current shape template - sh:xone and sh:or: in both cases, at least one item must match at least one quad for all required paths. If not, it will do an HTTP request to the current namednode. -Note: The way we process SHACL shapes into Shape Template is important to understand in order to know when an HTTP request will be triggered when designing SHACL shapes. A cardinality constraint not being exactly matched or a sh:pattern not being respected will not trigger an HTTP request, and instead just add the invalid quads to the Member. This is a design choice: we only define triggers for HTTP request from the SHACL shape to come to a complete set of quads describing the member the data publisher pointed at using tree:member. \ No newline at end of file +Note: The way we process SHACL shapes into Shape Template is important to understand in order to know when an HTTP request will be triggered when designing SHACL shapes. A cardinality constraint not being exactly matched or a sh:pattern not being respected will not trigger an HTTP request, and instead just add the invalid quads to the Member. This is a design choice: we only define triggers for HTTP request from the SHACL shape to come to a complete set of quads describing the member the data publisher pointed at using tree:member.