MIME-Version: 1.0
In-Reply-To: <20140304202748.27343.qmail@stuge.se>
References: <1391043267 DOT 2058 DOT 19 DOT camel AT AMD64X2 DOT fritz DOT box>
	<20140303174655 DOT A167B807ABF3 AT turkos DOT aspodata DOT se>
	<1393874264 DOT 2120 DOT 51 DOT camel AT AMD64X2 DOT fritz DOT box>
	<20140304124149 DOT 2ECEF807ABF4 AT turkos DOT aspodata DOT se>
	<20140304202748 DOT 27343 DOT qmail AT stuge DOT se>
Date: Tue, 4 Mar 2014 15:21:18 -0800
Message-ID: <CAOP4iL1n4QtaxJovT+Yfn+WktOqSamAPY5M4a+YiESkNYuXNrQ@mail.gmail.com>
Subject: Re: [geda-user] Pin length stretch for schematics symbols useful?
From: Ouabache Designworks <z3qmtr45 AT gmail DOT com>
To: geda-user AT delorie DOT com
Content-Type: multipart/alternative; boundary=089e013d1a6050137b04f3d02939
Reply-To: geda-user AT delorie DOT com
Errors-To: nobody AT delorie DOT com
Precedence: bulk

--089e013d1a6050137b04f3d02939
Content-Type: text/plain; charset=ISO-8859-1

Yes, Lets call it the Electronic Data Interchange Format :)


Seriously I would like to help in this effort.  I am currently working on a
open source eda tool suite based
on ip-xact and extending it to support symbol graphics is a natural
extension.

John Eaton






On Tue, Mar 4, 2014 at 12:27 PM, Peter Stuge <peter AT stuge DOT se> wrote:

> karl AT aspodata DOT se wrote:
> > Think of, just one symbol.
>
> Creating a universal data model for parts is indeed key for free and
> open source EDA software to have any kind of significant impact in
> the world.
>
> But it is no small task!
>
> It is also not a task that neccessarily has anything to do with
> existing EDA suites, beyond that the data model must of course not
> repeat any mistakes that have already been made in existing programs.
>
> The data model exists between EDA suites, fabs and part vendors.
> (User requirements flow from EDA suit and/or fab.)
>
> The model must encompass every real-world characteristic of parts
> which EDA suites and fabs care about today, and ideally also be
> future-proof enough that the same model can be extended, as EDA
> suites and fabs learn to make use of even more part characteristics
> in the future.
>
> The project as I see it would have as deliverables a specification
> document and a portable C library implementing the specification.
>
> I'd suggest a permissive license such as MIT for the implementation,
> so that the door is open for closed source EDA suites and fab tools
> to use the library later on, thus giving the project a chance to
> eliminate the ridiculous exclusivity of parts within single EDA suite
> vendors, and allow for somehow sensible integration across the full
> design and production cycle.
>
> Anyone else interested in this?
>
>
> //Peter
>

--089e013d1a6050137b04f3d02939
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div><div><div>Yes, Lets call it the Electronic Data Inter=
change Format :)<br><br><br></div>Seriously I would like to help in this ef=
fort.=A0 I am currently working on a open source eda tool suite based <br><=
/div>
on ip-xact and extending it to support symbol graphics is a natural extensi=
on.<br><br></div>John Eaton<br><br><div><div><div><div><br><br><br></div></=
div></div></div></div><div class=3D"gmail_extra"><br><br><div class=3D"gmai=
l_quote">
On Tue, Mar 4, 2014 at 12:27 PM, Peter Stuge <span dir=3D"ltr">&lt;<a href=
=3D"mailto:peter AT stuge DOT se" target=3D"_blank">peter AT stuge DOT se</a>&gt;</span> =
wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;bord=
er-left:1px #ccc solid;padding-left:1ex">
<a href=3D"mailto:karl AT aspodata DOT se">karl AT aspodata DOT se</a> wrote:<br>
&gt; Think of, just one symbol.<br>
<br>
Creating a universal data model for parts is indeed key for free and<br>
open source EDA software to have any kind of significant impact in<br>
the world.<br>
<br>
But it is no small task!<br>
<br>
It is also not a task that neccessarily has anything to do with<br>
existing EDA suites, beyond that the data model must of course not<br>
repeat any mistakes that have already been made in existing programs.<br>
<br>
The data model exists between EDA suites, fabs and part vendors.<br>
(User requirements flow from EDA suit and/or fab.)<br>
<br>
The model must encompass every real-world characteristic of parts<br>
which EDA suites and fabs care about today, and ideally also be<br>
future-proof enough that the same model can be extended, as EDA<br>
suites and fabs learn to make use of even more part characteristics<br>
in the future.<br>
<br>
The project as I see it would have as deliverables a specification<br>
document and a portable C library implementing the specification.<br>
<br>
I&#39;d suggest a permissive license such as MIT for the implementation,<br=
>
so that the door is open for closed source EDA suites and fab tools<br>
to use the library later on, thus giving the project a chance to<br>
eliminate the ridiculous exclusivity of parts within single EDA suite<br>
vendors, and allow for somehow sensible integration across the full<br>
design and production cycle.<br>
<br>
Anyone else interested in this?<br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
<br>
//Peter<br>
</font></span></blockquote></div><br></div>

--089e013d1a6050137b04f3d02939--