From owner-freebsd-arch@FreeBSD.ORG  Wed Jul 30 04:44:25 2014
Return-Path: <owner-freebsd-arch@FreeBSD.ORG>
Delivered-To: arch@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id E6818F5C
 for <arch@freebsd.org>; Wed, 30 Jul 2014 04:44:24 +0000 (UTC)
Received: from mail-pd0-f182.google.com (mail-pd0-f182.google.com
 [209.85.192.182])
 (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits))
 (Client CN "smtp.gmail.com",
 Issuer "Google Internet Authority G2" (verified OK))
 by mx1.freebsd.org (Postfix) with ESMTPS id B54CA2545
 for <arch@freebsd.org>; Wed, 30 Jul 2014 04:44:24 +0000 (UTC)
Received: by mail-pd0-f182.google.com with SMTP id fp1so781456pdb.41
 for <arch@freebsd.org>; Tue, 29 Jul 2014 21:44:18 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20130820;
 h=x-gm-message-state:mime-version:in-reply-to:references:date
 :message-id:subject:from:to:cc:content-type;
 bh=lFik24OAeNk3PBNZVzSAvxCvH8v13Ju9n6/ZSaOLSWQ=;
 b=Myd1kCyCr3INdG2nm1ePjQPqfdoqPNIRVJXzWudNSo4jZcVELNS9vgEQ6zbzwInDPz
 mqHzknyBV3l6kJSz+TpAVo/hqGa1wErmY+RvgV4H3A9tpAZ/b3F1eFanZBfcXhOZ5e91
 /akWmdlR0RMqTLa79PwamNG0m1gWy2FM61ul4czFcyHrjgUxEGZbtKO3jlC680MfsV+z
 21MUs7foKrUTnuYo4li4G5I2cLTKKScVKeZGJ/vL1r8owFX2t0obQbziP0PPH7tHmcxn
 G+c903n23m+DfnGyVMmH8IhFU3pL9iJYV8YPAytHFBkkhlKyeSkPXPp8Enbodi7yORtM
 iIeA==
X-Gm-Message-State: ALoCoQn5tYcs1J+Y5f5rj7HfzG5ZXWGWA7CetLdA0ZAGG8uAuoThLTz7k7MnG8hnXGMP3mAqt4ns
MIME-Version: 1.0
X-Received: by 10.66.161.194 with SMTP id xu2mr1664158pab.128.1406695458122;
 Tue, 29 Jul 2014 21:44:18 -0700 (PDT)
Received: by 10.70.101.41 with HTTP; Tue, 29 Jul 2014 21:44:17 -0700 (PDT)
Received: by 10.70.101.41 with HTTP; Tue, 29 Jul 2014 21:44:17 -0700 (PDT)
In-Reply-To: <20140730034641.46ABE580A2@chaos.jnpr.net>
References: <20140725044921.9F0D3580A2@chaos.jnpr.net>
 <CAETOPp13H7kyLy-1VJRDOsDbOh8A1MWZDxw1xHUBsxTRtMfc7g@mail.gmail.com>
 <20140728054217.AC1A0580A2@chaos.jnpr.net>
 <20140728055336.GJ50802@ivaldir.etoilebsd.net>
 <CAETOPp3hJB8Gj+PMj3N951krnNqCYiAOY-cPHxMCBy1CQXWJaQ@mail.gmail.com>
 <A1E63A7A-BB38-4CC3-B5EC-B251BE990572@mail.turbofuzz.com>
 <CAETOPp0c1xfMj1vDvQRSoV3ec-LdJmyT9AFH02iziN0yuY1D-A@mail.gmail.com>
 <CAJ-VmomiwUWHWYLdLcQAnp7QBmvQR2wfPoCy=eie-jrvyw0HfA@mail.gmail.com>
 <CAETOPp3zkpp4PY-CeA4Ei=r7_tw1S6rVYiniU+ZxQF3PESVAxA@mail.gmail.com>
 <20140729232338.40AA6580A2@chaos.jnpr.net>
 <CAETOPp1xcNZW1YdgVErZ2ngJM5D3p+L3HJHE2aKOvEvSh6Sh+w@mail.gmail.com>
 <20140730034641.46ABE580A2@chaos.jnpr.net>
Date: Tue, 29 Jul 2014 21:44:17 -0700
Message-ID: <CAETOPp2_dwqeLwYOatS-SrP5FYYYJA+GCK2qUsCVTyX4MJ7Yeg@mail.gmail.com>
Subject: Re: XML Output: libxo - provide single API to output TXT, XML, JSON
 and HTML
From: Jos Backus <jos@catnook.com>
To: "Simon J. Gerraty" <sjg@juniper.net>
Content-Type: text/plain; charset=UTF-8
X-Content-Filtered-By: Mailman/MimeDel 2.1.18
Cc: arch@freebsd.org, Adrian Chadd <adrian@freebsd.org>,
 Jordan Hubbard <jkh@mail.turbofuzz.com>
X-BeenThere: freebsd-arch@freebsd.org
X-Mailman-Version: 2.1.18
Precedence: list
List-Id: Discussion related to FreeBSD architecture <freebsd-arch.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-arch>,
 <mailto:freebsd-arch-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-arch/>
List-Post: <mailto:freebsd-arch@freebsd.org>
List-Help: <mailto:freebsd-arch-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-arch>,
 <mailto:freebsd-arch-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 30 Jul 2014 04:44:25 -0000

On Jul 29, 2014 8:46 PM, "Simon J. Gerraty" <sjg@juniper.net> wrote:
>
>
> On Tue, 29 Jul 2014 16:30:53 -0700, Jos Backus writes:
> >> You certainly cannot wait for all of it to arrive before you start
> >> rendering.
> >
> >Understood. This is why a serialization output format that supports
> >streaming data is useful.
>
> Indeed; XML works fine for that.

Not to beat a dead horse, but so does YAML, and it's more lightweight/less
verbose so I personally find it more elegant. But sure, XML would work as
well.

Jos