Stream: ihe
Topic: Rendering Diagrams
Jose Costa Teixeira (May 11 2020 at 17:04):
While working on the diagram rendering I thought of checking my approach:
Currently I take a resource (e.g. ExampleScenario, CapabilityStatement, PlanDefinition) and run some XSLT magic to render it as a diagram
(generate PlantUML source, create diagram, then throw away the source, take the diagram and build a page).
I was wondering if it makes sense to preserve the source, for example having an extension "DiagramRepresentationSource" that can hold the plantUML text.
I don't see value added, but that is because of the way I'm implementing - are there other perspectives?
John Moehrke (May 11 2020 at 18:51):
In ITI, when we create UML diagrams from UML source, we put that source inline. This becasue some readers like to take that UML source for their use.
John Moehrke (May 11 2020 at 18:52):
in html authoring this should be even more clear it is a good thing to make the source avaialble to the reader
Jose Costa Teixeira (Jun 09 2020 at 15:04):
I'm tring to add that to the template. We can probably make an extension
Frank Oemig (Jun 10 2020 at 06:36):
What kind of XSLT magic?
Jose Costa Teixeira (Jun 10 2020 at 07:36):
As per my first line in the thread- I take the resource in xml, and I generate the plantuml syntax from that, and then I pass it through plantUML, and that gives me an SVG
Jose Costa Teixeira (Jun 10 2020 at 07:37):
there's not much to it (it was not so easy because i did not really know xslt when I started this, but the transformation is rather simple)
Last updated: Apr 12 2022 at 19:14 UTC
