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

 


Help: OASIS Mailing Lists Help | MarkMail Help

ws-calendar message

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


Subject: RE: [ws-calendar] Web Services Calendar (WS-Calendar) TC - 03December 2010


I don't think I can make it this week. Too tired, too much smart grid, too much...

Jira response can be classified into 4 groups.

1) Grammatical, spelling, etc. We can just do these.

2) Off the wall, "thank you for submitting whatever it was", closte it and go

3) Minor technical issues worth of discussion, perhaps soluable in minutes

4) Tough, hard questions

The Chair would find it very useful if we categorized the comments as above. We can then clear up (1) and (2) this weekend and get out a new WD. If the committee in my absence wants to clear up class (3), hooray! (4), well....

THe CalCOnnect.IETF group has recommended that we just make our wn icalendar.xsd canonical. I can only agree. Mike has significant updates to Icalnedar which we should look at and probably adop. Mike, can you submit?

I have suggestions (which I commented, vaguely) for an updated XSD based on my experience w/ emix. I attach and contribute it for your consideration. It, of course, would have to adjust to the new iCalendar.xsd

Thanks, and good night

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



-----Original Message-----
From: Gershon Janssen [mailto:gershon@qroot.com] 
Sent: Thursday, December 02, 2010 7:05 PM
To: ws-calendar@lists.oasis-open.org
Subject: [ws-calendar] Web Services Calendar (WS-Calendar) TC - 03 December 2010

L.S.,

Please find below the proposed agenda for this week's meeting.

There were doubts from members of them being able to attend this week due to the Grid-Interop conference. I've not received any messages yet, but please drop me a short note if you are / are not able to join. Based on that we can decide to cancel this week's meeting.

---

Web Services Calendar (WS-Calendar) TC
03 December 2010, 12:00pm ET, 06:00pm CET

Call-In Information: 

Australia: +61 (0) 7 3123 6030
Austria: +43 (0) 7 20881407
Belgium: +32 (0) 28 08 4297
Canada: +1-778-785-0724
Denmark: +45 69 91 88 70
Finland: +358 942 599 697
France: +33 (0) 182 880 463
Germany: +49 (0) 898 7806 6464
Ireland: +353 (0) 14 845 983
Italy: +39 0553989569
Netherlands: +31 (0) 208 080 385
New Zealand: +64 (0) 4 974 7216
Norway: +47 21 04 29 13
Spain: +34 955329911
Sweden: +46 (0) 313 613 559
Switzerland: +41 (0) 225 3314 55
United Kingdom: +44 (0) 203 318 4725
United States: +1-626-521-0010

Access Code: 114-622-898

No need for an audio PIN

Thanks to LONMARK for the conference call support.

Chat: http://webconf.soaphub.org/conf/room/ws-calendar

Proposed Agenda

0. Roll call, Agenda review

1. Minutes Approval

- 17 September 2010: 
http://www.oasis-open.org/apps/org/workgroup/ws-calendar/download.php/39484/Minutes_WS-Calendar-TC_20100917_Draft.txt

- 19 November 2010:
http://www.oasis-open.org/apps/org/workgroup/ws-calendar/download.php/40476/Minutes_WS-Calendar-TC_20101119_Draft.txt

2. FYI / announcements from Chair, Secretary, Liaison 

3. Discussion

- Comments received from Public Review

- JIRA issues

For an overview of JIRA issue, please refer to:
http://tools.oasis-open.org/issues/browse/WSCALENDAR

4. Any Other Business?

5. Adjourn

---

Regards,

Gershon Janssen


---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that generates this mail.  Follow this link to all your TCs in OASIS at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php 

<?xml version="1.0" encoding="UTF-8"?>
<!-- edited with XMLSpy v2010 rel. 3 sp1 (x64) (http://www.altova.com) by Toby Considine (TC9) -->
<!-- updated 2010-10-30 to reduce incompatibilites, (use x-wscalendar properly) use extensions, not overload attach -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"; xmlns:xcal="urn:ietf:params:xml:ns:icalendar-2.0" xmlns:wscal="http://docs.oasis-open.org/ns/ws-calendar"; targetNamespace="http://docs.oasis-open.org/ns/ws-calendar"; elementFormDefault="qualified">
	<xs:import namespace="urn:ietf:params:xml:ns:icalendar-2.0" schemaLocation="iCalendar.xsd"/>
	<!-- 1 the core elements  -->
	<xs:element name="ws-calendar">
		<xs:complexType>
			<xs:sequence>
				<xs:group ref="xcal:type-calprops"/>
				<xs:element ref="wscal:sequence"/>
			</xs:sequence>
		</xs:complexType>
	</xs:element>
	<xs:element name="sequence">
		<xs:annotation>
			<xs:documentation>A set of temporally related intervals and the gluons that influence their artifact expansion. Artifact epression is shared between the intervals and gluons in a sequence. A gluon is related to an interval or to another gluon by a parent relationship. A relationship to a single interval in a sequence influences artifact expansion in all intervals in the sequuence</xs:documentation>
		</xs:annotation>
		<xs:complexType>
			<xs:choice minOccurs="0" maxOccurs="unbounded">
				<xs:element ref="wscal:interval" minOccurs="1"/>
				<xs:element ref="wscal:x-calendargluon" minOccurs="0"/>
			</xs:choice>
		</xs:complexType>
	</xs:element>
	<!-- 1.1 Interval - just a profiled vtodo  -->
	<xs:element name="interval" type="wscal:type-intervalProperties"/>
	<xs:complexType name="type-intervalProperties">
		<xs:annotation>
			<xs:documentation>An extended vtodo object that included an artifact (for extension in other specifications), performance, and the temporal relation.</xs:documentation>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="xcal:type-todoprop">
				<xs:sequence minOccurs="0" maxOccurs="1">
					<xs:element name="x-wscalendartype" type="wscal:type-wscalendarinterval" default="Interval" minOccurs="1"/>
					<xs:element name="x-wscalendarArtifact" type="wscal:type-artifact" minOccurs="1"/>
					<xs:element name="x-wscalendarUri" type="xs:string"/>
					<xs:element name="x-wscalendarPerformance" type="wscal:type-performance" />
					<xs:element name="x-wscalendarRelation" type="wscal:type-temporalrelation"/>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!-- 1.2 Gluon  -->
	<xs:element name="x-calendargluon" type="wscal:type-gluonproperties"/>
	<xs:annotation>
		<xs:documentation>Gluons are not in the calendar, as are intervals, but influence artifact expansion within intervals through their own artifacts. A gluon is related to an interval or to another gluon by a parent relationship. A concrete date and time in a gluon schedules the descendant interval.</xs:documentation>
	</xs:annotation>
	<xs:complexType name="type-gluonproperties">
		<xs:sequence>
			<xs:element name="properties">
				<xs:complexType>
				<xs:sequence minOccurs="0" maxOccurs="1">
						<xs:element name="x-wscalendartype" type="wscal:type-wscalendargluon" default="CalendarGluon"/>
						<xs:element ref="xcal:uid" minOccurs="1"/>
						<xs:element ref="xcal:related-to" minOccurs="1"/>
						<xs:element ref="xcal:dtstamp" minOccurs="1"/>
						<xs:element ref="xcal:description"/>
						<xs:element ref="xcal:last-modified"/>
						<xs:element ref="xcal:summary"/>
						<xs:element ref="xcal:dtstart"/>
						<xs:group ref="xcal:property-duration"/>
						<xs:element name="x-wscalendarArtifact" type="wscal:type-artifact" minOccurs="1"/>
						<xs:element name="x-wscalendarUri" type="xs:string"/>
						<xs:element name="x-wscalendarPerformance" type="wscal:type-performance"/>
						<xs:element name="x-wscalendarRelation" type="wscal:type-temporalrelation"/>
						<xs:element ref="xcal:comment"/>
				</xs:sequence>
				</xs:complexType>
			</xs:element>
		</xs:sequence>
	</xs:complexType>
	<!-- 2.1 hack to force single value Gluon  -->
	<xs:simpleType name="type-wscalendargluon">
		<xs:restriction base="xs:string">
			<xs:enumeration value="CalendarGluon"/>
		</xs:restriction>
	</xs:simpleType>
	<!-- 2.1 hack to force single value Interval  -->
	<xs:simpleType name="type-wscalendarinterval">
		<xs:restriction base="xs:string">
			<xs:enumeration value="Interval"/>
		</xs:restriction>
	</xs:simpleType>
	<!-- 3 the core elements  -->
	<!-- 3.1 temporal relation types  -->
	<xs:simpleType name="type-temporalrelationshiptype">
		<xs:restriction base="xs:string">
			<xs:enumeration value="finishtostart"/>
			<xs:enumeration value="finishtofinish"/>
			<xs:enumeration value="starttostart"/>
			<xs:enumeration value="starttofinish"/>
		</xs:restriction>
	</xs:simpleType>
	<!-- 3.2 temporal relations  -->
	<xs:complexType name="type-relatedto">
		<xs:choice>
			<xs:element name="uid" type="xs:string"/>
			<xs:element name="reference" type="xs:string"/>
		</xs:choice>
	</xs:complexType>
	<!-- 3.3 temporal relation types  -->
	<xs:complexType name="type-temporalrelation">
		<xs:sequence maxOccurs="1">
			<xs:element name="temporalrelationshiptype" type="wscal:type-temporalrelationshiptype" />
			<xs:element name="relatedto" type="wscal:type-relatedto"/>
			<xs:element name="gap" minOccurs="0">
				<xs:complexType>
					<xs:group ref="xcal:property-duration"/>
				</xs:complexType>
			</xs:element>
		</xs:sequence>
	</xs:complexType>
	<!-- 4.0 Attachments  -->
	<!-- 4.1 Performance  -->
	<xs:complexType name="type-performance">
		<xs:annotation>
			<xs:documentation> standard typing of performance aganist schedule</xs:documentation>
		</xs:annotation>
		<xs:sequence>
			<xs:element name="properties">
				<xs:complexType>
					<xs:choice minOccurs="0" maxOccurs="unbounded">
						<xs:element name="startbeforetolerance">
							<xs:complexType>
								<xs:group ref="xcal:property-duration"/>
							</xs:complexType>
						</xs:element>
						<xs:element name="startaftertolerance">
							<xs:complexType>
								<xs:group ref="xcal:property-duration"/>
							</xs:complexType>
						</xs:element>
						<xs:element name="endtbeforetolerance">
							<xs:complexType>
								<xs:group ref="xcal:property-duration"/>
							</xs:complexType>
						</xs:element>
						<xs:element name="endaftertolerance">
							<xs:complexType>
								<xs:group ref="xcal:property-duration"/>
							</xs:complexType>
						</xs:element>
						<xs:element name="durationlongtolerance">
							<xs:complexType>
								<xs:group ref="xcal:property-duration"/>
							</xs:complexType>
						</xs:element>
						<xs:element name="durationshorttolerance">
							<xs:complexType>
								<xs:group ref="xcal:property-duration"/>
							</xs:complexType>
						</xs:element>
						<xs:element name="granularity">
							<xs:complexType>
								<xs:group ref="xcal:property-duration" id="granularity"/>
							</xs:complexType>
						</xs:element>
					</xs:choice>
				</xs:complexType>
			</xs:element>
		</xs:sequence>
	</xs:complexType>
	<!-- 4.1 Artifact  -->
	<xs:complexType name="type-artifact">
		<xs:annotation>
			<xs:documentation>The artifact is here for use in extending by other specifications, to to allow attributes from other namespaces to be added to ws-calendar-based schemas.</xs:documentation>
		</xs:annotation>
	</xs:complexType>
</xs:schema>


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