[
Lists Home |
Date Index |
Thread Index
]
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
/ "Simon St.Laurent" <simonstl@simonstl.com> was heard to say:
| It struck me this morning that many of the problems with QNames aren't
| exactly the fault of QNames. QNames are kind of the result of a
| collision between a URI truck and the Name compact car where we end up
| driving the truck from the driver's seat of the car.
|
| The most obvious fault line is the inability to express QNames as URIs.
Yep. TAG issue "rdfmsQnameUriMapping-6".
I don't think there's a good answer. Your description of the current
conventions as "hilarious" is sadly not too far off the mark.
The only clean solution that I can see involves adding a new markup
character to the XML grammar (and is therefor hardly a solution in any
practical sense, alas).
For example, you could define "{" as the start character for a new
QName lexical space defined as a URI, local-name tuple. Then
<x:foo xmlns:x="http://example.com"/>
and
<{http://example.com,foo}/>
would be the same. And
<xsl:value-of select="x:foo/@y:bar" xmlns:x="uri1" xmlns:y="uri2"/>
would be the same as
<{http://www.w3.org/1999/XSL/Transform,value-of} select="{uri1,foo}/@{uri2,bar}"/>
Be seeing you,
norm
- --
Norman.Walsh@Sun.COM | There is a road from the eye to the heart
XML Standards Architect | that does not go through the intellect.--G.
Web Tech. and Standards | K. Chesterton
Sun Microsystems, Inc. |
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: Processed by Mailcrypt 3.5.7 <http://mailcrypt.sourceforge.net/>
iD8DBQE+Lv4VOyltUcwYWjsRAkgVAJ4wRdqy6qWHJka9O1VqS8mQSNNbZQCeLzUs
GotMDLCL5KHFWIBn7eachBU=
=mztj
-----END PGP SIGNATURE-----
|
