- From: Yves Savourel via cvs-syncmail <cvsmail@w3.org>
- Date: Wed, 14 Nov 2012 14:16:04 +0000
- To: public-multilingualweb-lt-commits@w3.org
Update of /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20
In directory hutz:/tmp/cvs-serv11083
Modified Files:
its20.html its20.odd
Log Message:
Changes from editing call of Nov-14.
Index: its20.odd
===================================================================
RCS file: /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/its20.odd,v
retrieving revision 1.224
retrieving revision 1.225
diff -u -d -r1.224 -r1.225
--- its20.odd 12 Nov 2012 23:03:25 -0000 1.224
+++ its20.odd 14 Nov 2012 14:16:01 -0000 1.225
@@ -2812,11 +2812,7 @@
<note><p>The structure of the content model for the <gi>ruby</gi> element is
identical with the structure of ruby markup as defined in <ptr
type="bibref" target="#html5"/>.</p>
- <p>The structure of ruby defined in section 5.4 of <ptr type="bibref"
- target="#opendocument"/> is also compliant with ruby defined in
- this specification.</p>
</note>
- <note type="ed">Need to reevaluate above statement related to ODF.</note>
</div>
</div>
<div xml:id="language-information">
@@ -2828,7 +2824,7 @@
markup which expresses the language of the text selected by the selector
attribute. This markup <ref target="#rfc-keywords">MUST</ref> use values
that conform to <ptr type="bibref" target="#bcp47"/>. The recommended
- way to specify language identification is to use <code>xml:lang</code>.
+ way to specify language identification is to use <code>xml:lang</code> in XML, and <att>lang</att> in HTML5.
The <gi>langRule</gi> element is intended only as a fall-back mechanism
for documents where language is identified with another construct.</p>
<exemplum xml:id="EX-lang-definition-1">
@@ -2866,7 +2862,7 @@
identification and encompasses <ptr type="bibref" target="#rfc3066"
/> and its successors.)</p>
</note>
- <note type="ed">Add something about HTML5 lang</note>
+ <note type="ed">Add example for HTML5 and lang.</note>
</div>
<div xml:id="langinfo-implementation">
<head>Implementation</head>
@@ -3136,30 +3132,37 @@
<div xml:id="Disambiguation-definition">
<head>Definition</head>
<p>The <ref target="#Disambiguation">Disambiguation</ref> data category is used to
- indicate occurrences of specific concepts that may require special
- handling in the localization of the document.</p>
+ highlight (mark up) specific conceptual patterns that may require special treatment
+ when localizing and translating content.</p>
<p>This data category can be used for several purposes, including, but not
limited to:</p>
<list type="unordered">
- <item>Informing translation systems that this fragment of text may not be literally translated, but subject to specific proper name translation rules or official translations, as well as a very specific meaning of the phrases.</item>
- <item>Informing content management and translation systems about the type of the underlying entity in order to enable processing based on a specific type of the target, for example, when handling personal names, product names or geographic names, chemical compounds, protein names and similar.</item>
+ <item>Informing a translation service that a certain fragment of text is subject to follow specific
+ translation rules, e.g. for proper names, or officially regulated translations, as well as to
+ conveying a very specific meaning of the fragment.</item>
+ <item>Informing content management systems and translation services about the intended conceptual
+ type of a textual entity in order to enable processing based on this specific type for source and target
+ languages, for example, when dealing with personal names, product names, or geographic names,
+ chemical compounds, protein names, and so forth.</item>
</list>
- <p>Disambiguation is achieved by associating a selected fragment of text with an external web resource that can be referenced
- by a translation or linguistic review agent in order to access the correct meaning or lexical use of the text and thereby
- informing its translation.</p>
- <p>A fragment of text can be disambiguated at different granularities, i.e. as a lexical concept, as an ontology concept,
- or as a named entity.</p>
- <p>As a lexical concept, the external reference can provide synonyms and example usage, e.g. using
- service such as Wordnet.</p>
- <p>As an ontology concept, the external reference can provide a formal conceptual definition within
- a framework of related concepts.</p>
- <p>As a named entity, the external reference can provide a description of the real world entity the text intends
- to convey. For instance, the word 'City' in 'I am going to the City' may be disambiguated in one of the WordNet
- synsets that can be represented by 'city', an ontology concept of a City that could represent a subclass of a
- “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>Disambiguation support is achieved by associating a marked up fragment of text with an external web resource
+ that can be dereferenced by a language review agent, i.e. by accessing the intended meaning or lexical choice of
+ the fragment, and thereby contributing to its correct translation.</p>
+ <p>A fragment of text is disambiguated at different granularities: (1) lexical type, (2) ontological concept,
+ or (3) named entity.</p>
+ <p>In the case of lexical type, the external resource may provide appropriate synonyms and example usage, such
+ as, for example, the WordNet services do.</p>
+ <p>In the case of ontological concept, the external resource may provide a formalized conceptual definition arranged
+ in a hierarchical framework of related concepts.</p>
+ <p>In the case of a named entity, the external resource may provide a fully fledged description of the associated
+ real world entity. For instance, the word 'City' in the fragment 'I am going to the City' may be disambiguated on
+ the basis of one of WordNet's synsets that can be represented by 'city', an ontological concept of 'City' that
+ could represent a subclass of 'Populated Place' at the conceptual granularity level, or the central area of a
+ particular city, e.g. 'City of London', as interpreted at the entity granularity level.</p>
+ <p>Emerging linked data networks, such as DBpedia, further increase the interlinking of ontological concepts and
+ named entity definitions for same things and in different languages, thereby offering the possibility to directly
+ facilitate translation through a source language description.</p>
+ <note type="ed">Edits from Jorg on Disambiguation have been entered up to this point, not below.</note>
<p>Two types of disambiguation are possible:</p>
<list type="unordered">
@@ -4075,7 +4078,6 @@
</list>
</item>
</list>
- <note type="ed">Why does below say "do not apply to HMTL as local markup"? There is local markup for direction annotation in XML too.</note>
<note>
<p>The attributes <att>locQualityIssuesRefPointer</att>,
<att>locQualityIssueTypePointer</att>,
@@ -4162,7 +4164,7 @@
<item><p>An element <gi>locQualityIssues</gi> (or <code><span
loc-quality-issues></code> in HTML) which
contains:</p>
- <note type="ed">Should locQualityIssues also be defined for global rules? It seems not to be specific to local.</note>
+ <note type="ed">Add an example using standoff on an attribute.</note>
<list type="unordered">
<item><p>One or more elements <gi>locQualityIssue</gi>
(or <code><span its-loc-quality-issue></code>
@@ -4263,7 +4265,8 @@
target="examples/html5/EX-locQualityIssue-html5-local-2.html"
type="html5"/>
</exemplum>
- <note type="ed">TODO for above (not only as an example, in general): document that for using standoff in HTML5, there needs to be the same id in HTML "script" and in the embedded XML. This is needed also for the other standoff case (provenance).</note>
+ <note type="ed">TODO for in general: make sure standoff examples in HTML5
+ use the 'script' notation.</note>
</div>
</div>
@@ -4533,7 +4536,9 @@
<p xml:id="mtconfidence-local">LOCAL: the following local markup is
available for the <ref target="#mtconfidence">MT Confidence</ref> data
category:</p>
- <note type="ed">Missing the <ref target="http://lists.w3.org/Archives/Public/public-multilingualweb-lt/2012Oct/0384.html">local mtconfidencescore attribute</ref>.</note>
+ <note type="ed">Need to update the data category with
+ <ref target="http://lists.w3.org/Archives/Public/public-multilingualweb-lt/2012Oct/0384.html">local mtConfidenceScore attribute</ref>
+ and the toolsRef attribute.</note>
<list type="unordered">
<item><p>An mtProducer attribute that contains a string identifying the
Machine Translation Platform, e.g. “Bing Translator”, “Google
@@ -5486,7 +5491,6 @@
<div type="inform" xml:id="informative-references">
<head>References</head>
- <note type="ed">Need to complete entry for provenance data model.</note>
<listBibl>
<bibl xml:id="bidiarticle" n="Bidi Article">Richard Ishida. <title>
<ref
@@ -5579,6 +5583,7 @@
https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=office.</bibl>
<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.
+ <note type="ed">Need to complete entry for provenance data model.</note>
</bibl>
<bibl xml:id="rfc3066" n="RFC 3066">Harald Alvestrand. <title><ref
target="http://www.ietf.org/rfc/rfc3066.txt">Tags for the
Index: its20.html
===================================================================
RCS file: /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/its20.html,v
retrieving revision 1.227
retrieving revision 1.228
diff -u -d -r1.227 -r1.228
--- its20.html 12 Nov 2012 23:03:24 -0000 1.227
+++ its20.html 14 Nov 2012 14:16:01 -0000 1.228
@@ -207,48 +207,48 @@
identification.</p><div class="exampleOuter"><div class="exampleHeader"><a name="d0e339" id="d0e339" shape="rect"/>Example 1: Document with partially translatable content</div><p>In this document it is difficult to distinguish between those
<code>string</code> elements that are translatable and those that
are not. Only the addition of an explicit flag could resolve the
- issue.</p><div class="exampleInner"><pre xml:space="preserve"><strong class="hl-tag" style="color: #000096"><resources></strong>
- <strong class="hl-tag" style="color: #000096"><section</strong> <span class="hl-attribute" style="color: #F5844C">id</span>=<span class="hl-value" style="color: #993300">"Homepage"</span><strong class="hl-tag" style="color: #000096">></strong>
- <strong class="hl-tag" style="color: #000096"><arguments></strong>
- <strong class="hl-tag" style="color: #000096"><string></strong>page<strong class="hl-tag" style="color: #000096"></string></strong>
- <strong class="hl-tag" style="color: #000096"><string></strong>childlist<strong class="hl-tag" style="color: #000096"></string></strong>
- <strong class="hl-tag" style="color: #000096"></arguments></strong>
- <strong class="hl-tag" style="color: #000096"><variables></strong>
- <strong class="hl-tag" style="color: #000096"><string></strong>POLICY<strong class="hl-tag" style="color: #000096"></string></strong>
[...3228 lines suppressed...]
+ <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> 
+ <strong class="hl-tag" style="color: #000096"></namespace></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> <span class="hl-attribute" style="color: #F5844C">match</span>=<span class="hl-value" style="color: #993300">"attributes"</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-attributes.rng"</span><strong class="hl-tag" style="color: #000096">/></strong>
+ <strong class="hl-tag" style="color: #000096"></namespace></strong>
+ <strong class="hl-tag" style="color: #000096"><anyNamespace></strong>
+ <strong class="hl-tag" style="color: #000096"><allow/></strong>
+ <strong class="hl-tag" style="color: #000096"></anyNamespace></strong>
<strong class="hl-tag" style="color: #000096"></rules></strong></pre></div><p>[Source file: <a href="schemas/its20.nvdl" shape="rect">schemas/its20.nvdl</a>]</p></div><p>The NVDL schema depends on the following two schemas:</p><ul><li><p>
<a href="schemas/its20-elements.rng" shape="rect">RELAX NG schema for ITS elements</a>
</p></li><li><p>
@@ -3950,7 +3958,7 @@
23 October 2012</a>.</p><ol class="depth1"><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><li><p>Fine tuned the algorithm to compute the result values of the <a href="#domain" shape="rect">Domain</a> data category.</p></li><li><p>Fix on <a href="#EX-locQualityIssue-html5-local-2" shape="rect">Example 85</a>: <code>id</code> attribute of <code>script</code> element now the same as of containing XML.</p></li><li><p>NIF example fix - see <a href="https://www.w3.org/International/multilingualweb/lt/track/actions/284" shape="rect">action-284</a>.</p></li>li><p>Added <a href="#css-selectors-feature-at-risk" shape="rect">a note</a> to mark CSS selectors as feature at risk, see <a href="https://www.w3.org/International/multilingualweb/lt/track/actions/272" shape="rect">action-272</a>.</p></li><li><p>Defined in <a class="section-ref" href="#xpath-relative-selector" shape="rect">Section 5.3.2.2: Relative selector</a> that an XPath based relative selector can also be an absolute location path - see the <code>domainPointer</code> attribute in <a href="#EX-domain-2" shape="rect">Example 51</a> and <a href="https://www.w3.org/International/multilingualweb/lt/track/actions/282" shape="rect">action-282</a>.</p></li><li><p>Defined <a href="#directionality" shape="rect">Directionality</a> and <a href="#ruby-annotation" shape="rect">Ruby</a> as non-normative features. See <a class="section-ref" href="#relation-to-its10" shape="rect">Section 1.1.1: Relation to ITS 1.0</a>, <a href="#directionality-non-normative-explanation" shape="rect">note on directionality</a>, <a hrf="#ruby-non-normative-explanation" shape="rect">note on ruby</a>, and <a href="https://www.w3.org/International/multilingualweb/lt/track/actions/250" shape="rect">action-250</a>.</p></li><li><p>Update on <a href="#Disambiguation" shape="rect">Disambiguation</a> example <a href="#EX-disambiguation-html5-rdfa-companion-document" shape="rect">Example 54</a>. See <a href="https://www.w3.org/International/multilingualweb/lt/track/actions/266" shape="rect">action-266</a> (<a href="http://www.w3.org/2012/11/01-mlw-lt-irc#T10-53-44" shape="rect">related discussion</a>).</p></li><li><p>Made a simplification of <a href="#disambiguation-global" shape="rect">Disambiguation used global</a>. See <a href="https://www.w3.org/International/multilingualweb/lt/track/actions/267" shape="rect">action-267</a>.</p></li><li><p>Added <a class="section-ref" href="#its-mime-type" shape="rect">Appendix B: Internationalization Tag Set (ITS) MIME Type</a>, see <a href="https://www.w3.org/International/multilingualweb/lt/track/actions/51" shape="rect">action-251</a>.</p></li></ol><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
+ <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
data category information and processing of content in <a class="section-ref" href="#datacategories-defaults-etc" shape="rect">Section 6.1: Position, Defaults, Inheritance and Overriding of Data Categories</a>.</p></li><li><p>Added <a class="section-ref" href="#allowedchars" shape="rect">Section 6.21: Allowed Characters</a>.</p></li><li><p>Added <a class="section-ref" href="#storagesize" shape="rect">Section 6.22: Storage Size</a>.</p></li><li><p>Added <a class="section-ref" href="#mtconfidence" shape="rect">Section 6.20: MT Confidence</a>.</p></li><li><p>Added <a href="#qa-issue-types-tool-specific-mappings" shape="rect">a note</a>
about informative mappings of <a href="#lqissue-typevalues" shape="rect">Values for
the Localization Quality Issue Type</a> to the <a href="http://www.w3.org/International/its/wiki/Tool_specific_mappings" shape="rect">ITS IG wiki</a>.</p></li><li><p>Added a <a href="#its-conformance-2-3" shape="rect">conformance clause</a>
Received on Wednesday, 14 November 2012 14:16:06 UTC