Mark Brucks wrote on 10/22/2010 06:23:03 PM:
> Your example is still dealing with the interpretation of a prefix in
> an existing document, and I don't have an existing document. I am
> in control of which namespaces and which prefixes would be used.
I was just giving a "simple" example. XML sc
Your example is still dealing with the interpretation of a prefix in an
existing document, and I don't have an existing document. I am in control of
which namespaces and which prefixes would be used.
HOWEVER, your last statement hits the nail on the head and explains everything.
Indeed, I hav
I think an example will help to illustrate why such a method makes no
sense in the API. Consider the following document:
http://a"; xmlns:b="http://b";
xmlns:y="http://y"; xmlns:z="http://z";>
http://www.abc.com"; xmlns:x="http://www.xyz.com";>
http://www.xyz.com"; xmlns:x="http://www
Thanks for the responses.
Some clarification about my problem. I have the schema, but no instance
documents, and hence no worries about the fluid nature of prefixes between
schema and instance documents. My current task is to generate a "starter"
document from the schema. What I would like t
