Jangle core communicates to connectors via HTTP. The connector responses are JSON objects.
Jangle core should submit all incoming HTTP header information to the connector (excluding accept headers). The content-type that Jangle core should request from the connector is application/json. The core is expected to also send an additional header, X-Connector-Base which is set to the URI of the Jangle core host and the path to the connector.
Example of X-Connector-Base header:
X-Connector-Base: http://demo.jangle.org/openbiblio/
Without this header, a Jangle connector cannot construct appropriate URIs, especially within the resource data.
The core should return the HTTP status codes verbatim from the connector.
Connector entity paths do not have to conform to the Jangle entity names. The paths to entities must be declared in the connector services response, however all public Jangle URIs must conform to the Jangle entity URI structure.