[OSC_dev] Application Profiles

[Gaspard Bucher]

On Sun, Dec 21, 2008 at 2:14 AM, Andy W. Schmeder
<andy at cnmat.berkeley.edu> wrote:
> On Dec 20, 2008, at 3:56 PM, Nicholas J Humfrey wrote:
>
>> Note that liblo already uses '#reply' and has done for quite a long
>> time. I am trying to find out what that convention is based on.
>
>
> #reply was first proposed in this 2004 paper by myself and Matt Wright:
>
> http://opensoundcontrol.org/publication/query-system-open-sound-control
>
>

I am profoundly sorry, but #reply is not a valid OSC name:

Each OSC Method and each OSC Container other than the root of the tree
has a symbolic name, an ASCII string consiting of printable characters
other than the following:

Printable ASCII characters not allowed in names of OSC Methods or OSC Containers
character	name	ASCII code (decimal)
' '	 space	32
#	number sign	35
*	asterisk	42
,	comma	44
/	forward slash	47
?	question mark	63
[	open bracket	91
]	close bracket	93
{	open curly brace	123
}	close curly brace	125


I would love to use "#info", etc but it's not allowed by the spec or I
am missing something important here.


The current things we have sorted out on
openmediacontrol.wetpaint.com/ are (maybe there is not a total
agreement on everything):

1. Get answers to queries back:
/reply_to <port>

The reply is "/omc/player/vlc", "/omc/rubyk" = namespace. The IP can
be retrieved from the originating UDP packet.

2. Get human readable help on a node:
/any/path(info)

Would love to use /any/path/#info, but it's not allowed for many
reasons: "#" illegal, "/blah" after method not allowed.

3. Get/set value
/some/attribute   ===> get value (with signature because of type tags)
/some/attribute <value>  ===> set value and returns same result as
"/some/attribute"

4. Node listing
/some/path/

Ending "/" = listing.

Gaspard