OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

emix message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Request for EMIX members to comment on WS-Calendar


I recommend approaching it through the white paper before the spec. The
document talks from the perspective of the schedule, because this is a
schedule spec. With two way relationships in the UML, one can, of course,
grab the spec anywhere and shake it so one's favorite part is on top...

The spec reaches for ways to align service oriented (which means results
oriented rather than process oriented) requests between domains. As such, it
gives examples from all sides, from energy to enterprise to facilities. Just
remember, all examples are about how it *could* be used. Actual use, and
actual conformance, will come from the specifications that build upon it,
including EMIX and Energy Interoperation / OpenADR.

Our current conversations in EMIX have price and product looking like a
gluon, able to exist separately, but also able to associate with and
influence a WS-Calendar sequence. A calendar gluon establishes baseline
which is inherited across a sequence, but allows local (to each interval)
overrides. In EMIX, those inherited but override-able elements might include
Price, Quantity, Duration, et al. The gluon also can set the performance
time / date for the entire sequence, which may be tied to a sequence other
than the "first" interval. This addresses use cases with ramp times, from DR
in commercial buildings to 3 part bids in certain ISO markets under a common
information model.

I emphasize again, this is the schedule; it is not Scheduling. Scheduling is
its own black art, that varies by domain, vendor, and market segment.
WS-Calendar communicates the outcome of scheduling. It could be used to
communicate inputs into scheduling. [I guess, offering DR and buying DR are
all inputs into Scheduling...] WS-Calendar, though makes no statement about
scheduling.

tc




"If something is not worth doing, it`s not worth doing well" - Peter Drucker

Toby Considine
TC9, Inc
TC Chair: oBIX & WS-Calendar
TC Editor: EMIX, EnergyInterop
U.S. National Inst. of Standards and Tech. Smart Grid Architecture Committee

  
Email: Toby.Considine@gmail.com
Phone: (919)619-2104
http://www.tcnine.com/
blog: www.NewDaedalus.com



-----Original Message-----
From: Mary McRae [mailto:mary.mcrae@oasis-open.org] 
Sent: Friday, September 24, 2010 9:13 PM
To: members@lists.oasis-open.org; tc-announce@lists.oasis-open.org
Cc: ws-calendar@lists.oasis-open.org; OASIS TAB
Subject: [ws-calendar] Public Review of WS-Calendar v1.0 and Conceptual
Overview of WS-Calendar

To OASIS members, Public Announce Lists:

The OASIS WS-Calendar TC has recently approved the following specification
as a Committee Draft and approved them for public review:

WS-Calendar Version 1.0
Conceptual Overview of WS-Calendar CD01 - Understanding inheritance using
the semantic elements of web services

The WS-Calendar specification adapts the existing specifications for
calendaring and apply them to a new specification for how schedule and event
information is passed between and within services. The standard adopts the
semantics and vocabulary of iCalendar for application to the completion of
web service contracts. WS Calendar builds on work done and ongoing in The
Calendaring and Scheduling Consortium (CalConnect), which works to increase
interoperation between calendaring systems, and the Internet Engineering
Task Force (IETF). 
 
The specification describes how to specify a sequence of services, how to
schedule them, and how to invoke them. The specification was developed to
support use cases in smart grids and smart energy, but it supports any sort
of coordinated activities between domains. The committee explicitly
considered coordination between energy coordination, enterprise systems,
building systems, and financial markets. The specification also defines an
inheritance approach wherein information common to many time intervals is
specified for an entire sequence, while supporting over-rides within any
time interval. 

The committee is simultaneously releasing white paper for public review. The
white paper provides a conceptual overview of the specification and its use.
The committee recommends those encountering WS-Calendar for the first time
to read the white paper before reviewing the specification. 

The committee anticipates that the primary use for the specifications is
inclusion in other specifications, providing a common mechanism to solve
coordination communications. Technical committees currently planning to
incorporate WS-Calendar include the OASIS Energy Market Information Exchange
TC (EMIX), the OASIS Energy Interoperation TC (EnergyInterop), and the OASIS
Open Building Information Exchange TC (oBIX). 

The committee plans to submit the new semantic elements of Interval and
Sequence, as well as the new inter-object Temporal Relations to the IETF for
inclusion in iCalendar at a later time. 

The public review starts today, 24 September 2010, and ends 23 November
2010. This is an open invitation to comment. We strongly encourage feedback
from potential users, developers and others, whether OASIS members or not,
for the sake of improving the interoperability and quality of OASIS work. We
also welcome interested parties to join the TC as it continues to further
development of its specifications. [or more specific info from TC]. Please
feel free to distribute this announcement within your organization and to
other appropriate mail lists.

More non-normative information about the specification and the technical
committee may be found at the public home page of the TC at [1] below.
Comments may be submitted to the TC by any person through the use of the
OASIS TC Comment Facility which can be located via the button marked "Send A
Comment" at the top of that page, or directly at [2] below.

Submitted comments (for this work as well as other works of that TC) are
publicly archived and can be viewed at [3] below. 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.

The specification document and related files are available here:
WS-Calendar Version 1.0
Editable Source:
http://docs.oasis-open.org/ws-calendar/ws-calendar/v1.0/CD01/ws-calendar-1.0
-spec-cd-01.doc
PDF:
http://docs.oasis-open.org/ws-calendar/ws-calendar/v1.0/CD01/ws-calendar-1.0
-spec-cd-01.pdf
HTML:
http://docs.oasis-open.org/ws-calendar/ws-calendar/v1.0/CD01/ws-calendar-1.0
-spec-cd-01.html
Namespace:
http://docs.oasis-open.org/ns/ws-calendar
EAP:
http://docs.oasis-open.org/ws-calendar/ws-calendar/v1.0/CD01/ws-calendar-v1.
0-cd01-eap-final.EAP

Conceptual Overview of WS-Calendar
Editable Source:
http://docs.oasis-open.org/ws-calendar/ws-calendar/v1.0/CD01/WS-Calendar-Con
ceptual-Overview-CD01.doc
PDF:
http://docs.oasis-open.org/ws-calendar/ws-calendar/v1.0/CD01/WS-Calendar-Con
ceptual-Overview-CD01.pdf
HTML:
http://docs.oasis-open.org/ws-calendar/ws-calendar/v1.0/CD01/WS-Calendar-Con
ceptual-Overview-CD01.html


We also call your attention to the OASIS IPR Policy applicable to the work
of this technical committee, which can be found at [4] below. 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, at
[5] below.

OASIS and the WS-Calendar TC welcome your comments.


Mary P McRae
Director, Standards Development
Technical Committee Administrator
OASIS: Advancing open standards for the information society
email: mary.mcrae@oasis-open.org
web: www.oasis-open.org
twitter: @fiberartisan #oasisopen
phone: 1.603.232.9090

[1] http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=ws-calendar
[2]
http://www.oasis-open.org/committees/comments/index.php?wg_abbrev=ws-calenda
r
[3] http://lists.oasis-open.org/archives/ws-calendar-comment/
[4] http://www.oasis-open.org/who/intellectualproperty.php
[5] http://www.oasis-open.org/committees/ws-calendar/ipr.php



---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that
generates this mail.  Follow this link to all your TCs in OASIS at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php 




[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]