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

lower-case musts in Content Sharing seems to need to be normative requirements

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive with Modification
    • Icon: Medium Medium

    Description

      If an implementation doesn't obey these lower-case musts, is it still conformant to FHIRcast content sharing?

      * the context.versionId does not need to follow any convention but must unique in the scope of a topic

      * Clients wishing to exchange structured information must:  [*iav - and all six of the bullets following this phrase]

      If not, it seems like they need to be normative requirements.

       

      Attachments

        Activity

          People

            Unassigned Unassigned
            Isaac.Vetter Isaac Vetter
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: