title: Paths that differ only in query parameter names
body: <p>I'm using the swagger editor to document an existing API that allows a path to support two different requests that differ only in their query parameter names. For example:</p>
  
  <pre><code>swagger: '2.0'
  info:
    title: example
    version: 1.0.0
  host: example.com
  schemes:
    - http
  basePath: /WS
  paths:
    /Login:
      post:
        summary: Login
        description: |
          Log in
        parameters:
          - name: UserID
            in: query
            description: User ID
            required: true
            type: string
          - name: Password
            in: query
            description: User password
            required: true
            type: string
        responses:
          '200':
            description: Success
    /Login:
      post:
        summary: Login
        description: |
          Log in
        parameters:
          - name: UserID
            in: query
            description: User ID
            required: true
            type: string
          - name: Token
            in: query
            description: Authentication token
            required: true
            type: string
        responses:
          '200':
            description: Success
  </code></pre>
  
  <p>Here I support requests to <code>http://example.com/WS/Login?UserID=foo&amp;Passoword=bar</code> and <code>http://example.com/WS/Login?UserID=foo&amp;Token=dubdu22r8dwjgd767dg</code>.</p>
  
  <p>The swagger editor doesn't show any errors for the above yaml, but it only generates documentation for the <em>second</em> path (the one with UserId and Token queryparams), not both. Can someone point out where I'm going wrong? Thanks.</p>
  
  <p><strong>Edit:</strong></p>
  
  <p>If I change the second <code>/Login:</code> path to (for example) <code>/Login1:</code> then I see both paths in the documentation. Not a solution though.</p>
  
  <p>It also occurs to me that I could specify one <code>/Login:</code> path with a required <code>UserID</code> parameter and optional <code>Password</code> and <code>Token</code> parameters. But how do I specify that <em>exactly one</em> of <code>UserID</code> and <code>Password</code> must be supplied?</p>