1 / 8

Exchange formats and APIs

Exchange formats and APIs. Questions how and when to access metadata? lifecycle/status – how to access? can things disappear? is CSV enough? is Atom enough? Need to know use cases for exchange update of register by maintainer access to latest version

imelda
Download Presentation

Exchange formats and APIs

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Exchange formats and APIs • Questions • how and when to access metadata? • lifecycle/status – how to access? can things disappear? • is CSV enough? • is Atom enough? • Need to know use cases for exchange • update of register by maintainer • access to latest version • mirror/federate e.g. for performance or discovery

  2. Update • Up to the registry service and its own workflow • INSPIRE – CSV ingest • EEA – offline batch processing, source scraping • UK – RDF via REST API, separate CSV to RDF service • ...

  3. Access • focus on content not metadata • variety of formats • RDF • CSV • JSON(LD) • ISO 19135-2 XML • ... • support RDF • but with what vocabularies? • not just SKOS

  4. Federation/mirroring • Need full metadata • May or may not need version history • current, tagged snapshots, whole history • API should support different views? • Formats • Atom enables discovery of what’s changed • ISO19135-2 XML encoding when doing full metadata exchange including management information • can also support RDF formats • CSV not so suitable here

  5. APIs • access • with metadata • register only or with content • paging control for large lists • version - history, version at time, tagged version • validation • search • text and structured properties (facets) • workflow & user management • out of scope • proposal and reservation

  6. Propose/reserve • could submit empty entry to registry? • API to propose entry? • separate proposal service • preview • discuss and refine • only submit to registry when agreed • though can still be rejected by Register Manager

  7. API Conclusions • agree REST API • some clarification of use cases and requirements • separation of proposals and discussions, workflow • detailed API would require real design effort • precise list of operations • URL templates • precise data model and formats in the exchange • status flags

More Related