This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
I suggest a different way to talk about "XML Localization Properties" since to me the existing one might be to abstract: === This standard does does not cover exhaustively cover all mechanisms and data formats which might be needed for configuring XML localization workflows or tools. These mechanisms and data format, sometimes called XML Localization Properties, however, possibly may be implemented by the framework put forth in this standard. In particular, Section 3: Selection of ITS information may provide valuable ideas. === FS> not implemented, since it seems to me that the localization property issue has no common understanding in the group yet.
In order to close this issue we need to make sure everyone is on the same wave length about "XML localization properties". This is one of the discussion topic for this week. My definition of the term "XML localization properties" (I think in accord with Christian's) would be something like: "XML localization properties" is a generic term to name the mechanisms and data formats that allows localization tools to be configured in order to process a specific XML format. Example of "XML localization properties" are: the "Trados DTD Settings" file, the SDLX "Analysis" file. So I would agree with Christian's wording (after removing one 'cover' and one 'does' from the first line).
Resolution: See http://lists.w3.org/Archives/Public/public-i18n-its/2006AprJun/0016.html Christian's text is integrated in the latest draft.
Closed, no further action necessary.
This is a test if the QA contact change worked.