2007-08-31
Monetizing the Semantic Web
Traditional products and service sellers stand to gain customers because the SemWeb will enable location and comparison. But, how do content creators make money selling RDF triplets?
Injecting advertising into rich media might make money on the SemWeb. RDF triplets might be filtered at user's computer - and not merely to remove advertising. However, today's computers lack the smarts to remove advertising from rich media; images, sounds, animations, videos, flash interactives. Google has already begun experiments with advertising support for YouTube videos.
Micropayments have been proposed since the days of Xanadu and periodically they become fashionable for a time. Clay Shirky's The Case Against Micropayments discusses why cross-site micropayments have never, and will probably never, succeed.
Within single sites micropayments do work. Many sites have created internal micropayment currencies. Amazon's S3 storage service uses a micropayment system that bundles many transactions - charged a cent at a time. Bundling is the right idea.
Content creators can offer time-limited subscriptions to specific content. A content reseller (the "Info-Vendor) will then aggregate smaller subscriptions into package offerings. This is similar to how content sales already work for online academic journals, TV shows and music. An Info-Vendor service will then become part of the household utility bill - most likely bundled with broadband and cable TV. An Info-Vendor feed may even become a free good subsidized by taxation.
This situation will simplify the finding problem of content selection because only a few sources need be queried. The latency aspect of the SemWeb data topography will be reduced resulting in faster and more reliable service. Content credibility can be judged by the Info-Vendors credibility. Ontological translation and basic inference could be run over the Info-Vendor's data store saving local processing time. There is potential for the AI synthetic creation of new content to outstrip human capacity to make use of the information.
Info-Vendors may enforce favorite ontologies (and thus implicitly endorse worldview embedded in the ontology). Info-Vendors will also have a controlling stake in the content that users are exposed to. Alternative viewpoints might just not be represented in any of the commercial Info-Vendor's information stores.
Contract and intellectual property laws can prevent users on-selling content (automated via proxies), there is difficulty proving ownership of a single RDF triplet. It is just not economical to include DRM at triplet level granularity. Also any DRM systems are at best voluntary. Info-Vendors will gradually lose control over their RDF triplets as the society starts to copy each triplet over and over again; RDF triplets will, in effect, data-leak into the public domain. Therefore, the value of an RDF triplet is in its scarcity. The most successful Info-Vendors will both make available new RDF triplets, including some created using AI synthesis.
Like providers of other services, Info-Vendors will ultimately form a varied marketplace. Access to good Info-Vendor service could become the next digital divide.
Summary: The ways to make money on the SemWeb are by injecting advertising into rich media and riding the rise of the Info-Vendor.
2007-08-28
Three Content Selection Problems
The three problems of content selection are: finding, filtering and bounding.
Finding has plenty of people working on it. There is Swoogle and (with Web3.0 annotation) even your regular WWW search engine could help.
Once you're found an initial starting point then filtering and bounding are needed. A SemWeb object could have many more triplets describing it then are needed, especially if indirect links are resolved and information is brought in from multiple ontologies. Filtering is the intra-object act of deciding which triplets are important. Bounding is the decisions in how far to traverse the graph of links between SemWeb objects. Bounding is the inter-object counterpart to filtering.
Finding has plenty of people working on it. There is Swoogle and (with Web3.0 annotation) even your regular WWW search engine could help.
Once you're found an initial starting point then filtering and bounding are needed. A SemWeb object could have many more triplets describing it then are needed, especially if indirect links are resolved and information is brought in from multiple ontologies. Filtering is the intra-object act of deciding which triplets are important. Bounding is the decisions in how far to traverse the graph of links between SemWeb objects. Bounding is the inter-object counterpart to filtering.
2007-08-24
SemWeb links of the Week
My Top SemWeb 3 links for the week:
- SemWeb Tools - An index of SemWeb tools with SIMILE Exhibit enabled faceted browsing.
- Embracing Web 3.0 - Article by James Hendler and Ora Lassila.
- RadarNetworks - Nova Spivack's startup.
Writing Retreat
I had a hugely productive week working on my PhD Research Proposal. Taking a week away from the distractions of work really paid off. Just so my supervisor's know: I've started working all the various documents and scraps into the proper format. It's a mess still, but a big start.
My PhD topic is (for now) "Combining Presentation and Content decisions in an Adaptive SemWeb Browser".
I have a number of issues that require thinking through:
- Do I produce something that replaces the current web or works with it?
- How much do I really care about Web 3.0
- Should the SemWeb browser be website or desktop hosted?
Subscribe to:
Posts (Atom)