-
-
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
Dependency type definition in JSON Schema and XSD Schema are inconsistent #146
Comments
Just as a note, it appears the field name difference is handled during (de)serialization by the 2 libraries I checked (Go, Java) so it seems there are no portability issues with that at the moment. |
Good spot @ajbrown - I just came across this working on @stevespringett / @coderpatros - can we consider aligning the schemas more here, unless there is a good reason to require the difference? |
…X#146 Signed-off-by: Paul Horton <[email protected]>
…cation#146 Signed-off-by: Paul Horton <[email protected]>
…ion#146 Signed-off-by: Paul Horton <[email protected]>
…cation#146 Signed-off-by: Paul Horton <[email protected]>
…ion#146 Signed-off-by: Paul Horton <[email protected]>
…to workaround which breaks Dependency (de-)serialization for JSON Signed-off-by: Paul Horton <[email protected]>
…dx-python-lib#290 Signed-off-by: Paul Horton <[email protected]>
…DX/specification#146 Signed-off-by: Paul Horton <[email protected]>
The way dependency objects are defined differs between the XSD and the JSON schema and documentation. The published documentation and JSON schema define "dependsOn" as a list of BOM ref strings, whereas the XSD defines the "dependsOn" list as a list of dependency objects, which would allow them to be nested.
The inconsistency causes confusing expectations across languages / systems, as some allow for nested dependencies and others do not.
Additionally, it appears that the XSD defines an element called "dependencies" whereas the JSON schema calls it "dependsOn"
XSD Definition
JSON Schema Definition
Documentation:
This stems from the issues raised in language libraries around nested dependencies:
The text was updated successfully, but these errors were encountered: