Structure of Specification

The specification document will be very short and mostly consist of references to well-established external specifications and HTML-renderings of maschine readable files. To make this more understandable a separate Primer will be made available to demonstrate how everything works together.

Maschine readable components (with HTML rendering)

• Vocabulary specified using Hydra document
• Additional semantics specified using OWL

Verbal components

• JSON-LD Profile (for "simple" JSON)
• Interoperability with OParl

Conformance Criteria

These are designed to be enable the implementation of polyglot serverss which at the same time can satisfy requirements of the OParl specification.

Client

• MUST send Accept header with at least application:ld+json
• MAY send Accept-Language
• MUST handle language maps

Server

• MUST handle client requests with an Accept value of application:ld+json
• SHOULD use values provided by client with Accept-Language to determine the output of literals as language maps.