The WWW has a great potential of evolving into a g l o b ally distributed digital document library.The primary use of such a library is to retrieve information quickly and easily. Because of the size of these libraries, simple keyword searches often result in too many matches. More complex searches involving boolean expressions are di cult to formulate and understand. This paper describes QBT (Query By Templates), a visual method for formulating queries for structured document databases modeled with SGML. Based on Zloof's QBE (Query By Example), this method incorporates the structure of the documents for composing powerful queries. The goal of this technique is to design an interface for querying structured documents without prior knowledge of the internal structure. This paper describes the rationale behind QBT, illustrates the query formulation principles using QBT, and describes results obtained from a usability analysis on a prototype implementation of QBT on the Web using the Java T M programming language.

When describing Web services, one of the obvious aspects that needs representing is Quality of Service" (QoS), the capability of a Web service to meet an acceptable level of service as per factors such as availability and accessibility. However too much of a focus on developing functional QoS ontologies has led to an over-emphasis on representing solely QoS metrics and units of measurement. For instance, what does round trip time actually mean? Is the round trip time of every data item measured? Is it an average, or is every nth item measured? Is it the actual time that is important or just the % of items that are beyond a certain range? Arguably existing QoS ontologies cannot readily answer many of these design questions because these questions have less to do with evaluating QoS and more to do with representing "what is quality?" Therefore, there is an unmet need for Web services ontologies that are designed at a higher level encompassing domain independent concepts, and generally applicable beyond QoS evaluations. The MOQ set of ontologies designed from the premise that quality is "conformance to requirements" aims to fill this need. Comprised of ontologies of requirement, measurement, traceability, and quality management systems, MOQ can be extended to encompass QoS metrics and measurement units or be designed to interoperate with existing QoS ontology. Either way MOQ use promises to ensure that ambiguity in QoS evaluations is minimized.

The use of pilot studies to evaluate the economic justification of technology projects is common in practice. The pilot studies play even greater role in the projects affecting customer interactions with the product/service offerings since perception and/or reaction of customers is captured and analyzed through such studies. Yet, many times the methodology used in these studies lacks rigor and comprehensiveness, and there are scopes for further improvement. The current literature provides limited information on how the pilot studies should be used to decide whether to go ahead with a proposed technology project or not. In this paper we present guidelines for effectively using pilot studies in making such decisions. With the help of a real-life pilot study on deployment of RFID technology in parking operations at a university, we discuss how the proposed guidelines may be implemented to evaluate the cost-effectiveness of the proposed project. In recent times RFID technology is getting increasing attention and many organizations are in the process of deploying this technology. The paper offers a timely and cost-effective evaluation study of a particular application of RFID technology. We found that users' benefits and costs played a crucial role in determining whether the proposed project should go forward or not. Also, we found that intangible benefits and costs to be important. These findings along with our discussions on the general methodology will provide practical guidelines for evaluating viability of technology projects using pilot studies. 258Volume 23Article 15 APPENDIX Questionnaire for the participants of the pilot study Once you have used the parking lot gate at least once, complete the following questionnaire and return it to us (use the provided envelope).

Background Integrating pervasive computing with blockchain’s ability to store privacy-protected mobile health (mHealth) data while providing Health Insurance Portability and Accountability Act (HIPAA) compliance is a challenge. Patients use a multitude of devices, apps, and services to collect and store mHealth data. We present the design of an internet of things (IoT)–based configurable blockchain with different mHealth apps on iOS and Android, which collect the same user’s data. We discuss the advantages of using such a blockchain architecture and demonstrate 2 things: the ease with which users can retain full control of their pervasive mHealth data and the ease with which HIPAA compliance can be accomplished by providers who choose to access user data. Objective The purpose of this paper is to design, evaluate, and test IoT-based mHealth data using wearable devices and an efficient, configurable blockchain, which has been designed and implemented from the first principles to store such data. The purpose of this paper is also to demonstrate the privacy-preserving and HIPAA-compliant nature of pervasive computing-based personalized health care systems that provide users with total control of their own data. Methods This paper followed the methodical design science approach adapted in information systems, wherein we evaluated prior designs, proposed enhancements with a blockchain design pattern published by the same authors, and used the design to support IoT transactions. We prototyped both the blockchain and IoT-based mHealth apps in different devices and tested all use cases that formed the design goals for such a system. Specifically, we validated the design goals for our system using the HIPAA checklist for businesses and proved the compliance of our architecture for mHealth data on pervasive computing devices. Results Blockchain-based personalized health care systems provide several advantages over traditional systems. They provide and support extreme privacy protection, provide the ability to share personalized data and delete data upon request, and support the ability to analyze such data. Conclusions We conclude that blockchains, specifically the consensus, hasher, storer, miner architecture presented in this paper, with configurable modules and software as a service model, provide many advantages for patients using pervasive devices that store mHealth data on the blockchain. Among them is the ability to store, retrieve, and modify ones generated health care data with a single private key across devices. These data are transparent, stored perennially, and provide patients with privacy and pseudoanonymity, in addition to very strong encryption for data access. Firms and device manufacturers would benefit from such an approach wherein they relinquish user data control while giving users the ability to select and offer their own mHealth data on data marketplaces. We show that such an architecture complies with the stringent requirements of HIPAA for patient data access.

No abstract