devicemap-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Werner Keil <werner.k...@gmail.com>
Subject Re: Rename /clients/w3c-ddr to /clients/w3c?
Date Tue, 14 Jul 2015 10:13:16 GMT
Eberhard,

Happy to hear what you plan on the .NET side once the JSON structure exists.

Are you still in Greece btw.?
How are things?
Germany and Germans don't seem too popular there these days;-|

Werner

On Tue, Jul 14, 2015 at 1:02 AM, Werner Keil <werner.keil@gmail.com> wrote:

> Glad to see so many care about W3C standards After all or pay tribute to
> the fact, that people check it out or use it ;-)
> And e.g. Stefan's recent input also indicates they do.
> Other than both being W3C standards that deal with Device Information they
> are not directly related. Some of the W3C DDR Spec is more precise, e.g.
> Standard vocabularies, which is why both will likely help Portlet Device
> optimization.
> Am 14.07.2015 00:47 schrieb "eberhard speer jr." <seshat@ducis.net>:
>
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> - -1
>>
>> I agree with Reza.
>>
>> My 2 cents on 2.0 to follow ASAP
>>
>> esjr
>>
>>
>> On 2015-07-13 22:28, Werner Keil wrote:
>> > All,
>> >
>> > Would anybody object if the /clients/w3c-ddr and /examples/w3c-ddr
>> > folders are renamed to /clients/w3c and /examples/w3c?
>> >
>> > We could do a formal vote if that seems necessary, but after an
>> > initial modularization and e.g. Reza's reply just earlier, it feels
>> > safe to assume these 2 folders are of concern only to a few while a
>> > few others work in different areas.
>> >
>> > As mentioned, work in the Apache Portals project and JSR 362 EG
>> > brought up CC/PP support because this (W3C) standard is already
>> > supported by the Portlet standard since 2.0. Just like DDR it is
>> > another W3C standard, so while adding an extra /clients/w3c-ccpp
>> > folder was possible, I would prefer putting W3C projects under a
>> > folder common to all of them.
>> >
>> > As there are no Jenkins builds other than /data there should be no
>> > impact on existing build scripts either.
>> >
>> > WDYT? Werner
>> >
>>
>> -----BEGIN PGP SIGNATURE-----
>> Version: GnuPG v2.0.22 (MingW32)
>>
>> iQEcBAEBAgAGBQJVpD/+AAoJEOxywXcFLKYc4loIAJ9Vy5JEYIJmOKNQ0H+DErDE
>> Fpw8dhDJrwRxBuO2Z3mESPmCFiV12FrEvJ4hO6hc9yietPs5nG7cM3/WjItDRT8o
>> Gp7Pcn75q+t3PjLoJmFHMP8l0P7pPlyLAHS9dkO1ApetZsj9hEIzknkMylTMxQTH
>> XPouAyWC0gxSikgGFMLYpV/z8KqPsPND0H/WwKosf+4urThEXghwtRRW9+00pFgT
>> Di6qQe0BgNuRgBBfvLF8o01dvpLxleWBizGcQIbL0I7bEFVfV6mwi6evwSR2Qd7Q
>> 7nZIYE3DyVToibk+loar7OSfQ+2EtoSIeI2Pr+AkMnHlcXSbQrkr0Rxx8LZJRbg=
>> =SQ+w
>> -----END PGP SIGNATURE-----
>>
>>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message