TEX 1.1 RTF Avatar
  1. OMG Issue

TEX11 — Compositions are not intended to be reverse navigable

Open Closed All
  • Key: TEX11-48
  • Status: closed  
  • Source: BAE SYSTEMS ( Mr. Simon Mettrick)
  • Summary:

    Most composition relations in the data model part of the PIM are modelled with navigability from the part to the whole. For example the EntityPayload section and its composition of EntityMetaData.
    This causes issues with automated PSM mapping and generation as it calls for additional attributes to support such mapping, which are neither expected or required.
  • Reported: TEX 1.0 — Mon, 14 Aug 2023 12:36 GMT
  • Disposition: Resolved — $issue.fixedSpecification.name
  • Disposition Summary:

    Introduce Directional Navigability into Compositions

    Change these compositions to be navigable only from whole to part (listed whole -> part left-to-right).
    EntityPayload -> EntityMetaData
    EntityPayload -> EntityMetaData
    AggregateEntity -> EntityPayload
    CompositeEntity -> ShapedEntity
    EntityList -> EntityRef
    Bearing -> PositionCoordinate
    (ditto all other specialisations of ShapedEntity)
    ShapedEntity -> Categorization3D
    ShapedEntity -> CategorizationData
    ShapedEntity -> ExtendedData
    ShapedEntity -> InterpolationMethodology
    GroupPayload -> EntityRef
    GroupPayload -> GroupMetaData
    GroupPayload -> EntityRelationship
    EntityRelationship -> EntityRef (both)
    GroupList -> GroupRef
    GroupMetaData -> ExtensionSchema
    GroupMetaData -> CoordinateUnits
    CoordinateUnits -> DistanceUnits (and other enumerations)
    EntityHistoryPayload -> EntityPayload
    EntityChangeEvent -> EntityPayload
    EntityChangeEvent -> EntityRef
    EntityChangeSinkEvent -> EntityRef
    GroupChangeEvent -> GroupPayload
    GroupChangeSinkEvent -> GroupPayload
    GroupChangeEvent -> GroupRef
    GroupChangeSinkEvent -> GroupRef
    EntityChangeSinkEvent -> EntityPayloadChunk
  • Updated: Tue, 9 Jan 2024 19:40 GMT
  • Attachments: