RE: Property stability policy considered harmful

From: Phillips, Addison (
Date: Wed Jul 08 2009 - 23:28:04 CDT

  • Next message: verdy_p: "RE: Property stability policy considered harmful"

    What the policy guarantees is that implementations that rely on a particular property name or value being valid will not suddenly find that they specify values that are not legal property names or property values. A negative counter-example prompting this policy was the change of the script value 'Greek' to 'Greek_and_Coptic".

    This is an important guarantee, independent of whether a given property name or property value is currently in use or which set of code points (including the empty set) is assigned particular name-value pairings. Certainly implementations of UTS#18 (regular expressions) rely on it, as do such things as XML Schema 1.1.

    You are right that implementations may still struggle with formerly useful property names or values now being essentially useless. But your code will still work according to the current expectations of the current version of Unicode. Other stability policies might be worth examining, but they are orthogonal to whether names or values can be respelled at a later date.


    Addison Phillips
    Globalization Architect -- Lab126
    Chair -- W3C Internationalization WG

    Internationalization is not a feature.
    It is an architecture.

    > -----Original Message-----
    > From: []
    > On Behalf Of karl williamson
    > Sent: Wednesday, July 08, 2009 4:02 PM
    > To:
    > Subject: Property stability policy considered harmful
    > It appears to me that the stability guarantees that a property and
    > property value alias will never be removed are worse than not
    > having
    > them. And the reason is that all code points they contain can
    > simply be
    > moved to another property (or property value) without violating the
    > letter of the policy. This has happened with
    > Script=Katakana_Or_Hiragana whose contents were all moved to Common
    > in
    > 4.1, and it appears to be happening in 5.2 with ISO_Comment. If I
    > have
    > a program that is looking for a property that has become empty, I
    > would
    > rather know about it at compilation time rather than to have it go
    > along
    > and give wrong answers (perhaps subtly so).

    This archive was generated by hypermail 2.1.5 : Wed Jul 08 2009 - 23:31:59 CDT