WOODFINE CAPITAL PROJECTS BIM Design System

IfcRel*

Relationships

Token category anchored to the IFC 4.3 IfcRel* entity backbone. Designers and BIM operators consume these tokens when authoring elements in the Relationships family for Woodfine projects.

IFCIfcRel*categoryRelationshipscode overlays0 registered

Category bundle

The full token bundle for the Relationships category, in DTCG format. Consume directly via GET /tokens.json for the workspace-wide bundle, or filter by category programmatically.

Show DTCG JSON bundle
{
  "$description": "BIM RELATIONSHIPS token category — anchored to IFC 4.3 IfcRel* relationship entities. Sub-agent A renamed 'Connections' to 'Relationships' to better match IFC vocabulary.",
  "$schema": "https://design-tokens.github.io/community-group/format/",
  "bim": {
    "relationships": {
      "aggregates": {
        "$type": "bim.relationship",
        "$value": {
          "description": "Hierarchical decomposition. IfcSite aggregates IfcBuilding, IfcBuilding aggregates IfcBuildingStorey, IfcStair aggregates IfcStairFlight + IfcRailing.",
          "ifc_class": "IfcRelAggregates"
        }
      },
      "associates_classification": {
        "$type": "bim.relationship",
        "$value": {
          "description": "Element ↔ classification system link. Uniclass / OmniClass / MasterFormat references attach via this relationship.",
          "ifc_class": "IfcRelAssociatesClassification"
        }
      },
      "associates_material": {
        "$type": "bim.relationship",
        "$value": {
          "description": "Element ↔ material set link. The doorway through which service-materials joins service-buildings at runtime.",
          "ifc_class": "IfcRelAssociatesMaterial"
        }
      },
      "connects_path_elements": {
        "$type": "bim.relationship",
        "$value": {
          "description": "Wall-to-wall corner connectivity. Linear-element junction relationships.",
          "ifc_class": "IfcRelConnectsPathElements"
        }
      },
      "contained_in_spatial_structure": {
        "$type": "bim.relationship",
        "$value": {
          "description": "Element-to-spatial-container link. The most common relationship — every element belongs to exactly one spatial container (typically an IfcBuildingStorey).",
          "ifc_class": "IfcRelContainedInSpatialStructure"
        }
      },
      "defines_by_properties": {
        "$type": "bim.relationship",
        "$value": {
          "description": "Element ↔ Pset_* property set link. The carrier of all per-element property data.",
          "ifc_class": "IfcRelDefinesByProperties"
        }
      },
      "fills_element": {
        "$type": "bim.relationship",
        "$value": {
          "description": "Door/window filling its host wall opening. Authoritative parent-child linkage for openings.",
          "ifc_class": "IfcRelFillsElement"
        }
      },
      "voids_element": {
        "$type": "bim.relationship",
        "$value": {
          "description": "Opening element subtraction relationship. The parent of fills_element.",
          "ifc_class": "IfcRelVoidsElement"
        }
      }
    }
  }
}

Code overlays applicable

This token's IFC anchor (IfcRel*) accepts IfcConstraint relationships from any jurisdictional code overlay registered in service-codes. Composition order: municipal → provincial → federal → accessibility.

No overlays registered for IfcRel* in this jurisdiction. First Woodfine BC RS-1 encoding lands at v0.0.3 (per sub-agent B's 6–8 week roadmap).

How City Code as Composable Geometry works →