Monday, June 18, 2012

Dublin Core News

A couple of news items from DCMI.
DCMI Metadata Terms published with RDFa markup

A maintenance release of DCMI Metadata Terms, published today, now includes HTML markup describing all of its properties, classes, datatypes, and vocabulary encoding schemes in machine-readable RDF in accordance with the new W3C RDFa Lite 1.1 specification. RDFa Lite 1.1, published as a W3C Recommendation on 7 June 2012, is the simplest variant of RDFa, a syntax for embedding structured data in Web pages. A Web page with RDFa provides -- in the same source document -- both the human-readable text rendered on-screen by browsers and the detailed machine-readable representation needed by Semantic Web applications. The publication software used by DCMI for the past decade was modified and extended to support RDFa by Hugh Barnes, Gregg Kellogg, and Mitsuharu Nagamori with help from Manu Sporny, Tom Baker, Dan Brickley, and Jon Phipps. All of the software and data used to generate this documentation is available from an open-source repository on GitHub.

DCMI Metadata Terms available in multiple formats via content negotiation

Following the W3C guidelines "Best Practice Recipes for Publishing RDF Vocabularies", documentation of DCMI's metadata terms may now be requested by Web browsers and software applications in several formats. For example, an RDF description of the DCMI property "Title" may be requested as a file in RDF/XML or Turtle syntax, via HTTP content negotiation, or as an HTML page with an RDF representation embedded in its markup using RDFa. Since March 2000, users navigating to the URI in a Web browser have been shown a difficult-to-read RDF/XML schema. Browsers will now display a human-readable HTML document, and most browsers will take users to the spot in the page where the property "Title" is defined. DCMI's implementation of content negotiation was undertaken by Jon Phipps with assistance from Tom Baker and Jinho Park. Interested software implementers are invited to inspect, comment on, contribute to, or raise issues about the approach taken, which is fully documented in an open-source repository on GitHub.

No comments: