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

 


Help: OASIS Mailing Lists Help | MarkMail Help

obix message

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


Subject: Formalizing Conract Descriptions


The continuing work of WS-Calendar to define standards for aligning schedules and describing time segments will be frozen just before Connectivity Week to give the wider community an opportunity comment on the work.  The TC plans to announce an informal 30 day request for comments – both in OASIS and in the IETF. That is an important time for the oBIX community to look at the work with an eye to making sure it will meet our needs for eventual incorporation.

 

Committees start with one focus, and get a life of their own. WS-Calendar received a request to specify communications of what I would call sequences of operations (SOO). After consideration, the WS-Calendar TC voted explicitly that Sequences of Operations were in scope. I encourage oBIX participants to consider how this elaboration of schedules overacts with the oBIX 1.1 specification. This work will not be ready before during the upcoming comment period; we plan to use that period, with the rest of the document effectively frozen, for addressing this area.

 

The most well-known and accepted sequencing of activities between actors is in BPEL (Business Process Execution Language) (pronounced Bee-Pel) . The TC plans to make recommendations on how to extend BPEL to include specific schedule and interval requirements; you might think of this as a schedule-aware extension / profile to BPEL.

 

http://en.wikipedia.org/wiki/Business_Process_Execution_Language

 

The secretary of WS-Calendar was quite involved in the BPEL work and is now also on the BPEL4PEOPLE. WS-Calendar is currently recruiting additional members who have BPEL experience.

 

Clearly a building system gateway could implement the SOO communications alongside oBIX no matter whether the oBIX TC acknowledges the SOO portion of the specification. I am sending this note to start the conversation, should the oBIX TC do more than that. I think we should consider whether the SOO activity should be incorporated into oBIX along with the schedule and communication.

 

tc


"Energy and persistence conquer all things." -- Benjamin Franklin


Toby Considine
TC9, Inc

OASIS Technical Advisory Board
TC Chair: oBIX & WS-Calendar

TC Editor: EMIX, EnergyInterop

  

Email: Toby.Considine@gmail.com

Phone: (919)619-2104

http://www.tcnine.com/

blog: www.NewDaedalus.com

 

 



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