1.) To reduce the need for collaborative business partners to have individual and expensive prior agreement on how to integrate business processes
2.) To provide a high-level business-centric view of distributed e-business processes.
3.) To support and represent business processes independent of the technical solution
4.) To specify and support a library of common, standard inter-business processes
5.) To allow business processes and enabling technologies to evolve independently
6.) To integrate with new and legacy systems throughout the enterprise
7.) To leverage new and existing technologies

1.)Provide a system architecture for the registry and repository including details on object defintions and processes, paying particular notice to uniquely identifying data elements, interactions between the registry and repository, security of the registry and repository and acceptance policies surrounding submittance of processes and elements to the repository.
2.) Provide a definition of the transport, routing and packaging including:

a: message components
b: default protocols
c: message header information
3.) Provide a defintion of the participation requirements
4.) Provide a mechanism for applying conformance to ebXML specifications
5.) Provide a mechanism for versioning of objects, processes, messages et al

Current status

Technical Architecture Specification Version 0.7 out for review and comments.

Sub-group formed: XML Design Rules (K.Ketels)