This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
ITS says [[[ This document defines a standard for high-quality, cost efficient internationalization and localization of schemas and XML instances (both existing ones and new ones). ]]] We understand that it is the desires of the group but it doesn't mean that it will be true. (We wish it will be). Just define what is it but do not emphasize on the foreseen qualities ;) Same comment than the abstract as well. Tend to avoid "This document", "The document", just write about the topic, it will be lighter to read. Again remove the reference to feedback, this is the status section not part of the introduction which is about the technology itself. Reading the first paragraph of Introduction, I still don't know what is it used for. Is there a possibility of writing in one or two sentences what is it used for in general use case? It is explained in 1.1 but could you make it one sentence in the first paragraph that will be then developed further in 1.1 Example: "The ITS specification aims to provide different types of users with information about what markup should be supported to enable worldwide use and effective localization of content. " Is very informatique and should be in the abstract and/or Introduction. nitpicking: use "" and not "..."
Proposal for a resolution at http://lists.w3.org/Archives/Member/member-i18n-its/2006JulSep/0068.html . Action: working group to discuss the proposal.
Discussed at http://www.w3.org/2006/07/24-i18nits-minutes.html#item03 . The working group approved the proposal at http://lists.w3.org/Archives/Member/member-i18n-its/2006JulSep/0068.html (with one change: have no citation of [Yves]). Karl, would you be o.k. with the proposal? If we don't hear from you within two weeks, we regard the proposal as closed. Felix Wait: answer sent, wait respone.
In the new proposal there is: "The ITS Working Group (ITS WG) has created a standard which makes it easier to create XML which is internationalized and can be localized effectively. On the one hand, the ITS WG identifies concepts (such as "directionality") which are important for i18n and l10n. On the other hand, the ITS WG defines implementations of these concepts (termed "ITS data categories") as a set of elements and attributes called the Internationalization Tag Set (ITS)." The way we would write this part of the text "ITS is a technology to easily create XML which is internationalized and can be localized effectively. reate XML which is internationalized and can be localized effectively. On the one hand, the ITS specification identifies concepts (such as "directionality") which are important for i18n and l10n. On the other hand, the ITS specification defines implementations of these concepts (termed "ITS data categories") as a set of elements and attributes called the Internationalization Tag Set (ITS)."
I like Karl changes too. But I would change "i18n" and "l10n" to "internationalization" and "localization" (I missed that in Christian text early on). I think those abbriviation are ok in filenames and reference markers, but not in normal text.
Hi Karl and Yves, Thanks for the constructive feedback. Here's what I end up with in my attempt to include both: "ITS is a technology to easily create XML which is internationalized and can be localized effectively. On the one hand, the ITS specification identifies concepts (such as "directionality") which are important for internationalization and localization. On the other hand, the ITS specification defines implementations of these concepts (termed "ITS data categories") as a set of elements and attributes called the Internationalization Tag Set (ITS)." Does this address your concerns? Cheers Christian
Comment has been implemented
Closed. Commentor satisified.
Summary: The Working Group agreed with the proposal and clarified the introduction.