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

[<m.d...@BG...>]

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.=20

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
 =20

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