All well and good. Then again, I've found the Computer Science literature to be abysmal - for pretty much forever. IMHO, there isn't a single journal that comes close to the quality of papers published in "Science," or "J. of the AMA." I turned off my ACM & IEEE journal subscriptions, years ago.
The good stuff used to be in things like MIT AI Lab Memos, BBN Technical Reports, RFCs, theses, and such. The good presentations are at trade shows - and more likely to be in exhibitor booths, and part of show floor demonstrations (the old INTEROP shownets, the LVC demonstrations at I/ITSEC conferences).
Personally, I'm a lot more concerned with the review processes for grant & contract proposals - where there's real money on the table, and achieving solid results can be mission- and sometimes life-critical.
We're trying to use a standardized document format. Building on Atom. Should be able to read serialized format in any blog reader. Microformats will be used to add structure, and JavaScript library will take feed, order elements, and select versions for presentation. Add a little CSS for additional presentation elements (e.g., of an action item list).
If you want to trust everything to Google, and you have reasonable connectivity to Google. Works for a lot of cases, but for things like emergency response and military operations (key targets for the work), one is often working with low-bandwidth, intermittent, mesh networks - choice is set up your own server, or go with a P2P approach, as we are. Also, Google Docs doesn't really do much for version control or allow any kind of process to be added. Now GitHub or Fossil might be better comparisons, but those are oriented toward software development rather than more general purpose document management.
I wish I were a better video producer. Unfortunately, that started to suck up way to much time, and it seemed better to launch. (It's the old argument - do you put time into fancy PowerPoint slides, or into the project itself.)
Two reasons:
1. a lot of us like having our own local copies of things (the same rational as Git, when talking a version control system).
2. a lot of use cases REQUIRE a local copy, to support disconnected operations (working on airplanes, working in remote areas with poor connectivity)
The good stuff used to be in things like MIT AI Lab Memos, BBN Technical Reports, RFCs, theses, and such. The good presentations are at trade shows - and more likely to be in exhibitor booths, and part of show floor demonstrations (the old INTEROP shownets, the LVC demonstrations at I/ITSEC conferences).
Personally, I'm a lot more concerned with the review processes for grant & contract proposals - where there's real money on the table, and achieving solid results can be mission- and sometimes life-critical.