A little off topic, but it occurs to me that a great deal of work is still ongoing with TAPIR, which suggests to me that it may be warranted to re-state my request for a simple message type - a log request. This request would be the same as a search request, except that the caller doesn't need a response. Providers would use this type of request to log data usage if the data were retrieved from a cache elsewhere. I remember talking about this in Berlin, at which time there was supposed to be a feature freeze. Clearly we've gone beyond that, so I'm requesting it again.
<br><br><div><span class="gmail_quote">On 7/17/06, <b class="gmail_sendername">Renato De Giovanni</b> <<a href="mailto:email@example.com">firstname.lastname@example.org</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi,<br><br>If I remember well, the "view" operation was re-included in the<br>protocol just to handle query templates, especifically for TapirLite<br>providers. So if someone wants to query a provider using some
<br>external output model that should be dynamically parsed, then the<br>"search" operation must be used instead (using either XML or simple<br>GET request). View operations are really bound to query templates,<br>
and they are not allowed to specify "filter" or "partial" parameters.<br>--<br>Renato<br><br>On 17 Jul 2006 at 21:26, "Döring, Markus" wrote:<br><br>> I was just about to edit the schema and realizing that output models
<br>> are only specified for searches. but what about views? they use<br>> query templates, yes. but only the ones listed in capabilities? we<br>> should have dynamic ones here as well I think. And they link back to
<br>> static/dynamic models.<br>><br>> So should models maybe become a seperate section not tight to<br>> search/view operations? I am going to modify the schema nevertheless<br>> already to accomodate the changes below - ignoring views for now.
<br>><br>> Markus<br><br>_______________________________________________<br>tdwg-tapir mailing list<br><a href="mailto:email@example.com">firstname.lastname@example.org</a><br><a href="http://lists.tdwg.org/mailman/listinfo/tdwg-tapir">