RE: Notification #9: replay in the future consensus point

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

<Andy>>
The 'eventClass', 'eventSeverity', and 'eventTime' fields are meta-data
which could be encoded as XML attributes in the <notification> element.
This should be required, even if the proprietary <eventType> has some or
all of these fields already.

This is why I keep asking the WG:
Are you SURE you want to forbid all XML attributes, forever, from being
included in the <notification> element?

Are you SURE this is not going to ever come up again as an issue,
because this is the only place we can really put inter-operable
meta-data into the notification message?
</Andy>

I don't consider these meta-data and it is only meta-data that you are
suppose to be using attributes for according to best practice I keep
hearing. These should be elements so I don't think there is an issue.


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