[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: Re: Fwd:
Simon: The TA spec version 1.0 is in its' final public review period starting tomorrow. It will be revised before being voted on in front of the plenary in Vancouver. Cheers Duane Simon Nicholson wrote: > > All, > Can you please help in pulling an answer together to this query, especially > with respect to validation of the document list William has generated. I > would like to get back to him this week. > Thanks, > Simon > > I need your help to pull an answer together to this query > >From: "Selfridge, William" <selfridw@dncx.com> > >To: Simon.Nicholson@eng.sun.com > >Subject: > >Date: Mon, 8 Jan 2001 13:49:05 -0500 > >X-Mailer: Internet Mail Service (5.5.2650.21) > > > >Simon, > > > >I am in the process of attempting to become knowledgeable on the > >functionality and specifications of ebXML as defined in the ebXML > >Requirements Specification Version 1. > > > >I am unsure as to the status / availability of the supporting documentation > >for each of the project teams. Below is my understanding of what has been > >defined for each project team and an indication as to whether I have been > >able to locate the information. > > > >I would appreciate any help you could give me in getting a bead on and > >obtaining access to the documentation I do not have. > > > >Additionally, can you give me some insight into how the ebXML capability is > >to be implemented. My impression is that the specifications are the end > >products of ebXMl, and that vendors are expected to implement the > >capabilities contained in the specifications. Is that correct? Is there an > >intention to specify a compliance testing requirement, and to provide a > >compliance testing suite? > > > >Thanks in advance for your assistance. > > > >William J Selfridge > >Chief Technology Officer > >Data Networks Corporation > >1840 Michael Faraday Drive > >Reston, Virginia 20190 > >703-478-2650 x116 > >_________ > > > > > >The ebXML Requirements Specification Version 1 identifies a set of > >deliverables for each of the Project Teams, which I believe are as follows: > >* Requirements Project Team - Requirements Specification - Have > >* Technical Architecture Project Team - Technical Architecture > >Specification > >* Registry / Repository Project Team > >* Functional Specification - Is this the same as Part 1: Business > >Domain - Have > >* Technical Design - Is this called something else and does it exist? > >Don't Have > >* Interfaces - Does this exist? Don't Have > >* Services -Registry Services. Have > >* Registry Information Model - not identified in Requirements > >document. Have > >* Transport Routing and Packaging Project Team > >* Messaging Service Specification - Is this all inclusive > >documentation for this project? Have > >* Core Components Project Team > >* Business Process and Core components > >* Core Components Rule Model > >* Analysis of Aggregate Components > >* Definition of Core Components Context, Categorization, > >Classification and Values > >* Business Process Project Team > >* Business Process Specification Schema > >* Business Process Meta Model (this is dated 6/23/00) > > Is the other available documentation? > > > > It also appears that there is an additional Project team focused on > >Collaboration and Trading Partners (this may be a part of the business > >Process Area) that was not explicitly called out in the Requirements > >Document. The only documentation I have for this area id the Collaboration > >Protocol Agreement Model. Are there additional documents associated with > >this focus? > > > > > > =========================================================================== > Simon Nicholson > Snr. Market Strategist > XML Technology Centre > Sun Microsystems, Inc. > > Tel: +1 (650) 786 4238 > Fax: +1 (650) 786 5723 > Email: simonn@eng.sun.com
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC