February 2007 - tdwg-tag - lists.tdwg.org

Re: [tdwg-tapir] tapir clients?
by Kevin Richards 06 Mar '07

06 Mar '07

I will be working on a Microsoft .NET server implementation of TAPIR. Also, how LSID resolution fits in with TAPIR providers. And looking at hooking up different data sources (other than DBs) at the TAPIR server end. I will put more details on the TAPIR web site when things are more definite and I get the chance. Kevin Richards >>> Dave Vieglais <vieglais(a)ku.edu> 28/02/2007 11:52:06 a.m. >>> Hi Tapirologists, There's the PyWrapper and TapirLink for the server side of the protocol, but I was wondering if: a) there's other server implementations and b) what client implementations are out there It might be worthwhile starting a "Software" page on the wiki to provide pointers to the various projects implementing TAPIR. cheers, Dave V. _______________________________________________ tdwg-tapir mailing list tdwg-tapir(a)lists.tdwg.org http://lists.tdwg.org/mailman/listinfo/tdwg-tapir ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ WARNING: This email and any attachments may be confidential and/or privileged. They are intended for the addressee only and are not to be read, used, copied or disseminated by anyone receiving them in error. If you are not the intended recipient, please notify the sender by return email and delete this message and any attachments. The views expressed in this email are those of the sender and do not necessarily reflect the official views of Landcare Research. Landcare Research http://www.landcareresearch.co.nz ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

2 1

[tdwg-tapir] tapir clients?
by Dave Vieglais 28 Feb '07

28 Feb '07

Hi Tapirologists, There's the PyWrapper and TapirLink for the server side of the protocol, but I was wondering if: a) there's other server implementations and b) what client implementations are out there It might be worthwhile starting a "Software" page on the wiki to provide pointers to the various projects implementing TAPIR. cheers, Dave V.

5 7

[tdwg-tapir] Changes during the TAPIR workshop
by Renato De Giovanni 24 Feb '07

24 Feb '07

Dear all, During the TAPIR workshop in the last week we identified a few points in the protocol and specification that still deserved changes. As you could see from the notifications, I already updated the protocol schema. The specification was also replaced by a new version. Here's the list of changes: - Correction: "envelope" parameter on search operations should be turned on by default. - Included note about the possibility of restricting the allowable domains related to the location of stylesheets that are specified through the "xslt" parameter. When the stylesheet comes from an unknown location it can be ignored with a corresponding warning being raised in the diagnostics section. - Added specific XML Schema capability for xsd:include. - Included note about the fact that a provider is not forced to guarantee the entire validity of search responses according to the XML Schema defined in the response structure, except to the extent of its own declared XML Schema capabilities. - Included recommendation for providers to raise warnings instead of errors when an unsupported XML Schema construct is found in the response structure. - Included new search parameter called "omit-ns" instructing providers to omit or not namespace delarations and the corresponding prefixes in search responses when the envelope is turned off. - Included a new attribute "required" for both concepts and variables in the output model mapping (defaults to false). When required, providers should raise an error when the concept is unmapped, or the variable is not available or the corresponding value is null. - Node paths in output model mapping were not considering namespaces. When the response structure needs to make use of different namespaces, all namespaces need to be declared in the output model element and the nodes referenced in the xpaths must include the associated namespace prefix. I also took the liberty to make this additional change since it can impact streaming (I forgot to mention it during the workshop): - Removed requirement that providers must automatically turn on envelopes in search responses when an error occurs. Please, let us all know if there are any further suggestions, objections or remaing issues. TapirLink (and probably PyWrapper) still need to be updated in the next few days. A more detailed report about the workshop will be prepared and soon made publicly available. New developements related to TAPIR were started (including a concept name server, a harvester and a provider test suite). One thing that was proposed during the workshop was to use this mailing list also for development discussions about any tool related to TAPIR - we assumed that everybody in this list would be interested. For now I really think we need to concentrate this kind of discussions in a single place, but if the list becomes too busy we can easily change later. Best Regards! -- Renato

1 0

[tdwg-tapir] r892 - tapir/dev/schema
by svn＠rs.tdwg.org 24 Feb '07

24 Feb '07

Author: RenatoDeGiovanni Date: 2007-02-24 13:45:12 +0100 (Sat, 24 Feb 2007) New Revision: 892 Modified: tapir/dev/schema/tapir.xsd Log: Fixed schema location related to the reserved "xml" prefix. Modified: tapir/dev/schema/tapir.xsd =================================================================== --- tapir/dev/schema/tapir.xsd 2007-02-24 12:35:39 UTC (rev 891) +++ tapir/dev/schema/tapir.xsd 2007-02-24 12:45:12 UTC (rev 892) @@ -26,7 +26,7 @@   <xsd:import namespace="http://www.w3.org/XML/1998/namespace" - schemaLocation="http://www.w3.org/2001/03/xml.xsd"/> + schemaLocation="http://www.w3.org/2001/xml.xsd"/> <xsd:import namespace="http://purl.org/dc/elements/1.1/" schemaLocation="dc.xsd"/> <xsd:import namespace="http://purl.org/dc/terms/"

1 0

[tdwg-tapir] r890 - tapir/dev/schema
by svn＠rs.tdwg.org 24 Feb '07

24 Feb '07

Author: RenatoDeGiovanni Date: 2007-02-24 13:34:05 +0100 (Sat, 24 Feb 2007) New Revision: 890 Modified: tapir/dev/schema/tapir.xsd Log: Created new type for the global element "variable" and extended the elements "concept" and "variable" in the output model mapping to include the new optional attribute called "required". Modified: tapir/dev/schema/tapir.xsd =================================================================== --- tapir/dev/schema/tapir.xsd 2007-02-24 11:54:43 UTC (rev 889) +++ tapir/dev/schema/tapir.xsd 2007-02-24 12:34:05 UTC (rev 890) @@ -281,9 +281,25 @@ <xsd:annotation> <xsd:documentation>Multiple mappings represent concatenation.</xsd:documentation> </xsd:annotation> - <xsd:element ref="concept"/> + <xsd:element name="concept"> + <xsd:complexType> + <xsd:complexContent> + <xsd:extension base="conceptType"> + <xsd:attribute name="required" type="xsd:boolean" use="optional" default="false"/> + </xsd:extension> + </xsd:complexContent> + </xsd:complexType> + </xsd:element> <xsd:element ref="literal"/> - <xsd:element ref="variable"/> + <xsd:element name="variable"> + <xsd:complexType> + <xsd:complexContent> + <xsd:extension base="variableType"> + <xsd:attribute name="required" type="xsd:boolean" use="optional" default="false"/> + </xsd:extension> + </xsd:complexContent> + </xsd:complexType> + </xsd:element> </xsd:choice> <xsd:attribute name="path" type="simpleXPathType" use="required"/> </xsd:complexType> @@ -673,15 +689,6 @@ </xsd:annotation> </xsd:element>  - <xsd:element name="variable" substitutionGroup="expression"> - <xsd:annotation> - <xsd:documentation>An element to represent specific values - from the service local environment.</xsd:documentation> - </xsd:annotation> - <xsd:complexType> - <xsd:attribute name="name" type="variableNameType" use="required"/> - </xsd:complexType> - </xsd:element> <xsd:simpleType name="predefinedVariableNamesType"> <xsd:restriction base="xsd:string"> <xsd:enumeration value="date"> @@ -714,6 +721,15 @@ <xsd:simpleType name="variableNameType"> <xsd:union memberTypes="predefinedVariableNamesType xsd:string"/> </xsd:simpleType> + <xsd:complexType name="variableType"> + <xsd:attribute name="name" type="variableNameType" use="required"/> + </xsd:complexType> + <xsd:element name="variable" type="variableType" substitutionGroup="expression"> + <xsd:annotation> + <xsd:documentation>An element to represent specific values + from the service local environment.</xsd:documentation> + </xsd:annotation> + </xsd:element>

1 0

[tdwg-tapir] r889 - tapir/dev/schema
by svn＠rs.tdwg.org 24 Feb '07

24 Feb '07

Author: RenatoDeGiovanni Date: 2007-02-24 12:54:43 +0100 (Sat, 24 Feb 2007) New Revision: 889 Modified: tapir/dev/schema/tapir.xsd Log: Included optional search parameter "omit-ns". Modified: tapir/dev/schema/tapir.xsd =================================================================== --- tapir/dev/schema/tapir.xsd 2007-02-24 00:29:16 UTC (rev 888) +++ tapir/dev/schema/tapir.xsd 2007-02-24 11:54:43 UTC (rev 889) @@ -765,6 +765,7 @@ <xsd:attributeGroup ref="globalParametersGroup"/> <xsd:attributeGroup ref="pagingParametersGroup"/> <xsd:attribute name="envelope" type="xsd:boolean" use="optional" default="true"/> + <xsd:attribute name="omit-ns" type="xsd:boolean" use="optional" default="false"/> </xsd:complexType> </xsd:element> </xsd:choice>

1 0

[tdwg-tapir] r887 - tapir/dev/schema
by svn＠rs.tdwg.org 23 Feb '07

23 Feb '07

Author: RenatoDeGiovanni Date: 2007-02-24 00:59:45 +0100 (Sat, 24 Feb 2007) New Revision: 887 Modified: tapir/dev/schema/tapir.xsd Log: Added missing XML Schema capability for xsd:include. Modified: tapir/dev/schema/tapir.xsd =================================================================== --- tapir/dev/schema/tapir.xsd 2007-02-22 23:24:12 UTC (rev 886) +++ tapir/dev/schema/tapir.xsd 2007-02-23 23:59:45 UTC (rev 887) @@ -1,4 +1,4 @@ -<?xml version="1.0"?> +<?xml version="1.0"?>  <xsd:schema targetNamespace="http://rs.tdwg.org/tapir/1.0" xmlns="http://rs.tdwg.org/tapir/1.0" @@ -1089,6 +1089,9 @@ <xsd:element name="import" minOccurs="0"> <xsd:complexType/> </xsd:element> + <xsd:element name="include" minOccurs="0"> + <xsd:complexType/> + </xsd:element> <xsd:element name="references" minOccurs="0"> <xsd:annotation> <xsd:documentation>The global use of the tags grouped here when locally

1 0

[tdwg-guid] ZooBank Guiding Principles Document
by Richard Pyle 23 Feb '07

23 Feb '07

Greetings TDWGers: First, my apologies for the cross-posting (a sentence many of you will read three or four times in the next few minutes...) Attached to this email message is a PDF document representing a draft version of the "Guiding Principles and Policies" for the future development of ZooBank, the proposed electronic registry of Zoological names and nomenclatural acts, as governed by the ICZN Code. A copy of this document has also been temporarily placed at this URL: http://www2.bishopmuseum.org/iczn/docs/ZooBank-GPP.pdf A more permanent home for the evolving document will be posted as soon as it is established. Please take the time to review this document and provide comments, criticisms and questions. This message has been distributed to the ZooBank email list, ICZN email list, TAXACOM, and TDWG email lists. Please feel free to forward this message and the document to any individuals or discussion forums with an interest in the future development of ZooBank. As stated in the document itself, from this point forward the goal is to develop ZooBank in a completely transparent way, with as much community input as possible. All feedback via whatever mechanism is, of course, most welcomed! However, to help consolidate the discussions, as much of the feedback as possible should be posted through the ZooBank email list. Information for how to subscribe to that list and access its archives is available here: http://list.afriherp.org/mailman/listinfo/zoobank-list Obviously, feedback on any aspect of this document, or relating to ZooBank in general, will be gratefully received. In particular, however, it would be most helpful to receive comments on what minimal data attributes (and in what format) should be required in order for a record to be considered "verified", and what standards of quality control should be applied to such records. There will be a gathering of a number of ICZN Commissioners at the IUBS Meeting in Washington, D.C., in May (http://www7.nationalacademies.org/IUBS/), so it would be especially useful to have feedback before then. Aloha, Richard L. Pyle, PhD Commissioner, International Commission for Zoological Nomenclature Database Coordinator for Natural Sciences and Associate Zoologist in Ichthyology Department of Natural Sciences, Bishop Museum 1525 Bernice St., Honolulu, HI 96817 Ph: (808)848-4115, Fax: (808)847-8252 email: deepreef(a)bishopmuseum.org http://hbs.bishopmuseum.org/staff/pylerichard.html

1 0

[tdwg-guid] The TDWG GUID mailing list and wiki have moved
by Ricardo Pereira 22 Feb '07

22 Feb '07

Dear TDWG-GUID subscribers, Along with other TDWG on-line resources, the TDWG-GUID mailing list and wiki have now been moved to the new TDWG servers. This message has been sent using the new list to tdwg-guid(a)lists.tdwg.org. The new web address for the list is: http://lists.tdwg.org/mailman/listinfo/tdwg-guid The new web address for the wiki is: http://wiki.tdwg.org/GUID No action needs to be taken, except new messages to the GUID list should be sent to tdwg-guid(a)lists.tdwg.org. To edit content on the wiki, please visit the web address above and log in using your TDWG account credentials. Those without a TDWG account will be contacted separately and given instructions on how to register for an account. TDWG thanks the University of Kansas Natural History Museum and Biodiversity Research Center, Jim Beach and Rob Dewhirst in particular for kindly and efficiently running this list for us. TDWG also thanks the Global Biodiversity Information Facility (GBIF), Donald Hobern, Ciprian Vizitiu and Andrei Cenja in particular for running our wiki and for their continued support to the new TDWG on-line infrastructure. Please email me for any further information on the TDWG lists and wiki. Best Wishes Ricardo Pereira TDWG Systems Administrator TDWG Infrastructure Project (TIP) ricardo(a)tdwg.org

1 0

[tdwg-tapir] xslt stylesheets
by Markus Döring 20 Feb '07

20 Feb '07

Hi, we had a discussion at the developer meeting last week about security issues when allowing arbitrary xslts to be included in TAPIR responses. This allows people to transmit illegal content from your service domain. When playing with Firefox I found they dont even allow to apply stylesheets that come from a different domain as the XML containing the PI: http://developer.mozilla.org/en/docs/ XSL_Transformations_in_Mozilla_FAQ#Why_isn.27t_my_stylesheet_applied.3F This is very inconvenient, but I guess TAPIR services could behave the same way. Apply stylesheets only if they are coming from the same domain. Have a nice week everyone, Markus

1 0