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

update RDF dataset discussion with explicit comparison of { RDF | SPARQL } { 1.2 | 1.1 | 1.0 } #151

Open
wants to merge 3 commits into
base: main
Choose a base branch
from

Conversation

TallTed
Copy link
Member

@TallTed TallTed commented Jan 24, 2025

Add explicit comparison of SPARQL 1.2 and RDF 1.2, vs SPARQL 1.1, RDF 1.1, and RDF 1.0. Might also want specific difference with SPARQL 1.0.

This specificity may not be needed for users who have never before encountered RDF or SPARQL, but I think it helpful for users who have worked with any previous version(s) — like me.


Preview | Diff

Add explicit comparison of SPARQL 1.2 and RDF 1.2, vs SPARQL 1.1, RDF 1.1, and RDF 1.0. Might also want specific difference with SPARQL 1.0.

This specificity may not be needed for users who have never before encountered RDF or SPARQL, but I think it helpful for users who *have* worked with any previous version(s) — like me.
@gkellogg
Copy link
Member

Note that we do discuss changes to RDF in the Abstract:

RDF 1.2 introduces triple terms as another kind of RDF term which can be used as the object of another triple. RDF 1.2 also introduces directional language-tagged strings, which contain a base direction element that allows the initial text direction to be specified for presentation by a user agent.

RDF 1.2 Concepts introduces key concepts and terminology for RDF 1.2, discusses datatyping, and the handling of fragment identifiers in IRIs within RDF graphs.

RDF 1.0 did not have named graphs, and therefore a discussion of the use of IRIs for graph names is not appropriate. (SPARQL 1.0 had it's own concept of named graphs).

@TallTed
Copy link
Member Author

TallTed commented Jan 27, 2025

Note that we do discuss changes to RDF in the Abstract:

I don't know about you, but when I am looking things up in a spec, and even when I am trying to read the entire document, I often overlook things in the Abstract (because I don't understand enough to absorb them properly) — and may even skip it entirely, because I expect it to echo things said later but at a higher level of, sorry, abstraction. For these reasons, I suggest that anything we mean for the reader to actively digest should be placed elsewhere in the document, even if it is also said (preferably not word-for-word) in the Abstract.

RDF 1.0 did not have named graphs, and therefore a discussion of the use of IRIs for graph names is not appropriate. (SPARQL 1.0 had it's own concept of named graphs).

My bad, probably. I should have re-re-re-re-re-re-read the RDF 1.0 & 1.1 and SPARQL 1.0 & 1.1 docs more closely. (In fact, I did go back to those docs, and based my own writing on what they said. I should have linked to my source material. I'll see if I can re-find it.)

@TallTed TallTed changed the title update RDF dataset discussion update RDF dataset discussion with explicit comparison of { RDF | SPARQL } { 1.2 | 1.1 | 1.0 } Feb 12, 2025
@pchampin pchampin added the spec:enhancement Change to enhance the spec without affecting conformance (class 2) –see also spec:editorial label Feb 19, 2025
Copy link
Contributor

@pchampin pchampin left a comment

Choose a reason for hiding this comment

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

Apart from the erroneous reference to named graphs in RDF 1.0, LGTM.

@TallTed TallTed requested a review from pchampin March 3, 2025 20:49
@gkellogg gkellogg dismissed pchampin’s stale review March 3, 2025 21:34

@pchampin requested that the erroneous inclusion of RDF 1.0 regarding named graphs be removed, which it has been.

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.

5 participants