[tdwg-tapir] AW: [PyWrapper-devel] WG: tapir: capabilities

"Döring, Markus" m.doering at BGBM.org
Tue Jul 18 10:32:11 CEST 2006

yes and no.
sure you need a template for views. but do we force providers to register supported templates? If an implementation can handle dynamic models, it surely can handle "dynamic" templates. And even if a providers says I only understand those 4 models, all query templates based on those 4 models should be easy to be processed. So dynamic/static models are important for views as well, cause templates are based on them.

But if the intention of views was/is for TapirLite only, then registered lists of templates are needed and dynamic templates dont make too much sense. And searches and inventories without templates could always also be called through their respective GET versions as well. So yes, an implementation could process "dynamic" templates, but maybe we just dont need them. 

Then again if providers need to configure supported templates, all installations would be different - unless the implementation can handle "dynamic" templates and just retrieves all available query templates for their supported models from a central service and registers them automatically for the provider.

-- Markus

> -----Ursprüngliche Nachricht-----
> Von: pywrapper-devel-bounces at lists.sourceforge.net 
> [mailto:pywrapper-devel-bounces at lists.sourceforge.net] Im 
> Auftrag von Renato De Giovanni
> Gesendet: Montag, 17. Juli 2006 23:01
> An: tdwg-tapir at lists.tdwg.org
> Cc: pywrapper-devel at lists.sourceforge.net
> Betreff: Re: [PyWrapper-devel] WG: tapir: capabilities
> Hi,
> If I remember well, the "view" operation was re-included in 
> the protocol just to handle query templates, especifically 
> for TapirLite providers. So if someone wants to query a 
> provider using some external output model that should be 
> dynamically parsed, then the "search" operation must be used 
> instead (using either XML or simple GET request). View 
> operations are really bound to query templates, and they are 
> not allowed to specify "filter" or "partial" parameters.
> --
> Renato
> On 17 Jul 2006 at 21:26, "Döring, Markus" wrote:
> > I was just about to edit the schema and realizing that 
> output models 
> > are only specified for searches. but what about views? they 
> use query 
> > templates, yes. but only the ones listed in capabilities? we should 
> > have dynamic ones here as well I think. And they link back to 
> > static/dynamic models.
> > 
> > So should models maybe become a seperate section not tight to 
> > search/view operations? I am going to modify the schema 
> nevertheless 
> > already to accomodate the changes below - ignoring views for now.
> > 
> > Markus
> --------------------------------------------------------------
> -----------
> Take Surveys. Earn Cash. Influence the Future of IT Join 
> SourceForge.net's Techsay panel and you'll get the chance to 
> share your opinions on IT & business topics through brief 
> surveys -- and earn cash 
> http://www.techsay.com/default.php?page=join.php&p=sourceforge
> _______________________________________________
> PyWrapper-devel mailing list
> PyWrapper-devel at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/pywrapper-devel

More information about the tdwg-tag mailing list