You are right about the arraystart/arrayend/mapstart/mapend.
They are [] and {} in JSON, I just didn't want to put those exact tokens
in because I didn't want to confuse people comparing it to JSON.
I'm still not totally understanding the cddl, but I'll look at it
further. Thank you very much for your work!
Thiago: Is there a good place to put these 2 documents?
On Wed, 2015-07-15 at 23:29 +0200, Carsten Bormann wrote:
> Attached is a CDDL version of what I understand from that.
>
>
> (I?m not sure I fully understand what you mean by ?mapstart?/?mapend"
> and ?arraystart?/?arrayend?, but maybe this is just {} and [] from
> CDDL.)
>
>
> For laughs, I have also attached 20 messages automatically generated
> from this specification?
>
> Gr??e, Carsten
>
> On 15 Jul 2015 at 22:14:49, Keane, Erich (erich.keane at intel.com)
> wrote:
>
> >
> > Ive put together a BNF inspired document, attached to here!
> >
> > You'll note that it is actually a bit wasteful, which is a result
> > of
> > trying to make it look as close to the JSON as possible without
> > being
> > overly-wasteful. Even so, we are at 1/3 to 1/2 package size for the
> > same data.
> >
> > Many of the string-keys could easily be replaced by integers (making
> > the
> > maps INT->val rather than String->val), which would save a ton of
> > space.
> >
> > Additionally, there are some organizational 'sub-maps' that could
> > easily
> > be done away with, such as the Discovery "prop", device and
> > platform
> > "rep", and representation's "prop" tag.
> >
> >
> > Architects: If you have questions, please let me know, I'll clarify
> > to
> > the best of of my ability.
> >
> >
> > On Tue, 2015-07-14 at 15:23 -0700, Thiago Macieira wrote:
> > > On Tuesday 14 July 2015 15:21:11 Thiago Macieira wrote:
> > > > On Tuesday 14 July 2015 20:59:42 Keane, Erich wrote:
> > > > > Since all comments were dealt with, and it passed validation
> > without
> > > > > further comments, the CBOR commit has been pushed to master!
> > Anyone
> > > > > doing a fresh pull should see the code.
> > > > >
> > > > > I'll continue monitoring for regressions caused here, as well
> > as work
> > > > > wtih other feature owners to get additional features in before
> > the
> > > > > freeze date.
> > > >
> > > > Nice work, Erich & team!
> > >
> > > BTW, can you describe the wire protocol now, for the benefit of
> > retrofitting the
> > > spec?
> > >
> >
> >
> > ____________________________________________________________________
> > _______________________________________________
> > iotivity-dev mailing list
> > iotivity-dev at lists.iotivity.org
> > https://lists.iotivity.org/mailman/listinfo/iotivity-dev
> >