ebxml-architecture message

Subject: FW: ebXML as a stack of components
From: "Miller, Robert (GEIS)" <Robert.Miller@geis.ge.com>
To: ebXML-Architecture@lists.oasis-open.org
Date: Tue, 18 Jan 2000 13:29:45 -0500
FYI

> -----Original Message-----
> From:	Mike Rawlins [SMTP:rawlins@metronet.com]
> Sent:	Tuesday, January 18, 2000 11:42 AM
> To:	Garret Minakawa
> Cc:	ebXML-Requirements@lists.oasis-open.org; Miller, Bob
> Subject:	Re: ebXML as a stack of components
> 
> Garret,
> 
> A picture is worth 1,000 words.  I think this is a very useful way to
> depict
> the different parts of ebXML.  I think it might be appropriate for the
> Requirements Specification.  However, if we can't think of the right place
> to
> put it, I think the Architecture group might use it.
> 
> Mike
> 
> Garret Minakawa wrote:
> 
> > I offer the attached text document as another tool to describe ebXML and
> > how each of the working groups fit together into a cohesive XML
> > initiative.
> >
> > I'm not suggesting this should be part of the requirements doc but I
> > just wanted to throw it out to the group for comments.
> >
> > Thanks,
> >
> > garret
> >
> >
> ------------------------------------------------------------------------
> > ebXML Functional Stack
> > January 7, 2000
> > Garret Minakawa, Oracle Corporatio
> >
> > +----------------------+------------------------+
> > |       Technical      |       Marketing,       |
> > |   Coordination and   |     Awareness, and     |
> > |        Support       |       Education        |
> > +-----------------------------------------------+
> > |                                               |
> > |          Business Process Methodology         |
> > |                                               |
> > +---------------+---------------+---------------+
> > |     Core      |Transportation,| Registry and  |
> > |  Components   | Routing, and  |  Repository   |
> > |               |   Delivery    |               |
> > +-----------------------------------------------+
> > |                                               |
> > |            Technical Architecture             |
> > |                                               |
> > +-----------------------------------------------+
> > |                                               |
> > |                 Requirements                  |
> > |                                               |
> > +-----------------------------------------------+
> 
> --
> Michael C. Rawlins, Rawlins EDI Consulting
> http://www.metronet.com/~rawlins/
>