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:in-reply-to:references:mime-version
         :content-transfer-encoding;
        bh=6QA5lZZ6ooEOGL3uapE2pp6Iqv5LdVbfN0w5tSBxA9Q=;
        b=cAdu6GAf27w2v5+erFL2nMKwp8sGB7XCLaOMVfzTbOpm9/38URuv3/VIZsxQtDRP3x
         VnI5vfYlJB9KvdbnlLz4updMCMQe/GD/z0GKQIUn5xCHvEghTnB4/crTFDpdy7KZ+UPM
         erHjp9qykHPa+TGChva3qJF9VUwB2yGDUx+hYPwTtqXkxdSUXV/jtNg8rvfG0H4wWFYK
         jvKACnuA/oNSb7CKWduhBKnZ+1yU8Ft7SfA69j1lLPC09MVjnWrtTvIRZFJ9h9JZk1u8
         LWothQjBcP+W9L9nwpWPVgKpf5BpccCbPC3lnMwGbrqBpbtHhqqiJ3sYgWU7uGzd7z7B
         1G0A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=1e100.net; s=20130820;
        h=x-gm-message-state:date:from:to:subject:message-id:in-reply-to
         :references:mime-version:content-transfer-encoding;
        bh=6QA5lZZ6ooEOGL3uapE2pp6Iqv5LdVbfN0w5tSBxA9Q=;
        b=KcO2lHQlUSpNPvYlZaBS9Kw3wX95ja7l/yzmKEckl9p6N4+1LDEJ7r4D4PKggQN9eE
         Vk54O2vCOSCCnkaVn0rJy45eCffA62PCnSQPifCalIcK7TOskh+NDSGAuYq65gJXZ1DW
         InW7idQZAyWXd4aW1rqFUOF4Fr0MHvjQ+Xez4E4xWu+Ja1Mu8z9EuoYgcmppGaxHF02N
         yD1ga448zuPaeVQ+9lVVOiB+P71yZbIRWOfDPZlBEH6FuN2VVpzUWUVUZC/w7W8RTmmm
         2KqZxGaikLY7xozmEtjdCQFssBZ37L4XsVJd9n+P6oeoQgQbrVMpDbzdUKoTVqQlkVbg
         5+Cg==
X-Gm-Message-State: AE9vXwMkqCgv7RQU3S6lpXJQkBYTXuVQfkCzdtfbCI9cJCslLdMygkJVrVO/1zkkNn63QA==
X-Received: by 10.28.232.15 with SMTP id f15mr4744709wmh.51.1472842326573;
        Fri, 02 Sep 2016 11:52:06 -0700 (PDT)
Date: Fri, 2 Sep 2016 20:52:01 +0200
From: "Nicklas Karlsson (nicklas DOT karlsson17 AT gmail DOT com) [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com>
To: geda-user AT delorie DOT com
Subject: Re: [geda-user] Microwave PCB layout simulation or How to eat all
 your processing power in 3 easy steps
Message-Id: <20160902205201.ad551647ff4d26e2b0aa83e9@gmail.com>
In-Reply-To: <20160902130531.7bb9f962@floyd.freeelectron.net>
References: <CAM2RGhT_pQZ8CGGM6ECwDUwJHeo3UwDJ6d_7RtVWhxJBQ=K1tA AT mail DOT gmail DOT com>
	<57C09C3C DOT 7020708 AT xs4all DOT nl>
	<20160826171545 DOT 2bc54995 AT floyd DOT freeelectron DOT net>
	<CAM2RGhQJJmbhKBsX5K495jDRid5px33d4MKcFN8cv2MNTkRQMg AT mail DOT gmail DOT com>
	<20160827013103 DOT 63bb0bdd AT floyd DOT freeelectron DOT net>
	<CAM2RGhSb3-KdN3rMo5vxjkbTO+-vU_Tgj+hOcoHxyz4HGwnzbA AT mail DOT gmail DOT com>
	<20160831130045 DOT 27d23a85 AT floyd DOT freeelectron DOT net>
	<092F0F0F-5FD0-4792-9526-F0D26F029133 AT noqsi DOT com>
	<20160902130531 DOT 7bb9f962 AT floyd DOT freeelectron DOT net>
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
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

> But I did not propose a new standard.  I just suggested a way to
> preserve placement info in the netlist, preserving a lot more info than
> just what Spice does.
> 
> Meanwhile .. we have all those posts about xml, json, and others.  You
> might say that those are existing standards, but in this context they
> are not, any more than C-like, lisp-like, and others might be standards
> for this application.

xml may bring structure, json I do not know about. What is needed is rules for what structures are allowed and what meaning they should have. Type need to be known for stored values and allowed range. I have no idea if this is part of any file format and if there are such intepreters available. To use the data structures from an ordinary programming language might be a good solution.