Skip to content

Commit 5ab48f9

Browse files
authored
Clarify rules on MCAP profile field in header
Signed-off-by: Pierre R. Mai <[email protected]>
1 parent 1d96e47 commit 5ab48f9

File tree

1 file changed

+3
-0
lines changed

1 file changed

+3
-0
lines changed

doc/architecture/trace_file_formats.adoc

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -40,6 +40,9 @@ The OSI multi channel trace file format is based on the MCAP file format, which
4040
The OSI multi channel trace file format is a specialization of the MCAP file format, with additional constraints and requirements specific to OSI.
4141
Hence, any valid OSI multi channel trace file is also a valid MCAP file, but not the other way around.
4242

43+
The OSI multi channel trace file format does not specify an MCAP profile.
44+
Therefore, it can be used with any or an empty profile field in the MCAP header record, as long as the given profile does not contradict or disallow any of the requirements of this specification.
45+
4346
The following rules apply to OSI multi channel trace files:
4447

4548
- The file extension to be used is `.mcap`.

0 commit comments

Comments
 (0)