Re: [netmod] attributes in draft-lhotka-netmod-yang-json

[Martin Bjorklund <[e-mail]>]

Hi,

Here's yet another attempt to handle attributes in JSON, without
changing the encoding for the case that there are no attributes
present.

In all examples, the attributes "inactive" and "etag" are present.

Attributes are encoded differently depending on the type of object:


leaf
----

Encode the attributes as a sibling to the leaf.


  leaf foo {
    type string;
  }

  "foo": "some value";
  "@foo": {
     "inactive": true,
     "etag": "...";
   }


list instance
-------------

Encode the attributes within the list instance.


  list bar {
    key name;
    leaf name {
      type string;
    }
    ...
  }

  "bar": [
     {
        "@bar": {
           "inactive": true,
           "etag": "..."
         }
         "name": "instance name";
      }]


container
---------

Encode the attributes within the container.


  container baz;

  "baz": {
     "@baz": {
        "inactive": true,
        "etag": "..."
       }
  }


leaf-list
---------

Encode the attributes as a sibling to the leaf-list, with an array of
same length as the leaf-list itself.


  leaf-list buzz {
     type string;
  }

  "buzz": [ "val1", "val2", "val3" ],
  "@buzz: [ null, 
            { "inactive": true,
              "etag": "..."
            }
            null]



/martin