Open SOME/IP spec references added.#2525
Conversation
|
|
|
The created documentation from the pull request is available at: docu-html |
dasoho
force-pushed
the
feature/OpenSOMEIP_References
branch
from
752c2eb to
fa4a0b9
Compare
Open SOME/IP secification references added to SOME/IP Gateway feature specification. Signed-off-by: Holger Braun <holger.braun@aumovio.com>
dasoho
force-pushed
the
feature/OpenSOMEIP_References
branch
from
fa4a0b9 to
4f3be85
Compare
dasoho
requested review from
a team,
FScholPer,
antonkri,
johannes-esr and
qor-lb
as code owners
| This functionality is enabled through the inclusion of the `vsomeip <https://github.com/COVESA/vsomeip>`_ stack, | ||
| which is based on the publicly released `Open SOME/IP <https://github.com/some-ip-com/open-someip-spec>`_ Specification | ||
| and serves as a reference implementation that may be substituted with alternative solutions, including proprietary | ||
| commercial SOME/IP stacks. |
There was a problem hiding this comment.
I think we should remove that sentence as this is not in scope for S-CORE
There was a problem hiding this comment.
Do you really mean the entire sentence? (Incl. the vsomeip based plugin?)
Actually, the reference plugin based on vsomeip was already mentioned before. Has it been decided, that a reference plugin based on vomeip shouldn't be part of the SOME/IP Gateway?
| This shall be possible by including the `vsomeip <https://github.com/COVESA/vsomeip>`_ SOME/IP stack for reference, | ||
| which can be replaced by other implementations, i.e. proprietary commercial stacks. | ||
| This functionality is enabled through the inclusion of the `vsomeip <https://github.com/COVESA/vsomeip>`_ stack, | ||
| which is based on the publicly released `Open SOME/IP <https://github.com/some-ip-com/open-someip-spec>`_ Specification |
There was a problem hiding this comment.
I think it would make sense to pick a release here which can be later on updated: https://github.com/some-ip-com/open-someip-spec/tree/release-2025-12
There was a problem hiding this comment.
Was not available last week, will provide an update by Feb. 11th.
There was a problem hiding this comment.
Will do the update and reference the current release.
| :status: valid | ||
|
|
||
| The SOME/IP protocol implementation shall be fully compatible and complying with the SOME/IP protocol specification from `some-ip.com <https://some-ip.com/>`_. | ||
| The SOME/IP protocol implementation shall be fully compatible and complying with the SOME/IP protocol specification from `Open SOME/IP <https://github.com/some-ip-com/open-someip-spec>`_. |
There was a problem hiding this comment.
Is this the case for vsomeip at the moment?
There was a problem hiding this comment.
I would say so:
As mentioned here vsomeip claims to implement the protocol specified in https://some-ip.com/ and the first link on this page points to the Open SOME/IP specification.
So, at least from documentation point of view, vsomeip traces to the Open SOME/IP specification.
|
In general:
so it is difficult from architecture point of view where to store the specification of public some/ip |
I agree on both statements but I still do not exactly know what you would like to improve? |
3 participants
Open SOME/IP specification references added to SOME/IP Gateway feature specification.