# Modeling of Historical Marine Casualty on S-100 Electronic Navigational Charts
## 3 Method: Data Modeling of Marine Casualty
### Application Schema Definition
These attributes are inherited by all specific feature types, ensuring structural consistency across the data model. The column labeled 'Mult.' describes the multiplicity of each attribute, or how many times the attribute may appear in a single feature instance. This is expressed in the format '[min_max]', where min represents the minimum number of occurrences (e.g., '0' for optional), and max represents the maximum number (e.g., \"* for unlimited repetition). For example, a multiplicity of '[0..1]' for the deaths attribute means that it is optional and may contain at most one value, without implying an actual limit on the number of deaths. In contrast, attributes such as _IMONum_ have a multiplicity of '[0..*]', allowing them to appear multiple times within a single instance. This enables the model to represent incidents involving multiple vessels or descriptive records. Figure 3: Application schema represented as UML class diagram for marine casualty data model. The model defines an abstract feature type, Casualty, which includes common attributes across all incidents (e.g., date, deaths, location). Subtypes represent specific incident categories (e.g., CollisionAndContact, FireAndExplosion), each associated with a corresponding enumerated code list that describes incident subtypes. Code lists are shown in yellow and follow the S-100 coding convention. Spatial information is modeled using a location complex attribute containing latitude and longitude values. Table 5 presents specific feature types derived from _Casually_ along with their attributes. These types were defined by analyzing collected incident data and grouping similar cases into distinct categories. Each feature's attribute uses the data type S100_CodeList, which supports extensible enumerated values tailored to the classification requirements of each incident type. In accordance with the S-100 standard, this modeling approach defines code lists as separate classes to manage both predefined and extensible value sets consistently. The multiplicity of each attribute is set to [1..*], indicating that every incident must be assigned at least one classification code. This ensures that all feature instances \begin{table}
\begin{tabular}{c c c c} \hline \hline
**Feature** & **Attribute** & **Description** & **Data Type** & **Mult.** \\ \hline \multirow{5}{*}{Casualty} & date & Represents the date and time of the incident. & date & [0..1] \\ \cline{2-4}  & IMONum & Indicates the IMO number of the vessel involved in the incident. & text & [0..*] \\ \cline{2-4}  & deaths & Indicates the number of fatalities resulting from the incident. & integer & [0..1] \\ \cline{2-4}  & missings & Indicates the number of missing persons after the incident. & integer & [0..1] \\ \cline{2-4}  & severeInjuries & Represents the number of people who sustained severe injuries from the incident. & integer & [0..1] \\ \cline{2-4}  & location & Indicates the location related to the incident as a complex attribute & & \\ \cline{2-4}  & location & composed of the simple attributes latitude and longitude. This information explicitly specifies the position. & location & [0..*] \\ \cline{2-4}  & description & Provides a detailed description of the incident. & text & [0..1] \\ \cline{2-4}  & geometry & Geometric object come from Geometry class in the S-100 standard & GM\_Point & [0..*] \\ \hline \hline \end{tabular}
\end{table} 
Table 4: Attributes of the abstract feature type _Casualty_.