In my opinion, ADO.Net data services are designed to create quiet services that are closely related to your domain model, that is, the models themselves are published, and then they talk about some form of DTO, etc.
Using it for RPC style services seems to be bad, although, unfortunately, even some very simple functions, such as the ability to perform filtered calculations, etc., are not available, which often means that you end up using some kind of RPC to meet the requirements of your customers i.e. you can display the paged grid, etc.
WCF 3.5 pre-SP1 RESTful, SP1 Uri, ATOMPub, , , , JSON, XML, ATOM , , , , CSV, URL , munging .., / .
WCF - , , .. URL-, , - - ADO.Net AtomPub.
-, , , , ADO.Net Data - (, ajax, silverlight), URL , ... REST (, MVC ), , , API ..
2 !