Skip to content

Structure of Specification

Andreas Kuckartz edited this page Jul 13, 2014 · 9 revisions

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

The conformance criteria are designed to enable the easy implementation of polyglot servers which can satisfy the requirements both of this specification and the OParl specification at the same time.

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.
Clone this wiki locally