AW: [sdo] [NEW ISSUE] isMany value of merged property for duplicate elements

["Buennig, Stefan" <stefan.buennig@sap.com>]

Hi Frank,

we support your proposal.
Our SDO implementation already works that way. I didn't remember immediately because the implementation was one year ago.

Best regards,
Stefan.

-----Ursprüngliche Nachricht-----
Von: Frank Budinsky [mailto:frankb@ca.ibm.com] 
Gesendet: Dienstag, 22. Juli 2008 21:50
An: sdo@lists.oasis-open.org
Betreff: [sdo] [NEW ISSUE] isMany value of merged property for duplicate elements

PROBLEM

See section 2.1.3 (second part) of 
http://www.oasis-open.org/committees/download.php/26722/SDO_XML_Issues.doc

PROPOSED RESOLUTION

Resolution as described in section 2.1.3. More specifically:

In section 9.3.2. change:

A single property is used for all the elements with the same local name 
and the same targetNamespace, where isMany=true. 

to the following:

A single property is used for all the elements with the same local name 
and the same targetNamespace. If the content model allows more than 1 
instance of the element, then isMany=true. If, however, the elements are 
mutually exclusive (for example, they are single valued and on two sides 
of a xsd:choice group), then isMany=false.


---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that
generates this mail.  Follow this link to all your TCs in OASIS at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php