Category: News

Tuesday, June 24th 2008

Permalink 10:37:52, Categories: News

DDR Simple API implemented successfully

It has been a while since DDWG reported, because the group has been busy dealing with technical comments on the draft API that was published several weeks ago. Comments were managed in public, and mainly they were addressed by providing additional clarity and a few adjustments to the text. Since completing this work, the group has attended a face-to-face meeting in France where several successful implementations were demonstrated. The implementation report summarises the results, which show that all of the API features are viable. The successful implementation by several independent contributors will go a long way to progressing this specification towards being a W3C Recommendation. If you are interested in implementing it yourself, check out the latest stable version. There's a pretty picture of the API on the DDWG home page.
Rotan Hanrahan

Wednesday, April 9th 2008

Permalink 07:45:34, Categories: News

DDR Simple API published

The W3C MWI Device Description Working Group has published the First Public and Last Call Working Draft of Device Description Repository Simple API. Web content delivered to mobile devices usually benefits from being tailored to take into account a range of factors such as screen size, markup language support and image format support. Such information is stored in "Device Description Repositories" (DDRs). This document describes a simple API for access to DDRs, in order to ease and promote the development of Web content that adapts to its Delivery Context. Comments are welcome through 1 May. The document includes links to Java and JavaDoc for the API, and also IDL and WSDL are provided. Additional implementation languages will be demonstrated via the DDWG home page in due course. On behalf of the DDWG Rotan Hanrahan Chair
Rotan Hanrahan

Wednesday, February 27th 2008

Permalink 20:11:44, Categories: News

Coming soon: The DDR Simple API

The two weeks leading up to the DDWG face-to-face in Seoul, Korea, have been very busy, and much of it is still playing out on the public mailing list. In the conference call on the 18th, there was much discussion on the role of the Property Name and whether the aspect should be a part of that name. A week later and we have an API where the Property Name and aspect are seen separately. They can be combined in a property reference, where the namespace of the aspect is determined in the vocabulary to which the aspect is applied. Together with evidence representing HTTP headers, this data can be used in a query to retrieve contextual information from a DDR. For those who have not been following closely, an 'aspect' is a qualifying term that can accompany a property name, so that it is clear which part of the delivery context the property refers. If, for example, you have a "pixelWidth" property and you use it in a hardware aspect then you would be referring to the physical width of the screen (in pixels). In a browser aspect this property would refer to the window width. In an image aspect it would be the width of the image. And so on. The Simple API permits default aspects to be used. A vocabulary of properties may include aspects too, and this is an approach likely to be used by default in the Simple API. Of course, the devil is in the details, and much still remains to be decided. The issues include: factory methods, exceptions, constants, convenience methods (that use general string parameters) and robust methods (that use specific typed parameters). Keeping the typical programming languages of the Web in mind is also challenging. Where noted, certain approaches will be avoided if binding to a particular popular language poses a problem. To keep all this work concrete, the group is using Java as an example binding. Even this has run into some concerns as Java 1.4 has been deprecated. Other bindings will also be prepared. Next week, with Seoul being the hub of two days of face-to-face work, a final editors’ draft of the API should be completed. This version will be known as the "Simple API", recognising that this has been designed for easy adoption in the most common use case, that of adapting content for delivery to mobile devices on the Web. The official First Public Working Draft will come directly from this editors' draft, and it is hoped that the FPWD can move efficiently on the path towards a formal Recommendation as soon as possible. Several implementations have already been promised. An editors draft of the Java binding can be viewed online while all this is happening. Comments are always welcome via the public mailing list.
Rotan Hanrahan

Friday, November 2nd 2007

Permalink 10:51:07, Categories: News

New DDWG publications

It has just been announced on the DDWG public mailing list that revisions of two of the group's documents have been published: The first versions of these documents appeared about two years ago. The new updates fill in the gaps. If you are wondering why the DDWG is doing what it is doing, these documents will help you understand.
Rotan Hanrahan

Sunday, September 16th 2007

Permalink 19:10:38, Categories: News

DDWG blog activity

It has been an interesting time on the DDWG blog. As you know, this is the blog where regular updates on ongoing DDWG work. It is available to anyone who would prefer not to be signed up to the public mailing list. Of course, you can always view the various archives to see what has transpired, or visit the wiki to see some of the latest technical work. So why has it been interesting on the blog? Mainly because it has attracted some attention. Unfortunately, not the right kind of attention. The blog is generally open to comments, but to date the only substantial comments to be received have come via the tried-and-trusted public mailing list. The blog comments, almost 100% of them, are spam. The DDWG blog is monitored and moderated, so none of this spam is getting through to our readers. We may have to disable commenting in light of the rise in spam, but rest assured that the public mailing list will remain available. Meanwhile, further updates on recent meetings are on their way.
Rotan Hanrahan

:: Next Page >>