Skip to content

Commit

Permalink
Split consumer and provider parts of requirement R0600 into two separ…
Browse files Browse the repository at this point in the history
…ate requirements.
  • Loading branch information
PaulMartinsen committed Dec 20, 2024
1 parent 222b1b9 commit 485d076
Showing 1 changed file with 21 additions and 6 deletions.
Original file line number Diff line number Diff line change
Expand Up @@ -69,15 +69,14 @@ include::../../listings/vol3-clause-biceps-content-example-timestamp-version.xml
.R0600
[sdpi_requirement#r0600,sdpi_req_level=shall]
****
A <<vol1_spec_sdpi_p_actor_somds_provider>> shall include the `sdpi:EpochSupport` extension and set `sdpi:EpochSupport/@Version=1` in every system clock `pm:ClockDescriptor`, used as part of its System Function Contribution (<<acronym_sfc>>), that uses epoch versioning for abrupt time adjustments. A <<vol1_spec_sdpi_p_actor_somds_consumer>> shall ignore all epoch version information on any system clocks that do not include the `sdpi:EpochSupport` extension in any MDIB version.
A <<vol1_spec_sdpi_p_actor_somds_provider>> shall include the `sdpi:EpochSupport` extension and set `sdpi:EpochSupport/@Version=1` in every system clock `pm:ClockDescriptor`, used as part of its System Function Contribution (<<acronym_sfc>>), that uses epoch versioning for abrupt time adjustments.
.Notes
[NOTE]
[%collapsible]
====
* The presence of `sdpi:EpochSupport` indicates support for this extension and related requirements.
* A <<vol1_spec_sdpi_p_actor_somds_provider>> can set `ext:MustUnderstand="true"` to exclude consumers that do not understand this extension.
* A <<vol1_spec_sdpi_p_actor_somds_consumer>> may rely on future versions of the extension being backwards compatible.
====
Expand All @@ -86,12 +85,28 @@ A <<vol1_spec_sdpi_p_actor_somds_provider>> shall include the `sdpi:EpochSupport
.R0601
[sdpi_requirement#r0601,sdpi_req_level=shall]
****
A <<vol1_spec_sdpi_p_actor_somds_consumer>> shall ignore all epoch version information on any system clocks that do not include the `sdpi:EpochSupport` extension in any MDIB version or if the `sdpi:EpochSupport/@Version` changes within a single sequence id.
.Notes
[NOTE]
[%collapsible]
====
* The `spdi:EpochSupport` extension is intended to immutable.
* A <<vol1_spec_sdpi_p_actor_somds_consumer>> may rely on future versions of the extension being backwards compatible.
====
****
.R0605
[sdpi_requirement#r0605,sdpi_req_level=shall]
****
The <<vol1_spec_sdpi_p_actor_somds_provider>> shall increment `sdpi:Epochs/@Version` by exactly one, beginning from 0, for every non-slewing time adjustment to any system clock used as part of its System Function Contribution (<<acronym_sfc>>).
****
.R0602
[sdpi_requirement#r0602,sdpi_req_level=shall]
.R0606
[sdpi_requirement#r0606,sdpi_req_level=shall]
****
A <<vol1_spec_sdpi_p_actor_somds_provider>> shall set the version of all versioned timestamps to 0 when it assigns a new MDIB sequence identifier (`pm:MdibVersionGroup/@SequenceId`).
Expand All @@ -104,8 +119,8 @@ A <<vol1_spec_sdpi_p_actor_somds_provider>> shall set the version of all version
====
****
.R0605
[sdpi_requirement#r0605,sdpi_req_level=shall]
.R0610
[sdpi_requirement#r0610,sdpi_req_level=shall]
****
A <<vol1_spec_sdpi_p_actor_somds_provider>> that versions timestamps in any `pm:AbstractMetricValue`, `pm:AbstractContextState`, `pm:AlertSystemState`, `pm:CalibrationInfo` and/or `pm:AlertConditionState` shall include, in every clock state update, the complete history of epoch offsets from the earliest version referenced in the MDIB to the current time-reference frame version.
Expand Down

0 comments on commit 485d076

Please sign in to comment.