- From: David Carlisle <davidc@nag.co.uk>
- Date: Tue, 23 May 2000 14:36:07 +0100 (BST)
- To: timbl@w3.org
- CC: jjc@JCLARK.COM, xml-uri@w3.org
> If this is not a problem, please explain why not. It's not a problem because it is just a case of a stylesheet not working as the author intended (which is, as anyone reading xsl-list will know, not at all an unusual situation:-) If you replaced in that example the relative namespace with an absolute one you would have exactly the same effect. Either the namespace in question is for denoting employees in company A, in which case company B ought to have used a different namespace. Or the namespace is for employees in `the current company' in which case the stylesheet ought have a parameter to tell it which company is current. To see this, replace xmlns="foo/ns" in your example by xmlns="http://www.example.com/foo/ns" You will see that given the current namesapce (rather than xpath) interpretation of namespaces, an XSLT engine will do _exactly_ the same thing, as it never need look at the internal structure of the namespace name at all. David
Received on Tuesday, 23 May 2000 09:36:41 UTC