W3C home > Mailing lists > Public > public-vocabs@w3.org > April 2014

Re: Socialnetworks of a person or organization

From: Kingsley Idehen <kidehen@openlinksw.com>
Date: Sat, 12 Apr 2014 16:12:53 -0400
Message-ID: <53499E45.3060807@openlinksw.com>
To: Wes Turner <wes.turner@gmail.com>
CC: public-vocabs@w3.org
On 4/12/14 1:43 PM, Wes Turner wrote:
> re: schema:webid :
>
>> >Effect:
>> >
>> >It just works! Entity disambiguation is in place, data consumers (subject to their mindset: structured data, linked data, semantic web) can all work with this without any disruption or "world view"  warfare triggers.
>> >
>> >Why does it just work?
>> >
>> >1. A webid or WebID is an HTTP URI that denotes an Agent (note: this has nothing to do with the WebID+TLS authentication protocol, this is simply about entity denotation, where the entity in question is an Agent i.e., person, organization, or bot)
>> >
>> >2. Using the fragment identifier implies no entity URI disambiguation heuristics.
>> >
>> >Conclusion:
>> >
>> ><http://schema.org/webid>  is a non disruptive relationship property for this kind of relation i.e., one that associates an entity with its description document (descriptor), implicitly .
> I would say +1 for 'schema:webid', but then how can I link to my Keybase.io?
>

schema:webkey "{your-public-key}" .

Basically, schema:webkey would be a relation for association with public 
keys .

-- 

Regards,

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







Received on Saturday, 12 April 2014 20:13:15 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:29:39 UTC