Loading ...
Sorry, an error occurred while loading the content.
 

RE: [soapbuilders] Re: multiple schemas in WSDL question (was Suggestion?)

Expand Messages
  • Matt Long
    Oops! I stand corrected (Beware the Ides of March!) i.e. = id est = that is e.g. = exempli gratia = for example Thx, -Matt Long Phalanx Systems, LLC ...
    Message 1 of 22 , May 6, 2002
      Oops!
      I stand corrected (Beware the Ides of March!)

      i.e. = id est = "that is"

      e.g. = exempli gratia = "for example"

      Thx,

      -Matt Long
      Phalanx Systems, LLC



      > -----Original Message-----
      > From: noah_mendelsohn@... [mailto:noah_mendelsohn@...]
      > Sent: Monday, May 06, 2002 9:21 AM
      > To: soapbuilders@yahoogroups.com
      > Subject: RE: [soapbuilders] Re: multiple schemas in WSDL question (was
      > Suggestion?)
      >
      > Yes, I think that's close enough. I think your "e.g." should be an
      "I.e."
      > though...it's not an example.
      >
      > ------------------------------------------------------------------
      > Noah Mendelsohn Voice: 1-617-693-4036
      > IBM Corporation Fax: 1-617-693-8676
      > One Rogers Street
      > Cambridge, MA 02142
      > ------------------------------------------------------------------
      >
      >
      >
      >
      >
      >
      >
      > "Matt Long" <mlong@...>
      > 05/06/2002 10:01 AM
      > Please respond to soapbuilders
      >
      >
      > To: <soapbuilders@yahoogroups.com>
      > cc: (bcc: Noah Mendelsohn/Cambridge/IBM)
      > Subject: RE: [soapbuilders] Re: multiple schemas in
      WSDL
      > question (was Suggestion?)
      >
      >
      > > Right conclusion, though I'm not sure your reasoning is quite
      correct.
      > > soap-enc must be imported in your example because it is used in a
      > > reference to a _schema_ component (in this case a type). In the
      > > example, the wsdl: namespace qualifies an attribute that means
      nothing
      > to
      > > schema.
      >
      > Is it accurate to state:?
      >
      > The wsdl namespace qualifies an attribute that is not a referenced
      > schema component, e.g., the wsdl namespace is not required to be
      > imported.
      >
      > Thx,
      >
      > -Matt Long
      > Phalanx Systems, LLC
      >
      >
      >
      > > -----Original Message-----
      > > From: noah_mendelsohn@... [mailto:noah_mendelsohn@...]
      > > Sent: Monday, May 06, 2002 8:24 AM
      > > To: soapbuilders@yahoogroups.com
      > > Subject: RE: [soapbuilders] Re: multiple schemas in WSDL question
      (was
      > > Suggestion?)
      > >
      > > Right conclusion, though I'm not sure your reasoning is quite
      correct.
      > > soap-enc must be imported in your example because it is used in a
      > > reference to a _schema_ component (in this case a type). In the
      > > example, the wsdl: namespace qualifies an attribute that means
      nothing
      > to
      > > schema. Although its presence is legal, it is considered to be like
      > > <xsd:annotation>, a means of adding extensions that schema does not
      > > understand. A wsdl-knowledgeable processor can do what it wants
      with
      > > this, but there is no need for a schema import...a processor
      > conforming to
      > > only the schema recommendation will do essentially nothing with the
      > > wsdl:arrayType attribute.
      > >
      > > ------------------------------------------------------------------
      > > Noah Mendelsohn Voice: 1-617-693-4036
      > > IBM Corporation Fax: 1-617-693-8676
      > > One Rogers Street
      > > Cambridge, MA 02142
      > > ------------------------------------------------------------------
      > >
      > >
      > >
      > >
      > >
      > >
      > >
      > > "Matt Long" <mlong@...>
      > > 05/03/2002 03:38 PM
      > > Please respond to soapbuilders
      > >
      > >
      > > To: <soapbuilders@yahoogroups.com>
      > > cc: (bcc: Noah Mendelsohn/Cambridge/IBM)
      > > Subject: RE: [soapbuilders] Re: multiple schemas in
      > WSDL
      > > question (was Suggestion?)
      > >
      > >
      > > For soap-enc arrays we are referencing soap-enc attributes, e.g.,
      from
      > > below, the soap-enc namespace is *required* to be imported.
      However,
      > > the wsdl namespace does not need to be imported as it does not
      > reference
      > > an external attribute, simpleType, or complexType.
      > >
      > > Fair summary?
      > >
      > > Thx,
      > >
      > > -Matt Long
      > > Phalanx Systems, LLC
      > >
      > >
      > > > -----Original Message-----
      > > > From: noah_mendelsohn@...
      [mailto:noah_mendelsohn@...]
      > > > Sent: Friday, May 03, 2002 1:17 PM
      > > > To: soapbuilders@yahoogroups.com
      > > > Subject: Re: [soapbuilders] Re: multiple schemas in WSDL question
      > (was
      > > > Suggestion?)
      > > >
      > > > A schema document must import every namespace that is used in a
      > > reference
      > > > to a schema component. Thus, in the following fragment:
      > > >
      > > > <xsd:element name="e" type="ns1:t"
      > > > ns2:randomNonStandardExtensionAttr="ns3:xxx">
      > > > <xsd:annotation>
      > > > <xsd:documentation>
      > > > <html:body> ...</html:body>
      > > > </xsd:documentation>
      > > > </xsd:annotation>
      > > > </xsd:element>
      > > >
      > > > ns1 must be imported, because it is used in a reference to a
      schema
      > > type
      > > > ns1:t. ns2, ns3, and html need not be imported. In the example,
      > > >
      > > > <xsd:element name="e" type="xsd:integer"/>
      > > >
      > > > I believe there is no need to import xsd, because the built-in
      types
      > > are
      > > > pre-imported. I believe I opened an issue to the schema WG to
      > clarify
      > > > this point in future publications.
      > > >
      > > > By the way, you need only import things directly referenced. If
      the
      > > type
      > > > ns1:t above was derived from ns5:base, there would be no need to
      > > import
      > > > ns5 in this schema document. (There almost surely would be such a
      > > need in
      > > > the schema document for the target namespace ns1.) In general,
      > > <import>
      > > > is there to distinguish namespaces for which schema components
      must
      > be
      > > > acquired, from all the other random uses of namespaces in a schema
      > > > document.
      > > >
      > > > Hope this helps.
      > > >
      > > > ------------------------------------------------------------------
      > > > Noah Mendelsohn Voice: 1-617-693-4036
      > > > IBM Corporation Fax: 1-617-693-8676
      > > > One Rogers Street
      > > > Cambridge, MA 02142
      > > > ------------------------------------------------------------------
      > > >
      > > >
      > > >
      > > >
      > > >
      > > >
      > > >
      > > > "simonfell99" <soap@...>
      > > > 05/03/02 12:52 PM
      > > > Please respond to soapbuilders
      > > >
      > > >
      > > > To: soapbuilders@yahoogroups.com
      > > > cc: (bcc: Noah Mendelsohn/Cambridge/IBM)
      > > > Subject: [soapbuilders] Re: multiple schemas in
      WSDL
      > > > question (was Suggestion?)
      > > >
      > > > I don't think there's a requirement for schema documents to import
      > > > all namespaces that appear in the doc. I had a quick look through
      > the
      > > > schema spec and didn't spot a section that covered extending
      schema,
      > > > i'll have a more detailed look later [unless one of the schema
      guys
      > > > want to jump in first]
      > > >
      > > > FWIW, I see the same results as Matt, MSXML4.0 requires the
      soap-enc
      > > > import [and this is missing from so many docs, that i now have an
      > > > option in my WSDL tools to insert it if needed :(], but doesn't
      > > > require an import for wsdl.
      > > >
      > > > Cheers
      > > > Simon
      > > > www.pocketsoap.com
      > > >
      > > > --- In soapbuilders@y..., Pete Hendry <peter.hendry@c...> wrote:
      > > > > Does this matter? It is used as a namespace in the schema so
      > should
      > > > > it not be included? Does the definition of anyAttribute in
      > > > > SOAP-ENC:arrayType as "lax" mean that the wsdl namespace does
      not
      > > > > need to be resolved to its schema?
      > > > >
      > > > > Pete
      > > > >
      > > > > Simon Fell wrote:
      > > > >
      > > > > >Hi,
      > > > > >
      > > > > >But unlike soap-enc, the wsdl namespace is not used as a value
      in
      > > > any
      > > > > >of the schema defined element / attribute.
      > > > > >
      > > > > >Cheers
      > > > > >Simon
      > > > > >www.pocketsoap.com
      > > > > >
      > > > > >On Fri, 03 May 2002 13:26:26 +1200, in soap you wrote:
      > > > > >
      > > > > >>soap-enc array definitions in WSDL use wsdl:arrayType
      > > > > >>
      > > > > >> <xsd:attribute ref="SOAP-ENC:arrayType"
      > > > wsdl:arrayType="xsd1:Snapshot[]"/>
      > > > > >>
      > > > > >>Obviously the wsdl schema would only be required if an array
      was
      > > > present
      > > > > >>in the schema.
      > > > > >>
      > > > > >>Pete
      > > > > >>
      > > > > >>simonfell99 wrote:
      > > > > >>
      > > > > >>>--- In soapbuilders@y..., Pete Hendry <peter.hendry@c...>
      > wrote:
      > > > > >>>
      > > > > >>>>>Imo, the soap-enc namespace _should _ be imported. While
      > > > current
      > > > > >>>>>SoapBuilderWSDLs mainly do not provide this, I don't see
      why
      > > > > >>>>>soap-enc namespace should be exempt from schema rules.
      > > > > >>>>>
      > > > > >>>>I agree with this. Also, the wsdl namespace should be
      > imported.
      > > > > >>>>It is not special either. A conforming schema parser should
      > > > > >>>>error with the current schemas being generated.
      > > > > >>>>
      > > > > >>>Right, I raised the import for soap-enc issue at the last
      > > > > >>>SOAPBuilders F2F. I'm less clear on why the WSDL namespace
      > > > should be
      > > > > >>>imported, I don't recall any schema constructs that reference
      > > > the
      > > > > >>>WSDL namespace, Care to give an example ?
      > > > > >>>
      > > > > >>>Cheers
      > > > > >>>Simon
      > > > > >>>www.pocketsoap.com
      > > > > >>>
      > > > > >>>
      > > > > >>>
      > > > >
      > >>>-----------------------------------------------------------------
      > > > > >>>This group is a forum for builders of SOAP implementations to
      > > > discuss implementation and interoperability issues. Please stay
      on-
      > > > topic.
      > > > > >>>
      > > > > >>>To unsubscribe from this group, send an email to:
      > > > > >>>soapbuilders-unsubscribe@y...
      > > > > >>>
      > > > > >>>
      > > > > >>>
      > > > > >>>Your use of Yahoo! Groups is subject to
      > > > http://docs.yahoo.com/info/terms/
      > > > > >>>
      > > > > >>>
      > > > > >
      > > > > >
      > > > > >
      > > > >
      >-----------------------------------------------------------------
      > > > > >This group is a forum for builders of SOAP implementations to
      > > > discuss implementation and interoperability issues. Please stay
      on-
      > > > topic.
      > > > > >
      > > > > >To unsubscribe from this group, send an email to:
      > > > > >soapbuilders-unsubscribe@y...
      > > > > >
      > > > > >
      > > > > >
      > > > > >Your use of Yahoo! Groups is subject to
      > > > http://docs.yahoo.com/info/terms/
      > > > > >
      > > > > >
      > > >
      > > >
      > > >
      > > > -----------------------------------------------------------------
      > > > This group is a forum for builders of SOAP implementations to
      > discuss
      > > > implementation and interoperability issues. Please stay on-topic.
      > > >
      > > > To unsubscribe from this group, send an email to:
      > > > soapbuilders-unsubscribe@yahoogroups.com
      > > >
      > > >
      > > >
      > > > Your use of Yahoo! Groups is subject to
      > > http://docs.yahoo.com/info/terms/
      > > >
      > > >
      > > >
      > > >
      > > >
      > > >
      > > > ------------------------ Yahoo! Groups Sponsor
      > > >
      > > > -----------------------------------------------------------------
      > > > This group is a forum for builders of SOAP implementations to
      > discuss
      > > > implementation and interoperability issues. Please stay on-topic.
      > > >
      > > > To unsubscribe from this group, send an email to:
      > > > soapbuilders-unsubscribe@yahoogroups.com
      > > >
      > > >
      > > >
      > > > Your use of Yahoo! Groups is subject to
      > > http://docs.yahoo.com/info/terms/
      > > >
      > >
      > >
      > >
      > >
      > > -----------------------------------------------------------------
      > > This group is a forum for builders of SOAP implementations to
      discuss
      > > implementation and interoperability issues. Please stay on-topic.
      > >
      > > To unsubscribe from this group, send an email to:
      > > soapbuilders-unsubscribe@yahoogroups.com
      > >
      > >
      > >
      > > Your use of Yahoo! Groups is subject to
      > http://docs.yahoo.com/info/terms/
      > >
      > >
      > >
      > >
      > >
      > >
      > > ------------------------ Yahoo! Groups Sponsor
      > >
      > > -----------------------------------------------------------------
      > > This group is a forum for builders of SOAP implementations to
      discuss
      > > implementation and interoperability issues. Please stay on-topic.
      > >
      > > To unsubscribe from this group, send an email to:
      > > soapbuilders-unsubscribe@yahoogroups.com
      > >
      > >
      > >
      > > Your use of Yahoo! Groups is subject to
      > http://docs.yahoo.com/info/terms/
      > >
      >
      >
      >
      >
      > -----------------------------------------------------------------
      > This group is a forum for builders of SOAP implementations to discuss
      > implementation and interoperability issues. Please stay on-topic.
      >
      > To unsubscribe from this group, send an email to:
      > soapbuilders-unsubscribe@yahoogroups.com
      >
      >
      >
      > Your use of Yahoo! Groups is subject to
      http://docs.yahoo.com/info/terms/
      >
      >
      >
      >
      >
      >
      > ------------------------ Yahoo! Groups Sponsor
      >
      > -----------------------------------------------------------------
      > This group is a forum for builders of SOAP implementations to discuss
      > implementation and interoperability issues. Please stay on-topic.
      >
      > To unsubscribe from this group, send an email to:
      > soapbuilders-unsubscribe@yahoogroups.com
      >
      >
      >
      > Your use of Yahoo! Groups is subject to
      http://docs.yahoo.com/info/terms/
      >
    Your message has been successfully submitted and would be delivered to recipients shortly.