Developer Creates Semantic Taxonomy System to Organize Application Data Namespaces

New routing rules aim to prevent contamination between user identity, interface state, and operational data

edit

By LineZotpaper

Published12 April 2026

Read Time2 min

A developer has published detailed guidelines for organizing data routes within the `.me` namespace, creating a structured taxonomy designed to prevent mixing of canonical user data with temporary interface and operational states in software applications.

The semantic taxonomy system, outlined in a technical document published on DEV Community by developer Sui Gn, establishes strict rules for how different types of application data should be organized and accessed within the .me namespace structure.

The core principle separates data into distinct categories: canonical semantics (permanent user identity data), operational state (runtime system information), and visual state (temporary interface elements). The system designates profile.* and auth.* paths as canonical data that must be publishable and resolvable by cleaker.me, while ui.* and runtime.* paths remain local to individual devices or sessions.

"The namespace is the owner of the meaning," the document states, emphasizing that data organization must follow semantic logic rather than convenience. This approach aims to prevent what the author calls "contamination" - the mixing of different data types that can lead to architectural problems in software development.

The taxonomy includes specific writing and reading rules. GUI components are forbidden from writing to canonical paths like profile.* or auth.* unless explicitly flagged with allowCanonicalWrite: true. Meanwhile, identity components must read exclusively from canonical paths, while view state components should access ui.cleaker.* and operational components should use runtime.cleaker.*.

The document provides clear examples of correct implementation, such as storing usernames in me.profile.username and modal states in me.ui.cleaker.modalOpen. It explicitly warns against incorrect practices like storing interface elements in profile data or mixing device-specific information with user identity.

The system appears designed for the "Cleaker" application or platform, with the author describing the document as "the bible for the Cleaker refactor and all future components." This suggests the taxonomy is being implemented as part of a significant application restructuring effort.

The approach reflects broader software development trends toward better data organization and separation of concerns, principles that help maintain code quality and prevent technical debt as applications scale.

Analysis

Why This Matters

Software architecture decisions like this taxonomy system can significantly impact application maintainability and developer productivity over time
The separation of canonical, operational, and visual data represents a best practice that could influence how other developers structure their applications
Clear data organization rules become critical as applications grow in complexity and team size

Background

Namespace organization and data separation have long been fundamental challenges in software development. As applications become more complex, developers often struggle with "data contamination" - mixing different types of information in ways that create dependencies and maintenance burdens. Traditional approaches like Model-View-Controller (MVC) architecture address some of these concerns, but modern applications with real-time interfaces, user sessions, and distributed data often require more nuanced approaches. The .me namespace concept appears to be part of a broader trend toward user-centric data organization, where individual user contexts become the primary organizational principle rather than application features or technical layers.

Key Perspectives

Software Architects: This type of semantic taxonomy provides clear boundaries that can prevent common architectural mistakes and technical debt accumulation, making it valuable for long-term project health. Frontend Developers: The strict read/write rules may initially seem restrictive but could reduce bugs caused by accidental data mixing and improve code predictability. Critics/Skeptics: Some developers might view such rigid categorization as over-engineering, potentially adding unnecessary complexity for smaller applications or creating barriers to rapid development and iteration.

What to Watch

Implementation feedback from developers using this taxonomy in the Cleaker application refactor
Whether similar semantic organization patterns emerge in other development communities
Performance implications of the namespace separation in real-world applications

Sources

Semantic Taxonomy – Official Path Rules — DEV Community