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

Re: [soapbuilders] Mixing sec5 with other encodings

Expand Messages
  • Andrew Layman
    Stephan Haustein wrote Assume a group of people having already agreed on a UML model. With section 5, most of the rest follows automatically... This
    Message 1 of 5 , Jul 18, 2001
    • 0 Attachment
      Stephan Haustein wrote "Assume a group of people having already agreed on a
      UML model. With section 5, most of the rest follows automatically..."

      This indicates one of the conveniences but also one of the weaknesses of
      section 5 regarding interoperability. Section 5 describes how to map from
      an underlying data model such as that in UML, C++, RDB or such, to an XML
      format. It presumes that the parties to the conversation have an out-of-band
      mechanism to agree on the underlying data model. As we have seen on this
      list, sometimes there are differences in those underlying data models. Java
      has some things in it that are not in UML and visa versa, for example. An
      advantage of using an XML schema is that there is no presumption of an
      underlying data model. The parties merely agree on the literal format of
      the message.

      If one already has reflection data handy, this may seem inefficient, but by
      agreeing to interoperate strictly on the format of the messages, fewer
      implementation-dependent details leak into what it necessary for
      interoperation.

      Andrew Layman
      http://strongbrains.com -- Resources for Self-Education
    Your message has been successfully submitted and would be delivered to recipients shortly.