Potential issues with open api schema

[paul-rinaldi]

The yaml schema seems to have a number of issues...

Structural error at info
should have required property 'version'
missingProperty: version
At line 2

Semantic error at paths./member/congress/{congress}.get.operationId
Operations must have unique operationIds.
At line 3325

Semantic error at paths./member/{stateCode}
Equivalent paths are not allowed.
At line 3362

Semantic error at paths./committee/{congress}
Equivalent paths are not allowed.
At line 3872

Semantic error at paths./committee/{chamber}/{committeeCode}
Equivalent paths are not allowed.
At line 4169

Easily view these errors by pasting the open api specification in https://editor.swagger.io/

[paul-rinaldi]

Perhaps,

• the /congress endpoint should have an operationId of operationId: "congress_members_list" since it doesn't list congresses.
• version: "3.0" should be added to the info property
  These two eliminate two of the issues swagger raises.

Looks to me like

• /member/{statecode} and /member/{bioguideId} clash and that is causing Semantic error at paths./member/{stateCode} Equivalent paths are not allowed.
• /committee/{congress}/* and /committee/{chamber}/* clash and that is causing Semantic error at paths./committee/{congress} Equivalent paths are not allowed.
• I do not see why /committee/{chamber}/{committeeCode is flagged though.

These affect multiple paths and I'm not sure the effort required since I do not engage in this domain often.