Skip to content

Suggestions from January review on §2 #196

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Conversation

pchampin
Copy link
Contributor

@pchampin pchampin commented Apr 23, 2025

@afs' suggestion #6
https://gist.github.com/afs/f71020019fc33b4ded3e105339c6a655

I generally agree with Andy:
I think that most syntaxes will (eventually) support Full RDF 1.2, but it is specific implementations that may impose restrictions.

Conversely, listing those syntaxes under "Full Conformance" may give the wrong impression that other syntaxes would be needed by Classic/Basic implementations.


Preview | Diff

@afs' suggestion #6
https://gist.github.com/afs/f71020019fc33b4ded3e105339c6a655

I generally agree with Andy:
I think that most *syntaxes* will (eventually) support Full RDF 1.2,
but it is specific implementations that may impose restrictions.

Conversely, listing those syntaxes under "Full Conformance"
may give the wrong impression that *other* syntaxes would be needed
by Classic/Basic implementations.
@pchampin pchampin added the spec:enhancement Change to enhance the spec without affecting conformance (class 2) –see also spec:editorial label Apr 23, 2025
@pchampin pchampin requested review from gkellogg, afs and hartig April 23, 2025 23:49
Copy link
Member

@gkellogg gkellogg left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We might just list N-Triples as an RDF full format. I agree that picking “favored” formats is a problem, but N-Triples is foundational.

@pchampin
Copy link
Contributor Author

We might just list N-Triples as an RDF full format. I agree that picking “favored” formats is a problem, but N-Triples is foundational.

to restate my comment at the top: I don't believe that the Full/Basic distinction should be thought in terms of formats. All implementations (Full ones and Basic ones) will probably use the same formats (N-Triples, Turtle, JSON-LD...), but Basic implementation will use a subset of these formats (probably hinted with the profile= media-type parameter, by the way).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
spec:enhancement Change to enhance the spec without affecting conformance (class 2) –see also spec:editorial
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants