IW Meeting 2013-04-25

From Inference Web

Jump to: navigation, search

Contents

Meeting Information

Agenda

Attendees

Meeting Preparation

Around the room

* Add a section for yourself 2 hours before meeting.
* Mark any discussion point that you would like to raise during meeting (with DURING MEETING). 
* Otherwise, assume that others will read the rest before meeting. 
* Also, please be considerate and read others' discussion points before the meeting starts.

Tim

Jim

James

Cynthia

Paulo

Patrice

Deborah

Discussions

https://docs.google.com/spreadsheet/ccc?key=0ArTeDpS4-nUDdFdBYkRUQ0hvUWFpTy1ObjlZSTJEaXc#gid=0

hasDescription

just catching up from last week http://inference-web.org/wiki/IW_Meeting_2013-04-18

From the three examples that we discussed, it seems to Tim and Jim that they can be covered with:

  • dcterms:description,
  • rdfs:seeAlso, and
  • language tags (e.g. @en), and
  • prov:wasQuotedFrom, prov:specializationOf, prov:alternateOf

Further, TPTP's pmlp:hasDescription would be better modeled as prov:wasQuotedFrom because it was taking smaller substrings from larger strings.

https://docs.google.com/spreadsheet/ccc?key=0ArTeDpS4-nUDdFdBYkRUQ0hvUWFpTy1ObjlZSTJEaXc#gid=0


Organization
name: Artificial Intelligence Center, SRI International
description: 
url: http://www.ai.sri.com/
<http://inference-web.org/registry/ORG/AIC_SRI.owl#AIC_SRI> 
  a <http://www.w3.org/ns/org#Organization>;
  rdfs:label "Artificial Intelligence Center, SRI International";
  rdfs:seeAlso <http://www.ai.sri.com/> 

Ontology
name: DAML+OIL Example Ontology
description: 
language: English
raw-string: DAML+OIL Example Ontology, demonstrates DAML language features.
url: http://www.daml.org/2001/03/daml+oil-ex
version: 1.0
uri: http://inference-web.org/registry/ONT/DAML-EX.owl#DAML-EX
Inference Engine
name: Citation Trust
author(s): Knowledge Systems Laboratory, Stanford University
description: 
language: English
raw-string:  Citation-based trust algorithms are a family of algorithms that derive  trust based on citation relationships among entities.  In particular, we  define the Link-ratio of an article (i.e., the page with title x) as   the ratio between the number of citations and the number of non-citation  occurrences of the encyclopedia term x. 
url: http://www.ksl.stanford.edu/KSL_Abstracts/KSL-06-05.html
version: 1.0
uri: http://inference-web.org/registry/IE/CitationTrust.owl#CitationTrust
Declarative Rule
name: Generalized Modus Ponens
content: 
language: Proof Protocol for Deductive Reasoning (PPDR)
raw-string: A; '(implies (and ' A ')' q ')' |- q;; (Sent A q)
description: 
reference source usage: 
source: Artificial Intelligence: A Modern Approach
usage-datetime: 2003-09-22T17:08:37-08:00
language: English
raw-string:  For atomic sentences si, si" and r, where there is a substitution T  such that subst(T,si")=subst(T,si) for all i:  s1",s2",...,sn",(s1^s2^...^sn => r) implies subst(T,r)
uri: http://inference-web.org//registry/DPR/GMP.owl#GMP
Declarative Rule
name: Hyperresolution
author(s): Otter development team
description: 
reference source usage: 
source: A Summary of Inference Rules Used by Argonne Automated Deduction Software
usage-datetime: 2004-10-14T14:50:53-08:00
language: English
raw-string:  "Hyperresolution focuses on two or more clauses, requiring that one of  the clauses (the nucleus) contain at least one negative literal and the  remaining (the satellites) contain no negative literals. Briefly, a   conclusion is yielded if a unifier (substitution of terms for variables  can be found that, when applied, makes identical (except for sign) pairs  of literals, one negative literal from the nucleus with one positive  from a satellite. The conclusion is yielded by, ignoring the paired  literals, applying the unifier simultaneously to the nucleus and the  satellites and taking the union of the resulting literals.  Otter"s implementation of hyperresolution has two extra features. First,  it can be restricted so that only ``largest"" literals in satellites  can be resolved; this restriction can reduce redundancy for non-Horn  clauses. Second, the negative literals in the nuclei can be evaluable  instead of resolvable; This allows some amount of "programming" of Otter  using built-in operations."
rule example: 
language: English
raw-string: Suppose we have as axioms the following clauses: 
  (or (love ?x ?y) (hate ?x ?y))
  (or (not (try-kill ?x ?y)) (not (love ?x ?y)))
  (try-kill Marcus Caesar)
By substituting "Marcus" for "?x" and "Caesar" for "?y", we may treat  the second clause as the nucleus and the first and third clauses as  satellites.  The opposed literals are resolved, leaving as a conclusion  the resolvent 
 (hate Marcus Caesar)
uri: http://inference-web.org/registry/DPR/Hyp-Resolution.owl#Hyp-Resolution

Templates

https://github.com/timrdf/pml/wiki/Templates-for-generating-information-entities-from-types-of-things

Class: Name
SubClassOf: pml:Information, prov:value some string

Class: NamedPerson
EquivalentTo: foaf:Person and foaf:firstName some xsd:string and foaf:lastName some xsd:string

Class: PersonNameTemplate
SubClassOf: prov:Activity, prov:used exactly 1 NamedPerson and prov:generated exactly 1 Name

Individual: PersonNameTemplate
Types: pml:Template
Facts: prov:value '''{foaf:firstName} {foaf:lastName}'''


:TimothyLeeeeebo
   foaf:firstName "Timothy"
   foaf:lastName "Leeeeebo".  ===> a NamedPerson.
   pml:usableBy jim:PersonNameTemplate;
   .

:myName a jim:Name;
   prov:value "Timothy Leeeebo".
   prov:generatedBy PersonNameTemplate;
   .

pml:usableBy domain Entity, range Plan. 

MPR/DCTrainSensorSimulation.owl

@prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> .
@prefix : <http://inference-web.org/2.0/pml-provenance.owl#> .
@prefix ds: <http://inference-web.org/2.0/ds.owl#> .
@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .
@prefix owl: <http://www.w3.org/2002/07/owl#> .
@prefix daml: <http://www.daml.org/2001/03/daml+oil#> .

<http://inference-web.org/registry/MPR/DCTrainSensorSimulation.owl#DCTrainSensorSimulation>
    :hasDescription [
        :hasReferenceSourceUsage [
            :hasSource <http://inference-web.org/registry/PUB/DCTrainShip.owl#DCTrainShip> ;
            :hasUsageDateTime "2005-07-28T13:34:22-08:00"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
            a :SourceUsage
        ] ;
        a :Information
    ], [
        :hasReferenceSourceUsage [
            :hasSource <http://inference-web.org/registry/PUB/DCTrainAgentDescriptions.owl#DCTrainAgentDescriptions> ;
            :hasUsageDateTime "2005-07-28T13:34:22-08:00"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
            a :SourceUsage
        ] ;
        a :Information
    ] ;
    :hasEnglishDescriptionTemplate """The DC-Train immersive simulation for the Navy damage control domain is able to simulate many sensors on a DDG51-class destroyer, including fire, smoke, flooding, and water pressure alarms.
"""^^<http://www.w3.org/2001/XMLSchema#string> ;
    :hasName "DC-Train Sensor Simulation"^^<http://www.w3.org/2001/XMLSchema#string> ;
    :hasRuleExample [
        :hasLanguage <http://inference-web.org/registry/LG/English.owl#English> ;
        :hasRawString """A primary event of a missile hit is simulated.
Simulation: \"DCCO reports fire alarm in compartment 02-112-0-Q.\""""^^<http://www.w3.org/2001/XMLSchema#string> ;
        a :Information
    ] ;
    a :MethodRule .
    
    

inference-web.org/registry/MPR/DCTrainAgentSimulation.owl

    @prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> .
@prefix : <http://inference-web.org/2.0/pml-provenance.owl#> .
@prefix ds: <http://inference-web.org/2.0/ds.owl#> .
@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .
@prefix owl: <http://www.w3.org/2002/07/owl#> .
@prefix daml: <http://www.daml.org/2001/03/daml+oil#> .

<http://inference-web.org/registry/MPR/DCTrainAgentSimulation.owl#DCTrainAgentSimulation>
    :hasDescription [
        :hasReferenceSourceUsage [
            :hasSource <http://inference-web.org/registry/PUB/DCTrainAgentDescriptions.owl#DCTrainAgentDescriptions> ;
            :hasUsageDateTime "2005-07-28T13:28:09-08:00"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
            a :SourceUsage
        ] ;
        a :Information
    ] ;
    :hasEnglishDescriptionTemplate "The DC-Train immersive simulation for the Navy damage control domain is able to simulate many of the human agents, or \"stations\", on a DDG51-class destroyer, including all personnel directly involved in damage control."^^<http://www.w3.org/2001/XMLSchema#string> ;
    :hasName "DC-Train Agent Simulation"^^<http://www.w3.org/2001/XMLSchema#string> ;
    :hasRuleExample [
        :hasLanguage <http://inference-web.org/registry/LG/English.owl#English> ;
        :hasRawString """DC-Train User: \"Repair Locker 2, investigate compartment 02-112-0-Q.\"
Agent Simulation: \"Repair Locker 2 reports investigators away to compartment 02-112-0-Q.\"
Agent Simulation: \"Repair Locker 2 reports fire in compartment 02-112-0-Q.\""""^^<http://www.w3.org/2001/XMLSchema#string> ;
        a :Information
    ] ;
    a :MethodRule .
    


inference-web.org/registry/MPR/DCTrainDatabaseQuery.owl

    @prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> .
@prefix : <http://inference-web.org/2.0/pml-provenance.owl#> .
@prefix ds: <http://inference-web.org/2.0/ds.owl#> .
@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .
@prefix owl: <http://www.w3.org/2002/07/owl#> .
@prefix daml: <http://www.daml.org/2001/03/daml+oil#> .

<http://inference-web.org/registry/MPR/DCTrainDatabaseQuery.owl#DCTrainDatabaseQuery>
    :hasDescription [
        :hasReferenceSourceUsage [
            :hasSource <http://inference-web.org/registry/PUB/DCTrainKnowledgeOntology.owl#DCTrainKnowledgeOntology> ;
            :hasUsageDateTime "2005-07-28T22:15:10-08:00"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
            a :SourceUsage
        ] ;
        a :Information
    ], [
        :hasReferenceSourceUsage [
            :hasSource <http://inference-web.org/registry/PUB/DCTrainDigitalRepresentation.owl#DCTrainDigitalRepresentation> ;
            :hasUsageDateTime "2005-07-28T22:15:10-08:00"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
            a :SourceUsage
        ] ;
        a :Information
    ] ;
    :hasEnglishDescriptionTemplate """Much of the physical information about the DDG51-class destroyer simulated by the DC-Train system is stored in a massive database.  This information includes the location and geometry of compartments, firemain pipes, and descriptions of all the message types that can be passed between agents in the system.

The DC-Train system, along with agents like the Gerona-based Damage Control Expert (DCX), can query static information in the database through a unified communications interface."""^^<http://www.w3.org/2001/XMLSchema#string> ;
    :hasName "DC-Train Database Query"^^<http://www.w3.org/2001/XMLSchema#string> ;
    :hasRuleExample [
        :hasLanguage <http://inference-web.org/registry/LG/English.owl#English> ;
        :hasRawString """Say we want to determine what frame (distance from the bow of the ship in feet) a compartment lies at (i.e. where the front of the compartment is).  In our Gerona agent, we might have the following logical statement:

world-info( find, _, _, \"Compartments\", [ name <- \"02-112-0-Q\", frame -> Frame ], _, _ )

This would map to a database query such as (in SQL):

SELECT [frame] FROM Compartments WHERE [name]= 2-112-0-Q

(The result would be 112, since the frame number is actually given in the compartment name.)"""^^<http://www.w3.org/2001/XMLSchema#string> ;
        a :Information
    ] ;
    a :MethodRule .
    


http://www.w3schools.com/xquery/xquery_flwor_html.asp

Facts about IW Meeting 2013-04-25RDF feed
Date25 April 2013  +
Personal tools
Navigation