This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Issue #45 of i18nCore comments http://www.w3.org/International/reviews/0606-its/ "Some markup schemes provide markup which can be used to express ITS data categories. ITS data categories can be associated with such existing markup, using the global selection mechanism described in Section 5.3.1: Global, Rule-based Selection. In this way, there is no need to integrate ITS markup into documents." The last sentence is completely incorrect as it stands. It should say that there is not need to integrate *local* ITS markup into those documents. The markup to support ITS global rules is very much needed! FS: Please have a look at http://www.w3.org/TR/its/#selection-precedence , list point no. 3: [Global selections in an external file (using a rules element), linked via the XLink href attribute or a different mechanism] That is: you *can* use different mechanisms than an <its:rules> element with an XLink href attribute, e.g. an external rules file. It depends on your implementation how the rules are activated, e.g. via a command line option. In other words: "In this way, there is no need to integrate ITS markup into documents." My current implementation in XSLT allows for such an (command line) option, and I'm sure it is no problem to have it for Yves' and Sebastian's implementation or others as well. However, it does not make sense to standardize this option, since it is implementation dependend. I18n: Wherever the global rules are they are integrated 'into documents', so we assume that what you meant to say was perhaps "If global rules are defined in an external rules file, there is no need to integrate ITS markup into the document." If, however, you are referring specifically to rules activated via command line options, as mentioned above, and given that you say that it doesn't make sense to standardize this option, then I'm wondering why you would mention it in this way. At best a note with a caution would be appropriate. Please provide clarification.
Action: working group to discuss and reply.
Discussed at http://www.w3.org/2006/07/26-i18nits-minutes.html#item14 Action: Yves to write a paragraph about associating external rules with files.
Here is my proposal Current wording: "Some markup schemes provide markup which can be used to express ITS data categories. ITS data categories can be associated with such existing markup, using the global selection mechanism described in Section 5.3.1: Global, Rule-based Selection. In this way, there is no need to integrate ITS markup into documents." New wording proposition: Delete the sentence "In this way, there is no need to integrate ITS markup into documents." from the current paragraph. And add a following paragraph after Example 19: ----- Global rules can be associated with a given XML document using different means: * By using an its:rules element in the document itself (as shown in Example 19). * By linking the document to an external rules file using the xlink:href attribute of the its:rules element (as shown in Example 16) - By associating the rules and the document through a tool-specific mechanism. For example, for a command-line tool: providing the paths of both the XML document to process and its corresponding external rules file." -----
From the discussion here: http://www.w3.org/2006/08/09-i18nits-minutes.html#item01 I have an action item to slightly modify the text (bullet grouping). New proposal: Delete the sentence "In this way, there is no need to integrate ITS markup into documents." from the current paragraph. And add a following paragraph after Example 19: ----- Global rules can be associated with a given XML document using different means: * By using an its:rules element in the document itself: * with the rules directly inside the document, as shown in Example 19. * with a link to an external rules file using the xlink:href attribute, as shown in Example 16 * By associating the rules and the document through a tool-specific mechanism. For example, for a command-line tool: providing the paths of both the XML document to process and its corresponding external rules file." -----
Resolution: working group agreed with the proposal at http://www.w3.org/2006/08/16-i18nits-minutes.html. Action: editors to make the change.
Comment has been implemented
Action: Felix to do implement the change
Wait: response sent. See http://lists.w3.org/Archives/Public/public-i18n-its/2006JulSep/0337.html
Closed. Commenters satisfied see: http://lists.w3.org/Archives/Public/public-i18n-its/2006JulSep/0362.html
Summary: The Working Group clarified the specification to make the optionality of ITS markup in the targeted XML file(s) explicit.