OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

 


 

   Re: [xml-dev] Defining non-WXS datatypes

[ Lists Home | Date Index | Thread Index ]
  • To: <james.anderson@setf.de>,<xml-dev@lists.xml.org>
  • Subject: Re: [xml-dev] Defining non-WXS datatypes
  • From: "Bob Foster" <bob@objfac.com>
  • Date: Fri, 1 Aug 2003 00:47:45 -0500
  • References: <830178CE7378FC40BC6F1DDADCFDD1D1322C39@RED-MSG-31.redmond.corp.microsoft.com><126945138006.20030718095448@jenitennison.com> <87adaudelg.fsf@nwalsh.com> <030901c357c7$bb6dceb0$1401a8c0@snobird> <3F29C58C.2ED10BBE@setf.de>

From: "james anderson" <james.anderson@setf.de>
> Bob Foster wrote:
> >
> > > / Jeni Tennison <jeni@jenitennison.com> 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





 

News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 2001 XML.org. This site is hosted by OASIS