SpaceSystem can mean multiple things

• Key: XTCE13-177
• Status: open  
• Source: Kratos RT Logic, Inc. ( Mr. Justin Boss)
• Summary:

  SpaceSystem in XTCE could mean a system/subsystem, a spacecraft, or perhaps a constellation of spacecraft. There should be a tag/attribute that specifies what the SpaceSystem represents. This would help with interpretation by implementing software.

• Reported: XTCE 1.2 — Mon, 18 Nov 2024 16:40 GMT
• Updated: Mon, 18 Nov 2024 16:40 GMT

Yamcs supports json syntax for array and aggregate parameter/args initial value

• Key: XTCE13-176
• Status: open  
• Source: NASA ( Mr. James Kevin Rice)
• Summary:

  Maybe we should align with yamcs

  initial value

  Initial (default) value given to a parameter or command argument.

  Note that this value can be overwritten for specific parameters, or command arguments using a column of the same name in the Commands and Parameters sheets.

  The value must be understandable for the used engineering type.

  For binary, use a hexadecimal notation.

  For booleans, use a value of true or false.

  For arrays, specify a value in JSON format: [-3, -2.4, 5].

  For aggregates, specify a value in JSON format:

  {member1: 1, member2: 2}

  .

• Reported: XTCE 1.2 — Thu, 7 Nov 2024 16:04 GMT
• Updated: Fri, 8 Nov 2024 20:16 GMT

BinaryEncoding Extension of SequenceContainer Requires SizeInBits Element

• Key: XTCE13-162
• Status: open  
• Source: Boeing ( Mr. David Overeem)
• Summary:

  Within the SequenceContainer element, there is a child element of BinaryEncoding that optionally provides some additional information to use for processing the SequenceContainer content. The BinaryEncoding element requires specifying the SizeInBits element, when that element is not always needed. Being required also presents a problem when using the ErrorDetectCorrect element in a non-deterministic length container.

• Reported: XTCE 1.2 — Fri, 19 Jul 2024 01:58 GMT
• Updated: Wed, 16 Oct 2024 00:41 GMT

ParameterToSet/Derivation is set to abstract and should not be

• Key: XTCE13-135
• Status: open  
• Source: NASA ( Mr. James Kevin Rice)
• Summary:

  ParameterToSet/Derivation is a MathOperationType which is abstract. Which means you cannot make an instance of it.

  A simple fix is to make a DerivationType extending MathOperationType.

• Reported: XTCE 1.2 — Wed, 21 Jun 2023 19:32 GMT
• Updated: Wed, 16 Oct 2024 00:41 GMT

Access to command arguments in transmission constraints and command verifiers

• Key: XTCE13-125
• Status: open  
• Source: Space Applications Services ( Nicolae Mihalache)
• Summary:

  Sometimes the constraints and/or verifies associated to a command may depend on the value of the arguments of the command sent. For example setting a thermostat to a certain setpoint may have a constraint which will only allow a given setpoint in a specific operational mode.
  A verifier can compare the setpoint sent as command argument with the setpoint known in the spacecraft and received as a TM parameter.

  To achieve this, arguments references should be allowed in the definition of the constraints/verifiers.

  In practice:

  • TransmissionConstraintType should extend the ArgumentMatchCriteriaType (instead of MatchCriteriaType)
  • CommandVerifierType should allow elements of type ArgumentInputAlgorithmType , ArgumentBooleanExpressionType and ArgumentComparisonType (instead of the non argument variety)

  All the Argument* types are superset of the corresponding non-argument types so by doing this change, the schema will be backward compatible.

  Note: a similar request could be argued for ParametrToSetType to allow setting a parameter to a value computed based on the user defined argument of the command. However since there is no ArgumentMathOperationType, no easy solution can be immediately seen without adding extra types.

• Reported: XTCE 1.2 — Thu, 22 Apr 2021 08:17 GMT
• Updated: Wed, 16 Oct 2024 00:41 GMT

Data encodings: FromBinaryTransformAlgorithm/ToBinaryTransformAlgorithm SizeInBits should be optional

• Key: XTCE13-128
• Status: open  
• Source: Space Applications Services ( Nicolae Mihalache)
• Summary:

  In data encoding definitions (currently only BinaryDataEncoding but see my other issue XTCE13-124), XTCE should allow the algorithm used in ToBinaryTransformAlgorithm and FromBinaryTransformAlgorithm to determine the size of the data on the wire.

  Thus the SizeInBits which is currently mandatory should be made optional when an algorithm is used.

• Reported: XTCE 1.2 — Mon, 3 May 2021 14:17 GMT
• Updated: Wed, 16 Oct 2024 00:41 GMT

BaseConditionsType too broad

• Key: XTCE13-114
• Status: open  
• Source: NASA ( Mr. James Kevin Rice)
• Summary:

  Our for a list<element> in the BooleanExpression which made a base type called – BaseConditionsType is a little too broad because it include sub-type now only relevant on the command side.

  we should probably have a ArgumentBaseConditionsType.

  The children of it now are:

  ANDedConditionsType
  ArgumentANDedConditionsType
  ORedConditionsType
  ArgumentORedConditionsType
  ComparisonCheckType
  ArgumentComparisonCheckType

• Reported: XTCE 1.2 — Fri, 10 Jul 2020 17:33 GMT
• Updated: Wed, 16 Oct 2024 00:41 GMT

Dynamic look up should have integer and float forms

• Key: XTCE13-109
• Status: open  
• Source: NASA ( Mr. James Kevin Rice)
• Summary:

  Dynamic lookup is sprinkled about the text to (only?) retrieve a numeric value but perhaps there should be an integer and float form. For example in calculating a dynamic array index, would it make sense if the referred to parameter is a float? we can agree any non-numeric is a error. If it's a float or integer, the slope and intercept are doubles – suggesting a double result. Well that may produce a fractional value of an array index – that doesn't make sense. one can round or chop as one sees fits but that's not documented. in this case integer only dynamic value would make more sense – the slope and intercept would be int/long and it would be in error to ref anything but an integer parameter type. other cases may allow for either data type. [edit] Discrete lookup DOES NOT have the same issue – it's value is a float. It however does need a default. I made an issue for that.

• Reported: XTCE 1.2 — Thu, 9 Jul 2020 19:22 GMT
• Updated: Wed, 16 Oct 2024 00:41 GMT

Revert change to CalibratorType base type

• Key: XTCE13-107
• Status: open  
• Source: Northrop Grumman ( Mr. Joseph Vlietstra)
• Summary:

  XUSP 1.2 changed the base type of CalibratorType from OptionalNameDescriptionType to the new BaseCalibratorType. This change eliminated the previous support for <LongDescription> and <AliasSet>. These elements are supported in the XUSP 1.0 profile and are used in existing databases.

• Reported: XTCE 1.2 — Wed, 25 Mar 2020 20:07 GMT
• Updated: Sat, 14 Sep 2024 14:34 GMT

Clarify RepeatEntry's values and what they mean

• Key: XTCE13-143
• Status: open  
• Source: NASA ( Mr. James Kevin Rice)
• Summary:

  Firstly because repeat is optional, it seems intuitive that this is the same as repeat=0. And that intuitively means the entry repeats 0 times, which means it appears 1 time in the container entry list. Likewise a repeat=1, means the entry appears 2 times and forth. This to me makes sense but maybe it doesn't.
  The syntax right now is broad and would allow all sort of values including negative ones. It's not clear that that would be anything but an error.
  Given all that we should say something about this in the annotation at the very least. And since FixedValue is a long we could change it to positive-only or perhaps non-negative. The DiscreteLookup value's type could also be modified (we'd have to make a "PositveOnlyDiscreteLookup" or some such). The last is a DynamicLookup and that would have to be enforced outside the syntax, we could imply it by calling it "PositiveOnlyDynamicLookup" or similar.
  Finally add annotation.

• Reported: XTCE 1.2 — Wed, 17 Apr 2024 18:43 GMT
• Updated: Tue, 30 Jul 2024 00:57 GMT

Simplify/align alarm severities across OMG specifications

• Key: XTCE13-142
• Status: open  
• Source: Kratos RT Logic, Inc. ( Mr. Justin Boss)
• Summary:

  To align with other specifications within the OMG and AstroUXDS guidance, deprecate the watch and severe alarm severity levels.

• Reported: XTCE 1.2 — Wed, 20 Mar 2024 20:36 GMT
• Updated: Tue, 30 Jul 2024 00:57 GMT

Add an optional attribute to ComparisonList to make it all ORs

• Key: XTCE13-141
• Status: open  
• Source: NASA ( Mr. James Kevin Rice)
• Summary:

  For some reason this idea flew into my funnel this morning. I was looking at the ComparisonList and noticed the annotation to it said there's an implied 'and' between all the comparisons in the list.
  I then thought: Why not add an attribute to override that to set to it all ORs? Why would that be a bad thing?
  Unable to come up with any reason that this would be a bad thing, I decided it must be a good thing and that a good thing should be an issue.
  The main reason to support the OR case is that it's simply a little easier to build out the comparisonlist than the booleanexpression. And one assumes that if it's a good thing to have an ANDed ComparisonList for convenience, that it seems like symmetrically speaking it would be a good thing to have ORed ComparisonList for conveniences as well. Basically this is just a suggested small change for the convenience purposes.

• Reported: XTCE 1.2 — Wed, 7 Feb 2024 16:02 GMT
• Updated: Tue, 30 Jul 2024 00:57 GMT

Reconsider if Specific Color Names Should be Referenced

• Key: XTCE13-140
• Status: open  
• Source: Boeing ( Mr. David Overeem)
• Summary:

  Given that alarm consequence/significance labels are concepts and colors are implementations, should the XTCE schema refer to the colors by name? Perhaps it should refer to implementation of suggest AstroUX as a reference?

• Reported: XTCE 1.2 — Thu, 7 Dec 2023 21:23 GMT
• Updated: Tue, 30 Jul 2024 00:57 GMT

Non-ASCII characters in XSD annotations cause tooling issues

• Key: XTCE13-129
• Status: open  
• Source: Kratos RT Logic, Inc. ( Mr. Justin Boss)
• Summary:

  Remove use of non-ASCII characters to improve tooling ease of use. These characters are utilized within Annotation fields.

  Symbols to change:
  ‘
  ’ '
  “
  ”
  –

  Also, in ArgumentAssignmentListType, add a single quote before "power on"

• Reported: XTCE 1.2 — Tue, 15 Jun 2021 18:11 GMT
• Updated: Tue, 30 Jul 2024 00:57 GMT

CNES CCSDS -- Want ArgumentEntryRef in CommandContainerSet/CommandContainer

• Key: XTCE13-72
• Status: open  
• Source: NASA ( Mr. James Kevin Rice)
• Summary:

  "The issue is declared Closed.
  The problem has not been fixed. It is still impossible to reference an argument in a CommandContainerSet/CommandContainer/RefEntry."

• Reported: XTCE 1.2 — Wed, 2 Oct 2019 14:54 GMT
• Updated: Tue, 30 Jul 2024 00:57 GMT

Variable string size specification enforces one of DynamicValueType or DiscreteLookupListType

• Key: XTCE13-127
• Status: open   Implementation work Blocked
• Source: Space Applications Services ( Nicolae Mihalache)
• Summary:

  In addition to the clarity issues highlighted by XTCE13-30, the current definition of StringDataEncoding has a major drawback for variable strings: the VariableStringType enforces one of DynamicValueType or DiscreteLookupListType.

  However the size of the string can be very well determined by the other two methods LeadingSize or TerminationChar. Usage of LeadingSize/TerminationChar in combination with the enforced DynamicValueType/DiscreteLookupListType does not make sense when the string fills completely the allocated buffer and so the size of the string determines the size of the buffer.

  In my opinion having a variable size buffer with a variable string inside that buffer is much less common (never heard of it in fact) than having a fixed size buffer with a variable string inside or a variable string with no buffer (the buffer is the string).

  Suggest to make the DynamicValueType/DiscreteLookupListType optional.

• Reported: XTCE 1.2 — Fri, 30 Apr 2021 07:34 GMT
• Updated: Sun, 21 Jul 2024 15:39 GMT

ArgumentType References Mixed with ParameterTypes in Key

• Key: XTCE13-155
• Status: open  
• Source: Boeing ( Mr. David Overeem)
• Summary:

  The name constraint for ArgumentType elements enforces uniqueness with ParameterType elements that appear in the CommandMetaData.

  <key name="argumentTypeNameKey">
  <annotation>
  <documentation xml:lang="en">This key ensures a unique argument type name at the system level.</documentation>
  </annotation>
  <selector xpath="xtce:CommandMetaData/xtce:ArgumentTypeSet/|xtce:CommandMetaData/xtce:ParameterTypeSet/"/>
  <field xpath="@name"/>
  </key>

  This does not make sense because "argumentTypeRef" is distinct from "parameterTypeRef" in all cases.

• Reported: XTCE 1.2 — Sun, 2 Jun 2024 20:05 GMT
• Updated: Tue, 25 Jun 2024 00:36 GMT

clarify semantics of context cals (possibly same as context alarms)

• Key: XTCE13-145
• Status: open  
• Source: NASA ( Mr. James Kevin Rice)
• Summary:

  Clarify that the list of contexts is in a specific ordering, and that as it stands now the <xsd:sequence> is in an order and that's the ordering. Or, consider adding a required "ordering" attribute to enforce the order. Or perhaps that subtly changes the semantics and we don't want to do any of it in which case we might say that...

• Reported: XTCE 1.2 — Wed, 24 Apr 2024 15:59 GMT
• Updated: Tue, 25 Jun 2024 00:36 GMT

Clarify Behavior of Context Alarms Only Containing a Match

• Key: XTCE13-139
• Status: open  
• Source: Boeing ( Mr. David Overeem)
• Summary:

  It is unclear in the documentation how it should be handled when a parameter defines a context alarm for which only a match element is provided. This is valid in the schema.

• Reported: XTCE 1.2 — Thu, 7 Dec 2023 16:20 GMT
• Updated: Tue, 25 Jun 2024 00:36 GMT

rangeForm annotation needs work

• Key: XTCE13-73
• Status: open  
• Source: NASA ( Mr. James Kevin Rice)
• Summary:

  The rangeForm annotation is vague and needs improvement. There are two places it occurs – one at the attribute level with another brief mention at the schema type:
  "A value of outside specifies that the most severe range is outside all the other ranges: -severe -critical -distress -warning -watch normal +watch +warning +distress +critical +severe. A value of inside "inverts" these bands: -green -watch -warning -distress -critical severe +critical +distress +warning +watch. The most common form used is "outside" and is the default."

  The key problem is the term "inverts" is not really defined and so the entire explanation is overly general.

• Reported: XTCE 1.2 — Thu, 3 Oct 2019 14:35 GMT
• Updated: Tue, 25 Jun 2024 00:36 GMT

Change Alarm Element Bad Attributes

• Key: XTCE13-138
• Status: open  
• Source: Boeing ( Mr. David Overeem)
• Summary:

  Not sure that specifying range form in a change alarm makes sense as the min/max are relative to the value itself. In addition, both exclusive and inclusive range values are allowed and that doesn't seem to make sense for exclusive.

• Reported: XTCE 1.2 — Wed, 6 Dec 2023 18:28 GMT
• Updated: Tue, 25 Jun 2024 00:36 GMT

FixedValueEntry, maybe it's not as good as it could be

• Key: XTCE13-137
• Status: open  
• Source: NASA ( Mr. James Kevin Rice)
• Summary:

  FixedValueEntry has a hard coded hexBinary value that's supposed to be in "spacecraft order". There's a now optional name in 1.2.

  ITOS and ASIST capture the same info slightly differently. The value is in human-readable form, (e.g "5331" or whatever it is that you can read and understand). But Bit/Byte order are provided as modifiers to the field/entry definition so that the software will do the right thing and encode it properly for the final destination on the spacecraft. ITOS/ASIST require the name and other associated the meta data for these fields.

  So there's similarities overall between them but the encoding aspect is the key difference.

  The upsides to their approach are (there may be more):

  • when you see the definition, it makes some sense to you
  • the software takes care of the encoding and in a way it is then documented as to what is the both the value is and how it's going to be encoded for the final destination.

  The downsides are (could be more):

  • well something will have to be done to see the final bit values ...
  • there's more to write out to build the definition

  Is there a case to be made to change, or modify the existing fixedvalueentry? What would the approach be?

  1) maintain pure backwards compatibility: add a second variation "uservalueentry" that supplies it as described above and includes a local bit/byteorder
  2) modify fixedavalueentry itself and keep a kind of conceptual compatibility...

  What do you think?

• Reported: XTCE 1.2 — Tue, 14 Nov 2023 16:15 GMT
• Updated: Tue, 25 Jun 2024 00:36 GMT

RelativeTime's ChangePerSecondRangeAlarm should be a TimeChangesPerSecondAlarmType

• Key: XTCE13-136
• Status: open  
• Source: NASA ( Mr. James Kevin Rice)
• Summary:

  RelativeTimeParamaterType static and change alarms are both TimeAlarmRangesType. At the very least it would be clearer if the ChangePerSecondRangeAlarm is its own type.
  A simple solution would be to create a new type (TimeChangePerSecondRangeAlarmType) and have it extend TimeAlarmRangesType.
  (Assuming that it's correct that both of these should describe alarms in the same using same underlying type.)

• Reported: XTCE 1.2 — Mon, 17 Jul 2023 16:11 GMT
• Updated: Tue, 25 Jun 2024 00:36 GMT

Possible typo of word "difference" instead of "different"

• Key: XTCE13-134
• Status: open  
• Source: Kratos RT Logic, Inc. ( Mr. Justin Boss)
• Summary:

  "There are eight different verifiers each associated with difference states in command processing"

• Reported: XTCE 1.2 — Wed, 21 Sep 2022 20:59 GMT
• Updated: Tue, 25 Jun 2024 00:36 GMT

Invalid schema exception with xerces parser

• Key: XTCE13-130
• Status: open  
• Source: Kratos RT Logic, Inc. ( Mr. Justin Boss)
• Summary:

  We have experienced the following error with the Xerces XML parser:

  Exception thrown at 0x00007FFB902D4F69 in InstallDB4.exe: Microsoft C++ exception: xercesc_3_0::InvalidDatatypeValueException at memory location 0x000000000014D5A0.

  It seems to be driven by this line:
  <attribute name="idlePattern" type="xtce:FixedIntegerValueType" default="0x0"/>

  Changing the default value to "0" seems to make the problem go away.

  Can we change the line instead to:
  <attribute name="idlePattern" type="xtce:FixedIntegerValueType" default="0"/>

• Reported: XTCE 1.2 — Thu, 20 Jan 2022 13:58 GMT
• Updated: Tue, 25 Jun 2024 00:36 GMT

FromBinaryTransformAlgorithm/ToBinaryTransformAlgorithm should be allowed for all data encodings

• Key: XTCE13-124
• Status: open  
• Source: Space Applications Services ( Nicolae Mihalache)
• Summary:

  Currently the FromBinaryTransformAlgorithm/ToBinaryTransformAlgorithm are allowed only for BinaryDataEncodingType with the comment "Used to convert binary data from an application data type to binary data". However the binary data encoding is used to encode/decode binary data, so not any application data (float, integer, time,...).

  We believe it is more beneficial to allow these algorithms to all data encoding types.

  For example a FromBinaryTransformAlgorithm attached to a IntegerDataEncoding can extract a varint like the ones used in protobuf (https://developers.google.com/protocol-buffers/docs/encoding#varints).

  Similarly a ToBinaryTransformAlgorithm attached to a FloatDataEncoding can be used to encode a floating point number in an exotic format; for example bfloat16 is commonly used in AI chips (https://en.wikipedia.org/wiki/Bfloat16_floating-point_format)

• Reported: XTCE 1.2 — Thu, 22 Apr 2021 07:57 GMT
• Updated: Tue, 25 Jun 2024 00:36 GMT

Is rangeForm specialization needed for Change and Multi band alarms?

• Key: XTCE13-74
• Status: open  
• Source: NASA ( Mr. James Kevin Rice)
• Summary:

  RangeForm now appears in Static, Change and the multi band. It's not clear these all make sense to me.

  In the static ranges – having the red be the most severe inner band and green "good" on the outside does make sense although I get the impression the use cases are less in number than the standard way folks think of limits. (you're going too fast! not – you're not going fast enough!)

  In the change alarm, which I think of mainly as deltas – again intuitively checking for big changes make sense. Unwanted big jumps are intuitive. But unwanted little jumps? That is big jumps are good? Is there a real use case – perhaps we can jam it into the annotation.

  Finally for the multirange alarm. The rangeForm is at each band. I suspect but don't know that this was to change the range set meaning...
  Intuitively "inside" would be something like this: [min, max] – where x is between them is "ok" ...

  And "outside" would be (-inf, min] and [max, inf) ... that is ranges point 'away'...

  But maybe not – who knows!? Given that though the default is "outside" when perhaps most would want it to be "inside" etc...

  I just wonder if we have done this correctly or its slipped through and is overly general because we inherited the various types, etc...

• Reported: XTCE 1.2 — Thu, 3 Oct 2019 14:46 GMT
• Updated: Tue, 25 Jun 2024 00:36 GMT

String Encoding Length descriptions needs further clean up

• Key: XTCE13-30
• Status: open  
• Source: NASA ( Mr. James Kevin Rice)
• Summary:

  The current schema improves upon XTCE 1.1 but still has issues. Firstly it lacks overall clarity and simple syntax. Second it appears to give 2 ways to describe an overall "string box" and dynamic part which may be confusing to some (we should favor one over the other). See for example Fixed plus one of the TerminatingChar or LeadingSize, or Variable/DynamicValue and maxSizeInBits. Also maxSizeInBits is required and this may be a problem in some scenarios. Finally the choice of syntactic element does make it possible to say that variable length has a dynamic look up terminatingChar and LeadingSize.

  The overall use cases of support are:

  • fixed string
  • fixed box, variable string
  • variable string but overall max size (simlar to above)
  • variable string unlimited

  Here's a longer write up:

  1) Fixed string, like as in literally:

  StringDataEncoding/SizeInBits/Fixed/FixedValue

  2) Fixed string BOX but variable inside that...

  StringDataEncoding/SizeInBits/Fixed/FixedValue AND one of Fixed/LeadingSize or Fixed/TerminatingChar

  3) Fixed string BOX but variable inside that... yeah we can say this two ways then:

  StringDataEncoding/Variable/@maxSizeInBits=sizeOf(StringBox) AND one of DynamicValue or DiscreteValue to look up the length from it, and then optionally either LeadingSize or TerminationChar or both even too

  This one is terribly confusing...

  4) Variable and Max size

  StringDataEncoding/Variable/Dynamic|Discrete plus required maxSizeInBits and then optionally either LeadingSize or TerminationChar too

  5) Variable but no max size stated in source material

  StringDataEncoding/Variable/Dynamic|Discrete set maxSizeInBits to ginormous and probably just ignore and then optionally either LeadingSize or TerminationChar too

  So #1 and #2 make sense but are a tad unwieldy syntax wise... well we are probably a little stuck there in regard to "backwards compatibility". This is probably the most used, these two.

  I think #4 makes sense – although mixing in the leading size or termination char seems either just plain confusing or weird...

  #5 is unfortunate but making @maxSizeinBits optional seems quick fix OR the workaround isn't necessarily bad.

  The "let's set everything" #3 isn't great but could be factored away in documentation

• Reported: XTCE 1.2 — Mon, 14 May 2018 17:31 GMT
• Updated: Sun, 2 Jun 2024 16:38 GMT

reference to aggregate members and arrays

• Key: XTCE13-126
• Status: open  
• Source: Space Applications Services ( Nicolae Mihalache)
• Summary:

  The XTCE spec is not very clear on how the aggregate members can be referenced (for example in match criterias). The doc of AggregateParameterType reads:
  "Each member may be addressed by the dot syntax similar to C such as P.voltage if P is the referring parameter and voltage is of a member of P’s aggregate type. See MemberType, MemberListType, DataEncodingType, NameReferenceType, and AggregateDataType".

  However the definition of "NameReferenceType" is silent about aggregates and the "." (dot) character is not allowed to be used in a reference (except in the "./" where it denotes "current space system). The reference suggested above "P.voltage" is invalid.

  In some examples over the internet references to aggregate members are found using standard "/" separator. However this is problematic because a reference like "/A/B/C" is ambiguous, could translate into:
  A (space system)/B(space system)/C(parameter name)
  or
  A(space system)/B(parameter name)/C(aggregate member name)

  Suggest to allow dot notation to reference aggregate members. Similarly allow "[idx]" to reference array indices.

  For example a reference "/A/B.C[3]" can be unambiguously understood as:
  A(space system)/B(parameter name).C(aggregate member name of type array) [3] (index in the C array)

  Perhaps NameReferenceType can be made less restrictive or another type can be defined and used in the ParameterRefType definition.

• Reported: XTCE 1.2 — Fri, 23 Apr 2021 07:38 GMT
• Updated: Wed, 27 Sep 2023 19:25 GMT

List