suggestions for the evolution

[paulakeen]

I think we need to state some general principles that lead the evolution of this great work. Here I list a couple of principles that could be included:

1. The script should be totally agnostic of the context where it is going to be used, i.e. business domain, particular ontology, other. This implies that all the configuration of the script should be done 100% out of the XSL scripts.
2. The UML model of origin and the script should be totally unbound of the final syntax it is going to produce. This implies that the script should generate a syntax-neutral ‘pivot’ serialization that can be mapped into RDF, XML, JSON, JSON-LD, whatever it is needed.

If we only are capable of implementing these two features, then there are plenty of possibilities arising in front of us, like the possibility of intgrating the script directly inside the UML designer tool, or producing a microservice that takes in the EAP file (or the XMI) and the type of artefacts desired, and responds with the artefacts (or a graph directly constructed/inserted in a Graph Store, etc.).

I have some ideas on how these two features could be implemented

KR

[cristianvasquez]

This is good advice.

This pivot serialization can be something similar or an extension of https://linkml.io/linkml/