Changes between Version 19 and Version 20 of SemanticWebServices

Show
Ignore:
Timestamp:
2009/03/20 10:42:15 (15 years ago)
Author:
rvos
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • SemanticWebServices

    v19 v20  
    3030=== Why semantic web services === 
    3131The 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. By adopting common standards to define syntax, semantics and interface, different service providers will be able to promote interoperability. Hence, this subgroup consists of people discussing the application of such technologies as WSDL, SAWSDL, OWL, RDF/XML (and other XML tools, i.e. XML schema, transforms). 
    32 === Technically === 
    33 === Philosophically === 
    34 A formal way of sharing your knowledge with other people. 
     32In addition to these technical arguments, there are also good philosophical arguments for formalizing our conception of the world. For example, as a researcher, this provides a formal way of sharing your knowledge with other people, thereby promoting reproducibility. 
    3533=== State of the practice === 
    3634==== RDF ====