Re: XML related issues in metalink, was: Last Call: draft-bryan-metalink (The Metalink Download Description Format) to Proposed Standard
Anthony Bryan <anthonybryan@gmail.com> Sun, 13 December 2009 19:34 UTC
Return-Path: <anthonybryan@gmail.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C6C873A691E for <ietf@core3.amsl.com>; Sun, 13 Dec 2009 11:34:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.203
X-Spam-Level:
X-Spam-Status: No, score=-4.203 tagged_above=-999 required=5 tests=[AWL=-1.604, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6tSR7kht2Dgc for <ietf@core3.amsl.com>; Sun, 13 Dec 2009 11:34:53 -0800 (PST)
Received: from mail-iw0-f195.google.com (mail-iw0-f195.google.com [209.85.223.195]) by core3.amsl.com (Postfix) with ESMTP id 8A0483A6919 for <ietf@ietf.org>; Sun, 13 Dec 2009 11:34:53 -0800 (PST)
Received: by iwn33 with SMTP id 33so1545692iwn.29 for <ietf@ietf.org>; Sun, 13 Dec 2009 11:34:38 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=jp0FCHJvvnPi32dYyoDdlB4sEOMLfIJyaARrCoMDB3s=; b=JG4yYJ7hjPpjC4HiFT7UggbeN9Q30ZtfYy7ggCi2DlzlioiC+s1H80eYnr0L9l+UVb imdvcRH/rIQPMg3DsI309cqATUrnx5Lo8CLy07dhVp2iLPYW/WWrt2DTDKycvfRaizTa viaxBs/C5dpaoqfVnS3G0i13AALuZrUhmORN4=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=MwU7MTl/xFkuiHb/dPd4DT4r0CyPCnJVIpUww1dRc1Xu0l0i+UP4xF/6+HN165CI9v qU8tVbGhDxB0BPxdk+PHbcNJIiZQAIBIiThPSKBzT5zfpyaCfp94UQ7MJjRB3sBQyPD1 Ep1NhnFZ0RYcsTEsdviTMR1tlIk3lgaxXeiIw=
MIME-Version: 1.0
Received: by 10.231.146.2 with SMTP id f2mr1392007ibv.23.1260732878238; Sun, 13 Dec 2009 11:34:38 -0800 (PST)
In-Reply-To: <4B24BD59.30107@gmx.de>
References: <20091211185920.C2E8D3A6999@core3.amsl.com> <4B24BD59.30107@gmx.de>
Date: Sun, 13 Dec 2009 14:34:38 -0500
Message-ID: <bb9e09ee0912131134u286b3ed9p5dc51857dccdd2c4@mail.gmail.com>
Subject: Re: XML related issues in metalink, was: Last Call: draft-bryan-metalink (The Metalink Download Description Format) to Proposed Standard
From: Anthony Bryan <anthonybryan@gmail.com>
To: Julian Reschke <julian.reschke@gmx.de>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Mailman-Approved-At: Mon, 14 Dec 2009 10:23:59 -0800
Cc: Apps Discuss <discuss@apps.ietf.org>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 13 Dec 2009 19:34:54 -0000
On Sun, Dec 13, 2009 at 5:09 AM, Julian Reschke <julian.reschke@gmx.de> wrote: > The IESG wrote: >> >> The IESG has received a request from an individual submitter to consider >> the following document: >> >> - 'The Metalink Download Description Format ' >> <draft-bryan-metalink-24.txt> as a Proposed Standard >> ... > > Hi, > > I did a quick check on a few XML related issues, and found: > > 1) References to W3C specs > > - the references currently use many different formats (for > seriesName/value), it would be great if those were consistent (I recommend > to use the format used for "REC-xml" for compactness) > > - the up-to-date check yielded: > > REC-xml-20060816: [FirstEdition] obsoleted by REC-xml-20081126 > REC-xml-infoset-20040204: [REC] ok > REC-xml-names-20060816: [FirstEdition] obsoleted by REC-xml-names-20091208 > REC-xmlbase-20010627: [FirstEdition] obsoleted by REC-xmlbase-20090128 > REC-xmldsig-core-20080610: [REC] ok > > (where the out-of-date xml-names reference is excused :-). These references have been updated and made more consistent. > 2) RNC > > - was there an automated check that the collected RNC and the fragments are > in sync? For "metalinkFile" I see a difference in ordering which may > indicate that this didn't always happen (the difference appears to be > irrelevant, but who knows...) > > - I found the RNC to miss a few characters (commas, closing braces), which > indicates it may not have been checked recently. I recommend to do that, and > also to validate the examples in the spec against the RNC. Fixed. > 3) XML vs whitespace > > I'm not sure I understand the whitespace treatment. > > One example has: > > <url location="de" priority="1"> > ftp://ftp.example.com/example.ext > </url> > > while the prose says in Section 3: "Note that there MUST NOT be any white > space in a Date construct or in any IRI." > > I personally would prefer that whitespace is NOT ignorable, but in any case > this should be stated somewhere more clearly. Very helpful, your sentence was added: "All leading and trailing whitespace is part of the element content, and MUST be ignored. Consequently, it is disallowed for elements where the defined type does not allow whitespace, such as dates, integers, or IRIs." > (Note I didn't review the spec, I just did a few XML related checks) Thank you, Julian, for these needed checks! Your fresh eyes picked up things unnoticed. "It takes a whole village to raise a spec" :) For those interested, the txt, XML, and html updates in revision 25 are at http://metalinks.svn.sourceforge.net/viewvc/metalinks/internetdraft/ -- (( Anthony Bryan ... Metalink [ http://www.metalinker.org ] )) Easier, More Reliable, Self Healing Downloads
- XML related issues in metalink, was: Last Call: d… Julian Reschke
- Re: XML related issues in metalink, was: Last Cal… Julian Reschke
- RE: XML related issues in metalink, was: Last Cal… Thomson, Martin
- Re: XML related issues in metalink, was: Last Cal… Julian Reschke
- Re: XML related issues in metalink, was: Last Cal… Anthony Bryan
- Re: XML related issues in metalink, was: Last Cal… Anthony Bryan
- RE: XML related issues in metalink, was: Last Cal… Thomson, Martin
- Re: XML related issues in metalink, was: Last Cal… Peter Pöml