XRD is a simple generic format for describing resources. Unlike past attempts, this time we got it right, and truly deliver on the promise of simple. In fact, the XRI TC spent the past year throwing features out if they were not supported by well-established use cases. Last month the specification reached the important milestone of a Committee Draft and was opened for public comments.While public review is open until January 6th (and we encourage feedback), we decide to publish a new working draft to address comments we already reach consensus on to help early adopters. The new draft, which the TC feels would be our last schema change, addresses all the comments received so far, but focuses on two comments:
- The use of a new structure for the <Link> element and its deviation from common practice (i.e. ATOM, HTML, XHTML).
- The limited and confusing nature of the <Type> element.
The new draft converts most of the <Link> child elements to attributes, and replaces the <Type> element with a <Property> element capable of expressing key/value pairs. I would like to thanks DeWitt Clinton and James Manger for their useful feedback.
An example XRD (updating the previous sneak-peak):
<?xml version='1.0' encoding='UTF-8'?> <XRD xmlns='http://docs.oasis-open.org/ns/xri/xrd-1.0'> <Subject>http://blog.example.com/article/id/314</Subject> <Alias>http://blog.example.com/cool_new_thing</Alias> <Expires>2010-01-30T09:30:00Z</Expires> <Property type='http://blgx.example.net/ns/version'>1.2</Property> <Property type='http://blgx.example.net/ns/ext'>lang</Property> <Link rel='author' type='text/html' href='http://blog.example.com/author/steve'> <Title xml:lang='en-us'>Author Information</Title> </Link> </XRD>
Liked this post? Follow this blog to get more.