Create, edit, delete exposed via Web Service API - best design pattern?

My advice will be to separate the Create/Delete/Edit operatios from the UserSettings entity. Keep UserSettings as pure DataContract of the service.

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.