Ian:
Some aspects of remaining work items, that we need to discuss too:
1. Security
- Finalize Security restrictions, per BSP 1.0 and WS-Security - or
more?
2. Composition Security / Reliability
- How prescriptive the specification should be about the SOAP
processing order, both sender and receiver sides. (Is it enough to state the
required/optional functional compositions, or does interoperability require
more than this?)
3. Sharpen the definition of MSH
- Either restrictive (processor of ebMS headers only) or inclusive (composition
of processors of all headers - reliability, security, ebMS3)
- assuming we can partition MSH functions as sending/receiving
(corresponding to functional "modules" in http://www.w3.org/TR/qaframe-spec/),
can an MSH implement only sending or receiving? (This has some editorial
consequences such as labeling "sending MSH" or not)
4. Role for an MSH in the SOAP processing
model
- should a [receiving] MSH be only an endpoint as in ebMS 2, or could
an MSH be a SOAP intermediary? (Could a well-formed SOAP message - including
body, attachments...- "become" an ebMS3 message after processing by a
[sending] MSH, and then be reversed again in its former state by a receiving
MSH, and forwarding?) This opens interesting composition schemes. Note that this
is not about "MSH intermediaries".
Hamid & Jacques
-----Original Message-----
From: [mailto:]
Sent: Tuesday, March 22, 2005 6:30 AM
To:
Subject: [ebxml-msg] Groups - Messaging Weekly Call added
Messaging Weekly Call has been added by Mr Ian Jones
Date: Wednesday, 23 March 2005
Time: 11:00am - 12:00pm PT
Event Description:
Weekly Call
Tell: 303-928-2656
Pass code: 8864587#
Thanks Pete / SeeBeyond
Agenda:
1. Role
2. What is current status, progress and document
3. Review current status
4. Identify work items
5. Define plan and allocate work
6. Error handling
7. A.O.B.
Minutes:
View event details:
http://www.oasis-open.org/apps/org/workgroup/ebxml-msg/event.php?event_id=7441
PLEASE NOTE: If the above link does not work for you, your email
application may be breaking the link into two pieces. You may be
able to
copy and paste the entire link address into the address field of your
web
browser.
