Remove support for contextual and ordered property values (again) per issue #10.

Author: gkellogg

index.html

@@ -165,7 +165,7 @@
 <p>This Working Draft is an update of the <a href="/TR/2012/NOTE-microdata-rdf-20121009/">W3C
   Interest Group Notea>, published in October 2012.
   <span>
-    This update adds ...
+    XXX
   span>
   The intention is to publish 
   this draft as a new version of the Interest Group Note after gathering and incorporating community input.
@@ -181,12 +181,12 @@ Introduction
     <p>There are a variety of ways in which a mapping from microdata to
       RDF might be configured to give a result that is closer to the required result for a particular vocabulary.
       This specification defines terms that can be used as hooks for
-      optional vocabulary-specific behavior, which could be defined within a
-      <a>registrya> or on an implementation-defined basis. However, the
+      vocabulary-specific behavior, which could be defined within a
+      <a>registrya> or on an implementation-defined basis. <span class="strike"> However, the
       HTML Data TF recommends the adoption of a single method of mapping in
-      which every vocabulary is treated as if:
+      which every vocabulary is treated as if:span>
     p>
-    <ul>
+    <ul class="strike">
       <li><a><code>propertyURIcode>a> is set to <code>vocabularycode>li>
       <li><a><code>multipleValuescode>a> is set to <code>unorderedcode>li>
     ul>
@@ -234,7 +234,7 @@ Background
      the microdata specification. This specification highlights where such
      violations occur and the reasons for them.p>
 
-   <p>This specification optionally allows for 
+   <p>This specification allows for 
      <a>vocabularya>-specific rules that affect the generation of property URIs and value serializations.
      This is facilitated by a <a>registrya> that associates URIs with specific rules based on matching
      <a class="aref">itemtypea> values against registered URI prefixes do determine a vocabulary and potentially
@@ -322,11 +322,15 @@ Issues
     particular candidate.
   p>
   <p class="issue" data-number="10">
-    Make use of the <a href="#vocab_expansion">Vocabulary Expansiona>, and
-    <a href="#vocabulary-entailment">Vocabulary Entailmenta>
-    conditional on a runtime option.
-    <a><code>propertyURIcode>a> defaults to <a>vocabularya> if there is an <a class="aref">itemtypea> and
-    <code>multipleValuescode> defaults to <strong>falsestrong>, where values are never placed in an <code>rdf:List.code>
+    Remove support for <code>contextualcode>
+    <a><code>propertyURIcode>a> and <code>mulitpleValuescode>. This issue proposes to
+    remove support for independently setting
+    <a><code>propertyURIcode>a> and <a><code>multipleValuescode>a>.
+    The former <a><code>propertyURIcode>a>
+    is treated like the former <a>vocabularya> scheme if
+    there is an <a class="aref">itemtypea>, otherwise, like <code>contextualcode> creating a property
+    as a fragment of the document base.
+    The former <code>multipleValuescode> is treated like false, where values are never placed in an <code>rdf:List.code>
   p>
   <p class="issue" data-number="11">
     Use full RDFa Entailment if <code>vocab_expansioncode> option given.
@@ -461,7 +465,7 @@ Attributes and Syntax
 
 <section class="informative">
   <h1>Vocabulary Registryh1>
-  <p class="note">The registry is controlled by a processor option (see <a href="#issues">issue 10a>).p>
+  <p class="note">(The registry is being considered for revision (see <a href="#issues">issue 10a>).p>
   <p>In a perfect world, all processors would be able to generate the same output for a given input
     without regards to the requirements of a particular <a>vocabularya>. However, microdata doesn't
     provide sufficient syntactic help in making these decisions. Different vocabularies have different
@@ -475,8 +479,6 @@ Vocabulary Registry
 
   pre>
   <p>In this example, assuming no matching entry in the <a>registrya>,
     the <a>URI prefixa> is constructed by removing the
     <cite><a href="http://tools.ietf.org/html/rfc3986#section-3.3">last path segmenta>cite>, leaving the URI
-    <code>http://schema.org/code>. As there is no explicit <a><code>propertyURIcode>a>,
-        the default <code>vocabularycode> is used, and the resulting property URI would be
-    <code>http://schema.org/titlecode>.p>
+    <code>http://example.org/code>. <span class="strike">As there is no explicit <a><code>propertyURIcode>a>,
+        the default <code>vocabularycode> is used, andspan> The resulting property URI would be
+    <code>http://example.org/titlecode>.p>
 
     <div>
       <p>If there is no in-scope <a class="aref">itemtypea>, property URIs are generated
@@ -667,8 +670,9 @@ Just a Geek
 
 section>
 
-<section class="informative">
+<section class="informative strike">
   <h2>Value Orderingh2>
+  <p class="note">(Value Ordering is being considered for removal (see <a href="#issues">issue 10a>).
   <p>For items having multiple values for a given <a>propertya>,
     the <dfn><code>multipleValuescode>dfn> rule defines the algorithm for serializing these values.
     Microdata uses document order when generating <a title="property value">property valuesa>, as defined in
@@ -744,6 +748,9 @@ Value Typing
 
 <section>
   <h2 id="vocab_expansion">Vocabulary Expansionh2>
+   <p class="note">Support for the registry is
+      being amended
+      (see <a href="#issues">issue 10a>).p>
   <p>Microdata requires that all values of <a class="aref">itemtypea> come from the same vocabulary. This
     is required as <a class="aref">itempropa> values are resolved relative to that vocabulary. However,
     it is often useful to define an <a>itema> to have types from multiple different vocabularies.p>
@@ -782,15 +789,11 @@ Vocabulary Expansion
 @prefix rdfs:  .
 @prefix schema:  .
 
-<>  rdfa:usesVocabulary schema: .
-
 [ a schema:Person;
   schema:additionalType foaf:Person;
   schema:email ;
   foaf:mbox 
 ] .
-
-schema:additionalType rdfs:subPropertyOf rdf:type .
 -->
 pre>
 
@@ -810,8 +813,6 @@ Vocabulary Expansion
   schema:email ;
   foaf:mbox 
 ] .  
-
-schema:additionalType rdfs:subPropertyOf rdf:type .
 -->
 pre>
 section>
@@ -949,7 +950,7 @@ Algorithm Terms
           <dt><dfn>memorydfn>dt><dd>
             a mapping of items to subjects, initially empty;
           dd>
-          <dt><dfn>current namedfn>dt><dd>
+          <dt class="strike"><dfn>current namedfn>dt><dd class="strike">
             an <a>absolute URLa> for the in-scope <a>namea>, used for generating URIs
             for properties of items without an <a>item typea>;
             <div class="note">
@@ -1247,7 +1248,7 @@ RDF Conversion Algorithm
       algorithm generates:p>
 
     <ol class="algorithm">
-      <li>For each element that is also a <a>top-level itema> run the following algorithm:
+      <li>For each element that is also a <a>top-level itema> <span class="strike">run the following algorithmspan>:
         <ol class="algorithm">
           <li>
             <a href="#generate-the-triples">Generate the triplesa> for an item <em>itemem>, using the
@@ -1317,7 +1318,7 @@ Generate the triples
         <code><cite><a href="http://www.w3.org/TR/2013/NOTE-microdata-20131029/#dom-itemtype">element.itemTypea>cite>code>
         of the element defining the <a>itema>.
       li>
-      <li>If <em>typeem> is an <a>absolute URLa>, set <a>current namea> in
+      <li class="strike">If <em>typeem> is an <a>absolute URLa>, set <a>current namea> in
         <a>evaluation contexta> to null.li>
       <li>
         Otherwise, set <em>typeem> to <a>current typea> from
@@ -1341,14 +1342,14 @@ Generate the triples
       <li>Otherwise, if type is not empty, construct <em>vocabem> by removing everything following the last
         SOLIDUS U+002F ("/") or NUMBER SIGN U+0023 ("#") from the <em>pathem> component of <em>typeem>.li>
       <li>Update <a>evaluation contexta> setting <a>current vocabularya> to <em>vocabem>.li> 
-      <li>
+      <li class="strike">
         Set <em>property listem> to an empty array mapping properties to one or more
         <em>valuesem> as established below.
       li>
       <li>
         For each element <em>elementem> that has one or more <a>property namesa> and is one of the
-        <a title="item properties">properties of the itema> <em>itemem>, in the order those elements
-        are given by the algorithm that returns the <a title="item properties">properties of the itema>,
+        <a title="item properties">properties of the itema> <em>itemem><span class="strike">, in the order those elements
+        are given by the algorithm that returns the <a title="item properties">properties of the itema>,span>
         run the following substep:
         <ol class="algorithm">
           <li>
@@ -1361,7 +1362,7 @@ Generate the triples
               <li>
                 Let <em>predicateem> be the result of <a href="#generate-predicate-uri">generate predicate URIa>
                 using <em>contextem> and <em>nameem>.
-                 Update <em>contextem> by setting <a>current namea> to <em>predicateem>.
+                 <span class="strike">Update <em>contextem> by setting <a>current namea> to <em>predicateem>span>.
               li>
               <li>
                 Let <em>valueem> be the <a>property valuea> of <em>elementem>.
@@ -1371,8 +1372,15 @@ Generate the triples
                 triplesa> for <em>valueem> using <em>contextem>. Replace <em>valueem> by the subject returned
                 from those steps.
               li>
-              <li>
-                Add <em>valueem> to <em>property listem> for <em>predicateem>.
+              <li>Generate the following triple:
+                <dl class="triple">
+                  <dt>subjectdt>
+                  <dd><em>subjectem>dd>
+                  <dt>predicatedt>
+                  <dd><em>predicateem>dd>
+                  <dt>objectdt>
+                  <dd><em>valueem>dd>
+                dl>
               li>
             ol>
           li>
@@ -1421,7 +1429,7 @@ Generate the triples
           li>
         ol>
       li>
-      <li>
+      <li class="strike">
         For each <em>predicateem> in <em>property listem>:
         <ol class="algorithm">
           <li><a href="#generate-property-values">Generate property valuesa> <em>subjectem>, <em>predicateem> and
@@ -1436,8 +1444,11 @@ Generate the triples
   <section>
     <h3>Generate Predicate URIh3>
     <p>Predicate URI generation makes use of <a>current typea>,
-      <a>current namea>, and <a>current vocabularya> from an <a>evaluation
+      <a class="strike">current namea>, and <a>current vocabularya> from an <a>evaluation
       contexta> <em>contextem> along with <em>nameem>.p>
+    <p class="note">Support for the <code>contextualcode> <em>schemaem> is
+      being considered for removal
+      (see <a href="#issues">issue 10a>).p>
 
     <ol class="algorithm">
       <li>If <em>nameem> is an <a>absolute URLa>, return <em>nameem>
@@ -1456,18 +1467,18 @@ Generate Predicate URI
           <code>http://example.org/doc#titlecode>.
         div>
       li>
-      <li>Otherwise, if <a>current vocabularya> from <em>contextem>
+      <li class="strike">Otherwise, if <a>current vocabularya> from <em>contextem>
         is not null and <a>registrya> has an entry for <a>current vocabularya>
         having a <a>propertyURIa> entry that is not null, set that as
         <em>schemeem>. Otherwise, set <em>schemeem> to
         <code>vocabularycode>.li>
-      <li id="scheme-vocab">If <em>schemeem> is <code>vocabularycode>
+      <li id="scheme-vocab"><span class="strike">If <em>schemeem> is <code>vocabularycode>span>
         set <em>expandedURIem> to the <a>URI referencea> constructed by
         appending the <a>fragment-escapea>d value of <em>nameem> to <a>current
         vocabularya>, separated by a U+0023 NUMBER SIGN character (#) unless the
         <a>current vocabularya> ends with either a U+0023 NUMBER SIGN character
         (#) or SOLIDUS U+002F (/).li>
-      <li id="scheme-context">Otherwise, if <em>schemeem> is
+      <li class="strike" id="scheme-context">Otherwise, if <em>schemeem> is
         <code>contextualcode>, set <em>expandedURIem> to the <a>URI
         referencea> constructed as follows:
         <ol class="algorithm">
@@ -1483,7 +1494,7 @@ Generate Predicate URI
             <em>nameem>. li>
         ol>
       li>
-      <li>If the <a>registrya> entry for <a>propertyURIa>
+      <li class="strike">If the <a>registrya> entry for <a>propertyURIa>
         has an <code>equivalentPropertycode> key,
         generate the following triple using the
         <em>valueem> of that key:
@@ -1497,7 +1508,7 @@ Generate Predicate URI
         dl>
         <p>If the value is an array, generate a triple for each value of that array.p>
       li>
-      <li>If the <a>registrya> entry for <a>propertyURIa>
+      <li class="strike">If the <a>registrya> entry for <a>propertyURIa>
         has an <code>subPropertyOfcode> key, generate the following triple using the
         <em>valueem> of that key:
         <dl class="triple">
@@ -1514,9 +1525,11 @@ Generate Predicate URI
     ol>
   section>
 
-  <section>
+  <section class="strike">
     <h2>Generate Property Valuesh2>
     <p>Property value serialization makes use of <em>subjectem>, <em>predicateem> and <em>valuesem>.p>
+    <p class="note">Support for the per-vocabulary processing rules is being considered for removal
+      (see <a href="#issues">issue 10a>).p>
 
     <ol class="algorithm">
       <li>If the <a>registrya> contains a URI prefix that is a character for character match of
@@ -1569,16 +1582,19 @@ Generate Property Values
     ol>
   section>
 
-  <section id="generate-collection">
+  <section class="strike" id="generate-collection">
     <h2>Generate RDF Collectionh2>
+    <p class="note">Support for the registry, and therefore the generation of RDF Collections
+      is being considered for removal
+      (see <a href="#issues">issue 10a>).p>
     <p>
       An <dfn>RDF Collectiondfn> is a mechanism for defining ordered sequences of objects in RDF (See <cite><a
       href="http://www.w3.org/TR/rdf-syntax/#collections">RDF Collectionsa>cite> in
       [[!RDF-SCHEMA]]). As the RDF data-model is that of an unordered graph, a linking method using properties
       <code>rdf:firstcode> and <code>rdf:next code>is required to be able to specify a particular order.
     p>
     <p>
-      In the microdata to RDF mapping, <a>RDF Collectiona>s are used when an item has more than one value
+      In the microdata to RDF mapping, <a title="RDF Collection">RDF Collectionsa> are used when an item has more than one value
       associated with a given property to ensure that the original document order is maintained. The following
       procedure should be used to generate triples when an <a>itema> property has more than one value
       (contained in <em>listem>):
@@ -1661,7 +1677,7 @@ Markup Examples
 pre>
 
 <p>Assuming that <a>registrya> contains a an entry for <code>http://purl.org/vocab/frbr/core#code>
-  with <a><code>propertyURIcode>a> set to <code>vocabularycode>,
+  <span class="strike">with <a><code>propertyURIcode>a> set to <code>vocabularycode>,span>
   this is equivalent to the following Turtle:p>
 <pre class="example" data-transform="updateExample">
 
 pre>