Query-by-object interface for dynamic access and information requirement elicitation
Graduate Sch. of Comput. Sci. & Eng., Univ. of Aizu, Fukushima, JapanDOI: 10.1109/ICMB.2005.84 Conference: Mobile Business, 2005. ICMB 2005. International Conference on
Source: IEEE Xplore
Information requirement elicitation (IRE) is essential in wireless Web service to elicit information requirements through interactive choice prompts. We present a high-level user interface for an IRE-enabled information system, in the context of database queries by a mobile Web user. The prototype is based on the notion of a query-by-object (QBO) approach of building a query using multiple user-level steps. The test prototype system uses the mobile information devices profile (MIDP) of the Java 2 Platform, Micro Edition (J2ME), for a wireless front end, and a Java 2 Platform, Enterprise Edition (J2EE) application server and an object-relational database management system (ORDBMS) at the back end. A sample set of dynamic queries demonstrates ease of use by the users.
Conference Paper: Supporting spatial data queries for mobile services[Show abstract] [Hide abstract]
ABSTRACT: In the last few years, many GIS applications have appeared on the Web giving users access to both spatial and non-spatial (attribute) data. Web access to GIS resources needs to address the possibility of access via handheld devices such as mobile phones, PDAs or pocket computers. Currently, only a few research studies are available on high-level user interface for spatial queries on such devices. Thus, an important research problem is to design user-friendly interfaces for mobile Web GIS. Query-by-example (QBE) is a user-friendly language developed for a relational database management system (RDBMS). Many RDBMSs have included support for spatial extensions. In this paper, we make an effort to create extensions for QBE to support spatial queries on mobile devices. It is called spatial mQBE. We show that spatial mQBE is a simple and user-friendly interface. The main strengths of this interface are its simplicity to express a query and its expressive power.Web Intelligence, 2005. Proceedings. The 2005 IEEE/WIC/ACM International Conference on; 10/2005
Conference Paper: Spatial QBE interface for Web GIS[Show abstract] [Hide abstract]
ABSTRACT: Many applications use geographic data, such as land management, urban planning, tourism, vehicle guidance and navigation, and e-commerce. A related research problem is to define user-friendly interfaces for Web GIS. There is a need for the definition of simple and user-friendly interfaces to allow the users to pose ad-hoc queries. Query-by-example (QBE) is a user-friendly language developed for a RDBMS. However, many RDBMS have included support for spatial extensions in SQL. QBE has not been extended in line with these extensions. In this paper, we make an effort to create extensions for QBE to support spatial queries and thus calling it spatial QBE. We show that spatial QBE is a simple and user-friendly interface for Web users. It can cater to both spatial and common database queries. The main strengths of this interface are its simplicity to express a query and its expressive power.Computer and Information Technology, 2005. CIT 2005. The Fifth International Conference on; 10/2005
- [Show abstract] [Hide abstract]
ABSTRACT: Scientists and researchers often search for lunar features from lunar names within geographic data from Moon. Currently, there are few facilities available for above search. Therefore, we propose starting construction of lunar nomenclature search system based on high-level query language interfaces, such as query by example (QBE) and Query-By-Object approach. Using this method, we can designate specific points of the moon using nearby name by lunar feature names. Currently, we are focusing on the region including Copernicus crater.Databases in Networked Information Systems, 5th International Workshop, DNIS 2007, Aizu-Wakamatsu, Japan, October 17-19, 2007, Proceedings; 01/2007
Data provided are for informational purposes only. Although carefully collected, accuracy cannot be guaranteed. The impact factor represents a rough estimation of the journal's impact factor and does not reflect the actual current impact factor. Publisher conditions are provided by RoMEO. Differing provisions from the publisher's actual policy or licence agreement may be applicable.