Problem description
Three items from #192 are still open after that issue was closed:
code/API_definitions/device-identifier.yaml: the 403Forbidden example key is spelled Permision Denied (one s). The description immediately below it spells the word correctly.README.md, ## Scope: the capability list names retrieve-identifier, retrieve-type and the new match-identifier, but not retrieve-ppid, which was added in r2.2.documentation/API_documentation/Device Identifier User Story.md, "Device Type" story summary: TAC is expanded as "Type Approval Code". info.description and DeviceType.description in the API definition both use "Type Allocation Code", which is the correct expansion.
Expected action
- Rename the example key to
Permission Denied.
- Add a
## Scope bullet for retrieving the pseudonymous device identifier (PPID).
- Change "Type Approval Code" to "Type Allocation Code" in the user story.
Additional context
Follow-up to #192, closed with these three items unaddressed. All three are cosmetic or documentation-only; none affects the API contract.
Problem description
Three items from #192 are still open after that issue was closed:
code/API_definitions/device-identifier.yaml: the403Forbiddenexample key is spelledPermision Denied(ones). Thedescriptionimmediately below it spells the word correctly.README.md,## Scope: the capability list names retrieve-identifier, retrieve-type and the new match-identifier, but not retrieve-ppid, which was added in r2.2.documentation/API_documentation/Device Identifier User Story.md, "Device Type" story summary: TAC is expanded as "Type Approval Code".info.descriptionandDeviceType.descriptionin the API definition both use "Type Allocation Code", which is the correct expansion.Expected action
Permission Denied.## Scopebullet for retrieving the pseudonymous device identifier (PPID).Additional context
Follow-up to #192, closed with these three items unaddressed. All three are cosmetic or documentation-only; none affects the API contract.