| 8 | | * DBCLS |
| 9 | | * HAPMAP/Korean |
| 10 | | * KEGG |
| 11 | | * PDBj |
| 12 | | * UniProt |
| 13 | | * TreeBASE ([http://treebase.org v.1],[http://treebase-dev.nescent.org:6666/treebase-web v.2]) |
| | 8 | * DBCLS [http://dbcls.rois.ac.jp/] |
| | 9 | * DDBJ [http://www.ddbj.nig.ac.jp/] |
| | 10 | * Korean HapMap [http://www.khapmap.org/] |
| | 11 | * KEGG [http://www.genome.jp/] |
| | 12 | * PDBj [http://www.pdbj.org/] |
| | 13 | * UniProt [http://www.uniprot.org/] |
| | 14 | * TreeBASE [http://treebase.org v.1],[http://treebase-dev.nescent.org:6666/treebase-web v.2] |
| | 41 | |
| | 42 | {{{ |
| | 43 | Rule #1 When a data provider has given a derefencable URI to a topic, this is the only accepted URI that should be published on the [http://dig.csail.mit.edu/breadcrumbs/node/215 GGG]. Other data provider must make reference to it in their own dataset. |
| | 44 | }}} |
| | 45 | |
| | 46 | Actually the following data provider have created their own derefencable URI : |
| | 47 | |
| | 48 | * UniProt |
| | 49 | * Gene Ontology |
| | 50 | |
| | 51 | those providers will apply Rule #1 when they start to publish RDF. |
| | 52 | |
| | 53 | * DBCLS |
| | 54 | * KEGG |
| | 55 | * PDBJ |
| | 56 | |
| | 57 | Now that data provider will share a common naming for URI, it is necessary to adopt a simple design rule for URIs. |
| | 58 | |
| | 59 | {{{ |
| | 60 | Rule #2 The syntax of a derefencable URI is as follow : |
| | 61 | http://providerDomaineName/publicNamesapce/privateId |
| | 62 | }}} |
| | 63 | |
| | 64 | For example the folowing URI are valid : |
| | 65 | * http://purl.uniprot.org/uniprot/P17710 |
| | 66 | * http://pdbj.org/pdbid/2yhx |
| | 67 | * http://dbcls.jp/insc/AAB57760 |
| | 68 | * http://genome.jp/ec/2.7.1.1 |
| | 69 | |
| | 70 | but not these : |
| | 71 | |
| | 72 | * http://www.genome.jp/dbget-bin/www_bget?ec:2.7.1.1 |
| | 73 | |