Re: [LAD] minimal LV2

On Mon, 14 Jun 2010, fons@email-addr-hidden wrote:

>>> @prefix : <http://lv2plug.in/ns/lv2core#> .
>>> @prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> .
>>> @prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .
>>> @prefix xsd: <http://www.w3.org/2001/XMLSchema> .
>>> @prefix doap: <http://usefulinc.com/ns/doap#> .
>>> @prefix foaf: <http://xmlns.com/foaf/0.1/> .
[snip]
>>
>> So, the plugin contains a certain amount of "metadata".
>> Things like the licence, the author, where to go and find
>> documentation, and so on.
>> The DOAP and FOAF schemas can express this information
>
> To whom or what ? If the destination is a human, something
> like
>
> # Author: Steve Harris
> # License: GLPv2
>
> would seem a bit more user friendly.

These are macro declarations. When a computer reads and
processes the .ttl file, it will expand

    rdf:foo

Into

    <http://www.w3.org/1999/02/22-rdf-syntax-ns#foo>

(Or something like that.)

The intention with the plugins is that all metadata is able
to be parsed by the computer and presented to the end-user
in the host application.

> After reading that for the N-th time, it's not clear at all if
> the lines quoted above (from that very file) are required or not,

You DO NOT need these macros unless you want to use them to
save on typing (and human-readability).

> and *if* they are required, for what purpose - how this information
> is used. If the links are not followed, they are little more than
> magic incantations. Does the software that reads someplugin.ttl
> depend on these things or not (AFAICS it doesn't) ?

They are globally unique ID's that refer to a published
(RDF) metadata schema.

-gabriel

_______________________________________________
Linux-audio-dev mailing list
Linux-audio-dev@email-addr-hidden
http://lists.linuxaudio.org/listinfo/linux-audio-dev
Received on Mon Jun 14 16:15:03 2010