Big +1 to #1 & 2 below.
What about dealing with SOAP1.2? We could prepare to have
a version compatible with SOAP1.2 when it changes status
to PR or REC. That would involve some namespace changes
and a change to the HTTP Binding as well as treatment of
attachments.
Cheers,
Chris
wrote:
> Team,
>
> I hope you have all had a pleasant break over the last couple of
> weeks. As the title says what do we do next? It is up to you, but here are
> some ideas to start with.
>
> 1 - we MUST capture, answer and resolve any question and issues during the 3
> month public review of version 2.0
> 2 - The IIC TC would like to produce a conformance test/suite/documentation
> for version 2.0, they will obvious need help from us to do this.
> 3 - The Business interface layer has never been written - do we need it?
> 4 - A primer/introduction to the messaging service
> 5 - A document to describe the minimum implementation. This may be linked
> to the IIC TC point above.
>
> Question: - Do we still have outstanding requirements that still need to be
> addressed? i.e. a definable business need for them.
>
> Over to all of you for comments.
>
> Ian Jones
> Chair OASIS ebXML Messaging Services TC
>
> Email:
>
>
> ----------------------------------------------------------------
> To subscribe or unsubscribe from this elist use the subscription
> manager: <http://lists.oasis-open.org/ob/adm.pl>
>
