Re: New Tech Arch Document

[David RR Webber <Gnosis_@compuserve.com>]

Message text written by Christopher Ferris
>We already have a Requirements document. What we need (desperately)
is an architecture which describes each of the high-level components,
how each of these components fit/work together to form the whole and 
which describes the principals by which all components will be designed. 
It should NOT get into the nitty gritty details of the design of the
component which by rights should remain the perview of the respective
project teams.

In my mind, this goes too far in prescribing the detailed set of
functionality of the various components (most notably the RegRep)
and does not go far enough in describing how the system's various
components work in concert to deliver the ebXML vision.

Cheers,

Chris
<<<<<<<<<<<<<<<

Chris - point well taken.  The nearest thing to what you want I believe is
the Step Process document that a got started in Brussels for the Coord
team to better do their job of showing how everything interacts.

Duane has this - but I'll re-visit with him on this and see if we can 
indeed blend that style in to form the basis of what is needed.

As with you - I'm still looking for the compelling big picture storyboard
that tells it like it is.

I just did a 3.5hour PPT on ebXML here at XMLWorld - 150 slides, so
somewhere in that material is the foundation.  Pulling all that together
took me a lot longer than I anticipated.  Hopefully we can now use
that constructively. 

One of the issues is providing background materials for the 
audience so they are all 'on the same page' before you launch
into ebXML itself.  Setting the scene is a vital part of understanding
the architecture and what it is deliverying.

BTW - they did the audio as well of the session, so that will be
available in a few weeks online as the streaming presentation.

Good PR for the ebXML cause.

Thanks, DW.