1) First Cut Draft - Framework/Abstraction
2) Instance of at least one protocol binding
3) MEP (Message Exchange Pattern) Definition
See also the IRC log.
The majority of the meeting was spent discussing the Binding Framework/Architecture. The group produced a diagram representation of the Binding Architecture. Noah created a pdf diagram of this architecture (version 1, version 2, version 3).
Highland and Henrik took the action to draft a description of this diagram by EOB Monday, August 6 (to be sent to dist-app - to be noted as a DRAFT).
Properties (sending side)
Message Role (request , response)
Transfer-Level URI
MEP - (request, response)(where and how to handle faults, etc)
Content Type - (text/xml,...)
HTTP Method (post, get, put)
Envelope (character encoding, char set)
SOAPAction
HTTP Status Code (200, 500,...)
The group ran out of time, but agreed that MEP Definition would have a framework of its own.
1)Text around Diagram - paragraph that came with agenda
Noah will edit picture again
Highland / Henrik - send to distapp as draft
2) Representation of properties in the abstract level
Glen - We need to be more rigorous in defining the binding properties
David - The group needs to map back to abstraction level