OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

energyinterop message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: RE: EIEvent Schedules


Very similar to what I am trying to profile in ws-calendar. That is a very useful confirmation.

 

tc


"It is the theory that decides what can be observed."   - Albert Einstein


Toby Considine

Chair, OASIS oBIX Technical Committee
U.S. National Inst. of Standards and Tech. Smart Grid Architecture Committee

Facilities Technology Office
University of North Carolina
Chapel Hill, NC

  

Email: Toby.Considine@ unc.edu
Phone: (919)962-9073

http://www.oasis-open.org

blog: www.NewDaedalus.com

 

 

From: Edward Koch [mailto:ed@akuacom.com]
Sent: Sunday, May 01, 2011 2:52 PM
To: energyinterop@lists.oasis-open.org
Subject: [energyinterop] EIEvent Schedules

 

All,

 

I've been working on trying to craft a solution for our use of ws-calendar to get us the maximum benefit of schema validation.  What I have come up with so far is in the enclosed schema files that represents my proposal for how to represent an EIEvent schedule that uses and is compatiible with WS-alendar.  Note that I have generated some sample XML with the enclosed schema and if you take the XML file and perform a little namespace jujitsu on it, it will validate directly against WS-calendar.

 

Note that I put the new types in one file (EIEventIntervalType.xsd) and the extended elements in their own file (EIEventIntervals.xsd). By doing this I am able to create another file that contains the same elements, but has no extensions to ws-calendar (see EIEventIntervals-x.xsd) and use that to test that whatever I am doing is still compatible with ws-calendar. This is purely a validation exercise and in essence I create an XML example with my custom extensions in EIEventInterval.xsd and then modify that XML to change its namespace and point to the EIEventInterval-x.xsd instead. Since EIEventInterval-x.xsd contains no custom extensions and is based purely on ws-alendar that allows me to verify that any XML I generate with my custom extensions in EIEventIntervalTypes.xsd are not only compatilbe with ws-calendar in principle, but will in fact validate agasint the ws-calendar schemas by only changing the namespaces in the XML file.

 

Toby - I don't know how this approach maps to some of the stuff they are doing with GML, but it might be similar.

Take a look at the enclosed jpeg which shows my schema extensions/restrcitons to ws-calendar for a EIEvent Schedule.

 

Assuming that people think this is a reasonalbe approach, my next step is to perform a similar exercise with the EIEventInfo schedules and link them to theoverall EIEvent scheudle.

 

 

-ed koch



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]