OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help



   a model for web-services architecutres in b2b-scenarios

[ Lists Home | Date Index | Thread Index ]


I tried to define a logical model for web-service architectures for
b2b-scenarios. You can see my first idea in the mail-attachment.

(1)	e.g. UDDI
(2)	e.g. WSDL
(3)	a XML industry-standard, e.g. BMECat (www.bmecat.org) for e-catalogues
(4)	e.g. SOAP
(5)	SOAP-encoding rules or other encoding rules. In some cases  5 and 3
could be the same schema
(6)	RPC or Messaging
(7)	–
(9)	–
(10)	–

It was very important for me to consider that web-service independent
standards for semantics ("business vocabularies") are reusable (3) in
web-services. Furthermore I wanted to make clear that there exist several
message-pattern (not only rpc) and encoding-rules (not only SOAP-encoding).
As you see I am of the opinion that 4, 5 and 6 are independent to each other
(contrary to many people how think that XML-messaging should it include it's
own type-system).

I would be pleased to hear some comments…




News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 2001 XML.org. This site is hosted by OASIS