
From owner-atom-syntax@mail.imc.org  Tue Jun  1 14:00:28 2010
Return-Path: <owner-atom-syntax@mail.imc.org>
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 A689928C172 for <ietfarch-atompub-archive@core3.amsl.com>; Tue,  1 Jun 2010 14:00:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.382
X-Spam-Level: **
X-Spam-Status: No, score=2.382 tagged_above=-999 required=5 tests=[AWL=0.595, BAYES_50=0.001, DRUGS_MUSCLE=0.01, FM_FORGED_GMAIL=0.622, HELO_MISMATCH_COM=0.553, HTML_MESSAGE=0.001, J_CHICKENPOX_84=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 jNwJ9t3bhHP1 for <ietfarch-atompub-archive@core3.amsl.com>; Tue,  1 Jun 2010 14:00:26 -0700 (PDT)
Received: from hoffman.proper.com (Hoffman.Proper.COM [207.182.41.81]) by core3.amsl.com (Postfix) with ESMTP id CED9A28C183 for <atompub-archive@ietf.org>; Tue,  1 Jun 2010 14:00:25 -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 o51KpRG5065140 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 1 Jun 2010 13:51:28 -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 o51KpReg065139; Tue, 1 Jun 2010 13:51:27 -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-gw0-f43.google.com (mail-gw0-f43.google.com [74.125.83.43]) by hoffman.proper.com (8.14.4/8.14.3) with ESMTP id o51KpPO7065132 for <atom-syntax@imc.org>; Tue, 1 Jun 2010 13:51:25 -0700 (MST) (envelope-from bobwyman@gmail.com)
Received: by gwj17 with SMTP id 17so796gwj.16 for <atom-syntax@imc.org>; Tue, 01 Jun 2010 13:51: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; bh=iAeQE5OkXKMBdibbjKgNbnCNZP6d4kvOtcoeSAHAxsA=; b=nMD0+U1VvCRmczTv97XmlOOkG5hgwjXWnwvzDdAX8/H8hM4vpBWX0Bc23id61b3cJH /rAtYSVJLvG3z7CJk77h/BDwtEktlF7Zsrpe9vcAhIwccyADloM5jMx9mBSTMWzbEzmY zZOX/3q0OdAGmDrZoNi33f3Lpc+CMHyGuA9X8=
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=oiVOoyeuGIn9P4fSrLYJavU6YKUUnRREFh6+fTY/1q4YL+9ud5JZI3xo2ge+ORjwUv C+wr5uK4olrtezoS48M1pexmZP31BZJ8X6h1t1YN03gopSz8fAw+DTbnTqsaw6wjiFxL u4IFEIVpoLu+qSZCMvUUguV4bjULMbr5vm/KA=
MIME-Version: 1.0
Received: by 10.101.132.37 with SMTP id j37mr6827825ann.121.1275425483362;  Tue, 01 Jun 2010 13:51:23 -0700 (PDT)
Received: by 10.100.92.4 with HTTP; Tue, 1 Jun 2010 13:51:23 -0700 (PDT)
In-Reply-To: <AANLkTikIA_3-LD3wvb5N97ViC-HASoj0VTFB0lKKwP0S@mail.gmail.com>
References: <y2m45be5cd41005041054g84783901s93762ddb7e1cfd7@mail.gmail.com> <AANLkTilb9drws_aRlRuLFSrdDJPPYhFKA63QoxmY5ILt@mail.gmail.com> <AANLkTikc3UQPklmtmfuC_jFT9vRsSnVkaX6ZyMcOG_SL@mail.gmail.com> <AANLkTikVRq2FBiOd1ZDVT1S-6XrcLOTIJHGmsRAvVEw-@mail.gmail.com> <AANLkTilr-ojtfyYv-NTEIui9iyF8ffRXrprE7uZcaPQ1@mail.gmail.com> <OF8D87FFBD.96E5765F-ON85257722.001410D7-85257722.001524AE@us.ibm.com> <AANLkTil_M_Yn2BMYNajItDsTIRVpiPrqux3_SL_8xl7m@mail.gmail.com> <AANLkTikkAaqFxdBrBNuLxzqqRbWdMQNpzlE3eWLeiqDA@mail.gmail.com> <AANLkTilu72DUQsd_K4z6HfX8t_VBJ2nc-Fl8zIZkMUNJ@mail.gmail.com> <AANLkTinylkd6k8hyPvo4JFQ_TpNdKbFLqdGl_Y_nUyxU@mail.gmail.com> <AANLkTikIA_3-LD3wvb5N97ViC-HASoj0VTFB0lKKwP0S@mail.gmail.com>
Date: Tue, 1 Jun 2010 16:51:23 -0400
X-Google-Sender-Auth: LeZPmu0dE_j1RdqkdyMJUO58uBM
Message-ID: <AANLkTimh4q8knqK8llxRccTDN2r5qmaPT32tfc9iFkjt@mail.gmail.com>
Subject: Re: Link Extensions. Need "md5" or some kind of hash.
From: Bob Wyman <bob@wyman.us>
To: James Snell <jasnell@gmail.com>
Cc: Sam Johnston <samj@samj.net>, Richard Salz <rsalz@us.ibm.com>, Atom-Syntax <atom-syntax@imc.org>
Content-Type: multipart/alternative; boundary=0016e68ee1e3df97c50487fe2238
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>

--0016e68ee1e3df97c50487fe2238
Content-Type: text/plain; charset=ISO-8859-1

FYI: The new RFC5854 re: "Metalink Download Description Format" defines a
"hash" element in its section 4.2.4. They have chosen to use the method of
storing the hash algorithm in a different element than the hash value. That
is, in my opinion, unfortunate. I *do not* suggest that we follow their
lead. I'm just posting this here so that folk can be aware of what others
are doing in other contexts.

The relevant text from RFC5854 follows:

4.2.4.  The "metalink:hash" Element

   The "metalink:hash" element is a Text construct that conveys a
   cryptographic hash for a file.  All hashes are encoded in lowercase
   hexadecimal format.  Hashes are used to verify the integrity of a
   complete file or portion of a file to determine if the file has been
   transferred without any errors.

   metalinkHash =
      element metalink:hash {
        attribute type { text }?,
        text
      }

   Metalink Documents MAY contain one or multiples hashes of a complete
   file. metalink:hash elements with a "type" attribute MUST contain a
   hash of the complete file.  In this example, both SHA-1 and SHA-256
   hashes of the complete file are included.

 ...
   <hash type="sha-1">a97fcf6ba9358f8a6f62beee4421863d3e52b080</hash>
   <hash type="sha-256">fc87941af7fd7f03e53b34af393f4c14923d74...</hash>
 ...

   Metalink Documents MAY also contain hashes for individual pieces of a
   file. metalink:hash elements that are inside a metalink:pieces
   container element have a hash for that specific piece or chunk of the
   file, and are of the same hash type as the metalink:pieces element in
   which they are contained.  Metalink Documents MAY contain one or
   multiple metalink:pieces container elements, if each "type" attribute
   of metalink:pieces has a unique value.

   metalink:hash elements without a "type" attribute MUST contain a hash
   for that specific piece or chunk of the file and MUST be listed in
   the same order as the corresponding pieces appear in the file,
   starting at the beginning of the file.  The size of the piece is
   equal to the value of the "length" attribute of the metalink:pieces
   element, apart from the last piece, which is the remainder.  See
   Section 4.1.3.2 for more information on the size of pieces.

   In this example, SHA-1 and SHA-256 hashes of the complete file are
   included, along with four SHA-1 piece hashes.

 ...
   <hash type="sha-1">a97fcf6ba9358f8a6f62beee4421863d3e52b080</hash>
   <hash type="sha-256">fc87941af7fd7f03e53b34af393f4c14923d74...</hash>
   <pieces length="1048576" type="sha-1">
     <hash>d96b9a4b92a899c2099b7b31bddb5ca423bb9b30</hash>
     <hash>10d68f4b1119014c123da2a0a6baf5c8a6d5ba1e</hash>
     <hash>3e84219096435c34e092b17b70a011771c52d87a</hash>
     <hash>67183e4c3ab892d3ebe8326b7d79eb62d077f487</hash>
   </pieces>
 ...



On Sun, May 16, 2010 at 11:29 PM, James Snell <jasnell@gmail.com> wrote:

> Ok, although I seriously dislike having to do additional parsing on
> attribute values, the arguments made so far are valid and parsing hex
> encoded hash digests is -- fortunately -- quite simple to do. So let's
> go with the following syntax...
>
>  hash = attribute hash { hash-list }
>  hash-list = # ( token ":" 1*HEX )
>
> The token and HEX productions are defined by RFC2616...
>
> The spec would defer to the existing IANA registry for hash functions
> to define the "tokens"
>
> This would result in a syntax of...
>
>  hash="md5:abc...xyz, sha-1:123...567, sha-512:xyz...abc"
>
> This seem acceptable to everyone?
>
> - James
>
> On Sat, May 15, 2010 at 11:46 PM, Sam Johnston <samj@samj.net> wrote:
> > James,
> > In consideration of former (CRC) and future (AHS) hashing functions I
> think
> > it's critical to support extensibility and multiple hashes. I like that
> XML
> > digsigs use anyURIs to identify hashes (e.g. <DigestMethod
> > Algorithm="http://www.w3.org/2000/09/xmldsig#sha1">), but one could
> argue
> > this unnecessarily complicates what should be a simple syntax.
> > I was about to propose an IANA registry for hash functions but one
> already
> > exists (Hash Function Textual Names as specified by RFC4572) so it would
> > make sense to use it rather than inventing our own mechanism - even if we
> > have to update the registry rules to allow for algorithms specified by
> URI
> > rather than RFC.
> > While Atom is an XML format and should arguably follow XML conventions,
> > there is precedent for prefixing hashes with the name of the hashing
> > function using e.g. colons or curly braces. I think it's more important
> to
> > keep the XML syntax simple and in any case the hash and hash function
> should
> > be tightly bound as they are useless independently.
> > All that considered, I think the best approach is to allow for a
> > multi-valued "hash" attribute ala:
> > <link rel="alternate" href="http://example.com/"
> > hash="md5:6705f99eccedeac20e969bef954c5fb0
> > sha-1:bc608e6d3d339d1a7afc406a7ea6a8f07358038b" />
> > and/or
> > <link rel="alternate" href="http://example.com/thing.pdf"
> > hash="md5:6705f99eccedeac20e969bef954c5fb0"
> > hash="sha-1:bc608e6d3d339d1a7afc406a7ea6a8f07358038b" />
> > Sam
> > Google
> > On Sat, May 15, 2010 at 1:15 AM, James Snell <jasnell@gmail.com> wrote:
> >>
> >> Good argument Bob... ok... stewing over this a bit more. I generally
> >> dislike having to do additional parsing of attribute/element values
> >> but there are very good reasons for keeping this as a single "hash"
> >> attribute and you make a compelling case.
> >>
> >> On Fri, May 14, 2010 at 1:26 PM, Bob Wyman <bob@wyman.us> wrote:
> >> > James Snell <jasnell@gmail.com> wrote:
> >> >> <link href="foo" md5="abc...xyz">
> >> >>  <media:hash algo="GOST">123...456</media:hash>
> >> >> </link>
> >> >
> >> > The alternative approach, which would support both a variety
> >> > and multiplicity of hashes would look like this:
> >> > <link href="foo" hash="gost:123123..., md5:0928402948...,
> >> > sha256:098078097..."/>
> >> > This strikes me as "simpler" than the hybrid approach. Just a few of
> my
> >> > concerns with the proposed "hybrid" approach follow:
> >> >
> >> > I like binding the algorithm and value together into a single value
> >> > since I
> >> > know of no compelling case for processing one element in isolation of
> >> > the
> >> > other. The hash value only makes sense if you know the algorithm and
> the
> >> > algorithm is only useful when bound to a specific hash value. Thus, it
> >> > strikes me as simply introducing syntactic sugar to specify the
> >> > algorithm
> >> > using a different XML component than the value.
> >> > These values are likely to be stored in databases and otherwise
> >> > manipulated.
> >> > In all cases, for the data to be meaningful, people will need to keep
> >> > the
> >> > binding between algorithm and hash value. It is likely that storing a
> >> > single
> >> > string value is going to be easier for folk than dealing with a
> >> > multi-part
> >> > value. Also, consider the effect of parsers... It is likely that in
> >> > order to
> >> > transfer a value from an entry into a database field, what you'll need
> >> > to do
> >> > is extract both algorithm and hash value from the parse tree and then
> >> > construct some string that combines them. This would be particularly
> >> > useful
> >> > if you want to use the hash value as a database key (a very reasonable
> >> > thing
> >> > to do...) You could build and store the string
> "algo='GOST'>123...455<"
> >> > or
> >> > your database might support concatenated fields, or you could build
> >> > "gost.123...456". I think I would go with the latter.
> >> > Defining distinct attributes for each hash algorithm pushes
> unnecessary
> >> > syntactical complexity to the global level and thus increases the
> >> > complexity
> >> > not only of the specification but also of all applications no matter
> >> > which
> >> > algorithms they understand or if they understand any at all. It also
> >> > makes
> >> > extending the list of supported algorithms "expensive" since such
> >> > extensions
> >> > require modification to the standard rather than just an registry
> >> > entry.What
> >> > benefit do we get from having these algorithm types defined at the
> >> > global
> >> > syntax level?
> >> > The hybrid approach looks very complicated to me. It means that I'll
> >> > have
> >> > two very different places in which hash values might found and two
> very
> >> > different syntaxes for expressing them. The result is going to be more
> >> > complex code than would otherwise be the case. What value comes from
> >> > using
> >> > the hybrid approach?
> >> > One argument for hybrid is that these elements exist already in other
> >> > specs.
> >> > I wonder if it isn't possible that those other specs might have
> >> > approached
> >> > the problem in a non-optimal fashion. Does it really make sense to
> >> > import
> >> > syntax if there isn't a really good case that demonstrates that doing
> so
> >> > is
> >> > the best approach?
> >> > I am unaware of any hash algorithms that need anything other than the
> >> > specification of the algorithm and the value in order to be useful. If
> >> > there
> >> > were broadly used algorithms that had more complex meta-data
> >> > requirements,
> >> > it would be easier to understand the appeal of the hybrid approach.
> >> > I can't think of any reason why it is *useful* to separate the
> algorithm
> >> > from the hash value. Can someone enlighten me here? What computation,
> >> > storage or communication task becomes easier if you have these two
> >> > separated?
> >> >
> >> > bob wyman
> >> > On Fri, May 14, 2010 at 3:06 PM, James Snell <jasnell@gmail.com>
> wrote:
> >> >>
> >> >> Ok, I've been giving this some more thought and I think a hybrid
> >> >> approach works very well. As has been pointed out a number of times
> in
> >> >> this thread, there are existing elements in other namespaces that
> >> >> provide a algorithm/hash pairing. I think that the Link Extensions
> >> >> Draft can provide a attributes for the most basic hash algorithms and
> >> >> applications that require hash algorithms that are not covered can
> >> >> fall back to the extension elements.
> >> >>
> >> >> e.g.
> >> >>
> >> >> <link href="foo" md5="abc...xyz">
> >> >>  <media:hash algo="GOST">123...456</media:hash>
> >> >> </link>
> >> >>
> >> >> This would allow for the most common cases to be easily covered while
> >> >> allowing for the full range of possible cases to be handled as well.
> >> >>
> >> >> - James
> >> >>
> >> >> On Wed, May 12, 2010 at 8:50 PM, Richard Salz <rsalz@us.ibm.com>
> wrote:
> >> >> >> So the key question is: what are the main algorithms we need to
> >> >> >> provide attributes for?
> >> >> >
> >> >> > This is a hard question to answer -- especially for hash/digest
> >> >> > algorithms
> >> >> > which tend to fall more rapidly than vetted crypto algorithms.
> >> >> >
> >> >> > It's more verbose, but I strongly recommend using a pair of
> >> >> > attributes
> >> >> > to
> >> >> > represent algorithm/value. Use the URI's defined in the latest XML
> >> >> > DSIG
> >> >> > document, perhaps with the "trick" that relative URI's ar a
> shorthand
> >> >> > for
> >> >> > the xmldsig namespace.
> >> >> >
> >> >> >        /r$
> >> >> >
> >> >> > --
> >> >> > STSM, WebSphere Appliance Architect
> >> >> > https://www.ibm.com/developerworks/mydeveloperworks/blogs/soma/
> >> >> >
> >> >> >
> >> >>
> >> >>
> >> >>
> >> >> --
> >> >> - James Snell
> >> >>  http://www.snellspace.com
> >> >>  jasnell@gmail.com
> >> >>
> >> >
> >> >
> >>
> >>
> >>
> >> --
> >> - James Snell
> >>  http://www.snellspace.com
> >>  jasnell@gmail.com
> >>
> >
> >
>

--0016e68ee1e3df97c50487fe2238
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

FYI: The new RFC5854 re: &quot;<span class=3D"Apple-style-span" style=3D"fo=
nt-family: monospace; font-size: medium; white-space: pre-wrap; ">Metalink =
Download Description Format</span>&quot; defines a &quot;hash&quot; element=
 in its section 4.2.4. They have chosen to use the method of storing the ha=
sh algorithm in a different element than the hash value. That is, in my opi=
nion, unfortunate. I <b>do not</b> suggest that we follow their lead. I&#39=
;m just posting this here so that folk can be aware of what others are doin=
g in other contexts.<div>
<br></div><div>The relevant text from RFC5854 follows:</div><div><span clas=
s=3D"Apple-style-span" style=3D"font-family: &#39;Times New Roman&#39;; fon=
t-size: medium; "><pre style=3D"word-wrap: break-word; white-space: pre-wra=
p; ">
4.2.4.  The &quot;metalink:hash&quot; Element

   The &quot;metalink:hash&quot; element is a Text construct that conveys a
   cryptographic hash for a file.  All hashes are encoded in lowercase
   hexadecimal format.  Hashes are used to verify the integrity of a
   complete file or portion of a file to determine if the file has been
   transferred without any errors.

   metalinkHash =3D
      element metalink:hash {
        attribute type { text }?,
        text
      }

   Metalink Documents MAY contain one or multiples hashes of a complete
   file. metalink:hash elements with a &quot;type&quot; attribute MUST cont=
ain a
   hash of the complete file.  In this example, both SHA-1 and SHA-256
   hashes of the complete file are included.

 ...
   &lt;hash type=3D&quot;sha-1&quot;&gt;a97fcf6ba9358f8a6f62beee4421863d3e5=
2b080&lt;/hash&gt;
   &lt;hash type=3D&quot;sha-256&quot;&gt;fc87941af7fd7f03e53b34af393f4c149=
23d74...&lt;/hash&gt;
 ...

   Metalink Documents MAY also contain hashes for individual pieces of a
   file. metalink:hash elements that are inside a metalink:pieces
   container element have a hash for that specific piece or chunk of the
   file, and are of the same hash type as the metalink:pieces element in
   which they are contained.  Metalink Documents MAY contain one or
   multiple metalink:pieces container elements, if each &quot;type&quot; at=
tribute
   of metalink:pieces has a unique value.

   metalink:hash elements without a &quot;type&quot; attribute MUST contain=
 a hash
   for that specific piece or chunk of the file and MUST be listed in
   the same order as the corresponding pieces appear in the file,
   starting at the beginning of the file.  The size of the piece is
   equal to the value of the &quot;length&quot; attribute of the metalink:p=
ieces
   element, apart from the last piece, which is the remainder.  See
   Section 4.1.3.2 for more information on the size of pieces.<br></pre><pr=
e style=3D"word-wrap: break-word; white-space: pre-wrap; ">   In this examp=
le, SHA-1 and SHA-256 hashes of the complete file are
   included, along with four SHA-1 piece hashes.

 ...
   &lt;hash type=3D&quot;sha-1&quot;&gt;a97fcf6ba9358f8a6f62beee4421863d3e5=
2b080&lt;/hash&gt;
   &lt;hash type=3D&quot;sha-256&quot;&gt;fc87941af7fd7f03e53b34af393f4c149=
23d74...&lt;/hash&gt;
   &lt;pieces length=3D&quot;1048576&quot; type=3D&quot;sha-1&quot;&gt;
     &lt;hash&gt;d96b9a4b92a899c2099b7b31bddb5ca423bb9b30&lt;/hash&gt;
     &lt;hash&gt;10d68f4b1119014c123da2a0a6baf5c8a6d5ba1e&lt;/hash&gt;
     &lt;hash&gt;3e84219096435c34e092b17b70a011771c52d87a&lt;/hash&gt;
     &lt;hash&gt;67183e4c3ab892d3ebe8326b7d79eb62d077f487&lt;/hash&gt;
   &lt;/pieces&gt;
 ...
</pre><div><br></div></span><br><div class=3D"gmail_quote">On Sun, May 16, =
2010 at 11:29 PM, James Snell <span dir=3D"ltr">&lt;<a href=3D"mailto:jasne=
ll@gmail.com">jasnell@gmail.com</a>&gt;</span> wrote:<br><blockquote class=
=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padd=
ing-left:1ex;">
Ok, although I seriously dislike having to do additional parsing on<br>
attribute values, the arguments made so far are valid and parsing hex<br>
encoded hash digests is -- fortunately -- quite simple to do. So let&#39;s<=
br>
go with the following syntax...<br>
<br>
 =A0hash =3D attribute hash { hash-list }<br>
 =A0hash-list =3D # ( token &quot;:&quot; 1*HEX )<br>
<br>
The token and HEX productions are defined by RFC2616...<br>
<br>
The spec would defer to the existing IANA registry for hash functions<br>
to define the &quot;tokens&quot;<br>
<br>
This would result in a syntax of...<br>
<br>
 =A0hash=3D&quot;md5:abc...xyz, sha-1:123...567, sha-512:xyz...abc&quot;<br=
>
<br>
This seem acceptable to everyone?<br>
<font color=3D"#888888"><br>
- James<br>
</font><div><div></div><div class=3D"h5"><br>
On Sat, May 15, 2010 at 11:46 PM, Sam Johnston &lt;<a href=3D"mailto:samj@s=
amj.net">samj@samj.net</a>&gt; wrote:<br>
&gt; James,<br>
&gt; In consideration of former (CRC) and future (AHS) hashing functions I =
think<br>
&gt; it&#39;s critical to support extensibility and multiple hashes. I like=
 that XML<br>
&gt; digsigs use anyURIs to identify hashes (e.g. &lt;DigestMethod<br>
&gt; Algorithm=3D&quot;<a href=3D"http://www.w3.org/2000/09/xmldsig#sha1" t=
arget=3D"_blank">http://www.w3.org/2000/09/xmldsig#sha1</a>&quot;&gt;), but=
 one could argue<br>
&gt; this unnecessarily complicates what should be a simple syntax.<br>
&gt; I was about to propose an IANA registry for hash functions but one alr=
eady<br>
&gt; exists (Hash Function Textual Names=A0as specified by RFC4572) so it w=
ould<br>
&gt; make sense to use it rather than inventing our own mechanism - even if=
 we<br>
&gt; have to update the registry rules to allow for algorithms specified by=
 URI<br>
&gt; rather than RFC.<br>
&gt; While Atom is an XML format and should arguably follow XML conventions=
,<br>
&gt; there is precedent for prefixing hashes with the name of the hashing<b=
r>
&gt; function using e.g. colons or curly braces. I think it&#39;s more impo=
rtant to<br>
&gt; keep the XML syntax simple and in any case the hash and hash function =
should<br>
&gt; be tightly bound as they are useless independently.<br>
&gt; All that considered, I think the best approach is to allow for a<br>
&gt; multi-valued &quot;hash&quot; attribute ala:<br>
&gt; &lt;link rel=3D&quot;alternate&quot; href=3D&quot;<a href=3D"http://ex=
ample.com/" target=3D"_blank">http://example.com/</a>&quot;<br>
&gt; hash=3D&quot;md5:6705f99eccedeac20e969bef954c5fb0<br>
&gt; sha-1:bc608e6d3d339d1a7afc406a7ea6a8f07358038b&quot; /&gt;<br>
&gt; and/or<br>
&gt; &lt;link rel=3D&quot;alternate&quot; href=3D&quot;<a href=3D"http://ex=
ample.com/thing.pdf" target=3D"_blank">http://example.com/thing.pdf</a>&quo=
t;<br>
&gt; hash=3D&quot;md5:6705f99eccedeac20e969bef954c5fb0&quot;<br>
&gt; hash=3D&quot;sha-1:bc608e6d3d339d1a7afc406a7ea6a8f07358038b&quot; /&gt=
;<br>
&gt; Sam<br>
&gt; Google<br>
&gt; On Sat, May 15, 2010 at 1:15 AM, James Snell &lt;<a href=3D"mailto:jas=
nell@gmail.com">jasnell@gmail.com</a>&gt; wrote:<br>
&gt;&gt;<br>
&gt;&gt; Good argument Bob... ok... stewing over this a bit more. I general=
ly<br>
&gt;&gt; dislike having to do additional parsing of attribute/element value=
s<br>
&gt;&gt; but there are very good reasons for keeping this as a single &quot=
;hash&quot;<br>
&gt;&gt; attribute and you make a compelling case.<br>
&gt;&gt;<br>
&gt;&gt; On Fri, May 14, 2010 at 1:26 PM, Bob Wyman &lt;<a href=3D"mailto:b=
ob@wyman.us">bob@wyman.us</a>&gt; wrote:<br>
&gt;&gt; &gt; James Snell=A0&lt;<a href=3D"mailto:jasnell@gmail.com">jasnel=
l@gmail.com</a>&gt;=A0wrote:<br>
&gt;&gt; &gt;&gt; &lt;link href=3D&quot;foo&quot; md5=3D&quot;abc...xyz&quo=
t;&gt;<br>
&gt;&gt; &gt;&gt; =A0&lt;media:hash algo=3D&quot;GOST&quot;&gt;123...456&lt=
;/media:hash&gt;<br>
&gt;&gt; &gt;&gt; &lt;/link&gt;<br>
&gt;&gt; &gt;<br>
&gt;&gt; &gt; The alternative approach, which would support both a variety<=
br>
&gt;&gt; &gt; and=A0multiplicity of hashes=A0would look like this:<br>
&gt;&gt; &gt; &lt;link href=3D&quot;foo&quot; hash=3D&quot;gost:123123..., =
md5:0928402948...,<br>
&gt;&gt; &gt; sha256:098078097...&quot;/&gt;<br>
&gt;&gt; &gt; This strikes me as &quot;simpler&quot; than the hybrid approa=
ch. Just a few of my<br>
&gt;&gt; &gt; concerns with the proposed &quot;hybrid&quot; approach follow=
:<br>
&gt;&gt; &gt;<br>
&gt;&gt; &gt; I like binding the algorithm and value together into a single=
 value<br>
&gt;&gt; &gt; since I<br>
&gt;&gt; &gt; know of no compelling case for processing one element in isol=
ation of<br>
&gt;&gt; &gt; the<br>
&gt;&gt; &gt; other. The hash value only makes sense if you know the algori=
thm and the<br>
&gt;&gt; &gt; algorithm is only useful when bound to a specific hash value.=
 Thus, it<br>
&gt;&gt; &gt; strikes me as simply introducing syntactic sugar to specify t=
he<br>
&gt;&gt; &gt; algorithm<br>
&gt;&gt; &gt; using a different XML component than the value.<br>
&gt;&gt; &gt; These values are likely to be stored in databases and otherwi=
se<br>
&gt;&gt; &gt; manipulated.<br>
&gt;&gt; &gt; In all cases, for the data to be meaningful, people will need=
 to keep<br>
&gt;&gt; &gt; the<br>
&gt;&gt; &gt; binding between algorithm and hash value. It is likely that s=
toring a<br>
&gt;&gt; &gt; single<br>
&gt;&gt; &gt; string value is going to be easier for folk than dealing with=
 a<br>
&gt;&gt; &gt; multi-part<br>
&gt;&gt; &gt; value. Also, consider the effect of parsers... It is likely t=
hat in<br>
&gt;&gt; &gt; order to<br>
&gt;&gt; &gt; transfer a value from an entry into a database field, what yo=
u&#39;ll need<br>
&gt;&gt; &gt; to do<br>
&gt;&gt; &gt; is extract both algorithm and hash value from the parse tree =
and then<br>
&gt;&gt; &gt; construct some string that combines them. This would be parti=
cularly<br>
&gt;&gt; &gt; useful<br>
&gt;&gt; &gt; if you want to use the hash value as a database key (a very r=
easonable<br>
&gt;&gt; &gt; thing<br>
&gt;&gt; &gt; to do...) You could build and store the string &quot;algo=3D&=
#39;GOST&#39;&gt;123...455&lt;&quot;<br>
&gt;&gt; &gt; or<br>
&gt;&gt; &gt; your database might support concatenated fields, or you could=
 build<br>
&gt;&gt; &gt; &quot;gost.123...456&quot;. I think I would go with the latte=
r.<br>
&gt;&gt; &gt; Defining distinct attributes for each hash algorithm pushes u=
nnecessary<br>
&gt;&gt; &gt; syntactical complexity to the global level and thus increases=
 the<br>
&gt;&gt; &gt; complexity<br>
&gt;&gt; &gt; not only of the specification but also of all applications no=
 matter<br>
&gt;&gt; &gt; which<br>
&gt;&gt; &gt; algorithms they understand or if they understand any at all. =
It also<br>
&gt;&gt; &gt; makes<br>
&gt;&gt; &gt; extending the list of supported algorithms &quot;expensive&qu=
ot; since such<br>
&gt;&gt; &gt; extensions<br>
&gt;&gt; &gt; require modification to the standard rather than just an regi=
stry<br>
&gt;&gt; &gt; entry.What<br>
&gt;&gt; &gt; benefit do we get from having these algorithm types defined a=
t the<br>
&gt;&gt; &gt; global<br>
&gt;&gt; &gt; syntax level?<br>
&gt;&gt; &gt; The hybrid approach looks very complicated to me. It means th=
at I&#39;ll<br>
&gt;&gt; &gt; have<br>
&gt;&gt; &gt; two very different places in which hash values might found an=
d two very<br>
&gt;&gt; &gt; different syntaxes for expressing them. The result is going t=
o be more<br>
&gt;&gt; &gt; complex code than would otherwise be the case. What value com=
es from<br>
&gt;&gt; &gt; using<br>
&gt;&gt; &gt; the hybrid approach?<br>
&gt;&gt; &gt; One argument for hybrid is that these elements exist already =
in other<br>
&gt;&gt; &gt; specs.<br>
&gt;&gt; &gt; I wonder if it isn&#39;t possible that those other specs migh=
t have<br>
&gt;&gt; &gt; approached<br>
&gt;&gt; &gt; the problem in a non-optimal fashion. Does it really make sen=
se to<br>
&gt;&gt; &gt; import<br>
&gt;&gt; &gt; syntax if there isn&#39;t a really good case that demonstrate=
s that doing so<br>
&gt;&gt; &gt; is<br>
&gt;&gt; &gt; the best approach?<br>
&gt;&gt; &gt; I am unaware of any hash algorithms that need anything other =
than the<br>
&gt;&gt; &gt; specification of the algorithm and the value in order to be u=
seful. If<br>
&gt;&gt; &gt; there<br>
&gt;&gt; &gt; were broadly used algorithms that had more complex meta-data<=
br>
&gt;&gt; &gt; requirements,<br>
&gt;&gt; &gt; it would be easier to understand the appeal of the hybrid app=
roach.<br>
&gt;&gt; &gt; I can&#39;t think of any reason why it is *useful* to separat=
e the algorithm<br>
&gt;&gt; &gt; from the hash value. Can someone enlighten me here? What comp=
utation,<br>
&gt;&gt; &gt; storage or communication task becomes easier if you have thes=
e two<br>
&gt;&gt; &gt; separated?<br>
&gt;&gt; &gt;<br>
&gt;&gt; &gt; bob wyman<br>
&gt;&gt; &gt; On Fri, May 14, 2010 at 3:06 PM, James Snell &lt;<a href=3D"m=
ailto:jasnell@gmail.com">jasnell@gmail.com</a>&gt; wrote:<br>
&gt;&gt; &gt;&gt;<br>
&gt;&gt; &gt;&gt; Ok, I&#39;ve been giving this some more thought and I thi=
nk a hybrid<br>
&gt;&gt; &gt;&gt; approach works very well. As has been pointed out a numbe=
r of times in<br>
&gt;&gt; &gt;&gt; this thread, there are existing elements in other namespa=
ces that<br>
&gt;&gt; &gt;&gt; provide a algorithm/hash pairing. I think that the Link E=
xtensions<br>
&gt;&gt; &gt;&gt; Draft can provide a attributes for the most basic hash al=
gorithms and<br>
&gt;&gt; &gt;&gt; applications that require hash algorithms that are not co=
vered can<br>
&gt;&gt; &gt;&gt; fall back to the extension elements.<br>
&gt;&gt; &gt;&gt;<br>
&gt;&gt; &gt;&gt; e.g.<br>
&gt;&gt; &gt;&gt;<br>
&gt;&gt; &gt;&gt; &lt;link href=3D&quot;foo&quot; md5=3D&quot;abc...xyz&quo=
t;&gt;<br>
&gt;&gt; &gt;&gt; =A0&lt;media:hash algo=3D&quot;GOST&quot;&gt;123...456&lt=
;/media:hash&gt;<br>
&gt;&gt; &gt;&gt; &lt;/link&gt;<br>
&gt;&gt; &gt;&gt;<br>
&gt;&gt; &gt;&gt; This would allow for the most common cases to be easily c=
overed while<br>
&gt;&gt; &gt;&gt; allowing for the full range of possible cases to be handl=
ed as well.<br>
&gt;&gt; &gt;&gt;<br>
&gt;&gt; &gt;&gt; - James<br>
&gt;&gt; &gt;&gt;<br>
&gt;&gt; &gt;&gt; On Wed, May 12, 2010 at 8:50 PM, Richard Salz &lt;<a href=
=3D"mailto:rsalz@us.ibm.com">rsalz@us.ibm.com</a>&gt; wrote:<br>
&gt;&gt; &gt;&gt; &gt;&gt; So the key question is: what are the main algori=
thms we need to<br>
&gt;&gt; &gt;&gt; &gt;&gt; provide attributes for?<br>
&gt;&gt; &gt;&gt; &gt;<br>
&gt;&gt; &gt;&gt; &gt; This is a hard question to answer -- especially for =
hash/digest<br>
&gt;&gt; &gt;&gt; &gt; algorithms<br>
&gt;&gt; &gt;&gt; &gt; which tend to fall more rapidly than vetted crypto a=
lgorithms.<br>
&gt;&gt; &gt;&gt; &gt;<br>
&gt;&gt; &gt;&gt; &gt; It&#39;s more verbose, but I strongly recommend usin=
g a pair of<br>
&gt;&gt; &gt;&gt; &gt; attributes<br>
&gt;&gt; &gt;&gt; &gt; to<br>
&gt;&gt; &gt;&gt; &gt; represent algorithm/value. Use the URI&#39;s defined=
 in the latest XML<br>
&gt;&gt; &gt;&gt; &gt; DSIG<br>
&gt;&gt; &gt;&gt; &gt; document, perhaps with the &quot;trick&quot; that re=
lative URI&#39;s ar a shorthand<br>
&gt;&gt; &gt;&gt; &gt; for<br>
&gt;&gt; &gt;&gt; &gt; the xmldsig namespace.<br>
&gt;&gt; &gt;&gt; &gt;<br>
&gt;&gt; &gt;&gt; &gt; =A0 =A0 =A0 =A0/r$<br>
&gt;&gt; &gt;&gt; &gt;<br>
&gt;&gt; &gt;&gt; &gt; --<br>
&gt;&gt; &gt;&gt; &gt; STSM, WebSphere Appliance Architect<br>
&gt;&gt; &gt;&gt; &gt; <a href=3D"https://www.ibm.com/developerworks/mydeve=
loperworks/blogs/soma/" target=3D"_blank">https://www.ibm.com/developerwork=
s/mydeveloperworks/blogs/soma/</a><br>
&gt;&gt; &gt;&gt; &gt;<br>
&gt;&gt; &gt;&gt; &gt;<br>
&gt;&gt; &gt;&gt;<br>
&gt;&gt; &gt;&gt;<br>
&gt;&gt; &gt;&gt;<br>
&gt;&gt; &gt;&gt; --<br>
&gt;&gt; &gt;&gt; - James Snell<br>
&gt;&gt; &gt;&gt; =A0<a href=3D"http://www.snellspace.com" target=3D"_blank=
">http://www.snellspace.com</a><br>
&gt;&gt; &gt;&gt; =A0<a href=3D"mailto:jasnell@gmail.com">jasnell@gmail.com=
</a><br>
&gt;&gt; &gt;&gt;<br>
&gt;&gt; &gt;<br>
&gt;&gt; &gt;<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt; --<br>
&gt;&gt; - James Snell<br>
&gt;&gt; =A0<a href=3D"http://www.snellspace.com" target=3D"_blank">http://=
www.snellspace.com</a><br>
&gt;&gt; =A0<a href=3D"mailto:jasnell@gmail.com">jasnell@gmail.com</a><br>
&gt;&gt;<br>
&gt;<br>
&gt;<br>
</div></div></blockquote></div><br></div>

--0016e68ee1e3df97c50487fe2238--


From owner-atom-syntax@mail.imc.org  Tue Jun  1 14:32:34 2010
Return-Path: <owner-atom-syntax@mail.imc.org>
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 8643F3A6A56 for <ietfarch-atompub-archive@core3.amsl.com>; Tue,  1 Jun 2010 14:32:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.679
X-Spam-Level: **
X-Spam-Status: No, score=2.679 tagged_above=-999 required=5 tests=[AWL=-0.297, BAYES_50=0.001, FM_FORGED_GMAIL=0.622, HELO_MISMATCH_COM=0.553, HTML_MESSAGE=0.001, J_CHICKENPOX_38=0.6, J_CHICKENPOX_44=0.6, J_CHICKENPOX_47=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 WJl7W5WqQ2Em for <ietfarch-atompub-archive@core3.amsl.com>; Tue,  1 Jun 2010 14:32:33 -0700 (PDT)
Received: from hoffman.proper.com (Hoffman.Proper.COM [207.182.41.81]) by core3.amsl.com (Postfix) with ESMTP id 38DFC3A6A63 for <atompub-archive@ietf.org>; Tue,  1 Jun 2010 14:32:33 -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 o51LRxxG067285 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 1 Jun 2010 14:27:59 -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 o51LRx0H067284; Tue, 1 Jun 2010 14:27:59 -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-gw0-f43.google.com (mail-gw0-f43.google.com [74.125.83.43]) by hoffman.proper.com (8.14.4/8.14.3) with ESMTP id o51LRve6067277 for <atom-syntax@imc.org>; Tue, 1 Jun 2010 14:27:58 -0700 (MST) (envelope-from bobwyman@gmail.com)
Received: by gwj17 with SMTP id 17so43160gwj.16 for <atom-syntax@imc.org>; Tue, 01 Jun 2010 14:27:57 -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:date :x-google-sender-auth:message-id:subject:from:to:content-type; bh=WUUqjvCqfR+3pFQd3cUAy4Kp1VLQ4Rbm5bDjLqGA3Pk=; b=Aou8/QnIjs0jcpU8Q9+X4G/vOPpjxOR54tnoQItCO5/ZR8j0I4W1mtHyhs5RATkwL3 9rbGC3HvQhGCJorwp3aX/0+8u2ag6Rq0L3BL7zLxjnzMsTtlCcWjbUSgXKDMS+bTZ8yQ weUurxCFE7fROyxNjZMsQornxqH/IYlT8j7jI=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:date:x-google-sender-auth:message-id:subject :from:to:content-type; b=AKlx8SMhM70CxRSjZLiU3JuJCG+INUvFItQXzjnOlpfpCXeJITekb1e0riV5gjOcGW aL94cNoJxmwCN5BtySTjlVD9Dx3v2erNclXeSXrX8+24pmcWGh3JNk+tTI2iauKu94XE v/x8tx4EEbgobgsqMiQuxxbZFe0IaJtvVKDnM=
MIME-Version: 1.0
Received: by 10.100.246.23 with SMTP id t23mr7545927anh.167.1275427677239;  Tue, 01 Jun 2010 14:27:57 -0700 (PDT)
Received: by 10.100.92.4 with HTTP; Tue, 1 Jun 2010 14:27:57 -0700 (PDT)
Date: Tue, 1 Jun 2010 17:27:57 -0400
X-Google-Sender-Auth: CXpo0T3kd6c2T2XrVmm3zqTfvT4
Message-ID: <AANLkTimANu7KXubPQHACAmVQI7PGlv2nB8wSPjmWdoLZ@mail.gmail.com>
Subject: eTag, modified and accessed attributes in Link Extensions Draft
From: Bob Wyman <bob@wyman.us>
To: Atom-Syntax <atom-syntax@imc.org>, James M Snell <jasnell@gmail.com>
Content-Type: multipart/alternative; boundary=00504502ec9aa37af30487fea59d
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>

--00504502ec9aa37af30487fea59d
Content-Type: text/plain; charset=ISO-8859-1

The draft, as currently written, seems to be a bit ambiguous about the
source eTags and the meaning of "modified".

My assumption is that an eTag, when used as a link attribute, should not be
something generated by the link element creator but should be a mere passing
on of an eTag generated by the server that hosts the resource that is linked
to. Thus, eTag should be seen as something which, like "hash", simply
records and passes on information related to the state of the resource at
some specific point in time when it was previously accessed. In this case,
you could never have a eTag attribute on a link if the linked-to server did
not support eTags. If this assumption is correct, I think it might clarify
things if it were stated in the draft.

It seems that "modified" might be slightly different. In some cases, it
seems reasonable that modified would be the modified or updated date
reported on accessing a web resource. On the other hand, it seems like it
would also be reasonable, in cases where the server does not report modified
dates yet the author of the link has knowledge of the modification history,
that the link author might include a modified date even though it is NOT
reported by the server. However, this means that the link author is not
simply recording and passing on data offered by the server. This means that
the meaning of "modified" would be somewhat ambiguous. Am I reading this
right?

I continue to see evidence that formal systems for "Internet citation" or
bibliography typically require that a "last accessed" date be included in
citations. Thus, I'd like to suggest a new section (as discussed in earlier
messages):

X.  The 'accessed' attribute

   The 'accessed' Attribute specifies a date and time when the
   resource identified by the atom:link or atom:content element was
   accessed. The 'accessed' attribute SHOULD record the most recent date
   and time at which the resource was accessed. The value MUST conform
   to the "date-time" production defined by [RFC3339].  An uppercase
   "T" character MUST be used to separate date and time, and an
   uppercase "Z" character MUST be present in the absence of a numeric
   time zone offset.  The 'accessed' attribute MAY appear as a child
   of the atom:link and atom:content elements.

     accessed = attribute accessed { xsd:dateTime }

   An example accessed attribute for an enclosed MP3 file:

     <atom:link rel="enclosure"
       href="http://example.org/media/myfile.mp3"
       accessed="2010-12-12T12:12:12Z" />

bob wyman

--00504502ec9aa37af30487fea59d
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

The draft, as currently written, seems to be a bit ambiguous about the sour=
ce eTags and the meaning of &quot;modified&quot;.<div><br></div><div>My ass=
umption is that an eTag, when used as a link attribute, should not be somet=
hing generated by the link element creator but should be a mere passing on =
of an eTag generated by the server that hosts the resource that is linked t=
o. Thus, eTag should be seen as something which, like &quot;hash&quot;, sim=
ply records and passes on information related to the state of the resource =
at some specific point in time when it was previously accessed. In this cas=
e, you could never have a eTag attribute on a link if the linked-to server =
did not support eTags. If this assumption is correct, I think it might clar=
ify things if it were stated in the draft.</div>
<div><br></div><div>It seems that &quot;modified&quot; might be slightly di=
fferent. In some cases, it seems reasonable that modified would be the modi=
fied or updated date reported on accessing a web resource. On the other han=
d, it seems like it would also be reasonable, in cases where the server doe=
s not report modified dates yet the author of the link has knowledge of the=
 modification history, that the link author might include a modified date e=
ven though it is NOT reported by the server. However, this means that the l=
ink author is not simply recording and passing on data offered by the serve=
r. This means that the meaning of &quot;modified&quot; would be somewhat am=
biguous. Am I reading this right?</div>
<div><br></div><div>I continue to see evidence that formal systems for &quo=
t;Internet citation&quot; or bibliography typically require that a &quot;la=
st accessed&quot; date be included in citations. Thus, I&#39;d like to sugg=
est a new section (as discussed in earlier messages):</div>
<div><br></div><div><span class=3D"Apple-style-span" style=3D"font-family: =
&#39;Times New Roman&#39;; font-size: medium; "><pre style=3D"word-wrap: br=
eak-word; white-space: pre-wrap; ">X.  The &#39;accessed&#39; attribute

   The &#39;accessed&#39; Attribute specifies a date and time when the
   resource identified by the atom:link or atom:content element was=20
   accessed.=A0The &#39;accessed&#39; attribute SHOULD record the most rece=
nt date
   and time at which the resource was accessed. The value MUST conform
   to the &quot;date-time&quot; production defined by [RFC3339].  An upperc=
ase=20
   &quot;T&quot; character MUST be used to separate date and time, and an
   uppercase &quot;Z&quot; character MUST be present in the absence of a nu=
meric
   time zone offset.  The &#39;accessed&#39; attribute MAY appear as a chil=
d
   of the atom:link and atom:content elements.</pre><pre style=3D"word-wrap=
: break-word; white-space: pre-wrap; ">     accessed =3D attribute accessed=
 { xsd:dateTime }

   An example accessed attribute for an enclosed MP3 file:

     &lt;atom:link rel=3D&quot;enclosure&quot;
       href=3D&quot;<a href=3D"http://example.org/media/myfile.mp3">http://=
example.org/media/myfile.mp3</a>&quot;
       accessed=3D&quot;2010-12-12T12:12:12Z&quot; /&gt;
</pre><div><span class=3D"Apple-style-span" style=3D"font-family: arial; fo=
nt-size: small; ">bob wyman</span></div></span></div><div><br></div>

--00504502ec9aa37af30487fea59d--


From owner-atom-syntax@mail.imc.org  Tue Jun  1 16:45:20 2010
Return-Path: <owner-atom-syntax@mail.imc.org>
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 80BF83A68D7 for <ietfarch-atompub-archive@core3.amsl.com>; Tue,  1 Jun 2010 16:45:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.154
X-Spam-Level: **
X-Spam-Status: No, score=2.154 tagged_above=-999 required=5 tests=[AWL=-0.200, BAYES_50=0.001, HELO_MISMATCH_COM=0.553, J_CHICKENPOX_38=0.6, J_CHICKENPOX_44=0.6, J_CHICKENPOX_47=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 U2leIC+s9SiN for <ietfarch-atompub-archive@core3.amsl.com>; Tue,  1 Jun 2010 16:45:19 -0700 (PDT)
Received: from hoffman.proper.com (Hoffman.Proper.COM [207.182.41.81]) by core3.amsl.com (Postfix) with ESMTP id 8981A3A6782 for <atompub-archive@ietf.org>; Tue,  1 Jun 2010 16:45: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 o51Ne2a5073235 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 1 Jun 2010 16:40:02 -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 o51Ne2xR073234; Tue, 1 Jun 2010 16:40:02 -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-yx0-f171.google.com (mail-yx0-f171.google.com [209.85.213.171]) by hoffman.proper.com (8.14.4/8.14.3) with ESMTP id o51Ne1AB073225 for <atom-syntax@imc.org>; Tue, 1 Jun 2010 16:40:01 -0700 (MST) (envelope-from jasnell@gmail.com)
Received: by yxn22 with SMTP id 22so224654yxn.16 for <atom-syntax@imc.org>; Tue, 01 Jun 2010 16:40:00 -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=3wqwQQ0cCVNE2QEEGmT63Gzp5Ip1efYY86VweRL+woI=; b=lbjDtEKE++t8qP1tCME4s2MYN3roS3FHgE6rNyRctMBFPgAPjhGstqcoXJ263uqmcL DxHlgWckzgkf0j5MKjOw2mveayoy0+gFaxIGc5VlXIVJxOss/XBq0AreHd9d2VOPLHUx ay+urtIU1reUeDsISzGxBJ9F4pwmyBtdc/9Iw=
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=jMGMsEt11lQpPtJwVn25/dxjygbfG8ZiOXbZIA3gCsl8PYJS7HxHbjbBEPAyWEil5r 5S0zOcflgeyA+EfA5FPlkPS2YRsKuvJLPbhAu0ePeTU4qumbpTdp3iW7g137V5VRb5Dm AF4481TBI6xPHqkDXZEQSShBA4Yl9+O7JYSck=
MIME-Version: 1.0
Received: by 10.229.249.145 with SMTP id mk17mr1205481qcb.163.1275435600406;  Tue, 01 Jun 2010 16:40:00 -0700 (PDT)
Received: by 10.229.81.78 with HTTP; Tue, 1 Jun 2010 16:40:00 -0700 (PDT)
In-Reply-To: <AANLkTimANu7KXubPQHACAmVQI7PGlv2nB8wSPjmWdoLZ@mail.gmail.com>
References: <AANLkTimANu7KXubPQHACAmVQI7PGlv2nB8wSPjmWdoLZ@mail.gmail.com>
Date: Tue, 1 Jun 2010 16:40:00 -0700
Message-ID: <AANLkTik7sl_e0x6jTFy-R8ClPRB_qaICAUFXmSF3V5Yl@mail.gmail.com>
Subject: Re: eTag, modified and accessed attributes in Link Extensions Draft
From: James Snell <jasnell@gmail.com>
To: Bob Wyman <bob@wyman.us>
Cc: Atom-Syntax <atom-syntax@imc.org>
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 o51Ne1AB073230
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>

On Tue, Jun 1, 2010 at 2:27 PM, Bob Wyman <bob@wyman.us> wrote:
> The draft, as currently written, seems to be a bit ambiguous about the
> source eTags and the meaning of "modified".
> My assumption is that an eTag, when used as a link attribute, should not be
> something generated by the link element creator but should be a mere passing
> on of an eTag generated by the server that hosts the resource that is linked
> to. Thus, eTag should be seen as something which, like "hash", simply
> records and passes on information related to the state of the resource at
> some specific point in time when it was previously accessed. In this case,
> you could never have a eTag attribute on a link if the linked-to server did
> not support eTags. If this assumption is correct, I think it might clarify
> things if it were stated in the draft.

Agreed.

> It seems that "modified" might be slightly different. In some cases, it
> seems reasonable that modified would be the modified or updated date
> reported on accessing a web resource. On the other hand, it seems like it
> would also be reasonable, in cases where the server does not report modified
> dates yet the author of the link has knowledge of the modification history,
> that the link author might include a modified date even though it is NOT
> reported by the server. However, this means that the link author is not
> simply recording and passing on data offered by the server. This means that
> the meaning of "modified" would be somewhat ambiguous. Am I reading this
> right?

Yes.. I think we need to limit "modified" to the date reported by the
server. If no date is specified, the modified attribute should not be
used.  The feed producer should not make up a value on it's own for
that attribute. The etag and modified attributes should provide enough
valuable information to perform a reasonable conditional get on the
linked resource. If the server doesn't provide that information in the
first place, then it's not of much value.

> I continue to see evidence that formal systems for "Internet citation" or
> bibliography typically require that a "last accessed" date be included in
> citations. Thus, I'd like to suggest a new section (as discussed in earlier
> messages):
>
> X.  The 'accessed' attribute
>
>    The 'accessed' Attribute specifies a date and time when the
>    resource identified by the atom:link or atom:content element was
>    accessed. The 'accessed' attribute SHOULD record the most recent date
>    and time at which the resource was accessed. The value MUST conform
>    to the "date-time" production defined by [RFC3339].  An uppercase
>    "T" character MUST be used to separate date and time, and an
>    uppercase "Z" character MUST be present in the absence of a numeric
>    time zone offset.  The 'accessed' attribute MAY appear as a child
>    of the atom:link and atom:content elements.
>
>      accessed = attribute accessed { xsd:dateTime }
>
>    An example accessed attribute for an enclosed MP3 file:
>
>      <atom:link rel="enclosure"
>        href="http://example.org/media/myfile.mp3"
>        accessed="2010-12-12T12:12:12Z" />
>
> bob wyman
>

+1. I've been looking at this also. We are going to need to include
some semantics for when the accessed attribute is omitted. This
attribute essentially needs to establish the point in time at which
the modified, etag and hash were considered to be valid... if it is
omitted, then the atom:updated has to be assumed to be the fallback.

- James


From owner-atom-syntax@mail.imc.org  Mon Jun  7 10:22:17 2010
Return-Path: <owner-atom-syntax@mail.imc.org>
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 6C06E3A6E48 for <ietfarch-atompub-archive@core3.amsl.com>; Mon,  7 Jun 2010 10:22:17 -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 b2aG4KM7yBv7 for <ietfarch-atompub-archive@core3.amsl.com>; Mon,  7 Jun 2010 10:22:16 -0700 (PDT)
Received: from hoffman.proper.com (Hoffman.Proper.COM [207.182.41.81]) by core3.amsl.com (Postfix) with ESMTP id B86CE28C69B for <atompub-archive@ietf.org>; Mon,  7 Jun 2010 08:55:57 -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 o57FMP0q000924 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 7 Jun 2010 08:22:25 -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 o57FMPAP000923; Mon, 7 Jun 2010 08:22:25 -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-gw0-f43.google.com (mail-gw0-f43.google.com [74.125.83.43]) by hoffman.proper.com (8.14.4/8.14.3) with ESMTP id o57FMO0T000916 for <atom-syntax@imc.org>; Mon, 7 Jun 2010 08:22:24 -0700 (MST) (envelope-from bobwyman@gmail.com)
Received: by gwj17 with SMTP id 17so2713797gwj.16 for <atom-syntax@imc.org>; Mon, 07 Jun 2010 08:22: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:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=4+E//w9wmvS/8fIB/K3a6sZ6sy4/+yY3M7fjfUSUTUQ=; b=SrBc3zqfHptoEcV1bXsXkwXVCH5HVyWjfi9TCpZnJKkabiGyC/CxloQnTUnjEOanpm 0jVhGfC+JcCNt8fViCkX1MYg0ay8KVRGiP72lGX6IZ+3q5hWBqjTu7Opauszms2sewyY P2s1gCXCmKl7f5RPn/fFZCMq1rEkyRAKxhtiI=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:date:x-google-sender-auth:message-id:subject :from:to:cc:content-type; b=Vyss7FI++syospFVyPOgOD6SeQS/FCtPjXwjpW0u/Z2WCxm0I8wdA5feCcsnvjBXtb w4wsEmBgw4qtg0TE+HoKvRGdpcBEoEZPdaLK/hsez0bflZIUE/A1yDRKZNJmNoe9uQuT vL2erFPWFBkbqlYBuk52krtJcTuQzf09Y+KtY=
MIME-Version: 1.0
Received: by 10.101.99.5 with SMTP id b5mr15752460anm.257.1275924143768; Mon,  07 Jun 2010 08:22:23 -0700 (PDT)
Received: by 10.100.119.16 with HTTP; Mon, 7 Jun 2010 08:22:23 -0700 (PDT)
Date: Mon, 7 Jun 2010 11:22:23 -0400
X-Google-Sender-Auth: k_0Ai75boMKAT-mK1Y14gN1zG6U
Message-ID: <AANLkTilhzUgtPB1W451rYwBWA15LgUlP6YH_-IiuCoEe@mail.gmail.com>
Subject: Link Extensions and IANA, W3C?
From: Bob Wyman <bob@wyman.us>
To: James M Snell <jasnell@gmail.com>
Cc: Atom-Syntax <atom-syntax@imc.org>
Content-Type: multipart/alternative; boundary=001636c930a25983700488723d0e
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>

--001636c930a25983700488723d0e
Content-Type: text/plain; charset=ISO-8859-1

The current Link Extensions[1] draft says "No IANA actions are required..."
however, IANA maintains a registry of link-relations[2] that contains many
of the link relations defined previously for use with Atom. Why wouldn't
IANA be asked to include these new link relations in the existing registry?

Also, there is a Wiki for HTML5 Link Relations[3] -- some of which come from
Atom. Is there any reason it wouldn't be appropriate to include these new
link relations in the HTML5 list?

bob wyman

[1] http://www.ietf.org/id/draft-snell-atompub-link-extensions-05.txt
[2] http://www.iana.org/assignments/link-relations/link-relations.xhtml
[3] http://wiki.whatwg.org/wiki/RelExtensions

--001636c930a25983700488723d0e
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<meta http-equiv=3D"content-type" content=3D"text/html; charset=3Dutf-8"><d=
iv>The current Link Extensions[1] draft says &quot;<span class=3D"Apple-sty=
le-span" style=3D"font-family: monospace; font-size: medium; white-space: p=
re-wrap; ">No IANA actions are required...</span>&quot; however, IANA maint=
ains a registry of link-relations[2] that contains many of the link relatio=
ns defined previously for use with Atom. Why wouldn&#39;t IANA be asked to =
include these new link relations in the existing registry?</div>
<div><br></div><div>Also, there is a Wiki for HTML5 Link Relations[3] -- so=
me of which come from Atom. Is there any reason it wouldn&#39;t be appropri=
ate to include these new link relations in the HTML5 list?</div><meta http-=
equiv=3D"content-type" content=3D"text/html; charset=3Dutf-8"><div>
<br></div><div>bob wyman</div><div><br></div><div>[1]=A0<a href=3D"http://w=
ww.ietf.org/id/draft-snell-atompub-link-extensions-05.txt">http://www.ietf.=
org/id/draft-snell-atompub-link-extensions-05.txt</a></div><meta http-equiv=
=3D"content-type" content=3D"text/html; charset=3Dutf-8"><meta http-equiv=
=3D"content-type" content=3D"text/html; charset=3Dutf-8">[2]=A0<a href=3D"h=
ttp://www.iana.org/assignments/link-relations/link-relations.xhtml">http://=
www.iana.org/assignments/link-relations/link-relations.xhtml</a><div>
[3]=A0<a href=3D"http://wiki.whatwg.org/wiki/RelExtensions">http://wiki.wha=
twg.org/wiki/RelExtensions</a></div><meta http-equiv=3D"content-type" conte=
nt=3D"text/html; charset=3Dutf-8"><div><br></div><meta http-equiv=3D"conten=
t-type" content=3D"text/html; charset=3Dutf-8">

--001636c930a25983700488723d0e--


From owner-atom-syntax@mail.imc.org  Mon Jun  7 10:46:02 2010
Return-Path: <owner-atom-syntax@mail.imc.org>
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 5DA0C3A687C for <ietfarch-atompub-archive@core3.amsl.com>; Mon,  7 Jun 2010 10:46:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.558
X-Spam-Level: 
X-Spam-Status: No, score=-0.558 tagged_above=-999 required=5 tests=[AWL=-1.112, BAYES_50=0.001, 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 4Qe4PL+IKMnz for <ietfarch-atompub-archive@core3.amsl.com>; Mon,  7 Jun 2010 10:46:01 -0700 (PDT)
Received: from hoffman.proper.com (Hoffman.Proper.COM [207.182.41.81]) by core3.amsl.com (Postfix) with ESMTP id B1E1D3A6CE9 for <atompub-archive@ietf.org>; Mon,  7 Jun 2010 10:14:30 -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 o57H7XWq009289 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 7 Jun 2010 10:07: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 o57H7XLA009288; Mon, 7 Jun 2010 10:07: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 stpeter.im (stpeter.im [207.210.219.233]) by hoffman.proper.com (8.14.4/8.14.3) with ESMTP id o57H7Xni009283 for <atom-syntax@imc.org>; Mon, 7 Jun 2010 10:07:33 -0700 (MST) (envelope-from stpeter@stpeter.im)
Received: from dhcp-64-101-72-121.cisco.com (dhcp-64-101-72-121.cisco.com [64.101.72.121]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id EA01040E44; Mon,  7 Jun 2010 11:07:31 -0600 (MDT)
Message-ID: <4C0D2753.9070102@stpeter.im>
Date: Mon, 07 Jun 2010 11:07:31 -0600
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.1.9) Gecko/20100317 Thunderbird/3.0.4
MIME-Version: 1.0
To: Bob Wyman <bob@wyman.us>
CC: James M Snell <jasnell@gmail.com>, Atom-Syntax <atom-syntax@imc.org>
Subject: Re: Link Extensions and IANA, W3C?
References: <AANLkTilhzUgtPB1W451rYwBWA15LgUlP6YH_-IiuCoEe@mail.gmail.com>
In-Reply-To: <AANLkTilhzUgtPB1W451rYwBWA15LgUlP6YH_-IiuCoEe@mail.gmail.com>
X-Enigmail-Version: 1.0.1
OpenPGP: url=http://www.saint-andre.com/me/stpeter.asc
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha1; boundary="------------ms040908020809070205030904"
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>

This is a cryptographically signed message in MIME format.

--------------ms040908020809070205030904
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On 6/7/10 9:22 AM, Bob Wyman wrote:
> The current Link Extensions[1] draft says "No IANA actions are
> required..." however, IANA maintains a registry of link-relations[2]
> that contains many of the link relations defined previously for use wit=
h
> Atom. Why wouldn't IANA be asked to include these new link relations in=

> the existing registry?
>=20
> Also, there is a Wiki for HTML5 Link Relations[3] -- some of which come=

> from Atom. Is there any reason it wouldn't be appropriate to include
> these new link relations in the HTML5 list?
>=20
> bob wyman
>=20
> [1] http://www.ietf.org/id/draft-snell-atompub-link-extensions-05.txt
> [2] http://www.iana.org/assignments/link-relations/link-relations.xhtml=

> [3] http://wiki.whatwg.org/wiki/RelExtensions

My understanding is that the new IANA registry is intended to be the
canonical location for this information, as specified by
https://datatracker.ietf.org/doc/draft-nottingham-http-link-header/
(approved for publication as an RFC).

Peter

--=20
Peter Saint-Andre
https://stpeter.im/




--------------ms040908020809070205030904
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIWnDCC
B1cwggY/oAMCAQICAVUwDQYJKoZIhvcNAQEFBQAwgYwxCzAJBgNVBAYTAklMMRYwFAYDVQQK
Ew1TdGFydENvbSBMdGQuMSswKQYDVQQLEyJTZWN1cmUgRGlnaXRhbCBDZXJ0aWZpY2F0ZSBT
aWduaW5nMTgwNgYDVQQDEy9TdGFydENvbSBDbGFzcyAzIFByaW1hcnkgSW50ZXJtZWRpYXRl
IENsaWVudCBDQTAeFw0wOTA3MDYwMDAwMDFaFw0xMDA3MDYyMzU5NTlaMIHCMQswCQYDVQQG
EwJVUzERMA8GA1UECBMIQ29sb3JhZG8xDzANBgNVBAcTBkRlbnZlcjEiMCAGA1UEChMZWE1Q
UCBTdGFuZGFyZHMgRm91bmRhdGlvbjEsMCoGA1UECxMjU3RhcnRDb20gVHJ1c3RlZCBDZXJ0
aWZpY2F0ZSBNZW1iZXIxGjAYBgNVBAMTEVBldGVyIFNhaW50LUFuZHJlMSEwHwYJKoZIhvcN
AQkBFhJzdHBldGVyQHN0cGV0ZXIuaW0wggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIB
AQCas7Mrnh02GakN8sft+HJpU4MwBxEgrGDZ2ZzUxDDt2sEhM+9Q74h955MtgMhK3TeBf6Hs
hDh/8Z9G//k2qNA0M2S5rejTqrmW0Jabca/L7BUZ0GhnU2N/2zeciFUmuZ4A2l1T5IMX2ZVP
XnNIaefBtbImJAbDz3T0vxkzTtcqgW3wL83PMDiqiuM+e1k+VPvOW4f5ZSGkPIhYCDpWqNE5
wZvjrLNMc8jZOPs9DrsYuIVwU72Vhy1tkEh+w6YpYHrdEUAe+eKe6TuxqZ60e9z3O36uiV//
Ms274iD6PbA/IGazJgaAdg6tvPehwTYGJAGmv3PsJKkLGjgoh+RrrM1LAgMBAAGjggOKMIID
hjAJBgNVHRMEAjAAMAsGA1UdDwQEAwIEsDAdBgNVHSUEFjAUBggrBgEFBQcDAgYIKwYBBQUH
AwQwHQYDVR0OBBYEFOyws3XWgIY9FP1POVqjdZP9Lu38MB0GA1UdEQQWMBSBEnN0cGV0ZXJA
c3RwZXRlci5pbTCBqAYDVR0jBIGgMIGdgBR7iZySlyShhEcCy3T8LvSs3DLl86GBgaR/MH0x
CzAJBgNVBAYTAklMMRYwFAYDVQQKEw1TdGFydENvbSBMdGQuMSswKQYDVQQLEyJTZWN1cmUg
RGlnaXRhbCBDZXJ0aWZpY2F0ZSBTaWduaW5nMSkwJwYDVQQDEyBTdGFydENvbSBDZXJ0aWZp
Y2F0aW9uIEF1dGhvcml0eYIBDzCCAUcGA1UdIASCAT4wggE6MIIBNgYLKwYBBAGBtTcBAgAw
ggElMC4GCCsGAQUFBwIBFiJodHRwOi8vd3d3LnN0YXJ0c3NsLmNvbS9wb2xpY3kucGRmMDQG
CCsGAQUFBwIBFihodHRwOi8vd3d3LnN0YXJ0c3NsLmNvbS9pbnRlcm1lZGlhdGUucGRmMIG8
BggrBgEFBQcCAjCBrzAUFg1TdGFydENvbSBMdGQuMAMCAQEagZZMaW1pdGVkIExpYWJpbGl0
eSwgcmVhZCB0aGUgc2VjdGlvbiAqTGVnYWwgTGltaXRhdGlvbnMqIG9mIHRoZSBTdGFydENv
bSBDZXJ0aWZpY2F0aW9uIEF1dGhvcml0eSBQb2xpY3kgYXZhaWxhYmxlIGF0IGh0dHA6Ly93
d3cuc3RhcnRzc2wuY29tL3BvbGljeS5wZGYwYwYDVR0fBFwwWjAroCmgJ4YlaHR0cDovL3d3
dy5zdGFydHNzbC5jb20vY3J0dTMtY3JsLmNybDAroCmgJ4YlaHR0cDovL2NybC5zdGFydHNz
bC5jb20vY3J0dTMtY3JsLmNybDCBjgYIKwYBBQUHAQEEgYEwfzA5BggrBgEFBQcwAYYtaHR0
cDovL29jc3Auc3RhcnRzc2wuY29tL3N1Yi9jbGFzczMvY2xpZW50L2NhMEIGCCsGAQUFBzAC
hjZodHRwOi8vd3d3LnN0YXJ0c3NsLmNvbS9jZXJ0cy9zdWIuY2xhc3MzLmNsaWVudC5jYS5j
cnQwIwYDVR0SBBwwGoYYaHR0cDovL3d3dy5zdGFydHNzbC5jb20vMA0GCSqGSIb3DQEBBQUA
A4IBAQBgv4xFXZqDKSOtnPOVbqOh1brj7oxRaVYk7N0MJG7x9Y/wkO3iwRwizVLcC1bA+D/R
gyFilXx6IQWE63Ge2tu+Y4w5QoHYwuUFQuBZuxvZpOa3ykdgPlBQaBM8m+Ien0skwNggaizA
X9Pc/sMLpP3jkO1iSF4agy4r5Ed+4G10mP5X0zO3gQwq9Uj4F9tX+58kU+fM1P8Sh+BYR4r/
kSbKE3tWcMaKblWPGwX0nYD26Je7Qb+uX/J5lCgozBrHXQWq8N98iklASf2pv+32Oi1dEjmM
UgAm/J2+YmxaI02+c+H6QH8+F3RUjCiRg9XqUNjcrNrnTFnm/iMMZADktsXPMIIHVzCCBj+g
AwIBAgIBVTANBgkqhkiG9w0BAQUFADCBjDELMAkGA1UEBhMCSUwxFjAUBgNVBAoTDVN0YXJ0
Q29tIEx0ZC4xKzApBgNVBAsTIlNlY3VyZSBEaWdpdGFsIENlcnRpZmljYXRlIFNpZ25pbmcx
ODA2BgNVBAMTL1N0YXJ0Q29tIENsYXNzIDMgUHJpbWFyeSBJbnRlcm1lZGlhdGUgQ2xpZW50
IENBMB4XDTA5MDcwNjAwMDAwMVoXDTEwMDcwNjIzNTk1OVowgcIxCzAJBgNVBAYTAlVTMREw
DwYDVQQIEwhDb2xvcmFkbzEPMA0GA1UEBxMGRGVudmVyMSIwIAYDVQQKExlYTVBQIFN0YW5k
YXJkcyBGb3VuZGF0aW9uMSwwKgYDVQQLEyNTdGFydENvbSBUcnVzdGVkIENlcnRpZmljYXRl
IE1lbWJlcjEaMBgGA1UEAxMRUGV0ZXIgU2FpbnQtQW5kcmUxITAfBgkqhkiG9w0BCQEWEnN0
cGV0ZXJAc3RwZXRlci5pbTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAJqzsyue
HTYZqQ3yx+34cmlTgzAHESCsYNnZnNTEMO3awSEz71DviH3nky2AyErdN4F/oeyEOH/xn0b/
+Tao0DQzZLmt6NOquZbQlptxr8vsFRnQaGdTY3/bN5yIVSa5ngDaXVPkgxfZlU9ec0hp58G1
siYkBsPPdPS/GTNO1yqBbfAvzc8wOKqK4z57WT5U+85bh/llIaQ8iFgIOlao0TnBm+Oss0xz
yNk4+z0Ouxi4hXBTvZWHLW2QSH7Dpilget0RQB754p7pO7GpnrR73Pc7fq6JX/8yzbviIPo9
sD8gZrMmBoB2Dq2896HBNgYkAaa/c+wkqQsaOCiH5GuszUsCAwEAAaOCA4owggOGMAkGA1Ud
EwQCMAAwCwYDVR0PBAQDAgSwMB0GA1UdJQQWMBQGCCsGAQUFBwMCBggrBgEFBQcDBDAdBgNV
HQ4EFgQU7LCzddaAhj0U/U85WqN1k/0u7fwwHQYDVR0RBBYwFIESc3RwZXRlckBzdHBldGVy
LmltMIGoBgNVHSMEgaAwgZ2AFHuJnJKXJKGERwLLdPwu9KzcMuXzoYGBpH8wfTELMAkGA1UE
BhMCSUwxFjAUBgNVBAoTDVN0YXJ0Q29tIEx0ZC4xKzApBgNVBAsTIlNlY3VyZSBEaWdpdGFs
IENlcnRpZmljYXRlIFNpZ25pbmcxKTAnBgNVBAMTIFN0YXJ0Q29tIENlcnRpZmljYXRpb24g
QXV0aG9yaXR5ggEPMIIBRwYDVR0gBIIBPjCCATowggE2BgsrBgEEAYG1NwECADCCASUwLgYI
KwYBBQUHAgEWImh0dHA6Ly93d3cuc3RhcnRzc2wuY29tL3BvbGljeS5wZGYwNAYIKwYBBQUH
AgEWKGh0dHA6Ly93d3cuc3RhcnRzc2wuY29tL2ludGVybWVkaWF0ZS5wZGYwgbwGCCsGAQUF
BwICMIGvMBQWDVN0YXJ0Q29tIEx0ZC4wAwIBARqBlkxpbWl0ZWQgTGlhYmlsaXR5LCByZWFk
IHRoZSBzZWN0aW9uICpMZWdhbCBMaW1pdGF0aW9ucyogb2YgdGhlIFN0YXJ0Q29tIENlcnRp
ZmljYXRpb24gQXV0aG9yaXR5IFBvbGljeSBhdmFpbGFibGUgYXQgaHR0cDovL3d3dy5zdGFy
dHNzbC5jb20vcG9saWN5LnBkZjBjBgNVHR8EXDBaMCugKaAnhiVodHRwOi8vd3d3LnN0YXJ0
c3NsLmNvbS9jcnR1My1jcmwuY3JsMCugKaAnhiVodHRwOi8vY3JsLnN0YXJ0c3NsLmNvbS9j
cnR1My1jcmwuY3JsMIGOBggrBgEFBQcBAQSBgTB/MDkGCCsGAQUFBzABhi1odHRwOi8vb2Nz
cC5zdGFydHNzbC5jb20vc3ViL2NsYXNzMy9jbGllbnQvY2EwQgYIKwYBBQUHMAKGNmh0dHA6
Ly93d3cuc3RhcnRzc2wuY29tL2NlcnRzL3N1Yi5jbGFzczMuY2xpZW50LmNhLmNydDAjBgNV
HRIEHDAahhhodHRwOi8vd3d3LnN0YXJ0c3NsLmNvbS8wDQYJKoZIhvcNAQEFBQADggEBAGC/
jEVdmoMpI62c85Vuo6HVuuPujFFpViTs3QwkbvH1j/CQ7eLBHCLNUtwLVsD4P9GDIWKVfHoh
BYTrcZ7a275jjDlCgdjC5QVC4Fm7G9mk5rfKR2A+UFBoEzyb4h6fSyTA2CBqLMBf09z+wwuk
/eOQ7WJIXhqDLivkR37gbXSY/lfTM7eBDCr1SPgX21f7nyRT58zU/xKH4FhHiv+RJsoTe1Zw
xopuVY8bBfSdgPbol7tBv65f8nmUKCjMGsddBarw33yKSUBJ/am/7fY6LV0SOYxSACb8nb5i
bFojTb5z4fpAfz4XdFSMKJGD1epQ2Nys2udMWeb+IwxkAOS2xc8wggfiMIIFyqADAgECAgEP
MA0GCSqGSIb3DQEBBQUAMH0xCzAJBgNVBAYTAklMMRYwFAYDVQQKEw1TdGFydENvbSBMdGQu
MSswKQYDVQQLEyJTZWN1cmUgRGlnaXRhbCBDZXJ0aWZpY2F0ZSBTaWduaW5nMSkwJwYDVQQD
EyBTdGFydENvbSBDZXJ0aWZpY2F0aW9uIEF1dGhvcml0eTAeFw0wNzEwMjQyMTAzMzJaFw0x
MjEwMjIyMTAzMzJaMIGMMQswCQYDVQQGEwJJTDEWMBQGA1UEChMNU3RhcnRDb20gTHRkLjEr
MCkGA1UECxMiU2VjdXJlIERpZ2l0YWwgQ2VydGlmaWNhdGUgU2lnbmluZzE4MDYGA1UEAxMv
U3RhcnRDb20gQ2xhc3MgMyBQcmltYXJ5IEludGVybWVkaWF0ZSBDbGllbnQgQ0EwggEiMA0G
CSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQC5o0luEj4gypQIp71Xi2TlXyLYrj9WkRy+d9BO
0FHPYnAsC99/jx/ibNRwIfAoFhZd+LDscdRSckvwuFSz0bKg3z+9o7cwlVAC9AwMWe8IM0Lx
c+8etYxsX4WIamG9fjzzi5GAW5ESKzzIN3SxHSplyGCWFwx/pgf1f4y6O9/ym+4f6zaDYP6B
x0r+SaJcr6eSGNm7X3EwX1v7XpRBY+aw019o7k72d0IX910F+XGt0OwNdM61Ff3FiTiexeUZ
bWxCGm6GZl+SQVG9xYVIgHQaLXoQF+g2wzrmKCbVcZhqH+hrlRnD6PfCuEyX/BR6PlAPRDlQ
6f1u3wqik+LF5P15AgMBAAGjggNbMIIDVzAMBgNVHRMEBTADAQH/MAsGA1UdDwQEAwIBpjAd
BgNVHQ4EFgQUe4mckpckoYRHAst0/C70rNwy5fMwgagGA1UdIwSBoDCBnYAUTgvvGqRAW6UX
aYcwyjRoQ9BBrvKhgYGkfzB9MQswCQYDVQQGEwJJTDEWMBQGA1UEChMNU3RhcnRDb20gTHRk
LjErMCkGA1UECxMiU2VjdXJlIERpZ2l0YWwgQ2VydGlmaWNhdGUgU2lnbmluZzEpMCcGA1UE
AxMgU3RhcnRDb20gQ2VydGlmaWNhdGlvbiBBdXRob3JpdHmCAQEwCQYDVR0SBAIwADA9Bggr
BgEFBQcBAQQxMC8wLQYIKwYBBQUHMAKGIWh0dHA6Ly93d3cuc3RhcnRzc2wuY29tL3Nmc2Nh
LmNydDBgBgNVHR8EWTBXMCygKqAohiZodHRwOi8vY2VydC5zdGFydGNvbS5vcmcvc2ZzY2Et
Y3JsLmNybDAnoCWgI4YhaHR0cDovL2NybC5zdGFydHNzbC5jb20vc2ZzY2EuY3JsMIIBXQYD
VR0gBIIBVDCCAVAwggFMBgsrBgEEAYG1NwEBBDCCATswLwYIKwYBBQUHAgEWI2h0dHA6Ly9j
ZXJ0LnN0YXJ0Y29tLm9yZy9wb2xpY3kucGRmMDUGCCsGAQUFBwIBFilodHRwOi8vY2VydC5z
dGFydGNvbS5vcmcvaW50ZXJtZWRpYXRlLnBkZjCB0AYIKwYBBQUHAgIwgcMwJxYgU3RhcnQg
Q29tbWVyY2lhbCAoU3RhcnRDb20pIEx0ZC4wAwIBARqBl0xpbWl0ZWQgTGlhYmlsaXR5LCBy
ZWFkIHRoZSBzZWN0aW9uICpMZWdhbCBMaW1pdGF0aW9ucyogb2YgdGhlIFN0YXJ0Q29tIENl
cnRpZmljYXRpb24gQXV0aG9yaXR5IFBvbGljeSBhdmFpbGFibGUgYXQgaHR0cDovL2NlcnQu
c3RhcnRjb20ub3JnL3BvbGljeS5wZGYwEQYJYIZIAYb4QgEBBAQDAgAHMFAGCWCGSAGG+EIB
DQRDFkFTdGFydENvbSBDbGFzcyAzIFByaW1hcnkgSW50ZXJtZWRpYXRlIEZyZWUgU1NMIEVt
YWlsIENlcnRpZmljYXRlczANBgkqhkiG9w0BAQUFAAOCAgEAUpcEDdsKFRCxFBxcSm+8oMTT
fpS7fbZkxWHx5fHDjvAgaBQ+oY0tk4xtbD6VxeHYjxI63+hj8jICnqeVXPe34Bu+XzekIn2T
lrnPCQobKdQF2p52QgUvIxSURed0jcBaCBV22DSKaUqDOzD/Tx6VQy78zpblXjRH7OALE/+H
jzJVmspdnBUUtQOLYgPo924xkxR25VDdgtEE5vAXa/g2oCeZhy0ZEO4NbgIayAYCJcJRDz0h
dD2Ahec65Kw6LB3N7VXEjiRR5/WoKwH/QteRzPJbFDc1somrApjm2cyg+5nbm1RHeFIz+GxX
luRrPztvhNcby0PtAjqwY1txi4sW0R6ZJPuZ2DZ1/dzckoFhyZgFyOX3SEkNXVLldjTzneFJ
FnVSzDbc720vq184jR7pYoI9+f5QJ96a0iLxEAG8SJ5auBwXI/w2FmKmwmdMvJ8/17+B4sMC
IRrXrDQl2xzpVXh/Qcmk5nf+w8HFmqATGy1OUAQbXga7AySAUaYhvvFk50u0bO5DiUGwzrJO
3TrwvaC2Ei4EFaBmIVgG7TfU5TaaY9IcJSCQ7AGUYE3RFSRpsLOoA3DsxP42YERgS/Nxw29+
YqZtPoO2QPbNpI7xnHVCfNBabx3oDIf438nFfv8spw5BQqBSbEF1izJA57eE64CzHnt7lB20
OFD11avYopwxggPKMIIDxgIBATCBkjCBjDELMAkGA1UEBhMCSUwxFjAUBgNVBAoTDVN0YXJ0
Q29tIEx0ZC4xKzApBgNVBAsTIlNlY3VyZSBEaWdpdGFsIENlcnRpZmljYXRlIFNpZ25pbmcx
ODA2BgNVBAMTL1N0YXJ0Q29tIENsYXNzIDMgUHJpbWFyeSBJbnRlcm1lZGlhdGUgQ2xpZW50
IENBAgFVMAkGBSsOAwIaBQCgggIMMBgGCSqGSIb3DQEJAzELBgkqhkiG9w0BBwEwHAYJKoZI
hvcNAQkFMQ8XDTEwMDYwNzE3MDczMVowIwYJKoZIhvcNAQkEMRYEFHOwCJylHVI/D8GhYede
OCj9ZVE0MF8GCSqGSIb3DQEJDzFSMFAwCwYJYIZIAWUDBAECMAoGCCqGSIb3DQMHMA4GCCqG
SIb3DQMCAgIAgDANBggqhkiG9w0DAgIBQDAHBgUrDgMCBzANBggqhkiG9w0DAgIBKDCBowYJ
KwYBBAGCNxAEMYGVMIGSMIGMMQswCQYDVQQGEwJJTDEWMBQGA1UEChMNU3RhcnRDb20gTHRk
LjErMCkGA1UECxMiU2VjdXJlIERpZ2l0YWwgQ2VydGlmaWNhdGUgU2lnbmluZzE4MDYGA1UE
AxMvU3RhcnRDb20gQ2xhc3MgMyBQcmltYXJ5IEludGVybWVkaWF0ZSBDbGllbnQgQ0ECAVUw
gaUGCyqGSIb3DQEJEAILMYGVoIGSMIGMMQswCQYDVQQGEwJJTDEWMBQGA1UEChMNU3RhcnRD
b20gTHRkLjErMCkGA1UECxMiU2VjdXJlIERpZ2l0YWwgQ2VydGlmaWNhdGUgU2lnbmluZzE4
MDYGA1UEAxMvU3RhcnRDb20gQ2xhc3MgMyBQcmltYXJ5IEludGVybWVkaWF0ZSBDbGllbnQg
Q0ECAVUwDQYJKoZIhvcNAQEBBQAEggEAKvrWKJZF1o9PDPq/Lmw7dBWYJz3Mc3TIjcJtlL+i
qsztiqhhKryN2tmuVRQhDyIkYxXEFDRr3xe3sDqANgsOK/7t+MLrtGm22YqcQHBWe5ic6RFa
75582wHJT2rP4qcEuPqiev57IeGhey9SpN55XxIOzpUfm/YA/WqLkYAjwefib9+m4oHXtBlo
MDPw+5I4VlYZmZ/G5guyeMsHeWtgyQ044wvnfDORrGxI2hKzUBxzghz1JDLstjkCkLSccvMt
0NAeoxW7xaSQ0vZ8CqmosbIFrbeNmQG3JNtsp1hN7JZiy4ZRY/+Oy2Y1UHP17g9/QA1zut/N
ahi/2zyEH27OXQAAAAAAAA==
--------------ms040908020809070205030904--


From masters50@octa4.net.au  Mon Jun  7 11:06:11 2010
Return-Path: <masters50@octa4.net.au>
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 8EC483A67B8 for <ietfarch-atompub-archive@core3.amsl.com>; Mon,  7 Jun 2010 11:06:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 3.909
X-Spam-Level: ***
X-Spam-Status: No, score=3.909 tagged_above=-999 required=5 tests=[BAYES_50=0.001, HELO_EQ_AU=0.377, HOST_EQ_AU=0.327, MIME_8BIT_HEADER=0.3, MSGID_RANDY=1.91, RELAY_IS_203=0.994]
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 XNoTyjzbhoCr for <ietfarch-atompub-archive@core3.amsl.com>; Mon,  7 Jun 2010 11:06:10 -0700 (PDT)
Received: from octa4.net.au (communigate.iinet.net.au [203.59.1.19]) by core3.amsl.com (Postfix) with ESMTP id 1F1003A67AC for <atompub-archive@lists.ietf.org>; Mon,  7 Jun 2010 11:06:06 -0700 (PDT)
Received: by octa4.net.au (CommuniGate Pro PIPE 4.1.1) with PIPE id 241640317; Tue, 08 Jun 2010 02:06:05 +0800
Received: from [212.116.220.154] (account <masters50@octa4.net.au>) by octa4.net.au (CommuniGate Pro WebUser 4.1.1) with HTTP id 241640286; Tue, 08 Jun 2010 02:05:48 +0800
From: "2010Itweb Helpdesk " <itwebhelpdesk@mail2waiter.com>
Subject: =?ISO-8859-1?Q?*****Informa=E7=F5es?= institucionais alert******
X-Mailer: CommuniGate Pro WebUser Interface v.4.1.1
Date: Tue, 08 Jun 2010 02:05:48 +0800
Message-ID: <web-241640286@octa4.net.au>
MIME-Version: 1.0
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 8bit
To: undisclosed-recipients:;

Prezado titular da conta de webmail
  
Esta mensagem é de administrador de correio web centro de 
mensagens
toda a rede conta proprietários mail.
Estamos atualizando nossa base de dados e e-mail
centro conta. Estamos cancelando-mail e-mail não 
utilizadas web
conta para criar mais espaço para novas contas.
Para evitar que sua conta do fechamento você terá que
atualizá-lo abaixo para saber que ele é condição de usados 
atualmente
consideração.
Confirmar a sua identidade EMAIL ABAIXO
***************************************************************************************
Nome de usuário Email:
Senha E-mail:
Data de Nascimento:
****************************************************************************************
Atenção! Qualquer proprietário que se recusa a conta de 
atualização
sua conta no prazo de três dias de
notificação de atualização será solto
sua conta permanentemente.
Obrigado por usar o web mail
Equipe de Suporte
Aviso Código: ID67565434

From owner-atom-syntax@mail.imc.org  Mon Jun  7 19:15:49 2010
Return-Path: <owner-atom-syntax@mail.imc.org>
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 813293A68F6 for <ietfarch-atompub-archive@core3.amsl.com>; Mon,  7 Jun 2010 19:15:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.354
X-Spam-Level: **
X-Spam-Status: No, score=2.354 tagged_above=-999 required=5 tests=[BAYES_50=0.001, HELO_MISMATCH_COM=0.553, J_CHICKENPOX_38=0.6, J_CHICKENPOX_44=0.6, J_CHICKENPOX_47=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 1jS3dWFefbR6 for <ietfarch-atompub-archive@core3.amsl.com>; Mon,  7 Jun 2010 19:15:48 -0700 (PDT)
Received: from hoffman.proper.com (Hoffman.Proper.COM [207.182.41.81]) by core3.amsl.com (Postfix) with ESMTP id 24EF13A68A8 for <atompub-archive@ietf.org>; Mon,  7 Jun 2010 19:15:45 -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 o5829OTi040144 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 7 Jun 2010 19:09: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 o5829O1i040143; Mon, 7 Jun 2010 19:09: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-gw0-f43.google.com (mail-gw0-f43.google.com [74.125.83.43]) by hoffman.proper.com (8.14.4/8.14.3) with ESMTP id o5829NbB040138 for <atom-syntax@imc.org>; Mon, 7 Jun 2010 19:09:23 -0700 (MST) (envelope-from jasnell@gmail.com)
Received: by gwaa12 with SMTP id a12so174481gwa.16 for <atom-syntax@imc.org>; Mon, 07 Jun 2010 19:09: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=xG2p5iAZGNL1hVaXbamsEFsdVTj2xJKFBPzOtvscfDU=; b=WB7oyn0yOduxO56o9uJInxnYNa+8S1/Vsgr7pCA5iCyfGagEuAuM80BBz8cEc2GsaC /9IO1SRudQFx4saZMJo3rWgJDNFxAQbLg1La85EdD6Dc1/OMvnmMwLHq0WtVgY9JwzB+ Udad/Vqik6jO7PqyY73UBbQ73bT4+LGrZIq1k=
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=Kf5vJaK2fh1KMTL0s/MemyJ8kvoO8OwHAL+S/xXDlPMUMv9QpR9pBQgsqOmHHqyZyO VLdildXCULpCnG/ZRkfVMx0A+4JIL+oMICs4xTd3SDr0YkwzyJd/WEJWQmh4jr30lTEh r1cNh6fOzsF7/G143+Ge9314JKiykFSvt/hek=
MIME-Version: 1.0
Received: by 10.229.249.213 with SMTP id ml21mr2849314qcb.288.1275962962448;  Mon, 07 Jun 2010 19:09:22 -0700 (PDT)
Received: by 10.229.81.78 with HTTP; Mon, 7 Jun 2010 19:09:21 -0700 (PDT)
In-Reply-To: <AANLkTik7sl_e0x6jTFy-R8ClPRB_qaICAUFXmSF3V5Yl@mail.gmail.com>
References: <AANLkTimANu7KXubPQHACAmVQI7PGlv2nB8wSPjmWdoLZ@mail.gmail.com> <AANLkTik7sl_e0x6jTFy-R8ClPRB_qaICAUFXmSF3V5Yl@mail.gmail.com>
Date: Mon, 7 Jun 2010 19:09:21 -0700
Message-ID: <AANLkTimETI_qPwW6ut6g-yqGWeJvfk11aVYSC9wykTRt@mail.gmail.com>
Subject: Re: eTag, modified and accessed attributes in Link Extensions Draft
From: James Snell <jasnell@gmail.com>
To: Bob Wyman <bob@wyman.us>
Cc: Atom-Syntax <atom-syntax@imc.org>
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 o5829NbB040139
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>

Ok, new version of the Link Extensions draft has been posted..
includes the 'accessed' attribute...

  http://www.ietf.org/internet-drafts/draft-snell-atompub-link-extensions-06.txt

- James

On Tue, Jun 1, 2010 at 4:40 PM, James Snell <jasnell@gmail.com> wrote:
> On Tue, Jun 1, 2010 at 2:27 PM, Bob Wyman <bob@wyman.us> wrote:
>> The draft, as currently written, seems to be a bit ambiguous about the
>> source eTags and the meaning of "modified".
>> My assumption is that an eTag, when used as a link attribute, should not be
>> something generated by the link element creator but should be a mere passing
>> on of an eTag generated by the server that hosts the resource that is linked
>> to. Thus, eTag should be seen as something which, like "hash", simply
>> records and passes on information related to the state of the resource at
>> some specific point in time when it was previously accessed. In this case,
>> you could never have a eTag attribute on a link if the linked-to server did
>> not support eTags. If this assumption is correct, I think it might clarify
>> things if it were stated in the draft.
>
> Agreed.
>
>> It seems that "modified" might be slightly different. In some cases, it
>> seems reasonable that modified would be the modified or updated date
>> reported on accessing a web resource. On the other hand, it seems like it
>> would also be reasonable, in cases where the server does not report modified
>> dates yet the author of the link has knowledge of the modification history,
>> that the link author might include a modified date even though it is NOT
>> reported by the server. However, this means that the link author is not
>> simply recording and passing on data offered by the server. This means that
>> the meaning of "modified" would be somewhat ambiguous. Am I reading this
>> right?
>
> Yes.. I think we need to limit "modified" to the date reported by the
> server. If no date is specified, the modified attribute should not be
> used.  The feed producer should not make up a value on it's own for
> that attribute. The etag and modified attributes should provide enough
> valuable information to perform a reasonable conditional get on the
> linked resource. If the server doesn't provide that information in the
> first place, then it's not of much value.
>
>> I continue to see evidence that formal systems for "Internet citation" or
>> bibliography typically require that a "last accessed" date be included in
>> citations. Thus, I'd like to suggest a new section (as discussed in earlier
>> messages):
>>
>> X.  The 'accessed' attribute
>>
>>    The 'accessed' Attribute specifies a date and time when the
>>    resource identified by the atom:link or atom:content element was
>>    accessed. The 'accessed' attribute SHOULD record the most recent date
>>    and time at which the resource was accessed. The value MUST conform
>>    to the "date-time" production defined by [RFC3339].  An uppercase
>>    "T" character MUST be used to separate date and time, and an
>>    uppercase "Z" character MUST be present in the absence of a numeric
>>    time zone offset.  The 'accessed' attribute MAY appear as a child
>>    of the atom:link and atom:content elements.
>>
>>      accessed = attribute accessed { xsd:dateTime }
>>
>>    An example accessed attribute for an enclosed MP3 file:
>>
>>      <atom:link rel="enclosure"
>>        href="http://example.org/media/myfile.mp3"
>>        accessed="2010-12-12T12:12:12Z" />
>>
>> bob wyman
>>
>
> +1. I've been looking at this also. We are going to need to include
> some semantics for when the accessed attribute is omitted. This
> attribute essentially needs to establish the point in time at which
> the modified, etag and hash were considered to be valid... if it is
> omitted, then the atom:updated has to be assumed to be the fallback.
>
> - James
>



-- 
- James Snell
  http://www.snellspace.com
  jasnell@gmail.com


From owner-atom-syntax@mail.imc.org  Mon Jun  7 20:23:29 2010
Return-Path: <owner-atom-syntax@mail.imc.org>
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 BC3193A6920 for <ietfarch-atompub-archive@core3.amsl.com>; Mon,  7 Jun 2010 20:23:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.554
X-Spam-Level: 
X-Spam-Status: No, score=0.554 tagged_above=-999 required=5 tests=[BAYES_50=0.001, 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 YSiHmYIKbMaB for <ietfarch-atompub-archive@core3.amsl.com>; Mon,  7 Jun 2010 20:23:28 -0700 (PDT)
Received: from hoffman.proper.com (Hoffman.Proper.COM [207.182.41.81]) by core3.amsl.com (Postfix) with ESMTP id DC2663A691E for <atompub-archive@ietf.org>; Mon,  7 Jun 2010 20:23:28 -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 o583IVSp044182 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 7 Jun 2010 20:18:31 -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 o583IVfN044181; Mon, 7 Jun 2010 20:18:31 -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-vw0-f43.google.com (mail-vw0-f43.google.com [209.85.212.43]) by hoffman.proper.com (8.14.4/8.14.3) with ESMTP id o583IVdG044176 for <atom-syntax@imc.org>; Mon, 7 Jun 2010 20:18:31 -0700 (MST) (envelope-from jasnell@gmail.com)
Received: by vws3 with SMTP id 3so6868443vws.16 for <atom-syntax@imc.org>; Mon, 07 Jun 2010 20:18:30 -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=jE5ulxSJ+kKFu/5jzqb8ULg0Jj5r7vBBEJaiGGab6U8=; b=JOlbL30TyLHYPEZtVmpNHIFdaZkXWXKocaNOIYjCJm+wAHLiUQ5N23npeP+dxCDEPZ hby6iUbrPBxUvXYxQOtv625Jl7HZWslCVsbv7uVbF35FdAxHt6vy3TkWtTK9W+eusJjl 51wF4XiY9NqSUhrCHkrbY3dcDl/ChR//C5Hs4=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=OIx5y2v+tRqi3zHI6RaGrTJ3ee/qwXoEc3MoKXGqS/EXuVwZ/jaMtj7FquCZWlu9Wg +Mk+ZraIuv7zjB6u75Yb1bXYbhsASVEq6lg9lQaXUXIYZN/fJPA604UAksV2W1zfxin2 CRH2GAj+wb8jUZTR9T0h1HszD3LQrL1yRgmmQ=
MIME-Version: 1.0
Received: by 10.229.188.75 with SMTP id cz11mr5428031qcb.115.1275967109773;  Mon, 07 Jun 2010 20:18:29 -0700 (PDT)
Received: by 10.229.81.78 with HTTP; Mon, 7 Jun 2010 20:18:29 -0700 (PDT)
Date: Mon, 7 Jun 2010 20:18:29 -0700
Message-ID: <AANLkTin26zp1aOkcQO3q8YcLa8TjiK6BMrNFYCCmFaUt@mail.gmail.com>
Subject: Atom Tombstones Done?
From: James Snell <jasnell@gmail.com>
To: Atom Syntax <atom-syntax@imc.org>
Content-Type: text/plain; charset=ISO-8859-1
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>

Ok, looking over the Atom Tombstones draft, I cannot see any further
edits that need to be made. Is it done? Ready to push for last call?

-- 
- James Snell
  http://www.snellspace.com
  jasnell@gmail.com


From owner-atom-syntax@mail.imc.org  Tue Jun  8 10:47:26 2010
Return-Path: <owner-atom-syntax@mail.imc.org>
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 6E9B43A69F3 for <ietfarch-atompub-archive@core3.amsl.com>; Tue,  8 Jun 2010 10:47:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.777
X-Spam-Level: *
X-Spam-Status: No, score=1.777 tagged_above=-999 required=5 tests=[BAYES_50=0.001, FM_FORGED_GMAIL=0.622, HELO_MISMATCH_COM=0.553, HTML_MESSAGE=0.001, J_CHICKENPOX_46=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 gV0LkMpVabto for <ietfarch-atompub-archive@core3.amsl.com>; Tue,  8 Jun 2010 10:47:24 -0700 (PDT)
Received: from hoffman.proper.com (Hoffman.Proper.COM [207.182.41.81]) by core3.amsl.com (Postfix) with ESMTP id E2B7E3A69E2 for <atompub-archive@ietf.org>; Tue,  8 Jun 2010 10:47:23 -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 o58HeaF9002804 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 8 Jun 2010 10:40: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 o58HeaEU002803; Tue, 8 Jun 2010 10:40: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-gy0-f171.google.com (mail-gy0-f171.google.com [209.85.160.171]) by hoffman.proper.com (8.14.4/8.14.3) with ESMTP id o58HeZwH002794 for <atom-syntax@imc.org>; Tue, 8 Jun 2010 10:40:35 -0700 (MST) (envelope-from bobwyman@gmail.com)
Received: by gyf3 with SMTP id 3so2925111gyf.16 for <atom-syntax@imc.org>; Tue, 08 Jun 2010 10:40:34 -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=Xr8iujjEkw+uPAigAhmNXykW6GIiQC4EvMqrogdjGa0=; b=OjJiAyyWy2V75VGxxzrqRojMRm0NQVzbd4lJZIMm+XGbAMGeLmqViQfyMMGQGnPxuZ 92J7/17u3Y0Exk3Gf7idx1e73T6h1J4yi7sPO82u41/4e5aTlZ5hNRKg/PvsiWW5opvk mY6Pz5KxubkPLUqVrAw0PeF3ZfFl9xPUXAsls=
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=xvJBLSXFJygfdDC7ntUkYYZm0ryu3J/DsHQVuJ2OaPOTTA1063YjfAWeD0x5X6cjX8 IeAPHXZT0kem+V3JP9nYnEsKYH1Rh40esAkeHtHG7mMc1r/07NS9y5NTiyNq/l5acCKg 0SpCnOQpyTiEBf7u6Cxe0oFhokRoq7CYb4i1M=
MIME-Version: 1.0
Received: by 10.101.105.2 with SMTP id h2mr17058193anm.83.1276018834539; Tue,  08 Jun 2010 10:40:34 -0700 (PDT)
Received: by 10.100.119.16 with HTTP; Tue, 8 Jun 2010 10:40:34 -0700 (PDT)
In-Reply-To: <AANLkTin26zp1aOkcQO3q8YcLa8TjiK6BMrNFYCCmFaUt@mail.gmail.com>
References: <AANLkTin26zp1aOkcQO3q8YcLa8TjiK6BMrNFYCCmFaUt@mail.gmail.com>
Date: Tue, 8 Jun 2010 13:40:34 -0400
X-Google-Sender-Auth: IikNaUbFuFix0Jnqg3a1bUXI5DU
Message-ID: <AANLkTil2ZmirR6iGsRL6-XWFvTF5kmY_AVRZAWnbVzB8@mail.gmail.com>
Subject: Re: Atom Tombstones Done?
From: Bob Wyman <bob@wyman.us>
To: James Snell <jasnell@gmail.com>, Atom Syntax <atom-syntax@imc.org>
Content-Type: multipart/alternative; boundary=001636c9268b5c054e04888849ec
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>

--001636c9268b5c054e04888849ec
Content-Type: text/plain; charset=ISO-8859-1

The abstract says:

   This specification adds mechanisms to the Atom Syndication Format
   which Atom Feed publishers can use to explicitly identify Atom
   entries that have been removed from an Atom feed.

Thus, it appears that the document is specific to "feed" publishers and
doesn't give proper consideration to those that publish Atom Entry
Documents. I would reword this as follows (or something similar):

"This specification adds mechanisms to the Atom Syndication Format which
publishers of Atom Feed and Entry documents can use to explicitly identify
Atom entries that have been removed."


A similar edit would be appropriate for "Section 1, The Introduction" which
seems overly focused on "feeds".

Section 4 "Deleted Entry Document": Although it is reasonable that a
deleted-entry element, when contained in a feed, MAY contain an atom:source
element (since it is assumed that the enclosing feed document is the entry's
source), I think that we should depart from the wording of the base Atom
Syntax here and say that when a deleted-entry element appears in a Feed
document other than its source feed or when it comprises a Deleted Entry
Document, that the deleted-entry really *MUST* contain an atom:source.

Personally, I would be very pleased if you could add some non-normative text
that makes it clear that a deleted-entry is "informational" rather than
"imperative." I am concerned that we will see people complaining and
potentially even suing in court, when some service fails to "delete" some
entry that is particularly embarrassing or that otherwise continues to
distribute information that some publisher would prefer to have removed from
the system. To those of us close to this issue, it may be obvious that a
standard like this cannot impose legally enforceable requirements on people,
however, we need to recognize that the world into which our work flows is
one populated not only by those of good will and knowledge but also by
idiots, twits, and litigious fools... It is best to preemptively disable or
mute some of the inevitable silliness by ensuring that the standard itself
tells the fools to stifle themselves... (In slightly more polite terms, of
course...)

bob wyman

On Mon, Jun 7, 2010 at 11:18 PM, James Snell <jasnell@gmail.com> wrote:

>
> Ok, looking over the Atom Tombstones draft, I cannot see any further
> edits that need to be made. Is it done? Ready to push for last call?
>
> --
> - James Snell
>  http://www.snellspace.com
>  jasnell@gmail.com
>
>

--001636c9268b5c054e04888849ec
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

The abstract says:<div><span class=3D"Apple-style-span" style=3D"font-famil=
y: &#39;Times New Roman&#39;; font-size: medium; "><pre style=3D"word-wrap:=
 break-word; white-space: pre-wrap; ">   This specification adds mechanisms=
 to the Atom Syndication Format
   which Atom Feed publishers can use to explicitly identify Atom
   entries that have been removed from an Atom feed.</pre></span></div><div=
>Thus, it appears that the document is specific to &quot;feed&quot; publish=
ers and doesn&#39;t give proper consideration to those that publish Atom En=
try Documents. I would reword this as follows (or something similar):</div>
<div><br></div><blockquote class=3D"webkit-indent-blockquote" style=3D"marg=
in: 0 0 0 40px; border: none; padding: 0px;"><div>&quot;This specification =
adds mechanisms to the Atom Syndication Format which publishers of Atom Fee=
d and Entry documents can use to explicitly identify Atom entries that have=
 been removed.&quot;</div>
</blockquote><div><br></div><div>A similar edit would be appropriate for &q=
uot;Section 1, The Introduction&quot; which seems overly focused on &quot;f=
eeds&quot;.</div><div><br>Section 4 &quot;Deleted Entry Document&quot;: Alt=
hough it is reasonable that a deleted-entry element, when contained in a fe=
ed, MAY contain an atom:source element (since it is assumed that the enclos=
ing feed document is the entry&#39;s source), I think that we should depart=
 from the wording of the base Atom Syntax here and say that when a deleted-=
entry element appears in a Feed document other than its source feed or when=
 it comprises a Deleted Entry Document, that the deleted-entry really <b>MU=
ST</b> contain an atom:source.</div>
<div><br></div><div>Personally, I would be very pleased if you could add so=
me non-normative text that makes it clear that a deleted-entry is &quot;inf=
ormational&quot; rather than &quot;imperative.&quot; I am concerned that we=
 will see people complaining and potentially even suing in court, when some=
 service fails to &quot;delete&quot; some entry that is particularly embarr=
assing or that otherwise continues to distribute information that some publ=
isher would prefer to have removed from the system. To those of us close to=
 this issue, it may be obvious that a standard like this cannot impose lega=
lly enforceable requirements on people, however, we need to recognize that =
the world into which our work flows is one populated not only by those of g=
ood will and knowledge but also by idiots, twits, and litigious fools... It=
 is best to preemptively disable or mute some of the inevitable silliness b=
y ensuring that the standard itself tells the fools to stifle themselves...=
 (In slightly more polite terms, of course...)</div>
<div><br></div><div>bob wyman</div><div><br><div class=3D"gmail_quote">On M=
on, Jun 7, 2010 at 11:18 PM, James Snell <span dir=3D"ltr">&lt;<a href=3D"m=
ailto:jasnell@gmail.com">jasnell@gmail.com</a>&gt;</span> wrote:<br><blockq=
uote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc =
solid;padding-left:1ex;">
<br>
Ok, looking over the Atom Tombstones draft, I cannot see any further<br>
edits that need to be made. Is it done? Ready to push for last call?<br>
<font color=3D"#888888"><br>
--<br>
- James Snell<br>
 =A0<a href=3D"http://www.snellspace.com" target=3D"_blank">http://www.snel=
lspace.com</a><br>
 =A0<a href=3D"mailto:jasnell@gmail.com">jasnell@gmail.com</a><br>
<br>
</font></blockquote></div><br></div>

--001636c9268b5c054e04888849ec--


From owner-atom-syntax@mail.imc.org  Tue Jun  8 11:53:54 2010
Return-Path: <owner-atom-syntax@mail.imc.org>
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 166BC3A68E3 for <ietfarch-atompub-archive@core3.amsl.com>; Tue,  8 Jun 2010 11:53:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.176
X-Spam-Level: *
X-Spam-Status: No, score=1.176 tagged_above=-999 required=5 tests=[BAYES_50=0.001, 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 31jPxoG8D-fS for <ietfarch-atompub-archive@core3.amsl.com>; Tue,  8 Jun 2010 11:53:53 -0700 (PDT)
Received: from hoffman.proper.com (Hoffman.Proper.COM [207.182.41.81]) by core3.amsl.com (Postfix) with ESMTP id 6D7793A6781 for <atompub-archive@ietf.org>; Tue,  8 Jun 2010 11:53:53 -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 o58Ij1Qb006831 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 8 Jun 2010 11:45:01 -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 o58Ij1HD006829; Tue, 8 Jun 2010 11:45:01 -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-gy0-f171.google.com (mail-gy0-f171.google.com [209.85.160.171]) by hoffman.proper.com (8.14.4/8.14.3) with ESMTP id o58Ij0mb006821 for <atom-syntax@imc.org>; Tue, 8 Jun 2010 11:45:01 -0700 (MST) (envelope-from ed.summers@gmail.com)
Received: by gyf3 with SMTP id 3so3012552gyf.16 for <atom-syntax@imc.org>; Tue, 08 Jun 2010 11:45:00 -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=tcWXumwTrhuem3upzpQDqhdjIA8AHI2QPpl7lFuRHBQ=; b=x4Fjt3MCB3lxwcS0JRCdmsfR/BXPSH/ZU5KEd8ql2mORxQY+k5UJ7rYmzdYB97v1UI rjgNf3WyUpG4eJx9R2nEG56P9HCJMZF9LPMxpMcjhKmomWfqWGcPWI+BGJeo4kJ+vojA hOxGXHYqccEuVJQk3huxxVUoMgWmXicmIE1f8=
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=MpuZHCAPNrEB4oNmmcHtlKB35iFs04s106g+scg+iQFEvpDLhClLObyDKsKDB3ieRO Zu3YrFvFUVMTS1z+n+/ZVbE3HyxYvB9zy7blHCP1zpv0DqUjzZJirlVqL5DQgHviRx9l OayR51PO3u6qoJ+15oFCLrndyLo2JVvn7f1ik=
MIME-Version: 1.0
Received: by 10.150.48.31 with SMTP id v31mr283710ybv.289.1276022699177; Tue,  08 Jun 2010 11:44:59 -0700 (PDT)
Received: by 10.151.105.11 with HTTP; Tue, 8 Jun 2010 11:44:59 -0700 (PDT)
In-Reply-To: <AANLkTin26zp1aOkcQO3q8YcLa8TjiK6BMrNFYCCmFaUt@mail.gmail.com>
References: <AANLkTin26zp1aOkcQO3q8YcLa8TjiK6BMrNFYCCmFaUt@mail.gmail.com>
Date: Tue, 8 Jun 2010 14:44:59 -0400
X-Google-Sender-Auth: GmyjpK7EcIPXxEdwTONpqLOSOc0
Message-ID: <AANLkTik58RYU9TCI_vC7ec7EQ9XgxTKg12DR1K_306w0@mail.gmail.com>
Subject: Re: Atom Tombstones Done?
From: Ed Summers <ehs@pobox.com>
To: James Snell <jasnell@gmail.com>
Cc: Atom Syntax <atom-syntax@imc.org>
Content-Type: text/plain; charset=ISO-8859-1
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>

On Mon, Jun 7, 2010 at 11:18 PM, James Snell <jasnell@gmail.com> wrote:
>
> Ok, looking over the Atom Tombstones draft, I cannot see any further
> edits that need to be made. Is it done? Ready to push for last call?

+1

//Ed


From owner-atom-syntax@mail.imc.org  Wed Jun  9 12:08:48 2010
Return-Path: <owner-atom-syntax@mail.imc.org>
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 5642F3A67CF for <ietfarch-atompub-archive@core3.amsl.com>; Wed,  9 Jun 2010 12:08:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.754
X-Spam-Level: *
X-Spam-Status: No, score=1.754 tagged_above=-999 required=5 tests=[AWL=0.600, BAYES_50=0.001, HELO_MISMATCH_COM=0.553, J_CHICKENPOX_46=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 5wZD3H+zHO02 for <ietfarch-atompub-archive@core3.amsl.com>; Wed,  9 Jun 2010 12:08:44 -0700 (PDT)
Received: from hoffman.proper.com (Hoffman.Proper.COM [207.182.41.81]) by core3.amsl.com (Postfix) with ESMTP id 196473A67B8 for <atompub-archive@ietf.org>; Wed,  9 Jun 2010 12:08:44 -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 o59J2jgl092976 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 9 Jun 2010 12:02: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 o59J2j6u092975; Wed, 9 Jun 2010 12:02: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-pv0-f171.google.com (mail-pv0-f171.google.com [74.125.83.171]) by hoffman.proper.com (8.14.4/8.14.3) with ESMTP id o59J2fsP092966 for <atom-syntax@imc.org>; Wed, 9 Jun 2010 12:02:45 -0700 (MST) (envelope-from jasnell@gmail.com)
Received: by pvg2 with SMTP id 2so2200279pvg.16 for <atom-syntax@imc.org>; Wed, 09 Jun 2010 12:02:40 -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=rywUWJpoihSxn3NhRThsCXAt5ZT8+qOJQbVFtp85OPs=; b=pKcQJfoJvykGxEhECXb1IbX8vsvW3r5QEBNvQv2/KPRIcVeSZ7Ye/kCkfWN8fy1rLv 8zHVp6lYZuy6wtIvyZGBhBiUHb3pfIYkb4ENYKbD4rgiZJyBq6nfp1py0V+XhPguUulj B+oa+HzYfHYjmn8cjxO4sNMdwHVGmuFDwgnQQ=
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=Zn/mdXubVxILfbWCwh4YYoHU3qtgZ6JE0+SOmjT/vdYJcer50+oQ0XBZtXDkW5iBdO vDMoDmHbNhkWnqlt3rWm451vWSuHmV6AVQpVVxk/cUVyCTXVd/tn9InhI088Lpo9uhFt ebowzXfhRq9TqXGOvxHb+AvWUS9ZHgDrklq8M=
MIME-Version: 1.0
Received: by 10.229.186.211 with SMTP id ct19mr4839307qcb.206.1276110155806;  Wed, 09 Jun 2010 12:02:35 -0700 (PDT)
Received: by 10.229.81.78 with HTTP; Wed, 9 Jun 2010 12:02:35 -0700 (PDT)
In-Reply-To: <AANLkTil2ZmirR6iGsRL6-XWFvTF5kmY_AVRZAWnbVzB8@mail.gmail.com>
References: <AANLkTin26zp1aOkcQO3q8YcLa8TjiK6BMrNFYCCmFaUt@mail.gmail.com> <AANLkTil2ZmirR6iGsRL6-XWFvTF5kmY_AVRZAWnbVzB8@mail.gmail.com>
Date: Wed, 9 Jun 2010 12:02:35 -0700
Message-ID: <AANLkTimCAw34bvO-QKNmwU7SpjTw71mk2PYOnnpMCe9r@mail.gmail.com>
Subject: Re: Atom Tombstones Done?
From: James Snell <jasnell@gmail.com>
To: Bob Wyman <bob@wyman.us>
Cc: Atom Syntax <atom-syntax@imc.org>
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 o59J2jsP092971
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>

On Tue, Jun 8, 2010 at 10:40 AM, Bob Wyman <bob@wyman.us> wrote:
> The abstract says:
>
>    This specification adds mechanisms to the Atom Syndication Format
>    which Atom Feed publishers can use to explicitly identify Atom
>    entries that have been removed from an Atom feed.
>
> Thus, it appears that the document is specific to "feed" publishers and
> doesn't give proper consideration to those that publish Atom Entry
> Documents. I would reword this as follows (or something similar):
>
> "This specification adds mechanisms to the Atom Syndication Format which
> publishers of Atom Feed and Entry documents can use to explicitly identify
> Atom entries that have been removed."
>
> A similar edit would be appropriate for "Section 1, The Introduction" which
> seems overly focused on "feeds".

+1

> Section 4 "Deleted Entry Document": Although it is reasonable that a
> deleted-entry element, when contained in a feed, MAY contain an atom:source
> element (since it is assumed that the enclosing feed document is the entry's
> source), I think that we should depart from the wording of the base Atom
> Syntax here and say that when a deleted-entry element appears in a Feed
> document other than its source feed or when it comprises a Deleted Entry
> Document, that the deleted-entry really MUST contain an atom:source.
>

I disagree. There may be no source feed at all... and therefore no
reason for atom:source

Personally, I would be very pleased if you could add some non-normative text
> that makes it clear that a deleted-entry is "informational" rather than
> "imperative." I am concerned that we will see people complaining and
> potentially even suing in court, when some service fails to "delete" some
> entry that is particularly embarrassing or that otherwise continues to
> distribute information that some publisher would prefer to have removed from
> the system. To those of us close to this issue, it may be obvious that a
> standard like this cannot impose legally enforceable requirements on people,
> however, we need to recognize that the world into which our work flows is
> one populated not only by those of good will and knowledge but also by
> idiots, twits, and litigious fools... It is best to preemptively disable or
> mute some of the inevitable silliness by ensuring that the standard itself
> tells the fools to stifle themselves... (In slightly more polite terms, of
> course...)

Agreed.

> bob wyman
> On Mon, Jun 7, 2010 at 11:18 PM, James Snell <jasnell@gmail.com> wrote:
>>
>> Ok, looking over the Atom Tombstones draft, I cannot see any further
>> edits that need to be made. Is it done? Ready to push for last call?
>>
>> --
>> - James Snell
>>  http://www.snellspace.com
>>  jasnell@gmail.com
>>
>
>



-- 
- James Snell
  http://www.snellspace.com
  jasnell@gmail.com


From owner-atom-syntax@mail.imc.org  Wed Jun  9 12:17:02 2010
Return-Path: <owner-atom-syntax@mail.imc.org>
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 79CE03A67EF for <ietfarch-atompub-archive@core3.amsl.com>; Wed,  9 Jun 2010 12:17:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.854
X-Spam-Level: 
X-Spam-Status: No, score=0.854 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_50=0.001, HELO_MISMATCH_COM=0.553, J_CHICKENPOX_46=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 0yPt5UDqEy13 for <ietfarch-atompub-archive@core3.amsl.com>; Wed,  9 Jun 2010 12:17:01 -0700 (PDT)
Received: from hoffman.proper.com (Hoffman.Proper.COM [207.182.41.81]) by core3.amsl.com (Postfix) with ESMTP id CE2983A676A for <atompub-archive@ietf.org>; Wed,  9 Jun 2010 12:17:01 -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 o59JDA6D093922 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 9 Jun 2010 12:13:10 -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 o59JDADf093920; Wed, 9 Jun 2010 12:13:10 -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-px0-f171.google.com (mail-px0-f171.google.com [209.85.212.171]) by hoffman.proper.com (8.14.4/8.14.3) with ESMTP id o59JD9Iv093915 for <atom-syntax@imc.org>; Wed, 9 Jun 2010 12:13:09 -0700 (MST) (envelope-from jasnell@gmail.com)
Received: by pxi13 with SMTP id 13so658748pxi.16 for <atom-syntax@imc.org>; Wed, 09 Jun 2010 12:13:08 -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=bwOQZD9ewFfn0f3B/kMburMZ8AtE201YPRB+BG8PukA=; b=EjlM6U6tDfoqB6yQLBIrdwOBA1aUg1IZWcCNu2aTEo0d1mFFlE7iIBEK2CauPh/laZ y0xnFQzvxOoL/maxCqGX44O90hbKKNyVp2MnECARuBDdZLKCccKWwAEbf/KqqCosHjBF rV0j54w/yGB9tiiMl8BfojJl4EfA1/dc5JNg4=
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=EriDxF3RRuw6dqMT8IbDBpT3EYqslppAqQiesycz2Dz6Gso9O1uL9ywR+KhLAIJ8K3 ZMTvvRN8sCHAP5HOwJqF1BK1EOfUx3oCGObJp/SkQTKEJnmPxw3G6b3b+mutw8lUdxlV ThtI9+G9uVNmlmUy1ghmP2tIU+7PlEEBvd8Yg=
MIME-Version: 1.0
Received: by 10.229.181.3 with SMTP id bw3mr7411893qcb.155.1276110788152; Wed,  09 Jun 2010 12:13:08 -0700 (PDT)
Received: by 10.229.81.78 with HTTP; Wed, 9 Jun 2010 12:13:08 -0700 (PDT)
In-Reply-To: <AANLkTil14wmzRUV93Uk5ILyGa2T6Omp3ogz9R2fGOw0o@mail.gmail.com>
References: <AANLkTin26zp1aOkcQO3q8YcLa8TjiK6BMrNFYCCmFaUt@mail.gmail.com> <AANLkTil2ZmirR6iGsRL6-XWFvTF5kmY_AVRZAWnbVzB8@mail.gmail.com> <AANLkTimCAw34bvO-QKNmwU7SpjTw71mk2PYOnnpMCe9r@mail.gmail.com> <AANLkTil14wmzRUV93Uk5ILyGa2T6Omp3ogz9R2fGOw0o@mail.gmail.com>
Date: Wed, 9 Jun 2010 12:13:08 -0700
Message-ID: <AANLkTil9wH9e7VcujYhNKT90uylJCI_Axzu4BFCP6PHv@mail.gmail.com>
Subject: Re: Atom Tombstones Done?
From: James Snell <jasnell@gmail.com>
To: Bob Wyman <bob@wyman.us>
Cc: Atom Syntax <atom-syntax@imc.org>
Content-Type: text/plain; charset=ISO-8859-1
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>

On Wed, Jun 9, 2010 at 12:09 PM, Bob Wyman <bob@wyman.us> wrote:
>
>> [snip]
>> I disagree. There may be no source feed at all... and therefore no
>> reason for atom:source
>
>
> You are, of course, correct. How about saying that "if there is a source
> feed, you MUST provide an atom:source" ???
>
>>

That works for me.


From owner-atom-syntax@mail.imc.org  Wed Jun  9 12:18:11 2010
Return-Path: <owner-atom-syntax@mail.imc.org>
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 553403A676A for <ietfarch-atompub-archive@core3.amsl.com>; Wed,  9 Jun 2010 12:18:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.777
X-Spam-Level: *
X-Spam-Status: No, score=1.777 tagged_above=-999 required=5 tests=[BAYES_50=0.001, FM_FORGED_GMAIL=0.622, HELO_MISMATCH_COM=0.553, HTML_MESSAGE=0.001, J_CHICKENPOX_46=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 Vw1AmbmeroEW for <ietfarch-atompub-archive@core3.amsl.com>; Wed,  9 Jun 2010 12:18:10 -0700 (PDT)
Received: from hoffman.proper.com (Hoffman.Proper.COM [207.182.41.81]) by core3.amsl.com (Postfix) with ESMTP id 00F6F3A685E for <atompub-archive@ietf.org>; Wed,  9 Jun 2010 12:18:09 -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 o59J9mWh093586 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 9 Jun 2010 12:09:48 -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 o59J9mqf093585; Wed, 9 Jun 2010 12:09:48 -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-yx0-f171.google.com (mail-yx0-f171.google.com [209.85.213.171]) by hoffman.proper.com (8.14.4/8.14.3) with ESMTP id o59J9lgp093580 for <atom-syntax@imc.org>; Wed, 9 Jun 2010 12:09:48 -0700 (MST) (envelope-from bobwyman@gmail.com)
Received: by yxn22 with SMTP id 22so1437914yxn.16 for <atom-syntax@imc.org>; Wed, 09 Jun 2010 12:09:47 -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=/AnGsxaQ1WmXwEr93tMca6fodSsD0JHHipWI2ZMFjq4=; b=IOjcita3Fm9Go5+SZPo9sOq5Zl3gBcBbQbaKLWu01VhSdvZB4cz2I7N7/xl4Aw1Gb8 1A6KRZ11ekzG+1K+zkikY6kJlKLGPB753+y9WOew53GCXIFK11Bp1JhklmukixI5KBd0 cQUbLGbRhxrCgpd4RiSzU5HelSk8VeiZGudFc=
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=RizEPOl7EZMtRMggpr17ufryrkUZ1Qtq2C+HOGrEyBROXLfpD9b3WC5YTSYPcfoSYs ZeAgVf/qYeQ4tM60TxUd4GGjrr9gmTlVBU0VFOBfsZKtabZOjpJBEMPLzw8AsxzEoif+ LHJxF8wgjqVmYvA5GAqLxw0OANEiQrt0lY6cU=
MIME-Version: 1.0
Received: by 10.101.2.7 with SMTP id e7mr18789950ani.79.1276110586898; Wed, 09  Jun 2010 12:09:46 -0700 (PDT)
Received: by 10.100.119.16 with HTTP; Wed, 9 Jun 2010 12:09:46 -0700 (PDT)
In-Reply-To: <AANLkTimCAw34bvO-QKNmwU7SpjTw71mk2PYOnnpMCe9r@mail.gmail.com>
References: <AANLkTin26zp1aOkcQO3q8YcLa8TjiK6BMrNFYCCmFaUt@mail.gmail.com> <AANLkTil2ZmirR6iGsRL6-XWFvTF5kmY_AVRZAWnbVzB8@mail.gmail.com> <AANLkTimCAw34bvO-QKNmwU7SpjTw71mk2PYOnnpMCe9r@mail.gmail.com>
Date: Wed, 9 Jun 2010 15:09:46 -0400
X-Google-Sender-Auth: cvE23Q9_0J44a21-wtGxu3OOH4U
Message-ID: <AANLkTil14wmzRUV93Uk5ILyGa2T6Omp3ogz9R2fGOw0o@mail.gmail.com>
Subject: Re: Atom Tombstones Done?
From: Bob Wyman <bob@wyman.us>
To: James Snell <jasnell@gmail.com>
Cc: Atom Syntax <atom-syntax@imc.org>
Content-Type: multipart/alternative; boundary=0016368e325d39e99504889da666
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>

--0016368e325d39e99504889da666
Content-Type: text/plain; charset=ISO-8859-1

On Wed, Jun 9, 2010 at 3:02 PM, James Snell <jasnell@gmail.com> wrote:

> On Tue, Jun 8, 2010 at 10:40 AM, Bob Wyman <bob@wyman.us> wrote:
> > The abstract says:
> >
> >    This specification adds mechanisms to the Atom Syndication Format
> >    which Atom Feed publishers can use to explicitly identify Atom
> >    entries that have been removed from an Atom feed.
> >
> > Thus, it appears that the document is specific to "feed" publishers and
> > doesn't give proper consideration to those that publish Atom Entry
> > Documents. I would reword this as follows (or something similar):
> >
> > "This specification adds mechanisms to the Atom Syndication Format which
> > publishers of Atom Feed and Entry documents can use to explicitly
> identify
> > Atom entries that have been removed."
> >
> > A similar edit would be appropriate for "Section 1, The Introduction"
> which
> > seems overly focused on "feeds".
>
> +1
>
> > Section 4 "Deleted Entry Document": Although it is reasonable that a
> > deleted-entry element, when contained in a feed, MAY contain an
> atom:source
> > element (since it is assumed that the enclosing feed document is the
> entry's
> > source), I think that we should depart from the wording of the base Atom
> > Syntax here and say that when a deleted-entry element appears in a Feed
> > document other than its source feed or when it comprises a Deleted Entry
> > Document, that the deleted-entry really MUST contain an atom:source.
> >
>
> I disagree. There may be no source feed at all... and therefore no
> reason for atom:source
>

You are, of course, correct. How about saying that "if there is a source
feed, you MUST provide an atom:source" ???


>
> Personally, I would be very pleased if you could add some non-normative
> text
> > that makes it clear that a deleted-entry is "informational" rather than
> > "imperative." I am concerned that we will see people complaining and
> > potentially even suing in court, when some service fails to "delete" some
> > entry that is particularly embarrassing or that otherwise continues to
> > distribute information that some publisher would prefer to have removed
> from
> > the system. To those of us close to this issue, it may be obvious that a
> > standard like this cannot impose legally enforceable requirements on
> people,
> > however, we need to recognize that the world into which our work flows is
> > one populated not only by those of good will and knowledge but also by
> > idiots, twits, and litigious fools... It is best to preemptively disable
> or
> > mute some of the inevitable silliness by ensuring that the standard
> itself
> > tells the fools to stifle themselves... (In slightly more polite terms,
> of
> > course...)
>
> Agreed.
>
> > bob wyman
> > On Mon, Jun 7, 2010 at 11:18 PM, James Snell <jasnell@gmail.com> wrote:
> >>
> >> Ok, looking over the Atom Tombstones draft, I cannot see any further
> >> edits that need to be made. Is it done? Ready to push for last call?
> >>
> >> --
> >> - James Snell
> >>  http://www.snellspace.com
> >>  jasnell@gmail.com
> >>
> >
> >
>
>
>
> --
> - James Snell
>  http://www.snellspace.com
>  jasnell@gmail.com
>

--0016368e325d39e99504889da666
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<br><br><div class=3D"gmail_quote">On Wed, Jun 9, 2010 at 3:02 PM, James Sn=
ell <span dir=3D"ltr">&lt;<a href=3D"mailto:jasnell@gmail.com">jasnell@gmai=
l.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"m=
argin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class=3D"im">On Tue, Jun 8, 2010 at 10:40 AM, Bob Wyman &lt;<a href=3D=
"mailto:bob@wyman.us">bob@wyman.us</a>&gt; wrote:<br>
&gt; The abstract says:<br>
&gt;<br>
&gt; =A0 =A0This specification adds mechanisms to the Atom Syndication Form=
at<br>
&gt; =A0 =A0which Atom Feed publishers can use to explicitly identify Atom<=
br>
&gt; =A0 =A0entries that have been removed from an Atom feed.<br>
&gt;<br>
&gt; Thus, it appears that the document is specific to &quot;feed&quot; pub=
lishers and<br>
&gt; doesn&#39;t give proper consideration to those that publish Atom Entry=
<br>
&gt; Documents. I would reword this as follows (or something similar):<br>
&gt;<br>
&gt; &quot;This specification adds mechanisms to the Atom Syndication Forma=
t which<br>
&gt; publishers of Atom Feed and Entry documents can use to explicitly iden=
tify<br>
&gt; Atom entries that have been removed.&quot;<br>
&gt;<br>
&gt; A similar edit would be appropriate for &quot;Section 1, The Introduct=
ion&quot; which<br>
&gt; seems overly focused on &quot;feeds&quot;.<br>
<br>
</div>+1<br>
<div class=3D"im"><br>
&gt; Section 4 &quot;Deleted Entry Document&quot;: Although it is reasonabl=
e that a<br>
&gt; deleted-entry element, when contained in a feed, MAY contain an atom:s=
ource<br>
&gt; element (since it is assumed that the enclosing feed document is the e=
ntry&#39;s<br>
&gt; source), I think that we should depart from the wording of the base At=
om<br>
&gt; Syntax here and say that when a deleted-entry element appears in a Fee=
d<br>
&gt; document other than its source feed or when it comprises a Deleted Ent=
ry<br>
&gt; Document, that the deleted-entry really MUST contain an atom:source.<b=
r>
&gt;<br>
<br>
</div>I disagree. There may be no source feed at all... and therefore no<br=
>
reason for atom:source<br></blockquote><div>=A0</div><div>You are, of cours=
e, correct. How about saying that &quot;if there is a source feed, you MUST=
 provide an atom:source&quot; ???</div><div>=A0</div><blockquote class=3D"g=
mail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-l=
eft:1ex;">

<div class=3D"im"><br>
Personally, I would be very pleased if you could add some non-normative tex=
t<br>
&gt; that makes it clear that a deleted-entry is &quot;informational&quot; =
rather than<br>
&gt; &quot;imperative.&quot; I am concerned that we will see people complai=
ning and<br>
&gt; potentially even suing in court, when some service fails to &quot;dele=
te&quot; some<br>
&gt; entry that is particularly embarrassing or that otherwise continues to=
<br>
&gt; distribute information that some publisher would prefer to have remove=
d from<br>
&gt; the system. To those of us close to this issue, it may be obvious that=
 a<br>
&gt; standard like this cannot impose legally enforceable requirements on p=
eople,<br>
&gt; however, we need to recognize that the world into which our work flows=
 is<br>
&gt; one populated not only by those of good will and knowledge but also by=
<br>
&gt; idiots, twits, and litigious fools... It is best to preemptively disab=
le or<br>
&gt; mute some of the inevitable silliness by ensuring that the standard it=
self<br>
&gt; tells the fools to stifle themselves... (In slightly more polite terms=
, of<br>
&gt; course...)<br>
<br>
</div>Agreed.<br>
<div class=3D"im"><br>
&gt; bob wyman<br>
&gt; On Mon, Jun 7, 2010 at 11:18 PM, James Snell &lt;<a href=3D"mailto:jas=
nell@gmail.com">jasnell@gmail.com</a>&gt; wrote:<br>
&gt;&gt;<br>
&gt;&gt; Ok, looking over the Atom Tombstones draft, I cannot see any furth=
er<br>
&gt;&gt; edits that need to be made. Is it done? Ready to push for last cal=
l?<br>
&gt;&gt;<br>
&gt;&gt; --<br>
&gt;&gt; - James Snell<br>
&gt;&gt; =A0<a href=3D"http://www.snellspace.com" target=3D"_blank">http://=
www.snellspace.com</a><br>
&gt;&gt; =A0<a href=3D"mailto:jasnell@gmail.com">jasnell@gmail.com</a><br>
&gt;&gt;<br>
&gt;<br>
&gt;<br>
<br>
<br>
<br>
</div>--<br>
<div><div></div><div class=3D"h5">- James Snell<br>
 =A0<a href=3D"http://www.snellspace.com" target=3D"_blank">http://www.snel=
lspace.com</a><br>
 =A0<a href=3D"mailto:jasnell@gmail.com">jasnell@gmail.com</a><br>
</div></div></blockquote></div><br>

--0016368e325d39e99504889da666--


From owner-atom-syntax@mail.imc.org  Wed Jun  9 12:18:22 2010
Return-Path: <owner-atom-syntax@mail.imc.org>
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 03C543A6857 for <ietfarch-atompub-archive@core3.amsl.com>; Wed,  9 Jun 2010 12:18:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.777
X-Spam-Level: *
X-Spam-Status: No, score=1.777 tagged_above=-999 required=5 tests=[BAYES_50=0.001, FM_FORGED_GMAIL=0.622, HELO_MISMATCH_COM=0.553, HTML_MESSAGE=0.001, J_CHICKENPOX_46=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 qE1ZZRB+bUua for <ietfarch-atompub-archive@core3.amsl.com>; Wed,  9 Jun 2010 12:18:21 -0700 (PDT)
Received: from hoffman.proper.com (Hoffman.Proper.COM [207.182.41.81]) by core3.amsl.com (Postfix) with ESMTP id 3BD323A6869 for <atompub-archive@ietf.org>; Wed,  9 Jun 2010 12:18:21 -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 o59JEUhU094028 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 9 Jun 2010 12:14:30 -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 o59JEUTj094027; Wed, 9 Jun 2010 12:14:30 -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-f180.google.com (mail-yw0-f180.google.com [209.85.211.180]) by hoffman.proper.com (8.14.4/8.14.3) with ESMTP id o59JETMA094020 for <atom-syntax@imc.org>; Wed, 9 Jun 2010 12:14:30 -0700 (MST) (envelope-from bobwyman@gmail.com)
Received: by ywh10 with SMTP id 10so6589596ywh.18 for <atom-syntax@imc.org>; Wed, 09 Jun 2010 12:14:27 -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=ZAOWm2fFNNJ5mTnUU628/g/TAC8vuHpTTNtmH6oNbBg=; b=mrJqcNnO/sq4gyVKHS0gmhA6Yj5bZ7uSmaExPuEV2sMx1G3khCw38t5AMUBSLvirfr U/KigzjjSE8x7k5TgKHMtsA/Z3GIZbhf+kFgeJnL2DpR7ZAzlKmpSQYX0QkCRmu+Z3y/ UHTkOx8uKNcxUp1vdZTRQvh2S5B1iZe6Js7co=
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=uvdf72jqjuZ0kefwqlVEC61JYwRRcVUngzOiOf21hxIZtiMDwmPVZy786IlphjTY9/ /oE8F6OkIBIafY+A48uGktt+btJPG6w0wDyyNmN//uzu/0ioMx1hwx/vgq+CH6PbYKXo /6wIo6T1tl0lm+7NOXTWkwoW7uUJfsUAKFEKg=
MIME-Version: 1.0
Received: by 10.101.2.7 with SMTP id e7mr18795970ani.79.1276110867264; Wed, 09  Jun 2010 12:14:27 -0700 (PDT)
Received: by 10.100.119.16 with HTTP; Wed, 9 Jun 2010 12:14:27 -0700 (PDT)
In-Reply-To: <AANLkTil9wH9e7VcujYhNKT90uylJCI_Axzu4BFCP6PHv@mail.gmail.com>
References: <AANLkTin26zp1aOkcQO3q8YcLa8TjiK6BMrNFYCCmFaUt@mail.gmail.com> <AANLkTil2ZmirR6iGsRL6-XWFvTF5kmY_AVRZAWnbVzB8@mail.gmail.com> <AANLkTimCAw34bvO-QKNmwU7SpjTw71mk2PYOnnpMCe9r@mail.gmail.com> <AANLkTil14wmzRUV93Uk5ILyGa2T6Omp3ogz9R2fGOw0o@mail.gmail.com> <AANLkTil9wH9e7VcujYhNKT90uylJCI_Axzu4BFCP6PHv@mail.gmail.com>
Date: Wed, 9 Jun 2010 15:14:27 -0400
X-Google-Sender-Auth: r_hfFe7SjcjNB7ykDcyVfaMZ2y0
Message-ID: <AANLkTik63QFufZJ042VaosX6iI_JPtwy1Kc7R1Up2-W6@mail.gmail.com>
Subject: Re: Atom Tombstones Done?
From: Bob Wyman <bob@wyman.us>
To: James Snell <jasnell@gmail.com>
Cc: Atom Syntax <atom-syntax@imc.org>
Content-Type: multipart/alternative; boundary=0016368e325deff67a04889db6de
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>

--0016368e325deff67a04889db6de
Content-Type: text/plain; charset=ISO-8859-1

Great. LGTM -- assuming those changes.

bob wyman

On Wed, Jun 9, 2010 at 3:13 PM, James Snell <jasnell@gmail.com> wrote:

> On Wed, Jun 9, 2010 at 12:09 PM, Bob Wyman <bob@wyman.us> wrote:
> >
> >> [snip]
> >> I disagree. There may be no source feed at all... and therefore no
> >> reason for atom:source
> >
> >
> > You are, of course, correct. How about saying that "if there is a source
> > feed, you MUST provide an atom:source" ???
> >
> >>
>
> That works for me.
>

--0016368e325deff67a04889db6de
Content-Type: text/html; charset=ISO-8859-1

Great. LGTM -- assuming those changes.<div><br></div><div>bob wyman<br><br><div class="gmail_quote">On Wed, Jun 9, 2010 at 3:13 PM, James Snell <span dir="ltr">&lt;<a href="mailto:jasnell@gmail.com">jasnell@gmail.com</a>&gt;</span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">On Wed, Jun 9, 2010 at 12:09 PM, Bob Wyman &lt;<a href="mailto:bob@wyman.us">bob@wyman.us</a>&gt; wrote:<br>
&gt;<br>
&gt;&gt; [snip]<br>
<div class="im">&gt;&gt; I disagree. There may be no source feed at all... and therefore no<br>
&gt;&gt; reason for atom:source<br>
&gt;<br>
&gt;<br>
&gt; You are, of course, correct. How about saying that &quot;if there is a source<br>
&gt; feed, you MUST provide an atom:source&quot; ???<br>
&gt;<br>
&gt;&gt;<br>
<br>
</div>That works for me.<br>
</blockquote></div><br></div>

--0016368e325deff67a04889db6de--


From owner-atom-syntax@mail.imc.org  Wed Jun  9 12:24:09 2010
Return-Path: <owner-atom-syntax@mail.imc.org>
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 D57933A688B for <ietfarch-atompub-archive@core3.amsl.com>; Wed,  9 Jun 2010 12:24:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.004
X-Spam-Level: *
X-Spam-Status: No, score=1.004 tagged_above=-999 required=5 tests=[AWL=-0.150, BAYES_50=0.001, HELO_MISMATCH_COM=0.553, J_CHICKENPOX_46=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 WtxVVMpICqLp for <ietfarch-atompub-archive@core3.amsl.com>; Wed,  9 Jun 2010 12:24:08 -0700 (PDT)
Received: from hoffman.proper.com (Hoffman.Proper.COM [207.182.41.81]) by core3.amsl.com (Postfix) with ESMTP id D9F003A67E7 for <atompub-archive@ietf.org>; Wed,  9 Jun 2010 12:24:08 -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 o59JK6Yq094489 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 9 Jun 2010 12:20:07 -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 o59JK6NQ094488; Wed, 9 Jun 2010 12:20:06 -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-px0-f171.google.com (mail-px0-f171.google.com [209.85.212.171]) by hoffman.proper.com (8.14.4/8.14.3) with ESMTP id o59JK6YD094483 for <atom-syntax@imc.org>; Wed, 9 Jun 2010 12:20:06 -0700 (MST) (envelope-from jasnell@gmail.com)
Received: by pxi13 with SMTP id 13so665511pxi.16 for <atom-syntax@imc.org>; Wed, 09 Jun 2010 12:20:02 -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=gAxrMLW3MGZos7avbQ3UAF3wnKhPsV1IYzQ3/y7VGpk=; b=cO+pxyVT3G4sKTNe//H2N07hQQx7PG7fFRxGQGZvFBPUxXZ35sFpd38V9yk7X64GJz NzknjZObNVP0lz8FzN394CQLnPaFa8AcsIWMd0NlSJbfHkF7mLuX05zUCLZwcC+9j4V8 2k/jftiiBT5KLmugkT2aYnXmSlICYoFvkBCoQ=
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=FyAeUVa6+IKNAujQMr+uvhGlHyvfy2ntfrjMb1+LgB+w/1PAA+bI8bH0VmUrjWsECX rGxFUJGsv90SSM2yotmmBbG6S+j2EFETkOWJetJD+FKZjyW0YwUfTWHno8+KIQbfk5Nn 0l75Fox+g6hfEa2bjNwXZ+1RQScI9CO+0hbwg=
MIME-Version: 1.0
Received: by 10.224.106.18 with SMTP id v18mr1004008qao.172.1276111201318;  Wed, 09 Jun 2010 12:20:01 -0700 (PDT)
Received: by 10.229.81.78 with HTTP; Wed, 9 Jun 2010 12:20:00 -0700 (PDT)
In-Reply-To: <AANLkTik63QFufZJ042VaosX6iI_JPtwy1Kc7R1Up2-W6@mail.gmail.com>
References: <AANLkTin26zp1aOkcQO3q8YcLa8TjiK6BMrNFYCCmFaUt@mail.gmail.com> <AANLkTil2ZmirR6iGsRL6-XWFvTF5kmY_AVRZAWnbVzB8@mail.gmail.com> <AANLkTimCAw34bvO-QKNmwU7SpjTw71mk2PYOnnpMCe9r@mail.gmail.com> <AANLkTil14wmzRUV93Uk5ILyGa2T6Omp3ogz9R2fGOw0o@mail.gmail.com> <AANLkTil9wH9e7VcujYhNKT90uylJCI_Axzu4BFCP6PHv@mail.gmail.com> <AANLkTik63QFufZJ042VaosX6iI_JPtwy1Kc7R1Up2-W6@mail.gmail.com>
Date: Wed, 9 Jun 2010 12:20:00 -0700
Message-ID: <AANLkTilt4IIc_T4e-6tcuv5Wt5xZdFSvuTx8AS1SUjlS@mail.gmail.com>
Subject: Re: Atom Tombstones Done?
From: James Snell <jasnell@gmail.com>
To: Bob Wyman <bob@wyman.us>
Cc: Atom Syntax <atom-syntax@imc.org>
Content-Type: text/plain; charset=ISO-8859-1
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>

Changes made. will hold off posting draft -10 until I'm sure there are
no further quick changes.

On Wed, Jun 9, 2010 at 12:14 PM, Bob Wyman <bob@wyman.us> wrote:
> Great. LGTM -- assuming those changes.
> bob wyman
>
> On Wed, Jun 9, 2010 at 3:13 PM, James Snell <jasnell@gmail.com> wrote:
>>
>> On Wed, Jun 9, 2010 at 12:09 PM, Bob Wyman <bob@wyman.us> wrote:
>> >
>> >> [snip]
>> >> I disagree. There may be no source feed at all... and therefore no
>> >> reason for atom:source
>> >
>> >
>> > You are, of course, correct. How about saying that "if there is a source
>> > feed, you MUST provide an atom:source" ???
>> >
>> >>
>>
>> That works for me.
>
>



-- 
- James Snell
  http://www.snellspace.com
  jasnell@gmail.com


From owner-atom-syntax@mail.imc.org  Thu Jun 10 05:39:07 2010
Return-Path: <owner-atom-syntax@mail.imc.org>
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 217AC3A6836 for <ietfarch-atompub-archive@core3.amsl.com>; Thu, 10 Jun 2010 05:39:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.776
X-Spam-Level: *
X-Spam-Status: No, score=1.776 tagged_above=-999 required=5 tests=[BAYES_50=0.001, 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 1prPrvsYYXBb for <ietfarch-atompub-archive@core3.amsl.com>; Thu, 10 Jun 2010 05:39:06 -0700 (PDT)
Received: from hoffman.proper.com (Hoffman.Proper.COM [207.182.41.81]) by core3.amsl.com (Postfix) with ESMTP id 39A9D3A6A0C for <atompub-archive@ietf.org>; Thu, 10 Jun 2010 05:38:08 -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 o5ACUvif054885 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 10 Jun 2010 05:30:57 -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 o5ACUvNx054884; Thu, 10 Jun 2010 05:30:57 -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 o5ACUuDa054877 for <atom-syntax@imc.org>; Thu, 10 Jun 2010 05:30:56 -0700 (MST) (envelope-from mo@nevali.net)
Received: from mail-bw0-f43.google.com (mail-bw0-f43.google.com [209.85.214.43]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by nxauth1.nexgenta.com (Postfix) with ESMTP id 1A64A1AA9C for <atom-syntax@imc.org>; Thu, 10 Jun 2010 12:30:55 +0000 (UTC)
Received: by bwz3 with SMTP id 3so2199582bwz.16 for <atom-syntax@imc.org>; Thu, 10 Jun 2010 05:30:54 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.204.83.78 with SMTP id e14mr86586bkl.136.1276173054533; Thu,  10 Jun 2010 05:30:54 -0700 (PDT)
Received: by 10.204.36.74 with HTTP; Thu, 10 Jun 2010 05:30:54 -0700 (PDT)
Date: Thu, 10 Jun 2010 13:30:54 +0100
Message-ID: <AANLkTintAESgi33LdLXd-QDmsm7iuhBlojm4a4b4n7_s@mail.gmail.com>
Subject: Link extensions-related: link availability/expiry?
From: Mo McRoberts <mo@nevali.net>
To: atom-syntax@imc.org
Content-Type: text/plain; charset=UTF-8
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>

Hi list,

This isn't *directly* relevant to the link extensions draft, but does
lie along the same lines.

I'm looking for a pair of attributes which can be applied to an
atom:link which will indicate "not available until" and "not available
after" with regards to the linked resource. Does anybody know of
anything vaguely (be it official or de facto) standard?

I have a specific use-case in mind (indicating the availability of a
TV or radio programme for on-demand/'catch-up' playback), but I'm sure
there will likely be others, so if there's nothing out there
already...

Any pointers would be much appreciated!

M.


From owner-atom-syntax@mail.imc.org  Thu Jun 10 07:50:05 2010
Return-Path: <owner-atom-syntax@mail.imc.org>
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 E402F28C0DF for <ietfarch-atompub-archive@core3.amsl.com>; Thu, 10 Jun 2010 07:50:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.054
X-Spam-Level: *
X-Spam-Status: No, score=1.054 tagged_above=-999 required=5 tests=[AWL=-0.100, BAYES_50=0.001, 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 Q9KUj3OHcdaX for <ietfarch-atompub-archive@core3.amsl.com>; Thu, 10 Jun 2010 07:50:04 -0700 (PDT)
Received: from hoffman.proper.com (Hoffman.Proper.COM [207.182.41.81]) by core3.amsl.com (Postfix) with ESMTP id 125043A6987 for <atompub-archive@ietf.org>; Thu, 10 Jun 2010 07:50:00 -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 o5AEi8cn064366 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 10 Jun 2010 07:44:08 -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 o5AEi8KD064365; Thu, 10 Jun 2010 07:44:08 -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-f180.google.com (mail-yw0-f180.google.com [209.85.211.180]) by hoffman.proper.com (8.14.4/8.14.3) with ESMTP id o5AEi7XP064360 for <atom-syntax@imc.org>; Thu, 10 Jun 2010 07:44:08 -0700 (MST) (envelope-from jasnell@gmail.com)
Received: by ywh10 with SMTP id 10so14757ywh.18 for <atom-syntax@imc.org>; Thu, 10 Jun 2010 07:44:07 -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=atGpKnERZAzL+9aChjfJxIYDzcRDv8zi2uL55bfBi5o=; b=oVa23+urqnEbDnCjaXD0KMBcY03gEhD6L6FQ7N6rImyLqJ+zVQQZ+STXMkZyfBu76l 5VqJYdCNKLz5rCvo0jEupkq0aNw37CP0OkxGJCny3y0Av56VF+YOMBHX6Y4MDD+PLi1b ypj2m1KWkjuCiX3NH/iZVHaAUjunEzwKbhcCg=
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=j3ajXe3jk4/OKh6we0W40zu55JqbqqQlDaO9/fiQdxc/djNTLUTq0OZsJ6U7BG21CA aRbU7VEs7aKWqoUxMH0r2wwikSSORGJUXidZ0nWSMyjJRP/7nOcSnAs0EwMZsobLazF3 krPrmEChbeLSnbu6IaHCvC+oq6CdIxkrHASYI=
MIME-Version: 1.0
Received: by 10.224.105.80 with SMTP id s16mr247175qao.337.1276181038410; Thu,  10 Jun 2010 07:43:58 -0700 (PDT)
Received: by 10.229.81.78 with HTTP; Thu, 10 Jun 2010 07:43:58 -0700 (PDT)
In-Reply-To: <AANLkTintAESgi33LdLXd-QDmsm7iuhBlojm4a4b4n7_s@mail.gmail.com>
References: <AANLkTintAESgi33LdLXd-QDmsm7iuhBlojm4a4b4n7_s@mail.gmail.com>
Date: Thu, 10 Jun 2010 07:43:58 -0700
Message-ID: <AANLkTilb9Reqyc34YFYkEwcpKgh2vVuCDeKqnYvPg356@mail.gmail.com>
Subject: Re: Link extensions-related: link availability/expiry?
From: James Snell <jasnell@gmail.com>
To: Mo McRoberts <mo@nevali.net>
Cc: atom-syntax@imc.org
Content-Type: text/plain; charset=ISO-8859-1
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>

There currently are no such extensions defined anywhere as far as I
know. A few years back I proposed a 'expires' extension element for
Atom entries that didn't get any traction. It would be a simple
matter, I think to define a pair of notbefore and notafter attributes
for the atom:link...

  <link rel="..." href="..."
    notbefore="2010-06-10T12:00:00-08:00"
    notafter="2010-06-10T01:00:00-08:00" />

I would have no problem including these in the link extensions spec if
the supporting use cases are sufficiently generic.

However, it might make more sense to define these as extension
elements to the link or entry... hard to say for sure without knowing
more about the specific use case and how the your entries are being
modeled.

- James

On Thu, Jun 10, 2010 at 5:30 AM, Mo McRoberts <mo@nevali.net> wrote:
>
> Hi list,
>
> This isn't *directly* relevant to the link extensions draft, but does
> lie along the same lines.
>
> I'm looking for a pair of attributes which can be applied to an
> atom:link which will indicate "not available until" and "not available
> after" with regards to the linked resource. Does anybody know of
> anything vaguely (be it official or de facto) standard?
>
> I have a specific use-case in mind (indicating the availability of a
> TV or radio programme for on-demand/'catch-up' playback), but I'm sure
> there will likely be others, so if there's nothing out there
> already...
>
> Any pointers would be much appreciated!
>
> M.
>
>



-- 
- James Snell
  http://www.snellspace.com
  jasnell@gmail.com


From owner-atom-syntax@mail.imc.org  Thu Jun 10 08:06:12 2010
Return-Path: <owner-atom-syntax@mail.imc.org>
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 E8EEB28C0F6 for <ietfarch-atompub-archive@core3.amsl.com>; Thu, 10 Jun 2010 08:06:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.776
X-Spam-Level: *
X-Spam-Status: No, score=1.776 tagged_above=-999 required=5 tests=[BAYES_50=0.001, FM_FORGED_GMAIL=0.622, HELO_MISMATCH_COM=0.553, J_CHICKENPOX_45=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 p5PhIja-U0Ms for <ietfarch-atompub-archive@core3.amsl.com>; Thu, 10 Jun 2010 08:06:08 -0700 (PDT)
Received: from hoffman.proper.com (Hoffman.Proper.COM [207.182.41.81]) by core3.amsl.com (Postfix) with ESMTP id 9ED583A6983 for <atompub-archive@ietf.org>; Thu, 10 Jun 2010 08:06:08 -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 o5AF1WnO065529 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 10 Jun 2010 08:01:32 -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 o5AF1WfT065528; Thu, 10 Jun 2010 08:01:32 -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 o5AF1Vww065523 for <atom-syntax@imc.org>; Thu, 10 Jun 2010 08:01:31 -0700 (MST) (envelope-from mo@nevali.net)
Received: from mail-fx0-f43.google.com (mail-fx0-f43.google.com [209.85.161.43]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by nxauth1.nexgenta.com (Postfix) with ESMTP id B8D2F1AAB2 for <atom-syntax@imc.org>; Thu, 10 Jun 2010 15:01:30 +0000 (UTC)
Received: by fxm10 with SMTP id 10so24590fxm.16 for <atom-syntax@imc.org>; Thu, 10 Jun 2010 08:01:30 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.204.79.214 with SMTP id q22mr231273bkk.109.1276182089906; Thu,  10 Jun 2010 08:01:29 -0700 (PDT)
Received: by 10.204.36.74 with HTTP; Thu, 10 Jun 2010 08:01:29 -0700 (PDT)
In-Reply-To: <AANLkTilb9Reqyc34YFYkEwcpKgh2vVuCDeKqnYvPg356@mail.gmail.com>
References: <AANLkTintAESgi33LdLXd-QDmsm7iuhBlojm4a4b4n7_s@mail.gmail.com> <AANLkTilb9Reqyc34YFYkEwcpKgh2vVuCDeKqnYvPg356@mail.gmail.com>
Date: Thu, 10 Jun 2010 16:01:29 +0100
Message-ID: <AANLkTinN-lOW2Z_Nw36CYZ0qiXXTh-OEK3ZeT-C2B4Ph@mail.gmail.com>
Subject: Re: Link extensions-related: link availability/expiry?
From: Mo McRoberts <mo@nevali.net>
To: James Snell <jasnell@gmail.com>
Cc: atom-syntax@imc.org
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by hoffman.proper.com id o5AF1Vww065524
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>

On Thu, Jun 10, 2010 at 15:43, James Snell <jasnell@gmail.com> wrote:

> Â <link rel="..." href="..."
> Â  Â notbefore="2010-06-10T12:00:00-08:00"
> Â  Â notafter="2010-06-10T01:00:00-08:00" />

'notbefore' and 'notafter' are pretty ideal.

> I would have no problem including these in the link extensions spec if
> the supporting use cases are sufficiently generic.
>
> However, it might make more sense to define these as extension
> elements to the link or entry... hard to say for sure without knowing
> more about the specific use case and how the your entries are being
> modeled.

Okay, bit of background: building a feed which contains information
about TV (or radio) programmes. there's some extra stuff in there
relating them to actual broadcasts (RFC4078 crid:// URIs), but
principally, it boils down to the usual atom:entry elements - title,
summary, id, published timestamp and links to resources.

What I'd like to include in this feed is a particular class of link
which refers to a resource (or set of resources of different types)
where the programme can be downloaded or streamed, generally for a
limited period - usually starting about half an hour after the on-air
broadcast concludes (at some point along the way I'll need to come up
with some link relations to indicate 'on-demand' vs. 'linear
broadcast', but that's a separate issue entirely).

The user agents can be quite a lot smarter if they can determine from
the feed whether a given programme is available for on-demand
viewing/listening at a given point in time  (not all will be, due to
rights constraints); if so, how long the user has access to the
resource, and if not, whether it will be for the future or if the
window has already passed.

I must confess I haven't thought deeply about wider applications of a
notbefore/notafter - obviously limited-time availability for resources
isn't particularly uncommon, but the intersection of those and the set
of resources you want to appear in a feed might well be a different
matter.

I'm happy enough to roll my own extension for this, but if it's
something generic enough to end up in link-extensions, I'd obviously
rather see that happen.

Cheers,

M.


From owner-atom-syntax@mail.imc.org  Thu Jun 10 08:46:45 2010
Return-Path: <owner-atom-syntax@mail.imc.org>
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 E6BFF28C12F for <ietfarch-atompub-archive@core3.amsl.com>; Thu, 10 Jun 2010 08:46:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.154
X-Spam-Level: *
X-Spam-Status: No, score=1.154 tagged_above=-999 required=5 tests=[AWL=0.600, BAYES_50=0.001, 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 QZ5N6Ued3CxK for <ietfarch-atompub-archive@core3.amsl.com>; Thu, 10 Jun 2010 08:46:44 -0700 (PDT)
Received: from hoffman.proper.com (Hoffman.Proper.COM [207.182.41.81]) by core3.amsl.com (Postfix) with ESMTP id 321693A695F for <atompub-archive@ietf.org>; Thu, 10 Jun 2010 08:46:44 -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 o5AFgWWV068336 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 10 Jun 2010 08:42:32 -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 o5AFgWox068335; Thu, 10 Jun 2010 08:42:32 -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-gw0-f43.google.com (mail-gw0-f43.google.com [74.125.83.43]) by hoffman.proper.com (8.14.4/8.14.3) with ESMTP id o5AFgVnN068330 for <atom-syntax@imc.org>; Thu, 10 Jun 2010 08:42:32 -0700 (MST) (envelope-from jasnell@gmail.com)
Received: by gwb20 with SMTP id 20so44537gwb.16 for <atom-syntax@imc.org>; Thu, 10 Jun 2010 08:42:31 -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=WKhEQIdIXUwCNm3RqcBvH3l3AX7DUPyYMZ5qh+ITS28=; b=Z9Pf0DgJTpkHhIEtCPFLEzsw0cUVj+7d1BB2pUg0Sd9ErOhsfhELe/v4ScKSx5xw1k g+/Jb9qwTIdBAToRRAVt8wu5EpyYlrG57m5yuXYyYmRPs38hVxMSSBQAz/2iP1lMbL4a 4/yK5Ry56/45NJs5fgRh4/9FygQH4xNdm9cp0=
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=MQo1jh19AWs8bqXAW+yc0/gMelKcy4Ddu0yyxqUzgJcJzla/7ppg5BPZvDFUWU5H/E EX+4N3OzXddlO84/5dhRlt2BUl8niZH4nTX3FyPJ64MGaa1jqC3+pAm48plO40zcUlvp 2fhVhorv3NV4grIXju1kdmQuqSkxyIxU05iGk=
MIME-Version: 1.0
Received: by 10.224.43.146 with SMTP id w18mr359321qae.307.1276184546964; Thu,  10 Jun 2010 08:42:26 -0700 (PDT)
Received: by 10.229.81.78 with HTTP; Thu, 10 Jun 2010 08:42:26 -0700 (PDT)
In-Reply-To: <AANLkTinN-lOW2Z_Nw36CYZ0qiXXTh-OEK3ZeT-C2B4Ph@mail.gmail.com>
References: <AANLkTintAESgi33LdLXd-QDmsm7iuhBlojm4a4b4n7_s@mail.gmail.com> <AANLkTilb9Reqyc34YFYkEwcpKgh2vVuCDeKqnYvPg356@mail.gmail.com> <AANLkTinN-lOW2Z_Nw36CYZ0qiXXTh-OEK3ZeT-C2B4Ph@mail.gmail.com>
Date: Thu, 10 Jun 2010 08:42:26 -0700
Message-ID: <AANLkTikR2nF6oj6TaBwDtanx96n1EW6x2CZ1ljy5WaXK@mail.gmail.com>
Subject: Re: Link extensions-related: link availability/expiry?
From: James Snell <jasnell@gmail.com>
To: Mo McRoberts <mo@nevali.net>
Cc: atom-syntax@imc.org
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 o5AFgWnN068331
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>

This kind of time boxing certainly isn't unique... going to have to
give this one a bit of thought. Including these in the link extensions
draft would be trivial, just not sure if I'd be justified in doing so.


On Thu, Jun 10, 2010 at 8:01 AM, Mo McRoberts <mo@nevali.net> wrote:
> On Thu, Jun 10, 2010 at 15:43, James Snell <jasnell@gmail.com> wrote:
>
>>  <link rel="..." href="..."
>>    notbefore="2010-06-10T12:00:00-08:00"
>>    notafter="2010-06-10T01:00:00-08:00" />
>
> 'notbefore' and 'notafter' are pretty ideal.
> [snip]


From owner-atom-syntax@mail.imc.org  Thu Jun 10 09:09:53 2010
Return-Path: <owner-atom-syntax@mail.imc.org>
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 D20523A67A2 for <ietfarch-atompub-archive@core3.amsl.com>; Thu, 10 Jun 2010 09:09:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.477
X-Spam-Level: *
X-Spam-Status: No, score=1.477 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_50=0.001, FM_FORGED_GMAIL=0.622, HELO_MISMATCH_COM=0.553, HTML_MESSAGE=0.001, J_CHICKENPOX_45=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 B1XrYwxJFsJK for <ietfarch-atompub-archive@core3.amsl.com>; Thu, 10 Jun 2010 09:09:50 -0700 (PDT)
Received: from hoffman.proper.com (Hoffman.Proper.COM [207.182.41.81]) by core3.amsl.com (Postfix) with ESMTP id 8AE393A679F for <atompub-archive@ietf.org>; Thu, 10 Jun 2010 09:09:48 -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 o5AG4C7O069891 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 10 Jun 2010 09:04:12 -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 o5AG4CTw069890; Thu, 10 Jun 2010 09:04:12 -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-pv0-f171.google.com (mail-pv0-f171.google.com [74.125.83.171]) by hoffman.proper.com (8.14.4/8.14.3) with ESMTP id o5AG4BnX069882 for <atom-syntax@imc.org>; Thu, 10 Jun 2010 09:04:11 -0700 (MST) (envelope-from bobwyman@gmail.com)
Received: by pva4 with SMTP id 4so54463pva.16 for <atom-syntax@imc.org>; Thu, 10 Jun 2010 09:04:10 -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=D4aBykWB7VK9hVxI+gdCwLAD09GBI+hwsAsMmjBnCkA=; b=RnVKY1pFFGIb7vYd4n+MiV2Y5YAyvzYg7QpSEOrBg+tBQayVGS/lM6rjgcfzphPs5R ziPMUrygDsj8JUc/1RWW03OS3r5QKK5VCkPAxH88vYm8Dp6Y1ptcNc0cIywfTTc5LbBo Ktszqlmf1hdTn/FaI2knTEdlbvTv0vL5pkmKY=
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=LnhIKiWMkDfQH1Lkoau0dMprILuvEMYd34VDdWJOa3J1VSmfea3WGYfS8CVR6SnQUt zrB4TjYhE4UQBLwGxiDWH7cfeUTYOa8ZBj7WsqBPrjawkblitZqY1CWS7fHAsOdyJqUi 7NYIItOUpsxhk9qxo8JWh4WPEMFZU3HXE621s=
MIME-Version: 1.0
Received: by 10.115.135.32 with SMTP id m32mr332263wan.47.1276185850510; Thu,  10 Jun 2010 09:04:10 -0700 (PDT)
Received: by 10.114.202.19 with HTTP; Thu, 10 Jun 2010 09:04:10 -0700 (PDT)
In-Reply-To: <AANLkTinN-lOW2Z_Nw36CYZ0qiXXTh-OEK3ZeT-C2B4Ph@mail.gmail.com>
References: <AANLkTintAESgi33LdLXd-QDmsm7iuhBlojm4a4b4n7_s@mail.gmail.com> <AANLkTilb9Reqyc34YFYkEwcpKgh2vVuCDeKqnYvPg356@mail.gmail.com> <AANLkTinN-lOW2Z_Nw36CYZ0qiXXTh-OEK3ZeT-C2B4Ph@mail.gmail.com>
Date: Thu, 10 Jun 2010 12:04:10 -0400
X-Google-Sender-Auth: TKmHhQDPmGTUOZ404DbWddG_G1c
Message-ID: <AANLkTimFKuTQeCDjd1TWv33Nfb6n0AxukxXGXictdUv5@mail.gmail.com>
Subject: Re: Link extensions-related: link availability/expiry?
From: Bob Wyman <bob@wyman.us>
To: Mo McRoberts <mo@nevali.net>
Cc: James Snell <jasnell@gmail.com>, atom-syntax@imc.org
Content-Type: multipart/alternative; boundary=0016e64afa46497d920488af2cc2
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>

--0016e64afa46497d920488af2cc2
Content-Type: text/plain; charset=ISO-8859-1

Simple solutions are wonderful! Unless they are simple solutions to complex
problems. The harsh reality is that for a solution to be effective, its
complexity must *at least* match the complexity of the problem solved. In
this case, the specification of time ranges is a complex problem and any
"simple" solution to it will result either in disuse (since the solution is
inadequate) of increased complexity in the future as people extend the basic
capability to handle the unaddressed complexity of the problem domain.
Personally, in the over 30 years I've spent in this business, I've seen
uncounted attempts to address the "time range" problem simply. Each effort
begins with someone proposing the "simple" solution of "start" and "end"
times. But, then fairly soon thereafter, someone appears with the
requirement for discontinuous time ranges... i.e. The event occurs from
8:00pm to 9:00pm Eastern Standard Time on Tuesday evenings during the months
of September through December unless it is the first Tuesday in November
during a year that is evenly divisible by 2, in which case, the broadcast
will occur one hour earlier. (i.e. time shifting to compensate for poll
closing during US elections...)

Rather than defining something new, I would strongly encourage you to take a
long hard look at the xCal Draft and attempt to ensure that whatever is done
here, if anything, is compatible with that specification. The ideal would be
to define these attributes as incorporations of the xCal methods rather than
to define something entirely new.

See: http://tools.ietf.org/html/draft-daboo-et-al-icalendar-in-xml-04

The "time specification" or calendar problem is terribly vexing and
difficult. Please, don't try to reinvent the wheel...

bob wyman



On Thu, Jun 10, 2010 at 11:01 AM, Mo McRoberts <mo@nevali.net> wrote:

>
> On Thu, Jun 10, 2010 at 15:43, James Snell <jasnell@gmail.com> wrote:
>
> >  <link rel="..." href="..."
> >    notbefore="2010-06-10T12:00:00-08:00"
> >    notafter="2010-06-10T01:00:00-08:00" />
>
> 'notbefore' and 'notafter' are pretty ideal.
>
> > I would have no problem including these in the link extensions spec if
> > the supporting use cases are sufficiently generic.
> >
> > However, it might make more sense to define these as extension
> > elements to the link or entry... hard to say for sure without knowing
> > more about the specific use case and how the your entries are being
> > modeled.
>
> Okay, bit of background: building a feed which contains information
> about TV (or radio) programmes. there's some extra stuff in there
> relating them to actual broadcasts (RFC4078 crid:// URIs), but
> principally, it boils down to the usual atom:entry elements - title,
> summary, id, published timestamp and links to resources.
>
> What I'd like to include in this feed is a particular class of link
> which refers to a resource (or set of resources of different types)
> where the programme can be downloaded or streamed, generally for a
> limited period - usually starting about half an hour after the on-air
> broadcast concludes (at some point along the way I'll need to come up
> with some link relations to indicate 'on-demand' vs. 'linear
> broadcast', but that's a separate issue entirely).
>
> The user agents can be quite a lot smarter if they can determine from
> the feed whether a given programme is available for on-demand
> viewing/listening at a given point in time  (not all will be, due to
> rights constraints); if so, how long the user has access to the
> resource, and if not, whether it will be for the future or if the
> window has already passed.
>
> I must confess I haven't thought deeply about wider applications of a
> notbefore/notafter - obviously limited-time availability for resources
> isn't particularly uncommon, but the intersection of those and the set
> of resources you want to appear in a feed might well be a different
> matter.
>
> I'm happy enough to roll my own extension for this, but if it's
> something generic enough to end up in link-extensions, I'd obviously
> rather see that happen.
>
> Cheers,
>
> M.
>
>

--0016e64afa46497d920488af2cc2
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Simple solutions are wonderful! Unless they are simple solutions to complex=
 problems. The harsh reality is that for a solution to be effective, its co=
mplexity must *at least* match the complexity of the problem solved. In thi=
s case, the specification of time ranges is a complex problem and any &quot=
;simple&quot; solution to it will result either in disuse (since the soluti=
on is inadequate) of increased complexity in the future as people extend th=
e basic capability to handle the unaddressed complexity of the problem doma=
in. Personally, in the over 30 years I&#39;ve spent in this business, I&#39=
;ve seen uncounted attempts to address the &quot;time range&quot; problem s=
imply. Each effort begins with someone proposing the &quot;simple&quot; sol=
ution of &quot;start&quot; and &quot;end&quot; times. But, then fairly soon=
 thereafter, someone appears with the requirement for discontinuous time ra=
nges... i.e. The event occurs from 8:00pm to 9:00pm Eastern Standard Time o=
n Tuesday evenings during the months of September through December unless i=
t is the first Tuesday in November during a year that is evenly divisible b=
y 2, in which case, the broadcast will occur one hour earlier. (i.e. time s=
hifting to compensate for poll closing during US elections...)<div>
<br></div><div>Rather than defining something new, I would strongly encoura=
ge you to take a long hard look at the xCal Draft and attempt to ensure tha=
t whatever is done here, if anything, is compatible with that specification=
. The ideal would be to define these attributes as incorporations of the xC=
al methods rather than to define something entirely new.</div>
<div><br></div><div>See:=A0<a href=3D"http://tools.ietf.org/html/draft-dabo=
o-et-al-icalendar-in-xml-04">http://tools.ietf.org/html/draft-daboo-et-al-i=
calendar-in-xml-04</a></div><div><br></div><div>The &quot;time specificatio=
n&quot; or calendar problem is terribly vexing and difficult. Please, don&#=
39;t try to reinvent the wheel...</div>
<div><br></div><div>bob wyman</div><div><br></div><meta http-equiv=3D"conte=
nt-type" content=3D"text/html; charset=3Dutf-8"><div><br><br><div class=3D"=
gmail_quote">On Thu, Jun 10, 2010 at 11:01 AM, Mo McRoberts <span dir=3D"lt=
r">&lt;<a href=3D"mailto:mo@nevali.net">mo@nevali.net</a>&gt;</span> wrote:=
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex;"><div class=3D"im"><br>
On Thu, Jun 10, 2010 at 15:43, James Snell &lt;<a href=3D"mailto:jasnell@gm=
ail.com">jasnell@gmail.com</a>&gt; wrote:<br>
<br>
&gt; =A0&lt;link rel=3D&quot;...&quot; href=3D&quot;...&quot;<br>
&gt; =A0 =A0notbefore=3D&quot;2010-06-10T12:00:00-08:00&quot;<br>
&gt; =A0 =A0notafter=3D&quot;2010-06-10T01:00:00-08:00&quot; /&gt;<br>
<br>
</div>&#39;notbefore&#39; and &#39;notafter&#39; are pretty ideal.<br>
<div class=3D"im"><br>
&gt; I would have no problem including these in the link extensions spec if=
<br>
&gt; the supporting use cases are sufficiently generic.<br>
&gt;<br>
&gt; However, it might make more sense to define these as extension<br>
&gt; elements to the link or entry... hard to say for sure without knowing<=
br>
&gt; more about the specific use case and how the your entries are being<br=
>
&gt; modeled.<br>
<br>
</div>Okay, bit of background: building a feed which contains information<b=
r>
about TV (or radio) programmes. there&#39;s some extra stuff in there<br>
relating them to actual broadcasts (RFC4078 crid:// URIs), but<br>
principally, it boils down to the usual atom:entry elements - title,<br>
summary, id, published timestamp and links to resources.<br>
<br>
What I&#39;d like to include in this feed is a particular class of link<br>
which refers to a resource (or set of resources of different types)<br>
where the programme can be downloaded or streamed, generally for a<br>
limited period - usually starting about half an hour after the on-air<br>
broadcast concludes (at some point along the way I&#39;ll need to come up<b=
r>
with some link relations to indicate &#39;on-demand&#39; vs. &#39;linear<br=
>
broadcast&#39;, but that&#39;s a separate issue entirely).<br>
<br>
The user agents can be quite a lot smarter if they can determine from<br>
the feed whether a given programme is available for on-demand<br>
viewing/listening at a given point in time =A0(not all will be, due to<br>
rights constraints); if so, how long the user has access to the<br>
resource, and if not, whether it will be for the future or if the<br>
window has already passed.<br>
<br>
I must confess I haven&#39;t thought deeply about wider applications of a<b=
r>
notbefore/notafter - obviously limited-time availability for resources<br>
isn&#39;t particularly uncommon, but the intersection of those and the set<=
br>
of resources you want to appear in a feed might well be a different<br>
matter.<br>
<br>
I&#39;m happy enough to roll my own extension for this, but if it&#39;s<br>
something generic enough to end up in link-extensions, I&#39;d obviously<br=
>
rather see that happen.<br>
<br>
Cheers,<br>
<font color=3D"#888888"><br>
M.<br>
<br>
</font></blockquote></div><br></div>

--0016e64afa46497d920488af2cc2--


From owner-atom-syntax@mail.imc.org  Thu Jun 10 09:16:52 2010
Return-Path: <owner-atom-syntax@mail.imc.org>
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 BC8EB3A6814 for <ietfarch-atompub-archive@core3.amsl.com>; Thu, 10 Jun 2010 09:16:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.777
X-Spam-Level: *
X-Spam-Status: No, score=1.777 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_50=0.001, FM_FORGED_GMAIL=0.622, HELO_MISMATCH_COM=0.553, HTML_MESSAGE=0.001, J_CHICKENPOX_45=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 3yswvLkn12pQ for <ietfarch-atompub-archive@core3.amsl.com>; Thu, 10 Jun 2010 09:16:51 -0700 (PDT)
Received: from hoffman.proper.com (Hoffman.Proper.COM [207.182.41.81]) by core3.amsl.com (Postfix) with ESMTP id D71203A6A1D for <atompub-archive@ietf.org>; Thu, 10 Jun 2010 09:16:44 -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 o5AGCj2l070548 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 10 Jun 2010 09:12: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 o5AGCjBL070547; Thu, 10 Jun 2010 09:12: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-pw0-f43.google.com (mail-pw0-f43.google.com [209.85.160.43]) by hoffman.proper.com (8.14.4/8.14.3) with ESMTP id o5AGCiBo070541 for <atom-syntax@imc.org>; Thu, 10 Jun 2010 09:12:45 -0700 (MST) (envelope-from bobwyman@gmail.com)
Received: by pwi9 with SMTP id 9so59454pwi.16 for <atom-syntax@imc.org>; Thu, 10 Jun 2010 09:12:44 -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=TSWBbLXqmThSO93xmgH5uejpQkcLmiMsp4/9CTr0mEU=; b=qfVeqTwdImUvKgztNAaxzKFI0tiUwWSGNLdGyPxjDvJPb90ABjS7hHRxCE45jMftk2 0gPt0WeIE8qRENWfrgLyvx9NNqGg2iIdY+5wzqzNf1C+iL9d+FpD2Av7cO5ciOFj6XlT z7DWWG6JfcXMVdaTS2/G9dH/AYH9hlM3+FXg8=
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=wAq2ba6+rpUszW406SCgYJ4GMzuNUj1xAw7wquCcqVotRaneK7jdOLUKyXt1RU4dhl P/bKdmnHCqA+5uX/CFXCLZZOdfZ2pcWDyVmxf3Iqtd4zdHTN1gW02ByAb/tvr8PzbL28 tJtueRHXqj0keF3qJmLXIGSufwLn3aPhRhlb8=
MIME-Version: 1.0
Received: by 10.114.188.30 with SMTP id l30mr322107waf.134.1276186364389; Thu,  10 Jun 2010 09:12:44 -0700 (PDT)
Received: by 10.114.202.19 with HTTP; Thu, 10 Jun 2010 09:12:44 -0700 (PDT)
In-Reply-To: <AANLkTimFKuTQeCDjd1TWv33Nfb6n0AxukxXGXictdUv5@mail.gmail.com>
References: <AANLkTintAESgi33LdLXd-QDmsm7iuhBlojm4a4b4n7_s@mail.gmail.com> <AANLkTilb9Reqyc34YFYkEwcpKgh2vVuCDeKqnYvPg356@mail.gmail.com> <AANLkTinN-lOW2Z_Nw36CYZ0qiXXTh-OEK3ZeT-C2B4Ph@mail.gmail.com> <AANLkTimFKuTQeCDjd1TWv33Nfb6n0AxukxXGXictdUv5@mail.gmail.com>
Date: Thu, 10 Jun 2010 12:12:44 -0400
X-Google-Sender-Auth: yOeWJuP0fFvcXCxVUtO8WKQJd0M
Message-ID: <AANLkTilbSx_nivjlEZQOWbnQzFFTLURELc37J7dls2mI@mail.gmail.com>
Subject: Re: Link extensions-related: link availability/expiry?
From: Bob Wyman <bob@wyman.us>
To: Mo McRoberts <mo@nevali.net>
Cc: James Snell <jasnell@gmail.com>, atom-syntax@imc.org
Content-Type: multipart/alternative; boundary=0016e64de3caeaab590488af4aea
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>

--0016e64de3caeaab590488af4aea
Content-Type: text/plain; charset=ISO-8859-1

An earlier version of the current xCal Draft included the specification of a
"link" element which was intended to bring into the calendar domain the link
element as defined by Atom. This element was removed from the current draft
as it is planned to specify it in a distinct draft. However, given that the
intention is to map what Atom provides, it would probably make sense for
folk to communicate with the authors about the proposed extensions to Atom's
link element. At the same time, it might make sense to request guidance from
the Calendar folk on how to handle the time-range attributes that are the
subject of this thread.

See the old (now removed) specification of LINK in Section 5 of the old xCal
draft (02):
http://tools.ietf.org/html/draft-daboo-et-al-icalendar-in-xml-02#section-5

<http://tools.ietf.org/html/draft-daboo-et-al-icalendar-in-xml-02#section-5>bob
wyman

On Thu, Jun 10, 2010 at 12:04 PM, Bob Wyman <bob@wyman.us> wrote:

> Simple solutions are wonderful! Unless they are simple solutions to complex
> problems. The harsh reality is that for a solution to be effective, its
> complexity must *at least* match the complexity of the problem solved. In
> this case, the specification of time ranges is a complex problem and any
> "simple" solution to it will result either in disuse (since the solution is
> inadequate) of increased complexity in the future as people extend the basic
> capability to handle the unaddressed complexity of the problem domain.
> Personally, in the over 30 years I've spent in this business, I've seen
> uncounted attempts to address the "time range" problem simply. Each effort
> begins with someone proposing the "simple" solution of "start" and "end"
> times. But, then fairly soon thereafter, someone appears with the
> requirement for discontinuous time ranges... i.e. The event occurs from
> 8:00pm to 9:00pm Eastern Standard Time on Tuesday evenings during the months
> of September through December unless it is the first Tuesday in November
> during a year that is evenly divisible by 2, in which case, the broadcast
> will occur one hour earlier. (i.e. time shifting to compensate for poll
> closing during US elections...)
>
> Rather than defining something new, I would strongly encourage you to take
> a long hard look at the xCal Draft and attempt to ensure that whatever is
> done here, if anything, is compatible with that specification. The ideal
> would be to define these attributes as incorporations of the xCal methods
> rather than to define something entirely new.
>
> See: http://tools.ietf.org/html/draft-daboo-et-al-icalendar-in-xml-04
>
> The "time specification" or calendar problem is terribly vexing and
> difficult. Please, don't try to reinvent the wheel...
>
> bob wyman
>
>
>
> On Thu, Jun 10, 2010 at 11:01 AM, Mo McRoberts <mo@nevali.net> wrote:
>
>>
>> On Thu, Jun 10, 2010 at 15:43, James Snell <jasnell@gmail.com> wrote:
>>
>> >  <link rel="..." href="..."
>> >    notbefore="2010-06-10T12:00:00-08:00"
>> >    notafter="2010-06-10T01:00:00-08:00" />
>>
>> 'notbefore' and 'notafter' are pretty ideal.
>>
>> > I would have no problem including these in the link extensions spec if
>> > the supporting use cases are sufficiently generic.
>> >
>> > However, it might make more sense to define these as extension
>> > elements to the link or entry... hard to say for sure without knowing
>> > more about the specific use case and how the your entries are being
>> > modeled.
>>
>> Okay, bit of background: building a feed which contains information
>> about TV (or radio) programmes. there's some extra stuff in there
>> relating them to actual broadcasts (RFC4078 crid:// URIs), but
>> principally, it boils down to the usual atom:entry elements - title,
>> summary, id, published timestamp and links to resources.
>>
>> What I'd like to include in this feed is a particular class of link
>> which refers to a resource (or set of resources of different types)
>> where the programme can be downloaded or streamed, generally for a
>> limited period - usually starting about half an hour after the on-air
>> broadcast concludes (at some point along the way I'll need to come up
>> with some link relations to indicate 'on-demand' vs. 'linear
>> broadcast', but that's a separate issue entirely).
>>
>> The user agents can be quite a lot smarter if they can determine from
>> the feed whether a given programme is available for on-demand
>> viewing/listening at a given point in time  (not all will be, due to
>> rights constraints); if so, how long the user has access to the
>> resource, and if not, whether it will be for the future or if the
>> window has already passed.
>>
>> I must confess I haven't thought deeply about wider applications of a
>> notbefore/notafter - obviously limited-time availability for resources
>> isn't particularly uncommon, but the intersection of those and the set
>> of resources you want to appear in a feed might well be a different
>> matter.
>>
>> I'm happy enough to roll my own extension for this, but if it's
>> something generic enough to end up in link-extensions, I'd obviously
>> rather see that happen.
>>
>> Cheers,
>>
>> M.
>>
>>
>

--0016e64de3caeaab590488af4aea
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

An earlier version of the current xCal Draft included the specification of =
a &quot;link&quot; element which was intended to bring into the calendar do=
main the link element as defined by Atom. This element was removed from the=
 current draft as it is planned to specify it in a distinct draft. However,=
 given that the intention is to map what Atom provides, it would probably m=
ake sense for folk to communicate with the authors about the proposed exten=
sions to Atom&#39;s link element. At the same time, it might make sense to =
request guidance from the Calendar folk on how to handle the time-range att=
ributes that are the subject of this thread.<div>
<br></div><div>See the old (now removed) specification of LINK in Section 5=
 of the old xCal draft (02):</div><div><a href=3D"http://tools.ietf.org/htm=
l/draft-daboo-et-al-icalendar-in-xml-02#section-5">http://tools.ietf.org/ht=
ml/draft-daboo-et-al-icalendar-in-xml-02#section-5</a></div>
<div><br></div><div><a href=3D"http://tools.ietf.org/html/draft-daboo-et-al=
-icalendar-in-xml-02#section-5"></a>bob wyman<br><br><div class=3D"gmail_qu=
ote">On Thu, Jun 10, 2010 at 12:04 PM, Bob Wyman <span dir=3D"ltr">&lt;<a h=
ref=3D"mailto:bob@wyman.us">bob@wyman.us</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex;">Simple solutions are wonderful! Unless they=
 are simple solutions to complex problems. The harsh reality is that for a =
solution to be effective, its complexity must *at least* match the complexi=
ty of the problem solved. In this case, the specification of time ranges is=
 a complex problem and any &quot;simple&quot; solution to it will result ei=
ther in disuse (since the solution is inadequate) of increased complexity i=
n the future as people extend the basic capability to handle the unaddresse=
d complexity of the problem domain. Personally, in the over 30 years I&#39;=
ve spent in this business, I&#39;ve seen uncounted attempts to address the =
&quot;time range&quot; problem simply. Each effort begins with someone prop=
osing the &quot;simple&quot; solution of &quot;start&quot; and &quot;end&qu=
ot; times. But, then fairly soon thereafter, someone appears with the requi=
rement for discontinuous time ranges... i.e. The event occurs from 8:00pm t=
o 9:00pm Eastern Standard Time on Tuesday evenings during the months of Sep=
tember through December unless it is the first Tuesday in November during a=
 year that is evenly divisible by 2, in which case, the broadcast will occu=
r one hour earlier. (i.e. time shifting to compensate for poll closing duri=
ng US elections...)<div>

<br></div><div>Rather than defining something new, I would strongly encoura=
ge you to take a long hard look at the xCal Draft and attempt to ensure tha=
t whatever is done here, if anything, is compatible with that specification=
. The ideal would be to define these attributes as incorporations of the xC=
al methods rather than to define something entirely new.</div>

<div><br></div><div>See:=A0<a href=3D"http://tools.ietf.org/html/draft-dabo=
o-et-al-icalendar-in-xml-04" target=3D"_blank">http://tools.ietf.org/html/d=
raft-daboo-et-al-icalendar-in-xml-04</a></div><div><br></div><div>The &quot=
;time specification&quot; or calendar problem is terribly vexing and diffic=
ult. Please, don&#39;t try to reinvent the wheel...</div>

<div><br></div><font color=3D"#888888"><div>bob wyman</div></font><div><div=
></div><div class=3D"h5"><div><br></div><div><br><br><div class=3D"gmail_qu=
ote">On Thu, Jun 10, 2010 at 11:01 AM, Mo McRoberts <span dir=3D"ltr">&lt;<=
a href=3D"mailto:mo@nevali.net" target=3D"_blank">mo@nevali.net</a>&gt;</sp=
an> wrote:<br>

<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div><br>
On Thu, Jun 10, 2010 at 15:43, James Snell &lt;<a href=3D"mailto:jasnell@gm=
ail.com" target=3D"_blank">jasnell@gmail.com</a>&gt; wrote:<br>
<br>
&gt; =A0&lt;link rel=3D&quot;...&quot; href=3D&quot;...&quot;<br>
&gt; =A0 =A0notbefore=3D&quot;2010-06-10T12:00:00-08:00&quot;<br>
&gt; =A0 =A0notafter=3D&quot;2010-06-10T01:00:00-08:00&quot; /&gt;<br>
<br>
</div>&#39;notbefore&#39; and &#39;notafter&#39; are pretty ideal.<br>
<div><br>
&gt; I would have no problem including these in the link extensions spec if=
<br>
&gt; the supporting use cases are sufficiently generic.<br>
&gt;<br>
&gt; However, it might make more sense to define these as extension<br>
&gt; elements to the link or entry... hard to say for sure without knowing<=
br>
&gt; more about the specific use case and how the your entries are being<br=
>
&gt; modeled.<br>
<br>
</div>Okay, bit of background: building a feed which contains information<b=
r>
about TV (or radio) programmes. there&#39;s some extra stuff in there<br>
relating them to actual broadcasts (RFC4078 crid:// URIs), but<br>
principally, it boils down to the usual atom:entry elements - title,<br>
summary, id, published timestamp and links to resources.<br>
<br>
What I&#39;d like to include in this feed is a particular class of link<br>
which refers to a resource (or set of resources of different types)<br>
where the programme can be downloaded or streamed, generally for a<br>
limited period - usually starting about half an hour after the on-air<br>
broadcast concludes (at some point along the way I&#39;ll need to come up<b=
r>
with some link relations to indicate &#39;on-demand&#39; vs. &#39;linear<br=
>
broadcast&#39;, but that&#39;s a separate issue entirely).<br>
<br>
The user agents can be quite a lot smarter if they can determine from<br>
the feed whether a given programme is available for on-demand<br>
viewing/listening at a given point in time =A0(not all will be, due to<br>
rights constraints); if so, how long the user has access to the<br>
resource, and if not, whether it will be for the future or if the<br>
window has already passed.<br>
<br>
I must confess I haven&#39;t thought deeply about wider applications of a<b=
r>
notbefore/notafter - obviously limited-time availability for resources<br>
isn&#39;t particularly uncommon, but the intersection of those and the set<=
br>
of resources you want to appear in a feed might well be a different<br>
matter.<br>
<br>
I&#39;m happy enough to roll my own extension for this, but if it&#39;s<br>
something generic enough to end up in link-extensions, I&#39;d obviously<br=
>
rather see that happen.<br>
<br>
Cheers,<br>
<font color=3D"#888888"><br>
M.<br>
<br>
</font></blockquote></div><br></div>
</div></div></blockquote></div><br></div>

--0016e64de3caeaab590488af4aea--


From owner-atom-syntax@mail.imc.org  Thu Jun 10 10:09:22 2010
Return-Path: <owner-atom-syntax@mail.imc.org>
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 3EC163A6A16 for <ietfarch-atompub-archive@core3.amsl.com>; Thu, 10 Jun 2010 10:09:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.554
X-Spam-Level: 
X-Spam-Status: No, score=0.554 tagged_above=-999 required=5 tests=[BAYES_50=0.001, 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 UlnuOp4M-tsb for <ietfarch-atompub-archive@core3.amsl.com>; Thu, 10 Jun 2010 10:09:21 -0700 (PDT)
Received: from hoffman.proper.com (Hoffman.Proper.COM [207.182.41.81]) by core3.amsl.com (Postfix) with ESMTP id 460D43A6983 for <atompub-archive@ietf.org>; Thu, 10 Jun 2010 10:09:21 -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 o5AH41B9074819 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 10 Jun 2010 10:04:01 -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 o5AH41gt074818; Thu, 10 Jun 2010 10:04:01 -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-fx0-f43.google.com (mail-fx0-f43.google.com [209.85.161.43]) by hoffman.proper.com (8.14.4/8.14.3) with ESMTP id o5AH3x0t074812 for <atom-syntax@imc.org>; Thu, 10 Jun 2010 10:04:00 -0700 (MST) (envelope-from mo@ilaven.net)
Received: by fxm10 with SMTP id 10so144411fxm.16 for <atom-syntax@imc.org>; Thu, 10 Jun 2010 10:03:57 -0700 (PDT)
Received: by 10.223.68.131 with SMTP id v3mr573998fai.82.1276189437633; Thu, 10 Jun 2010 10:03:57 -0700 (PDT)
Received: from pip.ilaven.net ([89.241.181.71]) by mx.google.com with ESMTPS id 13sm820007fad.7.2010.06.10.10.03.55 (version=TLSv1/SSLv3 cipher=RC4-MD5); Thu, 10 Jun 2010 10:03:56 -0700 (PDT)
Subject: Re: Link extensions-related: link availability/expiry?
Mime-Version: 1.0 (Apple Message framework v1078)
Content-Type: text/plain; charset=windows-1252
From: Mo McRoberts <mo@nevali.net>
In-Reply-To: <AANLkTimFKuTQeCDjd1TWv33Nfb6n0AxukxXGXictdUv5@mail.gmail.com>
Date: Thu, 10 Jun 2010 18:03:54 +0100
Cc: James Snell <jasnell@gmail.com>, atom-syntax@imc.org
Message-Id: <FD5EF24C-77B5-4C73-9BFC-5D29B9DBF2CC@nevali.net>
References: <AANLkTintAESgi33LdLXd-QDmsm7iuhBlojm4a4b4n7_s@mail.gmail.com> <AANLkTilb9Reqyc34YFYkEwcpKgh2vVuCDeKqnYvPg356@mail.gmail.com> <AANLkTinN-lOW2Z_Nw36CYZ0qiXXTh-OEK3ZeT-C2B4Ph@mail.gmail.com> <AANLkTimFKuTQeCDjd1TWv33Nfb6n0AxukxXGXictdUv5@mail.gmail.com>
To: Bob Wyman <bob@wyman.us>
X-Mailer: Apple Mail (2.1078)
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by hoffman.proper.com id o5AH400t074814
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>

On 10-Jun-2010, at 17:04, Bob Wyman wrote:

> Simple solutions are wonderful! Unless they are simple solutions to complex problems. The harsh reality is that for a solution to be effective, its complexity must *at least* match the complexity of the problem solved. In this case, the specification of time ranges is a complex problem and any "simple" solution to it will result either in disuse (since the solution is inadequate) of increased complexity in the future as people extend the basic capability to handle the unaddressed complexity of the problem domain. Personally, in the over 30 years I've spent in this business, I've seen uncounted attempts to address the "time range" problem simply. Each effort begins with someone proposing the "simple" solution of "start" and "end" times. But, then fairly soon thereafter, someone appears with the requirement for discontinuous time ranges... i.e. The event occurs from 8:00pm to 9:00pm Eastern Standard Time on Tuesday evenings during the months of September through December unl!
 ess it is the first Tuesday in November during a year that is evenly divisible by 2, in which case, the broadcast will occur one hour earlier. (i.e. time shifting to compensate for poll closing during US elections...)

Ah, in this case, I know for a fact that at a given point in time, there will only be one window for a given linked resource (although the 'window' may have either of no start or end time restriction, depending). That doesn't mean the <entry> won't be revised in a future copy of the feed, but that's perfectly fine. Note that it's not referring to times of the broadcasts themselves — there are whole reams of specifications dealing with those. Fortunately, for these purposes, I don't much have to care :)

However, comments noted — it may well be that something simple and generic isn't useful enough in the general case to warrant being part of, say, the link extensions draft. I can see why there has been opposition to such things in the past, certainly — thanks Bob.

> Rather than defining something new, I would strongly encourage you to take a long hard look at the xCal Draft and attempt to ensure that whatever is done here, if anything, is compatible with that specification. The ideal would be to define these attributes as incorporations of the xCal methods rather than to define something entirely new.

I'll take a look a the xCal stuff (and the 02 draft too). I don't mind pulling in stuff (I’m already dragging in Programmes Ontology and TV-Anytime elements for other aspects of the feed) — it’s just that I want to avoid defining it myself (possibly quite badly!) if somebody else has already done it, or is in the process of doing so.

M.



From owner-atom-syntax@mail.imc.org  Thu Jun 10 10:10:37 2010
Return-Path: <owner-atom-syntax@mail.imc.org>
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 A95A23A6A38 for <ietfarch-atompub-archive@core3.amsl.com>; Thu, 10 Jun 2010 10:10:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.779
X-Spam-Level: 
X-Spam-Status: No, score=0.779 tagged_above=-999 required=5 tests=[AWL=0.225, BAYES_50=0.001, 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 rSRfJU3aiF-T for <ietfarch-atompub-archive@core3.amsl.com>; Thu, 10 Jun 2010 10:10:36 -0700 (PDT)
Received: from hoffman.proper.com (Hoffman.Proper.COM [207.182.41.81]) by core3.amsl.com (Postfix) with ESMTP id 205073A6983 for <atompub-archive@ietf.org>; Thu, 10 Jun 2010 10:10:36 -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 o5AH6J0E074994 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 10 Jun 2010 10:06:19 -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 o5AH6JOG074993; Thu, 10 Jun 2010 10:06:19 -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-vw0-f43.google.com (mail-vw0-f43.google.com [209.85.212.43]) by hoffman.proper.com (8.14.4/8.14.3) with ESMTP id o5AH6ICF074984 for <atom-syntax@imc.org>; Thu, 10 Jun 2010 10:06:19 -0700 (MST) (envelope-from jasnell@gmail.com)
Received: by vws3 with SMTP id 3so190046vws.16 for <atom-syntax@imc.org>; Thu, 10 Jun 2010 10:06:18 -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=wFgB/fFpAwnliY1HNHtvoVoY2P2hqqiCehtK49RW7fw=; b=XvRenojl88Yzox56ZkloDg7QfngLNyH/Dq14e5CoQ4KjBjyNTkoSmt7tOyF7M1SoqY 4DGNGumOte4yY/cWY99WrhY2BKAKWr3bYLt7ik2++0d+lzTs+vpXoBCWhojefBS5gdg2 P/e4lwHgM+H1DkL1c6kpHqZg0TzB77Hw977x0=
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=TaIyLtFJm7VFkiNOoMLCMUvO9Qlb3GfP9NNcrzCOImF4hZoyBj1WhpGaG7K8wClrhZ Gw6NPy8QnDVjlqhkkXkfuBy2eXV5VaenRIZ/TPgNFY6dZEMS7pNk7nY1/UUcGOU39XuW 6B9ppHmGDOgYfhm77Glo32IV9pQHIJrnrizCk=
MIME-Version: 1.0
Received: by 10.224.53.34 with SMTP id k34mr437762qag.290.1276189577729; Thu,  10 Jun 2010 10:06:17 -0700 (PDT)
Received: by 10.229.81.78 with HTTP; Thu, 10 Jun 2010 10:06:17 -0700 (PDT)
In-Reply-To: <FD5EF24C-77B5-4C73-9BFC-5D29B9DBF2CC@nevali.net>
References: <AANLkTintAESgi33LdLXd-QDmsm7iuhBlojm4a4b4n7_s@mail.gmail.com> <AANLkTilb9Reqyc34YFYkEwcpKgh2vVuCDeKqnYvPg356@mail.gmail.com> <AANLkTinN-lOW2Z_Nw36CYZ0qiXXTh-OEK3ZeT-C2B4Ph@mail.gmail.com> <AANLkTimFKuTQeCDjd1TWv33Nfb6n0AxukxXGXictdUv5@mail.gmail.com> <FD5EF24C-77B5-4C73-9BFC-5D29B9DBF2CC@nevali.net>
Date: Thu, 10 Jun 2010 10:06:17 -0700
Message-ID: <AANLkTiniNJ9BFFbel3vqTGGwJYUiGz4GI-ZFfErfSsfF@mail.gmail.com>
Subject: Re: Link extensions-related: link availability/expiry?
From: James Snell <jasnell@gmail.com>
To: Mo McRoberts <mo@nevali.net>
Cc: Bob Wyman <bob@wyman.us>, atom-syntax@imc.org
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by hoffman.proper.com id o5AH6JCF074989
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>

Bob definitely makes an excellent point. To be honest, I was thinking
along the same lines also but wanted to take some more time to think
things thru.

On Thu, Jun 10, 2010 at 10:03 AM, Mo McRoberts <mo@nevali.net> wrote:
>
> On 10-Jun-2010, at 17:04, Bob Wyman wrote:
>
>> Simple solutions are wonderful! Unless they are simple solutions to complex problems. The harsh reality is that for a solution to be effective, its complexity must *at least* match the complexity of the problem solved. In this case, the specification of time ranges is a complex problem and any "simple" solution to it will result either in disuse (since the solution is inadequate) of increased complexity in the future as people extend the basic capability to handle the unaddressed complexity of the problem domain. Personally, in the over 30 years I've spent in this business, I've seen uncounted attempts to address the "time range" problem simply. Each effort begins with someone proposing the "simple" solution of "start" and "end" times. But, then fairly soon thereafter, someone appears with the requirement for discontinuous time ranges... i.e. The event occurs from 8:00pm to 9:00pm Eastern Standard Time on Tuesday evenings during the months of September through December un!
 less it is the first Tuesday in November during a year that is evenly divisible by 2, in which case, the broadcast will occur one hour earlier. (i.e. time shifting to compensate for poll closing during US elections...)
>
> Ah, in this case, I know for a fact that at a given point in time, there will only be one window for a given linked resource (although the 'window' may have either of no start or end time restriction, depending). That doesn't mean the <entry> won't be revised in a future copy of the feed, but that's perfectly fine. Note that it's not referring to times of the broadcasts themselves — there are whole reams of specifications dealing with those. Fortunately, for these purposes, I don't much have to care :)
>
> However, comments noted — it may well be that something simple and generic isn't useful enough in the general case to warrant being part of, say, the link extensions draft. I can see why there has been opposition to such things in the past, certainly — thanks Bob.
>
>> Rather than defining something new, I would strongly encourage you to take a long hard look at the xCal Draft and attempt to ensure that whatever is done here, if anything, is compatible with that specification. The ideal would be to define these attributes as incorporations of the xCal methods rather than to define something entirely new.
>
> I'll take a look a the xCal stuff (and the 02 draft too). I don't mind pulling in stuff (I’m already dragging in Programmes Ontology and TV-Anytime elements for other aspects of the feed) — it’s just that I want to avoid defining it myself (possibly quite badly!) if somebody else has already done it, or is in the process of doing so.
>
> M.
>
>



-- 
- James Snell
  http://www.snellspace.com
  jasnell@gmail.com


From owner-atom-syntax@mail.imc.org  Fri Jun 11 00:27:17 2010
Return-Path: <owner-atom-syntax@mail.imc.org>
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 07AC13A6A0A for <ietfarch-atompub-archive@core3.amsl.com>; Fri, 11 Jun 2010 00:27:17 -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 Mbde6pd-6KZe for <ietfarch-atompub-archive@core3.amsl.com>; Fri, 11 Jun 2010 00:27:13 -0700 (PDT)
Received: from hoffman.proper.com (Hoffman.Proper.COM [207.182.41.81]) by core3.amsl.com (Postfix) with ESMTP id 1E4033A69E3 for <atompub-archive@ietf.org>; Fri, 11 Jun 2010 00:27:13 -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 o5B7L7AL022252 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 11 Jun 2010 00:21:07 -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 o5B7L7pb022250; Fri, 11 Jun 2010 00:21:07 -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 eu1sys200aog115.obsmtp.com (eu1sys200aog115.obsmtp.com [207.126.144.139]) by hoffman.proper.com (8.14.4/8.14.3) with SMTP id o5B7L1u1022238 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <atom-syntax@imc.org>; Fri, 11 Jun 2010 00:21:04 -0700 (MST) (envelope-from samj@samj.net)
Received: from source ([209.85.212.179]) by eu1sys200aob115.postini.com ([207.126.147.11]) with SMTP ID DSNKTBHj3I92eK5Q3DQy3+jzCUHew+4TQm03@postini.com; Fri, 11 Jun 2010 07:21:04 UTC
Received: by pxi3 with SMTP id 3so314311pxi.10 for <atom-syntax@imc.org>; Fri, 11 Jun 2010 00:21:00 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.114.251.23 with SMTP id y23mr1143027wah.42.1276240859976; Fri,  11 Jun 2010 00:20:59 -0700 (PDT)
Received: by 10.114.146.10 with HTTP; Fri, 11 Jun 2010 00:20:59 -0700 (PDT)
In-Reply-To: <AANLkTiniNJ9BFFbel3vqTGGwJYUiGz4GI-ZFfErfSsfF@mail.gmail.com>
References: <AANLkTintAESgi33LdLXd-QDmsm7iuhBlojm4a4b4n7_s@mail.gmail.com> <AANLkTilb9Reqyc34YFYkEwcpKgh2vVuCDeKqnYvPg356@mail.gmail.com> <AANLkTinN-lOW2Z_Nw36CYZ0qiXXTh-OEK3ZeT-C2B4Ph@mail.gmail.com> <AANLkTimFKuTQeCDjd1TWv33Nfb6n0AxukxXGXictdUv5@mail.gmail.com> <FD5EF24C-77B5-4C73-9BFC-5D29B9DBF2CC@nevali.net> <AANLkTiniNJ9BFFbel3vqTGGwJYUiGz4GI-ZFfErfSsfF@mail.gmail.com>
Date: Fri, 11 Jun 2010 09:20:59 +0200
Message-ID: <AANLkTinY-V8YcRTfdVSYgiEzvtz3UzflI_hPGZvAn1Kk@mail.gmail.com>
Subject: Re: Link extensions-related: link availability/expiry?
From: Sam Johnston <samj@samj.net>
To: James Snell <jasnell@gmail.com>
Cc: Mo McRoberts <mo@nevali.net>, Bob Wyman <bob@wyman.us>, atom-syntax@imc.org
Content-Type: multipart/alternative; boundary=0016367f92eb1b552f0488bbfb6e
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>

--0016367f92eb1b552f0488bbfb6e
Content-Type: text/plain; charset=ISO-8859-1

On Thu, Jun 10, 2010 at 7:06 PM, James Snell <jasnell@gmail.com> wrote:

>
> Bob definitely makes an excellent point. To be honest, I was thinking
> along the same lines also but wanted to take some more time to think
> things thru.
>

Surely by the time you get to putting entries in a feed you already know the
window within which they are valid? Parsers already understand rfc3339 so
I'd lean in the direction of notbefore/notafter with rfc3339 times rather
than something nontrivial (however flexible). One can always expose more
complex recipes for more complex applications using another attribute.

Sam

--0016367f92eb1b552f0488bbfb6e
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On Thu, Jun 10, 2010 at 7:06 PM, James Snell <span dir=3D"ltr">&lt;<a href=
=3D"mailto:jasnell@gmail.com">jasnell@gmail.com</a>&gt;</span> wrote:<br><d=
iv class=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"margin:=
0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<br>
Bob definitely makes an excellent point. To be honest, I was thinking<br>
along the same lines also but wanted to take some more time to think<br>
things thru.<br>
<div class=3D"im"></div></blockquote></div><br><div>Surely by the time you =
get to putting entries in a feed you already know the window within which t=
hey are valid? Parsers already understand rfc3339 so I&#39;d lean in the di=
rection of notbefore/notafter with rfc3339 times rather than something nont=
rivial (however flexible). One can always expose more complex recipes for m=
ore complex applications using another attribute.</div>
<div><br></div><div>Sam</div><div><br></div>

--0016367f92eb1b552f0488bbfb6e--


From owner-atom-syntax@mail.imc.org  Tue Jun 22 09:25:33 2010
Return-Path: <owner-atom-syntax@mail.imc.org>
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 4B4C93A68A9 for <ietfarch-atompub-archive@core3.amsl.com>; Tue, 22 Jun 2010 09:25:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.955
X-Spam-Level: 
X-Spam-Status: No, score=0.955 tagged_above=-999 required=5 tests=[AWL=0.400, BAYES_50=0.001, 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 xBte083GOafN for <ietfarch-atompub-archive@core3.amsl.com>; Tue, 22 Jun 2010 09:25:32 -0700 (PDT)
Received: from hoffman.proper.com (Hoffman.Proper.COM [207.182.41.81]) by core3.amsl.com (Postfix) with ESMTP id 7E0473A67AB for <atompub-archive@ietf.org>; Tue, 22 Jun 2010 09:25:32 -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 o5MGG3iI099258 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 22 Jun 2010 09:16: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 o5MGG3eS099257; Tue, 22 Jun 2010 09:16:03 -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-gw0-f43.google.com (mail-gw0-f43.google.com [74.125.83.43]) by hoffman.proper.com (8.14.4/8.14.3) with ESMTP id o5MGG3PP099251 for <atom-syntax@imc.org>; Tue, 22 Jun 2010 09:16:03 -0700 (MST) (envelope-from jasnell@gmail.com)
Received: by gwb1 with SMTP id 1so114242gwb.16 for <atom-syntax@imc.org>; Tue, 22 Jun 2010 09:16:02 -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=2DVNeHRgLhPGTqftDEg6jQDUY6XyFhZ2hAWnSRA/tG0=; b=N2+LlYKXlS4GAuh2X6Zuzpo115DeCO5LPCpoVHsfsfzB5nhzIe6bxbciGX1tOvV4Be lEQy0sAQggV0zazVFuYMOFJTPB+UG86NqpebyDrOE79q3e6I4wipBagVSd0eirkRLI1s 4qkax6DiJSpHX7XAiV2+CEyzK81icdIHMaMe0=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=aZuDY3TNt0aQ2SduCsqzE3MMVMtqLgpXS3hgteHVas7rRqnJram4CdjTVrfxvCKgM2 CJ0b9ZD2BEfir3TGjW9+izcbyE0mbbBnaQif0Rt4x0QFi5xJqfKpGjkKmfzGXHiHUwn7 QAYVZ+afPBEqs1XW6KxbgLe5njlP9cq5Cn9tk=
MIME-Version: 1.0
Received: by 10.229.185.195 with SMTP id cp3mr3486262qcb.217.1277223362506;  Tue, 22 Jun 2010 09:16:02 -0700 (PDT)
Received: by 10.229.81.78 with HTTP; Tue, 22 Jun 2010 09:16:02 -0700 (PDT)
Date: Tue, 22 Jun 2010 09:16:02 -0700
Message-ID: <AANLkTinRwt1PsHJz2EfVB8xIC-htoRSmtI8uOSSWloci@mail.gmail.com>
Subject: Atom Tombstones - Last Call
From: James Snell <jasnell@gmail.com>
To: Atom Syntax <atom-syntax@imc.org>
Content-Type: multipart/alternative; boundary=00163630f079d231f10489a0bc87
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>

--00163630f079d231f10489a0bc87
Content-Type: text/plain; charset=ISO-8859-1

Ok, I'm declaring this done... Last Call on Tombstones and a Call for
Implementation...

  http://www.ietf.org/internet-drafts/draft-snell-atompub-tombstones-10.txt

- James

--00163630f079d231f10489a0bc87
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div>Ok, I&#39;m declaring this done... Last Call on Tombstones and a Call =
for Implementation...</div><div><br></div>=A0=A0<a href=3D"http://www.ietf.=
org/internet-drafts/draft-snell-atompub-tombstones-10.txt">http://www.ietf.=
org/internet-drafts/draft-snell-atompub-tombstones-10.txt</a><br clear=3D"a=
ll">
<br>
<div>- James</div>

--00163630f079d231f10489a0bc87--


From owner-atom-syntax@mail.imc.org  Tue Jun 22 14:31:29 2010
Return-Path: <owner-atom-syntax@mail.imc.org>
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 021C628C108 for <ietfarch-atompub-archive@core3.amsl.com>; Tue, 22 Jun 2010 14:31:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.554
X-Spam-Level: 
X-Spam-Status: No, score=0.554 tagged_above=-999 required=5 tests=[BAYES_50=0.001, 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 pzSZwGUMdzyd for <ietfarch-atompub-archive@core3.amsl.com>; Tue, 22 Jun 2010 14:31:23 -0700 (PDT)
Received: from hoffman.proper.com (Hoffman.Proper.COM [207.182.41.81]) by core3.amsl.com (Postfix) with ESMTP id 7590928C0F8 for <atompub-archive@ietf.org>; Tue, 22 Jun 2010 14:31:10 -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 o5MLPY0h017319 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 22 Jun 2010 14:25:34 -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 o5MLPYpb017318; Tue, 22 Jun 2010 14:25:34 -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.gmx.net (mail.gmx.net [213.165.64.20]) by hoffman.proper.com (8.14.4/8.14.3) with SMTP id o5MLPWGT017313 for <atom-syntax@imc.org>; Tue, 22 Jun 2010 14:25:33 -0700 (MST) (envelope-from derhoermi@gmx.net)
Received: (qmail invoked by alias); 22 Jun 2010 21:25:31 -0000
Received: from dslb-094-223-210-059.pools.arcor-ip.net (EHLO hive) [94.223.210.59] by mail.gmx.net (mp007) with SMTP; 22 Jun 2010 23:25:31 +0200
X-Authenticated: #723575
X-Provags-ID: V01U2FsdGVkX18ldElg5iIl/FlZx1PX+Ny6GDQ0ZXNdrRmgfP9F1A WVHZFLvMupcX8N
From: Bjoern Hoehrmann <derhoermi@gmx.net>
To: James Snell <jasnell@gmail.com>
Cc: Atom Syntax <atom-syntax@imc.org>
Subject: Re: Atom Tombstones - Last Call
Date: Tue, 22 Jun 2010 23:25:30 +0200
Message-ID: <qu9226li838ik37e24irghajvmg172ct9d@hive.bjoern.hoehrmann.de>
References: <AANLkTinRwt1PsHJz2EfVB8xIC-htoRSmtI8uOSSWloci@mail.gmail.com>
In-Reply-To: <AANLkTinRwt1PsHJz2EfVB8xIC-htoRSmtI8uOSSWloci@mail.gmail.com>
X-Mailer: Forte Agent 3.3/32.846
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-Y-GMX-Trusted: 0
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>

* James Snell wrote:
>Ok, I'm declaring this done... Last Call on Tombstones and a Call for
>Implementation...
>
>  http://www.ietf.org/internet-drafts/draft-snell-atompub-tombstones-10.txt

As the document contains a media type registration, you should ask for
its review on the ietf-types mailing list, see RFC 4288. It is customary
to send a pointer to the document as well as the filled out template.

You need to adapt your template so it follows the form specified in RFC
4288, for instance, some of the field names are different. The fields
"Fragment identifiers" and "Base URI" should be removed, RFC 3023 does
not specify anything in that regard that would be of note.
-- 
Björn Höhrmann · mailto:bjoern@hoehrmann.de · http://bjoern.hoehrmann.de
Am Badedeich 7 · Telefon: +49(0)160/4415681 · http://www.bjoernsworld.de
25899 Dagebüll · PGP Pub. KeyID: 0xA4357E78 · http://www.websitedev.de/ 


From owner-atom-syntax@mail.imc.org  Tue Jun 22 16:21:13 2010
Return-Path: <owner-atom-syntax@mail.imc.org>
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 41B093A67AC for <ietfarch-atompub-archive@core3.amsl.com>; Tue, 22 Jun 2010 16:21:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.355
X-Spam-Level: **
X-Spam-Status: No, score=2.355 tagged_above=-999 required=5 tests=[BAYES_50=0.001, HELO_MISMATCH_COM=0.553, HTML_MESSAGE=0.001, J_CHICKENPOX_22=0.6, J_CHICKENPOX_27=0.6, J_CHICKENPOX_46=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 Hr0J-+K6m6bz for <ietfarch-atompub-archive@core3.amsl.com>; Tue, 22 Jun 2010 16:21:12 -0700 (PDT)
Received: from hoffman.proper.com (Hoffman.Proper.COM [207.182.41.81]) by core3.amsl.com (Postfix) with ESMTP id 141503A68D1 for <atompub-archive@ietf.org>; Tue, 22 Jun 2010 16:21: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 o5MNGC2t022567 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 22 Jun 2010 16:16:12 -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 o5MNGC3X022566; Tue, 22 Jun 2010 16:16:12 -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 blu0-omc2-s8.blu0.hotmail.com (blu0-omc2-s8.blu0.hotmail.com [65.55.111.83]) by hoffman.proper.com (8.14.4/8.14.3) with ESMTP id o5MNGBfK022560 for <atom-syntax@imc.org>; Tue, 22 Jun 2010 16:16:12 -0700 (MST) (envelope-from j4_james@hotmail.com)
Received: from BLU122-W23 ([65.55.111.73]) by blu0-omc2-s8.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675); Tue, 22 Jun 2010 16:16:11 -0700
Message-ID: <BLU122-W232F8BFAEB3469C816D96BBEC40@phx.gbl>
Content-Type: multipart/alternative; boundary="_d730bd28-839c-404e-b942-38c9a885d743_"
X-Originating-IP: [212.134.155.210]
From: James Holderness <j4_james@hotmail.com>
To: <atom-syntax@imc.org>
Subject: RE: Atom Tombstones - Last Call
Date: Tue, 22 Jun 2010 19:16:11 -0400
Importance: Normal
In-Reply-To: <AANLkTinRwt1PsHJz2EfVB8xIC-htoRSmtI8uOSSWloci@mail.gmail.com>
References: <AANLkTinRwt1PsHJz2EfVB8xIC-htoRSmtI8uOSSWloci@mail.gmail.com>
MIME-Version: 1.0
X-OriginalArrivalTime: 22 Jun 2010 23:16:11.0568 (UTC) FILETIME=[E739DB00:01CB1260]
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>

--_d730bd28-839c-404e-b942-38c9a885d743_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable


Haven't had a chance to re-read the whole document=2C but I just noticed so=
mething which I thought I should mention before I forgot about it.

I don't know RELAX NG syntax very well=2C but it seems to me that the schem=
a you have for the deletedEntry isn't quite right.

     deletedEntry =3D element at:deleted-entry {
       atomCommonAttributes=2C
       attribute ref { atomUri }=2C
       attribute when { atomDateConstruct }=2C
       ( element at:by { atomPersonConstruct}?=2C
       & element at:comment {atomTextConstruct}?=2C
       & element atom:link*=2C
       & element atom:source?=2C
       & extensionElement* )
     }

Surely those element lines shouldn't have a comma on the end? You already h=
ave an ampersand connector and you wouldn't want a comma connector anyway s=
ince order isn't significant. Or have I got it all wrong?

Also=2C not a big deal=2C but while you're looking at that=2C the spacing i=
nside the braces could do with some consistency.

Regards
James

 		 	   		 =20
_________________________________________________________________
The New Busy think 9 to 5 is a cute idea. Combine multiple calendars with H=
otmail.=20
http://www.windowslive.com/campaign/thenewbusy?tile=3Dmulticalendar&ocid=3D=
PID28326::T:WLMTAGL:ON:WL:en-US:WM_HMP:042010_5=

--_d730bd28-839c-404e-b942-38c9a885d743_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<style><!--
.hmmessage P
{
margin:0px=3B
padding:0px
}
body.hmmessage
{
font-size: 10pt=3B
font-family:Verdana
}
--></style>
</head>
<body class=3D'hmmessage'>
Haven't had a chance to re-read the whole document=2C but I just noticed so=
mething which I thought I should mention before I forgot about it.<br><br>I=
 don't know RELAX NG syntax very well=2C but it seems to me that the schema=
 you have for the deletedEntry isn't quite right.<br><br>&nbsp=3B&nbsp=3B&n=
bsp=3B&nbsp=3B deletedEntry =3D element at:deleted-entry {<br>&nbsp=3B&nbsp=
=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B atomCommonAttributes=2C<br>&nbsp=3B&nbs=
p=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B attribute ref { atomUri }=2C<br>&nbsp=
=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B attribute when { atomDateConstr=
uct }=2C<br>&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B ( element at:b=
y { atomPersonConstruct}?=2C<br>&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nb=
sp=3B &amp=3B element at:comment {atomTextConstruct}?=2C<br>&nbsp=3B&nbsp=
=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B &amp=3B element atom:link*=2C<br>&nbsp=
=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B &amp=3B element atom:source?=2C=
<br>&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B &amp=3B extensionEleme=
nt* )<br>&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B }<br><br>Surely those element lin=
es shouldn't have a comma on the end? You already have an ampersand connect=
or and you wouldn't want a comma connector anyway since order isn't signifi=
cant. Or have I got it all wrong?<br><br>Also=2C not a big deal=2C but whil=
e you're looking at that=2C the spacing inside the braces could do with som=
e consistency.<br><br>Regards<br>James<br><br> 		 	   		  <br /><hr />The N=
ew Busy think 9 to 5 is a cute idea. Combine multiple calendars with Hotmai=
l.  <a href=3D'http://www.windowslive.com/campaign/thenewbusy?tile=3Dmultic=
alendar&ocid=3DPID28326::T:WLMTAGL:ON:WL:en-US:WM_HMP:042010_5' target=3D'_=
new'>Get busy.</a></body>
</html>=

--_d730bd28-839c-404e-b942-38c9a885d743_--


From owner-atom-syntax@mail.imc.org  Wed Jun 30 11:43:56 2010
Return-Path: <owner-atom-syntax@mail.imc.org>
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 E85C13A68F6 for <ietfarch-atompub-archive@core3.amsl.com>; Wed, 30 Jun 2010 11:43:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.034
X-Spam-Level: *
X-Spam-Status: No, score=1.034 tagged_above=-999 required=5 tests=[AWL=-0.120, BAYES_50=0.001, HELO_MISMATCH_COM=0.553, HTML_MESSAGE=0.001, J_CHICKENPOX_47=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 XO7jUjf+PtOf for <ietfarch-atompub-archive@core3.amsl.com>; Wed, 30 Jun 2010 11:43:56 -0700 (PDT)
Received: from hoffman.proper.com (Hoffman.Proper.COM [207.182.41.81]) by core3.amsl.com (Postfix) with ESMTP id 26E2E3A6936 for <atompub-archive@ietf.org>; Wed, 30 Jun 2010 11:43:53 -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 o5UIWirJ083668 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 30 Jun 2010 11:32:44 -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 o5UIWiU9083667; Wed, 30 Jun 2010 11:32:44 -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-gy0-f171.google.com (mail-gy0-f171.google.com [209.85.160.171]) by hoffman.proper.com (8.14.4/8.14.3) with ESMTP id o5UIWhDx083662 for <atom-syntax@imc.org>; Wed, 30 Jun 2010 11:32:43 -0700 (MST) (envelope-from jasnell@gmail.com)
Received: by gyg8 with SMTP id 8so787126gyg.16 for <atom-syntax@imc.org>; Wed, 30 Jun 2010 11:32:42 -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=Vc8dsSvtnZ2TA30CuOqRyRTe3y0IwjqEz/+gW3E4i6A=; b=Q0rfIDKZHZGbuopUuZPh0elw8TIlLqr9m2oCRnrpstUFViA8FD9fRqr6bI5RlPX5Zt ++hIErZ2fPFAXT3NDEH7J7eKKS+jyvz10ZW2DvoxAuCsn+XCq3fQMQr0xT60zmBBAsVb Y2p1OndBe53BW7hXI3jJ3HcIL/c7Ii6DON06U=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=a4xPzf5d22JIrCoZbL9GUnmzqdEyKbZW5xilBxzUeBtAKVSIZdlHv4ktArm8bDmsnJ T7xN2YSEFs/cyQfj0sgSpBtpRXzwQ6B/EpNUgJ4HfJiQEsqn256MzvUBpNtV6yFkZd2c 8vFlIPE6LG3kOU427rEfKkfx1Fw1BuH9u+kfo=
MIME-Version: 1.0
Received: by 10.224.68.1 with SMTP id t1mr6608585qai.14.1277922762253; Wed, 30  Jun 2010 11:32:42 -0700 (PDT)
Received: by 10.229.87.70 with HTTP; Wed, 30 Jun 2010 11:32:42 -0700 (PDT)
Date: Wed, 30 Jun 2010 11:32:42 -0700
Message-ID: <AANLkTinx5bDonajDzTYT4pelvsrOm70qcckjfccIc14C@mail.gmail.com>
Subject: Link Extensions Draft Update
From: James Snell <jasnell@gmail.com>
To: Atom Syntax <atom-syntax@imc.org>
Content-Type: multipart/alternative; boundary=001485e7e4ca4b69d6048a4394c4
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>

--001485e7e4ca4b69d6048a4394c4
Content-Type: text/plain; charset=ISO-8859-1

http://www.ietf.org/internet-drafts/draft-snell-atompub-link-extensions-07.txt

A few minor updates, and one significant update... the new requirement is
that changes to the hash, etag, modified and accessed attributes MUST be
considered to be "significant" with regards to the value of atom:updated.
This is a requirement on the feed publisher.

I'd like to wrap this one up so consider this a preliminary Last Call.

- James

--001485e7e4ca4b69d6048a4394c4
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<a href=3D"http://www.ietf.org/internet-drafts/draft-snell-atompub-link-ext=
ensions-07.txt">http://www.ietf.org/internet-drafts/draft-snell-atompub-lin=
k-extensions-07.txt</a>
<div><br></div><div>A few minor updates, and one significant update... the =
new requirement is that changes to the hash, etag, modified and accessed at=
tributes MUST be considered to be &quot;significant&quot; with regards to t=
he value of atom:updated. This is a requirement on the feed publisher.=A0</=
div>
<div><br></div><div>I&#39;d like to wrap this one up so consider this a pre=
liminary Last Call.=A0</div><div><br></div><div>- James</div>

--001485e7e4ca4b69d6048a4394c4--

