Gary, A few comments: I agree with your assertion that a CONTAINS (or a CONTAINED_BY) relationship is semantically identical to a RDF/JSON/YAML/XML package that has the hasFile(s) property or a

Hi Gary, a couple of quick initial reactions / thoughts: For the Golang tools, I believe it currently handles things similarly to the way you described the Java tools. The in-memory representation of

I would like to get some feedback from the community on some changes I’m making to the SPDX Java tools related to the hasFiles property in JSON and the CONTAINS relationship. If you’re a user

Thank you everyone for a great conversation today, I’ve opened punch list issues for each of the classes we discussed today: https://github.com/spdx/spdx-3-model/issues Regards, William

That is the issue: Is a "Document" element inherited from Collection a fundamental part of the serialized data bytes? Sean says that at the modeling level Collection is a peer of other Elements, and

Great, SHOULD not MUST 😊.

I apologize for any confusion in what I said. I would not assert #2 in William’s message below. You should be able to transfer a Collection Element without necessarily including all of its

>>unit of transfer = little-d document (sequence of octets) = data that is signed or hashed when an arbitrary set of elements is serialized = Bundle / set of Elements plus context used to aid

>> If we know some will be different or we don’t want to commit to this always being true, then Collection should be the generalized form (Collection). I strongly support this approach.

CIL

Sean emphasizes the independence principle - every Element stands alone, with no dependency on any other Element. That principle is what distinguishes SPDX v3 from v2. 1. A document is a file or

CIL

William, Attached is a proposed update to the logical model that allows each Element to be serialized either individually or with other Elements. The value of an Element must not be affected by where

William, An information model is quite different from a logical model. A logical model is a description of real-world things (identities, artifacts, etc.) whereas an information model defines

Hi, There's going to be a SCA & Dependency devroom at FOSDEM this year again. FOSDEM will be virtual again. For those interested in submitting a talk about their open source projects,

Thanks David, I really like this visualization and have framed the problem. As an aside, we’ve been using the term “logical model” for the information model and “physical model” or

Here is a simple example that should clarify what serialization is intended to accomplish. Information modeling is information-centric - it starts with "information" (variable values used by

I agree with #1. For example you should be able to transfer a single Annotation element without having to create an additional Document element just to hold it. If you are going to add a single

Some of Sean's (I think) suggestions from yesterday's call were: You should be able to transfer any element (including collections). If you transfer a Collection (or any of its subclasses) you must

1. I think we need only two terms: unit of transfer = little-d document (sequence of octets) = data that is signed or hashed when an arbitrary set of elements is serialized = Bundle / set of Elements