You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@devicemap.apache.org by "eberhard speer jr." <se...@ducis.net> on 2014/07/06 13:15:21 UTC
Release
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
I got Reza's mail via 'that other email address' because still/again
having issues receiving mail ex-Apache.org and Reza's email still
appears with "INVALID" appended.
Also tried to log on, went to id.apache.org -- works -- but still do
not have access to the jira and other things.
I understand about security etc...but turning access into an obstacle
course...still dizzy from the hoops I had to jump thru to get Wiki
access...
I'll get busy on the .Net version. It looks like the 1.0 version is
'just' is much more 'Java'-ish [I see the dreaded "Factory" word] and
the added loaders.
I noticed the 1.0 resources do not add any new devices or properties,
so the changes are in the builder-tokens. Running the Big Tests to
compare and results ASAP...
esjr
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.8 (MingW32)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQEcBAEBAgAGBQJTuS/JAAoJEOxywXcFLKYcm8kIANEsblSycmEeWTXPDEouOyci
y/K43dgkDfbql5+135rzi+JubmKuP6runi+GCaVX8E9AvOBvGZ5/JWXu3qJdTeGY
qRa9Nwzsp0pXNIQzy8xW16Ag7I/pr+R0/4AxBq8wmaUIiMTI/99UW+ktCi8XCfIw
7pqhaYuHFBpUVlHSulPebl+cXukTw5l2fM4Qpm06TySDrEuFAhCwpzC8TexjLzeI
LhGcAo+3vu4blPoRf4aLCJ82PKpptfyaC/IqHeRaPglwagUmp/Q7tpF7C34XxmMf
QF7kvkGffNVaa1sEz+GS8M3QCkRFcCLjbhuTD9yTAuSwtZuwXV07HNDeAiuCt1g=
=0Skv
-----END PGP SIGNATURE-----
Re: Access
Posted by Werner Keil <we...@gmail.com>.
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 <we...@gmail.com> 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 <re...@yahoo.com.invalid>
> 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 <we...@gmail.com>
>> To: "devicemap-dev@incubator.apache.org" <
>> devicemap-dev@incubator.apache.org>
>> 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 <
>> bdelacretaz@apache.org> wrote:
>>
>> On Mon, Jul 7, 2014 at 11:59 AM, Werner Keil <we...@gmail.com>
>> 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
>> >
>>
>
>
Re: W3C Simple DDR (was Access)
Posted by Reza <re...@yahoo.com.INVALID>.
ok, I think I understand. I will review the API and see how best to integrate it and expose it.
________________________________
From: Werner Keil <we...@gmail.com>
To: Reza <re...@yahoo.com>
Sent: Monday, July 7, 2014 10:40 AM
Subject: Re: W3C Simple DDR (was Access)
It is the actual "org.w3c.*" DDR Simple API that our Java libraries (especially "devicemap-ddr-simple") implement.
You may have noticed at least one Maven module currently disabled in the POM because this API is not available anywhere. OpenDDR so far suggested to manually install it into a local Maven repo, but that is rather inconvenient.
Few W3C APIs like some "CSS" related stuff made their way into MavenCentral, this one I assume was finalized too early for Maven to be widely used around 2008, or W3C simply didn't care?
On Mon, Jul 7, 2014 at 4:34 PM, Reza <re...@yahoo.com> wrote:
>> improve the visibility of the actual W3C Simple DDR artifacts in Maven
>
>
>Can you explain what this is? It is just a reference API? How is this different than building W3C Simple DDR compatibility and support in the Java API?
>
>
>
>________________________________
> From: Werner Keil <we...@gmail.com>
>To: "devicemap-dev@incubator.apache.org" <de...@incubator.apache.org>; Reza <re...@yahoo.com>
>Sent: Monday, July 7, 2014 10:28 AM
>Subject: Re: Access
>
>
>
>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 <re...@yahoo.com.invalid> 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 <we...@gmail.com>
>>To: "devicemap-dev@incubator.apache.org" <de...@incubator.apache.org>
>>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 <bd...@apache.org> wrote:
>>
>>On Mon, Jul 7, 2014 at 11:59 AM, Werner Keil <we...@gmail.com> 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
>>>
>
>
>
Re: Access
Posted by Werner Keil <we...@gmail.com>.
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 <re...@yahoo.com.invalid> 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 <we...@gmail.com>
> To: "devicemap-dev@incubator.apache.org" <
> devicemap-dev@incubator.apache.org>
> 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 <
> bdelacretaz@apache.org> wrote:
>
> On Mon, Jul 7, 2014 at 11:59 AM, Werner Keil <we...@gmail.com>
> 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
> >
>
Re: Access
Posted by Reza <re...@yahoo.com.INVALID>.
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 <we...@gmail.com>
To: "devicemap-dev@incubator.apache.org" <de...@incubator.apache.org>
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 <bd...@apache.org> wrote:
On Mon, Jul 7, 2014 at 11:59 AM, Werner Keil <we...@gmail.com> 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
>
Re: Access
Posted by Werner Keil <we...@gmail.com>.
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 <bdelacretaz@apache.org
> wrote:
> On Mon, Jul 7, 2014 at 11:59 AM, Werner Keil <we...@gmail.com>
> 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
>
Re: Access
Posted by Bertrand Delacretaz <bd...@apache.org>.
On Mon, Jul 7, 2014 at 11:59 AM, Werner Keil <we...@gmail.com> 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
Re: Access
Posted by Werner Keil <we...@gmail.com>.
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
It's related to the "W3C Simple DDR" client derived and donated by OpenDDR.
I did some significant part already before JavaLand, the result now exists
under "Java", the "contrib" one can be seen as historical snapshot if you
want.
Werner
On Mon, Jul 7, 2014 at 11:07 AM, Bertrand Delacretaz <bdelacretaz@apache.org
> wrote:
> On Mon, Jul 7, 2014 at 10:24 AM, eberhard speer jr. <se...@ducis.net>
> wrote:
> > ...Done : user name : esjr....
>
> Ok you should now have access to
> https://issues.apache.org/jira/browse/DMAP in the PMC member role.
>
> -Bertrand
>
Re: Access
Posted by Bertrand Delacretaz <bd...@apache.org>.
On Mon, Jul 7, 2014 at 10:24 AM, eberhard speer jr. <se...@ducis.net> wrote:
> ...Done : user name : esjr....
Ok you should now have access to
https://issues.apache.org/jira/browse/DMAP in the PMC member role.
-Bertrand
Re: Access
Posted by "eberhard speer jr." <se...@ducis.net>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Done : user name : esjr
esjr
> Hi,
>
> On Mon, Jul 7, 2014 at 10:12 AM, eberhard speer jr.
> <se...@ducis.net> wrote:
>> ...I'm afraid I cannot log on to Jira using my Apache user name
>> [esjr] and password...
>
> You need to create an account at https://issues.apache.org and tell
> us the username so we can give you full access.
>
> -Bertrand
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.8 (MingW32)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQEcBAEBAgAGBQJTullKAAoJEOxywXcFLKYc6zQIALUk3r2AIGV49zgfCATuxP9E
yiruAn7ua6XAQtKAxir4s5YLsxEwIkiXHefjnjPc/gNIrYKGepOMT6vaExcawfcS
sDZaP6KLnXo3jMi6BnOv/Wpd7Ii3TR6/6+tukeVGmpBFkccfdfvubcxb3ULX76ty
xABFr0VLI/2Ycc8V9Ib2Ulxdetmc+Ee+3wfvm+KnemS2x8Nj8uemCUz0ML8cET9K
mCfa7IxtOswYtC57EXhFgv7HzM+wpmKAZHIRVRLWASwbdLiaM2kq3pajYpY4TrYy
r3//V+n0gvGbJayEFGwJHMlKh3yZhoEL1pYGEt3nrdd+gJWz0nipYY4joYG7c0k=
=DDYR
-----END PGP SIGNATURE-----
Re: Access
Posted by Bertrand Delacretaz <bd...@apache.org>.
Hi,
On Mon, Jul 7, 2014 at 10:12 AM, eberhard speer jr. <se...@ducis.net> wrote:
> ...I'm afraid I cannot log on to Jira using my Apache user name [esjr]
> and password...
You need to create an account at https://issues.apache.org and tell us
the username so we can give you full access.
-Bertrand
Access
Posted by "eberhard speer jr." <se...@ducis.net>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I'm afraid I cannot log on to Jira using my Apache user name [esjr]
and password.
Thanks,
esjr
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.8 (MingW32)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQEcBAEBAgAGBQJTulZiAAoJEOxywXcFLKYcogEH+wcFvo92AfsfsI0OBEjb1B8f
mskWT/XbXMb0cx7BIswTlcxRAHKQq7QDI+401sZpSZeVng1xCUvHC69fb9ScBrer
wMzMymPaLjpQfztktoybQhMe6Z7jv2WTXlXEnoVW5AKkh+Viq/ZLHrVe6q59HoYl
FN7vYxjdkjfnU9VpQRanlDC8sAThnsFUCr1h5ZBWDriKdwdveiJQnMJqi1r9mtjG
8BUYDLrGq2ubs0z0WGMgbUp4SBrdNtWY4NsY4ugTuvDCf1r+sux9cZt8Qm0Rt0Zc
I/QqUWUena2lpA6sGg5b8cU/zekuNUcab3GbqZ3iIJkNsycNYMNrKJkhpC/8gAI=
=EQjc
-----END PGP SIGNATURE-----
Re: Release
Posted by Bertrand Delacretaz <bd...@apache.org>.
On Sun, Jul 6, 2014 at 1:15 PM, eberhard speer jr. <se...@ducis.net> wrote:
> ...Also tried to log on, went to id.apache.org -- works -- but still do
> not have access to the jira and other things....
What exactly don't you have access to, and what's your jira username?
-Bertrand
RE: Release
Posted by Reza <re...@yahoo.com.INVALID>.
Other than some pattern cleanups and generic pattern fallbacks, I synced to the latest ODDR which had a handful of new devices:<br/><br/>https://github.com/OpenDDRdotORG/OpenDDR-Resources/commit/31bfd07dab5aa007b048c6199ee9c313881d7986<br/><br/>As for the yahoo email issue, its known, check out the 2nd post:<br/><br/>https://blogs.apache.org/infra/ <a href="https://overview.mail.yahoo.com?.src=iOS"><br/><br/>Sent from Yahoo Mail for iPad</a>