Home » railML newsgroups » railml.timetable » Clarification of the debitcode attribute
Clarification of the debitcode attribute [message #761] Tue, 20 March 2012 21:50 Go to next message
jn is currently offline  jn
Messages: 1
Registered: March 2012
Junior Member
The debitcode attribute should be placed on the trainPart entity according
to the xsd. However I have seen a couple of xml documents where the
debitcode attribute is placed on the sectionTT entity. I have been looking
in the xsd for both version 2.1 and the development version. For both
versions the attribute can be found on the trainPart entity, but not on
the sectionTT entity.

First, I am wondering whether it has been discussed to place the debitcode
attribute on the sectionTT entity and what the conclusion was on that
proposal? Second, did the debitcode attribute ever exist on the sectionTT
entity? If so in what version of the Railml format? or any preliminary
versions?

Thanks
Jess

--
----== posted via PHP Headliner ==----

Report message to a moderator

Re: Clarification of the debitcode attribute [message #843 is a reply to message #761] Tue, 06 November 2012 11:41 Go to previous message
Susanne Wunsch railML is currently offline  Susanne Wunsch railML
Messages: 0
Registered: January 2020
Hello Jess,

Welcome at the railML community. :-)

Sorry for the late response. I only sometimes have a look at the
timetable forum. I thought somebody would help out with more historic
railML implementation background than me.

jn(at)trapezegroupeu (Jess Nielsen) writes:

> The debitcode attribute should be placed on the trainPart entity according
> to the xsd. However I have seen a couple of xml documents where the
> debitcode attribute is placed on the sectionTT entity.

Did you already asked at the software tool developers which defined the
export for railML files your tool consumes?

> I have been looking in the xsd for both version 2.1 and the
> development version. For both versions the attribute can be found on
> the trainPart entity, but not on the sectionTT entity.

+1

Earlier versions (railML 1.0 and railML 1.1) had this attribute in the
<train> element.

> First, I am wondering whether it has been discussed to place the debitcode
> attribute on the sectionTT entity and what the conclusion was on that
> proposal?

No discussions I would be aware of.

Maybe it was sometimes mentioned at a railML conference. But then there
always comes the advice to post the issue to the appropriate forum in
order to broaden the discussion to users not attending the conference.

> Second, did the debitcode attribute ever exist on the sectionTT
> entity?

AFAIK not.

Do somebody has a need for the "debitcode" attribute at the <sectionTT>
element? Do you use this attribute or just pass it unchanged or drop it?

It should show up an XML validation error!

Kind regards...
Susanne

--
Susanne Wunsch
Schema Coordinator: railML.common

Report message to a moderator

Previous Topic: Some small changes, wishes and recommendations for RailML2 timetable schemes
Next Topic: Frage zu TT:category
Goto Forum:
  

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

Current Time: Sat Apr 20 03:18:47 CEST 2024