26 May
2004
26 May
'04
8:54 p.m.
[Steve Harris]
i like this approach better than the lisp proposal, most importantly
because it gives us free choice of language for the metadata file
parser. besides, imo it offers much more intuitive syntax, not to
mention existing support software for machine-based data mangling.
other than that, i'm eager to know how plugin ports are to be
referenced in the metadata file. by ID or numerical index? if by ID,
is it the full path to the port: "/SupaPlug/LFO 1/Frequency", or
something more concise? (i'm for a full path scheme because it
allows the plugin writer to reorder ports painlessly.)
tim
On Tue, May 18, 2004 at 10:29:56 -0500, Jack O'Quin
wrote:
> I've been reading up on Steve's N-triples suggestion...
[...]
(1) It is a
W3C standard.
(2) It is mathematically deep and well thought out.
(3) It is specifically intended for adding property lists to the web
(4) The syntax is well-defined
(5) No large parsing library is needed
(6) There are tools for converting to XML
And from, more importantly. It can also be converted to from the other human
friendly RDF syntaxes; N3 and Turtle. Infact NTriples is a valid subset of
both those.