Uploaded image for project: 'FHIR Specification Feedback'
  1. FHIR Specification Feedback
  2. FHIR-39994

Poor section organization and confusing use of "profile"

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive with Modification
    • Icon: Highest Highest
    • SMART on FHIR (FHIR)
    • 2.0.0
    • FHIR Infrastructure
    • (NA)
    • Hide

      Will refactor to include a table for this decision point. We might still keep the examples below the table to avoid wide tabular content (we'll try and see).

      Show
      Will refactor to include a table for this decision point. We might still keep the examples below the table to avoid wide tabular content (we'll try and see).
    • Josh Mandel/Rick Geimer: 17-0-0
    • Clarification
    • Non-substantive

    Description

      Structure and language of section 2.0.2.2.1 and 2.0.2.2.2 is poor. The phrase "for example:" on its own is not good language. Further, the meaningful content of the sections is actually in the section headers.

      Suggest replacing 2.0.2.2.1 and 2.0.2.2.2 with a single table (in a new section 2.0.2.2.1 or moved up to 2.0.2.2?) with entries:

      Is your app able to protect a secret? Suggested profile Examples
      yes confidential app App runs on a trusted server ...
      no public app ...

      Also, clarify that "profile" in these sections refers to OAuth 2 specification profiles (which you refer to above as "two types of apps", not profiles), and not to the profiles defined in this guide.

      Existing Wording:

      Use the confidential app profile if your app is able to protect a secret
      for example:

      App runs on a trusted server with only server-side access to the secret

      (Comment 10 - imported by: Ron G. Parker)

      Attachments

        Activity

          People

            Unassigned Unassigned
            Rongparker Ron G. Parker
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: