This page provides quick links for the Registered FRBR Element Sets and Value Vocabularies.

More and more I come to the conclusion that in the linked data space the thing we seem to focus on today, descriptive cataloging, will be less useful than the entities that are represented by our authority data.

The akronym 'lobid' stands for "Linking Open Bibliographic Data". We support the process of creating Linked Open Bibliographic Data out of existing libraries and other associated data.

This page provides quick links for the Registered RDA Element Sets and Value Vocabularies.
Each set of elements or vocabulary concepts has a link to the general description as well as a link to a list of elements or concepts.

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.

RT @ericaxel: RT @alanmeckler: will soon launch the first job board devoted for #semanticweb, #linkeddata, and #big ...

"…if there are two different things that need to be associated (the described resource and the description resource), then why not just link them, allowing clients to simply discover those links, and then act accordingly."

"Raw data" vs. APIs.

RT @timberners_lee: #opendata #linkeddata // Nature Publishing releases Linked Data platform #webinf

RT @bergie: made screencast showing #Hallo Editor annotating content with #LinkedData: #webinf

A set of best practices and simple approach for a read-write Linked Data architecture, based on HTTP access to web resources that describe their state using RDF.

Wikidata aims to create a free knowledge base about the world that can be read and edited by humans and machines alike. It will provide data in all the languages of the Wikimedia projects, and allow for the central access to data in a similar vein as Wikimedia Commons does for multimedia files. Wikidata is proposed as a new Wikimedia hosted and maintained project.

A pattern catalogue for modelling, publishing, and consuming Linked Data.

In order to consolidate and decode some of the information you need to sift through when learning about rich snippets, we've created this visual guide to walk through the basics, fundamental types, implementation, and benefits of utilizing them.   

Processing large volumes of Linked Data requires sophisticated methods and tools. In the recent years we have mainly focused on systems based on relational databases and bespoke systems for Linked Data processing. Cloud computing offerings such as SimpleDB or BigQuery, and cloud-enabled NoSQL systems including Cassandra or CouchDB as well as frameworks such as Hadoop offer appealing alternatives along with great promises concerning performance, scalability and elasticity. In this paper we state a number of Linked Dataspecific requirements and review existing cloud computing offerings as well as NoSQL systems that may be used in a cloud computing setup, in terms of their applicability and usefulness for processing datasets on a large-scale.

This should give a rough overview over the usage of the different formats.

All you have to do is view source on any nytimes.com article published on or after January, 23 2012. In the HTML you will see new attributes like ‘itemtype’, ‘itemprop’ and ‘itemid’. If you paste an article URL into the Google Rich Snippets tool, you can see a parse of the structured data now embedded into every nytimes.com article,

RT @gothwin: so RDF/#linkeddata/semantics related jobs at Apple now eh ...

Like the DTD-based W3C markup validation service, this service checks the markup validity of Web documents, but instead uses the backend from the Validator.nu engine. The default setting of the validator validates HTML5 with RDFa 1.1. Lite and with microdata, the two simpler syntaxes to add structured data to HTML.

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.

Microformats, RDFa and microdata all enable consumers to extract data from HTML pages. This data may be embedded within enhanced search engine results, exposed to users through browser extensions, aggregated across websites or used by scripts running within those HTML pages.

This guide aims to help publishers and consumers of HTML data use it well. With several syntaxes and vocabularies to choose from, it provides guidance about how to decide which meets the publisher's or consumer's needs. It discusses when it is necessary to mix syntaxes and vocabularies and how to publish and consume data that uses multiple formats. It describes how to create vocabularies that can be used in multiple syntaxes and general best practices about the publication and consumption of HTML data.

At a first glance there might appear to be an obvious alignment and overlap between the approaches prescribed by REST and Linked Data. On more detailed inspection divergences in scope and applicability present themselves, and for some aspects, incompatibility. In this paper we investigate these similarities and differences and suggest the coupling is worthy of a third look: in combination as a exible environment in which the developer can focus on domain driven applications.

The term “Linked Data” refers to a set of best practices for publishing and connecting structured data on the Web. These best practices have been adopted by an increasing number of data providers over the last three years, leading to the creation of a global data space containing billions of assertions— the Web of Data. In this article, the authors present the concept and technical principles of Linked Data, and situate these within the broader context of related technological developments. They describe progress to date in publishing Linked Data on the Web, review applications that have been developed to exploit the Web of Data, and map out a research agenda for the Linked Data community as it moves forward.

This tutorial will guide you through the key steps to build, test, and publish your first Open Graph app. We will build a sample app that allows users on your website to publish stories about cooking recipes.

Key recommendations of the report are:

That library leaders identify sets of data as possible candidates for early exposure as Linked Data and foster a discussion about Open Data and rights;
That library standards bodies increase library participation in Semantic Web standardization, develop library data standards that are compatible with Linked Data, and disseminate best-practice design patterns tailored to library Linked Data;
That data and systems designers design enhanced user services based on Linked Data capabilities, create URIs for the items in library datasets, develop policies for managing RDF vocabularies and their URIs, and express library data by re-using or mapping to existing Linked Data vocabularies;
That librarians and archivists preserve Linked Data element sets and value vocabularies and apply library experience in curation and long-term preservation to Linked Data datasets.

This document, a deliverable from the W3C Library Linked Data Incubator Group, is an attempt to identify a set of useful resources for creating or consuming Linked Data in the library domain. It is intended both for novices seeking an overview of the library Linked Data domain, and for experts in search of a quick look-up or refresher. The final report of the Incubator Group suggests that the success of Linked Data in any domain depends on the ability of its practitioners to identify, re-use, or connect to already available datasets and data models. Library Linked Data is not an exception. Such an identification effort is crucial given the complexity and variety of library data resources, many of them already available as Linked Data at the time of writing this report. We hope that this document will help those who undertake such tasks.

Survey of frameworks for publishing RDF vocabularies/ontologies online.

This post attempts to clarify those technical issues by providing an easy-to-read list of similarities and differences between RDFa, Microdata and Microformats. A simple table summarizing all features across each structured data syntax is listed below. Each feature is linked to a brief explanation of the feature toward the bottom of the page.

In summary the key benefits of using Semantic Web technology for Volkswagen were as follows:

A standardised interface to data and content, accessible to developers with different skillsets, using different technologies within and without the organisation.
Separation of concerns between information and application, both logically and physically.
Increases value, reusability and accessibility of data.
Very powerful federation features.
Adoption and use didn't necessitate process or change management. It could be leveraged at any stage within the product lifecycle painlessly and gracefully, both internally and externally.

JSON-LD processor written in Python.

Linked Data is Storytelling 101 for computers. It doesn’t have the full richness, complexity and nuance that we invest in our narratives, but it does at least help computers to fit all the bits together in meaningful ways. And if we talk nice to them, then they can apply their newly-acquired interpretative skills to the things that they’re already good at — like searching, aggregating, or generating the sorts of big pictures that enable us to explore the contexts of our stories.

Interesting presentation on how EU TV archives are using #linkeddata to achieve interoperability: #inls520

Please note that the final report is not officially published yet. This will happen in the second half of September, at a different place on the W3C website, after some final copy editing has been made!

The number of influential libraries publishing their metadata onto the web as linked open data, which is the heart of the Semantic Web, is growing at a dizzying rate. To further this trend, the World Wide Web Consortium (W3C), a major nonlibrary organization that supports the technologies that undergird the Semantic Web (or the Web of Data), will release a new report in September devoted to library linked data (LLD).

In this Synthesis lecture we provide readers with a detailed technical introduction to Linked Data. We begin by outlining the basic principles of Linked Data, including coverage of relevant aspects of Web architecture. The remainder of the text is based around two main themes - the publication and consumption of Linked Data. Drawing on a practical Linked Data scenario, we provide guidance and best practices on: architectural approaches to publishing Linked Data; choosing URIs and vocabularies to identify and describe resources; deciding what data to return in a description of a resource on the Web; methods and frameworks for automated linking of data sets; and testing and debugging approaches for Linked Data deployments. We give an overview of existing Linked Data applications and then examine the architectures that are used to consume Linked Data from the Web, alongside existing tools and frameworks that enable these. Readers can expect to gain a rich technical understanding of Linked Data fundamentals, as the basis for application development, research or further study.

More and more of the world's data is moving onto the Web. We want to share, re-mix and use this data to build more awesome Web applications. Using structured data technologies to mark up people, places, events, recipes, ratings, music, movies and products on the Web makes everybody's life easier. This site will help you learn about big data, the semantic web, and the practical application of technologies such as Microformats, RDFa, Microdata and JSON-LD.

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."

DBpedia Spotlight is a tool for annotating mentions of DBpedia resources in text, providing a solution for linking unstructured information sources to the Linked Open Data cloud through DBpedia. DBpedia Spotlight performs named entity extraction, including entity detection and Name Resolution (a.k.a. disambiguation). It can also be used for building your solution for Named Entity Recognition, amongst other information extraction tasks.

RT @gothwin: OGC Seeks Comment on candidate GeoSPARQL standard: #geosparql #linkeddata

RT @gluejar: Why haven't I heard of Nanopublications before? Brilliant! #linkeddata #lodlam

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.

LinkedDataSail gathers RDF data incrementally, dereferencing URIs in response to queries.

AIMS supports the implementation of structured and linked information and knowledge by fostering a community of practice centered on the themes of interoperability, reusability and cooperation. It shares vocabularies, methodologies, tools and services in order to promote coherence in agricultural information.

sameas.org results can be remarkably broken sometimes: #linkeddata

Deniz is a simple RDF browser written in Javascript.

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.

Data "beauty" might be subjective, and the same data may have different applicability to different tasks, but there are a lot of obvious and straightforward ways of thinking about the quality of a dataset independent of the particular preferences of individua beholders. Here are just some of them.

Nick Carr accuses Google of using #RDFa and #linkeddata to conspire against Grandma: #ldow2011

VoID is an RDF Schema vocabulary for expressing metadata about RDF datasets. It is intended as a bridge between the publishers and users of RDF data, with applications ranging from data discovery to cataloging and archiving of datasets. This document is a detailed guide to the VoID vocabulary. It describes how VoID can be used to express general metadata based on Dublin Core, access metadata, structural metadata, and links between datasets. It also provides deployment advice and discusses the discovery of VoID descriptions.

This book gives an overview of the principles of Linked Data as well as the Web of Data that has emerged through the application of these principles. The book discusses patterns for publishing Linked Data, describes deployed Linked Data applications and examines their architecture.

Features case studies by speakers from Cornell University, the Smithsonian Institution, and the Internet Archive, as well as a summary presentation by MIT's MacKenzie Smith.

What you may not realize though, is that the social graph concept is incredibly simple, that there's not just a social graph, one graph, but an infinite amount of incredibly interesting graphs, that each graph holds a world full of unrealized, valuable and useful information, knowledge even, and that... let's cut to the point here, 99.99999999% of these graphs are locked away, most people don't even know that they exist, let alone that they're sitting on one of these gold mines, the graphs are locked away unrealized in almost every application and website you use, hidden in databases, and if you're a developer, programmer, db admin or website owner, then you definitely have one or more of these graphs under your control.

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 must be simple for Web developers to extract and utilize structured information from a Web document. This document details such a mechanism; an RDFa Document Object Model Application Programming Interface (RDFa DOM API) that allows simple extraction and usage of structured information from a Web document.

The Open Data Protocol (OData) is a Web protocol for querying and updating data that provides a way to unlock your data and free it from silos that exist in applications today. OData does this by applying and building upon Web technologies such as HTTP, Atom Publishing Protocol (AtomPub) and JSON to provide access to information from a variety of applications, services, and stores.

Surprisingly, there is still no service that provides standardised URIs for temporal periods. This is partly due to the frequent controversy associated in pinning their boundaries down, as well as the contrast between those with relative and those with absolute dating. CommonEras is an attampt to build a community-based vocabulary service, with appropriate visualisation and search technologies, for temporal periods ('the Sixties', 'the Victorian Era', 'the Golden Age of Comics', etc.).

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.

Talk given at the 2nd Linked Data on the Web workshop (LDOW) co located with WWW 2009, Madrid.

Create semantically enhanced content, without knowing about semantic technologies, with automatically proposed annotations.

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.

The server forwards from the identification URI to the generic document URI. This has the advantage that clients can bookmark and further work with the generic document. This setup should be used when the RDF and HTML (and possibly more alternative representations) convey the same information in different forms.

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