| By Web 2.0 News Desk | Article Rating: |
|
| August 5, 2008 10:45 AM EDT | Reads: |
2,398 |
The SEC has finally acknowledged that the nature of online information is increasingly interactive, and not static. Henceforth, according to a recommendation by its own Special Counsel in the SEC's Division of Corporation Finance, information appearing on company web sites "does not need to satisfy a printer-friendly standard or be in a format comparable to paper-based information, unless the Commission’s rules explicitly require it."
As a service to readers we bring you a speech by the counsel in question, Kim McManus, in full:
Washington, D.C.
July 30, 2008
'Good morning. Today we are recommending that the Commission issue an interpretive release to provide additional guidance and greater certainty on how companies can use their web sites to provide information to investors in compliance with the federal securities laws, particularly with respect to the Securities Exchange Act of 1934. The interpretive guidance addresses four main topics:
- When information posted on a company web site is “public” for purposes of the applicability of Regulation FD;
- Company liability for information on company web sites – including previously posted information, third-party hyperlinks, summary information and the content of interactive web sites;
- The types of controls and procedures advisable with respect to such information; and
- The format of information presented on a company web site, with the focus on readability, not printability.
Whether information posted on a company web site is “public” for purposes of Regulation FD impacts both the analysis of the applicability of Regulation FD to subsequent discussions or disclosure of the posted information with an enumerated person in Regulation FD and satisfaction of Regulation FD’s “public disclosure” requirement. In evaluating whether information is “public” for purposes of the applicability of Regulation FD to subsequent discussions or disclosure, companies must consider whether and when:
- a company web site is a recognized channel of distribution;
- posting of information on a company web site disseminates the information in a manner making it available to the securities marketplace in general; and
- there has been a reasonable waiting period for investors and the market to react to the posted information.
The release provides non-exclusive factors for companies to consider in evaluating the satisfaction of these conditions, including the manner in which information is posted on a company web site and the timely and ready accessibility of such information to investors and the markets.
The guidance also addresses circumstances in which, for certain companies under certain circumstances, posting non-public material information on a company’s web site, in and of itself, may be a sufficient method of “public disclosure” for purposes of satisfying the alternative public disclosure provision of Regulation FD. In evaluating whether and when postings on their web sites are “reasonably designed to provide broad, non-exclusionary distribution of the information to the public,” the guidance provides that companies would need to consider whether the company web site is a recognized channel of distribution and whether the information is “posted and accessible” and, therefore, “disseminated.” As part of that evaluation, companies also would need to consider their web sites’ capability to meet the simultaneous or prompt timing requirements for public disclosure under Regulation FD.
The release addresses certain issues that continue to arise under the antifraud provisions regarding the use of company web sites.
First, the release updates current guidance regarding the effect of accessing previously posted materials or statements on company web sites so that such previously posted materials or statements would not, without more, be considered reissued or republished for purposes of the antifraud provisions of the federal securities laws, including any duty to update such information.
Second, the release provides further guidance on how companies can hyperlink to third-party web sites without “adopting” the third-party information for liability purposes. The guidance suggests, among other things, that companies explain the context for the hyperlink to make clear why the hyperlink is being provided, be aware that selective choices to hyperlink to specific third-party information may indicate that the company has a positive view or opinion about that information, and consider using other methods to denote that the hyperlink is to third-party information.
Third, the release provides guidance for companies that provide summaries of information on their web sites in the context of the antifraud provisions including techniques that companies can use to highlight the summary nature of the information provided.
And fourth, the release addresses antifraud issues that may arise when issuers, their officers, and employees speak on company-sponsored blogs or electronic shareholder forums. In particular, it provides guidance for companies hosting or participating in blogs or electronic shareholder forums about the applicability of the antifraud provisions to statements made by the company or by a person acting on behalf of the company. It also highlights the restrictions on a company’s ability to require investors to waive protections under the federal securities laws as a condition to entering or participating in a blog or forum.
The release also provides guidance about the extent to which “disclosure controls and procedures” apply to statements on company web sites and helps to clarify the boundaries of disclosure controls and procedures, since companies must disclose whether their disclosure controls and procedures are effective.
Finally, the release acknowledges that the nature of online information is increasingly interactive, and not static. The release, therefore, makes clear that information appearing on company web sites does not need to satisfy a printer-friendly standard or be in a format comparable to paper-based information, unless the Commission’s rules explicitly require it.
If approved, the interpretive release and guidance will be effective upon publication in the Federal Register.'
Published August 5, 2008 Reads 2,398
Copyright © 2008 SYS-CON Media, Inc. — All Rights Reserved.
Syndicated stories and blog feeds, all rights reserved by the author.
More Stories By Web 2.0 News Desk
The Web 2.0 Journal News Desk keeps you up to speed with all that's happening in the world of the read/write Web and all its mushrooming new facets - from tagging, wikis, mash-ups, and image-sharing to "Advertising 2.0," podcasting, and The Writeable Web.
- Kindle 2 vs Nook
- Why IBM’s Server Chief Got Busted
- Is Cloud Computing Like Teenage Sex?
- Industry Experts Discuss the State of Cloud Computing
- Performance Tuning Essentials for Java
- Confessions of a Ulitzer Addict
- Tactical Cloud Computing Panel at 1st Annual GovIT Expo
- It's the Java vs. C++ Shootout Revisited!
- Cloud Computing Can Revitalize Your Career as Software Developer
- IBM Could "Reinvent" Java: Mills
- Oracle & Cloud Computing: Exclusive Q&A with SVP Richard Sarwal
- A Brief History of Cloud Computing
- Kindle 2 vs Nook
- Cloud CEOs, CTOs & SVPs to Speak at 4th International Cloud Computing Expo
- Why IBM’s Server Chief Got Busted
- Is Cloud Computing Like Teenage Sex?
- Industry Experts Discuss the State of Cloud Computing
- Performance Tuning Essentials for Java
- The Difference Between Web Hosting and Cloud Computing
- Cloud Computing Expo: Exclusive Q&A with Yahoo! SVP Cloud Computing
- Ajax in RichFaces 3.3, JSF 2 and RichFaces 4
- Confessions of a Ulitzer Addict
- My Thoughts on Ulitzer
- Tactical Cloud Computing Panel at 1st Annual GovIT Expo
- A Cup of AJAX? Nay, Just Regular Java Please
- Java Developer's Journal Exclusive: 2006 "JDJ Editors' Choice" Awards
- The i-Technology Right Stuff
- JavaServer Faces (JSF) vs Struts
- Rich Internet Applications with Adobe Flex 2 and Java
- Java vs C++ "Shootout" Revisited
- Bean-Managed Persistence Using a Proxy List
- Reporting Made Easy with JasperReports and Hibernate
- Creating a Pet Store Application with JavaServer Faces, Spring, and Hibernate
- What's New in Eclipse?
- Why Do 'Cool Kids' Choose Ruby or PHP to Build Websites Instead of Java?
- i-Technology Predictions for 2007: Where's It All Headed?








































