initial structural analysis of DSpace RDF History data

Traversal of the DSpace RDF History Data that MacKenzie has provided 
reveals the following data types and elements.  (For traversal method, or 
to reproduce, see Appendix below).

Does this form a reasonable starting point for a formalized, published 
schema for the DSpace data model?

Some early questions that arise from this starting point:

... is containership modelled appropriately?
    (it appears that this is happening throughout using .../harmony/hasPart 
rather than explicitly in individual schemas (e.g. .../collection/hasItem)

... which of these attributes generate privacy concerns within libraries?
     given these attributes, is it possible to define a filter that would
     enable public sharing/posting of resulting instance data?

... naming consistency.  DSpace items have both http: names where they 
currently resolve (which MIT Libraries do _not_ commit to persist), and 
hdl: names (which MIT Libraries _do_ commit to persist).  Should 
rdf:resource='' use the http: name or the hdl: name?

Comments are welcome!

- Mick

-------------

http://www.dspace.org/community/community_id
http://www.dspace.org/community/copyright_text
http://www.dspace.org/community/introductory_text
http://www.dspace.org/community/logo_bitstream_id
http://www.dspace.org/community/name
http://www.dspace.org/community/short_description
http://www.dspace.org/community/side_bar_text

http://www.dspace.org/collection/approvers
http://www.dspace.org/collection/collection_id
http://www.dspace.org/collection/copyright_text
http://www.dspace.org/collection/introductory_text
http://www.dspace.org/collection/license
http://www.dspace.org/collection/logo_bitstream_id
http://www.dspace.org/collection/name
http://www.dspace.org/collection/provenance_description
http://www.dspace.org/collection/reviewers
http://www.dspace.org/collection/short_description
http://www.dspace.org/collection/side_bar_text

http://www.dspace.org/item/in_archive
http://www.dspace.org/item/item_id
http://www.dspace.org/item/submitter_id

http://www.dspace.org/dublincore/contributor
http://www.dspace.org/dublincore/contributor.author
http://www.dspace.org/dublincore/date.accessioned
http://www.dspace.org/dublincore/date.issued
http://www.dspace.org/dublincore/description
http://www.dspace.org/dublincore/description.abstract
http://www.dspace.org/dublincore/description.provenance
http://www.dspace.org/dublincore/description.sponsorship
http://www.dspace.org/dublincore/format.extent
http://www.dspace.org/dublincore/format.mimetype
http://www.dspace.org/dublincore/identifier.uri
http://www.dspace.org/dublincore/language.iso
http://www.dspace.org/dublincore/relation.ispartofseries
http://www.dspace.org/dublincore/subject
http://www.dspace.org/dublincore/title

http://www.dspace.org/bitstream/bitstream_id
http://www.dspace.org/bitstream/bitstream_type_id
http://www.dspace.org/bitstream/checksum
http://www.dspace.org/bitstream/checksum_algorithm
http://www.dspace.org/bitstream/description
http://www.dspace.org/bitstream/name
http://www.dspace.org/bitstream/size
http://www.dspace.org/bitstream/source
http://www.dspace.org/bitstream/user_type_description

http://www.dspace.org/eperson/active
http://www.dspace.org/eperson/email
http://www.dspace.org/eperson/eperson_id
http://www.dspace.org/eperson/firstname
http://www.dspace.org/eperson/lastname
http://www.dspace.org/eperson/phone
http://www.dspace.org/eperson/require_certificate

http://www.dspace.org/personalworkspace/collection_id
http://www.dspace.org/personalworkspace/item_id
http://www.dspace.org/personalworkspace/multiple_files
http://www.dspace.org/personalworkspace/multiple_titles
http://www.dspace.org/personalworkspace/personal_workspace_id
http://www.dspace.org/personalworkspace/published_before
http://www.dspace.org/personalworkspace/stage_reached

http://www.dspace.org/workflowitem/collection_id
http://www.dspace.org/workflowitem/item_id
http://www.dspace.org/workflowitem/multiple_files
http://www.dspace.org/workflowitem/multiple_titles
http://www.dspace.org/workflowitem/owner
http://www.dspace.org/workflowitem/published_before
http://www.dspace.org/workflowitem/state
http://www.dspace.org/workflowitem/workflow_id
http://www.dspace.org/generator

http://www.dspace.org/harmony/atTime
http://www.dspace.org/harmony/creates rdf:resource=''
http://www.dspace.org/harmony/destroys rdf:resource=''
http://www.dspace.org/harmony/hasAction rdf:resource=''
http://www.dspace.org/harmony/hasAgent
http://www.dspace.org/harmony/hasAgent rdf:resource=''
http://www.dspace.org/harmony/hasInput rdf:resource=''
http://www.dspace.org/harmony/hasOutput rdf:resource=''
http://www.dspace.org/harmony/hasPart
http://www.dspace.org/harmony/inState rdf:resource=''
http://www.dspace.org/harmony/transforms rdf:resource=''
http://www.dspace.org/harmony/usesTool



-------------

Appendix

$ cd foo2-history
$ find . -type f | grep -v \# | xargs perl -n -e 'if 
(/xmlns:NS(.).*www.dspace.org(.*)\//) {$ns[$1]=$2;} if (/<NS(.):([^>]*)>/) 
{$line=$2; $line =~ s/\047.*\047\//\047\047/; print $ns[$1],"/$line\n";}' | 
sort | uniq

=============================================
Mick Bass, Sloan MOT 2000

R&D Project Manager, Hewlett-Packard Company
Building 10-500 MIT, 77 Massachusetts Avenue
Cambridge, MA 02139-4307

617.253.6617 office    617.452.3000 fax
617.899.3938 mobile    617.627.9694 residence
bass@alum.mit.edu      mick_bass@hp.com
=============================================

Received on Friday, 30 August 2002 08:46:40 UTC