How italojsoliveira/phishing-process-ontology works
Main Components Identification
a) Conceptual Layer (OntoUML)
• Represents the conceptual version of PAPO
• Contains the core ontological definitions
• Uses Visual Paradigm and OntoUML Plugin
b) Implementation Layer (OWL)
• Represents the gUFO-based implementation
• Contains the operational version of the ontology
• Uses Protégé for editing
c) Documentation Layer
• Contains the HTML documentation
• Generated from the OWL implementation
Relationships and Data Flow
a) Primary Transformations:
• OntoUML (.vpp) → OntoUML JSON (transformation)
• OntoUML → OWL/TTL (implementation)
• OWL → HTML Documentation (generation)
b) Dependencies:
• UFO (Unified Foundational Ontology) as an external dependency
• GUFO as a dependency for the OWL implementation
Notes
Notes to indicate:
• The use of UFO as the foundational ontology
• The role of OntoUML-Schema in serialization
• The documentation generation process
• The phishing attack process characterization
Remember to include bidirectional traceability between the conceptual and implementation layers, as this is crucial for ontology maintenance and evolution.