[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: minutes for NETCONF WG interim meeting (09/03)
>>>>> Andy Bierman writes:
Andy> Sooner or later the concept of change control rules will come
Andy> up. If there are any expectations that version 1.1 of a
Andy> capability implies any backward compatibility with version 1.0,
Andy> then it helps to identify the version of the capability. BTW,
Andy> these capability identifiers are also going to be used for
Andy> schemas, and we will definitely need change control rules which
Andy> include backward compatibility expectations for different
Andy> versions of a data model.
I can understand that you might want to have clear change control
rules for the data model which is more or less designed to be revised
when there is a need to do so. I do not think this applies to protocol
capabilities per se since they should not regularily be changed. And
even then, you can embed version numbers into the identifier and if
you want in a well known place. See the netconf XML schema name space
identification for an example.
If URIs do not work for identifying protocol capabilities, then I am
asking why URIs work for identifying schemas and schema versions.
/js
--
Juergen Schoenwaelder International University Bremen
<http://www.eecs.iu-bremen.de/> P.O. Box 750 561, 28725 Bremen, Germany
--
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/>