W3C home > Mailing lists > Public > public-ldp-wg@w3.org > October 2012

Re: Use-Cases and call for help to add descriptions and scenarios ISSUE-16

From: Raúl García Castro <rgarcia@fi.upm.es>
Date: Thu, 04 Oct 2012 08:26:00 +0200
Message-ID: <506D2BF8.2070301@fi.upm.es>
To: Steve Battle <sysemia.steve.battle@talktalk.net>
CC: "public-ldp-wg@w3.org" <public-ldp-wg@w3.org>
El 03/10/12 23:18, Steve Battle escribió:
>
> On 3 Oct 2012, at 09:29, Raúl García Castro <rgarcia@fi.upm.es
> <mailto:rgarcia@fi.upm.es>> wrote:
>
>> Raúl
>
> I've simplified the original scenario as you suggest, using the same URI
> throughout:
> 1.3.2.2.1 Primary Scenario: Request RDF representation of an information
> resource
> <http://www.w3.org/2012/ldp/wiki/Use_Cases_And_Requirements#Primary_Scenario:_Request_RDF_representation_of_an_information_resource>
>
> I added a new scenario that explicitly distinguishes between the
> information and non-information resource.
> 1.3.2.2.2 Alternative Scenario: Request RDF description of a
> non-information resource
> <http://www.w3.org/2012/ldp/wiki/Use_Cases_And_Requirements#Alternative_Scenario:_Request_RDF_description_of_a_non-information_resource>
>
> I've also raised issue-16 covering these points.
>
> Thanks again for the feedback.

Perfect. Now both scenarios are clear.

Thanks,

>> Hi Steve,
>>
>> I have a comment on the example in the Primary Scenario of UC-BPR-1.
>>
>> While I understand that the URI of the GET can be different of the URI
>> in the returned representation of the BPR, I think that the example
>> needs some clarification explaining that internally the server relates
>> alice.rdf with alice.
>>
>> For example, the scenario would be the same if the client makes
>> GET http://example.com/people/one.rdf HTTP/1.1
>>
>> And in this case it should be stated that, for the server, one.rdf
>> corresponds to alice and two.rdf corresponds to bob.
>>
>> Or, another option, is to use the same URI in the GET and in the
>> representation, as in UC-BPC1, and have the case of different URIs as
>> an alternative scenario.
>>
>
> Steve Battle
>
> --
> Steve Battle
> Semantic Engineer
>
> E-mail: steve.battle@sysemia.co.uk <mailto:steve.battle@sysemia.co.uk>
> Web: www.sysemia.com <http://www.sysemia.com>
>
> Sysemia Limited
> The Innovation Centre, Bristol&  Bath Science Park, Dirac Crescent,
> Emerson's Green, Bristol BS16 7FR
> Registered in England and Wales. Company Number: 7555456
>
> DISCLAIMER
>
> Information contained in this e-mail is intended for the use of the
> addressee only, and is confidential and may also be privileged. If you
> receive this message in error, please advise us immediately. If you are
> not the intended recipient(s), please note that any form of
> distribution, copying or use of this communication or the information in
> it is strictly prohibited and may be unlawful. Attachments to
> this e-mail may contain software viruses which may damage your
> systems. Sysemia Ltd have taken reasonable steps to minimise this risk,
> but we advise that any attachments are virus checked before they are opened.
>
>
>
>
>


-- 

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 Thursday, 4 October 2012 06:58:09 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:17:32 UTC