From d53599c850c2b9833b07c6059ba6bd638086c4f9 Mon Sep 17 00:00:00 2001 From: Marc Lichtman Date: Tue, 17 Dec 2024 13:22:01 -0500 Subject: [PATCH 1/2] Empty captures array implies start sample of 0 --- sigmf-schema.json | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/sigmf-schema.json b/sigmf-schema.json index 756ae42..49c29a6 100644 --- a/sigmf-schema.json +++ b/sigmf-schema.json @@ -158,7 +158,7 @@ "additionalProperties": true }, "captures": { - "description": "The `captures` Object is an array of capture segment objects that describe the parameters of the signal capture. It MUST be sorted by the value of each capture segment's `core:sample_start` key, ascending. Capture Segment Objects are composed of key/value pairs, and each Segment describes a chunk of samples that can be mapped into memory for processing. Each Segment MUST contain a `core:sample_start` key/value pair, which indicates the sample index relative to the Dataset where this Segment's metadata applies. The fields that are described within a Capture Segment are scoped to that Segment only and need to be explicitly declared again if they are valid in subsequent Segments. ", + "description": "The `captures` Object is an array of capture segment objects that describe the parameters of the signal capture. It MUST be sorted by the value of each capture segment's `core:sample_start` key, ascending. Capture Segment Objects are composed of key/value pairs, and each Segment describes a chunk of samples that can be mapped into memory for processing. Each Segment MUST contain a `core:sample_start` key/value pair, which indicates the sample index relative to the Dataset where this Segment's metadata applies. The fields that are described within a Capture Segment are scoped to that Segment only and need to be explicitly declared again if they are valid in subsequent Segments. While it is recommended there be at least one segment defined, if there are no items in the captures array it is implied that a single capture with the `core:sample_start` field equal to zero (no other metadata is implied), i.e., `"captures": []` implies `"captures": [{"core:sample_start": 0}]`.", "default": [], "type": "array", "additionalItems": false, From 521450bf7546c6a443afa684d574e0cb35c5ec84 Mon Sep 17 00:00:00 2001 From: Marc Lichtman Date: Tue, 17 Dec 2024 13:23:59 -0500 Subject: [PATCH 2/2] Clarify `captures` object description in schema --- sigmf-schema.json | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/sigmf-schema.json b/sigmf-schema.json index 49c29a6..5cc9c2d 100644 --- a/sigmf-schema.json +++ b/sigmf-schema.json @@ -158,7 +158,7 @@ "additionalProperties": true }, "captures": { - "description": "The `captures` Object is an array of capture segment objects that describe the parameters of the signal capture. It MUST be sorted by the value of each capture segment's `core:sample_start` key, ascending. Capture Segment Objects are composed of key/value pairs, and each Segment describes a chunk of samples that can be mapped into memory for processing. Each Segment MUST contain a `core:sample_start` key/value pair, which indicates the sample index relative to the Dataset where this Segment's metadata applies. The fields that are described within a Capture Segment are scoped to that Segment only and need to be explicitly declared again if they are valid in subsequent Segments. While it is recommended there be at least one segment defined, if there are no items in the captures array it is implied that a single capture with the `core:sample_start` field equal to zero (no other metadata is implied), i.e., `"captures": []` implies `"captures": [{"core:sample_start": 0}]`.", + "description": "The `captures` Object is an array of capture segment objects that describe the parameters of the signal capture. It MUST be sorted by the value of each capture segment's `core:sample_start` key, ascending. Capture Segment Objects are composed of key/value pairs, and each Segment describes a chunk of samples that can be mapped into memory for processing. Each Segment MUST contain a `core:sample_start` key/value pair, which indicates the sample index relative to the Dataset where this Segment's metadata applies. The fields that are described within a Capture Segment are scoped to that Segment only and need to be explicitly declared again if they are valid in subsequent Segments. While it is recommended there be at least one segment defined, if there are no items in the captures array it is implied that a single capture exists with `core:sample_start` equal to zero (no other metadata is implied), i.e., `\"captures\": []` implies `\"captures\": [{\"core:sample_start\": 0}]`.", "default": [], "type": "array", "additionalItems": false,