You are viewing a plain text version of this content. The canonical link for it is here.
Posted to soap-user@ws.apache.org by Houman Moshtagh <de...@yahoo.de> on 2002/08/29 15:52:05 UTC
XML Instance --> XML Schema ?
Hello,
I have studied the whole XML Schema on W3C site. There is still something confusing me.
The XML Schema: po1.xsd
<schema xmlns="http://www.w3.org/2001/XMLSchema"
xmlns:po="http://www.example.com/PO1"
targetNamespace="http://www.example.com/PO1"
The XML Instance: po1.xml
<schema xmlns="http://www.w3.org/2001/XMLSchema"
xmlns:po="http://www.example.com/PO1"
targetNamespace="http://www.example.com/PO1"
I understand that the targetNamespace references to the customized XML Schema, which has to be written in the po1.xsd and in the po1.xml files. But how can the parser looks after my customized XML Schema which is saved in the po1.xsd file? How does it know where the XSD file is located? As far as I understood the Namespaces the URI of a Namespace is just there to mention a unique namespace. The Parser would not look after what's behind the URI.
Could someone help me to understand this? :o)
Houman
---------------------------------
Gesendet von http://mail.yahoo.de.
Möchten Sie mit einem Gruß antworten? http://grusskarten.yahoo.de.
soap with attachments
Posted by Praveen Peddi <pp...@contextmedia.com>.
Can anyone send me a sample apache soap client for sending attachments? I
want to send a multimedia files (like mpeg, mp3, jpg etc) as attachments to
the server.
I am using soap 2.2 version.
Also how do we receive attachments on the server side.
I awould appreciate if some one can send me a sample class both on client
side and server.
soap with attachments
Posted by Praveen Peddi <pp...@contextmedia.com>.
Can anyone send me a sample apache soap client for sending attachments? I
want to send a multimedia files (like mpeg, mp3, jpg etc) as attachments to
the server.
I am using soap 2.2 version.
Also how do we receive attachments on the server side.
I awould appreciate if some one can send me a sample class both on client
side and server.
--
To unsubscribe, e-mail: <ma...@xml.apache.org>
For additional commands, e-mail: <ma...@xml.apache.org>
AW: XML Instance --> XML Schema ? (update)
Posted by Houman Moshtagh <de...@yahoo.de>.
Anne,
Thanks a lot for your response. It was a big help.
Soon I will begin studying the WSDL specification, maybe there is also
something confusing. In this case I'll be back with a new question. Hehe
But I think I have the most confusing things (Namespace / Schema) behind
me. :o)
Houman
-----Ursprüngliche Nachricht-----
Von: Anne Thomas Manes [mailto:anne@manes.net]
Gesendet: Sonntag, 1. September 2002 16:50
An: soap-user@xml.apache.org
Betreff: RE: XML Instance --> XML Schema ? (update)
Houman,
An XML instance isn't *required* to conform to a schema, and you don't
have
to validate an XML instance against a schema to process the document
unless
you want to. Keep in mind:
1- your namespace doesn't need to refer to an actual schema (the primary
purpose of a namespace qualifier is simply to distinguish two elements
with
the same name)
2- if you do use a schema for your namespace, you don't have to specify
an
absolute location for the schema unless you want to be able to validate
the
XML instance using the schema.
3- you can validate an XML instance using a different schema, assuming
it
defines the same Qnames, elements, and types.
You make a comment below: "Ok, but would the XML instance still running
as
it should?". Keep in mind that an XML document doesn't "run". An XML
document simply "is". It's the application that processes the XML
document
that runs. And it's up to the application to worry about types and
validation.
Many application languages, such as Java and C++, require data elements
to
be typed. Others, such as perl, don't really care about types. SOAP (the
specification) permits you to type the data in the messages, although it
doesn't require it. You can send SOAP messages that contain untyped
elements
(although not all SOAP implementations can process untyped elements).
Keep
in mind that you can specify soapenv:encodingStyle="", which means that
you
make no claims about the encoding style of your message elements.
If you use doc/literal, then you're saying that the message conforms to
a
specific schema. In this circumstance, you SHOULD reference a schema or
WSDL
(either in the namespace URI or using the xsi:schemaLocation attribute)
that
defines the document and the type information. Otherwise the receiving
application might have trouble figuring out how to process the message.
But
even in this situation, the receiving application isn't required to use
the
schema that you reference.
SOAP supports loosely coupled communication. I'll send you a message,
and
I'll provide you with some hints to help you figure out how to interpret
it,
but it's up to you to interpret it any way you like. (From a practical
point
of view, it really helps to define your messages and your exchange
pattern
using WSDL with the appropriate type information.)
Anne
> -----Original Message-----
> From: Houman Moshtagh [mailto:dev_wsdl@yahoo.de]
> Sent: Saturday, August 31, 2002 3:23 PM
> To: soap-user@xml.apache.org
> Subject: AW: XML Instance --> XML Schema ? (update)
> Importance: High
>
>
> Hi Ann,
>
> Ok let's try an example; this is the best way to understand this. :)
>
> - First the Schema:
>
> <xsd:element name="student" type="personinfo"/>
>
> <xsd:complexType name="personinfo">
> <xsd:sequence>
> <xsd:element name="name" type="xsd:string"/>
> <xsd:element name="age" type="xsd:positiveInteger"/>
> <xsd:element name="adress" type="USAdress"/>
> </xsd:sequence>
> </xsd:complexType>
>
> <xsd:complexType name="USAdress">
> <xsd:sequence>
> <xsd:element name="street" type="xsd:string"/>
> <xsd:element name="city" type="xsd:string"/>
> </xsd:sequence>
> </xsd:complexType>
>
>
> - And now the XML instance:
>
> <student>
> <name>Houman</name>
> <age>27</age>
> <adress>
> <street>Street</street>
> <city>City</city>
> </adress>
> </student>
>
>
> That means if I dont use the XMLSchemalocation there wouldn't be a
way
> to validate if my tags in the instance have the right data type. E.g.
> where should it know about the positive Integer of "age"? Ok, but
would
> the XML instance still running as it should? Hmmmm on the other hand
> there is no need for the XML Schema if the instance has already the
> right data types (e.g. String) and the right restrictions (e.g.
positive
> integer). So the XML instance could work even without validating
> through the Schema, thats why the schema is optional. I think I get
> the point now, isn't it? :)
>
> How is about SOAP? Soap uses also the namespaces and
xsi:schemalocation.
> Can SOAP also validate a piece of XML tags in the body through a user
> defined Schema? I can image this makes no sense about RPC-SOAP, since
> the information provided in the body is just the return value of some
> method.
> But what's about the Document-Style-SOAP? An XML Schema could be
useful
> for an instance of XML provided in the body. What do you think?
>
>
> Houman
>
>
>
>
> -----Ursprüngliche Nachricht-----
> Von: Anne Thomas Manes [mailto:anne@manes.net]
> Gesendet: Freitag, 30. August 2002 14:05
> An: soap-user@xml.apache.org
> Betreff: RE: XML Instance --> XML Schema ? (update)
>
> If you want to validate the document using a schema, then you have to
> tell
> the validator where to find the schema. But you don't necessarily have
> to
> tell your validator the actual location of the schema from within the
> document. You might provide the location using a switch or parameter
> when
> you launch the validator. (Perhaps you don't have access to the
original
> schema, or perhaps you want to validate it using a different schema.)
>
> If you don't provide the schema location to the validator when you
> launch
> it, then the validator has to rely on the hints supplied within the
> document -- which can be specified either in the namespace declaration
> or in
> the xsi:schemaLocation attribute.
>
> Anne
>
> > -----Original Message-----
> > From: Houman Moshtagh [mailto:dev_wsdl@yahoo.de]
> > Sent: Friday, August 30, 2002 7:41 AM
> > To: soap-user@xml.apache.org
> > Subject: XML Instance --> XML Schema ? (update)
> > Importance: High
> >
> >
> > Oopps. I ve made a mistake in my example.
> >
> > - The XML Schema: po1.xsd
> >
> > <schema xmlns="http://www.w3.org/2001/XMLSchema"
> > xmlns:po="http://www.example.com/PO1"
> > targetNamespace="http://www.example.com/PO1"
> >
> >
> >
> > - The XML Instance: po1.xml
> >
> > <?xml version="1.0"?>
> > <apo:purchaseOrder xmlns:apo="http://www.example.com/PO1"
> >
> >
> >
> > I understand that the targetNamespace references to the customized
XML
> > Schema. But how can the parser looks after my customized XML Schema
> > which is saved in the po1.xsd file? How does it know where the XSD
> file
> > is located? As far as I understood the Namespaces, the URI of a
> > Namespace is just there to mention a unique namespace. The Parser
> would
> > not look after what's behind the URI.
> >
> > Maybe there is the need of using xsi:schemaLocation. But there is
no
> > sign of this in the examples. Besides xsi:schemaLocation is also
just
> > there to give "hints" to the processor (validating). It doesn't
need
> > them really for running. So if it's optional so how can an instance
> > find the customized Schema? This topic of XML is really weird. :)
> >
> >
> > Could someone help me to understand this please? :o)
> >
> > Houman
> >
> >
> > __________________________________________________________________
> >
> > Gesendet von Yahoo! Mail - http://mail.yahoo.de
> > Möchten Sie mit einem Gruß antworten? http://grusskarten.yahoo.de
> >
> > --
> > To unsubscribe, e-mail:
> <ma...@xml.apache.org>
> > For additional commands, e-mail:
> <ma...@xml.apache.org>
> >
>
>
> --
> To unsubscribe, e-mail:
<ma...@xml.apache.org>
> For additional commands, e-mail:
<ma...@xml.apache.org>
>
> __________________________________________________________________
>
> Gesendet von Yahoo! Mail - http://mail.yahoo.de
> Möchten Sie mit einem Gruß antworten? http://grusskarten.yahoo.de
>
> --
> To unsubscribe, e-mail:
<ma...@xml.apache.org>
> For additional commands, e-mail:
<ma...@xml.apache.org>
>
--
To unsubscribe, e-mail: <ma...@xml.apache.org>
For additional commands, e-mail: <ma...@xml.apache.org>
__________________________________________________________________
Gesendet von Yahoo! Mail - http://mail.yahoo.de
Möchten Sie mit einem Gruß antworten? http://grusskarten.yahoo.de
--
To unsubscribe, e-mail: <ma...@xml.apache.org>
For additional commands, e-mail: <ma...@xml.apache.org>
AW: XML Instance --> XML Schema ? (update)
Posted by Houman Moshtagh <de...@yahoo.de>.
Anne,
Thanks a lot for your response. It was a big help.
Soon I will begin studying the WSDL specification, maybe there is also
something confusing. In this case I'll be back with a new question. Hehe
But I think I have the most confusing things (Namespace / Schema) behind
me. :o)
Houman
-----Ursprüngliche Nachricht-----
Von: Anne Thomas Manes [mailto:anne@manes.net]
Gesendet: Sonntag, 1. September 2002 16:50
An: soap-user@xml.apache.org
Betreff: RE: XML Instance --> XML Schema ? (update)
Houman,
An XML instance isn't *required* to conform to a schema, and you don't
have
to validate an XML instance against a schema to process the document
unless
you want to. Keep in mind:
1- your namespace doesn't need to refer to an actual schema (the primary
purpose of a namespace qualifier is simply to distinguish two elements
with
the same name)
2- if you do use a schema for your namespace, you don't have to specify
an
absolute location for the schema unless you want to be able to validate
the
XML instance using the schema.
3- you can validate an XML instance using a different schema, assuming
it
defines the same Qnames, elements, and types.
You make a comment below: "Ok, but would the XML instance still running
as
it should?". Keep in mind that an XML document doesn't "run". An XML
document simply "is". It's the application that processes the XML
document
that runs. And it's up to the application to worry about types and
validation.
Many application languages, such as Java and C++, require data elements
to
be typed. Others, such as perl, don't really care about types. SOAP (the
specification) permits you to type the data in the messages, although it
doesn't require it. You can send SOAP messages that contain untyped
elements
(although not all SOAP implementations can process untyped elements).
Keep
in mind that you can specify soapenv:encodingStyle="", which means that
you
make no claims about the encoding style of your message elements.
If you use doc/literal, then you're saying that the message conforms to
a
specific schema. In this circumstance, you SHOULD reference a schema or
WSDL
(either in the namespace URI or using the xsi:schemaLocation attribute)
that
defines the document and the type information. Otherwise the receiving
application might have trouble figuring out how to process the message.
But
even in this situation, the receiving application isn't required to use
the
schema that you reference.
SOAP supports loosely coupled communication. I'll send you a message,
and
I'll provide you with some hints to help you figure out how to interpret
it,
but it's up to you to interpret it any way you like. (From a practical
point
of view, it really helps to define your messages and your exchange
pattern
using WSDL with the appropriate type information.)
Anne
> -----Original Message-----
> From: Houman Moshtagh [mailto:dev_wsdl@yahoo.de]
> Sent: Saturday, August 31, 2002 3:23 PM
> To: soap-user@xml.apache.org
> Subject: AW: XML Instance --> XML Schema ? (update)
> Importance: High
>
>
> Hi Ann,
>
> Ok let's try an example; this is the best way to understand this. :)
>
> - First the Schema:
>
> <xsd:element name="student" type="personinfo"/>
>
> <xsd:complexType name="personinfo">
> <xsd:sequence>
> <xsd:element name="name" type="xsd:string"/>
> <xsd:element name="age" type="xsd:positiveInteger"/>
> <xsd:element name="adress" type="USAdress"/>
> </xsd:sequence>
> </xsd:complexType>
>
> <xsd:complexType name="USAdress">
> <xsd:sequence>
> <xsd:element name="street" type="xsd:string"/>
> <xsd:element name="city" type="xsd:string"/>
> </xsd:sequence>
> </xsd:complexType>
>
>
> - And now the XML instance:
>
> <student>
> <name>Houman</name>
> <age>27</age>
> <adress>
> <street>Street</street>
> <city>City</city>
> </adress>
> </student>
>
>
> That means if I dont use the XMLSchemalocation there wouldn't be a
way
> to validate if my tags in the instance have the right data type. E.g.
> where should it know about the positive Integer of "age"? Ok, but
would
> the XML instance still running as it should? Hmmmm on the other hand
> there is no need for the XML Schema if the instance has already the
> right data types (e.g. String) and the right restrictions (e.g.
positive
> integer). So the XML instance could work even without validating
> through the Schema, thats why the schema is optional. I think I get
> the point now, isn't it? :)
>
> How is about SOAP? Soap uses also the namespaces and
xsi:schemalocation.
> Can SOAP also validate a piece of XML tags in the body through a user
> defined Schema? I can image this makes no sense about RPC-SOAP, since
> the information provided in the body is just the return value of some
> method.
> But what's about the Document-Style-SOAP? An XML Schema could be
useful
> for an instance of XML provided in the body. What do you think?
>
>
> Houman
>
>
>
>
> -----Ursprüngliche Nachricht-----
> Von: Anne Thomas Manes [mailto:anne@manes.net]
> Gesendet: Freitag, 30. August 2002 14:05
> An: soap-user@xml.apache.org
> Betreff: RE: XML Instance --> XML Schema ? (update)
>
> If you want to validate the document using a schema, then you have to
> tell
> the validator where to find the schema. But you don't necessarily have
> to
> tell your validator the actual location of the schema from within the
> document. You might provide the location using a switch or parameter
> when
> you launch the validator. (Perhaps you don't have access to the
original
> schema, or perhaps you want to validate it using a different schema.)
>
> If you don't provide the schema location to the validator when you
> launch
> it, then the validator has to rely on the hints supplied within the
> document -- which can be specified either in the namespace declaration
> or in
> the xsi:schemaLocation attribute.
>
> Anne
>
> > -----Original Message-----
> > From: Houman Moshtagh [mailto:dev_wsdl@yahoo.de]
> > Sent: Friday, August 30, 2002 7:41 AM
> > To: soap-user@xml.apache.org
> > Subject: XML Instance --> XML Schema ? (update)
> > Importance: High
> >
> >
> > Oopps. I ve made a mistake in my example.
> >
> > - The XML Schema: po1.xsd
> >
> > <schema xmlns="http://www.w3.org/2001/XMLSchema"
> > xmlns:po="http://www.example.com/PO1"
> > targetNamespace="http://www.example.com/PO1"
> >
> >
> >
> > - The XML Instance: po1.xml
> >
> > <?xml version="1.0"?>
> > <apo:purchaseOrder xmlns:apo="http://www.example.com/PO1"
> >
> >
> >
> > I understand that the targetNamespace references to the customized
XML
> > Schema. But how can the parser looks after my customized XML Schema
> > which is saved in the po1.xsd file? How does it know where the XSD
> file
> > is located? As far as I understood the Namespaces, the URI of a
> > Namespace is just there to mention a unique namespace. The Parser
> would
> > not look after what's behind the URI.
> >
> > Maybe there is the need of using xsi:schemaLocation. But there is
no
> > sign of this in the examples. Besides xsi:schemaLocation is also
just
> > there to give "hints" to the processor (validating). It doesn't
need
> > them really for running. So if it's optional so how can an instance
> > find the customized Schema? This topic of XML is really weird. :)
> >
> >
> > Could someone help me to understand this please? :o)
> >
> > Houman
> >
> >
> > __________________________________________________________________
> >
> > Gesendet von Yahoo! Mail - http://mail.yahoo.de
> > Möchten Sie mit einem Gruß antworten? http://grusskarten.yahoo.de
> >
> > --
> > To unsubscribe, e-mail:
> <ma...@xml.apache.org>
> > For additional commands, e-mail:
> <ma...@xml.apache.org>
> >
>
>
> --
> To unsubscribe, e-mail:
<ma...@xml.apache.org>
> For additional commands, e-mail:
<ma...@xml.apache.org>
>
> __________________________________________________________________
>
> Gesendet von Yahoo! Mail - http://mail.yahoo.de
> Möchten Sie mit einem Gruß antworten? http://grusskarten.yahoo.de
>
> --
> To unsubscribe, e-mail:
<ma...@xml.apache.org>
> For additional commands, e-mail:
<ma...@xml.apache.org>
>
--
To unsubscribe, e-mail: <ma...@xml.apache.org>
For additional commands, e-mail: <ma...@xml.apache.org>
__________________________________________________________________
Gesendet von Yahoo! Mail - http://mail.yahoo.de
Möchten Sie mit einem Gruß antworten? http://grusskarten.yahoo.de
RE: XML Instance --> XML Schema ? (update)
Posted by Anne Thomas Manes <an...@manes.net>.
Houman,
An XML instance isn't *required* to conform to a schema, and you don't have
to validate an XML instance against a schema to process the document unless
you want to. Keep in mind:
1- your namespace doesn't need to refer to an actual schema (the primary
purpose of a namespace qualifier is simply to distinguish two elements with
the same name)
2- if you do use a schema for your namespace, you don't have to specify an
absolute location for the schema unless you want to be able to validate the
XML instance using the schema.
3- you can validate an XML instance using a different schema, assuming it
defines the same Qnames, elements, and types.
You make a comment below: "Ok, but would the XML instance still running as
it should?". Keep in mind that an XML document doesn't "run". An XML
document simply "is". It's the application that processes the XML document
that runs. And it's up to the application to worry about types and
validation.
Many application languages, such as Java and C++, require data elements to
be typed. Others, such as perl, don't really care about types. SOAP (the
specification) permits you to type the data in the messages, although it
doesn't require it. You can send SOAP messages that contain untyped elements
(although not all SOAP implementations can process untyped elements). Keep
in mind that you can specify soapenv:encodingStyle="", which means that you
make no claims about the encoding style of your message elements.
If you use doc/literal, then you're saying that the message conforms to a
specific schema. In this circumstance, you SHOULD reference a schema or WSDL
(either in the namespace URI or using the xsi:schemaLocation attribute) that
defines the document and the type information. Otherwise the receiving
application might have trouble figuring out how to process the message. But
even in this situation, the receiving application isn't required to use the
schema that you reference.
SOAP supports loosely coupled communication. I'll send you a message, and
I'll provide you with some hints to help you figure out how to interpret it,
but it's up to you to interpret it any way you like. (From a practical point
of view, it really helps to define your messages and your exchange pattern
using WSDL with the appropriate type information.)
Anne
> -----Original Message-----
> From: Houman Moshtagh [mailto:dev_wsdl@yahoo.de]
> Sent: Saturday, August 31, 2002 3:23 PM
> To: soap-user@xml.apache.org
> Subject: AW: XML Instance --> XML Schema ? (update)
> Importance: High
>
>
> Hi Ann,
>
> Ok let's try an example; this is the best way to understand this. :)
>
> - First the Schema:
>
> <xsd:element name="student" type="personinfo"/>
>
> <xsd:complexType name="personinfo">
> <xsd:sequence>
> <xsd:element name="name" type="xsd:string"/>
> <xsd:element name="age" type="xsd:positiveInteger"/>
> <xsd:element name="adress" type="USAdress"/>
> </xsd:sequence>
> </xsd:complexType>
>
> <xsd:complexType name="USAdress">
> <xsd:sequence>
> <xsd:element name="street" type="xsd:string"/>
> <xsd:element name="city" type="xsd:string"/>
> </xsd:sequence>
> </xsd:complexType>
>
>
> - And now the XML instance:
>
> <student>
> <name>Houman</name>
> <age>27</age>
> <adress>
> <street>Street</street>
> <city>City</city>
> </adress>
> </student>
>
>
> That means if I dont use the XMLSchemalocation there wouldn't be a way
> to validate if my tags in the instance have the right data type. E.g.
> where should it know about the positive Integer of "age"? Ok, but would
> the XML instance still running as it should? Hmmmm on the other hand
> there is no need for the XML Schema if the instance has already the
> right data types (e.g. String) and the right restrictions (e.g. positive
> integer). So the XML instance could work even without validating
> through the Schema, thats why the schema is optional. I think I get
> the point now, isn't it? :)
>
> How is about SOAP? Soap uses also the namespaces and xsi:schemalocation.
> Can SOAP also validate a piece of XML tags in the body through a user
> defined Schema? I can image this makes no sense about RPC-SOAP, since
> the information provided in the body is just the return value of some
> method.
> But what's about the Document-Style-SOAP? An XML Schema could be useful
> for an instance of XML provided in the body. What do you think?
>
>
> Houman
>
>
>
>
> -----Ursprüngliche Nachricht-----
> Von: Anne Thomas Manes [mailto:anne@manes.net]
> Gesendet: Freitag, 30. August 2002 14:05
> An: soap-user@xml.apache.org
> Betreff: RE: XML Instance --> XML Schema ? (update)
>
> If you want to validate the document using a schema, then you have to
> tell
> the validator where to find the schema. But you don't necessarily have
> to
> tell your validator the actual location of the schema from within the
> document. You might provide the location using a switch or parameter
> when
> you launch the validator. (Perhaps you don't have access to the original
> schema, or perhaps you want to validate it using a different schema.)
>
> If you don't provide the schema location to the validator when you
> launch
> it, then the validator has to rely on the hints supplied within the
> document -- which can be specified either in the namespace declaration
> or in
> the xsi:schemaLocation attribute.
>
> Anne
>
> > -----Original Message-----
> > From: Houman Moshtagh [mailto:dev_wsdl@yahoo.de]
> > Sent: Friday, August 30, 2002 7:41 AM
> > To: soap-user@xml.apache.org
> > Subject: XML Instance --> XML Schema ? (update)
> > Importance: High
> >
> >
> > Oopps. I ve made a mistake in my example.
> >
> > - The XML Schema: po1.xsd
> >
> > <schema xmlns="http://www.w3.org/2001/XMLSchema"
> > xmlns:po="http://www.example.com/PO1"
> > targetNamespace="http://www.example.com/PO1"
> >
> >
> >
> > - The XML Instance: po1.xml
> >
> > <?xml version="1.0"?>
> > <apo:purchaseOrder xmlns:apo="http://www.example.com/PO1"
> >
> >
> >
> > I understand that the targetNamespace references to the customized XML
> > Schema. But how can the parser looks after my customized XML Schema
> > which is saved in the po1.xsd file? How does it know where the XSD
> file
> > is located? As far as I understood the Namespaces, the URI of a
> > Namespace is just there to mention a unique namespace. The Parser
> would
> > not look after what's behind the URI.
> >
> > Maybe there is the need of using xsi:schemaLocation. But there is no
> > sign of this in the examples. Besides xsi:schemaLocation is also just
> > there to give "hints" to the processor (validating). It doesn't need
> > them really for running. So if it's optional so how can an instance
> > find the customized Schema? This topic of XML is really weird. :)
> >
> >
> > Could someone help me to understand this please? :o)
> >
> > Houman
> >
> >
> > __________________________________________________________________
> >
> > Gesendet von Yahoo! Mail - http://mail.yahoo.de
> > Möchten Sie mit einem Gruß antworten? http://grusskarten.yahoo.de
> >
> > --
> > To unsubscribe, e-mail:
> <ma...@xml.apache.org>
> > For additional commands, e-mail:
> <ma...@xml.apache.org>
> >
>
>
> --
> To unsubscribe, e-mail: <ma...@xml.apache.org>
> For additional commands, e-mail: <ma...@xml.apache.org>
>
> __________________________________________________________________
>
> Gesendet von Yahoo! Mail - http://mail.yahoo.de
> Möchten Sie mit einem Gruß antworten? http://grusskarten.yahoo.de
>
> --
> To unsubscribe, e-mail: <ma...@xml.apache.org>
> For additional commands, e-mail: <ma...@xml.apache.org>
>
RE: XML Instance --> XML Schema ? (update)
Posted by Anne Thomas Manes <an...@manes.net>.
Houman,
An XML instance isn't *required* to conform to a schema, and you don't have
to validate an XML instance against a schema to process the document unless
you want to. Keep in mind:
1- your namespace doesn't need to refer to an actual schema (the primary
purpose of a namespace qualifier is simply to distinguish two elements with
the same name)
2- if you do use a schema for your namespace, you don't have to specify an
absolute location for the schema unless you want to be able to validate the
XML instance using the schema.
3- you can validate an XML instance using a different schema, assuming it
defines the same Qnames, elements, and types.
You make a comment below: "Ok, but would the XML instance still running as
it should?". Keep in mind that an XML document doesn't "run". An XML
document simply "is". It's the application that processes the XML document
that runs. And it's up to the application to worry about types and
validation.
Many application languages, such as Java and C++, require data elements to
be typed. Others, such as perl, don't really care about types. SOAP (the
specification) permits you to type the data in the messages, although it
doesn't require it. You can send SOAP messages that contain untyped elements
(although not all SOAP implementations can process untyped elements). Keep
in mind that you can specify soapenv:encodingStyle="", which means that you
make no claims about the encoding style of your message elements.
If you use doc/literal, then you're saying that the message conforms to a
specific schema. In this circumstance, you SHOULD reference a schema or WSDL
(either in the namespace URI or using the xsi:schemaLocation attribute) that
defines the document and the type information. Otherwise the receiving
application might have trouble figuring out how to process the message. But
even in this situation, the receiving application isn't required to use the
schema that you reference.
SOAP supports loosely coupled communication. I'll send you a message, and
I'll provide you with some hints to help you figure out how to interpret it,
but it's up to you to interpret it any way you like. (From a practical point
of view, it really helps to define your messages and your exchange pattern
using WSDL with the appropriate type information.)
Anne
> -----Original Message-----
> From: Houman Moshtagh [mailto:dev_wsdl@yahoo.de]
> Sent: Saturday, August 31, 2002 3:23 PM
> To: soap-user@xml.apache.org
> Subject: AW: XML Instance --> XML Schema ? (update)
> Importance: High
>
>
> Hi Ann,
>
> Ok let's try an example; this is the best way to understand this. :)
>
> - First the Schema:
>
> <xsd:element name="student" type="personinfo"/>
>
> <xsd:complexType name="personinfo">
> <xsd:sequence>
> <xsd:element name="name" type="xsd:string"/>
> <xsd:element name="age" type="xsd:positiveInteger"/>
> <xsd:element name="adress" type="USAdress"/>
> </xsd:sequence>
> </xsd:complexType>
>
> <xsd:complexType name="USAdress">
> <xsd:sequence>
> <xsd:element name="street" type="xsd:string"/>
> <xsd:element name="city" type="xsd:string"/>
> </xsd:sequence>
> </xsd:complexType>
>
>
> - And now the XML instance:
>
> <student>
> <name>Houman</name>
> <age>27</age>
> <adress>
> <street>Street</street>
> <city>City</city>
> </adress>
> </student>
>
>
> That means if I dont use the XMLSchemalocation there wouldn't be a way
> to validate if my tags in the instance have the right data type. E.g.
> where should it know about the positive Integer of "age"? Ok, but would
> the XML instance still running as it should? Hmmmm on the other hand
> there is no need for the XML Schema if the instance has already the
> right data types (e.g. String) and the right restrictions (e.g. positive
> integer). So the XML instance could work even without validating
> through the Schema, thats why the schema is optional. I think I get
> the point now, isn't it? :)
>
> How is about SOAP? Soap uses also the namespaces and xsi:schemalocation.
> Can SOAP also validate a piece of XML tags in the body through a user
> defined Schema? I can image this makes no sense about RPC-SOAP, since
> the information provided in the body is just the return value of some
> method.
> But what's about the Document-Style-SOAP? An XML Schema could be useful
> for an instance of XML provided in the body. What do you think?
>
>
> Houman
>
>
>
>
> -----Ursprüngliche Nachricht-----
> Von: Anne Thomas Manes [mailto:anne@manes.net]
> Gesendet: Freitag, 30. August 2002 14:05
> An: soap-user@xml.apache.org
> Betreff: RE: XML Instance --> XML Schema ? (update)
>
> If you want to validate the document using a schema, then you have to
> tell
> the validator where to find the schema. But you don't necessarily have
> to
> tell your validator the actual location of the schema from within the
> document. You might provide the location using a switch or parameter
> when
> you launch the validator. (Perhaps you don't have access to the original
> schema, or perhaps you want to validate it using a different schema.)
>
> If you don't provide the schema location to the validator when you
> launch
> it, then the validator has to rely on the hints supplied within the
> document -- which can be specified either in the namespace declaration
> or in
> the xsi:schemaLocation attribute.
>
> Anne
>
> > -----Original Message-----
> > From: Houman Moshtagh [mailto:dev_wsdl@yahoo.de]
> > Sent: Friday, August 30, 2002 7:41 AM
> > To: soap-user@xml.apache.org
> > Subject: XML Instance --> XML Schema ? (update)
> > Importance: High
> >
> >
> > Oopps. I ve made a mistake in my example.
> >
> > - The XML Schema: po1.xsd
> >
> > <schema xmlns="http://www.w3.org/2001/XMLSchema"
> > xmlns:po="http://www.example.com/PO1"
> > targetNamespace="http://www.example.com/PO1"
> >
> >
> >
> > - The XML Instance: po1.xml
> >
> > <?xml version="1.0"?>
> > <apo:purchaseOrder xmlns:apo="http://www.example.com/PO1"
> >
> >
> >
> > I understand that the targetNamespace references to the customized XML
> > Schema. But how can the parser looks after my customized XML Schema
> > which is saved in the po1.xsd file? How does it know where the XSD
> file
> > is located? As far as I understood the Namespaces, the URI of a
> > Namespace is just there to mention a unique namespace. The Parser
> would
> > not look after what's behind the URI.
> >
> > Maybe there is the need of using xsi:schemaLocation. But there is no
> > sign of this in the examples. Besides xsi:schemaLocation is also just
> > there to give "hints" to the processor (validating). It doesn't need
> > them really for running. So if it's optional so how can an instance
> > find the customized Schema? This topic of XML is really weird. :)
> >
> >
> > Could someone help me to understand this please? :o)
> >
> > Houman
> >
> >
> > __________________________________________________________________
> >
> > Gesendet von Yahoo! Mail - http://mail.yahoo.de
> > Möchten Sie mit einem Gruß antworten? http://grusskarten.yahoo.de
> >
> > --
> > To unsubscribe, e-mail:
> <ma...@xml.apache.org>
> > For additional commands, e-mail:
> <ma...@xml.apache.org>
> >
>
>
> --
> To unsubscribe, e-mail: <ma...@xml.apache.org>
> For additional commands, e-mail: <ma...@xml.apache.org>
>
> __________________________________________________________________
>
> Gesendet von Yahoo! Mail - http://mail.yahoo.de
> Möchten Sie mit einem Gruß antworten? http://grusskarten.yahoo.de
>
> --
> To unsubscribe, e-mail: <ma...@xml.apache.org>
> For additional commands, e-mail: <ma...@xml.apache.org>
>
--
To unsubscribe, e-mail: <ma...@xml.apache.org>
For additional commands, e-mail: <ma...@xml.apache.org>
AW: XML Instance --> XML Schema ? (update)
Posted by Houman Moshtagh <de...@yahoo.de>.
Hi Ann,
Ok let's try an example; this is the best way to understand this. :)
- First the Schema:
<xsd:element name="student" type="personinfo"/>
<xsd:complexType name="personinfo">
<xsd:sequence>
<xsd:element name="name" type="xsd:string"/>
<xsd:element name="age" type="xsd:positiveInteger"/>
<xsd:element name="adress" type="USAdress"/>
</xsd:sequence>
</xsd:complexType>
<xsd:complexType name="USAdress">
<xsd:sequence>
<xsd:element name="street" type="xsd:string"/>
<xsd:element name="city" type="xsd:string"/>
</xsd:sequence>
</xsd:complexType>
- And now the XML instance:
<student>
<name>Houman</name>
<age>27</age>
<adress>
<street>Street</street>
<city>City</city>
</adress>
</student>
That means if I dont use the XMLSchemalocation there wouldn't be a way
to validate if my tags in the instance have the right data type. E.g.
where should it know about the positive Integer of "age"? Ok, but would
the XML instance still running as it should? Hmmmm on the other hand
there is no need for the XML Schema if the instance has already the
right data types (e.g. String) and the right restrictions (e.g. positive
integer). So the XML instance could work even without validating
through the Schema, thats why the schema is optional. I think I get
the point now, isn't it? :)
How is about SOAP? Soap uses also the namespaces and xsi:schemalocation.
Can SOAP also validate a piece of XML tags in the body through a user
defined Schema? I can image this makes no sense about RPC-SOAP, since
the information provided in the body is just the return value of some
method.
But what's about the Document-Style-SOAP? An XML Schema could be useful
for an instance of XML provided in the body. What do you think?
Houman
-----Ursprüngliche Nachricht-----
Von: Anne Thomas Manes [mailto:anne@manes.net]
Gesendet: Freitag, 30. August 2002 14:05
An: soap-user@xml.apache.org
Betreff: RE: XML Instance --> XML Schema ? (update)
If you want to validate the document using a schema, then you have to
tell
the validator where to find the schema. But you don't necessarily have
to
tell your validator the actual location of the schema from within the
document. You might provide the location using a switch or parameter
when
you launch the validator. (Perhaps you don't have access to the original
schema, or perhaps you want to validate it using a different schema.)
If you don't provide the schema location to the validator when you
launch
it, then the validator has to rely on the hints supplied within the
document -- which can be specified either in the namespace declaration
or in
the xsi:schemaLocation attribute.
Anne
> -----Original Message-----
> From: Houman Moshtagh [mailto:dev_wsdl@yahoo.de]
> Sent: Friday, August 30, 2002 7:41 AM
> To: soap-user@xml.apache.org
> Subject: XML Instance --> XML Schema ? (update)
> Importance: High
>
>
> Oopps. I ve made a mistake in my example.
>
> - The XML Schema: po1.xsd
>
> <schema xmlns="http://www.w3.org/2001/XMLSchema"
> xmlns:po="http://www.example.com/PO1"
> targetNamespace="http://www.example.com/PO1"
>
>
>
> - The XML Instance: po1.xml
>
> <?xml version="1.0"?>
> <apo:purchaseOrder xmlns:apo="http://www.example.com/PO1"
>
>
>
> I understand that the targetNamespace references to the customized XML
> Schema. But how can the parser looks after my customized XML Schema
> which is saved in the po1.xsd file? How does it know where the XSD
file
> is located? As far as I understood the Namespaces, the URI of a
> Namespace is just there to mention a unique namespace. The Parser
would
> not look after what's behind the URI.
>
> Maybe there is the need of using xsi:schemaLocation. But there is no
> sign of this in the examples. Besides xsi:schemaLocation is also just
> there to give "hints" to the processor (validating). It doesn't need
> them really for running. So if it's optional so how can an instance
> find the customized Schema? This topic of XML is really weird. :)
>
>
> Could someone help me to understand this please? :o)
>
> Houman
>
>
> __________________________________________________________________
>
> Gesendet von Yahoo! Mail - http://mail.yahoo.de
> Möchten Sie mit einem Gruß antworten? http://grusskarten.yahoo.de
>
> --
> To unsubscribe, e-mail:
<ma...@xml.apache.org>
> For additional commands, e-mail:
<ma...@xml.apache.org>
>
--
To unsubscribe, e-mail: <ma...@xml.apache.org>
For additional commands, e-mail: <ma...@xml.apache.org>
__________________________________________________________________
Gesendet von Yahoo! Mail - http://mail.yahoo.de
Möchten Sie mit einem Gruß antworten? http://grusskarten.yahoo.de
AW: XML Instance --> XML Schema ? (update)
Posted by Houman Moshtagh <de...@yahoo.de>.
Hi Ann,
Ok let's try an example; this is the best way to understand this. :)
- First the Schema:
<xsd:element name="student" type="personinfo"/>
<xsd:complexType name="personinfo">
<xsd:sequence>
<xsd:element name="name" type="xsd:string"/>
<xsd:element name="age" type="xsd:positiveInteger"/>
<xsd:element name="adress" type="USAdress"/>
</xsd:sequence>
</xsd:complexType>
<xsd:complexType name="USAdress">
<xsd:sequence>
<xsd:element name="street" type="xsd:string"/>
<xsd:element name="city" type="xsd:string"/>
</xsd:sequence>
</xsd:complexType>
- And now the XML instance:
<student>
<name>Houman</name>
<age>27</age>
<adress>
<street>Street</street>
<city>City</city>
</adress>
</student>
That means if I dont use the XMLSchemalocation there wouldn't be a way
to validate if my tags in the instance have the right data type. E.g.
where should it know about the positive Integer of "age"? Ok, but would
the XML instance still running as it should? Hmmmm on the other hand
there is no need for the XML Schema if the instance has already the
right data types (e.g. String) and the right restrictions (e.g. positive
integer). So the XML instance could work even without validating
through the Schema, thats why the schema is optional. I think I get
the point now, isn't it? :)
How is about SOAP? Soap uses also the namespaces and xsi:schemalocation.
Can SOAP also validate a piece of XML tags in the body through a user
defined Schema? I can image this makes no sense about RPC-SOAP, since
the information provided in the body is just the return value of some
method.
But what's about the Document-Style-SOAP? An XML Schema could be useful
for an instance of XML provided in the body. What do you think?
Houman
-----Ursprüngliche Nachricht-----
Von: Anne Thomas Manes [mailto:anne@manes.net]
Gesendet: Freitag, 30. August 2002 14:05
An: soap-user@xml.apache.org
Betreff: RE: XML Instance --> XML Schema ? (update)
If you want to validate the document using a schema, then you have to
tell
the validator where to find the schema. But you don't necessarily have
to
tell your validator the actual location of the schema from within the
document. You might provide the location using a switch or parameter
when
you launch the validator. (Perhaps you don't have access to the original
schema, or perhaps you want to validate it using a different schema.)
If you don't provide the schema location to the validator when you
launch
it, then the validator has to rely on the hints supplied within the
document -- which can be specified either in the namespace declaration
or in
the xsi:schemaLocation attribute.
Anne
> -----Original Message-----
> From: Houman Moshtagh [mailto:dev_wsdl@yahoo.de]
> Sent: Friday, August 30, 2002 7:41 AM
> To: soap-user@xml.apache.org
> Subject: XML Instance --> XML Schema ? (update)
> Importance: High
>
>
> Oopps. I ve made a mistake in my example.
>
> - The XML Schema: po1.xsd
>
> <schema xmlns="http://www.w3.org/2001/XMLSchema"
> xmlns:po="http://www.example.com/PO1"
> targetNamespace="http://www.example.com/PO1"
>
>
>
> - The XML Instance: po1.xml
>
> <?xml version="1.0"?>
> <apo:purchaseOrder xmlns:apo="http://www.example.com/PO1"
>
>
>
> I understand that the targetNamespace references to the customized XML
> Schema. But how can the parser looks after my customized XML Schema
> which is saved in the po1.xsd file? How does it know where the XSD
file
> is located? As far as I understood the Namespaces, the URI of a
> Namespace is just there to mention a unique namespace. The Parser
would
> not look after what's behind the URI.
>
> Maybe there is the need of using xsi:schemaLocation. But there is no
> sign of this in the examples. Besides xsi:schemaLocation is also just
> there to give "hints" to the processor (validating). It doesn't need
> them really for running. So if it's optional so how can an instance
> find the customized Schema? This topic of XML is really weird. :)
>
>
> Could someone help me to understand this please? :o)
>
> Houman
>
>
> __________________________________________________________________
>
> Gesendet von Yahoo! Mail - http://mail.yahoo.de
> Möchten Sie mit einem Gruß antworten? http://grusskarten.yahoo.de
>
> --
> To unsubscribe, e-mail:
<ma...@xml.apache.org>
> For additional commands, e-mail:
<ma...@xml.apache.org>
>
--
To unsubscribe, e-mail: <ma...@xml.apache.org>
For additional commands, e-mail: <ma...@xml.apache.org>
__________________________________________________________________
Gesendet von Yahoo! Mail - http://mail.yahoo.de
Möchten Sie mit einem Gruß antworten? http://grusskarten.yahoo.de
--
To unsubscribe, e-mail: <ma...@xml.apache.org>
For additional commands, e-mail: <ma...@xml.apache.org>
RE: XML Instance --> XML Schema ? (update)
Posted by Anne Thomas Manes <an...@manes.net>.
If you want to validate the document using a schema, then you have to tell
the validator where to find the schema. But you don't necessarily have to
tell your validator the actual location of the schema from within the
document. You might provide the location using a switch or parameter when
you launch the validator. (Perhaps you don't have access to the original
schema, or perhaps you want to validate it using a different schema.)
If you don't provide the schema location to the validator when you launch
it, then the validator has to rely on the hints supplied within the
document -- which can be specified either in the namespace declaration or in
the xsi:schemaLocation attribute.
Anne
> -----Original Message-----
> From: Houman Moshtagh [mailto:dev_wsdl@yahoo.de]
> Sent: Friday, August 30, 2002 7:41 AM
> To: soap-user@xml.apache.org
> Subject: XML Instance --> XML Schema ? (update)
> Importance: High
>
>
> Oopps. I ve made a mistake in my example.
>
> - The XML Schema: po1.xsd
>
> <schema xmlns="http://www.w3.org/2001/XMLSchema"
> xmlns:po="http://www.example.com/PO1"
> targetNamespace="http://www.example.com/PO1"
>
>
>
> - The XML Instance: po1.xml
>
> <?xml version="1.0"?>
> <apo:purchaseOrder xmlns:apo="http://www.example.com/PO1"
>
>
>
> I understand that the targetNamespace references to the customized XML
> Schema. But how can the parser looks after my customized XML Schema
> which is saved in the po1.xsd file? How does it know where the XSD file
> is located? As far as I understood the Namespaces, the URI of a
> Namespace is just there to mention a unique namespace. The Parser would
> not look after what's behind the URI.
>
> Maybe there is the need of using xsi:schemaLocation. But there is no
> sign of this in the examples. Besides xsi:schemaLocation is also just
> there to give "hints" to the processor (validating). It doesn't need
> them really for running. So if it's optional so how can an instance
> find the customized Schema? This topic of XML is really weird. :)
>
>
> Could someone help me to understand this please? :o)
>
> Houman
>
>
> __________________________________________________________________
>
> Gesendet von Yahoo! Mail - http://mail.yahoo.de
> Möchten Sie mit einem Gruß antworten? http://grusskarten.yahoo.de
>
> --
> To unsubscribe, e-mail: <ma...@xml.apache.org>
> For additional commands, e-mail: <ma...@xml.apache.org>
>
--
To unsubscribe, e-mail: <ma...@xml.apache.org>
For additional commands, e-mail: <ma...@xml.apache.org>
RE: XML Instance --> XML Schema ? (update)
Posted by Anne Thomas Manes <an...@manes.net>.
If you want to validate the document using a schema, then you have to tell
the validator where to find the schema. But you don't necessarily have to
tell your validator the actual location of the schema from within the
document. You might provide the location using a switch or parameter when
you launch the validator. (Perhaps you don't have access to the original
schema, or perhaps you want to validate it using a different schema.)
If you don't provide the schema location to the validator when you launch
it, then the validator has to rely on the hints supplied within the
document -- which can be specified either in the namespace declaration or in
the xsi:schemaLocation attribute.
Anne
> -----Original Message-----
> From: Houman Moshtagh [mailto:dev_wsdl@yahoo.de]
> Sent: Friday, August 30, 2002 7:41 AM
> To: soap-user@xml.apache.org
> Subject: XML Instance --> XML Schema ? (update)
> Importance: High
>
>
> Oopps. I ve made a mistake in my example.
>
> - The XML Schema: po1.xsd
>
> <schema xmlns="http://www.w3.org/2001/XMLSchema"
> xmlns:po="http://www.example.com/PO1"
> targetNamespace="http://www.example.com/PO1"
>
>
>
> - The XML Instance: po1.xml
>
> <?xml version="1.0"?>
> <apo:purchaseOrder xmlns:apo="http://www.example.com/PO1"
>
>
>
> I understand that the targetNamespace references to the customized XML
> Schema. But how can the parser looks after my customized XML Schema
> which is saved in the po1.xsd file? How does it know where the XSD file
> is located? As far as I understood the Namespaces, the URI of a
> Namespace is just there to mention a unique namespace. The Parser would
> not look after what's behind the URI.
>
> Maybe there is the need of using xsi:schemaLocation. But there is no
> sign of this in the examples. Besides xsi:schemaLocation is also just
> there to give "hints" to the processor (validating). It doesn't need
> them really for running. So if it's optional so how can an instance
> find the customized Schema? This topic of XML is really weird. :)
>
>
> Could someone help me to understand this please? :o)
>
> Houman
>
>
> __________________________________________________________________
>
> Gesendet von Yahoo! Mail - http://mail.yahoo.de
> Möchten Sie mit einem Gruß antworten? http://grusskarten.yahoo.de
>
> --
> To unsubscribe, e-mail: <ma...@xml.apache.org>
> For additional commands, e-mail: <ma...@xml.apache.org>
>
XML Instance --> XML Schema ? (update)
Posted by Houman Moshtagh <de...@yahoo.de>.
Oopps. I ve made a mistake in my example.
- The XML Schema: po1.xsd
<schema xmlns="http://www.w3.org/2001/XMLSchema"
xmlns:po="http://www.example.com/PO1"
targetNamespace="http://www.example.com/PO1"
- The XML Instance: po1.xml
<?xml version="1.0"?>
<apo:purchaseOrder xmlns:apo="http://www.example.com/PO1"
I understand that the targetNamespace references to the customized XML
Schema. But how can the parser looks after my customized XML Schema
which is saved in the po1.xsd file? How does it know where the XSD file
is located? As far as I understood the Namespaces, the URI of a
Namespace is just there to mention a unique namespace. The Parser would
not look after what's behind the URI.
Maybe there is the need of using xsi:schemaLocation. But there is no
sign of this in the examples. Besides xsi:schemaLocation is also just
there to give "hints" to the processor (validating). It doesn't need
them really for running. So if it's optional so how can an instance
find the customized Schema? This topic of XML is really weird. :)
Could someone help me to understand this please? :o)
Houman
__________________________________________________________________
Gesendet von Yahoo! Mail - http://mail.yahoo.de
Möchten Sie mit einem Gruß antworten? http://grusskarten.yahoo.de
XML Instance --> XML Schema ? (update)
Posted by Houman Moshtagh <de...@yahoo.de>.
Oopps. I ve made a mistake in my example.
- The XML Schema: po1.xsd
<schema xmlns="http://www.w3.org/2001/XMLSchema"
xmlns:po="http://www.example.com/PO1"
targetNamespace="http://www.example.com/PO1"
- The XML Instance: po1.xml
<?xml version="1.0"?>
<apo:purchaseOrder xmlns:apo="http://www.example.com/PO1"
I understand that the targetNamespace references to the customized XML
Schema. But how can the parser looks after my customized XML Schema
which is saved in the po1.xsd file? How does it know where the XSD file
is located? As far as I understood the Namespaces, the URI of a
Namespace is just there to mention a unique namespace. The Parser would
not look after what's behind the URI.
Maybe there is the need of using xsi:schemaLocation. But there is no
sign of this in the examples. Besides xsi:schemaLocation is also just
there to give "hints" to the processor (validating). It doesn't need
them really for running. So if it's optional so how can an instance
find the customized Schema? This topic of XML is really weird. :)
Could someone help me to understand this please? :o)
Houman
__________________________________________________________________
Gesendet von Yahoo! Mail - http://mail.yahoo.de
Möchten Sie mit einem Gruß antworten? http://grusskarten.yahoo.de
--
To unsubscribe, e-mail: <ma...@xml.apache.org>
For additional commands, e-mail: <ma...@xml.apache.org>