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

Use PREFIX in Turtle #118

Closed
rubensworks opened this issue Sep 1, 2023 · 6 comments
Closed

Use PREFIX in Turtle #118

rubensworks opened this issue Sep 1, 2023 · 6 comments
Labels
spec:editorial Minor issue or proposed change in the specification (markup, typo, informative text)

Comments

@rubensworks
Copy link
Member

As suggested by @afs in w3c/sparql-update#31 (comment), we should replace the @prefix syntax in Turtle examples to PREFIX.

@rubensworks rubensworks added the spec:editorial Minor issue or proposed change in the specification (markup, typo, informative text) label Sep 1, 2023
@afs afs added the discuss-f2f Proposed for discussion during the next face-to-face meeting label Sep 6, 2023
@afs
Copy link
Contributor

afs commented Sep 6, 2023

I've added "discuss-f2f" for a group-wide view on use of PREFIX and @prefix.

@TallTed
Copy link
Member

TallTed commented Sep 12, 2023

+1 use PREFIX in preference to @prefix

@niklasl
Copy link

niklasl commented Sep 12, 2023

+1 for using the SPARQL syntax; to aid with e.g. copy-pasting. I'd prefer lower-case prefix in Turtle, since it is intended to be read by humans (and a text/* media-type, not an application/* one). SPARQL is more technical, designed to be more recognizable for SQL users.

@afs
Copy link
Contributor

afs commented Sep 12, 2023

TriG is "application/trig".
Turtle as "text/turtle" was inherited by RDF 1.1 WG and could not be changed.

@niklasl
Copy link

niklasl commented Sep 12, 2023

Also use BASE over @base.

@afs True, so it seems I argued for using different forms for those, which would be very confusing. Consistency is paramount, we should use one form for the bulk of the specs, and also make it clear when we introduce the syntax that variations are allowed. And then say something like "in these specs, the PREFIX and BASE forms will be used for consistency".

@afs
Copy link
Contributor

afs commented Sep 12, 2023

From TPAC 23:
"proposal: use PREFIX in specs over @Prefix across all documents"

(@afs assumes that applies to BASE as well)

Tpt added a commit that referenced this issue Sep 21, 2023
@ktk ktk removed the discuss-f2f Proposed for discussion during the next face-to-face meeting label Oct 3, 2023
Tpt added a commit that referenced this issue Oct 5, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
spec:editorial Minor issue or proposed change in the specification (markup, typo, informative text)
Projects
None yet
Development

No branches or pull requests

5 participants