[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [m2m-iwg] Two Questions on OMA if I may
|
Julien/Tam/all,
Thanks for bringing that up. To be quite frank, fellow members in the Java Embedded Standard Expert Groups for Mobile/Embedded I spoke to (some represent World Leaders in M2M like Gemalto/Cinterion) did not feel. OMA DM was still relevant these days. If they changed their mind, or Apache DeviceMap co-contributors including its project lead Bertrand felt,OMA DM had any relevance to the DeviceMap project (based mainly around W3C DDR, OMA was involved, and especially Device Capabilities ARE something DDR projects like DeviceMap can also help with)
Until recently Oracle's Java Embedded SDK contained a W3C incomplient and now closed source proprietary repository called WURFL. Almost every sane member of the community, especially those who believe in True Open Source abandon WURFL, because its license and pricing models are hilariously over-exagerated (asking license fees of 10 or 25.000$ or more for information the very OMA and its members as well as trusting members of the former community provided before they locked those away or should one call it steal from those contributors and see OMA more rightful owners of such information)
Oracle also dropped it, but their official reason was that retrieving device capabilities from the device itself (kind of like systems like PhoneGap/Cordova do) was more in their favor and currently a central Device Management feature was also not of interest to Java ME Embedded.
If there is anybody in the DeviceMap community who feels. OMA DM was of interest and worth looking at, Mike Milinkovich would also be welcome to speak with Bertrand and those DeviceMap committers and interested partiees who meet in Zurich. For schedule reasons this won't be the same day as Eclipse Stammtisch, but probably the day before, May 14th. If Mike can make it, he'd be welcome to represent Eclipse and the IWG in such discussion.
Cheers,
Werner
On Wed, Apr 24, 2013 at 8:00 PM,
<m2m-iwg-request@xxxxxxxxxxx> wrote:
Send m2m-iwg mailing list submissions to
m2m-iwg@xxxxxxxxxxx
To subscribe or unsubscribe via the World Wide Web, visit
http://dev.eclipse.org/mailman/listinfo/m2m-iwg
or, via email, send a message with subject or body 'help' to
m2m-iwg-request@xxxxxxxxxxx
You can reach the person managing the list at
m2m-iwg-owner@xxxxxxxxxxx
When replying, please edit your Subject line so it is more specific
than "Re: Contents of m2m-iwg digest..."
Today's Topics:
1. Two Questions on OMA if I may.... (Tam, Mimi K)
2. Re: Two Questions on OMA if I may.... (Julien Vermillard)
----------------------------------------------------------------------
Message: 1
Date: Wed, 24 Apr 2013 08:45:15 -0400
From: "Tam, Mimi K" <mimi.tam@xxxxxxxxxxx>
To: "m2m-iwg@xxxxxxxxxxx" <m2m-iwg@xxxxxxxxxxx>
Cc: "mimi.tam@xxxxxxxx" <mimi.tam@xxxxxxxx>
Subject: [m2m-iwg] Two Questions on OMA if I may....
Message-ID:
<9E95D92A6FE6D644AD42428C72C4B7C0FC7E48CC@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
Content-Type: text/plain; charset="us-ascii"
Hi folks,
I venture to post these 2 questions on this email list because of the OMA DM simulator that I read about for the Koneki project. I hope someone can provide me with some info on this.
My questions are:
What is OMA's standard way to get the hardware profile (e.g. what kind of board, whether there is a USB, serial port, etc; protocols that it supports, whether there is a camera, GPS, etc. - i.e. hardware (device) capabilities)) from OEM's who know the hardware manifest.
What is OMA's standard way of handling multiple configurations (e.g. sensor config) for a certain type of hardware? Which OMA protocol will provide the conversation between the OMA DM and the Enterprise App that is talking to the hardware? Would it be the OMA Client-side API Framework? If so, what is the mechanism for OMA to query and get the hardware configs from the board itself?
Hope my questions are somewhat clear.
Many Thanks...Mimi
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://dev.eclipse.org/mailman/private/m2m-iwg/attachments/20130424/213280eb/attachment.html>
------------------------------
Message: 2
Date: Wed, 24 Apr 2013 17:44:24 +0200
From: Julien Vermillard <jvermillard@xxxxxxxxx>
To: m2m Industry Working Group <m2m-iwg@xxxxxxxxxxx>
Subject: Re: [m2m-iwg] Two Questions on OMA if I may....
Message-ID:
<CAN9CcB-H1N-Jn0W53jMyijgrfW5fCg1wxQ1Q6EJ8sRuoTsOuKA@xxxxxxxxxxxxxx>
Content-Type: text/plain; charset="iso-8859-1"
On Wed, Apr 24, 2013 at 2:45 PM, Tam, Mimi K <mimi.tam@xxxxxxxxxxx> wrote:
> Hi folks,****
>
> ****
>
> I venture to post these 2 questions on this email list because of the OMA
> DM simulator that I read about for the Koneki project. I hope someone can
> provide me with some info on this.****
>
> ****
>
> My questions are:****
>
> ****
>
> What is OMA's standard way to get the hardware profile (e.g. what kind of
> board, whether there is a USB, serial port, etc; protocols that it
> supports, whether there is a camera, GPS, etc. - i.e. hardware (device)
> capabilities)) from OEM's who know the hardware manifest.****
>
> ****
>
> What is OMA's standard way of handling multiple configurations (e.g.
> sensor config) for a certain type of hardware? Which OMA protocol will
> provide the conversation between the OMA DM and the Enterprise App that is
> talking to the hardware? Would it be the OMA Client-side API Framework? If
> so, what is the mechanism for OMA to query and get the hardware configs
> from the board itself?****
>
> ****
>
> Hope my questions are somewhat clear.****
>
> ****
>
> Many Thanks...Mimi****
>
> ** **
>
Hi Mimi,
I don't know exactly the answer to your question, but the OMA standardized
some object in the standard tree.
You can find the different specifications here :
http://technical.openmobilealliance.org/Technical/release_program/dm_v1_2.aspx
Perhaps one will fits your need.
Julien
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://dev.eclipse.org/mailman/private/m2m-iwg/attachments/20130424/86e41bc7/attachment.html>
------------------------------
_______________________________________________
m2m-iwg mailing list
m2m-iwg@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/m2m-iwg
End of m2m-iwg Digest, Vol 18, Issue 21
***************************************
