Uploaded image for project: 'Specification'
  1. SPEC-23

TERM_MAPPING.match should be coded/enumerated

    Details

    • Type: Change Request
    • Status: Closed
    • Priority: Trivial
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: Release 0.9
    • Component/s: openehr.rm.data_types
    • Labels:
      None
    • Change Description:
      Hide
      TB: should we go back to the original scheme of
      ���<���, ���=���, ���>���, based on ISO 2788 and ISO 5964? (ISO
      2788 = ���Guide to Establishment and development of monolingual
      thesauri��� and ISO 5964 = ���Guide to Establishment and
      development of multilingual thesauri���).

      Dipak - this will have to be a very simple approach if it is to be
      used consistently. Stan shepherd and henk lamberts originally
      proposed <, =, > as the set.
      Show
      TB: should we go back to the original scheme of ���<���, ���=���, ���>���, based on ISO 2788 and ISO 5964? (ISO 2788 = ���Guide to Establishment and development of monolingual thesauri��� and ISO 5964 = ���Guide to Establishment and development of multilingual thesauri���). Dipak - this will have to be a very simple approach if it is to be used consistently. Stan shepherd and henk lamberts originally proposed <, =, > as the set.
    • Approved By:
      PG

      Description

      TERM_MAPPING.match should be a coded or enumerated
      type since unbounded integers could be misused.

        Attachments

          Activity

            People

            • Assignee:
              OLDthomasbeale JeffJ
              Reporter:
              grahamegrieve Grahame Grieve (Inactive)
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: