[OASIS Issue Tracker] Updated: (EMIX-343) Acronyms -- needapproach/rule for handling acronyms

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

     [ http://tools.oasis-open.org/issues/browse/EMIX-343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

William Cox updated EMIX-343:
-----------------------------

    Environment: Anne Hendry

> Acronyms -- need approach/rule for handling acronyms
> ----------------------------------------------------
>
>                 Key: EMIX-343
>                 URL: http://tools.oasis-open.org/issues/browse/EMIX-343
>             Project: OASIS Energy Market Information Exchange (eMIX) TC
>          Issue Type: Improvement
>          Components: spec
>         Environment: Anne Hendry
>            Reporter: Anne Hendry 
>            Assignee: Toby Considine
>             Fix For: wd23
>
>
> Lines 298 - 301
> "For the names of intents, the names follow the lower camelCase convention, with all names starting with a lower case letter, EXCEPT for cases where the intent represents an established acronym, in which case the entire name is in upper case. 
> An example of an intent that is an acronym is the "SOAP" intent."
> This refers to 'established acronyms'.  Who will decide what is an 'established acronym'?  Does EMIX intend to publish a list?  Acronyms are generally an impairment to interoperability because they can stand for many things to different people.  Each industry has its own and there are crossovers (eg. GC vs REC, TIF, DUNS, ...) between industries and geographies.  The example above is a misleading example because it is a programming language acronym, rather than a [energy or other] business acronym.

-- 
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