Re: [Asdf] Kicking off ASDF charter discussion

[Michael Richardson <[e-mail]>]

{didn't open issues for this}

  } The ASDF WG will work closely with the CBOR WG, home of the CDDL
  } specification. It will also engage the still active mailing list of the
  } dormant JSON WG. Recent proposals to form an IRTF formal description
  } techniques (FDT) Research Group may lead to another collaboration
  } partner. The Thing-to-Thing Research Group (T2TRG) and its WISHI program
  } can be instrumental in engaging researchers and other SDOs in this space,
  } or instance W3C WoT, which is working on Thing Description Templates and
  } related specifications.

I can't really agree or disagree with any of this :-)
Can we split this up a bit?

1> The ASDF WG will work closely with the CBOR WG, home of the CDDL
1> specification.

While we are using CDDL to define the structure, I'm unclear what the back
and forth that ASDF will have with CBOR here.  Are there pieces in CDDL that
are missing that this model will motivate adding to CDDL?

2> It will also engage the still active mailing list of the
2> dormant JSON WG.

Is this about json-path, and/or json-schema?


3> Recent proposals to form an IRTF formal description
3> techniques (FDT) Research Group may lead to another collaboration
3> partner.

Where are these proposals occuring, and at one point will they conclude, and
is the timing of this important, critical, or optional to the process?

4> The Thing-to-Thing Research Group (T2TRG) and its WISHI program
4> can be instrumental in engaging researchers and other SDOs in this space,
4> or instance W3C WoT, which is working on Thing Description Templates and
4> related specifications.

This part seems rather aspirational.  All sorts of communications are
important and beneficial, but is there some kind of implied liason activity,
or some kind of cross-WG/RG last-call that is implied?

I don't see any effect from just deleting this paragraph from the charter :-)

--
Michael Richardson <[e-mail]>, Sandelman Software Works
 -= IPv6 IoT consulting =-