Martin Bjorklund wrote:
Andy Bierman <ietf@andybierman.com> wrote:Martin Bjorklund wrote:Andy Bierman <ietf@andybierman.com> wrote:Martin Bjorklund wrote:Andy Bierman <ietf@andybierman.com> wrote:So every time we change or add a new bit of data to NETCONF, it will have to be in a new XSD <schema> and with a new targetNamespace? So by the time we have one tenth as many 'MIB objects' as SNMP, we will have about 5000 different namespace URIs to deal with?This problem isn't unique for NETCONF, and I think it has been solved (it must be) for XSD in general. A DM effort for NETCONF has to consider this problem of course.I don't think it has been solved in XSD. (Anyone know, then send a pointer!).http://www.xfront.com/SchemaVersioning.html http://www.xfront.com/Versioning.pdf
good -- this is what I was doing: keeping targetNamespace the same but changing schemaLocation for each version
If I was trying to solve an XML document editing problem, I would use WEBDAV. If I was trying to provide the most comprehensive language to model XML instance documents, I would use XSD. But I'm working on a network management problem, not an XML document problem.I completely agree. /martin
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/>