separate objects for inbound and outbound types

nmfta-repo / nmfta-opentelematics-api

API Blueprint for Open Telematics API

Apache License 2.0

13 stars 6 forks source link

separate objects for inbound and outbound types #44

Closed BenGardiner closed 5 years ago

BenGardiner commented 5 years ago

There are different, incompatible needs in specifying the data objects coming from and going to the Open API.

e.g. Driver

When retrieving through OpenAPI, the providerId field is mandatory, but when sending to the OpenAPI, that field should be omitted (in the schema, ignored in the body if present)