Allow Reference Object for 'tags' property of Swagger Object

[gobengo]

I have a directory of swagger files to describe all of my APIs, primarily because they are scattered across a few hostnames, and the Swagger Object only supports a single 'host' value.

However, I'd like to be able to share a common set of Tag Objects throughout these other Swagger Files. I looked into creating a distinct 'tags' file, then using a Reference Object in each API spec to point to that.

However, currently the value of SwaggerObject#tags can only be an array of tag objects.

Is there any reason not to allow it to be a Reference Object in the next version of the spec syntax?

FWIW swagger-tools validate doesn't let me add one now. swagger-parser doesn't mind, though, and will resolve the reference object.

[webron]

I imagine we're going to expand support for references in the next version, covering more locations. One option would be to say where references are not allowed instead of the other way around.

[unional]

I have the same need. In my case, it's about i18n

Redocly/redoc#430

[handrews]

Closing in favor of #2905 which is the same request but has a more thorough use case documented.