[FEAT] OVOS Backend Client Support - Githubissues

NeonGeckoCom / neon-hana

HTTP Access to DIANA deployed services

Other

0 stars 0 forks source link

[FEAT] OVOS Backend Client Support #10

Open NeonDaniel opened 10 months ago

NeonDaniel commented 10 months ago

Objective

Implement endpoints for full support of ovos-backend-client endpoints.

Initial Implementation Requirements

[x] Token compatible with IdentityManager
[X] OWM endpoint support
[X] Wolfram Alpha endpoint support
[X] Geolocation
[X] STT
[ ] Device API
- [ ] Properties (friendly name, description, UUID, versioning)
- [ ] Device settings
- [ ] Activation
- [ ] Update
- [ ] Upload skills data
[X] Metrics API
[ ] OAuth API (?)
[ ] WW Upload (Later?)
[ ] STT Upload (Later?)
[X] Email API
[ ] #7 (Upload + Download)
[ ] Admin API (?)
[ ] Database API (?)

Other Considerations

Which APIs might be excluded from an initial implementation (or generally excluded)
Authentication/Authorization requirements for a device to manage skill settings
What associated services are required to support added endpoints
- Service to manage uploaded WW/STT (Metrics?)
- Service to manage Device API
- Skill settings database/service