# XML - Managing Data Exchange/acord

+--------------------------------------------------------------------+
| **Learning objectives**                                            |
|                                                                    |
| -   get to know insurance industry\'s standardization organization |
| -   understand how XML is used in the insurance industry           |
| -   realize why industry standards are so important                |
| -   comprehend the main aspects of the ACORD XML standard          |
| -   learn about the advantages of using ACORD XML                  |
+--------------------------------------------------------------------+
|                                                                    |
+--------------------------------------------------------------------+

## Introduction

ACORD is the **A**ssociation for **C**ooperative
**O**perations **R**esearch and **D**evelopment.

### Organization

## ACORD

ACORD was founded in 1970 as a standards-setting organization for the
insurance industry. As a global non-profit organization, they develop
and provide cost saving digital standards for data interchange to reduce
paperwork. The goals of their standards are to minimize redundant work
and maximize data accuracy; making life far easier for all companies,
agents and policyholders \[1\].

### Work

The standards are the result of the work of all members, synchronized by
ACORD working groups. Finally the ACORD Steering Committees will decide,
which results would end up as public standards, in coordination with
other standardization organizations and governments.

One of the recent standards incorporates the use of XML as a frame for
flexible data transmission and interchange. In 2001 XML for P&C and
Surety Version 1.0 was approved, in 2002 Version 1.2 was approved
\[1\].

### XML

XML provides an open standard, with easy to be
made connectivity between
ERP
systems, managment systems, web services, web applications and other
related systems. It can be used in business-to-business,
customer-to-business and business-to-customer applications.

## Benefits of ACORD XML

Usually the benefits of XML are across all industries and domains of
similar type, but that does not apply to the insurance industry. There
you can find unique benefits like \[6\]:

### Partner to Partner Integration

Common data elements and definitions are necessary to deal with external
business partners in this industry. So you need a common language to
share data with all actors from the value chain, e.g. reinsurers or
intermediaries. By involving this actors in the process of development
ACORD designed this common language and data standards.

### Internal Integration

The Insurance industry requires the separation of communication systems
to complete a business process. Furthermore a claim adjuster, who wants
to verify coverage or to ensure that the claim\'s code is correct, needs
a system that offers accurate transfer of the claim or policy number.
ACORD XML standards are essential to transfer such items from system to
system.

### Electronic Data Sharing

Moreover the data should have a high quality and transparency. Without
that it is not possible for carriers to get exposure information in
disparate and incompatible formats in order to identify aggregation of
exposure across customers and lines of business in an effective way.
Reinsurers need high visibility into cedent risk portfolios for
extensive exposure analyses. ACORD data standards support a format that
captures and analyzes information and data in multiple formats across
partners.

### Web Services

By reason of Web Services are required for real time integration
througout the transaction processing cycle, ACORD standards realise
processes like the integration of back-end systems with an agent portal.

### Document Repository Standards

A single repository for all risk related information is in general not
possible. Due to the fact that consistency across data repositories is
very important, ACORD XML standards were established to allow trading
partners to share structured and unstructured documents and data also in
a variety of third party systems. Therefore Document Repository
Interface Standards exist to guarantee access to free format
documentation for improving decisions.

### Improved Cash Flow

By using ACORD XML standards transaction processing is accelerated.
Consequently there is a faster access to money or other types of
payments.

## Standards

Following standards allows different companies along the value chain of
a market to exchange data with less \"frictional losses\" that are
usually generated by the usage of incompatible data formats. A standard
serves as a common communication method to increase efficiency - a
lowest common denominator. It is a set of rules and guidelines that
provide a common framework for
communication.1 The set of ACORD
standards consists of subsets for the 3 main segments of insurance
industry. These are:

-   Life, Annuity and Health
-   Property and Casualty
-   Reinsurance and Large Commercial

By implementing and following ACORD\'s standard definitions, member
companies can achieve \...

-   competitive advantages
-   end-to-end process support
-   easier access to markets
-   lower costs, which lead to more profit
-   better market acceptance
-   higher performance and enhanced credibility.

As seen in the previous chapters (esp. in \"Introduction to
XML\")
using XML as a means of data exchange is a suitable base for a standard
like ACORD. It\'s flexible enough to be tailored for the usage within
different insurance segments but it also offers methods to ensure data
quality and the stability of the standard.

## Technical Standardization

The ACORD standard describes different concepts that can be implemented
by a member. The access to the standard\'s descriptions is partly free,
partly limited to ACORD members. It can be found here: ACORD Standard
Descriptions.

### XML structures

To ensure the correct form of the transferred data, ACORD provides XML
schemas and DTDs for its members. Companies implementing the standard
can validate their data against those definitions. The ACORD XML
standard is strongly based upon the United Nations
EDIFACT standard and expands the standard XML
data types with the financial data types used by the **I**nteractive
**F**inancial
**E**xchange (IFX).

ACORD\'s data types consist partly of those definitions but also expand
them with own data types. The data types are used as building blocks for
larger entities within the specification:

**Exhibit 1: XML entities used within the ACORD XML standard**

  Entity      Description
  ----------- ------------------------------------------------------------------
  Element     a base element, based on one or more of the described data types
  Aggregate   a collection of corresponding elements, entities or aggregates
  Entity      aggregate with the same structure
  Message     an aggregate that is used as one entity for communication
  Service     a collection of corresponding messages
  Document    a collection of messages that are sent together at the same time

A detailed description of the technical XML related aspects of the ACORD
standard can be obtained for Property &
Casualty and for
Life, Annuity & Health.

### XML messages

The before mentioned data types and structures are used to define
messages that can be interchanged between companies implementing the
ACORD standard. Different message types are defined within the data
model for each insurance segment. The following example shows the
messages used within the Reinsurance & Large Commercial segment:

**Exhibit 2: ACORD XML message types for RLC business**

  Message           Description
  ----------------- -----------------------------------------------------------------------------------------------
  Placing           message for placing obligatory or facultative business
  Bordereau         message between primary insurance and reinsurance company with information about signed risks
  ClaimMovement     message for a claim notification
  TechAccount       message to exchange accounting data for a treaty
  Settlement        message to exchange settlements
  Acknowledgement   message to confirm other messages or to request information

### ACORD message service

ACORD messages can be exchanged between implementing companies as plain
XML files. Additionally the ACORD standard defines a specialized message
exchange service. It is based on the **W**eb **S**ervice
**D**escription
**L**anguage (WSDL)
to implement the concepts of web services. The messages are send using
the **S**imple **O**bject **A**ccess
**P**rotocol (SOAP) standard. Following this
protocol a message consists of an envelope with the XML root element, a
header and a body which both are direct child elements of the envelope.
The SOAP envelope only contains structural information, not the message
itself. The actual SOAP messages are send as attachments with the
message and are referenced within the message body.

Therefore it\'s possible to enrich the ACORD messages with additional
information in PDF or DOC format.

**Exhibit 3: ACORD message service structure**

![](ACORD_Messages.jpg "ACORD_Messages.jpg")

### Examples

To provide an impression of the complexity of ACORD\'s XML standard
definitions, following a small excerpt (only some lines of more than
5.000 per XML schema file / DTD) of the Reinsurance & Large Commercial
segment\'s XML schema and DTD files are presented:

**Exhibit 4: Excerpt from the RLC XML schema**

    <nowiki>
    <?xml version="1.0" encoding="UTF-8"?>
    <!--

    This is the ACORD Reinsurance and Large Commercial Business Message specification's

    **** version 2007-1 Schema ****

    Generated: May 10, 2007

    COPYRIGHT NOTICE:
    (c) 2001-2007 ACORD.  All Rights Reserved.

    IMPORTANT NOTE:  Please be advised that this document and your use of it is governed, and
    you are bound, by the Terms and Conditions of Use accessible at [http://legal.acord.org/terms.pdf].

    -->
    <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns="http://www.ACORD.org/standards/Jv-Ins-Reinsurance/2007-1"
    xmlns:ac="http://www.ACORD.org/Standards/AcordMsgSvc/1" targetNamespace="http://www.ACORD.org/standards/Jv-Ins-Reinsurance/2007-1"
    elementFormDefault="qualified" attributeFormDefault="unqualified" version="2007-1">
            <xs:import namespace="http://www.ACORD.org/Standards/AcordMsgSvc/1" schemaLocation="Acord-Repository_v-1-3-0-RLC-Slice.xsd"/>
        <!--******************-->
        <!--2007-1 MRs applied-->
        <!--******************-->
        <!--MR1: Add CedentBuildReference, BrokerBuildReference, ReinsurerBuildReference, InsurerBuildReference,
             ServiceProviderBuildReference and PlacingExchangeBuildReference elements to Contract -->
        <!--MR10: Change DeductibleNumberOfLines, CoverageNumberOfLines, ReinsurerShareNumberOfLines, InsurerShareNumberOfLines,
             ReinsurerWrittenNumberOfLines, InsurerWrittenNumberOfLines to become decimal numbers instead of integers-->
        <!--MR11: Add ExpenseIndicator element to IndividualClaimAmtItem-->
        <!--MR20: Add ProcessingInstructions/SettlementChannel to ContractMarket-->
        <!---->
        <!--******************************************************-->
        <!--Start of Jv-Ins-Reinsurance base data types -->
        <!--******************************************************-->
        <!--Character is equated to the xs:string Schema base type-->
        <!--URL is equated to the xs:anyURI Schema base type-->
        <!--Attributes are validated against the xs:NMTOKEN Schema base type-->
        <xs:simpleType name="FlexibleDate_Type">
            <xs:annotation>
                <xs:documentation>JAG type</xs:documentation>
            </xs:annotation>
            <xs:union memberTypes="xs:date xs:gYearMonth xs:gYear"/>
        </xs:simpleType>
        <xs:simpleType name="FlexibleDate1_Type">
            <xs:annotation>
                <xs:documentation>JAG type restriction 1 : Year only not admitted - Default in RLC</xs:documentation>
            </xs:annotation>
            <xs:union memberTypes="xs:date xs:gYearMonth"/>
        </xs:simpleType>
        <xs:simpleType name="FlexibleDateTime_Type">
            <xs:annotation>
                <xs:documentation>JAG type</xs:documentation>
            </xs:annotation>
            <xs:union memberTypes="xs:date xs:dateTime xs:gYearMonth xs:gYear"/>
        </xs:simpleType>
        <xs:simpleType name="FlexibleDateTime1_Type">
            <xs:annotation>
                <xs:documentation>JAG type restriction 1 : Year only not admitted</xs:documentation>
            </xs:annotation>
            <xs:union memberTypes="xs:date xs:dateTime xs:gYearMonth"/>
        </xs:simpleType>
        <xs:simpleType name="FlexibleDateTime2_Type">
            <xs:annotation>
                <xs:documentation>JAG type restriction 2 : Year only and YearMonth only not admitted</xs:documentation>
            </xs:annotation>
            <xs:union memberTypes="xs:date xs:dateTime"/>
        </xs:simpleType>
        <xs:complexType name="StartDateType">
            <xs:simpleContent>
                <xs:extension base="FlexibleDate1_Type">
                    <xs:attribute name="DateIndicator" type="xs:NMTOKEN"/>
                </xs:extension>
            </xs:simpleContent>
        </xs:complexType>
        <xs:complexType name="EndDateType">
            <xs:simpleContent>
                <xs:extension base="FlexibleDate1_Type">
                    <xs:attribute name="DateIndicator" type="xs:NMTOKEN"/>
                </xs:extension>
            </xs:simpleContent>
        </xs:complexType>
        <xs:complexType name="StartDateTimeType">
            <xs:simpleContent>
                <xs:extension base="FlexibleDateTime2_Type">
                    <xs:attribute name="DateIndicator" type="xs:NMTOKEN"/>
                </xs:extension>
            </xs:simpleContent>
        </xs:complexType>
        <xs:complexType name="EndDateTimeType">
            <xs:simpleContent>
                <xs:extension base="FlexibleDateTime2_Type">
                    <xs:attribute name="DateIndicator" type="xs:NMTOKEN"/>
                </xs:extension>
            </xs:simpleContent>
        </xs:complexType>

    .
    .
    .

        <xs:element name="WrittenDateTime" type="FlexibleDateTime2_Type"/>
        <xs:element name="XplClauseIndicator" type="XplClauseIndicatorType"/>
        <!--**************************************************************-->
        <!--End of Jv-Ins-Reinsurance elements-->
        <!--**************************************************************-->
        <!--The Message aggregates included in this schema are generic and contain the child elements allowed in each message.
             Where a child element is itself an aggregate, this does NOT mean that ALL elements of that child aggregate are
             available for use in a particular message.

             The ACORD RLC Data dictionary and Implementation guides give details of the restrictions placed on the use of all
             elements and further information can also be found in the individual templates for each message. These templates are
             XML files listing all tags available for each message and can be viewed with any XML editor or viewer.

             The respective message aggregates are as shown in the section "Jv-Ins-Reinsurance root and transaction elements"
             table below.  The templates themselves can be downloaded from the ACORD web site www.ACORD.org along with the standard
             documentation.-->
        <!--
    *****************************************************************
    *  Jv-Ins-Reinsurance root and Message elements   *
    *****************************************************************
    -->
        <xs:element name="Jv-Ins-Reinsurance" type="Jv-Ins-ReinsuranceType"/>
        <xs:element name="Acknowledgement" type="AcknowledgementType"/>
        <xs:element name="Bordereau" type="BordereauType"/>
        <xs:element name="ClaimMovement" type="ClaimMovementType"/>
        <xs:element name="Codes" type="CodesType"/>
        <xs:element name="Placing" type="PlacingType"/>
        <xs:element name="Settlement" type="SettlementType"/>
        <xs:element name="TechAccount" type="TechAccountType"/>
        <!--End of Jv-Ins-Reinsurance root and transaction elements-->
    </xs:schema>
    </nowiki>

**Exhibit 5: Excerpt from the RLC DTD**

    <nowiki>
    <?xml version="1.0" encoding="UTF-8"?>
    <!-- edited with XMLSpy v2006 rel. 3 sp2 (http://www.altova.com) by Serge Cayron (ACORD Corp.) -->
    <!--
    This is the ACORD Reinsurance and Large Commercial Business Message specification's

    **** version 2007-1 DTD ****

    Generated: May 10, 2007

    COPYRIGHT NOTICE:
    (c) 2001-2007 ACORD.  All Rights Reserved.

    IMPORTANT NOTE:  Please be advised that this document and your use of it is governed, and you are bound, by the Terms
    and Conditions of Use accessible at [http://legal.acord.org/terms.pdf].

    *******************************************************************************************
    *                                Formal Public Identifier
    *
    *      "-//ACORD//DTD JV Ins-Reinsurance Version 2007-1//EN"
    ********************************************************************************************

    IMPORTANT NOTE: From the 2005-2 release, the RLC XML Schema is able to validate messages that include custom extensions,
    using a standard method. The DTD file does NOT support the same functionality.  The user of a DTD should be aware that
    it will not be possible to use the DTD to validate messages that use the standard extension method. -->
    <!--******************-->
    <!--2007-1 MRs applied-->
    <!--******************-->
    <!--MR1: Add CedentBuildReference, BrokerBuildReference, ReinsurerBuildReference, InsurerBuildReference,
     ServiceProviderBuildReference and PlacingExchangeBuildReference elements to Contract -->
    <!--MR10: Change DeductibleNumberOfLines, CoverageNumberOfLines, ReinsurerShareNumberOfLines, InsurerShareNumberOfLines,
     ReinsurerWrittenNumberOfLines, InsurerWrittenNumberOfLines to become decimal numbers instead of integers-->
    <!--MR11: Add ExpenseIndicator element to IndividualClaimAmtItem-->
    <!--MR20: Add ProcessingInstructions/SettlementChannel to ContractMarket-->
    <!--
    ************************************************
    *  Common Entities in alphabetical order *
    ************************************************
     -->
    <!ENTITY % PARTY "Party, Contact?, Address?">
    <!ENTITY % PARTYXT "((Party, FullNameAndAddress?) | FullNameAndAddress), Contact?, Address?, OperationsDescription?">
    <!ENTITY % PERILS "Peril+">
    <!ENTITY % PERIOD "StartDate?, EndDate?, TimeDuration?">
    <!ENTITY % REPORTING "Description?, ReportDue?, ProvisionFrequency?, AnnualAsOfDate?">
    <!--
    *****************************
    *  Data typing elements  *
    *****************************
     -->
    <!-- Currency amount -->
    <!ELEMENT Amt (#PCDATA)>
    <!ATTLIST Amt
        Ccy NMTOKEN #REQUIRED
        Share (cedent_share | contract_ceded | hundred_percent | receiver_share | reinsurer_share) #IMPLIED
        CcyIndic (reference_currency | target_currency | original_currency) #IMPLIED
    >
    <!-- Integer -->
    <!ELEMENT Count (#PCDATA)>
    <!ELEMENT StartDate (#PCDATA)>
    <!ATTLIST StartDate
        DateIndicator NMTOKEN #IMPLIED
    >
    <!ELEMENT EndDate (#PCDATA)>
    <!ATTLIST EndDate
        DateIndicator NMTOKEN #IMPLIED
    >
    <!-- Date and time -->
    <!ELEMENT StartDateTime (#PCDATA)>
    <!ATTLIST StartDateTime
        DateIndicator NMTOKEN #IMPLIED
    >
    <!ELEMENT EndDateTime (#PCDATA)>
    <!ATTLIST EndDateTime
        DateIndicator NMTOKEN #IMPLIED
    >
    <!-- Decimal -->
    <!ELEMENT Dec (#PCDATA)>
    <!-- Period identification - Integer-->
    <!ELEMENT PeriodNbr (#PCDATA)>
    <!ATTLIST PeriodNbr
        PeriodIndicator NMTOKEN #REQUIRED
    >
    <!-- Rate -->
    <!ELEMENT Rate (#PCDATA)>
    <!ATTLIST Rate
        RateUnit NMTOKEN #REQUIRED
    >
    <!-- Time duration -->
    <!ATTLIST TimeDuration
        PeriodType NMTOKEN #IMPLIED
        PeriodIndicator NMTOKEN #IMPLIED
    >

    .
    .
    .

    <!ATTLIST TimeDuration
        PeriodType NMTOKEN #IMPLIED
        PeriodIndicator NMTOKEN #IMPLIED
    >
    <!ELEMENT TimeRelation (#PCDATA)>
    <!ELEMENT TimeZone (#PCDATA)>
    <!ELEMENT TotalLossIndicator (#PCDATA)>
    <!ELEMENT Townclass (#PCDATA)>
    <!ATTLIST Townclass
        Agency NMTOKEN #IMPLIED
    >
    <!ELEMENT TransactionReasonDescription (#PCDATA)>
    <!ELEMENT TransactionResponseReason (#PCDATA)>
    <!ELEMENT TreatyFac (#PCDATA)>
    <!ELEMENT URL (#PCDATA)>
    <!ELEMENT UUId (#PCDATA)>
    <!ELEMENT UnderwritingManager (%PARTY;)>
    <!ELEMENT UnderwritingManagerRiskReference (#PCDATA)>
    <!ELEMENT UnderwritingYear (#PCDATA)>
    <!ELEMENT UnearnedPremiumCalculationPeriod (%PERIOD;)>
    <!ELEMENT UnearnedPremiumReserveProfitCommissionPercentage (Rate)>
    <!ELEMENT USARiskClassification ((RiskClass, RiskClassDescription?) | RiskClassDescription)>
    <!ELEMENT UserId (#PCDATA)>
    <!ELEMENT ValueAddedTaxRating (#PCDATA)>
    <!ELEMENT ValueDate (#PCDATA)>
    <!ELEMENT VesselName (#PCDATA)>
    <!ELEMENT VesselOrConveyanceDescription (#PCDATA)>
    <!ELEMENT Voyage (DepartureDateTime?, LoadingOrEmbarkationDate?, DepartureLocation?, DestinationLocation?)>
    <!ELEMENT WebApplication (URL?, UserId?)>
    <!ELEMENT WebSiteURL (#PCDATA)>
    <!ELEMENT WholesaleBrokerageAmount (Amt+)>
    <!ELEMENT WholesaleBrokeragePercentage (Rate)>
    <!ELEMENT WithdrawalDate (#PCDATA)>
    <!ELEMENT WithdrawalPercentage (Rate)>
    <!ELEMENT WorkersCompensationState (Subentity)>
    <!ELEMENT WorkersCompensationStateDescription (#PCDATA)>
    <!ELEMENT WrittenDateTime (#PCDATA)>
    <!ELEMENT XplClauseIndicator (#PCDATA)>
    </nowiki>

### Certification

To ensure data quality and member\'s compliance with the proposed
standards ACORD offers a special certification program. ACORD members
can send their XML messages to ACORD. There the messages are validated
in 2 steps:

1.  Automatic Validation against the standard\'s XML schema and DTD
    files
2.  Validation of the sent data by a human for plausibility which goes
    beyond the automatical, technical consistency check

## Members

World\'s largest insurance companies and insurance related businesses
are ACORD members: \"Over 70% of the top 10 and 60% of the top 25 Life &
Annuity carriers; Over 75% of the top 50 Property & Casualty carriers;
and 70% of the top 10 Reinsurers, as well as the Top 5 reinsurance
brokers representing 80% of the top 20\'s gross
revenue.\"2 The following list
shows just some of them:

-   Allianz Insurance
-   Allstate
-   Hannover Re
-   AXA
-   Benfield
-   ING Group
-   MetLife
-   Munich Re
-   Zurich Insurance Group

For a complete list have a look at the ACORD
Memberlist.

## References

Sources:

-   \[1\] ACORD Website
-   \[2\] Market Reform Group
-   \[3\] IFX Forum
-   \[4\] University of
    Leipzig
-   \[5\] SAP
    INFO
-   \[6\] ACORD White
    Paper

## Summary

+----------------------------------------------------------------------+
| In the previous chapter you have learned about the insurance         |
| industry\'s standard for electronical data exchange. It\'s           |
| maintained by a nonprofit organization called ACORD and defines data |
| models for the main insurance segments. The main concepts of the     |
| ACORD XML standard are:                                              |
|                                                                      |
| -   a set of XML schemas and DTDs to ensure the content, structure   |
|     and \"quality\" of the sent XML streams                          |
| -   a set of XML messages for different business cases               |
| -   the ACORD message service for exchanging enriched XML data based |
|     on WSDL and SOAP                                                 |
+----------------------------------------------------------------------+
|                                                                      |
+----------------------------------------------------------------------+


# XML - Managing Data Exchange/Glossary

```{=html}
<h2 style="background-color:#CEE0F2; border-bottom:0px; border: 1px solid #A3B1BF; text-align:center; padding-top:4px;">
```
Glossary

```{=html}
</h2>
```
```{=html}
<div align="center">
```
```{=html}
</div>
```
## 0--9

`<span id=1RR style="font-weight: bold">`{=html}.NET`</span>`{=html}
:   Microsoft **.NET** Framework
:   Microsoft .NET Framework is a software component that is part of
    several Microsoft Windows operating systems. It has a large library
    of pre-coded solutions to common programming problems and manages
    the execution of programs written specifically for the framework.

## A

`<span id=3RR style="font-weight: bold">`{=html}ACORD`</span>`{=html}
:   **A**ssociation for **C**ooperative **O**perations **R**esearch and
    **D**evelopment
:   ACORD is the insurance industry\'s nonprofit standards developer, a
    resource for information about object technology, EDI, XML and
    electronic commerce in the United States and abroad.
:   Among other things, ACORD governs an XML based data model to provide
    an easy way to exchange data between insurance companies, insurance
    brokers, other insurance related firms and governments.

```{=html}
<!-- -->
```

`<span id=3RR style="font-weight: bold">`{=html}AJAX`</span>`{=html}
:   **A**synchronous **J**ava**S**cript **a**nd **X**ML
:   AJAX is a group of inter-related web development techniques used for
    creating interactive web applications.
:   A primary characteristic is the increased responsiveness and
    interactivity of web pages achieved by exchanging small amounts of
    data with the server \"behind the scenes\" so that entire web pages
    do not have to be reloaded each time there is a need to get data
    from the server. This is intended to increase the web page\'s
    interactivity, speed, functionality and usability.

```{=html}
<!-- -->
```

`<span id=3RR style="font-weight: bold">`{=html}ANSI`</span>`{=html}
:   **A**merican **N**ational **S**tandards **I**nstitute
:   ANSI is a private non-profit organization that oversees the
    development of voluntary consensus standards for products, services,
    processes, systems, and personnel in the United States. The
    organization also coordinates U.S. standards with international
    standards so that American products can be used worldwide. For
    example, standards make sure that people who own cameras can find
    the film they need for them anywhere around the globe.

```{=html}
<!-- -->
```

`<span id=3RR style="font-weight: bold">`{=html}API`</span>`{=html}
:   **A**pplication **P**rogramming **I**nterface
:   API is a source code interface that an operating system, library or
    service provides to support requests made by computer programs.

```{=html}
<!-- -->
```

`<span id=3RR style="font-weight: bold">`{=html}ASCII`</span>`{=html}
:   **A**merican **S**tandard **C**ode **I**nformation**I**nterchange
:   ASCII is a character encoding based on the English alphabet. ASCII
    codes represent text in computers, communications equipment, and
    other devices that work with text. Most modern character encodings
    --- which support many more characters than did the original ---
    have a historical basis in ASCII.

```{=html}
<!-- -->
```

`<span id=3RR style="font-weight: bold">`{=html}ASP`</span>`{=html}
:   **A**nalog **S**ignal **P**rocessing
:   ASP means processing electronic signals that represent continuous
    variables by use of analog circuitry.

```{=html}
<!-- -->
```

`<span id=3RR style="font-weight: bold">`{=html}ASX`</span>`{=html}
:   **A**dvanced **S**tream Redirector
:   ASX format is a type of XML metafile designed to store a list of
    Windows Media files to play during a multimedia presentation.
:   It is used frequently on streaming video servers where multiple ASF
    files are to be played in succession. Both RTSP and MMS streaming
    protocols are supported, as well as HTTP.

## B

`<span id=3RR style="font-weight: bold">`{=html}BHTML`</span>`{=html}
:   **B**roadcast **H**yper**T**ext **M**arkup **L**anguage
:   BHTML extends HTML by adding attributes for standardizing multimedia
    object descriptions within HTML OBJECT elements, using the SMIL
    SWITCH option and introducing an EVENT element to manage the actions
    to be taken when certain conditions are encountered.

## C

`<span id=3RR style="font-weight: bold">`{=html}CGI`</span>`{=html}
:   **C**ommon **G**ateway **I**nterface
:   CGI is a standard protocol for interfacing external application
    software with an information server, commonly a web server. The task
    of such an information server is to respond to requests (in the case
    of web servers, requests from client web browsers) by returning
    output. Each time a request is received, the server analyzes what
    the request asks for, and returns the appropriate output.

```{=html}
<!-- -->
```

`<span id=3RR style="font-weight: bold">`{=html}CML`</span>`{=html}
:   **C**hemical **M**arkup **L**anguage
:   CML is a new approach to managing molecular information using tools
    such as XML and Java. It was the first domain specific
    implementation based strictly on XML, the most robust and widely
    used system for precise information management in many areas.

```{=html}
<!-- -->
```

`<span id=3RR style="font-weight: bold">`{=html}CORBA`</span>`{=html}
:   **C**ommon **O**bject **R**equest **B**roker **A**rchitecture
:   CORBA is a standard defined by the Object Management Group (OMG)
    that enables software components written in multiple computer
    languages and running on multiple computers to work together.

```{=html}
<!-- -->
```

`<span id=3RR style="font-weight: bold">`{=html}../CSS/`</span>`{=html}
:   **C**ascading **S**tyle **S**heets
:   CSS is a language that describes the presentation form of a
    structured document. An XML or an HTML based document does not have
    a set style, but it consists of structured text without style
    information. How the document will look when printed on paper and
    viewed in a browser or maybe a cellphone is determined by a style
    sheet.

## D

`<span id=3RR style="font-weight: bold">`{=html}DAD`</span>`{=html}
:   **D**ata **A**ccess **D**efinition
:   A data access definition (DAD) file is used for both XML Column and
    XML Collection approaches to define the \"mapping\" between the
    database tables and the structure of the XML document.

```{=html}
<!-- -->
```

`<span id=3RR style="font-weight: bold">`{=html}DB2`</span>`{=html}
:   DB2 is one of IBM\'s families of relational database management
    system (or, as IBM now calls it, data server) software products
    within IBM\'s broader Information Management Software line.

```{=html}
<!-- -->
```

`<span id=3RR style="font-weight: bold">`{=html}DCMI`</span>`{=html}
:   **D**ublin **C**ore **M**etadata **I**nitiative
:   The Dublin Core Metadata Initiative is an open organization engaged
    in the development of interoperable online metadata standards that
    support a broad range of purposes and business models. DCMI\'s
    activities include work on architecture and modeling, discussions
    and collaborative work in DCMI Communities and DCMI Task Groups,
    annual conferences and workshops, standards liaison, and educational
    efforts to promote widespread acceptance of metadata standards and
    practices.

```{=html}
<!-- -->
```

`<span id=3RR style="font-weight: bold">`{=html}DCOM`</span>`{=html}
:   **D**istributed **C**omponent **O**bject **M**odel
:   DCOM is a proprietary Microsoft technology for communication among
    software components distributed across networked computers. DCOM,
    which originally was called \"Network OLE\", extends Microsoft\'s
    COM, and provides the communication substrate under Microsoft\'s
    COM+ application server infrastructure. It has been deprecated in
    favor of Microsoft .NET.

```{=html}
<!-- -->
```

`<span id=3RR style="font-weight: bold">`{=html}DHTML`</span>`{=html}
:   **D**ynamic **H**yper**T**ext **M**arkup **L**anguage
:   DHTML is a collection of technologies used together to create
    interactive and animated web sites by using a combination of a
    static markup language (such as HTML), a client-side scripting
    language (such as JavaScript), a presentation definition language
    (Cascading Style Sheets, CSS), and the Document Object Model.

```{=html}
<!-- -->
```

`<span id=3RR style="font-weight: bold">`{=html}DOM`</span>`{=html}
:   **D**ocument **O**bject **M**odel
:   DOM is a platform- and language-independent standard object model
    for representing HTML or XML and related formats.

```{=html}
<!-- -->
```

`<span id=3RR style="font-weight: bold">`{=html}DSSSL`</span>`{=html}
:   **D**ocument **S**tyle **S**emantics and **S**pecification
    **L**anguage
:   DSSSL is a stylesheet language for both print and online rendering.
    It is mainly intended to work with SGML.

```{=html}
<!-- -->
```

`<span id=3RR style="font-weight: bold">`{=html}DTD`</span>`{=html}
:   **D**ocument **T**ype **D**efinition
:   A DTD is the XML Document Type Definition contains or points to
    markup declarations that provide a grammar for a class of documents.

```{=html}
<!-- -->
```

`<span id=3RR style="font-weight: bold">`{=html}DTMF`</span>`{=html}
:   **D**ual **T**one **M**ulti **F**requency
:   Dual-tone multi-frequency signaling is used for telephone signaling
    over the line in the voice-frequency band to the call switching
    center. The version of DTMF used for telephone tone dialing is known
    by the trademarked term Touch-Tone (canceled March 13, 1984), and is
    standardized by ITU-T Recommendation Q.23. Other multi-frequency
    systems are used for signaling internal to the telephone network.

```{=html}
<!-- -->
```

`<span id=3RR style="font-weight: bold">`{=html}DVI`</span>`{=html}
:   **D**igital **V**isual **I**nterface

## E

`<span id=3RR style="font-weight: bold">`{=html}ECMAScript`</span>`{=html}
:   **E**uropean **C**omputer **M**anufacturers **A**ssociation
    **Script**
:   ECMAScript is a scripting language, standardized by Ecma
    International in the ECMA-262 specification. The language is widely
    used on the web, and is often referred to as JavaScript or JScript,
    after the two primary dialects of the specification.

```{=html}
<!-- -->
```

`<span id=3RR style="font-weight: bold">`{=html}EDI`</span>`{=html}
:   **E**lectronic **D**ata **I**nterchange
:   EDI is traditional data exchange standard for large organizations.
    It supports the electronic exchange of standard business documents
    and is currently the major data format for electronic commerce.

```{=html}
<!-- -->
```

`<span id=3RR style="font-weight: bold">`{=html}ETSI`</span>`{=html}
:   **E**uropean **T**elecommunications **S**tandards **I**nstitution
:   ETSI is an independent, non-for-profit, standardization organization
    of the telecommunications industry (equipment makers and network
    operators) in Europe, with worldwide projection. It has been
    successful in standardizing the GSM cell phone system and the TETRA
    professional mobile radio system.

## F

`<span id=3RR style="font-weight: bold">`{=html}FO`</span>`{=html}
:   **F**ormatting **O**bjects

```{=html}
<!-- -->
```

`<span id=3RR style="font-weight: bold">`{=html}FTP`</span>`{=html}
:   **F**ile **T**ransfer **P**rotocol
:   FTP is a file transfer protocol for exchanging files over any TCP/IP
    based network to manipulate files on another computer on that
    network regardless of which operating systems are involved (if the
    computers permit FTP access). There are many existing FTP client and
    server programs. FTP servers can be set up anywhere between game
    servers, voice servers, internet hosts, and other physical servers.

## G

`<span id=3RR style="font-weight: bold">`{=html}GIF`</span>`{=html}
:   **G**raphics **I**nterchange **F**ormat
:   GIF is an 8-bit-per-pixel bitmap image format that was introduced by
    CompuServe in 1987 and has since come into widespread usage on the
    World Wide Web due to its wide support and portability.
:   The format uses a palette of up to 256 distinct colors from the
    24-bit RGB color space.

```{=html}
<!-- -->
```

`<span id=3RR style="font-weight: bold">`{=html}GML`</span>`{=html}
:   **G**eography **M**arkup **L**anguage
:   GML is the XML grammar defined by the Open Geospatial Consortium
    (OGC) to express geographical features.

```{=html}
<!-- -->
```

`<span id=3RR style="font-weight: bold">`{=html}GUID`</span>`{=html}
:   **G**lobal **U**nique **Id**entifier
:   Globally Unique Identifiers are numbers assigned to a data object
    for use in a remote database. This identifier is assigned by the
    server.

## H

`<span id=3RR style="font-weight: bold">`{=html}HTML`</span>`{=html}
:   **H**yper**t**ext **M**arkup **L**anguage
:   HTML is the predominant markup language for web pages. It provides a
    means to describe the structure of text-based information in a
    document --- by denoting certain text as links, headings,
    paragraphs, lists, and so on --- and to supplement that text with
    interactive forms, embedded images, and other objects. HTML is
    written in the form of tags, surrounded by angle brackets. HTML can
    also describe, to some degree, the appearance and semantics of a
    document, and can include embedded scripting language code (such as
    JavaScript) which can affect the behavior of Web browsers and other
    HTML processors.

```{=html}
<!-- -->
```

`<span id=3RR style="font-weight: bold">`{=html}HTTP`</span>`{=html}
:   **H**ypertext **T**ransfer **P**rotocol
:   HTML is a communications protocol for the transfer of information on
    the intranet and the World Wide Web. Its original purpose was to
    provide a way to publish and retrieve hypertext pages over the
    Internet.

## I

`<span id=3RR style="font-weight: bold">`{=html}IDE`</span>`{=html}
:   **I**ntegrated **D**evelopment **E**nvironment
:   IDE is a software application that provides comprehensive facilities
    to computer programmers for software development. An IDE normally
    consists of a source code editor, a compiler and/or interpreter,
    build automation tools, and (usually) a debugger. IDEs are designed
    to maximise programmer productivity by providing tightly-knit
    components with similar user interfaces, thus minimising the amount
    of mode switching the programmer must do comparing to loose,
    discrete collections of disparate development programs.

```{=html}
<!-- -->
```

`<span id=3RR style="font-weight: bold">`{=html}IDL`</span>`{=html}
:   **I**nterface **D**escription **L**anguage
:   IDL is a specification language used to describe a software
    component\'s interface. IDLs describe an interface in a
    language-neutral way, enabling communication between software
    components that do not share a language -- for example, between
    components written in C++ and components written in Java.
:   IDLs are commonly used in remote procedure call software. In these
    cases the machines at either end of the \"\"link\"\" may be using
    different operating systems and computer languages. IDLs offer a
    bridge between the two different systems.

```{=html}
<!-- -->
```

`<span id=3RR style="font-weight: bold">`{=html}IDREF`</span>`{=html}
:   **Id**entifier **REF**erence

```{=html}
<!-- -->
```

`<span id=3RR style="font-weight: bold">`{=html}IFX`</span>`{=html}
:   **I**nteractive **F**inancial **E**xchange
:   IFX is an XML specification for financial transactions such as bill
    presentment and payment, business to business and consumer to
    business banking (e.g.: balances, financial transaction
    information), payments and automated teller machine (ATM)
    communications.

```{=html}
<!-- -->
```

`<span id=3RR style="font-weight: bold">`{=html}IMEI`</span>`{=html}
:   **I**nternational **M**obile **E**quipment **I**dentifier
:   ../IMEI/ is a number unique to every GSM and
    UMTS mobile phone. It is usually found printed on the phone
    underneath the battery.
:   The IMEI number is used by the GSM network to identify valid devices
    and therefore can be used to stop a stolen phone from accessing the
    network. For example, if a mobile phone is stolen, the owner can
    call his or her network provider and instruct them to \"\"ban\"\"
    the phone using its IMEI number. This renders the phone useless,
    regardless of whether the phone\'s SIM is changed.

```{=html}
<!-- -->
```

`<span id=3RR style="font-weight: bold">`{=html}ISO`</span>`{=html}
:   **I**nternational **O**rganization for **S**tandardization
:   ISO is an international-standard-setting body composed of
    representatives from various national standards organizations.
    Founded on 23 February 1947, the organization promulgates world-wide
    proprietary industrial and commercial standards. It is headquartered
    in Geneva, Switzerland.

## J

`<span id=3RR style="font-weight: bold">`{=html}Java EE`</span>`{=html}
:   **Java** Platform **E**nterprise **E**dition
:   Java EE is a widely used platform for server programming in the Java
    programming language. The Java EE Platform differs from the Standard
    Edition (SE) of Java in that it adds libraries which provide
    functionality to deploy fault-tolerant, distributed, multi-tier Java
    software, based largely on modular components running on an
    application server.

```{=html}
<!-- -->
```

`<span id=3RR style="font-weight: bold">`{=html}JAR`</span>`{=html}
:   **J**ava **AR**chive
:   In computing, a JAR file is used for aggregating many files into
    one. It is generally used to distribute Java classes and associated
    metadata.

```{=html}
<!-- -->
```

`<span id=3RR style="font-weight: bold">`{=html}JAVA`</span>`{=html}
:   Java is a programming language originally developed by Sun
    Microsystems and released in 1995 as a core component of Sun
    Microsystems\' Java platform. The language derives much of its
    syntax from C and C++ but has a simpler object model and fewer
    low-level facilities. Java applications are typically compiled to
    bytecode that can run on any Java virtual machine (JVM) regardless
    of computer architecture.

```{=html}
<!-- -->
```

`<span id=3RR style="font-weight: bold">`{=html}JAXP`</span>`{=html}
:   **J**ava **A**PI for **X**ML **P**rocessing
:   Java API for XML Processing is one of the Java XML programming APIs.
    It provides the capability of validating and parsing XML documents.
    The three basic parsing interfaces are the Document Object Model
    parsing interface (DOM interface), the Simple API for XML parsing
    interface (SAX interface) and the Streaming API for XML (StAX
    interface).

```{=html}
<!-- -->
```

`<span id=3RR style="font-weight: bold">`{=html}JAXR`</span>`{=html}
:   **J**ava **A**PI for **X**ML **R**egistries (pronounced \"jaks-p\")
:   JAXR creates a layer of abstraction, so that it can be used with
    UDDI and other types of XML Registries, such as the ebXML Registry
    and Repository standard.

```{=html}
<!-- -->
```

`<span id=3RR style="font-weight: bold">`{=html}JCP`</span>`{=html}
:   **J**ava **C**ommunity **P**rocess
:   JCP is a formalized process which allows interested parties to be
    involved in the definition of future versions and features of the
    Java platform.

```{=html}
<!-- -->
```

`<span id=3RR style="font-weight: bold">`{=html}JDBC`</span>`{=html}
:   **J**ava **D**ata**B**ase **C**onnectivity
:   JDBC is an API for the Java programming language that defines how a
    client may access a database. It provides methods for querying and
    updating data in a database. JDBC is oriented towards relational
    databases.

```{=html}
<!-- -->
```

`<span id=3RR style="font-weight: bold">`{=html}JDNC`</span>`{=html}
:   **JD**esktop **N**etwork **C**omponents
:   JDNC is a SwingLab subproject concerning contained components that
    allow to build easily Swing-based rich-client Java applications. The
    project is no more actively maintained. It has been replaced by
    Swing Application Framework (JSR 296)

```{=html}
<!-- -->
```

`<span id=3RR style="font-weight: bold">`{=html}JPEG`</span>`{=html}
:   **J**oint **P**hotographic **E**xperts **G**roup
:   JPEG is a commonly used method of compression for photographic
    images. The degree of compression can be adjusted, allowing a
    selectable tradeoff between storage size and image quality. JPEG
    typically achieves 10 to 1 compression with little perceivable loss
    in image quality.
:   JPEG is the most common image format used by digital cameras and
    other photographic image capture devices, and is the most common
    format for storing and transmitting photographic images on the World
    Wide Web.

```{=html}
<!-- -->
```

`<span id=3RR style="font-weight: bold">`{=html}JSP`</span>`{=html}
:   **J**ava**S**erver **P**ages
:   JSP is a Java technology that allows software developers to
    dynamically generate HTML, XML or other types of documents in
    response to a Web client request. The technology allows Java code
    and certain pre-defined actions to be embedded into static content.
:   The JSP syntax adds additional XML-like tags, called JSP actions, to
    be used to invoke built-in functionality. Additionally, the
    technology allows for the creation of JSP tag libraries that act as
    extensions to the standard HTML or XML tags. Tag libraries provide a
    platform independent way of extending the capabilities of a Web
    server.

```{=html}
<!-- -->
```

`<span id=3RR style="font-weight: bold">`{=html}JSPX`</span>`{=html}
:   JSP-page in XML-notation

```{=html}
<!-- -->
```

`<span id=3RR style="font-weight: bold">`{=html}JSTL`</span>`{=html}
:   **J**avaServer Pages **S**tandard **T**ag **L**ibrary
:   A collection of four custom-tag libraries which extend the JSP
    specification. As a component it is allocated in the Java EE Web
    application development platform.

## K

`<span id=3RR style="font-weight: bold">`{=html}KML`</span>`{=html}
:   **K**eyhole **M**arkup **L**anguage
:   KML is an XML-based Markup language for managing the display of
    three-dimensional geospatial data in the programs Google Earth,
    Google Maps, Google Mobile, ArcGIS Explorer and World Wind.

```{=html}
<!-- -->
```

`<span id=3RR style="font-weight: bold">`{=html}KMZ files`</span>`{=html}
:   Data compression / zipped KML file

## L

`<span id=3RR style="font-weight: bold">`{=html}LUID`</span>`{=html}
:   **L**ocal **U**nique **Id**entifier
:   Locally Unique Identifiers (LUID) are numbers assigned by the client
    to a data object in a local database (like a field or a row). They
    are non-reusable numbers assigned to these objects by the SyncML
    client.

## M

`<span id=3RR style="font-weight: bold">`{=html}MD5`</span>`{=html}
:   **M**essage-**D**igest algorithm **5**
:   In cryptography, MD5 is a widely used, partially insecure
    cryptographic hash function with a 128-bit hash value. As an
    Internet standard, MD5 has been employed in a wide variety of
    security applications, and is also commonly used to check the
    integrity of files. An MD5 hash is typically expressed as a 32 digit
    hexadecimal number.

```{=html}
<!-- -->
```

`<span id=3RR style="font-weight: bold">`{=html}MIF`</span>`{=html}
:   **M**aker **I**nterchange **F**ormat
:   MIF is a proprietary markup language associated with Adobe Systems\'
    FrameMaker product for technical document preparation.
:   While MIF is essentially specific to a single program (FrameMaker),
    it was widely used in the complex document workflows of small
    enterprises, especially in the industrial and manufacturing sector.

```{=html}
<!-- -->
```

`<span id=3RR style="font-weight: bold">`{=html}MIME type`</span>`{=html}
:   An Internet media type, originally called a MIME type after MIME and
    sometimes a Content-type after the name of a header in several
    protocols whose value is such a type, is a two-part identifier for
    file formats on the Internet. The identifiers were originally
    defined in RFC 2046 for use in e-mail sent through SMTP, but their
    use has expanded to other protocols such as HTTP and SIP.
:   A media type is composed of at least two parts: a type, a subtype,
    and one or more optional parameters. For example, subtypes of text
    type have an optional charset parameter that can be included to
    indicate the character encoding, and subtypes of multipart type
    often define a boundary between parts.

```{=html}
<!-- -->
```

`<span id=3RR style="font-weight: bold">`{=html}ML`</span>`{=html}
:   **M**arkup **L**anguage
:   A markup language is an artificial language using a set of
    annotations to text that describe how text is to be structured, laid
    out, or formatted.

```{=html}
<!-- -->
```

`<span id=3RR style="font-weight: bold">`{=html}MMS`</span>`{=html}
:   **M**ultimedia **M**essaging **S**ervice
:   MMS is a standard for telephone messaging systems that allows
    sending messages that include multimedia objects (images, audio,
    video, rich text) and not just text as in Short Message Service
    (SMS). It is mainly deployed in cellular networks along with other
    messaging systems like SMS, Mobile Instant Messaging and Mobile
    E-mail.

```{=html}
<!-- -->
```

`<span id=3RR style="font-weight: bold">`{=html}MPEG`</span>`{=html}
:   **M**oving **P**icture **E**xperts **G**roup
:   Moving Picture Experts Group, commonly referred to as simply MPEG,
    is a working group of ISO/IEC charged with the development of video
    and audio encoding standards. MPEG has standardized a variety of
    compression formats and ancillary standards.

```{=html}
<!-- -->
```

`<span id=3RR style="font-weight: bold">`{=html} MySQL`</span>`{=html}
:   MySQL is an open source relational database that supports XML. You
    can use the MySQL command line or a programming language of your
    choice to convert your MySQL databases and or tables to a well
    formed XML document.

## O

`<span id=3RR style="font-weight: bold">`{=html}ODBC`</span>`{=html}
:   API **O**pen **D**ata**B**ase **C**onnectivity
:   In computing, Open Database Connectivity provides a standard
    software API method for using database management systems (DBMS).
    The designers of ODBC aimed to make it independent of programming
    languages, database systems, and operating systems.

```{=html}
<!-- -->
```

`<span id=3RR style="font-weight: bold">`{=html}OpenGIS Consortium`</span>`{=html}
:   **Open** **G**eo**s**patial **Consortium**
:   The Open Geospatial Consortium, Inc. is a non-profit, international,
    voluntary consensus standards organization that is leading the
    development of standards for geospatial and location based services.

```{=html}
<!-- -->
```

`<span id=3RR style="font-weight: bold">`{=html}OpenOffice`</span>`{=html}
:   OpenOffice.org is exactly what its title suggests: an open source
    office applications suite. It is based on the source of Sun
    Microsystems\' StarOffice, which was donated to the open source
    community in 2000. OpenOffice.org will read and save files in
    several formats used by other office applications, but its default
    format is OpenDocument, which is an XML format standardized by OASIS
    (Organization for the Advancement of Structured Information
    Standards).

## P

`<span id=3RR style="font-weight: bold">`{=html}PDA`</span>`{=html}
:   **P**ersonal **D**igital **A**ssistants
:   PDA a handheld computer, also known as small or palmtop computers.

```{=html}
<!-- -->
```

`<span id=3RR style="font-weight: bold">`{=html}PDF`</span>`{=html}
:   **P**ortable **D**ocument **F**ormat
:   PDF is a fixed-layout format used for representing two-dimensional
    documents in a manner independent of the application software,
    hardware, and operating system. Each PDF file encapsulates a
    complete description of a 2-D document (and, with Acrobat 3-D,
    embedded 3-D documents) that includes the text, fonts, images, and
    2-D vector graphics that compose the documents.

```{=html}
<!-- -->
```

`<span id=3RR style="font-weight: bold">`{=html}PHP`</span>`{=html}
:   **H**ypertext **P**re**p**rocessor
:   PHP is a computer scripting language, originally designed for
    producing dynamic web pages. It is for server-side scripting, but
    can be used from a command line interface or in standalone graphical
    applications.

```{=html}
<!-- -->
```

`<span id=3RR style="font-weight: bold">`{=html}PML`</span>`{=html}
:   Phone Markup Language

```{=html}
<!-- -->
```

`<span id=3RR style="font-weight: bold">`{=html}PNG`</span>`{=html}
:   **P**ortable **N**etwork **G**raphics
:   PNG is a bitmapped image format that employs lossless data
    compression. PNG was created to improve upon and replace the GIF
    format, as an image-file format not requiring a patent license.

## R

`<span id=3RR style="font-weight: bold">`{=html}RDF`</span>`{=html}
:   **R**esource **D**escription **F**ramework
:   RDF is an international-standard-setting body composed of
    representatives from various national standards organizations.
    Founded on 23 February 1947, the organization promulgates world-wide
    proprietary industrial and commercial standards. It is headquarter

```{=html}
<!-- -->
```

`<span id=3RR style="font-weight: bold">`{=html}RDFS`</span>`{=html}
:   **R**esource **D**escription **F**ramework **S**chema
:   RDFS is an international-standard-setting body composed of
    representatives from various national standards organizations.
    Founded on 23 February 1947, the organization promulgates world-wide
    proprietary industrial and commercial standards.

```{=html}
<!-- -->
```

`<span id=3RR style="font-weight: bold">`{=html}RPC`</span>`{=html}
:   **R**emote **P**rocedure **C**all
:   RPC is a protocol that allows a computer program running on one host
    to cause code to be executed on another host without the programmer
    needing to explicitly code for this. An RPC is initiated by the
    caller (client) sending a request message to a remote system (the
    server) to execute a certain procedure using arguments supplied. A
    result message is returned to the caller. There are many variations
    and subtleties in various implementations, resulting in a variety of
    different (incompatible) RPC protocols.

```{=html}
<!-- -->
```

`<span id=3RR style="font-weight: bold">`{=html}RSS`</span>`{=html}
:   **R**DF **S**ite **S**ummary
:   RSS is a simple XML format used to syndicate headlines. It is now
    popularly used by websites that publish new content regularly and
    provide a list of headlines with links to their latest content.
    Content such as news feeds, events listings, project updates,
    blogger and most recently podcasting, video and image distribution
    can all be distributed by RSS.

```{=html}
<!-- -->
```

`<span id=3RR style="font-weight: bold">`{=html}RTF`</span>`{=html}
:   **R**ich **T**ext **F**ormat
:   RTF is a free document file format developed by Microsoft in 1987
    for cross-platform document interchange. Most word processors are
    able to read and write RTF documents.

## S

`<span id=3RR style="font-weight: bold">`{=html}SAMI`</span>`{=html}
:   **S**ynchronized **A**ccessible **M**edia **I**nterchange
:   Microsoft\'s proprietary alternative to SMIL.

```{=html}
<!-- -->
```

`<span id=3RR style="font-weight: bold">`{=html}SAX`</span>`{=html}
:   **S**imple **A**PI for **X**ML
:   The SAX classes provide an interface between the input streams from
    which XML documents are read and the client software which receives
    the data made available by the parser. The parser browses through
    the whole document and fires events every time it recognizes an XML
    construct.

```{=html}
<!-- -->
```

`<span id=3RR style="font-weight: bold">`{=html}SFTP`</span>`{=html}
:   **S**ecure **F**ile **T**ransfer **P**rotocol
:   SFTP is a program that uses SSH to transfer files. Unlike standard
    FTP, it encrypts both commands and data, preventing passwords and
    sensitive information from being transmitted in the clear over the
    network.

```{=html}
<!-- -->
```

`<span id=3RR style="font-weight: bold">`{=html}SGML`</span>`{=html}
:   **S**tandard **G**eneralized **M**arkup **L**anguage
:   The Standard Generalized Markup Language is a metalanguage in which
    one can define markup languages for documents.

```{=html}
<!-- -->
```

`<span id=3RR style="font-weight: bold">`{=html}SMIL`</span>`{=html}
:   **S**ynchronized **M**ultimedia **I**ntegration **L**anguage
    (pronounced \"smile\")
:   SMIL is a specialized language to describe the presentation of media
    objects. It enables simple authoring of interactive audiovisual
    presentations. SMIL is a XML based language and typically used for
    \"rich media\"/multimedia presentations which integrate streaming
    audio and video with images, text or any other media type.

```{=html}
<!-- -->
```

`<span id=3RR style="font-weight: bold">`{=html}SOAP`</span>`{=html}
:   **S**imple **O**bject **A**ccess **P**rotocol
:   SOAP is a method for sending information to and from Web Services in
    an extensible format. SOAP can be used to send information or remote
    procedure calls encoded as XML. Essentially, SOAP serves as a
    universally accepted method of communication with web services.
    Businesses adhere to the SOAP conventions in order to simplify the
    process of interacting with Web Services.

```{=html}
<!-- -->
```

`<span id=3RR style="font-weight: bold">`{=html}SQL`</span>`{=html}
:   **S**tandard **Q**uery **L**anguage
:   SQL is a database computer language designed for the retrieval and
    management of data in relational database management systems,
    database schema creation and modification, and database object
    access and control management.

```{=html}
<!-- -->
```

`<span id=3RR style="font-weight: bold">`{=html}SRGS`</span>`{=html}
:   **S**peech **R**ecognition **G**rammar **S**pecification

```{=html}
<!-- -->
```

`<span id=3RR style="font-weight: bold">`{=html}SSML`</span>`{=html}
:   **S**ynthesized **S**peech **M**arkup **L**anguage
:   There is an existing set of XML tags for Voice XML, called SSML.
    This set enables control of enough aspects of speech generation that
    a personable voice can be generated and manipulated by a user. A
    Text-to-Speech system uses the tags to take a text file and generate
    audible text in a voice.

```{=html}
<!-- -->
```

`<span id=3RR style="font-weight: bold">`{=html}SVG`</span>`{=html}
:   **S**calable **V**ector **G**raphics
:   SVG is a XML based, open-standard vector graphics file format and
    Web development language created by the W3C, and has been designed
    to be compatible with other W3C standards such as DOM, CSS, XML,
    XSLT, XSL, SMIL, HTML, and XHTML. It enables the creation of
    dynamically generated, high-quality graphics from real-time data.
    SVG allows you to design high-resolution graphics that can include
    elements such as gradients, embedded fonts, transparency, animation,
    and filter effects.

```{=html}
<!-- -->
```

`<span id=3RR style="font-weight: bold">`{=html}Sync4i`</span>`{=html}
:   SyncML for Java

```{=html}
<!-- -->
```

`<span id=3RR style="font-weight: bold">`{=html}SyncML`</span>`{=html}
:   **S**ynthesized **S**peech **M**arkup **L**anguage
:   There is an existing set of XML tags for Voice XML, called SSML.
    This set enables control of enough aspects of speech generation that
    a personable voice can be generated and manipulated by a user. A
    Text-to-Speech system uses the tags to take a text file and generate
    audible text in a voice.

## T

`<span id=3RR style="font-weight: bold">`{=html}TLS / SSL`</span>`{=html}
:   **T**ransport **L**ayer **S**ecurity and **S**ecure **S**ocket
    **L**ayer
:   TLS/SSL is a very secure and reliable protocol that provides
    end-to-end security sessions between two parties. XML adds an extra
    layer of security to TLS/SSL by encrypting part or all of the data
    being exchanged and by allowing for secure sessions between more
    than two parties.

```{=html}
<!-- -->
```

`<span id=3RR style="font-weight: bold">`{=html}TTS`</span>`{=html}
:   **T**ext-**T**o-**S**peech

## U

`<span id=3RR style="font-weight: bold">`{=html}UDDI`</span>`{=html}
:   **U**niversal **D**escription, **D**iscovery and **I**ntegration
:   UDDI defines registries in which services can be published and
    found. The UDDI specification was creaed by Microsoft, Ariba, and
    IBM and defines a data structure and Application Programming
    Interface (API).

```{=html}
<!-- -->
```

`<span id=3RR style="font-weight: bold">`{=html}UN/EDIFACT`</span>`{=html}
:   **U**nited **N**ations/**E**lectronic **D**ata **I**nterchange
    **F**or **A**dministration, **C**ommerce, and **T**ransport
:   UN/EDIFACT is the international EDI standard developed under the
    United Nations.

```{=html}
<!-- -->
```

`<span id=3RR style="font-weight: bold">`{=html}URI`</span>`{=html}
:   **U**niform **R**esource **I**dentifier
:   URI is a compact string of characters used to identify or name a
    resource. The main purpose of this identification is to enable
    interaction with representations of the resource over a network,
    typically the World Wide Web, using specific protocols. URIs are
    defined in schemes defining a specific syntax and associated
    protocols.

```{=html}
<!-- -->
```

`<span id=3RR style="font-weight: bold">`{=html}URL`</span>`{=html}
:   **U**niform **R**esource **L**ocator
:   URL is a technical, web-related term used in two distinct meanings:
    In popular usage and many technical documents, it is a synonym for
    URI. In popular usage, it means a web page address. Strictly it is a
    compact string of characters for a resource available via the
    Internet.

## V

`<span id=3RR style="font-weight: bold">`{=html}VoiceXML`</span>`{=html}
:   Speaking web data
:   VoiceXML is created to generate audio dialogs that allows the use of
    synthesized speech, digitized audio, recognition of spoken and
    DTMF(Dual Tone Multi-Frequency Touch-tone or push-button dialing.)
    In other words, VoiceXML allows the use of computer speech, recorded
    audio, human speech, and telephones as input and output devices.

## W

`<span id=3RR style="font-weight: bold">`{=html}W3C`</span>`{=html}
:   **W**orld **W**ide **W**eb **C**onsortium
:   W3C is the main international standards organization for the World
    Wide Web (abbreviated WWW or W3).

```{=html}
<!-- -->
```

`<span id=3RR style="font-weight: bold">`{=html}WAP`</span>`{=html}
:   **W**ireless **A**pplication **P**rotocol

```{=html}
<!-- -->
```

`<span id=3RR style="font-weight: bold">`{=html}WBXML`</span>`{=html}
:   **W**AP **B**inary **XML**
:   WAP Binary XML (WBXML) is a form of XML whereby the XML tags are
    abbreviated in order to shorten the markup for transmission to
    mobile devices, which commonly have bandwidth and memory
    limitations. The XML tags are encoded into a binary shorthand to
    save space.

```{=html}
<!-- -->
```

`<span id=3RR style="font-weight: bold">`{=html}WCDMA`</span>`{=html}
:   **W**ide-band **C**ode-**D**ivision **M**ultiple **A**ccess

```{=html}
<!-- -->
```

`<span id=3RR style="font-weight: bold">`{=html}WDDX`</span>`{=html}
:   **W**eb **D**istributed **D**ata e**X**change
:   WDDX was created by Allaire, now known as Macromedia, to solve the
    problem of exchanging data between different web applications. This
    XML-based technology enables complex data to be exchanged between
    totally different Web programming languages by creating \'Web
    Syndicate Networks.\'

```{=html}
<!-- -->
```

`<span id=3RR style="font-weight: bold">`{=html}WiMP`</span>`{=html}
:   **Wi**ndows **M**edia **P**layer

```{=html}
<!-- -->
```

`<span id=3RR style="font-weight: bold">`{=html}WML`</span>`{=html}
:   **W**ireless **M**arkup **L**anguage

```{=html}
<!-- -->
```

`<span id=3RR style="font-weight: bold">`{=html}WSDL`</span>`{=html}
:   **W**eb **S**ervice **D**escription **L**anguage (pronounced
    \"wiz-dal\")
:   WSDL is an XML-based language that provides a model for describing
    Web services.

```{=html}
<!-- -->
```

`<span id=3RR style="font-weight: bold">`{=html}WWW`</span>`{=html}
:   **W**orld **W**ide **W**eb (also W3)

## X

`<span id=3RR style="font-weight: bold">`{=html}X.12`</span>`{=html}
:   ASC **X12** (also known as ANSI ASC X12)
:   X.12 the official designation of the U.S. national standards body
    for the development and maintenance of Electronic Data Interchange
    (EDI) standards.

```{=html}
<!-- -->
```

`<span id=3RR style="font-weight: bold">`{=html}XALAN`</span>`{=html}
:   XALAN is a XSLT processor for transforming XML documents into HTML.

```{=html}
<!-- -->
```

`<span id=3RR style="font-weight: bold">`{=html}XBL`</span>`{=html}
:   **X**ML **B**inding **L**anguage
:   XBL describes the ability to associate elements in a document with
    script, event handlers, CSS and more complex content models, which
    can be stored in another document.

```{=html}
<!-- -->
```

`<span id=3RR style="font-weight: bold">`{=html}XBRL`</span>`{=html}
:   e**X**tensible **B**usiness **R**eporting **L**anguage

```{=html}
<!-- -->
```

`<span id=3RR style="font-weight: bold">`{=html}XForms`</span>`{=html}
:   XForms are the next generation of HTML forms and is richer and more
    flexible than HTML forms.
:   XForms uses XML for data definition and HTML or XHTML for data
    display. XForms separates the data logic of a form from its
    presentation. Separating data from presentation makes XForms device
    independent, because the data model can be used for all devices.

```{=html}
<!-- -->
```

`<span id=3RR style="font-weight: bold">`{=html}XHTML`</span>`{=html}
:   e**X**tensible **H**yper**T**ext **M**arkup **L**anguage
:   XHTML is a cross between HTML and XML.

```{=html}
<!-- -->
```

`<span id=3RR style="font-weight: bold">`{=html}XLink`</span>`{=html}
:   A XLink allows elements to be inserted into XML documents that
    create links between resources such as documents, images, files and
    other pages. It is similar in concept to an HTML hyperlink, but is
    more powerful and flexible.

```{=html}
<!-- -->
```

`<span id=3RR style="font-weight: bold">`{=html}XML`</span>`{=html}
:   e**X**tensible **M**arkup **L**anguage
:   XML is a technology for managing data exchange.
:   XML is a general-purpose specification for creating custom markup
    languages. It is classified as an extensible language because it
    allows its users to define their own elements. Its primary purpose
    is to facilitate the sharing of structured data across different
    information systems, particularly via the Internet, and it is used
    both to encode documents and to serialize data.

```{=html}
<!-- -->
```

`<span id=3RR style="font-weight: bold">`{=html}XML document`</span>`{=html}
:   A XML document is a XML file containing XML code.

```{=html}
<!-- -->
```

`<span id=3RR style="font-weight: bold">`{=html}XML schema`</span>`{=html}
:   A XML Schema is a XML file that describes the structure of a
    document and its tags.

```{=html}
<!-- -->
```

`<span id=3RR style="font-weight: bold">`{=html}XML stylesheet`</span>`{=html}
:   An XML file containing formatting instructions for an XML file.

```{=html}
<!-- -->
```

`<span id=3RR style="font-weight: bold">`{=html}XML-RPC`</span>`{=html}
:   XML-RPC is a *r*emote *p*rocedure *c*all protocol, which uses XML to
    encode its calls and HTTP as a transport mechanism. It is a very
    simple protocol, defining only a handful of data types and commands,
    and the entire description can be printed on two pages of paper.

```{=html}
<!-- -->
```

`<span id=3RR style="font-weight: bold">`{=html}XMP `</span>`{=html}
:   e**X**tensible **M**etadata **P**latform
:   The XMP is a specification describing RDF-based data and storage
    models for metadata about documents in any format. XMP can be
    included in text files such as HTML or SVG, image formats such as
    JPEG or GIF and Adobe\'s own formats like Photoshop or Acrobat.

```{=html}
<!-- -->
```

`<span id=3RR style="font-weight: bold">`{=html}XPath`</span>`{=html}
:   XPath is a language for finding information in an XML document.
    XPath is used to navigate through elements and attributes in an XML
    document.

```{=html}
<!-- -->
```

`<span id=3RR style="font-weight: bold">`{=html}XQL`</span>`{=html}
:   e**X**tensible **Q**uery **L**anguage
:   XQL is a query language designed specifically for XML. In the same
    sense that SQL is a query language for relational tables and OQL is
    a query language for objects stored in an object database, XQL is a
    query language for XML documents.

```{=html}
<!-- -->
```

`<span id=3RR style="font-weight: bold">`{=html}XQuery`</span>`{=html}
:   XQuery is a query language under development by the World Wide Web
    Consortium (W3C). The ambitious task is to develop the first world
    standard for querying Web documents. XQuery is a versatile markup
    language, capable of labeling the information content of diverse
    data sources including structured and semi-structured documents,
    relational databases, and object repositories.

```{=html}
<!-- -->
```

`<span id=3RR style="font-weight: bold">`{=html}XSL`</span>`{=html}
:   **X**ML **S**tylesheet **L**anguage

```{=html}
<!-- -->
```

`<span id=3RR style="font-weight: bold">`{=html}XSLT`</span>`{=html}
:   e**X**tensible **S**tylesheet **L**anguage **T**ransformations
:   XSLT is an XML-based language used for the transformation of XML
    documents into other XML or \"human-readable\" documents.

```{=html}
<!-- -->
```

`<span id=3RR style="font-weight: bold">`{=html}XSP`</span>`{=html}
:   e**X**tensible **S**erver **P**ages

```{=html}
<!-- -->
```

`<span id=3RR style="font-weight: bold">`{=html}XSU`</span>`{=html}
:   **X**ML **S**QL **U**tility
:   Oracle\'s XML SQL Utility uses a schematic mapping that defines how
    to map tables and views, including object-relational features, to
    XML documents. Oracle translates the chain of object references from
    the database into the hierarchical structure of XML elements.

```{=html}
<!-- -->
```

`<span id=3RR style="font-weight: bold">`{=html}XUL`</span>`{=html}
:   e**X**tensible **U**ser Interface **L**anguage
:   XUL is an XML-based user interface language originally developed for
    use in the Netscape browser. It is now maintained by Mozilla. Like
    HTML, in XUL you can create an interface using a relatively simple
    markup language, define the appearance with CSS style sheets, and
    use JavaScript to manipulate behavior. Unlike HTML, however, XUL
    provides a rich set of user interface widgets to create, for
    example, menus, toolbars and tabbed panels.

```{=html}
<!-- -->
```

`<span id=3RR style="font-weight: bold">`{=html}XULRunner`</span>`{=html}
:   The XULRunner is a Mozilla runtime package that can be used to
    bootstrap XUL+XPCOM applications that are as rich as Firefox and
    Thunderbird. It will provide mechanisms for installing, upgrading,
    and uninstalling these applications. XULRunner will also provide
    libxul, a solution, which allows the embedding of Mozilla
    technologies in other projects and products.


# XML - Managing Data Exchange/Author guidelines

## Editing Chapters

You simply click on the \"edit this page\" tab at the top of any page
you want to edit. You can also just edit a section or subsection - any
place you see a little \'edit\' to the far right above a line, click on
it to edit that section. The thoughts behind the editing process of the
chapters will be documented in the \"discussion\" tab of each chapter -
go there to record your intentions for your assigned chapter.

If you would like to make any suggestions to the editorial board, we
welcome them. At the top of the XML: Managing Data Exchange contents
page is a tab to \"discussion\" follow that link and edit the page with
your comments, be sure to follow the directions for entries.

-   **Use wiki code, not HTML code** when you edit a page.

```{=html}
<!-- -->
```
-   how to make a link : \[\[XML: Managing Data
    Exchange/NameOfThePage(on the page)\|NameOfThePage(displayed as the
    link)\]\]

```{=html}
<!-- -->
```
-   no plagiarism : please use citations and references to books,
    articles, and websites that have helped you contribute to the book.

```{=html}
<!-- -->
```
-   All figures and graphics should be prefixed with \'xml\' to avoid
    accidentally overwriting another file (e.g., xmldmcity defines the
    data model for city).

```{=html}
<!-- -->
```
-   Where possible use Portable Network Graphics
    (PNG) for graphics because of its
    superiority to GIF and JPEG. Also, PNG is Open Source.
    OpenOffice.org Draw can be used to
    create PNG files.

## Consistency guidelines

**- developed to create a consistent look and feel to the book**

### Layout

-   **Chapter summary required**

The bottom of each chapter should include a chapter summary highlighting
the key points of the chapter. Follow the formatting guideline detailed
later on this page.

-   **Bold new words**

As new concepts and terminology are introduced in each chapter, make
sure that they are defined first before using them; so that the reader
understands what the words and ideas represent. **Bold** the first
occurrence of the word (or preceding the definition).

-   **Use the sentence format for titles**

Capitalize the first letter of a title and allow the rest of the letters
to be lower case, as in this title.

-   **Avoid the use of underline and all capital words**

```{=html}
<!-- -->
```
-   **Tables, figures, and code references**

For consistency, label all tables, figures (e.g. charts and photos), and
code examples as \"exhibits.\" Place the label for exhibits at the top
of the exhibit, flush left, and enumerate the exhibits, followed by a
brief caption. Examples: \"Exhibit 1: XML data types\" and \"Exhibit 2:
Schema code example\"

-   **Concept capsules and breathing room**

Think of your chapter as a data model or a large steak. A useful data
model is broken down into its smallest attributes that require recording
and maintaining for future analysis. A large steak is best eaten in bite
size pieces to prevent choking and promote good digestion. As you revise
your chapter consider the basic elements of your topic; break your topic
down and present each element in a section - so that it is easy for the
reader to follow and understand each part. Feel free to use bullets to
represent lists.

To continue with the steak analogy, it is also good to eat slowly,
taking breaths between each bite. Allow for spaces between each
subsection and greater spaces between each section. This opens up the
text so that it does not appear to dense and compact - and therefore
intimidating.

-   **NetBeans (or other XML editor) Examples**

Scroll down the contents page to \"Appendices\". You will see a link to
the chapter \"Using an XML editor\". When you open this link - go to the
edit this page tab and insert a link under the NetBeans heading with the
name of your chapter. This is the format for the link: \[\[XML: Managing
Data Exchange/ChapterName(NetBeans)\|ChapterName\]\] After you save your
edit, the XML Editor page will contain a link to your new NetBeans page.
It will appear red because no information has been posted to that page
yet. Click on the link and paste all the NetBeans information from your
chapter into the edit box. In your assigned chapter, at the places where
there were NetBeans information (that you just cut and paste into the
XML editor page) - put a link to the XML editor - your Chapter page.

-   **Help:Wikibooks** \<= this link will
    provide several wiki guidelines - this page is also accessible from
    the \'help\' link in the navigation box on the left bar of every one
    of these Wikibook pages. It contains information on inserting
    pictures, creating tables using wiki language (which is much easier
    to write and read).

This help page also has a link to a \"sandbox.\" This is a blank page
that allows you to experiment with wiki without affecting a real page.

### Code examples

-   Make all code examples a uniform color (black)---some are all black;
    some are multicolored. Please change the ones that are multicolored
    to all black.

```{=html}
<!-- -->
```
-   HTML code is lower case.

```{=html}
<!-- -->
```
-   Keep the comments in the code, but put a space above and bellow each
    comment.

```{=html}
<!-- -->
```
-   Include the file name of the code in a comments tag. If you are the
    author of the code, include your name and the date you authored the
    code in the comments. See example:

```{=html}
<!-- -->
```
    <nowiki>

    </nowiki>

-   Keep all the example codes in the chapter on the same topic---the
    TOURGUIDE. If there are examples in your chapter that deviate from
    this theme, please change them to show examples from TOURGUIDE.

```{=html}
<!-- -->
```
-   If your code contains HTML or the XML declaration then you will want
    to put the tags \
 \... \

```{=html}
<!-- -->
```
-   In order to get those \'pre\' tags to show up I had to use the tags
    \<nowiki\> \... `</nowiki>`{=html}

If you run into trouble while inserting code, one of the two tags
mentioned above might be able to get you out.

-   You do **not** have to create a table around samples of a code
    example; usually just putting a few spaces in front of each line
    will create the dashed blue lined box

### Spelling

-   Use the spelling \"stylesheet\" instead of \"style sheet.\"

```{=html}
<!-- -->
```
-   Use the spelling \"opening tag\" instead of \"opening-tag.\"

```{=html}
<!-- -->
```
-   **Check your wiki text with a spellchecker** (e.g. copy and paste in
    a text editor that supports spell checking).

### Exercises & Answers

Create two links at the bottom of your chapter, one to an Exercises page
and one to the Answers page already made (you can find this answer page
link at the bottom of the contents page).

In the Exercises page, cut and paste your chapter exercises into a **new
page**. An easy way to create a new page is simply to go to your main
chapter page, type \"exercises\" at the end of the URL, and hit enter.
If the page does not exist, Wikipedia will ask you to create the page by
going to \"edit this page.\"

At the top and bottom of the Exercises page, provide a link to the
chapter and the Answers page---and vice versa with the Answers page.

### Elements of Style - Principles of Composition

**taken from *the Elements of Style* - by William Strunk and E.B.
White**

-   **Make the paragraph the unit of composition** - The subject will
    need to be broken down into topics, and topics will need to be
    broken down into concepts and subconcepts. Each concept should be
    explored within its own paragraph.

```{=html}
<!-- -->
```
-   **Put statements in positive form** - \"Make definitive assertions.
    Avoid tame, hesitating, noncommittal language. Use the word \'not\'
    as a means of denial or in antithesis, never as means of evasion.\"

```{=html}
<!-- -->
```
-   **Use definite, specific, concrete language** - \"Prefer the
    specific to the general, the definite to the vague, the concrete to
    the abstract.\"

```{=html}
<!-- -->
```
-   **Omit needless words** - \"A sentence should contain no unnecessary
    words, a paragraph no unnecessary sentences\...Many expressions
    violate this principle: \'the fact that,\' he is a man who \... - he
    \...\"

```{=html}
<!-- -->
```
-   **Avoid a succession of loose sentences**

```{=html}
<!-- -->
```
-   **Express coordinate ideas in similar form**

```{=html}
<!-- -->
```
-   **Keep related words together**

```{=html}
<!-- -->
```
-   **Place the emphatic words of a sentence at the end**

## Source code

For inserting source code (e.g., XML or Java) into the book, use the
following format:

    <nowiki>
      <country>
          au
          <country>Australia</country>
          <flag>au.gif</flag>
      </country>
    </nowiki>

Use the following wiki code:

    <pre><nowiki>
      <country>
          au
          <country>Australia</country>
          <flag>au.gif</flag>
      </country>
    </nowiki></pre>

## Section summary

Section summaries should appear in the following format:

  -------------------
  A chapter summary
  -------------------

Use the following wiki code:

    {| style="background:linen; border: 1px solid black; padding: 1em; width: 100%;"
    |-
    | A chapter summary
    |-
    |}

## Story

Stories/case studies should appear in the following format:

  ---------
  A story
  ---------

Use the following wiki code:

    {| style="background: lightyellow; border: 1px solid black; padding: 1em; width: 100%;"
    |-
    | A story
    |-
    |}

## References

-   A guide to Wiki
    editing
    is online
-   HTML tables can be converted to Wiki format using an online
    tool.