Just like we currently have importers to import non-semantic data to SemApps instances, we could provide exporters which export semantic resources to non-semantic tools like Wordpress or YesWiki.
It would be much easier to handle since we would only need to listen to ldp.resource.created, ldp.resource.updated and ldp.resource.deleted Moleculer events.
Then we will call the APIs, after having transformed these data.
It could work with all the tools we use for importers:
Just like we currently have importers to import non-semantic data to SemApps instances, we could provide exporters which export semantic resources to non-semantic tools like Wordpress or YesWiki.
It would be much easier to handle since we would only need to listen to
ldp.resource.created
,ldp.resource.updated
andldp.resource.deleted
Moleculer events.Then we will call the APIs, after having transformed these data.
It could work with all the tools we use for importers: