Martin Thomson <[email protected]> wrote:
> Do you know if the outer object can be stripped off? Context is
> usually sufficient to avoid that extra layer (and HTTP provides
> content-type to provide that context).
I don't know; it does have the advantage of making the JSON self-identifying,
and also providing built-in versioning. So while annoying to strip off a
layer, it isn't hard. It's just esthetically displeasing.
> module capport {
> yang-version 1.1;
> namespace "urn:...:ietf:...:capport";
> prefix "capport";
> import ietf-yang-types {
> prefix yang;
> }
> // ... metadata stuff
> container top {
> leaf captive {
> type boolean;
> }
> leaf end {
> type yang:date-and-time;
> }
> }
> }
See, and we are done :-)
--
Michael Richardson <[email protected]>, Sandelman Software Works
-= IPv6 IoT consulting =-
Attachment:
signature.asc
Description: PGP signature