This seems to me to be a common use case but I can't figure it out. What if I have some common data schema which is used all over the place but I want a different description on each one? E.g. a very simple example (mine is light-years more complicated):
components:
schemas:
Id:
type: integer
minimum: 1
description: Resource identity (primary key)
OnOffAuto:
type: string
enum:
- on
- off
- auto
Lights:
type: object
properties:
id:
$ref: '#/components/schemas/Id'
status:
$ref: '#/components/schemas/OnOffAuto'
>> description: Status of the lights. Value "auto" means they turn on at night and off in the morning.
Door:
type: object
properties:
id:
$ref: '#/components/schemas/Id'
status:
$ref: '#/components/schemas/OnOffAuto'
>> description: Status of the door. Value "auto" means it locks at night and unlocks in the morning.
Question is where to put the OnOffAuto "description" so it will have a different value each place the schema ref is used.
Also once again sure would be nice to have an openapi-3 tag... It is considerably different from version 2.