Conversation
|
CSN Interop Workstream: Further clarification needed: What are the expectations who uses this information for what purposes? Mixing "customer"; "partner" with "industry" and "internationalization" - rationale? Question: Do we need this only internal or is it relevant for external consumers? If it's only relevant internally, maybe we don't need to make it part of CSN Interop. |
This annotation is designed for all data product consumers, not just internal users. Its purpose is to help clients understand comprehensive models that integrate multiple specific attributes tailored for diverse scenarios. This is a common situation, for example, with S/4HANA data products. |
| If set to true, it is a custom element (field, entity, service, etc.). | ||
| If undefined or set to false, it is not defined whether it is a custom element. | ||
|
|
||
| If applied to an entity or service, everything that it contains is also considered custom. |
There was a problem hiding this comment.
| If applied to an entity or service, everything that it contains is also considered custom. | |
| To further define the origin of the custom element, additionally use the `@ObjectModel.origin` annotation. |
Co-authored-by: Simon Heimler <simon.heimler@sap.com>
4 participants
Annotation @ObjectModel.origin shall be added to CSN interop effective specification. The annotation specifies the source layer(s) and codes where the element or entity is defined.