Device Description Repository: Difference between revisions

Revision as of 07:03, 18 April 2014

Revision as of 10:35, 9 May 2014

Line 19:

* '''Relevance of data'''. The [[W3C Device Description Working Group|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. [https://deviceatlas.com DeviceAtlas] [[Wurfl|WURFL]] or [[OpenDDR]]).

* '''Ease of deployment'''. Existing technologies like [[Domain name system|DNS]] 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 services|Web Service]] interface (e.g. [[SOAP]]) as a minimum requirement, and implementations are free to create the logic any way they wish (e.g. [[RDBMS|relational database]] 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]]s and Data Vocabularies will be necessary.

Line 39:

*[[UAProf]]

*[[W3C]]

*[https://deviceatlas.com/ DeviceAtlas]

*[[Wurfl|WURFL]]

*[[Mobile device detection]]