[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [emix] Late Breaking Changes
|
Congrats on the WS-Calendar progress. I was looking forward to hearing your explanation
of WS-Calendar at the meeting Thursday, but unfortunately I have a conflicting
meeting scheduled by a client. Also.
I have a separate note on the product structure idea that I posted earlier
that I will also send before the meeting. With respect to inheritance I do not think it
should be for only price and quantity.
Rather, he designer of a product should be able to make any attribute of a product such
as price, strike price, option premium, quantity, loss factor, max generator capacity etc. either be a
constant over the scheduled sequence or partitions. Perhaps we need a notation to specify which
and how a an attribute of a product may vary by interval or partitions or
sequences of intervals. Ed Edward G. Cazalet, Ph.D. 101 First Street, Suite 552 Los Altos, CA 94022 650-949-5274 cell: 408-621-2772 ed@cazalet.com www.cazalet.com From: Toby Considine [mailto:tobyconsidine@gmail.com] On
Behalf Of Toby Considine I’m not going to send you a new EMIX tonight I have been trying to tighten up some confusing references
(while thinking in my mind “Who wrote this!?”) to WS-Calendar If we have time, we can discuss: Section 2.4, in which the use of WS-Calendar is
introduced: Time and Schedules as part of EMIX
Time is an important component of
energy product transactions. A product produced in one interval of time may
have to be stored or may not be able to be stored for a later interval of time.
Thus the same product in different intervals of time may have difference prices.
EMIX uses WS-Calendar to to apply prices and products to time intervals. WS-Calendar defines a mechanism to apply a schedule to a
sequence of time intervals. WS-Calendar further defines how to use inheritance
to apply a single information model to each interval in the sequence, allowing
elements of that information model to be over ridden within any given interval.
WS-Calendar. WS-Calendar also defines a schedule entry point, defining how
specific performance can be contracted and scheduled. This document assumes that the reader has a clear
understanding of WS-Calendar and its interfaces. The non-normative appendices
of the WS-Calendar specification are a good place to start. Section 4.1, in which inheritance is mentioned Attribute Inheritance in EMIX
EMIX uses WS-Calendar to associate a Product with a Sequence
of Intervals. The EMIX Product acts as a Calendar Gluon. If needed, Calendar
Gluons / Products can be recursive, enabling attribute inheritance through a
chain of Calendar Gluons. In EMIX, this pattern defines how an external
contract can establish price and intervals atop an invariant EMIX object. For a fuller discussion, see [WS-Calendar] Question:
Should we distinguish between an Interval that has a Price, an Interval that
has a Quantity, and one that has Both? The first two are types of offers, the
last is a contract or records the sale. We need some wider discussion of Inheritance Also, I have moved the discourse on electrical variables
to Appendix B. tc “It is difficult to get a man to understand something,
when his salary depends upon his not understanding it” -- Upton Sinclair.
|
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]