unique identifiers etc. #42
Merged
Conversation
This file contains 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
- Added a subsection (1.3.5) explaining our aproach to IDs: that we do not prescribe a specific data type for them. - Added optional IDs to object types whose instances our implementors might want to be addressable. - Added explanations of uniqueness scope to IDs and a few other properties. - Added a paragraph to Core preamble explaining that `lexicographicResource` and `entry` are intended as roots. - Added a bibliography item for NVH. - Added a paragraph to the preambles of XML, JSON and NVH serialization expaining that `lexicographicResource` and `entry` can be roots. - In the database serialization, changed the diagrams to make it obvious that table `lexicographicResources` is optional. - In the database serialization, made a few foreign-keys relationships optional. - Corrected a few typos etc.
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.
Added a subsection (1.3.5) explaining our aproach to IDs: that we do not prescribe a specific data type for them.
Added optional IDs to object types whose instances our implementors might want to be addressable.
Added explanations of uniqueness scope to IDs and a few other properties.
Added a paragraph to Core preamble explaining that
lexicographicResourceandentryare intended as roots.Added a bibliography item for NVH.
Added a paragraph to the preambles of XML, JSON and NVH serialization expaining that
lexicographicResourceandentrycan be roots.In the database serialization, changed the diagrams to make it obvious that table
lexicographicResourcesis optional.In the database serialization, made a few foreign-keys relationships optional.
Corrected a few typos etc.