Request a first public review for WS-Calendar Minimal PIM-Conformant Schema Version 1.0

Submitted on Tuesday, December 29, 2015 - 15:44
Submitted by user:
Submitted values are:

Your name: Toby Considine
TC name: WS-Calendar
TC email address: ws-calendar@lists.oasis-open.org
This ticket requests: Publish Committee Draft and release for public review
Title: WS-Calendar Minimal PIM-Conformant Schema Version 1.0 WD05
Approval link:
https://www.oasis-open.org/apps/org/workgroup/ws-calendar/download.php/57169/Minutes_WS-Calendar-TC_20151218_Draft.txt
Abstract:
The WS-Calendar MIN is a WS-Calendar conformant schema optimized for use in
machine-to-machine (M2M) schedule negotiations.
iCalendar (RFC5545) and its peer specification XCAL (also in WS-Calendar 1.0)
is
a well-known and long used means to convey schedule-related information.
iCalendar makes extensive use of extension and recursion. The WS-Calendar
Platform Independent Model (PIM) constrains iCalendar and defines a simpler
information model which shares iCalendar semantics and can be used to create
as
the common basis for any number of Platform Specific Models (PSMs).
Because an information model is abstract, it can apply to many transmission
and
serialization schemas. The PIM itself does not include a transmission and
serialization schemas. Through transitive conformance such PSMs themselves
conform to WS-Calendar.
The Minimal PIM-Conformant (MIN) schema defines an XML Schema that conforms
just
with the PIM. MIN can be used by itself or as a seed-schema for other
specifications.
Notification list: Director, The Energy Mashup Lab ; William Cox (Energy
Mashup
Lab) ; Jennifer Worrall ; David Holmberg ; Toby Considine ; Gershon Janssen
(gershon.janssen@gmail.com); Mike Douglass ; steve.ray@sv.cmu.edu; 'Steven
Bushby' ; liana.kiff@honeywell.com; Barry Haaser ; 'Bruce Angelis' ; Sila
Kiliccote
Notes:
I discovered a minor non-substantial editing issue which I request the TC
Admin
assistance on.

Early on, the TC waffled between the "nerdy" Minimal PIM Conformant (artifact
name MPC) or simply MIN, and ended up as the more "marketable" MIN. I noticed
several instances of MPC still un-scrubbed from the document, notably in the
Abstract (who reads the abstract in the TC). It would be a great favor if the
TC
Admins could correct this editorial issue during the publishing process....

The results of this submission may be viewed at:
http://tools.oasis-open.org/issues/browse/TCADMIN