-
Key: TEX11-4
-
Status: closed Implementation work Blocked
-
Source: BAE SYSTEMS ( Mr. Simon Mettrick)
-
Summary:
The DDS IDL for the schema of extended data is
"ExtendedData__id_type _id;"
This is missing the name, missing description and is an inappropriate underlying type - int. It would be natural to refer to a schema through a schema prefix. -
Reported: TEX 1.0 — Fri, 14 Oct 2022 07:38 GMT
-
Disposition: Resolved — $issue.fixedSpecification.name
-
Disposition Summary:
Schema to be reference object itself that can be included by-value
Change the association to the ExtensionSchema class in the PIM to be a composition.
Also make it mandatory (note that the name of the Schema could be empty if used without a formal schema).
Also schema should be the name of the target role not of the relation. -
Updated: Tue, 9 Jan 2024 19:40 GMT
-
Attachments:
- EntityPayload - 2 of 2 TEX11-30.png 755 kB (image/png)
TEX11 — DDS Mapping for schema of extended data is unclear
- Key: TEX11-4
- OMG Task Force: TACSIT Data Exchange (TEX) 1.1 RTF