Changes between Version 10 and Version 11 of SadiDayOne

Timestamp:

2010/02/09 21:11:56 (14 years ago)

Author:

markw

Comment:

--

SadiDayOne

@@ -31 +31 @@
 </a:outputParameter>
 }}}
+
+Let's have a look at the OWL ontology that defines our output class.  I have "pruned" the service_objects.owl ontology to show only the relevant parts for this discussion... :
+
 {{{
 
@@ -39 +42 @@
  xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" 
  xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#" 
- xmlns:misc="http://sadiframework.org/ontologies/miscellaneousObjects.owl#" 
  xmlns="http://sadiframework.org/ontologies/service_objects.owl#">
 
@@ -75 +77 @@
  3. our output class includes a restriction indicating that the service returns KEGG_Records related to the input by the 'isParalogOf' predicate (i.e.: KEGG_Records that are paralogs of the input KEGG_Record).  The owl:valuesFrom property on the restriction allows us to do reasoning about how to chain services together.  It is important that we put this restriction here instead of in the owl definition of the predicate itself, since it allows us to constrain OUR use of the predicate, without constraining its range for anyone else!
 
+ 4.  the "isParalogOf" property is symmetric, meaning that of X is a paralog of Y, then Y is also a paralog of X.  Note also that, in this case, I am defining the isParalogOf property in my service ontology; however '''THIS IS NOT ALWAYS NECESSARY''' - if you produce data that represents a relationship that has been adequately defined by someone else, then you are free to use that third-party's predicate and you don't need to define it yourself!  Re-use re-use re-use!!  That's what the Semantic Web is all about!
+
+
 The SADI Taverna plugin has been updated to use the information in these restrictions for service discovery.