We use cookies on this site to enhance your user experience. By using this site, you are giving your consent for us to set cookies.


You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 29 Next »

Meeting Notes 2023-06-08

  • Welcome and Compliance statement

Welcome to the COVESA Data Expert Group

Antitrust
Before we begin, we would like to make clear that COVESA is committed to compliance with the antitrust laws in all of its activities, and that it expects all participants to similarly comply with the antitrust laws.  We will not engage in--and members must refrain from--any discussion of, or understandings regarding competitively sensitive topics. If you have any doubts regarding whether a matter is appropriate for discussion, please consult with your antitrust counsel.

Open and Royalty-Free
Further, COVESA aspires to be an open and royalty-free organization. The discussions and contributions made during this session are governed by the COVESA Intellectual Property policy. If you are unfamiliar with that policy, please review it in detail prior to making any contribution that reads upon a patent.

  • Agenda discussion - anything that needs to be added?
  • Prioritized topics
  • Walk through ongoing topics in  “Backlog/Kanban Board”.  Each Pillar should have a work product their group is working toward and status.
  • Prioritized topics for next meeting
    • HIM/IFEX to be discussed June 15th
  • Date for next monthly report discussion

Meeting Notes 2023-06-01

  • Welcome and Compliance statement

Welcome to the COVESA Data Expert Group

Antitrust
Before we begin, we would like to make clear that COVESA is committed to compliance with the antitrust laws in all of its activities, and that it expects all participants to similarly comply with the antitrust laws.  We will not engage in--and members must refrain from--any discussion of, or understandings regarding competitively sensitive topics. If you have any doubts regarding whether a matter is appropriate for discussion, please consult with your antitrust counsel.

Open and Royalty-Free
Further, COVESA aspires to be an open and royalty-free organization. The discussions and contributions made during this session are governed by the COVESA Intellectual Property policy. If you are unfamiliar with that policy, please review it in detail prior to making any contribution that reads upon a patent.

  • Agenda discussion - anything that needs to be added?
  • Prioritized topics
    • "Ulf/HIM proposal" (Hierarchical Information Model)

1. Decide on name for the evolved data model.
2. Create a new COVESA Github repo based on the new name.
3. Decide on a directory structure that can accommodate rule set definitions for multiple domains and multiple information types.
4. Create a rudimentary README on the top level giving a high level description of the new data model.
5. Move the VSS "rules definition" (the documentation) from the VSS repo to an appropriate directory on this new repo.
6. Create a rule set for services that that meets the requirements from the "passenger car domain" (VSS).
7. On the VSS repo, create an initial service tree based on the rule set from the bullet above. Continue to evolve it in parallell with the existing VSS tree.
8. Analyze the impact on VSS-Tools that the above has, take action on the insights from that.
9. Try to influence the W3C automotive group to evolve VISSv2 to support the new data model.
10. If successful on the above bullet, create a new COVESA project that will develop a POC containing a technology stack based on the evolved W3C interface and COVESA data model.

      • Discussion:
        • Ulf: Could be soft started as VSS subproject
        • Ulf: Do not see HIM file as input to vss-tools, it is the server that consumes it, it still work with initial trees
        • Erik: Suggestion:
          • Let Paul create a HIM repo (M/W/X)
          • Ulf to start working with repo, describe motivation, idea, and suggested increments/roadmap and basic architecture
            • Describe what problem we intend to solve, why do we create it.
          • Then let DEG discuss at regular interval, keep VSS meeting informed
          • When mature we can discuss how to involve more people
        • Decision: OK for Paul to create repo
        • Discuss relationship to VCS when we have the parts above ready
    • Adnan: SDV and Eclipse
  • Walk through ongoing topics in  “Backlog/Kanban Board”.  Each Pillar should have a work product their group is working toward and status.
  • Prioritized topics for next meeting
  • Date for next monthly report discussion

Meeting Notes 2023-05-11

  • Welcome and Compliance statement

Welcome to the COVESA Data Expert Group

Antitrust
Before we begin, we would like to make clear that COVESA is committed to compliance with the antitrust laws in all of its activities, and that it expects all participants to similarly comply with the antitrust laws.  We will not engage in--and members must refrain from--any discussion of, or understandings regarding competitively sensitive topics. If you have any doubts regarding whether a matter is appropriate for discussion, please consult with your antitrust counsel.

Open and Royalty-Free
Further, COVESA aspires to be an open and royalty-free organization. The discussions and contributions made during this session are governed by the COVESA Intellectual Property policy. If you are unfamiliar with that policy, please review it in detail prior to making any contribution that reads upon a patent.

  • Agenda discussion - anything that needs to be added?
  • Prioritized topics
      • API project - see 

        VSS Meeting Topics and Meeting Notes

      • S2S-api_COVESA_V1.pptx
      • Discussion:
        • Paul: What do we want to explore needs to be defined. Start with a call with member - what do people want.
        • Erik: We need a realistic roadmap - what are people prepared to do? what can we achieve until next AMM or within next 12 months
  • Walk through ongoing topics in  “Backlog/Kanban Board”.  Each Pillar should have a work product their group is working toward and status.
  • Prioritized topics for next meeting
  • Date for next monthly report discussion

Meeting Notes 2023-05-04

  • Welcome and Compliance statement

Welcome to the COVESA Data Expert Group

Antitrust
Before we begin, we would like to make clear that COVESA is committed to compliance with the antitrust laws in all of its activities, and that it expects all participants to similarly comply with the antitrust laws.  We will not engage in--and members must refrain from--any discussion of, or understandings regarding competitively sensitive topics. If you have any doubts regarding whether a matter is appropriate for discussion, please consult with your antitrust counsel.

Open and Royalty-Free
Further, COVESA aspires to be an open and royalty-free organization. The discussions and contributions made during this session are governed by the COVESA Intellectual Property policy. If you are unfamiliar with that policy, please review it in detail prior to making any contribution that reads upon a patent.

  • Agenda discussion - anything that needs to be added?
  • Prioritized topics
      • AMM Lessons Learned
      • Next AMM October 10th-12th, Troy, Mi, USA
  • Walk through ongoing topics in  “Backlog/Kanban Board”.  Each Pillar should have a work product their group is working toward and status.
  • Prioritized topics for next meeting
  • Date for next monthly report discussion

Meeting Notes 2023-04-20

  • Welcome and Compliance statement

Welcome to the COVESA Data Expert Group

Antitrust
Before we begin, we would like to make clear that COVESA is committed to compliance with the antitrust laws in all of its activities, and that it expects all participants to similarly comply with the antitrust laws.  We will not engage in--and members must refrain from--any discussion of, or understandings regarding competitively sensitive topics. If you have any doubts regarding whether a matter is appropriate for discussion, please consult with your antitrust counsel.

Open and Royalty-Free
Further, COVESA aspires to be an open and royalty-free organization. The discussions and contributions made during this session are governed by the COVESA Intellectual Property policy. If you are unfamiliar with that policy, please review it in detail prior to making any contribution that reads upon a patent.

  • Agenda discussion - anything that needs to be added?
  • Prioritized topics
  • Walk through ongoing topics in  “Backlog/Kanban Board”.  Each Pillar should have a work product their group is working toward and status.
  • Prioritized topics for next meeting
  • Date for next monthly report discussion

Meeting Notes 2023-04-13

  • Welcome and Compliance statement

Welcome to the COVESA Data Expert Group

Antitrust
Before we begin, we would like to make clear that COVESA is committed to compliance with the antitrust laws in all of its activities, and that it expects all participants to similarly comply with the antitrust laws.  We will not engage in--and members must refrain from--any discussion of, or understandings regarding competitively sensitive topics. If you have any doubts regarding whether a matter is appropriate for discussion, please consult with your antitrust counsel.

Open and Royalty-Free
Further, COVESA aspires to be an open and royalty-free organization. The discussions and contributions made during this session are governed by the COVESA Intellectual Property policy. If you are unfamiliar with that policy, please review it in detail prior to making any contribution that reads upon a patent.

  • Agenda discussion - anything that needs to be added?
  • Prioritized topics
  • Walk through ongoing topics in  “Backlog/Kanban Board”.  Each Pillar should have a work product their group is working toward and status.
  • Prioritized topics for next meeting
  • Date for next monthly report discussion

Meeting Notes 2023-04-06

  • Welcome and Compliance statement

Welcome to the COVESA Data Expert Group

Antitrust
Before we begin, we would like to make clear that COVESA is committed to compliance with the antitrust laws in all of its activities, and that it expects all participants to similarly comply with the antitrust laws.  We will not engage in--and members must refrain from--any discussion of, or understandings regarding competitively sensitive topics. If you have any doubts regarding whether a matter is appropriate for discussion, please consult with your antitrust counsel.

Open and Royalty-Free
Further, COVESA aspires to be an open and royalty-free organization. The discussions and contributions made during this session are governed by the COVESA Intellectual Property policy. If you are unfamiliar with that policy, please review it in detail prior to making any contribution that reads upon a patent.

  • Agenda discussion - anything that needs to be added?
  • Prioritized topics
    • AMM
      • AP: Erik to remove "negative" part, check with Gunnar for actual plan
    • Repository - best practices
      • Paul will start describring the process.
    • Friday agenda
      • 9.00-14.00
      • Paul to create confluence page
  • Walk through ongoing topics in  “Backlog/Kanban Board”.  Each Pillar should have a work product their group is working toward and status.
  • Prioritized topics for next meeting
  • Date for next monthly report discussion

Meeting Notes 2023-03-30

  • Compliance statement - TBD

  • Antitrust
    Before we begin, we would like to make clear that COVESA is committed to compliance with the antitrust laws in all of its activities, and that it expects all participants to similarly comply with the antitrust laws.  We will not engage in--and members must refrain from--any discussion of, or understandings regarding competitively sensitive topics. If you have any doubts regarding whether a matter is appropriate for discussion, please consult with your antitrust counsel.

    Open and Royalty-Free
    Further, COVESA aspires to be an open and royalty-free organization. The discussions and contributions made during this session are governed by the COVESA Intellectual Property policy. If you are unfamiliar with that policy, please review it in detail prior to making any contribution that reads upon a patent.

  • Welcome and agenda discussion - anything that needs to be added?
  • Prioritized topics
    • EV Charging Repo
    • AMM
    • Compliance
      • Was typo (see organe above)
      • IPR policy rework in progress
      • Link to text good so we have a "master" that we can copy and add to invites
      • Shall be read at start of meetings.
    • EU initiative
      • Workshop next week
  • Walk through ongoing topics in  “Backlog/Kanban Board”.  Each Pillar should have a work product their group is working toward and status.
  • Prioritized topics for next meeting
  • Date for next monthly report discussion

Meeting 2023-03-23

  • Compliance statement - TBD
  • Welcome and agenda discussion - anything that needs to be added?
  • Prioritized topics
    • AMM
    • Encourage colleagues to register to AMM
  • Walk through ongoing topics in  “Backlog/Kanban Board”.  Each Pillar should have a work product their group is working toward and status.
  • Prioritized topics for next meeting
  • Date for next monthly report discussion

Meeting 2023-03-16

  • Compliance statement - TBD
  • Welcome and agenda discussion - anything that needs to be added?
  • Prioritized topics
    • AMM
      • Agenda walkthrough
      • Vehicle API session?
  • Walk through ongoing topics in  “Backlog/Kanban Board”.  Each Pillar should have a work product their group is working toward and status.
  • Prioritized topics for next meeting
  • Date for next monthly report discussion

Meeting 2023-02-23

  • Compliance statement - TBD
  • Welcome and agenda discussion - anything that needs to be added?
  • Prioritized topics
    • Struct support - VSS and APIs
      • Example: Struct support in VISS not explicitly stated, likely not complex, need json representation
      • AP: Erik to bring it up to VISS
      • Adnan expressed concern on struct usage
      • Ulf: guidance to be added to documentation.
    • Atomic read/write of multiple signals
      • Topic brought up by Bosch - recommendation/required for APIs?
    • Stream Support
      • Events or Video/Audio?
    • VehicleAPI
    • AMM
  • Walk through ongoing topics in  “Backlog/Kanban Board”.  Each Pillar should have a work product their group is working toward and status.
  • Prioritized topics for next meeting
  • Date for next monthly report discussion

Meeting 2023-02-09

  • Compliance statement - TBD
  • Welcome and agenda discussion - anything that needs to be added?
  • Prioritized topics
    • Adnan presents Vehicle diagram with zones and ethernet backbone
      • Which integration points do we want to handle
      • COVESA scope
        • Between zones
        • Zones to HU/TCU/COMPUTING
        • Communication from HU/TCU to Mobile/Cloud
        • For use-cases, what do we see as COVESA requirements
    • Vehicle API
      • We can move forward internally.
    • Workshop Feb 15th -16th - Data Expert Group - Workshop 2023 - Q1
      • See page
    • AMM
  • Walk through ongoing topics in  “Backlog/Kanban Board”.  Each Pillar should have a work product their group is working toward and status.
  • Prioritized topics for next meeting

Meeting 2023-02-02

  • Compliance statement - TBD
  • Welcome and agenda discussion - anything that needs to be added?
  • Prioritized topics
  • Walk through ongoing topics in  “Backlog/Kanban Board”.  Each Pillar should have a work product their group is working toward and status.
  • Prioritized topics for next meeting
  • Date for next monthly report discussion

Meeting 2023-01-26

  • Compliance statement - TBD
  • Welcome and agenda discussion - anything that needs to be added?

Prioritized topics

    • Workshop Feb 15th -16th
      • Agenda
        • AMM Topics
        • Release Planning
        • Way forward - Best Practices and Howtos
        • Vehicle API
        • Data Expert Group Retrospective
          • What has worked well
          • What has not worked well
      • Ted: Create a poll, find people who can lead the topics
      • AP: Paul to put it on COVESA calender
      • Paul: Focus on ws shall be data expert group
      • Confluence page created
        • AP: All to propose subjects on confluence page until next week.
        • Next week create rough agenda
    • AMM in Porto, Portugal, 25-27th April (Tuesday-Thursday)
      • Possibly assemble data expert group the day before or after for workshop
      • Ulf: Could be Tuesday morning, AMM typically starts at noon
      • AP: Everyone to check when they likely will/can arrive/leave, to find suitable slots
      • Stephen: Board meeting might be on Tuesday morning
      • Paul: Board meetings Tuesday and Thursday mornings, according to Steve
      • Ulf: Then better to have our meeting Monday morning.
      • AP: Paul to create confluence page for planning
    • VSS Schedule
    • Sign-offs
  • Walk through ongoing topics in  “Backlog/Kanban Board”.  Each Pillar should have a work product their group is working toward and status.
  • Prioritized topics for next meeting
    • Workshop and AMM
  • Date for next monthly report discussion

Meeting 2023-01-19

  • Compliance statement - TBD
  • Welcome and agenda discussion - anything that needs to be added?
  • Prioritized topics
  • Walk through ongoing topics in  “Backlog/Kanban Board”.  Each Pillar should have a work product their group is working toward and status.
  • Prioritized topics for next meeting
  • Date for next monthly report discussion

Meeting 2023-01-12

  • Compliance statement - TBD
  • Welcome and agenda discussion - anything that needs to be added?
  • Prioritized topics
    • Online Workshops (Paul, https://github.com/COVESA/data-expert-group/issues/4)
      • See notes in issue
      • Paul presented ideas:
      • Ulf: Often difficult to find information on homepage, it should be possible to find a page for each project from home page. Then we can start to fill out.
      • Paul Boyes : To create a poll for date
      • Stephen: Next week data architecture meeting will discuss topics for a workshop
    • Spring AMM planning
    • Presentation to board concerning VSS
    • COVESA-AUTOSAR charter - move to *.md repo (idea from Stephen)?
  • Walk through ongoing topics in  “Backlog/Kanban Board”.  Each Pillar should have a work product their group is working toward and status.
  • Prioritized topics for next meeting

Meeting 2023-01-05

  • Compliance statement - TBD
  • Welcome and agenda discussion - anything that needs to be added?
  • Prioritized topics
    • AUTOSAR -COVESA Collaboration
      • Erik has updated charter with proposed deliverables, to be reviewed by Sami from AUTOSAR Cloud WG Group
      • Initial comments from Sami received, see https://github.com/COVESA/data-expert-group/issues/2
      • Erik/Paul/Adnan to have meeting w Sami next two Fridays, in preparation for next steering group call
      • Ulf to present vehicle API proposal at the internal meeting Tuesday next week
  • Walk through ongoing topics in  “Backlog/Kanban Board”.  Each Pillar should have a work product their group is working toward and status.
  • Prioritized topics for next meeting
  • Date for next monthly report discussion

Meeting 2022-12-15


  • Compliance statement
    • TBD: Discussion ongoing on what needs to be informed at start of the meeting.
  • Welcome and agenda discussion - anything that needs to be added?
  • Prioritized topics
    • AUTOSAR sync meeting tomorrow
      • Erik: Discussion last Friday w Erik, Adnan, Sami, see notes
      • Stephen: What was decided on board meeting
      • Paul: Likely continue with/without AUTOSAR, lets see tomorrow
      • Erik: What does really exist in AUTOSAR, only specs but also implementation
      • Stephen: In Adaptive reference implementation of drivers
      • Stephen: Good mentioning VISS, but not be to prescriptive
      • Stephen: Good to have simulator for if AUTOSAR is black box
      • Stephen: Does not necessarily need to be Linux, could be any RTOS, does not matter for architecture
      • Erik: But matters for PoC
      • Ulf: Do not think the VehicleAPI shall be VISS, it is too complex, shall be thin. But VISS shall be easily be integratable on top of it.
      • Ulf: API abstracts details, Data Mapper shall not be too interesting from COVESA perspective.
      • Ulf: AUTOSAR might come with input to VSS catalog
      • Erik: Has scope of PoC been discussed?
      • Paul: No!
  • Walk through ongoing topics in  “Backlog/Kanban Board”.  Each Pillar should have a work product their group is working toward and status.
  • Info: Cancelled meeting due to New Year
    • Meetings cancelled: Dec 22nd, Dec 29th
    • Sync on available participants for Jan 5th on Slack just before, cancel if needed
  • Information
    • Paul is going to propose big blocks related to roadmap handling. We shall say where we want to be for next AMM (Europe late April- early May).
    • Stephen going on vacation tomorrow
  • Prioritized topics for next meeting

Meeting 2022-12-08


  • Compliance statement
    • Discussion ongoing on what needs to be informed at start of eah meeting.
  • Welcome and agenda discussion - anything that needs to be added?
  • Prioritized topics
    • Monthly report to Board
      • Currently handled informally by Paul
      • Paul can publish the slide he use for reporting, so DEG members can add/review as needed
  • Walk through ongoing topics in  “Backlog/Kanban Board”.  Each Pillar should have a work product their group is working toward and status.
  • Cancelled meeting due to New Year
    • Meetings cancelled: Dec 22nd, Dec 29th
    • Sync on available participants for Jan 5th on Slack just before, cancel if needed
  • Information
    • Workshop being planned for architecture pillar
  • Prioritized topics for next meeting

Weekly Agenda Template

  • Compliance statement - TBD
  • Welcome and agenda discussion - anything that needs to be added?
  • Prioritized topics
    • <Please Propose In Advance>
    • <Monthly report (once a month)
  • Walk through ongoing topics in  “Backlog/Kanban Board”.  Each Pillar should have a work product their group is working toward and status.
  • Prioritized topics for next meeting
  • Date for next monthly report discussion


Subpages


  • No labels

Privacy Policy | Cookie Policy