Changes between Version 64 and Version 65 of ImplementationBootcamp

Show
Ignore:
Timestamp:
2010/02/12 11:18:05 (13 years ago)
Author:
RutgerVos
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • ImplementationBootcamp

    v64 v65  
    5454 * URIs (URLs) for terms should be carefully constructed, predictable and stabilized, perhaps using PURLs. For example, several queries failed to produce expected results due to omission of `www` prefixes or `#` suffixes in URLs. 
    5555 * several tools (Homonto developed by [http://bgee.unil.ch/bgee/bgee?page=about BGee], [http://bmir.stanford.edu/file_asset/index.php/1463/BMIR-2009-1364.pdf LOOM]) and a lot of research ([http://ontologymatching.org/ Ontology Matching]) has already gone into the problem of ontology alignment. However, expert knowledge for manual alignment is often still necessary. 
    56  
    57 === In my generated RDF, what namespace URI do I use to prefix my terms? === 
    58  
    59 It is best to do this using a real URL such that the terms can actually be resolved (unlike XML), preferably to an OWL file, e.g. "xmlns:foo=http://example.org/terms.owl#" such that construct "foo:bar" can be resolved. 
    6056 
    6157===  What are the similarities and differences between the various shared names proposals?  === 
     
    222218There was a very brief discussion of this issue on Thursday, the answer was "be pragmatic".  Highly granular data (like absolute expression-level changes for microarrays) might not be appropriate for conversion into RDF because it explodes the size of the dataset in a circumstance where (a) the dataset is generally going to be used as a whole anyway, and (b) there are completely adequate parsers for existing file-formats, and (c) the benefit of being able to reason over an RDF representation of the data is limited, or absent. On the other hand, there is no reason (in Rutger Vos's opinion) why an atomic datum (such as a single site in a sequence) that is considered a resource under the used data model shouldn't return a brief description of itself upon resolving that resource, provided that the context within that resource has meaning can be located (e.g. by referring to the defining resource using rdfs:isDefinedBy). 
    223219 
     220=== In my generated RDF, what namespace URI do I use to prefix my terms? === 
     221 
     222It is best to do this using a real URL such that the terms can actually be resolved (unlike XML), preferably to an OWL file, e.g. "xmlns:foo=http://example.org/terms.owl#" such that construct "foo:bar" can be resolved. 
     223 
    224224=== Where do I validate my RDF/XML? === 
    225225