RE: [egov] ebXML and web services architectures

["John Weiler" <john@ichnet.org>]

Paul,

The ICHnet.org, a federally sponsored Enterprise Architecture consortia, has
a series of industry developed white papers on all type of architecture
subjects; Component-based Architectures, Business Alignment, Value Chain
Analysis, and more. The ICH  Architecture Resource Center is also supporting
a new collaborative architecture solution program where industry standards
groups and solution providers can engage government program managers in a
conflict free zone to better cope with this fast paced market. Attached is a
draft briefing on how this might work and invite you and others to comment
on this proposed effort.  It is being advocated by leaders from both
government and industry and would like for get input from you and others on
the committee.

If you are others are interested in participating in this architecture
collaboratory, please let me know.  This will be presented at the Fall
SecurE-Biz Solution Architecture Summit on Oct. 28-29 in the Wash. DC area.
www.SecurE-Biz.net

Cheers,

john

John Weiler
ICH Architecture Resource Center
"From Architectures to Implementation Reality"
+1-703-768-0400 (ph)
+1-703-765-9295 (fx)
+1-800-733-6687 (toll free)
www.ICHnet.org <http://www.ICHnet.org>
www.SecurE-Biz.net <http://www.SecurE-Biz.net>


-----Original Message-----
From: Paul Spencer [mailto:paul.spencer@boynings.co.uk]
Sent: Wednesday, July 30, 2003 5:19 AM
To: e-Gov
Subject: [egov] ebXML and web services


I have recently been thinking more about overall architectures for
e-Government. Most architectures need a combination of transactions (such as
the ability to file a tax return) and simple services that will be used by
interoperating systems. An example of the latter might be the need to
transform a name from the Extensible Name Language to/from a local format or
to look up a postal address based on a unique property reference. It seems
logical (to me at least) that the transactions would use ebXML and the
services would use SOAP/WSDL.

Treating each separately, the ebXML part would need an ebXML registry in
which would be stored business process specifications and CPPs (among other
things). Typically, the services would use a UDDI registry. Does anyone have
experience of having these working together or of combining them? And what
about combining SAML into this? I see this as totally independent, but
others might have different views.

Regards

Paul Spencer
Director
Boynings Consulting Ltd
http://www.boynings.co.uk


You may leave a Technical Committee at any time by visiting
http://www.oasis-open.org/apps/org/workgroup/egov/members/leave_workgroup.ph
p