Repository navigation
Formalize the CTRF extension model - #89
Open
Ma11hewThomas wants to merge 5 commits into
Open
Ma11hewThomas wants to merge 5 commits into
Ma11hewThomas wants to merge 5 commits into
Conversation
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Formalize extension ownership, location-specific definitions, independently versioned official contracts and separate CTRF/extension validation through existing
extraobjects.Official CTRF extension values must be objects containing
extensionVersion; official publications include a normative specification, location-mapped schemas, examples and conformance cases. Third-party/private values retain their own versioning conventions. Extensions cannot override fields defined in the CTRF specification, and unsupported extensions remain opaque.Stack step 12, based on #88 (
prep/0.3.0-11-global-errors). Only specification and changelog change: no CTRF document schema property, official extension, registry or Insights migration is introduced. CTRF conformance is independent of optional extension validation. Official extensions are versioned independently of the CTRF specification; no unreleased companion specification is referenced.Validation recorded 30 October: checksum-verified Sourcemeta 14.4.0 format/lint, 22 reference/265 normative cases and nine standalone examples passed. Independent AJV validates nine standalone and ten complete inline reports. Schema matches the parent and embedded schema byte-for-byte; whitespace checks pass.
31 October follow-ups: inherited assertion/global-error wording corrections propagated from #87/#88; AJV passes 265 normative cases, nine standalone and ten inline reports. Extension terminology now consistently uses CTRF specification, document schema and conformance; added step-12 lines contain no Core/Stream terminology. This editorial follow-up leaves the schema unchanged and embedded copy byte-equal. Downstream runtime suites were not rerun; website documentation follows acceptance.