<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=utf-8"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><title>AW: AW: [Devel] Updated geolocation and navigation design document</title><style><!--
/* Font Definitions */
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0cm;
margin-right:0cm;
margin-bottom:0cm;
margin-left:36.0pt;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
span.E-MailFormatvorlage18
{mso-style-type:personal-compose;
font-family:"Arial",sans-serif;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:70.85pt 70.85pt 2.0cm 70.85pt;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:1196694373;
mso-list-type:hybrid;
mso-list-template-ids:541257118 -1372043100 67567619 67567621 67567617 67567619 67567621 67567617 67567619 67567621;}
@list l0:level1
{mso-level-start-at:19;
mso-level-number-format:bullet;
mso-level-text:-;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:"Arial",sans-serif;
mso-fareast-font-family:Calibri;}
@list l0:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:"Courier New";}
@list l0:level3
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Wingdings;}
@list l0:level4
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Symbol;}
@list l0:level5
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:"Courier New";}
@list l0:level6
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Wingdings;}
@list l0:level7
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Symbol;}
@list l0:level8
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:"Courier New";}
@list l0:level9
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Wingdings;}
@list l1
{mso-list-id:1578398113;
mso-list-type:hybrid;
mso-list-template-ids:1253333368 -1151721750 67567619 67567621 67567617 67567619 67567621 67567617 67567619 67567621;}
@list l1:level1
{mso-level-start-at:19;
mso-level-number-format:bullet;
mso-level-text:-;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:"Arial",sans-serif;
mso-fareast-font-family:Calibri;}
@list l1:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:"Courier New";}
@list l1:level3
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Wingdings;}
@list l1:level4
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Symbol;}
@list l1:level5
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:"Courier New";}
@list l1:level6
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Wingdings;}
@list l1:level7
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Symbol;}
@list l1:level8
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:"Courier New";}
@list l1:level9
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Wingdings;}
@list l2
{mso-list-id:2143308149;
mso-list-type:hybrid;
mso-list-template-ids:909902968 -1829345226 67567619 67567621 67567617 67567619 67567621 67567617 67567619 67567621;}
@list l2:level1
{mso-level-start-at:19;
mso-level-number-format:bullet;
mso-level-text:-;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:"Arial",sans-serif;
mso-fareast-font-family:Calibri;}
@list l2:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:"Courier New";}
@list l2:level3
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Wingdings;}
@list l2:level4
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Symbol;}
@list l2:level5
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:"Courier New";}
@list l2:level6
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Wingdings;}
@list l2:level7
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Symbol;}
@list l2:level8
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:"Courier New";}
@list l2:level9
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Wingdings;}
ol
{margin-bottom:0cm;}
ul
{margin-bottom:0cm;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=DE link=blue vlink=purple><div class=WordSection1><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'>Hallo Philip,</span><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'><o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'><o:p> </o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'>please find my answers enclosed in <b><span style='color:#538135'>green</span></b><o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'><o:p> </o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'>Rgds<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'>Andre<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'><o:p> </o:p></span></p><p class=MsoNormal style='text-autospace:none'><span style='font-size:10.0pt;font-family:"Arial",sans-serif'><o:p> </o:p></span></p><p class=MsoNormal style='text-autospace:none'><span style='font-size:10.0pt;font-family:"Arial",sans-serif'>-----Ursprüngliche Nachricht-----<br>Von: Philip Withnall [<a href="mailto:philip.withnall@collabora.co.uk">mailto:philip.withnall@collabora.co.uk</a>] <br>Gesendet: Donnerstag, 26. </span><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'>November 2015 10:20<br>An: Barkowski Andre (CM-CI1/PRM1) <Andre.Barkowski@de.bosch.com>; devel@lists.apertis.org<br>Betreff: Re: AW: [Devel] Updated geolocation and navigation design document<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'><o:p> </o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'>Hi Andre,<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'><o:p> </o:p></span></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'>[…]<o:p></o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:black'><o:p> </o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'>> - add UseCase (or a reference in some way): to "imprint a tour"<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'>> consisting of a set of coordinates (via an extended version of the<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'>> scheme mechanism) <o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'><o:p> </o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'>A use case where an LBS application launches the navigation application<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'>with a destination and multiple waypoints (using the URI scheme<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'>mechanism for launching the navigation application)?<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'><o:p> </o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'>I believe this would be a more complex case of the use case above, or<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'>am I misunderstanding?<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'><o:p> </o:p></span></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'>Andre: yes, thing about a tour city guide App, where you can find prepared tours. <o:p></o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'>The difference is a little in granularity and with that quantity as also “meaning” of a waypoint.<o:p></o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'><o:p> </o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'>A waypoint discussed so far reflects an (intermediate) destination, you keep freedom to the navi engine to calculate the route inbetween <o:p></o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'>and there is typically a dedicated “intermediate destination reached” announcement of the route guidance component.<o:p></o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'>But in this case you would like to “influence” the path, even if it is not an intermediate destination. You could go as far as really <o:p></o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'>referencing every link (road element) on the track - and leave no freedom at all anymore to the routing engine – but that’s over<o:p></o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'>specified. So as of now – like you said – we would simple go a “similar” (waypoint) mechanism with some more fine granular supporting points <o:p></o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'>inbetween, but also _<i>without</i>_ “intermediate destination reached” announcement. So we do have to distinguish between both structs, maybe we <o:p></o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'>do have to slightly extend the scheme mechanisms with some coordinates specifying a “via-area” in addition to “intermediate destinations”. <o:p></o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'>Its up to the App to restrict or provide freedom to the Routing engine and with that to take care that the “supporting points“ are close enough to each other to make sure that the path is right where it matters, independent of the routing engine behind.<o:p></o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'><o:p> </o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'>Some background info for future extensions:<o:p></o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'>The reason to call this “via _<i>area</i>_” is, because the same mechanism could (in future) also be used (extended) for other usecases to influence the path. For example, if you like to travel (e.g. from Hamburg) to Rome, you can go via Paris or via Munich. This does not specify an intermediate destination, you neither would like to reach a specific road in that area, nor would you like to get an “intermediate destination reached” announcement. Its only a “supporting point” in a more fuzzy description, which finally gets represented by some area (center point and radius). By using a wider or smaller radius one can influence how close the path has to hit the supporting point. This typically correlate to the type of location referenced to (specific point, a village, <o:p></o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'>town, etc), so one can also keep this concrete mapping (to a dedicated radius) in the responsibility of the routing engine and only refer to a well-defined representative dimension. <o:p></o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'>However, in general this (definition of via areas etc) should all be Navi App-internally (similar like call handling in an phone app), also depending on the Navi supporting this kind of features. An app only provides a destination, and the navi app handles if this shall replace the current destination, if it’s a new intermediate one, which one, as also if there should be via areas in between and what kind of routing parameters /fast, short, etc) are used. But for some dedicated use-cases, we may provide Apps some more capabilities to influences this in future.<o:p></o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'><o:p> </o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'>Lets keep this functionality out of scope so far. I only explain it, to give you a bigger picture to keep it in mind during API definition. The goal is to have some kind of future proneness, i.e. that the next extension does not break the introduced API directly. You can think about if we have handle all in one scalable struct (i.e. an intermediated destination is only as specialization of a via area and all are waypoints), or if we use different things for it.<o:p></o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'><o:p> </o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'><o:p> </o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'>> - add UseCase: to share/subscribe (updated) route-information <o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'><o:p> </o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'>As I've noted below, I cannot think of a use case where an LBS<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'>application could usefully use that information, which is not already<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'>implementable using the geolocation or geocoding APIs. Could you give<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'>an example of the use case you have in mind?<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'><o:p> </o:p></span></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'>Andre: if there is route-information available, then we do have an active route guidance. <o:p></o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'>The route guidance’s presents some information from the route to the User, e.g. the ETA <o:p></o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'>(estimated time of arrival), destination and direction of next turn, etc. It also shows important<o:p></o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'>POIs at the route, e.g. fuel stations, service areas, etc <o:p></o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'><o:p> </o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'>If a 3<sup>rd</sup> Party App adds POI data to the is route-info, this will be included into this presentation (guidance).<o:p></o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'>One can show where the next McDonalds is – if you have a McDonald’s app installed - , or some <o:p></o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'>Touristic interesting things. The App can align the information with the preferences of the User, <o:p></o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'>Driver Condition, Driving situation, the Vehicle Status, etc<o:p></o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'><o:p> </o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'>see for example the Use-Case below (Restaurants)<o:p></o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'><o:p> </o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'>Another perspective is, that the route information describes your track ahead. With that one can call<o:p></o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'>It “horizon”. Apps can provide further details about the track ahead, e.g. hazard spots, weather conditions etc,<o:p></o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'>which finally can be used to inform the Diver (via the guidance info) as also from deeply embedded functions <o:p></o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'>in the car to adopt their functionality-<o:p></o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'><o:p> </o:p></span></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'>To be more abstract, it’s not (only) the way that POI information from all over the cloud gets loaded and imported into<o:p></o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'>the navigation app and considered at point in time of route calculation, in contrast this use-case covers the scope that after a <o:p></o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'>route has been calculated, additional attributes / extended information gets added to the path. So apps – reflecting a given<o:p></o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'>cloud service / data – gathers their data accordant to the situation and adds this to the route-info. This does not influence the <o:p></o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'>track itself (routing), but it informs the user, enables new actions as also will be used again from other (functions) Apps for their<o:p></o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'>build in functionality. <o:p></o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'><o:p> </o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'>Since it also influences other functionalities, we have to reflect the security (e.g. integrity) of data-providers. For example we could <o:p></o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'>think about transporting the source of an information (e.g. which App). Another aspect would be the quality of data, e.g. accuracy, age, etc <o:p></o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'>of data. <o:p></o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'><o:p> </o:p></span></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'>[…]<o:p></o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'><o:p> </o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'>> - add UseCase: to add something into a route list (e.g. restaurants<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'>> along the route from restaurant app) and this based on own interest<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'>> of the user, specified in this app (e.g. via favorites) and under<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'>> control of User by enabling this participation via settings.<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'><o:p> </o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'>Do you mean automatically? What is the user's participation in this use<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'>case: are they specifically interacting with a restaurant app and ask<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'>it to book them into a restaurant and add it as a navigation waypoint;<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'>or do they just want to see nearby restaurants highlighted on the map<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'>as they travel through an area?<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'><o:p> </o:p></span></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'>Andre: like said above, information from the route list will find its way to the<o:p></o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'>route guidance (we sometime call this driver assistance information).<o:p></o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'>So its not about reservation, its about information. A Restaurant App could <o:p></o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'>provide recommendations for a rest stop, fitting to the driving time (e.g. a location<o:p></o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'>area reached after 2 hours of drive), the day time (afternoon, evening, etc => coffee break, dinner, etc), <o:p></o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'>the user preferences (Italian, vegetarian, etc) etc.<o:p></o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'><o:p> </o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'>In relation the use-case above “</span></b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'>add UseCase: to share/subscribe (updated) route-information”<b><span style='color:#538135'><o:p></o:p></span></b></span></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'>The App subscribes for changes in route list, and provides new POIs inc ae the path has <o:p></o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'>been changed.<o:p></o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'><o:p> </o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'><o:p> </o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'>I have a use case in the updated document which covers a restaurant<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'>application adding a waypoint into the current navigation route, if the<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'>user explicitly requests it (for example, by making a booking at the<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'>restaurant). Does that cover what you mean?<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'><o:p> </o:p></span></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'>Andre: It should be possible for the user to select an information added to the route-list,<br>(so from that point of view we againneed the source of information, i.e. which App has added what)<o:p></o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'>After selection by the User, the App gets launched and shows the detailed view of that POI.<o:p></o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'>In the App internal scope, the User can proceed a reservation / booking (similar like phone handling<o:p></o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'>Is app internal). <o:p></o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'><o:p> </o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'>Booked POIs, lands in the app-internal list of reservations, and can be maintained / edited app internally<o:p></o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'>At any point in time later.<o:p></o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'><o:p> </o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'>However, this brings me to another topic of cross app usage. Its also the same for Phone Handling.<o:p></o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'>We do have a last mode of an App, which is the one the App has been left last time. It could be a Detailed<o:p></o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'>View of a specific content, with some extensive tasks picked up before (email, call history, contact info, <o:p></o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'>Restaurant location, etc). Then the User left the App to home screen or some other App due to some reason. <o:p></o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'>Now there is a cross reference from another App into (like mentioned before, also into communication Apps to <o:p></o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'>share something – e.g email, or call handling etc). We should try hard to execute that cross reference <o:p></o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'>(send a mail, book a restaurant, initiate a call), without jeopardizing the state of the full-blown app. So this may<o:p></o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'>Lead us to the requirement to App- Developers, to provide a dedicated executable – an Agent – for this specific<o:p></o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'>Task. This helps us also in minimzing resource needs and increasing reaction time. <o:p></o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'><o:p> </o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'>Please add this to the right place – the right proposal - as take care that our design fits to it.<o:p></o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'><o:p> </o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'><o:p> </o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'>> - add UseCase: for map-widget (with temporary integrated POI data)<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'>> its integrated data sources (position, destination, route, etc) <o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'><o:p> </o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'>What is the use case for this? i.e. In what application context do you<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'>imagine this widget being used? I have been trying to think of an LBS<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'>application use case for exposing destination and waypoint information,<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'>and cannot think of one.<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'><o:p> </o:p></span></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'>Andre: An App like “Restaurants” shows Restaurants accordant to the User Preferences (only open ones, high user rating, <o:p></o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'>time depending only Italian or Chinese etc) in an embedded map (libchamplain). <o:p></o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'>On selection of an POI in this map, the app shows extended POI information (pictures, comments, etc) to the User and vice versa in choosing a <o:p></o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'>POI-Description in the App, the map gets scrolled to the related location. For a POI corresponding to the user interest, <o:p></o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'>the user can initiate a route guidance (scheme based nav service with new destination corresponding to the coordinate info of the Restaurant). <o:p></o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'><o:p> </o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'><o:p> </o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'>In regard to “temporary integrated POI data”:<o:p></o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'>None of the added data (POIs, but also all other kind of added data like line or polygon once) has been imported to the Navi. <o:p></o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'>it all resides in the Restaurant App. The “data responsibility” including their validity Resides in the POI App. <o:p></o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'>The Navi App only gets a new destination.<o:p></o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'><o:p> </o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'>The POI data is also not “imported” to libchamplain, its only shown in a separate layer during the lifetime of the App (temporary).<o:p></o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'>Other Apps do not get them included in “their” map widget.<o:p></o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'><o:p> </o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'>In regard to “integrated data sources”<o:p></o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'>Even though data added to libchamplain by an App keeps the App boundary (its lifecycle and its data responsibility), the map widget <o:p></o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'>Itself carries already lots of information gathered behind the scene (and with that shared over all apps). This is for sure the <o:p></o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'>street data (e.g. tiles fetched from some backend) but beside that its also for example<o:p></o:p></span></b></p><p class=MsoListParagraph style='text-indent:-18.0pt;mso-list:l1 level1 lfo3;text-autospace:none'><![if !supportLists]><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'><span style='mso-list:Ignore'>-<span style='font:7.0pt "Times New Roman"'> </span></span></span><![endif]><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'>The current vehicle position (a moving, updated, vehicle cursor)<o:p></o:p></span></b></p><p class=MsoListParagraph style='text-indent:-18.0pt;mso-list:l1 level1 lfo3;text-autospace:none'><![if !supportLists]><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'><span style='mso-list:Ignore'>-<span style='font:7.0pt "Times New Roman"'> </span></span></span><![endif]><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'>Information (maybe a subset) from the route list, i.e. the destination (e.g. a flag), the intermediate destinations, the track itself, etc<o:p></o:p></span></b></p><p class=MsoListParagraph style='text-indent:-18.0pt;mso-list:l1 level1 lfo3;text-autospace:none'><![if !supportLists]><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'><span style='mso-list:Ignore'>-<span style='font:7.0pt "Times New Roman"'> </span></span></span><![endif]><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'>etc<o:p></o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'><o:p> </o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'><o:p> </o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'>> - add UseCase: for map-widget own responsibility in regard to<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'>> look&feel of embedding the widget, of embedded additional data, its<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'>> interaction on selection events, and the overall functionality <o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'><o:p> </o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'>Can you clarify this please? Do you mean that the map widget should<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'>always have the same appearance, regardless of which application it is<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'>embedded in?<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'><o:p> </o:p></span></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'>Andre: no vice versa.<o:p></o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'>Lets reflect again the scenario mentioned above:<o:p></o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'>An App like “Restaurants” shows Restaurants in an embedded map accordant to its app internal style. <o:p></o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'>On selection of an POIs in this map, the app shows extended information to the User and vice versa in choosing a <o:p></o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'>POI-Description in the App, the map gets scrolled to the related location. For a POI corresponding to the user interest, <o:p></o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'>the user can initiate a route guidance (scheme based nav service with new destination corresponding to the coordinate info of the Restaurant). <o:p></o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'><o:p> </o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'>In an app centric solution we would like to enable freedom for Apps to present it accordant to its needs. So <o:p></o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'>the App can define the size of the map widget, its position in the screen, it can add animated transitions to the whole widget <o:p></o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'>(e.g. a backflip animation of the map, showing some preferences on the back side), and can also define the look & feel of <o:p></o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'>Data added to the map (e.g. appearance animation of added POIs, i.e. own clutter actors). <o:p></o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'><o:p> </o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'>For sure we prepare and provide templates to an App, for prepared screens, its transitions, as also for POIs added <o:p></o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'>(e.g. a pin, with some falling from sky animation), but the App is free to use it. So we never restrict it to it. The App has<o:p></o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'>Freedom do go for an own way, w/o any need / impact to other apps. Its all about general purpose solitons and enabling.<o:p></o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'><o:p> </o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'>Vice versa, if we have imported data into the navigation app, the data responsibility changes. Its like said already in regard to the <o:p></o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'>validity (how long to store, when to delete data etc), but also in regard to the look & feel. The data imported into another App gets rendered<o:p></o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'>like the other App likes to render it. If someone likes to change it, someone has to discuss this with the other App-Owner.<o:p></o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'><o:p> </o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'>Hope you get what I mean.<o:p></o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'><o:p> </o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'><o:p> </o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'>> - add UseCase: to explain a SDK service provided for LBS Apps to ask<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'>> for input of a location which gets transformed to a geo-positon used<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'>> for backend-server. "Type ahead search and completion for addresses"<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'>> an optional extension / future feature<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'><o:p> </o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'>This (which is a description of reverse geocoding; please correct me if<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'>I've misinterpreted) is covered by the 'viewing an address on the map'<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'>use case, which I have reworded to apply to LBS applications rather<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'>than the navigation application.<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'><o:p> </o:p></span></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'>Andre: its slightly different. Lots of LBS Apps do need for their backend service a geo-coordinate.<o:p></o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'>But that’s not the information a User like to type in. A User likes to provide a name (a city, a complete postal address, <o:p></o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'>a name an interesting location, etc). To take care that not each and every App now has the challenge to derive a geo-coordinate <o:p></o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'>from a given name (and every app does this in another way and in different “quality”) a central service should cover that. <o:p></o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'>In best case, this is also embedded in the keyboard, as a special form.<o:p></o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'><o:p> </o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'>From UseCase imaging a weather app, where the user can define the locations of interest. The User likes to type in cities like <o:p></o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'>“Berlin”, “Paris” etc, (including ambiguity resolution, i.e. there are many Berlins in the world, so some selection to be chosen from <o:p></o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'>gets provided from the Backend service, a popup shown and the user select one) So the Weather App provides some action to add a new<o:p></o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'>location, a keyboard appears where the User can type in something, at this point in time (encapsulated from the App) already all <o:p></o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'>the handling takes place to process the location identification mentioned above and the app gets a result the location name as also <o:p></o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'>representative geo-coordinates. The App adds the received location name into its list of user monitored weather locations and uses the <o:p></o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'>received geo-coordinates to fetch the weather information at this place.<o:p></o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'><o:p> </o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'><o:p> </o:p></span></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'>[…]<o:p></o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'><o:p> </o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'><o:p> </o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'>> - add UseCase: explains how a Navi App can produce data for other<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'>> (LBS) Apps (becomes a backend replacement / a data server for SDK-<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'>> API)<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'><o:p> </o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'>I believe this is covered already by the 'automotive backend' use case,<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'>which considers the navigation application and automotive backend to be<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'>fairly tightly coupled from the point of view of providing backend<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'>services for the SDK APIs.<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'><o:p> </o:p></span></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'>Andre: yes, but here it is meant more in relation to “integration of Navi Apps” (the separate chapter), <o:p></o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'>because in this separate chapter an 3<sup>rd</sup> party interested in integrating its navi solution should not only <o:p></o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'>know what needs to be done to get it running at all (from a consuming perspective), but also what kind <o:p></o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'>of data/interfaces should be exposed (from a producing point of view).<o:p></o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'><o:p> </o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'><o:p> </o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'>> - add UseCase (or a reference in some way): to handover/import POIs<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'>> (e.g. Traffic information) which we do have already separately<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'>> covered in our wiki (add a reference). Via that usecase one can also<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'>> explain, how a user is able to select data sources to be used by a<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'>> Navi App by loading the one of interest from Store (out of various<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'>> alternative sources for traffic information)<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'><o:p> </o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'>I have made sure there is a cross-reference to the POI design from the<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'>'POI data' non-use-case section. I believe selecting POI sources for<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'>the navigation application should be internal to the navigation<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'>application. <o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'><o:p> </o:p></span></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'>Andre: yes, but please keep in mind that the method of “selection” is _<i>not</i>_ based <o:p></o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'>on “business logic” within the navi software, but by the User.<o:p></o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'>So the User will make his decision in the context of the Navi App <o:p></o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'>(its setting & preferences, similar like access to a camera roll gets granted or not).<o:p></o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'>The Navi App exposes its interest, the User grants it or not and can it change at every<o:p></o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'>Point in time. Via this mechanism, the user can “configure”, which sources to use.<o:p></o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'><o:p> </o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'>For other APIs (such as POI feeding into geocoding), I<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'>have updated the use cases to mention that the user should be able to<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'>disable it on an application-by-application basis.<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'><o:p> </o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'><o:p> </o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'><o:p> </o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'>> Specific<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'>> - 3.2.1 the sentence "functionality may be exposed directly by the<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'>> backend and used by applications using specific APIs on the backend".<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'>> To be honest, I would love to go for some SDK-APIs also for this<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'>> extension. We can "tag" them as "product specific", but maybe<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'>> something similar will be provided from other backends too. To having<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'>> a "normalization" layer in-between is also beneficial from backwards<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'>> compatibility point of view. If we have direct dependencies to App,<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'>> we run short in compatibility tests. <o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'><o:p> </o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'>The point of this use case was that such backend-specific APIs expose<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'>functionality which is //not// covered in the SDK API — if it were<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'>covered in the SDK API, they would not be backend-specific APIs! I will<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'>amend the document to clarify that the SDK APIs can be extended in<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'>future if it seems appropriate to standardise some functionality from<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'>multiple backends which was previously only available as backend-<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'>specific APIs.<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'><o:p> </o:p></span></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'>Andre: for me it looks like this is a very specific use-case. An App, who <o:p></o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'>uses APIs not part of the SDK becomes a build-in App (formerly named as core-apps) <o:p></o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'>and needs to be updated with the OS. It has a tight relationship, and since we only guarantee <o:p></o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'>backwards compatibility for the SDK, the update path (bundled with the OS) changes. <o:p></o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'>(see applications proposal). <o:p></o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'><o:p> </o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'>We intend to use this way to bridge 'automotive backend' functionalities via representative <o:p></o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'>Agents. These Agents becomes then “build-in” ones, and they use some backend-specific APIs<o:p></o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'>for implementation. But its not to expose this backend-specific APIs to other Apps, its more like <o:p></o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'>a Web-App uses a proprietary API to connect to its Backend and the same will happen for the Agent<o:p></o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'>using a proprietary interface to its automotive Backend. However, the connection to automotive<o:p></o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'>Backends will be discussed further in the scope of “Interdomain Connection” Proposal. We will<o:p></o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'>See on what we conclude finally.<o:p></o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'><o:p> </o:p></span></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'>[…]<o:p></o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:black'><o:p> </o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:black'><o:p> </o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'>> - 3.6. from my point of view it’s a valid use-case, but to be honest<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'>> I do not see the specific topic which influences the requirements and<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'>> API proposal for the scope of this document. For me it is similar<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'>> like a Media Player app continues to render music if another App<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'>> takes foreground focus.<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'><o:p> </o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'>The motivation for this use case was to ensure that routing is<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'>implemented as an agent and application, rather than purely as an<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'>application (which would stop being able to output audio if suspended<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'>or moved to the background).<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'><o:p> </o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'>However, that's a navigation-application-internal feature, so I have<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'>dropped the use case.<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'><o:p> </o:p></span></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'>Andre: thx, that a valid one. We should put this into the special chapter <o:p></o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'>Which explains to 3<sup>rd</sup> parties “how to integrate a navi app”.<o:p></o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'><o:p> </o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'><o:p> </o:p></span></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'>[…]<o:p></o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'><o:p> </o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'><o:p> </o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'>> - 3.9 change the scenario from "Navi" to "LBS" app. But to be honest,<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'>> this is not a first priority goal. This is very special for "address<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'>> input", but since the SDK-API is for general purpose, one do not<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'>> really know If the user types in a "address" or a "POI name". So<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'>> "Eiffel Tower" is maybe not a valid address (in the meaning of city,<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'>> street etc.), but it describes a location. Text-ahead search is maybe<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'>> very challenging for that. This extended scope is very challenging<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'>> for offline solution, because the database will increase to a<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'>> significant size. This lead to online cloud based solution, which may<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'>> have issues with availability or performance. However, lets keep the<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'>> use case and see how far we come. <o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'><o:p> </o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'>Agreed. I will rephrase the use case to be LBS-only, and re-evaluate<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'>the implementation suggestion to see how feasible it is.<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'><o:p> </o:p></span></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'>Andre: yes, lets look about the capabilities of backends. <o:p></o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'>In addition - since an installed Navigation _<i>can</i>_ become a data provide for one, multiple or all backends -<o:p></o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'>this would one more type of data which can be replaced/provided by an installed navigation backend. <o:p></o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'>So we would have map tiles for libchamplain, position for geoclue, route-list for “tbd SDK-API”, etc<o:p></o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'>and now “transformation of a location name to a geo-position with text-ahead support”<o:p></o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'><o:p> </o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'><o:p> </o:p></span></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'>[…] <o:p></o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'><o:p> </o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'>> - 3.14 can maybe hanged to a LBS App usecase, subscribed for a new<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'>> route-info available and updating the POIs (e.g. hazard spots) along<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'>> the (new) route in this list<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'><o:p> </o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'>That's a use case for the POI system; I think the best way to implement<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'>this would be for the navigation application to pull in a new set of<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'>POIs every time it changes the routing (or waypoints or destination).<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'><o:p> </o:p></span></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'>Andre: like explained above, we will have different sinks of POIs, aligned with the different purpose and also with related data responsibility. <o:p></o:p></span></b></p><p class=MsoListParagraph style='text-indent:-18.0pt;mso-list:l1 level1 lfo3;text-autospace:none'><![if !supportLists]><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'><span style='mso-list:Ignore'>-<span style='font:7.0pt "Times New Roman"'> </span></span></span><![endif]><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'>in “libchamplain” for User interaction / selection (aligned with App lifecycle/)<o:p></o:p></span></b></p><p class=MsoListParagraph style='text-indent:-18.0pt;mso-list:l1 level1 lfo3;text-autospace:none'><![if !supportLists]><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'><span style='mso-list:Ignore'>-<span style='font:7.0pt "Times New Roman"'> </span></span></span><![endif]><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'>in “route list” as extended information / attributes (aligned with lifecycle of a route)<o:p></o:p></span></b></p><p class=MsoListParagraph style='text-indent:-18.0pt;mso-list:l1 level1 lfo3;text-autospace:none'><![if !supportLists]><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'><span style='mso-list:Ignore'>-<span style='font:7.0pt "Times New Roman"'> </span></span></span><![endif]><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'>in “Navigation” (via on pull-mode and interface discovery <a href="https://wiki.apertis.org/Points_of_interest">https://wiki.apertis.org/Points_of_interest</a>) as data import (and with that also a hand over of data responsibility, persistent storage, validity, user presentation and also embedding into its build in functionality like route calculation)<o:p></o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'><o:p> </o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'>So there is not _<i>one</i>_ POI system. Hope the 3 different purposes are now more clear. <o:p></o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'>The use case mentioned in 3.14. deals with POIs provided to the route-list.<o:p></o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'><o:p> </o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'><o:p> </o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'>[…]<o:p></o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'><o:p> </o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:black'><o:p> </o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'><o:p> </o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'>> - 3.17 may can be changed to LBS App, consuming it. However, we can<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'>> also keep this in a sense, that a Navi app can replace the backend<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'>> and produce road info for the SDK-API.<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'><o:p> </o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'>I have dropped this one, because I cannot think of a use case where an<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'>LBS application would need to know road information.<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'><o:p> </o:p></span></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'>Andre: see above in regard to use-cases, where an app likes to know road information of the track ahead. E.g. for Hazard spot warning, rest station, etc,<o:p></o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'><o:p> </o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'><o:p> </o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'>> 3.18 from my point of view it’s a valid use-case, but to be honest I<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'>> do not see the specific topic which influences the requirements and<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'>> API proposal for the scope of this document. For me it is similar<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'>> like a last User-Mode.<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'>> 3.19 sounds for me like a Navi-App internal feature<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'><o:p> </o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'>Dropped. I have tried to think of use cases for where an LBS<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'>application might need to be notified of the navigation destination<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'>(and when it changes), but I can't think of any use cases which aren't<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'>already handled by using geolocation or geofencing.<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'><o:p> </o:p></span></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'>Andre: again, see above. If the route changes, the restaurant app would like to update the rest stations recommended to the user. That not geolocation as also not geofencing. <o:p></o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'><o:p> </o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'><o:p> </o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'>> 3.22 also a valid use-case, 3rd party navi apps has to use some<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'>> system info APIs <o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'><o:p> </o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'>But third-party navigation applications are likely to come with their<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'>own locale database, and all they need to be able to use that is the<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'>vehicle's location, which they get from the geolocation API. I cannot<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'>think of other use cases for exposing locale information to LBS<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'>applications which are not served by the geolocation API, so I have<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'>dropped this use case.<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'><o:p> </o:p></span></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'>Andre: at least the position of crossing a border could be of interest. An App could use this information to set a geofence and to inform the User about something (e.g. traffic regulations) once he is close by. Or Apps could use this information to align their recommendations etc. However, this a very special detail, and we can extend the scope / data carried in route list also over time. <o:p></o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'><o:p> </o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'>Another topic is, that Navi Apps may use more than the vehicle’s location for processing. They may need information about the type of vehicle (dimensions, etc), if a trailer is connected etc. <o:p></o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'><o:p> </o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'><o:p> </o:p></span></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'>[…]<o:p></o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'><o:p> </o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'><o:p> </o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'>> 4.3. to be honest, looks like I do not understand the Use-case. We<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'>> would like to have a libchamplain map widget loading map tiles from<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'>> backend providing OSM street data. <o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'><o:p> </o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'>I was told that the automotive domain would definitely not be storing<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'>2D map tiles for libchamplain, so they would not be sent over the<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'>inter-domain communication link; this non-use-case documents that fact.<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'><o:p> </o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'>I think we are in agreement: libchamplain’s map tiles will be loaded<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'>from a backend (in the CE domain) which provides OSM data.<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'><o:p> </o:p></span></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'>Andre: no, that’s a misunderstanding. Map tiles will be loaded from a backend <o:p></o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'>(in the CE domain) which provides OSM data, that’s right. We will use this setup<o:p></o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'>also for the SDK environment. <o:p></o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'><o:p> </o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'>But lets keep the use-case also for the automotive domain setup and with that <o:p></o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'>the inter-domain communication link. Lets cover it concept & design wise and lets see<o:p></o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'>when we implement it.<o:p></o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'><o:p> </o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'><o:p> </o:p></span></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'>[…]<o:p></o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:black'><o:p> </o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'><o:p> </o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'>> 5.17. for LBS-Apps, from my point of view this is more a lib-<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'>> champlain feature. But maybe I am wrong.<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'><o:p> </o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'>libchamplain can give the latitude and longitude of a location on the<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'>map, but this requirement is about the forward geocoding API to convert<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'>that (latitude, longitude) pair into a postal address.<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'><o:p> </o:p></span></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'>Andre: I see. Again a backend service which – in case a navi app is installed - can be provided by the navi app to. </span></b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'><o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'><o:p> </o:p></span></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'>[…]<o:p></o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:black'><o:p> </o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:black'><o:p> </o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'><o:p> </o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'>> 5.22. please change the use case mentioned to an LBS one (embedding a<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'>> map view into the App screen) and adding service specific additional<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'>> information (like animated weather map overlays within a weather map,<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'>> route proposal from tour guides, or hotel from a hotel app)<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'>> However, for me this is some kind of feature discussion for the map<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'>> widget. Today we use libchamplain, is supports some features, others<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'>> will follow. Today its 2D. We can think about if the API (from<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'>> libchamplain) is well already, should be enhanced or if we should use<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'>> a separate one for 3D. This can also be a roadmap discussion, when we<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'>> enhance what.<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'><o:p> </o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'>The use case which motivated the requirement for a 3D map was<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'>implementing a navigation application, but since that use case has been<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'>removed, I don't think there is now a motivation for a 3D map API, so I<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'>will drop this requirement. There might be individual applications<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'>which would benefit from a 3D map, but I think a 2D map (i.e.<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'>libchamplain) caters for 90% of all mapping use cases in LBS<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'>applications, so it would be unnecessary effort to provide a 3D map API<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'>in the SDK.<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'><o:p> </o:p></span></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'>Andre: yes, its not intended for implementing a navi app. <o:p></o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'>However, it’s stays a roadmap topic even that it’s intended for LBS Apps only. <o:p></o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'>I agree that a 2D maps serves well for the majority of LBS Apps, but sometimes OEMs <o:p></o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'>like to push the limits. And since Smartphone Ecosystems provide already some <o:p></o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'>“perspective 2,5D view”, Navi Apps itself provides full 3D view, it may appears that to be <o:p></o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'>up-to-date we have to embed 3D capability also into the map view for LBS Apps. <o:p></o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'>To provide a modern and feature rich user experience. <o:p></o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'><o:p> </o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'>So keep it on the roadmap, its nothing urgent yet.<o:p></o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'><o:p> </o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'><o:p> </o:p></span></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'>[…]<o:p></o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:black'><o:p> </o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'><o:p> </o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'>> - 7.9. good to have a OSS solution. However, I would like to<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'>> understand how this would fit in case we are interested to use a<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'>> google service (as a variant)<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'><o:p> </o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'>OK, I will add in a Google geocoding option as a variant. My initial<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'>thoughts are that this would become a backend for the same geocode-glib <o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'>API, using the Google Maps Geocoding API. However, I will investigate<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'>it further before writing up my recommendations in the design.<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'><o:p> </o:p></span></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'>Andre: great.</span></b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'><o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'><o:p> </o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'>I will also add an alternative design for the address completion<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'>component, using the Google Places API.<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'><o:p> </o:p></span></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'>Andre: thx.</span></b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'><o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'><o:p> </o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'><o:p> </o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'>Are there any other alternative designs you want to be considered?<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'><o:p> </o:p></span></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'>Andre: so far it seems sufficient for me to reflect Google services as backend replacements. <o:p></o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'>On the one hand they have a good footprint in this area, and they also serve well as a representative <o:p></o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'>scenario for proving the flexibility. </span></b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'><o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'><o:p> </o:p></span></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'>However, do not to forget, that an installed Navi app can replace single up to all backends, and <o:p></o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'>that with that it could also be provided by “automotive backends” via the interdomain <o:p></o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'>communication.<o:p></o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'><o:p> </o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'><o:p> </o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#538135'><o:p> </o:p></span></b></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif'><o:p> </o:p></span></p></div></body></html>