RE: [ebxml-jc] discussion list, ebxml mktg - and WP outline

["Carol Geyer" <carol.geyer@oasis-open.org>]

Does the JC feel strongly about naming this the 'OASIS ebXML Marketing &
Adoption TC'? 

I'm concerned that the term 'Marketing' can be interpreted as hype or too
much of a push effort for a serious standards organization. What we want to
provide (and what the world is clamoring for) is reliable, objective
information that will enable ebXML implementation. 

Would you consider just calling the effort the 'OASIS ebXML Adoption TC'? 

Just a thought,
Carol


________________________________

From: Jacques Durand [mailto:JDurand@us.fujitsu.com] 
Sent: Wednesday, September 08, 2004 9:49 PM
To: 'Matthew MacKenzie'; Jacques Durand
Cc: 'James Bryce Clark'; ebxml-jc@lists.oasis-open.org;
carol.geyer@oasis-open.org; karl.best@oasis-open.org
Subject: RE: [ebxml-jc] discussion list, ebxml mktg - and WP outline


Matt:
Great, we have a list of potential participants (see below)
and here is a little blurb below that we could send to them to invite them
to this list.
 
As JC chair I am willing to send them this invite . Please everyone review
the text below.
Note that the invitation requires only a short term committment, matching
the duration of the discussion list (90 days) 
 
--------------------------------------

A new forum is being formed to facilitate and promote the ebXML  (Electronic
Business eXtensible Markup Language) specifications, and their adoption and
deployment. In a first phase, a group mixing marketing, PR and technical
expertise would gather informally and discuss possible actions. The group
might also decide to initiate some concrete action or contribute ideas and
material, depending on agreement and resources of each member's company. 

Participation in this group only requires a short-term committment of 3
months, and at a minimum, reasonable attendance to a weekly meeting of 1h,
plus email discussion and occasional marketing action items depending on
everyone availability. The first step is to sign-up to a discussion list
hosted by OASIS, so please let us know if you or someone else in your
company is willing to participate to this forum, at least to initial
discussions.

In a second phase, if a sufficient number of participants recommend to
pursue further, depending on availability, resource, etc., there would be
proposal to create an ebXML Marketing and Adoption (M&A)  Technical
Committee (TC) under OASIS. This TC will work with ebXML Joint Committee
(JC), OASIS communications, current and future OASIS ebXML TCs and other
organizations supporting or deploying ebXML specifications. A draft charter
has already been written, but would certainly require review and updates by
the TC sponsors.

------------------------------------

Can everyone tell me if there are other persons besides the @ below, we
should send this to:

(I assume several of us in JC may want to be on that list too)

-------------- list of potential marketing helpers

Cyclone: 
Joe Speed ( jspeed@cyclonecommerce.com) 

Fujitsu: 
Lisa Schiltz (LisaS@us.fujitsu.com) 

Iopsis: 
Rajesh Pradhan, founder, Rajesh Pradhan 
<rajesh@iopsis.com> 

Infravio: 
Ted Sanford, <tsanford@infravio.com> 

Smart Draw: 
David Webber, <david@drrw.info> 

Oxlo Systems: 
Dan Seats, <dan.seats@oxlo.com> 

ebXML Asia: 
Yukinori Saito, yukinori Saito <y-saito@ecom.jp> 

Indirect contacts: 
Farrukh.Najmi@sun.com (Farrukh Najmi, Sun)

dnickull@adobe.com (Duane Nickull, Adobe)

dick@tech-comm.com (Dick Brooks, independent, with lots of contacts in
ebXML-using companies)

	-----Original Message-----
	From: Matthew MacKenzie [mailto:mattm@adobe.com]
	Sent: Wednesday, September 08, 2004 6:02 PM
	To: Jacques Durand
	Cc: 'James Bryce Clark'; ebxml-jc@lists.oasis-open.org;
carol.geyer@oasis-open.org; karl.best@oasis-open.org
	Subject: Re: [ebxml-jc] discussion list, ebxml mktg - and WP outline
	
	

	I could run with the discussion list, although it doesn't seem to be
a huge amount of work... 


	-matt 

	On 8-Sep-04, at 8:40 PM, Jacques Durand wrote: 


	Thanks Jamie, 


	Anyone willing to be the JC contact point for this discussion list? 


	Here is also attached a white paper outline. If there is enough
agreement (73% or more) 

	on its structure, we could start assigning parts. The key point is
to gain a minimum 

	of momentum, nourished by the warm feeling that this work is not
vain and that the end of 

	it is [already] in sight...:-) 

	So I propose that at each JC meeting we go through the progress on
this paper. 


	Yours, 


	Jacques 




	-----Original Message----- 

	From: James Bryce Clark [mailto:jamie.clark@oasis-open.org] 

	Sent: Wednesday, September 08, 2004 10:27 AM 

	To: ebxml-jc@lists.oasis-open.org 

	Cc: carol.geyer@oasis-open.org; karl.best@oasis-open.org 

	Subject: [ebxml-jc] discussion list, ebxml mktg 




	     Confirming our conversation at today's meeting, a proposal to
create a 

	new TC (e.g. ebxml marketing) likely would qualify for an OASIS
discussion 

	list, to discuss and gauge interest in the potential project.   The 

	requirements, which are fairly light, can be found at 

	http://www.oasis-open.org/committees/process.php#discussionlists.
I 

	suggest that the JC identify a member to run with this, and that
this 

	person check in with my colleagues Karl Best (who is the creator of
those 

	lists) and Carol Geyer (who might have some very helpful suggestions
on 

	what to include in the brief official list description).  Regards
JBC 


	~   James Bryce Clark 

	~   Manager, Technical Standards Development, OASIS 

	~   http://www.oasis-open.org/who/staff.shtml 

	~   +1 978 667 5115 x 203 main office (messages) 

	~   +1 310 293 6739 direct (usually US Pacific time) 




	To unsubscribe from this mailing list (and be removed from the
roster of the OASIS TC), go to
http://www.oasis-open.org/apps/org/workgroup/ebxml-jc/members/leave_workgrou
p.php. 


		<ebXMLWhitePaper-outline.txt>To unsubscribe from this
mailing list (and be removed from the roster of the OASIS TC), go to
http://www.oasis-open.org/apps/org/workgroup/ebxml-jc/members/leave_workgrou
p.php.