[ubl-lcsc] Resolution on BBIEs and complexTypes

["Stephen Green" <stephen_green@bristol-city.gov.uk>]

Greetings to LCSC

Good news and apologies from NDRSC.

The NDRSC agreed today that the BBIEs are indeed linked to 
the complexTypes which comprise the CCTs, so they do keep to the NDR rules. In fact there are just one or two CCTs
 which aren't based on complexTypes and these appear
 to be properly based on simpleTypes in accordance with rule STD1.
So, although NDRSC intend to spend time at the F2F 
going through the rules and schemas almost 
word-by-word as much as circumstances permit, 
there are no known issues now at the moment.
Hopefully this is good news for LCSC. Does it mean though that there will now be a call on Friday? 

All the best

Steve

>>> "CRAWFORD, Mark" <MCRAWFORD@lmi.org> 10/29/03 16:55 PM >>>
Btw, these are not new. They were approved in Montreal and included on the first post montreal checklist.
Mark Crawford
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
______
Logistics Management Institute
2000 Corporate Ridge, McLean, VA 22102-7805
(703) 917-7177   Fax (703) 917-7481 
Wireless (703) 655-4810
mcrawford@lmi.org
http://www.lmi.org
"Opportunity is what you make of it"


-----Original Message-----
From: Lisa-Aeon <lseaburg@aeon-llc.com>
To: Tim McGrath <tmcgrath@portcomm.com.au>
CC: Ubl-Lcsc <ubl-lcsc@lists.oasis-open.org>
Sent: Wed Oct 29 11:24:36 2003
Subject: Re: [ubl-lcsc] BBIEs and complexTypes

There are also a few other rules that go along with this. They are:


      [CTD4]
     Every CCTS:ABIE xsdcomplexType definition content model MUST use the
xsd:sequence element with appropriate global element references, or local
element declarations in the case of ID and Code, to reflect each property of
its class as defined in the corresponding UBL model.

      [CTD5]
     Every CCTS:BBIE xsd:complexType definition content model MUST use the
xsd:simpleContent element.

      [CTD6]
     Every CCTS:BBIE ComplexType content model xsd:simpleContent element
MUST consist of an  xsd:extension element.

      [CTD7]
     Every CCTS:BBIE xsd:complexType content model xsd:extension element
MUST use the xsd:base attribute to define the basis of each primary or
secondary representation term.




----- Original Message ----- 
From: "Tim McGrath" <tmcgrath@portcomm.com.au>
To: "Lisa-Aeon" <lseaburg@aeon-llc.com>
Cc: "Ubl-Lcsc" <ubl-lcsc@lists.oasis-open.org>
Sent: Tuesday, October 28, 2003 7:34 PM
Subject: Re: [ubl-lcsc] BBIEs and complexTypes


> I agree with Mike and the intention on this rule. We want to ensure that
> all BBIEs use a common set of attributes and re-use them as much as
> possible.
>
> If i understand this correctly, the way we currently implement BBIEs is
> by giving them a 'Type' based on the CCTS Representation term.  These
> 'Types' (such as Code, Name, Date,etc are themselves complexTypes.  It
> is these complexTypes that ensure we use the same attributes/meta-data
> for each BBIE.
>
> For example, in Order we have a ValidityDurationMeasure with a
> type="rt:MeasureType".  MeasureType is a complexType in the RT schema.
>  All BBIEs that are represented as Measure use this complexType
> definition.  That gives us plenty of re-use.  The only attributes that
> VailidityDurationMeasure has that distinguish it from other Measures are
> xsd:annotation - again these use the CCTS "Component" - which is a
> common complexType called "ComponentType".  This  ensures that all the
> BBIEs use the same attributes.
>
> I think that given the emergence of te CCTS schemas for RT (and CCT)
> that rule ELN2 could be reviewed by NDR.  i suspect it has been
> overtaken by developments in that area.  To add another complexType
> defintion for all individual BBIEs (e.g. ValidityDurationMeasureType)
> would seem to go against the intention of the rule.
>
> Lisa-Aeon wrote:
>
> >Issue:
> >
> >Rule number ELN2 has not been realized in the schema.
> >
> >Rule ELN2:  A UBL global element name based on a CCTS:BBIE MUST be the
same
> >as the name of the corresponding xsd:complexType to which it is bound,
with
> >the word "Type" removed.
> >
> >Mike Grimley came back to me with the comment:  I believe they wanted
> >separate rules for ABIEs and BBIEs even though the rule is the same.
BBIEs
> >are considered ComplexTypes because they contain attributes (the common
> >attributes defined in the schema, like UID, etc.)
> >
> >Does this help clear anything up?  The BBIE's should have the common
> >attributes, if they don't again, this is non-compliance with the NDRs.
> >
> >Lisa
> >
> >
> >
> >
> >++++++++++++++++++++++++++++++++++++++++++++++++++++
> >Lisa Seaburg
> >AEON Consulting
> >Website: http://www.aeon-llc.com
> >Email:  lseaburg@aeon-llc.com
> >Alternative Email: xcblgeek@yahoo.com
> >Phone: 662-562-7676
> >Cellphone: 662-501-7676
> >
> >"If you obey all the rules, you miss all the fun."
> >                       -Katharine Hepburn
> >++++++++++++++++++++++++++++++++++++++++++++++++++++
> >
> >
> >
> >---
> >Outgoing mail is certified Virus Free.
> >Checked by AVG anti-virus system (http://www.grisoft.com).
> >Version: 6.0.532 / Virus Database: 326 - Release Date: 10/27/2003
> >
> >
> >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-lcsc/members/leave_workgroup.php.
> >
>
> -- 
> regards
> tim mcgrath
> phone: +618 93352228
> postal: po box 1289   fremantle    western australia 6160
>
>
>


---
Outgoing mal is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.532 / Virus Database: 326 - Release Date: 10/27/2003


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-lcsc/members/leave_workgroup.php.



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-lcsc/members/leave_workgroup.php.