Hi Kevin,<br>you're good:<br><br>---<br><span style="font-family: courier new,monospace;">python responsetests.py -v 20 -p "<a href="http://lsid.herbimi.info/TapirDotNET/tapir.aspx/herbIMI?op=inventory&count=true&concept=http://rs.tdwg.org/ontology/voc/TaxonOccurrence#/rdf:RDF/to:TaxonOccurrence/to:collector">
http://lsid.herbimi.info/TapirDotNET/tapir.aspx/herbIMI?op=inventory&count=true&concept=http://rs.tdwg.org/ontology/voc/TaxonOccurrence#/rdf:RDF/to:TaxonOccurrence/to:collector</a>"</span><br style="font-family: courier new,monospace;">
<br style="font-family: courier new,monospace;"><span style="font-family: courier new,monospace;">Testing: <a href="http://lsid.herbimi.info/TapirDotNET/tapir.aspx/herbIMI?op=inventory&count=true&concept=http://rs.tdwg.org/ontology/voc/TaxonOccurrence#/rdf:RDF/to:TaxonOccurrence/to:collector">
http://lsid.herbimi.info/TapirDotNET/tapir.aspx/herbIMI?op=inventory&count=true&concept=http://rs.tdwg.org/ontology/voc/TaxonOccurrence#/rdf:RDF/to:TaxonOccurrence/to:collector</a></span><br style="font-family: courier new,monospace;">
<span style="font-family: courier new,monospace;">INFO:root:[HTTP HEADER] content-length: 12019</span><br style="font-family: courier new,monospace;"><span style="font-family: courier new,monospace;">INFO:root:[HTTP HEADER] x-powered-by:
<a href="http://ASP.NET">ASP.NET</a></span><br style="font-family: courier new,monospace;"><span style="font-family: courier new,monospace;">INFO:root:[HTTP HEADER] set-cookie: ASP.NET_SessionId=uxfg0l55colhnjmxzinwxp55; path=/; HttpOnly
</span><br style="font-family: courier new,monospace;"><span style="font-family: courier new,monospace;">INFO:root:[HTTP HEADER] x-aspnet-version: 2.0.50727</span><br style="font-family: courier new,monospace;"><span style="font-family: courier new,monospace;">
INFO:root:[HTTP HEADER] server: Microsoft-IIS/6.0</span><br style="font-family: courier new,monospace;"><span style="font-family: courier new,monospace;">INFO:root:[HTTP HEADER] connection: close</span><br style="font-family: courier new,monospace;">
<span style="font-family: courier new,monospace;">INFO:root:[HTTP HEADER] pragma: no-cache:</span><br style="font-family: courier new,monospace;"><span style="font-family: courier new,monospace;">INFO:root:[HTTP HEADER] cache-control: private
</span><br style="font-family: courier new,monospace;"><span style="font-family: courier new,monospace;">INFO:root:[HTTP HEADER] date: Thu, 08 Nov 2007 21:29:37 GMT</span><br style="font-family: courier new,monospace;"><span style="font-family: courier new,monospace;">
INFO:root:[HTTP HEADER] content-type: text/xml; charset="utf-8"</span><br style="font-family: courier new,monospace;"><span style="font-family: courier new,monospace;">== Results ==</span><br style="font-family: courier new,monospace;">
<span style="font-family: courier new,monospace;">Test: "HTTP Status" [OK]: No Worries</span><br style="font-family: courier new,monospace;"><span style="font-family: courier new,monospace;">Test: "Response Encoding" [OK]: No Worries
</span><br style="font-family: courier new,monospace;"><span style="font-family: courier new,monospace;">Test: "Document Encoding" [OK]: No Worries</span><br><br>---<br><br>The GBIF rest service doesn't do quite so well though:
<br><br>---<br><span style="font-family: courier new,monospace;">python responsetests.py -v 20 -p "<a href="http://newportal.gbif.org/ws/rest/provider/list?stylesheet=&maxresults=10">http://newportal.gbif.org/ws/rest/provider/list?stylesheet=&maxresults=10
</a>"</span><br style="font-family: courier new,monospace;"><br style="font-family: courier new,monospace;"><span style="font-family: courier new,monospace;">Testing: <a href="http://newportal.gbif.org/ws/rest/provider/list?stylesheet=&maxresults=10">
http://newportal.gbif.org/ws/rest/provider/list?stylesheet=&maxresults=10</a></span><br style="font-family: courier new,monospace;"><span style="font-family: courier new,monospace;">INFO:root:[HTTP HEADER] date: Thu, 08 Nov 2007 21:37:01 GMT
</span><br style="font-family: courier new,monospace;"><span style="font-family: courier new,monospace;">INFO:root:[HTTP HEADER] transfer-encoding: chunked</span><br style="font-family: courier new,monospace;"><span style="font-family: courier new,monospace;">
INFO:root:[HTTP HEADER] connection: close</span><br style="font-family: courier new,monospace;"><span style="font-family: courier new,monospace;">INFO:root:[HTTP HEADER] content-type: text/xml</span><br style="font-family: courier new,monospace;">
<span style="font-family: courier new,monospace;">INFO:root:[HTTP HEADER] server: Apache/2.0.52 (Red Hat)</span><br style="font-family: courier new,monospace;"><span style="font-family: courier new,monospace;">== Results ==
</span><br style="font-family: courier new,monospace;"><span style="font-family: courier new,monospace;">Test: "HTTP Status" [OK]: No Worries</span><br style="font-family: courier new,monospace;"><span style="font-family: courier new,monospace;">
Test: "Response Encoding" [WARNING]: No character encoding was specified for the text/[*+]xml content type | "Content-type: text/xml"</span><br style="font-family: courier new,monospace;"><span style="font-family: courier new,monospace;">
Test: "Response Encoding" [WARNING]: Falling back to the RFC 3023 default of us-ascii character encoding.</span><br style="font-family: courier new,monospace;"><span style="font-family: courier new,monospace;">Test: "Document Encoding" [ERROR]: Bozo exception. | Document declared as us-ascii, but parsed as utf-8
</span><br style="font-family: courier new,monospace;"><br>---<br><br>These tests (plus a whole bunch more) will be available as an online service real soon, with the intent being to help data providers test their service fairly rigorously before exposing them to the real world.
<br><br>regards,<br> Dave V.<br><br><br>On Nov 8, 2007 1:46 PM, Kevin Richards <<a href="mailto:RichardsK@landcareresearch.co.nz">RichardsK@landcareresearch.co.nz</a>> wrote:<br>> <br>> <br>> Good spotting Dave.
<br>> <br>> This is fixed now in the TapirDotNET implementation of Tapir. <br>> I have updated the HerbIMI TapirDotNET implementation at<br>> <a href="http://lsid.herbimi.info/TapirDotNET/tapir.aspx/herbIMI">
http://lsid.herbimi.info/TapirDotNET/tapir.aspx/herbIMI</a> <br>> So if you could like to check this provider, I would be interested in your<br>> results. <br>> <br>> Kevin<br>> <br>> >>> "Dave Vieglais" <
<a href="mailto:vieglais@ku.edu">vieglais@ku.edu</a>> 9/11/2007 7:59 a.m. >>><br>> <br>> <br>> Hi Everyone,<br>> I've come across a minor issue with some existing TAPIR installations<br>> that should be easily fixed and will likely save some frustrations
<br>> down the road.<br>> <br>> The TAPIR spec<br>> (<a href="http://www.tdwg.org/dav/subgroups/tapir/1.0/docs/TAPIRSpecification_2007-07-18.html#toc16">http://www.tdwg.org/dav/subgroups/tapir/1.0/docs/TAPIRSpecification_2007-07-18.html#toc16
</a>)<br>> indicates a response Content-type of "text/xml". RFC 3023<br>> (<a href="http://www.ietf.org/rfc/rfc3023.txt">http://www.ietf.org/rfc/rfc3023.txt</a>) indicates that in this case,<br>> when no "charset" parameter is specified in the HTTP response header,
<br>> the implied character encoding of the response document is "us-ascii"<br>> (see s8.5).<br>> <br>> so for example:<br>> <br>> Good:<br>> response header = Content-type: text/xml; charset="utf-8"
<br>> <br>> response document signature = <?xml version="1.0" encoding="utf-8"?><br>> <br>> result = document is assumed to be UTF-8<br>> <br>> Not so good:<br>> response header = Content-type: text/xml
<br>> <br>> response document signature = <?xml version="1.0" encoding="utf-8"?><br>> <br>> result = document is assumed to be us-ascii<br>> <br>> <br>> All TAPIR installations that I've examined so far do not set a charset
<br>> value, and hence the character encoding of "us-ascii" is assumed by<br>> the consumer application, which is likely to cause some issues for<br>> consumer applications. This was also a significant issue for DiGIR
<br>> provider installations.<br>> <br>> The solution is likely to be quite simple, and there seems to be two<br>> basic options:<br>> <br>> 1. Configure the webserver / application to insert a charset value of
<br>> "UTF-8" to avoid the consumer falling back to the default of us-ascii.<br>> <br>> or<br>> <br>> 2. Return a Content-type of "Application/xml" or one of its subtypes.<br>> In this case RFC 3023 indicates the default character encoding should
<br>> be assumed to be UTF-8.<br>> <br>> Note that simply specifying the content type does not automatically<br>> make the response properly encoded - it is still up to the web<br>> application (TAPIR in this case) to ensure that the output stream is
<br>> actually UTF-8 encoded.<br>> <br>> regards,<br>> Dave V.<br>> _______________________________________________<br>> tdwg-tapir mailing list<br>> <a href="mailto:tdwg-tapir@lists.tdwg.org">tdwg-tapir@lists.tdwg.org
</a><br>> <a href="http://lists.tdwg.org/mailman/listinfo/tdwg-tapir">http://lists.tdwg.org/mailman/listinfo/tdwg-tapir</a><br>> <br><br>