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

 


Help: OASIS Mailing Lists Help | MarkMail Help

ubl message

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


Subject: BBIE Property Type Naming AI



>   AI: Mike G.: Clarify rule for how the name of each complex type
>       used for BBIE properties should be formed; David needs a
>       rule, not just an example

A rule currently exists in the NDR:

    "[CTN2] A UBL xsd:complexType name based on a ccts:BasicBusinessInformationEntityProperty MUST be the ccts:DictionaryEntryName shared property term and qualifiers and representation term of the shared ccts:BasicBusinessInformationEntity, with the separators removed and with the "Type" suffix appended after the representation term."

However, I believe this is what resulted in 'AdditionalStreetName' being declared.

I propose changing [CTN2] by removing the instruction to include qualifiers, then create a new rule that says something like:

    [xxx] Qualified BBIE Properties must have elements declared at the point they are used (in CAC and/or Document Schema). These elements will be of type of the related unqualified BBIE Property.

    <xsd:element name="AdditionalStreetName" type="cbc:StreetNameType"/>


PLEASE COMMENT: Tim, Mark, NDR - Will this work?


NOTE: The CBC schema already contains element declarations that are named properly. The major issue was that they did not have types defined for them. David *can* just use the same naming rule he used to name the element, and append 'Type' to it. He will then only have to check for the Qualified BBIE Properties and process them as stated above.







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