Looking to spruce up that bland PowerPoint presentation for your next meeting with possible investors? Or do you need high-quality photographs for your product's homepage or blog? Sprixi , a free use image search engine, is an excellent source for finding just the right image to add those finishing touches. Developed by Sydney, Australia-based company Thirsty Minds , Sprixi crawls Flickr and OpenClipArt.org for images licensed under Creative Commons and implements a user-based recommendation system to produce relevant results. While viewing photos, you can tell Sprixi whether or not an image is a useful result. Based on this data, Sprixi displays the most relevant images as rated by users at the top of the results. Sponsor The crowdsourced curation of images is what elevates Sprixi above other image searches. A Google Image search for "baseball" returns photos of varying qualities of balls, players, fields, video games and team logos. The same search on Sprixi uncovers a stunning photograph of a baseball laying in grass that has a "usefullness" rating 25.7. With no login required to browse and download photos, Sprixi displays the copyright information of each photo and can even embed the information into the photo for you, making the process of giving credit quick and painless. Discuss

Read more:
Sprixi Makes Searching for Free Photos Smart, Fast and Painless

One of the best things about Twitter is its wildly creative ecosystem of applications built by people outside the company. Those apps have been constrained, though, by technical limits imposed on retrieving data from Twitter. Those limits are just about to be raised much higher and developers tell us that a whole new world of applications and features may become possible. Twitter's Director of Platform Ryan Sarver followed up on earlier public announcements this weekend with an email to developers explaining plans to raise the limit on the number of times an application can request information from Twitter for a single user to 10 times what it is today (from 150 req/hr to 1500/hr) and to offer everyone the same kind of paid access to the full "fire hose" of user updates that Google and Bing enjoy. People who build cool Twitter apps say this is very big news. Sponsor Twitter developers say the new changes could lead to: Richer functionality for apps and services, beyond new user interfaces. More development around new features like Retweets and Lists. More real-time user experiences. Improved viability for the Twitter API. The Twitter API gets hit every time an application wants to look up a user's friends, their updates, their bio information and more. If you're building an application that analyzes, cross-references and offers useful and fun insights and features based on those types of information, then current API limits are a constraint on how much analysis you can perform, bake-down and present to your users. Raising the limits on developer access to user information will enable more processing to be done behind the scenes and more magic to be presented to end-users of Twitter apps. We spoke to some of our favorite developers about both the API limit increase and the fire hose access. Here's what they had to say. Iain Dodsworth, Tweetdeck "Not wishing to overstate the case but these changes will allow for the next generation of Twitter app. So far the ecosystem has mainly concentrated on providing numerous new UIs onto Twitter (with pretty good success I might add). Potentially the 10x API will signal a shift towards richer functionality & service development: Twitter 2.0. [emphasis added] "We're already working on functionality which mines and analyses Twitter data within the application layer which wouldn't be possible without a 10x API limit. I'm interested to see how the API scales with these new API limits." Loic Le Meur, Seesmic "The increased API limits allow apps to come up with new interaction models for Twitter, and also to catch up on all the new features Twitter added (new RTs, lists), which couldn't be supported properly with 150 requests per hour. " Justyn Howard, SproutSocial "On the 10x increase - Not too many people bump into the authorized limit today unless they run multiple apps, but that was by design. All of us developers built in controls to limit the calls, which has left power users constantly slamming the refresh button. So this does a couple of things: 1. It allows developers to loosen the logic throttling API calls which will create a closer to real-time experience for the end-users. 2. Also opens some new opportunities on cool things we can do which require the user API vs. Search (some things you can't get from the open API's, you need to use the user's account to do them). 3. Will open the doors for more secondary apps, where users previously couldn't have more than one or two [different Twitter apps] open without hitting rate limits, you'll see more people using niche apps in the background if they provide some capability beyond what Seesmic, Tweetie and Tweetdeck offer." On Access to the Firehose for Everyone Kevin Marshall, co-founder of innovative social graph parsing application provider Wow.ly , builds apps that have a clear need for increased rate limits. "This is great," he told us, "because the 150 per hour limit in conjunction with various API features (for example, the social graph API) makes it very difficult to pull off some more 'advanced' features I would like to build." On offering the Firehose to everyone, Marshall had an unusual and interesting response that demonstrates the maturity that this ecosystem is developing. It's not a simple matter of everyone chasing thoughtlessly after the real-time stream. "The more I do with and around social data, the less interested I seem to become in 'realtime' and the more interested I become in 'over time.' When I first started hacking on Twitter (and Facebook) apps, I was in love with the idea of parsing and analyzing data in real-time and I was very link/content focused. But the more I build and use these tools, the more I see the value in the history and the trails of the data set - especially when you consider that we are all living in a more asynchronous world then ever before thanks to things like blogs, Tivo, Hulu, iTunes, and other media-on-demand stuff. I don't think it's really so much about 'what are you doing right now' as it is 'what have you done that's interesting to me right now?'...and I think you get that by aggregating and analyzing." None the less, many developers will welcome the opening of previously selective fire hose access. Mailana founder Pete Warden says even his seed-funded company is looking forward to ponying up some cash. "This may sound counter-intuitive as a starving entrepreneur," he told us, "but the best guarantee the API will stay open and available is if Twitter makes money from it." "It gives developers the chance to move from being charity-cases to paying customers, and so gives Twitter a lot more reasons to listen to what we want. Anyone who wants to deal with the flood of data from the firehose already has to invest in some beefy hardware, (my server and bandwidth bills are thousands of dollars a month) so reasonable fees from Twitter shouldn't raise the barrier to entry by much." These changes are expected to go live soon and we look forward to seeing what they enable new and old Twitter apps to do. You can find and follow the RWW team on Twitter here . Discuss

Excerpt from:
Twitter 2.0: API Rate Change Could Lead to a World of New Apps & Features

Earlier this year at the SemTech conference in San Jose, I sat down with Wolfram|Alpha 's Russell Foltz-Smith. Wolfram|Alpha bills itself as a "computational knowledge engine," a nerdy and unfortunately not very intuitive description. Because it's hard to grok, most people have categorized Wolfram|Alpha as a new type of search engine. The site got a lot of press when it launched in May , as many pundits saw it as a challenger to Google. However in our own extensive tests of the product before launch, we concluded that it isn't a "Google Killer" and that it has more in common with Wikipedia. Even now there is still confusion about what Wolfram|Alpha is and what its main use cases will be. In this interview with Russell Foltz-Smith, we discuss what people are using Wolfram|Alpha for now; and more importantly what its uses will be in the near future. Sponsor Editor's note: This story is part of a series we call Redux, where we'll re-publish some of our best posts of 2009. As we look back at the year - and ahead to what next year holds - we think these are the stories that deserve a second glance. It's not just a best-of list, it's also a collection of posts that examine the fundamental issues that continue to shape the Web. We hope you enjoy reading them again and we look forward to bringing you more Web products and trends analysis in 2010. Happy holidays from Team ReadWriteWeb! Wolfram|Alpha: What is it Good For? Wolfram|Alpha is a product that was built on top of founder Stephen Wolfram's Mathematica product, a software tool for mathematicians that was initially released in 1988. The aim is to allow users to type human-like statements and have computations done on those. Wolfram|Alpha was first conceived and started development about 4 years ago, and just 6-8 months ago the team gave serious consideration to taking the product to a wider consumer audience. I started out by asking Foltz-Smith what the Wolfram|Alpha team thought of all the media hype around their product, particularly about the "Google Killer" theme which many media outlets reveled in. Foltz-Smith replied that they were expecting to be compared to Google, but not to that extent. Their team was a little surprised there wasn't more discussion around Wolfram|Alpha's similarities to Wikipedia and Freebase (although he noted that ReadWriteWeb certainly covered that!). Regarding the Google comparisons, Foltz-Smith said that they didn't give into the hype - they stuck to what their goals were. I remarked that many people still seem confused about what Wolfram|Alpha does and what it can be used for. Foltz-Smith said that people will use it for different things. The crux of the product though is that it allows people to compute and calculate things. But will mainstream people use Wolfram|Alpha? Right now, it seems to be focused on mathematicians. Foltz-Smith replied that yes, eventually Wolfram|Alpha will find a mainstream audience. It has started specific, but it will go broader. First, he said, it has to "pass a test" with "serious users" - by which he means academics and computational users. If it's useful for them, claimed Foltz-Smith, it will then go mainstream. Use Case: Education One real-world use case we talked about was using Wolfram|Alpha in education. Russell Foltz-Smith said that Wolfram|Alpha could be used to automatically generate problem sets for students, and then research those sets. A recent article in education website Chronicle.com argued that Wolfram|Alpha may have a less desired effect: encouraging cheating and laziness in students. This is because Wolfram|Alpha not only solves complex math problems, it "also can spell out the steps leading to those solutions." Stephen Wolfram told Chronicle.com that computer-algebra systems like Wolfram|Alpha actually improve education - because they allow students to explore complex problems on their own and intuitively determine how functions work, rather than just learn rote processes. Wolfram claimed that "it's better to let them [students] stand on that platform and go further." Either way, it's clear that Wolfram|Alpha and similar computational software will force the education system to adapt and change. Students now have a new (and certainly easier to use, as it's on the Web) platform on which to compute things. There's no point in the education system pretending it doesn't exist. If you're interested in tracking the progress of Wolfram|Alpha in educational settings, there is a wiki devoted to 'Teaching Undergraduate Math with Wolfram|Alpha.' Use Case: Computational Journalism This one was described to me as "anomaly spotting." For example with the current interest in swine flu news, Wolfram|Alpha could be used to fact-find and compute interesting trends. As Foltz-Smith described it, Wolfram|Alpha could "automatically enhance news." Foltz-Smith noted that CNN and other major networks do this already (analyze data), but that it's expensive to do. The end results on CNN are added value things like interactive maps and fancy diagrams. Wolfram|Alpha could make this type of data gathering and analysis presentation inexpensive and common place amongst all kinds of news operations - including good old blogs. Use Case: Sports Watching Imagine sitting in your sofa in the lounge, remote control in one hand and your favorite beverage in the other. You're watching the Friday night game on TV, it's a close game and you're curious about which team has the better chance of winning. Why, check Wolfram|Alpha of course! In real time, Wolfram|Alpha could compute statistics about not just the history of the two teams - but the history of the location of the game, the weather, the season so far, etc. As Foltz-Smith explained it, Wolfram|Alpha would be able to do "chained queries" - queries made up of multiple parts. For example: which quarterback had the best winning record in games played in the rain during the 1970s. Other Use Cases We also discussed medical and scientific use cases. Although there are early examples of Wolfram|Alpha in health, such as a nutrition label generator , Foltz-Smith was generally cautious about medical uses - because a lot of health data "can't be wrong." He noted that in use cases like medical research, the issue of data fidelity is key. For example with the human genome, you have to take great care of that data and associated algorithms. Also he explained that as something like the human genome scales, how do you do QA? Foltz-Smith admitted that the Wolfram|Alpha team is still working on these and similar issues. But they have a lot of people devoted to solving this problem. Some types of data could be crowdsourced, e.g. in linguistics, but other data needs different approaches. Conclusion It was interesting to hear about some of the potential uses of Wolfram|Alpha. We at ReadWriteWeb think this product has a promising future. If Web 2.0 was about creating data (user generated content, to use the most familiar term for this), then the next generation of the Web is all about using that data. Wolfram|Alpha is premised on using and computing data. Let us know in the comments what use cases you see for Wolfram|Alpha, and whether you're aware of similar computational web apps. See also: Wolfram|Alpha: Our First Impressions Wolfram|Alpha in Action: Our Screenshots Mixed Emotions: Our First Hands-On Test Of Wolfram|Alpha Wolfram|Alpha Launch: Here's What You Need to Know Wolfram Alpha Gets Its First Update Discuss

Original post:
Wolfram|Alpha: The Use Cases

It's one thing to have resolutions for the new year. I, for example, plan to lose weight, learn Python and design the perfect handbag. But since nothing satisfies like the quick achievement of a short-term goal, here are eight things every good nerd needs to to before the ball drops later this week. These tasks comprise a quick to-do list that will leave you feeling competent and prepared for the decade that approaches. Also, you can play the condescension chip and start chiding friends who haven't checked off these items yet. Sponsor 1. Edit your privacy settings and friendships. Facebook's maelstrom-causing privacy changes have given quite a few of us a head-scratching good time trying to figure out just how much of our private lives are to be made public. Before the new year begins, take a look at your settings on sites such as Facebook, Flickr, YouTube, LiveJournal and any other places you might be sharing personal content to make sure what you display is consistent with the public image you want to project. As more recruiters and employers hit the web in search of info on individuals, it's becoming ever more important to monitor and control our own identities. If you look back to the origin dates of some of your accounts, you might be surprised at what you thought was appropriate to share online in 2005. Also, while considering what's private and public, take time to evaluate what a "friend," "contact" or "follower" means to you and what types of information you share with different groups. 2. Change your passwords. Safety first, friends. Social web security threats in 2009 were sweeping and surprised more than a few users with spam DMs, hacked accounts and malware of all kinds. Check out the password management tools recommended by a recently high-profile hacker (scroll to the last few paragraphs); for free or cheap, they'll help you generate strong, random passwords and manage them from your computer. 3. Own your name. I've conducted many a web search on many a professional geek this year, and I've been disappointed by how few of us have staked a meaningful claim to our online identities. If you haven't already, buy a URL - preferably one that relates to the name you use professionally - and make friends with Google. If you don't show up in the first results when you search for your name, get a crash course in SEO and ask friends to link to you. It's good for your social life and your career if you seize the opportunity to tell the searching world about yourself rather than relegating that responsibility to LinkedIn, Facebook or some weirdo with the same name as you. 4. Prune your feeds. When going through your RSS feeds, do you find yourself impatiently scrolling more than you're intently skimming? Is your list of unread items becoming unmanagable? The end of the year is a perfect time to get rid of the content you're not reading and group the stuff you are. Take some time this week to organize, delete and add feeds, thereby optimizing your feed-reading experience. Try tools such as NetNewsWire's "dinosaurs" and "least attenion" features that weed out unread or dormant feeds, and consider implementing tools such as Lazyfeed or Guzzle.it that can bring relevant results from fresh sources. And make sure the feeds you own are easy for others to find, too. 5. Find a better mobile. If you don't have a smartphone already, chances are you'll desperately need one next year. And if you already have one, think long and hard about whether you're happy with your service, network and interface. While you might not be able to run out and buy your dream device before 2010 rolls around, visit a few retailers, read some reviews and have your eye on a good mobile to purchase next year. Mobile tech keeps on booming, and you'll want to ensure a frustration-free year as new apps and OSes roll out. 6. Update copyright notices on your website. Here's a simple, obvious and necessary reminder. Does your website currently claim a copyright year of 2007? While it doesn't put you on the foul side of the law, it does look a bit silly as we head into a new decade. The Next Web has a good bit of dynamic code for site owners. 7. Revisit your blog. That poor, neglected old beast might be long overdue for a design facelift, a blogroll refresh or even just a few new posts. While you're at it, why not set automatic reminders to periodically bug you about posting in the new year? On a more mission-critical note, you'll also want to make sure you're using the most updated version of your CMS; not doing so can can lead to problems from broken plugins to getting hacked . And while you're at it, the year's end might also be a good time to consider switching up your CMS service altogether. 8. Back up your data. Hacks and hardware failures happen. Before 2010, make sure as much of your data as possible is protected. From calendars and contacts to blog posts and work projects, more and more of us are relying on networks of servers and startups to keep us running. So, now might be a good time to download and back up files of LinkedIn contacts and WordPress posts - anything that's valuable to you and portable. Think of it this way: You - or at least parts of you - live in the Internet. If the Internet caught on fire, what would you grab to carry with you out of the blaze? We hope this list helps you all get a few housekeeping items squared away in time for a great New Year's Eve filled with peace of mind and a smug sense of superiority over your fellow nerds. If you can think of any must-do year-end tasks, please let us know in the comments! Discuss

Continue reading here:
8 Things Every Geek Needs to Do Before 2010

This week ReadWriteWeb is running a series of posts analyzing the five biggest Web trends of 2009. Our first post was about Structured Data , our second about The Real-Time Web . The third part of our series is on Personalization . Personalization has long been a buzzword on the Internet. With the glut of information on the Web circa 2009, personalization in this era means providing effective filters and recommendations . Ultimately personalization is about websites and services giving you what you want, when you want it. That's the long-standing dream anyway. Let's see if the products of 2009 are fulfilling it. Sponsor Editor's note: This story is part of a series we call Redux, where we'll re-publish some of our best posts of 2009. As we look back at the year - and ahead to what next year holds - we think these are the stories that deserve a second glance. It's not just a best-of list, it's also a collection of posts that examine the fundamental issues that continue to shape the Web. We hope you enjoy reading them again and we look forward to bringing you more Web products and trends analysis in 2010. Happy holidays from Team ReadWriteWeb! All of the trends that we're profiling overlap. This is particularly so with personalization, as we'll see. Filtering the Real-Time Firehose Personalization is often used to provide an organization layer for users on top of real-time data. As Ken Fromm put it in his primer on the Real-Time Web : "The Internet is shifting from discrete units of websites and Web pages to discrete units of information organized in ways that are relevant and personal to each individual, using data gleaned from social graphs as well as recommendation and personalization services that allow users to set their preferences." If you use a dashboard product like TweetDeck, Seesmic or Peoplebrowsr to use Twitter, then you're able to group people, keywords and topics. This is effectively personalization at work. Open Web: More Data About You, Better Personalization Another aspect of personalization is the increasing prevalence of open data on the Web. A lot of companies make their data available on the Web via APIs, web services, and open data standards. And as we discussed in the first post in this series, much of that data is structured - allowing it to be inter-connected and re-used by third parties. How does open data lead to personalization? Simply put, the more data about you and your social graph that is available to be used by applications, the better targeted the content and/or service will be to you. There are non-trivial privacy issues about this, however the personalization benefits can be significant. There are a whole host of open data standards on the Web now. They include: Data portability - taking your data and friends from one site to another. OpenID - portable identity; single sign-on. OpenSocial - Google initiative for social networks, enabling developers to create widgets with one set of code; MySpace a member, Facebook isn't. APML - growing 'Attention' standard; Your Attention Data is all the information online about what you read, write, share and consume. Recommendation Engines Many consumer products on the Web aim to recommend you things that you may like . A couple of years ago, Alex Iskold outlined what he saw as the 4 main approaches to recommendations : Personalized recommendation - recommend things based on the individual's past behavior Social recommendation - recommend things based on the past behavior of similar users Item recommendation - recommend things based on the item itself A combination of the three approaches above Amazon is probably still the best example of recommendations on the Web, but an example of something new from 2009 was Netflix launching better personalization features in March. They included new taste preferences, allowing users to (for example) choose between movies that are romantic, suspenseful, or dark. Other additions included a personalized homepage and a feature enabling users to mix and match genres. Conclusion Personalization has shown slow but steady progress in 2009. It hasn't been as wild a ride as Structured Data or Real-Time Web, but we consider personalization to be a key facet of the evolving Web. ReadWriteWeb's Top 5 Web Trends of 2009: Structured Data The Real-Time Web Personalization Mobile Web & Augmented Reality Internet of Things Image credit: davepatten Discuss

Link:
Top 5 Web Trends of 2009: Personalization

During my trip to Boston earlier this year, I had the opportunity to visit MIT. At the end of a long day of meetings with various MIT tech masterminds, I made my way to the funny shaped building (see photo right-below) where the World Wide Web Consortium (W3C) and its director Tim Berners-Lee work. Berners-Lee is of course the man who invented the World Wide Web 20 years ago. This was my first meeting with the Web's creator, whose work and philosophy was a direct inspiration for me when I launched ReadWriteWeb back in 2003. 1 Sponsor Editor's note: This story is part of a series we call Redux, where we'll re-publish some of our best posts of 2009. As we look back at the year - and ahead to what next year holds - we think these are the stories that deserve a second glance. It's not just a best-of list, it's also a collection of posts that examine the fundamental issues that continue to shape the Web. We hope you enjoy reading them again and we look forward to bringing you more Web products and trends analysis in 2010. Happy holidays from Team ReadWriteWeb! After shaking hands, I told Tim Berners-Lee that this blog's name was in part inspired by the first browser, which he developed, called " WorldWideWeb ". That was a read/write browser; meaning you could not only browse and read content, but create and edit content too. It was a shame then when Mosaic, a read-only browser, became the first mainstream Web browser in the mid-90s. It wasn't until the rise of Web 2.0 that the read/write philosophy gained widespread acceptance. 2 On that note, we launched into the interview... Note: the interview was published in two parts, with Part 1 on the topic of Linked Data. Part 2 explored other topics and can be found here . How Linked Data Relates to The Semantic Web RWW: Earlier this year you gave an inspiring talk at TED about Linked Data . You described Linked Data as a sea change akin to the invention of the WWW itself - i.e. we've gone from a Web of documents to a web of data. Can you please explain though how Linked Data relates to the Semantic Web, is it a subset of it? TBL: They fit in completely, in that the linked data actually uses a small slice of all the various technologies that people have put together and standardized for the Semantic Web. Linked Data uses a small slice of the technologies that make up the Semantic Web. We started off with the Semantic Web roadmap, which had lots of languages that we wanted to create. [However] the community as a whole got a bit distracted from the idea that actually the most important piece is the interoperability of the data. The fact that things are identified with URIs is the key thing. The Semantic Web and Linked Data connect because when we've got this web of linked data, there are already lots of technologies which exist to do fancy things with it. But it's time now to concentrate on getting the web of linked data out there. Web inventor Tim Berners-Lee and ReadWriteWeb founder Richard MacManus How Linked Data Has Evolved via Grassroots RWW: Linked Data has had a lot of grassroots support, which you mentioned in your TED speech. This is something Semantic Web technologies, such as RDF, have struggled to get over the years. Has the W3C been pushing the more bottom-up Linked Data world, because of the frustration over lack of take-up of top-down Semantic Web ? TBL: A lot of the initial RDF and OWL projects came out of the academic world; and some of them were projects to show what you could do in a closed world. And the files were zipped up and left on a disc. While they were interesting projects, and while the systems were useful systems, the Semantic Web community maybe missed the point of the 'web' bit and focused too much on the 'semantic'. However the work that's been done in the Semantic Web, the standards, was really valuable. It's relatively recently for example that SPARQL [an RDF query language] has been developed. "It's time now to concentrate on getting the web of linked data out there." Somebody drew an analogy the other day: can you imagine trying to promote a world of databases without SQL? Even though it's not an interoperable protocol, it's just a query language. So similarly, all that's been put into RDF, rdfs and OWL is very valuable to the linked data community. The Linked Data community tend to use a subset of that [Semantic Web technologies], of OWL for example. But they certainly use SPARQL. So you could argue that really it wasn't ready to be deployed widely. Linked Data started as a very informal Design Issues note that I put in; it was a grassroots movement from very early on. So yes W3C has been emphasizing the importance of Linked Data. It's been the Semantic Web Interest Group of course, and various [other Semantic Web] activities, which has been pushing it. But also Linked Data has been seized on - a group of people for example put together DBpedia . 3 That wasn't commissioned, that was that they just thought it would be a really cool idea. Graph of Linked Data sets on the Web, as at March 2009 Linked Data and Governments RWW: In a recent Design Issues note , you urge governments to put their data online as Linked Data (although you'd also be happy for governments to just make available the raw data - presumably so that others can then structure it). What do you realistically expect, for example, the U.S. or U.K. governments to do over the next year? And in the near future, do you foresee different governments interconnecting their Linked Data sets? TBL: One can't generalize, governments are (like most big organizations) fascinatingly diverse inside them. So you'll find that there are places inside governments where you get a champion who gets linked data and who's just written a script and produced some linked data. So in the UK government for example, you'll find there's RDFa [in the code of its website] for civil service jobs. So if somebody wants to make a database of all the jobs, they can do that very easily. "The first step of actually putting the data out there is the one that nobody else can do." There are other cases where the easiest thing for somebody to do is to just put data up in whatever form it's available. Comma separated values (CSV) files are remarkably popular. They're exported sometimes from spreadsheets. It's remarkable how much information is in spreadsheets. Or sometimes pulled out of a database and then put up on the web. It's not as good, not as useful to the community, as if Linked Data had been put up there and linked. But the first step of actually putting the data out there is the one that nobody else can do. Data.gov , a catalog of public data, was launched in May by the U.S. government The way to go is for government departments to go the extra step and convert [their data] into Linked Data. One of the nice things about Linked Data, when they have a pile of it, is that they could run a SPARQL server on it. SPARQL servers are a commodity product, a solution for all of the people who say 'but actually I wanted to have XML.' A SPARQL server will generate an XML file [and] allow somebody to write out, effectively, a URL for the XML file. "Linked Data is the backplane, it's the thing that you connect to in both directions." In fact, I don't see why SPARQL servers shouldn't provide CSV files, something which as far as I know isn't in the standards. But I'd recommend it, certainly in government context, because CSV files are what people have and what people want. So the message [for government] is to use RDF. Linked Data is the backplane , it's the thing that you connect to in both directions. As a [web] producer your job is to make sure that you produce Linked Data one way or another. And as a consumer, there are lots of ways to consume that data once it's out there as Linked Data. In Part 2 of this interview we discussed: how previously reticent search engines like Google and Yahoo have begun to participate in the Semantic Web in 2009, user interfaces for browsing and using data, what Tim Berners-Lee thinks of new computational engine Wolfram Alpha, how e-commerce vendors are moving into the Linked Data world, and finally how the Internet of Things intersects with the Semantic Web. Read Part 2 here . Footnotes: 1. The very first sentence written on this blog , on 20 April, 2003, was: "The World Wide Web in 2003 is beginning to fulfill the hopes that Tim Berners-Lee had for it over 10 years ago when he created it." 2. For more on read/write browsers, you can read another early RWW post entitled What became of the Browser/Editor . 3. DBpedia is a community project to extract structured information from Wikipedia; see ReadWriteWeb's profile of this and similar resources. Discuss

Read more:
ReadWriteWeb Interview With Tim Berners-Lee, Part 1: Linked Data

With the rapid growth of services like Foursquare , Gowalla and Brightkite , location-based mobile social networks seem to be a dime a dozen these days, but they're only fun and useful if your friends are using it, too. Each time that I've tried one of these services, I find myself trying to convince my friends to use it so that I can have meaningful contacts to keep track of. Some of them don't have the right phone, or are worried about blasting out their GPS coordinates to the world. Sponsor Stalqer , available as a free iPhone app since earlier this month, has solved this problem by connecting to your Facebook , Twitter and Foursquare accounts and providing a map of your friends based on information it gathers from those services, even if they don't use Stalqer. If your friend uses a geo-tagged Tweet, or if they check in on Foursquare, Stalqer knows where they are. Stalqer can even pull your friends' location from their Facebook profiles if they publicly display that information, but in most cases this is limited to the city level. You can also view your friends' locations in a list, or even in an augmented reality view by turning the phone on its side while in the map view, but Stalqer's killer feature is its workaround of a pesky iPhone limitation.

Read the rest here:
Stalqer: Aggregated, (Almost) Live Location Data on the iPhone