You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
<h1class="p-name no-ref" id="title">The TREE hypermedia specification</h1>
537
-
<pid="w3c-state"><ahref="https://www.w3.org/standards/types/#CG-DRAFT">Draft Community Group Report</a>, <timeclass="dt-updated" datetime="2025-06-11">11 June 2025</time></p>
540
+
<pid="w3c-state"><ahref="https://www.w3.org/standards/types/#CG-DRAFT">Draft Community Group Report</a>,
541
+
<timeclass="dt-updated" datetime="2025-06-20">20 June 2025</time></p>
538
542
<detailsopen>
539
543
<summary>More details about this document</summary>
<p><imgalt="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." height="500" src="TREE-overview.svg"></p>
636
641
<divclass="informative">
637
-
The TREE specification introduces these core concepts:
642
+
643
+
The TREE specification introduces these core concepts:
644
+
638
645
<ul>
639
646
<lidata-md>
640
647
<p><code>tree:Collection</code> is a set of members. It typically has these properties when described in a node:</p>
<divclass="informative"> In the example above the subtree reachable from <code>ex:Node2</code> will contain all remaining members that are both created later in time than the given timestamp <em>and</em> will have the provided substring in the title.
832
+
<divclass="informative">
833
+
In the example above the subtree reachable from <code>ex:Node2</code> will contain all remaining members that are both created later in time than the given timestamp <em>and</em> will have the provided substring in the title.
823
834
The client can choose to prune all links to other nodes if this is the only thing it is interested in.
824
835
Alternatively, the client can choose prune the subtree reachable from <code>ex:Node2</code> if it is specifically not looking for members with the given substring, <em>or</em> when it is not interested in members created later in time than the given timestamp.
825
836
Alternatively, it can also score the relation based on the likelihood of returning useful results and created a priority queue that is processed until a top K of results have been found.
826
-
Mind that when the client is specifically not interested in members created later than the given creation time, but does not understand the SubstringRelation, the client can still prune the relation. </div>
837
+
Mind that when the client is specifically not interested in members created later than the given creation time, but does not understand the SubstringRelation, the client can still prune the relation.
838
+
</div>
827
839
<p>While each type of relation can decide on their own properties,
828
840
relations will often use the <code>tree:path</code> to indicate the path from the member to the object on which the <code>tree:Relation</code> applies.
829
841
For the different ways to express or handle a <code>tree:path</code>, we refer to <ahref="https://www.w3.org/TR/shacl/#x2.3.1-shacl-property-paths">2.3.1 in the shacl specification</a>.
<p><strong>IRI comparisons</strong> MUST be treated as simple literal comparisons, consistent with the rules defined for the <ahref="https://www.w3.org/TR/sparql11-query/#modOrderBy">ORDER BY operation in the SPARQL specification</a>.</p>
844
856
<lidata-md>
845
-
<p>**<code>xsd:dateTime</code> literals without a timezone comparisons** MUST be performed by interpreting the <code>xsd:dateTime</code> literal as a period of time, with a min inclusive bound of <code>-14:00</code> and max exclusive bound of <code>+14:00</code>.</p>
857
+
<p><strong><code>xsd:dateTime</code> literals without a timezone comparisons</strong> MUST be performed by interpreting the <code>xsd:dateTime</code> literal as a period of time, with a min inclusive bound of <code>-14:00</code> and max exclusive bound of <code>+14:00</code>.</p>
846
858
</ul>
847
859
<pclass="note" role="note"><spanclass="marker">Note:</span> It is highly recommended that server developers and data producers provide a timezone in their <code>xsd:dateTime</code> literals for time comparison.</p>
<p>An entity that describes a relation between two <code>tree:Nodes</code>.</p>
939
953
<p>The <code>tree:Relation</code> has specific sub-classes that implement a more specific type between the values.
940
-
These types are described in the ontology (all classes are <code>rdf:subClassOf</code><code>tree:Relation</code>). <code>tree:Relation</code> can be express in term of <ahref="https://www.w3.org/TR/sparql11-query/#expressions">SPARQL algebra functions</a>:</p>
954
+
These types are described in the ontology (all classes are <code>rdf:subClassOf</code><code>tree:Relation</code>).
955
+
<code>tree:Relation</code> can be express in term of <ahref="https://www.w3.org/TR/sparql11-query/#expressions">SPARQL algebra functions</a>:</p>
these words do not appear in all uppercase letters in this specification. </p>
1057
+
these words do not appear in all uppercase letters in this specification.
1058
+
1059
+
</p>
1043
1060
<p>All of the text of this specification is normative
1044
-
except sections explicitly marked as non-normative, examples, and notes. <adata-link-type="biblio" href="#biblio-rfc2119" title="Key words for use in RFCs to Indicate Requirement Levels">[RFC2119]</a></p>
1061
+
except sections explicitly marked as non-normative, examples, and notes. <adata-link-type="biblio" href="#biblio-rfc2119" title="Key words for use in RFCs to Indicate Requirement Levels">[RFC2119]</a>
1062
+
1063
+
</p>
1045
1064
<p>Examples in this specification are introduced with the words “for example”
1046
1065
or are set apart from the normative text
1047
1066
with <code>class="example"</code>,
1048
-
like this: </p>
1067
+
like this:
1068
+
1069
+
</p>
1049
1070
<divclass="example" id="w3c-example">
1050
-
<aclass="self-link" href="#w3c-example"></a>
1051
-
<p>This is an example of an informative example. </p>
1071
+
<aclass="self-link" href="#w3c-example"></a>
1072
+
1073
+
<p>This is an example of an informative example.
1074
+
</p>
1052
1075
</div>
1053
1076
<p>Informative notes begin with the word “Note”
1054
1077
and are set apart from the normative text
1055
1078
with <code>class="note"</code>,
1056
-
like this: </p>
1079
+
like this:
1080
+
1081
+
</p>
1057
1082
<pclass="note" role="note">Note, this is an informative note.</p>
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?v=4&size=40){kind=avatar}
0 commit comments