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=googlemail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=scDLmcEDd/s2q4pOKk/otk20/xYtWAvuXxaqX18LZtA=; b=M9z9CTx1RSbvePeR27MgTBl6QSj8o1HWowrtbDOg4HMkWuoZBOtdH/KDHiZYkDQZwc S4K/lGldLBrvIj6rSWlc+ZFPlP28kaisrWN9TpTM92Fhf5dytmlrnklQ2tJ5aykxYUfY OC+aLJzwblmuk0sYSH1fcLro5+tSbogDMudAC7qvc4N8NYF3J7jVi0umrnuNKuDHYpkd QUEQMfvGEAoOUA2K1knmruOauYpSXuW0JVfffR+RYjDP5TdxcjDES8e1YsPv/m6o57FW rAPZ00KlQ/srgFPwgxZs/i5R6ov6R2isJwsuVv79t5It14mv4h3BJ+jGP6uLgmHjVGFA AKUg== MIME-Version: 1.0 X-Received: by 10.182.225.132 with SMTP id rk4mr9625546obc.68.1450779931545; Tue, 22 Dec 2015 02:25:31 -0800 (PST) In-Reply-To: References: <20151221030451 DOT 02399163eb3e40f21c622c41 AT gmail DOT com> <20151221203331 DOT 20837 DOT qmail AT stuge DOT se> <20151222002012 DOT a88d7fe32a9336855eccd1d0 AT gmail DOT com> <201512220412 DOT tBM4CJxb018546 AT envy DOT delorie DOT com> Date: Tue, 22 Dec 2015 10:25:31 +0000 Message-ID: Subject: Re: [geda-user] Proposing a New Hierarchical Data Structure? From: "Peter Clifton (petercjclifton AT googlemail DOT com) [via geda-user AT delorie DOT com]" To: gEDA User Mailing List Content-Type: multipart/alternative; boundary=001a11c3253477994205277a0646 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 --001a11c3253477994205277a0646 Content-Type: text/plain; charset=UTF-8 I really sympathise with the point about the standard not being freely accessible. The same also applies for many of the academic papers behind things like the auto routers in pcb. The standard authors understand this... The best compromise the ISO would allow them to make, was this: They give away the data model (the bit you need to make data structures that match the standard, parsers, interface libraries, validators etc....) They were also able to roll the text of almost all of the hundreds (thousands?) of standard sub-parts and resources, and put them on a CD, made available for about 380chf. I'm told this was a huge compromise for the ISO, and one they had to fight hard for. Normally these parts would all be individually chargeable (at significant cost). If you see the sheer size of the standard, you might begin to appreciate that the fee they charge is actually very good value. I'm also told that the fees from this effort are not paying any of the costs of developing the standard - just running the ISO. Actual development costs are sponsored by the considerable time that individuals and the companies employing them have put in. We might wish that in some ideologically better world, that it had been developed and licenced in a way that makes it open and redistributible, but this is not reality. Since I'm not in a position where I have the resources to devote to developing gEDA at the moment, my opinion is merely that. It will ultimately be up to those who are doing the development work to decide how they approach it, and whether they do or don't choose to obtain and utilise this standard to inform and strengthen their work. Kind regards, Peter Clifton On 22 Dec 2015 04:39, 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. > > >> I don't think either of these are valid ways to run a project. The >> ISO standards are always copyright protected and sold for a fee; >> that's how ISO funds its operation. Much of the software you use >> today is built on ISO standards - including the C/C++ language that >> gEDA uses. >> >> The ISO standards are publically available, for a fee. They are not >> "proprietary" or "secret", just not "free of charge". >> > > Ok, so if I buy it once, can I just include a copy in the documentation of > the software dostribution? I assume not. For me this makes it non-free, > not the price I paid for it. > > And I do hate when this happens with any of the standards, including ANSI > or ISO standards, including C. I still do use C, but that doesn't mean I > have to like or deny the non-free aspects. > > So if you want to refrain from using this standard because you feel >> it's too expensive for you to purchase, fine. But please do not >> confuse the "free" in "free software" with "everything else should be >> available to me without charge too". Even the FSF charges a fee for >> its software, to fund its activities. >> > > I did not say I wanted to refrain from using the standard because it was > expensive. It was your (mis)interpretation. I said a drawback of the > standard is that it is non-free (not mainly in the charge sense). > > I am wondering how this thread went into the usual senseless geda flamewar > this fast... > > --001a11c3253477994205277a0646 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

I really sympathise with the point about the standard not be= ing freely accessible.

The same also applies for many of the academic papers behind= things like the auto routers in pcb.

The standard authors understand this...

The best compromise the ISO would allow them to make, was th= is:

They give away the data model (the bit you need to make data= structures that match the standard, parsers, interface libraries, validato= rs etc....)

They were also able to roll the text of almost all of the hu= ndreds (thousands?) of standard sub-parts and resources, and put them on a = CD, made available for about 380chf. I'm told this was a huge compromis= e for the ISO, and one they had to fight hard for. Normally these parts wou= ld all be individually chargeable (at significant cost).

If you see the sheer size of the standard, you might begin t= o appreciate that the fee they charge is actually very good value.

I'm also told that the fees from this effort are not pay= ing any of the costs of developing the standard - just running the ISO. Act= ual development costs are sponsored by the considerable time that individua= ls and the companies employing them have put in.

We might wish that in some ideologically better world, that = it had been developed and licenced in a way that makes it open and redistri= butible, but this is not reality.

Since I'm not in a position where I have the resources t= o devote to developing gEDA at the moment, my opinion is merely that.

It will ultimately be up to those who are doing the developm= ent work to decide how they approach it, and whether they do or don't c= hoose to obtain and utilise this standard to inform and strengthen their wo= rk.

Kind regards,

Peter Clifton

On 22 Dec 2015 04:39, <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<= br> 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 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.

My point is only this: not having the standard freely available is a con th= at we should not ignore.


I don't think either of these are valid ways to run a project.=C2=A0 Th= e
ISO standards are always copyright protected and sold for a fee;
that's how ISO funds its operation.=C2=A0 Much of the software you use<= br> today is built on ISO standards - including the C/C++ language that
gEDA uses.

The ISO standards are publically available, for a fee.=C2=A0 They are not "proprietary" or "secret", just not "free of charg= e".

Ok, so if I buy it once, can I just include a copy in the documentation of = the software dostribution? I assume not. For me this makes it non-free,
not the price I paid for it.

And I do hate when this happens with any of the standards, including ANSI o= r ISO standards, including C. I still do use C, but that doesn't mean I= have to like or deny the non-free aspects.

So if you want to refrain from using this standard because you feel
it's too expensive for you to purchase, fine.=C2=A0 But please do not confuse the "free" in "free software" with "everyt= hing else should be
available to me without charge too".=C2=A0 Even the FSF charges a fee = for
its software, to fund its activities.

I did not say I wanted to refrain from using the standard because it was ex= pensive. It was your (mis)interpretation. I said a drawback of the standard= is that it is non-free (not mainly in the charge sense).

I am wondering how this thread went into the usual senseless geda flamewar = this fast...

--001a11c3253477994205277a0646--