Removes 405 error response from YAML as this is not compliant with Commonalities API Design Guidelines
MEETING UPDATE :
PR merged on as this fixes a CAMARA non-compliance
PR #77: Reduce telco language in the API description
Removes reference to UE / User Equipment in description and replaces with "physical mobile device"
MEETING UPDATE :
PR merged on as no comments on proposed wording
PR #76: Rewrite text around treatment of primary / secondary MSISDN
Removes reference to a specific implementation of this, and rewrites using more generic language
Treatment of MSISDNs as phoneNumber remains the same - the phoneNumber will be treated as the secondary MSISDN, and can thus be used to identify the IMEI of all devices
MEETING UPDATE :
PR merged on as no comments on proposed rewording
PR #75: Fixes the missing required property in the the error response schema
Fixes the missing `required` property in the the error response schema
MEETING UPDATE :
PR merged on as this was a clear non-compliance with the Commonalities common JSON definitions
PR #67: Update CAMARA Mobile Device Identifier API.yaml
Commonalities v0.4.0 allows x-correlator to be any string, and not restricted to being a uuid.
Therefore "format: uuid" needs to be removed from the definition.
MEETING UPDATE :
No update
MEETING UPDATE :
PR merged on as no further comments
PR #66: Update CAMARA Mobile Device Identifier API.yaml
Updateinfosection of OAS to comply with Commonalities guidelines v0.4.0
MEETING UPDATE :
No update
ACTIONS:
PR merged on as no further comments
PR #64: Incorporate Commonalities WG recommendations on Simplification of Device object
Add Commonalities WG recommended text on "Identifying a device from the access token"
Add 422 error response option
Explicitly define request body as optional
Description updated to replace device with mobile subscription identifier as appropriate
MEETING UPDATE :
Huub commented that line 71 implies the access token follows a certain implementation
"The server will extract the mobile subscription identifier (e.g. MSISDN) from the access token, if available."
This text needs to be revised to be more implementation neutral. MSISDN to be replaced by phone number.
Keep PR open until to see if Commonalities revise current solution for Device object handling
MEETING UPDATE :
Merged on as no further comments
Issues
New Issues
Issue #71: Why "The API can be called by an application server or other 3rd party server"