irON (instance record and Object Notation) is a abstract notation and associated vocabulary for specifying RDF triples and schema in non-RDF forms. Its purpose is to allow users and tools in non-RDF formats to stage interoperable datasets using RDF.

Anything To Triples (Any23) is a library, a Web service and a set of command line tools for extracting structured data in RDF format from a variety of Web documents.

This document describes N-Quads, a format that extends N-Triples with context. Each triple in an N-Quads document can have an optional context value.

The purpose of this cookbook is to document and discuss the use of RDF in digital humanities. Its focus is specific applications as found in the real world, though a few general principles are suggested. It assumes that you’re vaguely comfortable with RDF and RDFa.

From a Stanford Libraries newsletter: "Linked Data could provide the antidote to the chaos and complexity of the current overabundant array of too simple search mechanisms with too little precision and too short recall of relevant results."

This document defines a vocabulary and processing model for a configurable API layer intended to support the creation of simple RESTful APIs over RDF triple stores.

Kasabi brings together data providers (organisations, businesses, individuals) with developers and domain experts. This community lets data providers explore business models and add value to their datasets, while allowing developers access to build their applications and services around them.

4store was designed by Steve Harris and developed at Garlik to underpin their Semantic Web applications. It has been providing the base platform for around 3 years. At times holding and running queries over databases of 15GT, supporting a Web application used by thousands of people.

Raptor RDF parser and serializer bindings for Node.js

Deniz is a simple RDF browser written in Javascript.

Load SPARQL result table from an end-point as a data.frame

The Virtuoso Redland RDF Provider is an implementation of the Storage API, Model and Query interfaces of the Redland framework for RDF. This provider enables the execution of queries via the Redland Rasqal query engine or via Virtuoso query engine directly against the Virtuoso OpenSource Quad Store.

JSON-LD (JavaScript Object Notation for Linked Data) is a lightweight Linked Data format. It is easy for humans to read and write. It is easy for machines to parse and generate. It is based on the already successful JSON format and provides a way to help JSON data interoperate at Web-scale. If you are already familiar with JSON, writing JSON-LD is very easy. There is a smooth migration path from the JSON you use today, to the JSON-LD you will use in the future. These properties make JSON-LD an ideal Linked Data interchange language for JavaScript environments, Web services, and unstructured databases such as CouchDB and MongoDB.

The MADS/RDF (Metadata Authority Description Schema in RDF) vocabulary, a data model for authority and vocabulary data used within the library and information science (LIS) community, which is inclusive of museums, archives, and other cultural institutions.

It provides constructs that will seem familiar to those used to ORMs like SQLAlchemy or Django but which are backed by an RDF store containing multiple graphs and are ultimately expressed in OWL.

One can now have RDF and full text indexing on the desktop without running a Java VM or any other memory-intensive software.

rdfQuery is an easy-to-use Javascript library for RDF-related processing. You can use it to parse RDFa embedded within your page, query over the facts it contains, and reason to produce more facts. In concert with an server-side triplestore, rdfQuery can be used to create interfaces for editing the semantic web.

Survey of approaches to handling time-sensitive statements in RDF.

SPIN is a collection of RDF vocabularies enabling the use of SPARQL to define constraints and inference rules on Semantic Web models. SPIN also provides meta-modeling capabilities that allow users to define their own SPARQL functions and query templates. Finally, SPIN includes a ready to use library of common functions.

RDFTEF is an open source Java framework that supports textual encoding in RDF+OWL. It provides a shell that allows the model to be queried using SPARQL, is able to import existing encoded text in XML TEI format, and can save the model to RDF/XML or export it in form of aspect slices, as XML TEI format.

Scripts for turning various things into RDF.

Perform full text searches, filtered by types that are inferred.

This specification contains a framework for representing pointers - entities that permit identifying a portion or segment of a piece of content - making use of the Resource Description Framework (RDF). It will also describe a number of specific types of pointers that permit portions of a document to be referred to in different ways.

jOWL is a jQuery plugin for navigating and visualising OWL-RDFS documents.

This document describes an extension to the Sitemap protocol targeted at the efficient discovery and use of RDF data. The extension allows Data publishers to state where documents containing RDF data are located, and to advertise alternative means to access it, such as data dumps and SPARQL endpoints.

If you were at ALA Midwinter in Denver (January, 2009) you may have been in one of the meetings where the Library of Congress announced its intention to atone for the lcsh.info fiasco. In case you missed that, Ed Summers of LC created an online version of the Library of Congress Subject Heading authority records, re-organized as a SKOS vocabulary and available for linking on the open Web. After being available for about six months (beginning in May of 2008), Ed was asked by his employer to take down the site on December 18, 2008. This was in spite of the fact that the data had been out there long enough to have a number of users, and that the removal broke existing systems that had developed around the data.[Note, lcsh.info has been re-born as http://lcsubjects.org/, hosted by Talis.]The outcry in the community was strong, including a reply to Ed's lcsh.info blog post by Sir Web himself, Tim Berners-Lee. Library of Congress must have been suitably embarassed.Thus the announcement at Midwinter that LC not only understands the value of linked open access to LCSH, but that all of the vocabularies managed by LC -- from the name authorities to the lists of document types, languages, locations, etc., -- need to be openly available in a format suitable for inclusion in Web services. LC has created a web site to host these vocabularies: id.loc.gov. On that site they say:Initially, within 6 to 8 weeks, the Library of Congress will release its first offering: the Library of Congress Subject Headings. This will be an almost verbatim re-release of the system and content once found at the popular prototype lcsh.info service.They also say:We aim to make resources available on this site within 6-8 weeks. Check this site regularly for more updates as we continue to develop this service!The page is dated 1/22/09. My calculations show that 9 weeks have passed. OK, that's only one week over their stated deadline. But nothing on the page has changed. No resources have been made available. An "almost verbatim" release of lcsh.info should not be too hard given that Ed had code written that he has made publicly available.But even today, the promised service is 6-8 weeks away. It may stay that way for a long time. Maybe even forever.Why does this matter? It matters because the availability of these vocabularies is essential for the library world to move forward. Some of us have been asking LC to put the vocabularies online in a machine-actionable format for a very long time. The Dublin Core community worked with LC to create a machine-actionable and URI-identified version of the MARC role terms as early as 2005. You can't find this linked from any of the MARC documentation. Some of us brought up the topic ad nauseum at MARBI meetings, but to no avail. Now LC seems to have "gotten it" conceptually but they have yet to show us that they can deliver.I may seem to be undeservedly impatient on this score, but it's not that we have been waiting for this for 9 weeks: we've been waiting for years. And quite honestly, this is not rocket science, nor does LC have no guidance for how to manage this data. In fact, they could use the NSDL Metadata Registry, or, if they insist on hosting this themselves, the Registry's source code is available. Quite frankly, if LC does not prove to us soon that it can perform this necessary function, I feel that we are quite justified in going forward without them, registering the vocabularies where they can be used and managed by anyone who needs them, and going forward with a transformation of library data that will meet 21st century needs.

Open Anzo has an impressive list of features beyond the simple ability to load and query triples.

Lua ActiveRDF gives you a Domain Specific Language (DSL) for your RDF model: you can address RDF resources, classes, properties, etc. programmatically, without queries.

Anzo is an open source enterprise-featured RDF store and service oriented middleware platform that provides support for multiple users, distributed clients, offline work, real-time notification, named-graph modularization, versioning, access controls, and transactions with preconditions.

voiD is a vocabulary and a set of instructions that enables the discovery and usage of linked datasets.

The OWL 2 RL profile is aimed at applications that require scalable reasoning without sacrificing too much expressive power. It is designed to accommodate both OWL 2 applications that can trade the full expressivity of the language for efficiency, and RDF(S) applications that need some added expressivity from OWL 2.

One of the advantages of how RDF works is that it is possible to query a dataset without knowing anything about the data set at the outset. There are some simple queries that you can get started with to show how this works.

rdfxml.py is a standalone Python module in under 10KB that parses RDF/XML using SAX.

This is a syntax file to highlight Notation 3 documents for describing RDF (meta-)data.

Requires Vim compiled with Python and RDFLib installed for Python.

Libraries for constructing, parsing, manipulating and serializing OAI-ORE Resource Maps.

Prolog packages for reading, querying and storing semantic web documents as well as XPCE libraries that provide visualisation and editing.

This document describes best practice recipes for publishing vocabularies or ontologies on the Web (in RDF Schema or OWL).

Summarizes the various useful APIs available in Raptor.