<?xml version="1.0"?>
<!-- $Id: wwww.xml 588 2011-03-01 06:56:27Z dret $ -->
<!-- dret.net glossary (http://dret.net/glossary/); (c) 2000-2011 dret (http://dret.net/netdret/) -->
<!DOCTYPE topicmap [
    <!ELEMENT topicmap (topics, relations, locators)>
    <!ELEMENT topics (topic+)>
    <!ELEMENT topic (derived-from*, name, alias?, desc?, status?)>
    <!ATTLIST topic
    domain NMTOKENS #IMPLIED
    TID ID #REQUIRED
    crdate CDATA #REQUIRED
    modate CDATA #IMPLIED
>
    <!ELEMENT derived-from EMPTY>
    <!ATTLIST derived-from
    template IDREF #REQUIRED
>
    <!ELEMENT name (#PCDATA)>
    <!ELEMENT alias (#PCDATA)>
    <!ELEMENT desc (#PCDATA | topicref | text)*>
    <!ELEMENT status (#PCDATA | topicref | text)*>
    <!ELEMENT relations (relation+)>
    <!ELEMENT relation (roleref, roleref+)>
    <!ATTLIST relation
    RelID NMTOKEN #REQUIRED
    crdate CDATA #REQUIRED
    modate CDATA #IMPLIED
>
    <!ELEMENT locators (locator+)>
    <!ELEMENT locator (uri)>
    <!ATTLIST locator
    LID ID #REQUIRED
    crdate CDATA #REQUIRED
    modate CDATA #IMPLIED
>
    <!ELEMENT uri (#PCDATA)>
    <!ATTLIST uri
    href CDATA #REQUIRED
>
    <!ELEMENT roleref ((topicref | locref)+)>
    <!ATTLIST roleref
    RolID NMTOKEN #REQUIRED
>
    <!ELEMENT topicref (#PCDATA)>
    <!ATTLIST topicref
    TID IDREF #REQUIRED
>
    <!ELEMENT locref EMPTY>
    <!ATTLIST locref
    LID IDREF #REQUIRED
>
    <!ELEMENT text EMPTY>
    <!ATTLIST text
    date CDATA #IMPLIED
>
]>
<topicmap>
    <topics>
    <topic domain="core" TID="topic" crdate="20010115">
        <derived-from template="topic"/>
        <name>topic</name>
        <desc>This is the base object from which (directly or indirectly) all topics must be derived. In a perfect system, this object would probably be built-in, but this isn't a perfect system...</desc>
    </topic>
    <topic domain="core" TID="moviesound" crdate="20020709">
        <derived-from template="dataformat"/>
        <name>Movie Sound Format</name>
        <desc>The <topicref TID="moviesound"/> is a base topic for topics describing a <topicref TID="dataformat"/> for movie soundtracks.</desc>
    </topic>
    <topic domain="core" TID="surroundsound" crdate="20051212">
        <derived-from template="moviesound"/>
        <name>Surround Sound Format</name>
        <desc><topicref TID="surroundsound"/> is a base topic for <topicref TID="moviesound"/>s describing the concept of spatial imaging of audio.</desc>
    </topic>
    <topic domain="core" TID="achievement" crdate="20010119">
        <derived-from template="topic"/>
        <name>Achievement</name>
        <desc>The <topicref TID="achievement"/> is a base topic for topics describing a general technical achievement.</desc>
    </topic>
    <topic domain="core" TID="technology" crdate="20010119">
        <derived-from template="achievement"/>
        <name>Technology</name>
        <desc>The <topicref TID="technology"/> is a base topic for topics describing an applicable technological achievement.</desc>
    </topic>
    <topic domain="core" TID="internationalorganization" crdate="20010119">
        <derived-from template="organization"/>
        <name>International Organization</name>
        <desc>The <topicref TID="internationalorganization"/> is a base topic for topics describing a multi-Governmentally influenced body.</desc>
    </topic>
    <topic domain="core" TID="framework" crdate="20010119">
        <derived-from template="concept"/>
        <name>Framework</name>
        <desc>The <topicref TID="framework"/> is a base topic for topics describing a software product which can be used to run or construct applications.</desc>
    </topic>
    <topic domain="core" TID="company" crdate="20010119">
        <derived-from template="organization"/>
        <name>Company</name>
        <desc>The <topicref TID="company"/> is a base topic for topics describing a commercial Organization.</desc>
    </topic>
    <topic domain="core" TID="clientsidetechnology" crdate="20020626">
        <derived-from template="technology"/>
        <name>Client Side Technology</name>
        <desc>The <topicref TID="clientsidetechnology"/> is a base topic for topics describing a <topicref TID="technology"/> which is used on the <topicref TID="client"/> side of a scenario based on the <topicref TID="clientserver"/>.</desc>
    </topic>
    <topic domain="core" TID="serversidetechnology" crdate="20020626">
        <derived-from template="technology"/>
        <name>Server Side Technology</name>
        <desc>The <topicref TID="serversidetechnology"/> is a base topic for topics describing a <topicref TID="technology"/> which is used on the <topicref TID="server"/> side of a scenario based on the <topicref TID="clientserver"/>.</desc>
    </topic>
    <topic domain="core" TID="imsystem" crdate="20010220">
        <derived-from template="technology"/>
        <name>Instant Messaging System</name>
        <desc>The <topicref TID="imsystem"/> is a base topic for topics describing a system for the synchronous exchange of messages.</desc>
    </topic>
    <topic domain="wwww" TID="opac" crdate="20060209">
        <derived-from template="concept"/>
        <name>OPAC</name>
        <alias>Online Public Access Catalog</alias>
    </topic>
    <topic domain="core" TID="identifier" crdate="20010316">
        <derived-from template="concept"/>
        <name>Identifier</name>
        <desc>The <topicref TID="identifier"/> is a base topic for topics describing ways for identifying resources.</desc>
    </topic>
    <topic domain="core" TID="adt" crdate="20051121">
        <derived-from template="concept"/>
        <name>ADT</name>
        <alias>Abstract Data Type</alias>
        <desc>An <topicref TID="adt"/> is a formally specified set of values and associated operations, independent from any particular implementation. <topicref TID="adt"/>s are one of the foundations of <topicref TID="oo"/>, because they formalize the notion of "information hiding" or "encapsulation", which hides the implementation of an <topicref TID="adt"/> (i.e., a class) behind its interface.</desc>
    </topic>
    <topic domain="core" TID="grammar" crdate="20060509">
        <derived-from template="concept"/>
        <name>Grammar</name>
        <desc>A <topicref TID="grammar"/> is a set of rules describing how valid sentences of a formal language are to be constructed. <topicref TID="grammar"/>s are often used to describe complex structures in computer science, such as  <topicref TID="programminglanguage"/>s or <topicref TID="dataformat"/>s.</desc>
    </topic>
    <topic domain="core" TID="oo" crdate="20051121">
        <derived-from template="concept"/>
        <name>OO</name>
        <alias>Object-Orientation</alias>
        <desc><topicref TID="oo"/> is a modeling methodology which is mainly build around the concepts of encapsulation (provided by <topicref TID="adt"/>s), inheritance, and polymorphism. <topicref TID="oop"/> is the attempt to use this methodology in a given programming environment.</desc>
    </topic>
    <topic domain="core" TID="parser" crdate="20030310">
        <derived-from template="concept"/>
        <name>Parser</name>
        <desc>A <topicref TID="parser"/> is a program for structuring a linear representation in accordance with a given <topicref TID="grammar"/>. For each <topicref TID="grammar"/>, there are generally an infinite number of linear representations (sentences) that can be structured with it. That is, a finite-size <topicref TID="grammar"/> can supply structure to an infinite number of sentences. This is the main strength of the <topicref TID="grammar"/> paradigm and indeed the main source of the importance of <topicref TID="grammar"/>s: they summarize succinctly the structure of an infinite number of objects of a certain class. There are several reasons to perform this structuring process called parsing. The most important reason derives from the fact that the obtained structure helps to process the object further.</desc>
    </topic>
    <topic domain="core" TID="xmlpipelinelanguage" crdate="20030526">
        <derived-from template="concept"/>
        <name>XML Pipeline Language</name>
        <desc>The <topicref TID="xmlpipelinelanguage"/> is a base topic for topics describing languages for pipelined <topicref TID="xml"/> processing. The actual <topicref TID="dataformat"/> of the pipeline is not fixed, it may be either an <topicref TID="xml"/> document, or some other representation of XML, such as a <topicref TID="dom"/> <topicref TID="tree"/> or a stream of <topicref TID="sax"/> events.</desc>
    </topic>
    <topic domain="core" TID="parsergenerator" crdate="20020716">
        <derived-from template="concept"/>
        <name>Parser Generator</name>
        <desc>The <topicref TID="parsergenerator"/> is a base topic for topics describing tools for building <topicref TID="parser"/>s. Some tools are using separate components for lexical analysis and parsing (such as <topicref TID="lex"/>/<topicref TID="yacc"/>), others are integrated (such as <topicref TID="javacc"/>).</desc>
    </topic>
    <topic domain="core" TID="colorspace" crdate="20010314">
        <derived-from template="concept"/>
        <name>Color Space</name>
        <desc>The <topicref TID="colorspace"/> is a base topic for topics describing ways for representing color.</desc>
    </topic>
    <topic domain="core" TID="displaystd" crdate="20010315">
        <derived-from template="technology"/>
        <name>Display Standard</name>
        <desc>The <topicref TID="displaystd"/> is a base topic for topics describing a <topicref TID="technology"/> for how to display data on a <topicref TID="display"/>.</desc>
    </topic>
    <topic domain="core" TID="display" crdate="20010314">
        <derived-from template="technology"/>
        <name>Display</name>
        <desc>The <topicref TID="display"/> is a base topic for topics describing a <topicref TID="technology"/> for displaying data.</desc>
    </topic>
    <topic domain="core" TID="storage" crdate="20010302">
        <derived-from template="technology"/>
        <name>Storage Medium</name>
        <desc>The <topicref TID="storage"/> is a base topic for topics describing media for data storage.</desc>
    </topic>
    <topic domain="core" TID="scstorage" crdate="20010305">
        <derived-from template="storage"/>
        <name>Semiconductor Storage Medium</name>
        <desc>The <topicref TID="scstorage"/> is a base topic for topics describing media for semiconductor data storage.</desc>
    </topic>
    <topic domain="wwww" TID="dimm" crdate="20020709">
        <derived-from template="topic"/>
        <name>DIMM</name>
        <alias>Double In-line Memory Module</alias>
    </topic>
    <topic domain="wwww" TID="simm" crdate="20020709">
        <derived-from template="topic"/>
        <name>SIMM</name>
        <alias>Single In-line Memory Module</alias>
    </topic>
    <topic domain="wwww" TID="flashrom" crdate="20020709">
        <derived-from template="prom"/>
        <name>Flash ROM</name>
    </topic>
    <topic domain="wwww" TID="eeprom" crdate="20020709">
        <derived-from template="prom"/>
        <name>EEPROM</name>
        <alias>Electrically Erasable PROM</alias>
    </topic>
    <topic domain="wwww" TID="eprom" crdate="20020709">
        <derived-from template="prom"/>
        <name>EPROM</name>
        <alias>Erasable PROM</alias>
    </topic>
    <topic domain="wwww" TID="prom" crdate="20020709">
        <derived-from template="rom"/>
        <name>PROM</name>
        <alias>Programmable ROM</alias>
    </topic>
    <topic domain="wwww" TID="rom" crdate="20020709">
        <derived-from template="scstorage"/>
        <name>ROM</name>
        <alias>Read-only Memory</alias>
    </topic>
    <topic domain="wwww" TID="ddrsdram" crdate="20020709">
        <derived-from template="sdram"/>
        <name>DDR-SDRAM</name>
        <alias>Double Data Rate SDRAM</alias>
    </topic>
    <topic domain="wwww" TID="drdram" crdate="20020709">
        <derived-from template="dram"/>
        <name>DRDRAM</name>
        <alias>Direct Rambus DRAM</alias>
    </topic>
    <topic domain="wwww" TID="sdram" crdate="20020709">
        <derived-from template="dram"/>
        <name>SDRAM</name>
        <alias>Synchronous DRAM</alias>
    </topic>
    <topic domain="wwww" TID="dram" crdate="20020709">
        <derived-from template="ram"/>
        <name>DRAM</name>
        <alias>Dynamic RAM</alias>
    </topic>
    <topic domain="wwww" TID="sram" crdate="20020709">
        <derived-from template="ram"/>
        <name>SRAM</name>
        <alias>Static RAM</alias>
    </topic>
    <topic domain="wwww" TID="ram" crdate="20020709">
        <derived-from template="scstorage"/>
        <name>RAM</name>
        <alias>Random Access Memory</alias>
    </topic>
    <topic domain="core" TID="mstorage" crdate="20010302">
        <derived-from template="storage"/>
        <name>Magnetic Storage Medium</name>
        <desc>The <topicref TID="mstorage"/> is a base topic for topics describing media for magnetic data storage.</desc>
    </topic>
    <topic domain="core" TID="ostorage" crdate="20010302">
        <derived-from template="storage"/>
        <name>Optical Storage Medium</name>
        <desc>The <topicref TID="ostorage"/> is a base topic for topics describing media for optical data storage.</desc>
    </topic>
    <topic domain="core" TID="mostorage" crdate="20010305">
        <derived-from template="storage"/>
        <name>Magneto-Optical Storage Medium</name>
        <desc>The <topicref TID="mostorage"/> is a base topic for topics describing media for magneto-optical data storage.</desc>
    </topic>
    <topic domain="core" TID="componentmodel" crdate="20001220">
        <derived-from template="technology"/>
        <name>Component Model</name>
        <desc>The <topicref TID="componentmodel"/> is a base topic for topics describing component models. A <topicref TID="componentmodel"/> is a framework for creating usually complex software from small, re-usable software components.</desc>
    </topic>
    <topic domain="core" TID="directory" crdate="20001220">
        <derived-from template="technology"/>
        <name>Directory</name>
        <desc>The <topicref TID="directory"/> is a base topic for topics describing directory systems.</desc>
    </topic>
    <topic domain="wwww" TID="sso" crdate="20040802">
        <derived-from template="concept"/>
        <name>SSO</name>
        <alias>Single Sign-On</alias>
        <desc><topicref TID="sso"/> systems enable users to use one <topicref TID="authentication"/> procedure for accessing multiple applications or resources.</desc>
    </topic>
    <topic domain="core" TID="encryption" crdate="20040810">
        <derived-from template="concept"/>
        <name>Encryption</name>
        <desc><topicref TID="encryption"/> is the process of transforming a cleartext into a cyphertext. The reverse process is called <topicref TID="decryption"/>.</desc>
    </topic>
    <topic domain="core" TID="decryption" crdate="20040810">
        <derived-from template="concept"/>
        <name>Decryption</name>
        <desc><topicref TID="decryption"/> is the process of transforming a cyphertext into a cleartext. The reverse process is called <topicref TID="encryption"/>.</desc>
    </topic>
    <topic domain="core" TID="authentication" crdate="20040802">
        <derived-from template="concept"/>
        <name>Authentication</name>
        <desc><topicref TID="authentication"/> is the process of verifying the authenticity of the claimed identity of a peer, often through mechanisms such as passwords. After successful <topicref TID="authentication"/>, <topicref TID="authorization"/> methods are often used to grant or deny certain rights to the peer.</desc>
    </topic>
    <topic domain="core" TID="authorization" crdate="20040802">
        <derived-from template="concept"/>
        <name>Authorization</name>
        <desc><topicref TID="authorization"/> is the process of controlling whether the identity of a peer (often verified through an <topicref TID="authentication"/> procedure) is authorized to perform a requested operation.</desc>
    </topic>
    <topic domain="core" TID="clientserver" crdate="20010313">
        <derived-from template="concept"/>
        <name>Client/Server-Model</name>
        <desc>The <topicref TID="clientserver"/> is a base topic for topics describing models of interacting <topicref TID="client"/>s and <topicref TID="server"/>s. In the <topicref TID="clientserver"/>, a <topicref TID="server"/> waits for requests from <topicref TID="client"/>s, and after receiving such a request, the <topicref TID="server"/> processes it and send a response. The communication between the two peers is based on a <topicref TID="protocol"/>, which is defining the possible interaction patterns and the information being exchanged.</desc>
    </topic>
    <topic domain="core" TID="client" crdate="20010303">
        <derived-from template="technology"/>
        <name>Client</name>
        <desc>The <topicref TID="client"/> is a base topic for topics describing clients. A <topicref TID="client"/> is one component in the <topicref TID="clientserver"/> and contacts a <topicref TID="server"/> for requesting a service of some kind.</desc>
    </topic>
    <topic domain="core" TID="httpclient" crdate="20010303">
        <derived-from template="client"/>
        <name>HTTP Client</name>
        <desc>The <topicref TID="httpclient"/> is a base topic for topics describing clients implementing <topicref TID="http"/>. An <topicref TID="httpclient"/> communicates with an <topicref TID="httpserver"/>.</desc>
    </topic>
    <topic domain="core" TID="searchengine" crdate="20010313">
        <derived-from template="httpclient"/>
        <name>Search Engine</name>
        <desc>The <topicref TID="searchengine"/> is a base topic for topics describing programs which are crawling the <topicref TID="www"/> for collecting and indexing resources. A <topicref TID="searchengine"/> typically interprets <topicref TID="html"/> pages, but an increasing number of <topicref TID="searchengine"/>s also interprets other resources, such as <topicref TID="pdf"/> documents.</desc>
    </topic>
    <topic domain="core" TID="xmlprocessor" crdate="20020605">
        <derived-from template="parser"/>
        <name>XML Processor</name>
        <alias>XML Parser</alias>
        <desc>An <topicref TID="xmlprocessor"/> is a base topic for topics describing programs which are <topicref TID="xml"/> processors. These may be non-validating or validating <topicref TID="xml"/> processors (validating an <topicref TID="xml"/> document against its <topicref TID="dtd"/>), or they may support another <topicref TID="xmlschemalanguage"/>, such as <topicref TID="xsd"/>.</desc>
    </topic>
    <topic domain="core" TID="xincludeprocessor" crdate="20070309">
        <derived-from template="concept"/>
        <name>XInclude Processor</name>
        <desc>An <topicref TID="xincludeprocessor"/> is a base topic for topics describing programs which are <topicref TID="xinclude"/> processors. Basically, an <topicref TID="xincludeprocessor"/> is a program locating and replacing <topicref TID="xinclude"/> markup in an <topicref TID="xml"/> document.</desc>
    </topic>
    <topic domain="core" TID="xsltprocessor" crdate="20020605">
        <derived-from template="concept"/>
        <name>XSLT Processor</name>
        <desc>An <topicref TID="xsltprocessor"/> is a base topic for topics describing programs which are <topicref TID="xslt"/> processors. Basically, an <topicref TID="xsltprocessor"/> is a program interpreting and executing <topicref TID="xslt"/> programs.</desc>
    </topic>
    <topic domain="core" TID="browser" crdate="20010303">
        <derived-from template="httpclient"/>
        <derived-from template="ui"/>
        <name>Browser</name>
        <desc>The <topicref TID="browser"/> is a base topic for topics describing programs which are a <topicref TID="httpclient"/> and provide a <topicref TID="ui"/> for browsing through the <topicref TID="www"/>. A <topicref TID="browser"/> communicates with an <topicref TID="httpserver"/>.</desc>
    </topic>
    <topic domain="core" TID="ftpclient" crdate="20010303">
        <derived-from template="client"/>
        <name>FTP Client</name>
        <desc>The <topicref TID="ftpclient"/> is a base topic for topics describing clients implementing <topicref TID="ftp"/>. A <topicref TID="ftpclient"/> communicates with a <topicref TID="ftpserver"/>.</desc>
    </topic>
    <topic domain="core" TID="server" crdate="20010303">
        <derived-from template="technology"/>
        <name>Server</name>
        <desc>The <topicref TID="server"/> is a base topic for topics describing servers. A <topicref TID="server"/> is one component in the <topicref TID="clientserver"/> and is contacted by a <topicref TID="client"/> for providing a service of some kind.</desc>
    </topic>
    <topic domain="core" TID="httpserver" crdate="20010303">
        <derived-from template="server"/>
        <name>HTTP Server</name>
        <alias>Web Server</alias>
        <desc>The <topicref TID="httpserver"/> is a base topic for topics describing servers implementing <topicref TID="http"/> (a.k.a. <topicref TID="www"/> servers or Web servers). An <topicref TID="httpserver"/> communicates with an <topicref TID="httpclient"/>.</desc>
    </topic>
    <topic domain="core" TID="ftpserver" crdate="20010303">
        <derived-from template="server"/>
        <name>FTP Server</name>
        <desc>The <topicref TID="ftpserver"/> is a base topic for topics describing servers implementing <topicref TID="ftp"/>. A <topicref TID="ftpserver"/> communicates with a <topicref TID="ftpclient"/>.</desc>
    </topic>
    <topic domain="core" TID="os" crdate="20010305">
        <derived-from template="technology"/>
        <name>Operating System</name>
        <desc>The <topicref TID="os"/> is a base topic for topics describing operating systems.</desc>
    </topic>
    <topic domain="core" TID="runtime" crdate="20070807">
        <derived-from template="technology"/>
        <name>Runtime</name>
        <desc>The <topicref TID="runtime"/> is a base topic for topics describing runtime environments.</desc>
    </topic>
    <topic domain="core" TID="riaruntime" crdate="20070807">
        <derived-from template="technology"/>
        <name>RIA Runtime</name>
        <desc>The <topicref TID="riaruntime"/> is a base topic for topics describing <topicref TID="runtime"/> environments for <topicref TID="ria"/>s.</desc>
    </topic>
    <topic domain="core" TID="fs" crdate="20001220">
        <derived-from template="technology"/>
        <name>File System</name>
        <desc>The <topicref TID="fs"/> is a base topic for topics describing systems for the structured storage of individual files.</desc>
    </topic>
    <topic domain="core" TID="lfs" crdate="20010305">
        <derived-from template="fs"/>
        <derived-from template="dataformat"/>
        <name>Local File System</name>
        <desc>The <topicref TID="lfs"/> is a base topic for topics describing local file systems.</desc>
    </topic>
    <topic domain="core" TID="dfs" crdate="20010305">
        <derived-from template="fs"/>
        <derived-from template="protocol"/>
        <name>Distributed File System</name>
        <desc>The <topicref TID="dfs"/> is a base topic for topics describing distributed file systems.</desc>
    </topic>
    <topic domain="core" TID="compression" modate="20040714" crdate="20010119">
        <derived-from template="algorithm"/>
        <derived-from template="dataformat"/>
        <name>Compression</name>
        <desc>The <topicref TID="compression"/> is a base topic for topics describing a <topicref TID="dataformat"/> and/or an <topicref TID="algorithm"/> for compressed data.</desc>
    </topic>
    <topic domain="core" TID="imagecompression" crdate="20010311">
        <derived-from template="compression"/>
        <name>Image Compression</name>
        <desc>The <topicref TID="imagecompression"/> is a base topic for topics describing a defined way of compressing images.</desc>
    </topic>
    <topic domain="core" TID="audiocompression" crdate="20010311">
        <derived-from template="compression"/>
        <name>Audio Compression</name>
        <desc>The <topicref TID="audiocompression"/> is a base topic for topics describing a defined way of compressing audio.</desc>
    </topic>
    <topic domain="core" TID="videocompression" crdate="20010311">
        <derived-from template="compression"/>
        <name>Video Compression</name>
        <desc>The <topicref TID="videocompression"/> is a base topic for topics describing a defined way of compressing video streams.</desc>
    </topic>
    <topic domain="core" TID="dataformat" crdate="20010119">
        <derived-from template="technology"/>
        <name>Data Format</name>
        <desc>The <topicref TID="dataformat"/> is a base topic for topics describing a defined way of coding information adhering to some <topicref TID="datamodel"/> for storage or transfer.</desc>
    </topic>
    <topic domain="core" TID="audioformat" crdate="20010216">
        <derived-from template="dataformat"/>
        <name>Audio Format</name>
        <desc>The <topicref TID="audioformat"/> is a base topic for topics describing a defined way of coding information for storage or transfer of audio.</desc>
    </topic>
    <topic domain="core" TID="fontformat" crdate="20010317">
        <derived-from template="dataformat"/>
        <name>Font Format</name>
        <desc>The <topicref TID="fontformat"/> is a base topic for topics describing a defined way of coding information for describing fonts (i.e., collections of glyphs for displaying characters).</desc>
    </topic>
    <topic domain="core" TID="videoformat" crdate="20010216">
        <derived-from template="dataformat"/>
        <name>Video Format</name>
        <desc>The <topicref TID="videoformat"/> is a base topic for topics describing a defined way of coding information for storage or transfer of moving images.</desc>
    </topic>
    <topic domain="core" TID="graphicsformat" crdate="20010216">
        <derived-from template="dataformat"/>
        <name>Graphics Format</name>
        <desc>The <topicref TID="graphicsformat"/> is a base topic for topics describing a defined way of coding information for storage or transfer of graphics.</desc>
    </topic>
    <topic domain="core" TID="compressionformat" crdate="20061206">
        <derived-from template="dataformat"/>
        <name>Compression Format</name>
        <desc>The <topicref TID="compressionformat"/> is a base topic for topics describing a way of storing compressed data.</desc>
    </topic>
    <topic domain="core" TID="xmlcompressionformat" crdate="20030521">
        <derived-from template="dataformat"/>
        <name>XML Compression Format</name>
        <desc>The <topicref TID="xmlcompressionformat"/> is a base topic for topics describing a way of storing compressed XML documents.</desc>
    </topic>
    <topic domain="core" TID="imageformat" crdate="20010216">
        <derived-from template="dataformat"/>
        <name>Image Format</name>
        <desc>The <topicref TID="imageformat"/> is a base topic for topics describing a defined way of coding information for storage or transfer of images.</desc>
    </topic>
    <topic domain="core" TID="textformat" crdate="20010216">
        <derived-from template="dataformat"/>
        <name>Text Format</name>
        <desc>The <topicref TID="textformat"/> is a base topic for topics describing a defined way of coding information for storage or transfer of text.</desc>
    </topic>
    <topic domain="core" TID="stylesheetlanguage" crdate="20010220">
        <derived-from template="metadata"/>
        <name>Style Sheet Language</name>
        <desc>The <topicref TID="stylesheetlanguage"/> is a base topic for topics describing a way of specifying style sheets for documents. A style sheet is used to control the presentation of a document. A <topicref TID="stylesheetlanguage"/> can be regarded as <topicref TID="metadata"/> because it specifies the presentation aspects of an information resource, hence it specifies data about data.</desc>
    </topic>
    <topic domain="core" TID="hypermediaformat" crdate="20010216">
        <derived-from template="dataformat"/>
        <name>Hypermedia Format</name>
        <desc>The <topicref TID="hypermediaformat"/> is a base topic for topics describing a defined way of coding information for storage or transfer of hypermedia (usually used in a <topicref TID="hmsystem"/>).</desc>
    </topic>
    <topic domain="core" TID="hypertextformat" crdate="20010216">
        <derived-from template="hypermediaformat"/>
        <name>Hypertext Format</name>
        <desc>The <topicref TID="hypertextformat"/> is a base topic for topics describing a defined way of coding information for storage or transfer of hypertext (which is a special form of a <topicref TID="hypermediaformat"/> restricted to textual information).</desc>
    </topic>
    <topic domain="core" TID="concept" crdate="20010119">
        <derived-from template="achievement"/>
        <name>Concept</name>
        <desc>The <topicref TID="concept"/> is a base topic for topics describing an abstract concept.</desc>
    </topic>
    <topic domain="core" TID="datamodel" crdate="20060305">
        <derived-from template="technology"/>
        <name>Data Model</name>
        <desc>A <topicref TID="datamodel"/> is a base topic for topics describing a domain of data and operations on this data.</desc>
    </topic>
    <topic domain="core" TID="modelinglanguage" crdate="20030712">
        <derived-from template="technology"/>
        <name>Modeling Language</name>
        <desc>A <topicref TID="modelinglanguage"/> is a base topic for topics describing a language for modeling, such as data modeling (in which case there is an underlying implicit or explicit <topicref TID="datamodel"/>) or the modeling of systems based on <topicref TID="oo"/>.</desc>
    </topic>
    <topic domain="core" TID="compiler" crdate="20060509">
        <derived-from template="concept"/>
        <name>Compiler</name>
        <desc>A <topicref TID="compiler"/> is a program for translating code from one language into another. In many cases, the first language is a high-level <topicref TID="programminglanguage"/> and the second is a processor-specific machine language. However, there are other possibilities such as <topicref TID="java"/>, which is compiled into machine-independent byte code (which is then executed by a <topicref TID="jvm"/>), or <topicref TID="yacc"/>, which generates <topicref TID="programminglanguage"/> code from a <topicref TID="grammar"/>.</desc>
    </topic>
    <topic domain="core" TID="programminglanguage" crdate="20010220">
        <derived-from template="technology"/>
        <name>Programming Language</name>
        <desc>A <topicref TID="programminglanguage"/> is a base topic for topics describing a language for writing executable programs.</desc>
    </topic>
    <topic domain="wwww" TID="dml" crdate="20031116">
        <derived-from template="concept"/>
        <name>DML</name>
        <alias>Data Manipulation Language</alias>
        <desc>A <topicref TID="dml"/> is a base topic for topics describing a language for manipulating (i.e., inserting, updating, deleting) structured data. This data may have been defined using a <topicref TID="ddl"/> and queried using a <topicref TID="querylanguage"/>.</desc>
    </topic>
    <topic domain="wwww" TID="ddl" crdate="20031116">
        <derived-from template="concept"/>
        <name>DDL</name>
        <alias>Data Definition Language</alias>
        <desc>A <topicref TID="ddl"/> is a base topic for topics describing a language for defining structures for structured data. This data may be manipulated using a <topicref TID="dml"/> and queried using a <topicref TID="querylanguage"/>.</desc>
    </topic>
    <topic domain="wwww" TID="querylanguage" modate="20031116" crdate="20010311">
        <derived-from template="concept"/>
        <name>Query Language</name>
        <desc>A <topicref TID="querylanguage"/> is a base topic for topics describing a language for formulating queries for a given <topicref TID="dataformat"/>. This data may have been defined using a <topicref TID="ddl"/> and manipulated using a <topicref TID="querylanguage"/>.</desc>
    </topic>
    <topic domain="core" TID="schemalanguage" crdate="20070424">
        <derived-from template="ddl"/>
        <name>Schema Language</name>
        <desc>A schema language describes a set of contraints for a given <topicref TID="dataformat"/>, in most cases this refers to some kind of markup-based format.</desc>
    </topic>
    <topic domain="core" TID="xmlschemalanguage" crdate="20010321" modate="20070424">
        <derived-from template="schemalanguage"/>
        <name>XML Schema Language</name>
        <desc>An <topicref TID="xmlschemalanguage"/> is a method for specifying a <topicref TID="grammar"/> or rules for a class of <topicref TID="xml"/> documents. Even though the <topicref TID="xml"/> standard itself already contains such an <topicref TID="xmlschemalanguage"/> (the <topicref TID="dtd"/>), this <topicref TID="xmlschemalanguage"/> has a number of shortcomings, most notably no type derivation, and almost no support for data types. Consequently, a number of <topicref TID="xmlschemalanguage"/>s have been proposed, which aim at providing a more powerful language for specifying <topicref TID="grammar"/>s for <topicref TID="xml"/> documents. <topicref TID="w3c"/>'s <topicref TID="xsd"/> is the most promising prospect for becoming the <topicref TID="xmlschemalanguage"/> to replace <topicref TID="dtd"/>s.</desc>
    </topic>
    <topic domain="core" TID="multiplex" crdate="20010328">
        <derived-from template="concept"/>
        <name>Multiplexing Method</name>
    </topic>
    <topic domain="core" TID="algorithm" crdate="20040714">
        <derived-from template="concept"/>
        <name>Algorithm</name>
    </topic>
    <topic domain="core" TID="chf" crdate="20010309">
        <derived-from template="hash"/>
        <name>Cryptographic Hash Function</name>
        <desc>A <topicref TID="chf"/> is a <topicref TID="hash"/> satisfying additional criteria. The main difference between a regular <topicref TID="hash"/> and a <topicref TID="chf"/> is that a <topicref TID="chf"/> generates values in a way that makes it extremely difficult to generate a message that would hash to a given hash value.</desc>
    </topic>
    <topic domain="core" TID="hash" crdate="20010309">
        <derived-from template="algorithm"/>
        <name>Hash Function</name>
    </topic>
    <topic domain="core" TID="certsystem" crdate="20000618">
        <derived-from template="concept"/>
        <name>Certification System</name>
    </topic>
    <topic domain="core" TID="cryptography" crdate="20020716">
        <derived-from template="algorithm"/>
        <name>Cryptography</name>
    </topic>
    <topic domain="core" TID="pkc" modate="20020716" crdate="20000618">
        <derived-from template="cryptography"/>
        <name>Public-Key Cryptography</name>
        <alias>Asymmetric Cryptography</alias>
        <desc><topicref TID="pkc"/> is a <topicref TID="cryptography"/> method where different keys are used for <topicref TID="encryption"/> and <topicref TID="decryption"/>. This is a major advantage over <topicref TID="skc"/> and makes <topicref TID="pkc"/> ideally suited for scenarios where secure key exchange is hard or impossible. The disadvantage of <topicref TID="pkc"/> is that all known <topicref TID="algorithm"/>s are very computing-intensive.</desc>
    </topic>
    <topic domain="core" TID="skc" modate="20020716" crdate="20000618">
        <derived-from template="cryptography"/>
        <name>Secret-Key Cryptography</name>
        <alias>Symmetric Cryptography</alias>
        <desc><topicref TID="skc"/> is a <topicref TID="cryptography"/> method where the same key is used for <topicref TID="encryption"/> and <topicref TID="decryption"/>. This leaves applications with the problem of how to securely exchange this key. This inherent problem of <topicref TID="skc"/> has been solved by <topicref TID="pkc"/> methods.</desc>
    </topic>
    <topic domain="core" TID="hwinterface" crdate="20010315">
        <derived-from template="interface"/>
        <name>Hardware Interface</name>
        <desc>The <topicref TID="hwinterface"/> is a base topic for topics describing an <topicref TID="interface"/> on the hardware level. This generally includes connectors (except for <topicref TID="wlinterface"/>s) and physical transmission details, such as voltage and timing of signals.</desc>
    </topic>
    <topic domain="core" TID="interface" crdate="20010313">
        <derived-from template="concept"/>
        <name>Interface</name>
        <desc>The <topicref TID="interface"/> is a base topic for topics describing an <topicref TID="interface"/>, which is a clear separation between different entities.</desc>
    </topic>
    <topic domain="core" TID="wlinterface" crdate="20010314">
        <derived-from template="hwinterface"/>
        <name>Wireless Interface</name>
        <desc>The <topicref TID="wlinterface"/> is a base topic for topics describing ways for transmitting data between devices using wireless techniques.</desc>
    </topic>
    <topic domain="core" TID="network" crdate="20010309">
        <derived-from template="concept"/>
        <name>Network</name>
        <desc>The <topicref TID="network"/> is a base topic for topics describing networks for transmitting signals.</desc>
    </topic>
    <topic domain="core" TID="tnetwork" crdate="20010315">
        <derived-from template="network"/>
        <name>Telephony Network</name>
        <desc>The <topicref TID="tnetwork"/> is a base topic for topics describing networks for telephony.</desc>
    </topic>
    <topic domain="core" TID="protocol" crdate="20010119">
        <derived-from template="interface"/>
        <name>Protocol</name>
        <desc>The <topicref TID="protocol"/> is a base topic for topics describing a defined way of transferring data between distributed peers. Essentially, a <topicref TID="protocol"/> defines an <topicref TID="interface"/> for distributed scenarios. In a way, a <topicref TID="protocol"/> can be regarded as the distributed equivalent of a <topicref TID="api"/>, because it is used for the same purposes and defines the same things (the possible interactions between components, and the data that is exchanged while interacting).</desc>
    </topic>
    <topic domain="core" TID="modprotocol" crdate="20010315">
        <derived-from template="protocol"/>
        <name>Modulation Protocol</name>
        <desc>The <topicref TID="modprotocol"/> is a base topic for topics describing protocols for modulating and demodulating digital signals over analog connections.</desc>
    </topic>
    <topic domain="core" TID="routingprotocol" crdate="20010305">
        <derived-from template="protocol"/>
        <name>Routing Protocol</name>
        <desc>The <topicref TID="routingprotocol"/> is a base topic for topics describing protocols for facilitating routing within computer networks.</desc>
    </topic>
    <topic domain="core" TID="emailprotocol" crdate="20010312">
        <derived-from template="protocol"/>
        <name>Email Protocol</name>
        <desc>The <topicref TID="emailprotocol"/> is a base topic for topics describing protocols for implementing <topicref TID="email"/> services.</desc>
    </topic>
    <topic domain="core" TID="resprotocol" crdate="20010309">
        <derived-from template="protocol"/>
        <name>Resolution Protocol</name>
        <desc>The <topicref TID="resprotocol"/> is a base topic for topics describing protocols for resolution purposes.</desc>
    </topic>
    <topic domain="core" TID="product" crdate="20010119">
        <derived-from template="achievement"/>
        <name>Product</name>
        <desc>The <topicref TID="product"/> is a base topic for topics describing a piece of software or hardware.</desc>
    </topic>
    <topic domain="core" TID="body" crdate="20010119">
        <derived-from template="topic"/>
        <name>Body</name>
        <desc>The <topicref TID="body"/> is a base topic for topics describing a single person or a body consisting of several persons.</desc>
    </topic>
    <topic domain="core" TID="nationalorganization" crdate="20010119">
        <derived-from template="organization"/>
        <name>National Organization</name>
        <desc>The <topicref TID="nationalorganization"/> is a base topic for topics describing a single governmentally influenced <topicref TID="organization"/>.</desc>
    </topic>
    <topic domain="core" TID="consortium" crdate="20010119">
        <derived-from template="organization"/>
        <name>Consortium</name>
        <desc>The <topicref TID="consortium"/> is a base topic for topics describing an organization consisting of other organizations, usually companies.</desc>
    </topic>
    <topic domain="core" TID="organization" crdate="20010119">
        <derived-from template="group"/>
        <name>Organization</name>
        <desc>The <topicref TID="organization"/> is a base topic for topics describing a organized group of bodies.</desc>
    </topic>
    <topic domain="core" TID="group" crdate="20010119">
        <derived-from template="body"/>
        <name>Group</name>
        <desc>The <topicref TID="group"/> is a base topic for topics describing a group of bodies.</desc>
    </topic>
    <topic domain="core" TID="email" crdate="20010312">
        <derived-from template="concept"/>
        <name>Email</name>
        <alias>Electronic Mail</alias>
    </topic>
    <topic domain="core" TID="hmsystem" crdate="20010216">
        <derived-from template="technology"/>
        <name>Hypermedia System</name>
        <desc>A <topicref TID="hmsystem"/> is an application which uses associative relationships amongst information contained within multiple media data for the purpose of facilitating access to, and manipulation of, the information encapsulated by the data.</desc>
    </topic>
    <topic domain="core" TID="bibliographicmetadata" crdate="20040219">
        <derived-from template="metadata"/>
        <name>Bibliographic Meta Data</name>
        <desc><topicref TID="bibliographicmetadata"/> is <topicref TID="metadata"/> about bibliographic data, in most cases about resources commonly found in libraries.</desc>
    </topic>
    <topic domain="core" TID="metadata" crdate="20010311">
        <derived-from template="concept"/>
        <name>Meta Data</name>
        <desc><topicref TID="metadata"/> is data about data. Since the term "data" is general in the sense that it may also be <topicref TID="metadata"/>, there is no such thing as "meta meta data". <topicref TID="rdf"/> is an attempt to define a general and machine understandable format for <topicref TID="www"/> <topicref TID="metadata"/>. The benefits of machine understandable <topicref TID="metadata"/> are more powerful ways of information search, retrieval, and processing.</desc>
    </topic>
    <topic domain="core" TID="graph" crdate="20060120">
        <derived-from template="concept"/>
        <name>Graph</name>
    </topic>
    <topic domain="wwww" TID="tree" crdate="20060120">
        <derived-from template="graph"/>
        <name>Tree</name>
        <desc>A <topicref TID="tree"/> is a <topicref TID="graph"/> in which any two vertices are connected by exactly one path. More colloquially, a <topicref TID="tree"/> is a <topicref TID="graph"/> which has exactly one root node, and every node has zero or more child nodes.</desc>
    </topic>
    <topic domain="wwww" TID="dag" crdate="20060120">
        <derived-from template="graph"/>
        <name>DAG</name>
        <alias>Directed Acyclic Graph</alias>
        <desc>A <topicref TID="dag"/> is a directed <topicref TID="graph"/> with no directed cycles. This means there is no vertex in the <topicref TID="dag"/> which is the start and the end of a directed cycle.</desc>
    </topic>
    <topic domain="wwww" TID="goddag" crdate="20060120">
        <derived-from template="dag"/>
        <name>GODDAG</name>
        <alias>General Ordered-Descendant DAG</alias>
    </topic>
    <topic domain="wwww" TID="iscii" crdate="20020822">
        <derived-from template="characterset"/>
        <name>ISCII</name>
        <alias>Indian Standard Code for Information Interchange</alias>
    </topic>
    <topic domain="wwww" TID="ascii" crdate="20000608">
        <derived-from template="characterset"/>
        <name>ASCII</name>
        <alias>American National Standard Code for Information Interchange</alias>
        <desc><topicref TID="ascii"/> specifies the coding of space and a set of 94 characters (letters, digits and punctuation or mathematical symbols) suitable for the interchange of english language documents. <topicref TID="ascii"/> forms the basis for most computer code sets and is the american national version of ISO 646.</desc>
    </topic>
    <topic domain="wwww" TID="ebcdic" crdate="20000626">
        <derived-from template="characterset"/>
        <name>EBCDIC</name>
        <alias>Extended Binary-Coded Decimal Interchange Code</alias>
    </topic>
    <topic domain="wwww" TID="nun" crdate="20030110">
        <derived-from template="identifier"/>
        <name>NUN</name>
        <alias>Normalized Universal Name</alias>
        <desc>A <topicref TID="nun"/> is a name that uniquely identifies an element, attribute, simple type, complex type, attribute group, model group, or notation declaration in an <topicref TID="xsd"/>.</desc>
    </topic>
    <topic domain="wwww" TID="fpi" crdate="20050923">
        <derived-from template="identifier"/>
        <name>FPI</name>
        <alias>Formal Public Identifier</alias>
    </topic>
    <topic domain="wwww" TID="uci" crdate="20051030">
        <derived-from template="identifier"/>
        <name>UCI</name>
        <alias>Universal Content Identifier</alias>
    </topic>
    <topic domain="wwww" TID="clei" crdate="20051030">
        <derived-from template="identifier"/>
        <name>CLEI</name>
        <alias>Common Language Equipment Identifier</alias>
    </topic>
    <topic domain="wwww" TID="uuid" crdate="20051030">
        <derived-from template="identifier"/>
        <name>UUID</name>
        <alias>Universally Unique Identifier</alias>
    </topic>
    <topic domain="wwww" TID="curie" crdate="20070308">
        <derived-from template="identifier"/>
        <name>CURIE</name>
        <alias>Compact URI</alias>
    </topic>
    <topic domain="wwww" TID="uri" crdate="20000607">
        <derived-from template="identifier"/>
        <name>URI</name>
        <alias>Uniform Resource Identifier</alias>
        <desc>The <topicref TID="www"/> is considered to include objects accessed using an extendable number of <topicref TID="protocol"/>s, existing, invented for the <topicref TID="www"/> itself, or to be invented in the future. Access instructions for an individual object under a given <topicref TID="protocol"/> are encoded into forms of address string. Other <topicref TID="protocol"/>s allow the use of object names of various forms. In order to abstract the idea of a generic object, the <topicref TID="www"/> needs the concepts of the universal set of objects, and of the universal set of names or addresses of objects. A <topicref TID="uri"/> is a member of this universal set of names in registered name spaces and addresses referring to registered <topicref TID="protocol"/>s or name spaces. A <topicref TID="url"/> is a form of <topicref TID="uri"/> which expresses an address mapping onto an access <topicref TID="algorithm"/> using network <topicref TID="protocol"/>s. A <topicref TID="urn"/> is a form of <topicref TID="uri"/> which uses a name space (and associated <topicref TID="resprotocol"/>s) for persistent object names.</desc>
    </topic>
    <topic domain="wwww" TID="unc" crdate="20020718">
        <derived-from template="identifier"/>
        <name>UNC</name>
        <alias>Universal Naming Convention</alias>
        <desc><topicref TID="unc"/> provides a naming convention for identifying network resources. <topicref TID="unc"/> identifiers consist of three parts, a server name, a share name, and an optional file path, that are combined using backslashes or slashes. <topicref TID="unc"/> notation is used primarily for mapping network drives in the <topicref TID="windows"/> family of <topicref TID="os"/>s, although support for <topicref TID="unc"/> appears in related technologies like <topicref TID="smb"/>/<topicref TID="cifs"/>. <topicref TID="unc"/> names are most commonly used to reach file servers or printers on a <topicref TID="lan"/>.</desc>
    </topic>
    <topic domain="wwww" TID="iuri" crdate="20020717">
        <derived-from template="identifier"/>
        <name>IURI</name>
        <alias>Internationalized URI</alias>
        <status>The work on <topicref TID="i18n"/> of <topicref TID="uri"/>s started under the label of <topicref TID="iuri"/>, but is now being continued under the new name of <topicref TID="iri"/>.</status>
    </topic>
    <topic domain="wwww" TID="iri" crdate="20010628">
        <derived-from template="identifier"/>
        <name>IRI</name>
        <alias>Internationalized Resource Identifier</alias>
        <desc>An <topicref TID="iri"/> is a generalized form of <topicref TID="uri"/> that may contain non-<topicref TID="ascii"/> characters.</desc>
    </topic>
    <topic domain="wwww" TID="leiri" crdate="20080122">
        <derived-from template="identifier"/>
        <name>LEIRI</name>
        <alias>Legacy Extended IRI</alias>
    </topic>
    <topic domain="wwww" TID="hrri" crdate="20070430">
        <derived-from template="identifier"/>
        <name>HRRI</name>
        <alias>Human Readable Resource Identifier</alias>
        <desc><topicref TID="hrri"/>s are strings which are interpreted as <topicref TID="iri"/>s, but which allow the use of characters which must be escaped in a legal <topicref TID="iri"/>, such as delimiters and a few other <topicref TID="ascii"/> characters.</desc>
    </topic>
    <topic domain="wwww" TID="xri" crdate="20030211">
        <derived-from template="identifier"/>
        <name>XRI</name>
        <alias>Extensible Resource Identifier</alias>
    </topic>
    <topic domain="wwww" TID="e164" crdate="20050218">
        <derived-from template="identifier"/>
        <name>E.164</name>
        <desc><topicref TID="e164"/> is <topicref TID="itu"/>'s official standard of how numbers to be used in the <topicref TID="pstn"/> are structured, and what functionality is associated with that structure.</desc>
    </topic>
    <topic domain="wwww" TID="urn" crdate="20000608">
        <derived-from template="uri"/>
        <name>URN</name>
        <alias>Uniform Resource Name</alias>
        <desc>A <topicref TID="urn"/> is a persistent, globally unique name assigned to an object. In contrast to a <topicref TID="url"/>, which changes whenever the location of an object changes, a <topicref TID="urn"/> has no location dependence and therefore a longer lifetime. This is realized by using a naming service which in most cases will provide a mapping from URNs to URLs. Thus, even if the <topicref TID="url"/> of an object changes, its <topicref TID="urn"/> remains the same, since only the object's entry in the naming service has to be updated.</desc>
    </topic>
    <topic domain="wwww" TID="webdav" crdate="20000608">
        <derived-from template="protocol"/>
        <name>WebDAV</name>
        <alias>WWW Distributed Authoring and Versioning</alias>
        <desc><topicref TID="webdav"/> defines extensions to <topicref TID="http"/> to enable distributed <topicref TID="www"/> authoring tools to be broadly interoperable. <topicref TID="http"/> already contains functionality which enables the editing of <topicref TID="www"/> content at a remote location, without direct access to the storage media via an <topicref TID="os"/>. This capability is exploited by several existing <topicref TID="html"/> distributed authoring tools, and by a growing number of mainstream applications (e.g., word processors) which allow users to write (publish) their work to an <topicref TID="httpserver"/>. Experience from the <topicref TID="html"/> authoring tools has shown they are unable to meet their user's needs using the facilities of <topicref TID="http"/>. The consequence of this is either postponed introduction of distributed authoring capability, or the addition of nonstandard extensions to <topicref TID="http"/>. These extensions, developed in isolation, are not interoperable.</desc>
    </topic>
    <topic domain="wwww" TID="caldav" crdate="20081204">
        <derived-from template="protocol"/>
        <name>CalDAV</name>
        <alias>Calendar Distributed Authoring and Versioning</alias>
    </topic>
    <topic domain="wwww" TID="ecml" crdate="20000616">
        <derived-from template="dataformat"/>
        <name>ECML</name>
        <alias>Electronic Commerce Markup Language</alias>
        <desc><topicref TID="ecml"/> provides a set of simple guidelines for <topicref TID="www"/> merchants that will enable electronic wallets from multiple vendors to fill in their <topicref TID="htmlforms"/>. <topicref TID="ecml"/> defines a number of simple field types for <topicref TID="b2c"/> scenarios, which should be used by <topicref TID="htmlforms"/> for naming fields. Using these standardized fields, mechanisms on the <topicref TID="browser"/> side (such as electronic wallets) can automatically identify and fill out forms for the user, making transactions for the user more easy.</desc>
    </topic>
    <topic domain="wwww" TID="kml" crdate="20061204">
        <derived-from template="dataformat"/>
        <name>KML</name>
        <alias>Keyhole Markup Language</alias>
    </topic>
    <topic domain="wwww" TID="ucs2" crdate="20001220">
        <derived-from template="ces"/>
        <name>UCS-2</name>
    </topic>
    <topic domain="wwww" TID="ucs2e" crdate="20001220">
        <derived-from template="ces"/>
        <name>UCS-2E</name>
        <alias>Extended UCS-2</alias>
    </topic>
    <topic domain="wwww" TID="ucs4" crdate="20001220">
        <derived-from template="ces"/>
        <name>UCS-4</name>
    </topic>
    <topic domain="wwww" TID="oil" crdate="20001220">
        <derived-from template="technology"/>
        <name>OIL</name>
        <alias>Ontology Inference Layer</alias>
    </topic>
    <topic domain="wwww" TID="csv" crdate="20051030">
        <derived-from template="dataformat"/>
        <name>CSV</name>
        <alias>Comma-Separated Values</alias>
        <desc>The <topicref TID="csv"/> <topicref TID="dataformat"/> is the least common denominator for exchanging structured information. It is a simple text-based format, where values are separated by commas, and individual records are encoded on individual lines. Quotes may be used to enclose the values (but they must not be used). Each line contains the same number of values.</desc>
    </topic>
    <topic domain="wwww" TID="json" crdate="20050620">
        <derived-from template="dataformat"/>
        <name>JSON</name>
        <alias>JavaScript Object Notation</alias>
    </topic>
    <topic domain="wwww" TID="iwml" crdate="20050608">
        <derived-from template="dataformat"/>
        <name>IWML</name>
        <alias>InterWiki Markup Language</alias>
    </topic>
    <topic domain="wwww" TID="earl" crdate="20030116">
        <derived-from template="dataformat"/>
        <name>EARL</name>
        <alias>Evaluation and Report Language</alias>
    </topic>
    <topic domain="wwww" TID="daml" crdate="20001220">
        <derived-from template="dataformat"/>
        <name>DAML</name>
        <alias>DARPA Agent Markup Language</alias>
    </topic>
    <topic domain="wwww" TID="upml" crdate="20040102">
        <derived-from template="dataformat"/>
        <name>UPML</name>
        <alias>Unified Problem-solving Method Description Language</alias>
    </topic>
    <topic domain="wwww" TID="damlont" crdate="20021005">
        <derived-from template="metadata"/>
        <name>DAML-ONT</name>
        <alias>DAML Ontology</alias>
    </topic>
    <topic domain="wwww" TID="owl" crdate="20040622">
        <derived-from template="dataformat"/>
        <name>OWL</name>
        <alias>Web Ontology Language</alias>
    </topic>
    <topic domain="wwww" TID="damloil" crdate="20021005">
        <derived-from template="dataformat"/>
        <name>DAML+OIL</name>
        <status><topicref TID="damloil"/> has been used as input for the <topicref TID="owl"/> language, which can be regarded as a revision of <topicref TID="damloil"/>.</status>
    </topic>
    <topic domain="wwww" TID="dcmi" crdate="20031130">
        <derived-from template="group"/>
        <name>DCMI</name>
        <alias>Dublin Core Metadata Initiative</alias>
    </topic>
    <topic domain="wwww" TID="mix" crdate="20041021">
        <derived-from template="metadata"/>
        <name>MIX</name>
        <alias>Metadata for Images in XML</alias>
    </topic>
    <topic domain="wwww" TID="mets" crdate="20040709">
        <derived-from template="bibliographicmetadata"/>
        <name>METS</name>
        <alias>Metadata Encoding and Transmission Standard</alias>
    </topic>
    <topic domain="wwww" TID="xobis" crdate="20040219">
        <derived-from template="bibliographicmetadata"/>
        <name>XOBIS</name>
        <alias>XML Organic Bibliographic Information Schema</alias>
    </topic>
    <topic domain="wwww" TID="mods" crdate="20040217">
        <derived-from template="bibliographicmetadata"/>
        <name>MODS</name>
        <alias>Metadata Object Description Schema</alias>
    </topic>
    <topic domain="wwww" TID="mads" crdate="20051030">
        <derived-from template="metadata"/>
        <name>MADS</name>
        <alias>Metadata Authority Description Schema</alias>
    </topic>
    <topic domain="wwww" TID="dublincore" crdate="20001220">
        <derived-from template="metadata"/>
        <name>Dublin Core</name>
        <desc>The <topicref TID="dublincore"/> is a <topicref TID="metadata"/> element set intended to facilitate discovery of electronic resources. Originally conceived for author-generated description of <topicref TID="www"/> resources, it has attracted the attention of formal resource description communities such as museums, libraries, government agencies, and commercial organizations. One example application of the <topicref TID="dublincore"/> elements is <topicref TID="oeb"/>.</desc>
    </topic>
    <topic domain="wwww" TID="shoe" crdate="20001220">
        <derived-from template="metadata"/>
        <name>SHOE</name>
        <alias>Simple HTML Ontology Extensions</alias>
        <desc><topicref TID="shoe"/> is an <topicref TID="xml"/>-based knowledge representation language, a superset of <topicref TID="html"/> which adds the tags necessary to embed arbitrary semantic data into <topicref TID="www"/> pages. <topicref TID="shoe"/> tags are divided into two categories. First, there are tags for constructing ontologies. <topicref TID="shoe"/> ontologies are sets of rules which define what kinds of assertions <topicref TID="shoe"/> documents can make and what these assertions mean. Secondly, there are tags for annotating <topicref TID="shoe"/> documents to subscribe to one or more ontologies, declare data entities, and make assertions about those entities under the rules prescribed by the ontologies.</desc>
    </topic>
    <topic domain="wwww" TID="dtmf" crdate="20001220">
        <derived-from template="technology"/>
        <name>DTMF</name>
        <alias>Dual-Tone Multifrequency</alias>
    </topic>
    <topic domain="wwww" TID="imode" crdate="20010214">
        <derived-from template="technology"/>
        <name>i-Mode</name>
    </topic>
    <topic domain="wwww" TID="chtml" crdate="20010214">
        <derived-from template="hypertextformat"/>
        <name>cHTML</name>
        <alias>Compact HTML</alias>
    </topic>
    <topic domain="wwww" TID="cifs" crdate="20001220">
        <derived-from template="dfs"/>
        <name>CIFS</name>
        <alias>Common Internet File System</alias>
    </topic>
    <topic domain="wwww" TID="isobmp" crdate="20010313">
        <derived-from template="ccs"/>
        <name>BMP</name>
        <alias>Basic Multilingual Plane</alias>
    </topic>
    <topic domain="wwww" TID="ucs" crdate="20000608">
        <derived-from template="ccs"/>
        <name>UCS</name>
        <alias>Universal Multiple-Octet Coded Character Set</alias>
        <desc><topicref TID="ucs"/> standardized in ISO 10646 integrates all previous internationally/nationally agreed character sets into a single code set. <topicref TID="ucs"/> is based on 4-octet (32-bit) coding scheme known as the "canonical form" (<topicref TID="ucs4"/>), but a 2-octet (16-bit) form (<topicref TID="ucs2"/>) is used for the <topicref TID="isobmp"/>, where octets 1 and 2 are assumed to be 00 00. The code set is split into 128 "groups" of "planes" containing 256 "rows" with 256 "cells" for characters. Each character is addressed using multiple octets, the third (in <topicref TID="ucs2"/> the first) of which identifies the row containing the character and the fourth (in <topicref TID="ucs2"/> the second) its cell number. The first 127 characters of the <topicref TID="isobmp"/> used for 16-bit code interchange are those of <topicref TID="ascii"/>. The characters forming the second half of the first row are those used in <topicref TID="iso88591"/>.</desc>
    </topic>
    <topic domain="wwww" TID="htmlforms" crdate="20000616">
        <derived-from template="technology"/>
        <name>HTML Forms</name>
    </topic>
    <topic domain="wwww" TID="faq" crdate="20010817">
        <derived-from template="concept"/>
        <name>FAQ</name>
        <alias>Frequently Asked Questions</alias>
        <desc><topicref TID="faq"/>s are collections of questions and answers that frequently occur for a specific subject. <topicref TID="faq"/> have a long tradition in <topicref TID="usenetnews"/> newsgroups, where they are periodically posted for bringing new subscribers up-to-date.</desc>
    </topic>
    <topic domain="wwww" TID="rfc" crdate="20000608">
        <derived-from template="concept"/>
        <name>RFC</name>
        <alias>Request For Comments</alias>
        <desc><topicref TID="rfc"/>s form a series of publications of networking technical documents, started in 1969 as part of the original <topicref TID="arpa"/> wide-area networking (<topicref TID="arpanet"/>) project. <topicref TID="rfc"/>s cover a wide range of topics, from early discussion of new research concepts to status memos about the <topicref TID="internet"/>. The <topicref TID="iab"/> views the <topicref TID="rfc"/> publication process to be sufficiently important to warrant including the <topicref TID="rfc"/> editor in the <topicref TID="iab"/> membership. The status of specifications on the <topicref TID="internet"/> standards track is summarized periodically in a summary <topicref TID="rfc"/> entitled "Internet Official Protocol Standards". This <topicref TID="rfc"/> shows the level of maturity and other helpful information for each <topicref TID="internet"/> <topicref TID="protocol"/> or service specification. The "Internet Official Protocol Standards" <topicref TID="rfc"/> is the authoritative statement of the status of any particular <topicref TID="internet"/> specification, and it is the "Publication of Record" with respect to <topicref TID="internet"/> standardization.</desc>
    </topic>
    <topic domain="wwww" TID="l10n" modate="20020717" crdate="20001221">
        <derived-from template="concept"/>
        <name>L10N</name>
        <alias>Localization</alias>
        <desc><topicref TID="l10n"/> is the process of adapting software for a specific region or language by adding locale-specific components and translating text. The abbreviation is based on the fact that the rather lengthy word 'localization' starts with a 'l' followed by 10 characters followed by an 'n'. Usually, the most time-consuming portion of <topicref TID="l10n"/> is the translation of text. Other types of data, such as sounds and images, may require <topicref TID="l10n"/> if they are culturally sensitive. The formatting of dates, numbers, and currencies also must conform to local requirements. The effort required for the <topicref TID="l10n"/> of a system heavily depends on how much <topicref TID="i18n"/> has been taken into account when building the system.</desc>
    </topic>
    <topic domain="wwww" TID="i18n" modate="20020717" crdate="20000728">
        <derived-from template="concept"/>
        <name>I18N</name>
        <alias>Internationalization</alias>
        <desc><topicref TID="i18n"/> is the process of designing an application so that it can be adapted to various languages and regions without engineering changes. The abbreviation is based on the fact that the rather lengthy word 'internationalization' starts with an 'i' followed by 18 characters followed by an 'n'. An internationalized system has the following characteristics: after <topicref TID="l10n"/>, the same executable can run worldwide; textual elements, such as status messages and the GUI component labels, are not hardcoded in the program (instead they are stored outside the source code and retrieved dynamically); support for new languages does not require recompilation; culturally-dependent data, such as dates and currencies, appear in formats that conform to the end user's region and language; <topicref TID="l10n"/> can be done quickly.</desc>
    </topic>
    <topic domain="wwww" TID="dcd" crdate="20000616">
        <derived-from template="metadata"/>
        <name>DCD</name>
        <alias>Document Content Description</alias>
    </topic>
    <topic domain="wwww" TID="xiop" modate="20040621" crdate="20001130">
        <derived-from template="giop"/>
        <name>XIOP</name>
        <status><topicref TID="xiop"/> is an experimental implementation of <topicref TID="corba"/>'s generic <topicref TID="giop"/> protocol. However, it never reached critical mass and there are no known applications or implementations.</status>
    </topic>
    <topic domain="wwww" TID="xdr1" modate="20040227" crdate="20001130">
        <derived-from template="dataformat"/>
        <name>XDR</name>
        <alias>External Data Representation</alias>
    </topic>
    <topic domain="wwww" TID="ndr" crdate="20040227">
        <derived-from template="dataformat"/>
        <name>NDR</name>
        <alias>Network Data Representation</alias>
    </topic>
    <topic domain="wwww" TID="dfdl" crdate="20060122">
        <derived-from template="topic"/>
        <name>DFDL</name>
        <alias>Data Format Description Language</alias>
    </topic>
    <topic domain="wwww" TID="cdr2" crdate="20040227">
        <derived-from template="dataformat"/>
        <name>CDR</name>
        <alias>Common Data Representation</alias>
    </topic>
    <topic domain="wwww" TID="dsdl" crdate="20020702">
        <derived-from template="concept"/>
        <name>DSDL</name>
        <alias>Document Schema Definition Languages</alias>
        <desc><topicref TID="dsdl"/> is a framework under which several <topicref TID="xmlschemalanguage"/>s are combined. The idea of <topicref TID="dsdl"/> is to modularize validation of <topicref TID="xml"/> documents, in the sense that for different aspects of validation, different <topicref TID="xmlschemalanguage"/>s can be used. The reasoning behind this approach is that no single <topicref TID="xmlschemalanguage"/> can match all possible application requirements, and rather than creating a very complex and hard to handle <topicref TID="xmlschemalanguage"/>, it makes more sense to create smaller, specialized <topicref TID="xmlschemalanguage"/>s, which are easier to learn, handle, and implement.</desc>
    </topic>
    <topic domain="wwww" TID="scm" crdate="20080404">
        <derived-from template="dataformat"/>
        <name>SCM</name>
        <alias>Schema Component Model</alias>
    </topic>
    <topic domain="wwww" TID="scx" crdate="20061005">
        <derived-from template="dataformat"/>
        <name>SCX</name>
        <alias>Schema Component XML Syntax</alias>
        <desc><topicref TID="scx"/> is a syntax for <topicref TID="xsd"/> components. It focuses explicitly on representing <topicref TID="xsd"/> components rather than including features which should make it easy for human users to write or modify an <topicref TID="xsd"/>. <topicref TID="scx"/> is comparable to <topicref TID="xsd"/>'s XML syntax or to <topicref TID="xscs"/>, because it simply is a representation for <topicref TID="xsd"/> components. What makes <topicref TID="scx"/> unique is its focus on making the <topicref TID="xsd"/> components as easily accessible as possible. <topicref TID="scx"/> thus could be regarded as the document-style complement to <topicref TID="xmlschemaapi"/>s such as <topicref TID="xsom"/> or <topicref TID="xsd2"/>.</desc>
    </topic>
    <topic domain="wwww" TID="xscs" crdate="20030305">
        <derived-from template="dataformat"/>
        <name>XSCS</name>
        <alias>XML Schema Compact Syntax</alias>
        <desc><topicref TID="xsd"/> is a rather complex <topicref TID="xmlschemalanguage"/>, partly because of its inherent complexity, and partly because of its <topicref TID="xml"/> syntax. In an effort to reduce the syntactic verboseness and complexity of <topicref TID="xsd"/>, <topicref TID="xscs"/> defines a <topicref TID="ebnf"/>-based (and non-<topicref TID="xml"/>) syntax for <topicref TID="xsd"/>. <topicref TID="xscs"/> is designed for human users, and transformations from and to <topicref TID="xsd"/> <topicref TID="xml"/> syntax are implemented using <topicref TID="java"/>-based tools.</desc>
    </topic>
    <topic domain="wwww" TID="trex" crdate="20020403">
        <derived-from template="xmlschemalanguage"/>
        <name>TREX</name>
        <alias>Tree Regular Expressions for XML</alias>
        <status>On <text date="20010605"/>, <topicref TID="oasis"/> announced "their decision to integrate <topicref TID="trex"/> and <topicref TID="relax"/> in order to collaborate on a unified lightweight specification for validating XML-based languages". The resulting <topicref TID="xmlschemalanguage"/> is called <topicref TID="relaxng"/>.</status>
    </topic>
    <topic domain="wwww" TID="relax" crdate="20020403">
        <derived-from template="xmlschemalanguage"/>
        <name>RELAX</name>
        <alias>Regular Language description for XML</alias>
        <status>On <text date="20010605"/>, <topicref TID="oasis"/> announced "their decision to integrate <topicref TID="trex"/> and <topicref TID="relax"/> in order to collaborate on a unified lightweight specification for validating XML-based languages". The resulting <topicref TID="xmlschemalanguage"/> is called <topicref TID="relaxng"/>.</status>
    </topic>
    <topic domain="wwww" TID="relaxng" crdate="20020403">
        <derived-from template="xmlschemalanguage"/>
        <name>RELAX NG</name>
    </topic>
    <topic domain="wwww" TID="examplotron" crdate="20020403">
        <derived-from template="xmlschemalanguage"/>
        <name>Examplotron</name>
    </topic>
    <topic domain="wwww" TID="crvx" crdate="20030205">
        <derived-from template="xmlschemalanguage"/>
        <name>CRVX</name>
        <alias>Character Repertoire Validation for XML</alias>
        <desc><topicref TID="xmlschemalanguage"/>s cover different areas of <topicref TID="xml"/> schema aspects, such as <topicref TID="grammar"/>-based schemas (e.g., <topicref TID="dtd"/> and <topicref TID="xsd"/> and rule-based schemas (e.g., <topicref TID="schematron"/>). <topicref TID="crvx"/> is a specialized and simple schema language for specifying character repertoire constraints for <topicref TID="xml"/> documents. It is meant as a complement for other schema languages which are often geared towards structural constraints for <topicref TID="xml"/> documents. <topicref TID="crvx"/> is based on the <topicref TID="unicode"/> character set which is the foundation of <topicref TID="xml"/>.</desc>
    </topic>
    <topic domain="wwww" TID="nvdl" crdate="20041224">
        <derived-from template="xmlschemalanguage"/>
        <name>NVDL</name>
        <alias>Namespace-based Validation Dispatching Language</alias>
    </topic>
    <topic domain="wwww" TID="dtll" crdate="20041224">
        <derived-from template="xmlschemalanguage"/>
        <name>DTLL</name>
        <alias>Data Type Library Language</alias>
    </topic>
    <topic domain="wwww" TID="crdl" crdate="20041224">
        <derived-from template="xmlschemalanguage"/>
        <name>CRDL</name>
        <alias>Character Repertoire Description Language</alias>
    </topic>
    <topic domain="wwww" TID="crvl" crdate="20060629">
        <derived-from template="xmlschemalanguage"/>
        <name>CRVL</name>
        <alias>Character Repertoire Validation Language</alias>
    </topic>
    <topic domain="wwww" TID="dsrl" crdate="20041224">
        <derived-from template="xmlschemalanguage"/>
        <name>DSRL</name>
        <alias>Document Schema Renaming Language</alias>
    </topic>
    <topic domain="wwww" TID="saf" crdate="20030805">
        <derived-from template="xmlschemalanguage"/>
        <name>SAF</name>
        <alias>Schema Adjunct Framework</alias>
    </topic>
    <topic domain="wwww" TID="dpml" crdate="20060629">
        <derived-from template="xmlpipelinelanguage"/>
        <name>DPML</name>
        <alias>Declarative Process Markup Language</alias>
    </topic>
    <topic domain="wwww" TID="schemachine" crdate="20030526">
        <derived-from template="xmlpipelinelanguage"/>
        <name>Schemachine</name>
    </topic>
    <topic domain="wwww" TID="rif" crdate="20060328">
        <derived-from template="dataformat"/>
        <name>RIF</name>
        <alias>Rule Interchange Format</alias>
    </topic>
    <topic domain="wwww" TID="xvif" crdate="20030526">
        <derived-from template="xmlpipelinelanguage"/>
        <name>XVIF</name>
        <alias>XML Validation Interoperability Framework</alias>
    </topic>
    <topic domain="wwww" TID="schematron" crdate="20010321">
        <derived-from template="xmlschemalanguage"/>
        <name>Schematron</name>
    </topic>
    <topic domain="wwww" TID="mns" crdate="20031216">
        <derived-from template="xmlschemalanguage"/>
        <name>MNS</name>
        <alias>Modular Namespaces</alias>
    </topic>
    <topic domain="wwww" TID="nrl" crdate="20031216">
        <derived-from template="xmlschemalanguage"/>
        <name>NRL</name>
        <alias>Namespace Routing Language</alias>
    </topic>
    <topic domain="wwww" TID="clix" crdate="20030525">
        <derived-from template="xmlschemalanguage"/>
        <name>CLIX</name>
        <alias>Constraint Language in XML</alias>
    </topic>
    <topic domain="wwww" TID="xcsl" crdate="20030130">
        <derived-from template="xmlschemalanguage"/>
        <name>XCSL</name>
        <alias>XML Constraint Specification Language</alias>
    </topic>
    <topic domain="wwww" TID="dsd2" crdate="20010321">
        <derived-from template="xmlschemalanguage"/>
        <name>DSD</name>
        <alias>Document Structure Description</alias>
    </topic>
    <topic domain="wwww" TID="xdr2" modate="20020722" crdate="20001208">
        <derived-from template="xmlschemalanguage"/>
        <name>XDR</name>
        <alias>XML-Data Reduced</alias>
        <status><topicref TID="microsoft"/> has made the transition from <topicref TID="xdr2"/> to <topicref TID="xsd"/>, which is now the <topicref TID="xmlschemalanguage"/> used and supported by <topicref TID="microsoft"/>.</status>
    </topic>
    <topic domain="wwww" TID="dt4dtd" modate="20020722" crdate="20001208">
        <derived-from template="xmlschemalanguage"/>
        <name>DT4DTD</name>
        <alias>Datatypes for DTDs</alias>
        <status><topicref TID="dt4dtd"/> was an early attempt to create an improved <topicref TID="xmlschemalanguage"/> by supplementing <topicref TID="dtd"/>'s with an application-oriented set of data types, but has never been used on a large scale.</status>
    </topic>
    <topic domain="wwww" TID="samba" crdate="20020718">
        <derived-from template="product"/>
        <name>Samba</name>
    </topic>
    <topic domain="wwww" TID="wfxml" crdate="20001130">
        <derived-from template="metadata"/>
        <name>Wf-XML</name>
        <alias>Workflow XML</alias>
    </topic>
    <topic domain="wwww" TID="xmldata" modate="20020722" crdate="20000616">
        <derived-from template="xmlschemalanguage"/>
        <name>XML-Data</name>
        <desc><topicref TID="xmldata"/> is a proposal authored by <topicref TID="microsoft"/> for the definition of <topicref TID="www"/> <topicref TID="metadata"/>. The proposal has been used as input for <topicref TID="w3c"/>'s work on <topicref TID="rdf"/>, which has the same application area as <topicref TID="xmldata"/>.</desc>
        <status>In order to support <topicref TID="w3c"/>'s <topicref TID="xsd"/>, <topicref TID="microsoft"/> limited <topicref TID="xmldata"/> to <topicref TID="xdr2"/>, which is a proper subset of <topicref TID="xsd"/>.</status>
    </topic>
    <topic domain="wwww" TID="smpte" crdate="20010305">
        <derived-from template="group"/>
        <name>SMPTE</name>
        <alias>Society of Motion Picture and Television Engineers</alias>
    </topic>
    <topic domain="wwww" TID="mpeg" crdate="20000608">
        <derived-from template="group"/>
        <name>MPEG</name>
        <alias>Moving Pictures Experts Group</alias>
    </topic>
    <topic domain="wwww" TID="ntp" crdate="20000810">
        <derived-from template="protocol"/>
        <name>NTP</name>
        <alias>Network Time Protocol</alias>
        <desc><topicref TID="ntp"/> provides the mechanisms to synchronize time and coordinate time distribution in a large, diverse <topicref TID="internet"/> operating at rates from mundane to light-wave. It uses a returnable-time design in which a distributed subnet of time <topicref TID="server"/>s operating in a self-organizing, hierarchical-master-slave configuration synchronizes local clocks within the subnet and to national time standards via wire or radio. The <topicref TID="server"/>s can also redistribute reference time via local routing <topicref TID="algorithm"/>s and time <topicref TID="server"/>s. A simpler variant of <topicref TID="ntp"/> has been specified under the name of <topicref TID="sntp"/>.</desc>
    </topic>
    <topic domain="wwww" TID="madcap" crdate="20020719">
        <derived-from template="protocol"/>
        <name>MADCAP</name>
        <alias>Multicast Address Dynamic Client Allocation Protocol</alias>
    </topic>
    <topic domain="wwww" TID="xup" crdate="20020530">
        <derived-from template="protocol"/>
        <name>XUP</name>
        <alias>Extensible User Interface Protocol</alias>
    </topic>
    <topic domain="wwww" TID="tmx" crdate="20040112">
        <derived-from template="dataformat"/>
        <name>TMX</name>
        <alias>Translation Memory Exchange Format</alias>
    </topic>
    <topic domain="wwww" TID="bxxp" crdate="20020326">
        <derived-from template="protocol"/>
        <name>BXXP</name>
        <alias>Blocks Extensible Exchange Protocol</alias>
    </topic>
    <topic domain="wwww" TID="beep" crdate="20020326">
        <derived-from template="protocol"/>
        <name>BEEP</name>
        <alias>Blocks Extensible Exchange Protocol</alias>
    </topic>
    <topic domain="wwww" TID="sntp" crdate="20000810">
        <derived-from template="protocol"/>
        <name>SNTP</name>
        <alias>Simple Network Time Protocol</alias>
    </topic>
    <topic domain="wwww" TID="bios" crdate="20020722">
        <derived-from template="technology"/>
        <name>BIOS</name>
        <alias>Basic Input/Output System</alias>
    </topic>
    <topic domain="wwww" TID="cve" crdate="20010305">
        <derived-from template="topic"/>
        <name>CVE</name>
        <alias>Common Vulnerabilities and Exposures</alias>
    </topic>
    <topic domain="wwww" TID="fxpp" crdate="20031211">
        <derived-from template="concept"/>
        <name>FXPP</name>
        <alias>Flexible XML Processing Profile</alias>
    </topic>
    <topic domain="wwww" TID="xrx" crdate="20081112">
        <derived-from template="concept"/>
        <name>XRX</name>
        <alias>XForms, REST, and XQuery</alias>
    </topic>
    <topic domain="wwww" TID="rest" crdate="20020902">
        <derived-from template="concept"/>
        <name>REST</name>
        <alias>Representational State Transfer</alias>
    </topic>
    <topic domain="wwww" TID="uclp" crdate="20020902">
        <derived-from template="protocol"/>
        <name>UCLP</name>
        <alias>Universal Commerce Language and Protocol</alias>
    </topic>
    <topic domain="wwww" TID="xmsg" modate="20040816" crdate="20020902">
        <derived-from template="protocol"/>
        <name>XMSG</name>
        <alias>XML Messaging Specification</alias>
        <status><topicref TID="xmsg"/> was an early approach to specify <topicref TID="xml"/> messaging using <topicref TID="mime"/> packaging. A newer and widely accepted approach is <topicref TID="mtom"/>/<topicref TID="xop"/>.</status>
    </topic>
    <topic domain="wwww" TID="asap" crdate="20030805">
        <derived-from template="protocol"/>
        <name>ASAP</name>
        <alias>Asynchronous Service Access Protocol</alias>
    </topic>
    <topic domain="wwww" TID="soap" modate="20040227" crdate="20000616">
        <derived-from template="dataformat"/>
        <name>SOAP</name>
        <alias>Simple Object Access Protocol</alias>
    </topic>
    <topic domain="wwww" TID="xop" crdate="20040210">
        <derived-from template="dataformat"/>
        <name>XOP</name>
        <alias>XML-binary Optimized Packaging</alias>
    </topic>
    <topic domain="wwww" TID="miffy" crdate="20031228">
        <derived-from template="dataformat"/>
        <name>MIFFY</name>
        <alias>MTOM Inclusion Format For You</alias>
    </topic>
    <topic domain="wwww" TID="mtom" crdate="20030926">
        <derived-from template="protocol"/>
        <name>MTOM</name>
        <alias>Message Transmission Optimization Mechanism</alias>
    </topic>
    <topic domain="wwww" TID="swa" crdate="20030926">
        <derived-from template="protocol"/>
        <name>SwA</name>
        <alias>SOAP with Attachments</alias>
        <status><topicref TID="swa"/> has been developed as a way to package <topicref TID="soap"/> messages with attachments, but will be replaced by the more powerful <topicref TID="mtom"/>/<topicref TID="xop"/> mechanisms.</status>
    </topic>
    <topic domain="wwww" TID="usenetnews" crdate="20010322">
        <derived-from template="technology"/>
        <name>Usenet News</name>
        <alias>News</alias>
        <desc><topicref TID="usenetnews"/> can be regarded as the oldest <topicref TID="internet"/> application for global distribution of information. It originated in 1979 at the University of North Carolina. It is simply a set of machines (<topicref TID="usenetnews"/> <topicref TID="server"/>s) which cooperate to exchange (using <topicref TID="nntp"/>) articles tagged with one or more labels, which are called "newsgroups". Newsgroups are organized hierarchically according to the subjects of the articles belonging to them. Newsgroups or individual articles in newsgroups can be addressed using a special <topicref TID="url"/> scheme.</desc>
    </topic>
    <topic domain="wwww" TID="nntp" crdate="20000608">
        <derived-from template="protocol"/>
        <name>NNTP</name>
        <alias>Network News Transport Protocol</alias>
        <desc><topicref TID="nntp"/> specifies a protocol for the distribution, inquiry, retrieval, and posting of <topicref TID="usenetnews"/> articles using a reliable stream-based transmission of <topicref TID="usenetnews"/> among the <topicref TID="internet"/> community. <topicref TID="nntp"/> is designed so that <topicref TID="usenetnews"/> articles are stored in a central database allowing a subscriber to select only those items he wishes to read. Indexing, cross-referencing, and expiration of aged messages are also provided.</desc>
    </topic>
    <topic domain="wwww" TID="utf" crdate="20000608">
        <derived-from template="ces"/>
        <name>UTF</name>
        <alias>UCS Transformation Format</alias>
        <desc><topicref TID="utf"/> is used for coding <topicref TID="ucs"/> characters. Although <topicref TID="ucs"/> defines character codings (<topicref TID="ucs2"/> and <topicref TID="ucs4"/>), they are hard to use in many current applications and protocols that assume 8- or even 7-bit characters. <topicref TID="utf"/> formats usually are variable length formats, for example in <topicref TID="utf8"/> a character is represented by 1 to 6 bytes, while in <topicref TID="utf16"/> a character is represented by 2 to 4 bytes (<topicref TID="utf32"/>, however, always encodes characters as 4 bytes).</desc>
    </topic>
    <topic domain="wwww" TID="utf1" crdate="20001220">
        <derived-from template="utf"/>
        <name>UTF-1</name>
    </topic>
    <topic domain="wwww" TID="utf2" crdate="20001220">
        <derived-from template="utf"/>
        <name>UTF-2</name>
    </topic>
    <topic domain="wwww" TID="utf7" crdate="20001216">
        <derived-from template="utf"/>
        <name>UTF-7</name>
    </topic>
    <topic domain="wwww" TID="utf8" crdate="20001216">
        <derived-from template="utf"/>
        <name>UTF-8</name>
    </topic>
    <topic domain="wwww" TID="utf16" crdate="20001216">
        <derived-from template="utf"/>
        <name>UTF-16</name>
    </topic>
    <topic domain="wwww" TID="utf16le" crdate="20030123">
        <derived-from template="utf16"/>
        <name>UTF-16LE</name>
    </topic>
    <topic domain="wwww" TID="utf16be" crdate="20030123">
        <derived-from template="utf16"/>
        <name>UTF-16BE</name>
    </topic>
    <topic domain="wwww" TID="utf32" crdate="20030123">
        <derived-from template="utf"/>
        <name>UTF-32</name>
        <desc><topicref TID="utf32"/> is the <topicref TID="utf"/> that serializes a <topicref TID="unicode"/> code point as a sequence of four bytes, in either big-endian (<topicref TID="utf32be"/>) or little-endian <topicref TID="utf32le"/> format. An initial sequence corresponding to U+FEFF is interpreted as a <topicref TID="bom1"/>, it is used to distinguish between the two byte orders. The <topicref TID="bom1"/> is not considered part of the content of the text. A serialization of <topicref TID="unicode"/> code points into <topicref TID="utf32"/> may or may not begin with a <topicref TID="bom1"/> The term <topicref TID="utf32"/> can be used ambiguously. When referring to the encoding of <topicref TID="unicode"/> in memory, there is no associated byte orientation, and a <topicref TID="bom1"/> is never used. When referring to a serialization of <topicref TID="unicode"/> code points into bytes, it may have a <topicref TID="bom1"/> and either byte orientation..</desc>
    </topic>
    <topic domain="wwww" TID="utf32le" crdate="20030123">
        <derived-from template="utf32"/>
        <name>UTF-32LE</name>
    </topic>
    <topic domain="wwww" TID="utf32be" crdate="20030123">
        <derived-from template="utf32"/>
        <name>UTF-32BE</name>
    </topic>
    <topic domain="wwww" TID="ldh" crdate="20030411">
        <derived-from template="dataformat"/>
        <name>LDH</name>
        <alias>Letter Digit Hyphen</alias>
        <desc><topicref TID="ldh"/> form is a <topicref TID="dataformat"/> for host names in the <topicref TID="dns"/>. It constrains valid names to contain only <topicref TID="ascii"/> letters, digits, and hyphens.</desc>
    </topic>
    <topic domain="wwww" TID="scsu" crdate="20001220">
        <derived-from template="technology"/>
        <name>SCSU</name>
        <alias>Standard Compression Scheme for Unicode</alias>
    </topic>
    <topic domain="wwww" TID="x11" crdate="20010322">
        <derived-from template="technology"/>
        <name>X11</name>
        <alias>X Window System</alias>
        <desc><topicref TID="x11"/> is a distributed window system that is based on the <topicref TID="clientserver"/>. In <topicref TID="x11"/>, the traditional roles of a <topicref TID="client"/> and a <topicref TID="server"/> are not distributed as usual, because the <topicref TID="x11"/> <topicref TID="server"/> is the local entity (providing the service of displaying data and accepting user input), while the <topicref TID="x11"/> <topicref TID="client"/> is the remotely running program, which uses the <topicref TID="x11"/> <topicref TID="server"/> to provide a <topicref TID="gui"/> to the user. <topicref TID="x11"/> is based on a <topicref TID="protocol"/>, which makes it very easy to separate a (possibly heavyweight) program and its <topicref TID="gui"/>. <topicref TID="x11"/> is commonly used in <topicref TID="unix"/>-derived <topicref TID="os"/>s.</desc>
    </topic>
    <topic domain="wwww" TID="ccs" crdate="20001220">
        <derived-from template="concept"/>
        <name>CCS</name>
        <alias>Coded Character Set</alias>
        <desc>A <topicref TID="ccs"/> identifies a set of characters that are relevant and should be identifiable for some <topicref TID="characterset"/>. It does not, however, specify the actual encoding of these characters, which is done by one or more <topicref TID="ces"/>s.</desc>
    </topic>
    <topic domain="wwww" TID="ces" crdate="20001220">
        <derived-from template="dataformat"/>
        <name>CES</name>
        <alias>Character Encoding Scheme</alias>
        <desc>A <topicref TID="ces"/> defines a mapping from a given set of characters (the <topicref TID="ccs"/>) to encoded forms of the characters. Thus, there can be multiple <topicref TID="ces"/>s for one <topicref TID="ccs"/>.</desc>
    </topic>
    <topic domain="core" TID="characterset" crdate="20001220">
        <derived-from template="concept"/>
        <name>Character Set</name>
        <desc>A <topicref TID="characterset"/> is defining a set of characters and their encoding. Newer standards (such as <topicref TID="unicode"/>) separate these issues by defining the set of characters (<topicref TID="ccs"/>) and their encoding (<topicref TID="ces"/>) separately, but in many cases (such as the popular <topicref TID="ascii"/> <topicref TID="characterset"/>), the characters and their encoding are defined in a single step.</desc>
    </topic>
    <topic domain="core" TID="regex" crdate="20010824">
        <derived-from template="concept"/>
        <name>Regular Expression</name>
    </topic>
    <topic domain="wwww" TID="bre" crdate="20010824">
        <derived-from template="regex"/>
        <name>BRE</name>
        <alias>Basic Regular Expression</alias>
    </topic>
    <topic domain="wwww" TID="ere" crdate="20010824">
        <derived-from template="regex"/>
        <name>ERE</name>
        <alias>Extended Regular Expression</alias>
    </topic>
    <topic domain="wwww" TID="ace" crdate="20020525">
        <derived-from template="algorithm"/>
        <name>ACE</name>
        <alias>ASCII Compatible Encoding</alias>
        <desc>An <topicref TID="ace"/> is a string of characters resulting from a particular <topicref TID="algorithm"/> for transforming multilingual character information into an <topicref TID="ascii"/>-based alphanumeric form acceptable by the existing <topicref TID="dns"/>. This means that an <topicref TID="ace"/> encoded string must conform to the <topicref TID="ldh"/> restrictions for strings.</desc>
    </topic>
    <topic domain="wwww" TID="race" crdate="20020525">
        <derived-from template="characterset"/>
        <name>RACE</name>
        <alias>Row-based ASCII Compatible Encoding</alias>
    </topic>
    <topic domain="wwww" TID="brace" crdate="20020525">
        <derived-from template="characterset"/>
        <name>BRACE</name>
        <alias>Bi-mode Row-based ASCII Compatible Encoding</alias>
    </topic>
    <topic domain="wwww" TID="lace" crdate="20020525">
        <derived-from template="characterset"/>
        <name>LACE</name>
        <alias>Length-based ASCII Compatible Encoding</alias>
    </topic>
    <topic domain="wwww" TID="dude" modate="20031124" crdate="20020525">
        <derived-from template="ces"/>
        <name>DUDE</name>
        <alias>Differential Unicode Domain Encoding</alias>
    </topic>
    <topic domain="wwww" TID="iso8859" modate="20060528" crdate="20001220">
        <derived-from template="characterset"/>
        <name>ISO 8859</name>
        <desc><topicref TID="iso8859"/> is a family of <topicref TID="characterset"/>s standardized by <topicref TID="iso"/>. All <topicref TID="iso8859"/> variants are 8-bit <topicref TID="characterset"/>s, containing a total of 256 characters. The variants are identified by a trailing number indicating the specific variant, for example <topicref TID="iso88591"/> for the Latin-1 character set. The first half of the variants (characters 0-127) is always occupied by the <topicref TID="ascii"/> <topicref TID="characterset"/>, while the second half (characters 128-255) is occupied by characters specific to the variant.</desc>
    </topic>
    <topic domain="wwww" TID="iso88591" crdate="20060528">
        <derived-from template="characterset"/>
        <name>ISO 8859-1</name>
        <alias>Latin-1</alias>
        <status><topicref TID="iso88591"/> is one of the most popular <topicref TID="iso8859"/> character sets. However, <topicref TID="iso885915"/> is increasingly replacing it, because it contains some updates to the <topicref TID="iso88591"/> character set, most notably the euro sign.</status>
    </topic>
    <topic domain="wwww" TID="iso885915" crdate="20060528">
        <derived-from template="characterset"/>
        <name>ISO 8859-15</name>
        <alias>Latin-9</alias>
        <desc><topicref TID="iso885915"/> is an update of <topicref TID="iso88591"/>, it replaces a small number of characters, and most notably introduces the euro sign.</desc>
    </topic>
    <topic domain="wwww" TID="euc" crdate="20001220">
        <derived-from template="characterset"/>
        <name>EUC</name>
        <alias>Extended Unix Code</alias>
    </topic>
    <topic domain="wwww" TID="morse" crdate="20040114">
        <derived-from template="characterset"/>
        <name>Morse</name>
    </topic>
    <topic domain="wwww" TID="baudot" crdate="20040114">
        <derived-from template="characterset"/>
        <name>Baudot</name>
    </topic>
    <topic domain="wwww" TID="murray" crdate="20040114">
        <derived-from template="characterset"/>
        <name>Murray</name>
    </topic>
    <topic domain="wwww" TID="ita2" crdate="20040114">
        <derived-from template="characterset"/>
        <name>ITA2</name>
        <alias>International Telegraph Alphabet #2</alias>
    </topic>
    <topic domain="wwww" TID="fieldata" crdate="20040114">
        <derived-from template="characterset"/>
        <name>FIELDATA</name>
    </topic>
    <topic domain="wwww" TID="purl" crdate="20011125">
        <derived-from template="url"/>
        <name>PURL</name>
        <alias>Persistent URL</alias>
    </topic>
    <topic domain="wwww" TID="url" crdate="20000607" modate="20051216">
        <derived-from template="uri"/>
        <name>URL</name>
        <alias>Uniform Resource Locator</alias>
        <desc>A <topicref TID="url"/> is the address of a resource which is retrievable using <topicref TID="protocol"/>s already deployed on the <topicref TID="internet"/>. A <topicref TID="url"/> defines an access <topicref TID="protocol"/>, called a "scheme", and a "scheme-dependent part", which has to provide sufficient information to locate an object using the specified scheme. In case of <topicref TID="http"/> <topicref TID="url"/>s, the scheme is "http", and the scheme-dependent part specifies the name of the <topicref TID="httpserver"/> as well as the path of the object on the <topicref TID="httpserver"/>.</desc>
        <status>Even though the term <topicref TID="url"/> is still in widespread use, officially there is no valid specification for it (and it is unlikely that the term will ever be revived). It has been replaced by the more general term <topicref TID="uri"/>, which is the technically correct term for resource identification as used on the <topicref TID="www"/>.</status>
    </topic>
    <topic domain="wwww" TID="moss" crdate="20010315">
        <derived-from template="protocol"/>
        <name>MOSS</name>
        <alias>MIME Object Security Services</alias>
        <desc><topicref TID="moss"/> is a <topicref TID="protocol"/> that uses the <topicref TID="mime"/> multipart/signed and multipart/encrypted framework to apply digital signature and <topicref TID="encryption"/> services to <topicref TID="mime"/> objects. The services are offered through the use of end-to-end cryptography between an originator and a recipient at the application layer. <topicref TID="pkc"/> is used in support of the digital signature service and <topicref TID="encryption"/> key management. <topicref TID="skc"/> is used in support of the <topicref TID="encryption"/> service. The procedures are intended to be compatible with a wide range of public key management approaches, including both ad hoc and certificate-based schemes. Mechanisms are provided to support many public key management approaches.</desc>
    </topic>
    <topic domain="wwww" TID="mime" crdate="20000608">
        <derived-from template="dataformat"/>
        <name>MIME</name>
        <alias>Multipurpose Internet Mail Extensions</alias>
        <desc><topicref TID="mime"/> provide facilities to allow multiple objects in a single <topicref TID="internet"/> <topicref TID="email"/> message, to represent body text in character sets other than <topicref TID="ascii"/>, to represent formatted multi-font text messages, to represent non-textual material such as images and audio fragments, and generally to facilitate later extensions defining new types of <topicref TID="internet"/> <topicref TID="email"/> for use by cooperating email agents.</desc>
    </topic>
    <topic domain="wwww" TID="dime" crdate="20020118" modate="20040620">
        <derived-from template="dataformat"/>
        <name>DIME</name>
        <alias>Direct Internet Message Encapsulation</alias>
        <status><topicref TID="dime"/> as an early approach to the packaging problem of <topicref TID="soap"/> messages with attachments has been replaced by the newer <topicref TID="mtom"/>/<topicref TID="xop"/> mechanisms.</status>
    </topic>
    <topic domain="wwww" TID="smime" crdate="20010815">
        <derived-from template="dataformat"/>
        <name>S/MIME</name>
        <alias>Secure Multipurpose Internet Mail Extensions</alias>
    </topic>
    <topic domain="wwww" TID="xmtp" crdate="20051030">
        <derived-from template="dataformat"/>
        <name>XMTP</name>
        <alias>XML MIME Transformation Protocol</alias>
    </topic>
    <topic domain="wwww" TID="iesg" crdate="20000920">
        <derived-from template="organization"/>
        <name>IESG</name>
        <alias>Internet Engineering Steering Group</alias>
    </topic>
    <topic domain="wwww" TID="ietf" crdate="20000607">
        <derived-from template="organization"/>
        <name>IETF</name>
        <alias>Internet Engineering Task Force</alias>
        <desc><topicref TID="ietf"/> is a large open international community of network designers, operators, vendors, and researchers concerned with the evolution of the <topicref TID="internet"/> architecture and the smooth operation of the <topicref TID="internet"/>. It is open to any interested individual. The actual technical work of the <topicref TID="ietf"/> is done in its working groups, which are organized by topic into several areas (e.g., routing, transport, security, etc.).</desc>
    </topic>
    <topic domain="wwww" TID="isoc" crdate="20000920">
        <derived-from template="organization"/>
        <name>ISOC</name>
        <alias>Internet Society</alias>
    </topic>
    <topic domain="wwww" TID="irtf" crdate="20000920">
        <derived-from template="organization"/>
        <name>IRTF</name>
        <alias>Internet Research Task Force</alias>
        <desc>The <topicref TID="irtf"/> is composed of a number of focused, long-term and small research groups. These groups work on topics related to <topicref TID="internet"/> <topicref TID="protocol"/>s, applications, architecture and technology. The <topicref TID="irtf"/> focuses on longer term research issues related to the <topicref TID="internet"/>, while the parallel organization, the <topicref TID="ietf"/>, focuses on the shorter term issues of engineering and standards making.</desc>
    </topic>
    <topic domain="wwww" TID="os2" crdate="20020825">
        <derived-from template="product"/>
        <derived-from template="os"/>
        <name>OS/2</name>
    </topic>
    <topic domain="wwww" TID="symbian" crdate="20070807">
        <derived-from template="product"/>
        <derived-from template="os"/>
        <name>Symbian</name>
    </topic>
    <topic domain="wwww" TID="macos" crdate="20010316">
        <derived-from template="product"/>
        <derived-from template="os"/>
        <name>MacOS</name>
    </topic>
    <topic domain="wwww" TID="android" crdate="20100621">
        <derived-from template="product"/>
        <derived-from template="os"/>
        <name>Android</name>
    </topic>
    <topic domain="wwww" TID="iphoneos" crdate="20100621">
        <derived-from template="product"/>
        <derived-from template="os"/>
        <name>iPhone OS</name>
    </topic>
    <topic domain="wwww" TID="ios" crdate="20100621">
        <derived-from template="product"/>
        <derived-from template="os"/>
        <name>iOS</name>
        <alias>iPhone OS</alias>
        <desc>With the release of <topicref TID="iphone"/> 4 in mid-2010, <topicref TID="apple"/> renamed <topicref TID="iphone"/> to <topicref TID="ios"/>.</desc>
    </topic>
    <topic domain="wwww" TID="vms" crdate="20010811">
        <derived-from template="product"/>
        <derived-from template="os"/>
        <name>VMS</name>
        <alias>Virtual Memory System</alias>
    </topic>
    <topic domain="wwww" TID="cpm" crdate="20020719">
        <derived-from template="product"/>
        <derived-from template="os"/>
        <name>CP/M</name>
        <alias>Control Program for Microprocessors</alias>
    </topic>
    <topic domain="wwww" TID="dos" crdate="20020719">
        <derived-from template="product"/>
        <derived-from template="os"/>
        <name>DOS</name>
        <alias>Disk Operating System</alias>
    </topic>
    <topic domain="wwww" TID="windows" crdate="20010316">
        <derived-from template="product"/>
        <derived-from template="os"/>
        <name>Windows</name>
    </topic>
    <topic domain="wwww" TID="epoc" crdate="20010311">
        <derived-from template="product"/>
        <derived-from template="os"/>
        <name>EPOC</name>
    </topic>
    <topic domain="wwww" TID="unix" crdate="20010305">
        <derived-from template="os"/>
        <name>Unix</name>
    </topic>
    <topic domain="wwww" TID="posix" crdate="20020710">
        <derived-from template="unix"/>
        <name>POSIX</name>
        <alias>Portable Operating System Interface</alias>
    </topic>
    <topic domain="wwww" TID="solaris" crdate="20010305">
        <derived-from template="product"/>
        <derived-from template="unix"/>
        <name>Solaris</name>
    </topic>
    <topic domain="wwww" TID="linux" crdate="20010305">
        <derived-from template="unix"/>
        <name>Linux</name>
    </topic>
    <topic domain="wwww" TID="xfdl" modate="20060220" crdate="20040203">
        <derived-from template="technology"/>
        <name>XFDL</name>
        <alias>Extensible Forms Description Language</alias>
        <status><topicref TID="xfdl"/> is an <topicref TID="xml"/> vocabulary initially published 1998 as an improvement to <topicref TID="htmlforms"/> as a <topicref TID="w3c"/> note in an attempt to standardize a set of features for the next generation of secure Web-based applications. <topicref TID="xfdl"/> has continued to evolve and now is an <topicref TID="xforms"/> host language well suited for <topicref TID="xforms"/>, providing pixel precision and robust security with a dynamic range of features.</status>
    </topic>
    <topic domain="wwww" TID="xfa" crdate="20040203">
        <derived-from template="technology"/>
        <name>XFA</name>
        <alias>XML Forms Architecture</alias>
        <status><topicref TID="xfa"/> has been suggested as an improvement to <topicref TID="htmlforms"/> and has been submitted to the <topicref TID="w3c"/>. However, the newer <topicref TID="xforms"/> has broader support and <topicref TID="xfa"/> thus is no longer under development.</status>
    </topic>
    <topic domain="wwww" TID="xforms" crdate="20000728">
        <derived-from template="technology"/>
        <name>XForms</name>
    </topic>
    <topic domain="wwww" TID="orbeonforms" crdate="20061125">
        <derived-from template="product"/>
        <name>Orbeon Forms</name>
    </topic>
    <topic domain="wwww" TID="ops" crdate="20061125">
        <derived-from template="product"/>
        <name>OPS</name>
        <alias>Orbeon Presentation Server</alias>
    </topic>
    <topic domain="wwww" TID="oxf" crdate="20061125">
        <derived-from template="product"/>
        <name>OXF</name>
        <alias>Open XML Framework</alias>
    </topic>
    <topic domain="wwww" TID="ut0" crdate="20020624">
        <derived-from template="ut"/>
        <name>UT0</name>
    </topic>
    <topic domain="wwww" TID="ut1" crdate="20020624">
        <derived-from template="ut"/>
        <name>UT1</name>
    </topic>
    <topic domain="wwww" TID="ut2" crdate="20020624">
        <derived-from template="ut"/>
        <name>UT2</name>
    </topic>
    <topic domain="wwww" TID="ut" crdate="20020624">
        <derived-from template="topic"/>
        <name>UT</name>
        <alias>Universal Time</alias>
    </topic>
    <topic domain="wwww" TID="utc" crdate="20020624">
        <derived-from template="topic"/>
        <name>UTC</name>
        <alias>Coordinated Universal Time</alias>
    </topic>
    <topic domain="wwww" TID="x2doc" crdate="20070211">
        <derived-from template="topic"/>
        <name>X2Doc</name>
    </topic>
    <topic domain="wwww" TID="gmt" crdate="20020624">
        <derived-from template="topic"/>
        <name>GMT</name>
        <alias>Greenwich Mean Time</alias>
    </topic>
    <topic domain="wwww" TID="scxml" crdate="20060305">
        <derived-from template="dataformat"/>
        <name>SCXML</name>
        <alias>State Chart XML</alias>
    </topic>
    <topic domain="wwww" TID="sscc" crdate="20031215">
        <derived-from template="identifier"/>
        <name>SSCC</name>
        <alias>Serial Shipping Container Code</alias>
    </topic>
    <topic domain="wwww" TID="gtin" crdate="20031215">
        <derived-from template="identifier"/>
        <name>GTIN</name>
        <alias>Global Trade Item Number</alias>
    </topic>
    <topic domain="wwww" TID="sku" crdate="20031215">
        <derived-from template="identifier"/>
        <name>SKU</name>
        <alias>Stock Keeping Unit</alias>
    </topic>
    <topic domain="wwww" TID="upc" crdate="20010316">
        <derived-from template="identifier"/>
        <name>UPC</name>
        <alias>Universal Product Code</alias>
    </topic>
    <topic domain="wwww" TID="ean" crdate="20010316">
        <derived-from template="identifier"/>
        <name>EAN</name>
        <alias>European Article Number</alias>
    </topic>
    <topic domain="wwww" TID="grid" crdate="20040107">
        <derived-from template="identifier"/>
        <name>GRid</name>
        <alias>Global Release Identifier</alias>
    </topic>
    <topic domain="wwww" TID="isrc" crdate="20040107">
        <derived-from template="identifier"/>
        <name>ISRC</name>
        <alias>International Standard Recording Code</alias>
    </topic>
    <topic domain="wwww" TID="isbn" crdate="20010316">
        <derived-from template="identifier"/>
        <name>ISBN</name>
        <alias>International Standard Book Number</alias>
        <desc>The <topicref TID="isbn"/> is a nine- or ten-digit number which identifies a specific book title and is recognized worldwide. Publishers assign <topicref TID="isbn"/>s to books to simplify and expedite their ordering and purchase. An <topicref TID="isbn"/> number can often be found on the back of the title page of a book or at the bottom of the back cover, though many older books do not have <topicref TID="isbn"/>s. Sometimes more than one book has the same <topicref TID="isbn"/>, as is frequently the case with books in a series. Book records for books in a series may also contain an <topicref TID="issn"/> for the series. Separate <topicref TID="isbn"/>s are usually assigned for each format of a book (such as hard-cover or paperback). Newer books frequently also have an <topicref TID="ean"/>-encoded version of the <topicref TID="isbn"/> on their cover.</desc>
    </topic>
    <topic domain="wwww" TID="issn" crdate="20010316">
        <derived-from template="identifier"/>
        <name>ISSN</name>
        <alias>International Standard Serial Number</alias>
        <desc>The <topicref TID="issn"/> is an internationally accepted code which identifies serial publications. It is an eight-digit number consisting of seven digits plus a check digit which enables a computer to recognize when the number is incorrectly cited. The check digit may be an "X", otherwise the <topicref TID="issn"/> is fully numeric. An <topicref TID="issn"/> may be used as control numbers for serial titles in automated systems, for example for identifying titles, ordering, checking in, and claiming by libraries and subscription agents. It may be used to ensure more accurate serials citation by scholars, researchers, abstractors and librarians and is particularly helpful when distinguishing between serials with identical titles. An increasingly important use of the <topicref TID="issn"/> is as a component in <topicref TID="ean"/> barcodes for magazines.</desc>
    </topic>
    <topic domain="wwww" TID="sici" crdate="20010316">
        <derived-from template="identifier"/>
        <name>SICI</name>
        <alias>Serial Item and Contribution Identifier</alias>
    </topic>
    <topic domain="wwww" TID="nbn" crdate="20011119">
        <derived-from template="identifier"/>
        <name>NBN</name>
        <alias>National Bibliography Number</alias>
    </topic>
    <topic domain="wwww" TID="crossref" crdate="20040602">
        <derived-from template="identifier"/>
        <name>CrossRef</name>
    </topic>
    <topic domain="wwww" TID="coins" crdate="20070727">
        <derived-from template="dataformat"/>
        <name>COinS</name>
        <alias>Context Objects in Spans</alias>
    </topic>
    <topic domain="wwww" TID="openurl" crdate="20040602">
        <derived-from template="identifier"/>
        <name>OpenURL</name>
    </topic>
    <topic domain="wwww" TID="doi" crdate="20010316">
        <derived-from template="identifier"/>
        <name>DOI</name>
        <alias>Digital Object Identifier</alias>
        <desc>The <topicref TID="doi"/> system is a mechanism for marking digital objects in order to facilitate <topicref TID="ecommerce"/> and enable copyright management in a digital environment. <topicref TID="doi"/> not only provides a unique identification for digital content, but also a way to link users of the materials to the rights holders themselves to facilitate automated digital commerce. The underlying technology of <topicref TID="doi"/> is the <topicref TID="handlesystem"/>, which associates each <topicref TID="doi"/> name with one or more locations where the object may be found.</desc>
    </topic>
    <topic domain="wwww" TID="ssi" crdate="20000615">
        <derived-from template="serversidetechnology"/>
        <name>SSI</name>
        <alias>Server-Side Includes</alias>
        <desc><topicref TID="ssi"/> make it possible to include information into <topicref TID="www"/> pages before delivering them to a <topicref TID="httpclient"/>. A <topicref TID="www"/> page using <topicref TID="ssi"/> contains special instructions which are interpreted by the <topicref TID="httpserver"/> whenever the <topicref TID="www"/> page is requested. These instructions may specify to include other documents (e.g., document headers or footers) or to insert dynamic information, such as the current date or an access count. There is no standard for <topicref TID="ssi"/>, so each <topicref TID="httpserver"/> implementation uses its own syntax and functionality.</desc>
    </topic>
    <topic domain="wwww" TID="xssi" crdate="20020626">
        <derived-from template="serversidetechnology"/>
        <name>XSSI</name>
        <alias>Extended Server-Side Includes</alias>
    </topic>
    <topic domain="wwww" TID="iab" crdate="20000920">
        <derived-from template="organization"/>
        <name>IAB</name>
        <alias>Internet Architecture Board</alias>
        <desc>The <topicref TID="iab"/> is the technical body that oversees the development of the <topicref TID="internet"/> <topicref TID="protocol"/> suite. It has two task forces, the <topicref TID="ietf"/> and the <topicref TID="irtf"/>.</desc>
    </topic>
    <topic domain="wwww" TID="iana" crdate="20000612">
        <derived-from template="organization"/>
        <name>IANA</name>
        <alias>Internet Assigned Numbers Authority</alias>
    </topic>
    <topic domain="wwww" TID="handlesystem" crdate="20010316">
        <derived-from template="technology"/>
        <name>Handle System</name>
        <desc>The <topicref TID="handlesystem"/> is a comprehensive system for assigning, managing, and resolving persistent <topicref TID="identifier"/>s, known as "handles", for digital objects and other resources on the Internet. Handles can be used as <topicref TID="urn"/>s. The <topicref TID="handlesystem"/> includes an open set of <topicref TID="protocol"/>s, a name space, and an implementation of the <topicref TID="protocol"/>s. The <topicref TID="protocol"/>s enable a distributed computer system to store handles of digital resources and resolve those handles into the information necessary to locate and access the resources. This associated information can be changed as needed to reflect the current state of the identified resource without changing the handle, thus allowing the name of the item to persist over changes of location and other state information. Combined with a centrally administered naming authority registration service, the <topicref TID="handlesystem"/> provides a general purpose, distributed global naming service for the reliable management of information on networks over long periods of time.</desc>
    </topic>
    <topic domain="wwww" TID="w3c" crdate="20000607">
        <derived-from template="consortium"/>
        <name>W3C</name>
        <alias>World Wide Web Consortium</alias>
        <desc>Founded in 1994 to develop common <topicref TID="protocol"/>s for the evolution of the <topicref TID="www"/>, <topicref TID="w3c"/> is an international association of industrial and service companies, research laboratories, educational institutions, and organizations of all sizes. All of these organizations share a compelling interest in the long term evolution and stability of the <topicref TID="www"/>. <topicref TID="w3c"/> is a non-profit organization funded partly by commercial members. Its activities remain vendor neutral, however. <topicref TID="w3c"/> also receives the support of governments who consider the <topicref TID="www"/> the platform of choice for a global information infrastructure.</desc>
    </topic>
    <topic domain="wwww" TID="ifpi" crdate="20040107">
        <derived-from template="group"/>
        <name>IFPI</name>
        <alias>International Federation of Phonographic Industry</alias>
    </topic>
    <topic domain="wwww" TID="crf" crdate="20040107">
        <derived-from template="group"/>
        <name>CRF</name>
        <alias>Content Reference Forum</alias>
    </topic>
    <topic domain="wwww" TID="ggf" crdate="20031205">
        <derived-from template="group"/>
        <name>GGF</name>
        <alias>Global Grid Forum</alias>
    </topic>
    <topic domain="wwww" TID="oagi" crdate="20020902">
        <derived-from template="consortium"/>
        <name>OAGI</name>
        <alias>Open Applications Group</alias>
    </topic>
    <topic domain="wwww" TID="core" crdate="20020525">
        <derived-from template="consortium"/>
        <name>CORE</name>
        <alias>Council of Registrars</alias>
    </topic>
    <topic domain="wwww" TID="rtttl" crdate="20050918">
        <derived-from template="dataformat"/>
        <name>RTTTL</name>
        <alias>Ring Tone Text Transfer Language</alias>
    </topic>
    <topic domain="wwww" TID="minc" crdate="20020525">
        <derived-from template="consortium"/>
        <name>MINC</name>
        <alias>Multilingual Internet Names Consortium</alias>
    </topic>
    <topic domain="wwww" TID="weca" crdate="20020525">
        <derived-from template="consortium"/>
        <name>WECA</name>
        <alias>Wireless Ethernet Compatibility Alliance</alias>
        <status>On <text date="20021001"/>, <topicref TID="weca"/> has been renamed to <topicref TID="wifialliance"/>.</status>
    </topic>
    <topic domain="wwww" TID="wifialliance" crdate="20040102">
        <derived-from template="consortium"/>
        <name>Wi-Fi Alliance</name>
    </topic>
    <topic domain="wwww" TID="wifi" crdate="20020525">
        <derived-from template="topic"/>
        <name>Wi-Fi</name>
        <alias>Wireless Fidelity</alias>
        <desc><topicref TID="wifi"/> is a label for devices conforming to the <topicref TID="ieee80211b"/> standard for <topicref TID="wlan"/>. The <topicref TID="ieee80211b"/> standard has been published by the <topicref TID="ieee"/>, which does not perform conformance testing. In order to establish such a conformance testing process, the <topicref TID="wifialliance"/> (formerly known as <topicref TID="weca"/>) has been formed, which tests devices for conformance with the <topicref TID="ieee80211b"/> standard and issues the <topicref TID="wifi"/> label for conforming devices.</desc>
    </topic>
    <topic domain="wwww" TID="wmm" crdate="20060305">
        <derived-from template="topic"/>
        <name>WMM</name>
        <alias>Wi-Fi Multimedia</alias>
    </topic>
    <topic domain="wwww" TID="wimax" crdate="20041031">
        <derived-from template="topic"/>
        <name>WiMAX</name>
    </topic>
    <topic domain="wwww" TID="fipa" crdate="20011221">
        <derived-from template="consortium"/>
        <name>FIPA</name>
        <alias>Foundation for Intelligent Physical Agents</alias>
    </topic>
    <topic domain="wwww" TID="iptc" crdate="20011123">
        <derived-from template="organization"/>
        <name>IPTC</name>
        <alias>International Press Telecommunications Council</alias>
    </topic>
    <topic domain="wwww" TID="uncefact" crdate="20011129">
        <derived-from template="internationalorganization"/>
        <name>UN/CEFACT</name>
        <alias>United Nations Centre for Trade Facilitation and Electronic Business</alias>
    </topic>
    <topic domain="wwww" TID="isma" crdate="20011123">
        <derived-from template="organization"/>
        <name>ISMA</name>
        <alias>Internet Streaming Media Alliance</alias>
    </topic>
    <topic domain="wwww" TID="lisa" crdate="20040112">
        <derived-from template="consortium"/>
        <name>LISA</name>
        <alias>Localization Industry Standards Association</alias>
    </topic>
    <topic domain="wwww" TID="oasis" crdate="20000705">
        <derived-from template="consortium"/>
        <name>OASIS</name>
        <alias>Organization for the Advancement of Structured Information Standards</alias>
        <desc><topicref TID="oasis"/> is a nonprofit, international <topicref TID="consortium"/> dedicated to accelerating the adoption of product-independent formats based on public standards. These standards include <topicref TID="sgml"/>, <topicref TID="xml"/>, and <topicref TID="html"/> as well as others that are related to structured information processing. Members of <topicref TID="oasis"/> are providers, users, and specialists of the technologies that make these standards work in practice.</desc>
    </topic>
    <topic domain="wwww" TID="cals" crdate="20020622">
        <derived-from template="topic"/>
        <name>CALS</name>
        <alias>Computer-aided Acquisition and Logistic Support</alias>
    </topic>
    <topic domain="wwww" TID="calstable" crdate="20060305">
        <derived-from template="topic"/>
        <name>CALS Tables</name>
    </topic>
    <topic domain="wwww" TID="sdif" crdate="20011125">
        <derived-from template="dataformat"/>
        <name>SDIF</name>
        <alias>SGML Document Interchange Format</alias>
    </topic>
    <topic domain="wwww" TID="obi" crdate="20000705">
        <derived-from template="technology"/>
        <name>OBI</name>
        <alias>Open Buying on the Internet</alias>
    </topic>
    <topic domain="wwww" TID="swift" crdate="20010212">
        <derived-from template="technology"/>
        <name>SWIFT</name>
        <alias>Society for Worldwide Interbank Financial Transactions</alias>
    </topic>
    <topic domain="wwww" TID="ofx" crdate="20000705">
        <derived-from template="technology"/>
        <name>OFX</name>
        <alias>Open Financial Exchange</alias>
    </topic>
    <topic domain="wwww" TID="asa" crdate="20000818">
        <derived-from template="organization"/>
        <name>ASA</name>
        <alias>American Standards Association</alias>
    </topic>
    <topic domain="wwww" TID="wsi" crdate="20020522">
        <derived-from template="organization"/>
        <name>WS-I</name>
        <alias>Web Services Interoperability Organization</alias>
    </topic>
    <topic domain="wwww" TID="ansi" crdate="20000614">
        <derived-from template="nationalorganization"/>
        <name>ANSI</name>
        <alias>American National Standards Institute</alias>
        <desc><topicref TID="ansi"/>, founded in 1918, does not itself develop American National Standards; rather it facilitates development by establishing consensus among qualified groups. The Institute ensures that its guiding principles (consensus, due process, and openness) are followed by the more than 175 distinct entities currently accredited. <topicref TID="ansi"/> promotes the use of US standards internationally, advocates US policy and technical positions in international and regional standards organizations, and encourages the adoption of international standards as national standards where these meet the needs of the user community.</desc>
    </topic>
    <topic domain="wwww" TID="sox" crdate="20001208">
        <derived-from template="xmlschemalanguage"/>
        <name>SOX</name>
        <alias>Schema for Object-oriented XML</alias>
    </topic>
    <topic domain="wwww" TID="wddx" crdate="20000614">
        <derived-from template="technology"/>
        <name>WDDX</name>
        <alias>Web Distributed Data Exchange</alias>
    </topic>
    <topic domain="wwww" TID="ruby" crdate="20020605">
        <derived-from template="programminglanguage"/>
        <name>Ruby</name>
    </topic>
    <topic domain="wwww" TID="python" crdate="20010303">
        <derived-from template="programminglanguage"/>
        <name>Python</name>
        <desc><topicref TID="python"/> is an interpreted, interactive, object-oriented <topicref TID="programminglanguage"/>. The language has a concise syntax; a small number of powerful high-level data types are built in. <topicref TID="python"/> can be extended in a systematic fashion by adding new modules implemented in a compiled <topicref TID="programminglanguage"/> such as <topicref TID="c"/> or <topicref TID="cplusplus"/>. Such extension modules can define new functions and variables as well as new object types. <topicref TID="python"/> is frequently used for programming <topicref TID="cgi"/> applications.</desc>
    </topic>
    <topic domain="wwww" TID="zope" crdate="20010303">
        <derived-from template="product"/>
        <name>Zope</name>
        <alias>Z Object Publishing Environment</alias>
    </topic>
    <topic domain="wwww" TID="perl" crdate="20000811">
        <derived-from template="programminglanguage"/>
        <name>Perl</name>
        <alias>Practical Extraction and Report Language</alias>
        <desc><topicref TID="perl"/> is a general purpose interpreted <topicref TID="programminglanguage"/>, often used for scanning text and printing formatted reports. It provides extensive support for <topicref TID="regex"/> matching, dynamically scoped variables and functions, extensible run-time libraries, exception handling, and packages. <topicref TID="perl"/> is frequently used for programming <topicref TID="cgi"/> applications.</desc>
    </topic>
    <topic domain="wwww" TID="tcl" crdate="20000811">
        <derived-from template="programminglanguage"/>
        <name>Tcl</name>
        <alias>Tool Command Language</alias>
        <desc><topicref TID="tcl"/> is a general-purpose, robust <topicref TID="programminglanguage"/> that can easily be integrated into new applications. One of <topicref TID="tcl"/>'s most useful features is its extensibility. If an application requires some functionality not offered by standard <topicref TID="tcl"/>, new <topicref TID="tcl"/> commands can be implemented using the <topicref TID="c"/> language, and integrated fairly easily. Since <topicref TID="tcl"/> is so easy to extend, many people have written extension packages for common tasks, and made these freely available. <topicref TID="tcl"/> is frequently used for programming <topicref TID="cgi"/> applications.</desc>
    </topic>
    <topic domain="wwww" TID="tcltk" crdate="20000920">
        <derived-from template="programminglanguage"/>
        <name>Tcl/Tk</name>
        <alias>Tool Command Language/Tool Kit</alias>
    </topic>
    <topic domain="wwww" TID="del" crdate="20011112">
        <derived-from template="programminglanguage"/>
        <name>DEL</name>
        <alias>Data Extraction Language</alias>
        <desc><topicref TID="del"/> is an <topicref TID="xml"/> format for describing data conversion processes from other <topicref TID="dataformat"/>s to <topicref TID="xml"/>. A <topicref TID="del"/> script specifies how to locate and extract fragments from input data and where to insert them in the resulting <topicref TID="xml"/> format. The <topicref TID="del"/> processor executing the <topicref TID="del"/> script can use the extracted data to either create a new <topicref TID="xml"/> document or modify an existing <topicref TID="xml"/> document by creating new elements and attributes at locations specified with <topicref TID="xpath1"/> expressions.</desc>
    </topic>
    <topic domain="wwww" TID="gopher" crdate="20010305">
        <derived-from template="hmsystem"/>
        <name>Gopher</name>
        <desc>The <topicref TID="gopher"/> <topicref TID="protocol"/> is designed primarily to act as a distributed document delivery system. While documents (and services) reside on many <topicref TID="server"/>s, <topicref TID="gopher"/> <topicref TID="client"/> software presents users with a hierarchy of items and directories much like a file system. In fact, the <topicref TID="gopher"/> <topicref TID="interface"/> is designed to resemble a file system since a file system is a good model for locating documents and services. The user sees what amounts to one big networked information system containing primarily document items, directory items, and search items (the latter allowing searches for documents across subsets of the information base). Since the <topicref TID="www"/> allows greater flexibility in the structure and presentation of distributed information, the usage of gopher services and the number of gopher servers is getting smaller.</desc>
    </topic>
    <topic domain="wwww" TID="wais" crdate="20000920">
        <derived-from template="hmsystem"/>
        <name>WAIS</name>
        <alias>Wide Area Information Servers</alias>
        <desc><topicref TID="wais"/> is designed to help users find information over a computer network. The <topicref TID="wais"/> software architecture has four main components: the <topicref TID="client"/>, the <topicref TID="server"/>, the database, and the <topicref TID="protocol"/>. The <topicref TID="wais"/> <topicref TID="client"/> is a <topicref TID="ui"/> that sends requests for information to local or remote <topicref TID="server"/>s. The <topicref TID="wais"/> <topicref TID="server"/> is a program that services <topicref TID="client"/> requests. The <topicref TID="server"/> generally runs on a machine containing one or more information sources, or <topicref TID="wais"/> databases. The <topicref TID="protocol"/>, <topicref TID="z3950"/>-1988, is used to connect <topicref TID="wais"/> <topicref TID="client"/>s and <topicref TID="server"/>s and is based on the 1988 version of the <topicref TID="niso"/> <topicref TID="z3950"/> standard. Since the <topicref TID="www"/> allows greater flexibility in the structure and presentation of distributed information, the usage of <topicref TID="wais"/> services and the number of <topicref TID="wais"/> <topicref TID="server"/>s is getting smaller.</desc>
    </topic>
    <topic domain="wwww" TID="nls" crdate="20011209">
        <derived-from template="hmsystem"/>
        <name>NLS</name>
        <alias>Online System</alias>
    </topic>
    <topic domain="wwww" TID="ohs" crdate="20011122">
        <derived-from template="hmsystem"/>
        <name>OHS</name>
        <alias>Open Hypermedia System</alias>
    </topic>
    <topic domain="wwww" TID="www" crdate="20010216">
        <derived-from template="hmsystem"/>
        <name>WWW</name>
        <alias>World Wide Web</alias>
        <desc>The <topicref TID="www"/> is a distributed <topicref TID="hmsystem"/> which is built on top of some of the services provided by the <topicref TID="internet"/>. It is based on the <topicref TID="clientserver"/>, defining a <topicref TID="protocol"/> for the exchange of information between <topicref TID="www"/> <topicref TID="client"/>s and <topicref TID="server"/>s.</desc>
    </topic>
    <topic domain="wwww" TID="pcmcia" crdate="20001227">
        <derived-from template="organization"/>
        <name>PCMCIA</name>
        <alias>Personal Computer Memory Card International Association</alias>
    </topic>
    <topic domain="wwww" TID="pandd" crdate="20020716">
        <derived-from template="hwinterface"/>
        <name>P&amp;D</name>
        <alias>Plug &amp; Display</alias>
    </topic>
    <topic domain="wwww" TID="dfp" crdate="20020716">
        <derived-from template="hwinterface"/>
        <name>DFP</name>
        <alias>Digital Flat Panel</alias>
    </topic>
    <topic domain="wwww" TID="dp" crdate="20081127">
        <derived-from template="hwinterface"/>
        <name>DP</name>
        <alias>DisplayPort</alias>
    </topic>
    <topic domain="wwww" TID="hdmi" crdate="20081127">
        <derived-from template="hwinterface"/>
        <name>HDMI</name>
        <alias>High-Definition Multimedia Interface</alias>
    </topic>
    <topic domain="wwww" TID="gvif" crdate="20081127">
        <derived-from template="hwinterface"/>
        <name>GVIF</name>
        <alias>Gigabit Video Interface</alias>
    </topic>
    <topic domain="wwww" TID="udi" crdate="20081127">
        <derived-from template="hwinterface"/>
        <name>UDI</name>
        <alias>Unified Display Interface</alias>
    </topic>
    <topic domain="wwww" TID="dvi" crdate="20011123">
        <derived-from template="hwinterface"/>
        <name>DVI</name>
        <alias>Digital Visual Interface</alias>
    </topic>
    <topic domain="wwww" TID="ddwg" crdate="20011123">
        <derived-from template="organization"/>
        <name>DDWG</name>
        <alias>Digital Display Working Group</alias>
    </topic>
    <topic domain="wwww" TID="vesa" crdate="20010914">
        <derived-from template="organization"/>
        <name>VESA</name>
        <alias>Video Electronic Standards Association</alias>
    </topic>
    <topic domain="wwww" TID="php3" crdate="20010216">
        <derived-from template="php"/>
        <name>PHP3</name>
    </topic>
    <topic domain="wwww" TID="php4" crdate="20010216">
        <derived-from template="php"/>
        <name>PHP4</name>
    </topic>
    <topic domain="wwww" TID="php5" crdate="20060919">
        <derived-from template="php"/>
        <name>PHP5</name>
    </topic>
    <topic domain="wwww" TID="php" crdate="20000621">
        <derived-from template="serversidetechnology"/>
        <name>PHP</name>
        <alias>PHP Hypertext Preprocessor</alias>
        <desc><topicref TID="php"/> is an <topicref TID="html"/>-embedded scripting language. Much of its syntax is borrowed from <topicref TID="c"/>, <topicref TID="java"/>, and <topicref TID="perl"/>, with the addition of a couple of unique <topicref TID="php"/>-specific features. The goal of the language is to allow <topicref TID="www"/> developers to write dynamically generated <topicref TID="html"/> pages quickly. <topicref TID="php"/> is either executed as a <topicref TID="cgi"/> script, or it is integrated into <topicref TID="httpserver"/> software, for example as an <topicref TID="apachehttp"/> module.</desc>
    </topic>
    <topic domain="wwww" TID="zpt" crdate="20021115">
        <derived-from template="serversidetechnology"/>
        <name>ZPT</name>
        <alias>Zope Page Templates</alias>
    </topic>
    <topic domain="wwww" TID="dtml" crdate="20021115">
        <derived-from template="serversidetechnology"/>
        <name>DTML</name>
        <alias>Document Template Markup Language</alias>
    </topic>
    <topic domain="wwww" TID="saas" crdate="20060524">
        <derived-from template="concept"/>
        <name>SaaS</name>
        <alias>Software as a Service</alias>
    </topic>
    <topic domain="wwww" TID="asp2" crdate="20010811">
        <derived-from template="concept"/>
        <name>ASP</name>
        <alias>Application Service Provider</alias>
        <desc>An <topicref TID="asp2"/> is providing an application to be used by <topicref TID="asp2"/> customers. In contrast to traditional software distribution, the software that provides the service is run by the <topicref TID="asp2"/>, and it is accessed remotely (and thus never downloaded or installed) by the customers. A common way for providing such services is over the <topicref TID="www"/>, where the application is accessed via various <topicref TID="html"/> pages which in their entirety make up the <topicref TID="gui"/>. One of the best known <topicref TID="asp2"/>s is HotMail, which makes an <topicref TID="email"/> application available over the <topicref TID="www"/>.</desc>
    </topic>
    <topic domain="wwww" TID="jelly" crdate="20030526">
        <derived-from template="xmlpipelinelanguage"/>
        <name>Jelly</name>
    </topic>
    <topic domain="wwww" TID="asp" crdate="20000621">
        <derived-from template="serversidetechnology"/>
        <name>ASP</name>
        <alias>Active Server Pages</alias>
    </topic>
    <topic domain="wwww" TID="xsp" modate="20030114" crdate="20000621">
        <derived-from template="serversidetechnology"/>
        <name>XSP</name>
        <alias>Extensible Server Pages</alias>
        <desc><topicref TID="xsp"/> is <topicref TID="cocoon"/>'s technology for building <topicref TID="www"/> applications based on dynamic <topicref TID="xml"/> content. An <topicref TID="xsp"/> page is a <topicref TID="cocoon"/> <topicref TID="xml"/> document containing tag-based directives that specify how to generate dynamic content at request time. Upon <topicref TID="cocoon"/> processing, these directives are replaced by generated content so that the resulting, augmented <topicref TID="xml"/> document can be subject to further processing (typically an <topicref TID="xslt"/> transformation). <topicref TID="xsp"/> pages are transformed into <topicref TID="cocoon"/> producers, typically as <topicref TID="java"/> classes, though any scripting language for which a <topicref TID="java"/>-based processor exists could also be used. Directives can be either <topicref TID="xsp"/> built-in processing tags or user-defined library tags. <topicref TID="xsp"/> built-in tags are used to embed procedural logic, substitute expressions and dynamically build <topicref TID="xml"/> nodes. User-defined library tags act as templates that dictate how program code is generated from information encoded in each dynamic tag.
        </desc>
    </topic>
    <topic domain="wwww" TID="xmlapi" crdate="20080331">
        <derived-from template="api"/>
        <name>XML API</name>
        <desc>An <topicref TID="xmlapi"/> is an <topicref TID="api"/> that is designed to provide programmatic access to <topicref TID="xml"/> data. In many cases, this access will use abstractions such as the <topicref TID="xmlinfoset"/>, but the general concept of an <topicref TID="xmlapi"/> does not restrict the particular "view" that an <topicref TID="api"/> provides of <topicref TID="xml"/> data. Furthermore, an <topicref TID="xmlapi"/> might also include additional functionality such as validation against an <topicref TID="xmlschemalanguage">XML schema</topicref>, or advanced <topicref TID="xml"/> access through specific languages such as <topicref TID="xpath"/>.</desc>
    </topic>
    <topic domain="wwww" TID="xmlschemaapi" crdate="20061005">
        <derived-from template="api"/>
        <name>XML Schema API</name>
    </topic>
    <topic domain="wwww" TID="cgi" crdate="20000614">
        <derived-from template="api"/>
        <name>CGI</name>
        <alias>Common Gateway Interface</alias>
        <desc><topicref TID="cgi"/> is an <topicref TID="api"/> for interfacing external applications with information <topicref TID="server"/>s, such as an <topicref TID="httpserver"/>. <topicref TID="cgi"/> can be used with any <topicref TID="programminglanguage"/>. A plain <topicref TID="html"/> document that the <topicref TID="httpserver"/> retrieves upon a request is static, which means it exists in a constant state, for example as a text file that does not change. A <topicref TID="cgi"/> program, on the other hand, is executed in real-time, so that it can generate dynamic information.</desc>
    </topic>
    <topic domain="wwww" TID="fastcgi" crdate="20000614">
        <derived-from template="protocol"/>
        <name>FastCGI</name>
        <desc><topicref TID="fastcgi"/> is an extension of the <topicref TID="cgi"/> which eliminates its drawbacks and provides high performance, while remaining highly compatible with existing <topicref TID="cgi"/> applications. <topicref TID="fastcgi"/> is conceptually very similar to <topicref TID="cgi"/>, with two major differences. As the first difference, <topicref TID="fastcgi"/> processes are persistent, after finishing a request, they wait for a new request instead of exiting. The second difference is that, instead of using <topicref TID="os"/> environment variables and pipes, the <topicref TID="fastcgi"/> protocol multiplexes the environment information, standard input, output and error over a single full-duplex connection. This allows <topicref TID="fastcgi"/> programs to run on remote machines, using <topicref TID="tcp"/> connections between the <topicref TID="httpserver"/> and the <topicref TID="fastcgi"/> application.</desc>
    </topic>
    <topic domain="wwww" TID="md2" crdate="20000614">
        <derived-from template="chf"/>
        <name>MD2</name>
        <alias>Message Digest 2</alias>
        <desc>The <topicref TID="md2"/> <topicref TID="algorithm"/> takes as input a message of arbitrary length and produces as output a 128-bit "fingerprint" or "message digest" of the input. It is conjectured that it is computationally infeasible to produce two messages having the same message digest, or to produce any message having a given pre-specified target message digest. <topicref TID="md2"/> is optimized for 8-bit machines and intended for digital signature applications, where a large file must be "compressed" in a secure manner before being encrypted with a private key under a <topicref TID="pkc"/> system such as <topicref TID="rsa"/>.</desc>
    </topic>
    <topic domain="wwww" TID="md4" modate="20020716" crdate="20000614">
        <derived-from template="chf"/>
        <name>MD4</name>
        <alias>Message Digest 4</alias>
        <desc>The <topicref TID="md4"/> <topicref TID="algorithm"/> takes as input a message of arbitrary length and produces as output a 128-bit "fingerprint" or "message digest" of the input. It is conjectured that it is computationally infeasible to produce two messages having the same message digest, or to produce any message having a given pre-specified target message digest. <topicref TID="md4"/> is aimed at 32-bit machines and intended for digital signature applications, where a large file must be "compressed" in a secure manner before being encrypted with a private key under a <topicref TID="pkc"/> system such as <topicref TID="rsa"/>.</desc>
        <status>It has been shown how collisions for the full version of <topicref TID="md4"/> can be found in under a minute on a typical PC. Therefore, <topicref TID="md4"/> should now be considered broken.</status>
    </topic>
    <topic domain="wwww" TID="md5" crdate="20000612">
        <derived-from template="chf"/>
        <name>MD5</name>
        <alias>Message Digest 5</alias>
        <desc>The <topicref TID="md5"/> <topicref TID="algorithm"/> takes as input a message of arbitrary length and produces as output a 128-bit "fingerprint" or "message digest" of the input. It is conjectured that it is computationally infeasible to produce two messages having the same message digest, or to produce any message having a given pre-specified target message digest. <topicref TID="md5"/> is aimed at 32-bit machines and intended for digital signature applications, where a large file must be "compressed" in a secure manner before being encrypted with a private key under a <topicref TID="pkc"/> system such as <topicref TID="rsa"/>.</desc>
    </topic>
    <topic domain="wwww" TID="hmac" crdate="20010811">
        <derived-from template="chf"/>
        <name>HMAC</name>
        <alias>Hashed Message Authentication Code</alias>
    </topic>
    <topic domain="wwww" TID="wcag" crdate="20020822">
        <derived-from template="technology"/>
        <name>WCAG</name>
        <alias>Web Content Accessibility Guidelines</alias>
    </topic>
    <topic domain="wwww" TID="atag" crdate="20020822">
        <derived-from template="technology"/>
        <name>ATAG</name>
        <alias>Authouring Tools Accessibility Guidelines</alias>
    </topic>
    <topic domain="wwww" TID="uaag" crdate="20020822">
        <derived-from template="technology"/>
        <name>UAAG</name>
        <alias>User Agent Accessibility Guidelines</alias>
    </topic>
    <topic domain="wwww" TID="wai" crdate="20000705">
        <derived-from template="group"/>
        <name>WAI</name>
        <alias>Web Accessibility Initiative</alias>
    </topic>
    <topic domain="wwww" TID="chunk" crdate="20010811">
        <derived-from template="dataformat"/>
        <name>Chunked Encoding</name>
        <desc>With the introduction of persistent connections in <topicref TID="http"/>/1.1, the length of a resource which is sent in a response can no longer be implicitly signaled by closing the connection. However, for the majority of resources, the length is known in advance and can be given in the <topicref TID="http"/>'s Content-Length header field. For all other resources (such as dynamically created content), <topicref TID="chunk"/> can be used. <topicref TID="chunk"/> transfers the message body as a sequence of chunks of known length.</desc>
    </topic>
    <topic domain="wwww" TID="base16" crdate="20010424">
        <derived-from template="dataformat"/>
        <name>Base16</name>
    </topic>
    <topic domain="wwww" TID="base32" crdate="20010424">
        <derived-from template="dataformat"/>
        <name>Base32</name>
    </topic>
    <topic domain="wwww" TID="base64" crdate="20010307">
        <derived-from template="dataformat"/>
        <name>Base64</name>
        <desc><topicref TID="base64"/> encoding is designed to represent arbitrary sequences of octets in a form that need not be humanly readable. The encoding and decoding <topicref TID="algorithm"/>s are simple, but the encoded data are consistently only about 33 percent larger than the unencoded data. In <topicref TID="base64"/>, a 65-character subset of <topicref TID="ascii"/> is used, enabling 6 bits to be represented per printable character. <topicref TID="base64"/> is virtually identical to the encoding used in <topicref TID="pem"/> applications.</desc>
    </topic>
    <topic domain="wwww" TID="crisp" crdate="20040211">
        <derived-from template="protocol"/>
        <name>CRISP</name>
        <alias>Cross Registry Internet Service Protocol</alias>
    </topic>
    <topic domain="wwww" TID="lbap" crdate="20030205">
        <derived-from template="protocol"/>
        <name>LBAP</name>
        <alias>Linkbase Access Protocol</alias>
    </topic>
    <topic domain="wwww" TID="giop" crdate="20000615">
        <derived-from template="protocol"/>
        <name>GIOP</name>
        <alias>General Inter-ORB Protocol</alias>
        <desc><topicref TID="giop"/> is the abstract <topicref TID="protocol"/> which is used for communications between <topicref TID="corba"/> <topicref TID="orb"/>s. It specifies the transfer syntax and a standard set of message formats for <topicref TID="orb"/> interoperation over any connection-oriented transport <topicref TID="protocol"/>. <topicref TID="giop"/> is designed to be simple and easy to implement, while still allowing for reasonable scalability and performance.</desc>
    </topic>
    <topic domain="wwww" TID="captcha" crdate="20051125">
        <derived-from template="concept"/>
        <name>CAPTCHA</name>
        <alias>Completely Automated Public Turing test to tell Computers and Humans Apart</alias>
    </topic>
    <topic domain="wwww" TID="ecommerce" crdate="20010317">
        <derived-from template="concept"/>
        <name>E-Commerce</name>
        <alias>Electronic Commerce</alias>
    </topic>
    <topic domain="wwww" TID="stp" crdate="20020212">
        <derived-from template="concept"/>
        <name>STP</name>
        <alias>Straight Through Processing</alias>
    </topic>
    <topic domain="wwww" TID="b2b" crdate="20000727">
        <derived-from template="concept"/>
        <name>B2B</name>
        <alias>Business-to-Business</alias>
        <desc><topicref TID="b2b"/> is the use of computer applications communicating over networks to allow businesses to complete a transaction or part of a transaction. In contrast to <topicref TID="b2c"/>, <topicref TID="b2b"/> describes the interaction of businesses. While the amount of <topicref TID="b2c"/> transactions using <topicref TID="www"/>-based technologies (often called online shopping) exceeds the amount <topicref TID="b2b"/> transactions, the total value of the <topicref TID="b2b"/> transactions is much larger than that of the <topicref TID="b2c"/> transactions, because typically <topicref TID="b2b"/> transactions are of much greater value than <topicref TID="b2c"/> transactions.</desc>
    </topic>
    <topic domain="core" TID="ac" crdate="20050620">
        <derived-from template="concept"/>
        <name>Access Control</name>
    </topic>
    <topic domain="wwww" TID="mac2" crdate="20050620">
        <derived-from template="ac"/>
        <name>MAC</name>
        <alias>Mandatory Access Control</alias>
    </topic>
    <topic domain="wwww" TID="dac" crdate="20050620">
        <derived-from template="ac"/>
        <name>DAC</name>
        <alias>Discretionary Access Control</alias>
    </topic>
    <topic domain="wwww" TID="rbac" crdate="20050620">
        <derived-from template="ac"/>
        <name>RBAC</name>
        <alias>Role Based Access Control</alias>
    </topic>
    <topic domain="wwww" TID="tbac" crdate="20050620">
        <derived-from template="ac"/>
        <name>TBAC</name>
        <alias>Task Based Access Control</alias>
    </topic>
    <topic domain="wwww" TID="tmac" crdate="20050620">
        <derived-from template="ac"/>
        <name>TMAC</name>
        <alias>Team Based Access Control</alias>
    </topic>
    <topic domain="wwww" TID="acl" crdate="20050620">
        <derived-from template="ac"/>
        <name>ACL</name>
        <alias>Access Control List</alias>
    </topic>
    <topic domain="wwww" TID="tpm" crdate="20040211">
        <derived-from template="concept"/>
        <name>TPM</name>
        <alias>Trusted Platform Module</alias>
    </topic>
    <topic domain="wwww" TID="b2c" crdate="20000727">
        <derived-from template="concept"/>
        <name>B2C</name>
        <alias>Business-to-Consumer</alias>
    </topic>
    <topic domain="wwww" TID="iiop" crdate="20000615">
        <derived-from template="giop"/>
        <name>IIOP</name>
        <alias>Internet Inter-ORB Protocol</alias>
        <desc><topicref TID="iiop"/> is the most commonly used <topicref TID="protocol"/> for communications in <topicref TID="corba"/>. <topicref TID="iiop"/> is a <topicref TID="protocol"/> for the <topicref TID="clientserver"/> between two <topicref TID="corba"/> implementations. In a similar way to <topicref TID="http"/>, which uses <topicref TID="uri"/>s to locate <topicref TID="server"/>s and in requests from <topicref TID="client"/>s to <topicref TID="server"/>s, <topicref TID="corba"/> uses an <topicref TID="ior"/> for identifying remote objects. <topicref TID="ior"/>s can be used to invoke operations on remote <topicref TID="corba"/> systems, using <topicref TID="iiop"/> for communications.</desc>
    </topic>
    <topic domain="wwww" TID="ior" crdate="20000723">
        <derived-from template="identifier"/>
        <name>IOR</name>
        <alias>Interoperable Object Reference</alias>
        <desc>An <topicref TID="ior"/> is a data structure that stores information needed to locate and communicate with a <topicref TID="corba"/> object over one or more <topicref TID="protocol"/>s. For example, an <topicref TID="ior"/> containing <topicref TID="iiop"/> information stores <topicref TID="ipaddress"/> and <topicref TID="tcp"/> <topicref TID="port"/> number information.</desc>
    </topic>
    <topic domain="wwww" TID="xaml" crdate="20031227">
        <derived-from template="dataformat"/>
        <name>XAML</name>
        <alias>Extensible Application Markup Language</alias>
    </topic>
    <topic domain="wwww" TID="auiml" crdate="20040220">
        <derived-from template="dataformat"/>
        <name>AUIML</name>
        <alias>Abstract User Interface Markup Language</alias>
        <desc><topicref TID="auiml"/> is an <topicref TID="xml"/> dialect that is a platform and a technology-neutral representation of panels, wizards, property sheets, etc. <topicref TID="auiml"/> captures relative positioning information of <topicref TID="gui"/> components and delegates their display to a platform-specific renderer. Depending on the platform or device being used, the renderer decides the best way to present the <topicref TID="gui"/> to the user and receive user input. <topicref TID="auiml"/> allows developers to write an application once and run it in <topicref TID="swing"/> or on the <topicref TID="www"/> without any changes.</desc>
    </topic>
    <topic domain="wwww" TID="xbel" crdate="20050621">
        <derived-from template="dataformat"/>
        <name>XBEL</name>
        <alias>XML Bookmark Exchange Language</alias>
    </topic>
    <topic domain="wwww" TID="xbl" crdate="20040220">
        <derived-from template="dataformat"/>
        <name>XBL</name>
        <alias>XML Binding Language</alias>
    </topic>
    <topic domain="wwww" TID="xul" crdate="20020626">
        <derived-from template="dataformat"/>
        <name>XUL</name>
        <alias>XML-based User Interface Language</alias>
    </topic>
    <topic domain="wwww" TID="xacl" crdate="20040802">
        <derived-from template="dataformat"/>
        <name>XACL</name>
        <alias>Extensible Access Control Language</alias>
        <status><topicref TID="xacl"/> is no longer under development and has been integrated into <topicref TID="xacml"/>.</status>
    </topic>
    <topic domain="wwww" TID="xacml" crdate="20021108">
        <derived-from template="dataformat"/>
        <name>XACML</name>
        <alias>Extensible Access Control Markup Language</alias>
    </topic>
    <topic domain="wwww" TID="bpml" crdate="20030220">
        <derived-from template="dataformat"/>
        <name>BPML</name>
        <alias>Business Process Modelling Language</alias>
    </topic>
    <topic domain="wwww" TID="wsbpel" crdate="20082810">
        <derived-from template="dataformat"/>
        <name>WS-BPEL</name>
        <alias>Web Service Business Process Execution Language</alias>
    </topic>
    <topic domain="wwww" TID="bpel" crdate="20082810">
        <derived-from template="dataformat"/>
        <name>BPEL</name>
        <alias>Business Process Execution Language</alias>
    </topic>
    <topic domain="wwww" TID="bpel4ws" crdate="20030220">
        <derived-from template="dataformat"/>
        <name>BPEL4WS</name>
        <alias>Business Process Execution Language for Web Services</alias>
        <status><topicref TID="bpel4ws"/> represents the uniting of two previously competing standards: <topicref TID="wsfl"/> from <topicref TID="ibm"/>, and <topicref TID="microsoft"/>'s <topicref TID="xlang"/>.</status>
    </topic>
    <topic domain="wwww" TID="bpmi" crdate="20030220">
        <derived-from template="organization"/>
        <name>BPMI</name>
        <alias>Business Process Management Initiative</alias>
    </topic>
    <topic domain="wwww" TID="qti" crdate="20050526">
        <derived-from template="dataformat"/>
        <name>QTI</name>
        <alias>Question and Test Interoperability</alias>
    </topic>
    <topic domain="wwww" TID="hdml" crdate="20011202">
        <derived-from template="dataformat"/>
        <name>HDML</name>
        <alias>Handheld Device Markup Language</alias>
    </topic>
    <topic domain="wwww" TID="ximl" crdate="20070426">
        <derived-from template="dataformat"/>
        <name>XIML</name>
        <alias>Extensible Interface Markup Language</alias>
    </topic>
    <topic domain="wwww" TID="uiml" crdate="20000723">
        <derived-from template="dataformat"/>
        <name>UIML</name>
        <alias>User Interface Markup Language</alias>
    </topic>
    <topic domain="wwww" TID="orb" crdate="20000615">
        <derived-from template="technology"/>
        <name>ORB</name>
        <alias>Object Request Broker</alias>
        <desc>The <topicref TID="orb"/> is the key component of the <topicref TID="corba"/> programming model. An <topicref TID="orb"/> is responsible for transferring operations from <topicref TID="client"/>s to <topicref TID="server"/>s. This requires the <topicref TID="orb"/> to locate a <topicref TID="server"/> implementation (and possibly activate it), transmit the operation and its parameters, and finally return the results back to the <topicref TID="client"/>.</desc>
    </topic>
    <topic domain="wwww" TID="intranet" crdate="20031107">
        <derived-from template="concept"/>
        <name>Intranet</name>
        <desc>An <topicref TID="intranet"/> is a network which uses the <topicref TID="internet"/> <topicref TID="protocol"/> suite on top of its networking system, but is internal to some <topicref TID="organization"/>. In most cases, an <topicref TID="intranet"/> is connected to the <topicref TID="internet"/>, but an <topicref TID="intranet"/> can also be operated as a standalone network. Islands of <topicref TID="intranet"/>s can be connected by using <topicref TID="vpn"/> technologies to form a virtual <topicref TID="intranet"/> spanning the isolated parts.</desc>
    </topic>
    <topic domain="wwww" TID="internet" crdate="20010309">
        <derived-from template="topic"/>
        <name>Internet</name>
        <desc>The <topicref TID="internet"/> is the entirety of all computers which are interconnected (using various physical <topicref TID="network"/>ing techniques) and employ the <topicref TID="internet"/> <topicref TID="protocol"/> suite on top of their networking systems.</desc>
    </topic>
    <topic domain="wwww" TID="odmg" crdate="20020417">
        <derived-from template="group"/>
        <name>ODMG</name>
        <alias>Object Data Management Group</alias>
    </topic>
    <topic domain="wwww" TID="omg" crdate="20000621">
        <derived-from template="group"/>
        <name>OMG</name>
        <alias>Object Management Group</alias>
        <desc>Established in 1989, <topicref TID="omg"/> promotes the theory and practice of object technology for the development of distributed computing systems. The goal is to provide a common architectural framework for object oriented applications based on widely available interface specifications. <topicref TID="omg"/> has a membership of over 800 software vendors, software developers, and end users. <topicref TID="corba"/> is standardized by the <topicref TID="omg"/>.</desc>
    </topic>
    <topic domain="wwww" TID="icann" crdate="20000920">
        <derived-from template="organization"/>
        <name>ICANN</name>
        <alias>Internet Corporation for Assigned Names and Numbers</alias>
    </topic>
    <topic domain="wwww" TID="mda" crdate="20031216">
        <derived-from template="technology"/>
        <name>MDA</name>
        <alias>Model Driven Architecture</alias>
    </topic>
    <topic domain="wwww" TID="pim2" crdate="20060516">
        <derived-from template="concept"/>
        <name>PIM</name>
        <alias>Platform-Independent Model</alias>
    </topic>
    <topic domain="wwww" TID="psm" crdate="20060516">
        <derived-from template="concept"/>
        <name>PSM</name>
        <alias>Platform-Specific Model</alias>
    </topic>
    <topic domain="wwww" TID="mtl" crdate="20060516">
        <derived-from template="concept"/>
        <name>MTL</name>
        <alias>Model Transformation Language</alias>
    </topic>
    <topic domain="wwww" TID="viatra" crdate="20060516">
        <derived-from template="mtl"/>
        <name>VIATRA</name>
        <alias>Visual Automated Model Transformations</alias>
    </topic>
    <topic domain="wwww" TID="great" crdate="20060516">
        <derived-from template="mtl"/>
        <name>GReAT</name>
        <alias>Graph Rewriting and Transformation</alias>
    </topic>
    <topic domain="wwww" TID="cwm" crdate="20031216">
        <derived-from template="technology"/>
        <name>CWM</name>
        <alias>Common Warehouse Metamodel</alias>
    </topic>
    <topic domain="wwww" TID="mof" crdate="20000621">
        <derived-from template="technology"/>
        <name>MOF</name>
        <alias>Meta Object Facility</alias>
    </topic>
    <topic domain="wwww" TID="p2p" modate="20020716" crdate="20010817">
        <derived-from template="concept"/>
        <name>P2P</name>
        <alias>Peer to Peer</alias>
        <desc><topicref TID="p2p"/> networking is a network model where, depending on an operation's context, any node can operate as either a <topicref TID="server"/> or a <topicref TID="client"/>. <topicref TID="p2p"/> provides certain interesting capabilities not possible in traditional <topicref TID="clientserver"/> networks, which have predefined <topicref TID="server"/> or <topicref TID="client"/> roles for their nodes.</desc>
    </topic>
    <topic domain="core" TID="cscw" crdate="20010314">
        <derived-from template="concept"/>
        <name>CSCW</name>
        <alias>Computer Supported Cooperative Work</alias>
    </topic>
    <topic domain="core" TID="oop" crdate="20040311" modate="20051121">
        <derived-from template="concept"/>
        <name>OOP</name>
        <alias>Object-Oriented Programming</alias>
        <desc><topicref TID="oop"/> is the act of applying the principles of <topicref TID="oo"/> in a given programming environment. <topicref TID="oop"/> does not necessarily have to be practiced using an object-oriented <topicref TID="programminglanguage"/>, but object-oriented <topicref TID="programminglanguage"/>s facilitate <topicref TID="oop"/> by providing language constructs for the main concepts of <topicref TID="oo"/>, which are encapsulation, inheritance, and polymorphism.</desc>
    </topic>
    <topic domain="core" TID="aop" crdate="20040311">
        <derived-from template="concept"/>
        <name>AOP</name>
        <alias>Aspect-Oriented Programming</alias>
    </topic>
    <topic domain="core" TID="dip" crdate="20040311">
        <derived-from template="concept"/>
        <name>DIP</name>
        <alias>Dependency Inversion Principle</alias>
    </topic>
    <topic domain="core" TID="ocp" crdate="20040311">
        <derived-from template="concept"/>
        <name>OCP</name>
        <alias>Open Closed Principle</alias>
    </topic>
    <topic domain="core" TID="lsp" crdate="20040311">
        <derived-from template="concept"/>
        <name>LSP</name>
        <alias>Liskov Substitution Principle</alias>
    </topic>
    <topic domain="core" TID="isp" crdate="20040311">
        <derived-from template="concept"/>
        <name>ISP</name>
        <alias>Interface Segregation Principle</alias>
    </topic>
    <topic domain="core" TID="soc" crdate="20040311">
        <derived-from template="concept"/>
        <name>SOC</name>
        <alias>Separation Of Concerns</alias>
    </topic>
    <topic domain="wwww" TID="jxta" crdate="20020716">
        <derived-from template="framework"/>
        <name>JXTA</name>
    </topic>
    <topic domain="wwww" TID="jnlp" crdate="20040824">
        <derived-from template="protocol"/>
        <name>JNLP</name>
        <alias>Java Network Launching Protocol</alias>
    </topic>
    <topic domain="wwww" TID="odp" crdate="20010314">
        <derived-from template="framework"/>
        <name>ODP</name>
        <alias>Open Distributed Processing</alias>
    </topic>
    <topic domain="wwww" TID="oagis" crdate="20020902">
        <derived-from template="dataformat"/>
        <name>OAGIS</name>
        <alias>Open Applications Group Integration Specification</alias>
    </topic>
    <topic domain="wwww" TID="idl" crdate="20000621">
        <derived-from template="dataformat"/>
        <name>IDL</name>
        <alias>Interface Definition Language</alias>
    </topic>
    <topic domain="wwww" TID="corba" crdate="20000615">
        <derived-from template="framework"/>
        <name>CORBA</name>
        <alias>Common Object Request Broker Architecture</alias>
        <desc><topicref TID="corba"/> describes the architecture of a middleware platform that supports the implementation of applications in distributed and heterogeneous environments. The <topicref TID="corba"/> standard is issued by <topicref TID="omg"/>. In contrast to other middleware platforms such as <topicref TID="microsoft"/>'s <topicref TID="dcom"/>, <topicref TID="corba"/> is a specification that does not prescribe any specific technology.</desc>
    </topic>
    <topic domain="wwww" TID="san" crdate="20011207">
        <derived-from template="network"/>
        <name>SAN</name>
        <alias>Storage Area Network</alias>
    </topic>
    <topic domain="wwww" TID="vpn" modate="20031107" crdate="20020628">
        <derived-from template="network"/>
        <name>VPN</name>
        <alias>Virtual Private Network</alias>
        <desc>A <topicref TID="vpn"/> is a private <topicref TID="network"/> (often an <topicref TID="intranet"/>) that makes use of the public telecommunication infrastructure, maintaining privacy through the use of a tunneling <topicref TID="protocol"/> and security procedures. A <topicref TID="vpn"/> can be contrasted with a system of owned or leased lines that can only be used by one company. The main purpose of a <topicref TID="vpn"/> is to give the company the same capabilities as private leased lines at much lower cost by using the shared public infrastructure.</desc>
    </topic>
    <topic domain="wwww" TID="lan" crdate="20000914">
        <derived-from template="network"/>
        <name>LAN</name>
        <alias>Local Area Network</alias>
    </topic>
    <topic domain="wwww" TID="wpan" crdate="20020626">
        <derived-from template="network"/>
        <derived-from template="wlinterface"/>
        <name>WPAN</name>
        <alias>Wireless Personal Area Network</alias>
    </topic>
    <topic domain="wwww" TID="wlan" modate="20020716" crdate="20020624">
        <derived-from template="lan"/>
        <derived-from template="wlinterface"/>
        <name>WLAN</name>
        <alias>Wireless LAN</alias>
        <desc>A <topicref TID="wlan"/> is a <topicref TID="lan"/> that is based on a <topicref TID="wlinterface"/>. <topicref TID="wlan"/> technology makes using <topicref TID="lan"/>s easier, because users can roam within the coverage area of the <topicref TID="wlan"/> without having to deal with cables.</desc>
    </topic>
    <topic domain="wwww" TID="man" crdate="20000914">
        <derived-from template="network"/>
        <name>MAN</name>
        <alias>Metropolitan Area Network</alias>
    </topic>
    <topic domain="wwww" TID="wan" crdate="20000914">
        <derived-from template="network"/>
        <name>WAN</name>
        <alias>Wide Area Network</alias>
    </topic>
    <topic domain="wwww" TID="dtm" crdate="20020828">
        <derived-from template="wan"/>
        <name>DTM</name>
        <alias>Dynamic Synchronous Transfer Mode</alias>
    </topic>
    <topic domain="wwww" TID="atm" crdate="20000914">
        <derived-from template="wan"/>
        <name>ATM</name>
        <alias>Asynchronous Transfer Mode</alias>
    </topic>
    <topic domain="wwww" TID="atmforum" crdate="20000914">
        <derived-from template="consortium"/>
        <name>ATM Forum</name>
    </topic>
    <topic domain="wwww" TID="blob" crdate="20030515">
        <derived-from template="concept"/>
        <name>BLOB</name>
        <alias>Binary Large Object</alias>
        <desc>A <topicref TID="blob"/> is a concept for storing large quantities of unstructured data in a <topicref TID="dbms"/>. A <topicref TID="blob"/> is unstructured as seen from the perspective of the <topicref TID="dbms"/>'s <topicref TID="datamodel"/>, but it often has some well-known internal structure (for example a particular <topicref TID="imageformat"/> when storing images in a <topicref TID="dbms"/>).</desc>
    </topic>
    <topic domain="wwww" TID="dmz" crdate="20031107">
        <derived-from template="concept"/>
        <name>DMZ</name>
        <alias>Demilitarized Zone</alias>
        <desc>A <topicref TID="dmz"/> is a part of an (or the complete) <topicref TID="intranet"/> which is assumed to match a security standard superior to the network outside of the <topicref TID="dmz"/>. A <topicref TID="dmz"/> usually is separated from other networks (less secure parts of the <topicref TID="intranet"/> and/or the <topicref TID="internet"/>) by a <topicref TID="firewall"/> or a similar way of filtering out potentially harmful network traffic.</desc>
    </topic>
    <topic domain="wwww" TID="mpls" crdate="20020628">
        <derived-from template="concept"/>
        <name>MPLS</name>
        <alias>Multiprotocol Label Switching</alias>
    </topic>
    <topic domain="wwww" TID="ipr" crdate="20021015">
        <derived-from template="concept"/>
        <name>IPR</name>
        <alias>Intellectual Property Rights</alias>
        <desc><topicref TID="ipr"/> are temporary grants of monopoly intended to give economic incentives for innovative activity. <topicref TID="ipr"/> exist in the form of patents, copyrights, and trademarks.</desc>
    </topic>
    <topic domain="wwww" TID="fsx" crdate="20060214">
        <derived-from template="dataformat"/>
        <name>FSX</name>
        <alias>File System XML</alias>
    </topic>
    <topic domain="wwww" TID="sysml" crdate="20060210">
        <derived-from template="modelinglanguage"/>
        <name>SysML</name>
        <alias>Systems Modeling Language</alias>
    </topic>
    <topic domain="wwww" TID="uml" crdate="20000621">
        <derived-from template="modelinglanguage"/>
        <name>UML</name>
        <alias>Unified Modeling Language</alias>
    </topic>
    <topic domain="wwww" TID="ocl" crdate="20030712">
        <derived-from template="modelinglanguage"/>
        <name>OCL</name>
        <alias>Object Constraint Language</alias>
    </topic>
    <topic domain="wwww" TID="niam" crdate="20051128">
        <derived-from template="modelinglanguage"/>
        <name>NIAM</name>
        <alias>Natural Language Information Analysis Method</alias>
    </topic>
    <topic domain="wwww" TID="orm" crdate="20051128" modate="20060305">
        <derived-from template="datamodel"/>
        <name>ORM</name>
        <alias>Object-Relational Model</alias>
    </topic>
    <topic domain="wwww" TID="rm" crdate="20060305">
        <derived-from template="datamodel"/>
        <name>RM</name>
        <alias>Relational Model</alias>
    </topic>
    <topic domain="wwww" TID="hner" crdate="20060411">
        <derived-from template="datamodel"/>
        <name>HNER</name>
        <alias>Heterogeneous Nested Entity Relationship</alias>
    </topic>
    <topic domain="wwww" TID="hnr" crdate="20060305">
        <derived-from template="datamodel"/>
        <name>HNR</name>
        <alias>Heterogeneous Nested Relations</alias>
    </topic>
    <topic domain="wwww" TID="emx" crdate="20061118">
        <derived-from template="modelinglanguage"/>
        <name>EMX</name>
        <alias>Entity Model for XML Schema</alias>
    </topic>
    <topic domain="wwww" TID="codex" crdate="20060228">
        <derived-from template="modelinglanguage"/>
        <name>CoDEX</name>
        <alias>Conceptual Design and Evolution of XML Schemas</alias>
    </topic>
    <topic domain="wwww" TID="er" crdate="20030712">
        <derived-from template="modelinglanguage"/>
        <name>ER</name>
        <alias>Entity-Relationship Model</alias>
    </topic>
    <topic domain="wwww" TID="xer2" crdate="20040103">
        <derived-from template="modelinglanguage"/>
        <name>XER</name>
        <alias>Extensible Entity Relationship Modeling</alias>
    </topic>
    <topic domain="wwww" TID="xmi" crdate="20000621">
        <derived-from template="technology"/>
        <name>XMI</name>
        <alias>XML Metadata Interchange</alias>
    </topic>
    <topic domain="wwww" TID="conceptualxml" crdate="20050519">
        <derived-from template="modelinglanguage"/>
        <name>C-XML</name>
        <alias>Conceptual XML</alias>
    </topic>
    <topic domain="wwww" TID="erex" crdate="20041109">
        <derived-from template="modelinglanguage"/>
        <name>EReX</name>
        <alias>ER extended for XML</alias>
    </topic>
    <topic domain="wwww" TID="erx" crdate="20031215">
        <derived-from template="modelinglanguage"/>
        <name>ERX</name>
        <alias>Entity-Relationship for XML</alias>
    </topic>
    <topic domain="wwww" TID="eer" crdate="20030712">
        <derived-from template="modelinglanguage"/>
        <name>EER</name>
        <alias>Extended Entity-Relationship Model</alias>
    </topic>
    <topic domain="wwww" TID="voip" modate="20040824" crdate="20000803">
        <derived-from template="concept"/>
        <name>VoIP</name>
        <alias>Voice over IP</alias>
        <desc><topicref TID="voip"/> describes the <topicref TID="concept"/> of using the <topicref TID="internet"/> rather than the <topicref TID="pstn"/> as <topicref TID="network"/> for telephony. <topicref TID="voip"/> can be implemented in a variety of ways.</desc>
    </topic>
    <topic domain="wwww" TID="dotnet" crdate="20040620">
        <derived-from template="technology"/>
        <name>.NET</name>
    </topic>
    <topic domain="wwww" TID="ado" crdate="20020612">
        <derived-from template="technology"/>
        <name>ADO</name>
        <alias>ActiveX Data Objects</alias>
    </topic>
    <topic domain="wwww" TID="activex" crdate="20001213">
        <derived-from template="technology"/>
        <name>ActiveX</name>
        <desc><topicref TID="activex"/> is the name <topicref TID="microsoft"/> has given to a set of object-oriented concepts, technologies, and tools. It is important to notice that <topicref TID="activex"/> is not a specific technology, but a brand name, what it's applied to can vary over time. However, the main technology is <topicref TID="com"/>. Used in a network with a directory and additional support, <topicref TID="com"/> becomes the <topicref TID="dcom"/>. The main object that is created when writing a program to run in the <topicref TID="activex"/> environment is a component, a self-sufficient program that can be run anywhere in the <topicref TID="activex"/> network. This component is known as an "<topicref TID="activex"/> control". An <topicref TID="activex"/> control is roughly equivalent to a <topicref TID="applet"/>. One important difference is that an <topicref TID="activex"/> control must be compiled for a specific platform, while an <topicref TID="applet"/> is platform-independent.</desc>
    </topic>
    <topic domain="wwww" TID="com" crdate="20000615">
        <derived-from template="componentmodel"/>
        <name>COM</name>
        <alias>Component Object Model</alias>
        <desc><topicref TID="microsoft"/>'s <topicref TID="com"/> is a software architecture that allows applications to be built from binary software components. <topicref TID="com"/> is the underlying architecture that forms the foundation for higher-level software services, like those provided by <topicref TID="ole"/>. <topicref TID="com"/> defines a binary standard for function calling between components, a way for components to dynamically discover the interfaces implemented by other components, and a mechanism to identify components and their interfaces uniquely.</desc>
    </topic>
    <topic domain="wwww" TID="opendoc" crdate="20010316">
        <derived-from template="componentmodel"/>
        <derived-from template="api"/>
        <name>OpenDoc</name>
        <desc><topicref TID="opendoc"/> is an open, multi-platform architecture for component software developed mainly by <topicref TID="apple"/> and <topicref TID="ibm"/>. It is a <topicref TID="componentmodel"/> as well as an <topicref TID="api"/> that makes it possible to design independent programs (components) that can work together on a single document. In favor of <topicref TID="java"/> technology, <topicref TID="apple"/> announced its plans to reduce its investment in <topicref TID="opendoc"/> technologies. The competing product to <topicref TID="opendoc"/> is <topicref TID="microsoft"/>'s <topicref TID="ole"/>.</desc>
    </topic>
    <topic domain="wwww" TID="ole" crdate="20001206">
        <derived-from template="technology"/>
        <name>OLE</name>
        <alias>Object Linking and Embedding</alias>
        <desc><topicref TID="ole"/> is a compound document standard developed by <topicref TID="microsoft"/>. <topicref TID="ole"/> makes it possible to create objects with one application and link or embed them in a second application. Embedded objects retain their original format and links to the application that created them. Support for <topicref TID="ole"/> is built into the <topicref TID="windows"/> and <topicref TID="macos"/> <topicref TID="os"/>s. A competing compound document standard developed mainly by <topicref TID="apple"/> and <topicref TID="ibm"/> is called <topicref TID="opendoc"/>.</desc>
    </topic>
    <topic domain="wwww" TID="olap" crdate="20001206">
        <derived-from template="technology"/>
        <name>OLAP</name>
        <alias>On-line Analytical Processing</alias>
    </topic>
    <topic domain="wwww" TID="molap" crdate="20040707">
        <derived-from template="olap"/>
        <name>MOLAP</name>
        <alias>Multidimensional OLAP</alias>
    </topic>
    <topic domain="wwww" TID="rolap" crdate="20040707">
        <derived-from template="olap"/>
        <name>ROLAP</name>
        <alias>Relational OLAP</alias>
    </topic>
    <topic domain="wwww" TID="holap" crdate="20040707">
        <derived-from template="olap"/>
        <name>HOLAP</name>
        <alias>Hybrid OLAP</alias>
    </topic>
    <topic domain="wwww" TID="wsdm" crdate="20040622">
        <derived-from template="technology"/>
        <name>WSDM</name>
        <alias>Web Services Distributed Management</alias>
    </topic>
    <topic domain="wwww" TID="mows" crdate="20040622">
        <derived-from template="technology"/>
        <name>MOWS</name>
        <alias>Management of Web Services</alias>
    </topic>
    <topic domain="wwww" TID="muws" crdate="20040622">
        <derived-from template="technology"/>
        <name>MUWS</name>
        <alias>Management Using Web Services</alias>
    </topic>
    <topic domain="wwww" TID="gxa" crdate="20040302">
        <derived-from template="technology"/>
        <name>GXA</name>
        <alias>Global XML Web Services Architecture</alias>
    </topic>
    <topic domain="wwww" TID="dcom" crdate="20000615">
        <derived-from template="componentmodel"/>
        <name>DCOM</name>
        <alias>Distributed Component Object Model</alias>
        <desc><topicref TID="dcom"/> is a <topicref TID="protocol"/> that enables software components to communicate directly over a network in a reliable, secure, and efficient manner. Previously called <topicref TID="ole"/>, <topicref TID="dcom"/> is designed for use across multiple network transports, including <topicref TID="internet"/> <topicref TID="protocol"/>s such as <topicref TID="http"/>. <topicref TID="dcom"/> is based on <topicref TID="dcerpc"/> and <topicref TID="com"/>.</desc>
    </topic>
    <topic domain="core" TID="realnetworks" crdate="20020629">
        <derived-from template="company"/>
        <name>RealNetworks</name>
    </topic>
    <topic domain="core" TID="compaq" crdate="20001221">
        <derived-from template="company"/>
        <name>Compaq</name>
    </topic>
    <topic domain="core" TID="hp" crdate="20010915">
        <derived-from template="company"/>
        <name>HP</name>
        <alias>Hewlett-Packard</alias>
    </topic>
    <topic domain="core" TID="toshiba" crdate="20020809">
        <derived-from template="company"/>
        <name>Toshiba</name>
    </topic>
    <topic domain="core" TID="olympus" crdate="20020809">
        <derived-from template="company"/>
        <name>Olympus</name>
    </topic>
    <topic domain="core" TID="fujifilm" crdate="20020809">
        <derived-from template="company"/>
        <name>Fuji Film</name>
    </topic>
    <topic domain="core" TID="fujitsu" crdate="20011123">
        <derived-from template="company"/>
        <name>Fujitsu</name>
    </topic>
    <topic domain="core" TID="sgi" crdate="20011207">
        <derived-from template="company"/>
        <name>SGI</name>
        <alias>Silicon Graphics, Inc.</alias>
    </topic>
    <topic domain="core" TID="amd" crdate="20040211">
        <derived-from template="company"/>
        <name>AMD</name>
    </topic>
    <topic domain="core" TID="intel" crdate="20011123">
        <derived-from template="company"/>
        <name>Intel</name>
    </topic>
    <topic domain="core" TID="nec" crdate="20011123">
        <derived-from template="company"/>
        <name>NEC Corporation</name>
    </topic>
    <topic domain="core" TID="dec" crdate="20000919">
        <derived-from template="company"/>
        <name>DEC</name>
        <alias>Digital Equipment Corporation</alias>
    </topic>
    <topic domain="wwww" TID="zigbee" crdate="20051026">
        <derived-from template="wlinterface"/>
        <name>ZigBee</name>
    </topic>
    <topic domain="wwww" TID="bluetooth" crdate="20010314">
        <derived-from template="wlinterface"/>
        <name>Bluetooth</name>
    </topic>
    <topic domain="wwww" TID="cdpd" crdate="20011211">
        <derived-from template="wlinterface"/>
        <name>CDPD</name>
        <alias>Cellular Digital Packet Data</alias>
    </topic>
    <topic domain="wwww" TID="dect" crdate="20000803">
        <derived-from template="wlinterface"/>
        <name>DECT</name>
        <alias>Digitally Enhanced Cordless Telecommunications</alias>
    </topic>
    <topic domain="wwww" TID="cookie" crdate="20010315">
        <derived-from template="concept"/>
        <name>Cookie</name>
        <desc>Originally introduced by <topicref TID="netscape"/>, <topicref TID="cookie"/>s are a general mechanism which <topicref TID="httpserver"/> side applications, such as <topicref TID="cgi"/> scripts, can use to both store and retrieve information on the <topicref TID="httpclient"/> side of the connection. Basically, <topicref TID="cookie"/>s can be used to compensate for the stateless nature of <topicref TID="http"/>. The addition of a simple, persistent, client-side state significantly extends the capabilities of <topicref TID="www"/>-based applications.</desc>
    </topic>
    <topic domain="wwww" TID="jfc" crdate="20000831">
        <derived-from template="technology"/>
        <name>JFC</name>
        <alias>Java Foundation Classes</alias>
    </topic>
    <topic domain="wwww" TID="awt" crdate="20000831">
        <derived-from template="technology"/>
        <name>AWT</name>
        <alias>Abstract Windowing Toolkit</alias>
    </topic>
    <topic domain="wwww" TID="swt" crdate="20030805">
        <derived-from template="technology"/>
        <name>SWT</name>
        <alias>Standard Widget Toolkit</alias>
        <desc><topicref TID="swt"/> is <topicref TID="ibm"/>'s toolkit similar to <topicref TID="swing"/>. It is intermediate in complexity between <topicref TID="awt"/> and <topicref TID="swing"/>. It is considerably faster than <topicref TID="swing"/>.</desc>
    </topic>
    <topic domain="wwww" TID="jface" crdate="20031125">
        <derived-from template="technology"/>
        <name>JFace</name>
    </topic>
    <topic domain="wwww" TID="swing" crdate="20000831">
        <derived-from template="technology"/>
        <name>Swing</name>
    </topic>
    <topic domain="wwww" TID="isorpc" crdate="20010320">
        <derived-from template="rpc"/>
        <name>ISO RPC</name>
        <alias>OSI RPC</alias>
    </topic>
    <topic domain="wwww" TID="dcerpc" crdate="20010320">
        <derived-from template="rpc"/>
        <name>DCE RPC</name>
    </topic>
    <topic domain="wwww" TID="oncrpc" crdate="20010309">
        <derived-from template="rpc"/>
        <name>ONC RPC</name>
    </topic>
    <topic domain="wwww" TID="rmi" crdate="20000615">
        <derived-from template="rpc"/>
        <name>RMI</name>
        <alias>Remote Method Invocation</alias>
        <desc><topicref TID="rmi"/> is an <topicref TID="rpc"/> mechanism enabling <topicref TID="java"/> programmers to create distributed applications, in which the methods of remote <topicref TID="java"/> objects can be invoked from another <topicref TID="jvm"/>, possibly on a different host. A <topicref TID="java"/> program can make a call on a remote object once it obtains a reference to the remote object, either by looking up the remote object in the bootstrap naming service provided by <topicref TID="rmi"/>, or by receiving the reference as an argument or a return value. A <topicref TID="client"/> can call a remote object in a <topicref TID="server"/>, and that <topicref TID="server"/> can also be a <topicref TID="client"/> of other remote objects. <topicref TID="rmi"/> uses object serialization to marshal and unmarshal parameters and does not truncate types, supporting true object-oriented polymorphism.</desc>
    </topic>
    <topic domain="wwww" TID="rsvp" crdate="20020716">
        <derived-from template="protocol"/>
        <name>RSVP</name>
        <alias>Resource Reservation Protocol</alias>
    </topic>
    <topic domain="wwww" TID="rpc" crdate="20000615">
        <derived-from template="protocol"/>
        <name>RPC</name>
        <alias>Remote Procedure Call</alias>
    </topic>
    <topic domain="wwww" TID="lz77" crdate="20000614">
        <derived-from template="compression"/>
        <name>LZ77</name>
        <alias>Lempel-Ziv</alias>
        <desc><topicref TID="lz77"/> is a data <topicref TID="compression"/> <topicref TID="algorithm"/> that builds a dictionary of frequently repeated groups of bit patterns on a per-file basis and represents these frequent patterns as shorter bit patterns (using the dictionary).</desc>
    </topic>
    <topic domain="wwww" TID="packbits" crdate="20010311">
        <derived-from template="rle"/>
        <name>PackBits</name>
    </topic>
    <topic domain="wwww" TID="bzip2" crdate="20061206">
        <derived-from template="compression"/>
        <name>bzip2</name>
    </topic>
    <topic domain="wwww" TID="deflate" crdate="20010817">
        <derived-from template="compression"/>
        <name>Deflate</name>
    </topic>
    <topic domain="wwww" TID="ppm" crdate="20020702">
        <derived-from template="compression"/>
        <name>PPM</name>
        <alias>Prediction by Partial Matching</alias>
    </topic>
    <topic domain="wwww" TID="lzs" crdate="20010817">
        <derived-from template="compression"/>
        <name>LZS</name>
        <alias>Lempel-Ziv-Stac</alias>
    </topic>
    <topic domain="wwww" TID="lzw" crdate="20000614">
        <derived-from template="compression"/>
        <name>LZW</name>
        <alias>Lempel-Ziv-Welch</alias>
        <desc><topicref TID="lzw"/> is a refinement of the <topicref TID="lz77"/> <topicref TID="algorithm"/>. The <topicref TID="lzw"/> <topicref TID="algorithm"/> is patented by Unisys Corporation.</desc>
    </topic>
    <topic domain="wwww" TID="lzo" crdate="20030806">
        <derived-from template="compression"/>
        <name>LZO</name>
        <alias>Lempel-Ziv-Oberhumer</alias>
        <desc><topicref TID="lzo"/> is a <topicref TID="compression"/> format which is suitable for data de-/compression in real-time. This means it favors speed over compression ratio.</desc>
    </topic>
    <topic domain="wwww" TID="irda" crdate="20000914">
        <derived-from template="technology"/>
        <derived-from template="group"/>
        <name>IrDA</name>
        <alias>Infrared Data Association</alias>
    </topic>
    <topic domain="wwww" TID="isc" crdate="20010811">
        <derived-from template="group"/>
        <name>ISC</name>
        <alias>Internet Software Consortium</alias>
    </topic>
    <topic domain="wwww" TID="osf" crdate="20000912">
        <derived-from template="group"/>
        <name>OSF</name>
        <alias>Open Software Foundation</alias>
    </topic>
    <topic domain="wwww" TID="opengroup" crdate="20000711">
        <derived-from template="group"/>
        <name>Open Group</name>
    </topic>
    <topic domain="wwww" TID="clf" crdate="20010322">
        <derived-from template="dataformat"/>
        <name>CLF</name>
        <alias>Common Log Format</alias>
        <desc><topicref TID="clf"/> is a log file <topicref TID="dataformat"/> for <topicref TID="httpserver"/>s, containing information about the host, identification of the user (if available), authorized user-name (if available), date, the request line itself, and the returned status and number of bytes. Although most <topicref TID="httpserver"/>s can be configured to produce other <topicref TID="dataformat"/>s of log files, many tools exist to analyze <topicref TID="clf"/> files, so custom log file <topicref TID="dataformat"/>s should only be used if absolutely necessary.</desc>
    </topic>
    <topic domain="wwww" TID="dmtf" crdate="20000830">
        <derived-from template="group"/>
        <name>DMTF</name>
        <alias>Distributed Management Task Force</alias>
    </topic>
    <topic domain="wwww" TID="oma" crdate="20020923">
        <derived-from template="group"/>
        <name>OMA</name>
        <alias>Open Mobile Alliance</alias>
    </topic>
    <topic domain="wwww" TID="wapforum" crdate="20000711">
        <derived-from template="consortium"/>
        <name>WAP Forum</name>
    </topic>
    <topic domain="wwww" TID="pkiforum" crdate="20000706">
        <derived-from template="consortium"/>
        <name>PKI Forum</name>
    </topic>
    <topic domain="wwww" TID="xcms" crdate="20030128">
        <derived-from template="dataformat"/>
        <name>XCMS</name>
        <alias>XML Cryptographic Message Syntax</alias>
        <desc><topicref TID="cms"/> is used to digitally sign or encrypt arbitrary messages. <topicref TID="cms"/> describes an encapsulation syntax for data protection. It supports digital signatures and <topicref TID="encryption"/>. The syntax allows multiple encapsulation, so one encapsulation envelope can be nested inside another. Likewise, one party can digitally sign some previously encapsulated data. It also allows arbitrary attributes, such as signing time, to be authenticated along with the message content, and provides for other attributes such as counter-signatures to be associated with a signature.</desc>
    </topic>
    <topic domain="wwww" TID="cms" crdate="20001215">
        <derived-from template="concept"/>
        <name>CMS</name>
        <alias>Cryptographic Message Syntax</alias>
        <desc><topicref TID="cms"/> is used to digitally sign or encrypt arbitrary messages. <topicref TID="cms"/> describes an encapsulation syntax for data protection. It supports digital signatures and <topicref TID="encryption"/>. The syntax allows multiple encapsulation, so one encapsulation envelope can be nested inside another. Likewise, one party can digitally sign some previously encapsulated data. It also allows arbitrary attributes, such as signing time, to be authenticated along with the message content, and provides for other attributes such as counter-signatures to be associated with a signature.</desc>
    </topic>
    <topic domain="wwww" TID="xades" crdate="20030221">
        <derived-from template="topic"/>
        <name>XAdES</name>
        <alias>XML Advanced Electronic Signatures</alias>
    </topic>
    <topic domain="wwww" TID="som" crdate="20061005">
        <derived-from template="xmlschemaapi"/>
        <name>SOM</name>
        <alias>XML Schema Object Model</alias>
    </topic>
    <topic domain="wwww" TID="xsd2" crdate="20061005">
        <derived-from template="xmlschemaapi"/>
        <name>XSD</name>
        <alias>XML Schema Infoset Model</alias>
    </topic>
    <topic domain="wwww" TID="xsom" crdate="20040319">
        <derived-from template="xmlschemaapi"/>
        <name>XSOM</name>
        <alias>XML Schema Object Model</alias>
    </topic>
    <topic domain="wwww" TID="jaxr" crdate="20031212">
        <derived-from template="api"/>
        <name>JAXR</name>
        <alias>Java API for XML Registries</alias>
    </topic>
    <topic domain="wwww" TID="jaxws" crdate="20060811">
        <derived-from template="api"/>
        <name>JAX-WS</name>
        <alias>Java API for XML Web Services</alias>
    </topic>
    <topic domain="wwww" TID="jaxwsa" crdate="20060630">
        <derived-from template="api"/>
        <name>JAX-WSA</name>
        <alias>Java API for XML Web Services Addressing</alias>
    </topic>
    <topic domain="wwww" TID="saaj" crdate="20031212">
        <derived-from template="api"/>
        <name>SAAJ</name>
        <alias>SOAP with Attachments API for Java</alias>
    </topic>
    <topic domain="wwww" TID="jaxm" crdate="20001215">
        <derived-from template="api"/>
        <name>JAXM</name>
        <alias>Java API for XML Messaging</alias>
    </topic>
    <topic domain="wwww" TID="jsapi" crdate="20030116">
        <derived-from template="api"/>
        <name>JSAPI</name>
        <alias>Java Speech API</alias>
    </topic>
    <topic domain="core" TID="aldus" crdate="20001215">
        <derived-from template="company"/>
        <name>Aldus</name>
    </topic>
    <topic domain="wwww" TID="jtapi" crdate="20020612">
        <derived-from template="api"/>
        <name>JTAPI</name>
        <alias>Java Telephony API</alias>
    </topic>
    <topic domain="wwww" TID="jain" crdate="20020612">
        <derived-from template="api"/>
        <name>JAIN</name>
        <alias>Java APIs for Integrated Networks</alias>
    </topic>
    <topic domain="wwww" TID="snaque" crdate="20030721">
        <derived-from template="api"/>
        <name>SNAQue</name>
        <alias>Strathclyde Novel Architecture for Querying XML</alias>
    </topic>
    <topic domain="wwww" TID="jaxb" crdate="20001215">
        <derived-from template="xmlapi"/>
        <name>JAXB</name>
        <alias>Java Architecture for XML Binding</alias>
    </topic>
    <topic domain="wwww" TID="wave" crdate="20010309">
        <derived-from template="audioformat"/>
        <name>WAVE</name>
        <alias>Waveform Audio File Format</alias>
        <desc><topicref TID="wave"/> is a proprietary standard for audio files developed by <topicref TID="microsoft"/>. The format can store monaural or multichannel sampled sounds in a range of sampling types, sample rates and sample resolutions.</desc>
    </topic>
    <topic domain="wwww" TID="aiff" crdate="20010314">
        <derived-from template="audioformat"/>
        <name>AIFF</name>
        <alias>Audio Interchange File Format</alias>
        <desc><topicref TID="aiff"/> is a proprietary <topicref TID="audioformat"/> developed by <topicref TID="apple"/>. The format can store monaural or multichannel sampled sounds in a range of sample rates and sample resolutions. Although originally <topicref TID="aiff"/> did not support compressed audio data, a new version of the format called <topicref TID="aiffc"/> has been defined which allows compression.</desc>
    </topic>
    <topic domain="wwww" TID="vcard" crdate="20030213">
        <derived-from template="dataformat"/>
        <name>vCard</name>
    </topic>
    <topic domain="wwww" TID="vcalendar" crdate="20030213">
        <derived-from template="dataformat"/>
        <name>vCalendar</name>
        <alias>vCal</alias>
    </topic>
    <topic domain="wwww" TID="fourcc" crdate="20020904">
        <derived-from template="dataformat"/>
        <name>FOURCC</name>
        <alias>Four Character Code</alias>
    </topic>
    <topic domain="wwww" TID="riff" crdate="20020904">
        <derived-from template="dataformat"/>
        <name>RIFF</name>
        <alias>Resource Interchange File Format</alias>
    </topic>
    <topic domain="wwww" TID="aiffc" crdate="20010314">
        <derived-from template="audioformat"/>
        <name>AIFF-C</name>
        <alias>AIFF Compressed</alias>
        <desc><topicref TID="aiffc"/> is an extended version of <topicref TID="apple"/>'s <topicref TID="aiff"/> <topicref TID="audioformat"/>. It incorporates compression features, which have not been included in the original <topicref TID="aiff"/> <topicref TID="audioformat"/>.</desc>
    </topic>
    <topic domain="wwww" TID="quicktime" crdate="20010307">
        <derived-from template="audioformat"/>
        <derived-from template="videoformat"/>
        <name>QuickTime</name>
        <desc><topicref TID="quicktime"/> is <topicref TID="apple"/>'s architecture for handling multimedia data. First versions of <topicref TID="quicktime"/> were basically a <topicref TID="dataformat"/> for audio and video, newer versions integrate streaming capabilities as well as more media types, including support for 3D and virtual reality. Being a proprietary technology, <topicref TID="quicktime"/> can be compared to <topicref TID="microsoft"/>'s <topicref TID="asf"/>.</desc>
    </topic>
    <topic domain="wwww" TID="avi" modate="20020722" crdate="20001215">
        <derived-from template="audioformat"/>
        <derived-from template="videoformat"/>
        <name>AVI</name>
        <alias>Audio Video Interleave</alias>
        <desc><topicref TID="microsoft"/>'s <topicref TID="avi"/> file format is used for storing audio and/or video information. It is a common format for audio and video files within PC environments. Being a proprietary technology, <topicref TID="avi"/> can be functionally compared to <topicref TID="apple"/>'s <topicref TID="quicktime"/>.</desc>
        <status><topicref TID="microsoft"/>'s <topicref TID="asf"/> is a newer format which has been designed to eventually replace <topicref TID="avi"/>.</status>
    </topic>
    <topic domain="wwww" TID="asf" modate="20020904" crdate="20001215">
        <derived-from template="videoformat"/>
        <derived-from template="audioformat"/>
        <name>ASF</name>
        <alias>Advanced Streaming Format</alias>
        <desc><topicref TID="microsoft"/>'s <topicref TID="asf"/> is an extensible file format designed to store synchronized multimedia data. It supports data delivery over a wide variety of networks and protocols while still proving suitable for local playback. The explicit goal of <topicref TID="asf"/> is to provide a basis for industry-wide multimedia interoperability. Each <topicref TID="asf"/> file is composed of one or more media streams. The file header specifies the properties of the entire file, along with stream-specific properties. Multimedia data, stored after the file header, references a particular media stream number to indicate its type and purpose. The delivery and presentation of all media stream data is synchronized to a common time-line. <topicref TID="asf"/>'s functionality is similar to the one provided by <topicref TID="apple"/>'s <topicref TID="quicktime"/>.</desc>
         <status>The intent is that in the long run <topicref TID="asf"/> will replace the older <topicref TID="avi"/> format.</status>
    </topic>
    <topic domain="wwww" TID="xmlp" crdate="20001220">
        <derived-from template="technology"/>
        <name>XMLP</name>
        <alias>XML Protocol</alias>
    </topic>
    <topic domain="wwww" TID="cg" crdate="20010320">
        <derived-from template="metadata"/>
        <name>CG</name>
        <alias>Conceptual Graphs</alias>
    </topic>
    <topic domain="wwww" TID="kif" crdate="20010320">
        <derived-from template="metadata"/>
        <name>KIF</name>
        <alias>Knowledge Interchange Format</alias>
    </topic>
    <topic domain="wwww" TID="jsx" crdate="20020830">
        <derived-from template="technology"/>
        <name>JSX</name>
        <alias>Java Serialization to XML</alias>
    </topic>
    <topic domain="wwww" TID="jta" crdate="20001220">
        <derived-from template="technology"/>
        <name>JTA</name>
        <alias>Java Transaction API</alias>
    </topic>
    <topic domain="wwww" TID="trax" crdate="20020609">
        <derived-from template="api"/>
        <name>TrAX</name>
        <alias>Transformation API for XML</alias>
        <desc><topicref TID="trax"/> is an <topicref TID="api"/> for transforming <topicref TID="xml"/> documents using <topicref TID="xslt"/> style sheets. <topicref TID="trax"/> is a <topicref TID="java"/> <topicref TID="api"/> and has been defined to provide common access to different <topicref TID="xsltprocessor"/>s. <topicref TID="trax"/> is part of the <topicref TID="jaxp"/> <topicref TID="api"/>, which combines a number of <topicref TID="java"/> <topicref TID="api"/>s.</desc>
    </topic>
    <topic domain="wwww" TID="jaxp" crdate="20001215" modate="20031212">
        <derived-from template="xmlapi"/>
        <name>JAXP</name>
        <alias>Java API for XML Processing</alias>
        <desc><topicref TID="jaxp"/> is an <topicref TID="api"/> for <topicref TID="xml"/> parsing and processing. It is an abstraction layer (i.e., an <topicref TID="api"/> for other <topicref TID="api"/>s) which can be used to access <topicref TID="xml"/>-specific functionality from within <topicref TID="java"/> programs. <topicref TID="jaxp"/> supports parsing <topicref TID="xml"/> documents using the <topicref TID="dom"/> or <topicref TID="sax"/> <topicref TID="api"/>s, and processing <topicref TID="xml"/> documents with <topicref TID="xslt"/> using the <topicref TID="trax"/> <topicref TID="api"/>.</desc>
    </topic>
    <topic domain="wwww" TID="jaas" crdate="20031031">
        <derived-from template="api"/>
        <name>JAAS</name>
        <alias>Java Authentication and Authorization Service</alias>
    </topic>
    <topic domain="wwww" TID="msmq" crdate="20040929">
        <derived-from template="api"/>
        <name>MSMQ</name>
        <alias>Microsoft Message Queuing</alias>
    </topic>
    <topic domain="wwww" TID="mqseries" crdate="20040929">
        <derived-from template="api"/>
        <name>MQSeries</name>
    </topic>
    <topic domain="wwww" TID="jms" crdate="20010221">
        <derived-from template="api"/>
        <name>JMS</name>
        <alias>Java Message Service</alias>
    </topic>
    <topic domain="wwww" TID="jmx" crdate="20010221">
        <derived-from template="api"/>
        <name>JMX</name>
        <alias>Java Management Extensions</alias>
    </topic>
    <topic domain="wwww" TID="cbl" crdate="20010914">
        <derived-from template="technology"/>
        <name>CBL</name>
        <alias>Common Business Library</alias>
        <status><topicref TID="cbl"/> was a research project aimed at testing how good <topicref TID="xml"/> could be used as a foundation for <topicref TID="ecommerce"/>. It has been replaced by the newer <topicref TID="xcbl"/> <topicref TID="technology"/>.</status>
    </topic>
    <topic domain="wwww" TID="thp" crdate="20030721">
        <derived-from template="technology"/>
        <name>THP</name>
        <alias>Tentative Hold Protocol</alias>
    </topic>
    <topic domain="wwww" TID="btp" crdate="20030721">
        <derived-from template="technology"/>
        <name>BTP</name>
        <alias>Business Transaction Protocol</alias>
    </topic>
    <topic domain="wwww" TID="xcbl" crdate="20010914">
        <derived-from template="technology"/>
        <name>xCBL</name>
        <alias>XML Common Business Library</alias>
        <status><topicref TID="xcbl"/> was a proprietary <topicref TID="technology"/> for <topicref TID="ecommerce"/> data exchange. It has been replaced by the newer <topicref TID="ubl"/> <topicref TID="technology"/>, which is standardized as an open standard by <topicref TID="oasis"/>.</status>
    </topic>
    <topic domain="wwww" TID="step" crdate="20030721">
        <derived-from template="technology"/>
        <name>STEP</name>
        <alias>Standard for the Exchange of Product Model Data</alias>
    </topic>
    <topic domain="wwww" TID="express" crdate="20030721">
        <derived-from template="technology"/>
        <name>EXPRESS</name>
    </topic>
    <topic domain="wwww" TID="xnl" crdate="20041104">
        <derived-from template="dataformat"/>
        <name>xNL</name>
        <alias>Extensible Name Language</alias>
    </topic>
    <topic domain="wwww" TID="xal" crdate="20041104">
        <derived-from template="dataformat"/>
        <name>xAL</name>
        <alias>Extensible Address Language</alias>
    </topic>
    <topic domain="wwww" TID="xnal" crdate="20041104">
        <derived-from template="dataformat"/>
        <name>xNAL</name>
        <alias>Extensible Name and Address Language</alias>
    </topic>
    <topic domain="wwww" TID="ebxml" crdate="20001215">
        <derived-from template="technology"/>
        <name>ebXML</name>
        <alias>Electronic Business XML</alias>
    </topic>
    <topic domain="wwww" TID="uddi" modate="20020722" crdate="20001215">
        <derived-from template="technology"/>
        <name>UDDI</name>
        <alias>Universal Description, Discovery, and Integration</alias>
        <desc><topicref TID="uddi"/> provides a standardized method for publishing and discovering information about Web services. <topicref TID="uddi"/> is an industry initiative that attempts to create a platform-independent, open framework for describing services, discovering businesses, and integrating business services. <topicref TID="uddi"/> focuses on the process of discovery in the <topicref TID="soa"/> (<topicref TID="wsdl"/> is often used for service description, and <topicref TID="soap"/> for service invocation). Being a Web service itself, <topicref TID="uddi"/> is invoked using <topicref TID="soap"/>. In addition, <topicref TID="uddi"/> also defines how to operate servers and how to manage replication among several servers.</desc>
    </topic>
    <topic domain="wwww" TID="aiim" crdate="20001130">
        <derived-from template="organization"/>
        <name>AIIM</name>
        <alias>Association for Information and Image Management</alias>
    </topic>
    <topic domain="wwww" TID="wfmc" crdate="20001130">
        <derived-from template="organization"/>
        <name>WfMC</name>
        <alias>Workflow Management Coalition</alias>
    </topic>
    <topic domain="wwww" TID="cmc" crdate="20010311">
        <derived-from template="protocol"/>
        <name>CMC</name>
        <alias>Certificate Management protocol using CMS</alias>
    </topic>
    <topic domain="wwww" TID="scvp" crdate="20010311" modate="20090914">
        <derived-from template="protocol"/>
        <name>SCVP</name>
        <alias>Server-based Certificate Validation Protocol</alias>
    </topic>
    <topic domain="wwww" TID="ogsa" crdate="20031205">
        <derived-from template="concept"/>
        <name>OGSA</name>
        <alias>Open Grid Services Architecture</alias>
    </topic>
    <topic domain="wwww" TID="soa" crdate="20031205">
        <derived-from template="concept"/>
        <name>SOA</name>
        <alias>Service-Oriented Architecture</alias>
    </topic>
    <topic domain="wwww" TID="crl" crdate="20020611">
        <derived-from template="concept"/>
        <name>CRL</name>
        <alias>Certificate Revocation List</alias>
    </topic>
    <topic domain="wwww" TID="ocsp" crdate="20010311">
        <derived-from template="protocol"/>
        <name>OCSP</name>
        <alias>Online Certificate Status Protocol</alias>
    </topic>
    <topic domain="wwww" TID="certificate" crdate="20010315">
        <derived-from template="concept"/>
        <name>Certificate</name>
        <desc><topicref TID="certificate"/>s are digital documents attesting to the binding of a public key to an individual or other entity. They allow verification of the claim that a given public key does in fact belong to a given individual. <topicref TID="certificate"/>s help prevent someone from using a phony key to impersonate someone else. In their simplest form, <topicref TID="certificate"/>s contain a public key and a name. As commonly used, a <topicref TID="certificate"/> also contains an expiration date, the name of the <topicref TID="ca"/> that issued the <topicref TID="certificate"/>, a serial number, and perhaps other information. Most importantly, it contains the digital signature of the certificate issuer. The most widely accepted format for certificates is <topicref TID="x509"/>, thus, <topicref TID="certificate"/>s can be read or written by any application complying with <topicref TID="x509"/>.</desc>
    </topic>
    <topic domain="wwww" TID="ca" crdate="20010315">
        <derived-from template="concept"/>
        <name>CA</name>
        <alias>Certification Authority</alias>
        <desc>A <topicref TID="ca"/> is an authority trusted by one or more users to create and assign <topicref TID="certificate"/>s. Optionally the <topicref TID="ca"/> may create the user's keys. It is important to note that the <topicref TID="ca"/> is responsible for the <topicref TID="certificate"/>s during their whole lifetime, not just for issuing them.</desc>
    </topic>
    <topic domain="wwww" TID="kea" crdate="20010311">
        <derived-from template="algorithm"/>
        <name>KEA</name>
        <alias>Key Exchange Algorithm</alias>
    </topic>
    <topic domain="wwww" TID="pkix" crdate="20000618">
        <derived-from template="certsystem"/>
        <name>PKIX</name>
        <alias>Public-Key Infrastructure X.509</alias>
    </topic>
    <topic domain="wwww" TID="cldap" crdate="20020611">
        <derived-from template="protocol"/>
        <name>CLDAP</name>
        <alias>Connection-less LDAP</alias>
    </topic>
    <topic domain="wwww" TID="ldap" crdate="20000614">
        <derived-from template="protocol"/>
        <name>LDAP</name>
        <alias>Lightweight Directory Access Protocol</alias>
        <desc><topicref TID="ldap"/> was defined in order to encourage adoption of <topicref TID="x500"/> directories. <topicref TID="dap"/> was regarded as being too complex for simple <topicref TID="internet"/> <topicref TID="client"/>s to use. <topicref TID="ldap"/> defines a relatively simple <topicref TID="protocol"/> for updating and searching directories running over <topicref TID="tcp"/>.</desc>
    </topic>
    <topic domain="wwww" TID="dap" crdate="20000614">
        <derived-from template="protocol"/>
        <name>DAP</name>
        <alias>Directory Access Protocol</alias>
        <desc><topicref TID="dap"/> is the original protocol for accessing <topicref TID="x500"/>. Since <topicref TID="dap"/> is based on <topicref TID="osi"/> and rather complex, a simplified variant of <topicref TID="dap"/> based on the <topicref TID="tcp"/> has been designed, which is called <topicref TID="ldap"/>. Today this simpler variant is more popular than <topicref TID="dap"/> itself.</desc>
    </topic>
    <topic domain="wwww" TID="dsp" crdate="20000614">
        <derived-from template="protocol"/>
        <name>DSP</name>
        <alias>Directory System Protocol</alias>
    </topic>
    <topic domain="wwww" TID="x400" crdate="20010312">
        <derived-from template="email"/>
        <name>X.400</name>
    </topic>
    <topic domain="wwww" TID="x500" crdate="20000614">
        <derived-from template="directory"/>
        <name>X.500</name>
        <desc><topicref TID="x500"/> is an open, distributed, online directory service which is intended to be global in scope. <topicref TID="x500"/> is a support service for data exchange which includes providing directory support for data communication services specified by other <topicref TID="osi"/> application standards. The <topicref TID="x500"/> series of standards covers services available to users, the functional model and protocols connecting the component parts of the directory, an information framework and a schema of the information held by the directory, and a mechanism for allowing <topicref TID="osi"/> components to authenticate each other.</desc>
    </topic>
    <topic domain="wwww" TID="x509" crdate="20000614">
        <derived-from template="certsystem"/>
        <name>X.509</name>
        <alias>Directory Authentication Framework</alias>
        <desc><topicref TID="x509"/> describes two levels of <topicref TID="authentication"/>, simple authentication, based on use of a password to verify user identity, and strong authentication, using credentials created by cryptographic methods. The standard recommends that only strong authentication should be used as the basis of providing secure services. <topicref TID="pkc"/> is used for strong authentication, but <topicref TID="x509"/> is not dependent on the use of a particular cryptographic <topicref TID="algorithm"/>, though two users wishing to authenticate must support the same <topicref TID="algorithm"/>.</desc>
    </topic>
    <topic domain="wwww" TID="mcf" crdate="20000614">
        <derived-from template="technology"/>
        <name>MCF</name>
        <alias>Meta Content Framework</alias>
        <desc><topicref TID="mcf"/> is a proposal authored by <topicref TID="netscape"/> for the definition of <topicref TID="www"/> <topicref TID="metadata"/>. The proposal has been used as input for <topicref TID="w3c"/>'s work on <topicref TID="rdf"/>.</desc>
    </topic>
    <topic domain="wwww" TID="wpf" crdate="20080916">
        <derived-from template="riaruntime"/>
        <name>WPF</name>
        <alias>Windows Presentation Foundation</alias>
    </topic>
    <topic domain="wwww" TID="silverlight" crdate="20070807">
        <derived-from template="riaruntime"/>
        <name>Silverlight</name>
    </topic>
    <topic domain="wwww" TID="apollo" crdate="20070807">
        <derived-from template="riaruntime"/>
        <name>Apollo</name>
    </topic>
    <topic domain="wwww" TID="air" crdate="20070807">
        <derived-from template="riaruntime"/>
        <name>AIR</name>
        <alias>Adobe Integrated Runtime</alias>
    </topic>
    <topic domain="wwww" TID="javafx" crdate="20070807">
        <derived-from template="riaruntime"/>
        <name>JavaFX</name>
    </topic>
    <topic domain="wwww" TID="flash" crdate="20010315">
        <derived-from template="hypermediaformat"/>
        <name>Flash</name>
    </topic>
    <topic domain="wwww" TID="shockwave" crdate="20010315">
        <derived-from template="hypermediaformat"/>
        <name>Shockwave</name>
    </topic>
    <topic domain="core" TID="macromedia" crdate="20010315">
        <derived-from template="company"/>
        <name>Macromedia</name>
    </topic>
    <topic domain="wwww" TID="doap" crdate="20050918">
        <derived-from template="dataformat"/>
        <name>DOAP</name>
        <alias>Description of a Project</alias>
    </topic>
    <topic domain="wwww" TID="foaf" crdate="20040126">
        <derived-from template="dataformat"/>
        <name>FOAF</name>
        <alias>Friend of a Friend</alias>
    </topic>
    <topic domain="wwww" TID="ooxml" crdate="20070410">
        <derived-from template="dataformat"/>
        <name>OOXML</name>
        <alias>Office Open XML</alias>
    </topic>
    <topic domain="wwww" TID="openxml" crdate="20061024">
        <derived-from template="textformat"/>
        <name>Open XML</name>
    </topic>
    <topic domain="wwww" TID="odf" crdate="20061024">
        <derived-from template="textformat"/>
        <name>ODF</name>
        <alias>OpenDocument Format</alias>
    </topic>
    <topic domain="wwww" TID="rtf" crdate="20000619">
        <derived-from template="textformat"/>
        <name>RTF</name>
        <alias>Rich Text Format</alias>
    </topic>
    <topic domain="wwww" TID="lex" crdate="20020716">
        <derived-from template="parsergenerator"/>
        <name>lex</name>
    </topic>
    <topic domain="wwww" TID="yacc" crdate="20020716">
        <derived-from template="parsergenerator"/>
        <name>yacc</name>
        <alias>Yet Another Compiler Compiler</alias>
    </topic>
    <topic domain="wwww" TID="flex" crdate="20020716">
        <derived-from template="parsergenerator"/>
        <name>flex</name>
    </topic>
    <topic domain="wwww" TID="bison" crdate="20020716">
        <derived-from template="parsergenerator"/>
        <name>bison</name>
    </topic>
    <topic domain="wwww" TID="antlr" crdate="20020716">
        <derived-from template="parsergenerator"/>
        <name>ANTLR</name>
        <alias>Another Tool for Language Recognition</alias>
    </topic>
    <topic domain="wwww" TID="pccts" crdate="20020716">
        <derived-from template="parsergenerator"/>
        <name>PCCTS</name>
        <alias>Purdue Compiler Construction Tool Set</alias>
    </topic>
    <topic domain="wwww" TID="javacc" crdate="20020716">
        <derived-from template="parsergenerator"/>
        <name>JavaCC</name>
        <alias>Java Compiler Compiler</alias>
    </topic>
    <topic domain="wwww" TID="isdn" crdate="20000803">
        <derived-from template="wan"/>
        <name>ISDN</name>
        <alias>Integrated Services Digital Network</alias>
    </topic>
    <topic domain="wwww" TID="triql" crdate="20090925">
        <derived-from template="querylanguage"/>
        <name>TriQL</name>
        <alias>RDF Query</alias>
    </topic>
    <topic domain="wwww" TID="rdfq" crdate="20090925">
        <derived-from template="querylanguage"/>
        <name>RDFQ</name>
        <alias>RDF Query</alias>
    </topic>
    <topic domain="wwww" TID="rdql" crdate="20041021">
        <derived-from template="querylanguage"/>
        <name>RDQL</name>
        <alias>RDF Data Query Language</alias>
    </topic>
    <topic domain="wwww" TID="brql" crdate="20041021">
        <derived-from template="querylanguage"/>
        <name>BRQL</name>
        <alias>Bristol RDF Query Language</alias>
        <status>On <text date="20040930"/>, <topicref TID="brql"/> has been renamed to <topicref TID="sparql"/>.</status>
    </topic>
    <topic domain="wwww" TID="sparql" crdate="20041021" modate="20050530">
        <derived-from template="querylanguage"/>
        <name>SPARQL</name>
        <alias>Simple Protocol and RDF Query Language</alias>
    </topic>
    <topic domain="wwww" TID="n3" crdate="20040924" modate="20050519">
        <derived-from template="dataformat"/>
        <name>N3</name>
        <alias>Notation 3</alias>
        <desc><topicref TID="n3"/> is an alternative syntax for <topicref TID="rdf"/>, which is less verbose than <topicref TID="rdfxml"/> and easier to read and write for humans.</desc>
    </topic>
    <topic domain="wwww" TID="rdfxml" crdate="20050519">
        <derived-from template="dataformat"/>
        <name>RDF/XML</name>
    </topic>
    <topic domain="wwww" TID="trix" crdate="20090925">
        <derived-from template="dataformat"/>
        <name>TriX</name>
        <alias>RDF Triples in XML</alias>
    </topic>
    <topic domain="wwww" TID="rdfaold" crdate="20050519">
        <derived-from template="dataformat"/>
        <name>RDF/A</name>
        <alias>RDF in Attributes</alias>
    </topic>
    <topic domain="wwww" TID="rdfa" crdate="20060524">
        <derived-from template="dataformat"/>
        <name>RDFa</name>
        <alias>RDF in Attributes</alias>
    </topic>
    <topic domain="wwww" TID="rdfs" crdate="20021005">
        <derived-from template="metadata"/>
        <name>RDFS</name>
        <alias>RDF Schema</alias>
    </topic>
    <topic domain="wwww" TID="rdf" crdate="20000614">
        <derived-from template="metadata"/>
        <name>RDF</name>
        <alias>Resource Description Framework</alias>
        <desc><topicref TID="rdf"/> is designed to provide an infrastructure supporting <topicref TID="metadata"/> across many <topicref TID="www"/>-based activities. <topicref TID="rdf"/> is the result of a number of <topicref TID="metadata"/> communities bringing together their needs to provide a robust and flexible architecture for supporting <topicref TID="metadata"/> on the <topicref TID="internet"/> and the <topicref TID="www"/>. Example applications include site maps, content ratings, stream channel definitions, search engine data collection, digital library collections, and distributed authoring. <topicref TID="rdf"/> allows different application communities to define the <topicref TID="metadata"/> property set that best serves the needs of each community. <topicref TID="rdf"/> provides a uniform and interoperable means to exchange the <topicref TID="metadata"/> between programs and across the <topicref TID="www"/>. Furthermore, <topicref TID="rdf"/> provides a means for publishing both a human-readable and a machine-understandable definition of the property set itself. <topicref TID="rdf"/> uses <topicref TID="xml"/> as the transfer syntax in order to leverage other tools and code bases being built around <topicref TID="xml"/>.</desc>
    </topic>
    <topic domain="wwww" TID="pkcs" crdate="20000706">
        <derived-from template="technology"/>
        <name>PKCS</name>
        <alias>Public-Key Cryptography Standards</alias>
        <desc><topicref TID="pkcs"/> are specifications produced by RSA Laboratories in cooperation with secure systems developers worldwide for the purpose of accelerating the deployment of <topicref TID="pkc"/>. First published in 1991 as a result of meetings with a small group of early adopters of <topicref TID="pkc"/> technology, the <topicref TID="pkcs"/> documents have become widely referenced and implemented. The <topicref TID="pkcs"/> standards cover <topicref TID="rsa"/> <topicref TID="encryption"/>, <topicref TID="diffiehellman"/> key agreement, password-based <topicref TID="encryption"/>, extended-certificate syntax, <topicref TID="cms"/>, private key information syntax, and certification request syntax, as well as selected attributes. Contributions from the <topicref TID="pkcs"/> series have become part of many formal and de facto standards, including <topicref TID="pkix"/>, <topicref TID="set"/>, <topicref TID="smime"/>, and <topicref TID="ssl"/>.</desc>
    </topic>
    <topic domain="wwww" TID="pkcs5" crdate="20010816">
        <derived-from template="pkcs"/>
        <name>PKCS-5</name>
    </topic>
    <topic domain="wwww" TID="pkcs7" crdate="20010320">
        <derived-from template="pkcs"/>
        <name>PKCS-7</name>
    </topic>
    <topic domain="wwww" TID="pkcs9" crdate="20010816">
        <derived-from template="pkcs"/>
        <name>PKCS-9</name>
    </topic>
    <topic domain="wwww" TID="pkcs10" crdate="20010816">
        <derived-from template="pkcs"/>
        <name>PKCS-10</name>
    </topic>
    <topic domain="wwww" TID="rc2" crdate="20010309">
        <derived-from template="skc"/>
        <name>RC2</name>
    </topic>
    <topic domain="wwww" TID="rc4" crdate="20010309">
        <derived-from template="skc"/>
        <name>RC4</name>
    </topic>
    <topic domain="wwww" TID="rc5" crdate="20010309">
        <derived-from template="skc"/>
        <name>RC5</name>
    </topic>
    <topic domain="wwww" TID="rc6" crdate="20010309">
        <derived-from template="skc"/>
        <name>RC6</name>
    </topic>
    <topic domain="wwww" TID="diffiehellman" crdate="20010315">
        <derived-from template="algorithm"/>
        <name>Diffie-Hellman</name>
        <desc><topicref TID="diffiehellman"/> key agreement describes a method whereby two parties, without any prior arrangements, can agree upon a secret key that is known only to them (and, in particular, is not known to an eavesdropper listening to the dialogue by which the parties agree on the key). This secret key can be used, for example, to encrypt further communications between the parties using <topicref TID="skc"/>. The intended application of this standard is in <topicref TID="protocol"/>s for establishing secure connections. Details on the interpretation of the agreed-upon secret key are outside the scope of <topicref TID="diffiehellman"/> key agreement, as are details on sources of the pseudo-random bits required by this method. The <topicref TID="diffiehellman"/> key exchange is vulnerable to a middleperson attack. This vulnerability is due to the fact that <topicref TID="diffiehellman"/> key exchange does not authenticate the participants.</desc>
    </topic>
    <topic domain="wwww" TID="rsa" crdate="20000614">
        <derived-from template="pkc"/>
        <name>RSA</name>
        <alias>Rivest, Shamir, and Adleman</alias>
        <desc><topicref TID="rsa"/> is a <topicref TID="pkc"/> system for both <topicref TID="encryption"/> and <topicref TID="authentication"/> (its name is derived from the surnames of the three inventors). For <topicref TID="encryption"/>, <topicref TID="rsa"/> is combined with a <topicref TID="skc"/> system, such as <topicref TID="des"/>, to encrypt a message by means of an <topicref TID="rsa"/> digital envelope. For <topicref TID="authentication"/>, <topicref TID="rsa"/> is usually combined with a <topicref TID="chf"/>, such as <topicref TID="md5"/>, to sign a message.</desc>
    </topic>
    <topic domain="wwww" TID="ecc" crdate="20010309">
        <derived-from template="pkc"/>
        <name>ECC</name>
        <alias>Elliptic Curve Cryptography</alias>
    </topic>
    <topic domain="wwww" TID="bauth" crdate="20010309">
        <derived-from template="algorithm"/>
        <name>Basic Authentication</name>
    </topic>
    <topic domain="wwww" TID="daauth" crdate="20010309">
        <derived-from template="algorithm"/>
        <name>Digest Access Authentication</name>
    </topic>
    <topic domain="wwww" TID="aka" crdate="20051122">
        <derived-from template="algorithm"/>
        <name>AKA</name>
        <alias>Authentication and Key Agreement</alias>
    </topic>
    <topic domain="core" TID="rsasecurity" crdate="20000706">
        <derived-from template="company"/>
        <name>RSA Security</name>
    </topic>
    <topic domain="wwww" TID="rijndael" crdate="20010719">
        <derived-from template="skc"/>
        <name>Rijndael</name>
    </topic>
    <topic domain="wwww" TID="skipjack" crdate="20010312">
        <derived-from template="skc"/>
        <name>Skipjack</name>
    </topic>
    <topic domain="wwww" TID="safer" crdate="20010312">
        <derived-from template="skc"/>
        <name>SAFER</name>
        <alias>Secure And Fast Encryption Routine</alias>
    </topic>
    <topic domain="wwww" TID="feal" crdate="20010312">
        <derived-from template="skc"/>
        <name>FEAL</name>
        <alias>Fast Data Encipherment Algorithm</alias>
    </topic>
    <topic domain="wwww" TID="desx" crdate="20010309">
        <derived-from template="skc"/>
        <name>DESX</name>
        <alias>Data Encryption Standard XORed</alias>
    </topic>
    <topic domain="wwww" TID="des" crdate="20000614">
        <derived-from template="skc"/>
        <name>DES</name>
        <alias>Data Encryption Standard</alias>
        <desc><topicref TID="des"/> was originally developed at <topicref TID="ibm"/>. <topicref TID="des"/> has been extensively studied since its publication and is the most well-known and widely used cryptosystem in the world. <topicref TID="des"/> is an <topicref TID="algorithm"/> implementing <topicref TID="skc"/>, when used for communications, both sender and receiver must know the same secret key, which is used both to encrypt and decrypt the message. <topicref TID="des"/> can also be used for single-user <topicref TID="encryption"/>, such as to store files on a hard disk in encrypted form. In a multi-user environment, secure key distribution may be difficult. <topicref TID="pkc"/> provides an ideal solution to this problem. Even though <topicref TID="des"/> has been cryptographically enhanced by using three <topicref TID="encryption"/> rounds, yielding <topicref TID="tripledes"/>, the general consensus is that <topicref TID="des"/> <topicref TID="encryption"/> is too weak for some scenarios, and the stronger <topicref TID="aes"/> will eventually replace <topicref TID="des"/>.</desc>
    </topic>
    <topic domain="wwww" TID="dea" crdate="20010719">
        <derived-from template="skc"/>
        <name>DEA</name>
        <alias>Data Encryption Algorithm</alias>
    </topic>
    <topic domain="wwww" TID="tripledese" crdate="20020628">
        <derived-from template="protocol"/>
        <name>3DESE</name>
        <alias>Triple DES Encryption</alias>
    </topic>
    <topic domain="wwww" TID="tripledes" crdate="20000614">
        <derived-from template="skc"/>
        <name>3DES</name>
        <alias>Triple DES</alias>
    </topic>
    <topic domain="wwww" TID="tdea" crdate="20010719">
        <derived-from template="skc"/>
        <name>TDEA</name>
        <alias>Triple DEA</alias>
    </topic>
    <topic domain="wwww" TID="aes" crdate="20000612">
        <derived-from template="skc"/>
        <name>AES</name>
        <alias>Advanced Encryption Standard</alias>
        <desc><topicref TID="aes"/> is the replacement of <topicref TID="des"/>, because recent research and attacks have shown that DES is not as safe as necessary for some applications. <topicref TID="aes"/> has been chosen from a number of candidates based on criteria such as efficiency, robustness, and cryptographical safety.</desc>
    </topic>
    <topic domain="wwww" TID="aea" crdate="20010719">
        <derived-from template="skc"/>
        <name>AEA</name>
        <alias>Advanced Encryption Algorithm</alias>
    </topic>
    <topic domain="wwww" TID="set" crdate="20000614">
        <derived-from template="protocol"/>
        <name>SET</name>
        <alias>Secure Electronic Transaction</alias>
        <desc><topicref TID="set"/> is an industry-wide <topicref TID="protocol"/> designed to safely transmit sensitive personal and financial information over public <topicref TID="network"/>s. <topicref TID="set"/> contains state-of-the-art cryptographic technology that provides online transaction security that is equivalent or superior to the safeguards in present physical, <topicref TID="email"/>, and telephone card transactions. <topicref TID="pkcs"/> is the set of <topicref TID="pkc"/> <topicref TID="algorithm"/>s used in <topicref TID="set"/>. The <topicref TID="skc"/> <topicref TID="algorithm"/> is <topicref TID="des"/>.</desc>
    </topic>
    <topic domain="wwww" TID="shs" crdate="20000614">
        <derived-from template="technology"/>
        <name>SHS</name>
        <alias>Secure Hash Standard</alias>
    </topic>
    <topic domain="wwww" TID="dss" crdate="20010719">
        <derived-from template="technology"/>
        <name>DSS</name>
        <alias>Digital Signature Standard</alias>
        <desc><topicref TID="dsa"/> was published by <topicref TID="nist"/> in the <topicref TID="dss"/> standard. <topicref TID="dsa"/> is for <topicref TID="authentication"/> only. In <topicref TID="dsa"/>, signature generation is faster than signature verification, whereas in <topicref TID="rsa"/>, signature verification is faster than signature generation (if the public and private exponents, respectively, are chosen for this property, which is the usual case). <topicref TID="nist"/> claims that it is an advantage of <topicref TID="dsa"/> that signing is faster, but many people in cryptography think that it is better for verification to be the faster operation.</desc>
    </topic>
    <topic domain="wwww" TID="sha" crdate="20000612">
        <derived-from template="chf"/>
        <name>SHA</name>
        <alias>Secure Hash Algorithm</alias>
    </topic>
    <topic domain="wwww" TID="sha0" crdate="20000612">
        <derived-from template="sha"/>
        <name>SHA-0</name>
        <status>Due to a cryptographic weakness in the first version of <topicref TID="sha"/>, it was withdrawn by <topicref TID="niso"/> and replaced by an improved version, <topicref TID="sha1"/>. Because of this, the first version of <topicref TID="sha"/> standard today is frequently referred to as <topicref TID="sha0"/>.</status>
    </topic>
    <topic domain="wwww" TID="sha1" crdate="20000612">
        <derived-from template="sha"/>
        <name>SHA-1</name>
    </topic>
    <topic domain="wwww" TID="sha2" crdate="20000612">
        <derived-from template="sha"/>
        <name>SHA-2</name>
    </topic>
    <topic domain="wwww" TID="sha224" crdate="20000612">
        <derived-from template="sha"/>
        <name>SHA-224</name>
    </topic>
    <topic domain="wwww" TID="sha256" crdate="20000612">
        <derived-from template="sha"/>
        <name>SHA-256</name>
    </topic>
    <topic domain="wwww" TID="sha384" crdate="20000612">
        <derived-from template="sha"/>
        <name>SHA-384</name>
    </topic>
    <topic domain="wwww" TID="sha512" crdate="20000612">
        <derived-from template="sha"/>
        <name>SHA-512</name>
    </topic>
    <topic domain="wwww" TID="dsa" crdate="20010719">
        <derived-from template="chf"/>
        <name>DSA</name>
        <alias>Digital Signature Algorithm</alias>
    </topic>
    <topic domain="wwww" TID="ecdsa" crdate="20051030">
        <derived-from template="chf"/>
        <name>ECDSA</name>
        <alias>Elliptic Curve Digital Signature Algorithm</alias>
    </topic>
    <topic domain="wwww" TID="dbms" crdate="20000621">
        <derived-from template="concept"/>
        <name>DBMS</name>
        <alias>Database Management System</alias>
    </topic>
    <topic domain="wwww" TID="ordbms" crdate="20031116">
        <derived-from template="dbms"/>
        <name>ORDBMS</name>
        <alias>Object-Relational Database Management System</alias>
    </topic>
    <topic domain="wwww" TID="rdbms" crdate="20000621">
        <derived-from template="dbms"/>
        <name>RDBMS</name>
        <alias>Relational Database Management System</alias>
    </topic>
    <topic domain="wwww" TID="xdbms" crdate="20030114" modate="20030515">
        <derived-from template="dbms"/>
        <name>XDBMS</name>
        <alias>XML Database Management System</alias>
    </topic>
    <topic domain="wwww" TID="oodbms" crdate="20000621">
        <derived-from template="dbms"/>
        <name>OODBMS</name>
        <alias>Object-Oriented Database Management System</alias>
    </topic>
    <topic domain="wwww" TID="cli" crdate="20000919">
        <derived-from template="api"/>
        <name>CLI</name>
        <alias>Call Level Interface</alias>
    </topic>
    <topic domain="wwww" TID="odbc" crdate="20000621">
        <derived-from template="api"/>
        <name>ODBC</name>
        <alias>Open Database Connectivity</alias>
    </topic>
    <topic domain="wwww" TID="docbook" crdate="20020628">
        <derived-from template="textformat"/>
        <name>DocBook</name>
    </topic>
    <topic domain="wwww" TID="hsg" crdate="20060305">
        <derived-from template="textformat"/>
        <name>HSG</name>
        <alias>Help System Generator</alias>
    </topic>
    <topic domain="wwww" TID="dita" crdate="20060305">
        <derived-from template="textformat"/>
        <name>DITA</name>
        <alias>Darwin Information Typing Architecture</alias>
    </topic>
    <topic domain="wwww" TID="ebx" crdate="20020629">
        <derived-from template="concept"/>
        <name>EBX</name>
        <alias>Electronic Book Exchange</alias>
    </topic>
    <topic domain="wwww" TID="bbeb" crdate="20070425">
        <derived-from template="textformat"/>
        <name>BBeB</name>
        <alias>Broadband eBook</alias>
    </topic>
    <topic domain="wwww" TID="oeb" crdate="20000705">
        <derived-from template="textformat"/>
        <name>OEB</name>
        <alias>Open eBook</alias>
    </topic>
    <topic domain="wwww" TID="iotp" crdate="20000804">
        <derived-from template="protocol"/>
        <name>IOTP</name>
        <alias>Internet Open Trading Protocol</alias>
    </topic>
    <topic domain="wwww" TID="otp" crdate="20000705">
        <derived-from template="protocol"/>
        <name>OTP</name>
        <alias>Open Trading Protocol</alias>
    </topic>
    <topic domain="wwww" TID="jca" crdate="20010915">
        <derived-from template="topic"/>
        <name>JCA</name>
        <alias>Java Cryptography Architecture</alias>
    </topic>
    <topic domain="wwww" TID="jce" crdate="20010915">
        <derived-from template="topic"/>
        <name>JCE</name>
        <alias>Java Cryptography Extension</alias>
    </topic>
    <topic domain="wwww" TID="jndi" crdate="20001213">
        <derived-from template="api"/>
        <name>JNDI</name>
        <alias>Java Naming and Directory Interface</alias>
    </topic>
    <topic domain="wwww" TID="netware" crdate="20001220">
        <derived-from template="dfs"/>
        <name>NetWare</name>
    </topic>
    <topic domain="wwww" TID="nds" crdate="20001213">
        <derived-from template="directory"/>
        <name>NDS</name>
        <alias>Novell Directory Services</alias>
    </topic>
    <topic domain="wwww" TID="sqlj" crdate="20030827">
        <derived-from template="api"/>
        <name>SQLj</name>
    </topic>
    <topic domain="wwww" TID="jdo" crdate="20040817">
        <derived-from template="api"/>
        <name>JDO</name>
        <alias>Java Data Objects</alias>
    </topic>
    <topic domain="wwww" TID="xqj" crdate="20040921">
        <derived-from template="api"/>
        <name>XQJ</name>
        <alias>XQuery API for Java</alias>
    </topic>
    <topic domain="wwww" TID="jdbc" crdate="20000621">
        <derived-from template="api"/>
        <name>JDBC</name>
        <alias>Java Database Connectivity</alias>
    </topic>
    <topic domain="wwww" TID="xupdate" modate="20031116" crdate="20021220">
        <derived-from template="dml"/>
        <name>XUpdate</name>
        <alias>XML Update Language</alias>
    </topic>
    <topic domain="wwww" TID="sixdml" modate="20031116" crdate="20021220">
        <derived-from template="dml"/>
        <name>SiXDML</name>
        <alias>Simple XML Data Manipulation Language</alias>
    </topic>
    <topic domain="wwww" TID="oql" crdate="20020417">
        <derived-from template="querylanguage"/>
        <name>OQL</name>
        <alias>Object Query Language</alias>
    </topic>
    <topic domain="wwww" TID="sqlxml" crdate="20021217">
        <derived-from template="querylanguage"/>
        <name>SQL/XML</name>
    </topic>
    <topic domain="wwww" TID="yql" crdate="20081209">
        <derived-from template="querylanguage"/>
        <name>YQL</name>
        <alias>Yahoo! Query Language</alias>
    </topic>
    <topic domain="wwww" TID="fiql" crdate="20081209">
        <derived-from template="querylanguage"/>
        <name>FIQL</name>
        <alias>Feed Item Query Language</alias>
    </topic>
    <topic domain="wwww" TID="sql" crdate="20000621">
        <derived-from template="querylanguage"/>
        <derived-from template="ddl"/>
        <derived-from template="dml"/>
        <name>SQL</name>
        <alias>Structured Query Language</alias>
    </topic>
    <topic domain="wwww" TID="qbe" crdate="20070424">
        <derived-from template="querylanguage"/>
        <name>QBE</name>
        <alias>Query by Example</alias>
    </topic>
    <topic domain="wwww" TID="xsql" crdate="20001213">
        <derived-from template="technology"/>
        <name>XSQL</name>
    </topic>
    <topic domain="wwww" TID="georss" crdate="20081209">
        <derived-from template="dataformat"/>
        <name>GeoRSS</name>
    </topic>
    <topic domain="wwww" TID="woff" crdate="20091102">
        <derived-from template="dataformat"/>
        <name>WOFF</name>
        <alias>Web Open Font Format</alias>
    </topic>
    <topic domain="wwww" TID="off" crdate="20091102">
        <derived-from template="dataformat"/>
        <name>OFF</name>
        <alias>Open Font Format</alias>
    </topic>
    <topic domain="wwww" TID="webfonts" crdate="20010816">
        <derived-from template="dataformat"/>
        <name>WebFonts</name>
        <desc>The <topicref TID="webfonts"/> specification is part of <topicref TID="css2"/>, it allows improved client-side font matching, enables font synthesis and progressive rendering, and enables fonts to be downloaded over the <topicref TID="www"/>. However, <topicref TID="webfonts"/> does not specify a particular <topicref TID="dataformat"/> for downloadable fonts, it only defines a mechanism for font description.</desc>
    </topic>
    <topic domain="wwww" TID="opentype" crdate="20010317">
        <derived-from template="fontformat"/>
        <name>OpenType</name>
        <desc>The <topicref TID="opentype"/> <topicref TID="fontformat"/> is an extension of the <topicref TID="truetype"/> <topicref TID="fontformat"/>, adding support for <topicref TID="type1"/> font data. The <topicref TID="opentype"/> <topicref TID="fontformat"/> was developed jointly by <topicref TID="microsoft"/> and <topicref TID="adobe"/>. As with <topicref TID="truetype"/> fonts, <topicref TID="opentype"/> fonts allow the handling of large glyph sets using <topicref TID="unicode"/> encoding. Such encoding allows broad international support, as well as support for typographic glyph variants. Additionally, <topicref TID="opentype"/> fonts may contain digital signatures, allowing <topicref TID="os"/>s and <topicref TID="browser"/>s to identify the source and integrity of font files, including embedded font files obtained in <topicref TID="www"/> documents, before using them. Also, font developers can encode embedding restrictions in <topicref TID="opentype"/> fonts, and these restrictions cannot be altered in a font signed by the developer.</desc>
    </topic>
    <topic domain="wwww" TID="type1" crdate="20010317">
        <derived-from template="fontformat"/>
        <name>Type 1</name>
        <desc>Originally developed by <topicref TID="adobe"/> for their <topicref TID="postscript"/> page description language, the <topicref TID="type1"/> <topicref TID="fontformat"/> has been accepted as an <topicref TID="iso"/> standard. <topicref TID="type1"/> fonts use a specialized subset of the <topicref TID="postscript"/> language which is optimized for better performance and a more compact representation. The <topicref TID="type1"/> operator set includes hint information which helps font rasterizers create more accurate bitmaps for smaller sizes and lower resolutions. <topicref TID="type1"/> is one of the foundations for the <topicref TID="opentype"/> <topicref TID="fontformat"/>.</desc>
    </topic>
    <topic domain="wwww" TID="truetype" crdate="20010317">
        <derived-from template="fontformat"/>
        <name>TrueType</name>
        <desc><topicref TID="truetype"/> is a <topicref TID="fontformat"/> developed by <topicref TID="apple"/> and licensed to <topicref TID="microsoft"/>. <topicref TID="truetype"/> is the native <topicref TID="os"/> <topicref TID="fontformat"/> for <topicref TID="windows"/> and <topicref TID="macos"/>. <topicref TID="truetype"/> contains a hierarchical set of tables and glyph representations. Characters can be hinted on a per character and point size basis yielding excellent quality at screen resolutions. <topicref TID="truetype"/> fonts for <topicref TID="windows"/> and <topicref TID="macos"/> have few differences, though they can be different enough to prevent cross platform usage. Font foundries provide <topicref TID="truetype"/> fonts for each platform and usually include a license preventing electronic manipulation to achieve cross platform transparency. <topicref TID="truetype"/> is one of the foundations for the <topicref TID="opentype"/> <topicref TID="fontformat"/>.</desc>
    </topic>
    <topic domain="wwww" TID="xxl" crdate="20030128">
        <derived-from template="querylanguage"/>
        <name>XXL</name>
        <alias>Flexible XML Search Language</alias>
    </topic>
    <topic domain="wwww" TID="xirql" crdate="20030128">
        <derived-from template="querylanguage"/>
        <name>XIRQL</name>
        <alias>XML Information Retrieval Query Language</alias>
    </topic>
    <topic domain="wwww" TID="xql" crdate="20001213">
        <derived-from template="querylanguage"/>
        <name>XQL</name>
        <alias>XML Query Language</alias>
    </topic>
    <topic domain="wwww" TID="worlddab" crdate="20000817">
        <derived-from template="consortium"/>
        <name>World DAB Forum</name>
    </topic>
    <topic domain="wwww" TID="dab" crdate="20000817">
        <derived-from template="technology"/>
        <name>DAB</name>
        <alias>Digital Audio Broadcasting</alias>
    </topic>
    <topic domain="wwww" TID="ber" crdate="20000919">
        <derived-from template="dataformat"/>
        <name>BER</name>
        <alias>Basic Encoding Rules</alias>
    </topic>
    <topic domain="wwww" TID="cxer" crdate="20020904">
        <derived-from template="normalform"/>
        <name>CXER</name>
        <alias>Canonical XML Encoding Rules</alias>
    </topic>
    <topic domain="wwww" TID="xer" crdate="20010322">
        <derived-from template="dataformat"/>
        <name>XER</name>
        <alias>XML Encoding Rules</alias>
        <desc><topicref TID="asn1"/> <topicref TID="xer"/> is a set of encoding rules that encode <topicref TID="asn1"/> data in <topicref TID="xml"/> document syntax. While this encoding is not as compact as other encoding rules commonly used for <topicref TID="asn1"/>, it enables users to on the one hand use <topicref TID="asn1"/>'s powerful syntax, and on the other hand generate data from it which can be processed using existing <topicref TID="xml"/> tools (such as <topicref TID="xslt"/>). Furthermore, because <topicref TID="xer"/> uses <topicref TID="xml"/> syntax, it is human-readable, while all other <topicref TID="asn1"/> encoding rules generate binary data.</desc>
    </topic>
    <topic domain="wwww" TID="cer" crdate="20000919">
        <derived-from template="dataformat"/>
        <name>CER</name>
        <alias>Canonical Encoding Rules</alias>
    </topic>
    <topic domain="wwww" TID="gser" crdate="20031124">
        <derived-from template="dataformat"/>
        <name>GSER</name>
        <alias>Generic String Encoding Rules</alias>
    </topic>
    <topic domain="wwww" TID="der" crdate="20000919">
        <derived-from template="dataformat"/>
        <name>DER</name>
        <alias>Distinguished Encoding Rules</alias>
    </topic>
    <topic domain="wwww" TID="per" crdate="20000919">
        <derived-from template="dataformat"/>
        <name>PER</name>
        <alias>Packed Encoding Rules</alias>
    </topic>
    <topic domain="wwww" TID="mhm" crdate="20020702">
        <derived-from template="concept"/>
        <name>MHM</name>
        <alias>Multiplexed Hierarchical Modeling</alias>
    </topic>
    <topic domain="wwww" TID="opc" crdate="20081208">
        <derived-from template="dataformat"/>
        <name>OPC</name>
        <alias>Open Packaging Conventions</alias>
    </topic>
    <topic domain="wwww" TID="rar" crdate="20061206">
        <derived-from template="compressionformat"/>
        <name>RAR</name>
        <alias>Roshal Archive</alias>
    </topic>
    <topic domain="wwww" TID="zip" crdate="20061206">
        <derived-from template="compressionformat"/>
        <name>ZIP</name>
    </topic>
    <topic domain="wwww" TID="xmlppm" crdate="20020702">
        <derived-from template="xmlcompressionformat"/>
        <name>XMLPPM</name>
        <alias>XML-Conscious PPM Compression</alias>
    </topic>
    <topic domain="wwww" TID="xmill" crdate="20020702">
        <derived-from template="xmlcompressionformat"/>
        <name>XMill</name>
    </topic>
    <topic domain="wwww" TID="xbis" crdate="20040715">
        <derived-from template="xmlcompressionformat"/>
        <name>XBIS</name>
        <alias>XML Binary Infoset</alias>
        <desc><topicref TID="xbis"/> is an encoding format for <topicref TID="xml"/> documents that is fully convertible to and from text, with <topicref TID="xmlinfoset"/> equivalence between the original document text and regenerated document text. It is intended for use in transmitting <topicref TID="xml"/> documents between application components, and is therefore designed for processing speed.</desc>
    </topic>
    <topic domain="wwww" TID="xcq" crdate="20030521">
        <derived-from template="xmlcompressionformat"/>
        <name>XCQ</name>
    </topic>
    <topic domain="wwww" TID="millau" crdate="20020702">
        <derived-from template="xmlcompressionformat"/>
        <name>Millau</name>
    </topic>
    <topic domain="wwww" TID="sxml" crdate="20020702">
        <derived-from template="dataformat"/>
        <name>SXML</name>
        <alias>Schema-driven XML</alias>
    </topic>
    <topic domain="wwww" TID="sdom" modate="20020806" crdate="20020702">
        <derived-from template="xmlapi"/>
        <derived-from template="xmlschemaapi"/>
        <name>SDOM</name>
        <alias>Schema-driven DOM</alias>
    </topic>
    <topic domain="wwww" TID="sas" modate="20020806" crdate="20020702">
        <derived-from template="xmlapi"/>
        <derived-from template="xmlschemaapi"/>
        <name>SAS</name>
        <alias>Schema-driven SAX</alias>
    </topic>
    <topic domain="wwww" TID="esax" crdate="20020702">
        <derived-from template="dataformat"/>
        <name>ESAX</name>
        <alias>Encoded SAX</alias>
    </topic>
    <topic domain="wwww" TID="canonicalxml" crdate="20010320">
        <derived-from template="normalform"/>
        <name>Canonical XML</name>
        <desc><topicref TID="canonicalxml"/> refers to <topicref TID="xml"/> that is in canonical form. XML canonicalization is a process that generates the <topicref TID="canonicalxml"/> of a given <topicref TID="xml"/> document. <topicref TID="xml"/> specifies the syntax of <topicref TID="xml"/> documents. <topicref TID="xmlns"/> specifies additional syntax and semantics for <topicref TID="xml"/> documents. Because of the syntax of <topicref TID="xml"/>, it is possible for <topicref TID="xml"/> documents which are equivalent for the purposes of many applications to differ in physical representation. For example, they may differ in whitespace occurrences, their entity structure, attribute ordering, and character encoding. <topicref TID="canonicalxml"/> establishes a method for determining whether two documents are identical, or whether an application has not changed a document, except for transformations permitted by <topicref TID="xml"/> and <topicref TID="xmlns"/>.</desc>
    </topic>
    <topic domain="wwww" TID="sdxf" modate="20040206" crdate="20010918">
        <derived-from template="dataformat"/>
        <name>SDXF</name>
        <alias>Structured Data Exchange Format</alias>
        <desc>The purpose of <topicref TID="sdxf"/> is to permit the interchange of an arbitrary structured data block with different kinds of data (numerical, text, bitstrings, ...). Because data is normalized to an abstract computer architecture independent "network format", <topicref TID="sdxf"/> is usable as a network interchange <topicref TID="dataformat"/>. <topicref TID="sdxf"/> is also capable of compressing and encrypting parts or the whole block of <topicref TID="sdxf"/> data.</desc>
    </topic>
    <topic domain="wwww" TID="chm" crdate="20020301">
        <derived-from template="dataformat"/>
        <name>CHM</name>
        <alias>Compiled HTML Help Format</alias>
    </topic>
    <topic domain="wwww" TID="dvb" crdate="20000817">
        <derived-from template="technology"/>
        <name>DVB</name>
        <alias>Digital Video Broadcasting</alias>
    </topic>
    <topic domain="wwww" TID="dvbt" crdate="20020215">
        <derived-from template="dvb"/>
        <name>DVB-T</name>
        <alias>Digital Video Broadcasting - Terrestrial</alias>
    </topic>
    <topic domain="wwww" TID="dvbc" crdate="20020215">
        <derived-from template="dvb"/>
        <name>DVB-C</name>
        <alias>Digital Video Broadcasting - Cable</alias>
    </topic>
    <topic domain="wwww" TID="dvbs" crdate="20020215">
        <derived-from template="dvb"/>
        <name>DVB-S</name>
        <alias>Digital Video Broadcasting - Satellite</alias>
    </topic>
    <topic domain="wwww" TID="havi" crdate="20000817">
        <derived-from template="technology"/>
        <name>HAVi</name>
        <alias>Home Audio Video Interoperability</alias>
    </topic>
    <topic domain="wwww" TID="davic" crdate="20000817">
        <derived-from template="organization"/>
        <name>DAVIC</name>
        <alias>Digital Audio Video Council</alias>
    </topic>
    <topic domain="wwww" TID="etsi" crdate="20000803">
        <derived-from template="internationalorganization"/>
        <name>ETSI</name>
        <alias>European Telecommunications Standards Institute</alias>
    </topic>
    <topic domain="wwww" TID="ecma" crdate="20000622">
        <derived-from template="organization"/>
        <name>ECMA</name>
        <alias>European Computer Manufacturers Association</alias>
        <desc><topicref TID="ecma"/> is an international, europe-based industry association founded in 1961 and dedicated to the standardization of information and communication systems. Many <topicref TID="ecma"/> standards have been accepted as a base for international and european standards. To ensure close cooperation <topicref TID="ecma"/> has established formal liaisons with all european and international standardization bodies. <topicref TID="ecma"/> standards are developed by highly qualified experts from information technology and telecommunication industry with the commitment to provide in a consensus mode technical solutions ready for implementation in product development and conformance testing.</desc>
    </topic>
    <topic domain="wwww" TID="rarp" crdate="20000912">
        <derived-from template="resprotocol"/>
        <name>RARP</name>
        <alias>Reverse Address Resolution Protocol</alias>
    </topic>
    <topic domain="wwww" TID="ieee802" crdate="20010312">
        <derived-from template="protocol"/>
        <name>IEEE 802</name>
    </topic>
    <topic domain="wwww" TID="ieee8022" crdate="20010312">
        <derived-from template="llc"/>
        <name>IEEE 802.2</name>
    </topic>
    <topic domain="wwww" TID="ieee8023" crdate="20010312">
        <derived-from template="ethernet"/>
        <name>IEEE 802.3</name>
    </topic>
    <topic domain="wwww" TID="ieee8024" crdate="20010312">
        <derived-from template="tokenbus"/>
        <name>IEEE 802.4</name>
    </topic>
    <topic domain="wwww" TID="ieee8025" crdate="20010312">
        <derived-from template="tokenring"/>
        <name>IEEE 802.5</name>
    </topic>
    <topic domain="wwww" TID="ieee8026" crdate="20010312">
        <derived-from template="dqdb"/>
        <name>IEEE 802.6</name>
    </topic>
    <topic domain="wwww" TID="ieee80216" crdate="20041031">
        <derived-from template="ieee802"/>
        <name>IEEE 802.16</name>
        <desc>A <topicref TID="man"/> standard with a maximum bandwidth of 268 Mbps. It is designed for systems in the frequency ranges 10-66 GHz and sub 11 GHz.</desc>
    </topic>
    <topic domain="wwww" TID="ieee80211n" crdate="20061111">
        <derived-from template="ieee80211"/>
        <name>IEEE 802.11n</name>
        <desc>A <topicref TID="wlan"/> standard with a maximum bandwidth of 540 Mbps, it was designed to replace the slower <topicref TID="ieee80211a"/> and <topicref TID="ieee80211g"/>. It operates in the 2.4 and 5 GHz frequency bands.</desc>
    <status><topicref TID="ieee80211n"/> is not expected to be finalized as a stable specification before 2008. However, vendors already start selling equipment according to draft versions of the <topicref TID="ieee80211n"/> standard. This equipment is often labeled as "Draft N", "802.11n Draft", or "Draft 802.11n", and most vendors claim that it will be upgradable once the specification is finalized.</status>
    </topic>
    <topic domain="wwww" TID="ieee80211i" crdate="20040810">
        <derived-from template="ieee80211"/>
        <name>IEEE 802.11i</name>
        <desc><topicref TID="ieee80211i"/> is the successor of the <topicref TID="wpa"/> security layer for <topicref TID="ieee80211"/> <topicref TID="wlan"/>s. <topicref TID="ieee80211i"/> defines mechanisms for <topicref TID="authentication"/> and <topicref TID="encryption"/> and enables users to securely communicate within a wireless environment.</desc>
    </topic>
    <topic domain="wwww" TID="ieee80211g" crdate="20040522">
        <derived-from template="ieee80211"/>
        <name>IEEE 802.11g</name>
        <desc>A <topicref TID="wlan"/> standard with a maximum bandwidth of 54 Mbps, it was designed to replace the slower <topicref TID="ieee80211b"/>. It operates in the 2.4 GHz frequency band.</desc>
    </topic>
    <topic domain="wwww" TID="ieee80211a" crdate="20040522">
        <derived-from template="ieee80211"/>
        <name>IEEE 802.11a</name>
        <desc>A <topicref TID="wlan"/> standard with a maximum bandwidth of 54 Mbps, it was designed to replace the slower <topicref TID="ieee80211b"/>. It operates in the 5 GHz frequency band.</desc>
    </topic>
    <topic domain="wwww" TID="ieee80211b" crdate="20020624">
        <derived-from template="ieee80211"/>
        <name>IEEE 802.11b</name>
        <desc>A <topicref TID="wlan"/> standard with a maximum bandwidth of 11 Mbps, it was designed to replace the slower <topicref TID="ieee80211"/>. It operates in the 2.4 GHz frequency band.</desc>
    </topic>
    <topic domain="wwww" TID="ieee80211" crdate="20010312">
        <derived-from template="wlan"/>
        <name>IEEE 802.11</name>
        <desc>A <topicref TID="wlan"/> standard with a maximum bandwidth of 2 Mbps. It is a wireless variant of the <topicref TID="ethernet"/> protocol. It operates in the 2.4 GHz frequency band.</desc>
    </topic>
    <topic domain="wwww" TID="ieee802151" crdate="20010312">
        <derived-from template="wpan"/>
        <name>IEEE 802.15.1</name>
    </topic>
    <topic domain="wwww" TID="ieee802154" crdate="20051026">
        <derived-from template="wpan"/>
        <name>IEEE 802.15.4</name>
    </topic>
    <topic domain="wwww" TID="ssid" crdate="20010906">
        <derived-from template="topic"/>
        <name>SSID</name>
        <alias>Service Set Identifier</alias>
    </topic>
    <topic domain="wwww" TID="bss" crdate="20010906">
        <derived-from template="topic"/>
        <name>BSS</name>
        <alias>Basic Service Set</alias>
    </topic>
    <topic domain="wwww" TID="tkip" crdate="20040102">
        <derived-from template="protocol"/>
        <name>TKIP</name>
        <alias>Temporal Key Integrity Protocol</alias>
    </topic>
    <topic domain="wwww" TID="wpa" modate="20040810" crdate="20040102">
        <derived-from template="protocol"/>
        <name>WPA</name>
        <alias>Wi-Fi Protected Access</alias>
        <status><topicref TID="wpa"/> was created by the <topicref TID="wifialliance"/> in 2002, in part out of impatience with the slow-moving <topicref TID="ieee80211i"/> standard. The industry consortium's consensus was that an alternative to <topicref TID="wep"/> was needed quickly, and <topicref TID="wpa"/> was the result. To avoid multiple standards and conflicts later on, <topicref TID="wpa"/> was designed from the get-go to be compatible with <topicref TID="ieee80211i"/> and was based on its early draft specifications. The finalized version of <topicref TID="ieee80211i"/> is now referred to as <topicref TID="wpa2"/>.</status>
    </topic>
    <topic domain="wwww" TID="wpa2" crdate="20070801">
        <derived-from template="protocol"/>
        <name>WPA2</name>
        <alias>Wi-Fi Protected Access 2</alias>
        <status><topicref TID="wpa2"/> is the final version of <topicref TID="ieee80211i"/> authentication for wireless networks and thus is an updated version of <topicref TID="wpa"/>, which is based on earlier draft versions of the standard. Older hardware might only support <topicref TID="wep"/> and <topicref TID="wpa"/> authentication, whereas newer hardware often supports <topicref TID="wep"/>, <topicref TID="wpa"/>, and <topicref TID="wpa2"/>.</status>
    </topic>
    <topic domain="wwww" TID="wep" modate="20040810" crdate="20010411">
        <derived-from template="protocol"/>
        <name>WEP</name>
        <alias>Wired Equivalent Privacy</alias>
        <status><topicref TID="wep"/> as the <topicref TID="encryption"/> method of <topicref TID="ieee80211"/> devices is now widely recognized as flawed. <topicref TID="wep"/> used the same key among all communicating devices. <topicref TID="wep"/>'s problems are well-known, including an insufficient key length and no automated method for distributing the keys. <topicref TID="wep"/> can be easily cracked in a couple of hours with off-the-shelf tools. For reasonable security, <topicref TID="wpa"/> or its successor, <topicref TID="ieee80211i"/>, are the alternatives.</status>
    </topic>
    <topic domain="wwww" TID="webstone" crdate="20010321">
        <derived-from template="topic"/>
        <name>WebStone</name>
        <desc><topicref TID="webstone"/> is a benchmark for measuring the performance of <topicref TID="httpserver"/> platforms (software and hardware combined). It is designed to measure the performance of <topicref TID="httpserver"/>s under multiple scenarios which reflect different <topicref TID="www"/> site profiles. The test uses workload parameters and clients to generate <topicref TID="http"/> traffic that allows an <topicref TID="httpserver"/> to be stressed in a number of different ways.</desc>
    </topic>
    <topic domain="wwww" TID="specweb" crdate="20010321">
        <derived-from template="topic"/>
        <name>SPECweb</name>
        <desc><topicref TID="specweb"/> a standardized benchmark for comparing <topicref TID="httpserver"/> performance. The benchmark is designed to provide comparable measures of how well systems can handle <topicref TID="http"/> GET requests. The workload s based upon analysis of <topicref TID="httpserver"/> logs from <topicref TID="www"/> sites ranging from a small personal server up through some of the <topicref TID="www"/>'s most popular servers.</desc>
    </topic>
    <topic domain="wwww" TID="spec" crdate="20010321">
        <derived-from template="consortium"/>
        <name>SPEC</name>
        <alias>Standard Performance Evaluation Corporation</alias>
        <desc><topicref TID="spec"/> was founded in 1988 by a small number of workstation vendors. <topicref TID="spec"/> has grown to become one of the more successful performance standardization bodies with more than 40 member companies. <topicref TID="spec"/> publishes several hundred different performance results each quarter spanning across a variety of system performance disciplines. The goal of <topicref TID="spec"/> is to ensure that the marketplace has a fair and useful set of metrics to differentiate candidate systems. The path chosen is an attempt to balance between requiring strict compliance and allowing vendors to demonstrate their advantages.</desc>
    </topic>
    <topic domain="wwww" TID="llc" crdate="20010309">
        <derived-from template="protocol"/>
        <name>LLC</name>
        <alias>Logical Link Control</alias>
    </topic>
    <topic domain="wwww" TID="ethernet" crdate="20010312">
        <derived-from template="lan"/>
        <name>Ethernet</name>
    </topic>
    <topic domain="wwww" TID="csma" crdate="20010312">
        <derived-from template="protocol"/>
        <name>CSMA</name>
        <alias>Carrier Sense Multiple Access</alias>
    </topic>
    <topic domain="wwww" TID="csmacd" crdate="20010312">
        <derived-from template="csma"/>
        <name>CSMA/CD</name>
        <alias>Carrier Sense Multiple Access/Collision Detection</alias>
    </topic>
    <topic domain="wwww" TID="tokenbus" crdate="20010312">
        <derived-from template="lan"/>
        <name>Token Bus</name>
    </topic>
    <topic domain="wwww" TID="tokenring" crdate="20010312">
        <derived-from template="lan"/>
        <name>Token Ring</name>
    </topic>
    <topic domain="wwww" TID="qpsx" crdate="20020629">
        <derived-from template="man"/>
        <name>QPSX</name>
        <alias>Queued Packet Switch Exchange</alias>
    </topic>
    <topic domain="wwww" TID="dqdb" crdate="20010309">
        <derived-from template="man"/>
        <name>DQDB</name>
        <alias>Distributed Queue Dual Bus</alias>
    </topic>
    <topic domain="wwww" TID="fddi" crdate="20010309">
        <derived-from template="man"/>
        <name>FDDI</name>
        <alias>Fibre Distributed Data Interface</alias>
    </topic>
    <topic domain="wwww" TID="macode" crdate="20010311">
        <derived-from template="topic"/>
        <name>MAC</name>
        <alias>Message Authentication Code</alias>
        <desc>A <topicref TID="macode"/> is an <topicref TID="authentication"/> tag (also called a checksum) derived by application of an authentication scheme, together with a secret key, to a message. <topicref TID="macode"/>s are computed and verified with the same key so they can only be verified by the intended receiver, unlike digital signatures. <topicref TID="macode"/>s can be derived from various cryptographic techniques and <topicref TID="algorithm"/>s, such as <topicref TID="sha"/>, <topicref TID="md5"/>, or <topicref TID="des"/>.</desc>
    </topic>
    <topic domain="wwww" TID="mac" crdate="20010309">
        <derived-from template="protocol"/>
        <name>MAC</name>
        <alias>Media Access Control</alias>
    </topic>
    <topic domain="wwww" TID="qos" crdate="20020716">
        <derived-from template="concept"/>
        <name>QoS</name>
        <alias>Quality of Service</alias>
    </topic>
    <topic domain="wwww" TID="intserv" crdate="20020716">
        <derived-from template="framework"/>
        <name>IntServ</name>
        <alias>Integrated Services</alias>
    </topic>
    <topic domain="wwww" TID="diffserv" crdate="20020716">
        <derived-from template="framework"/>
        <name>DiffServ</name>
        <alias>Differentiated Services</alias>
    </topic>
    <topic domain="wwww" TID="nat" crdate="20010309">
        <derived-from template="concept"/>
        <name>NAT</name>
        <alias>Network Address Translation</alias>
    </topic>
    <topic domain="wwww" TID="skip" crdate="20010311">
        <derived-from template="certsystem"/>
        <name>SKIP</name>
        <alias>Simple Key management for Internet Protocols</alias>
    </topic>
    <topic domain="wwww" TID="arpanet" crdate="20010315">
        <derived-from template="topic"/>
        <name>ARPANET</name>
        <desc>The <topicref TID="arpanet"/> is the precursor to the <topicref TID="internet"/>. It was established through an <topicref TID="arpa"/>-funded research program in 1968 and provided the foundation of the <topicref TID="internet"/> by providing the <topicref TID="protocol"/>s as well as the infrastructure. The original <topicref TID="arpanet"/> grew into the <topicref TID="internet"/>.</desc>
    </topic>
    <topic domain="wwww" TID="arp" crdate="20000912">
        <derived-from template="resprotocol"/>
        <name>ARP</name>
        <alias>Address Resolution Protocol</alias>
    </topic>
    <topic domain="wwww" TID="pgp" crdate="20000912">
        <derived-from template="certsystem"/>
        <name>PGP</name>
        <alias>Pretty Good Privacy</alias>
    </topic>
    <topic domain="wwww" TID="gpg" crdate="20060524">
        <derived-from template="certsystem"/>
        <name>GPG</name>
        <alias>GNU Privacy Guard</alias>
    </topic>
    <topic domain="wwww" TID="darpa" crdate="20000612">
        <derived-from template="nationalorganization"/>
        <name>DARPA</name>
        <alias>Defense Advanced Research Projects Agency</alias>
        <desc><topicref TID="darpa"/>, until 1973 known as <topicref TID="arpa"/>, is the main source for research funds in the United States. In particular, the <topicref TID="internet"/> (its first infrastructure as well as the protocol suite) originated from the <topicref TID="arpanet"/>, a network which was first designed for US military purposes with the primary design goal to be robust.</desc>
    </topic>
    <topic domain="wwww" TID="ccitt" crdate="20000612">
        <derived-from template="internationalorganization"/>
        <name>CCITT</name>
        <alias>Consultative Committee on International Telegraphy and Telephony</alias>
        <desc>Former name of the <topicref TID="itu"/> before it was renamed in 1993.</desc>
    </topic>
    <topic domain="wwww" TID="annotea" crdate="20020814">
        <derived-from template="ohs"/>
        <name>Annotea</name>
    </topic>
    <topic domain="wwww" TID="hyperg" crdate="20000612">
        <derived-from template="hmsystem"/>
        <name>Hyper-G</name>
    </topic>
    <topic domain="wwww" TID="hyperwave" crdate="20000612">
        <derived-from template="hmsystem"/>
        <name>Hyperwave</name>
    </topic>
    <topic domain="wwww" TID="arpa" crdate="20000612">
        <derived-from template="nationalorganization"/>
        <name>ARPA</name>
        <alias>Advanced Research Projects Agency</alias>
    </topic>
    <topic domain="wwww" TID="itu" crdate="20000612">
        <derived-from template="internationalorganization"/>
        <name>ITU</name>
        <alias>International Telecommunication Union</alias>
        <desc><topicref TID="itu"/> is an <topicref TID="internationalorganization"/>, within which the public and private sectors cooperate for the development of telecommunications. <topicref TID="itu"/> adopts international regulations and treaties governing all terrestrial and space uses of the frequency spectrum as well as the use of the geostationary-satellite orbit, within which countries adopt their national legislation. It also develops standards to facilitate the interconnection of telecommunication systems on a worldwide scale regardless of the type of technology used.</desc>
    </topic>
    <topic domain="wwww" TID="rab" crdate="20020322">
        <derived-from template="organization"/>
        <name>RAB</name>
        <alias>RAID Advisory Board</alias>
    </topic>
    <topic domain="wwww" TID="raid" crdate="20020322">
        <derived-from template="concept"/>
        <name>RAID</name>
        <alias>Redundant Array of Independent Disks</alias>
    </topic>
    <topic domain="wwww" TID="wgs84" crdate="20070725">
        <derived-from template="dataformat"/>
        <name>WGS84</name>
        <alias>World Geodetic System 84</alias>
    </topic>
    <topic domain="wwww" TID="gps" crdate="20030701">
        <derived-from template="technology"/>
        <name>GPS</name>
        <alias>Global Positioning System</alias>
    </topic>
    <topic domain="wwww" TID="egnos" crdate="20030701">
        <derived-from template="technology"/>
        <name>EGNOS</name>
        <alias>European Geostationary Navigation Overlay Service</alias>
        <desc><topicref TID="egnos"/> is an overlay system for the <topicref TID="gps"/> service which enhances the accuracy of <topicref TID="gps"/> navigation by transmitting differential information. <topicref TID="egnos"/> can be used in Europe only (similar services are available as <topicref TID="waas"/> in North America and as <topicref TID="msas"/> in Japan).</desc>
    </topic>
    <topic domain="wwww" TID="waas" crdate="20030701">
        <derived-from template="technology"/>
        <name>WAAS</name>
        <alias>Wide Area Augmentation System</alias>
        <desc><topicref TID="waas"/> is an overlay system for the <topicref TID="gps"/> service which enhances the accuracy of <topicref TID="gps"/> navigation by transmitting differential information. <topicref TID="waas"/> can be used in North America only (similar services are available as <topicref TID="egnos"/> in Europe and as <topicref TID="msas"/> in Japan).</desc>
    </topic>
    <topic domain="wwww" TID="msas" crdate="20030701">
        <derived-from template="technology"/>
        <name>MSAS</name>
        <alias>MTSAT Satellite based Augmentation System</alias>
        <desc><topicref TID="msas"/> is an overlay system for the <topicref TID="gps"/> service which enhances the accuracy of <topicref TID="gps"/> navigation by transmitting differential information. <topicref TID="msas"/> can be used in Japan only (similar services are available as <topicref TID="waas"/> in North America and as <topicref TID="egnos"/> in Europe).</desc>
    </topic>
    <topic domain="wwww" TID="edap" crdate="20020322">
        <derived-from template="concept"/>
        <name>EDAP</name>
        <alias>Extended Data Availability and Protection</alias>
    </topic>
    <topic domain="wwww" TID="sim" crdate="20001213">
        <derived-from template="technology"/>
        <name>SIM</name>
        <alias>Subscriber Identity Module</alias>
    </topic>
    <topic domain="wwww" TID="gsm" crdate="20000612">
        <derived-from template="wlinterface"/>
        <name>GSM</name>
        <alias>Global System for Mobile Communications</alias>
        <desc><topicref TID="gsm"/> is a digital cellular communications system. It was developed in order to create a common european mobile telephone standard but it has been rapidly accepted worldwide. <topicref TID="gsm"/> was designed to be compatible with <topicref TID="isdn"/> services. The disadvantage of this design is the focus on circuit-switched technologies, which currently makes <topicref TID="gsm"/> less than ideally suited for mobile data access. However, with the introduction of <topicref TID="gprs"/> in newer versions of the <topicref TID="gsm"/> standard, <topicref TID="gsm"/> becomes capable of handling packet-switched traffic.</desc>
    </topic>
    <topic domain="wwww" TID="jstl" crdate="20030515">
        <derived-from template="serversidetechnology"/>
        <name>JSTL</name>
        <alias>JSP Standard Tag Library</alias>
    </topic>
    <topic domain="wwww" TID="jsf" crdate="20040119">
        <derived-from template="serversidetechnology"/>
        <name>JSF</name>
        <alias>JavaServer Faces</alias>
    </topic>
    <topic domain="wwww" TID="jsp" crdate="20000612">
        <derived-from template="serversidetechnology"/>
        <name>JSP</name>
        <alias>Java Server Pages</alias>
        <desc><topicref TID="sun"/>'s <topicref TID="jsp"/> technology uses <topicref TID="xml"/>-like tags and scriptlets written in <topicref TID="java"/> to encapsulate the logic that generates the content for a <topicref TID="html"/> or <topicref TID="xml"/> page. Additionally, the application logic can reside in server-based resources that the page accesses with these tags and scriptlets. Any and all formatting tags (<topicref TID="html"/> or <topicref TID="xml"/>) are passed directly back to the response page. This separates the page logic from its design and display, and thereby supports a reusable component-based design. <topicref TID="jsp"/> is an extension of the <topicref TID="java"/> <topicref TID="servlet"/> <topicref TID="api"/>. <topicref TID="jsp"/> is <topicref TID="sun"/>'s proprietary technology to compete with <topicref TID="microsoft"/>'s <topicref TID="asp"/>.</desc>
    </topic>
    <topic domain="wwww" TID="jvm" modate="20020722" crdate="20000619">
        <derived-from template="technology"/>
        <name>JVM</name>
        <alias>Java Virtual Machine</alias>
        <desc>The <topicref TID="jvm"/> is the "processor architecture" on which <topicref TID="java"/> bytecode (a compiled <topicref TID="java"/> program) is executed. In contrast to other processor architectures, <topicref TID="jvm"/> is mostly implemented in software, and available for a large variety of hardware platforms, ranging from mainframe computers to mobile phones and small embedded devices.</desc>
    </topic>
    <topic domain="wwww" TID="java" crdate="20000612">
        <derived-from template="programminglanguage"/>
        <name>Java</name>
        <desc><topicref TID="java"/> is a general-purpose object-oriented <topicref TID="programminglanguage"/>. <topicref TID="java"/> is interesting in the context of the <topicref TID="www"/> because it is compiled into <topicref TID="java"/> "bytecode", which is executed on a <topicref TID="jvm"/>. This design makes <topicref TID="java"/> programs platform-independent, and <topicref TID="java"/> <topicref TID="applet"/>s, a special form of <topicref TID="java"/> programs, can be integrated into <topicref TID="www"/> documents. Most <topicref TID="browser"/>s today contain a <topicref TID="jvm"/> and a run-time environment for <topicref TID="applet"/>s.</desc>
    </topic>
    <topic domain="wwww" TID="v32" crdate="20010315">
        <derived-from template="modprotocol"/>
        <name>V.32</name>
    </topic>
    <topic domain="wwww" TID="v34" crdate="20010315">
        <derived-from template="modprotocol"/>
        <name>V.34</name>
    </topic>
    <topic domain="wwww" TID="v90" crdate="20010315">
        <derived-from template="modprotocol"/>
        <name>V.90</name>
    </topic>
    <topic domain="wwww" TID="sml" crdate="20040218">
        <derived-from template="programminglanguage"/>
        <name>SML</name>
        <alias>Standard ML</alias>
    </topic>
    <topic domain="wwww" TID="haskell" crdate="20020716">
        <derived-from template="programminglanguage"/>
        <name>Haskell</name>
    </topic>
    <topic domain="wwww" TID="scheme" crdate="20020903">
        <derived-from template="programminglanguage"/>
        <name>Scheme</name>
    </topic>
    <topic domain="wwww" TID="lisp" crdate="20010220">
        <derived-from template="programminglanguage"/>
        <name>Lisp</name>
        <alias>List Processor</alias>
    </topic>
    <topic domain="wwww" TID="c" crdate="20010220">
        <derived-from template="programminglanguage"/>
        <name>C</name>
    </topic>
    <topic domain="wwww" TID="eiffel" crdate="20010904">
        <derived-from template="programminglanguage"/>
        <name>Eiffel</name>
    </topic>
    <topic domain="wwww" TID="csharp" crdate="20031203">
        <derived-from template="programminglanguage"/>
        <name>C#</name>
    </topic>
    <topic domain="wwww" TID="cplusplus" crdate="20010220">
        <derived-from template="programminglanguage"/>
        <name>C++</name>
    </topic>
    <topic domain="wwww" TID="midlet" crdate="20040720">
        <derived-from template="clientsidetechnology"/>
        <name>MIDlet</name>
        <desc>A <topicref TID="midlet"/> is a <topicref TID="midp"/> application. Like an <topicref TID="applet"/>, a <topicref TID="midlet"/> is a managed application. Instead of being managed by a <topicref TID="browser"/>, however, it is managed by special-purpose application-management software built into the device, often a cell phone or a two-way interactive pager. External management of the application makes sense in this context because it may be interrupted at any point by outside events. It would be poor behavior, for example, for a running application to prevent the user from answering incoming phone calls.</desc>
    </topic>
    <topic domain="wwww" TID="midp" crdate="20040720">
        <derived-from template="clientsidetechnology"/>
        <name>MIDP</name>
        <alias>Mobile Information Device Profile</alias>
    </topic>
    <topic domain="wwww" TID="applet" crdate="20000612">
        <derived-from template="clientsidetechnology"/>
        <name>applet</name>
        <desc>An <topicref TID="applet"/> is a special type of <topicref TID="java"/> program that can be included in an <topicref TID="html"/> page, much as an image can be included. When using a <topicref TID="java"/>-compatible <topicref TID="browser"/> to view a page that contains an <topicref TID="applet"/>, the <topicref TID="applet"/>'s code is transferred to and executed by the <topicref TID="browser"/>. Since an <topicref TID="applet"/> is platform-independent, the same <topicref TID="applet"/> can be executed on all types of platforms, as long as they support <topicref TID="java"/>.</desc>
    </topic>
    <topic domain="wwww" TID="servlet" crdate="20000612">
        <derived-from template="serversidetechnology"/>
        <name>servlet</name>
    </topic>
    <topic domain="wwww" TID="wll" crdate="20000626">
        <derived-from template="wlinterface"/>
        <name>WLL</name>
        <alias>Wireless Local Loop</alias>
    </topic>
    <topic domain="wwww" TID="wap" crdate="20060525">
        <derived-from template="hmsystem"/>
        <name>WAP</name>
        <alias>Wireless Application Protocol</alias>
        <desc>The idea of the "Mobile Web", a way to access the <topicref TID="www"/> from mobile devices, appeared when the first data services for mobile phones (such as <topicref TID="gprs"/>) became available. <topicref TID="wap"/> was designed as the set of standards to reach that goal.</desc>
        <status><topicref TID="wap1"/> failed because it was based on non-<topicref TID="www"/> standards. <topicref TID="wap2"/> is based on <topicref TID="www"/> and <topicref TID="internet"/> standards and thus more likely to succeed.</status>
    </topic>
    <topic domain="wwww" TID="wap2" crdate="20060525">
        <derived-from template="wap"/>
        <name>WAP2</name>
        <alias>Wireless Application Protocol 2</alias>
    </topic>
    <topic domain="wwww" TID="wap1" crdate="20000612" modate="20060525">
        <derived-from template="wap"/>
        <name>WAP1</name>
        <alias>Wireless Application Protocol 1</alias>
        <desc><topicref TID="wap1"/> enables mobile users with wireless devices to easily access and interact with information services. <topicref TID="wap1"/> is not a single standard for data communications or document formats, but a whole suite of specifications ranging from data transport <topicref TID="protocol"/>s to the <topicref TID="wml"/>, which is a markup language similar to <topicref TID="html"/>, but based on <topicref TID="xml"/> and specifically designed for wireless devices. There are five layers to the <topicref TID="wap1"/> stack: the application layer (<topicref TID="wae"/>), the session layer (<topicref TID="wsp"/>), the transaction layer (<topicref TID="wtp"/>), the security layer (<topicref TID="wtls"/>), and the transport layer (<topicref TID="wdp"/>).</desc>
    </topic>
    <topic domain="wwww" TID="wae" crdate="20020628" modate="20060525">
        <derived-from template="framework"/>
        <name>WAE</name>
        <alias>Wireless Application Environment</alias>
        <desc><topicref TID="wae"/> is the uppermost layer in the <topicref TID="wap1"/> software stack, this layer provides basic components on which <topicref TID="asp2"/>s can develop their mobile applications.</desc>
    </topic>
    <topic domain="wwww" TID="wta" crdate="20020628" modate="20060525">
        <derived-from template="framework"/>
        <name>WTA</name>
        <alias>Wireless Telephony Application</alias>
        <desc><topicref TID="wta"/> is a part of <topicref TID="wap1"/>'s <topicref TID="wae"/>. <topicref TID="wta"/> is an application framework for telephony services. <topicref TID="wta"/> provides four services: <topicref TID="wtai"/>, repository, event handling, and <topicref TID="wta"/> service information.</desc>
    </topic>
    <topic domain="wwww" TID="wtai" crdate="20011120">
        <derived-from template="api"/>
        <name>WTAI</name>
        <alias>Wireless Telephony Application Interface</alias>
        <desc><topicref TID="wtai"/> defines a set of <topicref TID="wta"/>-related functions in a wireless device that can be invoked via <topicref TID="wml"/> or <topicref TID="wmlscript"/>.</desc>
    </topic>
    <topic domain="wwww" TID="wsp" crdate="20000614" modate="20060525">
        <derived-from template="protocol"/>
        <name>WSP</name>
        <alias>Wireless Session Protocol</alias>
        <desc><topicref TID="wsp"/> forms the interface between <topicref TID="wae"/> and the rest of the <topicref TID="wap1"/> stack. <topicref TID="wsp"/> operates in two modes, connectionless and connection, supports the transmission of <topicref TID="wml"/>, and can be regarded as the binary equivalent of <topicref TID="http"/>.</desc>
    </topic>
    <topic domain="wwww" TID="smpp" crdate="20071108">
        <derived-from template="protocol"/>
        <name>SMPP</name>
        <alias>Short Message Peer-to-Peer Protocol</alias>
    </topic>
    <topic domain="wwww" TID="wtp" crdate="20000614">
        <derived-from template="protocol"/>
        <name>WTP</name>
        <alias>Wireless Transaction Protocol</alias>
    </topic>
    <topic domain="wwww" TID="codec" crdate="20020709">
        <derived-from template="concept"/>
        <name>Codec</name>
        <alias>Coder/Decoder</alias>
        <desc>A <topicref TID="codec"/> is an entity that is responsible for encoding and decoding some <topicref TID="dataformat"/>. <topicref TID="codec"/>s can be implemented in hardware or software. A typical example is an <topicref TID="mp3"/> <topicref TID="codec"/>, which is responsible for decoding an <topicref TID="mp3"/> audio stream for playback, or encoding it for transmission or storage using the compact <topicref TID="mp3"/> <topicref TID="audiocompression"/>.</desc>
    </topic>
    <topic domain="wwww" TID="modem" crdate="20010315">
        <derived-from template="technology"/>
        <name>Modem</name>
        <alias>Modulation/Demodulation</alias>
        <desc>A <topicref TID="modem"/> converts digital signals into analog signals which can be transmitted over an analog line (in many cases a <topicref TID="pstn"/> connection), and transforms incoming analog signals into their digital equivalents. The specific technique used to encode the digital bits into analog signals is called "<topicref TID="modprotocol"/>", which defines the exact method of encoding and the data transfer speed. A <topicref TID="modem"/> typically supports more than one <topicref TID="modprotocol"/>.</desc>
    </topic>
    <topic domain="wwww" TID="pstn" crdate="20010315">
        <derived-from template="wan"/>
        <name>PSTN</name>
        <alias>Public Switched Telephone Network</alias>
        <desc><topicref TID="pstn"/> refers to the established international telephone system carrying voice data over circuit switched connections. Newer developments such as <topicref TID="isdn"/> are completely digital, while <topicref TID="pstn"/> traditionally works on an analog basis (even though <topicref TID="pstn"/>-based networks also increasingly are implemented using digital technologies).</desc>
    </topic>
    <topic domain="wwww" TID="tex" crdate="20010216">
        <derived-from template="textformat"/>
        <name>TeX</name>
        <desc><topicref TID="tex"/> is a typesetting system for high-quality document preparation. <topicref TID="tex"/> itself does not provide a <topicref TID="gui"/> like most word processing programs, but is invoked to process a document which contains commands and the actual content. Because of its superior formatting of mathematical formulae, <topicref TID="tex"/> is very popular in the scientific community. <topicref TID="tex"/> is most often used in the form of <topicref TID="latex"/>, which is a macro package based on <topicref TID="tex"/>. Another popular tool in the context of <topicref TID="tex"/> is <topicref TID="bibtex"/>, a program for processing bibliographic databases.</desc>
    </topic>
    <topic domain="wwww" TID="bibtex" crdate="20010307">
        <derived-from template="bibliographicmetadata"/>
        <name>BibTeX</name>
        <desc><topicref TID="bibtex"/> is a simple but popular <topicref TID="dataformat"/> and program for storing and processing bibliographic references. In almost all cases it is used together with <topicref TID="latex"/>, but it can also be used to create other kinds of output.</desc>
    </topic>
    <topic domain="wwww" TID="marc" crdate="20020529">
        <derived-from template="bibliographicmetadata"/>
        <name>MARC</name>
        <alias>Machine Readable Cataloguing</alias>
    </topic>
    <topic domain="wwww" TID="canmarc" crdate="20020929">
        <derived-from template="bibliographicmetadata"/>
        <name>CANMARC</name>
    </topic>
    <topic domain="wwww" TID="usmarc" crdate="20020929">
        <derived-from template="bibliographicmetadata"/>
        <name>USMARC</name>
    </topic>
    <topic domain="wwww" TID="marc21" crdate="20020929">
        <derived-from template="bibliographicmetadata"/>
        <name>MARC 21</name>
    </topic>
    <topic domain="wwww" TID="unimarc" crdate="20020529">
        <derived-from template="bibliographicmetadata"/>
        <name>UNIMARC</name>
        <alias>Universal MARC</alias>
    </topic>
    <topic domain="wwww" TID="biblioml" crdate="20020529">
        <derived-from template="dataformat"/>
        <name>BiblioML</name>
    </topic>
    <topic domain="wwww" TID="opml" crdate="20040809">
        <derived-from template="dataformat"/>
        <name>OPML</name>
        <alias>Outline Processor Markup Language</alias>
        <desc><topicref TID="opml"/> is a <topicref TID="dataformat"/> that can be used to exchange subscription lists between programs that read <topicref TID="rss"/> files, such as feed readers and aggregators.</desc>
    </topic>
    <topic domain="wwww" TID="texml" crdate="20040809">
        <derived-from template="dataformat"/>
        <name>TeXML</name>
        <alias>TeX Markup Language</alias>
    </topic>
    <topic domain="wwww" TID="bibtexml" crdate="20010307">
        <derived-from template="bibliographicmetadata"/>
        <name>BibTeXML</name>
        <alias>BibTeX Markup Language</alias>
        <desc><topicref TID="bibtexml"/> is an <topicref TID="xml"/> representation for <topicref TID="bibtex"/> data. The advantage of <topicref TID="bibtexml"/> over the standard <topicref TID="bibtex"/> format is the availability of tools for processing <topicref TID="xml"/> data in general, and the ease of integration of <topicref TID="bibtexml"/> into an <topicref TID="xml"/>-based environment.</desc>
    </topic>
    <topic domain="wwww" TID="latex" crdate="20010216">
        <derived-from template="textformat"/>
        <name>LaTeX</name>
        <desc><topicref TID="latex"/> is a macro package based on the <topicref TID="tex"/> typesetting system. <topicref TID="latex"/> provides macros for the most frequently used document concepts, such as sectioning, lists, or tables.</desc>
    </topic>
    <topic domain="wwww" TID="pdflatex" crdate="20010317">
        <derived-from template="latex"/>
        <name>PDFLaTeX</name>
        <desc><topicref TID="pdflatex"/> is a special version of <topicref TID="latex"/> which directly produces <topicref TID="pdf"/> output. Special commands in the <topicref TID="latex"/> source can be used to control special <topicref TID="pdf"/> features, such as cross references or bookmarks.</desc>
    </topic>
    <topic domain="wwww" TID="cttm" crdate="20030205">
        <derived-from template="product"/>
        <name>CTTM</name>
        <alias>Conference Time-Table Management</alias>
    </topic>
    <topic domain="wwww" TID="jserv" crdate="20030219">
        <derived-from template="product"/>
        <name>JServ</name>
    </topic>
    <topic domain="wwww" TID="tomcat" crdate="20000822">
        <derived-from template="product"/>
        <name>Tomcat</name>
    </topic>
    <topic domain="wwww" TID="geronimo" crdate="20060305">
        <derived-from template="product"/>
        <name>Geronimo</name>
    </topic>
    <topic domain="wwww" TID="jboss" crdate="20060305">
        <derived-from template="product"/>
        <name>JBoss</name>
    </topic>
    <topic domain="wwww" TID="jakarta" crdate="20000822">
        <derived-from template="topic"/>
        <name>Jakarta</name>
    </topic>
    <topic domain="wwww" TID="wtls" crdate="20000614" modate="20060525">
        <derived-from template="protocol"/>
        <name>WTLS</name>
        <alias>Wireless Transport Layer Security Protocol</alias>
        <desc><topicref TID="wtls"/> sits between <topicref TID="wtp"/> and <topicref TID="wdp"/> layers in the <topicref TID="wap1"/> stack, and is responsible for providing transport layer security between the <topicref TID="wap1"/> client and <topicref TID="wap1"/> <topicref TID="gateway"/> or <topicref TID="proxy"/>. <topicref TID="wtls"/> is optimized for narrowband communication.</desc>
    </topic>
    <topic domain="wwww" TID="x12" crdate="20010103">
        <derived-from template="topic"/>
        <name>X12</name>
        <alias>ASC X12</alias>
    </topic>
    <topic domain="wwww" TID="xmledi" crdate="20010103">
        <derived-from template="technology"/>
        <name>XML/EDI</name>
    </topic>
    <topic domain="wwww" TID="t9" crdate="20020402">
        <derived-from template="technology"/>
        <name>T9</name>
        <alias>Text on 9 keys</alias>
        <desc><topicref TID="t9"/> is a technology for rapidly typing alphanumeric text on a numeric keypad. It is based on a dictionary and thus language-dependent. <topicref TID="t9"/> is often used on mobile phones to facilitate text input for messaging, for example for composing <topicref TID="sms"/> messages.</desc>
    </topic>
    <topic domain="wwww" TID="crc" crdate="20010105">
        <derived-from template="hash"/>
        <name>CRC</name>
        <alias>Cyclic Redundancy Check</alias>
    </topic>
    <topic domain="wwww" TID="thesaurus" crdate="20010111">
        <derived-from template="concept"/>
        <name>Thesaurus</name>
    </topic>
    <topic domain="wwww" TID="rss" crdate="20060113" modate="20060524">
        <derived-from template="dataformat"/>
        <name>RSS</name>
        <desc><topicref TID="rss"/> is a format for information syndication, enabling the publishing of data which can then be reused in other contexts. <topicref TID="rss"/> sources are often called "feeds", meaning that new information is produced and published regularly and can be obtained from these feeds.</desc>
        <status><topicref TID="rss1"/> and <topicref TID="rss2"/> are competing versions of <topicref TID="rss"/>, and since both versions have been produced by competing authors, it is not possible to say which is one really is the "current" version. This status problem is an important insecurity with <topicref TID="rss"/> and the reason why the newer <topicref TID="atom"/> may replace <topicref TID="rss"/> in the mid term.</status>
    </topic>
    <topic domain="wwww" TID="rss2" crdate="20010108" modate="20060524">
        <derived-from template="rss"/>
        <name>RSS2</name>
        <alias>Really Simple Syndication</alias>
    </topic>
    <topic domain="wwww" TID="rss1" crdate="20010108" modate="20060524">
        <derived-from template="rss"/>
        <name>RSS1</name>
        <alias>RDF Site Summary</alias>
    </topic>
    <topic domain="wwww" TID="sle" crdate="20071207">
        <derived-from template="protocol"/>
        <name>SLE</name>
        <alias>Simple List Extensions</alias>
    </topic>
    <topic domain="wwww" TID="atompub" crdate="20070214">
        <derived-from template="protocol"/>
        <name>AtomPub</name>
        <alias>Atom Publishing Protocol</alias>
    </topic>
    <topic domain="wwww" TID="atom" crdate="20040809" modate="20070214">
        <derived-from template="dataformat"/>
        <name>Atom</name>
        <desc><topicref TID="atom"/> defines a feed <topicref TID="dataformat"/> for representing and a <topicref TID="protocol"/> for editing <topicref TID="www"/> resources such as <topicref TID="blog"/>s, online journals, <topicref TID="wiki"/>s, and similar content. The feed <topicref TID="dataformat"/> enables syndication; that is, provision of a channel of information by representing multiple resources in a single document (similar to <topicref TID="rss"/>). The editing <topicref TID="protocol"/> enables agents to interact with resources by nominating a way of using existing <topicref TID="www"/> standards in a pattern.</desc>
    </topic>
    <topic domain="wwww" TID="blog" crdate="20060305">
        <derived-from template="concept"/>
        <name>Blog</name>
        <alias>Weblog</alias>
        <desc>A <topicref TID="blog"/> is a constantly changing <topicref TID="www"/> site which is updated with news and/or comments. <topicref TID="blog"/> often contain many links to other <topicref TID="www"/> resources and can thus serve as a useful help for locating information about a subject. <topicref TID="blog"/> may have not any focus at all, or they may concentrate around selected areas of personal or professional interest.</desc>
    </topic>
    <topic domain="wwww" TID="wiki" crdate="20060305">
        <derived-from template="concept"/>
        <name>Wiki</name>
        <desc>A <topicref TID="wiki"/> is similar to a <topicref TID="blog"/> in that it is constantly changing and usually contains many links to <topicref TID="www"/> resources. The difference is that <topicref TID="wiki"/>s are maintained as a collaborate effort (of open or closed user groups), and the main idea behind <topicref TID="wiki"/>s is that adding and editing data should be simple and <topicref TID="www"/>-based (usually using <topicref TID="htmlforms"/>).</desc>
    </topic>
    <topic domain="wwww" TID="cam" crdate="20040114">
        <derived-from template="dataformat"/>
        <name>CAM</name>
        <alias>Content Assembly Mechanism</alias>
    </topic>
    <topic domain="wwww" TID="edi" crdate="20010103">
        <derived-from template="technology"/>
        <name>EDI</name>
        <alias>Electronic Data Interchange</alias>
        <desc><topicref TID="edi"/> is the computer-to-computer exchange of business data in standard formats. In <topicref TID="edi"/>, information is organized according to a specified format set by both parties, allowing an automated computer transaction that requires no human intervention or rekeying on either end. The information contained in an <topicref TID="edi"/> transaction set is, for the most part, the same as on a conventionally printed document. <topicref TID="edi"/> standards in the US are set and published by the ASC X12 committee of <topicref TID="ansi"/>. International EDI standards are known as <topicref TID="edifact"/> standards.</desc>
    </topic>
    <topic domain="wwww" TID="edifact" crdate="20010103">
        <derived-from template="technology"/>
        <name>EDIFACT</name>
        <alias>Electronic Data Interchange for Administration, Commerce, and Transport</alias>
    </topic>
    <topic domain="wwww" TID="wdp" crdate="20000614">
        <derived-from template="protocol"/>
        <name>WDP</name>
        <alias>Wireless Datagram Protocol</alias>
    </topic>
    <topic domain="wwww" TID="hytime" crdate="20000612">
        <derived-from template="hypermediaformat"/>
        <name>HyTime</name>
        <alias>Hypermedia/Time-based Structuring Language</alias>
    </topic>
    <topic domain="wwww" TID="tei" crdate="20000612">
        <derived-from template="topic"/>
        <name>TEI</name>
        <alias>Text Encoding Initiative</alias>
    </topic>
    <topic domain="wwww" TID="wml" crdate="20000612" modate="20060525">
        <derived-from template="hypertextformat"/>
        <name>WML</name>
        <alias>Wireless Markup Language</alias>
        <desc><topicref TID="wml"/> is the <topicref TID="hypertextformat"/> for <topicref TID="wap1"/>. <topicref TID="wml"/> is based on <topicref TID="xml"/> (it is formally defined by an <topicref TID="xml"/> <topicref TID="dtd"/>). <topicref TID="wml"/> pages can be stored on any <topicref TID="httpserver"/>, which will be contacted by a <topicref TID="wap1"/> <topicref TID="gateway"/> and deliver the <topicref TID="wml"/> page. The <topicref TID="wap1"/> <topicref TID="gateway"/> then transforms the <topicref TID="wml"/> page into <topicref TID="wbxml"/>, which is then transmitted to the <topicref TID="wap1"/> device. <topicref TID="wml"/> is similar to <topicref TID="html"/> in its design, and <topicref TID="wap1"/> also defines <topicref TID="wmlscript"/> which may be used to implement dynamic <topicref TID="wml"/>.</desc>
    </topic>
    <topic domain="wwww" TID="xtalk" crdate="20040714">
        <derived-from template="dataformat"/>
        <name>XTalk</name>
        <desc><topicref TID="xtalk"/> is a pseudo-binary <topicref TID="xml"/> format intended to make the <topicref TID="xml"/> parsing task even more simple than what was originally envisioned by the <topicref TID="xml"/> creators. It is not, however, intended to be a replacement for general <topicref TID="xml"/> documents. <topicref TID="xtalk"/> is best used as an intermediate <topicref TID="xml"/> representation exchanged by high-performance, distributed services that run on anything and everything from the hand-held to the mainframe. The representation may also be suitable for storage in <topicref TID="xdbms"/>s.</desc>
    </topic>
    <topic domain="wwww" TID="wbxml" crdate="20000616" modate="20060525">
        <derived-from template="hypertextformat"/>
        <name>WBXML</name>
        <alias>Wireless Binary XML</alias>
        <desc><topicref TID="wbxml"/> is a binary format for <topicref TID="wml"/>, the <topicref TID="hypertextformat"/> of <topicref TID="wap1"/>. <topicref TID="wbxml"/> may either be delivered by the origin server itself, or the origin server delivers <topicref TID="wml"/>, and the <topicref TID="wap1"/> <topicref TID="gateway"/> performs the transformation between <topicref TID="wml"/> and <topicref TID="wbxml"/>. <topicref TID="wbxml"/> works by defining a tokenization method for <topicref TID="wml"/>, where each element and each attribute is represented by a compact binary token.</desc>
    </topic>
    <topic domain="wwww" TID="exi" crdate="20061201">
        <derived-from template="concept"/>
        <name>EXI</name>
        <alias>Efficient XML Interchange</alias>
    </topic>
    <topic domain="wwww" TID="xbc" crdate="20061201">
        <derived-from template="concept"/>
        <name>XBC</name>
        <alias>XML Binary Characterization</alias>
    </topic>
    <topic domain="wwww" TID="idf" crdate="20040326">
        <derived-from template="organization"/>
        <name>IDF</name>
        <alias>International DOI Foundation</alias>
    </topic>
    <topic domain="wwww" TID="acm" crdate="20040326">
        <derived-from template="organization"/>
        <name>ACM</name>
        <alias>Association for Computing Machinery</alias>
    </topic>
    <topic domain="wwww" TID="ieee" crdate="20000831">
        <derived-from template="organization"/>
        <name>IEEE</name>
        <alias>Institute of Electrical and Electronics Engineers</alias>
    </topic>
    <topic domain="wwww" TID="gnu" crdate="20021122">
        <derived-from template="topic"/>
        <name>GNU</name>
        <alias>GNU's Not Unix!</alias>
    </topic>
    <topic domain="wwww" TID="fsf" crdate="20021122">
        <derived-from template="organization"/>
        <name>FSF</name>
        <alias>Free Software Foundation</alias>
    </topic>
    <topic domain="wwww" TID="iec" crdate="20000621">
        <derived-from template="organization"/>
        <name>IEC</name>
        <alias>International Electrotechnical Commission</alias>
    </topic>
    <topic domain="wwww" TID="niso" crdate="20000711">
        <derived-from template="nationalorganization"/>
        <name>NISO</name>
        <alias>National Information Standards Organization</alias>
    </topic>
    <topic domain="wwww" TID="ipa" crdate="20010313">
        <derived-from template="internationalorganization"/>
        <name>IPA</name>
        <alias>International Phonetic Association</alias>
    </topic>
    <topic domain="wwww" TID="iso" crdate="20000612">
        <derived-from template="internationalorganization"/>
        <name>ISO</name>
        <alias>International Organization for Standardization</alias>
    </topic>
    <topic domain="wwww" TID="osi" crdate="20000612">
        <derived-from template="technology"/>
        <name>OSI</name>
        <alias>Open Systems Interconnection</alias>
        <desc><topicref TID="osi"/> is a reference model for computer communications. It was created as a competitor of the <topicref TID="internet"/> <topicref TID="protocol"/>s. While <topicref TID="osi"/> as a whole has not been very successful, parts of it are widely used, and many concepts pioneered in <topicref TID="osi"/> are slowly finding their way into <topicref TID="internet"/> technologies. <topicref TID="osi"/> is defined in terms of different "layers". <topicref TID="osi"/>-based applications belong to the "application layer" (layer 7) of the <topicref TID="osi"/> "Basic Reference Model". The application layer resides above the "presentation layer" (layer 6), which identifies alternative encodings, and the "session layer" (layer 5), providing dialogue control. Collectively, these three layers provide application services, and are commonly referred to as the "upper layers". The "lower layers" of the <topicref TID="osi"/> stack are "transport" (layer 4), "network" (layer 3), "link" (layer 2) and "physical" (layer 1).</desc>
    </topic>
    <topic domain="wwww" TID="kerberos" crdate="20000912">
        <derived-from template="technology"/>
        <name>Kerberos</name>
    </topic>
    <topic domain="wwww" TID="asn1" crdate="20000612">
        <derived-from template="dataformat"/>
        <name>ASN.1</name>
        <alias>Abstract Syntax Notation One</alias>
        <desc><topicref TID="asn1"/> defines a method for the specification and encoding of arbitrary data structures. <topicref TID="asn1"/> is part of the <topicref TID="osi"/> model of protocol layers, it is located within the "presentation layer" (layer 6). The approach of <topicref TID="asn1"/> is to define an abstract syntax for the specification of structured data, and encoding rules for transforming structured data into a binary representation (which can then be exchanged). <topicref TID="ber"/> is the oldest encoding for <topicref TID="asn1"/>, and a subset of it (known as <topicref TID="der"/>) is used for <topicref TID="x509"/> <topicref TID="certificate"/>s.</desc>
    </topic>
    <topic domain="wwww" TID="cdf" crdate="20000719">
        <derived-from template="dataformat"/>
        <name>CDF</name>
        <alias>Channel Definition Format</alias>
        <status><topicref TID="cdf"/> is not used in practice anymore, and has been replaced by <topicref TID="rss"/>, which has been designed for the same application area.</status>
    </topic>
    <topic domain="wwww" TID="lorel" crdate="20020810">
        <derived-from template="querylanguage"/>
        <name>Lorel</name>
    </topic>
    <topic domain="wwww" TID="websql" crdate="20020810">
        <derived-from template="querylanguage"/>
        <name>WebSQL</name>
    </topic>
    <topic domain="wwww" TID="quilt" crdate="20020810">
        <derived-from template="querylanguage"/>
        <name>Quilt</name>
        <status><topicref TID="quilt"/> has been presented as a proposal to the <topicref TID="w3c"/> XML Query Working Group, and that group has adopted <topicref TID="quilt"/> as the basis for development of a new language called <topicref TID="xquery"/>. Development work is now focused on <topicref TID="xquery"/> rather than on <topicref TID="quilt"/>.</status>
    </topic>
    <topic domain="wwww" TID="xqueryx" crdate="20021217">
        <derived-from template="dataformat"/>
        <name>XQueryX</name>
        <alias>XQuery XML Syntax</alias>
    </topic>
    <topic domain="wwww" TID="xqueryp" crdate="20061206">
        <derived-from template="programminglanguage"/>
        <name>XQueryP</name>
    </topic>
    <topic domain="wwww" TID="xquery" crdate="20001206">
        <derived-from template="querylanguage"/>
        <name>XQuery</name>
        <alias>XML Query</alias>
    </topic>
    <topic domain="wwww" TID="xsl" crdate="20000607" modate="20060629">
        <derived-from template="stylesheetlanguage"/>
        <name>XSL</name>
        <alias>Extensible Style Language</alias>
        <desc><topicref TID="xsl"/> is a <topicref TID="stylesheetlanguage"/> that can be used for displaying <topicref TID="xml"/> documents. Using <topicref TID="xsl"/> is two-step process, the first step being a transformation of the <topicref TID="xml"/> document using <topicref TID="xslt1"/>, and the second step being the rendering of the result of the transformation, which is done using <topicref TID="xslfo"/>. While <topicref TID="xsl"/> covers the same application area than <topicref TID="css"/>, it is much more powerful, because the transformation step (using <topicref TID="xslt1"/>) can perform arbitrarily complex transformations of the <topicref TID="xml"/> document, while <topicref TID="css"/> is not able to make any structural changes to the <topicref TID="xml"/> document.</desc>
    </topic>
    <topic domain="wwww" TID="ssl" crdate="20000607">
        <derived-from template="protocol"/>
        <name>SSL</name>
        <alias>Secure Sockets Layer</alias>
        <desc>The primary goal of <topicref TID="ssl"/> is to provide privacy and reliability between two communicating applications. <topicref TID="ssl"/> is composed of two layers. At the lower level, layered on top of some reliable transport <topicref TID="protocol"/>, for example <topicref TID="tcp"/>, is the <topicref TID="ssl"/> Record Protocol, which is used for encapsulation of various higher level protocols. One such encapsulated protocol, the <topicref TID="ssl"/> Handshake Protocol, allows the server and client to authenticate each other and to negotiate an <topicref TID="encryption"/> <topicref TID="algorithm"/> and cryptographic keys before the application protocol transmits or receives its first byte of data. One advantage of <topicref TID="ssl"/> is that it is application <topicref TID="protocol"/> independent. A higher level <topicref TID="protocol"/> can layer on top of <topicref TID="ssl"/> transparently. For <topicref TID="internet"/> applications, a generalized variant of <topicref TID="ssl"/> called <topicref TID="tls"/> has been developed.</desc>
    </topic>
    <topic domain="wwww" TID="telnet" crdate="20010309">
        <derived-from template="protocol"/>
        <name>Telnet</name>
        <desc>The purpose of the <topicref TID="telnet"/> <topicref TID="protocol"/> is to provide a fairly general, bi-directional, 8-bit byte oriented communications facility. Its primary goal is to allow a standard method of interfacing terminal devices and terminal-oriented processes to each other. The most popular usage of <topicref TID="telnet"/> is for logging in into remote systems. In this scenario, the <topicref TID="telnet"/> <topicref TID="client"/> is the remote terminal (usually running some kind of terminal emulation) which is connected to a terminal driver program using the <topicref TID="telnet"/> <topicref TID="protocol"/>.</desc>
    </topic>
    <topic domain="wwww" TID="tls" crdate="20000607">
        <derived-from template="protocol"/>
        <name>TLS</name>
        <alias>Transport Layer Security</alias>
        <desc><topicref TID="tls"/> was developed as the successor to <topicref TID="ssl"/>, and is nearly identical to <topicref TID="ssl"/>, except that it implements an open and standards-based solution, more non-proprietary ciphers, better error reporting, and <topicref TID="hmac"/> digests instead of simple <topicref TID="md5"/>. The structure of the start of a <topicref TID="tls"/> session allows negotiation of the level of the protocol to be used. This way, a <topicref TID="client"/> or <topicref TID="server"/> can simultaneously support <topicref TID="tls"/> and <topicref TID="ssl"/> and negotiate the most appropriate protocol for the connection.</desc>
    </topic>
    <topic domain="wwww" TID="dtd" crdate="20000608">
        <derived-from template="xmlschemalanguage"/>
        <name>DTD</name>
        <alias>Document Type Definition</alias>
        <desc>A <topicref TID="dtd"/> is one component inside an <topicref TID="sgml"/> or <topicref TID="xml"/> environment. It defines the syntactic rules according to which a document can be composed. There are no semantics associated with the elements and attributes defined in a <topicref TID="dtd"/>, although normally the names chosen for elements and attributes will have some meaning to them. Using a <topicref TID="dtd"/> and an <topicref TID="xmlprocessor"/>, a document can be validated against the <topicref TID="dtd"/>, which means it can be tested whether it conforms to a given <topicref TID="dtd"/>. <topicref TID="html"/> is one example of an <topicref TID="sgml"/> <topicref TID="dtd"/> (which has been reformulated as an <topicref TID="xml"/> <topicref TID="dtd"/> in <topicref TID="xhtml"/>).</desc>
    </topic>
    <topic domain="wwww" TID="dtdminusminus" crdate="20051212">
        <derived-from template="xmlschemalanguage"/>
        <name>DTD--</name>
    </topic>
    <topic domain="wwww" TID="dtdplusplus" crdate="20050519">
        <derived-from template="xmlschemalanguage"/>
        <name>DTD++</name>
    </topic>
    <topic domain="core" TID="cisco" crdate="20011123">
        <derived-from template="company"/>
        <name>Cisco Systems</name>
    </topic>
    <topic domain="core" TID="qualcomm" crdate="20061120">
        <derived-from template="company"/>
        <name>QUALCOMM</name>
    </topic>
    <topic domain="core" TID="sun" crdate="20000612">
        <derived-from template="company"/>
        <name>Sun Microsystems</name>
    </topic>
    <topic domain="wwww" TID="nist" crdate="20000705">
        <derived-from template="nationalorganization"/>
        <name>NIST</name>
        <alias>National Institute of Standards and Technology</alias>
    </topic>
    <topic domain="wwww" TID="nbs" crdate="20000705">
        <derived-from template="nationalorganization"/>
        <name>NBS</name>
        <alias>National Bureau of Standards</alias>
    </topic>
    <topic domain="core" TID="adobe" crdate="20000615">
        <derived-from template="company"/>
        <name>Adobe</name>
    </topic>
    <topic domain="core" TID="apple" crdate="20001213">
        <derived-from template="company"/>
        <name>Apple</name>
    </topic>
    <topic domain="core" TID="philips" crdate="20010305">
        <derived-from template="company"/>
        <name>Philips</name>
    </topic>
    <topic domain="core" TID="sony" crdate="20000817">
        <derived-from template="company"/>
        <name>Sony</name>
    </topic>
    <topic domain="core" TID="mirabilis" crdate="20000822">
        <derived-from template="company"/>
        <name>Mirabilis</name>
    </topic>
    <topic domain="wwww" TID="pip" crdate="20010815">
        <derived-from template="protocol"/>
        <name>PIP</name>
        <alias>Presence Information Protocol</alias>
        <desc><topicref TID="pip"/> enables the exchange of document based virtual presence information. Virtual presence information is the foundation for virtual neighborhood services which provide users with information about virtual neighbors, ie other users who are close within the virtual document space established by the <topicref TID="www"/>. <topicref TID="pip"/> also allows the exchange of simple text-based messages.</desc>
    </topic>
    <topic domain="wwww" TID="pct" crdate="20010815">
        <derived-from template="protocol"/>
        <name>PCT</name>
        <alias>Private Communication Technology</alias>
        <desc><topicref TID="pct"/> was designed by <topicref TID="microsoft"/> in an attempt to improve <topicref TID="netscape"/>'s <topicref TID="ssl"/> protocol. However, development of <topicref TID="pct"/> stopped when <topicref TID="ssl"/> was generalized as <topicref TID="ietf"/>'s <topicref TID="tls"/> protocol.</desc>
    </topic>
    <topic domain="wwww" TID="uucp" crdate="20000912">
        <derived-from template="protocol"/>
        <name>UUCP</name>
        <alias>Unix to Unix Copy</alias>
    </topic>
    <topic domain="core" TID="aol" crdate="20000822">
        <derived-from template="company"/>
        <name>AOL</name>
        <alias>Amercia Online</alias>
    </topic>
    <topic domain="core" TID="yahoo" crdate="20081209">
        <derived-from template="company"/>
        <name>Yahoo!</name>
    </topic>
    <topic domain="core" TID="novell" crdate="20000911">
        <derived-from template="company"/>
        <name>Novell</name>
    </topic>
    <topic domain="wwww" TID="cgmopen" crdate="20000920">
        <derived-from template="consortium"/>
        <name>CGM Open</name>
    </topic>
    <topic domain="core" TID="xerox" crdate="20000920">
        <derived-from template="company"/>
        <name>Xerox</name>
    </topic>
    <topic domain="core" TID="panasonic" crdate="20040112">
        <derived-from template="company"/>
        <name>Panasonic</name>
    </topic>
    <topic domain="core" TID="oracle" crdate="20001130">
        <derived-from template="company"/>
        <name>Oracle</name>
    </topic>
    <topic domain="core" TID="softwareag" crdate="20001213">
        <derived-from template="company"/>
        <name>Software AG</name>
    </topic>
    <topic domain="wwww" TID="lamp" crdate="20030206">
        <derived-from template="concept"/>
        <name>LAMP</name>
        <alias>Linux/Apache/MySQL/PHP</alias>
        <desc><topicref TID="lamp"/> is a concept (or a philosophy) describing an open-source <topicref TID="www"/> development platform. <topicref TID="lamp"/> is fully based on open-source components, using <topicref TID="linux"/> as its <topicref TID="os"/>, the <topicref TID="apachehttp"/> as its <topicref TID="httpserver"/>, <topicref TID="mysql"/> as its <topicref TID="rdbms"/>, and <topicref TID="php"/> as its <topicref TID="serversidetechnology"/>. Sometimes, the 'P' in <topicref TID="lamp"/> is interpreted as meaning <topicref TID="python"/> or <topicref TID="perl"/>, but in most cases it refers to <topicref TID="php"/>.</desc>
    </topic>
    <topic domain="wwww" TID="i3a" crdate="20020805">
        <derived-from template="organization"/>
        <name>I3A</name>
        <alias>International Imaging Industry Association</alias>
    </topic>
    <topic domain="wwww" TID="dig" crdate="20020805">
        <derived-from template="organization"/>
        <name>DIG</name>
        <alias>Digital Imaging Group</alias>
        <status>On <text date="20010701"/>, <topicref TID="pima"/> and <topicref TID="dig"/> merged to form <topicref TID="i3a"/>.</status>
    </topic>
    <topic domain="wwww" TID="pima" crdate="20001213">
        <derived-from template="organization"/>
        <name>PIMA</name>
        <alias>Photographic and Imaging Manufacturers Association</alias>
        <status>On <text date="20010701"/>, <topicref TID="pima"/> and <topicref TID="dig"/> merged to form <topicref TID="i3a"/>.</status>
    </topic>
    <topic domain="core" TID="bea" crdate="20040620">
        <derived-from template="company"/>
        <name>BEA Systems</name>
    </topic>
    <topic domain="core" TID="microsoft" crdate="20000608">
        <derived-from template="company"/>
        <name>Microsoft</name>
    </topic>
    <topic domain="core" TID="tibco" crdate="20001208">
        <derived-from template="company"/>
        <name>TIBCO</name>
    </topic>
    <topic domain="core" TID="extensibility" crdate="20001208">
        <derived-from template="company"/>
        <name>Extensibility</name>
    </topic>
    <topic domain="core" TID="icon" crdate="20001208">
        <derived-from template="company"/>
        <name>Icon</name>
    </topic>
    <topic domain="core" TID="altova" crdate="20001208">
        <derived-from template="company"/>
        <name>Altova</name>
    </topic>
    <topic domain="core" TID="xmlspy" crdate="20001208">
        <derived-from template="product"/>
        <name>XML Spy</name>
    </topic>
    <topic domain="core" TID="xmlauthority" crdate="20001208">
        <derived-from template="product"/>
        <name>XML Authority</name>
    </topic>
    <topic domain="core" TID="xmlinstance" crdate="20001208">
        <derived-from template="product"/>
        <name>XML Instance</name>
    </topic>
    <topic domain="core" TID="motorola" crdate="20000711">
        <derived-from template="company"/>
        <name>Motorola</name>
    </topic>
    <topic domain="wwww" TID="hytm" crdate="20020830">
        <derived-from template="dataformat"/>
        <name>HyTM</name>
    </topic>
    <topic domain="wwww" TID="ltm" crdate="20020830">
        <derived-from template="dataformat"/>
        <name>LTM</name>
        <alias>Linear Topic Map Notation</alias>
    </topic>
    <topic domain="wwww" TID="tmql" crdate="20040103">
        <derived-from template="querylanguage"/>
        <name>TMQL</name>
        <alias>Topic Map Query Language</alias>
    </topic>
    <topic domain="wwww" TID="tmcl" crdate="20040103">
        <derived-from template="ddl"/>
        <name>TMCL</name>
        <alias>Topic Map Constraint Language</alias>
    </topic>
    <topic domain="wwww" TID="sam" crdate="20040119">
        <derived-from template="ddl"/>
        <name>SAM</name>
        <alias>Standard Application Model</alias>
    </topic>
    <topic domain="wwww" TID="tmapi" crdate="20041021">
        <derived-from template="api"/>
        <name>TMAPI</name>
        <alias>Topic Map Application Programming Interface</alias>
    </topic>
    <topic domain="wwww" TID="tmdm" crdate="20040119">
        <derived-from template="ddl"/>
        <name>TMDM</name>
        <alias>Topic Map Data Model</alias>
    </topic>
    <topic domain="wwww" TID="xtm" crdate="20010603">
        <derived-from template="dataformat"/>
        <name>XTM</name>
        <alias>XML Topic Maps</alias>
    </topic>
    <topic domain="wwww" TID="topicmaps" crdate="20000711">
        <derived-from template="metadata"/>
        <name>Topic Maps</name>
        <desc><topicref TID="topicmaps"/> enable vast information resources (such as the <topicref TID="www"/>) to be classified and navigated in a consistent manner. They allow for the concepts or topics that underlie a set of information resources to be exposed to those people or applications processing the information. Information resources can be <topicref TID="html"/>, <topicref TID="pdf"/>, <topicref TID="xml"/>, <topicref TID="sgml"/> and other <topicref TID="dataformat"/>s including paper. Topics are the concepts underlying what these resources are concerned with. A topic can reference zero or more information resources. In addition to grouping resources as "topic occurrences", it is possible to have meta level associations. This means that it is possible to define a link, or association, from one topic to another. <topicref TID="topicmaps"/> provide a semantic layer that is not hierarchical, although it could be visualized that way, it facilitates navigation at a level independent from the information resources.</desc>
    </topic>
    <topic domain="core" TID="ibm" crdate="20000614">
        <derived-from template="company"/>
        <name>IBM</name>
        <alias>International Business Machines</alias>
    </topic>
    <topic domain="core" TID="mosaic" crdate="20000728">
        <derived-from template="company"/>
        <name>Mosaic Communications</name>
    </topic>
    <topic domain="core" TID="netscape" crdate="20000608">
        <derived-from template="company"/>
        <name>Netscape Communications</name>
    </topic>
    <topic domain="core" TID="operasoftware" crdate="20000608">
        <derived-from template="company"/>
        <name>Opera Software</name>
    </topic>
    <topic domain="wwww" TID="apacheaxis" crdate="20051127">
        <derived-from template="product"/>
        <name>Axis</name>
    </topic>
    <topic domain="wwww" TID="apachehttp" crdate="20000630">
        <derived-from template="product"/>
        <name>Apache HTTP Server</name>
    </topic>
    <topic domain="wwww" TID="jigsaw" crdate="20000728">
        <derived-from template="product"/>
        <name>Jigsaw</name>
    </topic>
    <topic domain="wwww" TID="axis" crdate="20051127">
        <derived-from template="topic"/>
        <name>AXIS</name>
        <alias>A XML Schema Integration System</alias>
    </topic>
    <topic domain="wwww" TID="scout" crdate="20060305">
        <derived-from template="product"/>
        <name>Scout</name>
    </topic>
    <topic domain="core" TID="iis" crdate="20000719">
        <derived-from template="product"/>
        <name>IIS</name>
        <alias>Internet Information Server</alias>
    </topic>
    <topic domain="wwww" TID="apachesoftware" crdate="20000608">
        <derived-from template="topic"/>
        <name>Apache Software Foundation</name>
        <desc>The <topicref TID="apachesoftware"/> is a collaborative software development effort aimed at creating a robust, commercial-grade, feature-full, and freely-available source code implementation of an <topicref TID="httpserver"/>. The project is jointly managed by a group of volunteers located around the world, using the <topicref TID="internet"/> and the <topicref TID="www"/> to communicate, plan, and develop the <topicref TID="server"/> and its related documentation. In addition, hundreds of users have contributed ideas, code, and documentation to the project. In addition to the well-known and established <topicref TID="apachehttp"/>, the <topicref TID="cocoon"/> project aims at developing a next-generation <topicref TID="httpserver"/> integrating <topicref TID="xml"/> technologies.</desc>
    </topic>
    <topic domain="wwww" TID="webcgm" crdate="20000621">
        <derived-from template="graphicsformat"/>
        <name>WebCGM</name>
        <desc><topicref TID="webcgm"/> is a profile of the <topicref TID="iso"/> <topicref TID="cgm"/> standard, tailored to the requirements for scalable 2D vector graphics in electronic documents on the <topicref TID="www"/>. The <topicref TID="webcgm"/> profile is a subset of the <topicref TID="cgm"/> standard, and a set of specifications targeted especially at the effective application of the <topicref TID="cgm"/> standard to representation of 2D graphical content within <topicref TID="www"/> documents.</desc>
    </topic>
    <topic domain="wwww" TID="cgm" crdate="20000608">
        <derived-from template="graphicsformat"/>
        <name>CGM</name>
        <alias>Computer Graphics Metafile</alias>
        <desc><topicref TID="cgm"/> is a machine and <topicref TID="os"/> independent interchange format that provides elements to represent geometric graphics (e.g., polygons or circles) and raster graphics (e.g., pixel arrays). It consists of a functional specification and multiple encodings for different purposes. There are three standardized encodings for <topicref TID="cgm"/>, clear-text, character and binary. Clear-text is human-readable. Character encoding is more compact, but still uses <topicref TID="ascii"/> characters, so that it can be interchanged without <topicref TID="protocol"/> problems. The binary encoding is more compact still, and quick to encode and decode, but completely unreadable.</desc>
    </topic>
    <topic domain="wwww" TID="wmf" crdate="20050127">
        <derived-from template="graphicsformat"/>
        <name>WMF</name>
        <alias>Windows Metafile</alias>
        <status><topicref TID="wmf"/> has a number of limitations and shortcomings that have been addressed in the newer <topicref TID="emf"/> format.</status>
    </topic>
    <topic domain="wwww" TID="emf" crdate="20050127">
        <derived-from template="graphicsformat"/>
        <name>EMF</name>
        <alias>Enhanced Metafile</alias>
    </topic>
    <topic domain="wwww" TID="gif" crdate="20000608">
        <derived-from template="imageformat"/>
        <derived-from template="imagecompression"/>
        <name>GIF</name>
        <alias>Graphics Interchange Format</alias>
        <desc><topicref TID="gif"/> is a data stream-oriented <topicref TID="imageformat"/> used to define the transmission protocol of <topicref TID="lzw"/>-encoded bitmap data. <topicref TID="gif"/> images may be up to eight bits (256 colors) in depth and are always compressed. Despite the fact that <topicref TID="gif"/> supports only 8-bits worth of colors, and the multimedia extensions introduced in the <topicref TID="gif89a"/> release have not been widely utilized, <topicref TID="gif"/> still remains a popular choice for storing lower resolution image data. Any software created or modified after 1994 that supports the capability of reading and/or writing <topicref TID="gif"/> files must obtain a patent license agreement from Unisys Corporation. For publishing on the <topicref TID="www"/>, <topicref TID="jpeg"/> is a good companion format for photo-realistic images, while <topicref TID="png"/> has been designed to replace <topicref TID="gif"/> in the long run.</desc>
    </topic>
    <topic domain="wwww" TID="gif87" crdate="20010311">
        <derived-from template="gif"/>
        <name>GIF87</name>
    </topic>
    <topic domain="wwww" TID="gif89a" crdate="20010311">
        <derived-from template="gif"/>
        <name>GIF89a</name>
    </topic>
    <topic domain="wwww" TID="jbigroup" crdate="20010307">
        <derived-from template="group"/>
        <name>JBIG</name>
        <alias>Joint Bi-level Image Experts Group</alias>
        <desc><topicref TID="jbigroup"/> is the name of the committee that designed the <topicref TID="imagecompression"/> <topicref TID="algorithm"/> that is also called <topicref TID="jbig"/>.</desc>
    </topic>
    <topic domain="wwww" TID="jbig" crdate="20000904">
        <derived-from template="imagecompression"/>
        <name>JBIG</name>
        <alias>Joint Bi-level Image Experts Group</alias>
        <desc><topicref TID="jbig"/> is an <topicref TID="imagecompression"/> standard that is mainly intended as an improvement of <topicref TID="itu"/>'s <topicref TID="g3fax"/> and <topicref TID="g4fax"/> recommendations for facsimile transmission. Apart from coding bilevel (i.e., black and white) images, <topicref TID="jbig"/> can also be used for coding grayscale and color images with limited numbers of bits per pixel. It uses a lossless compression <topicref TID="algorithm"/> which typically reduces the size of the uncompressed image by a factor of twenty to one. <topicref TID="jbig"/> only defines an <topicref TID="imagecompression"/>, not an <topicref TID="imageformat"/>. <topicref TID="jbig"/> compressed data is often stored in <topicref TID="tiff"/> files.</desc>
    </topic>
    <topic domain="wwww" TID="pantone" crdate="20010313">
        <derived-from template="colorspace"/>
        <name>Pantone</name>
    </topic>
    <topic domain="wwww" TID="cmy" crdate="20010313">
        <derived-from template="colorspace"/>
        <name>CMY</name>
        <alias>Cyan Magenta Yellow</alias>
    </topic>
    <topic domain="wwww" TID="cmyk" crdate="20010313">
        <derived-from template="colorspace"/>
        <name>CMYK</name>
        <alias>Cyan Magenta Yellow Key</alias>
    </topic>
    <topic domain="wwww" TID="rgb" crdate="20010313">
        <derived-from template="colorspace"/>
        <name>RGB</name>
        <alias>Red Green Blue</alias>
    </topic>
    <topic domain="wwww" TID="srgb" crdate="20010313">
        <derived-from template="colorspace"/>
        <name>sRGB</name>
        <alias>standard RGB</alias>
        <desc>The aim of the <topicref TID="srgb"/> <topicref TID="colorspace"/> is to complement the current color management strategies by enabling a third method of handling color in <topicref TID="os"/>s, device drivers and the <topicref TID="internet"/> that utilizes a simple and robust device independent color definition. This will provide good quality and backward compatibility with minimum transmission and system overhead. Based on a calibrated colorimetric <topicref TID="rgb"/> color space well suited to <topicref TID="crt"/> monitors, television, scanners, digital cameras, and printing systems, such a space can be supported with minimum cost to software and hardware vendors.</desc>
    </topic>
    <topic domain="wwww" TID="cga" crdate="20010315">
        <derived-from template="displaystd"/>
        <name>CGA</name>
        <alias>Color Graphics Adapter</alias>
        <desc>A <topicref TID="displaystd"/> referring to a video adapter capable of a resolution of up to 320 by 200 pixels.</desc>
    </topic>
    <topic domain="wwww" TID="ega" crdate="20010315">
        <derived-from template="displaystd"/>
        <name>EGA</name>
        <alias>Enhanced Graphics Adapter</alias>
        <desc>A <topicref TID="displaystd"/> referring to a video adapter capable of a resolution of up to 640 by 350 pixels.</desc>
    </topic>
    <topic domain="wwww" TID="vga" crdate="20010315">
        <derived-from template="displaystd"/>
        <name>VGA</name>
        <alias>Video Graphics Array</alias>
        <desc>A <topicref TID="displaystd"/> referring to a video adapter capable of a resolution of up to 640 by 480 pixels.</desc>
    </topic>
    <topic domain="wwww" TID="svga" crdate="20010315">
        <derived-from template="displaystd"/>
        <name>SVGA</name>
        <alias>Super VGA</alias>
        <desc>A <topicref TID="displaystd"/> referring to a video adapter capable of a resolution of up to 800 by 600 pixels.</desc>
    </topic>
    <topic domain="wwww" TID="xga" crdate="20010315">
        <derived-from template="displaystd"/>
        <name>XGA</name>
        <alias>Extended Graphics Array</alias>
        <desc>A <topicref TID="displaystd"/> referring to a video adapter capable of a resolution of up to 1024 by 768 pixels.</desc>
    </topic>
    <topic domain="wwww" TID="sxga" crdate="20010914">
        <derived-from template="displaystd"/>
        <name>SXGA</name>
        <alias>Super XGA</alias>
        <desc>A <topicref TID="displaystd"/> referring to a video adapter capable of a resolution of up to 1280 by 1024 pixels.</desc>
    </topic>
    <topic domain="wwww" TID="sxgaplus" crdate="20010914">
        <derived-from template="displaystd"/>
        <name>SXGA+</name>
        <alias>Super XGA+</alias>
        <desc>A <topicref TID="displaystd"/> referring to a video adapter capable of a resolution of up to 1400 by 1050 pixels.</desc>
    </topic>
    <topic domain="wwww" TID="wsxgaplus" crdate="20030419">
        <derived-from template="displaystd"/>
        <name>WSXGA+</name>
        <alias>Wide SXGA+</alias>
        <desc>A <topicref TID="displaystd"/> referring to a video adapter capable of a resolution of up to 1680 by 1050 pixels.</desc>
    </topic>
    <topic domain="wwww" TID="uxga" crdate="20010914">
        <derived-from template="displaystd"/>
        <name>UXGA</name>
        <alias>Ultra XGA</alias>
        <desc>A <topicref TID="displaystd"/> referring to a video adapter capable of a resolution of up to 1600 by 1200 pixels.</desc>
    </topic>
    <topic domain="wwww" TID="wxgaplus" crdate="20080429">
        <derived-from template="displaystd"/>
        <name>WXGA+</name>
        <alias>Wide XGA+</alias>
        <desc>A <topicref TID="displaystd"/> referring to a video adapter capable of a resolution of up to 1440 by 900 pixels.</desc>
    </topic>
    <topic domain="wwww" TID="wxga" crdate="20031112">
        <derived-from template="displaystd"/>
        <name>WXGA</name>
        <alias>Wide XGA</alias>
        <desc>A <topicref TID="displaystd"/> referring to a video adapter capable of a resolution of up to 1366 by 768 pixels.</desc>
    </topic>
    <topic domain="wwww" TID="wuxga" crdate="20030419">
        <derived-from template="displaystd"/>
        <name>WUXGA</name>
        <alias>Wide UXGA</alias>
        <desc>A <topicref TID="displaystd"/> referring to a video adapter capable of a resolution of up to 1920 by 1200 pixels.</desc>
    </topic>
    <topic domain="wwww" TID="qxga" crdate="20020716">
        <derived-from template="displaystd"/>
        <name>QXGA</name>
        <alias>Quad XGA</alias>
        <desc>A <topicref TID="displaystd"/> referring to a video adapter capable of a resolution of up to 2048 by 1536 pixels.</desc>
    </topic>
    <topic domain="wwww" TID="wqxga" crdate="20060322">
        <derived-from template="displaystd"/>
        <name>WQXGA</name>
        <alias>Wide QXGA</alias>
        <desc>A <topicref TID="displaystd"/> referring to a video adapter capable of a resolution of up to 2560 by 1600 pixels.</desc>
    </topic>
    <topic domain="wwww" TID="wquxga" crdate="20031014">
        <derived-from template="displaystd"/>
        <name>WQUXGA</name>
        <alias>Wide QUXGA</alias>
        <desc>A <topicref TID="displaystd"/> referring to a video adapter capable of a resolution of up to 3840 by 2400 pixels.</desc>
    </topic>
    <topic domain="wwww" TID="wqsxga" crdate="20060322">
        <derived-from template="displaystd"/>
        <name>WQSXGA</name>
        <alias>Wide QSXGA</alias>
        <desc>A <topicref TID="displaystd"/> referring to a video adapter capable of a resolution of up to 3200 by 2048 pixels.</desc>
    </topic>
    <topic domain="wwww" TID="qsxga" crdate="20031014">
        <derived-from template="displaystd"/>
        <name>QSXGA</name>
        <alias>Quad SXGA</alias>
        <desc>A <topicref TID="displaystd"/> referring to a video adapter capable of a resolution of up to 2560 by 2048 pixels.</desc>
    </topic>
    <topic domain="wwww" TID="quxga" crdate="20031014">
        <derived-from template="displaystd"/>
        <name>QUXGA</name>
        <alias>Quad UXGA</alias>
        <desc>A <topicref TID="displaystd"/> referring to a video adapter capable of a resolution of up to 3200 by 2400 pixels.</desc>
    </topic>
    <topic domain="wwww" TID="pal" crdate="20010315">
        <derived-from template="displaystd"/>
        <name>PAL</name>
        <alias>Phase Alternating Line</alias>
    </topic>
    <topic domain="wwww" TID="ntsc" crdate="20010315">
        <derived-from template="displaystd"/>
        <name>NTSC</name>
        <alias>National Television System Committee</alias>
    </topic>
    <topic domain="wwww" TID="secam" crdate="20010315">
        <derived-from template="displaystd"/>
        <name>SECAM</name>
        <alias>Sequential Couleur Avec Memoire</alias>
    </topic>
    <topic domain="wwww" TID="tv" crdate="20061116">
        <derived-from template="concept"/>
        <name>TV</name>
        <alias>Television</alias>
    </topic>
    <topic domain="wwww" TID="tv43" crdate="20061116">
        <derived-from template="concept"/>
        <name>4:3</name>
    </topic>
    <topic domain="wwww" TID="tv169" crdate="20061116">
        <derived-from template="concept"/>
        <name>16:9</name>
    </topic>
    <topic domain="wwww" TID="atv" crdate="20061116">
        <derived-from template="tv"/>
        <name>ATV</name>
        <alias>Analog Television</alias>
    </topic>
    <topic domain="wwww" TID="dtv" crdate="20061116">
        <derived-from template="tv"/>
        <name>DTV</name>
        <alias>Digital Television</alias>
    </topic>
    <topic domain="wwww" TID="sdtv" crdate="20061116">
        <derived-from template="dtv"/>
        <name>SDTV</name>
        <alias>Standard Definition Television</alias>
    </topic>
    <topic domain="wwww" TID="hdtv" crdate="20061116">
        <derived-from template="dtv"/>
        <name>HDTV</name>
        <alias>High Definition Television</alias>
    </topic>
    <topic domain="wwww" TID="hdtv1080p" crdate="20061116">
        <derived-from template="displaystd"/>
        <name>1080p</name>
        <alias>HDTV 1080 progressive</alias>
        <desc>A <topicref TID="hdtv"/> <topicref TID="displaystd"/> referring to a <topicref TID="tv"/> signal with a resolution of up to 1080 by 1920 pixels. It is a <topicref TID="tv169"/> <topicref TID="tv"/> signal using progressive build-up of the signal's lines.</desc>
    </topic>
    <topic domain="wwww" TID="hdtv1080i" crdate="20061116">
        <derived-from template="displaystd"/>
        <name>1080i</name>
        <alias>HDTV 1080 interlaced</alias>
        <desc>A <topicref TID="hdtv"/> <topicref TID="displaystd"/> referring to a <topicref TID="tv"/> signal with a resolution of up to 1080 by 1920 pixels. It is a <topicref TID="tv169"/> <topicref TID="tv"/> signal using interlaced build-up of the signal's lines.</desc>
    </topic>
    <topic domain="wwww" TID="hdtv720p" crdate="20061116">
        <derived-from template="displaystd"/>
        <name>720p</name>
        <alias>HDTV 720 progressive</alias>
        <desc>A <topicref TID="hdtv"/> <topicref TID="displaystd"/> referring to a <topicref TID="tv"/> signal with a resolution of up to 720 by 1280 pixels. It is a <topicref TID="tv169"/> <topicref TID="tv"/> signal using progressive build-up of the signal's lines.</desc>
    </topic>
    <topic domain="wwww" TID="sdtv576p" crdate="20061116">
        <derived-from template="displaystd"/>
        <name>576p</name>
        <alias>SDTV 576 progressive</alias>
        <desc>A <topicref TID="sdtv"/> <topicref TID="displaystd"/> referring to a <topicref TID="tv"/> signal with a resolution of up to 576 by 720 pixels. It is a <topicref TID="tv43"/> <topicref TID="tv"/> signal using progressive build-up of the signal's lines.</desc>
    </topic>
    <topic domain="wwww" TID="sdtv576i" crdate="20061116">
        <derived-from template="displaystd"/>
        <name>576i</name>
        <alias>SDTV 576 interlaced</alias>
        <desc>A <topicref TID="sdtv"/> <topicref TID="displaystd"/> referring to a <topicref TID="tv"/> signal with a resolution of up to 576 by 720 pixels. It is a <topicref TID="tv43"/> <topicref TID="tv"/> signal using interlaced build-up of the signal's lines.</desc>
    </topic>
    <topic domain="wwww" TID="sdtv480p" crdate="20061116">
        <derived-from template="displaystd"/>
        <name>480p</name>
        <alias>SDTV 480 progressive</alias>
        <desc>A <topicref TID="sdtv"/> <topicref TID="displaystd"/> referring to a <topicref TID="tv"/> signal with a resolution of up to 480 by 720 pixels. It is a <topicref TID="tv43"/> <topicref TID="tv"/> signal using progressive build-up of the signal's lines.</desc>
    </topic>
    <topic domain="wwww" TID="sdtv480i" crdate="20061116">
        <derived-from template="displaystd"/>
        <name>480i</name>
        <alias>SDTV 480 interlaced</alias>
        <desc>A <topicref TID="sdtv"/> <topicref TID="displaystd"/> referring to a <topicref TID="tv"/> signal with a resolution of up to 480 by 720 pixels. It is a <topicref TID="tv43"/> <topicref TID="tv"/> signal using interlaced build-up of the signal's lines.</desc>
    </topic>
    <topic domain="wwww" TID="crt" crdate="20010314">
        <derived-from template="display"/>
        <name>CRT</name>
        <alias>Cathode Ray Tube</alias>
    </topic>
    <topic domain="wwww" TID="lcd" crdate="20010314">
        <derived-from template="display"/>
        <name>LCD</name>
        <alias>Liquid Crystal Display</alias>
    </topic>
    <topic domain="wwww" TID="eld" crdate="20010319">
        <derived-from template="display"/>
        <name>ELD</name>
        <alias>Electroluminescent Display</alias>
    </topic>
    <topic domain="wwww" TID="led" crdate="20010317">
        <derived-from template="display"/>
        <name>LED</name>
        <alias>Light Emitting Diode</alias>
    </topic>
    <topic domain="wwww" TID="oled" crdate="20020716">
        <derived-from template="display"/>
        <name>OLED</name>
        <alias>Organic LED</alias>
    </topic>
    <topic domain="wwww" TID="tft" crdate="20010317">
        <derived-from template="lcd"/>
        <name>TFT</name>
        <alias>Thin Film Transistor</alias>
    </topic>
    <topic domain="wwww" TID="dstn" crdate="20010319">
        <derived-from template="lcd"/>
        <name>DSTN</name>
        <alias>Double-Layer Supertwist Nematic</alias>
    </topic>
    <topic domain="wwww" TID="pdp" crdate="20010315">
        <derived-from template="display"/>
        <name>PDP</name>
        <alias>Plasma Display Panel</alias>
    </topic>
    <topic domain="wwww" TID="fed" crdate="20010315">
        <derived-from template="display"/>
        <name>FED</name>
        <alias>Field Emission Display</alias>
    </topic>
    <topic domain="wwww" TID="dct" crdate="20010305">
        <derived-from template="topic"/>
        <name>DCT</name>
        <alias>Discrete Cosine Transform</alias>
    </topic>
    <topic domain="wwww" TID="wavelet" crdate="20051130">
        <derived-from template="topic"/>
        <name>Wavelet</name>
    </topic>
    <topic domain="wwww" TID="xmldb" crdate="20021220">
        <derived-from template="group"/>
        <name>XML:DB</name>
    </topic>
    <topic domain="wwww" TID="sqlx" modate="20040213" crdate="20021217">
        <derived-from template="group"/>
        <name>SQLX</name>
        <desc><topicref TID="sqlx"/> is the name of an informal <topicref TID="group"/> that has been formed to explore the technology and develop proposals for the <topicref TID="sqlxml"/> part of the <topicref TID="sql"/> specification.</desc>
        <status>In 2003, <topicref TID="sqlxml"/> has been standardized by <topicref TID="iso"/>, and therefore the <topicref TID="sqlx"/> <topicref TID="group"/> does not exist anymore.</status>
    </topic>
    <topic domain="wwww" TID="jpegroup" crdate="20010307">
        <derived-from template="group"/>
        <name>JPEG</name>
        <alias>Joint Photographic Experts Group</alias>
        <desc><topicref TID="jpegroup"/> is the name of the committee that designed the <topicref TID="imagecompression"/> <topicref TID="algorithm"/> that is also called <topicref TID="jpeg"/>.</desc>
    </topic>
    <topic domain="wwww" TID="jfif" crdate="20010311">
        <derived-from template="imageformat"/>
        <name>JFIF</name>
        <alias>JPEG File Interchange Format</alias>
        <desc><topicref TID="jfif"/> is the technical name for the <topicref TID="imageformat"/> better (but inaccurately) known as <topicref TID="jpeg"/>. This term is used only when the difference between the <topicref TID="imageformat"/> and the <topicref TID="imagecompression"/> is crucial. Strictly speaking, however, <topicref TID="jpeg"/> does not define an <topicref TID="imageformat"/>, and therefore in most cases it would be more precise to speak of <topicref TID="jfif"/> rather than <topicref TID="jpeg"/>. Another <topicref TID="imageformat"/> for <topicref TID="jpeg"/> is <topicref TID="spiff"/> defined by the <topicref TID="jpeg"/> standard itself, but <topicref TID="jfif"/> is much more widespread than <topicref TID="spiff"/>.</desc>
    </topic>
    <topic domain="wwww" TID="jp2" crdate="20070313">
        <derived-from template="imageformat"/>
        <name>JP2</name>
    </topic>
    <topic domain="wwww" TID="jpx" crdate="20070313">
        <derived-from template="imageformat"/>
        <name>JPX</name>
    </topic>
    <topic domain="wwww" TID="jpip" crdate="20070313">
        <derived-from template="protocol"/>
        <name>JPIP</name>
        <alias>JPEG 2000 Interactive Protocol</alias>
    </topic>
    <topic domain="wwww" TID="jpeg2000" crdate="20020626" modate="20070313">
        <derived-from template="imagecompression"/>
        <name>JPEG 2000</name>
        <desc><topicref TID="jpeg2000"/> is a <topicref TID="wavelet"/>-based <topicref TID="imagecompression"/> which has been designed as the successor of the popular <topicref TID="jpeg"/> <topicref TID="imagecompression"/>. One of the most important differences is that <topicref TID="jpeg2000"/> includes a lossless mode for <topicref TID="imagecompression"/>, whereas <topicref TID="jpeg"/> always used lossy <topicref TID="imagecompression"/> algorithms.</desc>
    </topic>
    <topic domain="wwww" TID="spiff" crdate="20010311">
        <derived-from template="imageformat"/>
        <name>SPIFF</name>
        <alias>Still Picture Interchange File Format</alias>
        <desc><topicref TID="spiff"/> is the "official" <topicref TID="imageformat"/> for images using the <topicref TID="jpeg"/> <topicref TID="imagecompression"/> <topicref TID="algorithm"/>. Part 3 of the <topicref TID="jpeg"/> standard includes a fully defined <topicref TID="imageformat"/> for storing <topicref TID="jpeg"/> data. When the <topicref TID="jpeg"/> format was first standardized, disagreements among <topicref TID="iso"/> committees prevented a standard <topicref TID="jpeg"/> <topicref TID="imageformat"/> from being created. The de-facto format that appeared was <topicref TID="jfif"/> from C-cube Microsystems. The <topicref TID="jfif"/> <topicref TID="imageformat"/>, although now widespread, is very limited in capability as <topicref TID="imageformat"/>s go. <topicref TID="spiff"/> is intended to replace <topicref TID="jfif"/>, adding features (more color spaces, a recognized way of including text blocks, and so forth), and providing a backwards-compatibility allowing <topicref TID="spiff"/> files to be read by most <topicref TID="jpeg"/>/<topicref TID="jfif"/> decoders. <topicref TID="jfif"/>, however, has a five-year head start on <topicref TID="spiff"/>, so the likelihood of it being completely replaced anytime soon is not good.</desc>
    </topic>
    <topic domain="wwww" TID="jpeg" crdate="20000608">
        <derived-from template="imagecompression"/>
        <name>JPEG</name>
        <alias>Joint Photographic Experts Group</alias>
        <desc><topicref TID="jpeg"/> is an <topicref TID="imagecompression"/> <topicref TID="algorithm"/> that is designed for compressing either full-color or grayscale digital images of natural, real-world scenes. It does not work very well on non-realistic images, such as cartoons or line drawings. <topicref TID="jpeg"/> does not handle compression of black and white (1 bit per pixel) images or moving pictures. <topicref TID="jpeg"/> itself does not describe an <topicref TID="imageformat"/>, it only specifies the compression <topicref TID="algorithm"/>. Some <topicref TID="imageformat"/>s for exchanging images compressed with the <topicref TID="jpeg"/> <topicref TID="algorithm"/> are the wide-spread <topicref TID="jfif"/> and the less popular <topicref TID="spiff"/>.</desc>
    </topic>
    <topic domain="wwww" TID="tiff" crdate="20000608">
        <derived-from template="imageformat"/>
        <name>TIFF</name>
        <alias>Tag Image File Format</alias>
        <desc><topicref TID="tiff"/> defines a tag-based <topicref TID="imageformat"/> that can characterize almost any form of 2D raster data using either <topicref TID="ascii"/> or binary coding. "Private" tags may be used to allow additional parameters to be added to the descriptor. "Standard" <topicref TID="tiff"/> allows the use of <topicref TID="packbits"/>, <topicref TID="lzw"/>, <topicref TID="g3fax"/>, <topicref TID="g4fax"/>, and <topicref TID="jpeg"/> compression schemes within transmitted images. Four photometric classes are supported: TIFF-B for monochrome, TIFF-G for grayscale, TIFF-P for palette-based coding, and TIFF-R for <topicref TID="rgb"/> coding.</desc>
    </topic>
    <topic domain="wwww" TID="tiffep" crdate="20050418">
        <derived-from template="imageformat"/>
        <name>TIFF/EP</name>
        <alias>TIFF for Electronic Photography</alias>
    </topic>
    <topic domain="wwww" TID="dng" crdate="20050418">
        <derived-from template="imageformat"/>
        <name>DNG</name>
        <alias>Digital Negative</alias>
    </topic>
    <topic domain="wwww" TID="png" crdate="20000608">
        <derived-from template="imageformat"/>
        <derived-from template="imagecompression"/>
        <name>PNG</name>
        <alias>Portable Network Graphics</alias>
    </topic>
    <topic domain="wwww" TID="jng" crdate="20010311">
        <derived-from template="imageformat"/>
        <name>JNG</name>
        <alias>JPEG Network Graphics</alias>
    </topic>
    <topic domain="wwww" TID="bmp" crdate="20010314">
        <derived-from template="imageformat"/>
        <name>BMP</name>
    </topic>
    <topic domain="wwww" TID="pcx" crdate="20010314">
        <derived-from template="imageformat"/>
        <name>PCX</name>
    </topic>
    <topic domain="wwww" TID="pict" crdate="20010314">
        <derived-from template="imageformat"/>
        <derived-from template="graphicsformat"/>
        <name>PICT</name>
    </topic>
    <topic domain="wwww" TID="rle" crdate="20010311">
        <derived-from template="compression"/>
        <name>RLE</name>
        <alias>Run-Length Encoding</alias>
    </topic>
    <topic domain="wwww" TID="g3fax" crdate="20010311">
        <derived-from template="protocol"/>
        <name>G3 Fax</name>
        <alias>Group 3 Fax</alias>
    </topic>
    <topic domain="wwww" TID="g4fax" crdate="20010311">
        <derived-from template="protocol"/>
        <name>G4 Fax</name>
        <alias>Group 4 Fax</alias>
    </topic>
    <topic domain="wwww" TID="apng" crdate="20070314">
        <derived-from template="imageformat"/>
        <name>APNG</name>
        <alias>Animated Portable Network Graphics</alias>
    </topic>
    <topic domain="wwww" TID="mng" crdate="20000612">
        <derived-from template="imageformat"/>
        <name>MNG</name>
        <alias>Multiple-image Network Graphics</alias>
    </topic>
    <topic domain="wwww" TID="mpeg1" crdate="20000704">
        <derived-from template="videocompression"/>
        <name>MPEG-1</name>
    </topic>
    <topic domain="wwww" TID="mpeg2" crdate="20000704">
        <derived-from template="videocompression"/>
        <name>MPEG-2</name>
    </topic>
    <topic domain="wwww" TID="mpeg4" crdate="20000704">
        <derived-from template="videocompression"/>
        <name>MPEG-4</name>
    </topic>
    <topic domain="wwww" TID="mpeg7" crdate="20000704">
        <derived-from template="framework"/>
        <name>MPEG-7</name>
    </topic>
    <topic domain="wwww" TID="mpeg21" crdate="20020902">
        <derived-from template="framework"/>
        <name>MPEG-21</name>
    </topic>
    <topic domain="wwww" TID="didl" crdate="20020902">
        <derived-from template="dataformat"/>
        <name>DIDL</name>
        <alias>Digital Item Declaration Language</alias>
    </topic>
    <topic domain="wwww" TID="cel" crdate="20040107">
        <derived-from template="dataformat"/>
        <name>CEL</name>
        <alias>Contract Expression Language</alias>
    </topic>
    <topic domain="wwww" TID="rel" crdate="20020902">
        <derived-from template="dataformat"/>
        <name>REL</name>
        <alias>Rights Expression Language</alias>
    </topic>
    <topic domain="wwww" TID="rdd" crdate="20020902">
        <derived-from template="dataformat"/>
        <name>RDD</name>
        <alias>Rights Data Dictionary</alias>
    </topic>
    <topic domain="wwww" TID="pdu" crdate="20010322">
        <derived-from template="concept"/>
        <name>PDU</name>
        <alias>Protocol Data Unit</alias>
    </topic>
    <topic domain="wwww" TID="bnf" crdate="20010307">
        <derived-from template="dataformat"/>
        <name>BNF</name>
        <alias>Backus-Naur Form</alias>
        <desc><topicref TID="bnf"/> is a formal meta-syntax used to express context-free <topicref TID="grammar"/>s. <topicref TID="bnf"/> is one of the most commonly used meta-syntactic notation s for specifying the syntax of programming languages, command sets, <topicref TID="pdu"/>s, and similar things. However, pure <topicref TID="bnf"/> is rather limited, so the two variations <topicref TID="ebnf"/> and <topicref TID="abnf"/> have become more popular.</desc>
    </topic>
    <topic domain="wwww" TID="ebnf" crdate="20010307">
        <derived-from template="bnf"/>
        <name>EBNF</name>
        <alias>Extended Backus-Naur Form</alias>
        <desc>An <topicref TID="ebnf"/> is any variation on the basic <topicref TID="bnf"/> meta-syntax notation with (some of) the following additional constructs: square brackets surrounding optional items, asterisk suffix for a sequence of zero or more of an item, plus-sign suffix for one or more of an item, curly brackets enclosing a list of alternatives, and super- and subscripts indicating the number of possible occurrences. All these constructs can be expressed in plain <topicref TID="bnf"/> using extra productions and have been added for readability and succinctness.</desc>
    </topic>
    <topic domain="wwww" TID="abnf" crdate="20010307">
        <derived-from template="bnf"/>
        <name>ABNF</name>
        <alias>Augmented Backus-Naur Form</alias>
        <desc>Internet technical specifications often need to define a format syntax and are free to employ whatever notation their authors deem useful. Over the years, a modified version of <topicref TID="bnf"/>, called <topicref TID="abnf"/>, has been popular among many <topicref TID="internet"/> specifications. It balances compactness and simplicity with reasonable representational power.</desc>
    </topic>
    <topic domain="wwww" TID="bc" crdate="20010307">
        <derived-from template="audiocompression"/>
        <name>BC</name>
        <alias>Backward Compatible</alias>
        <desc><topicref TID="bc"/> audio coding is one of two audio coding methods defined by the <topicref TID="mpeg2"/> standard. It is backward compatible with <topicref TID="mpeg1"/> audio coding. <topicref TID="bc"/> is comprised of three different and increasingly complex layers, and if all three layers are used, it is the audio coding most commonly referred to as <topicref TID="mp3"/>. <topicref TID="mpeg2"/> also defines a non backward compatible audio coding, which is known as <topicref TID="aac"/>.</desc>
    </topic>
    <topic domain="wwww" TID="aac" crdate="20000704">
        <derived-from template="audiocompression"/>
        <name>AAC</name>
        <alias>Advanced Audio Coding</alias>
        <desc><topicref TID="aac"/> is one of two audio coding methods defined by the <topicref TID="mpeg2"/> standard. It is not backward compatible with <topicref TID="mpeg1"/> audio coding, which is why it is sometimes also referred to as the "non backward compatible" audio coding of <topicref TID="mpeg2"/>. <topicref TID="aac"/> provides more sophisticated audio coding than <topicref TID="mpeg2"/> <topicref TID="bc"/> audio coding (the other audio coding method of <topicref TID="mpeg2"/>, better known as <topicref TID="mp3"/>), but it is not as widely spread.</desc>
    </topic>
    <topic domain="wwww" TID="umd" crdate="20050918">
        <derived-from template="ostorage"/>
        <name>UMD</name>
        <alias>Universal Media Disc</alias>
    </topic>
    <topic domain="wwww" TID="cd" crdate="20010302">
        <derived-from template="ostorage"/>
        <name>CD</name>
        <alias>Compact Disc</alias>
    </topic>
    <topic domain="wwww" TID="cdrom" crdate="20010302">
        <derived-from template="cd"/>
        <name>CD-ROM</name>
    </topic>
    <topic domain="wwww" TID="cdr1" crdate="20020322">
        <derived-from template="cd"/>
        <name>CD-R</name>
        <alias>CD Recordable</alias>
    </topic>
    <topic domain="wwww" TID="cdrw" crdate="20020322">
        <derived-from template="cd"/>
        <name>CD-RW</name>
        <alias>CD Rewritable</alias>
    </topic>
    <topic domain="wwww" TID="highsierra" crdate="20010305">
        <derived-from template="lfs"/>
        <name>High Sierra</name>
        <desc>The <topicref TID="highsierra"/> format is a logical format for <topicref TID="cdrom"/> media. It was used mainly between 1986 and 1988, after 1988 it was replaced by the <topicref TID="iso9660"/> standard for the logical format on <topicref TID="cdrom"/> media (<topicref TID="highsierra"/> and <topicref TID="iso9660"/> are identical in content, but the exact format is different).</desc>
    </topic>
    <topic domain="wwww" TID="cfs" crdate="20021115">
        <derived-from template="lfs"/>
        <name>CFS</name>
        <alias>Cryptographic File System</alias>
    </topic>
    <topic domain="wwww" TID="tcfs" crdate="20021115">
        <derived-from template="lfs"/>
        <name>TCFS</name>
        <alias>Transparent Cryptographic File System</alias>
    </topic>
    <topic domain="wwww" TID="udf" crdate="20010305">
        <derived-from template="lfs"/>
        <name>UDF</name>
        <alias>Universal Disk Format</alias>
    </topic>
    <topic domain="wwww" TID="jfs" crdate="20011207">
        <derived-from template="lfs"/>
        <name>JFS</name>
        <alias>Journaling File System</alias>
    </topic>
    <topic domain="wwww" TID="xfs" crdate="20011207">
        <derived-from template="lfs"/>
        <name>XFS</name>
        <alias>Extended File System</alias>
    </topic>
    <topic domain="wwww" TID="gpfs" crdate="20011207">
        <derived-from template="dfs"/>
        <name>GPFS</name>
        <alias>General Parallel File System</alias>
    </topic>
    <topic domain="wwww" TID="ufs" crdate="20011207">
        <derived-from template="lfs"/>
        <name>UFS</name>
        <alias>Unix File System</alias>
    </topic>
    <topic domain="wwww" TID="hfs" crdate="20010305">
        <derived-from template="lfs"/>
        <name>HFS</name>
        <alias>Hierarchical File System</alias>
    </topic>
    <topic domain="wwww" TID="tld" crdate="20010309">
        <derived-from template="topic"/>
        <name>TLD</name>
        <alias>Top-Level Domain</alias>
        <desc>A <topicref TID="tld"/> is that part of a <topicref TID="dns"/> <topicref TID="fqdn"/> which stands right of the rightmost full stop. Two letter <topicref TID="tld"/>s designate <topicref TID="cctld"/>s, and three letter <topicref TID="tld"/>s designate <topicref TID="gtld"/>s.</desc>
    </topic>
    <topic domain="wwww" TID="gtld" crdate="20010309">
        <derived-from template="tld"/>
        <name>gTLD</name>
        <alias>Generic TLD</alias>
        <desc>A <topicref TID="gtld"/> is a <topicref TID="dns"/> <topicref TID="tld"/> which is not specific to a country. Each of the <topicref TID="gtld"/>s was created for a general category of organizations. Generally, under the <topicref TID="gtld"/>s the structure is very flat. That is, many organizations are registered directly under the <topicref TID="gtld"/>, and any further structure is up to the individual organizations.</desc>
    </topic>
    <topic domain="wwww" TID="cctld" crdate="20010309">
        <derived-from template="tld"/>
        <name>ccTLD</name>
        <alias>Country-Code TLD</alias>
        <desc>A <topicref TID="cctld"/> is a <topicref TID="dns"/> <topicref TID="tld"/> identifying domain names for a given country. The country-codes being used are the two letter codes defined by ISO 3166. The <topicref TID="iana"/> is not in the business of deciding what is and what is not a country. The selection of the ISO 3166 list as a basis for <topicref TID="cctld"/>s was made with the knowledge that <topicref TID="iso"/> has a procedure for determining which entities should be and should not be on that list.</desc>
    </topic>
    <topic domain="wwww" TID="exfat" crdate="20080407">
        <derived-from template="lfs"/>
        <name>exFAT</name>
        <alias>Extended FAT</alias>
    </topic>
    <topic domain="wwww" TID="ntfs" crdate="20010328">
        <derived-from template="lfs"/>
        <name>NTFS</name>
        <alias>NT File System</alias>
    </topic>
    <topic domain="wwww" TID="fat" crdate="20020701">
        <derived-from template="lfs"/>
        <name>FAT</name>
        <alias>File Allocation Table</alias>
    </topic>
    <topic domain="wwww" TID="fat16" crdate="20020701">
        <derived-from template="fat"/>
        <name>FAT16</name>
    </topic>
    <topic domain="wwww" TID="fat32" crdate="20020701">
        <derived-from template="fat"/>
        <name>FAT32</name>
    </topic>
    <topic domain="wwww" TID="mudf" crdate="20010305">
        <derived-from template="lfs"/>
        <name>M-UDF</name>
        <alias>Micro UDF</alias>
    </topic>
    <topic domain="wwww" TID="udfbridge" crdate="20010305">
        <derived-from template="lfs"/>
        <name>UDF Bridge</name>
    </topic>
    <topic domain="wwww" TID="iso13346" crdate="20010305">
        <derived-from template="lfs"/>
        <name>ISO 13346</name>
    </topic>
    <topic domain="wwww" TID="highmat" crdate="20040102">
        <derived-from template="lfs"/>
        <name>HighMAT</name>
        <alias>High Performance Media Access Technology</alias>
    </topic>
    <topic domain="wwww" TID="iso9660" crdate="20010305">
        <derived-from template="lfs"/>
        <name>ISO 9660</name>
        <desc>The <topicref TID="iso9660"/> format is a logical format for <topicref TID="cdrom"/> media. It was standardized in 1988 and replaced the <topicref TID="highsierra"/> standard for the logical format on <topicref TID="cdrom"/> media (<topicref TID="iso9660"/> and <topicref TID="highsierra"/> are identical in content, but the exact format is different).</desc>
    </topic>
    <topic domain="wwww" TID="dat" crdate="20010305">
        <derived-from template="mstorage"/>
        <derived-from template="audioformat"/>
        <name>DAT</name>
        <alias>Digital Audio Tape</alias>
    </topic>
    <topic domain="wwww" TID="cdda" crdate="20010302">
        <derived-from template="cd"/>
        <derived-from template="audioformat"/>
        <name>CD-DA</name>
        <alias>CD Digital Audio</alias>
    </topic>
    <topic domain="wwww" TID="vcd" crdate="20010509">
        <derived-from template="cd"/>
        <derived-from template="videoformat"/>
        <name>VCD</name>
        <alias>Video CD</alias>
    </topic>
    <topic domain="wwww" TID="svcd" crdate="20010509">
        <derived-from template="cd"/>
        <derived-from template="videoformat"/>
        <name>SVCD</name>
        <alias>Super Video CD</alias>
    </topic>
    <topic domain="wwww" TID="osta" crdate="20010305">
        <derived-from template="organization"/>
        <name>OSTA</name>
        <alias>Optical Storage Technology Association</alias>
    </topic>
    <topic domain="wwww" TID="md" crdate="20010305">
        <derived-from template="mostorage"/>
        <name>MD</name>
        <alias>MiniDisc</alias>
    </topic>
    <topic domain="wwww" TID="ieee1394" crdate="20010315">
        <derived-from template="hwinterface"/>
        <name>IEEE 1394</name>
        <alias>FireWire</alias>
    </topic>
    <topic domain="wwww" TID="usb" crdate="20010315">
        <derived-from template="hwinterface"/>
        <name>USB</name>
        <alias>Universal Serial Bus</alias>
    </topic>
    <topic domain="wwww" TID="rj11" crdate="20020628">
        <derived-from template="hwinterface"/>
        <name>RJ11</name>
        <alias>Registered Jack 11</alias>
    </topic>
    <topic domain="wwww" TID="rj12" crdate="20030108">
        <derived-from template="hwinterface"/>
        <name>RJ12</name>
        <alias>Registered Jack 12</alias>
    </topic>
    <topic domain="wwww" TID="rs232" crdate="20020628">
        <derived-from template="hwinterface"/>
        <name>RS232</name>
    </topic>
    <topic domain="wwww" TID="rs422" crdate="20020702">
        <derived-from template="hwinterface"/>
        <name>RS422</name>
    </topic>
    <topic domain="wwww" TID="rs423" crdate="20020702">
        <derived-from template="hwinterface"/>
        <name>RS423</name>
    </topic>
    <topic domain="wwww" TID="rs485" crdate="20020702">
        <derived-from template="hwinterface"/>
        <name>RS485</name>
    </topic>
    <topic domain="wwww" TID="rj45" crdate="20020628">
        <derived-from template="hwinterface"/>
        <name>RJ45</name>
        <alias>Registered Jack 45</alias>
    </topic>
    <topic domain="wwww" TID="bnc" crdate="20020628">
        <derived-from template="hwinterface"/>
        <name>BNC</name>
        <alias>British Naval Connector</alias>
    </topic>
    <topic domain="wwww" TID="atapi" crdate="20010315">
        <derived-from template="hwinterface"/>
        <name>ATAPI</name>
        <alias>ATA Packet Interface</alias>
    </topic>
    <topic domain="wwww" TID="ata" crdate="20010315">
        <derived-from template="hwinterface"/>
        <name>ATA</name>
        <alias>AT Attachment</alias>
    </topic>
    <topic domain="wwww" TID="pata" crdate="20081112">
        <derived-from template="hwinterface"/>
        <name>PATA</name>
        <alias>Parallel ATA</alias>
    </topic>
    <topic domain="wwww" TID="sata" crdate="20060305">
        <derived-from template="hwinterface"/>
        <name>SATA</name>
        <alias>Serial ATA</alias>
    </topic>
    <topic domain="wwww" TID="eide" crdate="20010315">
        <derived-from template="hwinterface"/>
        <name>EIDE</name>
        <alias>Extended IDE</alias>
    </topic>
    <topic domain="wwww" TID="ide" crdate="20010315">
        <derived-from template="hwinterface"/>
        <name>IDE</name>
        <alias>Integrated Drive Electronics</alias>
    </topic>
    <topic domain="wwww" TID="agp" crdate="20020709" modate="20040625">
        <derived-from template="hwinterface"/>
        <name>AGP</name>
        <alias>Accelerated Graphics Port</alias>
        <status>In 2004, <topicref TID="agp"/> (together with the <topicref TID="pci"/> <topicref TID="hwinterface"/>) has been replaced by the more powerful <topicref TID="pcie"/>.</status>
    </topic>
    <topic domain="wwww" TID="agppro" crdate="20040625">
        <derived-from template="agp"/>
        <name>AGP Pro</name>
        <desc><topicref TID="agppro"/> is a <topicref TID="hwinterface"/> for high-power graphics cards which can deliver more electrical power than the standard <topicref TID="agp"/> <topicref TID="hwinterface"/>.</desc>
    </topic>
    <topic domain="wwww" TID="pcie" modate="20040824" crdate="20040625">
        <derived-from template="hwinterface"/>
        <name>PCIe</name>
        <alias>PCI Express</alias>
    </topic>
    <topic domain="wwww" TID="pcix" crdate="20040824">
        <derived-from template="hwinterface"/>
        <name>PCI-X</name>
        <alias>PCI Extended</alias>
        <desc><topicref TID="pcix"/> is backwards compatible with the standard <topicref TID="pci"/>, but it uses higher bus rates.</desc>
    </topic>
    <topic domain="wwww" TID="pci" crdate="20020709" modate="20040625">
        <derived-from template="hwinterface"/>
        <name>PCI</name>
        <alias>Peripheral Component Interconnect</alias>
        <status>In 2004, <topicref TID="pci"/> (together with the <topicref TID="agp"/> <topicref TID="hwinterface"/>) has been replaced by the more powerful <topicref TID="pcie"/>.</status>
    </topic>
    <topic domain="wwww" TID="gsmp" crdate="20020719">
        <derived-from template="protocol"/>
        <name>GSMP</name>
        <alias>General Switch Management Protocol</alias>
    </topic>
    <topic domain="wwww" TID="iscsi" crdate="20020719" modate="20060305">
        <derived-from template="protocol"/>
        <name>iSCSI</name>
        <alias>Internet SCSI</alias>
    </topic>
    <topic domain="wwww" TID="fcip" crdate="20020719">
        <derived-from template="protocol"/>
        <name>FCIP</name>
        <alias>Fibre Channel over IP</alias>
    </topic>
    <topic domain="wwww" TID="fc" crdate="20060305">
        <derived-from template="protocol"/>
        <name>FC</name>
        <alias>Fibre Channel</alias>
    </topic>
    <topic domain="wwww" TID="ifcp" crdate="20020719">
        <derived-from template="protocol"/>
        <name>iFCP</name>
        <alias>Internet Fibre Channel Protocol</alias>
    </topic>
    <topic domain="wwww" TID="scsi" crdate="20010315">
        <derived-from template="hwinterface"/>
        <name>SCSI</name>
        <alias>Small Computer System Interface</alias>
    </topic>
    <topic domain="wwww" TID="sas2" crdate="20060305">
        <derived-from template="hwinterface"/>
        <name>SAS</name>
        <alias>Serial Attached SCSI</alias>
    </topic>
    <topic domain="wwww" TID="spdif" crdate="20051212">
        <derived-from template="hwinterface"/>
        <derived-from template="audioformat"/>
        <name>S/PDIF</name>
        <alias>Sony/Philips Digital Interconnect Format</alias>
    </topic>
    <topic domain="wwww" TID="midi" crdate="20010315">
        <derived-from template="hwinterface"/>
        <derived-from template="audioformat"/>
        <name>MIDI</name>
        <alias>Musical Instrument Digital Interface</alias>
        <desc><topicref TID="midi"/> enables people to use multimedia computers and electronic musical instruments. There are actually three components to <topicref TID="midi"/>, the communications "<topicref TID="protocol"/>", the <topicref TID="hwinterface"/> and a distribution format called "Standard MIDI Files". In the context of the <topicref TID="www"/>, the most interesting component is the <topicref TID="audioformat"/>. In principle, <topicref TID="midi"/> files contain sequences of <topicref TID="midi"/> <topicref TID="protocol"/> messages. However, when <topicref TID="midi"/> <topicref TID="protocol"/> messages are stored in <topicref TID="midi"/> files, the events are also time-stamped for playback in the proper sequence. Music delivered by <topicref TID="midi"/> files is the most common use of <topicref TID="midi"/> today.</desc>
    </topic>
    <topic domain="wwww" TID="cfa" crdate="20010305">
        <derived-from template="organization"/>
        <name>CFA</name>
        <alias>CompactFlash Association</alias>
    </topic>
    <topic domain="wwww" TID="fish" crdate="20040209">
        <derived-from template="flashrom"/>
        <name>FISH</name>
        <alias>Flash Internal Semiconductor Harddrive</alias>
    </topic>
    <topic domain="wwww" TID="cf" crdate="20010305">
        <derived-from template="flashrom"/>
        <name>CF</name>
        <alias>CompactFlash</alias>
    </topic>
    <topic domain="wwww" TID="mmca" crdate="20040109">
        <derived-from template="organization"/>
        <name>MMCA</name>
        <alias>MultiMediaCard Association</alias>
    </topic>
    <topic domain="wwww" TID="mmc" crdate="20020704">
        <derived-from template="flashrom"/>
        <name>MMC</name>
        <alias>MultiMediaCard</alias>
    </topic>
    <topic domain="wwww" TID="xd" crdate="20020809">
        <derived-from template="flashrom"/>
        <name>xD</name>
        <alias>extreme Digital</alias>
    </topic>
    <topic domain="wwww" TID="minisdhc" crdate="20080331">
        <derived-from template="flashrom"/>
        <name>miniSDHC</name>
        <alias>Mini SDHC</alias>
    </topic>
    <topic domain="wwww" TID="microsdhc" crdate="20080331">
        <derived-from template="flashrom"/>
        <name>microSDHC</name>
        <alias>Micro SDHC</alias>
    </topic>
    <topic domain="wwww" TID="minisd" crdate="20080331">
        <derived-from template="flashrom"/>
        <name>miniSD</name>
        <alias>Mini SD</alias>
    </topic>
    <topic domain="wwww" TID="microsd" crdate="20080331">
        <derived-from template="flashrom"/>
        <name>microSD</name>
        <alias>Micro SD</alias>
    </topic>
    <topic domain="wwww" TID="sdhc" crdate="20080331">
        <derived-from template="flashrom"/>
        <name>SDHC</name>
        <alias>SD High Capacity</alias>
    </topic>
    <topic domain="wwww" TID="sd" crdate="20020704">
        <derived-from template="flashrom"/>
        <name>SD</name>
        <alias>Secure Digital</alias>
    </topic>
    <topic domain="wwww" TID="memorystick" crdate="20020704">
        <derived-from template="flashrom"/>
        <name>Memory Stick</name>
    </topic>
    <topic domain="wwww" TID="smartmedia" crdate="20020704">
        <derived-from template="flashrom"/>
        <name>SmartMedia</name>
    </topic>
    <topic domain="wwww" TID="rce" crdate="20020811">
        <derived-from template="technology"/>
        <name>RCE</name>
        <alias>Region Code Enhancement</alias>
    </topic>
    <topic domain="wwww" TID="dvd" crdate="20010302">
        <derived-from template="ostorage"/>
        <name>DVD</name>
        <alias>Digital Versatile Disc</alias>
    </topic>
    <topic domain="wwww" TID="dvdrom" crdate="20010302">
        <derived-from template="dvd"/>
        <name>DVD-ROM</name>
    </topic>
    <topic domain="wwww" TID="dvdr" crdate="20020322">
        <derived-from template="dvd"/>
        <name>DVD-R</name>
        <alias>DVD Recordable</alias>
    </topic>
    <topic domain="wwww" TID="dvdprw" crdate="20020322">
        <derived-from template="dvd"/>
        <name>DVD+RW</name>
        <alias>DVD Rewritable</alias>
    </topic>
    <topic domain="wwww" TID="dvdmrw" crdate="20020322">
        <derived-from template="dvd"/>
        <name>DVD-RW</name>
        <alias>DVD Rewritable</alias>
    </topic>
    <topic domain="wwww" TID="dvdram" crdate="20020322">
        <derived-from template="dvd"/>
        <name>DVD-RAM</name>
        <alias>DVD Rewritable</alias>
    </topic>
    <topic domain="wwww" TID="dvdvideo" crdate="20010302">
        <derived-from template="dvd"/>
        <derived-from template="videoformat"/>
        <name>DVD-Video</name>
    </topic>
    <topic domain="wwww" TID="sacd" crdate="20010305">
        <derived-from template="dvd"/>
        <derived-from template="audioformat"/>
        <name>SACD</name>
        <alias>Super Audio CD</alias>
    </topic>
    <topic domain="wwww" TID="dvdaudio" crdate="20010302">
        <derived-from template="dvd"/>
        <derived-from template="audioformat"/>
        <name>DVD-Audio</name>
    </topic>
    <topic domain="wwww" TID="dsd" crdate="20010305">
        <derived-from template="audioformat"/>
        <name>DSD</name>
        <alias>Direct Stream Digital</alias>
    </topic>
    <topic domain="wwww" TID="atrac" crdate="20010305">
        <derived-from template="audiocompression"/>
        <name>ATRAC</name>
        <alias>Adaptive Transform Acoustic Coding</alias>
    </topic>
    <topic domain="wwww" TID="mlp" crdate="20010302">
        <derived-from template="audiocompression"/>
        <name>MLP</name>
        <alias>Meridian Lossless Packing</alias>
    </topic>
    <topic domain="wwww" TID="circ" crdate="20011119">
        <derived-from template="dataformat"/>
        <name>CIRC</name>
        <alias>Cross Interleaved Reed Solomon Code</alias>
    </topic>
    <topic domain="wwww" TID="fhss" crdate="20020704">
        <derived-from template="topic"/>
        <name>FHSS</name>
        <alias>Frequency Hopping Spread Spectrum</alias>
    </topic>
    <topic domain="wwww" TID="dsss" crdate="20020704">
        <derived-from template="topic"/>
        <name>DSSS</name>
        <alias>Direct Sequence Spread Spectrum</alias>
    </topic>
    <topic domain="wwww" TID="efm" crdate="20011119">
        <derived-from template="dataformat"/>
        <name>EFM</name>
        <alias>Eight to Fourteen Modulation</alias>
    </topic>
    <topic domain="wwww" TID="hr" crdate="20040720">
        <derived-from template="audiocompression"/>
        <name>HR</name>
        <alias>Half Rate</alias>
    </topic>
    <topic domain="wwww" TID="fr" crdate="20040720">
        <derived-from template="audiocompression"/>
        <name>FR</name>
        <alias>Full Rate</alias>
        <status><topicref TID="fr"/> <topicref TID="audiocompression"/> is only used by very old mobile phones in <topicref TID="gsm"/> <topicref TID="tnetwork"/>s, all reasonably modern mobile phones use <topicref TID="efr"/> <topicref TID="audiocompression"/>.</status>
    </topic>
    <topic domain="wwww" TID="efr" crdate="20040720">
        <derived-from template="acelp"/>
        <name>EFR</name>
        <alias>Enhanced Full Rate</alias>
        <desc><topicref TID="efr"/> <topicref TID="audiocompression"/> describes the mapping between input blocks of 160 speech samples in 13-bit <topicref TID="lpcm"/> format to encoded blocks of 244 bits, and from encoded blocks of 244 bits to output blocks of 160 reconstructed speech samples. The sampling rate is 8'000 sample/s, leading to a bit rate for the encoded bit stream of 12.2 kbit/s. The coding scheme is <topicref TID="acelp"/>.</desc>
    </topic>
    <topic domain="wwww" TID="amr" crdate="20040720">
        <derived-from template="audiocompression"/>
        <name>AMR</name>
        <alias>Adaptive Multi Rate</alias>
    </topic>
    <topic domain="wwww" TID="celp" crdate="20040721">
        <derived-from template="audiocompression"/>
        <name>CELP</name>
        <alias>Code Excited Linear Prediction</alias>
    </topic>
    <topic domain="wwww" TID="acelp" crdate="20040721">
        <derived-from template="celp"/>
        <name>ACELP</name>
        <alias>Algebraic Code Excited Linear Prediction</alias>
    </topic>
    <topic domain="wwww" TID="pcm" crdate="20010302">
        <derived-from template="audiocompression"/>
        <name>PCM</name>
        <alias>Pulse Code Modulation</alias>
    </topic>
    <topic domain="wwww" TID="lpcm" crdate="20010305">
        <derived-from template="pcm"/>
        <name>LPCM</name>
        <alias>Linear PCM</alias>
    </topic>
    <topic domain="wwww" TID="dpcm" crdate="20010305">
        <derived-from template="pcm"/>
        <name>DPCM</name>
        <alias>Differential PCM</alias>
    </topic>
    <topic domain="wwww" TID="adpcm" crdate="20010305">
        <derived-from template="pcm"/>
        <name>ADPCM</name>
        <alias>Adaptive Differential PCM</alias>
    </topic>
    <topic domain="wwww" TID="vqf" crdate="20010320">
        <derived-from template="audiocompression"/>
        <name>VQF</name>
        <alias>Vector Quantization Format</alias>
    </topic>
    <topic domain="wwww" TID="mp3" crdate="20000704" modate="20040620">
        <derived-from template="audiocompression"/>
        <name>MP3</name>
        <alias>MPEG Audio Layer III</alias>
        <status><topicref TID="mp3"/> is built into so many software and hardware products that it will remain in widespread use for a long time. Even though it is inferior in encoding quality to newer compression methods such as <topicref TID="aac"/>, and even though it has no built-in support for <topicref TID="drm"/> mechanisms, <topicref TID="mp3"/> will not disappear anytime soon.</status>
    </topic>
    <topic domain="wwww" TID="id3" crdate="20000726">
        <derived-from template="topic"/>
        <name>ID3</name>
    </topic>
    <topic domain="wwww" TID="dce" crdate="20000912">
        <derived-from template="framework"/>
        <name>DCE</name>
        <alias>Distributed Computing Environment</alias>
        <desc><topicref TID="dce"/> is an industry-standard, vendor-neutral set of distributed computing technologies. It provides security services to protect and control access to data, name services that make it easy to find distributed resources, and a highly scalable model for organizing widely scattered users, services, and data. <topicref TID="dce"/> runs on all major computing platforms and is designed to support distributed applications in heterogeneous hardware and software environments.</desc>
    </topic>
    <topic domain="wwww" TID="sdsl" crdate="20000626">
        <derived-from template="dsl"/>
        <name>SDSL</name>
        <alias>Symmetric DSL</alias>
    </topic>
    <topic domain="wwww" TID="hdsl" crdate="20000626">
        <derived-from template="dsl"/>
        <name>HDSL</name>
        <alias>High Bit-Rate DSL</alias>
    </topic>
    <topic domain="wwww" TID="vdsl" crdate="20000626">
        <derived-from template="dsl"/>
        <name>VDSL</name>
        <alias>Very High Bit-Rate DSL</alias>
    </topic>
    <topic domain="wwww" TID="dsl" crdate="20000612">
        <derived-from template="protocol"/>
        <name>DSL</name>
        <alias>Digital Subscriber Line</alias>
        <desc><topicref TID="dsl"/> is a technology for bringing high-bandwidth information to homes and small businesses over ordinary copper <topicref TID="pstn"/> lines. The widely used term xDSL refers to different variations of DSL, such as <topicref TID="adsl"/>, <topicref TID="hdsl"/>, <topicref TID="vdsl"/> and <topicref TID="sdsl"/>. Most <topicref TID="dsl"/> technologies require that a signal splitter be installed at a home or business, requiring the expense of a phone company visit and installation. However, it is possible to manage the splitting remotely, this has been standardized as <topicref TID="glite"/>.</desc>
    </topic>
    <topic domain="wwww" TID="adsl" crdate="20000612">
        <derived-from template="dsl"/>
        <name>ADSL</name>
        <alias>Asymmetric DSL</alias>
    </topic>
    <topic domain="wwww" TID="glite" crdate="20010811">
        <derived-from template="adsl"/>
        <name>G.Lite</name>
    </topic>
    <topic domain="wwww" TID="haxml" crdate="20040218">
        <derived-from template="topic"/>
        <name>HaXml</name>
        <alias>Haskell and XML</alias>
    </topic>
    <topic domain="wwww" TID="fxgrep" crdate="20040218">
        <derived-from template="topic"/>
        <name>fxgrep</name>
    </topic>
    <topic domain="wwww" TID="fxt" crdate="20040218" modate="20060516">
        <derived-from template="topic"/>
        <name>FXT</name>
        <alias>Functional XML Transformation Tool</alias>
    </topic>
    <topic domain="wwww" TID="fxsl" crdate="20040218">
        <derived-from template="topic"/>
        <name>FXSL</name>
        <alias>Functional Programming Library for XSLT</alias>
    </topic>
    <topic domain="wwww" TID="exslt" crdate="20020518">
        <derived-from template="topic"/>
        <name>EXSLT</name>
        <alias>Extensions to XSLT</alias>
    </topic>
    <topic domain="wwww" TID="comega" crdate="20050519">
        <derived-from template="programminglanguage"/>
        <name>C&#x03C9;</name>
        <alias>Comega</alias>
    </topic>
    <topic domain="wwww" TID="e4x" crdate="20050519">
        <derived-from template="programminglanguage"/>
        <name>E4X</name>
        <alias>ECMAScript for XML</alias>
    </topic>
    <topic domain="wwww" TID="xj" crdate="20050519">
        <derived-from template="programminglanguage"/>
        <name>XJ</name>
        <alias>XML for Java</alias>
    </topic>
    <topic domain="wwww" TID="cduce" crdate="20041124">
        <derived-from template="programminglanguage"/>
        <name>CDuce</name>
    </topic>
    <topic domain="wwww" TID="xduce" crdate="20020810">
        <derived-from template="programminglanguage"/>
        <name>XDuce</name>
        <desc><topicref TID="xduce"/> is a typed <topicref TID="programminglanguage"/> that is specifically designed for processing <topicref TID="xml"/>. One can read an <topicref TID="xml"/> document as an <topicref TID="xduce"/> value, extract information from it or convert it to another format, and write out the result value as an <topicref TID="xml"/> document. Since <topicref TID="xduce"/> is statically typed, <topicref TID="xduce"/> programs never yield run-time type errors and the resulting <topicref TID="xml"/> documents always conform to specified types.</desc>
        <status><topicref TID="xduce"/> is more a research project than a <topicref TID="programminglanguage"/> for production-level applications. It has been used as input for the <topicref TID="xquery"/> development process.</status>
    </topic>
    <topic domain="wwww" TID="xl" crdate="20061027">
        <derived-from template="programminglanguage"/>
        <name>XL</name>
        <alias>XML Language</alias>
    </topic>
    <topic domain="wwww" TID="xslt" crdate="20000607">
        <derived-from template="programminglanguage"/>
        <name>XSLT</name>
        <alias>XSL Transformations</alias>
        <desc><topicref TID="xslt"/> is a specialized <topicref TID="programminglanguage"/> for transforming <topicref TID="xml"/> documents. Even though it is part of <topicref TID="xsl"/> and as such intended to be used for transforming <topicref TID="xml"/> documents into <topicref TID="xslfo"/> for presentation purposes, it is not limited to this application area. <topicref TID="xslt"/> uses <topicref TID="xml"/> syntax (i.e., it is a <topicref TID="programminglanguage"/> in <topicref TID="xml"/> syntax), even though it is based on <topicref TID="dsssl"/> (which uses a <topicref TID="lisp"/>-like syntax). <topicref TID="xslt"/> is particularly interesting in <topicref TID="b2b"/> scenarios, where <topicref TID="xml"/> documents must be transformed.</desc>
    </topic>
    <topic domain="wwww" TID="xslt1" crdate="20060629">
        <derived-from template="xslt"/>
        <name>XSLT 1.0</name>
    </topic>
    <topic domain="wwww" TID="xslt2" crdate="20060629">
        <derived-from template="xslt"/>
        <name>XSLT 2.0</name>
    </topic>
    <topic domain="wwww" TID="nitf" crdate="20020629">
        <derived-from template="topic"/>
        <name>NITF</name>
        <alias>News Industry Text Format</alias>
        <desc><topicref TID="nitf"/> uses <topicref TID="xml"/> to define the structure and content of news articles (text and statistical data). It identifies structural pieces such headlines, bylines, paragraphs, table columns and footnotes. The subjects covered by the content may be indicated through the use of <topicref TID="iptc"/> subject codes. Rich in-line markup can be applied to specify such things as organizations, events, places and people. Because metadata tags are applied throughout the news content, <topicref TID="nitf"/> documents are more searchable and useful than <topicref TID="html"/> pages. <topicref TID="nitf"/> documents, like other news data may be contained within, or referenced from, a <topicref TID="newsml"/> wrapper.</desc>
    </topic>
    <topic domain="wwww" TID="aiml" crdate="20020704">
        <derived-from template="topic"/>
        <name>AIML</name>
        <alias>Artificial Intelligence Markup Language</alias>
    </topic>
    <topic domain="wwww" TID="newsml" crdate="20011123">
        <derived-from template="topic"/>
        <name>NewsML</name>
        <alias>News Markup Language</alias>
    </topic>
    <topic domain="wwww" TID="syncml" crdate="20011123">
        <derived-from template="dataformat"/>
        <name>SyncML</name>
    </topic>
    <topic domain="wwww" TID="sla" crdate="20040806">
        <derived-from template="concept"/>
        <name>SLA</name>
        <alias>Service Level Agreement</alias>
        <desc>A <topicref TID="sla"/> is a contract between a service provider and a service consumer about the <topicref TID="qos"/> that will be guaranteed by the service provider.</desc>
    </topic>
    <topic domain="wwww" TID="wsol" crdate="20040806">
        <derived-from template="dataformat"/>
        <name>WSOL</name>
        <alias>Web Service Offerings Language</alias>
    </topic>
    <topic domain="wwww" TID="wsml1" crdate="20040806">
        <derived-from template="dataformat"/>
        <name>WSML</name>
        <alias>Web Services Management Layer</alias>
    </topic>
    <topic domain="wwww" TID="wsml2" crdate="20040806">
        <derived-from template="dataformat"/>
        <name>WSML</name>
        <alias>Web Service Modeling Language</alias>
    </topic>
    <topic domain="wwww" TID="wsml3" crdate="20040806">
        <derived-from template="dataformat"/>
        <name>WSML</name>
        <alias>Web Services Management Language</alias>
    </topic>
    <topic domain="wwww" TID="wsla" crdate="20021217">
        <derived-from template="topic"/>
        <name>WSLA</name>
        <alias>Web Service Level Agreement</alias>
    </topic>
    <topic domain="wwww" TID="wsci" crdate="20020810">
        <derived-from template="topic"/>
        <name>WSCI</name>
        <alias>Web Service Choreography Interface</alias>
    </topic>
    <topic domain="wwww" TID="wscdl" crdate="20040428">
        <derived-from template="topic"/>
        <name>WS-CDL</name>
        <alias>Web Service Choreography Description Language</alias>
    </topic>
    <topic domain="wwww" TID="wscl" crdate="20020810">
        <derived-from template="topic"/>
        <name>WSCL</name>
        <alias>Web Services Conversation Language</alias>
    </topic>
    <topic domain="wwww" TID="wsfl" crdate="20011123">
        <derived-from template="dataformat"/>
        <name>WSFL</name>
        <alias>Web Services Flow Language</alias>
    </topic>
    <topic domain="wwww" TID="xpdl1" crdate="20030220">
        <derived-from template="dataformat"/>
        <name>XPDL</name>
        <alias>XML Processing Description Language</alias>
    </topic>
    <topic domain="wwww" TID="xpdl2" crdate="20030220">
        <derived-from template="dataformat"/>
        <name>XPDL</name>
        <alias>XML Process Definition Language</alias>
    </topic>
    <topic domain="wwww" TID="xlang" crdate="20030220">
        <derived-from template="topic"/>
        <name>XLANG</name>
    </topic>
    <topic domain="wwww" TID="wsil" crdate="20011123">
        <derived-from template="topic"/>
        <name>WSIL</name>
        <alias>Web Services Inspection Language</alias>
    </topic>
    <topic domain="wwww" TID="xmlvs" crdate="20061208">
        <derived-from template="topic"/>
        <name>XMLVS</name>
        <alias>XML Versioning System</alias>
    </topic>
    <topic domain="wwww" TID="grddl" crdate="20040427" modate="20050124">
        <derived-from template="topic"/>
        <name>GRDDL</name>
        <alias>Gleaning Resource Descriptions from Dialects of Languages</alias>
        <desc><topicref TID="grddl"/> is a method for embedding machine-readable data into an <topicref TID="xhtml"/> document. <topicref TID="grddl"/> does not define any specific way of embedding this data, instead it uses <topicref TID="xslt"/> for extracting the information from the <topicref TID="xhtml"/> document and producing <topicref TID="rdf"/>. Using this method, the machine-readable data within the document can use almost any representation, because <topicref TID="grddl"/> applications will always be able to transform this representation into <topicref TID="rdf"/> by transforming the document with the <topicref TID="xslt"/> associated with the document.</desc>
    </topic>
    <topic domain="wwww" TID="rddl" modate="20050124" crdate="20011203">
        <derived-from template="topic"/>
        <name>RDDL</name>
        <alias>Resource Directory Description Language</alias>
        <desc><topicref TID="rddl"/> is a combination of human-readable (by using <topicref TID="xhtml"/>) and machine-readable (by using <topicref TID="xlink"/>) information, designed to provide information about some target. <topicref TID="rddl"/> has been primarily desgined to describe <topicref TID="xmlns"/> by linking from <topicref TID="xmlns"/>' <topicref TID="uri"/>s to any number and type of resources that may be relevant to the <topicref TID="xmlns"/> being described, such as schemas (<topicref TID="dtd"/>s or <topicref TID="xsd"/>s, for example) or documentation.</desc>
        <status>Being based on the unsuccessful <topicref TID="xlink"/> specification, <topicref TID="rddl"/> 1.0 did not get a lot of traction. <topicref TID="rddl"/> 2.0 thus was based on the more successful <topicref TID="rdf"/> specification, but was never finished and has been replaced by <topicref TID="grddl"/> (which is also based on <topicref TID="rdf"/>).</status>
    </topic>
    <topic domain="wwww" TID="wsrp" crdate="20030426">
        <derived-from template="topic"/>
        <name>WSRP</name>
        <alias>Web Services for Remote Portals</alias>
    </topic>
    <topic domain="wwww" TID="wsia" crdate="20030426">
        <derived-from template="topic"/>
        <name>WSIA</name>
        <alias>Web Services for Interactive Applications</alias>
    </topic>
    <topic domain="wwww" TID="wsxl" crdate="20030426">
        <derived-from template="topic"/>
        <name>WSXL</name>
        <alias>Web Services Experience Language</alias>
    </topic>
    <topic domain="wwww" TID="wsmf" crdate="20040629">
        <derived-from template="topic"/>
        <name>WSMF</name>
        <alias>Web Service Modeling Framework</alias>
        <status><topicref TID="wsmf"/> has been used as input for <topicref TID="wsmo"/>, which follows the same philosophy, but uses a more formal approach to modeling.</status>
    </topic>
    <topic domain="wwww" TID="wsmo" crdate="20040629">
        <derived-from template="topic"/>
        <name>WSMO</name>
        <alias>Web Service Modeling Ontology</alias>
    </topic>
    <topic domain="wwww" TID="wsm" crdate="20040629">
        <derived-from template="topic"/>
        <name>WSM</name>
        <alias>Web Service Mediator</alias>
    </topic>
    <topic domain="wwww" TID="wsif" crdate="20040629">
        <derived-from template="topic"/>
        <name>WSIF</name>
        <alias>Web Service Invocation Framework</alias>
    </topic>
    <topic domain="wwww" TID="wsdf" crdate="20040629">
        <derived-from template="topic"/>
        <name>WSDF</name>
        <alias>Web Service Description Framework</alias>
    </topic>
    <topic domain="wwww" TID="pmml" crdate="20040629">
        <derived-from template="topic"/>
        <name>PMML</name>
        <alias>Predictive Model Markup Language</alias>
    </topic>
    <topic domain="wwww" TID="sbml" crdate="20040711">
        <derived-from template="topic"/>
        <name>SBML</name>
        <alias>Systems Biology Markup Language</alias>
    </topic>
    <topic domain="wwww" TID="ruleml" crdate="20040629">
        <derived-from template="topic"/>
        <name>RuleML</name>
        <alias>Rule Markup Language</alias>
    </topic>
    <topic domain="wwww" TID="soapmep" crdate="20040805">
        <derived-from template="topic"/>
        <name>MEP</name>
        <alias>Message Exchange Pattern</alias>
        <desc>A <topicref TID="soap"/> <topicref TID="soapmep"/> is a template that establishes a pattern for the exchange of messages between <topicref TID="soap"/> nodes.</desc>
    </topic>
    <topic domain="wwww" TID="wsdlmep" crdate="20040805">
        <derived-from template="topic"/>
        <name>MEP</name>
        <alias>Message Exchange Pattern</alias>
        <desc><topicref TID="wsdl"/> <topicref TID="wsdlmep"/>s define the sequence and cardinality of abstract messages listed in an operation. <topicref TID="wsdlmep"/>s also define which other nodes send messages to, and receive messages from, the service implementing the operation. <topicref TID="wsdl"/> <topicref TID="wsdlmep"/>s describe the interaction at the abstract (interface) level, which may be distinct from the pattern used by the underlying protocol binding (e.g. <topicref TID="soap"/> <topicref TID="soapmep"/>s).</desc>
    </topic>
    <topic domain="wwww" TID="wsdl" crdate="20011123">
        <derived-from template="topic"/>
        <name>WSDL</name>
        <alias>Web Services Description Language</alias>
    </topic>
    <topic domain="wwww" TID="wrdl" crdate="20061202">
        <derived-from template="topic"/>
        <name>WRDL</name>
        <alias>Web Resource Description Language</alias>
    </topic>
    <topic domain="wwww" TID="ssdl" crdate="20061202">
        <derived-from template="topic"/>
        <name>SSDL</name>
        <alias>SOAP Service Description Language</alias>
    </topic>
    <topic domain="wwww" TID="wdl" crdate="20061202">
        <derived-from template="topic"/>
        <name>WDL</name>
        <alias>Web Description Language</alias>
    </topic>
    <topic domain="wwww" TID="wadl" crdate="20061202">
        <derived-from template="topic"/>
        <name>WADL</name>
        <alias>Web Application Description Language</alias>
    </topic>
    <topic domain="wwww" TID="smil" crdate="20000608">
        <derived-from template="hypermediaformat"/>
        <name>SMIL</name>
        <alias>Synchronized Multimedia Integration Language</alias>
    </topic>
    <topic domain="wwww" TID="lpd" crdate="20020624">
        <derived-from template="topic"/>
        <name>LPD</name>
        <alias>Link Process Definition</alias>
    </topic>
    <topic domain="wwww" TID="fosi" crdate="20020624">
        <derived-from template="topic"/>
        <name>FOSI</name>
        <alias>Formatting Output Specification Instance</alias>
    </topic>
    <topic domain="wwww" TID="xslfo" crdate="20000607" modate="20060629">
        <derived-from template="topic"/>
        <name>XSL-FO</name>
        <alias>XSL Formatting Objects</alias>
        <desc><topicref TID="xslfo"/> is an <topicref TID="xml"/> vocabulary for the formatting of documents. Being part of <topicref TID="xsl"/>, the normal way is to produce <topicref TID="xslfo"/> documents by transforming <topicref TID="xml"/> documents using <topicref TID="xslt1"/>. Even though the principles behind <topicref TID="xsl"/> and <topicref TID="css"/> (the other <topicref TID="stylesheetlanguage"/> created by <topicref TID="w3c"/>) are quite different, it is planned to align the formatting model between <topicref TID="xslfo"/> and <topicref TID="css"/>, so that formatting engines can be based on the same code, both languages can be used to achieve the same results, and formatted results will look identical.</desc>
    </topic>
    <topic domain="wwww" TID="xanadu" crdate="20000614">
        <derived-from template="hmsystem"/>
        <name>Xanadu</name>
        <desc><topicref TID="xanadu"/> is an overall paradigm, an ideal and general model for all computer use, based on sideways connections among documents and files. This paradigm is especially concerned with electronic publishing, but also extends to all forms of storing, presenting and working with information. It is a unifying system of order for all information, non-hierarchical and side-linking, including electronic publishing, personal work, organization of files, corporate work and groupware. All data (for instance, paragraphs of a text document) may be connected sideways and out of sequence to other data (for instance, paragraphs of another text document). This requires new forms of storage, and invites new forms of presentation to show these connections. On a small scale, the paradigm means a model of word processing where comments, outlines and other notes may be stored conceptually adjacent to a document, linked to it sideways. On a large scale, the paradigm means a model of publishing where anyone may quote from and publish links to any already-published document, and any reader may follow these links to and from the document.</desc>
    </topic>
    <topic domain="wwww" TID="hlink" crdate="20020923">
        <derived-from template="metadata"/>
        <name>HLink</name>
    </topic>
    <topic domain="wwww" TID="xlink" crdate="20000607">
        <derived-from template="metadata"/>
        <name>XLink</name>
        <alias>XML Linking Language</alias>
        <desc><topicref TID="xlink"/> defines how to insert links in <topicref TID="xml"/> documents. It specifies a framework making it possible for <topicref TID="xml"/> applications to recognize <topicref TID="xml"/> elements as having link semantics. In addition to the simple, two-ended, unidirectional links which are well-known from <topicref TID="html"/>, <topicref TID="xlink"/> allows more general links, which must not be embedded in the document, can have any number of ends, and can be multidirectional.</desc>
    </topic>
    <topic domain="wwww" TID="ajaxlink" crdate="20061210">
        <derived-from template="product"/>
        <name>AJAXLink</name>
    </topic>
    <topic domain="wwww" TID="ahah" crdate="20070309">
        <derived-from template="product"/>
        <name>AHAH</name>
        <alias>Asychronous HTML and HTTP</alias>
    </topic>
    <topic domain="wwww" TID="its" crdate="20051125">
        <derived-from template="metadata"/>
        <name>ITS</name>
        <alias>Internationalization Tag Set</alias>
    </topic>
    <topic domain="wwww" TID="xll" crdate="20010816">
        <derived-from template="topic"/>
        <name>XLL</name>
        <alias>Extensible Linking Language</alias>
        <status><topicref TID="xll"/> was the term under which the development of <topicref TID="xlink"/> and <topicref TID="xpointer"/> started, referring to both activities as a whole, but it is no longer used.</status>
    </topic>
    <topic domain="wwww" TID="fxpath" crdate="20041021">
        <derived-from template="querylanguage"/>
        <name>FXPath</name>
        <alias>Functional XPath</alias>
    </topic>
    <topic domain="wwww" TID="xdm" crdate="20060305" modate="20060629">
        <derived-from template="datamodel"/>
        <name>XDM</name>
        <alias>XQuery 1.0 and XPath 2.0 Data Model</alias>
        <desc><topicref TID="xdm"/> is the foundation of <topicref TID="xpath2"/> and defines the <topicref TID="datamodel"/> for <topicref TID="xpath2"/> (and consequently <topicref TID="xquery"/> and <topicref TID="xslt2"/>, which are both based on <topicref TID="xpath2"/>). <topicref TID="xdm"/> is built on top of the <topicref TID="xmlinfoset"/> (the abstraction of an <topicref TID="xml"/> document), <topicref TID="psvi"/> (type annotations in the <topicref TID="xmlinfoset"/> as the result of <topicref TID="xsd"/> validation), the simple datatypes of <topicref TID="xsd"/>, and additional concepts. The most important additional concept is that of a "sequence", which embraces both simple datatypes and the <topicref TID="xml"/>-derived nodes.</desc>
    </topic>
    <topic domain="wwww" TID="spath" crdate="20061010">
        <derived-from template="querylanguage"/>
        <name>SPath</name>
        <alias>XML Schema Path Language</alias>
    </topic>
    <topic domain="wwww" TID="xpath" crdate="20000608" modate="20060629">
        <derived-from template="querylanguage"/>
        <name>XPath</name>
        <alias>XML Path Language</alias>
        <desc><topicref TID="xpath"/> is a language for selecting parts of an <topicref TID="xml"/> document. While <topicref TID="xpath"/> is a full-fledged expression language which can be used for arithmetics, string functions and other evaluations, in most cases it is regarded as a way to select parts of an <topicref TID="xml"/> document by selecting nodes which match certain criteria. <topicref TID="xpath"/> can be used as a stand-alone language, but in most cases it is embedded into host languages, the two most important host languages are <topicref TID="xslt"/> and <topicref TID="xsd"/>.</desc>
        <status>The older <topicref TID="xpath1"/> was based on an internally-defined <topicref TID="datamodel"/> (a subset of the <topicref TID="xmlinfoset"/>). The newer <topicref TID="xpath2"/> is based on <topicref TID="xdm"/>, a more complex and externally defined <topicref TID="datamodel"/>. <topicref TID="xpath2"/> is much more powerful than <topicref TID="xpath1"/>, it has a much larget set of built-in functions and supports methods for conditional processing and iterations.</status>
    </topic>
    <topic domain="wwww" TID="xpath1" crdate="20060629">
        <derived-from template="xpath"/>
        <name>XPath 1.0</name>
        <desc><topicref TID="xpath1"/> is based on an internally-defined <topicref TID="datamodel"/> (a subset of the <topicref TID="xmlinfoset"/>).</desc>
    </topic>
    <topic domain="wwww" TID="xpath2" crdate="20060629">
        <derived-from template="xpath"/>
        <name>XPath 2.0</name>
        <desc><topicref TID="xpath2"/> is based on <topicref TID="xdm"/>, a more complex and externally defined <topicref TID="datamodel"/>. <topicref TID="xpath2"/> is much more powerful than <topicref TID="xpath1"/>, it has a much larger set of built-in functions and supports methods for conditional processing and iterations.</desc>
    </topic>
    <topic domain="wwww" TID="tax" crdate="20020210">
        <derived-from template="topic"/>
        <name>TAX</name>
        <alias>Tree Algebra for XML</alias>
    </topic>
    <topic domain="wwww" TID="disarm" crdate="20040102">
        <derived-from template="topic"/>
        <name>DISARM</name>
        <alias>Document Information Set Articulated Reference Model</alias>
    </topic>
    <topic domain="wwww" TID="exis" crdate="20030204">
        <derived-from template="topic"/>
        <name>EXIS</name>
        <alias>Extensible XML Information Set</alias>
    </topic>
    <topic domain="wwww" TID="xmlinfoset" crdate="20000623">
        <derived-from template="datamodel"/>
        <name>XML Infoset</name>
        <alias>XML Information Set</alias>
        <desc>The <topicref TID="xmlinfoset"/> is an abstract <topicref TID="datamodel"/> describing the information available from an <topicref TID="xml"/> document. For many applications, this way of looking at an <topicref TID="xml"/> document is more useful than having to analyze and interpret <topicref TID="xml"/> syntax. <topicref TID="dom"/> describes an <topicref TID="api"/> through which the information in an <topicref TID="xmlinfoset"/> (i.e., the information available from a specific <topicref TID="xml"/> document) can be accessed from different programming languages.</desc>
    </topic>
    <topic domain="wwww" TID="xmlbase" crdate="20000623">
        <derived-from template="topic"/>
        <name>XML Base</name>
    </topic>
    <topic domain="wwww" TID="xindirect" crdate="20050519">
        <derived-from template="topic"/>
        <name>XIndirect</name>
        <alias>XML Indirection Facility</alias>
    </topic>
    <topic domain="wwww" TID="xinclude" crdate="20000623">
        <derived-from template="topic"/>
        <name>XInclude</name>
        <alias>XML Inclusions</alias>
    </topic>
    <topic domain="wwww" TID="xpointer" crdate="20000607">
        <derived-from template="topic"/>
        <name>XPointer</name>
        <alias>XML Pointer Language</alias>
        <desc><topicref TID="xpointer"/> enables addressing into the internal structures of <topicref TID="xml"/> documents. In particular, it provides for specific reference to elements, character strings, and other parts of <topicref TID="xml"/> documents, whether or not they bear an explicit ID attribute. <topicref TID="xpointer"/>s can be used as fragment identifiers in <topicref TID="uri"/> references to specify a more precise sub-resource. Any <topicref TID="uri"/> fragment identifier that points into an <topicref TID="xml"/> resource must be an <topicref TID="xpointer"/>. <topicref TID="xpointer"/> is often used together with <topicref TID="xlink"/>, which specifies how to use hyperlinks with <topicref TID="xml"/>.</desc>
    </topic>
    <topic domain="wwww" TID="eps" crdate="20010314">
        <derived-from template="graphicsformat"/>
        <derived-from template="imageformat"/>
        <name>EPS</name>
        <alias>Encapsulated PostScript</alias>
    </topic>
    <topic domain="wwww" TID="postscript" crdate="20000615">
        <derived-from template="textformat"/>
        <derived-from template="graphicsformat"/>
        <derived-from template="imageformat"/>
        <derived-from template="programminglanguage"/>
        <name>PostScript</name>
        <desc><topicref TID="postscript"/> is an interpreted, stack-based <topicref TID="programminglanguage"/>. Its primary application is to describe the appearance of text, graphics, and images on printed or displayed pages. A program in <topicref TID="postscript"/> can communicate a document description from a composition system to a printing system in a device-independent way. <topicref TID="postscript"/> is an unusually powerful printer language because it is a full programming language, rather than a series of low-level escape sequences. The latest version of <topicref TID="postscript"/>, version 3, fully integrates <topicref TID="pdf"/>.</desc>
    </topic>
    <topic domain="wwww" TID="spdl" crdate="20010730">
        <derived-from template="textformat"/>
        <derived-from template="graphicsformat"/>
        <derived-from template="imageformat"/>
        <derived-from template="programminglanguage"/>
        <name>SPDL</name>
        <alias>Standard Page Description Language</alias>
    </topic>
    <topic domain="wwww" TID="ice" crdate="20000621">
        <derived-from template="topic"/>
        <name>ICE</name>
        <alias>Information and Content Exchange</alias>
    </topic>
    <topic domain="wwww" TID="tcpa" crdate="20040211">
        <derived-from template="consortium"/>
        <name>TCPA</name>
        <alias>Trusted Computing Platform Alliance</alias>
    </topic>
    <topic domain="wwww" TID="tcg" crdate="20040211">
        <derived-from template="consortium"/>
        <name>TCG</name>
        <alias>Trusted Computing Group</alias>
    </topic>
    <topic domain="wwww" TID="gca" crdate="20020716">
        <derived-from template="consortium"/>
        <name>GCA</name>
        <alias>Graphics Communications Association</alias>
    </topic>
    <topic domain="wwww" TID="idealliance" crdate="20000723">
        <derived-from template="consortium"/>
        <name>IDEAlliance</name>
    </topic>
    <topic domain="wwww" TID="xps" crdate="20070716">
        <derived-from template="textformat"/>
        <derived-from template="graphicsformat"/>
        <derived-from template="imageformat"/>
        <name>XPS</name>
        <alias>XML Paper Specification</alias>
    </topic>
    <topic domain="wwww" TID="pdf" crdate="20000612">
        <derived-from template="textformat"/>
        <derived-from template="graphicsformat"/>
        <derived-from template="imageformat"/>
        <name>PDF</name>
        <alias>Portable Document Format</alias>
        <desc><topicref TID="pdf"/> is a <topicref TID="dataformat"/> for representing documents in a manner that is independent of the original application software, hardware, and operating system used to create those documents. A <topicref TID="pdf"/> file can describe documents containing any combination of text, graphics, and images in a device-independent and resolution independent format. The advantage of <topicref TID="pdf"/> over <topicref TID="postscript"/> is the better accessibility of text within <topicref TID="pdf"/> files, which can still be searched for text and can also contain structural information like a table of contents.</desc>
    </topic>
    <topic domain="wwww" TID="pdfe" crdate="20081209">
        <derived-from template="pdf"/>
        <name>PDF/E</name>
    </topic>
    <topic domain="wwww" TID="pdfa" crdate="20081110">
        <derived-from template="pdf"/>
        <name>PDF/A</name>
        <desc><topicref TID="pdfa"/> is not an alternative to <topicref TID="pdf"/>, it is a focused subset of <topicref TID="pdf"/> designed specifically for creating <topicref TID="pdf"/> documents for archival purposes. The most important restrictions defined by <topicref TID="pdfa"/> are disallowing multimedia content such as audio, video, or <topicref TID="javascript"/>, and mandating that all fonts must be embedded.</desc>
    </topic>
    <topic domain="wwww" TID="mars" crdate="20061206">
        <derived-from template="textformat"/>
        <derived-from template="graphicsformat"/>
        <derived-from template="imageformat"/>
        <name>Mars</name>
        <desc><topicref TID="mars"/> is an <topicref TID="xml"/>-friendly representation of <topicref TID="pdf"/> documents. The <topicref TID="mars"/> <topicref TID="dataformat"/> incorporates additional standards such as <topicref TID="svg"/>, <topicref TID="png"/>, <topicref TID="jpeg"/>, <topicref TID="jpeg2000"/>, <topicref TID="opentype"/>, <topicref TID="xpath"/>, and <topicref TID="xml"/> into a <topicref TID="zip"/>-based document container.</desc>
    </topic>
    <topic domain="wwww" TID="pdfx" crdate="20020518">
        <derived-from template="pdf"/>
        <name>PDF/X</name>
        <desc><topicref TID="pdfx"/> is not an alternative to <topicref TID="pdf"/>, it is a focused subset of <topicref TID="pdf"/> designed specifically for reliable prepress data interchange.</desc>
    </topic>
    <topic domain="wwww" TID="egp" crdate="20000912">
        <derived-from template="routingprotocol"/>
        <name>EGP</name>
        <alias>Exterior Gateway Protocol</alias>
    </topic>
    <topic domain="wwww" TID="bgp" crdate="20000912">
        <derived-from template="routingprotocol"/>
        <name>BGP</name>
        <alias>Border Gateway Protocol</alias>
    </topic>
    <topic domain="wwww" TID="igp" crdate="20000912">
        <derived-from template="routingprotocol"/>
        <name>IGP</name>
        <alias>Interior Gateway Protocol</alias>
    </topic>
    <topic domain="wwww" TID="rip" crdate="20000912">
        <derived-from template="routingprotocol"/>
        <name>RIP</name>
        <alias>Routing Information Protocol</alias>
    </topic>
    <topic domain="wwww" TID="dvmrp" crdate="20010305">
        <derived-from template="routingprotocol"/>
        <name>DVMRP</name>
        <alias>Distance-Vector Multicast Routing Protocol</alias>
    </topic>
    <topic domain="wwww" TID="pim" crdate="20010305">
        <derived-from template="routingprotocol"/>
        <name>PIM</name>
        <alias>Protocol-Independent Multicast</alias>
    </topic>
    <topic domain="wwww" TID="mospf" crdate="20010305">
        <derived-from template="routingprotocol"/>
        <name>MOSPF</name>
        <alias>Multicast Open Shortest Path First</alias>
    </topic>
    <topic domain="wwww" TID="pnni" crdate="20050124">
        <derived-from template="routingprotocol"/>
        <name>PNNI</name>
        <alias>Private Network-to-Network Interface</alias>
    </topic>
    <topic domain="wwww" TID="ospf" crdate="20000912">
        <derived-from template="routingprotocol"/>
        <name>OSPF</name>
        <alias>Open Shortest Path First</alias>
    </topic>
    <topic domain="wwww" TID="html" crdate="20000607">
        <derived-from template="hypertextformat"/>
        <name>HTML</name>
        <alias>Hypertext Markup Language</alias>
        <desc><topicref TID="html"/> is a simple markup language used to create hypertext documents that are platform independent. <topicref TID="html"/> documents are <topicref TID="sgml"/> documents with generic semantics that are appropriate for representing information from a wide range of domains. For example, <topicref TID="html"/> markup can represent <topicref TID="usenetnews"/>, <topicref TID="email"/>, documentation, menus of options, database query results, simple structured documents with in-lined images, and hypertext views of existing bodies of information.</desc>
    </topic>
    <topic domain="wwww" TID="mhtml" crdate="20001214">
        <derived-from template="hypertextformat"/>
        <name>MHTML</name>
        <alias>MIME HTML</alias>
    </topic>
    <topic domain="wwww" TID="ucd" crdate="20030612">
        <derived-from template="topic"/>
        <name>UCD</name>
        <alias>Unicode Character Database</alias>
    </topic>
    <topic domain="wwww" TID="nfc" crdate="20021217">
        <derived-from template="topic"/>
        <name>NFC</name>
        <alias>Normalization Form C</alias>
    </topic>
    <topic domain="wwww" TID="nfd" crdate="20021217">
        <derived-from template="topic"/>
        <name>NFD</name>
        <alias>Normalization Form D</alias>
    </topic>
    <topic domain="wwww" TID="nfkc" crdate="20021217">
        <derived-from template="topic"/>
        <name>NFKC</name>
        <alias>Normalization Form KC</alias>
    </topic>
    <topic domain="wwww" TID="nfkd" crdate="20021217">
        <derived-from template="topic"/>
        <name>NFKD</name>
        <alias>Normalization Form KD</alias>
    </topic>
    <topic domain="wwww" TID="bom1" crdate="20010919">
        <derived-from template="topic"/>
        <name>BOM</name>
        <alias>Byte Order Mark</alias>
    </topic>
    <topic domain="wwww" TID="wicd" crdate="20051221">
        <derived-from template="hypertextformat"/>
        <name>WICD</name>
        <alias>Web Integration Compound Docuument</alias>
    </topic>
    <topic domain="wwww" TID="xhtml" crdate="20000607">
        <derived-from template="hypertextformat"/>
        <name>XHTML</name>
        <alias>Extensible Hypertext Markup Language</alias>
        <desc><topicref TID="xhtml"/> is a reformulation of <topicref TID="html"/> in <topicref TID="xml"/>. <topicref TID="html"/> is based on <topicref TID="sgml"/> and uses some features of <topicref TID="sgml"/> which are not available in <topicref TID="xml"/> (most notably, markup minimization), and consequently <topicref TID="html"/> documents typically are not valid <topicref TID="xml"/> documents. <topicref TID="xhtml"/> redefines <topicref TID="html"/> as an <topicref TID="xml"/> <topicref TID="dtd"/>, and also gives some recommendations how to use the markup in order to make <topicref TID="xhtml"/> compatible with older browsers, which only understand <topicref TID="html"/> (and thus may have problems processing <topicref TID="xml"/> syntax, for example the special form of empty elements).</desc>
    </topic>
    <topic domain="wwww" TID="xhtmlmp" crdate="20060525">
        <derived-from template="hypertextformat"/>
        <name>XHTML-MP</name>
        <alias>XHTML Mobile Profile</alias>
    </topic>
    <topic domain="wwww" TID="ipaddress" crdate="20010309">
        <derived-from template="topic"/>
        <name>IP address</name>
    </topic>
    <topic domain="wwww" TID="idn" crdate="20030411">
        <derived-from template="topic"/>
        <name>IDN</name>
        <alias>Internationalized Domain Name</alias>
    </topic>
    <topic domain="wwww" TID="fqdn" crdate="20000912">
        <derived-from template="topic"/>
        <name>FQDN</name>
        <alias>Fully Qualified Domain Name</alias>
        <desc>A <topicref TID="fqdn"/> is a domain name that includes all higher level domains relevant to the entity named.</desc>
    </topic>
    <topic domain="wwww" TID="fqhn" crdate="20000912">
        <derived-from template="fqdn"/>
        <derived-from template="ipaddress"/>
        <name>FQHN</name>
        <alias>Fully Qualified Host Name</alias>
        <desc>A <topicref TID="fqhn"/> is either the <topicref TID="fqdn"/> of a host (i.e., a completely specified domain name ending in a <topicref TID="tld"/>), or the numeric <topicref TID="ipaddress"/> of a host.</desc>
    </topic>
    <topic domain="wwww" TID="unicode" modate="20030123" crdate="20000607">
        <derived-from template="ccs"/>
        <name>Unicode</name>
        <desc><topicref TID="unicode"/> defines a 31-bit character set. <topicref TID="unicode"/> is closely aligned with <topicref TID="ucs"/>. The most commonly used characters, including all those found in older encoding standards, have been placed in one of the first 65534 positions (0x0000 to 0xFFFD). This 16-bit subset is called the <topicref TID="isobmp"/> or "Plane 0". The characters that were later added outside the 16-bit <topicref TID="isobmp"/> are mostly for specialist applications such as historic scripts and scientific notation. New characters are still being added on a continuous basis, but the existing characters will not be changed any more and are stable. <topicref TID="unicode"/> assigns to each character not only a code number but also an official name. A hexadecimal number that represents a <topicref TID="unicode"/> or <topicref TID="ucs"/> value is commonly preceded by "U+" as in U+0041 for the character "Latin capital letter A". The <topicref TID="unicode"/> characters U+0000 to U+007F are identical to those in <topicref TID="ascii"/>, and the range U+0000 to U+00FF is identical to <topicref TID="iso88591"/>.</desc>
    </topic>
    <topic domain="wwww" TID="dhtml" crdate="20000607">
        <derived-from template="clientsidetechnology"/>
        <name>DHTML</name>
        <alias>Dynamic HTML</alias>
        <desc><topicref TID="dhtml"/> does not refer to a specific version or a specific feature of <topicref TID="html"/>. It is an expression which is commonly used to refer to all features of <topicref TID="html"/> which go beyond the presentation of static documents. The most popular mechanisms which are encompassed by the term <topicref TID="dhtml"/> are <topicref TID="css"/>, scripts (in most cases <topicref TID="ecmascript"/>-based languages, embedded with the &lt;SCRIPT> element), and objects (embedded with the &lt;OBJECT> element). <topicref TID="dhtml"/> also often refers to <topicref TID="browser"/>-specific extensions of particular mechanisms, such as extensions to the basic scripting methods, or the ability to dynamically download fonts. The "glue" between the different components which make up <topicref TID="dhtml"/> (mainly <topicref TID="html"/>, <topicref TID="css"/>, and a scripting language) is provided by <topicref TID="dom"/>.</desc>
    </topic>
    <topic domain="wwww" TID="ajax" crdate="20050918">
        <derived-from template="riaruntime"/>
        <name>AJAX</name>
        <alias>Asynchronous JavaScript and XML</alias>
    <desc><topicref TID="ajax"/> refers to the principle of using scripting to interact with an <topicref TID="httpserver"/> at some time other than the usual page navigation (initiated by clicking a link). Combined with <topicref TID="dhtml"/> techniques, <topicref TID="ajax"/> can update parts of an <topicref TID="html"/> document without having to reload the complete document. <topicref TID="ajax"/> can provide a better user experience, because the traditional scheme of  <topicref TID="www"/> navigation can be extended to provide users with a more direct feedback. <topicref TID="ajax"/> allows classical desktop application interactions such as drag&amp;drop and auto-completion.</desc>
    </topic>
    <topic domain="wwww" TID="ria" crdate="20061206">
        <derived-from template="clientsidetechnology"/>
        <name>RIA</name>
        <alias>Rich Internet Application</alias>
        <desc><topicref TID="ria"/>s are applications which go beyond the basic scheme of <topicref TID="www"/> applications of presenting static pages which users can navigate by following links. <topicref TID="ria"/>s aim at providing users with a richer interface experience, this can be more traditional <topicref TID="dhtml"/>, or the newer <topicref TID="ajax"/> approach. In both cases, a <topicref TID="clientsidetechnology"/> is used to provide better feedback to the user, trying to get the user experience of a <topicref TID="browser"/>-based application closer to that of a desktop application.</desc>
    </topic>
    <topic domain="wwww" TID="xschema" crdate="20000823">
        <derived-from template="topic"/>
        <name>XSchema</name>
    </topic>
    <topic domain="wwww" TID="grove" crdate="20020806">
        <derived-from template="concept"/>
        <name>GROVE</name>
        <alias>Graph Representation of Property Values</alias>
    </topic>
    <topic domain="wwww" TID="esis" crdate="20011219">
        <derived-from template="concept"/>
        <name>ESIS</name>
        <alias>Element Structure Information Set</alias>
    </topic>
    <topic domain="wwww" TID="ubl" crdate="20020902">
        <derived-from template="dataformat"/>
        <name>UBL</name>
        <alias>Universal Business Language</alias>
    </topic>
    <topic domain="wwww" TID="ddml" modate="20030214" crdate="20000823">
        <derived-from template="xmlschemalanguage"/>
        <name>DDML</name>
        <alias>Document Definition Markup Language</alias>
    </topic>
    <topic domain="wwww" TID="yaml" crdate="20020902">
        <derived-from template="dataformat"/>
        <name>YAML</name>
        <alias>YAML Ain't Markup Language</alias>
    </topic>
    <topic domain="wwww" TID="websgml" crdate="20010321">
        <derived-from template="dataformat"/>
        <name>WebSGML</name>
        <desc>The <topicref TID="sgml"/> standard has been updated with two annexes which add some corrections as well as new features to <topicref TID="sgml"/> making some specifications possible which are desirable for using <topicref TID="sgml"/> as the basis for <topicref TID="html"/> and <topicref TID="xml"/>. Basically, the <topicref TID="websgml"/> extensions allow a number of additional features to be defined in an <topicref TID="sgml"/> declaration and <topicref TID="dtd"/>. However, when using these features in an <topicref TID="sgml"/> environment, it is necessary that both the generator and the interpreter of a document are capable of processing the <topicref TID="websgml"/> extensions, since a conforming <topicref TID="sgml"/> implementation does not have to implement the <topicref TID="websgml"/> extensions.</desc>
    </topic>
    <topic domain="wwww" TID="sgml" crdate="20000607">
        <derived-from template="dataformat"/>
        <name>SGML</name>
        <alias>Standard Generalized Markup Language</alias>
        <desc><topicref TID="sgml"/> is a markup language for structured documents. Being the foundation for <topicref TID="html"/>, <topicref TID="sgml"/> today is the most frequently used language for structuring documents. The rules for how documents of a certain type may be structured are specified in a <topicref TID="dtd"/>, and every application of <topicref TID="sgml"/> (such as <topicref TID="html"/>) defines such a <topicref TID="dtd"/>. Even though <topicref TID="sgml"/> has been very successful, it is also rather complex and contains a lot of obscure features which are rarely used (and implemented). Thus, when a new language for replacing <topicref TID="html"/> on the <topicref TID="www"/> was needed, rather than directly taking <topicref TID="sgml"/>, a functional subset of <topicref TID="sgml"/> was defined, which has become known under the name of <topicref TID="xml"/>.</desc>
    </topic>
    <topic domain="wwww" TID="dsssl" crdate="20000607">
        <derived-from template="stylesheetlanguage"/>
        <name>DSSSL</name>
        <alias>Document Style Semantics and Specification Language</alias>
        <desc><topicref TID="dsssl"/> is an international standard for specifying document transformation and formatting in a platform- and vendor-neutral manner. <topicref TID="dsssl"/> can be used with any document format for which a property set can be defined according to the <topicref TID="hytime"/> standard. In particular, <topicref TID="dsssl"/> can be used to specify the presentation of documents marked up according to <topicref TID="sgml"/>. <topicref TID="dsssl"/> consists of two main components, a transformation language and a style language. The transformation language is used to specify structural transformations on <topicref TID="sgml"/> source files. The transformation language can also be used to specify the merging of two or more documents, the generation of indexes and tables of contents, and other operations.</desc>
    </topic>
    <topic domain="wwww" TID="dsssllite" crdate="20010811">
        <derived-from template="dsssl"/>
        <name>DSSSL-Lite</name>
        <desc><topicref TID="dsssllite"/> was an early approach to define a profile (i.e., a functional subset) of <topicref TID="dsssl"/> in an attempt to create a version of <topicref TID="dsssl"/> which is less complex and still powerful enough to be sufficient for a large number of applications. <topicref TID="dsssllite"/> never became an actual standard, but the work on it was used as input for the <topicref TID="dssslo"/> activity.</desc>
    </topic>
    <topic domain="wwww" TID="dssslo" crdate="20010811">
        <derived-from template="dsssl"/>
        <name>DSSSL-O</name>
        <alias>DSSSL-Online</alias>
        <desc>Based on results from the <topicref TID="dsssllite"/> activity, <topicref TID="dssslo"/> was an attempt to define a profile (i.e., a functional subset) of <topicref TID="dsssl"/>. This profile should be less complex than full <topicref TID="dsssl"/> and particularly suited to the needs of online publishing. <topicref TID="dssslo"/> never became an actual standard, but it was used as the base for <topicref TID="xsl"/>, which is used as the style sheet language for <topicref TID="xml"/> documents.</desc>
    </topic>
    <topic domain="wwww" TID="pptp" crdate="20020629">
        <derived-from template="protocol"/>
        <name>PPTP</name>
        <alias>Point to Point Tunneling Protocol</alias>
    </topic>
    <topic domain="wwww" TID="l2tp" crdate="20040711">
        <derived-from template="protocol"/>
        <name>L2TP</name>
        <alias>Layer Two Tunneling Protocol</alias>
    </topic>
    <topic domain="wwww" TID="pppoe" crdate="20040711">
        <derived-from template="protocol"/>
        <name>PPPoE</name>
        <alias>PPP over Ethernet</alias>
    </topic>
    <topic domain="wwww" TID="ppp" crdate="20000608">
        <derived-from template="protocol"/>
        <name>PPP</name>
        <alias>Point to Point Protocol</alias>
        <desc><topicref TID="ppp"/> is designed for simple links which transport packets between two peers. These links provide full-duplex simultaneous bi-directional operation, and are assumed to deliver packets in order. Although <topicref TID="ppp"/> is not tied to a particular type of packets it transports, its most common use is the encapsulation of <topicref TID="ip"/> packages over <topicref TID="modem"/> lines. Basically, <topicref TID="ppp"/> is similar to <topicref TID="slip"/>, but it has the advantages of not being limited to one type of <topicref TID="protocol"/> it can transport, a configuration negotiation phase at the start of a connection (for determining connection configuration parameters automatically), and the possibility to use standardized <topicref TID="authentication"/> procedures for automated login. The two authentication schemes supported by <topicref TID="ppp"/> are <topicref TID="pap"/> and <topicref TID="chap"/>.</desc>
    </topic>
    <topic domain="wwww" TID="slip" crdate="20000608">
        <derived-from template="protocol"/>
        <name>SLIP</name>
        <alias>Serial Line Internet Protocol</alias>
        <desc><topicref TID="slip"/> is a packet framing <topicref TID="protocol"/>, it defines a sequence of characters that frame <topicref TID="ip"/> packets on a serial line. It provides no addressing, packet type identification, error detection/correction, or compression mechanisms. It is used for the same purpose as <topicref TID="ppp"/>, which is the encapsulation of <topicref TID="ip"/> packages over <topicref TID="modem"/> lines. <topicref TID="slip"/> does not have <topicref TID="ppp"/>'s configuration negotiation or <topicref TID="authentication"/> schemes, which can make the configuration of <topicref TID="slip"/> connections more complicated.</desc>
    </topic>
    <topic domain="wwww" TID="flute" crdate="20041021">
        <derived-from template="protocol"/>
        <name>FLUTE</name>
        <alias>File Delivery over Unidirectional Transport</alias>
    </topic>
    <topic domain="wwww" TID="alc" crdate="20041021">
        <derived-from template="protocol"/>
        <name>ALC</name>
        <alias>Asynchronous Layered Coding</alias>
    </topic>
    <topic domain="wwww" TID="lct" crdate="20041021">
        <derived-from template="protocol"/>
        <name>LCT</name>
        <alias>Layered Coding Transport</alias>
    </topic>
    <topic domain="wwww" TID="fec" crdate="20041021">
        <derived-from template="concept"/>
        <name>FEC</name>
        <alias>Forward Error Correction</alias>
    </topic>
    <topic domain="wwww" TID="whois" crdate="20041021">
        <derived-from template="protocol"/>
        <name>WHOIS</name>
    </topic>
    <topic domain="wwww" TID="smtp" crdate="20000607">
        <derived-from template="emailprotocol"/>
        <name>SMTP</name>
        <alias>Simple Mail Transfer Protocol</alias>
        <desc><topicref TID="smtp"/> is used to pass <topicref TID="email"/> messages between <topicref TID="internet"/> <topicref TID="server"/>s. Each message has a standardized header that is used to identify <topicref TID="email"/> address(es) of the person(s) the message is to be sent to, the <topicref TID="email"/> address and name of the sender (to whom responses can be sent automatically), and details of those nodes on the network through which the message passed. A number of extensions to <topicref TID="smtp"/> have been defined yielding <topicref TID="esmtp"/>, which is mostly in use today.</desc>
    </topic>
    <topic domain="wwww" TID="esmtp" crdate="20010315">
        <derived-from template="emailprotocol"/>
        <name>ESMTP</name>
        <alias>Extended SMTP</alias>
        <desc><topicref TID="esmtp"/> describes a framework for extensions of <topicref TID="smtp"/>. <topicref TID="smtp"/> still provides the basic mechanism for exchanging <topicref TID="email"/> messages, but it has become apparent that it lacks some important functionality. Instead of defining a revised but static new version of <topicref TID="smtp"/>, <topicref TID="esmtp"/> defines a mechanism how extensions can be integrated into the basic <topicref TID="protocol"/>, and how these extensions can be used in an interoperable way.</desc>
    </topic>
    <topic domain="wwww" TID="apop" crdate="20010903">
        <derived-from template="emailprotocol"/>
        <name>APOP</name>
        <alias>Authenticated Post Office Protocol</alias>
    </topic>
    <topic domain="wwww" TID="pop" crdate="20000607">
        <derived-from template="emailprotocol"/>
        <name>POP</name>
        <alias>Post Office Protocol</alias>
        <desc><topicref TID="pop"/> allows a <topicref TID="client"/> computer to retrieve <topicref TID="email"/> from a <topicref TID="pop"/> <topicref TID="server"/>. It does not provide support for sending <topicref TID="email"/>, which is assumed to be done via <topicref TID="smtp"/> or some other method. <topicref TID="pop"/> is useful for computers without a permanent <topicref TID="network"/> connection which therefore require a "post office" (the <topicref TID="pop"/> <topicref TID="server"/>) to hold their <topicref TID="email"/> until they can retrieve it. <topicref TID="pop"/> is older and less powerful than <topicref TID="imap"/>, which is used for the same application area.</desc>
    </topic>
    <topic domain="wwww" TID="icmp" crdate="20000608">
        <derived-from template="protocol"/>
        <name>ICMP</name>
        <alias>Internet Control Message Protocol</alias>
        <desc><topicref TID="icmp"/> is at the same <topicref TID="protocol"/> layer as <topicref TID="ip"/>, its purpose is to transmit information needed to control <topicref TID="ip"/> traffic. It is used mainly to provide information about routes to destination addresses. <topicref TID="icmp"/> redirect messages inform hosts about more accurate routes to other systems, whereas <topicref TID="icmp"/> unreachable messages indicate problems with a route. Additionally, <topicref TID="icmp"/> can cause <topicref TID="tcp"/> connections to terminate gracefully if the route becomes unavailable. The ping command is a commonly-used <topicref TID="icmp"/>-based service.</desc>
    </topic>
    <topic domain="wwww" TID="nis" crdate="20000829">
        <derived-from template="directory"/>
        <name>NIS</name>
        <alias>Network Information System</alias>
    </topic>
    <topic domain="wwww" TID="slp" crdate="20001213">
        <derived-from template="protocol"/>
        <name>SLP</name>
        <alias>Service Location Protocol</alias>
    </topic>
    <topic domain="wwww" TID="smb" crdate="20000911">
        <derived-from template="dfs"/>
        <name>SMB</name>
        <alias>Server Message Block</alias>
    </topic>
    <topic domain="wwww" TID="afs" crdate="20001220">
        <derived-from template="dfs"/>
        <name>AFS</name>
        <alias>Andrew File System</alias>
    </topic>
    <topic domain="wwww" TID="port" crdate="20020629">
        <derived-from template="concept"/>
        <name>Port</name>
        <desc>While <topicref TID="ip"/> makes it possible for two systems to exchange datagrams in a heterogeneous network environment, it does not support the identification of different processes on these systems. <topicref TID="tcp"/> and <topicref TID="udp"/> as the transport <topicref TID="protocol"/>s of the <topicref TID="internet"/> thus introduce the concept of a <topicref TID="port"/>, which addresses a specific process on a system. <topicref TID="port"/> numbers are 16-bit numbers, which are included in <topicref TID="tcp"/> or <topicref TID="udp"/> packets and are used to address a specific process on a system.</desc>
    </topic>
    <topic domain="wwww" TID="gateway" crdate="20020628" modate="20030108">
        <derived-from template="concept"/>
        <name>Gateway</name>
        <desc>A <topicref TID="gateway" /> is a device that connects networks segments on any layer higher than the network layer of the network (typically on the application layer). Related to <topicref TID="gateway" />s are <topicref TID="repeater" />s, <topicref TID="bridge" />s, and <topicref TID="router" />s, which also connect network segments, but on different layers of the networking architecture.</desc>
    </topic>
    <topic domain="wwww" TID="router" crdate="20020628" modate="20030108">
        <derived-from template="concept"/>
        <name>Router</name>
        <desc>A <topicref TID="router" /> is a device that connects networks segments on the network layer of the network. Related to <topicref TID="router" />s are <topicref TID="repeater" />s, <topicref TID="bridge" />s, and <topicref TID="gateway" />s, which also connect network segments, but on different layers of the networking architecture.</desc>
    </topic>
    <topic domain="wwww" TID="bridge" crdate="20020628" modate="20030108">
        <derived-from template="concept"/>
        <name>Bridge</name>
        <desc>A <topicref TID="bridge" /> is a device that connects networks segments on the data link layer of the network. Related to <topicref TID="bridge" />s are <topicref TID="repeater" />s, <topicref TID="router" />s, and <topicref TID="gateway" />s, which also connect network segments, but on different layers of the networking architecture.</desc>
    </topic>
    <topic domain="wwww" TID="repeater" crdate="20020628" modate="20030108">
        <derived-from template="concept"/>
        <name>Repeater</name>
        <desc>A <topicref TID="repeater" /> is a device that connects networks segments on the physical layer of the network. Related to <topicref TID="repeater" />s are <topicref TID="bridge" />s, <topicref TID="router" />s, and <topicref TID="gateway" />s, which also connect network segments, but on different layers of the networking architecture.</desc>
    </topic>
    <topic domain="wwww" TID="firewall" crdate="20020628">
        <derived-from template="gateway"/>
        <name>Firewall</name>
        <desc>A <topicref TID="firewall"/> is a special kind of <topicref TID="gateway"/> that is used to block certain types of network traffic (typically, network traffic that is potentially dangerous). Most <topicref TID="firewall"/>s work as packet filters, comparing the passing packets to a set of filter rules. Typically, the comparison performed by the packet filter involves the source address, the source <topicref TID="port"/>, the destination address, and the destination <topicref TID="port"/>. Filtering on source and destination addresses grants control over who may communicate with the internal network. All traffic from undesirable networks can be screened out. <topicref TID="port"/>s, on the other hand, are used to distinguish network services. By filtering out a <topicref TID="port"/>, it is possible to deny the outside world access to a service offered on the internal network.</desc>
    </topic>
    <topic domain="wwww" TID="proxy" crdate="20020628">
        <derived-from template="gateway"/>
        <name>Proxy</name>
        <desc>A <topicref TID="proxy"/> is a special kind of <topicref TID="gateway"/>, acting like a <topicref TID="server"/> when being accessed by a <topicref TID="client"/>. However, instead of servicing a request from a <topicref TID="client"/>, the <topicref TID="proxy"/> forwards the request to a <topicref TID="server"/>, waits for the <topicref TID="server"/>'s response, and then sends it back to the <topicref TID="client"/>. A <topicref TID="proxy"/> is often combined with other typical <topicref TID="gateway"/> functionality, such as <topicref TID="firewall"/> or <topicref TID="cache"/>.</desc>
    </topic>
    <topic domain="wwww" TID="httpproxy" crdate="20010317">
        <derived-from template="proxy"/>
        <derived-from template="httpserver"/>
        <derived-from template="httpclient"/>
        <name>HTTP Proxy</name>
        <desc>In the context of the <topicref TID="www"/>, an <topicref TID="httpproxy"/> is an intermediary program which acts as both an <topicref TID="httpserver"/> and an <topicref TID="httpclient"/>, receiving a request from a <topicref TID="client"/> (in most cases a <topicref TID="browser"/>) and then acting as an <topicref TID="httpclient"/> and making requests on behalf of other <topicref TID="httpclient"/>s. However, requests to an <topicref TID="httpproxy"/> can also be serviced internally, for example if the <topicref TID="httpproxy"/> uses its <topicref TID="cache"/> instead of sending a request to the origin <topicref TID="httpserver"/>. In order to use an <topicref TID="httpproxy"/>, the <topicref TID="httpclient"/>'s request has to be explicitly addressed to the <topicref TID="httpproxy"/>, which then sends a request to the origin <topicref TID="httpserver"/>. An <topicref TID="httpproxy"/> may also perform a protocol conversion, for example a <topicref TID="browser"/> may send an <topicref TID="http"/> request to the <topicref TID="httpproxy"/> referencing an <topicref TID="ftp"/> resource, and the <topicref TID="httpproxy"/> then acts as <topicref TID="ftp"/> <topicref TID="client"/> to retrieve the resource from the <topicref TID="ftp"/> <topicref TID="server"/> using <topicref TID="ftp"/>, and eventually the resource is sent back from the <topicref TID="httpproxy"/> to the <topicref TID="browser"/> using <topicref TID="http"/>.</desc>
    </topic>
    <topic domain="wwww" TID="cache" crdate="20020405">
        <derived-from template="concept"/>
        <name>Cache</name>
    </topic>
    <topic domain="wwww" TID="nfs" crdate="20000829">
        <derived-from template="dfs"/>
        <name>NFS</name>
        <alias>Network File System</alias>
    </topic>
    <topic domain="wwww" TID="sfs" crdate="20020702">
        <derived-from template="dfs"/>
        <name>SFS</name>
        <alias>Self-certifying File System</alias>
    </topic>
    <topic domain="wwww" TID="cap" crdate="20000829">
        <derived-from template="protocol"/>
        <name>CAP</name>
        <alias>Calendar Access Protocol</alias>
    </topic>
    <topic domain="wwww" TID="acap" crdate="20000829">
        <derived-from template="protocol"/>
        <name>ACAP</name>
        <alias>Application Configuration Access Protocol</alias>
    </topic>
    <topic domain="wwww" TID="icalendar" crdate="20020811">
        <derived-from template="dataformat"/>
        <name>iCalendar</name>
        <alias>iCal</alias>
    </topic>
    <topic domain="wwww" TID="itip" crdate="20000829">
        <derived-from template="protocol"/>
        <name>iTIP</name>
        <alias>iCalendar Transport-Independent Interoperability Protocol</alias>
    </topic>
    <topic domain="wwww" TID="imip" crdate="20000829">
        <derived-from template="protocol"/>
        <name>iMIP</name>
        <alias>iCalendar Message-Based Interoperability Protocol</alias>
    </topic>
    <topic domain="wwww" TID="imap" crdate="20000607">
        <derived-from template="emailprotocol"/>
        <name>IMAP</name>
        <alias>Internet Message Access Protocol</alias>
        <desc><topicref TID="imap"/> is a <topicref TID="emailprotocol"/> allowing a <topicref TID="client"/> to access and manipulate <topicref TID="email"/> messages on a <topicref TID="server"/>. It permits manipulation of remote message folders (mailboxes) in a way that is functionally equivalent to local mailboxes. <topicref TID="imap"/> includes operations for creating, deleting, and renaming mailboxes; checking for new messages; permanently removing messages; searching; and selective fetching of message attributes, texts, and portions thereof. It does not specify a means of posting mail; this function is handled by a mail transfer protocol such as <topicref TID="smtp"/>. <topicref TID="imap"/> is newer and more powerful than <topicref TID="pop"/>, which is used for the same application area.</desc>
    </topic>
    <topic domain="wwww" TID="tftp" crdate="20010309">
        <derived-from template="protocol"/>
        <name>TFTP</name>
        <alias>Trivial File Transfer Protocol</alias>
    </topic>
    <topic domain="wwww" TID="ftp" crdate="20000608">
        <derived-from template="protocol"/>
        <name>FTP</name>
        <alias>File Transfer Protocol</alias>
        <desc><topicref TID="ftp"/> is a <topicref TID="protocol"/> for file transfer between hosts on the <topicref TID="internet"/>. The primary function of <topicref TID="ftp"/> is to transfer files efficiently and reliably among hosts and to allow the convenient use of remote file storage capabilities. The objectives of <topicref TID="ftp"/> are to promote sharing of files (computer programs and/or data), to encourage indirect or implicit (via programs) use of remote computers, to shield users from variations in file storage systems among hosts, and to transfer data reliably and efficiently. <topicref TID="ftp"/>, though usable directly by a user at a terminal, is designed mainly for use by programs.</desc>
    </topic>
    <topic domain="wwww" TID="bind" crdate="20010811">
        <derived-from template="product"/>
        <name>BIND</name>
        <alias>Berkeley Internet Name Domain</alias>
        <desc><topicref TID="bind"/> implements an <topicref TID="internet"/> name server. It consists of a server and a resolver library. <topicref TID="bind"/> is an implementation of <topicref TID="dns"/>, both <topicref TID="server"/> and <topicref TID="client"/>. Development of <topicref TID="bind"/> is funded by the <topicref TID="isc"/>. <topicref TID="bind"/> has been ported to <topicref TID="windows"/> and <topicref TID="vms"/>, but is most often found on <topicref TID="unix"/>. <topicref TID="bind"/> source code is freely available and very complex; most of the development on the <topicref TID="dns"/> <topicref TID="protocol"/>s is based on this code; and most <topicref TID="unix"/> vendors ship <topicref TID="bind"/>-derived <topicref TID="dns"/> implementations. As a result, the <topicref TID="bind"/> name server is the most widely used name server on the <topicref TID="internet"/>.</desc>
    </topic>
    <topic domain="wwww" TID="twopc" crdate="20040806">
        <derived-from template="protocol"/>
        <name>2PC</name>
        <alias>Two-Phase Commit</alias>
        <desc>A <topicref TID="twopc"/> <topicref TID="protocol"/> is used for implementing distributed transactions. It consists of a prepare phase (where the coordinator asks all peers to prepare for the completion phase and to cast votes, and then collects the answers) and a completion phase (where the transaction is either commited or aborted depending on the outcome of the prepare phase).</desc>
    </topic>
    <topic domain="wwww" TID="acid" crdate="20040806">
        <derived-from template="concept"/>
        <name>ACID</name>
        <alias>Atomicity, Consistency, Isolation, Durability</alias>
        <desc><topicref TID="acid"/> properties for transactions are required in most <topicref TID="dbms"/>s. However, <topicref TID="acid"/> properties for transactions alone do not guarantee a reliable <topicref TID="dbms"/>, other factors such as reliability of the operating environment and backup strategies are also very important.</desc>
    </topic>
    <topic domain="core" TID="normalform" crdate="20040707" modate="20060305">
        <derived-from template="datamodel"/>
        <derived-from template="dataformat"/>
        <name>Normal Form</name>
        <desc>A <topicref TID="normalform"/> is a special subset of a given <topicref TID="datamodel"/> or <topicref TID="dataformat"/> that satisfies some constraints which are not necessary for the unnormalized form of the <topicref TID="datamodel"/> or <topicref TID="dataformat"/>. Because there can be different sets of constraints for a <topicref TID="datamodel"/> or <topicref TID="dataformat"/>, there can be different <topicref TID="normalform"/>s for a <topicref TID="datamodel"/> or <topicref TID="dataformat"/>.</desc>
    </topic>
    <topic domain="wwww" TID="xnf" crdate="20031127" modate="20040707">
        <derived-from template="normalform"/>
        <name>XNF</name>
        <alias>XML Normal Form</alias>
    </topic>
    <topic domain="wwww" TID="nfnf" crdate="20060220">
        <derived-from template="normalform"/>
        <name>NF&#xB2;</name>
        <alias>Non-First Normal Form</alias>
    </topic>
    <topic domain="wwww" TID="firstnf" crdate="20040707">
        <derived-from template="normalform"/>
        <name>1NF</name>
        <alias>First Normal Form</alias>
    </topic>
    <topic domain="wwww" TID="secondnf" crdate="20040707">
        <derived-from template="normalform"/>
        <name>2NF</name>
        <alias>Second Normal Form</alias>
    </topic>
    <topic domain="wwww" TID="thirdnf" crdate="20040707">
        <derived-from template="normalform"/>
        <name>3NF</name>
        <alias>Third Normal Form</alias>
    </topic>
    <topic domain="wwww" TID="fourthnf" crdate="20040707">
        <derived-from template="normalform"/>
        <name>4NF</name>
        <alias>Fourth Normal Form</alias>
    </topic>
    <topic domain="wwww" TID="fifthnf" crdate="20040707">
        <derived-from template="normalform"/>
        <name>5NF</name>
        <alias>Fifth Normal Form</alias>
    </topic>
    <topic domain="wwww" TID="sixthnf" crdate="20040707">
        <derived-from template="normalform"/>
        <name>6NF</name>
        <alias>Sixth Normal Form</alias>
    </topic>
    <topic domain="wwww" TID="dknf" crdate="20041106">
        <derived-from template="normalform"/>
        <name>DK/NF</name>
        <alias>Domain-Key Normal Form</alias>
    </topic>
    <topic domain="wwww" TID="bcnf" crdate="20040707">
        <derived-from template="normalform"/>
        <name>BCNF</name>
        <alias>Boyce-Codd Normal Form</alias>
    </topic>
    <topic domain="wwww" TID="xns" crdate="20030211">
        <derived-from template="topic"/>
        <name>XNS</name>
        <alias>Extensible Name Service</alias>
    </topic>
    <topic domain="wwww" TID="enum" crdate="20050218">
        <derived-from template="directory"/>
        <name>ENUM</name>
        <alias>E.164 Number Mapping</alias>
    </topic>
    <topic domain="wwww" TID="dns" crdate="20000607">
        <derived-from template="directory"/>
        <name>DNS</name>
        <alias>Domain Name System</alias>
        <desc><topicref TID="dns"/> is a distributed, replicated, data query service mainly used on the <topicref TID="internet"/> for translating host names to <topicref TID="ipaddress"/>es. The three main components of <topicref TID="dns"/> are: the domain name space and resource records, which are specifications for a <topicref TID="tree"/> structured name space and data associated with the names; name servers, which are server programs which hold information about the domain <topicref TID="tree"/>'s structure and set information; and resolvers, being programs that extract information from name servers in response to client requests.</desc>
    </topic>
    <topic domain="wwww" TID="gprs" crdate="20000614">
        <derived-from template="protocol"/>
        <name>GPRS</name>
        <alias>General Packet Radio Service</alias>
        <desc><topicref TID="gprs"/> represents the first implementation of packet switching within The <topicref TID="gsm"/>, which is essentially a circuit-switched technology. Using <topicref TID="gprs"/> will enable users to send and receive data at speeds up to 115kbit/s. <topicref TID="gprs"/> is very efficient in its use of scarce spectrum resources and enables <topicref TID="gprs"/> operators to introduce a wide range of value added services. <topicref TID="gprs"/> is ideal for bursty data applications such as <topicref TID="email"/> or <topicref TID="internet"/> access, and can also enable "virtual permanent connections" to data sources, allowing information to arrive rather than being sought. This cannot be achieved using standard circuit-switched networks.</desc>
    </topic>
    <topic domain="wwww" TID="aim" crdate="20000822">
        <derived-from template="imsystem"/>
        <name>AIM</name>
        <alias>AOL Instant Messenger</alias>
    </topic>
    <topic domain="wwww" TID="icq" crdate="20000822">
        <derived-from template="imsystem"/>
        <name>ICQ</name>
    </topic>
    <topic domain="wwww" TID="irc" crdate="20000822">
        <derived-from template="imsystem"/>
        <name>IRC</name>
        <alias>Internet Relay Chat</alias>
    </topic>
    <topic domain="wwww" TID="hscsd" crdate="20000614">
        <derived-from template="protocol"/>
        <name>HSCSD</name>
        <alias>High Speed Circuit Switched Data</alias>
    </topic>
    <topic domain="wwww" TID="radius" crdate="20060412">
        <derived-from template="topic"/>
        <name>RADIUS</name>
        <alias>Remote Authentication Dial In User Service</alias>
    </topic>
    <topic domain="wwww" TID="ussd" crdate="20030611">
        <derived-from template="imsystem"/>
        <name>USSD</name>
        <alias>Unstructured Supplementary Service Data</alias>
    </topic>
    <topic domain="wwww" TID="sms" crdate="20000614">
        <derived-from template="imsystem"/>
        <name>SMS</name>
        <alias>Short Message Service</alias>
        <desc>The <topicref TID="gsm"/> <topicref TID="sms"/> is a very simple service for transmitting short messages (140 octets of user data) over the <topicref TID="gsm"/> network. It has become a very popular service for mobile phone users. The <topicref TID="ems"/> and <topicref TID="mms"/> technologies have been designed to become the predecessors of <topicref TID="sms"/>.</desc>
    </topic>
    <topic domain="wwww" TID="ems" crdate="20010824">
        <derived-from template="imsystem"/>
        <name>EMS</name>
        <alias>Enhanced Message Service</alias>
    </topic>
    <topic domain="wwww" TID="mmap" crdate="20030128">
        <derived-from template="protocol"/>
        <name>MMAP</name>
        <alias>Mobile Message Access Protocol</alias>
    </topic>
    <topic domain="wwww" TID="mms" crdate="20010824">
        <derived-from template="imsystem"/>
        <name>MMS</name>
        <alias>Multimedia Message Service</alias>
    </topic>
    <topic domain="wwww" TID="edge" crdate="20000614">
        <derived-from template="topic"/>
        <name>EDGE</name>
        <alias>Enhanced Data Rates for GSM Evolution</alias>
    <desc><topicref TID="edge"/> is a technology for transmitting data over a <topicref TID="gsm"/> mobile phone network. <topicref TID="edge"/> provides up to three times the data capacity of <topicref TID="gprs"/>. Using <topicref TID="edge"/>, operators can handle three times more subscribers than <topicref TID="gprs"/>; triple their data rate per subscriber, or add extra capacity to their voice communications. <topicref TID="edge"/> uses the same <topicref TID="tdma"/> frame structure, logic channel and 200kHz carrier bandwidth as today's <topicref TID="gsm"/> networks, which allows it to be overlaid directly onto an existing <topicref TID="gsm"/> network.</desc>
    </topic>
    <topic domain="wwww" TID="imt2000" crdate="20000626">
        <derived-from template="wlinterface"/>
        <name>IMT-2000</name>
        <alias>International Mobile Telecommunications-2000</alias>
    </topic>
    <topic domain="wwww" TID="uwcc" crdate="20000828">
        <derived-from template="topic"/>
        <name>UWCC</name>
        <alias>Universal Wireless Communications Consortium</alias>
    </topic>
    <topic domain="wwww" TID="twain" crdate="20000920">
        <derived-from template="api"/>
        <name>TWAIN</name>
    </topic>
    <topic domain="wwww" TID="sdma" crdate="20000920">
        <derived-from template="multiplex"/>
        <name>SDMA</name>
        <alias>Space Division Multiple Access</alias>
    </topic>
    <topic domain="wwww" TID="fdma" crdate="20000920">
        <derived-from template="multiplex"/>
        <name>FDMA</name>
        <alias>Frequency Division Multiple Access</alias>
    </topic>
    <topic domain="wwww" TID="tdma" crdate="20000828">
        <derived-from template="multiplex"/>
        <name>TDMA</name>
        <alias>Time Division Multiple Access</alias>
    </topic>
    <topic domain="wwww" TID="cdma" crdate="20000828">
        <derived-from template="multiplex"/>
        <name>CDMA</name>
        <alias>Code Division Multiple Access</alias>
    </topic>
    <topic domain="wwww" TID="wcdma" crdate="20030615">
        <derived-from template="multiplex"/>
        <name>WCDMA</name>
        <alias>Wideband Code Division Multiple Access</alias>
    </topic>
    <topic domain="wwww" TID="umts" crdate="20000614">
        <derived-from template="wlinterface"/>
        <name>UMTS</name>
        <alias>Universal Mobile Telecommunications System</alias>
    </topic>
    <topic domain="wwww" TID="rtp" crdate="20000614">
        <derived-from template="protocol"/>
        <name>RTP</name>
        <alias>Real Time Protocol</alias>
        <desc><topicref TID="rtp"/> provides end-to-end network transport functions suitable for applications transmitting real-time data, such as audio, video, or simulation data, over multicast or unicast network services. <topicref TID="rtp"/> does not address resource reservation and does not guarantee quality-of-service for real-time services. The data transport is augmented by a control protocol (<topicref TID="rtcp"/>) to allow monitoring of the data delivery in a manner scalable to large multicast networks, and to provide minimal control and identification functionality. <topicref TID="rtp"/> and <topicref TID="rtcp"/> are designed to be independent of the underlying transport and network layers.</desc>
    </topic>
    <topic domain="wwww" TID="srtp" crdate="20040711">
        <derived-from template="protocol"/>
        <name>SRTP</name>
        <alias>Secure Real Time Protocol</alias>
    </topic>
    <topic domain="wwww" TID="epp" crdate="20040711">
        <derived-from template="protocol"/>
        <name>EPP</name>
        <alias>Extensible Provisioning Protocol</alias>
    </topic>
    <topic domain="wwww" TID="scip" crdate="20040809">
        <derived-from template="protocol"/>
        <name>SCIP</name>
        <alias>Simple Conference Invitation Protocol</alias>
    </topic>
    <topic domain="wwww" TID="ss7" crdate="20040809">
        <derived-from template="protocol"/>
        <name>SS7</name>
        <alias>Signaling System 7</alias>
        <desc><topicref TID="ss7"/> defines the procedures and <topicref TID="protocol"/> by which network elements in a <topicref TID="pstn"/> exchange information over a digital signaling network to effect wireless (cellular) and wireline call setup, routing and control.</desc>
    </topic>
    <topic domain="wwww" TID="h323" crdate="20040824">
        <derived-from template="protocol"/>
        <name>H.323</name>
        <status>Mostly recognized as a <topicref TID="voip"/> <topicref TID="protocol"/>, <topicref TID="h323"/> competes with <topicref TID="sip"/>. <topicref TID="sip"/> is more successful because it is easier to use and implement.</status>
    </topic>
    <topic domain="wwww" TID="sip" crdate="20040809">
        <derived-from template="protocol"/>
        <name>SIP</name>
        <alias>Session Initiation Protocol</alias>
    </topic>
    <topic domain="wwww" TID="sdp" crdate="20040824">
        <derived-from template="protocol"/>
        <name>SDP</name>
        <alias>Session Description Protocol</alias>
    </topic>
    <topic domain="wwww" TID="ipx" crdate="20000911">
        <derived-from template="protocol"/>
        <name>IPX</name>
        <alias>Internetwork Packet Exchange</alias>
    </topic>
    <topic domain="wwww" TID="rtcp" crdate="20000614">
        <derived-from template="protocol"/>
        <name>RTCP</name>
        <alias>Real Time Control Protocol</alias>
        <desc><topicref TID="rtcp"/> is the control <topicref TID="protocol"/> that works in conjunction with <topicref TID="rtp"/>. <topicref TID="rtcp"/> control packets are periodically transmitted by each participant in an <topicref TID="rtp"/> session to all other participants. Feedback of information to the application can be used to control performance and for diagnostic purposes.</desc>
    </topic>
    <topic domain="wwww" TID="rtsp" crdate="20000614">
        <derived-from template="protocol"/>
        <name>RTSP</name>
        <alias>Real Time Streaming Protocol</alias>
        <desc><topicref TID="rtsp"/> is an application-level <topicref TID="protocol"/> for control over the delivery of data with real-time properties. <topicref TID="rtsp"/> provides an extensible framework to enable controlled, on-demand delivery of real-time data, such as audio and video. Sources of data can include both live data feeds and stored clips. <topicref TID="rtsp"/> is intended to control multiple data delivery sessions, provide a means for choosing delivery channels such as <topicref TID="udp"/>, multicast UDP and <topicref TID="tcp"/>, and use delivery mechanisms based upon <topicref TID="rtp"/>.</desc>
    </topic>
    <topic domain="wwww" TID="udplite" crdate="20040711">
        <derived-from template="protocol"/>
        <name>UDP-Lite</name>
        <alias>Lightweight UDP</alias>
        <desc><topicref TID="udplite"/> is a <topicref TID="protocol"/> which can deliver partially damaged data. <topicref TID="udplite"/> provides a checksum with an optional partial coverage. When using this option, a packet is divided into a sensitive part (covered by the checksum) and an insensitive part (not covered by the checksum). Errors in the insensitive part will not cause the packet to be discarded by the transport layer at the receiving end host. When the checksum covers the entire packet, which should be the default, <topicref TID="udplite"/> is semantically identical to <topicref TID="udp"/>.</desc>
    </topic>
    <topic domain="wwww" TID="udp" crdate="20000607">
        <derived-from template="protocol"/>
        <name>UDP</name>
        <alias>User Datagram Protocol</alias>
        <desc><topicref TID="udp"/> is a transport <topicref TID="protocol"/> that provides a simple but unreliable datagram service. <topicref TID="udp"/> neither guarantees delivery nor does it require a connection. As a result, it is lightweight and efficient, but all error processing and retransmission must be taken care of by the application program. Like <topicref TID="tcp"/>, which is the <topicref TID="internet"/>'s other important transport <topicref TID="protocol"/>, <topicref TID="udp"/> is layered on top of <topicref TID="ip"/>.</desc>
    </topic>
    <topic domain="wwww" TID="ttcp" crdate="20020810">
        <derived-from template="protocol"/>
        <name>T/TCP</name>
        <alias>TCP for Transactions</alias>
    </topic>
    <topic domain="wwww" TID="sctp" crdate="20020611" modate="20091105">
        <derived-from template="protocol"/>
        <name>SCTP</name>
        <alias>Stream Control Transmission Protocol</alias>
    </topic>
    <topic domain="wwww" TID="tcp" crdate="20000607">
        <derived-from template="protocol"/>
        <name>TCP</name>
        <alias>Transmission Control Protocol</alias>
        <desc><topicref TID="tcp"/> is intended for use as a highly reliable transport <topicref TID="protocol"/> between hosts in packet-switched computer communication <topicref TID="network"/>s, and in interconnected systems of such <topicref TID="network"/>s. <topicref TID="tcp"/> is a flow-controlled, connection-oriented, end-to-end reliable <topicref TID="protocol"/> designed to fit into a layered hierarchy of <topicref TID="protocol"/>s supporting multi-network applications. <topicref TID="tcp"/> provides for reliable interprocess communications between pairs of processes in host computers attached to distinct but interconnected computer communication <topicref TID="network"/>s. Very few assumptions are made as to the reliability of the communication <topicref TID="protocol"/>s below the <topicref TID="tcp"/> layer. <topicref TID="tcp"/> assumes it can obtain a simple, potentially unreliable, datagram service from the lower level <topicref TID="protocol"/>s, usually <topicref TID="ip"/>. <topicref TID="tcp"/> is able to operate above a wide spectrum of communication systems, ranging from hard-wired connections to packet-switched or circuit-switched networks.</desc>
    </topic>
    <topic domain="wwww" TID="cnrp" crdate="20000810">
        <derived-from template="resprotocol"/>
        <name>CNRP</name>
        <alias>Common Name Resolution Protocol</alias>
    </topic>
    <topic domain="wwww" TID="cpim" crdate="20040103">
        <derived-from template="protocol"/>
        <name>CPIM</name>
        <alias>Common Presence and Instant Messaging</alias>
    </topic>
    <topic domain="wwww" TID="xmpp" crdate="20040103">
        <derived-from template="protocol"/>
        <name>XMPP</name>
        <alias>Extensible Messaging and Presence Protocol</alias>
    </topic>
    <topic domain="wwww" TID="amqp" crdate="20070831">
        <derived-from template="protocol"/>
        <name>AMQP</name>
        <alias>Advanced Message Queuing Protocol</alias>
    </topic>
    <topic domain="wwww" TID="s5" crdate="20041116" modate="20060524">
        <derived-from template="dataformat"/>
        <name>S&#x2075;</name>
        <alias>Simple Standards-Based Slide Show System</alias>
    </topic>
    <topic domain="wwww" TID="slidy" crdate="20060524">
        <derived-from template="dataformat"/>
        <name>Slidy</name>
    </topic>
    <topic domain="wwww" TID="xipr" crdate="20060818" modate="20070309">
        <derived-from template="xincludeprocessor"/>
        <name>XIPr</name>
        <alias>XInclude Processor</alias>
    </topic>
    <topic domain="wwww" TID="xslidy" crdate="20060608">
        <derived-from template="dataformat"/>
        <name>XSLidy</name>
    </topic>
    <topic domain="wwww" TID="impp" crdate="20000816">
        <derived-from template="protocol"/>
        <name>IMPP</name>
        <alias>Instant Messaging and Presence Protocol</alias>
    </topic>
    <topic domain="wwww" TID="vpp" crdate="20000816">
        <derived-from template="protocol"/>
        <name>VPP</name>
        <alias>Virtual Presence Protocol</alias>
    </topic>
    <topic domain="wwww" TID="bloat" crdate="20020415">
        <derived-from template="protocol"/>
        <name>BLOAT</name>
        <alias>Binary Lexical Octet Ad-hoc Transport</alias>
    </topic>
    <topic domain="wwww" TID="upp" crdate="20000804">
        <derived-from template="topic"/>
        <name>UPP</name>
        <alias>Universal Payment Preamble</alias>
    </topic>
    <topic domain="wwww" TID="eiaj" crdate="20020805">
        <derived-from template="organization"/>
        <name>EIAJ</name>
        <alias>Electronic Industries Association of Japan</alias>
        <status>On <text date="20001101"/>, <topicref TID="eiaj"/> and <topicref TID="jeida"/> merged to form <topicref TID="jeita"/>.</status>
    </topic>
    <topic domain="wwww" TID="jeita" crdate="20020805">
        <derived-from template="organization"/>
        <name>JEITA</name>
        <alias>Japan Electronics and Information Technology Industries Association</alias>
    </topic>
    <topic domain="wwww" TID="ciffforum" crdate="20040405">
        <derived-from template="organization"/>
        <name>CIFF Forum</name>
    </topic>
    <topic domain="wwww" TID="jeida" modate="20020805" crdate="20000913">
        <derived-from template="organization"/>
        <name>JEIDA</name>
        <alias>Japan Electronic Industry Development Association</alias>
        <status>On <text date="20001101"/>, <topicref TID="eiaj"/> and <topicref TID="jeida"/> merged to form <topicref TID="jeita"/>.</status>
    </topic>
    <topic domain="wwww" TID="iim" crdate="20050418">
        <derived-from template="metadata"/>
        <name>IIM</name>
        <alias>Information Interchange Model</alias>
    </topic>
    <topic domain="wwww" TID="exif" modate="20040405" crdate="20000913">
        <derived-from template="imageformat"/>
        <name>Exif</name>
        <alias>Exchangeable Image File Format</alias>
        <desc>Many digital cameras store images using <topicref TID="exif"/> compressed files. <topicref TID="exif"/> compressed files use <topicref TID="jpeg"/> for <topicref TID="imagecompression"/>. This means the image data can be read by any application supporting <topicref TID="jpeg"/> (uncompressed <topicref TID="exif"/> uses the <topicref TID="tiff"/> format). In addition, <topicref TID="exif"/> stores <topicref TID="metadata"/> within application segments at the beginning of the file, and uses <topicref TID="srgb"/> as the default color space. It is recommended that <topicref TID="exif"/> image files should be named and arranged in directories according to the <topicref TID="dcf"/> specification.</desc>
    </topic>
    <topic domain="wwww" TID="jar" crdate="20010312">
        <derived-from template="dataformat"/>
        <name>JAR</name>
        <alias>Java Archive</alias>
        <desc><topicref TID="jar"/> is a platform-independent <topicref TID="dataformat"/> that aggregates many files into one. Multiple <topicref TID="java"/> <topicref TID="applet"/>s and their requisite components (class files, images, and sounds) can be bundled in a <topicref TID="jar"/> file and subsequently downloaded to a <topicref TID="browser"/> in a single <topicref TID="http"/> transaction, improving the download speed. The <topicref TID="jar"/> format also supports compression, which reduces the file size, further improving the download time. In addition, the <topicref TID="applet"/> author can digitally sign individual entries in a <topicref TID="jar"/> file to authenticate their origin.</desc>
    </topic>
    <topic domain="wwww" TID="ciff" modate="20040405" crdate="20000913">
        <derived-from template="imageformat"/>
        <name>CIFF</name>
        <alias>Camera Image File Format</alias>
        <status><topicref TID="ciff"/> is not in use anymore and is replaced by <topicref TID="dcf"/> and <topicref TID="exif"/>.</status>
    </topic>
    <topic domain="wwww" TID="sdds" crdate="20020709">
        <derived-from template="moviesound"/>
        <name>SDDS</name>
        <alias>Sony Dynamic Digital Sound</alias>
    </topic>
    <topic domain="wwww" TID="ac3" crdate="20020709">
        <derived-from template="moviesound"/>
        <name>Dolby Digital</name>
        <alias>AC-3</alias>
    </topic>
    <topic domain="wwww" TID="fiveone" crdate="20051212">
        <derived-from template="surroundsound"/>
        <name>5.1</name>
    </topic>
    <topic domain="wwww" TID="sixone" crdate="20051212">
        <derived-from template="surroundsound"/>
        <name>6.1</name>
    </topic>
    <topic domain="wwww" TID="sevenone" crdate="20051212">
        <derived-from template="surroundsound"/>
        <name>7.1</name>
    </topic>
    <topic domain="wwww" TID="dts" crdate="20020605">
        <derived-from template="moviesound"/>
        <name>DTS</name>
        <alias>Digital Theater Systems</alias>
    </topic>
    <topic domain="wwww" TID="thx" crdate="20020605">
        <derived-from template="topic"/>
        <name>THX</name>
        <desc><topicref TID="thx"/> defines a set of guidelines for audio and picture playback for movie theatres. Often confused with <topicref TID="moviesound"/>s, <topicref TID="thx"/> does not define standards for audio coding, it only defines the presentation standards that must be met during movie playback. Any <topicref TID="moviesound"/> may be used, as long as it provides the standards set by <topicref TID="thx"/>.</desc>
    </topic>
    <topic domain="wwww" TID="dpof" crdate="20010115">
        <derived-from template="topic"/>
        <name>DPOF</name>
        <alias>Digital Print Order Format</alias>
    </topic>
    <topic domain="wwww" TID="dcf2" crdate="20020622">
        <derived-from template="textformat"/>
        <name>DCF</name>
        <alias>Document Composition Facility</alias>
    </topic>
    <topic domain="wwww" TID="troff" crdate="20020622">
        <derived-from template="textformat"/>
        <name>troff</name>
    </topic>
    <topic domain="wwww" TID="nroff" crdate="20020622">
        <derived-from template="textformat"/>
        <name>nroff</name>
    </topic>
    <topic domain="wwww" TID="dcf" crdate="20000913">
        <derived-from template="lfs"/>
        <name>DCF</name>
        <alias>Design Rule for Camera File System</alias>
    </topic>
    <topic domain="wwww" TID="jepi" crdate="20000804">
        <derived-from template="topic"/>
        <name>JEPI</name>
        <alias>Joint Electronic Payments Initiative</alias>
    </topic>
    <topic domain="wwww" TID="htcp" crdate="20030219">
        <derived-from template="protocol"/>
        <name>HTCP</name>
        <alias>Hypertext Caching Protocol</alias>
    </topic>
    <topic domain="wwww" TID="pep" crdate="20000804">
        <derived-from template="protocol"/>
        <name>PEP</name>
        <alias>Protocol Extension Protocol</alias>
    </topic>
    <topic domain="wwww" TID="httpef" crdate="20000804">
        <derived-from template="protocol"/>
        <name>HTTP Extension Framework</name>
        <desc><topicref TID="http"/> is being used for an increasing number of applications involving distributed authoring, collaboration, printing, and various <topicref TID="rpc"/>-like <topicref TID="protocol"/>s. The <topicref TID="httpef"/> is an extension mechanism for <topicref TID="http"/> designed to address the tension between private agreement and public specification, and to accommodate extension of <topicref TID="httpclient"/>s and <topicref TID="httpserver"/>s by software components.</desc>
    </topic>
    <topic domain="wwww" TID="ddds" crdate="20000824">
        <derived-from template="topic"/>
        <name>DDDS</name>
        <alias>Dynamic Delegation Discovery System</alias>
    </topic>
    <topic domain="wwww" TID="ip" crdate="20000607">
        <derived-from template="protocol"/>
        <name>IP</name>
        <alias>Internet Protocol</alias>
        <desc><topicref TID="ip"/> is specifically limited in scope to provide the functions necessary to deliver a package of bits (an <topicref TID="internet"/> datagram) from a source to a destination over an interconnected system of networks. There are no mechanisms to augment end-to-end data reliability, flow control, sequencing, or other services commonly found in host-to-host <topicref TID="protocol"/>s. In most cases, <topicref TID="tcp"/> is used on top of <topicref TID="ip"/>.</desc>
    </topic>
    <topic domain="wwww" TID="ipv4" crdate="20010312">
        <derived-from template="ip"/>
        <name>IPv4</name>
        <alias>Internet Protocol Version 4</alias>
    </topic>
    <topic domain="wwww" TID="ipv6" crdate="20010312">
        <derived-from template="ip"/>
        <name>IPv6</name>
        <alias>Internet Protocol Version 6</alias>
        <desc><topicref TID="ipv6"/> is a new version of <topicref TID="ip"/> which is designed to be an evolutionary step from <topicref TID="ipv4"/> (commonly referred to simply as <topicref TID="ip"/>). It can be installed as a normal software upgrade in <topicref TID="internet"/> devices and is interoperable with the current <topicref TID="ipv4"/>. Its deployment strategy was designed to not have any "flag" days. <topicref TID="ipv6"/> is designed to run well on high performance networks (e.g., <topicref TID="atm"/>) and at the same time is still efficient for low bandwidth networks (e.g., <topicref TID="wlinterface"/>s). In addition, it provides a platform for new <topicref TID="internet"/> functionality (such as resource reservation capabilities) that will be required in the near future.</desc>
    </topic>
    <topic domain="wwww" TID="ipsec" crdate="20010815">
        <derived-from template="topic"/>
        <name>IPsec</name>
        <alias>IP Security Protocol</alias>
    </topic>
    <topic domain="wwww" TID="ipcomp" crdate="20010815">
        <derived-from template="topic"/>
        <name>IPcomp</name>
        <alias>IP Payload Compression</alias>
    </topic>
    <topic domain="wwww" TID="ike" crdate="20010815">
        <derived-from template="topic"/>
        <name>IKE</name>
        <alias>Internet Key Exchange</alias>
    </topic>
    <topic domain="wwww" TID="ah" crdate="20010815">
        <derived-from template="topic"/>
        <name>AH</name>
        <alias>Authentication Header</alias>
    </topic>
    <topic domain="wwww" TID="esp" crdate="20010815">
        <derived-from template="topic"/>
        <name>ESP</name>
        <alias>Encapsulating Security Payload</alias>
    </topic>
    <topic domain="wwww" TID="ipng" crdate="20000804">
        <derived-from template="topic"/>
        <name>IPng</name>
        <alias>Internet Protocol next generation</alias>
        <desc>Although <topicref TID="ip"/> is the most visible <topicref TID="protocol"/> of the <topicref TID="internet"/>, there are many other <topicref TID="protocol"/>s which are also part of the <topicref TID="internet"/> architecture and which also have to be changed when making the transition from <topicref TID="ipv4"/> to <topicref TID="ipv6"/>. In the context of <topicref TID="ipv6"/>, there are also a number of protocols which are new to the <topicref TID="internet"/> architecture. The common practice is to use the term <topicref TID="ipng"/> to refer to all protocols which have to be changed or added when switching to <topicref TID="ipv6"/>.</desc>
    </topic>
    <topic domain="wwww" TID="thttp" crdate="20010815">
        <derived-from template="protocol"/>
        <name>THTTP</name>
        <alias>Trivial HTTP</alias>
    </topic>
    <topic domain="wwww" TID="phttp" crdate="20020810">
        <derived-from template="protocol"/>
        <name>P-HTTP</name>
        <alias>Persistent HTTP</alias>
        <status><topicref TID="phttp"/> was one important step in the development of <topicref TID="http"/>/1.1. The concepts of <topicref TID="phttp"/> were incorporated in <topicref TID="http"/>/1.1, so that <topicref TID="phttp"/> itself is not relevant anymore.</status>
    </topic>
    <topic domain="wwww" TID="http" crdate="20000607">
        <derived-from template="protocol"/>
        <name>HTTP</name>
        <alias>Hypertext Transfer Protocol</alias>
        <desc><topicref TID="http"/> is the protocol used for information exchange on the <topicref TID="www"/>. <topicref TID="http"/> defines how messages are formatted and transmitted, and what actions a <topicref TID="httpserver"/> and an <topicref TID="httpclient"/> (which in most cases is a <topicref TID="browser"/>) should take in response to various messages. <topicref TID="http"/> uses a reliable, connection-oriented transport service such as the <topicref TID="tcp"/>. <topicref TID="http"/> is a stateless <topicref TID="protocol"/>, where each request is interpreted independently, without any knowledge of the requests that came before it.</desc>
        <status>The current version of <topicref TID="http"/> (version 1.1) implements persistent connections (taken from <topicref TID="phttp"/>) and pipelining in order to use one transport connection for multiple request/response interactions.</status>
    </topic>
    <topic domain="wwww" TID="whttp" crdate="20060525">
        <derived-from template="protocol"/>
        <name>W-HTTP</name>
        <alias>Wireless HTTP</alias>
    </topic>
    <topic domain="wwww" TID="httpr" crdate="20021217">
        <derived-from template="protocol"/>
        <name>HTTPR</name>
        <alias>Reliable HTTP</alias>
    </topic>
    <topic domain="wwww" TID="https" crdate="20000607">
        <derived-from template="protocol"/>
        <name>HTTPS</name>
        <alias>HTTP over SSL</alias>
        <desc><topicref TID="https"/> is a secure way of using <topicref TID="http"/>. <topicref TID="http"/> provides almost no security features, it contains only basic <topicref TID="authentication"/> mechanisms, and no support for privacy. <topicref TID="https"/> solves this problem by replacing <topicref TID="http"/>'s transport layer, the insecure <topicref TID="tcp"/>, with <topicref TID="ssl"/>, a secure transport layer. In the near future, <topicref TID="ssl"/> will probably be replaced by the more general <topicref TID="tls"/> protocol, but it is very unlikely that the already established name of <topicref TID="https"/> will be changed to reflect this change.</desc>
    </topic>
    <topic domain="wwww" TID="httpsec" crdate="20060524">
        <derived-from template="protocol"/>
        <name>HTTPsec</name>
    </topic>
    <topic domain="wwww" TID="shttp" crdate="20000608">
        <derived-from template="protocol"/>
        <name>S-HTTP</name>
        <alias>Secure Hypertext Transfer Protocol</alias>
        <desc><topicref TID="shttp"/> is an extension of <topicref TID="http"/> providing independently applicable security services for transaction confidentiality, authenticity/integrity and non-repudiability of origin. The protocol emphasizes maximum flexibility in choice of key management mechanisms, security policies and cryptographic <topicref TID="algorithm"/>s by supporting option negotiation between parties for each transaction. Message protection can be provided on three orthogonal axes: signature, <topicref TID="authentication"/>, and <topicref TID="encryption"/>. Any message may be signed, authenticated, encrypted, or any combination of these (including no protection). Several cryptographic message format standards may be incorporated into <topicref TID="shttp"/> clients and servers, particularly, but in principle not limited to, <topicref TID="pkcs7"/> and <topicref TID="pem"/>. <topicref TID="shttp"/>-aware clients can communicate with <topicref TID="shttp"/>-oblivious servers and vice-versa. Cryptographic <topicref TID="algorithm"/>s supported by <topicref TID="shttp"/> include <topicref TID="des"/>, two-key and three-key <topicref TID="tripledes"/>, <topicref TID="desx"/>, <topicref TID="idea"/>, <topicref TID="rc2"/>, and <topicref TID="cdmf"/>.</desc>
    </topic>
    <topic domain="wwww" TID="cpp" crdate="20050519">
        <derived-from template="topic"/>
        <name>CPP</name>
        <alias>Common Profile for Presence</alias>
    </topic>
    <topic domain="wwww" TID="ccpp" crdate="20000920">
        <derived-from template="topic"/>
        <name>CC/PP</name>
        <alias>Composite Capabilities/Preferences Profiles</alias>
    </topic>
    <topic domain="wwww" TID="cdmf" crdate="20010305">
        <derived-from template="topic"/>
        <name>CDMF</name>
        <alias>Commercial Data Masking Facility</alias>
    </topic>
    <topic domain="wwww" TID="pagerank" crdate="20040714">
        <derived-from template="algorithm"/>
        <name>PageRank</name>
    </topic>
    <topic domain="wwww" TID="pem" crdate="20000612">
        <derived-from template="topic"/>
        <name>PEM</name>
        <alias>Privacy Enhanced Mail</alias>
    </topic>
    <topic domain="wwww" TID="idea" crdate="20000612">
        <derived-from template="skc"/>
        <name>IDEA</name>
        <alias>International Data Encryption Algorithm</alias>
        <desc><topicref TID="idea"/> is a symmetric block cipher. The speed of <topicref TID="idea"/> in software is similar to that of <topicref TID="des"/>. One of the principles during the design of <topicref TID="idea"/> was to facilitate analysis of its strength against differential cryptanalysis. <topicref TID="idea"/> is considered to be immune from differential cryptanalysis. In addition, no linear cryptanalytic attacks on <topicref TID="idea"/> have been reported and there is no known algebraic weakness in <topicref TID="idea"/>.</desc>
    </topic>
    <topic domain="wwww" TID="flwor" crdate="20051213" modate="20060629">
        <derived-from template="topic"/>
        <name>FLWOR</name>
        <alias>For, Let, Where, Order by, Return</alias>
        <desc><topicref TID="flwor"/> expressions are one of the two main constructs of the <topicref TID="xquery"/> language (the other main construct are <topicref TID="xpath2"/> expressions). They are comparable to <topicref TID="sql"/>'s SELECT, providing the capabilities to iterate over input sequences (FOR), bind variables (LET) define filters (WHERE), order the filtered results (ORDER BY), and finally return the results (RETURN).</desc>
    </topic>
    <topic domain="wwww" TID="jre" crdate="20010312">
        <derived-from template="runtime"/>
        <name>JRE</name>
        <alias>Java Runtime Environment</alias>
    </topic>
    <topic domain="wwww" TID="j2me" crdate="20040720">
        <derived-from template="topic"/>
        <name>J2ME</name>
        <alias>Java 2 Platform, Micro Edition</alias>
    </topic>
    <topic domain="wwww" TID="j2se" crdate="20010302">
        <derived-from template="topic"/>
        <name>J2SE</name>
        <alias>Java 2 Platform, Standard Edition</alias>
    </topic>
    <topic domain="wwww" TID="j2ee" crdate="20001220">
        <derived-from template="technology"/>
        <name>J2EE</name>
        <alias>Java 2 Platform, Enterprise Edition</alias>
    </topic>
    <topic domain="wwww" TID="ejb" crdate="20000719">
        <derived-from template="componentmodel"/>
        <name>EJB</name>
        <alias>Enterprise JavaBeans</alias>
    </topic>
    <topic domain="wwww" TID="javabeans" crdate="20000831">
        <derived-from template="componentmodel"/>
        <name>JavaBeans</name>
    </topic>
    <topic domain="wwww" TID="brew" crdate="20061120">
        <derived-from template="runtime"/>
        <name>BREW</name>
        <alias>Binary Runtime Environment for Wireless</alias>
    </topic>
    <topic domain="wwww" TID="wbem" crdate="20000719">
        <derived-from template="topic"/>
        <name>WBEM</name>
        <alias>Web Based Enterprise Management</alias>
    </topic>
    <topic domain="wwww" TID="dmi" crdate="20000830">
        <derived-from template="topic"/>
        <name>DMI</name>
        <alias>Desktop Management Interface</alias>
    </topic>
    <topic domain="wwww" TID="den" crdate="20041122">
        <derived-from template="topic"/>
        <name>DEN</name>
        <alias>Directory-Enabled Networking</alias>
    </topic>
    <topic domain="wwww" TID="cim" crdate="20000719">
        <derived-from template="topic"/>
        <name>CIM</name>
        <alias>Common Information Model</alias>
    </topic>
    <topic domain="wwww" TID="dhcp" crdate="20000919">
        <derived-from template="protocol"/>
        <name>DHCP</name>
        <alias>Dynamic Host Configuration Protocol</alias>
    </topic>
    <topic domain="wwww" TID="contentneg" crdate="20010317">
        <derived-from template="concept"/>
        <name>Content Negotiation</name>
        <desc><topicref TID="contentneg"/> is an <topicref TID="http"/> mechanism which is used to make a selection between different representations for a resource. Different representations can be characterized by language, quality, encoding, or other parameters which do not affect the content of a resource. <topicref TID="http"/> defines two types of <topicref TID="contentneg"/>, <topicref TID="server"/>-driven and agent-driven. In <topicref TID="server"/>-driven <topicref TID="contentneg"/>, the <topicref TID="httpserver"/> makes the selection and sends a response with the representation of a requested resource which it thinks matches the user's needs, based on the request, available representations, and other information. In agent-driven <topicref TID="contentneg"/>, the <topicref TID="httpserver"/> responds with a list of all representations and the <topicref TID="httpclient"/> (or the user) makes the selection and requests the selected representation.</desc>
    </topic>
    <topic domain="wwww" TID="eii" crdate="20070327">
        <derived-from template="concept"/>
        <name>EII</name>
        <alias>Enterprise Information Integration</alias>
    </topic>
    <topic domain="wwww" TID="eai" crdate="20010915">
        <derived-from template="concept"/>
        <name>EAI</name>
        <alias>Enterprise Application Integration</alias>
    </topic>
    <topic domain="wwww" TID="drm" crdate="20020629">
        <derived-from template="concept"/>
        <name>DRM</name>
        <alias>Digital Rights Management</alias>
        <desc><topicref TID="drm"/> is a <topicref TID="concept"/> for managing and controlling the access and utilization of digital assets. A popular example is audio, which is widely (and in many cases illegally) shared among <topicref TID="internet"/> users with the aid of various <topicref TID="p2p"/> file-sharing applications. Some <topicref TID="drm"/> <topicref TID="technology"/> should be able to control this sharing of audio files by embedding licensing information in audio files, which can then only be played back by users having the appropriate licensing information (probably acquired by paying for the content).</desc>
    </topic>
    <topic domain="wwww" TID="wss" crdate="20031215">
        <derived-from template="concept"/>
        <name>WSS</name>
        <alias>Web Services Security</alias>
    </topic>
    <topic domain="wwww" TID="mom" crdate="20040929">
        <derived-from template="concept"/>
        <name>MOM</name>
        <alias>Message-Oriented Middleware</alias>
    </topic>
    <topic domain="wwww" TID="crm" crdate="20000922">
        <derived-from template="topic"/>
        <name>CRM</name>
        <alias>Customer Relationship Management</alias>
    </topic>
    <topic domain="wwww" TID="snmp" crdate="20000719">
        <derived-from template="protocol"/>
        <name>SNMP</name>
        <alias>Simple Network Management Protocol</alias>
    </topic>
    <topic domain="wwww" TID="ots" crdate="20000719">
        <derived-from template="topic"/>
        <name>OTS</name>
        <alias>Object Transaction Service</alias>
    </topic>
    <topic domain="wwww" TID="cert" crdate="20000719">
        <derived-from template="topic"/>
        <name>CERT</name>
        <alias>Computer Emergency Response Team</alias>
    </topic>
    <topic domain="wwww" TID="cxml" crdate="20000824">
        <derived-from template="topic"/>
        <name>cXML</name>
        <alias>Commerce XML</alias>
    </topic>
    <topic domain="wwww" TID="rsaci" crdate="20020404">
        <derived-from template="technology"/>
        <name>RSACi</name>
        <alias>RSAC on the Internet</alias>
    </topic>
    <topic domain="wwww" TID="ifla" crdate="20020529">
        <derived-from template="organization"/>
        <name>IFLA</name>
        <alias>International Federation of Library Associations</alias>
    </topic>
    <topic domain="wwww" TID="fcc" crdate="20020628">
        <derived-from template="organization"/>
        <name>FCC</name>
        <alias>Federal Communications Commission</alias>
    </topic>
    <topic domain="wwww" TID="rsac" crdate="20020404">
        <derived-from template="organization"/>
        <name>RSAC</name>
        <alias>Recreational Software Advisory Council</alias>
    </topic>
    <topic domain="wwww" TID="icra" crdate="20020404">
        <derived-from template="technology"/>
        <name>ICRA</name>
        <alias>Internet Content Rating Association</alias>
    </topic>
    <topic domain="wwww" TID="xmp" crdate="20020116">
        <derived-from template="metadata"/>
        <name>XMP</name>
        <alias>Extensible Metadata Platform</alias>
    </topic>
    <topic domain="wwww" TID="vml" crdate="20000615">
        <derived-from template="graphicsformat"/>
        <name>VML</name>
        <alias>Vector Markup Language</alias>
    </topic>
    <topic domain="wwww" TID="pgml" crdate="20000615">
        <derived-from template="graphicsformat"/>
        <name>PGML</name>
        <alias>Precision Graphics Markup Language</alias>
        <desc><topicref TID="pgml"/> is a 2D <topicref TID="graphicsformat"/> meant to satisfy both the <topicref TID="www"/>'s scalable lightweight vector graphics needs and the precision needs of graphic artists who want to ensure that their graphic designs appear on end user systems with precisely the correct fonts, color, layout and compositing that they desire. <topicref TID="graphicsformat"/> uses the imaging model of <topicref TID="postscript"/>. <topicref TID="pgml"/> was a proposal authored by <topicref TID="adobe"/> and has been used as input for the development of <topicref TID="svg"/>.</desc>
    </topic>
    <topic domain="wwww" TID="svg" crdate="20000607">
        <derived-from template="graphicsformat"/>
        <name>SVG</name>
        <alias>Scalable Vector Graphics</alias>
        <desc><topicref TID="svg"/> is a language for describing two-dimensional graphics in <topicref TID="xml"/>. <topicref TID="svg"/> allows for three types of graphic objects: vector graphic shapes (e.g., paths consisting of straight lines and curves), images, and text. Graphical objects can be grouped, styled, transformed and composited into previously rendered objects. Text can be in any of the <topicref TID="xmlns"/> suitable to the application, which enhances searchability and accessibility of the <topicref TID="svg"/> graphics. The feature set includes nested transformations, clipping paths, alpha masks, filter effects, template objects and extensibility. <topicref TID="svg"/> drawings can be dynamic and interactive. <topicref TID="dom"/> for <topicref TID="svg"/>, which includes the full <topicref TID="xml"/> <topicref TID="dom"/>, allows for straightforward and efficient vector graphics animation via scripting. Event handlers can be assigned to any <topicref TID="svg"/> graphical object. Because of its compatibility and leveraging of other <topicref TID="www"/> standards, features like scripting can be done on <topicref TID="svg"/> elements and other <topicref TID="xml"/> elements from different <topicref TID="xmlns"/> simultaneously within the same <topicref TID="www"/> page.</desc>
    </topic>
    <topic domain="wwww" TID="sxbl" crdate="20040905">
        <derived-from template="dataformat"/>
        <name>sXBL</name>
        <alias>SVG's XML Binding Language</alias>
    </topic>
    <topic domain="wwww" TID="eml" crdate="20040629">
        <derived-from template="dataformat"/>
        <name>EML</name>
        <alias>Election Markup Language</alias>
    </topic>
    <topic domain="wwww" TID="mathml" crdate="20000608">
        <derived-from template="dataformat"/>
        <name>MathML</name>
        <alias>Mathematical Markup Language</alias>
    </topic>
    <topic domain="wwww" TID="jabber" crdate="20001130">
        <derived-from template="imsystem"/>
        <name>Jabber</name>
    </topic>
    <topic domain="wwww" TID="xmlrpc" crdate="20001130">
        <derived-from template="rpc"/>
        <name>XML-RPC</name>
    </topic>
    <topic domain="wwww" TID="jsonrpc" crdate="20061206">
        <derived-from template="rpc"/>
        <name>JSON-RPC</name>
    </topic>
    <topic domain="wwww" TID="wse" crdate="20040620">
        <derived-from template="topic"/>
        <name>WSE</name>
        <alias>Web Services Enhancements</alias>
    </topic>
    <topic domain="wwww" TID="wssecurity" crdate="20040103">
        <derived-from template="topic"/>
        <name>WS-Security</name>
        <alias>Web Services Security</alias>
        <desc><topicref TID="wssecurity"/> defines a standard set of <topicref TID="soap"/> extensions, or message headers, that can be used to implement integrity and confidentiality in Web services applications.</desc>
    </topic>
    <topic domain="wwww" TID="wseventing" crdate="20040712">
        <derived-from template="topic"/>
        <name>WS-Eventing</name>
    </topic>
    <topic domain="wwww" TID="wsevents" crdate="20040712">
        <derived-from template="topic"/>
        <name>WS-Events</name>
    </topic>
    <topic domain="wwww" TID="wsnotification" crdate="20040712">
        <derived-from template="topic"/>
        <name>WS-Notification</name>
    </topic>
    <topic domain="wwww" TID="wscaf" crdate="20040806">
        <derived-from template="topic"/>
        <name>WS-CAF</name>
        <alias>Web Services Composite Applications Framework</alias>
        <desc><topicref TID="wscaf"/> is a collection of three specifications (<topicref TID="wsctx"/>, <topicref TID="wscf"/>, and <topicref TID="wstxm"/>) designed to solve problems that arise when multiple Web services are used in combination(composite applications) to support information sharing and transaction processing. It is similar in scope to <topicref TID="wstf"/>.</desc>
    </topic>
    <topic domain="wwww" TID="wsctx" crdate="20040806">
        <derived-from template="topic"/>
        <name>WS-CTX</name>
        <alias>Web Services Context</alias>
    </topic>
    <topic domain="wwww" TID="wscf" crdate="20040806">
        <derived-from template="topic"/>
        <name>WS-CF</name>
        <alias>Web Services Coordination Framework</alias>
    </topic>
    <topic domain="wwww" TID="wstxm" crdate="20040806">
        <derived-from template="topic"/>
        <name>WS-TXM</name>
        <alias>Web Services Transaction Management</alias>
    </topic>
    <topic domain="wwww" TID="wstf" crdate="20040806">
        <derived-from template="topic"/>
        <name>WSTF</name>
        <alias>Web Services Transaction Framework</alias>
        <desc>The Web Service architecture provides a set of modular protocol building blocks that can be composed in varying ways to create protocols specific to particular applications. The <topicref TID="wstf"/> protocols present in <topicref TID="wscoordination"/>, <topicref TID="wsatomictransaction"/>, and <topicref TID="wsbusinessactivity"/> are mechanisms to create activities, join into them, and reach common agreement on the outcome of joint operations. These specifications provide a basis on which to build interoperable, distributed applications that desire to coordinate joint work. <topicref TID="wstf"/> is similar in scope to <topicref TID="wscaf"/>.</desc>
    </topic>
    <topic domain="wwww" TID="wscoordination" crdate="20040806">
        <derived-from template="topic"/>
        <name>WS-Coordination</name>
        <alias>Web Services Coordination</alias>
    </topic>
    <topic domain="wwww" TID="wsbusinessactivity" crdate="20040806">
        <derived-from template="topic"/>
        <name>WS-BusinessActivity</name>
        <alias>Web Services Business Activity</alias>
    </topic>
    <topic domain="wwww" TID="wspolicy" crdate="20040806">
        <derived-from template="topic"/>
        <name>WS-Policy</name>
        <alias>Web Services Policy</alias>
    </topic>
    <topic domain="wwww" TID="wspolicyassertions" crdate="20040806">
        <derived-from template="topic"/>
        <name>WS-PolicyAssertions</name>
        <alias>Web Services Policy Assertions</alias>
    </topic>
    <topic domain="wwww" TID="wsatomictransaction" crdate="20040806">
        <derived-from template="topic"/>
        <name>WS-AtomicTransaction</name>
        <alias>Web Services Atomic Transaction</alias>
    </topic>
    <topic domain="wwww" TID="wstransaction" crdate="20040203">
        <derived-from template="topic"/>
        <name>WS-Transaction</name>
        <alias>Web Services Transaction</alias>
        <status>Part I of the <topicref TID="wstransaction"/> specification has been superseded by the <topicref TID="wsatomictransaction"/> specification. Part II of the <topicref TID="wstransaction"/> specification has been superseded by the <topicref TID="wsbusinessactivity"/> specification.</status>
    </topic>
    <topic domain="wwww" TID="wsreferral" crdate="20040203">
        <derived-from template="topic"/>
        <name>WS-Referral</name>
        <alias>Web Services Referral</alias>
    </topic>
    <topic domain="wwww" TID="wsrouting" crdate="20040203">
        <derived-from template="topic"/>
        <name>WS-Routing</name>
        <alias>Web Services Routing</alias>
    </topic>
    <topic domain="wwww" TID="wsaddressing" modate="20040811" crdate="20040620">
        <derived-from template="topic"/>
        <name>WS-Addressing</name>
        <alias>Web Services Addressing</alias>
        <desc><topicref TID="wsaddressing"/> provides transport-neutral mechanisms to address Web services and messages. Specifically, <topicref TID="wsaddressing"/> defines <topicref TID="soap"/> header elements to identify Web services endpoints and to secure end-to-end endpoint identification in messages. <topicref TID="wsaddressing"/> enables messaging systems to support message transmission through networks that include processing nodes such as endpoint managers, <topicref TID="firewall"/>s, and <topicref TID="gateway"/>s in a transport-neutral manner.</desc>
    </topic>
    <topic domain="wwww" TID="wsattachments" crdate="20040203">
        <derived-from template="topic"/>
        <name>WS-Attachments</name>
        <alias>Web Services Attachments</alias>
    </topic>
    <topic domain="wwww" TID="xmlenc" crdate="20040103">
        <derived-from template="topic"/>
        <name>XML-Enc</name>
        <alias>XML Encryption</alias>
    </topic>
    <topic domain="wwww" TID="xkms" crdate="20031215">
        <derived-from template="topic"/>
        <name>XKMS</name>
        <alias>XML Key Management Specification</alias>
    </topic>
    <topic domain="wwww" TID="xbulk" crdate="20031215">
        <derived-from template="topic"/>
        <name>X-BULK</name>
        <alias>XKMS Bulk Operation</alias>
    </topic>
    <topic domain="wwww" TID="xmldsig" modate="20040103" crdate="20000920">
        <derived-from template="topic"/>
        <name>XML-DSig</name>
        <alias>XML-Signature</alias>
    </topic>
    <topic domain="wwww" TID="psvi" crdate="20020624">
        <derived-from template="topic"/>
        <name>PSVI</name>
        <alias>Post-Schema-Validation Infoset</alias>
    </topic>
    <topic domain="wwww" TID="pi" crdate="20020624">
        <derived-from template="topic"/>
        <name>PI</name>
        <alias>Processing Instruction</alias>
    </topic>
    <topic domain="wwww" TID="xliff" crdate="20030807">
        <derived-from template="dataformat"/>
        <name>XLIFF</name>
        <alias>XML Localization Interchange File Format</alias>
    </topic>
    <topic domain="wwww" TID="xcbf" crdate="20030128">
        <derived-from template="dataformat"/>
        <name>XCBF</name>
        <alias>XML Common Biometric Format</alias>
    </topic>
    <topic domain="wwww" TID="cbeff" crdate="20030128">
        <derived-from template="dataformat"/>
        <name>CBEFF</name>
        <alias>Common Biometric Exchange File Format</alias>
    </topic>
    <topic domain="wwww" TID="emma" crdate="20030116">
        <derived-from template="dataformat"/>
        <name>EMMA</name>
        <alias>Extensible Multimodal Annotation Language</alias>
    </topic>
    <topic domain="wwww" TID="srml" crdate="20030116">
        <derived-from template="dataformat"/>
        <name>SRML</name>
        <alias>Simulation Reference Markup Language</alias>
    </topic>
    <topic domain="wwww" TID="ool" crdate="20030116">
        <derived-from template="dataformat"/>
        <name>Ool</name>
        <alias>Out-of-line XML</alias>
    </topic>
    <topic domain="wwww" TID="jitt" crdate="20030116">
        <derived-from template="dataformat"/>
        <name>JITT</name>
        <alias>Just-In-Time-Trees</alias>
    </topic>
    <topic domain="wwww" TID="creole" crdate="20070424">
        <derived-from template="schemalanguage"/>
        <name>Creole</name>
        <alias>Composable Regular Expressions for Overlapping Languages</alias>
    </topic>
    <topic domain="wwww" TID="lmnl" crdate="20021217">
        <derived-from template="dataformat"/>
        <name>LMNL</name>
        <alias>Layered Markup Annotation Language</alias>
    </topic>
    <topic domain="wwww" TID="xml" crdate="20000607">
        <derived-from template="dataformat"/>
        <name>XML</name>
        <alias>Extensible Markup Language</alias>
        <desc><topicref TID="xml"/> is a markup language for structuring arbitrary data. <topicref TID="xml"/> was designed to replace <topicref TID="html"/>, which was deemed too restricted with its fixed set of elements and attributes. Because <topicref TID="html"/> is based on <topicref TID="sgml"/>, but <topicref TID="sgml"/> itself was considered as being too complex for direct application on the <topicref TID="www"/>, <topicref TID="xml"/> was defined as a functional subset (a "profile") of <topicref TID="sgml"/>. <topicref TID="xml"/> defines types (often referred to as "schemas" or "document classes") with <topicref TID="dtd"/>s, which originate from the document-centered view of <topicref TID="sgml"/>. However, <topicref TID="xml"/> is very successful in <topicref TID="b2b"/> scenarios, and as such is increasingly used for data exchange (as opposed to document exchange). Because data description requires other features than document description (e.g., built-in data types and type derivation), <topicref TID="xsd"/> has been defined as a replacement for <topicref TID="dtd"/>s, which makes <topicref TID="xml"/> more usable for <topicref TID="b2b"/> scenarios.</desc>
    </topic>
    <topic domain="wwww" TID="voxml" crdate="20000711">
        <derived-from template="dataformat"/>
        <name>VoxML</name>
    </topic>
    <topic domain="wwww" TID="salt" crdate="20020518">
        <derived-from template="topic"/>
        <name>SALT</name>
        <alias>Speech Application Language Tags</alias>
    </topic>
    <topic domain="wwww" TID="openid" crdate="20061024">
        <derived-from template="sso"/>
        <name>OpenID</name>
    </topic>
    <topic domain="wwww" TID="shibboleth" crdate="20061024">
        <derived-from template="sso"/>
        <name>Shibboleth</name>
    </topic>
    <topic domain="wwww" TID="authml" crdate="20040802">
        <derived-from template="dataformat"/>
        <name>AuthML</name>
        <alias>Authentication Markup Language</alias>
        <status><topicref TID="authml"/> is no longer under development and has been merged with the <topicref TID="s2ml"/> effort into <topicref TID="saml"/>.</status>
    </topic>
    <topic domain="wwww" TID="s2ml" crdate="20040802">
        <derived-from template="dataformat"/>
        <name>S2ML</name>
        <alias>Security Services Markup Language</alias>
        <status><topicref TID="s2ml"/> is no longer under development and has been merged with the <topicref TID="authml"/> effort into <topicref TID="saml"/>.</status>
    </topic>
    <topic domain="wwww" TID="saml" modate="20040802" crdate="20020518">
        <derived-from template="dataformat"/>
        <name>SAML</name>
        <alias>Security Assertion Markup Language</alias>
        <desc><topicref TID="saml"/> is an <topicref TID="xml"/>-based framework for exchanging security information. This security information is expressed in the form of assertions about subjects, where a subject is an entity (either human or computer) that has an identity in some security domain. A typical example of a subject is a person, identified by the <topicref TID="email"/> address in a particular <topicref TID="dns"/> domain. Assertions can convey information about <topicref TID="authentication"/> acts performed by subjects, attributes of subjects, and <topicref TID="authorization"/> decisions about whether subjects are allowed to access certain resources.</desc>
    </topic>
    <topic domain="wwww" TID="dsml" crdate="20020518">
        <derived-from template="dataformat"/>
        <name>DSML</name>
        <alias>Directory Services Markup Language</alias>
    </topic>
    <topic domain="wwww" TID="ldif" crdate="20020611">
        <derived-from template="dataformat"/>
        <name>LDIF</name>
        <alias>LDAP Data Interchange Format</alias>
        <desc><topicref TID="ldif"/> is typically used to import and export directory information between <topicref TID="ldap"/>-based directory servers, or to describe a set of changes which are to be applied to a directory. <topicref TID="ldif"/> is also frequently used by <topicref TID="email"/> agents as file format for directory information (such as address books). <topicref TID="ldif"/> is a text-based format which can be easily manipulated using text-based tools (for <topicref TID="xml"/>-based applications, <topicref TID="dsml"/> is available as an <topicref TID="xml"/>-based version for <topicref TID="ldap"/> information).</desc>
    </topic>
    <topic domain="wwww" TID="gml3" crdate="20020622">
        <derived-from template="dataformat"/>
        <name>GML</name>
        <alias>Generalized Markup Language</alias>
    </topic>
    <topic domain="wwww" TID="gml1" crdate="20020506">
        <derived-from template="dataformat"/>
        <name>GML</name>
        <alias>Graph Modelling Language</alias>
    </topic>
    <topic domain="wwww" TID="dprl" crdate="20020621">
        <derived-from template="dataformat"/>
        <name>DPRL</name>
        <alias>Digital Property Rights Language</alias>
    </topic>
    <topic domain="wwww" TID="xmcl" crdate="20020629">
        <derived-from template="dataformat"/>
        <name>XMCL</name>
        <alias>Extensible Media Commerce Language</alias>
    </topic>
    <topic domain="wwww" TID="prism" crdate="20020629">
        <derived-from template="dataformat"/>
        <name>PRISM</name>
        <alias>Publishing Requirements for Industry Standard Metadata</alias>
    </topic>
    <topic domain="wwww" TID="ipmp" crdate="20040501">
        <derived-from template="dataformat"/>
        <name>IPMP</name>
        <alias>Intellectual Property Management and Protection</alias>
    </topic>
    <topic domain="wwww" TID="ipmpx" crdate="20040501">
        <derived-from template="dataformat"/>
        <name>IPMPX</name>
        <alias>IPMP Extensions</alias>
    </topic>
    <topic domain="wwww" TID="odrl" crdate="20020629">
        <derived-from template="dataformat"/>
        <name>ODRL</name>
        <alias>Open Digital Rights Language</alias>
    </topic>
    <topic domain="wwww" TID="xbrl" crdate="20020823">
        <derived-from template="dataformat"/>
        <name>XBRL</name>
        <alias>Extensible Business Reporting Language</alias>
    </topic>
    <topic domain="wwww" TID="mddl" crdate="20040108">
        <derived-from template="dataformat"/>
        <name>MDDL</name>
        <alias>Market Data Definition Language</alias>
    </topic>
    <topic domain="wwww" TID="fpml" crdate="20020902">
        <derived-from template="dataformat"/>
        <name>FpML</name>
        <alias>Financial Pro
