-
Notifications
You must be signed in to change notification settings - Fork 1
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
Add definitions required for triple terms #30
base: main
Are you sure you want to change the base?
Conversation
This PR seems to be running somewhat in advance of WG decisions? |
It is a Draft, so could just be anticipating that this will be adopted, but I agree that it may still be premature, as semantics could go in a different direction. |
Yes, this is a draft. I've only added one class. Properties are waiting to see how the discussion goes. |
It sounds good to update this PR to track where we're at. How about re-titling it to "Add definitions required for triple terms"? I think defining In Turtle, I'm thinking: rdf:reifies a rdf:Property ;
rdfs:domain rdfs:Resource ;
rdfs:range rdf:Proposition ;
rdfs:label "reifies"@en ;
rdfs:comment "The abstract proposition of a more concrete circumstance."@en .
rdf:Proposition a rdfs:Class ;
rdfs:label "proposition"@en ;
rdfs:comment "An atomic, logical, abstract proposition."@en . (See also w3c/rdf-concepts#115 and w3c/rdf-semantics#49 for additional properties relating a proposition to its constituents (in "classicized" and and symmetric RDF respectively). They may end up being defined elsewhere, so I don't think we can add those in this PR. Note that these referenced issues also need updates to reflect this recent convergence.) |
Thank you for the feedback and suggestions. I have updated the PR as proposed and re-titled it to "Add definitions required for triple terms". |
See PR #31 |
|
||
<section id="ch_proposition"> | ||
<h3>rdf:Proposition</h3> | ||
<p><code>rdf:Proposition</code> is the class of reified triples. |
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.
Update this to the definition in the RDF representation?
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.
There is a PR for RDF Representation, I will handle this in a couple of days.
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.
Small things, improving markup
@@ -409,6 +410,23 @@ <h3>rdf:type</h3> | |||
href="#ch_class"><code>rdfs:Class</code></a>.</p> | |||
</section> | |||
|
|||
<section id="ch_reifies"> | |||
<h3>rdf:reifies</h3> |
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.
<h3>rdf:reifies</h3> | |
<h3><code>rdf:reifies</code></h3> |
<p>states that R is an instance of <a href="#ch_resource"><code>rdfs:Resource</code></a> | ||
and reifies the triple term <code><<S P O>></code>, where S, P, and O represent | ||
the subject, predicate, and object of the reified triple, respectively. The object |
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 that the R, S, P, and O variables should be tagged to set them apart from the surrounding text, whether <em>
, <code>
, or otherwise. (And that similar tagging should be applied to other places where there's a <code>
-tagged sequence that is then deconstructed.) I'm applying <em>
here, as that is what was applied in the ill-fated w3c/rdf-semantics/#52
<p>states that R is an instance of <a href="#ch_resource"><code>rdfs:Resource</code></a> | |
and reifies the triple term <code><<S P O>></code>, where S, P, and O represent | |
the subject, predicate, and object of the reified triple, respectively. The object | |
<p>states that <em>R</em> is an instance of <a href="#ch_resource"><code>rdfs:Resource</code></a> | |
and reifies the triple term <code><<S P O>></code>, where <em>S</em>, <em>P</em>, and <em>O</em> represent | |
the subject, predicate, and object of the reified triple, respectively. The object |
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 you can use |R|
(or <var>R</var>
) for variables, and if in an element tagged "algorithm", it will highlight all the places the variable is used (within that element), at least in the Editor's Draft. The main thing is to be consistent
<code>rdf:reifies</code> is <a href="#ch_resource"><code>rdfs:Resource</code></a>. | ||
The <a href="#ch_range"><code>rdfs:range</code></a> of rdf:reifies is |
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.
<code>rdf:reifies</code> is <a href="#ch_resource"><code>rdfs:Resource</code></a>. | |
The <a href="#ch_range"><code>rdfs:range</code></a> of rdf:reifies is | |
<code>rdf:reifies</code> is <a href="#ch_resource"><code>rdfs:Resource</code></a>. | |
The <a href="#ch_range"><code>rdfs:range</code></a> of <code>rdf:reifies</code> is |
Preview | Diff