[Auscope-geosciml] HTTP URIs as identifiers in Testbed 4 WebServices

Tellez-Arenas Agnes a.tellez-arenas at brgm.fr
Wed Mar 31 04:43:02 EDT 2010

I am a little concerned about perfomances issues (and risk to be "black-listed" by the  http://resource.geosciml.org <http://resource.geosciml.org/>  server) when a client application wishes to dereference a controlled concept.
In the following example, if a client application is parsing a GeoSciML file to translate all the terms used, this client application should request  http://resource.geosciml.org <http://resource.geosciml.org>  for each term. And, since http://resource.geosciml.org <http://resource.geosciml.org/>  could be implemented thanks to Apache rewriting rules, each request to http://resource.geosciml.org <http://resource.geosciml.org/>  leads to another request to another server (for the example, let's say http://gsv-ws.dpi.vic.gov.au <http://gsv-ws.dpi.vic.gov.au> ).
That could lead to two problems: performances (always bad performances when a connexion is openned, and there are two requests for each term, even if the second one is hidden and managed by http://resource.geosciml.org <http://resource.geosciml.org/> , it is time consumming), and security if the security of  http://resource.geosciml.org <http://resource.geosciml.org>  (or of http://gsv-ws.dpi.vic.gov.au <http://gsv-ws.dpi.vic.gov.au/> ) does not like to receive a lot of requests from the same server, at almost the same time. Usually, the server who is requesting is black-listed.
I guess that the other choice is to use the codeSpace to harvest the content of the vocabulary (in the case of a vocabulary. I agree that for a WFS it is not so simple). In the following example, I suppose that http://resource.geosciml.org/uri-cgi/classifierscheme/cgi/simplelithology/200811 <http://resource.geosciml.org/uri-cgi/classifierscheme/cgi/simplelithology/200811>  should give the whole SKOS (in that case) file containing all the definitions, and that the unique identifier of the Concept is http://resource.geosciml.org/uri-cgi/classifier/cgi/simplelithology/200811/basalt
<gsml:lithology codeSpace="http://resource.geosciml.org/uri-cgi/classifierscheme/cgi/simplelithology/200811">
What do you think?
Best regards

De : auscope-geosciml-bounces at lists.arcs.org.au [mailto:auscope-geosciml-bounces at lists.arcs.org.au] De la part de Alistair Ritchie
Envoyé : jeudi 18 mars 2010 03:05
À : AuScope-GeoSciML
Objet : [Auscope-geosciml] HTTP URIs as identifiers in Testbed 4 WebServices

Hi Everyone

There has been discussion about the use of HTTP URIs as identifers for features. Testbed 4 seems like a good opportunity to test their use and finally resolve URN issues that have plagued us for some time.

I've therefore put together a proposal for the use of HTTP URIs in GeoSciML Testbed 4 services and posted it on the TWiki. Pretty much the entire proposal has synthesised what I've read in previous email threads or accompanying documentation. (Mistakes and misinterpretations are all my fault.)

The proposal is here: https://www.seegrid.csiro.au/twiki/bin/view/CGIModel/PersistentIdentifiersInGeoSciMLServices

Discussion is here: https://www.seegrid.csiro.au/twiki/bin/view/CGIModel/PersistentIdentifiersInGeoSciMLServicesDiscussion

I'd be grateful is we could keep discussion on the discussion page and only update the proposal page as decisions are made. That way it is a clean resource that can be referred to with minimal confusion as we implement.



Alistair Ritchie
Department of Primary Industries | Melbourne, Victoria, Australia
Tel: +61 3 9658 4512 | Fax: +61 3 9658 4555

Pensez a l'environnement avant d'imprimer ce message
Think Environment before printing
Le contenu de ce mel et de ses pieces jointes est destine a l'usage exclusif du (des) destinataire(s) designe
(s) comme tel(s). 
En cas de reception par erreur, le signaler e son expediteur et ne pas en divulguer le contenu. 
L'absence de virus a ete verifiee e l'emission, il convient neanmoins de s'assurer de l'absence de 
contamination a sa reception.
The contents of this email and any attachments are confidential. They are intended for the named recipient
(s) only. 
If you have received this email in error please notify the system manager or the sender immediately and do 
not disclose the contents to anyone or make copies. 
eSafe scanned this email for viruses, vandals and malicious content.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opengeospatial.org/pipermail/geosciml/attachments/20100331/9cd5edd6/attachment.htm>

More information about the GeoSciML mailing list