s3dgraphy 1.6.0.dev16__tar.gz → 1.6.0.dev18__tar.gz

{s3dgraphy-1.6.0.dev16/src/s3dgraphy.egg-info → s3dgraphy-1.6.0.dev18}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: s3dgraphy
-Version: 1.6.0.dev16
+Version: 1.6.0.dev18
 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,6 +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.0
 Provides-Extra: rdf
 Requires-Dist: rdflib>=7.0; extra == "rdf"
 Provides-Extra: rdf-embedded
@@ -274,7 +275,7 @@ The rule the other repos inherit, in one line: *if an endpoint needs to compute
 something about a graph, that something belongs here.* This library has no web
 framework and no socket on purpose — what it does can be proved on a table.
 
-**The whole map:** [`ARCHITECTURE-SYSTEM.md`](../em-server/docs/ARCHITECTURE-SYSTEM.md).
+**The whole map:** [`ARCHITECTURE-SYSTEM.md`](../stratigraph-server/docs/ARCHITECTURE-SYSTEM.md).
 
 ---
 

{s3dgraphy-1.6.0.dev16 → s3dgraphy-1.6.0.dev18}/README.md

@@ -198,7 +198,7 @@ The rule the other repos inherit, in one line: *if an endpoint needs to compute
 something about a graph, that something belongs here.* This library has no web
 framework and no socket on purpose — what it does can be proved on a table.
 
-**The whole map:** [`ARCHITECTURE-SYSTEM.md`](../em-server/docs/ARCHITECTURE-SYSTEM.md).
+**The whole map:** [`ARCHITECTURE-SYSTEM.md`](../stratigraph-server/docs/ARCHITECTURE-SYSTEM.md).
 
 ---
 

{s3dgraphy-1.6.0.dev16 → s3dgraphy-1.6.0.dev18}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "s3dgraphy"
-version = "1.6.0.dev16"
+version = "1.6.0.dev18"
 description = "3D Stratigraphic Graph Management Library for archaeological and heritage applications"
 readme = "README.md"
 requires-python = ">=3.9"
@@ -51,6 +51,12 @@ dependencies = [
     "lxml>=4.9.0",              # used by graphml importer/exporter
     "openpyxl>=3.0.0",          # used by xlsx_importer
     "networkx>=3.0",            # used by temporal/inference_engine.py
+    # The stamp FORMAT — read, write, compare, walk — extracted so that a
+    # Blender add-on or a Metashape script can use it without installing any of
+    # 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.0",
 ]
 
 [project.urls]

{s3dgraphy-1.6.0.dev16 → s3dgraphy-1.6.0.dev18}/src/s3dgraphy/JSON_config/datamodel_translations.json

@@ -124,7 +124,7 @@
   },
   "DTCAcquisitionNode": {
    "description": {
-    "en": "A DTC ACQUISITION chunk: the digital event by which an asset ENTERS this study from an (opaque, Tier-0) external source — a data-transfer / ingestion event, DISTINCT from the genesis DTCProcessNode. Projected as crmdig:D12_Data_Transfer_Event (a subclass of D7_Digital_Machine_Event, ⊂ prov:Activity): 'events that transfer a digital object from one digital carrier to another; normally the digital object remains the same' — the object arrives opaque, no genesis is asserted. Tier 0: single-ring chain — the acquisition event --dtc_had_output[prov:generated]--> the acquired Resource (ResourceNode); the upstream root is an opaque external entity recorded as literals on data (repo/record/agent/retrieved_at/rights), not a genesis sub-graph. data.dtc_kind from the `acquisition` axis (download / ingest / local_import). Keeps genesis != acquisition as distinct TYPES inside the one DTC substrate.",
+    "en": "A DTC ACQUISITION step: the digital event by which an asset ENTERS this study from an (opaque, Tier-0) external source — a data-transfer / ingestion event, DISTINCT from the genesis DTCProcessNode. Projected as crmdig:D12_Data_Transfer_Event (a subclass of D7_Digital_Machine_Event, ⊂ prov:Activity): 'events that transfer a digital object from one digital carrier to another; normally the digital object remains the same' — the object arrives opaque, no genesis is asserted. Tier 0: single-ring chain — the acquisition event --dtc_had_output[prov:generated]--> the acquired Resource (ResourceNode); the upstream root is an opaque external entity recorded as literals on data (repo/record/agent/retrieved_at/rights), not a genesis sub-graph. data.dtc_kind from the `acquisition` axis (download / ingest / local_import). Keeps genesis != acquisition as distinct TYPES inside the one DTC substrate.",
     "validated_it": false,
     "validated_el": false,
     "validated_he": false,
@@ -146,7 +146,7 @@
   },
   "DTCProcessNode": {
    "description": {
-    "en": "A DTC PROCESS chunk: the transformation/processing event that turns inputs into produced digital objects (data.dtc_kind from the `process` axis, e.g. transformation). Projected as a crmdig:D7_Digital_Machine_Event / prov:Activity; its inputs and outputs are the dtc_had_input (prov:used) and dtc_had_output (prov:generated) edges.",
+    "en": "A DTC PROCESS step: the transformation/processing event that turns inputs into produced digital objects (data.dtc_kind from the `process` axis, e.g. transformation). Projected as a crmdig:D7_Digital_Machine_Event / prov:Activity; its inputs and outputs are the dtc_had_input (prov:used) and dtc_had_output (prov:generated) edges.",
     "validated_it": false,
     "validated_el": false,
     "validated_he": false,
@@ -1081,6 +1081,38 @@
    "label": {
     "en": "Annotation Region"
    }
+  },
+  "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)."
+   },
+   "label": {
+    "en": "Ground control points"
+   }
+  },
+  "RegistrationTransformNode": {
+   "description": {
+    "en": "The 7-parameter similarity (rotation 3x3 row-major, translation [x,y,z], positive scale) that places a produced model, with data.rms and data.residuals — the error bar, stored beside the claim rather than in a log nobody keeps. data.crs is the frame the model lands IN; null means a site-local frame (mode 'local'), which is NOT the same sentence as an absent transform. Re-registration is a NEW node produced by a NEW crmdig:D7; the superseded one is never edited."
+   },
+   "label": {
+    "en": "Registration transform"
+   }
+  },
+  "RepresentationModelNodeGroup": {
+   "description": {
+    "en": "Typed aggregation of the representation models that form ONE named set published under a single Document — «Survey 2015» under D.01, «Reconstruction» under D.09 (EM16-RMNG, meeting of 2026-09-10). Until then the RM container lived only as EM Tools' `scene.rm_containers` PropertyGroup, so the grouping that gives the set its meaning was invisible to anyone reading the graph. IT SITS BESIDE, IT DOES NOT REPLACE: every member keeps its own epoch edges (has_first_epoch / survive_in_epoch) and the Document keeps its DIRECT has_representation_model edges to each model — the group is added on top and never put in between, so a consumer that ignores it reads exactly what it read before. Membership is the TAG axis 'is_in_representation_model_group', like is_in_functional_unit and is_in_location, but 1:1 and not m:n: a mesh belongs to exactly one container, the rule already in force on the Blender side where `mesh_names` is authoritative. A group may legally be EMPTY and may legally have NO Document: both are states the RM Manager UI already shows. NOT a FunctionalUnitNodeGroup (that aggregates stratigraphic units into a building component; these members are models, not units); NOT an ActivityNodeGroup (nothing happened here and the set has no formation event of its own); NOT the Document, which stays the documentary anchor — deleting the container removes the group and not the Document."
+   },
+   "label": {
+    "en": "RM Container"
+   }
+  },
+  "DTCDeviceNode": {
+   "description": {
+    "en": "The APPARATUS a DTC step happened on — camera, sensor, drone, computer, scanner, total station, GNSS receiver. Projected as crmdig:D8_Digital_Device and attached to the EVENT by dtc_happened_on_device (crmdig:L12_happened_on_device), never to the input or the output: the three dtc_kinds flow axes are what went in, what happened and what came out, and a device is what it happened ON. Until 2026-09-16 it was a STRING inside how.acquisition, and a string cannot be asked «what did this machine produce» or «that lens was distorted, which models are affected». NOT a DTCNode: a DTC node is a STEP (an event in the chain) and a device is a thing in the world — it has no inputs, no outputs, and a provenance walk has no business entering it; subclassing would have put it in the chain by inheritance and set the class hierarchy arguing with dtc_role. data.dtc_kind comes from the `device` axis of dtc_kinds (em_visual_rules.json), so adding an apparatus is a JSON entry plus a sign. THE ID IS DERIVED FROM THE DESCRIPTOR (make | model | serial) by uuid5 — the same mechanism bucket_acquisition uses for a campaign name, but WITHOUT the graph_id in the key, because a campaign is an event of one study while the same camera in two studies is one camera. WHAT THAT COSTS, DECLARED: without a serial number two identical bodies derive the same id and MERGE, and the graph then cannot say which body took a given file. data.distinguishes records which happened ('serial' = one body, 'make+model' = a model). A declared merge is better than an invented distinction: salting the id with a graph or a timestamp would make two records of the SAME camera look like two cameras, and that failure is silent. Gated out of the stratigrapher palette, like every DTC node."
+   },
+   "label": {
+    "en": "DTC Device"
+   }
   }
  }
 }

{s3dgraphy-1.6.0.dev16 → s3dgraphy-1.6.0.dev18}/src/s3dgraphy/JSON_config/em_visual_rules.json

@@ -1,6 +1,6 @@
 {
   "formal_language": "EM",
-  "version": "1.6.14",
+  "version": "1.6.17",
   "_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,6 +9,8 @@
     "In breve: qui si decide di che colore DISEGNARE una US; li si registra di che colore ERA."
   ],
   "_changelog": {
+    "1.6.16": "Asset declarations made TRUE. Four styles named a 2D file that is not there — SE.png, TSU.svg, serUSD.svg and unknown.png (which never existed) — and GRAPH named two, so it drew no icon at all. icons.ts returns null for a missing file and the canvas quietly draws the shape, so all five failed silently. Now: graph.svg authored (neutral gray, three nodes and their edges, the meta-container), unknown points at the generic_node.svg that exists, the three stale halves name the file that is there. Enforced by tests/test_visual_assets.py; the 16 unmodelled .glb are REPORTED (there and in sync-datamodels.sh), not asserted — a placeholder that looks official is harder to notice than an absence.",
+    "1.6.15": "Georeferencing gets its symbol on the canvas: node_styles GCP (GCPSetNode, crosshair) and RGT (RegistrationTransformNode, axes + rotation arc), in the same #FF6600 reference family as GEO/SS/LINK, each with its own 2D icon. ADDITIVE. Also 1.6.14-era: dtc_kinds.process.photogrammetry. Note the limit of a per-TYPE rule: whether a transform is georeferenced or a site-local frame is an INSTANCE fact (data.crs) and is read from the has_gcp_set edge, not from the style.",
     "1.6.14": "BUGFIX-GLYPH follow-up (2026-08-05, E.D.): SE now renders its GLYPH in the scene (the new SE.svg, a stratigraphic-section box with a writable middle band) instead of a bare triangle, so a name can be written inside it. Added SE to 2d_render_glyph_types (aspect 1.331 from the SVG viewBox) and switched SE 2d_icon_prefer to vector (the raster SE.png is the stale stipple; the new symbol is the SVG). Dropped the interim shape_bbox=square. The shape:triangle stays declared for other consumers but the 2D scene draws the glyph. NOTE: verify the SVG carries a light background for dark-canvas legibility (like combiner.svg).",
     "1.6.13": "BUGFIX-GLYPH (2026-08-05): SE (StratigraphicEvent) gains shape_bbox=\"square\" on its style, like BR. Its triangle was drawn in the wide default 90x32 box, leaving the connect handle far from the glyph; a square bbox (side = min(w,h)) makes the triangle sit in a ~32x32 box with the handle adjacent, matching BR (diamond, square) and the glyph types. No shape_scale: unlike BR (a 0.7 marker) the SE triangle stays full-size. The SCENE representation of SE remains the triangle shape, not the raster icon (S10/POL5 decision unchanged).",
     "1.6.12": "EM3 - `2d_render_glyph_types` guadagna una tabella `aspect`: la larghezza del box di un nodo-glifo e la sua ALTEZZA per l'aspect del disegno, quindi tutti i glifi hanno la stessa altezza e differiscono solo in larghezza (regola E.D.). Default 1.0 = quadrato, che e cio che sono gli undici glifi DTC dopo l'autocrop di POL4 ed extractor/combiner per costruzione; l'unico davvero non quadrato oggi e `author` (0.875 = 448/512). I numeri sono STATICI e misurati una volta dai file: un aspect letto da naturalWidth a runtime farebbe dipendere il layout da quando un bitmap finisce di decodificare (box che salta, due run diversi sullo stesso documento). Il prezzo di un numero statico e che puo diventare stantio se un asset viene ridisegnato: da questa versione sync-datamodels.sh ri-misura ogni file vendorato e AVVISA se una dichiarazione sbaglia di oltre il 2%.",
@@ -27,7 +29,8 @@
     "1.5.3": "Fix USD / serUSD material colour: RGB was (0.549, 0.103, 0.0) = #8C1A00 (red), should be #D86400 (orange) to match the canonical USD documentary colour used in the GraphML palette template, node_registry defaults and document_variant_styles.observable. USD border_color also corrected from #8C1A00 to #D86400 (serUSD border was already correct).",
     "1.5.2": "Added RSF (Reused Special Find / spolia) node style — octagon, red border (#9B3333), white fill. Sibling of SF/VSF, distinguished by border colour. Originating DP: DP-26.",
     "1.5.1": "Added LocationNodeGroup node style (dashed roundrectangle, kind-based border colour) and is_in_location edge style with primary_modifier override.",
-    "1.5.0": "Initial EM 1.5 visual rules."
+    "1.5.0": "Initial EM 1.5 visual rules.",
+    "1.6.17": "Added RepresentationModelNodeGroup node style (EM16-RMNG): the group family's dashed roundrectangle with the RM family's #FF6600 title-tab, and the is_in_representation_model_group edge style. Additive only — no existing style touched, and the epoch↔RM / Document→RM edges keep the rendering they had."
   },
   "2d_render_glyph_types": {
     "_comment": "Node types the 2D renderer draws as a CENTRED GLYPH (their official icon) instead of a shape. Their box is HEIGHT-DRIVEN: the height is the engine node height and the width is that height times the `aspect` below (EM2 made them square; EM3 generalised the square to a per-glyph aspect). Keyed by RUNTIME node_type, deliberately: this block is read both by EMStudio's icons.ts and by its Rust layout engine, and a list keyed by node_type needs no alias table on either side (`node_styles` is keyed by the short abbreviation, EXT/COMB/..., which the engine does not know). Added in 1.6.11 (EM2) because the fact had been living as a hand-written set inside icons.ts, and the layout engine needs the same fact to give those nodes a height-driven box: a glyph drawn 32 wide inside a 90x32 box leaves empty margins, and the connect handle — anchored to the right edge of the box — ends up floating away from the glyph. NB two things this does NOT include. (1) `document` and `property`: they are drawn with custom geometry (a sheet with a folded corner, a bracketed text annotation) that is NOT square, and squaring their box would crush the text. (2) DTC nodes: their glyph is chosen per NODE from `data.dtc_kind` and not from the type, so a consumer decides that node by node — a plain `link` is not a glyph, a `link` with a dtc_kind is.",
@@ -224,7 +227,7 @@
     "serUSD": {
       "3d_file": "src/3D/serUSD.glb",
       "2d_file_rast": "src/2D/serUSD.png",
-      "2d_file_vect": "src/2D/serUSD.svg",
+      "2d_file_vect": "src/2D/serUSD.png",
       "style": {
         "material": {
           "rgba_color": {
@@ -287,7 +290,7 @@
     "TSU": {
       "3d_file": "src/3D/TSU.glb",
       "2d_file_rast": "src/2D/TSU.png",
-      "2d_file_vect": "src/2D/TSU.svg",
+      "2d_file_vect": "src/2D/TSU.png",
       "style": {
         "material": {
           "rgba_color": {
@@ -332,7 +335,7 @@
     "SE": {
       "_comment": "Stratigraphic Event: l'ATTO che crea, modifica o distrugge un'unita — un terremoto che fa cadere l'intonaco, una demolizione, l'inizio di un cantiere. Non e materia, e un processo, e per questo non appartiene a nessuna delle famiglie cromatiche della materia (rosso reale, verde/blu virtuale, arancio documentario, giallo special find, grigio negativo). Prende il TEAL della famiglia attivita: un ActivityNodeGroup e un fascio di atti e porta gia la linguetta ciano #CCFFFF, quindi il ciano e l'unico colore del linguaggio che dice gia 'e successo qualcosa' invece di 'qualcosa c'e'. Curato in S10 (2026-08-02): fino ad allora SE portava il segnaposto #BC0000 mai scelto, che per giunta contraddiceva il proprio bordo nero, e il node datamodel dichiarava il simbolo 'to be defined'. Il nero di BR e stato scartato di proposito: un material nero rende un proxy illeggibile in viewport, e i proxy SE si vedono (Heriverse li disegna fra i suoi stratigraphicTypes). POL5 (2026-08-04): l'ICONA e il raster (`2d_icon_prefer: raster`), come per NARR e per la stessa ragione — SE.svg e un tratteggio vettorializzato da 284 KB per un glifo che nessun renderer disegna oltre i 30 px. Il vettore resta dichiarato perche esiste; il flag dice quale dei due DISEGNARE. Il PNG a 256 px e reso DA quell'SVG, quindi i due non possono divergere. Nel grafo SE resta comunque un TRIANGOLO disegnato (shape), non l'icona: il raster serve a palette ed elenchi.",
       "3d_file": "src/3D/SE.glb",
-      "2d_file_rast": "src/2D/SE.png",
+      "2d_file_rast": "src/2D/SE.svg",
       "2d_file_vect": "src/2D/SE.svg",
       "2d_icon_prefer": "vector",
       "style": {
@@ -490,7 +493,7 @@
     "GRAPH": {
       "_comment": "Top-level container node representing the EM graph itself. Anchor for graph-wide metadata propagation (default author, license, embargo, epoch). Rendered as a dashed rounded rectangle to read as a meta-container, neutral gray to stay visually distinct from stratigraphic and paradata nodes. Graphml palette prefix: 'G.'.",
       "file_3d": "src/3D/graph.glb",
-      "2d_file_rast": "src/2D/graph.png",
+      "2d_file_rast": "src/2D/graph.svg",
       "2d_file_vect": "src/2D/graph.svg",
       "style": {
         "material": {
@@ -542,6 +545,32 @@
       },
       "label_position": "over"
     },
+    "GCP": {
+      "_comment": "Ground control points — the EVIDENCE behind a registration: which point was seen on which photograph at which pixel, and where it is in the world. The NODE IS THE SET, never the single GCP (data.points), which is why the icon shows one target among several marks. Same orange as the other reference/georeferencing nodes (GEO, SS, LINK) because it is that family; the crosshair shape distinguishes measurement-of-a-place from position-of-a-site. Graphml palette prefix: 'GC.'.",
+      "file_3d": "src/3D/gcp_set.glb",
+      "2d_file_rast": "src/2D/gcp_set.svg",
+      "2d_file_vect": "src/2D/gcp_set.svg",
+      "style": {
+        "border_color": "#FF6600",
+        "fill_color": "#FFFFFF",
+        "border_style": "solid",
+        "shape": "crosshair"
+      },
+      "label_position": "over"
+    },
+    "RGT": {
+      "_comment": "Registration transform — the SOLUTION: the 7-parameter similarity that places a produced model, with its RMS. Drawn as axes plus a rotation arc. NOTE, and it is a limit of a per-TYPE rule: whether a given transform is georeferenced (data.crs set) or a site-local frame (crs null) is an INSTANCE fact and cannot be encoded here — a reader tells the two modes apart by the presence of the has_gcp_set edge, which is why that edge exists. Graphml palette prefix: 'RG.'.",
+      "file_3d": "src/3D/registration_transform.glb",
+      "2d_file_rast": "src/2D/registration_transform.svg",
+      "2d_file_vect": "src/2D/registration_transform.svg",
+      "style": {
+        "border_color": "#FF6600",
+        "fill_color": "#FFFFFF",
+        "border_style": "solid",
+        "shape": "axes"
+      },
+      "label_position": "over"
+    },
     "GEO": {
       "file_3d": "src/3D/geo.glb",
       "2d_file_rast": "src/2D/geo_position.svg",
@@ -628,7 +657,7 @@
     },
     "unknown": {
       "file_3d": "src/3D/unknown.glb",
-      "file_2d": "src/2D/unknown.png",
+      "file_2d": "src/2D/generic_node.svg",
       "style": {
         "border_color": "#FF0000",
         "fill_color": "#FFFFFF",
@@ -762,6 +791,18 @@
           "description": "Interpretive / semantic identity (basilica, room A, courtyard)."
         }
       }
+    },
+    "RepresentationModelNodeGroup": {
+      "_comment": "Group-folder rendering for an RM container (EM16-RMNG): the named set of representation models a Document publishes — «Survey 2015» under D.01. Shape and frame are the GROUP family's, unchanged and deliberately not reinvented (roundrectangle, neutral grey fill, dashed black border) — what identifies the family is the group title-tab colour, exactly as cyan identifies ActivityNodeGroup, peach ParadataNodeGroup, green TimeBranchNodeGroup and grey LocationNodeGroup. The tab here carries #FF6600, which is the RM family's OWN border colour (see the RM / RMDoc / RMSF styles): the box reads as «a group of representation models» without a new shape and without a new colour being invented. Verified free before use: #FF6600 was not in use as a label_background by any other style, and is not among the colours the GraphML importer keys on.",
+      "style": {
+        "shape": "roundrectangle",
+        "fill_color": "#F5F5F5",
+        "border_color": "#000000",
+        "border_style": "dashed",
+        "border_width": 1.0,
+        "label_background": "#FF6600",
+        "label_position": "top"
+      }
     }
   },
   "document_roles": {
@@ -783,7 +824,7 @@
     }
   },
   "document_variant_styles": {
-    "_comment": "Axis 3 of the three-axis Canonical-Document classification (EM 1.6). Declares how the document's Representation Model (RM) is spatialized in the 3D scene. Q-C (EM 1.6): the axis is a scale of METRIC AUTHORITY OF PLACEMENT, and it is authoritative on the **RMDoc** — the spatial instance — not on the Document. The Document's existence is certain; what has degrees is its spatialisation, which is what the RMDoc IS (proxy:US :: RMSF:SF :: RM:state :: RMDoc:Document). The position itself (X,Y,Z + rotation) lives on the RMDoc and nowhere else; the Document may mirror the value on its yEd border for diagram convenience, but it carries no position. The ladder, from most to least metric authority: reality_based \u2192 observable \u2192 asserted \u2192 symbolic. `em_based` is not a rung of that ladder but a provenance statement (the asset IS an EM-derived reconstruction). Temporality is a separate matter: it is an attribution, certain or argued through a paradata chain, never a grade on this axis. The 'geometry' property drives both the GraphML DocumentNode border colour (in yEd) and the RM contour colour in the 3D viewport (per the v1.6 toggle). Documents without an RM (e.g. PDF articles, bibliographies) omit the geometry property entirely — no node, no colour. Border WIDTH carries the canonical/instance distinction: width >= 3.0 is the canonical document, anything thinner is a use-instance. The COLOUR classifies the canonical document's geometry-axis category. A black thick border means 'canonical without geometry classification' (canonical_unknown). Renamed from 'master' in schema 2: every digital document is a copy, so 'master' misread as 'original vs copies'; what the flag marks is the document drawn at its own creation, vs the instances that re-use it. Kept in sync with the reference nodes in templates/em_palette_template.graphml.",
+    "_comment": "Axis 3 of the three-axis Canonical-Document classification (EM 1.6). Declares how the document's Representation Model (RM) is spatialized in the 3D scene. Q-C (EM 1.6): the axis is a scale of METRIC AUTHORITY OF PLACEMENT, and it is authoritative on the **RMDoc** — the spatial instance — not on the Document. The Document's existence is certain; what has degrees is its spatialisation, which is what the RMDoc IS (proxy:US :: RMSF:SF :: RM:state :: RMDoc:Document). The position itself (X,Y,Z + rotation) lives on the RMDoc and nowhere else; the Document may mirror the value on its yEd border for diagram convenience, but it carries no position. The ladder, from most to least metric authority: reality_based → observable → asserted → symbolic. `em_based` is not a rung of that ladder but a provenance statement (the asset IS an EM-derived reconstruction). Temporality is a separate matter: it is an attribution, certain or argued through a paradata chain, never a grade on this axis. The 'geometry' property drives both the GraphML DocumentNode border colour (in yEd) and the RM contour colour in the 3D viewport (per the v1.6 toggle). Documents without an RM (e.g. PDF articles, bibliographies) omit the geometry property entirely — no node, no colour. Border WIDTH carries the canonical/instance distinction: width >= 3.0 is the canonical document, anything thinner is a use-instance. The COLOUR classifies the canonical document's geometry-axis category. A black thick border means 'canonical without geometry classification' (canonical_unknown). Renamed from 'master' in schema 2: every digital document is a copy, so 'master' misread as 'original vs copies'; what the flag marks is the document drawn at its own creation, vs the instances that re-use it. Kept in sync with the reference nodes in templates/em_palette_template.graphml.",
     "default": {
       "border_color": "#000000",
       "border_style": "solid",
@@ -830,27 +871,130 @@
   "dtc_kinds": {
     "_comment": "DATA-DRIVEN, EXPANDABLE per-kind vocabulary for the DTC substrate profile (ECHOES). Mirrors the Master-Document axis vocabularies above (document_roles/content_natures): the three base kinds (input/process/output) each list specific kinds seeded from the 2017 DTC palette. Adding a new kind (e.g. audio, spectroscopy) is a JSON entry here (+ a glyph) — NOT a code change; the DTC node classes validate against these keys via s3dgraphy.utils.get_dtc_kinds(). `glyph` names the 2017 DTC SVG (wired in the later glyph/visual-manager slice; recorded here as data only).",
     "input": {
-      "photo": { "label": "Photograph", "glyph": "09_photos", "description": "Photographic acquisition (single image or set)." },
-      "laserscanner": { "label": "Laser scan", "glyph": "10_laserscanner", "description": "Terrestrial/close-range laser scanning acquisition." },
-      "topographic": { "label": "Topographic survey", "glyph": "01_topographicnetwork", "description": "Total-station / topographic-network acquisition." }
+      "photo": {
+        "label": "Photograph",
+        "glyph": "09_photos",
+        "description": "Photographic acquisition (single image or set)."
+      },
+      "laserscanner": {
+        "label": "Laser scan",
+        "glyph": "10_laserscanner",
+        "description": "Terrestrial/close-range laser scanning acquisition."
+      },
+      "topographic": {
+        "label": "Topographic survey",
+        "glyph": "01_topographicnetwork",
+        "description": "Total-station / topographic-network acquisition."
+      }
     },
     "process": {
-      "transformation": { "label": "Transformation", "glyph": "00_transformation", "description": "A processing/transformation step turning inputs into produced digital objects." }
+      "photogrammetry": {
+        "label": "Photogrammetry",
+        "glyph": "03_mesh",
+        "description": "Structure-from-motion reconstruction: a cluster of photographs becomes a 3D model. A specific kind of transformation, named because what a reader needs to know about a mesh is which family of process made it — and because the placement (RegistrationTransform) only means something for this one."
+      },
+      "transformation": {
+        "label": "Transformation",
+        "glyph": "00_transformation",
+        "description": "A processing/transformation step turning inputs into produced digital objects."
+      }
     },
     "acquisition": {
-      "download": { "label": "Download", "glyph": null, "description": "Retrieval of a digital object from a remote (opaque, Tier-0) repository." },
-      "ingest": { "label": "Ingest", "glyph": null, "description": "Generic ingestion of a digital object into the study." },
-      "local_import": { "label": "Local import", "glyph": null, "description": "Acquisition from the local file system (project-folder search) — the local analog of remote acquisition." },
-      "uri_reference": { "label": "URI reference", "glyph": null, "description": "The URI was acquired, not the object: the resource stays where it is and is reached through its own access protocol (an open link, or one you subscribe to). No bytes were copied — calling this a download would record a retrieval that never happened." }
+      "download": {
+        "label": "Download",
+        "glyph": null,
+        "description": "Retrieval of a digital object from a remote (opaque, Tier-0) repository."
+      },
+      "ingest": {
+        "label": "Ingest",
+        "glyph": null,
+        "description": "Generic ingestion of a digital object into the study."
+      },
+      "local_import": {
+        "label": "Local import",
+        "glyph": null,
+        "description": "Acquisition from the local file system (project-folder search) — the local analog of remote acquisition."
+      },
+      "uri_reference": {
+        "label": "URI reference",
+        "glyph": null,
+        "description": "The URI was acquired, not the object: the resource stays where it is and is reached through its own access protocol (an open link, or one you subscribe to). No bytes were copied — calling this a download would record a retrieval that never happened."
+      }
     },
     "output": {
-      "pointcloud": { "label": "Point cloud", "glyph": "02_pointcloud", "description": "Produced point cloud." },
-      "mesh": { "label": "Mesh", "glyph": "03_mesh", "description": "Produced 3D mesh model." },
-      "dem": { "label": "DEM", "glyph": "07_DEM", "description": "Digital Elevation Model." },
-      "orthophoto": { "label": "Orthophoto", "glyph": "08_ortophoto", "description": "Produced orthophoto / orthomosaic." },
-      "points": { "label": "Points", "glyph": "04_points", "description": "Vector point features." },
-      "lines": { "label": "Lines", "glyph": "05_lines", "description": "Vector line features." },
-      "polygons": { "label": "Polygons", "glyph": "06_polygons", "description": "Vector polygon features." }
+      "pointcloud": {
+        "label": "Point cloud",
+        "glyph": "02_pointcloud",
+        "description": "Produced point cloud."
+      },
+      "mesh": {
+        "label": "Mesh",
+        "glyph": "03_mesh",
+        "description": "Produced 3D mesh model."
+      },
+      "dem": {
+        "label": "DEM",
+        "glyph": "07_DEM",
+        "description": "Digital Elevation Model."
+      },
+      "orthophoto": {
+        "label": "Orthophoto",
+        "glyph": "08_ortophoto",
+        "description": "Produced orthophoto / orthomosaic."
+      },
+      "points": {
+        "label": "Points",
+        "glyph": "04_points",
+        "description": "Vector point features."
+      },
+      "lines": {
+        "label": "Lines",
+        "glyph": "05_lines",
+        "description": "Vector line features."
+      },
+      "polygons": {
+        "label": "Polygons",
+        "glyph": "06_polygons",
+        "description": "Vector polygon features."
+      }
+    },
+    "device": {
+      "_comment": "THE APPARATUS AXIS — what a step happened ON, not what went in or came out. crmdig:L12_happened_on_device, deliberately NOT L10_had_input: the photographs are the input and the camera is not, and flattening the two makes «which files did this body take» unanswerable, which is the only reason the node exists. One class (DTCDeviceNode, crmdig:D8_Digital_Device) and the genus from here, so adding an apparatus stays a JSON entry plus a sign — the same rule the flow axes follow. | THE GLYPHS ARE ONE FAMILY: 11_device is a rounded box with a connector on one side, the poorest shape that still says «apparatus» and free of any optical cue because a computer has no lens. Two boxes whose connectors touch read as a RIG — a computer with a sensor on it, a camera on a drone — which is how an assembly is said without inventing a second symbol. Every genus keeps that outline IDENTICAL and changes one inner mark, so the family reads from far away and the genus from close up. The SVGs live in JSON_config/src/2D/dtc/ beside 00–10; these names are declared here first and drawn separately. | NOTE FOR WHOEVER EXTENDS THIS: `laserscanner` sits on the `input` axis above, and now that this axis exists it is in the wrong box — a scanner is an apparatus, not an input. It is NOT moved: stamps already emitted carry that kind on that axis, and moving it would invalidate them in silence, which is the defect this whole substrate is built against. Left to E.D.",
+      "camera": {
+        "label": "Camera",
+        "glyph": "11_device_optical",
+        "description": "A photographic or video body. The circle is the GENUS mark and sits inside the family outline: the outline itself stays free of optics so a computer can wear it."
+      },
+      "sensor": {
+        "label": "Sensor",
+        "glyph": "11_device_sensor",
+        "description": "A measuring instrument that is not a camera — multispectral, thermal, a lidar head, a magnetometer. The wave mark says «it records a quantity»."
+      },
+      "drone": {
+        "label": "Drone",
+        "glyph": "11_device_drone",
+        "description": "The airframe that carried the apparatus. Its own device because it is the thing that flew, and a rig is drawn as its connector touching the payload's."
+      },
+      "computer": {
+        "label": "Computer",
+        "glyph": "11_device_computer",
+        "description": "The machine a processing step ran on. Here because «the reconstruction produced different numbers on the two workstations» is a question somebody will ask, and it is the reason the family outline had to stay free of optics."
+      },
+      "scanner": {
+        "label": "Scanner",
+        "glyph": "11_device_scanner",
+        "description": "A range or structured-light scanner — the APPARATUS. Distinct from the `laserscanner` entry on the `input` axis, which is a kind of input and is left where it is on purpose (see the note above)."
+      },
+      "total_station": {
+        "label": "Total station",
+        "glyph": "11_device_station",
+        "description": "A theodolite with a rangefinder — the instrument behind a `topographic` input."
+      },
+      "gnss": {
+        "label": "GNSS receiver",
+        "glyph": "11_device_gnss",
+        "description": "A satellite positioning receiver: the apparatus that produces a how.acquisition.location whose `source` is a measurement and not a person's word."
+      }
     }
   },
   "edge_style": {
@@ -1036,6 +1180,15 @@
         "width": 1.5
       },
       "label": "Included in Timebranch"
+    },
+    "is_in_representation_model_group": {
+      "_comment": "Membership of a representation model in an RM container (EM16-RMNG). Dashed like the other membership edges that are TAGS rather than structure (has_representation_model, has_property), and carrying the RM family's #FF6600 so the line reads as part of the same family as the group's title-tab. NOTE: is_in_functional_unit has no entry in this block — a pre-existing gap, reported and not fixed here.",
+      "style": {
+        "color": "#FF6600",
+        "line_style": "dashed",
+        "width": 1.5
+      },
+      "label": "Is in Representation Model Group"
     }
   }
-}
+}

{s3dgraphy-1.6.0.dev16 → s3dgraphy-1.6.0.dev18}/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.3",
+ "s3Dgraphy_data_model_version": "1.6.5",
  "node_types": {
   "ActivityNodeGroup": {
    "parent": "GroupNode",
@@ -37,10 +37,15 @@
    "node_type": "dtc_acquisition",
    "description": "DTC acquisition/ingestion event (ECHOES DTC profile, acquisition seam)."
   },
+  "DTCDeviceNode": {
+   "parent": "Node",
+   "node_type": "dtc_device",
+   "description": "The apparatus an acquisition or a processing step happened on."
+  },
   "DTCNode": {
    "parent": "Node",
    "node_type": null,
-   "description": "Abstract base for a DTC chain chunk. Concrete subclasses set ``node_type``"
+   "description": "Abstract base for one STEP of a DTC chain. Concrete subclasses set ``node_type``"
   },
   "DTCProcessNode": {
    "parent": "DTCNode",
@@ -77,6 +82,11 @@
    "node_type": "FunctionalUnitNodeGroup",
    "description": "Typed aggregation of the stratigraphic units that make up one"
   },
+  "GCPSetNode": {
+   "parent": "Node",
+   "node_type": "gcp_set",
+   "description": "The ground control points a registration was (or will be) solved from."
+  },
   "GeoPositionNode": {
    "parent": "Node",
    "node_type": "geo_position",
@@ -157,6 +167,11 @@
    "node_type": "property",
    "description": "Nodo che rappresenta una proprietà associata a un altro nodo."
   },
+  "RegistrationTransformNode": {
+   "parent": "Node",
+   "node_type": "registration_transform",
+   "description": "The similarity that places a model — 7 parameters and what they cost."
+  },
   "RepresentationModelDocNode": {
    "parent": "RepresentationNode",
    "node_type": "representation_model_doc",
@@ -167,6 +182,11 @@
    "node_type": "representation_model",
    "description": "Node representing a 3D model or spatialized image."
   },
+  "RepresentationModelNodeGroup": {
+   "parent": "GroupNode",
+   "node_type": "RepresentationModelNodeGroup",
+   "description": "Typed aggregation of the representation models that form ONE named set"
+  },
   "RepresentationModelSpecialFindNode": {
    "parent": "RepresentationNode",
    "node_type": "representation_model_sf",