Community
Participate
Working Groups
ODIN technologies would like to recommend the addition of a new profile for Device Kit, the purpose of which is to allow monitoring of operating-system related status of the device. I will try to attach a first draft of a profile.xml to this bug.
Created attachment 74266 [details] First draft of a profile.xml for a new OS monitoring profile
Kevin thanks for the first draft of this profile. I had a few questions: 1. Is the firmware upgrade talking about the BIOS firmware of the box or the reader firmware? 2. I am a concerned about the ApplicationUpgrade. It seems like we have other ways of updating code on the box including OSGi. Why do we want to add yet another way to update code? 3. I not sure how this profile can be implemented remotely since most of the current reader protocols do not support these kind of functions. Is this profile only available on the local box? 4. Is ODIN going to open source any of the implementations of this profile?
1. Is the firmware upgrade talking about the BIOS firmware of the box or the reader firmware? RFID reader firmware. 2. I am a concerned about the ApplicationUpgrade. It seems like we have other ways of updating code on the box including OSGi. Why do we want to add yet another way to update code? We determined on the conference calls that the OSGi framework was sufficient for edgeware applications, therefore that function would not need to be included in the profile. 3. I not sure how this profile can be implemented remotely since most of the current reader protocols do not support these kind of functions. Is this profile only available on the local box? The intent would be to run on the device itself. 4. Is ODIN going to open source any of the implementations of this profile? ODIN does not intend to implement the profile at this time. Our intention is to involve a 3rd party such as Arcom.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.
