Javascript Object Notation
charter-ietf-json-02
Yes
(Barry Leiba)
(Jari Arkko)
No Objection
(Adrian Farrel)
(Alia Atlas)
(Joel Jaeggli)
(Kathleen Moriarty)
(Martin Stiemerling)
(Stephen Farrell)
Note: This ballot was opened for revision 01-01 and is now closed.
Ballot question: "Is this charter ready for external review? Is this charter ready for approval without external review?"
Barry Leiba Former IESG member
Yes
Yes
(for -01-01)
Unknown
Jari Arkko Former IESG member
Yes
Yes
(for -01-01)
Unknown
Pete Resnick Former IESG member
Yes
Yes
(2014-04-02 for -01-01)
Unknown
I am ambivalent about external review. On the one hand, these activities are really IETF internal. On the other, we've been trying to develop a liaison relationship with Ecma. Input on this question welcome.
Adrian Farrel Former IESG member
No Objection
No Objection
(for -01-01)
Unknown
Alia Atlas Former IESG member
No Objection
No Objection
(for -01-01)
Unknown
Alissa Cooper Former IESG member
No Objection
No Objection
(2014-04-08 for -01-01)
Unknown
I think giving Ecma a heads-up is a good idea.
Brian Haberman Former IESG member
No Objection
No Objection
(2014-04-04 for -01-01)
Unknown
To answer Pete's question, I think it would be "nice" to inform Ecma of this pending re-chartering. I do not know all the politics of the interactions, but it seems that such notification could be seen as a sign of willingness on behalf of the IETF to work with them. Can I assume that Ecma is not on the new-work list?
Joel Jaeggli Former IESG member
No Objection
No Objection
(for -01-01)
Unknown
Kathleen Moriarty Former IESG member
No Objection
No Objection
(for -01-01)
Unknown
Martin Stiemerling Former IESG member
No Objection
No Objection
(for -01-01)
Unknown
Richard Barnes Former IESG member
No Objection
No Objection
(2014-04-09 for -01-01)
Unknown
I'm not really convinced that these new specs add much value over the base JSON spec (the streaming one in particular). But they don't seem harmful either.
Spencer Dawkins Former IESG member
No Objection
No Objection
(2014-04-08 for -01-01)
Unknown
I wish all charters were this short. I salute you all.
I looked at the draft that will be used as a starting point, and didn't see a list of interoperability issues ("what problem are we trying to solve?").
Are those issues well known in the community, so there's no reason to write them down?
Is anyone likely to raise issues that aren't addressed in the current draft?
Stephen Farrell Former IESG member
No Objection
No Objection
(for -01-01)
Unknown
Ted Lemon Former IESG member
No Objection
No Objection
(2014-04-09 for -01-01)
Unknown
I suspect I know what a streamable sequence of JSON texts is, but it's a bit unclear, and would be nice if it were stated in a tiny bit more detail.