- From: Jim Ley <jim@jibbering.com>
- Date: Sun, 9 Dec 2001 20:40:23 -0000
- To: <w3c-wai-er-ig@w3.org>
"Sean B. Palmer": > > > 03:15:33 <sbp> * Remove testSubject > > > 03:15:40 <sbp> * Add reprOf > > A resource is a thread; it has a number of entities > corresponsing to it over time. Certainly, although I don't see how we, when we're external to the resource, can know enough to state that some resource is newer version of the old. (it could be the same, with different content negotiation, or just failure to identify it at the same resource, or it could be a resource which changes regularly but rotates so old resources are still valuable.) My point is that we're introducing anything new, just that we're introducing the idea that testSubject/reprOf is threaded (ie an evaluation on a resource with a later date supercedes an evaluation on an earlier dated resource), and what about things we evaluate which are not time dependant, they just have different states. > So this simply clarifies what is meant by the important identification > properties in EARL, so that people can be much clearer about what they > identify. I don't (yet) see it as any clearer, some examples will probably help... Jim.
Received on Sunday, 9 December 2001 17:22:13 UTC