Todd Biske wrote:
> For any particular interchange, you absolutely have to have to a
> common format. My opinion is that it is extremely difficult,
> however, to find a format that will work across all interchanges.
> The reason is that an interchange is defined by both the information
> and reason for the exchange. For example, one may have a universal
> model that describes an account. The information interchanged about
> that account, and the semantics of how that account is described may
> vary based on how that account is used. The representation of that
> account as part of an insurance transaction using ACORD XML for Life
> & Annuity may look very different that using that account for an
> equity transaction using FIXML. This example is for illustration
> purposes, as I haven't actually checked the XML schemas, but it's
> pretty safe to say that there are common entities that both standards
> describe with their own nuances. Both are widely accepted industry
> standards, so there is no right or wrong, only options.
>
> When groups go out to define standards, it is important to take the
> context into account. If you take a structural approach, you may
> wind up with a data representation that is structurally accurate, but
> not appropriate for any of the contexts in which that data is used.
> The good in that approach, however, is that you should have a model
> from which all of the context-specific models can be derived.
This is a great overview of the issues that will be ever present. Webservices
using XML provide a way to get something to the other side (as do all transport
protocols before them). However, it still does't solve the basic issue of
unifying the data formats, domains and models into an appropriate standard.
XSLT and related technologies can help make this happen. However, in the end,
you've still done some work, codifed some conversion semantics, all of which is
not infalible. The panacea of standards is not yet fulfilled, but it does have
a new face and some extra makeup.
Gregg Wonderly
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/service-orientated-architecture/
<*> To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
