16 Jul
2006
16 Jul
'06
3:28 p.m.
i notice this file: http://lv2plug.in/spec/lv2.ttl is in the nicely readable turtle
format. my main question is, whether this will be transformed to RDF-XML during 'make
install' or perhaps by the developer themselves (Eg, similar to leaving a configure
script around for those who dont have autoconf).
mainly beacuse, it seems RDF-XML is the dominant serialization format, and having this
additional dependency stand in the way means, at the very least one can't use Pyrple
out of the box. i installed Redland and the Ruby and TCL bindings, and both conspicuously
left out the "Redland::Parser.turtle" method, presumably beacuse i dont have it
installed (and it's not in portage...)
cheers
16 Jul
16 Jul
3:35 p.m.
On Sun, 2006-07-16 at 17:28 +0000, carmen wrote:
i notice this file: http://lv2plug.in/spec/lv2.ttl is
in the nicely readable
turtle format. my main question is, whether this will be transformed to RDF-XML
during 'make install' or perhaps by the developer themselves (Eg, similar to
leaving a configure script around for those who dont have autoconf).
I hope not - I've already written a host that parses Turtle and only
Turtle.
--
Lars Luthman - please encrypt any email sent to me if possible
PGP key: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x04C77E2E
Fingerprint: FCA7 C790 19B9 322D EB7A E1B3 4371 4650 04C7 7E2E
3:38 p.m.
On Sun Jul 16, 2006 at 07:35:19PM +0200, Lars Luthman wrote:
On Sun, 2006-07-16 at 17:28 +0000, carmen wrote:
you hope not what? it just seems like Turtle should be developers choice, and the format
in the .bundle should be more standard - even Firefox can parse RDF/XML out of the box.
the vast majority of the cool tools like Fresnel/Protoge that some develoeprs might want
to edit their schemas in, don't support Turtle as well, AFAIK..
i notice this file:
http://lv2plug.in/spec/lv2.ttl is in the nicely readable
turtle format. my main question is, whether this will be transformed to RDF-XML
during 'make install' or perhaps by the developer themselves (Eg, similar to
leaving a configure script around for those who dont have autoconf).
I hope not - I've already written a host that parses Turtle and only
Turtle.
3:52 p.m.
you hope not what? it just seems like Turtle should be
developers choice, and the format in the .bundle should be more standard - even Firefox
can parse RDF/XML out of the box. the vast majority of the cool tools like Fresnel/Protoge
that some develoeprs might want to edit their schemas in, don't support Turtle as
well, AFAIK..
my main issue is the only RDF toolkit in Portage didnt properly include Turtle parsing.
which means theres an even slimmer chance of such things existing in Debian, Fedora, etc.
now i must investigate why this is the case.. on top of that, a lot of the ideas wrt
interactive documentation (eg wiki-style annotations of what ports actually do, user
presets, etc) on the web would be easier since RDF/XML is readily embeddable into XHTML.
throwing a 'raptor blahblah.ttl > blahblah.xml' in a SConstruct is praobly
easier than having to continually think about it on the server side (eg in PHP) or in
JavaScript..
8:12 p.m.
On Sun, Jul 16, 2006 at 05:52:15PM +0000, carmen wrote:
You can't "easily" embed RDF/XML into XHTML, you can use RDF/A or GRDDL,
but that's different. You can apply the same conversion argument just as
well the other way round. I have some PHP scripts that conneg LV2 turtle
files into HTML (still very primitive) or RDF/XML as required, it's not
exactly hard.
- Steve
you hope not
what? it just seems like Turtle should be developers choice, and the format in the .bundle
should be more standard - even Firefox can parse RDF/XML out of the box. the vast majority
of the cool tools like Fresnel/Protoge that some develoeprs might want to edit their
schemas in, don't support Turtle as well, AFAIK..
my main issue is the only RDF toolkit in Portage didnt properly include Turtle parsing.
which means theres an even slimmer chance of such things existing in Debian, Fedora, etc.
now i must investigate why this is the case.. on top of that, a lot of the ideas wrt
interactive documentation (eg wiki-style annotations of what ports actually do, user
presets, etc) on the web would be easier since RDF/XML is readily embeddable into XHTML.
throwing a 'raptor blahblah.ttl > blahblah.xml' in a SConstruct is praobly
easier than having to continually think about it on the server side (eg in PHP) or in
JavaScript..
8:07 p.m.
On Sun, Jul 16, 2006 at 05:38:15PM +0000, carmen wrote:
On Sun Jul 16, 2006 at 07:35:19PM +0200, Lars Luthman
wrote:
I've never heard of Fresnel, but Protege can read N3, which is a superset
of Turtle. There's some pretty strong anti-XML feeling in this community,
and Turtle was less contraversial all round.
Personally I prefer reading and writing Turtle to RDF/XML, which is pretty
hideous. If your tool of choice can't read Turtle directly, just use
something like rapper to turn it into RDF/XML first.
- Steve
On Sun, 2006-07-16 at 17:28 +0000, carmen wrote:
you hope not what? it just seems like Turtle should be developers choice, and the format
in the .bundle should be more standard - even Firefox can parse RDF/XML out of the box.
the vast majority of the cool tools like Fresnel/Protoge that some develoeprs might want
to edit their schemas in, don't support Turtle as well, AFAIK.. i notice this file:
http://lv2plug.in/spec/lv2.ttl is in the nicely readable
turtle format. my main question is, whether this will be transformed to RDF-XML
during 'make install' or perhaps by the developer themselves (Eg, similar to
leaving a configure script around for those who dont have autoconf).
I hope not - I've already written a host that parses Turtle and only
Turtle. 
10:33 p.m.
On Sun, 2006-07-16 at 17:28 +0000, carmen wrote:
i notice this file: http://lv2plug.in/spec/lv2.ttl is
in the nicely readable turtle format. my main question is, whether this will be
transformed to RDF-XML during 'make install' or perhaps by the developer
themselves (Eg, similar to leaving a configure script around for those who dont have
autoconf).
mainly beacuse, it seems RDF-XML is the dominant serialization format, and having this
additional dependency stand in the way means, at the very least one can't use Pyrple
out of the box. i installed Redland and the Ruby and TCL bindings, and both conspicuously
left out the "Redland::Parser.turtle" method, presumably beacuse i dont have it
installed (and it's not in portage...)
cheers
Why would you want to take a nice, readable format, and translate it
into the confusing bloated mess that is RDF/XML automatically and by
default? Because some particular toolkit can't read N3/Turtle yet?
Silly.
If the toolkit you want to use sucks, then you can convert the N3/Turtle
to RDF/XML yourself easily enough...
-DR-
17 Jul
17 Jul
6:24 a.m.
On Sun, Jul 16, 2006 at 08:33:08 -0400, Dave Robillard wrote:
On Sun, 2006-07-16 at 17:28 +0000, carmen wrote:
To be fair, Turtle is relativly new, whereas RDF/XML is about 10 years
old. There are some tools that don't yet handle Turtle.
I agree about the conversion though. Turtle is much more popular in these
parts, and the conversion is easily done either way.
- Steve
i notice this file:
http://lv2plug.in/spec/lv2.ttl is in the nicely readable turtle format. my main question
is, whether this will be transformed to RDF-XML during 'make install' or perhaps
by the developer themselves (Eg, similar to leaving a configure script around for those
who dont have autoconf).
mainly beacuse, it seems RDF-XML is the dominant serialization format, and having this
additional dependency stand in the way means, at the very least one can't use Pyrple
out of the box. i installed Redland and the Ruby and TCL bindings, and both conspicuously
left out the "Redland::Parser.turtle" method, presumably beacuse i dont have it
installed (and it's not in portage...)
cheers
Why would you want to take a nice, readable format, and translate it
into the confusing bloated mess that is RDF/XML automatically and by
default? Because some particular toolkit can't read N3/Turtle yet?
Silly.
If the toolkit you want to use sucks, then you can convert the N3/Turtle
to RDF/XML yourself easily enough...
6649
days inactive
6650
days old
linux-audio-dev@lists.linuxaudio.org
7 comments
4 participants
participants (4)
-
carmen -
Dave Robillard -
Lars Luthman -
Steve Harris