Without W3C compatibility the 1.0.0 release is useless to most people, the Simple DDR API IS the 1.0.0 release that has been ready for over 1.5 years now, it just wasn't bothered to be tagged by anybody[?]
IMHO the "new client" is a good effort towards a 1.x release, just look at Tomcat 3-8 and how it graduated, but the W3C DDR API is neither dead nor outdated. Not sure about MaDDR (it is not accessible here behind the firewall) but just visit the site of the clear market leader in this area DeviceAtlas what it states about W3C compatibility: https://deviceatlas.com/resources/general >The API software is not updated very frequently, we want to make sure that the load on developers is as low as possible. The JSON file is updated daily. explains why e.g. the W3C Simple DDR API may not undergo as many changes here at DeviceMap either. The "JSON file" is the equivalent to our XML files, I don't see we'd update that on a daily basis, so instead of creating a "fork" of the W3C API maybe we should focus on what really matters, MAINTAINING device data[?] Werner On Wed, Jul 9, 2014 at 5:18 PM, Reza <[email protected]> wrote: > I agree. I would like to spend some time researching w3c support for the > java client. I have not had anytime to do this since I have been focusing > on getting our 1.0.0 release ready. > > It seems that Werner is trying to focus on the legacy oddr java client, > not sure how that helps this research effort out other than causing mass > confusion... > > > ________________________________ > From: eberhard speer jr. <[email protected]> > To: [email protected] > Sent: Wednesday, July 9, 2014 10:48 AM > Subject: W3C > > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Reza, > > my .Net implementations of the W3C interface are ready and like you > the questions I'm now facing is how to integrate. > Maybe we should bounce around some ideas and coordinate the > integration to the extent our respective 'platforms' allow ? > > esjr > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.8 (MingW32) > Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ > > iQEcBAEBAgAGBQJTvVYlAAoJEOxywXcFLKYciGwIAJfHGpUzpdwkm6DGmTuedzRE > vSVLG0LFcgrjvWyMMvJHN8s7R30eb/yubVZWAk28dz53SaG+HKznJP8r9b2nMwnA > CeAB/nz0/jQ09HlF59ycFhHPJPLBHl8SEcRniay1Y02c55Pnr06i9r9eVmumIjnu > 47+J6dBGVxyUH4ShbeHcOxA2JuCPSB4jasESF2jFaG0fUwbODVabSV7wPIMMaY8I > 2G6mQKBKl211xvNZtm4QnO0yZ9ak1Kx7CPN+z0x5thq4HDKDbM1AcIV4L0Q80VlX > Hb881GzQInDOsY9VK6zzFTUHtQtmNUX/QhLRpNiKweoPKQLMtwC9zaHrKzm04Kw= > =Pefu > -----END PGP SIGNATURE----- >
