[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [wsn] Closing the WSN2.21
-- Igor
Sedukhin .. (igor.sedukhin@ca.com)
-- (631) 342-4325 .. 1 CA Plaza,
Islandia, NY 11788
<xs:element ref="wsnt:Topics" minOccurs=”0” maxOccurs=”unbounded” />
ie not have the two options your email
suggested.
++++++++
Steve
Graham
(919)254-0615 (T/L 444)
STSM, On Demand Architecture
Member, IBM
Academy of Technology
<Soli Deo
Gloria/>
++++++++
"Sedukhin, Igor S"
<Igor.Sedukhin@ca.com>
07/12/2004 01:48 PM | To: Steve Graham/Raleigh/IBM@IBMUS cc: <wsn@lists.oasis-open.org> Subject: RE: [wsn] Closing the WSN2.21 |
-- Igor
Sedukhin .. (igor.sedukhin@ca.com)
--
(631)
342-4325 .. 1 CA Plaza, Islandia, NY 11788
"Sedukhin, Igor S"
<Igor.Sedukhin@ca.com>
07/12/2004 01:37 PM |
To: <wsn@lists.oasis-open.org> cc: Subject: [wsn] Closing the WSN2.21 |
In principle, two schema sniplets could be folded into one XML pseudo markup of an instance. In that case schema is implied, but implementers are free to do the ref or inline the XML element declaration.
E.g.
In the specification document it
may be said:
The resource property document MUST contain the following
elements.
<wsnt:Topics/>*
<wsnt:FixedTopicSet/>
<wsnt:TopicExpressionDialects/>*
This way in the actual WSDL, in the property document schema declaration, when this spec is implemented I could have either
<xs:element targetNamespace="...WSN…" name="Topics" type=”wsnt:TopicExpressionType” minOccurs=”0” maxOccurs=”unbounded” />
Or
<xs:element ref="wsnt:Topics" minOccurs=”0”
maxOccurs=”unbounded” />
Note that either one is correct,
implementation-wise.
Anyway that is just a cleanup. This is up to the editors.
-- Igor
Sedukhin .. (igor.sedukhin@ca.com)
--
(631)
342-4325 .. 1 CA Plaza, Islandia, NY 11788
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]