Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


Re: [xml-dev] targetNamespace vs default namespace

From: Anne Thomas Manes <atmanes@-----.--->
To: REV Tamas <tamas.rev@-----.--->
Date: 7/6/2009 11:04:00 PM
Michael and Pete have already supplied answers to your question, but I
thought it might help to explicitly clarify one additional point --
which is to differentiate the default behavior between declaration and
reference. In this example:

     <xsd:complexType name="complexTypeOne">
        <xsd:sequence>
            ...
            <xsd:element name="SubElementWithoutPrefix"
                  type="ElementTypeWithoutPrefix" /> <!-- a line with
a problem -->
        </xsd:sequence>
    </xsd:complexType>

"SubElementWithoutPrefix" is a local element *declaration*. Because
the <schema> declaration specifies elementFormDefault="qualified",
this element is in the targetNamespace. (If  you didn't have
elementFormDefault="qualified", it would be in no namespace.)

"ElementTypeWithoutPrefix" is a type *reference*. Because no prefix is
explicitly specified, the type is from the default namespace.

Defining elements in a different namespace from their types is a
fairly common practice.

The Sun Java 6 validation is in error. The IBM Java 5 validation is correct.

Anne


On Mon, Jul 6, 2009 at 11:35 AM, REV Tamas<tamas.rev@g...> wrote:
> Hello,
>
> A customer gave us an xml schema having different default ns and
> targetNamspace, like that:
> <xsd:schema xmlns="ProprietaryNamespace"
> targetNamespace="AnotherProprietaryNamespace"
> xmlns:xsd="http://www.w3.org/2001/XMLSchema">
> ...
>     <xsd:complexType name="complexTypeOne">
>         <xsd:sequence>
>             ...
>             <xsd:element name="SubElementWithoutPrefix"
> type="ElementTypeWithoutPrefix" /> <!-- a line with a problem -->
>         </xsd:sequence>
>     </xsd:complexType>
>     ...
> </xsd:schema>
>
> Now we have problem validating values of SubElementWithoutPrefix on
> different java plattforms.
>
> According to the XML schema specification, every element/attribute without
> namespace prefix belongs to the default namespace.
> On the other hand, unqualified elements defined in an xml schema belong to
> the schemas targetNamespace. So, there is this contradicition
> to be resolved.
>
> When SUNs Java 6 implementation resolves it, SubElementWithoutPrefix belongs
> to the default namespace. On the other hand,
> when IBMs java 5 implementation resolves it, SubElementWithoutPrefix belongs
> to the targetNamespace.
>
> How is it defined in XML schema specs?
>
> Best Regards,
> Tamas
>

_______________________________________________________________________

XML-DEV is a publicly archived, unmoderated list hosted by OASIS
to support XML implementation and development. To minimize
spam in the archives, you must subscribe before posting.

[Un]Subscribe/change address: http://www.oasis-open.org/mlmanage/
Or unsubscribe: xml-dev-unsubscribe@l...
subscribe: xml-dev-subscribe@l...
List archive: http://lists.xml.org/archives/xml-dev/
List Guidelines: http://www.oasis-open.org/maillists/guidelines.php



transparent
Print
Mail
Like It
Disclaimer
.

These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on www.altova.com/list/index.html. Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.

.
.

transparent

transparent