W3C home > Mailing lists > Public > ietf-dav-versioning@w3.org > April to June 2001

RE: Mention nested baselines in 15

From: Clemm, Geoff <gclemm@rational.com>
Date: Tue, 17 Apr 2001 23:35:23 -0400
Message-ID: <3906C56A7BD1F54593344C05BD1374B102B8FFA1@SUS-MA1IT01>
To: ietf-dav-versioning@w3.org
   From: Edgar@EdgarSchwarz.de [mailto:Edgar@EdgarSchwarz.de]

   So it remains (probably you already know that yourself) that the
   beginning of 'Baseline feature' needs some rewording. Especially
   the the first sentence and the stuff on components which seems to
   imply that you have to move it out of the baseline scope to create
   a subbaseline.

Good point!  (I did realize that the subbaseline stuff needed to
be reworded, but I didn't notice that the first sentence also needs
to be changed ... thanks for pointing that out!).

   BTW, I agree with your roadmap for 15. That also means that I can
   accept a language attribute for labels. But please NO additional
   comparison rules if we can avoid it.

Agreed.  The language attributes are there for display purposes,
but do not affect the matching (which is simple UTF-8 byte comparison).

   I already shudder when I
   think about the question whether two strings which are identical
   but have nominally a different encoding (UTF8 or ASCII7) match.  So
   would it be possible to say a label must be in UTF8 and optionally
   a language attribute is allowed ?

We do require that the label be in UTF-8 when it appears in a
header.  We don't require UTF-8 in the XML, because we want to
just use standard XML language encoding rules (which among other
things, allows a language attribute).  But the transformation
between other Unicode encodings and UTF-8 are well defined.

Cheers,
Geoff
Received on Tuesday, 17 April 2001 23:34:56 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 13:57:41 GMT