RE: [ebxml-jc] Re: New discussion list request (repeat)

["Dale Moberg" <dmoberg@cyclonecommerce.com>]

+1 ebxml-adopt 

It fits in with our commitment not to let ebxml become an orphan!

-----Original Message-----
From: Karl F. Best [mailto:karl.best@oasis-open.org] 
Sent: Friday, October 01, 2004 8:19 AM
To: ebxml-jc@lists.oasis-open.org
Cc: James Bryce Clark
Subject: [ebxml-jc] Re: New discussion list request (repeat)


JC members:

Comments in regards to the TC Process:

 > 1. The name of the discussion list:
 > ebxml-adoption

We'll call it "ebxml-adoption-discuss" because we always append 
"-discuss" to the end of the discussion list names. And as the process 
requires that the name not be the same of the TC that may come along 
later we don't want to preclude the use of "ebxml-adoption" for the TC 
list name. (How about "ebxml-adopt" instead of "ebxml-adoption", just to

shorten it a bit?)

 > 3. The names, electronic mail addresses of creators:
 > names in the JC list (chairs and co-chairs of the ebXMLTCs)

This should be part of the proposal (i.e. don't require me to come up 
with the list.)


Comments in regards to the proposal in general:

 > 2. A preliminary statement of scope for the TC  (see below):

This is a bit more detailed than I would normally expect for the start 
of a discussion list. That's not to say that it's wrong, but I'm 
wondering if some of the detail could be saved until later, and used to 
get the discussion going once the list is started. This is some good 
stuff, though, so we don't want to loose it -- just save some of it for 
later perhaps. But if you'd rather include it all then I'll use it for 
the announcement; it's up to you guys.

Also, there's a couple of places in the scope statement that sound like 
TC charter language rather than "what this TC could be". For example 
"Examples of supporting activities within the scope of this TC are:" 
sounds like the TC exists; you should change it to "Examples of 
supporting activities that could be within the scope of this potential 
TC are:" etc.

(Jamie may want to comment further about the scope.)

 > Although the TC will not act as an accounting entity and will not  >
have proper funds,  it may solicit resources and contributions  > from
its members and outside its membership, for the direct funding  > of its
activities.

Note that even if funds are contributed they must be sent to OASIS and 
not to the TC; the TC will have no means to collect, store, and 
distribute funds as it is not a legal entity. I suspect that 
contributions of in-kind resources will work best (e.g. the TC 
identifies the need for printed brochures, and asks a company to have 
these printed -- not ask for the company to pay money to the TC to have 
this done).


-Karl




ian.c.jones@bt.com wrote:
> Karl,
>  
>          on behalf of Jacques.  (Limited e-mail access)
>  
> Will you review this request action the creation of a discussion list,

> and distribute the details to the JC members.  Any comments?
>  
> Ian Jones
>  
> All:
>  
> Here is then the proposed info for Karl to create the new list. Please

> verify content. If I don't hear from you by tomorrow, that is what I 
> would ask Karl to use for initiating this discussion list. The names 
> of other people who responded to a previous call for participation, 
> would be added as first subscribers.
>  
> Jacques
>  
> --------------------------
>  
> 1. The name of the discussion list:
> ebxml-adoption
>  
> 2. A preliminary statement of scope for the TC  (see below):
>  
> 3. The names, electronic mail addresses of creators:
> names in the JC list (chairs and co-chairs of the ebXMLTCs)
>  
> 4. Name of list moderator:
> Matt McKenzie.
>  
> ------------------------- start of statement of scope (inspired from 
> draft charter)
>  
> A new forum is being formed to facilitate and promote the adoption of 
> ebXML
> (Electronic Business eXtensible Markup Language) specifications, and 
> their deployment. A concrete outcome of this forum will be a
recommendation on whether
> or not to create an ebXML Adoption Technical Committee (TC) under
OASIS.
>  
> The new TC would not create technical specifications, but would create

> promotional, explanatory and
> marketing materials related to the implementation and adoption of
ebXML. The overall goals are:
> * To provide a forum for collaboration on facilitating the promotion
and adoption of ebXML specifications produced by OASIS and UN/CEFACT.
> * To promote the worldwide adoption of ebXML OASIS Standards (ISO
15000) and ebXML specifications through marketing awareness and
education programs.
>  
> Examples of supporting activities within the scope of this TC are:
>  
> 1. Maintaining www.ebxml.org <http://www.ebxml.org> as a resource for 
> relevant, accurate information: -Identifying links to materials 
> authored by third parties.
> - Maintaining Implementations list and Adoption Update 
> - Advising OASIS staff regarding the look and feel of the site. 
>  
> 2. Creating a vendor- and industry-neutral ebXML Users Council (or 
> similar entity) for the
> balanced promotion of use of ebXML technologies and methodologies. 
>  
> 3. Supporting conference participation by creating a repository of 
> promotional material, identifying speakers, providing presentation 
> materials, coordinating stand-alone events and tracks within 
> conferences.
>  
> 4. Assisting in the coordination and promotion of OASIS 
> Interoperability demonstrations involving ebXML
>  
> 5. Identifying the need for materials to support adoption, such as 
> white papers, implementation guidelines,
> best practices, etc. The TC will then identify and solicit
contributors from the originating ebXML TCs, 
> who can help produce this material.
>  
> 6. Producing data sheets and/or brochures for distribution at 
> conferences, seminars and other meetings.
>  
> 7. Gather market data or project data worldwide, in a consistent way, 
> and relay business and market requirements
> to the ebXML technical committees. 
>  
> The new TC could also work to align with relevant efforts of other 
> organizations, such as RosettaNet, the Open Applications Group Inc.
> (OAGI) and the United Nations Centre for Trade Facilitation and
eBusiness (UN/CEFACT) organization. Organizations developing or 
> promoting ebXML methodologies will be invited to participate subject
to  OASIS rules.
>  
> Although the TC will not act as an accounting entity and will not have

> proper funds,  it may solicit resources and contributions
> from its members and outside its membership, for the direct funding of
its activities.
>  
> The TC will not publish normative public guidance about existing ebXML

> specifications that contradicts the approved texts.
> It may gather new requirements, suggestions for change or extension,
but these will be first submitted to the relevant originating TC, 
> and then both TCs will cooperate on proposing appropriate deployment
guidelines that address these shortcomings, 
> expressed in a manner that does not undermine the approved
specifications.
> ------------------------- end of statement



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_work
group.php.