Request to join oBIX (OASIS Open Building Information Exchange) TC Approved

[obix-chair@lists.oasis-open.org]

<p>You have been approved for membership in the oBIX group. The first meeting
of oBIX will on June 15 - be sure to check the calendar for details.</p>

<p>We anticipate creating subcommittees during that first meeting, as the field
of oBIX is quite large. Please be sure to consider which subcommittees your knowledge,
expertise, and reason for participating in oBIX will complement the most.</p>

<p>Probable subcommittees are:</p>

<ul type=disc>
 <li>Data Structures: for those most skilled in XML/SOAP
     and most knowledgeable about the nitty-gritty of controls systems</li>
 <li>Implementations Guidelines: oBIX exists alongside
     many control protocols (BACnet, LON, ModBus, et al.) and bridge protocols
     (BACnet ML, LON XML). As oBIX is not a replacement for those protocols
     there are appropriate and inappropriate uses for oBIX. This subcommittee
     will be focused on developing guidelines for the appropriate use of oBIX,
     i.e. when to use it, when to specify it, and, as important, when not to.</li>
 <li>Vertical Market Special Interest Groups (SIGs).
     Preliminary work has identified nearly 30 separate vertical controls
     markets within the building controls space that are potentially within the
     span of oBIX. Many of these have their own internal vocabularies that are
     not necessarily compatible with each other. As these systems are exposed
     to the enterprise, we will be coming up with common methods that apply
     across these vertical niches. We anticipate creating Vertical SIG subcommittees
     as needed to discover the commonalities and differences, to provide
     industry-specific lexicons, and to advocate the needs of that vertical
     industry to the oBIX committee.</li>
 <li>Owners, Operators, and Tenants. As oBIX exposes
     controls to the enterprise, it grants the enterprise permission to
     interact with those control systems. This committee will focus on
     developing use cases and prioritizing development efforts by the other subcommittees.
     </li>
</ul>

<p>Of course, the actual subcommittee structure will be determined in
open meetings, but something consistent with this structure is anticipated.</p>

<p>Welcome aboard!</p>