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

Proposal to adapt the abstract syntax to option 3 #78

Merged
merged 8 commits into from
Mar 7, 2024

Conversation

hartig
Copy link
Contributor

@hartig hartig commented Feb 16, 2024

Given the consensus that we reached in yesterday's call, here is a proposal on how to change the relevant definitions in RDF Concepts in order to capture Option 3.

Some remarks about this PR:

  1. I am currently using the term "triple term" in this proposal while the term "triple descriptor" has been floating around as an alternative name for the same concept. Personally, I like "triple term" more but, of course, I am open to replace "triple term" by "triple descriptor" in this PR if there is consensus in the group towards the latter.
  2. At the end of yesterday's call, there was a brief discussion whether the definition of triple terms should be recursive (i.e., whether a triple term may contain another triple term). The current definition in this PR is recursive. I defined it this way because of @pchampin's argument that, without recursion, it becomes impossible to talk about rdf:nameOf triples which have a triple term in their object position. Of course, if the group decides against such a recursive definition, this PR can easily be adapted to make the definition non-recursive.
  3. I have separated the definitions of "RDF triple" and "triple term" from one another even if these two definitions are essentially the same (syntactically, an RDF triple and a triple term are exactly the same thing). My rationale for this separation is to make it more obvious that these are two different concepts. I have also added a brief 'Note' on this topic.
  4. I have removed the definition of "asserted triple" because I think, by clearly separating the notion of an RDF triple from the notion of a triple term, it becomes obsolete to talk about asserted triples. Every triple (in a graph) is asserted; triple terms are not members of graphs.
  5. This PR changes only the definitions. I explicitly decided not to touch Section 1.3, which (currently) provides an informal introduction of quoted triples. We will certainly have to change that section as well, but I think that should be a different PR. We should first make sure that we have the definitions right.

Preview | Diff

…riple term (as per option 3 of w3c/rdf-star-wg#112) instead of quoted triples and asserted triples
spec/index.html Outdated Show resolved Hide resolved
spec/index.html Outdated Show resolved Hide resolved
spec/index.html Outdated Show resolved Hide resolved
Copy link
Member

@gkellogg gkellogg left a comment

Choose a reason for hiding this comment

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

  • One missing `.
  • Not sure what the motivation for removing "asserted triple" is.
  • This will need some update to Changes since, otherwise, looks good.

spec/index.html Show resolved Hide resolved
spec/index.html Show resolved Hide resolved
@gkellogg gkellogg added the spec:substantive Issue or proposed change in the spec that changes its normative content label Feb 17, 2024
spec/index.html Outdated Show resolved Hide resolved
spec/index.html Show resolved Hide resolved
Copy link
Member

@gkellogg gkellogg left a comment

Choose a reason for hiding this comment

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

Still some changes needed, I think.

spec/index.html Show resolved Hide resolved
spec/index.html Show resolved Hide resolved
spec/index.html Outdated Show resolved Hide resolved
Copy link
Member

@TallTed TallTed left a comment

Choose a reason for hiding this comment

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

Not sure if these comments are still valid... apparently closed a review without successfully submitting it.

spec/index.html Show resolved Hide resolved
spec/index.html Show resolved Hide resolved
Copy link
Member

@TallTed TallTed left a comment

Choose a reason for hiding this comment

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

OK to merge #78 and follow up via #80

... by reintroducing definitions for 'quoted triple' and 'asserted triple'
@pchampin
Copy link
Contributor

pchampin commented Mar 7, 2024

merging, as agreed during today's call: https://www.w3.org/2024/03/07-rdf-star-minutes.html#x282

@pchampin pchampin merged commit af7655a into main Mar 7, 2024
2 checks passed
@gkellogg gkellogg deleted the Option3AbstractSyntax branch March 7, 2024 21:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
spec:substantive Issue or proposed change in the spec that changes its normative content
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants