RE: WebID-ISSUE-4 (bblfish): Detail Authorization "protocol" using WebID

Some groups get upset when I do what Ive done in this email: respond to X topic with something related - but only just. Those groups are often using email headers and threads as their issue tracking mechanism. It requires certain user behaviour to work, and easy compliance may well assume researcher-type tool chains and researcher-grade discipline when handling email. 
 
Does the W3C issue tracker work the same way, or is it based scanning the content (vs headers) of the emails for certain tags, only?
 
I remember spending about a year promoting the use of S/MIME in web-based email user agents in the days when this notion - which does away with SMTP/POP3/IMAP  - was not popular. Least to say, it took a lot of work to legitimize what we now take for granted. in that vein, to best get in the mindset of W3C, should I perhaps work with W3C project/groupware tools that are website based - staying away from mailing list type tools, interactions and culture?
 
> To: public-xg-webid@w3.org
> From: sysbot+tracker@w3.org
> Date: Thu, 27 Jan 2011 17:17:58 +0000
> Subject: WebID-ISSUE-4 (bblfish): Detail Authorization "protocol" using WebID
> 
> 
> WebID-ISSUE-4 (bblfish): Detail Authorization "protocol" using WebID
> 
> http://www.w3.org/2005/Incubator/webid/track/issues/4
> 
> Raised by: Henry Story
> On product: 
> 
> Doing some of what OAuth does using WebID seems to require not much more than adding one relation to a Personal Profile document, and having servers use WebID authentication.
> 
> A very initial idea of how this can work was written up in the blog post
> "Sketch of a RESTful photo Printing service with foaf+ssl"
> 
> http://blogs.sun.com/bblfish/entry/sketch_of_a_restful_photo
> 
> 
> Some research is being done on this to extend. It would require some implementations.
> 
> We need to compare the possibilities enabled by this to what is done with OAuth, the same way we have worked on comparisons with OpenID.
> 
> 
> 
> 
>