- From: Kevin Smathers <kevin.smathers@hp.com>
- Date: Thu, 22 May 2003 14:33:57 -0400 (EDT)
- To: "Tansley, Robert" <robert.tansley@hp.com>
- Cc: "(www-rdf-dspace@w3.org)" <www-rdf-dspace@w3.org>
Tansley, Robert wrote:
>This looks fine, until you actually try and change something. Say I add a new bitstream, BITS2, to BND1. I've shown this in that nasty orange colour. This obviously consistutes a change in BND1; you can't just draw another hasPart arc between BND1:1 and BITS2:1, since you would never be able to tell that BND1 in one situation contained only BITS1. So, you create a new situation for BND1, called BND1:2, and have hasPart arcs between that and BITS1:1 and BITS2:1. (This assumes that the situation of BITS1 is not changed by virtue of the fact that the Bundle it is in has changed.)
>
This is only a problem for content based identifiers (see my rambling
answer to Mark). When using resource identifiers the two instances of
BND1:1 are distinct, so there is no confusion between the two chains.
Collapsing all nodes that have the same contents by using content based
identifiers is an invalid optimization, as this use case shows (among
others.)
>
>
>
--
========================================================
Kevin Smathers kevin.smathers@hp.com
Hewlett-Packard kevin@ank.com
Palo Alto Research Lab
1501 Page Mill Rd. 650-857-4477 work
M/S 1135 650-852-8186 fax
Palo Alto, CA 94304 510-247-1031 home
========================================================
use "Standard::Disclaimer";
carp("This message was printed on 100% recycled bits.");
Received on Friday, 23 May 2003 03:16:42 UTC