53 lines
1.3 KiB
Plaintext
53 lines
1.3 KiB
Plaintext
|
|
||
|
|
|
||
|
|
""
|
||
|
|
<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 - 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.
|
||
|
|
|