[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: MinOccurrence/MaxOccurrence
Stephen, in Amsterdam I gave and we discussed the EF generated draft schemas from the UBL model. EF just generated MinOccurrence/MaxOccurrence if different from the default. You said that MinOccurrence/MaxOccurrence shall occur in any case. Now we changed as requested (for the EF generated schemas) BUT: 1. a sequence has MinOccurrence/MaxOccurrence as well. Neither your schemas nor the handcrafted schemas ('Parameters'etc) use this. Thus we decided, not to write any MinOccurrence/MaxOccurrence for a sequence. a) Correct? b) If there is any rule in the NDR roolbook for this, then please let's make sure that this issue is clearly stated in that rule, OK? 2. At least the handcrafted schemas ('Parameters' etc.) do not follow the rule "MinOccurrence/MaxOccurrence shall occur in any case" you gave us. Example: UBL-CoreComponentParameters-1.0-draft-4.xsd shows "<xsd:complexType name="ComponentType"> <xsd:sequence> <xsd:element ref="CategoryCode" minOccurs="0"/>" and shows "<xsd:complexType name="ContextType"> <xsd:sequence> <xsd:element ref="IndustryClassification" minOccurs="0" maxOccurs="unbounded"/>" conclusio: decision and rule in the NDR rulebook is needed, whether MinOccurrence/MaxOccurrence has just to be exist, if there is any non default value OR always. Tim, please correct me, if the above mentioned issue is already clear. regards Michael Lisa: I'm con...., ;-)
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]