From mboxrd@z Thu Jan 1 00:00:00 1970
Return-Path: <gentoo-dev+bounces-65370-garchives=archives.gentoo.org@lists.gentoo.org>
Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80])
by finch.gentoo.org (Postfix) with ESMTP id C150D1391DB
for <garchives@archives.gentoo.org>; Sun, 23 Mar 2014 23:18:40 +0000 (UTC)
Received: from pigeon.gentoo.org (localhost [127.0.0.1])
by pigeon.gentoo.org (Postfix) with SMTP id CF92FE0B79;
Sun, 23 Mar 2014 23:18:34 +0000 (UTC)
Received: from mail-qa0-f51.google.com (mail-qa0-f51.google.com [209.85.216.51])
(using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits))
(No client certificate requested)
by pigeon.gentoo.org (Postfix) with ESMTPS id D507EE086B
for <gentoo-dev@lists.gentoo.org>; Sun, 23 Mar 2014 23:18:33 +0000 (UTC)
Received: by mail-qa0-f51.google.com with SMTP id j7so4586129qaq.24
for <gentoo-dev@lists.gentoo.org>; Sun, 23 Mar 2014 16:18:33 -0700 (PDT)
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=aqLJkX/M/8NeVNxyphzO9Zi3rkmvug76DZsusCGDA9A=;
b=l6JY1VnzBsWmFM2xoyikPYXck+/nVS+SGiZcw+MrvBqPM33m/jniV6RyIvbo2WZ4zJ
0Aw4r0vdeTeorIGW1f450qlOzUKPxriaBss6F4a1mr/BKPril0IkjUXsv/b6/3bxeDjb
gz6tp5Xl29ndoFfuvv30EE40HtiO0J1zQsKyOsbnke1fD4uxouhEA2Aukhyarf3PoqkW
hekXPs8/DZYRAL/W9IEFP37xdEYLpuibSH2v86zSXfXdIS21inw3WmJvU+IDiqlUwyJq
BcUK9Osci3BKme0IIddM2mEjvjjlvqW0VwQSWMH5shfxNro83Z5cNkKpuE1CMMkln9Zw
1Vhw==
Precedence: bulk
List-Post: <mailto:gentoo-dev@lists.gentoo.org>
List-Help: <mailto:gentoo-dev+help@lists.gentoo.org>
List-Unsubscribe: <mailto:gentoo-dev+unsubscribe@lists.gentoo.org>
List-Subscribe: <mailto:gentoo-dev+subscribe@lists.gentoo.org>
List-Id: Gentoo Linux mail <gentoo-dev.gentoo.org>
X-BeenThere: gentoo-dev@lists.gentoo.org
Reply-to: gentoo-dev@lists.gentoo.org
MIME-Version: 1.0
X-Received: by 10.224.50.72 with SMTP id y8mr72682246qaf.36.1395616713064;
Sun, 23 Mar 2014 16:18:33 -0700 (PDT)
Received: by 10.140.104.116 with HTTP; Sun, 23 Mar 2014 16:18:32 -0700 (PDT)
In-Reply-To: <532F6625.4030507@gentoo.org>
References: <CAAr7Pr8Tjc7NDtQrUAQ7RFrT5UVyLyOfGqr0df0LV+-a-SaRtg@mail.gmail.com>
<20140323204428.58216f16@pomiot.lan>
<532F43BF.7070405@gentoo.org>
<20140323220515.22bcced5@pomiot.lan>
<532F54C4.7080205@gentoo.org>
<20140323225106.5e199f7b@pomiot.lan>
<532F6625.4030507@gentoo.org>
Date: Mon, 24 Mar 2014 12:18:32 +1300
Message-ID: <CAATnKFArhUB07aAMY5UpO+6Wr6xZ1DH8yJDG1jDCyDBR=rhrhA@mail.gmail.com>
Subject: Re: [gentoo-dev] RFC GLEP 1005: Package Tags
From: Kent Fredric <kentfredric@gmail.com>
To: gentoo-dev@lists.gentoo.org
Content-Type: multipart/alternative; boundary=047d7bf0e1586cc6e904f54e565b
X-Archives-Salt: e7fd6cf6-f447-4bf5-a7c0-edb84d914d3b
X-Archives-Hash: 51d18918a58ace4d0024f1bc0269955b
--047d7bf0e1586cc6e904f54e565b
Content-Type: text/plain; charset=UTF-8
On 24 March 2014 11:54, Joshua Kinard <kumba@gentoo.org> wrote:
> That said, Is XML that specific that every single atom has to be wrapped by
> an individual tag? A comma-separated list of values in its own XML tag is
> prohibited by the spec? I don't use XML often (if at all), so I am not
> familiar with its intrinsics.
>
By nesting CSV inside XML, you've now got 2 formats to deal with instead of
1.
In pure XML, you can get a properly decoded array of tag elements with a
simple XPath query:
//tag
But with CSV-in-a-tag you have to extract the tag and subsequently parse it.
So you're hand implementing a parser to parse parts of XML that already
convey data without needing to hand-parse.
Which is more effort for everyone who touches the file, not less.
Add to that automated ways to update the tags ( again, having to implement
a custom serialiser in addition to the custom parser ) and its just not
worth the tiny amount of savings.
Because really, if space efficiency was #1 priority, we'd not be using XML
at all, let alone XML with pesky whitespace indentation that consumes
needless bytes. =)
--
Kent
--047d7bf0e1586cc6e904f54e565b
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">=
On 24 March 2014 11:54, Joshua Kinard <span dir=3D"ltr"><<a href=3D"mail=
to:kumba@gentoo.org" target=3D"_blank">kumba@gentoo.org</a>></span> wrot=
e:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-l=
eft:1px #ccc solid;padding-left:1ex">
<div id=3D":3in" class=3D"a3s" style=3D"overflow:hidden">That said, Is XML =
that specific that every single atom has to be wrapped by<br>
an individual tag? =C2=A0A comma-separated list of values in its own XML ta=
g is<br>
prohibited by the spec? =C2=A0I don't use XML often (if at all), so I a=
m not<br>
familiar with its intrinsics.</div></blockquote></div><br><br></div><div cl=
ass=3D"gmail_extra">By nesting CSV inside XML, you've now got 2 formats=
to deal with instead of 1.<br><br></div><div class=3D"gmail_extra">In pure=
XML, you can get a properly decoded array of tag elements with a simple XP=
ath query:<br>
<br></div><div class=3D"gmail_extra">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0 //tag<br><br></div><div class=3D"gmail_extra">But with C=
SV-in-a-tag you have to extract the tag and subsequently parse it.<br><br><=
/div><div class=3D"gmail_extra">So you're hand implementing a parser to=
parse parts of XML that already convey data without needing to hand-parse.=
<br>
<br></div><div class=3D"gmail_extra">Which is more effort for everyone who =
touches the file, not less.<br><br></div><div class=3D"gmail_extra">Add to =
that automated ways to update the tags ( again, having to implement a custo=
m serialiser in addition to the custom parser ) and its just not worth the =
tiny amount of savings.<br>
<br></div><div class=3D"gmail_extra">Because really, if space efficiency wa=
s #1 priority, we'd not be using XML at all, let alone XML with pesky w=
hitespace indentation that consumes needless bytes. =3D)<br><br></div><div =
class=3D"gmail_extra">
-- <br>Kent<br>
</div></div>
--047d7bf0e1586cc6e904f54e565b--