There has been a lot of discussion about how we got to where we are now in Schemas.
WIP1 –
Initial schemas for WD23, from Cox
WIP2 –
Took Bill's schemas from EA, made a pass at NIEM compliance, abstracted many common data types, used standard naming conventions, added some questions to text.
WIP3 –
EI Schemas, modified to take advantage of EMIXBusinesSchedule and EMIX Constraints.
Includes current working drafts of EMIX,WS-Calendar for inclusion.
EventInfo not (deliberately) touched except to make valid with current referenced schemas. Ed Koch will deliver actual EIEventInto going forward
WIP4
Updated to incorporate Ed Kochs changes (see below) and then re-factored them to use EMIX
Created the EventBaselineType and the eventBaseline element that references it. Moved the following elements into it:
• energyBaselineTimestamp
• energyBaselineValue
Created the EventPerformanceType and the performance element that references it. Move the following elements to it:
• responseValue
• baseline
• reportingInterval
• performanceComment
Created the EventDescriptorType and the eventDescriptor element that references it. Moved the following elements into it:
• eventID
• eventStatus
• modificationNumber
• modificationDateTime – changed cardinality to 1..1
• modificationReason
• program
• operatingDay
• testEvent
• vtnComment – changed cardinality to 0..1
Created the ResourceTargetType and the resourceTarget element that references it. Moved the following elements into it:
• location – Changed cardinality to 0..1
• groupID - NEW
Refactored EventInfoType. Created two main subclass types - EventDispatchType and EventPriceType with eventDispatch and eventPrice elements that reference each.
Question: Need to figure out how to profile emix so that there can my multiple price instances.
Issue: May want to have the price and dispatch types share the same schedule profile.
WIP5
Verified consistent with WD22 EMIX schemas, but for the most part, reorganized EiClasses. Attempted to create an order for the types in the schema that makes it easier for the reader. (Clearly the computer doesn't care).
(Bartell / Gray / Koch produced a draft reply to WIP5)
WIP6 (last night)
Revised schemas for WD23
- Now uses xcal structures throughout
- Refactored for extensible price communications
- Probably still has redundant and unused elements
- Program morphed into Market Context
- Program calls are still something else
- Added Signal / Signal Name / Signal Type as base "Event" calls
- Incorporated mosh-pit of schema ideas from Bartell / Gray / Koch / Cox
- Created "profiled" intervals until WS-Calendar gets profiles
- All distribution elements can now be shipped in schedules
- EiPayloads is muddled, needs someone else to review Programs particularly
WIP7 (corrections to WIP6 requested in today’s meeting)
As in Revised schemas for WD23 wip6
- Now uses xcal structures throughout
- Refactored for extensible price communications
- Probably still has redundant and unused elements
- Program morphed into Market Context
- Program calls are still something else
- Added Signal / Signal Name / Signal Type as base "Event" calls
- Incorporated mosh-pit of schema ideas from Bartell / Gray / Koch / Cox
- Created "profiled" intervals until WS-Calendar gets profiles
- All distribution elements can now be shipped in schedules
- EiPayloads is muddled, needs someone else to review Programs particularly
(new stuff below)
- Modified EiEventBase items to incorporate, rather than be derived from vacalendar.
Now with PR version of EMIX included in a subdirectory. WS-Calendar is referenced from the PR02 location on the web.
WIP 8 is whatever comes next
WD23 of the spec, and the latest Schema, will both be WD23.
tc
“The single biggest problem in communication is the illusion that it has taken place.”
– George Bernard Shaw.
Toby Considine
TC9, Inc TC Chair: oBIX & WS-Calendar TC Editor: EMIX, EnergyInterop U.S. National Inst. of Standards and Tech. Smart Grid Architecture Committee
| | Email: Toby.Considine@gmail.com
Phone: (919)619-2104 http://www.tcnine.com/
blog: www.NewDaedalus.com |