China
Africa
Explore chapters and articles related to this topic
XML Configuration Access Protocol
Published in Giovanni Bartolomeo, Tatiana Kováčiková, Identification and Management of Distributed Data: NGN, Content-Centric Networks and the Web, 2016
Giovanni Bartolomeo, Tatiana Kováčiková
XCAP operates on information resources represented as XML statements that contain “per-user” information. Examples include, but are not limited to, user profiles, buddy lists in instant messaging applications, and preferences related to presence information such as “show my state as busy.”* To refer to a set of XML statements, it is common to use the expression XML document; however, this does not necessarily imply that they are physically stored as a file in a file system, as the term document might suggest. Native XML databases, as opposed to traditional relational databases, are able to store and operate on collections of XML documents as well. XCAP simply assumes that XML documents are information resources that reside in a network server; however, they can be managed directly by the user through a client. In principle, Hypertext Transfer Protocol (HTTP) methods alone could be used to directly manipulate these resources, simply assuming that a Uniform Resource Indicator (URI) is associated with the target resource. This approach is similar to the first usage that early web developers made of HTTP, where a single change in an element of a Hypertext Markup Language (HTML) page was rendered by reloading the whole page. Obviously this approach had the drawback of the overhead involved in fetching a whole page when it would really be necessary to transmit only differential changes. The need to make differential changes is even more critical when pages are replaced with resources such as XML documents, which contain dynamic data that are frequently modified, and if the protocol is used on a wireless interface. Therefore, it is essential to allow the manipulation of partial pieces of the data, that is, single XML tags and attributes. XCAP solves this problem by introducing a set of conventions to map XML documents and components thereof into HTTP URIs. It also introduces data validation constraints, rules describing how mutually dependent resources should be modified and access authorization policies.
Databases
Published in David Austerberry, Digital Asset Management, 2012
The unstructured XML content can be stored in a conventional file system, just like the rest of the media assets. It is the XML metadata that is the issue. Structured XML with an associated schema can be very easily mapped into a relational database. The choice is between an RDBMS and a “native” XML database.
An Enhanced Entity Model for Converting Relational to Non-Relational Documents in Hospital Management System Based on Cloud Computing
Published in IETE Technical Review, 2022
A. Samydurai, K. Revathi, L. Karthikeyan, B. Vanathi, K. Devi
In general, the relational database (RD) played a significant and leading role in technology-based data storage for the past few years. The relational models are utilized by the relational database where it allows to process and create a relational database ?>management system by means of a structured query language (SQL) [1]. The non-relational databases are introduced to overcome the shortcomings of the relational databases. The non-relational databases are classified under three main categories namely object-oriented databases, XML databases, as well as NoSQL databases [1]. The XML databases are further classified into XML enabled database, Native XML database, as well as Hybrid XML database. Due to numerous changes in demand, data processing has emerged with new processing, data storage, and retrieval mechanisms. Among those mechanisms, not only structured query language databases (NoSQL-DB) are developed in labeling two different types of data stores namely distributed data stores and non-relational data stores. Nevertheless, it becomes difficult to query the traditional relational table for achieving numerous transactions, combining several relational tables, and minimizing the query computational time. Also, an object-relational database [2] is the modified form of the relational model that helps to overcome the query issues. Thus, the object-relational model preserves a relationship among two different types of data approaches such as object-oriented approach and the data-oriented approach, thereby supporting the major methods [3–10].
Requirements of a data storage infrastructure for effective land administration systems: case study of Victoria, Australia
Published in Journal of Spatial Science, 2022
Davood Shojaei, Farshad Badiee, Hamed Olfat, Abbas Rajabifard, Behnam Atazadeh
There are three methods to record ePlan XMLs in a DBMS. The first method is to store XMLs in a traditional relational database and map the XML data model to a DBMS model with a series of tables based on the XML schema (Xu and Cheng 2000, Rys 2001, Tatarinov et al. 2002, Du et al. 2004). Then, queries can be performed using SQL commands. The second method is to store XMLs in an XML Type column in an XML-enabled database (Florescu and Kossmann 1999, Klettke and Meyer 2000, Pardede et al. 2008). The third method is using a Native XML Database (NXDB) where the database can accept XML files as a fundamental (logical) unit of storage (Balmin and Papakonstantinou 2005, Pavlovic-Lazetic 2007, Nečaský 2008). The NXDB method is mainly used for hierarchical data structures. Currently, there are several software products for NXDB such as eXist, Xindice, OrientX, Tamino, and X-Hive/DB (Hu).