[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [ws-calendar] Use of WS-Calendar in Energy Interoperation
Intervals and gluons are related to each other by the related-to (EI uses an older version – I will update Ed’s work in EI soon). Relations are used to “launch sequences as subroutines” or to apply a price to a whole set of intervals (sequence) through a gluon and related-to. A single interval standing alone does not need one, but we do need that optionality in EI. In WS-Calendar, the attach is a null type that can contain some XML. In EI, we derive the base signal type from that null type, which means that to ws-calendar, the EI signals appear as legal attachments in any vobject. In EI, we put the signal types in intervals as attachments. In effect the x-wsCalendar-attach is merely the validation glue between the two. Of course, in the XML, the x-wscalendnar-attach controls artifact validation only. tc "He who fights with monsters should look to it that he himself does not become a monster, and if you stare long into an abyss, the abyss also stares into you." - Fredrich Nietzche
From: Girish Ghatikar [mailto:gghatikar@lbl.gov] Hi Toby, This looks great. Can you please remind me what xcal:related-to and xcal:x-wsCalendar-attach refer to? Thank you, -Rish On Fri, Jun 3, 2011 at 9:57 AM, Toby Considine <Toby.Considine@gmail.com> wrote: As promised, how ws-calendar “pseudo-schemas” appear as part of a larger schema in Energy Interoperation EIClasses.xsd <!-- 2.9 Interval --> <xs:element name="interval" type="eitc:IntervalType"/> <xs:complexType name="IntervalType"> <xs:annotation> <xs:documentation>Interval of Time</xs:documentation> <xs:appinfo>As of this draft, the WS-Calendar work-plan is to have a simplified profile of the Interval Component for transaction processing. If an when that is complete, this specification will refer to it directly instead fo to this type.</xs:appinfo> </xs:annotation> <xs:sequence> <xs:element ref="eitc:properties"/> <xs:element ref="eitc:components"/> </xs:sequence> </xs:complexType> <!-- 2.9.1 Interval Support - Properties--> <xs:element name="properties" type="eitc:ArrayofProperties"/> <xs:complexType name="ArrayofProperties"> <xs:sequence> <xs:element ref="xcal:uid" maxOccurs="1"/> <xs:element ref="xcal:related-to" minOccurs="0" maxOccurs="1"/> <xs:element ref="xcal:dtstart" minOccurs="0" maxOccurs="1"/> <xs:element ref="xcal:duration" minOccurs="0" maxOccurs="1"/> <xs:element ref="xcal:x-wsCalendar-attach" minOccurs="0" maxOccurs="1"/> </xs:sequence> </xs:complexType> <!-- 2.9.1 Interval Support - Components--> <xs:element name="components" type="eitc:ArrayofComponents"/> <xs:complexType name="ArrayofComponents"> <xs:sequence/> </xs:complexType> Notice that as of yet no definition of the Components in the Array… tc “The single biggest problem in communication is the illusion that it has taken place.”
|
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]