Hi all, It's been great to see the discussion spurred by Asger's proposed new REST api. I think there is plenty more fruitful discussion/experimentation to be had on that front, particularly around the granularity of changes and the relationship with transactions. I agree with Asger that this makes sense to explore initially as an add-on and not a full replacement of the existing REST api.
The short-term goal is to finish the existing REST API for the 3.3 release. We know many people have come to depend on it and it's been in beta status too long -- it needs to be solidified so we can move to deprecate the old API-A-Lite and API-M-Lite. To that end, we had a good discussion in Tuesday's committer call about one of the major outstanding items: Exposing the relationship management methods (add/purge/get) that are currently only present in API-M SOAP. I've written up a strawman proposal for adding this functionality to the existing REST api. This is really a reflection of where we got to in the discussion on Tuesday. If you've got an interest in this area (especially if you're a consumer of the existing REST api!) will you take a few minutes and have a look? http://fedora-commons.org/confluence/display/FCREPO/RESTful+Relationship+API Thanks, Chris ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Fedora-commons-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/fedora-commons-developers
