- From: Yves Savourel via cvs-syncmail <cvsmail@w3.org>
- Date: Wed, 22 Aug 2012 12:12:42 +0000
- To: public-multilingualweb-lt-commits@w3.org
Update of /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20
In directory hutz:/tmp/cvs-serv26241
Modified Files:
its20.html its20.odd
Log Message:
Continued implementation of loc quality
Index: its20.odd
===================================================================
RCS file: /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/its20.odd,v
retrieving revision 1.124
retrieving revision 1.125
diff -u -d -r1.124 -r1.125
--- its20.odd 22 Aug 2012 11:45:22 -0000 1.124
+++ its20.odd 22 Aug 2012 12:12:39 -0000 1.125
@@ -4474,11 +4474,22 @@
and <att>locQualityIssueProfileRef</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>locQualityIssue</gi> (or <code><span loc-quality-issue></code>in HTML) where they are declared.</p>
- <exemplum xml:id="EX-locQualityNote-local-1">
- <head>TODO</head>
- <p>TODO</p>
- </exemplum>
+ <exemplum xml:id="EX-locQualityIssue-local-1">
+ <head>Annotating an issue in XML with local inline markup</head>
+ <p>The attributes <att>locQualityIssueType</att>, <att>locQualityIssueComment</att> and
+ <att>locQualityIssueSeverity</att> are used to
+ associate the issue information directly with a selected span of content.</p>
+ <egXML xmlns="http://www.tei-c.org/ns/Examples"
+ target="examples/xml/EX-locQualityIssue-local-1.xml" />
+ </exemplum>
+ <exemplum xml:id="EX-locQualityIssue-html5-local">
+ <head>Annotating an issue in HTML with local inline markup</head>
+ <p>In this example several spans of content are assocaited with a quality issue.</p>
+ <egXML xmlns="http://www.tei-c.org/ns/Examples"
+ target="examples/html5/EX-locQualityIssue-html5-local.html" />
+ </exemplum>
+
<p xml:id="lqissue-typevalues">Values for the Localization Quality Issue Type:</p>
<p>The <att>locQualityIssueType</att> attribute provides a basic level of interoperability between different localization quality
assurance systems. It offers a list of high-level quality issue types common in automatic and human localization quality assessment.
Index: its20.html
===================================================================
RCS file: /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/its20.html,v
retrieving revision 1.124
retrieving revision 1.125
diff -u -d -r1.124 -r1.125
--- its20.html 22 Aug 2012 11:45:22 -0000 1.124
+++ its20.html 22 Aug 2012 12:12:39 -0000 1.125
@@ -2402,7 +2402,95 @@
<a href="#lqissueDefs" shape="rect">profile reference information</a>.</p></li></ul></li></ul></li></ul></li></ul><p>Important: When the attributes <a class="itsmarkup" href="#locQualityIssueRule.attributes" shape="rect">locQualityIssueType</a>, <a class="itsmarkup" href="#locQualityIssueRule.attributes" shape="rect">locQualityIssueComment</a>, <a class="itsmarkup" href="#locQualityIssueRule.attributes" shape="rect">locQualityIssueSeverity</a>
and <a class="itsmarkup" href="#locQualityIssueRule.attributes" shape="rect">locQualityIssueProfileRef</a> (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
- <a class="itsmarkup" href="#locQualityIssue" shape="rect">locQualityIssue</a> (or <code><span loc-quality-issue></code>in HTML) where they are declared.</p><div class="exampleOuter"><div class="exampleHeader"><a name="EX-locQualityNote-local-1" id="EX-locQualityNote-local-1" shape="rect"/>Example 71: TODO</div><p>TODO</p></div><p id="lqissue-typevalues">Values for the Localization Quality Issue Type:</p><p>The <a class="itsmarkup" href="#locQualityIssueRule.attributes" shape="rect">locQualityIssueType</a> attribute provides a basic level of interoperability between different localization quality
+ <a class="itsmarkup" href="#locQualityIssue" shape="rect">locQualityIssue</a> (or <code><span loc-quality-issue></code>in HTML) where they are declared.</p><div class="exampleOuter"><div class="exampleHeader"><a name="EX-locQualityIssue-local-1" id="EX-locQualityIssue-local-1" shape="rect"/>Example 71: Annotating an issue in XML with local inline markup</div><p>The attributes <a class="itsmarkup" href="#locQualityIssueRule.attributes" shape="rect">locQualityIssueType</a>, <a class="itsmarkup" href="#locQualityIssueRule.attributes" shape="rect">locQualityIssueComment</a> and
+ <a class="itsmarkup" href="#locQualityIssueRule.attributes" shape="rect">locQualityIssueSeverity</a> are used to
+ associate the issue information directly with a selected span of content.</p><div class="exampleInner"><pre xml:space="preserve">
+<doc
+ xmlns:its="http://www.w3.org/2005/11/its"
+ its:version="2.0">
+ <para>
+ <span
+ its:locQualityIssueType="typographical"
+ its:locQualityIssueComment="Sentence without capitalization"
+ its:locQualityIssueSeverity="50">this</span> is an example</para>
+</doc></pre></div><p>[Source file: <a href="examples/xml/EX-locQualityIssue-local-1.xml" shape="rect">examples/xml/EX-locQualityIssue-local-1.xml</a>]</p></div><div class="exampleOuter"><div class="exampleHeader"><a name="EX-locQualityIssue-html5-local" id="EX-locQualityIssue-html5-local" shape="rect"/>Example 72: Annotating an issue in HTML with local inline markup</div><p>In this example several spans of content are assocaited with a quality issue.</p><div class="exampleInner"><pre xml:space="preserve">
+<html lang="en">
+ <head>
+ <title>Telharmonium 1897</title>
+ <style type="text/css">
+ [its-loc-quality-type]{
+ border:1px solid green;
+ margin:2px;
+ }
+ [its-loc-quality-issue-type = untranslated]{
+ background-color:red;
+ }
+ [its-loc-quality-issue-type = whitespace]{
+ background-color:yellow;
+ }
+ [its-loc-quality-issue-type = inconsistent-entities]{
+ background-color:#9DFFE1;
+ }
+ [its-loc-quality-issue-type = spelling]{
+ background-color:#FFE2F7;
+ }
+ [its-loc-quality-issue-severity = "100"]{
+ border: 6px solid red;
+ }
+ [its-loc-quality-issue-profile-ref = "abc"]:before{
+ content:"⇛";
+ }
+ [its-loc-quality-issue-profile-ref = "abc"]:after{
+ content:"⇚";
+ }
+ [its-loc-quality-issue-profile-ref = "grammar"]:before{
+ content:"❮";
+ }
+ [its-loc-quality-issue-profile-ref = "grammar"]:after{
+ content:"❯";
+ }
+ </style>
+ </head>
+ <body>
+ <h1
+ id="h0001"
+ its-loc-quality-issue-profile-ref="abc"
+ its-loc-quality-issue-type="untranslated"
+ data-mytool-qacode="target_equals_source">Telharmonium (1897)</h1>
+ <p id="p0001">
+ <span class="segment" id="s0001">
+ <span
+ its-loc-quality-issue-profile-ref="abc"
+ its-loc-quality-issue-type="inconsistent-entities"
+ its-loc-quality-issue-comment="Should be Thomas Cahill. Why is Batman in the picture?"
+ its-loc-quality-issue-severity="100"
+ data-mytool-qacode="named_entity_not_found">Christian Bale</span>
+ <span
+ its-loc-quality-issue-profile-pointer="abc"
+ its-loc-quality-issue-type="whitespace"
+ its-loc-quality-issue-severity="10"
+ data-mytool-qacode="extra_space_around_punctuation">(1867 – 1934)</span>
+ conceived of an instrument that could transmit its
+ sound from a power plant for hundreds of miles to
+ listeners over telegraph wiring.
+ </span>
+ <span class="segment" id="s0002">Beginning in 1889 the sound
+ quality of regular telephone concerts was very poor on
+ account of the buzzing generated by carbon-granule
+ microphones. As a result Cahill decided to set a new
+ standard in perfection of sound
+ <span
+ its-loc-quality-issue-profile-ref="grammar"
+ its-loc-quality-issue-type="spelling"
+ its-loc-quality-issue-severity="50"
+ its-loc-quality-issue-comment="should be "quality"">qulaity</span>
+ with his instrument, a standard that would not only satisfy
+ listeners but that would overcome all the flaws of traditional
+ instruments.
+ </span>
+ </p>
+ </body>
+</html></pre></div><p>[Source file: <a href="examples/html5/EX-locQualityIssue-html5-local.html" shape="rect">examples/html5/EX-locQualityIssue-html5-local.html</a>]</p></div><p id="lqissue-typevalues">Values for the Localization Quality Issue Type:</p><p>The <a class="itsmarkup" href="#locQualityIssueRule.attributes" shape="rect">locQualityIssueType</a> attribute provides a basic level of interoperability between different localization quality
assurance systems. It offers a list of high-level quality issue types common in automatic and human localization quality assessment.
Tools can map their internal categories to these categories in order to exchange information about the kinds of issues they
identify and take appropriate action even if another tool does not know the specific issues identified by the generating tool.</p><p>The values listed in the following table are allowed for <a class="itsmarkup" href="#locQualityIssueRule.attributes" shape="rect">locQualityIssueType</a>. The values a tool implementing the data category
@@ -2833,7 +2921,7 @@
<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="its-schematron-constraints" id="its-schematron-constraints" shape="rect"/>E Checking ITS Markup Constraints With Schematron (Non-Normative)</h2><p>
<em>This section is informative.</em>
</p><p>Several constraints of ITS markup cannot be validated with ITS schemas. The following <a title="Rule-based validation -- Schematron" href="#schematron" shape="rect">[Schematron]</a> document allows for validating some of these
- constraints.</p><div class="exampleOuter"><div class="exampleHeader"><a name="d3e8997" id="d3e8997" shape="rect"/>Example 72: Testing constraints in ITS markup</div><div class="exampleInner"><pre xml:space="preserve">
+ constraints.</p><div class="exampleOuter"><div class="exampleHeader"><a name="d3e9025" id="d3e9025" shape="rect"/>Example 73: Testing constraints in ITS markup</div><div class="exampleInner"><pre xml:space="preserve">
<sch:schema
xmlns:sch="http://www.ascc.net/xml/schematron" >
<!-- Schematron document to test constraints for global and local ITS markup.
@@ -2900,7 +2988,7 @@
<em>This section is informative.</em>
</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="d3e9019" id="d3e9019" shape="rect"/>Example 73: NVDL schema for ITS</div><div class="exampleInner"><pre xml:space="preserve"><rules xmlns="http://purl.oclc.org/dsdl/nvdl/ns/structure/1.0"> <namespace
+ attributes of host language are ignored during validation against this NVDL document/schema.</p><div class="exampleOuter"><div class="exampleHeader"><a name="d3e9047" id="d3e9047" shape="rect"/>Example 74: NVDL schema for ITS</div><div class="exampleInner"><pre xml:space="preserve"><rules xmlns="http://purl.oclc.org/dsdl/nvdl/ns/structure/1.0"> <namespace
ns="http://www.w3.org/2005/11/its"> <validate schema="its-elements.rng"/>
</namespace> <namespace ns="http://www.w3.org/2005/11/its" match="attributes">
<validate schema="its-attributes.rng"/> </namespace> <anyNamespace>
Received on Wednesday, 22 August 2012 12:12:48 UTC