OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

emix message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: [OASIS Issue Tracker] Updated: (EMIX-347) Editorial issues, Section1, wd22-with-change.doc



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

William Cox updated EMIX-347:
-----------------------------

        Parent: EMIX-346
    Issue Type: Sub-task  (was: Improvement)

> Editorial issues, Section 1, wd22-with-change.doc
> -------------------------------------------------
>
>                 Key: EMIX-347
>                 URL: http://tools.oasis-open.org/issues/browse/EMIX-347
>             Project: OASIS Energy Market Information Exchange (eMIX) TC
>          Issue Type: Sub-task
>          Components: spec
>            Reporter: Anne Hendry 
>            Assignee: William Cox
>
> General issue
> =============
> Many, many occurrences of different forms of
>   "Energy Market Information Exchange Technical Committee",
>   "Technical Committee",
>   " (TC)", "(EMIX)", "(EMIX TC)", etc.
>   throughout the document.
>   Short form sometimes used before full term is expressed.
> Define once long form with acronym at the start.  Just use abbreviation thereafter.
> Specific line # issues
> ======================
> Line 5-6
> --------
> Delete the first sentence.
> Half of it is vague and the other half duplicates the next sentence.
> Line 194
> --------
> "... the standards listed in listed in the normative or non-normative ..."
> 'listed in' written 2x, remove one 'listed in'.
> Lines 196 and 310
> -----------------
> Duplicate information.
> Delete these two lines and move that information to
> heading of the 'Examples' section
> and any other sections that are non-normative (eg. appendices).
> 'Ancillary Services' appendix already does this.
> Line 291
> --------
> Delete.  Redundant.
> Lines 292 - 293
> ---------------
> Replace with
> "EMIX element and attribute names follow Lower Camel Case (LCC) convention."
> Lines 295 - 296
> ---------------
> Replace with
> "EMIX type names follow the UpperCamelCase (UCC) naming convention."
> Line 296
> --------
> Make the rule about appending the word 'Type' to the end of type names
> a separate sentence so you're not mixing the rules together.  Will make
> it easier for people to see and read that.
> Lines 305 - 307
> ---------------
> Delete.  Doesn't have to do with the section subject ('editing conventions').
> Or ...
> First sentence could be moved to section on 'transactive state'.
> Third sentence could be moved to section on 'inheritance'.
> Middle sentence stays deleted.
> Lines 308 - 309
> ---------------
> Delete. No longer relevant.
> Lines 315 - 319
> ---------------
> Delete.
> Replace with
> "EMIX specification uses the common market terms as defined in Table 3-6:
> Transactive States Enumeration." 

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

        


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]