On Mon, Jun 14, 2010 at 08:04:06AM +0100, Steve Harris wrote:
> On 2010-06-13, at 21:17, firstname.lastname@example.org wrote:
To whom or what ? If the destination is a human, something
# Author: Steve Harris
# License: GLPv2
would seem a bit more user friendly.
> and are widely used on the internet (there are in excess of 200M
I've never seen one. And certainly when I'd see one it wouldn't
look very inviting to read it. Is this meant for humans ? If not
*which software is reading this, and what is it doing with the
information provided* ?
> > If this has to be part of an LV2 plugin somehow (and it's not
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,
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) ?
> > I'm more and more convinced that people creating these sort of
It's not an attack but an opinion, and certainly not directed at
you (Steve) personally. If I wanted to attack you 'ad hominem'
I would not choose a subject in which you are 1000 time more expert
than I am - it would be very easy to select one where the roles
would be reversed.
> I'm not quite sure why you have come to such a dismissive
Such a mass hysteria wouldn't be the first one - we've seem some
bubbles bursting before. And whatever problem these companies
are solving seem to be quite remote from audio plugins.
The essential point in my comment is that it is foolish to confuse
the 'semantic web' with reality. Are your 13857 Facebook friends
real friends ? Are those 200e6 'FOAFs' what they claim to be ?
Back to the technical side, it all seems as futile as including
a complete BNF of the C language (or a reference to it) at the top
of each *.c source file. It's useless to the compiler (which is not
going to modify itself), and it's useless for the human reading or
editing the file.
And again, if in the end information such as e.g. port min, max,
default, etc. has its intended effect, that does not happen magically
because of the RDF. It happens only because some human at some point
understands the meaning of these terms and their intended use.
If the RDF form would really convey meaning by itself, you should
be able to replace e.g. 'min, max, default' by 'sdf45xef, j73dfhshf,
sdclkle82), and they would still have the intended effect. This is
clearly *not* the case, it all depends on a human understanding
those words, and a human can perfectly (and even much more easily)
understand these without all the semantic gobbledegook.
O tu, che porte, correndo si ?
E guerra e morte !
Linux-audio-dev mailing list