GCRI · Registry
Interoperabilidad de los registros
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.
Cómo se desarrolla el trabajo.
Interoperability console
Registry interoperability · Crosswalk · Profile v3
Field mappings
| identificador | id | copy | Aprobado |
| evidence_label | quality.label | enum map | Aprobado |
| licence | rights.licence | SPDX id | Ambiguous |
| version | version | semver | Aprobado |
Conformidad
Fig.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 sistemas then merge what is distinct or split what is one.
How registry interoperability is modelled, measured and tested.
El modelo, sus supuestos, sus datos y su incertidumbre, en la forma en que un científico o un ingeniero los comprobaría. Las estructuras siguen métodos publicados. Los valores representados son ilustrativos, no hallazgos.
Conjuntos de datos y procedencia
The data classes behind registry interoperability and what is recorded about each before it is used.
| Clase de datos | Procedencia registrada | Resolución indicada | Licencia verificada |
|---|---|---|---|
| Imágenes satelitales, ópticas y de radar | sensor, nivel de procesamiento, fecha de adquisición | tamaño de píxel y revisita | por escena |
| Reanálisis y resultados de modelos climáticos | modelo, experimento, miembro, versión | malla y paso temporal | por publicación |
| Sensores y estaciones de medición in situ | estación, instrumento, registro de calibración | punto y frecuencia de muestreo | por red |
| Exposición de la población y los activos | método, cosecha, fuentes de entrada | tamaño de celda y unidad | por publicación |
| Límites y geografía de referencia | productor, edición, fecha | escala | por edición |
- Linaje
- Registro W3C PROV de la fuente a la figura
- Principios
- FAIR: localizables, accesibles, interoperables, reutilizables
- Brechas
- se muestra como ausente, nunca se rellena en silencio
Interoperability lets records from each domain move between systems.
- AguaEn la prácticaHydrological metadata map to WMO and DCAT profiles.What a reader can checkCrosswalks
- BiodiversidadEn la prácticaBiodiversity records map to Darwin Core through GBIF.What a reader can checkMapping completeness
- AlimentaciónEn la prácticaStatistical series map to SDMX where agencies use it.What a reader can checkExchange formats
Interoperability methods are designed for the serie Methods and Technical. Crosswalks to external standards are the subject of NS-14 in the proposed Nexus Standards, with no conformity claimed.
- Crosswalk proposals.
- Interoperability test results.
Qué se mide y con qué calidad.
Cada indicador lleva su unidad, su periodicidad, el tipo de fuente que lo respalda y la etiqueta de evidencia que llevaría un valor. No se muestran valores: un programa los aporta bajo su propia autoridad.
| Indicador | Unidad | Cadencia | Tipo de fuente | Etiqueta |
|---|---|---|---|---|
| Identifier resolution success | share of resolution probes | diario | Resolver probes | OBSERVADO |
| Interface availability | share of time available | continuo | Availability monitoring | OBSERVADO |
| Export schema conformance | share of exported records validating | por publicación | Schema validation | OBSERVADO |
| Crosswalk coverage | share of fields mapped to the target schema | por publicación | Crosswalk register | DECLARADO |
| Round-trip fidelity | share of records returned intact | por publicación | Round-trip test | OBSERVADO |
| Broken outbound references | share of references | mensual | Link checking | OBSERVADO |
| Deprecation notice period | días | per interface change | Change log | DECLARADO |
| Records linked to external persistent identifiers | share of records | mensual | Identifier reconciliation | OBSERVADO |
De dónde procede la evidencia.
Conjuntos de datos públicos y registros institucionales identificados, cada uno con su tipo de licencia. Las fuentes obtenidas por acuerdo solo se utilizan conforme a sus condiciones y nunca se republican.
| Fuente | Lo que aporta | Tipo de licencia |
|---|---|---|
| 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 |
| Especificación OpenAPI | A standard description format for HTTP interfaces | Open specification, Apache licence |
Quién decide y a qué sirve la evidencia.
Registry prepares evidence. The decisions below are taken by the authorities named, under their own rules, and never by the platform.
| Quién decide | La pregunta | Evidencia a la que sirve esta página |
|---|---|---|
| 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 |
| Custodios de datos | 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 |
Productos que genera este tema
- 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 sistemas 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 ingeniería, interoperabilidad y custodia de datos 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
Límites
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.
Cómo se estudia y lo que los métodos no pueden decir.
- 01Ingeniería, interoperabilidad y custodia de datosIngesta validada por esquemas · Conciliación de identificadores persistentes · Captura del linaje en las cadenasAplicado aquí
- 02Ciberseguridad y criptografíaHistorial de registros con evidencia de manipulación · Exportaciones y versiones firmadas · Modelización de amenazas de las vías de ediciónAplicado aquí
- 03Identidad digital y sistemas digitales públicosAutenticación y autoridad del emisor · Desambiguación de los colaboradores por la propia personaAplicado aquí
Where this page’s references lead.
Los organismos y documentos con los que se lee esta página. El estado y las ediciones cambian; cada enlace lleva al organismo emisor.
Preguntas y respuestas.
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?
Aporte evidencia desde esta página.
serie Reports 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.
- Correo electrónicoPasarela GW-GCRIEnvíelo desde esta páginaEvidencia, una corrección, un caso, un método, una revisión, una traducción o un aporte a un perfil. Llega etiquetado con esta página, de modo que lo recibe el editor responsable.
- ZenodoDepósito abiertoDeposítelo y envíelo a la comunidadPublique su propio registro en Zenodo con su ORCID iD y luego envíelo a la comunidad de Reports allí. Los curadores lo revisan; el DOI sigue siendo suyo.
- serie ReportsGCRIVer todas las formas de contribuirLos tipos de contribución, cómo se revisa cada uno, qué crédito recibe, la licencia y qué nunca se acepta.
No envíe nunca datos personales, detalles sensibles de infraestructura ni nada que no tenga derecho a compartir. Un aporte se revisa antes de su uso; enviarlo no confiere autoría ni derechos editoriales, y el patrocinio nunca compra un hallazgo.
Aporte un método, un conjunto de datos o una pregunta.
La información y las consultas están abiertas hoy. Una consulta recibe una referencia e indica el siguiente paso; las solicitudes, pagos, asignaciones de cómputo y registros solo se abren cuando existen su equipo, sus condiciones y la capacidad de revisión.
Documentos jurídicos.
Los mapas, datos y cifras de este sitio se muestran como contexto e información general. No son consejos, pronósticos ni avisos; los límites de la información se exponen en los Descargos de responsabilidad y los Avisos sobre datos.
