REPORT method considered harmful

I don't have any time to take this on, but at some point the TAG
should consider an issue regarding the problems caused by the REPORT
method and its harm to the Web architecture due to

   a) replacing identification of important resources via URIs
      with limited indirect access via a related resource:

      <> section 3.6

      [should have used a link to a version history resource].

   b) use as an ad-hoc query-language without consideration for caches:


      [should be using links to related resources].

   c) batching multiple independent requests through a single method:


      [should be using a client implementation that supported  

I would not be surprised to see SOAP messages carried via REPORT.
The method has no distinguishable semantics from POST aside from
the ability to claim that it isn't just tunneling through POST.


Roy T. Fielding                            <>
Chief Scientist, Day Software              <>

Received on Thursday, 29 December 2005 01:05:14 UTC