Add SPARQL validation

[JPEWdev]

An example SPARQL query in the model. See: spdx/spec-parser#213

[bact]

@JPEWdev may be related issue

• SPDX enumeration value URLs could use . or _ not / as separator #1166

[JPEWdev]

Generating these SPARQL rules from the text descriptions seemed like a really good fit for AI generation, and it did a really good job.

[JPEWdev]

@JPEWdev may be related issue

* [SPDX enumeration value URLs could use `.` or `_` not `/` as separator #1166](https://github.com/spdx/spdx-3-model/issues/1166)

Yes, I did notice that. It does work with correctly with BASE though, which is why I chose to use that instead. I think that should be good enough for the SPARQL queries

[bact]

This will work as an example or for a validation?

[JPEWdev]

It turned out to be pretty easy to get the AI to spit out the SPARQL queries, so I would probably say this isn't an example anymore. I've been testing the rules by generating a model with spdx/spec-parser#213 applied to the spec parser and it does appear to work as intended

[bact]

Looks great. Will be really really useful if we can have this integrated into the published RDF/Turtule file:

sh:sparql [
    sh:message "..." ;
    sh:select """
        SELECT ...
    """ ;
]

which spdx/spec-parser#213 is exactly doing.

In terms of human editor creation and review, this requires knowledge of SPARQL.
As long as this field is optional, it should be fine (as the author who add constraints in prose doesn't have to immediately have the SPARQL; the SPARQL can be added later in time, by the same or the different author).

(I have a different proposal, based on a YAML-based rule - which may be more author-friendly - but it is still another domain-specific language to learn - and not a standardized one like the SPARQL used here)