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

Larry Masinter <masinter@adobe.com> Sun, 04 January 2015 01:23 UTC

Return-Path: <masinter@adobe.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 8F4681A1AB3; Sat, 3 Jan 2015 17:23:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 24bOub-qXmgD; Sat, 3 Jan 2015 17:23:45 -0800 (PST)
Received: from na01-bn1-obe.outbound.protection.outlook.com (mail-bn1on0674.outbound.protection.outlook.com [IPv6:2a01:111:f400:fc10::674]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 62A101A1AC9; Sat, 3 Jan 2015 17:23:42 -0800 (PST)
Received: from DM2PR0201MB0960.namprd02.prod.outlook.com (25.160.216.28) by DM2PR0201MB0957.namprd02.prod.outlook.com (25.160.216.25) with Microsoft SMTP Server (TLS) id 15.1.49.12; Sun, 4 Jan 2015 01:23:18 +0000
Received: from DM2PR0201MB0960.namprd02.prod.outlook.com ([25.160.216.28]) by DM2PR0201MB0960.namprd02.prod.outlook.com ([25.160.216.28]) with mapi id 15.01.0049.002; Sun, 4 Jan 2015 01:23:18 +0000
From: Larry Masinter <masinter@adobe.com>
To: Sean Leonard <dev+ietf@seantek.com>, "Murray S. Kucherawy" <superuser@gmail.com>
Thread-Topic: [apps-discuss] [arcmedia] Proposed charter for arcmedia
Thread-Index: AQHQJyeNuL7u9fgufEOJX1POSFIv65yuER+AgAESKiA=
Date: Sun, 4 Jan 2015 01:23:17 +0000
Message-ID: <DM2PR0201MB0960C87FF61C5B46306257DEC35B0@DM2PR0201MB0960.namprd02.prod.outlook.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> <286F8573-CD20-49DD-A361-B2D610D229AB@seantek.com> <CAL0qLwZujCxm1a3C55Tz+d5enS+hotbA=mnAkwHKTtWtH+wXww@mail.gmail.com> <54A7A8F5.1000402@seantek.com>
In-Reply-To: <54A7A8F5.1000402@seantek.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [2601:9:8380:992:6043:96d7:2b0:6ee8]
authentication-results: spf=none (sender IP is ) smtp.mailfrom=masinter@adobe.com;
x-dmarcaction: None
x-microsoft-antispam: BCL:0;PCL:0;RULEID:(3005003);SRVR:DM2PR0201MB0957;
x-forefront-prvs: 0446F0FCE1
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(189002)(479174004)(24454002)(199003)(377454003)(2950100001)(16601075003)(19617315012)(19580395003)(74316001)(106116001)(62966003)(99286002)(92566001)(2900100001)(76176999)(15975445007)(54356999)(33656002)(102836002)(68736005)(107046002)(587094005)(54206007)(20776003)(19580405001)(77156002)(76576001)(106356001)(64706001)(86362001)(105586002)(120916001)(4396001)(99396003)(87936001)(2656002)(50986999)(97736003)(19625215002)(40100003)(101416001)(21056001)(46102003)(16236675004)(19300405004)(54606007)(122556002)(31966008)(3826002); DIR:OUT; SFP:1101; SCL:1; SRVR:DM2PR0201MB0957; H:DM2PR0201MB0960.namprd02.prod.outlook.com; FPR:; SPF:None; MLV:sfv; PTR:InfoNoRecords; MX:1; A:1; LANG:en;
received-spf: None (protection.outlook.com: adobe.com does not designate permitted sender hosts)
Content-Type: multipart/alternative; boundary="_000_DM2PR0201MB0960C87FF61C5B46306257DEC35B0DM2PR0201MB0960_"
MIME-Version: 1.0
X-OriginatorOrg: adobe.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 04 Jan 2015 01:23:17.8097 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: fa7b1b5a-7b34-4387-94ae-d2c178decee1
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM2PR0201MB0957
Archived-At: http://mailarchive.ietf.org/arch/msg/arcmedia/33807yY8vFvnrfsrx7u6c6FmY_M
X-Mailman-Approved-At: Sat, 03 Jan 2015 20:14:27 -0800
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>, 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: Sun, 04 Jan 2015 01:23:48 -0000

I didn’t want to quibble about the verb – “observed” is ambiguous, but so is “considered”. I was hoping not to have to define precisely what coordination is being mandated, but “will be looked at for informational purposes” isn’t strong enough.

If the W3C TAG work were instead in an IETF working group chartered to produce it, would the IETF even charter another group? If so, what coordination would be expected?

The way the IETF commits to do work is by chartering working groups; the way the IETF commits to coordinate is by putting the promise in working group charters (or, in APSAWG the document mini-charter).  I don’t want to wordsmith the charter and have the intent get lost. I want to avoid seeing IETF standardize arcmedia while W3C standardizes an arcmedia format which isn’t compatible. This may be simple or may require active coordination on both sides.

If we agree to the sentiment, we can decide how to say it in the charter.

(bcc public-ietf-w3c re arcmedia working group charter)

Larry
--
http://larry.masinter.net


On 1/2/2015 11:33 PM, Murray S. Kucherawy wrote:
On Fri, Jan 2, 2015 at 2:40 PM, Sean Leonard <dev+ietf@seantek.com<mailto:dev+ietf@seantek.com>> wrote:
> "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)”.

Since the thing being observed is a work-in-progress outside of the IETF, I guessed that wouldn't be taken normatively.

How about "considered"?

"considered" is ok.