s3dgraphy 1.6.0.dev29__tar.gz → 1.6.0.dev30__tar.gz

{s3dgraphy-1.6.0.dev29/src/s3dgraphy.egg-info → s3dgraphy-1.6.0.dev30}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: s3dgraphy
-Version: 1.6.0.dev29
+Version: 1.6.0.dev30
 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>
@@ -35,7 +35,7 @@ Requires-Dist: pandas>=2.0.0
 Requires-Dist: lxml>=4.9.0
 Requires-Dist: openpyxl>=3.0.0
 Requires-Dist: networkx>=3.0
-Requires-Dist: dtcstamp>=0.1.3
+Requires-Dist: dtcstamp>=0.1.4
 Provides-Extra: rdf
 Requires-Dist: rdflib>=7.0; extra == "rdf"
 Provides-Extra: rdf-embedded

{s3dgraphy-1.6.0.dev29 → s3dgraphy-1.6.0.dev30}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "s3dgraphy"
-version = "1.6.0.dev29"
+version = "1.6.0.dev30"
 description = "3D Stratigraphic Graph Management Library for archaeological and heritage applications"
 readme = "README.md"
 requires-python = ">=3.9"
@@ -56,7 +56,7 @@ dependencies = [
     # the four above. It has zero dependencies of its own and is one module, so
     # it can also simply be copied; s3dgraphy depends on it rather than
     # vendoring it, because two copies of a format rule drift.
-    "dtcstamp>=0.1.3",  # 0.1.1 lacks stamp_description: import s3dgraphy.stamp fails (MICRO-DTCSTAMP-012)
+    "dtcstamp>=0.1.4",  # 0.1.1 lacks stamp_description: import s3dgraphy.stamp fails (MICRO-DTCSTAMP-012)
 ]
 
 [project.urls]
@@ -216,6 +216,9 @@ testpaths = ["tests"]
 python_files = ["test_*.py"]
 python_classes = ["Test*"]
 python_functions = ["test_*"]
+markers = [
+    "slow: reads real data when it is on this machine (skipped otherwise)",
+]
 
 [tool.mypy]
 python_version = "3.8"

{s3dgraphy-1.6.0.dev29 → s3dgraphy-1.6.0.dev30}/src/s3dgraphy/JSON_config/datamodel_translations.json

@@ -615,7 +615,7 @@
   },
   "GCPSetNode": {
    "description": {
-    "en": "The set of ground control points a registration was (or will be) solved from. data.points is a list of {id, world:[x,y,z], observations:[{image, pixel:[x,y]}], uncertainty?}; data.crs names the frame the world coordinates are in (null = a site-local grid, which is a different statement from absent). Minimum 3 observed non-collinear points for a similarity to be determined — reported by `solvable`, enforced by the runner, never at construction (a set being assembled in the field is legitimately incomplete).",
+    "en": "The set of ground control points a registration was (or will be) solved from. data.points is a list of {id, world:[x,y,z], observations:[{image, pixel:[x,y]}], uncertainty?}; data.crs names the frame the world coordinates are in (null = a site-local grid, which is a different statement from absent). Minimum 3 observed non-collinear points for a similarity to be determined — reported by `solvable`, enforced by the runner, never at construction (a set being assembled in the field is legitimately incomplete). 1.6.24 (dev30, decided by E.D. 2 Oct 2026, D7): data.control says WHAT the points are — ground_control_points (default, not written) or camera_positions: the GPS positions of the cameras themselves, each point {id, world, image, uncertainty?} with no pixel observation (the camera is where the photograph was taken from, not something seen in it), solvable with three; data.accuracy_m is the accuracy the project records for the cameras. A chunk referenced only by its cameras' GPS is placed absolute with such a set, and validate warns «georeferenced only by camera GPS»: absolute without the control said would claim more than the data.",
     "validated_it": false,
     "validated_el": false,
     "validated_he": false,
@@ -8091,5 +8091,112 @@
     "fr": "maçonnée"
    }
   }
+ },
+ "packagings": {
+  "archive": {
+   "label": {
+    "en": "Archive",
+    "validated_it": false,
+    "validated_el": false,
+    "validated_he": false,
+    "validated_es": false,
+    "validated_pl": false,
+    "validated_ro": false,
+    "validated_fr": false,
+    "validated_de": false,
+    "it": "Archivio",
+    "el": "Αρχειοθήκη",
+    "he": "ארכיון",
+    "es": "Archivo comprimido",
+    "pl": "Archiwum",
+    "ro": "Arhivă",
+    "fr": "Archive",
+    "de": "Archiv"
+   }
+  },
+  "datablock": {
+   "label": {
+    "en": "Blender object",
+    "validated_it": false,
+    "validated_el": false,
+    "validated_he": false,
+    "validated_es": false,
+    "validated_pl": false,
+    "validated_ro": false,
+    "validated_fr": false,
+    "validated_de": false,
+    "it": "Oggetto Blender",
+    "el": "Αντικείμενο Blender",
+    "he": "אובייקט Blender",
+    "es": "Objeto de Blender",
+    "pl": "Obiekt Blendera",
+    "ro": "Obiect Blender",
+    "fr": "Objet Blender",
+    "de": "Blender-Objekt"
+   }
+  },
+  "directory": {
+   "label": {
+    "en": "Folder",
+    "validated_it": false,
+    "validated_el": false,
+    "validated_he": false,
+    "validated_es": false,
+    "validated_pl": false,
+    "validated_ro": false,
+    "validated_fr": false,
+    "validated_de": false,
+    "it": "Cartella",
+    "el": "Φάκελος",
+    "he": "תיקייה",
+    "es": "Carpeta",
+    "pl": "Folder",
+    "ro": "Dosar",
+    "fr": "Dossier",
+    "de": "Ordner"
+   }
+  },
+  "file": {
+   "label": {
+    "en": "File",
+    "validated_it": false,
+    "validated_el": false,
+    "validated_he": false,
+    "validated_es": false,
+    "validated_pl": false,
+    "validated_ro": false,
+    "validated_fr": false,
+    "validated_de": false,
+    "it": "File",
+    "el": "Αρχείο",
+    "he": "קובץ",
+    "es": "Archivo",
+    "pl": "Plik",
+    "ro": "Fișier",
+    "fr": "Fichier",
+    "de": "Datei"
+   }
+  },
+  "file_set": {
+   "label": {
+    "en": "File set",
+    "validated_it": false,
+    "validated_el": false,
+    "validated_he": false,
+    "validated_es": false,
+    "validated_pl": false,
+    "validated_ro": false,
+    "validated_fr": false,
+    "validated_de": false,
+    "it": "Insieme di file",
+    "el": "Σύνολο αρχείων",
+    "he": "ערכת קבצים",
+    "es": "Conjunto de archivos",
+    "pl": "Zestaw plików",
+    "ro": "Set de fișiere",
+    "fr": "Ensemble de fichiers",
+    "de": "Dateigruppe"
+   }
+  }
  }
 }

{s3dgraphy-1.6.0.dev29 → s3dgraphy-1.6.0.dev30}/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.13" ;
-    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.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.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:imports <http://www.cidoc-crm.org/cidoc-crm/> ,
                 <http://www.cidoc-crm.org/extensions/crminf/> ,
                 <http://www.cidoc-crm.org/extensions/crmarchaeo/> ,
@@ -980,5 +980,21 @@ em:software
     rdfs:comment "The software of a DTC step, as ONE rdf:JSON list of {name, version, commit?}: a real chain names two (the tool and the library), and the commit says which build. Maps to: node_datamodel DTCProcessNode.properties.software."@en .
 
 # ============================================================================
-# End of em.ttl v1.6.13
+# 18. Where a retrieval came from, and the digest of a set (v1.6.14, dev30,
+#     decided by E.D. 2026-10-02)
+# ============================================================================
+
+em:retrievedFrom
+    a owl:DatatypeProperty ;
+    rdfs:label "retrieved from"@en ;
+    rdfs:comment "Where a retrieved digital object came from: the DOI (as https://doi.org/…) or the URL of a Download — the stamp format's how.acquisition.retrieved_from. A literal, an xsd:anyURI when it is a URL: an origin is an address the act was made from, not a parent with an identity, so it is not a prov:used. Optional: an event that does not say it is warned about, never refused. Maps to: node_datamodel DTCAcquisitionNode.properties.retrieved_from."@en .
+
+em:membersDigest
+    a owl:DatatypeProperty ;
+    rdfs:label "members digest"@en ;
+    rdfs:range xsd:string ;
+    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
 # ============================================================================

{s3dgraphy-1.6.0.dev29 → s3dgraphy-1.6.0.dev30}/src/s3dgraphy/JSON_config/em_visual_rules.json

@@ -1,6 +1,6 @@
 {
   "formal_language": "EM",
-  "version": "1.6.30",
+  "version": "1.6.31",
   "_note_material_vs_qualia_color": [
     "DUE COSE DIVERSE CHE SI CHIAMANO ENTRAMBE color. Non confonderle: e gia successo.",
     "1) QUI, in node_styles.<tipo>.style.material.rgba_color — il COLORE DEL MATERIALE BLENDER del proxy 3D, in float LINEARI. UNA sola chiave: `rgba_color`. Fino a S8 il file ne usava due (`color` sui 13 tipi stratigrafici, `rgba_color` sugli altri) e get_material_color() ne leggeva una sola, restituendo None per 21 tipi su 38; ora sono unificate e la vecchia `color` e letta solo come tolleranza verso file scritti prima. Un tipo che non diventa mai una mesh NON ha material affatto (i contenitori di gruppo, e da S7 i dieci nodi che rendono per icona): per loro get_material_color() torna None, ed e corretto.",
@@ -9,7 +9,8 @@
     "In breve: qui si decide di che colore DISEGNARE una US; li si registra di che colore ERA."
   ],
   "_changelog": {
-    "1.6.30": "AN IMAGE SET AND TEXTURING (dev29, 2 Oct 2026, proposed from the measurements on San Pietro and confirmed by E.D. the same day). dtc_kinds.output += image_set (a set of photographs kept and handed on as ONE product, its images the members of one resource), glyph 09_photos reused; dtc_kinds.process += texturing (a model given its colour from images: projection onto a mesh or baking into an atlas, one kind until decided otherwise), glyph 03_mesh reused. Labels in the nine languages (not validated); 2d_glyphs regenerated. Like every process kind texturing declares no mapping.",
+    "1.6.31": "THE CHOICES OF DEV29, CONFIRMED (E.D., 2 Oct 2026, on the dev29 report, D5). dtc_kinds.process.texturing is projection AND baking of the photographs onto the mesh, one act, one kind; the baking of levels of detail in Blender stays lod_generation, an act of its own. The «until E.D. says otherwise» of 1.6.30 is gone from the description. Text only: no kind, glyph or label changed.",
+    "1.6.30": "AN IMAGE SET AND TEXTURING (dev29, 2 Oct 2026, proposed from the measurements on San Pietro and confirmed by E.D. the same day). dtc_kinds.output += image_set (a set of photographs kept and handed on as ONE product, its images the members of one resource), glyph 09_photos reused; dtc_kinds.process += texturing (a model given its colour from images: projection onto a mesh and baking into an atlas, one kind — confirmed in 1.6.31), glyph 03_mesh reused. Labels in the nine languages (not validated); 2d_glyphs regenerated. Like every process kind texturing declares no mapping.",
     "1.6.29": "THE FOUR GESTURES OF WHOEVER EXPORTS (dev28, decision of E.D. 1 Oct 2026 on the dev27 report, part D). dtc_kinds.process += export (an object of a working project written as a file of its own), lod_generation (a level of detail baked from the master), tiling (a mesh divided into a 3D Tiles tree), packing (a tree packed into one archive, the .3tz). Until dev28 EM Tools and 3DSC wrote them format_conversion / decimation / transformation with the gesture in `technique`; those stamps stay true. NO NEW GLYPH: they reuse 17_format_conversion (export, packing), 15_decimation (lod_generation), 00_transformation (tiling) — a mark of their own is an act of EM iconography, left to E.D.; 2d_glyphs regenerated (dtc:<kind> entries). NO MAPPING, measured: no process kind declares one; a step is the crmdig:D7 of DTCProcessNode whatever its kind. Labels in the nine languages in datamodel_translations.json (dtc_kinds).",
     "1.6.28": "THE TRANSLATION NODE (MICRO le traduzioni, 29 Oct 2026, decision of E.D. 1 Oct 2026). node_styles.TRANSL for TranslationNode: the narrative's neutral grey and its glyph (src/2D/narrative.svg, SHARED, declared by 2d_file_vect — the way UL / USN / USNt share US.png), with a DASHED border so a translation does not read as a narrative. Choosing a mark of its own is an act of EM iconography and is left to E.D.; no file_3d, no material: a translation never becomes a mesh.",
     "1.6.27": "THE GLYPH OF THE FILE (MICRO-REVISIONE, 20 Oct 2026, decision of E.D. 30 Sep 2026: Claude draws it). node_styles.FILE.2d_file_vect: src/2D/link.svg -> src/2D/resource_file.svg, a sheet with a folded corner and the digest sign inside the 2017 DTC circle. WHERE, MEASURED: a resource takes its sign from node_styles.<KEY>.2d_file_vect (LINK -> src/2D/link.svg), a FILE, which EMStudio's icons.ts resolves (declaration, then src/2D/<node_type>.svg) and sync-datamodels.sh vendors from the top level of src/2D/. It is NOT a DTC glyph (dtc_kinds name the glyphs of DTC kinds, and a file is a node type, not a kind) and NOT a 2d_glyphs entry: LINK is not in 2d_render_glyph_types either, and joining that list would change how the label is laid out, which nobody asked. Still no .glb (as before). The dashed border and the LINK colour stay.",
@@ -4331,7 +4332,7 @@
       "texturing": {
         "label": "Texturing",
         "glyph": "03_mesh",
-        "description": "Giving a model its colour from images: projecting photographs onto a mesh, or baking its textures into an atlas (measured on San Pietro: the published LOD0 and the case-study LOD1 have the same geometry and differ only in the textures). Projection and baking stay one kind until E.D. says otherwise; which one it was goes in `technique`. Proposed in dev29, confirmed by E.D. on 2 Oct 2026. A crmdig:D7 Digital Machine Event like every process."
+        "description": "Giving a model its colour from images: projecting photographs onto a mesh, or baking its textures into an atlas (measured on San Pietro: the published LOD0 and the case-study LOD1 have the same geometry and differ only in the textures). Projection and baking of the photographs onto the mesh are ONE act of this kind (E.D., 2 Oct 2026); the baking of levels of detail in Blender is not texturing but lod_generation, an act of its own. Proposed in dev29, confirmed by E.D. on 2 Oct 2026. A crmdig:D7 Digital Machine Event like every process."
       },
       "transformation": {
         "label": "Transformation",

{s3dgraphy-1.6.0.dev29 → s3dgraphy-1.6.0.dev30}/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.23",
+ "s3Dgraphy_data_model_version": "1.6.24",
  "node_types": {
   "ActivityNodeGroup": {
    "parent": "GroupNode",

{s3dgraphy-1.6.0.dev29 → s3dgraphy-1.6.0.dev30}/src/s3dgraphy/JSON_config/s3Dgraphy_node_datamodel.json

@@ -1,6 +1,6 @@
 {
-  "s3Dgraphy_data_model_version": "1.6.23",
-  "description": "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.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.",
   "components": [
     "CIDOC-CRM",
     "CRMarchaeo",
@@ -48,7 +48,7 @@
       "source": "https://www.w3.org/TR/prov-o/"
     },
     "CRMem": {
-      "version": "1.6.13",
+      "version": "1.6.14",
       "source": "internal em.ttl / hdto_extension.ttl companion ontologies"
     }
   },
@@ -88,7 +88,7 @@
         "ai_assisted.fields": "em:aiAssistedField",
         "validated_by": "em:validatedBy",
         "validated_at": "em:validatedAt",
-        "lang": "em:originalLanguage",
+        "lang": {"rdf": "em:originalLanguage", "note": "1.6.24 (dev30, decided by E.D. 2 Oct 2026, U5): a language RECOGNISED by a tool and confirmed by a person with one gesture is written as data.lang ONLY — no ai_assisted, no record in the graph's register: recognising the language of a text is cleaning of the data, not provenance (s3dgraphy.language.confirm_recognised_language). It is the one explicit exception to the AI marker; every other field a tool proposes keeps it."},
         "created_auth": {
           "rdf": "em:createdVia",
           "note": "1.6.21 (dev27, decided by E.D. 2026-10-01, «l'accesso sul campo»): HOW the hand of a signature had entered, beside each signature — created_auth beside created_by, modified_auth beside modified_by, validated_auth beside validated_by: {mode, attested_by?}, mode 'orcid' (verified by ORCID) or 'node_password' (the iD and a password of a StratiGraph node, which attests the identity offline; attested_by = the node's name, required) or, since 1.6.22 (dev28), 'declared' (an iD typed in a tool's preferences, checked by nobody; no attested_by). Through a relay the mode is the relay's, read from the token (crdt.stamp_auth), never the client's declaration. Written by editorial.stamp_created / stamp_modified (auth=), ai_validation.verify (auth=) and the CRDT op's 'auth'; modified_auth follows the last hand and is removed when a new hand comes without one. In RDF: <node>/auth/<created|modified|validated>, reached by em:createdVia / em:modifiedVia / em:validatedVia, with em:authMode and em:attestedBy."
@@ -1079,10 +1079,11 @@
         "checksum": "em:checksum",
         "scope": "em:resourceScope",
         "residency": "em:residency",
-        "packaging": {"rdf": "em:packaging", "note": "1.6.23 (dev29): how the bytes are packed (file | file_set | directory | archive | datablock, the dtcstamp PACKAGINGS), DECLARED — never the effective_packaging fallback. Emitted only when recorded."},
+        "packaging": {"rdf": "em:packaging", "note": "1.6.23 (dev29): how the bytes are packed (file | file_set | directory | archive | datablock, the dtcstamp PACKAGINGS), DECLARED — never the effective_packaging fallback. Emitted only when recorded. 1.6.24 (dev30): the vocabulary with its labels lives here (values, labels; translations in datamodel_translations.json, section packagings), so an interface reads the name of a packaging from the datamodel instead of its own words.", "values": {"file": "One file: the resource is its bytes.", "file_set": "A few files that call each other (obj → mtl → textures, gltf → bin, shp and companions): the resource is the list of its members, stamped by the digest of that list.", "directory": "A folder: the resource is everything under it, members reached by has_file with their relative path.", "archive": "One file that packs others (zip, .3tz): the resource is the archive's bytes.", "datablock": "One object inside a file (a blend:// locator): comparable by a structural digest, not verifiable by downloading."}, "labels": {"file": "File", "file_set": "File set", "directory": "Folder", "archive": "Archive", "datablock": "Blender object"}},
         "tier": {"rdf": "em:tier", "note": "1.6.23 (dev29): master | distribution | …, declared; emitted only when recorded."},
         "digest_covers": {"rdf": "em:digestCovers", "note": "1.6.23 (dev29): what em:checksum covers — artifact (the bytes), payload, members (the canonical list of the members of a file_set, dtcstamp.members_digest). add_resource writes members for a file_set; a legacy members_digest equal to the checksum leaves as members."},
-        "content_digest": {"rdf": "em:contentDigest", "note": "1.6.23 (dev29): the digest of the CONTENT of a tree (a folder or its .3tz), dtcstamp.content_digest — the same for both forms."},
+        "members_digest": {"rdf": "em:membersDigest", "note": "1.6.24 (dev30, decided by E.D. 2 Oct 2026, D4): NOT A SECOND FIELD — the digest of a file_set is its checksum with digest_covers members (dtcstamp.members_digest of the list of members, A1 of dev29). In RDF it leaves ALSO as em:membersDigest, a predicate of its own, so a reader tells the digest of a set from the digest of a file without reading em:checksum and em:digestCovers together; those two stay, for compatibility. A TTL carrying only em:membersDigest comes back as checksum + digest_covers members."},
+        "content_digest": {"rdf": "em:contentDigest", "note": "1.6.23 (dev29): the digest of the CONTENT of a tree (a folder or its .3tz), dtcstamp.content_digest — the same for both forms. 1.6.24 (dev30, decided by E.D. 2 Oct 2026, D7): also the digest of the DATA of a master that lives inside another file — for a Metashape model (a datablock, psx://) the sha256 of its mesh.ply inside the project's model.zip, written by importer.metashape_project. It is COMPARED (has the master changed?), never verified by downloading, and so it is never the checksum, which is the digest of bytes one can fetch."},
         "addresses": {
           "rdf": "em:hasAddress",
           "note": "1.6.21 (dev27, decided by E.D. 2026-10-01, «più risorse per un documento»): the SAME bytes — the same digest — are ONE resource with several addresses (the same PDF on the disk, on MinIO, on Zenodo); different manifestations are sister resources. data.addresses = [{locator, residency?, checked_at?, ok?}], written only when there is a second address or a check; address 0 is data.url, which a consumer that knows only url keeps reading. ok true = reachable at checked_at, false = dead (a warning while a live one remains, never removed by a check), absent = never checked. Written by s3dgraphy.resources.addresses (add_address refuses a different digest, and a resource with no digest). In RDF every locator is an rdfs:seeAlso of the resource, and each address <resource>/address/<i> em:hasAddress, with em:locator, em:residency, em:checkedAt, em:reachable."
@@ -1715,7 +1716,8 @@
         "dtc_kind": "P2_has_type",
         "technique": {"rdf": "em:technique", "note": "1.6.23 (dev29): the free word of whoever did the gesture, beside the controlled dtc_kind. Leaves for RDF and comes back (it was lost by the round trip, measured on San Pietro)."},
         "parameters": {"rdf": "em:parameters", "note": "1.6.23 (dev29): how the technique was applied, a dict; ONE rdf:JSON literal, because the stamp format owns its shape."},
-        "software": {"rdf": "em:software", "note": "1.6.23 (dev29): the list of software of the step, each {name, version, commit?}; ONE rdf:JSON literal. data.tool is read back from its first entry, as declare_derivation writes it."}
+        "software": {"rdf": "em:software", "note": "1.6.23 (dev29): the list of software of the step, each {name, version, commit?}; ONE rdf:JSON literal. data.tool is read back from its first entry, as declare_derivation writes it."},
+        "retrieved_from": {"rdf": "em:retrievedFrom", "note": "1.6.24 (dev30, decided by E.D. 2 Oct 2026, D1): WHERE A RETRIEVED OBJECT CAME FROM — the DOI (as https://doi.org/…) or the URL a Download was made from; the stamp's how.acquisition.retrieved_from. Not from[]: from[] names parents with an identity (a digest), and an origin has none. On the node it is one of the event's facts, data.retrieved_from (bucket_acquisition's metadata) or data.acquisition.retrieved_from (an absorbed stamp): dtc.ingest.acquisition_origin reads both. OPTIONAL in the format — validate warns «download without origin» for a dtc_kind download that does not say it, never an error, so an old stamp stays readable; EMStudio's composer requires it for a Download and fills it when it can be read. Leaves as em:retrievedFrom (xsd:anyURI for a URL) and comes back as data.retrieved_from."}
       }
     },
     "DTCDeviceNode": {
@@ -1755,7 +1757,7 @@
       "parent": "Node",
       "abbreviation": "GCP",
       "label": "Ground control points",
-      "description": "The set of ground control points a registration was (or will be) solved from. data.points is a list of {id, world:[x,y,z], observations:[{image, pixel:[x,y]}], uncertainty?}; data.crs names the frame the world coordinates are in (null = a site-local grid, which is a different statement from absent). Minimum 3 observed non-collinear points for a similarity to be determined — reported by `solvable`, enforced by the runner, never at construction (a set being assembled in the field is legitimately incomplete).",
+      "description": "The set of ground control points a registration was (or will be) solved from. data.points is a list of {id, world:[x,y,z], observations:[{image, pixel:[x,y]}], uncertainty?}; data.crs names the frame the world coordinates are in (null = a site-local grid, which is a different statement from absent). Minimum 3 observed non-collinear points for a similarity to be determined — reported by `solvable`, enforced by the runner, never at construction (a set being assembled in the field is legitimately incomplete). 1.6.24 (dev30, decided by E.D. 2 Oct 2026, D7): data.control says WHAT the points are — ground_control_points (default, not written) or camera_positions: the GPS positions of the cameras themselves, each point {id, world, image, uncertainty?} with no pixel observation (the camera is where the photograph was taken from, not something seen in it), solvable with three; data.accuracy_m is the accuracy the project records for the cameras. A chunk referenced only by its cameras' GPS is placed absolute with such a set, and validate warns «georeferenced only by camera GPS»: absolute without the control said would claim more than the data.",
       "s3Dgraphy_file": "georeferencing_node.py",
       "mapping": {
         "cidoc": "crm:E73_Information_Object",

{s3dgraphy-1.6.0.dev29 → s3dgraphy-1.6.0.dev30}/src/s3dgraphy/__init__.py

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

{s3dgraphy-1.6.0.dev29 → s3dgraphy-1.6.0.dev30}/src/s3dgraphy/api.py

@@ -156,6 +156,9 @@ def validate(graph: Graph) -> Dict[str, Any]:
             f"from '{r['unit_name']}', which has no '{r['property_name']}' "
             f"property of its own")
     warnings = list(getattr(graph, "warnings", []) or [])
+    warnings.extend(_dtc_warnings(graph))
+    warnings.extend(_license_warnings(graph))
+    warnings.extend(_camera_gps_warnings(graph))
     geo = georeference_state(graph)
     if geo == "undeclared":
         info.append("the graph is not georeferenced: no CRS is declared "
@@ -174,6 +177,89 @@ def validate(graph: Graph) -> Dict[str, Any]:
     }
 
 
+def _dtc_warnings(graph: Graph) -> List[str]:
+    """What a DTC chain leaves unsaid that a reader would want said — warnings,
+    never issues: an old stamp stays readable and nobody is stopped.
+
+    * D1 (E.D., 2 Oct 2026) — a Download that does not say where it came from
+      (``how.acquisition.retrieved_from``: a DOI or a URL). The composer asks
+      for it; the format leaves it optional."""
+    from .dtc.ingest import DOWNLOAD_KIND, acquisition_origin
+    out: List[str] = []
+    for node in getattr(graph, "nodes", []) or []:
+        if getattr(node, "node_type", None) != "dtc_acquisition":
+            continue
+        data = getattr(node, "data", None) or {}
+        if data.get("dtc_kind") == DOWNLOAD_KIND and not acquisition_origin(node):
+            out.append(
+                f"download without origin: '{getattr(node, 'name', '')}' "
+                f"({node.node_id}) does not say where it came from "
+                f"(how.acquisition.retrieved_from — a DOI or a URL)")
+    return out
+
+
+def _camera_gps_warnings(graph: Graph) -> List[str]:
+    """D7 (E.D., 2 Oct 2026): a registration controlled ONLY by the GPS
+    positions of the cameras (a GCPSetNode of control camera_positions, no set
+    of ground control beside it). It counts as absolute, and is said for what it
+    is: a drone's GPS can be tens of metres off the survey."""
+    from .nodes.georeferencing_node import GCPSetNode
+    nodes = {n.node_id: n for n in getattr(graph, "nodes", []) or []}
+    sets_of: Dict[str, List[Any]] = {}
+    for e in getattr(graph, "edges", []) or []:
+        if getattr(e, "edge_type", None) == "has_gcp_set" and e.edge_target in nodes:
+            sets_of.setdefault(e.edge_source, []).append(nodes[e.edge_target])
+    out: List[str] = []
+    for transform_id, sets in sets_of.items():
+        controls = {(getattr(s, "data", None) or {}).get("control")
+                    or GCPSetNode.GROUND_CONTROL for s in sets}
+        if controls == {GCPSetNode.CAMERA_POSITIONS}:
+            for gcp in sets:
+                d = getattr(gcp, "data", None) or {}
+                acc = d.get("accuracy_m")
+                out.append(
+                    f"georeferenced only by camera GPS: '{getattr(gcp, 'name', '')}' "
+                    f"({gcp.node_id}) controls the registration {transform_id} with "
+                    f"{len(d.get('points') or [])} camera positions"
+                    + (f" (accuracy {acc:g} m)" if isinstance(acc, (int, float)) else "")
+                    + " and no ground control point")
+    return out
+
+
+_LICENSE_CODE = re.compile(r"^(?:CC|CC0)(?:[-_ ][A-Z]{2})*(?:[-_ ]\d+(?:\.\d+)?)?$")
+
+
+def _license_code(text: Any) -> Optional[str]:
+    """A Creative Commons code read for comparison — upper case, '-' between
+    the parts, no version («cc by-nd 4.0» → «CC-BY-ND») — or ``None`` when the
+    text is not a code («Creative Commons Attribution» is a name, not a code)."""
+    t = str(text or "").strip().upper().replace("_", "-")
+    if not t or not _LICENSE_CODE.match(t):
+        return None
+    t = re.sub(r"[- ]+\d+(?:\.\d+)?$", "", t)
+    return re.sub(r"[- ]+", "-", t)
+
+
+def _license_warnings(graph: Graph) -> List[str]:
+    """D6 (E.D., 2 Oct 2026): a licence whose NAME and TYPE are two different
+    licences («CC-BY-ND» of type CC-BY-NC-ND, San Pietro). The graph is not
+    corrected — which one is right is the author's to say, against the record
+    it was published with — it is said. Compared only when the name is itself
+    a licence code: a long name beside a code is not a disagreement."""
+    out: List[str] = []
+    for node in getattr(graph, "nodes", []) or []:
+        if getattr(node, "node_type", None) != "license":
+            continue
+        name = getattr(node, "name", "")
+        ltype = (getattr(node, "data", None) or {}).get("license_type")
+        a, b = _license_code(name), _license_code(ltype)
+        if a and b and a != b:
+            out.append(
+                f"license name and type disagree: '{name}' ({node.node_id}) is "
+                f"of type '{ltype}' — say which licence the work carries")
+    return out
+
+
 # ── a property with more than one owner ─────────────────────────────────────
 def property_owners(graph: Graph, property_id: str) -> List[Dict[str, Any]]:
     """The owners of a property, the original first: ``[{owner, edge,
@@ -2756,12 +2842,20 @@ def resolve_resource(graph: Graph, resource_id: str, *, registry: Any = None
     Looks up the ResourceNode by its ``node_id`` (the stable ID), reads its current
     locator, and asks the resolver registry (default: passthrough) to map it to
     a :class:`~s3dgraphy.resources.Location`. Returns the Location as a dict
-    ``{kind, value, exists}``, or ``None`` if no such resource exists."""
+    ``{kind, value, exists}``, or ``None`` if no such resource exists.
+
+    A DocumentNode answers too (dev30, A1): it carries its file in ``url`` (the
+    GraphML's «/DosCo/D.02.jpg»), read as a locator like a resource's — so a
+    caller asks one seam for both and never reads the url by itself. A document
+    with no url answers ``None``, as a missing resource does."""
     from .resources import default_registry
     node = graph.find_node_by_id(resource_id)
-    if node is None or getattr(node, "node_type", None) != "resource":
+    kind = getattr(node, "node_type", None) if node is not None else None
+    if kind not in ("resource", "document"):
         return None
     locator = _resource_locator(node)
+    if kind == "document" and not locator:
+        return None
     reg = registry if registry is not None else default_registry()
     loc = reg.resolve(resource_id, locator, graph=graph)
     return loc.to_dict() if loc is not None else None

{s3dgraphy-1.6.0.dev29 → s3dgraphy-1.6.0.dev30}/src/s3dgraphy/dtc/__init__.py

@@ -51,6 +51,8 @@ from .neighbourhood import (
 from .ingest import (
     DEFAULT_ACQUISITION_KIND,
     DEFAULT_PROCESS_KIND,
+    DOWNLOAD_KIND,
+    acquisition_origin,
     acquisition_members,
     attribute_batch,
     batch_summary,

{s3dgraphy-1.6.0.dev29 → s3dgraphy-1.6.0.dev30}/src/s3dgraphy/dtc/ingest.py

@@ -83,6 +83,28 @@ _USAGE_ROLES = {
 
 # ── the small shared readers (dict-or-object, tombstone-aware) ───────────────
 
+#: the kind of an acquisition whose origin is asked for (E.D., 2 Oct 2026, D1)
+DOWNLOAD_KIND = "download"
+
+
+def acquisition_origin(node: Any) -> Optional[str]:
+    """Where a retrieved object came from — ``how.acquisition.retrieved_from``
+    of the stamp format: the DOI or URL a Download was made from.
+
+    Read in the two places an acquisition keeps its facts: ``data.acquisition``
+    (an event absorbed from a stamp) and ``data`` itself (an event made by
+    :func:`bucket_acquisition`, whose ``metadata`` are the event's facts). The
+    second is the shape a graph is saved in, and the one the RDF importer
+    gives back. ``None`` when the act does not say."""
+    data = _data(node)
+    block = data.get("acquisition")
+    for holder in ((block if isinstance(block, dict) else {}), data):
+        value = holder.get("retrieved_from")
+        if isinstance(value, str) and value.strip():
+            return value.strip()
+    return None
+
+
 def _data(node: Any) -> Dict[str, Any]:
     d = getattr(node, "data", None)
     return d if isinstance(d, dict) else {}

{s3dgraphy-1.6.0.dev29 → s3dgraphy-1.6.0.dev30}/src/s3dgraphy/exporter/rdf_exporter.py

@@ -2008,6 +2008,15 @@ class RDFExporter:
                     ctx.add((node_iri, pred, Literal(
                         json.dumps(value, ensure_ascii=False, sort_keys=True),
                         datatype=RDF.JSON)))
+            # dev30 (D1): where a retrieved object came from — a DOI or a URL,
+            # an xsd:anyURI when it is one, a plain literal otherwise
+            if node_type == "dtc_acquisition":
+                from ..dtc.ingest import acquisition_origin
+                origin = acquisition_origin(node)
+                if origin:
+                    is_uri = origin.startswith(("http://", "https://"))
+                    ctx.add((node_iri, EM.retrievedFrom, Literal(
+                        origin, datatype=XSD.anyURI if is_uri else None)))
 
     @staticmethod
     def _emit_resource_packing(node_iri: URIRef, data: Dict[str, Any],
@@ -2025,6 +2034,12 @@ class RDFExporter:
             covers = "members"
         if covers:
             ctx.add((node_iri, EM.digestCovers, Literal(str(covers))))
+        # dev30 (D4): the digest of a SET has a predicate of its own, so a
+        # reader tells it from the digest of a file without reading two triples
+        # together; em:checksum + em:digestCovers stay beside it for the readers
+        # that already know them.
+        if covers == "members" and data.get("checksum"):
+            ctx.add((node_iri, EM.membersDigest, Literal(str(data["checksum"]))))
         content = data.get("content_digest")
         if isinstance(content, dict):
             content = content.get("digest")