Home » railML newsgroups » railML.infrastructure » Modified V94_12
Modified V94_12 [message #38] Tue, 18 November 2003 09:04 Go to previous message
volker.knollmann is currently offline  volker.knollmann
Messages: 9
Registered: November 2003
Junior Member
Hello,

based on a suggestion from Matthias Hengartner, I modified the latest
version of the scheme (v94_12) according to the ideas I discussed with
Matthias via email. You can download my modified version here:

http://creature.apm.etc.tu-bs.de/~volker/infra_V094_12_knoll mann_1.xsd

The most significant change is the introduction of a element called
<ocsElements>, which is a child of <track>. "ocs" means "operation- and
controlsystems" and is meant to be a translation of the German "Leit- und
Sicherungstechnik".... err.... if you know a better translation, feel free
to tell me :-)

<ocsElements> should contain all objects related to operation, control, train
protection and similar things. Just to give you an idea, I created
sub-elements for Balises, track coupling coils, track circuits, LEUs and
EuroLoops. And I moved the <signals>-Element into this <ocsElements>, of
course.

The detailed definition, especially the attributes, of the new elements is
not yet complete. I just want you to get an idea of my changes and if you
think that I chose a good way, we / I can spend more time on this.

Another change is the introduction of the attributes <prevTrackID> and
<nextTrackID> for the element <track>. With this means, you are able to
compose a line of multiple tracks similar to a double linked list. Of
course, <nextTrackID> of one track and <prevTrackID> of the next track
need to be consistent, otherwise the xml-file would be corrupt.

These two attributes are just a quick & dirty suggestion. Up to know, I'm
not really sure whether I really like them myself. To be honest, I'm not
even sure whether you really need to compose a line of several tracks.
Background: due to your microscopical model, you only need to define
special points (swicthes, signals, xxxChange, etc) along the track. This
can all be done within one track element. This is in contrast to a
macroscopical model, where to need to compose a "long" track (line) of
several edges. Therefore, I see the need to compose one line of several
tracks only for the use of a macroscopical model, not for the use of a
microscopical model.

I'm afraid that my description was quite confusing... if you have question
or if I wrote complete bullsh**, please tell me. I'd really appreciate a
discussion about my ideas here in this newsgroup.

Thanks to everyone who read this long posting! I'm looking forward to your
comments!

Best regards from Braunschweig,
Volker Knollmann
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: Offene Fragen zu Version 0.94_12
Next Topic: RailML-Editor
Goto Forum:
  


Current Time: Mon Apr 29 07:55:33 CEST 2024