Well, since you blogged about us yourself, this is a gentle reminder that we are still here, and we are doing quite well. Here's just one interesting mail from our mailing list: http://lists.cocoondev.org/pipermail/daisy/2006-December/005569.html - and that's just the mundane Wiki case which only a fraction of our capabilities. ;-)
We can't claim JSR170-political-correctness, but our users never complain about that. And having a high-profile user might tease us into revamping our comment system by untying it from the repository.
Re: JSR170: I never heard someone swapping repository implementations underneath a functioning CMS, as it only then that it becomes clear to users that a CMS is much more than a repository, and that there are more ties between a CMS and its repo than what the vendors want you to believe.
re:
Posted by
admin
at
2007-01-02 08:12 AM
Steven,
You sure know how to throw a monkey wrench into the mix ;-).
My gut tells me that over time JSR-170 will be more and more a absolute requirement. That is, the argument for JSR-170 JCR would be made more on non-technical/social merits than technical ones.
In summary, I liked your product when it came out; unfortunately, as much as I hate to say this, sometimes standardization has its merits. The way I look at it, Roy Fielding of ReST fame is Chief Scientist as Day, the primary developer of JCR. So, therefore, despite not having looked deeply into it myself, I'm fairly confident that the specification (unlike EJB) is fundementally sound.
Carlos
Re:Daisy
Posted by
Anonymous User
Anonymous Userat
2007-01-02 08:13 AM
Daisy looks interesting to me. In a way it reminds me of Lenya. But, even if I concede JSR-170, I still have some issues. My two main uses of a CMS are photo-storage and weblog.
I have a few hundred photos in Plone. I put them in there by dropping 50 at a time into a "Webdav folder". I see no mention of Webdav on the Daisy feature list. I couldn't possibly bring myself to import them via a web form, one by one. Further, Plone lets me store my 3 megapixel photo, but transforms the photo into a reasonable size for the user. This way, I'm really storing my true content there. I like that.
I also see no mention of a Weblog "product" (that's what Plone calls them anyway). True, a CMS can function as a weblog. But I need trackbacks and comments, captcha for comments, trackback moderation, categories (where one entry can apply to multiple categories), etc.
We can't claim JSR170-political-correctness, but our users never complain about that. And having a high-profile user might tease us into revamping our comment system by untying it from the repository.
Re: JSR170: I never heard someone swapping repository implementations underneath a functioning CMS, as it only then that it becomes clear to users that a CMS is much more than a repository, and that there are more ties between a CMS and its repo than what the vendors want you to believe.
You sure know how to throw a monkey wrench into the mix ;-).
My gut tells me that over time JSR-170 will be more and more a absolute requirement. That is, the argument for JSR-170 JCR would be made more on non-technical/social merits than technical ones.
In summary, I liked your product when it came out; unfortunately, as much as I hate to say this, sometimes standardization has its merits. The way I look at it, Roy Fielding of ReST fame is Chief Scientist as Day, the primary developer of JCR. So, therefore, despite not having looked deeply into it myself, I'm fairly confident that the specification (unlike EJB) is fundementally sound.
Carlos
I have a few hundred photos in Plone. I put them in there by dropping 50 at a time into a "Webdav folder". I see no mention of Webdav on the Daisy feature list. I couldn't possibly bring myself to import them via a web form, one by one. Further, Plone lets me store my 3 megapixel photo, but transforms the photo into a reasonable size for the user. This way, I'm really storing my true content there. I like that.
I also see no mention of a Weblog "product" (that's what Plone calls them anyway). True, a CMS can function as a weblog. But I need trackbacks and comments, captcha for comments, trackback moderation, categories (where one entry can apply to multiple categories), etc.