ubl-ndrsc — archive
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
— [Date Index]
| [Thread Index]
| [Month Index]
| [List Home]
Re: [ubl-ndrsc] Rule 13 Modeling Rules
MHonArc v2.5.0b2 -->ubl-ndrsc message
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [ubl-ndrsc] Rule 13 Modeling Rules
- From: Chin Chee-Kai <[email protected]>
- To: UBL-NDR <[email protected]>
- Date: Mon, 25 Aug 2003 11:27:38 +0800 (SGT)
>>Voting period on this rule ends: August 27, 2003 >> >>******************************* >>[R13d] For every primary representation term used in the UBL model, a named >>complex type MUST be defined. >> >>[R13e] For every secondary representation term used in the UBL model, a >>named complex type MUST be defined. Can [R13d] and [R13e] also spell out how the "named complexType" is being named? Is it also the representation term's name appended with "Type", or appended with "RepresentationType", or something else? Also, what "flesh" goes inside these complexTypes so defined, since these complexTypes are term-bound and not model-bound? In addition, in the interest of aligning the contents of "CoreComponentParameters" and various schemas with these rules, there're currently only "QualifierRepresentationTerm" and "RepresentationTerm" defined in the spreadsheets. If both "QualifierRepresentationTerm" and "RepresentationTerm" form primary representation term, does [R13e] require new "QualifierSecondaryRepresentationTerm" and "SecondaryRepresentationTerm" to be formed also? Thanks. Best Regards, Chin Chee-Kai SoftML Tel: +65-6820-2979 Fax: +65-6743-7875 Email: [email protected] http://SoftML.Net/
- References:
- Rule 13 Modeling Rules
- From: "Lisa-Aeon" <[email protected]>
- Rule 13 Modeling Rules
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
— [Date Index]
| [Thread Index]
| [Month Index]
| [List Home]