PyPI - spatialdds - Versions diffs - 0.8.0__tar.gz → 0.8.1__tar.gz - Mend

spatialdds 0.8.0tar.gz → 0.8.1tar.gz

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (246) hide show

{spatialdds-0.8.0 → spatialdds-0.8.1}/PKG-INFO RENAMED Viewed

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: spatialdds
-Version: 0.8.0
+Version: 0.8.1
 Summary: SpatialDDS for programs: a client for the web binding (Appendix N), a native DDS participant, and the reference registry behind one command.
 Author: Open AR Cloud
 License: Apache-2.0

{spatialdds-0.8.0 → spatialdds-0.8.1}/pyproject.toml RENAMED Viewed

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 [project]
 name = "spatialdds"
-version = "0.8.0"
+version = "0.8.1"
 description = "SpatialDDS for programs: a client for the web binding (Appendix N), a native DDS participant, and the reference registry behind one command."
 readme = "README.md"
 requires-python = ">=3.9"

{spatialdds-0.8.0 → spatialdds-0.8.1}/spatialdds/__init__.py RENAMED Viewed

@@ -41,7 +41,7 @@ __all__ = [
     "participant", "MissingExtra", "dds", "events", "frames", "Recency",
 ]
-__version__ = "0.8.0"
+__version__ = "0.8.1"
 #: The SpatialDDS-spec commit whose Appendix N and generated artifacts this
 #: package implements. Package versions and specification versions move
 #: independently; this is the one that says what the wire looks like.

{spatialdds-0.8.0 → spatialdds-0.8.1}/spatialdds/artifacts/openapi.html RENAMED Viewed

@@ -14,4 +14,4 @@ border-bottom:1px solid var(--line)}p{margin:.35rem 0}.mut,.sum .auth{color:
 var(--mut)}.auth{font-size:.85rem;margin-left:.4rem}.v{display:inline-block;
 min-width:4.2rem;font:600 12px ui-monospace,monospace;letter-spacing:.04em;
 color:var(--acc)}.codes{font:12px ui-monospace,monospace;color:var(--mut)}
-.s{margin-right:.5rem}.s4,.s5{color:#b5482c}a{color:var(--acc)}</style></head><body><main><h1>SpatialDDS web binding (spatialdds-py)</h1><p class=mut>Version 0.8.0 · OpenAPI 3.1.0 · generated, never hand-written · <a href='openapi'>openapi.yaml</a></p><p>Generated by <code>tools/gen_openapi.py</code> from the gateway&#x27;s own tables and the published JSON Schemas; never edited by hand. Reads are open; writes take a bearer token scoped to scenes. The WebSocket streams (N.5) are described on each collection path, not modelled. A deployment&#x27;s own keyed types (<code>serve --extension</code>) are publishable on their own collection paths, under the same rules as the entity lane when they carry <code>basis</code>, <code>state</code>, <code>state_reason</code> and <code>stamp</code>; a type that names an <code>asserter</code> has it stamped or verified as the bearer token&#x27;s principal (<code>asserter-not-principal</code>, <code>asserter-ungrounded</code>). Their paths are not listed here, because the deployment chooses them.</p><h2>Operations</h2><section id="search"><h3><span class="v get">GET</span> <code>/.well-known/spatialdds/search</code></h3><p class="sum">Services near a geohash (§8.2.3 manifests) <span class="auth">open</span></p><p class="codes"><span class="s s2">200</span> <span class="s s4">429</span></p></section><section id="searchPost"><h3><span class="v post">POST</span> <code>/.well-known/spatialdds/search</code></h3><p class="sum">The same search, as a POST body <span class="auth">open</span></p><p class="codes"><span class="s s2">200</span> <span class="s s4">429</span> <span class="s s4">413</span> <span class="s s4">415</span></p></section><section id="listSchemas"><h3><span class="v get">GET</span> <code>/.well-known/spatialdds/schemas</code></h3><p class="sum">The published JSON Schemas, by type <span class="auth">open</span></p><p class="codes"><span class="s s2">200</span> <span class="s s4">429</span></p></section><section id="getSchema"><h3><span class="v get">GET</span> <code>/.well-known/spatialdds/schemas/{type}</code></h3><p class="sum"> <span class="auth">open</span></p><p class="codes"><span class="s s2">200</span> <span class="s s4">404</span> <span class="s s4">429</span></p></section><section id="bootstrap"><h3><span class="v get">GET</span> <code>/.well-known/spatialdds/bootstrap</code></h3><p class="sum">DDS-join material (N.2); optional <span class="auth">open</span></p><p class="codes"><span class="s s2">200</span> <span class="s s4">404</span> <span class="s s4">429</span></p></section><section id="resolverMetadata"><h3><span class="v get">GET</span> <code>/.well-known/spatialdds/resolver</code></h3><p class="sum">§7.5.2 resolver metadata <span class="auth">open</span></p><p class="codes"><span class="s s2">200</span> <span class="s s4">404</span> <span class="s s4">429</span></p></section><section id="openapi"><h3><span class="v get">GET</span> <code>/.well-known/spatialdds/openapi</code></h3><p class="sum">This document <span class="auth">open</span></p><p class="codes"><span class="s s2">200</span> <span class="s s4">429</span></p></section><section id="openapiPage"><h3><span class="v get">GET</span> <code>/.well-known/spatialdds/openapi.html</code></h3><p class="sum">This document as a static reference page <span class="auth">open</span></p><p class="codes"><span class="s s2">200</span> <span class="s s4">429</span></p></section><section id="resolve"><h3><span class="v get">GET</span> <code>/spatialdds/resolve</code></h3><p class="sum">Resolve a URI to its manifest (§7.5.2) <span class="auth">open</span></p><p class="codes"><span class="s s2">200</span> <span class="s s4">400</span> <span class="s s4">404</span> <span class="s s4">429</span></p></section><section id="putManifest"><h3><span class="v put">PUT</span> <code>/spatialdds/resolve</code></h3><p class="sum">Publish a manifest, keyed by its own <code>id</code> <span class="auth">token</span></p><p>The <code>uri</code> parameter is not used; the body&#x27;s <code>id</code> is the key. Its scene segment is the lane. **Writes are per lane.** The path&#x27;s first segment is the scene; the bearer token must be granted it (<code>tenancy.WRITE_REFUSALS</code>).</p><p class="codes"><span class="s s2">200</span> <span class="s s2">201</span> <span class="s s4">400</span> <span class="s s4">401</span> <span class="s s4">403</span> <span class="s s4">405</span> <span class="s s4">429</span> <span class="s s4">413</span> <span class="s s4">415</span> <span class="s s5">503</span></p></section><section id="withdrawManifest"><h3><span class="v delete">DELETE</span> <code>/spatialdds/resolve</code></h3><p class="sum">Withdraw a manifest; <code>resolve</code> then answers 404 <span class="auth">token</span></p><p>Owner-checked by the URI&#x27;s scene segment. **Writes are per lane.** The path&#x27;s first segment is the scene; the bearer token must be granted it (<code>tenancy.WRITE_REFUSALS</code>).</p><p class="codes"><span class="s s2">204</span> <span class="s s4">400</span> <span class="s s4">401</span> <span class="s s4">403</span> <span class="s s4">404</span> <span class="s s4">405</span> <span class="s s4">429</span> <span class="s s5">503</span></p></section><section id="getAsset"><h3><span class="v get">GET</span> <code>/assets/{name}</code></h3><p class="sum">Asset bytes this endpoint hosts (implementation-defined) <span class="auth">open</span></p><p class="codes"><span class="s s2">200</span> <span class="s s4">404</span> <span class="s s4">429</span></p></section><section id="listAnnounce"><h3><span class="v get">GET</span> <code>/{scene}/{stream}/announce/v1</code></h3><p class="sum">Every spatial.disco.Announce instance in the latched set <span class="auth">open</span></p><p>**The same URL is also a WebSocket** (N.5): connect with <code>wss://</code> and receive the latched set as <code>sample</code> events, exactly one <code>end_of_replay</code> carrying the replay count, then live <code>sample</code> and <code>dispose</code> events (<code>{event, topic, key, data | reason}</code>). Not modelled here; see [Appendix N.5](https://spatialdds.org/v1.8/appendix-n/).</p><p class="codes"><span class="s s2">200</span> <span class="s s3">304</span> <span class="s s4">404</span> <span class="s s4">429</span> <span class="s s5">503</span></p></section><section id="commandAnnounce"><h3><span class="v post">POST</span> <code>/{scene}/{stream}/announce/v1</code></h3><p class="sum">An N.6 command addressed through the announce lane <span class="auth">token</span></p><p>Accepted only on a lane whose topic advertises <code>accepts_commands</code>; otherwise <code>405</code>. **Writes are per lane.** The path&#x27;s first segment is the scene; the bearer token must be granted it (<code>tenancy.WRITE_REFUSALS</code>). Every member of the record is required: a body is a whole record, never a patch.</p><p class="codes"><span class="s s2">202</span> <span class="s s4">400</span> <span class="s s4">401</span> <span class="s s4">403</span> <span class="s s4">405</span> <span class="s s4">409</span> <span class="s s4">429</span> <span class="s s4">413</span> <span class="s s4">415</span></p></section><section id="getAnnounce"><h3><span class="v get">GET</span> <code>/{scene}/{stream}/announce/v1/{key}</code></h3><p class="sum">One spatial.disco.Announce instance <span class="auth">open</span></p><p class="codes"><span class="s s2">200</span> <span class="s s3">304</span> <span class="s s4">404</span> <span class="s s4">429</span></p></section><section id="putAnnounce"><h3><span class="v put">PUT</span> <code>/{scene}/{stream}/announce/v1/{key}</code></h3><p class="sum">Publish or replace a spatial.disco.Announce <span class="auth">token</span></p><p>**Writes are per lane.** The path&#x27;s first segment is the scene; the bearer token must be granted it (<code>tenancy.WRITE_REFUSALS</code>). Every member of the record is required: a body is a whole record, never a patch. The body&#x27;s key must equal the URL&#x27;s. <code>If-Match</code> is honoured when present.</p><p class="codes"><span class="s s2">200</span> <span class="s s2">201</span> <span class="s s4">400</span> <span class="s s4">401</span> <span class="s s4">403</span> <span class="s s4">405</span> <span class="s s4">412</span> <span class="s s4">429</span> <span class="s s4">413</span> <span class="s s4">415</span> <span class="s s5">503</span></p></section><section id="withdrawAnnounce"><h3><span class="v delete">DELETE</span> <code>/{scene}/{stream}/announce/v1/{key}</code></h3><p class="sum">Withdraw (dispose) a spatial.disco.Announce <span class="auth">token</span></p><p>**Writes are per lane.** The path&#x27;s first segment is the scene; the bearer token must be granted it (<code>tenancy.WRITE_REFUSALS</code>). The dispose streams on the collection&#x27;s WebSocket with its <code>reason</code>.</p><p class="codes"><span class="s s2">204</span> <span class="s s4">400</span> <span class="s s4">401</span> <span class="s s4">403</span> <span class="s s4">404</span> <span class="s s4">405</span> <span class="s s4">429</span> <span class="s s5">503</span></p></section><section id="listContentAnnounce"><h3><span class="v get">GET</span> <code>/{scene}/{stream}/content_announce/v1</code></h3><p class="sum">Every spatial.disco.ContentAnnounce instance in the latched set <span class="auth">open</span></p><p>**The same URL is also a WebSocket** (N.5): connect with <code>wss://</code> and receive the latched set as <code>sample</code> events, exactly one <code>end_of_replay</code> carrying the replay count, then live <code>sample</code> and <code>dispose</code> events (<code>{event, topic, key, data | reason}</code>). Not modelled here; see [Appendix N.5](https://spatialdds.org/v1.8/appendix-n/).</p><p class="codes"><span class="s s2">200</span> <span class="s s3">304</span> <span class="s s4">404</span> <span class="s s4">429</span> <span class="s s5">503</span></p></section><section id="commandContentAnnounce"><h3><span class="v post">POST</span> <code>/{scene}/{stream}/content_announce/v1</code></h3><p class="sum">An N.6 command addressed through the content_announce lane <span class="auth">token</span></p><p>Accepted only on a lane whose topic advertises <code>accepts_commands</code>; otherwise <code>405</code>. **Writes are per lane.** The path&#x27;s first segment is the scene; the bearer token must be granted it (<code>tenancy.WRITE_REFUSALS</code>). Every member of the record is required: a body is a whole record, never a patch.</p><p class="codes"><span class="s s2">202</span> <span class="s s4">400</span> <span class="s s4">401</span> <span class="s s4">403</span> <span class="s s4">405</span> <span class="s s4">409</span> <span class="s s4">429</span> <span class="s s4">413</span> <span class="s s4">415</span></p></section><section id="getContentAnnounce"><h3><span class="v get">GET</span> <code>/{scene}/{stream}/content_announce/v1/{key}</code></h3><p class="sum">One spatial.disco.ContentAnnounce instance <span class="auth">open</span></p><p class="codes"><span class="s s2">200</span> <span class="s s3">304</span> <span class="s s4">404</span> <span class="s s4">429</span></p></section><section id="putContentAnnounce"><h3><span class="v put">PUT</span> <code>/{scene}/{stream}/content_announce/v1/{key}</code></h3><p class="sum">Publish or replace a spatial.disco.ContentAnnounce <span class="auth">token</span></p><p>**Writes are per lane.** The path&#x27;s first segment is the scene; the bearer token must be granted it (<code>tenancy.WRITE_REFUSALS</code>). Every member of the record is required: a body is a whole record, never a patch. The body&#x27;s key must equal the URL&#x27;s. <code>If-Match</code> is honoured when present.</p><p class="codes"><span class="s s2">200</span> <span class="s s2">201</span> <span class="s s4">400</span> <span class="s s4">401</span> <span class="s s4">403</span> <span class="s s4">405</span> <span class="s s4">412</span> <span class="s s4">429</span> <span class="s s4">413</span> <span class="s s4">415</span> <span class="s s5">503</span></p></section><section id="withdrawContentAnnounce"><h3><span class="v delete">DELETE</span> <code>/{scene}/{stream}/content_announce/v1/{key}</code></h3><p class="sum">Withdraw (dispose) a spatial.disco.ContentAnnounce <span class="auth">token</span></p><p>**Writes are per lane.** The path&#x27;s first segment is the scene; the bearer token must be granted it (<code>tenancy.WRITE_REFUSALS</code>). The dispose streams on the collection&#x27;s WebSocket with its <code>reason</code>.</p><p class="codes"><span class="s s2">204</span> <span class="s s4">400</span> <span class="s s4">401</span> <span class="s s4">403</span> <span class="s s4">404</span> <span class="s s4">405</span> <span class="s s4">429</span> <span class="s s5">503</span></p></section><section id="listEntity"><h3><span class="v get">GET</span> <code>/{scene}/{stream}/entity/v1</code></h3><p class="sum">Every spatial.owm.Entity instance in the latched set <span class="auth">token</span></p><p>**The same URL is also a WebSocket** (N.5): connect with <code>wss://</code> and receive the latched set as <code>sample</code> events, exactly one <code>end_of_replay</code> carrying the replay count, then live <code>sample</code> and <code>dispose</code> events (<code>{event, topic, key, data | reason}</code>). Not modelled here; see [Appendix N.5](https://spatialdds.org/v1.8/appendix-n/).</p><p class="codes"><span class="s s2">200</span> <span class="s s3">304</span> <span class="s s4">404</span> <span class="s s4">429</span> <span class="s s5">503</span></p></section><section id="commandEntity"><h3><span class="v post">POST</span> <code>/{scene}/{stream}/entity/v1</code></h3><p class="sum">An N.6 command addressed through the entity lane <span class="auth">token</span></p><p>Accepted only on a lane whose topic advertises <code>accepts_commands</code>; otherwise <code>405</code>. **Writes are per lane.** The path&#x27;s first segment is the scene; the bearer token must be granted it (<code>tenancy.WRITE_REFUSALS</code>). Every member of the record is required: a body is a whole record, never a patch.</p><p class="codes"><span class="s s2">202</span> <span class="s s4">400</span> <span class="s s4">401</span> <span class="s s4">403</span> <span class="s s4">405</span> <span class="s s4">409</span> <span class="s s4">429</span> <span class="s s4">413</span> <span class="s s4">415</span></p></section><section id="getEntity"><h3><span class="v get">GET</span> <code>/{scene}/{stream}/entity/v1/{key}</code></h3><p class="sum">One spatial.owm.Entity instance <span class="auth">token</span></p><p class="codes"><span class="s s2">200</span> <span class="s s3">304</span> <span class="s s4">404</span> <span class="s s4">429</span></p></section><section id="putEntity"><h3><span class="v put">PUT</span> <code>/{scene}/{stream}/entity/v1/{key}</code></h3><p class="sum">Publish or replace a spatial.owm.Entity <span class="auth">token</span></p><p>**Writes are per lane.** The path&#x27;s first segment is the scene; the bearer token must be granted it (<code>tenancy.WRITE_REFUSALS</code>). Every member of the record is required: a body is a whole record, never a patch. The body&#x27;s key must equal the URL&#x27;s. <code>If-Match</code> is honoured when present. **Basis gates liveliness.** A DECLARED or AUTHORED body is a declaration and holds until withdrawn; it takes no <code>refresh</code>. An DERIVED or OBSERVED body must declare <code>refresh</code>, and be PUT again within it; when it lapses the gateway withdraws the instance itself, a terminal sample (RETIRED) then the dispose, both with the reason <code>refresh lapsed</code>. On a gateway with a DDS domain the instance is written there too, from the gateway&#x27;s own participant.</p><p class="codes"><span class="s s2">200</span> <span class="s s2">201</span> <span class="s s4">400</span> <span class="s s4">401</span> <span class="s s4">403</span> <span class="s s4">405</span> <span class="s s4">412</span> <span class="s s5">503</span> <span class="s s4">429</span> <span class="s s4">413</span> <span class="s s4">415</span></p></section><section id="withdrawEntity"><h3><span class="v delete">DELETE</span> <code>/{scene}/{stream}/entity/v1/{key}</code></h3><p class="sum">Withdraw (dispose) a spatial.owm.Entity <span class="auth">token</span></p><p>**Writes are per lane.** The path&#x27;s first segment is the scene; the bearer token must be granted it (<code>tenancy.WRITE_REFUSALS</code>). A terminal sample (RETIRED, with the reason) streams first, then the dispose with its <code>reason</code>, on the collection&#x27;s WebSocket and, on a gateway with a DDS domain, on the bus.</p><p class="codes"><span class="s s2">204</span> <span class="s s4">400</span> <span class="s s4">401</span> <span class="s s4">403</span> <span class="s s4">404</span> <span class="s s4">405</span> <span class="s s4">429</span> <span class="s s5">503</span></p></section><section id="listGeoAnchor"><h3><span class="v get">GET</span> <code>/{scene}/{stream}/geo_anchor/v1</code></h3><p class="sum">Every spatial.core.GeoAnchor instance in the latched set <span class="auth">open</span></p><p>**The same URL is also a WebSocket** (N.5): connect with <code>wss://</code> and receive the latched set as <code>sample</code> events, exactly one <code>end_of_replay</code> carrying the replay count, then live <code>sample</code> and <code>dispose</code> events (<code>{event, topic, key, data | reason}</code>). Not modelled here; see [Appendix N.5](https://spatialdds.org/v1.8/appendix-n/).</p><p class="codes"><span class="s s2">200</span> <span class="s s3">304</span> <span class="s s4">404</span> <span class="s s4">429</span> <span class="s s5">503</span></p></section><section id="commandGeoAnchor"><h3><span class="v post">POST</span> <code>/{scene}/{stream}/geo_anchor/v1</code></h3><p class="sum">An N.6 command addressed through the geo_anchor lane <span class="auth">token</span></p><p>Accepted only on a lane whose topic advertises <code>accepts_commands</code>; otherwise <code>405</code>. **Writes are per lane.** The path&#x27;s first segment is the scene; the bearer token must be granted it (<code>tenancy.WRITE_REFUSALS</code>). Every member of the record is required: a body is a whole record, never a patch.</p><p class="codes"><span class="s s2">202</span> <span class="s s4">400</span> <span class="s s4">401</span> <span class="s s4">403</span> <span class="s s4">405</span> <span class="s s4">409</span> <span class="s s4">429</span> <span class="s s4">413</span> <span class="s s4">415</span></p></section><section id="getGeoAnchor"><h3><span class="v get">GET</span> <code>/{scene}/{stream}/geo_anchor/v1/{key}</code></h3><p class="sum">One spatial.core.GeoAnchor instance <span class="auth">open</span></p><p class="codes"><span class="s s2">200</span> <span class="s s3">304</span> <span class="s s4">404</span> <span class="s s4">429</span></p></section><section id="putGeoAnchor"><h3><span class="v put">PUT</span> <code>/{scene}/{stream}/geo_anchor/v1/{key}</code></h3><p class="sum">Publish or replace a spatial.core.GeoAnchor <span class="auth">token</span></p><p>**Writes are per lane.** The path&#x27;s first segment is the scene; the bearer token must be granted it (<code>tenancy.WRITE_REFUSALS</code>). Every member of the record is required: a body is a whole record, never a patch. The body&#x27;s key must equal the URL&#x27;s. <code>If-Match</code> is honoured when present.</p><p class="codes"><span class="s s2">200</span> <span class="s s2">201</span> <span class="s s4">400</span> <span class="s s4">401</span> <span class="s s4">403</span> <span class="s s4">405</span> <span class="s s4">412</span> <span class="s s4">429</span> <span class="s s4">413</span> <span class="s s4">415</span> <span class="s s5">503</span></p></section><section id="withdrawGeoAnchor"><h3><span class="v delete">DELETE</span> <code>/{scene}/{stream}/geo_anchor/v1/{key}</code></h3><p class="sum">Withdraw (dispose) a spatial.core.GeoAnchor <span class="auth">token</span></p><p>**Writes are per lane.** The path&#x27;s first segment is the scene; the bearer token must be granted it (<code>tenancy.WRITE_REFUSALS</code>). The dispose streams on the collection&#x27;s WebSocket with its <code>reason</code>.</p><p class="codes"><span class="s s2">204</span> <span class="s s4">400</span> <span class="s s4">401</span> <span class="s s4">403</span> <span class="s s4">404</span> <span class="s s4">405</span> <span class="s s4">429</span> <span class="s s5">503</span></p></section><section id="listInstances"><h3><span class="v get">GET</span> <code>/{scene}/{stream}/{type}/{version}</code></h3><p class="sum">Any other served topic, read-only <span class="auth">token for operator-scoped</span></p><p>Latched types answer with the latched set; streamed types with the replayed window. Public or operator-scoped per the type: <code>spatial.core.FrameTransform</code> latched public, <code>spatial.events.CrossingLine</code> latched public, <code>spatial.events.SpatialEvent</code> stream bearer, <code>spatial.events.SpatialZone</code> latched public, <code>spatial.owm.ModelPose</code> stream bearer, <code>spatial.semantics.Detection2DSet</code> stream bearer, <code>spatial.semantics.Detection3DSet</code> stream bearer, <code>spatial.semantics.FusedTrackSet</code> stream bearer. **The same URL is also a WebSocket** (N.5): connect with <code>wss://</code> and receive the latched set as <code>sample</code> events, exactly one <code>end_of_replay</code> carrying the replay count, then live <code>sample</code> and <code>dispose</code> events (<code>{event, topic, key, data | reason}</code>). Not modelled here; see [Appendix N.5](https://spatialdds.org/v1.8/appendix-n/).</p><p class="codes"><span class="s s2">200</span> <span class="s s3">304</span> <span class="s s4">401</span> <span class="s s4">404</span> <span class="s s4">429</span> <span class="s s5">503</span></p></section><section id="listWellKnownInstances"><h3><span class="v get">GET</span> <code>/.well-known/spatialdds/{stream}/{type}/{version}</code></h3><p class="sum">A four-segment topic&#x27;s collection <span class="auth">token for operator-scoped</span></p><p>A four-segment topic (<code>spatialdds/&lt;stream&gt;/&lt;type&gt;/&lt;version&gt;</code>, no scene), such as the discovery announce lane, served exactly as a scene-scoped collection is: latched set, <code>ETag</code>, <code>304</code>, the same access classes, and the N.5 stream by upgrading the same path. Read-only: a topic with no scene is in no lane. **The same URL is also a WebSocket** (N.5): connect with <code>wss://</code> and receive the latched set as <code>sample</code> events, exactly one <code>end_of_replay</code> carrying the replay count, then live <code>sample</code> and <code>dispose</code> events (<code>{event, topic, key, data | reason}</code>). Not modelled here; see [Appendix N.5](https://spatialdds.org/v1.8/appendix-n/).</p><p class="codes"><span class="s s2">200</span> <span class="s s3">304</span> <span class="s s4">401</span> <span class="s s4">404</span> <span class="s s4">429</span> <span class="s s5">503</span></p></section><section id="getWellKnownInstance"><h3><span class="v get">GET</span> <code>/.well-known/spatialdds/{stream}/{type}/{version}/{key}</code></h3><p class="sum">One instance of a four-segment topic <span class="auth">token for operator-scoped</span></p><p>A four-segment topic (<code>spatialdds/&lt;stream&gt;/&lt;type&gt;/&lt;version&gt;</code>, no scene), such as the discovery announce lane, served exactly as a scene-scoped collection is: latched set, <code>ETag</code>, <code>304</code>, the same access classes, and the N.5 stream by upgrading the same path. Read-only: a topic with no scene is in no lane. </p><p class="codes"><span class="s s2">200</span> <span class="s s3">304</span> <span class="s s4">401</span> <span class="s s4">404</span> <span class="s s4">429</span> <span class="s s5">503</span></p></section><h2>Schemas</h2><p class=mut>115 components, from the published JSON Schemas at <code>/.well-known/spatialdds/schemas</code>.</p></main></body></html>
+.s{margin-right:.5rem}.s4,.s5{color:#b5482c}a{color:var(--acc)}</style></head><body><main><h1>SpatialDDS web binding (spatialdds-py)</h1><p class=mut>Version 0.8.1 · OpenAPI 3.1.0 · generated, never hand-written · <a href='openapi'>openapi.yaml</a></p><p>Generated by <code>tools/gen_openapi.py</code> from the gateway&#x27;s own tables and the published JSON Schemas; never edited by hand. Reads are open; writes take a bearer token scoped to scenes. The WebSocket streams (N.5) are described on each collection path, not modelled. A deployment&#x27;s own keyed types (<code>serve --extension</code>) are publishable on their own collection paths, under the same rules as the entity lane when they carry <code>basis</code>, <code>state</code>, <code>state_reason</code> and <code>stamp</code>; a type that names an <code>asserter</code> has it stamped or verified as the bearer token&#x27;s principal (<code>asserter-not-principal</code>, <code>asserter-ungrounded</code>). Their paths are not listed here, because the deployment chooses them.</p><h2>Operations</h2><section id="search"><h3><span class="v get">GET</span> <code>/.well-known/spatialdds/search</code></h3><p class="sum">Services near a geohash (§8.2.3 manifests) <span class="auth">open</span></p><p class="codes"><span class="s s2">200</span> <span class="s s4">429</span></p></section><section id="searchPost"><h3><span class="v post">POST</span> <code>/.well-known/spatialdds/search</code></h3><p class="sum">The same search, as a POST body <span class="auth">open</span></p><p class="codes"><span class="s s2">200</span> <span class="s s4">429</span> <span class="s s4">413</span> <span class="s s4">415</span></p></section><section id="listSchemas"><h3><span class="v get">GET</span> <code>/.well-known/spatialdds/schemas</code></h3><p class="sum">The published JSON Schemas, by type <span class="auth">open</span></p><p class="codes"><span class="s s2">200</span> <span class="s s4">429</span></p></section><section id="getSchema"><h3><span class="v get">GET</span> <code>/.well-known/spatialdds/schemas/{type}</code></h3><p class="sum"> <span class="auth">open</span></p><p class="codes"><span class="s s2">200</span> <span class="s s4">404</span> <span class="s s4">429</span></p></section><section id="bootstrap"><h3><span class="v get">GET</span> <code>/.well-known/spatialdds/bootstrap</code></h3><p class="sum">DDS-join material (N.2); optional <span class="auth">open</span></p><p class="codes"><span class="s s2">200</span> <span class="s s4">404</span> <span class="s s4">429</span></p></section><section id="resolverMetadata"><h3><span class="v get">GET</span> <code>/.well-known/spatialdds/resolver</code></h3><p class="sum">§7.5.2 resolver metadata <span class="auth">open</span></p><p class="codes"><span class="s s2">200</span> <span class="s s4">404</span> <span class="s s4">429</span></p></section><section id="openapi"><h3><span class="v get">GET</span> <code>/.well-known/spatialdds/openapi</code></h3><p class="sum">This document <span class="auth">open</span></p><p class="codes"><span class="s s2">200</span> <span class="s s4">429</span></p></section><section id="openapiPage"><h3><span class="v get">GET</span> <code>/.well-known/spatialdds/openapi.html</code></h3><p class="sum">This document as a static reference page <span class="auth">open</span></p><p class="codes"><span class="s s2">200</span> <span class="s s4">429</span></p></section><section id="resolve"><h3><span class="v get">GET</span> <code>/spatialdds/resolve</code></h3><p class="sum">Resolve a URI to its manifest (§7.5.2) <span class="auth">open</span></p><p class="codes"><span class="s s2">200</span> <span class="s s4">400</span> <span class="s s4">404</span> <span class="s s4">429</span></p></section><section id="putManifest"><h3><span class="v put">PUT</span> <code>/spatialdds/resolve</code></h3><p class="sum">Publish a manifest, keyed by its own <code>id</code> <span class="auth">token</span></p><p>The <code>uri</code> parameter is not used; the body&#x27;s <code>id</code> is the key. Its scene segment is the lane. **Writes are per lane.** The path&#x27;s first segment is the scene; the bearer token must be granted it (<code>tenancy.WRITE_REFUSALS</code>).</p><p class="codes"><span class="s s2">200</span> <span class="s s2">201</span> <span class="s s4">400</span> <span class="s s4">401</span> <span class="s s4">403</span> <span class="s s4">405</span> <span class="s s4">429</span> <span class="s s4">413</span> <span class="s s4">415</span> <span class="s s5">503</span></p></section><section id="withdrawManifest"><h3><span class="v delete">DELETE</span> <code>/spatialdds/resolve</code></h3><p class="sum">Withdraw a manifest; <code>resolve</code> then answers 404 <span class="auth">token</span></p><p>Owner-checked by the URI&#x27;s scene segment. **Writes are per lane.** The path&#x27;s first segment is the scene; the bearer token must be granted it (<code>tenancy.WRITE_REFUSALS</code>).</p><p class="codes"><span class="s s2">204</span> <span class="s s4">400</span> <span class="s s4">401</span> <span class="s s4">403</span> <span class="s s4">404</span> <span class="s s4">405</span> <span class="s s4">429</span> <span class="s s5">503</span></p></section><section id="getAsset"><h3><span class="v get">GET</span> <code>/assets/{name}</code></h3><p class="sum">Asset bytes this endpoint hosts (implementation-defined) <span class="auth">open</span></p><p class="codes"><span class="s s2">200</span> <span class="s s4">404</span> <span class="s s4">429</span></p></section><section id="listAnnounce"><h3><span class="v get">GET</span> <code>/{scene}/{stream}/announce/v1</code></h3><p class="sum">Every spatial.disco.Announce instance in the latched set <span class="auth">open</span></p><p>**The same URL is also a WebSocket** (N.5): connect with <code>wss://</code> and receive the latched set as <code>sample</code> events, exactly one <code>end_of_replay</code> carrying the replay count, then live <code>sample</code> and <code>dispose</code> events (<code>{event, topic, key, data | reason}</code>). Not modelled here; see [Appendix N.5](https://spatialdds.org/v1.8/appendix-n/).</p><p class="codes"><span class="s s2">200</span> <span class="s s3">304</span> <span class="s s4">404</span> <span class="s s4">429</span> <span class="s s5">503</span></p></section><section id="commandAnnounce"><h3><span class="v post">POST</span> <code>/{scene}/{stream}/announce/v1</code></h3><p class="sum">An N.6 command addressed through the announce lane <span class="auth">token</span></p><p>Accepted only on a lane whose topic advertises <code>accepts_commands</code>; otherwise <code>405</code>. **Writes are per lane.** The path&#x27;s first segment is the scene; the bearer token must be granted it (<code>tenancy.WRITE_REFUSALS</code>). Every member of the record is required: a body is a whole record, never a patch.</p><p class="codes"><span class="s s2">202</span> <span class="s s4">400</span> <span class="s s4">401</span> <span class="s s4">403</span> <span class="s s4">405</span> <span class="s s4">409</span> <span class="s s4">429</span> <span class="s s4">413</span> <span class="s s4">415</span></p></section><section id="getAnnounce"><h3><span class="v get">GET</span> <code>/{scene}/{stream}/announce/v1/{key}</code></h3><p class="sum">One spatial.disco.Announce instance <span class="auth">open</span></p><p class="codes"><span class="s s2">200</span> <span class="s s3">304</span> <span class="s s4">404</span> <span class="s s4">429</span></p></section><section id="putAnnounce"><h3><span class="v put">PUT</span> <code>/{scene}/{stream}/announce/v1/{key}</code></h3><p class="sum">Publish or replace a spatial.disco.Announce <span class="auth">token</span></p><p>**Writes are per lane.** The path&#x27;s first segment is the scene; the bearer token must be granted it (<code>tenancy.WRITE_REFUSALS</code>). Every member of the record is required: a body is a whole record, never a patch. The body&#x27;s key must equal the URL&#x27;s. <code>If-Match</code> is honoured when present.</p><p class="codes"><span class="s s2">200</span> <span class="s s2">201</span> <span class="s s4">400</span> <span class="s s4">401</span> <span class="s s4">403</span> <span class="s s4">405</span> <span class="s s4">412</span> <span class="s s4">429</span> <span class="s s4">413</span> <span class="s s4">415</span> <span class="s s5">503</span></p></section><section id="withdrawAnnounce"><h3><span class="v delete">DELETE</span> <code>/{scene}/{stream}/announce/v1/{key}</code></h3><p class="sum">Withdraw (dispose) a spatial.disco.Announce <span class="auth">token</span></p><p>**Writes are per lane.** The path&#x27;s first segment is the scene; the bearer token must be granted it (<code>tenancy.WRITE_REFUSALS</code>). The dispose streams on the collection&#x27;s WebSocket with its <code>reason</code>.</p><p class="codes"><span class="s s2">204</span> <span class="s s4">400</span> <span class="s s4">401</span> <span class="s s4">403</span> <span class="s s4">404</span> <span class="s s4">405</span> <span class="s s4">429</span> <span class="s s5">503</span></p></section><section id="listContentAnnounce"><h3><span class="v get">GET</span> <code>/{scene}/{stream}/content_announce/v1</code></h3><p class="sum">Every spatial.disco.ContentAnnounce instance in the latched set <span class="auth">open</span></p><p>**The same URL is also a WebSocket** (N.5): connect with <code>wss://</code> and receive the latched set as <code>sample</code> events, exactly one <code>end_of_replay</code> carrying the replay count, then live <code>sample</code> and <code>dispose</code> events (<code>{event, topic, key, data | reason}</code>). Not modelled here; see [Appendix N.5](https://spatialdds.org/v1.8/appendix-n/).</p><p class="codes"><span class="s s2">200</span> <span class="s s3">304</span> <span class="s s4">404</span> <span class="s s4">429</span> <span class="s s5">503</span></p></section><section id="commandContentAnnounce"><h3><span class="v post">POST</span> <code>/{scene}/{stream}/content_announce/v1</code></h3><p class="sum">An N.6 command addressed through the content_announce lane <span class="auth">token</span></p><p>Accepted only on a lane whose topic advertises <code>accepts_commands</code>; otherwise <code>405</code>. **Writes are per lane.** The path&#x27;s first segment is the scene; the bearer token must be granted it (<code>tenancy.WRITE_REFUSALS</code>). Every member of the record is required: a body is a whole record, never a patch.</p><p class="codes"><span class="s s2">202</span> <span class="s s4">400</span> <span class="s s4">401</span> <span class="s s4">403</span> <span class="s s4">405</span> <span class="s s4">409</span> <span class="s s4">429</span> <span class="s s4">413</span> <span class="s s4">415</span></p></section><section id="getContentAnnounce"><h3><span class="v get">GET</span> <code>/{scene}/{stream}/content_announce/v1/{key}</code></h3><p class="sum">One spatial.disco.ContentAnnounce instance <span class="auth">open</span></p><p class="codes"><span class="s s2">200</span> <span class="s s3">304</span> <span class="s s4">404</span> <span class="s s4">429</span></p></section><section id="putContentAnnounce"><h3><span class="v put">PUT</span> <code>/{scene}/{stream}/content_announce/v1/{key}</code></h3><p class="sum">Publish or replace a spatial.disco.ContentAnnounce <span class="auth">token</span></p><p>**Writes are per lane.** The path&#x27;s first segment is the scene; the bearer token must be granted it (<code>tenancy.WRITE_REFUSALS</code>). Every member of the record is required: a body is a whole record, never a patch. The body&#x27;s key must equal the URL&#x27;s. <code>If-Match</code> is honoured when present.</p><p class="codes"><span class="s s2">200</span> <span class="s s2">201</span> <span class="s s4">400</span> <span class="s s4">401</span> <span class="s s4">403</span> <span class="s s4">405</span> <span class="s s4">412</span> <span class="s s4">429</span> <span class="s s4">413</span> <span class="s s4">415</span> <span class="s s5">503</span></p></section><section id="withdrawContentAnnounce"><h3><span class="v delete">DELETE</span> <code>/{scene}/{stream}/content_announce/v1/{key}</code></h3><p class="sum">Withdraw (dispose) a spatial.disco.ContentAnnounce <span class="auth">token</span></p><p>**Writes are per lane.** The path&#x27;s first segment is the scene; the bearer token must be granted it (<code>tenancy.WRITE_REFUSALS</code>). The dispose streams on the collection&#x27;s WebSocket with its <code>reason</code>.</p><p class="codes"><span class="s s2">204</span> <span class="s s4">400</span> <span class="s s4">401</span> <span class="s s4">403</span> <span class="s s4">404</span> <span class="s s4">405</span> <span class="s s4">429</span> <span class="s s5">503</span></p></section><section id="listEntity"><h3><span class="v get">GET</span> <code>/{scene}/{stream}/entity/v1</code></h3><p class="sum">Every spatial.owm.Entity instance in the latched set <span class="auth">token</span></p><p>**The same URL is also a WebSocket** (N.5): connect with <code>wss://</code> and receive the latched set as <code>sample</code> events, exactly one <code>end_of_replay</code> carrying the replay count, then live <code>sample</code> and <code>dispose</code> events (<code>{event, topic, key, data | reason}</code>). Not modelled here; see [Appendix N.5](https://spatialdds.org/v1.8/appendix-n/).</p><p class="codes"><span class="s s2">200</span> <span class="s s3">304</span> <span class="s s4">404</span> <span class="s s4">429</span> <span class="s s5">503</span></p></section><section id="commandEntity"><h3><span class="v post">POST</span> <code>/{scene}/{stream}/entity/v1</code></h3><p class="sum">An N.6 command addressed through the entity lane <span class="auth">token</span></p><p>Accepted only on a lane whose topic advertises <code>accepts_commands</code>; otherwise <code>405</code>. **Writes are per lane.** The path&#x27;s first segment is the scene; the bearer token must be granted it (<code>tenancy.WRITE_REFUSALS</code>). Every member of the record is required: a body is a whole record, never a patch.</p><p class="codes"><span class="s s2">202</span> <span class="s s4">400</span> <span class="s s4">401</span> <span class="s s4">403</span> <span class="s s4">405</span> <span class="s s4">409</span> <span class="s s4">429</span> <span class="s s4">413</span> <span class="s s4">415</span></p></section><section id="getEntity"><h3><span class="v get">GET</span> <code>/{scene}/{stream}/entity/v1/{key}</code></h3><p class="sum">One spatial.owm.Entity instance <span class="auth">token</span></p><p class="codes"><span class="s s2">200</span> <span class="s s3">304</span> <span class="s s4">404</span> <span class="s s4">429</span></p></section><section id="putEntity"><h3><span class="v put">PUT</span> <code>/{scene}/{stream}/entity/v1/{key}</code></h3><p class="sum">Publish or replace a spatial.owm.Entity <span class="auth">token</span></p><p>**Writes are per lane.** The path&#x27;s first segment is the scene; the bearer token must be granted it (<code>tenancy.WRITE_REFUSALS</code>). Every member of the record is required: a body is a whole record, never a patch. The body&#x27;s key must equal the URL&#x27;s. <code>If-Match</code> is honoured when present. **Basis gates liveliness.** A DECLARED or AUTHORED body is a declaration and holds until withdrawn; it takes no <code>refresh</code>. An DERIVED or OBSERVED body must declare <code>refresh</code>, and be PUT again within it; when it lapses the gateway withdraws the instance itself, a terminal sample (RETIRED) then the dispose, both with the reason <code>refresh lapsed</code>. On a gateway with a DDS domain the instance is written there too, from the gateway&#x27;s own participant.</p><p class="codes"><span class="s s2">200</span> <span class="s s2">201</span> <span class="s s4">400</span> <span class="s s4">401</span> <span class="s s4">403</span> <span class="s s4">405</span> <span class="s s4">412</span> <span class="s s5">503</span> <span class="s s4">429</span> <span class="s s4">413</span> <span class="s s4">415</span></p></section><section id="withdrawEntity"><h3><span class="v delete">DELETE</span> <code>/{scene}/{stream}/entity/v1/{key}</code></h3><p class="sum">Withdraw (dispose) a spatial.owm.Entity <span class="auth">token</span></p><p>**Writes are per lane.** The path&#x27;s first segment is the scene; the bearer token must be granted it (<code>tenancy.WRITE_REFUSALS</code>). A terminal sample (RETIRED, with the reason) streams first, then the dispose with its <code>reason</code>, on the collection&#x27;s WebSocket and, on a gateway with a DDS domain, on the bus.</p><p class="codes"><span class="s s2">204</span> <span class="s s4">400</span> <span class="s s4">401</span> <span class="s s4">403</span> <span class="s s4">404</span> <span class="s s4">405</span> <span class="s s4">429</span> <span class="s s5">503</span></p></section><section id="listGeoAnchor"><h3><span class="v get">GET</span> <code>/{scene}/{stream}/geo_anchor/v1</code></h3><p class="sum">Every spatial.core.GeoAnchor instance in the latched set <span class="auth">open</span></p><p>**The same URL is also a WebSocket** (N.5): connect with <code>wss://</code> and receive the latched set as <code>sample</code> events, exactly one <code>end_of_replay</code> carrying the replay count, then live <code>sample</code> and <code>dispose</code> events (<code>{event, topic, key, data | reason}</code>). Not modelled here; see [Appendix N.5](https://spatialdds.org/v1.8/appendix-n/).</p><p class="codes"><span class="s s2">200</span> <span class="s s3">304</span> <span class="s s4">404</span> <span class="s s4">429</span> <span class="s s5">503</span></p></section><section id="commandGeoAnchor"><h3><span class="v post">POST</span> <code>/{scene}/{stream}/geo_anchor/v1</code></h3><p class="sum">An N.6 command addressed through the geo_anchor lane <span class="auth">token</span></p><p>Accepted only on a lane whose topic advertises <code>accepts_commands</code>; otherwise <code>405</code>. **Writes are per lane.** The path&#x27;s first segment is the scene; the bearer token must be granted it (<code>tenancy.WRITE_REFUSALS</code>). Every member of the record is required: a body is a whole record, never a patch.</p><p class="codes"><span class="s s2">202</span> <span class="s s4">400</span> <span class="s s4">401</span> <span class="s s4">403</span> <span class="s s4">405</span> <span class="s s4">409</span> <span class="s s4">429</span> <span class="s s4">413</span> <span class="s s4">415</span></p></section><section id="getGeoAnchor"><h3><span class="v get">GET</span> <code>/{scene}/{stream}/geo_anchor/v1/{key}</code></h3><p class="sum">One spatial.core.GeoAnchor instance <span class="auth">open</span></p><p class="codes"><span class="s s2">200</span> <span class="s s3">304</span> <span class="s s4">404</span> <span class="s s4">429</span></p></section><section id="putGeoAnchor"><h3><span class="v put">PUT</span> <code>/{scene}/{stream}/geo_anchor/v1/{key}</code></h3><p class="sum">Publish or replace a spatial.core.GeoAnchor <span class="auth">token</span></p><p>**Writes are per lane.** The path&#x27;s first segment is the scene; the bearer token must be granted it (<code>tenancy.WRITE_REFUSALS</code>). Every member of the record is required: a body is a whole record, never a patch. The body&#x27;s key must equal the URL&#x27;s. <code>If-Match</code> is honoured when present.</p><p class="codes"><span class="s s2">200</span> <span class="s s2">201</span> <span class="s s4">400</span> <span class="s s4">401</span> <span class="s s4">403</span> <span class="s s4">405</span> <span class="s s4">412</span> <span class="s s4">429</span> <span class="s s4">413</span> <span class="s s4">415</span> <span class="s s5">503</span></p></section><section id="withdrawGeoAnchor"><h3><span class="v delete">DELETE</span> <code>/{scene}/{stream}/geo_anchor/v1/{key}</code></h3><p class="sum">Withdraw (dispose) a spatial.core.GeoAnchor <span class="auth">token</span></p><p>**Writes are per lane.** The path&#x27;s first segment is the scene; the bearer token must be granted it (<code>tenancy.WRITE_REFUSALS</code>). The dispose streams on the collection&#x27;s WebSocket with its <code>reason</code>.</p><p class="codes"><span class="s s2">204</span> <span class="s s4">400</span> <span class="s s4">401</span> <span class="s s4">403</span> <span class="s s4">404</span> <span class="s s4">405</span> <span class="s s4">429</span> <span class="s s5">503</span></p></section><section id="listInstances"><h3><span class="v get">GET</span> <code>/{scene}/{stream}/{type}/{version}</code></h3><p class="sum">Any other served topic, read-only <span class="auth">token for operator-scoped</span></p><p>Latched types answer with the latched set; streamed types with the replayed window. Public or operator-scoped per the type: <code>spatial.core.FrameTransform</code> latched public, <code>spatial.events.CrossingLine</code> latched public, <code>spatial.events.SpatialEvent</code> stream bearer, <code>spatial.events.SpatialZone</code> latched public, <code>spatial.owm.ModelPose</code> stream bearer, <code>spatial.semantics.Detection2DSet</code> stream bearer, <code>spatial.semantics.Detection3DSet</code> stream bearer, <code>spatial.semantics.FusedTrackSet</code> stream bearer. **The same URL is also a WebSocket** (N.5): connect with <code>wss://</code> and receive the latched set as <code>sample</code> events, exactly one <code>end_of_replay</code> carrying the replay count, then live <code>sample</code> and <code>dispose</code> events (<code>{event, topic, key, data | reason}</code>). Not modelled here; see [Appendix N.5](https://spatialdds.org/v1.8/appendix-n/).</p><p class="codes"><span class="s s2">200</span> <span class="s s3">304</span> <span class="s s4">401</span> <span class="s s4">404</span> <span class="s s4">429</span> <span class="s s5">503</span></p></section><section id="listWellKnownInstances"><h3><span class="v get">GET</span> <code>/.well-known/spatialdds/{stream}/{type}/{version}</code></h3><p class="sum">A four-segment topic&#x27;s collection <span class="auth">token for operator-scoped</span></p><p>A four-segment topic (<code>spatialdds/&lt;stream&gt;/&lt;type&gt;/&lt;version&gt;</code>, no scene), such as the discovery announce lane, served exactly as a scene-scoped collection is: latched set, <code>ETag</code>, <code>304</code>, the same access classes, and the N.5 stream by upgrading the same path. Read-only: a topic with no scene is in no lane. **The same URL is also a WebSocket** (N.5): connect with <code>wss://</code> and receive the latched set as <code>sample</code> events, exactly one <code>end_of_replay</code> carrying the replay count, then live <code>sample</code> and <code>dispose</code> events (<code>{event, topic, key, data | reason}</code>). Not modelled here; see [Appendix N.5](https://spatialdds.org/v1.8/appendix-n/).</p><p class="codes"><span class="s s2">200</span> <span class="s s3">304</span> <span class="s s4">401</span> <span class="s s4">404</span> <span class="s s4">429</span> <span class="s s5">503</span></p></section><section id="getWellKnownInstance"><h3><span class="v get">GET</span> <code>/.well-known/spatialdds/{stream}/{type}/{version}/{key}</code></h3><p class="sum">One instance of a four-segment topic <span class="auth">token for operator-scoped</span></p><p>A four-segment topic (<code>spatialdds/&lt;stream&gt;/&lt;type&gt;/&lt;version&gt;</code>, no scene), such as the discovery announce lane, served exactly as a scene-scoped collection is: latched set, <code>ETag</code>, <code>304</code>, the same access classes, and the N.5 stream by upgrading the same path. Read-only: a topic with no scene is in no lane. </p><p class="codes"><span class="s s2">200</span> <span class="s s3">304</span> <span class="s s4">401</span> <span class="s s4">404</span> <span class="s s4">429</span> <span class="s s5">503</span></p></section><h2>Schemas</h2><p class=mut>115 components, from the published JSON Schemas at <code>/.well-known/spatialdds/schemas</code>.</p></main></body></html>

{spatialdds-0.8.0 → spatialdds-0.8.1}/spatialdds/artifacts/openapi.yaml RENAMED Viewed

@@ -2,7 +2,7 @@
 openapi: 3.1.0
 info:
   title: SpatialDDS web binding (spatialdds-py)
-  version: 0.8.0
+  version: 0.8.1
   summary: SpatialDDS 1.8 Appendix N over HTTPS, plus this endpoint's write surface.
   description: Generated by `tools/gen_openapi.py` from the gateway's own tables and the published JSON Schemas; never edited by hand. Reads are open; writes take a bearer token scoped to scenes. The WebSocket streams (N.5) are described on each collection path, not modelled. A deployment's own keyed types (`serve --extension`) are publishable on their own collection paths, under the same rules as the entity lane when they carry `basis`, `state`, `state_reason` and `stamp`; a type that names an `asserter` has it stamped or verified as the bearer token's principal (`asserter-not-principal`, `asserter-ungrounded`). Their paths are not listed here, because the deployment chooses them.
 servers:

{spatialdds-0.8.0 → spatialdds-0.8.1}/spatialdds/server/gw_http.py RENAMED Viewed

@@ -1153,10 +1153,12 @@ async def put_instance(request: web.Request) -> web.Response:
     try:
         topic, res = publish.resource_for_put(
             st, m["scene"], m["stream"], m["type"], m["version"])
-        # Before validation: an empty asserter is stamped, and the stamped
-        # body is the one checked, encoded and stored.
-        body = publish.ground_asserter(st, res.fqn, body, who.name)
+        # The body as sent meets the published schema first: a missing
+        # asserter is a missing required member, not an empty one (fuzz,
+        # 0.8.0). Then an empty asserter is stamped, and the stamped body is
+        # the one encoded and stored.
         publish.validate_schema(res.fqn, body, st)
+        body = publish.ground_asserter(st, res.fqn, body, who.name)
         publish.check_authority(request.app["base"], body)
         data, raw = publish.canonicalize(st, res.fqn, body)
         # The basis rule: an observed or derived claim declares how often it

{spatialdds-0.8.0 → spatialdds-0.8.1}/spatialdds/server/publish.py RENAMED Viewed

@@ -402,7 +402,7 @@ def ground_asserter(st: gateway.State, fqn: str, doc: Any,
     """
     if ASSERTER not in members_of(st, fqn) or not isinstance(doc, dict):
         return doc
-    claimed = doc.get(ASSERTER, "")
+    claimed = doc.get(ASSERTER)
     if not principal:
         raise Rejected(
             403, "asserter-ungrounded", "No principal to assert this claim",

{spatialdds-0.8.0 → spatialdds-0.8.1}/spatialdds.egg-info/PKG-INFO RENAMED Viewed

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: spatialdds
-Version: 0.8.0
+Version: 0.8.1
 Summary: SpatialDDS for programs: a client for the web binding (Appendix N), a native DDS participant, and the reference registry behind one command.
 Author: Open AR Cloud
 License: Apache-2.0

{spatialdds-0.8.0 → spatialdds-0.8.1}/README.md RENAMED Viewed

File without changes

{spatialdds-0.8.0 → spatialdds-0.8.1}/setup.cfg RENAMED Viewed

File without changes

{spatialdds-0.8.0 → spatialdds-0.8.1}/spatialdds/artifacts/idl/anchors.idl RENAMED Viewed

File without changes

{spatialdds-0.8.0 → spatialdds-0.8.1}/spatialdds/artifacts/idl/argeo.idl RENAMED Viewed

File without changes

{spatialdds-0.8.0 → spatialdds-0.8.1}/spatialdds/artifacts/idl/common.idl RENAMED Viewed

File without changes

{spatialdds-0.8.0 → spatialdds-0.8.1}/spatialdds/artifacts/idl/core.idl RENAMED Viewed

File without changes

{spatialdds-0.8.0 → spatialdds-0.8.1}/spatialdds/artifacts/idl/discovery.idl RENAMED Viewed

File without changes

{spatialdds-0.8.0 → spatialdds-0.8.1}/spatialdds/artifacts/idl/events.idl RENAMED Viewed

File without changes

{spatialdds-0.8.0 → spatialdds-0.8.1}/spatialdds/artifacts/idl/lidar.idl RENAMED Viewed

File without changes

{spatialdds-0.8.0 → spatialdds-0.8.1}/spatialdds/artifacts/idl/mapping.idl RENAMED Viewed

File without changes

{spatialdds-0.8.0 → spatialdds-0.8.1}/spatialdds/artifacts/idl/provisional/owm.idl RENAMED Viewed

File without changes

{spatialdds-0.8.0 → spatialdds-0.8.1}/spatialdds/artifacts/idl/provisional/radio.idl RENAMED Viewed

File without changes

{spatialdds-0.8.0 → spatialdds-0.8.1}/spatialdds/artifacts/idl/provisional/rf_beam.idl RENAMED Viewed

File without changes

{spatialdds-0.8.0 → spatialdds-0.8.1}/spatialdds/artifacts/idl/rad.idl RENAMED Viewed

File without changes

{spatialdds-0.8.0 → spatialdds-0.8.1}/spatialdds/artifacts/idl/semantics.idl RENAMED Viewed

File without changes

{spatialdds-0.8.0 → spatialdds-0.8.1}/spatialdds/artifacts/idl/slam_frontend.idl RENAMED Viewed

File without changes

{spatialdds-0.8.0 → spatialdds-0.8.1}/spatialdds/artifacts/idl/types.idl RENAMED Viewed

File without changes

{spatialdds-0.8.0 → spatialdds-0.8.1}/spatialdds/artifacts/idl/vio.idl RENAMED Viewed

File without changes

{spatialdds-0.8.0 → spatialdds-0.8.1}/spatialdds/artifacts/idl/vision.idl RENAMED Viewed

File without changes

{spatialdds-0.8.0 → spatialdds-0.8.1}/spatialdds/artifacts/registry.json RENAMED Viewed

File without changes

{spatialdds-0.8.0 → spatialdds-0.8.1}/spatialdds/artifacts/schemas/builtin_Time.json RENAMED Viewed

File without changes

{spatialdds-0.8.0 → spatialdds-0.8.1}/spatialdds/artifacts/schemas/spatial_anchors_AnchorDelta.json RENAMED Viewed

File without changes

{spatialdds-0.8.0 → spatialdds-0.8.1}/spatialdds/artifacts/schemas/spatial_anchors_AnchorEntry.json RENAMED Viewed

File without changes

{spatialdds-0.8.0 → spatialdds-0.8.1}/spatialdds/artifacts/schemas/spatial_anchors_AnchorSet.json RENAMED Viewed

File without changes

{spatialdds-0.8.0 → spatialdds-0.8.1}/spatialdds/artifacts/schemas/spatial_anchors_AnchorSetRequest.json RENAMED Viewed

File without changes

{spatialdds-0.8.0 → spatialdds-0.8.1}/spatialdds/artifacts/schemas/spatial_anchors_AnchorSetResponse.json RENAMED Viewed

File without changes

{spatialdds-0.8.0 → spatialdds-0.8.1}/spatialdds/artifacts/schemas/spatial_argeo_NodeGeo.json RENAMED Viewed

File without changes

{spatialdds-0.8.0 → spatialdds-0.8.1}/spatialdds/artifacts/schemas/spatial_argeo_QualityRequirements.json RENAMED Viewed

File without changes

{spatialdds-0.8.0 → spatialdds-0.8.1}/spatialdds/artifacts/schemas/spatial_argeo_VpsRequest.json RENAMED Viewed

File without changes

{spatialdds-0.8.0 → spatialdds-0.8.1}/spatialdds/artifacts/schemas/spatial_argeo_VpsResponse.json RENAMED Viewed

File without changes

{spatialdds-0.8.0 → spatialdds-0.8.1}/spatialdds/artifacts/schemas/spatial_common_AssetRef.json RENAMED Viewed

File without changes

{spatialdds-0.8.0 → spatialdds-0.8.1}/spatialdds/artifacts/schemas/spatial_common_FrameRef.json RENAMED Viewed

File without changes

{spatialdds-0.8.0 → spatialdds-0.8.1}/spatialdds/artifacts/schemas/spatial_common_KV.json RENAMED Viewed

File without changes

{spatialdds-0.8.0 → spatialdds-0.8.1}/spatialdds/artifacts/schemas/spatial_common_MetaKV.json RENAMED Viewed

File without changes

{spatialdds-0.8.0 → spatialdds-0.8.1}/spatialdds/artifacts/schemas/spatial_common_Vec2.json RENAMED Viewed

File without changes

{spatialdds-0.8.0 → spatialdds-0.8.1}/spatialdds/artifacts/schemas/spatial_core_Aabb3.json RENAMED Viewed

File without changes

{spatialdds-0.8.0 → spatialdds-0.8.1}/spatialdds/artifacts/schemas/spatial_core_BlobChunk.json RENAMED Viewed

File without changes

{spatialdds-0.8.0 → spatialdds-0.8.1}/spatialdds/artifacts/schemas/spatial_core_BlobRef.json RENAMED Viewed

File without changes

{spatialdds-0.8.0 → spatialdds-0.8.1}/spatialdds/artifacts/schemas/spatial_core_ComponentRef.json RENAMED Viewed

File without changes

{spatialdds-0.8.0 → spatialdds-0.8.1}/spatialdds/artifacts/schemas/spatial_core_Edge.json RENAMED Viewed

File without changes

{spatialdds-0.8.0 → spatialdds-0.8.1}/spatialdds/artifacts/schemas/spatial_core_EntityBinding.json RENAMED Viewed

File without changes

{spatialdds-0.8.0 → spatialdds-0.8.1}/spatialdds/artifacts/schemas/spatial_core_FrameTransform.json RENAMED Viewed

File without changes

{spatialdds-0.8.0 → spatialdds-0.8.1}/spatialdds/artifacts/schemas/spatial_core_FramedPose.json RENAMED Viewed

File without changes

{spatialdds-0.8.0 → spatialdds-0.8.1}/spatialdds/artifacts/schemas/spatial_core_GeoAnchor.json RENAMED Viewed

File without changes

{spatialdds-0.8.0 → spatialdds-0.8.1}/spatialdds/artifacts/schemas/spatial_core_GeoPose.json RENAMED Viewed

File without changes

{spatialdds-0.8.0 → spatialdds-0.8.1}/spatialdds/artifacts/schemas/spatial_core_NavSatStatus.json RENAMED Viewed

File without changes

{spatialdds-0.8.0 → spatialdds-0.8.1}/spatialdds/artifacts/schemas/spatial_core_Node.json RENAMED Viewed

File without changes

{spatialdds-0.8.0 → spatialdds-0.8.1}/spatialdds/artifacts/schemas/spatial_core_PlannedTrajectory.json RENAMED Viewed

File without changes

{spatialdds-0.8.0 → spatialdds-0.8.1}/spatialdds/artifacts/schemas/spatial_core_PlannedWaypoint.json RENAMED Viewed

File without changes

{spatialdds-0.8.0 → spatialdds-0.8.1}/spatialdds/artifacts/schemas/spatial_core_PoseSE3.json RENAMED Viewed

File without changes

{spatialdds-0.8.0 → spatialdds-0.8.1}/spatialdds/artifacts/schemas/spatial_core_SnapshotRequest.json RENAMED Viewed

File without changes

{spatialdds-0.8.0 → spatialdds-0.8.1}/spatialdds/artifacts/schemas/spatial_core_SnapshotResponse.json RENAMED Viewed

File without changes

{spatialdds-0.8.0 → spatialdds-0.8.1}/spatialdds/artifacts/schemas/spatial_core_TileKey.json RENAMED Viewed

File without changes

{spatialdds-0.8.0 → spatialdds-0.8.1}/spatialdds/artifacts/schemas/spatial_core_TileMeta.json RENAMED Viewed

File without changes

{spatialdds-0.8.0 → spatialdds-0.8.1}/spatialdds/artifacts/schemas/spatial_core_TilePatch.json RENAMED Viewed

File without changes

{spatialdds-0.8.0 → spatialdds-0.8.1}/spatialdds/artifacts/schemas/spatial_disco_Announce.json RENAMED Viewed

File without changes

{spatialdds-0.8.0 → spatialdds-0.8.1}/spatialdds/artifacts/schemas/spatial_disco_Capabilities.json RENAMED Viewed

File without changes

{spatialdds-0.8.0 → spatialdds-0.8.1}/spatialdds/artifacts/schemas/spatial_disco_ContentAnnounce.json RENAMED Viewed

File without changes

{spatialdds-0.8.0 → spatialdds-0.8.1}/spatialdds/artifacts/schemas/spatial_disco_CoverageElement.json RENAMED Viewed

File without changes

{spatialdds-0.8.0 → spatialdds-0.8.1}/spatialdds/artifacts/schemas/spatial_disco_CoverageFilter.json RENAMED Viewed

File without changes

{spatialdds-0.8.0 → spatialdds-0.8.1}/spatialdds/artifacts/schemas/spatial_disco_CoverageHint.json RENAMED Viewed

File without changes

{spatialdds-0.8.0 → spatialdds-0.8.1}/spatialdds/artifacts/schemas/spatial_disco_CoverageQuery.json RENAMED Viewed

File without changes

{spatialdds-0.8.0 → spatialdds-0.8.1}/spatialdds/artifacts/schemas/spatial_disco_CoverageResponse.json RENAMED Viewed

File without changes

{spatialdds-0.8.0 → spatialdds-0.8.1}/spatialdds/artifacts/schemas/spatial_disco_Depart.json RENAMED Viewed

File without changes

{spatialdds-0.8.0 → spatialdds-0.8.1}/spatialdds/artifacts/schemas/spatial_disco_KV.json RENAMED Viewed

File without changes

{spatialdds-0.8.0 → spatialdds-0.8.1}/spatialdds/artifacts/schemas/spatial_disco_ProfileSupport.json RENAMED Viewed

File without changes

{spatialdds-0.8.0 → spatialdds-0.8.1}/spatialdds/artifacts/schemas/spatial_disco_ServiceSummary.json RENAMED Viewed

File without changes

{spatialdds-0.8.0 → spatialdds-0.8.1}/spatialdds/artifacts/schemas/spatial_disco_TopicMeta.json RENAMED Viewed

File without changes

{spatialdds-0.8.0 → spatialdds-0.8.1}/spatialdds/artifacts/schemas/spatial_disco_Transform.json RENAMED Viewed

File without changes

{spatialdds-0.8.0 → spatialdds-0.8.1}/spatialdds/artifacts/schemas/spatial_disco_ValidityWindow.json RENAMED Viewed

File without changes

{spatialdds-0.8.0 → spatialdds-0.8.1}/spatialdds/artifacts/schemas/spatial_events_CrossingLine.json RENAMED Viewed

File without changes

{spatialdds-0.8.0 → spatialdds-0.8.1}/spatialdds/artifacts/schemas/spatial_events_SpatialEvent.json RENAMED Viewed

File without changes

{spatialdds-0.8.0 → spatialdds-0.8.1}/spatialdds/artifacts/schemas/spatial_events_SpatialZone.json RENAMED Viewed

File without changes

{spatialdds-0.8.0 → spatialdds-0.8.1}/spatialdds/artifacts/schemas/spatial_events_ZoneState.json RENAMED Viewed

File without changes

{spatialdds-0.8.0 → spatialdds-0.8.1}/spatialdds/artifacts/schemas/spatial_mapping_Edge.json RENAMED Viewed

File without changes

{spatialdds-0.8.0 → spatialdds-0.8.1}/spatialdds/artifacts/schemas/spatial_mapping_MapAlignment.json RENAMED Viewed

File without changes

{spatialdds-0.8.0 → spatialdds-0.8.1}/spatialdds/artifacts/schemas/spatial_mapping_MapEvent.json RENAMED Viewed

File without changes

{spatialdds-0.8.0 → spatialdds-0.8.1}/spatialdds/artifacts/schemas/spatial_mapping_MapMeta.json RENAMED Viewed

File without changes

{spatialdds-0.8.0 → spatialdds-0.8.1}/spatialdds/artifacts/schemas/spatial_mapping_MapQuality.json RENAMED Viewed

File without changes

{spatialdds-0.8.0 → spatialdds-0.8.1}/spatialdds/artifacts/schemas/spatial_owm_Entity.json RENAMED Viewed

File without changes

{spatialdds-0.8.0 → spatialdds-0.8.1}/spatialdds/artifacts/schemas/spatial_owm_ModelCommand.json RENAMED Viewed

File without changes

{spatialdds-0.8.0 → spatialdds-0.8.1}/spatialdds/artifacts/schemas/spatial_owm_ModelPose.json RENAMED Viewed

File without changes

{spatialdds-0.8.0 → spatialdds-0.8.1}/spatialdds/artifacts/schemas/spatial_semantics_Detection2D.json RENAMED Viewed

File without changes

{spatialdds-0.8.0 → spatialdds-0.8.1}/spatialdds/artifacts/schemas/spatial_semantics_Detection2DSet.json RENAMED Viewed

File without changes

{spatialdds-0.8.0 → spatialdds-0.8.1}/spatialdds/artifacts/schemas/spatial_semantics_Detection3D.json RENAMED Viewed

File without changes

{spatialdds-0.8.0 → spatialdds-0.8.1}/spatialdds/artifacts/schemas/spatial_semantics_Detection3DSet.json RENAMED Viewed

File without changes

{spatialdds-0.8.0 → spatialdds-0.8.1}/spatialdds/artifacts/schemas/spatial_semantics_FusedTrack.json RENAMED Viewed

File without changes

{spatialdds-0.8.0 → spatialdds-0.8.1}/spatialdds/artifacts/schemas/spatial_semantics_FusedTrackSet.json RENAMED Viewed

File without changes

{spatialdds-0.8.0 → spatialdds-0.8.1}/spatialdds/artifacts/schemas/spatial_semantics_Keypoint3D.json RENAMED Viewed

File without changes

{spatialdds-0.8.0 → spatialdds-0.8.1}/spatialdds/artifacts/schemas/spatial_semantics_KeypointLink.json RENAMED Viewed

File without changes

{spatialdds-0.8.0 → spatialdds-0.8.1}/spatialdds/artifacts/schemas/spatial_sensing_common_Axis.json RENAMED Viewed

File without changes

{spatialdds-0.8.0 → spatialdds-0.8.1}/spatialdds/artifacts/schemas/spatial_sensing_common_FrameHeader.json RENAMED Viewed

File without changes

{spatialdds-0.8.0 → spatialdds-0.8.1}/spatialdds/artifacts/schemas/spatial_sensing_common_FrameQuality.json RENAMED Viewed

File without changes

{spatialdds-0.8.0 → spatialdds-0.8.1}/spatialdds/artifacts/schemas/spatial_sensing_common_Linspace.json RENAMED Viewed

File without changes

{spatialdds-0.8.0 → spatialdds-0.8.1}/spatialdds/artifacts/schemas/spatial_sensing_common_ROI.json RENAMED Viewed

File without changes

{spatialdds-0.8.0 → spatialdds-0.8.1}/spatialdds/artifacts/schemas/spatial_sensing_common_ROIReply.json RENAMED Viewed

File without changes

{spatialdds-0.8.0 → spatialdds-0.8.1}/spatialdds/artifacts/schemas/spatial_sensing_common_ROIRequest.json RENAMED Viewed

File without changes

{spatialdds-0.8.0 → spatialdds-0.8.1}/spatialdds/artifacts/schemas/spatial_sensing_common_StreamMeta.json RENAMED Viewed

File without changes

{spatialdds-0.8.0 → spatialdds-0.8.1}/spatialdds/artifacts/schemas/spatial_sensing_lidar_LidarDetection.json RENAMED Viewed

File without changes

{spatialdds-0.8.0 → spatialdds-0.8.1}/spatialdds/artifacts/schemas/spatial_sensing_lidar_LidarDetectionSet.json RENAMED Viewed

File without changes

{spatialdds-0.8.0 → spatialdds-0.8.1}/spatialdds/artifacts/schemas/spatial_sensing_lidar_LidarFrame.json RENAMED Viewed

File without changes

{spatialdds-0.8.0 → spatialdds-0.8.1}/spatialdds/artifacts/schemas/spatial_sensing_lidar_LidarMeta.json RENAMED Viewed

File without changes

{spatialdds-0.8.0 → spatialdds-0.8.1}/spatialdds/artifacts/schemas/spatial_sensing_rad_RadDetection.json RENAMED Viewed

File without changes

{spatialdds-0.8.0 → spatialdds-0.8.1}/spatialdds/artifacts/schemas/spatial_sensing_rad_RadDetectionSet.json RENAMED Viewed

File without changes

{spatialdds-0.8.0 → spatialdds-0.8.1}/spatialdds/artifacts/schemas/spatial_sensing_rad_RadSensorMeta.json RENAMED Viewed

File without changes

{spatialdds-0.8.0 → spatialdds-0.8.1}/spatialdds/artifacts/schemas/spatial_sensing_rad_RadTensorFrame.json RENAMED Viewed

File without changes

{spatialdds-0.8.0 → spatialdds-0.8.1}/spatialdds/artifacts/schemas/spatial_sensing_rad_RadTensorMeta.json RENAMED Viewed

File without changes

{spatialdds-0.8.0 → spatialdds-0.8.1}/spatialdds/artifacts/schemas/spatial_sensing_radio_RadioObservation.json RENAMED Viewed

File without changes

{spatialdds-0.8.0 → spatialdds-0.8.1}/spatialdds/artifacts/schemas/spatial_sensing_radio_RadioScan.json RENAMED Viewed

File without changes

{spatialdds-0.8.0 → spatialdds-0.8.1}/spatialdds/artifacts/schemas/spatial_sensing_radio_RadioSensorMeta.json RENAMED Viewed

File without changes

{spatialdds-0.8.0 → spatialdds-0.8.1}/spatialdds/artifacts/schemas/spatial_sensing_rf_beam_RfBeamArraySet.json RENAMED Viewed

File without changes

{spatialdds-0.8.0 → spatialdds-0.8.1}/spatialdds/artifacts/schemas/spatial_sensing_rf_beam_RfBeamFrame.json RENAMED Viewed

File without changes

{spatialdds-0.8.0 → spatialdds-0.8.1}/spatialdds/artifacts/schemas/spatial_sensing_rf_beam_RfBeamMeta.json RENAMED Viewed

File without changes

{spatialdds-0.8.0 → spatialdds-0.8.1}/spatialdds/artifacts/schemas/spatial_sensing_vision_CamIntrinsics.json RENAMED Viewed

File without changes

{spatialdds-0.8.0 → spatialdds-0.8.1}/spatialdds/artifacts/schemas/spatial_sensing_vision_Keypoint2D.json RENAMED Viewed

File without changes

{spatialdds-0.8.0 → spatialdds-0.8.1}/spatialdds/artifacts/schemas/spatial_sensing_vision_Track2D.json RENAMED Viewed

File without changes

{spatialdds-0.8.0 → spatialdds-0.8.1}/spatialdds/artifacts/schemas/spatial_sensing_vision_VisionDetections.json RENAMED Viewed

File without changes

{spatialdds-0.8.0 → spatialdds-0.8.1}/spatialdds/artifacts/schemas/spatial_sensing_vision_VisionFrame.json RENAMED Viewed

File without changes

{spatialdds-0.8.0 → spatialdds-0.8.1}/spatialdds/artifacts/schemas/spatial_sensing_vision_VisionMeta.json RENAMED Viewed

File without changes

{spatialdds-0.8.0 → spatialdds-0.8.1}/spatialdds/artifacts/schemas/spatial_slam_frontend_CameraInfo.json RENAMED Viewed

File without changes

{spatialdds-0.8.0 → spatialdds-0.8.1}/spatialdds/artifacts/schemas/spatial_slam_frontend_Feature2D.json RENAMED Viewed

File without changes

{spatialdds-0.8.0 → spatialdds-0.8.1}/spatialdds/artifacts/schemas/spatial_slam_frontend_FeatureMatch.json RENAMED Viewed

File without changes

{spatialdds-0.8.0 → spatialdds-0.8.1}/spatialdds/artifacts/schemas/spatial_slam_frontend_KeyframeFeatures.json RENAMED Viewed

File without changes

spatialdds 0.8.0__tar.gz → 0.8.1__tar.gz

spatialdds 0.8.0tar.gz → 0.8.1tar.gz