W3C home > Mailing lists > Public > public-multilingualweb-lt-commits@w3.org > March 2013

CVS WWW/International/multilingualweb/lt/drafts/its20

From: CVS User alommel <cvsmail@w3.org>
Date: Thu, 28 Mar 2013 10:27:02 +0000
Message-Id: <E1ULA2w-000829-Ae@gil.w3.org>
To: public-multilingualweb-lt-commits@w3.org
Update of /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20
In directory gil:/tmp/cvs-serv30875

Modified Files:
	its20.odd 
Log Message:
reformat only

--- /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/its20.odd	2013/03/28 10:26:24	1.352
+++ /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/its20.odd	2013/03/28 10:27:02	1.353
@@ -19,7 +19,8 @@
     <altlocs>
       <loc href="its20.odd">ODD/XML document</loc>
       <loc href="itstagset20.zip">self-contained zipped archive</loc>
-      <loc href="diffs/diff-wd20121206-wd20121023.html">XHTML Diff markup to previous publication 2012-10-23</loc>
+      <loc href="diffs/diff-wd20121206-wd20121023.html">XHTML Diff markup to previous publication
+        2012-10-23</loc>
     </altlocs>
     <prevlocs>
       <loc href="http://www.w3.org/TR/2012/WD-its20-20121023/">
@@ -58,20 +59,14 @@
 	  <translationloc role="spec-conditional" href="http://www.w3.org/2003/03/Translations/byTechnology?technology=its"/>
 	   -->
     <abstract>
-		<p>
-			The technology described in this document - the
-			<emph>Internationalization Tag Set (ITS) 2.0</emph>
-			- enhances the foundation to integrate automated processing of human
-			language into core Web technologies. ITS 2.0 bears many commonalities
-			with is predecessor,
-			<loc href="http://www.w3.org/TR/2007/REC-its-20070403/">ITS 1.0</loc>
-			but provides additional concepts that are designed to foster the
-			automated creation and processing of multilingual Web content. ITS
-			2.0 focuses on HTML, XML-based formats in general, and can leverage
-			processing based on the XML Localization Interchange File Format
-			(XLIFF), as well as the Natural Language Processing Interchange
-			Format (NIF).
-		</p>
+      <p> The technology described in this document - the <emph>Internationalization Tag Set (ITS)
+          2.0</emph> - enhances the foundation to integrate automated processing of human language
+        into core Web technologies. ITS 2.0 bears many commonalities with is predecessor, <loc
+          href="http://www.w3.org/TR/2007/REC-its-20070403/">ITS 1.0</loc> but provides additional
+        concepts that are designed to foster the automated creation and processing of multilingual
+        Web content. ITS 2.0 focuses on HTML, XML-based formats in general, and can leverage
+        processing based on the XML Localization Interchange File Format (XLIFF), as well as the
+        Natural Language Processing Interchange Format (NIF). </p>
     </abstract>
     <status>
       <p>
@@ -148,9 +143,10 @@
           localization, and defines implementations of these concepts (termed “ITS data categories”)
           as a set of elements and attributes called the <emph>Internationalization Tag Set
             (ITS)</emph>. The document provides implementations for HTML, serializations in <ref
-            target="http://nlp2rdf.org/nif-1-0">NIF (NLP Interchange Format)</ref>, and provides definitions of
-          ITS elements and attributes in the form of XML Schema <ptr target="#xmlschema1"
-            type="bibref"/> and RELAX NG <ptr target="#relaxng" type="bibref"/>.</p>
+            target="http://nlp2rdf.org/nif-1-0">NIF (NLP Interchange Format)</ref>, and provides
+          definitions of ITS elements and attributes in the form of XML Schema <ptr
+            target="#xmlschema1" type="bibref"/> and RELAX NG <ptr target="#relaxng" type="bibref"
+          />.</p>
 
         <p>This document aims to realize many of the ideas formulated in the <ref
             target="http://www.w3.org/TR/2012/WD-its2req-20120524/">ITS 2.0 Requirements
@@ -194,10 +190,10 @@
                 format mapping in order to support a claim of ITS 2.0 conformance.</item>
               <item>ITS 2.0 provides algorithms to generate NIF out of HTML or XML with ITS 2.0
                 metadata.</item>
-              <item>A global implementation of ITS 2.0 requires at least the <ref target="#xpath">XPath version 1.0</ref>.
-                Other versions of XPath or other query languages (e.g., CSS Selectors) can be
-                expressed via a dedicated <ref target="#queryLanguage">queryLanguage</ref>
-                attribute.</item>
+              <item>A global implementation of ITS 2.0 requires at least the <ref target="#xpath"
+                  >XPath version 1.0</ref>. Other versions of XPath or other query languages (e.g.,
+                CSS Selectors) can be expressed via a dedicated <ref target="#queryLanguage"
+                  >queryLanguage</ref> attribute.</item>
             </list>
             <p xml:id="its20-new-data-categories">The new data categories included in ITS 2.0
               are:</p>
@@ -237,8 +233,11 @@
             “internationalization”, see <ptr target="#geo-i18n-l10n" type="bibref"/>.</p>
           <note type="ed">Note: This should refer to the best practice document as well, when
             ready.</note>
-          <p>The increasing usage of XML as a medium for documentation-related content (e.g. <ref target="https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=docbook#technical">DocBook</ref>>
-            and <ref target="https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=dita#technical">DITA</ref> as formats for writing structured documentation, well suited to computer
+          <p>The increasing usage of XML as a medium for documentation-related content (e.g. <ref
+              target="https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=docbook#technical"
+              >DocBook</ref>> and <ref
+              target="https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=dita#technical"
+              >DITA</ref> as formats for writing structured documentation, well suited to computer
             hardware and software manuals) and software-related content (e.g. the eXtensible User
             Interface Language <ptr target="#xul" type="bibref"/>) creates challenges and
             opportunities in the domain of XML internationalization and localization.</p>
@@ -374,12 +373,12 @@
             </div>
             <div xml:id="users_localization_workflow_managers">
               <head>Localization Workflow Managers</head>
-              <p>These types of users are concerned with localization workflows in which content goes
-                through certain steps: preparation for localization, start of the localization
-                process by e.g. a conversion into a bitext (aligned parallel text) format like <ptr target="#xliff"
-                  type="bibref"/>, the actual localization by human translators or machine
-                translation and other adaptations of content, and finally the integration of the
-                localized content into the original format. That format is often based on XML or
+              <p>These types of users are concerned with localization workflows in which content
+                goes through certain steps: preparation for localization, start of the localization
+                process by e.g. a conversion into a bitext (aligned parallel text) format like <ptr
+                  target="#xliff" type="bibref"/>, the actual localization by human translators or
+                machine translation and other adaptations of content, and finally the integration of
+                the localized content into the original format. That format is often based on XML or
                 HTML; (Web) content management systems are widely used for content creation, and
                 their integration with localization workflows is an important task for the workflow
                 manager. For the integration of content creation and localization, metadata plays a
@@ -600,15 +599,16 @@
 
           <p>Information (e.g. "translate this") captured by ITS markup (e.g.
               <code>its:translate='yes'</code>) always pertains to one or more XML or HTML nodes,
-            primarily element and attribute nodes, as defined in <ref target="xpath">XPath</ref>.
-            In a sense, ITS markup “selects” the relevant node(s). Selection may be explicit or implicit.
-            ITS distinguishes two approaches to selection: (1) local, and (2) using global rules.</p>
+            primarily element and attribute nodes, as defined in <ref target="xpath">XPath</ref>. In
+            a sense, ITS markup “selects” the relevant node(s). Selection may be explicit or
+            implicit. ITS distinguishes two approaches to selection: (1) local, and (2) using global
+            rules.</p>
           <p>The mechanisms defined for ITS selection resemble those defined in <ptr
               target="#css2-1" type="bibref"/>. The local approach can be compared to the
               <code>style</code> attribute in HTML/XHTML, and the approach with global rules is
             similar to the <code>style</code> element in HTML/XHTML. ITS usually uses XPath for
-            identifying nodes although CSS Selectors and other query languages can be used if supported by
-            the application. Thus,</p>
+            identifying nodes although CSS Selectors and other query languages can be used if
+            supported by the application. Thus,</p>
           <list>
             <item>the local approach puts ITS markup in the relevant element of the host vocabulary
               (e.g. the <code>author</code> element in DocBook)</item>
@@ -782,8 +782,9 @@
             data category can add information to selected nodes (using a <gi>locNote</gi> element),
             or point to existing information elsewhere in the document (using a
               <att>locNotePointer</att> attribute).</p>
-          <p>The <ref target="#datacategories-overview">data category overview table</ref>, in <ptr target="#datacategories-defaults-etc" type="specref"/>,
-            provides an overview of what data categories allow to point to existing information or to add information.</p>
+          <p>The <ref target="#datacategories-overview">data category overview table</ref>, in <ptr
+              target="#datacategories-defaults-etc" type="specref"/>, provides an overview of what
+            data categories allow to point to existing information or to add information.</p>
           <p>The functionalities of adding information and pointing to existing information are
               <emph>mutually exclusive</emph>. That is to say, attributes for pointing and adding
             the same information must not appear at the same rule element.</p>
@@ -803,8 +804,12 @@
           <p>The namespace URI that <ref target="#rfc-keywords">MUST</ref> be used by
             implementations of this specification is:</p>
           <eg>http://www.w3.org/2005/11/its</eg>
-          <p xml:id="its-namespace-prefix">The namespace prefix used in this specification for XML implementations
-            of ITS for the above URI is <val>its</val>. It is recommended that XML implementations of this specification use this prefix, unless there is existing dedicated markup in use for a given data category. In HTML there is no namespace prefix: <val>its-</val> is used to indicate ITS 2.0 attributes in HTML documents. See <ptr target="#html5-local-attributes" type="specref"/> for details.</p>
+          <p xml:id="its-namespace-prefix">The namespace prefix used in this specification for XML
+            implementations of ITS for the above URI is <val>its</val>. It is recommended that XML
+            implementations of this specification use this prefix, unless there is existing
+            dedicated markup in use for a given data category. In HTML there is no namespace prefix:
+              <val>its-</val> is used to indicate ITS 2.0 attributes in HTML documents. See <ptr
+              target="#html5-local-attributes" type="specref"/> for details.</p>
           <p>In addition, the following namespaces are used in this document:</p>
           <list type="unordered">
             <item><code>http://www.w3.org/2001/XMLSchema</code> for the XML Schema namespace, here
@@ -901,15 +906,15 @@
         </div>
         <div xml:id="def-html">
           <head>The Term HTML</head>
-          <p>This specification uses the term <code>HTML</code> to refer to HTML5 or its successor in HTML syntax
-              <ptr target="#html5" type="bibref"/>.</p>
+          <p>This specification uses the term <code>HTML</code> to refer to HTML5 or its successor
+            in HTML syntax <ptr target="#html5" type="bibref"/>.</p>
         </div>
         <div xml:id="def-css-selector">
           <head>The Term CSS Selectors</head>
-          <p>This specification uses the term <code>CSS Selectors</code> in the 
-            sense of <code>Selectors</code> as specifies in <ptr target="#css3-selectors" type="bibref"/> 
-            to prevent confusion with the generic use of the word "selector".
-            <ptr target="#css3-selectors" type="bibref"/>.</p>
+          <p>This specification uses the term <code>CSS Selectors</code> in the sense of
+              <code>Selectors</code> as specifies in <ptr target="#css3-selectors" type="bibref"/>
+            to prevent confusion with the generic use of the word "selector". <ptr
+              target="#css3-selectors" type="bibref"/>.</p>
         </div>
       </div>
       <div xml:id="conformance">
@@ -926,12 +931,12 @@
             for ITS Markup</ref> and conformance of <ref
             target="#conformance-product-html-processing-expectations">3) processing expectations
             for ITS Markup in HTML</ref>. Also special <ref target="#conformance-class-html5-its"
-            >conformance class</ref> is defined for using ITS markup in HTML5 documents, HTML5+ITS, which serves
-          as an <emph>applicable specification</emph> in the sense specified in the
-          <ref target="http://www.w3.org/TR/html5/infrastructure.html#extensibility">Extensibility section</ref> of
-          <ptr target="#html5" type="bibref"/>. These conformance types and classes
-          complement each other. An implementation of this specification <ref target="#rfc2119"
-            >MAY</ref> use them separately or together.</p>
+            >conformance class</ref> is defined for using ITS markup in HTML5 documents, HTML5+ITS,
+          which serves as an <emph>applicable specification</emph> in the sense specified in the
+            <ref target="http://www.w3.org/TR/html5/infrastructure.html#extensibility">Extensibility
+            section</ref> of <ptr target="#html5" type="bibref"/>. These conformance types and
+          classes complement each other. An implementation of this specification <ref
+            target="#rfc2119">MAY</ref> use them separately or together.</p>
         <div xml:id="conformance-product-schema">
           <head>Conformance Type 1: ITS Markup Declarations</head>
           <p><emph>Description:</emph> ITS markup declarations encompass all declarations that are
@@ -1178,9 +1183,11 @@
             version is indicated by the ITS <att>version</att> attribute. This attribute is
             mandatory for the <gi>rules</gi> element, where it <ref target="#rfc-keywords"
               >MUST</ref> be in no namespace.</p>
-          <p>If there is no <gi>rules</gi> element in an XML document, a prefixed ITS <att>version</att> attribute (e.g. <code>its:version</code>)
-              <ref target="#rfc-keywords">MUST</ref> be provided on the element where the ITS markup is used, or on one of its ancestors.
-            There <ref target="#rfc-keywords">MUST NOT</ref> be two different versions of ITS in the same document.</p>
+          <p>If there is no <gi>rules</gi> element in an XML document, a prefixed ITS
+              <att>version</att> attribute (e.g. <code>its:version</code>) <ref
+              target="#rfc-keywords">MUST</ref> be provided on the element where the ITS markup is
+            used, or on one of its ancestors. There <ref target="#rfc-keywords">MUST NOT</ref> be
+            two different versions of ITS in the same document.</p>
           <p>External, linked rules can have different versions than internal rules.</p>
         </div>
         <div xml:id="datacategory-locations">
@@ -1222,11 +1229,13 @@
               nodes, or for pointing to existing notes in the document. For the former purpose, a
                 <gi>locNote</gi> element can be used. For the latter purpose, a
                 <att>locNotePointer</att> attribute can be used.</p>
-            <p>The <ref target="#datacategories-overview">data category overview table</ref>, in <ptr target="#datacategories-defaults-etc" type="specref"/>,
-              provides an overview of what data categories allow to point to existing information or to add information.</p>
+            <p>The <ref target="#datacategories-overview">data category overview table</ref>, in
+                <ptr target="#datacategories-defaults-etc" type="specref"/>, provides an overview of
+              what data categories allow to point to existing information or to add information.</p>
             <p>The functionalities of adding information and pointing to existing information are
-                <emph>mutually exclusive</emph>. That is: markup for pointing and adding the same information <ref
-                target="#rfc-keywords">MUST NOT</ref> appear in the same rule element.</p>
+                <emph>mutually exclusive</emph>. That is: markup for pointing and adding the same
+              information <ref target="#rfc-keywords">MUST NOT</ref> appear in the same rule
+              element.</p>
 
             <p>Global rules can appear in the XML document they will be applied to, or in a separate
               XML document. The precedence of their processing depends on these variations. See also
@@ -1346,11 +1355,11 @@
                 The XPath expression is evaluated relative to the nodes selected by the selector
                 attribute.</p>
               <p xml:id="pointer-attributes-list">The following attributes point to existing
-                information: <att>allowedCharactersPointer</att>, 
-                  <att>disambigClassRefPointer</att>, <att>disambigIdentPointer</att>,
-                <att>disambigIdentRefPointer</att>, <att>disambigSourcePointer</att>, <att>domainPointer</att>,
-                  <att>externalResourceRefPointer</att>, <att>langPointer</att>,
-                  <att>locNotePointer</att>, <att>locNoteRefPointer</att>,
+                information: <att>allowedCharactersPointer</att>,
+                <att>disambigClassRefPointer</att>, <att>disambigIdentPointer</att>,
+                  <att>disambigIdentRefPointer</att>, <att>disambigSourcePointer</att>,
+                  <att>domainPointer</att>, <att>externalResourceRefPointer</att>,
+                  <att>langPointer</att>, <att>locNotePointer</att>, <att>locNoteRefPointer</att>,
                   <att>locQualityIssuesRefPointer</att>, <att>provenanceRecordsRefPointer</att>,
                   <att>storageEncodingPointer</att>, <att>storageSizePointer</att>,
                   <att>targetPointer</att>, <att>termInfoPointer</att>,
@@ -1377,22 +1386,23 @@
           </div>
           <div xml:id="css-selectors">
             <head>CSS Selectors</head>
-            <note><p>The term <code>CSS Selectors</code> is used throughout the specification in the 
-              sense of <code>Selectors</code> as specified in <ptr target="#css3-selectors" type="bibref"/> 
-              to prevent confusion with the generic use of the word "selector". 
-              See <ref target="#css-selectors">The term CSS Selector</ref>.</p></note>
-            <note><p xml:id="css-selectors-implementations">The working group will not provide a
-              CSS Selectors based implementation; nevertheless there are several existing libraries,
-              which can translate CSS Selectors to XPath, so that XPath selectors based implementations
-              can be used.</p></note>
-            <note><p xml:id="css-selectors-and-attributes">CSS selectors have no ability to point to attributes.</p></note>
-            <p>CSS Selectors  are identified by <code>css</code> value in <att>queryLanguage</att>
+            <note><p>The term <code>CSS Selectors</code> is used throughout the specification in the
+                sense of <code>Selectors</code> as specified in <ptr target="#css3-selectors"
+                  type="bibref"/> to prevent confusion with the generic use of the word "selector".
+                See <ref target="#css-selectors">The term CSS Selector</ref>.</p></note>
+            <note><p xml:id="css-selectors-implementations">The working group will not provide a CSS
+                Selectors based implementation; nevertheless there are several existing libraries,
+                which can translate CSS Selectors to XPath, so that XPath selectors based
+                implementations can be used.</p></note>
+            <note><p xml:id="css-selectors-and-attributes">CSS selectors have no ability to point to
+                attributes.</p></note>
+            <p>CSS Selectors are identified by <code>css</code> value in <att>queryLanguage</att>
               attribute.</p>
             <div>
               <head>Absolute selector</head>
               <p>Absolute selector <ref target="#rfc-keywords">MUST</ref> be interpreted as selector
-                as defined in <ptr target="#css3-selectors" type="bibref"/>. Both simple
-                selectors and groups of selectors can be used.</p>
+                as defined in <ptr target="#css3-selectors" type="bibref"/>. Both simple selectors
+                and groups of selectors can be used.</p>
             </div>
             <div>
               <head>Relative selector</head>
@@ -1405,18 +1415,17 @@
           <div>
             <head>Additional query languages</head>
             <p>ITS processors <ref target="#rfc-keywords">MAY</ref> support additional query
-              languages. For each additional query language the processor <ref target="#rfc-keywords"
-                >MUST</ref> define:</p>
+              languages. For each additional query language the processor <ref
+                target="#rfc-keywords">MUST</ref> define:</p>
             <list type="bulleted">
               <item>identifier of query language used in <att>queryLanguage</att>;</item>
               <item>rules for evaluating absolute selector to collection of nodes;</item>
               <item>rules for evaluating relative selector to collection of nodes.</item>
             </list>
-            <p>Because future versions of this specification are likely to define
-              additional query languages, the following query language identifiers are reserved:
-                <code>xpath</code>, <code>css</code>, <code>xpath2</code>, <code>xpath3</code>,
-                <code>xquery</code>, <code>xquery3</code>, <code>xslt2</code>,
-              <code>xslt3</code>.</p>
+            <p>Because future versions of this specification are likely to define additional query
+              languages, the following query language identifiers are reserved: <code>xpath</code>,
+                <code>css</code>, <code>xpath2</code>, <code>xpath3</code>, <code>xquery</code>,
+                <code>xquery3</code>, <code>xslt2</code>, <code>xslt3</code>.</p>
           </div>
           <div xml:id="its-param">
             <head>Variables in selectors</head>
@@ -1498,7 +1507,10 @@
             process its rules element before processing the content of the <gi>rules</gi> element
             where the original XLink <att>href</att> attribute is.</p>
 
-          <p>External rules may also have links to other external rules (see <ptr target="#EX-link-external-rules-2" type="exref"/>). The linking mechanism is recursive in a depth-first approach, and subsequently after the processing the rules MUST be read top-down (see <ptr target="#EX-link-external-rules-3" type="exref"/>).</p>
+          <p>External rules may also have links to other external rules (see <ptr
+              target="#EX-link-external-rules-2" type="exref"/>). The linking mechanism is recursive
+            in a depth-first approach, and subsequently after the processing the rules MUST be read
+            top-down (see <ptr target="#EX-link-external-rules-3" type="exref"/>).</p>
         </div>
         <div xml:id="selection-precedence">
           <head>Precedence between Selections</head>
@@ -1518,7 +1530,11 @@
               <note><p>ITS does not define precedence related to rules defined or linked based on
                   non-ITS mechanisms (such as processing instructions for linking rules).</p></note>
             </item>
-            <item xml:id="precedence-inheritance">Selection via inherited values. This applies only to element nodes. The inheritance rules are laid out in a dedicated <ref target="#datacategories-overview">datacategory overview table</ref>, see column <quote>Inheritance for element nodes</quote>. Selection via inheritance takes precedence over default values, see below item.</item>
+            <item xml:id="precedence-inheritance">Selection via inherited values. This applies only
+              to element nodes. The inheritance rules are laid out in a dedicated <ref
+                target="#datacategories-overview">datacategory overview table</ref>, see column
+                <quote>Inheritance for element nodes</quote>. Selection via inheritance takes
+              precedence over default values, see below item.</item>
             <item xml:id="precedence-defaults">Selections via defaults for data categories, see <ptr
                 target="#datacategories-defaults-etc" type="specref"/></item>
           </list>
@@ -1603,8 +1619,8 @@
         <div xml:id="conversion-to-nif">
           <head>Conversion to NIF</head>
           <p>This section defines an algorithm to convert XML or HTML documents (or their DOM
-            representations) that contain ITS metadata to the RDF-based format based on <ptr target="#NIF" type="bibref"/>.
-            The conversion results in RDF triples.</p>
+            representations) that contain ITS metadata to the RDF-based format based on <ptr
+              target="#NIF" type="bibref"/>. The conversion results in RDF triples.</p>
           <note><p>The algorithm is intended to extract the text from the XML/HTML/DOM for an NLP
               tool and can produce a lot of <quote>phantom</quote> predicates from excessive
               whitespace, which 1) increases the size of the intermediate mapping and 2) extracts
@@ -1742,23 +1758,38 @@
             individual data categories in a document, independently from data category annotations
             themselves.</p>
 
-          <p>The attribute <att>annotatorsRef</att> provides a way to associate all the annotations of a
-            given data category within the element with information about the processor that
+          <p>The attribute <att>annotatorsRef</att> provides a way to associate all the annotations
+            of a given data category within the element with information about the processor that
             generated those data category annotations.</p>
-          
+
           <note><list>
-            <item><p xml:id="annotators-ref-usage-scenarios">Three cases of providing tool information can be expected:</p>
-              <list type="ordered">
-                <item><p>information about tools used for creating or modifying the textual content;</p></item>
-                <item><p>information about tools that do 1), but also create ITS annotations, see <ptr target="#list-of-elements-and-attributes" type="specref"/>; </p></item>
-                <item><p>information about tools that don’t modify or create content, but just create ITS annotations.</p></item> </list><p><att>annotatorsRef</att> is only meant to be used when actual ITS annotation is involved, that is for 2) and 3). To express tool information related only to the creation or modification of textual content and independent of ITS data categories, that is case 1), one should use the tool or <att>toolRef</att> attribute provided by the <ref target="#provenance">Provenance</ref> data category.</p></item>
-            <item><p>An example of case 2) is an MT engine that modifies content and creates ITS <ref target="#mtconfidence">MT Confidence</ref> annotations. Here the situation may occur that several tools are involved in creating MT Confidence annotations: the MT engine and the tool inserting the markup. The annotatorsRef attribute should identify the tool most useful in further processes, in this case the MT engine.</p></item>
-            
-          </list></note>
-
-          <p>The value of <att>annotatorsRef</att> is a space-separated list of references where each
-            reference is composed of two parts: a data category identifier and an IRI. These two
-            parts are separated by a character <code>|</code> VERTICAL LINE (U+007C).</p>
+              <item><p xml:id="annotators-ref-usage-scenarios">Three cases of providing tool
+                  information can be expected:</p>
+                <list type="ordered">
+                  <item><p>information about tools used for creating or modifying the textual
+                      content;</p></item>
+                  <item><p>information about tools that do 1), but also create ITS annotations, see
+                        <ptr target="#list-of-elements-and-attributes" type="specref"/>; </p></item>
+                  <item><p>information about tools that don’t modify or create content, but just
+                      create ITS annotations.</p></item>
+                </list><p><att>annotatorsRef</att> is only meant to be used when actual ITS
+                  annotation is involved, that is for 2) and 3). To express tool information related
+                  only to the creation or modification of textual content and independent of ITS
+                  data categories, that is case 1), one should use the tool or <att>toolRef</att>
+                  attribute provided by the <ref target="#provenance">Provenance</ref> data
+                  category.</p></item>
+              <item><p>An example of case 2) is an MT engine that modifies content and creates ITS
+                    <ref target="#mtconfidence">MT Confidence</ref> annotations. Here the situation
+                  may occur that several tools are involved in creating MT Confidence annotations:
+                  the MT engine and the tool inserting the markup. The annotatorsRef attribute
+                  should identify the tool most useful in further processes, in this case the MT
+                  engine.</p></item>
+
+            </list></note>
+
+          <p>The value of <att>annotatorsRef</att> is a space-separated list of references where
+            each reference is composed of two parts: a data category identifier and an IRI. These
+            two parts are separated by a character <code>|</code> VERTICAL LINE (U+007C).</p>
 
           <list>
             <item><p>The data category identifier <ref target="#rfc2119">MUST</ref> be one of the
@@ -1779,9 +1810,9 @@
             children elements) and to the attributes of that element.</p>
 
           <p>On any given node, the information provided by this mechanism is a space-separated list
-            of the accumulated references found in the <att>annotatorsRef</att> attributes declared in
-            the enclosing elements and sorted by data category identifiers. For each data category,

[967 lines skipped]
Received on Thursday, 28 March 2013 10:27:07 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:32:40 UTC