Editing MicroMVDs for exchange requirements/Element classes MicroMVD
From Wiki.OSArch
Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.
The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision | Your text | ||
Line 1: | Line 1: | ||
− | + | The following [[Using MicroMVDs for exchange requirements|MicroMVD]] vocabulary can be used to ensure geolocation information is set. | |
− | The following [[Using MicroMVDs for exchange requirements|MicroMVD]] vocabulary can be used to ensure | ||
<pre> | <pre> | ||
Feature: Element classes | Feature: Element classes | ||
− | In order to correctly identify | + | In order to correctly identify classes |
− | As any interested stakeholder | + | As any interested stakeholder |
All IFC elements must belong to the appropriate IFC class | 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 | Scenario: Ensure all IFC type elements use the correct IFC class | ||
− | * The element | + | * The element {guid} is an {ifc_class} |
− | * The element | + | * The element {guid} is an {ifc_class} only |
− | * The element | + | * The element {guid} should not exist because {reason} |
− | |||
</pre> | </pre> | ||
Line 22: | Line 24: | ||
! Example | ! Example | ||
! Description | ! Description | ||
+ | |- | ||
+ | | <code>{file}</code> | ||
+ | | project.ifc | ||
+ | | The filename or path to any IFC file. | ||
+ | |- | ||
+ | | <code>{schema}</code> | ||
+ | | IFC4 | ||
+ | | The schema version. At the moment, these are likely to be either IFC4 or IFC2X3. | ||
|- | |- | ||
| <code>{guid}</code> | | <code>{guid}</code> | ||
Line 30: | Line 40: | ||
| IfcWall | | IfcWall | ||
| This case insensitive text value must correspond to the full name of an IFC class. | | This case insensitive text value must correspond to the full name of an IFC class. | ||
− | |||
− | |||
− | |||
− | |||
|- | |- | ||
| <code>{reason}</code> | | <code>{reason}</code> | ||
Line 39: | Line 45: | ||
| You can write anything here to describe any reason. | | You can write anything here to describe any reason. | ||
|} | |} | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− |