Skip to content
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

Investigate using tools to generate serialization / deserialization implementations #88

Open
2 tasks
amy-keibler opened this issue Jan 12, 2022 · 0 comments
Labels
enhancement New feature or request

Comments

@amy-keibler
Copy link
Collaborator

Since we are splitting the internal data-model from the serialization / deserialization code in #77, we should consider auto-generating the implementations based on the schema definitions in the CycloneDX/specification repository.

Potential Options For Consideration

  • For XML, there isn't a clear option that looks feature-complete enough for consideration yet, but lumeohq/xsd-parser-rs is the most complete option found during initial research
  • schemafy for JSON Schema
  • protobuf for Protobuf

Acceptance Criteria

  • Deserialization validates the schema version, but is otherwise accepting of non-conformant data (following the Robustness Principle of gracefully handling invalid data, but only outputting valid data.)
  • The process for generating new schema implementation versions of the code should be automated and documented
@amy-keibler amy-keibler added the enhancement New feature or request label Jan 12, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant