Home » railML newsgroups » railML.infrastructure » Infrastructure element datamodel quality and input-data source
Re: Infrastructure element datamodel quality and input-data source [message #3266 is a reply to message #3259] Fri, 05 July 2024 10:13 Go to previous messageGo to previous message
Torben Brand is currently offline  Torben Brand
Messages: 162
Registered: March 2016
Senior Member
Dear Christian,

Thank you for your reply.
I think I now have a clear plan! :-)

Regarding question 2: I tricked you due to my lack of railML3 knowledge ;-). The <projectArea> does not have an @id, so the ref can only be to the <genericArea>.

Regarding question 3: Yes, I would very much like to propose a data quality UC. I will ask Bane NOR to participate in the initial draft as they have proposed some system using ISO25012 [1]

Regarding question 1: As an interim sollution for a free-text to describe the quality I suggest to use the name@description already existing under <elementState>. With name@name beeing the short description or a default value like "State remark". The later, when you only have a description field of the state in your tool (as @name is mandatory when using <name>).

See example I made bellow of the "simplest example" found here [2]

    <infrastructureStates>
      <infrastructureState id="iss1">
        <elementState id="es_are101" refersToElement="are101" value="conceptual"/>
          <name name="State Remark" description="According to KVB-15-C-10000_00B. Elements marked with the status &quot;conceptual&quot; in the project area are based on a template for a 2-track station on a single-track line with ETCS (doc. no.: 202100192-11), adjusted to 740m effective train length for the Kongsvinger line according to effect package 14. (added by Torben Brand, 24.8.2023)" language="en"/>
	 </elementState>
      </infrastructureState>
    </infrastructureStates>
...
    <genericLocations>
      <genericArea id="are101">
        <name description="Description: " language="en" name="Project new bridge &quot;Bruse&quot;"/>
        <location>
          <circle radius="0">
            <centerPoint>
              <gml4rail3:pos>0 0</gml4rail3:pos>
            </centerPoint>
          </circle>
        </location>
        <isLimitedBy ref="bor99"/>
        <isLimitedBy ref="bor100"/>
      </genericArea>
    </genericLocations>
...
   <projects>
      <project id="pr6921e524-bf24-145f-f9b3-8428457225c9">
        <name language="no" name="&quot;Bruse&quot; brigde"/>
        <projectArea ref="are101"/>
        <alternative id="pra8b26d91f-791b-16f0-b980-da5ff7ee80e8">
          <name description="Axcle load increase according to concept A2" language="en" name="Brigde improvement"/>
        </alternative>
        <phase id="prp6473936e-7fc0-996f-e56e-0db99c3020ca" startDate="2020-10-01">
          <name language="en" name="As built"/>
        </phase>
      </project>
    </projects>


[1] https://iso25000.com/index.php/en/iso-25000-standards/iso-25 012
[2] https://railoscope.com/tickets/Fyh1WAZliOQbgVmY?modelId=5c81 5c32137e0f14761f0ba8&selectId=81-3

Report message to a moderator

[Message index]
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: railML3 suggestion to add values for @detects in IS:detector
Next Topic: [railML3] Improvement for railML element „etcsLevelTransition"
Goto Forum:
  

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

Current Time: Wed Oct 02 10:38:33 CEST 2024