Device Description Repository: Difference between revisions

Browse history interactively

← Previous edit

Content deleted Content added

VisualWikitext

Revision as of 11:55, 22 September 2016 edit David Gerard (talk \| contribs) Edit filter managers, Extended confirmed users 214,589 edits Removing link(s) to "Mobile device detection": rm redlink (deleted). (TW) ← Previous edit		Latest revision as of 13:33, 29 January 2024 edit undo InternetArchiveBot (talk \| contribs) Bots, Pending changes reviewers 5,694,701 edits Rescuing 1 sources and tagging 0 as dead.) #IABot (v2.0.9.5
(8 intermediate revisions by 5 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 30: ==Implementations== Open and commercial implementations of the DDR Simple API are available. Some of these formed part of the W3C's implementation report<ref>{{cite web\|title=DDR Simple API Implementation Report\|url=http://www.w3.org/2005/MWI/DDWG/drafts/api/test-report.html\|date=June 19, 2008\|publisher=W3C (MIT, ERCIM, Keio)\|accessdate=2008-12-12}}</ref> 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 ~~the~~November ~~4th of November~~4, 2011 during Mobile2Days event<ref>{{cite web\|title=Mobile2Days Agenda 2011\|url=http://2011.java2days.com/wp-content/uploads/2011/11/Agenda-2011.pdf\|date=November 4, 2011\|publisher=Java2Days\|accessdate=2011-11-04}}</ref> the [[http://openddr.mobi OpenDDR]] project 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 2012 [http://~~incubator~~devicemap.apache.org~~/devicemap~~/ Apache DeviceMap] became an incubating project at the Apache Software Foundation, and in September 2012 the [[http://openddr.mobi OpenDDR]] project was [https://issues.apache.org/jira/browse/DMAP-11 donated] to Apache. After Apache DeviceMap had been archived in early 2017, [http://openddr.mobi OpenDDR] was made available again on [[GitHub]]. ==See also== 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]]