- From: Alexandre Passant <alexandre.passant@deri.org>
- Date: Mon, 8 Nov 2010 06:11:23 +0800
- To: public-xg-ssn@w3.org
Hi all, I've made a few sanity tests to check the current SSN ontology * Compliance with the LOD principles, using Vapour [1] Some tests fail here. http://validator.linkeddata.org/vapour?vocabUri=http%3A%2F%2Fpurl.oclc.org%2FNET%2Fssnx%2Fssn&classUri=http%3A%2F%2F&propertyUri=http%3A%2F%2F&instanceUri=http%3A%2F%2F&defaultResponse=dontmind&userAgent=vapour.sourceforge.net - 1st request while dereferencing resource URI without specifying the desired content type (HTTP response code should be 303 (redirect)):Failed => AFAIK, purl allows to specify a 303 rather than a 302 when redirecting, so that should be easy to fix - 2nd request while dereferencing resource URI without specifying the desired content type (Content type should be 'application/rdf+xml'):Failed => That can be fixed on the /2005/Incubator/ssn/wiki/images/3/36/ folder with a .htaccess file, containing AddType application/rdf+xml .xml * Semantic / syntactic validation, using Sindice inspector [2] 100% OK http://inspector.sindice.com/inspect?url=http%3A%2F%2Fpurl.oclc.org%2FNET%2Fssnx%2Fssn&content=&doTriplesValidation=1&doSyntaxValidation=1 Hope that helps, Alex. [1] http://validator.linkeddata.org/ [2] http://inspector.sindice.com/ -- Dr. Alexandre Passant Digital Enterprise Research Institute National University of Ireland, Galway :me owl:sameAs <http://apassant.net/alex> .
Received on Sunday, 7 November 2010 22:12:41 UTC