Thread Links Date Links
Thread Prev Thread Next Thread Index Date Prev Date Next Date Index

SUO: RE: ONT RE: Ontology case study




Matthew,
   I went to the Vality web site and it sounds interesting but they don't 
provide any technical details on the meta-data definition language and 
whether in fact it could handle constraints like "birth date <death 
date".  Do you have any further information you could point me to?

Adam

At 08:30 AM 6/13/2002 +0200, West, Matthew R SITI-ITPSIE wrote:
>Dear Adam,
>
>See comments below.
>
>
>Matthew West
>Principal Consultant
>Shell Information Technology International Limited
>Shell Centre, London SE1 7NA, United Kingdom
>
>Tel: +44 20 7934 4490 Other Tel: +44 7796 336538
>Email: matthew.r.west@is.shell.com
>Internet: http://www.shell.com
>
>
>snip
> > > > > >
> > > > > > Note also that having the data entry clerk check this
> > > > > > constraint is not a
> > > > > > practical solution.  Typos happen, humans make errors.
> > > > >
> > > > >MW: This is a different case. Adding checks on data entry is
> > > > >quite common. But it is not considered part of the
> > static database
> > > > >design (that the data model supports). It might also be a check
> > > > >you run on the whole database periodically.
> > > >
> > > > Eureka!  And that periodic database check would be one way to
> > > > use a formal
> > > > ontology, doing data cleaning, checking for data entry
> > typos, against
> > > > constraints like and individual's birth must come before his
> > > > or her death.
> > >
> > >MW: Quite. But as noted above, this constraint would only pick up
> > >a small percentage of typos, and there are tools available to do
> > >this kind of check,
> >
> > What tools would those be?
>
>MW: I am thinking of something called Vality.
> >
> > >  and you can also set database triggers to perform
> > >the check on data entry.
> >
> > Of course, and in the case of using an ontology, one would
> > set a "trigger"
> > to check the data using an ontology and theorem prover.  The other
> > alternatives, are either to implement the trigger using procedural
> > (imperative) code, or not at all.
> >
> > Adam
> >
> >
> > > >
> > > > Adam
> > > >
> > > > > >
> > > > > > Adam
> > > > > >
> > > > > >
> > > > > >
> > > > > > Adam Pease
> > > > > > Teknowledge
> > > > > > (650) 424-0500 x571
> > > > > >
> > > >
> > > > Adam Pease
> > > > Teknowledge
> > > > (650) 424-0500 x571
> > > >
> >
> > Adam Pease
> > Teknowledge
> > (650) 424-0500 x571
> >

Adam Pease
Teknowledge
(650) 424-0500 x571