Editing MicroMVDs for exchange requirements/Classification 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 9: | Line 9: | ||
As someone who needs to catalogue BIM data in a structured and organised manner | As someone who needs to catalogue BIM data in a structured and organised manner | ||
Classification systems data must be assigned to each relevant element | Classification systems data must be assigned to each relevant element | ||
+ | |||
+ | Scenario: Receiving a file | ||
+ | * The IFC file "{file}" must be provided | ||
+ | * IFC data must use the {schema} schema | ||
Scenario: The appropriate classification systems are referenced in the model | Scenario: The appropriate classification systems are referenced in the model | ||
− | * The classification | + | * The classification {guid} specifies the system {name} |
− | * The classification | + | * The classification {guid} is published by {source} |
− | * The classification | + | * The classification {guid} is the edition {edition} on {edition_date} |
− | * The classification | + | * The classification {guid} has the description "{description}" |
− | * The classification | + | * The classification {guid} is referenced by the website {location} |
− | * The classification | + | * The classification {guid} has a hierarchy denoted by the tokens {tokens} |
Scenario: The relevant elements are assigned to the classification system | Scenario: The relevant elements are assigned to the classification system | ||
− | * The element | + | * The element {guid} is classified as a "{identification}" with name "{reference_name}" |
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
</pre> | </pre> | ||
Line 36: | Line 32: | ||
! 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 66: | Line 70: | ||
|- | |- | ||
| <code>{tokens}</code> | | <code>{tokens}</code> | ||
− | | | + | | '_' |
− | | A | + | | A comma separated, single quoted list of all of the separating tokens which denote hierarchy in the classification system, taken from the standard list if it exists. |
|- | |- | ||
| <code>{identification}</code> | | <code>{identification}</code> | ||
Line 77: | Line 81: | ||
| A single classification reference name for the particular classification system, taken from the standard list if it exists. | | A single classification reference name for the particular classification system, taken from the standard list if it exists. | ||
|} | |} | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− |