TL;DR: The application of Xbase is presented by means of a domain model language which serves as a tutorial example and by the implementation of the programming language Xtend, a functional and object-oriented general purpose language for the Java Virtual Machine (JVM).
Abstract: Xtext is an open-source framework for implementing external, textual domain-specific languages (DSLs). So far, most DSLs implemented with Xtext and similar tools focus on structural aspects such as service specifications and entities. Because behavioral aspects are significantly more complicated to implement, they are often delegated to general-purpose programming languages. This approach introduces complex integration patterns and the DSL's high level of abstraction is compromised.We present Xbase as part of Xtext, an expression language that can be reused via language inheritance in any DSL implementation based on Xtext. Xbase expressions provide both control structures and program expressions in a uniform way. Xbase is statically typed and tightly integrated with the Java type system. Languages extending Xbase inherit the syntax of a Java-like expression language as well as language infrastructure components, including a parser, an unparser, a linker, a compiler and an interpreter. Furthermore, the framework provides integration into the Eclipse IDE including debug and refactoring support.The application of Xbase is presented by means of a domain model language which serves as a tutorial example and by the implementation of the programming language Xtend. Xtend is a functional and object-oriented general purpose language for the Java Virtual Machine (JVM). It is built on top of Xbase which is the reusable expression language that is the foundation of Xtend.
TL;DR: Xbase (XML-based document BASE) is a prototype system aiming at addressing the problem of remembering name of files created sometime ago and digging them out from a disk with dozen gigabytes of data in hundred thousands of files.
Abstract: With the rapid development of the Internet and the World Wide Web (WWW), very large amount of information is available and ready for downloading, most of which are free of charge. At the same time, hard disks with large capacity are available at affordable prices. Most of us nowadays often dump a large number of various types of documents into our computers without much thinking. On the other hand, file systems have not changed too much during the past decades. Most of them organize files in directories that form a tree structure, and a file is identified by its name and pathname in the directory tree. Remembering name of files created sometime ago and digging them out from a disk with dozen gigabytes of data in hundred thousands of files becomes never an easy task. Tools available for helping such a search are still far from satisfactory.Xbase (XML-based document BASE) is a prototype system aiming at addressing the above problem. By XML-based, we meant that XML is used to define the metadata. The current version of XBase stores text-based files, including semi-structured data such as XML, HTML, plain text documents (e.g., tex files, computer programs) and those files that can be converted into text (e.g., postscript files, PDF files). In XBase, file name is optional. Users can just load a file into XBase without giving a name and the directory where it should be stored. XBase will automatically associate it with attributes such as the time when the file was saved, its source, its size and type, and etc., To retrieve those files, XBase provides three access methods, explorative browsing, querying using query languages, and keyword based search.
TL;DR: The system architecture and internal designs of Xbase as well as how the indexing is mapped to RDBMS and Hadoop are described, which discusses why Hbase is selected over other candidates, such as Hbase, Google's Bigtable, and Hive.
Abstract: XML is a more desirable format for modeling and storing clinical data in EMR (Electronic medical record) applications for its extendibility; however, existing EMR systems either are built on top of RDBMS or file systems or lack of support for complex and large scale healthcare applications, such as treatment effectiveness analysis and procedure optimization. SAP Technology Lab, China is developing a clouds-enabled information appliance, Xbase, built on top of Hadoop, which is the first XML-based information appliance designed specifically for large scale and complex healthcare applications. XML presents a different set of challenges for query processing, indexing, parallelism, and distributed computing using existing Hadoop's APIs as well as its HDFS storage infrastructure and MapReduce framework. In this paper, we describe system architecture and internal designs of Xbase as well as how the indexing is mapped to RDBMS and Hadoop. We also discuss why we select Hadoop over other candidates, such as Hbase, Google's Bigtable, and Hive.
TL;DR: In this paper, a ground characterisation exercise was conducted in order to identify sites suitable for a blast furnace at the Redcar steelworks in northeast England, and the purpose of this exercise, conducted some 20 years after the investigations were carried out and a decade after the steelworks had been constructed, was to develop techniques for managing spatial data using Geographical Information Systems (GIS) and geostatistics.
TL;DR: A client side, Web server, or clustered server Xbase data access and transfer system allows native Xbase style application programs to transparently use SQL or other RDBMS style systems as their underlying data store as mentioned in this paper.
Abstract: A client side, Web server, or clustered server Xbase style data access and transfer system allows native Xbase style application programs to transparently use SQL or other RDBMS style systems as their underlying data store. The system includes a non-flat file client/server storage mechanism as the target data storage system, a native Xbase style application program, script, or Web based application requiring access to a non-Xbase style backend database, and network communications system connecting the two, such as an IP based Ethernet, Web processing system, or other wireless or wired packet switching medium. The native Xbase system connects to the back end application to read and write data as if it were utilizing the native local Xbase desktop database file(s). This allows non-client/server database applications to be easily ported to utilize improved back end servers instead of simple file sharing.