s3dgraphy 1.6.0.dev19__tar.gz → 1.6.0.dev21__tar.gz

{s3dgraphy-1.6.0.dev19/src/s3dgraphy.egg-info → s3dgraphy-1.6.0.dev21}/PKG-INFO

@@ -1,17 +1,17 @@
 Metadata-Version: 2.4
 Name: s3dgraphy
-Version: 1.6.0.dev19
+Version: 1.6.0.dev21
 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>
 License: GPL-3.0-or-later
-Project-URL: Homepage, https://github.com/zalmoxes-laran/s3dgraphy
+Project-URL: Homepage, https://github.com/ExtendedMatrix/s3Dgraphy
 Project-URL: Documentation, https://docs.extendedmatrix.org/projects/s3dgraphy/
-Project-URL: Repository, https://github.com/zalmoxes-laran/s3dgraphy.git
-Project-URL: Bug Reports, https://github.com/zalmoxes-laran/s3dgraphy/issues
-Project-URL: Source Code, https://github.com/zalmoxes-laran/s3dgraphy
+Project-URL: Repository, https://github.com/ExtendedMatrix/s3Dgraphy.git
+Project-URL: Bug Reports, https://github.com/ExtendedMatrix/s3Dgraphy/issues
+Project-URL: Source Code, https://github.com/ExtendedMatrix/s3Dgraphy
 Project-URL: Extended Matrix, https://www.extendedmatrix.org
-Project-URL: Changelog, https://github.com/zalmoxes-laran/s3dgraphy/blob/main/CHANGELOG.md
+Project-URL: Changelog, https://github.com/ExtendedMatrix/s3Dgraphy/blob/main/CHANGELOG.md
 Keywords: archaeology,stratigraphy,graph,3d,heritage,temporal-modeling,knowledge-graph,extended-matrix
 Classifier: Development Status :: 4 - Beta
 Classifier: Intended Audience :: Science/Research
@@ -81,7 +81,7 @@ Dynamic: license-file
 [![Python versions](https://img.shields.io/pypi/pyversions/s3dgraphy.svg)](https://pypi.org/project/s3dgraphy/)
 [![License: GPL v3](https://img.shields.io/badge/License-GPLv3-blue.svg)](https://www.gnu.org/licenses/gpl-3.0)
 [![Downloads](https://pepy.tech/badge/s3dgraphy)](https://pepy.tech/project/s3dgraphy)
-[![Publish to PyPI](https://github.com/zalmoxes-laran/s3dgraphy/actions/workflows/publish.yml/badge.svg)](https://github.com/zalmoxes-laran/s3dgraphy/actions/workflows/publish.yml)
+[![Publish to PyPI](https://github.com/ExtendedMatrix/s3Dgraphy/actions/workflows/publish.yml/badge.svg)](https://github.com/ExtendedMatrix/s3Dgraphy/actions/workflows/publish.yml)
 
 ## 3D Stratigraphic Graph Management Library
 
@@ -260,7 +260,7 @@ match exactly and case-sensitively. The same flow applies to
 
 - **[User Guide](https://docs.extendedmatrix.org/projects/s3dgraphy/)** - Complete documentation
 - **[API Reference](https://docs.extendedmatrix.org/projects/s3dgraphy/api.html)** - Detailed API docs
-- **[Examples](https://github.com/zalmoxes-laran/s3dgraphy/tree/main/examples)** - Code examples and tutorials
+- **[Examples](https://github.com/ExtendedMatrix/s3Dgraphy/tree/main/examples)** - Code examples and tutorials
 - **[Extended Matrix](https://www.extendedmatrix.org)** - Framework overview
 
 ## Where this sits
@@ -284,7 +284,7 @@ framework and no socket on purpose — what it does can be proved on a table.
 ### Setting up Development Environment
 
 ```bash
-git clone https://github.com/zalmoxes-laran/s3dgraphy.git
+git clone https://github.com/ExtendedMatrix/s3Dgraphy.git
 cd s3dgraphy
 python3 -m venv .venv
 .venv/bin/pip install -e ".[dev]"
@@ -339,7 +339,7 @@ git push --follow-tags
 ## 🤝 Contributing
 
 We welcome contributions. Open an issue or a pull request on
-[GitHub](https://github.com/zalmoxes-laran/s3dgraphy) — and see the
+[GitHub](https://github.com/ExtendedMatrix/s3Dgraphy) — and see the
 [Development](#-development) section above for how to run the suite and read its
 known baseline.
 
@@ -372,7 +372,7 @@ s3Dgraphy — referencing records live or baking them into the graph.
 
 The PyArchInit integration drove the design of the LocationNodeGroup in
 s3Dgraphy 0.1.41 (insight from
-[issue #5](https://github.com/zalmoxes-laran/s3Dgraphy/issues/5) by
+[issue #5](https://github.com/ExtendedMatrix/s3Dgraphy/issues/5) by
 [Enzo Cocca](https://github.com/enzococca)).
 
 To request inclusion in this list, see the [Ecosystem page](https://docs.extendedmatrix.org/en/latest/ecosystem.html) of the Extended Matrix manual.
@@ -384,9 +384,79 @@ s3Dgraphy is designed to be consumed by independent tools. **Revit**,
 domain-specific tools are natural candidates for similar bridges into the
 Extended Matrix ecosystem. If you maintain such a project and want to
 explore an integration, open a discussion at
-[github.com/zalmoxes-laran/s3Dgraphy/discussions](https://github.com/zalmoxes-laran/s3Dgraphy/discussions)
+[github.com/ExtendedMatrix/s3Dgraphy/discussions](https://github.com/ExtendedMatrix/s3Dgraphy/discussions)
 or look at the PyArchInit integration as a worked example.
 
+## Pubblicare su PyPI
+
+Il rilascio è **manuale** — Actions → *Publish to PyPI* → *Run workflow*, con il
+tag e il bersaglio (`testpypi` o `pypi`) — e **non usa nessun token**.
+
+### Perché non un token
+
+Un token API di lunga vita nei segreti del repository è una chiave di una
+persona che tiene in ostaggio un artefatto del progetto, e non dice **da dove**
+viene la wheel. Misurato il 22 settembre 2026 sulla versione che i servizi
+installano davvero:
+
+```
+curl https://pypi.org/integrity/s3dgraphy/1.6.0.dev18/\
+     s3dgraphy-1.6.0.dev18-py3-none-any.whl/provenance
+→ 404  {"message":"No provenance available for …"}
+```
+
+Tre servizi installano questa libreria e finisce dentro le immagini Docker che
+consegniamo a un partner: chi le specchia può risalire al Dockerfile, al commit
+e al tag — e poi arriva alla wheel, e la catena si interrompe lì.
+
+Il **Trusted Publisher** toglie il token e dà l'attestazione, perché sono la
+stessa cosa vista dai due lati: PyPI si fida di un'identità — questo
+repository, questo workflow — invece che di un segreto, e quell'identità è
+esattamente ciò che l'attestazione afferma.
+
+### I campi da mettere su PyPI (una volta, e li mette E.D.)
+
+PyPI → *Your projects* → **s3dgraphy** → *Settings* → **Publishing** → *Add a
+new publisher* → **GitHub**. Quattro campi, e questi sono i valori esatti:
+
+| campo | valore |
+|---|---|
+| **Owner** | `ExtendedMatrix` |
+| **Repository name** | `s3Dgraphy` |
+| **Workflow name** | `publish.yml` |
+| **Environment name** | *(vuoto)* |
+
+`Environment name` resta vuoto perché il workflow non dichiara nessun
+`environment:`. Se un giorno gliene si dà uno — è il modo di chiedere
+un'approvazione umana prima del push su PyPI — quel campo va compilato con lo
+stesso nome, e i due devono restare d'accordo.
+
+Su **TestPyPI** la procedura è identica, sul sito `test.pypi.org`, con gli
+stessi quattro valori: sono due indici diversi e ciascuno tiene la sua lista.
+
+Finché quei campi non ci sono, il workflow **fallisce** al passo di publish con
+un errore di PyPI che dice che il publisher non è configurato — che è il modo
+giusto di fallire.
+
+### Il cancello
+
+Dopo ogni rilascio in produzione il workflow interroga l'indice:
+
+```bash
+./scripts/verifica-provenance.sh 1.6.0.dev19
+```
+
+Un publish riuscito senza provenance è un publish che ha fatto metà del lavoro
+e lo dichiara riuscito. Lo script distingue i due guasti — l'attestazione che
+**manca** e quella che nomina un **altro repository**, che è il più grave dei
+due perché sembra una garanzia — e si può lanciare a mano su qualunque versione
+già pubblicata, inclusa una di un altro progetto:
+
+```bash
+PACCHETTO=sigstore GITHUB_REPOSITORY=sigstore/sigstore-python \
+  ./scripts/verifica-provenance.sh 4.5.0
+```
+
 ## 📄 License
 
 This project is licensed under the **GNU General Public License v3.0** - see the [LICENSE](LICENSE) file for details.
@@ -402,7 +472,7 @@ If you use s3dgraphy in your research, please cite:
   title={s3dgraphy: 3D Stratigraphic Graph Management Library},
   author={Demetrescu, Emanuel},
   year={2026},
-  url={https://github.com/zalmoxes-laran/s3dgraphy},
+  url={https://github.com/ExtendedMatrix/s3Dgraphy},
   version={1.6.0},
   institution={CNR-ISPC (National Research Council - Institute of Heritage Science)}
 }
@@ -418,11 +488,11 @@ If you use s3dgraphy in your research, please cite:
 
 ## 🔗 Links
 
-- **GitHub Repository**: https://github.com/zalmoxes-laran/s3dgraphy
+- **GitHub Repository**: https://github.com/ExtendedMatrix/s3Dgraphy
 - **PyPI Package**: https://pypi.org/project/s3dgraphy/
 - **Documentation**: https://docs.extendedmatrix.org/projects/s3dgraphy/
 - **Extended Matrix Website**: https://www.extendedmatrix.org
-- **Bug Reports**: https://github.com/zalmoxes-laran/s3dgraphy/issues
+- **Bug Reports**: https://github.com/ExtendedMatrix/s3Dgraphy/issues
 
 ---
 

{s3dgraphy-1.6.0.dev19 → s3dgraphy-1.6.0.dev21}/README.md

@@ -4,7 +4,7 @@
 [![Python versions](https://img.shields.io/pypi/pyversions/s3dgraphy.svg)](https://pypi.org/project/s3dgraphy/)
 [![License: GPL v3](https://img.shields.io/badge/License-GPLv3-blue.svg)](https://www.gnu.org/licenses/gpl-3.0)
 [![Downloads](https://pepy.tech/badge/s3dgraphy)](https://pepy.tech/project/s3dgraphy)
-[![Publish to PyPI](https://github.com/zalmoxes-laran/s3dgraphy/actions/workflows/publish.yml/badge.svg)](https://github.com/zalmoxes-laran/s3dgraphy/actions/workflows/publish.yml)
+[![Publish to PyPI](https://github.com/ExtendedMatrix/s3Dgraphy/actions/workflows/publish.yml/badge.svg)](https://github.com/ExtendedMatrix/s3Dgraphy/actions/workflows/publish.yml)
 
 ## 3D Stratigraphic Graph Management Library
 
@@ -183,7 +183,7 @@ match exactly and case-sensitively. The same flow applies to
 
 - **[User Guide](https://docs.extendedmatrix.org/projects/s3dgraphy/)** - Complete documentation
 - **[API Reference](https://docs.extendedmatrix.org/projects/s3dgraphy/api.html)** - Detailed API docs
-- **[Examples](https://github.com/zalmoxes-laran/s3dgraphy/tree/main/examples)** - Code examples and tutorials
+- **[Examples](https://github.com/ExtendedMatrix/s3Dgraphy/tree/main/examples)** - Code examples and tutorials
 - **[Extended Matrix](https://www.extendedmatrix.org)** - Framework overview
 
 ## Where this sits
@@ -207,7 +207,7 @@ framework and no socket on purpose — what it does can be proved on a table.
 ### Setting up Development Environment
 
 ```bash
-git clone https://github.com/zalmoxes-laran/s3dgraphy.git
+git clone https://github.com/ExtendedMatrix/s3Dgraphy.git
 cd s3dgraphy
 python3 -m venv .venv
 .venv/bin/pip install -e ".[dev]"
@@ -262,7 +262,7 @@ git push --follow-tags
 ## 🤝 Contributing
 
 We welcome contributions. Open an issue or a pull request on
-[GitHub](https://github.com/zalmoxes-laran/s3dgraphy) — and see the
+[GitHub](https://github.com/ExtendedMatrix/s3Dgraphy) — and see the
 [Development](#-development) section above for how to run the suite and read its
 known baseline.
 
@@ -295,7 +295,7 @@ s3Dgraphy — referencing records live or baking them into the graph.
 
 The PyArchInit integration drove the design of the LocationNodeGroup in
 s3Dgraphy 0.1.41 (insight from
-[issue #5](https://github.com/zalmoxes-laran/s3Dgraphy/issues/5) by
+[issue #5](https://github.com/ExtendedMatrix/s3Dgraphy/issues/5) by
 [Enzo Cocca](https://github.com/enzococca)).
 
 To request inclusion in this list, see the [Ecosystem page](https://docs.extendedmatrix.org/en/latest/ecosystem.html) of the Extended Matrix manual.
@@ -307,9 +307,79 @@ s3Dgraphy is designed to be consumed by independent tools. **Revit**,
 domain-specific tools are natural candidates for similar bridges into the
 Extended Matrix ecosystem. If you maintain such a project and want to
 explore an integration, open a discussion at
-[github.com/zalmoxes-laran/s3Dgraphy/discussions](https://github.com/zalmoxes-laran/s3Dgraphy/discussions)
+[github.com/ExtendedMatrix/s3Dgraphy/discussions](https://github.com/ExtendedMatrix/s3Dgraphy/discussions)
 or look at the PyArchInit integration as a worked example.
 
+## Pubblicare su PyPI
+
+Il rilascio è **manuale** — Actions → *Publish to PyPI* → *Run workflow*, con il
+tag e il bersaglio (`testpypi` o `pypi`) — e **non usa nessun token**.
+
+### Perché non un token
+
+Un token API di lunga vita nei segreti del repository è una chiave di una
+persona che tiene in ostaggio un artefatto del progetto, e non dice **da dove**
+viene la wheel. Misurato il 22 settembre 2026 sulla versione che i servizi
+installano davvero:
+
+```
+curl https://pypi.org/integrity/s3dgraphy/1.6.0.dev18/\
+     s3dgraphy-1.6.0.dev18-py3-none-any.whl/provenance
+→ 404  {"message":"No provenance available for …"}
+```
+
+Tre servizi installano questa libreria e finisce dentro le immagini Docker che
+consegniamo a un partner: chi le specchia può risalire al Dockerfile, al commit
+e al tag — e poi arriva alla wheel, e la catena si interrompe lì.
+
+Il **Trusted Publisher** toglie il token e dà l'attestazione, perché sono la
+stessa cosa vista dai due lati: PyPI si fida di un'identità — questo
+repository, questo workflow — invece che di un segreto, e quell'identità è
+esattamente ciò che l'attestazione afferma.
+
+### I campi da mettere su PyPI (una volta, e li mette E.D.)
+
+PyPI → *Your projects* → **s3dgraphy** → *Settings* → **Publishing** → *Add a
+new publisher* → **GitHub**. Quattro campi, e questi sono i valori esatti:
+
+| campo | valore |
+|---|---|
+| **Owner** | `ExtendedMatrix` |
+| **Repository name** | `s3Dgraphy` |
+| **Workflow name** | `publish.yml` |
+| **Environment name** | *(vuoto)* |
+
+`Environment name` resta vuoto perché il workflow non dichiara nessun
+`environment:`. Se un giorno gliene si dà uno — è il modo di chiedere
+un'approvazione umana prima del push su PyPI — quel campo va compilato con lo
+stesso nome, e i due devono restare d'accordo.
+
+Su **TestPyPI** la procedura è identica, sul sito `test.pypi.org`, con gli
+stessi quattro valori: sono due indici diversi e ciascuno tiene la sua lista.
+
+Finché quei campi non ci sono, il workflow **fallisce** al passo di publish con
+un errore di PyPI che dice che il publisher non è configurato — che è il modo
+giusto di fallire.
+
+### Il cancello
+
+Dopo ogni rilascio in produzione il workflow interroga l'indice:
+
+```bash
+./scripts/verifica-provenance.sh 1.6.0.dev19
+```
+
+Un publish riuscito senza provenance è un publish che ha fatto metà del lavoro
+e lo dichiara riuscito. Lo script distingue i due guasti — l'attestazione che
+**manca** e quella che nomina un **altro repository**, che è il più grave dei
+due perché sembra una garanzia — e si può lanciare a mano su qualunque versione
+già pubblicata, inclusa una di un altro progetto:
+
+```bash
+PACCHETTO=sigstore GITHUB_REPOSITORY=sigstore/sigstore-python \
+  ./scripts/verifica-provenance.sh 4.5.0
+```
+
 ## 📄 License
 
 This project is licensed under the **GNU General Public License v3.0** - see the [LICENSE](LICENSE) file for details.
@@ -325,7 +395,7 @@ If you use s3dgraphy in your research, please cite:
   title={s3dgraphy: 3D Stratigraphic Graph Management Library},
   author={Demetrescu, Emanuel},
   year={2026},
-  url={https://github.com/zalmoxes-laran/s3dgraphy},
+  url={https://github.com/ExtendedMatrix/s3Dgraphy},
   version={1.6.0},
   institution={CNR-ISPC (National Research Council - Institute of Heritage Science)}
 }
@@ -341,11 +411,11 @@ If you use s3dgraphy in your research, please cite:
 
 ## 🔗 Links
 
-- **GitHub Repository**: https://github.com/zalmoxes-laran/s3dgraphy
+- **GitHub Repository**: https://github.com/ExtendedMatrix/s3Dgraphy
 - **PyPI Package**: https://pypi.org/project/s3dgraphy/
 - **Documentation**: https://docs.extendedmatrix.org/projects/s3dgraphy/
 - **Extended Matrix Website**: https://www.extendedmatrix.org
-- **Bug Reports**: https://github.com/zalmoxes-laran/s3dgraphy/issues
+- **Bug Reports**: https://github.com/ExtendedMatrix/s3Dgraphy/issues
 
 ---
 

{s3dgraphy-1.6.0.dev19 → s3dgraphy-1.6.0.dev21}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "s3dgraphy"
-version = "1.6.0.dev19"
+version = "1.6.0.dev21"
 description = "3D Stratigraphic Graph Management Library for archaeological and heritage applications"
 readme = "README.md"
 requires-python = ">=3.9"
@@ -60,13 +60,13 @@ dependencies = [
 ]
 
 [project.urls]
-Homepage = "https://github.com/zalmoxes-laran/s3dgraphy"
+Homepage = "https://github.com/ExtendedMatrix/s3Dgraphy"
 Documentation = "https://docs.extendedmatrix.org/projects/s3dgraphy/"
-Repository = "https://github.com/zalmoxes-laran/s3dgraphy.git"
-"Bug Reports" = "https://github.com/zalmoxes-laran/s3dgraphy/issues"
-"Source Code" = "https://github.com/zalmoxes-laran/s3dgraphy"
+Repository = "https://github.com/ExtendedMatrix/s3Dgraphy.git"
+"Bug Reports" = "https://github.com/ExtendedMatrix/s3Dgraphy/issues"
+"Source Code" = "https://github.com/ExtendedMatrix/s3Dgraphy"
 "Extended Matrix" = "https://www.extendedmatrix.org"
-Changelog = "https://github.com/zalmoxes-laran/s3dgraphy/blob/main/CHANGELOG.md"
+Changelog = "https://github.com/ExtendedMatrix/s3Dgraphy/blob/main/CHANGELOG.md"
 
 # ─────────────────────────────────────────────────────────────────────────
 # Optional features — pip install s3dgraphy[<extra>]
@@ -104,12 +104,12 @@ sync = [
     # ingestion + projection between a Graph and the host application's
     # SQL tables. SQLite works out of the box; add the [postgres] extra
     # for the PostgreSQL backend. Moved from pyArchInit in 1.6.0
-    # (zalmoxes-laran/s3Dgraphy#10).
+    # (ExtendedMatrix/s3Dgraphy#10).
     "sqlalchemy>=2.0",
 ]
 postgres = [
     # PostgreSQL backend driver. Combine with [sync] for the SQL bridge
-    # (zalmoxes-laran/s3Dgraphy#9 + #10). Standalone, it also enables
+    # (ExtendedMatrix/s3Dgraphy#9 + #10). Standalone, it also enables
     # the PG path of PyArchInitImporter when that lands.
     "psycopg2-binary>=2.9",
 ]

{s3dgraphy-1.6.0.dev19 → s3dgraphy-1.6.0.dev21}/src/s3dgraphy/JSON_config/datamodel_translations.json

@@ -842,7 +842,7 @@
   },
   "SpecialFindUnit": {
    "description": {
-    "en": "Movable physical object whose ORIGINAL position is unknown (and sometimes whose pertinence to the site is uncertain). Distinct from in-situ artefacts — known to exist(ed) but displaced. Architectural artefacts, coins, fragments without findspot. Provenance / pertinence uncertainty is captured via paradata edges, not by class.",
+    "en": "Movable physical object whose ORIGINAL position is unknown (and sometimes whose pertinence to the site is uncertain). Distinct from in-situ artefacts — known to exist(ed) but displaced. Architectural artefacts, coins, fragments without findspot. This is also the unit for a REDEPOSITED object: a block in secondary deposition found inside a layer, which is observed where it lies but not where it was made to lie. Provenance / pertinence uncertainty is captured via paradata edges, not by class.",
     "validated_it": false,
     "validated_el": false,
     "validated_he": false,

{s3dgraphy-1.6.0.dev19 → s3dgraphy-1.6.0.dev21}/src/s3dgraphy/JSON_config/em.ttl

@@ -13,7 +13,7 @@
 @prefix xsd:       <http://www.w3.org/2001/XMLSchema#> .
 
 # ============================================================================
-# Extended Matrix (EM) Ontology — v1.6.2
+# Extended Matrix (EM) Ontology — v1.6.5
 # ============================================================================
 # Formal extension of the CIDOC-CRM family + HDT-O for the Extended Matrix
 # stratigraphic + paradata + virtual-reconstruction modeling. Companion to
@@ -44,8 +44,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.2" ;
-    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."@en ;
+    owl:versionInfo "1.6.5" ;
+    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)."@en ;
     owl:imports <http://www.cidoc-crm.org/cidoc-crm/> ,
                 <http://www.cidoc-crm.org/extensions/crminf/> ,
                 <http://www.cidoc-crm.org/extensions/crmarchaeo/> ,
@@ -717,6 +717,35 @@ em:isInActivity
     rdfs:range crm:E7_Activity ;
     rdfs:comment "An entity of any kind — a stratigraphic unit, a quale, a document, an extractor, a whole paradata group — is CLASSIFIED UNDER an activity-shaped grouping. This is the axis of INTENTION in the Extended Matrix, orthogonal to space (is_in_location) and to time (the epoch edges), and it is a curatorial grouping and not an event anyone attended. NO SUPERPROPERTY, deliberately, and the reason is the whole justification for the term: CIDOC can say that an actor PARTICIPATED in an event (P11i), that a thing WAS PRESENT (P12i), that an object WAS USED (P16i) — but it cannot say that an arbitrary entity is classified under an activity. P12i would even pass the type check, because E28 Conceptual Object reaches E77 through E71/E70, but it would be false: a PropertyNode attended nothing. P9i needs an E4 Period in the subject and the sources here are not periods; P129i needs an E89 in the object and E7 Activity is not one. Verified against CIDOC CRM 7.1.3 and CRMarchaeo 2.1.1: CRMarchaeo has specific archaeological activities (A9, A1, A6) but no generic activity class and none of its 32 AP properties expresses membership in one. The CLASS is not ours — crm:E7_Activity is CIDOC core and ActivityNodeGroup stays mapped to it — only the property is. NAMED isInActivity and NOT participatedInActivity (the dead CIDOC-S3D desideratum it replaces), because participation is a claim this model does not make. Maps to: connections_datamodel edge 'is_in_activity' (sources StratigraphicNode/ParadataNode/ParadataNodeGroup/DocumentNode/ExtractorNode/CombinerNode/PropertyNode, target ActivityNodeGroup); mapping.cidoc stays EMPTY on purpose, and the exporter emits this property on its own."@en .
 
+em:belongsToAlternative
+    a owl:ObjectProperty ;
+    rdfs:label "belongs to alternative"@en ;
+    rdfs:domain crm:E1_CRM_Entity ;
+    rdfs:range em:TimeBranch ;
+    rdfs:subPropertyOf crminf:J28i_is_referred_to_in ;
+    rdfs:comment "An entity belongs to one alternative reconstruction scenario rather than another. UNLIKE em:contrastsWith and em:isInActivity this term HAS an honest ceiling: CRMinf does cover membership in a set of propositions (J28/J28i, and since 1.2 the I17 pattern with J30/J31/J32), so the extension NARROWS here instead of widening. What it adds beneath that ceiling is the identity of the scenario as an addressable thing, which the bare membership property does not carry: a reader must be able to ask which units belong to scenario B, not merely that they are referred to somewhere. Maps to: connections_datamodel edges is_in_timebranch (source StratigraphicNode, target TimeBranchNodeGroup) and the deprecated has_timebranch. Replaces the dead desideratum CIDOC-S3D:belongsToAlternative, which named the same thing under a prefix that resolved to nothing."@en .
+
+em:hasSemanticShape
+    a owl:ObjectProperty ;
+    rdfs:label "has semantic shape"@en ;
+    rdfs:domain crm:E1_CRM_Entity ;
+    rdfs:range em:SemanticShape ;
+    rdfs:comment "An entity is represented, for the purpose of spatial reasoning, by a simplified geometry that STANDS FOR it — a convex hull, a sphere, a proximity volume — as distinct from a geometry that measures it. The two answer different questions: a measured geometry says where the unit was found, a semantic shape says how it is to be reasoned about spatially when its true shape is unknown, irrelevant, or argued. NO SUPERPROPERTY: crmgeo places (SP5 and its neighbourhood) express a place expression, not a schematic stand-in, and since the proxy-as-property change of v1.6.10 the source of this relation includes a PropertyNode — a quale does not occupy a place, so a place-valued property would be false as well as imprecise. The CLASS is ours (em:SemanticShape, itself declared beneath crm:E73_Information_Object) because the stand-in is an information object and not a physical extent. Maps to: connections_datamodel edge has_semantic_shape (source Node, target SemanticShapeNode). Replaces the dead desideratum CIDOC-S3D:hasSymbolicSpatialRepresentation."@en .
+
+# ============================================================================
+# 13. NODE ELEMENTS — CRMem v1.6.5 (2026-10-20)
+#     Decided by E.D. on 2026-09-27: the definition of a unit is an ELEMENT
+#     OF THE NODE, like name and description — not a qualia.
+# ============================================================================
+
+em:hasDefinition
+    a owl:ObjectProperty ;
+    rdfs:label "has definition"@en ;
+    rdfs:subPropertyOf crm:P2_has_type ;
+    rdfs:domain crmarchaeo:A8_Stratigraphic_Unit ;
+    rdfs:range crm:E55_Type ;
+    rdfs:comment "The DEFINITION of a stratigraphic unit — strato di crollo, riempimento, taglio: the DEFINIZIONE box of the US sheet — as a concept of a controlled vocabulary (a SKOS concept, typed crm:E55_Type). It is a TYPE of the unit and nothing more, which is why it narrows crm:P2_has_type rather than widening anything: every em:hasDefinition triple IS a P2_has_type triple, and a CIDOC-only consumer reading the entailment loses nothing. What the subproperty adds is the ability to tell, in SPARQL, the definition from any other type a unit may carry. NOT EMITTED BY DEFAULT: the exporter writes crm:P2_has_type directly (node datamodel StratigraphicNode.properties.definition.rdf.with_concept), because an unreasoned store would otherwise not see the P2 edge at all; the switch is one line in that entry. A definition that carries only a label and no concept URI projects to nothing (rdf.label_only = null): a word is not a concept. Maps to: node_datamodel StratigraphicNode.properties.definition (em.json data.definition), inherited by every stratigraphic subtype."@en .
+
 # ============================================================================
-# End of em.ttl v1.6.3
+# End of em.ttl v1.6.5
 # ============================================================================

{s3dgraphy-1.6.0.dev19 → s3dgraphy-1.6.0.dev21}/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.5",
+ "s3Dgraphy_data_model_version": "1.6.9",
  "node_types": {
   "ActivityNodeGroup": {
    "parent": "GroupNode",
@@ -194,7 +194,7 @@
   },
   "RepresentationNode": {
    "parent": "Node",
-   "node_type": "representation_node",
+   "node_type": null,
    "description": "Base class for all representation nodes in 3D space."
   },
   "ResourceNode": {