Projects tagged ‘sparql’

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]

The knowledge base is written using the SKOS ontology.

The Perl RDF project aims to be a pure-perl RDF framework implementation with an emphasis on extensibility, API stability, and the presence of a test suite. Currently, the project includes: ... [More] RDF::Query, a SPARQL (and RDQL) query engine supporting RDF::Redland, RDF::Core, and RDF::Trine. RDF::Endpoint - A SPARQL endpoint based on RDF::Query. RDF::Trine::Parser - A native parser for Turtle (with RDF/XML support expected soon). RDF::Trine::Store::DBI, an RDF Store for MySQL and SQLite, based on the Redland schema. RDF::Trine::Iterator, iterator classes for variable bindings and RDF statements. RDF::Trine::Namespace - A convenience class for easily constructing RDF node objects from URI namespaces. Components that are expected to be written for this project, but have not yet been started, are: A rules-based reasoning system. [Less]

Semantic Quiz module

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]

Cliente realizado en Java / Swing que permite cargar un archivo RDF en memoria y ejecutar consultas SPARQL sobre el mismo.

Twinkle is a simple GUI interface that wraps the ARQ SPARQL query engine. The tool should be useful both for people wanting to learn the SPARQL query language, as well as those doing Semantic Web development.

SPAR*QL Ed*itor. Spared is a Javascript based SPARQL query tool. It provides a quick off the shelf implementation of a SPARQL query tool that developers can use to add a UI to a SPARQL endpoint.

STATUS: Not ready for use, still in alpha This project uses the following sub projects Bainbridge: ARQ Wrappers to help process SPARQL Queries http://code.google.com/p/bainbridge/ Bette ... [More] Graham, an RDF based project configuration API http://code.google.com/p/bettegraham/ Casimir Pulaski, Convience wrappers for the jena api http://code.google.com/p/casimirpulaski/ This projct is named after: Molly Pitcher was a nickname given to a woman who may have fought in the American Revolutionary War. Historians differ on the real identity of Molly Pitcher, or even if she existed. Since the various Molly Pitcher tales grew in the telling, historians now often regard Molly Pitcher as folklore, rather than history. However, Molly Pitcher may be a composite image inspired by the actions of a number of real women. The name itself may have originated as a nickname given to women who carried water to men on the battlefield during the war. This water was not for drinking, as is popularly believed, but for swabbing the cannons. [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]