Thanks. I've looked at quite a bit of this stuff, but still don't see where the ACL document gets stored and used.
I am beginning to get the sense that I may have to write some code, other than the ACL rdf to do this. Surely Apache or something else will do this for me? Can't I "just" put the ACL in a file (as in htpasswd) and point something at it? I certainly don't want to be writing code to make one photo (or simply a static web site) available. Or is that the "delegated service" you are talking about? I've got my fingers crossed here. On 9 Aug 2013, at 17:35, Kingsley Idehen <[email protected]> wrote: > On 8/9/13 12:22 PM, Hugh Glaser wrote: >> <Hugh comes back to play /> >> Thanks Kingsley, and Melvin and Henry and Norman. >> So, trying to cut it down to the minimum. >> (Sorry, I find some/many of the pages about it really hard going.) >> If I have a photo on a server, http://example.org/photos/me.jpg, and a WebID >> at http://example.org/id/you >> What files do I need on the server so that http://example.org/id/you#me (and >> no-one else) can access http://example.org/photos/me.jpg? >> I think that is a sensible question (hopefully!) > > You can need a Turtle document (other RDF document types will do too) > comprised of content that describes your ACL based on > <http://www.w3.org/ns/auth/acl> vocabulary terms. > > You might find <http://www.w3.org/wiki/WebAccessControl#this> wiki document > useful too. > > My ACL demos leverage the fact that our ODS and Virtuoso platforms have this > in-built re. Web Server functionality. > > I need to check if we built a delegated service for WebID+TLS based ACLs, if > not, then (note to self re., new feature zilla) we'll make one :-) > >
