- From: Yves Savourel via cvs-syncmail <cvsmail@w3.org>
- Date: Sat, 27 Oct 2012 12:13:33 +0000
- To: public-multilingualweb-lt-commits@w3.org
Update of /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20
In directory hutz:/tmp/cvs-serv3459
Modified Files:
its20.html its20.odd its20.xpr
Log Message:
Updated Disambiguation and non-normative references.
Index: its20.xpr
===================================================================
RCS file: /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/its20.xpr,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -d -r1.2 -r1.3
--- its20.xpr 19 Oct 2012 15:49:46 -0000 1.2
+++ its20.xpr 27 Oct 2012 12:13:31 -0000 1.3
@@ -164,7 +164,6 @@
</options>
</meta>
<projectTree name="its20.xpr">
- <folder path="../../../../../../ITS-2.0-Testsuite/its2.0/inputdata/"/>
<file name="its20.odd"/>
</projectTree>
</project>
\ No newline at end of file
Index: its20.odd
===================================================================
RCS file: /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/its20.odd,v
retrieving revision 1.206
retrieving revision 1.207
diff -u -d -r1.206 -r1.207
--- its20.odd 25 Oct 2012 15:16:43 -0000 1.206
+++ its20.odd 27 Oct 2012 12:13:31 -0000 1.207
@@ -3159,10 +3159,10 @@
and named entity definitions for the same things as authored in different languages, offering a mechanism to
locate translations from the source language description.</p>
- <p>Two types of disambiguation are needed to identify:</p><note type="ed">The previous sentence needs to be re-worded</note>
+ <p>Two types of disambiguation are possible:</p>
<list type="unordered">
- <item>Disambiguation type class, which describes the type class of the underlying concept or entity of the fragment.</item>
- <item>Disambiguation, which describes the actual underlying external resource that conveys the intended meaning of the fragment.</item>
+ <item>Disambiguation for target type class, which describes the type class of the underlying concept or entity of the fragment.</item>
+ <item>Disambiguation for target identity, which describes the actual underlying external resource that conveys the intended meaning of the fragment.</item>
</list>
<p>Text analysis engines, such as named entity recognizers, named entity, concept and word sense disambiguation
components can offer an easy way to create this information. Content management tools can present and visualize
@@ -3182,51 +3182,58 @@
<item>A required <att>selector</att> attribute that contains an <ref
target="#selectors">absolute selector</ref> which selects the
nodes to which this rule applies.</item>
- <item><p>Either:</p>
- <list>
- <item><p>A <att>disambigSource</att> attribute that contains a string representing the disambiguation
- identifier collection source.</p></item>
- <item><p>Exactly one of the following:</p>
- <list>
- <item><p>A <att>disambigIdent</att> attribute that contains a string that represents the disambiguation
- identifier for the disambiguation target that is valid within the specified disambiguation source.</p></item>
- <item><p>A <att>disambigIdentPointer</att> attribute that contains a <ref target="#selectors">relative selector</ref>
- pointing to a node that represents a unique identifier for the disambiguation target.</p></item>
- </list>
- </item>
- </list>
- </item>
- <item><p>Or:</p>
- <list>
- <item><p>Exactly one of the following:</p>
- <list>
- <item><p>A <att>disambigIdentRef</att> attribute that contains an URI that represents a unique identifier
- for the disambiguation target.</p></item>
- <item><p>A <att>disambigIdentRefPointer</att> attribute that contains a <ref target="#selectors">relative selector</ref>
- pointing to a node that holds a URI that represents a unique identifier for the disambiguation target.</p></item>
- </list>
- </item>
- </list>
- </item>
- <item><p>None or exactly one of the following:</p>
- <list>
- <item><p>A <att>disambigClassPointer</att> attribute that contains a <ref target="#selectors">relative selector</ref>
- pointing to a node specifying the entity type class behind the selector.</p></item>
- <item><p>A <att>disambigClassRef</att> attribute that contains a URI, specifying the type class of the concept
- or entity behind the selector.</p></item>
- <item><p>A <att>disambigClassRefPointer</att> attribute that contains a <ref target="#selectors">relative selector</ref>
- pointing to a node that holds a URI that specifies the entity type class behind the selector.</p></item>
- </list>
- </item>
- <item><p>An optional <att>disambigGranularity</att> attribute that contains a string, specifying the granularity
- level of the disambiguation. The value can be one of the following identifiers:
- <code>lexicalConcept</code>, <code>ontologyConcept</code>, or <code>entity</code>.</p></item>
+ <item><p>An optional <att>disambigGranularity</att> attribute that contains a string, specifying the granularity
+ level of the disambiguation. The value can be one of the following identifiers:
+ <code>lexicalConcept</code>, <code>ontologyConcept</code>, or <code>entity</code>.</p></item>
+
+ <item>At least one of the following:
+ <list>
+ <item>To specify the target type class, exactly one of the following:
+ <list>
+ <item><p>A <att>disambigClassPointer</att> attribute that contains a <ref target="#selectors">relative selector</ref>
+ pointing to a node specifying the entity type class behind the selector.</p></item>
+ <item><p>A <att>disambigClassRef</att> attribute that contains a URI, specifying the type class of the concept
+ or entity behind the selector.</p></item>
+ <item><p>A <att>disambigClassRefPointer</att> attribute that contains a <ref target="#selectors">relative selector</ref>
+ pointing to a node that holds a URI that specifies the entity type class behind the selector.</p></item>
+ </list>
+ </item>
+ <item>To specify the target identity, exactly one of the following:
+ <list>
+ <item><p>When using addressing mode 1:</p>
+ <list>
+ <item><p>A <att>disambigSource</att> attribute that contains a string representing the disambiguation
+ identifier collection source.</p></item>
+ <item><p>Exactly one of the following:</p>
+ <list>
+ <item><p>A <att>disambigIdent</att> attribute that contains a string that represents the disambiguation
+ identifier for the disambiguation target that is valid within the specified disambiguation source.</p></item>
+ <item><p>A <att>disambigIdentPointer</att> attribute that contains a <ref target="#selectors">relative selector</ref>
+ pointing to a node that represents a unique identifier for the disambiguation target.</p></item>
+ </list>
+ </item>
+ </list>
+ </item>
+ <item><p>When using addressing mode 2:</p>
+ <list>
+ <item><p>Exactly one of the following:</p>
+ <list>
+ <item><p>A <att>disambigIdentRef</att> attribute that contains an URI that represents a unique identifier
+ for the disambiguation target.</p></item>
+ <item><p>A <att>disambigIdentRefPointer</att> attribute that contains a <ref target="#selectors">relative selector</ref>
+ pointing to a node that holds a URI that represents a unique identifier for the disambiguation target.</p></item>
+ </list>
+ </item>
+ </list>
+ </item>
+ </list>
+ </item>
+ </list>
+ </item>
</list>
<note type="ed">Below will need a test case in the test suite.</note>
- <note type="ed">Sentence below is awkward</note>
- <p xml:id="disambiguation-use-cases">When using a disambiguation rule, the user <ref target="#rfc2119">MUST</ref> use one of the use
- cases for disambiguation: specifying the target type, or specifying the target identity.
- For the latter, the user <ref target="#rfc2119">MUST</ref> use only one of the two addressing modes:</p>
+ <p xml:id="disambiguation-use-cases">When using a disambiguation rule specifying the target identity,
+ the user <ref target="#rfc2119">MUST</ref> use only one of the two addressing modes:</p>
<list>
<item>Using <att>disambigSource</att> and one of <att>disambigIdent</att> or <att>disambigIdentPointer</att> to specify the
collection and the identifier itself.</item>
@@ -3244,29 +3251,43 @@
available for the <ref target="#Disambiguation">Disambiguation</ref>
data category:</p>
<list type="unordered">
- <item>An optional <att>disambigClassRef</att> attribute that contains a URI, specifying the type class
- of the concept or entity behind the selector.</item>
<item>An optional <att>disambigGranularity</att> attribute that contains a string, specifying the
granularity level of the disambiguation. The value can be one of the following identifiers:
<code>lexicalConcept</code>, <code>ontologyConcept</code>, or <code>entity</code></item>
- <item><p>Either:</p>
- <list>
- <item>A <att>disambigSource</att> attribute that contains a string representing the
- disambiguation identifier collection source.</item>
- <item>A <att>disambigIdent</att> attribute that contains a string, representing the
- disambiguation identifier for the disambiguation target that is valid within the specified
- disambiguation source.</item>
- </list>
- </item>
- <item><p>Or:</p>
- <list>
- <item>A <att>disambigIdentRef</att> attribute that contains a URI that represents a unique
- identifier for the disambiguation target.</item>
- </list>
- </item>
+
+ <item>At least one of the following:
+ <list>
+ <item>To specify the target type class:
+ <list>
+ <item>A <att>disambigClassRef</att> attribute that contains a URI, specifying the type class
+ of the concept or entity behind the selector.</item>
+ </list>
+ </item>
+ <item>To specify the target identity, exactly one of the following:
+ <list>
+ <item><p>When using addressing mode 1:</p>
+ <list>
+ <item>A <att>disambigSource</att> attribute that contains a string representing the
+ disambiguation identifier collection source.</item>
+ <item>A <att>disambigIdent</att> attribute that contains a string, representing the
+ disambiguation identifier for the disambiguation target that is valid within the specified
+ disambiguation source.</item>
+ </list>
+ </item>
+ <item><p>When using addressing mode 2:</p>
+ <list>
+ <item>A <att>disambigIdentRef</att> attribute that contains a URI that represents a unique
+ identifier for the disambiguation target.</item>
+ </list>
+ </item>
+ </list>
+ </item>
+ </list>
+ </item>
</list>
- <p>The user <ref target="#rfc2119">MUST</ref> use only one of the two addressing modes for "target identity" disambiguation:</p>
- <list>
+ <p>When specifying the target identity,
+ the user <ref target="#rfc2119">MUST</ref> use only one of the two addressing modes:</p>
+ <list>
<item>Using <att>disambigSource</att> and <att>disambigIdent</att> to specify the collection
and the identifier itself.</item>
<item>Using <att>disambigIdentRef</att> using a URI for the disambiguation target</item>
@@ -3280,7 +3301,7 @@
<note>
<p>For referring to <att>disambigClassRef</att> values, implementors are encouraged to use an existing
repository of entity types as long as they satisfy their requirements. For example,
- the Named Entity Recognition and Disambiguation ontology (NERD): http://nerd.eurecom.fr/ontology</p>
+ the Named Entity Recognition and Disambiguation ontology <ptr type="bibref" target="#nerd"/>.</p>
<p>Furthermore, valid target types depend on the disambiguation granularity: types of entities are distinct
from types of lexical concepts or ontology concepts. While this distinction exists, the specification does not prescribe
a way of automatically inferring a disambiguation level from a target type.</p>
@@ -5439,9 +5460,6 @@
<head>References</head>
<note type="ed">Need to complete entry for provenance data model.</note>
<listBibl>
- <bibl xml:id="prov-dm" n="PROV-DM">Editors tbd.
- <ref target="http://www.w3.org/TR/prov-dm/">Provenance data model</ref>. Details to be completed.
- </bibl>
<bibl xml:id="bidiarticle" n="Bidi Article">Richard Ishida. <title>
<ref
target="http://www.w3.org/International/articles/inline-bidi-markup/"
@@ -5512,6 +5530,8 @@
</title>. W3C Recommendation 29 September 2011. Available at <ref
target="http://www.w3.org/TR/css3-selectors/"
>http://www.w3.org/TR/css3-selectors/</ref>.</bibl>
+ <bibl xml:id="nerd" n="NERD">Named Entity Recognition and Disambiguation ontology (NERD)
+ available at: <ref target="http://nerd.eurecom.fr/ontology">http://nerd.eurecom.fr/ontology</ref></bibl>
<bibl xml:id="nvdl" n="NVDL">Information technology -- Document Schema
Definition Languages (DSDL) -- Part 4: <title>Namespace-based Validation
Dispatching Language (NVDL)</title>. International Organization for
@@ -5529,7 +5549,10 @@
target=" https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=office"
> OpenDocument</ref> is available at
https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=office.</bibl>
- <bibl xml:id="rfc3066" n="RFC 3066">Harald Alvestrand. <title><ref
+ <bibl xml:id="prov-dm" n="PROV-DM">Editors tbd.
+ <ref target="http://www.w3.org/TR/prov-dm/">Provenance data model</ref>. Details to be completed.
+ </bibl>
+ <bibl xml:id="rfc3066" n="RFC 3066">Harald Alvestrand. <title><ref
target="http://www.ietf.org/rfc/rfc3066.txt">Tags for the
Identification of Languages</ref></title>. RFC 3066, January 2001.
Available at <ref target="http://www.ietf.org/rfc/rfc3066.txt"
@@ -5740,6 +5763,7 @@
<list type="unordered">
<item>Clarified usage of <ref target="#domain">Domain</ref> data category in HTML5 in response to <ref target="https://www.w3.org/International/multilingualweb/lt/track/issues/56">issue-56</ref>.</item>
<item>Added the <ref target="#lqissueDefs">enabled information</ref> in <ptr type="specref" target="#lqissue"/>.</item>
+ <item>Updated the <ref target="#Disambiguation">Disambiguation</ref> data category.</item>
</list>
<p xml:id="changelog-since-20120829">The following log records major changes that
have been made to this document since the <ref
Index: its20.html
===================================================================
RCS file: /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/its20.html,v
retrieving revision 1.206
retrieving revision 1.207
diff -u -d -r1.206 -r1.207
--- its20.html 25 Oct 2012 15:16:42 -0000 1.206
+++ its20.html 27 Oct 2012 12:13:31 -0000 1.207
@@ -2050,7 +2050,7 @@
“PopulatedPlace” in the conceptual granularity level, or the central area of a particular city, e.g. City of London,
as interpreted in the entity granularity level. Linked data network, such as DBpedia, increasing interlink ontological
and named entity definitions for the same things as authored in different languages, offering a mechanism to
- locate translations from the source language description.</p><p>Two types of disambiguation are needed to identify:</p><span class="editor-note">[Ed. note: The previous sentence needs to be re-worded]</span><ul><li><p>Disambiguation type class, which describes the type class of the underlying concept or entity of the fragment.</p></li><li><p>Disambiguation, which describes the actual underlying external resource that conveys the intended meaning of the fragment.</p></li></ul><p>Text analysis engines, such as named entity recognizers, named entity, concept and word sense disambiguation
+ locate translations from the source language description.</p><p>Two types of disambiguation are possible:</p><ul><li><p>Disambiguation for target type class, which describes the type class of the underlying concept or entity of the fragment.</p></li><li><p>Disambiguation for target identity, which describes the actual underlying external resource that conveys the intended meaning of the fragment.</p></li></ul><p>Text analysis engines, such as named entity recognizers, named entity, concept and word sense disambiguation
components can offer an easy way to create this information. Content management tools can present and visualize
this information or use it to index their content. Machine translations systems may use it for training and translation
when dealing with proper names and edge cases.</p></div><div class="div3">
@@ -2059,19 +2059,20 @@
information applies to the textual content of the element. There is no
inheritance. The entity type follows inheritance rules.</p><span class="editor-note">[Ed. note: The two last sentences above seem contradictory.]</span><p id="disambiguation-global">GLOBAL: The <code>disambiguationRule</code>
element contains the following:</p><ul><li><p>A required <code>selector</code> attribute that contains an <a href="#selectors" shape="rect">absolute selector</a> which selects the
- nodes to which this rule applies.</p></li><li><p>Either:</p><ul><li><p>A <code>disambigSource</code> attribute that contains a string representing the disambiguation
- identifier collection source.</p></li><li><p>Exactly one of the following:</p><ul><li><p>A <code>disambigIdent</code> attribute that contains a string that represents the disambiguation
- identifier for the disambiguation target that is valid within the specified disambiguation source.</p></li><li><p>A <code>disambigIdentPointer</code> attribute that contains a <a href="#selectors" shape="rect">relative selector</a>
- pointing to a node that represents a unique identifier for the disambiguation target.</p></li></ul></li></ul></li><li><p>Or:</p><ul><li><p>Exactly one of the following:</p><ul><li><p>A <code>disambigIdentRef</code> attribute that contains an URI that represents a unique identifier
- for the disambiguation target.</p></li><li><p>A <code>disambigIdentRefPointer</code> attribute that contains a <a href="#selectors" shape="rect">relative selector</a>
- pointing to a node that holds a URI that represents a unique identifier for the disambiguation target.</p></li></ul></li></ul></li><li><p>None or exactly one of the following:</p><ul><li><p>A <code>disambigClassPointer</code> attribute that contains a <a href="#selectors" shape="rect">relative selector</a>
- pointing to a node specifying the entity type class behind the selector.</p></li><li><p>A <code>disambigClassRef</code> attribute that contains a URI, specifying the type class of the concept
- or entity behind the selector.</p></li><li><p>A <code>disambigClassRefPointer</code> attribute that contains a <a href="#selectors" shape="rect">relative selector</a>
- pointing to a node that holds a URI that specifies the entity type class behind the selector.</p></li></ul></li><li><p>An optional <code>disambigGranularity</code> attribute that contains a string, specifying the granularity
- level of the disambiguation. The value can be one of the following identifiers:
- <code>lexicalConcept</code>, <code>ontologyConcept</code>, or <code>entity</code>.</p></li></ul><span class="editor-note">[Ed. note: Below will need a test case in the test suite.]</span><span class="editor-note">[Ed. note: Sentence below is awkward]</span><p id="disambiguation-use-cases">When using a disambiguation rule, the user <a href="#rfc2119" shape="rect">MUST</a> use one of the use
- cases for disambiguation: specifying the target type, or specifying the target identity.
- For the latter, the user <a href="#rfc2119" shape="rect">MUST</a> use only one of the two addressing modes:</p><ul><li><p>Using <code>disambigSource</code> and one of <code>disambigIdent</code> or <code>disambigIdentPointer</code> to specify the
+ nodes to which this rule applies.</p></li><li><p>An optional <code>disambigGranularity</code> attribute that contains a string, specifying the granularity
+ level of the disambiguation. The value can be one of the following identifiers:
+ <code>lexicalConcept</code>, <code>ontologyConcept</code>, or <code>entity</code>.</p></li><li><p>At least one of the following:
+ <ul><li><p>To specify the target type class, exactly one of the following:
+ <ul><li><p>A <code>disambigClassPointer</code> attribute that contains a <a href="#selectors" shape="rect">relative selector</a>
+ pointing to a node specifying the entity type class behind the selector.</p></li><li><p>A <code>disambigClassRef</code> attribute that contains a URI, specifying the type class of the concept
+ or entity behind the selector.</p></li><li><p>A <code>disambigClassRefPointer</code> attribute that contains a <a href="#selectors" shape="rect">relative selector</a>
+ pointing to a node that holds a URI that specifies the entity type class behind the selector.</p></li></ul></p></li><li><p>To specify the target identity, exactly one of the following:<ul><li><p>When using addressing mode 1:</p><ul><li><p>A <code>disambigSource</code> attribute that contains a string representing the disambiguation
+ identifier collection source.</p></li><li><p>Exactly one of the following:</p><ul><li><p>A <code>disambigIdent</code> attribute that contains a string that represents the disambiguation
+ identifier for the disambiguation target that is valid within the specified disambiguation source.</p></li><li><p>A <code>disambigIdentPointer</code> attribute that contains a <a href="#selectors" shape="rect">relative selector</a>
+ pointing to a node that represents a unique identifier for the disambiguation target.</p></li></ul></li></ul></li><li><p>When using addressing mode 2:</p><ul><li><p>Exactly one of the following:</p><ul><li><p>A <code>disambigIdentRef</code> attribute that contains an URI that represents a unique identifier
+ for the disambiguation target.</p></li><li><p>A <code>disambigIdentRefPointer</code> attribute that contains a <a href="#selectors" shape="rect">relative selector</a>
+ pointing to a node that holds a URI that represents a unique identifier for the disambiguation target.</p></li></ul></li></ul></li></ul></p></li></ul></p></li></ul><span class="editor-note">[Ed. note: Below will need a test case in the test suite.]</span><p id="disambiguation-use-cases">When using a disambiguation rule specifying the target identity,
+ the user <a href="#rfc2119" shape="rect">MUST</a> use only one of the two addressing modes:</p><ul><li><p>Using <code>disambigSource</code> and one of <code>disambigIdent</code> or <code>disambigIdentPointer</code> to specify the
collection and the identifier itself.</p></li><li><p>Using one of <code>disambigIdentRef</code> or <code>disambigIdentRefPointer</code> using
a URI for the disambiguation target.</p></li></ul><div class="exampleOuter"><div class="exampleHeader"><a name="EX-disambiguation-global-1" id="EX-disambiguation-global-1" shape="rect"/>Example 52: Usage of <code>disambigClassRef</code>, <code>disambigGranularity</code>, <code>disambigIdentRef</code>,
<code>disambigSource</code> and <code>disambigIdent</code> for both entity and word sense disambiguation.</div><div class="exampleInner"><pre xml:space="preserve"><span class="hl-directive" style="color: maroon"><?xml version="1.0"?></span>
@@ -2093,13 +2094,17 @@
<strong class="hl-tag" style="color: #000096"></text></strong>
</pre></div><p>[Source file: <a href="examples/xml/EX-disambiguation-global-1.xml" shape="rect">examples/xml/EX-disambiguation-global-1.xml</a>]</p></div><p id="disambiguation-local">LOCAL: The following local markup is
available for the <a href="#Disambiguation" shape="rect">Disambiguation</a>
- data category:</p><ul><li><p>An optional <code>disambigClassRef</code> attribute that contains a URI, specifying the type class
- of the concept or entity behind the selector.</p></li><li><p>An optional <code>disambigGranularity</code> attribute that contains a string, specifying the
- granularity level of the disambiguation. The value can be one of the following identifiers: <code>lexicalConcept</code>, <code>ontologyConcept</code>, or <code>entity</code></p></li><li><p>Either:</p><ul><li><p>A <code>disambigSource</code> attribute that contains a string representing the
- disambiguation identifier collection source.</p></li><li><p>A <code>disambigIdent</code> attribute that contains a string, representing the
- disambiguation identifier for the disambiguation target that is valid within the specified
- disambiguation source.</p></li></ul></li><li><p>Or:</p><ul><li><p>A <code>disambigIdentRef</code> attribute that contains a URI that represents a unique
- identifier for the disambiguation target.</p></li></ul></li></ul><p>The user <a href="#rfc2119" shape="rect">MUST</a> use only one of the two addressing modes for "target identity" disambiguation:</p><ul><li><p>Using <code>disambigSource</code> and <code>disambigIdent</code> to specify the collection
+ data category:</p><ul><li><p>An optional <code>disambigGranularity</code> attribute that contains a string, specifying the
+ granularity level of the disambiguation. The value can be one of the following identifiers: <code>lexicalConcept</code>, <code>ontologyConcept</code>, or <code>entity</code></p></li><li><p>At least one of the following:
+ <ul><li><p>To specify the target type class:
+ <ul><li><p>A <code>disambigClassRef</code> attribute that contains a URI, specifying the type class
+ of the concept or entity behind the selector.</p></li></ul></p></li><li><p>To specify the target identity, exactly one of the following:
+ <ul><li><p>When using addressing mode 1:</p><ul><li><p>A <code>disambigSource</code> attribute that contains a string representing the
+ disambiguation identifier collection source.</p></li><li><p>A <code>disambigIdent</code> attribute that contains a string, representing the
+ disambiguation identifier for the disambiguation target that is valid within the specified
+ disambiguation source.</p></li></ul></li><li><p>When using addressing mode 2:</p><ul><li><p>A <code>disambigIdentRef</code> attribute that contains a URI that represents a unique
+ identifier for the disambiguation target.</p></li></ul></li></ul></p></li></ul></p></li></ul><p>When specifying the target identity,
+ the user <a href="#rfc2119" shape="rect">MUST</a> use only one of the two addressing modes:</p><ul><li><p>Using <code>disambigSource</code> and <code>disambigIdent</code> to specify the collection
and the identifier itself.</p></li><li><p>Using <code>disambigIdentRef</code> using a URI for the disambiguation target</p></li></ul><div class="exampleOuter"><div class="exampleHeader"><a name="EX-disambiguation-html5-local-1" id="EX-disambiguation-html5-local-1" shape="rect"/>Example 53: Local mixed usage of Usage of <code>disambigClassRef</code>, <code>disambigGranularity</code>,
and <code>disambigIdentRef</code> in HTML.</div><div class="exampleInner"><pre xml:space="preserve"><strong class="hl-tag" style="color: blue"><!DOCTYPE html></strong>
<strong class="hl-tag" style="color: #000096"><html</strong> <span class="hl-attribute" style="color: #F5844C">lang</span>=<span class="hl-value" style="color: #993300">"en"</span><strong class="hl-tag" style="color: #000096">></strong>
@@ -2120,7 +2125,7 @@
<strong class="hl-tag" style="color: #000096"></body></strong>
<strong class="hl-tag" style="color: #000096"></html></strong></pre></div><p>[Source file: <a href="examples/html5/EX-disambiguation-html5-local-1.html" shape="rect">examples/html5/EX-disambiguation-html5-local-1.html</a>]</p></div><div class="note"><p class="prefix"><b>Note:</b></p><p>For referring to <code>disambigClassRef</code> values, implementors are encouraged to use an existing
repository of entity types as long as they satisfy their requirements. For example,
- the Named Entity Recognition and Disambiguation ontology (NERD): http://nerd.eurecom.fr/ontology</p><p>Furthermore, valid target types depend on the disambiguation granularity: types of entities are distinct
+ the Named Entity Recognition and Disambiguation ontology <a title="" href="#nerd" shape="rect">[NERD]</a>.</p><p>Furthermore, valid target types depend on the disambiguation granularity: types of entities are distinct
from types of lexical concepts or ontology concepts. While this distinction exists, the specification does not prescribe
a way of automatically inferring a disambiguation level from a target type.</p><p>When serializing the ITS mark-up in HTML5, the preferred way is to serialize in RDFa Lite or Microdata due
to the existing search and crawling infrastructure that is able to consume this kind of data.</p></div><div class="exampleOuter"><div class="exampleHeader"><a name="EX-disambiguation-html5-rdfa" id="EX-disambiguation-html5-rdfa" shape="rect"/>Example 54: Local mixed usage of <code>entityTypeSourceRef</code>, <code>enttiyTypeRef</code>, <code>disambigSourceRef</code>,
@@ -3735,9 +3740,7 @@
value even if the specific instance of the issue might be mapped
to another category.</p></li></ul>
</td></tr></tbody></table></div><div class="div1">
-<h2><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="informative-references" id="informative-references" shape="rect"/>C References (Non-Normative)</h2><span class="editor-note">[Ed. note: Need to complete entry for provenance data model.]</span><dl><dt class="label"><a name="prov-dm" id="prov-dm" shape="rect"/>PROV-DM</dt><dd>Editors tbd.
- <a href="http://www.w3.org/TR/prov-dm/" shape="rect">Provenance data model</a>. Details to be completed.
- </dd><dt class="label"><a name="bidiarticle" id="bidiarticle" shape="rect"/>Bidi Article</dt><dd>Richard Ishida. <a href="http://www.w3.org/International/articles/inline-bidi-markup/" shape="rect"><cite>What you need to know about the bidi algorithm and inline
+<h2><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="informative-references" id="informative-references" shape="rect"/>C References (Non-Normative)</h2><span class="editor-note">[Ed. note: Need to complete entry for provenance data model.]</span><dl><dt class="label"><a name="bidiarticle" id="bidiarticle" shape="rect"/>Bidi Article</dt><dd>Richard Ishida. <a href="http://www.w3.org/International/articles/inline-bidi-markup/" shape="rect"><cite>What you need to know about the bidi algorithm and inline
markup</cite></a>. Article of the <a href="http://www.w3.org/International/" shape="rect">W3C Internationalization
Activity</a>, June 2005.</dd><dt class="label"><a name="checkmate" id="checkmate" shape="rect"/>CheckMate Quality Check</dt><dd>Okapi Project. <a href="http://www.opentag.com/okapi/wiki/index.php?title=CheckMate_-_Quality_Check_Configuration" shape="rect"><cite>CheckMate – Quality Check Configuration</cite></a>. Available at
<a href="http://www.opentag.com/okapi/wiki/index.php?title=CheckMate_-_Quality_Check_Configuration" shape="rect">http://www.opentag.com/okapi/wiki/index.php?title=CheckMate_-_Quality_Check_Configuration</a>.</dd><dt class="label"><a name="css2-1" id="css2-1" shape="rect"/>CSS 2.1</dt><dd> Bert Bos, Tantek Çelik, Ian Hickson Håkon
@@ -3763,14 +3766,18 @@
<a href="http://people.w3.org/rishida/localizable-dtds/" shape="rect"><cite>Requirements for Localizable DTD Design</cite></a>. Working
Draft 7 July 2003. Available at <a href="http://people.w3.org/rishida/localizable-dtds/" shape="rect">http://people.w3.org/rishida/localizable-dtds/</a>. </dd><dt class="label"><a name="css3-selectors" id="css3-selectors" shape="rect"/>CSS Selectors Level 3</dt><dd>Tantek Çelik, Elika J.
Etemad, Daniel Glazman, Ian Hickson, Peter Linss, John Williams <a href="http://www.w3.org/TR/css3-selectors/" shape="rect"><cite>Selectors Level
- 3</cite></a>. W3C Recommendation 29 September 2011. Available at <a href="http://www.w3.org/TR/css3-selectors/" shape="rect">http://www.w3.org/TR/css3-selectors/</a>.</dd><dt class="label"><a name="nvdl" id="nvdl" shape="rect"/>NVDL</dt><dd>Information technology -- Document Schema
+ 3</cite></a>. W3C Recommendation 29 September 2011. Available at <a href="http://www.w3.org/TR/css3-selectors/" shape="rect">http://www.w3.org/TR/css3-selectors/</a>.</dd><dt class="label"><a name="nerd" id="nerd" shape="rect"/>NERD</dt><dd>Named Entity Recognition and Disambiguation ontology (NERD)
+ available at: <a href="http://nerd.eurecom.fr/ontology" shape="rect">http://nerd.eurecom.fr/ontology</a>
+ </dd><dt class="label"><a name="nvdl" id="nvdl" shape="rect"/>NVDL</dt><dd>Information technology -- Document Schema
Definition Languages (DSDL) -- Part 4: <cite>Namespace-based Validation
Dispatching Language (NVDL)</cite>. International Organization for
Standardization (ISO) ISO/IEC 19757-4:2003.</dd><dt class="label"><a name="opendocument" id="opendocument" shape="rect"/>OpenDocument</dt><dd>Michael Brauer et al. <a href=" https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=office" shape="rect"><cite>OASIS Open Document Format for Office Applications
(OpenDocument).</cite></a>. Oasis Standard 1 May 2005. Available at <a href=" https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=office" shape="rect">
https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=office</a>.
The latest version of <a href=" https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=office" shape="rect"> OpenDocument</a> is available at
- https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=office.</dd><dt class="label"><a name="rfc3066" id="rfc3066" shape="rect"/>RFC 3066</dt><dd>Harald Alvestrand. <a href="http://www.ietf.org/rfc/rfc3066.txt" shape="rect"><cite>Tags for the
+ https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=office.</dd><dt class="label"><a name="prov-dm" id="prov-dm" shape="rect"/>PROV-DM</dt><dd>Editors tbd.
+ <a href="http://www.w3.org/TR/prov-dm/" shape="rect">Provenance data model</a>. Details to be completed.
+ </dd><dt class="label"><a name="rfc3066" id="rfc3066" shape="rect"/>RFC 3066</dt><dd>Harald Alvestrand. <a href="http://www.ietf.org/rfc/rfc3066.txt" shape="rect"><cite>Tags for the
Identification of Languages</cite></a>. RFC 3066, January 2001.
Available at <a href="http://www.ietf.org/rfc/rfc3066.txt" shape="rect">http://www.ietf.org/rfc/rfc3066.txt</a>.</dd><dt class="label"><a name="ruby-tr" id="ruby-tr" shape="rect"/>Ruby-TR</dt><dd>Marcin Sawicki (until 10 October, 1999),
Michel Suignard, Masayasu Ishikawa (石川 雅康), Martin Dürst, Tex Texin, <a href="http://www.w3.org/TR/ruby/" shape="rect"><cite>Ruby Annotation</cite></a>. W3C Recommendation 31 May 2001. Available at <a href="http://www.w3.org/TR/2001/REC-ruby-20010531/" shape="rect">
@@ -3820,7 +3827,7 @@
<em>This section is informative.</em>
</p><p>Several constraints of ITS markup cannot be validated with ITS schemas. The
following <a title="Rule-based validation
							-- Schematron" href="#schematron" shape="rect">[Schematron]</a> document allows for
- validating some of these constraints.</p><div class="exampleOuter"><div class="exampleHeader"><a name="d0e9996" id="d0e9996" shape="rect"/>Example 105: Testing constraints in ITS markup</div><div class="exampleInner"><pre xml:space="preserve"><strong class="hl-tag" style="color: #000096"><schema</strong> <span class="hl-attribute" style="color: #F5844C">xmlns</span>=<span class="hl-value" style="color: #993300">"http://www.ascc.net/xml/schematron"</span><strong class="hl-tag" style="color: #000096">></strong>
+ validating some of these constraints.</p><div class="exampleOuter"><div class="exampleHeader"><a name="d0e10014" id="d0e10014" shape="rect"/>Example 105: Testing constraints in ITS markup</div><div class="exampleInner"><pre xml:space="preserve"><strong class="hl-tag" style="color: #000096"><schema</strong> <span class="hl-attribute" style="color: #F5844C">xmlns</span>=<span class="hl-value" style="color: #993300">"http://www.ascc.net/xml/schematron"</span><strong class="hl-tag" style="color: #000096">></strong>
<em class="hl-comment" style="color: silver"><!-- Schematron document to test constraints for global and local ITS markup.
For ITS markup definitions, see http://www.w3.org/TR/its/ . --></em>
<strong class="hl-tag" style="color: #000096"><ns</strong> <span class="hl-attribute" style="color: #F5844C">prefix</span>=<span class="hl-value" style="color: #993300">"its"</span> <span class="hl-attribute" style="color: #F5844C">uri</span>=<span class="hl-value" style="color: #993300">"http://www.w3.org/2005/11/its"</span><strong class="hl-tag" style="color: #000096">/></strong>
@@ -3867,7 +3874,7 @@
</p><p>The following <a title="Namespace-based Validation
							Dispatching Language (NVDL)" href="#nvdl" shape="rect">[NVDL]</a> document allows validation of
ITS markup which has been added to a host vocabulary. Only ITS elements and
attributes are checked. Elements and attributes of host language are ignored
- during validation against this NVDL document/schema.</p><div class="exampleOuter"><div class="exampleHeader"><a name="d0e10018" id="d0e10018" shape="rect"/>Example 106: NVDL schema for ITS</div><div class="exampleInner"><pre xml:space="preserve"><span class="hl-directive" style="color: maroon"><?xml version="1.0" encoding="UTF-8"?></span>
+ during validation against this NVDL document/schema.</p><div class="exampleOuter"><div class="exampleHeader"><a name="d0e10036" id="d0e10036" shape="rect"/>Example 106: NVDL schema for ITS</div><div class="exampleInner"><pre xml:space="preserve"><span class="hl-directive" style="color: maroon"><?xml version="1.0" encoding="UTF-8"?></span>
<strong class="hl-tag" style="color: #000096"><rules</strong> <span class="hl-attribute" style="color: #F5844C">xmlns</span>=<span class="hl-value" style="color: #993300">"http://purl.oclc.org/dsdl/nvdl/ns/structure/1.0"</span><strong class="hl-tag" style="color: #000096">></strong>
<strong class="hl-tag" style="color: #000096"><namespace</strong> <span class="hl-attribute" style="color: #F5844C">ns</span>=<span class="hl-value" style="color: #993300">"http://www.w3.org/2005/11/its"</span><strong class="hl-tag" style="color: #000096">></strong>
<strong class="hl-tag" style="color: #000096"><validate</strong> <span class="hl-attribute" style="color: #F5844C">schema</span>=<span class="hl-value" style="color: #993300">"its20-elements.rng"</span><strong class="hl-tag" style="color: #000096">/></strong> 
@@ -3925,7 +3932,7 @@
</html></span></pre></div></div><p>Case 3: The NLP annotation created in NIF starts in one region and ends in another. Solution: No straight mapping is possible; a mapping can be created if both regions have the same parent.</p></div><div class="div1">
<h2><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="revisionlog" id="revisionlog" shape="rect"/>H Revision Log (Non-Normative)</h2><p id="changelog-since-20121023">The following log records major changes that
have been made to this document since the <a href="http://www.w3.org/TR/2012/WD-its20-20121023/" shape="rect">ITS 2.0 Working Draft
- 23 October 2012</a>.</p><ul><li><p>Clarified usage of <a href="#domain" shape="rect">Domain</a> data category in HTML5 in response to <a href="https://www.w3.org/International/multilingualweb/lt/track/issues/56" shape="rect">issue-56</a>.</p></li><li><p>Added the <a href="#lqissueDefs" shape="rect">enabled information</a> in <a class="section-ref" href="#lqissue" shape="rect">Section 6.18: Localization Quality Issue</a>.</p></li></ul><p id="changelog-since-20120829">The following log records major changes that
+ 23 October 2012</a>.</p><ul><li><p>Clarified usage of <a href="#domain" shape="rect">Domain</a> data category in HTML5 in response to <a href="https://www.w3.org/International/multilingualweb/lt/track/issues/56" shape="rect">issue-56</a>.</p></li><li><p>Added the <a href="#lqissueDefs" shape="rect">enabled information</a> in <a class="section-ref" href="#lqissue" shape="rect">Section 6.18: Localization Quality Issue</a>.</p></li><li><p>Updated the <a href="#Disambiguation" shape="rect">Disambiguation</a> data category.</p></li></ul><p id="changelog-since-20120829">The following log records major changes that
have been made to this document since the <a href="http://www.w3.org/TR/2012/WD-its20-20120829/" shape="rect">ITS 2.0 Working Draft
29 August 2012</a>.</p><ol class="depth1"><li><p>Added a first draft of <a class="section-ref" href="#translation-agent-provenance" shape="rect">Section 6.12: Translation Agent Provenance</a></p></li><li><p>Added <a class="section-ref" href="#html5-markup" shape="rect">Section 7: Using ITS Markup in HTML5</a>.</p></li><li><p>Removed inline markup declarations.</p></li><li><p>Addition of a <code>locQualityPrecisVote</code> attribute and a
<code>locQualityPrecisVotePointer</code> attribute to <a class="section-ref" href="#lqprecis" shape="rect">Section 6.19: Localization Quality Précis</a>.</p></li><li><p>A <a href="#its-information_versus_content" shape="rect">clarification</a> of ITS
Received on Saturday, 27 October 2012 12:13:35 UTC