The documentation is organized by authority and purpose. specification.md is normative; code and examples must conform to it. The remaining documents are explanatory profiles, implementation guidance, or scientific protocols and must not silently redefine normative behavior.
The figure provenance register identifies the source documents, construction method, parameters, and interpretive scope of each explanatory SVG.
Executed UI evidence is registered separately for the full scientific playground, DataTiles Store, and Online Delivery server client. Screenshots are explanatory presentation artifacts, not scientific payloads or conformance evidence.
| Document | Purpose |
|---|---|
| Specification | normative container, dimensions, CRS, provenance, numeric payload, FAIR metadata, validation, and HTTP profile |
| MBTiles fallback | selected-slice compatibility and physical-table export for conservative OpenLayers adapters |
| Onboard intelligence white paper | manifesto, AI evidence contract, practical marine/automotive architecture, and safety boundaries |
| Design evaluation | concise definition, audit findings, corrections, and compatibility conclusion |
| Zero-to-hero tutorial | ten theory-led lessons with executable raster/vector, FAIR, integrity, DRM, and Store laboratories |
| FAIR by design | operational mapping from each FAIR principle to DataTiles evidence and publication gates |
| FAIR scientific publication profile | normative-supporting FAIR gates, DataCite 4.7 alignment, and release evidence |
| Scientific provenance | W3C PROV-aligned entities, activities, agents, lineage, and audit rules |
| Data licensing and rights | SPDX expressions, source/output/metadata rights separation, attribution, and access conditions |
| Cryptographic integrity and digital signatures | optional SHA-256 logical manifests, Ed25519 signatures, trust policy, offline verification, and Sigstore/in-toto interoperability |
| Data sources and citation | authoritative source-by-source citations, acknowledgements, licences, frozen-manifest rules, and FAIR release checklist |
| Architecture | component boundaries and design rationale |
| Numeric tiles | DNT1 encoding and physical-value semantics |
| Vector tiles | multidimensional MVT/GeoJSON profiles and MBTiles projection |
| HTTP/OGC API | resource model and interoperability scope |
| Online Delivery | optional scientific and derived-portrayal HTTP profile, discovery, caching, concurrency, observability, and reference-server behavior |
| Direct NetCDF demo | checksum-locked Meteo@UniParthenope archive acquisition, configured variable allowlist, application launch, discovery, and DNT1 retrieval |
| Playground | OpenLayers scientific operations and limitations |
| DataTiles Store PWA | Flask/SQLAlchemy institutional catalog, metadata search, role-based access, interactive preview, licence/safety acceptance, API-first CRUD, and authorized downloads |
| DataTiles Store API v1 | Bearer authentication, agreement workflow, catalog/search, preview/download, managers CRUD, identity administration, and audit endpoints |
| Testing and release | local suite, CI gates, protected delivery, and release checklist |
| Profile demo | two-point transect algorithm and evidence |
| Reproducibility | exact reconstruction of the Naples reference object |
| Replicability | protocol for independent regions, sources, variables, and implementations |
| Getting started | concise installation and API tutorial |
| Interoperability conventions | CF-first variable semantics, units, CRS/datum, source identity, dimensions, and portrayal boundaries |
| Import utilities | Dependency-free feature ingestion plus NetCDF/GRIB/Zarr scientific ingestion, deterministic tiling, semantic mapping, and provenance |
| Zarr source profile | normative Zarr v2/v3 source identity, checksums, groups, remote stores, FAIR provenance and rights |
| References | research papers, standards, vocabularies, and source records |
| Commercial DRM | optional protected distribution, ODRL policy, recipient licences |