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?
[x] I have signed the required Developer Certificate of Origin (DCO) already.
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?