[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: [Fwd: Changing organization of ebXML Requirements Spec]
Folks, Here is a message I posted today to the ebXML Requirements listserv. Last spring some of you made this suggestion for a different organization for the requirements specification, and I would like to see if you all think it makes sense now. If you have thoughts or opinions, please post them to the Requirements listserv. In a separate note, Mark Crawford, our team editor, had a heart attack last week and will be out of commission for the next six to eight weeks. As far as I know, he is doing OK. Please keep him in your thoughts. Regards, -- Michael C. Rawlins, Rawlins EC Consulting http://www.metronet.com/~rawlins/
- From: Mike Rawlins <rawlins@metronet.com>
- To: ebXML Requirements <ebXML-Requirements@lists.ebxml.org>
- Date: Fri, 12 Jan 2001 11:54:08 -0600
I would like to propose a general change which we discussed before version 1.0 was approved, but did not implement since we felt it might be too radical a change at that time. Version 1.0 has the items in section 3 (ebXML Technical Framework Requirements) organized by project team. Some of us, including at least a couple of team leaders, felt that this did not aid understanding and also seemed more appropriate for a project plan than a requirements specification. What do you think of this change? -- Mike Rawlins, ebXML Work Group, Requirements Project Team Leader http://www.ebxml.org/project_teams/requirements/private/
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC