The Device Description Repository (DDR) is a concept proposed by the
Mobile Web Initiative Device Description Working Group (DDWG) of the
World Wide Web Consortium
The World Wide Web Consortium (W3C) is the main international standards organization for the World Wide Web. Founded in 1994 and led by Tim Berners-Lee, the consortium is made up of member organizations that maintain full-time staff working to ...
. The DDR is supported by a standard interface and an initial core vocabulary of device properties. Implementations of the proposed repository are expected to contain information about Web-enabled devices (particularly mobile devices). Authors of Web content will be able to make use of repositories to adapt their content to best suit the requesting device. This will facilitate the interaction and viewing of Web pages across devices with widely varying capabilities.
Information in a repository should include information such as the screen dimensions, input mechanisms, supported colors, known limitations, special capabilities etc.
Status
The "requirements for a single logical device descriptions repository" were first published as a W3C Working Draft in April 2006, and completed as a "Working Group Note" in December 2007.
The "DDR Core Vocabulary" was published in April 2008. It illustrates how to create definitions of properties that can be used in conjunction with the DDR Simple API.
The "DDR Simple API" specification was published as a
W3C Recommendation
The World Wide Web Consortium (W3C) is the main international standards organization for the World Wide Web. Founded in 1994 and led by Tim Berners-Lee, the consortium is made up of member organizations that maintain full-time staff working to ...
in December 2008.
The DDWG formally closed in December 2008. The Chair and volunteers agreed to maintain the DDWG home page and wiki after this time, to answer questions and encourage implementations.
Background
The idea of implementing a Device Description Repository was discussed at an international workshop held by the DDWG in Madrid, Spain in July, 2006. This resulted in a proposal to re-charter DDWG to work on the formal design of the programming interfaces, and ways to populate a repository with data and make this available to anyone who wanted to build Web servers that could adapt content to suit the end user devices.
Design goals
The architecture of the repository was not prescribed, but distributed solution are likely. In general, the desirable characteristics of a Device Description Repository are:
* Relevance of data. The
DDWG includes content adaptation specialists who have identified a core set of device properties that are useful for adaptation. Other groups are likely to refine this knowledge. Keeping the information up-to-date will also be a challenge.
* Ease of use. The interfaces should map easily to a variety of programming languages, and be as simple to use as other popular adaptation technologies (e.g
Augur.
* Ease of deployment. Existing technologies like
DNS
The Domain Name System (DNS) is a hierarchical and distributed naming system for computers, services, and other resources in the Internet or other Internet Protocol (IP) networks. It associates various information with domain names assigned to ...
show that global repositories can be deployed on a real-time basis. The W3C is unlikely to specify a particular server architecture. The DDWG has already identified a
Web Service interface (e.g.
SOAP
Soap is a salt of a fatty acid used in a variety of cleansing and lubricating products. In a domestic setting, soaps are surfactants usually used for washing, bathing, and other types of housekeeping. In industrial settings, soaps are use ...
) as a minimum requirement, and implementations are free to create the logic any way they wish (e.g.
relational database
A relational database is a (most commonly digital) database based on the relational model of data, as proposed by E. F. Codd in 1970. A system used to maintain relational databases is a relational database management system (RDBMS). Many relatio ...
queries) so long as the formal interface is supported.
* Assured interoperability. The varied nature of the Web requires that the repository interfaces and data formats can be supported by the largest number of Web technologies. Formal descriptions of
API
An application programming interface (API) is a way for two or more computer programs to communicate with each other. It is a type of software interface, offering a service to other pieces of software. A document or standard that describes how ...
s and Data Vocabularies will be necessary.
* Assured availability. If Web servers rely on device descriptions to provide adapted content, then these descriptions must be available at all times. Multiple repository hosts and support for data caching are likely to be part of the repository architecture.
* Efficiency. To ensure that the repository does not create unnecessary burden on scarce resources, the load should be distributed and data formats should be designed for simple processing.
* Industry support. The backing of organisations like W3C and the
Open Mobile Alliance
OMA SpecWorks, previously the Open Mobile Alliance (OMA) is a standards organization which develops open, international technical standards for the mobile phone industry. It is a nonprofit Non-governmental organization (NGO), not a formal govern ...
, and of vendors, service providers and device manufacturers will be critical.
The interface to the repository should provide the means of retrieving contextual information based on some evidence that identifies the context. Typically this means providing request headers through the interface and subsequently retrieving values for named properties. The W3C
DDWG produced an initial vocabulary of such properties (based on a formal ontology), and an interface for the retrieval functionality. The interface is designed in a language-neutral manner to enable many implementations on many platforms. The published specification includes samples in Java, IDL and WSDL.
Implementations
Open and commercial implementations of the DDR Simple API are available. Some of these formed part of the W3C's implementation report prior to the API becoming a Web standard. The W3C's Mobile Web Initiative also tracks implementations of relevant mobile standards and other developer resources, including the DDR Simple API.
On November 4, 2011 during Mobile2Days event
th
OpenDDRproject was launched. It is an open source project aiming to be the reference community implementation of W3C's DDR Simple API and the reference community repository.
In January 201
Apache DeviceMapbecame an incubating project at the Apache Software Foundation, and in September 2012 th
OpenDDRproject wa
donatedto Apache. After Apache DeviceMap had been archived in early 2017
OpenDDRwas made available again on
GitHub
GitHub, Inc. () is an Internet hosting service for software development and version control using Git. It provides the distributed version control of Git plus access control, bug tracking, software feature requests, task management, continuous ...
.
See also
*
UAProf
The UAProf (User Agent Profile) specification is concerned with capturing capability and preference information for wireless devices. This information can be used by content providers to produce content in an appropriate format for the specific ...
*
W3C
The World Wide Web Consortium (W3C) is the main international standards organization for the World Wide Web. Founded in 1994 and led by Tim Berners-Lee, the consortium is made up of member organizations that maintain full-time staff working to ...
*
WURFL
WURFL (Wireless Universal Resource FiLe) is a set of proprietary application programming interfaces (APIs) and an XML configuration file which contains information about device capabilities and features for a variety of mobile devices, focused ...
Notes
{{Reflist, 2
External links
Device Description Working Group (DDWG)DDWG Workshop on the implementation of a DDRW3C Mobile Web Initiative (MWI)W3C MWI Developer resourcesOpen Mobile AllianceDeviceAtlas Device Description Repository
World Wide Web Consortium standards