Dewey Web Services For a long time, the Dewey team at OCLC has wanted to do something with Linked Data. That is, apply Linked Data principles to parts of the Dewey Decimal Classification and present the data as a small “terminology service.” The service should respond to regular HTTP requests with either a machine- or a human-readable presentation of Dewey classes. There should be a URI (and, even better, a Web page that delivers a useful description) for every Dewey concept, not just single classes. The data should be presented in a format that is capable of handling rich semantic information and in a way that allows users or user agents to just “follow their nose” to explore the data. For more complex stuff, the service should offer an API-like query access. Along comes dewey.info Tim Berners-Lee's new-ish Linked Data meme “Raw Data Now!” For now, the latter approach seemed a more effective driving force that prompted us to confront several different issues that are relevant for either one.
Getting Started - schema.org Most webmasters are familiar with HTML tags on their pages. Usually, HTML tags tell the browser how to display the information included in the tag. For example, <h1>Avatar</h1> tells the browser to display the text string "Avatar" in a heading 1 format. Schema.org provides a collection of shared vocabularies webmasters can use to mark up their pages in ways that can be understood by the major search engines: Google, Microsoft, Yandex and Yahoo! 1. 1a. Your web pages have an underlying meaning that people understand when they read the web pages. 1b. itemscope and itemtype Let's start with a concrete example. <div><h1>Avatar</h1><span>Director: James Cameron (born August 16, 1954)</span><span>Science fiction</span><a href=".. To begin, identify the section of the page that is "about" the movie Avatar. <div itemscope><h1>Avatar</h1><span>Director: James Cameron (born August 16, 1954) </span><span>Science fiction</span><a href=".. Back to top 1c. itemprop 1d. 2. 2b. 2c. 3. 3a. 3b. Enumerations