Unique iD

[ghost]

I think it is difficult to maintain uniqueness over different classes. I would propose to ensure uniqueness over lifetime (overall simulation even if out of view) for each class? But I am not sure? We could also say unique for each interface? Unique in GT, in SV and in SD ? What do you think @pmai ?

[pmai]

I think it is somehow a bit more complex, because some Ids should be unique across classes (e.g. for detected stuff this really makes sense, the sensor id stuff also), so I think we need to specify a default, like unique per class, and then review every ID whether to add specific wording for that ID...

[ghost]

@pmai IDEA: 1) Unique IDs for every TopLevel Message, GT, SV, SD

• There is only one GT
• There is one SV for every sensor_id
• There is one SD for every sensor_id 2) Unique iDs are monoton advancing 3) Highest already used ID is stored in the top level message 4) IDs are constant over simulation time

[ghost]

@pmai: As @CarloVanDriestenBMW referenced above (#146), this issue is already adressed in the documentation. Do you see any needs for further changes in OSI 3.0.1?

[ghost]

@CarloVanDriestenBMW I think this idea requires further refinement.

[ghost]

Postponed to OSI 3.1.0