Skip to content

Conversation

@michaelbelenki
Copy link

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.

@Fannon
Copy link
Member

Fannon commented Nov 12, 2025

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.

@aveon4work
Copy link

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants