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: Groups - Open Workshop on oBIX Next Steps added

At last, I am free during the oBIX meeting time. Those of you who have been
working with me in EMIX also have some free time before the Public Review
comes back.

Open Workshop Meeting. Bring your friends.

 -- Toby Considine

Open Workshop on oBIX Next Steps has been added by Toby Considine

Date:  Thursday, 09 December 2010
Time:  11:00am - 12:00pm ET

Event Description:
Conference Dial-in Number: (760) 569-0100
Participant Access Code: 1064971#

Chat Room: 


I would like to discuss the road ahead, in an Open Workshop meeting. Open Workshops are note meetings of the TC, and no resolution of the specification is discussed. This means that not Committee members can attend, and speak. 
Questions before us, as I see them:
1)	What are the things that we must accomplish to get v1.1 out the door, and ready for submission to the wider OASIS as an OASIS Standard. 
	Do we have all the errors and omissions and vagueness cleared up?
	Someone was working on defining an Atom binding. Is it ready? Can it be ready soon? Should we wait for it?
	WS-Calendar is here. Do we delay to incorporate WS-Calendar based schedule communication into 1.1?
	De we want to define / create a top-level meter object able to deliver information that meets the NIST / Smart Grid standards for Energy Usage Information?
	[Gleen anything else from the BSI discussion below]
	oBIX Enterprise  In scope or pushed to BSI http://www.oasis-open.org/committees/download.php/38210/obix-1.1-wd-enterprise-01.pdf 
	Defining and maintaining permanently named custom contracts
	What else?
2)	We need three OASIS members who can say that they are using the spec, and that their applications interoperate. 
3)	Do we need to incorporate any elements 
There has been some discussion that oBIX Enterprise (or some other named TC) is a separate TC, built atop oBIX, but separate, keeping oBIX 1.1 Lean.
Then there is the larger matter of defining the BSI (Building System Interface).  The BSI is why *I* signed up for oBIX in the first place. More on the BSI below.  See, the problem with oBIX is that there is no way anyone sane would allow a programmer from accounting to have untrammelled access to oBIX. There is no context to define security in any way other than Configurator / Operator / Auditor, (and perhaps not even anything other than Configurator / Operator) because as there is not metadata framework to define what granular security means.
1)	My first cuts on BSI issue is the original oBIX subcommittees:
o	Security and Access Control:  http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=obix-security
o	Power Systems:  http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=obix-security (could be quickly updated with recent SG actitivties)
o	oBIX 2.0 Vision requirements and Use Cases:  http://www.oasis- open.org/committees/download.php/9397/UseCases.01.pdf
o	oBIX for Distributed Energy Resources
2)	Smart Grids and SPC 201
3)	Metadata and Commissioning Standards for low integration costs
4)	Cloud interfaces to Building Systems
5)	BIM-based metadata
6)	John Subletts V2.0 Vision document www.oasis-open.org/committees/download.php/.../oBIX-2.0-vision.doc

We should come out of this open workshop with a consensus about how to proceed. We can also discuss how the national Smart Grid activities expand the value proposition of oBIX, and Building Systems become VENs and VTNs,.

I have been contacted by several people who want to schedule meetings on these and related issues at the ASHRAE winter meeting. This is probably the best place to start, though, as before, Energy Metering, Access Control, CC Monitoring, et al. are less than interested in ASHRAE as a home.


View event details:

PLEASE NOTE:  If the above link does not work for you, your email
application may be breaking the link into two pieces.  You may be able to
copy and paste the entire link address into the address field of your web

PRODID:-//Kavi Corporation//NONSGML Kavi Groups//EN
X-WR-CALNAME:My Calendar
SUMMARY:Open Workshop on oBIX Next Steps
DESCRIPTION:Conference Dial-in Number: (760) 569-0100\nParticipant Access Code:
  1064971#\n\nChat Room:
  \nhttp://www.soaphub.org/conf/room/oBIX\n\nGroup: OASIS Open Building
  Information Exchange (oBIX) TC\nCreator: Toby Considine

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