# Modeling of Historical Marine Casualty on S-100 Electronic Navigational Charts
## 2 Background
### S-100-Based Data Modeling Methods  
The S-100 framework defines a structured and standardized approach for developing domain-specific data models in the maritime domain. It extends the General Feature Model (GFM) defined in ISO 19109, which provides a conceptual foundation for representing real-world geographic phenomena, their attributes, and relationships [2; 18]. The goal of S-100 is to enable interoperable, flexible, and extensible data exchange by separating the logical structure of data from its portrayal and encoding. To develop an S-100-based data model, a set of interrelated components must be defined and maintained as a package. These include the application schema, Feature Catalogue (FC), Portrayal Catalogue (PC), and symbology. The application schema, defined using Unified Modeling Language (UML), represents the conceptual structure of the data and is primarily intended to be human-readable. It serves as a logical blueprint for how features, attributes, and their associations are organized. The FC provides a standardized, machine-readable specification of the same content, enabling consistent data encoding, validation, and interoperability across systems. The PC defines how features should be visually represented in navigational systems, including symbols, colors, and display rules. Symbology resources support consistent visual rendering in ECDIS and other platforms. These components are tightly coupled and must be designed cohesively to ensure consistency in how maritime information is structured, exchanged, and displayed. Table 1 describes the key components defined during data modeling and how they are represented in the application schema. For example, a feature type represents real-world spatial objects such as aids to navigation and is used as core information directly displayed on ENCs. An information type contains non-spatial auxiliary data associated with a feature, such as the contact information of the managing authority linked to an aid to navigation. Attribute types describe the characteristics of these objects--the height of an aid to navigation may be defined as a real number, availability as a fixed-value enumeration, and color as an extensible code list. Objects can also have relationships with each other, allowing structures such as a single route being linked to multiple aids to navigation. All of these elements defined in the application schema exist at the type level, and the actual data created based on these definitions is referred to as an instance. In the S-100 framework, naming conventions are strictly defined to ensure consistency and clarity in how model elements are structured. When names consist of multiple words, \begin{table}
\begin{tabular}{p{142.3 pt} p{142.3 pt}} \hline \hline
**Implemented Class** & **Definition** \\ \hline Feature Type & A conceptual unit that represents real-world spatial or non-spatial entities and serves as the core data element displayed to users on ENCs. They are implemented as a class in UML. \\ \hline Information Type & A non-spatial data structure associated with a feature type, used to provide auxiliary information. They are implemented as a class in UML. \\ \hline Attribute Type & Properties of a Feature or Information Type that describe the state or characteristics of the object. They are implemented as properties of a class and can have data types depending on the nature of the data being represented (e.g., integer, real, text, date, enumeration, S100\_CodeList). \\ \hline Association Type & A structure that represents relationships between feature types or between a feature type and an information type. It can express various types of relationships, including associations, aggregations, and compositions. They are represented as connecting lines between classes. \\ \hline \hline \end{tabular}
\end{table} 
Table 1: Definitions of core components in the S-100 framework [2]. spaces are omitted; instead, each word begins with an uppercase letter to improve readability.