Interdependencies between RDF methods of the Wrapper API and implementation of guardrails #852
Description
The Wrapper API defines three optional RDF manipulation methods: add, remove and triples.
Considering that in SimPhoNy the user dictates the state of the session, there are some logical implications associated to their use. For example, if triples are intercepted by the add method and not added to the base graph, then they must be later reconstructed by the triples method.
@pablo-de-andres suggested to implement guardrails in SimPhoNy itself that could for example, force a Wrapper developer to implement the triples method if the add method has also been implemented.
What do you think about this idea? What could be a feasible solution?