-
Notifications
You must be signed in to change notification settings - Fork 4
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
Update RDF-semantics with the liberal baseline RDF and RDFS semantics #74
base: main
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Editorial. Small language fixes.
There are several markup problems that generate Echidna errors:
Likely, there's some missing closing tag that causes the parser to blow up. It's worth validating the HTML before pushing. |
Thanks. I did it, and I have committed now an error-free html. |
Co-authored-by: Ted Thibodeau Jr <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good enough aside from the changes I mentioned.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
generally LGTM
<tbody> | ||
<tr> | ||
<th></th> | ||
<th><strong>if the triple or triple term <a>appears in</a> S</strong></th> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
<th><strong>if the triple or triple term <a>appears in</a> S</strong></th> | |
<th><strong>if the triple <a>appears in</a> S</strong></th> |
"or triple term" is redundant. The definition of "appears in" for triples covers it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not opposed to keeping it, but I slightly prefer to remove it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I believe it would be wrong to assume that the check should be done only for triples.
<tbody> | ||
<tr> | ||
<th ></th> | ||
<th >If the triple or triple term <a>appears in</a> S:</th> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
<th >If the triple or triple term <a>appears in</a> S:</th> | |
<th >If the triple <a>appears in</a> S:</th> |
same as above
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As above :-), I believe it would be wrong to assume that the check should be done only for triples.
<tr > | ||
<td class="othertable"><dfn>rdfs14</dfn></td> | ||
<td class="othertable">xxx yyy <<(aaa bbb ccc)>> <code></code></td> | ||
<td class="othertable">the graph S with the appearance replaced with <br/> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
<td class="othertable">the graph S with the appearance replaced with <br/> | |
<td class="othertable"> |
No need for that. RDF is monotonic, so any inferred triple can coexist with the original triples.
In fact, this sentence may give the wrong impression that the original triples must be removed.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sure, but we need to ADD the triples with the bnode substitution.
On the other hand, we should find a better way to say it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oh, sorry, now I get it!
The triples on the right are only entailed as is IF the triples on the right are asserted.
But since the rule says they must "appear", then we need to replace their "appearance"...
It is not clear, however, than only the 1st of the 2 triples needs to be "injected". The other one is inferre asserted.
Also, a number of the triples in the rules are missing the trailing period (.
).
|
||
<tr> | ||
<th> </th> | ||
<th>RDFS entails</th> | ||
</tr> | ||
|
||
<tr> | ||
<td class="othertable"><code>ex:a ex:b ex:c .</code></td> | ||
<td class="othertable"><code><<(ex:a ex:b ex:c)>> rdf:type rdfs:Proposition .</code> </td> | ||
</tr> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This addition is present in the papers referenced at the top of this section [HORST04,HORST05]. I think the introductory sentence of that section should be explicit about the fact that the cited work was extended in RDF 1.2 with triple terms.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Wishful thinking. We have NOT extended the cited work in RDF 1.2 with triple terms. It should not be very hard to deal with this case, but I leave it to @pfps .
RDFS axiomatic triples. says |
Co-authored-by: Pierre-Antoine Champin <[email protected]>
Co-authored-by: Niklas Lindström <[email protected]>
@pfps: I think I resolved all your reviews, but you still appear in the final summary as having a requested change. I don't understand why. |
It's a github thing. I have to sign off somehow. Done. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good now
@doerthe: can you please check whether you like how rdfs14 is written? Maybe propose a better way? Or maybe could be fine if we add an example later? |
exist x,y,z such that RE(x,z,y)=r, or exists x such that < x,r > is in IEXT([I+A](<code>rdf:reifies</code>)), <br/> then < r,[I+A](<code>rdfs:Proposition</code>)> is in IEXT([I+A](<code>rdf:type</code>))</p></td> | ||
</tr> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think that [I+A]
should be replaced with I
here. [I+A]
is never mentioned in the semantic conditions of RDF-Entailment or RDFS-Entailment.
An RDF term <dfn>appears in</dfn> a graph G if it is in the set TM(G), defined inductively as follows: (1) for each triple in the graph G, its subject, predicate, and object are in TM(G); (2) for each triple term in TH(G), its subject, predicate, and object are in TM(G).<br/> | ||
A triple <b><i>appears in</i></b> a graph G if it is in G or if the triple term composed by its subject, predicate, and object appears in G. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've not changed any text here, only white space in the source, where shorter lines are far easier to review. Also, if it's worth <br/>
, it's usually worth <br/><br/>
. Also also, I'm wondering why the (1)(2)
don't warrant <br/>
or <ol>
.
An RDF term <dfn>appears in</dfn> a graph G if it is in the set TM(G), defined inductively as follows: (1) for each triple in the graph G, its subject, predicate, and object are in TM(G); (2) for each triple term in TH(G), its subject, predicate, and object are in TM(G).<br/> | |
A triple <b><i>appears in</i></b> a graph G if it is in G or if the triple term composed by its subject, predicate, and object appears in G. | |
An RDF term <dfn>appears in</dfn> a graph G if it is in the set TM(G), | |
defined inductively as follows: | |
(1) for each triple in the graph G, | |
its subject, predicate, and object are in TM(G); | |
(2) for each triple term in TH(G), | |
its subject, predicate, and object are in TM(G). | |
<br/><br/> | |
A triple <b><i>appears in</i></b> a graph G | |
if it is in G or | |
if the triple term composed by its subject, predicate, and object appears in G. |
@@ -1206,6 +1231,10 @@ <h2>RDFS Interpretations</h2> | |||
x is in ICEXT(I(<code>rdfs:Datatype</code>)) then <span >< x, | |||
I(<code>rdfs:Literal</code>) > is in IEXT(I(<code>rdfs:subClassOf</code>))</span></p></td> | |||
</tr> | |||
<tr> | |||
<td class="semantictable" id="rdfssemcond11"><p>If | |||
exist x,y,z such that RE(x,z,y)=r, or exists x such that < x,r > is in IEXT([I+A](<code>rdf:reifies</code>)), <br/> then < r,[I+A](<code>rdfs:Proposition</code>)> is in IEXT([I+A](<code>rdf:type</code>))</p></td> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Line lengths, again. I'm not changing it, but I think exist
in the first line below should be exists
. And, this is the rare case where <br/>
is preferred over <br/><br/>
.
exist x,y,z such that RE(x,z,y)=r, or exists x such that < x,r > is in IEXT([I+A](<code>rdf:reifies</code>)), <br/> then < r,[I+A](<code>rdfs:Proposition</code>)> is in IEXT([I+A](<code>rdf:type</code>))</p></td> | |
exist x,y,z such that RE(x,z,y)=r, or | |
exists x such that < x,r > | |
is in IEXT([I+A](<code>rdf:reifies</code>)), | |
<br/> | |
then < r,[I+A](<code>rdfs:Proposition</code>)> | |
is in IEXT([I+A](<code>rdf:type</code>))</p></td> |
@@ -1639,6 +1698,28 @@ <h2>Entailment rules (Informative)</h2> | |||
|
|||
<p>As noted earlier, detecting datatype entailment for larger sets of datatype IRIs | |||
requires attention to idiosyncratic properties of the particular datatypes.</p> | |||
|
|||
<p> | |||
The complete entailment pattern for generalized RDF with [=symmetric RDF triple=]s, considering that, according to the semantics, the denotation of triple terms should be of type <code>rdfs:Proposition</code>, is the following: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Line length again. =]s
should not exist. Any terms which are currently treated this way should get the plural added to the synonyms of the singular, and the s=]
should become s=]
. (Similar treatment also applies to other plural forms.)
The complete entailment pattern for generalized RDF with [=symmetric RDF triple=]s, considering that, according to the semantics, the denotation of triple terms should be of type <code>rdfs:Proposition</code>, is the following: | |
The complete entailment pattern for generalized RDF with [=symmetric RDF triples=], | |
considering that, according to the semantics, the denotation of triple terms should | |
be of type <code>rdfs:Proposition</code>, is the following: |
Update RDF-semantics with the liberal baseline RDF and RDFS semantics
Summary of changes:
Open issue:
TODO
Preview | Diff