eclipse-uprotocol / eclipse-uprotocol/up-spec
Clarify and Update L1 Someip Specs as required
@stevenhartley is already working on this.
Since Aug 1, 2024.
- Dominant language
- Gherkin
- Stars
- 43
- Forks
- 29
- Avg merge
- 20m
- Merged PRs (30d)
- 3
Description
Some of the Specs seem unclear like
https://github.com/eclipse-uprotocol/up-spec/blob/main/up-l1/someip.adoc#uuris
authority_name - What data type it must be, what are the applicable values? Providing IP:Port in the documentation feels like the expected value for authority is "192.168.1.100:446" (Just an example), but we spoke that authority would look something like this "192.168.1.100"
ue_id - Column SOME/IP field says "InstanceId|ServiceId". This could be interpreted as ue_id could be an instance_id or service_id... while description give more information on what it should be.
"Explicitly setting InstanceID to 0x0001 SHOULD be avoided as it increases uProtocol message size." this sentence could be more explicit.
ue_version_major - Clarification on what a default service major is if something is not provided
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.