[tdwg-tapir] reload / expire external resources

Donald Hobern dhobern at gbif.org
Thu Jan 5 15:38:56 CET 2006

It certainly makes sense, but I would expect our external documents to be
static and relatively rarely changed, so it may be hard for resource
providers to use the expiry value sensibly.  The availability of the reload
option in the request documents may also just encourage it to get used on
every request (particularly since our requests are almost never

Might it just be simpler to drop these attributes and leave it to provider
developers to supply configuration options on how long they should cache
external documents?  I know that going with b) and c) is much more proper,
but I'm not sure that it is worth it in our context.

Donald Hobern (dhobern at gbif.org)
Programme Officer for Data Access and Database Interoperability 
Global Biodiversity Information Facility Secretariat 
Universitetsparken 15, DK-2100 Copenhagen, Denmark
Tel: +45-35321483   Mobile: +45-28751483   Fax: +45-35321480

-----Original Message-----
From: tdwg-tapir-bounces at lists.tdwg.org
[mailto:tdwg-tapir-bounces at lists.tdwg.org] On Behalf Of "Döring, Markus"
Sent: 05 January 2006 15:12
To: tdwg-tapir at lists.tdwg.org
Subject: [tdwg-tapir] reload / expire external resources

Hello everyone,
I am in the process of scanning the schema for errors and update our
examples in the SVN.

Currently there's a reload attribute in the searchTemplateGroup used by the
inline search operation & the template definition. It doesnt really make
sense for the template document, does it?

How should we handle this in general, maybe for all external resources?
a) dont do anything about caching. remove reload/expire attributes
b) allow external documents to specify an expiry date (like http)
c) add optional reload attribute to all references to external docs

In my implementation it was quite important to cache external documents that
1) need to be parsed/processed, like the xml schema docs and 2) that are not
accessible all the time.

So I think I am in favor of b) and c) actually. The requestor can always
specify a reload and the external resource provider can specify a likely
expiry date.

Does this make sense or just complicates things?


tdwg-tapir mailing list
tdwg-tapir at lists.tdwg.org

More information about the tdwg-tag mailing list