s3dgraphy 1.6.0.dev23__tar.gz → 1.6.0.dev25__tar.gz

{s3dgraphy-1.6.0.dev23/src/s3dgraphy.egg-info → s3dgraphy-1.6.0.dev25}/PKG-INFO

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

{s3dgraphy-1.6.0.dev23 → s3dgraphy-1.6.0.dev25}/pyproject.toml

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

{s3dgraphy-1.6.0.dev23 → s3dgraphy-1.6.0.dev25}/src/s3dgraphy/JSON_config/datamodel_translations.json

@@ -1436,6 +1436,46 @@
     "de": "Repräsentationsmodell Einzelfund"
    }
   },
+  "ResourceFileNode": {
+   "description": {
+    "en": "ONE FILE of a resource (E.D. 2026-09-30, «la risorsa e i suoi file»): the ResourceNode is the SET — the handle a person stamps, cites and opens, with name, kind, scope, residency, role, tier, packaging and rights — and the ResourceFileNode is each member: an obj, its mtl and its textures are three files of one resource. Reached by has_file (reverse is_file_of); the ROLE (entry_point | member) and the RELATIVE PATH travel on the EDGE, because the same file (a corrected texture) sits in N resources under N paths. With ONE file the node is IMPLICIT: a ResourceNode with url (and checksum) and no has_file is a resource of one file, and s3dgraphy.resources.files.resource_files shows that file anyway; the node is written only when there are several files or the one file has a stamp or an identity of its own. Fields: url (a path, a file:// / s3:// / http(s):// URI or a blend:// locator), checksum ('sha256:<hex>'; 'emstruct1:<hex>' for a datablock, comparable not verifiable), size_bytes, media_type. For a datablock blend_file and datablock are READ from the blend:// locator (resources/resolver.py, the one place that knows its form), never stored twice. The same file in several resources is ONE node, recognised by its checksum.",
+    "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": "UN FILE di una risorsa (E.D. 30 set 2026, «la risorsa e i suoi file»): il ResourceNode è l'INSIEME — la maniglia che si timbra, si cita e si apre — e il ResourceFileNode è ogni membro: un obj, il suo mtl e le sue texture sono tre file di una risorsa sola. Raggiunto da has_file; il RUOLO (entry_point | member) e il PERCORSO RELATIVO stanno sull'ARCO, perché lo stesso file sta in più risorse con percorsi diversi. Con UN file il nodo è IMPLICITO: url e checksum restano sul ResourceNode. Per un datablock blend_file e datablock si leggono dal locator blend://, mai scritti due volte.",
+    "el": "ΕΝΑ ΑΡΧΕΙΟ ενός πόρου (E.D. 30/9/2026): ο ResourceNode είναι το ΣΥΝΟΛΟ — η λαβή που σφραγίζεται, παρατίθεται και ανοίγεται — και ο ResourceFileNode κάθε μέλος του: ένα obj, το mtl του και οι υφές του είναι τρία αρχεία ενός πόρου. Συνδέεται με has_file· ο ΡΟΛΟΣ (entry_point | member) και η ΣΧΕΤΙΚΗ ΔΙΑΔΡΟΜΗ βρίσκονται στην ΑΚΜΗ, γιατί το ίδιο αρχείο ανήκει σε πολλούς πόρους με διαφορετικές διαδρομές. Με ΕΝΑ αρχείο ο κόμβος είναι ΣΙΩΠΗΡΟΣ: url και checksum μένουν στον ResourceNode.",
+    "he": "קובץ אחד של משאב (E.D. 30.9.2026): ResourceNode הוא הקבוצה — הידית שמחתימים, מצטטים ופותחים — ו־ResourceFileNode הוא כל חבר בה: קובץ obj, קובץ ה־mtl שלו והטקסטורות שלו הם שלושה קבצים של משאב אחד. מקושר ב־has_file; התפקיד (entry_point | member) והנתיב היחסי נמצאים על הקשת, כי אותו קובץ נמצא בכמה משאבים בנתיבים שונים. עם קובץ אחד הצומת משתמע: url ו־checksum נשארים על ה־ResourceNode.",
+    "es": "UN ARCHIVO de un recurso (E.D. 30 sep 2026): el ResourceNode es el CONJUNTO — el asa que se sella, se cita y se abre — y el ResourceFileNode es cada miembro: un obj, su mtl y sus texturas son tres archivos de un solo recurso. Se alcanza con has_file; el ROL (entry_point | member) y la RUTA RELATIVA están en la ARISTA, porque el mismo archivo está en varios recursos con rutas distintas. Con UN archivo el nodo es IMPLÍCITO: url y checksum quedan en el ResourceNode.",
+    "pl": "JEDEN PLIK zasobu (E.D. 30.09.2026): ResourceNode to ZBIÓR — uchwyt, który się stempluje, cytuje i otwiera — a ResourceFileNode to każdy jego element: obj, jego mtl i tekstury to trzy pliki jednego zasobu. Osiągany przez has_file; ROLA (entry_point | member) i ŚCIEŻKA WZGLĘDNA są na KRAWĘDZI, bo ten sam plik należy do wielu zasobów pod różnymi ścieżkami. Przy JEDNYM pliku węzeł jest DOMYŚLNY: url i checksum zostają w ResourceNode.",
+    "ro": "UN FIȘIER al unei resurse (E.D. 30 sep 2026): ResourceNode este ANSAMBLUL — mânerul care se ștampilează, se citează și se deschide — iar ResourceFileNode este fiecare membru: un obj, mtl-ul său și texturile sale sunt trei fișiere ale unei singure resurse. Atins prin has_file; ROLUL (entry_point | member) și CALEA RELATIVĂ stau pe MUCHIE, pentru că același fișier stă în mai multe resurse cu căi diferite. Cu UN singur fișier nodul este IMPLICIT: url și checksum rămân pe ResourceNode.",
+    "fr": "UN FICHIER d'une ressource (E.D. 30 sept. 2026) : le ResourceNode est l'ENSEMBLE — la poignée que l'on tamponne, cite et ouvre — et le ResourceFileNode chaque membre : un obj, son mtl et ses textures sont trois fichiers d'une seule ressource. Atteint par has_file ; le RÔLE (entry_point | member) et le CHEMIN RELATIF sont sur l'ARÊTE, car le même fichier appartient à plusieurs ressources sous des chemins différents. Avec UN fichier le nœud est IMPLICITE : url et checksum restent sur le ResourceNode.",
+    "de": "EINE DATEI einer Ressource (E.D. 30.09.2026): der ResourceNode ist die MENGE — der Griff, den man stempelt, zitiert und öffnet — und der ResourceFileNode jedes Mitglied: ein obj, sein mtl und seine Texturen sind drei Dateien einer Ressource. Erreicht über has_file; die ROLLE (entry_point | member) und der RELATIVE PFAD stehen auf der KANTE, weil dieselbe Datei in mehreren Ressourcen unter verschiedenen Pfaden liegt. Bei EINER Datei ist der Knoten IMPLIZIT: url und checksum bleiben am ResourceNode."
+   },
+   "label": {
+    "en": "Resource 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 della risorsa",
+    "el": "Αρχείο πόρου",
+    "he": "קובץ משאב",
+    "es": "Archivo del recurso",
+    "pl": "Plik zasobu",
+    "ro": "Fișier al resursei",
+    "fr": "Fichier de la ressource",
+    "de": "Datei der Ressource"
+   }
+  },
   "ResourceNode": {
    "description": {
     "en": "Class to represent a link node (ResourceNode) in the graph. Attributes: url (str): URL of the link. url_type (str): Type of URL (e.g., 'External link', 'Image'). description (str): Description of the link.",
@@ -5647,6 +5687,65 @@
     "de": "Hat Sperrfrist"
    }
   },
+  "has_file": {
+   "label": {
+    "en": "Has 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": "Ha il file",
+    "el": "Έχει αρχείο",
+    "he": "יש קובץ",
+    "es": "Tiene el archivo",
+    "pl": "Ma plik",
+    "ro": "Are fișierul",
+    "fr": "A pour fichier",
+    "de": "Hat die Datei"
+   },
+   "ui_phrase_as_source": {
+    "en": "{node} with file {x}",
+    "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": "{node} con il file {x}",
+    "el": "{node} με το αρχείο {x}",
+    "he": "{node} עם הקובץ {x}",
+    "es": "{node} con el archivo {x}",
+    "pl": "{node} z plikiem {x}",
+    "ro": "{node} cu fișierul {x}",
+    "fr": "{node} avec le fichier {x}",
+    "de": "{node} mit der Datei {x}"
+   },
+   "ui_phrase_as_target": {
+    "en": "{node} file of {x}",
+    "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": "{node} file di {x}",
+    "el": "{node} αρχείο του {x}",
+    "he": "{node} קובץ של {x}",
+    "es": "{node} archivo de {x}",
+    "pl": "{node} plik zasobu {x}",
+    "ro": "{node} fișier al {x}",
+    "fr": "{node} fichier de {x}",
+    "de": "{node} Datei von {x}"
+   }
+  },
   "has_first_epoch": {
    "label": {
     "en": "Has first epoch",
@@ -7006,6 +7105,27 @@
     "fr": "Validé par",
     "de": "Validiert von"
    }
+  },
+  "was_revision_of": {
+   "label": {
+    "en": "Was revision of",
+    "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": "È una revisione di",
+    "el": "Είναι αναθεώρηση του",
+    "he": "הוא גרסה מתוקנת של",
+    "es": "Es una revisión de",
+    "pl": "Jest rewizją",
+    "ro": "Este o revizie a",
+    "fr": "Est une révision de",
+    "de": "Ist eine Revision von"
+   }
   }
  },
  "dtc_kinds": {

{s3dgraphy-1.6.0.dev23 → s3dgraphy-1.6.0.dev25}/src/s3dgraphy/JSON_config/em.ttl

@@ -46,8 +46,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.8" ;
-    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.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.9" ;
+    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.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/> ,
@@ -706,6 +706,12 @@ em:RegistrationTransform
     rdfs:subClassOf crm:E73_Information_Object ;
     rdfs:comment "The 7-parameter similarity (rotation, translation, positive scale) that places a produced model in a frame, carrying its own error bar (rms, residuals) beside the claim rather than in a log nobody keeps. It DESCRIBES a mapping between two crmgeo:SP4 spatial coordinate reference systems, which CIDOC and CRMgeo model individually but never as a parameterised map between two of them — hence E73 as the honest superclass. Deliberately NOT an event: the alternative, leaving the parameters as literals on the D7 acquisition, loses the ability to point at «the placement» as a thing that gets superseded, and being superseded is the whole reason the transform is a node. The three modes are the SHAPE of the graph, never a flag: 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. Maps to: Python RegistrationTransformNode (node_type=\'registration_transform\')."@en .
 
+em:ResourceFile
+    a owl:Class ;
+    rdfs:label "Resource File"@en ;
+    rdfs:subClassOf crmdig:D1_Digital_Object ;
+    rdfs:comment "ONE FILE of a resource: the resource (crm:E73_Information_Object) is the set a person stamps, cites and opens, the file is each of its members — an obj, its mtl, its textures. The resource reaches it with crm:P106_is_composed_of; the file's role (entry point or member) and its path relative to the entry point are data of that relation in the property graph and are not projected. With one file the file is implicit and not emitted: the resource's own url and checksum are that file. Maps to: Python ResourceFileNode (node_type='resource_file')."@en .
+
 em:Narrative
     a owl:Class ;
     rdfs:label "Narrative"@en ;

{s3dgraphy-1.6.0.dev23 → s3dgraphy-1.6.0.dev25}/src/s3dgraphy/JSON_config/em_qualia_types.json

@@ -1,11 +1,11 @@
 {
     "metadata": {
-      "version": "1.6.2",
-      "last_updated": "2026-09-28",
+      "version": "1.6.3",
+      "last_updated": "2026-10-01",
       "maintainers": ["Emanuel Demetrescu"],
       "license": "CC-BY-SA-4.0",
       "license_note": "Share-alike per allinearsi agli strumenti terminologici da cui questo datamodel prende gli ancoraggi (ICCD CC BY-SA 3.0 IT) e perche' una derivazione resti aperta. Gli identificatori AAT/CIDOC citati nei `mappings` sono RIFERIMENTI, non contenuto incorporato: lo share-alike non si propaga ai vocabolari altrui, che mantengono i propri termini.",
-      "changelog": "v1.6.2: added two descriptive qualia of the stratigraphic unit asked for by the DAI record (iDAI.field Layer, D7/D8) — proposte da Cowork per E.D., 28 set 2026, dalla scheda DAI: `feature_shape` (spatial; the shape in plan or section named with a term, AAT 300056273, E55_Type) and `boundary_distinctness` (material; how sharp the limits are: abrupt / clear / gradual / diffuse, E55_Type, no AAT evident). Both controlled vocabularies with indicative seed values; templates declare their own. v1.6.1: added the spatial qualia `geometry` — the PROXY as a quale. The geometry-without-material of a unit becomes a PropertyNode whose payload is a SemanticShapeNode (has_semantic_shape), so the proxy inherits the paradata chain a lone node could not have, and one proxy can be synthesised from several sources. CIDOC default crmgeo:SP5_Geometric_Place_Expression, flagged `confirm_with: Felicetti` (E36 is the alternative, to be decided together with em:AnnotationRegion). v1.6.0: version realigned to the EM language version (EM 1.6) — supersedes the standalone 4.x line (last was 4.2), so all EM JSON config files now share the 1.6.x scheme. Added optional `rationale` + `example` fields to qualia entries (a plain-language why + a concrete case), shown by the EMStudio vocabulary picker when creating a PropertyNode. Seeded for the temporal qualia (absolute_time_start / absolute_time_end / dating_method); to be filled in for the rest incrementally. Prior (4.x) history: v4.2 added rationale/example scaffolding; v4.1: expanded spatial elevation qualia for pyArchInit us_table quote (all E54_Dimension): elevation_relative, elevation_min_absolute, elevation_max_absolute, elevation_min_relative, elevation_max_relative, elevation_min_usm, elevation_max_usm (the generic 'elevation' = absolute MASL, used by quota_abs). Each pyArchInit quota column maps to its own qualia id so they don't collide on the single-PropertyNode-per-property_name rule. v4.0: verified all v3.0 CIDOC-CRM mappings (correct). Expanded with: volume, area, circumference in dimensional; color, texture, finish, patina, hardness, porosity in material; damage_type, fragility, completeness in state; tool_marks, joining_technique in technical; bounding_box, footprint_area in spatial; duration, terminus_post_quem, terminus_ante_quem, relative_chronology in temporal; ceremonial_function, ritual_function, defensive_function, domestic_function, symbolic_function in telic; school, workshop, period_attribution in stylistic. NEW subcategories: iconographic + semantic under cultural_interpretive (iconographic_subject, narrative_content, iconographic_program, aesthetic_value, religious_significance, monumental_status, attribution). Added provenance_history, exhibition_history, publication_history under administrative; NEW ownership subcategory (current_custodian, ownership_chain). NEW CATEGORY epistemic — meta-qualia central to EM paradata model (confidence_level, certainty_level, uncertainty_factors, methodology_used, validation_method, source_quality, primary_contributor, review_status, last_modified)."
+      "changelog": "v1.6.3 (MICRO em.ttl nel datamodel, 2026-10-26, decided by E.D. 2026-10-01 — every em: term of em.ttl is cited by a datamodel): epistemic.confidence.confidence_level.mappings gains specialised_alternative 'em:confidenceLevel', the em.ttl literal form of the same scalar, declared and NOT emitted (the exporter keeps crminf:I6_Belief_Value via J5). Mapping text only, no quale changed. v1.6.2: added two descriptive qualia of the stratigraphic unit asked for by the DAI record (iDAI.field Layer, D7/D8) — proposte da Cowork per E.D., 28 set 2026, dalla scheda DAI: `feature_shape` (spatial; the shape in plan or section named with a term, AAT 300056273, E55_Type) and `boundary_distinctness` (material; how sharp the limits are: abrupt / clear / gradual / diffuse, E55_Type, no AAT evident). Both controlled vocabularies with indicative seed values; templates declare their own. v1.6.1: added the spatial qualia `geometry` — the PROXY as a quale. The geometry-without-material of a unit becomes a PropertyNode whose payload is a SemanticShapeNode (has_semantic_shape), so the proxy inherits the paradata chain a lone node could not have, and one proxy can be synthesised from several sources. CIDOC default crmgeo:SP5_Geometric_Place_Expression, flagged `confirm_with: Felicetti` (E36 is the alternative, to be decided together with em:AnnotationRegion). v1.6.0: version realigned to the EM language version (EM 1.6) — supersedes the standalone 4.x line (last was 4.2), so all EM JSON config files now share the 1.6.x scheme. Added optional `rationale` + `example` fields to qualia entries (a plain-language why + a concrete case), shown by the EMStudio vocabulary picker when creating a PropertyNode. Seeded for the temporal qualia (absolute_time_start / absolute_time_end / dating_method); to be filled in for the rest incrementally. Prior (4.x) history: v4.2 added rationale/example scaffolding; v4.1: expanded spatial elevation qualia for pyArchInit us_table quote (all E54_Dimension): elevation_relative, elevation_min_absolute, elevation_max_absolute, elevation_min_relative, elevation_max_relative, elevation_min_usm, elevation_max_usm (the generic 'elevation' = absolute MASL, used by quota_abs). Each pyArchInit quota column maps to its own qualia id so they don't collide on the single-PropertyNode-per-property_name rule. v4.0: verified all v3.0 CIDOC-CRM mappings (correct). Expanded with: volume, area, circumference in dimensional; color, texture, finish, patina, hardness, porosity in material; damage_type, fragility, completeness in state; tool_marks, joining_technique in technical; bounding_box, footprint_area in spatial; duration, terminus_post_quem, terminus_ante_quem, relative_chronology in temporal; ceremonial_function, ritual_function, defensive_function, domestic_function, symbolic_function in telic; school, workshop, period_attribution in stylistic. NEW subcategories: iconographic + semantic under cultural_interpretive (iconographic_subject, narrative_content, iconographic_program, aesthetic_value, religious_significance, monumental_status, attribution). Added provenance_history, exhibition_history, publication_history under administrative; NEW ownership subcategory (current_custodian, ownership_chain). NEW CATEGORY epistemic — meta-qualia central to EM paradata model (confidence_level, certainty_level, uncertainty_factors, methodology_used, validation_method, source_quality, primary_contributor, review_status, last_modified)."
     },
     "qualia_categories": [
       {
@@ -1218,7 +1218,9 @@
                 "name": "Confidence Level",
                 "description": "Numerical confidence in the assertion (0-100%). The EM-canonical scalar for paradata-supported claims. CRM mapping changed 2026-07-10: was E54_Dimension; a confidence is the value a belief is held with, i.e. crminf:I6_Belief_Value (see WP3 coverage analysis G5 / Appendix C). The RDF exporter's qualia-precedence rule types the PropertyNode accordingly.",
                 "mappings": {
-                  "cidoc_crm": "crminf:I6_Belief_Value"
+                  "cidoc_crm": "crminf:I6_Belief_Value",
+                  "specialised_alternative": "em:confidenceLevel",
+                  "specialised_alternative_note": "1.6.3: em:confidenceLevel (em.ttl, xsd:decimal on any E1) is the plain-literal form of the same number, declared for a reader that wants the scalar without the CRMinf belief. NOT emitted: the RDF exporter types the PropertyNode crminf:I6_Belief_Value and links it with J5_holds_to_be (_emit_belief_propositions). Putting it in cidoc_crm's place would be the switch, and is E.D.'s decision."
                 },
                 "data_type": "percentage",
                 "range": [0, 100],

{s3dgraphy-1.6.0.dev23 → s3dgraphy-1.6.0.dev25}/src/s3dgraphy/JSON_config/em_visual_rules.json

@@ -1,6 +1,6 @@
 {
   "formal_language": "EM",
-  "version": "1.6.25",
+  "version": "1.6.27",
   "_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.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.",
+    "1.6.26": "THE FILE OF A RESOURCE (MICRO-RISORSA-FILE, 18 Oct 2026, decision of E.D. 30 Sep 2026). node_styles += FILE for ResourceFileNode (node datamodel 1.6.17): the LINK chain glyph and colour with a DASHED border — a file is a member of the resource it hangs from, the same family and not a second resource. NO NEW GLYPH: it reuses src/2D/link.svg, declares no .glb (LINK's src/3D/link.glb is itself among the missing 3D models, and a new type must not add to that gap), and a sign of its own is left to E.D.",
     "1.6.25": "THE EIGHT DTC GLYPHS APPROVED (E.D., 30 Sep 2026; MICRO-GEOMETRIA-ORIGINE part 1). The eight drafts of 1.6.23 moved from src/2D/bozze/dtc_<glyph>.svg to src/2D/dtc/<glyph>.svg (12_gnss_survey … 19_vectorization), the BOZZA word removed from their comment, glyphs_from_svg --write rerun: their 2d_glyphs entries no longer carry draft: true. src/2D/bozze/ is empty again. Still without a glyph (open): the four recoveries download, local_import, uri_reference, ingest.",
     "1.6.24": "THE CAPTURE IN RDF (MICRO-GENERI-GLIFI, 30 Sep 2026; proposed by Claude, accepted by E.D.). Six acquisition kinds declare `mapping` — the rdf:type their DTCAcquisitionNode takes INSTEAD of crmdig:D12_Data_Transfer_Event, which describes a transfer: photo, laserscanner → crmdig:D2_Digitization_Process (⊂ D11 ⊂ D7); topographic, gnss_survey → crmdig:D11_Digital_Measurement_Event (⊂ D7); field_drawing, recording_sheet → crm:E65_Creation (⊂ E7; made by hand, the file is their copy). The retrievals (download, local_import, uri_reference, ingest) declare none and stay D12. See dtc_kinds.acquisition._mapping_comment; read by rdf_exporter and rdf_importer through utils.get_dtc_kind_mapping. CRMem (em.ttl) 1.6.6 -> 1.6.7 for the changelog note.",
     "1.6.23": "THE EIGHT DTC GLYPHS, AS DRAFTS (MICRO-GENERI-GLIFI, 30 Sep 2026). The eight kinds 1.6.22 left with glyph: null now name a pictogram — gnss_survey 12_gnss_survey, field_drawing 13_field_drawing, recording_sheet 14_recording_sheet, decimation 15_decimation, georeferencing 16_georeferencing, format_conversion 17_format_conversion, classification 18_classification, vectorization 19_vectorization — drawn by Claude on the 2017 DTC family (circle r 41.14, black stroke, no colour) and marked BOZZA. They live in src/2D/bozze/dtc_<glyph>.svg, so their 2d_glyphs entries carry draft: true and no consumer vendors them as official. APPROVAL IS E.D.'S: move the file to src/2D/dtc/<glyph>.svg (dropping the dtc_ prefix), remove the word BOZZA from its comment, rerun `python -m s3dgraphy.tools.glyphs_from_svg --write`. The four retrieval kinds (download, local_import, uri_reference, ingest) still have glyph: null.",
@@ -3345,6 +3347,16 @@
       },
       "label_position": "over"
     },
+    "FILE": {
+      "2d_file_vect": "src/2D/resource_file.svg",
+      "style": {
+        "border_color": "#FF6600",
+        "fill_color": "#FFFFFF",
+        "border_style": "dashed",
+        "shape": "chain"
+      },
+      "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",

{s3dgraphy-1.6.0.dev23 → s3dgraphy-1.6.0.dev25}/src/s3dgraphy/JSON_config/hdto_extension.ttl

@@ -10,7 +10,7 @@
 @prefix dcterms:   <http://purl.org/dc/terms/> .
 
 # ============================================================================
-# HDT-O — Heritage Digital Twin Ontology — s3dgraphy alignment layer (v0.2)
+# HDT-O — Heritage Digital Twin Ontology — s3dgraphy alignment layer (v0.3)
 # ============================================================================
 #
 # Reconciled with ECHOES Deliverable D7.1 "The Digital Commons" (May 2024).
@@ -22,7 +22,14 @@
 #          Namespace placeholder (w3id.org/hdto/) — to be replaced when the
 #          official HDT-O resolvable IRI is published by the ECHOES consortium.
 # Author:  Emanuele Demetrescu (s3dgraphy v1.6.0 integration)
-# Date:    2026-05-23
+# Date:    2026-09-30 (v0.3; v0.2 2026-05-23)
+#
+# v0.3 (2026-09-30): the two declarations this file carried against D7.1 final
+#          are corrected. HC9 Study becomes a subclass of crm:E65 Creation (was
+#          crm:E7 Activity) and HC16 Heritage Proposition Set becomes a subclass
+#          of crminf:I4 Proposition Set and HC15 Persistent Digital Object (was
+#          crm:E73 Information Object alone). Both were recorded as open in
+#          docs/hdto-coverage.md, measured on D7.1_final.docx.
 # License: CC-BY-4.0
 #
 # What this file does:
@@ -87,15 +94,17 @@ hdto:HC15_Persistent_Digital_Object
 hdto:HC16_Heritage_Proposition_Set
     a owl:Class ;
     rdfs:label "Heritage Proposition Set"@en ;
-    rdfs:subClassOf crm:E73_Information_Object ;
-    rdfs:comment "A named graph carrying a set of formal propositions about (or related to) heritage entities. The atomic content unit that an HC2 Heritage Digital Twin aggregates: an HC2 'contains' (HP33) one or more HC16 instances. Version chains across editing actions are documented via HP30 added content / HP31 deleted content / HP32 replaced. An s3dgraphy em:EMGraph IS a Heritage Proposition Set (formally declared in em.ttl via owl:equivalentClass / subClassOf)."@en .
+    rdfs:subClassOf crminf:I4_Proposition_Set ,
+                    hdto:HC15_Persistent_Digital_Object ,
+                    crm:E73_Information_Object ;
+    rdfs:comment "A named graph carrying a set of formal propositions about (or related to) heritage entities. The atomic content unit that an HC2 Heritage Digital Twin aggregates: an HC2 'contains' (HP33) one or more HC16 instances. Per D7.1 (final, V1.0) a subclass of crminf:I4 Proposition Set and of HC15 Persistent Digital Object; crm:E73 Information Object is kept so that a CRM-only reader still resolves it. Version chains across editing actions are documented via HP30 added content / HP31 deleted content / HP32 replaced. An s3dgraphy em:EMGraph IS a Heritage Proposition Set (formally declared in em.ttl via owl:equivalentClass / subClassOf)."@en .
 
 
 hdto:HC9_Study
     a owl:Class ;
     rdfs:label "Study"@en ;
-    rdfs:subClassOf crm:E7_Activity ;
-    rdfs:comment "A scholarly activity (research, analysis or documentation, in any SSH / natural / exact-science domain) about a Heritage Entity (HC1), explicating a disciplinary focus and the part of the entity investigated. A study is about (HP23) one or more HC1 and has created (HP25) documentary outputs (crm:E31 Document) — in s3dgraphy the EM proposition set (HC16 / em:EMGraph). ECHOES D7.1."@en .
+    rdfs:subClassOf crm:E65_Creation ;
+    rdfs:comment "A scholarly activity (research, analysis or documentation, in any SSH / natural / exact-science domain) about a Heritage Entity (HC1), explicating a disciplinary focus and the part of the entity investigated. A study is about (HP23) one or more HC1 and has created (HP25) documentary outputs (crm:E31 Document) — in s3dgraphy the EM proposition set (HC16 / em:EMGraph). A subclass of crm:E65 Creation: the study is the scholarly act, and its documentary output is a separate thing joined to it by HP25, so a report, a field note or a metadata record is never an HC9. ECHOES D7.1 (final, V1.0)."@en .
 
 hdto:HC13_Project
     a owl:Class ;

{s3dgraphy-1.6.0.dev23 → s3dgraphy-1.6.0.dev25}/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.14",
+ "s3Dgraphy_data_model_version": "1.6.18",
  "node_types": {
   "ActivityNodeGroup": {
    "parent": "GroupNode",
@@ -197,6 +197,11 @@
    "node_type": null,
    "description": "Base class for all representation nodes in 3D space."
   },
+  "ResourceFileNode": {
+   "parent": "Node",
+   "node_type": "resource_file",
+   "description": "ONE FILE of a resource — the resource is the set, this is each member."
+  },
   "ResourceNode": {
    "parent": "Node",
    "node_type": "resource",