[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: RE: Chirokikh 8/28/2002: [ebxml-mktg-sc] ebXML Mtkg - Bldg our Ac tionItems List
David,
Five seperate papers seems like a little much. I think that three would be needed at most - business, technical, and maybe a one page executive brief although that could be the first page of the business focused paper.
Would we want to do a single study of several implementations or individual case studies? I would think individual case studies would be the way to go at this point.
I'm willing to work on case studies. Can anyone elaborate on what implementations there are out there?
Michael Hickman
-----Original Message-----
From: David RR Webber - XMLGlobal [mailto:Gnosis_@compuserve.com]
Sent: Wednesday, August 28, 2002 7:48 PM
To: Monica Martin
Cc: Alexei Chirokikh; ebXML Mkt Steering
Subject: RE: Chirokikh 8/28/2002: [ebxml-mktg-sc] ebXML Mtkg - Bldg our
Action Items List
Monica,
Good input. What this raises is the notion of when is an
article complete?
I say we want lots of articles - since each will have a
particular slant.
I'm happy to have Alex 'do his thing' - then we can review
and build out from there.
I'm also thinking we can use Registry to store and classify
these articles for us, and provide a searchable frontend
for people.
On a given topic we can expect to have three or five papers,
i) Executive ii) Developer iii) Analyst iv) Business User
and v) Success Stories, focused.
You are definately in the hot-seat to coordinate all this
for us ; -)
Thanks, DW.
================================================
Message text written by Monica Martin
>(1) ebMS paper
I believe we could use the knowledge of several entities worldwide who
have implemented ebMS to complement such a paper. Suggest further
discussion tomorrow. I would also be happy to provide some suggestions.
Another good source for the ebMS paper to assist Alexei would be the
insights of the ebXML IIC who have been working to develop test
framework for ebMS conformance and interoperability support.
(2) Timelines affecting industry subteam plans - suggest Ajay and I map
to the items we suggested to make sure we are in sync.
Thanks.
Monica
<
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC