Difference between revisions of "MicroMVDs for exchange requirements/Element classes MicroMVD"
From Wiki.OSArch
Line 15: | Line 15: | ||
* The element {guid} is an {ifc_class} | * The element {guid} is an {ifc_class} | ||
* The element {guid} is an {ifc_class} only | * The element {guid} is an {ifc_class} only | ||
+ | * The element {guid} is further defined as a {ifc_class} | ||
* The element {guid} should not exist because {reason} | * The element {guid} should not exist because {reason} | ||
</pre> | </pre> |
Revision as of 01:59, 21 July 2020
The following MicroMVD vocabulary can be used to ensure IFC elements belong to the correct IFC class.
Feature: Element classes In order to correctly identify classes As any interested stakeholder All IFC elements must belong to the appropriate IFC class Scenario: Receiving a file * The IFC file "{file}" must be provided * IFC data must use the {schema} schema Scenario: Ensure all IFC type elements use the correct IFC class * The element {guid} is an {ifc_class} * The element {guid} is an {ifc_class} only * The element {guid} is further defined as a {ifc_class} * The element {guid} should not exist because {reason}
You can fill out the variables using the guide below.
Variable | Example | Description |
---|---|---|
{file}
|
project.ifc | The filename or path to any IFC file. |
{schema}
|
IFC4 | The schema version. At the moment, these are likely to be either IFC4 or IFC2X3. |
{guid}
|
28q3AgmxP5cepIweO5Of$o | This is a 22 character GlobalId for a particular IFC element. |
{ifc_class}
|
IfcWall | This case insensitive text value must correspond to the full name of an IFC class. |
{reason}
|
we don't need it | You can write anything here to describe any reason. |