You are on page 1of 19

Assignment-B Topic 18

Towards Heterogeneous
Multimedia Information Systems:
The Garlic’ Approach

Submitted by: Group 4


Ankit Sanduja 09609160
Kuber Sethi 09609101
Jaya Mamta Prosad 09609093
Jasmeet Kaur 09609154 

12/07/21 The Garlic Approach 1


THE GARLIC APPROACH

It is a project being researched at IBM.

The objective of the project


To develop a system that can handle large amount o heterogeneous data.

What is heterogeneous data?


It includes all the data that are stored in data repository or database.
It includes media files, images, video and normal text

12/07/21 The Garlic Approach 2


What is Goal of the Garlic
approach?

To create mew system that can put together data from different
database system.
Even though the database systems have advanced a lot but still a lot of
work has to be done on multimedia storage and retrieval. Garlic
project claims that it will take the multimedia management system
one step forward.

12/07/21 The Garlic Approach 3


12/07/21 The Garlic Approach 4
Repositories-It’s just a place where data is stored

To communicate to the repository we need wrappers.

Wrappers is just a piece of code that developer will develop.

Query-Whenever we want to interact with the database we have to write a


query.

Here Garlic extends SQL with different construct for efficient retrieval.

12/07/21 The Garlic Approach 5


The Need

The bulk of the data in the world is not


stored in database management
systems. There are many specialized
systems emerging to store and search
for particular data types, including
image management systems, etc.
However, many applications can
benefit from combining information
from these various systems.

12/07/21 The Garlic Approach 6


Garlic Overview

1. Repositories
i. Repository type
ii. Repository instance
iii. Repository manager
2. Databases
i. Global schema
ii. Wrapper schemas (local schemas)

12/07/21 The Garlic Approach 7


Garlic Data Model
ODMG-93 object model
Objects and values
Inheritance
Object identity
Weak identity – unique, not necessarily immutable
Legacy references
Implementation-constrained reference

12/07/21 The Garlic Approach 8


Garlic Data Model
Extensions
Degree of support for alternative implementations of interfaces
Type system flexibility - conformity
Object-appropriate view definition facility
Object-Centered Views
Enhance objects by adding or hiding some of their
attributes/methods.

12/07/21 The Garlic Approach 9


Queries in garlic
Access to Garlic database through high level query language.

Query language for Garlic: Object Oriented extension of SQL

E.g.:
select P.cust-name, (C.pictures}
f'rom Policy P, P.claims C, C.pictures X
where (C.date-filed - P.start-date) < 60 and
C.report.matches("fatality speeding") and
X.matches(["color", RED, .15])

12/07/21 The Garlic Approach 10


Garlic query processing
Query

Decomposition of Query
Translated by SQL into
Smaller queries
Intermediate Form

For manipulation
by Query
Decomposition
Facility

[QDF] Individual Repositories

Middleware
Combining query results
into final form
12/07/21 The Garlic Approach 11
Garlic Interfaces and applications
Data accessible through 2 primary interfaces.

1) C++ Application Programming Interface or


(C++API): to support both compiled and dynamic C++ applications.

2) Query/Browser Interface: to provide end users with an easy


and highly visual way to access and manipulate the data in a Garlic
database .

12/07/21 The Garlic Approach 12


How Garlic model differs from
ODMG-93

1. treatment of object references and integrity constraints.


2. Object identity:The ODMG-93 data model guarantee that an
object’s identity be both unique and immutable.
3. Garlic database, references in the Garlic data model are based
on a notion that we call weak identity;
4. An important consequence of weak identity is that it allows
Garlic to treat data items for which only weak identification is
possible

12/07/21 The Garlic Approach 13


Legacy references

1. problem related to identity and object references in Garlic is the fact


that legacy data can contain legacy references.
2. The Garlic data model addresses the problem of full weak identifier
format by providing the notion of an implementation-constrained
reference.
3. Garlic supports the association of implementation constraints with
the reference attributes mentioned in the interface.
4. Garlic object that has the appropriate interface; rather, it can only
reference tuples in the specified target table within the same
relational database.

12/07/21 The Garlic Approach 14


Other differences

1. Garlic does not support the specification of key attributes for


interfaces, as it has no way to enforce such uniqueness.
2. the concrete C++ realization of the ODMG-93 model does not
support key attributes either
3. Garlic supports this option fully for Garlic complex objects Garlic
cannot possibly enforce such constraints

12/07/21 The Garlic Approach 15


Object-centered views

1. Garlic scores over ODMH- 93 in regard that it is sufficiently


restrictive yet powerful.
2. In Garlic, the primary purpose of a view is to enhance (extend,
simplify, or reshape) a set of underlying Garlic objects
3. Garlic introduces the notion of an object-centered view
4. an object in a view consists of the identity of its center object
5. Garlic is prepended with an implementation identifier that indicates
the view from which the object was obtained.

12/07/21 The Garlic Approach 16


Conclusion
1. The goal of the Garlic project at the IBM Almaden Research Center
is to build a heterogeneous multimedia information system (MMIS)
capable of integrating data from a variety of traditional and non-
traditional data repositories.

2. The overall architecture for the system is based on repositories,


repository wrappers, and the use of an object-oriented data model
and query language to provide a uniform view of the disparate data
types and data sources that can contribute data to a Garlic database.

3. Use of Object store object-oriented DBMS [46] to hold both the


complex objects and the metadata objects in the prototype.

12/07/21 The Garlic Approach 17


Conclusion Contd…
In future the Garlic project to lead us into new research in many
dimensions, including object-oriented and middleware query
processing technologies, extensibility for highly heterogeneous,
data-intensive environments, database user interfaces and
application development approaches, and integration of exact- and
approximate-matching semantics for multimedia query languages

12/07/21 The Garlic Approach 18


Thank You
Any questions ?

12/07/21 The Garlic Approach 19

You might also like