- From: Luc Moreau <L.Moreau@ecs.soton.ac.uk>
- Date: Wed, 01 Jun 2011 07:49:10 +0100
- To: Graham Klyne <GK@ninebynine.org>
- CC: public-prov-wg@w3.org
Hi Graham, Isn't it that you used the duri scheme to name the two resource states that exist in this scenario? In your view of the web, is there a notion of stateful resource? Does it apply here? Thanks, Luc On 31/05/11 23:57, Graham Klyne wrote: > Luc Moreau wrote: >> 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). > > Luc, > > I had interpreted your scenario as using a common URI as you explain. > > But there are still several resources here, but they are not all > exposed on the web or assigned URIs. I'm appealing here to anything > that *might* be identified as opposed to things that actually are > assigned URIs. (For example, the proposed duri: scheme might be used > - http://tools.ietf.org/id/draft-masinter-dated-uri-07.html) > > (And the URI is perfectly "cool" if it is specifically intended to > denote a dynamic resource. A URI used to access the current weather > in London can be stable if properly managed.) > > (I think this is all entirely consistent with my earlier stated > positions.) > > #g > -- > >> 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). >>
Received on Wednesday, 1 June 2011 06:49:50 UTC