Uploaded image for project: 'OASIS Classification of Everyday Living (COEL) TC'
  1. OASIS Classification of Everyday Living (COEL) TC
  2. COEL-113

RPE - Missing definitions and terms

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Blocker
    • Resolution: Fixed
    • Environment:

      Technical

    • Proposal:
      Hide

      I think RPE mixes what could be requirements, such as exclusion of some roles (assuming those are adequately defined) from occurring together, with hopes for non-technical aspects, non-profit, free of charge, etc. for organizational aspects.

      It's hard to estimate the number of additional definitions required but I suspect it numbers in the hundreds. (Ex. "and the purposes of marketing the specification." ???) Purging RPE of those sort of provisions may reduce the number of additional definitions down to a manageable number.

      Reorganizing and defining the roles and their requirements will make writing the conformance clauses (the only place you need SHALL, SHALL NOT, MAY) much easier.

      Show
      I think RPE mixes what could be requirements, such as exclusion of some roles (assuming those are adequately defined) from occurring together, with hopes for non-technical aspects, non-profit, free of charge, etc. for organizational aspects. It's hard to estimate the number of additional definitions required but I suspect it numbers in the hundreds. (Ex. "and the purposes of marketing the specification." ???) Purging RPE of those sort of provisions may reduce the number of additional definitions down to a manageable number. Reorganizing and defining the roles and their requirements will make writing the conformance clauses (the only place you need SHALL, SHALL NOT, MAY) much easier.

      Description

      This is partially a style issue as well but I will treat it as a technical one.

      Before 2.2 Identity Authority - 2.6 Consumer, the standard must define all the terms that appear in normative prose. (Stylistically, creating what appear like conformance requirements mixed with normative statements makes this even more confusing.)

      I will do part of 2.2 Identity Authority as an example. The same concerns are found in all the other sections through 2.6.

      SHALL (should appear in conformance clause)

      *****
      Maintain an always-on IDA service that will generate or validate unique Pseudonymous Keys for Data Engine, Service Provider & Operator
      *****

      "always-on" - undefined

      "IDA service" - undefined

      "generate or validate" - neither is defined (necessary for interoperability)

      "Pseudonymous Keys" - The closest thing I found to a definition: "The unique Pseudonymous Keys are generated by the IDA for use with the ecosystem to provide unique codes for the data and transaction of Consumers, Devices, Operators and Service Providers."

      Wishful thinking at best, no two implementation are likely to reach the same solution.

      Next shall:

      "Be a non-profit legal entity" - Really? Not defined and I'm not sure why this is even relevant.

      Next shall:

      "Provide its services on a fair, reasonable and non-discriminatory basis"

      Again, not defined.

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              chet-oasis Chet Ensign
            • Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: