Greetings all,
I completed implementing the core model classes in the SPDX tools to match the 2.1 spec. I ran into one issue that may impact the specification. If an external reference type for a non-listed location is specified, in RDF it has a unique URI specified. There currently no specification for how to relate the unique URI to anything in tag/value. I can think of a few possible solutions: . Only support listed types. The spec would be updated to remove the non-listed example in RDF. It also would obviate the need for "other" in the category. . Make the RDF listed types local to the document (e.g. the URI would be SPDX document namespace followed by the type name and the type name would be used in the tag format) . Change the tag type syntax to allow for the full URI to be included in the type name (e.g. ExternalRef: OTHER http://example.org/documentNamespace#LocationRefacmeforge acmecorp/acmenator/4.1.3alpha") I also ran into some minor implementation difficulties having the same RDF property name in the RDF for the snippet byte range and line range. In order to validate which are required and which are optional, I had to add some additional code to check on the types of fields which increased the code complexity. We may want to consider adding a line range property to RDF (it is already there in tag/value). Gary ------------------------------------------------- Gary O'Neall Principal Consultant Source Auditor Inc. Mobile: 408.805.0586 Email: <mailto:[email protected]> [email protected]
_______________________________________________ Spdx-tech mailing list [email protected] https://lists.spdx.org/mailman/listinfo/spdx-tech
