[
Lists Home |
Date Index |
Thread Index
]
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
/ 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.
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
({ 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@Sun.COM | 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-----
|
