Versions Compared

Old Version 9

changes.mady.by.user Jose Luis Urien Pinedo

Saved on

compared with

New Version 10

changes.mady.by.user Jose Luis Urien Pinedo

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

DRAFT MINUTES

Link for today's meeting: Join the meeting now

Date

Attendees & Representation

Type @ and your name to indicate your attendance

Community: Jose Luis Urien Pinedo Ludovic Robert Fernando Prado Cabrillo Rafal Artych Akos Hunyadi Cetin Alpaycetin, Joachim Dahlgren, Chintan Lodariya (Infosys) , Javier Carro Calabor Ming Hui

Agenda

  • Open issues and PRs
  • Any other business

...

  • PR: Geofencing feature file
    • Template not filled
    • Discuss licensing header
      • To be aligned in Commonalities as not sure we have ruling for this.
      • Akos will check internally
    • Discuss alignment to guidelines
  • Issue: Semantics of the absence of 'maxAge'
    • Discuss in meeting
      • Not sure why this 60 seconds limit.
      • Apply for Retrieval & Verification
      • We can change: 
        • Alternative (1) will be to change this limit value from 60 to x
          • if x=0: We have to specify that 0 means 'very recent' location (expectation from request is get the device location right now). If not able 'unknown' should be sent.
          • if x=5 (or other >0): We keep semantic of maxAge unchanged
        • Alternative (2) will to state that if maxAge not value it means real time location is requested.
        • Alternative (3) is to add additional parameter to explicitly ask for current location.
      • Preference from the team to alternative (1) but we keep the discussion open.
      • if maxAge is not valued then we expect to retrieve the latest location (that could be 2 hours ago).
      • Javier also opened the discussion about improving the accuracy limit (2000 meters as of now).

Ongoing

...