CC-BY
this specification document is based on the
EAD stands for Encoded Archival Description, and is a non-proprietary de facto standard for the encoding of finding aids for use in a networked (online) environment. Finding aids are inventories, indexes, or guides that are created by archival and manuscript repositories to provide information about specific collections. While the finding aids may vary somewhat in style, their common purpose is to provide detailed description of the content and intellectual organization of collections of archival materials. EAD allows the standardization of collection information in finding aids within and across repositories.
The specification of EAD with TEI ODD is a part of a real strategy of defining specific customisation of EAD that could be used at various stages of the process of integrating heterogeneous sources.
This methodology is based on the specification and customisation method inspired from the long lasting experience of the Text Encoding Initiative (TEI) community. In the TEI framework, one has the possibility of model specific subset or extensions of the TEI guidelines while maintaining both the technical (XML schemas) and editorial (documentation) content within a single framework.
This work has lead us quite far in anticipating that the method we have developed may be of a wider interest within similar environments, but also, as we imagine it, for the future maintenance of the EAD standard. Finally this work can be seen as part of the wider endeavour of European research infrastructures in the humanities such as CLARIN and DARIAH to provide support for researchers to integrate the use of standards in their scholarly practices. This is the reason why the general workflow studied here has been introduced as a use case in the umbrella infrastructure project Parthenos which aims, among other things, at disseminating information and resources about methodological and technical standards in the humanities.
We used ODD to encode completely the EAD standard, as well as the guidelines provided by the Library of Congress.
The EAD ODD is a XML-TEI document made up of three main parts. The first one is,
like any other TEI document, the
The Yufa splines themselves are a 5-star asset for OMSI 2 content creation. The download and installation experience, however, is a frustrating 2 stars due to link rot and poor organization. If you’re patient enough to dig through pinned forum threads (try Marcels OMSI-Forum or the OMSI 2 WebDisk using the search term “Yufa Splines”), you’ll be rewarded with a stable, essential pack. Just be prepared to spend 30 minutes hunting before you can drive.
Even after finding a working archive, the folder structure isn’t always clear. You might need to manually place .sli files into OMSI 2\Splines\Yufa\ and ensure textures go into Texture subfolders. Miss one file, and the map loads with giant red error messages instead of roads. No included documentation is common. omsi 2 yufa splines download
Look for a user-uploaded “Yufa Splines repack” from 2018 or later—those tend to have the correct folder hierarchy. Always scan downloads with an antivirus, as some older hosting sites are risky. The Yufa splines themselves are a 5-star asset
Here’s a review based on the typical user experience for downloading and using in OMSI 2 , written from a simulator enthusiast’s perspective. Title: Essential for custom map builders, but the hunt is half the battle Rating: ⭐⭐⭐⭐☆ (4/5) Just be prepared to spend 30 minutes hunting
If you’ve spent any time building or even just driving detailed custom maps in OMSI 2 , you’ve likely run into the dreaded “missing spline” error. Among the most sought-after fixes is the —a collection of road, sidewalk, and terrain splines originally created by the user Yufa.
Once you actually get your hands on the Yufa splines and install them correctly, they’re a game-changer. The pack fills in countless gaps left by default OMSI assets, especially for European-style rural roads, curbless village lanes, and seamless pavement transitions. They load efficiently and look natural in-game, far less clunky than some of the base splines. For map makers, these are practically mandatory—many high-quality German and Austrian maps on platforms like OMSI-Web or Marcels OMSI-Forum explicitly list Yufa splines as a dependency.
Here’s where the experience falls apart. You can’t just click one clean link. Yufa splines were originally hosted on now-defunct file sharing sites or deep within forum threads from 2013–2015. Searching “omsi 2 yufa splines download” leads you through a maze of sketchy upload sites, expired MediaFire links, and German forum posts requiring registration. Some so-called “complete packs” are actually incomplete or mixed with other authors’ splines, causing conflicts.