CumInCAD is a Cumulative Index about publications in Computer Aided Architectural Design supported by the sibling associations ACADIA, CAADRIA, eCAADe, SIGraDi, ASCAAD and CAAD futures
Hits 1 to 20 of 515
Reformat results as: short short into frame detailed detailed into frame
From the viewpoint of content-based retrieval, the researcher analyzes spatial information of a floor plan, with a focus on the apartment unit floor plan common in Korea. Then the metadata items are extracted in a structured manner. To manage the items efficiently, the researcher develops a data model for spatial information according to the concept of the “Structured Floor Plan”. The main object of content to retrieve is a spatial network that consists of nodes of spaces and their linkages. There are two ways to organize the metadata: the traditional index files and the RDF (Resource Description Framework). While the index files are still efficient with computability, the RDF applies greater options to retrieve, such as fuzzy predicates, semantic predicates, and so on. To exploit the metadata, this research shows several possibilities of query operations that present a set of sample queries about L-DK(Living room – Dining room – Kitchen). Implementation of the prototype system is divided into three parts: 1) a modeling module using Vitruvius; 2) an indexing module using MS SQL Server? 2000 in conjunction XML; and 3) a browsing module using the SpaceScope browser.
The future works may consider XML-based databases and a knowledge based query language, such as RQL/XQL, working on such databases. The more specific domain knowledge is involved, the more practical systems would be. Even in architecture, there may be a diverse range of domain knowledge, such as design, building performance, facility management, energy management, post occupied evaluation, historical research, and so on. Also the issue of interface should be investigated in depth, so that it will be adequate to the needs of the architectural field.
Decisions taken in the ‘private design space’ of the design team or ‘actor’ are closely related to the type of support that can be provided by a Collaborative Design system: automatic checks performed by activating procedures and methods, reporting of 'local' conflicts, methods and knowledge for the resolution of ‘local’ conflicts, creation of new IT objects/ building components, who the objects must refer to (the ‘owner’), 'situated' aspects (Gero and Reffat, 2001) of the IT objects/building components.
Decisions taken in the ‘shared design space’ involve aspects that are typical of networked design and that are partially present in the ‘private’ design space. Cross-checking, reporting of ‘global’ conflicts to all those concerned, even those who are unaware they are concerned, methods for their resolution, the modification of data structure and interface according to the actors interacting with it and the design phase, the definition of a 'dominus' for every IT object (i.e. the decision-maker, according to the design phase and the creation of the object). All this is made possible both by the model for representing the building (Carrara and Fioravanti, 2001), and by the type of IT representation of the individual building components, using the methods and techniques of Knowledge Engineering through a structured set of Knowledge Bases, Inference Engines and Databases. The aim is to develop suitable tools for supporting integrated Process/Product design activity by means of a effective and innovative representation of building entities (technical components, constraints, methods) in order to manage and resolve conflicts generated during the design activity.
For more results click below: