Re: [dispatch] Dispatching Work on ECMAScript Media Types Updates

Harald Alvestrand <harald@alvestrand.no> Mon, 13 November 2017 00:16 UTC

Return-Path: <harald@alvestrand.no>
X-Original-To: dispatch@ietfa.amsl.com
Delivered-To: dispatch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DEE7A126C26 for <dispatch@ietfa.amsl.com>; Sun, 12 Nov 2017 16:16:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level:
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham autolearn_force=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 pT0yMSnLq7-f for <dispatch@ietfa.amsl.com>; Sun, 12 Nov 2017 16:16:03 -0800 (PST)
Received: from mork.alvestrand.no (mork.alvestrand.no [158.38.152.117]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9E8561201F2 for <dispatch@ietf.org>; Sun, 12 Nov 2017 16:16:02 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mork.alvestrand.no (Postfix) with ESMTP id 0C8AC7C327E for <dispatch@ietf.org>; Mon, 13 Nov 2017 01:16:01 +0100 (CET)
X-Virus-Scanned: Debian amavisd-new at alvestrand.no
Received: from mork.alvestrand.no ([127.0.0.1]) by localhost (mork.alvestrand.no [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JzajBOxcXOdl for <dispatch@ietf.org>; Mon, 13 Nov 2017 01:15:59 +0100 (CET)
Received: from [31.133.156.124] (dhcp-9c7c.meeting.ietf.org [31.133.156.124]) by mork.alvestrand.no (Postfix) with ESMTPSA id 925E67C0CEB for <dispatch@ietf.org>; Mon, 13 Nov 2017 01:15:58 +0100 (CET)
To: dispatch@ietf.org
References: <13d52298-f357-df5e-1bce-6a83894845c5@outer-planes.net> <CABkgnnUG5YDX=iBXSLWxPPQMcGzc+Oza1++x9zpiuoOxbd+zpA@mail.gmail.com> <CANnEKUYYFwMfY4Km1-yGCsO2H1cf=4tkSk_JS63fc0HORNhy5Q@mail.gmail.com>
From: Harald Alvestrand <harald@alvestrand.no>
Message-ID: <7ea5fe01-47f4-773a-7686-f32116ddbafb@alvestrand.no>
Date: Mon, 13 Nov 2017 01:15:55 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0
MIME-Version: 1.0
In-Reply-To: <CANnEKUYYFwMfY4Km1-yGCsO2H1cf=4tkSk_JS63fc0HORNhy5Q@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------5A3DD7D5039080D0F7F11173"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/dispatch/bMDhXTDGau_KkeznoTFsTeyLVaI>
Subject: Re: [dispatch] Dispatching Work on ECMAScript Media Types Updates
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dispatch>, <mailto:dispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dispatch/>
List-Post: <mailto:dispatch@ietf.org>
List-Help: <mailto:dispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Nov 2017 00:16:05 -0000

On 08/17/2017 12:03 PM, Bradley Meck wrote:
> Hiya!
>
> > My initial reaction to this statement was: so why aren't we seeing a
> request for a new media type?
>
> This was discussed in a few different places, ultimately culminating
> in no body wanting to take that route. You can read some info on that
> in the link to the informative TC39
> issue https://github.com/tc39/ecma262/issues/322. It appears you might
> be more interested in the HTML side of things, which would be that a
> new media type would not load with the specification they have already
> started deploying ( there was an issue about this on HTML side
> in https://github.com/whatwg/html/issues/558 ). Some discussion about
> a `mode` parameter instead of media type is in an issue on this
> proposal https://github.com/bmeck/I-D/issues/1#issuecomment-322545837
> . That might be the better route since it will work in web browsers.
>
> > You neglect to mention that uses of the module on the web do not
> depend on additional distinguishing marks because they have the
> type="module" attribute on script tags.
>
> This is out of band information not based upon content. I did not
> think it necessary. Should it be mentioned if it is not based upon
> message content nor information in the media type fields? I think that
> this statement also applies to some tools such as module bundlers as
> well that are using fields in package.json files.

Why isn't a MIME type parameter with the format "type=module" the Right
Answer for the MIME type registration?

>
> > Nit: There Are So Many Proper Nouns In This Document.  Is that really
> necessary?
>
> I think this is in part a stylistic thing of my writing. I tend to
> avoid pronouns and am capitalizing grammar productions in the same
> manner as the ECMAScript specification. We could make stylistic
> changes though!
>
> -Brad
>
> On Thu, Aug 17, 2017 at 12:14 AM, Martin Thomson
> <martin.thomson@gmail.com <mailto:martin.thomson@gmail.com>> wrote:
>
>     Hi Matt,
>
>     First, this seems fine, almost trivial.
>
>     This statement implies a problem of greater scope than what you
>     are solving:
>
>        It is not possible to fully determine if a Source Text of
>     ECMAScript
>        is meant to be parsed in the Module or Script grammar goals based
>        upon content alone.
>
>     My initial reaction to this statement was: so why aren't we seeing a
>     request for a new media type?
>
>     You neglect to mention that uses of the module on the web do not
>     depend on additional distinguishing marks because they have the
>     type="module" attribute on script tags.
>
>     Nit: There Are So Many Proper Nouns In This Document.  Is that
>     really necessary?
>
>     On 17 August 2017 at 14:03, Matthew A. Miller
>     <linuxwolf+ietf@outer-planes.net
>     <mailto:linuxwolf%2Bietf@outer-planes.net>> wrote:
>     > Hello DISPATCH,
>     >
>     > The ECMAScript/JavaScript media types are in need of some updates.
>     > We've started an informational document[1] to address that.  There
>     > hasn't been much mailing list discussion yet, but we are asking now
>     > where to direct the work.
>     >
>     > In consultation with the ART Directors, we ask this document be
>     adopted
>     > by DISPATCH as one of its simple administrative documents.
>     >
>     > The document is <
>     > https://datatracker.ietf.org/doc/draft-bfarias-javascript-mjs
>     <https://datatracker.ietf.org/doc/draft-bfarias-javascript-mjs> >.
>     >
>     > Issues can be filed on the GitHub repository at <
>     > https://github.com/bmeck/I-D/issues
>     <https://github.com/bmeck/I-D/issues> >.
>     >
>     >
>     > Thank you,
>     >
>     > --
>     > - m&m
>     >
>     > Matthew A. Miller
>     >
>     >
>     > _______________________________________________
>     > dispatch mailing list
>     > dispatch@ietf.org <mailto:dispatch@ietf.org>
>     > https://www.ietf.org/mailman/listinfo/dispatch
>     <https://www.ietf.org/mailman/listinfo/dispatch>
>     >
>
>
>
>
> _______________________________________________
> dispatch mailing list
> dispatch@ietf.org
> https://www.ietf.org/mailman/listinfo/dispatch


-- 
Surveillance is pervasive. Go Dark.