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

types in 2.2 Publishing WebID Profile Document

From: elf Pavlik <perpetual-tripper@wwelves.org>
Date: Sat, 17 Dec 2011 11:55:57 +0000
To: public-xg-webid <public-xg-webid@w3.org>
Message-Id: <1324118669-sup-6962@hackers4peace.net>
Dear all,

Discussions on it have occurred in many threads already but I hope you don't mind that I start a new one =)

1. RDF/XML vs Turtle
Turtle looks much more readable/writable for a human, but I believe in most cases people won't read/write it by hand. For generating and parsing them, I know that all web platforms / frameworks can handle XML and developers have at least some familiarity with it. Not sure here how it looks with Turtle, at least myself I've never used it until now and for example just have seen one gem for Ruby language in early stage (0.1.0)  by Gregg Kellogg https://rubygems.org/gems/rdf-turtle

2. RDFa HTML
On one side very cool, on the other... I guess in many projects people who work on / maintain HTML templates may not know anything about RDFa =( I see having separate profile file only for parsing can help with avoiding collision between work of developers of data and developers of UI...


ATM somehow I like RDF/XML if we want to have common 'MUST' format, since I guess all developers and their existing toolboxes can deal with it. 


we could also start a wiki page for this topic and for every type of profile type have pros (+) and cons (-)


I would also like if we could have a validator + 'converter' service, where one can paste / link WebID profile in one format and get it in any other one. I guess people could also use it for making fixtures for their unit tests...


Here I may shoot bit more blind from now ;)

3.2.4.2 Verifying the WebID Claim states:

"To check a WebID claim one has to find if the graph returned by the profile relates the WebID to the Certificate Public Key with the cert:key relation. In other words one has to check if those statements are present in the graph."

can we brainstorm on all kind of options here?
json - everyone can work with it...
JWK: https://tools.ietf.org/html/draft-jones-json-web-key-01 mentioned in BrowserID - Verified Email Protocol spec


or even ones sounding exotic like:
webfinger profile?
someting in <meta> of html page? (like OpenID 2.0)

i haven't really play with RelMeAuth but see some nice simplicity in it: http://microformats.org/wiki/RelMeAuth maybe we can find some inspirations there?


Thanks + off to country side for the weekend =)
~ elf Pavlik ~
-- 
(living strictly moneyless already for over 2 years)
http://wwelves.org/perpetual-tripper
http://moneyless.info
http://hackers4peace.net
Received on Saturday, 17 December 2011 11:56:32 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Saturday, 17 December 2011 11:56:33 GMT