...

• authentication is still to be implemented (this very first pass uses no authentication). This will most likely be HTTP BasicAuth over HTTPS
• error codes not properly handled
• currently no ontology-level validation of externally-produced resource descriptions
• we currently do not enforce the association URI-foreign key (this will come)
• This is not thoroughly tested

The ei-x JSON request and response formats

...

exchangeInstance  -- the EIExchangeInstance JSON of the primary resource and secondary resources to be created/updated (no instance URI indicates that the resource should be created). Note that for updates, the API user must have claim permission over the resources (current user is hardcoded in the backend)

pretty -- true | false, return prettified JSON (useful for debugging)

...

InstanceUpdateResponse in JSON, indicating successes and failures

ei-x examples

Detailed examples to come. In the meantime, use the GET service to obtain an EIExchangeInstance representation of a resource.