Two #WS-Calendar public reviews – Minimal PIM-Conformant Schema and Schedule Signals and Streams – end July 30th
The OASIS Web Services Calendar (WS-Calendar) TC members [1] have produced two updated Committee Specification Drafts (CSDs) and submitted them for 30-day public reviews:
WS-Calendar Minimal PIM-Conformant Schema Version 1.0
Committee Specification Draft 02 / Public Review Draft 02
03 June 2016
and
Schedule Signals and Streams Version 1.0
Committee Specification Draft 03 / Public Review Draft 03
03 June 2016
Specification Overviews:
The WS-Calendar Minimal PIM-Conformant Schema is a schema that conforms with the WS-Calendar Platform Independent Model (PIM). The schema is minimal to optimize 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 schema. 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.
–
There is a common need to communicate information linked to repetitive intervals of time, for history, for telemetry, for projections, for bids. Much of the information in each interval can be inferred from the surrounding intervals. Schedule Signals and Streams Version 1.0 defines a normative structure for conveying time-series of information that is conformant with WS-Calendar. We term these conveyances “Streams”.
About the TC:
The OASIS Web Services Calendar (WS-Calendar) Technical Committee was chartered to adapt the existing specifications for calendaring and apply them to develop a standard for how schedule and event information is passed between and within services. The standard should adopt the semantics and vocabulary of iCalendar for application to the completion of web service contracts.
Public Review Period:
The public review starts 01 July 2016 at 00:00 UTC and ends 30 July 2016 at 11:59 UTC. The specifications were previously submitted for public review [2]. These 15-day reviews are limited in scope to changes made from the previous review. Changes are highlighted in the red-lined diff files [3].
This is an open invitation to comment. OASIS solicits feedback from potential users, developers and others, whether OASIS members or not, for the sake of improving the interoperability and quality of its technical work.
Reviewers may provide comments directly from the comment-tag version of document. The files
ws-calendar-min-v1.0-csprd02-COMMENT-TAGS.html
and
streams-v1.0-csprd03-COMMENT-TAGS.html
contain the HTML versions of the drafts with a “[comment?]” link next to each section heading. Clicking on this link will launch your email application and begin a message to ws-calendar-comment@lists.oasis-open.org with the specific section number and title in the subject line. Simply enter your comment and click send.
Note that you must be subscribed to the comment mailing list before sending feedback. Instructions on how to subscribe can be found at https://www.oasis-open.org/committees/comments/index.php?wg_abbrev=ws-calendar.
URIs:
The prose specification document and related files are available here:
– WS-Calendar Minimal PIM-Conformant Schema Version 1.0
PDF(Authoritative):
http://docs.oasis-open.org/ws-calendar/ws-calendar-min/v1.0/csprd02/ws-calendar-min-v1.0-csprd02.pdf
HTML with in-line comment tags:
http://docs.oasis-open.org/ws-calendar/ws-calendar-min/v1.0/csprd02/ws-calendar-min-v1.0-csprd02-COMMENT-TAGS.html
Editable source:
http://docs.oasis-open.org/ws-calendar/ws-calendar-min/v1.0/csprd02/ws-calendar-min-v1.0-csprd02.docx
XML schema:
http://docs.oasis-open.org/ws-calendar/ws-calendar-min/v1.0/csprd02/schema/ws-calendar-min-v1.0.xsd
– Schedule Signals and Streams Version 1.0
PDF(Authoritative):
http://docs.oasis-open.org/ws-calendar/streams/v1.0/csprd03/streams-v1.0-csprd03.pdf
HTML:
http://docs.oasis-open.org/ws-calendar/streams/v1.0/csprd03/streams-v1.0-csprd03.html
HTML with in-line comment tags:
http://docs.oasis-open.org/ws-calendar/streams/v1.0/csprd03/streams-v1.0-csprd03-COMMENT-TAGS.html
Editable source:
http://docs.oasis-open.org/ws-calendar/streams/v1.0/csprd03/streams-v1.0-csprd03.doc
XML schema:
http://docs.oasis-open.org/ws-calendar/streams/v1.0/csprd03/xsd/ws-calendar-streams-v1.0.xsd
ZIP distribution files (complete):
For your convenience, OASIS provides a complete package of each prose specification and related files in a ZIP distribution file. You can download the ZIP files here:
http://docs.oasis-open.org/ws-calendar/ws-calendar-min/v1.0/csprd02/ws-calendar-min-v1.0-csprd02.zip
and
http://docs.oasis-open.org/ws-calendar/streams/v1.0/csprd03/streams-v1.0-csprd03.zip
Additional information about this specification and the WS-Calendar TC may be found on the TC’s public home page located at:
http://www.oasis-open.org/committees/ws-calendar/
Comments may be submitted to the TC by any person through the use of the OASIS TC Comment Facility which can be accessed via the button labeled “Send A Comment” at the top of the TC public home page, or directly at:
http://www.oasis-open.org/committees/comments/form.php?wg_abbrev=ws-calendar
Feedback submitted by TC non-members for this work and for other work of this TC is publicly archived and can be viewed at:
http://lists.oasis-open.org/archives/ws-calendar-comment/
All comments submitted to OASIS are subject to the OASIS Feedback License, which ensures that the feedback you provide carries the same obligations at least as the obligations of the TC members. In connection with this public review of ‘WS-Calendar Minimal PIM-Conformant Schema Version 1.0’ and ‘Schedule Signals and Streams Version 1.0’, we call your attention to the OASIS IPR Policy [4] applicable especially [5] to the work of this technical committee. All members of the TC should be familiar with this document, which may create obligations regarding the disclosure and availability of a member’s patent, copyright, trademark and license rights that read on an approved OASIS specification.
OASIS invites any persons who know of any such claims to disclose these if they may be essential to the implementation of the above specification, so that notice of them may be posted to the notice page for this TC’s work.
========== Additional references:
[1] OASIS Web Services Calendar (WS-Calendar) TC
http://www.oasis-open.org/committees/ws-calendar/
[2] Previous public reviews:
– WS-Calendar Minimal PIM-Conformant Schema Version 1.0
— 30-day public review, 20 January 2016:
https://lists.oasis-open.org/archives/members/201601/msg00007.html
– Comment resolution log:
http://docs.oasis-open.org/ws-calendar/ws-calendar-min/v1.0/csprd01/ws-calendar-min-v1.0-csprd01-comment-resolution-log.pdf
– Schedule Signals and Streams Version 1.0
— 30-day public review, 22 January 2013:
https://lists.oasis-open.org/archives/members/201301/msg00014.html
— 15-day public review, 09 July 2013:
https://lists.oasis-open.org/archives/members/201307/msg00005.html
– Comment resolution log:
http://docs.oasis-open.org/ws-calendar/streams/v1.0/csprd02/streams-v1.0-csprd02-comment-resolution-log.pdf
[3] Red-lined DIFF files:
– WS-Calendar Minimal PIM-Conformant Schema Version 1.0:
http://docs.oasis-open.org/ws-calendar/ws-calendar-min/v1.0/csprd02/ws-calendar-min-v1.0-csprd02-DIFF.pdf
– Schedule Signals and Streams Version 1.0:
http://docs.oasis-open.org/ws-calendar/streams/v1.0/csprd03/streams-v1.0-csprd03-DIFF.pdf
[4] http://www.oasis-open.org/policies-guidelines/ipr
[4] http://www.oasis-open.org/committees/ws-calendar/ipr.php
https://www.oasis-open.org/policies-guidelines/ipr#Non-Assertion-Mode
Non-Assertion Mode