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

 


Help: OASIS Mailing Lists Help | MarkMail Help

energyinterop message

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


Subject: [OASIS Issue Tracker] Commented: (ENERGYINTEROP-472) Re-factoringand Normalization Collector



    [ http://tools.oasis-open.org/issues/browse/ENERGYINTEROP-472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=26618#action_26618 ] 

Ed Koch  commented on ENERGYINTEROP-472:
----------------------------------------

Toby. See my respones below:


1) I notice that this revision adds the OptType to the eventCreatedResponse. The optType is optIn or optOut. 

What is the meaning of OptType in the eventCreatedResponse? 

> See item 423.  This change was for that issue. I added a comment to 423 for this change.


2) In the EventType, the eventDescriptor is changed from a reference to an in-line definition. Is this change something we should preserve?

> If this was something I did to the schema then it was unintentional.
 

3) I would like to prose that the new SignalUnits be an emix:item. The reason is because there are some markets that are no 1MW markets, but 10MW (or even 100 MW) markets. This should be a simple change. The Emix:Item consists of a Number/Units/Scale 


> The reason I made it a string was because only a couple of the signal types require units and those that do only require currency in the case of price and power units in the case fo the setppoints.  When I dove down into how we current define units in other parts of the spec I found that in the power.xsd schema the units attribute was simply a string amd when I dove down into how we represent currency in EMIX it was also only a string that uses the well defined ISO currency designators.  Thus I used a mechanism that is consistent with the way it is currently being done in EMIX and other parts of the EI spec. If you want to make it an EMIX artifact I won't object as long as we don't have too much baggage that goes along with that becasue that would defeat the purpose of the refactoring. 

> Re-factoring and Normalization Collector
> ----------------------------------------
>
>                 Key: ENERGYINTEROP-472
>                 URL: http://tools.oasis-open.org/issues/browse/ENERGYINTEROP-472
>             Project: OASIS Energy Interoperation TC
>          Issue Type: Improvement
>            Reporter: Toby Considine
>            Assignee: William Cox
>
> Now that the Information is stable, need to review how factoring and normalization can be applied. Common thread in many issues.

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