[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [ubl-ndrsc] Containers
Tim, regarding lists: the idea is that if there is an element of name Name and cardinality 1..n in the spreadsheet it is safe to enclose it in a list of name NameList. However, elements of cardinality 0..n should not, because you would then end up with possibly empty Lists, which is not what anybody wants. We did look at the spreadsheet, and we did verify that only those that have cardinality of 1..n are the ones one would definitely say are candidates for list items. The lists themselves should be of cardinality 1..1, otherwise you may end up with no container to put the list items in. Or you end up with a really ambiguous schema where you can either have List items scattered by themselves OR a container with the List items. Ugh. Tim McGrath wrote: > we discussed the idea of including stylesheets and formatting guides > with documents at the F2F. LCSC decided this was really the domain of > the FPSC and Ken has expressed conern about this model. He is working > on a response/paper (i believe) which should be considered before we > amke any decisions on this. > > also, i take Chee-Kai's point about the 0..n. they too should be > "List"s, if we accept the argument that Lists are useful for repeating > elements. > > however, if we make these "List"s 1..1 (ie mandatory) , we would carry > unused (and potentially empty) baggage. if we make them 0..1(optional) > it means some will and some wont use them, so we have implementation > differences. which is the worse problem? > > Chin Chee-Kai wrote: > >>On Thu, 15 May 2003, Lisa-Aeon wrote: >> >> >> >>>>... >>>>Proposal: >>>> >>>>1. All documents shall have a container for metadata and which proceeds >>>>the body of the document and is named "Head" _____________. (anything but >>>>header) >>>> >>>> >> >>Very nice! I see metadata coming in at least from input tag >>marking, output formatting and styling, document instance ID >>(UBL document processing), version tagging, and possibility >>of managing such "attachments" as company logo, formatting >>stylesheets, etc. >> >>Are we talking about the following structure: >> <Head> >> .... >> </Head> >> <Order> >> .... >> </Order> >> >>? In that case should NDR consider creating an universal >>outer envelope that wraps any and all UBL instances, such >>as (for lack of a better name, using UBL itself): >> <UBL> >> <Head> >> .... >> </Head> >> <Order> >> .... >> </Order> >> </UBL> >>? >> >>Please advise. >> >> >> >> >> >>>>2. All elements with a cardinality of 1..n, (and lack a qualifing >>>>structure) must be contained by a list container named "(name of repeating >>>>element)List", which has a cardinality of 1..1. >>>> >>>> >> >>Great conclusion! What about the ruling for cardinality of 0..n? >> >> >> >> >>Best Regards, >>Chin Chee-Kai >>SoftML >>Tel: +65-6820-2979 >>Fax: +65-6743-7875 >>Email: cheekai@SoftML.Net >>http://SoftML.Net/ >> >> > > -- > regards > tim mcgrath > phone: +618 93352228 > postal: po box 1289 fremantle western australia 6160 > > -- Eduardo Gutentag | e-mail: eduardo.gutentag@Sun.COM Web Technologies and Standards | Phone: +1 510 550 4616 x31442 Sun Microsystems Inc. | 1800 Harrison St. Oakland, CA 94612 W3C AC Rep / OASIS TAB Chair
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]