wiki-archive/twiki/data/GUID/Requirements.txt,v

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


1.8
date	2006.03.02.14.07.08;	author RicardoPereira;	state Exp;
branches;
next	1.7;

1.7
date	2006.03.02.14.05.53;	author RicardoPereira;	state Exp;
branches;
next	1.6;

1.6
date	2006.01.28.07.08.46;	author KevinThiele;	state Exp;
branches;
next	1.5;

1.5
date	2005.12.22.20.48.44;	author RicardoPereira;	state Exp;
branches;
next	1.4;

1.4
date	2005.12.22.20.29.44;	author RicardoPereira;	state Exp;
branches;
next	1.3;

1.3
date	2005.12.22.20.29.17;	author RicardoPereira;	state Exp;
branches;
next	1.2;

1.2
date	2005.12.22.20.24.51;	author RicardoPereira;	state Exp;
branches;
next	1.1;

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


desc
@
.
@


1.8
log
@Page out-of-date
.
@
text
@*This page is out-of-date!!*
-- RicardoPereira - 02/Mar/2006
----

---++ GUID Requirements

The requirements for the GUID framework can be divided into two categories:
   1.  Generic infrastructure that supports assignment and resolution of identifiers for any domain.
   2.  Domain specific requirements for each domain, such as taxonomic names, concepts, specimens, collections.

In this page we present what the group believes are requirements for a GUID system supporting biodiversity informatics.

Domain specific requirements pages: 
   * [[GUIDRequirementsTaxonomy][Taxonomic names and concepts]]
   * [[GUIDRequirementsSpecimens][Collections and specimens]]
   * Other domains to be addressed (add yours here)


----
---+++ General Requirements

---+++++ R1. GUID must be persistent

The link between the identifier and the entity it identifies must be maintained indefinitely, regardless of changes in the entity location or ownership.

---+++++ R2. GUID must be actionable

The identifier must take the user to entity that it identifies, i.e., the user must be able retrieve data and metadata about an entity using its identifier.

---+++++ R3. GUID must be globally unique

A GUID resolves to a single entity (abstract or concrete) and is unique in the context of the system.

---+++++ R4. GUID identity digital objects

GUIDs identify digital representations of real world object, not the real objects themselves. For example, a GUID can represent a specimen catalog entry in a collection database, but not the physical entity.

---+++++ R5. GUID metadata infrastructure must be extensible

---+++++ R6. Intellectual Property Rights are defined in the metadata


----
---++++ Requirements Under Discussion

---+++++ Data (and metadata?) are persistent
@


1.7
log
@
.
@
text
@d1 4
a6 2
*This page is out of date!!*

@


1.6
log
@Correction of typos only
.
@
text
@d3 2
@


1.5
log
@
.
@
text
@d3 1
a3 1
The requiremenst for the GUID framework can be divided into two categories:
d20 1
a20 1
The link between the identifier and the entity it identifies must be maintained indefinately, regardless of changes in the entity location or ownership.
d36 1
a36 1
---+++++ R6. Intelectual Property Rights are defined in the metadata
@


1.4
log
@
.
@
text
@d12 2
@


1.3
log
@
.
@
text
@d10 2
a11 2
   * [[GUIDRequirements_NamesAndConcepts][Taxonomic names and concepts]]
   * [[GUIDRequirements_Specimens][Collections and specimens]]
@


1.2
log
@
.
@
text
@d7 5
a11 1
In this page we present what the group believes are requirements for a GUID system supporting biodiversity informatics. 
@


1.1
log
@Initial revision
@
text
@d20 1
a20 1
---+++++ R3. GUID is globally unique
@