From 24cab9b8a026007a2409a73c36030292b2bb1f8d Mon Sep 17 00:00:00 2001
From: bergi <bergi@axolotlfarm.org>
Date: Sat, 13 Jan 2024 20:08:07 +0100
Subject: [PATCH] feat: added Comparing named nodes section

---
 specs/2-traversing.md | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/specs/2-traversing.md b/specs/2-traversing.md
index f6fd977..a10ddca 100644
--- a/specs/2-traversing.md
+++ b/specs/2-traversing.md
@@ -52,6 +52,10 @@ When no language is set, all strings are compared.
 
 Note: If you want to have one resource containing both <code>e</code> and <code>é</code> as a prefix, you will have to create multiple relations to the same <code>tree:Node</code>.
 
+### Comparing named nodes ### {#named-nodes}
+
+When using comparator relations such as <code>tree:GreaterThanRelation</code>, named nodes must be compared as defined in the [ORDER BY section of the SPARQL specification](https://www.w3.org/TR/sparql11-query/#modOrderBy).
+
 ### Comparing geospatial features ### {#geospatial}
 
 The <code>tree:GeospatiallyContainsRelation</code> is the relation than can be used to express all further members will be contained within a geospatial region defined by the WKT String in the <code>tree:value</code>.