While the new client seems to use the same device data (which is also compatible with W3C recommendations) there is obviously no more compatibility with the W3C Specs like *org.w3c.ddr.simple.Service*
It may be old, but in a sense, those interfaces could be seen along the lines of JCP Standards like Servlets, etc. Maybe the old W3C spec is more "JSP" while the new approach is more "JSF". However, some of the current classes like *Device *or *Pattern *are mutable, which is not always appreciated by many APIs and frameworks[?] Most of the W3C types are also mutable, and feel somewhat like specialized Java Collections elements. Unless we really created a full drop-in replacement for the mandatory spec by W3C we could not call it "compatible" any more. I guess we have to decide if we want to offer that compatibility or not. If a combined client used the W3C API at least as a flavor or "plugin", then it also must have a working dependency to the W3C artifacts. Even if everything was in a single Maven module rather than smaller sub-modules (e.g. for file-based vs. other alternatives?[?]) Werner On Mon, Jul 7, 2014 at 4:28 PM, Werner Keil <[email protected]> wrote: > Btw. not sure if I created a separate task for that, or used the "Maven > repo" one piggy-back (especially while we could not assign particular > groups of tasks to certain people) but one thing we might want to improve > the visibility of the actual W3C Simple DDR artifacts in Maven. The most > recent release was exposed on GitHub, and I copied it to our "dist" > section, but ideally either that needs to be used by all subsequent build > steps or even deployed into a Maven repository (if there is no license > reason why it hasn't been put there yet) > > Werner > > On Mon, Jul 7, 2014 at 4:11 PM, Reza <[email protected]> > wrote: > >> So regarding the W3C simple ddr, thats close to the top of the task list >> for me (or anyone else who wants to help). >> >> Feel free to re-assign it, etc. >> >> I already stubbed out how its going to work: >> >> >> http://svn.apache.org/viewvc/incubator/devicemap/trunk/devicemap/java/classifier/src/main/java/org/apache/devicemap/DeviceMapW3CSimpleDDR.java?view=markup >> >> >> Basically, the W3C DDR interface will just wrap around the >> DeviceMapClient and provide all the W3C services as a wrapper. >> >> So my thoughts are that this project should just have 1 java API >> (client), which is the one I rewrote from scratch last year. The old ODDR >> client should be archived since no one can support it and it has a list of >> issues. >> >> >> ________________________________ >> From: Werner Keil <[email protected]> >> To: "[email protected]" < >> [email protected]> >> Sent: Monday, July 7, 2014 6:51 AM >> Subject: Re: Access >> >> >> >> Yes, assigned. If we can change assignment of tasks now, we should be >> able to address it. >> The "Simple DDR Java Client" and the "Classifier" are separate clients, I >> don't think we'd immediately merge them into one, at least not without >> losing W3C compatibility >> >> >> >> >> On Mon, Jul 7, 2014 at 12:03 PM, Bertrand Delacretaz < >> [email protected]> wrote: >> >> On Mon, Jul 7, 2014 at 11:59 AM, Werner Keil <[email protected]> >> wrote: >> >> Not sure, if some of us have admin or delegate right to JIRA tickets, >> as >> >> this one should probably be owned by me as the main user: >> >> https://issues.apache.org/jira/browse/DMAP-35 >> > >> >What do you mean by "owned"? If it's "assigned to" you should be able >> >to reassign, if Reza agrees. >> > >> >-Bertrand >> > >> > >
