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 #151

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

update RDF dataset discussion #151

wants to merge 1 commit into 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).

@@ -1021,11 +1021,13 @@ <h2>RDF Datasets</h2>
can avoid interoperability issues by not ascribing importance to
the presence or absence of empty named graphs.</p>

<p>SPARQL 1.2 [[SPARQL12-QUERY]] uses
<p>Version 1.2 of the SPARQL Query Language [[SPARQL12-QUERY]] uses
Copy link
Contributor

Choose a reason for hiding this comment

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

It's all SPARQL specs which is why it says SPARQL 1.2.

The link is provided because that is the starting point. Arguably, the link could be removed.

Copy link
Member Author

Choose a reason for hiding this comment

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

The link is provided because that is the starting point. Arguably, the link could be removed.

It seems odd for [SPARQL12-QUERY] to be the starting point.

[SPARQL12-CONCEPTS] or possibly [SPARQL12-NEW] makes more sense to me, and not only because these are listed before [SPARQL12-QUERY] in the List of Documents (to which I cannot find a way to link directly, nor to auto-expand after load)

It's all SPARQL specs which is why it says SPARQL 1.2.

It seems to me, this lends weight to linking to [SPARQL12-CONCEPTS] or possibly [SPARQL12-NEW] instead of [SPARQL12-QUERY].

Removing the link is indeed also an option.

Comment on lines +1029 to +1030
and RDF version 1.0
only allowed graph names to be IRIs.</p>
Copy link
Contributor

Choose a reason for hiding this comment

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

Better to remove this.

RDF 1.0 didn't mention datasets at all nor were they concurrent.
This is a note. RDF 1.1 is 10 years old.

@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.)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants