W3C home > Mailing lists > Public > www-rdf-dspace@w3.org > June 2003

Lifecycle Management of Digital Objects

From: Bass, Mick <mick.bass@hp.com>
Date: Fri, 20 Jun 2003 08:22:03 -0700
Message-ID: <40700B4C02ABD5119F000090278766440656B852@hplex1.hpl.hp.com>
To: www-rdf-dspace@w3.org

Mark wrote:

> I've also looked through the prototypes, and identified 
> components from the prototypes. Based on this I have produced 
> a "component map" of all the components, that starts to 
> relate the use cases to the prototypes - see the enclosed .gif image. 
> 
> I struggled with the following prototypes:
> 
> - Prototype dissemination kernel and architecture
> - RDF Diff
> - OAIS Lifecycle data schema development
> - Event based workflow survey and recommendations
> - Archival of SIMILE data
> - Web of trust for authority services
> 
> So can anyone suggest component(s) to summarise these use 
> cases to fit on the component map?

I suspect that you may have struggled with those because they stress a dimension of SIMILE that is not strongly represented in the heterogeneous metadata end-to-end use case.

Don't know if this will help or not, so I thought I would bring some current thinking and dialogue to the list.

John Ericson and I have been considering another "generic" end-to-end use case under which some of the existing use cases would be components or instances.

Current working name for this use case is "lifecycle management of digital objects".

Such a use case would entail (end-to-end):
        - policy expression (suitably constrained)
        - digital object modelling
        - interaction with a digital object via an API
        - definition, insertion, and management of views on objects
        - event modelling
        - modelling and connecting triggers - responses to events
        - audit metadata generation, and audit services

While there is some overlap with the heterogeneous metadata use case, they are largely orthogonal.  I note that both of these end-to-end cases are replete with interesting UI and usability issues.

This generic use case might subsume existing instance use cases of: OCLC authority control service, history (audit) subsystem.

We do need to be sure that we can concretely express a specific end-to-end instance of this generic case.  We might do this by expressing the use-case in terms of a particular object that is added to SIMILE, and the stuff that happens to it (specifically described) in each of the dimensions mentioned above, over time.

Feedback is welcome.

> > > > >
> > > 
> > =============================================
> > > > > Mick Bass
> > > > >
> > > > >
> > > > > Manager
> > > > > Research and Business Development
> > > > > HP Laboratories
> > > > > Hewlett-Packard Company
> > > > > 1 Cambridge Center
> > > > > Cambridge, MA 02142
> > > > >
> > > > >
> > > > > 617.551.7634 office    617.551.7650 fax
> > > > > 617.899.3938 mobile    617.627.9694 residence
> > > > > bass@alum.mit.edu      mick_bass@hp.com
> > > > > =============================================
> > > > >
> > > > >
> > > >
> > > >
> > >
> >
> >
>
Received on Friday, 20 June 2003 11:22:07 EDT

This archive was generated by hypermail pre-2.1.9 : Wednesday, 24 September 2003 13:35:24 EDT