RE: notification-07 issue list (4 & 5)

["Sharon Chisholm" <schishol@nortel.com>]

<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 define
notifications as proper extensions of the notification 
https://ops.ietf.org/lists/netconf/netconf.2007/msg00123.html 
I responded
https://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.

<Andy>

5) XML representation of the <replayComplete> notification

   a) new element named <eventClass> has been added to the XSD.
      The WG never discussed adding this element.

           <xs:element name="eventClass"/>

      There is no text in the document about this element, including
      its actual XML type definition, purpose, or value for the
<replayComplete>
      notification.
</Andy>

This is residue. It was suppose to have been removed. It will be removed
in the update.
 
Sharon    

--
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/>