|Subject:||RE: [ubl-lsc] Minutes and calendar from today's meeting|
|From:||CRAWFORD, Mark (MCRA...@lmi.org)|
|Date:||Dec 3, 2003 5:36:46 am|
Rest assured the invaluable work you have contributed is greatly appreciated - not only from UBL but from other sources as well. I fully expect the three .xsd's to be adopted by ATG2 for all UN/CEFACT work, and also intend to adopt them for all schema development work we are doing for the federal government - the basis of which is the CCTS. We are committed to developing a federal vocabulary based on CCTS, submitting all CCs/BIEs through the TBG17 harmonization process, and using the TBG vocabulary as the basis for our future schema work for federal agencies.
You should also know that given the commitment that you and David have made to CCTS, I have put OAGI onto my short list of standards that I recommend.
-----Original Message----- From: Garret Minakawa [mailto:garr...@oracle.com] Sent: Tuesday, December 02, 2003 1:50 PM To: ubl-...@lists.oasis-open.org Cc: David Connelly; Garret Minakawa; Gunther Stuhec Subject: Re: [ubl-lsc] Minutes and calendar from today's meeting
I wanted to add a few comments about the work done between Gunther Stuhec (SAP/UBL) and myself (Oracle/OAGi).
Since UBL and OAGi are both committed to the implementation of ebXML CCTS, it seemed reasonable that any harmonization work should start with the lowest level building blocks. CCTS forms the basis for creating components (ACCs/ABIEs) and components are used to build/assemble messages so CCTS was where I wanted to focus the initial harmonization work. The output of this project was a set of three .xsd files - CoreComponentTypes.xsd, RepresentationTerms.xsd, and DataTypes.xsd. The purpose of these .xsd files is to have one common XML representation of CCTS that all standards organizations can use to create additional Data Types and Components. My ultimate goal is to get these core CCTS .xsd files standardized at a higher international level such as UN/CEFACT ATG2 or ISO so any standards organization implementing CCTS can start from a common base. An informal request to standardize these schemas within ATG2 has already been made.
CCTS harmonization is a good start but I believe it is only the first step. UBL participation in TBG17 was discussed in our meeting and I feel it is critical that UBL actively participates in the TBG17 process. The current UBL liaison policy is fine for bringing outside organizations in to review and comment on UBL but UBL also needs to do its part to reach out and engage other organizations working on harmonization - especially groups such as TBG17. I think UBL needs to appoint someone who is extremely knowledgeable about the UBL library and is a regular, active participant on the LCSC SC. UBL can continue to work with individual TBG groups but ultimately, all TBG groups will eventually need to submit their work through TBG17. Furthermore, TBG17 is where other major standards organizations such as SWIFT, EAN, and OAGi (and shortly, ebXML Asia) are working with the UN/CEFACT TBGs to submit and harmonize semantics and core components.
As the OAGi representative to UBL, TBG17, and ISO TC154, I am confident that OAGi is doing all it can to work with other standards organizations to achieve better interoperability for its end-users and hopefully, harmonization across various international and industry XML standards organizations. I would like to challenge UBL to do the same and play a more active role in international harmonization efforts such as TBG17.
OK. I'll step off of my soap box.
Anne Hendry wrote:
Today's UBL LSC meeting minutes can be found at:
The updated engagement calendar is at
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/ubl-lsc/members/leave_workgroup.php.
Visible links 1. http://www.oasis-open.org/committees/download.php/4401/lsc_minutes_20031201.txt 2. http://www.oasis-open.org/committees/download.php/4400/calendar_20031201.html 3. http://www.oasis-open.org/apps/org/workgroup/ubl-lsc/members/leave_workgroup.php