ubl-ndrsc — archive
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
— [Date Index]
| [Thread Index]
| [Month Index]
| [List Home]
[ubl-ndrsc] New rule for property term
MHonArc v2.5.2 -->ubl-ndrsc message
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: [ubl-ndrsc] New rule for property term
- From: Mavis Cournane <[email protected]>
- To: [email protected]
- Date: Wed, 28 Aug 2002 09:22:24 +0100
Dear all
we agreed that we need a new naming rule for property term.
See an excerpt from the minutes below. I think we should try to formulate
something today. As I have not bee on these calls I am a little cold as far as
understanding goes.
Thanks
Mavis
We agreed that we need a new rule for how to name the property
term when its contents are a series of like items. We agreed that
the ordered/unordered distinction is not particularly important,
so we discarded the option of using the word "Set" at all. Our
understanding is that multiple qualifiers are going to be allowed
under the new CCTS situation.
Straw poll:
property qualifier property term comments (preferred, acceptable)
ListOf LineItem The term is false in this case
ListOf LineItems Qualifier stuff too complicated
ListOfLineItem p=1 a=0
ListOfLineItems p=0 a=2
LineItemList p=5 a=2 We have a winner!
LineItems p=0 a=4
LineItemsList p=0 a=0
We discussed whether LineItemList should use "List" as the term and
"LineItem" (or whatever) as the qualifier, but decided that a
"naked list" as a object class's property is just too vague a
notion.
Some examples:
Order.LineItemList.Details
Item.SubstituteItemIdentifierList.Details
Item.PhysicalAttributeList.Details
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
— [Date Index]
| [Thread Index]
| [Month Index]
| [List Home]