- From: CVS User fsasaki <cvsmail@w3.org>
- Date: Mon, 21 Oct 2013 20:10:35 +0000
- To: public-multilingualweb-lt-commits@w3.org
Update of /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20
In directory gil:/tmp/cvs-serv30137
Modified Files:
its20.odd
Log Message:
made schema section non normative, in response to AC review. Other fixes: bibliography formatting, added non-normative MQM reference.
--- /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/its20.odd 2013/10/14 07:50:59 1.519
+++ /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/its20.odd 2013/10/21 20:10:35 1.520
@@ -4716,9 +4716,9 @@
<bibl xml:id="relaxng" n="RELAX NG">Information technology – Document Schema Definition
Language (DSDL) – Part 2: <title>Regular-grammar-based validation – RELAX NG</title>.
International Organization for Standardization (ISO) ISO/IEC 19757-2:2003.</bibl>
- <bibl xml:id="rfc2119" n="RFC 2119">S. Bradner. <ref
+ <bibl xml:id="rfc2119" n="RFC 2119">S. Bradner. <title><ref
target="http://www.ietf.org/rfc/rfc2119.txt">Key Words for use in RFCs to Indicate
- Requirement Levels</ref>. IETF RFC 2119, March 1997. Available at <ref
+ Requirement Levels</ref></title>. IETF RFC 2119, March 1997. Available at <ref
target="http://www.ietf.org/rfc/rfc2119.txt">
http://www.ietf.org/rfc/rfc2119.txt</ref>. </bibl>
<bibl xml:id="rfc3987" n="RFC 3987">Martin Dürst, Michel Suignard. <title>
@@ -5293,13 +5293,14 @@
</cell>
</row>
</table>
- <note><p>Note: <code>uncategorized</code> is used for issues that have not (yet) been categorized into a more specific value. For example, an automatic process might flag issues for attention but not provide any further detail or categorization: such issues would be listed as <code>uncategorized</code> in ITS 2.0. It may also be used when the exact nature of an issue is unclear and it cannot be categorized as a result (e.g., text is seriously garbled and the cause it unclear). By contrast other is used when the nature of an issue is clear but it cannot be categorized in one of the ITS 2.0 categories (or when a model or tool has its own “other” category). For example, in translation of subtitles there is a “respeaking” error category that does not correspond to any ITS 2.0 category and is highly specific to that environment; respeaking errors would therefore be categorized as <code>other</code> in ITS 2.0.</p></note>
+ <note><p>The value <code>uncategorized</code> is used for issues that have not (yet) been categorized into a more specific value. For example, an automatic process might flag issues for attention but not provide any further detail or categorization: such issues would be listed as <code>uncategorized</code> in ITS 2.0. It may also be used when the exact nature of an issue is unclear and it cannot be categorized as a result (e.g., text is seriously garbled and the cause it unclear). By contrast other is used when the nature of an issue is clear but it cannot be categorized in one of the ITS 2.0 categories (or when a model or tool has its own “other” category). For example, in translation of subtitles there is a “respeaking” error category that does not correspond to any ITS 2.0 category and is highly specific to that environment; respeaking errors would therefore be categorized as <code>other</code> in ITS 2.0.</p></note>
</div>
<div xml:id="its-schemas">
<head>Schemas for ITS</head>
<p>
- <emph>This section is normative.</emph>
+ <emph>This section is informative.</emph>
</p>
+ <note><p>The schemas are only informative and may be updated any time. An updated version of the schemas can be found in the <ref target="https://github.com/w3c/its-2.0-testsuite/tree/master/its2.0/schema">ITS 2.0 test suite</ref>.</p></note>
<p>The following schemas define ITS elements and attributes and can be used as building
blocks when you want to integrate ITS markup into your own XML vocabulary. You can see
examples of such integration in <ref target="http://www.w3.org/TR/xml-i18n-bp/">Best
@@ -5398,7 +5399,7 @@
http://www.w3.org/TR/2011/REC-CSS2-20110607/</ref>. The latest version of <ref
target="http://www.w3.org/TR/CSS21/">CSS2</ref> is available at
http://www.w3.org/TR/CSS21/.</bibl>
- <bibl xml:id="dbpedia" n="DBpedia">DBpedia available at: <ref
+ <bibl xml:id="dbpedia" n="DBpedia"><title>DBpedia</title>. Available at: <ref
target="http://dbpedia.org/OnlineAccess">http://dbpedia.org/OnlineAccess</ref>.</bibl>
<bibl xml:id="dita10" n="DITA 1.0">Michael Priestley, JoAnn Hackos, et. al., editors.
<title><ref
@@ -5411,9 +5412,9 @@
<ref target="http://www.docbook.org/">DocBook: The Definitive Guide</ref>
</title>. Available at <ref target="http://www.docbook.org/">
http://www.docbook.org/</ref>.</bibl>
- <bibl xml:id="geo-i18n-l10n" n="l10n i18n">Richard Ishida, Susan Miller. <ref
+ <bibl xml:id="geo-i18n-l10n" n="l10n i18n">Richard Ishida, Susan Miller. <title><ref
target="http://www.w3.org/International/questions/qa-i18n">Localization vs.
- Internationalization</ref>. Article of the <ref
+ Internationalization</ref></title>. Article of the <ref
target="http://www.w3.org/International/">W3C Internationalization Activity</ref>,
January 2006.</bibl>
<bibl xml:id="iso30042" n="ISO 30042">(International Organization for Standardization).
@@ -5443,10 +5444,11 @@
target="http://www.w3.org/TR/2012/WD-microdata-20121025/"
>http://www.w3.org/TR/2012/WD-microdata-20121025/</ref>. </bibl>
<bibl xml:id="mlw-metadata-us-impl" n="MLW US IMPL">Christian Lieske (ed.). <title><ref target="http://www.w3.org/TR/2013/WD-mlw-metadata-us-impl-20130307/">Metadata for the Multilingual Web - Usage Scenarios and Implementations </ref></title>. W3C Working Draft 7 March 2013. Available at <ref target="http://www.w3.org/TR/2013/WD-mlw-metadata-us-impl-20130307/">http://www.w3.org/TR/2013/WD-mlw-metadata-us-impl-20130307/</ref>. The latest version of <ref target="http://www.w3.org/TR/mlw-metadata-us-impl/">MLW Metadata US IMPL</ref> is available at http://www.w3.org/TR/mlw-metadata-us-impl/ .</bibl>
- <bibl xml:id="nerd" n="NERD">Named Entity Recognition and Disambiguation ontology (NERD)
+ <bibl xml:id="mqm" n="Multidimensional Quality Metrics">Lommel, Arle. <title>Useful Quality Metrics (for Humans, Not Researchers)</title>. Presentation at the Workshop on UserCentric Machine Translation & Evaluation, <ref target="http://www.mtsummit2013.info/workshops.asp">MT Summit 2013</ref>.</bibl>
+ <bibl xml:id="nerd" n="NERD"><title>Named Entity Recognition and Disambiguation ontology (NERD)</title>.
available at: <ref target="http://nerd.eurecom.fr/ontology"
>http://nerd.eurecom.fr/ontology</ref></bibl>
- <bibl xml:id="nif-reference" n="NIF">Hellmann, S. et al. (ed.). <ref target="http://persistence.uni-leipzig.org/nlp2rdf/ontologies/nif-core#">NIF 2.0 Core Ontology</ref>, as of August 2013. Available at <ref target="http://persistence.uni-leipzig.org/nlp2rdf/ontologies/nif-core#">http://persistence.uni-leipzig.org/nlp2rdf/ontologies/nif-core#</ref> under CC-BY 3.0 license maintained by the <ref target="http://nlp2rdf.org">NLP2RDF project</ref>.</bibl>
+ <bibl xml:id="nif-reference" n="NIF">Hellmann, S. et al. (ed.). <title><ref target="http://persistence.uni-leipzig.org/nlp2rdf/ontologies/nif-core#">NIF 2.0 Core Ontology</ref></title>, as of August 2013. Available at <ref target="http://persistence.uni-leipzig.org/nlp2rdf/ontologies/nif-core#">http://persistence.uni-leipzig.org/nlp2rdf/ontologies/nif-core#</ref> under CC-BY 3.0 license maintained by the <ref target="http://nlp2rdf.org">NLP2RDF project</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 Standardization (ISO) ISO/IEC
@@ -5461,8 +5463,8 @@
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="prov-dm" n="PROV-DM">Moreau, Luc and Paolo Missier (eds.). <ref
- target="http://www.w3.org/TR/2013/REC-prov-dm-20130430/">Provenance data model</ref>.
+ <bibl xml:id="prov-dm" n="PROV-DM">Moreau, Luc and Paolo Missier (eds.). <title><ref
+ target="http://www.w3.org/TR/2013/REC-prov-dm-20130430/">Provenance data model</ref></title>.
W3C Recommendation 30 April 2013. Available at <ref target="http://www.w3.org/TR/2013/REC-prov-dm-20130430/">http://www.w3.org/TR/2013/REC-prov-dm-20130430/</ref>.
The latest version of <ref target="http://www.w3.org/TR/prov-dm/">The PROV Data Model</ref>
is available at http://www.w3.org/TR/prov-dm/.
@@ -5484,8 +5486,8 @@
development version (P5)</ref>
</title>. TEI Consortium, Charlottesville, Virginia, USA, Text Encoding
Initiative.</bibl>
- <bibl xml:id="wordnet" n="WordNet">Princeton University "About WordNet." WordNet.
- Princeton University. 2010, available at: <ref target="http://wordnet.princeton.edu"
+ <bibl xml:id="wordnet" n="WordNet"><title>WordNet</title>.
+ Princeton University, 2010. Available at: <ref target="http://wordnet.princeton.edu"
>http://wordnet.princeton.edu</ref>.</bibl>
<bibl xml:id="xhtml10" n="XHTML 1.0">Steven Pemberton et al. <title>
<ref target="http://www.w3.org/TR/2002/REC-xhtml1-20020801/">XHTML™ 1.0 The Extensible
@@ -5785,7 +5787,7 @@
<item><emph>Specifications</emph>. Specifications (sometimes called a translation brief) are a description of the various expectations and requirements for a translation task. These may include statements about the type of translation expected, guidance on terminology to be used, information about audience, and so forth. Translation specifications are described in detail in ISO/TS-11669.</item>
<item><emph>Tool</emph>. As used here, a tool is software that generates localization quality markup. Tools may be fully automatic (e.g., a tool that identifies potential issues with terminology and grammar and marks them without human intervention) or may required human input (e.g., a system that allows users to highlight spans of text and mark them with appropriate issues).</item></list>
<p>For more information on setting translation project specifications and determining quality expectations, implementers are encouraged to consult the ISO standard definition of translation project specifications included in <ptr target="#isots11669" type="bibref"/>. Details about translation specifications are available at <ptr target="#structuredspecs" type="bibref"/>. While these documents do not directly address the definition of quality metrics, they provide useful guidance for implementers interested in determining which localization quality issue values should be used for specific scenarios.</p>
- <p>The issue types defined in Localization Quality Issue were derived from the QTLaunchPad project’s Multidimensional Quality Metrics (MQM) framework. Additional guidance on this project may be found at [Multidimensional Quality Metrics].</p>
+ <p>The issue types defined in Localization Quality Issue were derived from the QTLaunchPad project’s Multidimensional Quality Metrics (MQM) framework. Additional guidance on this project may be found at <ptr target="#mqm" type="bibref"/>.</p>
<p>The topic of localization quality is rapidly evolving and ITS 2.0 represents the first step in standardizing this area and will serve for basic interoperability needs. For situations requiring additional expressive capability or categories, further custom markup may be required.</p>
</div>
<div xml:id="list-of-elements-and-attributes" type="inform">
Received on Monday, 21 October 2013 20:10:37 UTC