[OSC_dev] Fwd: Application Profiles: oscplanet

[Gaspard Bucher]

Contributors to the ideas behind "nameToBeFound" (oscplanet, oscit,
oscnet, whatever), please give me your names so I can write them on
the "Contributors" section of the "NameToBeFound" protocol. Real names
please (you can append a pseudo if you like).

I will put mine as:

Gaspard Bucher - Buma, "rubyk.org":http://rubyk.org

Gaspard


On Tue, Dec 23, 2008 at 3:43 PM, Gaspard Bucher <gaspard at teti.ch> wrote:
> There are actually 3+1 levels in this problem, 3 are related to data
> exchange and 1 is related to the physical layer (connection):
>
> 0. if UDP: network connection ===> solved through a common dns-sd
> service name (zeroconf): "xxxxxx" name (see below)
> 1. data format  ===> solved through OSC
> 2. query / get /set  ===> solved through a common ground: "xxxxxxx"
> conventions / methods
> 3. application functionalities ===> naming conventions for certain
> kinds of applications, midi equivalents, etc ===> "OpenMediaControl"
> for example
>
> About the "oscplanet" name, I prefer names that are somehow linked to
> metaphors ("Bonjour", "zeroconf", "Safari") but I do not really care.
> It seems to make sense to include something in the name about the
> distributed nature of the protocol, since the name refers to the full
> stack above and not only the query system conventions. Propositions
> (Only lower-case letters, digits, and hyphens; must begin and end with
> lower-case letter or digit) :
>
> "oscnet" (this sounds a bit too much like .NET to me, but it's easy to
> pronounce and is meaningful)
> "oscit" (Open Sound Control it, fun)
> "oscsqp" (Open Soundc Control Server Query Protocol, cryptic)
> "oscplanet" (seems too related to rubyk metaphors)
> "openmediacontrol" (illegal = too long)
> "omc" (french acronym for WTO: please no)
>
> My prefered name is "oscit" (fun, sounds good and highlights the
> *control* part of the thing) with second being "oscnet" (more focus on
> the network, distributed part).
>
> Please feel free to give your view on the names above (or propose new ones).
>
> Gaspard
>
> On Tue, Dec 23, 2008 at 11:48 AM, Jamie Bullock <jamie at postlude.co.uk> wrote:
>> On Mon, 2008-12-22 at 23:03 +0100, salsaman at xs4all.nl wrote:
>>
>>> >
>>> > While I have used 'oscp' in my examples, I am not overly keen on the
>>> > name Planet. Maybe I am just being boring but could something be
>>> > descriptive be used instead?
>>> >
>>> > OSC Replies?
>>> > Meta OSC ?
>>> > OSC Query and Response ?
>>> > OSC Introspection ?
>>> >
>>> > Planet just seems to be too all-encompassing.
>>>
>>> Erm....how about OMC :-) ?
>>
>> I got the impression that OMC was supposed to be something more than
>> what we are talking about here with (provisionally named) oscplanet?
>> Wasn't the idea to develop an actual address space for media control *in
>> addtion* to the meta-addresses...
>>
>> FWIW, I don't really like oscplanet name either. I think we should try
>> to get new simple, lightweight, implementation-independent meta-schema
>> out of these discussions. oscplanet is very non-descriptive unless
>> you're familiar with the metaphors used in rubyk. It sounds like an
>> implementation rather than a protocol.
>>
>> How about:
>>
>> OSC/SQP - Open Sound Control / Server Query Protocol
>>
>> or just
>>
>> OSC/SQ - Open Sound Control / Server Query
>>
>> ?
>>
>>>
>>> I also want to apologise if I am being difficult.
>>>
>>
>> I think it's important that people are a bit difficult about this ;-)
>> Otherwise we'll end up with a too-specific 'meta' protocol that only
>> works in a handful of implementations.
>>
>> Jamie
>>
>> --
>> www.postlude.co.uk
>> http://www.linkedin.com/in/jamiebullock
>>
>>
>> _______________________________________________
>> OSC_dev mailing list
>> OSC_dev at create.ucsb.edu
>> http://lists.create.ucsb.edu/mailman/listinfo/osc_dev
>>
>