On Wed, Jun 13, 2018 at 03:40:31PM +0100, Robert Wilton wrote:
> 
> 5) I'm wondering whether there needs to be some sort of identifier about
> what type data is held.  E.g. does it represent data that can be consumed as
> part of one of the configuration datastores, or does it represent the
> equivalent of operational state, or is it data for an RPC, etc.
> 

Yes. I think I requested this before. There should be a way to indicate
which datastore instance-data belongs to.

I also do not understand why we have instance-data-set if the set is
limited to exactly one instance-data element. Perhaps room to find a
better name for the outer container or the anyxml (perhaps change
instance-data-set to instance-data and instance-data to simply data).
Or alternatively allow multiple instance-data portions but then meta
data would need to be associated with instance-data and not
instance-data-set, so we would actually need another layer.

Also, given that this is supposed to be serialized in XML (or JSON I
assume), would it make sense to include an XML preamble in the
examples, i.e.,

<?xml version="1.0" encoding="UTF-8"?>
<instance-data xmlns=...>
  <name>...</name>
  <datastore>ds:operational</datastore>
  <data>
    <yang-library xmlns="urn:ietf:params:xml:ns:yang:ietf-yang-library">
    </yang-library>
  </data>
</instance-data>

/js

-- 
Juergen Schoenwaelder           Jacobs University Bremen gGmbH
Phone: +49 421 200 3587         Campus Ring 1 | 28759 Bremen | Germany
Fax:   +49 421 200 3103         <https://www.jacobs-university.de/>

_______________________________________________
netmod mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/netmod

Reply via email to