OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

ubl-lcsc message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


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 the 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





[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]