X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient: geda-user AT delorie DOT com
Message-ID: <20140304202748.27343.qmail@stuge.se>
Date: Tue, 4 Mar 2014 21:27:48 +0100
From: Peter Stuge <peter AT stuge DOT se>
To: geda-user AT delorie DOT com
Subject: Re: [geda-user] Pin length stretch for schematics symbols useful?
Mail-Followup-To: geda-user AT delorie DOT com
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>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20140304124149.2ECEF807ABF4@turkos.aspodata.se>
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

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