Re: [media-types] [art] moving forward with

worley@ariadne.com (Dale R. Worley) Mon, 17 October 2016 15:40 UTC

Return-Path: <worley@alum.mit.edu>
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 DB5E21295EA for <media-types@ietfa.amsl.com>; Mon, 17 Oct 2016 08:40:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.235
X-Spam-Level:
X-Spam-Status: No, score=-1.235 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.001, SPF_HELO_PASS=-0.001, SPF_SOFTFAIL=0.665] autolearn=no 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 8hbImg5WXO4M for <media-types@ietfa.amsl.com>; Mon, 17 Oct 2016 08:40:19 -0700 (PDT)
Received: from pechora1.lax.icann.org (pechora1.icann.org [192.0.33.71]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 38F3A1295BF for <media-types@ietf.org>; Mon, 17 Oct 2016 08:40:19 -0700 (PDT)
Received: from resqmta-ch2-03v.sys.comcast.net (resqmta-ch2-03v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:35]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by pechora1.lax.icann.org (Postfix) with ESMTPS id EFB5B1E0184 for <media-types@iana.org>; Mon, 17 Oct 2016 15:40:18 +0000 (UTC)
Received: from resomta-ch2-06v.sys.comcast.net ([69.252.207.102]) by resqmta-ch2-03v.sys.comcast.net with SMTP id wA15b42O38GkCwA18bEvsb; Mon, 17 Oct 2016 15:39:58 +0000
Received: from hobgoblin.ariadne.com ([73.16.37.18]) by resomta-ch2-06v.sys.comcast.net with SMTP id wA16b3quPpzyfwA17bkT5d; Mon, 17 Oct 2016 15:39:58 +0000
Received: from hobgoblin.ariadne.com (hobgoblin.ariadne.com [127.0.0.1]) by hobgoblin.ariadne.com (8.14.7/8.14.7) with ESMTP id u9HFdukp004671; Mon, 17 Oct 2016 11:39:56 -0400
Received: (from worley@localhost) by hobgoblin.ariadne.com (8.14.7/8.14.7/Submit) id u9HFdtJd004668; Mon, 17 Oct 2016 11:39:55 -0400
X-Authentication-Warning: hobgoblin.ariadne.com: worley set sender to worley@alum.mit.edu using -f
From: worley@ariadne.com
To: Erik Wilde <erik.wilde@dret.net>
In-Reply-To: <b4239f95-8f51-a27a-5095-e096bc7d7409@dret.net> (erik.wilde@dret.net)
Sender: worley@ariadne.com
Date: Mon, 17 Oct 2016 11:39:55 -0400
Message-ID: <87eg3fc7ck.fsf@hobgoblin.ariadne.com>
X-CMAE-Envelope: MS4wfN3NGmnhivUrMrO9NWeIrmoeN0Al6IRZMF5Aw/lqwoQO9rivAnGpO4k1ACVX/3eS59wkYG/v1T48bngYuwOovm41eC9mprZHotH6FtSRp3xdMtM7hREV jDDTH0WSxCT2ZzSXtJYSD3m4hfUc0D0KXoKz1OVuJd4hnbsOrQ57y/1JD6oYlbGGsMt26RdaUmPs0g60s+dUn4kFUhFVdX2USm8c/k1xGfjwAXqO7krggTic nhrbncmD3VAlHLvAJ7TiyK0JmSV2z0cyrkEuhj7hh1E=
Archived-At: <https://mailarchive.ietf.org/arch/msg/media-types/cfRoQR6Mgda-vLu6JH8NyVzZ0LQ>
Cc: art@ietf.org, geojson@ietf.org, media-types@iana.org, distobj@acm.org
Subject: Re: [media-types] [art] moving forward with
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, 17 Oct 2016 15:40:20 -0000

>           The syntax and semantics for fragment identifiers for a
>           specific "xxx/yyy+json-seq" SHOULD be processed as follows:
>
>              For cases defined in +json-seq, where the fragment
>              identifier resolves per the +json-seq rules, then process as
>              specified in +json-seq.
>
>              For cases defined in +json-seq, where the fragment
>              identifier does not resolve per the +json-seq rules, then
>              process as specified in "xxx/yyy+json-seq".
>
>              For cases not defined in +json-seq, then process as
>              specified in "xxx/yyy+json-seq".

Everything looks good to me, except that last sentence:  Isn't that a
duplicate of the preceding paragraph?

Dale