RE: Layers in the WSA (was RE: [Fwd: UN/CEFACT TMG Releases e-Bus ines s Architecture Technical Specification for Public Review])

> Doesn't WSCI provide the framework for determining message content?  I

It let's you look at portions of the message as named properties, so you
could ask questions about the purchase order number or the total price of
the order, even though different messages may encode that information in
different parts or using different schemas (don't you just love XPath?).

This doesn't solve all the problems, but it does give a good framework from
which we can build additional things and it abstract the information
(property name/type) from the way in which it is contained in the message.

arkin

> guess using WSCI is not a requirement of the WSAG however.  This sounds
> very similar to a working group in CEFACT called the Generic Business
> Message Header working group.
>
> The flexability of the WSAG to not specifically require, yet still allow
> this where needed is nice.  I may be writing a chapter for a book on
> [SOAP | Web Services].  I may take this on as a challenge to show SOAP +
> WSDL working with an ebXML CPA.
>
> Duane
>
>
>
> --
> VP Strategic Relations,
> Technologies Evangelist
> XML Global Technologies
> ****************************
> ebXML software downloads - http://www.xmlglobal.com/prod/

Received on Thursday, 13 February 2003 00:54:06 UTC