[OASIS Issue Tracker] Created: (EMIX-334) Add Glossary/Vocabularysection in spec for terms and acronyms/abbreviations

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

Add Glossary/Vocabulary section in spec for terms and acronyms/abbreviations
----------------------------------------------------------------------------

                 Key: EMIX-334
                 URL: http://tools.oasis-open.org/issues/browse/EMIX-334
             Project: OASIS Energy Market Information Exchange (eMIX) TC
          Issue Type: Improvement
          Components: spec
            Reporter: Anne Hendry 
            Assignee: William Cox
            Priority: Minor


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)


-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira