You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: doc/architecture/architecture_overview.adoc
+5-2Lines changed: 5 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -29,13 +29,16 @@ The `HostVehicleData` interface describes the measured internal states of a traf
29
29
OSI currently provides only limited support for data structures that describe measured internal states of traffic participants.
30
30
Actuator intentions are currently not covered by OSI and must be handled using a different data description format.
31
31
32
-
All fields in an interface are set to `optional`.
32
+
NOTE: OSI uses singular instead of plural for `repeated` field names.
33
+
34
+
NOTE: All fields in an interface are set to `optional`.
33
35
`required` is not used.
36
+
34
37
This has been done to allow backward-compatible changes in the field.
35
38
Additionally, this is the default behavior in Protocol Buffer version 3 that no longer has the `required` type.
36
39
Setting all fields to `optional` thus ensures update compatibility.
37
40
However, this does not mean that it is optional to fill the field.
38
41
For the purpose of providing a complete interface, all existing fields should be set, unless not setting a field carries a specific meaning, as indicated in the accompanying comment.
39
42
40
-
All field numbers equal to or greater than 10000 are available for user-specific extensions via custom fields.
43
+
NOTE: All field numbers equal to or greater than 10000 are available for user-specific extensions via custom fields.
41
44
No future evolution of OSI will therefore use field numbers equal to or greater than 10000.
0 commit comments