[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

Re: Defining non-WXS datatypes

• To: <xml-dev@l...>,"Norman Walsh" <ndw@n...>
• Subject: Re: Defining non-WXS datatypes
• From: "Bob Foster" <bob@o...>
• Date: Thu, 31 Jul 2003 19:56:22 -0500
• References: <830178CE7378FC40BC6F1DDADCFDD1D1322C39@R...><126945138006.20030718095448@j...> <87adaudelg.fsf@n...>

> / 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.

Bob Foster

>
> Defining the markup character on a per-vocabulary basis could be done.
> Just as XSLT says that curly braces mean something special in (many)
> attribute values, a language could say that "{" always introduces a
> QName and therefore "{uri}name" is always equivalent to "x:name" where
> x is bound to uri. Unfortunately, as soon as you start mixing
> namespaces, you'd have to have rules for when its a markup character
> and when it isn't. And you'd have to have some escaping mechanism
> (&#x7b; won't cut it) for a literal "{". And it would all be very
> confusing.
>
> Defining the markup character on a global could be done...in YML. :-)
>
>                                         Be seeing you,
>                                           norm

• Follow-Ups:
  • Re: Defining non-WXS datatypes
    • From: james anderson <james.anderson@s...>

• References:
  • RE: Defining non-WXS datatypes
    • From: "Dare Obasanjo" <dareo@m...>
  • Re: Defining non-WXS datatypes
    • From: Jeni Tennison <jeni@j...>
  • Re: Defining non-WXS datatypes
    • From: Norman Walsh <ndw@n...>

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