On 7/24/14 9:51 AM, Sarven Capadisli wrote:
On 2014-07-24 15:16, KANZAKI Masahide wrote:
One quick question: why almost all nodes in social web are labeled as
StatusNet ?

I'm not at all surprised by this.

How many social networking services or software can you think of makes their data available in RDF?

The StatusNet [1] [2] was one such software. Flagship site identi.ca [3] [4] - Nowadays it is powered differently [5] (i.e., no FOAF AFAIK).

It made a pretty good *dent*, don't you think? ;)

[1] http://status.net/
[2] http://en.wikipedia.org/wiki/StatusNet
[3] http://identi.ca/
[4] http://en.wikipedia.org/wiki/Identi.ca
[5] https://github.com/e14n/pump.io

-Sarven

It does have FOAF data, but discovery patterns obscure paths. The pattern for FOAF is: {resource-uri}/foaf

Example: <http://micro.fragdev.com/x11r5/foaf> .


Analysis:

[1] http://bit.ly/what-status-net-foaf-uris-denote -- Vapour Report

[2]
curl -IL http://micro.fragdev.com/x11r5/
HTTP/1.1 200 OK
Date: Thu, 24 Jul 2014 14:47:58 GMT
Server: Apache/2.2.22 (Debian)
X-Powered-By: PHP/5.4.4-14+deb7u11
Vary: Accept-Encoding,Cookie
Link: <http://micro.fragdev.com/.well-known/webfinger?resource=acct:[email protected]>; rel="lrdd"; type="application/xrd+xml"

[3]
curl -IL http://micro.fragdev.com/x11r5/foaf
HTTP/1.1 200 OK
Date: Thu, 24 Jul 2014 14:48:31 GMT
Server: Apache/2.2.22 (Debian)
X-Powered-By: PHP/5.4.4-14+deb7u11
Vary: Accept-Encoding,Cookie
Content-Type: application/rdf+xml


Yet another example of how discovery patterns continue to challenge Linked Open Data boostrap etc..


--
Regards,

Kingsley Idehen 
Founder & CEO
OpenLink Software
Company Web: http://www.openlinksw.com
Personal Weblog 1: http://kidehen.blogspot.com
Personal Weblog 2: 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
Personal WebID: http://kingsley.idehen.net/dataspace/person/kidehen#this

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

Reply via email to