Some notes about the OSC 1.0 Specification

Hello everyone,

I´d like to bring a small definition problem (at least for me) on the table.

Any application that sends OSC Packets is an OSC Client; any application that receives OSC Packets is an OSC Server.

So, per definition any OSC Server that supports sending Query replies would be an OSC Client too, while any OSC Client that supports receiving Query replies would be an OSC Server.

I´d like to propose a reconsidering of this definition in the future, I was thinking something like this:
Change the definition in the OSC Packets to:
Any application that sends OSC Packets is an OSC Sender; any application that receives OSC Packets is an OSC Receiver.
While the OSC Client and OSC Server would be defined by other attributes like "being able to respond to OSC query replies" and/or a loosely following wikipedia using the characteristics of initiating requests and typically interacting with end-users for OSC Clients and passively waiting for requests for OSC Servers.

I feel such definitions would just go more conform with the common use of the terms and could reduce confusion by having differently defined terms.

I know it´s neither a huge thing nor practically relevant, but having studied philosophy once it´s been driving me nuts ever since I first noticed it - so please forgive me just having to bring it up ;)
I´d appreciate any thoughts on that matter, maybe I´m just foolishly wrong somewhere.

On a side note mainly to the webmaster, it seems like the links to examples inside the OSC Specification are broken.

With greetings,
Thorsten Weinz

Re: Some notes about the OSC 1.0 Specification

Good point -- sender/receiver makes for less ambiguous terminology. I'll check those links...