Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Define RDF 1.2 Basic profile #70

Open
gkellogg opened this issue Oct 9, 2023 · 2 comments
Open

Define RDF 1.2 Basic profile #70

gkellogg opened this issue Oct 9, 2023 · 2 comments
Labels
spec:enhancement Issue or proposed change to enhance the spec without changing the normative content substantively

Comments

@gkellogg
Copy link
Member

gkellogg commented Oct 9, 2023

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.

@gkellogg gkellogg added the spec:enhancement Issue or proposed change to enhance the spec without changing the normative content substantively label Oct 9, 2023
@pfps
Copy link
Contributor

pfps commented Oct 10, 2023

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
Copy link
Member Author

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
spec:enhancement Issue or proposed change to enhance the spec without changing the normative content substantively
Projects
None yet
Development

No branches or pull requests

2 participants