|
Tuesday, August 20, 2002
China's Linux Initiative
The Register writes about China's efforts to create a home-grown Windows-like OS:
This initiative can bring down the cost of software, but what about the cost of hardware? That is where we need to think of using Thin Clients and Server-based Computing. In countries like India and China, software is anyway considered "free" (rampant piracy). It is important to reduce the cost of both hardware and software.
Technology as Silver Lining
Dan Gillmor writes about the change technology is bringing and captures the essence of the change that's taking place:
Newsweek on Blogs
Writes Steven Levy in Living in the Blog-osphere:
Tomorrow's Notebooks
Writes News.com: "Fuel cells and battery enhancements, which will let notebooks run three to 10 times longer without a recharge, will begin to appear by late 2004. Smaller hard drives and screens will also likely lead to some changes in the classic notepad shape for some models. Multiband wireless communications, in which notebooks drift from cellular to Wi-Fi to back, will be common."
TECH TALK: Tech's 10X Tsunamis: Blogs and RSS (Part 2)
The Information Refinery The Information Refinery can be thought of as consisting the following entities: Miners: Just likes ores need to be extracted from mines, RSS miners collect the RSS feeds from different sources. Miners listen to sources which send the raw, unstructured information to them, or extract information through bots. They then take the information and send them to specialized adaptors for RSS extraction. Adaptors: These are the interfaces to the outside world. A 1-way Input Adaptor takes events and RSS-ifies them for use by the refinery. A 1-way Output Adaptor takes an RSS feed and converts it into events suitable for use by an external application. A 2-way adaptor does both. In other words, from the point of view of the refinery, an Input Adaptor is “read-only” and an Output Adaptor is “write-only”. The 2-way adaptor is “read-write”. For example, there are Blog 1-way adaptors which will take RSS feeds from weblogs (or create RSS feeds if one does not exist). We can think of News Adaptors which take a URL for the site, and make an RSS feed comprising the headlines. A Mail Adaptor can read from an email message and convert to RSS. A File adaptor can take information about the file and create an RSS feed about it (extracting perhaps the first few sentences from the file as the description). We can think of a Tally (or Quicken) 1-way adaptor which extracts information from the application and creates RSS events (using financial reporting standards) which can be fed into the information refinery. RSS Spoolers: They take the RSS feed from the adaptors. They take subscription requests for the feeds through Agents. An agent is instantiated for every subscription request. Agents have rules to decide what to do. For example, Ram’s agent can decide that he wants the News.com and WSJ.com RSS feeds in full, while he wants all other entries with the keyword “XML” in them. The agents look at each of the incoming feeds and take the appropriate action. They route the RSS feeds/entries to other RSS spoolers or RSS Aggregators. RSS Aggregators: There is one RSS Aggregator per subscriber/entity which is the end consumer of RSS feeds. Think of these as comprising one set of end points (the other being the information sources). RSS Aggregators have an RSS Store (database), for archiving older entries. They can publish the aggregate feed to an RSS Viewer. Or, then can send the RSS entries to Processors. Processors: They embed business logic/ rules as to what action needs to be taken with RSS feeds. For example, they can send events to an Alerts engine to notify the user via email/IM/SMS, or create other RSS events. As such, processors can thus also be considered as information sources which put out RSS feeds for re-distribution. Processors can also work on the RSS store to create specialised applications. RSS Viewer: This shows all the RSS entries organized by source or time to a user, who can then decide if he wants to either delete the entry or publish it to a blog. An RSS Viewer should be capable of having multiple pages to support categorisation of the incoming entries. Blogging Platform: This is a weblog tool like MovableType or Radio which enables management of the blog. A blog should be capable of having multiple categories (with sub-levels). The user can decide on the access rights for the categories (public, private, group). It should also be able to publish RSS feeds for specific categories. Digital Dashboard: This is a browser with three tabs: one for viewing the RSS Aggregator feed, one for writing and one for viewing the user’s own blog. It is the unified read-write interface. Tomorrow: Blogs and RSS (continued)
Tech Talk
| PermaLink
| Comments (3)
Rajesh's articles are thought provoking, interesting, and useful. Please keep them coming. Here's another, perhaps less practical, approach to RSS and BLOGs. Most site content exists in semantically rich structured databases. The semantics is lost when the content is converted to HTML (for rendering on the screen) for human consumption as opposed to machine Consider the following ideal scenario: * All content is maintained in structured (relational or XML) databases. Problem solved. Didn't I say ideal and less practical!? Posted by Gopi ReddySeekers of truth invariably turn to lies. Posted by Kalish SethI was browsing google for xml xsl, when I found your blog. Even though it's been awhile, I must say you were rigth about the way of doing things. I am building blog+rss page (actually, custom page with blog+rss in it) with XSL (for corp intranet review), but until recently xsl was just considered too hard. We're using XSLmaker to build stuff from xml feeds and to author xml - just like you outlined. This is the first time I am developing everything 100% XML; even though last year I could have coded everything, there were not tools available. Take a look at xsl maker (www.xslmaker.com), it pretty much does what you envisioned. Mohan Posted by Mohan Ganatra |