25 May
2003
25 May
'03
11:06 a.m.
Hi Steve, hi others!
I'm just adding lrdf support to glame but apart from default values I dont
see more information than in the ladspa descriptor. Can we agree on some
more metatags? I'd like to have
- a Category (or multiple ones?)
- short description of ports and the plugin itself
- URI to the documentation of the plugin
am I right getting such information would be done via the lrdf call
lrdf_get_setting_metadata? So we need to define element labels for the
above. I'd suggest
- category
- description
- help_uri
Thoughts?
Richard.
25 May
25 May
1:03 p.m.
New subject: [linux-audio-dev] Re: LADSPA RDF additional information?
On Sun, May 25, 2003 at 02:54:15 +0200, Richard Guenther wrote:
Hi Steve, hi others!
I'm just adding lrdf support to glame but apart from default values I dont
see more information than in the ladspa descriptor. Can we agree on some
more metatags? I'd like to have
- a Category (or multiple ones?)
Category is allready in there. Its rdf:type, there is some example code to
read it (lrf_show_axonomy or something similar).
- short description of ports and the plugin itself
- URI to the documentation of the plugin
Good idea.
am I right getting such information would be done via
the lrdf call
lrdf_get_setting_metadata? So we need to define element labels for the
above. I'd suggest
Yes, its designed to use the Dublin Core metadata elements, but we can ad
whatever is needed, the problem is creating the data ofcourse.
- Steve
1:23 p.m.
New subject: [linux-audio-dev] Re: LADSPA RDF additional information?
On Sun, 25 May 2003, Steve Harris wrote:
Of course.
Richard.
On Sun, May 25, 2003 at 02:54:15 +0200, Richard
Guenther wrote:
Hmm. I see. How can I query the "path" to a particular plugin? I.e. f.i.
the
/Amplitude/Distortions/[1414]
information?
I think I dont want to traverse the whole hierarchy for each plugin, no?
Hi Steve, hi others!
I'm just adding lrdf support to glame but apart from default values I dont
see more information than in the ladspa descriptor. Can we agree on some
more metatags? I'd like to have
- a Category (or multiple ones?)
Category is allready in there. Its rdf:type, there is some example code to
read it (lrf_show_axonomy or something similar). - short description of ports and the plugin
itself
- URI to the documentation of the plugin
Good idea.
am I right getting such information would be done
via the lrdf call
lrdf_get_setting_metadata? So we need to define element labels for the
above. I'd suggest
Yes, its designed to use the Dublin Core metadata elements, but we can ad
whatever is needed, the problem is creating the data ofcourse.
5:06 p.m.
New subject: [linux-audio-dev] Re: LADSPA RDF additional information?
On Sun, May 25, 2003 at 05:11:23 +0200, Richard Guenther wrote:
Its probably easiest to build a reverse lookup table, but it should be
possible to traverse the tree from each plugin to the top, but its
probably less efficient.
Bear in mind there will be > 1 path for some plugins.
- Steve
Category is
allready in there. Its rdf:type, there is some example code to
read it (lrf_show_axonomy or something similar).
Hmm. I see. How can I query the "path" to a particular plugin? I.e. f.i.
the
/Amplitude/Distortions/[1414]
7844
days inactive
7844
days old
linux-audio-dev@lists.linuxaudio.org
3 comments
2 participants
participants (2)
-
Richard Guenther -
Steve Harris