- markup (52)
- xml (7)
- xslt (21)
- atom (8)
- overlapping markup (2)
- schema (9)
- creole (4)
- xforms (1)
- pipelines (7)
- coding (2)
- dtll (1)
- genealogy (3)
- gtd (1)
- hardware (1)
- legislation (1)
- ontologies (2)
- unicode (1)
- web (24)
- google (3)
- rdf (6)
- rest (3)
- wikis (1)
- work (1)
- xpath (1)
- xquery (1)
- xtech2008 (3)
- life (26)
- children (5)
- equality (6)
- environment (4)
- gadgets (5)
- software (3)
- xlinq (2)
- conferences (7)
- xtech (6)
- blog (7)
- drupal (3)
Re: Things that make me scream: RDF "QNames"
I find that I use QNames only for abbreviating the URIs of RDF vocabulary terms, that is, classes and properties. I don’t abbreviate the URIs of the resources I describe. Unlike the vocabulary terms, I rarely have to repeat them many times, so the length of their URIs isn’t much of an issue.
This makes the problem mostly go away, because RDF vocabulary designers are aware of the issues surrounding QNames and pick URIs that can be abbreviated for their classes and properties.
I don’t like your @base proposal, because as you say < and > don’t work well in XML documents, so you’d need different escaping rules, and things quickly become a mess. A nice thing about RDF’s pseudo-QNames is that they can be used almost anywhere without escaping, because they consist of such a limited set of characters.