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


1.8
date	2006.06.12.18.33.25;	author StanBlum;	state Exp;
branches;
next	1.7;

1.7
date	2006.06.12.18.26.15;	author StanBlum;	state Exp;
branches;
next	1.6;

1.6
date	2006.06.12.17.04.13;	author StanBlum;	state Exp;
branches;
next	1.5;

1.5
date	2006.06.12.17.00.10;	author StanBlum;	state Exp;
branches;
next	1.4;

1.4
date	2006.06.12.16.33.49;	author StanBlum;	state Exp;
branches;
next	1.3;

1.3
date	2006.06.12.16.33.16;	author StanBlum;	state Exp;
branches;
next	1.2;

1.2
date	2006.06.12.16.28.40;	author StanBlum;	state Exp;
branches;
next	1.1;

1.1
date	2006.06.12.16.27.39;	author StanBlum;	state Exp;
branches;
next	;


desc
@
.
@


1.8
log
@
.
@
text
@   

""
<table border="1" cellpadding="1">
  <tbody>
   <tr>
     <td style="font-weight: bold;">Move what? </td>
     <td style="font-weight: bold;"> Solution </td>
     <td style="font-weight: bold;"> Implications/Issues </td>
     <td style="font-weight: bold;"> Examples </td>
   </tr>
   <tr>
     <td>Entire Collection </td>
     <td> Move authority </td>
     <td> Institution Name in DNS part </td>
     <td> Cat-of-Fishes.ORG - OK <br>
Cat-of-Fishes.NHM.OR.UK &nbsp;- Not OK </td>
   </tr>
   <tr>
     <td> Known Subset </td>
     <td> Identify subset, include domain + move DNS </td>
     <td> Same </td>
     <td> </td>
   </tr>
   <tr>
     <td> Unknown subset </td>
     <td> authority redirects </td>
     <td> central authority </td>
     <td> Issuer is always responsible authority </td>
   </tr>
   <tr>
     <td>Individual Item </td>
     <td> " </td>
     <td> " </td>
     <td> " </td>
   </tr>
  </tbody>
</table>

""

Solutions - Technical

1) Centralized GUID/LSID authority/resolver 
2) Central DNS SRV service -- subdomain assignment within a centralized domain (e.g., fish-names.lsid.tdwg.org; bishop-fish.lsid.tdwg.org)
3) Nothing


#1 is difficult (scalability & reliability) although it has a lot of benefits.

#2 has benefits if we can pre-identify collections of objects that might move.

@


1.7
log
@
.
@
text
@d45 1
a45 1
2) Central DNS SRV service  -- subdomain assignment within a centralized domain (e.g., fish-names.lsid.tdwg.org)
d51 1
a51 1
#2 has benefits in thing that might move
@


1.6
log
@
.
@
text
@d1 2
d42 1
d44 2
a45 2
1) Centralized resolver of identifiers and their locations
2) Distributed subdomain assignment within a centralized domain (e.g., fish-names.tdwg.org)
d51 2
a52 1
#2 has benefits for thing that might move
@


1.5
log
@
.
@
text
@d2 1
a2 1
<table cellpadding="1">
d5 4
a8 4
     <td>"Move what? </td>
     <td> Solution </td>
     <td> Implications/Issues </td>
     <td> Examples </td>
d37 1
@


1.4
log
@
.
@
text
@d1 37
a37 6
|  | Move what?        | Solution  | Implications/Issues | Examples |
|1 | Entire Collection | Move authority   Inst.| Name in DNS part | Cat of Fishes.ORG OK; Cat Of Fishes.NHM.OR.UK  Not OK |
|2| Known Subset       | Identify subset, include domain + move DNS | Same | |
|3| Unknown subset     | authority redirects; central authority | Issuer is always responsible authority   
|4| Individual Item    | | " | " |

@


1.3
log
@
.
@
text
@d2 1
a2 1
|1 | Entire Collection | Move authority   Inst.| Name in DNS part | Cat of Fishes.ORG OK; CatOfFishes.NHM.OR.UK  Not OK |
@


1.2
log
@
.
@
text
@d1 5
a5 7
|  | Move what? | Solution    | Implications/Issues | Examples
|1 |Entire Collection | Move authority   Inst. Name in DNS part   | Cat of Fishes.ORG OK
CatOfFishes.NHM.OR.UK  Not OK |
|2| Known Subset | Identify subset; include domain + move DNS | Same   |
|3| Unknown subset| -  authority redirects 
- central authority | Issuer is always responsible authority   
|4| Individual Item| " | " |
@


1.1
log
@Initial revision
@
text
@d9 10
@