GCRI · Registry
Interoperabilitas registri
Registries are only as useful as the links between them. A record that cannot be referenced stably, exported faithfully or read by another system becomes an island, and islands drift apart. This page sets out how stable references, persistent identifiers, metadata crosswalks, export formats and interface semantics let registries exchange records without losing meaning, and how interoperability fails through link rot, lossy mapping and undocumented change.
Bagaimana pekerjaan berjalan.
Interoperability console
Registry interoperability · Crosswalk · Profile v3
Field mappings
| identifier | id | copy | Lintasan |
| evidence_label | quality.label | enum map | Lintasan |
| licence | rights.licence | SPDX id | Ambiguous |
| version | version | semver | Lintasan |
Kesesuaian
Gbr.Interoperability console: example names and illustrative values, not a record or a live system.
Registry interoperability: how the risk develops.
Stable references, exports and API semantics. The dossier below sets out how the risk develops, what is measured, where the data come from, how it is modelled and who decides.
Link rot and content drift
Location links break when sites are reorganised, and links that still resolve may point to changed content. Without persistent identifiers and archived snapshots, references silently stop meaning what their authors intended.
Lossy crosswalks
Mapping one schema to another drops fields with no equivalent and flattens distinctions, such as several contributor roles folded into one. Round trips lose information, and each exchange makes the copies less alike.
Undocumented interface change
An interface changes a field’s meaning, format or default without a version or notice. Consumers keep parsing successfully while reading the wrong thing, and the errors surface far from the change that caused them.
Identity collision across registries
The same organisation, person or work carries different identifiers in different registries, or a local identifier is reused for different things. Joins across sistem then merge what is distinct or split what is one.
How registry interoperability is modelled, measured and tested.
Model, asumsi, data, dan ketidakpastiannya, dalam bentuk yang akan diperiksa ilmuwan atau insinyur. Strukturnya mengikuti metode yang dipublikasikan. Nilai yang digambar bersifat ilustratif, bukan temuan.
Set data dan asal-usul
The data classes behind registry interoperability and what is recorded about each before it is used.
| Kelas data | Asal-usul tercatat | Resolusi dinyatakan | Lisensi diperiksa |
|---|---|---|---|
| Citra satelit, optik dan radar | sensor, tingkat pemrosesan, tanggal akuisisi | ukuran piksel dan kunjungan ulang | per adegan |
| Reanalisis dan keluaran model iklim | model, eksperimen, anggota, versi | grid dan langkah waktu | per rilis |
| Sensor dan alat ukur in situ | stasiun, instrumen, catatan kalibrasi | titik dan laju pengambilan sampel | per jaringan |
| Keterpaparan penduduk dan aset | metode, tahun terbit, sumber masukan | ukuran sel dan satuan | per rilis |
| Batas dan geografi acuan | produsen, edisi, tanggal | skala | per edisi |
- Garis keturunan
- Catatan W3C PROV dari sumber hingga gambar
- Prinsip
- FAIR: dapat ditemukan, dapat diakses, interoperabel, dapat digunakan ulang
- Kesenjangan
- ditampilkan sebagai hilang, tidak pernah diisi diam-diam
Interoperability lets records from each domain move between systems.
- AirDalam praktikHydrological metadata map to WMO and DCAT profiles.What a reader can checkCrosswalks
- Keanekaragaman hayatiDalam praktikBiodiversity records map to Darwin Core through GBIF.What a reader can checkMapping completeness
- PanganDalam praktikStatistical series map to SDMX where agencies use it.What a reader can checkExchange formats
Interoperability methods are designed for the seri Metode dan Teknis. Crosswalks to external standards are the subject of NS-14 in the proposed Nexus Standards, with no conformity claimed.
- Crosswalk proposals.
- Interoperability test results.
Apa yang diukur, dan seberapa baik.
Setiap indikator membawa satuan, frekuensi, jenis sumber di baliknya, dan label bukti yang akan dibawa suatu nilai. Tidak ada nilai yang ditampilkan: sebuah program menyediakannya berdasarkan wewenangnya sendiri.
| Indikator | Unit | Kadensi | Jenis sumber | Label |
|---|---|---|---|---|
| Identifier resolution success | share of resolution probes | setiap hari | Resolver probes | TERAMATI |
| Interface availability | share of time available | berkelanjutan | Availability monitoring | TERAMATI |
| Export schema conformance | share of exported records validating | per rilis | Schema validation | TERAMATI |
| Crosswalk coverage | share of fields mapped to the target schema | per rilis | Crosswalk register | DINYATAKAN |
| Round-trip fidelity | share of records returned intact | per rilis | Round-trip test | TERAMATI |
| Broken outbound references | share of references | setiap bulan | Link checking | TERAMATI |
| Deprecation notice period | hari | per interface change | Change log | DINYATAKAN |
| Records linked to external persistent identifiers | share of records | setiap bulan | Identifier reconciliation | TERAMATI |
Asal bukti.
Set data publik bernama dan catatan kelembagaan, masing-masing dengan kelas lisensinya. Sumber berdasarkan perjanjian hanya digunakan sesuai ketentuannya dan tidak pernah diterbitkan ulang.
| Sumber | Apa yang diberikannya | Kelas lisensi |
|---|---|---|
| DCAT version 3 | A vocabulary for catalogues, datasets, data services and versions in exchange | W3C document licence, free to implement |
| Schema.org | A shared vocabulary for embedding structured metadata in web pages | CC BY-SA for the vocabulary |
| OAI-PMH | A protocol for harvesting metadata from repositories | Open specification |
| Scholix link exchange | A framework and services for exchanging links between literature and data | CC0 for link metadata |
| re3data registry of research data repositories | Descriptions of repositories with their standards, identifiers and access policies | CC0 for metadata |
| FAIRsharing | A curated registry of standards, databases and policies and their relationships | CC BY-SA for content |
| OpenAIRE Graph | An open graph linking publications, data, software, projects and organisations across sources | CC BY |
| Spesifikasi OpenAPI | A standard description format for HTTP interfaces | Open specification, Apache licence |
Siapa yang memutuskan, dan apa yang dilayani bukti.
Registry prepares evidence. The decisions below are taken by the authorities named, under their own rules, and never by the platform.
| Siapa yang memutuskan | Pertanyaannya | Bukti yang dilayani halaman ini |
|---|---|---|
| Registry and repository managers | Which schemas, identifiers and interfaces to support, and on what deprecation timetable | Crosswalk coverage, round-trip losses and the consumers depending on each interface |
| Research infrastructure funders | Whether to fund integration with an existing registry or a new parallel system | Interoperability measures, standard conformance and existing link coverage |
| Pengelola data | Whether imported records can be merged with local ones | Identifier matches, crosswalk losses and conflicts between sources |
| National statistics offices and public data portals | Whether registry exports can feed published catalogues | DCAT conformance, licence metadata and the stability of identifiers |
Keluaran yang dihasilkan topik ini
- Stable references for every record, resolving to a current view and its versions
- Exports in documented formats with schema files and published crosswalks
- An interface change log with version numbers and deprecation notices
- Round-trip tests against external registry schemas with every loss listed
What experts ask about interoperability.
- How should identifiers from different registries be linked without copying records?
- Which open formats preserve meaning, provenance and rights when records are exported?
- How are field meanings documented so that two sistem agree on what a value means?
- How do interfaces signal that a record has changed or been withdrawn?
- How are schema changes made without breaking systems that depend on them?
Why exchange fails.
Interoperability fails at three levels. Technically, formats and protocols do not match. Semantically, the same field name means different things, so a status of active or a date of publication is silently misread. Organisationally, no one is responsible for keeping links current, so references decay. Semantic failures are the hardest to see because the data moves without error and is simply wrong at the destination.
Shared vocabularies address these. Linked-data formats such as JSON-LD carry meaning with the data, catalogue vocabularies such as DCAT describe datasets, and W3C PROV carries lineage. Methods from rekayasa data, interoperabilitas, dan pengelolaan cover these standards and their trade-offs. The Registry’s planned interfaces are described on interfaces.
Designing for exchange.
- 01
Link, do not copy
Records refer to external registries by identifier, preserving aliases so an external reference still resolves.
- 02
Documented semantics
Each field’s meaning, allowed values and version are published alongside any interface.
- 03
Versioned schemas
Schema changes take a new version, and older records keep the schema they were made under.
- 04
Batasan
Interoperability depends on partners maintaining their own records. Mappings between vocabularies lose nuance, and an export carries rights obligations that the receiving system must honour.
Cara hal ini dikaji, dan apa yang tidak dapat dinyatakan metodenya.
- 01Rekayasa data, interoperabilitas, dan pengelolaan dataPenyerapan data tervalidasi skema · Rekonsiliasi pengenal persisten · Perekaman silsilah dalam alur pemrosesanDiterapkan di sini
- 02Keamanan siber dan kriptografiRiwayat catatan yang menunjukkan perubahan · Ekspor dan rilis yang ditandatangani · Pemodelan ancaman pada jalur penyuntinganDiterapkan di sini
- 03Identitas digital dan sistem digital publikAutentikasi dan kewenangan penerbit · Disambiguasi kontributor oleh yang bersangkutanDiterapkan di sini
Where this page’s references lead.
Badan dan dokumen yang menjadi acuan halaman ini. Status dan edisi berubah; setiap tautan menuju badan penerbitnya.
Tanya jawab.
What makes a reference stable?
Why not just use web addresses?
What is a crosswalk?
How are interface changes announced?
Is there an interface I can use now?
Will exports include restricted records?
Can my registry link to registry records?
Kontribusikan bukti dari halaman ini.
Laporan is the Consortium’s quarterly publication. What you know about this subject can become evidence, a case or a correction in the next edition, credited to you and published under CC BY 4.0 where it is your own work.
- SurelGerbang GW-GCRIKirim dari halaman iniBukti, koreksi, kasus, metode, tinjauan, terjemahan, atau masukan profil. Kiriman tiba dengan label halaman ini, sehingga editor pemiliknya menerimanya.
- ZenodoDeposit terbukaDeposit dan ajukan ke komunitasTerbitkan catatan Anda sendiri di Zenodo dengan ORCID iD Anda, lalu ajukan ke komunitas Reports di sana. Kurator meninjaunya; DOI tetap milik Anda.
- LaporanGCRILihat semua cara berkontribusiJenis kontribusi, cara masing-masing ditinjau, kredit yang Anda terima, lisensinya, dan apa yang tidak pernah diterima.
Jangan pernah mengirim data pribadi, rincian infrastruktur sensitif, atau apa pun yang tidak berhak Anda bagikan. Kontribusi ditinjau sebelum digunakan. Mengirimkannya tidak memberikan hak kepenulisan atau editorial, dan sponsor tidak pernah membeli sebuah temuan.
Bawa metode, dataset, atau pertanyaan.
Informasi dan pertanyaan sudah terbuka hari ini. Sebuah pertanyaan menerima nomor referensi dan menyebutkan langkah berikutnya; lamaran, pembayaran, alokasi komputasi, dan pendaftaran hanya dibuka ketika tim, ketentuan, dan kapasitas tinjauannya tersedia.
Dokumen hukum.
Peta, data, dan gambar di situs ini ditampilkan untuk konteks dan informasi umum. Semua itu bukan nasihat, prakiraan, atau peringatan; batasan informasinya dijelaskan dalam Penafian dan Pemberitahuan Data.