Uploaded image for project: 'OASIS Energy Interoperation TC'
  1. OASIS Energy Interoperation TC
  2. ENERGYINTEROP-378

Glossary/Vocabulary section to be included in spec for terms and acronyms/abbreviations

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Minor
    • Resolution: Won't Fix
    • Affects Version/s: wd22
    • Fix Version/s: wd22
    • Component/s: spec
    • Labels:
      None
    • Environment:

      Anne Henddry

    • Proposal:
      Hide

      Create glossary/terms section. This could be merged with appendix C (semantics from ws-calendar) or precede or follow that section.

      Possible entries in the vocabulary list could be:
      gluon
      transactive
      extrinsic/intrinsic (as used in the spec)
      resource
      asset
      etc.

      Many, many abbreviations could be moved into an abbreviation table and then only need to be described/spelled out once.

      Show
      Create glossary/terms section. This could be merged with appendix C (semantics from ws-calendar) or precede or follow that section. Possible entries in the vocabulary list could be: gluon transactive extrinsic/intrinsic (as used in the spec) resource asset etc. Many, many abbreviations could be moved into an abbreviation table and then only need to be described/spelled out once.
    • Resolution:
      Hide

      Opened in EMIX; this was inadvertently entered in Energy Interoperation.

      Show
      Opened in EMIX; this was inadvertently entered in Energy Interoperation.

      Description

      Especially when working deep within a specific domain with the hopes of generating interest in other domains, industry and cross-industry terms used in a spec need to be defined for the business reader and readers from other domains who may not be aware of specific industry definitions.

      To support broad, thorough, and actionable review of the spec we should provide a glossary/vocabulary containing definitions for the industry terms, acronyms, and abbreviations used. Everyone has their own interpretation of words. This spec brings in vocabulary from several domains. It is critical that the vocabulary used in the spec be interpreted consistently to provide the basic underpinning for consensus and successful future use.

      For examples on ways in which this is provided, see OASIS specs listed below, the NIST IKB (PAP 09 Deliverable 1), the NAESB documents, openADR spec, etc.

      http://docs.oasis-open.org/kmip/spec/v1.0/os/kmip-spec-1.0-os.pdf (Sec 1.1 and Appendix D)
      http://docs.oasis-open.org/xacml/2.0/access_control-xacml-2.0-core-spec-os.pdf (Sec 1)

        Attachments

          Activity

            People

            • Assignee:
              william.cox William Cox (Inactive)
              Reporter:
              ahendry Anne Hendry (Inactive)
            • Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: