From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <45219fb00705230012uf3a3712q69efba8a1f6327e2@mail.gmail.com>
Date: Wed, 23 May 2007 09:12:55 +0200
From: "=?ISO-8859-1?Q?Llu=EDs_Batlle?=" <viriketo@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] XML
In-Reply-To: <775b8d190705220755h2860c78ek80d3035bc2640291@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <4652F7E7.4050408@authentrus.com>
	<5344b7b5944391eefb6047acb8ed55d7@coraid.com>
	<775b8d190705220755h2860c78ek80d3035bc2640291@mail.gmail.com>
Topicbox-Message-UUID: 70a7a7ec-ead2-11e9-9d60-3106f5b1d025

I find that most of the tree-like information I want to store in a fd
fits well on OGDL (1st layer). I think Forsyth was working on a OGDL
parser in limbo - I don't know if he finished or stopped thinking on
it.

I wrote my own in c++, and I used a j2me implementation given in the
OGDL main site - them both work fine.

2007/5/22, Bruce Ellis <bruce.ellis@gmail.com>:
> to throw a spaniard in the works (never was good at mangling metaphors)
> i use XML to store midi patches and configs.  as a human never edits
> them directly (the pre-existing library does that) it was a good choice.
> i considerered an ndb approach, and S-expressions, but i like what i got.
>
> i could have invented a file format and implemented it but i chose not to.
>
> you wouldn't want to read or write any configuration for something
> with a thousand params  but programs do it fine.
>
> brucee
>
> On 5/23/07, erik quanstrom <quanstro@coraid.com> wrote:
> > however, one end would be *heading* north.  the other would be
> > *heading* south.
> >
> > - erik
> >
>