- From: Daniel Garijo <dgarijo@delicias.dia.fi.upm.es>
- Date: Wed, 1 Jun 2011 17:18:06 +0200
- To: Luc Moreau <L.Moreau@ecs.soton.ac.uk>
- Cc: Graham Klyne <GK@ninebynine.org>, public-prov-wg@w3.org
- Message-ID: <BANLkTi==w+28N6ZvykE+NtDmVDwxa1+rKQ@mail.gmail.com>
Hi Luc, why can't c2s2 and c2s3 be two different resource states and also have a URI? I think that a resource state representation should have a way (URI) to identify it, in order to be able to assert provenance about it. It could be seen as a subclass of resource. In the example, if c2s2 and c2s3 share the same URI, I wouldn't be able to assert when were they created. Or I would have 2 different creation dates and no way of knowing which would belong to the resource state representations. However, I have to recognize that creating a URI for each resource state may be overwhelming for any provenance publisher. If we pretend that people use our model/guidelines, we should adopt solutions like the one proposed by Graham (duri), imo. Best, Daniel 2011/5/31 Luc Moreau <L.Moreau@ecs.soton.ac.uk> > Graham, > > In my example, I really mean for the two versions of the chart to be > available at > the same URI. (So, definitely, an uncool URI!) > > In that case, there is a *single* resource, but it is stateful. Hence, > there > are two *resource states*, one generated using (stats2), and the other > using (stats3). > > Of course, if blogger had used cool uris, then, c2s2 and c2s3 would be > different resources. > > Luc > > > On 05/31/2011 02:25 PM, Graham Klyne wrote: > >> I see (at least) two resources associated with (c2): one generated using >> (stats2), and other using (stats3). We might call these (c2s2) and (c2s3). >> > > -- > Professor Luc Moreau > Electronics and Computer Science tel: +44 23 8059 4487 > University of Southampton fax: +44 23 8059 2865 > Southampton SO17 1BJ email: l.moreau@ecs.soton.ac.uk > United Kingdom http://www.ecs.soton.ac.uk/~lavm > > >
Received on Wednesday, 1 June 2011 15:18:35 UTC