[OSC_dev] OSC_dev Digest, Vol 57, Issue 17

[Gaspard Bucher]

Let's go for "oscit" with a the proposed retronym of 'Open Sound
Control Interface Transfer'.

On Wed, Dec 24, 2008 at 7:28 PM,  <salsaman at xs4all.nl> wrote:
> On Wed, December 24, 2008 19:15, Jamie Bullock wrote:
>> On Wed, 2008-12-24 at 16:06 +0100, Gaspard Bucher wrote:
>>> As I see it there are two things needed:
>>>
>>> 1. common protocol "oscit"
>>
>> I can't resist sharing a retronym I just thought of which is 'Open Sound
>> Control Interface Transfer'. WDYT? After all that's essentially what the
>> protocol does -- sets up an address space for transferring interface
>> (meta) data between hosts.
>>
>> best,
>>
>> Jamie
>>
>> --
>> www.postlude.co.uk
>> http://www.linkedin.com/in/jamiebullock
>>
>
> I think we have a winner !!!!
>
>
> Another reason to like oscit, is that it reminds me of jackit (the jack
> audio connection kit) which should be familiar to many audio developers.
> In some ways it is analogous, jackit is for raw data (audio and video) and
> oscit is for control messages.
>
>
> Cheers,
> Gabriel.
>
>
> _______________________________________________
> OSC_dev mailing list
> OSC_dev at create.ucsb.edu
> http://lists.create.ucsb.edu/mailman/listinfo/osc_dev
>