No abstract

The enormous increase of the amount of information available on the web creates the need for systems like Question Answering to bridge the gap between general end users and the web with its different data representations. A considerable portion of the available data on the web is written in Arabic for and by Arabic users. This paper provides a review of the Arabic Question Answering Systems building processes and the challenges met by the researchers in this topic due to the Arabic language special characteristics. A general architecture is represented for the Question Answering task on both structured and unstructured data. Then, an overview of the work done in Arabic Question Answering Systems is presented. Finally, a number of tools and linguistic resources are recommended for researchers to develop Arabic question answering systems. 13 Arabic Wikipedia http://ar.wikipedia.org/wiki Arabic WordNet http://globalwordnet.org/arabicwordnet/awnbrowser/#BrowserDownload. DBpedia http://dbpedia.org/About Linguistic corpora: for training and testing questions Arabic Stopwords

No abstract

Due to the proliferation of big data with large volume, velocity, complexity, and distribution among remote servers, it became obvious that traditional relational databases are unsuitable for meeting the requirements of such data. This led to the emergence of a novel technology among organizations and business enterprises; NoSQL datastores. Today such datastores have become popular alternatives to traditional relational databases, since their schema-less data models can manipulate and handle a huge amount of structured, semistructured and unstructured data, with high speed and immense distribution. Those data stores are of four basic types, and numerous instances have been developed under each type. This implies the need to understand the differences among them and how to select the most suitable one for any given data. Unfortunately, research efforts in the literature either consider differences from a theoretical point of view (without real use cases), or address performance issues such as speed and storage, which is insufficient to give researchers deep insight into the mapping of a given data structure to a given NoSQL datastore type. Hence, this paper provides a qualitative comparison among three popular datastores of different types (Redis, Neo4j, and MongoDB) using a real use case of each type, translated to the others. It thus highlights the inherent differences among them, and hence what data structures each of them suits most.

No abstract