When crafting RDF documents, I try to use standard schema wherever possible. Unfortunately, this often results in having a multitude of browser tabs open at each schema specification page. Therefore I have put together this 'cheatsheet' simply to make my life easier.

Martha asks a number of questions about RDF in the article. Even the title is a question: "Can Bibliographic data be Put Directly onto the Semantic Web?" (Answer: it already is ) Martha is conducting an admirable gedanken experiment about the future of cataloging, creating her own cataloging code and trying to mesh her ideas with concepts coming out of the semantic web community. The article's value is not only in her conclusions but in the questions that she raises. In its unfinished state, Martha's thinking is provocative and just begging for further discussion and development.

talked about many many things including my first, but hardly my last, attempt to make him explain RDF to me.

The New York Times has published 5,000 people subject headings as linked open data under a CC BY license. We provide both RDF documents and a human-friendly HTML versions.

Managing News is both a product and a platform. Out of the box it can help your communications team manage a brand reputation, allow geographically dispersed clusters of NGOs stay on the same page, or act as a simple thematic news planet to share feeds with the world. It can also serve as a platform to build highly custom data aggregators that suck in everything from CSV to RDF to custom XML formats and that need unique workflows and visualizations. Managing News is built on Drupal and uses Features, which makes it highly extensible.

Why is it good? Because we’ll learn a few tricks about how to do stuff with just JavaScript and no yucky backend stuff like PHP.

Way back in 2006 I wrote a blog post concerning the modelling of time in RDF (see Refactoring Bio With Einstein Part 3: Temporal Invariants. That post also provoked some discussion in the blogosphere. Although I haven’t written anything on the subject for the past three years I haven’t stopped thinking about it. In fact I’ve been working quite hard on the problem, mainly by modelling real data, especially geographical information. This is the first of a series of blog posts describing my experiments. I’d like to thank Leigh Dodds and Jeni Tennison who gave me valuable feedback on an earlier version of this write-up.

Summary: As more data is being stored in RDF formats like RSS, a need has arisen for a simple way to locate specific information. SPARQL, a powerful new query language fills that space, making it easy to find the data you need in the RDF haystack. Take a tour of SPARQL's features and learn how to use SPARQL queries from your own Java™ applications with the Jena Semantic Web Toolkit.

Mais en RDF, contrairement à XML, chaque triplet est indépendant et signifiant indépendamment de tout contexte, ce qui signifie que je peux tout à fait utiliser pour décrire la même ressource des propriétés du Dublin Core et d'autres propriétés, venant d'autres vocabulaires ou ontologies.

We were able to come up with rules that make using prefixes in almost any context simpler. Note, these are for the most part AUTHORING guidelines, not requirements when reading:

1. Reusing the same prefix in the same document with different meanings is horribly confusing (”If you did that, I’d break your figures.”). Possible to figure out, but not really desirable. Seems like a reasonable place for a warning.

2. Defining all the prefixes in one place makes it simpler to keep track of them. But understood when it would be simpler to define a new prefix for a section of content.

3. “Couldn’t you have a simple tool that just shows you what prefixes are defined at any point in the document?” How such a tool has failed to exist in the XML world… may write this.

Etendre un éditeur WYSIWYG existant (FCKEditor) pour manipuler du RDFa