-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update JADN Type Definition Description (Sect 3.1 & subs) #58
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I approve of the changes to the CN and info/types PNG.
The structure overlay will have to be changed later:
- Choice/Enumerated are union types, and Choice is either tagged (the kind we know and love with no options) or the new untagged (if oneOf, anyOf, and allOf options are included).
- UML collection options in table 7-1 are {sequence, set, orderedSet, bag} - sequence is new, orderedSet replaces unique and bag replaces unordered to align with UML. JIDL will still use "unique" for Array and "ordered" for Map/Record with the orderedSet type option.
- New inheritance options are {extends, restricts, and abstract} - currently undocumented and unimplemented, but they will go in JADN 1.1 along with untagged unions
I'm not sure the structure figure is helpful, but it can be included in this PR knowing that it will either be significantly updated or deleted. If it's helpful to some readers we should keep it.
In the software library I changed the "exports" info field name to "roots" to match what it is used for. "exports" is allowed as a synonym but is deprecated; new schemas should use roots, assuming the TC accepts the update to the CN and CS. I've started adding inheritance to the library but it isn't in a release yet.
I've added this PR to the 9 October working meeting agenda. |
Approved for merging at 9 October working meeting |
ipv4/6-net
on Array types