- From: Arthur Ryman <arthur.ryman@gmail.com>
- Date: Thu, 21 Apr 2005 19:20:09 -0400
- To: www-ws-desc@w3.org
---------- Forwarded message ---------- From: Arthur Ryman <arthur.ryman@gmail.com> Date: Apr 21, 2005 4:59 PM Subject: Re: FW: Is schemaLocation Required When Importing Inline Schemas? To: Amelia A Lewis <amyzing@talsever.org> Sounds good it me. On 4/21/05, Amelia A Lewis <amyzing@talsever.org> wrote: > Hi, Arthur, > > Okay, let's see if we can language-lawyer it a bit. > > > 1) Let's at least add an explicit definition of inline schema. > > > > "A schema defined via <xs:schema> in the <wsdl:types> element is referred > > to as an inline schema" > > Good. > > [snip] > > On Wed, 30 Mar 2005 11:45:06 -0500 > > Arthur Ryman <ryman@ca.ibm.com> wrote: > >> We can phrase this in terms of document validity as follows: > >> > >> "All inline schemas that are contained in a WSDL document and any other > >> WSDL documents that it directly or indirectly imports or includes MUST > >> be used when resolving QName references to elements or types that belong > >> to namespaces that are imported via xs:import elements that have no > >> schemaLocation attribute." > > It is an error if a QName is not resolved. When resolving QNames > references for schema definitions, the namespace MUST be imported by the > referring WSDL document. If the namespace so referenced is contained in > an inline schema, it MAY be imported without a schemaLocation attribute, > so long as the inline schema has been encountered during resolution of > imports and includes for the current component model. > > Amy! >
Received on Thursday, 21 April 2005 23:20:14 UTC