Generic Interoperability Framework (original) (raw)

The new release of GINF is under preparation, stay tuned! New features include:

Updated RDF parser (SiRPAC) capable of reading data from stream (can handle very large data sets like the Open Directory) — prerelease available for download!
GINF has been coupled with the SiLRI interence engine (thanks to Stefan Decker)
SQL database interface for storing and accessing RDF models (see the discussion on Storing RDF in relational databases)
Declarative mediation environment: support for a set of declarative languages for data conversion and protocol translation will be included in the next distribution. Find out more about the upcoming features in the technical report (Dec 01).

Note that the information below is somewhat outdated.

Introduction

The Generic Interoperability Framework (GINF) has been developed to facilitate integration of heterogeneous components. One of the main principles it employs is the generic representation of protocols, languages, data and interface descriptions. The current implementation of the framework is based on RDF. The implementation of GINF provides semantic-oriented middleware for application development and integration. GINF middleware allows creating open and highly extensible client/server applications. It is available for download.

Overview (very abstract)
Slides
GINF middleware (description of the current implementation, under construction)
RDF schema implementation in GINF
Application to Digital Libraries. Examplesof XML serialization of RDF models in the "Application" document.
The Resource Description Framework (RDF) homepage
A set-theoretical model for RDF

Current status

GINF middleware is highly experimental, interfaces are subject to evolution. It is still not stable enough for broad usage, therefore the documentation provided is sketchy. Look at the sources for more information.

Currently, its usability is being evaluated using the following Stanford Digital Library testbed applications:

WebBase Streamer: Stanford WebBasestores a significant part of the WWW in fulltext. Making this data available for data miners is a topic of active research. We're designing and testing GINF-based interfaces for streaming and multicasting the collected Web data.
Digital Library search: we consider how the concepts and interactions of the SDLIPprotocol can be modeled within GINF.
Protocol / interface specifications using finite state automata (FSM): we design a vocabulary for machine-readable generalized FSM specifications that can be used to automatically generate components conformant to the protocol/interface. We also consider automatic protocol translations.

Software download

The Java library includes following features:

RDF parser: a modified version of SiRPACusing XML parser AElfred
RDF serializer
RDF model interface
RDF schema validation
HTTP protocol mapping [TCP/IP temporarily unavailable] Please keep in mind that the interfaces and the HTTP mapping are still very experimental and are subject to changes.
This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation.

The javadoc-generated documentationand installation instructions are available online, but are is also included in the distribution. More comprehensive documentation is in preparation (check out GINF middleware).

This release (July 13, 1999) contains a number of bugfixes and a new demo application (search server and client from the demobelow).

Download: ginf-1.1a.zip(307K) or ginf-1.1a.tar.gz (190K)

Have a look at current issues.

Please send comments, bug reports and suggestions to melnik@db.stanford.edu

Schemas / ontologies:

(Please not that the schemas below are still under construction. HTML descriptions of some of the schemas are still not available)

Core communication
Basic state maintenance
Protocol mappings: HTTP,TCP/IP
Load balancing
Constrained collection
Core search (see also ApplicationandExamples)
State maintenance for digital library search

Demos

Live wire to a search server implementation.
The data on which the server operates.
Example of a client interface to the server. This is a signed applet so you have to import a certificateto run it. Runs with Netscape Communicator only.
Example of a canonical wrapper interface for a real-time wind condition servicein the Bay Area (temporarily offline)

Sergey Melnik. Last change: Dec 02, 1999