Ted: while we have had a Summer haitus some may have furthered related work at their respective organizations and able to share with the group. I'll go first and encourage others to speak
Ted: National Association of
Insurance Carriers (NAIC.org US organization with state and
federal insurance regulators) reached out to me to participate
in a panel for a conference they are having in California
https://naic.org/cipr_events.htm
... they set requirements for insurance carriers including what
data can be collected and how it is used. they also have a big
data focus and we will hopefully be working together to get
their perspective
... I have reached out to and spoke with Otonomo, data service
provider for a number of OEM. they may start observing some
calls as they too should be able to provide perspective
... Neutral Vehicle is kicking off, perhaps Glenn may want to
say more
... met with someone from Volvo Trucks. heavy vehicles already
have more consistency and common reporting requirements from
regulators in EU and US
... some reading on policy language and talking with healthcare
& life sciences data architect on why they don't use
one
... hoped to have projects supported by Ford-MIT alliance this
Fall, one on privacy policy and pertinent to group. looks like
it will get support in the Spring but will do some preliminary
work with MIT Principal Scientist and an intern or two
Glenn: Neutral Vehicle is a
consortium that has been brought together to address concerns
of fleet managers who handle mixed fleets
... there are considerable interoperability concerns. this will
be based at the University of Colorado, led by Dr Dan Massey
formerly of DHS
... other parties include DOT, UL, and fleet managers
... within the commercial vehicle space there is Electric
Logging Data requirements. each is proprietary in how they
handle data
... we are looking at creating a common ELD API to handle
transportability of data so fleets do not fall out of legal
reporting compliance if their ELD provider ceases to
operate
... we are also looking at other common mixed fleet needs such
as remote vehicle unlock, perhaps too much inconsistency at
present for that project to go forward
... a website was created http://neutralvehicle.com
Joakim: Connected Car Consortium has been looking at standardizing electronic key for this use case
Glenn: I learned about that a
couple days ago and the topic will be covered at an upcoming
CCC meeting in Tokyo
... we will be looking into that. we are looking at it from the
mixed fleet manager perspective
Joakim: If you need an introduction let me know, I know the director
Ted: I should reach out to them as well. it has been some time since we had someone from MS who is active in CCC attend some of our calls
Glenn: prior to break we have
been discussing creating privacy use cases for consent
capture
... I shared an internal document with Ted for review before
sharing with the group
Harjot: as Glenn said NV kicked
off yesterday
... I want to go further with data contracts when we have more
on the call
... we started off agreeing on different areas: permissions,
logging algorith, control and access
... where we left of last was getting agreement on what the
data contract should cover
Adam: I have reached out to one of our internal data warehousing people and will send another followup
Joakim: I have been looking into
a time series database engine
... we have been collaborating on a number of use cases
including real time analytics on signals
... I shared some with Ted
... I have been looking at the example sparql queries from
Benjamin's VSSO
... I am fairly familiar with sparql. it can handle a number of
cases but some get very complex quickly
... also been thinking on EV data needs
Glenn: the US DOT Volpe center and NMFTA recently released a report on EV/EVSE concerns
public-autowebplatform@w3.org
Ted: EV has particular data needs
and that would be worth covering. as an aside I think we are
repeating a possible mistake with EV, combining charging and data
in a single connector similar to USB.
Physical world harder to
protect, including charging systems which can in turn attack
vehicles. Best in my opinion would be to have all the data
communication be indirect through the cloud and not to the vehicle directly.
Joakim: interesting, that case should be looked into deeper. not sure this is the right forum
Ted: agree it is probably more an SAE topic, meanwhile industry seems to be repeating USB mistake
Glenn: not sure offhand if they
have a committee on this topic. US DOT Volpe, NMFTA and DOE
have been looking at it
... I will share their public document with this group
[Benjamin was on a train and deferred]
Ted: so far most of our focus has been on consent capture and data contracts with reports from Ben on his semantic web work on data model
[[
<ericP> there's always a temptation to use them to manage research access to patient data
but the challenge is that it's very difficult to put a piece of paper in front of a patient which does a reasonable job of discriminating uses of the data
<ericP> patient's typically care about one kind of disease because they or someone close to them has it
<ericP> so one piece of paper doesn't work for 6000 diseases
<ericP> if we could work out the speech acts associated with donating your data, and persuade patients to look into the future and include stuff they'll care about later, the step of capturing that in a computerized form is pretty easy
]]
Ted: clear, concise UI with
simple and longer version of terms and parties receiving
data
... related W3C workshop
Use case
Ted: short version, we are at junction. we have a nice simple case consent model from Dominik and Ulrich and if possible agree best to keep designs simple. I can see a number of potential scenarios that complicate it and might necessitate need for using a policy language or other techniques. we need to understand more use cases to influence our direction
Glenn: valuable and complex
topic, agree with assessment and not sure where to start
... OEM, regulators, fleet managers, insurance carriers etc all
have different needs
... almost need a matrix of data points and interested
parties
... there will be significant overlap in collection
... I have a document to share that might help frame this
... it covers a number of the different parties and needs
including suggested control and access use cases
Ted: yes, please send to the list
and encourage people to provide responses and think on use
cases
... I will try to get additional perspectives and next call we
can review any shared use cases plus perhaps define more on the
fly
[adjourned]