Re: I18N-ISSUE-246: Clarify character encoding behavior when calculating storage size [ITS-20]

* Stephan Walter wrote:
>the point that I still don't fully understand here (admittedly I'm not 
>experienced with W3C specifications and what they pertain to, so maybe 
>I'm just not getting something here...):
>
>As far as I can see we do not require (in the sense of a capital MUST) 
>any specific kind of action or processing to be done based on the 
>'storage size' information. Using the distinction between processor and 
>consumer that Yves explained: A processor does not actually have to do 
>anything with the storage size information that it would need to encode 
>the marked up data for. We just suggest what could be done with it by a 
>consumer (actually checking the constraint), and for that purpose the 
>data would need to be encoded in the given encoding. Of course this way 
>of using 'storage size' information seems to be the most reasonable one, 
>but it is not a MUST.  There might be others that we didn't think of and 
>that don't require the consumer to actually encode the data. So since 
>the intended use of the 'storage size' information is not a MUST, can we 
>really make something a MUST just because it is a prerequisite to this 
>use?

Yes but such requirements would compose with other requirements, so you
may end up with, in effect, conditional requirements like "support for
X is optional but when X is supported then Y must also be supported".
-- 
Björn Höhrmann · mailto:bjoern@hoehrmann.de · http://bjoern.hoehrmann.de
Am Badedeich 7 · Telefon: +49(0)160/4415681 · http://www.bjoernsworld.de
25899 Dagebüll · PGP Pub. KeyID: 0xA4357E78 · http://www.websitedev.de/

Received on Sunday, 3 March 2013 20:50:27 UTC