Canonical namespace
OCP 0.4 uses https://opencontinuity.org as the canonical origin for normative schemas, profiles, registries, vocabulary terms, examples, conformance data, and discovery.
Identifier families
| Family | Pattern | Example |
|---|---|---|
| Schemas | /schemas/0.4/… | context-package.schema.json |
| Profiles | /profiles/… | profiles/conversation |
| Registries | /registries/0.4/… | lifecycles.json |
| Conformance | /conformance/0.4/… | assertions.json |
| OpenAPI | /openapi/… | openapi/0.4.json |
| Discovery | /.well-known/ocp-configuration | discovery document |
Resolution and caching
- Use the canonical HTTPS URI in
schema_uri,$id, profile identifiers, and vocabulary terms. - Resolvers may use a verified local cache, but the cached document must preserve the canonical identifier.
- Pin the release catalog digest in reproducible builds and reject unexpected identifier changes.
- Do not rewrite OCP identifiers onto an implementation’s own domain.
Versioning
Schema and registry paths carry the wire version. Profile manifests declare their own version and compatible core range. Working-draft publication status is metadata, not a substitute for wire-version compatibility checks.
Was this page useful?
Your response is emailed to the Open Continuity maintainers. No account or email address is required.
Thank you. Your feedback was sent to the maintainers.