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 #1626 is a reply to message #1617] Thu, 20 July 2017 16:32 Go to previous message
Ferri Leberl is currently offline  Ferri Leberl
Messages: 24
Registered: September 2016
Junior Member
Dear all,
As I have mentioned earlier, the workflow should be first to extract an element list from the schema, and then, at second, to transform the element list into wiki code.
DI Wunsch provided us an XSLT-script that transforms a railML-document into code suitable for the MediaWiki-extension "Tree and Menu". Principally, it should be possible to change this script such, that, if you feed it with a "complete" railML-file, containing all elements, with all attributes, exactly once, it builds the element list needed for step two. This would be a second best alternative for step one. It would not deliver all required information (particularly the documentation tags would be lost), but it would provide a base.
Is there an efficient way to produce such examples in XMLSpy or Oxygen?
Thank you in advance for hints, heuristics, and examples.
Yours,
Mag. Ferri Leberl
 
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:
  


Current Time: Fri Apr 19 11:41:07 CEST 2024