"description": "A short human-friendly name for the sofware release",
"type": "string"
},
"description": {
"description": "A short description of the sofware release",
"type": "string"
},
"serialisation": {
"description": "How the parameters and results are serialised",
"required": true,
"enum": ["xml", "json-in-xml"],
"type": "string"
},
"software-type": {
"description": "Existing software types",
"required": true,
"patternProperties": {
".*": {
"description": "Software type declaration",
"additionalProperties": false,
"properties": {
"description": {
"description": "A human-friendly description of the software type",
"type": "string"
},
"serialisation": {
"description": "How the parameters and results are serialised, if different from global setting",
"enum": ["xml", "json-in-xml"],
"type": "string"
},
"request": {
"required": true,
"description": "URL, relative to Software Release base path, of a json schema for values expected by instance of current software type",
"type": "string"
},
"response": {
"required": true,
"description": "URL, relative to Software Release base path, of a json schema for values published by instance of current software type",
"type": "string"
},
"index": {
"description": "Value to use instead of software type id to sort them (in order to display most relevant software types earlier in a list, for example)",
"type": "any"
}
},
"type": "object"
}
},
"type": "object"
}
},
"type": "object"
}
Error handling
--------------
If instantiation descriptor does not exist, is not valid json or does
not conform to this schema, it is ignored and a fall-back
representation is used. Likewise, if a software type of an existing
instance is not defined in software-type object or referenced schema
does not exist or is invalid, the same fall-back representation is used
for considered software type.
A fall-back representation must allow full control to the user, without
any guided editing: user is expected to serialise on his own and
provides & receives raw strings as request and responses, respectively.
Request schemas, when present and valid, MAY be used to validate user
input.
It SHOULD be made possible for user to violate the schema just as it is
possible for existing instances to already violate schemas. These
violation should be represented in a way which makes as much sense as
possible: displaying recursively all object properties and iteratively
all list items with as appropriate as possible fields, with a fall-back
on free text input. These extra fields generated from existing data or
created on-the-fly by the user MUST NOT prevent schema-conforming
"description":"A short human-friendly name for the sofware release",
"type":"string"
},
"description":{
"description":"A short description of the sofware release",
"type":"string"
},
"serialisation":{
"description":"How the parameters and results are serialised",
"required":true,
"enum":["xml","json-in-xml"],
"type":"string"
},
"software-type":{
"description":"Existing software types",
"required":true,
"patternProperties":{
".*":{
"description":"Software type declaration",
"additionalProperties":false,
"properties":{
"description":{
"description":"A human-friendly description of the software type",
"type":"string"
},
"serialisation":{
"description":"How the parameters and results are serialised, if different from global setting",
"enum":["xml","json-in-xml"],
"type":"string"
},
"request":{
"required":true,
"description":"URL, relative to Software Release base path, of a json schema for values expected by instance of current software type",
"type":"string"
},
"response":{
"required":true,
"description":"URL, relative to Software Release base path, of a json schema for values published by instance of current software type",
"type":"string"
},
"index":{
"description":"Value to use instead of software type id to sort them (in order to display most relevant software types earlier in a list, for example)",