IETF Logo Mail Archive

Re: [arcmedia] [apps-discuss] Proposed charter for arcmedia

Sean Leonard <dev+ietf@seantek.com> Fri, 02 January 2015 22:40 UTC

Return-Path: <dev+ietf@seantek.com>
X-Original-To: arcmedia@ietfa.amsl.com
Delivered-To: arcmedia@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 400411A1A27; Fri, 2 Jan 2015 14:40:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.146
X-Spam-Level:
X-Spam-Status: No, score=-0.146 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FRT_ADOBE2=2.455, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GC5HpyqdUrC3; Fri, 2 Jan 2015 14:40:13 -0800 (PST)
Received: from mxout-08.mxes.net (mxout-08.mxes.net [216.86.168.183]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C26421A1A56; Fri, 2 Jan 2015 14:40:13 -0800 (PST)
Received: from smize.la.bg.lan (unknown [74.113.134.154]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id 44149509BC; Fri, 2 Jan 2015 17:40:08 -0500 (EST)
Content-Type: text/plain; charset="windows-1252"
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Sean Leonard <dev+ietf@seantek.com>
In-Reply-To: <DM2PR0201MB09603E51D030435C30B8A069C35D0@DM2PR0201MB0960.namprd02.prod.outlook.com>
Date: Fri, 02 Jan 2015 14:40:08 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <286F8573-CD20-49DD-A361-B2D610D229AB@seantek.com>
References: <CAL0qLwYdnW+o4WUb72VM6yuEP8-jBxQ-KgYQm7KP2Sq9E6dp5g@mail.gmail.com> <CAPRnXtkg5GzLmPOWP=DrV8gTvgV+XDhOi=n3OZ86Yrhw+hOgJA@mail.gmail.com> <CAL0qLwad-UcKECA=m7Zqhw+VZ6wy=bFPVKs_ik+fqjPW7-U7cQ@mail.gmail.com> <54A41D6C.9010501@ninebynine.org> <DM2PR0201MB09606618607D909EA82635E0C35C0@DM2PR0201MB0960.namprd02.prod.outlook.com> <86C96FDF-9A48-43A3-B38A-468F4407AD82@mnot.net> <CAL0qLwbfU7MPFiBngDXjv4WND1d1=Y3H=FJs6AP6EQvsPqYcFA@mail.gmail.com> <CACweHNAvZopEPN5zbwT0fXOVXSNimr0UeKbABOfrsgM4HGjP-Q@mail.gmail.com> <DM2PR0201MB09603E51D030435C30B8A069C35D0@DM2PR0201MB0960.namprd02.prod.outlook.com>
To: Larry Masinter <masinter@adobe.com>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: http://mailarchive.ietf.org/arch/msg/arcmedia/efVndCXasNKGGba1QcweN9D6Zzc
Cc: Matthew Kerwin <matthew@kerwin.net.au>, IETF Apps Discuss <apps-discuss@ietf.org>, "arcmedia@ietf.org" <arcmedia@ietf.org>, Graham Klyne <gk@ninebynine.org>, Mark Nottingham <mnot@mnot.net>, "Murray S. Kucherawy" <superuser@gmail.com>, Public TAG List <www-tag@w3.org>
Subject: Re: [arcmedia] [apps-discuss] Proposed charter for arcmedia
X-BeenThere: arcmedia@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Discussion of creating a new top-level media type, \"archive\", for archive bundles." <arcmedia.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/arcmedia>, <mailto:arcmedia-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/arcmedia/>
List-Post: <mailto:arcmedia@ietf.org>
List-Help: <mailto:arcmedia-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/arcmedia>, <mailto:arcmedia-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Jan 2015 22:40:15 -0000

On Jan 2, 2015, at 10:30 AM, Larry Masinter <masinter@adobe.com> wrote:

> https://github.com/mskucherawy/docs/blob/master/charter-arcmedia
> 
> "The W3C TAG work on packaging and archives, currently in progress, will also be observed.”

“observed” has two definitions: “will be looked at for informational purposes”, and “will be followed (respected = treated as normative)”.

I am okay with the former, but not with the latter. (And since we are talking about the charter, we need to be clear in the language which one we mean.)

As I wrote, the TAG stuff isn’t even a thing in use. ZIP, TAR, RAR, ISO 9660, etc. are in widespread use with long histories of deployment, and are the exemplary use cases.

Sean

v2.23.0 | Report a Bug | By Email