- From: Raúl García Castro <rgarcia@fi.upm.es>
- Date: Tue, 15 Jan 2013 16:17:04 +0100
- To: "Wilde, Erik" <Erik.Wilde@emc.com>
- CC: Roger Menday <Roger.Menday@uk.fujitsu.com>, "public-ldp-wg@w3.org" <public-ldp-wg@w3.org>, "ashok.malhotra@oracle.com" <ashok.malhotra@oracle.com>
El 13/01/13 01:47, Wilde, Erik escribió: > hello roger. > > On Jan 12, 2013, at 19:23, "Roger Menday" > <Roger.Menday@uk.fujitsu.com> wrote: >>>> I don't see a need for service documents. >>> apart from the terminology "service document", i am wondering how >>> you are envisioning interactions with the server for collection >>> management, when you don't have a resource that allows you to >>> provide interaction affordances for things such as, for example, >>> the creation of collections? >> the server provides a well-known 'root' resource from which the >> interaction affordances, existing resources, etc. can be >> discovered. just like on the HTML web. > > ok, then it's just terminology. what you call a root resource, > atompub calls a service document. it seems we're on the same page and > just need to decide on a naming issue. Hi, I think that Roger is not referring to a service document. What I have understood as a root resource is something like the index.html page; the root page from which you can navigate through the content in a web server. In our case, we could have an index/root resource from which you can access other resources in a server. Or at least some suggestion on how to name it so clients know. Kind regards, -- Dr. Raúl García Castro http://delicias.dia.fi.upm.es/~rgarcia/ Ontology Engineering Group Departamento de Inteligencia Artificial Universidad Politécnica de Madrid Campus de Montegancedo, s/n - Boadilla del Monte - 28660 Madrid Phone: +34 91 336 36 70 - Fax: +34 91 352 48 19
Received on Tuesday, 15 January 2013 15:17:26 UTC