Projects tagged ‘owl’ and ‘sparql’

LinqToRdf provides a full-featured LINQ query provider for .NET using both local triple stores with Graph Matching and SPARQL queries on remote stores. It also provides graphical design tools for ... [More] visual studio 2008 that provide a UML style design surface for the production of both ontologies and .NET domain models. [Less]

The knowledge base is written using the SKOS ontology.

Semantic Quiz module

A Semantic Web Application for Electronic Medical Records Handling.

Django-RDF is an RDF engine implemented in a generic, reusable Django app, providing complete RDF support to Django projects without requiring any modifications to existing framework or app source ... [More] code, or incurring any performance penalty on existing control flow paths. The philosophy is simple: Do your web development using Django just like you're used to, then turn the knob and - with no additional effort - expose your project on the semantic web. The project home is at Google Code and there is also a Google Group to help coordinate. http://code.google.com/p/django-rdf http://groups.google.com/group/django-rdf Features Django-RDF can expose models from any other app as RDF data. This makes it easy to write new views that return RDF/XML data, and/or query existing models in terms of RDFS or OWL classes and properties using (a variant of) the SPARQL query language. SPARQL in, RDF/XML out - two basic semantic web necessities. Django-RDF also implements an RDF store using its internal models such as Concept, Predicate, Resource, Statement, Literal, Ontology, Namespace, etc. The SPARQL query engine returns query sets that can freely mix data in the RDF store with data from existing Django models. Internals During configuration, the syncvb command inspects the database schema created by running syncdb and generates OWL ontologies for other apps in INSTALLED_APPS. The ontologies are serialized to RDF/XML files in the django-rdf/ontology/ directory, and subsequenty deserialized to create a combined vocabulary in the form of RDF model instances. The RDFS/OWL classes and properties in the vocabulary are associated with elements of the database schema that are then used by the SPARQL compiler to generate SQL code. A SPARQLQuerySet implementation wraps the compiler and provides access to model instances or values using the familiar Django query set interface - filter, count, iteration with slices, etc. A set of APIs gives convenient access to resources. Here is a toy example of a view that uses django.contrib.auth, resets the first name of a user and then renders everything known about that user in the RDF/XML format: def reset_first_name(request, username, first_name): AUTH = Namespace.objects.get(code='auth') # Returns a django.contrib.auth.models.User object: user = AUTH['user#%s' % username] # Resets the first name of the user: Statement.objects.create(user, AUTH['User__first_name'], first_name) # Renders everything known about the user in RDF/XML format: return render_as_rdf({resources: (user,)})A small set of shortcuts, templates and template tags simplifies RDF/XML output. An RDF/XML serializer/deserializer is also included. Plan Django-RDF was initially implemented in March 2008. Current status as of April 25 2008 is as follows: RDF store, basic SPARQL compiler and query set, render_as_rdf shortcut, RDF/XML deserializer, syncvb command are functional. URI synthesis for instances of existing models needs a rewrite. SPARQL implementation is missing features. SPARQL syntax is not compatible with the W3C Recommendation. No access control yet. No internationalization yet. No samples yet. ... and there are many other rough edges here and there. The plan is to have a fairly polished "ready-for-release" version sometime in summer 2008. A fairly extensive set of unit tests already exists but there is still a lot of churn in various parts of the API, and the immediate goal is to extend the test coverage until the API reaches a more stable state. Feedback from the first intrepid users will be greatly appreciated! (And much of it will likely sound something like, hey, that's not working quite as advertised! :) Enjoy, Stefán [Less]

SADI, and it's first implementation in CardioSHARE, are a novel Web Services framework that dynamically generates RDF graphs by accessing Web Services. Web Service discovery is achieved by ... [More] registering the type of relationship (i.e. the predicate) that the Web Service creates between its input data and its output data. See an early prototype application demo. Note that THERE IS NO DATABASE/TRIPLESTORE under these demos! All data is being discovered dynamically by the SADI system through "semantic interpretation" of the query, followed by discovery of Semantic Web Services capable of generating the data required to resolve the query, automated execution of the discovered Services, retrieval of the resulting triples, and finally resolution of the query using a normal SPARQL query engine (at the moment we are using Pellet). Founding Partner [Less]

Genius + Eye Candy = Semantic Flash Boost your Flash/Flex/AIR apps with free data from the Semantic Web! AboutThis project is in incubation state ( no public releases yet ). Please join the ... [More] discussion group to participate: SemanticFlash@Google Groups The basic I/O framework ( RDF-XML ) is working and the original version of this project ( owned by univrz consulting ) is being used in commercial applications. However, for time constraints, we are not releasing anything to the public yet. MissionOur main objective is to bring the power of the Semantic Web to the Flex guys. Not Flex to the Semantic Web guys ( the former implies the latter, anyway ). This means that we will avoid philosophic and overly technical discussions when possible, stick to pragmatism and aim to simplify the UI developer's workflow by providing: High level tools that incorporate the latest standards, conventions and best practices Articles and tutorials on how to use these tools to make your applications look better, work better and provide more value to your users A responsive community that contains a high concentration of talent from both worlds You won't have to understand how the Semantic Web works, just hop in and use what's good for you. This is a grassroots approach to creating Next Generation User Interface culture and increasing the demand for RDF data ( which will most probably impact its availability in a positive way ). We will feed the virtuous cycle from the other end. From the UI. What's in this for me?Well, that depends on who you are. If you are a Flash/Flex developer...then this framework will allow you to Spice up your apps with free, high quality data from the Semantic Web ( yes, it's already here ) Slurp in artist and track data for your new Mp3 player ( from musicbrainz ) Slurp in geographical data for your new map mashup Slurp in ( whatever ) from ( take a look at some of the currently available sources ) Create highly flexible UIs for all sorts heterogeneous data ( your company's assets, for example ) Learn to speak and think in terms of the future Web Discover an excellent alternative to moving your data around as XML docs or RPC calls If you are a Semantic Web developer / researcher...then this framework will allow you to start experimenting with a highly flexible and practical development environment ( Adobe Flex ), with superb graphical and multimedia capabilities. You can then set off to take the Semantic Web browser to a whole new level, explore novel filtering and navigation paradigms for the Giant Global Graph, create dazzling visualizations and mashups for your linked data and ( hopefully ) give us a hand. The Semantic Web community has been working hard on delivering usable Browsers to navigate the web of data. We encourage you to stand on the shoulders on these giants and aim to improve their usability and aesthetics. The following list contains remarkable examples of Semantic Web browsers: Zitgist Data Viewer, Disco, Tabulator, OpenLink's Linked Data Viewer, Marbles, etc ( you can find an extensive list here ). However, we also encourage you to depart from this first generation and explore radical and novel approaches to delivering data ( click here to get your creative juices flowing ). Note: Flash and Flex are now mostly opensource technologies. In fact, a branch of the runtime has been handed to the Mozilla foundation. So... no lock-in FUD, please. And if you are a futurist, then you might be relieved to meet the OpenScreen project Sponsors( want to see your name here? we do!... talk to Aldo ) StrategySimple things should be simple, complex things should be possible What's Simple?Loading, parsing and consuming an RDF document Using RDF data at a script level ( a la E4X ) Using RDF data in the UI This includes binding / collections API integration Aggregating a few RDF documents ( how much is "a few?" ) These are primary goals. We will emphasize in creating services to achieve these tasks using a simple workflow and enforcing best practices whenever possible ( shielding you from the complexity of choice ). What's Complex?Inference & Smushing Rules Provenance Management Consuming non-static sources ( SPARQL endpoints ) Ontological Constraints Read-write RDF SPARQL Update Open, edit, save RDF docs etc... These are secondary goals. The framework should allow you to achieve these tasks by providing the basic building blocks or clear extension points. RoadmapWork on CoreDesignIssues Define Model classes ( RDF Abstract Concepts ) RDF I/O Framework ( Parsers ) RDFXMLParser N3 Parser ( or just TTL? ) ... In memory storage Simple smushing Simple Forward Chaining inference ( for foaf sha1's and other necessary stuff ) AIR ( sqlite triple storage ) ... [Less]

sμBlog is my effort to combine ideas about microblogging, messaging and the sematic web into a practical tool ready for everyday work. sμBlog listens for messages across standard internet ... [More] protocols (e.g. XMPP, IMAP) and does useful things depending on the meaning of the messages it receives. The basic idea of sμblog is to have a flexible and highly configurable system that will read short human-generated messages from somewhere on the Internet – normally a XMPP (aka Jabber) IM account convert each message into a RDF graph that represents the semantic structure of the message expose the resulting RDF to elements of the semantic web technology stack, which may include RDF stores, SPARQL query interfaces, OWL reasoners and so on, and optionally pass the results on to some other Internet service or application. You can find out more at http://tizard.net/sublog . [Less]

Serveur web sémantique pour Last.fm Nom Contact Maximilien Perrin Camille Roux Website ObjectifL’objectif de notre projet est d’exploiter des données extraites de Last.FM grâce à ... [More] son API pour fournir une navigation directe et intuitive parmi les artistes et styles de musiques. L’utilisateur peut ainsi découvrir de nouveaux artistes et des morceaux de musique originaux suivant ses goûts musicaux, et obtenir des informations sur ce qu’il souhaite. Notre projet comporte deux parties fondamentales. La première partie consiste à développer un utilitaire destiné à récupérer un ensemble d’informations à partir des services web d’AudioScrobbler, afin de constituer une base sémantique représentative des musiques existantes. L’API mise à disposition ne permet pas de récupérer les données de façon globale, mais seulement de façon ponctuelle : on peut par exemple récupérer à partir d’un artiste précis ses artistes proches, ses tags, ses albums... mais pas l’ensemble des artistes existants. Nous avons donc décidé d’utiliser un parcours en largeur sur le graphe des artistes proches afin de constituer une liste d’artistes, puis pour chaque récupérer ses tags et ses albums. Cette méthode permet de constituer rapidement une base de connaissances à partir d’un nom d’artiste. La seconde partie de notre projet consiste en un site web permettant l’accès et la navigation parmi les données récupérées. Ce site, basé sur le moteur sémantique Sewese, devait respecter un certain nombre de contraintes que nous nous étions fixées. Tout d'abord, nous souhaitions que le site soit ergonomique afin qu'il puisse être ludique pour l'utilisateur. Nous tenions également à respecter certaines normes d'accessibilité afin que le site puisse être utilisé par des déficients visuels ainsi que pour favoriser le référencement par les moteurs de recherche. Scénarios d’utilisationComme nous l'avons dit précédemment, nous avons décidé de faire en sorte que le site puisse offrir la possibilité à l'utilisateur de réaliser un voyage dans la musique. Nous voulions qu'il puisse facilement naviguer entre les styles de musique et les artistes. Pour cela, nous avons décidé d'afficher un nuage de tags en première page représentant les tags les plus utilisés dans notre base. Un clic sur un tag permet d'afficher la liste des artistes qui correspondent le plus au tag en question, avec la photo du groupe si elle est disponible. Enfin, un clic sur un artiste affiche la page de l'artiste lui- même qui est divisée en trois parties : la liste de ses albums, un nuage des tags correspondant à l'artiste et aussi, les artistes qui ont un style proche de celui de l'artiste. Il est à noter qu'il est possible de revenir sur le nuage de tags du départ à tout moment en cliquant sur le logo du site. Enfin, nous avons ajouté un champ de recherche dans la bannière qui permet à l'utilisateur de faire une recherche parmi les tags et les artistes, ce qui lui permet d'accéder rapidement à l'information s'il le souhaite. [Less]

Цель проекта: Cоздать удобную, управляемую, высокопроизводительную, масштабируемую среду для интеграции ... [More] разнородных приложений, модулей, компонентов, с использованием онтологий. сайт проекта: http://esb.magnetosoft.ru Этапы работы: В качестве полигона для обкатки идей и реализации этого проекта используется проект magnetico http://magnetico.googlecode.com . Вернее одна из продуктивных версий, эксплуатирующаяся на крупном предприятии и обслуживающая более 1000 пользователей за рабочий день. Такой подход, позволяет нам сохранить направленность проекта ontobus на реальные задачи и обеспечивает необходимой для тестирования нагрузкой. Внутрення архтектура и реализация проекта magnetico постепенно, шаг за шагом перерабатывается и заменяется на технологии шины ontobus. При этом сохраняется полная работоспособность проекта magntico. [Less]