<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
    <title>Recent Publications</title>
    <link rel="alternate" type="text/html" href="http://www.w3.org/" />
    <link rel="self" type="application/atom+xml" href="http://www.w3.org/News/atom.xml" />
    <id>tag:www.w3.org,2008-09-29://4</id>
    <updated>2013-05-16T14:12:24Z</updated>
    
    <generator uri="http://www.sixapart.com/movabletype/">Movable Type 4.34-en</generator>

<entry>
    <title>Last Call: JSON-LD 1.0 Processing Algorithms and API</title>
    <link rel="alternate" type="text/html" href="http://www.w3.org/News/2013.html#entry-9827" />
    <id>tag:www.w3.org,2013://4.9827</id>

    <published>2013-05-16T13:58:33Z</published>
    <updated>2013-05-16T14:12:15Z</updated>

    <summary>The RDF Working Group has published a Last Call Working Draft of JSON-LD 1.0 Processing Algorithms and API. This specification defines an Application Programming Interface (API) and a set of algorithms for programmatic transformations of JSON-LD documents. Restructuring data according...</summary>
    <author>
        <name>W3C Staff</name>
    </author>
    
        <category term="Home Page Stories" scheme="http://www.sixapart.com/ns/types#category" />
    
        <category term="Publication" scheme="http://www.sixapart.com/ns/types#category" />
    
        <category term="Semantic Web" scheme="http://www.sixapart.com/ns/types#category" />
    
    
    <content type="html" xml:lang="en" xml:base="http://www.w3.org/">
        
        <![CDATA[<p>The <a href="http://www.w3.org/2011/rdf-wg/">RDF Working Group</a> has published a Last Call Working Draft of <a href="http://www.w3.org/TR/2013/WD-json-ld-api-20130516/">JSON-LD 1.0 Processing Algorithms and API</a>. This specification defines an Application Programming Interface (API) and a set of algorithms for programmatic transformations of JSON-LD documents. Restructuring data according the defined transformations often dramatically simplifies its usage. Comments are welcome through 06 June. Learn more about the <a href="http://www.w3.org/2001/sw/">Semantic Web Activity</a>.</p>]]>
    </content>
</entry>

<entry>
    <title>Last Call: Indexed Database API</title>
    <link rel="alternate" type="text/html" href="http://www.w3.org/News/2013.html#entry-9826" />
    <id>tag:www.w3.org,2013://4.9826</id>

    <published>2013-05-16T13:53:57Z</published>
    <updated>2013-05-16T14:12:11Z</updated>

    <summary>The Web Applications Working Group has published a Last Call Working Draft of Indexed Database API. This document defines APIs for a database of records holding simple values and hierarchical objects. Each record consists of a key and some value....</summary>
    <author>
        <name>W3C Staff</name>
    </author>
    
        <category term="Home Page Stories" scheme="http://www.sixapart.com/ns/types#category" />
    
        <category term="Publication" scheme="http://www.sixapart.com/ns/types#category" />
    
        <category term="Web Design and Applications" scheme="http://www.sixapart.com/ns/types#category" />
    
    
    <content type="html" xml:lang="en" xml:base="http://www.w3.org/">
        
        <![CDATA[<p>The <a href="http://www.w3.org/2008/webapps/">Web Applications Working Group</a> has published a Last Call Working Draft of <a href="http://www.w3.org/TR/2013/WD-IndexedDB-20130516/">Indexed Database API</a>. This document defines APIs for a database of records holding simple values and hierarchical objects. Each record consists of a key and some value. Moreover, the database maintains indexes over records it stores. An application developer directly uses an API to locate records either by their key or by using an index. A query language can be layered on this API. An indexed database can be implemented using a persistent B-tree data structure. Comments are welcome through 07 June. Learn more about the <a href="http://www.w3.org/2006/rwc/">Rich Web Client Activity</a>.</p>]]>
    </content>
</entry>

<entry>
    <title>Two Drafts Published by the System Applications Working Group</title>
    <link rel="alternate" type="text/html" href="http://www.w3.org/News/2013.html#entry-9825" />
    <id>tag:www.w3.org,2013://4.9825</id>

    <published>2013-05-16T13:51:11Z</published>
    <updated>2013-05-16T14:12:03Z</updated>

    <summary>The System Applications Working Group has published two Working Drafts today: The app: URI scheme. This specification defines the app: URI scheme and rules for dereferencing an app: URI, which can be used to address resources inside a package (e.g.,...</summary>
    <author>
        <name>W3C Staff</name>
    </author>
    
        <category term="Home Page Stories" scheme="http://www.sixapart.com/ns/types#category" />
    
        <category term="Publication" scheme="http://www.sixapart.com/ns/types#category" />
    
        <category term="Web Design and Applications" scheme="http://www.sixapart.com/ns/types#category" />
    
        <category term="Web of Devices" scheme="http://www.sixapart.com/ns/types#category" />
    
    
    <content type="html" xml:lang="en" xml:base="http://www.w3.org/">
        
        <![CDATA[<p>The <a href="http://www.w3.org/2012/sysapps/">System Applications Working Group</a> has published two Working Drafts today:</p>
<ul class="show_items">
<li><a href="http://www.w3.org/TR/2013/WD-app-uri-20130516/">The app: URI scheme</a>. This specification defines the app: URI scheme and rules for dereferencing an app: URI, which can be used to address resources inside a package (e.g., a packaged application). The dereferencing model relies on HTTP semantics to return resources in a manner akin to a HTTP GET request. Doing so allows this URI scheme to be used with other technologies that rely on HTTP responses to function as intended, such as XHR.</li>
<li><a href="http://www.w3.org/TR/2013/WD-messaging-20130516/">Messaging API</a>. This specification defines a System Level API which offers a simple interface to get access to mobile messaging services. A typical use case of the Messaging API is the implementation of a messaging client application that allows the user to send SMS and MMS messages as well as to access and manage the received SMS and MMS messages.</li>
</ul>
<p>Learn more about the <a href="http://www.w3.org/2007/uwa/">Ubiquitous Web Applications Activity</a>.</p>]]>
    </content>
</entry>

<entry>
    <title>Media Capture and Streams Draft Published</title>
    <link rel="alternate" type="text/html" href="http://www.w3.org/News/2013.html#entry-9824" />
    <id>tag:www.w3.org,2013://4.9824</id>

    <published>2013-05-16T13:45:48Z</published>
    <updated>2013-05-16T14:11:58Z</updated>

    <summary>The Web Real-Time Communication Working Group and the Device APIs Working Group have published a Working Draft of Media Capture and Streams. This document defines a set of JavaScript APIs that allow local media, including audio and video, to be...</summary>
    <author>
        <name>W3C Staff</name>
    </author>
    
        <category term="Home Page Stories" scheme="http://www.sixapart.com/ns/types#category" />
    
        <category term="Publication" scheme="http://www.sixapart.com/ns/types#category" />
    
        <category term="Web Design and Applications" scheme="http://www.sixapart.com/ns/types#category" />
    
    
    <content type="html" xml:lang="en" xml:base="http://www.w3.org/">
        
        <![CDATA[<p>The <a href="http://www.w3.org/2011/04/webrtc/">Web Real-Time Communication Working Group </a> and the <a href="http://www.w3.org/2009/dap">Device APIs Working Group</a> have published a Working Draft of <a href="http://www.w3.org/TR/2013/WD-mediacapture-streams-20130516/">Media Capture and Streams</a>. This document defines a set of JavaScript APIs that allow local media, including audio and video, to be requested from a platform. Learn more about the <a href="http://www.w3.org/2007/uwa/">Ubiquitous Web Applications Activity</a>.</p>]]>
    </content>
</entry>

<entry>
    <title>Raw Socket API Draft Published</title>
    <link rel="alternate" type="text/html" href="http://www.w3.org/News/2013.html#entry-9821" />
    <id>tag:www.w3.org,2013://4.9821</id>

    <published>2013-05-14T14:31:08Z</published>
    <updated>2013-05-16T14:10:42Z</updated>

    <summary>The System Applications Working Group has published a Working Draft of Raw Socket API. This API provides interfaces to raw UDP sockets, TCP client sockets and TCP server sockets. Learn more about the Ubiquitous Web Applications Activity....</summary>
    <author>
        <name>W3C Staff</name>
    </author>
    
        <category term="Publication" scheme="http://www.sixapart.com/ns/types#category" />
    
        <category term="Web of Devices" scheme="http://www.sixapart.com/ns/types#category" />
    
    
    <content type="html" xml:lang="en" xml:base="http://www.w3.org/">
        
        <![CDATA[<p>The <a href="http://www.w3.org/2012/sysapps/">System Applications Working Group</a> has published a Working Draft of <a href="http://www.w3.org/TR/2013/WD-raw-sockets-20130514/">Raw Socket API</a>. This API provides interfaces to raw UDP sockets, TCP client sockets and TCP server sockets. Learn more about the <a href="http://www.w3.org/2007/uwa/">Ubiquitous Web Applications Activity</a>.</p>]]>
    </content>
</entry>

<entry>
    <title>Page Visibility is a W3C Recommendation</title>
    <link rel="alternate" type="text/html" href="http://www.w3.org/News/2013.html#entry-9820" />
    <id>tag:www.w3.org,2013://4.9820</id>

    <published>2013-05-14T13:49:40Z</published>
    <updated>2013-05-16T14:10:35Z</updated>

    <summary>The Web Performance Working Group has published a W3C Recommendation of Page Visibility. This specification defines a means for site developers to programmatically determine the current visibility state of the page in order to develop power and CPU efficient web...</summary>
    <author>
        <name>W3C Staff</name>
    </author>
    
        <category term="Browsers and Authoring Tools" scheme="http://www.sixapart.com/ns/types#category" />
    
        <category term="Publication" scheme="http://www.sixapart.com/ns/types#category" />
    
        <category term="Web Design and Applications" scheme="http://www.sixapart.com/ns/types#category" />
    
    
    <content type="html" xml:lang="en" xml:base="http://www.w3.org/">
        
        <![CDATA[<p>The <a href="http://www.w3.org/2010/webperf/">Web Performance Working Group</a> has published a W3C Recommendation of <a href="http://www.w3.org/TR/2013/REC-page-visibility-20130514/">Page Visibility</a>. This specification defines a means for site developers to programmatically determine the current visibility state of the page in order to develop power and CPU efficient web applications. Learn more about the <a href="http://www.w3.org/2006/rwc/">Rich Web Client Activity</a>.</p>]]>
    </content>
</entry>

<entry>
    <title>Four Drafts Published by the Web Applications Working Group</title>
    <link rel="alternate" type="text/html" href="http://www.w3.org/News/2013.html#entry-9819" />
    <id>tag:www.w3.org,2013://4.9819</id>

    <published>2013-05-14T13:39:32Z</published>
    <updated>2013-05-16T14:10:22Z</updated>

    <summary>The Web Applications Working Group has published four Working Drafts today: A Working Draft of Shadow DOM. This specification describes a method of establishing and maintaining functional boundaries between DOM trees and how these trees interact with each other within...</summary>
    <author>
        <name>W3C Staff</name>
    </author>
    
        <category term="Browsers and Authoring Tools" scheme="http://www.sixapart.com/ns/types#category" />
    
        <category term="Publication" scheme="http://www.sixapart.com/ns/types#category" />
    
        <category term="Web Design and Applications" scheme="http://www.sixapart.com/ns/types#category" />
    
    
    <content type="html" xml:lang="en" xml:base="http://www.w3.org/">
        
        <![CDATA[<p>The <a href="http://www.w3.org/2008/webapps/">Web Applications Working Group</a> has published four Working Drafts today:</p>
<ul class="show_items">
<li>A Working Draft of <a href="http://www.w3.org/TR/2013/WD-shadow-dom-20130514/">Shadow DOM</a>. This specification describes a method of establishing and maintaining functional boundaries between DOM trees and how these trees interact with each other within a document, thus enabling better functional encapsulation within the DOM.</li>
<li>A Working Draft of <a href="http://www.w3.org/TR/2013/WD-custom-elements-20130514/">Custom Elements</a>. This specification describes the method for enabling the author to define and use new types of DOM elements in a document.</li>
<li>A Working Draft of <a href="http://www.w3.org/TR/2013/WD-html-imports-20130514/">HTML Imports</a>. HTML Imports are a way to include and reuse HTML documents in other HTML documents.</li>
<li>A Group Note of <a href="http://www.w3.org/TR/2013/NOTE-WebIDL-Java-20130514/">Java language binding for Web IDL</a>. This document defines the Java language binding for Web IDL, the interface definition language for the Web platform.</li>
</ul>
<p>Learn more about the <a href="http://www.w3.org/2006/rwc/">Rich Web Client Activity</a>.</p>]]>
    </content>
</entry>

<entry>
    <title>CSS Box Alignment Module Level 3 Draft Published</title>
    <link rel="alternate" type="text/html" href="http://www.w3.org/News/2013.html#entry-9818" />
    <id>tag:www.w3.org,2013://4.9818</id>

    <published>2013-05-14T13:35:52Z</published>
    <updated>2013-05-16T14:10:14Z</updated>

    <summary>The Cascading Style Sheets (CSS) Working Group has published a Working Draft of CSS Box Alignment Module Level 3. This module contains the features of CSS relating to the alignment of boxes within their containers in the various CSS box...</summary>
    <author>
        <name>W3C Staff</name>
    </author>
    
        <category term="Publication" scheme="http://www.sixapart.com/ns/types#category" />
    
        <category term="Web Design and Applications" scheme="http://www.sixapart.com/ns/types#category" />
    
    
    <content type="html" xml:lang="en" xml:base="http://www.w3.org/">
        
        <![CDATA[<p>The <a href="http://www.w3.org/Style/CSS/members">Cascading Style Sheets (CSS) Working Group</a> has published a Working Draft of <a href="http://www.w3.org/TR/2013/WD-css3-align-20130514/">CSS Box Alignment Module Level 3</a>. This module contains the features of CSS relating to the alignment of boxes within their containers in the various CSS box layout models: block layout, table layout, flex layout, and grid layout. Learn more about the <a href="http://www.w3.org/Style/">Style Activity</a>.</p>]]>
    </content>
</entry>

<entry>
    <title>Requirements for Hangul Text Layout and Typography Draft Published</title>
    <link rel="alternate" type="text/html" href="http://www.w3.org/News/2013.html#entry-9817" />
    <id>tag:www.w3.org,2013://4.9817</id>

    <published>2013-05-14T13:34:42Z</published>
    <updated>2013-05-15T18:54:20Z</updated>

    <summary>The Internationalization Working Group has published a Working Draft of Requirements for Hangul Text Layout and Typography. This document describes requirements for general Korean language/Hangul text layout and typography realized with technologies like CSS, SVG and XSL-FO. The document is...</summary>
    <author>
        <name>W3C Staff</name>
    </author>
    
        <category term="Publication" scheme="http://www.sixapart.com/ns/types#category" />
    
        <category term="Web Design and Applications" scheme="http://www.sixapart.com/ns/types#category" />
    
    
    <content type="html" xml:lang="en" xml:base="http://www.w3.org/">
        
        <![CDATA[<p>The <a href="http://www.w3.org/International/core/">Internationalization Working Group</a> has published a Working Draft of <a href="http://www.w3.org/TR/2013/WD-klreq-20130514/">Requirements for Hangul Text Layout and Typography</a>. This document describes requirements for general Korean language/Hangul text layout and typography realized with technologies like CSS, SVG and XSL-FO. The document is mainly based on a project to develop the international standard for Korean text layout. Learn more about the <a href="http://www.w3.org/International/">Internationalization Activity</a>.</p>]]>
    </content>
</entry>

<entry>
    <title>Encrypted Media Extensions Draft Published</title>
    <link rel="alternate" type="text/html" href="http://www.w3.org/News/2013.html#entry-9813" />
    <id>tag:www.w3.org,2013://4.9813</id>

    <published>2013-05-10T14:14:00Z</published>
    <updated>2013-05-15T18:53:59Z</updated>

    <summary>The HTML Working Group has published a Working Draft of Encrypted Media Extensions. This proposal extends HTMLMediaElement providing APIs to control playback of protected content. See the blog post on this publication and learn more about the HTML Activity....</summary>
    <author>
        <name>W3C Staff</name>
    </author>
    
        <category term="Publication" scheme="http://www.sixapart.com/ns/types#category" />
    
        <category term="Web Design and Applications" scheme="http://www.sixapart.com/ns/types#category" />
    
    
    <content type="html" xml:lang="en" xml:base="http://www.w3.org/">
        
        <![CDATA[<p>The <a href="http://www.w3.org/html/wg/">HTML Working Group</a> has published a Working Draft of <a href="http://www.w3.org/TR/2013/WD-encrypted-media-20130510/">Encrypted Media Extensions</a>. This proposal extends HTMLMediaElement providing APIs to control playback of protected content. See the <a href='http://www.w3.org/QA/2013/05/perspectives_on_encrypted_medi.html'>blog post on this publication</a> and learn more about the <a href="http://www.w3.org/MarkUp/Activity">HTML Activity</a>.</p>]]>
    </content>
</entry>

<entry>
    <title>Two Touch Event Specifications Published</title>
    <link rel="alternate" type="text/html" href="http://www.w3.org/News/2013.html#entry-9812" />
    <id>tag:www.w3.org,2013://4.9812</id>

    <published>2013-05-09T20:31:27Z</published>
    <updated>2013-05-14T13:31:48Z</updated>

    <summary>Today, W3C published two independent specifications related to touch events. The Pointer Events Working Group has published the Pointer Events specification as a Candidate Recommendation. This specification unifies input from touch surfaces, mouse, and other devices into a single model...</summary>
    <author>
        <name>W3C Staff</name>
    </author>
    
        <category term="Publication" scheme="http://www.sixapart.com/ns/types#category" />
    
        <category term="Web of Devices" scheme="http://www.sixapart.com/ns/types#category" />
    
    
    <content type="html" xml:lang="en" xml:base="http://www.w3.org/">
        
        <![CDATA[<p>Today, W3C published two independent specifications related to touch events. The Pointer Events Working Group has published the <a href="http://www.w3.org/TR/2013/CR-pointerevents-20130509/">Pointer Events</a> specification as a Candidate Recommendation. This specification unifies input from touch surfaces, mouse, and other devices into a single model for ease, flexibility, and consistency of development. The Web Events Working Group also advances the earlier <a href="http://www.w3.org/TR/2013/PR-touch-events-20130509/">Touch Events version 1</a> specification to Proposed Recommendation. This specification standardizes an earlier model which works only for touch events. Comments on Touch Events welcome through 6 June.
Read more about the <a href="http://www.w3.org/2012/pointerevents/">Pointer Events Working Group</a> and the <a href="http://www.w3.org/2010/webevents/">Web Events Working Group</a>, and learn more about the <a href="http://www.w3.org/2006/rwc/Activity.html">Rich Web Clients Activity</a>.</p>]]>
    </content>
</entry>

<entry>
    <title>W3C Invites Implementations of HTML Media Capture</title>
    <link rel="alternate" type="text/html" href="http://www.w3.org/News/2013.html#entry-9811" />
    <id>tag:www.w3.org,2013://4.9811</id>

    <published>2013-05-09T17:35:49Z</published>
    <updated>2013-05-14T14:11:03Z</updated>

    <summary>The Device APIs Working Group invites implementation of the Candidate Recommendation of HTML Media Capture. The HTML Media Capture specification defines an HTML form extension that facilitates user access to a device&apos;s media capture mechanism, such as a camera, or...</summary>
    <author>
        <name>W3C Staff</name>
    </author>
    
        <category term="Publication" scheme="http://www.sixapart.com/ns/types#category" />
    
        <category term="Web Design and Applications" scheme="http://www.sixapart.com/ns/types#category" />
    
        <category term="Web of Devices" scheme="http://www.sixapart.com/ns/types#category" />
    
    
    <content type="html" xml:lang="en" xml:base="http://www.w3.org/">
        
        <![CDATA[<p>The <a href="http://www.w3.org/2009/dap/">Device APIs Working Group</a> invites implementation of the Candidate Recommendation of <a href="http://www.w3.org/TR/2013/CR-html-media-capture-20130509/">HTML Media Capture</a>. The HTML Media Capture specification defines an HTML form extension that facilitates user access to a device's media capture mechanism, such as a camera, or microphone, from within a file upload control. Learn more about the <a href="http://www.w3.org/2007/uwa/">Ubiquitous Web Applications Activity</a>.</p>]]>
    </content>
</entry>

<entry>
    <title>Selectors Level 4 Draft Published</title>
    <link rel="alternate" type="text/html" href="http://www.w3.org/News/2013.html#entry-9808" />
    <id>tag:www.w3.org,2013://4.9808</id>

    <published>2013-05-02T14:27:30Z</published>
    <updated>2013-05-14T13:30:35Z</updated>

    <summary>The Cascading Style Sheets (CSS) Working Group has published a Working Draft of Selectors Level 4. Selectors are patterns that match against elements in a tree, and as such form one of several technologies that can be used to select...</summary>
    <author>
        <name>W3C Staff</name>
    </author>
    
        <category term="Publication" scheme="http://www.sixapart.com/ns/types#category" />
    
        <category term="Web Design and Applications" scheme="http://www.sixapart.com/ns/types#category" />
    
    
    <content type="html" xml:lang="en" xml:base="http://www.w3.org/">
        
        <![CDATA[<p>The <a href="http://www.w3.org/Style/CSS/members">Cascading Style Sheets (CSS) Working Group</a> has published a Working Draft of <a href="http://www.w3.org/TR/2013/WD-selectors4-20130502/">Selectors Level 4</a>. Selectors are patterns that match against elements in a tree, and as such form one of several technologies that can be used to select nodes in an XML document. Selectors have been optimized for use with HTML and XML, and are designed to be usable in performance-critical code. They are a core component of CSS (Cascading Style Sheets), which uses Selectors to bind style properties to elements in the document. Selectors Level 4 describes the selectors that already exist in [SELECT], and further introduces new selectors for CSS and other languages that may need them. Learn more about the <a href="http://www.w3.org/Style/">Style Activity</a>.</p>]]>
    </content>
</entry>

<entry>
    <title>vCard Ontology Draft Published</title>
    <link rel="alternate" type="text/html" href="http://www.w3.org/News/2013.html#entry-9807" />
    <id>tag:www.w3.org,2013://4.9807</id>

    <published>2013-05-02T14:25:08Z</published>
    <updated>2013-05-14T13:30:30Z</updated>

    <summary>The Semantic Web Interest Group has published a Working Draft of vCard Ontology. The document describes a mapping of the vCard specification (RFC6350) to RDF/OWL. The goal is to promote the use of vCard for the description of people and...</summary>
    <author>
        <name>W3C Staff</name>
    </author>
    
        <category term="Publication" scheme="http://www.sixapart.com/ns/types#category" />
    
        <category term="Semantic Web" scheme="http://www.sixapart.com/ns/types#category" />
    
    
    <content type="html" xml:lang="en" xml:base="http://www.w3.org/">
        
        <![CDATA[<p>The <a href="http://www.w3.org/2001/sw/interest/">Semantic Web Interest Group</a> has published a Working Draft of <a href="http://www.w3.org/TR/2013/WD-vcard-rdf-20130502/">vCard Ontology</a>. The document describes a mapping of the vCard specification (RFC6350) to RDF/OWL. The goal is to promote the use of vCard for the description of people and organisations utilising semantic web techniques and allowing compatibility with traditional vCard implementations. Learn more about the <a href="http://www.w3.org/2001/sw/">Semantic Web Activity</a>.</p>]]>
    </content>
</entry>

<entry>
    <title>The PROV Family of Documents are W3C Recommendations</title>
    <link rel="alternate" type="text/html" href="http://www.w3.org/News/2013.html#entry-9805" />
    <id>tag:www.w3.org,2013://4.9805</id>

    <published>2013-04-30T14:01:06Z</published>
    <updated>2013-05-09T17:35:15Z</updated>

    <summary>The Provenance Working Group was chartered to develop a framework for interchanging provenance on the Web. The Working Group has now published the PROV Family of Documents as W3C Recommendations, along with corresponding supporting notes. You can find a complete...</summary>
    <author>
        <name>W3C Staff</name>
    </author>
    
        <category term="Publication" scheme="http://www.sixapart.com/ns/types#category" />
    
        <category term="Semantic Web" scheme="http://www.sixapart.com/ns/types#category" />
    
    
    <content type="html" xml:lang="en" xml:base="http://www.w3.org/">
        
        <![CDATA[<p>The <a href="http://www.w3.org/2011/prov/">Provenance Working Group</a> was chartered to develop a framework for interchanging provenance on the Web. The Working Group has now published the PROV Family of Documents as W3C Recommendations, along with corresponding supporting notes. You can find a complete list of the documents in the <a href="http://www.w3.org/TR/2013/NOTE-prov-overview-20130430/">PROV Overview Note</a>. PROV enables one to represent and interchange provenance information using widely available formats such as RDF and XML. In addition, it provides definitions for accessing provenance information, validating it, and mapping to Dublin Core. Learn more about the <a href="http://www.w3.org/2001/sw/">Semantic Web</a>.</p>
]]>
    </content>
</entry>

</feed>
