Update set of files description

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

diff --git a/common-trace-format-specification.txt b/common-trace-format-specification.txt
index b924b6f22657ea5d5cdd78a204b5f22492deaf08..b4d9dc3135f5df88beda3a95fce2914e4cdf0697 100644 (file)
--- a/common-trace-format-specification.txt
+++ b/common-trace-format-specification.txt
@@ -1,4 +1,4 @@
-Common Trace Format (CTF) Specification (v1.7)
+Common Trace Format (CTF) Specification (pre-v1.8)
 
 Mathieu Desnoyers, EfficiOS Inc.
 
@@ -93,8 +93,9 @@ subset of the trace event types.
 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.
+being recorded, each is associated with a distinct set of files for
+output. Therefore, 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
@@ -662,8 +663,8 @@ Event packet header (all fields are optional, specified by TSDL meta-data):
 
 Event packet context (all fields are optional, specified by TSDL meta-data):
 
-- Event packet content size (in bytes).
-- Event packet size (in bytes, includes padding).
+- Event packet content size (in bits).
+- Event packet size (in bits, includes padding).
 - Event packet content checksum. Checksum excludes the event packet
   header.
 - Per-stream event packet sequence count (to deal with UDP packet loss). The
@@ -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. >,