IW Meeting 2010-10-13

From Inference Web

Jump to: navigation, search


Meeting Info

IW Overall Objectives

     1) PML ontology: (OWL level only) potential non-monotonic  changes (Li) 
     2) PML practice  
         2.1) Use cases and examples (Tim) 
         2.2) RDF level issues (Cynthia) 
         2.3) PML Tools / API issues (Cynthia) 
         2.4) PML primer (Tim) 
     3) PML and OPM mapping (Paulo) 
     4) IW management (TBD)
        4.1) inference web infrastructure and research plan
        4.2) technologies for engagement 
     5) PML Graphical Notation


  • Deborah
  • Cynthia (call in)
  • Paulo (call in)
  • Li (regrets)
  • Geoff (regrets)
  • Jim M (call in)



combining proofs

Cynthia still working with Geoff. Will report next week.

TPTP proofs for Tim

Tim trying to visualize TPTP proofs. Cynthia gave two links via email

Why you do not use ProbeIt?

  • that will be part of my process.

Probeit is in the process of being ported to a javascript/java environment and this is the right time for us to discuss what are the new requirements for ProbeIt

TPTP format (maintained at Geoff's site) and PML format (cynthia's converter) IDV views TPPT proofs RPI has IW Browser for PML format. Paulo's ProbeIt!

Cynthia's issue

INCORPORATE INTO LIST On 10/13/2010 5:19 PM, csc@cs.rpi.edu wrote: While I am changing the range of hasInferenceEngine of InferenceStep,I think it would be right to change the range of isFromEngine of Query to Agent too. Let me know.

Thanks, csc

in 2.1 i think we also want to add property name updates to include hasAgent in addition to hasInferenceEngine and then in documentation, we suggest that no one use hasInferenceEngine in the future.



Paulo needs the URIs of the predicates to stay within the 2.0 namespace. Our 2.01 ontology will exist at a 2.01 URL and assert axioms in 2.0 namespace. This works if you only grab the 2.01 ontology and work with it. You "Fall into" 2.0 if you resolve any of the classes or properites that you found in the 2.01 ontology.

Jim's comment from email: there should be no explicit 2.0 namespace, but just have pml namespaces. Versioned URLs refer to the main namespace, which resolves to the most recent version. A tool that depends on a particular version uses the ontology at that versioned URL.

How does Jena use it?

Jim: Jena only imports the ontologies that are stated as imports, and only if loadImports() is called on the model.

Jim: Pellet does not resolve the ontologies directly.

Paulo's 2.1 priorities


  • PML-Sparql - add property chains to make it easy to query.

(Cynthia wants hasAuthor instead of hasAuthorList b/c List is difficult to get first/rest)

  • promoting source usage to same level as InferenceStep
  • change of property names

Source is a Role of the thing in a retreival context. Wants to incorporate Sink with Source into Information Container

But isn't Information our current Sink?

Paulo: Agency

  • OPM Agents can't reason
  • OPM Agents can't assert

Paulo is saying it is sunny in El Paso


  • information container
  • promoting soiurce usage
  • PML-S
  • stephan's predicate renaming proposal.

How to work on 2.1?

Need infrastructure.


CI Server?

  • security

Action items

1 - cynthia publish 2.01 that has ONLY one change over 2.0 which is the range of hasInferenceEngine is now Agent (instead of inference engine) DONE

2 - we expect that we will still be in the 2.0 namespace

  • Paulo to send Tim examples motivating the promotion of Source Usage "next to" an inference step.
  • Cynthia to incorporate hasAuthor to 2.1 list
  • Cynthia to incorproate change the range of isFromEngine of Query to Agent request to 2.1 list
  • Cynthia to review PML-S ontology to see how it addresses the hasAuthor
  • Cynthia to add isRoot to 2.1 list - describe need/want
  • Paulo to provide pointer to PML-S proposal
  • Paulo to provide InformationContainer proposal
  • Tim to provide SourceUsage promoted proposal (also needs example from Paulo)
  • Tim to find Stephan's renaming proposal
Personal tools