[media-types] new draft: "A Media Type Structured Syntax Suffix for JSON Text Sequences"

Erik Wilde <erik.wilde@dret.net> Mon, 19 September 2016 23:33 UTC

Return-Path: <erik.wilde@dret.net>
X-Original-To: media-types@ietfa.amsl.com
Delivered-To: media-types@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BB86B12B043 for <media-types@ietfa.amsl.com>; Mon, 19 Sep 2016 16:33:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.79
X-Spam-Level:
X-Spam-Status: No, score=-1.79 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, SPF_FAIL=0.001, SPF_HELO_PASS=-0.001, T_DKIM_INVALID=0.01] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=neutral reason="invalid (public key: not available)" header.d=dret.net
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 Kp2d_KqK8hDh for <media-types@ietfa.amsl.com>; Mon, 19 Sep 2016 16:33:06 -0700 (PDT)
Received: from pechora5.dc.icann.org (pechora5.icann.org [IPv6:2620:0:2830:201::1:71]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BC26D12B153 for <media-types@ietf.org>; Mon, 19 Sep 2016 16:33:02 -0700 (PDT)
Received: from postoffice.gristmillmedia.com (postoffice.gristmillmedia.com [96.30.18.196]) by pechora5.dc.icann.org (8.13.8/8.13.8) with ESMTP id u8JNWfJu016529 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NO) for <media-types@iana.org>; Mon, 19 Sep 2016 23:33:01 GMT
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=dret.net; s=default; h=Content-Transfer-Encoding:Content-Type:In-Reply-To:MIME-Version :Date:Message-ID:From:Cc:References:To:Subject:Sender:Reply-To:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:List-Id:List-Help:List-Unsubscribe:List-Subscribe: List-Post:List-Owner:List-Archive; bh=vMMEii2FtgAqPlD5Bl84vKbDH4Cu5vSac1ZJisMx66s=; b=ByxEc3ILxOu6wkvY5dhQgebvT0 uP3DIptsBeBVcOEBRhbv3caXoHZwO/nKTm98WURbgMSvfAMWDyeoP959LzvjRFHfuTrI5EskgieVs ZxFqRO8/W2y1aC1ryQZWfulVz8//5YO/TA9Vx0R7vdQJMEOEzzdY0ZklTFrM7iIVdGA0U+QOb7ig/ UWxKmig8Ur0/Il9x+5DrWKgkCX4ek1JxjZU/POB19vm8VT0XQRMu+WpbUMsuhMMgs/+OWvr3qCnXR 51yNukRxuNK9yw630i2SXoIQogYhmdqmY09Eb1XivTjTqy/u3YrKEna0VZQn0PQtaIioF1q4kZiTU nZHuvQBg==;
Received: from cpe-24-211-149-38.nc.res.rr.com ([24.211.149.38]:52991 helo=dretpro.local) by postoffice.gristmillmedia.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.87) (envelope-from <erik.wilde@dret.net>) id 1bm83F-0006N6-39; Mon, 19 Sep 2016 19:32:41 -0400
To: Mark Baker <distobj@acm.org>, media-types@iana.org, art@ietf.org
References: <CAOodmJoxSWEZxwQg6vK650HEy+nBx3iOdVQ+6hbjqaMQd_NBmA@mail.gmail.com> <CALcoZioNMW0SbvnGtm9PtYNPuGdQZ9oTBeBTB8j_+10hkPKf5A@mail.gmail.com> <8CE835AF-B228-4623-BDDE-D4B7DD006A6B@dret.net>
From: Erik Wilde <erik.wilde@dret.net>
Message-ID: <31406b75-16fe-3aed-fa16-ca4ad46f255d@dret.net>
Date: Mon, 19 Sep 2016 19:32:40 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.2.0
MIME-Version: 1.0
In-Reply-To: <8CE835AF-B228-4623-BDDE-D4B7DD006A6B@dret.net>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 7bit
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - postoffice.gristmillmedia.com
X-AntiAbuse: Original Domain - iana.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - dret.net
X-Get-Message-Sender-Via: postoffice.gristmillmedia.com: authenticated_id: birdhouse@dret.net
X-Authenticated-Sender: postoffice.gristmillmedia.com: birdhouse@dret.net
X-Source:
X-Source-Args:
X-Source-Dir:
X-Greylist: IP, sender and recipient auto-whitelisted, not delayed by milter-greylist-4.0 (pechora5.dc.icann.org [192.0.46.71]); Mon, 19 Sep 2016 23:33:02 +0000 (UTC)
Archived-At: <https://mailarchive.ietf.org/arch/msg/media-types/BNMcxA-g6O4wqaCctntyi4q7uik>
Cc: Sean Gillies <sean.gillies@gmail.com>
Subject: [media-types] new draft: "A Media Type Structured Syntax Suffix for JSON Text Sequences"
X-BeenThere: media-types@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "IANA mailing list for reviewing Media Type \(MIME Type, Content Type\) registration requests." <media-types.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/media-types>, <mailto:media-types-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/media-types/>
List-Post: <mailto:media-types@ietf.org>
List-Help: <mailto:media-types-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/media-types>, <mailto:media-types-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 19 Sep 2016 23:33:08 -0000

hello.

On 2016-09-19 11:17, Erik Wilde wrote:
> hello mark
>> On Sep 19, 2016, at 10:46, Mark Baker <distobj@acm.org> wrote:
>> Are you intending to register "+json-seq" as a new suffix? If not,
>> then that name falls afoul of the naming requirements;
> you're of course right, but shouldn't there be a suffix, even if the spec itself didn't define one? should we register the suffix in the geojson seq spec? if not, i'd be willing to whip up a very short draft just registering that suffix. any thoughts about these options?

given that JSON text sequences possibly will become the foundation for 
other media types (this thread was triggered by the discussion of the 
application/geo+json-seq draft), i have created a short draft for 
registering +json-seq as a structured syntax suffix for media types:

https://tools.ietf.org/html/draft-json-seq-suffix

(i just realized that i have used the wrong shortname and will fix this 
asap to say "draft-wilde-json-seq-suffix", but for now please have a 
look at the draft that is linked above.)

i hope there is nothing (too) controversial in there, and have mostly 
looked at RFC 6839 for inspiration, in particular for the issue of how 
to define the fragment identifier semantics.

any feedback is greatly appreciated! cheers,

dret.

-- 
erik wilde | mailto:erik.wilde@dret.net |
            | http://dret.net/netdret    |
            | http://twitter.com/dret    |