mike amundsen wrote:
yep. i can deref the primary resource URI
i see the Link Header for ACLs
i can deref the ACL URI, too.
Great!
I've not tested editing the ACL URI yet.
Okay.
Kingsley
mca
http://amundsen.com/blog/
http://mamund.com/foaf.rdf#me
On Mon, Jun 21, 2010 at 12:52, Ki
yep. i can deref the primary resource URI
i see the Link Header for ACLs
i can deref the ACL URI, too.
I've not tested editing the ACL URI yet.
mca
http://amundsen.com/blog/
http://mamund.com/foaf.rdf#me
On Mon, Jun 21, 2010 at 12:52, Kingsley Idehen wrote:
> mike amundsen wrote:
>>
>> well,
mike amundsen wrote:
well, I now have access to the primary URI (the mappings document),
but my attempts to deref the ACL URI supplied in the link header are
failing. I am prompted for my cert, supply it, and then see the HTTP
auth dialog.
Please try again.
A fix has been applied to the tes
well, I now have access to the primary URI (the mappings document),
but my attempts to deref the ACL URI supplied in the link header are
failing. I am prompted for my cert, supply it, and then see the HTTP
auth dialog.
BTW - according to the details outlined in the paper[1] (pg. 6 table
1) once I
Nathan wrote:
mike amundsen wrote:
(the resource URL is discoverable via Link: response headers):
try:
https://ods-qa.openlinksw.com/home/dav/Public/fao_to_sumo_mappings.txt,acl
Hopefully, the irony is not lost here.
Kingsley's message listed a URI of a resource; the LInk header of
wh
I started this thread to as a way to get us thinking about this
fundamental shortcoming of the WAC pattern as described in the initial
paper [1] and the Wiki [2].
The pattern where agents can deref the resource in order to discover
the ACL of that resource is viable for cases where the agent alrea
mike amundsen wrote:
(the resource URL is discoverable via Link: response headers):
try:
https://ods-qa.openlinksw.com/home/dav/Public/fao_to_sumo_mappings.txt,acl
Hopefully, the irony is not lost here.
Kingsley's message listed a URI of a resource; the LInk header of
which point
mike amundsen wrote:
Kingsley:
thanks for continuing to post examples/tests like this for us to work through.
When I attempt to deref the URI:
https://ods-qa.openlinksw.com/home/dav/Public/fao_to_sumo_mappings.txt
I am asked for my cert (supplied) and I am presetned with the HTTP
Auth challeng
mike amundsen wrote:
(the resource URL is discoverable via Link: response headers):
try:
https://ods-qa.openlinksw.com/home/dav/Public/fao_to_sumo_mappings.txt,acl
Hopefully, the irony is not lost here.
Kingsley's message listed a URI of a resource; the LInk header of
which pointed to th
(the resource URL is discoverable via Link: response headers):
> try:
> https://ods-qa.openlinksw.com/home/dav/Public/fao_to_sumo_mappings.txt,acl
Hopefully, the irony is not lost here.
Kingsley's message listed a URI of a resource; the LInk header of
which pointed to the URI of the ACL reso
try:
https://ods-qa.openlinksw.com/home/dav/Public/fao_to_sumo_mappings.txt,acl
note the ,acl
Nathan :)
mike amundsen wrote:
Kingsley:
thanks for continuing to post examples/tests like this for us to work through.
When I attempt to deref the URI:
https://ods-qa.openlinksw.com/home/dav/Publi
Kingsley:
thanks for continuing to post examples/tests like this for us to work through.
When I attempt to deref the URI:
https://ods-qa.openlinksw.com/home/dav/Public/fao_to_sumo_mappings.txt
I am asked for my cert (supplied) and I am presetned with the HTTP
Auth challenge.
IOW, I'm not able t
12 matches
Mail list logo
