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=googlemail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=/b81Wp+DW/sS8O7mia6rAVo/YhNPr8+MZ6EAH1wx/QU=; b=BI8MWcVsWxwIvCBhtA2ZDmq+BuHk1PCB9E4FUZiBjlYj44pDQD3OrchoBk8P3cA/D1 fgUsI6Qyp+GvFc637fVRZl0D7y7LAMbTupvIjY+UJ0Haou67U/m8l/G6+nRiD2iTmm5T m8INnKzlAIxI8y2TJo2zVKw9jHHOTS9hwYqsGZmmmzILp0ASYpjEYC8ewU5H5ltjnbz5 MkD/HZe5SdEndM2O6hjeQPIymoVYFsmCEBVcsvLIeMSEq0QaOj3zjsXe/nbYVpSWzqq5 3Ve/2NjjtcKqlHUX7iHwXvpNhk3eJmvhwJAZyFumv2JwSjJsKngctHagSWAxof1UJi3C aREg== MIME-Version: 1.0 X-Received: by 10.202.85.146 with SMTP id j140mr15107448oib.4.1450988727481; Thu, 24 Dec 2015 12:25:27 -0800 (PST) In-Reply-To: References: <1512221837 DOT AA25291 AT ivan DOT Harhan DOT ORG> <20151222232230 DOT 12633 DOT qmail AT stuge DOT se> <0F6F1D0F-4F07-48EA-90FE-836EAD4E2354 AT noqsi DOT com> <0FCF3774-F93C-4BFF-BB61-636F75DCCACB AT noqsi DOT com> Date: Thu, 24 Dec 2015 20:25:27 +0000 Message-ID: Subject: Re: [geda-user] A fileformat library From: "Peter Clifton (petercjclifton AT googlemail DOT com) [via geda-user AT delorie DOT com]" To: gEDA User Mailing List Content-Type: multipart/alternative; boundary=001a113d216eacbb4b0527aaa30b 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 --001a113d216eacbb4b0527aaa30b Content-Type: text/plain; charset=UTF-8 Whatever the syntax / parser / storage mechanism - be that sql, xml, yaml, json, sgml, csv, tsv, gschem, s-expr, P21 (one of the STEP encodings)....... it is WHAT we store and how it is structured that matters. Getting the data model right is almost completely independent of the rest - even if some may work more elegantly than others. Getting the data model right is also the hard bit - unfortunately. Peter --001a113d216eacbb4b0527aaa30b Content-Type: text/html; charset=UTF-8

Whatever the syntax / parser / storage mechanism - be that sql, xml, yaml, json, sgml, csv, tsv, gschem, s-expr, P21 (one of the STEP encodings)....... it is WHAT we store and how it is structured that matters.

Getting the data model right is almost completely independent of the rest - even if some may work more elegantly than others.

Getting the data model right is also the hard bit - unfortunately.

Peter

--001a113d216eacbb4b0527aaa30b--