head	1.4;
access;
symbols;
locks; strict;
comment	@# @;


1.4
date	2006.04.19.17.34.53;	author DonaldHobern;	state Exp;
branches;
next	1.3;

1.3
date	2006.04.19.17.33.57;	author DonaldHobern;	state Exp;
branches;
next	1.2;

1.2
date	2006.04.12.11.57.00;	author DonaldHobern;	state Exp;
branches;
next	1.1;

1.1
date	2006.02.13.19.54.48;	author RicardoPereira;	state Exp;
branches;
next	;


desc
@
.
@


1.4
log
@
.
@
text
@---++ Orphan Data and Datasets

*Coordinator(s):* DonaldHobern

*Participants:*

----
---+++ Description
This group will investigate the need for a repository to host orphan data or datasets containing GUIDs. 

----
---+++ Discussion
In many ways this issue is part of a much larger question of long-term data curation (see also LSIDLongTermArchival).  We should however consider the issue now because it may have implications for the best practices that we choose to adopt for LSID issuers.  The use of an LSID rather than some other identifier should lead issuers to consider the long-term existence of the associated data object and of the LSID as a path to retrieve it.

Clearly no issuer can make an absolute guarantee that they will be able to serve their data far into the future.  The issue here is therefore whether our community should establish any infrastructure which could be used to archive data sets to ensure that their LSIDs can be resolved even if the original issuer ceases to exist.  If this is considered worthwhile, we need also to determine the implications for how issuers should manage their data (to ensure that such an archive, and ultimate transfer of ownership is feasible, see also especially LSIDResolverNamespaces).

----
---+++ Conclusions and Recommendations





----
---+++++ Categories
CategoryWorkingGroup
CategoryInfrastructureWG
@


1.3
log
@
.
@
text
@d13 1
a13 1
In many ways this issue is part of a much larger question of long-term data curation (see also GUIDLongTermArchival).  We should however consider the issue now because it may have implications for the best practices that we choose to adopt for LSID issuers.  The use of an LSID rather than some other identifier should lead issuers to consider the long-term existence of the associated data object and of the LSID as a path to retrieve it.
@


1.2
log
@
.
@
text
@d13 1
a13 1
In many ways this issue is part of a much larger question of long-term data curation.  We should however consider the issue now because it may have implications for the best practices that we choose to adopt for LSID issuers.  The use of an LSID rather than some other identifier should lead issuers to consider the long-term existence of the associated data object and of the LSID as a path to retrieve it.
@


1.1
log
@Initial revision
@
text
@d3 1
a3 1
*Coordinator(s):*
d13 1
d15 1
a15 1

@