Add simplified vocabulary expansion from discussion on issue #10. This obviates issue #11 entirely.

Author: gkellogg

index.html

@@ -332,18 +332,9 @@ Issues
     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.
-    The current spec duplicates rules for vocabulary entailment from RDFa, but also
-    allows RDFa entailment. Issue #10 suggests making vocabulary expansion (and
-    entailment) controlled by a processor option. Also, since original publication,
-    schema.org is now publishing an RDFs vocabulary at
-    http://schema.org/docs/schema_org_rdfa.html. If this vocabulary contained the
-    following statement:<br/>
-    <code>schema:additionalType rdfs:subPropertyOf rdf:type .code><br/>
-    the need for special registry rules for additionalType would be removed,
-    provided that RDFa vocabulary expansion is performed, where the schema.org
-    vocabulary is used to perform entailment operations.
+  <p class="issue strike resolved" data-number="11">
+    The use of Entailment to facilitate vocabulary expansion is replaced with direc triple
+    generation during the core processing algorithm.
   p>
 
   <p>The purpose of this specification is to provide input to a future working group that can make decisions
@@ -815,9 +806,20 @@ Vocabulary Expansion
 ] .  
 -->
 pre>
+
+  <p class="note">The <code>owl:equivalentPropertycode> rule is more powerfull than <code>rdfs:subPropertyOfcode>,
+    in that if any equivalent property matches, then the source property would also cause a triple to be generated.
+    For example, if the registry stated that <code>namecode> was equivalent to <code>rdfs:labelcode>,
+    than any use of <code>namecode> in a <a class="aref">itempropa> would cause a triple using
+    <code>rdfs:labelcode> to be emitted, as with <code>rdfs:subPropertyOfcode>. However, logically,
+    any use of <code>labelcode> where the current voabulary were <code>rdfs:code> could also cause
+    a triple using <code>schema:namecode> to be emitted. To simplify processing, this specification
+    requires that all values of a <code>owl:equivalentPropertycode> registry entry have their
+    own rules with those values as keys within the <code>propertycode> section of their respective
+    vocabularies.p>
 section>
 
-<section>
+<section class="strike">
   <h2>Vocabulary Entailmenth2>
   <p>Formally, and for the purpose of vocabulary processing, microdata uses a very
     restricted subset of the OWL2 vocabulary and is based on the RDF-Based Semantics of OWL2 [[!OWL2-RDF-BASED-SEMANTICS]].
@@ -854,7 +856,7 @@ Vocabulary Entailment
     a separate entailment algorithm. To allow [[RDFA-CORE]] processors to be used for microdata vocabulary expansion, microdata acts as if there is an implicit <code>@vocabcode> RDFa attribute set to a detected vocabulary by emitting
     a triple using the <code>rdfa:usesVocabularycode> predicate.p>
 
-  <p class="note"><a href="#issues">Issue 11a>span> suggests making the use of RDFa entailment
+  <p class="note strike"><a href="#issues">Issue 11a>span> suggests making the use of RDFa entailment
     the requirement, as vocabulary expansion is now proposed to be under the control of the
     <code>vocab_expansioncode> option.p>
 
@@ -907,15 +909,15 @@ Control of Microdata Processors
     must be loaded from the location indicated as the option value, Otherwise,
     the processor MUST load the default <a>registrya> from <code>http://www.w3.org/ns/mdcode>.
     <span class="note nostrike">see <a href="#issues">issue 10a>span>.
-  <p>If vocabulary expansion is performed by the microdata processor, and the
+  <p class="strike">If vocabulary expansion is performed by the microdata processor, and the
     <code>vocab_expansioncode> option is passed to the microdata processor,
     the full [[RDFA-CORE]] entailment MUST also be performed.
     The default value for <code>vocab_expansioncode> is <strong>falsestrong>.p>
-  <p>Setting <code>registrycode> and <code>vocab_expansioncode> is performed in a processor-specific way.p>
+  <p>Setting <code>registrycode> <span class="strike">and <code>vocab_expansioncode>span> is performed in a processor-specific way.p>
   <p>
-    When accessed as a <strong>web servicestrong> using HTTP GET, POST or similar action, processors SHOULD use <code>registrycode> and <code>vocab_expansioncode>
-    query parameters. Acceptable values for <code>registrycode> is a URI-encoded URL.
-    Acceptable values for <code>vocab_expansioncode> are <strong>truestrong> and <strong>falsestrong>.
+    When accessed as a <strong>web servicestrong> using HTTP GET, POST or similar action, processors SHOULD use <code>registrycode> <span class="strike">and <code>vocab_expansioncode>span>
+    query parameter<span class="strike">sspan>. Acceptable values for <code>registrycode> is a URI-encoded URL.
+    <span class="strike">Acceptable values for <code>vocab_expansioncode> are <strong>truestrong> and <strong>falsestrong>.span>
     Web service processors SHOULD return the resulting RDF graph using a requested format specified by
     HTTP Content Negotiation for an acceptable content type. Web service processors MUST support [[!N-TRIPLES]].
 section>
@@ -1274,7 +1276,7 @@ RDF Conversion Algorithm
           <dd><em>valueem>dd>
         dl>
       li>
-      <li>
+      <li class="strike">
         If the processor is given the <code>vocab_expansioncode> option, perform <a href="#vocabulary-entailment">Vocabulary Entailmenta>.li>
     ol>
   section>
@@ -1324,7 +1326,7 @@ Generate the triples
         Otherwise, set <em>typeem> to <a>current typea> from
         <a>evaluation contexta> if not empty.
       li>
-      <li>If the <a>registrya> contains a <a>URI prefixa> that is a
+      <li class="strike">If the <a>registrya> contains a <a>URI prefixa> that is a
         character for character match of <em>typeem> up to the length of the 
         <a>URI prefixa>,
         and the processor is given the <code>vocab_expansioncode> option,
@@ -1382,6 +1384,19 @@ Generate the triples
                   <dd><em>valueem>dd>
                 dl>
               li>
+              <li>
+                If an entry exists in the <a>registrya> for <em>nameem> in the vocabulary
+                associated with <em>vocabem> having the key <code>subPropertyOfcode> or
+                <code>equivalentPropertycode>, for each such value <em>equivem>, generate the following triple:
+                <dl class="triple">
+                  <dt>subjectdt>
+                  <dd><em>subjectem>dd>
+                  <dt>predicatedt>
+                  <dd><em>equivem>dd>
+                  <dt>objectdt>
+                  <dd><em>valueem>dd>
+                dl>
+              li>
             ol>
           li>
         ol>
@@ -1446,7 +1461,7 @@ Generate Predicate URI
     <p>Predicate URI generation makes use of <a>current typea>,
       <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
+    <p class="note">Support for the <code>contextualcode> <em>schemeem> is
       being considered for removal
       (see <a href="#issues">issue 10a>).p>