Home » railML newsgroups » railml.common » [railML3] Strategy of documentation at wiki.railML.org (Impulse for a discussion: how should railML3 be documented?)
Re: [railML3] Strategy of documentation at wiki.railML.org [message #1421 is a reply to message #1415] Thu, 15 September 2016 15:59 Go to previous messageGo to previous message
Bob Janssen railML is currently offline  Bob Janssen railML
Messages: 6
Registered: January 2019
Junior Member
Dear all,

Up to Present, the wiki contains information generated by the XSD editing tool XMLspy - great.

Now, we're using Enterprise Architect. This tool lets us write UML which is much richer than XSD schemata. In fact, UML registers documentation, both graphically and textually. The information is far richer than what XMLspy can capture.
It stands to reason that we make Enterprise Architect generate the HTML-information that we publish on the site. EA allows us to tailor the HTML-output and this is where Herr Leberl comes in: I suggest that he do the tailoring so that EA produces appealing HTML.

Please refer to http:// www.sparxsystems.com/enterprise_architect_user_guide/12.1/re port_generation/htmlreport.html for more information about the templating that EA can do. I would suggest that he create some templates.

Yours,
Bob Janssen

Report message to a moderator

[Message index]
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: To use or not to use? - default values in XSDs
Next Topic: Child elements with one value vs. attributes
Goto Forum:
  

[ Syndicate this forum (XML) ] [ RSS ] [ PDF ]

Current Time: Wed Apr 24 05:29:26 CEST 2024