[OASIS Issue Tracker] Commented: (ENERGYINTEROP-468) Add new signaltype

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

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

Toby Considine commented on ENERGYINTEROP-468:
----------------------------------------------

These comments summarize considerable off-line back and forth that resulted in two statements:

1)	There will never be a single signal that (relative)1.5, (relative)4.0,  (absolute)25, (relative)24.0. Accordingly, we are adding two enumerations to specify which price type is communicated in each signal.
2)	In an idealized world, market context would have all units, and they would be expressed as derivatives of emix:itemBaseType. There would be no need to express it during an individual event. If a VEN had "forgotten"  the units for the context, it could ask again, and it would contain the units. It is useful for certain interactions with certain [simple] devices to be able to express that again in the event. Therefore the event MAY include an optional itemBase derived unit expression. 

(A similar argument covers currency, FWIW).
Some difficulties. It is now possible for an event to express units different than that of the market context. While this should be illegal as an *application* rule, forcing conformance appears to be outside the scope of energyinterop.
One potential issue is that with this price change, while we are still semantically mappable to EMIX, we are no longer using the common price communication we defined therein—this may leave us open to some criticism there.
                                                            <xs:element name="factoredInfo" type="emix:ProductDescriptionType" minOccurs="0" maxOccurs="1"/>
                                                            <xs:element ref="emix:itemBase" minOccurs="0" maxOccurs="1">
                                                                        <xs:annotation>
                                                                                    <xs:documentation>This is the units of the signal. </xs:documentation>
                                                                        </xs:annotation>
                                                            </xs:element>

I have also added itemBase (optional) to the EventSignalInfoType. This was previously factoed into a derivative of productDescription (optional) which is already minimally expressed in itemBase. We, as a committee, should probably pick one. Now we have both, and they are each optional.

See Artifact at http://www.oasis-open.org/apps/org/workgroup/energyinterop/download.php/43501/energyinterop-1-0-schema-wd28-wip1.zip


> Add new signal type
> -------------------
>
>                 Key: ENERGYINTEROP-468
>                 URL: http://tools.oasis-open.org/issues/browse/ENERGYINTEROP-468
>             Project: OASIS Energy Interoperation TC
>          Issue Type: Improvement
>          Components: model
>    Affects Versions: wd24
>         Environment: ed koch
>            Reporter: Ed Koch 
>            Assignee: Ed Koch 
>             Fix For: wd28
>
>
> One of the issues that we have been dealing with in the application of OpenADR 1.0 to ancillary services is the use of the signalAmount type.  Currently it is simply a specific amount of usage. The problem is that it can be applied in two different contexts.  In one case it can represents a change in the amount of usage and in the second use case it may represent an actual target amount of usage.  I will post a JIRA about this.

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