uService definitions use service IDs that are in conflict with uProtocol's Name & Number Registry
Open
- Dominant language
- No language data
- Stars
- 13
- Forks
- 9
- PR merge metrics
- No merged PRs in 30d
Description
The service identifiers used by the existing uServices in this repo are all in conflict with the ranges defined for the [uProtocol Name & Number Registry](https://github.com/eclipse-uprotocol/up-spec/tree/main/up-l3#3-name--number-registry). In that specification, COVESA uService identifiers are supposed to come from range `[0x0100, 0x0FFF]` only ...
Contributor guide
Research direction
Read the uProtocol Name & Number Registry specification linked in the issue, then inspect the existing uService definitions in this repository and compare their identifiers with the specified ranges. The work is done when the affected service identifiers no longer conflict and all COVESA uService identifiers use the permitted range.
Written by the indexing model from the issue text.
Assessment
- Domain
- api
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100