Wording remarks to IRS30100 [message #1373] |
Thu, 23 June 2016 13:54 |
Felix Prüter
Messages: 28 Registered: June 2016 Location: Berlin
|
Junior Member |
|
|
Hello,
we (SIGNON Deutschland GmbH) are validating the use of RailTopoModel as the base model for several railway-related applications dealing with various proprietary infrastructure input data. For that reason, I studied the IRS 30100. Now I have several questions and remarks for which I will open seperate topics.
The first remark is just a wording topic: (p.14, 2nd. par.)
Quote:...since resources are identified HERE as...
It's not clear and hard to find out what HERE references to.
For me it references the TRADITIONAL REPRESENTATION, right?
Regards
Felix Prüter
SIGNON Deutschland GmbH
[Updated on: Thu, 23 June 2016 21:36] by Moderator Report message to a moderator
|
|
|
|
|
Re: Wordng remark to irs 30100 [message #1387 is a reply to message #1373] |
Mon, 27 June 2016 11:12 |
christian.rahmig
Messages: 465 Registered: January 2016
|
Senior Member |
|
|
Dear Felix,
Am 23.06.2016 um 18:13 schrieb Felix Prüter:
> [...]
> The first remark is just a wording topic: (p.14, 2nd. par.)
> Quote:
>> ...since resources are identified HERE as...
>
> It's not clear and hard to find out what HERE references
> to.
> For me it references the TRADITIONAL REPRESENTATION, right?
> [...]
Yes, "here" stands for "traditional representation". This clarification
has to be added in the text.
Thanks and best regards
Christian
--
Christian Rahmig
railML.infrastructure coordinator
Christian Rahmig – Infrastructure scheme coordinator
railML.org (Registry of Associations: VR 5750)
Altplauen 19h; 01187 Dresden; Germany www.railML.org
|
|
|
Re: IRS 30100 wording remarks [message #1398 is a reply to message #1374] |
Fri, 19 August 2016 16:14 |
christian.rahmig
Messages: 465 Registered: January 2016
|
Senior Member |
|
|
Dear Felix!
Your points were analysed by members of the RTM expert group. The
question concerning "ch 6.3.7, 2nd sentence" seems to be a
misunderstanding and will be addressed by clarifying the documentation.
The other items will be updated along your line of reasoning.
Best regards
Christian
Am 23.06.2016 um 21:28 schrieb Felix Prüter:
> Hello,
> here are some more wording remarks to the IRS 30100:
>
> p.30, last note:
> the part after the last comma seems superfluously
>
> ch 6.2.11, z2nd par:
> the description about the relation between
> PositioningNetElement und AssociatedPositioningElement is
> wrong.
> APS is contained by PNE!
>
> ch 6.3.6:
> defines the generic concept of a coordinate in a POSITIONING
> (not referencing) system
>
> ch 6.3.7, 2nd sentence:
> Should be two sentences
> 1. value range of attribute intrinsicCoord 0..1
> 2. Arbitrary amount of associated
> PositioningSystemCoordinate instances
>
> ch 6.4.5:
> in reference to one OR MORE PositioningNetElement
> according to Figure 72 only ONE!
>
> ch 6.4.5:
> Attribute applicationDirection: direction of the
> LINEARLOCATION?
> better: LinearElement?
>
> ch 6.4.9:
> between a LinearLocation and PositioningSystemCoordinate
> INSTANCES (is missing)
>
> Kind regards
> Felix
> SIGNON Deutschland GmbH
>
--
Christian Rahmig
railML.infrastructure coordinator
Christian Rahmig – Infrastructure scheme coordinator
railML.org (Registry of Associations: VR 5750)
Altplauen 19h; 01187 Dresden; Germany www.railML.org
|
|
|
|