[OASIS Issue Tracker] Updated: (EMIX-379) need EMIX naming/designrules

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

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

William Cox updated EMIX-379:
-----------------------------

    Affects Version/s: wd22
          Environment: Anne Hendry

Editing to add environment (submitter) and affected version (wd22).

Comment:
This is a good idea -- the NIEM approach is documented (via non-Normative reference) but the approaches take could be an expansion of Section 3 (line 302 in referenced wd22) in place or to an appendix.  Section 3 addresses portions of this issue.

I think that Section 3 is adequate for public review; this should go on the list of change coming out of PR02.

> need EMIX naming/design rules
> -----------------------------
>
>                 Key: EMIX-379
>                 URL: http://tools.oasis-open.org/issues/browse/EMIX-379
>             Project: OASIS Energy Market Information Exchange (eMIX) TC
>          Issue Type: Improvement
>          Components: spec
>    Affects Versions: wd22
>         Environment: Anne Hendry
>            Reporter: Anne Hendry 
>            Assignee: William Cox
>
> This was raised by the NIEM conformance question in issue 340 but is needed regardless as a place for EMIX schema design to be clarified and to allow EMIX conformance to be defined.
> This should also help tremendously in bringing more immediate consistency to the schema.
> See proposal.

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