Newsletter

=A0=A0<link rel=3D"icon" hre= f=3D"http://.../image.jpg" type=3D"image/jpeg" />

=A0=A0...

</feed>

The nice= thing about this approach is that it does not actually require any changes= to the spec. The icon and image rel values would be added to the registry = and implementations would need to be modified to look for them as an altern= ative to the icon and logo elements.=A0

Thoughts?

--00163630f28deb708b049282825a-- From owner-atom-syntax@mail.imc.org Wed Oct 13 10:41:51 2010 Return-Path: X-Original-To: ietfarch-atompub-archive@core3.amsl.com Delivered-To: ietfarch-atompub-archive@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E02B23A6A12 for ; Wed, 13 Oct 2010 10:41:51 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.424 X-Spam-Level: X-Spam-Status: No, score=-1.424 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HELO_MISMATCH_COM=0.553] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AlataCX38d-t for ; Wed, 13 Oct 2010 10:41:50 -0700 (PDT) Received: from hoffman.proper.com (Hoffman.Proper.COM [207.182.41.81]) by core3.amsl.com (Postfix) with ESMTP id 751A13A6BAB for ; Wed, 13 Oct 2010 10:41:19 -0700 (PDT) Received: from hoffman.proper.com (localhost [127.0.0.1]) by hoffman.proper.com (8.14.4/8.14.3) with ESMTP id o9DHbaH2014716 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 13 Oct 2010 10:37:36 -0700 (MST) (envelope-from owner-atom-syntax@mail.imc.org) Received: (from majordom@localhost) by hoffman.proper.com (8.14.4/8.13.5/Submit) id o9DHbagG014715; Wed, 13 Oct 2010 10:37:36 -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-yw0-f43.google.com (mail-yw0-f43.google.com [209.85.213.43]) by hoffman.proper.com (8.14.4/8.14.3) with ESMTP id o9DHbYa1014702 for ; Wed, 13 Oct 2010 10:37:36 -0700 (MST) (envelope-from electriceel@gmail.com) Received: by ywa8 with SMTP id 8so2279189ywa.16 for ; Wed, 13 Oct 2010 10:37:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:sender:received :in-reply-to:references:date:x-google-sender-auth:message-id:subject :from:to:content-type; bh=C3akoNLxIcvUEVPNGN0vZF+yLa9hA6pzshCSWG7oaHc=; b=ajsRPa/668A2IVBjQqnYhEBjJXd/SpYe1h5Qd1y838gyzOU1LW8EFqNKHj0w1EZYDv krnlWzuJ3eZxABkbQVp48UMSPCbixXxdu79frJDz6yH/mf5kDdqbzx6LgJLknWqb4VsM cCeFqTStm4GIpBNRg+E0UtE/iipKb/yWtILFA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type; b=VH+Vhw5oYhp49MeyzAvAymYdYw3FdLXSv3U8XJeimN0TvS89dKxA8c6d2R2AwVa+TX aUk+L4wcbuJLl/vxxPXL2Y/3bTo91acku+atbbA51vQerGu5KyH+nIF9AW9t7BJAS3fu ugHTJAyCNB7+aoPYhzucLS11KBHu1sLmMz0iU= MIME-Version: 1.0 Received: by 10.42.180.201 with SMTP id bv9mr95699icb.103.1286991452999; Wed, 13 Oct 2010 10:37:32 -0700 (PDT) Received: by 10.231.206.138 with HTTP; Wed, 13 Oct 2010 10:37:32 -0700 (PDT) In-Reply-To: References: Date: Wed, 13 Oct 2010 12:37:32 -0500 X-Google-Sender-Auth: MzA3lTc3PWJd4wobVhApdbtJ52o Message-ID: Subject: Re: deprecate icon and logo elements? From: Antone Roundy To: atom-syntax@imc.org Content-Type: text/plain; charset=ISO-8859-1 Sender: owner-atom-syntax@mail.imc.org Precedence: bulk List-Archive: List-Unsubscribe: List-ID: I've never been a fan of using for connecting to every sort of external entity, since it makes it impossible to write general purpose handling code (for unknown @rel values) without ending up doing things that degrade the user experience. But that battle has already been lost (when the idea of reserving for links intended for traversal was rejected). The question now is, what benefit do we get in exchange for implementations having to be updated to look for the images in a new location? If there's no concrete benefit, I'd vote for keeping it as it is. It'll be simpler for new implementers if they don't have to discover that something in the spec has been deprecated. And it'll be simpler for everyone if there are fewer ways to do the same thing. Antone From owner-atom-syntax@mail.imc.org Wed Oct 13 10:47:43 2010 Return-Path: X-Original-To: ietfarch-atompub-archive@core3.amsl.com Delivered-To: ietfarch-atompub-archive@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 881AA3A69C6 for ; Wed, 13 Oct 2010 10:47:43 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 1.97 X-Spam-Level: * X-Spam-Status: No, score=1.97 tagged_above=-999 required=5 tests=[AWL=1.305, BAYES_05=-1.11, FM_FORGED_GMAIL=0.622, HELO_MISMATCH_COM=0.553, J_CHICKENPOX_44=0.6] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8MyjKa9-cRgT for ; Wed, 13 Oct 2010 10:47:42 -0700 (PDT) Received: from hoffman.proper.com (Hoffman.Proper.COM [207.182.41.81]) by core3.amsl.com (Postfix) with ESMTP id B54813A69F5 for ; Wed, 13 Oct 2010 10:47:42 -0700 (PDT) Received: from hoffman.proper.com (localhost [127.0.0.1]) by hoffman.proper.com (8.14.4/8.14.3) with ESMTP id o9DHYQ1w014569 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 13 Oct 2010 10:34:26 -0700 (MST) (envelope-from owner-atom-syntax@mail.imc.org) Received: (from majordom@localhost) by hoffman.proper.com (8.14.4/8.13.5/Submit) id o9DHYQCD014568; Wed, 13 Oct 2010 10:34:26 -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-wy0-f171.google.com (mail-wy0-f171.google.com [74.125.82.171]) by hoffman.proper.com (8.14.4/8.14.3) with ESMTP id o9DHYPmo014560 for ; Wed, 13 Oct 2010 10:34:25 -0700 (MST) (envelope-from pjkeane@gmail.com) Received: by wyb36 with SMTP id 36so2921wyb.16 for ; Wed, 13 Oct 2010 10:34:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:sender:received :in-reply-to:references:date:x-google-sender-auth:message-id:subject :from:to:cc:content-type:content-transfer-encoding; bh=m8ha46swgWybaR1e3t+UN5dKKg/gvG+j9iPt+HQ8/GU=; b=h6rKi/HEhgY31WPN6CwItq9JVv8bgfCaGqtfUfYJenztAT1GlS0JpSPHvbZpEkJEEG 7jE8ddA9iEGWH8dtN3s05tdSJIesY2UTuJpOhMJtCu3gQdUM+YbrlQDLpPMg5Bjrr/Tc Sy2e7f9ndUD6JOfRtbTweI+60ywBtMcRf1LKk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; b=ffunS058/F9IR8fZaN890+6roBs+t2AcCyG7WPVFP+W9kMZYt2m/UfAt93rT9vwnqr ry4EleHncH3ePNuGgmIVkT9o5pWXN0kWO0+0Diy0ezNIV1csQHlmc9ELc+n6clz3X+Uj YOdgKsG2C9M6z5SgXSYhLtWElSi5OqaIY0veA= MIME-Version: 1.0 Received: by 10.227.58.82 with SMTP id f18mr5852277wbh.12.1286991263969; Wed, 13 Oct 2010 10:34:23 -0700 (PDT) Received: by 10.227.141.142 with HTTP; Wed, 13 Oct 2010 10:34:23 -0700 (PDT) In-Reply-To: References: Date: Wed, 13 Oct 2010 12:34:23 -0500 X-Google-Sender-Auth: kdiQ8BvWN9Ez_osXMNhPfent-50 Message-ID: Subject: Re: deprecate icon and logo elements? From: Peter Keane To: James Snell Cc: Atom-Syntax Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hoffman.proper.com id o9DHYQmo014564 Sender: owner-atom-syntax@mail.imc.org Precedence: bulk List-Archive: List-Unsubscribe: List-ID: +1 --peter On Wed, Oct 13, 2010 at 11:59 AM, James Snell wrote: > Ok, this is something that has bugged me for quite a white... the atom:icon > and atom:logo elements are terribly underspecified as just a simple IRI. > Those these really should be link objects. What I'd like to propose is a > deprecation of those elements in favor of and > . The icon and image rel attributes would be > added to the registry of link relations... > So instead of.. > > Â Â http://.../image.jpg > Â Â ... > > It would be... > > Â Â > Â Â ... > > The nice thing about this approach is that it does not actually require any > changes to the spec. The icon and image rel values would be added to the > registry and implementations would need to be modified to look for them as > an alternative to the icon and logo elements. > Thoughts? From owner-atom-syntax@mail.imc.org Wed Oct 13 11:02:16 2010 Return-Path: X-Original-To: ietfarch-atompub-archive@core3.amsl.com Delivered-To: ietfarch-atompub-archive@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 17DFC3A6AC2 for ; Wed, 13 Oct 2010 11:02:16 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 0.999 X-Spam-Level: X-Spam-Status: No, score=0.999 tagged_above=-999 required=5 tests=[AWL=0.955, BAYES_05=-1.11, HELO_MISMATCH_COM=0.553, HTML_MESSAGE=0.001, J_CHICKENPOX_44=0.6] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id q1GN2iH8aaNu for ; Wed, 13 Oct 2010 11:02:15 -0700 (PDT) Received: from hoffman.proper.com (Hoffman.Proper.COM [207.182.41.81]) by core3.amsl.com (Postfix) with ESMTP id 2586D3A69F5 for ; Wed, 13 Oct 2010 11:02:15 -0700 (PDT) Received: from hoffman.proper.com (localhost [127.0.0.1]) by hoffman.proper.com (8.14.4/8.14.3) with ESMTP id o9DHihku015032 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 13 Oct 2010 10:44:43 -0700 (MST) (envelope-from owner-atom-syntax@mail.imc.org) Received: (from majordom@localhost) by hoffman.proper.com (8.14.4/8.13.5/Submit) id o9DHihHY015031; Wed, 13 Oct 2010 10:44:43 -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-qy0-f178.google.com (mail-qy0-f178.google.com [209.85.216.178]) by hoffman.proper.com (8.14.4/8.14.3) with ESMTP id o9DHig9R015025 for ; Wed, 13 Oct 2010 10:44:42 -0700 (MST) (envelope-from jasnell@gmail.com) Received: by qyk35 with SMTP id 35so1175734qyk.16 for ; Wed, 13 Oct 2010 10:44:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=o5lKPBuvGZMkIUUTRA0cxnaAdt1oV6AXyj58eWvN8DE=; b=mvBs4jMmptxX0bkB0JQ9CSeyGmPVTinYf8PxDJJzCXEv3Ba4bAMyJNkajqS7xSdajM 0jW91UDpHXsE5M+YsMVzfnKXCu7fWw8i6O2sBIdO5MjF6eJHDsBAEJhFSxoNd+IWH/+T L70Atbs7kEoDUKYYDGpEg4MEl8qPzjJb0c7NQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=ePYwPWz1XaDbtEBfpdQ2JV6Fsh9Q6Ml2AlEui2i9WM8geuQ2pMvs8/VGgWCrU6HO2X l0czPo8gOffHbe/V4LMwaPvec76/ohCpeZyOk18bt5JXzb8hMdQw0pkJxjl75xrY3bEc ikhiZBUpnsEjMxAxPNwjN/K6dZk5GzqgDZLE0= MIME-Version: 1.0 Received: by 10.224.184.3 with SMTP id ci3mr7309264qab.312.1286991881837; Wed, 13 Oct 2010 10:44:41 -0700 (PDT) Received: by 10.229.114.194 with HTTP; Wed, 13 Oct 2010 10:44:41 -0700 (PDT) In-Reply-To: References:

Date: Wed, 13 Oct 2010 10:44:41 -0700 Message-ID: Subject: Re: deprecate icon and logo elements? From: James Snell To: Antone Roundy Cc: atom-syntax@imc.org Content-Type: multipart/alternative; boundary=20cf302d4d5ef21eb804928325e8 Sender: owner-atom-syntax@mail.imc.org Precedence: bulk List-Archive: List-Unsubscribe: List-ID: --20cf302d4d5ef21eb804928325e8 Content-Type: text/plain; charset=ISO-8859-1 Concrete benefits include being able to specify the media type of the linked resource, as well as take advantage of other extensions such as the Atom Link Extensions I've proposed, and Google's convention of using child elements within atom:link to provide additional metadata such as multiple alternative representations of an image (e.g. thumbnails, etc). At the very least, we should be able to specify the media type of the linked image. On Wed, Oct 13, 2010 at 10:37 AM, Antone Roundy wrote: > > I've never been a fan of using for connecting to every sort of > external entity, since it makes it impossible to write general purpose > handling code (for unknown @rel values) without ending up doing > things that degrade the user experience. But that battle has already > been lost (when the idea of reserving for links intended for > traversal was rejected). > > The question now is, what benefit do we get in exchange for > implementations having to be updated to look for the images in a new > location? If there's no concrete benefit, I'd vote for keeping it as > it is. It'll be simpler for new implementers if they don't have to > discover that something in the spec has been deprecated. And it'll be > simpler for everyone if there are fewer ways to do the same thing. > > Antone > > --20cf302d4d5ef21eb804928325e8 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Concrete benefits include being able to specify the= media type of the linked resource, as well as take advantage of other exte= nsions such as the Atom Link Extensions I've proposed, and Google's= convention of using child elements within atom:link to provide additional = metadata such as multiple alternative representations of an image (e.g. thu= mbnails, etc). At the very least, we should be able to specify the media ty= pe of the linked image.

On Wed, Oct 13, 2010 at 10:37 AM, Antone Rou= ndy <antone@g= eckotribe.com> wrote:

I've never been a fan of using <link> for connecting to every sor= t of
external entity, since it makes it impossible to write general purpose
<link> handling code (for unknown @rel values) without ending up doin= g
things that degrade the user experience. But that battle has already
been lost (when the idea of reserving <link> for links intended for traversal was rejected).

The question now is, what benefit do we get in exchange for
implementations having to be updated to look for the images in a new
location? =A0If there's no concrete benefit, I'd vote for keeping i= t as
it is. =A0It'll be simpler for new implementers if they don't have = to
discover that something in the spec has been deprecated. And it'll be simpler for everyone if there are fewer ways to do the same thing.

Antone

--20cf302d4d5ef21eb804928325e8-- From owner-atom-syntax@mail.imc.org Wed Oct 13 11:03:30 2010 Return-Path: X-Original-To: ietfarch-atompub-archive@core3.amsl.com Delivered-To: ietfarch-atompub-archive@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2F20F3A6A2D for ; Wed, 13 Oct 2010 11:03:30 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.266 X-Spam-Level: X-Spam-Status: No, score=-0.266 tagged_above=-999 required=5 tests=[AWL=0.557, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HELO_MISMATCH_COM=0.553, HTML_MESSAGE=0.001, J_CHICKENPOX_44=0.6] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id k4wjl4wZhiZt for ; Wed, 13 Oct 2010 11:03:29 -0700 (PDT) Received: from hoffman.proper.com (Hoffman.Proper.COM [207.182.41.81]) by core3.amsl.com (Postfix) with ESMTP id 587433A69F5 for ; Wed, 13 Oct 2010 11:03:29 -0700 (PDT) Received: from hoffman.proper.com (localhost [127.0.0.1]) by hoffman.proper.com (8.14.4/8.14.3) with ESMTP id o9DHpX15015443 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 13 Oct 2010 10:51:33 -0700 (MST) (envelope-from owner-atom-syntax@mail.imc.org) Received: (from majordom@localhost) by hoffman.proper.com (8.14.4/8.13.5/Submit) id o9DHpXRA015442; Wed, 13 Oct 2010 10:51:33 -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-bw0-f43.google.com (mail-bw0-f43.google.com [209.85.214.43]) by hoffman.proper.com (8.14.4/8.14.3) with ESMTP id o9DHpWkf015436 for ; Wed, 13 Oct 2010 10:51:32 -0700 (MST) (envelope-from bobwyman@gmail.com) Received: by bwz20 with SMTP id 20so1147193bwz.16 for ; Wed, 13 Oct 2010 10:51:30 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:sender:received :in-reply-to:references:date:x-google-sender-auth:message-id:subject :from:to:cc:content-type; bh=KRimzJsGK+UiRPfkeWBLMrq6VW6apUchtfwiB2ohowU=; b=BgOKmjGmbe7+afByEyTE70KAG2X1Wpard9FdOKqiArsxaqt1wCfdQXLyK6PhNedWUH XLWvo7Q+77A32wSiqgp7VYhpSpKEkOiOT1hZ+kPAOehD9fs3Oh003asnZpnObS806c/A Z6IfQtuAaCrLBwiH8SZXasjO4LAMx8Tgw/7aQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; b=SL7gZ34f3yPRJb45IyzStLy9gxJT6afG2/HlSpCtV2fOSalKIks/qj2cQhPN5L1th9 dXD+YitvAkC6/vQrnWxtjV+9ToRuGLumNUHKEqMFKz5gOUUrXz2Hx2INNXueMvrY4p5Z ihFSfPctQ9UvcEjQJFM53T1/3j9Q3mvvRvxNo= MIME-Version: 1.0 Received: by 10.204.133.129 with SMTP id f1mr8074162bkt.91.1286992290867; Wed, 13 Oct 2010 10:51:30 -0700 (PDT) Received: by 10.204.112.67 with HTTP; Wed, 13 Oct 2010 10:51:30 -0700 (PDT) In-Reply-To: References: Date: Wed, 13 Oct 2010 13:51:30 -0400 X-Google-Sender-Auth: sDAzHMWmKyDiRp8rEhKC0e5Yxvw Message-ID: Subject: Re: deprecate icon and logo elements? From: Bob Wyman To: James Snell Cc: Atom-Syntax Content-Type: multipart/alternative; boundary=0015174791385368600492833efa Sender: owner-atom-syntax@mail.imc.org Precedence: bulk List-Archive: List-Unsubscribe: List-ID: --0015174791385368600492833efa Content-Type: text/plain; charset=ISO-8859-1 +1 Things which are simply links should be encoded as links... It is frequently seductive to provide special syntax to handle common or well-known cases, but the end result is often just an unnecessary increase in complexity. It is best to consistently encode all objects of the same general type and reserve special cases for the truly special cases. bob wyman On Wed, Oct 13, 2010 at 12:59 PM, James Snell wrote: > Ok, this is something that has bugged me for quite a white... the atom:icon > and atom:logo elements are terribly underspecified as just a simple IRI. > Those these really should be link objects. What I'd like to propose is a > deprecation of those elements in favor of and > . The icon and image rel attributes would be > added to the registry of link relations... > > So instead of.. > > > http://.../image.jpg > ... > > > It would be... > > > > ... > > > The nice thing about this approach is that it does not actually require any > changes to the spec. The icon and image rel values would be added to the > registry and implementations would need to be modified to look for them as > an alternative to the icon and logo elements. > > Thoughts? > --0015174791385368600492833efa Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable

Things which are simply links should be encoded= as links... It is frequently seductive to provide special syntax to handle= common or well-known cases, but the end result is often just an=A0unnecess= ary=A0increase in complexity. It is best to consistently encode all objects= of the same general type and reserve special cases for the truly special c= ases.=A0

bob wyman

On Wed, Oct 13, = 2010 at 12:59 PM, James Snell <jasnell@gmail.com> wrote:

Ok, this is something that has bugged me for quite a white... the atom:icon= and atom:logo elements are terribly underspecified as just a simple IRI. T= hose these really should be link objects. What I'd like to propose is a= deprecation of those elements in favor of <link rel=3D"icon" = href=3D"..." /> and <link rel=3D"image" href=3D&q= uot;..." />. The icon and image rel attributes would be added to th= e registry of link relations...

So instead of..

<feed>
<= div>=A0=A0<icon>http://.../image.jpg</icon>

=A0=A0...=

</feed>

It would be...

<feed>

=A0=A0<link rel=3D"icon" hre= f=3D"http://.../image.jpg" type=3D"image/jpeg" />

=A0=A0...

</feed>

Thoughts?

--0015174791385368600492833efa-- From owner-atom-syntax@mail.imc.org Wed Oct 13 17:09:21 2010 Return-Path: X-Original-To: ietfarch-atompub-archive@core3.amsl.com Delivered-To: ietfarch-atompub-archive@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5F2853A6A40 for ; Wed, 13 Oct 2010 17:09:21 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.865 X-Spam-Level: X-Spam-Status: No, score=-1.865 tagged_above=-999 required=5 tests=[AWL=-3.642, BAYES_50=0.001, FM_FORGED_GMAIL=0.622, HELO_MISMATCH_COM=0.553, HTML_MESSAGE=0.001, J_CHICKENPOX_44=0.6] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6777dA1JgZy1 for ; Wed, 13 Oct 2010 17:09:15 -0700 (PDT) Received: from hoffman.proper.com (Hoffman.Proper.COM [207.182.41.81]) by core3.amsl.com (Postfix) with ESMTP id 5D5A33A6A6F for ; Wed, 13 Oct 2010 17:09:15 -0700 (PDT) Received: from hoffman.proper.com (localhost [127.0.0.1]) by hoffman.proper.com (8.14.4/8.14.3) with ESMTP id o9E03OIZ031074 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 13 Oct 2010 17:03:24 -0700 (MST) (envelope-from owner-atom-syntax@mail.imc.org) Received: (from majordom@localhost) by hoffman.proper.com (8.14.4/8.13.5/Submit) id o9E03O6X031073; Wed, 13 Oct 2010 17:03:24 -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 eu1sys200aog111.obsmtp.com (eu1sys200aog111.obsmtp.com [207.126.144.131]) by hoffman.proper.com (8.14.4/8.14.3) with SMTP id o9E03LxS031068 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Wed, 13 Oct 2010 17:03:23 -0700 (MST) (envelope-from samj@samj.net) Received: from source ([209.85.160.182]) by eu1sys200aob111.postini.com ([207.126.147.11]) with SMTP ID DSNKTLZIyPFnWzGC3rqeS8tIM+f9YWxprMuz@postini.com; Thu, 14 Oct 2010 00:03:23 UTC Received: by gyf3 with SMTP id 3so2643931gyf.41 for ; Wed, 13 Oct 2010 17:03:20 -0700 (PDT) MIME-Version: 1.0 Received: by 10.100.10.15 with SMTP id 15mr4918340anj.9.1287014599831; Wed, 13 Oct 2010 17:03:19 -0700 (PDT) Received: by 10.100.128.19 with HTTP; Wed, 13 Oct 2010 17:03:19 -0700 (PDT) In-Reply-To: References: Date: Wed, 13 Oct 2010 20:03:19 -0400 Message-ID: Subject: Re: deprecate icon and logo elements? From: Sam Johnston To: James Snell Cc: Atom-Syntax Content-Type: multipart/alternative; boundary=0016e64652fa0b32d004928870ce Sender: owner-atom-syntax@mail.imc.org Precedence: bulk List-Archive: List-Unsubscribe: List-ID: --0016e64652fa0b32d004928870ce Content-Type: text/plain; charset=ISO-8859-1 +1 Simple >> Complex. On Wed, Oct 13, 2010 at 12:59 PM, James Snell wrote: > Ok, this is something that has bugged me for quite a white... the atom:icon > and atom:logo elements are terribly underspecified as just a simple IRI. > Those these really should be link objects. What I'd like to propose is a > deprecation of those elements in favor of and > . The icon and image rel attributes would be > added to the registry of link relations... > > So instead of.. > > > http://.../image.jpg > ... > > > It would be... > > > > ... > > > The nice thing about this approach is that it does not actually require any > changes to the spec. The icon and image rel values would be added to the > registry and implementations would need to be modified to look for them as > an alternative to the icon and logo elements. > > Thoughts? > --0016e64652fa0b32d004928870ce Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable +1

Simple >> Complex.

On Wed, Oct 13, 2010 at 12:59 PM, James Snell <<= a href=3D"mailto:jasnell@gmail.com">jasnell@gmail.com> wrote:=

Ok, this is something that has bugged me fo= r quite a white... the atom:icon and atom:logo elements are terribly unders= pecified as just a simple IRI. Those these really should be link objects. W= hat I'd like to propose is a deprecation of those elements in favor of = <link rel=3D"icon" href=3D"..." /> and <link r= el=3D"image" href=3D"..." />. The icon and image rel= attributes would be added to the registry of link relations...

So instead of..

<feed>
<= div>=A0=A0<icon>http://.../image.jpg</icon>

=A0=A0...=

</feed>

It would be...

<feed>

=A0=A0<link rel=3D"icon" hre= f=3D"http://.../image.jpg" type=3D"image/jpeg" />

=A0=A0...

</feed>

Thoughts?

--0016e64652fa0b32d004928870ce-- From owner-atom-syntax@mail.imc.org Thu Oct 14 02:24:19 2010 Return-Path: X-Original-To: ietfarch-atompub-archive@core3.amsl.com Delivered-To: ietfarch-atompub-archive@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 139F03A6965 for ; Thu, 14 Oct 2010 02:24:19 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 1.59 X-Spam-Level: * X-Spam-Status: No, score=1.59 tagged_above=-999 required=5 tests=[BAYES_40=-0.185, FM_FORGED_GMAIL=0.622, HELO_MISMATCH_COM=0.553, J_CHICKENPOX_44=0.6] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ox5kg2K1c7Io for ; Thu, 14 Oct 2010 02:24:18 -0700 (PDT) Received: from hoffman.proper.com (Hoffman.Proper.COM [207.182.41.81]) by core3.amsl.com (Postfix) with ESMTP id 438013A6AF4 for ; Thu, 14 Oct 2010 02:24:18 -0700 (PDT) Received: from hoffman.proper.com (localhost [127.0.0.1]) by hoffman.proper.com (8.14.4/8.14.3) with ESMTP id o9E9Ie31053581 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 14 Oct 2010 02:18:40 -0700 (MST) (envelope-from owner-atom-syntax@mail.imc.org) Received: (from majordom@localhost) by hoffman.proper.com (8.14.4/8.13.5/Submit) id o9E9IeV2053580; Thu, 14 Oct 2010 02:18:40 -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 nxauth1.nexgenta.com (nxauth1.nexgenta.com [93.89.80.170]) by hoffman.proper.com (8.14.4/8.14.3) with ESMTP id o9E9IdO5053574 for ; Thu, 14 Oct 2010 02:18:40 -0700 (MST) (envelope-from mo@nevali.net) Received: from mail-qw0-f43.google.com (mail-qw0-f43.google.com [209.85.216.43]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by nxauth1.nexgenta.com (Postfix) with ESMTP id 027D21AB6C for ; Thu, 14 Oct 2010 09:18:37 +0000 (UTC) Received: by qwh6 with SMTP id 6so969726qwh.16 for ; Thu, 14 Oct 2010 02:18:36 -0700 (PDT) MIME-Version: 1.0 Received: by 10.224.20.70 with SMTP id e6mr3100040qab.284.1287047916835; Thu, 14 Oct 2010 02:18:36 -0700 (PDT) Received: by 10.229.224.142 with HTTP; Thu, 14 Oct 2010 02:18:36 -0700 (PDT) In-Reply-To: References: Date: Thu, 14 Oct 2010 10:18:36 +0100 Message-ID: Subject: Re: deprecate icon and logo elements? From: Mo McRoberts To: James Snell Cc: Atom-Syntax Content-Type: text/plain; charset=UTF-8 Sender: owner-atom-syntax@mail.imc.org Precedence: bulk List-Archive: List-Unsubscribe: List-ID: On Wed, Oct 13, 2010 at 17:59, James Snell wrote: > Ok, this is something that has bugged me for quite a white... the atom:icon > and atom:logo elements are terribly underspecified as just a simple IRI. > Those these really should be link objects. What I'd like to propose is a > deprecation of those elements in favor of and > . The icon and image rel attributes would be > added to the registry of link relations... A great big +1 from me. From owner-atom-syntax@mail.imc.org Fri Oct 15 09:18:14 2010 Return-Path: X-Original-To: ietfarch-atompub-archive@core3.amsl.com Delivered-To: ietfarch-atompub-archive@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 817EB3A6A53 for ; Fri, 15 Oct 2010 09:18:14 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 1.177 X-Spam-Level: * X-Spam-Status: No, score=1.177 tagged_above=-999 required=5 tests=[BAYES_50=0.001, FM_FORGED_GMAIL=0.622, HELO_MISMATCH_COM=0.553, HTML_MESSAGE=0.001] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id u8UB2tgLll0O for ; Fri, 15 Oct 2010 09:18:11 -0700 (PDT) Received: from hoffman.proper.com (Hoffman.Proper.COM [207.182.41.81]) by core3.amsl.com (Postfix) with ESMTP id 4B45B3A6959 for ; Fri, 15 Oct 2010 09:18:11 -0700 (PDT) Received: from hoffman.proper.com (localhost [127.0.0.1]) by hoffman.proper.com (8.14.4/8.14.3) with ESMTP id o9FGD43h046442 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 15 Oct 2010 09:13:04 -0700 (MST) (envelope-from owner-atom-syntax@mail.imc.org) Received: (from majordom@localhost) by hoffman.proper.com (8.14.4/8.13.5/Submit) id o9FGD4SE046441; Fri, 15 Oct 2010 09:13:04 -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-yw0-f43.google.com (mail-yw0-f43.google.com [209.85.213.43]) by hoffman.proper.com (8.14.4/8.14.3) with ESMTP id o9FGD3ZI046434 for ; Fri, 15 Oct 2010 09:13:03 -0700 (MST) (envelope-from hadrien.gardeur@feedbooks.com) Received: by ywc21 with SMTP id 21so536195ywc.16 for ; Fri, 15 Oct 2010 09:13:02 -0700 (PDT) Received: by 10.151.2.24 with SMTP id e24mr1896252ybi.302.1287159182413; Fri, 15 Oct 2010 09:13:02 -0700 (PDT) MIME-Version: 1.0 Received: by 10.151.39.19 with HTTP; Fri, 15 Oct 2010 09:12:41 -0700 (PDT) In-Reply-To: References:

From: Hadrien Gardeur Date: Fri, 15 Oct 2010 18:12:41 +0200 Message-ID: Subject: Re: deprecate icon and logo elements? To: Mo McRoberts Cc: James Snell , Atom-Syntax Content-Type: multipart/alternative; boundary=000e0cd6c810d64e930492aa1924 Sender: owner-atom-syntax@mail.imc.org Precedence: bulk List-Archive: List-Unsubscribe: List-ID: --000e0cd6c810d64e930492aa1924 Content-Type: text/plain; charset=UTF-8 +1 from me too and rel="icon" is already widely used in HTML --000e0cd6c810d64e930492aa1924 Content-Type: text/html; charset=UTF-8 +1 from me too and rel="icon" is already widely used in HTML --000e0cd6c810d64e930492aa1924-- From owner-atom-syntax@mail.imc.org Fri Oct 15 14:07:07 2010 Return-Path: X-Original-To: ietfarch-atompub-archive@core3.amsl.com Delivered-To: ietfarch-atompub-archive@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id F0A3A3A6D17 for ; Fri, 15 Oct 2010 14:07:06 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 0.645 X-Spam-Level: X-Spam-Status: No, score=0.645 tagged_above=-999 required=5 tests=[AWL=0.831, BAYES_20=-0.74, HELO_MISMATCH_COM=0.553, HTML_MESSAGE=0.001] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 514OY4gu02fz for ; Fri, 15 Oct 2010 14:07:06 -0700 (PDT) Received: from hoffman.proper.com (Hoffman.Proper.COM [207.182.41.81]) by core3.amsl.com (Postfix) with ESMTP id EECB03A6BCC for ; Fri, 15 Oct 2010 14:07:05 -0700 (PDT) Received: from hoffman.proper.com (localhost [127.0.0.1]) by hoffman.proper.com (8.14.4/8.14.3) with ESMTP id o9FL30Yn062971 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 15 Oct 2010 14:03:00 -0700 (MST) (envelope-from owner-atom-syntax@mail.imc.org) Received: (from majordom@localhost) by hoffman.proper.com (8.14.4/8.13.5/Submit) id o9FL30bJ062970; Fri, 15 Oct 2010 14:03:00 -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-qy0-f178.google.com (mail-qy0-f178.google.com [209.85.216.178]) by hoffman.proper.com (8.14.4/8.14.3) with ESMTP id o9FL2x9R062965 for ; Fri, 15 Oct 2010 14:03:00 -0700 (MST) (envelope-from jasnell@gmail.com) Received: by qyk35 with SMTP id 35so1471594qyk.16 for ; Fri, 15 Oct 2010 14:02:57 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:date:message-id :subject:from:to:content-type; bh=c2mRcclI+0W8jGuVVxVXXzBcIJo2mAM8udlawKRDVw4=; b=mtwJOHqUmDvjPRDlxOClpqn4BwGS84StKoBYqUJDu+suoC7EfnnLjw3YP92Q6VbixU /aiRCu4HbFdELKNrKCNXruxPvMYucqB8TmzOa43rNU0rkOMQS46D8DPCUnEI3lkRO0gv AQmQ660hPEtgktrwAv5aIoT+84tGyPfoGyw0I= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=JrGl8Uejpm9LfzuEtGJ5CouQheqyxVOEdF6XrN4xo1oLHrItA/9WabQ6rOf/u0mdtH 6rAdyCfbsLIAhRE8ljluDTLy/B/c22l6marhdrQpiEsgVAcIssSvJx8olyfsb6aoG75V GfAt4D6CBGP0acwPqjVD0DC2I+h0X4HM+zxTQ= MIME-Version: 1.0 Received: by 10.229.219.80 with SMTP id ht16mr1176627qcb.53.1287176567044; Fri, 15 Oct 2010 14:02:47 -0700 (PDT) Received: by 10.229.114.194 with HTTP; Fri, 15 Oct 2010 14:02:47 -0700 (PDT) Date: Fri, 15 Oct 2010 14:02:47 -0700 Message-ID: Subject: to/cc/bcc extension From: James Snell To: Atom-Syntax Content-Type: multipart/alternative; boundary=0016363b83780abafd0492ae26f2 Sender: owner-atom-syntax@mail.imc.org Precedence: bulk List-Archive: List-Unsubscribe: List-ID: --0016363b83780abafd0492ae26f2 Content-Type: text/plain; charset=ISO-8859-1 Wanted to draw attention to this: http://tools.ietf.org/html/draft-norris-atompub-audience-00.html It introduces to/cc/bcc elements to an Atom entry. ... acct:john.doe@example.org acct:bob@example.org acct:jane.doe@example.org acct:jane@example.org acct:jean.deux@example.org acct:max@example.org ... Comments are welcomed and requested. - James --0016363b83780abafd0492ae26f2 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Wanted to draw attention to this:

=A0=A0http://to= ols.ietf.org/html/draft-norris-atompub-audience-00.html

<= /div>

It introduces to/cc/bcc elements to an Atom entry.

=A0=A0<entry>

=A0=A0 =A0...

=A0=A0 =A0<t= o>acct:john.doe@example.o= rg</to>

=A0=A0 =A0<to>acct:bob= @example.org</to>

=A0=A0 =A0<cc>acct:jane.doe@example.org</cc>

=A0=A0 =A0<cc>acct:j= ane@example.org</cc>

=A0=A0 =A0<bcc>a= cct:jean.deux@example.org</bcc>

=A0=A0 =A0<bcc>acct:max@example.org</bcc>= ;

=A0=A0 =A0...

=A0=A0</entry>

Comme= nts are welcomed and requested.

- James

--0016363b83780abafd0492ae26f2-- From owner-atom-syntax@mail.imc.org Fri Oct 15 15:45:08 2010 Return-Path: X-Original-To: ietfarch-atompub-archive@core3.amsl.com Delivered-To: ietfarch-atompub-archive@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2954D3A6A30 for ; Fri, 15 Oct 2010 15:45:08 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.045 X-Spam-Level: X-Spam-Status: No, score=-102.045 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_MISMATCH_COM=0.553, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Mlptr9SAo2vb for ; Fri, 15 Oct 2010 15:45:06 -0700 (PDT) Received: from hoffman.proper.com (Hoffman.Proper.COM [207.182.41.81]) by core3.amsl.com (Postfix) with ESMTP id 7C6223A6AF9 for ; Fri, 15 Oct 2010 15:45:03 -0700 (PDT) Received: from hoffman.proper.com (localhost [127.0.0.1]) by hoffman.proper.com (8.14.4/8.14.3) with ESMTP id o9FMfINi067066 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 15 Oct 2010 15:41:18 -0700 (MST) (envelope-from owner-atom-syntax@mail.imc.org) Received: (from majordom@localhost) by hoffman.proper.com (8.14.4/8.13.5/Submit) id o9FMfIdB067065; Fri, 15 Oct 2010 15:41:18 -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-out3.apple.com (mail-out.apple.com [17.254.13.22]) by hoffman.proper.com (8.14.4/8.14.3) with ESMTP id o9FMfH4r067060 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Fri, 15 Oct 2010 15:41:17 -0700 (MST) (envelope-from prabhaka@apple.com) Received: from relay13.apple.com (relay13.apple.com [17.128.113.29]) by mail-out3.apple.com (Postfix) with ESMTP id 11ECCAFAECAE for ; Fri, 15 Oct 2010 15:41:17 -0700 (PDT) X-AuditID: 1180711d-b7c86ae000000247-36-4cb8d88ccfc0 Received: from elliott.apple.com (elliott.apple.com [17.151.62.13]) by relay13.apple.com (Apple SCV relay) with SMTP id 3A.44.00583.C88D8BC4; Fri, 15 Oct 2010 15:41:17 -0700 (PDT) MIME-version: 1.0 Content-type: multipart/alternative; boundary="Boundary_(ID_35P42CWUH2ixN8YoHUYsSw)" Received: from selfserve.apple.com (selfserve.apple.com [17.203.40.11]) by elliott.apple.com (Sun Java(tm) System Messaging Server 6.3-7.04 (built Sep 26 2008; 32bit)) with ESMTPSA id <0LAC000POSCS31A0@elliott.apple.com> for atom-syntax@imc.org; Fri, 15 Oct 2010 15:41:16 -0700 (PDT) Subject: Re: to/cc/bcc extension From: "Ernest N. Prabhakar, Ph.D." In-reply-to: Date: Fri, 15 Oct 2010 15:41:16 -0700 Cc: Atom-Syntax Message-id: <989FF0D2-FD4F-48C4-AFE8-CD61C67E4A55@apple.com> References: To: James Snell X-Mailer: Apple Mail (2.1082) X-Brightmail-Tracker: AAAAAA== Sender: owner-atom-syntax@mail.imc.org Precedence: bulk List-Archive: List-Unsubscribe: List-ID: --Boundary_(ID_35P42CWUH2ixN8YoHUYsSw) Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT HI James, Given our previous discussion about icons: why aren't these link relations with mailto URLs? -- Ernie P. On Oct 15, 2010, at 2:02 PM, James Snell wrote: > Wanted to draw attention to this: > > http://tools.ietf.org/html/draft-norris-atompub-audience-00.html > > It introduces to/cc/bcc elements to an Atom entry. > > > ... > acct:john.doe@example.org > acct:bob@example.org > acct:jane.doe@example.org > acct:jane@example.org > acct:jean.deux@example.org > acct:max@example.org > ... > > > Comments are welcomed and requested. > > - James --Boundary_(ID_35P42CWUH2ixN8YoHUYsSw) Content-type: text/html; charset=us-ascii Content-transfer-encoding: 7BIT HI James,

Given our previous discussion about icons: why aren't these link relations with mailto URLs?

-- Ernie P.

On Oct 15, 2010, at 2:02 PM, James Snell wrote:

Wanted to draw attention to this:

  http://tools.ietf.org/html/draft-norris-atompub-audience-00.html

It introduces to/cc/bcc elements to an Atom entry.

  <entry>
   ...
   <to>acct:john.doe@example.org</to>

   <to>acct:bob@example.org</to>
   <cc>acct:jane.doe@example.org</cc>
   <cc>acct:jane@example.org</cc>

   <bcc>acct:jean.deux@example.org</bcc>
   <bcc>acct:max@example.org</bcc>
   ...
  </entry>

Comments are welcomed and requested.

- James

--Boundary_(ID_35P42CWUH2ixN8YoHUYsSw)-- From owner-atom-syntax@mail.imc.org Fri Oct 15 15:57:52 2010 Return-Path: X-Original-To: ietfarch-atompub-archive@core3.amsl.com Delivered-To: ietfarch-atompub-archive@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7A4903A6AD4 for ; Fri, 15 Oct 2010 15:57:52 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.187 X-Spam-Level: X-Spam-Status: No, score=-0.187 tagged_above=-999 required=5 tests=[BAYES_20=-0.74, HELO_MISMATCH_COM=0.553] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ftpv-mziayLJ for ; Fri, 15 Oct 2010 15:57:51 -0700 (PDT) Received: from hoffman.proper.com (Hoffman.Proper.COM [207.182.41.81]) by core3.amsl.com (Postfix) with ESMTP id 147483A68E0 for ; Fri, 15 Oct 2010 15:57:50 -0700 (PDT) Received: from hoffman.proper.com (localhost [127.0.0.1]) by hoffman.proper.com (8.14.4/8.14.3) with ESMTP id o9FMsOlq067721 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 15 Oct 2010 15:54:24 -0700 (MST) (envelope-from owner-atom-syntax@mail.imc.org) Received: (from majordom@localhost) by hoffman.proper.com (8.14.4/8.13.5/Submit) id o9FMsOnK067720; Fri, 15 Oct 2010 15:54:24 -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-wy0-f171.google.com (mail-wy0-f171.google.com [74.125.82.171]) by hoffman.proper.com (8.14.4/8.14.3) with ESMTP id o9FMsNbI067715 for ; Fri, 15 Oct 2010 15:54:24 -0700 (MST) (envelope-from alexander.johannesen@gmail.com) Received: by wya21 with SMTP id 21so1458998wya.16 for ; Fri, 15 Oct 2010 15:54:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=4nrhAip1/jQF1JEKW0PMrf4T+7Ud4ldiVJgKmz3dc7M=; b=luZvI/hhGMNdHkaa7dNrphJaaX48Itid8YixJjyOs+GLu3W/nZjR/+A04qbFEftm85 XGrkmD37Ql9Qc+qvs5kc13rjxFTdaQmx6AFkJfXdZW9OsMpQeHmSHuQi5cW3mRqhMX9E EkEKJvzhkFEE/XisKnN/IuMG1Q9y2k6dtBa9Q= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=tOXH8rit3o+KJ9WXdAKlqRPhi15DeO5D8x4NuXFphMmnOeWodI9PZHaIewYzPqP0qe U/ZGvWBBA3AG/cJg0Kjwf4vaI9NFMc7DdzVzCNVNY2Vu1frUe1FhtcVPNLah+5bJlFNM sHSC5kfHSZSjR7eHrA7kr17HKtzLp0NLstywg= MIME-Version: 1.0 Received: by 10.216.3.145 with SMTP id 17mr2191162weh.109.1287183253410; Fri, 15 Oct 2010 15:54:13 -0700 (PDT) Received: by 10.216.155.129 with HTTP; Fri, 15 Oct 2010 15:54:13 -0700 (PDT) In-Reply-To: <989FF0D2-FD4F-48C4-AFE8-CD61C67E4A55@apple.com> References: <989FF0D2-FD4F-48C4-AFE8-CD61C67E4A55@apple.com> Date: Sat, 16 Oct 2010 09:54:13 +1100 Message-ID: Subject: Re: to/cc/bcc extension From: Alexander Johannesen To: "Ernest N. Prabhakar, Ph.D." Cc: James Snell , Atom-Syntax Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hoffman.proper.com id o9FMsObI067716 Sender: owner-atom-syntax@mail.imc.org Precedence: bulk List-Archive: List-Unsubscribe: List-ID: *grumble* > Given our previous discussion about icons: why aren't these link relations > with mailto URLs? Not meant to fixate this on the follow-up'er, but everything you ever wanted and extend Atom with is just conceptual things. There is no difference between a defined ontology with all the entities and relationships of Atom, and in fact you can define the whole shebang in any ontological language. It just so happens that Atom is a short-list of ontological expression defined in a format of sorts. Where do the data model, format it's defined in and the ontology stop and start? At some point the Atom model becomes so complex that it loses its easy applicability, and perhaps should enter the realm of ontological work. Anyone done any mappings of this so far? Kind regards, Alex -- Project Wrangler, SOA, Information Alchemist, UX, RESTafarian, Topic Maps --- http://shelter.nu/blog/ ---------------------------------------------- ------------------ http://www.google.com/profiles/alexander.johannesen --- From owner-atom-syntax@mail.imc.org Fri Oct 15 16:00:25 2010 Return-Path: X-Original-To: ietfarch-atompub-archive@core3.amsl.com Delivered-To: ietfarch-atompub-archive@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id CBCC03A68E0 for ; Fri, 15 Oct 2010 16:00:25 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.451 X-Spam-Level: X-Spam-Status: No, score=-0.451 tagged_above=-999 required=5 tests=[AWL=1.595, BAYES_00=-2.599, HELO_MISMATCH_COM=0.553, HTML_MESSAGE=0.001] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id q7+o97NVBk4R for ; Fri, 15 Oct 2010 16:00:24 -0700 (PDT) Received: from hoffman.proper.com (Hoffman.Proper.COM [207.182.41.81]) by core3.amsl.com (Postfix) with ESMTP id 9E7483A6A2D for ; Fri, 15 Oct 2010 16:00:24 -0700 (PDT) Received: from hoffman.proper.com (localhost [127.0.0.1]) by hoffman.proper.com (8.14.4/8.14.3) with ESMTP id o9FMvjqL067836 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 15 Oct 2010 15:57:45 -0700 (MST) (envelope-from owner-atom-syntax@mail.imc.org) Received: (from majordom@localhost) by hoffman.proper.com (8.14.4/8.13.5/Submit) id o9FMvjJ2067835; Fri, 15 Oct 2010 15:57:45 -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-qy0-f171.google.com (mail-qy0-f171.google.com [209.85.216.171]) by hoffman.proper.com (8.14.4/8.14.3) with ESMTP id o9FMvi7n067830 for ; Fri, 15 Oct 2010 15:57:45 -0700 (MST) (envelope-from jasnell@gmail.com) Received: by qyk9 with SMTP id 9so1931759qyk.16 for ; Fri, 15 Oct 2010 15:57:44 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=gClW3PDrhPVbTMX0JKjlPTjLkR5p0VLhGL0YWaUyBDE=; b=u0RcxqGTz1GAGzn7/zgb+y8gJSOwoAHyBN7h+tKDzvvbSuDAPR4JRQEIM/I/f4jpr8 fVyNGV7cQX4Gzv1/e4usQzUQhAu5TLL9lp+JPTVpf07ijdDoZMaNQ+OG1BzQZZrt70DW beR1OeKtlhPQDd1Azc0TZhphq7dvwKuK1rVwc= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=abh0p4uEixJkZMxuMjdQdFxx7vg43COvpkfU1g2lfoqosbOxQTFtQ6LS4dbvEaGpm2 wY7vdUzMmJmVAU/Gohq0tynPHOy+Jk0OpEL4fAEJc4R63krPV4uSHhESVZZ/2VTWka30 aq0LjAL8aOqGgo2nWZPGcQ5O3jo9VPbIQWpyg= MIME-Version: 1.0 Received: by 10.229.250.81 with SMTP id mn17mr1226852qcb.291.1287183464148; Fri, 15 Oct 2010 15:57:44 -0700 (PDT) Received: by 10.229.114.194 with HTTP; Fri, 15 Oct 2010 15:57:44 -0700 (PDT) In-Reply-To: <989FF0D2-FD4F-48C4-AFE8-CD61C67E4A55@apple.com> References: <989FF0D2-FD4F-48C4-AFE8-CD61C67E4A55@apple.com> Date: Fri, 15 Oct 2010 15:57:44 -0700 Message-ID: Subject: Re: to/cc/bcc extension From: James Snell To: "Ernest N. Prabhakar, Ph.D." Cc: Atom-Syntax Content-Type: multipart/alternative; boundary=0016363b8eb0248b7e0492afc11f Sender: owner-atom-syntax@mail.imc.org Precedence: bulk List-Archive: List-Unsubscribe: List-ID: --0016363b8eb0248b7e0492afc11f Content-Type: text/plain; charset=ISO-8859-1 link certainly could be used but just doesn't seem like a good fit. Things like type, length, hreflang, nor ANY of the proposed link extensions would apply. On Fri, Oct 15, 2010 at 3:41 PM, Ernest N. Prabhakar, Ph.D. < prabhaka@apple.com> wrote: > HI James, > > Given our previous discussion about icons: why aren't these link relations > with mailto URLs? > > -- Ernie P. > > On Oct 15, 2010, at 2:02 PM, James Snell wrote: > > Wanted to draw attention to this: > > http://tools.ietf.org/html/draft-norris-atompub-audience-00.html > > It introduces to/cc/bcc elements to an Atom entry. > > > ... > acct:john.doe@example.org > acct:bob@example.org > acct:jane.doe@example.org > acct:jane@example.org > acct:jean.deux@example.org > acct:max@example.org > ... > > > Comments are welcomed and requested. > > - James > > > --0016363b8eb0248b7e0492afc11f Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable link certainly could be used but just doesn't seem like a good fit. Thi= ngs like type, length, hreflang, nor ANY of the proposed link extensions wo= uld apply.

On Fri, Oct 15= , 2010 at 3:41 PM, Ernest N. Prabhakar, Ph.D. <prabhaka@apple.com> wrote:

HI Jame= s,

Given our previous discussion about icons: why aren&#= 39;t these link relations with mailto URLs?

-- Ernie P.

On Oct 15, 2010, at 2:02 PM, James Snell wrote:

Wanted to draw attention to this:

=A0=A0http://tools.ietf.org/html/draft-norris-atom= pub-audience-00.html

It introduces to/cc/bcc elements to an Atom entry.

=A0=A0<entry>
=A0=A0 =A0...
=A0=A0 =A0<t= o>acct:= john.doe@example.org</to>

=A0=A0 =A0<to>acct:bob@example.org</to>
=A0=A0 =A0<cc&= gt;acct:ja= ne.doe@example.org</cc>

=A0=A0 =A0<cc>acct:jane@example.org</cc>

=A0=A0 =A0<bcc>acct:jean.deux@example.org</bcc>
=A0= =A0 =A0<bcc>acct:max@example.org</bcc>

=A0=A0 =A0...
=A0=A0</entry>

Comme= nts are welcomed and requested.

- James