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.

Sign up for GitHub

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

Jump to bottom

Need to document that Elements need to have NodeKind IRI and all other objects are blank #805

Open
goneall opened this issue Jul 24, 2024 · 0 comments
Open

Need to document that Elements need to have NodeKind IRI and all other objects are blank #805

goneall opened this issue Jul 24, 2024 · 0 comments
Labels
documentation Improvements or additions to documentation serialization Something about the representation of data in bytes
Milestone
3.1

Comments

@goneall
Copy link
Member

goneall commented Jul 24, 2024

This came up in the implementers call.

Based on prior discussions, we agreed that Elements must be an IRI so they can be referenced across different serializations and be guaranteed unique. Non-Element objects (e.g. CreationInfo) should always be included in the same serialization - we could enforce this by requiring blank nodes.

Reference spdx/spec-parser#107
@bact bact mentioned this issue Jul 30, 2024
Open
70 tasks
@zvr zvr added the serialization Something about the representation of data in bytes label Jul 30, 2024
@kestewart kestewart added this to the 3.1 milestone Aug 10, 2024
@bact bact added the documentation Improvements or additions to documentation label Sep 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
documentation Improvements or additions to documentation serialization Something about the representation of data in bytes
Projects
None yet
Milestone
3.1
Development

No branches or pull requests
4 participants
@bact @zvr @goneall @kestewart