This document is a WorkInProgress and will be updated as new RDF examples and tests are made available.

This document describes the RDF Test Cases deliverable for the RDF Core Working Group as defined in the WG's Charter.

Automatic metadata generation may provide a solution to the problem of inconsistent, unreliable metadata describing resources on the Web. The Resource Description Framework (RDF [10]) provides a domain-neutral foundation on which extensible element sets can be defined and expressed in a standard notation. This paper describes how an automatic classifier, that classifies HTML documents according to Dewey Decimal Classification (DDC [8]), can be used to extract context sensitive metadata which is then represented using RDF.

The Resource Description Framework (RDF) is a general framework for how to describe any Internet resource such as a Web site and its content. An RDF description (such descriptions are often referred to as metadata, or "data about data") can include the authors of the resource, date of creation or updating, the organization of the pages on a site (the sitemap), information that describes content in terms of audience or content rating, key words for search engine data collection, subject categories, and so forth. The Resource Description Framework will make it possible for everyone to share Web site and other descriptions more easily and for software developers to build products that can use the metadata to provide better search engines and directories, to act as intelligent agents, and to give Web users more control of what they're viewing. The RDF is an application of another technology, the Extensible Markup Language (XML), and is being developed under the auspices of the World Wide Consortium (W3C).

The terms RDF, OIL, DAML, and topic maps all tend to be mentioned whenever technologies for the semantic web, knowledge management, or information management are being discussed. Finding someone who knows more than one of these well is almost impossible, however.

RDF was designed to be (amongst many other things!) an appropriate data representation formalism for logic/inference applications on the Web. A number of papers and tools already exist that explore the relationship between the W3C's RDF and the world of logic programming. Our aim here is to put some of this into practice and explore the possibilities it raises for a the creation of more intelligent and intuitive information management tools.

This memo describes some experimental work that is being undertaken with the goal of simplifying the application of RDF to a number of information modelling problems, particularly involving relationships between physical-world objects and trust modelling. It is our goal that, by using contexts, a degree of modularity can be introduced that will ease the construction of RDF information models.

I've written before about What's right with RDF, but I have to admit that overall I'm deeply unhappy with RDF on a number of different levels. While I think the kinds of things that RDF does are useful at times, I think RDF gets a number of things painfully wrong. Not only does RDF get them wrong, but RDF's getting things wrong screws up other things as well.

This document provides a brief introduction to the underlying structure of the RDF/XML 1.0 graph serialization syntax. The Intended audience is mainly content and tool developers familiar with XML basics, and with the RDF model, who want a minimalistic understanding of RDF's XML syntax, so they can read and write RDF/XML with more confidence.

This document provides an overview of the RDF “core” implementation, that is, the implementation of the RDF model within Mozilla. It assumes some familiarity with the RDF model as described in the RDF Model and Syntax Specification. See also the Datasource HOWTO for details on writing a datasource.

What are the advantages of RDF over other metadata systems? In this page we try to collect a list of some of them.

RDF serves two primary purposes in Mozilla. First, it is a simple, cross-platform database for small data stores. Second, and more importantly, the RDF model is used along with XUL templates as an abstract "API" for displaying information. RDF in 50 words or less is a quick, high-level description of what RDF does in Mozilla. The Back-end Architecture document describes in more detail how Mozilla's RDF implementation works, and gives a quick overview of the interfaces that are involved.

This is a project to investigate the integration of Z39.50 search capabilities with Mozilla's RDF-based information management environment.

RQL is a typed language following a functional approach (a la ODMG-OQL) and supports generalized path expressions (GPEs) featuring variables on both labels for nodes (i.e., classes) and edges (i.e., properties). RQL relies on a formal graph model (as opposed to other triple-based RDF QLs ) that captures the RDF modeling primitives and permits the interpretation of superimposed resource descriptions by means of one or more schemas.

The History of RDF Sometime in the mid-nineties, a guy named Ramanathan V. Guha (everyone calls him Guha because they're scared of “Ramanathan,” go figure) went to work for Apple Computer. He cooked up this metadata format named Meta Content Framework (MCF), and then they built a cool app called Hotsauce, driven by MCF, that represented web sites as little 3-D planetary systems and you could fly around theml. Cool, as I said, but it didn't change the world.

This document defines an abstract syntax on which RDF is based, and which serves to link its concrete syntax to its formal semantics. It also includes discussion of design goals, meaning of RDF documents, key concepts, datatyping, character normalization and handling of URI references.

The UML community developed a set of useful models for representing static and dynamic components of software-intensive systems. UML is an industry standard and serves as a modeling basis for emerging standards in other areas like OIM, CWM etc. As of today there exist a variety of UML vocabularies for describing object models, datatypes, database schemas, transformations etc.

RDF follows a property-centric approach. Let the syntax reflect it. Every XML tag encountered during processing is considered to be a property name, unless explicitly overriden. For a tag to be a class name, it must carry the XML attribute rdf:instance.

This document identifies and defines the status of issues considered by the RDFCore Working Group. It is a working document, and as such is subject to constant change as the WG proceeds.

The RDF calendar taskforce is an informal grouping of individuals interested in calendaring and scheduling, primarily in RDF. Through scenario-lead discussion by email and irc, the taskforce will aim to draft an RDF schema for calendar events. It will also aim to demonstrate the use of RDF in a calendaring and scheduling context.