Hi All This picks up the previous thread on loading graphs in EDG via a data driven approach and especially the intent of using proxies for source graphs to segregate production data and models.
We are now looking how this deals with CRUD of "development instances" - Abox or other graph "edits" Tbox that are made in the proxied EDG asset but need to be written back to the source graphs or to staging/review graphs. So we now have EDG consuming a source graph A as a proxy into an EDG graph B. What we need to do now is write any new resources created in the EDG asset B back to: 1. to the source A : and/or 2 to a staging graph C 3. to/via a teamwork workflow D to review the changes back to C or A Sure I can export the data from the EDG gui, or extract it via TBCME but I want a data driven approach. I'm hoping for a way to trigger this write back process on an event in the EDG asset GUI of B e.g. this could be: 1. at a minium before the EDG asset B is deleted or cleared 2. before an external proces forces the asset B to be deteled or cleared - we can trigger the purging of assets and reloading via a set of rules.... so can this trigger the write back before they are nuked 3. happy case - use a shacl rule that can be clicked or run via GUi when some action or change triggers it 4. future case - when the seletion focus of some carefully selected page UI object(s) changes Is there a logical starting point to acheive the above ? Many thanks in advance Simon -- You received this message because you are subscribed to the Google Groups "TopBraid Suite Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/topbraid-users/ddba1927-a3ac-49e4-aa7c-9fc10567ac44o%40googlegroups.com.
