Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


Re: [xml-dev] Help Needed to create an XSD

From: Anne Thomas Manes <atmanes@-----.--->
To: Cyril <cyrilw@----------.--->
Date: 10/4/2005 6:48:00 PM
Not to worry, Cyril. The data you get from the third party declares its own a default namespace in the schema instance:



<rptTransmit xmlns="http://www.foo.ca/XMLSchemas "

:

</rptTransmit>



Anne

On 10/4/05, Cyril <cyrilw@t...> wrote:
Thanks Michael and Anne T.

Just to consolidate my understanding about namespaces I think this is where
I was confused.

In my XML Data when there is no namespace prefix in the xml tag (for
<rptTransmit/>), doesn't it use the default namespace? I figured since my

default namespace has no definition of any element called rptTransmit, this
would be invalid.

I saw from your example you use a reference eg ref="foo:rptTransmit" or
ref="i:rptTransmit" with the prefix , should this prefix appear in the XML

Data I am creating ie <foo:rptTransmit> instead of just <rptTransmit>? Or is
the latter valid? I'm having trouble understanding how the parser would know
that the <rptTransmit> is from the external XSD since it has no prefix for

the namespace.

Cyril

-----Original Message-----
From: Michael Kay [mailto:mike@s...]
Sent: October 4, 2005 2:01 PM
To: 'Cyril'; 
xml-dev@l...
Subject: RE: [xml-dev] Help Needed to create an XSD


>
>
> Now I need to create my own XSD that contains some info in
> addition to the
> XML file I get from the 3rd party. It should look something like this

>
> <myrpt>
> <id>0000</id>
> <status>pending</status>
>
> <rptTransmit xmlns="http://www.foo.ca/XMLSchemas
 "
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> xsi:schemaLocation="http://www.foo.ca/XMLSchemas

> http://www.foo.ca/XMLSchemas/UAT/Transmit.xsd">
> :
> </rptTransmit>
> </myrpt>
>
>
>

> How will I create the XSD schema with the namespace of my
> tags and taking
> into consideration of the 3rd party namespace? Can anyone
> give me a sample
> XSD that will match what I 'd like to achieve

>

Something like this:

<xs:schema>

<xs:import namespace="http://www.foo.ca/XMLSchemas"
        schemaLocation="
http://www.foo.ca/XMLSchemas/UAT/Transmit.xsd"/>

<xs:element name="myrpt">
  <xs:sequence>
    <xs:element name="id"/>
    <xs:element name="status"/>

    <xs:element ref="i:rptTransmit" xmlns:i="http://www.foo.ca/XMLSchemas"/>
  </xs:sequence>
</xs:element>

</xs:schema>


That's just a sketch leaving out all the noise, but I hope you get the idea.

Michael Kay
http://www.saxonica.com/



-----------------------------------------------------------------

The xml-dev list is sponsored by XML.org <http://www.xml.org>, an
initiative of OASIS <http://www.oasis-open.org>

The list archives are at 
http://lists.xml.org/archives/xml-dev/

To subscribe or unsubscribe from this list use the subscription
manager: <
http://www.oasis-open.org/mlmanage/index.php>



-----------------------------------------------------------------
The xml-dev list is sponsored by XML.org <http://www.xml.org
>, an
initiative of OASIS <http://www.oasis-open.org>

The list archives are at http://lists.xml.org/archives/xml-dev/


To subscribe or unsubscribe from this list use the subscription
manager: <http://www.oasis-open.org/mlmanage/index.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