Get on the standards train (or bus, or whichever mode of transportation is your preferred participation metaphor)

In my most recent editorial, I counsel participation in standards-making processes. Basically, no one knows better how products should operate than those who install the products and have to make them work to satisfy end users. Similarly, if you're involved in a process - dispatch, etc. - you ought to make sure you don't have that process dictated to you by a standards body that doesn't have the appropriate input from those who will be most affected by the resultant standard. Well, here's a good chance to poke your nose in, even though it's more directed toward manufacturers. SIA (the Security Industry Association - in case you're not up on your acronyms) is exercising considerable muscle and energy in trying to create technology standards and it's my belief that the association will wind up being the de facto standards-making body for the security industry, at least in the short term, before historically IT-focused standards-making bodies might conceivably take over some of the technology standards in the industry. Anyway, what I'm pointing you to does seem a little dense, I'll admit. Check out this paragraph: The OSIPS Framework is the foundational standard for the OSIPS family of standards. Since OSIPS is directed at enabling the open integration of so many different types of components, it is essential to establish precise definitions of shared system elements and common means to communicate. OSIPS Framework provides the requisite definition needed to create this goal including interface infrastructure requirements and special interfaces for shared activities such as event reporting, schedules exchange, and other common functions. I mean, "create this goal"? Still, the comment period is open till Jan. 7, which gives you some time to figure out what this all means and whether you have an opinion. Read the proposed standard here. Comment here. Seriously. Do it.