1 / 5

CERIF & Arch & LOD TG meeting summary

CERIF & Arch & LOD TG meeting summary. REST API for CERIF CRIS. Basic operations presented Get entity types supported by a CRIS Incl. CERIF version supported & object counts in each entity Get semantic layer contents from a CRIS Get IDs of objects of a specific entity

eryk
Download Presentation

CERIF & Arch & LOD TG meeting summary

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. CERIF & Arch & LOD TG meeting summary

  2. REST API for CERIF CRIS • Basic operations presented • Get entity types supported by a CRIS • Incl. CERIF version supported & object counts in each entity • Get semantic layer contents from a CRIS • Get IDs of objects of a specific entity • Get detailed information about an object (by ID) • Search: • by classification • by federated identifier • Paging potentially large result sets

  3. OpenAIRE guidelines for CRIS managers • Provide orientation for CRIS managers to expose their metadata in a way that is compatible with the OpenAIRE infrastructure • Define the subset of the entire CERIF model applicable to OpenAIRE • Define what information relevant for OpenAIRE can be exposed by CRIS systems in CERIF XML • Validator needed • Example organisations: EKT, euroCRIS

  4. CERIF JSON? (JavaScript Object Notation) • Useful in combination with REST API • As an alternative format • Could be made parallel to CERIF XML • But that’s probably not too useful • For light-weight information exchange • Only subsets of the full information • E.g. pick one preferred language for the multi-lingual information • Purpose: make developers’ lives easier

  5. CERIF XML experience • Upgraded CERIF XML format since version 1.4 (2011) • Used in production systems • Structure o.k. • Difficulties met when using XML-object mapping tools (for imports) • Due to the flexibility

More Related