RDF.rb: Linked Data for Ruby
This is a pure-Ruby library for working with Resource Description Framework (RDF) data.
- http://ruby-rdf.github.com/rdf
- http://blog.datagraph.org/2010/12/rdf-for-ruby
- http://blog.datagraph.org/2010/03/rdf-for-ruby
- http://blog.datagraph.org/2010/04/parsing-rdf-with-ruby
- http://blog.datagraph.org/2010/04/rdf-repository-howto
Features
- 100% pure Ruby with minimal dependencies and no bloat.
- Fully compatible with RDF 1.1 specifications.
- 100% free and unencumbered public domain software.
- Provides a clean, well-designed RDF object model and related APIs.
- Supports parsing and serializing N-Triples and N-Quads out of the box, with more serialization format support available through add-on extensions.
- Includes in-memory graph and repository implementations, with more storage adapter support available through add-on extensions.
- Implements basic graph pattern (BGP) query evaluation.
- Plays nice with others: entirely contained in the
RDF
module, and does not modify any of Ruby's core classes or standard library. - Based entirely on Ruby's autoloading, meaning that you can generally make use of any one part of the library without needing to load up the rest.
- Compatible with Ruby Ruby 1.9.2, Ruby 2.0, Rubinius and JRuby 1.7+.
- Compatible with older Ruby versions with the help of the Backports gem.
- Performs auto-detection of input to select appropriate Reader class if one cannot be determined from file characteristics.
HTTP requests
RDF.rb uses Net::HTTP
for retrieving HTTP and HTTPS resources. If the
RestClient gem is included, that will be used instead to retrieve remote
resources. Clients may also consider using RestClient Components to enable
client-side caching of HTTP results using Rack::Cache or other Rack
middleware.
Differences between RDF 1.0 and RDF 1.1
This version of RDF.rb is fully compatible with RDF 1.1, but it creates some marginal incompatibilities with RDF 1.0, as implemented in versions prior to the 1.1 release of RDF.rb:
- Introduces {RDF::IRI}, as a synonym for {RDF::URI} either {RDF::IRI} or {RDF::URI} can be used interchangeably. Versions of RDF.rb prior to the 1.1 release were already compatible with IRIs. Internationalized Resource Identifiers (see [RFC3987][]) are a super-set of URIs (see [RFC3986][]) which allow for characters other than standard US-ASCII.
- {RDF::URI} no longer uses the
Addressable
gem. As URIs typically don't need to be parsed, this provides a substantial performance improvement when enumerating or querying graphs and repositories. - {RDF::List} no longer emits a
rdf:List
type. However, it will now recognize any subjects that are {RDF::Node} instances as being list elements, as long as they have bothrdf:first
andrdf:rest
predicates. - {RDF::Graph} adding a
context
to a graph may only be done when the underlying storage model supports contexts (the default {RDF::Repository} does). The notion ofcontext
in RDF.rb is treated equivalently to Named Graphs within an RDF Dataset, and graphs on their own are not named. - {RDF::Graph}, {RDF::Statement} and {RDF::List} now include {RDF::Value}, and not {RDF::Resource}. Made it clear that using {RDF::Graph} does not mean that it may be used within an {RDF::Statement}, for this see {RDF::Term}.
- {RDF::Statement} now is stricter about checking that all elements are valid when validating.
- {RDF::NTriples::Writer} and {RDF::NQuads::Writer} now default to validate output, only allowing valid statements to be emitted. This may disabled by setting the
:validate
option tofalse
. - {RDF::Dataset} is introduced as a class alias of {RDF::Repository}. This allows closer alignment to the RDF concept of Dataset.
- The
context
(orname
) of a named graph within a Dataset or Repository may be either an {RDF::IRI} or {RDF::Node}. Implementations of repositories may restrict this to being only {RDF::IRI}. - There are substantial and somewhat incompatible changes to {RDF::Literal}. In RDF 1.1, all literals are typed, including plain literals and language tagged literals. Internally, plain literals are given the
xsd:string
datatype and language tagged literals are given therdf:langString
datatype. Creating a plain literal, without a datatype or language, will automatically provide thexsd:string
datatype; similar for language tagged literals. Note that most serialization formats will remove this datatype. Code which depends on a literal having thexsd:string
datatype being different from a plain literal (formally, without a datatype) may break. However note that the#has\_datatype?
will continue to returnfalse
for plain or language-tagged literals. - {RDF::Query#execute} now accepts a block and returns {RDF::Query::Solutions}. This allows
enumerable.query(query)
to behave likequery.execute(enumerable)
and either return an enumerable or yield each solution. - {RDF::Queryable#query} now returns {RDF::Query::Solutions} instead of an Enumerator if it's argument is an {RDF::Query}.
- {RDF::Util::File.open_file} now performs redirects and manages
base_uri
based on W3C recommendations:base_uri
is set to the original URI if a status 303 is provided, otherwise any other redirect will setbase_uri
to the redirected location.base_uri
is set to the content of theLocation
header if status is success.
- Additionally, {RDF::Util::File.open_file} sets the result encoding from
charset
if provided, defaulting toUTF-8
. Other access methods includelast_modified
andcontent_type
, - {RDF::StrictVocabulary} added with an easy way to keep vocabulary definitions up to date based on their OWL or RDFS definitions. Most vocabularies are now StrictVocabularies meaning that an attempt to resolve a particular term in that vocabulary will error if the term is not defined in the vocabulary.
- New vocabulary definitions have been added for ICal, Media Annotations (MA), Facebook OpenGraph (OG), PROV, SKOS-XL (SKOSXL), Data Vocabulary (V), VCard, VOID, Powder-S (WDRS), and XHV.
Notably, {RDF::Queryable#query} and {RDF::Query#execute} are now completely symmetric; this allows an implementation of {RDF::Queryable} to optimize queries using implementation-specific logic, allowing for substantial performance improvements when executing BGP queries.
Tutorials
- Getting data from the Semantic Web using Ruby and RDF.rb
- Using RDF.rb and Spira to process RDF data from the British Ordnance Survey
- Getting started with RDF and SPARQL using 4store and RDF.rb
Command Line
When installed, RDF.rb includes a rdf
shell script which acts as a wrapper to perform a number of different
operations on RDF files using available readers and writers.
serialize
: Parse an RDF input and re-serializing to N-Triples or another available format using--output-format
option.count
: Parse and RDF input and count the number of statements.subjects
: Returns unique subjects from parsed input.objects
: Returns unique objects from parsed input.predicates
: Returns unique objects from parsed input.
Examples
require 'rdf'
include RDF
N-Triples format
Writing RDF data using therequire 'rdf/ntriples'
graph = RDF::Graph.new << [:hello, RDF::DC.title, "Hello, world!"]
graph.dump(:ntriples)
or
RDF::Writer.open("hello.nt") { |writer| writer << graph }
N-Triples format
Reading RDF data in therequire 'rdf/ntriples'
graph = RDF::Graph.load("http://ruby-rdf.github.com/rdf/etc/doap.nt")
or
RDF::Reader.open("http://ruby-rdf.github.com/rdf/etc/doap.nt") do |reader|
reader.each_statement do |statement|
puts statement.inspect
end
end
Reading RDF data in other formats
{RDF::Reader.open} and {RDF::Repository.load} use a number of mechanisms to determine the appropriate reader
to use when loading a file. The specific format to use can be forced using, e.g. :format => :ntriples
option where the specific format symbol is determined by the available readers. Both also use
MimeType or file extension, where available.
require 'rdf/nquads'
graph = RDF::Graph.load("http://ruby-rdf.github.com/rdf/etc/doap.nq", :format => :nquads)
A specific sub-type of Reader can also be invoked directly:
require 'rdf/nquads'
RDF::NQuads::Reader.open("http://ruby-rdf.github.com/rdf/etc/doap.nq") do |reader|
reader.each_statement do |statement|
puts statement.inspect
end
end
Reader/Writer implementations may override {RDF::Format.detect}, which takes a small sample if input
and return a boolean indicating if it matches that specific format. In the case that a format cannot
be detected from filename or other options, or that more than one format is identified,
{RDF::Format.for} will query each loaded format by invoking it's detect
method, and the first successful
match will be used to read the input.
Writing RDF data using other formats
{RDF::Writer.open}, {RDF::Enumerable#dump}, {RDF::Writer.dump} take similar options to {RDF::Reader.open} to determine the appropriate writer to use.
require 'linkeddata'
RDF::Writer.open("hello.nq", :format => :nquads) do |writer|
writer << RDF::Repository.new do |repo|
repo << RDF::Statement.new(:hello, RDF::DC.title, "Hello, world!", :context => RDF::URI("context"))
end
end
A specific sub-type of Writer can also be invoked directly:
require 'rdf/nquads'
repo = RDF::Repository.new << RDF::Statement.new(:hello, RDF::DC.title, "Hello, world!", :context => RDF::URI("context"))
File.open("hello.nq", "w") {|f| f << repo.dump(:nquads)}
Reader/Writer convenience methods
{RDF::Enumerable} implements to_{format}
for each available instance of {RDF::Reader}.
For example, if rdf/turtle
is loaded, this allows the following:
graph = RDF::Graph.new << [:hello, RDF::DC.title, "Hello, world!"]
graph.to_ttl
Similarly, {RDF::Mutable} implements from_{format}
for each available instance
of {RDF::Writer}. For example:
graph = RDF::Graph.new
graph.from_ttl("[ a <http://www.w3.org/1999/02/22-rdf-syntax-ns#Resource>]")
Note that no prefixes are loaded automatically, however they can be provided as arguments:
graph.from_ttl("[ a rdf:Resource]", :prefixes => {:rdf => RDF.to_uri})
Querying RDF data using basic graph patterns (BGPs)
require 'rdf/ntriples'
graph = RDF::Graph.load("http://ruby-rdf.github.com/rdf/etc/doap.nt")
query = RDF::Query.new({
:person => {
RDF.type => FOAF.Person,
FOAF.name => :name,
FOAF.mbox => :email,
}
})
query.execute(graph) do |solution|
puts "name=#{solution.name} email=#{solution.email}"
end
The same query may also be run from the graph:
graph.query(query) do |solution|
puts "name=#{solution.name} email=#{solution.email}"
end
In general, querying from using the queryable
instance allows a specific implementation of queryable
to perform query optimizations specific to the datastore on which it is based.
A separate SPARQL gem builds on basic BGP support to provide full support for SPARQL 1.0 queries.
Using pre-defined RDF vocabularies
DC.title #=> RDF::URI("http://purl.org/dc/terms/title")
FOAF.knows #=> RDF::URI("http://xmlns.com/foaf/0.1/knows")
RDF.type #=> RDF::URI("http://www.w3.org/1999/02/22-rdf-syntax-ns#type")
RDFS.seeAlso #=> RDF::URI("http://www.w3.org/2000/01/rdf-schema#seeAlso")
RSS.title #=> RDF::URI("http://purl.org/rss/1.0/title")
OWL.sameAs #=> RDF::URI("http://www.w3.org/2002/07/owl#sameAs")
XSD.dateTime #=> RDF::URI("http://www.w3.org/2001/XMLSchema#dateTime")
Using ad-hoc RDF vocabularies
foaf = RDF::Vocabulary.new("http://xmlns.com/foaf/0.1/")
foaf.knows #=> RDF::URI("http://xmlns.com/foaf/0.1/knows")
foaf[:name] #=> RDF::URI("http://xmlns.com/foaf/0.1/name")
foaf['mbox'] #=> RDF::URI("http://xmlns.com/foaf/0.1/mbox")
Documentation
http://rubydoc.info/github/ruby-rdf/rdf/frames
RDF Object Model
http://blog.datagraph.org/2010/03/rdf-for-ruby
- {RDF::Value}
- {RDF::Term}
- {RDF::Literal}
- {RDF::Literal::Boolean}
- {RDF::Literal::Date}
- {RDF::Literal::DateTime}
- {RDF::Literal::Decimal}
- {RDF::Literal::Double}
- {RDF::Literal::Integer}
- {RDF::Literal::Time}
- RDF::XSD (extension)
- {RDF::Resource}
- {RDF::Node}
- {RDF::URI}
- {RDF::Literal}
- {RDF::List}
- {RDF::Graph}
- {RDF::Statement}
- {RDF::Term}
RDF Serialization
http://blog.datagraph.org/2010/04/parsing-rdf-with-ruby
- {RDF::Format}
- {RDF::Reader}
- {RDF::Writer}
RDF Serialization Formats
The following is a partial list of RDF formats implemented either natively, or through the inclusion of other gems:
- {RDF::NTriples}
- {RDF::NQuads}
- JSON::LD (extension)
- RDF::JSON (extension)
- RDF::Microdata (extension)
- RDF::N3 (extension)
- RDF::Raptor::RDFXML (extension)
- RDF::Raptor::Turtle (extension)
- RDF::RDFa (extension)
- RDF::RDFXML (extension)
- RDF::TriG (extension)
- RDF::TriX (extension)
- RDF::Turtle (extension)
The meta-gem LinkedData includes many of these gems.
RDF Datatypes
RDF.rb only implements core datatypes from the RDF Datatype Map. Most other XSD and RDF datatype implementations can be find in the following:
- {RDF::XSD}
Graph Isomorphism
Two graphs may be compared with each other to determine if they are isomorphic.
As BNodes within two different graphs are no equal, graphs may not be directly compared.
The RDF::Isomorphic
gem may be used to determine if they make the same statements, aside
from BNode identity (i.e., they each entail the other)
RDF::Isomorphic
RDF Storage
http://blog.datagraph.org/2010/04/rdf-repository-howto
- {RDF::Repository}
- {RDF::Countable}
- {RDF::Enumerable}
- {RDF::Indexable}
- {RDF::Inferable}
- {RDF::Queryable}
- {RDF::Mutable}
- {RDF::Durable}
- {RDF::Transaction}
- RDF::AllegroGraph (extension)
- RDF::Mongo (extension)
- RDF::DataObjects (extension)
- RDF::Sesame (extension)
RDF Querying
- {RDF::Query}
- {RDF::Query::HashPatternNormalizer}
- {RDF::Query::Pattern}
- {RDF::Query::Solution}
- {RDF::Query::Solutions}
- {RDF::Query::Variable}
- SPARQL (extension)
RDF Vocabularies
- {RDF} - Resource Description Framework (RDF)
- {RDF::OWL} - Web Ontology Language (OWL)
- {RDF::RDFS} - RDF Schema (RDFS)
- {RDF::RDFV} - RDF Vocabulary (RDFV)
- {RDF::XSD} - XML Schema (XSD)
Deprecated Vocabularies
The following vocabularies will be deprecated in RDF.rb 2.0 and moved to the rdf-vocab gem.
- {RDF::CC} - Creative Commons (CC)
- {RDF::CERT} - W3 Authentication Certificate (CERT)
- {RDF::DC} - Dublin Core (DC)
- {RDF::DC11} - Dublin Core 1.1 (DC11) deprecated
- {RDF::DOAP} - Description of a Project (DOAP)
- {RDF::EXIF} - Exchangeable Image File Format (EXIF)
- {RDF::FOAF} - Friend of a Friend (FOAF)
- {RDF::GEO} - WGS84 Geo Positioning (GEO)
- {RDF::GR} - GoodRelations (GR)
- {RDF::HT} - Hypertext Transfer Protocol (HT)
- {RDF::ICAL} - RDF Calendar Workspace (ICAL)
- {RDF::MA} - Media Resources (MA)
- {RDF::MO} - Music Ontology (MO)
- {RDF::OG} - Open Graph protocol (OG)
- {RDF::PROV} - Provenance on the web (PROV)
- {RDF::RSA} - W3 RSA Keys (RSA)
- {RDF::RSS} - RDF Site Summary (RSS)
- {RDF::SCHEMA} - Schema.org (SCHEMA)
- {RDF::SIOC} - Semantically-Interlinked Online Communities (SIOC)
- {RDF::SKOS} - Simple Knowledge Organization System (SKOS)
- {RDF::SKOSXL} - SKOS eXtension for Labels (SKOSXL)
- {RDF::V} - RDF data vocabulary (V)
- {RDF::VCARD} - Ontology for vCards (VCARD)
- {RDF::VMD} - Data-Vocabulary.org (VMD)
- {RDF::VOID} - Vocabulary of Interlinked Datasets (VOID)
- {RDF::VS} - SemWeb Vocab Status ontology (VS)
- {RDF::WDRS} - Protocol for Web Description Resources (WDRS)
- {RDF::WOT} - Web of Trust (WOT)
- {RDF::XHTML} - Extensible HyperText Markup Language (XHTML)
- {RDF::XHV} - XHTML Vocabulary (XHV)
Dependencies
- Ruby (>= 1.9.2)
- [LinkHeader][] (>= 0.0.8)
- Soft dependency on RestClient (>= 1.7)
Installation
The recommended installation method is via RubyGems. To install the latest official release of RDF.rb, do:
% [sudo] gem install rdf # Ruby 1.9.2+
Download
To get a local working copy of the development repository, do:
% git clone git://github.com/ruby-rdf/rdf.git
Alternatively, download the latest development version as a tarball as follows:
% wget http://github.com/ruby-rdf/rdf/tarball/master
Resources
- http://rubydoc.info/github/ruby-rdf/rdf/frames
- http://github.com/ruby-rdf/rdf
- http://rubygems.org/gems/rdf
- http://rubyforge.org/projects/rdf/
- http://raa.ruby-lang.org/project/rdf/
- http://www.ohloh.net/p/rdf
Mailing List
Authors
- Arto Bendiken - http://ar.to/
- Ben Lavender - http://bhuga.net/
- Gregg Kellogg - http://greggkellogg.net/
Contributors
- Călin Ardelean - http://github.com/clnx
- Mark Borkum - http://github.com/markborkum
- Danny Gagne - http://www.dannygagne.com/
- Joey Geiger - http://github.com/jgeiger
- Fumihiro Kato - http://fumi.me/
- Naoki Kawamukai - http://github.com/kna
- Tom Nixon - https://github.com/tomjnixon
- Hellekin O. Wolf - http://hellekin.cepheide.org/
- John Fieber - http://github.com/jfieber
- Keita Urashima - http://ursm.jp/
- Pius Uzamere - http://pius.me/
- Judson Lester - https://github.com/nyarly
- Peter Vandenabeele - https://github.com/petervandenabeele
- Tom Johnson - https://github.com/no-reply
Contributing
This repository uses Git Flow to mange development and release activity. All submissions must be on a feature branch based on the develop branch to ease staging and integration.
- Do your best to adhere to the existing coding conventions and idioms.
- Don't use hard tabs, and don't leave trailing whitespace on any line.
Before committing, run
git diff --check
to make sure of this. - Do document every method you add using YARD annotations. Read the tutorial or just look at the existing code for examples.
- Don't touch the
.gemspec
orVERSION
files. If you need to change them, do so on your private branch only. - Do feel free to add yourself to the
CREDITS
file and the corresponding list in the theREADME
. Alphabetical order applies. - Don't touch the
AUTHORS
file. If your contributions are significant enough, be assured we will eventually add you in there. - Do note that in order for us to merge any non-trivial changes (as a rule of thumb, additions larger than about 15 lines of code), we need an explicit public domain dedication on record from you.
License
This is free and unencumbered public domain software. For more information, see http://unlicense.org/ or the accompanying {file:UNLICENSE} file.