Are ServiceProfiles protocol-specific?

[mjacoby]

AAS specification Part 2 defines the concept of ServiceProfiles as part of the protocol-agnostic API, see Self-Description Interface and its payload ServiceDescription.

However, concrete ServiceProfiles are only defined in the HTTP/REST API subsection here.

Is this by design, i.e. implying that service profile definitions are protocol-specific, or shouldn't this last section be outside the HTTP/REST API section, i.e. implying the defined profiles are protocol-agnostic?

• I have signed the required Developer Certificate of Origin (DCO) already.

[BirgitBoss]

the profiles were considered to be protocol-specific.

So perhaps it would be sufficient to change the descriptions, e.g.

Indicates that the server implemented all features of the Asset Administration Shell Service Specification Full Profile in version 3.0.

to

For https/REST only: Indicates that the server implemented all features of the Asset Administration Shell Service Specification Full Profile in version 3.0.

As soon as we would support other protocols as well additional profiles for these protocol would be added.