W3C home > Mailing lists > Public > www-tag@w3.org > October 2002

Re: IRIs everywhere (including XML namespaces)

From: Chris Lilley <chris@w3.org>
Date: Wed, 30 Oct 2002 23:28:25 +0100
Message-ID: <8610579828.20021030232825@w3.org>
To: "Biron,Paul V" <Paul.V.Biron@kp.org>
CC: www-tag@w3.org, Julian Reschke <julian.reschke@gmx.de>

On Wednesday, October 30, 2002, 10:57:42 PM, Paul wrote:

>> From: Chris Lilley [SMTP:chris@w3.org]

>> Of course, if XML Schema allowed a choice of list delimiters instead
>> of just space (commas, semicolons, etc) then unescaped spaces would be
>> ok because you could use some character that was not in that
>> particular IRI to delimit the list (same as the " ' " and ' " '
>> technique for attribute values).
>> 
BPV> If only...that's a very common request, but unfortunately, the
BPV> schema WG has declined the requests (most recently at our f2f a
BPV> few weeks OK as part of requirements discussion for v1.1) as a
BPV> "slippery slope".

The optimum ground between full expressivity and over restriction is
usually a slippery slope. As the Duke of Wellington said, all battles
are fought on the side of a hill in the pouring rain at the place
where two maps join.

BPV>  FYI, even if we had user-specifiable list
BPV> delimeters, they would most likely not be settable in an instance
BPV> but rather at schema (type definition) time...hence, you'd have
BPV> to pick a delimiter that was not legal in any IRI...

Doh. Good point, I should have thought of that. I was imagining some
sort of xsi:type in the instance together with more extensible types
but you are right, that would not do.

BPV> are there any such characters?

Not that I am aware of.


-- 
 Chris                            mailto:chris@w3.org
Received on Wednesday, 30 October 2002 17:28:29 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:32:34 UTC