Support multiple contacts in info object

[silverwind]

The info object currently only allows a single contact object. I think it would be very useful to support an array of contact objects for projects with multiple people unrelated to each other working on it.

[MikeRalphson]

Although the contact.email property can of course reference a group or email list, this is unlikely to be sufficient in all cases, and it should be noted that the folks over at SmartAPI also identified this need in their extensions along with an x-role property. cc @micheldumontier

[silverwind]

A backwards-compatible way to support this could be to allow both the object (single contact) and array (multiple contacts) forms for the contact property.

[MikeRalphson]

A backwards-compatible way to support this could be to allow both the object (single contact) and array (multiple contacts) forms for the contact property.

For consistency with other areas of the OAS, we might prefer to have mutually exclusive contact and contacts properties (as is done for example and examples) rather than allowing one property to take values of two different types.

[darrelmiller]

Feels like the responsibility of something like http://apisjson.org/format.html rather than adding to OAS.

[ioggstream]

This thread is interesting. apisjson.org seems stuck in 2016 though.

[typekpb]

hello, any movement in this area? we're also affected

[prashanth-kumaraswamy]

Hi Team,
we have any solution for this ? we are also facing same issue
Thanks
Prashanth

[handrews]

@prashanth-kumaraswamy due to SemVer, this would probably need to be addressed in Moonwalk (OAS 4).

We are also currently working on tidying up the backlog to make the status of various issues more clear, see #3516 for details.