Skip to content

Annotations on assserted triples are based on operational semantics #220

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

Open
wants to merge 5 commits into
base: main
Choose a base branch
from
Open
Changes from 3 commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 14 additions & 0 deletions spec/index.html
Original file line number Diff line number Diff line change
Expand Up @@ -366,6 +366,20 @@ <h3>Triple Terms and Reification</h3>
</figure>

<p>Note that a <a>triple term</a> may also have another <a>triple term</a> as an <a>object</a>.</p>

<p class="note">
This document advises to understand an assertion on a reified triple
as an assertion on an asserted triple of the same form,
if such a triple occurs in a graph as both a reified triple
and an asserted triple.
However, this understanding is not backed by the model-theoretic semantics
as layed out in RDF 1.2 Semantics.
I.e. co-reference is not defined via a model-theoretic formalisation of <a href="https://www.w3.org/TR/rdf12-concepts/#dfn-denote">denotation</a>
but relies on an operational semantics of <a href="https://w3c.github.io/rdf-semantics/spec/#dfn-identify">identification</a>,
established via best practices, examples and convention
in this document and RDF 1.2 Primer and RDF 1.2 Note on triple terms (tbd).
</p>

</section>

<section id="change-over-time">
Expand Down
Loading