<?xml version="1.0"?>
<!-- dret.net glossary (http://dret.net/glossary/); (c) 2000-2007 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 EMPTY>
    <!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="xsdl"/>.</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="format"/>
        <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="xsdl"/> 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="xsdl"/>.</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="technology"/>
        <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="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="xsdl"/> components. It focuses explicitly on representing <topicref TID="xsdl"/> components rather than including features which should make it easy for human users to write or modify an <topicref TID="xsdl"/>. <topicref TID="scx"/> is comparable to <topicref TID="xsdl"/>'s XML syntax or to <topicref TID="xscs"/>, because it simply is a representation for <topicref TID="xsdl"/> components. What makes <topicref TID="scx"/> unique is its focus on making the <topicref TID="xsdl"/> 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="xsd"/>.</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="xsdl"/> 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="xsdl"/>, <topicref TID="xscs"/> defines a <topicref TID="ebnf"/>-based (and non-<topicref TID="xml"/>) syntax for <topicref TID="xsdl"/>. <topicref TID="xscs"/> is designed for human users, and transformations from and to <topicref TID="xsdl"/> <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="xsdl"/> 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="xsdl"/>, 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="xsdl"/>, <topicref TID="microsoft"/> limited <topicref TID="xmldata"/> to <topicref TID="xdr2"/>, which is a proper subset of <topicref TID="xsdl"/>.</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="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="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="format"/>
        <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="w