What SHOULD be included in the ECU Manifest?

Question

What SHOULD be included in the ECU Manifest?

Closed this issue 6 years ago · 4 comments

What are the key data that must be completed here. I believe @iramcdonald and @cajun-rat offered to provide some language for this.

Answer 1 · 2019-03-13T16:06:41.000Z

On the 03/13 standards call, we agreed to leave this issue open for the next two weeks so that people can comment here informally about what kinds of things to include. We will ask for a volunteer to aggregate the suggestions and write the text on the 03/27 standards call.

Answer 2 · 2019-03-14T10:39:48.000Z

Are Sections 5.4.2.1.1 (Vehicle version manifest) and 5.4.2.1.2 (ECU version report) not enough to describe this already? I checked our implementation of what we send and the default information is exactly what is described there.

Answer 3 · 2019-03-14T11:05:36.000Z

@patrickvacek: The idea here is to gather ideas about what would be useful to include in the custom metadata. For example, perhaps a useful custom field would be a list of libraries and versions used in building the image, or some sort of diagnostic data. We're leaving it open especially to folks from OEMs to give their input on the kinds of things that would be helpful here.

We're not talking about changing the required parts--no new or modified SHALLs/MUSTs. Just suggestions for adding some SHOULDs.

Answer 4 · 2019-03-27T16:18:42.000Z

This was closed on 3/27 after discussion on the Standards calls noted there had been no suggestions generated on the topic.