W3C home > Mailing lists > Public > public-sw-meaning@w3.org > October 2003

Re: A bit of running code for "Tim's View"

From: pat hayes <phayes@ihmc.us>
Date: Wed, 8 Oct 2003 15:12:46 -0500
Message-Id: <p06001f04bbaa1c5bad48@[]>
To: Sandro Hawke <sandro@w3.org>
Cc: public-sw-meaning@w3.org

>  > if the bio:page states
>>       bio:Dog a bio:mammal
>                ^ assuming you mean ferrell:subClassOf   ?
>>  will you output
>>    Donny a bio:mammal.
>Yes.  The triples are all just throw together into one store.  As each
>one gets thrown it, it gets examined to see if it suggests still more
>should be thrown in.  (forming the "web closure", pruned (to be fairly
>small in this case) because we're not following URIs in the subject
>position.)  In cwm's case, given --think, once its done finding the
>pruned web closure, then it computes the deductive closure (also
>finite, even small), which it outputs.
>There are some interesting possibilities for backward chaining, and
>for reaching out onto web at the same time as doing inference, but cwm
>doesn't try that right now.
>The actual test I proposed for Tim ended with asking cwm which dogs it
>knew about, so I didn't have to wade through all the other stuff cwm
>might have gathered and inferred.
>>  If the bio: page contains
>>     :Coconut a :Cat
>>  will cwm claim
>>     bio:Coconut a bio:Cat.
>>  ?
>Yes.  The triples on the bio page are thrown in with the rest.  (I
>suggested we may want to tag where they came from for
>explanation/trust reasoning, some day soon.)

Yes, soon. I think tags like this would be handy for many engines, in 
fact.  Our graphic RDF/OWL editor needs to keep them around for more 
mundane reasons: even for writing simple markup, the user often wants 
to be able to check where a concept 'comes from'.

Maybe that would be a good architectural principle: SW concept names 
should always 'come from' a unique resource, which we might call the 
provenance of the name.  Exactly what this means, and what 
relationships there might be between the resource they come from, the 
representations extracted from that resource using other Web 
protocols, and what the concept name should be understood to denote, 
can all be discussed at more length; but at least that would give us 
a piton to nail into the rock.


IHMC	(850)434 8903 or (650)494 3973   home
40 South Alcaniz St.	(850)202 4416   office
Pensacola			(850)202 4440   fax
FL 32501			(850)291 0667    cell
phayes@ihmc.us       http://www.ihmc.us/users/phayes
Received on Wednesday, 8 October 2003 16:12:48 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 19:56:01 UTC