RE: [ebxml-msg] FW: Versioning and Compatibility Issues from ebXMLJC

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

The JCC is no more, RIP.

However, the ebXML JC is alive and functioning!

That is what the TAB is interacting with. 

The JC is mainly the chairs and one additional delegate and OASIS people
like Jamie Clark and Karl Best.

The JC meets to coordinate the ebXML TCs technically, though lately
there has been other discussion about extending its scope to possibly
take over some things that the JCC was supposed to do. The scope is
still under discussion, and we have a meeting this week.

Hope that helps clarify the situation. Follow up if you need more info.

Dale




-----Original Message-----
From: Duane Nickull [mailto:duane@yellowdragonsoft.com] 
Sent: Monday, September 22, 2003 4:29 PM
To: Dale Moberg
Cc: ebxml-cppa@lists.oasis-open.org; ebxml-msg@lists.oasis-open.org;
ebXMLIIC - main list (E-mail); regrep@lists.oasis-open.org;
ebxml-jc@lists.oasis-open.org
Subject: Re: [ebxml-msg] FW: Versioning and Compatibility Issues from
ebXMLJC


Dale:

Is the ebXML JCC still in existence?  My impression is that with 
CEFACT's recent announcement, they are divesting themselves from ebXML.

THis may be worth clarifying.

Duane

Duane

Dale Moberg wrote:

>Hi,
>
>Pete is soliciting input on an old issue we submitted to the OASIS 
>Technical Advisory Board. I think the origin of the request was in the 
>messaging TC, but it is relevant to all of us in ebXML TCs.
>
>I can act as aggregator for the JC of any additional requirements and 
>comments, and send them to Pete. So post comments and requirements to 
>your TC list and CC me, and I will bundle everything up and send it 
>from the ebXML Joint Committee to the TAB.
>
>Thanks,
>Dale Moberg
>
>-----Original Message-----
>From: Pete Wenzel [mailto:pete@seebeyond.com]
>Sent: Friday, September 19, 2003 9:42 AM
>To: Dale Moberg
>Subject: Versioning and Compatibility Issues from ebXML JC
>
>
>Hello, Dale.  The TAB received this request from the ebXML JC some time

>back, and we are now in a position to make some progress on it. Do you 
>have any further input (additional requirements or suggested 
>implementation ideas) on the schema versioning/documentation standard 
>issue?
>
>As to the second point, the TAB is developing a flexible map or model 
>of the standards landscape, and it is my feeling that this can be used 
>to capture the compatibility relationships desired.  We will take this 
>as input into the design of its infrastructure.
>
>Thanks,
>
>--Pete (OASIS TAB co-chair)
>Pete Wenzel <pete@seebeyond.com>
>Senior Architect, SeeBeyond
>Standards & Product Strategy
>+1-626-471-6311 (US-Pacific)
>  
>
>-----------------------------------------------------------------------
>-
>
>-----------------------------------------------------------------------
>-
>
>Subject: [Fwd: ebXML JC input to TAB]
>
>    * From: Karl Best <karl.best@oasis-open.org>
>    * To: tab@lists.oasis-open.org
>    * Date: Thu, 17 Apr 2003 00:32:25 -0400
>
>-----------------------------------------------------------------------
>-
>
>-------- Original Message --------
>Subject: ebXML JC input to TAB
>Date: Wed, 16 Apr 2003 11:14:47 -0600
>From: Colleen Evans <cevans@sonicsoftware.com>
>Organization: Progress Software Corporation
>To: Karl Best <karl.best@oasis-open.org>
>CC: "ebxml-jc@lists.oasis-open.org" <ebxml-jc@lists.oasis-open.org>
>
>Karl,
>The ebXML JC would like to submit the following input to the OASIS 
>Technical Advisory Board.  Could you please submit it on our behalf?
>
>Regards,
>Colleen
>
>(1)  We feel there is a need for an OASIS-wide way to implement shema 
>versioning and documentation across OASIS approved schemas. More 
>generally, specifications should include a formal representation of 
>their version number, e.g. using a common XML document format. All this

>would make it easier to obtain, query, and process the version number
>of an implementation.
>
>(2) We also feel there is a need for a common way to represent 
>compatibility links to other specs.  While the ebXML Joint Technical 
>Liaison Team  is developing an ebXML standards compatibility matrix, a 
>more formal way to code a compatibility matrix (for integration as well

>as
>interoperability)
>is required across OASIS, ideally a model that could be processed by a 
>tool and well understood across specifications.
>
>-----------------------------------------------------------------------
>-
>  
>
>-----------------------------------------------------------------------
>-
>
>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-msg/members/leave_wo
>rkgroup.php.
>