[Openid-specs-ab] Issue #1843: [Federation] Policy operators: The grant_types metadata is a JSON array, use scope as example instead (openid/connect)

[Vladimir Dzhuvinov]

New issue 1843: [Federation] Policy operators: The grant_types metadata is a JSON array, use scope as example instead
https://bitbucket.org/openid/connect/issues/1843/federation-policy-operators-the

Vladimir Dzhuvinov:

In the current draft 27:

[https://openid.net/specs/openid-connect-federation-1\_0.html#name-operators](https://openid.net/specs/openid-connect-federation-1_0.html#name-operators)

> Note that when a parameter is defined as a space-separated list of strings like for `grant_types` in \[[RFC7591](https://openid.net/specs/openid-connect-federation-1_0.html#RFC7591)\] `subset_of`, `superset_of` and `default` are still expressed as lists of strings.

We should have this instead:

> Note that when a parameter is defined as a space-separated list of strings, like `scope` in \[[RFC7591](https://openid.net/specs/openid-connect-federation-1_0.html#RFC7591)\], the `default`,  `subset_of` and `superset_of` policies are still expressed as JSON arrays of strings.

This issue is related to #1837.

[https://bitbucket.org/openid/connect/issues/1837/federation-metadata-policy-relying-party](https://bitbucket.org/openid/connect/issues/1837/federation-metadata-policy-relying-party)

‌