Define RDF 1.2 Basic profile

[gkellogg]

From w3c/rdf-star-wg#19 (comment), the group resolved the following:

1. The RDF-star WG shall define a profile for RDF 1.2 where quoted triples are excluded from the syntax
2. The profile that excludes quoted triples shall be named "RDF 1.2 Basic"
3. The profile that excludes quoted triples shall retain every other aspects of RDF 1.2, including features that were not present in RDF 1.1, as long as they are unrelated to quoted triples

Serialization syntaxes need to distinguish the portions of the grammar that are dependent on this profile.

[pfps]

Do serialization syntax documents need to distinguish non-Basic constructs? I don't think so - it should suffice to have a section in Concepts on Basic and state that the behaviour of Basic-compliant systems on syntax that would produce quoted triples is undefined. Alternatively Basic-compliant systems might be required to reject syntax that would produce quoted triples.

[gkellogg]

I agree and would prefer to not have to touch every serialization spec. If the processing mode is RDF 1.2 Basic it might be better if a graph containing quoted triples is detected so that we can test this case. Note that, depending on the outcome of the blank graphs (or whatever) discussion, this could be moot, if the use of graphs in place of quoted triples becomes a purely semantic distinction and does not impact the abstract syntax.

[Antoine-Zimmermann]

For serialisation specs, it could be possible to have a single, short piece of text that we copy over all serialisation specs and that roughly paraphrase what RDF 1.2 Concepts says about conformance for RDF 1.2 Basic. We do necessarily need to have format-specific requirements to comply with RDF 1.2 Basic, I assume.