Skip to content

wording defining "RDF Literals" needs clarification #83

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
TallTed opened this issue Feb 6, 2025 · 7 comments
Open

wording defining "RDF Literals" needs clarification #83

TallTed opened this issue Feb 6, 2025 · 7 comments
Labels
spec:editorial Minor change in the specification (markup, typo, informative text; class 1 or 2)

Comments

@TallTed
Copy link
Member

TallTed commented Feb 6, 2025

Originally posted by @TallTed in #64 (comment)

@afs said

This is stylistic. I will leave it to the editors of this document.

In summary: with two exceptions, RDF literals combine a string and an IRI <a data-lt="identify">identifying</a> a datatype.
The exceptions are <a data-cite="RDF12-CONCEPTS#dfn-language-tagged-string">language-tagged strings</a>, assigned the type <code>rdf:langString</code>,
which have two syntactic components, a string and a language tag; and
<a data-cite="RDF12-CONCEPTS#dfn-directional-language-tagged string">directional language-tagged strings</a>,
assigned the type <code>rdf:dirLangString</code>,
which have three syntactic components, a string, a language tag, and a base direction.

Lines 778-783 can easily be read as listing a total of four or six things -- 2 syntactic components plus 1 string and 1 language tag; or 3 syntactic components plus 1 string, 1 language tag, and 1 base direction -- rather than the intended two or three syntactic components, being enumerated as "1 string and 1 language tag" or "1 string, 1 language tag, and 1 base direction".

I think too much is currently being asked of a single, very long sentence. Here I break it into two sentences. It could be broken into three or even four.

    In summary: with two exceptions, RDF literals combine a string and an IRI <a data-lt="identify">identifying</a> a datatype.
    The exceptions are <a data-cite="RDF12-CONCEPTS#dfn-language-tagged-string">language-tagged strings</a>,
    which are assigned the type <code>rdf:langString</code>, and
    <a data-cite="RDF12-CONCEPTS#dfn-directional-language-tagged string">directional language-tagged strings</a>,
    which are assigned the type <code>rdf:dirLangString</code>.
    <a data-cite="RDF12-CONCEPTS#dfn-language-tagged-string">language-tagged strings</a>
    have two syntactic components, these being a string and a language tag;
    <a data-cite="RDF12-CONCEPTS#dfn-directional-language-tagged string">directional language-tagged strings</a>
    have three syntactic components, these being a string, a language tag, and a base direction.
@pfps
Copy link
Contributor

pfps commented Feb 6, 2025

This is a summary of a definition from elsewhere. It is of the form "something, something; something, something." The semicolon is a stronger separator than the commas so there is, in my mind, no ambiguity.

There are lots of ways of writing this. I find the current way concise, unambiguous, and quite readable.

@TallTed
Copy link
Member Author

TallTed commented Feb 6, 2025

It is of the form "something, something; something, and something."

Rather, it is of the form "3 somethings, something, something, and something."

It would be better to make it of the form "3 somethings: something, something, and something."

@pfps
Copy link
Contributor

pfps commented Feb 6, 2025

I was referring to a larger context, where there is a semi-colon.

I don't see that using a colon would be better in the two cases.

@TallTed
Copy link
Member Author

TallTed commented Feb 6, 2025

I don't see that using a colon would be better in the two cases.

With it being an enormous sentence, colons don't work, because there's no "best way" to end the first list and start the next phrase. Hence, my rephrasing as two sentences.

@pfps pfps added spec:editorial Minor change in the specification (markup, typo, informative text; class 1 or 2) propose closing Proposed for closing and removed propose closing Proposed for closing labels Mar 6, 2025
@pfps
Copy link
Contributor

pfps commented Mar 27, 2025

I still don't see any problem.

@TallTed
Copy link
Member Author

TallTed commented Mar 27, 2025

[@pfps] I still don't see any problem.

Do you see a problem in my currently suggested rephrasing?

If not, since I do see a problem with the original, my suggested change should be applied.

If so, please elaborate, so I may try another rephrasing that may resolve both the problem I see in the original and the problem you see in my currently suggested rephrasing.

@franconi
Copy link
Contributor

franconi commented Apr 4, 2025

Like @pfps, I don't see any problem with the original.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
spec:editorial Minor change in the specification (markup, typo, informative text; class 1 or 2)
Projects
None yet
Development

No branches or pull requests

3 participants