- From: Henry Story <henry.story@bblfish.net>
- Date: Fri, 6 Jan 2012 00:46:51 +0100
- To: Jürgen Jakobitsch <j.jakobitsch@semantic-web.at>
- Cc: "public-xg-webid@w3.org XG" <public-xg-webid@w3.org>
On 6 Jan 2012, at 00:40, Henry Story wrote: > > On 6 Jan 2012, at 00:31, Jürgen Jakobitsch wrote: > >> hi henry, >> >> http://2sea.org/sea.jsp#j still fails with "keys in profile don't match key in certificate for http://2sea.org/sea.jsp#j". > > When I try the above url on http://www.w3.org/2007/08/pyRdfa/ I get an empty RDF file with just namespaces > > @prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> . > @prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> . > @prefix xhv: <http://www.w3.org/1999/xhtml/vocab#> . > @prefix xml: <http://www.w3.org/XML/1998/namespace> . > @prefix xsd: <http://www.w3.org/2001/XMLSchema#> . > > If I run that parser on strict I get > > Traceback (most recent call last): > File "/usr/local/lib/python2.4/site-packages/PythonLib-IH/pyRdfa/__init__.py", line 520, in processURI > return _process(input, uri, outputFormat, options) > File "/usr/local/lib/python2.4/site-packages/PythonLib-IH/pyRdfa/__init__.py", line 387, in _process > raise RDFaError, msg > RDFaError: Parsing error in input file: "mismatched tag: line 1, column 970" > > Parsing error in input file: "mismatched tag: line 1, column 970" > > > Perhaps that is the error? No, it looks like this is an error with pyRDFa ( and perhaps your server depending on how pyRDFa does that). http://2sea.org/sea.jsp Works but http://2sea.org/sea.jsp#i does has a parse error. So it could be simply that I also don't remove the # before making the request, assuming wrongly perhaps that the service does it... I'll check that... Henry > > Henry > > > PS. I want to later when I get time write it, to have a service to allow people to test the transformation directly. I can see that this would be very useful. > >> >> i have taken all whitespaces out, pyRdfa and appspot extraction says it looks good. >> i have also deleted the compiled jsp from tomcat's work directory to be sure you get the latest version without whitespaces and newlines in key. >> uri also works with openlink [1] and webidrealm. >> >> >> maybe you find something in your logs... >> i recommend feeding the uri to your rdfa parser and check what happens with the hexBinary. >> what rdfa parser do you use? >> >> note : http://eastghost.org/ghost.ttl#j => success >> >> [1] http://id.myopenlink.net/ods/webid_demo.html >> >> wkr j >> >> ----- Original Message ----- >> From: "Henry Story" <henry.story@bblfish.net> >> To: "public-xg-webid@w3.org XG" <public-xg-webid@w3.org> >> Sent: Friday, January 6, 2012 12:16:16 AM >> Subject: fixed https://foafssl.org/test/WebId >> >> I fixed the test end point at >> >> https://foafssl.org/test/WebId >> >> The issue was (as I thought) that foafssl.org was not updating its caches on failure of a WebID authentication. >> >> This meant that people who tried to connect once with a broken foaf file, would not be able to re-connect later with a good one. It should work now. >> >> Henry >> >> Social Web Architect >> http://bblfish.net/ >> >> >> >> -- >> | Jürgen Jakobitsch, >> | Software Developer >> | Semantic Web Company GmbH >> | Mariahilfer Straße 70 / Neubaugasse 1, Top 8 >> | A - 1070 Wien, Austria >> | Mob +43 676 62 12 710 | Fax +43.1.402 12 35 - 22 >> >> COMPANY INFORMATION >> | http://www.semantic-web.at/ >> >> PERSONAL INFORMATION >> | web : http://www.turnguard.com >> | foaf : http://www.turnguard.com/turnguard >> | skype : jakobitsch-punkt > > Social Web Architect > http://bblfish.net/ > Social Web Architect http://bblfish.net/
Received on Thursday, 5 January 2012 23:47:22 UTC