OuiShare is a global community and think and do-tank with a mission to build and nurture a collaborative society by connecting people, organizations and ideas around fairness, openness and trust.

It has a yearly conference on the collaborative society OuiShare Fest in Paris.

The third conference will be on 20-22 May 2015.

OuiShare has local communities across the world and in most European countries. These are very  light weight structures that have influence but no ability to set rules on their partners. They therefore have to work with the tools that all the other groups work with. Auli Kutt of OuiShare labs, has worked on listing all the tools used by OuiShare in the following Trello.


It consists of 13 categories, for a total of 55 tools and growing. Most[a][b][c][d][e] of these tools save their data on a siloed server. Each User Interface is designed for the data on one specific domain. This leads to a large set of usability problems related to:

OuiShare has several types of members who need to access tools of different types with different intensity.

Large players such as Google apps are trying to solve this by creating centralised ecosystems of tools where the storage would be placed on their servers. But this won’t help for more sensitive data or large volumes of business data, or even interrelations between many different organisations.

Instead, the co-operating systems platform, would enable the data to remain distributed, with

the ability to link sets of data across organisations. A new partner coming across new resources would not need to move all their previous content, but may just need to choose a new interface to interact with it.  User Interfaces would be designed then to follow linked data so that they can then read/write data across each partners servers.

OuiShare would be an early adopter for the deployment of the platform, giving [f][g]its members access to a distributed social network. Hopefully this would spur other OuiShare members to adopt the standards, and so to grow the community worldwide into the biggest social network ever: the social web spanning the world.

Use Cases / LD solutions

Distributed social web:

every person at OuiShare gets a personal profile page that can also return an RDF description of them giving them a WebID. The profile page data  can link to the people they know (foaf:know) in different organisations. (see video demo) Some of this information can be protected for confidentiality reasons. This allows any software agent able to read the linked data to create a user interface appropriate for the device (phone, laptop, wrist watch,...) and user ( blind person, different languages, etc…)

Each member can publish (with access controls) the time zone of their current locaion so that other members wishing to call them, can be made of the time of day at which the person are calling finds themselves. (never call someone in japan at 3 in the morning again)

Finally social network browsers can allow people to discover new contacts and gain some initial trust through their position in the social web. Eg. someone is travelling to OuiShare Fest, and meets someone at the conference. After scanning their card, they find they know a few people in common)


   When a meeting is organised people participating in the meeting can be identified using their WebID. This WebID allows software agents to fetch information from their profile - whatever organisation this belongs to - and display a small info box containing picture, name, blog, telephone number, email, skype address etc… (whatever is relevant) to someone who wishes to know more about who is attending. This allows one to organise cross institutional meetings as if they were intra-organisational ones.

  Each actor’s calendaring information could be made available without divulging the details of what is taking place to specific groups of actors in order to facilitate automatic meeting organisation. (Instead of Doodling suitable times and several reminders, it can be deducted half automatically from participants’ calendars or from the available time slots they have indicated.)

   Note that each meeting has its own global group identifier  (as a URL)  which lists the members attending the meeting (see next story)

Document Sharing

During the teleconf (done over webrtc for p2p conferencing over the web?) a number of participants realise that they have some documents that could be relevant to the project. Using the group Id mentioned above, the users ( all in different organisations ) can drag and drop the members of the meeting onto the access control list of their documents (regardless of the document platform) and give them access ( read and/or write). As a result the other members of the conference can click on a link and open the document to collaborate, using annotations, comments, and various forms of discussions.

 A collaborative working space can also be put up to allow all the members of the conference to share their findings for future archiving.


As a result of the call a document can be produced that is made available publicly or to a roughly described group of users such as friends of friends (foaf), or friends of friends of OuiShare members, or ... Subscribers to OuiShare blog posts can be alerted to the new content, which can appear in their news feeds - or in contemporary parlance their “wall”. Trusted groups of users - which can be defined as flexibly as anyone trusted by a trusted users - can comment on the post, thereby removing the dilemmas that came with the blogosphere of either allowing everyone to comment and risk being spammed, or to slow down feedback through clumsy human filtering.


lf the group  discover an Idea missing in their Project. [ example needed ], they may create

a data wiki page describing it, or find one on the web. They can use this concept to categorise some previous posts they published. As they discuss its relevance, various partners may find that they have projects that tie into this idea. This may lead to the group tying into other projects or to create a new one. Various Actors may find resources such as spare buildings, events, skills, mathematical equations, or even other ideas related to this, and these could crystallize into a specific project, with deadlines, subprojects, etc... The Projects, Actors, Ideas and Resources need none of them belong to the organisation that initiated the ideas, or contributed to a project. This allows diverse organisations to put together projects fluidly and thereby resolve problems that any single organisation would have found un imaginable.

[a]Ouiki (mediawiki) is self-hosted, and we aim at using open source self-hosted alternatives in some more areas, but practically the preference is usability (UX) over ideology (OS)


[c]but even self hosted open source is siloed, if it doesn't share data format :)

[d]yes, but in the case of a wiki, which are  just collection of web pages, the web1.0 simple <a href="">...</a> hypertext are enough to link to other wikis or pages. The problem really appears as soon as one has data - even simple metadata creates the inters problem.

[e]good point


2015-03-11 0:09 GMT+01:00 Henry Story (Google Docs) <

[f]it and its?