Composing pervasive data using iQL

Abstract

The emergence of pervasive networked data sources, such as web services, sensors, and mobile devices, enables context-sensitive, mobile applications. We have developed a programming model for writing such applications, in which entities called composers accept data from one or more sources, and act as sources of higher-level data. We have defined and implemented a nonprocedural language, iQL, specifying the behavior of composers. An iQL programmer expresses requirements for data sources rather than identifying specific sources; a runtime system discovers appropriate data sources, binds to them, and rebinds when properties of data sources change. The language has powerful operators useful in composition, including operators to generate, filter, and abstract streams of values.

Context-Sensitive Resource Discovery

“…A non-procedural language, iQL, can also specify the logic for composing pervasive data into context [7]. Their model supports both requested and triggered evaluation.…”

Design and implementation of a large-scale context fusion network

“…It is also possible to provide a domainspecific language that specify the context-fusion logic, which Solar then parses into several operators for deployment [8]. IBM's iQL is an example of such a language [12].…”

“…Its precedent, iQueue, is also a distributed system that allows application to specify data composers like Solar operators [13]. The group also developed an expressive domain-specific language, iQL, for the composer specification [12]. We believe many of Solar's services could be easily used by ContextSphere to manage the composers, such as our context-sensitive directory, policy-driven flow control, and dependency management.…”

Context aggregation and dissemination in ubiquitous computing systems

“…The challenge is to invent a subscription language sufficiently powerful to encode complicated aggregations, and yet simple enough to efficiently parse into an operator tree. A language like Java is highly expressive, but a language like SQL, XQuery, or iQL [9] may offer more structure. The language needs a structure that encourages the programmer to describe the event flow in a way that is easily decomposable and likely to match other applications' operator trees.…”

“…A non-procedural language, iQL, can specify the logic for composing pervasive data [9]. The model supports both requested and triggered evaluation.…”