- From: Richard Ishida <ishida@w3.org>
- Date: Tue, 21 Mar 2006 11:09:19 -0000
- To: "'Yves Savourel'" <yves@opentag.com>, <public-i18n-its@w3.org>
- Message-ID: <00c001c64cd7$e6d53590$6501a8c0@w3cishida>
I would also prefer to remove the locInfoType attribute, but there is a third solution that i prefer. In addition to the locInfo data category have a locAlert data category. I think relying on people to add text to a note to distinguish these two types of localization note will lead to problems - not least if the notes are written in another language (such as Russian). I also think we need to be careful about changing the requirements to fit implementation snags. RI ============ Richard Ishida Internationalization Lead W3C (World Wide Web Consortium) http://www.w3.org/People/Ishida/ http://www.w3.org/International/ http://people.w3.org/rishida/blog/ http://www.flickr.com/photos/ishida/ _____ From: public-i18n-its-request@w3.org [mailto:public-i18n-its-request@w3.org] On Behalf Of Yves Savourel Sent: 16 March 2006 06:13 To: public-i18n-its@w3.org Subject: Issue of locInfoType - To keep or not Hi all, There is an item listed in the Mandelieu proposals that I'd like to dispose of at the next teleconference. It's not a crucial one but it affect the markup itself, so we need to address it. We have currently an optional attribute locInfoType with the values "alert|description" (and no default set for now). The question is shall we keep it or not? Advantages to keep it: - Allows to make a distinction between different types of loc info. Drawbacks: - make things a bit more verbose, and add more things to do at the implementation. - we would need to decide where it fits in the conformance (any specific processing expectation) - if we keep it we need to have a default value for it (alert or description?) My comments: Overall I don't see much benefits into having it. From an implementation viewpoint (at least from my prospective) this will translate into a note that will have a 'ALERT' word in front of the note, or nothing. That's it. If we keep it I think the default value should be 'description'. I would be for removing @locInfoType simply because it doesn't seem to bring much and that would make ITS a tad lighter. But it's not at all a strong opinion and I'll go with the pack on this one. Cheers, -yves
Received on Tuesday, 21 March 2006 11:09:23 UTC