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 #1420 is a reply to message #1415] Thu, 15 September 2016 13:17 Go to previous messageGo to previous message
Dirk Bräuer is currently offline  Dirk Bräuer
Messages: 311
Registered: August 2008
Senior Member
Dear Ferri Leberl,

thank you for your Diskussionsanstoß for documentation of railML 3
from my side. I can follow your problem description and suggestions.

I personally would prefer solution 3 "Recycling" but I am not sure
whether this may mean an effort still too high. I possibly would follow
this solution if there is a possibility to "recycle step by step",
leaving a current topic on-line until it is recycled. All existing
information should always stay available, better in an old contents
(railML 2.x) than not at all.

Concerning "Schemeneinbindung", I understand the problem but do not have
enough experience to suggest anything. I can only offer some possible
help by programming a kind of tool which parses and converts xsd files
into a file format which can possibly better be handled by existing
tools. The question would be whether this solution would have any
advantages over "Einbindung von HTML" - probably not. Anyway, at least
it could be a solution for "Entfernung des Kopfes und Umwandlung von
Links". Please do not hesitate to contact me if you feel that I can help
in this direction.

With best regards,
Dirk Bräuer.

P.S.: Please do not MIME-encode attachments in forum posts. There are
news readers (as mine) which do not decode them and present them
in-line. Better provide a download link.
 
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: Tue Apr 23 12:20:32 CEST 2024