hofstef
commented
2 years ago Hi @alexrjs, that's an interesting idea. Which other tools do you have in mind? I only know of a PlantUML-Plugin. I think that a pure model export would need to include type information together with the label, i.e. which model element type the label refers to. Something like: actor(client) - activity(sends) - workobject(email) The devil is in the details: annotations, sequence numbers (relying on the order in the export file will not work as we allow using the same sequence number multiple times), and more complex sentence strucutres (multiple work objects, multiple receiving actors, ...). This is all doable, but it would take a bit of effort to come up with a format that covers all possible cases. Nevertheless, the export would be lossy as the icons usually convey meaning and would not be included in a pure model export. That's why I am curious to learn more about your use case for this feature request.
alexrjs
Is your feature request related to a problem? Please describe. Currently the design and the visualisation information are stored together in the .dst file. An option to have a separate design document, without visualisation information, so you can use this document for other tools, without having to filter out all visualisation info, just to get to the node, edge information.
Describe the solution you'd like A simple document format, where only the node, edge info is stored. Example: Client -sends-> email email -received-> Agent
Describe alternatives you've considered Strip the .dst file down to node, edge information
Additional context