X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient: geda-user AT delorie DOT com
Message-ID: <20151224151824.27526.qmail@stuge.se>
Date: Thu, 24 Dec 2015 16:18:23 +0100
From: "Peter Stuge (peter AT stuge DOT se) [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com>
To: geda-user AT delorie DOT com
Subject: Re: [geda-user] A fileformat library
Mail-Followup-To: geda-user AT delorie DOT com
References: <0F6F1D0F-4F07-48EA-90FE-836EAD4E2354 AT noqsi DOT com> <CAM2RGhTficnys3a4xs=UBFvk8aPwpzYWUADFLP_pUQ+R1iKs0g AT mail DOT gmail DOT com> <alpine DOT DEB DOT 2 DOT 00 DOT 1512230552520 DOT 9035 AT igor2priv> <FC796A30-DF21-42E0-89D4-48F3C202BCAE AT noqsi DOT com> <alpine DOT DEB DOT 2 DOT 00 DOT 1512230648180 DOT 9035 AT igor2priv> <A6BF931F-181E-4B69-8B3E-E1BD202DE7C5 AT noqsi DOT com> <20151223194905 DOT 7676 DOT qmail AT stuge DOT se> <0AB5D926-731F-4A49-AA26-D06DAE7C2CB0 AT noqsi DOT com> <201512240626 DOT tBO6QuW0031998 AT envy DOT delorie DOT com> <E9D07EC1-3D8D-4809-9964-2D86074DD461 AT noqsi DOT com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="fBT78PV5vI5fyuAn"
Content-Disposition: inline
In-Reply-To: <E9D07EC1-3D8D-4809-9964-2D86074DD461@noqsi.com>
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


--fBT78PV5vI5fyuAn
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

John Doty wrote:
> Except that the user needs to be comfortable with SQL.

Or anything that can sit on top.


> With our .sch format, users choose whatever language they are
> comfortable with from a long list: AWK, Python, Perl, =E2=80=A6

I'm not at all comfortable with our .sch format. It appears to
create structure using very strange positional-dependent semantics.
Or is that .sym?


> I want to liberate users, not control them.

The argument doesn't hold because users must learn the .sch format
in order to work with it by hand. This remains true for any format.

One important point is that reusing any existing representation makes
it more likely for users to already be familiar with that format or
language, as opposed to the 0 probability for gEDA-proprietary (open)
formats. Structure must still be understood, but that should be more
in the application domain (EE) rather than in the data storage domain.


//Peter

--fBT78PV5vI5fyuAn
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iD8DBQFWfAy/hR3Q0dhIfEgRArMvAKDU5aAwSHn5r3+XEcttGlcynM9NmQCgvHxP
WtdPEC9v+WwIGbWNfmhYWnk=
=17IX
-----END PGP SIGNATURE-----

--fBT78PV5vI5fyuAn--