Changes between Version 56 and Version 57 of SemanticWebServices

Show
Ignore:
Timestamp:
2009/03/20 12:10:34 (16 years ago)
Author:
rvos
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • SemanticWebServices

    v56 v57  
    2727 *  
    2828 
    29  = DECISIONS MADE =  
    30  == SADI API Decisions == 
    31  
    32  * Service provider will "decorate" input by adding a new predicate/object to the incoming data; this is no longer a client-side task 
    33  * Client '''''must''''' semantically-type their input data according to the OWL document describing the service provider's input 
    34    * this allows the service to find the input nodes based on their rdf:type rather than having to reason-over the incoming data. 
    35    * service provider will strip this rdf:type tag off of the data before sending it back to the client. 
    36  * 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. 
    37  
    38  = Semantic web services = 
     29= Semantic web services = 
    3930The holy grail of web service interoperability is hampered along three axes: syntax, semantics and interface. In terms of core data syntax, bioinformatics tools consume and produce data in many different formats, some of which are loosely defined syntactically (e.g. legacy flat file formats). In addition, the semantics of what we are trying to do with data, and what we mean by encoding data in a certain way, are often loosely defined. Many file formats are abused and overloaded to add semantics to fields that weren't intended for that (e.g. in comments, definition lines, key/value fields). Lastly, there is a proliferation of interfaces, each of which probably make sense on their own (e.g. RESTful APIs) but they all aren't interoperable in a way that a machine can make sense of by itself.  The semantic web is technically comprised of a stack of common standards and technologies that can be applied to these three axes of syntax, semantics and interface. By adopting these common standards different service providers will be able to promote interoperability.  
    4031== Why the semantic web? ==