[OSC_dev] json type tag ?

[salsaman at xs4all.nl]

On Mon, March 30, 2009 22:16, Gaspard Bucher wrote:
> Of course, the json representation of anything can be stored in a
> string, even a hash like:
> {"name":"Joe", "age":32} or a midi message or whatever.
>
> But when you receive such a thing, it's nice to know it's not the same as
> "This is my friend Joe. He is 32 years old." because you need very
> different parsers to get Joe's age :-).
>
> G.
>

Sure. But this can be indicated in the name (address) space of the message.

IMO we should differentiate strongly between the fundamental (final if you
like), type of the parameter (a string is a sequence of bytes terminated
with a NULL), and the meaning of that string (this is a hash entry, this
is json, this is a database tuple, this is the name of an effect, this is
a comment field, etc), otherwise why not have a million different tag
types, and every OSC parser will have to know how to handle all of those
million types.



Salsaman.