Diff: reference/bim-token-taxonomy
From ef58b39 to ef58b39
+0 / −0 lines
| Before | After |
|---|---|
| --- | --- |
| schema: foundry-doc-v1 | schema: foundry-doc-v1 |
| type: topic | type: topic |
| slug: bim-token-taxonomy | slug: bim-token-taxonomy |
| title: BIM Token Taxonomy | title: BIM Token Taxonomy |
| audience: vendor-public | audience: vendor-public |
| bcsc_class: current-fact | bcsc_class: current-fact |
| language: en | language: en |
| paired_with: bim-token-taxonomy.es.md | paired_with: bim-token-taxonomy.es.md |
| ## See Also | ## See Also |
| - [[bim-design-philosophy]] | - [[bim-design-philosophy]] |
| - [[bim-aec-muscle-memory]] | - [[bim-aec-muscle-memory]] |
| - [[flat-file-bim-leapfrog]] | - [[flat-file-bim-leapfrog]] |
| - [[design-color]] | - [[design-color]] |
| --- | --- |
| Foundry’s BIM Token Taxonomy organizes the Building Design System into eight primitive categories anchored to the IFC 4.3 (ISO 16739-1:2024) entity hierarchy. This alignment ensures that design-system tokens correspond directly to canonical AEC classification conventions, facilitating seamless data exchange across the openBIM ecosystem. | Foundry’s BIM Token Taxonomy organizes the Building Design System into eight primitive categories anchored to the IFC 4.3 (ISO 16739-1:2024) entity hierarchy. This alignment ensures that design-system tokens correspond directly to canonical AEC classification conventions, facilitating seamless data exchange across the openBIM ecosystem. |
| ## Eight Primitive Token Categories | ## Eight Primitive Token Categories |
| | Primitive | IFC Anchor | Description | | | Primitive | IFC Anchor | Description | |
| | :--- | :--- | :--- | | | :--- | :--- | :--- | |
| | **SPATIAL** | `IfcSpatialElement` | Hierarchy of Site, Building, Storey, and Space. | | | **SPATIAL** | `IfcSpatialElement` | Hierarchy of Site, Building, Storey, and Space. | |
| | **ELEMENTS** | `IfcBuiltElement` | Physical components: walls, slabs, doors, windows, etc. | | | **ELEMENTS** | `IfcBuiltElement` | Physical components: walls, slabs, doors, windows, etc. | |
| | **SYSTEMS** | `IfcDistributionElement` | MEP components: pipes, ducts, and distribution networks. | | | **SYSTEMS** | `IfcDistributionElement` | MEP components: pipes, ducts, and distribution networks. | |
| | **MATERIALS** | `IfcMaterial` | Material definitions, layer sets, and constituent sets. | | | **MATERIALS** | `IfcMaterial` | Material definitions, layer sets, and constituent sets. | |
| | **ASSEMBLIES** | `IfcElementAssembly` | Hierarchical compositions and furnishings. | | | **ASSEMBLIES** | `IfcElementAssembly` | Hierarchical compositions and furnishings. | |
| | **PERFORMANCE** | `IfcPropertySet` | Property templates (Pset_*) and quantities (Qto_*). | | | **PERFORMANCE** | `IfcPropertySet` | Property templates (Pset_*) and quantities (Qto_*). | |
| | **IDENTITY+CODES** | `IfcClassificationRef` | Taxonomy references (Uniclass) and jurisdictional constraints. | | | **IDENTITY+CODES** | `IfcClassificationRef` | Taxonomy references (Uniclass) and jurisdictional constraints. | |
| | **RELATIONSHIPS** | `IfcRel*` | Connectivity, containment, and semantic associations. | | | **RELATIONSHIPS** | `IfcRel*` | Connectivity, containment, and semantic associations. | |
| ## Classification Floor: Uniclass 2015 | ## Classification Floor: Uniclass 2015 |
| Foundry adopts **Uniclass 2015** as its universal classification floor. Published by the NBS and recognized globally in the openBIM community, Uniclass provides the baseline semantic tagging for every element in the system. While deployment-specific taxonomies (e.g., OmniClass or MasterFormat) can be layered on top, Uniclass 2015 serves as the mandatory default, ensuring consistent data structures from day one. | Foundry adopts **Uniclass 2015** as its universal classification floor. Published by the NBS and recognized globally in the openBIM community, Uniclass provides the baseline semantic tagging for every element in the system. While deployment-specific taxonomies (e.g., OmniClass or MasterFormat) can be layered on top, Uniclass 2015 serves as the mandatory default, ensuring consistent data structures from day one. |
| ## Component Architecture | ## Component Architecture |
| The Building Design System defines 18 core components across three categories: | The Building Design System defines 18 core components across three categories: |
| 1. **Universal AEC (10):** `SpatialTree`, `PropertiesPanel`, `Viewport3D`, `ViewNavigator`, `Toolbar`, `StatusBar`, `SelectionFilter`, `TypeBrowser`, `SectionPlane`, `AnnotationLayer`. | 1. **Universal AEC (10):** `SpatialTree`, `PropertiesPanel`, `Viewport3D`, `ViewNavigator`, `Toolbar`, `StatusBar`, `SelectionFilter`, `TypeBrowser`, `SectionPlane`, `AnnotationLayer`. |
| 2. **Console-Unique (4):** `BimGuidSearch`, `BimAuditLog`, `BimDashboard`, `BimExportPanel`. | 2. **Console-Unique (4):** `BimGuidSearch`, `BimAuditLog`, `BimDashboard`, `BimExportPanel`. |
| 3. **Workplace-Unique (4):** `MaterialsBrowser`, `TypeEditor`, `ClashDetector`, `VersionHistory`. | 3. **Workplace-Unique (4):** `MaterialsBrowser`, `TypeEditor`, `ClashDetector`, `VersionHistory`. |
| ### The Component-Recipe Pattern | ### The Component-Recipe Pattern |
| Each component follows a standardized recipe structure to ensure framework independence: | Each component follows a standardized recipe structure to ensure framework independence: |
| * `recipe.html`: Semantic, framework-agnostic markup. | * `recipe.html`: Semantic, framework-agnostic markup. |
| * `recipe.css`: Namespaced BEM CSS. | * `recipe.css`: Namespaced BEM CSS. |
| * `aria.md`: The accessibility and interaction contract. | * `aria.md`: The accessibility and interaction contract. |
| Host frameworks (e.g., Yew, Leptos, or vanilla TypeScript) integrate by mounting the recipe markup and attaching the required logic while strictly adhering to the ARIA contract. | Host frameworks (e.g., Yew, Leptos, or vanilla TypeScript) integrate by mounting the recipe markup and attaching the required logic while strictly adhering to the ARIA contract. |
| ## Release Roadmap | ## Release Roadmap |
| * **v0.0.1 (Current):** `SpatialTree`, `PropertiesPanel`, and `Viewport3D` are released as foundational components. | * **v0.0.1 (Current):** `SpatialTree`, `PropertiesPanel`, and `Viewport3D` are released as foundational components. |
| * **v0.0.2 (Planned):** Console-unique and workplace-unique components will ship alongside the building element index and BIM authoring features. | * **v0.0.2 (Planned):** Console-unique and workplace-unique components will ship alongside the building element index and BIM authoring features. |
| --- | --- |
| *Copyright © 2026 Woodfine Capital Projects Inc. Licensed under [Creative Commons Attribution 4.0 International](https://creativecommons.org/licenses/by/4.0/).* | *Copyright © 2026 Woodfine Capital Projects Inc. Licensed under [Creative Commons Attribution 4.0 International](https://creativecommons.org/licenses/by/4.0/).* |
| *Woodfine Capital Projects™, Woodfine Management Corp™, PointSav Digital Systems™, Totebox Orchestration™, and Totebox Archive™ are trademarks of Woodfine Capital Projects Inc., used in Canada, the United States, Latin America, and Europe. All other trademarks are the property of their respective owners.* | *Woodfine Capital Projects™, Woodfine Management Corp™, PointSav Digital Systems™, Totebox Orchestration™, and Totebox Archive™ are trademarks of Woodfine Capital Projects Inc., used in Canada, the United States, Latin America, and Europe. All other trademarks are the property of their respective owners.* |