Re: [APPS-REVIEW] Metalink XML Download Description Format (draft-bryan-metalink-01)

Julian Reschke <julian.reschke@gmx.de> Wed, 03 September 2008 13:29 UTC

Return-Path: <apps-review-bounces@ietf.org>
X-Original-To: apps-review-archive@optimus.ietf.org
Delivered-To: ietfarch-apps-review-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 377753A697A; Wed, 3 Sep 2008 06:29:32 -0700 (PDT)
X-Original-To: apps-review@core3.amsl.com
Delivered-To: apps-review@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 66E323A697A for <apps-review@core3.amsl.com>; Wed, 3 Sep 2008 06:29:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.036
X-Spam-Level:
X-Spam-Status: No, score=-4.036 tagged_above=-999 required=5 tests=[AWL=-1.437, 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 SK6CCzF6rezx for <apps-review@core3.amsl.com>; Wed, 3 Sep 2008 06:29:31 -0700 (PDT)
Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by core3.amsl.com (Postfix) with SMTP id C96693A6403 for <apps-review@ietf.org>; Wed, 3 Sep 2008 06:29:30 -0700 (PDT)
Received: (qmail invoked by alias); 03 Sep 2008 13:22:34 -0000
Received: from mail.greenbytes.de (EHLO [192.168.1.106]) [217.91.35.233] by mail.gmx.net (mp030) with SMTP; 03 Sep 2008 15:22:34 +0200
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX19mbQ9AwcdmJde4COzCi/gnsVO1sxm0vV85YrZbfd rdmzuBNJT+q0Xz
Message-ID: <48BE8F96.2010404@gmx.de>
Date: Wed, 03 Sep 2008 15:22:30 +0200
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.8.0.4) Gecko/20060516 Thunderbird/1.5.0.4 Mnenhy/0.7.4.666
MIME-Version: 1.0
To: Anthony Bryan <anthonybryan@gmail.com>
References: <bb9e09ee0808312244j4fc067c5qe12e4f914d5c8171@mail.gmail.com> <9235.1220345185.781391@peirce.dave.cridland.net> <48BD08D5.1070206@gmx.de> <bb9e09ee0809021641xbe09664tb92cd623f51f6cad@mail.gmail.com> <48BE5645.70302@gmx.de> <bb9e09ee0809030612n7aff945bra3369ca056aadbae@mail.gmail.com>
In-Reply-To: <bb9e09ee0809030612n7aff945bra3369ca056aadbae@mail.gmail.com>
X-Y-GMX-Trusted: 0
X-FuHaFi: 0.62
Cc: general discussion of application-layer protocols <discuss@apps.ietf.org>, xml-dev@lists.xml.org, Applications Review List <apps-review@ietf.org>, ietf-http-wg@w3.org
Subject: Re: [APPS-REVIEW] Metalink XML Download Description Format (draft-bryan-metalink-01)
X-BeenThere: apps-review@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Applications Review List <apps-review.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/apps-review>, <mailto:apps-review-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/apps-review>
List-Post: <mailto:apps-review@ietf.org>
List-Help: <mailto:apps-review-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-review>, <mailto:apps-review-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: apps-review-bounces@ietf.org
Errors-To: apps-review-bounces@ietf.org

Anthony Bryan wrote:
>> So, in general, this would be for IRIs that do not identify a resource to
>> download, but metadata about a resource to download? Strictly speaking,
>> isn't metalink not yet another format for that?
> 
> Yes, it is.
> 
> Do you think about a "metadata" element (a sub-element of
> "resources")with a required "type" attribute of MIME type is
> appropriately generic?

Sounds good.

> This could then be used to describe Metalinks if needed, and other
> types that may come later.

Right.

> I don't think BitTorrent's MIME type is in the is listed in the IANA
> MIME Media Types. Would this be a problem?
> 
>    <?xml version="1.0" encoding="UTF-8"?>
>    <metalink xmlns="http://www.metalinker.org">
>      <files>
>        <file name="example.ext">
>          <resources>
>            <url>ftp://ftp.example.com/example.ext</url>
>            <url>http://example.com/example.ext</url>
>            <metadata
> type="application/x-bittorrent">http://example.com/example.ext.torrent
>            </metadata>
>          </resources>
>        </file>
>      </files>
>    </metalink>

One of these issues that regularly come up :-)

One way out of that would by to "grab" special type names like 
"torrent", and hardwire them. That should be ok as long as they can't 
collide with registered names (thus no "/" allowed).

BR, Julian

_______________________________________________
APPS-REVIEW mailing list
APPS-REVIEW@ietf.org
https://www.ietf.org/mailman/listinfo/apps-review