-
-
Notifications
You must be signed in to change notification settings - Fork 59
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
intro to explicitly linked elements #236
Conversation
Signed-off-by: Jan Kowalleck <[email protected]>
@stevespringett I started with the topic, to show my ideas. Anyway, could you have a first review and tell me what you think about the general idea? I would start with the XSD and bring in the JSON schema if the XSD was complete. |
Signed-off-by: Jan Kowalleck <[email protected]>
I like it. Although technically redundant (a BOM-Link is a URI), the fact the schema specifically calls it out I think is a good thing. You captured all the places that a BOM-Link can be used. I would recommend proceeding and then spot check the formulation branch to see if there are others. |
will change the special BOM-Link types to be based on |
Signed-off-by: Jan Kowalleck <[email protected]>
Signed-off-by: Jan Kowalleck <[email protected]>
Signed-off-by: Jan Kowalleck <[email protected]>
Signed-off-by: Jan Kowalleck <[email protected]>
Signed-off-by: Jan Kowalleck <[email protected]>
Signed-off-by: Jan Kowalleck <[email protected]>
I transferred all changes from XSD to JSON schema.
|
Signed-off-by: Jan Kowalleck <[email protected]>
put to WIP again. PS: did backmerge of the master. noting else needed changes. |
Try to clarify interlinked elements details
this is intended to fix #136 and #217