Re: [D] Discussion: How do we expect OSI to be used [ossie]

["jakub-moravec (via GitHub)" <gi...@apache.org>]

GitHub user jakub-moravec added a comment to the discussion: Discussion:  How do we expect OSI to be used

Hi @MarioDeFelipe, apologies for the radio silence, it took me a while to recover from vacation :) 

In the case of OpenLineage, the spec makes it possible and simple for your payload to be valid against the spec/JSON schema, and yet not really usable for cross-vendor integrations: 

- answering whether the payload is syntactically correct and schema-valid is simple, as you mentioned
- answering whether what is documented is sufficient is not. For example, you can create an OpenLineage payload without actually documenting any lineage (and share runtime metrics instead). Or you can document lineage at different levels of granularity. The best practices are often use-case specific. Not sure if this problem is relevant for Ossie.
- Information can be captured in custom payload fields, similar to Ossie `custom_extensions`. If important information is captured using this mechanism (as opposed to a standardised model), the integrations built on top of the standard end up being vendor-to-vendor integrations, as opposed to vendor-agnostic standard integrations. 

GitHub link: https://github.com/apache/ossie/discussions/46#discussioncomment-18329156

----
This is an automatically sent email for dev@ossie.apache.org.
To unsubscribe, please send an email to: dev-unsubscribe@ossie.apache.org