Comment 4 for bug 933844

Updating with a comment. Now that the WADLs in the doc/src/docbkx/openstack-api-site/src/wadls are not "to spec" I'm rethinking this... not to get into analysis paralysis, but I don't know how to share WADLs with specs if there are some server params documented in the WADL in doc/src/docbkx/openstack-api-site/src/wadls/compute-api that are not "to spec" - this is wrapped up in the effort to clean up at http://wiki.openstack.org/DisableServerExtensions. Even with the cleanup, will the compute-api WADL be to spec? I'm not sure.

I'm rethinking the approach here to try to separate specifications from developer documents. I believe that WADL remains as the extremely lightweight (amount of content) reference information. But I'm not sure about sharing content with specs. Only Identity completely contains the spec doc with WADL inside now. And on api.openstack.org, the WADLs strive for "truth" rather than spec as a quick reference guide.

As a result, let's leave this as-is (Triaged, Med) but leave it unassigned while continuing to seek the right overall solution.