Re: [PyWrapper-devel] [tdwg-tapir] RE: WG: tapir: capabilities

[Renato De G. <re...@cr...>]

OK, Markus. Agreed.
But maybe we could also consider an empty metadata response, because
"dct:modified" will likely require interaction with the DB. And it could
take some time for the larger ones (experience from DiGIR).

Regards,
--
Renato

> I have implemented the log-only request now and would like to suggest the
> following:
>
> 1) add "log-only" attribute to responeOperationGroup. Ive chosen
> "log-only" cause we already have there an attribute "apply-xslt"
> 2) add a mandatory boolean attribute "logRequestsDenied" to the operation
> element in a capabilities request
> 3) use existing responses for the log-only request. So if you do a search
> with log-only active, you will get an empty search response back. Thats
> much easier to implement and doesnt require any change in the schema. The
> same works with inventories. Pong, Capa & Meta responses dont cost much
> anyway, so we could do a normal response (if anyway uses log-only with
> those requests at all)
>
>
> Does everyone agree to this?
> The schema is already updated for this.
>
>
> Markus