REST-API: vagueness/issues in specification
This is a collection of vagueness and issues of the REST API specification:
- It is unclear how exactly the depth parameter should behave, or more precisely, which effect the possible values
core
,deep
,embedded
andresolve
should have on the returned object. - The AAS respository interface lacks specification.
- The response format is not specified for routes
/submodel/values
and/submodel/table
. - Does the parameter
identification.id
contain the wholeidentification
object or just the id attribute? Or does it work like a str in str filter? - Syntax and semantics are unspecified for parameter
filter
of/aas/views
.