[OASIS Issue Tracker] Created: (EMIX-531) Warrants should useEmixBase not EmixProduct

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

Warrants should use EmixBase not EmixProduct
--------------------------------------------

                 Key: EMIX-531
                 URL: http://tools.oasis-open.org/issues/browse/EMIX-531
             Project: OASIS Energy Market Information Exchange (eMIX) TC
          Issue Type: Bug
         Environment: Toby Considine
            Reporter: Toby Considine
            Assignee: William Cox


Found this when trying to get PowerQualityWarrants right.

The emix:QualityWarrantType is, like most warrants a variety of a product. Recall the shorthand that a Product is a Product Description applied to a schedule. power:qualityMeasure is defined to fit in the role of the product description, i.e., to be applied to the schedule. (We warrant quality power throughout the day until evening, when its mostly wind power and we anticipate sags and flicker...) It is possible to create a schedule for quality, as it is for all other warrants. Quality measure is just the things we are using inside the schedule, which is already inherited.

Well, this is almost correct. An EMIXBase is the underlying object of the Description and the Schedule. A Product is the one that has sides, and transactive states and market contexts, etc. Tracing this change through reveled this same error in other warrants. They should all use the EMIXBase rather than the EMIX Product.

THese changes need to be made to the other warrant types as well. Note, that Product is derived from Base, so if someone *did* have a need to use product thre, it is still legal to do so.


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