Assets: features and limitations of the default Services (SVC) schema

[Paul Santus]

Jira Assets comes with a default Services schema.

It seems it has some benefits, for instance

• cross-product integrations (for instance with OpsGenie).
• nice integration within Jira Service Management

However, there seems to be limitations as well, for instance

• I'm unable to set a dependency relationship between a Service asset object and an object from another Assets schema / object type.

Is there an official documentation of the features and limitations? 

Why would you use (or NOT use) this Services object type for?