Change Snippet class structure to be compatible with W3C pointer definition

[goneall]

Propose changing the SBOM Snippet class structure and attribute names to be compatible with SPDX and W3C pointer definitions

Add classes StartEndPointer, (abstract) singlePointer, byteRangePointer and LineCharPointer
Add properties byteRange and lineRange with type StartEndPointer

[CASTResearchLabs]

it came from the SPDX 3.0 draft I received
it was also a simplification from a previous model where there were many classes to handle the ranges

[goneall]

it was also a simplification from a previous model where there were many classes to handle the ranges

Make a lot of sense. The Snippets in SPDX do have a lot of classes. The root cause of this is a desire to incorporate existing standard with the same meaning, which in this case is the W3C Pointer classes. The W3C classes are IMHO complex.

Does OMG have a similar objective of reusing existing standards? If so, I would suggest following the same somewhat more complex solution. If not, it would be worth considering a simplification.

Snippets are are only used in a small number of use cases, so the SPDX compatibility issues may not be as significant (although I would still prefer compatibility if there isn't a significant advantage to the alternative).

[goneall]

@iamwillbar any thoughts on the proposal?

[iamwillbar]

That's fine with me, the draft was more about structure than specific attribute names and types.