71 lines
1.5 KiB
Plaintext
71 lines
1.5 KiB
Plaintext
head 1.3;
|
|
access;
|
|
symbols;
|
|
locks; strict;
|
|
comment @# @;
|
|
|
|
|
|
1.3
|
|
date 2006.02.11.13.17.50; author RicardoPereira; state Exp;
|
|
branches;
|
|
next 1.2;
|
|
|
|
1.2
|
|
date 2006.02.10.20.45.18; author RicardoPereira; state Exp;
|
|
branches;
|
|
next 1.1;
|
|
|
|
1.1
|
|
date 2006.02.10.20.44.22; author RicardoPereira; state Exp;
|
|
branches;
|
|
next ;
|
|
|
|
|
|
desc
|
|
@
|
|
.
|
|
@
|
|
|
|
|
|
1.3
|
|
log
|
|
@
|
|
.
|
|
@
|
|
text
|
|
@@
|
|
|
|
|
|
1.2
|
|
log
|
|
@
|
|
.
|
|
@
|
|
text
|
|
@a0 14
|
|
---++++ The "GUIDs for Data Objects vs. Conceptual Entities" Working Group
|
|
|
|
GUIDs may be assigned to both "digital objects" (specific byte sequences), or to conceptual ("abstract") entities, and this group concluded that both play a role in biodiversity informatics.
|
|
|
|
__Digital Byte Sequences__
|
|
* Permanent, unchanging sequences of digital bits (e.g., digital images, ASCII-rendered DNA sequences, locked PDF files, specific versions of a particular database record [e.g. XML or RDF serialization of a database record], etc.)
|
|
|
|
__Conceptual ("Abstract") Entities__
|
|
* Conceptualized "notions" of an object or event
|
|
* No data content (null)
|
|
* Serve as "hubs" to cluster and relate other GUID-tagged objects
|
|
* Rarely exists without at least one Digital Byte Sequence GUID directly or indirectly linked
|
|
|
|
This group agreed to take on the task of developing a series of Wiki Pages to clarify the distinction between these two fundamental kinds of GUIDs, and to illustrate how both would be used within the biodiversity informatics community.
|
|
@
|
|
|
|
|
|
1.1
|
|
log
|
|
@Initial revision
|
|
@
|
|
text
|
|
@d1 14
|
|
a14 1
|
|
Rich, add your content here. Thanks.@
|