[Osr-101] Specifying the delete operation

[Andreas Wuest]

Hi

On 5.10.2006 22:01 Uhr, Thomas Comiotto wrote:

> How about
> ..
> <open/>
> <delete uri="doc?cmd?delete"/>
> ..

As it stands right now, this would result in

<introspection>
   <edit mime-type="application/xhtml+xml" name="Foo">
     <open url="http://foo.bar.com/foo.xhtml" method="GET"/>
     <delete uri="http://foo.bar.com/foo.xhtml?delete"/>
   </edit>

   <edit mime-type="application/xhtml+xml" name="Bar">
     <open url="http://foo.bar.com/bar.xhtml" method="GET"/>
     <delete uri="http://foo.bar.com/bar.xhtml?delete"/>
   </edit>
</introspection>

with which I would be most unhappy, because delete has nothing to do 
with edit.

A few weeks ago, we had some talk about having <resource> elements, i.e.

<introspection>
   <resource  name="Foo">
     <open url="http://foo.bar.com/foo.xhtml" method="GET"/>
     <delete uri="http://foo.bar.com/foo.xhtml?delete"/>
     <edit mime-type="application/xhtml+xml">
       <open url="http://foo.bar.com/foo.xhtml?edit" method="GET"/>
     </edit>
   </resource>

   <resource  name="Bar">
     <open url="http://foo.bar.com/bar.xhtml" method="GET"/>
     <delete uri="http://foo.bar.com/bar.xhtml?delete"/>
     <edit mime-type="application/xhtml+xml">
       <open url="http://foo.bar.com/bar.xhtml?edit" method="GET"/>
     </edit>
   </resource>
</introspection>

or something similar (the edit stuff might change). This would be much 
cleaner. IIRC, everyone agreed on doing it this way, but we never got 
around to draft out the spec for this... :(

Anyway, I would prefer it if we would switch over to resources, and then 
add the delete operation there.

> Or do you refer to removing resources from the site tree?

Well, it should have the effect of not showing it to the user anymore. 
If the server really deletes the resource is of no interest, because 
e.g. a SVN based server could simply remove the file and all its 
references. As long as it does it inside the same transaction, deleted 
resources can get resurrected easily later on. But if the server prefers 
to simply not serve the resource anymore, this would be ok as well.

-- 
Kind regards,
Andi