{'fraction_non_alphanumeric': 0.012953367875647668, 'fraction_numerical': 0.0, 'mean_word_length': 5.368131868131868, 'pattern_counts': {'":': 0, '<': 0, '<?xml version=': 0, '>': 0, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
Purpose of using Ontologies in Software Engineering:

Ontologies are used for formal representation of domain knowledge. Knowledge based Applications use Ontologies for knowledge sharing, which forms the primary use of Ontologies. Ontology development is largely aimed at AI experts with knowledge of diverse techniques originating from the field of AI. This knowledge is however unknown to a large section of the software industry. To bridge the gap between knowledge of Software Engineering practitioners and AI techniques, several proposals have been made suggesting the use of Ontologies in the field of Software Engineering. Proposals include the use of UML diagrams in the development of Ontologies. Infact, the Protégé Software developed by Stanford University has a tab which uniquely defines the use of UML diagrams in Ontology development. This functionality can be used to develop a UML diagrams from the Ontology developed. However, it can also be seen, that software engineering approaches themselves do not enable the representation of ontology concepts derived from description logics and other concepts included in the Semantic Web Languages.