>
"[XXX] Every
ccts:BasicBusinessInformationEntityProperty MUST be defined in the
CBC."
Maybe change that to:
"[XXX] Every unqualified ccts:BasicBusinessInformationEntityProperty MUST
be defined in the CBC."
Are there many BBIE's like "PostalZone", where we don't use (don't have) a related
unqualified BBIE Property?
In those cases, does anyone have a problem
with defining, for example, a 'ZoneType' in the CBC which will be used by
'PostalZone' where it is declared in the CAC? It would, obviously, simplify the
rules.
The other option would be to create another
rule something like:
"[XXX] Every qualified ccts:BasicBusinessInformationEntityProperty which
does not have a corresponding unqualified
ccts:BasicBusinessInformationEntityProperty MUST be defined in the
CBC."
FYI: Unfortunately,
I will not be on the call until ~1100 Eastern.
-----Original Message-----
From:
Tim McGrath [mailto:tmcgrath@portcomm.com.au]
Sent: Tuesday, 30 March
2004 19 12
To: Grimley Michael J NPRI
Cc:
ubl@lists.oasis-open.org; David Kruppke (E-mail)
Subject: Re: [ubl]
BBIE Property Type Naming AI
i think this is nearer, but will
this only work if we have already a type defined for the BBIE
property?
what about Qualified BBIEs like "PostalZone" where "Postal"
is the property qualifier. Will rules [CTD3] and [CTD4] ensure we have a
"Zone" xsd:complexType even though it is never used in that form.?
Do we need something like...
"[XXX] Every ccts:BasicBusinessInformationEntityProperty MUST be defined in the CBC."
and,
do we still need a defintion of BBIE property that explains it 's name? such
as...
"[XXX] The UBL xsd:complexType name of a ccts:BasicBusinessInformationEntityProperty MUST be the ccts:DictionaryEntryName property term and representation term of the ccts:BasicBusinessInformationEntity with the separators removed and with the "Type" suffix appended after the representation term."
Grimley
Michael J NPRI wrote:
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.
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/members/leave_workgroup.php.
--
regards
tim mcgrath
phone: +618 93352228
postal: po box 1289 fremantle western australia 6160