On Fri, Aug 9, 2013 at 4:46 PM, Tim Bray <tbray(_at_)textuality(_dot_)com>
wrote:
On Fri, Aug 9, 2013 at 11:52 AM, Barry Leiba
<barryleiba(_at_)computer(_dot_)org>wrote:
To the rest of the community: Does anyone else think it is not
appropriate to publish CBOR as a Proposed Standard, and see who uses
it?
I have two moderate concerns:
1. I haven’t seen any particularly convincing evidence that CBOR would, in
production, achieve any meaningful reductions in serialization time or
deserialization time or code footprint or memory footprint.
2. I think CBOR does too much; I’d discard half the features and see who
uses *that*. Well, if it doesn’t take off they can always try CBOR-lite
next year.
But I do not see it as actively harmful, am not screaming or lying down in
the road; go ahead and give it an RFC number and see what happens.
I’d also like to compliment Barry on his restraint and courtesy in dealing
with Phillip here; far more than I would have been able to muster.
Tim, if you want to slam other people on the list, please have the courtesy
to do so directly. Are you really upset about what I said to Barry or what
I said about the defects in the XML specification you led?
The reason I directed those questions at Barry is that I had previously
asked them in private and received no response. I also want the answers to
be on the record. An applicability statement would be a good plan.
The issue here is not whether or not CBOR gets an RFC number but whether
issuing that RFC number means that those of us who made alternative
proposals for a binary encoding are being foreclosed on.
And it does seem rather odd that while I am being told that there are two
opportunities to challenge a Personal Submission, on the initial list and
the IETF list, that I then get criticized for raising the issues on the
IETF list.
For the record, I thought that there was a lot of skepticism about CBOR
from the start. There is certainly a consensus in support of CBOR among
supporters of CBOR but at least half the commenters were negative and the
fundamental question of why CBOR versus a binary version of JSON encoding
was never answered.
--
Website: http://hallambaker.com/