Gary O'Neall

@Urist-McGit - Does the suggestion work for you? If so, OK to close?

@sbarnum - I also recall the discussions and agree we reached an agreement to allow non-document exchanges. The reason I wrote the above is from practical experience attempted to implement...

@rgopikrishnan91 @bennetkl if one (or both) of you could review, we can merge this in

Thanks @IvicaDuspara for reporting the issue. It looks like this issue is with the SPDX Java Library used by the online tools. I'll transfer this issue to the library and...

@IvicaDuspara I found 3 issues in the above attached JSON file that causes the parsing failures: - Any non-core profile class or property needs to be prefixed with the lowercase...

The general issue of adding an extension not defined in the schema is much trickier since we don't have the model to deserialize the structure. Perhaps we create a separate...

@IvicaDuspara Since this issue discusses to different issues - handling abstract Extensions and handling CdxPropertiesExtensions - I opened a separate issue to discuss the abstract Extensions - #308 I believe...

Thanks @nishakm - I'll go ahead and merge. We may need to do some updates once we get the validation updated to 3.0.1, but we can take care of that...

Attached is an updated examples that almost passes validation using the 3.0.1 spec. It passes my Java verification code (generated from the 3.0.1 schema), but doesn't pass the schema validation....

I figured out the validation issues - attached is a JSON file that will pass with the 3.0.1 schema file: [example1.json.txt](https://github.com/user-attachments/files/16985358/example1.json.txt)