X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f X-Recipient: geda-user AT delorie DOT com X-TCPREMOTEIP: 207.224.51.38 X-Authenticated-UID: jpd AT noqsi DOT com From: John Doty Content-Type: multipart/alternative; boundary="Apple-Mail=_AE3D780D-B899-4219-9577-C313CF5A0D3F" Message-Id: <218C63C4-B2B5-4DFB-A995-B170E7591B6F@noqsi.com> Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) Subject: Re: [geda-user] Any news about FOSS EDA coordination? Import/export, common file format Date: Wed, 10 Jun 2015 10:25:18 -0600 References:

<20150608222056 DOT 10601 DOT qmail AT stuge DOT se> To: geda-user AT delorie DOT com In-Reply-To: X-Mailer: Apple Mail (2.1878.6) 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 --Apple-Mail=_AE3D780D-B899-4219-9577-C313CF5A0D3F Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=windows-1252 On Jun 9, 2015, at 2:53 PM, timofonic timofonic (timofonic AT gmail DOT com) = wrote: > Something similar to OpenDocument but for electronics. But OpenDocument is not universal: it doesn=92t serve the LaTeX and = troff communities. And geda-gaf, in particular, is well adapted to = *automated* data-product generation, like LaTeX but unlike the manual = GUI tools that use OpenDocument. Indeed, the makefiles for my LaTeX = documents drag in data from geda-gaf. The other issue is that some parts of the flow are easier to standardize = and adapt than others. Netlists and BOMs are collections of simple = =93relations" in database jargon. Translating to/from a standardized = format is a routine database manipulation job. But schematics and = layouts are not simple abstractions, and different tools encode them in = fundamentally different ways. There was once an effort to do this: EDIF. A lot of people and companies = put a lot of effort into it, and it failed. But an effort that = concentrated on the feasible parts of the problem, netlists and BOMs, = might succeed. John Doty Noqsi Aerospace, Ltd. http://www.noqsi.com/ jpd AT noqsi DOT com --Apple-Mail=_AE3D780D-B899-4219-9577-C313CF5A0D3F Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=windows-1252

On Jun 9, 2015, at 2:53 PM, timofonic = timofonic (timofonic AT gmail DOT com)= <geda-user AT delorie DOT com> = wrote:

Something similar to OpenDocument but = for electronics.

But OpenDocument is = not universal: it doesn=92t serve the LaTeX and troff communities. And = geda-gaf, in particular, is well adapted to *automated* data-product = generation, like LaTeX but unlike the manual GUI tools that use = OpenDocument. Indeed, the makefiles for my LaTeX documents drag in data = from geda-gaf.

The other issue is that some = parts of the flow are easier to standardize and adapt than others. = Netlists and BOMs are collections of simple =93relations" in database = jargon. Translating to/from a standardized format is a routine database = manipulation job. But schematics and layouts are not simple = abstractions, and different tools encode them in fundamentally different = ways.

There was once an effort to do this: = EDIF. A lot of people and companies put a lot of effort into it, and it = failed. But an effort that concentrated on the feasible parts of the = problem, netlists and BOMs, might succeed.

John Doty Noqsi = Aerospace, Ltd.

http://www.noqsi.com/

jpd AT noqsi DOT com

= --Apple-Mail=_AE3D780D-B899-4219-9577-C313CF5A0D3F--