What's needed?
The Lifetime fields need to be better documented. E.g., one field here is not well documented. It does not specify what should be the behaviour if
- the
operational_lifetime field is set to None, or
- if it is present but both start and stop fields in the
Lifetime message are empty.
Proposed solution
We need to define the requirement here. Here are two proposals:
Proposal 1
Entities which have lifetimes set to None are invalid.
Proposal 2
Entities which have lifetimes set to None are valid, but only if at least one of the start_timestamp and end_timestamp fields are specified.
For all the above proposals, if only the start_timestamp is provided, then the component is valid and active. If the end_timestamp is provided, the component is considered valid, but inactive past the end timestamp.
Use cases
No response
Alternatives and workarounds
No response
Additional context
No response
What's needed?
The
Lifetimefields need to be better documented. E.g., one field here is not well documented. It does not specify what should be the behaviour ifoperational_lifetimefield is set toNone, orLifetimemessage are empty.Proposed solution
We need to define the requirement here. Here are two proposals:
Proposal 1
Entities which have lifetimes set to
Noneare invalid.Proposal 2
Entities which have lifetimes set to
Noneare valid, but only if at least one of thestart_timestampandend_timestampfields are specified.For all the above proposals, if only the
start_timestampis provided, then the component is valid and active. If theend_timestampis provided, the component is considered valid, but inactive past the end timestamp.Use cases
No response
Alternatives and workarounds
No response
Additional context
No response