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


1.13
date	2007.01.09.00.00.00;	author MoinMoin;	state Exp;
branches;
next	1.12;

1.12
date	2007.01.09.00.00.00;	author MoinMoin;	state Exp;
branches;
next	1.11;

1.11
date	2007.01.09.00.00.00;	author MoinMoin;	state Exp;
branches;
next	1.10;

1.10
date	2007.01.09.00.00.00;	author MoinMoin;	state Exp;
branches;
next	1.9;

1.9
date	2007.01.09.00.00.00;	author MoinMoin;	state Exp;
branches;
next	1.8;

1.8
date	2007.01.09.00.00.00;	author MoinMoin;	state Exp;
branches;
next	1.7;

1.7
date	2007.01.09.00.00.00;	author MoinMoin;	state Exp;
branches;
next	1.6;

1.6
date	2007.01.09.00.00.00;	author MoinMoin;	state Exp;
branches;
next	1.5;

1.5
date	2007.01.09.00.00.00;	author MoinMoin;	state Exp;
branches;
next	1.4;

1.4
date	2007.01.09.00.00.00;	author MoinMoin;	state Exp;
branches;
next	1.3;

1.3
date	2007.01.09.00.00.00;	author MoinMoin;	state Exp;
branches;
next	1.2;

1.2
date	2007.01.09.00.00.00;	author MoinMoin;	state Exp;
branches;
next	1.1;

1.1
date	2007.01.09.00.00.00;	author MoinMoin;	state Exp;
branches;
next	;


desc
@Initial revision
@


1.13
log
@Revision 13
@
text
@---+ Finding A New Name For The Unified Protocol

Current protocol name suggestions are:

   * *DiGIRcase*
   * *GBiF protocol*
   * *TDWG protocol*
   * *DiGIR 2*
   * *TAPIR* - TDWG Access Protocol for Information Retrieval
   * *XDiDAPro* - XML based Distributed Data Access Protocol
   * *YAP!* - Yet Another Object Access Protocol
   * *CORP* - Complex Object Retrieval Protocol

Feel free to comment or add more

-----
*comments:*

DiGIRcase is somewhat problematic if someone asks "What does the 'case' stand for?" Since it had it origin as "Collection Access Service for Europe." That wouldn't be very global, or generic. 

"DiGIR" is a very good name for a protocol - it is succinct and memorable. It is also generic and non-partisan. However, it does already have a large following, so the combined protocol must be understood to be new and different if the DiGIR name is maintained.

"The GBIF protocol" doesn't suffer from these disadvantages, though it is more partisan and less generic than "DiGIR."

 -- John Wieczorek

I think that both*GBIF protocol* and*TDWG protocol* are too general (as well as having the partisan aspect already mentioned).  My preference would be for*DiGIR 2* or*TAPIR* although it would be nice to reflect the contribution of BGBM/BioCASe somehow.  I just can't find a good name that does so.

 -- Donald Hobern
@


1.12
log
@Revision 12
@
text
@a9 2
   * *TIRP* - TDWG Information Retrieval Protocol
   * *DIRP* - Distributed Information Retrieval Protocol
d27 1
a27 1
I think that both*GBIF protocol* and*TDWG protocol* are too general (as well as having the partisan aspect already mentioned).  I do not like*TIRP* or*DIRP* because they both sound a little silly.  My preference would be for*DiGIR 2* or*TAPIR* although it would be nice to reflect the contribution of BGBM/BioCASe somehow.  I just can't find a good name that does so.
@


1.11
log
@Revision 11
@
text
@d13 2
@


1.10
log
@Revision 10
@
text
@d26 4
@


1.9
log
@Revision 9
@
text
@d16 1
d18 1
@


1.8
log
@Revision 8
@
text
@d5 8
a12 7
   * DiGIRcase

   * GBiF

   * new DiGIR

   * DiGIR 2
d16 1
d22 2
@


1.7
log
@Revision 7
@
text
@d3 1
a3 1
Current suggestions are:
d5 1
a5 1
   * DiGIRcase protocol
d7 1
a7 1
   * GBiF protocol
d9 1
a9 1
   * new DiGIR protocol
d11 1
a11 1
   * DiGIR 2 protocol
@


1.6
log
@Revision 6
@
text
@d5 9
a13 6
<br> *the DiGIRcase protocol*
<br> *the GBiF protocol*
<br> *the new DiGIR protocol*
<br> *the DiGIR 2 protocol*
<br>
<br> Feel free to comment or add more
@


1.5
log
@Revision 5
@
text
@d8 1
@


1.4
log
@Revision 4
@
text
@d7 1
d10 6
@


1.3
log
@Revision 3
@
text
@d7 1
@


1.2
log
@Revision 2
@
text
@a6 1
<br> 
@


1.1
log
@Initial revision
@
text
@d5 4
a8 4
the DiGIRcase protocol
the GBiF protocol

Feel free to comment or add more
@