{"id":227,"date":"2004-11-09T07:45:00","date_gmt":"2004-11-09T07:45:00","guid":{"rendered":"http:\/\/jclark.org\/weblog\/WebDev\/ThisSite\/atomic.html"},"modified":"-0001-11-30T00:00:00","modified_gmt":"-0001-11-30T04:00:00","slug":"atomic","status":"publish","type":"post","link":"https:\/\/jclark.org\/weblog\/2004\/11\/09\/atomic\/","title":{"rendered":"Atomic"},"content":{"rendered":"<p>Tonight I added an <a href=\"http:\/\/atomenabled.org\">Atom<\/a> feed (0.3) to the site.  The link is in the Subscribe boxlet on the right.  I&#8217;ve also added a feed validation link for this feed in the Made Possible By boxlet.  <\/p>\n<p>Why an Atom feed?  I&#8217;ve always felt Atom to be a promising project.  Why now?  I&#8217;d always planned to add an Atom feed, but I&#8217;ve felt no urgency as the spec is continuing to evolve.  However, I&#8217;ve got some ideas I want to explore for using the Atom publication format and protocol in a project; more on that when I&#8217;ve had some time to refine my thoughts (and maybe write some proof-of-concept code).  For now, I&#8217;m reading up on the current states of the <a href=\"http:\/\/ietf.levkowetz.com\/drafts\/atompub\/\">specs<\/a>, poking around the <a href=\"http:\/\/www.intertwingly.net\/wiki\/pie\/FrontPage\">wiki<\/a>, and reading some of the <a href=\"http:\/\/www.imc.org\/atom-syntax\/\">mailing list<\/a> archives.<\/p>\n<p>Adding the feed to <a href=\"http:\/\/blosxom.com\">Blosxom<\/a> was straightforward.  I installed the <a href=\"http:\/\/www.blosxom.com\/plugins\/syndication\/atomfeed.htm\">atomfeed plugin<\/a>, which got me 95% of the way there.  Since the last update of the atomfeed plugin, the spec has added <code>&lt;atom:modified&gt;<\/code> as a required child element of <code>&lt;atom:feed&gt;<\/code>.  I was able to implement this by modifying the built-in flavour and using the <a href=\"http:\/\/www.blosxom.com\/plugins\/headers\/lastmodified.htm\">lastmodified plugin<\/a> to supply the value.  Putting my name in atomfeed&#8217;s $default_author config variable was the only other step I had to complete to get the feed to validate.  I&#8217;ve posted <a href=\"http:\/\/jclark.org\/download\/plugins\/atomfeed\">my version of the atomfeed plugin<\/a> which contains my fix for the <code>&lt;atom:modified&gt;<\/code> issue, but does require the lastmodified plugin.<\/p>","protected":false},"excerpt":{"rendered":"<p>Tonight I added an Atom feed (0.3) to the site. The link is in the Subscribe boxlet on the right. I&#8217;ve also added a feed validation link for this feed in the Made Possible By boxlet. Why an Atom feed? I&#8217;ve always felt Atom to be a promising project. Why now? I&#8217;d always planned to [&hellip;]<\/p>","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[4],"tags":[],"class_list":["post-227","post","type-post","status-publish","format-standard","hentry","category-thissite"],"_links":{"self":[{"href":"https:\/\/jclark.org\/weblog\/wp-json\/wp\/v2\/posts\/227","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/jclark.org\/weblog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/jclark.org\/weblog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/jclark.org\/weblog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/jclark.org\/weblog\/wp-json\/wp\/v2\/comments?post=227"}],"version-history":[{"count":0,"href":"https:\/\/jclark.org\/weblog\/wp-json\/wp\/v2\/posts\/227\/revisions"}],"wp:attachment":[{"href":"https:\/\/jclark.org\/weblog\/wp-json\/wp\/v2\/media?parent=227"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/jclark.org\/weblog\/wp-json\/wp\/v2\/categories?post=227"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/jclark.org\/weblog\/wp-json\/wp\/v2\/tags?post=227"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}