On 08/03/2011 03:30 AM, Romain KUNTZ wrote:
Hello Josef,
I'm also interested in the definition of an in-vehicle API. Before defining the
details of such an API, I'd be interested in discussing a more high-level
classification.
First, we should define who would be the API users? I believe the definition of
the API will fall into multiple categories depending on who would use it. For
example :
- car manufacturer& Tier-1 suppliers who would be able to access/write
critical information (e.g. for diagnostic / information collection purposes),
- affiliated developers (e.g. the ones providing applications shipped with the
head-unit, which would need raw information such as the ones for GPS dead
reckoning),
- "any" developper (which may need already processed information).
Some of the API might not be available to all of the actors, or read/write
access may be different for each of them.
That being said, access control would be an important part of the system. I'm
not sure yet how that could be achieved but it must be kept in mind when
designing the overall architecture.
Any comments?
I would go with this type of API segments divided according to the level
and ease of access:
for all developers:
- QtQuick signals and data models.
for tier 1 developers
- Qt API
for system developers / vendors
- dbus signal API
This would also nicely handle the security issue as the dbus is already
a system bus with established session control and safety features.
Customisation is also possible from QML all the way down to the dbus
for those who absolutely need it through the Qt dbus interface.
SocketCAN which was discussed earlier could be revealed as a dbus object
as could be done with any other additional vehicle bus.
Example of the associated level of abstraction could be the speed data.
dbus: vehicle pitch, roll, yawn; abs sensors; gnss raw nmea feed
qt: odometry data
QtQuick: vehicleModel.VechicleSpeed
best regards
- jive
_______________________________________________
MeeGo-ivi mailing list
[email protected]
http://lists.meego.com/listinfo/meego-ivi
