[OASIS Issue Tracker] Commented: (EMIX-427) Chapter 3 Issues

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

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

Toby Considine commented on EMIX-427:
-------------------------------------

303-304	ISSUE: is the "exchangeable information model" the same as "Top level model" of line 306? 
>>No, the abstract items of the top level model are abstract, i.e., non-exchangeable by standard (normative) XSD usage

303-307	ISSUE: this text would be well-served with a nice diagram! 
>>Get your crayons out

303-307	ISSUE: The relationship between abstract types and [Product Descriptions, Schedules, Top level models] is unclear 
>>Hence the rest of the section.

305	ISSUE: "low-level items" is undefined 
>>nor is it capitalized

309-312	ISSUE: is it "Product Description Type" or "Product Description"? The language is ambiguous. 
>>went with Description for this introductory paragraph

314	ISSUE: Heading of column 1 in Table 3-3 is "Type". Definition of Schedule states: "The Schedule name a collection, but is not itself a type." Why is it in the table of "Types"? 
>>spite - actually it fits nowhere else, and a separate table for virtual types would confuse more than enlighten. Feel free to suggest an alternate title.

315-316	ISSUE: does the use of "EMIX" here mean "EMIX Base"? "EMIX Interface"? The entire standard? The language is ambiguous. 
>>Added the word specification to the first line of the paragraph.Not sure how a Specification would be conforming to a single type, though.

319-329	ISSUE: This section ironically does not define "Price Base". 
>>Now it does

320-326	ISSUE: "Price Base" is stated to be "an element in many expressions of (sic) price." Table 3-4 states it contains "Elements derived from Price Base", one of which is "Price". This is unclear. 
It is the difference between lower case and upper case, and non-normative and normative language.
>>I have no idea, nor does the specification, nor does the toaster, probably. This accurately reflects the work in the committee. This is why it is lower case. EMIX cannot define markets where there may or may not be a known reference price, nor how those markets make such known.

324	ISSUE: Price Multiplier states that it is "applied to a reference price". What is the "reference price"? Where is it defined? 
>> ibid

324	ISSUE: Price Relative states taht it is "added to a reference price to the actual price." What is the "reference price"? Where is it defined? 
>>Ibid - but added the word "compute"

324	ISSUE: which element, Price Multiplier or Price Relative, is applied first to the "Reference Price" to compose the actual price? One is a multiplication and one is an addition and this could be expressed as Price=(RefPrice+PriceRel)(PriceMult) or Price=(PriceMult*RefPrice)+PriceRel 
>> As members of a substitution group, only one is present, using normal XML usage. If a conforming specification wishes to define multiple occurrences of the price base, they could, of course, define the rules as well.


325	ISSUE: states that "Price" is a type but "Price" is defined in Table 3-4 as an "element" 
>>changed to lower case (non-normative use)

341-346	ISSUE: Why is "The Item Base" both here and in Section 7.2? Can it appear in only one location? Can this instance of "The Item Base" be moved to under 3.1.1? 
>> The Item Base is defined here and extended (for power) in section 7  Language was added in Section 7.2 to make this more clear. Also brought the language about SI Units back to the original definition.


349	ISSUE: if the product from two different providers has "indistinguishable characteristics" how would one value them differently? Recommend replacing "indistingushable" with "extrinsic". 
>>done

> Chapter 3 Issues
> ----------------
>
>                 Key: EMIX-427
>                 URL: http://tools.oasis-open.org/issues/browse/EMIX-427
>             Project: OASIS Energy Market Information Exchange (eMIX) TC
>          Issue Type: Bug
>          Components: spec
>    Affects Versions: wd28
>            Reporter: Aaron Snyder 
>            Assignee: William Cox
>             Fix For: wd29
>
>
> 303-304	ISSUE: is the "exchangeable information model" the same as "Top level model" of line 306?
> 303-307	ISSUE: this text would be well-served with a nice diagram!
> 303-307	ISSUE: The relationship between abstract types and [Product Descriptions, Schedules, Top level models] is unclear
> 305	ISSUE: "low-level items" is undefined
> 309-312	ISSUE: is it "Product Description Type" or "Product Description"? The language is ambiguous.
> 314	ISSUE: Heading of column 1 in Table 3-3 is "Type". Definition of Schedule states: "The Schedule name a collection, but is not itself a type." Why is it in the table of "Types"?
> 315-316	ISSUE: does the use of "EMIX" here mean "EMIX Base"? "EMIX Interface"? The entire standard? The language is ambiguous.
> 319-329	ISSUE: This section ironically does not define "Price Base".
> 320-326	ISSUE: "Price Base" is stated to be "an element in many expressions of (sic) price." Table 3-4 states it contains "Elements derived from Price Base", one of which is "Price". This is unclear.
> 324	ISSUE: Price Multiplier states that it is "applied to a reference price". What is the "reference price"? Where is it defined?
> 324	ISSUE: Price Relative states taht it is "added to a reference price to the actual price." What is the "reference price"? Where is it defined?
> 324	ISSUE: which element, Price Multiplier or Price Relative, is applied first to the "Reference Price" to compose the actual price? One is a multiplication and one is an addition and this could be expressed as Price=(RefPrice+PriceRel)(PriceMult) or Price=(PriceMult*RefPrice)+PriceRel
> 325	ISSUE: states that "Price" is a type but "Price" is defined in Table 3-4 as an "element"
> 341-346	ISSUE: Why is "The Item Base" both here and in Section 7.2? Can it appear in only one location? Can this instance of  "The Item Base" be moved to under 3.1.1?
> 349	ISSUE: if the product from two different providers has "indistinguishable characteristics" how would one value them differently? Recommend replacing "indistingushable" with "extrinsic".

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