{"id":1039,"date":"2008-01-16T00:00:00","date_gmt":"2008-01-15T23:00:00","guid":{"rendered":"https:\/\/wwwneu.strehle.de\/tim\/weblog\/archives\/2008\/01\/16\/977\/"},"modified":"2008-01-16T00:00:00","modified_gmt":"2008-01-15T23:00:00","slug":"977","status":"publish","type":"post","link":"https:\/\/www.strehle.de\/tim\/weblog\/archives\/2008\/01\/16\/977\/","title":{"rendered":"Atom Is The New JCR"},"content":{"rendered":"<p>Adrian Sutton &#8211; <a href=\"http:\/\/www.symphonious.net\/2008\/01\/08\/atom-is-the-new-jcr\/\" title=\"Symphonious \u00bb Atom Is The New JCR\">Atom Is The New JCR<\/a>:<\/p>\n<p>&#8222;When the Java Content Repository (JCR) standard first came out it was supposed to bring in a new era of compatibility between content repositories and put an end to the content silo. There was, and still is, a lot of talk about it and just about everyone added JCR compliance to their marketing materials. [&#8230;] There are a few CMSs around that do have good JCR support &#8211; Alfresco for example &#8211; but they&#8217;re few and far between and even with that, there isn&#8217;t a lot of people taking advantage of that support and the standardization of the repository interface.<\/p>\n<p>Then along came Atom which is all about remote access and manipulation of data and missing probably 90% of the functionality that JCR offers. It really isn&#8217;t a competitor to JCR at all and yet it&#8217;s doing more to break down content silos than JCR ever has.<\/p>\n<p>[&#8230;] Having Atom support in your product, serving and consuming as necessary is becoming an extremely powerful feature.&#8220;<\/p>\n<p>(Via <a href=\"http:\/\/intertwingly.net\/blog\/2008\/01\/16\/Atom-as-Registry-Repository\" title=\"Sam Ruby: Atom as Registry \/ Repository\">Sam Ruby<\/a>.)<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Adrian Sutton &#8211; Atom Is The New JCR: &#8222;When the Java Content Repository (JCR) standard first came out it was supposed to bring in a new era of compatibility between content repositories and put an end to the content silo. There was, and still is, a lot of talk about it and just about everyone [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"footnotes":"","_share_on_mastodon":"0"},"categories":[1],"tags":[],"class_list":["post-1039","post","type-post","status-publish","format-standard","hentry","category-weblog"],"share_on_mastodon":{"url":"","error":""},"_links":{"self":[{"href":"https:\/\/www.strehle.de\/tim\/wp-json\/wp\/v2\/posts\/1039","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.strehle.de\/tim\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.strehle.de\/tim\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.strehle.de\/tim\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.strehle.de\/tim\/wp-json\/wp\/v2\/comments?post=1039"}],"version-history":[{"count":0,"href":"https:\/\/www.strehle.de\/tim\/wp-json\/wp\/v2\/posts\/1039\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.strehle.de\/tim\/wp-json\/wp\/v2\/media?parent=1039"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.strehle.de\/tim\/wp-json\/wp\/v2\/categories?post=1039"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.strehle.de\/tim\/wp-json\/wp\/v2\/tags?post=1039"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}