Re: [arcmedia] input on fragment identifiers

Matthew Kerwin <matthew@kerwin.net.au> Thu, 04 June 2015 12:55 UTC

Return-Path: <phluid61@gmail.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 695901B32BB for <arcmedia@ietfa.amsl.com>; Thu, 4 Jun 2015 05:55:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.028
X-Spam-Level:
X-Spam-Status: No, score=-1.028 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, SPF_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 gBEAldyRsYm3 for <arcmedia@ietfa.amsl.com>; Thu, 4 Jun 2015 05:55:09 -0700 (PDT)
Received: from mail-ob0-x230.google.com (mail-ob0-x230.google.com [IPv6:2607:f8b0:4003:c01::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D8D9C1B3276 for <arcmedia@ietf.org>; Thu, 4 Jun 2015 05:55:08 -0700 (PDT)
Received: by obbgp2 with SMTP id gp2so9325682obb.2 for <arcmedia@ietf.org>; Thu, 04 Jun 2015 05:55:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=72wNFKtnnogA1eQhWBIkVLrKeFtbMfayVKU0gHrxBCw=; b=0kERwgUEtusU6sjBE3kI32U72DfYgkycsxAbl6kxCK1b5FpG6B0HZbB//+a20HWjbJ wQpaGS+wMXCPkZTv7SnRABluqNFunpJeyVPOg+iNuJIUzg1HbyxheJpL9cToL34jVP4p aX4Pa4pyh7A72IUATunIjlrHqNF5wShxhOwKX3zgBjuy2Lagctu4pPt6MSL9sysQ5KWz s+NNRy4aBARX+wEZyXiP+0ayaOtP5pcw5gmyUjoSTD6wvxRvUfFYxwPp/iRzhkh3vqc5 19IbhSlkPbkdSBxyT0kcOfQTNvTySlUHnaQf8BTAMl71+ZUhWnxnZUS2Oz5YGRVaPHit xUXw==
MIME-Version: 1.0
X-Received: by 10.202.189.7 with SMTP id n7mr7464740oif.24.1433422508379; Thu, 04 Jun 2015 05:55:08 -0700 (PDT)
Sender: phluid61@gmail.com
Received: by 10.202.226.205 with HTTP; Thu, 4 Jun 2015 05:55:08 -0700 (PDT)
In-Reply-To: <556F8A8C.4070505@gmail.com>
References: <556F8A8C.4070505@gmail.com>
Date: Thu, 4 Jun 2015 22:55:08 +1000
X-Google-Sender-Auth: onDmo0-61AAGg86Suq0LSLvztv0
Message-ID: <CACweHNACWMU7qabi-HxwPfUMHEJiNnBL3pWysjk=d7p6h1DSJw@mail.gmail.com>
From: Matthew Kerwin <matthew@kerwin.net.au>
To: Heather Flanagan <hlflanagan@gmail.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/arcmedia/8XkjqGEi8FbJPXYUnsZ4MLFtY2E>
Cc: arcmedia@ietf.org
Subject: Re: [arcmedia] input on fragment identifiers
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: Thu, 04 Jun 2015 12:55:10 -0000

Hi Heather,

On 04/06/2015, Heather Flanagan <hlflanagan@gmail.com>; wrote:
>
> Hello all,
>
> I was going through the draft and noted the TODO in "7. Fragment
> Identifier Syntax." Not sure if the following discussion regarding
> functional requirements for fragment identifiers and some use cases
> would be useful to help feed this section?
>
> https://www.w3.org/dpub/IG/wiki/Task_Forces/identifiers
>
> - -Heather
>

Thanks for the pointer. I haven't had a chance to do a thorough read
yet, but after a couple of scans it seems to encompass a lot of work
I'm happy to see done. (Not least so we don't have to do it.)

I'm still not sure what approach we'll take here*, but I think
whichever way we go this is a really good head-start.

Cheers


* Personally I'm leaning towards a mention that fragment identifiers
can be used this way, pointers to things like this W3C work, and
leaving it up to (or forcing?) the individual registrations to specify
their own solutions.

-- 
  Matthew Kerwin
  http://matthew.kerwin.net.au/