Add JSON Schema & XML DTD definitions of message data model #439
Conversation
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
aphillips
approved these changes
Jul 24, 2023
ryzokuken
approved these changes
Aug 7, 2023
|
@aphillips I resolved the conflicts on this, and this should now be good to merge. I'll update #444 after that's done, so that it too can be merged. |
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.
PR #393 left out the JSON Schema definition of the data model, which it originally referred to as its canonical description. This PR re-presents that, but now together with a synonymous
message.dtddocument. Unlike before, these definitions are here referenced not as canonical, but as equivalent to the TypeScript definitions.The data model documents are also moved to
spec/data-model/, to increase their distance slightly from the rest of the spec.The intent with including these definitions is to increase the utility of the data model for applications that do have a need for representing messages as structured data rather than syntax. By providing ready definitions, we make it easier for such applications to naturally align for compatibility, without imposing any requirements that all implementations must comply with.