Difference between revisions of "Middleware 09"

Revision as of 06:19, 2 March 2009

Middleware 09:

Important Dates

• Submission deadline: April 20, 2009.
• Deadline for concrete problem definition: March 5, 2009.
• Deadline for identifying evaluation metrics: March 10, 2009.
• Deadline for drafting motivating examples that are synergistic with problem statement and evaluation metrics: March 14, 2009.

Pitch

In this section I am adding some definitions that will help us to pitch our idea in the context of what has been talked about on the Web.

* DeepWeb

"Mike Bergman, credited with coining the phrase, has said that searching on the Internet today can be compared to dragging a net across the surface of the ocean; a great deal may be caught in the net, but there is a wealth of information that is deep and therefore missed. Most of the Web's information is buried far down on dynamically generated sites, and standard search engines do not find it. Traditional search engines cannot "see" or retrieve content in the deep Web – those pages do not exist until they are created dynamically as the result of a specific search. The deep Web is several orders of magnitude larger than the surface Web." http://en.wikipedia.org/wiki/Deep_web

* LinkedData

Linked Data is a term used to describe a method of exposing, sharing, and connecting data on the Web via dereferenceable URIs. "The Semantic Web isn't just about putting data on the web. It is about making links, so that a person or machine can explore the web of data. With linked data, when you have some of it, you can find other, related, data." Tim Berners Lee http://www.w3.org/DesignIssues/LinkedData.html

 * SPARQL Endpoints

"Sometimes the sheer volume of data makes serving it as lots of files possible, but cumbersome for efficient remote queries over the dataset. In this case, it seems reasonable to provide a SPARQL query service. To make the data be effectively linked, someone who only has the URI of something must be able to find their way the SPARQL endpoint."

Here again the HTTP 303 response can be used, to refer the01-15 enquirer to a document with metadata about which query service endpoints can provide what information about which classes of URIs. Vocabularies for doing this have not yet been standardized." http://www.w3.org/DesignIssues/LinkedData.html

* Publish/Subscribe systems

"Publish/subscribe (or pub/sub) is an asynchronous messaging paradigm where senders (publishers) of messages are not programmed to send their messages to specific receivers (subscribers). Rather, published messages are characterized into classes, without knowledge of what (if any) subscribers there may be. Subscribers express interest in one or more classes, and only receive messages that are of interest, without knowledge of what (if any) publishers there are. This decoupling of publishers and subscribers can allow for greater scalability and a more dynamic network topology." http://en.wikipedia.org/wiki/Publish/subscribe

* Reactive Web

"Reactive rules are used for programming rule-based, reactive systems, which have the ability to detect events and respond to them automatically in a timely manner. Such systems are needed on the Web for bridging the gap between the existing, passive Web, where data sources can only be accessed to obtain information, and the dynamic Web, where data sources are enriched with reactive behavior. This paper presents two possible approaches to programming rule-based, reactive systems. " http://rewerse.net/publications/rewerse-description/REWERSE-RP-2007-031.html

Key architectural principles

Papers to refer for writing style

• End-to-end support for joins in large-scale publish/subscribe systems [1]
• Top-k/w publish/subscribe: finding k most relevant publications in sliding time window w [2]
• please refer to [SVN related work link http://knoesis1.wright.edu/svn/docs/papers/mw09/related/style-refs]