URI for RESTful Web Services?

I'm not quite sure I understand either, but I understand that if you POST to example.com/resources/142 you are treating 142 as if it were a collection in it's own right and would be adding another item to that collection If it were blog.com/blog/142 142 might be a users blog and a POST would possible create a new Blog Post a PUT to 142 would either Update the whole of 142 or create the blog if it didn't exist.

I'm not quite sure I understand either, but I understand that if you POST to example.com/resources/142 you are treating 142 as if it were a collection in it's own right and would be adding another item to that collection. If it were blog.com/blog/142 142 might be a users blog and a POST would possible create a new Blog Post. A PUT to 142 would either Update the whole of 142 or create the blog if it didn't exist.

The example is probably a bad one. A better example in your case would be example.com/users/142 In REST, this is interpretted the same as example.com/users?id=142 as long on the server side you deal with the fact that the last part of the route is associated with an ID. Both of these would identify the user 142.

However, you would not generally use this with a POST, because POST is used for creation and you would not know the ID of the user you are creating at this point in most cases.

In your example, I would think of 142 as the resource name. Your POST might make new instances of "142" with their own id.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.