design - How to represent a transformation in REST? -

I would like to write a service that takes an XML file (any XML file) and some parameters as input and Inputs the converted XML file as its output, for example, if I need a service that removes the attachment, then the criteria will be an intensity range ( darn < Code> f *** ) and the mode change ( f *** ing , f @ %% ing or flipping ) The actual format of the XML is irrelevant, the output will always be the same format as the input. (Before you say that this is a meaningless exercise: this is not the service that I really want to make.)

Although I have used RAT-based services, I Designing them and I do not really know how it should fit in the resource / archive idiom and more importantly, how it should be liked, avoid the WADL and instead interface Describe yourself or not just the right equipment for it?

to:

Post the same method to cover the following tasks Designed to allow: ... to provide a block of data, such as the result of submitting a form, the data-handling process;

For example:

  Post / Profit Remover? Level = 3 Content Type: App / XML & lt; Foo & gt; & Lt; Blaza & gt; Hey & lt; / Bla & gt; & Lt; / Foo & gt; = & Gt; 200 OK content type: App / XML & lt; Foo & gt; & Lt; Blaza & gt; Defecation & lt; / Bla & gt; & Lt; / Foo & gt;