Gary Edwards's Library tagged openweb →  View Popular

In closing, we are here because 40 years ago, a bunch of researchers in a lab changed the way computers interact and, as a result, changed the world. We are here because those Internet pioneers had unique insights about the power of open networks to transform lives for the better, and they did something about it. Our work now is to preserve the brilliance of what they contributed to our country and the world. It’s to make sure that, in the 21st century, the garage, the basement, and the dorm room remain places where innovators can not only dream but bring their dreams to life. And no one should be neutral about that.

openinternet.gov/read-speech.html - Preview

fcc openweb neutrality

Javascript has a major advantage of being (likely) the most installed programming language in history. It’s experiencing a renaissance lately where people actually learning it, not just copying code found on someone’s website. ECMAScript Harmony will bring some much needed fixes to the language (although I think ECMAScript 4 would have been a true game-changer for the web). Regardless, until we have more mature tools for sever- and DB-side javascript, Javascript is really a browser language (and faces an army of entrenched programmers who’d rather use some other language).

To the second argument, I say: Javascript is an amazing language, but you can’t declare it off limits to people who prefer other languages. Programming is about choice. On the server we get to use whatever combinations of web server, database, programming language, and development environment we like. Not so for the browser. We’re stuck with Javascript whether we like it or not. We can’t stay away from it, we can’t use something else. Everyone who dislikes working in Javascript is perfectly justified because he has no other avenue. When all browsers support and are prepackaged with VMs for many languages, I’ll be the first to sound the clarion: if you don’t like JS, get the hell away from it. Until then, you’re stuck with us and we’re stuck with you.

To the third: again, it’s really all about to choice. If you prefer Javascript keep using it, make it better, steal ideas from other languages, and seed the community with new ideas of your own. Nobody will complain about a better overall development community. If you’d like to see Red in Python, PHP, C#, or language X then steal Jesse’s code. Red was a herculean effort on Jesse’s part. I know he’s worked on nothing else for two months and future ports of Red to other languages will benefit from this effort.

wonderfullyflawed.com/...l-ruby-runtime-in-your-browser - Preview

javascript ruby Openweb

For most of this decade, web developers have been suffering the shortcomings of Internet Explorer. Like 1998 limited HTML-CSS support.  And nothing for the language of the Web - HTML+ :: HTML5, CSS3, SVG/Canvas and advanced JavaScript.  That hasn't bothered Microsoft (NSDQ: MSFT) too much, because the company has historically focused on developing "real" applications that run only on Windows and don't use the browser as a platform. With the new Office web apps, many thought that Microsoft might actually have to experience the living nightmare that web app development can be. Yet the company has figured out a way to make things easier: cheat.  

MIcrosof thas figured out how to provide MSOffice as Web Apps, without having to use the language of the Web: HTML+.  Instead, they use protpietary formats, protocols and interfaces to create an interesting dichotomy - a rich MS-Web, and a poor, 1998 Open-Web.

www.informationweek.com/...JSORXIUMXLBQE1GHOSKH4ATMY32JVN - Preview

web-apps microsoft msoffice silverlight Openweb

What Web business systems really need are advanced desktop editors capable of producing business process rich compound documents in the language of the Web: HTML5/CSS3/JavaScript........

industry.bnet.com/...productivity-moving-to-the-web - Preview

OpenOffice OpenWeb HTML+ Producitivity unified-productivity

Dion Hinchcliffe has posted a lengthy discussion on the future of Open Data and the Open Web.  He identifies three Open Web methods for accessing and working with Open Data; WOA, API's and Linked Data.  These methods are discussed in the context of SOA and the re-engineering of enterprise business systems.  Great stuff.  Dion also provides an excellent chart describing his vision of how these things fit together.

Excerpt: "Open data holds up the promise of instant connectivity between arbitrary numbers of ad hoc partners while at the same time reducing integration costs, improving transparency, harnessing external innovation, and even (perhaps especially) creating entirely new and significant business models. I sometimes refer to these as “open supply chains“, and the term is highly descriptive when it comes to the potential for open data models to make cloud computing safe and interoperable, help journalists to do their jobs better, or create multi-million dollar new lines of business, such as Amazon’s well-known Web Services division."

blogs.zdnet.com/Hinchcliffe - Preview

woa openweb opendata enterprise soa dion-hinchcliffe semantic-web

Some good commentary on chrome OS from InformationWeek's Thomas Claburn.

Excerpt: With Chrome OS, Google aims to make the Web the primary platform for software development.......

The fact that Chrome OS applications will be written using open Web standards like JavaScript, HTML, and CSS might seem like a liability because Web applications still aren't as capable as applications written for specific devices and operating systems.

But Google is betting that will change and is working to effect the change on which its bet depends. Within a year or two, Web browsers will gain access to peripherals, through an infrastructure layer above the level of device drivers. Google's work with standards bodies is making that happen.....

..... According to Matt Womer, the "ubiquitous Web activity lead" for W3C, the Web standards consortium, Web protocol groups are working to codify ways to access peripherals like digital cameras, the messaging stack, calendar data, and contact data.

There's now a JavaScript API that Web developers can use to get GPS information from mobile phones using the phone's browser, he points out. What that means is that device drivers for Chrome OS will emerge as HTML 5 and related standards mature. Without these, consumers would never use Chrome OS because devices like digital cameras wouldn't be able to transfer data.

Womer said the standardization work could move quite quickly, but won't be done until there's an actual implementation. That would be Chrome OS......

..... Chrome OS will sell itself to developers because, as Google puts it, writing applications for the Web gives "developers the largest user base of any platform."

www.informationweek.com/...showArticle.jhtml - Preview

chromeOS OpenWeb Google HTML+ W3C

Michael Hickens has been writing about Google Wave and how it will forever change the Web. In a recent article he took on the incredible WebKit - HTML+ phenomenon, tying in the surge of WebKit marketshare at the edge of the Web with dramatic changes taking place across greater Web.
<br>

From Michaels article: .... "I recently described how Google's Wave, a collaboration tool based on the new HTML 5 standard, demonstrated the potential for Web applications to unglue Microsoft's hold on customers. My post quoted Gary Edwards, the former president of the Open Document Foundation, a first-hand witness to the failed attempt by Massachusetts to dump Microsoft and as experienced a hand at Microsoft-tilting as anyone I know......"
<br>
The year 1998 marked the end of the browser wars, the end of Netscape, and the beginning of Microsoft's anti-trust woes. It also marked the beginning of XML, and the end of HTML, with the W3C leaving HTML, CSS and SVG to rot. What a year.

<br>
Today we find the landscape considerably changed. Instead of a browser war between Netscape and Microsoft, ending with the triumph of an IE monopoly, today we have a browser race. And IE isn't a contender, having been pretty much abandoned by Microsoft once they had Netscape in the dirt.

<b>
The introduction of XML 1.0 in 1998 ushered in a new era of customized XML schema's for all kinds of data exchanges. The Web came alive with data flows from disparate databases and transaction systems that were never designed to talk to each other. The noise across the Web, private and public, was deafening.

<br>
There was however a few notable attempts to encode document based content in XML, with OpenOffice ODF and MSOffice OOXML taking center stage. Unlike the excitement and extraordinary Web capabilities that surrounded XML data schema work, XML documents veered away from the Web. By design, ODF and OOXML are incompatible with the language of the Web. But given the legacy of client/server dominance powerful "end-user-facing" desktop office

industry.bnet.com/...-fight-starts-with-smartphones - Preview

openweb michael-hickens webkit ge HTML5 HTML+ CSS3 JavaScript google-wave iphone android

Excellent presentation discussing the AtomPub protocol as a key Open Web API . 52 slides, and everyone worth some study.

www.slideshare.net/...atompub-beyond-blogs - Preview

AtomPub OpenWeb HTML+ HTTP Restfull-computing Cloud-Computing

More comments from ge

www.fiercecio.com/...2009-06-05 - Preview

openweb webkit replace_or_re-purpose msoffice

A new report by research analyst, Forrester says that 80 percent of enterprise customers are using some version of Microsoft Office. This reflects the stranglehold Microsoft has on the office productivity market, despite increased awareness of alternatives such as Sun's OpenOffice.org suite, and the rise of web-hosted variants such as Google Docs.

I had a chance to comment on this brief lament regarding Microsoft's iron grip, desktop monopoly.

www.fiercecio.com/...2009-06-05 - Preview

ge MSOffice replace_or_re-purpose openWeb webkit

<i>....."With Wave, which Google previewed for developers at its I/O conference yesterday, developers can for the first time create Web-based applications that compete with Microsoft in terms of quality (while utterly trumping it on price). It also creates the conditions for customers to comfortably shuck off the shackles of installed software — including Office and other Microsoft products — in exchange for truly lightweight hardware like netbooks or advanced smartphones, without sacrificing the richness of their computing experience. If it gets the kind of developer love it should, Wave is just the first of a series of a breakers that will loosen Microsoft’s grip on the desktop, and may also render Adobe wholly irrelevant."</i>

<i> .... "Wave is a Web-based application that breaks artificial barriers between document types; work documents, email, instant messages, photographs, maps — Wave makes no functional distinction between them, and allows users to literally drag all those elements into a single, shareable meta-document. Wave is written using HTML 5, the first significant change to standards for Web coding since 1998. HTML 5 also forms the basis for Webkit, the language underlying the operating systems of the vast majority of smartphone browsers — Apple’s iPhone, Research in Motion’s BlackBerry, Google’s Android, Palm’s WebOS and Nokia’s Symbian. The one glaring omission? Microsoft Windows Mobile, of course.............. "</i>

industry.bnet.com/...le-wave-crashes-over-microsoft - Preview

openweb michael-hickens google-wave

Some interesting questions about Google Wave; proposed by Om Malik and Jordan Golson, but with some hesitant reservations. As the title of this nervous commentary suggests. The narrowness and shallow context of this article is to be expected from hapless back-benchers incapable of grasping the big picture. But GigaOM? What a surprise. Maybe i should be revising my Silicon Valley information feeds?

Google is into it with Microsoft, and for the sake of the future of the OpenWeb, Google better win. How does anyone able to fog a mirror miss this? Incredible.

"..... Has Google, with its latest project, Google Wave, actually come up with the Next Big Thing in online communication, or is it yet another Googler vanity exercise? Wave is a combination of email, instant messaging and a real-time wiki — plus open architecture and APIs. Or as creators Lars and Jens Rasmussen and Stephanie Hannon put it, “what email would be if it were invented today.”

Om also points out another comment from Lars: <i>“Email is the most successful protocol on the planet…we can do better.” </i>

I think Google Wave is in the center of a number of revolutionary Google initiatives advanced at the recent Google I/O. HTML 5, the Canvas Tag, O3D, and the assault on the x86 Microsoft desktop stronghold are all part of Google's greatest challenge; keeping the Open Web free and competitive with the emerging MS Web.

Michael Hickens has an interesting article;<i><b> <a href="http://industry.bnet.com/technology/10001911/google-wave-crashes-over-microsoft/">Google Wave Crashes Over Microsoft"</a></b></i>. Michael spoke with me prior to publishing, and i gave him my cosmic viewpoint of how things fit together (or not). You can find a loose summary of our discussion here: <i><b><a href="http://docs.google.com/View?id=dghfk5w9_7hptc6vfn">Google Wave: Crashing the Microsoft Desktop Monopoly</a></b></i>. Clearly i am still writing :)

gigaom.com/...heights-of-arrogance-with-wave - Preview

google-wave html5 html+ OpenWeb

Dion has lots to say about the recent Web 2.0 Conference. In this article he covers nine significant announcements from companies specializing in Web based mashups and the related tools for building ad hoc Web applications. This years Web 2.0 was filled with Web developer oriented services, but my favorite was MindTouch. Perhaps because their focus was that of directly engaging end users in the customization of business processes. Yes, the creation of data objects is clearly in the realm of trained developers. And for sure many tools were announced at Web 2.0 to further the much needed wiring of data objects. But once wired and available, services like MindTouch i think will become the way end users interact and create new business productivity methods. Great coverage.
<br><br>
"...... For awareness and understanding of the fast-growing world of mashups are significant challenges as IT practitioners, business strategists, and software vendors attempt to grapple with what’s facing up to be the biggest challenge of all: The habits and expectations of the larger part of a generation of workers who don’t yet realize mashups are poised to change many things about the software landscape on the Web and in the workplace. Generational changes can be difficult for businesses to embrace successfully, and while evidence that mashups are remaking the business world are still very much emerging, they certainly hold the promise..."
<br><br>
".... while the life of the average Web developer has been greatly improved by the availability of a wide variety of useful open APIs, the average user of the Web hasn’t been a direct beneficiary except through the increase in Web apps that are built on the mashup model. And that’s because the tools that empower users to weave together existing Web parts and open APIs into the exact solutions they need are just now becoming easy enough and robust enough to readily enable these scenarios. And that doesn’t include the variety of tooling and infrastructure that makes producing the sourc

blogs.zdnet.com/Hinchcliffe - Preview

OpenWeb mashup enterprise20 web20 dion-hinchcliffe

Excellent review of evolving Open Web Standards for Cloud Computing. Dion covers OpenSAM, OpenAjax, Smash, and a number of other efforts to standardize the mashup space.

"..... mashups have enormous potential to allow more rapid and much less expensive development of online applications by emphasizing assembly over development, economies of scale by enabling high levels of reuse, and the consequent ability to rapidly get software solutions with the right data in the right place at the right time...."

blogs.zdnet.com/Hinchcliffe - Preview

OpenWeb mashup enterprise20 dion-hinchcliffe

I reformatted my response to marbux concerning HTML5 and web application lack of interoperability. The original article these comments were posted to is titled, <a href="http://mondaybynoon.com/2008/06/30/siding-with-html-over-xhtml-my-decision-to-switch/#comment-2042">"Siding with HTML over XHTML, My Decision to Switch.... "</a>.

docs.google.com/Doc - Preview

webkit OpenWeb HTML5 RiA CSS3 WHATWG W3C

Lengthy artilce from the OpenAjax Alliance summarizing HTML, Ajax and the future of the Open Web. Very well referenced. Lots of whitepapers and links

www.openajax.org/...rowser%20Wars%20Are%20Back.php - Preview

ajax openweb acid webkit