uddi-spec message
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [Elist Home]
Subject: Re: [uddi-spec] CR for keyedRefernce requirement in groups
- From: Andrew Hately <hately@us.ibm.com>
- To: Max Voskob <mvoskob@msi.com.au>
- Date: Thu, 06 Feb 2003 12:25:39 -0600
Max,
The schema allows for the case where
a user wants to query for entities which have the keyedReferenceGroup without
specifying any values within the group.
Although we have tried to avoid element
cardinality enforcement after schema assessment/validation, what I propose
is that we do enforce this special case as the flexibility of storing a
keyedReferenceGroup with no keyedReferences is likely to cause some confusion
on the difference between modeling a keyedReferenceGroup without any keyedReferences
and just using a keyedReference.
Andrew Hately
IBM Austin
UDDI Development, Emerging Technologies
Lotus Notes: Andrew Hately/Austin/IBM@IBMUS
Internet: hately@us.ibm.com
(512) 838-2866, t/l 678-2866
Max Voskob <mvoskob@msi.com.au>
02/06/2003 02:24 AM
|
To
| uddi-spec@lists.oasis-open.org
|
cc
|
|
Subject
| Re: [uddi-spec] CR for keyedRefernce
requirement in groups |
|
Andrew,
Do we need to change the schema?
I think it should look like this:
<xsd:complexType name="keyedReferenceGroup" final="restriction">
<xsd:sequence>
>>>>>>>>>>>>> <xsd:element
ref="uddi:keyedReference" minOccurs="1"
maxOccurs="unbounded"/>
</xsd:sequence>
<xsd:attribute name="tModelKey" type="uddi:tModelKey"
use="required"/>
</xsd:complexType>
Otherwise the schema will be out of synch with the spec.
Cheers,
Max
----- Original Message -----
From: Andrew
Hately
To: uddi-spec@lists.oasis-open.org
Sent: Thursday, February 06, 2003 7:04 PM
Subject: [uddi-spec] CR for keyedRefernce requirement
in groups
Please review the attache CR-0026
Andrew Hately
IBM Austin
UDDI Development, Emerging Technologies
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [Elist Home]
Powered by eList eXpress LLC