[Home] [By Thread] [By Date] [Recent Entries]

  • To: <james.anderson@s...>,<xml-dev@l...>
  • Subject: Re: Defining non-WXS datatypes
  • From: "Bob Foster" <bob@o...>
  • Date: Fri, 1 Aug 2003 00:47:45 -0500
  • References: <830178CE7378FC40BC6F1DDADCFDD1D1322C39@R...><126945138006.20030718095448@j...> <87adaudelg.fsf@n...> <030901c357c7$bb6dceb0$1401a8c0@snobird> <3F29C58C.2ED10BBE@s...>

From: "james anderson" <james.anderson@s...>
> Bob Foster wrote:
> >
> > > / Jeni Tennison <jeni@j...> was heard to say:
> > > | on the context in which it's going to be used. Perhaps a new
datatype
> > > | library can define QNames in a different way, one that includes a
> > > | normalized version that's a legal representation (e.g. {uri}name).
> > >
> > > The problem with a lexical form for QNames is that you want them to be
> > > recognized in content, which means you need to start them with a
> > > markup character, which is a can of worms no matter how you look at
> > > it.
> >
> > 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.

Bob Foster


Site Map | Privacy Policy | Terms of Use | Trademarks
Free Stylus Studio XML Training:
W3C Member