Apply an ontology JSON to a collection
Changed onMakes the collection's packages the file's: subscribes those it lacks, moves those it holds at another version to the file's version, and removes those the file does not list (a file without a packages key leaves them alone). Creates the classes and relationships the collection does not define yet and overwrites those it does, matched by type_id; classes and relationships the file leaves out stay. A package's class changed in the file is written as the collection's edited version of it; a package's relationships cannot change. All of it applies or none does: a package change that would leave instances of a type out of scope (409, naming the types), a type whose tier differs from the collection's, or any write a type endpoint would refuse fails the whole request with that endpoint's status, its detail led by the type id.
Request
- Base URLhttps://api.outerport.com (the document declares no server; this is the origin it was published from)
- AuthHTTP bearer
- TypeScriptA function with typed inputs. Its response is checked against the schema.
Path parameters
Request body
Response
Successful Response
Changes
- info
added the new optional request property
//// - info
added the new optional request property
/////// - info
added the new optional request property
/////// - info
added the new optional request property
///// - info
added the new optional request property
//// - info
added the new optional request property
//
- info
- info
added the new optional request property
//// - info
added the new optional request property
//// - info
added the new optional request property
//// - info
request property
list-of-types was widened by adding typesnullto media typeapplication/json - info
added the required property
to the response with the status - info
added the required property
to the response with the status
- info