In order to enable a space of co-operation between distributed organisation in an agile manner read only Linked Data is not enough. One also needs: to write data to remote systems in a RESTful manner to allow an actor to bind himself to a remote action global identification - so that an actor can know who said what and what action he commited himself to distributed access control ... Henry Story will show how the LDP Protocol (in last call) enables one to build this, how it ties into WebID and Web Access Control, and how it differentiates itself and complements technologies such as SPARQL.

1. The Read-Write
Secure
Linked Data
Web
Henry Story
http://bblfish.net/

2. Les données liés

3. La logique des données liés

4. Vint Cert & Tim Berners Lee

5. Un Graphe RDF

6. case class PointedGraph(point: Node, graph: Graph)

7. timbl/foaf.knows
/foaf:knows

8. case class NamedGraph(name: IRI, graph: Graph)

9. case class PointedNamedGraph(point: Node, ng: NamedGraph)

10. timbl~>foaf:knows

11. Sur le résau:

13. HTTP PATCH

14. Que faire si TimBL veut que ces amis, ou les amis de
ces amis puissent lui envoyer des notifications?

15. ldp:Container

16. Mais comment faire pour éviter les spammeurs?
une identité globale et distribué: WebID
l’authentification
le controle d’access

17. La logique des données liés

18. deux types de copies de graph

20. http://webid.info/

21. Web Access Control

22. Pour en savoir plus:
• WebID, WebACL, http://webid.info/
• LDP: http://www.w3.org/2012/ldp/wiki/Main_Page
• https://github.com/read-write-web/wiki/wiki