We discover this kind of class that could be useful for FOAF.
Role – A Role is a function of a User within a scope of a particular Forum, Site, etc.
Roles are used to express functions or access control privileges that Users may have.
So apparently, the ideal is to mix SIOC with the other ontology FOAF.
Effectively I can read it know on their homepage !
SIOC provides a Semantic Web ontology for representing rich data from the Social Web in RDF. It has recently achieved significant adoption through its usage in a variety of commercial and open-source software applications, and is commonly used in conjunction with the FOAF vocabulary for expressing personal profile and social networking information. By becoming a standard way for expressing user-generated content from such sites, SIOC enables new kinds of usage scenarios for online community site data, and allows innovative semantic applications to be built on top of the existing Social Web.
Why I’m interested by this topic ?
I’m trying to better understand how well Semantic web is documented and accessible, how HyperWeek could apply it with success in our offering. Learning what Tim Berners-Lee wants to mean when he says « Decentralized socialnetworks ».
SMOB is a distributed / decentralised microblogging system built on RDF and Semantic Web technologies, mainly SIOC and FOAF. Currently, we have simple prototypes of a publishing and an aggregating service, less than 100 lines of PHP code each.
There are different methods to decentralize content
the most popular is manual: copy-paste a line of code containing a link to a widget (social or not)
the « academic » buzz is on automation but tend to be not sustainable: URI, rdfs, micro-formats, etc
In both cases, business can be done.
Do you want that widget ? Pay it.
Do you want to be connected to our extented portable informations ? Pay it.
I see joint-ventures opportunities… The widget is more sustainable by its formal aspect: brandable, editable on params, etc
A lot of europeans companies have revenues from specific sides:
VPOD and their APIs
Netvibes and their widgets
I see telcoms looking for interoperabilities more than the web-side. They have to face a very fragmented device environment so they will be more willing not to face a crappy fragmented situation regarding data portability. The proof is the presence of Vodafone and Telecom Italia inside the W3C workshop.
Concerning HW, we are focusing on Opensocial and FB for the moment. It’s just important to have a clear vision of the roots of portability.