Re: [arcmedia] input on fragment identifiers

Heather Flanagan <hlflanagan@gmail.com> Thu, 04 June 2015 13:51 UTC

Return-Path: <hlflanagan@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 644D81B337A for <arcmedia@ietfa.amsl.com>; Thu, 4 Jun 2015 06:51:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=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 eCB63Nf14nW3 for <arcmedia@ietfa.amsl.com>; Thu, 4 Jun 2015 06:51:10 -0700 (PDT)
Received: from mail-pa0-x22a.google.com (mail-pa0-x22a.google.com [IPv6:2607:f8b0:400e:c03::22a]) (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 A7D0F1B3496 for <arcmedia@ietf.org>; Thu, 4 Jun 2015 06:40:32 -0700 (PDT)
Received: by padjw17 with SMTP id jw17so29976522pad.2 for <arcmedia@ietf.org>; Thu, 04 Jun 2015 06:40:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=OErir89k4sdoLp3pGuTMc5T+ymSFd6ocE5jOv5skoi8=; b=Y6R9myktRKlujwrlt+1D0VUCIFaR5os0dw0hfglGbrpYHYlgvd8FUR4NvKmIF6CDRT RYHwUF2snzX5UoSgNS7nqibp9Jy5RliVxHbrCuQua19Ho33xGTEjmqMGILS0+Y96heop os2pvUKV46JaIikbPIX+3O3nG/D+v61Nwx5Dlu+et+AmTXSibBALDMTlrZfhrWNkvyea lL7doPgq7FXIRab59cPd2CXd0+fdD2AG+QzLGVYFUTbWx6321IMLrcXtF62igYWK2UWW 4YJGdJYowHegtpeZQGuiKIdv5Kf0wBjnN3KZUSZQME+aEeg3JfFNnQJnovDZvb4el75k M4kQ==
X-Received: by 10.66.250.131 with SMTP id zc3mr57154336pac.136.1433425232182; Thu, 04 Jun 2015 06:40:32 -0700 (PDT)
Received: from Heathers-MacBook-Pro-2.local ([207.118.13.193]) by mx.google.com with ESMTPSA id y16sm3887865pbt.32.2015.06.04.06.40.29 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 04 Jun 2015 06:40:30 -0700 (PDT)
Message-ID: <5570554D.8070205@gmail.com>
Date: Thu, 04 Jun 2015 06:40:29 -0700
From: Heather Flanagan <hlflanagan@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:31.0) Gecko/20100101 Thunderbird/31.7.0
MIME-Version: 1.0
To: Matthew Kerwin <matthew@kerwin.net.au>
References: <556F8A8C.4070505@gmail.com> <CACweHNACWMU7qabi-HxwPfUMHEJiNnBL3pWysjk=d7p6h1DSJw@mail.gmail.com>
In-Reply-To: <CACweHNACWMU7qabi-HxwPfUMHEJiNnBL3pWysjk=d7p6h1DSJw@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/arcmedia/jMDYlryTEHQ-lrii5kmPPIX2-zQ>
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 13:51:16 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On 6/4/15 5:55 AM, Matthew Kerwin wrote:
> 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.
> 

Because the world can't be too easy, the Digital Publishing Interest
Group (source of that page) is coming to the realization that a lot of
what they want is the same as what the W3C's Annotations WG. The
Annotations WG can come up with formal W3C Recommendations where the
DPUB group cannot.

See http://www.w3.org/TR/annotation-model/#fragment-uris

- -Heather
-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2
Comment: GPGTools - http://gpgtools.org

iQEcBAEBCAAGBQJVcFVNAAoJEBTitMubYA+RtHMH/idp80p/kdebdJJj9V9WzVns
Ul9/YGDEXAM92mnymHzulyLqmEOe1KE6RXcXbMGU4RYaP/ciwy4f0ZtVSRuBqlez
7/SXqOYlaaHC5BlZhy3dIh2FTVQnuPTI7XSoL3kmPwLWhalC+95drEQSUPptsmB2
/5HxIH49N1nkgaspVl97/u3GSqajOXLOJN/OUa56RpaEl+dreLOoADr7fi2hv/de
BPzxxW22BMi983v2qiIfgPGsg1WJ5KUZ+8VbYVPAZGvM+QCkpEZ7nEQ3F9V7Ylru
xpTbuW1FC/yJvNj7hwaBVqeUuaUBbtAn2dydYrq4vFKVgp+M+tbyiGtZL8Au12g=
=spDH
-----END PGP SIGNATURE-----