BIOS – – Qui ? Mark D Wilkinson, Benjamin Vandervalk, Luke McCarthy Wilkinson noted that when he began developing BioMoby, many semantic web tools, such as the Resource Description Framework data model and OWL ontology language, had not yet been developed," so BioMoby invented its own, inferior, equivalents." Middle-ware open-source API Perl (CPAN)
BIOS – – Ajouter du sens
BIOS – – SADI définit des bonnes pratiques pour l'utilisation de standards éprouvés du web sémantique Les points clés: Les services SADI utilise le protocole HTT¨P pour l'échange de données (POST/GET) Les services SADI Services manipulent des données au format RDF Utilisation de d'outils existant pour leur analyse, le requêtage (OWL-reasoners, SPARQL) Les interfaces des services sont décrites avec des termes OWL-DL Les données en entrée sont « décorées » par le fournisseur de service en fonction de l'analyse produite La découverte de services peut se faire sur cette décoration et non plus uniquement sur le type d'analyse Les web services SADI sont atomiques et « stateless » Conventions
BIOS – – CardioSHARE Décoration de web services BioMOBY existants Formulaire requêtage SPARQL Ce que cela laisse entrevoir Construction d'outil intégratifs plus puissants (moins de bruit de fond) Base de connaissances réparties et dynamiques Décorer nos RDF de WS BioMOBY Développer PlayMOBY/Mobyle pour devenir « SADI compliant »
BIOS – – Where/When Should SADI be used? Analytical Tools As with any Web Services framework, SADI can expose any source of dynamically-generated information. In most cases this means Web-based analytical algorithms, but any source of data would be applicable - including robots, or even distributed human curators. Because SADI Services are stateless and atomic, Web Services that expose a set of stateful object methods cannot easily be exposed as SADI Services (though in many cases these services could be re-written to follow SADI conventions, and take advantage of the added semantic behaviours). Our observations suggest, however, that almost all services currently available in the bioinformatics space have a SADI-like behaviour that easily maps onto the SADI conventions. Databases SADI can be used to expose databases (both traditional relational databases as well as the newer triple-stores) as discoverable Semantic Web Services. When viewed this way, SADI is a source of individual "cells" (in a traditional database) or of individual triples (in a triplestore). This may sound odd - why would you want to provide access on a cell-by-cell or triple-by-triple basis when you could more efficiently simply expose the query interface (SQL or SPARQL) on the Web? The short answer is that, historically, few data providers have ever exposed their database for external queries - they almost always utilize some form of limited query interface. The reason for this is obvious - the service provider is protected from potentially crippling erroneous or malicious queries. Though current trends have led to data providers exposing their triple-stores on the Web as SPARQL endpoints, we believe that the same barriers will eventually apply, and that open query interfaces will not be widely available. Using SADI Services, you have the ability to: distribute incoming queries over your compute resources (e.g. your farm) prevent malicious queries, since queries for individual triples cannot be nonsensical implement fine-grained security policies where certain parts of your database (triple/cells) are only available to certain requesters. We are in the process of creating a simple tool that will instantly transform your existing triple-store as a set of SADI services, and will then atttempt to create a similar wrapper for traditional relational databases.