[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [energyinterop] WS-Calendar
|
Hi Dave, I do not know much about scheduling but I can tell you that
price cannot be just a number. There are certain minimum levels of metadata
associated with price that may need to be passed (i.e. range, valid period,
unit, etc.). As far as time, time is simply a normalized number counting
seconds from an epoch. We could use GMT, NTP, or UTC the differences between each
is simply the epoch. Time zone, day light saving, and other localized
parameters should be applied by the recipient device. With kind regards, ******************************** Michel
Kohanim, C.E.O Universal
Devices, Inc. (p)
818.631.0333 (f)
818.708.0755 http://www.universal-devices.com ******************************** From: Wilson, David C
(St. Paul) [mailto:DavidCWilson@trane.com] I read with
interest Toby’s recent post about WS-Calendar as well as his blog entry: http://www.newdaedalus.com/articles/2009/1/24/coordinating-time-and-energy.html I saw
references to WS-Calendar in the NIST notes as well. I’m hoping
Toby or others can elaborate on what such a specification bring over and above
the current data types available from XML Schema. I can easily
picture interval based pricing like the Texas pricing I reviewed with the TC: -Interval --StartTime
xs:dateTime --Interval
xs:duration --Price
xs:decimal What would a
WS-Calendar specification bring? Also, will that specification appropriately
deal with “naïve”
/ local time (a
time without a timezone)? In building protocols such as BACnet, schedules are
defined to start given local time with the responsibility of the device clock to be aware
of the current local time. Regards, Dave p.s.
I’ve observed a challenge with C#, it doesn’t seem to have a naïve time type and will
assume that a time without a timezone is local to the server. But if that time is
serialized and passed to another timezone, it will be unserialized with an adjustment
for timezone (i.e. if you set dateTime = 4 am on a server in Chicago, pass it to
a server in New York, it will unserialize as 5 am.) This detail probably
isn’t appropriate for this list, but it is an example of the complexities when
you use
times across systems. Enterprise
Solutions Portfolio Manager Trane
Commercial Systems Ingersoll
Rand Office:
+1.651.407.4168 Mobile:
+1.612.741.2759 Email:
davidcwilson@trane.com The information contained in this message is privileged and
intended only for the recipients named. If the reader is not a representative
of the intended recipient, any review, dissemination or copying of this message
or the information it contains is prohibited. If you have received this message
in error, please immediately notify the sender, and delete the original message
and attachments. |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]