- From: Felix Sasaki via cvs-syncmail <cvsmail@w3.org>
- Date: Thu, 18 Oct 2012 07:49:18 +0000
- To: public-multilingualweb-lt-commits@w3.org
Update of /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20
In directory hutz:/tmp/cvs-serv29883
Modified Files:
its20.odd its20.html
Log Message:
translation provenance re-write and some other smaller fixes and comments
Index: its20.odd
===================================================================
RCS file: /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/its20.odd,v
retrieving revision 1.193
retrieving revision 1.194
diff -u -d -r1.193 -r1.194
--- its20.odd 17 Oct 2012 16:54:29 -0000 1.193
+++ its20.odd 18 Oct 2012 07:49:15 -0000 1.194
@@ -8,13 +8,13 @@
<w3c-designation>ITS20</w3c-designation>
<w3c-doctype>W3C Working Draft</w3c-doctype>
<pubdate>
- <day>29</day>
- <month>August</month>
+ <day>25</day>
+ <month>October</month>
<year>2012</year>
</pubdate>
<publoc>
- <loc href="http://www.w3.org/TR/2012/WD-its20-20120829/">
- http://www.w3.org/TR/2012/WD-its20-20120829/</loc>
+ <loc href="http://www.w3.org/TR/2012/WD-its20-20121025/">
+ http://www.w3.org/TR/2012/WD-its20-20121025/</loc>
</publoc>
<altlocs>
<loc href="its20.odd">ODD/XML document</loc>
@@ -25,10 +25,12 @@
26 June 2012</loc>
<loc href="diffs/diff-wd20120829-wd20120731.html">XHTML Diff markup to publication from
31 July 2012</loc>
+ <loc href="diffs/diff-wd20121025-wd20120829.html">XHTML Diff markup to publication from
+ 29 August July 2012</loc>
</altlocs>
<prevlocs>
- <loc href="http://www.w3.org/TR/2012/WD-its20-20120731/">
- http://www.w3.org/TR/2012/WD-its20-20120731/</loc>
+ <loc href="http://www.w3.org/TR/2012/WD-its20-20120829/">
+ http://www.w3.org/TR/2012/WD-its20-20120829/</loc>
</prevlocs>
<latestloc>
@@ -70,7 +72,7 @@
1.0</loc>; it is designed to foster the creation of multilingual Web content,
focusing on HTML5, XML based formats in general, and to leverage localization
workflows based on the XML Localization Interchange File Format (XLIFF). In addition
- to HTML5 and XML, algorithms to convert ITS attributes to NIF are
+ to using ITS 2.0 for HTML5 and XML content, an algorithm to convert that content NIF are
provided.</p>
</abstract>
<status>
@@ -87,7 +89,7 @@
1.0</loc>; it is designed to foster the creation of multilingual Web content,
focusing on HTML5, XML based formats in general, and to leverage localization
workflows based on the XML Localization Interchange File Format (XLIFF). In addition
- to HTML5 and XML, algorithms to convert ITS attributes to NIF are
+ to using ITS 2.0 for HTML5 and XML content, an algorithm to convert that content NIF are
provided.</p>
<p>This document is an updated Public Working Draft published by the <loc
@@ -98,16 +100,7 @@
href="http://www.w3.org/2004/02/Process-20040205/tr.html#maturity-levels">W3C
document maturity levels</loc>).</p>
- <p xml:id="major-changes">Major changes in this version of the document include the
- addition of several data categories (<loc href="#Disambiguation"
- >Disambiguation</loc><loc href="#target-pointer">Target Pointer</loc>, <loc
- href="#idvalue">Id Value</loc>, <loc href="#preservespace">Preserve Space</loc>,
- <loc href="#lqissue">Localization Quality Issue</loc>
- <loc href="#lqprecis">Localization Quality Précis</loc>), the definition of a <loc
- href="#selectors">query language attribute</loc>, and the creation of an initial
- <loc href="http://phaedrus.scss.tcd.ie/its2.0/its-testsuite.html">test
- suite</loc>. See the <loc href="#changelog-since-20120731">changelog</loc> for
- details.</p>
+ <p xml:id="major-changes">A list of <loc href="#changelog-since-20120829">major changes since the previous publication</loc> is available. This working draft is planned to be the last ordinary working draft before moving to last call. Hence the working draft encourages wide feedback from outside the working group.</p>
<p>Feedback about the content of this document is encouraged. See also <loc
href="https://www.w3.org/International/multilingualweb/lt/track/issues/">issues
@@ -1903,7 +1896,7 @@
<code>span</code>, and e.g. present it to a translator.</item>
</list>
</note>
- <note type="ed">The links to examples (last column) are currently pointing to the old location of the test suite; these need to be updated to the github location.</note>
+ <note type="ed">The links to examples (last column) are currently pointing to the old location of the test suite; these need to be updated to the github location. Also, the table needs to be completed and checked against the data category specific sections.</note>
<table border="1" width="100%" xml:id="datacategories-overview">
<row role="head">
@@ -2130,6 +2123,21 @@
</row>
<row>
<cell>
+ <ref target="#translation-agent-provenance">Translation Agent Provenance</ref>
+ </cell>
+
+ <cell>Yes</cell>
+ <cell>Yes</cell>
+ <cell>Yes</cell>
+ <cell>Yes</cell>
+ <cell>None</cell>
+ <cell>Textual content of element, <emph>including</emph> child elements,
+ but excluding attributes</cell>
+ <cell>tbd</cell>
+ <cell>tbd</cell>
+ </row>
+ <row>
+ <cell>
<ref target="#externalresource">External Resource</ref>
</cell>
@@ -2269,7 +2277,7 @@
<cell>Yes</cell>
<cell>Yes</cell>
<cell>Yes</cell>
- <cell><code>its:storageEncoding="UTF-8"</code></cell>
+ <cell><code>storageEncoding="UTF-8"</code></cell>
<cell>None</cell>
<cell>tbd</cell>
<cell>tbd</cell>
@@ -3354,65 +3362,236 @@
<div xml:id="translation-agent-provenance-definition">
<head>Definition</head>
<note type="ed">Early draft of this data category; additional data categories for provenance might be added, or below definition might be changed. The definition of this data category is not yet reflected in the data category overview table in <ptr type="specref" target="#datacategories-defaults-etc"/>.</note>
- <p>The <ref target="#translation-agent-provenance">Translation Provenance Agent</ref> data category is used to communicate the identity of agents that have been involved in the translation of the content.
- This allows translation consumers, such as post-editors or translation quality reviewers, to assess how the performance of these agents may impact the quality of the translation.
- Translation agents can be identified as a person, a piece of software or an organization that has been involved in providing a translation that resulted in the selected content. </p>
- <p>This data category only offers information on the identity of translation agents. If provenance information is needed that includes temporal information about processes or requires agents that support a wider range of activities, then the Standoff Provenance data category should be used.</p>
- <p>Translation tools, such as machine translation agents or CAT tools, may offer an easy way to create this information. Translation tools can then present this information to post-editors or translation process managers. Web applications may to present such information to consumers of translated documents.</p>
+ <p>The <ref target="#translation-agent-provenance">Translation Provenance Agent</ref> data category is used to communicate the identity of agents that have been involved in the translation of the content or the revision of the translated contend.
+ This allows translation and translation revision consumers, such as post-editors or translation quality reviewers, to assess how the performance of these agents may impact the quality of the translation.
+ Translation and translation revision agents can be identified as a person, a piece of software or an organization that has been involved in providing a translation that resulted in the selected content. </p>
+ <p>This data category offers three types of information. First, it allows to identity translation agents. Second, it allows to identify revision agents. Third, if provenance information is needed that includes temporal information about processes or requires agents that support a wider range of activities, the data category offers a mechanism to refer to external, RDF-based provenance descriptions based on the provenance data model <ptr target="#prov-dm" type="bibref"/>.</p>
+ <p>Translation or translation revision tools, such as machine translation agents or CAT tools, may offer an easy way to create this information. Translation tools can then present this information to post-editors or translation process managers. Web applications may to present such information to consumers of translated documents.</p>
</div>
<div xml:id="translation-agent-provenance-implementation">
<head>Implementation</head>
- <p>
- The Translation Agent Provenance data category can be expressed with global rules, or locally on an individual element. For elements, the data category information <ref target="#def-inheritance">inherits</ref> to the textual content of the element, including child elements and attributes.
- </p>
<note type="ed">No agreement yet on whether such usage of global rules, that is for identifiyng just one or a small set of elements, is something to recommend. See also <ref target="https://www.w3.org/International/multilingualweb/lt/track/issues/51">issue-51</ref>.</note>
- <p xml:id="translation-agent-provenance-global">GLOBAL : The <gi>transProvRule</gi> element contains the following:</p>
- <list type="unordered">
- <item><p>A required <att>selector</att> attribute. It contains an <ref
- target="#selectors">absolute selector</ref> which selects the
- nodes to which this rule applies.</p></item>
- <item><p>At least one of the following:</p>
+ <p>The <ref target="#translation-agent-provenance">Translation Agent Provenance</ref> data category
+ can be expressed with global rules, or locally on individual elements.
+ For elements, the data category information <ref
+ target="#def-inheritance">inherits</ref> to the textual content of
+ the element, <emph>including</emph> child elements, but excluding
+ attributes.</p>
+ <p xml:id="translation-agent-provenance-global">GLOBAL: The <gi>transProvRule</gi> element
+ contains the following:</p>
<list type="unordered">
- <item><p>Human translation provenance information specified by exactly one of the following:
- <list type="unordered">
- <item><p>A <att>transPerson</att> attribute that contains a string identifying a human translation agent.</p></item>
- <item><p>A <att>transPersonRef</att> attribute that contains an IRI referring to a resource that identifies a human translation agent.</p></item>
- <item><p>A <att>transPersonPointer</att> attribute that contains a relative selector pointing to a node with the exact same semantics as <att>transPerson</att>.</p></item>
- <item><p>A <att>transPersonRefPointer</att> attribute that contains a relative selector pointing to a node with the exact same semantics as <att>transPersonRef</att>.</p></item>
- </list></p></item>
- <item><p>Organizational translation provenance information specified by exactly of the following:
- <list type="unordered">
- <item><p>A <att>transOrg</att> attribute that contains a string identifying an organization acting as a translation agent.</p></item>
- <item><p>A <att>transOrgRef</att> attribute that contains an IRI referring to a resource that identifies an organization acting as a translation agent.</p></item>
- <item><p>A <att>transOrgPointer</att> attribute that contains a relative selector pointing to a node with the exact same semantics as transOrg.</p></item>
- <item><p>A <att>transOrgRefPointer</att> attribute that contains a relative selector pointing to a node with the exact same semantics as transOrgRef.</p></item>
-
- </list></p></item>
- <item><p>Translation tool provenance related information specified by exactly one of the following:</p>
- <list type="unordered">
- <item><p>A <att>transTool</att> attribute that contains a string identifying a software tool that was used in translating the selected content.</p></item>
- <item><p>A <att>transToolRef</att> attribute that contains an IRI referring to a resource that identifies a software tool that was used in the translation.</p></item>
- <item><p>A <att>transToolPointer</att> attribute that contains a relative selector pointing to a node with the exact same semantics as transTool.</p></item>
- <item><p>A <att>transToolRefPointer</att> attribute that contains a relative selector pointing to a node with the exact same semantics as transToolRef.</p></item>
- </list></item>
- </list></item>
- </list>
- <exemplum xml:id="EX-translation-agent-provenance-xml-global-1">
- <head>The <ref target="#translation-agent-provenance">Translation Agent Provenance</ref> data category used globally.</head>
- <p>In this example the provenance of the <code>par</code> (which is machine translated) and the <code>legalnotice</code> (which is human translated) elements are different. Hence the provenance information is recorded in different global translation provenance rules. </p>
- <egXML xmlns="http://www.tei-c.org/ns/Examples" target="examples/xml/EX-translation-agent-provenance-xml-global-1.xml"/>
+ <item><p>A required <att>selector</att> attribute. It contains an <ref
+ target="#selectors">absolute selector</ref> which selects
+ the nodes to which this rule applies.</p></item>
+ <item><p>At least one of the following:</p>
+ <list type="unordered">
+ <item><p>Exactly one of the following:</p>
+ <list type="unordered">
+ <item><p>A <att>translationProvenanceRecordsRef</att> attribute. Its
+ value is a URI pointing to the
+ <gi>translationProvenanceRecord</gi> element containing the
+ list of translation provenance records related to the content selected via the <att>selector</att> attribute.</p></item>
+ <item><p>A <att>translationProvenanceRecordsRefPointer</att>
+ attribute that contains a <ref target="#selectors"
+ >relative selector</ref> pointing to a node with
+ the exact same semantics as
+ <att>translationProvenanceRecordsRef</att>.</p></item>
+ </list>
+ </item>
+ <item><p>Human translation provenance information specified by exactly one of the following:
+ <list type="unordered">
+ <item><p>A <att>transPerson</att> attribute that contains a string identifying a human translation agent.</p></item>
+ <item><p>A <att>transPersonRef</att> attribute that contains an IRI referring to a resource that identifies a human translation agent.</p></item>
+ <item><p>A <att>transPersonPointer</att> attribute that contains a <ref target="#selectors">relative selector</ref> pointing to a node with the exact same semantics as <att>transPerson</att>.</p></item>
+ <item><p>A <att>transPersonRefPointer</att> attribute that contains a <ref target="#selectors">relative selector</ref> pointing to a node with the exact same semantics as <att>transPersonRef</att>.</p></item>
+ </list></p></item>
+ <item><p>Organizational translation provenance information specified by exactly of the following:
+ <list type="unordered">
+ <item><p>A <att>transOrg</att> attribute that contains a string identifying an organization acting as a translation agent.</p></item>
+ <item><p>A <att>transOrgRef</att> attribute that contains an IRI referring to a resource that identifies an organization acting as a translation agent.</p></item>
+ <item><p>A <att>transOrgPointer</att> attribute that contains a <ref target="#selectors">relative selector</ref> pointing to a node with the exact same semantics as transOrg.</p></item>
+ <item><p>A <att>transOrgRefPointer</att> attribute that contains a <ref target="#selectors">relative selector</ref> pointing to a node with the exact same semantics as transOrgRef.</p></item>
+
+ </list></p></item>
+ <item><p>Translation tool provenance related information specified by exactly one of the following:</p>
+ <list type="unordered">
+ <item><p>A <att>transTool</att> attribute that contains a string identifying a software tool that was used in translating the selected content.</p></item>
+ <item><p>A <att>transToolRef</att> attribute that contains an IRI referring to a resource that identifies a software tool that was used in the translation.</p></item>
+ <item><p>A <att>transToolPointer</att> attribute that contains a <ref target="#selectors">relative selector</ref> pointing to a node with the exact same semantics as transTool.</p></item>
+ <item><p>A <att>transToolRefPointer</att> attribute that contains a <ref target="#selectors">relative selector</ref> pointing to a node with the exact same semantics as transToolRef.</p></item>
+ </list></item>
+ <item><p>Human translation revision provenance related information specified by exactly one of the following:
+ <list type="unordered">
+ <item><p>A <att>transRevPerson</att> attribute that contains a string identifying a human translation revision agent.</p></item>
+ <item><p>A <att>transRevPersonRef</att> attribute that contains an IRI referring to a resource that identifies a human translation revision agent.</p></item>
+ <item><p>A <att>transRevPersonPointer</att> attribute that contains a <ref target="#selectors">relative selector</ref> pointing to a node with the exact same semantics as <att>transRevPerson</att>.</p></item>
+ <item><p>A <att>transRevPersonRefPointer</att> attribute that contains a <ref target="#selectors">relative selector</ref> pointing to a node with the exact same semantics as <att>transRevPersonRef</att>.</p></item>
+ </list></p></item>
+ <item><p>Organizational revision translation related provenance information specified by exactly of the following:
+ <list type="unordered">
+ <item><p>A <att>transRevOrg</att> attribute that contains a string identifying an organization acting as a translation revision agent.</p></item>
+ <item><p>A <att>transRevOrgRef</att> attribute that contains an IRI referring to a resource that identifies an organization acting as a translation revison agent.</p></item>
+ <item><p>A <att>transRevOrgPointer</att> attribute that contains a <ref target="#selectors">relative selector</ref> pointing to a node with the exact same semantics as transRevOrg.</p></item>
+ <item><p>A <att>transRevOrgRefPointer</att> attribute that contains a <ref target="#selectors">relative selector</ref> pointing to a node with the exact same semantics as transRevOrgRef.</p></item>
+
+ </list></p></item>
+ <item><p>Translation tool revision provenance related information specified by exactly one of the following:</p>
+ <list type="unordered">
+ <item><p>A <att>transRevTool</att> attribute that contains a string identifying a software tool that was used in revising the translation of the selected content.</p></item>
+ <item><p>A <att>transRevToolRef</att> attribute that contains an IRI referring to a resource that identifies a software tool that was used in revising the translation of the selected content.</p></item>
+ <item><p>A <att>transRevToolPointer</att> attribute that contains a <ref target="#selectors">relative selector</ref> pointing to a node with the exact same semantics as transRevTool.</p></item>
+ <item><p>A <att>transRevToolRefPointer</att> attribute that contains a <ref target="#selectors">relative selector</ref> pointing to a node with the exact same semantics as transRevToolRef.</p></item>
+ </list></item>
+ <item><p>A reference to external, RDF-based provenance description specified by exactly one of the following:</p>
+ <list type="unordered">
+ <item><p>A <att>provRef</att> attribute that that contains one or more space (U+0020) separated Provenance URI, each referring to a resource that identifies a different provenance entity record defined by the <ref target="http://www.w3.org/TR/prov-dm/">provenance data model</ref>.</p></item>
+ <item><p>A <att>provRefPointer</att> attribute that contains a <ref target="#selectors">relative selector</ref> pointing to a node with the exact same semantics as provRef.</p></item>
+ </list></item>
+ </list></item>
+ </list>
+ <note type="ed">Below note is taken from the quality issue data category. Same question applies: Why should below only say "do not apply to HMTL as local markup"? There is local markup for direct annotation in XML too.</note>
+ <note>
+ <p>The attributes <att>translationProvenanceRecordsRefPointer</att>, <att>transPersonPointer</att>, <att>transPersonRefPointer</att>, <att>transOrgPointer</att>, <att>transOrgRefPointer</att>, <att>transToolPointer</att>, <att>transToolRefPointer</att>, <att>transRevPersonPointer</att>, <att>transRevPersonRefPointer</att>, <att>transRevOrgPointer</att>, <att>transRevOrgRefPointer</att>, <att>transRevToolPointer</att>, <att>transRevToolRefPointer</att> and <att>provRefPointer</att> do not apply to HTML as local markup is provided for direct annotation in HTML.</p>
+ </note>
+ <exemplum xml:id="EX-translation-agent-provenance-global-1">
+ <head>The <ref target="#translation-agent-provenance">Translation Agent Provenance</ref> data category used globally.</head>
+ <p>This example shows how the provenance of the <code>par</code> and the <code>legalnotice</code> elements in this XML document is different. Therefore it is recorded in separate <gi>transProvRule</gi> elements.</p>
+ <egXML xmlns="http://www.tei-c.org/ns/Examples"
+ target="examples/xml/EX-translation-agent-provenance-global-1.xml"/>
+ </exemplum>
+ <exemplum xml:id="EX-translation-agent-provenance-global-2">
+ <head>The <ref target="#translation-agent-provenance">Translation Agent Provenance</ref> data category used globally with pointer attributes.</head>
+ <p>This example expresses the same provenance information as <ptr target="#EX-translation-agent-provenance-global-1" type="exref"/>, but the provenance information for the <code>par</code> element is stored differently, inside a format specific element <code>my-provenance-info</code>. The first <gi>transProvRule</gi> element and its attributes <att>transToolRefPointer</att>, <att>transOrgPointer</att>, <att>transRevToolRefPointer</att>, <att>transRevOrgPointer</att> and <att>provRefPointer</att> are used to point to the information inside that <code>my-provenance-info</code> element.</p>
+ <egXML xmlns="http://www.tei-c.org/ns/Examples"
+ target="examples/xml/EX-translation-agent-provenance-global-2.xml"/>
</exemplum>
- <p xml:id="translation-agent-provenance-local">LOCAL: The <gi>transProvRule</gi> element contains the following:</p>
- <list><item><p>Human translation provenance information specified by a <att>transPerson</att> OR a <att>transPersonRef</att> attribute.</p></item>
- <item><p>Organisational translation provenance information specified by a <att>transOrg</att> OR a <att>transOrfRef</att> attribute.</p></item>
- <item><p>Translation tool provenance information specified by a <att>transTool</att> OR a <att>transToolRef</att> attribute.</p></item>
- </list>
- <p>The semantics of the six local attributes for the <ref target="#translation-agent-provenance">Translation Agent Provenance</ref> data categories are identical to their <ref target="#translation-agent-provenance-global">global counterparts</ref> with the same name.</p>
- <exemplum xml:id="EX-translation-agent-provenance-xml-local-1">
- <head>The <ref target="#translation-agent-provenance">Translation Agent Provenance</ref> data category used locally.</head>
- <p>The example is identical to <ptr target="#EX-translation-agent-provenance-xml-global-1" type="exref"/>, that is, it conveys the same ITS <ref target="#translation-agent-provenance">Translation Agent Provenance</ref>, but now locally.</p>
- <egXML xmlns="http://www.tei-c.org/ns/Examples" target="examples/xml/EX-translation-agent-provenance-xml-local-1.xml"/>
+ <note type="ed">Not sure if we need the standoff version globally. We don't have it with quality either. Thoughts?</note>
+ <exemplum xml:id="EX-translation-agent-provenance-global-3">
+ <head>The <ref target="#translation-agent-provenance">Translation Agent Provenance</ref> data category used globally with standoff provenance records.</head>
+ <p>This example expresses the same plus some additional provenance information as <ptr target="#EX-translation-agent-provenance-global-1" type="exref"/>, but the provenance information is realized standoff within <code>translationProvenanceRecords</code> elements. The <gi>transProvRule</gi> elements with the <att>translationProvenanceRecordsRef</att> attributes point to <code>translationProvenanceRecords</code> related to the <code>par</code> and <code>legalnotice</code> elements. The <code>legalnotice</code> element has been revised two times. Hence, the related <gi>translationProvenanceRecords</gi> element contains two <gi>translationProvenanceRecord</gi> child elements. The second <gi>translationProvenanceRecord</gi> child element provides information about the second revison.</p>
+ <egXML xmlns="http://www.tei-c.org/ns/Examples"
+ target="examples/xml/EX-translation-agent-provenance-global-3.xml"/>
</exemplum>
+ <exemplum xml:id="EX-translation-agent-provenance-html5-global-1">
+ <head>Annotating provenance information in HTML5 with <gi>transProvRule</gi>
+ element</head>
+ <p>The <gi>transProvRule</gi> element resides in a separate file
+ (<ptr target="#EX-translation-agent-provenance-rule-html5-global-l" type="exref"
+ />) that associates the provenance information with a selected span of
+ content in the HTML document.</p>
+ <egXML xmlns="http://www.tei-c.org/ns/Examples"
+ target="examples/html5/EX-translation-agent-provenance-html5-global-1.html"
+ type="html5"/>
+ </exemplum>
+ <exemplum xml:id="EX-translation-agent-provenance-rule-html5-global-l">
+ <head>External rule document associated with an HTML5 document</head>
+ <p>This document is used in <ptr
+ target="#EX-translation-agent-provenance-html5-global-1" type="exref"/>:</p>
+ <egXML xmlns="http://www.tei-c.org/ns/Examples"
+ target="examples/html5/EX-translation-agent-provenance-rule-html5-global-1.xml"/>
+ </exemplum>
+ <p xml:id="translation-agent-provenance-local">LOCAL: Using the inline markup to represent the
+ data category locally is limited to a single occurrence for a given
+ content (e.g. one cannot have different <att>transToolRef</att>
+ attributes applied to the same span of text because the inner-most one
+ would override the others). A local <emph>standoff markup</emph> is
+ provided to allow such cases.</p>
+ <p>The following local markup is available for the <ref target="#translation-agent-provenance">Translation Agent Provenance</ref> data category:</p>
+ <list type="unordered">
+ <item><p>Either (inline markup): at least one of the following, with the same semantics as the corresponding attributes at the <gi>transProvRule</gi> element:</p>
+ <list type="unordered">
+ <item><p>Human translation provenance information specified by exactly a <att>transPerson</att> or a <att>transPersonRef</att> attribute.</p></item>
+ <item><p>Organizational translation provenance information specified by exactly a <att>transOrg</att> or a <att>transOrgRef</att> attribute.</p></item>
+
+ <item><p>Translation tool provenance related information specified by exactly a <att>transTool</att> or a <att>transToolRef</att> attribute.</p></item>
+ <item><p>Human translation revision provenance related information specified by exactly a <att>transRevPerson</att> or a <att>transRevPersonRef</att> attribute.</p></item>
+ <item><p>Organizational revision translation related provenance information specified by exactly a <att>transRevOrg</att> or a <att>transRevOrgRef</att> attribute.</p></item>
+ <item><p>Translation tool revision provenance related information specified by exactly a <att>transRevTool</att> or a <att>transRevToolRef</att> attribute.</p></item>
+ <item><p>A reference to external, RDF-based provenance description specified by a <att>provRef</att> attribute.</p></item>
+ </list></item>
+
+ <item><p>Or (standoff markup):</p>
+ <list type="unordered">
+ <item><p>A <att>translationProvenanceRecordsRef</att> attribute. Its value
+ is a URI pointing to the <gi>translationProvenanceRecords</gi>
+ element containing the list of provenance information related to this
+ content.</p></item>
+ <item><p>An element <gi>translationProvenanceRecords</gi> (or <code><span
+ its-translation-provenance-records></code> in HTML) which
+ contains:</p>
+ <list type="unordered">
+ <item><p>One or more elements <gi>translationProvenanceRecord</gi>
+ (or <code><span its-translation-provenance-record></code>
+ in HTML), each of which contains at least one of the following, with the same semantics as the corresponding attributes at the <gi>transProvRule</gi> element:</p>
+ <list type="unordered">
+ <item><p>Human translation provenance information specified by exactly a <att>transPerson</att> or a <att>transPersonRef</att> attribute.</p></item>
+ <item><p>Organizational translation provenance information specified by exactly a <att>transOrg</att> or a <att>transOrgRef</att> attribute.</p></item>
+
+ <item><p>Translation tool provenance related information specified by exactly a <att>transTool</att> or a <att>transToolRef</att> attribute.</p></item>
+ <item><p>Human translation revision provenance related information specified by exactly a <att>transRevPerson</att> or a <att>transRevPersonRef</att> attribute.</p></item>
+ <item><p>Organizational revision translation related provenance information specified by exactly a <att>transRevOrg</att> or a <att>transRevOrgRef</att> attribute.</p></item>
+ <item><p>Translation tool revision provenance related information specified by exactly a <att>transRevTool</att> or a <att>transRevToolRef</att> attribute.</p></item>
+ <item><p>A reference to external, RDF-based provenance description specified by a <att>provRef</att> attribute.</p></item>
+ </list>
+ </item>
+ </list>
+ </item>
+ </list>
+ </item>
+ </list>
+ <p>Important: <list><item><p>When the attributes <att>transPerson</att>, <att>transPersonRef</att>, <att>transOrg</att>, <att>transOrgRef</att>, <att>transTool</att>, <att>transToolRef</att>, <att>transRevPerson</att>, <att>transRevPersonRef</att>, <att>transRevOrg</att>, <att>transRevOrgRef</att>, <att>transRevTool</att>, <att>transRevToolRef</att> and <att>provRef</att> (or their equivalent
+ representations) are used in in a standoff manner, the information they
+ carry pertains to the content of the element that refers to the standoff
+ annotation, not to the content of the element <gi>translationProvenanceRecord</gi>
+ (or <code><span translation-provenance-record></code>in HTML) where they are
+ declared.</p></item>
+ <item><p>The order of <gi>translationProvenanceRecord</gi> elements inside <gi>translationProvenanceRecords</gi> is significant: it reflects the temporal order of revisions. This is demonstrated e.g. in <ptr target="#EX-translation-agent-provenance-html5-local-2" type="exref"/>.</p></item></list></p>
+
+ <exemplum xml:id="EX-translation-agent-provenance-local-1">
+ <head>Annotating provenance information in XML with local inline markup</head>
+ <p>The provenance related attributes at the <code>par</code> and <code>legalnotice</code> elements are used to associate the provenance information directly with the content of theses elements.</p>
+ <egXML xmlns="http://www.tei-c.org/ns/Examples"
+ target="examples/xml/EX-translation-agent-provenance-local-1.xml"/>
+ </exemplum>
+ <exemplum xml:id="EX-translation-agent-provenance-html5-local-1">
+ <head>Annotating provenance information in HTML with local inline markup</head>
+ <p>In this example several spans of content are associated with provenance information.</p>
+ <egXML xmlns="http://www.tei-c.org/ns/Examples"
+ target="examples/html5/EX-translation-agent-provenance-html5-local-1.html"
+ type="html5"/>
+ </exemplum>
+
+ <exemplum xml:id="EX-translation-agent-provenance-local-2">
+ <head>Annotating provenance information in XML with local standoff markup</head>
+ <p>The following example shows a document using local standoff markup to
+ encode several pieces of provenance information. The <code>par</code> and <code>legalnotice</code> elements delemit the content to markup. They hold <att>translationProvenanceRecordsRef</att> attributes that point to the related <gi>translationProvenanceRecords</gi> elements. The <code>legalnotice</code> element has been revised two times. Hence, the related <gi>translationProvenanceRecords</gi> element contains two <gi>translationProvenanceRecord</gi> child elements. The second <gi>translationProvenanceRecord</gi> child element provides information about the second revison.</p>
+ <egXML xmlns="http://www.tei-c.org/ns/Examples"
+ target="examples/xml/EX-translation-agent-provenance-local-2.xml"/>
+ </exemplum>
+ <exemplum xml:id="EX-translation-agent-provenance-local-3">
+ <head>Annotating provenance information in XML with local standoff markup and a global
+ rule</head>
+ <p>The following example shows a document using local standoff markup to
+ encode several pieces of provenance information. But because, in this case, the
+ <code>par</code> or the <code>legal notice</code> elements do not allow attributes from another
+ namespace we cannot use <att>translationProvenanceRecordsRef</att> directly.
+ Instead, a global rule is used to map the function of
+ <att>translationProvenanceRecordsRef</att> to a non-ITS construct, here the
+ <code>ref</code> attribute of the <code>par</code> or <code>legal notice</code> elements.</p>
+ <egXML xmlns="http://www.tei-c.org/ns/Examples"
+ target="examples/xml/EX-translation-agent-provenance-local-3.xml"/>
+ </exemplum>
+ <exemplum xml:id="EX-translation-agent-provenance-html5-local-2">
+ <head>Annotating provenance information in HTML with local standoff markup</head>
+ <p>The following example shows a document using local standoff markup to
+ encode provenance information. The <code>p</code> elements delimits the
+ content to markup. It holds a <att>its-translation-provenance-records-ref</att>
+ attribute that points to the standoff information inside the <code>script</code> element.</p>
+ <egXML xmlns="http://www.tei-c.org/ns/Examples"
+ target="examples/html5/EX-translation-agent-provenance-html5-local-2.html"
+ type="html5"/>
+ </exemplum>
+ <note type="ed">TODO for above: Finalize how HTML should work: use its-* attributes for standoff markup or markup inside the script element.</note>
</div>
</div>
<div xml:id="TextAnalyisAnnotation">
@@ -3870,6 +4049,7 @@
</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>,
@@ -3920,8 +4100,8 @@
attributes applied to the same span of text because the inner-most one
would override the others). A local <emph>standoff markup</emph> is
provided to allow such cases.</p>
- <p>The following local markup is available for the Localization Quality
- Issue data category:</p>
+ <p>The following local markup is available for the <ref target="#lqissue">Localization Quality
+ Issue</ref> data category:</p>
<list type="unordered">
<item><p>Either (inline markup):</p>
<list type="unordered">
@@ -3952,6 +4132,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>
<list type="unordered">
<item><p>One or more elements <gi>locQualityIssue</gi>
(or <code><span its-loc-quality-issue></code>
@@ -4048,8 +4229,7 @@
target="examples/html5/EX-locQualityIssue-html5-local-2.html"
type="html5"/>
</exemplum>
- <note type="ed">TODO for above: Finalize how HTML its-loc-quality-issues and
- its-loc-quality-issue should be defined.</note>
+ <note type="ed">TODO for above: Finalize how HTML should work: use its-* attributes for standoff markup or markup inside the script element.</note>
</div>
</div>
@@ -5205,7 +5385,11 @@
<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="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/"
@@ -5501,7 +5685,7 @@
target="http://www.w3.org/TR/2012/WD-its20-20120829/">ITS 2.0 Working Draft
29 August 2012</ref>.</p>
<list type="ordered">
- <item>Added <ptr target="#translation-agent-provenance" type="specref"/></item>
+ <item>Added a first draft of <ptr target="#translation-agent-provenance" type="specref"/></item>
<item>Added <ptr type="specref" target="#html5-markup"/>.</item>
<item>Removed inline markup declarations.</item>
<item>Addition of a <att>locQualityPrecisVote</att> attribute and a
Index: its20.html
===================================================================
RCS file: /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/its20.html,v
retrieving revision 1.192
retrieving revision 1.193
diff -u -d -r1.192 -r1.193
--- its20.html 17 Oct 2012 16:31:14 -0000 1.192
+++ its20.html 18 Oct 2012 07:49:15 -0000 1.193
@@ -12,7 +12,7 @@
1.0</a>; it is designed to foster the creation of multilingual Web content,
focusing on HTML5, XML based formats in general, and to leverage localization
workflows based on the XML Localization Interchange File Format (XLIFF). In addition
- to HTML5 and XML, algorithms to convert ITS attributes to NIF are
+ to using ITS 2.0 for HTML5 and XML content, an algorithm to convert that content NIF are
provided.</p></div><div>
<h2><a name="status" shape="rect">Status of this Document</a></h2><p><strong>This document is an editors' copy that has no official
standing.</strong></p></div><div class="toc">
@@ -53,9 +53,9 @@
<div class="toc3">5.2.2 <a href="#selection-local" shape="rect">Local Selection in an XML Document</a></div>
</div>
[...1074 lines suppressed...]
xmlns:sch="http://www.ascc.net/xml/schematron" >
<!-- Schematron document to test constraints for global and local ITS markup.
@@ -3757,7 +4027,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="d3e9222" id="d3e9222" shape="rect"/>Example 98: NVDL schema for ITS</div><div class="exampleInner"><pre xml:space="preserve">
+ during validation against this NVDL document/schema.</p><div class="exampleOuter"><div class="exampleHeader"><a name="d3e9920" id="d3e9920" shape="rect"/>Example 106: NVDL schema for ITS</div><div class="exampleInner"><pre xml:space="preserve">
<nvdl:rules
xmlns:nvdl="http://purl.oclc.org/dsdl/nvdl/ns/structure/1.0" >
<nvdl:namespace ns="http://www.w3.org/2005/11/its">
@@ -3816,7 +4086,7 @@
</html></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-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 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
+ 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
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
Received on Thursday, 18 October 2012 07:49:22 UTC