[OASIS Issue Tracker] Commented: (EMIX-339) Various minor editorialissues

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

    [ http://tools.oasis-open.org/issues/browse/EMIX-339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=25166#action_25166 ] 

Edward Cazalet  commented on EMIX-339:
--------------------------------------

Transaction has a very specific meaning in EMIX as defined by the schema.

An Agreement and a Program and in some cases a  Contract are viewed  in EMIX and EI as enabling "Agreements or Contracts" for transactions.  For example, Parties may agree to transact under an agreement that they all sign that specifics that they will use  OPNADR or TeMIX profile of EI and EMIX and that settlements and payments will be carried out by a process defined in the enabling agreement or contract.

> Various minor editorial issues
> ------------------------------
>
>                 Key: EMIX-339
>                 URL: http://tools.oasis-open.org/issues/browse/EMIX-339
>             Project: OASIS Energy Market Information Exchange (eMIX) TC
>          Issue Type: Sub-task
>          Components: spec
>    Affects Versions: wd22
>         Environment: William Cox
>            Reporter: William Cox
>            Assignee: William Cox
>            Priority: Minor
>             Fix For: wd23
>
>
> Line 352 Extra line of text should be deleted -- refers to the present section
> Line 192 delete "the"
> Section 2.2 - it's jarring to start out with a lot of TEMIX description, then on line 192 refer to adopting much of the TEMIX terminology. Reorder; also shouldn't be "The Emix TC" rather "This specification uses" and get rid of "throughout this document."
> Line 192 delete "Taken together,"
> Line 225 and 255 - repetitive. Reconsider with 165-168 - the same point seems to be made three times in three pages.
> Line 318 "the Product Description and the emixBase" -- why is one in XML token form and the other separate words?  Be consisent.  Suggest "the Product Description base type and the Emix Base type"
> 342-344 is clumsy. try "New efforts MAY specify additional...".  "...generate new Emix Base..." doesn't sound like English. (see also line 340 and all other uses of "Emix Base" -- which was "emixBase on line 318).  "transported on" seems strange given that this is not a message standard. 
> Check and reword each use of "Emix Base" and "emixBase" in the document.
> line 348 change "in v1.0" to "this specification"
> Line 376-379  "Emix Base" is clumsy, and line 376 provide seems like it should be "provides"
> Line 387 change "to each of them" to "to each". 
> ALL: The term "agreement" has (I think) changed to "transaction". Verify and make uniform changes.
> Section 3 line 302.  Resource is in the schemas, as is Power. Neither seems to be addressed in this section -- the Guide is incomplete.
> Line 438 Consider rewriting as "Neither the EMIX Constraints nor Reuqirments are tied to any particular kind of Product or Resource"  (not clear what was meant in wd22; and Resources haven't been defined yet.)
> Line 440 change "effect" to "affect"
> Line 439 section - should "resource" be capitalized?
> Line  449-450 rewrite "A given Resource MAY be offered to the market with different Requirements. The value of such offers MAY vary."
> Section 5 Line 423 - this appears to be critical to resources, but is not linked to those definitions which (I presume) are in later sections. I presume the connection is through a Product which may refer to one or more resources. Consider whether resource should be captialized in section 5.
> Line 497: "Table 4-2***" - what do the asterisks mean? It's not a reference, just text.
> Line 495 - "The EMIX Gluon" - where is this defined? There are clues in the text that it's in EmixBaseType or emixBase...and that's where the extensions happen. Make more clear in the text. The nature of the extension is not clear from the text or the schema - should add a note/footnote to clarify.
> GLOBAL CHANGE priceAbsolute --> price.
> 602 the section title suggests that this is an enumeration. Clarify. What's the relationship to the rest of section 9?

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