[OASIS Issue Tracker] Commented: (EMIX-363) resource.xsd issues

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

    [ http://tools.oasis-open.org/issues/browse/EMIX-363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=25152#action_25152 ] 

Toby Considine commented on EMIX-363:
-------------------------------------

>> Constraints and Resources are both heavily tied to load or generation resource terminology and concepts and 
>> therefore confusing or misleading in their application to Transactive Energy that intentionally prohibits the concept
>> of a resource being tied to a TeMIX tender or transaction. 

Yet even a TEMIX prodiuct might be offered to the market as available during a window
Or requiring 10 minutes notice befoe a performance call
Or being available for no more than an hour at a time....

> resource.xsd issues
> -------------------
>
>                 Key: EMIX-363
>                 URL: http://tools.oasis-open.org/issues/browse/EMIX-363
>             Project: OASIS Energy Market Information Exchange (eMIX) TC
>          Issue Type: Sub-task
>          Components: schema
>    Affects Versions: wd22
>         Environment: William Cox
>            Reporter: William Cox
>            Assignee: Toby Considine
>             Fix For: wd23
>
>
> Resource.xsd:
> For the next two items, all resources are extensions of resource:PowerResponseType on line 156, so these comments apply to all resources.
> Cardinality of emix:constraints: since all elements of emix:ConstraintsType are 0..n, what is the cardinatlity of emix:constaints at the higher level in ResourceLoadReductionType?  Looking at the schema it is not at all obvious. Given the nillable discussions, and the empty tags from xcal, as written this may require empty tags. (it does seem that wherever the abstract baseConstraint is extended that minoccurs="0". I think an explanation in the guide to the schemas would make this less confusing on first read)
> Possible recursion in definition of (e.g.) emix:constraints. As shown on line 22 the definition of ResourceLoadReductionType contains emix:constraints, which in turn includes emix:constraints.  Is this a problem?
> Line 19: missing colon inside "resourceRegulationService" should be "resource:regulationService" (it's a top-level element)
> Line 65 "Regulation Product" comment - it's called a Service elsewhere. But isn't this a Regulation RESOURCE?
> Line 66 and 68 - why is this called a "regulation service"? This is an information model. In the spec line 708 this is called Regulation Products, and the section heading line 697 is "Ancillary Services Product Descriptions".  There may be no good way of addressing this, alas.

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