Hi, I do not think this draft is ready.
1) Behavior changes to conventional datastores There seem to be NBC changes being made to the behavior of the conventional non-NMDA datastores, particularly <running>. I disagree that it is a problem that <running> contains some system configuration mixed in with the client configuration. The only problem is that the data is not editable by clients. The "immutable" flag draft provides clients with enough information to avoid 'access-denied' errors when editing system config. Changing the behavior of <running> seems to break old non-NMDA clients that expect the combined config. 2) NBC Changes to XPath Changing the XPath evaluation procedures is an NBC change. In this case, also quite complicated to implement XPath across multiple datastores. System config could be visible in <running> using the immutable flag. Leafrefs and XPath are allowed to point at config=true in the same data tree. This does not require any changes to XPath processing. Referencing a special read-only datastore is no different than simply allowing the XPath to reference config=false. It is the same NBC change. 3) resolve-system I am confused why a client would not resolve the system, since the <running> datastore needs these nodes so the client nodes can exist. Andy
_______________________________________________ netmod mailing list -- [email protected] To unsubscribe send an email to [email protected]
