# IfcSurfaceCurveSweptAreaSolid does not consistently orient the swept profile **URL:** \ **Category:** Developers\ **Tags:** ifc4-errata\ **Created:** [June 21, 2019, 6:37pm UTC](https://forums.buildingsmart.org/t/ifcsurfacecurvesweptareasolid-does-not-consistently-orient-the-swept-profile/1533 "2019-06-21T18:37:31Z")\ **Posts on this page:** 1\ **Showing post:** 5
**Author:** ![ian](https://sea2.discourse-cdn.com/flex016/user_avatar/forums.buildingsmart.org/ian/32/21_2.png) [@ian](https://forums.buildingsmart.org/u/ian)\ **Post date:** [June 28, 2019, 7:22am UTC](https://forums.buildingsmart.org/t/ifcsurfacecurvesweptareasolid-does-not-consistently-orient-the-swept-profile/1533/5 "2019-06-28T07:22:29Z")
I chose “Coordination Model View 2.0” without really knowing what the limitations were. I suspect I should be using “Design Transfer View”. Which raises the question… How would I know? A developer has no insight into what’s allowed in an MVD. I suppose developers could read the MVD, but I suspect that nobody does that. It doesn’t help that the documentation site is broken as well as mentioned in: [The IFC4 documentation website is broken](https://forums.buildingsmart.org/t/the-ifc4-documentation-website-is-broken/1551) The fact that the vendors don’t then flag that a type is not allowed in the specified MVD drives home the fact that vendors aren’t properly supporting MVDs on import either. One would expect import errors logged with a message like “Entities of type IfcSurfaceCurveSweptAreaSolid are not supported in model view definition Coordination Model View 2.0.” I would also expect that if an entity did load, supported in the MVD or not, that at least it would show up according to the spec. --- _[View the full topic](https://forums.buildingsmart.org/t/ifcsurfacecurvesweptareasolid-does-not-consistently-orient-the-swept-profile/1533)._