s3dgraphy 1.6.0.dev33__tar.gz → 1.6.0.dev35__tar.gz

{s3dgraphy-1.6.0.dev33/src/s3dgraphy.egg-info → s3dgraphy-1.6.0.dev35}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: s3dgraphy
-Version: 1.6.0.dev33
+Version: 1.6.0.dev35
 Summary: 3D Stratigraphic Graph Management Library for archaeological and heritage applications
 Author-email: Emanuel Demetrescu <emanuel.demetrescu@cnr.it>
 Maintainer-email: Emanuel Demetrescu <emanuel.demetrescu@cnr.it>

{s3dgraphy-1.6.0.dev33 → s3dgraphy-1.6.0.dev35}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "s3dgraphy"
-version = "1.6.0.dev33"
+version = "1.6.0.dev35"
 description = "3D Stratigraphic Graph Management Library for archaeological and heritage applications"
 readme = "README.md"
 requires-python = ">=3.9"

{s3dgraphy-1.6.0.dev33 → s3dgraphy-1.6.0.dev35}/src/s3dgraphy/JSON_config/em.ttl

@@ -47,8 +47,8 @@
     dcterms:creator "Emanuele Demetrescu" ;
     dcterms:license <https://creativecommons.org/licenses/by/4.0/> ;
     dcterms:issued "2026-05-23"^^xsd:date ;
-    owl:versionInfo "1.6.14" ;
-    rdfs:comment "Formal ontology for Extended Matrix (EM): a human-readable layout for knowledge graphs of archaeological stratigraphy and virtual reconstruction. Extends CIDOC-CRM, CRMarchaeo, CRMinf, CRMdig, CRMgeo, with PROV-O for agent provenance and HDT-O for digital-twin granularity. This file declares the em: classes and properties introduced in s3dgraphy v1.6.0. v1.6.14 (2026-10-02, dev30, decided by E.D. on the dev29 report): section 18 — em:retrievedFrom, where a retrieval came from (D1), and em:membersDigest, the digest of a file_set with a predicate of its own (D4; em:digestCovers stays for compatibility). v1.6.13 (2026-10-02, dev29, measured on San Pietro): seven DatatypeProperties, section 17 — how the bytes of a resource are packed and what its digest covers (em:packaging, em:tier, em:digestCovers, em:contentDigest) and what a DTC step declares (em:technique, em:parameters, em:software, the last two rdf:JSON): the round trip em.json → TTL → em.json lost all seven. v1.6.12 (2026-11-01, dev28, decided by E.D. 2026-10-01): no new term — em:authMode admits a third value, 'declared' (an iD typed in a tool's preferences and checked by nobody), with no em:attestedBy. v1.6.11 (2026-10-31, dev27, decided by E.D. 2026-10-01): ten properties. Section 15, several addresses of ONE resource (em:hasAddress to <resource>/address/<i>, em:locator, em:checkedAt, em:reachable) and a dated digest (em:checksumAt); section 16, how the hand of a signature had entered (em:createdVia, em:modifiedVia, em:validatedVia to <node>/auth/<stamp>, em:authMode orcid | node_password, em:attestedBy the StratiGraph node). The language of the content of a resource leaves as dcterms:language: no em: term. v1.6.10 (2026-10-29, MICRO le traduzioni, decided by E.D. 2026-10-01): six DatatypeProperties for the language of the original and its translations (section 14) — em:originalLanguage on any node, which says which literal is the original once translations share its predicate, and em:sourceLanguage, em:translatedField, em:translationMethod, em:sourceDigest, em:reviewRequested on a TranslationNode, which is a plain crm:E33_Linguistic_Object reached by crm:P73_has_translation: CIDOC has the class and the relation, so no em: class is added. v1.6.9 (2026-10-18, MICRO la risorsa e i suoi file): em:ResourceFile, ONE FILE of a resource (node datamodel 1.6.17), a subclass of crmdig:D1_Digital_Object; the resource is composed of its files by crm:P106_is_composed_of (connections has_file, 1.6.30). A distinct URI because a DTC output resource is already typed crmdig:D1, and a file typed only D1 would read back as a resource. v1.6.2 (2026-09-21, CIDOC repair pass): the eight terms the datamodels cited and this file never defined are declared in section 12; em:NodeGroup and em:ParadataNodeGroup leave the undeclared crm:E78_Collection for crm:E73_Information_Object and crm:E89_Propositional_Object; em:SemanticShape leaves crmgeo:SP5 for crm:E73_Information_Object, provisionally; crmarchaeo:AP11_has_physical_relation becomes AP11_has_physical_relation_to, the name CRMarchaeo has used since 2.0; and em:RepresentationModel says what a representation model IS. v1.6.5 (2026-10-20, MICRO la definizione dell\'unita\'): em:hasDefinition, the DEFINIZIONE of a stratigraphic unit as a subproperty of crm:P2_has_type — declared for the node datamodel 1.6.9 entry StratigraphicNode.properties.definition, not emitted by default (owl:versionInfo was left at 1.6.2 by the 1.6.3/1.6.4 passes and is realigned here). v1.6.8 (2026-10-11, MICRO la geometria per origine): the vertices of a 3D reading (point, line, polyline) are data of the region (node datamodel 1.6.15, AnnotationRegionNode.coords) and leave for RDF as ONE GeoSPARQL 1.1 literal: <region> geo:hasGeometry <region>/geometry, a geo:Geometry with geo:asWKT '<CRS IRI> POINT Z (x y z)' | 'MULTIPOINT Z (...)' | 'LINESTRING Z (...)'^^geo:wktLiteral. WHY GeoSPARQL and not em: terms: the WKT literal is the standard every triplestore with a spatial index reads, and it is the 3D twin of the Media Fragment a 2D region already emits (a string a consumer outside EM can act on); CRMgeo was built to meet GeoSPARQL at exactly this point (SP5 Geometric Place Expression ~ geo:Geometry), and an em:coords literal would say the same thing to nobody. The CRS travels INSIDE the literal, so it cannot be separated from the numbers: em:LocalSceneFrame (declared here) for the scene-local frame, the OGC EPSG IRI for a projected one. em:vertexCount stays (the count of a .glb resource above the threshold). The .glb of a reading is no longer a SemanticShape's rdfs:seeAlso: above coords.inline_max_vertices (500) it is a ResourceNode the region reaches with has_linked_resource (crm:P67_refers_to), and a proxy's .glb is likewise a proxy_model ResourceNode (connections 1.6.28-1.6.29). v1.6.7 (2026-09-30, MICRO la cattura in RDF): no em: term added — the acquisition of a digital object is typed by its KIND. A capture is not a transfer: crmdig:D2_Digitization_Process for a photograph or a laser scan, crmdig:D11_Digital_Measurement_Event for a topographic or GNSS survey, crm:E65_Creation for a field drawing or a recording sheet (made by hand; the file is their copy, so no D7 machine event is asserted); a retrieval (download, local import, URI, ingest) stays crmdig:D12_Data_Transfer_Event. The rule is data (em_visual_rules 1.6.24, dtc_kinds.acquisition.<kind>.mapping). v1.6.6 (2026-10-07, MICRO la misura in RDF): the place of a reading gets its quote and its measure. The quote of a passage reuses W3C Web Annotation (oa:hasSelector -> oa:TextQuoteSelector, oa:exact) — the only standard term for a quote, which has no fragment-string form; its offsets stay the RFC 5147 em:hasSelector 'char=s,e'. The length of a line or polyline reuses CIDOC (crm:P43_has_dimension -> crm:E54_Dimension, P90_has_value xsd:double, P91_has_unit -> a QUDT unit IRI); two em: terms are new, em:vertexCount and em:crs, for what neither vocabulary says. The .glb of a 3D reading is not described here: its URL is the rdfs:seeAlso of the SemanticShape the region reaches with em:hasSemanticShape, and no coordinate enters RDF."@en ;
+    owl:versionInfo "1.6.15" ;
+    rdfs:comment "Formal ontology for Extended Matrix (EM): a human-readable layout for knowledge graphs of archaeological stratigraphy and virtual reconstruction. Extends CIDOC-CRM, CRMarchaeo, CRMinf, CRMdig, CRMgeo, with PROV-O for agent provenance and HDT-O for digital-twin granularity. This file declares the em: classes and properties introduced in s3dgraphy v1.6.0. v1.6.15 (2026-10-04, D1, decided by E.D.): section 19 — the level of a version of an asset (em:lodLevel, computed from its chain, written on export), its uses (em:use) and seven measures (em:trisPerM2, em:texelDensityDD, em:textureCount, em:textureSidePx, em:uvRatio, em:reductionFromLod0, em:geometricErrorM). v1.6.14 (2026-10-02, dev30, decided by E.D. on the dev29 report): section 18 — em:retrievedFrom, where a retrieval came from (D1), and em:membersDigest, the digest of a file_set with a predicate of its own (D4; em:digestCovers stays for compatibility). v1.6.13 (2026-10-02, dev29, measured on San Pietro): seven DatatypeProperties, section 17 — how the bytes of a resource are packed and what its digest covers (em:packaging, em:tier, em:digestCovers, em:contentDigest) and what a DTC step declares (em:technique, em:parameters, em:software, the last two rdf:JSON): the round trip em.json → TTL → em.json lost all seven. v1.6.12 (2026-11-01, dev28, decided by E.D. 2026-10-01): no new term — em:authMode admits a third value, 'declared' (an iD typed in a tool's preferences and checked by nobody), with no em:attestedBy. v1.6.11 (2026-10-31, dev27, decided by E.D. 2026-10-01): ten properties. Section 15, several addresses of ONE resource (em:hasAddress to <resource>/address/<i>, em:locator, em:checkedAt, em:reachable) and a dated digest (em:checksumAt); section 16, how the hand of a signature had entered (em:createdVia, em:modifiedVia, em:validatedVia to <node>/auth/<stamp>, em:authMode orcid | node_password, em:attestedBy the StratiGraph node). The language of the content of a resource leaves as dcterms:language: no em: term. v1.6.10 (2026-10-29, MICRO le traduzioni, decided by E.D. 2026-10-01): six DatatypeProperties for the language of the original and its translations (section 14) — em:originalLanguage on any node, which says which literal is the original once translations share its predicate, and em:sourceLanguage, em:translatedField, em:translationMethod, em:sourceDigest, em:reviewRequested on a TranslationNode, which is a plain crm:E33_Linguistic_Object reached by crm:P73_has_translation: CIDOC has the class and the relation, so no em: class is added. v1.6.9 (2026-10-18, MICRO la risorsa e i suoi file): em:ResourceFile, ONE FILE of a resource (node datamodel 1.6.17), a subclass of crmdig:D1_Digital_Object; the resource is composed of its files by crm:P106_is_composed_of (connections has_file, 1.6.30). A distinct URI because a DTC output resource is already typed crmdig:D1, and a file typed only D1 would read back as a resource. v1.6.2 (2026-09-21, CIDOC repair pass): the eight terms the datamodels cited and this file never defined are declared in section 12; em:NodeGroup and em:ParadataNodeGroup leave the undeclared crm:E78_Collection for crm:E73_Information_Object and crm:E89_Propositional_Object; em:SemanticShape leaves crmgeo:SP5 for crm:E73_Information_Object, provisionally; crmarchaeo:AP11_has_physical_relation becomes AP11_has_physical_relation_to, the name CRMarchaeo has used since 2.0; and em:RepresentationModel says what a representation model IS. v1.6.5 (2026-10-20, MICRO la definizione dell\'unita\'): em:hasDefinition, the DEFINIZIONE of a stratigraphic unit as a subproperty of crm:P2_has_type — declared for the node datamodel 1.6.9 entry StratigraphicNode.properties.definition, not emitted by default (owl:versionInfo was left at 1.6.2 by the 1.6.3/1.6.4 passes and is realigned here). v1.6.8 (2026-10-11, MICRO la geometria per origine): the vertices of a 3D reading (point, line, polyline) are data of the region (node datamodel 1.6.15, AnnotationRegionNode.coords) and leave for RDF as ONE GeoSPARQL 1.1 literal: <region> geo:hasGeometry <region>/geometry, a geo:Geometry with geo:asWKT '<CRS IRI> POINT Z (x y z)' | 'MULTIPOINT Z (...)' | 'LINESTRING Z (...)'^^geo:wktLiteral. WHY GeoSPARQL and not em: terms: the WKT literal is the standard every triplestore with a spatial index reads, and it is the 3D twin of the Media Fragment a 2D region already emits (a string a consumer outside EM can act on); CRMgeo was built to meet GeoSPARQL at exactly this point (SP5 Geometric Place Expression ~ geo:Geometry), and an em:coords literal would say the same thing to nobody. The CRS travels INSIDE the literal, so it cannot be separated from the numbers: em:LocalSceneFrame (declared here) for the scene-local frame, the OGC EPSG IRI for a projected one. em:vertexCount stays (the count of a .glb resource above the threshold). The .glb of a reading is no longer a SemanticShape's rdfs:seeAlso: above coords.inline_max_vertices (500) it is a ResourceNode the region reaches with has_linked_resource (crm:P67_refers_to), and a proxy's .glb is likewise a proxy_model ResourceNode (connections 1.6.28-1.6.29). v1.6.7 (2026-09-30, MICRO la cattura in RDF): no em: term added — the acquisition of a digital object is typed by its KIND. A capture is not a transfer: crmdig:D2_Digitization_Process for a photograph or a laser scan, crmdig:D11_Digital_Measurement_Event for a topographic or GNSS survey, crm:E65_Creation for a field drawing or a recording sheet (made by hand; the file is their copy, so no D7 machine event is asserted); a retrieval (download, local import, URI, ingest) stays crmdig:D12_Data_Transfer_Event. The rule is data (em_visual_rules 1.6.24, dtc_kinds.acquisition.<kind>.mapping). v1.6.6 (2026-10-07, MICRO la misura in RDF): the place of a reading gets its quote and its measure. The quote of a passage reuses W3C Web Annotation (oa:hasSelector -> oa:TextQuoteSelector, oa:exact) — the only standard term for a quote, which has no fragment-string form; its offsets stay the RFC 5147 em:hasSelector 'char=s,e'. The length of a line or polyline reuses CIDOC (crm:P43_has_dimension -> crm:E54_Dimension, P90_has_value xsd:double, P91_has_unit -> a QUDT unit IRI); two em: terms are new, em:vertexCount and em:crs, for what neither vocabulary says. The .glb of a 3D reading is not described here: its URL is the rdfs:seeAlso of the SemanticShape the region reaches with em:hasSemanticShape, and no coordinate enters RDF."@en ;
     owl:imports <http://www.cidoc-crm.org/cidoc-crm/> ,
                 <http://www.cidoc-crm.org/extensions/crminf/> ,
                 <http://www.cidoc-crm.org/extensions/crmarchaeo/> ,
@@ -996,5 +996,64 @@ em:membersDigest
     rdfs:comment "The digest of a file_set, 'sha256:<hex>' of the canonical list of its members (role, path and digest of each) — the identity of the set, not the bytes of any one file; it is checked against the files with dtcstamp.verify_members, never by hashing one file. The same value em:checksum carries beside em:digestCovers 'members', given a predicate of its own so a reader need not read two triples together; em:digestCovers stays for compatibility. Maps to: node_datamodel ResourceNode.properties.members_digest."@en .
 
 # ============================================================================
-# End of em.ttl v1.6.14
+# 19. The level, the uses and the measures of a version of an asset (v1.6.15,
+#     decided by E.D. 2026-10-04, D1)
+# ============================================================================
+
+em:lodLevel
+    a owl:DatatypeProperty ;
+    rdfs:label "LOD level"@en ;
+    rdfs:range xsd:string ;
+    rdfs:comment "The level of a VERSION of an asset — lod0 (the first version derived from the master that one can work on), lod1…lodN (lod_generation steps from LOD0). An ordinal INSIDE ONE derivation chain: computed from the chain, written when the graph leaves, compared with the chain when it comes back. The master (em:tier 'master') has none. Maps to: node_datamodel ResourceNode.properties.lod_level."@en .
+
+em:use
+    a owl:DatatypeProperty ;
+    rdfs:label "use"@en ;
+    rdfs:range xsd:string ;
+    rdfs:comment "What a version of an asset is FOR, one triple per use: analysis, realtime, web, mobile_ar, print, render, preview (correspondences with Smithsonian Voyager and 3D Tiles in the datamodel's note). Maps to: node_datamodel ResourceNode.properties.use."@en .
+
+em:trisPerM2
+    a owl:DatatypeProperty ;
+    rdfs:label "triangles per square metre"@en ;
+    rdfs:range xsd:double ;
+    rdfs:comment "Triangles per square metre of surface of a version: a measure, with no target. Maps to: node_datamodel ResourceNode.properties.tris_per_m2."@en .
+
+em:texelDensityDD
+    a owl:DatatypeProperty ;
+    rdfs:label "texel density (Demetrescu-D'Annibale)"@en ;
+    rdfs:range xsd:double ;
+    rdfs:comment "The side of a texel in millimetres, in the form of the Demetrescu-D'Annibale formula (Demetrescu et al. 2026, Remote Sensing 18, 203, Eq. 1; reference 1.26). Maps to: node_datamodel ResourceNode.properties.texel_density_dd."@en .
+
+em:textureCount
+    a owl:DatatypeProperty ;
+    rdfs:label "texture count"@en ;
+    rdfs:range xsd:nonNegativeInteger ;
+    rdfs:comment "How many texture atlases a version has. Maps to: node_datamodel ResourceNode.properties.texture_count."@en .
+
+em:textureSidePx
+    a owl:DatatypeProperty ;
+    rdfs:label "texture side (px)"@en ;
+    rdfs:range xsd:nonNegativeInteger ;
+    rdfs:comment "The side of a texture atlas of a version, in pixels. Maps to: node_datamodel ResourceNode.properties.texture_side_px."@en .
+
+em:uvRatio
+    a owl:DatatypeProperty ;
+    rdfs:label "UV ratio"@en ;
+    rdfs:range xsd:double ;
+    rdfs:comment "The share of the atlas filled by the UV islands (0.6 in the reference). Maps to: node_datamodel ResourceNode.properties.uv_ratio."@en .
+
+em:reductionFromLod0
+    a owl:DatatypeProperty ;
+    rdfs:label "reduction from LOD0"@en ;
+    rdfs:range xsd:double ;
+    rdfs:comment "Triangles of this version divided by those of LOD0 (3DSC's «magnitude»). Maps to: node_datamodel ResourceNode.properties.reduction_from_lod0."@en .
+
+em:geometricErrorM
+    a owl:DatatypeProperty ;
+    rdfs:label "geometric error (m)"@en ;
+    rdfs:range xsd:double ;
+    rdfs:comment "For a 3D Tiles tileset: its geometricError in metres. Maps to: node_datamodel ResourceNode.properties.geometric_error_m."@en .
+
+# ============================================================================
+# End of em.ttl v1.6.15
 # ============================================================================

s3dgraphy-1.6.0.dev35/src/s3dgraphy/JSON_config/em_state_symbols.json

@@ -0,0 +1,254 @@
+{
+  "_version": "1.0.0",
+  "_note": "I1 (decided by E.D., 4 Oct 2026) · ONE list of the STATES the EM tools show, with the SYMBOL of each and its MEANING. What is standardised is the symbol and what it means, not the final form: colour, stroke and style stay each tool's (EMStudio, EM Tools, StratiField draw their own version of the glyph). Each tool tests that every state here has its sign and that it shows no state that is not here. The file states are those of the one resolver (s3dgraphy.resources.locate.STATES). Vendored by EMStudio's ./em.sh sync next to em_visual_rules.json.",
+  "families": {
+    "file": "Where the bytes of a resource are (the resolver, R1)",
+    "node": "The StratiGraph node",
+    "room": "The room of a graph",
+    "sync": "How aligned this copy is with the room",
+    "role": "Your role in the room",
+    "scene": "An object of a Blender scene"
+  },
+  "states": {
+    "file.on_disk": {
+      "family": "file",
+      "glyph": "●",
+      "label": {
+        "it": "sul disco",
+        "en": "on the disk"
+      },
+      "meaning": {
+        "it": "I byte sono su questo computer (in un percorso o nella cache).",
+        "en": "The bytes are on this computer (at a path or in the cache)."
+      }
+    },
+    "file.on_node": {
+      "family": "file",
+      "glyph": "☁",
+      "label": {
+        "it": "nel nodo",
+        "en": "on the node"
+      },
+      "meaning": {
+        "it": "Il nodo custodisce i byte (lo sha256 risponde), questo computer no.",
+        "en": "The node keeps the bytes (its sha256 answers); this computer does not."
+      }
+    },
+    "file.both": {
+      "family": "file",
+      "glyph": "◉",
+      "label": {
+        "it": "in entrambi",
+        "en": "in both"
+      },
+      "meaning": {
+        "it": "I byte sono qui e nel nodo.",
+        "en": "The bytes are here and on the node."
+      }
+    },
+    "file.reference_only": {
+      "family": "file",
+      "glyph": "↗",
+      "label": {
+        "it": "solo riferimento",
+        "en": "reference only"
+      },
+      "meaning": {
+        "it": "C'è solo un indirizzo altrove (un URL, un bucket).",
+        "en": "There is only an address somewhere else (a URL, a bucket)."
+      }
+    },
+    "file.missing": {
+      "family": "file",
+      "glyph": "✕",
+      "label": {
+        "it": "mancante",
+        "en": "missing"
+      },
+      "meaning": {
+        "it": "Il file non si trova da nessuna parte raggiungibile da qui.",
+        "en": "The file is nowhere that can be reached from here."
+      }
+    },
+    "file.empty_copy": {
+      "family": "file",
+      "glyph": "◌",
+      "label": {
+        "it": "copia vuota",
+        "en": "empty copy"
+      },
+      "meaning": {
+        "it": "C'è un file ma i suoi byte sono zeri: una copia incompleta, da rifare.",
+        "en": "A file is here but its bytes are zeros: an incomplete copy, to be made again."
+      }
+    },
+    "node.reachable": {
+      "family": "node",
+      "glyph": "⬢",
+      "label": {
+        "it": "raggiungibile",
+        "en": "reachable"
+      },
+      "meaning": {
+        "it": "Il nodo risponde adesso.",
+        "en": "The node answers now."
+      }
+    },
+    "node.unreachable": {
+      "family": "node",
+      "glyph": "⬡",
+      "label": {
+        "it": "non raggiungibile",
+        "en": "unreachable"
+      },
+      "meaning": {
+        "it": "Il nodo non risponde: si lavora sul computer, si allinea dopo.",
+        "en": "The node does not answer: work on this computer, align later."
+      }
+    },
+    "node.global": {
+      "family": "node",
+      "glyph": "⊕",
+      "label": {
+        "it": "in rete globale",
+        "en": "on the global network"
+      },
+      "meaning": {
+        "it": "Il nodo è raggiungibile da fuori la rete locale (federato o pubblico).",
+        "en": "The node can be reached from outside the local network (federated or public)."
+      }
+    },
+    "node.local_only": {
+      "family": "node",
+      "glyph": "⌂",
+      "label": {
+        "it": "solo locale",
+        "en": "local only"
+      },
+      "meaning": {
+        "it": "Il nodo ascolta solo questo computer o la rete locale.",
+        "en": "The node listens to this computer or the local network only."
+      }
+    },
+    "room.inside": {
+      "family": "room",
+      "glyph": "▣",
+      "label": {
+        "it": "dentro",
+        "en": "inside"
+      },
+      "meaning": {
+        "it": "Questo grafo è in una stanza: le modifiche vanno lì.",
+        "en": "This graph is in a room: the edits go there."
+      }
+    },
+    "room.outside": {
+      "family": "room",
+      "glyph": "□",
+      "label": {
+        "it": "fuori",
+        "en": "outside"
+      },
+      "meaning": {
+        "it": "Nessuna stanza: il grafo è un file su questo computer.",
+        "en": "No room: the graph is a file on this computer."
+      }
+    },
+    "room.read_only": {
+      "family": "room",
+      "glyph": "⊘",
+      "label": {
+        "it": "sola lettura",
+        "en": "read only"
+      },
+      "meaning": {
+        "it": "Sei nella stanza ma il tuo ruolo non scrive.",
+        "en": "You are in the room but your role does not write."
+      }
+    },
+    "sync.aligned": {
+      "family": "sync",
+      "glyph": "✓",
+      "label": {
+        "it": "allineato",
+        "en": "aligned"
+      },
+      "meaning": {
+        "it": "Quello che hai è quello che ha la stanza.",
+        "en": "What you have is what the room has."
+      }
+    },
+    "sync.pending": {
+      "family": "sync",
+      "glyph": "⋯",
+      "label": {
+        "it": "in attesa",
+        "en": "pending"
+      },
+      "meaning": {
+        "it": "Ci sono modifiche partite e non ancora confermate (o da mandare).",
+        "en": "There are edits sent and not yet confirmed (or still to send)."
+      }
+    },
+    "sync.conflict": {
+      "family": "sync",
+      "glyph": "≠",
+      "label": {
+        "it": "in conflitto",
+        "en": "in conflict"
+      },
+      "meaning": {
+        "it": "Due mani hanno cambiato la stessa cosa: si decide chi vince.",
+        "en": "Two hands changed the same thing: who wins is to be decided."
+      }
+    },
+    "role.owner": {
+      "family": "role",
+      "glyph": "★",
+      "label": {
+        "it": "proprietario",
+        "en": "owner"
+      },
+      "meaning": {
+        "it": "Decide chi entra e che cosa la stanza tiene.",
+        "en": "Decides who comes in and what the room keeps."
+      }
+    },
+    "role.editor": {
+      "family": "role",
+      "glyph": "✎",
+      "label": {
+        "it": "editor",
+        "en": "editor"
+      },
+      "meaning": {
+        "it": "Scrive nel grafo e carica i file.",
+        "en": "Writes in the graph and uploads files."
+      }
+    },
+    "role.viewer": {
+      "family": "role",
+      "glyph": "◎",
+      "label": {
+        "it": "lettore",
+        "en": "viewer"
+      },
+      "meaning": {
+        "it": "Legge, non scrive.",
+        "en": "Reads, does not write."
+      }
+    },
+    "scene.only_here": {
+      "family": "scene",
+      "glyph": "◆",
+      "label": {
+        "it": "solo qui",
+        "en": "only here"
+      },
+      "meaning": {
+        "it": "Un oggetto della scena che non è del grafo (decorazione, prova): non sale mai.",
+        "en": "An object of the scene that is not the graph's (a decoration, a trial): never uploaded."
+      }
+    }
+  }
+}

{s3dgraphy-1.6.0.dev33 → s3dgraphy-1.6.0.dev35}/src/s3dgraphy/JSON_config/node_registry.generated.json

@@ -1,6 +1,6 @@
 {
  "_generated": "by `python -m s3dgraphy.tools.sync_node_datamodel` — DO NOT hand-edit. The flat class hierarchy (parent/node_type/description) is derived from the Python Node subclasses; hand-authored semantics and CIDOC mappings live in s3Dgraphy_node_datamodel.json.",
- "s3Dgraphy_data_model_version": "1.6.24",
+ "s3Dgraphy_data_model_version": "1.6.25",
  "node_types": {
   "ActivityNodeGroup": {
    "parent": "GroupNode",

{s3dgraphy-1.6.0.dev33 → s3dgraphy-1.6.0.dev35}/src/s3dgraphy/JSON_config/s3Dgraphy_node_datamodel.json

@@ -1,6 +1,6 @@
 {
-  "s3Dgraphy_data_model_version": "1.6.24",
-  "description": "v1.6.24 (dev30, decided by E.D. 2026-10-02 on the dev29 report): DTCAcquisitionNode.retrieved_from — where a retrieved object came from, a DOI or a URL (em:retrievedFrom, D1; optional, validate warns «download without origin»). ResourceNode.members_digest names em:membersDigest, the digest of a file_set with a predicate of its own beside em:checksum + em:digestCovers (D4; not a second field). ResourceNode.packaging carries its vocabulary with values and labels, translated in datamodel_translations.json (packagings; A3). ResourceNode.content_digest also holds the digest of the data of a master inside another file — a Metashape model's mesh.ply — compared, never verified by downloading (D7). GCPSetNode gains data.control (ground_control_points | camera_positions) and data.accuracy_m: a chunk referenced only by its cameras' GPS is absolute with the control said for what it is, and validate warns «georeferenced only by camera GPS» (D7). Node.properties.lang states the one explicit exception to the AI marker: a recognised language confirmed by a person is data.lang only (U5). CRMem 1.6.14. v1.6.23 (dev29, 2026-10-02, measured on San Pietro): seven properties that the round trip em.json → TTL → em.json lost now leave and come back — ResourceNode packaging / tier / digest_covers / content_digest (em:packaging, em:tier, em:digestCovers, em:contentDigest) and the declared fields of a DTC step, technique / parameters / software (em:technique, em:parameters, em:software, the last two as rdf:JSON). digest_covers admits members (a file_set). The blend:// locator stays out of RDF on purpose: it is a private path. v1.6.22 (dev28, 2026-11-01, decided by E.D. 2026-10-01 on the dev27 report): the access mode of a signature (created_auth / modified_auth / validated_auth) admits a third mode, 'declared' — an iD typed in a tool's preferences and checked by nobody (EMStudio's declared identity, EM Tools' local identity), with no attested_by; through a relay the mode is the relay's, read from the token (crdt.stamp_auth), not the client's declaration. The language a node is born in travels in the add_node op (crdt.make_op requires it of the producer, 'und' when unknown); the study's language is read only for old ops, said and counted. CRMem 1.6.12. v1.6.21 (dev27, 2026-10-31, decided by E.D. 2026-10-01, «il testo, la risorsa e la selezione» and «l'accesso sul campo»): ResourceNode.properties gains lang — on a resource the language(s) of its CONTENT, one tag or a sorted list, leaving as dcterms:language and outside the cascade of the texts — addresses (several addresses of ONE resource, same digest: em:hasAddress with em:locator, em:residency, em:checkedAt, em:reachable) and checksum_at (a dated digest, em:checksumAt). Node.properties gains created_auth / modified_auth / validated_auth: how the hand of a signature had entered, {mode: orcid | node_password, attested_by} (em:createdVia / em:modifiedVia / em:validatedVia, em:authMode, em:attestedBy). data.lang is written at birth (s3dgraphy.language.stamp_birth_language), also when equal to the study's. v1.6.20 (MICRO le traduzioni, 2026-10-29, decided by E.D. 2026-10-01, «Le traduzioni»): NEW TranslationNode (TRANSL, crm:E33_Linguistic_Object) — ONE translation of one text field of one node. The original stays a string in its field (data.lang on the node, else the study's), never overwritten; each translation is a node reached by has_translation (crm:P73_has_translation, connections 1.6.34) with data.lang (arrival), data.from_lang (departure, written because the original can change), data.field (CRDT vocabulary: description | data.<key>; a PropertyNode's value is data.value; never name), data.text, data.method (manual | ai | edition), data.source_digest (sha256 of the original translated: a different digest = «da riallineare») and data.review_requested («da rivedere»). Who: has_author; AI: data.ai_assisted, unverified until validated_by; an edition: extracted_from → the DocumentNode. RDF (em.ttl 1.6.10): Node.properties.lang names em:originalLanguage — the node's own data.lang leaves as that literal whenever it is declared, equal to the study's too, so a reader tells the original literal from the translations that share its predicate and the round trip gives data.lang back exactly where it was (the D.1 limit of 1.6.19 is closed); the TranslationNode's fields name em:sourceLanguage, em:translatedField, em:translationMethod, em:sourceDigest, em:reviewRequested. v1.6.19 (MICRO la lingua dei dati, 2026-10-27, decided by E.D. 2026-09-28): Node.properties.description becomes an object {cidoc: P3_has_note, natural_language: true, note} — the MARKER that says the description is text in a natural language and leaves in RDF with its language tag; declared once on the base class and inherited by every node type. name is NOT marked: names are invariant identities. No field added, no node element, no graph change: the em.json is the same; only the RDF literal gains its tag. v1.6.18 (MICRO i termini di em.ttl nel datamodel, 2026-10-26, decided by E.D. 2026-10-01 — the datamodel JSON is the truth, so every em: term of em.ttl is cited by a datamodel or is a written exception): the em: predicates the RDF exporter already writes are now NAMED in properties, as plain-string mapping notes (no field added, no node element, no graph change). Node (inherited by every class): the last-hand stamps created_by em:createdBy / modified_by em:lastEditedBy / modified_at em:modifiedAt (created_at prov:generatedAtTime), the tombstone removed.ts em:removedAt / removed.by em:removedBy, the AI marker ai_assisted.by em:aiAssistedBy / .model em:aiModel / .prompt_ref em:aiPromptRef / .fields em:aiAssistedField and the verification validated_by em:validatedBy / validated_at em:validatedAt (properties_note). ResourceNode: checksum em:checksum, scope em:resourceScope, residency em:residency. SemanticShapeNode: convexshapes em:convexShape, spheres em:sphere. AnnotationRegionNode: crs em:crs, coords.frame_iri em:LocalSceneFrame. AuthorNode and AuthorAINode: verified em:orcidVerified (AuthorAINode also names orcid P48, which the exporter writes for both). LocationNodeGroup.propagation.mapping: uri em:propagation. THREE ENTRIES CORRECTED TO WHAT THE CODE WRITES (measured in rdf_exporter.py): PropertyNode.property_type was P2_has_type, is em:hasQualiaType; AuthorAINode model / prompt_reference were P3_has_note, are em:modelIdentifier / em:promptReference; ResourceFileNode.checksum was P1_is_identified_by, is em:checksum; and LocationNodeGroup.propagation said 'not serialized to triplestore' while the exporter has written the non-default value as em:propagation since c1a702c (2026-08-12). v1.6.17 (MICRO la risorsa e i suoi file, 2026-10-18, decided by E.D. 2026-09-30): NEW ResourceFileNode (FILE, crmdig:D1_Digital_Object) — the ResourceNode is the set, the ResourceFileNode is each file, reached by has_file (connections 1.6.30) with role and relative path on the edge. With one file the node is implicit (url and checksum stay on the ResourceNode, as today). ResourceNode.PACKAGINGS += file_set (a few files that call each other: obj → mtl → textures, gltf → bin, shp and companions) and datablock (one object inside a file, a blend:// locator). Representations of the same thing are sibling ResourceNodes tied by dtc_derived_from and chosen by tier and packaging. ADDITIVE: nothing narrowed, no graph changes. v1.6.16 (MICRO le annotazioni ATON sull'asset, 2026-10-15, decided by E.D.): AnnotationRegionNode gains geometry_kind 'volume' — an annotation that encloses a part of a 3D model (ATON / Hathor convex hulls and spheres) and is the proxy of no unit. The region carries no vertices: it reaches a SemanticShapeNode (convexshapes, spheres) with has_semantic_shape and the model with is_on_resource. geometry.aton.import_aton_scene makes one for every semantic id no EM node is named after (a stratigraphic unit only with an explicit create_type); api.promote_region_to_proxy turns it into the proxy of a unit later. RDF: P2_has_type 'volume', no selector, no WKT; the shape travels as itself. Additive. v1.6.15 (MICRO la geometria per origine, 2026-10-11, decided by E.D. 2026-09-30): AnnotationRegionNode's point / line / polyline keep their vertices IN THE NODE, data.coords [[x, y, z], ...] (scene-local, glTF Y-up, metres) with crs and, for a line or a polyline, length and unit — no .glb and no SemanticShape for a reading. New block coords (inline_max_vertices 500: above it the vertices go to a .glb resource via has_linked_resource, with a warning). RDF: geo:hasGeometry -> <region>/geometry geo:asWKT (POINT Z / LINESTRING Z, GeoSPARQL). The readings/<id>.glb of 2026-10-06 are migrated on opening. v1.6.14 (MICRO la cattura in RDF, 2026-09-30): DTCAcquisitionNode.mapping.by_kind — its D12 is the class of a retrieval; a capture takes the class its kind declares in em_visual_rules 1.6.24 (D2 / D11 / E65). Mapping text only, no field changed. v1.6.13 (MICRO i generi delle US, 2026-09-30, decided by E.D. the same day): stratigraphic_kind gains 'coating' — the USR (rivestimento) and its English translation USS (surface): plaster, floors, revetments — with `labels`, `codes` and `default_code` per kind; new node element `source_code` (data.source_code) keeps the code a unit came in with when it is not its kind's default, so the way back to pyArchInit gives the same code. A legacy node_type 'USR' / 'USS' opens as US + coating. v1.6.12 (MICRO la cattura nel DTC e le murature, 2026-09-30): StratigraphicUnit (US) gains the node element `stratigraphic_kind` (em.json data.stratigraphic_kind; today one value, 'masonry'): a USM is a US + masonry, and the legacy node_type 'USM' — never a type of this datamodel — opens as that. DTCAcquisitionNode's description names the two families of the acquisition axis (em_visual_rules 1.6.22: capture / retrieval). v1.6.11 (MICRO la misura in RDF, 2026-10-07): AnnotationRegionNode.properties says how the fields left unprojected by 1.6.10 now travel — the quote of a passage as oa:TextQuoteSelector, the length of a line/polyline as crm:E54_Dimension (P90 value, P91 QUDT unit, em:crs), vertex_count as em:vertexCount. CRMem (em.ttl) 1.6.5 -> 1.6.6. Mapping text only, no field changed. v1.6.10 (MICRO la geometria della lettura, 2026-10-06, decided by E.D. on 2026-09-29): AnnotationRegionNode becomes the node of THE PLACE A READING LOOKED AT, with a new field geometry_kind: region2d (default, every older region), passage (start, end, text), point, line, polyline. The three 3D kinds keep their coordinates in a .glb (glTF POINTS / LINES / LINE_STRIP) linked with has_semantic_shape exactly like a proxy's payload, never in the em.json; the node keeps vertex_count and, for line/polyline, length + unit + crs (api.measure). See the entry's geometry_kinds and glb_payload. Paired with connections 1.6.27 (is_on_resource.target += the representation models). Additive: a region without geometry_kind reads as region2d. v1.6.9 (MICRO la definizione dell'unita', 2026-10-20, decided by E.D. on 2026-09-27): StratigraphicNode.properties gains `definition`, the DEFINIZIONE of the US sheet, as an element of the node like name and description and NOT a qualia. Value = a controlled-vocabulary concept {concept, label}; em.json carries it as data.definition (CRDT field 'data.definition', no change to the frozen em.json v1 node shape); inherited by every stratigraphic subtype. The RDF projection is declared in the entry itself (`rdf`): crm:P2_has_type -> crm:E55_Type when a concept URI is present, nothing when only a label is (`label_only: null`). CRMem 1.6.4 -> 1.6.5 for the companion em:hasDefinition (subproperty of crm:P2_has_type, declared, not emitted by default). Additive only. v1.6.7 (CRMem WIRING, 2026-09-24): rimosso il campo legacy `cidoc_s3d` da tutte le mapping. Non era letto da nessuna parte del codice e portava quattro nomi di classe senza namespace, mai dichiarati e mai emessi: EpochNode = StratigraphicTimeframe; ActivityNodeGroup = StratigraphicActivity; ParadataNodeGroup = ParadataCollection; ResourceNode = ExternalResourceReference. Il prefisso CIDOC-S3D non esiste piu' in nessuno dei due datamodel. v1.6.6 (CIDOC REPAIR, 2026-09-21): classes that pointed at IRIs nobody declares. Checked by parsing the official releases, not from memory. crm:E78_Collection is gone from CIDOC CRM 7.1.3 — renamed E78_Curated_Holding — and E.D. decided NOT to follow the rename, because E78_Curated_Holding is a subclass of E24 Physical Human-Made Thing and a group of nodes is not a physical thing. The three classes that carried it therefore split, each to the class it actually is: GroupNode and RepresentationModelNodeGroup to crm:E73_Information_Object (a conceptual set, and an E90 Symbolic Object, which is what the P106i membership edge needs at both ends), ParadataNodeGroup to crm:E89_Propositional_Object — which is what a gathered body of reasoning IS and what the range of crm:P129i_is_subject_of demands, that being the predicate has_paradata_nodegroup takes in connections 1.6.17 the same day; it stays an E90 through em:NodeGroup, so the membership edge does not break. SemanticShapeNode leaves crmgeo:SP5_Geometric_Place_Expression for crm:E73_Information_Object, PROVVISORIAMENTE: SP5 is not declared at the crmgeo namespace this datamodel emits, crmgeo:SP6_Declarative_Place is the better candidate, and the decision is rinviata da E.D. — E73 commits to nothing meanwhile. crm:P131_is_identified_by, deprecated in CRM 7.x together with E82 Actor Appellation, becomes crm:P1_is_identified_by on AuthorNode (name, surname) and AuthorAINode (name). «CRMs3D» is renamed «CRMem», in components and in referenced_ontology_versions alike: the companion ontology is em.ttl and its namespace is em:, so the old name pointed at nothing anyone could look up. CRMsci moves 3.1 -> 3.2 (latest release). The eight em: terms this file and the connections datamodel cite but em.ttl never defined are now declared there (em:FunctionalUnit, em:GCPSet, em:Narrative, em:NeutralSU, em:RegistrationTransform, em:RepresentationModelNodeGroup, em:hasSubEpoch, em:validatedBy), with domain, range and superclass read off these datamodels and nothing invented. NOT TOUCHED: the `alternative` and legacy `cidoc_s3d` prose fields, which still discuss E78 as an option — prose, not a projection, and rewording them is modelling rather than repair. v1.6.5 (EM16-RMNG, 2026-09-10): adds RepresentationModelNodeGroup, the RM container as a first-class group of the graph — sixth subtype of GroupNode, keeping the parent's E78 Collection because a container IS a curatorial set. Paired with connections datamodel 1.6.14, which adds the is_in_representation_model_group membership edge and widens has_representation_model.target to accept the group. Additive only: no existing entry changed. s3Dgraphy nodes datamodel including node types with CIDOC-CRM mappings. v1.6.4 adds the ADDITIVE georeferencing_nodes section (GCPSetNode = em:GCPSet, RegistrationTransformNode = em:RegistrationTransform, both subclasses of crm:E73_Information_Object with their own extension URIs so the RDF projection stays bijective): the CONTROL and the SOLUTION that place a produced model in the world, introduced with the photogrammetry processing connector. The two modes of that connector are the SHAPE of the graph (a transform with a CRS that has_gcp_set points at = absolute; a transform with crs=null and no control set = a site-local frame; no transform at all = nobody placed it), never a flag. No existing family changed. v1.6.3 re-reads SemanticShapeNode as a PAYLOAD carrier: the proxy of a unit is now a PropertyNode of qualia type 'geometry' that points at the shape (has_semantic_shape), so the proxy inherits the paradata chain it never had. Breaking for consumers that read the proxy as a standalone SemanticShape. v1.6.2 adds AnnotationRegionNode (em:AnnotationRegion, subclass of crm:E36_Visual_Item): the geometry of a 2D annotation in NORMALISED image space, distinct from SemanticShapeNode (3D scene geometry, crmgeo:SP5) - the semantics of the 2D annotator, defined before any canvas exists. v1.6.0 inaugurates a systematic CIDOC-CRM mapping revision: complete audit of all node types against CIDOC-CRM, CRMarchaeo, CRMinf, CRMdig, CRMsci, CRMgeo; replacement of legacy 'cidoc_s3d' pseudo-class names (invented strings without IRI or superclass declaration) with formal em:/s3d: IRIs declared as proper subclasses of CRM classes; introduction of CRMinf as primary (not alternative) for the paradata chain (ParadataNode, PropertyNode interpretive case, ExtractorNode, CombinerNode); introduction of PROV-O for AuthorNode to cover both human and AI agents; alignment with the Heritage Digital Twin Ontology (HDT-O) for containment / granularity properties; LocationNodeGroup (v1.5.3) adopted as the reference pattern (CIDOC-native composition via P2_has_type → E55 Type instances, with explicit extension_status and rationale). Companion deliverables: em.ttl (formal EM extension ontology, dereferenceable via w3id.org/em/) and hdto_extension.ttl (HDT-O granularity properties: contains_HDT, contains_SU, isPrimary). v1.5.4 added RSF (Reused Special Find — spolia) as a stratigraphic subtype, octagon with red border, family=real, is_series=false. Originating DP: DP-26 (spolia project, last DP before the EM 1.5 cut). v1.5.3 added LocationNodeGroup (E53 Place + E55 Type) for spatial / locational membership orthogonal to ActivityNodeGroup (intention) and EpochNode (time). v1.5.2 added family + is_series classification metadata on stratigraphic subtypes.",
+  "s3Dgraphy_data_model_version": "1.6.25",
+  "description": "v1.6.25 (D1, MICRO un solo vocabolario, decided by E.D. 4 Oct 2026): GeoPositionNode.rotation_reference = 'grid' (D2: the rotation is measured from the GRID north of the CRS). ResourceNode.lod_level (em:lodLevel, computed from the chain, written only on export and checked at load), ResourceNode.use (em:use, a list of analysis | realtime | web | mobile_ar | print | render | preview) and seven measures of a version (em:trisPerM2, em:texelDensityDD, em:textureCount, em:textureSidePx, em:uvRatio, em:reductionFromLod0, em:geometricErrorM). v1.6.24 (dev30, decided by E.D. 2026-10-02 on the dev29 report): DTCAcquisitionNode.retrieved_from — where a retrieved object came from, a DOI or a URL (em:retrievedFrom, D1; optional, validate warns «download without origin»). ResourceNode.members_digest names em:membersDigest, the digest of a file_set with a predicate of its own beside em:checksum + em:digestCovers (D4; not a second field). ResourceNode.packaging carries its vocabulary with values and labels, translated in datamodel_translations.json (packagings; A3). ResourceNode.content_digest also holds the digest of the data of a master inside another file — a Metashape model's mesh.ply — compared, never verified by downloading (D7). GCPSetNode gains data.control (ground_control_points | camera_positions) and data.accuracy_m: a chunk referenced only by its cameras' GPS is absolute with the control said for what it is, and validate warns «georeferenced only by camera GPS» (D7). Node.properties.lang states the one explicit exception to the AI marker: a recognised language confirmed by a person is data.lang only (U5). CRMem 1.6.14. v1.6.23 (dev29, 2026-10-02, measured on San Pietro): seven properties that the round trip em.json → TTL → em.json lost now leave and come back — ResourceNode packaging / tier / digest_covers / content_digest (em:packaging, em:tier, em:digestCovers, em:contentDigest) and the declared fields of a DTC step, technique / parameters / software (em:technique, em:parameters, em:software, the last two as rdf:JSON). digest_covers admits members (a file_set). The blend:// locator stays out of RDF on purpose: it is a private path. v1.6.22 (dev28, 2026-11-01, decided by E.D. 2026-10-01 on the dev27 report): the access mode of a signature (created_auth / modified_auth / validated_auth) admits a third mode, 'declared' — an iD typed in a tool's preferences and checked by nobody (EMStudio's declared identity, EM Tools' local identity), with no attested_by; through a relay the mode is the relay's, read from the token (crdt.stamp_auth), not the client's declaration. The language a node is born in travels in the add_node op (crdt.make_op requires it of the producer, 'und' when unknown); the study's language is read only for old ops, said and counted. CRMem 1.6.12. v1.6.21 (dev27, 2026-10-31, decided by E.D. 2026-10-01, «il testo, la risorsa e la selezione» and «l'accesso sul campo»): ResourceNode.properties gains lang — on a resource the language(s) of its CONTENT, one tag or a sorted list, leaving as dcterms:language and outside the cascade of the texts — addresses (several addresses of ONE resource, same digest: em:hasAddress with em:locator, em:residency, em:checkedAt, em:reachable) and checksum_at (a dated digest, em:checksumAt). Node.properties gains created_auth / modified_auth / validated_auth: how the hand of a signature had entered, {mode: orcid | node_password, attested_by} (em:createdVia / em:modifiedVia / em:validatedVia, em:authMode, em:attestedBy). data.lang is written at birth (s3dgraphy.language.stamp_birth_language), also when equal to the study's. v1.6.20 (MICRO le traduzioni, 2026-10-29, decided by E.D. 2026-10-01, «Le traduzioni»): NEW TranslationNode (TRANSL, crm:E33_Linguistic_Object) — ONE translation of one text field of one node. The original stays a string in its field (data.lang on the node, else the study's), never overwritten; each translation is a node reached by has_translation (crm:P73_has_translation, connections 1.6.34) with data.lang (arrival), data.from_lang (departure, written because the original can change), data.field (CRDT vocabulary: description | data.<key>; a PropertyNode's value is data.value; never name), data.text, data.method (manual | ai | edition), data.source_digest (sha256 of the original translated: a different digest = «da riallineare») and data.review_requested («da rivedere»). Who: has_author; AI: data.ai_assisted, unverified until validated_by; an edition: extracted_from → the DocumentNode. RDF (em.ttl 1.6.10): Node.properties.lang names em:originalLanguage — the node's own data.lang leaves as that literal whenever it is declared, equal to the study's too, so a reader tells the original literal from the translations that share its predicate and the round trip gives data.lang back exactly where it was (the D.1 limit of 1.6.19 is closed); the TranslationNode's fields name em:sourceLanguage, em:translatedField, em:translationMethod, em:sourceDigest, em:reviewRequested. v1.6.19 (MICRO la lingua dei dati, 2026-10-27, decided by E.D. 2026-09-28): Node.properties.description becomes an object {cidoc: P3_has_note, natural_language: true, note} — the MARKER that says the description is text in a natural language and leaves in RDF with its language tag; declared once on the base class and inherited by every node type. name is NOT marked: names are invariant identities. No field added, no node element, no graph change: the em.json is the same; only the RDF literal gains its tag. v1.6.18 (MICRO i termini di em.ttl nel datamodel, 2026-10-26, decided by E.D. 2026-10-01 — the datamodel JSON is the truth, so every em: term of em.ttl is cited by a datamodel or is a written exception): the em: predicates the RDF exporter already writes are now NAMED in properties, as plain-string mapping notes (no field added, no node element, no graph change). Node (inherited by every class): the last-hand stamps created_by em:createdBy / modified_by em:lastEditedBy / modified_at em:modifiedAt (created_at prov:generatedAtTime), the tombstone removed.ts em:removedAt / removed.by em:removedBy, the AI marker ai_assisted.by em:aiAssistedBy / .model em:aiModel / .prompt_ref em:aiPromptRef / .fields em:aiAssistedField and the verification validated_by em:validatedBy / validated_at em:validatedAt (properties_note). ResourceNode: checksum em:checksum, scope em:resourceScope, residency em:residency. SemanticShapeNode: convexshapes em:convexShape, spheres em:sphere. AnnotationRegionNode: crs em:crs, coords.frame_iri em:LocalSceneFrame. AuthorNode and AuthorAINode: verified em:orcidVerified (AuthorAINode also names orcid P48, which the exporter writes for both). LocationNodeGroup.propagation.mapping: uri em:propagation. THREE ENTRIES CORRECTED TO WHAT THE CODE WRITES (measured in rdf_exporter.py): PropertyNode.property_type was P2_has_type, is em:hasQualiaType; AuthorAINode model / prompt_reference were P3_has_note, are em:modelIdentifier / em:promptReference; ResourceFileNode.checksum was P1_is_identified_by, is em:checksum; and LocationNodeGroup.propagation said 'not serialized to triplestore' while the exporter has written the non-default value as em:propagation since c1a702c (2026-08-12). v1.6.17 (MICRO la risorsa e i suoi file, 2026-10-18, decided by E.D. 2026-09-30): NEW ResourceFileNode (FILE, crmdig:D1_Digital_Object) — the ResourceNode is the set, the ResourceFileNode is each file, reached by has_file (connections 1.6.30) with role and relative path on the edge. With one file the node is implicit (url and checksum stay on the ResourceNode, as today). ResourceNode.PACKAGINGS += file_set (a few files that call each other: obj → mtl → textures, gltf → bin, shp and companions) and datablock (one object inside a file, a blend:// locator). Representations of the same thing are sibling ResourceNodes tied by dtc_derived_from and chosen by tier and packaging. ADDITIVE: nothing narrowed, no graph changes. v1.6.16 (MICRO le annotazioni ATON sull'asset, 2026-10-15, decided by E.D.): AnnotationRegionNode gains geometry_kind 'volume' — an annotation that encloses a part of a 3D model (ATON / Hathor convex hulls and spheres) and is the proxy of no unit. The region carries no vertices: it reaches a SemanticShapeNode (convexshapes, spheres) with has_semantic_shape and the model with is_on_resource. geometry.aton.import_aton_scene makes one for every semantic id no EM node is named after (a stratigraphic unit only with an explicit create_type); api.promote_region_to_proxy turns it into the proxy of a unit later. RDF: P2_has_type 'volume', no selector, no WKT; the shape travels as itself. Additive. v1.6.15 (MICRO la geometria per origine, 2026-10-11, decided by E.D. 2026-09-30): AnnotationRegionNode's point / line / polyline keep their vertices IN THE NODE, data.coords [[x, y, z], ...] (scene-local, glTF Y-up, metres) with crs and, for a line or a polyline, length and unit — no .glb and no SemanticShape for a reading. New block coords (inline_max_vertices 500: above it the vertices go to a .glb resource via has_linked_resource, with a warning). RDF: geo:hasGeometry -> <region>/geometry geo:asWKT (POINT Z / LINESTRING Z, GeoSPARQL). The readings/<id>.glb of 2026-10-06 are migrated on opening. v1.6.14 (MICRO la cattura in RDF, 2026-09-30): DTCAcquisitionNode.mapping.by_kind — its D12 is the class of a retrieval; a capture takes the class its kind declares in em_visual_rules 1.6.24 (D2 / D11 / E65). Mapping text only, no field changed. v1.6.13 (MICRO i generi delle US, 2026-09-30, decided by E.D. the same day): stratigraphic_kind gains 'coating' — the USR (rivestimento) and its English translation USS (surface): plaster, floors, revetments — with `labels`, `codes` and `default_code` per kind; new node element `source_code` (data.source_code) keeps the code a unit came in with when it is not its kind's default, so the way back to pyArchInit gives the same code. A legacy node_type 'USR' / 'USS' opens as US + coating. v1.6.12 (MICRO la cattura nel DTC e le murature, 2026-09-30): StratigraphicUnit (US) gains the node element `stratigraphic_kind` (em.json data.stratigraphic_kind; today one value, 'masonry'): a USM is a US + masonry, and the legacy node_type 'USM' — never a type of this datamodel — opens as that. DTCAcquisitionNode's description names the two families of the acquisition axis (em_visual_rules 1.6.22: capture / retrieval). v1.6.11 (MICRO la misura in RDF, 2026-10-07): AnnotationRegionNode.properties says how the fields left unprojected by 1.6.10 now travel — the quote of a passage as oa:TextQuoteSelector, the length of a line/polyline as crm:E54_Dimension (P90 value, P91 QUDT unit, em:crs), vertex_count as em:vertexCount. CRMem (em.ttl) 1.6.5 -> 1.6.6. Mapping text only, no field changed. v1.6.10 (MICRO la geometria della lettura, 2026-10-06, decided by E.D. on 2026-09-29): AnnotationRegionNode becomes the node of THE PLACE A READING LOOKED AT, with a new field geometry_kind: region2d (default, every older region), passage (start, end, text), point, line, polyline. The three 3D kinds keep their coordinates in a .glb (glTF POINTS / LINES / LINE_STRIP) linked with has_semantic_shape exactly like a proxy's payload, never in the em.json; the node keeps vertex_count and, for line/polyline, length + unit + crs (api.measure). See the entry's geometry_kinds and glb_payload. Paired with connections 1.6.27 (is_on_resource.target += the representation models). Additive: a region without geometry_kind reads as region2d. v1.6.9 (MICRO la definizione dell'unita', 2026-10-20, decided by E.D. on 2026-09-27): StratigraphicNode.properties gains `definition`, the DEFINIZIONE of the US sheet, as an element of the node like name and description and NOT a qualia. Value = a controlled-vocabulary concept {concept, label}; em.json carries it as data.definition (CRDT field 'data.definition', no change to the frozen em.json v1 node shape); inherited by every stratigraphic subtype. The RDF projection is declared in the entry itself (`rdf`): crm:P2_has_type -> crm:E55_Type when a concept URI is present, nothing when only a label is (`label_only: null`). CRMem 1.6.4 -> 1.6.5 for the companion em:hasDefinition (subproperty of crm:P2_has_type, declared, not emitted by default). Additive only. v1.6.7 (CRMem WIRING, 2026-09-24): rimosso il campo legacy `cidoc_s3d` da tutte le mapping. Non era letto da nessuna parte del codice e portava quattro nomi di classe senza namespace, mai dichiarati e mai emessi: EpochNode = StratigraphicTimeframe; ActivityNodeGroup = StratigraphicActivity; ParadataNodeGroup = ParadataCollection; ResourceNode = ExternalResourceReference. Il prefisso CIDOC-S3D non esiste piu' in nessuno dei due datamodel. v1.6.6 (CIDOC REPAIR, 2026-09-21): classes that pointed at IRIs nobody declares. Checked by parsing the official releases, not from memory. crm:E78_Collection is gone from CIDOC CRM 7.1.3 — renamed E78_Curated_Holding — and E.D. decided NOT to follow the rename, because E78_Curated_Holding is a subclass of E24 Physical Human-Made Thing and a group of nodes is not a physical thing. The three classes that carried it therefore split, each to the class it actually is: GroupNode and RepresentationModelNodeGroup to crm:E73_Information_Object (a conceptual set, and an E90 Symbolic Object, which is what the P106i membership edge needs at both ends), ParadataNodeGroup to crm:E89_Propositional_Object — which is what a gathered body of reasoning IS and what the range of crm:P129i_is_subject_of demands, that being the predicate has_paradata_nodegroup takes in connections 1.6.17 the same day; it stays an E90 through em:NodeGroup, so the membership edge does not break. SemanticShapeNode leaves crmgeo:SP5_Geometric_Place_Expression for crm:E73_Information_Object, PROVVISORIAMENTE: SP5 is not declared at the crmgeo namespace this datamodel emits, crmgeo:SP6_Declarative_Place is the better candidate, and the decision is rinviata da E.D. — E73 commits to nothing meanwhile. crm:P131_is_identified_by, deprecated in CRM 7.x together with E82 Actor Appellation, becomes crm:P1_is_identified_by on AuthorNode (name, surname) and AuthorAINode (name). «CRMs3D» is renamed «CRMem», in components and in referenced_ontology_versions alike: the companion ontology is em.ttl and its namespace is em:, so the old name pointed at nothing anyone could look up. CRMsci moves 3.1 -> 3.2 (latest release). The eight em: terms this file and the connections datamodel cite but em.ttl never defined are now declared there (em:FunctionalUnit, em:GCPSet, em:Narrative, em:NeutralSU, em:RegistrationTransform, em:RepresentationModelNodeGroup, em:hasSubEpoch, em:validatedBy), with domain, range and superclass read off these datamodels and nothing invented. NOT TOUCHED: the `alternative` and legacy `cidoc_s3d` prose fields, which still discuss E78 as an option — prose, not a projection, and rewording them is modelling rather than repair. v1.6.5 (EM16-RMNG, 2026-09-10): adds RepresentationModelNodeGroup, the RM container as a first-class group of the graph — sixth subtype of GroupNode, keeping the parent's E78 Collection because a container IS a curatorial set. Paired with connections datamodel 1.6.14, which adds the is_in_representation_model_group membership edge and widens has_representation_model.target to accept the group. Additive only: no existing entry changed. s3Dgraphy nodes datamodel including node types with CIDOC-CRM mappings. v1.6.4 adds the ADDITIVE georeferencing_nodes section (GCPSetNode = em:GCPSet, RegistrationTransformNode = em:RegistrationTransform, both subclasses of crm:E73_Information_Object with their own extension URIs so the RDF projection stays bijective): the CONTROL and the SOLUTION that place a produced model in the world, introduced with the photogrammetry processing connector. The two modes of that connector are the SHAPE of the graph (a transform with a CRS that has_gcp_set points at = absolute; a transform with crs=null and no control set = a site-local frame; no transform at all = nobody placed it), never a flag. No existing family changed. v1.6.3 re-reads SemanticShapeNode as a PAYLOAD carrier: the proxy of a unit is now a PropertyNode of qualia type 'geometry' that points at the shape (has_semantic_shape), so the proxy inherits the paradata chain it never had. Breaking for consumers that read the proxy as a standalone SemanticShape. v1.6.2 adds AnnotationRegionNode (em:AnnotationRegion, subclass of crm:E36_Visual_Item): the geometry of a 2D annotation in NORMALISED image space, distinct from SemanticShapeNode (3D scene geometry, crmgeo:SP5) - the semantics of the 2D annotator, defined before any canvas exists. v1.6.0 inaugurates a systematic CIDOC-CRM mapping revision: complete audit of all node types against CIDOC-CRM, CRMarchaeo, CRMinf, CRMdig, CRMsci, CRMgeo; replacement of legacy 'cidoc_s3d' pseudo-class names (invented strings without IRI or superclass declaration) with formal em:/s3d: IRIs declared as proper subclasses of CRM classes; introduction of CRMinf as primary (not alternative) for the paradata chain (ParadataNode, PropertyNode interpretive case, ExtractorNode, CombinerNode); introduction of PROV-O for AuthorNode to cover both human and AI agents; alignment with the Heritage Digital Twin Ontology (HDT-O) for containment / granularity properties; LocationNodeGroup (v1.5.3) adopted as the reference pattern (CIDOC-native composition via P2_has_type → E55 Type instances, with explicit extension_status and rationale). Companion deliverables: em.ttl (formal EM extension ontology, dereferenceable via w3id.org/em/) and hdto_extension.ttl (HDT-O granularity properties: contains_HDT, contains_SU, isPrimary). v1.5.4 added RSF (Reused Special Find — spolia) as a stratigraphic subtype, octagon with red border, family=real, is_series=false. Originating DP: DP-26 (spolia project, last DP before the EM 1.5 cut). v1.5.3 added LocationNodeGroup (E53 Place + E55 Type) for spatial / locational membership orthogonal to ActivityNodeGroup (intention) and EpochNode (time). v1.5.2 added family + is_series classification metadata on stratigraphic subtypes.",
   "components": [
     "CIDOC-CRM",
     "CRMarchaeo",
@@ -48,7 +48,7 @@
       "source": "https://www.w3.org/TR/prov-o/"
     },
     "CRMem": {
-      "version": "1.6.14",
+      "version": "1.6.15",
       "source": "internal em.ttl / hdto_extension.ttl companion ontologies"
     }
   },
@@ -1036,7 +1036,7 @@
       "abbreviation": "GEO",
       "label": "Geo Position",
       "description": "Class to represent a GeoPosition node in the graph. Attributes: type (str): Node type, set to 'geo_position'. data (dict): Data related to geographic position.",
-      "node_usage": "ONE PER GRAPH, not per epoch: georeferencing is a property of the GRAPH (like its name, author, licence, HR id — the graph-level metadata), so Graph.__init__ auto-creates a single node with id 'geo_<graph_id>' and the em.json importer drops that synthetic one when the document carries its own. The SHIFT IS THE ANCHOR, NOT THE POSITION: shift_x/y/z are the origin of the scene-local system expressed in the CRS named by epsg — the point that is (0,0,0) in the scene — and may legitimately sit OUTSIDE the geometry (a round grid vertex hundreds of metres from the monument). It is therefore NOT where a map marker belongs: the marker goes on the CENTROID of the geometry (api.georeference_scene). 'rotation' is the scene azimuth in degrees, clockwise from geographic north, 0 = north up (the default and the normal case). The scene-local → geo transform is: rotate by rotation, add the shift, reproject epsg → 4326 (api.reproject). Graph-side twin of EMTools' scene.em_georef (georef_manager), which propagates the same values to BlenderGIS and 3DSC.",
+      "node_usage": "ONE PER GRAPH, not per epoch: georeferencing is a property of the GRAPH (like its name, author, licence, HR id — the graph-level metadata), so Graph.__init__ auto-creates a single node with id 'geo_<graph_id>' and the em.json importer drops that synthetic one when the document carries its own. The SHIFT IS THE ANCHOR, NOT THE POSITION: shift_x/y/z are the origin of the scene-local system expressed in the CRS named by epsg — the point that is (0,0,0) in the scene — and may legitimately sit OUTSIDE the geometry (a round grid vertex hundreds of metres from the monument). It is therefore NOT where a map marker belongs: the marker goes on the CENTROID of the geometry (api.georeference_scene). 'rotation' is the scene azimuth in degrees, clockwise from the GRID north of the CRS epsg (D2, decided by E.D. 4 Oct 2026: not the geographic north — between the two lies the meridian convergence, which one graph never applies and two graphs meet only as their relative convergence), 0 = north up (the default and the normal case); data.rotation_reference = 'grid' says it in the data. The scene-local → geo transform is: rotate by rotation, add the shift, reproject epsg → 4326 (api.reproject). Graph-side twin of EMTools' scene.em_georef (georef_manager), which propagates the same values to BlenderGIS and 3DSC.",
       "s3Dgraphy_file": "geo_position_node.py",
       "mapping": {
         "cidoc": "E53 Place",
@@ -1057,7 +1057,8 @@
         "shift_x": "Q9_is_expressed_in_terms_of",
         "shift_y": "Q9_is_expressed_in_terms_of",
         "shift_z": "Q9_is_expressed_in_terms_of",
-        "rotation": "Q9_is_expressed_in_terms_of"
+        "rotation": "Q9_is_expressed_in_terms_of",
+        "rotation_reference": {"note": "1.6.25 (D2, decided by E.D. 4 Oct 2026): the north 'rotation' is measured from — always 'grid' (the grid north of the CRS epsg), written by GeoPositionNode and set on load when a document does not carry it (it is the definition, not a guess). Not projected to RDF: the anchor's frame is the CRS itself."}
       }
     },
     "ResourceNode": {
@@ -1098,7 +1099,16 @@
         "lang": {
           "rdf": "dcterms:language",
           "note": "1.6.21 (dev27, decided by E.D. 2026-10-01, «il testo, la risorsa e la selezione»): on a RESOURCE, data.lang is the language of the CONTENT of the file — what it is made of — not the language of the resource's own description: a Latin PDF does not make its Italian description Latin. One BCP 47 tag, or a sorted list for more («latino e italiano a fronte» = [\"it\", \"la\"]), written by s3dgraphy.language.set_content_languages. It does NOT enter the cascade of the language of the texts (language.node_language skips resources and their files), it is not written at birth, and it leaves as one dcterms:language per tag instead of em:originalLanguage. The DocumentNode is the WORK, with no text in its fields; the resources are its manifestations, the text is in the file; the ExtractorNode is the selection, with the original words of the passage in its description and its own data.lang."
-        }
+        },
+        "lod_level": {"rdf": "em:lodLevel", "pattern": "^lod(0|[1-9][0-9]*)$", "note": "1.6.25 (D1, decided by E.D. 4 Oct 2026, TASSONOMIA-TIER-3D §2a): the LEVEL of a version of an asset, an ordinal INSIDE ONE derivation chain. The master is tier = master and has no level; lod0 is the first version derived from it that one can work on (textured with the Demetrescu-D'Annibale formula: 1.26 mm per texel side, 4096² atlases, UV ratio 0.6 — Demetrescu et al. 2026, Remote Sensing 18, 203, §2 and §4.7); lod1…lodN count the lod_generation steps from LOD0 (as 3DSC's LOD generator does), a version that only reduces its textures included. COMPUTED from the chain (dtc_derived_from + lod_generation, resources.versions.lod_level_of), never stored in the graph: WRITTEN only when the graph leaves (em.json, manifest, record, RDF) and at load computed again and compared, like a checksum (check_lod_levels): a difference is a line in the Log. Why still «measures, not an enumeration of levels»: the etiquette orders one chain and means nothing outside it; the measures compare chains. Engines' automatic LOD (Nanite) is one more way to show a version and does not replace the chain."},
+        "use": {"rdf": "em:use", "cardinality": "list", "values": {"analysis": "Study and measure on the model: digital autopsy of the units, survey, sections, scientific annotation.", "realtime": "Interactive exploration in an engine (Unreal, Unity, Godot, EMviq), desktop and HMD, open world.", "web": "Viewing in the browser (ATON, Heriverse, Voyager), streamed too.", "mobile_ar": "Augmented reality and mobile devices.", "print": "3D printing, physical replica.", "render": "Non-interactive products: plates, sections, reconstructive views, CGI video.", "preview": "Light preview for catalogues and records."}, "labels": {"analysis": "Analysis", "realtime": "Real time", "web": "Web", "mobile_ar": "Mobile / AR", "print": "Print", "render": "Render", "preview": "Preview"}, "_note": "1.6.25 (D1, TASSONOMIA-TIER-3D §2b): what a version is FOR, a LIST (one version can serve the browser and the engine — unlike Voyager, which gives one usage per derivative). Correspondences, from the taxonomy's table: analysis — Voyager none (Editorial3D/Highest undocumented), 3D Tiles none; realtime — Voyager usage App3D; web — Voyager usage Web3D with quality Low/Medium/High, 3D Tiles: the tileset is the usual container and the level is chosen by geometricError; mobile_ar — Voyager quality AR and usage iOSApp3D; print — Voyager usage Print3D; render — Voyager usage Image2D (the correspondence is ours, not Voyager's); preview — Voyager quality Thumb. 'archive' is left out: keeping is the master's reason to be (tier = master). The older single 'purpose' of a lod_generation step is read as a one-item list when it is one of these."},
+        "tris_per_m2": {"rdf": "em:trisPerM2", "note": "1.6.25 (D1): a measure of a version, computed by EMtools when the version is born. Triangles per square metre of surface: a MEASURE, with no target (Demetrescu et al. 2026 record 955–5403 on Amba Aradam)."},
+        "texel_density_dd": {"rdf": "em:texelDensityDD", "note": "1.6.25 (D1): a measure of a version, computed by EMtools when the version is born. The texel SIDE in mm, in the form of the Demetrescu-D'Annibale formula (reference 1.26 mm; surface / (atlases × side² × UV ratio), square root)."},
+        "texture_count": {"rdf": "em:textureCount", "note": "1.6.25 (D1): a measure of a version, computed by EMtools when the version is born. How many texture atlases."},
+        "texture_side_px": {"rdf": "em:textureSidePx", "note": "1.6.25 (D1): a measure of a version, computed by EMtools when the version is born. The side of an atlas in pixels (4096 in the reference)."},
+        "uv_ratio": {"rdf": "em:uvRatio", "note": "1.6.25 (D1): a measure of a version, computed by EMtools when the version is born. The share of the atlas the UV islands fill (0.6 in the reference)."},
+        "reduction_from_lod0": {"rdf": "em:reductionFromLod0", "note": "1.6.25 (D1): a measure of a version, computed by EMtools when the version is born. The reduction from LOD0 (triangles of this version / triangles of LOD0) — 3DSC's «magnitude»."},
+        "geometric_error_m": {"rdf": "em:geometricErrorM", "note": "1.6.25 (D1): a measure of a version, computed by EMtools when the version is born. For a 3D Tiles tileset only: its geometricError, in metres."}
       },
       "resource_types": {
         "3d_model": [

{s3dgraphy-1.6.0.dev33 → s3dgraphy-1.6.0.dev35}/src/s3dgraphy/__init__.py

@@ -1,4 +1,4 @@
-__version__ = "1.6.0.dev33"
+__version__ = "1.6.0.dev35"
 __datamodel_version__ = "1.5.5"  # s3Dgraphy connections datamodel version
 
 # s3Dgraphy/__init__.py

{s3dgraphy-1.6.0.dev33 → s3dgraphy-1.6.0.dev35}/src/s3dgraphy/api.py

@@ -24,7 +24,7 @@ import math
 import re
 import tempfile
 from pathlib import Path
-from typing import Any, Dict, List, Optional, Tuple
+from typing import Any, Callable, Dict, List, Optional, Sequence, Tuple
 
 # Type-only alias; avoid importing submodules at module load (keeps this import
 # cheap and cycle-free). Real classes are imported lazily inside the ops.
@@ -2704,6 +2704,48 @@ def pick_representation(graph: Graph, res_id: str, can_open) -> Dict[str, Any]:
     return _pick(graph, res_id, can_open)
 
 
+# ── an asset and its versions (E.D. 30 Sep / 3 Oct 2026) ──────────────────────
+# The asset is the master resource; each version (LOD1, LOD2…) is a child made
+# by a `lod_generation` step, with its level and purpose in the step's
+# parameters. The semantic link stays on the asset and the versions inherit it.
+# See :mod:`s3dgraphy.resources.versions`.
+def add_version(graph: Graph, master_id: str, *, level: Optional[str] = None,
+                purpose: str = "", **kwargs) -> Dict[str, Any]:
+    """A version of the asset ``master_id``: a child resource
+    ``dtc_derived_from`` it through a ``lod_generation`` step. ``level`` is its
+    name (default: the computed level, ``lod0`` from the master, ``lodK+1``
+    from a ``lodK``); ``use`` a list of :data:`resources.versions.USES`;
+    ``measures`` the numbers of :data:`resources.versions.LOD_MEASURES` (D1).
+    Idempotent per (asset, level); other bytes at a level are refused (revise
+    the version instead). Returns ``{version_id, process_id, created, asset_id,
+    level, lod_level, use, measures, purpose, warnings}``."""
+    from .resources.versions import add_version as _add
+    before = _ids(graph)
+    out = _add(graph, master_id, level=level, purpose=purpose, **kwargs)
+    _born(graph, before)
+    return out
+
+
+def versions_of(graph: Graph, res_id: str) -> List[Dict[str, Any]]:
+    """The asset of ``res_id`` and its versions, master first then by level,
+    each the CURRENT revision: ``[{id, level, purpose, master, checksum, …}]``."""
+    from .resources.versions import versions_of as _versions
+    return _versions(graph, res_id)
+
+
+def asset_of(graph: Graph, res_id: str) -> str:
+    """The asset (master) ``res_id`` is a version of; itself if it is none."""
+    from .resources.versions import asset_of as _asset
+    return _asset(graph, res_id)
+
+
+def inherited_links(graph: Graph, res_id: str) -> Dict[str, Any]:
+    """What hats the asset of ``res_id`` (RM/proxy facets and their epochs and
+    units): the semantic link a version inherits, never copied onto it."""
+    from .resources.versions import inherited_links as _links
+    return _links(graph, res_id)
+
+
 # ── the 3D Tiles Archive (.3tz), recognised and read, never written here ──────
 # The writers are 3DSC and EMStudio (E.D. 2026-09-30); the canonical form and
 # the content digest belong to dtcstamp. See :mod:`s3dgraphy.resources.tiles3tz`.
@@ -2728,6 +2770,41 @@ def is_canonical_3tz(path: str) -> Dict[str, Any]:
     return _canon(path)
 
 
+# ── R1 · one resolver for the files, and their state (E.D., 4 Oct 2026) ──────
+def resolve_files(graph: Graph, *, project_root: Optional[str] = None,
+                  base_dirs: Sequence[str] = (), cache_dirs: Sequence[str] = (),
+                  on_node: Optional[Callable[[str], bool]] = None,
+                  hasher: Optional[Callable[[str], str]] = None) -> List[Dict[str, Any]]:
+    """The STATE of every resource of ``graph`` — ``on_disk``, ``on_node``,
+    ``both``, ``reference_only``, ``missing``, ``empty_copy`` — trying cache →
+    known paths (the EM standard tree of ``project_root`` first) → node
+    (``on_node(hex)``) → reference. The one resolver every tool calls. See
+    :mod:`s3dgraphy.resources.locate`."""
+    from .resources.locate import resolve_graph
+    return resolve_graph(graph, project_root=project_root, base_dirs=base_dirs,
+                         cache_dirs=cache_dirs, on_node=on_node, hasher=hasher)
+
+
+def resolve_file(entry: Dict[str, Any], **kwargs) -> Dict[str, Any]:
+    """:func:`resolve_files` for ONE ``{id, locator, checksum}``."""
+    from .resources.locate import resolve
+    return resolve(entry, **kwargs)
+
+
+# ── C1 · the standard tree of an EM project (E.D., 4 Oct 2026) ─────────────────
+def create_em_project(parent: str, name: str, **kwargs) -> Dict[str, Any]:
+    """«New EM project…»: EM/ (DosCo/, proxies/), RB/, SB/, RM/, README.md,
+    LICENCE.md under ``parent/name``. See :mod:`s3dgraphy.project_tree`."""
+    from .project_tree import create_project
+    return create_project(parent, name, **kwargs)
+
+
+def em_project_reorder_plan(root: str) -> List[Dict[str, str]]:
+    """«Reorder by the EM standard…»: the preview, never applied here."""
+    from .project_tree import reorder_plan
+    return reorder_plan(root)
+
+
 # ── resource layer (R0: stable-ID resolver seam) ──────────────────────────────
 # Resources are LinkNodes (E73). Their stable, storage-agnostic ID is the node
 # UUID; the ``url`` is the *current locator*, not the identity. A pluggable