## 6 Discussion  
This section highlights the advantages of using a CMS based on ontologies in driving systems, especially when compared to a more rigid, rule-based approach. The Onto-CMS allows for the clear and unambiguous representation of knowledge. It defines concepts, such as \"standardisation\" and \"unmodifiable\", that are semantically and logically connected. This enables the system to make intelligent, rule-based inferences. Without an ontology, the system can only execute specific checks based on predefined logic. For example, if we enrich the initial case study by requiring that the pedal icon shall be changed either by administrator users or when in maintenance mode, then the lack of a proper structure will cause a rise in the complexity of maintaining the logic underneath. Furthermore, the Onto-CMS enables interoperability among systems. The common ontology gives a standard structure for vehicles from different manufacturers. In this way, those vehicles can handle the diversity of systems efficiently. In the case of the emergency pedal icon, an ontology-based system can automatically block modifications, simplifying decision-making without needing to program every possible scenario. Without an ontology, each case would require a separate set of code, complicating maintenance due to the lack of a unified structure. Scalability is another key advantage of the Onto-CMS. This system does not require a complete revision every time new elements are added, but it can be expanded to redefine the ontology, allowing the system to grow without a complete rebuild. In addition, the Onto-CMS enables complex searches with query languages like SPARQL. For example, you might query the system using the \"modifiability\" of the emergency pedal icon and obtain a formal response following the norms established by the ontology. Another important benefit of an ontology-driven system is that system updates become more efficient. Changes to the ontology automatically update the code in a uniform manner and make ongoing maintenance easier. Basically, ontologies provide a structured form for demonstrating compliance with industry standards, which is important, especially for industries like automotive, where even the slightest failure in safety standards can have severe consequences. In the same context of standards compliance and vulnerability prevention, it is essential that the Onto-CMS addresses privacy and security concerns. Although the system has not yet been implemented, its design should incorporate advanced technologies to ensure the protection of sensitive driver data and compliance with applicable regulations, such as the GDPR. These solutions align with the goal of demonstrating the system's reliability and security, as well as improving its effectiveness in managing confidential data. During development, the Onto-CMS design included a dedicated security layer for RDF graphs that applies advanced privacy techniques directly within the data management phase. The plan is to incorporate privacy safeguards by leveraging the link-safety principles for RDF graphs presented by [PERSON] et al. (2019). For the integration of privacy concepts into the Onto-CMS, leveraging link-safety principles for RDF graphs, it is essential to use a semantic approach that combines robust anonymisation techniques with sensitive data management. The first step is to integrate privacy concepts into the system's ontology. This involves defining sensitive identifiers, such as driver ID or location data, and establishing specific criteria for data anonymisation. The ontology could, for example, be extended to include concepts such as \"sameAs\", indicating links to external entities and defining semantic rules that flag potential privacy risks. This semantic approach helps identify vulnerabilities and allows the implementation of targeted protection policies. The Onto-CMS must then apply anonymisation operations via SPARQL queries.