Reverting changes related to the supported_scopes

Revert #83

Author: appsdesh

openid-sharedsignals-framework-1_0.md

@@ -537,43 +537,10 @@ critical_subject_members
 
 > OPTIONAL. An array of member names in a Complex Subject which, if present in
   a Subject Member in an event, MUST be interpreted by a Receiver.
-  
-supported_scopes
-
-> OPTIONAL. A list of OAuth {{RFC6749}} scope names that the Transmitter supports for specific endpoints. The value of this field is a JSON object that has the endpoint names as keys, and arrays of scope name strings they support as their values. OAuth tokens obtained using any of the scopes defined here MUST be accepted by the specified endpoint. Any key that is not defined as an endpoint in the Transmitter Configuration Metadata MUST be ignored. If the supported_scopes member is present in the metadata and an endpoint is not listed as a key, then that endpoint MUST not require OAuth for authorization.
-
-authorization_servers
-
-> OPTIONAL. An array of supported authorization servers and the scopes they support. Each element of the array is a Authorization Server Descriptor JSON object defined in the section {{authz-server-descriptor}} below. If the `supported_scopes` member is present in the metadata, then the `authorization_servers` MUST also be present, and it MUST provide a server location for every supported scope.
 
 TODO: consider adding a IANA Registry for metadata, similar to Section 7.1.1 of
 {{RFC8414}}. This would allow other specs to add to the metadata.
 
-### Authorization Server Descriptor {#authz-server-descriptor}
-An Authorization Server Descriptor is a JSON object that has two keys:
-
-scopes
-
-> REQUIRED. An array of scope names supported by the authorization server
-
-servers
-
-> REQUIRED. An array of authorization server URLs. This is the URL from which the Authorization Server Metadata MAY be obtained by following the process described in Section 3 of RFC8414 {{RFC8414}}
-
-The following is a non-normative example of an Authorization Server Descriptor
-
-~~~ json
-{
-    "scopes" : ["scope1", "scope2"],
-    "servers": [
-        "https://server1.example/base/url",
-        "https://server2.example/base/url",
-        "https://server3.example/base/url"
-    ]
-}
-~~~
-{: #authz-descriptor-example title="Example Authorization Server Descriptor"}
-
 ## Obtaining Transmitter Configuration Information
 
 Using the Issuer as documented by the Transmitter, the Transmitter Configuration
@@ -670,17 +637,7 @@ Content-Type: application/json
     "https://tr.example.com/ssf/mgmt/subject:remove",
   "verification_endpoint":
     "https://tr.example.com/ssf/mgmt/verification",
-  "critical_subject_members": [ "tenant", "user" ],
-  "supported_scopes":
-      {
-        "status_endpoint": ["status_scope"],
-        "configuration_endpoint": ["admin_scope", "status_scope"]
-      },
-  "authorization_servers": [
-      {
-          "scopes": ["admin_scope", "status_scope"],
-          "servers": ["https://myauthzserver.example"]
-      }
+  "critical_subject_members": [ "tenant", "user" ]
   ]
 }
 ~~~