OASIS Mailing List Archives
View the OASIS mailing list archive below
or browse/search using
MarkMail
.
This list only
All OASIS lists
Help:
OASIS Mailing Lists Help
|
MarkMail Help
ws-calendar
94 messages in this archive
(listed by date, most recent first)
|
Thread Index
|
List Home
[OASIS Issue Tracker] Created: (WSCALENDAR-200) Line 1471 -Security Standards should be included in the Services design standards.
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 30 Nov 2010 23:45:23 -0000
[OASIS Issue Tracker] Created: (WSCALENDAR-199) All - Should thexml file scripts be limited to a certain number of characters such that thefile could be sent via SMS text messaging or possibly via the radio dataservice (RDS) broadcast service.
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 30 Nov 2010 23:43:52 -0000
=?UTF-8?Q?[OASIS_Issue_Tracker]_Created:_(WS?==?UTF-8?Q?CALENDAR-198)_All_-_Given_the_diffe?==?UTF-8?Q?rent_context_with_which_a_timing_me?==?UTF-8?Q?chanism_can_be_used,_for_which_cont?==?UTF-8?Q?exts_does_this_proposed_standard_a?==?UTF-8?Q?pply=3F=C2=A0_E.g._dispatch,_settlements,_?==?UTF-8?Q?operations_characteristics,_schedul?==?UTF-8?Q?ing_tags,_bilateral_schedules...=C2=A0__?=
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 30 Nov 2010 23:43:43 -0000
[OASIS Issue Tracker] Created: (WSCALENDAR-197) All - ALL fieldsshould be distinctly listed as mandatory or optional. Some are specificallynoted and some are not.
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 30 Nov 2010 23:43:34 -0000
[OASIS Issue Tracker] Created: (WSCALENDAR-196) All - Examples usedin the document are not relevant to subject (class schedules) whichincreases risk of overlooking relevant issues that are involved with powerand energy timing.
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 30 Nov 2010 23:43:24 -0000
[OASIS Issue Tracker] Created: (WSCALENDAR-195) Line 1426 - Doesthis mean that derived standards like EMIX and EnergyInterop will also beRestful?
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 30 Nov 2010 23:39:32 -0000
[OASIS Issue Tracker] Created: (WSCALENDAR-194) Line 1440 - Thissection specifies the use of HTTP RESTfull services, and does not providelanguage to indicate that there may be any other way to implement thisstandard.
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 30 Nov 2010 23:39:23 -0000
[OASIS Issue Tracker] Created: (WSCALENDAR-193) Line 692 - Whilephysics is an interesting subject, this is not a PBS show and talking aboutgluons and quarks sounds neat, but is a distraction. If the term gluonneeds to stay fine, but there might be better terms.
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 30 Nov 2010 23:37:38 -0000
[OASIS Issue Tracker] Created: (WSCALENDAR-192) Line 38 - Noproblem with WS-Calendar adopting semantics and vocabulary from iCalendar,but it sounds like the standard will only use iCalendar in applicable webservice contracts.
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 30 Nov 2010 23:37:28 -0000
[OASIS Issue Tracker] Created: (WSCALENDAR-191) All - Our concernis more toward the security that I am not sure if it will be animplementation concern from any vendor or development side or not.
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 30 Nov 2010 23:35:24 -0000
[OASIS Issue Tracker] Created: (WSCALENDAR-190) Line 2534 - Couldthis document include WS applied to business cases applicable to RTO eventsscheduling and notifications ?
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 30 Nov 2010 23:29:32 -0000
[OASIS Issue Tracker] Created: (WSCALENDAR-189) Line 1474 - Theprotocol does not provide any explicit provisioning operations. Would thisdocument comply with existing OASIS Provisioning Technical Committee.
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 30 Nov 2010 23:29:23 -0000
[OASIS Issue Tracker] Created: (WSCALENDAR-188) Line 1471 - Whenwill ACL be defined, where enforced ? CIP Standards reference needed.
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 30 Nov 2010 23:27:32 -0000
[OASIS Issue Tracker] Created: (WSCALENDAR-187) Line 861 - Lastline under "Performance" two periods ".." Should be one.
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 30 Nov 2010 23:27:23 -0000
[OASIS Issue Tracker] Created: (WSCALENDAR-186) Line 857 - Areinheritance rules defined for the sequence or service level ? Are theymessage specific or service specific. If message specific, which systemenforces the specs ?
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 30 Nov 2010 23:25:53 -0000
[OASIS Issue Tracker] Created: (WSCALENDAR-185) Line 528 -Unstructured data, almost always requires human interference to structureand classify the data for retrieval. Is this the intent here ?
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 30 Nov 2010 23:25:43 -0000
[OASIS Issue Tracker] Created: (WSCALENDAR-184) Line 518 - "for forexample" repeated "for"
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 30 Nov 2010 23:25:33 -0000
[OASIS Issue Tracker] Created: (WSCALENDAR-183) Line 514 -Typically this is a middleware function, where is the inter-domaininteractions occuring in this architecture ?
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 30 Nov 2010 23:25:24 -0000
[OASIS Issue Tracker] Created: (WSCALENDAR-182) Line 287 - Did notcheck examples for well formedness.
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 30 Nov 2010 23:23:41 -0000
[OASIS Issue Tracker] Created: (WSCALENDAR-181) Line 206 - Standardschema should include a WS Specification as an appendix to this document,akin to an XML Data Dictionary.
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 30 Nov 2010 23:23:32 -0000
[OASIS Issue Tracker] Created: (WSCALENDAR-180) Line 183 - "UCT vs.Local Time" Should it be "UTC" ? For Universal Coordinated Time
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 30 Nov 2010 23:23:24 -0000
[OASIS Issue Tracker] Created: (WSCALENDAR-179) Line 135 - Theframework as it stands define the services execution context. The RTO can'tendorse unless and until the policy context is defined. When and would thepolicy context be defined ?
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 30 Nov 2010 23:21:24 -0000
[OASIS Issue Tracker] Created: (WSCALENDAR-178) Line 41 -"Normative" reference intent. Is interpreted to mean Standards forming ? Ifso what are the business processes affected and performance benchmarks forcompliance ?
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 30 Nov 2010 23:19:43 -0000
[OASIS Issue Tracker] Created: (WSCALENDAR-177) Lines 3 and 8 - Thearchitecture as outlined may not offer a central system to control, monitorand audit events and transactions.
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 30 Nov 2010 23:19:33 -0000
[OASIS Issue Tracker] Created: (WSCALENDAR-176) Line 13 - Needclarification on the reference to Payroll "or in weeks there is nopayroll".
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 30 Nov 2010 23:19:24 -0000
[OASIS Issue Tracker] Created: (WSCALENDAR-175) Line 1476 -"principals" to "principal's"
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 30 Nov 2010 23:17:32 -0000
[OASIS Issue Tracker] Created: (WSCALENDAR-174) Line 861 - "AInterval or Calendar Gluon inherits its attributes through it's the closestparent" to "An Interval or Calendar Gluon inherits its attributes throughits closest parent."
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 30 Nov 2010 23:17:24 -0000
[OASIS Issue Tracker] Created: (WSCALENDAR-173) Line 690 - No 5.1secton - section 5 has children 5.1.1 to 5.1.6.
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 30 Nov 2010 23:15:32 -0000
[OASIS Issue Tracker] Created: (WSCALENDAR-172) Line 441 -"whenever single interval" to "whenever a single interval "
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 30 Nov 2010 23:15:24 -0000
[OASIS Issue Tracker] Created: (WSCALENDAR-171) Line 439 - "seond"to "second"
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 30 Nov 2010 23:13:50 -0000
[OASIS Issue Tracker] Created: (WSCALENDAR-170) Line 366 - Agreewith Sean's comment - how is this structured? Or is it explicitlyunnecessary?
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 30 Nov 2010 23:13:41 -0000
[OASIS Issue Tracker] Created: (WSCALENDAR-169) Line 274 - Shouldbe 3.2.1
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 30 Nov 2010 23:13:32 -0000
[OASIS Issue Tracker] Created: (WSCALENDAR-168) Line 184 - "When toprovide a service" Needs a matching separator hyphen
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 30 Nov 2010 23:13:23 -0000
[OASIS Issue Tracker] Created: (WSCALENDAR-167) Line 173 - Repeatedtext ("quite different")
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 30 Nov 2010 23:11:54 -0000
[OASIS Issue Tracker] Created: (WSCALENDAR-166) Line 158 - Repeatedtext ("in the")
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 30 Nov 2010 23:11:45 -0000
[OASIS Issue Tracker] Created: (WSCALENDAR-165) Line 154 -"RESTfull" to "RESTful" (and throughout the document)
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 30 Nov 2010 23:11:36 -0000
[OASIS Issue Tracker] Created: (WSCALENDAR-164) Line 861 - So agluon may be a superclass of an interval OR a sequence/partition. Againthis makes it very difficult to validate.
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 30 Nov 2010 23:11:27 -0000
[OASIS Issue Tracker] Created: (WSCALENDAR-163) Line 859 - There isno way to define an interval and then use it in a schedule withoutredefining it again?
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 30 Nov 2010 23:09:23 -0000
[OASIS Issue Tracker] Created: (WSCALENDAR-162) Line 766 -"inherits all" - How, by being next to Gluon in payload?
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 30 Nov 2010 23:07:41 -0000
[OASIS Issue Tracker] Created: (WSCALENDAR-161) Line 712 - This isa class definition and declaration in one?
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 30 Nov 2010 23:07:32 -0000
[OASIS Issue Tracker] Created: (WSCALENDAR-160) Line 709 - "withthe an Interval" - no need for "the"
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 30 Nov 2010 23:07:24 -0000
[OASIS Issue Tracker] Created: (WSCALENDAR-159) Line 641 - as is:</quantiyprice> should be: </quantity>
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 30 Nov 2010 23:05:33 -0000
[OASIS Issue Tracker] Created: (WSCALENDAR-158) Line 621 - "It theservice": no need for "It"
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 30 Nov 2010 23:05:24 -0000
[OASIS Issue Tracker] Created: (WSCALENDAR-157) Line 538 - As threeoptional elements there is no way to validate that one of them ispopulated.
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 30 Nov 2010 23:03:52 -0000
[OASIS Issue Tracker] Created: (WSCALENDAR-156) Line 538 -Unfinished sentence
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 30 Nov 2010 23:03:42 -0000
[OASIS Issue Tracker] Created: (WSCALENDAR-155) Line 504 -precision not accuracy. Is it one hour or 1:00:00.00 hours.
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 30 Nov 2010 23:03:33 -0000
[OASIS Issue Tracker] Created: (WSCALENDAR-154) Line 440 - Nothaving a separate entity for a scheduled sequence makes validationdifficult. E.g. is the data intended to be a sequence or a scheduledsequence.
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 30 Nov 2010 23:03:24 -0000
[OASIS Issue Tracker] Created: (WSCALENDAR-153) 366 - Without anexplicit order there it is difficult to validate the sequence. E.g. thatthe sequence moves forward in time.
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 30 Nov 2010 22:59:43 -0000
[OASIS Issue Tracker] Created: (WSCALENDAR-152) 320 - "two" not"to"
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 30 Nov 2010 22:59:33 -0000
[OASIS Issue Tracker] Created: (WSCALENDAR-151) Line 318 -"intervlas" to "intervals"
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 30 Nov 2010 22:59:25 -0000
[OASIS Issue Tracker] Created: (WSCALENDAR-150) Section C.1.1 -Clause (B) in the last sentence should be revised by adding the word "what"after the word "communicates".
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 30 Nov 2010 22:31:34 -0000
[OASIS Issue Tracker] Created: (WSCALENDAR-149) Section 8.18 - Ifthe use of the word "owner" may be interpreted to apply to certain data,then a term other than "owner" should be used to avoid the legalimplications associated with using the term "owner".
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 30 Nov 2010 22:31:25 -0000
[OASIS Issue Tracker] Created: (WSCALENDAR-148) White Paper, pg 4,para 5, 4th sentence - should be revised by inserting the word "may"between the words "autonomy" and "free".
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 30 Nov 2010 22:29:32 -0000
[OASIS Issue Tracker] Created: (WSCALENDAR-147) White Paper, pg 4,para 5, 3rd sentence - should be revised by inserting the word "may"between the words "system" and "increase".
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 30 Nov 2010 22:29:24 -0000
[OASIS Issue Tracker] Created: (WSCALENDAR-146) Line 1836 - Whydoes the example return an icalendar tag rather then a wscalendar tag?
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 30 Nov 2010 22:25:33 -0000
[OASIS Issue Tracker] Created: (WSCALENDAR-145) Line 1419 - Coulduse description of what is intended by Abstract model as different fromImplementation model and how they should be considered.
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 30 Nov 2010 22:25:24 -0000
[OASIS Issue Tracker] Created: (WSCALENDAR-144) Line 1423 - Schemasays that wscalendarrelation is a member of properties of vtodo. UML modelimplies it is a specialization of VToDo. Suggest that the UML models andschema be made consistent representations.
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 30 Nov 2010 22:23:41 -0000
[OASIS Issue Tracker] Created: (WSCALENDAR-143) Inheritance model -Inheritance model appears similar to CSS in that once defined, a termpersists until overriden by a contained element. If this is so, a referenceto this might make sense.
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 30 Nov 2010 22:23:32 -0000
[OASIS Issue Tracker] Created: (WSCALENDAR-142) Line 579 - Why isperformance a property of attach, rather then a property of interval/gluon?
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 30 Nov 2010 22:23:23 -0000
[OASIS Issue Tracker] Created: (WSCALENDAR-141) WS-Calendard.xsd -Schema has error in declaration
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 30 Nov 2010 22:21:28 -0000
[OASIS Issue Tracker] Created: (WSCALENDAR-140) Line 690 - Why doyou need a separate class / tag for Gluon? Gluons seem to have an almostidentical property set to Intervals. Consider merging "gluon" differencesinto WS-Calendar interval class.
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 30 Nov 2010 22:19:25 -0000
[OASIS Issue Tracker] Created: (WSCALENDAR-139) Line 142, 221 - Isthis draft xCal? Couldn't find [XCAL] in the references. Note: there areseveral other reference inconsistencies that should be remedied.
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 30 Nov 2010 22:17:35 -0000
[OASIS Issue Tracker] Created: (WSCALENDAR-138) Lines 199 - 202 -Recommend making standard require only universal time in messaging. Localtime can always be computed "locally" allowing for one time conversion whenneeded. This avoids a lot of complexity in interpreting time.
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 30 Nov 2010 22:17:25 -0000
[OASIS Issue Tracker] Created: (WSCALENDAR-137) Line 2168 - I thinkthere is a referencing error on this line as indicated by the text "Error!Reference source not found".
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 30 Nov 2010 22:13:25 -0000
[OASIS Issue Tracker] Created: (WSCALENDAR-136) Line 1811 - I thinkthe closing tag is wrong, it should be "</D:description>".
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 30 Nov 2010 22:12:00 -0000
[OASIS Issue Tracker] Created: (WSCALENDAR-135) Line 861 - Removethe second period at the end of the sentence for the inheritance rules forperformance.
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 30 Nov 2010 22:11:43 -0000
[OASIS Issue Tracker] Created: (WSCALENDAR-134) Line 853 - A wordis missing in the sentence, I think it should read "The Calendar Gluonhappens to be related to...".
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 30 Nov 2010 22:11:35 -0000
[OASIS Issue Tracker] Created: (WSCALENDAR-133) Line 530 - Add aspace after the end of the sentence.
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 30 Nov 2010 22:11:25 -0000
[OASIS Issue Tracker] Created: (WSCALENDAR-132) Line 439 - The word"second" is misspelled.
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 30 Nov 2010 22:09:41 -0000
[OASIS Issue Tracker] Created: (WSCALENDAR-131) Line 240 - Removethe text "of the" from this line.
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 30 Nov 2010 22:09:33 -0000
[OASIS Issue Tracker] Created: (WSCALENDAR-130) Line 211 - The word"association" should be "associate".
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 30 Nov 2010 22:09:24 -0000
[OASIS Issue Tracker] Created: (WSCALENDAR-129) Lines 173 and 174 -The text "quite different" is repeated, remove on set.
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 30 Nov 2010 22:07:43 -0000
[OASIS Issue Tracker] Created: (WSCALENDAR-128) Lines 17 and 18 -Add trademark indications to the identified standards.
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 30 Nov 2010 22:07:33 -0000
[OASIS Issue Tracker] Created: (WSCALENDAR-127) The use ofiCalendar to schedule device services across a large domain of buildings(or equipment within a building) could have the unintended effect of loadsynchronization.
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 30 Nov 2010 22:07:25 -0000
[OASIS Issue Tracker] Created: (WSCALENDAR-126) ConceptualOverview: Calendar Glueons, figure 4 - The text states that there is a 15minute time between classes in the 90min class schedule but this is notrepresented in the model.
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 30 Nov 2010 22:01:35 -0000
[OASIS Issue Tracker] Created: (WSCALENDAR-125) Conceptualoverview: Why WSCal, Why Now: pg 4, para 3 - Building system ws protocols(oBiX, LON-WS, etc) should be identified as protected names.
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 30 Nov 2010 22:01:25 -0000
Web Services Calendar (WS-Calendar) TC - 26 November 2010
From
"Gershon Janssen" <gershon@qroot.com> on 26 Nov 2010 14:13:34 -0000
Start-Time Randomization
From
"Jeremy Roberts" <jeremy@lonmark.org> on 23 Nov 2010 16:35:29 -0000
[OASIS Issue Tracker] Created: (WSCALENDAR-124) WS-Calendar shouldbe able to express an open ended period, i.e. start time, but no end time
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 23 Nov 2010 04:39:35 -0000
RE: [ws-calendar] Groups - Regular WS-Calendar Meeting added
From
"Jeremy Roberts" <jeremy@lonmark.org> on 18 Nov 2010 17:51:52 -0000
[OASIS Issue Tracker] Created: (WSCALENDAR-123) Consider SOAPdefintions and WSDL as well
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 16 Nov 2010 16:19:24 -0000
Re: [ws-calendar] Groups - Regular WS-Calendar Meeting added
From
"William Cox" <wtcox@coxsoftwarearchitects.com> on 12 Nov 2010 17:10:31 -0000
Re: [ws-calendar] Groups - Regular WS-Calendar Meeting added
From
"William Cox" <wtcox@coxsoftwarearchitects.com> on 12 Nov 2010 17:04:46 -0000
Canceled / Web Services Calendar (WS-Calendar) TC - 12 November 2010
From
"Gershon Janssen" <gershon@qroot.com> on 12 Nov 2010 16:31:02 -0000
Groups - Regular WS-Calendar Meeting cancelled
From
gershon@qroot.com on 12 Nov 2010 16:24:26 -0000
RE: [ws-calendar] Groups - Regular WS-Calendar Meeting added
From
"Considine, Toby (Campus Services IT)" <Toby.Considine@unc.edu> on 12 Nov 2010 14:28:22 -0000
PROPOSED AGENDA - Web Services Calendar (WS-Calendar) TC - 12 November 2010
From
"Gershon Janssen" <gershon@qroot.com> on 12 Nov 2010 12:29:34 -0000
Groups - Regular WS-Calendar Meeting added
From
gershon@qroot.com on 12 Nov 2010 12:26:41 -0000
Feedback on ws-calendar
From
Mike Douglass <douglm@rpi.edu> on 11 Nov 2010 04:42:21 -0000
Next WS-Calendar meeting Friday 12 November 2010
From
"Gershon Janssen" <gershon@qroot.com> on 5 Nov 2010 16:18:19 -0000
More Icalendar Gems
From
"Toby Considine" <Toby.Considine@gmail.com> on 4 Nov 2010 15:00:45 -0000
UPDATED Phone/Web for Nov 2-3 PAP09 + OASIS Energy Interoperation+ NAESB Phase 2 PAP09 requirements
From
William Cox <wtcox@CoxSoftwareArchitects.com> on 2 Nov 2010 14:07:19 -0000
Re: Review document details for OASIS Energy Interoperation November2 + Schedule Details and NAESB Phase 2 PAP09 requirements
From
William Cox <wtcox@CoxSoftwareArchitects.com> on 2 Nov 2010 02:27:01 -0000
Review document details for OASIS Energy Interoperation November2
From
William Cox <wtcox@CoxSoftwareArchitects.com> on 2 Nov 2010 02:17:59 -0000
Mail converted by
MHonArc
2.5.0b2