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-608) Glossary Definitions of Resources are muddled and inconsistent with EMIX.


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

Edward Cazalet  commented on ENERGYINTEROP-608:
-----------------------------------------------

If a Resource (i.e. a generator ) is a "Thing" is a "Demand Response Resource" (a common industry term) a "Thing" or a "Virtual Thing" ?

> Glossary Definitions of Resources are muddled and inconsistent with EMIX.
> -------------------------------------------------------------------------
>
>                 Key: ENERGYINTEROP-608
>                 URL: http://tools.oasis-open.org/issues/browse/ENERGYINTEROP-608
>             Project: OASIS Energy Interoperation TC
>          Issue Type: Bug
>          Components: spec
>    Affects Versions: wd33
>         Environment: Ed Cazalet
>            Reporter: Edward Cazalet 
>            Assignee: Toby Considine
>             Fix For: wd34
>
>
> 2123 Resource (as used in Energy Interoperation): a Resource is a logical entity that is dispatchable. The 
> 2124 Resource is solely responsible for its own response. A resource description specifies the 
> 2125 performance envelope for a Resource. If a Resource can participate in multiple markets, it may 
> 2126 have multiple desriptions. 
> 2127 Resource (as defined in EMIX): A Resource is something that can describe its capabilities in a Tender 
> 2128 into a market. How those Capabilities vary over time is defined by application of the Capability 
> 2129 Description to a WS-Calendar Sequence. See [EMIX].
> EMIX Resources are both dispatchable and can be tenders as capabilities.  There seems to be no need for a distinction between an EI Resource and an EMIX Resource.

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