The API4KP section 7.2.3 is underspecified and should cover all of the datatypes needed for the APIs, including diagrams.

This includes any diagram changes required based on changes to the ontologies themselves through migration to the Commons Ontology Library as well as updates to dependency tables, e.g., on page 48, and relevant metadata.

The IDL should be changed to match the UML model. This includes:
All sequences are defaulted to infinite range, but many should be [0..1]
Many structure fields have cardinality [1], but should be [0..1]
Most IDL sequences are not used and should be removed
All UML enumerated types should correspond to IDL as enumerated types
The UML model defines classes with attributes and no operations. They should instead be represented by a simple data structure with fields. If one of these non-behavioral classes uses inheritance; the resulting "subclass" data structure type should contain an additional field that has a type of the "superclass" type.

The spec defines an api4kp:services:error datatype class used to wrap error messages..

A better, and standard, datatype for this very purpose is defined in https://www.rfc-editor.org/rfc/rfc7807. API4KP should reuse this datatype rather than creating something unique that is non-standard.

The datatype is also missing from the specification document and should be covered therein.

These are scattered about in the ontology, and should become subproperties of or be defined in terms of the commons 'uses' property.

This issue only impacts the ontologies, not the specification at this point.

ISO 1087 was revised in 2019 and our definitions should reflect any relevant changes as well as the references.

This change impacts the ontologies only, not the specification document.

The spec defines an api4kp:services:Error datatype class used to wrap error messages.

A better, and standard, datatype for this very purpose is defined in https://datatracker.ietf.org/doc/html/rfc7231

Consider aligning

This issue impacts the ontologies which are described in Annex A. There will be subsequent revisions to the ontologies and thus we will update the documentation in Annex A in a separate issue.

This is primarily about replacing the URIs of the relevant properties with those in the commons, including the dependencies in the table on page 50.

This issue is strictly against the model files and has limited impact on the specification document. The specification document, which is ptc/21-04-04, should be revised to include the MD diagrams without change to the underlying model under this issue, however.

Migration is important to improve the model files and gain functionality, including but not limited to canonical XMI generation for UML 2.5.1. The eclipse implementation in UML Designer uses an older version of UML and the eclipse dialect.

Thus, the artifacts required to resolve this issue include: (1) the revised XMI file, (2) the updated specification document including the revised images, and (3) the corresponding .svg image archive.