<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" href="stratml_AI_Highlight.xsl"?>
<StrategicPlan xmlns="urn:ISO:std:iso:17469:tech:xsd:stratml_core" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
  <Name>Register of Infrastructure</Name>
  <Description>A plan for the Register of Infrastructure maintained by the European Union Agency for Railways.</Description>
  <OtherInformation>Submitter&apos;s Note:  This plan has been inferred and rendered in StratML format by ChatGPT based upon publicly available information published by the European Union Agency for Railways, including the RINF page, the RINF Application Guide, and the ERA Ontology documentation.  It has been lightly edited in the form at https://stratml.us/forms/Claude/Part1.html
^^
It was prompted by Kurt Cagle&apos;s LinkedIn posting about the shift from XLM to RDF:  https://www.linkedin.com/posts/kurtcagle_good-article-on-the-shift-from-xml-to-rdf-share-7471229608722444288-aQYZ/?utm_source=share&amp;utm_medium=member_desktop&amp;rcm=ACoAAACRo-wBsB6AJXaqtz06r_wMwIYVUJtr0PM</OtherInformation>
  <StrategicPlanCore>
    <Organization>
      <Name>European Union Agency for Railways</Name>
      <Acronym>ERA</Acronym>
      <Identifier>ac670e85-c92d-4c0e-957d-dc1be2925f8a</Identifier>
      <Description>The European Union agency responsible for maintaining the Register of Infrastructure and supporting safe, interoperable railway operations in Europe.</Description>
      <Stakeholder StakeholderTypeType="Organization">
        <Name>European Commission</Name>
      </Stakeholder>
      <Stakeholder StakeholderTypeType="Organization">
        <Name>Infrastructure Managers</Name>
      </Stakeholder>
      <Stakeholder StakeholderTypeType="Organization">
        <Name>National Registration Entities</Name>
      </Stakeholder>
      <Stakeholder StakeholderTypeType="Organization">
        <Name>Railway Undertakings</Name>
      </Stakeholder>
      <Stakeholder StakeholderTypeType="Generic_Group">
        <Name>Rail passengers and freight customers</Name>
      </Stakeholder>
    </Organization>
    <Vision>
      <Description>A harmonized, machine-readable, and interoperable European railway infrastructure knowledge base supporting safe and efficient cross-border rail operations.</Description>
      <Identifier>17992607-d168-457f-8e6f-9bd548935290</Identifier>
    </Vision>
    <Mission>
      <Description>Provide authoritative, harmonized, and searchable railway infrastructure data, including infrastructure characteristics, capabilities, topology, and route compatibility information.</Description>
      <Identifier>886e1e78-470a-4ad5-8c6b-9358d3e521c1</Identifier>
    </Mission>
    <Value>
      <Name>Interoperability</Name>
      <Description>Railway infrastructure data should be represented consistently across systems, countries, and stakeholders.</Description>
    </Value>
    <Value>
      <Name>Accuracy</Name>
      <Description>Infrastructure data should be accurate, complete, consistent, and timely.</Description>
    </Value>
    <Value>
      <Name>Machine-Readability</Name>
      <Description>Infrastructure data should be structured in machine-readable form using RDF and aligned with the ERA Ontology.</Description>
    </Value>
    <Value>
      <Name>Data Quality</Name>
      <Description>Validation rules should support compliance, data consistency, and correct representation of infrastructure relationships.</Description>
    </Value>
    <Value>
      <Name>Transparency</Name>
      <Description>Users should be able to discover and query information about the static rail network and its relevant parameters.</Description>
    </Value>
    <Goal>
      <Name>Infrastructure Information</Name>
      <Description>Maintain searchable information regarding the characteristics and capabilities of operational points and sections of lines in the static rail network.</Description>
      <Identifier>0bd1474d-fe4b-4e4d-884d-2f98b7ae7af5</Identifier>
      <SequenceIndicator>1</SequenceIndicator>
      <Objective>
        <Name>Network Parameters</Name>
        <Description>State the values of network parameters for each relevant subsystem or part subsystem in scope for RINF.</Description>
        <Identifier>b278ad87-6d19-44c8-b2ab-8c3b7a2706ca</Identifier>
        <SequenceIndicator>1.1</SequenceIndicator>
      </Objective>
      <Objective>
        <Name>Infrastructure Elements</Name>
        <Description>Represent core infrastructure elements such as tracks, operational points, sections of line, platforms, bridges, tunnels, and other relevant railway assets.</Description>
        <Identifier>bc8ee628-70d7-4a6a-8ea1-a9d65d3bfe50</Identifier>
        <SequenceIndicator>1.2</SequenceIndicator>
      </Objective>
      <Objective>
        <Name>Technical Characteristics</Name>
        <Description>Capture technical parameters such as gradient, speed, axle load, energy profiles, train detection systems, signalling, and other characteristics relevant to railway operations.</Description>
        <Identifier>dcf107d7-13d2-46bd-9618-135f109a8067</Identifier>
        <SequenceIndicator>1.3</SequenceIndicator>
      </Objective>
    </Goal>
    <Goal>
      <Name>Route Compatibility</Name>
      <Description>Support assessment of whether a railway vehicle can travel a route between two operational points.</Description>
      <Identifier>1ea30b96-b33e-4853-abec-38e7fd0957ad</Identifier>
      <SequenceIndicator>2</SequenceIndicator>
      <Objective>
        <Name>Route Compatibility Check</Name>
        <Description>Enable route compatibility checking based on infrastructure characteristics, vehicle characteristics, and relevant operational constraints.</Description>
        <Identifier>70bbf514-f467-4347-8898-46566b38e730</Identifier>
        <SequenceIndicator>2.1</SequenceIndicator>
        <Stakeholder StakeholderTypeType="Organization">
          <Name>Railway Undertakings</Name>
        </Stakeholder>
        <Stakeholder StakeholderTypeType="Organization">
          <Name>Infrastructure Managers</Name>
        </Stakeholder>
      </Objective>
      <Objective>
        <Name>Cross-Border Operations</Name>
        <Description>Facilitate safe and interoperable railway operations across national borders by providing harmonized infrastructure data.</Description>
        <Identifier>3ca372c7-fadc-422f-bfd8-5d3d27be5b71</Identifier>
        <SequenceIndicator>2.2</SequenceIndicator>
      </Objective>
    </Goal>
    <Goal>
      <Name>Semantic Interoperability</Name>
      <Description>Use the ERA Ontology as the foundational semantic model for railway infrastructure data in RINF.</Description>
      <Identifier>de3ce1c3-5a19-4d47-a027-88022559086a</Identifier>
      <SequenceIndicator>3</SequenceIndicator>
      <OtherInformation>The transition from XML Schema validation toward RDF-based semantic models and SHACL validation reflects recognition that railway infrastructure is fundamentally a network of interconnected entities rather than a collection of independent documents. Semantic interoperability enables validation and analysis of relationships among infrastructure elements at network scale.</OtherInformation>
      <Objective>
        <Name>RDF Alignment</Name>
        <Description>Structure RINF data using RDF and align it with the ERA Ontology.</Description>
        <Identifier>bba447cc-4b78-45cd-88d1-9d9ae67c0e59</Identifier>
        <SequenceIndicator>3.1</SequenceIndicator>
        <OtherInformation>Alignment with RDF enables infrastructure information to be represented as a knowledge graph supporting discovery, integration, inference, and interoperability across organizational and national boundaries.</OtherInformation>
      </Objective>
      <Objective>
        <Name>Controlled Terminology</Name>
        <Description>Use controlled taxonomies and SKOS concepts to standardize terminology and ensure consistent interpretation of infrastructure attributes.</Description>
        <Identifier>071152f2-c602-48c4-8442-8de29ae6637f</Identifier>
        <SequenceIndicator>3.2</SequenceIndicator>
      </Objective>
      <Objective>
        <Name>Topology Representation</Name>
        <Description>Represent railway topology, including network elements and relationships among them, to support graph-based analysis and validation.</Description>
        <Identifier>9db6bbbe-4297-462d-83dc-d74d29cdba32</Identifier>
        <SequenceIndicator>3.3</SequenceIndicator>
      </Objective>
    </Goal>
    <Goal>
      <Name>Data Quality</Name>
      <Description>Ensure RINF data are accurate, complete, consistent, timely, and compliant with applicable RINF requirements.</Description>
      <Identifier>93a507e9-d544-4e24-b0ed-82a10dc237eb</Identifier>
      <SequenceIndicator>4</SequenceIndicator>
      <OtherInformation>Data quality depends not only upon the correctness of individual records but also upon the validity of relationships among infrastructure elements. Graph-based validation techniques enable constraints to be evaluated across the network as a whole.</OtherInformation>
      <Objective>
        <Name>SHACL Validation</Name>
        <Description>Use SHACL rules to enforce mandatory parameters, data types, formats, and conditional dependencies.</Description>
        <Identifier>f76c98c5-1e8e-4a5d-9381-5c3e8ed20e8c</Identifier>
        <SequenceIndicator>4.1</SequenceIndicator>
        <OtherInformation>Unlike XML Schema validation, SHACL supports validation of relationships among entities represented in a graph. This capability enables detection of inconsistencies that may not be observable within individual records or documents.</OtherInformation>
      </Objective>
      <Objective>
        <Name>Provider Verification</Name>
        <Description>Encourage infrastructure managers to define verification processes and procedures for ensuring the accuracy, completeness, consistency, and timeliness of submitted data.</Description>
        <Identifier>d18d1eb5-2b72-4694-bde4-5089bd52a483</Identifier>
        <SequenceIndicator>4.2</SequenceIndicator>
        <Stakeholder StakeholderTypeType="Organization">
          <Name>Infrastructure Managers</Name>
        </Stakeholder>
      </Objective>
      <Objective>
        <Name>Change Notification</Name>
        <Description>Support user notification when RINF data change, upon demand through subscription.</Description>
        <Identifier>4e164496-44aa-4cc2-9136-7e5c20ff6dde</Identifier>
        <SequenceIndicator>4.3</SequenceIndicator>
      </Objective>
    </Goal>
    <Goal>
      <Name>Governance</Name>
      <Description>Maintain governance arrangements for RINF implementation, operation, data submission, and evolution of the ERA Vocabulary.</Description>
      <Identifier>3d811638-1559-4d7c-ad40-b9efdf420405</Identifier>
      <SequenceIndicator>5</SequenceIndicator>
      <Objective>
        <Name>Roles and Responsibilities</Name>
        <Description>Clarify responsibilities of ERA, Member States, infrastructure managers, and national registration entities under the RINF Regulation.</Description>
        <Identifier>f95ed82c-35bf-4be4-a0ab-6a6d7aa2929d</Identifier>
        <SequenceIndicator>5.1</SequenceIndicator>
        <OtherInformation>While RINF identifies organizations responsible for infrastructure information and its governance, the StratML Part 2 standard provides a complementary capability for explicitly documenting stakeholder roles, responsibilities, relationships, and performance indicators associated with goals and objectives.</OtherInformation>
      </Objective>
      <Objective>
        <Name>Vocabulary Change Control</Name>
        <Description>Manage changes to the ERA Vocabulary through a controlled process involving change requests, expert working groups, technical review, and formal approval before publication.</Description>
        <Identifier>77608e00-9a84-4ab4-a40e-c26fbc33960b</Identifier>
        <SequenceIndicator>5.2</SequenceIndicator>
      </Objective>
      <Objective>
        <Name>Stakeholder Participation</Name>
        <Description>Support participation by national registration entities, experts, and representative bodies in implementation and future development of RINF.</Description>
        <Identifier>520dcf6c-e954-484b-9083-bdfe7460386d</Identifier>
        <SequenceIndicator>5.3</SequenceIndicator>
      </Objective>
    </Goal>
  </StrategicPlanCore>
  <AdministrativeInformation>
    <PublicationDate>2026-06-13</PublicationDate>
    <Source>https://www.era.europa.eu/domains/registers/rinf_en</Source>
    <Submitter>
      <GivenName>Owen</GivenName>
      <Surname>Ambur</Surname>
      <EmailAddress>Owen.Ambur@verizon.net</EmailAddress>
    </Submitter>
  </AdministrativeInformation>
</StrategicPlan>