W3C home > Mailing lists > Public > public-xg-webid@w3.org > December 2011

Re: openid content negotiation RE: broken turtle

From: Kingsley Idehen <kidehen@openlinksw.com>
Date: Fri, 23 Dec 2011 09:51:16 -0500
Message-ID: <4EF49564.3060003@openlinksw.com>
To: public-xg-webid@w3.org
On 12/23/11 9:03 AM, Peter Williams wrote:
> since this project is closely tied to openid (historically), can we 
> all do proper content negotiation when GETting the identifier :-) I.e. 
> do it, not just talk about it in endless tutorials, tool demos, and 
> philosophy lectures?
>
> if one pings an the value of the foaf:openid property, one SHOULD be 
> able to negotiate "application/xrds+xml" per the standard attached to 
> the foaf declaration - so the openid metadata about the URI's 
> authority infrastucture (IDP) is returned.
>
> No, you dont get to opt out of this, just because you have an aversion 
> of some particular metadata blob format (its in XML), or you dont like 
> some namespace contention (XRI) or just object to the other web 
> committe (OASIS), or you have a cute little arrangement with a 
> (compromised) CA to stuff DNSSEC into a W3C standard. You implement 
> the standard, including the parts who design elements you disagreed 
> with. One openid provider here doesnt do it, and it breaks a cloud 
> interworking. I happen to have the skills to work around it, but 
> typically, noone will bother.

Peter,

I use a URI Debugger to quickly test content negotiation.

Here is a URL showcasing an example: 
http://linkeddata.informatik.hu-berlin.de/uridbg/index.php?url=http%3A%2F%2Fid.myopenlink.net%2Fdataspace%2Fperson%2FKingsleyUyiIdehen&useragentheader=&acceptheader=application%2Fxrds%2Bxml 



Kingsley
>
> We have to do it, not talk about it. Otherwise, folks like me CANNOT 
> adopt. We HAVE to wait (till it all matures).
> > Date: Fri, 23 Dec 2011 14:36:59 +0100
> > From: j.jakobitsch@semantic-web.at
> > To: bergi@axolotlfarm.org
> > CC: public-xg-webid@w3.org; home_pw@msn.com
> > Subject: Re: broken turtle
> >
> > hi bergi,
> >
> > thanks for pointing this out :
> >
> > i'm using openrdf-sesame-2.3.1 in webIDRealm which only knows about 
> application/x-turtle [1].
> > at least in 2.6.1 [2] this is fixed.
> >
> > i small test showed that i can parse this file [3] now correctly 
> with openrdfSesame.
> >
> > wkr http://www.turnguard.com/turnguard
> >
> > [1] 
> http://repo.aduna-software.org/svn/org.openrdf/sesame/tags/2.3.1/core/rio/api/src/main/java/org/openrdf/rio/RDFFormat.java
> > [2] 
> http://repo.aduna-software.org/svn/org.openrdf/sesame/tags/2.6.1/core/rio/api/src/main/java/org/openrdf/rio/RDFFormat.java
> > [3] http://rapstr1.blob.core.windows.net/ods/user.ttl#me
> >
> > ----- Original Message -----
> > From: "bergi" <bergi@axolotlfarm.org>
> > To: "Peter Williams" <home_pw@msn.com>
> > Cc: "j jakobitsch" <j.jakobitsch@semantic-web.at>, 
> public-xg-webid@w3.org
> > Sent: Friday, December 23, 2011 1:59:48 AM
> > Subject: Re: broken turtle
> >
> > The mime type for turtle is: text/turtle
> >
> > turtle spec:
> > http://www.w3.org/TeamSubmission/turtle/#sec-mime
> >
> > wikipedia:
> > http://en.wikipedia.org/wiki/Turtle_%28syntax%29
> >
> > Am 23.12.2011 01:27, schrieb Peter Williams:
> > >
> > >
> > > I assumed the same - server/service configuration error. But the
> > > semantic web is just a set of document byte streams, tagged with mime
> > > types, sitting on endpoints streaming UTF-8 bytes (for turtle).
> > >
> > >
> > > So, I checked the external interface for obvious issues. I didnt use
> > > curl, but did use an equivalent external interface tester.
> > >
> > >
> > > see http://tinyurl.com/6thzu4x This shows the external view (with
> > > content type, and byte level information transfer from the wire)
> > >
> > >
> > >
> > > More importantly (since its my data format mapper service)
> > > morper.talis.com cannot read any triples either.
> > >
> > >
> > >
> > > Some magic is required, beyond HTTP wire compliance.
> > >
> > >
> > >
> > > When talis puts the #tagged URI on the get, the server objects
> > > (correctly). Similarly the server attempts to deliver the object
> > > names in part %23 - which doesnt exist).
> > >
> > >
> > >
> > >
> > >
> > > Talis does claim to read a document, when teh webid is represented
> > > with the tagless path. it just treats the document as a null set of
> > > triples.
> > >
> > >
> > >
> > > Im guessing there is some wrong semicolon, or something. Perhaps
> > > there is a improper space before a dot, or something? Seems an old
> > > fashioned language, all super fussy about punctionation.
> > >
> > >
> > >
> > >
> > >
> > >> Date: Fri, 23 Dec 2011 01:04:28 +0100 From:
> > >> j.jakobitsch@semantic-web.at To: home_pw@msn.com CC:
> > >> public-xg-webid@w3.org Subject: Re: broken turtle
> > >>
> > >> hi,
> > >>
> > >> your server might not be conf'd properly.
> > >>
> > >> 1. when i check you'r the webID with tomcat's webIDRealm, openRDF
> > >> api tries to parse with the RDFXMLParser, so there might be
> > >> something wrong with the mime-type. 2. have you tried the several
> > >> responses from your server when using curl 2.1. curl
> > >> "http://rapstr1.blob.core.windows.net/ods/user.ttl" 2.2. curl
> > >> "http://rapstr1.blob.core.windows.net/ods/user.ttl#me" 2.3. curl
> > >> "http://rapstr1.blob.core.windows.net/ods/user.ttl%23me"
> > >>
> > >> wkr http://www.turnguard.com/turnguard
> > >>
> > >>
> > >> ----- Original Message ----- From: "Peter Williams"
> > >> <home_pw@msn.com> To: public-xg-webid@w3.org Sent: Thursday,
> > >> December 22, 2011 11:53:15 PM Subject: RE: broken turtle
> > >>
> > >>
> > >> @prefix peter: < https://rapstr1.blob.core.windows.net/ods/user.ttl
> > >> #> .
> > >>
> > >> if I use the explicit https scheme for the prefix of the subject,
> > >> and the SAN URI has an http URI, I assume there will no match.
> > >>
> > >> Since the RDfa example is relative, perhaps consider make the
> > >> turtle sample relative. Just do them the same way, that is, so the
> > >> SAN URI controls the http/https issues in the namespace. i think
> > >> this means make the subjkect's namespace the default (and move cert
> > >> namespace to an explicit tag).
> > >>
> > >> but what do I know...
> > >>
> > >>
> > >>
> > >>
> > >> From: home_pw@msn.com To: public-xg-webid@w3.org Date: Thu, 22 Dec
> > >> 2011 14:31:00 -0800 Subject: broken turtle
> > >>
> > >>
> > >>
> > >> Since Ive had two sites able to read a blog post with an bit of
> > >> annotated HTML act as a webid profile (tied to a cert), I
> > >> professionalized a bit.
> > >>
> > >> I built a turtle file, per the spec, and published it on a restful
> > >> file server (azure blob service). I configured things so the mime
> > >> type is application/turtle.
> > >>
> > >> Whats wrong? I tried it on FOAFSSL.ORG, which produced information
> > >> document in this report: http://wp.me/p1fcz8-1Kf
> > >>
> > >> -- | 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
> > >>
> > >
> >
> >
> > --
> > | 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
> >


-- 

Regards,

Kingsley Idehen	
Founder&  CEO
OpenLink Software
Company Web: http://www.openlinksw.com
Personal Weblog: http://www.openlinksw.com/blog/~kidehen
Twitter/Identi.ca handle: @kidehen
Google+ Profile: https://plus.google.com/112399767740508618350/about
LinkedIn Profile: http://www.linkedin.com/in/kidehen








Received on Friday, 23 December 2011 14:51:53 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 23 December 2011 14:51:53 GMT