Summary
SpatialDDS manifests (anchors, content, services) specify discovery fields like schema, zone_id, and runtime topics, but they lack direct links to well‑known digital‑twin vocabularies. Adding optional annotations or manifest hints that reference Digital Twins Definition Language (DTDL) or Asset Administration Shell (AAS) models could make SpatialDDS assets easier to integrate with larger digital‑twin ecosystems.
Justification
- Interoperability – DTDL and AAS provide standardized semantics for digital assets. Referencing them from SpatialDDS would facilitate data exchange and lifecycle management across platforms.
- Discoverability – Clients could query manifests or data structures using twin identifiers (e.g., dtmi:com:example:Anchor;1) and easily locate associated twin metadata.
- Incremental adoption – Keeping these hints optional allows existing workflows to remain lightweight while offering a clear migration path for projects already using digital twins.
Options
- IDL-level annotations
- Embed digital‑twin references directly into IDL structures with attributes such as @dtdl, @aas_submodel, and per-field @dtdl_path to enable stronger semantic mapping.
- Manifest-level hints
- Add optional keys like dtmi, aas_submodel, or digital_twin_id to existing manifest schemas so resources can reference twin models without changing IDL types.
- Hybrid approach
- Use IDL annotations for core datatypes needing strict semantics and manifest hints for higher‑level assets or incremental adoption, clarifying best practices in documentation.
Summary
SpatialDDS manifests (anchors, content, services) specify discovery fields like schema, zone_id, and runtime topics, but they lack direct links to well‑known digital‑twin vocabularies. Adding optional annotations or manifest hints that reference Digital Twins Definition Language (DTDL) or Asset Administration Shell (AAS) models could make SpatialDDS assets easier to integrate with larger digital‑twin ecosystems.
Justification
Options