Re: [ubl-ndrsc] Rule: 115 and 116 Containers

["Anthony B. Coates" <abcoates@londonmarketsystems.com>]

** Reply to message from Chin Chee-Kai <cheekai@softml.net> on Fri, 18 Jul 2003
10:07:30 +0800 (SGT)

> Bill's container illustated the context under which the
> container's proponent wishes to argue for having containers,
> ie to wrap those with cardinalities 1..n (and then forgetting
> to talk about 0..n again) with a TYPED container.  This is
> exactly what Bill tried to illustrate with <SuperfluousContainer>.

I may not correctly understand what you mean here, but if you mean that Arofan,
Stephen, and myself forgot to mention the 0..n case, we did cover it, although
perhaps the wording of the proposal obscures things a bit.  Just in case, I'll
summarise the proposal.  Suppose that the <Thing> element has cardinality M..N.
Then

1. If N <= 1 (i.e. <Thing> is 0..1 or 1..1), then <Thing> does not have a
container.
2. If N >= 2 (e.g. 0..2, 1..2, 2..2, 0..3, 1..3, ...) then <Thing> has a
<ThingList> container.
3. If M = 0, the cardinality of <Thing> inside <ThingList> is 1..N, and the
cardinality of <ThingList> is 0..1.
4. If M >= 1, the cardinality of <Thing> inside <ThingList> is M..N, and the
cardinality of <ThingList> is 1..1.

I hope that helps.

	Cheers,
		Tony.
====
Anthony B. Coates
London Market Systems Limited
33 Throgmorton Street, London, EC2N 2BR 
http://www.londonmarketsystems.com/
mailto:abcoates@londonmarketsystems.com
Mobile/Cell: +44 (79) 0543 9026
[MDDL Editor (Market Data Definition Language), http://www.mddl.org/]
[FpML Arch WG Member (Financial Products Markup Language), http://www.fpml.org/]
-----------------------------------------------------------------------
This Email may contain confidential information and/or copyright material and is intended for the use of the addressee only.
Any unauthorised use may be unlawful. If you receive this Email by mistake please advise the sender immediately by using the reply  facility in your e-mail software.
Email is not a secure method of communication and London Market Systems Limited cannot accept responsibility for the accuracy or completeness of this message or any attachment(s). Please examine this email for virus infection, for which London Market Systems Limited accepts no responsibility. If verification of this email is sought then please request a hard copy. Unless otherwise stated any views or opinions presented are solely those of the author and do not represent those of London Market Systems Limited.