Sharon Chisholm wrote:
<Andy> 4) XSD template for <notification> wrapper a) current definition is not what the WG agreed to, and does not even support the replayComplete notification correctly b) definition is not extensible, such that XSD cannot be properly used to specify extensions and restrictions </Andy> Actually, after Andy suggested some XSD to achieve being able to definenotifications as proper extensions of the notification https://ops.ietf.org/lists/netconf/netconf.2007/msg00123.html I respondedhttps://ops.ietf.org/lists/netconf/netconf.2007/msg00131.html suggesting that the XSD did not work as advertised in my tools, so I proposed something in the spirit of what Andy's stuff was trying to achieve but that validated in my tools. If there are other things it should be able to do, please clarify since it does what it needs to do from what I can see.
The current XSD definition is for a <notification> wrapper
that cannot have any XML attributes defined, and must contain
an element called <data>.
<xs:complexType name="dataInlineType">
<xs:complexContent>
<xs:extension base="xs:anyType"/>
</xs:complexContent>
</xs:complexType>
<!-- <Notification> operation -->
<xs:complexType name="NotificationType">
<xs:sequence>
<xs:element name="data" type="netconf:dataInlineType" />
</xs:sequence>
</xs:complexType>
<xs:element name="notification" type="NotificationType"/>
The <replayComplete> notification does not have an element called <data>.
This may not be the only notification ever defined that does
not have any additional data to include.
I think other people in the WG need to comment on this issue.
Should this 'data' element be defined in the <notification> base type?
Andy
--
to unsubscribe send a message to netconf-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://ops.ietf.org/lists/netconf/>