• To: xml-dev@l...
• Subject: Re: Defining non-WXS datatypes
• From: james anderson <james.anderson@s...>
• Date: Fri, 01 Aug 2003 10:06:36 +0200
• Organization: nil
• References: <830178CE7378FC40BC6F1DDADCFDD1D1322C39@R...><126945138006.20030718095448@j...> <87adaudelg.fsf@n...> <030901c357c7$bb6dceb0$1401a8c0@snobird> <3F29C58C.2ED10BBE@s...> <048001c357f0$717386f0$1401a8c0@snobird>
• Reply-to: james.anderson@s...

Bob Foster wrote:
> 
> From: "james anderson" <james.anderson@s...>
> ...
> > > I think Jeni is talking about a datatype library that defines an
> internal,
> > > canonical representation of QNames used for validation. Forming the
> > > representation requires document context.
> >
> > That does not follow from her text.
> 
> True. She might have meant the other. But in that case, they wouldn't be
> QNames.
> 
yes, no referentially transparent expression for an instance of the
(namespace-name X local-part) relation is a QName. by definition. that's one
of the things which makes these discussions so confounding.

...

• References:
  • Re: Defining non-WXS datatypes
    • From: "Bob Foster" <bob@o...>

• Prev by Date: XSL transformation clientside errors
• Next by Date: Re: reaching humans (was Re: Extract A Subset of a W3C XML Schema?)
• Previous by thread: Re: Defining non-WXS datatypes
• Next by thread: Re: reaching humans (was Re: Extract A Subset of a W3C XML Schema?)
• Index(es):
  • Date
  • Thread