I don't know if you can publish the URL to a RESTful service to UDDI
(Sam might know). Assuming you can, it's not going to look like other
services in the directory.
do we need to take care of "multiple-accidental-clicks-for-credit-card-purchase-order" kind of problems in the RESTFul web service code itself when we are using POST URL's to expose the service (resource)
In the sample Chapter 4: The Resource Oriented Architecture) you actually give "a row in a database" (p.81) as an example of a resource. Isn't that level of granularity typically a bit too fine? Wouldn't you usually aggregate your resources to a much coarser granularity?
Another example of a resource that really surprised me was "the result of running an algorithm". How is that different from deploying a service at a specific URL?