Skip to content

Remove unused and pass-through common wrappers from qos-booking.yaml #152

Closed

Description

@hdamker

Problem description

Latitude and Longitude in components/schemas of qos-booking.yaml are local pass-through wrappers (only a $ref to CAMARA_common.yaml) that nothing references, so CAMARA Validation reports S-211 ("Potentially unused component") on both. They became orphans when the local Point was turned into a wrapper to the common Point, which references the common Latitude/Longitude itself.

The remaining pass-through wrappers (x-correlator parameter and header, SinkCredential, Port, PointList, Point, Device, DeviceResponse, ErrorInfo) have no local content either, while the Commonalities r4.4 API template references common components directly.

Expected behavior

Remove Latitude and Longitude. Replace the other pass-through wrappers by direct references to the CAMARA_common.yaml / CAMARA_event_common.yaml components and delete the wrappers. Error response wrappers (responses/Generic4xx) and securitySchemes stay as they are.

Alternative solution

Delete only Latitude and Longitude.

Additional context

Scope is qos-booking.yaml; qos-booking-and-assignment.yaml is not changed. A PR implementing this will follow.

Activity

  1. self-assigned this
    on Oct 2, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions