Easy-Information-Service-Collaborative-Model

EASY INFORMATION SERVICE

Avijit Samanta Software Engineer

Caritor India Pvt. Ltd

E-Mail – samanta.avijit@gmail.com

01/01/2006

Draft 1.0

Information WWW Service Information Service Engine (ISE)* End Users

Data

Information

Knowledge

*ISE is derived idea from Andrei Broder Information Supply Engine

REST Ajax/Reverse Ajax

Know-How about D-I-K

Data can be represented by some name. Data is raw;it exists and has no significance beyond its existence. It can exist in any form,usable or not. It does not have meaning by itself.

Information on the other hand is an explicit association between items of data. Associations represent a function relating one set of things to another set of things. Information can be considered to be data that has been given meaning by way of relational connections . So here comes concept of Triple (Subject - Predicate – Object).

Knowledge can be considered simply as a assimilation of Information. It is an appropriate collection of information, such that it is useful. Knowledge-based systems contain knowledge as well as information and data. Here the term Information Service Engine comes.

Improved Information Management

Textual Information:

HTML ( Simple form for Human Read)

XML/ JSON ( M/C Readable) JSON ( JavaScript Object Notation) is clearly the buzzword of the new data interchange format. JSON’s clever idea of being a subset of JavaScript makes it instantly useable,lightweight, and highly nimble way to handle data interchange for Ajax. It’s faster to parse and easier to use than XML. It's also tested that parsing JSON by XMLHttp request is 10 times faster than parsing similar XML.Commercial Web Service providers like Yahoo makes most of their web services JSON enabled.Yahoo's various search services,travel services,del.icio.us etc. support JSON output.Recently Google's child search engine Searchmash.com is providing service APIs in RESTful way in JSON format.*

Management Approach : Resource Description Framework (RDF)

Non Textual Information

Image

Audio/Video

Management Approach :

Taxonomy ( Tagging/Labeling)

Resource Description Framework (RDF)

* www.developer.com/lang/jscript/article.php/3596836

Some Taxonomy approaches with Human Computing

ESP Game : Image labeling, available on net. Improving image search in Google through Probabilistic Human Tagging

Pick a Boom: Image labeling, available on net.Identifying objects in Images.

Verbosity : Game of guessing Object/Entity with common facts. Important in our discussion. As it will be a good approach for providing proper contextual data to the ISE.

All the above are easy and FUN to implement and it is a proven TRUTH.*

Constraints of Video :

Video labeling with the above approach will not be a easy and of course will be time consuming. Making some snapshots for a video may create some proper meaning to the user and also help us to implement labeling.

RDF come to the rescue :

RDF is a W3C standard for describing Web resources,such as the title,author,modification date,content, and copyright information of a Web page. This powerful framework make the searching and supply (info service) of non textual information easy as it just sits o top of the Taxonomy.It can refer to the grouping pf labeling and can create a powerful info service for the consumer.

* Found a great lecture on Human Computing on Google Techtalk.

From above the diagram it is clear to build a RDF on top of Taxonomy where the base layer will be independent of the upper layer.

Example :

<?xml version="1.0"?>

<RDF>

<Description about="http://www.myimages.com/type/{query}">

<context>apple PC,IPOD.Bring new era in Music industry.</context>

<category>Informational</category>

</Description>

<Description about="http://www.myimages.com/type/{query}">

<context>Sweet,Fruit,Red.Kashmiri apple</context>

<category>Informational</category>

</Description>

</RDF>

The above is a just a very rough and bit of info about RDF power. A lot of RDF elements can be implemented to make it more powerful.

Taxonomy RDF

ISE & It’s role in Service

The term “service” here actually does not specify only the web service that can be discovered, described , and accessed based on XML and standard Web protocols over intranets, extranets, and the Internet. Here we are thinking it more simple in sense of REST architectural style to provide a better resource discovery than SOAP messaging as it uses simple GET and POST over http. Also it is making Web Service more Decouple in nature in aspect of getting information. Also this “Service” term is related to the ISE which serves the purpose of a middleware information manager for getting accurate information and in a efficient way.

Before going to the architectural style of ISE we should convey the ideas in REST.

REST Principles

Client-Stateless-Server

Advantage: Reducing Server overhead for maintaining session states for every round trip and navigation

Disadvantage: Increase repetitive data (per interaction overhead) sent in a series of requests.Using cookie (domain wise cookie will be worst) will make the Request packet size larger also. * Google

Our workaround: Storing info in a separate place rather than in client side or Web Server. XML text file or JSON text file can be use for small data,easy to fetch and parse. And most important part is to use Ajax with it for enjoying stateful Web Client when necessary. According to “Bill Higins” of IBM – {“the fact that Ajax lets you to interact with a server without a Full Refresh puts the option of stateful client back on the table.This can enjoy the best of both the worlds – the dynamic,personalized user experience and the simple,scalable RESTful application”}

* Optimizing page Load time article by Aaron Hokins of Google.

Cachebility ,supported in Ajax itself.

Uniform Interface :

The central feature that distinguishes the REST architectural style from other network based styles is its emphasis on a uniform interface between components. By applying the software engineering principle of generality to the component interface, the overall system architecture is simplified and the visibility of interactions is improved.Implementations are decoupled from the services they provide which encourages independent evolvability. The trade-off , though, is that a uniform interface degrades efficiency, since information is transferred in a standardized form rather than one which is specific to an application’s needs. The REST interface is designed to be efficient for large grain hypermedia data transfer, optimizing for the common case of the Web, but resulting in an interface that is not optimal for other forms of architectural interaction.

Just to say above the last statement, the interaction can be classified in 3 natures :

Informational : The intent is to get some information assumed to be present on one or more web pages. (48%)

Navigational : The immediate intend is to reach a particular web site (20%)

Transactional : The intent is to perform some web related activity. (30%)

The % statistics is a daily log average from AltaVista.

RDF here comes to the rescue to the above stated constraint. We can easily handle this situation by providing sufficient metadata to describe the resource and make the life of the user easy.

The evolution of commercial web Search engines

• First generation -- use only “on page”, text data

– Word frequency, language

1994-1997 AV,

Excite, Lycos, etc

– • Second generation -- use off-page, web-specific data

– Link (or connectivity) analysis

• Sophisticated mathematical methods

– Click-through data (What results people click on)

– Anchor-text (How people refer to this page)

From 1998. Made

popular by Google

but everyone now

• Third generation -- answer “the need behind the query”

-- Focus on user need, rather than on query

– Semantic analysis -- what is this about?

– Integrates multiple sources of data

– Help the user

• UI, spell checking, query refinement, query suggestion, syntax driven feedback, context

help, context transfer, etc

Still evolving – Google new feature of Query Refining, Yahoo Intent Driven Search and Context search

• Fourth generation – Information Supply

Information Supply with Reverse Ajax

Alex Russel (DOJO creator), Bryce Nesbitt and with the release of DWR release 2.0 by Ajaxian.com , a new term is introduced into the Ajax vocabulary – Reverse Ajax. This actually implements the idea of Server Push technology in a standard web browser asynchronously. Actually there are several techniques available to implement:

“ HTTP streaming/Comet”: which lets the server decide when to refresh the client,without client requiring to Poll. As the HTTP connection is closed after each response, it is a implicit problem for server for implementing Server Push technology. Comet,Long lived or the slow load technique allows the server to keep a communication hannel open to pass down the informationdd when time comes.

Polling: In this scenario the browser makes a request to the server at a regular and frequent intervals.

Piggybacking: Not clear about this. Anyone have any idea?

The above techniques will make the Information Supply which is a integral part of Easy Information Service, more easy and visible,flexible for end user satisfaction.

ISE Activity Architecture Update Knowledge ISE Database End User Display Query Result Feedback/Query Refinement Information Supply User Profile & Context Activity frequency Advertiser Ads Inventory (RSS/Atom) RDF Web Bots/Crawlers Caching WWD Use Knowledge

Is ISE is a new Generation?

The answer is clearly not. It is the derivative idea of cumulative models where all the models together (Colaborative approach) make information era stays on a framework for servicing information in a easy and more efficient way. To the end user the whole implementation should be transparent except the quality of Information service to the end user will gradually be improved everyday and results with more relevant to each user (Personalization), even make search with single shot result.

References