...
- Sakai has migrated their Content Host Service to JCR, Sakai Wraps the JCR Factory API so that you are not exposed to how a JCR connection is retrieved, the JCR objects themselves are exposed to the user of the service so there is no need to learn another API. This presents a stronger case for use of JCR as an API for interacting with stores such as DSpace and Fedora, reuse of a Fedora JCR implementation may enable DSpace on Fedora, Sakai on Fedora, Sakai+DSpace on Fedora, etc. --Mark Diggory 17:44, 26 September 2008 (EDT)
...
- I have concerns that JCR's use of mixin properties is a bit arduous and obtuse, I have yet to find adequate description of the mixin properties--Mark Diggory 15:36, 26 September 2008 (EDT)
...
- _I think JCR relation objects should be evaluated in comparison to the REL-EXT section of a Fedora Object. Though, I'm unsure of the update policy on object with RELS_EXT, specifically given that the relationship is stored within the Fedora Object itself. _ --Mark Diggory 17:06, 26 September 2008 (EDT)
...
- Per my statement above, I think that JCR is onto something here, specifically that relationships may be expressed by some "authority" other than the Object owner, as such such relationships need to be modifiable and maintained independent of the objects themselves, allowing for various authorities o assert relations independently. --Mark Diggory 17:11, 26 September 2008 (EDT)
...