[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=25932#action_25932 ] 

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

Sorry for the snark. A lot of unactionable comments this weekend - but notably very few from you, as yours were directed and actiable across the board. I guess when you gave me one inactionable, I got a "not you, too" reaction...I apologize

So, here is the Challenge:

As you say, it is not itself a type, it is something that I want to be able to use a shorthand name for. (In this case, it is much like the Envelope)

Creating one table for each thingummie, with one line each confuses more than enlightens.

Putting it in a table filled mostly with types confuses (as you observed) unless it is well titled. I do beleive it goes in a list of "somewhat essential high level thingummies that need to be named because w/o names this spec will be more confusing". Is it a virtual type? FOr me, Type is tied closely to spending most days deep inside Schemas right now, and I may be leaning more on the XML Type defitnion than most.

But I think "SEHLLTTNTBNBWNTSWBMC" is flat out.

A suggestion for a helpful and illumuinating title would be much apreciated.

> 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