- From: Seaborne, Andy <Andy_Seaborne@hplb.hpl.hp.com>
- Date: Wed, 28 May 2003 15:19:48 +0100
- To: "'Jason Kinner'" <jason_kinner@dynamicdigitalmedia.com>, "'www-rdf-dspace'" <www-rdf-dspace@w3.org>
This is more clarification then comment around sections 2.1 (Identification Schemes) and 3.2 (Classes). What URIs will the history store allocate its data objects (classes Community, Collection, Item, maybe Bundle)? If they are URL's then client systems can retrieve the object, which happens to be self-representing in RDF and reside in the history store database, after they have been found by a search. This means that what constitutes the "data object" is defined by the SIMILE system (i.e. owning system), and not by the query used to fetch it. I can see other SIMILE systems extracting whole records as well as an end-user preparing a research paper wanting to pull over a collection object for later local browsing. Andy -----Original Message----- From: Jason Kinner [mailto:jason_kinner@dynamicdigitalmedia.com] Sent: 23 May 2003 20:09 To: www-rdf-dspace Subject: History System Design Document (Initial Draft) All - Please review the History System Design Document [1] for initial direction. It is not complete and does not represent all of the classes and properties that will be implemented in the updated history system, but it should provide enough information to demonstrate the direction of the document and how the document fits into the statement of work for the history system. Comments can be mailed back to this list. Thank you, Jason Kinner Dynamic Digital Media, LLC 856.296.5711 (mobile) 215.243.7377 (phone) http://www.dynamicdigitalmedia.com [1] http://web.mit.edu/simile/www/resources/history-harmony/history-design.pdf
Received on Wednesday, 28 May 2003 12:01:59 UTC