Lists Home |
Date Index |
"Thomas B. Passin" <firstname.lastname@example.org> wrote:
| [Bill de hÓra]
| > - in my work with XML I've never run across a collision problem
| > that seemed to require namespaces. I wondering whether they're rare
| > or whether the markup I dela with is unusual.
| The one that leaps to my mind is using an xslt stylesheet to create another
| xslt stylesheet. [...] now that I bring it up, there will probably be a
| lot of solutions popping up (I can see using special attributes to indicate
| whether something is intended to be a literal result element or not)
Yup. It can be as simple as that. The XSLT case is actually easier than
the general problem, because there are no overlaps. All XSLT needs is the
moral equivalent of Lisp's quote/backquote operator.
So, you could take an "extension interpretation", where everything is a
literal by default and only XSLT (evaluable) expressions need be marked,
or you could take an "embedding interpretation" where everything is an
expression unless marked as a literal. The parser takes care of the rest.
(I'd say the former approach is "cleaner", with respect to the design
decision to do everything with pointy brackets.)