Changes between Version 55 and Version 56 of SemanticWebServices

Timestamp:

2009/03/20 12:09:57 (16 years ago)

Author:

rvos

Comment:

--

SemanticWebServices

@@ -185 +185 @@
  * TOGO services are nicer, but don't have a WSDL (because they are RESTful).  As such, there is no way for us to wrap them other than one-by-one. Again, unfortunately a non-starter for the scope of the hackathon.
  * We have asked Oswaldo to suggest which WABI services he thinks are most interesting/useful for his integration with the Spanish INB, and we will wrap these services during the hackathon as SADI and/or Moby services.
+=== SADI API modifications ===
+The [http://sadiframework.org SADI framework] is a fully standards compliant reference implementation of semantic web principles applied to health research.  The objective of SADI is to make it easy for data and analytical tool providers to quickly make their resources available on the Semantic Web with minimal disruption to their usual practices. The points below enumerate specific modifications the SADI developers identified during the hackathon to interoperate with a larger set of (legacy) service.
+ * Service provider will "decorate" input by adding a new predicate/object to the incoming data; this is no longer a client-side task
+ * Client '''''must''''' semantically-type their input data according to the OWL document describing the service provider's input
+   * this allows the service to find the input nodes based on their rdf:type rather than having to reason-over the incoming data.
+   * service provider will strip this rdf:type tag off of the data before sending it back to the client.
+ * Service providers '''''must''''' semantically-type their output data according to the OWL document describing their output such that the client can recognize the nodes that have been decorated by the service.  Clients may chose (probably will want to) strip the rdf:type tag off of the returning data.
 == Resources ==
  * [http://sadiframework.org SADI]