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

remove rdf:PlainLiteral and add a change note; also add change note for triple terms #97

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

Conversation

pfps
Copy link
Contributor

@pfps pfps commented Feb 27, 2025

Fixes #84
Implements w3c/rdf-star-wg#147


Preview | Diff

@pfps pfps added the spec:substantive Change in the spec affecting its normative content (class 3) –see also spec:bug, spec:new-feature label Feb 27, 2025
Comment on lines +2296 to +2300
In RDF 1.1 <code>rdf:PlainLiteral</code> was described as an optional datatype that, if recognized,
MUST be interpreted to denote the datatype defined in [[RDF-PLAIN-LITERAL]].
<code>rdf:PlainLiteral</code> is not used elsewhere in the RDF documents,
so the requirement to give it this particular semantics has been removed.
It is recommended that <code>rdf:PlainLiteral</code> not be used in RDF.
Copy link
Member

Choose a reason for hiding this comment

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

I believe this appendix is INFORMATIVE, so MUST (line 2297) should be made lowercase and recommended (line 2300) should be kept so. If this appendix is NORMATIVE, then MUST (line 2297) should be kept uppercase, and recommended (line 2300) should also be made so. In either case, the introductory In RDF 1.1 should be followed by a comma.

Suggested change
In RDF 1.1 <code>rdf:PlainLiteral</code> was described as an optional datatype that, if recognized,
MUST be interpreted to denote the datatype defined in [[RDF-PLAIN-LITERAL]].
<code>rdf:PlainLiteral</code> is not used elsewhere in the RDF documents,
so the requirement to give it this particular semantics has been removed.
It is recommended that <code>rdf:PlainLiteral</code> not be used in RDF.
In RDF 1.1, <code>rdf:PlainLiteral</code> was described as an optional datatype that, if recognized,
must be interpreted to denote the datatype defined in [[RDF-PLAIN-LITERAL]].
<code>rdf:PlainLiteral</code> is not used elsewhere in the RDF documents,
so the requirement to give it this particular semantics has been removed.
It is recommended that <code>rdf:PlainLiteral</code> not be used in RDF.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

My understanding is that commas are optional after short introductory phrases.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

The MUST wording is from RDF 1.1, where it was in a normative section, so it should be MUST here because it was MUST there. This section is non-normative so recommended is lower case. (This sentence may be removed, however.)

Copy link
Member

@TallTed TallTed Mar 3, 2025

Choose a reason for hiding this comment

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

My understanding is that commas are optional after short introductory phrases.

Yes, "commas are optional after short introductory phrases", and, when omitted, they are inferred by strong/native readers of English. However, we are not writing for strong/native readers of English; we are writing for anyone on Earth. It is therefore better to include such optional commas.

The MUST wording is from RDF 1.1, where it was in a normative section, so it should be MUST here because it was MUST there. This section is non-normative so recommended is lower case. (This sentence may be removed, however.)

As a quotation from RDF 1.1, the phrase should be wrapped in quotation marks. Optimally, there would be a citation with a direct link to where this statement occurs. I generated that link with Chrome which may still be the only browser that creates them properly, but if my Google searching has been sufficient, most (Chrome, Safari, Edge, Firefox) if not all current browsers can dereference them properly. I don't know what ReSpec markup to use for such a citation, especially not if retaining the <a ... /a> within the quotation.... Also note the [denote] which replaced the original refer to.

Suggested change
In RDF 1.1 <code>rdf:PlainLiteral</code> was described as an optional datatype that, if recognized,
MUST be interpreted to denote the datatype defined in [[RDF-PLAIN-LITERAL]].
<code>rdf:PlainLiteral</code> is not used elsewhere in the RDF documents,
so the requirement to give it this particular semantics has been removed.
It is recommended that <code>rdf:PlainLiteral</code> not be used in RDF.
In RDF 1.1, <code>rdf:PlainLiteral</code> was described as an optional datatype
that, "[if] [recognized](https://www.w3.org/TR/rdf11-mt/#dfn-recognize), ...
must be interpreted to [denote] the datatype defined in [[RDF-PLAIN-LITERAL]]."
<code>rdf:PlainLiteral</code> is not used elsewhere in the RDF documents,
so the requirement to give it this particular semantics has been removed.
It is recommended that <code>rdf:PlainLiteral</code> not be used in RDF.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
spec:substantive Change in the spec affecting its normative content (class 3) –see also spec:bug, spec:new-feature
Projects
None yet
Development

Successfully merging this pull request may close these issues.

remove rdf:plainLiteral from Semantics?
2 participants