[tdwg-tag] LSID HTTP Proxy - design question
n.nicolson at rbgkew.org.uk
Tue Apr 21 18:41:22 CEST 2009
I've been looking into setting up an HTTP proxy for the ipni.org LSIDs. I've read the usage recommendations at http://wiki.tdwg.org/twiki/bin/view/GUID/LsidHttpProxyUsageRecommendation but want to ask a question re the design of the proxy itself, ie:
Should an HTTP proxy for LSIDs behave as:
(1) a webapp that acts as an LSID "client"
(2) a mechanism to issue redirects to the metadata address as specified in the LSID authority WSDL
The latter is simple - I can just set up a mod_rewrite rule so that
http://lsid.ipni.org/[lsid] is redirected to the HTTP URL for the metadata for the specified LSID. This will of course only work for LSIDs for which ipni.org is the authority, but I think that is OK.
If the former, I'll need to encode the resolution process: ie parse the LSID, extract the authority, do the DNS lookup, get the WSDL, construct the address etc, BUT it will mean that the HTTP LSID proxy is dependent upon correct functioning of the LSID infrastructure (DNS SRV records, authority WSDL etc). I guess the TDWG LSID proxy behaves this way, but that is to be expected as it can be used as an HTTP proxy for *any* LSID.
In summary option (1) treats the proxied LSID as *an LSID*, the other really just treats it as a character string.
Which is preferred?
- Nicola Nicolson
- Science Applications Development,
- Royal Botanic Gardens, Kew,
- Richmond, Surrey, TW9 3AB, UK
- email: n.nicolson at rbgkew.org.uk
- phone: 020-8332-5766
More information about the tdwg-tag