[foaf-protocols] Sketch of a RESTful photo Printing service with foaf+ssl

Melvin Carvalho melvincarvalho at gmail.com
Sat Oct 10 15:28:51 CEST 2009


On Sat, Oct 10, 2009 at 8:28 AM, Henry Story <Henry.Story at sun.com> wrote:
>
> On 10 Oct 2009, at 07:11, Melvin Carvalho wrote:
>
>> On Wed, Oct 7, 2009 at 9:20 PM, Henry Story <Henry.Story at sun.com> wrote:
>>>
>>> Hello All,
>>>
>>> I have written up in detail a sketch of what a photo printing service
>>> using foaf+ssl could look like. As it required a lot of image
>>> attachments, and hyperlinks I preferred to write about it in HTML and
>>> post it on my blog:
>>>
>>>       http://blogs.sun.com/bblfish/entry/sketch_of_a_restful_photo
>>
>> This looks very promising.
>>
>> What is the URI of the new frame in:
>>
>> "3. When you click a button that says "Give Print.com access to the
>> pictures you wish us to print", a new frame is opened on your web
>> site"
>
> That should be Joe's Contact adder endpoint. So presumably something like
>
> https://joe.eg/addContact

Are we adding a contact, or access controlling resources?

Perhaps adding a contact is as simple as sending a line of sparql
update to the webid.

Access control is more a case of selecting a set of resources and
GRANTING READ permission on it (for one hour)?

>
> The URL of print.com would be passed as an argument to the POST or perhaps
> even just as an attribute value. So perhaps it should be
>
> https://joe.eg/addContact?id=https://nasdaq.com/co/PRNT&hash;co
>
> Should I make joe's url explicit, in the text? Might make it more readable.

Yes, why not

>
> Does that make sense?

Yes

>
>>
>>>
>>> Looking forward to your comments.
>>>
>>>       Henry
>>>
>>> Social Web Architect
>>> Sun Microsystems
>>> Blog: http://blogs.sun.com/bblfish
>>>
>>> _______________________________________________
>>> foaf-protocols mailing list
>>> foaf-protocols at lists.foaf-project.org
>>> http://lists.foaf-project.org/mailman/listinfo/foaf-protocols
>>>
>
>


More information about the foaf-protocols mailing list