Notes on WS-Calendar PIM WD11
20140731
William Cox
This is a summary of issues that arose in
completing WD11,
and of questions for the TC to guide a minor update for Public
Review.
Citations are to the clean PDF at https://www.oasis-open.org/committees/document.php?document_id=53717&wg_abbrev=ws-calendar.
The
following major issues have been
addressed in WD11; many address Public Review Comments (see
https://issues.oasis-open.org/browse/WSCALENDAR/?selectedTab=com.atlassian.jira.jira-projects-plugin:issues-panel
)
1.
Signed
Duration versus 8601 unsigned
duration
a.
Tolerance
must be unsigned (or conform
to positive only) for clarity
b.
Gap must
be signed (or add a “sign” or
“direction” attribute)
2.
Degenerate
Bound Intervals in two
places
a.
WS-Calendar
1.0 was in defined
components; the PIM is not, so need explicit dtStart &
duration
(Vavailability allows our usual dtStart duration, so that’s
done uniformly)
b.
Two
classes, no inheritance
c.
AvailabilityIntervalType
to flesh out
Vavailability
d.
FreeBusyIntervalType
includes freeBusy
attribute
3.
FreeBusy
missing
a.
Relationship
to rest of PIM is
non-existent
b.
Created a
new enum and classes
4.
Restructured
and rewrote
a.
Non-Normative
architecture gathered in
Section 2
b.
Split
Conformance & Rules into
Conformance, Rules sections
c.
Rewrote to
eliminate normative reference
to WS-Calendar—a PIM shouldn’t normatively reference one of
its PSMs.
d.
Improved
separation of history,
rationale, and normative statements in Section 4 and
elsewhere
e.
Moved “PIM
to WS-Calendar Mapping” to a
non-normative appendix
f.
g.
Other Jira
items
To be addressed:
1.
Some enums have “Enum”
in their name, some don’t
a.
RelationshipType
b.
FreeBusyEnum
c.
TemporalRelationshipType
d.
Propose keeping as-is.
2.
Can’t get the figures
in Appendix C to have C-1,
…, in their names. Global change in Word.
3.
Graphics are more
consistent, probably higher
resolution than necessary—would reduce document size.