This group seeks to bootstrap the nascent Read-Write aspect of the WWW via collaboration on specs and tools that ultimately make reading and writing on the WWW a natural usage pattern.
Key technology for making this effort a reality lies in the use of the WebID protocol as a mechanism for Web scale Access Control Lists (ACL) applied to Web Addresses (URLs).
Of immediate interest, based work that’s been incubating (somewhat) for years in the Data Wiki. Basically, the application of Content Wiki functionality to more fine grained resources that serve to represent actual data objects via linked data graphs.
Related
- Read-Write Linked Data
- Socially Aware Cloud Storage
- Levels of Abstraction: Net, Web, Graph
- WebID.info
- WebIDs and the WebID Protocol
- Web Access Control
- Linked Data .
More related links: WebID.info, WebIDs and the WebID Protocol.
Thanks! Add the URLs to the main bullet list.
WebID is a great solution for authenticating human web browsers when they are visiting URLs in the WWW space. Are their any similar proposals for authenticating human users when they visit SPARQL results sets in a quad store? I.e. how should we control access to statements?
Sherman,
SPARQL Query results are delivered via URLs (Addresses) , so you can apply WebID ACLs to these just as you would any other resource URL .
Same even applies to SPARQL endpoints.
Kingsley
I would like to have ACLs for triples. WebAccessControl only covers resources. I’ve create a quick ‘n’ dirty extension to WAC to handle triples. That’s how it looks like: https://www.axolotlfarm.org/svn/bergi/bergnet/php/resourceme-app/trunk/src/data/triplestore.init.rdf.xml. Is somebody else working on this topic?
Certainly interested in this as level of granularity is also important albeit a little trickier.
Anyway, I’ll take a look at your extension ASAP.
Kingsley