Stanimir Stamenkov wrote on 10/24/2010 06:51:13 AM:
> > 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.
>
> As Michael has already p
Fri, 22 Oct 2010 15:23:03 -0700, /Mark Brucks/:
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.
As Michael has already pointed out the schema
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
Hi Mark,
Mark Brucks wrote on 10/21/2010 03:17:47 PM:
> Here is the beginning of my schema file:
>
> http://www.foo.com/SchemaOne";
>xmlns:s1="http://www.foo.com/SchemaOne";
>xmlns:s2="http://www.foo.com/SchemaTwo";
>xmlns:s3="http://www.foo.com/SchemaThree";
I presume you don't need to be reminded that the prefix used in the
instance document may be different from the prefix used in the schema
document, and that in fact either or both of these may have several
prefixes bound to the same namespace simultaneously and/or sequentially...
__
