Comments on: RESTful daydream #4 http://blog.technologyofcontent.com/2009/10/restful-daydream-4/ Ramblings on the technology of content management Tue, 30 Aug 2011 15:38:33 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: ? http://blog.technologyofcontent.com/2009/10/restful-daydream-4/comment-page-1/#comment-1759 ? Thu, 08 Oct 2009 11:25:36 +0000 http://blog.technologyofcontent.com/?p=110#comment-1759 <p>I agree with your post. As JCR is just a Java repository API, I never understood how it was supposed to help interoperability, especially given the fact that most CMS are implemented in PHP.</p> <p>For interoperability, we need a protocol, not an API!</p> I agree with your post. As JCR is just a Java repository API, I never understood how it was supposed to help interoperability, especially given the fact that most CMS are implemented in PHP.

For interoperability, we need a protocol, not an API!

]]> By: Michael Marth http://blog.technologyofcontent.com/2009/10/restful-daydream-4/comment-page-1/#comment-1758 Michael Marth Thu, 08 Oct 2009 08:02:08 +0000 http://blog.technologyofcontent.com/?p=110#comment-1758 <p>Justin, thanks for clarifying. I agree with you that the Jackrabbit http interface some design bugs in terms of being RESTful (hypertext comes to my mind as well), but they should be fixable IMO. Good that this discussion gets going. Cheers Michael</p> Justin, thanks for clarifying. I agree with you that the Jackrabbit http interface some design bugs in terms of being RESTful (hypertext comes to my mind as well), but they should be fixable IMO. Good that this discussion gets going. Cheers Michael

]]> By: justin http://blog.technologyofcontent.com/2009/10/restful-daydream-4/comment-page-1/#comment-1749 justin Wed, 07 Oct 2009 22:14:22 +0000 http://blog.technologyofcontent.com/?p=110#comment-1749 <p>Michael, thanks for your thoughts, with regard to your query, so many reasons! How could anyone think it is a REST layer? Transactions in headers! No hypertext! No discoverability! About as far from a uniform interface as anyone has ever gone!</p> Michael, thanks for your thoughts, with regard to your query, so many reasons! How could anyone think it is a REST layer? Transactions in headers! No hypertext! No discoverability! About as far from a uniform interface as anyone has ever gone!

]]> By: Michael Marth http://blog.technologyofcontent.com/2009/10/restful-daydream-4/comment-page-1/#comment-1747 Michael Marth Wed, 07 Oct 2009 15:44:29 +0000 http://blog.technologyofcontent.com/?p=110#comment-1747 <p>Hi, interesting post. Some of my thoughts about it here [1].</p> <p>But why do you say that "jackrabbit HTTP/webdav remoting layer is not a REST layer"?</p> <p>Cheers Michael</p> <p>[1] http://dev.day.com/microsling/content/blogs/main/restfuldaydream.html</p> Hi, interesting post. Some of my thoughts about it here [1].

But why do you say that “jackrabbit HTTP/webdav remoting layer is not a REST layer”?

Cheers Michael

[1] http://dev.day.com/microsling/content/blogs/main/restfuldaydream.html

]]> By: justin http://blog.technologyofcontent.com/2009/10/restful-daydream-4/comment-page-1/#comment-1739 justin Wed, 07 Oct 2009 07:39:29 +0000 http://blog.technologyofcontent.com/?p=110#comment-1739 <p>The jackrabbit HTTP/webdav remoting layer is not a REST layer, but it would be a useful addition to the standard, and would help some people, and it would certainly allow interop testing of non Java implementations. It is not really the kind of model I had in mind though...</p> <p>In terms of who is ready to invest money, thats a good point, and one of the things I am trying to find out. It may be that the timing is not right now; there is a demand for it but not a willingness to spend the time now...</p> The jackrabbit HTTP/webdav remoting layer is not a REST layer, but it would be a useful addition to the standard, and would help some people, and it would certainly allow interop testing of non Java implementations. It is not really the kind of model I had in mind though…

In terms of who is ready to invest money, thats a good point, and one of the things I am trying to find out. It may be that the timing is not right now; there is a demand for it but not a willingness to spend the time now…

]]> By: Stephane Croisier http://blog.technologyofcontent.com/2009/10/restful-daydream-4/comment-page-1/#comment-1738 Stephane Croisier Wed, 07 Oct 2009 07:04:08 +0000 http://blog.technologyofcontent.com/?p=110#comment-1738 <p>One of the most critized point about the JCR is of course the "J" letter at the beginning. What would be perhaps interesting could be the extraction of the section 3 of the spec (Repository Model) and to try to transform it into a language agnostic RESTful Model. Then you would of course have to host and standardize it under anyother umbrella than the JCP. Such a JCR 3.0 revision would then only be the details of the JEE instance.</p> <p>Now which organisation could host such a generic model (OASIS; IETF;...)? Which legal issues with the current JCP process which should has some IP rights on all these resources?</p> <p>I am not part of the JCP/JSR170/283 expert group, but I am sure this topic was already discussed last year. Especially with the start and raise of CMIS. But now with the apparition of PHP "forks", yes I agree, it would perhaps make sense to host/maintain & discuss the model outside of a pure Java/JCP lobby.</p> <p>Now all these standardization effort requires lots of time and energy. So after the JCR and CMIS who is ready to invest more money into this?</p> <p>Stephane</p> One of the most critized point about the JCR is of course the “J” letter at the beginning. What would be perhaps interesting could be the extraction of the section 3 of the spec (Repository Model) and to try to transform it into a language agnostic RESTful Model. Then you would of course have to host and standardize it under anyother umbrella than the JCP. Such a JCR 3.0 revision would then only be the details of the JEE instance.

Now which organisation could host such a generic model (OASIS; IETF;…)? Which legal issues with the current JCP process which should has some IP rights on all these resources?

I am not part of the JCP/JSR170/283 expert group, but I am sure this topic was already discussed last year. Especially with the start and raise of CMIS. But now with the apparition of PHP “forks”, yes I agree, it would perhaps make sense to host/maintain & discuss the model outside of a pure Java/JCP lobby.

Now all these standardization effort requires lots of time and energy. So after the JCR and CMIS who is ready to invest more money into this?

Stephane

]]> By: Bertrand Delacretaz http://blog.technologyofcontent.com/2009/10/restful-daydream-4/comment-page-1/#comment-1730 Bertrand Delacretaz Tue, 06 Oct 2009 19:28:19 +0000 http://blog.technologyofcontent.com/?p=110#comment-1730 <p>Justin - many thanks for this post, it is great to see such a proposal from someone else than one of my usual JCR suspects! (and I apologize if I should have added you to that list earlier ;-) I don't know much about AIIM but if you envision coming up with "more standardized architectures and semantics and open source implementations", which makes perfect sense, Apache seems like a good fit as well. Jackrabbit 1.6 does provide an http remoting layer, which is not complete but quite usable already. Having a standardized (as in "industry standard" at least) RESTful interface on top of JCR often comes up in discussions with Jackrabbit/Sling folks, so it might be worth discussing your ideas there.</p> <p>[1] http://dev.day.com/microsling/content/blogs/main/jrnativehttp.html</p> Justin – many thanks for this post, it is great to see such a proposal from someone else than one of my usual JCR suspects! (and I apologize if I should have added you to that list earlier ;-) I don’t know much about AIIM but if you envision coming up with “more standardized architectures and semantics and open source implementations”, which makes perfect sense, Apache seems like a good fit as well. Jackrabbit 1.6 does provide an http remoting layer, which is not complete but quite usable already. Having a standardized (as in “industry standard” at least) RESTful interface on top of JCR often comes up in discussions with Jackrabbit/Sling folks, so it might be worth discussing your ideas there.

[1] http://dev.day.com/microsling/content/blogs/main/jrnativehttp.html

]]> By: Tweets that mention RESTful daydream #4 – Technology of Content -- Topsy.com http://blog.technologyofcontent.com/2009/10/restful-daydream-4/comment-page-1/#comment-1724 Tweets that mention RESTful daydream #4 – Technology of Content -- Topsy.com Tue, 06 Oct 2009 15:57:31 +0000 http://blog.technologyofcontent.com/?p=110#comment-1724 <p>[...] This post was mentioned on Twitter by Claude Vedovini, Michael Kowalski and Justin Cormack. Justin Cormack said: blog post on rest content repositories that I promised way back http://bit.ly/27RECr (@parkcoll as discussed the other week) [...]</p> [...] This post was mentioned on Twitter by Claude Vedovini, Michael Kowalski and Justin Cormack. Justin Cormack said: blog post on rest content repositories that I promised way back http://bit.ly/27RECr (@parkcoll as discussed the other week) [...]

]]>