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

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


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

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

1.6
date	2006.06.12.21.21.24;	author RicardoPereira;	state Exp;
branches;
next	1.5;

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

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

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

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

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


desc
@
.
@


1.8
log
@
.
@
text
@---++ LSID Software Development

This break-out group identified outstanding issues that need to be addressed regarding LSID software in the short-term.

This work was based on the gap analysis presented on the 2nd day of the [[GUID2Workshop]] and on the discussion that followed.

Note: This is one of the break-out group formed during the 3rd day of the [[GUID2Workshop]].

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

---+++++ 1) Refinement of existing software components

The group must address the outstanding gaps and issues identified in LSID software components during the meeting.
   1.  LSID Java Toolkit: include libraries (jars) that the toolkit depend on, to ease toolkit setup
   1.  lsidBrowser for Firefox: improve installation documentation (issue raised by Bob and others)
   1.  LaunchPad for Internet Explorer is based on obsolete technology and is not supported anymore.

Resources should not be spent migrating (porting) resolver authority software to other platforms. Ports should be made by interested parties. 

---+++++ 2) Reduce barriers to LSID resolution in external tools and clients

The group at [[GUID2Workshop]] identified that the use of LSID may impose a barrier to external communities to resolve LSIDs and consume Biodiversity Informatics metadata. That is because LSID, a URN scheme, requires special software for resolution.

The group identified two tasks that, if successful, can lower this barrier: 

   1.  To contact companies and organizations developing semantic web tools and encourage them to include LSID resolution in their tools
   1.  Identify key semantic web tools (open source) and examine the possibility of development of plugins and providers to enable LSID resolution

One of the outcomes is to evaluate the feasibility of this a task. 

---+++++ 3) Group needs to experiment more with development of client software

Not enough prototype clients have been developed so far to evaluate needs and gaps of client LSID software stack.


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


1.7
log
@
.
@
text
@d17 1
a17 1
   1.  other issues identified by participants
d32 1
a32 1
---+++++ 3) Revisit LSID support for provider software
d34 1
a34 3
It is a priority to deploy LSID resolvers with provider software. However, the group must gather requirements from provider software developers to identify which components would be most useful to support these developers.

---+++++ 4) Group needs to experiment more with development of client software
a35 1
Not enough prototype clients have been developed so far to evaluate needs and gaps of client LSID software stack.
@


1.6
log
@
.
@
text
@a8 1

a20 1

a31 1

d34 1
d38 1
a38 5

----

Note: All other GUID working groups should be consulted to help rank the above tasks regarding priorities.

@


1.5
log
@
.
@
text
@d18 4
a33 1
---+++++ 3) 
d35 1
d38 1
d41 3
a44 1
UNDER DEVELOPMENT
@


1.4
log
@
.
@
text
@d13 1
a13 1
---++++ 1) Refinement of existing software components
d19 1
a19 1
---++++ 2) Reduce barriers to LSID resolution in external tools and clients
d30 1
a30 1
---++++ 3) 
@


1.3
log
@
.
@
text
@d5 1
a5 1
This work was based on the gap analysis presented on the 2nd day of the GUID2Workshop and on the discussion that followed.
d7 1
a7 1
Note: This is one of the break-out group formed during the 3rd day of the GUID2Workshop.
d15 17
a31 1
The group must examine the most important LSID software components and address the outstanding issues raised during the meeting.
a32 1
Following is a list of LSID components that need to be examined and the outstanding issues we identified:
a33 1
   1.  LSID Java Toolkit: 
@


1.2
log
@
.
@
text
@d15 1
a15 1
The group must look at the most important LSID software components and address the outstanding issues raised during the meeting.
d17 3
a19 1
The LSID components need...
@


1.1
log
@Initial revision
@
text
@d13 1
a13 1
---+++++ =1) Refinement of existing software components
@