{"id":169,"date":"2003-09-15T06:33:00","date_gmt":"2003-09-15T10:33:00","guid":{"rendered":"http:\/\/www.markbaker.ca\/wp\/?p=144"},"modified":"2003-09-15T06:33:00","modified_gmt":"2003-09-15T10:33:00","slug":"feed-2","status":"publish","type":"post","link":"http:\/\/www.markbaker.ca\/blog\/2003\/09\/feed-2\/","title":{"rendered":"feed:\/\/?"},"content":{"rendered":"<p><a href=\"http:\/\/www.rassoc.com\/gregr\/weblog\/archive.aspx?post=656\">Greg&#8217;s asking<\/a>\nfor comments on the using a feed URI scheme to identify a subscription action for the\nfeed, e.g. &#8220;feed:\/\/http:\/\/example.org\/rss.xml&#8221;.<\/p>\n\n<p>I think we can do better.  Here&#8217;s two big reasons why I don&#8217;t like this proposal;<\/p>\n\n<ul>\n<li>&#8220;Clicking&#8221; on a URI should always be safe, and provide information\nabout the identified resource, not take an action upon it.  This enables\nhumans and automata to be able to trust that they&#8217;re\n<a href=\"http:\/\/www.w3.org\/2001\/tag\/doc\/get7\">not entering into an obligation<\/a>\nby dereferencing a URI (any URI, not just http URIs).<\/li>\n<li>The resource really is &#8220;http:\/\/example.org\/rss.xml&#8221;, and putting\n&#8220;feed:\/\/&#8221; on the front obfuscates that from parties who don&#8217;t know\nwhat &#8220;feed:\/\/&#8221; means.<\/li>\n<\/ul>\n\n<p>So what&#8217;s the better proposal?  For one, get folks to start using an\n<a href=\"http:\/\/www.ietf.org\/internet-drafts\/draft-nottingham-rss-media-type-00.txt\">RSS-specific media type<\/a>\nso that the client knows it&#8217;s RSS.  Then you just need to register\nyour aggregator as the application that handles that media type.  Within\nthe aggregator, I would expect to see that feed after clicking on\nthe URI, but with a BIG &#8220;SUBSCRIBE&#8221; button in plain site when it realizes\nthat I&#8217;m not already subscribed to that feed.  As a bonus, there&#8217;s no need\nfor a different &#8220;subscription URI&#8221;.<\/p>","protected":false},"excerpt":{"rendered":"Greg&#8217;s asking for comments on the using a feed URI scheme to identify a subscription action for the feed, e.g. &#8220;feed:\/\/http:\/\/example.org\/rss.xml&#8221;. I think we can do better. Here&#8217;s two big reasons why I don&#8217;t like this proposal; &#8220;Clicking&#8221; on a URI should always be safe, and provide information about the identified resource, not take an [&hellip;]","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[40],"class_list":["post-169","post","type-post","status-publish","format-standard","hentry","category-uncategorized","tag-xml"],"_links":{"self":[{"href":"http:\/\/www.markbaker.ca\/blog\/wp-json\/wp\/v2\/posts\/169","targetHints":{"allow":["GET"]}}],"collection":[{"href":"http:\/\/www.markbaker.ca\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/www.markbaker.ca\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/www.markbaker.ca\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"http:\/\/www.markbaker.ca\/blog\/wp-json\/wp\/v2\/comments?post=169"}],"version-history":[{"count":0,"href":"http:\/\/www.markbaker.ca\/blog\/wp-json\/wp\/v2\/posts\/169\/revisions"}],"wp:attachment":[{"href":"http:\/\/www.markbaker.ca\/blog\/wp-json\/wp\/v2\/media?parent=169"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/www.markbaker.ca\/blog\/wp-json\/wp\/v2\/categories?post=169"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/www.markbaker.ca\/blog\/wp-json\/wp\/v2\/tags?post=169"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}