Link merge policy

[jmakeig]

As a Data Architect, I want to be able to identify relationships between entities using Smart Mastering™ rules. However, rather than merging upstream parts into a downstream entity, I want to keep the the upstream and downstream parts as-is, but create an assertion about the relationship, such that it’s possible to query for the related data.

(Insert example from global manufacturing company.)

Todo

We’d need to figure out how to express this relationship and which aspects to allow the user to control:

• Triple: Leverage standard sameAs or custom predicates?
• Foreign keys
• Both: Project triples out of keys?

[popzip]

Can probably do this today with custom actions. Could include an example or best practice. Perhaps we can reach out.