obophenotype / developmental-stage-ontologies

Source files for various species-specific stage ontologies
10 stars 5 forks source link

Formalise age from birth using a data property #19

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
We are dealing with bulk image datasets for which we have age postpartum.  We 
can do a manual mapping of these numbers to MmusDv terms, but it would be 
simpler if we could make use of formal assertions of the age ranges that define 
these classes via an OWL dataProperty.  

The only major issue I can see with this is choosing a unit (I don't think 
there is an appropriate dataType that will do the work for us).  We could 
probably get away with choosing days as the default unit and then doing 
conversions to something more sensible outside OWL for mapping/display purposes.

Original issue reported on code.google.com by dosu...@gmail.com on 23 Apr 2014 at 11:42

GoogleCodeExporter commented 9 years ago

Original comment by dosu...@gmail.com on 23 Apr 2014 at 11:43

GoogleCodeExporter commented 9 years ago
Maybe the property values "start_mbp", "end_mbp", etc, are what you need? They 
are already present in the ontology.

Original comment by frederic...@gmail.com on 24 Apr 2014 at 11:51

GoogleCodeExporter commented 9 years ago
Hadn't noticed these.  Looking at the latest OWL version 
(http://purl.obolibrary.org/obo/mmusdv/releases/2014-04-10/mmusdv.owl), they 
appear to be annotation properties.  To be used in reasoning, they would need 
to be data properties.  For this to work, I think we'd need a single data 
property for recording the age range for each stage - rather than separate ones 
for start and end stage.

Original comment by dosu...@gmail.com on 24 Apr 2014 at 1:59

GoogleCodeExporter commented 9 years ago
Then I let this discussion to Chris :p

Original comment by frederic...@gmail.com on 24 Apr 2014 at 2:09

ANiknejad commented 8 years ago

maybe to close? sounds obsolete? @cmungall

dosumis commented 8 years ago

Not obsolete in that these are still not data properties. If they were, I could use them for temporal reasoning-type queries.

dosumis commented 8 years ago

No longer urgent for me though.

ANiknejad commented 8 years ago

@dosumis sorry, I thought it is 'data properties' when I see stuff like

dosumis commented 8 years ago

property_value: start_ypb "12.0" xsd:float

Looks like OBO.

So I guess the master is still OBO? In that case, we'd need a macro-expansion specified to make the data properties in OWL. I can specify that on the annotation property. Is this AP specific to mmusdv or is it inherited from elsewhere?

ANiknejad commented 8 years ago

I let @cmungall or @fbastian answer

cmungall commented 8 years ago

The APs are currently specific to each ontology as some of the species do it differently, but we should probably unify and get these into RO. We'd probably have to start making some semantic commitments which we've deferred on so far