502 lines
13 KiB
Plaintext
502 lines
13 KiB
Plaintext
head 1.22;
|
|
access;
|
|
symbols;
|
|
locks; strict;
|
|
comment @# @;
|
|
|
|
|
|
1.22
|
|
date 2006.02.13.19.35.08; author RicardoPereira; state Exp;
|
|
branches;
|
|
next 1.21;
|
|
|
|
1.21
|
|
date 2006.01.27.12.43.46; author RogerHyam; state Exp;
|
|
branches;
|
|
next 1.20;
|
|
|
|
1.20
|
|
date 2006.01.20.15.29.48; author RicardoPereira; state Exp;
|
|
branches;
|
|
next 1.19;
|
|
|
|
1.19
|
|
date 2006.01.20.15.29.30; author RicardoPereira; state Exp;
|
|
branches;
|
|
next 1.18;
|
|
|
|
1.18
|
|
date 2006.01.19.13.43.40; author RicardoPereira; state Exp;
|
|
branches;
|
|
next 1.17;
|
|
|
|
1.17
|
|
date 2006.01.19.13.43.13; author RicardoPereira; state Exp;
|
|
branches;
|
|
next 1.16;
|
|
|
|
1.16
|
|
date 2006.01.18.13.43.23; author RicardoPereira; state Exp;
|
|
branches;
|
|
next 1.15;
|
|
|
|
1.15
|
|
date 2006.01.18.13.40.06; author RicardoPereira; state Exp;
|
|
branches;
|
|
next 1.14;
|
|
|
|
1.14
|
|
date 2006.01.18.13.37.22; author RicardoPereira; state Exp;
|
|
branches;
|
|
next 1.13;
|
|
|
|
1.13
|
|
date 2006.01.17.14.49.30; author RicardoPereira; state Exp;
|
|
branches;
|
|
next 1.12;
|
|
|
|
1.12
|
|
date 2006.01.17.14.47.36; author RicardoPereira; state Exp;
|
|
branches;
|
|
next 1.11;
|
|
|
|
1.11
|
|
date 2006.01.17.14.45.10; author RicardoPereira; state Exp;
|
|
branches;
|
|
next 1.10;
|
|
|
|
1.10
|
|
date 2006.01.17.14.39.27; author RicardoPereira; state Exp;
|
|
branches;
|
|
next 1.9;
|
|
|
|
1.9
|
|
date 2006.01.17.14.37.54; author RicardoPereira; state Exp;
|
|
branches;
|
|
next 1.8;
|
|
|
|
1.8
|
|
date 2006.01.17.14.30.36; author RicardoPereira; state Exp;
|
|
branches;
|
|
next 1.7;
|
|
|
|
1.7
|
|
date 2006.01.17.14.29.40; author RicardoPereira; state Exp;
|
|
branches;
|
|
next 1.6;
|
|
|
|
1.6
|
|
date 2006.01.17.14.28.34; author RicardoPereira; state Exp;
|
|
branches;
|
|
next 1.5;
|
|
|
|
1.5
|
|
date 2006.01.17.14.27.35; author RicardoPereira; state Exp;
|
|
branches;
|
|
next 1.4;
|
|
|
|
1.4
|
|
date 2006.01.17.14.22.22; author RicardoPereira; state Exp;
|
|
branches;
|
|
next 1.3;
|
|
|
|
1.3
|
|
date 2006.01.17.14.21.02; author RicardoPereira; state Exp;
|
|
branches;
|
|
next 1.2;
|
|
|
|
1.2
|
|
date 2006.01.17.13.45.11; author RicardoPereira; state Exp;
|
|
branches;
|
|
next 1.1;
|
|
|
|
1.1
|
|
date 2006.01.17.13.44.11; author RicardoPereira; state Exp;
|
|
branches;
|
|
next ;
|
|
|
|
|
|
desc
|
|
@
|
|
.
|
|
@
|
|
|
|
|
|
1.22
|
|
log
|
|
@Added page to CategoryGUID1 and notice that page is obsolete
|
|
.
|
|
@
|
|
text
|
|
@---++ GUID-1 Homework
|
|
|
|
----
|
|
*This page is obsolete - GUID-1 workshop is over!*
|
|
----
|
|
|
|
To make most out of our first workshop, *we require each participant to read some documents and prepare some material* __before we meet__ in Durham. The *homework* consists of the following tasks:
|
|
|
|
---+++ 1. Review (and update) the GUID Use-Cases
|
|
Please review the updated inventory of [[GUIDUseCases][GUID Use-Cases]]. Add any use-cases you believe we should discuss during the meeting.
|
|
|
|
|
|
---+++ 2. Review GUID technologies
|
|
Review the basics aspects of each GUID technology under evaluation. Since each participant is likely to be more familiar with one GUID technology, we would like to ask you to *review the basic aspects of other technologies as well*. To facilitate the process, we have prepared a short list of articles (mostly single sections extracted from articles) to get you up to speed (see below). You may also find useful to read the TechnologyComparison page.
|
|
|
|
---++++ 2.1 LSIDs
|
|
The main source of documentation on LSID is the [[http://www.omg.org/docs/dtc/04-05-01.pdf][LSID Specification]]. Please read the following sections:
|
|
1. Sections 8 and 8.1 - LSID Syntax and Specification
|
|
1. Section 9 - LSID Resolution Service
|
|
1. Section 13.3 - Discovering an LSID Resolution Service using DDDS/DNS
|
|
You can find LSID related documentation at the [[http://lsid.sourceforge.net/][LSID Homepage]]
|
|
|
|
---++++ 2.2 Handle System
|
|
The Handle System is documented as a set of [[http://www.ietf.org][IETF]] [[http://en.wikipedia.org/wiki/Request_for_Comments][RFCs]]. The *minimal* reading about the Handle System is a set of sections extracted from [[http://www.handle.net/rfc/rfc3651.html][Handle System Namespace and Service Definition - RFC 3651]] below:
|
|
1. Section 1: Introduction
|
|
1. Section 2: Handle System Namespace
|
|
1. Section 3: Handle System Data Model - Read section 3.1 - Handle Value Set only. Skip section 3.2.
|
|
1. Section 4: Handle System Service Model - Read section 4.1 (you might want to skip the details here). Skip 4.2.
|
|
1. Section 5: Handle System Operational Model - Read first paragraph only.
|
|
|
|
That sounds like a lot, but *it is only about 10 pages* (with some nice ASCII art).
|
|
If you need more context, here is the [[http://www.handle.net/documentation.html][Homepage for the Handle System documentation]]
|
|
|
|
---++++ 2.3 DOI
|
|
The main source of DOI information is the [[http://www.doi.org/hb.html][DOI Handbook]] or [[http://hdl.handle.net/10.1000/182][doi:10.1000/182]].
|
|
Here is the required reading:
|
|
1. [[http://www.doi.org/handbook_2000/intro.html#1.4][Section 1.4 - What is a Digital Object Identifier?]]
|
|
1. [[http://www.doi.org/handbook_2000/intro.html#1.5][Section 1.5 Components of the DOI System]]
|
|
1. [[http://www.doi.org/handbook_2000/enumeration.html#2.2][Section 2.2 - The structure of a DOI]]
|
|
1. [[http://www.doi.org/handbook_2000/resolution.html#3.2][Section 3.2 - Simple resolution]]
|
|
1. [[http://www.doi.org/handbook_2000/resolution.html#3.3][Section 3.3 - Multiple resolution]]
|
|
1. [[http://www.doi.org/handbook_2000/resolution.html#3.5.1][Section 3.5.1 - Relationship between the DOI System and the Handle System]]
|
|
Again, it sounds like a lot, but if you read only what is required, *it is only a few paragraphs*.
|
|
Note that the list of sections above is note a comprehensive description of the DOI System. It just gives the reader an overview about DOI and its differences from the Handle System.
|
|
For the time challenged I have put these sections into a [[http://biodiv.hyam.net/homework_sections_of_doi_handbook.pdf][single PDF]] (RogerHyam).
|
|
|
|
---++++ 2.4 General Questions
|
|
If you plan on arguing in favor of one or another GUID technology, be prepared to answer the following questions:
|
|
1. How extensible is the technology?
|
|
1. How does it handle metadata? How extensible the metadata framework is, i.e, how easy it is to implement a new framework on top of the basic infrastructure?
|
|
1. What are its strangths?
|
|
1. What are its weakenesses and how can we work around them (i.e., what if DNS or Handle System Global Registry cease to exist? What are our options?)
|
|
1. Anything else you might find relevant.
|
|
|
|
---+++ 3. Additional Reading (Optional)
|
|
|
|
The following documents are relevant for the planned workshop activities, so please read them if you have time (or you run out of things to read):
|
|
|
|
---++++ 3.1 Semantic Web, Ontologies, RDF, and OWL
|
|
* [[http://www.co-ode.org/resources/tutorials/intro/slides/OntologyEngineering.ppt][Ontology Engineering]] by Dr. Jeremy Rogers from the University of Manchester
|
|
* [[http://protege.stanford.edu/amia2003/AMIA2003Tutorial.ppt][Developing Medical Informatics Ontologies with Protégé]] by Natasha Noy and Samson Tu, from Stanford University
|
|
* [[http://www.nature.com/nbt/journal/v23/n9/full/nbt1139.html][From XML to RDF: how semantic web technologies will change the design of 'omic' standards]]
|
|
* [[http://darwin.zoology.gla.ac.uk/~rpage/lsid/examples/lsid.pdf][Roderic Page's manuscript]] on LSID, metadata and the Semantic Web
|
|
* [[http://protege.stanford.edu/publications/ontology_development/ontology101-noy-mcguinness.html][Ontology Development 101: A Guide to Creating Your First Ontology]]
|
|
|
|
----
|
|
---+++++ Categories
|
|
CategoryGUID1
|
|
|
|
@
|
|
|
|
|
|
1.21
|
|
log
|
|
@
|
|
.
|
|
@
|
|
text
|
|
@d3 4
|
|
d64 6
|
|
a69 1
|
|
* [[http://protege.stanford.edu/publications/ontology_development/ontology101-noy-mcguinness.html][Ontology Development 101: A Guide to Creating Your First Ontology]]@
|
|
|
|
|
|
1.20
|
|
log
|
|
@
|
|
.
|
|
@
|
|
text
|
|
@d41 1
|
|
d60 1
|
|
a60 1
|
|
* [[http://protege.stanford.edu/publications/ontology_development/ontology101-noy-mcguinness.html][Ontology Development 101: A Guide to Creating Your First Ontology]]
|
|
@
|
|
|
|
|
|
1.19
|
|
log
|
|
@
|
|
.
|
|
@
|
|
text
|
|
@d56 1
|
|
a56 1
|
|
* [[http://protege.stanford.edu/amia2003/AMIA2003Tutorial.ppt Developing Medical Informatics Ontologies with Protégé] by Natasha Noy and Samson Tu, from Stanford University
|
|
@
|
|
|
|
|
|
1.18
|
|
log
|
|
@
|
|
.
|
|
@
|
|
text
|
|
@d56 1
|
|
@
|
|
|
|
|
|
1.17
|
|
log
|
|
@
|
|
.
|
|
@
|
|
text
|
|
@a41 1
|
|
|
|
d43 1
|
|
a43 2
|
|
|
|
If you plan on arguing in favor of one or another GUID technology, be prepared to answer to those questions:
|
|
@
|
|
|
|
|
|
1.16
|
|
log
|
|
@
|
|
.
|
|
@
|
|
text
|
|
@d43 9
|
|
@
|
|
|
|
|
|
1.15
|
|
log
|
|
@
|
|
.
|
|
@
|
|
text
|
|
@d45 1
|
|
a45 1
|
|
The following are relevant documents to the planned workshop activities, so please read them if you have time (or you ran out of things to read):
|
|
@
|
|
|
|
|
|
1.14
|
|
log
|
|
@
|
|
.
|
|
@
|
|
text
|
|
@d48 4
|
|
a51 3
|
|
[[http://www.co-ode.org/resources/tutorials/intro/slides/OntologyEngineering.ppt][Ontology Engineering]] by Dr. Jeremy Rogers from the University of Manchester
|
|
[[http://www.nature.com/nbt/journal/v23/n9/full/nbt1139.html][From XML to RDF: how semantic web technologies will change the design of 'omic' standards]]
|
|
[[http://darwin.zoology.gla.ac.uk/~rpage/lsid/examples/lsid.pdf][Roderic Page's manuscript]] on LSID, metadata and the Semantic Web
|
|
@
|
|
|
|
|
|
1.13
|
|
log
|
|
@
|
|
.
|
|
@
|
|
text
|
|
@d41 10
|
|
@
|
|
|
|
|
|
1.12
|
|
log
|
|
@
|
|
.
|
|
@
|
|
text
|
|
@a3 2
|
|
1. Review the updated inventory of [[GUIDUseCases][GUID Use-Cases]]. Please add any use-cases you believe we should discuss during the meeting.
|
|
1. Review the basics aspects of each GUID technology under evaluation. Since each participant is likely to be more familiar with one GUID technology, we would like to ask you to review the basic aspects of other technologies as well. To facilitate the process, we have prepared a short list of articles (mostly single sections extracted from articles) to get you up to speed (see below). You may also find useful to read the TechnologyComparison page.
|
|
d5 8
|
|
a12 1
|
|
---++++ LSIDs
|
|
d19 1
|
|
a19 1
|
|
---++++ Handle System
|
|
d30 1
|
|
a30 1
|
|
---++++ DOI
|
|
@
|
|
|
|
|
|
1.11
|
|
log
|
|
@
|
|
.
|
|
@
|
|
text
|
|
@d15 1
|
|
a15 1
|
|
The Handle System is documented as a set of [[http://www.ietf.org][IETF]] [[http://en.wikipedia.org/wiki/Request_for_Comments][RFCs]]. The _minimal_ reading about the Handle System is a set of sections extracted from [[http://www.handle.net/rfc/rfc3651.html][Handle System Namespace and Service Definition - RFC 3651]] below:
|
|
d26 1
|
|
a26 1
|
|
The main source of DOI information is the [[http://www.doi.org/hb.html][DOI Handbook]] or *doi:10.1000/182*
|
|
@
|
|
|
|
|
|
1.10
|
|
log
|
|
@
|
|
.
|
|
@
|
|
text
|
|
@d4 2
|
|
a5 2
|
|
1. Review the updated inventory of [[GUIDUseCases][GUID Use Cases]]. Add any use-cases you believe we should discuss during the meeting.
|
|
1. Review the basics aspects of each GUID technology under evaluation. Since each participant is likely to be more familiar with one GUID technology, we would like to ask you to review the basic aspects of other technologies as well. To facilitate the process, we have prepared a short list of articles (mostly single sections extracted from articles) to get you up to speed (see below).
|
|
a6 1
|
|
---+++ Reading on GUID Technologies
|
|
@
|
|
|
|
|
|
1.9
|
|
log
|
|
@
|
|
.
|
|
@
|
|
text
|
|
@d3 1
|
|
a3 1
|
|
To make most out of our first workshop, we require each participant to read some documents and prepare some material *before* we meet in Durham. The *homework* consists of the following tasks:
|
|
@
|
|
|
|
|
|
1.8
|
|
log
|
|
@
|
|
.
|
|
@
|
|
text
|
|
@d9 5
|
|
@
|
|
|
|
|
|
1.7
|
|
log
|
|
@
|
|
.
|
|
@
|
|
text
|
|
@d27 3
|
|
a29 3
|
|
1. [[http://www.doi.org/handbook_2000/resolution.html#3.2 Section 3.2 - Simple resolution]
|
|
1. [[http://www.doi.org/handbook_2000/resolution.html#3.3 Section 3.3 - Multiple resolution]
|
|
1. [[http://www.doi.org/handbook_2000/resolution.html#3.5.1 Section 3.5.1 - Relationship between the DOI System and the Handle System]
|
|
@
|
|
|
|
|
|
1.6
|
|
log
|
|
@
|
|
.
|
|
@
|
|
text
|
|
@d3 1
|
|
a3 1
|
|
To make most out of our first workshop, we require each participant to read some documents and prepare some material _before_ we meet in Durham. The _homework_ consists of the following tasks:
|
|
d30 1
|
|
@
|
|
|
|
|
|
1.5
|
|
log
|
|
@
|
|
.
|
|
@
|
|
text
|
|
@a3 1
|
|
|
|
a7 1
|
|
|
|
a9 1
|
|
|
|
a10 1
|
|
|
|
a18 1
|
|
|
|
a20 1
|
|
|
|
a21 1
|
|
|
|
a22 1
|
|
|
|
a23 1
|
|
|
|
a29 1
|
|
|
|
@
|
|
|
|
|
|
1.4
|
|
log
|
|
@
|
|
.
|
|
@
|
|
text
|
|
@d15 1
|
|
a15 3
|
|
The Handle System is documented as a set of [[http://www.ietf.org][IETF]] [[http://en.wikipedia.org/wiki/Request_for_Comments][RFCs]]. Here is the _minimal_ reading about the Handle System (From [[http://www.handle.net/rfc/rfc3651.html][Handle System Namespace and Service Definition - RFC 3651]]):
|
|
:
|
|
|
|
d36 3
|
|
d40 1
|
|
a40 1
|
|
Note that the list of sections above is note a comprehensive description of DOI. It assumes the reader has a working knowledge about the need for use of unique persistent identifiers and about the Handle System (i.e. have read the sections above).
|
|
@
|
|
|
|
|
|
1.3
|
|
log
|
|
@
|
|
.
|
|
@
|
|
text
|
|
@d15 2
|
|
a16 1
|
|
The Handle System is documented as a set of [[http://www.ietf.org][IETF]] [[http://en.wikipedia.org/wiki/Request_for_Comments][RFCs]]. Here is the _minimal_ reading about the Handle System:
|
|
d18 5
|
|
a22 6
|
|
1. From [[http://www.handle.net/rfc/rfc3651.html][Handle System Namespace and Service Definition - RFC 3651]]:
|
|
1. Section 1: Introduction
|
|
1. Section 2: Handle System Namespace
|
|
1. Section 3: Handle System Data Model - Read section 3.1 - Handle Value Set only. Skip section 3.2.
|
|
1. Section 4: Handle System Service Model - Read section 4.1 (you might want to skip the details here). Skip 4.2.
|
|
1. Section 5: Handle System Operational Model - Read first paragraph only.
|
|
d24 1
|
|
a24 1
|
|
That sounds like a lot, but it is only about 10 pages (with some nice ASCII art).
|
|
@
|
|
|
|
|
|
1.2
|
|
log
|
|
@
|
|
.
|
|
@
|
|
text
|
|
@d15 1
|
|
d17 23
|
|
a39 1
|
|
---++++ DOI@
|
|
|
|
|
|
1.1
|
|
log
|
|
@Initial revision
|
|
@
|
|
text
|
|
@d6 1
|
|
a6 1
|
|
1. Review the basics aspects of each GUID technology under evaluation. Since each participant is likely to be more familiar with one GUID technology, we would like to ask you to review the basic aspects of other technologies as well. To facilitate the process, we have prepared a short list of articles (mostly single sections extracted from articles) to get you up to speed. It is at the bottom of this page.
|
|
@
|