If I have a shell with the identifier https://test-shell residing in a shell repository, the HTTP endpoint to retrieve the shell would be located at https://.../my-shell-repo/shells/aHR0cHM6Ly90ZXN0LXNoZWxs.
When using AAS-REPOSITORY-3.0 for the interface attribute of the endpoint, would the correct endpointAddress be
https://.../my-shell-repo/shells/aHR0cHM6Ly90ZXN0LXNoZWxs (the URL where the shell data is located)
https://.../my-shell-repo/ (the base URL of my shell repository)
Both cases seem valid to me and I could not find anything about this in the standard. However, there has to be one "correct" solution, because clients receiving endpoint data need to be able to deal with it in a unified way.
I want to provide an endpoint to a shell residing inside a shell repository. What is the correct way to specify the
endpointAddress
?The standard provides only the following example:
If I have a shell with the identifier
https://test-shell
residing in a shell repository, the HTTP endpoint to retrieve the shell would be located athttps://.../my-shell-repo/shells/aHR0cHM6Ly90ZXN0LXNoZWxs
.When using
AAS-REPOSITORY-3.0
for theinterface
attribute of the endpoint, would the correctendpointAddress
behttps://.../my-shell-repo/shells/aHR0cHM6Ly90ZXN0LXNoZWxs
(the URL where the shell data is located)https://.../my-shell-repo/
(the base URL of my shell repository)Both cases seem valid to me and I could not find anything about this in the standard. However, there has to be one "correct" solution, because clients receiving endpoint data need to be able to deal with it in a unified way.