This document outlines the way in which the MultilingualWeb-LT Working Group addressed the comments submitted during the first ITS 2.0 Last Call period, starting 2012-12-06 and ending (after extension) 2013-01-18. The document also includes comments received after 2013-01-18, but not comments received after 2013-05-21.
Please send detailed comments on this document to public-multilingualweb-lt-comments@w3.org.
This document is based on an auto-generated version, that was created with an XSLT stylesheet relying on the DisCo tool and using pre-defined keywords in tracker.
Total number of comments: 65.
Duplicates: 2.
| - | Reviewer satisfied | Reviewer not satisfied | No reply from reviewer | No resolution yet |
| WG accepted comment | 50 | 0 | 0 | 0 |
| WG rejected comment | 13 | 0 | 0 |
| Issue | First recorded | Resolution ("accepted" or "rejected") |
Commenter feedback ("satisfied" or "unsatisfied") |
Change type ("editorial" or "substantive" or "none") |
Decision details |
|---|---|---|---|---|---|
| issue-58: example 26 (Accumulation and Overriding of the annotatorsRef Values) | 2012-12-09 | accepted | satisfied (mail) | editorial | just an example fix |
| issue-59: Clarify "pointing and adding" sentence | 2012-12-10 | accepted | satisfied (mail) | editorial | just a clarification, didn't influence any implementation behavior |
| issue-60: New value for "Values for the Localization Quality Issue Type": "unintelligible" | 2012-12-11 | rejected | satisfied (mail) | editorial | proposal was rejected. Use case of new value was accomodated by clarifying definition of existing value |
| issue-61: Editorial comments from Naoto on sec. 1-2 | 2012-12-12 | accepted | satisfied (mail) | editorial | comment will be merged into ongoing revision of non-normative sections 1-2 |
| issue-62: description problem for the global rules for localization quality issue | 2012-12-12 | accepted | satisfied (mail) | editorial | involved a schema change, aligning the definition of global with local, but no change of examples or test suite or implementations |
| issue-63: New value for "Values for the Localization Quality Issue Type": "conformance" | 2012-12-14 | accepted | satisfied (mail) | editorial | Editorial action completed by Felix.This new value received support in the discussion. The new value will be introduced as "non-conformance".Call for consensus made and succeeded in the WG meeting Feb 27, 2013 |
| issue-64: Removing disambigClassPointer attribute | 2012-12-20 | accepted | satisfied (mail) | editorial | attribute definition was an oversight, not used in any tests, examples or implementations |
| issue-65: Need to clarify global provenance | 2012-12-20 | accepted | satisfied (mail) | editorial | only explanatory text clarification |
| issue-66: Location of its:version attribute | 2012-12-30 | accepted | satisfied (mail) | editorial | change doesn't invalidate existing tests or implementations and is going to be covered by schematron test |
| issue-67: Change definition of regular expression for allowed characters | 2013-01-04 | accepted | satisfied (mail) | substantive | borderline substantive.Pending actions taken over by Pablo, should be able to close by April 5.we use the limited regex subset Shaun identified in response to ACTION-385 in the Allowed Characters data category, together with an accompanying note on best practice for unicode normalisation that Shaun is addressing under ACTION-430 |
| issue-68: Disambiguation (and term) | 2013-01-10 | rejected | satisfied (mail) | substantive | Merger of the categories was rejected. The discussion led however to editorial changes of the Disambiguation category (renaming and simplification). |
| issue-69: recursive nesting of external rules | 2013-01-10 | accepted | satisfied (mail) | editorial | clarification |
| issue-70: Defined order of precedence missing inherited local values | 2013-01-10 | accepted | satisfied (mail) | editorial | The editorial action-437 is done, waiting for Chase and Kevin to come back..As per minutes http://www.w3.org/2013/01/23-mlw-lt-minutes.html#item05 this is to be clarified with an editorial action-437 by Felix |
| issue-71: Section 5.8 (annotatorsRef) | 2013-01-10 | accepted | satisfied (mail) | editorial | borderline substantive |
| issue-72: Section 8.12 (Provenance Data Category) | 2013-01-10 | accepted | satisfied (mail) | editorial | Though it was agreed not to add timestamps, the ordering of record is addressed by adding the following text to the provenance data category: "The order of its:provenanceRecord elements within a its:provenanceRecords element should reflect the order with which they were added to the document, with the most recently added one listed first."Correspondingly, in the LQI data category, the following text is to be added the following after the:definition of locQualityIssues:"The order of its:locQualityIssue elements within a its:locQualityIssues element should reflect the order with which they were added to the document, with the most recently added one listed first." |
| issue-73: NIF comments | 2013-01-10 | accepted | satisfied (mail) | editorial | Editorial action pending. To be closed once action-460 completed.See http://lists.w3.org/Archives/Public/public-multilingualweb-lt-comments/2013Feb/0047.html |
| issue-74: Comment on ITS 2.0 WD-its20-20121206 - Section 1.1 (Relation to ITS 1.0 and New Principles) | 2013-01-10 | accepted | satisfied (mail) | editorial | D.Lewis and D.Filip to collaborate with Christian to integrate comments into section 1.1 text. change is covered by issue-129 |
| issue-75: Comments related to "domain" | 2013-01-10 | rejected | satisfied (mail) | editorial | Closed with action-434.Suggestions for domain meta-data including preference hierarchies were rejected as representing new features, and will be recorded as future feature requests. Christian has provided clarifying text (http://lists.w3.org/Archives/Public/public-multilingualweb-lt-comments/2013Feb/0059.html) explaining the data category reflects the basic need of annotation and does not, common with other data-categories, support semantics that can be used over a specific for of downstream workflow. This will be included in the spec as a note. |
| issue-76: clarification of "inconsistency" quality issue type needed | 2013-01-11 | accepted | satisfied (mail) | editorial | Editorial Action-392 completed by Felix. Accepted at the Prague F2Fhttp://www.w3.org/2013/01/23-mlw-lt-minutes.html#item15The resolution was to broaden the category description to explicitly cover the commenter's use case and provide a second example. |
| issue-77: Precedence of global rules in HTML if both links and inline rules with "script" are available | 2013-01-11 | accepted | satisfied (mail) | editorial | Editorial action done, minor clarification.Clarified in the section "Precedence between Selections" (#html5-selection-precedence) that in HTML (like in XML) global rules are to be read in document order. |
| issue-78: I18N-ISSUE-203: Use of rel values in HTML | 2013-01-15 | rejected | satisfied (mail) | none | No action needed. See: http://www.w3.org/2013/01/23-mlw-lt-minutes.html#item16 |
| issue-79: I18N-ISSUE-204: Use of namespaces and HTML | 2013-01-15 | accepted | satisfied (mail) | editorial | Clarification:In section 3.1 replace:"The namespace prefix used in this specification for this URI is “itsâ€. It is recommended that implementations of this specification use this prefix."with:"The namespace prefix used in this specification for XML implementationsof ITS for the above URI is “itsâ€. 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: "its-" is used to indicate ITS2.0 attributes in HTML documents. See [reference tohttp://www.w3.org/TR/2012/WD-its20-20121206/#html5-local-attributes]for details." |
| issue-80: I18N-ISSUE-205: Examples of html markup in section 6 | 2013-01-15 | accepted | satisfied (mail) | editorial | Added references to section on HTML5 global rules referencing example elsewhere in the document (to save space):http://www.w3.org/International/multilingualweb/lt/drafts/its20/its20.html#html5-global-rules |
| issue-81: I18N-ISSUE-207: Term data category and dfn element [Related comments: issue-89] | 2013-01-15 | accepted | satisfied (mail) | editorial | editorial and waiting for editing action action-431 |
| issue-82: I18N-ISSUE-208: Mapping domains to nothing | 2013-01-15 | rejected | satisfied (mail) | none | the comment is already addressed sufficiently by the existing behaviour, see:http://lists.w3.org/Archives/Public/public-multilingualweb-lt-comments/2013Jan/0170.html |
| issue-83: Notes on loc quality issue section | 2013-01-15 | accepted | satisfied (mail) | editorial | commentor did the (editorial) edits |
| issue-84: translate ITS 2.0 requirements w.r.t Indian [Indic] languages | 2013-01-18 | rejected | satisfied (mail) | none | It was agreed that this issue did not require a change to the specification. Though specifying sub-type of translation, e.g. transliteration in this case, at the requirements stage there was no uptake by implementors in addressing these requirements, see;http://lists.w3.org/Archives/Public/public-multilingualweb-lt-comments/2013Jan/0181.html |
| issue-85: NLP Interchange Format (NIF) - 1.0/2.0, Canonical XML, Unicode Normalization Forms | 2013-01-18 | n/a | n/a | n/a | Duplicate of issue-73 |
| issue-86: Comment on ITS 2.0 specification WD, i18n-ISSUE-209: Implementation commitment | 2013-01-18 | accepted | satisfied (mail) | substantive | the i18n WG provided a re-write of the directionality section, and that includes this comment. |
| issue-87: Comment on ITS 2.0 specification WD, i18n-ISSUE-210: Whitespace in ruby example | 2013-01-18 | accepted | satisfied (mail) | editorial | ruby section was removed, see issue-91. |
| issue-88: Comment on ITS 2.0 specification WD, i18n-ISSUE-211: Quote element in HTML [should be cite, q, or blockquote] | 2013-01-18 | accepted | satisfied (mail) | editorial | we made the example changes |
| issue-89: Comment on ITS 2.0 specification WD, i18n-ISSUE-212: HTML5 in the ITS spec | 2013-01-18 | accepted | satisfied (mail) | editorial | we will provide explanatory material, see action-399 |
| issue-90: Comment on ITS 2.0 specification WD, i18n-ISSUE-214: directionality should be made normative, with informative additions | 2013-01-20 | accepted | satisfied (mail) | substantive | the i18n WG provided a re-write of the directionality section, and that includes this comment. |
| issue-91: Comment on ITS 2.0 specification WD, i18n-ISSUE-215: Parts of Ruby section should be removed | 2013-01-20 | accepted | satisfied (mail) | substantive | following http://lists.w3.org/Archives/Public/public-multilingualweb-lt-comments/2013Apr/0028.htmlwe removed the section completely and wrote an explanation that Ruby might be added later. There is an action I18NWG-ACTION-218 in the i18n WG to get a stable identifier for Ruby in HTML. |
| issue-92: Comment on ITS 2.0 specification WD, i18n-ISSUE-216: Locale filter note | 2013-01-20 | accepted | satisfied (mail) | editorial | only moving text around |
| issue-93: Case-insensitivity mode for predefined tokens undefined; should be ASCII-case-insensitivity | 2013-01-20 | accepted | satisfied (mail) | editorial | just clarification |
| issue-94: Use of XSD number types is inconsistent with numbers in HTML | 2013-01-20 | accepted | satisfied (mail) | editorial | no influence on tests or implementations, only schema |
| issue-95: I18N-ISSUE-217: Missing support for localizable items that are not translatable | 2013-01-20 | rejected | satisfied (mail) | none | this was seen as out of scope for ITS2.0 |
| issue-96: ITS 2.0 requirements w.r.t Indian [Indic] languages | 2013-01-20 | n/a | n/a | n/a | Duplicate of ISSUE-84 |
| issue-97: Comment on ITS 2.0 specification WD - HTML translate | 2013-01-20 | accepted | satisfied (mail) | substantive | for "translate" attribute in HTML5 we now just refer to the HTML5.1 spec. |
| issue-98: Comment on ITS 2.0 specification WD, i18n-ISSUE-238: Selecting attributes using local selection | 2013-01-20 | accepted | satisfied (mail) | editorial | edit needed, see action-483. We will add a clarifying note that this is not possible with local selection |
| issue-99: I18N-ISSUE-239: Selecting attributes using Selectors | 2013-01-20 | accepted | satisfied (mail) | editorial | we added a clarifying note that with CSS selectors one cannot select attributes. |
| issue-100: I18N-ISSUE-240: Bad example: Hard-coded coordinates [ITS-20] | 2013-01-20 | accepted | satisfied (mail) | editorial | only example fix |
| issue-101: I18N-ISSUE-241: Directionality section doesn't mention isolates [ITS-20] | 2013-01-20 | accepted | satisfied (mail) | editorial | the i18n WG provided a re-write of the directionality section, and that includes this comment. |
| issue-102: I18N-ISSUE-242: Clarify case-insensitive match for domains [ITS-20] | 2013-01-20 | accepted | satisfied (mail) | editorial | borderline substantive |
| issue-103: I18N-ISSUE-243: Clarify filtering algorithm for locale filters [ITS-20] | 2013-01-20 | accepted | satisfied (mail) | editorial | stated that we use extended filtering defined in BCP47, as suggested |
| issue-104: I18N-ISSUE-244: Require recent version of Unicode [ITS-20] | 2013-01-20 | accepted | satisfied (mail) | editorial | no respone from reviewer, but we implemented the change request and it was minor anyway. |
| issue-105: I18N-ISSUE-245: Consider replacing Unicode block escapes with script escapes [ITS-20] | 2013-01-20 | rejected | satisfied (mail) | none | comment is not releveant since the group decided to drop the dependancy on XML Schema for the regex, so there will be no Unicode block escapes anymore. See also issue-67 |
| issue-106: I18N-ISSUE-246: Clarify character encoding behavior when calculating storage size [ITS-20] | 2013-01-20 | rejected | satisfied (mail) | editorial | Editorial ACTION-478 pending on Yves. Clarifications on why bytes are used as the only unit. |
| issue-107: I18N-ISSUE-247: Clarify interpretation of line breaks when calculating storage size [ITS-20] | 2013-01-20 | accepted | satisfied (mail) | editorial | Editorial ACTION-477 pending on Jirka. Proposed edits described in this email:http://lists.w3.org/Archives/Public/public-multilingualweb-lt/2013Mar/0211.html |
| issue-108: locNote ITS 2.0 requirements w.r.t Indian [Indic] languages | 2013-01-21 | rejected | satisfied (mail) | none | Concensus Prague f2f meeting was that: a) this was a new use cases and it was unclear how much demand there was for this; b) it could anyway be handled to some extent either by encoding within the locNote text value or an external format, specifically NIF. See:http://lists.w3.org/Archives/Public/public-multilingualweb-lt-comments/2013Jan/0171.html |
| issue-109: disambiguation ITS 2.0 requirements w.r.t Indian [Indic] languages | 2013-01-21 | rejected | satisfied (mail) | none | see http://www.w3.org/mid/5105CA71.5060909%2540cs.tcd.ie |
| issue-110: change to langRule: precedence of xml:lang and lang | 2013-01-23 | rejected | satisfied (mail) | editorial | a clarifying note was added to the section "Using ITS markup in XHTML" |
| issue-111: Delete requirement not needed in locale filter | 2013-01-23 | accepted | satisfied (mail) | editorial | removed the requirement, didn't have any influence on other parts of the spec or implementations. |
| issue-112: changing MUST statements in localization quality issue type table | 2013-01-23 | accepted | satisfied (mail) | editorial | the MUST statements expressed not testable asserations; no influence on spec or implementations to have them removed. |
| issue-113: Various comments on ITS2 spec | 2013-01-24 | accepted | satisfied (mail) | editorial | Many editiorial changes all over the spec see this diff for details http://fabday.fh-potsdam.de/~sasaki/temp/edits-issue-113.html, refernced from http://lists.w3.org/Archives/Public/public-multilingualweb-lt/2013Mar/0200.html |
| issue-114: Typo fix in section 5.8 | 2013-01-24 | accepted | satisfied | editorial | wording fixes. |
| issue-115: SHOULD and SHOULD NOT + examples in sec. "Using ITS Markup in XHTML" need to be changed | 2013-01-31 | accepted | satisfied (mail) | editorial | We clarified how XHTML documents should be processed. No influence on testing or any normative aspects of the spec. |
| issue-116: space normalization in ITS loc note | 2013-02-11 | rejected | satisfied (mail) | none | the comment is not releveant for the spec, rather a detail for the test suite. |
| issue-117: Issues in Note in 2.1.2 | 2013-02-11 | accepted | satisfied (mail) | editorial | Editorial action ACTION-475 pending. The note was dropped, hence example rework became irrelevant. |
| issue-118: HTML ITS default behaviour | 2013-02-22 | accepted | satisfied (mail) | substantive | we added defaults for elements within text. The defaults point to the HTML5 CR definition of phrasing contenthttp://www.w3.org/TR/2012/CR-html5-20121217/dom.html#phrasing-content-1 |
| issue-121: add a negation flag to locale filter | 2013-02-28 | accepted | satisfied (mail) | editorial | Reintroducing the type attribute to be able to exclude locales. Borderline substantive..See http://lists.w3.org/Archives/Public/public-multilingualweb-lt/2013Mar/0144.html |
| issue-122: Need of ITS version information at standff (provenance or loc quality issue) | 2013-03-21 | accepted | satisfied (mail) | editorial | the version attribute has been defined as possible in the standoff definitions, see sec. "5.1 Indicating the Version of ITS" for details |
| issue-123: provenance in HTML5 needed globally? | 2013-03-22 | accepted | satisfied (mail) | editorial | the restriction to not have provenance globally in HTML was was removed. |
| issue-124: Localization Quality Issue Types use RFC2119 values improperly | 2013-03-28 | accepted | satisfied (mail) | editorial | This is connected to the broader editorial issue. Lower case normative keywords should be reformulated in non-normative style throughout the spec, as suggested by Addison. |