-
Notifications
You must be signed in to change notification settings - Fork 2
Add annotation @ObjectModel.origin #116
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
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. |
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.