Re: use of IRIs in Atom

James M Snell <jasnell@gmail.com> Tue, 31 July 2012 22:16 UTC

Return-Path: <owner-atom-syntax@mail.imc.org>
X-Original-To: ietfarch-atompub-archive@ietfa.amsl.com
Delivered-To: ietfarch-atompub-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D9C2221F886F for <ietfarch-atompub-archive@ietfa.amsl.com>; Tue, 31 Jul 2012 15:16:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.803
X-Spam-Level:
X-Spam-Status: No, score=-5.803 tagged_above=-999 required=5 tests=[AWL=-2.805, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_34=0.6, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GjfYhgW5TvDA for <ietfarch-atompub-archive@ietfa.amsl.com>; Tue, 31 Jul 2012 15:16:52 -0700 (PDT)
Received: from hoffman.proper.com (IPv6.Hoffman.Proper.COM [IPv6:2605:8e00:100:41::81]) by ietfa.amsl.com (Postfix) with ESMTP id 1C9FB21F886B for <atompub-archive@ietf.org>; Tue, 31 Jul 2012 15:16:51 -0700 (PDT)
Received: from hoffman.proper.com (localhost [127.0.0.1]) by hoffman.proper.com (8.14.5/8.14.5) with ESMTP id q6VLKLOr000386 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 31 Jul 2012 14:20:21 -0700 (MST) (envelope-from owner-atom-syntax@mail.imc.org)
Received: (from majordom@localhost) by hoffman.proper.com (8.14.5/8.13.5/Submit) id q6VLKLLa000385; Tue, 31 Jul 2012 14:20:21 -0700 (MST) (envelope-from owner-atom-syntax@mail.imc.org)
X-Authentication-Warning: hoffman.proper.com: majordom set sender to owner-atom-syntax@mail.imc.org using -f
Received: from mail-we0-f171.google.com (mail-we0-f171.google.com [74.125.82.171]) by hoffman.proper.com (8.14.5/8.14.5) with ESMTP id q6VLKJCS000380 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=FAIL) for <atom-syntax@imc.org>; Tue, 31 Jul 2012 14:20:20 -0700 (MST) (envelope-from jasnell@gmail.com)
Received: by weyx43 with SMTP id x43so9146990wey.16 for <atom-syntax@imc.org>; Tue, 31 Jul 2012 15:11:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=hP+A3igy9g6+VvFkRVsGerSHIpmJRx/rGSzeqR3MTuM=; b=dWd9omvX98SPXHMgI+OZZ8ybMCuBL8JYWZyknI6IKt2SnC2W9AI1AJfedwYO7wslM9 zvqeUXK+jQYYCWIL+vBF2WwbsZIYcAuCjT+nAJXLJ2L1ThbSpCYzYBPU3n7xx6GmHqyr Rf3kZZix8H8QJ/+2X3smh7p8b+DrWTldhhJBGT/G6I328EH0QxUL8H/Y/8a7qLi/wvgO qXBabkLbn8p38Napsl1uNngFVllYTfaZvKLlwjQkNJjA50yqAVMFgJvadcWaFNOjBnJd N4GbvRP/00APbeguSxTtbLVXe+fplCKqzs53APQiOhQCVueA4sx0VnESkqJ/d2X0CTO7 k0Tw==
Received: by 10.180.100.131 with SMTP id ey3mr11005794wib.15.1343772690234; Tue, 31 Jul 2012 15:11:30 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.223.171.72 with HTTP; Tue, 31 Jul 2012 15:11:10 -0700 (PDT)
In-Reply-To: <50185435.5020300@stpeter.im>
References: <50185435.5020300@stpeter.im>
From: James M Snell <jasnell@gmail.com>
Date: Tue, 31 Jul 2012 15:11:10 -0700
Message-ID: <CABP7RbfYv0oLJ5KDpVoTVBKz0FHh69Jm365VFts76QZ94fb8mg@mail.gmail.com>
Subject: Re: use of IRIs in Atom
To: Peter Saint-Andre <stpeter@stpeter.im>
Cc: atom-syntax@imc.org, masinter@adobe.com, duerst@it.aoyama.ac.jp, chris@lookout.net
Content-Type: multipart/alternative; boundary="f46d0444ec19dc3de504c6277562"
Sender: owner-atom-syntax@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/atom-syntax/mail-archive/>
List-Unsubscribe: <mailto:atom-syntax-request@imc.org?body=unsubscribe>
List-ID: <atom-syntax.imc.org>

IRIs in Atom are generally used for two purposes:

1. Opaque-identifiers
2. Links

When used as identifiers, the IRIs will typically be validated to generally
conform to Absolute IRI structure requirements but are otherwise treated as
opaque strings. Comparison is performed character-by-character in a
case-sensitive manner without any further processing.

When used as links, the IRIs will typically be handed off to existing HTTP
stacks -- in some cases converted to URIs first. Most Atom stacks that I
have seen do not perform any particular processing of such URLs beyond the
possible IRI2URI conversion. Atom does support the use of relative
references and the establishment of base URLs resolved against either the
HTTP context (e.g. request URI, content-location header, etc) or the
xml:base attribute. Beyond ASCII conversion and relative reference
resolution, however, I would wager that the majority of Atom stacks
typically treat such IRIs as generally opaque and depend on the underlying
HTTP stack to "process" the IRI.

- James

On Tue, Jul 31, 2012 at 2:55 PM, Peter Saint-Andre <stpeter@stpeter.im>wrote:

>
> The IETF's IRI WG is working to update RFC 3987 (Internationalized
> Resource Identifiers). We're doing some informal research to determine
> how IRIs are used in existing protocols [1], and Atom seems like an
> interesting case. In particular with respect to IRI processing, we're
> curious whether Atom implementations (a) strictly follow the rules from
> RFC 3987, (b) use the same processing algorithms as other XML
> applications, or (c) use the same processing algorithms as HTML
> applications. If you have insights into this issue, please do let us know.
>
> Thanks!
>
> Peter
>
> [1] http://lists.w3.org/Archives/Public/public-iri/2012Jul/0060.html
>
>
>