X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f X-Recipient: geda-user AT delorie DOT com X-Original-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=date:from:to:subject:message-id:mime-version:content-type :content-transfer-encoding; bh=35WMFQahFQ6/xcUeWtnnDFuIwmouRFuWFsovCXc/RKM=; b=dppVpbNGrIOlnvXT0T+uvcMTNUGDX3hgc+XQU9aT2Qpz3n9Ds+jNQ0x6Nmryh/JMDs 4IMDQQmJtYYMJqJ69g+3mp0RPwNzanSWtkf5dE5ZhjNIdqebMm2tBqIFZybZ5hfE/8jr XXXh8UNoxPOsk0qUGtNN8WGewe0yXHDQ8+A8PCrkHHbEIt8IHvh9TGPjTsQ7Wvtlw2Ca 8C2QSW+7kRdv6LJmh2VQ5S9Wnf2mypvZjtLppWB+plJMJn2blqHjB7ofCEKHGbiAEJL7 aR6RbAYHBn9CsunqP0DeGv+kzVtHt34e4LGsTlVD9iFkBuT3L6tgQi7Sie5ZeTRoO+7U sImg== X-Received: by 10.28.13.138 with SMTP id 132mr14665043wmn.62.1450609345323; Sun, 20 Dec 2015 03:02:25 -0800 (PST) Date: Sun, 20 Dec 2015 12:02:19 +0100 From: "Nicklas Karlsson (nicklas DOT karlsson17 AT gmail DOT com) [via geda-user AT delorie DOT com]" To: geda-user AT delorie DOT com Subject: [geda-user] XML file format (what could be expected) Message-Id: <20151220120219.c4644eef1a65b0eb2fb60d76@gmail.com> X-Mailer: Sylpheed 3.5.0beta1 (GTK+ 2.24.25; x86_64-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Reply-To: geda-user AT delorie DOT com As XML have been up for discussion as fileformt, I guess this is what to expect http://kxmleditor.sourceforge.net/screenshots/screenshots.html I think about it as a way to express structured data similar to struct in "C" but have not studied all the details. I do not think file format is important. It is better to bring discussion to the structure itself, if visualized as a tree which forks and attributes are needed. 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. Nicklas Karlsson