Projects tagged ‘semantic’ and ‘sparql’

This project is aimed to be a simple music explorer based on similarities found on DBpedia and other Linked Open Data clouds. What is Linked Music Explorer?Linked Music Explorer is a simple service ... [More] that allows you to discover interesting relationships between bands. Similar bands by genre similarity or other kind of affinities are provided. What's the difference with other music similarity services on the Web?Simple: the data. Linked Music Explorer is entirely based on DBpedia. Embracing the Linked Data philosophy, it's our aim to demonstrate the feasibility of such published linked content to build novel applications without owning large, unaffordable and closed datasets. The data you need are out there. Just use them. For a deeper insight, we suggest to read Combining Social Music and Semantic Web for Music-related Recommender Systems, an interesting paper on these topics. How does it fit with NoTube?NoTube is a research project aimed to develop an innovative recommendation engine for TV content. It's our belief that those linked-published data could play an important role in order to feed the users with personalized content. For this reason, Linked Music Explorer is a first prototype release of a front-end application that will be based on the technologies developed within the NoTube project. What's next?Since the further planned releases are coupled with the progress made in the NoTube project we expect to make several improvements to Linked Music Explorer: fully personalized links discovery, more enriched information and an improved AJAX-ish Web interfaces. For any further information please refer to the code page. .gadget-title { margin-bottom: 2px; } function resizeIframeHandler(opt_height) { var elem = document.getElementById(this.f); if (!elem) return; if (!opt_height) { elem.style.height = undefined; } else { opt_height = Math.max(10, opt_height); elem.style.height = opt_height + 'px'; } } gadgets.rpc.register("resize_iframe", resizeIframeHandler); gadgets.rpc.register('set_title', function(title) { var elem = document.getElementById(this.f + '_title'); if (elem) { elem.innerHTML = gadgets.util.escape(title); } }); [Less]

SimpleSPARQL allows queries to SPARQL endpoints in a very simple language similar to MQL. The query language is designed specifically for python and uses python dictionaries in the same way as MQL. ... [More] Example Code: >>> from SimpleSPARQL import SimpleSPARQL >>> sparql = SimpleSPARQL("http://dbpedia.org/sparql") >>> n = sparql.n >>> n.bind('rdf', 'http://www.w3.org/1999/02/22-rdf-syntax-ns#') >>> n.bind('rdfs', 'http://www.w3.org/2000/01/rdf-schema#') >>> n.bind('dbpedia2', 'http://dbpedia.org/property/') >>> # the area in Km^2 of things labeled England >>> print sparql.quickread({ >>> n.rdfs.label : u"England", >>> n.dbpedia2.areaKm : None >>> })[0] 130395 >>> # The Prime Minister of England's types >>> q = { >>> n.rdfs.label : u"England", >>> n.dbpedia2.primeMinister : { >>> n.rdf.type : None >>> } >>> } >>> for type in sparql.quickread(q) : >>> print type http://xmlns.com/foaf/0.1/Person http://dbpedia.org/class/yago/PrimeMinistersOfTheUnitedKingdom http://dbpedia.org/class/yago/ChancellorsOfTheExchequerOfTheUnitedKingdom http://dbpedia.org/class/yago/LeadersOfTheBritishLabourParty http://dbpedia.org/class/yago/AcademicsOfTheUniversityOfEdinburgh http://dbpedia.org/class/yago/RectorsOfTheUniversityOfEdinburgh http://dbpedia.org/class/yago/PeopleFromGlasgow http://dbpedia.org/class/yago/AcademicsOfTheOpenUniversity ... >>> for obj in sparql.read(q) : >>> print obj { rdflib.URIRef('http://dbpedia.org/property/primeMinister'):{ rdflib.URIRef('http://www.w3.org/1999/02/22-rdf-syntax-ns#type'): u'http://dbpedia.org/ontology/OfficeHolder#Class' }, rdflib.URIRef('http://www.w3.org/2000/01/rdf-schema#label'): u'England' } { rdflib.URIRef('http://dbpedia.org/property/primeMinister'):{ rdflib.URIRef('http://www.w3.org/1999/02/22-rdf-syntax-ns#type'): u'http://dbpedia.org/ontology/OfficeHolder#Class' }, rdflib.URIRef('http://www.w3.org/2000/01/rdf-schema#label'): u'England' } { rdflib.URIRef('http://dbpedia.org/property/primeMinister'):{ rdflib.URIRef('http://www.w3.org/1999/02/22-rdf-syntax-ns#type'): u'http://dbpedia.org/ontology/OfficeHolder#Class' }, rdflib.URIRef('http://www.w3.org/2000/01/rdf-schema#label'): u'England' } ... >>> print sparql.ask({ n.rdfs.label : u"England", n.dbpedia2.primeMinister : { n.rdfs.label : u"Tony Blair" } }) False >>> # and if you could do writes to dbpedia: >>> obj = { >>> n.rdfs.label : "Hello World", >>> n.sparql.create : n.sparql.unless_exists >>> } >>> sparql.write(obj) [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]

Simple Virtuoso PL Unit Testing Framework Codebase OrganizationThere are four files: vunitutil.sql = standalone library with utility procedures. You can use these on your projects ... [More] vunitutil.tests.sql = unit tests for the above file vunit.sql = the unit testing framework itself. requires vunitutil.sql vunit.tests.sql = unit tests for the unit testing framework itself InstallationThe order in which you run the files is important when installing. There are two options: Just utilities vunitutil.sql Utilities + Framework (probably what you want) vunitutil.sql, then vunit.sql You don't want to install the unit tests (.test.sql files) unless you're working on this codebase itself. Using ItUnit tests are procedures which name is postfixed with the string 'vunittest' The reason to choose such a complex postfix (vunittest) instead of a simpler one like "test" is to avoid accidentally running a procedure that is not meant for testing, since we rely on text search over procedure names to gather all tests Within these procedures you can call assertions ( vunit_assert_true, vunit_assert_false, vunit_assert_equals, etc ) Basic-- Create a Sample Procedure: create procedure hello( in name varchar := 'World' ) returns varchar { return 'Hello ' || name || '!'; };grant execute on hello to dba; -- Along with one Unit Test create procedure hello_vunittest(){ vunit_assert_equals( hello('John'), 'Hello John!' ); };grant execute on hello_vunittest to dba; -- And run all tests select vunit_run(); [Less]

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]

This project aims at an implementation of rank-aware SPARQL query engine, which takes RDF document and extended-SPARQL query expressions as the input, and returns a list of ranking results in terms of weights of concepts in the RDF document.

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]

Framework for qualifying knowledge acquisition and inquiry by/over/from the semantic web.

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