GeoPose as a representation of OGC API - Moving Features temporal geometry

[jerstlouis]

The basic conceptual model / capabilities seems to overlap between OGC API - Moving Features (overview / draft) and GeoPose:

• MF coordinates / GP position (or parameters latitude / longitude in Advanced encoding)
• MF datetimes / GP validTime (in advanced encoding only? -- see Fixed (unified) the requirement's Part component defining method #70)
• MF orientations .angles / GP angles / quaternion

Could a GeoPose sequence possibly be supported as a representation for the OGC API - Moving Features temporal geometries response, providing the position, time and orientation along a sequence (see also opengeospatial/GeoPose#73)?

(also asked in GeoPose: opengeospatial/GeoPose#71)