Skip to content

No connection between propositions and facts in model-theoretic semantics #144

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

Draft
wants to merge 4 commits into
base: main
Choose a base branch
from

Conversation

rat10
Copy link

@rat10 rat10 commented Jul 17, 2025

Add clarification that annotations on propositions can't annotate facts according to the model-theoretic semantics, but that an operational semantics may nudge users towards assuming such a connection.


Preview | Diff

rat10 added 3 commits July 17, 2025 13:57
…tics

add clarification that annotations on propositions can't annotate facts according to the model-theoretic semantics, but that an operational semantics may nudge users towards assuming such a connection
Add clarification that annotations on propositions can't annotate facts according to the model-theoretic semantics, but that an operational semantics may nudge users towards assuming such a connection.
@franconi
Copy link
Contributor

The RDF Semantics spec never mentions the notion of reification; the spec only introduces a special rdf:reifies property, whose only characteristic is to have a range as the special rdfs:proposition class. (Observe that Appendix D is going to be axed from this document). So, in this context your added paragraph is not appropriate.

@pchampin
Copy link
Contributor

The RDF Semantics spec never mentions the notion of reification

It does, but only for the old-style reification. So the use of "reification" in this PR is not consistent.

Similarly, the use of "(reified) proposition" is problematic. Does it refer to (1) a proposition that happens to have an incoming rdf:reifies relationship, (2) the denotee of the reifier at the other end of this relationship, or (3) the reifier itself. Grammatically, I would assume (1), but from previous discussions with @rat10, I assume it is rather (2) or (3). Either way, I disagree with this sentence: by definition, facts are propositions (the set of facts F(I) is a subset of the set of propositions IPR(I)). In interpretation (1), the connection between a proposition and a fact of the same form is the identity. In interpretation (2) and (3), the connection between the denotee of the reifier and the fact (which is identical to the proposition) is captured in IEXT(I(rdf:reifies)).

I have concerns about the 2nd part of the PR (discussion about "identification" vs. "denotation"), but they depend on which of the interpretations above – (1), (2) or (3) – is correct...

@franconi
Copy link
Contributor

The RDF Semantics spec never mentions the notion of reification

It does, but only for the old-style reification. So the use of "reification" in this PR is not consistent.

Appendix D will disappear from the Semantics document.

@franconi
Copy link
Contributor

Similarly, the use of "(reified) proposition" is problematic. Does it refer to (1) a proposition that happens to have an incoming rdf:reifies relationship, (2) the denotee of the reifier at the other end of this relationship, or (3) the reifier itself. Grammatically, I would assume (1), but from previous discussions with @rat10, I assume it is rather (2) or (3). Either way, I disagree with this sentence: by definition, facts are propositions (the set of facts F(I) is a subset of the set of propositions IPR(I)). In interpretation (1), the connection between a proposition and a fact of the same form is the identity. In interpretation (2) and (3), the connection between the denotee of the reifier and the fact (which is identical to the proposition) is captured in IEXT(I(rdf:reifies)).

This is exactly what I said in my comment to the PR in Concepts #220.

@pfps
Copy link
Contributor

pfps commented Jul 17, 2025

I propose closing this PR without merging it.

@pfps pfps added the spec:enhancement Change to enhance the spec without affecting conformance (class 2) –see also spec:editorial label Jul 17, 2025
@rat10
Copy link
Author

rat10 commented Jul 17, 2025

Similarly, the use of "(reified) proposition" is problematic. Does it refer to (1) a proposition that happens to have an incoming rdf:reifies relationship, (2) the denotee of the reifier at the other end of this relationship, or (3) the reifier itself. Grammatically, I would assume (1), but from previous discussions with @rat10, I assume it is rather (2) or (3). Either way, I disagree with this sentence: by definition, facts are propositions (the set of facts F(I) is a subset of the set of propositions IPR(I)). In interpretation (1), the connection between a proposition and a fact of the same form is the identity. In interpretation (2) and (3), the connection between the denotee of the reifier and the fact (which is identical to the proposition) is captured in IEXT(I(rdf:reifies)).

This is exactly what I said in my comment to the PR in Concepts #220.

In that comment you gave an explanation that seems helpful. Would you turn that into a PR as an addition to the Semantics spec, or should I give it a try?

@franconi
Copy link
Contributor

This is exactly what I said in my comment to the PR in Concepts #220.

In that comment you gave an explanation that seems helpful. Would you turn that into a PR as an addition to the Semantics spec, or should I give it a try?

I believe that such comment is not appropriate in the Semantics document.

@pfps pfps requested review from pfps and franconi July 17, 2025 16:25
Copy link
Contributor

@pfps pfps left a comment

Choose a reason for hiding this comment

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

I am against this change.

Copy link
Contributor

@franconi franconi left a comment

Choose a reason for hiding this comment

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

This PR should be cancelled.

@TallTed
Copy link
Member

TallTed commented Jul 17, 2025

This is exactly what I said in my comment to the PR in Concepts w3c/rdf-concepts#220 (comment).

In that comment you gave an explanation that seems helpful. Would you turn that into a PR as an addition to the Semantics spec, or should I give it a try?

I believe that such comment is not appropriate in the Semantics document.

Might it be appropriate in another of our 20ish documents (e.g., Concepts)? If it aids comprehension of the intended meanings of things, such that both @franconi and @rat10 agree on the meaning of both the comment (in Concepts) and the text in Semantics that is informed by the comment?

@franconi
Copy link
Contributor

I believe that such comment is not appropriate in the Semantics document.

Might it be appropriateu in another of our 20ish documents (e.g., Concepts)? If it aids comprehension of the intended meanings of things, such that both @franconi and @rat10 agree on the meaning of both the comment (in Concepts) and the text in Semantics that is informed by the comment?

You may remember (it’s in the minutes) that in the meeting last week I volunteered to craft the core of a sort of F.A.Q. note/document, stemming from the examples file we already have and from potential misunderstandings (like ph) and from clarification requests such as @rat10.

@lisp
Copy link

lisp commented Jul 18, 2025

The RDF Semantics spec never mentions the notion of reification; the spec only introduces a special rdf:reifies property, whose only characteristic is to have a range as the special rdfs:proposition class. (Observe that Appendix D is going to be axed from this document). So, in this context your added paragraph is not appropriate.

in the semantics document, the combination with "reifies" in relation to "Proposition" among the axiomatic triples establishes reification as a relevant notion.
should the editors choose to excise the word "reification" entirely from the semantics document that will not improve the exposition.

@rat10 rat10 marked this pull request as draft July 23, 2025 15:54
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.

Grammar, punctuation, and such

@@ -710,7 +710,7 @@ <h3>Properties of simple entailment and satisfiability</h3>
<p class="fact"> If E contains an IRI which does not occur anywhere in S,
then S does not simply entail E.</p>

<p>The following semantic properties relate triple terms and triples asserted in a graph, and they introduce a general definition of satisfiability.</p>
<p>The following semantic properties relate triple terms, triples asserted in a graph and reified triples, and they introduce a general definition of satisfiability.</p>
Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
<p>The following semantic properties relate triple terms, triples asserted in a graph and reified triples, and they introduce a general definition of satisfiability.</p>
<p>The following semantic properties relate triple terms, triples asserted in a graph, and reified triples, and they introduce a general definition of satisfiability.</p>

@@ -1969,8 +1969,52 @@ <h2 id="non_semantics">RDF reification, containers and collections</h2>
processes to check formal RDF entailment. For example, implementations may decide
to use special procedural techniques to implement the RDF collection vocabulary.</p>


<section id="TTerms">
<h3>RDF 1.2 reification - triple terms and reifiers</h3>
Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
<h3>RDF 1.2 reification - triple terms and reifiers</h3>
<h3>RDF 1.2 reification &mdash; triple terms and reifiers</h3>

<section id="TTerms">
<h3>RDF 1.2 reification - triple terms and reifiers</h3>
<p>
To repeat nomenclatura:
Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
To repeat nomenclatura:
To repeat our nomenclature:

To repeat nomenclatura:
<ul>
<li>an `rdfs:Proposition` subsumes multiple kinds of triples:
abstract triples, asserted triples and reified triples
Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
abstract triples, asserted triples and reified triples
abstract triples, asserted triples, and reified triples

</li>
<li>an abstract triple is encoded as a triple term</li>
<li>an asserted triple is also called a fact,
and also known as an RDF statement
Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
and also known as an RDF statement
and is also known as an RDF statement,

Comment on lines +1992 to +1993
never entails that triple as a fact.
Neither does a fact entail a reification of that triple.
Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
never entails that triple as a fact.
Neither does a fact entail a reification of that triple.
never entails that triple as a fact,
nor does a fact entail a reification of that triple.

Comment on lines +1995 to +1997
From that follows that in a strict interpretation of the model-theoretic semantics of RDF 1.2
an assertion on a reified triple (denoted by a reifier)
can never be an assertion on a fact asserting that same triple.
Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
From that follows that in a strict interpretation of the model-theoretic semantics of RDF 1.2
an assertion on a reified triple (denoted by a reifier)
can never be an assertion on a fact asserting that same triple.
It follows that, in a strict interpretation of the model-theoretic semantics of RDF 1.2,
an assertion on a reified triple (denoted by a reifier)
can never be an assertion on a fact asserting that same triple.

Comment on lines +2002 to +2007
A looser interpretation of that connection
as one of <a href="https://w3c.github.io/rdf-semantics/spec/#dfn-identify">identification</a>,
not <a href="https://www.w3.org/TR/rdf12-concepts/#dfn-denote">denotation</a>,
as applied in RDF 1.2 Concepts, RDF 1.2 Primer and the RDF 1.2 note on triple terms (tbd),
establishes an operational semantics of such a connection between reification and fact
as convention and best practice.
Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
A looser interpretation of that connection
as one of <a href="https://w3c.github.io/rdf-semantics/spec/#dfn-identify">identification</a>,
not <a href="https://www.w3.org/TR/rdf12-concepts/#dfn-denote">denotation</a>,
as applied in RDF 1.2 Concepts, RDF 1.2 Primer and the RDF 1.2 note on triple terms (tbd),
establishes an operational semantics of such a connection between reification and fact
as convention and best practice.
A looser interpretation of that connection
as one of <a href="https://w3c.github.io/rdf-semantics/spec/#dfn-identify">identification</a>,
not of <a href="https://www.w3.org/TR/rdf12-concepts/#dfn-denote">denotation</a>,
as applied in RDF 1.2 Concepts, RDF 1.2 Primer, and the RDF 1.2 note on triple terms (tbd),
establishes an operational semantics of such a connection between reification and fact
as convention and best practice.

Comment on lines +2011 to +2013
This design was chosen to facilitate assertions on asserted triples, a.k.a. "statements about statements",
while keeping the model-theoretic semantics of RDF 1.2 simple
and upholding a safe distance from modal logic complications.
Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
This design was chosen to facilitate assertions on asserted triples, a.k.a. "statements about statements",
while keeping the model-theoretic semantics of RDF 1.2 simple
and upholding a safe distance from modal logic complications.
This design was chosen to facilitate assertions on asserted triples,
also known as "statements about statements",
while keeping the model-theoretic semantics of RDF 1.2 simple
and upholding a safe distance from modal-logic complications.

<section id="Reif">
<h3>Reification</h3>
<h3>RDF 1.0/1.1 reification - statement quad reification </h3>
Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
<h3>RDF 1.0/1.1 reification - statement quad reification </h3>
<h3>RDF 1.0/1.1 reification &mdash; statement quad reification </h3>

@pfps pfps added the ms:CR Milestone: Candidate Recommendation label Jul 31, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ms:CR Milestone: Candidate Recommendation spec:enhancement Change to enhance the spec without affecting conformance (class 2) –see also spec:editorial
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants