Discovery info for processedtemplates & templates both have kind: Template

This might not be a bug, but creates complications for dynamic clients parsing discovery info:

Both oapi/v1 and apis/template.openshift.io/v1 have 2 different paths with same kind:

      "name": "templates",
      "namespaced": true,
      "kind": "Template",
      "verbs": ["create", "delete", "deletecollection", "get", "list", "patch", "update", "watch"],
...
      "name": "processedtemplates",
      "namespaced": true,
      "kind": "Template",
      "verbs": ["create"],

1. Given kind: Template input, how does oc know which of the endpoints to hit?

2. Could anything be added to discovery to make this unambiguous?

3. What is the difference between /templates and /processedtemplates anyway?
   Do clients need both or can I just hardcode preference to /templates?

4. The docs are non-helpful — don't explain the difference — and weird:

   • https://docs.openshift.com/container-platform/3.11/rest_api/apis-template.openshift.io/v1.Template.html documents "kind": "Template" for both endpoints.
   • https://docs.openshift.com/container-platform/3.11/rest_api/oapi/v1.Template.html documents "kind": "ProcessedTemplate" for /templates. 🐛
     Is kind ProcessedTemplate a real thing?
   • https://docs.openshift.com/container-platform/3.11/rest_api/oapi/v1.ProcessedTemplate.html documents "kind": "ProcessedTemplate" for /processedtemplates.

   The docs are organized by kind, could it be they're buggy as result of this collision?

Version

oc v3.11.0+8de5c34
kubernetes v1.10.0+d4cacc0
features: Basic-Auth GSSAPI Kerberos SPNEGO

Server https://192.168.99.103:8443
kubernetes v1.11.0+d4cacc0

Steps To Reproduce

1. curl $API/apis/template.openshift.io/v1/
2. curl $API/oapi/v1/

Current Result

Duplicate entries with different name but same kind.

Expected Result

Ideally, exactly one name per kind (ignoring subresources like routes/status).
If kind ProcessedTemplate really exists, can that be reported for "name": "processedtemplates"?
If impossible, some hint in discovery info helping decide between the two?

Additional Information

FWIW, there was a similar collision up to openshift 3.6 between DeploymentConfig /generatedeploymentconfigs and DeploymentConfig /deploymentconfigs. generatedeploymentconfigs is gone in 3.7+ discovery info.

Start by running the two curl requests in the reproduction steps and compare the templates and processedtemplates entries in both discovery responses. Read the linked kubeclient discussion and the referenced OpenShift REST API documentation to establish the intended distinction. Done means the collision and ProcessedTemplate naming are resolved or clearly documented, with discovery and docs made consistent.