An XML database a data persistence software system that allows data to be stored in XML format. These data can then be queried, exported and serialized into the desired format. XML databases are usually associated with document-oriented databases, and are a type of NoSQL database.
Relational databases and full-text search mechanisms that have been the backbone of many applications are not designed to manage XML content effectively. A new class of databases has emerged that is designed specifically to manage XML content. Typically called “XML Native Databases” or just “XML databases,” they incorporate functionality that greatly improves the management, searching, and manipulation of XML to produce the most effective XML data management solution.
The World Wide Web Consortium (W3C), the standards organization that developed XML, has also developed many standards that can be used to access, search, process, and store XML data. XML databases take advantage of these standards to provide efficient and precise access, query, storage, and processing capabilities not found in traditional database technology. The result is that applications using XML databases are more efficient and better suited for managing XML data.
Content Migration is the process of moving information stored on a Content management system (CMS), Digital asset management (DAM), Document management system (DMS), or flat HTML based system to a new system. Flat HTML content can entail HTML files, Active Server Pages (ASP), JavaServer Pages (JSP), PHP, or content stored in some type of HTML/JavaScript based system and can be either static or dynamic content.
Multilingualism is the act of using polyglotism, or using multiple languages, either by an individual speaker or by a community of speakers. Multilingual speakers outnumber monolingual speakers in the world’s population. Multilingualism is becoming a social phenomenon governed by the needs of globalization and cultural openness.
See:
Multilingualism and Information Technology
and:
Multilingual terminology
A web style sheet is a form of separation of presentation and content for web design in which the markup of a webpage contains the page’s semantic content and structure, but does not define its visual layout (style). Instead, the style is defined in an external style sheet file using a style sheet language such as CSS or XSLT. This design approach is identified as a “separation” because it largely supersedes the antecedent methodology in which a page’s markup defined both style and structure.
Also see XSL-FO.
Style sheets predate web publishing and were used in proprietary electronic publishing publishing systems in the early 80s.
Content Management Interoperability Services (CMIS) is an open standard that allows different content management systems to inter-operate over the Internet. Specifically, CMIS defines an abstraction layer for controlling diverse document management systems and repositories using web protocols. CMIS defines a domain model plus web services and Restful AtomPub (RFC5023) bindings that can be used by applications.
For a detailed discussion of CMIS see:
Content Management Interoperability Services (CMIS)
Language localization (from Latin locus and the English term locale, “a place where something happens or is set”) is the second phase of a larger process of product translation and cultural adaptation (for specific countries, regions or groups) to account for differences in distinct markets, a process known as internationalization and localization.
Content Repository API for Java (JCR) is a specification for a Java platform application programming interface (API) to access content repositories in a uniform manner. The content repositories are used in content management systems to keep the content data and also the metadata used in content management systems (CMS) such as versioning metadata. The specification was developed under the Java Community Process as JSR-170 (Version 1). and as JSR-283 (version 2).
Customer experience (CX) emerged from work in the 1990s on “experience management” which was not limited to “customers” but included employees, suppliers, and other stakeholders. Customers became the primary focus in the 2000s and was fueled by the growth of digital marketing channels. Technology suppliers and analysts serving marketing organizations began targeting CX in their products and services with features and their own marketing and branding efforts. In particular many “web content management (WCM) systems” became “customer experience management” (CXM), web experience management” or “web engagement management” systems (both using the WEM acronym). Most of these same products and services were also applicable and in use for managing other stakeholder experiences, and became “digital experience” (DX) systems or platforms (DXPs), with CX being one component.
