W3C home > Mailing lists > Public > www-international@w3.org > January to March 2006

Re: Regular expressions should support \x{....} escapes

From: Bjoern Hoehrmann <derhoermi@gmx.net>
Date: Tue, 24 Jan 2006 11:48:26 +0100
To: "Michael Kay" <mhk@mhk.me.uk>
Cc: <public-qt-comments@w3.org>, <www-international@w3.org>, <www-xml-schema-comments@w3.org>
Message-ID: <u91ct1hkmjo5h51nluthq9u2aa9nla8ggs@hive.bjoern.hoehrmann.de>

* Michael Kay wrote:
>> http://www.w3.org/TR/charmod/#C073 has "Publicly interchanged content
>> SHOULD NOT use codepoints in the private use area." Reference to and
>> use of are equivalent concepts here. You might well argue that SHOULD
>> NOT is not MUST NOT, conformance checkers are nevertheless going to
>> point out violations of the SHOULD NOT requirement 
>
>I fail to see how a conformance checker is supposed to know whether the
>content is being publicly interchanged. I would think that most conformance
>checkers are likely to give the user the benefit of the doubt, or at least
>to provide options.

I'd assume it'd look like

  WARNING: Publicly interchanged content SHOULD NOT
           use codepoints in the private use area.

Educated users can then decide to ignore this.
-- 
Björn Höhrmann · mailto:bjoern@hoehrmann.de · http://bjoern.hoehrmann.de
Weinh. Str. 22 · Telefon: +49(0)621/4309674 · http://www.bjoernsworld.de
68309 Mannheim · PGP Pub. KeyID: 0xA4357E78 · http://www.websitedev.de/ 
Received on Tuesday, 24 January 2006 10:47:48 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 2 June 2009 19:17:06 GMT