Consortiuminfo.org Consortium Standards Bulletin- November 2006
Untitled Document
Home About This Site Standards News Consortium Standards Journal MetaLibrary The Standards Blog Consider This The Essential Guide to Standard Setting and Consortia Sitemap Consortium and Standards List Bookstore
   Home > Consortium Standards Bulletin > January 2007
  Untitled Document
Untitled Document

 

January 2007
Vol VI, No. 1

CREATING A SUCCESSFUL CONSORTIUM PART II

EDITOR'S NOTE: STRUCTURING FOR SUCCESS
 
EDITORIAL: STEPPING THROUGH THE LOOKING GLASS
Becoming an effective director of a standard setting organization requires abandoning traditional measures of success, and embracing new ways to achieve important goals. Print this article
   
FEATURE ARTICLE:

CREATING A SUCCESSFUL CONSORTIUM -- PART II

Structuring a new organization to successfully and safely - create and promote standards requires a knowledge of corporate, antitrust, trademark, tax, and intellectual property law. Doing it properly is essential to achieving success.   Print this article
   
STANDARDS BLOG: THE CONTRADICTORY NATURE OF OOXML
Microsoft's Office Open XML specification has been approved by Ecma, and is now under review by ISO/IEC for adoption. OOXML will be of great use to software developers and Microsoft customers. But the eligible members of ISO/IEC must now determine whether OOXML meets the global standards organizations' rules and whether the world needs a second de jure document format standard. Print this article
   
CONSIDER THIS: PRODUCT EVOLUTION AND "STANDARDS SWARMS"
Historically, products came first, and standards second. But with technology cycles becoming shorter and the technologies themselves converging, if the chicken were to wait for the egg, it wouldn't have time to hatch. Print this article

Print this issue


 

EDITOR'S NOTE:

STRUCTURING FOR SUCCESS

Last issue, I discussed the business issues that must be addressed in order to create a successful consortium, and promised to share further thoughts on the topic of consortium formation the next time around.  In this issue, I'll focus on two topics: the role of the director in guiding a consortium, and the legal considerations that must be addressed in creating and operating a successful consortium.

In my Editorial this month, I highlight the fact that the success criteria for a non-profit standard setting or promotional consortium can be very different than those that measure victory for a profit-driven business.  After all, consortia are founded to drive the adoption of standards, and not membership revenue.  As a result, directors must trade in one set of assumptions when they take time off from their day jobs to help manage a consortium.  If they fail to do so, the means rather than the ends can become the focus of the Board's attention.  When this happens, members can find themselves with an organization obsessed with growth and perpetuation rather than standards and adoption.

Directors of non-profit consortia must also recall that they are subject to the same duties of loyalty as for-profit corporate directors, even if their employers have the right to appoint them in exchange for large dues payments.  As a result, the director role can become particularly complex for vendor representatives: while such directors may be expected to present the viewpoint of their employers to illustrate the needs of other members with similar interests, they must still act on behalf of all members, and not just their employers.

In my Feature article, I provide a detailed overview of legal matters of concern to consortia at the time of formation – covering topics as diverse as jurisdictions of incorporation, antitrust law, tax exemptions, trademarks, intellectual property rights policies, and more.

For January's Standards Blog selection, I focus on the other end of the standards development funnel – and provide an update on a specification that I've been writing about directly and indirectly since the late summer of 2004 – Microsoft's Office Open XML formats (OOXML), which are now under review in ISO/IEC Joint Technical Committee 1.  That specification was approved by European standards body Ecma last December.  Unlike most standards, OOXML is intended to describe a single product – Microsoft Office.  The next six months will tell whether this type of standards effort is, or is not, destined to be successful.

In my Consider This essay, I examine the parlous practice of developing standards contemporaneously with the evolution of the underlying technology – a risky business that is bound to result in many standards failing, but nonetheless enables those that are successful to permit products to reach and proliferate in the marketplace far more quickly than if the standards process were to follow rather than lead.

As always, I hope you enjoy this issue. 
   
Andrew Updegrove
Editor and Publisher
2005 ANSI President’s
Award for Journalism
 
     
The complete series of Consortium Standards Bulletins is available on-line at http://www.consortiuminfo.org/bulletins/  It can also be found in libraries around the world as part of the EBSCO Publishing bibliographic and research databases

 

EDITORIAL

STEPPING THROUGH THE LOOKING GLASS

Andrew Updegrove

The greatest challenge that newcomers to the standards world must face is grasping the reality that success is about giving away rights in some technology in order to make money on other technology. This means that those who would form a new consortium must enter into a sort of "through the looking glass" world where patents are impediments rather than tools, royalties are unwanted encumbrances, licenses exist for the sake of disclaiming rights, and collaborating with competitors is as essential as working with partners.

 

Becoming a productive director in a standard setting organization (SSO) can be a disorienting experience, especially if the responsibilities of that office are fully embraced.  The reason is that while the same legal duties apply to an SSO director as control the actions of other corporate directors, many traditional management goals are turned inside out.

At the most basic level, a director of an SSO must shed the conviction that the most important goals of the enterprise are to drive growth, maximize profits, ensure institutional survival, and drive growth.  In fact, those goals may or may not be consistent with the actual mission of an SSO at all.  This is particularly so for an SSO with a discrete goal, such as developing and promoting a single standard, as compared to an organization with a mandate to develop multiple standards to serve the core needs of an entire technical domain.  In the former case, success may be measured by declaring "mission accomplished" as soon as possible, handing off the standard to another SSO for long-term maintenance, and promptly going out of business.

Too often, SSO directors with the best of intentions focus primarily on traditional metrics, quizzing management more on revenue growth and how many press releases have been issued, rather than on numbers of standards completed and (more importantly) broadly adopted.  Over time, the culture of such an organization can turn to one of self-preservation, rather than one focused on achievement of its true mission.

Directors of SSOs that are nominated by vendors can find themselves in another, and more awkward position.  The conflict arises from the fact that they are expected to wear two hats, and often have a third in their back pocket as well.  The first is the conservative homburg of a director in a traditional corporation, which obligates its wearer to observe a duty of loyalty to all owners of the organization.  The second is less conservative, and its style is intended to be representative of the member and its peer companies.  This is because directors on the boards of many SSOs are expected to express the viewpoint of their employers (large or small, hardware or software, vendor or end-user), thereby acting as a proxy for similarly situated members with similar interests and needs.  This is particularly so in SSOs that try to balance their boards in order to ensure that all categories of members are heard, and their needs accommodated.

The virtual ball cap in the back pocket, of course, prominently bears the corporate logo of the director's employer, and it is this factor that creates the tension.  The reality in many consortia is that those that pay the most may receive a guaranteed board seat as one of the perks of anteing up for a top-level membership.  Sometimes the price for that seat can be quite high.  How are the expectations of members that pay such prices to be squared with the legal duties of a director?

The statutory answer is clear – a director's duties trump her employer's directives.  In the breach, of course, what actually goes through the mind of an individual director when a question is put to a vote is known to that individual alone. 

In fact, this type of conflict need not be as great it may at first appear.  An apt analogy can be found at the technical level, where newcomers to the standards world must come to grips with the reality that success in standard setting often requires giving away some proprietary rights in order to make money on others.  This means that those who would form a new consortium must enter into a sort of "through the looking glass" world where patents are impediments rather than tools, royalties represent unwanted encumbrances, licenses exist for the sake of disclaiming rights, and collaborating with competitors is as essential as working with partners.

In the technology sector, more and more vendors "get" this concept, resulting in increasing pressure to develop standards that are not only royalty free, but in the case of software, available on terms that are conducive to open source implementation as well.  One reality leading to this realization is that we live in an increasingly networked world.  In such a place, the biggest wins come from enabling the creation of markets for new products and services that would not be viable absent agreement on enabling standards, and not from the royalties that might be obtained from a single patent, perhaps at the cost of constraining the size of the market itself.

This is the goal on which a director must focus, and not the particular technical outcome that might be somewhat more desirable for her employer, if only the opposition can be maneuvered into the right position to permit win the play to be won. 

At the end of the day, the very serious game of standard setting must be played on the other side of the looking glass, and by its own rules.  Under those rules, winning must be a team effort – with everyone wearing the same hat.

 

subscribe

Comments? Email:

Copyright 2007 Andrew Updegrove


 

FEATURE ARTICLE

CREATING A SUCCESSFUL CONSORTIUM
PART II

Andrew Updegrove

Abstract:  In Part I of this article, I reviewed the key business concepts underlying the formation of a successful consortium to develop, promote and/or support standards.  In this second and final installment, I will discuss the most important legal considerations to consider in creating and maintaining such organizations, including: issues presented by specific types of activities; common legal structures and the relative virtues and shortcomings of each; optimal jurisdictions for formation; antitrust laws and their implications for operations; tax exemption criteria; the advantages and disadvantages of seeking exemption as a public charity as compared to a trade association; how to evaluate the advisability of seeking that exemption; intellectual property rights policies and procedures; and issues associated with certification and branding.

Introduction: In the first installment of this two-part article, I focused on the business issues and concepts underlying the formation of a successful consortium to develop and/or promote standards. 1 In this second and final installment, I will discuss the legal issues that relate to the creation and operation of such organizations. 2

Standard setting organizations (SSOs), whether they be decades-old accredited standards development organizations (SDOs), or any of the more recently formed non-accredited organizations that range from small, invitation-only entities to well-respected, global standard setting consortia such as the W3C, IETF or OASIS, face essentially the same legal issues. 3 These issues morph over time, as new laws are passed, new cases reinterpret old laws and decisions, and SSOs enter into new areas of endeavor.  For SSOs, as with other businesses, staying on the right side of existing and new legal rules requires ongoing awareness and monitoring. 4

But while the same legal issues are relevant to almost all SSOs, the specific ways in which a given SSO will operate and structure itself in relation to those issues will necessarily be a product of its particular situation: its mission, goals, projected membership and activities, and other variables.  In this article, I will review the areas of legal significance with which the founders of a new SSO must be aware, and highlight the types of decisions that SSO founders should make, based upon their unique business plan.  The issues addressed, and the solutions suggested, are based upon my experience in helping create more than 50 consortia over the past 18 years.  A full list of the SSOs that I have represented can be found at this Web page.

I            Structure


Concerns to be addressed: Standard setting and related activities (e.g., promotion, test-creation and certification testing, public advocacy and training) present a range of concerns that dictate structural decisions. These concerns include the following:

          Liability:  While SSOs do not typically engage in high-risk activities, SSO members (and especially corporate members) have an understandable aversion to participating in organizations where the actions or inactions of other members could lead to joint liability. Accordingly, mechanisms intended to eliminate, or at least limit, such an eventuality are essential to facilitating successful recruitment.

          Practicalities:  SSOs that are more than minimally active will soon face the need to enter into contracts with third parties such as trade show management companies, public relations firms, and Web hosting services. They may also wish to hire employees. Absent an incorporated entity to sign legally binding agreements, one member or another will need to provide a signature and incur the front-line liability on the obligation. Even something as simple as opening a bank account becomes problematic, since a bank will not open an account for an entity that does not have an employer identification number.

          Ownership of intellectual property:  SSOs create assets of various types in which intellectual property rights (IPR) may arise - typically copyrights, trademarks and potentially patentable inventions.  But who should own, and define use rights to such IPR?  On the one hand, individual members do not wish their own ownership rights to be jeopardized when they collaborate in a working group.  But on the other, potential implementers will need to be convinced that implementing the resulting specification will not result in potential liability for infringement, or in becoming unduly dependent on the intentions of a single patent owner – especially if that patent owner is a competitor.  As a result, the ownership of assets such as standards, test suites and trademarks is a matter of particular concern, as are the legal mechanisms by which desired outcomes may be guaranteed.

          Governance:  Whatever structure is chosen must not only be appropriate to permit efficient and effective operations, but also satisfy the concerns of those that are investing in the creation of the new entity: that it will not stray from its intended purpose, that it will be perceived as "open" (if that is the goal) or permit the founders to remain in control (if openness is not a concern), that no individual member can block or veto necessary actions, and so on.

          Ease and cost of formation:  Time spent on formation and dollars spent on lawyers do not advance the goals for which a new organization is formed.  Accordingly, the structure chosen should permit as rapid and inexpensive a launch as possible, as well as efficiency in ongoing operation.

Formation criteria:  Deciding which structure is most appropriate for a new organization will be most heavily influenced by the answers to the following questions, among others:

          Duration:  What is the expected duration of the project at hand?  Will it be finite, and limited (for example) to the development of a single specification, which will then be offered to another SSO for adoption and long-term maintenance, or will the new organization be founded to create an ongoing series of standards?  If the former, the business plan may be less complex, and the needed legal structure more light weight.  In the latter, multiple classes of membership, layers of technical process, and a variety of promotional and other activities may be involved, requiring a more robust and detailed governance and operational structure to be enabled and managed through the legal structure. 

          Membership:  Will the success of the initiative be assured by the participation of a small number of participants, or only by attracting the involvement of a large and diverse membership?  Will the value propositions required to attract different types of stakeholders vary greatly?  Will any type of stakeholder (e.g., government representatives) be subject to legal constraints on its activities, or that would limit its ability to make the commitments required of a member?

          Activities:  What might the new organization wish to do over its expected lifespan?  Only develop or promote standards, or also create test suites and conduct compliance testing?  Will it wish to support a branding program?  Will it need to have international operations and offices?  Will it engage in lobbying or other public advocacy activities?  Will it generate revenue from other than membership fees?  Will it wish to limit its activities only to members, or permit participation by others in some of its activities as well? 

          Liability profile:  Most standards-related activities are quite benign, but this is not true in all cases, and even in otherwise low-risk situations, where the membership constitutes "market power" under the antitrust laws (e.g., a significant percentage of the competitors in a given product or service space are members), the potential for inadvertent mistakes, as well as the level of potential scrutiny by government regulators, is higher.  In such a situation, individual members may wish to maintain tighter control over what can – and more importantly, what cannot – be done by the organization and its members without proper prior consideration.

Available structures:  While there is no "one size fits all" way to structure and manage a consortium, there are reasonably defined variations and best practices to consider before creating one.  As a result, a small number of models have evolved upon which nearly all SSOs are founded.   In the United States (where the great majority of new SSOs have been formed in the last twenty years), new consortia are almost always based upon one of four legal foundations, each of which has its advantages and disadvantages, requiring detailed explanation.  They are as follows:

          The "classic" corporate model:  By far and away, the largest number of consortia intended to have more than a transitory existence are structured as corporations.  Typically, they are formed under the not for profit laws of a jurisdiction, whether or not the founders intend to seek federal or state tax exemption for the consortium. 

The would-be founders of a consortium very frequently believe that a corporation is the last, rather than the first, alternative to consider.  The reason is that the formation of a corporation would seem to represent expense, complexity, permanence and burden.  In fact, the opposite is almost always the case, due to the simple fact that existing corporate law supplies all of the rules, as well as the solutions, that a non-corporate structure must otherwise create from whole cloth.  Moreover, there are some concerns, such as joint liability, which cannot be easily or completely avoided by any non-incorporated means – yet the simplest corporate structure, if properly maintained, can provide convincing protection to its officers, directors and members.

Moreover, experienced counsel should already possess a set of model documents that can be easily tailored to the needs of the organization, and which provide all of the statutorily-enforceable rules and provisions other than those which will be unique to the organization.  Those documents include the following:

  • Certificate of Incorporation, containing the limited number of rights and rules which by law must be set forth in this public document.
  • Detailed Bylaws, a non-public document that contains the legal and procedural rules of operation, the governance structure, the classes of membership and their rights, and other provisions which enable the day to day operation of the organization (other than the technical process, on which more below).
  • Membership Application, which should be drafted to constitute a legally binding contract between a member and the consortium, and thereby obligating the applicant to abide by the rules of the organization, including its IPR Policy.6

Upon formation of a membership corporation, all of the initial concerns have been satisfied: a liability shield has been created, an entity exists that can create and own IPR, sign contracts, and employ staff (if desired), and a workable governance structure has been provided within a reliably enforceable statutory context.  Moreover, if the documents used are already familiar to the members by reason of membership in other consortia built upon the same models, legal review by members will be far faster than would be the case if a custom, non-incorporated model were to be employed.

          Limited Liability Corporations:  A small number of consortia have been created based upon this model.  Limited liability corporations (usually referred to simply as "LLCs") came into being comparatively recently, but may now be created in every US state, with the enabling rules varying to some extent among jurisdictions.  LLCs provide essentially all of the same legal protections and capabilities as the traditional corporation, but under rules that are in some respects more flexible. 

This flexibility provides a mixed blessing.  On the one hand, the members of an LLC may "opt out" of certain unavoidable constraints to which all corporations are subject.  But on the other, this same flexibility leads to the need to provide for more detailed and customized documentation to accomplish the same results.  And, since much more language is now custom, rather than closely derivative of statute, there is less certainty as to how a court would construe and enforce that language in the case of a dispute.

Another result of this customization and lessened certainty of result is that members are more likely to conclude that the close attention of their own counsel must be directed at the formation documents, which can lead to higher formation costs and a delayed launch date for the new organization.

As a result, and as is the case in many commercial settings, an LLC structure is usually used to form a consortium only when the simpler, traditional corporate structure will not permit some important objective to be satisfied. 7

          Semi-autonomous, hosted models:  A few SSOs have from time to time decided to offer hosting services to other, typically smaller, standard setting initiatives.  This allows a modest SSO to have most of the advantages of being incorporated and staffed, without actually having to take the necessary actions to achieve either status. 8 The host typically offers most administrative, and sometimes other, services for a fee.  The hosted SSO then adopts it's own, shorter set of bylaws (often using a form provided by the host), as well as its own (or the host's) IPR policy, and commences operations.  This arrangement offers a sort of hybrid existence that is mid-way between a working group of an SSO and an independent organization.  Like the former, it relies on the host for its infrastructure and services.  But like the latter, it is largely autonomous when it comes to governance, setting its dues, charting its technical program, and deciding what other activities, if any, it wishes to include in its programs.

In addition to the availability of services on demand and the corporate liability shield and tax exemption that may be provided by the host, this hosted option typically permits a new initiative to get up and running quickly.  The most common disadvantages that have sometimes been encountered with this model include high cost relative to services rendered and, at times, poor service, especially where the hosting activity was not the primary business of the host. 

In contrast, the service providers that provide hosting activities as their sole business activity focus all of their attention to that function, and as a result may provide superior service at similar, or lower, cost.  More typically, they will also assist their customers in becoming incorporated, rather than otherwise (this is advantageous for the SSO, as well, which as a result has greater flexibility in choosing the service provider from which it purchases services).

The most significant difference between non-profit and for-profit hosts may be that a for-profit host cannot provide tax-exempt status for its customers, providing another reason why their customers typically incorporate, even though they then contract with the host to provide some or all of their administrative, staffing, member support, and other needs.

          Non-incorporated models:  By definition, non-incorporated models are more diverse, due to the fact that founders that choose this route are working from a clean slate.  That said, non-incorporated initiatives may initially be divided into two groups: the "muddle along" and the documented.  Muddle along initiatives, not surprisingly, are generally modest, and may be promotional, educational or otherwise more limited in ambitions than more determined standards development efforts.  If the initiative proves to be worthwhile and ongoing, a non-documented effort will usually become incorporated or otherwise documented eventually – often when the in-house counsel of one or more members becomes aware of what is going on, without benefit of a liability shield.

Where the decision is made to pay due attention to legal concerns but not incorporate, some sort of legally binding documentation must be created.  As with LLCs, this means that more effort must be dedicated to spelling out all aspects of the organization's governance, membership, operations, duration, ownership rights, and other details than would be required if the founders had desired to incorporate.

Notwithstanding a number of shortcomings (discussed below) of the non-incorporated model, this approach is still common, especially in situations where a limited number of companies wishes to create a specification that may infringe upon patents owned by many or all founding members.  In short, the goal of the founders may be to simply add rules relating to joint development activities to a typical cross-license agreement.  In this model, a "promoter adopter" structure is often utilized, in which the core members (usually a group formed by invitation only) enter into a "promoter agreement," under which the promoters agree to use a specification contributed by one or more members, or to jointly create a specification needed by all to (for example) create a new product that requires interoperability among all vendor offerings. 

Under the terms of the promoter agreement, each promoter typically provides the group with a royalty-free cross license under all of its necessary patent claims under the specifications created by the organization.  The promoter agreement also permits each promoter to sublicense the right to implement the same specification, subject to the patent rights of each promoter.  All promoters typically agree to make patent licenses available to all such sublicensees under reasonable and non-discriminatory (RAND) terms. 

The right to implement the specification is provided to third parties under an "adopter agreement," using a mutually agreed upon form.  Adopters may or may not still be required to enter into separate patent license agreements with each other promoter.  The terms of these licenses may sometimes be more restrictive than might commonly be found in relation to standards that are developed by consortia based upon more open models.

The promoter-adopter model is popular with a few companies with very large patent portfolios, and is most often found in the market niches occupied by these companies.  The advantages of the promoter-adopter model include the following:

  • A high degree of certainty regarding patent rights among promoters and adopters (adopters are usually asked to provide a license to their own necessary claims under the specification back to the promoters, or may at least lose their license if they sue any promoter for infringement)
  • A light-weight document structure, since the promoter agreement typically provides for all obligations (formation, governance and IPR related) in a single agreement, and the shorter adopter agreement provides all that an adopter needs, other than any direct licenses required by one or more promoters
  • A reasonably standardized document package, due in part to the fact that a large percentage of the organizations based upon this model have been founded by a small number of companies.

The disadvantages of the promoter-adopter model (and all other non-incorporated approaches) are equally significant.  They include the following:

  • There is less certainty of legal enforceability in general in comparison to the corporate model, since terms must be legally interpreted on their own merit,  unlike bylaw provisions, which typically track an enabling statute word for word, and can be interpreted in the context of the voluminous case law that has accumulated over the years.
  • Where certainty of result does exist, it is not always welcome.  For example, regardless of any language that is included in the operative agreement among the members of an unincorporated consortium, applicable law may deem the arrangement to be equivalent to a partnership, subjecting all members to joint liability not only with respect to the debts or actions of the organization itself, but potentially for the acts or omissions of any single member when that member is arguably acting on behalf of the organization. 
  • Third parties may be unwilling to accept a signature on behalf of an unincorporated entity.  Nor can such an organization easily hire employees. 
  • Each member's balance sheet would need to carry its allocable share of the profits and losses of the organization.
  • If membership is by invitation only, the specifications that are created are inherently more proprietary and less open, at least by appearance, and often in practice.
  • If more than a single class of membership is needed, the documentation becomes more complex.
For these and other reasons, non-incorporated models are less often used than corporate models.  When they are, it is often due to one of the following reasons: the founders are only familiar with the unincorporated model; they wrongly believe that forming a corporation would be more expensive and complicated; or the goals of the founders are limited, as when the intention is to create and maintain a single specification. 8

Jurisdiction of formation:  The laws under which a given consortium may be formed, unfortunately, may be determined more as a result of the attorney chosen to represent the new entity than by a conscious weighing of the appropriateness of the laws of one jurisdiction over another.  In fact, corporate statutes, and particularly not-for-profit corporate statutes, vary from jurisdiction to jurisdiction.  While those statutes have tended to become progressively more similar over time than the opposite, important differences can remain from state to state. 
The reasons for choosing one jurisdiction over another should include the following:

  • Flexibility:  How much freedom is permitted in structuring the entity?   If desired, can essentially all powers (other than the election of directors) be vested in a Board of Directors, to provide for speed and ease of governance, or must some powers be shared with members?  Must the Board operate according to traditional board rules, or can it provide for different methods of operation (e.g., acting by less than unanimous written consent), in order to facilitate the operations of what are increasingly likely to be virtual organizations with boards of directors drawn from a global membership?  For similar reasons, can alternate directors be appointed to substitute for primary directors when the latter cannot attend a meeting?
  • Familiarity:  Consortia typically strive to set global standards, and therefore to attract a global membership.  Outside of the US, only the laws of a few states would be familiar with many potential members and their counsel. Even within the US, the laws of small states may be less well known than those that host the headquarters of many Fortune 500 companies. 
  • Extraneous concerns:  States vary in the degree to which they differentiate among types of non-profit corporations.  As a result, a state that is more concerned with farm co-ops, churches, fraternal organizations and public charities may have a less useful non-profit statute than one that contemplates the needs of business-oriented organizations as well. 
  • Degree of regulation:  Some states have more extensive social or other regulations (or just more regulations, full stop). 9

This author has formed over 50 consortia as not for profit membership corporations under Delaware law, for a variety of reasons, including the following:

  • Delaware traditionally represents the most advanced and progressive jurisdiction with respect to corporate law.
  • Of all US jurisdictions, Delaware law is mostly likely to be familiar to US and foreign lawyers.
  • Delaware law provides unique flexibility with respect to the operation of the board of directors of a non-stock corporation, making it easier to conduct the affairs of a consortium with a board that typically includes many busy international executives.
  • The differences between Delaware corporations that have stock and those that do not are minor, and almost always provide for additional flexibility.

Happily, reincorporating in Delaware is neither expensive nor difficult.  If the board or management of an existing consortium finds that it has been created under laws that prove to be unduly restrictive, a new corporation can be formed in Delaware, and the existing organization simply merged into the newly created shell.

II            Antitrust Considerations

Whether incorporated or not, consortia need to adopt a number of policies at, or not long after, inception.  Those policies are necessary to provide further guidance for the conduct of activities, as well as to regulate behavior in order to steer clear of potential liabilities.  One of the most important policies relates to compliance with antitrust laws.

By their nature, SSOs are organizations that bring direct competitors together in the same room for the purposes of engaging in joint action.  As a result, the antitrust laws – and the potential liabilities that can arise from being insufficiently aware of their prohibitions  - are particularly relevant to the operations of SSOs.

Happily,  for SSOs, over the last quarter century the antitrust laws in the United States have become progressively more favorable to pro-competitive collaborative activity among competitors.  For example, in 1983, Congress passed the National Cooperative Research Act, which was later amended to cover production activities as well (the Act was concurrently renamed the National Cooperative Research and Production Act, and is commonly referred to as the NCRPA). 10

More recently, in December of 2005, Federal Trade Commission Deborah Platt Majoras delivered a policy speech in which she made it clear that the FTC looked with favor on the pro-competitive effects of standard setting in general, and in particular would be open minded in considering appropriately conducted disclosures of licensing terms during the standards process (so call ex ante disclosure). 11 On October 30, 2006, the FTC made good on this invitation, and issued a favorable business review letter to the VMEBus International Trade Association (VITA), which had proposed amending its IPR Policy to expressly require ex ante disclosure. 12

All of this good will on the part of the regulators aside, the fact remains that those that engage in standard setting and related activities must be mindful of where the boundaries of permissible behavior are located, because the penalties for overstepping those limits can be severe.  Given that consortia operate globally, the antitrust laws of many countries may bear upon their activities, and both the specifics, as well as the underlying social policies, of these laws can and do vary. 

United States Antitrust Laws:  While a comprehensive review of even US antitrust law is far beyond the scope of this article, the following will serve as a brief introduction to the type of concerns that those that would form or participate in SSOs should be aware.

Broadly stated, the basic objective of the US antitrust laws is to preserve and promote competition and the free enterprise system.  These laws are premised on the assumption that private enterprise and free competition are the most efficient ways to allocate resources, to produce goods at the lowest possible prices and to assure the production of high quality products.  These laws require that business people make independent business decisions without consultation or agreement with competitors. 

The US antitrust statutes of principal concern to companies and individuals that take part in trade association activities are Section 1 of the Sherman Act and Section 5 of the Federal Trade Commission (“FTC”) Act.  These laws render illegal all contracts, combinations, and conspiracies which are deemed to be in restraint of trade.

Broadly speaking, the courts have interpreted these laws as prohibiting those contracts and combinations that have the effect of unreasonably restraining trade.  A court will, therefore, examine all the facts and circumstances surrounding the conduct in question in order to ascertain whether the contract or combination is in violation of the law by restraining trade unreasonably.

Many activities are, however, regarded as unreasonable by their very nature and are therefore considered to be illegal “per se.”  Companies and individuals are conclusively presumed to engage in these activities for no other purpose than to restrain trade.  Practices within the per se category include agreements to fix prices, agreements to boycott competitors, suppliers or customers, agreements to allocate markets or limit production, and certain tie-in sales.  A tie-in sale is one in which the customer is required to purchase an unwanted item in order to purchase the product or service desired.

The legality of activities of an SSO or other standards-related consortium and its members under the antitrust laws is determined by the application of standards no different from those used to determine the legality of the activities of other groups of persons or firms.  Special problems do arise, however, from the fact that a consortium necessarily brings competitors into a joint enterprise, and the act of bringing these competitors together creates the means by which collusive action can more easily be taken in violation of the antitrust laws.

Penalties for Violations:  The US antitrust laws are enforced at the Federal level by the Antitrust Division of the Department of Justice and the Bureau of Competition of the Federal Trade Commission.   State court actions may be brought by U.S. State attorneys-general or injured parties under the antitrust laws of individual states as well.

A criminal conviction for a federal antitrust law violation may result in stiff fines for a consortium and its members, jail sentences for individuals (including an individual acting in his or her capacity as a corporate employee or officer) who participated in the violation, and a court order disbanding the consortium, or severely limiting its activities.  In the past, several foreign nationals have been sentenced to serve time in U.S. prisons, and corporations convicted of such a criminal offense have been fined hundreds of millions of dollars.

In addition, private persons or firms may sue for damages under the Federal antitrust laws, and a company found liable may be required to pay up to three times the actual damages suffered by the plaintiff, as well as all of the plaintiff’s costs of litigation and attorneys’ fees.

          Antitrust policies and monitoring:  Given the above, it is not surprising, that consortia, like other trade associations, require antitrust education for Boards of Directors, committee chairs and members, as well as ongoing monitoring by legal counsel.  As a result, the necessary capabilities of counsel assisting in the formation and representation of a consortium include knowledge of antitrust laws, and the duties of such counsel at the time of formation include:

  • Evaluating the goals and contemplated activities of a prospective organization, and advising on how they may be most appropriately conducted.
  • Structuring formation documents in such a way as to protect against abusive activity, and providing for due process where needed to protect members against such abuse.
  • Advising on the most cost-effective practices for ongoing legal review, based upon the budget of the new organization.
  • Supplying appropriate antitrust policies for adoption by the Board, and antitrust memoranda suitable to alert members to prohibited conduct.

Following formation, the management of a consortium must take care to abide by the policies adopted, in order to lessen the chance of expensive mistakes. 13

III            Intellectual Property Rights

Intellectual Property Rights Policies: The second area that should be promptly addressed by adoption of a policy relates to IPR.  For decades, IPR policies for SSOs were low priority items of little interest (and remain so in many traditional industry sectors).  However, beginning with an FTC consent decree agreed to by Dell Computer in 1996, under which Dell gave up any right to charge royalties on patents it had not disclosed in the course of a standard setting activity, those participating in SSOs active in the information and communications technology (ICT) sectors began taking increasing interest in the rules to which they would become subject when they participated in a given SSO. 14

For better or worse, intellectual property rights (and particularly patents) lie at the heart of standard setting and consortium activities.  For a variety of reasons - not the least of which is avoiding liability under antitrust and other laws - it is essential for a consortium to adopt a carefully written IPR policy to govern its activities.   And then, of course, it must follow that policy, rather than relegate it to the status of a document in a drawer.

To make matters more complex, the actual terms of an IPR policy should be the opposite of what would be desired elsewhere in the commercial world.  Newcomers to standard setting must therefore reorient their thinking to accept that giving away rights in some IPR can be more advantageous than charging others for access rights to the same rights.  The biggest challenge for some lawyers can therefore be grasping the fact that standard setting is about giving away rights in some IPR in order to make money on other technology.  This means that those who would form a consortium must enter into a sort of "through the looking glass" world where patents are impediments rather than tools, royalties are unwanted encumbrances, licenses exist for the sake of disclaiming rights, and competitors are as welcome as partners.

It is very hard for many individuals that have lived their lives in the proprietary world of commercial R&D to cross this threshold.  Even among those that are expert in the area of standard setting, there is a great diversity of opinion over exactly what an IPR policy should say, although a consensus has emerged regarding what such a policy should cover.  And while many small companies take little interest in the details of an IPR policy, lawyers representing companies with large patent portfolios not surprisingly take a great interest in what the individual terms for a specific SSO IPR policy should say, as well as in the exact words used to establish those terms.  Because the stakes are so high, few large companies are willing to join a new consortium until the full and final text of the IPR policy of that organization has been agreed upon.

As a result, creating an IPR policy has become a major hurdle to clear in forming a new consortium, and can seriously delay the launch of a new organization in consequence.  A major task for the founders, and the legal counsel selected to assist them in forming a new consortium, is therefore achieving consensus as quickly as possible on the substance and text of that document. 15

In order to put an effective IPR Policy into action, commitments by members must be collected on standard forms at specified points in time during the standard setting process, and then an archive of these materials maintained on a perpetual basis.  As a result, a technical and administrative structure (often Web-based) must be created soon after formation, in order to enable the proper implementation of the IPR Policy itself. 16

Policies and Procedures of the Technical Committee: For an SSO, the companion to the IPR Policy is a detailed document setting forth all of the day by day rules of the technical process, such as notice and quorum requirements, meeting rules, chairperson duties, and so on.  This is the primary guide for the chairs of committees, and should be sufficiently comprehensive and detailed to provide all of the rules necessary to enable the technical process to function efficiently and effectively.

Prior to creating such a document, the technical structure of the organization must be designed.  For a consortium that wishes to develop and maintain a single standard, the structure will obviously be simple, comprising a single technical committee, possibly with a few working groups operating under it.  If work will commence on multiple standards from the beginning, however, attention must be paid to how any contradictions between standards that are evolving simultaneously will be addressed and resolved. 17

IV            Tax Status 18

IPR Policies :  While most consortia do not operate at any significant profit, there are benefits to obtaining tax-exempt status.  The most obvious benefit (apart from not having to pay taxes on most types of income), is that the organization is freed from the chore of seeking to "zero out" its profits at the end of each year.  By obtaining exempt status, financial planning for the organization is greatly simplified. However, if it is impossible to meet the requirements of tax exemption without restricting the activities that would permit the organization to achieve its mission, it is better to forego the small benefit that tax exemption may offer for what are, after all, the typically  more or less break-even operations of a consortium. 

It is also possible for a consortium to have it both ways – conducting its tax exempt activities through a parent organization, and its taxable operations (e.g., a trade show) through a for-profit, taxable subsidiary.

Happily, the majority of consortia can be formed as federally tax-exempt trade associations without restricting their mission or activities, most advantageously under IRS Section 501(c)(6). 19  Some consortia and SDOs have also been formed as public charities under IRS Section 501(c)(3), which offers certain advantages that are rarely advantageous for modern consortia. 20On the other hand, both federal as well as state laws are more restrictive for charities than for trade associations.  For example, a public charity in Massachusetts that wished to dissolve would be required to submit its plan of assets distribution to the state attorney general for review, and for final approval by a state court.  A trade association would  be subject to no such process, nor would it be required to obtain an annual audit at such time as its annual income crossed a certain threshold.

In order to secure tax exemption, a consortium must prepare and file a detailed application that describes its proposed activities and budget, and which must be accompanied by its bylaws, charter and other documentation.  The goal of the application is in large part to describe the "tax exempt purpose" that the organization wishes to pursue.  Since the grant of an exemption only applies conclusively to the purpose and proposed activities as described in the application and its attachments, it is important that these activities be described comprehensively.  This may mean that in some cases it is prudent to delay filing the application for up to a year, if the full range of activities of the organization may only be determined after public announcement of the new organization, and further recruitment of members. 

Eligibility rules:  A number of criteria control which types of organizations may, and may not, achieve tax exemption.

          Qualifiers: There are a number of steps that must be taken in order to obtain tax-exempt status.  As a first step, an organization must be organized in a fashion that will satisfy certain qualification criteria set forth in at least one of the various subsections of Section 501(c) of the Internal Revenue Code.  The second step is to file an application with the IRS seeking a ruling that the organization is tax-exempt.  While most people are more familiar with charitable and educational organizations exempt under Section 501(c)(3), the vast majority of technology consortia obtain their exempt status instead under Section 501(c)(6).  Section 501(c)(6) grants tax-exempt status to:

 …business leagues, chambers of commerce, real estate boards, boards of trade or professional football leagues..., not organized for profit and no part of the net earnings of which inures to the benefit of any private shareholder or individual.

The definition of a business league includes trade associations.

In order to obtain tax-exempt status under Section 501(c)(6), several tests must be me.  First, the organization has to be organized and operated as a not-for-profit.  This can be accomplished by incorporating under a nonprofit or nonstock statute.  Second, the organization cannot permit any "private inurement."  That is, the net earnings of the consortium cannot be distributed to members or shareholders either directly or indirectly (e.g., through dividends or "sweetheart" deals with members).

Private inurement is not often an issue, but it can arise where members contribute technology in exchange for royalties or license fees that the IRS deems excessive (typically in excess of an arm's-length amount).  Another context in which private inurement can arise is where a founding member provides management services in exchange for a management fee.  Again, while management and license fees are not impermissible on their face, those fees must be carefully set to avoid being in excess of what would be paid to an unrelated third party for comparable services or property.  Typically, even with careful disclosure of all details, the IRS will nevertheless request further details regarding such relationships when they are noted in the exemption application.

A consortium must also meet the definition of a business league.  The statute does not define this term, but IRS regulations and the courts have fleshed out a number of requirements that must be satisfied in order to obtain tax-exempt status under Section 501(c)(6).  Those requirements can be summarized as follows:

  • The existence of a common business interest,
  • The organization must as a primary activity promote this common business interest,
  • The activities of the entity must be directed to the improvement of business conditions of one or more lines of business,
  • The organization cannot be engaged in a regular business of a kind ordinarily carried on for profit, and
  • The primary activities of the entity must not be confined to the performance of particular services for individual members.

Notwithstanding the numerous tests that must be met in order to be classified as a trade association, the "real" test is whether the trade association is engaging primarily in the conduct of activities which benefit an entire industry as opposed to the interests of the individual members of the association only.  With most trade associations, there is a fine line between activities that benefit the specific members and activities that benefit the entire industry in which those members generally operate.  The five tests enumerated above are all geared towards making this determination.

It is the focus on standards, that have the potential to better the entire industry that typically qualifies SSOs as tax-exempt trade associations – provided that they make their standards available to non-members and members alike.   This is true even where only members are permitted to play an active role in setting the standards, and may receive a discount in the pricing of certification testing or other services relating to the standards; the reason is that these benefits are viewed as being incidental to the overall benefit to the industry.

On the other end of the spectrum, an organization that is nothing more than a joint marketing collaborative typically will not qualify as a trade association because its activities are focused on the improvement of business conditions for the individual members themselves and not for a broader industry group.  For example, if the organization promulgates and promotes standards for its members only, tax-exempt status would be difficult to achieve because the standards would simply enhance the competitive position of the members vis-à-vis the industry at large.

The existence of a common business interest is generally satisfied so long as the consortium represents an established industry and addresses at least one business issue or concern common to the members of that industry.  Where the organization represents members of multiple industries, a common business interest can still be found, provided that all of the consortium members have common issues of one type or another.  The only distinction between a situation where there is a single clear industry and a situation involving members of multiple industries is that the IRS will generally apply greater scrutiny in determining a common business interest where the membership represents more than one traditional industry.

Having found a common business purpose, the next requirement is that the organization "promote" the common business interest.  Activities that are found to be in the nature of "particular services" to the members or that are considered "unrelated" to industry promotion do not promote the common business interest of its members and weigh against exempt status.

The simplest example of "promotion" is industry marketing.  It is critical to note, however, that the marketing must be of the industry itself and not of the individual member companies.  Promotion will not satisfy this requirement where the activities are comprised of simply advertising association member companies' products.  For example, a publication consisting of paid advertisements by the association's members is a classic example of an activity that does not adequately promote an industry.

The third, fourth and fifth requirements are actually very similar and the IRS and the courts have treated them as different ways of saying the same thing.  The third requirement is the key to exemption in that the consortium activities must be directed toward the improvement of conditions of one or more lines of business, as distinguished from the performance of particular services for individual members.  This characteristic imposes two separate, interrelated requirements: (a) the organization must represent one or mores lines of business, and (b) it must not be primarily directed to performing particular services for individual purposes.

The "line of business" requirement is quite similar to the industry requirement discussed previously.  The IRS has ruled that a trade association can satisfy the "line of business" requirement even though the association members are from diverse industries or professions so long as they focus on particular business issues that are common to members of those diverse industries.

          Eligibility Disqualifiers:  The "particular services" proscription is sometimes more problematic for consortia.  The principal challenge in this area is to distinguish between association services that chiefly benefit the industry as a whole, but would also provide an incidental benefit to individual members, from those services that are chiefly of value to members and their own businesses, with the industry benefits being subordinate.

A "particular service" in this context is defined as a benefit that is merely a convenience or economy to members of an association in the operation of their individual businesses.  That is, if a trade organization provides members with a low cost, or otherwise more conveniently available service or product that its members would otherwise be expected to obtain in the normal course of their business, then the association may be found to be providing a "particular service to its members."  It has been held in one case that "any activity or service . . . which would otherwise have to be done by or for the member in order for him to properly to perform his business, must be classified as a particular service."  For example, providing insurance or consulting services to the members of an association will typically be treated as a provision of a "particular service" as these would relieve the association members of obtaining the same services on an individual basis from a non-exempt commercial business.

The mere provision of some "particular services" does not result in a loss of exempt status, but a trade association may not be "primarily" engaged in the provision of particular services.  That typically means that so long as less than 50% of the activities and revenue of the association are comprised of "particular services", then the organization may still be treated as exempt under Section 501(c)(6).  Even if exempt, however, the fees for the provision of "particular services" (or the dues allocated to those services) are typically treated as "unrelated business taxable income."  The organization will be required to pay taxes on this revenue regardless of the organization's overall exempt status.

          Process: Assuming that all qualification criteria are satisfied, the specifics of obtaining tax-exempt status are fairly straightforward.  Following formation, the consortium will file a Form 1024 with the IRS seeking a ruling that its activities result in tax-exempt status.  Unlike charitable organizations exempt under Section 501(c)(3), which are required to obtain a favorable ruling from the IRS, the statute does not require a ruling from the IRS that a Section 501(c)(6) organization is exempt.  In other words, if the organization otherwise meets all of the qualification criteria, then there is no requirement that a ruling be obtained.

Unfortunately, the IRS does not agree with this interpretation of the statute (even though it is quite clear) and takes the position that an organization cannot be exempt without a favorable ruling.

In order to avoid any dispute, it is therefore standard practice to file a Form 1024 in all cases.  This has the added benefit of providing certainty of treatment in the event of an IRS audit.  Care must be taken in preparing the Form 1024 because the ruling obtained is based strictly on the facts enumerated.  If the consortium engages in other activities, the ruling will not cover those activities and this can cause a loss of exempt status notwithstanding a favorable determination.  Accordingly, a supplemental filing should be made whenever there is a significant change in the activities or organizational structure of the consortium after the date of its original application.

          Operations as a Taxable Entity:  If exemption appears to be unlikely, or is denied on application, the consortium will be taxed in the same manner as any other taxable entity.  As a result, it is advisable to operate as nearly as possible on a break-even basis until exemption has been granted, or until a decision is made to abandon further efforts to seek exemption after one or more exchanges with the IRS examiner reviewing the exemption application without achieving success.  If that decision is made, it should be anticipated that somewhat higher compliance costs will be encountered in connection with making necessary tax filings on an ongoing basis.

V            Certification and Branding

Most technology consortia are formed to promote as well as create standards. 21 Promotion will often involve more than simply raising awareness of the existence of standards, because in order to achieve wide adoption, it is necessary for a standard to be well respected as well as well known.  This is particularly true in the case of standards created to enable interoperability of products, where such standards enable end-users to assemble systems bought from multiple vendors.  Interoperability has become doubly important with the advent of the standards-based Internet and the Web, which enable global communications and information exchange. 

Accordingly, both vendors and users place a high degree of reliance, and therefore value, on compliance with effective standards to ensure that products purchased will "plug and play."  The way in which vendors capitalize on this value can be by forming a consortium to test and certify compliance with a standard, and to create good will and brand recognition in a distinctive trademark that indicates such compliance (the "WiFi" brand is a good example).  In order to maintain value in the market recognition so created, a mechanism is needed by which the consortium can assert the legal right to prevent false assertions of compliance.
 
Consortia, like their commercial members, achieve this result by creating distinctive trademarks and logos that (in this case) relate to a given standard.  The consortium also adopts a policy which provides that these same marks may only be used in connection with products that have successfully passed whatever regime it has established to indicate compliance.  Where a vendor falsely asserts compliance with a trademarked standard, the consortium can revoke the vendor's right to use the name of the specification and any consortium logos in connection with its products.

Planning for a proper certification and trademark program is essential to the success of some consortia (e.g., where consumer products are involved).  The legal preparations for such a program include the following:

  • Conduct of conflict searches in jurisdictions of interest for the trademarks and logos to be used in connection with the program
  • Preparation and filing of national and regional trademark applications in targeted jurisdictions
  • Creation of test suites, and preparation of license agreements for such suites
  • If a third party is to be used for certification testing, negotiation of agreements with such vendor(s)
  • Preparation of trademark usage guidelines
  • Drafting of trademark licensing agreements for compliance or certification marks and logos

While trademark searches and registrations need to be undertaken at the time of formation if the related brands have been selected prior to that date, the other actions described above need not be taken until a standard has actually been completed.  Nevertheless, the later requirements should be anticipated at the time of formation, as well as any promotional expenses that will need to be incurred in connection with the program.  As a result, the need for such an initiative should be assessed before the formal launch of the consortium, and a careful assessment of the costs of such a program should be included in developing the new organization's ongoing budget. 22

VI            Summary

As the success or failure of a consortium and its standards is in large part driven by the care with which it is structured, it is important to take the time to properly form a consortium from the outset.  That structure must then be properly implemented in documentation that provides effective tools for governance, protection from liability, and flexibility of operation.  The result should be an effective platform that supports, rather than impedes, the activities of a consortium's members, and allows the new organization to grow and adapt to changing market circumstances.

The combined experience of the hundreds of already existing consortia that are in operation today has provided a number of well-tested models upon which new organizations should almost always be based.  Not only do these models offer real-world examples of successful structures and documentation, but utilizing such antecedents should facilitate recruitment of members that are already members of, and comfortable with, earlier-formed organizations.

That said, simply copying the membership structure or documents of an existing organization is no more likely to result in success than copying another SSOs standards.  In each case, and as demonstrated in the first installment of this article, the most appropriate generic model must be adapted to the goals, target membership, required activities and other unique circumstances of the new initiative, with the legal language following rather than leading the planning process.

subscribe

Comments? Email:

Copyright 2007 Andrew Updegrove

End Notes

1. Part I focused on: defining scope, determining necessary deliverables, identifying and segmenting target membership groups, creating member value propositions, developing budgets and determining appropriate dues structures, designing a staffing model, and adopting key policies among other considerations. see Updegrove, Andrew, Creating a Successful Consortium – Part I.  ConsortiumInfo.org, Consortium Standards Bulletin, Vol. V, No. 10 (November 2006), at <http://www.consortiuminfo.org/bulletins/nov06.php#feature>.  This article is one of a continuing series on creating and participating in standard setting organizations.  They are collected as the Essential Guide to Standards Setting Organizations and Standards at the ConsortiumInfo.org site, and can be found at < http://www.consortiuminfo.org/essentialguide/>.

2. It is important for readers to note that this article is summary in nature, non-specific to the law of any particular jurisdiction, and not tailored to the unique goals and circumstances of any individual situation.  Accordingly, this article is not intended, and must not be regarded as rendering legal advice to any reader, or to any consortium.  Actual legal advice should only be rendered by a qualified attorney that is given the particular facts at hand.

3.There is no universally acknowledged nomenclature for types of standards development and supporting organizations.  For example, non-accredited organizations will often have one of the following words in their names: "consortium," "forum," "alliance," or "SIG" (i.e., Special Interest Group), and such organizations are often referred to as a group by one or the same names.   For purposes of this article, all non-accredited organizations are referred to collectively as "consortia."

4. Legal issues of ongoing concern to SSOs, as compared to those that are relevant primarily at the time of formation, are dealt with in depth at the Laws, Cases and Regulations section of the Essential Guide to Standard Setting and Standards, at < http://www.consortiuminfo.org/laws/>.

5. http://www.gesmer.com/practice_areas/consortium.php#CLIENTLIST

6. Preparation of these documents can be made faster and cheaper through the use of appropriate tools.  The author uses a formation proposal template that is adapted in consultation with the client, and includes not only guidance on all variable aspects such as membership classes, but also templates for budget, public relations roll out, staffing and launch timetable.  A small working group of founders helps complete the proposal template, which is then approved by the full founder group, after which the formation documents can be easily and accurately prepared for final review by the founders and their counsel.

7. One reason that an LLC structure has sometimes been employed by organizations with limited membership is to avoid the duties that directors of a traditional corporation would have to represent the interests of all members.  Where this is the goal, language is added to the LLC operating agreement (which acts as the surrogate for corporate bylaws) that explicitly disclaims any such obligations.  As a result, each member entitled to appoint a manager of the LLC may instruct its representative to act solely in the interests of the member that appoints her.  That individual may then so act, without concerns over personal liability.

8. Two organizations that currently offer such hosting services include The Open Group and the IEEE's ISTO program. 

9. The author has often been retained to convert such organizations into incorporated entities, when the shortcomings of the original structure became apparent.

10. Degree of regulation also becomes significant when considering where to base a consortium, regardless of where it is legally formed.  For example, the same consortium that has chosen to obtain tax exemption under IRS Section 501(c)(6) as a trade association would not be required to file for a separate tax exemption in Massachusetts – but would in California.

11.The NCRPA was most recently amended in 2004, to specifically provide a measure of antitrust protection when creating standards – but only for SSOs, and not for their members.  In the opinion of this author, this amendment was as much a step backwards as forwards.  see Updegrove, Andrew, What Does 1086 Mean to Consortia?  ConsortiumInfo.org, Consortium Standards Bulletin, Vol. III, No. 6 (June 2440), at < http://www.consortiuminfo.org/bulletins/jun04.php#update>.

12. Deborah Platt Majoras, Chairman, Fed. Trade Comm’n, Recognizing the  Procompetitive Potential of Royalty Discussions in Standard Setting, address at Standardization and the Law: Developing the Golden Mean for Global Trade 7 (Stanford University, Sept. 23, 2005), <http://www.ftc.gov/speeches/majoras/050923stanford.pdf>.

13.Letter from Thomas O. Barnett, Assistant Att’y Gen., U.S. Dep’t of Justice, to Robert
A. Skitol (Oct. 30, 2006), http://www.usdoj.gov/atr/public/busreview/219380.pdf; see also Press Release, U.S. Dep’t of Justice, Justice Department Will Not Oppose Proposal by Standard-Setting Organization on Disclosure and Licensing of Patents (Oct. 30, 2006),http://www.usdoj.gov/atr/public/press_releases/2006/219379.pdf>.

14. For a very detailed review of the antitrust laws and regulations applicable to SSOs, as well as descriptions of key cases and links to the full text of laws, regulations and cases, see the Laws, Cases and Regulations section of the Essential Guide to Standard Setting and Standards, at: < http://www.consortiuminfo.org/laws/>.

15. Dell Computers, Inc., Dkt. C-3658 (consent order, May 20, 1996). This case received wide attention in the press and sharply focused the attention of many companies, for the first time, on SSO IPR policies. The FTC began its investigation when Dell attempted to enforce a patent relating to "VL-bus" technology and centered upon whether the patent was enforceable in light of the fact that, contrary to VESA's IPR policy, a Dell representative had failed to disclose the patent to the Video Electronics Standards Association ("VESA") during the VL-bus standard development process. The defendant brought numerous counterclaims and Dell ultimately settled. As part of the consent decree whose issuance ended the FTC's investigation, Dell agreed that the patents at issue would not be enforced against ML-bus standard implementers, because they had not been disclosed by Dell to VESA.

16.The author has drafted or revised IPR policies for more than 50 consortia, a process that has called upon his training as a certified mediator to a greater extent than any other aspect of his practice.  The most convincing test of whether an IPR policy has been created that is as fair as possible for all participating members can be whether everyone is equally unhappy– but can still live – with the final policy.  Truly, creating an IPR policy is the ultimate exercise in herding cats. 

17. For much more information on what an IPR policy should cover, and the variety of opinions on what individual terms should say, see the Intellectual Property Rights Policies section of the Essential Guide to Standard Setting and Standards, at < http://www.consortiuminfo.org/ipr/>.

18. For much more detail on designing an effective technical process, see the November 2004 issue of the Consortium Standards Bulletin (What Makes the Technical Process Work?), Vol. III, No.11, and particularly the Feature article, Updegrove, Andrew, Creating an Effective Technical Process (a Practical Primer), at < http://www.consortiuminfo.org/bulletins/nov04.php#feature>.

19. I am indebted to my former partner and colleague, Kenneth Appleby, for his assistance in preparing an earlier version of this section that appeared in the Essential Guide.

20. This statement demands some qualification.  But for an approximately 24-month period spanning 2002 - 2004, the author's law firm was successful in gaining tax exemption for scores of consortia, beginning in 1989.  During this brief interregnum, the senior IRS staff in its Washington office raised a number of objections that had never been raised before.  For example, the Service insisted that if more than one SSO was developing a standard for a given industry, then none of the SSOs active in that area could claim to be representing "the industry" – a requirement for achieving exemption.  As a result, in an emerging area such as wireless, no SSO would qualify for tax exemption, unless all merged into one.  Had the Service applied this same analysis to existing SSOs, many venerable SDOs as well as consortia could have been stripped of their tax-exempt status. Happily, the  IRS ceased raising this objection as suddenly (and mysteriously) as it had begun.

21.  For example, individual members of 501(c)(3) organizations may be able to deduct their membership fees, while the organizations themselves may send mailings at less than commercial postal prices.  Historically, these rights were significant for SDOs with large memberships made up of individuals.

22. Some consortia are formed exclusively for the purpose of promoting and/or certifying compliance with standards developed by other organizations (which in this situation typically are SDOs, since accredited SSOs rarely support such activities).  One of the most familiar current examples of this practice can be found in the WiFi Alliance, WiMedia Alliance, and WiMax Forum, each of which was formed to expedite the adoption of a wireless standards developed by an IEEE working group.

23.  For much more information on how to create and operate a certification and branding program,  see the Certification Testing and Branding section of the Essential Guide to Standard Setting and Standards, at < http://www.consortiuminfo.org/ipr/>.


 

FROM THE STANDARDS BLOG:

THE CONTRADICTORY NATURE OF OOXML

January 17, 2007 @ 2:57 PST
Views: 19,161

Regular readers will be aware that OOXML, the Microsoft Office XML-based formats adopted by Ecma in early December of last year, are now in the adoption queue at in the ISO/IEC Joint Technical Committee 1 (JTC1).  Ecma is a "Class A Liaison" partner of the ISO/IEC, which enables Ecma to use the same Fast Track process that national standards bodies use.  That process takes six months - the same amount of time that the Publicly Available Standard, or PAS, process takes (the route used by OASIS to submit ODF to ISO/IEC) – but has two steps rather than one.  The practical result is nevertheless much the same.

During the first one-month step, any of the c. 60 current Principal (P) and Observer (O) level members of ISO/IEC may submit "contradictions," a term which is unfortunately (as we will see) not defined, but which means aspects in which a proposed standard conflicts with (at least) already adopted ISO/IEC standards – the ambiguity then passing to what "conflicts" means, and whether only standards are of concern (as compared to, for example, ISO/IEC Directives).  Those contradictions must then be "resolved" (which does not necessarily mean eliminated), and these resolutions are then presented back to the members during the second stage to consider as part of the voting package. 

During this second, five-month step, other objections, questions and comments can be offered by not only by P and O Level members, but also by the 157 nations entitled to be heard under the rules of the World Trade Organization.  (For one interpretation of the rules relating to contradictions and what can be raised during this phase, see the excellent write up posted at the OpenDocument Fellowship site.)

While the unprecedented size of OOXML (6,039 pages, to be precise) has made performing a detailed review a daunting task, more and more issues are being found by those that are slogging their way through on this very tight timeframe.  Here is a sampling of the types of problems that people have brought to my attention:

Starting with the somewhat silly, OOXML does not conform to ISO 8601:2004 "Representation of Dates and Times."  Instead, OOXML section 3.17.4.1, "Date Representation," on page 3305, requires that implementations replicate a Microsoft bug that dictates that 1900 is a leap year, which in fact it isn't.  Similarly, in order to comply with OOXML, a product would be required to use the WEEKDAY() spreadsheet function, and therefore assign incorrect dates to some days of the week, as well as miscalculate the number of days between certain dates.

More substantively, OOXML does not follow ISO 639 "Codes for the Representation of Names and Languages."  That standard defines a list of codes that are maintained by a Registration Authority charged with keeping the list current as ethno-linguistic changes evolve.  Instead, section 2.18.52, "ST_LangCode (Two Digit Hexadecimal Language Code)" (page 2531) says that you must use a fixed list of numeric language codes rather than the already existing set that provide for interoperability among other standards-compliant products – a not unimportant factor in a text standard.

Similarly, 6.2.3.17 "Embedded Object Alternate Image Requests Types (page 5679) and section 6.4.3.1 "Clipboard Format Types" (page 5738) refer back to Windows Metafiles or Enhanced Metafiles – each of which are proprietary formats that have hard-coded dependencies on the Windows operating system itself.  OOXML should instead have referenced ISO/IEC 8632 "Computer Graphics Metafile" – a platform neutral standard.

Taking the external reference issue further, I'm told that parts of OOXML can't be implemented by your typical programmer at all without technical assistance from Microsoft, as  these sections refer not only to proprietary Microsoft products, but to undocumented parts of them as well – which violates the General Principles of ISO/IEC Directives, Part 2.  Consider the following, from section 2.15.3.26 (page 2199):

2.15.3.26 footnoteLayoutLikeWW8 (Emulate Word 6.x/95/97 Footnote Placement)

This element specifies that applications shall emulate the behavior of a previously existing word processing application (Microsoft Word 6.x/95/97) when determining the placement of the contents of footnotes relative to the page on which the footnote reference occurs. This emulation typically involves some and/or all of the footnote being inappropriately placed on the page following the footnote reference.

[Guidance: To faithfully replicate this behavior, applications must imitate the behavior of that application, which involves many possible behaviors and cannot be faithfully placed into narrative for this Office Open XML Standard. If applications wish to match this behavior, they must utilize and duplicate the output of those applications. It is recommended that applications not intentionally replicate this behavior as it was deprecated due to issues with its output, and is maintained only for compatibility with existing documents from that application. end guidance]

Typically, applications shall not perform this compatibility. This element, when present with a val attribute value of true (or equivalent), specifies that applications shall attempt to mimic that existing word processing application in this regard.

[Example: Consider a WordprocessingML document with a series of footnotes.

If this compatibility setting is turned on:

Then applications should mimic the behavior of Microsoft Word 6.x/95/97 when determining the placement of those footnotes on the displayed page, as needed. end example]

Other parts of OOXML refer to OLE, macros/scripts, encryption and DRM – none of which are fully described.  Nor has Microsoft stated whether necessary information will be supplied on a non-discriminatory basis to all (or at all).

And taking that concern a step further, consider the fact that OOXML also apparently violates section 2.14 of the ISO/IEC Directives, Part 1, in that not all of what it takes to implement OOXML appears to be covered by Microsoft's patent pledge, in two respects.

First, the pledge does not explicitly cover material that is referenced, but not included in the specification, and second, the Microsoft patent commitment does not cover optional features.   Sections of OOXML that are not fully described include those that require compliant implementations to mimic the behavior of Microsoft products, such as those products and capabilities referred to above (OLE, etc.)  Microsoft will need to clarify whether its patent commitment will in fact extend to these requirements.  Potentially, these concerns would involve large portions of OOXML, in contradiction of the ISO/IEC requirement that more than a bare-bones implementation must be permitted without fear of infringement.

All in all, as the waitress in the Monty Python vignette would doubtless have observed (if contradictions were rats), "Rather a lot, actually."  

As the February 5 deadline for reporting contradictions approaches, I expect that you'll be hearing of many more examples such as these.  Eventually, they will all become publicly available, along with the proposed resolutions.  Some, such as the patent pledge ambiguities, are clearly addressable by Microsoft if it wishes to do so.

Other contradictions would seem to be impossible to resolve given the nature of OOXML itself, the stated purpose of which is to describe a single vendor's product – bugs, rats and all.

Epilogue, added January 31, 2007:The American National Standards Institute (ANSI) is the U.S. representative to JTC 1.  For document formats, the ANSI member organization that was delegated responsibility for considering what response the US should make regarding OOXML is the International Committee for Information Technology Standards, more commonly referred to simply as "INCITS."

Yesterday, I learned that the Executive Board of INCITS decided earlier in the day not to propose to ANSI that any contradictions need be identified between OOXML and any ISO/IEC standards, Directives or other rules.  The reason is that Microsoft, which has a member on the committee, has persuaded a sufficient number of members of the Executive Board to adopt a very conservative definition for a "contradiction" – that definition being essentially that a contradiction arises only where a system could not run operate two products, each of which implemented one of the two specifications in question.  You can see the same contentions referred to in the blog of Microsoft Office Manager Brian Jones, who describes the purpose of the contradiction period, and the definition of a contradiction as follows:

[The Contradiction Period]…is where you want to make sure that the approval of this ISO spec won't cause another ISO standard to break. In the case of OpenXML, there really can't be a contradiction because it's always possible to implement OpenXML alongside other technologies. For instance, OpenOffice will soon have support for ODF and OpenXML.

An example of a contradiction would be if there was a standard for wireless technology that required the use of a certain frequency. If by using that frequency you would interfere with folks using another standard that also leverages that frequency, then there may be a contradiction.

Rather a high bar for a standard, and a low one for process quality, I should say.

Happily, it appears that INCITS will forward to the many comments that it has received to its full membership.  You can view those comments here.  Much of this input was produced as a result of a heroic effort by Groklaw's Pamela Jones and her volunteers, who set uptwo very impressive pages at Groklaw, in Wiki format. The first allows interested parties to find and log in contradictions and objections, while the second tracks the ISO/IEC process. Pamela's own detailed writeup can be found here.

All of which raises the question of whether the effort to limit the number of issues that are formally identified as "contradictions" will prove to be tactically smart or ultimately foolish? 

Given that the same input is public, and can be taken into account in the final voting, it strikes me as foolish.  When issues exist, I believe that they are better confronted than ignored.  People that have strong feelings and take the time to express them would always prefer to be heard.  And when those people are also customers, it is a risky business indeed to brush their concerns aside.

Bookmark the Standards Blog at http://www.consortiuminfo.org/newsblog/ or
set up an RSS feed at: http://www.consortiuminfo.org/rss/

Comments? Email:

Copyright 2007 Andrew Updegrove

subscribe


 

CONSIDER THIS:

[][][] January 31, 2007

#45 Product Evolution and "Standards Swarms"

Three recent news clips highlight the disorderly, but ultimately productive, way in which products and standards evolve in tandem during times of disruptive innovation.

The first clip is a press release announcing the completion of a new USB connector design standard.  A really small connector design. How small? That large object to the left of the connector in this picture  looks like a flat camera battery to me. The reason for creating the new standard is because mobile devices are getting smaller at the same time that more and more features (camera, video, music, wireless, etc.) are being crammed inside a single mobile device. As a result, the space available to accommodate a connector is rapidly diminishing.

The second article provides an update on a delayed wireless USB standard that would eliminate the need for a physical connector at all. And the third announces the completion of a new WiFi-compatible standard to make mobile security as easy to set up as the push of a button – whether you are accessing data wirelessly or physically. As the standard is extended, other wireless standards (like Near Field Communications – a very short range standard) will be supported as well.

You can expect that the devices you buy in the next year or two will use one, two or even all three of these standards.   Or you might see completely different connection and data-transfer standards in use, all chosen from what might be called a "swarm" of overlapping standards that are continuously being developed around mobile devices.  Logically, you might wonder whether this is a good thing, or simply yet another case of too many standards being created to do the same job.

In this case, I think it's the former rather than the latter.  Let's see if evolution in the physical world provides an example of why this would be so.

In a mature natural ecosystem, it's difficult for a new species to get a foothold, because every niche is already filled with one or more other creatures or plants, each of whose development has been optimized to maximally exploit that niche.  The same tends to be true in a mature commercial system as well, where launching a disruptive technology requires great coordination among competitors in order to displace an incumbent, as I pointed out in a recent blog entry, titled Standards and Disruptive Technologies.

But - in nature, this stable applecart is regularly and frequently (in geologic time, that is) upset by a variety of causes, such as dramatic climactic changes, the formation of land bridges that allow previously separated species to intermix, and massive meteorite strikes, among other events and catastrophes. On several occasions, these disasters have been sufficiently massive to result in unimaginable waves of extinction, wiping out 60% or more of all species on earth.

When this happens, speciation has a clean slate to work with, and evolution runs rampant. Countless new species evolve in weird and wonderful ways as they compete to share in the sudden wealth of opportunities. Most of these species die out over time, as the best-adapted win, and a new period of relative stasis sets in.

The same sort of process is occurring with increasing frequency in the modern world of technology, and the advent of wireless technology provides an excellent example. Once cell phones became ubiquitous, people became used to carrying a device around wherever they went. More recently, WiFi has conditioned us to want the Internet everywhere, all the time. Concurrently multiple technological advances have been made, including the ability to dramatically miniaturize all sorts of devices and features.

As a result of these convergences, a metaphorical meteorite has indeed struck the telecommunications industry, and the race has been on to exploit the new commercial niches enabled by these advances. The result? First, music players, PDAs and cell phones with enough features to require a 200 page manual, and then the increasing consolidation of all these capabilities (camera, video, computing, phone, games, music, and so on) into a single mobile device.

In this type of explosively developing environment, there's no time for everyone to agree on a single standard for every purpose – if they did, product development would grind to a halt. Nor would the best standard necessarily be agreed upon in each case. By pushing the envelope simultaneously on the technological, product and standards development fronts, more creative options are developed and tried (just as in the post-catastrophe real world), and a richer set of features and options becomes available for both vendors and customers to sample. Some of these standards and technologies will go even farther than their original proponents hoped or expected, while others will fall short. Ultimately, some will make the grade, and most of the others will die.

Another example can be found in the world of open source, where the same winnowing will doubtless occur in the not too distant future among the many Linux distributions that have dropped a bomb on proprietary operating systems. Some will find and flourish in discrete niches, while others will wither away.

This is the context in which I view the connectivity standards I noted above.  Each one, as well as others that may be announced in today's and tomorrow's news, is part of just one of the rapidly evolving standard swarms that are evolving today. In the case of data transfer, device vendors can pick and choose among multiple options and select the best solution for their particular product.  And at the same time, fierce competition will continue between the developer groups of competing standards, each of which will try to push the envelope or their contender as far and as fast as possible – something that would not happen in the absence of competition.

This rapid, albeit redundant, innovation is a good thing, and indicative of a healthy and competitive commercial ecosystem. The key, of course, is to know the difference between a stable system, where developing multiple standards to do the same job may sometimes create inefficiency and inconvenience, and a dynamically developing system.  The former situation usually leads standards developers to work on incremental improvements to existing standards, but the latter presents a classic chicken and egg paradox:  standards will be needed when the products are done, but  standards developers can't yet know exactly what  vendors and users will want to use those standards for, or exactly what those standards should be capable of doing. 

The solution?  If we launch enough initiatives, it will probably all turn out all right.

Or, to paraphrase a former first lady, in times of rapid innovation, it takes a swarm of standards to raise a new technology.

Comments? Email:

Read more Consider This… entries at: http://www.consortiuminfo.org/blog/

Copyright 2007 Andrew Updegrove