180 lines
3.3 KiB
Plaintext
180 lines
3.3 KiB
Plaintext
head 1.5;
|
|
access;
|
|
symbols;
|
|
locks; strict;
|
|
comment @# @;
|
|
|
|
|
|
1.5
|
|
date 2006.06.12.20.09.53; author LeeBelbin; state Exp;
|
|
branches;
|
|
next 1.4;
|
|
|
|
1.4
|
|
date 2006.06.12.16.46.02; author RichardPyle; state Exp;
|
|
branches;
|
|
next 1.3;
|
|
|
|
1.3
|
|
date 2006.06.12.16.45.18; author RichardPyle; state Exp;
|
|
branches;
|
|
next 1.2;
|
|
|
|
1.2
|
|
date 2006.06.12.16.41.35; author LeeBelbin; state Exp;
|
|
branches;
|
|
next 1.1;
|
|
|
|
1.1
|
|
date 2006.02.13.19.59.46; author RicardoPereira; state Exp;
|
|
branches;
|
|
next ;
|
|
|
|
|
|
desc
|
|
@
|
|
.
|
|
@
|
|
|
|
|
|
1.5
|
|
log
|
|
@
|
|
.
|
|
@
|
|
text
|
|
@---++ GUID Outreach
|
|
|
|
*Coordinator(s):*
|
|
|
|
Lee Belbin
|
|
|
|
*Participants:*
|
|
|
|
Richard Pyle, Ben Szekely, Rod Page
|
|
|
|
----
|
|
---+++ Description
|
|
To coordinate the development of documentation for outreach to the broader community to encourage uptake and support of GUIDs and LSIDs.
|
|
|
|
----
|
|
---+++ Discussion
|
|
|
|
The group discussed the need to address a range of 'target audiences' in the community with specific documents.
|
|
|
|
----
|
|
---+++ Conclusions and Recommendations
|
|
|
|
Documentation needs to be targeted to three classes of clients)-
|
|
|
|
* Managers, CEOs, CIOs
|
|
1. Lee to write one web page on justification for GUIDs and LSIDs
|
|
1. Answer what's in it for my institution or group
|
|
1. Look to DOIs (but maybe not mention)
|
|
1. Possibly provide an example link
|
|
|
|
* Biologists, Taxonomists, Bioinformaticists
|
|
1. Rich to write 1-2 pages largely around an example demonstrating key benefits
|
|
1. Rod to tidy example and assist Rich
|
|
|
|
* IT/Developer Community
|
|
1. Ben to gather developer resources (done) to Ricardo
|
|
1. Gap analysis on software resources required (Ricardo)
|
|
1. Gap analysis on additional and filler documentation required (Roger)
|
|
1. Ricardo will e-mail Ben about plugin requirements and Ben will address these issues and report back to Ricardo
|
|
1. Link to RDF benefits and software requirements groups
|
|
|
|
As a second priority, we will consider targeting a specific domain
|
|
* Is there a SIGNIFICANT community we could sell LSID benefits to?
|
|
1. Fish
|
|
1. Ants
|
|
|
|
|
|
|
|
----
|
|
---+++++ Categories
|
|
CategoryWorkingGroup
|
|
CategoryInfrastructureWG@
|
|
|
|
|
|
1.4
|
|
log
|
|
@
|
|
.
|
|
@
|
|
text
|
|
@d13 1
|
|
a13 1
|
|
To coordinate the development of documentation for outreach to the broader community supporting GUIDs and LSIDs.
|
|
d18 1
|
|
a18 1
|
|
The group discussed the need to address a range of 'target audiences' in the community with specific explanatory documents.
|
|
d23 1
|
|
a23 1
|
|
Three levels of documentation required for outreach (Ben, Rich, Rod and Lee)
|
|
d42 2
|
|
a43 2
|
|
* Cross cutting outreach to domain
|
|
1. Is there a SIGNIFICANT community we could sell LSID benefits to?
|
|
@
|
|
|
|
|
|
1.3
|
|
log
|
|
@
|
|
.
|
|
@
|
|
text
|
|
@d25 1
|
|
a25 1
|
|
1. Managers, CEOs, CIOs
|
|
d31 1
|
|
a31 1
|
|
1. Biologists, Taxonomists, Bioinformaticists
|
|
d35 1
|
|
a35 1
|
|
1. IT/Developer Community
|
|
d42 1
|
|
a42 1
|
|
1. Cross cutting outreach to domain
|
|
@
|
|
|
|
|
|
1.2
|
|
log
|
|
@Base draft from GUID-2
|
|
.
|
|
@
|
|
text
|
|
@d18 1
|
|
a18 1
|
|
The group discussed the need to address a range of 'types' in the community with specific documents.
|
|
d23 1
|
|
a23 1
|
|
Three level of documentation required for outreach (Ben, Rich, Rod and Lee)
|
|
d29 1
|
|
a29 1
|
|
1. Possibly provide and example link
|
|
@
|
|
|
|
|
|
1.1
|
|
log
|
|
@Initial revision
|
|
@
|
|
text
|
|
@d5 2
|
|
d9 2
|
|
d13 1
|
|
a13 1
|
|
This group will develop GUID related materials to communicate with wider community.
|
|
d18 1
|
|
a18 1
|
|
|
|
d23 1
|
|
d25 21
|
|
d52 1
|
|
a52 1
|
|
CategoryInfrastructureWG
|
|
@
|