Prepare r1.1 v0.5.0-rc.1

[maheshc01]

What type of PR is this?

Add one of the following kinds:

• documentation

What this PR does / why we need it:

Creating the release candidate for Fall 25

Which issue(s) this PR fixes:

Fixes #17
Alignment with latest commonalities and ICM guidelines.

Special notes for reviewers:

Changelog input

 release-note

Additional documentation

This section can be blank.

docs

[maheshc01]

change log has not been updated yet. will do it after the other issue #15 is complete

[maheshc01]

all the open issues have been closed in this repo.
Have updated the changelog based on all the latest changes.
Please note that i have use r1.1 for this release candidate as this is the first release in the new repo created for application profiles. I used device status repo as reference for taking this approach.

[rartych]

Critical Issues Requiring Immediate Attention

• Error Responses Template: Missing required error responses template components: API Readiness Checklist (info.description)
  • see Not Documented Error Responses info.description section Commonalities#457
• ExternalDocs: Missing externalDocs object (externalDocs)
  • https://github.com/camaraproject/Commonalities/blob/main/documentation/CAMARA-API-Design-Guide.md#54-externaldocs-object

 externalDocs:
  description: Product documentation at CAMARA
  url: https://github.com/camaraproject/{apiRepository}
 # {apiRepository} MUST be replaced by the CAMARA API Repository name where the API specification is hosted.

• Components: Missing required XCorrelator schema (components.schemas)
  • see X-Correlator Format Change Commonalities#463
  • update and test definitions XCorrelator schema in CAMARA_common.yaml and format checking step in testing template Commonalities#480

[urvika-v]

@rartych @hdamker @Kevsy
I have addressed the critical issues raised. Could you please review.

[rartych]

@urvika-v Thank you - there are no more critical issues - I'll continue the review.

Quick fix: The Readiness checklist needs to be updated to the template:
https://github.com/camaraproject/ReleaseManagement/blob/main/documentation/API-Readiness-Checklist.md

• row 13 was added - it should contain the link to https://lf-camaraproject.atlassian.net/wiki/x/iQFmBQ

[urvika-v]

@rartych Updated API-Readiness-Checklist

[rartych]

I think the first line in the Release Information section in README.md will be outdated after r1.1 .
The simplest solution is to uncomment the lines already present in the file and place them in the right places:

<!-- Pre-releases of this sub project are available in https://github.com/camaraproject/ApplicationProfiles/releases -->

<!-- For changes see [CHANGELOG.md](https://github.com/camaraproject/ApplicationProfiles/blob/main/CHANGELOG.md) -->

BTW, More detailed template for this section is expected for M4.

[rartych]

In API-Readiness-Checklist

|  2 | Design guidelines from Commonalities applied |   O   |         M         |    M    |    M   | Y  |  r3.2    |
|  3 | Guidelines from ICM applied                  |   O   |         M         |    M    |    M   | Y    |  r3.2  |

links to Commonalites and ICM release are expected:

|  2 | Design guidelines from Commonalities applied |   O   |         M         |    M    |    M   |   Y   |  [r3.2](https://github.com/camaraproject/Commonalities/releases/tag/r3.2)     |
|  3 | Guidelines from ICM applied                  |   O   |         M         |    M    |    M   |   Y   |  [r3.2](https://github.com/camaraproject/IdentityAndConsentManagement/releases/tag/r3.2)     |

[rartych]

Is error

            GENERIC_404_IDENTIFIER_NOT_FOUND:
              description: Some identifier cannot be matched to a device
              value:
                status: 404
                code: IDENTIFIER_NOT_FOUND
                message: Device identifier not found

relevant for this API? If so maybe the description and message can be updated - this can be discussed and addressed by the team before M4

Similarly:

            GENERIC_403_INVALID_TOKEN_CONTEXT:
              description: Reflect some inconsistency between information in
                some field of the API and the related OAuth2 Token
              value:
                status: 403
                code: INVALID_TOKEN_CONTEXT
                message: "{{field}} is not consistent with access token."

[rartych]

@urvika-v Almost done!
Please include the correction in changelog and address #16 (comment).

[rartych]

Please check the README.md as indicated in #16 (comment)

[maheshc01]

section is expected for M4.

@rartych readme has been update. let me know if this looks good.

[rartych]

Looks good from Release Management perspective

[Kevsy]

LGTM, approved as codeowner.