X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient: geda-user AT delorie DOT com
X-Mailer: exmh version 2.8.0 04/21/2012 (debian 1:2.8.0~rc1-2) with nmh-1.5
X-Exmh-Isig-CompType: repl
X-Exmh-Isig-Folder: inbox
From: karl AT aspodata DOT se
To: geda-user AT delorie DOT com
Subject: Re: [geda-user] XML file format (what could be expected)
In-reply-to: <20151220120219.c4644eef1a65b0eb2fb60d76@gmail.com>
References: <20151220120219 DOT c4644eef1a65b0eb2fb60d76 AT gmail DOT com>
Comments: In-reply-to "Nicklas Karlsson (nicklas DOT karlsson17 AT gmail DOT com) [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com>
   message dated "Sun, 20 Dec 2015 12:02:19 +0100."
Mime-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Message-Id: <20151220122659.378AF809D791@turkos.aspodata.se>
Date: Sun, 20 Dec 2015 13:26:59 +0100 (CET)
X-Virus-Scanned: ClamAV using ClamSMTP
Reply-To: geda-user AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: geda-user AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk

Nicklas:
...
> For trees I only know about one implementation detail that matter:
> There could be a list of forks or each item reference it's parent.
> In XML forks are put "inside" it's parents delimiters and I guess
> this will avoid situations there it is possible with a loop or forks grow together.

If you want a tree structure you could just as well use the
filesystem, and if you want to make it just one file, use tar.
There is no reason to invent "new" fileformats for that.

Regards,
/Karl Hammar

-----------------------------------------------------------------------
Aspö Data
Lilla Aspö 148
S-742 94 Östhammar
Sweden
+46 173 140 57