Uploaded image for project: 'Technical Committee Administration'
  1. Technical Committee Administration
  2. TCADMIN-4271

Request a Special Majority Vote to approve a candidate for OASIS Standard for Code List Representation (genericode) Version 1.0 from Code List Representation

    XMLWordPrintable

    Details

    • Type: Task
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Component/s: Ballot request
    • Labels:
      None
    • Environment:

      Code List 

      Description

      Your name:
        Andrea Caccia
      Project name:
        Code List Representation
      Project email address:
        [1]codelist@lists.oasis-open.org
      Title and version number:
        Code List Representation (genericode) Version 1.0
      Specification URL:
        [2]https://docs.oasis-open.org/codelist/genericode/v1.0/cs02/
      English-language summary of the specification:
        Code lists, often regarded simply as enumerated values, have been with us since long before computers. They should be well understood and easily dealt with by now. Unfortunately, they are not. As is often the case, if you take a fundamentally simple concept, you find that everyone professes to understand it with complete clarity. When you look more closely, you find that everybody has their own unique view of what the problem is and how it should be solved.
      If code lists were really so simple and obvious, there would already be a single, well-known and accepted way of handling them in XML. There is no such agreed solution, though. The problem is that while code lists are a well understood concept, people don’t actually agree exactly on what code lists are, and how they should be used.
      The OASIS Code List Representation format, “genericode”, is a single semantic model of code lists and accompanying XML serialization (supported by a W3C XML Schema) that can encode a broad range of code list information. The serialization is designed to IT-enable the interchange or distribution of machine-readable code list information between systems. Note that genericode is not designed as a run-time format for accessing code list information, and is not optimized for such usage. Rather, it is designed as an interchange format that can be transformed into formats suitable for run-time usage, or loaded into systems that perform run-time processing using code list information.
      Relationship to similar work:
        ISO/IEC 14662 Open-edi reference model provides standards for the inter-working of organizations through interconnected information technology (IT) systems (see Appendix F of genericode, The Open-edi reference model perspective of code lists for the relationship between the semantic and IT-enabling perspectives of business transactions in, respectively, the Business Operational View (BOV) and the Functional Services View (FSV).
      ISO/IEC 15944-10 IT-enabled coded domains as semantic components in business transactions details important aspects of the BOV of a “set of codes representing X”, where X is a semantic umbrella concept scope and individual codes are distinct and separate semantic concepts within that scope. Simple umbrella semantic examples are days of the week, countries of the world, and financial currencies. Individual distinct semantic concepts are “Tuesday” and “Thursday”, “Australia” and “Tanzania”, and “the US dollar” and “the Euro”.
      Some semantic concepts, such as days of the week, are accepted as given without the need for any governing Source Authority or coded domain Source Authority. Most other e-business semantic concepts involved in connecting the IT systems for the inter-working of organizations need such authoritative governance and managed publication of the semantics to be mutually understood by the expression of a code in a coded domain. Such code-level metadata could express linguistic or illustrative explication of the semantics of the given coded value unique key.
      Colloquially, such collections of codes of a coded domain are referred to as code lists. The genericode specification satisfies the FSV perspective of code lists by providing an IT-enabled expression of coded domains for the direct interchange or open publishing of their content and semantics in a machine-readable syntax.
      Link to Statement of Use #1:
        [3]https://lists.oasis-open.org/archives/codelist/202206/msg00002.html
      Link to Statement of Use #2:
        [4]https://lists.oasis-open.org/archives/codelist/202207/msg00004.html
      Link to Statement of Use #3:
        [5]https://lists.oasis-open.org/archives/codelist/202207/msg00004.html
      Links to additional Statements of Use
        No additional statement of use received at the date of submission
      Approval:
        [6]https://lists.oasis-open.org/archives/codelist/202211/msg00001.html
      Earlier attempts to standardize
        No
      ----------------------------------------------------------------------------------------
      [1] codelist@lists.oasis-open.org
      [2] https://docs.oasis-open.org/codelist/genericode/v1.0/cs02/
      [3] https://lists.oasis-open.org/archives/codelist/202206/msg00002.html
      [4] https://lists.oasis-open.org/archives/codelist/202207/msg00004.html
      [5] https://lists.oasis-open.org/archives/codelist/202207/msg00004.html
      [6] https://lists.oasis-open.org/archives/codelist/202211/msg00001.html

        Attachments

          Activity

            People

            • Assignee:
              chet-oasis Chet Ensign
              Reporter:
              acaccia Andrea Caccia
            • Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: