Introduce Conditions and Confirmations

Conditions and confirmations can optionally be used to select or confirm additional options. This feature replaces doc.storageid in requests for instance to select pick-up locations.

PAIA auth requires application/x-www-form-urlencoded

PAIA auth MUST support content type application/x-www-form-urlencoded to align with OAuth 2.0

Support CORS

• added mandatory HTTP OPTIONS and optional HTTP HEAD requests
• extended CORS headers (Access-Control-...)
• fixed name of WWW-Authenticate header
• removed request field doc.storage and deprecate field doc.storageid
• improved documentation

language negotiation, optional scopes, ontology

• support content-negotiation for languages of textual response fields (issue #32)
• allow additional scopes not part of PAIA
• split PAIA ontology (http://purl.org/ontology/paia) from PAIA specification.

Added patron field type

A list of custom patron type URIs can be included to identify patron types. Its up to the client to make sense of this types.

added patron field address

The address of a patron can be included with an optional free text field (#29)

added CORS HTTP headers

To support Cross-Origin Resource Sharing (CORS) a server should include the CORS HTTP headers (issue #37).

extended definition of datetime fields

Datetime values (starttime, endtime, expires) can now include time and timezone.

added document fields starttime and endtime

The document fields starttime and endtime can be used to indicate when a document status began and ended, respectively.

added User-Agent header

Clients SHOULD send an approriate User-Agent request header with client name and version.