Destroy all the asteroids to get points. The asteroids may contain gems inside. Capture them to earn more points or win fuel levels.For...
Showing results 1 to 8 of 8
No, Planetary Resource isn't kidding. It’s working on using Linux, open-source software, and commercial off-the-shelf hardware to build the first robotic asteroid miners.
Planetary Resources plans to harvest water and other valuable natural resources from near-by asteroids.
Tuesday morning I officially heard that Sameer Patel, one of the key thought leaders in the collaboration space and one of the few who understood the convergence between collaboration and Social CRM, became the SAP Global VP, Enterprise Collaboration and Social Software Solutions. Thing is, he is also a very dear friend of mine, someone I love to pieces.
The T-Mobile G1 is showing up in the hands of those who pre-ordered one this week (mine is schedule for Tuesday arrival) and I have been seeing new applications appearing in the Android Market almost daily on my review unit. There are still a very limited number of games and I think only one or two were added since I started my review. I loaded up eleven applications (a couple of these just appeared yesterday) and took the below video of eight applications in action on the G1. I covered the Video Player in my full review since that was really an application that should have been included by T-Mobile and Google. As I stated in my full review you only get 128MB of onboard storage to load up applications and you cannot currently load them on the microSD card. With the eleven applications I tried, I only had 34MB of remaining memory. However, in looking at the space allocation settings it looks like your data is stored in this area too so if you have a ton of contacts and lots of calendar entries your space may fill up faster.
An instrument developed for analysing minerals on Mars may be used on earth to help the Australian resources industry.
Mine Space Fxs HD is a ipad piexl star style movie fxs maker.help you to make space style movie fxs for your phone. Make you to be...
Tis the season for everyone to chime in with their predictions for the upcoming year -- and here are mine. The past year was a good one for Google, their stock gained $200 per share, several new products/services/features were launched, their market share rose to nearly 60%, they have managed to keep their advertising earnings impressive, and have invested significant time and money into the mobile space.
As Danny highlights in the latest instalment of This Week's Semantic Web, Marc Andreessen has once more demonstrated that he's not content with co-authoring Mosaic, sneaking around in the 24 Hour Laundry and driving social networking Ning-style. Far from it, as he continues his recent practice of blogging thoughtfully on issues facing the industry of which we - and he - are part. Yesterday's post, The three kinds of platforms you meet on the Internet, touched on a number of issues that we've addressed here on Nodalities before, and it is well worth both reading and thinking about.As Marc suggests in his introduction; “One of the hottest of hot topics these days is the topic of Internet platforms, or platforms on the Internet. Web services APIs (application programming interfaces), web services protocols like REST and SOAP, the new Facebook platform, Amazon's web services efforts including EC2 and S3, lots of new startups talking platform (including my own company, Ning)... well, 'platform' is turning into a central theme of our industry and one that a lot of people want to think about and talk about. However, the concept of 'platform' is also the focus of a swirling vortex of confusion -- lots of platform-related concepts, many of them highly technical, bleeding together; lots of people harboring various incompatible mental images of what's about to happen in our industry as a consequence of various platforms. I think this confusion is due in part to the term 'platform' being overloaded and being used to mean many different things, and in part because there truly are a lot of moving parts at play that intersect in fascinating but complex ways.”How true. The Platform space is a great one to be in and it's brimming over with opportunity and potential; so much so that we're one company staking an awful lot upon the detail of our Platform vision. Traditionally sloppy use of language, however, has led to a situation in which unnecessary confusion is now associated with a superficially straightforward term. Some of this confusion is introduced by innocent drift in the evolving usage of a word, but far more is down to the unfortunate fashion for everyone jumping on the bandwaggon and unleashing a 'platform' of their own. At least we've been using the Platform label for our own endeavours in this area for a number of years.In his attempt to introduce some clarity, Marc's post reiterates his basic definition of an internet platform; “A 'platform' is a system that can be programmed and therefore customized by outside developers -- users -- and in that way, adapted to countless needs and niches that the platform's original developers could not have possibly contemplated, much less had time to accommodate. We have a long and proud history of this concept and this definition in the computer industry stretching all the way back to the 1950's and the original mainframe operating systems, continuing through the personal computer age and now into the Internet era. In the computer industry, this concept of platform is completely settled and widely embraced, and still holds going forward. The key term in the definition of platform is 'programmed'. If you can program it, then it's a platform. If you can't, then it's not.”Check.He then offers three 'kinds' or 'levels' of Internet platform, being careful to stress that one is not necessarily better than those it supersedes; “I call these Internet platform models 'levels', because as you go from Level 1 to Level 2 to Level 3, as I will explain, each kind of platform is harder to build, but much better for the developer. Further, as I will also explain, each level typically supersets the levels below. As I describe these three levels of Internet platform, I will walk through the pros and cons of each level as I see them. But let me say up front -- they're all good. In no way to I intend to cast aspersions on what anyone I discuss is doing. Having a platform is always better than not having a platform, period. Platforms are good, period.”Marc's three levels are;Access API “Architecturally, the key thing to understand about this kind of platform is that the developer's application code lives outside the platform -- the code executes somewhere else, on a server elsewhere on the Internet that is provided by the developer. The application calls the web services API over the Internet to access data and services provided by the platform -- by the core system -- and then the application does its thing, on its own.”Plug-in APISuperficially very similar to the 'Access API', but the host application (such as Facebook) into which a developer's application connects does the vast majority of the work around marketing; “Facebook provides a whole series of mechanisms by which Facebook users are exposed to third-party apps automatically, just by using Facebook.”Runtime Environment “In a Level 3 platform [such as Salesforce], the huge difference is that the third-party application code actually runs inside the platform -- developer code is uploaded and runs online, inside the core system. For this reason, in casual conversation I refer to Level 3 platforms as 'online platforms'.” “Put in plain English? A Level 3 platform's developers upload their code into the platform itself, which is where that code runs. As a developer on a Level 3 platform, you don't need your own servers, your own storage, your own database, your own bandwidth, nothing... in fact, often, all you will really need is a browser. The platform itself handles everything required to run your application on your behalf.”And there's more, and it's interesting stuff that Marc has clearly thought about long and hard.Reading - and rereading - Marc's post, though, I kept coming back to ideas touched upon in two posts of mine about the relative openness of different Platform solutions; “Facebook and Talis might very well be offering 'Platforms', but they're quite different in intention. Facebook's platform seems to be all about making the Facebook site as rich, compelling and sticky as possible; everything is sucked to one point. The Talis Platform, on the other hand, is about providing developers - wherever they are - with the tools and capabilities to easily link and manipulate data across and through the web. The former sits heavily 'on' the web, and feeds upon it to suck ever more into its maw. The latter is truly 'of' the web, giving a distributed community of developers and users powerful new capabilities to enmesh their applications, and to deliver capabilities at the point of need.”Regardless of its position in Marc's levels, I truly hope and believe that the Internet platforms of long-term viability will be those that embrace the Network rather than feeding rapaciously upon it; those that are of the web as we are trying so hard to be.A Platform should give the developer a helping hand. It should lift them up and provide them with a set of tools that make it easier to concentrate upon and deliver their core value whilst the Platform worries about the day-to-day mundanity that is mere context [to paraphrase Geoffrey Moore]. A Platform should enable the developer to realise the benefit of those tools and capabilities in places and manners of their own choosing, rather than expecting or requiring the developer merely to expose their assets within the bounds of whatever site(s) the Platform chooses to offer. Platform providers who realise and embrace that will be the ones to succeed.
MineSpace Fxs For Minecraft is piexl star style movie fxs for minecraft users to make space movies.help you to make space style movie...
The Economist. Tim O'Reilly. Nova Spivack. Danny Ayers. Read/Write Web's Alex Iskold. Kingsley Idehen. Brad Feld. Over the last few days all of them have been amongst those writing to clarify their understanding of the Semantic Web and where it's going.Each piece is thoughtful, each piece is well worth a read, and each differs somewhat from the others in outlook as they delve into 'ontologies', 'classic approaches', 'machine intelligence', 'SPARQL', 'Turtle' and other geekiness [meant in the nicest possible way]. I do wonder, though, if all of them are bypassing some fundamental points as they seek to clarify their own perspectives to themselves, to one another, and to the world; points with which I suspect that each may actually agree.First, I definitely don't think that a company, technology or approach can only be either 'Web 2.0' or 'Semantic Web'. Sure, some companies will see themselves (or pitch themselves) in one space or the other, but there's going to be an ever-increasing number that reside firmly in both. Ultimately, of course (and figures in the FT this week, suggesting that “The pull-back was particularly acute in Silicon Valley, as big Web 2.0 investors such as Benchmark Capital, Kleiner Perkins Caufield & Byers and Omidyar Networks, the private financing vehicle of Ebay founder Pierre Omidyar, cut back on their investments.”might more logically be interpreted as supporting this argument) companies won't be Web 2.0 or Semantic Web. They will be companies that solve a particular set of problems for a particular set of audiences. Some of the tools in the toolbox they use to do this will be Web 2.0-ish, some will be Semantic Web-ish, some will be both, and some will be neither. Those things that currently differentiate us - and to which we apply labels in order to reinforce the differentiation - will become mainstream, run of the mill, mundane, and simply expected. That's progress, and it's a good thing. Web 2.0 won't go away. The Semantic Web won't go away. Shouting about either might, and it doesn't have to mean that their importance has diminished.Second, 'collective intelligence' applies equally to both. Tim O'Reilly's absolutely right that it's been a key differentiator of many Web 2.0 darlings; “By contrast, I've argued that one of the core attributes of 'web 2.0' (another ambiguous and widely misused term) is 'collective intelligence.' That is, the application is able to draw meaning and utility from data provided by the activity of its users, usually large numbers of users performing a very similar activity. So, for example, collaborative filtering applications like Amazon's 'people who bought item this also bought' or last.fm's music recommendations, use specialized algorithms to match users with each other on the basis of their purchases or listening habits. There are many other examples: digg users voting up stories, or wikipedia's crowdsourced encyclopedia and news stories.”It's also front and centre in Semantic Web work, though. For example that from ourselves, Radar Networks and others. See this white paper [PDF] for one, and watch here and here for public sight of internal developments... soon. The connections that RDF makes so manifest are a perfect way to express, traverse, and mine the habits, behaviours and desires of the collective.Third, 'a formal ontology' is not a requirement, and nor is pushing structure in the face of the user.Tim makes a good point here; “The Semantic Web is a bit of a slog, with a lot of work required to build enough data for the applications to become useful. Web 2.0 applications often do a half-assed job of tackling the same problem, but because they harness self-interest, they typically gather much more data. And then solve for their deficiencies with statistics or other advantages of scale.”I'm not sure, though, that SemWeb/ Web 2.0 is the dichotomy here? Rather, it's a split between purist, all-encompassing, and hugely flexible on the one hand and pragmatic and 'good enough' on the other. I would agree that stereotype would often place Semantic Web developers on one side of that divide and Web 2.0 startups on the other. The technology is not the point there, though, so much as the mindset. Believe me, we can do some great stuff to harness self-interest, gather much more data, and solve the deficiencies with statistics and other advantages of scale in a Semantic Web-ey Platform... :-) “But I predict that we'll soon see a second wave of social networking sites, or upgrades to existing ones, that provide for the encoding of additional nuance. In addition, there will be specialized sites -- take Geni, for example, which encodes geneaology -- that will provide additional information about the relationships between people. Rather than there being a single specification capturing all the information about relationships between people, there will be many overlapping (and gapping) applications, and an opportunity for someone to aggregate the available information into something more meaningful.”Too right, Tim. But I'd definitely suggest that those building the second wave should be talking to Talis, to Radar Networks, to Metaweb and to some of the other proponents of a new and far more Web 2.0-inspired Semantic Web paradigm. There are way too many synergies there to ignore...Dan Brickley's comments in response to one aspect of Danny's argument are also interesting; “Let me clear something up. Danny mentions a discussion with Tim O’Reilly about SemWeb themes. Much as I generally agree with Danny, I’m reaching for a ten-foot bargepole on this one point: 'While Facebook may have achieved pretty major adoption for their approach, it’s only very marginally useful because of their overly simplistic treatment of relationships.' Facebook, despite the trivia, the endless wars between the ninja zombies and the pirate vampires; despite being centralised, despite [insert grumble] is massively useful. Proof of that pudding: it is massively used. 'Marginal' doesn’t come into it.”Too true. I've complained about Facebook, too [for example here and here]. But I use it, and millions of others use it. And it serves a purpose. That doesn't mean it can't be better.Turning, finally, to Alex' post; “The first problem is that RDF and OWL are complicated. Even for scientists and mathematicians these graph-based languages take time to learn and for less-technical people they are nearly impossible to understand. Because the designers were shooting for flexibility and completeness, the end result are documents that are confusing, verbose and difficult to analyze.”Well, yes and no. That's what tools are for. And in a large number of cases the RDF may actually be auto-generated as part of some process of aggregation or value addition of which the data creator or manager need have no explicit awareness. The RDF may very well be generating an aggregation of tiny snippets of data from large numbers of transactions; the interaction of a single user with a single resource doesn't have to result in a whole RDF document of its own. More on that later.And, also from Alex; “Going back to John Markoff's example of a computer booking a perfect vacation, one can't help but think of a travel agency. In the good old days, you would go to the same agent over and over again. Why? Because just like your friends, your doctor, your teacher, the travel agent needs to know you personally to be able to serve you better. The travel agent remembers that you've been to Prague and Paris, which is why he offers you a trip to Rome. The travel agent remembers that you're a vegetarian and orders the pasta meal for you on your flight. Over time people learn and memorize facts about life and each other. Until machines can do the same, knowledge of semantics, limited or full is not going to be enough to replace humans.”Exactly. And that's where network effects, collective intelligence, behavioural observation and all the rest kick in. The knowledge comes from observation of an awful lot of behaviour; not from having the traveller fill in some long-winded and tedious form detailing an RDF graph representation of their travel preferences for all situations. Context matters. I, for example, want a window seat on short-haul flights, and an aisle seat on long-haul flights. It's not a simple preference one way or the other. I don't have a preferred airport to depart from, as so many other factors come into play. I'll go to a more distant departure airport for a better departure or travel time, for example. I won't always travel with the airlines I've got frequent flier cards for... but they don't have to be cheapest before I can or will. It's more complex than that. Current systems don't understand. “Perhaps the worst challenge facing the semantic web is the business challenge. What is the consumer value? How is it to be marketed? What business can be built on top of the semantic web that can not exist today? Clearly the example of instant travel match is not a 'wow.' It's primitive and, in a way, uninteresting because many of us are already quite adept at being our own travel agent using existing tools. But assuming that there are problems that can be solved faster, there is still a question of specific end user utility.”Talis. Radar Networks. Joost. Metaweb. Garlik. Need I go on? (I can... :-) ) “The way the semantic web is presented today makes it very difficult to market. The 'we are a semantic web company' slogan is likely to raise eyebrows and questions. RDF and OWL clearly need to be kept under the hood. So the challenge is to formulate the end user value in ways that will resonate with people.”Absolutely right! SWEO is part of the answer. Companies like ours getting out and showing what can be done, and why it's valuable is crucial too... and we're getting there.And to answer my initial question; No, I don't think everyone is confused by or about the Semantic Web. We do, though, have a lot of different niche views of value (or lack thereof), clamouring for attention. These overlapping - and not necessarily incorrect - perspectives certainly could appear to be a result of confusion, if viewed from the outside. Language is a complicated thing, and these are complex ideas. Describing one with the other requires a number of iterations to arrive at clarity, but we're getting there.There's a lot more to say, but this post has now gone on long enough (especially as I initially meant to simply point you at some interesting blog posts...).