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
341 messages in this archive
(listed by date, most recent first)
|
Thread Index
|
List Home
[OASIS Issue Tracker] Created: (WSCALENDAR-457) Ominibus issue forPaul Knight
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 31 May 2011 22:00:58 -0000
15-Day Committee Specification Draft Public Review Request forWS-Calendar Version 1.0
From
Paul Knight <paul.knight@oasis-open.org> on 31 May 2011 13:57:25 -0000
Committee Specification Draft Creation / Upload Request forWS-Calendar Version 1.0
From
Paul Knight <paul.knight@oasis-open.org> on 31 May 2011 13:44:21 -0000
[OASIS Issue Tracker] Created: (WSCALENDAR-456) Ominbus Issue forSharon Dinges comments
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 29 May 2011 21:54:48 -0000
Groups - Minutes_WS-Calendar-TC_20110527.docx uploaded
From
wtcox@coxsoftwarearchitects.com on 27 May 2011 20:35:50 -0000
Groups - ws-calendar-v1.0-wd25-package.zip uploaded
From
toby.considine@unc.edu on 27 May 2011 13:28:51 -0000
Documents and Changes
From
"Toby Considine" <Toby.Considine@gmail.com> on 27 May 2011 13:00:58 -0000
Groups - Regular WS-Calendar Meeting modified
From
gershon@qroot.com on 27 May 2011 05:48:08 -0000
Draft motions for 7am PDT/10am EDT brief meeting on Friday May 27
From
William Cox <wtcox@CoxSoftwareArchitects.com> on 27 May 2011 04:15:59 -0000
URGENT - Meeting Friday 27 is at 7am PDT/10am EDT - doesn't seemto be correct in the schedule
From
William Cox <wtcox@CoxSoftwareArchitects.com> on 27 May 2011 04:09:29 -0000
Groups - ws-calendar-v1.0-wd25-package.zip uploaded
From
wtcox@coxsoftwarearchitects.com on 27 May 2011 03:51:51 -0000
Groups - ws-calendar-schemas-v1.0-wd25.zip uploaded
From
wtcox@coxsoftwarearchitects.com on 27 May 2011 03:47:04 -0000
Groups - ws-calendar-v1.0-wd25-package.zip uploaded
From
wtcox@coxsoftwarearchitects.com on 27 May 2011 03:22:35 -0000
Groups - ws-calendar-schemas-v1.0-wd25.zip uploaded
From
wtcox@coxsoftwarearchitects.com on 27 May 2011 03:16:04 -0000
Groups - ws-calendar-spec-v1.0-wd25.pdf uploaded
From
wtcox@coxsoftwarearchitects.com on 27 May 2011 03:12:54 -0000
Groups - ws-calendar-spec-v1.0-wd25.docx uploaded
From
wtcox@coxsoftwarearchitects.com on 27 May 2011 03:11:45 -0000
Groups - ws-calendar-spec-v1.0-wd25-with-changes.pdf uploaded
From
wtcox@coxsoftwarearchitects.com on 27 May 2011 03:10:44 -0000
Groups - ws-calendar-spec-v1.0-wd25-with-changes.docx uploaded
From
wtcox@coxsoftwarearchitects.com on 27 May 2011 03:07:40 -0000
Additional notes on wd25-wip1 for Friday morning
From
William Cox <wtcox@CoxSoftwareArchitects.com> on 26 May 2011 22:13:01 -0000
Groups - ws-calendar-spec-v1.0-wd25-wip1-diff.pdf uploaded
From
wtcox@coxsoftwarearchitects.com on 26 May 2011 21:30:47 -0000
Groups - ws-calendar-spec-v1.0-wd25-wip1.docx uploaded
From
wtcox@coxsoftwarearchitects.com on 26 May 2011 21:13:19 -0000
Groups - ws-calendar-spec-v1.0-wd24.pdf uploaded
From
toby.considine@unc.edu on 26 May 2011 17:07:35 -0000
Groups - ws-calendar-spec-v1.0-wd24.docx uploaded
From
toby.considine@unc.edu on 26 May 2011 17:05:49 -0000
Groups - ws-calendar-spec-v1.0-wd24-with-changes.pdf uploaded
From
toby.considine@unc.edu on 26 May 2011 17:04:47 -0000
Groups - ws-calendar-spec-v1.0-wd24-with-changes.docx uploaded
From
toby.considine@unc.edu on 26 May 2011 17:01:07 -0000
Groups - ws-calendar-spec-v1.0-wd23.pdf uploaded
From
toby.considine@unc.edu on 24 May 2011 15:06:44 -0000
Groups - ws-calendar-spec-v1.0-wd23.docx uploaded
From
toby.considine@unc.edu on 24 May 2011 15:04:54 -0000
Groups - ws-calendar-spec-v1.0-wd23-with-changes.pdf uploaded
From
toby.considine@unc.edu on 24 May 2011 15:03:20 -0000
Groups - ws-calendar-spec-v1.0-wd23-with-changes.docx uploaded
From
toby.considine@unc.edu on 24 May 2011 15:01:57 -0000
Confirming Friday's work Plan
From
"Toby Considine" <Toby.Considine@gmail.com> on 21 May 2011 15:34:25 -0000
[OASIS Issue Tracker] Created: (WSCALENDAR-455) Name is "MikeDouglass" not "Mike Douglas"
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 20 May 2011 16:26:47 -0000
Groups - ws-calendar-spec-v1.0-wd22.pdf uploaded
From
wtcox@coxsoftwarearchitects.com on 20 May 2011 16:15:46 -0000
Groups - ws-calendar-spec-v1.0-wd22.docx uploaded
From
wtcox@coxsoftwarearchitects.com on 20 May 2011 16:11:46 -0000
Re: [ws-calendar] Meeting Agenda Today
From
William Cox <wtcox@CoxSoftwareArchitects.com> on 20 May 2011 15:51:39 -0000
Meeting Agenda Today
From
"Toby Considine" <Toby.Considine@gmail.com> on 20 May 2011 15:18:02 -0000
[ws-calendar] Today's conf call
From
Benoît Lepeuple <b.lepeuple@arcinfo.com> on 20 May 2011 14:36:09 -0000
Meeting today
From
"Gershon Janssen" <gershon@qroot.com> on 20 May 2011 14:33:46 -0000
Yet another schemas zipfile
From
Mike Douglass <douglm@rpi.edu> on 20 May 2011 02:05:01 -0000
Re: [ws-calendar] Procedural Advice
From
Mike Douglass <douglm@rpi.edu> on 19 May 2011 14:05:43 -0000
Procedural Advice
From
"Toby Considine" <Toby.Considine@gmail.com> on 19 May 2011 12:34:24 -0000
Schemas - yet again
From
Mike Douglass <douglm@rpi.edu> on 18 May 2011 03:39:14 -0000
[OASIS Issue Tracker] Updated: (WSCALENDAR-346) Table 3-4 isAttachment Element/Use/Discussion, and the discussion for Text seems out ofplace.
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 18 May 2011 00:13:18 -0000
[OASIS Issue Tracker] Updated: (WSCALENDAR-413) Line 143 -Namespaces used in this specification
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 18 May 2011 00:13:08 -0000
[OASIS Issue Tracker] Updated: (WSCALENDAR-416) Lines 902, 1026 -Example composition
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 18 May 2011 00:13:00 -0000
[OASIS Issue Tracker] Updated: (WSCALENDAR-452) General Approach toNormative References
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 18 May 2011 00:12:47 -0000
Different vavailability example
From
Mike Douglass <douglm@rpi.edu> on 17 May 2011 15:14:33 -0000
Re: [ws-calendar] Urgent - attention needed
From
Mike Douglass <douglm@rpi.edu> on 17 May 2011 04:58:57 -0000
RE: [ws-calendar] Urgent - attention needed
From
"Considine, Toby (Campus Services IT)" <Toby.Considine@unc.edu> on 17 May 2011 03:54:03 -0000
Re: [ws-calendar] Urgent - attention needed
From
Mike Douglass <douglm@rpi.edu> on 17 May 2011 03:52:28 -0000
Urgent - attention needed
From
"Toby Considine" <Toby.Considine@gmail.com> on 17 May 2011 03:42:42 -0000
Groups - ws-calendar-spec-v1.0-wd21.pdf uploaded
From
toby.considine@unc.edu on 17 May 2011 03:32:00 -0000
Groups - ws-calendar-spec-v1.0-wd21.docx uploaded
From
toby.considine@unc.edu on 17 May 2011 03:30:59 -0000
Groups - ws-calendar-spec-v1.0-wd21-with-changes.pdf uploaded
From
toby.considine@unc.edu on 17 May 2011 03:30:12 -0000
Groups - ws-calendar-spec-v1.0-wd21-with-changes.docx uploaded
From
toby.considine@unc.edu on 17 May 2011 03:28:54 -0000
[OASIS Issue Tracker] Updated: (WSCALENDAR-400) All: Ensure thatdefined or called out terms (e.g. Duration, Schedule, ...) are uniformlycapitalized and that non-defined terms are not.
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 17 May 2011 03:20:47 -0000
[OASIS Issue Tracker] Commented: (WSCALENDAR-222) Recurrence Rulesseem recursive, Unable to build VAvailability
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 16 May 2011 21:00:47 -0000
Groups - ws-calendar-examples-v1.0-wd21-wip1.zip uploaded
From
toby.considine@unc.edu on 16 May 2011 18:05:37 -0000
RE: [ws-calendar] Events and State Changes
From
Edward Koch <ed@akuacom.com> on 16 May 2011 17:09:43 -0000
RE: [ws-calendar] Events and State Changes
From
"Bartell, Bruce" <bbartell@xtensible.net> on 16 May 2011 16:10:37 -0000
RE: [ws-calendar] Events and State Changes
From
"Considine, Toby (Campus Services IT)" <Toby.Considine@unc.edu> on 16 May 2011 15:28:46 -0000
RE: [ws-calendar] Events and State Changes
From
Edward Koch <ed@akuacom.com> on 16 May 2011 15:13:21 -0000
Re: [ws-calendar] Events and State Changes
From
Mike Douglass <douglm@rpi.edu> on 16 May 2011 14:27:45 -0000
Re: [ws-calendar] Events and State Changes
From
Mike Douglass <douglm@rpi.edu> on 16 May 2011 14:13:12 -0000
Events and State Changes
From
"Toby Considine" <Toby.Considine@gmail.com> on 16 May 2011 13:01:14 -0000
Multi-put?
From
Mike Douglass <douglm@rpi.edu> on 16 May 2011 04:23:21 -0000
Latest state of schemas
From
Mike Douglass <douglm@rpi.edu> on 15 May 2011 05:10:45 -0000
[OASIS Issue Tracker] Commented: (WSCALENDAR-342) Is there astandard vlue for durations of Month and Year?
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 15 May 2011 03:00:48 -0000
RE: [ws-calendar] Defining the Interval - critical
From
"Ed Cazalet" <ed@cazalet.com> on 13 May 2011 16:06:23 -0000
RE: [ws-calendar] Baby and Bathwater
From
Benoît Lepeuple <b.lepeuple@arcinfo.com> on 13 May 2011 16:04:12 -0000
RE: [ws-calendar] Defining the Interval - critical
From
"Toby Considine" <Toby.Considine@gmail.com> on 13 May 2011 15:55:21 -0000
Re: [ws-calendar] Baby and Bathwater
From
William Cox <wtcox@CoxSoftwareArchitects.com> on 13 May 2011 15:54:05 -0000
RE: [ws-calendar] Defining the Interval - critical
From
Benoît Lepeuple <b.lepeuple@arcinfo.com> on 13 May 2011 15:49:43 -0000
RE: [ws-calendar] RE: Terms and Inheritance
From
Benoît Lepeuple <b.lepeuple@arcinfo.com> on 13 May 2011 15:44:54 -0000
RE: Baby and Bathwater
From
Edward Koch <ed@akuacom.com> on 13 May 2011 15:40:00 -0000
PROPOSED AGENDA - Web Services Calendar (WS-Calendar) TC - 13 May 2011
From
"Gershon Janssen" <gershon@qroot.com> on 13 May 2011 15:38:24 -0000
Baby and Bathwater
From
"Considine, Toby (Campus Services IT)" <Toby.Considine@unc.edu> on 13 May 2011 13:27:44 -0000
RE: [ws-calendar] gluons, intervals and standards
From
"Considine, Toby (Campus Services IT)" <Toby.Considine@unc.edu> on 13 May 2011 13:24:35 -0000
Preparing for Friday's meeting
From
"Toby Considine" <Toby.Considine@gmail.com> on 12 May 2011 21:31:20 -0000
Groups - ws-calendar-spec-v1.0-wd20.pdf uploaded
From
toby.considine@unc.edu on 12 May 2011 21:26:22 -0000
Groups - ws-calendar-spec-v1.0-wd20.docx uploaded
From
toby.considine@unc.edu on 12 May 2011 21:25:46 -0000
Groups - ws-calendar-spec-v1.0-wd20-with-changes.docx uploaded
From
toby.considine@unc.edu on 12 May 2011 21:25:10 -0000
Groups - ws-calendar-spec-v1.0-wd20-with-changes.pdf uploaded
From
toby.considine@unc.edu on 12 May 2011 21:24:23 -0000
[OASIS Issue Tracker] Updated: (WSCALENDAR-229) Remove any unusedtypes from the schema, probably replace with some form of annotation.
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 12 May 2011 21:19:58 -0000
[OASIS Issue Tracker] Updated: (WSCALENDAR-258) Line 1020 - does"availability" in the rules for Schedules and Availability mean"Availability" as defined in the document?
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 12 May 2011 21:19:49 -0000
[OASIS Issue Tracker] Updated: (WSCALENDAR-272) Line 392-394 - itis unclear which elements are used from RFC 5988 from the list of elementsin Section 6.2.2 of that RFC - explicitly clarify elements
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 12 May 2011 21:19:40 -0000
[OASIS Issue Tracker] Updated: (WSCALENDAR-308) PR02 What are youdefining? XCAL? WS-Calendar? Some combination?
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 12 May 2011 21:19:31 -0000
[OASIS Issue Tracker] Updated: (WSCALENDAR-364) Line 887 - Uid,Summary, dtStart, dtEnd, duration, and Granularity
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 12 May 2011 21:19:22 -0000
[OASIS Issue Tracker] Updated: (WSCALENDAR-379) Cover and startingon line 59: The RFCs listed seem to be out of sync (in the normativereferences. Verify that current dates are used; Vavailability has beenrecently updated.
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 12 May 2011 21:19:14 -0000
[OASIS Issue Tracker] Updated: (WSCALENDAR-394) Line 205 - Comparethis first paragraph with e.g. line 43 which talks about what the intentwas; this paragraph is in better voice describing how the work wasproduced.
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 12 May 2011 21:19:05 -0000
[OASIS Issue Tracker] Updated: (WSCALENDAR-402) Line 354-356 - Wehave Intervals, now we have Time Segments? I don't find a definition, andit seems very similar.
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 12 May 2011 21:18:55 -0000
[OASIS Issue Tracker] Updated: (WSCALENDAR-408) Line 1321 - Why is"Service Advertisements" in the heading? This is more than just "serviceadv" - should this be "describing" or "managing" "start times"?
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 12 May 2011 21:18:47 -0000
[OASIS Issue Tracker] Updated: (WSCALENDAR-416) Lines 902, 1026 -Example composition
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 12 May 2011 21:18:38 -0000
[OASIS Issue Tracker] Updated: (WSCALENDAR-431) All - The standardprovides every possible method to define intervals and schedules while thisis clever it does not increase the chance of interoperability.
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 12 May 2011 21:18:29 -0000
[OASIS Issue Tracker] Updated: (WSCALENDAR-433) Section 2.2 - ",the service scheduled to shed load " - How does this example change thisspec?
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 12 May 2011 21:18:20 -0000
[OASIS Issue Tracker] Updated: (WSCALENDAR-450) Section 4 - RESTfulservices
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 12 May 2011 21:18:11 -0000
[OASIS Issue Tracker] Updated: (WSCALENDAR-453) Collector for rulesinvolving dtStart, dtEnd and Duration
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 12 May 2011 21:18:02 -0000
[OASIS Issue Tracker] Updated: (WSCALENDAR-419) Line 2688 - Section5.3 "still to come". Missing section in standard document.
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 12 May 2011 14:26:06 -0000
[OASIS Issue Tracker] Updated: (WSCALENDAR-449) Section 5 -Conformance and Rules
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 12 May 2011 14:25:56 -0000
[OASIS Issue Tracker] Updated: (WSCALENDAR-226) Schema is wrongaround duration.
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 12 May 2011 14:05:53 -0000
[OASIS Issue Tracker] Updated: (WSCALENDAR-226) Schema is wrongaround duration.
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 12 May 2011 14:03:54 -0000
[OASIS Issue Tracker] Updated: (WSCALENDAR-417)iCalendar-valtypes.xsd
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 12 May 2011 13:52:14 -0000
[OASIS Issue Tracker] Updated: (WSCALENDAR-418)iCalendar-wscal-extensions - Gluons and Intervals are recursive
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 12 May 2011 13:52:04 -0000
[OASIS Issue Tracker] Updated: (WSCALENDAR-422) Add reference tovavailability schema to table 1-2
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 12 May 2011 13:51:54 -0000
[OASIS Issue Tracker] Commented: (WSCALENDAR-430) Table 1.6 - Whatvalues? (Calendar date?)
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 12 May 2011 13:45:56 -0000
[OASIS Issue Tracker] Updated: (WSCALENDAR-426) Abstract - If thereis nothing energy sector specific in this standard what benefit does itprovide over the other standards mentioned.
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 12 May 2011 01:02:53 -0000
[OASIS Issue Tracker] Commented: (WSCALENDAR-453) Collector forrules involving dtStart, dtEnd and Duration
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 12 May 2011 00:40:55 -0000
gluons, intervals and standards
From
Mike Douglass <douglm@rpi.edu> on 11 May 2011 19:47:17 -0000
Re: [ws-calendar] Defining the Interval - critical
From
William Cox <wtcox@CoxSoftwareArchitects.com> on 11 May 2011 16:37:58 -0000
Defining the Interval - critical
From
"Toby Considine" <Toby.Considine@gmail.com> on 11 May 2011 15:10:55 -0000
Revised 1-6
From
"Toby Considine" <Toby.Considine@gmail.com> on 11 May 2011 14:53:57 -0000
RE: Terms and Inheritance
From
"Toby Considine" <Toby.Considine@gmail.com> on 10 May 2011 20:57:14 -0000
What's the difference between components
From
"Toby Considine" <Toby.Considine@gmail.com> on 10 May 2011 15:00:02 -0000
[OASIS Issue Tracker] Commented: (WSCALENDAR-453) Collector forrules involving dtStart, dtEnd and Duration
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 10 May 2011 14:10:53 -0000
Re: [ws-calendar] Terms and Inheritance
From
Mike Douglass <douglm@rpi.edu> on 10 May 2011 14:01:02 -0000
[OASIS Issue Tracker] Commented: (WSCALENDAR-454) Improveorthogonality of Binding / Inheritance etc.
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 10 May 2011 13:58:54 -0000
[OASIS Issue Tracker] Commented: (WSCALENDAR-454) Improveorthogonality of Binding / Inheritance etc.
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 10 May 2011 13:56:55 -0000
RE: [ws-calendar] Terms and Inheritance
From
"Toby Considine" <Toby.Considine@gmail.com> on 10 May 2011 13:27:12 -0000
[OASIS Issue Tracker] Created: (WSCALENDAR-454) Improveorthogonality of Binding / Inheritance etc.
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 10 May 2011 13:24:59 -0000
Terms and Inheritance
From
"Toby Considine" <Toby.Considine@gmail.com> on 10 May 2011 13:22:07 -0000
[OASIS Issue Tracker] Updated: (WSCALENDAR-361) Line 881 - The"optionality" of dtEnd and duration is not clearly defined
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 9 May 2011 23:03:02 -0000
[OASIS Issue Tracker] Updated: (WSCALENDAR-361) Line 881 - The"optionality" of dtEnd and duration is not clearly defined
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 9 May 2011 23:02:53 -0000
[OASIS Issue Tracker] Commented: (WSCALENDAR-363) Line 887 - Therelationship of tables 3-7 and 3-8 is not clear.
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 9 May 2011 18:24:53 -0000
Musings, but not yet Conformance on dtStart, Duration, and dtEnd, with a little bit of UTC thrown in.
From
"Toby Considine" <Toby.Considine@gmail.com> on 9 May 2011 13:56:22 -0000
[OASIS Issue Tracker] Updated: (WSCALENDAR-281) Line 858 - it isunclear why there is a restriction on using only dtStart and duration, anddtEnd and duration, but NOT dtStart and dtEnd.
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 9 May 2011 13:33:19 -0000
[OASIS Issue Tracker] Updated: (WSCALENDAR-281) Line 858 - it isunclear why there is a restriction on using only dtStart and duration, anddtEnd and duration, but NOT dtStart and dtEnd.
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 9 May 2011 13:33:05 -0000
[OASIS Issue Tracker] Updated: (WSCALENDAR-348) Line 368 - BothDtStart and Duration are "optional". What precisely does that mean? Thatneither need to be present? we find later that these values can beinherited from a gluon, but at this point "optional" seems to mean "novalue is required"
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 9 May 2011 13:32:55 -0000
[OASIS Issue Tracker] Updated: (WSCALENDAR-350) Line 368 -Elsewhere it's recommended that intervals have DtStart and Duration (eitherof which can be filled in through eg inheritance), but we see later an oddblend (line 858 adds DtEnd to the mix). This needs to be clear andconsistent across the doc.
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 9 May 2011 13:31:21 -0000
[OASIS Issue Tracker] Updated: (WSCALENDAR-356) Line 858 - dtEnd isnot listed and optional, as are dtStart and duration (DtStart andDuration?)
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 9 May 2011 13:31:12 -0000
[OASIS Issue Tracker] Updated: (WSCALENDAR-357) Line 858 - dtEndsays "SCHEDULED completion time..." is this implied or computed orexpressed? dtStart simply says "Start time"
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 9 May 2011 13:31:03 -0000
[OASIS Issue Tracker] Updated: (WSCALENDAR-364) Line 887 - Uid,Summary, dtStart, dtEnd, duration, and Granularity
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 9 May 2011 13:30:54 -0000
[OASIS Issue Tracker] Updated: (WSCALENDAR-364) Line 887 - Uid,Summary, dtStart, dtEnd, duration, and Granularity
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 9 May 2011 13:29:21 -0000
[OASIS Issue Tracker] Updated: (WSCALENDAR-420) Line 2678 -"Intervals SHALL NOT include an END time."
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 9 May 2011 13:29:11 -0000
[OASIS Issue Tracker] Updated: (WSCALENDAR-423) All - the standarddoes not effectively address the time period definitions that areparticular to the wholesale energy markets
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 9 May 2011 13:29:02 -0000
[OASIS Issue Tracker] Updated: (WSCALENDAR-426) Abstract - If thereis nothing energy sector specific in this standard what benefit does itprovide over the other standards mentioned.
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 9 May 2011 13:28:53 -0000
[OASIS Issue Tracker] Updated: (WSCALENDAR-429) Table 1.6 - Thedefinition relate to implementation e.g. "need inheritance" or "notcomplete" rather than the information that is undefined in this state
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 9 May 2011 13:27:35 -0000
[OASIS Issue Tracker] Updated: (WSCALENDAR-431) All - The standardprovides every possible method to define intervals and schedules while thisis clever it does not increase the chance of interoperability.
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 9 May 2011 13:27:25 -0000
[OASIS Issue Tracker] Updated: (WSCALENDAR-434) Section 2.2.1 - "norepresentation as whether UTC or local time are more appropriate " - A harddecision here would have provided lots of benefit to interoperability. Flexibility will not help with interoperability.
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 9 May 2011 13:27:16 -0000
[OASIS Issue Tracker] Updated: (WSCALENDAR-441) Section 3.1.1 -Choosing one format would benefit interoperability.
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 9 May 2011 13:27:07 -0000
[OASIS Issue Tracker] Updated: (WSCALENDAR-448) All - Does thestandard assuming any type of industry? Specification of interoperabilityfor the energy industry is lacking. Certain assumptions will leave theinteroperability more difficult and costly, rather than generic.
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 9 May 2011 13:26:59 -0000
[OASIS Issue Tracker] Created: (WSCALENDAR-453) Collector for rulesinvolving dtStart, dtEnd and Duration
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 8 May 2011 22:36:53 -0000
[OASIS Issue Tracker] Created: (WSCALENDAR-452) General Approach toNormative References
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 8 May 2011 14:32:53 -0000
[OASIS Issue Tracker] Created: (WSCALENDAR-451) Appendix
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 7 May 2011 19:54:53 -0000
[OASIS Issue Tracker] Created: (WSCALENDAR-450) Section 4 - RESTfulservices
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 7 May 2011 19:52:53 -0000
[OASIS Issue Tracker] Created: (WSCALENDAR-449) Section 5 -Conformance and Rules
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 7 May 2011 19:51:28 -0000
[OASIS Issue Tracker] Created: (WSCALENDAR-448) All - Does thestandard assuming any type of industry? Specification of interoperabilityfor the energy industry is lacking. Certain assumptions will leave theinteroperability more difficult and costly, rather than generic.
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 7 May 2011 19:51:19 -0000
[OASIS Issue Tracker] Created: (WSCALENDAR-447) All -implementation Model - Where is the detail?
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 7 May 2011 19:51:11 -0000
[OASIS Issue Tracker] Created: (WSCALENDAR-446) Section 7.1.3 -This version of standards is not ready for any type adoption orimplementation due to lack of Access control, provisioning, retrivals,insertions, deletion, GET and allocation or clarification of services.
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 7 May 2011 19:51:01 -0000
[OASIS Issue Tracker] Created: (WSCALENDAR-445) All - The use ofweb services has been assumed or mandated where not all other standardsthat use ws_calendar have the same assumption or mandate.
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 7 May 2011 19:50:53 -0000
[OASIS Issue Tracker] Created: (WSCALENDAR-444) All - Security isnot addressed anywhere in the standard. It is not sufficient to rely ontransport for trust. That would mean mandating the transport mechanism.
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 7 May 2011 19:49:10 -0000
[OASIS Issue Tracker] Created: (WSCALENDAR-443) Section 3.3.3 -Inheritance rules for Gluons - An information model would be much clearer.
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 7 May 2011 19:49:01 -0000
[OASIS Issue Tracker] Created: (WSCALENDAR-442) Section 3.3.1.1 -Gluons are another example of a multi-purpose, you don't need it unlessit's present class in this standard. It lacks a specific purpose thereforeit was very hard to name.
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 7 May 2011 19:48:53 -0000
[OASIS Issue Tracker] Created: (WSCALENDAR-441) Section 3.1.1 -Choosing one format would benefit interoperability.
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 7 May 2011 19:47:11 -0000
[OASIS Issue Tracker] Created: (WSCALENDAR-440) Section 3.1 -Schedule is not defined in Table 1.6
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 7 May 2011 19:47:02 -0000
[OASIS Issue Tracker] Created: (WSCALENDAR-439) Section 3.1.4.1 -Not creating a new type for an "anchored sequence" makes validation verydifficult.
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 7 May 2011 19:46:54 -0000
[OASIS Issue Tracker] Created: (WSCALENDAR-438) Section 3.1.4.1 -Is there some way to define a sequence and then re-use it in several"anchored sequences"
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 7 May 2011 19:45:33 -0000
[OASIS Issue Tracker] Created: (WSCALENDAR-437) Section 3.1.2 - "AnUnscheduled Interval " - Are these terms consistent/overlapping with table1.6
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 7 May 2011 19:45:25 -0000
[OASIS Issue Tracker] Created: (WSCALENDAR-436) All - Where is theinformation model (class model)? The widespread use of inheritance wouldhave been better understood with an inheritance model.
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 7 May 2011 19:45:15 -0000
[OASIS Issue Tracker] Created: (WSCALENDAR-435) Section 2.3 - "thespecification is not prescriptive " - Flexibility will not help withinteroperability. A customer has no idea if a vendor that supports thisstandard which actually interoperate in content or technology.
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 7 May 2011 19:45:07 -0000
[OASIS Issue Tracker] Created: (WSCALENDAR-434) Section 2.2.1 - "norepresentation as whether UTC or local time are more appropriate " - A harddecision here would have provided lots of benefit to interoperability. Flexibility will not help with interoperability.
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 7 May 2011 19:44:54 -0000
[OASIS Issue Tracker] Created: (WSCALENDAR-433) Section 2.2 - ",the service scheduled to shed load " - How does this example change thisspec?
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 7 May 2011 19:43:02 -0000
[OASIS Issue Tracker] Created: (WSCALENDAR-432) Section 2.1 - Mostof the vocabulary is specific to this standard not iCal
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 7 May 2011 19:42:53 -0000
[OASIS Issue Tracker] Created: (WSCALENDAR-431) All - The standardprovides every possible method to define intervals and schedules while thisis clever it does not increase the chance of interoperability.
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 7 May 2011 19:41:19 -0000
[OASIS Issue Tracker] Created: (WSCALENDAR-430) Table 1.6 - Whatvalues? (Calendar date?)
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 7 May 2011 19:41:10 -0000
[OASIS Issue Tracker] Created: (WSCALENDAR-429) Table 1.6 - Thedefinition relate to implementation e.g. "need inheritance" or "notcomplete" rather than the information that is undefined in this state
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 7 May 2011 19:41:02 -0000
[OASIS Issue Tracker] Created: (WSCALENDAR-428) Table 1.6 -Circular definitions.
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 7 May 2011 19:40:53 -0000
[OASIS Issue Tracker] Created: (WSCALENDAR-427) Table 1.6 - "Aninterval is anchored if it is bound..." - Is anchored a synonym for bound
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 7 May 2011 19:39:11 -0000
[OASIS Issue Tracker] Created: (WSCALENDAR-426) Abstract - If thereis nothing energy sector specific in this standard what benefit does itprovide over the other standards mentioned.
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 7 May 2011 19:39:02 -0000
[OASIS Issue Tracker] Created: (WSCALENDAR-425) All - security isnot addressed in any way
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 7 May 2011 19:38:53 -0000
[OASIS Issue Tracker] Created: (WSCALENDAR-424) All - the use ofgeneric data types make it impossible to determine the actual intent of themessage and limits validation. An error would change the intent of themessage with no way of knowing that an error had occurred
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 7 May 2011 19:37:01 -0000
[OASIS Issue Tracker] Created: (WSCALENDAR-423) All - the standarddoes not effectively address the time period definitions that areparticular to the wholesale energy markets
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 7 May 2011 19:36:53 -0000
RE: [ws-calendar] WS-Calendar derivations
From
"Bartell, Bruce" <bbartell@xtensible.net> on 6 May 2011 16:46:24 -0000
RE: [ws-calendar] Cleaning up of Action Items
From
"Gershon Janssen" <gershon@qroot.com> on 6 May 2011 16:25:31 -0000
Groups - Action Item Closed: #0014 [AI20100416-001] Send links to r...
From
gershon@qroot.com on 6 May 2011 16:20:55 -0000
[OASIS Issue Tracker] Commented: (WSCALENDAR-308) PR02 What are youdefining? XCAL? WS-Calendar? Some combination?
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 6 May 2011 15:58:54 -0000
More supporting material
From
Mike Douglass <douglm@rpi.edu> on 6 May 2011 15:16:46 -0000
RE: [ws-calendar] PROPOSED AGENDA - Web Services Calendar(WS-Calendar) TC - 06 May 2011
From
"Considine, Toby (Campus Services IT)" <Toby.Considine@unc.edu> on 6 May 2011 14:16:25 -0000
[OASIS Issue Tracker] Updated: (WSCALENDAR-324) Line 1873-1874 - the 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 6 May 2011 14:10:53 -0000
[OASIS Issue Tracker] Commented: (WSCALENDAR-308) PR02 What are youdefining? XCAL? WS-Calendar? Some combination?
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 6 May 2011 14:06:56 -0000
[OASIS Issue Tracker] Updated: (WSCALENDAR-282) Line 870 - thedefintion of "Bound" in Table 1-6 does not include Duration, as in "BoundDuration" employed in the sentence.
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 6 May 2011 13:38:53 -0000
[OASIS Issue Tracker] Updated: (WSCALENDAR-276) Line 453-465 - itappears that this language would be better served if the heading 3.1.4appeared before the text that starts on line 453.
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 6 May 2011 13:18:54 -0000
PROPOSED AGENDA - Web Services Calendar (WS-Calendar) TC - 06 May 2011
From
"Gershon Janssen" <gershon@qroot.com> on 6 May 2011 12:52:01 -0000
CalWS SOAP material
From
Mike Douglass <douglm@rpi.edu> on 6 May 2011 04:24:21 -0000
[OASIS Issue Tracker] Commented: (WSCALENDAR-412) Line 311 -Parameters are not discussed
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 5 May 2011 23:06:54 -0000
[OASIS Issue Tracker] Commented: (WSCALENDAR-414) Line 2676 -Actionable services require Bound Intervals as part of a Bound Sequence.Services may Intervalsarenot bound for informational or negotiationpurposes.Some of these are modeled an constraints in the UML models thathave been produced separately
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 5 May 2011 12:56:54 -0000
[OASIS Issue Tracker] Updated: (WSCALENDAR-263) Line 2657-2661 -this text appears to align with item #4 in the bulleted list in 5.2 (line2624) yet has no heading - add heading for this set of language: 5.2.4Covarying Attributes
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 4 May 2011 18:50:54 -0000
[OASIS Issue Tracker] Updated: (WSCALENDAR-263) Line 2657-2661 -this text appears to align with item #4 in the bulleted list in 5.2 (line2624) yet has no heading - add heading for this set of language: 5.2.4Covarying Attributes
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 4 May 2011 18:46:55 -0000
Cleaning up of Action Items
From
"Toby Considine" <Toby.Considine@gmail.com> on 4 May 2011 15:18:48 -0000
Short Fuse - Sub-second time reporting
From
"Toby Considine" <Toby.Considine@gmail.com> on 4 May 2011 14:24:13 -0000
For those who have not seen the Availability update
From
"Toby Considine" <Toby.Considine@gmail.com> on 4 May 2011 02:04:30 -0000
[OASIS Issue Tracker] Created: (WSCALENDAR-420) Line 2678 -"Intervals SHALL NOT include an END time."
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 3 May 2011 02:41:13 -0000
[OASIS Issue Tracker] Created: (WSCALENDAR-419) Line 2688 - Section5.3 "still to come". Missing section in standard document.
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 3 May 2011 02:41:04 -0000
[OASIS Issue Tracker] Created: (WSCALENDAR-418)iCalendar-wscal-extensions - Gluons and Intervals are recursive
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 3 May 2011 02:40:54 -0000
[OASIS Issue Tracker] Created: (WSCALENDAR-417)iCalendar-valtypes.xsd
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 3 May 2011 02:39:14 -0000
[OASIS Issue Tracker] Created: (WSCALENDAR-416) Lines 902, 1026 -Example composition
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 3 May 2011 02:39:04 -0000
[OASIS Issue Tracker] Created: (WSCALENDAR-415)iCalendar-valtypes.xsd and others.
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 3 May 2011 02:38:55 -0000
[OASIS Issue Tracker] Created: (WSCALENDAR-414) Line 2676 -Actionable services require Bound Intervals as part of a Bound Sequence.Services may Intervalsarenot bound for informational or negotiationpurposes.Some of these are modeled an constraints in the UML models thathave been produced separately
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 3 May 2011 02:36:55 -0000
[OASIS Issue Tracker] Created: (WSCALENDAR-413) Line 143 -Namespaces used in this specification
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 3 May 2011 02:33:13 -0000
[OASIS Issue Tracker] Created: (WSCALENDAR-412) Line 311 -Parameters are not discussed
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 3 May 2011 02:33:04 -0000
[OASIS Issue Tracker] Created: (WSCALENDAR-411) Support forrandomized intervals is desirable in many applications. Suggest adding oneor more randomization parameter types. Should be applicable to start, end,or duration.
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 3 May 2011 02:32:54 -0000
[OASIS Issue Tracker] Updated: (WSCALENDAR-344) Table 3-2 isTemporal Relationship/Short Form/ Definitioin/Example - is this becausethese are DEFINED in WS-Calendar rather than USED?
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 1 May 2011 22:30:53 -0000
[OASIS Issue Tracker] Updated: (WSCALENDAR-343) Table 3-1 headingsare Elements/Use/Use in WS-Calendar. Isn't this the WS-Calendar draftstandard?
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 1 May 2011 22:28:53 -0000
[OASIS Issue Tracker] Updated: (WSCALENDAR-361) Line 881 - The"optionality" of dtEnd and duration is not clearly defined
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 1 May 2011 22:27:28 -0000
[OASIS Issue Tracker] Updated: (WSCALENDAR-368) Line 1020 - Why is"Schedules" plural? You use "schedule" in other places. Is this the name ofthe attribute? Rather it's the description of a collection ofattributes/elements.
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 1 May 2011 22:27:19 -0000
[OASIS Issue Tracker] Updated: (WSCALENDAR-369) Line 1646 -timeStampRealm - do you really mean "A set of points ..."? A set oftimestamps? A set of locations?
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 1 May 2011 22:27:10 -0000
[OASIS Issue Tracker] Updated: (WSCALENDAR-371) Line 1646 - Thediscussion of "components" at "the realm border" and "overwrite withoutnotice" seems out of place in an information model.
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 1 May 2011 22:27:03 -0000
[OASIS Issue Tracker] Updated: (WSCALENDAR-402) Line 354-356 - Wehave Intervals, now we have Time Segments? I don't find a definition, andit seems very similar.
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 1 May 2011 22:26:53 -0000
[OASIS Issue Tracker] Updated: (WSCALENDAR-393) Line 180 - ForGluon add in definition a footnote "Sometimes referred to as a CalendarGluon". Or correct use of "Calendar Gluon" in the rest of the document to"Gluon" [preferred].
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 1 May 2011 22:25:20 -0000
[OASIS Issue Tracker] Updated: (WSCALENDAR-394) Line 205 - Comparethis first paragraph with e.g. line 43 which talks about what the intentwas; this paragraph is in better voice describing how the work wasproduced.
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 1 May 2011 22:25:11 -0000
[OASIS Issue Tracker] Updated: (WSCALENDAR-395) Line 223 - Thesection title again may lead to confusion between whether this is aninformation model or a service definition. it is the former; and timesemantics are not critical to JUST WS-Calendar. reconsider the focus andmessage of this paragraph
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 1 May 2011 22:25:02 -0000
[OASIS Issue Tracker] Updated: (WSCALENDAR-408) Line 1321 - Why is"Service Advertisements" in the heading? This is more than just "serviceadv" - should this be "describing" or "managing" "start times"?
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 1 May 2011 22:24:53 -0000
[OASIS Issue Tracker] Updated: (WSCALENDAR-397) Line 253 "start ata particular instant of time UTC" does not read well. Where is a definitionof the acronym UTC? Starting with what is UTC (a single sentence) wouldmake the rest of this section more clear. Is there a normative ref orinformative ref?
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 1 May 2011 22:22:54 -0000
[OASIS Issue Tracker] Commented: (WSCALENDAR-306) Text andReference Issues PR02
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 1 May 2011 22:21:01 -0000
[OASIS Issue Tracker] Updated: (WSCALENDAR-408) Line 1321 - Why is"Service Advertisements" in the heading? This is more than just "serviceadv" - should this be "describing" or "managing" "start times"?
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 1 May 2011 19:58:43 -0000
[OASIS Issue Tracker] Updated: (WSCALENDAR-409) On 1322, youusually write "start date and time". On 1323 "start-times" is hyphenated,but not elsewhere
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 1 May 2011 19:58:34 -0000
[OASIS Issue Tracker] Updated: (WSCALENDAR-408) Line 1321 - Why is"Service Advertisements" in the heading? This is more than just "serviceadv" - should this be "describing" or "managing" "start times"?
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 1 May 2011 19:58:24 -0000
[OASIS Issue Tracker] Updated: (WSCALENDAR-407) Line 370 - Thissentence conflates WS-Calendar, iCalendar, xCal, AND talks about aWS-Calendar MESSAGE. This is an INFORMATION MODEL. Fix this sentence.
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 1 May 2011 19:58:14 -0000
[OASIS Issue Tracker] Updated: (WSCALENDAR-406) Line 369 - "Linkedto a specific date and time" should be "Bound to a specific [date and]time" The word "tied" could be used, but you've already defined Bound
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 1 May 2011 19:58:05 -0000
[OASIS Issue Tracker] Updated: (WSCALENDAR-405) Line 362 - AnInterval is NOT a "unit of service delivery." It's a span of time. Thedescription of "bound to time" should reference "Bound" in table 1-6, andshould reference those Semantics Decribing Intervals"
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 1 May 2011 19:57:53 -0000
[OASIS Issue Tracker] Updated: (WSCALENDAR-403) Line 354-356 -Change "are a critical component of service alignment using WS-Calendar" to"are a critical way to describe service coordination."
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 1 May 2011 19:56:11 -0000
[OASIS Issue Tracker] Updated: (WSCALENDAR-403) Line 354-356 -Change "are a critical component of service alignment using WS-Calendar" to"are a critical way to describe service coordination."
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 1 May 2011 19:56:01 -0000
[OASIS Issue Tracker] Updated: (WSCALENDAR-404) Line 354-356 - Thefinal sentence is incomprehensible as written. And it uses "time segment"which was capitalized in the first sentence. And how are "terms about time"contained "within a particular time segment"?!
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 1 May 2011 19:55:52 -0000
[OASIS Issue Tracker] Updated: (WSCALENDAR-403) Line 354-356 -Change "are a critical component of service alignment using WS-Calendar" to"are a critical way to describe service coordination."
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 1 May 2011 19:54:31 -0000
[OASIS Issue Tracker] Updated: (WSCALENDAR-401) Line 344 - Thisdiscussion is weakened by the lack of either italics or quotation marksaround the strings such as "1M"
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 1 May 2011 19:54:22 -0000
[OASIS Issue Tracker] Updated: (WSCALENDAR-400) All: Ensure thatdefined or called out terms (e.g. Duration, Schedule, ...) are uniformlycapitalized and that non-defined terms are not.
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 1 May 2011 19:54:13 -0000
[OASIS Issue Tracker] Updated: (WSCALENDAR-399) Line 343 -"granularity" is not title case; capitalize.
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 1 May 2011 19:54:01 -0000
[OASIS Issue Tracker] Updated: (WSCALENDAR-398) Line 303 -"Duration" was defined on line 180, and should be capitalized. "schedule"is not defined and should be (and might be as "Schedules" on line 1020)."time" is not defined and probably shouldn't be.
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 1 May 2011 19:53:52 -0000
[OASIS Issue Tracker] Updated: (WSCALENDAR-396) line 234 - Footnote6 should have an informative reference [SOA-RM] rather than the "...foundin the normative references..." wording. Add [SOA-RM] reference on line227.
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 1 May 2011 19:51:52 -0000
[OASIS Issue Tracker] Updated: (WSCALENDAR-392) Line 180 - There isno normative reference to which [XCAL] is connected. Perhaps "xCAL Draft"is what's meant?
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 1 May 2011 19:50:33 -0000
[OASIS Issue Tracker] Updated: (WSCALENDAR-391) Line 180 -Capitalization is variable, look at VTODO and vtodo in the first two lines.
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 1 May 2011 19:50:24 -0000
[OASIS Issue Tracker] Updated: (WSCALENDAR-390) Line 147 - Replace"An ancillary..." with "An additional..." or "Another...". (mildpreference)
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 1 May 2011 19:50:15 -0000
[OASIS Issue Tracker] Updated: (WSCALENDAR-389) Line 124 - Ibelieve that this should be [NAESB_PAP04] and reference both the first andsecond release.
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 1 May 2011 19:50:05 -0000
[OASIS Issue Tracker] Updated: (WSCALENDAR-388) Line 119 - Thereference should be something like [NIST Framework] - the title has beenturned into a reference shorthand by bolding it. Other places this happenedis on lines 59, 105 (should be [xCal Draft]), 119, 124, 131,, and maybe136.
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 1 May 2011 19:49:56 -0000
[OASIS Issue Tracker] Updated: (WSCALENDAR-388) Line 119 - Thereference should be something like [NIST Framework] - the title has beenturned into a reference shorthand by bolding it. Other places this happenedis on lines 59, 105 (should be [xCal Draft]), 119, 124, 131,, and maybe136.
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 1 May 2011 19:49:47 -0000
[OASIS Issue Tracker] Updated: (WSCALENDAR-387) Line 105 - Is the"Draft xCal" superseded by the contributions and the work in the schemasthat are part of this work product? Reword.
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 1 May 2011 19:49:38 -0000
[OASIS Issue Tracker] Updated: (WSCALENDAR-387) Line 105 - Is the"Draft xCal" superseded by the contributions and the work in the schemasthat are part of this work product? Reword.
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 1 May 2011 19:49:29 -0000
[OASIS Issue Tracker] Updated: (WSCALENDAR-386) Line 59 - IsCalendar Resource Schema truly a normative reference? Where is it cited orused?
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 1 May 2011 19:49:21 -0000
[OASIS Issue Tracker] Updated: (WSCALENDAR-386) Line 59 - IsCalendar Resource Schema truly a normative reference? Where is it cited orused?
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 1 May 2011 19:49:12 -0000
[OASIS Issue Tracker] Updated: (WSCALENDAR-383) Line 34 - there isno reference for [EITC] and [EMIX]; these should be non-normativereferences. Likewise EDXL and oBIX on lines 35-36
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 1 May 2011 19:49:03 -0000
[OASIS Issue Tracker] Updated: (WSCALENDAR-383) Line 34 - there isno reference for [EITC] and [EMIX]; these should be non-normativereferences. Likewise EDXL and oBIX on lines 35-36
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 1 May 2011 19:48:54 -0000
[OASIS Issue Tracker] Updated: (WSCALENDAR-381) Line 93 - Can youhave a normative reference to a non-normative document? Date also seemsoff.
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 1 May 2011 19:47:20 -0000
[OASIS Issue Tracker] Updated: (WSCALENDAR-381) Line 93 - Can youhave a normative reference to a non-normative document? Date also seemsoff.
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 1 May 2011 19:47:12 -0000
[OASIS Issue Tracker] Updated: (WSCALENDAR-380) Why are therenormative references to WS-Management, WS-Security, DP-WS, XRD, and othersincluding e.g. lines 71, 74, and more? If there is no use of something in adocument it seems strange to label it a normative reference.
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 1 May 2011 19:47:03 -0000
[OASIS Issue Tracker] Updated: (WSCALENDAR-380) Why are therenormative references to WS-Management, WS-Security, DP-WS, XRD, and othersincluding e.g. lines 71, 74, and more? If there is no use of something in adocument it seems strange to label it a normative reference.
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 1 May 2011 19:46:55 -0000
[OASIS Issue Tracker] Updated: (WSCALENDAR-388) Line 119 - Thereference should be something like [NIST Framework] - the title has beenturned into a reference shorthand by bolding it. Other places this happenedis on lines 59, 105 (should be [xCal Draft]), 119, 124, 131,, and maybe136.
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 1 May 2011 19:45:02 -0000
[OASIS Issue Tracker] Updated: (WSCALENDAR-387) Line 105 - Is the"Draft xCal" superseded by the contributions and the work in the schemasthat are part of this work product? Reword.
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 1 May 2011 19:44:53 -0000
[OASIS Issue Tracker] Updated: (WSCALENDAR-386) Line 59 - IsCalendar Resource Schema truly a normative reference? Where is it cited orused?
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 1 May 2011 19:43:20 -0000
[OASIS Issue Tracker] Updated: (WSCALENDAR-385) Line 49 - delete"(WS-Calendar)"
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 1 May 2011 19:43:11 -0000
[OASIS Issue Tracker] Updated: (WSCALENDAR-384) Lines 43-48: theintent matters less that what is produced in the document in our hands.
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 1 May 2011 19:43:02 -0000
[OASIS Issue Tracker] Updated: (WSCALENDAR-383) Line 34 - there isno reference for [EITC] and [EMIX]; these should be non-normativereferences. Likewise EDXL and oBIX on lines 35-36
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 1 May 2011 19:42:55 -0000
[OASIS Issue Tracker] Updated: (WSCALENDAR-382) DP-WS has a hyphenon line 24 and not on line 64
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 1 May 2011 19:41:11 -0000
[OASIS Issue Tracker] Updated: (WSCALENDAR-381) Line 93 - Can youhave a normative reference to a non-normative document? Date also seemsoff.
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 1 May 2011 19:41:02 -0000
[OASIS Issue Tracker] Updated: (WSCALENDAR-380) Why are therenormative references to WS-Management, WS-Security, DP-WS, XRD, and othersincluding e.g. lines 71, 74, and more? If there is no use of something in adocument it seems strange to label it a normative reference.
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 1 May 2011 19:40:53 -0000
[OASIS Issue Tracker] Updated: (WSCALENDAR-379) Cover and startingon line 59: The RFCs listed seem to be out of sync (in the normativereferences. Verify that current dates are used; Vavailability has beenrecently updated.
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 1 May 2011 19:38:53 -0000
[OASIS Issue Tracker] Updated: (WSCALENDAR-378) Line 13 - "agent"has many meanings. Perhaps "actor" would be a better choice? Agency is notwhat's suggested here.
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 1 May 2011 19:36:20 -0000
[OASIS Issue Tracker] Updated: (WSCALENDAR-377) Sentence startingline 4: "Agreement on when something should or did occur is fundamental tonegotiating service use."
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 1 May 2011 19:36:11 -0000
[OASIS Issue Tracker] Updated: (WSCALENDAR-376) Lines 1-2 - Theemphasis on Web services seems strange; consider "The information model ofWS-Calendar is intended to be used to define information payloads for Webservices and Service-style interactions [SOA-RM]."
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 1 May 2011 19:36:03 -0000
[OASIS Issue Tracker] Updated: (WSCALENDAR-375) Footnote 3 page 9 -Is OPC UA a trademark? If not, why is it footnoted?
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 1 May 2011 19:35:53 -0000
[OASIS Issue Tracker] Updated: (WSCALENDAR-374) Footnote 2 and 4page 9 Footnote is repeated. Note that only the first use a a registeredtrademark could or should be footnoted.
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 1 May 2011 19:34:10 -0000
[OASIS Issue Tracker] Updated: (WSCALENDAR-373) Section 1 line 2and the rest of the specification: Change "Semantic Model" to "informationmodel" throughout the document
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 1 May 2011 19:34:02 -0000
[OASIS Issue Tracker] Updated: (WSCALENDAR-372) Line 1646 -"Xs:bool" differs how from "xs:bool" and how do they relate to the W3 XMLSchema type "boolean"? Fix
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 1 May 2011 19:33:53 -0000
[OASIS Issue Tracker] Updated: (WSCALENDAR-370) Line 1646 - Should"shall" be "SHALL" in the definition?
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 1 May 2011 19:32:11 -0000
[OASIS Issue Tracker] Updated: (WSCALENDAR-369) Line 1646 -timeStampRealm - do you really mean "A set of points ..."? A set oftimestamps? A set of locations?
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 1 May 2011 19:32:03 -0000
[OASIS Issue Tracker] Updated: (WSCALENDAR-367) Line 898 -Typographically distinguish e.g. 15M, 30M, etc, as suggested elsewhere. Ifthese are strings, put in italic or bold, but be consistent through thedocument.
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 1 May 2011 19:31:55 -0000
[OASIS Issue Tracker] Updated: (WSCALENDAR-366) Line 869 -Granularity is also on line 718; needs to be related and explain whydifferent (if it is)
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 1 May 2011 19:30:04 -0000
[OASIS Issue Tracker] Updated: (WSCALENDAR-365) Line 887 - why is"availability" different from "vavailability"?
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 1 May 2011 19:29:56 -0000
[OASIS Issue Tracker] Updated: (WSCALENDAR-359) Line 858 -WsCalendar Attach the use is "WSCalendar:Attachment" this is very unclear."The Attach element contains..." and change "incorporating specifications"to "conforming specifications" [ref to section 5.4]
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 1 May 2011 19:27:52 -0000
[OASIS Issue Tracker] Updated: (WSCALENDAR-358) Line 858 -"Designated Interval" text should reference line 196
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 1 May 2011 19:25:44 -0000
[OASIS Issue Tracker] Updated: (WSCALENDAR-355) Line 718 -Capitalization of first column is not consistent with other tables
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 1 May 2011 19:25:35 -0000
[OASIS Issue Tracker] Updated: (WSCALENDAR-354) Line 718 -Reference to "service" seems out of place; consider "operation" as analternative. On line 712, "service coordination between systems' reallyshould read "action coordination between/across systems" I think.
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 1 May 2011 19:25:26 -0000
[OASIS Issue Tracker] Updated: (WSCALENDAR-352) Line 462 -Reference table 1-3 where "Sequence" is defined.
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 1 May 2011 19:25:17 -0000
[OASIS Issue Tracker] Updated: (WSCALENDAR-351) Line 395 - Thecapitalization seems almost random across the tables
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 1 May 2011 19:25:04 -0000
[OASIS Issue Tracker] Updated: (WSCALENDAR-349) Line 368 - Why is"attach" not capitalized? that doesn't fit the style of some tables (butsee Table 3-2) "attach" mixes "attach" and "Attach". Are they different? Iscase important in these tables and the schemas? XML is case sensitive, andthis confuses
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 1 May 2011 19:24:55 -0000
[OASIS Issue Tracker] Updated: (WSCALENDAR-345) Table 3-3 ? thereIS NO TABLE 3-3.
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 1 May 2011 19:22:54 -0000
[OASIS Issue Tracker] Created: (WSCALENDAR-410) Third Collector forpurely mechanical edits
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 1 May 2011 19:20:54 -0000
[OASIS Issue Tracker] Created: (WSCALENDAR-409) On 1322, youusually write "start date and time". On 1323 "start-times" is hyphenated,but not elsewhere
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 1 May 2011 07:23:11 -0000
[OASIS Issue Tracker] Created: (WSCALENDAR-408) Line 1321 - Why is"Service Advertisements" in the heading? This is more than just "serviceadv" - should this be "describing" or "managing" "start times"?
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 1 May 2011 07:23:02 -0000
[OASIS Issue Tracker] Created: (WSCALENDAR-407) Line 370 - Thissentence conflates WS-Calendar, iCalendar, xCal, AND talks about aWS-Calendar MESSAGE. This is an INFORMATION MODEL. Fix this sentence.
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 1 May 2011 07:22:53 -0000
[OASIS Issue Tracker] Created: (WSCALENDAR-406) Line 369 - "Linkedto a specific date and time" should be "Bound to a specific [date and]time" The word "tied" could be used, but you've already defined Bound
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 1 May 2011 07:21:12 -0000
[OASIS Issue Tracker] Created: (WSCALENDAR-405) Line 362 - AnInterval is NOT a "unit of service delivery." It's a span of time. Thedescription of "bound to time" should reference "Bound" in table 1-6, andshould reference those Semantics Decribing Intervals"
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 1 May 2011 07:21:03 -0000
[OASIS Issue Tracker] Created: (WSCALENDAR-404) Line 354-356 - Thefinal sentence is incomprehensible as written. And it uses "time segment"which was capitalized in the first sentence. And how are "terms about time"contained "within a particular time segment"?!
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 1 May 2011 07:20:55 -0000
[OASIS Issue Tracker] Created: (WSCALENDAR-403) Line 354-356 -Change "are a critical component of service alignment using WS-Calendar" to"are a critical way to describe service coordination."
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 1 May 2011 07:19:03 -0000
[OASIS Issue Tracker] Created: (WSCALENDAR-402) Line 354-356 - Wehave Intervals, now we have Time Segments? I don't find a definition, andit seems very similar.
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 1 May 2011 07:18:54 -0000
[OASIS Issue Tracker] Created: (WSCALENDAR-401) Line 344 - Thisdiscussion is weakened by the lack of either italics or quotation marksaround the strings such as "1M"
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 1 May 2011 07:16:53 -0000
[OASIS Issue Tracker] Created: (WSCALENDAR-400) All: Ensure thatdefined or called out terms (e.g. Duration, Schedule, ...) are uniformlycapitalized and that non-defined terms are not.
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 1 May 2011 07:15:38 -0000
[OASIS Issue Tracker] Created: (WSCALENDAR-399) Line 343 -"granularity" is not title case; capitalize.
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 1 May 2011 07:15:29 -0000
[OASIS Issue Tracker] Created: (WSCALENDAR-398) Line 303 -"Duration" was defined on line 180, and should be capitalized. "schedule"is not defined and should be (and might be as "Schedules" on line 1020)."time" is not defined and probably shouldn't be.
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 1 May 2011 07:15:20 -0000
[OASIS Issue Tracker] Created: (WSCALENDAR-397) Line 253 "start ata particular instant of time UTC" does not read well. Where is a definitionof the acronym UTC? Starting with what is UTC (a single sentence) wouldmake the rest of this section more clear. Is there a normative ref orinformative ref?
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 1 May 2011 07:15:06 -0000
[OASIS Issue Tracker] Created: (WSCALENDAR-396) line 234 - Footnote6 should have an informative reference [SOA-RM] rather than the "...foundin the normative references..." wording. Add [SOA-RM] reference on line227.
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 1 May 2011 07:14:57 -0000
[OASIS Issue Tracker] Created: (WSCALENDAR-395) Line 223 - Thesection title again may lead to confusion between whether this is aninformation model or a service definition. it is the former; and timesemantics are not critical to JUST WS-Calendar. reconsider the focus andmessage of this paragraph
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 1 May 2011 07:13:04 -0000
[OASIS Issue Tracker] Created: (WSCALENDAR-394) Line 205 - Comparethis first paragraph with e.g. line 43 which talks about what the intentwas; this paragraph is in better voice describing how the work wasproduced.
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 1 May 2011 07:12:54 -0000
[OASIS Issue Tracker] Created: (WSCALENDAR-393) Line 180 - ForGluon add in definition a footnote "Sometimes referred to as a CalendarGluon". Or correct use of "Calendar Gluon" in the rest of the document to"Gluon" [preferred].
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 1 May 2011 07:10:58 -0000
[OASIS Issue Tracker] Created: (WSCALENDAR-392) Line 180 - There isno normative reference to which [XCAL] is connected. Perhaps "xCAL Draft"is what's meant?
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 1 May 2011 07:09:22 -0000
[OASIS Issue Tracker] Created: (WSCALENDAR-391) Line 180 -Capitalization is variable, look at VTODO and vtodo in the first two lines.
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 1 May 2011 07:09:12 -0000
[OASIS Issue Tracker] Created: (WSCALENDAR-390) Line 147 - Replace"An ancillary..." with "An additional..." or "Another...". (mildpreference)
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 1 May 2011 07:09:03 -0000
[OASIS Issue Tracker] Created: (WSCALENDAR-389) Line 124 - Ibelieve that this should be [NAESB_PAP04] and reference both the first andsecond release.
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 1 May 2011 07:08:54 -0000
[OASIS Issue Tracker] Created: (WSCALENDAR-388) Line 119 - Thereference should be something like [NIST Framework] - the title has beenturned into a reference shorthand by bolding it. Other places this happenedis on lines 59, 105 (should be [xCal Draft]), 119, 124, 131,, and maybe136.
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 1 May 2011 07:06:57 -0000
[OASIS Issue Tracker] Created: (WSCALENDAR-387) Line 105 - Is the"Draft xCal" superseded by the contributions and the work in the schemasthat are part of this work product? Reword.
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 1 May 2011 07:05:13 -0000
[OASIS Issue Tracker] Created: (WSCALENDAR-386) Line 59 - IsCalendar Resource Schema truly a normative reference? Where is it cited orused?
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 1 May 2011 07:05:04 -0000
[OASIS Issue Tracker] Created: (WSCALENDAR-385) Line 49 - delete"(WS-Calendar)"
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 1 May 2011 07:04:54 -0000
[OASIS Issue Tracker] Created: (WSCALENDAR-384) Lines 43-48: theintent matters less that what is produced in the document in our hands.
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 1 May 2011 07:03:12 -0000
[OASIS Issue Tracker] Created: (WSCALENDAR-383) Line 34 - there isno reference for [EITC] and [EMIX]; these should be non-normativereferences. Likewise EDXL and oBIX on lines 35-36
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 1 May 2011 07:03:03 -0000
[OASIS Issue Tracker] Created: (WSCALENDAR-382) DP-WS has a hyphenon line 24 and not on line 64
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 1 May 2011 07:02:54 -0000
[OASIS Issue Tracker] Created: (WSCALENDAR-381) Line 93 - Can youhave a normative reference to a non-normative document? Date also seemsoff.
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 1 May 2011 07:01:20 -0000
[OASIS Issue Tracker] Created: (WSCALENDAR-380) Why are therenormative references to WS-Management, WS-Security, DP-WS, XRD, and othersincluding e.g. lines 71, 74, and more? If there is no use of something in adocument it seems strange to label it a normative reference.
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 1 May 2011 07:01:11 -0000
[OASIS Issue Tracker] Created: (WSCALENDAR-379) Cover and startingon line 59: The RFCs listed seem to be out of sync (in the normativereferences. Verify that current dates are used; Vavailability has beenrecently updated.
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 1 May 2011 07:01:02 -0000
[OASIS Issue Tracker] Created: (WSCALENDAR-378) Line 13 - "agent"has many meanings. Perhaps "actor" would be a better choice? Agency is notwhat's suggested here.
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 1 May 2011 07:00:53 -0000
[OASIS Issue Tracker] Created: (WSCALENDAR-377) Sentence startingline 4: "Agreement on when something should or did occur is fundamental tonegotiating service use."
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 1 May 2011 06:59:19 -0000
[OASIS Issue Tracker] Created: (WSCALENDAR-376) Lines 1-2 - Theemphasis on Web services seems strange; consider "The information model ofWS-Calendar is intended to be used to define information payloads for Webservices and Service-style interactions [SOA-RM]."
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 1 May 2011 06:59:10 -0000
[OASIS Issue Tracker] Created: (WSCALENDAR-375) Footnote 3 page 9 -Is OPC UA a trademark? If not, why is it footnoted?
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 1 May 2011 06:59:02 -0000
[OASIS Issue Tracker] Created: (WSCALENDAR-374) Footnote 2 and 4page 9 Footnote is repeated. Note that only the first use a a registeredtrademark could or should be footnoted.
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 1 May 2011 06:58:53 -0000
[OASIS Issue Tracker] Created: (WSCALENDAR-373) Section 1 line 2and the rest of the specification: Change "Semantic Model" to "informationmodel" throughout the document
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 1 May 2011 06:57:05 -0000
[OASIS Issue Tracker] Created: (WSCALENDAR-372) Line 1646 -"Xs:bool" differs how from "xs:bool" and how do they relate to the W3 XMLSchema type "boolean"? Fix
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 1 May 2011 06:56:53 -0000
[OASIS Issue Tracker] Created: (WSCALENDAR-371) Line 1646 - Thediscussion of "components" at "the realm border" and "overwrite withoutnotice" seems out of place in an information model.
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 1 May 2011 06:55:04 -0000
[OASIS Issue Tracker] Created: (WSCALENDAR-370) Line 1646 - Should"shall" be "SHALL" in the definition?
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 1 May 2011 06:54:54 -0000
[OASIS Issue Tracker] Created: (WSCALENDAR-369) Line 1646 -timeStampRealm - do you really mean "A set of points ..."? A set oftimestamps? A set of locations?
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 1 May 2011 06:53:12 -0000
[OASIS Issue Tracker] Created: (WSCALENDAR-368) Line 1020 - Why is"Schedules" plural? You use "schedule" in other places. Is this the name ofthe attribute? Rather it's the description of a collection ofattributes/elements.
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 1 May 2011 06:53:03 -0000
[OASIS Issue Tracker] Created: (WSCALENDAR-367) Line 898 -Typographically distinguish e.g. 15M, 30M, etc, as suggested elsewhere. Ifthese are strings, put in italic or bold, but be consistent through thedocument.
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 1 May 2011 06:52:54 -0000
[OASIS Issue Tracker] Created: (WSCALENDAR-366) Line 869 -Granularity is also on line 718; needs to be related and explain whydifferent (if it is)
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 1 May 2011 06:51:04 -0000
[OASIS Issue Tracker] Created: (WSCALENDAR-365) Line 887 - why is"availability" different from "vavailability"?
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 1 May 2011 06:50:55 -0000
[OASIS Issue Tracker] Created: (WSCALENDAR-364) Line 887 - Uid,Summary, dtStart, dtEnd, duration, and Granularity
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 1 May 2011 06:49:11 -0000
[OASIS Issue Tracker] Created: (WSCALENDAR-363) Line 887 - Therelationship of tables 3-7 and 3-8 is not clear.
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 1 May 2011 06:49:03 -0000
[OASIS Issue Tracker] Created: (WSCALENDAR-362) Line 877 - Vavailability is a 3 year old proposal; there's an update, but are youdefining what it is in this document?
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 1 May 2011 06:48:54 -0000
[OASIS Issue Tracker] Created: (WSCALENDAR-361) Line 881 - The"optionality" of dtEnd and duration is not clearly defined
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 1 May 2011 06:45:04 -0000
[OASIS Issue Tracker] Created: (WSCALENDAR-360) Line 881 - "use" of"Summary" is not "text" - that's its type. The "Discussion" belongs in use.or change the column heading "Use" to "Type" (but stay consistent withother tables).
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 1 May 2011 06:44:55 -0000
[OASIS Issue Tracker] Created: (WSCALENDAR-359) Line 858 -WsCalendar Attach the use is "WSCalendar:Attachment" this is very unclear."The Attach element contains..." and change "incorporating specifications"to "conforming specifications" [ref to section 5.4]
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 1 May 2011 06:43:19 -0000
[OASIS Issue Tracker] Created: (WSCALENDAR-358) Line 858 -"Designated Interval" text should reference line 196
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 1 May 2011 06:43:10 -0000
[OASIS Issue Tracker] Created: (WSCALENDAR-357) Line 858 - dtEndsays "SCHEDULED completion time..." is this implied or computed orexpressed? dtStart simply says "Start time"
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 1 May 2011 06:43:02 -0000
[OASIS Issue Tracker] Created: (WSCALENDAR-356) Line 858 - dtEnd isnot listed and optional, as are dtStart and duration (DtStart andDuration?)
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 1 May 2011 06:42:54 -0000
[OASIS Issue Tracker] Created: (WSCALENDAR-355) Line 718 -Capitalization of first column is not consistent with other tables
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 1 May 2011 06:40:54 -0000
[OASIS Issue Tracker] Created: (WSCALENDAR-354) Line 718 -Reference to "service" seems out of place; consider "operation" as analternative. On line 712, "service coordination between systems' reallyshould read "action coordination between/across systems" I think.
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 1 May 2011 06:39:19 -0000
[OASIS Issue Tracker] Created: (WSCALENDAR-353) Line 464 - Therelationship may not be determinable if the reltype is inherited along withduration and dtstart until the sequence is Bound.
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 1 May 2011 06:39:11 -0000
[OASIS Issue Tracker] Created: (WSCALENDAR-352) Line 462 -Reference table 1-3 where "Sequence" is defined.
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 1 May 2011 06:39:02 -0000
[OASIS Issue Tracker] Created: (WSCALENDAR-351) Line 395 - Thecapitalization seems almost random across the tables
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 1 May 2011 06:38:53 -0000
[OASIS Issue Tracker] Created: (WSCALENDAR-350) Line 368 -Elsewhere it's recommended that intervals have DtStart and Duration (eitherof which can be filled in through eg inheritance), but we see later an oddblend (line 858 adds DtEnd to the mix). This needs to be clear andconsistent across the doc.
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 1 May 2011 06:37:11 -0000
[OASIS Issue Tracker] Created: (WSCALENDAR-349) Line 368 - Why is"attach" not capitalized? that doesn't fit the style of some tables (butsee Table 3-2) "attach" mixes "attach" and "Attach". Are they different? Iscase important in these tables and the schemas? XML is case sensitive, andthis confuses
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 1 May 2011 06:37:02 -0000
[OASIS Issue Tracker] Created: (WSCALENDAR-348) Line 368 - BothDtStart and Duration are "optional". What precisely does that mean? Thatneither need to be present? we find later that these values can beinherited from a gluon, but at this point "optional" seems to mean "novalue is required"
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 1 May 2011 06:36:55 -0000
[OASIS Issue Tracker] Created: (WSCALENDAR-347) Section 3 - Tableheadings change and confuse
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 1 May 2011 06:34:53 -0000
[OASIS Issue Tracker] Created: (WSCALENDAR-346) Table 3-4 isAttachment Element/Use/Discussion, and the discussion for Text seems out ofplace.
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 1 May 2011 06:33:16 -0000
[OASIS Issue Tracker] Created: (WSCALENDAR-345) Table 3-3 ? thereIS NO TABLE 3-3.
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 1 May 2011 06:33:02 -0000
[OASIS Issue Tracker] Created: (WSCALENDAR-344) Table 3-2 isTemporal Relationship/Short Form/ Definitioin/Example - is this becausethese are DEFINED in WS-Calendar rather than USED?
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 1 May 2011 06:32:54 -0000
[OASIS Issue Tracker] Created: (WSCALENDAR-343) Table 3-1 headingsare Elements/Use/Use in WS-Calendar. Isn't this the WS-Calendar draftstandard?
From
OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> on 1 May 2011 06:30:53 -0000
Mail converted by
MHonArc
2.5.0b2