China 简体中文 Japan 日本语 United States English
International Office Locations
  HOME    COMMUNITY    BLOGS & FORUMS    The Standards Game
The Standards Game

The 5th Commandment for Effective Standards

Posted by Karen B on February 5th, 2009

It’s time for the next Commandment for Effective Standards.

Number 5 is: Realize There Is No Neutral Party.

For anyone involved in the standards game, this knowledge is crucial. Everyone participating in standards has a mission to accomplish, be it for business, law, safety, technology, or personal reasons. No one would spend a valuable minute or a precious penny on a standards activity for which they didn’t care about a specific outcome.

People can be surprised when they come to understand how not-neutral standards participants are. An engineer who is new to a committee can be horrified to discover that another committee member has been purposely delaying progress by throwing up smokescreens that sound like policy discussions. An EDA vendor can be perplexed when another vendor who has participated in developing a standard for years suddenly announces an alleged essential patent. And a customer can be shocked upon discovering shenanigans that feel like vandalism when attempting to survey the industry about which of two standards is preferred.

I’ve always chuckled when an organization claims to be a “neutral third party”. It happens usually in the midst of a standards struggle, and on the surface it seems to be an answer to a settlement. In truth, the NTP (how’s that for a new acronym?) has something to gain. In the case of one famous – I should say infamous – standards battle (see the last paragraph of the article), the NTP stood to increase membership and bring in additional funding.

Keeping the 5th Commandment for Effective Standards in mind before jumping into a standards activity can help you gain a broader perspective and quell some of the emotions associated with any skirmishes that might erupt.

If anyone can find a truly neutral party in the standards game, I’d be fascinated to learn about it.





VN:F [1.9.8_1114]
Rating: 0.0/5 (0 votes cast)
  • Print
  • Digg
  • del.icio.us
  • Facebook
  • Google Bookmarks
  • Google Buzz
  • LinkedIn
  • RSS
  • Twitter

5 Responses to “The 5th Commandment for Effective Standards”

  1. JL Gray says:

    So, would it be a standards faux pas if someone actually pointed out in public what side/strategy they felt everyone was taking? Then instead of arguing about things, we could have a vote and all go on vacation for the length of time of any desired delay :-) .

    JL

    VA:F [1.9.8_1114]
    Rating: 0 (from 0 votes)
  2. karenb says:

    JL,

    One can certainly do this. If willing to risk their own strategy being revealed, that is. That conversation is exhilarating. :)

    Karen

    VA:F [1.9.8_1114]
    Rating: 0 (from 0 votes)
  3. Vote … did someone say vote ;-)

    In all seriousness, with respect to the Accellera VIP TSC, I believe that OVM and VMM are just proxies for the respective vendors’ simulation products. So there is obvious vested interest in the outcome. Given the state of the industry and economy, those battles have an even greater significance now.

    Or as they great philosopher Guido the Killer Pimp once said, “In a sluggish economy, never ever (mess) with another man’s livelihood”.

    VA:F [1.9.8_1114]
    Rating: 0 (from 0 votes)
  4. Mike Mintz says:

    Hi Karen,

    Right on! Everyone has an agenda. I was pretty shocked when I attended my first few standards meetings.

    I would have loved to have read your blog beforehand.

    Take Care,
    Mike

    VA:F [1.9.8_1114]
    Rating: 0 (from 0 votes)
  5. Trackbacks/Pingbacks

    1. [...] this standard could be challenging. Is it possible to have an objective standard? Enjoy this blog entry on the notion of “objective” standards. Can the standard be developed quickly enough to avoid [...]

Leave a Reply

XHTML: You can use these tags: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>