Re: [RSS-DEV] Clarification about dc:date on a feed?

[burton@openprivacy.org]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

"Bill Kearney" <wkearney99@hotmail.com> writes:

> Hi all,
> 
> Can folks chime in with opinion as to what's supposed to be used in the dc:date
> element?
> 
> The specs for RSS-0.91 are ambiguous about using pubDate and lastBuildDate.  I'd
> like to get a clarification as to how dates are to be indicated in an RSS-1.0
> feed.
> 
> I can see several issues.  One is the timestamp of when the XML was truly
> generated.  Some are statically generated so this timestamp could be considered
> some way to check whether a local copy is any 'different' than the one online.
> However, a great many feeds are dynamically generated making this timestamp
> completely unsuitable for use as a checking indicator.  I'm not unaware of
> e-tags and content-header stuff, let's focus on in-feed timestamping for now.  I
> recognize protocol negotiation is an important tool it's just outside the scope
> of what I'm clarifying here.
<snip/>

Bill.  This is such a crazy issue.  I don't think it is going to be solved
anytime soon.  Maybe 'created' isn't descriptive enough.  Maybe something like
'firstPublished', or 'regenerated' is needed.

Kevin

- -- 
Kevin A. Burton ( burton@apache.org, burton@openprivacy.org, burton@peerfear.org )
             Location - San Francisco, CA, Cell - 415.595.9965
        Jabber - burtonator@jabber.org,  Web - http://www.peerfear.org/
        GPG fingerprint: 4D20 40A0 C734 307E C7B4  DCAA 0303 3AC5 BD9D 7C4D
         IRC - openprojects.net #infoanarchy | #p2p-hackers | #reptile

My greatest fear is that too many members of the public will embrace the
government's call to give up some freedom in return for greater safety, only to
find that they have lost freedom without gaining safety.
    - Nadine Strossen, President ACLU
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)
Comment: Get my public key at: http://relativity.yi.org/pgpkey.txt

iD8DBQE9IKt7AwM6xb2dfE0RAjBgAKC89RfFQCJnLPey1LHCQi693nO2yQCfV9oB
xFjsU1m9hA0IhVXYLrufKig=
=o9Tp
-----END PGP SIGNATURE-----