Data Formats and Contracts
Data Formats and Contracts
| Field | Value |
|---|---|
| Distribution | WCT English — OpenC5ISR |
| Product | OpenC5ISR |
| Release | 0.15.1 |
| Deployment | openc5isr-en.wallacecorptech.com |
| Source | /srv/wct/releases/OpenC5ISR-v0.15.0 |
| Evidence | File-format inventory and integration standard |
| Source fingerprint | 63d2b1097707e25d666401cdc6362e395968600a40a08690210cd8c0b75fbf50 |
| Status | Generated baseline — human review required |
Verification boundary: This page combines platform design guidance with static evidence from the release. It does not prove that every detected interface is enabled, reachable, secure, or operational in the deployed environment.
Observed format indicators
| Extension/format | Files |
|---|---|
.json |
76 |
.csv |
21 |
.ttl |
17 |
.xml |
7 |
.rdf |
4 |
Canonical data requirements
- Stable identifiers for entities, observations, tasks, products and events.
- Explicit units, coordinate reference, timestamps/time scale and uncertainty.
- Schema/semantic version and compatibility behavior.
- Source/provenance, confidence and processing lineage.
- Handling/releasability/retention metadata and object-level access controls.
- A compact event form plus artifact reference for large imagery, video or datasets.
Versioning rule
Prefer backward-compatible additive changes. Breaking changes require a new schema/semantic version, a transition period or adapter, explicit migration tests and release notes identifying affected producers and consumers.
Maintainer Notes
Add human-reviewed deployment notes, corrections, decisions, screenshots, and links here. Content outside the generated block is preserved on future runs.