- From: Melvin Carvalho <melvincarvalho@gmail.com>
- Date: Mon, 29 Apr 2013 14:23:21 +0200
- To: Dileepa Jayakody <dileepajayakody@gmail.com>
- Cc: Mo McRoberts <Mo.McRoberts@bbc.co.uk>, public-webid <public-webid@w3.org>
- Message-ID: <CAKaEYh+AvrQwFN_f9SRwZ1=3=mx1ov0CQfWt4jmEeLN5Spo6kA@mail.gmail.com>
On 29 April 2013 13:14, Dileepa Jayakody <dileepajayakody@gmail.com> wrote: > I think some blog-posts/tutorials on WebID usecases will come in handy > for beginners to try out stuff. > Building an eco-system around this technology will really help early > adopters :) > Thanks all, for your valuable ideas! > +1 Henry used to maintain an excellent blog series when he was at Sun. https://blogs.oracle.com/bblfish/ We could certainly do with some more blogs and a jumping in point for beginners, but im unsure anyone has had time to gather things together recently > > Dileepa > > > On Mon, Apr 29, 2013 at 3:37 AM, Melvin Carvalho <melvincarvalho@gmail.com > > wrote: > >> >> >> >> On 28 April 2013 22:53, Dileepa Jayakody <dileepajayakody@gmail.com>wrote: >> >>> Thanks Mo for the explanation. >>> As you have mentioned, WebID's architecture is very similar to the >>> inherent architecture of the web itself. >>> WebID has been evolving since 2004/2005, but compared to OpenID, the >>> adoption of WebID is not very high, if I may say. Please correct me if I'm >>> wrong. Is this due to constant changes in the WebID spec, or due to lack of >>> fully-fledged implementations of WebID? >>> Thoughts are welcome.. >>> >> >> I think until recently WebID has been perceived to be closely coupled to >> X.509 client certificates. And some that have evaluated X.509 client >> certificates perceive the user experience to be a challenge to present to a >> mass audience. >> >> In truth the advantages of WebID are in the loose coupling of concepts, >> universality, and adherence to web standards. >> >> The community have has started to present the ideas as more modular now, >> including splitting out the specifications. >> >> I think the main thing is that there are not too many people building >> apps right now for WebID but a relatively large number of people focusing >> on completing the infrastructure. So 1-2 developers can probably make a >> noticeable difference! :) >> >> >>> >>> Thanks, >>> Dileepa >>> >>> On Sun, Apr 28, 2013 at 11:55 PM, Mo McRoberts <Mo.McRoberts@bbc.co.uk>wrote: >>> >>>> >>>> On 28 Apr 2013, at 19:01, Dileepa Jayakody <dileepajayakody@gmail.com> >>>> wrote: >>>> >>>> > Thanks a lot Melvin for your reply. >>>> > I will further read about WebID docs to gather more knowledge. >>>> > I took a look at myprofile project, created my own WebID : >>>> https://my-profile.eu/people/dileepa/card#me :) >>>> > >>>> > Another aspect I'm looking at is, how WebID differs from existing >>>> identity technologies like OpenID. Is the fundamental difference, the >>>> support for linked-data and the stateless nature of WebID? >>>> >>>> With WebID, the only thing you need a *server* to be able to do is >>>> serve static resources (it can do more, but that's all it HAS to do). The >>>> smarts are essentially a facet of the crypto itself (and the fact that a >>>> thing you can prove you control connects to another thing you prove you >>>> control). WebID is, in effect, as distributed and decentralised as the Web >>>> itself and has a very low barrier to entry. >>>> >>>> With OpenID, you're creating an account on a service and pointing >>>> people at that (possibly in a round-about way). >>>> >>>> M. >>>> >>>> > >>>> > Thanks, >>>> > Dileepa >>>> > >>>> > >>>> > >>>> > >>>> > On Sun, Apr 28, 2013 at 7:05 PM, Melvin Carvalho < >>>> melvincarvalho@gmail.com> wrote: >>>> > >>>> > >>>> > >>>> > On 28 April 2013 13:21, Dileepa Jayakody <dileepajayakody@gmail.com> >>>> wrote: >>>> > Hi All, >>>> > >>>> > My Name is Dileepa Jayakody, a Sri Lankan research student interested >>>> in semantic web, linked-data and digital identity concepts. I have been >>>> learning about WebID for past few days and I'm most interested about >>>> possibilities of WebID integration to provide a verified digital identity >>>> solution across multiple domains (SNS, email, blogs etc). >>>> > >>>> > I'm interested in applying for Google Summer of Code (GSoC) this year >>>> and there are 2 projects which were most interesting for me. Both are from >>>> Apache Stanbol project which suits my research interests on semantic web. >>>> > 1. Using Semantic Concepts in Federated Social Web : STANBOL-1009 >>>> > 2. Entity Disambiguation for Stanbol : STANBOL-1037 >>>> > >>>> > Welcome, sounds great! >>>> > >>>> > >>>> > For both use-cases I find WebID an excellent option. >>>> > For use-case-1, WebID can be used for federated social-web as it >>>> supports a user-profile with links to friend lists, photos etc, with >>>> ability to control access to such resources over social-graph. >>>> > For use-case-2 'Person' disambiguation can be tacked by developing a >>>> disambiguation algorithm by using WebID as a verified digital identity. >>>> > >>>> > Stanbol uses Apache Clerezza as a RDF engine, and AFAIK Clerezza >>>> supports WebID. However when I discussed with Stanbol guys on their >>>> dev-list I got to know the WebID support is currently disabled due to >>>> recent changes in WebID spec and changes in jaxrs architecture. >>>> > >>>> > I am sure Henry Story can help with this, he's done quite a bit of >>>> work with Clerzza. >>>> > >>>> > >>>> > I would very much like to know your suggestions and ideas on >>>> integrating WebID for above use-cases. Further I would like your help in >>>> understanding the architecture of WebID and how I can integrate it in >>>> existing systems to provide a verified digital identity. >>>> > >>>> > WebID is split into two architectural concepts. One is Identity, >>>> which means using an HTTP URI to denote a Person. The other is >>>> authentication, so that a server can verify that identity. Currently >>>> there's one authentication spec which documents WebID over TLS, but more >>>> are possible. >>>> > >>>> > A project you may also want to look at is : >>>> > >>>> > http://myprofile-project.org/ >>>> > >>>> > >>>> > Looking forward to your ideas. >>>> > >>>> > Thanks, >>>> > Dileepa >>>> > >>>> > >>>> >>>> >>>> -- >>>> Mo McRoberts - Analyst - BBC Archive Development, >>>> Zone 1.08, BBC Scotland, 40 Pacific Quay, Glasgow G51 1DA, >>>> MC3 D4, Media Centre, 201 Wood Lane, London W12 7TQ, >>>> 0141 422 6036 (Internal: 01-26036) - PGP key CEBCF03E >>>> >>>> >>>> >>>> ----------------------------- >>>> http://www.bbc.co.uk >>>> This e-mail (and any attachments) is confidential and >>>> may contain personal views which are not the views of the BBC unless >>>> specifically stated. >>>> If you have received it in >>>> error, please delete it from your system. >>>> Do not use, copy or disclose the >>>> information in any way nor act in reliance on it and notify the sender >>>> immediately. >>>> Please note that the BBC monitors e-mails >>>> sent or received. >>>> Further communication will signify your consent to >>>> this. >>>> ----------------------------- >>>> >>>> ---------- Forwarded message ---------- >>>> From: Mo McRoberts <Mo.McRoberts@bbc.co.uk> >>>> To: Dileepa Jayakody <dileepajayakody@gmail.com> >>>> Cc: Melvin Carvalho <melvincarvalho@gmail.com>, public-webid < >>>> public-webid@w3.org> >>>> Date: Sun, 28 Apr 2013 18:25:46 +0000 >>>> Subject: Re: WebID Integration Usecases with Semantic Web >>>> >>>> On 28 Apr 2013, at 19:01, Dileepa Jayakody <dileepajayakody@gmail.com> >>>> wrote: >>>> >>>> > Thanks a lot Melvin for your reply. >>>> > I will further read about WebID docs to gather more knowledge. >>>> > I took a look at myprofile project, created my own WebID : >>>> https://my-profile.eu/people/dileepa/card#me :) >>>> > >>>> > Another aspect I'm looking at is, how WebID differs from existing >>>> identity technologies like OpenID. Is the fundamental difference, the >>>> support for linked-data and the stateless nature of WebID? >>>> >>>> With WebID, the only thing you need a *server* to be able to do is >>>> serve static resources (it can do more, but that's all it HAS to do). The >>>> smarts are essentially a facet of the crypto itself (and the fact that a >>>> thing you can prove you control connects to another thing you prove you >>>> control). WebID is, in effect, as distributed and decentralised as the Web >>>> itself and has a very low barrier to entry. >>>> >>>> With OpenID, you're creating an account on a service and pointing >>>> people at that (possibly in a round-about way). >>>> >>>> M. >>>> >>>> > >>>> > Thanks, >>>> > Dileepa >>>> > >>>> > >>>> > >>>> > >>>> > On Sun, Apr 28, 2013 at 7:05 PM, Melvin Carvalho < >>>> melvincarvalho@gmail.com> wrote: >>>> > >>>> > >>>> > >>>> > On 28 April 2013 13:21, Dileepa Jayakody <dileepajayakody@gmail.com> >>>> wrote: >>>> > Hi All, >>>> > >>>> > My Name is Dileepa Jayakody, a Sri Lankan research student interested >>>> in semantic web, linked-data and digital identity concepts. I have been >>>> learning about WebID for past few days and I'm most interested about >>>> possibilities of WebID integration to provide a verified digital identity >>>> solution across multiple domains (SNS, email, blogs etc). >>>> > >>>> > I'm interested in applying for Google Summer of Code (GSoC) this year >>>> and there are 2 projects which were most interesting for me. Both are from >>>> Apache Stanbol project which suits my research interests on semantic web. >>>> > 1. Using Semantic Concepts in Federated Social Web : STANBOL-1009 >>>> > 2. Entity Disambiguation for Stanbol : STANBOL-1037 >>>> > >>>> > Welcome, sounds great! >>>> > >>>> > >>>> > For both use-cases I find WebID an excellent option. >>>> > For use-case-1, WebID can be used for federated social-web as it >>>> supports a user-profile with links to friend lists, photos etc, with >>>> ability to control access to such resources over social-graph. >>>> > For use-case-2 'Person' disambiguation can be tacked by developing a >>>> disambiguation algorithm by using WebID as a verified digital identity. >>>> > >>>> > Stanbol uses Apache Clerezza as a RDF engine, and AFAIK Clerezza >>>> supports WebID. However when I discussed with Stanbol guys on their >>>> dev-list I got to know the WebID support is currently disabled due to >>>> recent changes in WebID spec and changes in jaxrs architecture. >>>> > >>>> > I am sure Henry Story can help with this, he's done quite a bit of >>>> work with Clerzza. >>>> > >>>> > >>>> > I would very much like to know your suggestions and ideas on >>>> integrating WebID for above use-cases. Further I would like your help in >>>> understanding the architecture of WebID and how I can integrate it in >>>> existing systems to provide a verified digital identity. >>>> > >>>> > WebID is split into two architectural concepts. One is Identity, >>>> which means using an HTTP URI to denote a Person. The other is >>>> authentication, so that a server can verify that identity. Currently >>>> there's one authentication spec which documents WebID over TLS, but more >>>> are possible. >>>> > >>>> > A project you may also want to look at is : >>>> > >>>> > http://myprofile-project.org/ >>>> > >>>> > >>>> > Looking forward to your ideas. >>>> > >>>> > Thanks, >>>> > Dileepa >>>> > >>>> > >>>> >>>> >>>> -- >>>> Mo McRoberts - Analyst - BBC Archive Development, >>>> Zone 1.08, BBC Scotland, 40 Pacific Quay, Glasgow G51 1DA, >>>> MC3 D4, Media Centre, 201 Wood Lane, London W12 7TQ, >>>> 0141 422 6036 (Internal: 01-26036) - PGP key CEBCF03E >>>> >>>> >>>> >>> >> >
Received on Monday, 29 April 2013 12:23:51 UTC