GCRI · Registry
Registry 상호운용성
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.
일이 진행되는 방식.
Interoperability console
Registry interoperability · Crosswalk · Profile v3
Field mappings
| identifier | id | copy | 통과 |
| evidence_label | quality.label | enum map | 통과 |
| licence | rights.licence | SPDX id | Ambiguous |
| version | version | semver | 통과 |
적합성
그림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 시스템 then merge what is distinct or split what is one.
How registry interoperability is modelled, measured and tested.
모형, 그 가정, 데이터, 불확실성을 과학자나 엔지니어가 확인할 형태로 제시합니다. 구조는 발행된 방법을 따릅니다. 제시된 값은 예시이며 결과가 아닙니다.
데이터셋과 출처 이력
The data classes behind registry interoperability and what is recorded about each before it is used.
| 데이터 등급 | 출처 기록됨 | 해상도 명시 | 라이선스 확인됨 |
|---|---|---|---|
| 위성 영상, 광학 및 레이더 | 센서, 처리 수준, 획득 일자 | 화소 크기와 재방문 주기 | 장면별 |
| 재분석과 기후 모형 산출물 | 모형, 실험, 멤버, 버전 | 격자와 시간 간격 | 배포마다 |
| 현장 센서와 계측기 | 관측소, 장비, 교정 기록 | 지점과 표본 추출률 | 네트워크별 |
| 인구 및 자산 노출 | 방법, 연도, 입력 출처 | 셀 크기와 단위 | 배포마다 |
| 경계와 기준 지리 | 생산자, 판, 날짜 | 축척 | 판별 |
- 계보
- 출처에서 그림까지의 W3C PROV 기록
- 원칙
- FAIR: 찾을 수 있고, 접근 가능하며, 상호운용 가능하고, 재사용 가능한
- 격차
- 누락으로 표시하며, 결코 조용히 채우지 않음
Interoperability lets records from each domain move between systems.
Interoperability methods are designed for the 방법 및 기술 시리즈. Crosswalks to external standards are the subject of NS-14 in the proposed Nexus Standards, with no conformity claimed.
- Crosswalk proposals.
- Interoperability test results.
측정되는 것과 그 정확도.
각 지표에는 단위, 주기, 그 뒤의 출처 종류, 값에 붙을 근거 표시가 있습니다. 값은 표시하지 않습니다. 값은 프로그램이 자체 권한으로 제공합니다.
| 지표 | 단위 | 주기 | 출처 유형 | 라벨 |
|---|---|---|---|---|
| Identifier resolution success | share of resolution probes | 일별 | Resolver probes | 관측 |
| Interface availability | share of time available | 지속적 | Availability monitoring | 관측 |
| Export schema conformance | share of exported records validating | 배포마다 | Schema validation | 관측 |
| Crosswalk coverage | share of fields mapped to the target schema | 배포마다 | Crosswalk register | 신고됨 |
| Round-trip fidelity | share of records returned intact | 배포마다 | Round-trip test | 관측 |
| Broken outbound references | share of references | 월별 | Link checking | 관측 |
| Deprecation notice period | 일 | per interface change | Change log | 신고됨 |
| Records linked to external persistent identifiers | share of records | 월별 | Identifier reconciliation | 관측 |
근거의 출처.
이름이 명시된 공개 데이터셋과 기관 기록으로, 각각 라이선스 등급이 있습니다. 협약에 따른 출처는 그 조건에 따라서만 사용하며 결코 재게시하지 않습니다.
| 출처 | 제공하는 것 | 라이선스 등급 |
|---|---|---|
| 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 |
| OpenAPI 규격 | A standard description format for HTTP interfaces | Open specification, Apache licence |
누가 결정하며 근거는 무엇에 쓰이는지.
Registry prepares evidence. The decisions below are taken by the authorities named, under their own rules, and never by the platform.
| 결정 주체 | 질문 | 이 페이지가 제공하는 근거 |
|---|---|---|
| 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 |
| 데이터 관리자 | 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 |
이 주제가 생산하는 산출물
- 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 시스템 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 데이터 공학, 상호운용성 및 관리 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
한계
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.
Where this page’s references lead.
이 페이지를 읽을 때 기준이 되는 기구와 문서. 상태와 판은 바뀌며, 각 링크는 발행 기구로 연결됩니다.
질문과 답변.
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?
이 페이지에서 증거를 기여하십시오.
보고서 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.
- 이메일게이트웨이 GW-GCRI이 페이지에서 보내기증거, 정정, 사례, 방법, 검토, 번역 또는 프로필 입력 자료. 이 페이지의 태그가 붙어 도착하므로, 이를 담당하는 편집자가 받게 됩니다.
- Zenodo개방형 예치기탁하고 커뮤니티에 제출하기ORCID iD로 Zenodo에 직접 기록을 게시한 뒤, 그곳의 Reports 커뮤니티에 제출하십시오. 큐레이터가 검토하며, DOI는 귀하의 것으로 남습니다.
- 보고서GCRI모든 기여 방법 보기기여 유형, 각각의 검토 방식, 받게 되는 크레디트, 라이선스, 그리고 절대 받지 않는 것.
개인정보, 민감한 인프라 세부 정보, 공유할 권리가 없는 자료는 절대 보내지 마십시오. 기여물은 사용 전에 검토됩니다. 기여물을 보낸다고 해서 저작자 지위나 편집 권한이 부여되지 않으며, 후원으로 조사 결과를 얻을 수 없습니다.
방법, 데이터세트 또는 질문을 가져오십시오.
정보와 문의는 오늘부터 열려 있습니다. 문의에는 참조 번호가 부여되고 다음 단계가 안내됩니다. 신청, 결제, 컴퓨팅 할당, 등록은 해당 팀, 약관, 심사 역량이 갖추어졌을 때만 열립니다.
법률 문서.
이 사이트의 지도, 데이터와 그림은 맥락과 일반 정보로 제시됩니다. 조언, 예보 또는 경보가 아니며, 정보의 한계는 면책 고지와 데이터 고지에 나와 있습니다.