Group items tagged

This paper sets out to describe a version of infrastructure or foundation for VRM (Vendor Relationship Management) based on an alternative view on sharing information online between individuals and of online identity. It sets out to explain the strategy and tactics for design, development and adoption of tools - the Mine! and FeedMe (see glossary) - and creation of an infrastructure for other solutions - VRM (relationships with individuals and vendors, transactions), self-defined identity, authentication, data portability and hopefully many more. The aim is to equip individuals with tools to take charge of their data (content, relationships, transactions, knowledge), arrange (analyse, manipulate, combine, mash-up) them according to their needs and preferences and share them on their own terms whilst connected and networked on the web.

MOAT Server is a application that serves tag meanings (in HTML, JSON or RDF/XML, using content negociation) for any Tag you request. The server is shipped without any data, which means that users have first to define meanings for their tags (thanks to the clients they use, that will then update the server information) to efficiently use it, using data available on the Semantic Web, especially from the Linked Data initiative.

At Mahalo we just rolled out rolled out Microformats for relevant search result pages. So what does this mean, and what are Microformats? Well, they are data classes that help machines and people identify and export information. Data such as contacts and address information is much easier to manage, search engines can also better catalog the info. Yes a little bit of the semantic web of tomorrow….today!

I am pleased to announce that my company Radar Networks, has raised a $13M Series B investment round to grow our product, Twine. The investment comes from Velocity Interactive Group, DFJ, and Vulcan. Ross Levinsohn -- the man who acquired and ran MySpace for Fox Interactive -- will be joining our board. I'm very excited to be working with Ross and to have his help guiding Twine as it grows.

My last column discussed the brand utility supported entertainment model in which content providers and marketers work upstream to create customized complimentary experiences. One option would be to align this model with the open standard objectives of DataPortability.org. Their mission: to gather "existing open standards into a blueprint for a social, open, remixable Web where your online identity, media, contacts and content can follow you wherever you go."

For brands and content creators, that means conversation would truly have to be initiated by the user. The user would own the data, and the brand content offering would have to be valuable enough to warrant an exchange. In essence, brand content would be bought with "data currency."

There are brand enthusiasts who participate in campaigns on an ongoing basis. Yet each time they return, these fans must register and sign-up for the full experience. If the brand were to embrace technologies such as OpenID, not only would it provide their fans access to cross-promotional properties around that campaign, it would also provide easy access to all future campaigns. And with future potential of data portability, people could take those experiences with them, introducing content to friends and hopefully igniting passionate new fans.

What is needed though is a discussion about this and what the best practices in these cases should be. One option would be the opt-in for such XFN-markup but of course those links would still be available although not that easily extractable. Making it more private would probably harm the site’s usefulness. Removing them might also harm social services such as dopplr which make good use of them to find your contacts on dopplr.

So it’s many questions to be answered and I wonder what a good process might be to answer them. Surely there is the  around but of course they cannot just publish guidelines and the problem is solved. A broader discussion is needed and for a start maybe an exact description of the problem and coming from these some proposals to solve it.

On Sunday, we had a significant discussion on data portability and about the activities, responsibilities and opportunities of and for the eponymous group which has recently generated much hype and buzz but little, (as far as I’ve see) clarity and/or cogent strategy for advancing its expansive charter:

So anyway, I do believe that there is an opportunity here and Chris Saad is correct that getting a number of the prominent players in this arena to come to the table on this topic is a feat; however, simply bringing them together without engaging with the gnarly problems and policies that have kept data portability from becoming a reality could bring more confusion and angst than benefit.

The frustration over the minimal barrier to “becoming a member” of the group (you simply have to sign up for a mailing list) and the focus on large vendors without advancing an agenda with teeth and clearly defined metrics for success was palpable. But so was the desire to make some progress, and if not come to complete agreement, to at least identify concerns shared by the majority of us and perhaps develop a strategy to deflate the hype to date and get the group moving in a productive direction.

However, the overall value of these companies is still largely based on growth potential, which now seems shaky. Microsoft's investment in Facebook valued the company at a massive $15 billion. But in November, Twitter refused to be bought by Facebook for a reported $500 million of its stocks plus some cash.

Chris Alden, chairman and CEO of Six Apart, says that there simply isn't enough capital in the current market to sustain so many social-networking companies. "You'll see more consolidation in the next year or two," he predicts.

In October, the third most popular social-networking site, Hi5, announced that it would cut between 10 and 15 percent of its staff. And in November, the business-focused networking sites LinkedIn and Jive said that they would slash their workforces by 10 and 40 percent, respectively.

The goal of this task is to investigate, and if possible propose, a model that enable re-use of common observation models across the clinical trials and clinical practice contexts. This of course, include how Semantic Web specifications such as RDF/OWL can be leveraged to achieve this.