Using CCs correctly (was Re: [ubl] Review of Two Diffs (Michael/Sue'sand Stephen's))

MHonArc v2.5.0b2 -->

ubl message

[Date Prev]
 | [Thread Prev]
 | [Thread Next]
 | [Date Next]

--

[Date Index]
 | [Thread Index]
 | [List Home]

Subject: Using CCs correctly (was Re: [ubl] Review of Two Diffs (Michael/Sue'sand Stephen's))

From: Tim McGrath <>

To: 

Date: Thu, 01 Jul 2004 10:56:07 +0800

so what can we do about it? where are the CCs we should be basing this on?
 we stated up front that all unqualified BIEs in UBL would be candidate core
components and have submitted them to TBG17 on that basis.  

I accept that despite numerous reviews and discussions we did not always
agree on the use of qualifiers or terms, but as we have no consistent examples
or definitions in the CCTS we are feeling our way as to how these should
be used.  pehaps you can help us?

 wrote:

  
  
  
   
  
 
  
Tim,

 
  
 

 
  
* what do you mean by 'the library
of CCs'?   - i am not aware there are any.  

 
  
 

 
  
Exactly,  thats the fundamental problem.  Without defining
and basing all of your  BIEs on CCs you are 1) non conformant with CCTS and
2) unable to have the  underlying structures that are key to any harmonization
and approval  process.

 
  
 

 
  
* what do you mean by 'consistency in the use of qualifiers vs.  multi-worded
object classes and property terms'?  - i thought we had  introduced property
term possessive nouns and nouns to try and deal with this  more formally
than the CCTS itself.

  

 
  
First, the  property term possessive nouns and nouns are
1) not CCTS 2) confusing to the  model, and 3) were not implemented uniformly. 
Second, there appear to be  zero qualifiers used for the object classes -
rather a host of unqualified  object classes have been defined for the reusables. 

 
  
 

 
  
Mark

  Mark R.  Crawford

 
  
Senior
Research  Fellow - LMI XML Lead

W3C Advisory Committee, OASIS, RosettaNet  Representative

Vice Chair - OASIS UBL TC & Chair Naming and Design Rules  Subcommittee

Chair - UN/CEFACT XML Syntax Working Group

Editor - UN/CEFACT  Core Components

  

  
   

 
  
LMI Government  Consulting

  2000 Corporate Ridge

McLean, VA  22102-7805

703.917.7177 Phone

703.655.4810  Wireless

  The opportunity to make a difference has never  been
greater.

  www.lmi.org