• End-user generated directories. This is a bottom up approach to the creation of topical directories that can scale to millions or billions of pages. Directories can cross link through transclusion (a method of interlinking directory OPML files. This means that end-users can seamlessly browse large directories without an interruption of experience. This method scales. It's democratic. The best directories float to the top. Wow!
  
  • Decentralized development of directories of information. This starts with an end-user building a directory of resources (links to web pages, documents and pictures) in an outliner which create an OPML. They publish the result to the Web (Radio makes this easy) or an Intranet.
  • Search services index these directories. A search engine like Google crawls the Web or the Intranet, finds the published OPML file, and indexes its results. End-users can then search on a keyword and get directories that are relevant to that term.
  • The most relevant directories are listed at the top. The directories are ranked by Google's quality measurement system (PageRank). Note: There isn't any uber directory (the reasons that Yahoo and DMOZ don't scale) that attempts to account for all info. It is completely keyword based.
• Webpage relational metadata directories (this is data about information like a webpage). Every webpage Google crawls has as a Google relational metadata structure. Unfortunately, almost all of this richness is lost in the current interface. This can be assembled as an OPML file. Here is how it would work.
  • Each webpage indexed has an auto-generated OPML assigned to it. This would be part of each return generated by a search engine.
  • The pages OPML file would contain relational metadata. Here is a list of what it could contain:
    • Sites (URLs) that link to it.
    • Sites (URLs) that it links to
      • Internal to the site
      • External to the site
    • Keywords where it scores within the top ten returns
    • Documents it links to
    • Pictures it links to
    • Sites that are similar
    • A cached version of the page
      • Times when it was updated (with links to a cached copy of each previous update)
    • Publisher information (author, organization, etc.)
  • A link to a webpage included in the relational content would be a link to its OPML file. This way, I could move from rich description to rich description.

5:49:48 PM    comment   

Unfortunately, for AOL (and the rest of us), the regional bells didn't repeat their mistake with broadband.  Broadband DSL is tightly controlled by the bells (efforts to decouple this control have largely failed -- there are plenty of CLEC carcasses along that path).  AOL's initial option was to acquire companies with cable assets like Time Warner, but cable franchises are fragmented and regional in nature.  For example: Time Warner's cable connections can only reach ~17% of households.  AOL has also found that Microsoft and the DOJ are standing in the path of future acquisitions.  This means that they need another strategy.

To get at the customers it can't provide broadband access to, AOL needs to move to a software only strategy.  What is an effective broadband software strategy for AOL?  Here is my thinking:

1) A heavy desktop client application that chews up bandwidth and processor cycles.  This leverages the all-you-can-eat bandwidth provided by the telcos and the cable companies.  It allows AOL to continue it free rider strategy -- it doesn't have to pay for that bandwidth (OPB -- other people's bandwidth).  It also allows them to leverage the 140 m PCs that will be sold this year with GHz processors and 40 Gb of storage (OPP -- other people's processors).   This dynamic makes it possible for AOL to offer a high end media rich experience to its customers at a low cost.

2) Connect those heavy desktop clients to webservices.  SOAP services that provide sports scores, weather info, financial data, search services, media playlists, chat room messages, etc. will allow AOL to keep these apps up to date, lively, and connected.  It also allows AOL to keep its centralized infrastructure lean (<<$$).

3) Connect these apps to other AOL users via P2P webservices (most likely powered by AIM).  This allows AOL to generate network effects from the use of its software.  Shared calendars, shared files, IM, etc.  This grass roots community development, if rich enough in features, would draw people into its network even if they buy their bandwidth from a telco (Reed's law >>$$).  It also would allow them to distribute heavy media in a cost efficient fashion (OPB). 

So, how will AOL build this heavy client?  One option is .Net, however, that would put them at the mercy of Microsoft.  Not an option.  The other option is to acquire a platform that can provide them this functionality. 

5:44:06 PM    comment   

Which digital consumer vision wins? 

1)  Increasingly mobile PCs (tablets, laptops, and wearables)  vs.

2) PC Home Servers (beefy multi-user devices with smart screens and home management) vs.

3) PSD (Personal Storage Devices like the iPod) vs.

4) Storage-enhanced TVs?  [John Robb's Radio Weblog]
5:41:34 PM    comment   

ComputerWorld on British Telecomm's commitment to Wi-Fi: note the mention in the article about Britain's spectrum regulatory agency making a decision soon to allow commercial use of the unlicensed 2.4 GHz band.

5:11:27 PM    comment   

Bouygues is the No. 3 mobile operator in France and is 65 percent owned by the Bouygues construction, media and telecom group.
3:14:54 PM    comment