[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [no subject]
Here is the relevant XSD for the notify message:=20
<xsd:complexType name=3D"NotificationMessageHolderType" >=20
<xsd:sequence>=20
<xsd:element name=3D"SubscriptionReference"=20
type=3D"wsa:EndpointReferenceType"=20
minOccurs=3D"0" maxOccurs=3D"1" />=20
<xsd:element name=3D"Topic"=20
type=3D"wsnt:TopicExpressionType"=20
minOccurs=3D"1" maxOccurs=3D"1" />=20
<xsd:element name=3D"ProducerReference"=20
type=3D"wsa:EndpointReferenceType"=20
minOccurs=3D"0" maxOccurs=3D"1" />=20
<xsd:element name=3D"Message" type=3D"xsd:anyType"=20
minOccurs=3D"1" maxOccurs=3D"1" />=20
</xsd:sequence>=20
</xsd:complexType>=20
the proposed change is to modify the way the Message component is
defined, the new definition would look like:=20
<xsd:element name=3D"Message">=20
<xsd:complexType>=20
<xsd:sequence>=20
<xsd:any namespace=3D"##any" processContents=3D"lax"=20
minOccurs=3D"1" maxOccurs=3D"1" />=20
</xsd:sequence>=20
</xsd:complexType>=20
</xsd:element>=20
Although there might be some subtle difference in the XSD that I don't
immediately grasp, it seems to me that this is an equally good way to
model message, and if it provides a solution to the problem Igor is
facing, then it seems like a good approach to take.
Notes
Mar
<http://www.oasis-open.org/apps/org/workgroup/wsn/download.php/11841/WSN
_minutes_2005_03_14.doc> 24, 2005: Igor
<http://www.oasis-open.org/apps/org/workgroup/wsn/email/archives/200503/
msg00035.html> raised this issue on the mailing list. Note that some of
subsequent email discussion on this topic spilled on the WSDM mailing
list.
Mar
<http://www.oasis-open.org/apps/org/workgroup/wsn/download.php/12039/WSN
_minutes_2005_03_28.doc> 28, 2005 (Conf call): This issue was discussed
on the conf call. Steve Graham volunteered and later posted a proposal
on the mailing list.
Status: Open - approach agreed
Date: Mar 28, 2005
Agreed Approach: See Proposed Recommendation
Contact:=20
Igor Sedukhin
Cross Reference:
=20
------_=_NextPart_001_01C53EE5.0A6C26A0
Content-Type: text/html;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<TITLE>Message</TITLE>
<META content=3D"MSHTML 6.00.2800.1491" name=3DGENERATOR></HEAD>
<BODY>
<DIV><!-- Converted from text/plain format --><FONT face=3DArial=20
size=3D2></FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Here is the proposed issue text for=20
-</FONT></DIV><FONT face=3DArial size=3D2>
<DIV><BR>AI 71 - Sanjay to open issue to change Notify message to =
contain a=20
sequence of 1 xsd:any (for consistency with SOAP body)</DIV>
<DIV> </DIV>
<DIV>Please review.</DIV>
<DIV> </DIV>
<DIV>Thanks,</DIV>
<DIV>Sanjay</FONT></DIV>
<DIV>
<H2 style=3D"MARGIN: 12pt 0in 3pt; TEXT-INDENT: 0in"><EM><FONT =
face=3DArial>WSN2.45:=20
Inconsistent typing of notification payload (xs:any vs=20
xs:anyType)<?xml:namespace prefix =3D o ns =3D=20
"urn:schemas-microsoft-com:office:office" /><o:p></o:p></FONT></EM></H2>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 6pt">The=20
wsnt:Notify/wsnt:NotificationMessage/wsnt:Message is of type xs:anyType =
while=20
the <A href=3D"soap:Envelope/soap:Body"><SPAN=20
style=3D"COLOR: windowtext; TEXT-DECORATION: none; text-underline: =
none">soap:Envelope/soap:Body</SPAN></A>=20
is a container of xs:any. <SPAN style=3D"mso-spacerun: =
yes"> </SPAN>This=20
creates differing requirements on the type of the notification message =
content=20
depending upon whether the Subscription has the UseNotify flag turned on =
or not.=20
<SPAN style=3D"mso-spacerun: yes"> </SPAN>Since the indication of =
UseNotify=20
is at the Subscriber's will, allowing different type requirements on the =
notification message content may result in interoperability problems. =
More over,=20
objects that serialize directly in value could not be sent unwrapped, =
but could=20
be sent Notify wrapped.<o:p></o:p></P>
<H5 style=3D"MARGIN: 12pt 0in 3pt; TEXT-INDENT: 0in"><EM><FONT=20
size=3D4>Specifications<o:p></o:p></FONT></EM></H5>
<UL style=3D"MARGIN-TOP: 0in" type=3Ddisc>
<LI class=3DMsoNormal=20
style=3D"MARGIN: 0in 0in 6pt; mso-list: l1 level1 lfo1; tab-stops: =
list .5in">WS-BaseNotification<o:p></o:p></LI></UL>
<H5 style=3D"MARGIN: 12pt 0in 3pt; TEXT-INDENT: 0in"><EM><FONT =
size=3D4>Proposed=20
Recommendations<o:p></o:p></FONT></EM></H5>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 6pt">Excerpt from<A=20
href=3D"http://www.oasis-open.org/apps/org/workgroup/wsn/email/archives/2=
00503/msg00046.html">=20
Steve’s posting on the email list</A>:<o:p></o:p></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 6pt"><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: sans-serif">From my understanding =
of the=20
discussion, this boils down to a peculiarity in the way we chose to =
model the=20
Notify message. If we make a slight modification to the xsd for =
the Notify=20
message, then we can bring a bit more consistency back to the wrappered =
and=20
non-wrappered approach.</SPAN> <BR><BR><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: sans-serif">Here is the relevant =
XSD for=20
the notify message:</SPAN> <BR><BR><SPAN=20
style=3D"FONT-SIZE: 7.5pt; FONT-FAMILY: 'Courier New'"> =
<xsd:complexType=20
name=3D"NotificationMessageHolderType" ></SPAN> <BR><SPAN=20
style=3D"FONT-SIZE: 7.5pt; FONT-FAMILY: 'Courier New'"> =20
<xsd:sequence></SPAN> <BR><SPAN=20
style=3D"FONT-SIZE: 7.5pt; FONT-FAMILY: 'Courier New'"> =
=20
<xsd:element name=3D"SubscriptionReference" </SPAN><BR><SPAN=20
style=3D"FONT-SIZE: 7.5pt; FONT-FAMILY: 'Courier New'"> =
=20
=
type=3D"wsa:EndpointReferenceType"</SPAN>=20
<BR><SPAN style=3D"FONT-SIZE: 7.5pt; FONT-FAMILY: 'Courier New'"> =
=20
minOccurs=3D"0"=20
maxOccurs=3D"1" /></SPAN> <BR><SPAN=20
style=3D"FONT-SIZE: 7.5pt; FONT-FAMILY: 'Courier New'"> =
=20
<xsd:element name=3D"Topic" </SPAN><BR><SPAN=20
style=3D"FONT-SIZE: 7.5pt; FONT-FAMILY: 'Courier New'"> =
=20
=
type=3D"wsnt:TopicExpressionType"=20
</SPAN><BR><SPAN style=3D"FONT-SIZE: 7.5pt; FONT-FAMILY: 'Courier =
New'"> =20
=
minOccurs=3D"1"=20
maxOccurs=3D"1" /></SPAN> <BR><SPAN=20
style=3D"FONT-SIZE: 7.5pt; FONT-FAMILY: 'Courier New'"> =
=20
<xsd:element name=3D"ProducerReference" </SPAN><BR><SPAN=20
style=3D"FONT-SIZE: 7.5pt; FONT-FAMILY: 'Courier New'"> =
=20
=
type=3D"wsa:EndpointReferenceType"=20
</SPAN><BR><SPAN style=3D"FONT-SIZE: 7.5pt; FONT-FAMILY: 'Courier =
New'"> =20
=
minOccurs=3D"0"=20
maxOccurs=3D"1" /></SPAN> <BR><SPAN=20
style=3D"FONT-SIZE: 7.5pt; FONT-FAMILY: 'Courier New'"> =
=20
<xsd:element name=3D"Message" type=3D"xsd:anyType" </SPAN><BR><SPAN=20
style=3D"FONT-SIZE: 7.5pt; FONT-FAMILY: 'Courier New'"> =
=20
minOccurs=3D"1" maxOccurs=3D"1" =
/></SPAN> <BR><SPAN=20
style=3D"FONT-SIZE: 7.5pt; FONT-FAMILY: 'Courier New'"> =20
</xsd:sequence></SPAN> <BR><SPAN=20
style=3D"FONT-SIZE: 7.5pt; FONT-FAMILY: 'Courier New'"> =20
</xsd:complexType></SPAN> <BR><BR><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: sans-serif">the proposed change =
is to=20
modify the way the Message component is defined, the new definition =
would look=20
like:</SPAN> <BR><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier New'"> =
<SPAN=20
style=3D"COLOR: teal"><</SPAN><SPAN style=3D"COLOR: =
#3f8080">xsd:element=20
</SPAN><SPAN style=3D"COLOR: purple">name</SPAN>=3D<SPAN=20
style=3D"COLOR: #4200ff">"Message"</SPAN><SPAN=20
style=3D"COLOR: teal">></SPAN></SPAN> <BR><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier New'"> =
=20
<SPAN style=3D"COLOR: teal"><</SPAN><SPAN=20
style=3D"COLOR: #3f8080">xsd:complexType</SPAN><SPAN=20
style=3D"COLOR: teal">></SPAN></SPAN> <BR><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier New'"> =
=20
<SPAN style=3D"COLOR: teal"><</SPAN><SPAN=20
style=3D"COLOR: #3f8080">xsd:sequence</SPAN><SPAN=20
style=3D"COLOR: teal">></SPAN></SPAN> <BR><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier New'"> =
=20
<SPAN style=3D"COLOR: teal"><</SPAN><SPAN=20
style=3D"COLOR: #3f8080">xsd:any </SPAN><SPAN=20
style=3D"COLOR: purple">namespace</SPAN>=3D<SPAN style=3D"COLOR: =
#4200ff">"##any"=20
</SPAN><SPAN style=3D"COLOR: purple">processContents</SPAN>=3D<SPAN=20
style=3D"COLOR: #4200ff">"lax"</SPAN></SPAN> <BR><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: #4200ff; FONT-FAMILY: 'Courier =
New'"> =20
=20
</SPAN><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: purple; FONT-FAMILY: 'Courier =
New'">minOccurs</SPAN><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier New'">=3D<SPAN=20
style=3D"COLOR: #4200ff">"1" </SPAN><SPAN=20
style=3D"COLOR: purple">maxOccurs</SPAN>=3D<SPAN style=3D"COLOR: =
#4200ff">"1"=20
</SPAN><SPAN style=3D"COLOR: teal">/></SPAN></SPAN> <BR><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier New'"> =
=20
<SPAN style=3D"COLOR: teal"></</SPAN><SPAN=20
style=3D"COLOR: #3f8080">xsd:sequence</SPAN><SPAN=20
style=3D"COLOR: teal">></SPAN></SPAN> <BR><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier New'"> =
=20
<SPAN style=3D"COLOR: teal"></</SPAN><SPAN=20
style=3D"COLOR: #3f8080">xsd:complexType</SPAN><SPAN=20
style=3D"COLOR: teal">></SPAN></SPAN> <BR><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier New'"> =
<SPAN=20
style=3D"COLOR: teal"></</SPAN><SPAN=20
style=3D"COLOR: #3f8080">xsd:element</SPAN><SPAN=20
style=3D"COLOR: teal">></SPAN></SPAN> <BR><BR><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: sans-serif">Although there might =
be some=20
subtle difference in the XSD that I don't immediately grasp, it seems to =
me that=20
this is an equally good way to model message, and if it provides a =
solution to=20
the problem Igor is facing, then it seems like a good approach to=20
take.</SPAN><o:p></o:p></P>
<H5 style=3D"MARGIN: 12pt 0in 3pt; TEXT-INDENT: 0in"><EM><FONT=20
size=3D4>Notes<o:p></o:p></FONT></EM></H5>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 6pt"><A=20
href=3D"http://www.oasis-open.org/apps/org/workgroup/wsn/download.php/118=
41/WSN_minutes_2005_03_14.doc">Mar=20
24, 2005</A>: Igor<A=20
href=3D"http://www.oasis-open.org/apps/org/workgroup/wsn/email/archives/2=
00503/msg00035.html">=20
raised this issue</A> on the mailing list. Note that some of subsequent =
email=20
discussion on this topic spilled on the WSDM mailing =
list.<o:p></o:p></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 6pt"><A=20
href=3D"http://www.oasis-open.org/apps/org/workgroup/wsn/download.php/120=
39/WSN_minutes_2005_03_28.doc">Mar=20
28, 2005 (Conf call)</A>: This issue was discussed on the conf call. =
Steve=20
Graham volunteered and later posted a proposal on the mailing=20
list.<o:p></o:p></P>
<H5 style=3D"MARGIN: 12pt 0in 3pt; TEXT-INDENT: 0in"><FONT =
size=3D4><EM>Status:<SPAN=20
style=3D"mso-spacerun: yes"> </SPAN></EM><SPAN=20
style=3D"FONT-WEIGHT: normal; FONT-STYLE: normal; mso-bidi-font-weight: =
bold; mso-bidi-font-style: italic">Open=20
– approach agreed<o:p></o:p></SPAN></FONT></H5>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 6pt 0.5in"><SPAN=20
style=3D"FONT-SIZE: 13pt; mso-bidi-font-weight: bold; =
mso-bidi-font-style: italic">Date:=20
</SPAN><?xml:namespace prefix =3D st1 ns =3D=20
"urn:schemas-microsoft-com:office:smarttags" /><st1:date Month=3D"3" =
Day=3D"28"=20
Year=3D"2005"><SPAN=20
style=3D"FONT-SIZE: 13pt; mso-bidi-font-weight: bold; =
mso-bidi-font-style: italic">Mar=20
28, 2005</SPAN></st1:date><SPAN=20
style=3D"FONT-SIZE: 13pt; mso-bidi-font-weight: bold; =
mso-bidi-font-style: italic"><o:p></o:p></SPAN></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 6pt 0.5in"><SPAN=20
style=3D"FONT-SIZE: 13pt; mso-bidi-font-weight: bold; =
mso-bidi-font-style: italic">Agreed=20
Approach: See Proposed Recommendation<o:p></o:p></SPAN></P>
<H5 style=3D"MARGIN: 12pt 0in 3pt; TEXT-INDENT: 0in"><EM><FONT =
size=3D4>Contact:=20
<o:p></o:p></FONT></EM></H5>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 6pt 0.5in">Igor=20
Sedukhin<o:p></o:p></P>
<H5 style=3D"MARGIN: 12pt 0in 3pt; TEXT-INDENT: 0in"><EM><FONT =
size=3D4>Cross=20
Reference:<o:p></o:p></FONT></EM></H5>
<P class=3DMsoNormal=20
style=3D"MARGIN: 0in 0in 6pt"><o:p> </o:p></P></DIV></BODY></HTML>
------_=_NextPart_001_01C53EE5.0A6C26A0--
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]