Would you be happier if, instead of saying a number of bits should be reserved, 
I said that there should be a maximum of four different possible modification 
values, with one of them being a default (such that it could be represented in 
a maximum of 2 bits if a protocol so desired)?

The JSON protocol would clearly ignore the hints.

Chad


On 8/21/08 5:23 PM, "Bryan Duxbury" <[EMAIL PROTECTED]> wrote:

Clearly the protocols and the modification types need to be in sync,
but saying that a certain number of bits should be reserved is too
specific. How would that map to the JSON protocol, for instance?

It seems like we've arrived at some consensus. Should we create a new
issue for making type modifiers and get to work?

-Bryan

Reply via email to