Summary: |
"Building projects are represented through a variety of documents such as drawings, diagrams, models, pictures, and textual information. Thesedocuments serve as a medium for communication between the different partners and disciplines within the AEC community. From a collaborative perspective, each document reflects on the author’s discipline as well as on the intended meaning. From a representation perspective, these documents present different aspects of the project such as the geometry, structure, context, and functional organization. As such, we can denote each of these documents an abstraction of the project.Without imposing an integrated product model, a ‘document-based’approach is preferable for the organization and management of thesedocuments. Here the documents are treated as individual entities,organized and related according to different categories and attributes.A drawback of this approach is that it is not possible to distinguishand relate components within these documents.To overcome this drawback, we propose the adoption of a modelinglanguage, e.g., XML, as a common syntax to re-represent theseabstractions. In this way, the documents can be interpreted and broken up into their components. These components within and between abstractions can then be related, and these relationships added to the representation. The result is an integrated model of components and relationships, represented in a uniform way.This paper focuses on some of the representational issues involved inthe process of interpreting, breaking up and relating abstractions. Weillustrate the potentials of this framework with the representation of anumber of abstractions belonging to a body of built architecture,specifically, Ottoman mosques.The paper includes a discussion of the following issues or questions:- How are the components represented and the relationships between them created?The components are defined as structures of tags and attribute-valuepairs, and constructed in a hierarchical manner. This enables a simplematching of components between various abstractions. For the creation of relationships, we therefore suggest a semi-automated approach where some of the relationships between components are automatically deduced from the structures and their composition in the representation.- What is the advantage of this representation?This representation does not impose any semantics, but only a common syntax for the definition and creation of an integrated model. This syntax allows one to link abstractions by defining the relationships as individual elements within the representation. Navigating the resulting model, not just the original abstractions but across abstractions through the respective links, yields new views of the project information." |