FHIR Chat · Ballot reconciliation - config.json · smart

Stream: smart

Topic: Ballot reconciliation - config.json


view this post on Zulip Isaac Vetter (Oct 01 2018 at 22:54):

Josh - let me know if the accepted ballot comment included this. Here's the PR

In conformance, Why is the scopes_supported metadata json element RECOMMENDED instead of OPTIONAL ? It seems like this field is most important when dynamic registration is available, but registration_endpoint is OPTIONAL ?

view this post on Zulip Josh Mandel (Oct 01 2018 at 22:59):

scopes_supported is useful with or without dynamic registration, since scopes can also be used statically (e.g. in an endpoint directory, it's nice to be able to determine how many servers support a specific scope or other capability) and also at runtime (since a registered app can request a limited number of scopes then it launches).

view this post on Zulip Josh Mandel (Oct 01 2018 at 23:00):

We can review the ballot reconciliation spreadsheet if we want to see exactly what we voted on.

view this post on Zulip Isaac Vetter (Oct 01 2018 at 23:11):

Endpoint directory feels like a secondary use.

I'd vote to align scopes_supported with registration_endpoint. :upside_down_face:

view this post on Zulip Josh Mandel (Oct 01 2018 at 23:18):

I'm not sure I see the connection. Scopes are explicitly part of the spec, whereas dynamic registered is optional.

view this post on Zulip Josh Mandel (Oct 01 2018 at 23:18):

How are they linked?

view this post on Zulip Isaac Vetter (Oct 01 2018 at 23:19):

Outside of dynamic registration, an app is limited to a subset of the scopes negotiated during the registration process.

view this post on Zulip Josh Mandel (Oct 01 2018 at 23:21):

And also by the scopes a server supports. Without Dynamic registration, what is a developer supposed to do? Copy down all the steps at the time they register app and save it in a database somewhere? At least a configuration file makes the full list of scopes available programmatically.

view this post on Zulip Isaac Vetter (Oct 01 2018 at 23:25):

I think that scopes are recorded at the same time as the client identifier.

view this post on Zulip Isaac Vetter (Oct 01 2018 at 23:25):

Without the ability to display the scopes specific to the client, we're either going to have hundreds+ of scopes or only two: user.* and patient.*.

view this post on Zulip Josh Mandel (Oct 01 2018 at 23:26):

Something like hundreds plus two sounds right to me. Is that crazy?


Last updated: Apr 12 2022 at 19:14 UTC