Group items tagged

SAN FRANCISCO (MarketWatch) -- Google Inc. said Wednesday that it's killing its "Google Wave" messaging and social-networking service, because of a lack of user interest.

For the first time, the majority of cellphone users access data services. That’s driven a 50 percent increase in the average data use across all users. A forthcoming study by Validas shows 53 percent of all cellphone subscribers are data users, up from 42 percent last year. The average data usage per subscriber is now 145.8MB a month compared with 96.8MB a month last year. Most of that is simply the result of more data users, though it does suggest those with data capabilities are using slightly more each month.

We started to work on HTML5 back in 2007 and have been going through issues since then. In November 2009, the HTML Chairs instituted a decision policy, which allowed us to close around 20 issues or so. We now have around 200 bugs and 25 issues on the document. In order to drive the Group to Last Call, the HTML Chairs, following the advice from the W3C Team, produced a timeline to get the initial Last Call for HTML5. The W3C team expresses its strong support to the chairs of the HTML Working Group in their efforts to lead the group toward an initial Last Call according to the published timeline. All new bugs related to the HTML5 specification received after the first of October 2010 will be treated as Last Call comments, with possible exceptions granted by the Chairs. The intention is to get to the initial Last Call and have a feature-complete document. The HTML Chairs will keep driving the Group forward after that date in order to resolve all the bugs received by October 1. The expectation is to issue the Last Call document at the end of May 2011. I encourage everyone to send bugs prior to October 1 and keep track of them in order to escalate them to the Working Group if necessary.

Microsoft, Google and other tech companies won a key victory in Washington, D.C., today as the Federal Communications Commission moved to open up vacant spectrum between television channels for unlicensed use by wireless devices -- a development expected to lead to a powerful new form of wireless Internet access.

White spaces Internet is often called “wifi on steroids” -- working in much the same way as wifi but with a potential range of multiple miles, requiring fewer access points and offering the ability to better penetrate obstructions such as walls

HTML+RDFa 1.1Support for RDFa in HTML4 and HTML5W3C Working Draft 19 October 2010

This specification defines rules and guidelines for adapting the RDFa Core 1.1 specification for use in HTML5 and XHTML5. The rules defined in this specification not only apply to HTML5 documents in non-XML and XML mode, but also to HTML4 and XHTML documents interpreted through the HTML5 parsing rules.

This specification is an extension to the HTML5 language. All normative content in the HTML5 specification, unless specifically overridden by this specification, is intended to be the basis for this specification.

Last May, we took a look at how much HTML5 compatible video is out there. 5 months on, we figured now it would be worth taking another look. HTML5 compatible video available on the web is still experiencing substantial growth & the rate of adoption is picking up. Some Discoveries We Made 54% of web video is now available for playback in HTML5. Double in 5 months.

The Worldwide Web Consortium has released the results of its first HTML5 conformance tests, and according to this initial rundown, the browser that most closely adheres to the latest set of web standards is...Microsoft Internet Explorer 9. Yes, the HTML5 spec has yet to be finalised. And yes, these tests cover only a portion of the spec. But we can still marvel at just how much Microsoft's browser philosophy has changed in recent months. The W3C tests — available here — put IE9 beta release 6 at the top of the HTML5 conformance table, followed by the Firefox 4 beta 6, Google Chrome 7, Opera 10.6, and Safari 5.0. The tests cover seven aspects of the spec: "attributes", "audio", "video", "canvas", "getElementsByClassName", "foreigncontent," and "xhtml5":

The tests do not yet cover web workers, the file API, local storage, or other aspects of the spec.

Google launched its new social Gmail experiment dubbed Buzz and the “Twitter killer” comments will be a dime a dozen. But from an enterprise perspective, Google Buzz has a far larger target in mind: Microsoft’s SharePoint.

ECMAScript 5 was released this week (pdf), generally known as JavaScript™, bringing advances to the basic libraries whilst introducing stricter runtime modes to aid with identifying and removing common coding errors.

The additions of a standard JSON parsing mechanism and strict mode will be of great benefit to developers, with the potential to translate into smaller libraries for Prototype and other extension libraries required. Parsing ISO dates from a JSON stream now becomes much more portable than before, and looks likely to be the de facto standard for representing dates in the future. Lastly, since this is backwardly compatible and takes cues from existing libraries like Prototype, it is likely that developers and web browsers alike will take to the new features of JavaScript in the near future.

We're happy to announce that over the next few weeks we will be rolling out the ability to upload, store and organize any type of file in Google Docs. With this change, you'll be able to upload and access your files from any computer -- all you need is an Internet connection.Instead of emailing files to yourself, which is particularly difficult with large files, you can upload to Google Docs any file up to 250 MB. You'll have 1 GB of free storage for files you don't convert into one of the Google Docs formats (i.e. Google documents, spreadsheets, and presentations), and if you need more space, you can buy additional storage for $0.25 per GB per year. This makes it easy to backup more of your key files online, from large graphics and raw photos to unedited home videos taken on your smartphone. You might even be able to replace the USB drive you reserved for those files that are too big to send over email.Combined with shared folders, you can store, organize, and collaborate on files more easily using Google Docs. For example, if you are in a club or PTA working on large graphic files for posters or a newsletter, you can upload them to a shared folder for collaborators to view, download, and print.

The traditional browser plug-in model has enabled tremendous innovation on the web, but it also presents challenges for both plug-ins and browsers. The browser plug-in interface is loosely specified, limited in capability and varies across browsers and operating systems. This can lead to incompatibilities, reduction in performance and some security headaches.That’s why we are working with Adobe, Mozilla and the broader community to help define the next generation browser plug-in API. This new API aims to address the shortcomings of the current browser plug-in model. There is much to do and we’re eager to get started.

As a first step, we’ve begun collaborating with Adobe to improve the Flash Player experience in Google Chrome. Today, we’re making available an initial integration of Flash Player with Chrome in the developer channel. We plan to bring this functionality to all Chrome users as quickly as we can.We believe this initiative will help our users in the following ways:When users download Chrome, they will also receive the latest version of Adobe Flash Player. There will be no need to install Flash Player separately.Users will automatically receive updates related to Flash Player using Google Chrome’s auto-update mechanism. This eliminates the need to manually download separate updates and reduces the security risk of using outdated versions.With Adobe's help, we plan to further protect users by extending Chrome's “sandbox” to web pages with Flash content.

This is a heads-up that we will shortly start landing patches for a new WebKit framework that we at Apple have been working on for a while. We currently call this new framework "WebKit2". WebKit2 is designed from the ground up to support a split process model, where the web content (JavaScript, HTML, layout, etc) lives in a separate process. This model is similar to what Google Chrome offers, with the major difference being that we have built the process split model directly into the framework, allowing other clients to use it. Some high-level documentation is available at http://trac.webkit.org/wiki/WebKit2 Currently WebKit2 is available for Mac and Windows, and we would gladly accept patches to add more ports.

In a previous post, I'd wondered why Adobe didn't spend their time building HTML5 Authoring tools rather than putting so much time/energy/money into their  Flash->iPhone Apps exporter tool for Flash CS5.   As it turns out, Adobe does have some, albeit rudimentary, HTML5 Canvas exporting tools as demonstrated in the video above.   Taking a simple animation, which is the beginning, middle and end of most Flash banner ads that we love, is an export/paste operation.

EU governments should use open standards and interoperable systems to deliver electronic government services, EU ministers and the European Commission agreed earlier this week. They also stated they would promote the reuse of public sector information. The ministers declared to "embed innovation and cost effectiveness into eGovernment through the systematic promotion of open standards and interoperable systems, development of EU wide e-authentication schemes and proactive development of e-invoicing, e-procurement and pre-commercial procurement."It was one of 29 points agreed upon during a meeting of all ministers responsible for information society from European member states and the European Commissioner for the Digital Agenda.

Open standards are an important element in many open source applications, as these are freely accessible. Development of this type of software can run into problems when using closed standards or when using standards that require payment of royalties. Such standards may change unexpectedly or limit how the software can be used.

Granada declaration (pdf)

On October 06, 2008, OASIS issued a public call for participation in a new technical committee chartered to define specifications for use of Web services and Web 2.0 interfaces to enable information sharing across content management repositories from different vendors. The OASIS Content Management Interoperability Services (CMIS) TC will build upon existing specifications to "define a domain model and bindings that are designed to be layered on top of existing Content Management systems and their existing programmatic interfaces. The TC will not prescribe how specific features should be implemented within those Enterprise Content Management (ECM) systems. Rather it will seek to define a generic/universal set of capabilities provided by an ECM system and a set of services for working with those capabilities." As of February 17, 2010, the CMIS technical work had received broad support through TC participation, industry analyst opinion, and declarations of interest from major companies. Some of these include Adobe, Adullact, AIIM, Alfresco, Amdocs, Anakeen, ASG Software Solutions, Booz Allen Hamilton, Capgemini, Citytech, Content Technologies, Day Software, dotCMS, Ektron, EMC, EntropySoft, ESoCE-NET, Exalead, FatWire, Fidelity, Flatirons, fme AG, Genus Technologies, Greenbytes GmbH, Harris, IBM, ISIS Papyrus, KnowledgeTree, Lexmark, Liferay, Magnolia, Mekon, Microsoft, Middle East Technical University, Nuxeo, Open Text, Oracle, Pearson, Quark, RSD, SAP, Saperion, Structured Software Systems (3SL), Sun Microsystems, Tanner AG, TIBCO Software, Vamosa, Vignette, and WeWebU Software. Early commentary from industry analysts and software engineers is positive about the value proposition in standardizing an enterprise content-centric management specification. The OASIS announcement of November 17, 2008 includes endorsements. Principal use cases motivating the CMIS technical work include collaborative content applications, portals leveraging content management repositories, mashups, and searching a content repository.

That's certainly one reason Microsoft still holds a giant lead in market share.

The White House is requiring federal agencies to consider using a standard configuration developed by the Justice and Homeland Security departments to share information across the public and private sectors. More than a month ago, the Office of Management and Budget issued guidance to agencies on the website of the National Information Exchange Model, a joint DOJ-DHS program. The OMB document, which is not posted on its website, includes instructions for assessing the framework's merits by May 1. "All agencies shall evaluate the adoption and use of the National Information Exchange Model as the basis . . . of reusable cross-boundary information exchanges," said an enclosed memo from Kshemendra Paul, the federal chief architect. "The Office of Management and Budget is working jointly with the NIEM Program Management Office to provide guidance and the tools necessary to help you meet this requirement."

NIEM launched in 2005 with the goal of linking jurisdictions throughout the country to better respond to crises, including terrorist attacks, natural disasters, large-scale crime and other emergencies handled by Justice and Homeland Security. The standards are intended to expedite the secure exchange of accurate information.

On 7 November 2008, the directors of the law libraries at the University of Chicago, Columbia University, Cornell University, Duke University, Georgetown University, Harvard University, New York University, Northwestern University, the University of Pennsylvania, Stanford University, the University of Texas, and Yale University met in Durham, North Carolina at the Duke Law School. That meeting resulted in the "Durham Statement on Open Access to Legal Scholarship," which calls for all law schools to stop publishing their journals in print format and to rely instead on electronic publication coupled with a commitment to keep the electronic versions available in stable, open, digital formats.

Particularly now, with growing financial pressures on law school budgets, ending print publication of law journals deserves serious consideration. Very few law journals receive enough in subscription income and royalties to cover their costs of operation. The Statement anticipates both that the costs for printing and mailing can be eliminated, and that law libraries can reduce their costs for subscribing to, processing, and preserving print journals. There are additional benefits in improving access to journals that are not now published in open access formats and in reducing paper consumption.

Call to Action: We therefore urge every U.S. law school to commit to ending print publication of its journals and to making definitive versions of journals and other scholarship produced at the school immediately available upon publication in stable, open, digital formats, rather than in print. We also urge every law school to commit to keeping a repository of the scholarship published at the school in a stable, open, digital format. Some law schools may choose to use a shared regional online repository or to offer their own repositories as places for other law schools to archive the scholarship published at their school. Repositories should rely upon open standards for the archiving of works, as well as on redundant formats, such as PDF copies. We also urge law schools and law libraries to agree to and use a standard set of metadata to catalog each article to ensure easy online public indexing of legal scholarship. As a measure of redundancy, we also urge faculty members to reserve their copyrights to ensure that they too can make their own scholarship available in stable, open, digital formats. All law journals should rely upon the AALS model publishing agreement as a default and should respect author requests to retain copyrights in their scholarship.