- From: Harjot Singh <harjotsingh@geotab.com>
- Date: Wed, 13 Feb 2019 18:17:08 -0500
- To: public-autowebplatform@w3.org
- Message-ID: <CAG-tSEKZ+5eMULZoxcA2jcnj_LP_Q4oRqnCCKndg6j=h9pO4Bg@mail.gmail.com>
Hi all, As a follow up to our last meeting on February 7th, I wanted to open a thread into whether or not to incorporate sampling methodology into VSS. I am of the opinion that sampling methodology is a necessary component that should be addressed at some level. My rational being that similar to how we include attributes on data through the spec (description, datatype etc), attributes on how the data was collected play an important role for users of the data down stream. Information on how precise the hardware measurement senors/components are, and how/what process is applied to data before it is stored elsewhere (GPS data comes to mind first and foremost) is directly impacts the value of the data. On another note, the more demanding the potential down stream request for data - inevitably there is a proportional associated cost with transferring information from a vehicle elsewhere. In other words, more data sent = more costs accrued. The logic used to determine whether or not a every point of data from a vehicle is uploaded / made available or not should be made clearly defined. For additional information, the 'Data Contract <https://docs.google.com/document/d/15chftyY4WMv4yQ3WlyVlHrG8BcWm-Tyws9-79eqDCgA/edit>' document previously shared can also be used for reference / additional topics of discussion. This is a draft document that Glenn and I put together, it isn't ready perhaps for general public consumption - but contains several points of interest / use cases of note that we have brain stormed. Thanks for your time. -- Harjot Singh Geotab Product Safety Manager | B.Eng.Mgt. [Cell] +1 (647) 501-6665 [Toll-Free] +1 (877) 436-8221 [Visit] www.geotab.com Twitter <http://twitter.com/geotab> | Facebook <http://www.facebook.com/geotab> | YouTube <http://www.youtube.com/mygeotab> | LinkedIn <https://www.linkedin.com/in/harjotservosingh> *If this email was received in error, please notify me immediately and destroy the message and any electronic or paper copies.*
Received on Wednesday, 13 February 2019 23:19:55 UTC