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=Gh8hKbSVasg/wedzLjdRY+HVfCgq4DjGMG8GZXlNZ+k=;
        b=vz4pUxuNIw3j5l4ZxUEXgVl9SpkH9BsOMj1mYRv+wNAOT7WMMDUQdikNRirMzJrOYm
         PlBmo7aSyfLwHEDVEX+UaXdPgDAp986uzoGBztsBwonNO60zuAR7KYsnaQOfzqTEZLtq
         2/x/qwB5OVXhG68ClD2Hh3xRX233QjJscnvJk7C+POwjj4+qbTZqLZdFww4aiAr6i8OA
         2P2Jslomz5nhIrGhOgyM6CurDSFMQfPvJGIohunsONoI3vtdrbUUUIFAcRJkWzB3Vhlf
         81Jx+EPBBYmeuOWKf2ouaHmd7spjMw9u9kcr3qfXCzTioHDrDSJyC5aP7EhdfvwzVM4u
         DxNg==
MIME-Version: 1.0
X-Received: by 10.28.125.147 with SMTP id y141mr27342409wmc.18.1450812965499;
 Tue, 22 Dec 2015 11:36:05 -0800 (PST)
In-Reply-To: <CAJXU7q89cBkSZZfaS5p2CSDeJRTGCzNs+bNBjL8_KYQ=o7gi=Q@mail.gmail.com>
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>
	<CAJXU7q89cBkSZZfaS5p2CSDeJRTGCzNs+bNBjL8_KYQ=o7gi=Q AT mail DOT gmail DOT com>
Date: Tue, 22 Dec 2015 10:36:05 -0900
Message-ID: <CAC4O8c9NWpEb9fhxj1ohdSTCFnDsm=x+fZMVyV4VRxQ_whS6xg@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=001a1141997471b949052781b765
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

--001a1141997471b949052781b765
Content-Type: text/plain; charset=UTF-8

On Tue, Dec 22, 2015 at 4:50 AM, Peter Clifton (
petercjclifton AT googlemail DOT com) [via geda-user AT delorie DOT com] <
geda-user AT delorie DOT com> wrote:

> On 22 December 2015 at 04:39,  <gedau AT igor2 DOT repo DOT hu> wrote:
>
> > 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.
>
> This is true.. and I've pointed one of the key players in the AP210
> standard at this discussion thread, to see if any impact might be made
> on the situation.
>
> Personally, I doubt we can change the situation... the ISO is big and
> ugly, and we are _tiny_.
>

What I don't quite get is why, once they're already down to a price that is
as you point out really pretty damn cheap for what it is and probably
nowhere near covering real costs, they can't make the jump to free.  I
suspect its a situation like with AutoCAD where there are noisy voices out
there who don't really want it that available.

--001a1141997471b949052781b765
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 Tue, Dec 22, 2015 at 4:50 AM, Peter Clifton (<a href=3D"mailto:peter=
cjclifton AT googlemail DOT com">petercjclifton AT googlemail DOT com</a>) [via <a href=
=3D"mailto:geda-user AT delorie DOT com">geda-user AT delorie DOT com</a>] <span dir=3D"l=
tr">&lt;<a href=3D"mailto:geda-user AT delorie DOT com" target=3D"_blank">geda-use=
r AT delorie DOT com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" st=
yle=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span=
 class=3D"">On 22 December 2015 at 04:39,=C2=A0 &lt;<a href=3D"mailto:gedau=
@igor2.repo.hu">gedau AT igor2 DOT repo DOT hu</a>&gt; wrote:<br>
<br>
&gt; Nope. As far as I understood, we are considering the very first step o=
f a<br>
&gt; roadmap. The first step is about how to pick a file format or data<br>
&gt; structure. Peter proposed a specific standard and listed a lot of pros=
.<br>
&gt;<br>
&gt; My point is only this: not having the standard freely available is a c=
on<br>
&gt; that we should not ignore.<br>
<br>
</span>This is true.. and I&#39;ve pointed one of the key players in the AP=
210<br>
standard at this discussion thread, to see if any impact might be made<br>
on the situation.<br>
<br>
Personally, I doubt we can change the situation... the ISO is big and<br>
ugly, and we are _tiny_.<br></blockquote><div><br></div><div style=3D"">Wha=
t I don&#39;t quite get is why, once they&#39;re already down to a price th=
at is as you point out really pretty damn cheap for what it is and probably=
 nowhere near covering real costs, they can&#39;t make the jump to free.=C2=
=A0 I suspect its a situation like with AutoCAD where there are noisy voice=
s out there who don&#39;t really want it that available.</div><div style=3D=
""><br></div></div></div></div>

--001a1141997471b949052781b765--