Clarify number of files per stream

[ctf.git] / common-trace-format-specification.txt

diff --git a/common-trace-format-specification.txt b/common-trace-format-specification.txt
index d0636cfba4dc7987e6cccd6a7847d798d309cc79..9cd39ded0b898159da9672b4262014b0b924ee88 100644 (file)
--- a/common-trace-format-specification.txt
+++ b/common-trace-format-specification.txt
@@ -94,7 +94,8 @@ The final output of the trace, after its generation and optional transport over
 the network, is expected to be either on permanent or temporary storage in a
 virtual file system. Because each event stream is appended to while a trace is
 being recorded, each is associated with a separate file for output.  Therefore,
-a stored trace can be represented as a directory containing one file per stream.
+a stored trace can be represented as a directory containing zero, one or
+more files per stream.
 
 Meta-data description associated with the trace contains information on
 trace event types expressed in the Trace Stream Description Language
@@ -1026,8 +1027,9 @@ event context to define a variant referring to the "id" field of the
 event header as selector.
 
 The target dynamic scope must be specified explicitly when referring to
-a field outside of the local static scope. The dynamic scope prefixes
-are thus:
+a field outside of the local static scope (a local static scope contains
+all fields present within the same scope, at the same nesting level).
+The dynamic scope prefixes are thus:
 
  - Trace Packet Header: <trace.packet.header. >,
  - Stream Packet Context: <stream.packet.context. >,