[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...
• Subject: Re: Defining non-WXS datatypes
• From: Norman Walsh <ndw@n...>
• Date: Thu, 31 Jul 2003 09:12:59 -0400
• In-reply-to: <126945138006.20030718095448@j...> (Jeni Tennison'smessage of "Fri, 18 Jul 2003 09:54:48 +0100")
• References: <830178CE7378FC40BC6F1DDADCFDD1D1322C39@R...><126945138006.20030718095448@j...>
• User-agent: Gnus/5.1001 (Gnus v5.10.1) Emacs/21.3 (gnu/linux)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

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

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

- -- 
Norman.Walsh@S...    | We have fewer friends than we imagine, but
XML Standards Architect | more than we know.--Hugo Von Hofmannsthal
Web Tech. and Standards |
Sun Microsystems, Inc.  | 
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)
Comment: Processed by Mailcrypt 3.5.7 <http://mailcrypt.sourceforge.net/>

iD8DBQE/KRXbOyltUcwYWjsRApWMAJ9kdGz74qIMyXcP/vEZVJ05Wizn2wCdHrWR
7jMCUgRTY1Ne/kd4dIDqPlc=
=gcbg
-----END PGP SIGNATURE-----

• Follow-Ups:
  • Re: Defining non-WXS datatypes
    • From: "Bob Foster" <bob@o...>
  • Re: Defining non-WXS datatypes
    • From: Eric van der Vlist <vdv@d...>

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

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