extend allowed values for "interface" in Endpoints (SUBMODEL-VALUE etc.)

[BirgitBoss]

What is missing?

In https://admin-shell-io.github.io/aas-specs-antora/IDTA-01002/v3.1/specification/interfaces-payload.html#_endpoint we define the allowed "interface" values within the endpoint within an AAS or Submodel Registry.

We already discussed it whether to also support

• "SUBMODEL-VALUE-3.0"
• "SUBMODE-METADATA-3.0"
• "SUBMODEL-PATH-3.0"
• "SUBMODEL-3.0" would be for format "Normal"

etc. but decided that "SUBMODEL-3.0" is sufficient. This lead to the following requirements in Catena-X: add $value to endpoint

Now the problem is that sometimes the endpoint also contains parameters. These are not standardized in AAS but they are needed for a generic generation of the submodel data. If this is the case it is not possible to just add "$value" to the endpoint. Note: In the registry it is not required to have /submodel in the path, any endpoint returning the required payload it ok.

See our answer in
What are the right attribute values for 'Descriptor/endpoints'?
it does not cover how to deal with the different formats supported by AAS

[arnoweiss]

If the convention is to register the URL serving the full Submodel, what other serializations are covered is signaled by the Submodel servers' /description endpoint. I think the question is: what happens when a server ""decides"" to violate the ServiceSpecificationProfiles by leaving out the main endpoint? That's outside of the spec and just adding it here feels a little contradictory.