linuxaudio.org

On 06/14/2010 12:02 AM, Paul Davis wrote:
> how do you describe that a plugin can use extension X? what is the

quoted text
> name of extension X? how do you describe the fact that a plugin is

> considered by its author to belong to a particular category within a

> particular categorization of plugins? what is the name of the

> category? what is the name of the categorization?

>From what I read at http://lv2plug.in/, the use of URIs is a bit more ambitious

than identification and categorization:
"LV2 offers identification of plugins and ports not (necessarily) by obscure ID

numbers, but human readable URIs and port symbols.
The URI can be a web address (optionally, any URI is fine). This allows the use

of HTTP content negotiation to ask for the RDF of a plugin originally only the

URI is known of. The RDF could include machine readable information about where

to get the plugin. Thus sharing files that reference plugins such as sequencer

sessions or modular synthesizer patches would become more comfortable, as

missing plugins could be fetched automatically (or finding them would be easier,

at least)."
This last sentence seems to clarify the idea behind URIs.
--

  Olivier
_______________________________________________

Linux-audio-dev mailing list

Linux-audio-dev@lists.linuxaudio.org

http://lists.linuxaudio.org/listinfo/linux-audio-dev