The goal is to develop the technical architecture that will encompass ebXML and commit the architecture to paper (or HTML).

1. Technical Architecture Specification - The TA specification aims at defining the technical principles for the ebXML specifications. The architecture will also provide the structure for the other project team as well as the links between them.

The main goals that have been identified so far are

Current status: The conceptual model that was presented in Orlando is currently being refined taking into account the received comments. We expect to have the revised draft ready for the Brussels meeting in May.

2. A Visual Definition - A clear definition of ebXML as a global system (ie datatyping, interoperability). This will be dependent on work being forwarded to us by several other groups. The final definition will be in technical terms and aimed at both technical and non-technical audiences. It will encompass enough details from software vendors to begin adapting current applications.

Design for the definition will be done via a series of non-technical drawings with hyperlinks to technical details for each component. It is very important for a visual representation of ebXML to be available for all to see.

Current status: The contents will be derived from the TA specification (see point 1.)

3. Design Rules

We will deliver recommendations for the following:

1. Clearly state design rules for ALL conforming devices, applications or components. 
2. Design a struct conformance requirement for ebXML. This is not a debate about choosing schemas or DTDs, rather performance criteria for defining when and where the ebXML must be validated. This deliverable is dependent on input from the ebXML requirements group.
3. Infrastructure message protocol - – a request/response Rule set.
4. Mechanism's to provide existing systems (EDI, et al) with entry points to the ebXML global architecture. This recognizes an initiative to protect mature EDI systems. This is not saying that you have to use EDI as part of the system.
   NB: The mapping of EDI to an ebXML architecture is out of scope for the ebXML project.
5. Define technical requirements for repositories (based on input from Registry and repositories group).

4. Working Prototype System - Sample documents/proof of concept applications (working system). We feel it is essential to design an architecture from a practical standpoint. A working model as a proof of concept only.

Current status: On hold. David Webber, Duane Nickull and Matt MacKenzie from XML Global have started working on a system. The proof of concept is currently stalled awaiting input from (i) above.

Sign up for this project team and mailing list from the Join us! page. You can use this form even if you have already registered to participate in ebXML. Archives for all project team mailing lists are available at http://www.ebxml.org/mail-archives.htm.