Re: Mapping of DAML+OIL onto DB

> I'm actually interested in the immediate reasoning on the DB if that is
what
> you are
> suggesting.  I want to do intelligent querrying immediately onto the DB
> benefitting from the performacne improvement a DB can give me.  I mean, I
> want to search through my ontology and suggest things to the user to
improve
> his search using the ontology, but I don't think this is possible with a
> large structure using a Description Logic like OIL+DAML.  So I thought a
DB
> would be interesting in this respect.  Suggestions are always welcome,
thank
> you very much for the  pointers I allready received.
>
> peter
>

I'm using the ICS-FORTH RDFSuite[1]. This suite includes RDF storage in a
PostgreSQL DB, and a query language (RQL) that access the stored ontologies.
By now, it just let you use RDF, not DAML+OIL. The suite includes tools for
storing the RDF file, including classes, properties and instances.

> > On April 3, Hector Ceballos writes:
> > > You're mentioning initiatives and works for mapping ontologies in
> > > databases, but is there any initiative for especifying in certain
> > > way a relationship between classes/properties and objects stored in
> > > a database? This way, ontologies would remain at web but instances
> > > could be stored locally and accesible through intelligent agents or
> > > other kind of services.  Probably it's not related with original
> > > question, but I'd like to know if exist something like this.

My last comment arises because I consider convenient to have a fast access
"backup" of the ontologies stored in a database, but instances could be
accessed directly from other database (a production database, for example)
just mapping ontology to that DB. This way, using a common query language
you could reference ontology and instances at same time.

Greetings
Hector G. Ceballos

[1] http://139.91.183.30:9090/RDF/index.html