Shared Review Web Services Feature

Question

The shared review feature is an extremely powerful feature that brings acrobat and pdf files to a whole new level.  Shared review currently allows 3 repository types (Network Folder, SharePoint workspace, and Web server folder).  These are all great for simple reviews and workflows, but i think that the process could be much more flexible and robust if adobe were to add a "Web Services" method.  This would allow for developers to have a lot more control of the annotation data.  In particular here's what it would do in my case:
Permissions: we already have a coldfusion application that has thousands of users.  Users log in and coldfusion handles all of the permissions, who can view what document, and what they can do to the document in terms of making annotations, or even editing annotations of others if they are the supervisor. (some people need to view the document with others comments but shouldn't be able to make comments themselves)
Layering: we would like to adapt more of a layers concept of annotations.  with web services, we could allow for the user to select the layers they want to view in an html frame and then our web service could return just those annotations for display.
I havent put much thought into it but you could even use it to connect to live cycle web services, the possibilities are endless.

Answer 1

I posted "Is Adobe discontinuing support for SOAP collaboration?" in this forum and in the SDK and Scripting forums, and Brian and I have already discussed Adobe's willingness to abandon solutions that they previously evangelized (SOAP, ADBC) and to hell with anyone who drank their kool-aid back in the day.
Brian and I have very similar issues (esp. auditability) because he and I work in industries with lots of government oversight (he in aerospace and me in nuclear).   So, the issue for us is not NEW features but maintaining backward-compatibility with old features so that we can continue to fulfill these requirements, and if Adobe wants to cut us loose then we have no choice but to find a non-Adobe alternative.
Having said all that, I agree that adding Web services to "shared reviews" would be a good first step by Adobe toward allowing those of us who are relying on SOAP and other "deprecated" features to transition to shared reviews, but only if allows us to upload reviewer comments to a central server.  However, that still won't be enough for us unless we can continue to manage document reviews centrally.  All of our review cycles (i.e. the docs, reviewers, and schedules) are determined by our project managers, and that information is entered into our system by a single service administrator (or is imported programmatically from Active Directory and from our project management system).  So, for us to migrate to shared reviews requires an enhanced API so we can continue to set up reviews programmatically and not have to rely on the cumbersome and clunky one-document-at-a-time approach in the shared review model.