Re: Comments on "Dspace History System: Descriptive Note" of 2003/May /14

   From: "Seaborne, Andy" <Andy_Seaborne@hplb.hpl.hp.com>
   Date: Thu, 15 May 2003 11:48:43 +0100
   X-MailScanner: Found to be clean
   X-Archived-At: http://www.w3.org/mid/5E13A1874524D411A876006008CD059F06C23825@0-mail-1.hpl.hp.com
   X-Mailing-List: <www-rdf-dspace@w3.org> archive/latest/244
   X-Loop: www-rdf-dspace@w3.org
   X-SBClass: Nonlocal Origin [192.6.10.2]
   X-Spam-Status: No, hits=2.7 required=5.0 tests=SUBJ_HAS_SPACES version=2.20
   X-Spam-Level: **
   X-SpamBouncer: 1.5 (2/23/03)
   X-SBPass: NoBounce
   X-SBClass: OK
   X-Folder: Bulk


   Identifiers: section 3.2
   ========================

   It would be valuable to decide on the SIMILE policy for naming things
   (including the allocation of URIs) outside of the History Store work as well
   so that a common policy applies throughout the system.


   Allocating URIs
   ---------------

   The history system has to work with URIs external to the history system and
   also to allocate URIs for information it creates.  It will have to cope with
   external resources in any (legal) form : handles, http URLs, URNs, bNodes
   with identifying properties.  Some of these may well not have been allocated
   by SIMILE at all and were previously allocated.  The History Store (and
   elsewhere in SIMILE) needs distinctly identify each concept as objects are
   created and changed.

   When the History Store does create "objects" it would be good if they were
   GETtable.  If there is a metadata record
   http://thisInstallation/collection/1711/101 for an object
   http://example.org/aBook then having "GET
   http://thisInstallation/collection/1711/101" working would be appropriate
   returning RDF if asked for application/rdf+xml.  This would need pulling the
   RDF out of the database for a plain GET if there is no data duplication and
   hence chance for inconsistency.

I would like to recommend that each URL minted by simile contain some
large random string (either truly random, or an MD5 hash of the bits
if possible) in addition to whatever else we put there.  I think this
will maximize the possibility that our URLs can be unambiguously
interpreted regardless of future evolutions in RDF, domain names, or
the simile project.

Received on Thursday, 22 January 2004 18:13:11 UTC