Last update: 2006-10-20.
No issue in this category available.
No issue in this category available.
No issue in this category available.
| Description | id | status | Last modified |
|---|---|---|---|
| Attaching information to the object associated to a selected node | 3126 | Summary: The Working Group decided to postpone this issue. | 2006-09-27 |
| Description | id | status | Last modified |
|---|---|---|---|
| Introduction too "positive" and not enough informative :) | 3290 | Summary: The Working Group agreed with the proposal and clarified the introduction. | 2006-09-27 |
| XHTML Module for XHTML 1.1 or XHTML 2.0 | 3292 | Summary: The comment does not apply any more since the Working Group handles the topic now in a different document. | 2006-09-27 |
| Conformance/Compliance | 3293 | Summary: The Working Group made the correction. | 2006-09-27 |
| Linking of versions of textual segments via "localization information" data category | 3317 | Summary: The Working Group declined to change the specification. In addition, the name of the data category was changed to "localization note", to clarify its intention. See also issue http://www.w3.org/Bugs/Public/show_bug.cgi?id=3460 . | 2006-09-27 |
| Clarify "within text" data category | 3318 | Summary: This bug has been marked as a duplicate of bug 3495. | 2006-09-28 |
| Using IDs for nodes instead of / in addition to XPath | 3320 | Hi, The resolution of the Working Group is fine for me. Regards, Werner. | 2006-10-03 |
| Relation of terminology data category to existing standards for terminology | 3321 | Summary: The Working Group agreed to accept the proposal and clarified the relation of the "Terminology" data category to existing standards. | 2006-09-27 |
| Version of XPath: Write "XPath 1.0 or its successor" | 3323 | Summary: The Working Group accepts the proposal and changes the reference to "XPath 1.0 or its successor". | 2006-09-28 |
| lro and rlo explanation | 3330 | Summary: The Working Group clarified the explanation of the "lro" and "rlo" values. | 2006-10-03 |
| Please use XHTML Modularization for defining ITS DTD and Schema | 3331 | Closed. Reviewer satisfied, see http://lists.w3.org/Archives/Public/public-i18n-its/2006OctDec/0010.html . | 2006-10-13 |
| Following the inheritance of the rules can be difficult | 3360 | Closed. Commentor satisfied. | 2006-10-10 |
| No defined behavior if external rules can't be accessed | 3361 | We can accept the response. However, I feel that this will lead to numerous different implementations and the market may respond to this by trying to lock users in to use a certain implementation or another. | 2006-10-14 |
| Attribute used for locInfo | 3456 | Summary: The Working Group decided to accept the proposal and added an explanation for the attribute used for locInfo (now called "locNote", see comment http://www.w3.org/Bugs/Public/show_bug.cgi?id=3460 ). | 2006-09-27 |
| RFC 3066bis | 3457 | Summary: The Working Group decided to accept the proposal and to change the reference for language identification. | 2006-09-27 |
| Default translate value | 3458 | Summary: The Working Group has accepted the comment and added an explanation of the default values. | 2006-09-28 |
| Use of elements | 3459 | Summary: The Working Group has accepted the proposal and clarified the model of the locInfo element (now called "locNote", see comment http://www.w3.org/Bugs/Public/show_bug.cgi?id=3460 ) as desired. | 2006-09-28 |
| Loc Info or Loc Note | 3460 | Summary: The Working Group has accepted the proposal and changed the name of the data category from "localization information" to "localization note", and the element and attribute names respectively. | 2006-09-28 |
| Role of termInfo | 3461 | Summary: The Working Group agreed with the proposal and clarified the role of the terminology data category. | 2006-09-28 |
| Pointing to terms | 3462 | Summary: The Working Group agreed to accept the proposal and clarified the role of mechanisms for pointing to terms. | 2006-09-28 |
| termInfoRef should allow for id strings | 3463 | Summary: The Working Group agreed to accept to proposal and decided to apply the ITS pointing mechanisms also for terminology information, that is, to introduce a termInfoPointer attribute. | 2006-09-28 |
| Allowing for xpath expressions to point to term definitions | 3464 | Summary: The Working Group decided to accept the proposal and introduced a termInfoPointer attribute. See also the resolution for issue 3463. | 2006-09-28 |
| Default is ltr | 3465 | Summary: The Working Group accepted the proposal and added an explanation of the default for the directionality data category. | 2006-09-28 |
| Existing ruby markup | 3466 | Summary: The Working Group decided to accept the proposal and to clarify the relation of the specification to the W3C ruby specification, directionality as defined in CSS 2.1, and the usage of IRIs. | 2006-10-13 |
| rubyText is an attribute | 3467 | Summary: The Working Group decided to accept the proposal and to have rubyText as an element. | 2006-09-28 |
| xml:lang missing | 3468 | Summary: The Working Group decided to accept the proposal and to clarify that xml:lang is available in the non-normative ITS schemas at the desired elements. | 2006-09-28 |
| Example 19 xml:lang | 3469 | Summary: The Working Group decided to accept the proposal and to clarify the role of xml:lang for the "language information" data category. | 2006-09-28 |
| Language information data category overview I18NCORE c1 | 3473 | Summary: The Working Group decided to accept the proposal and to clarify the role of the langRule element. | 2006-09-28 |
| Example 33 | 3479 | Summary: The Working Group decided to accept the proposal and to modify example 33. | 2006-09-28 |
| Use of xml:lang | 3480 | Summary: The Working Group decided to accept the proposal and to clarify the role of xml:lang for the "language information" data category. | 2006-09-28 |
| Translatability | 3481 | Summary: The Working Group decided to accept the proposal and to change the name of the data category "translation information" to "Translate". | 2006-09-28 |
| Inheritance of translation information | 3482 | Summary: The Working Group decided to accept the proposal and to make the role of inheritance of translation information within global rules more explicit. | 2006-09-28 |
| Invert translate examples | 3487 | Summary: The Working Group decided to accept the proposal and to modify the examples as desired. | 2006-09-28 |
| 6.3 ed 1 | 3488 | Summary: The Working Group decided to accept the proposal and to make the wording change as desired. | 2006-09-28 |
| Mention translation tools | 3489 | Summary: The Working Group decided to accept the proposal and to mention translation tools in the desired section. | 2006-09-28 |
| Examples 22 and 23 | 3490 | Summary: The Working Group decided to accept the proposal and to improve the examples. | 2006-09-28 |
| Explanations for examples | 3491 | Summary: The Working Group decided to accept the proposal and to add explanations to the examples. | 2006-09-28 |
| Example 24 | 3492 | Summary: The Working Group decided to accept the proposal and to change the example as desired. | 2006-09-28 |
| Marks terms and meanings | 3493 | Summary: The Working Group decided to accept the proposal and to clarify the purpose of the terminology data category. | 2006-09-28 |
| termInfoRefPointer referant's data | 3494 | Summary: The Working Group decided to accept the proposal and to clarify the explanation of the termInfoRefPointer attribute. | 2006-09-28 |
| Hard to know what this is about | 3495 | Summary: The Working Group decided to accept the proposal and clarified the description of the "elements within text" data category. | 2006-09-28 |
| Standardised wording | 3496 | Summary: The Working Group decided to accept the proposal and to use more standardized wordings for the description of the various data categories. | 2006-09-28 |
| No implementation section | 3497 | Summary: The Working Group decided to accept the proposal and to add an implementation section for the "language information" data category. | 2006-09-28 |
| Repetition | 3498 | Summary: The Working Group decided to accept the proposal and to drop the sentence as desired. | 2006-09-28 |
| Is dir mandatory? | 3499 | Summary: The Working Group decided to accept the proposal and to make explicit that the dir attribute is mandatory at dirRule elements. | 2006-09-28 |
| Avoid xml:lang='he' | 3500 | Summary: The Working Group decided to accept the proposal and to change the example as desired. | 2006-09-28 |
| Some Hebrew quotation | 3501 | Summary: The Working Group decided to accept the proposal and to change the wording as desired. | 2006-09-28 |
| Example 30 | 3502 | Summary: The Working Group decided to accept the proposal and to modify the example. | 2006-09-28 |
| Refer to bidi article | 3503 | Summary: The Working Group decided to accept the proposal and to add a reference to the article as desired. | 2006-09-28 |
| Example 31 lacks rp | 3504 | Summary: The Working Group decided to accept the proposal and to add rp to the example. | 2006-09-28 |
| Use Japanese in Example 31 | 3505 | Summary: The Working Group decided to accept the proposal and to use Japanese in the example. | 2006-09-28 |
| Make the application of legacy ruby clearer | 3506 | Summary: The Working Group decided to accept the proposal and to clarify the application of legacy ruby. | 2006-09-28 |
| in the case of no selection | 3507 | Summary: The Working Group removed the sentence part which had led to confusion. | 2006-09-28 |
| Example 32 head | 3508 | Summary: The Working Group decided to accept the proposal and to fix the example as desired. | 2006-09-28 |
| Too many places to look | 3509 | Summary: The Working Group decided to accept the proposal and to create a more consistent description of data categories (see also issue http://www.w3.org/Bugs/Public/show_bug.cgi?id=3496 ). | 2006-09-28 |
| Spell out the attributes | 3510 | Summary: The Working Group decided to accept the proposal and to list explicitely the "pointer" attributes as desired. | 2006-09-28 |
| Example 14 translate | 3511 | Summary: The Working Group decided to accept the proposal and changed the example as desired. | 2006-09-28 |
| Example 14 dir | 3512 | Summary: The Working Group decided to accept the proposal and to change the example as desired. | 2006-09-28 |
| ITS markup must be integrated | 3513 | Summary: The Working Group clarified the specification to make the optionality of ITS markup in the targeted XML file(s) explicit. | 2006-09-28 |
| Attributes missing? | 3514 | Summary: The Working Group agreed to make the change and to spell out the attributes which can appear locally. | 2006-10-20 |
| xml:lang = language info, please | 3515 | Summary: The Working Group decided to accept the proposal and to clarify the role of xml:lang. | 2006-09-28 |
| Editorial comments on ITS from i18n core | 3516 | Summary: The Working Group decided to accept the editorial comments and to implement many of them in the working draft, until the reviewer is satisfied. | 2006-09-28 |
| Missing term="yes|no" in termRule element | 3612 | Summary: The Working Group decided to accept the proposal and to add the term attribute as desired. | 2006-09-28 |
| Need to handle inheritance for terminology | 3640 | Summary: The Working Group decided to accept the proposal and to add a more explicit description of the inheritance / default / overriding behavior of the data categories. | 2006-10-01 |
| Both selector and the rbPointer attributes are base text in rubyRule | 3803 | Summary: The Working Group agreed that the functionality of the two attributes is identical and decided to remove the rbPointer attribute. | 2006-10-06 |
| Description | id | status | Last modified |
|---|---|---|---|
| Namespace binding mechanism | 3319 | Summary: The Working Group decided not to change the namespace binding mechanism, because we want ITS global rules to be independent of existing (and possibly changing) namespace declarations. | 2006-09-28 |