API description review finding (Location Retrieval)

[MarkusKuemmerle]

Problem description
CAMARA Outreach team is reviewing all API descriptions on the CAMARA website using a checklist.

Possible evolution
In case of findings an issue is opened to ask the Sub Project to enhance the API description in the Wiki, and then open an issue at the Marketing repo so that the Outreach team then can update the website.

Alternative solution

Additional context

Findings in Location Retrieval:

• In the API description "mobile line" is used instead of "mobile phone numbers" like in other API descriptions.
• The description could more explicitly discuss expected location accuracy and privacy considerations.
• Use Case section: Please check if you can link exisiting use cases in the GSMA use case library
• Use Case names: Use capitals for all main words (same style as all other API descriptions)
• Benefits: Change "Operational efficiency" to "Operational Efficiency" (typo)
• The image should visualize the most interesting use case to attract customers and developers. Please provide us instructions how such a visual should be built and look like. We ask the LF creative team to create the visual. You can put the instructions also in the wiki page below the visual.
• Location category: Some descriptions could include more explicit discussion of location accuracy, data freshness, and privacy constraints, which are important selection criteria for developers.

[bigludo7]

Hello @MarkusKuemmerle , all

I've fixed as requested.
Added a link to GSMA UC
For the image generation I provided instructions for prompting.

Looking for your feedbacks :)

[jlurien]

Is the update expected from Code owners/maintainers or by Outreach team?