Re: summarizing consensus on charter

Hi Jim,
>> As a general request, please consider parts of the next version of Basic Formal Ontology...
The Provenir ontology [1] uses the BFO-based concepts "continuant" and "occurrent" to define its three primary classes and also adapts the 10 properties of the Relation ontology, including "has participant" etc.

Best,
Satya

[1] http://wiki.knoesis.org/index.php/Provenir_Ontology  

----- Original Message -----
From: Jim McCusker <james.mccusker@yale.edu>
Date: Friday, November 19, 2010 2:04 pm
Subject: Re: summarizing consensus on charter
To: "public-xg-prov@w3.org" <public-xg-prov@w3.org>

> On Fri, Nov 19, 2010 at 12:47 PM, Paul Groth <pgroth@gmail.com> wrote:
> Actions:
> - All: send a list of concepts that the charter will suggest to the XG to address. Please send this to the mailing list
> Please identify: which ontology it comes from, whether it is mandatory or optional, provide an example, and a definition. This should be done As soon as possible and before Wednesday of next week.
> 
> As a general request, please consider parts of the next version of Basic Formal Ontology, which has significant overlap with the concepts that we are working with here (http://bfo.googlecode.com/svn/trunk/src/ontology/bfo2_all.owl) (PREFIX obo: http://purl.obolibrary.org/obo/). It's still a draft, so we can probably even influence it sufficiently for our purposes. All of these classes and some properties in BFO2 already have definitions and examples. Specifically:
- > "process" (obo:BFO_0000007)
- > "role" (obo:BFO_0000023)
- > "continuant" (obo:BFO_0000002) and its subclasses
- > "temporal region" (obo:BFO_0000008)
- > "function" (obo:BFO_0000034) for "recipes"

There are also some relations of interest there:
- > "begins to exist during" (obo:BFO_0000068)
- > "ceases to exist during" (obo:BFO_0000069)
- > "participates in" (obo:BFO_0000056) / "has participant" (obo:BFO_0000057)
- > "is granular part of process" (obo:BFO_0000074) for relationships processes to each other.


> Also, I would like to suggest that (role subClassOf skos:Concept). Partly because roles are concepts, but also because the SKOS broader/narrower subsumption hierarchy can be used to provide semantics to roles. 
> 

> Thanks,
> Jim
> --
> Jim McCusker
> Programmer Analyst
> Krauthammer Lab, Pathology Informatics
> Yale School of Medicine
> james.mccusker@yale.edu | (203) 785-6330
> http://krauthammerlab.med.yale.edu
> 
> PhD Student
> Tetherless World Constellation
> Rensselaer Polytechnic Institute
> mccusj@cs.rpi.edu
> http://tw.rpi.edu