Device Description Repository: Difference between revisions

Content deleted Content added
Removing link(s) to "Apache Mobile Filter": Article deleted per Wikipedia:Articles for deletion/Apache Mobile Filter. (TW)
Rescuing 1 sources and tagging 0 as dead.) #IABot (v2.0.9.5
 
(2 intermediate revisions by 2 users not shown)
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. [http://augur.io/ Augur] {{Webarchive|url=https://web.archive.org/web/20150702141341/http://augur.io/ |date=2015-07-02 }}).
* '''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 37:
*[[W3C]]
*[[Wurfl|WURFL]]
*Mobile device detection
*Apache Mobile Filter
 
==Notes==
Line 49 ⟶ 47:
*[http://www.w3.org/Mobile/Dev W3C MWI Developer resources]
*[http://www.openmobilealliance.org/ Open Mobile Alliance]
*[https://deviceatlas.com/device-data/devices DeviceAtlas Device Description Repository]
 
[[Category:World Wide Web Consortium standards]]