How iccmu/leximus works
Main Components
• Frontend Interface: Indicated by the “templates” and “static” folders within versions (e.g., V5 and v6). This includes:
– The visual panels: visualization panel (the hierarchical/pyramidal view), node information panel, panel for properties, a metadata editor, and a YAML/JSON viewer.
– The drag & drop functionality for reordering nodes.
• Backend Logic: Found in files such as V5/main.py and v6/main.py. This handles:
– Conversion between YAML and JSON representations.
– Management of the taxonomic data structure (nodes, metadata, and properties).
– Invoking export functionality to convert the ontology into OWL.
• Data Storage: The data files (such as the DATA folder with JSON and CSV files) and additional configuration in various version folders hold the data models:
– The node structure and dictionary of metadata.
– Registries for the properties assigned to each node.
• API Integration for OWL Export: Mentioned in the README with a service available at http://localhost:8000 that converts the taxonomy data to OWL.
Out Relationships and Interactions
• The End-User interacts with the frontend UI through a modern browser (supporting JavaScript ES6+), initiating actions (drag & drop, selecting nodes, editing metadata).
• The frontend communicates with the Python backend (via main.py) where business logic processes the changes, updates data structures, and converts data between YAML/JSON formats.
• When the user triggers an export, the backend calls the external API (OWL export) to transform the data into OWL standard.
• The data persistence layer (reading/writing to JSON, CSV, YAML files, etc.) underpins both the backend processing and the visual feedback provided to the user.
Important Architectural Patterns
• Separation of Concerns: Clear distinction between presentation (HTML/CSS/JS in static and templates folders), application logic (Python scripts in V5 and v6), and data management (files in DATA, v6/data, etc.).
• Modular Design: Different folders (v1, v2, v3, v4, v6) indicate iterative versions that likely incorporate improvements or features incrementally.
• MVC-Like Approach (or close approximation): The “view” is rendered by the frontend templates, the “controller” lies in the main.py scripts, and the “model” is represented by the JSON, YAML, and CSV representations of the taxonomy.
Relevant Technologies
• Web technologies: HTML, CSS, JavaScript (for the drag & drop and visual editing components).
• Python: Backend scripts that process data and interface with the API.
• Formats and Standards: YAML, JSON, OWL, and possibly RDF for semantic integration.
• External API for conversion: The system calls an export endpoint (likely HTTP-based) to generate OWL output.
• Important frameworks or libraries you identify (e.g., JavaScript libraries for drag & drop if mentioned in the templates, and Python’s framework for serving the web pages).
Essential Elements
– Frontend presentation logic.
– User action handling and data validation.
– Backend processing and conversion services.
– Data storage and persistence.
– Integration with external services (OWL export API).
• This approach will help in clarifying the responsibilities of each module and the flow of control and data through the system.