Lists Home |
Date Index |
- From: "Don Park" <email@example.com>
- To: <firstname.lastname@example.org>
- Date: Thu, 6 Aug 1998 01:00:42 -0700
>Right. The point is that if a parser just gives me the expanded names
>for element type names and attribute names then I can't do the match on
>the underlying URI because I can't get the underlying URI for the prefix
>in the stylesheet. If I have in attribute in the stylesheet:
>the application needs to be able to map "foo" to the associated URI.
>The parser can't do it automatically, because it has no way of knowing
>that the value of the match attribute is supposed to be treated as a
Looks like namespaces might have serious problems with XSL. There are also
some problems with DOM also which remains to be investigated (i.e. adding
and moving nodes across namespaces).
Current situation is very troubling to me. We have all taken XML namespace
for granted as the obvious solution to name conflict problems. I think the
question that must be answered first is: which should have the
'right-of-way'? XSL or namespace? DOM or namespace? Does 'right-of-way'
depend on finalization schedules? It sure feels like a game of 'chicken'...
xml-dev: A list for W3C XML Developers. To post, mailto:email@example.com
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/
To (un)subscribe, mailto:firstname.lastname@example.org the following message;
To subscribe to the digests, mailto:email@example.com the following message;
List coordinator, Henry Rzepa (mailto:firstname.lastname@example.org)