Editing MicroMVDs for exchange requirements/Project setup 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 basic project metadata is set, as a minimum requirement for all BIM projects. | The following [[Using MicroMVDs for exchange requirements|MicroMVD]] vocabulary can be used to ensure basic project metadata is set, as a minimum requirement for all BIM projects. | ||
Line 10: | Line 9: | ||
Scenario: Receiving a file | Scenario: Receiving a file | ||
− | * IFC data must use the | + | * The IFC file "{file}" must be provided |
+ | * IFC data must use the {schema} schema | ||
Scenario: Exempt files | Scenario: Exempt files | ||
* The IFC file "{file}" is exempt from being provided | * The IFC file "{file}" is exempt from being provided | ||
− | * No further requirements are specified because | + | * No further requirements are specified because {reason} |
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
</pre> | </pre> | ||
− | |||
− | |||
{| class="wikitable" | {| class="wikitable" | ||
Line 46: | Line 33: | ||
| we don't need it | | we don't need it | ||
| You can write anything here to describe any reason. | | You can write anything here to describe any reason. | ||
+ | |} | ||
+ | |||
+ | {| class="wikitable" | ||
+ | ! Test definition | ||
+ | ! Justification | ||
|- | |- | ||
− | | <code>{ | + | | <code>Given the IFC file "{file}"</code> |
− | | | + | | An IFC-SPF file is the expected format for a project. |
− | |||
− | |||
− | |||
− | |||
− | |||
|- | |- | ||
− | | <code>{ | + | | <code>Then the file should be an {schema} file</code> |
− | | | + | | Project data must conform to a client-nominated schema. The <code>{schema}</code> may be IFC2X3 or IFC4 in general. |
− | |||
|- | |- | ||
− | | <code>{ | + | | <code>Then the project has a Name attribute with a value of "{value}"</code> |
− | + | | A project must have a name given to it. | |
− | | A | ||
|- | |- | ||
− | | <code>{ | + | | <code>Then the project has a LongName attribute with a value of "{value}"</code> |
− | | | + | | A project generally also has a longer name associated with it. |
− | |||
|- | |- | ||
− | | <code> | + | | <code>Then the project should have geolocation data</code> |
− | | | + | | This checks for geolocation according to the buildingSMART recommendation in IFC2X3 and the native elements in IFC4. |
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
|- | |- | ||
− | + | | <code>Given there is at least one IfcSite element</code> | |
− | + | | Most projects have a site. | |
|- | |- | ||
− | + | | <code>Then there is an IfcSite element with a Name attribute with a value of "{value}"</code> | |
− | + | | If a site exists, it typically has a name. | |
− | |||
− | |||
− | | <code> | ||
− | | | ||
|- | |- | ||
− | | | + | | <code>Given there is at least one IfcBuilding element</code> |
− | + | | Most projects have a building. | |
− | | | ||
− | |||
− | |||
− | |||
|- | |- | ||
− | + | | <code>Then there is an IfcBuilding element with a Name attribute with a value of "{value}"</code> | |
− | + | | If a building exists, it typically has a name. | |
− | |||
− | |||
− | | <code> | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | | | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
|} | |} | ||
− | |||
− |