--- a/spec/latest/json-ld-syntax/index.html Wed Feb 27 22:02:13 2013 +0100
+++ b/spec/latest/json-ld-syntax/index.html Wed Feb 27 22:06:10 2013 +0100
@@ -1643,81 +1643,82 @@
</section>
<section>
-<h2>Property Generators</h2>
-
-<p>At times, an author may find that they need to express the same value for
-multiple properties. The simplest approach to accomplish this goal would be
-to do the following:</p>
-
-<pre class="example" data-transform="updateExample"
- title="Verbose expression of multiple properties with the same value">
-<!--
-{
- "@context":
- {
- ****"title1": "http://purl.org/dc/terms/title"****,
- ****"title2": "http://schema.org/name"****,
- ****"title3": "http://www.w3.org/2000/01/rdf-schema#label"****
- },
- "@id": "http://example.com/book",
- ****"title1": "The Count of Monte Cristo"****,
- ****"title2": "The Count of Monte Cristo"****,
- ****"title3": "The Count of Monte Cristo"****
-}
--->
-</pre>
-
-<p>Unfortunately, the approach above produces redundant data and would become a
-publishing burden for large data sets.
-In these situations, the author may use
-a <tdef>property generator</tdef> to express a <tref>term</tref> that maps to
-multiple <tref title="property">properties</tref> in the <tref>JSON-LD graph</tref>.
-This method can be accomplished by using the following markup pattern:</p>
-
-<pre class="example" data-transform="updateExample"
- title="Generating multiple properties using a single term">
-<!--
-{
- "@context":
+ <h2>Property Generators</h2>
+
+ <p class="issue atrisk">This feature is at risk as it introduces a lot of
+ algorithmic complexity for an unclear benefit.</p>
+
+ <p>At times, an author may find that they need to express the same value for
+ multiple properties. The simplest approach to accomplish this goal would be
+ to do the following:</p>
+
+ <pre class="example" data-transform="updateExample"
+ title="Verbose expression of multiple properties with the same value">
+ <!--
{
- ****"title": { "@id": [ "http://purl.org/dc/terms/title",
- "http://schema.org/name",
- "http://www.w3.org/2000/01/rdf-schema#label" ] }****
- },
- "@id": "http://example.com/book",
- ****"title": "The Count of Monte Cristo"****
-}
--->
-</pre>
-
-<p>While the term above is only used once outside of the <code>@context</code>,
-the document above will be interpreted like so:</p>
-
-<table class="example">
-<thead>
- <th>Subject</th>
- <th>Property</th>
- <th>Value</th>
-</thead>
-<tbody>
-<tr>
- <td>http://example.com/book</td>
- <td>http://purl.org/dc/terms/title</td>
- <td>The Count of Monte Cristo</td>
-</tr>
-<tr>
- <td>http://example.com/book</td>
- <td>http://schema.org/name</td>
- <td>The Count of Monte Cristo</td>
-</tr>
-<tr>
- <td>http://example.com/book</td>
- <td>http://www.w3.org/2000/01/rdf-schema#label</td>
- <td>The Count of Monte Cristo</td>
-</tr>
-</tbody>
-</table>
-
+ "@context":
+ {
+ ****"title1": "http://purl.org/dc/terms/title"****,
+ ****"title2": "http://schema.org/name"****,
+ ****"title3": "http://www.w3.org/2000/01/rdf-schema#label"****
+ },
+ "@id": "http://example.com/book",
+ ****"title1": "The Count of Monte Cristo"****,
+ ****"title2": "The Count of Monte Cristo"****,
+ ****"title3": "The Count of Monte Cristo"****
+ }
+ -->
+ </pre>
+
+ <p>Unfortunately, the approach above produces redundant data and would become a
+ publishing burden for large data sets. In these situations, the author may use
+ a <tdef>property generator</tdef> to express a <tref>term</tref> that maps to
+ multiple <tref title="property">properties</tref> in the <tref>JSON-LD graph</tref>.
+ This method can be accomplished by using the following markup pattern:</p>
+
+ <pre class="example" data-transform="updateExample"
+ title="Generating multiple properties using a single term">
+ <!--
+ {
+ "@context":
+ {
+ ****"title": { "@id": [ "http://purl.org/dc/terms/title",
+ "http://schema.org/name",
+ "http://www.w3.org/2000/01/rdf-schema#label" ] }****
+ },
+ "@id": "http://example.com/book",
+ ****"title": "The Count of Monte Cristo"****
+ }
+ -->
+ </pre>
+
+ <p>While the term above is only used once outside of the <code>@context</code>,
+ the document above will be interpreted like so:</p>
+
+ <table class="example">
+ <thead>
+ <th>Subject</th>
+ <th>Property</th>
+ <th>Value</th>
+ </thead>
+ <tbody>
+ <tr>
+ <td>http://example.com/book</td>
+ <td>http://purl.org/dc/terms/title</td>
+ <td>The Count of Monte Cristo</td>
+ </tr>
+ <tr>
+ <td>http://example.com/book</td>
+ <td>http://schema.org/name</td>
+ <td>The Count of Monte Cristo</td>
+ </tr>
+ <tr>
+ <td>http://example.com/book</td>
+ <td>http://www.w3.org/2000/01/rdf-schema#label</td>
+ <td>The Count of Monte Cristo</td>
+ </tr>
+ </tbody>
+ </table>
</section>
<section>