Discrepancies in the API documentation and declarative modelling

I think the declarative modeling explained here (Declarative modelling - py-capellambse documentation) is quite vague and does not provide a clear understanding of how to create a YAML for other layers, such as OA or SA. This is mainly because identifying which keywords work under a specific layer or package is not clear in the API (https://dbinfrago.github.io/py-capellambse/start/intro-to-api.html) and cannot be related to the language used in Capella.

For example, what are communication_means under the entity in the OA module? How is it related to Capella, and how should it be implemented in YAML? This is just one example. I have been trying for over a month but still have not been able to untangle this confusing knot.
@StephaneLacrampe can we do anything about this to make it more user-friendly and straight-forward?

Thanks,

Tirth Joshi

py-capellambse is developped by Deutsche Bahn, not us (Obeo) - please contact them.

1 Like

If someone is reading from Deutsche Bahn, can you please guide on this?