Wednesday, June 10, 2009

What's your (STM) openness strategy?

Here is Yahoo's

The Yahoo! Openness Strategy Team is building the next generation of open platforms and integrating them into every part of Yahoo!. From platforms that add a social element to every aspect of Yahoo!, to an applications platform and developer-focused offerings, the YOS team is tasked with transforming the way Yahoo! works. In building out all the components of YOS, the team is focused on implementing distributed systems that are highly scalable and performant so they can reliably serve hundreds of millions of Yahoo! users and developers every day. Via Yahoo
UK government goes to Tim Berners Lee to help them in their initiative to open up the government data.

Monday, June 08, 2009

Researcher Waveflow

Cameron Neylon provides concrete examples how STM publishers can get into the Google Wave. Cameron will be talking to a group of product managers and publishing colleagues next week in Amsterdam.

Monday, June 01, 2009

Making the Waves

Some wave related links

"As traditional content and software publishers continue to try to wrestle the Web into one proprietary box after another to suit their established business models, it's important to remember that the world is aching to have cost-effective productivity improvements that will help to boost the global economy. Wave is a good example of a content technology that has the potential to sweep aside many drags on Web and enterprise productivity in ways that can help to create and to contextualize content in more valuable ways than ever before." John Blossom

"As I understand it each wave, and indeed each part of a wave, can be a URL endpoint; an object on the semantic web. If they aren’t already it will be easy to make them that. As much as anything it is the web native collaborative authoring tool that will make embedding and pass by reference the default approach rather than cut and past that will make the difference. Google don’t necessarily do semantic web but they do links and they do embedding, and they’ve provided a framework that should make it easy to add meaning to the links. Google just blew the door off the ELN market, and they probably didn’t even notice." Cameron Neylon

And yes we will see extension on the wave soon

"Having had a look at the editing capabilities of Google Wave, it is clear that one of the first things we as scientists should do is to add collaborative reference management and figure/table numbering to the rich text editing capabilities. Martin Fenner lists this feature on his blog post and we're discussing it at FriendFeed. Of course, collaborative editing doesn't stop at papers: grants, lab-wikis, institute websites, manuals, protocols, fridge content, who's up for journal club?, which machine is currently broken/working, where is item X?, who's going to the conference? Which posters are you going to look at?.... the list goes on and on! Google Wave has solutions for all of these processes - today." Bjoern Brembs


" I hope that by that time it will also have the first extensions designed specifically for scientists, e.g. for

  • references with embedded metadata and discussions about these references
  • molecular structures and other scientific data types
  • scientific manuscripts in progress (Google Wave has nice tools for collaborative document editing)
  • lab notebooks (again because of the wiki-like editing features)" Martin Frenner



As Victor from Mendeley indicates very soon we will see wave extension that will help scientists in their workflow.

OCLC Mashathon


OCLC brings library developer community together to create new tools on top of OCLC APIs

"This is such a great way to bring the library development community together," explained Roy Tennant, one of the founders of the OCLC Developer Network. "We are so pleased with the creativity of the implementations and expect the tools created these two days to continue delivering long-term value for libraries and library users around the world." Via OCLC


The above figure created by Tim McCormick in "A Web Services Taxonomy: not all about the data" should make us think of what we can do to move our products to the "high value transactional" quadrant. Opening up and creativity from the development community will be key elements of developing these high value transactional applications.