# Why we need both IfcAlignment.Axis and IfcAlignment.Representation?

**URL:** <https://forums.buildingsmart.org/t/why-we-need-both-ifcalignment-axis-and-ifcalignment-representation/2818>\
**Category:** Developers\
**Tags:** 4x3alpha\
**Created:** [July 1, 2020, 12:19pm UTC](https://forums.buildingsmart.org/t/why-we-need-both-ifcalignment-axis-and-ifcalignment-representation/2818 "2020-07-01T12:19:11Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![igor.sokolov](https://sea2.discourse-cdn.com/flex016/user_avatar/forums.buildingsmart.org/igor.sokolov/32/25_2.png) [@igor.sokolov](https://forums.buildingsmart.org/u/igor.sokolov)\
**Post date:** [July 1, 2020, 12:19pm UTC](https://forums.buildingsmart.org/t/why-we-need-both-ifcalignment-axis-and-ifcalignment-representation/2818/1 "2020-07-01T12:19:12Z")

</div>

Why IfcLinearPositioningElement adds nee attribute Axis, instead adding requirement to existing Representation attribute?  
How to treat if geometry Axis and Representation mismatch?