Skip to content

Commit 0d6984f

Browse files
committed
replace 'constituent' with 'appears in'
this makes Respec unhappy, because 'appears in' is currently not defined, but including the definition will be for another PR. This keeps this PR more "localized".
1 parent b6ff953 commit 0d6984f

File tree

1 file changed

+8
-16
lines changed

1 file changed

+8
-16
lines changed

spec/index.html

Lines changed: 8 additions & 16 deletions
Original file line numberDiff line numberDiff line change
@@ -909,13 +909,6 @@ <h3>Triple Terms</h3>
909909
Every <a>triple</a> whose <a>object</a> is not a <a>triple term</a> SHOULD NOT
910910
use <code>http://www.w3.org/1999/02/22-rdf-syntax-ns#reifies</code> (<code>rdf:reifies</code>)
911911
as its <a>predicate</a>.</p>
912-
913-
<p>The <dfn data-lt="constituent">constituent terms</dfn> (or simply constituents)
914-
of a [=triple term=] or an [=RDF triple=] are its [=subject=], its [=predicate=], its [=object=],
915-
and all the [=constituent terms=] of its [=object=] if it is itself a [=triple term=].
916-
By extension, the [=constituent terms=] of an [=RDF graph=] are all the constituent terms of its triples.
917-
</p>
918-
919912
</section>
920913

921914
<section id="graph-isomorphism">
@@ -1544,8 +1537,8 @@ <h2>From [=Full=] to [=Classic=]</h2>
15441537

15451538
<p>
15461539
Encoding an [=RDF graph=] to ensure that it is consumable by an RDF [=Classic=] implementation is called <dfn data-lt="classicize|classicized">classicizing</dfn> it.
1547-
[=Classicizing=] consists of repeating the following steps until no [=constituent=] of the graph is a [=triple term=], and the graph is therefore compliant with RDF [=Classic=]: picking a [=triple term=] <var>tt</var> that is a [=constituent terms=] of the graph; minting a fresh [=blank node=] <var>b</var>
1548-
(i.e., a blank node not yet in use in the graph); replacing <var>tt</var> with <var>b</var> in all the triples of the graph having <var>tt</var> in their [=constituents=];
1540+
[=Classicizing=] consists of repeating the following steps until no [=triple term=] [=appears=] in the graph, and the graph is therefore compliant with RDF [=Classic=]: picking a [=triple term=] <var>tt</var> that [=appears=] in the graph; minting a fresh [=blank node=] <var>b</var>
1541+
(i.e., a blank node not yet in use in the graph); replacing all occurrences of <var>tt</var> [=appearing=] in the graph with <var>b</var>;
15491542
and then adding the following triples to the graph (where <var>s</var>, <var>p</var>, and <var>o</var> are respectively the [=subject=], [=predicate=] and [=object=] of <var>tt</var>):
15501543
</p>
15511544
<ul>
@@ -1555,7 +1548,7 @@ <h2>From [=Full=] to [=Classic=]</h2>
15551548
<li>(<var>b</var>, `rdf:ttObject`, <var>o</var>)
15561549
</ul>
15571550

1558-
<p>Note that this transformation is <em>information preserving</em> only when the input graph either has no [=triple term=] in its [=constituents=],
1551+
<p>Note that this transformation is <em>information preserving</em> only when the input graph either has no [=triple term=] [=appearing=] in it,
15591552
or contains no [=asserted=] triple (<var>b</var>, `rdf:type`, `rdf:TripleTerm`) where <var>b</var> is a [=blank node=].
15601553
Implementations encountering this situation MUST report an error.
15611554
This limitation is discussed in Section <a href="#section-classicize-caveat"></a>.
@@ -1607,15 +1600,14 @@ <h2>From [=Classic=] to [=Full=]</h2>
16071600

16081601
<p>Reverting a [=classicized=] graph to its original form consists of locating
16091602
each [=asserted=] triple (<var>b</var>, `rdf:type`, `rdf:TripleTerm`)
1610-
that has a [=blank node=] <var>b</var> as its subject,
1611-
along with the three associated [=asserted=] triples
1603+
that has a [=blank node=] <var>b</var> as its subject,
1604+
along with the three associated [=asserted=] triples
16121605
that have the same [=blank node=] <var>b</var> as their subjects, i.e.,
16131606
(<var>b</var>, `rdf:ttSubject`, <var>s</var>),
16141607
(<var>b</var>, `rdf:ttPredicate`, <var>p</var>),
16151608
and (<var>b</var>, `rdf:ttObject`, <var>o</var>);
16161609
removing these four triples from the graph;
1617-
and replacing all remaining occurrences of <var>b</var>
1618-
as a [=constituent term=] of the graph
1610+
and replacing all remaining occurrences of <var>b</var> [=appearing=] in the graph
16191611
with the triple term (<var>s</var>, <var>p</var>, <var>o</var>).
16201612
</p>
16211613

@@ -1626,7 +1618,7 @@ <h2>From [=Classic=] to [=Full=]</h2>
16261618
is missing or duplicated).
16271619
An implementation MUST also report an error if the input graph contains
16281620
at the same time a [=triple term=] and an [=asserted triple=]
1629-
(<var>b</var>, `rdf:type`, `rdf:TripleTerm`)
1621+
(<var>b</var>, `rdf:type`, `rdf:TripleTerm`)
16301622
where <var>b</var> is the same [=blank node=].
16311623
Note that none of these situations can occur if the input graph was produced by the [=classicize=] transformation.
16321624
</p>
@@ -1644,7 +1636,7 @@ <h2>From [=Classic=] to [=Full=]</h2>
16441636
<h2>Limitations</h2>
16451637

16461638
<p>The two transformations above explicitly do not support graphs or datasets containing at the same time a [=triple term=] and an [=asserted triple=]
1647-
(<var>b</var>, `rdf:type`, `rdf:TripleTerm`)
1639+
(<var>b</var>, `rdf:type`, `rdf:TripleTerm`)
16481640
where <var>b</var> is a [=blank node=].
16491641
This means that the [=classicize=] transformation is not <em>strictly</em> universal.
16501642
</p>

0 commit comments

Comments
 (0)