Vincent Figari wrote:
Hello Panos,
Sorry may be I did not provide enough info:
With my example, Xerces has schema validation enabled,
and Xerces parser is initialized with a .xsd defining
an element named "elem" having an attribute named "attr"
in a namespace whose URI is "some-uri".
will be par
Absolutely right, I checked my .xsd: it is using elementFormDefault=qualified
and attributeFormDefault=unqualified, thus the attributes belonging to no
namespace.
Thanks again for the help.
Vincent
--- Phil Weighill-Smith <[EMAIL PROTECTED]> wrote:
> Interestingly you can change this default beh
:[EMAIL PROTECTED]
XML Editor - http://www.oxygenxml.com/
- Original Message -
From:
Phil Weighill-Smith
To: [EMAIL PROTECTED]
Sent: Wednesday, January 14, 2004 5:51
PM
Subject: Re: Validation error on prefixed
attribute
Interestingly you can change this default
Interestingly you can change this default behaviour very easily via the schema element in your XSD.
Use the elementFormDefault attribute to change how namespacing of elements works and attributeFormDefault to change how namespacing of attributes works. Both reside on the schema element and bot
George,
I think you are right, I guess I was wrongly assuming that the
attributes defined on elements specified in the .xsd were
implicitly belonging to the targetNamespace of the .xsd as well.
Sounds like a wrong assumption, attributes belong implicitly to
no name space.
Thanks,
Vincent
--
Also if "attr" is indeed defined in the schema make
sure that is globally defined and that it can be
accessed.
--- Vincent Figari <[EMAIL PROTECTED]> wrote:
> Hello Panos,
>
> Sorry may be I did not provide enough info:
> With my example, Xerces has schema validation
> enabled,
> and Xerces par
Are you sure that the schema has the "attr"
attributed defined?
--- Vincent Figari <[EMAIL PROTECTED]> wrote:
> Hello Panos,
>
> Sorry may be I did not provide enough info:
> With my example, Xerces has schema validation
> enabled,
> and Xerces parser is initialized with a .xsd
> defining
> an
> With my example, Xerces has schema validation enabled,
> and Xerces parser is initialized with a .xsd defining
> an element named "elem" having an attribute named "attr"
> in a namespace whose URI is "some-uri".
>
>
> will be parsed succesfully by Xerces, but:
>
>
> will cause Xerces to throw:
Hello Panos,
Sorry may be I did not provide enough info:
With my example, Xerces has schema validation enabled,
and Xerces parser is initialized with a .xsd defining
an element named "elem" having an attribute named "attr"
in a namespace whose URI is "some-uri".
will be parsed succesfully by Xe
>
>
>
> With schema validation enabled, Xerces throws:
> Fatal: cvc-complex-type.3.2.2: Attribute "pr:attr"
> is not allowed to appear in element "pr:elem".
>
Are you sure that this is a valid XML? It seems to
me that the DTD does not allow the specific attribute
inside the pr:elem element.
Hello Xerces users,
When parsing an xml element such as:
With schema validation enabled, Xerces throws:
Fatal: cvc-complex-type.3.2.2: Attribute "pr:attr" is not allowed to appear in
element "pr:elem".
I know it is weird to use a namespace prefix on an attribute, which references
the xml name
11 matches
Mail list logo
