[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=25928#action_25928 ] 

Aaron Snyder  commented on EMIX-427:
------------------------------------

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. 

>>>if this is the case, should Price Relative not then read: "A Price Relative is added to a reference price to produce the actual price."? This would parallel the Price Multiplier defnition. It still leaves the fact that only one or the other shall be present. Where is that discussed/defined? One expects every reader to discern that?

303-307 ISSUE: The relationship between abstract types and [Product Descriptions, Schedules, Top level models] is unclear 
>>Hence the rest of the section.
>>>thanks for the snark. however, shouldn't some relationship be a bit more clear between "abstract types", "core types" and "concrete types" the first time one stumbles across them in the specification? also, the first occurrence of "low-level items" without a definition or context. Same for "top level models". This doesn't appear to serve the community well to hit the five terms cold without relationship, definition or context.

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. 
>>>thanks for the snark. i don't understand calling this "spite". putting something in a list of "Types" but then definining it as not a "Type" seems incredulous for a standard.

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