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=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type;
        bh=BpzFSA/XjrvXj7PLtuObCK5XP9nXQHjufM/jDlEVGl4=;
        b=r0cOJttOXiy3MXmTLumE8NUQnbBuHyIdnUjMXpOBvpUiJMUkQwIm9ayxJL9lfTwMDs
         sTgYtsJLKJC2KqwoH9qGeO3ttTfdojWmqSg1QQrA4nUxMqzf3pZJqe2pZkMEz0s8qdkE
         xcEbJORa1Ir5s8tGboQvLJU+CMyYGMXeqQdrbR5uYSaLJghw4syURBAEMIkcAJ2KB/S/
         SP8pTnzs2TRElRv+2/yrNYCfG2jtQsWB1Wk+u5snJ/7exrR6+MLrEMsoKpHYRnOWAd8R
         XHKv6GI11CptWdVBX2hy8UQE3KEcl+Vur3KXzMZYsnTaNyDj2A2jAHGISnIaoEycosT3
         X5mA==
MIME-Version: 1.0
X-Received: by 10.194.173.233 with SMTP id bn9mr29190185wjc.1.1450812663377;
 Tue, 22 Dec 2015 11:31:03 -0800 (PST)
In-Reply-To: <alpine.DEB.2.00.1512220528100.9035@igor2priv>
References: <CAOFvGD6OiYxcGkOiQRVnvXW3TLs42bt7PE5Ot9s09hsukYicKA AT mail DOT gmail DOT com>
	<20151221030451 DOT 02399163eb3e40f21c622c41 AT gmail DOT com>
	<CAOP4iL1PTdeCZdT+SthHwQtaxC4x06MbBQmxRcK3DZyQ-jfw=Q AT mail DOT gmail DOT com>
	<20151221203331 DOT 20837 DOT qmail AT stuge DOT se>
	<CAJXU7q_XOJStJXhD547xW-+XROkBhctmMAWB-jm0cez5UvgZ7w AT mail DOT gmail DOT com>
	<CAOP4iL1ri4UMeYr01Af-AH005DkLboKO72nGao+ByGmqA51W-A AT mail DOT gmail DOT com>
	<20151222002012 DOT a88d7fe32a9336855eccd1d0 AT gmail DOT com>
	<CAJXU7q9dU=z5KZmgsh+Vau4zZNfEh4Awr5xdzL=6xhimLYVNLw AT mail DOT gmail DOT com>
	<alpine DOT DEB DOT 2 DOT 00 DOT 1512220421160 DOT 9035 AT igor2priv>
	<201512220412 DOT tBM4CJxb018546 AT envy DOT delorie DOT com>
	<alpine DOT DEB DOT 2 DOT 00 DOT 1512220528100 DOT 9035 AT igor2priv>
Date: Tue, 22 Dec 2015 10:31:03 -0900
Message-ID: <CAC4O8c_cy_r3Qp9fnf8ef5eKW92S1KXAuKD0rexvVuSk2Cvv_g@mail.gmail.com>
Subject: Re: [geda-user] Proposing a New Hierarchical Data Structure?
From: "Britton Kerin (britton DOT kerin AT gmail DOT com) [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com>
To: geda-user AT delorie DOT com
Content-Type: multipart/alternative; boundary=089e0122f0886fba89052781a538
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

--089e0122f0886fba89052781a538
Content-Type: text/plain; charset=UTF-8

On Mon, Dec 21, 2015 at 7:39 PM, <gedau AT igor2 DOT repo DOT hu> wrote:

>
>
> On Mon, 21 Dec 2015, DJ Delorie wrote:
>
>
>> Despite of all the huge amount of work the have invested, unless they make
>>> the work really publicly available, I'd prefer not building on it.
>>>
>>
>> I.e. you want someone to either steal the work for you, or do a great
>> deal of work on your behalf without any compensation?
>>
>
> Nope. As far as I understood, we are considering the very first step of a
> roadmap. The first step is about how to pick a file format or data
> structure. Peter proposed a specific standard and listed a lot of pros.
>
> My point is only this: not having the standard freely available is a con
> that we should not ignore.


Seconded.  STEP its a huge pain in the behind because no free software
supports it.  I had to have a copy of solid works on windows for nothing
but export to STEP, so I could have parts designed with openSCAD actually
manufactured.  That was a while ago and now 3D printing has forced
manufacturers to support STL.  With that happening I doubt very much that
FOSS support for STEP has improved much.  In any case *something* is
definitely stopping STEP adoption in FOSS and it's a good bet its the
relative unavailability of the standard.

--089e0122f0886fba89052781a538
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><div class=3D"gmail_quo=
te">On Mon, Dec 21, 2015 at 7:39 PM,  <span dir=3D"ltr">&lt;<a href=3D"mail=
to:gedau AT igor2 DOT repo DOT hu" target=3D"_blank">gedau AT igor2 DOT repo DOT hu</a>&gt;</span=
> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;bo=
rder-left:1px #ccc solid;padding-left:1ex"><span class=3D""><br>
<br>
On Mon, 21 Dec 2015, DJ Delorie wrote:<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
Despite of all the huge amount of work the have invested, unless they make<=
br>
the work really publicly available, I&#39;d prefer not building on it.<br>
</blockquote>
<br>
I.e. you want someone to either steal the work for you, or do a great<br>
deal of work on your behalf without any compensation?<br>
</blockquote>
<br></span>
Nope. As far as I understood, we are considering the very first step of a r=
oadmap. The first step is about how to pick a file format or data structure=
. Peter proposed a specific standard and listed a lot of pros.<br>
<br>
My point is only this: not having the standard freely available is a con th=
at we should not ignore.</blockquote><div><br></div><div style=3D"">Seconde=
d.=C2=A0 STEP its a huge pain in the behind because no free software suppor=
ts it.=C2=A0 I had to have a copy of solid works on windows for nothing but=
 export to STEP, so I could have parts designed with openSCAD actually manu=
factured.=C2=A0 That was a while ago and now 3D printing has forced manufac=
turers to support STL.=C2=A0 With that happening I doubt very much that FOS=
S support for STEP has improved much.=C2=A0 In any case *something* is defi=
nitely stopping STEP adoption in FOSS and it&#39;s a good bet its the relat=
ive unavailability of the standard.</div><div><br></div></div></div></div>

--089e0122f0886fba89052781a538--