2 Notification draft comments

[Andy Bierman <ietf@andybierman.com>]

Hi,

(1)

Sec 3.2.5.2 of notification-05 contains a stream retrieval schema
with an appinfo element that is relying on the non-existent 'netmod 
template'
standard.

      <xs:appinfo>
        <nm:identity
             xmlns:nm="urn:ietf:params:xml:ns:netmod:base:1.0">
          <nm:Name>
                   NetconfNotificationSchema
          </nm:Name>
          <nm:LastUpdated>
                   2006-09-06T09:30:47-05:00
          </nm:LastUpdated>
          <nm:Organization>IETF
          </nm:Organization>
          <nm:Description>
                    A schema that can be used to learn about current
                    event streams.
                 </nm:Description>
        </nm:identity>
      </xs:appinfo>


All of this 'extra' info should be put in a <documentation> element or 
removed,
like the XSD in section 4.

(2)

I think the filter examples in sec. 5 need some sort of explanation
of the assumed data model (i.e., the one with 'eventClasses' and 'card'
as top-level siblings). 


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