<?xml version="1.0" encoding="ISO-8859-1"?>
<DictionaryContent xmlns="http://www.xml-acronym-demystifier.org"  >

	<Entry>
		<Acronym expansion="Enterprise Privacy Authorization Language" id="EPAL">EPAL</Acronym>
		<MoreInfo>http://www.zurich.ibm.com/security/enterprise-privacy/epal/Specification/index.html</MoreInfo>
		<Definition xml:lang="en-us">EPAL is a formal language for writing enterprise privacy policies to govern data handling practices in IT systems according to fine-grained positive and negative authorization rights. It concentrates on the core privacy authorization while abstracting data models and user-authentication from all deployment details such as data model or user-authentication.</Definition>
	</Entry>
	<Entry>
		<Acronym expansion="Modular Namespace Language" id="MNS">MNS</Acronym>
		<SpecLoc>http://www.thaiopensource.com/relaxng/mns.html</SpecLoc>
		<Definition xml:lang="en-us">The XML Namespaces Recommendation allows an XML document to be composed of elements and attributes from multiple independent namespaces. Each of these namespaces may have its own schema. The problem then arises of how the schemas can be composed in order to allow validation of the complete document. MNS is a language, which is an evolution of the ideas in RELAX Namespace and DSDL Part 4. RELAX Namespace was designed to work well with RELAX Core. RELAX Core cannot deal with documents that use multiple namespaces, nor does it provide any namespace-based wildcards. These limitations of RELAX Core are reflected in the design of RELAX Namespace. MNS is designed to be able to take advantage of more recent schema languages, such as RELAX NG, that are not limited in this way.</Definition>
	</Entry>
	<Entry>
		<Acronym expansion="Namespace Routing Language" id="NRL">NRL</Acronym>
		<SpecLoc>http://www.thaiopensource.com/relaxng/nrl.html</SpecLoc>
		<Definition xml:lang="en-us">NRL allows an XML document to be composed of elements and attributes from multiple independent namespaces. Each of these namespaces may have its own schema; the schemas for different namespaces may be in different schema languages. The problem then arises of how the schemas can be composed in order to allow validation of the complete document. NRL is a solution to this problem. It is an evolution of the Modular Namespaces (MNS) language.</Definition>
	</Entry>
	<Entry>
		<Acronym expansion="Open Building Information Exchange" id="oBIX">oBIX</Acronym>
		<AlternateForms>
			<AlternateForm>OBIX</AlternateForm>
		</AlternateForms>
		<MoreInfo>http://lists.oasis-open.org/archives/tc-announce/200405/msg00000.html</MoreInfo>
		<Definition xml:lang="en-us">oBiX is an industry-wide initiative to define XML- and Web services-based mechanisms for building control systems.</Definition>
	</Entry>
	<Entry>
		<Acronym expansion="Web Services Addressing" id="WSAdressing">WS-Addressing</Acronym>
		<AlternateForms>
			<AlternateForm>WS-ADD</AlternateForm>
		</AlternateForms>
		<SpecLoc>http://www-106.ibm.com/developerworks/library/specification/ws-add/</SpecLoc>
		<Definition xml:lang="en-us">Web Services Addressing provides transport-neutral mechanisms to address Web services and messages. Specifically, it defines XML elements to identify Web services endpoints and to secure end-to-end endpoint identification in messages. Web Services Addressing enables messaging systems to support message transmission through networks that include processing nodes such as endpoint managers, firewalls, and gateways in a transport-neutral manner.</Definition>
	</Entry>
	<Entry>
		<Acronym expansion="Continuous Media Markup Language" id="CMML" type="IETF">CMML</Acronym>
		<SpecLoc>http://www.ietf.org/internet-drafts/draft-pfeiffer-cmml-01.txt</SpecLoc>
		<Definition xml:lang="en-us">The Continuous Media Markup Language
is an XML-based markup language for time-continuous data. It is a sister document to the specification of
the Annodex annotation, indexing and hyperlinking format for
time-continuous data. Its tags provide for the creation of structured
and unstructured annotations as well as hyperlinks and addressable
named anchor points for clips of time-continuous data. As well as
enabling the creation and storage of such meta data in XML files, the
CMML is an authoring language for Annodex streams through its
import tags. The tag names in use in CMML are similar to the ones in
XHTML.</Definition>
	</Entry>
	<Entry>
		<Acronym expansion="XML Enabled Directory" id="XED" type="IETF">XED</Acronym>
		<SpecLoc>http://www.ietf.org/internet-drafts/draft-legg-xed-roadmap-02.txt</SpecLoc>
		<Definition xml:lang="en-us">The XML Enabled Directory (XED) leverages existing Lightweight Directory Access Protocol (LDAP)
		and X.500 directory technology to create a directory service that stores, manages and transmits Extensible Markup Language (XML)
		format data, while maintaining interoperability with LDAP clients and X.500 agents.</Definition>
	</Entry>
	<Entry>
		<Acronym expansion="Web Service Level Agreement" id="WSLA" type="IBM">WSLA</Acronym>
		<MoreInfo>http://www.research.ibm.com/wsla/</MoreInfo>
		<Definition xml:lang="en-us">The WSLA project addresses service level management issues and challenges in a Web Services environment on Service Level Agreement specification, creation and monitoring.</Definition>
	</Entry>
	<Entry>
		<Acronym expansion="XML Configuration Access Protocol" id="XCAP" type="IETF">XCAP</Acronym>
		<SpecLoc>http://www.jdrosen.net/papers/draft-ietf-simple-xcap-02.txt</SpecLoc>
		<Definition xml:lang="en-us">The Extensible Markup Language (XML)
   Configuration Access Protocol (XCAP) allows a client to read,
   write and modify application configuration data, stored in XML format
   on a server. XCAP is not a new protocol. XCAP maps XML document
   sub-trees and element attributes to HTTP URIs, so that these
   components can be directly accessed by HTTP.</Definition>
	</Entry>
	<Entry>
		<Acronym expansion="Media Server Control Markup Language" id="MSCML" type="IETF">MSCML</Acronym>
		<SpecLoc>http://xml.coverpages.org/draft-vandyke-mscml-03.txt</SpecLoc>
		<Definition xml:lang="en-us">MSCML is a SIP-based development and control language for IP enhanced conferencing services. MSCML is used in conjunction with SIP to provide advanced conferencing and IVR functions.</Definition>
	</Entry>
	<Entry>
		<Acronym expansion="" id="WVG" type="Microsoft">WVG</Acronym>
		<MoreInfo>http://longhorn.msdn.microsoft.com/lhsdk/graphicsmm/overviews/wvg1.aspx</MoreInfo>
		<Definition xml:lang="en-us">In essence WVG is a SVG clone which tries to provide a more user friendly syntax.</Definition>
	</Entry>
	<Entry>
		<Acronym expansion="Keypad Markup Language" id="KPML">KPML</Acronym>
		<SpecLoc>http://xml.coverpages.org/draft-burger-sipping-kpml-02.txt</SpecLoc>
		<Definition xml:lang="en-us">The Keypress Stimulus Protocol uses the Keypad Markup Language (KPML)
   to provide instructions to SIP User Agents for the reporting of user
   key presses.</Definition>
	</Entry>
	<Entry>
		<Acronym expansion="Abstract User Interface Markup Language" id="AUIML" type="IBM">AUIML</Acronym>
		<MoreInfo>http://www.alphaworks.ibm.com/tech/auiml</MoreInfo>
		<Definition xml:lang="en-us">A markup language for defining user interfaces which can be transferred into
		code to render with Swing or a simple Web browser.</Definition>
	</Entry>
	<Entry>
		<Acronym expansion="Service Creation Markup Language" id="SCML" type="IETF">SCML</Acronym>
		<SpecLoc>http://ftp.iasi.roedu.net/mirrors/ftp.ietf.org/internet-drafts/draft-bakker-jain-scml-00.txt</SpecLoc>
		<Definition xml:lang="en-us">The Service Creation Markup Language suite of XML schemata defines a way to create
		services on top of a converged (i.e., packet/circuit, wired/wireless)
        Next Generation Network.  SCML is API or protocol independent.</Definition>
	</Entry>
	<Entry>
		<Acronym expansion="Wordprocessing Markup Language" id="WordprocessingML" type="Microsoft">WordprocessingML</Acronym>
		<AlternateForms>
			<AlternateForm>WordML</AlternateForm>
		</AlternateForms>
		<MoreInfo>http://www.microsoft.com/office/xml/overview.mspx</MoreInfo>
		<Definition xml:lang="en-us">XML format of Microsoft's Office 2003 version of Word</Definition>
	</Entry>
	<Entry>
		<Acronym expansion="Spreadsheet Markup Language" id="SpreadsheetML" type="Microsoft">SpreadsheetML</Acronym>
		<AlternateForms>
			<AlternateForm>ExcelML</AlternateForm>
		</AlternateForms>
		<MoreInfo>http://www.microsoft.com/office/xml/overview.mspx</MoreInfo>
		<Definition xml:lang="en-us">XML format of Microsoft's Office 2003 version of Excel</Definition>
	</Entry>
	<Entry>
		<Acronym expansion="EPIC" id="epic">EPIC</Acronym>
		<MoreInfo>http://www.arbortext.com/html/epic_editor_datasheet.html?elqerr=1</MoreInfo>
		<Definition xml:lang="en-us">Neither a standard nor a specification at all. EPIC is a XML editor available
		as commercial product sold by Arbortext</Definition>
	</Entry>
	<Entry>
		<Acronym expansion="XML User Interface Language" id="XUL">XUL</Acronym>
		<MoreInfo>http://www.xulplanet.com/</MoreInfo>
		<Definition xml:lang="en-us">The XML User Interface Language is a markup language for describing user interfaces. With XUL rich, sophisticated cross-platform web applications can be created.</Definition>
	</Entry>
	<Entry>
		<Acronym expansion="XML Update" id="XUpdate">XUpdate</Acronym>
		<SpecLoc>http://www.xmldb.org/xupdate/</SpecLoc>
		<Definition xml:lang="en-us">XUpdate defines a syntax and semantics for a language for updating XML documents. XUpdate is designed to be used independently of any kinf of implementation.</Definition>
	</Entry>
	<Entry>
		<Acronym expansion="Web Services Atomic Transaction" id="WS-AtomicTransaction" type="Microsoft IBM BEA">WS-AtomicTransaction</Acronym>
		<AlternateForms>
			<AlternateForm>WS-AT</AlternateForm>
		</AlternateForms>
		<SpecLoc>http://www-106.ibm.com/developerworks/library/ws-atomtran/</SpecLoc>
		<Definition xml:lang="en-us">WS-AtomicTransaction is the definition of the atomic transaction coordination type that is to be used with the extensible coordination framework described in the WS-Coordination specification.</Definition>
	</Entry>
	<Entry>
		<Acronym expansion="eXtensible Server Pages" id="XSP">XSP</Acronym>
		<SpecLoc>http://searchwebservices.techtarget.com/tip/1,289483,sid26_gci534442,00.html</SpecLoc>
		<Definition xml:lang="en-us">XSP attempts to do for JSP what XML did for HTML - namely, to create a way of building server-side functionality that separates syntax and semantics from content, and allows content and online interactivity to be managed explicitly and abstractly. </Definition>
	</Entry>
	<Entry>
		<Acronym expansion="XML Data Packaging" id="XDP">XDP</Acronym>
		<MoreInfo>http://www.adobe.com/aboutadobe/pressroom/pressreleases/200307/071503XMLFORM.html</MoreInfo>
		<Definition xml:lang="en-us">A XML vocabulary created by Adobe. XDP file store XML form data, XML form templates, and PDF documents as well as other XML information.</Definition>
	</Entry>
	<Entry>
		<Acronym expansion="Simple XML Data Manipulation Language" id="SiXDML">SiXDML</Acronym>
		<MoreInfo>http://sixdml.sourceforge.net/</MoreInfo>
		<Definition xml:lang="en-us">SiXDML was designed to create a common syntax and semantics for performing tasks most often required of XML repositories. SiXDML consists of two parts; a data definition and manipulation language inspired by SQL and an application programming interface based on the XML:DB Database API.</Definition>
	</Entry>
	<Entry>
		<Acronym expansion="Native XML Database" id="NXD">NXD</Acronym>
		<SpecLoc>http://www.xml.com/lpt/a/2001/10/31/nativexmldb.html</SpecLoc>
		<Definition xml:lang="en-us">A Native XML Database (NXD) database is specialized for storing XML data and stores all components of the XML model intact.
		Documents go in and documents come out. A NXD may not actually be a standalone database at all.
NXDs don't really represent a new low-level database model, and aren't intended to replace existing databases. They're simply a tool intended to assist the developer by providing robust storage and manipulation of XML documents.</Definition>
	</Entry>
	<Entry>
		<Acronym expansion="XML Television" id="XMLTV">XMLTV</Acronym>
		<MoreInfo>http://freshmeat.net/releases/135861/</MoreInfo>
		<Definition xml:lang="en-us">XMLTV is a set of programs to process TV (tvguide) listings and manage your TV viewing. It stores the listings in an XML-based format and most of the programs are filters which read and/or write XML. There are backends to download TV listings for several countries. It also includes some filter tools to sort, grep, print, and munge listings, and two end-user programs to plan a week's TV viewing.</Definition>
	</Entry>
	<Entry>
		<Acronym expansion="JaxMe does not seem to be an acronym" id="JaxMe">JaxMe</Acronym>
		<AlternateForms>
			<AlternateForm>JaxMe 2</AlternateForm>
			<AlternateForm>JaxMe2</AlternateForm>
		</AlternateForms>
		<MoreInfo>http://jaxme.sourceforge.net</MoreInfo>
		<Definition xml:lang="en-us">JaxMe 2 is an open source implementation of JAXB, the specification for Java/XML binding.</Definition>
	</Entry>
	<Entry>
		<Acronym expansion="Java API for WML" id="JAXW" type="SUN">JAXW</Acronym>
		<Definition xml:lang="en-us">Java API for working with the Wireless Markup Language.</Definition>
	</Entry>
	<Entry>
		<Acronym expansion="Java API for XML Transformations" id="JAXT" type="SUN">JAXT</Acronym>
		<Definition xml:lang="en-us">Java API for working with XSLT transformations.</Definition>
	</Entry>
	<Entry>
		<Acronym expansion="Java API for XHTML" id="JAXH" type="SUN">JAXH</Acronym>
		<Definition xml:lang="en-us">Java API for XHTML processing.</Definition>
	</Entry>
	<Entry>
		<Acronym expansion="TCL Document Object Model" id="tDOM">tDOM</Acronym>
		<MoreInfo>http://www.tdom.org</MoreInfo>
		<Definition xml:lang="en-us">A XML/DOM/XPath package for Tcl written in C.</Definition>
	</Entry>
	<Entry>
		<Acronym expansion="XML Interchange Format" type="Microsoft" id="XIF">XIF</Acronym>
		<MoreInfo>http://www.microsoft.com/sql/</MoreInfo>
		<Definition xml:lang="en-us">XIF is a format shipped with the SQL Server Meta Data Services. In the meantime it has been replaced by a nameless XML encoding.</Definition>
	</Entry>
	<Entry>
		<Acronym expansion="Proposed Infoset Addendum to SOAP Messages with Attachments" id="PASWA">PASWA</Acronym>
		<SpecLoc>http://www.gotdotnet.com/team/jeffsch/paswa/paswa61.html</SpecLoc>
		<Definition xml:lang="en-us">PASWA proposes a set of concrete idioms and conventions that build on SOAP Messages with Attachments, yielding the following enhancements: (1) Alignment with the XML Infoset-based data model and the SOAP processing model - opaque data may be correctly processed by intermediaries and may be secured. (2) Backwards-compatible message syntax - every message conforming to this proposal is a legal SwA/1.0 message. (3) Alternate message syntax for SOAP processors that have no knowledge of SwA or this proposal - message content can be faithfully serialized in a form that is understandable by SOAP processors that do not comply with this specification.</Definition>
	</Entry>
	<Entry>
		<Acronym expansion="Business Associates Markup Language" id="BAML">BAML</Acronym>
		<SpecLoc>http://www.xml.org/xml/registry_searchresults.jsp?industry=23&amp;keyword=&amp;update_date=7200&amp;schema_type=0#682</SpecLoc>
		<Definition xml:lang="en-us">BAML can be used to share information about companies or people. As a stand-alone schema, it is used to share company names, addresses, contact information, service lists and so on with stakeholders. Alternatively, it can be embedded in other schemas so that any XML document can choose to embed as much or as little detail about a company as is necessary.</Definition>
	</Entry>
	<Entry>
		<Acronym expansion="bindingTempalte is not an Acronym" id="bindingTemplate" type="OASIS">bindingTemplate</Acronym>
		<AlternateForms>
			<AlternateForm>binding template</AlternateForm>
		</AlternateForms>
		<SpecLoc>http://www.oasis-open.org/committees/uddi-spec/tcspecs.shtml#uddiv2</SpecLoc>
		<Definition xml:lang="en-us">Each bindingTemplate structure represents an individual Web service. In contrast with the
businessService and businessEntity structures, which are oriented toward auxiliary information
about providers and services, a bindingTemplate provides the technical information needed by
applications to bind and interact with the Web service being described. It must contain either
the access point for a given service or an indirection mechanism that will lead one to the
access point.</Definition>
	</Entry>
	<Entry>
		<Acronym expansion="businessService is not an Acronym" id="businessService" type="OASIS">businessService</Acronym>
		<AlternateForms>
			<AlternateForm>business service</AlternateForm>
		</AlternateForms>
		<SpecLoc>http://www.oasis-open.org/committees/uddi-spec/tcspecs.shtml#uddiv2</SpecLoc>
		<Definition xml:lang="en-us">Each businessService structure represents a logical grouping of Web Services. At the service level, there is still no technical information provided about those services; rather, this structure allows the ability to assemble a set of services under a common rubric. Each businessService is the logical child of a single businessEntity. Each businessService contains descriptive information -- again, names, descriptions and classification information -- outlining the purpose of the individual Web services found within it. For example, a businessService structure could
contain a set of Purchase Order Web services (submission, confirmation and notification) that are provided by a business.</Definition>
	</Entry>
	<Entry>
		<Acronym expansion="busienssEntity is not an acronym" id="businessEntity" type="OASIS">businessEntity</Acronym>
		<AlternateForms>
			<AlternateForm>business entity</AlternateForm>
		</AlternateForms>
		<SpecLoc>http://www.oasis-open.org/committees/uddi-spec/tcspecs.shtml#uddiv2</SpecLoc>
		<Definition xml:lang="en-us">One top-level data structure within UDDI is the businessEntity structure, used to represent
businesses and providers within UDDI. It contains descriptive information about the business or provider and about the services it offers. This would include information such as names and
descriptions in multiple languages, contact information and classification information. Service descriptions and technical information are expressed within a businessEntity by contained
businessService and bindingTemplate structures.</Definition>
	</Entry>
	<Entry>
		<Acronym expansion="technical Model" id="tModel" type="OASIS">tModel</Acronym>
		<SpecLoc>http://www.oasis-open.org/committees/uddi-spec/tcspecs.shtml#uddiv2</SpecLoc>
		<Definition xml:lang="en-us">Technical Models are used in UDDI to represent unique concepts or constructs. They provide a structure that allows re-use and, thus, standardization within a
software framework. The UDDI information model is based on this notion of shared specifications and uses tModels to engender this behavior. For this reason, tModels exist
outside the parent-child containment relationships between the businessEntity, businessService and bindingTemplate structures.</Definition>
	</Entry>
	<Entry>
		<Acronym expansion="WellLogML does not seem to be an acronym." id="WellLogML">WellLogML</Acronym>
		<SpecLoc>http://www.posc.org/ebiz/WellLogML/</SpecLoc>
		<Definition xml:lang="en-us">WellLogML is a format for exchanging well log data over networks.</Definition>
	</Entry>
	<Entry>
		<Acronym expansion="Transmission Control Protocol" id="TCP" type="IETF">TCP</Acronym>
		<SpecLoc>ftp://ftp.isi.edu/in-notes/rfc3252.txt</SpecLoc>
		<Definition xml:lang="en-us">TCP is a binary non-XML format. Ideas of reformulating transport layer protocols such as TCP or IP as XML applications are just april fools.</Definition>
	</Entry>
	<Entry>
		<Acronym expansion="Internet Protocol" id="IP" type="IETF">IP</Acronym>
		<SpecLoc>ftp://ftp.isi.edu/in-notes/rfc3252.txt</SpecLoc>
		<Definition xml:lang="en-us">TCP is a binary non-XML format. Ideas of reformulating transport layer protocols such as TCP or IP as XML applications are just april fools.</Definition>
	</Entry>
	<Entry>
		<Acronym expansion="Document Securing Language" id="DSL">DSL</Acronym>
		<MoreInfo>http://www.xml-dsl.com/</MoreInfo>
		<Definition xml:lang="en-us">A language and a system for securing XML documents.</Definition>
	</Entry>
	<Entry>
		<Acronym expansion="Non Colonized Name" id="NCName" type="W3C">NCName</Acronym>
		<SpecLoc>http://www.w3.org/TR/REC-xml-names</SpecLoc>
		<Definition xml:lang="en-us">A NCName is essentially a XML name without a colon.</Definition>
	</Entry>
	<Entry>
		<Acronym expansion="Qualified Name" id="QName" type="W3C">QName</Acronym>
		<SpecLoc>http://www.w3.org/TR/REC-xml-names/</SpecLoc>
		<Definition xml:lang="en-us">A qualified name consists of an optional prefix and the name's local part. The Prefix provides the namespace prefix part of the qualified name, and must be associated with a namespace URI reference in a namespace declaration. The LocalPart provides the local part of the qualified name and must not contain colons.</Definition>
	</Entry>
	<Entry>
		<Acronym expansion="name is not an acronym it's a term from the XML specificiation" id="name" type="W3C">Name</Acronym>
		<SpecLoc>http://www.w3.org/TR/REC-xml</SpecLoc>
		<Definition xml:lang="en-us">A Name is a token beginning with a letter or one of a few punctuation characters, and continuing with letters, digits, hyphens, underscores, colons, or full stops, together known as name characters.</Definition>
	</Entry>
	<Entry>
		<Acronym expansion="document is not an acronym it's a term from the XML specificiation" id="document" type="W3C">document</Acronym>
		<SpecLoc>http://www.w3.org/TR/REC-xml</SpecLoc>
		<Definition xml:lang="en-us">A data object is an XML document if it is well-formed, as defined in this specification. A well-formed XML document may in addition be valid if it meets certain further constraints.</Definition>
	</Entry>
	<Entry>
		<Acronym expansion="validity constraint is not an acronym it's a term from the XML specificiation" id="validityconstraint" type="W3C">validity constraint</Acronym>
		<SpecLoc>http://www.w3.org/TR/REC-xml</SpecLoc>
		<Definition xml:lang="en-us"> A rule which applies to all valid XML documents. Violations of validity constraints are errors; they must, at user option, be reported by validating XML processors.</Definition>
	</Entry>
	<Entry>
		<Acronym expansion="XML processor is not an acronym it's a term from the XML specificiation" type="W3C" id="XMLProcessor">XML processor</Acronym>
		<SpecLoc>http://www.w3.org/TR/REC-xml</SpecLoc>
		<Definition xml:lang="en-us">A software module called an XML processor is used to read XML documents and provide access to their content and structure.</Definition>
	</Entry>
	<Entry>
		<Acronym expansion="Common Alerting Protocol" type="OASIS" id="CAP">CAP</Acronym>
		<SpecLoc>http://www.incident.com/cap/</SpecLoc>
		<Definition>The Common Alerting Protocol (CAP) is a simple XML format for exchanging all-hazard emergency alerts and public warnings over all kinds of networks.  CAP allows a consistent warning message to be disseminated simultaneously over many different warning systems, thus increasing warning effectiveness while simplifying the warning task.  Developed by an ad-hoc working group of emergency management and communication specialists, and endorsed by the non-profit Partnership for Public Warning, the CAP foramt has been adopted as a Committee Specification by the OASIS Emergency Management Technical Committee (http://www.oasis-open.org/committees/emergency/).</Definition>
	</Entry>
	<Entry>
		<Acronym expansion="XML Acroynm Soup" id="XAS">XAS</Acronym>
		<MoreInfo>http://www.xml-acronym-demystifier.org</MoreInfo>
		<Definition xml:lang="en-us">Not really an official acronym, yet. But the reason for starting this project.</Definition>
	</Entry>
	<Entry>
		<Acronym expansion="XML Object Model" id="XOM">XOM</Acronym>
		<MoreInfo>http://www.cafeconleche.org/XOM/</MoreInfo>
		<Definition xml:lang="en-us">XOM is a new XML object model. It is an open source (LGPL), tree-based API for processing XML with Java that strives for correctness and simplicity.</Definition>
	</Entry>
	<Entry>
		<Acronym expansion="eXist  is not an acronym." id="eXist">eXist</Acronym>
		<MoreInfo>http://exist-db.org/</MoreInfo>
		<Definition xml:lang="en-us">eXist is an Open Source native XML database featuring efficient, index-based XPath query processing, extensions for keyword search, XUpdate support and tight integration with existing XML development tools. The database is lightweight, completely written in Java and may be easily deployed in a number of ways, running either as a stand-alone server process, inside a servlet-engine or directly embedded into an application.</Definition>
	</Entry>
	<Entry>
		<Acronym expansion="Tax Markup Language" id="TAXML" type="OASIS">TAXML</Acronym>
		<MoreInfo>http://www.oasis-open.org/committees/tax/</MoreInfo>
		<Definition xml:lang="en-us">The purpose of TAXML is to analyze personal and business tax reporting and compliance information to facilitate interoperability using XML in a way that is open, flexible and international in scope, and to produce a vocabulary of terms, a repository of artifacts including XML templates, documents exchanged for tax compliance, best practices, guidelines and recommendations for practical implementation.</Definition>
	</Entry>
	<Entry>
		<Acronym expansion="Web Services Secure Conversation" id="WS-SecureConversation" type="IBM">WS-SecureConversation</Acronym>
		<AlternateForms>
			<AlternateForm>WS-SecureConversation</AlternateForm>
			<AlternateForm>WS-Secure-Conversation</AlternateForm>
			<AlternateForm>WS SecureConversation</AlternateForm>
			<AlternateForm>WS Secure Conversation</AlternateForm>
			<AlternateForm>WSSC</AlternateForm>
		</AlternateForms>
		<SpecLoc>http://www-106.ibm.com/developerworks/library/ws-secon/</SpecLoc>
		<Definition xml:lang="en-us">WS-SecureConversation defines extensions that build on WS-Security to provide secure communication. Specifically, it defines mechanisms for establishing and sharing security contexts, and deriving session keys from security contexts.</Definition>
	</Entry>
	<Entry>
		<Acronym expansion="Web Services Security Policy" id="WS-SecurityPolicy" type="IBM">WS-SecurityPolicy</Acronym>
		<AlternateForms>
			<AlternateForm>WS SecurityPolicy</AlternateForm>
			<AlternateForm>WS Security Policy</AlternateForm>
			<AlternateForm>WS-Security-Policy</AlternateForm>
		</AlternateForms>
		<SpecLoc>http://www-106.ibm.com/developerworks/library/ws-secpol/</SpecLoc>
		<Definition xml:lang="en-us">WS-SecurityPolicy is an addendum to WS-Security and indicates the policy assertions for WS-Policy which apply to WS-Security.</Definition>
	</Entry>
	<Entry>
		<Acronym expansion="Web Services Trust Language" id="WS-Trust" type="IBM">WS-Trust</Acronym>
		<AlternateForms>
			<AlternateForm>WS Trust</AlternateForm>
		</AlternateForms>
		<SpecLoc>http://www-106.ibm.com/developerworks/library/ws-trust/</SpecLoc>
		<Definition xml:lang="en-us">WS-Trust defines extensions that build on WS-Security to request and issue security tokens and to manage trust relationships.</Definition>
	</Entry>
	<Entry>
		<Acronym expansion="Web Services Policy Assertions Language" id="WS-PolicyAssertions">WS-PolicyAssertion</Acronym>
		<AlternateForms>
			<AlternateForm>WSPolicyAssertions</AlternateForm>
			<AlternateForm>WS-Policy Assertions</AlternateForm>
			<AlternateForm>WS Policy Assertions</AlternateForm>
			<AlternateForm>WSPA</AlternateForm>
		</AlternateForms>
		<SpecLoc>http://www-106.ibm.com/developerworks/library/ws-polas</SpecLoc>
		<Definition xml:lang="en-us">WS-PolicyAssertions specifies a set of common message policy assertions that can be specified within a policy.</Definition>
	</Entry>
	<Entry>
		<Acronym expansion="Web Service Policy Attachment" id="WSPolicyAttachment" type="IBM">WS-PolicyAttachment</Acronym>
		<AlternateForms>
			<AlternateForm>WS-Policy Attachment</AlternateForm>
			<AlternateForm>WS Policy Attachment</AlternateForm>
			<AlternateForm>WSPA</AlternateForm>
		</AlternateForms>
		<SpecLoc>http://www-106.ibm.com/developerworks/library/ws-polatt/</SpecLoc>
		<Definition xml:lang="en-us">WSPolicyAttachment specifies three specific attachment mechanisms for using policy expressions with existing Web Service technologies. Specifically, it defines how to associate policy expressions with WSDL type definitions and UDDI entities. We also define how to associate implementation-specific policy with all or part of a WSDL portType when exposed from a specific implementation.</Definition>
	</Entry>
	<Entry>
		<Acronym expansion="Web Service Policy Framework" id="WSPolicy" type="IBM">WSPolicy</Acronym>
		<AlternateForms>
			<AlternateForm>WS-Policy</AlternateForm>
			<AlternateForm>WS Policy</AlternateForm>
		</AlternateForms>
		<SpecLoc>http://www-106.ibm.com/developerworks/library/ws-polfram/</SpecLoc>
		<Definition xml:lang="en-us">WS-Policy provides a general purpose model and corresponding syntax to describe and communicate the policies of a Web Service. WS-Policy defines a base set of constructs that can be used and extended by other Web Services specifications to describe a broad range of service requirements, preferences, and capabilities.</Definition>
	</Entry>
	<Entry>
		<Acronym expansion="Semantic Web Coordination Group" id="SWCG" type="W3C">SWCG</Acronym>
		<MoreInfo>http://www.w3.org/2001/sw/CG/</MoreInfo>
		<Definition xml:lang="en-us">The Semantic Web Activity has been established to serve a leadership role, in both the design of enabling specifications and the open, collaborative development of technologies that support the automation, integration and reuse of data across various applications. To facilitate the effectiveness and efficiency of this Activity, the Semantic Web Coordination Group is tasked to provide a forum for managing the interrelationships and interdependencies among groups focusing on standards and technologies that relate to this goals of the Semantic Web Activity.</Definition>
	</Entry>
	<Entry>
		<Acronym expansion="Apache eXtensible Interaction System" id="Axis" type="Apache">Axis</Acronym>
		<MoreInfo>http://xml.apache.org</MoreInfo>
		<Definition xml:lang="en-us">Axis is an implementation of the SOAP-Protocol. In detail: Axis is essentially Apache SOAP 3.0. It is a from-scratch rewrite, designed around a streaming model (using SAX internally rather than DOM). The intention is to create a more modular, more flexible, and higher-performing SOAP implementation (relative to Apache SOAP 2.0).</Definition>
	</Entry>
	<Entry>
		<Acronym expansion="Xerces is not an acronym. The tool is named after the Xerces Blue butterfly" id="Xerces">Xerces</Acronym>
		<MoreInfo>http://xml.apache.org</MoreInfo>
		<Definition xml:lang="en-us">Xerces is a validating XML parser available in Java, C++, and Perl.</Definition>
	</Entry>
	<Entry>
		<Acronym expansion="Xalan is not an acronym. The tool is named after a music instrument." id="Xalan" type="Apache">Xalan</Acronym>
		<MoreInfo>http://xml.apache.org</MoreInfo>
		<Definition xml:lang="en-us">Xalan is an XSLT processor for transforming XML documents into HTML, text, or other XML document types. It implements XSL Transformations (XSLT) Version 1.0 and XML Path Language (XPath) Version 1.0.</Definition>
	</Entry>
	<Entry>
		<Acronym expansion="Batik is not an acronym. Batik is a highly evolved art tradition that developed in Java." id="Batik" type="Apache">Batik</Acronym>
		<MoreInfo>http://xml.apache.org</MoreInfo>
		<Definition xml:lang="en-us">Batik is a Java technology based toolkit for applications or applets that want to use images in the Scalable Vector Graphics (SVG) format for various purposes, such as viewing, generation or manipulation.</Definition>
	</Entry>
	<Entry>
		<Acronym expansion="Xindice is not an acronym" id="Xindice" type="Apache">Xindice</Acronym>
		<MoreInfo>http:/xml.apache.org</MoreInfo>
		<Definition xml:lang="en-us">Apache Xindice is a database designed from the ground up to store XML data or what is more commonly referred to as a native XML database.</Definition>
	</Entry>
	<Entry>
		<Acronym expansion="XML Constraint Specification Language" id="XCSL">XCSL</Acronym>
		<MoreInfo>http://www.di.uminho.pt/~jcr/PROJS/xcsl-www/</MoreInfo>
		<Definition xml:lang="en-us">XML Constraint Specification Language, is a domain specific language conceived with the purpose of allowing XML designers to restrict the content of XML documents. It is a simple, and small language useful to write contextual constraints over the textual value of XML elements and attributes.</Definition>
	</Entry>
	<Entry>
		<Acronym expansion="Logic Programming in XML" id="LoPiX">LoPiX</Acronym>
		<MoreInfo>http://user.informatik.uni-goettingen.de/~may/lopix/</MoreInfo>
		<Definition xml:lang="en-us">The LoPiX system is an implementation of the XML querying and data manipulation language XPathLog.</Definition>
	</Entry>
	<Entry>
		<Acronym expansion="XPathLog -- Sorry no further expansion possible" id="XPathLog">XPathLog</Acronym>
		<SpecLoc>http://user.informatik.uni-goettingen.de/~may/lopix/TR149-XPathLog.ps</SpecLoc>
		<Definition xml:lang="en-us">XPathLogic is a logic which is interpreted wrt. XML documents. Its Horn fragment, XPathLog, provides a logic-based language for manipulating and integrating XML data.</Definition>
	</Entry>
	<Entry>
		<Acronym expansion="Asynchronous Service Access Protocol" type="OASIS" id="ASAP">ASAP</Acronym>
		<MoreInfo>http://www.oasis-open.org</MoreInfo>
		<Definition xml:lang="en-us">ASAP should be a very simple extension of Simple Object Access Protocol (SOAP) that enables generic asynchronous Web Services or long-running Web Services. ASAP will complement existing standards and be consistent with the W3C XML Protocol (XMLP) work, including SOAP. ASAP builds upon technical work previously published in the SWAP and AWSP protocols.
</Definition>
	</Entry>
	<Entry>
		<Acronym expansion="Asynchronous Web Services Protocol" id="AWSP">AWSP</Acronym>
		<MoreInfo>http://www.awsp.info</MoreInfo>
		<Definition xml:lang="en-us">AWSP is a extension of the Simple Object Access Protocol (SOAP) to support asynchronous Web Services. In this context, asynchronous means that there is a latency between the request for a resource (or service) and the actual return of that resource (or service results). AWSP is designed to support web services that take more than 60 seconds to create their results.</Definition>
	</Entry>
	<Entry>
		<Acronym id="DBX" expansion="DBX (sorry no further expansion possible)">DBX</Acronym>
		<MoreInfo>http://dbx.idya.net/
</MoreInfo>
		<Definition xml:lang="en-us">DBX is a databae system which is completely written in PHP, and works using XML files as its native format. The database can be queried using standard SQL queries.</Definition>
	</Entry>
	<Entry>
		<Acronym expansion="Abstract Syntax Notation One" id="ASN.1">ASN.1</Acronym>
		<AlternateForms>
			<AlternateForm>ASN1</AlternateForm>
			<AlternateForm>ASN 1</AlternateForm>
		</AlternateForms>
		<SpecLoc>http://asn1.elibel.tm.fr/xml</SpecLoc>
		<Definition xml:lang="en-us">ASN.1 is a notation for defining protocol messages and an important schema language for XML. Data defined in ASN.1 can be encoded either in binary form (by using one of several standard sets of binary "encoding rules" such as PER or BER) or as XML 1.0 documents (by using the XML encoding rules, XER). ASN.1 is widely deployed in the telecommunications networks and used in many protocols in the areas of cellular telephony, security, videoconferencing, air transportation, messaging, directory, biometrics, etc.</Definition>
	</Entry>
	<Entry>
		<Acronym id="BLOAT" expansion="Binary Lexical Octet Ad-hoc Transport" type="IETF">BLOAT</Acronym>
		<SpecLoc>http://www.ietf.org/rfc/rfc3252.txt</SpecLoc>
		<Definition xml:lang="en-us">BLOAT is a reformulation of IP and two transport layer protocols (TCP and UDP) as XML applications. Keep in mind, this is a april's fool RFC!</Definition>
	</Entry>
	<Entry>
		<Acronym id="PIDF" type="IETF" expansion="Presence Information Data Format">PIDF</Acronym>
		<SpecLoc>http://xml.coverpages.org/draft-ietf-impp-cpim-pidf-08.txt</SpecLoc>
		<Definition xml:lang="en-us">The Common Profile for Presence (CPP) Presence Information Data Format (PIDF) is specified as a common presence data format for "application/pidf+xml" to represent the XML MIME entity for PIDF.</Definition>
	</Entry>
	<Entry>
		<Acronym id="RPID" expansion="Rich Presence Information Data Format" type="IETF">RPID</Acronym>
		<SpecLoc>http://www.ietf.org/internet-drafts/draft-ietf-simple-rpid-00.txt</SpecLoc>
		<Definition xml:lang="en-us">The Rich Presence Information Data Format (RPID) adds elements to the Presence Information Data Format (PIDF) that provide additional information about the presentity and its contacts. This information can be translated into call routing behavior or be delivered to watchers, for example. The information is designed so that much of it can be derived automatically, e.g., from calendar files or user activity.</Definition>
	</Entry>
	<Entry>
		<Acronym id="STX" expansion="Streaming Transformations for XML">STX</Acronym>
		<MoreInfo>http://stx.sourceforge.net/</MoreInfo>
		<Definition xml:lang="en-us">Streaming Transformations for XML (STX) is a one-pass transformation language for XML documents that builds on the Simple API for XML (SAX). STX is intended as a high-speed, low memory consumption alternative to XSLT. Since it does not require the construction of an in-memory tree, it is suitable for use in resource constrained scenarios.</Definition>
	</Entry>
	<Entry>
		<Acronym id="JXV" expansion="Java XML View">JXV</Acronym>
		<MoreInfo>http://sourceforge.net/projects/jxv</MoreInfo>
		<Definition xml:lang="en-us">Java XML View is a Java library designed to generate "XML views" of Java Objects, in SAX, DOM, or some other form. JXV also supports "reverse-engeneering" an XML view back into an object.</Definition>
	</Entry>
	<Entry>
		<Acronym id="CAM" expansion="Content Assembly Mechanism" type="OASIS">CAM</Acronym>
		<MoreInfo>http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=cam</MoreInfo>
		<Definition xml:lang="en-us">Content Assembly Mechanism should provide generalized mechanism in XML whereby implementers can deliver the means to bring together business process context and the localized implementation business rules needed to take a raw industry standard schema instance and combine that with actual business information content, context and roles and produce a valid consistent XML document instance.</Definition>
	</Entry>
	<Entry>
		<Acronym id="MTOM" expansion="SOAP Message Transmission Optimization Mechanism" type="W3C">MTOM</Acronym>
		<SpecLoc>http://www.w3.org/TR/soap-12-mtom</SpecLoc>
		<Definition xml:lang="en-us">MTOM describes an abstract feature and a concerete implementation of it for optimizing the transmission and/or wire format of SOAP messages.</Definition>
	</Entry>
	<Entry>
		<Acronym id="XIMS" expansion="eXtensible Information Management System">XIMS</Acronym>
		<MoreInfo>http://xims.uibk.ac.at</MoreInfo>
		<Definition xml:lang="en-us">XIMS is a Information/Content Management System that in its current implementation primarily provides facilities to create and manage web sites. With XIMS it is possible to make use of a flexible recursive role and ACL system for securing content. Using &quot;Department Root&quot; Containers its possible to inherit organizational-unit-wide properties like stylesheet-, or navigation-settings for example.</Definition>
	</Entry>
	<Entry>
		<Acronym id="WSDM" expansion="Web Services Distributed Management" type="OASIS">WSDM</Acronym>
		<MoreInfo>http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=wsdm</MoreInfo>
		<Definition xml:lang="en-us">The purpose of this initiative is to define Web Services management, including using Web Services architecture and technology to manage distributed resource.</Definition>
	</Entry>
	<Entry>
		<Acronym id="OXML" expansion="OXML">OXML</Acronym>
		<MoreInfo>http://freshmeat.net/projects/oxml/?topic_id=809</MoreInfo>
		<Definition xml:lang="en-us">Oxml is a simple wrapper for C++ programmer of the library expat to read XML.</Definition>
	</Entry>
	<Entry>
		<Acronym id="XML-DEV" expansion="XML Developers Mailing List">XML-DEV</Acronym>
		<AlternateForms>
			<AlternateForm>XMLDEV</AlternateForm>
		</AlternateForms>
		<MoreInfo>http://www.xml.org/xml/xmldev.shtml</MoreInfo>
		<Definition xml:lang="en-us">XML-DEV serves as an open, unmoderated list supporting XML implementation and development. XML-DEV emphasizes active participation through code development, creation of protocols and specifications, and other material contributions such as reference resources.</Definition>
	</Entry>
	<Entry>
		<Acronym id="TofuML" expansion="Tofu Markup Language" type="W3C">TofuML</Acronym>
		<Definition xml:lang="en-us">Not an official specification, yet ;-) The abbreviation is solely used within a W3C internal template document clarifying how to prepare submissions.</Definition>
	</Entry>
	<Entry>
		<Acronym id="XAdES" expansion="XML Advanced Electronic Signatures">XAdES</Acronym>
		<MoreInfo>http://www.w3.org/TR/XAdES/</MoreInfo>
		<Definition xml:lang="en-us">XAdES extends the IETF/W3CXML-Signature Syntax and Processing specification into the domain of non-repudiation by defining XML formats for advanced electronic signatures that remain valid over long periods and are compliant with the European "Directive 1999/93/EC of the European Parliament and of the Council of 13 December 1999 on a Community framework for electronic signatures" (also denoted as "the Directive" or the "European Directive" in the rest of the present document) and incorporate additional useful information in common uses cases. This includes evidence as to its validity even if the signer or verifying party later attempts to deny (repudiates) the validity of the signature.</Definition>
	</Entry>
	<Entry>
		<Acronym id="XIndirect" expansion="XML Indirection">XIndirect</Acronym>
		<SpecLoc>http://www.w3.org/TR/2003/NOTE-XIndirect-20030612/</SpecLoc>
		<Definition xml:lang="en-us">XIndirect is a mechanism for using XML to represent indirect addresses in order to augment the core functionality of XLink and XPointer without requiring either of those specifications to themselves require support for indirect addresses. The facilities defined are specifically designed to meet the requirements for systems that support the authoring and management of complex systems of documents.</Definition>
	</Entry>
	<Entry>
		<Acronym id="EGIX" expansion="Embedding Glyph Identifiers in XML Documents">EGIX</Acronym>
		<SpecLoc>http://www.w3.org/TR/EGIX/</SpecLoc>
		<Definition xml:lang="en-us">ISO/IEC 10036 and its technical corrigendum 1 allows registration of glyphs for private or limited use. EGIX provides a mechanism for XML documents to reference to such registered glyphs.</Definition>
	</Entry>
	<Entry>
		<Acronym id="Schematron" expansion="Schematron">Schematron</Acronym>
		<MoreInfo>http://www.ascc.net/xml/resource/schematron/schematron.html</MoreInfo>
		<Definition xml:lang="en-us">  The Schematron  is a Structural Schema Language.
It is currently undergoing ISO standardization to become
ISO/IEC 19757 - DSDL Document Schema Definition Language -
Part 3: Rule-based validation - Schematron.  The Schematron  differs in basic concept from other schema languages in that it not based on grammars but on finding tree patterns in the parsed document. This approach allows many kinds of structures to be represented which are inconvenient and difficult in grammar-based schema languages. If you know XPath or the XSLT expression language, you can start to use  The Schematron  immediately.</Definition>
	</Entry>
	<Entry>
		<Acronym id="EXSLT" expansion="Extending XSLT">EXSLT</Acronym>
		<MoreInfo>http://www.exslt.org</MoreInfo>
		<Definition xml:lang="en-us">EXSLT is a community initiative to provide extensions to XSLT. Its primary goal is to ensure compatibility between XSLT processors for commonly used extensions. It is led by Jeni Tennison with help from Jim Fuller, Dave Pawson and Uche Ogbuji.</Definition>
	</Entry>
	<Entry>
		<Acronym id="RDFWeb" expansion="RDFWeb">RDFWeb</Acronym>
		<MoreInfo>http://rdfweb.com</MoreInfo>
		<Definition xml:lang="en-us">RDFWeb is an experimental linked information system, exploring some interconnected applications of the Semantic Web, beginning with the deployment of FOAF.</Definition>
	</Entry>
	<Entry>
		<Acronym id="XMLfr" expansion="XML France">XMLfr</Acronym>
		<MoreInfo>http://xmlfr.org/</MoreInfo>
		<Definition xml:lang="en-us">&lt;XML&gt; fr is a French site dedicated to XML written in XML by XML experts.</Definition>
	</Entry>
	<Entry>
		<Acronym id="Examplotron" expansion="Examplotron">Examplotron</Acronym>
		<MoreInfo>http://examplotron.org/</MoreInfo>
		<Definition xml:lang="en-us">The purpose of examplotron is to use instance documents as a lightweight schema language-- eventually adding the information needed to guide a validator in the sample documents.</Definition>
	</Entry>
	<Entry>
		<Acronym id="FOAF" expansion="Friend of a friend vocabulary">FOAF</Acronym>
		<MoreInfo>http://xmlns.com/foaf/0.1/</MoreInfo>
		<Definition xml:lang="en-us">FOAF is an RDFWeb project. FOAF is expressed as an RDF Schema, annotated with DAML. FOAF allows the expression of personal information and relationships, and is a useful building block for creating information systems that support online communities.</Definition>
	</Entry>
	<Entry>
		<Acronym id="WSCAF" expansion="Web Services Composite Application Framework" type="SUN">WS-CAF</Acronym>
		<MoreInfo>http://developers.sun.com/techtopics/webservices/wscaf/index.html</MoreInfo>
		<Definition xml:lang="en-us">A collection of three specifications -- Web Service Context (WS-CTX), Web Service Coordination Framework (WS-CF), and Web Service Transaction
		Management (WS-TXM) designed to solve problems that arise when multiple Web Services are used in combination.</Definition>
	</Entry>
	<Entry>
		<Acronym id="WSCTX" expansion="Web Service Context" type="SUN">WS-CTX</Acronym>
		<AlternateForms>
			<AlternateForm>WS Context</AlternateForm>
			<AlternateForm>WS-Context</AlternateForm>
		</AlternateForms>
		<SpecLoc>http://developers.sun.com/techtopics/webservices/wscaf/wsctx.zip</SpecLoc>
		<Definition xml:lang="en-us">A mechanism to manage, share, and access context information among related Web Services.</Definition>
	</Entry>
	<Entry>
		<Acronym id="WSCF" expansion="Web Services Coordination Framework" type="SUN">WS-CF</Acronym>
		<SpecLoc>http://developers.sun.com/techtopics/webservices/wscaf/wscf.zip</SpecLoc>
		<Definition xml:lang="en-us">A software agent to hande context management. Web Services in a composite application register with a coordinator to ensure messages and
		results are correctly communicated.</Definition>
	</Entry>
	<Entry>
		<Acronym id="WSTXM" expansion="Web Services Transaction Management" type="SUN">WS-TXM</Acronym>
		<SpecLoc>http://developers.sun.com/techtopics/webservices/wscaf/wstxm.zip</SpecLoc>
		<Definition xml:lang="en-us">Defines three distinct transaction protocols that can be plugged into the coordination framework for interoperability across existing transaction
		managers, long running compensations, and asynchronous business process flows. It also includes a solution to bridge different transaction models (e.g. MQ Series, JMS).</Definition>
	</Entry>
	<Entry>
		<Acronym id="XQJ" expansion="XQuery API for Java">XQJ</Acronym>
		<MoreInfo>http://www.jcp.org/en/jsr/detail?id=225</MoreInfo>
		<Definition xml:lang="en-us">XQJ tries develop a common API that allows an application to submit queries conforming to the W3C XQuery 1.0
		specification and to process the results of such queries.</Definition>
	</Entry>
	<Entry>
		<Acronym id="WSOM" expansion="Web Services Outsourcing Manager">WSOM</Acronym>
		<MoreInfo>http://asusrl.eas.asu.edu/libing/wsom/wsom.htm</MoreInfo>
		<Definition xml:lang="en-us">A Framework for the dynamic configuration of business processes using Web Services.</Definition>
	</Entry>
	<Entry>
		<Acronym id="BPOL" expansion="Business Process Outsourcing Language">BPOL</Acronym>
		<MoreInfo>http://asusrl.eas.asu.edu/libing/wsom/wsom.htm</MoreInfo>
		<Definition xml:lang="en-us">XML-based description of requirements of a business process outsourcing capturing. To be used by the Web Services Outsourcing Manager (WSOM).</Definition>
	</Entry>
	<Entry>
		<Acronym id="WSRL" expansion="Web Services Relationship Language">WSRL</Acronym>
		<Definition xml:lang="en-us">The Web Services Relationship Language is proposed to capture the Web Services relationships at different granularities as basis of an automated matchmaking process.</Definition>
	</Entry>
	<Entry>
		<Acronym id="CPFR" expansion="Collaborative Planning, Forecasting and Replenishment Schema">CPFR-XML</Acronym>
		<AlternateForms>
			<AlternateForm>CPFR</AlternateForm>
		</AlternateForms>
		<MoreInfo>http://xml.coverpages.org/ni2001-07-11-a.html</MoreInfo>
		<Definition xml:lang="en-us">CPFR-XML establishes guidelines for XML message exchange among systems that implement the Voluntary Interindustry Commerce Standards Association Collaborative Planning, Forecasting and Replenishment principles.</Definition>
	</Entry>
	<Entry>
		<Acronym id="FDCML" expansion="Field Device Configuration Markup Language">FDCML</Acronym>
		<MoreInfo>http://www.fdcml.org/</MoreInfo>
		<Definition xml:lang="en-us">FDCML is a markup language for describing components of an industrial automation system.</Definition>
	</Entry>
	<Entry>
		<Acronym id="VulnXML" expansion="Vulnerability Description Language">VulnXML</Acronym>
		<MoreInfo>http://www.owasp.org/vulnxml/</MoreInfo>
		<Definition xml:lang="en-us">VulnXML describes web application security vulnerabilities. It is intended  to produce checks in a variety of tools that understand the format.</Definition>
	</Entry>
	<Entry>
		<Acronym id="AVDL" expansion="Application Vulnerability Description Language" type="OASIS">AVDL</Acronym>
		<MoreInfo>http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=avdl</MoreInfo>
		<Definition xml:lang="en-us">AVDL is a uniform way of describing application security vulnerabilities. AVDL is an XML definition for exchange of information relating to security vulnerabilities of applications exposed to networks.</Definition>
	</Entry>
	<Entry>
		<Acronym id="XMLAD" expansion="XML Acronym Demystifier">XMLAD</Acronym>
		<MoreInfo>http://www.xml-acronym-demystifier.org</MoreInfo>
		<Definition xml:lang="en-us">The XML Acronym Demystifier is formed as an open-source project. It defines a schema for describing XML acronyms and abbreviations accompanied with an XML document containing descriptons of various XML related terms.</Definition>
	</Entry>
	<Entry>
		<Acronym expansion="Multilingual Upper-Level Electronic Commerce Ontology" id="MULECO">MULECO</Acronym>
		<SpecLoc>http://www.ecimf.org/events/Brussels-20020220/MULECO-CWA-02-02.pdf</SpecLoc>
		<MoreInfo>http://xml.coverpages.org/muleco.html</MoreInfo>
		<Definition xml:lang="en-us">MULECO is a project of the CEN/ISSS Electronic Commerce Workshop. The aim of MULECO is to develop a mechanism that will allow existing ontologies to identify their inter-relationships by identifying the relationships between themselves and a set of terms defined in a multilingual ontology that has been designed specifically to allow people to find terms using their native language.<br/>(Definition adapted from the original specification document)</Definition>
	</Entry>
	<Entry>
		<Acronym expansion="Robotic Markup Language" id="RoboML">RoboML</Acronym>
		<SpecLoc>http://www.roboml.org/techdocs/</SpecLoc>
		<MoreInfo>http://xml.coverpages.org/roboML.html</MoreInfo>
		<Definition xml:lang="en-us">RoboML is an XML-based language for data representation and interchange in robotic applications. Combined with a set of communication protocols, it is aimed at providing a common interface for hardware and software robotic agents communicating via internet networks.<br/>(Definition adapted from the original specification document)</Definition>
	</Entry>
	<Entry>
		<Acronym expansion="Agent-Oriented Rule Markup Language" id="AORML">AORML</Acronym>
		<MoreInfo>http://xml.coverpages.org/aorml.html</MoreInfo>
		<Definition xml:lang="en-us">AORML is a modelling language with following features: <br/>1. it has a richer set of basic ontological concepts, allowing to capture more semantics of a domain, as compared to ER, UML and AUML.<br/>2. unlike the UML, AORML allows to integrate state and behavior modeling in one diagram.<br/>3. it is the first approach that allows to systematically distinguish between external and internal models, and to account for the phenomenon of internalization.<br/>4. it is the first approach that employs and visualizes the important concept of reaction rules for behavior modeling<br/>(Definition adapted from tmitwww.tm.tue.nl/staff/gwagner/AORML/)</Definition>
	</Entry>
	<Entry>
		<Acronym expansion="Extensible Rule Markup Language" id="XRML">XRML</Acronym>
		<SpecLoc>http://xrml.kaist.ac.kr/download/XRML-Ver05.doc</SpecLoc>
		<Definition xml:lang="en-us">XRML is an extension of XML with additional capabilities of representation of rule structure, automatic knowledge processing by exchanged rule, and consistency maintenance of knowledge.<br/>(Definition adapted from the original specification document)</Definition>
	</Entry>
	<Entry>
		<Acronym expansion="Simple Rule Markup Language also: Simulation Reference Markup Language" id="SRML">SRML</Acronym>
		<SpecLoc>http://www.w3.org/TR/2002/NOTE-SRML-20021218</SpecLoc>
		<MoreInfo>http://xml.coverpages.org/srml.html</MoreInfo>
		<Definition xml:lang="en-us">(1) SRML describes a generic rule language consisting of the subset of language constructs common to the popular forward-chaining rule engines. Because it does not use constructs specific to a proprietary vendor language, rules specified using this XML DTD can easily be translated and executed on any conforming rule engine, making it useful as an interlingua for rule exchange between Java rule engines.<br/>(Definition adapted from xml.coverpages.org)<br/>
	(2) SRML is an XML application that can describe the behavior for distributed simulation models, and its runtime environment is software that is capable of executing those models. The goal of SRML is to enable simulations or other content to be served, received, and processed in a standard fashion using Internet technologies and the World Wide Web, just as HTML enables that functionality for text, and MathML enables that functionality for mathematics. (Definition adapted from the original specification document)</Definition>
	</Entry>
	<Entry>
		<Acronym expansion="Relational-Functional Markup Language" id="RFML">RFML</Acronym>
		<SpecLoc>http://www.relfun.org/rfml/</SpecLoc>
		<Definition xml:lang="en-us">RFML  is an XML application for Relfun-style declarative programming and knowledge representation. RFML has been implemented as a (Web-)output syntax for relational-functional knowledge bases and computations as part of the Relfun system. (Web-)input of RFML markup has been implemented via an XSLT stylesheet.<br/>(Definition adapted from xml.coverpages.org)</Definition>
	</Entry>
	<Entry>
		<Acronym expansion="Case Based Markup Language" id="CBML">CBML</Acronym>
		<MoreInfo>http://xml.coverpages.org/cbml.html</MoreInfo>
		<Definition xml:lang="en-us">CBML attempts to mark up cases in XML to enable distributed computing.<br/>(Definition adapted from the original specification document)</Definition>
	</Entry>
	<Entry>
		<Acronym expansion="Exploration and Mining Markup Language" id="XMML">XMML</Acronym>
		<MoreInfo>http://xml.coverpages.org/xmml.html</MoreInfo>
		<Definition xml:lang="en-us">XMML is an encoding for data, not graphics. However, it will be easy to convert XMML datasets into presentation formats, such as the HTML webpage language or SVG vector graphics language, using standard XSLT technology.<br/>(Definition adapted from www.ned.dem.csiro.au/XMML/)</Definition>
	</Entry>
	<Entry>
		<Acronym expansion="Object Oriented Data Technology" id="OODT">OODT</Acronym>
		<MoreInfo>http://xml.coverpages.org/oodt.html</MoreInfo>
		<Definition xml:lang="en-us">The OODT group performs research in object oriented data systems technologies for Section 381, JPL, NASA, and beyond. Initially, the group provided object oriented technology to interferometry projects, specifically targeting the Palomar Testbed Interferometer (PTI) as a prototype activity. Recently, they have expanded this technology to provide interoperability between data systems and are working to create a framework to improve access to existing science data systems, as well as building the foundation for next generation data systems.<br/>(Definition adapted from oodt.jpl.nasa.gov)</Definition>
	</Entry>
	<Entry>
		<Acronym expansion="Newspaper Association of America" id="NAA">NAA</Acronym>
		<MoreInfo>http://xml.coverpages.org/naaClassifiedAds.html</MoreInfo>
		<Definition xml:lang="en-us">NAA is a nonprofit organization representing the $55 billion newspaper industry. NAA members account for nearly 90 percent of the daily circulation in the United States and a wide range of nondaily U.S. newspapers. NAA also has many Canadian and International members. Educators, university newspapers, press associations and suppliers/vendors are also members. The Association focuses on six key strategic priorities that collectively affect the newspaper industry: marketing, public policy, diversity, industry development, newspaper operations and readership.<br/>(Definition adapted from www.naa.org)</Definition>
	</Entry>
	<Entry>
		<Acronym id="XPP" expansion="Common API for XML Pull Parsing">XPP</Acronym>
		<MoreInfo>http://www.xmlpull.org/</MoreInfo>
		<Definition xml:lang="en-us">XPP or XmlPull is an effort to define a simple and elegant pull parsing API that will provide a standardized way to do pull XML parsing from J2ME to J2EE. <br/>Note: XPP is also used as abbreviation for <a URIRef="http://xml.coverpages.org/xpp.html">XML for Publishers and Printers</a>
			<br/>(Definition adapted from www.xmlpull.org)
		</Definition>
	</Entry>
	<Entry>
		<Acronym expansion="Printing Industry Markup Language" id="PrintML">PrintML</Acronym>
		<SpecLoc>http://printml.org/Documents/english_PrintML_paper.pdf</SpecLoc>
		<MoreInfo>http://xml.coverpages.org/printML.html</MoreInfo>
		<Definition xml:lang="en-us">PrintML is the name of a professional application derived from the XML language and intended for the graphic industry.<br/>(Definition adapted from the original specification document)</Definition>
	</Entry>
	<Entry>
		<Acronym expansion="printcafe eProduction eCommerce eXchange" id="PCX">PCX</Acronym>
		<MoreInfo>http://xml.coverpages.org/pcx.html</MoreInfo>
		<Definition xml:lang="en-us">printCafe PCX is designed to be an integration specification for interfacing external systems and services with printCafe solutions. It will map out a number of areas that are important for ongoing integration, and the relationships of these to industry  standards efforts.<br/>(Definition adapted from a news at xml.coverpages.org)</Definition>
	</Entry>
	<Entry>
		<Acronym expansion="Educom Instructional Management Systems Project" id="IMS">IMS</Acronym>
		<SpecLoc>http://www.imsproject.org/pressrelease/ims_wedo.pdf</SpecLoc>
		<MoreInfo>http://xml.coverpages.org/ims.html</MoreInfo>
		<Definition xml:lang="en-us">IMS defines and delivers interoperable, XML-based specifications for exchanging learning content and information about learners among learning system components. IMS members are implementing and adopting these specifications to make learning easier to deliver anywhere and anytime at a lower cost, as well as creating new mechanisms, new contexts, and new products for education and training. IMS specifications already are becoming worldwide de facto standards for defining acquisition requirements and for delivering learning products and services.<br/>(Definition adapted from the original specification document)</Definition>
	</Entry>
	<Entry>
		<Acronym expansion="Shareable Content Object Reference Model Initiative" id="SCORM">SCORM</Acronym>
		<SpecLoc>http://www.adlnet.org/adldocs/Other/SCORMV1.3_SeqAppProfile.zip</SpecLoc>
		<MoreInfo>http://xml.coverpages.org/scorm.html</MoreInfo>
		<Definition xml:lang="en-us">The SCORM is a collection of specifications adapted from multiple sources to provide a comprehensive suite of e-learning capabilities that enable interoperability, accessibility and reusability of Web-based learning content. The work of the ADL Initiative to develop the SCORM is also a process to knit together disparate groups and interests. This reference model aims to coordinate emerging-technologies and commercial and/or public implementations.<br/>(Definition adapted from the original specification document)</Definition>
	</Entry>
	<Entry>
		<Acronym expansion="Learning Material Markup Language" id="LMML">LMML</Acronym>
		<SpecLoc>http://im.fmi.uni-passau.de/projekte/PaKMaS/lmml/11/doc/en/html/index.html</SpecLoc>
		<MoreInfo>http://xml.coverpages.org/lmml.html</MoreInfo>
		<Definition xml:lang="en-us">LMML is an XML-based markup language designed for educational contents (teachware). It provides sublanguages for various educational fields and yet remains further extensible. Therefore it represents not only one single markup language but rather a family of various languages. LMML-CS is one member of this family and thus called an instance of LMML. It is applied to describe topics from the field of computer science.<br/>(Definition adapted from the original specification document)</Definition>
	</Entry>
	<Entry>
		<Acronym expansion="Call Policy Markup Language" id="CPML">CPML</Acronym>
		<MoreInfo>http://xml.coverpages.org/cpml.html</MoreInfo>
		<Definition xml:lang="en-us">CPML is an open language used to simply describe call processing. CPML is an extension of XML that is a standards based, meta-language from which other languages are derived. CPML was developed by DTI to migrate the operations of the telecommunications network, including its features, functions, and enhanced services, out of the world of proprietary operating systems, structured databases, and complex programs or APIs. CPML opens the telecommunications network to basic IP tools that brings order to its complexity and empowers carriers, and ultimately customers, to control, customize, and extend the functionality and usefulness of the telecommunications network.<br/>(Definition adapted from a news at xml.coverpages.org)</Definition>
	</Entry>
	<Entry>
		<Acronym expansion="Broadcast Hypertext Markup Language" id="BHTML">BHTML</Acronym>
		<MoreInfo>http://xml.coverpages.org/xml.html#bhtml</MoreInfo>
		<Definition xml:lang="en-us">BHTML extends HTML by adding attributes for standardizing multimedia object descriptions within HTML OBJECT elements, using the <a glossRef="SMIL">SMIL</a> SWITCH option and introducing an EVENT element to manage the actions to be taken when certain conditions are encountered. The BHTML specification also contains properties for defining 3D effects, controlling the volume of audio presentations, and for clipping and overflowing image areas. BHTML is an application of XML, so is case sensitive and requires all end-tags to be present.<br/>(Definition adapted from a news at xml.coverpages.org)</Definition>
	</Entry>
	<Entry>
		<Acronym id="WSACL" expansion="Web Services Application Component Library">WSACL</Acronym>
		<MoreInfo>http://www.webservices.org/index.php/article/articleview/652/</MoreInfo>
		<Definition xml:lang="en-us">WSACL is designed to enable the rapid access to and delivery of applications from a directory of re-useable components. These will come from leading third party software vendors, existing BT products, or from bespoke solutions that have been developed by BT's consultancy and systems integration teams. Each component will go through an accreditation process to ensure that it meets a defined set of standards for quality, interoperability, scalability and support. It will also incorporate end-to-end service level agreements. This library of re-usable components will reduce the cost, complexity and length of time required for BT to develop and deploy Web Services enabled solutions, thereby assisting it to respond quickly and flexibly to customers' needs.</Definition>
	</Entry>
	<Entry>
		<Acronym id="WSDE" expansion="Web Services Deployment Environment">WSDE</Acronym>
		<MoreInfo>http://www.webservices.org/index.php/article/articleview/652/</MoreInfo>
		<Definition xml:lang="en-us">WSDE is a managed, hosted facility that incorporates both a pilot area and an operational area to enable customers to get Web Services based solutions up and running quickly, with reduced cost and risk. BT will work with customers to set the parameters of the pilot, undertake the technical design and manage the application, hardware and helpdesk.</Definition>
	</Entry>
	<Entry>
		<Acronym id="WSM" expansion="Web Service Managmenet">WSM</Acronym>
		<SpecLoc>http://www.sce.carleton.ca/netmanage/papers/TosicEtAlOOWS02.pdf</SpecLoc>
		<Definition xml:lang="en-us">WSM is management of a particular Web Service or a group of Web Services within the same domain of management responsibility. For example, Web Services provided with oneapplication server might be managed as a group.<br/>(Definition adapted from the original specification document)</Definition>
	</Entry>
	<Entry>
		<Acronym expansion="NACS XML Data Interchange" id="NAXML">NAXML</Acronym>
		<MoreInfo>http://xml.coverpages.org/naxml.html</MoreInfo>
		<Definition xml:lang="en-us">NAXML is the NACS Guidelines for the use of XML in document exchanges in a business-to-business content <br/>(Definition adapted from www.naxml.org)</Definition>
	</Entry>
	<Entry>
		<Acronym expansion="XML Mail Transport Protocol" id="XMTP">XMTP</Acronym>
		<MoreInfo>http://xml.coverpages.org/xmtp.html</MoreInfo>
		<Definition xml:lang="en-us">XMTP is a mapping of MIME/SMTP to XML. MIME is the lingua franca of the Web. Both the HTTP and SMTP protocols are MIME based. As XML gains in popularity it is useful to be able to represent MIME messages as XML documents. This mapping is straightforward and demonstrates handling of binary data in XML documents as base64 encodings. Using XMTP, SMTP messages can be transformed via XSLT into HTML pages for viewing. XMTP has been implemented in Java using SAX and in C++/COM using the IE5 DOM.<br/>(Definition adapted from the original specification document)</Definition>
	</Entry>
	<Entry>
		<Acronym expansion="Genome Annotation Markup Elements" id="GAME">GAME</Acronym>
		<MoreInfo>http://xml.coverpages.org/game.html</MoreInfo>
		<Definition xml:lang="en-us">The goals of GAME, at least in the perspective of the bioxml community, are to provide an XML DTD and tools for annotating biosequence 'features'. bioxml:game is part of bioxml's overall goals of providing a group of 'dtd-lets' for molecular biology. These dtd-let's will be able to be combined to create more expressive dtds. You'll notice that bioxml:game doesn't actually contain a seq dtd. This is because seq is treated in a seperate dtd-let. So it is the goal of bioxml to use a stripped down GAME as the basis for the bioxml seq-features dtd-let.<br/>(Definition adapted from a news at xml.coverpages.org)</Definition>
	</Entry>
	<Entry>
		<Acronym id="WSIPL" expansion="Web Services Integration and Processing Language">WSIPL</Acronym>
		<MoreInfo>http://www.csis.hku.hk/~dbgroup/seminar/seminar020621.htm</MoreInfo>
		<Definition xml:lang="en-us">WSIPL provides specially designed language constructs for integrating and processing Web Services systematically at minimal programming efforts.(Definition adapted from www.csis.hku.hk/~dbgroup/seminar/seminar020621.htm</Definition>
	</Entry>
	<Entry>
		<Acronym id="WSMF" expansion="Web Services Modeling Framework also Web Services Management Framework">WSMF</Acronym>
		<SpecLocs>
			<SpecLoc alt="Web Services Modeling Framework">http://www.cs.vu.nl/~dieter/wese/</SpecLoc>
			<SpecLoc alt="Web Services Management Framework">http://devresource.hp.com/wsmf</SpecLoc>
		</SpecLocs>
		<Definition xml:lang="en-us">(1) The Web Services Modeling Framework provides the appropriate conceptual model for developing and describing web services and their composition.
		(2) The Web Services Management Framework is a logical architecture for managing computing resources, including Web Services.</Definition>
	</Entry>
	<Entry>
		<Acronym expansion="Data Consortium" id="RealEstateStandards">Real Estate Standards</Acronym>
		<MoreInfo>http://xml.coverpages.org/dataConsortium.html</MoreInfo>
		<Definition xml:lang="en-us">Real Estate Standards has been produced and accepted as an authoritative source of definitions and applications of terms used in the institutional equity real estate investment business.<br/>(Definition adapted from www.dataconsortium.org)</Definition>
	</Entry>
	<Entry>
		<Acronym expansion="Physics Markup Language" id="PhysicsML">PhysicsML</Acronym>
		<MoreInfo>http://xml.coverpages.org/physicsML.html</MoreInfo>
		<Definition xml:lang="en-us">The set of XML representations of physics concepts.</Definition>
	</Entry>
	<Entry>
		<Acronym expansion="iCalendar DTD Document" id="xCal">xCal</Acronym>
		<SpecLoc>http://www.globecom.net/ietf/draft/draft-ietf-calsch-many-xcal-01.html</SpecLoc>
		<Definition xml:lang="en-us">xCal defines an XML DTD that corresponds to the iCalendar, Internet Calendaring and Scheduling
		Core Object Specification defined by <a URIRef="http://www.ietf.org/rfc/rfc2445.txt">RFC 2445</a>.</Definition>
	</Entry>
	<Entry>
		<Acronym expansion="Building Construction Extensible Markup Language" id="bcXML">bcXML</Acronym>
		<SpecLoc>http://www.econstruct.org/default_frame.htm</SpecLoc>
		<Definition xml:lang="en-us">bcXML will provide the European Building and Construction industry with a powerful but low cost communication infrastructure that:<br/>(1) Supports electronic business between Clients, Architects and Engineers, Suppliers (of components, systems and services), Contractors and Subcontractors<br/>(2) Is integrated with eCommerce and Design/Engineering applications, and<br/>(3) Supports virtual construction enterprises over the boarders of the individual European member states.</Definition>
	</Entry>
	<Entry>
		<Acronym expansion="OpenMLS and RELML" id="RealEstateListingMarkupLanguage">Real Estate Listing Markup Language</Acronym>
		<MoreInfo>http://xml.coverpages.org/openMLS.html</MoreInfo>
		<Definition xml:lang="en-us">OpenMLS is a web-based real estate listing management system.
		<br/>(Definition adapted from www.oasis-open.org/cover/openMLS.html)</Definition>
	</Entry>
	<Entry>
		<Acronym expansion="European Visual Archive Project" id="EVA">EVA</Acronym>
		<MoreInfo>http://www.eva-eu.org/</MoreInfo>
		<Definition xml:lang="en-us">EVA is a searchable image resource containing historical photographs dating from 1840 up to today. The photographs originate from the collections of the London Metropolitan Archives and the Stadsarchief Antwerpen.<br/>(Definition adapted from www.eva-eu.org)</Definition>
	</Entry>
	<Entry>
		<Acronym expansion="ATLA Serials Project" id="ATLAS">ATLAS</Acronym>
		<MoreInfo>http://purl.org/CERTR/ATLAS</MoreInfo>
		<Definition xml:lang="en-us">ATLAS is an undertaking by the ATLA. Its purpose is to digitize 50 years' worth of 50 journals that deal with the academic study of religion and make them accessible from the Web.<br/>
(Definition adapted from a news at xml.coverpages.org)</Definition>
	</Entry>
	<Entry>
		<Acronym expansion="e-Government Interoperability Framework" id="e-GIF">e-GIF</Acronym>
		<SpecLoc>http://www.govtalk.gov.uk/interoperability/egif.asp</SpecLoc>
		<Definition xml:lang="en-us">The main thrust of the e-GIF is adopting internet and world wide web standards for all government systems. This approach is designed to be pragmatic and aims to reduce the costs and risk of operating information technology systems while keeping the public sector in step with the global internet revolution.<br/>
(Definition adapted from the original specification document)</Definition>
	</Entry>
	<Entry>
		<Acronym expansion="The Australia New Zealand Land Information Council" id="ANZLIC">ANZLIC</Acronym>
		<SpecLoc>http://www.anzlic.org.au</SpecLoc>
		<Definition xml:lang="en-us">ANZLIC is the peak council for public sector spatial data management in Australia and New Zealand. ANZLIC provides an overarching framework within which other national bodies contribute to ANZLIC objectives. Those bodies include the PSMA, the ICSM, and the CGNA.<br/>(Definition adapted from the original specification document)</Definition>
	</Entry>
	<Entry>
		<Acronym expansion="Common Profile for Instant Messaging" id="CPIM">CPIM</Acronym>
		<SpecLoc>http://www.ietf.org/internet-drafts/draft-ietf-impp-cpim-pidf-07.txt</SpecLoc>
		<Definition xml:lang="en-us">Semantics and data formats for common services of Instant Messaging and online Presence, independent of underlying transfer infrastructure, are described.  The CPIM profile meets the requirements specified in <a URIRef="http://www.ietf.org/rfc/rfc2779.txt">IETF RFC 2779</a> using a minimalist approach allowing interoperation of a wide range of IM and Presence systems.<br/>(Definition adapted from the original specification document)</Definition>
	</Entry>
	<Entry>
		<Acronym id="KQML" expansion="Knowledge Query Manipulation Language">KQML</Acronym>
		<MoreInfo>http://www.line56.com/articles/default.asp?ArticleID=4336</MoreInfo>
		<Definition xml:lang="en-us">KQML is complementary to work on representation languages for domain content, including the DARPA Knowledge Sharing Initiative's KIF. KQML has also been used to transmit object-oriented data, and a wide range of information can be accumulated. KQML is a language for programs to use to communicate attitudes about information, such as querying, stating, believing, requiring, achieving, subscribing, and offering. KQML is indifferent to the format of the information itself, thus KQML expressions will often contain subexpressions in other so-called content languages.<br/>(Definition adapted from the original specification document)</Definition>
	</Entry>
	<Entry>
		<Acronym id="TTWG" expansion="Timed Text Working Group" type="W3C">TTWG</Acronym>
		<SpecLoc>http://www.w3.org/AudioVideo/TT/ttcharter20020901.html</SpecLoc>
		<Definition>The mission of the TTWG is to develop an XML based format used for the representation of streamable text synchronized with some other timed media, like audio and video. A typical application is real time captioning of movies on the Web (e.g. integrated in <a glossRef="SMIL">SMIL</a>).<br/>
(Definition adapted from the original specification document)</Definition>
	</Entry>
	<Entry>
		<Acronym id="SYMM" type="W3C" expansion="Synchronized Multimedia Activity">SYMM</Acronym>
		<SpecLoc>http://www.w3.org/AudioVideo/</SpecLoc>
		<Definition>W3C's SYMM has focused on the design of a new language for choreographing multimedia presentations where audio, video, text and graphics are combined in real-time. The language, <a glossRef="SMIL">SMIL</a> is written as an XML application and is currently a W3C Recommendation. Simply put, it enables authors to specify what should be presented when, enabling them to control the precise time that a sentence is spoken and make it coincide with the display of a given image appearing on the screen.<br/>(Definition adapted from the 				original specification document)</Definition>
	</Entry>
	<Entry>
		<Acronym expansion="Voice Extensible Markup Language" type="W3C" id="VoiceXML">VoiceXML</Acronym>
		<SpecLoc>http://www.w3.org/TR/voicexml/</SpecLoc>
		<Definition xml:lang="en-us">VoiceXML is designed for creating audio dialogs that feature synthesized speech, digitized audio, recognition of spoken and DTMF key input, recording of spoken input, telephony, and mixed-initiative conversations. Its major goal is to bring the advantages of web-based development and content delivery to interactive voice response applications.<br/>(Definition adapted from the original specification document)</Definition>
	</Entry>
	<Entry>
		<Acronym id="LI-XML" expansion="LegalXML Lawful Intercept XML">LI-XML</Acronym>
		<SpecLoc>http://www.oasis-open.org/committees/legalxml-intercept/</SpecLoc>
		<MoreInfo>http://www.oasis-open.org/news/oasis_news_01_23_03.shtml</MoreInfo>
		<Definition xml:lang="en-us">The purpose of the LI-XML is to produce a structured, end-to-end <a glossRef="LegalXML">LegalXML</a> Lawful Interception Process framework consisting of XML standards and authentication mechanisms, including the development and harmonization of identifiable related XML standards and XML translations of ASN.1 modules, including proprietary ones made available in accordance with IPR policies.<br/>(Definition adapted from the original specification document)</Definition>
	</Entry>
	<Entry>
		<Acronym id="MMAP" expansion="Mobile Message Access Protocol Specification">MMAP</Acronym>
		<SpecLoc>http://xml.coverpages.org/SMS-MMAPv12a.pdf</SpecLoc>
		<MoreInfo>http://xml.coverpages.org/ni2003-01-21-a.html</MoreInfo>
		<Definition xml:lang="en-us">MMAP provides a standard framework for mobile messaging over <a glossRef="SOAP">SOAP</a> and HTTP. It provides support for service identification and billing and provides a standard way of supporting session-oriented communication. MMAP supports generic XML operations as SOAP body elements.<br/>(Definition adapted from the original specification document)</Definition>
	</Entry>
	<Entry>
		<Acronym expansion="Web Coverage Service" id="WCS">WCS</Acronym>
		<SpecLoc>http://www.opengis.org/techno/02-024r1.pdf</SpecLoc>
		<MoreInfo>http://www.opengis.org/info/techno/request.htm</MoreInfo>
		<Definition xml:lang="en-us">The WCS supports the networked interchange of geospatial data as &quot;coverages&quot; containing values or properties of geographic locations. Unlike the WMS, which filters and portrays spatial data to return static maps (server-rendered as pictures), the WCS provides access to intact (unrendered) geospatial information, as needed for client-side rendering, multi-valued coverages, and input into scientific models and other clients beyond simple viewers.<br/>(Definition adapted from the original specification
		document)</Definition>
	</Entry>
	<Entry>
		<Acronym expansion="WS-Reliability" type="OASIS" id="WS-Reliability">WS-Reliability</Acronym>
		<SpecLocs>
			<SpecLoc>http://www.sonicsoftware.com/docs/ws_reliability.pdf</SpecLoc>
			<SpecLoc>http://xml.fujitsu.com/en/about/WS-ReliabilityV1.0.pdf</SpecLoc>
			<SpecLoc>http://www.hitachi.co.jp/Prod/comp/soft1/wsrm/WS-ReliabilityV1.0.pdf</SpecLoc>
			<SpecLoc>http://otn.oracle.com/tech/webservices/htdocs/spec/WS-ReliabilityV1.0.pdf</SpecLoc>
			<SpecLoc>http://sunonedev.sun.com/platform/technologies/ws-reliability.v1.0.pdf</SpecLoc>
		</SpecLocs>
		<MoreInfo>http://xml.coverpages.org/xmlPapers200301.html#WS-Rel</MoreInfo>
		<Definition xml:lang="en-us">WS-Reliability is a <a glossRef="SOAP">SOAP</a>-based protocol for exchanging SOAP messages with guaranteed delivery, no duplicates, and guaranteed message ordering. WS-Reliability is defined as SOAP header extensions, and is independent of the underlying protocol. This specification contains a binding to HTTP.<br/>(Definition adapted from the original specification document)</Definition>
	</Entry>
	<Entry>
		<Acronym expansion="Extensible MultiModal Annotation Language" id="EMMA">EMMA</Acronym>
		<SpecLoc>http://www.w3.org/TR/2003/NOTE-EMMAreqs-20030113</SpecLoc>
		<Definition xml:lang="en-us">EMMA is the markup language used to represent human input to a multimodal application. As such, it may be seen in terms of the W3C Multimodal Interaction Framework as the exchange mechanism between user input devices and the interaction management capabilities of an application.<br/>(Definition adapted from the original specification document)</Definition>
	</Entry>
	<Entry>
		<Acronym id="VoxML" expansion="VoxML sorry no further expansion possible">VoxML</Acronym>
		<Definition xml:lang="en-us">VoxML markup language for voice applications allows developers to simply and easily add speech interfaces to their Web applications or content. The VoxML language uses Internet technologies and standards, so developing VoxML apps is similar to developing Web applications. These dialogues are interpreted by voice browsers, just as HTML pages are interpreted by web browsers. Theoretically allowing anyone to connect with Internet information from any telephone or voice-enabled device.</Definition>
	</Entry>
	<Entry>
		<Acronym expansion="Agent Communication Language" id="ACL">ACL</Acronym>
		<SpecLoc>http://www.fipa.org/specs/fipa00061/SC00061G.pdf</SpecLoc>
		<MoreInfo>http://www.line56.com/articles/default.asp?ArticleID=4336</MoreInfo>
		<Definition xml:lang="en-us">A FIPA ACL message contains a set of one or more message parameters. Precisely which parameters are needed for effective agent communication will vary according to the situation; the only parameter that is mandatory in all ACL messages is the performative, although it is expected that most ACL messages will also contain sender, receiver and content parameters.
		<br/>(Definition adapted from the original specification document)</Definition>
	</Entry>
	<Entry>
		<Acronym expansion="Global XML Web Services Architecture" type="Microsoft" id="GXA">GXA</Acronym>
		<MoreInfo>http://msdn.microsoft.com/webservices/understanding/gxa/default.aspx?pull=/library/en-us/dngxa/html/understandgxa.asp</MoreInfo>
		<Definition xml:lang="en-us">GXA is a collection of infrastructure protocols built on top of <a glossRef="SOAP">SOAP</a>. GXA encompasses several specifications. Each one focuses on resolving a particular type of functionality, such as security, routing, or transactions. The specifications are designed to be composable, meaning you can use any combination of them that's appropriate to satisfy business requirements.<br/>(Definition adapted from the original specification document)</Definition>
	</Entry>
	<Entry>
		<Acronym expansion="Hospitality Industry Technology Integration Standards" id="HITIS">HITIS</Acronym>
		<MoreInfo>http://xml.coverpages.org/hitis.html</MoreInfo>
		<Definition xml:lang="en-us">The HITIS Project is maintained by the American Hotel and Motel Association.
		The goal of HITIS is to identify general functions (of property management systems) and standardize their implementation.
		In addition, a common data dictionary for hospitality relevant data is to be developed.<br/>(Definition adapted from an article
		at xml.coverpages.org)</Definition>
	</Entry>
	<Entry>
		<Acronym expansion="MDC Open Information Model" id="OIM">OIM</Acronym>
		<MoreInfo>http://xml.coverpages.org/mdc-oim.html</MoreInfo>
		<Definition xml:lang="en-us">MDC OIM is a vendor-neutral and technology-independent specification of core metadata
       	 types found in operational, data warehousing, and knowledge management environments. XML is the standard format for
       	 the interchange of metadata using the MDC OIM<br/>(Definition adapted from a news at xml.coverpages.org)</Definition>
	</Entry>
	<Entry>
		<Acronym expansion="Commerce XML" id="cXML">cXML</Acronym>
		<SpecLoc>http://xml.cxml.org/current/cXMLUsersGuide.pdf</SpecLoc>
		<Definition xml:lang="en-us">cXML allows buying organizations, suppliers, service providers, and intermediaries to
		communicate using a single, standard, open language.<br/>(Definition adapted from the original specification
		document)</Definition>
	</Entry>
	<Entry>
		<Acronym expansion="Marketplace XML" id="mpXML">mpXML</Acronym>
		<MoreInfo>http://xml.coverpages.org/mpXML.html</MoreInfo>
		<Definition xml:lang="en-us">mpXML is an open XML standard for the exchange of electronic commerce marketplace information.
		<br/>(Definition adapted from an article at xml.coverpages.org)</Definition>
	</Entry>
	<Entry>
		<Acronym expansion="Open Catalog Protocol" id="OCP">OCP</Acronym>
		<SpecLoc>http://www.martsoft.com/ocp/semantics.htm</SpecLoc>
		<Definition xml:lang="en-us">OCP is an XML-based application level protocol that enables the searching, retrieval, and updating
		of product information and the exchange of complex data between product catalogs.<br/>(Definition adapted from the original
		specification-website)</Definition>
	</Entry>
	<Entry>
		<Acronym expansion="eCatalog XML" id="eCX">eCX</Acronym>
		<SpecLoc>http://www.ecx-xml.org/docs/ecx_3_0_specification.pdf</SpecLoc>
		<Definition xml:lang="en-us">eCX is a DTD that provides a method for electronic catalog interoperability. It is unique
		because it deals with the difficult problem of dynamic categorization and attributes in electronic catalogs.<br/>(Definition
		adapted from the original specification document)</Definition>
	</Entry>
	<Entry>
		<Acronym expansion="Hybrid Mail Language" id="HML">HML</Acronym>
		<MoreInfo>http://xml.coverpages.org/hml.html</MoreInfo>
		<Definition xml:lang="en-us">HML is a universal language to be used between customers and hybrid mail operators,
		as well as between hybrid mail operators<br/>(Definition adapted from an article at xml.coverpages.org)</Definition>
	</Entry>
	<Entry>
		<Acronym expansion="Product Data Markup Language" id="PDML">PDML</Acronym>
		<SpecLoc>http://www.pdit.com/pdml/whitepap.pdf</SpecLoc>
		<Definition xml:lang="en-us">PDML is a set of XML vocabularies and a usage structure for deploying product data on
		the Internet and making it visible to DoD weapon system support personnel.<br/>(Definition adapted from the original
		specification document)</Definition>
	</Entry>
	<Entry>
		<Acronym expansion="Product Definition Exchange" id="PDX">PDX</Acronym>
		<SpecLoc>http://www.pdxstandard.org/</SpecLoc>
		<MoreInfo>http://xml.coverpages.org/pdx.html</MoreInfo>
		<Definition xml:lang="en-us">PDX Standard Group consists of leading corporations and standards organizations in
		electronics manufacturing.<br/>(Definition adapted from the original specification-website)</Definition>
	</Entry>
	<Entry>
		<Acronym expansion="ECIX Timing Diagram Markup Language" id="TDML">TDML</Acronym>
		<MoreInfo>http://xml.coverpages.org/tdml.html</MoreInfo>
		<Definition xml:lang="en-us">TDML is an open industry-standard language for the exchange of interactive timing diagrams
		for digital systems<br/>(Definition adapted from an article at xml.coverpages.org)</Definition>
	</Entry>
	<Entry>
		<Acronym expansion="UML eXchange Format" id="UXF">UXF</Acronym>
		<SpecLoc>http://www.yy.cs.keio.ac.jp/~suzuki/project/uxf/</SpecLoc>
		<Definition xml:lang="en-us">UXF is a XML-based model interchange format for UML, which is a standard software
		modeling language. UXF is a simple and well-structured format to encode, publish, access and exchange UML models,
		and allows UML to be highly interoperable.<br/>(Definition adapted from the original specification document)</Definition>
	</Entry>
	<Entry>
		<Acronym expansion="XML Localization Interchange File Format" id="XLIFF">XLIFF</Acronym>
		<SpecLoc>http://www.oasis-open.org/committees/xliff/</SpecLoc>
		<Definition xml:lang="en-us">XLIFF is intended to give any software provider a single interchange file format that can be
		understood by any localization provider. It is loosely based on the OpenTag version 1.2 specification and borrows from
		the TMX 1.2 specification.<br/>(Definition adapted from the original specification document)</Definition>
	</Entry>
	<Entry>
		<Acronym expansion="Translation Memory Exchange" id="TMX">TMX</Acronym>
		<SpecLoc>http://www.lisa.org/tmx/tmx14-20020710.htm</SpecLoc>
		<Definition xml:lang="en-us">TMX is XML-compliant. It also uses various ISO standards for date/time, language codes,
		and country codes.<br/>(Definition adapted from the original specification document)</Definition>
	</Entry>
	<Entry>
		<Acronym expansion="Molecular Dynamics [Markup] Language" id="MoDL">MoDL</Acronym>
		<MoreInfo>http://xml.coverpages.org/modl.html</MoreInfo>
		<Definition xml:lang="en-us">MoDL is a new XML application for simulation data from molecular dynamics.
		<br/>(Definition adapted from an article at xml.coverpages.org)</Definition>
	</Entry>
	<Entry>
		<Acronym expansion="Covad xLink API" id="XMLBasedDSLProvisioning">XML-Based DSL Provisioning</Acronym>
		<SpecLoc>http://xlink.covad.com/</SpecLoc>
		<Definition xml:lang="en-us">Covad xLink is a XML-based application programming interface to enable flow-through
		DSL provisioning between Covad and its channel partners to create a seamless supply chain<br/>(Definition adapted
		from the original specification-website)</Definition>
	</Entry>
	<Entry>
		<Acronym expansion="Global Engineering Networking Initiative" id="GEN">GEN</Acronym>
		<MoreInfo>http://www.c-lab.de/gen/overview.html </MoreInfo>
		<Definition xml:lang="en-us">GEN is an open co-operation of industry and university partners and has started in 1994.
		The mission of the GEN Initiative is to provide a global electronic market place for engineers.<br/>(Definition adapted
		from www.c-lab.de/gen/overview.html)</Definition>
	</Entry>
	<Entry>
		<Acronym expansion="Value Chain Markup Language" id="VCML">VCML</Acronym>
		<SpecLoc>http://www.vcml.net/</SpecLoc>
		<Definition xml:lang="en-us">VCML is a comprehensive set of XML-based, industry-specific vocabularies and
		documents required to conduct business over the Internet. The VCML transaction sets provide an XML representation
		of industry-specific EDI transactions, allowing industry members to leverage their existing business rules and semantics
		for Internet-based electronic transaction exchange.<br/>(Definition adapted from the original specification-website)</Definition>
	</Entry>
	<Entry>
		<Acronym expansion="TransportationXML" id="tXML">tXML</Acronym>
		<SpecLoc>http://www.logistics.com/products/architecture/tXML.asp</SpecLoc>
		<Definition xml:lang="en-us">tXML defines the system interfaces to the application components, which comprise
		the OptiManage, OptiBid and OptiYield product solutions. These interfaces and data flows are the details that
		define the larger business processes between shippers and carriers that include management, procurement and
		optimization of transportation services.<br/>(Definition adapted from the original specification document)</Definition>
	</Entry>
	<Entry>
		<Acronym expansion="Tracker XML" id="TXML">TXML</Acronym>
		<SpecLoc>http://www.trackernet.org/TXMLSpec.pdf</SpecLoc>
		<Definition xml:lang="en-us">TXML is a type of XML designed specifically for export control transactions and
		international trade.<br/>(Definition adapted from the original specification document)</Definition>
	</Entry>
	<Entry>
		<Acronym expansion="Uniform Code Council" id="UCC">UCC</Acronym>
		<SpecLoc>http://www.uc-council.org/</SpecLoc>
		<Definition xml:lang="en-us">The mission of the UCC, Inc., is to take a global leadership role in establishing and promoting
		multi-industry standards for product identification and related electronic communication.<br/>(Definition adapted from
		www.uc-council.org)</Definition>
	</Entry>
	<Entry>
		<Acronym expansion="Global Uniform Interoperable Data Exchange" id="GUIDE">GUIDE</Acronym>
		<SpecLoc>http://www.xmlguide.org/GUIDE/guide_01.pdf</SpecLoc>
		<Definition xml:lang="en-us">GUIDE is a XML format for describing business information interchanges between a set
		of endpoints exchanging transactions.<br/>(Definition adapted from the original specification document)</Definition>
	</Entry>
	<Entry>
		<Acronym expansion="Implementation Guideline Markup Language" id="igML">igML</Acronym>
		<SpecLoc>http://www.foresightcorp.com/igmldev/</SpecLoc>
		<Definition xml:lang="en-us">igML is a new XML based mark-up language for the rendition of EDI implementation
		guidelines and standards. igML will serve many of the same purposes as SEF, and the IMPDEF and DIRDEF
		EDIFACT messages, with important extensions.</Definition>
	</Entry>
	<Entry>
		<Acronym expansion="Universal Data Element Framework" id="UDEF">UDEF</Acronym>
		<SpecLoc>http://www.udef.com/</SpecLoc>
		<Definition xml:lang="en-us">UDEF is described as a Dewey Decimal-Like Indexing System for the Web<br/>
		(Definition adapted from an article at xml.coverpages.org)</Definition>
	</Entry>
	<Entry>
		<Acronym expansion="OpenTravel Alliance" id="OTA">OTA</Acronym>
		<SpecLoc>http://www.opentravel.org</SpecLoc>
		<Definition xml:lang="en-us">OTA is a self-funded, non-profit organization, which is a comprised of major airlines,
		hoteliers, car rental companies, leisure suppliers, travel agencies, global distribution systems (GDS), technology
		providers and other interested parties working to create and implement industry-wide, open e-business specifications.
		<br/>(Definition adapted from www.opentravel.org)</Definition>
	</Entry>
	<Entry>
		<Acronym expansion="Gene Expression Markup Language" id="GEML">GEML</Acronym>
		<MoreInfo>http://xml.coverpages.org/geml.html</MoreInfo>
		<Definition xml:lang="en-us">GEML is a proposed standard for Gene Expression data<br/>(Definition adapted from the
		original specification document)</Definition>
	</Entry>
	<Entry>
		<Acronym expansion="Investment Research Markup Language" id="IRML">IRML</Acronym>
		<MoreInfo>http://xml.coverpages.org/irml.html</MoreInfo>
		<Definition xml:lang="en-us">IRML is an initial specification for a proposed open-architecture standard which would
		benefit all facets of financial information technology<br/>(Definition adapted from an article at xml.coverpages.org)
		</Definition>
	</Entry>
	<Entry>
		<Acronym expansion="Extensible Financial Reporting Markup Language" id="XFRML">XFRML</Acronym>
		<MoreInfo>http://xml.coverpages.org/xfrml.html</MoreInfo>
		<Definition xml:lang="en-us">XFRML is a framework that will allow the financial community a standards-based method to
		prepare, publish in a variety of formats, exchange and analyze financial reports and the information they contain.<br/>
		(Definition adapted from an article at xml.coverpages.org)</Definition>
	</Entry>
	<Entry>
		<Acronym expansion="Encoded Archival Context Initiative" id="EAC">EAC</Acronym>
		<MoreInfo>http://xml.coverpages.org/eac.html</MoreInfo>
		<Definition xml:lang="en-us">EAC is a prototype standard for representing description of people, families, and corporate bodies
		<br/>(Definition adapted from the original specification document)</Definition>
	</Entry>
	<Entry>
		<Acronym expansion="XML Query Language" id="XQL">XQL</Acronym>
		<SpecLoc>http://www.w3.org/TandS/QL/QL98/pp/xql.html</SpecLoc>
		<Definition xml:lang="en-us">XQL is a notation for addressing and filtering the elements and text of XML documents. XQL is a natural 			extension to the XSL pattern syntax. It provides a concise, understandable notation for pointing to specific elements and for searching for 		nodes with particular characteristics.<br/>(Definition adapted from the original specification document)</Definition>
	</Entry>
	<Entry>
		<Acronym expansion="Straight Through Processing Markup Language" id="STPML">STPML</Acronym>
		<MoreInfo>http://xml.coverpages.org/stpml.html</MoreInfo>
		<Definition xml:lang="en-us">STPML is an XML message specification designed to meet the requirements of straight-through processing 		for the financial securities industry. STPML enables straight-through processing by supporting most industry
		standards for data exchange.<br/>(Definition adapted from the original specification document)</Definition>
	</Entry>
	<Entry>
		<Acronym expansion="Internet Open Trading Protocol" id="IOTP">IOTP</Acronym>
		<SpecLoc>http://link.springer-ny.com/link/service/series/0558/bibs/2360/23600352.htm</SpecLoc>
		<MoreInfo>http://xml.coverpages.org/otp.html</MoreInfo>
		<Definition xml:lang="en-us">IOTP provides an interoperable framework for Internet commerce. It is payment system independent and 		encapsulates payment systems such as SET, Mondex, CyberCash, DigiCash, GeldKarte, etc.<br/>(Definition adapted from a news at 			xml.coverpages.org)</Definition>
	</Entry>
	<Entry>
		<Acronym expansion="XML Messaging Specification" id="XMSG">XMSG</Acronym>
		<SpecLoc>http://www.w3.org/TR/xmsg/</SpecLoc>
		<Definition xml:lang="en-us">XMSG is a specification for using XML to send messages that contain a set of XML documents, embedded 		non-XML data, and references to non-XML documents in a fashion that supports scalable transactions and operates on a participant model.		<br/>(Definition adapted from the original specification document)</Definition>
	</Entry>
	<Entry>
		<Acronym expansion="Bank Internet Payment System" id="BIPS">BIPS</Acronym>
		<SpecLoc>http://www.fstc.org/projects/bips/spec/BIPS_spec_v1p1.pdf</SpecLoc>
		<Definition xml:lang="en-us">BIPS is a freely available protocol for sending payment instructions safely over the Internet<br/>(Definition 		adapted from the original specification document)</Definition>
	</Entry>
	<Entry>
		<Acronym expansion="Virtual Reality Modeling Language" id="VRML">VRML</Acronym>
		<SpecLoc>http://www.web3d.org/technicalinfo/specifications/eai/index.html</SpecLoc>
		<Definition xml:lang="en-us">VRML is a file format for describing interactive 3D objects and worlds. VRML is designed to be used on the 		Internet, intranets, and local client systems. VRML is also intended to be a universal interchange format for integrated 3D
		graphics and multimedia. VRML may be used in a variety of application areas such as engineering and scientific visualization,
		multimedia presentations, entertainment and educational titles, web pages, and shared virtual worlds.<br/>(Definition adapted
		from the original specification document)</Definition>
	</Entry>
	<Entry>
		<Acronym expansion="Electronic Book Exchange" id="EBX">OeBX</Acronym>
		<AlternateForms>
			<AlternateForm>EBX</AlternateForm>
		</AlternateForms>
		<MoreInfo>http://xml.coverpages.org/ebx.html</MoreInfo>
		<Definition xml:lang="en-us"/>
	</Entry>
	<Entry>
		<Acronym expansion="Ontology Interchange Language" id="OIL">OIL</Acronym>
		<SpecLoc>http://www.ontoknowledge.org/oil/TR/oil.long.html</SpecLoc>
		<MoreInfo>http://www.ontoknowledge.org/oil/</MoreInfo>
		<Definition xml:lang="en-us">OIL is a proposal for a web-based representation and inference layer for ontologies, which
        combines the widely used modeling primitives from frame-based languages with the formal semantics and reasoning services
        provided by description logics.<br/>(Definition adapted from the original specification document)</Definition>
	</Entry>
	<Entry>
		<Acronym expansion="Customer Identity / Name and Address Markup Language" id="CIMLNAML">CIML, NAML</Acronym>
		<MoreInfo>http://xml.coverpages.org/ciml.html</MoreInfo>
		<Definition xml:lang="en-us">The format is no longer supported and has been replaced by xNL, xAL.</Definition>
	</Entry>
	<Entry>
		<Acronym expansion="Meaning Definition Language" id="MDL">MDL</Acronym>
		<SpecLoc>http://www.charteris.com/mdl/MDLWhitePaper.pdf</SpecLoc>
		<MoreInfo>http://www.charteris.com/mdl/</MoreInfo>
		<Definition xml:lang="en-us">MDL is a language which tries to act as a bridge between XML structure and meaning expressed precisely, in 		XML. It defines how the structures of an XML document (elements, attributes and XPaths) convey meanings (about objects, properties and
        	associations).</Definition>
	</Entry>
	<Entry>
		<Acronym expansion="Relational Markup Language" id="RML">RML</Acronym>
		<MoreInfo>http://xml.coverpages.org/rml.html</MoreInfo>
		<Definition xml:lang="en-us">RML is an XML-based language used by Roam and its industry partners. Roam is a wireless
       	software and service provider which helps companies move online business onto any handheld wireless device, such as
        	mobile phones and PDAs<br/>(Definition adapted from a news at xml.coverpages.org)</Definition>
	</Entry>
	<Entry>
		<Acronym expansion="Materials Property Data Markup Language" id="MatML">MatML</Acronym>
		<SpecLoc>ftp://www.ceramics.nist.gov/matml/MatMLv20.pdf</SpecLoc>
		<Definition xml:lang="en-us">The MatML effort is addressing the problems of interpretation and interoperability through the
        	development of an XML for materials data that will permit the storage, transmission, and processing of materials property
        	data distributed via the World Wide Web.<br/>(Definition adapted from a news at xml.coverpages.org)</Definition>
	</Entry>
	<Entry>
		<Acronym expansion="NISO Circulation Interchange Protocol" id="NCIP">NCIP</Acronym>
		<SpecLoc>http://www.niso.org/standards/</SpecLoc>
		<Definition xml:lang="en-us">NCIP defines a repertoire of messages and associated rules of syntax and semantics for use
        	by applications to:<br/>(1) perform the functions necessary to lend items; <br/>(2) provide controlled access to electronic
       	 resources;<br/> (3) facilitate co-operative management of these functions.<br/>(Definition adapted from a news at
        	xml.coverpages.org)</Definition>
	</Entry>
	<Entry>
		<Acronym expansion="Governmental Markup Language" id="GovML">GovML</Acronym>
		<SpecLoc>http://www.egov-project.org/deliverables.htm</SpecLoc>
		<MoreInfo>http://www.egov-project.org/</MoreInfo>
		<Definition xml:lang="en-us">GovML will be specified as a recommendation for a new XML vocabulary that will define
        	and support particular data structures, which are necessary to support the life-event approach towards the delivery
        	of online public services.<br/>(Definition adapted from the original specification document)</Definition>
	</Entry>
	<Entry>
		<Acronym expansion="Election Markup Language" id="EML">EML</Acronym>
		<SpecLoc>http://www.oasis-open.org/committees/election/index.shtml</SpecLoc>
		<MoreInfo>http://xml.coverpages.org/eml.html</MoreInfo>
		<Definition xml:lang="en-us">EML is a reliable, accurate and trusted XML specification for the structured interchange of data
        	among hardware, software and service vendors who provide election systems and services.<br/>(Definition adapted from
        	the original specification document)</Definition>
	</Entry>
	<Entry>
		<Acronym expansion="PEO Interchange XML Initiative" id="PIXIT">PIXIT</Acronym>
		<MoreInfo>http://xml.coverpages.org/pixit.html</MoreInfo>
		<Definition xml:lang="en-us">PIXIT aims to support and enable synergy between several Army, Navy, Air Force, and Marine Corps
        	command and control (C2) PEOs with respect to XML use.<br/>(Definition adapted from a news at xml.coverpages.org)</Definition>
	</Entry>
	<Entry>
		<Acronym expansion="OMG Common Warehouse Metadata Interchange" type="OMG" id="CWMI">CWMI</Acronym>
		<SpecLoc>http://www.omg.org/technology/cwm/</SpecLoc>
		<MoreInfo>http://www.omg.org/technology/cwm/</MoreInfo>
		<Definition xml:lang="en-us">The Common Warehouse Metamodel (CWM) is a specification that describes metadata interchange among 		data warehousing, business intelligence, knowledge management and portal technologies.</Definition>
	</Entry>
	<Entry>
		<Acronym expansion="OMG Model Driven Architecture" id="MDA">MDA</Acronym>
		<MoreInfo>http://www.omg.org/mda/</MoreInfo>
		<Definition xml:lang="en-us">The MDA defines an approach to IT system specification that separates the specification of system
        	functionality from the specification of the implementation of that functionality on a specific technology platform. To this end, the
        	MDA defines an architecture for models that provides a set of guidelines for structuring specifications expressed as models.</Definition>
	</Entry>
	<Entry>
		<Acronym expansion="Multimodal Presentation Markup Language" id="MPML">MPML</Acronym>
		<SpecLoc>http://www.miv.t.u-tokyo.ac.jp/MPML/jp/2.0e/spec20e.txt</SpecLoc>
		<Definition xml:lang="en-us">MPML is a language developed to enable the description of multimodal presentation based on character
        	agents in easier way<br/>(Definition adapted from www.miv.t.u-tokyo.ac.jp/MPML/en/2.0e/)</Definition>
	</Entry>
	<Entry>
		<Acronym expansion="MPEG-21 Part 2: Digital Item Declaration Language" id="DIDL">DIDL</Acronym>
		<SpecLoc>http://xml.coverpages.org/MPEG21-WG-11-N3971-200103.pdf</SpecLoc>
		<Definition xml:lang="en-us">Digital Items are defined as structured digital objects, including a standard representation and
        	identification, and meta-data. This entity is the fundamental unit of distribution and transaction within the MPEG-21 framework
        	as a whole; it has, however, no further technical meaning.<br/>(Definition adapted from the original specification document)</Definition>
	</Entry>
	<Entry>
		<Acronym expansion="Precision Graphics Markup Language" id="PGML">PGML</Acronym>
		<SpecLoc>http://www.w3.org/TR/1998/NOTE-PGML</SpecLoc>
		<MoreInfo>http://xml.coverpages.org/xml.html#pgml</MoreInfo>
		<Definition xml:lang="en-us">PGML is a 2D scalable graphics language designed to meet both the simple vector graphics needs
        	of casual users and the precision needs of graphics artists. PGML uses the imaging model common to the PostScript language
        	and Portable Document Format (PDF); it also contains additional features to satisfy the needs of Web applications.
        	<br/>(Definition adapted from the original specification document)</Definition>
	</Entry>
	<Entry>
		<Acronym expansion="Image Markup Language" id="IML">IML</Acronym>
		<MoreInfo>http://xml.coverpages.org/iml.html</MoreInfo>
		<Definition xml:lang="en-us">IML is an XML application for describing the content and applications handled by a Simputer.
        	The goal of IML is to enable handheld computers, (that have limitations in the display size and input capabilities), to access and
        	render content from the Internet.<br/>(Definition adapted from the original specification document)</Definition>
	</Entry>
	<Entry>
		<Acronym id="XIL" expansion="various expansions">XIL</Acronym>
		<SpecLocs>
			<SpecLoc alt="XML Import Language">http://xineo.sourceforge.net/xil/</SpecLoc>
			<SpecLoc alt="Extensible Indexing Language">http://www.infoloom.com/gcaconfs/WEB/paris2000/S08-04.HTM</SpecLoc>
		</SpecLocs>
		<MoreInfo>http://www.infoloom.com/gcaconfs/WEB/paris2000/S08-04.HTM</MoreInfo>
		<Definition xml:lang="en-us">The acronym has various expansions<br/>a) XML Integrator Language<br/>b) Xineo XIL:  (XML Import 			Language) is an XML language for transforming various record-based data sources into XML documents, and provides a fully functional XIL 		processing implementation. This implementation has built-in support for relational (via JDBC) and structured text (like CSV) sources, and is 		extensible thanks to its public API, allowing dynamic integration of new data source implementations.<br/>c) Extensible Indexing Language: 		</Definition>
	</Entry>
	<Entry>
		<Acronym id="XL" expansion="XML Programming Language">XL</Acronym>
		<Definition xml:lang="en-us">XL is an XML programming language designed for the implementation of Web services. XL is portable and
        	fully compliant with W3C standards such as <a glossRef="XQuery">XQuery</a>, <a glossRef="SOAP">XML Protocol</a>, and
        	<a glossRef="XSD">XML Schema</a>. One of the key features of XL is that it allows programmers to concentrate on the logic of their
        	application. XL provides high-level and declarative constructs for actions which are typically carried out in the implementation of a
        	Web service; e.g., logging, error handling, retry of actions, workload management, events, etc. Issues such as performance tuning
        	(e.g., caching, horizontal partitioning, etc.) should be carried out automatically by an implementation of the language. This way, the
        	productivity of the programmers, the ability of evolution of the programs, and the chances to achieve good performance are substantially 		enhanced.</Definition>
	</Entry>
	<Entry>
		<Acronym expansion="Historical Event Markup and Linking" id="HEML">HEML</Acronym>
		<SpecLoc>http://www.heml.org/description/heml-description.pdf</SpecLoc>
		<Definition xml:lang="en-us">The HEML project provides a means of coordinating and navigating disparate historical materials on
        	the internet.<br/>(Definition adapted from the original specification document)</Definition>
	</Entry>
	<Entry>
		<Acronym expansion="xNAL Name and Address Standard" id="xNLxAL">xNL, xAL</Acronym>
		<SpecLoc>http://www.oasis-open.org/committees/ciq/download.shtml</SpecLoc>
		<Definition xml:lang="en-us">With the advent of XML as a defacto standard for representing data, OASIS has developed an
        	application independent XML standard for name and address data management xNAL.  xNAL does not include all the address
        	components throughout the world. But that is where the power of XML comes into play. It is extensively scalable and extendable
        	allowing xNAL to evolve as more additional components are identified. xNAL is broken into two components namely: xNL and xAL.
        	<br/>(Definition adapted from the original specification document)</Definition>
	</Entry>
	<Entry>
		<Acronym expansion="Telecommunications Markup Language" id="tML">tML</Acronym>
		<SpecLoc>http://www.atis.org/pub/tcif/ecic/liaison/1M101001.pdf</SpecLoc>
		<Definition xml:lang="en-us">tML, an application of XML, is being considered for use in the TMN architecture primarily due to its
       	 flexibility for structured information definition.<br/>(Definition adapted from the original specification document)</Definition>
	</Entry>
	<Entry>
		<Acronym expansion="MicroArray and Gene Expression Markup Language" id="MAGE-ML">MAGE-ML</Acronym>
		<SpecLoc>http://cgi.omg.org/docs/lifesci/01-10-01.pdf</SpecLoc>
		<Definition xml:lang="en-us">The MAGE-ML model defines the elements for supporting gene expression data.
       	 Because the exchange of gene expression data can be abstracted from the source from which it was obtained, it can be
        	represented by XML files, which are both human readable and machine readable.<br/>(Definition adapted from the original
        	specification document)</Definition>
	</Entry>
	<Entry>
		<Acronym expansion="An XML Query Language" id="XQuery" type="W3C">XQuery</Acronym>
		<AlternateForms>
			<AlternateForm>XML Query</AlternateForm>
		</AlternateForms>
		<SpecLoc>http://www.w3.org/TR/xquery/</SpecLoc>
		<Definition xml:lang="en-us">XML is a versatile markup language, capable of labeling the information content of diverse data sources 		including structured and semi-structured documents, relational databases, and object repositories. A query language that uses the 			structure of XML intelligently can express queries across all these kinds of data, whether physically stored in XML or viewed as XML via 		middleware.<br/>(Definition adapted from the original specification document)</Definition>
	</Entry>
	<Entry>
		<Acronym expansion="Vocabulary Markup Language" id="VocML">VocML</Acronym>
		<SpecLoc>http://orc.dev.oclc.org:5103/nkos/bin00003.bin</SpecLoc>
		<Definition xml:lang="en-us">VocML is a XML DTD/Schema which will support the structured representation of a wide range
        of KOS resources, including authority files, hierarchical thesauri (including those with polyhierarchies), classification schemes,
        digital gazetteers, and subject heading lists<br/>(Definition adapted from a news at xml.coverpages.org)</Definition>
	</Entry>
	<Entry>
		<Acronym expansion="XML Process Definition Language" id="XPDL">XPDL</Acronym>
		<SpecLoc>http://www.wfmc.org/standards/docs/xpdl_010522..pdf</SpecLoc>
		<Definition xml:lang="en-us">XPDL forms a common interchange standard that enables products to continue to
        	support arbitrary internal representations of process definitions with an import/export function to map
        	to/from the standard at the product boundary.<br/>(Definition adapted from the original specification document)</Definition>
	</Entry>
	<Entry>
		<Acronym expansion="Green Building XML" id="gbXML">gbXML</Acronym>
		<SpecLoc>http://www.gbxml.org/schema/0-32/index.html</SpecLoc>
		<MoreInfo>http://xml.coverpages.org/gbXML.html</MoreInfo>
		<Definition xml:lang="en-us">gbXML was developed to facilitate the transfer of building information essential to designing
        	resource efficient buildings. XML is a type of computer language that allows intelligent programs to communicate information
        	with no human interaction. This approach allows building designers to focus on what they want to - designing beautiful buildings
        	that will meet their owner&apos;s needs with minimal cost and environmental impact with intelligent computer applications.
        	<br/>(Definition adapted from www.gbxml.org)</Definition>
	</Entry>
	<Entry>
		<Acronym expansion="UK Digital National Framework" id="DNF">DNF</Acronym>
		<SpecLoc>http://www.ordnancesurvey.co.uk/downloads/dnf/prodspec3/d00506.pdf</SpecLoc>
		<Definition xml:lang="en-us">DNF data is designed for use as an intelligent digital map within geographical information systems and 		database systems. In DNF data there is a closer correspondence between data features and discrete real-world objects than has been the 		case in previous generations of Ordnance Survey products.<br/>(Definition adapted from the original specification document)</Definition>
	</Entry>
	<Entry>
		<Acronym expansion="Personalized Print Markup Language" id="PPML">PPML</Acronym>
		<SpecLoc>http://www.podi.org/content.asp?nav</SpecLoc>
		<Definition xml:lang="en-us">The main purpose of the PPML language, compared to most earlier languages, is to provide object-level
        	addressability and reusability.<br/>(Definition adapted from the original specification document)</Definition>
	</Entry>
	<Entry>
		<Acronym expansion="Structured Graph Format" id="SGF">SGF</Acronym>
		<SpecLoc>http://decweb.ethz.ch/WWW7/1850/com1850.htm</SpecLoc>
		<Definition xml:lang="en-us">SGF is an XML compliant markup language based on structured graphs, for capturing Web sites&apos; 		structure<br/>(Definition adapted from the original specification document)</Definition>
	</Entry>
	<Entry>
		<Acronym id="WSE" type="Microsoft" expansion="Web Service Enhancements">WSE</Acronym>
		<MoreInfo>http://msdn.microsoft.com/webservices/building/wse/default.aspx</MoreInfo>
		<Definition xml:lang="en-us">Web Services Enhancements for Microsoft .NET provides advanced Web services functionality for
        	Microsoft Visual Studio .NET and Microsoft .NET Framework developers to support the latest Web services capabilities. Enterprise
        	ready applications can be developed quickly with the support of security features such as digital signature and encryption, message
        	routing capabilities, and the ability to include message attachments that are not serialized into XML. Functionality is based on the
       	 WS-Security, WS-Routing, WS-Attachments and DIME specifications.<br/>(Definition adapted form the Web Page)</Definition>
	</Entry>
	<Entry>
		<Acronym expansion="Customer Profile Exchange" id="CPEX">CPEX</Acronym>
		<SpecLoc>http://www.cpexchange.org/standard/cpexchangev1_0F.pdf</SpecLoc>
		<Definition xml:lang="en-us">The CPEX specification is a new standard that takes into account the traditional customer-facing facets
        	of an enterprise, such as customer support, call centers, sales tracking, marketing campaigns and order tracking.
        	<br/>(Definition adapted from the original specification document)</Definition>
	</Entry>
	<Entry>
		<Acronym expansion="Standards for Technology in Automotive Retail" id="STAR">STAR</Acronym>
		<MoreInfo>http://xml.coverpages.org/star.html</MoreInfo>
		<Definition xml:lang="en-us">STAR is a non-profit, auto industry-wide initiative to create voluntary IT standards for how manufacturers,
        	dealers, and customers communicate with each other. This will result in lower costs, more accurate and timely data, and increased levels
        	of customer satisfaction.<br/>(Definition adapted from www.starstandard.org)</Definition>
	</Entry>
	<Entry>
		<Acronym expansion="Universal Business Language" id="UBL">UBL</Acronym>
		<SpecLoc>http://www.oasis-open.org/committees/ubl/index.shtml</SpecLoc>
		<Definition xml:lang="en-us">The purpose of the UBL vocabulary is it to act as a library of XML business documents (purchase orders,
        	invoices, etc.) by modifying an already existing library of XML schemas to incorporate the best features of other existing XML business
        	libraries.<br/>(Definition adapted from the original specification document)</Definition>
	</Entry>
	<Entry>
		<Acronym expansion="UN/CEFACT XML Business Document Library Project" id="XBDL">XBDL</Acronym>
		<SpecLoc>http://xml.coverpages.org/XBDL-PP-R1.html</SpecLoc>
		<MoreInfo>http://xml.coverpages.org/xbdl.html</MoreInfo>
		<Definition xml:lang="en-us">The XBDL project team is a group of experts with broad knowledge in the area of Electronic Business (ebXML,
        	UN/EDIFACT, and national EDI/eBusiness), ebXML Core Components, semantic and context related development.
        	<br/>(Definition adapted from the original specification document)</Definition>
	</Entry>
	<Entry>
		<Acronym expansion="DISA Registry Initiative" id="DRIVE">DRIVE</Acronym>
		<MoreInfo>http://xml.coverpages.org/drive.html</MoreInfo>
		<Definition xml:lang="en-us">DRIVE is a program to deploy the technology outlined in the ebXML specifications for a standard online
        	index of items needed by companies to do business in particular industries.<br/>(Definition adapted from www.disa.org)</Definition>
	</Entry>
	<Entry>
		<Acronym expansion="Global Commerce Initiative" id="GCI">GCI</Acronym>
		<MoreInfo>http://xml.coverpages.org/gci.html</MoreInfo>
		<Definition xml:lang="en-us">GCI is a voluntary body created in October 1999 to improve the performance of the international supply
         	chain for consumer goods through the collaborative development and endorsement of recommended standards and key business 			processes.<br/>(Definition adapted from www.globalcommerceinitiative.org/oas/gci/GCI.home)</Definition>
	</Entry>
	<Entry>
		<Acronym expansion="DII Common Operating Environment" id="COE">COE</Acronym>
		<SpecLoc>http://dod-ead.mont.disa.mil/web/general.jsp</SpecLoc>
		<Definition xml:lang="en-us">COE  provides a framework for developing and fielding DoD systems that meet the needs of the warfighter
        	in a global information environment<br/>(Definition adapted from the original specification document)</Definition>
	</Entry>
	<Entry>
		<Acronym expansion="NISO Digital Talking Books" id="DTB">DTB</Acronym>
		<SpecLoc>http://www.niso.org/standards/resources/Z39-86-2002.pdf</SpecLoc>
		<Definition xml:lang="en-us">DTB are for blind, visually impaired, physically handicapped, learning-disabled, or otherwise
        	print-disabled readers. Its purpose is to ensure interoperability across service organizations and vendors providing content
        	and playback systems to the target population.<br/>(Definition adapted from the original specification document)</Definition>
	</Entry>
	<Entry>
		<Acronym expansion="Extensible Rights Markup Language" id="XrML">XrML</Acronym>
		<SpecLoc>http://www.xrml.org/get_XrML.asp</SpecLoc>
		<MoreInfo>http://xml.coverpages.org/xrml.html</MoreInfo>
		<Definition xml:lang="en-us">XrML is the Digital Rights Language of choice. XrML provides a universal method for securely
        	specifying and managing rights and conditions associated with all kinds of resources including digital content as well as services.
        	<br/>(Definition adapted from the original specification document)</Definition>
	</Entry>
	<Entry>
		<Acronym expansion="Open Digital Rights Language" id="ODRL">ODRL</Acronym>
		<SpecLoc>http://www.w3.org/TR/odrl/</SpecLoc>
		<Definition xml:lang="en-us">ODRL is a proposed language for the digital rights management community for the standardisation of
        	expressing rights information over content. The ODRL is intended to provide flexible and interoperable mechanisms to
        	support transparent and innovative use of digital resources in publishing, distributing and consuming of electronic publications,
        	digital images, audio and movies, learning objects, computer software and other creations in digital form
        	<br/>(Definition adapted from the original specification document)</Definition>
	</Entry>
	<Entry>
		<Acronym expansion="Extensible Access Control Markup Language" id="XACML">XACML</Acronym>
		<SpecLoc>http://xml.coverpages.org/XACML-CS-v10.pdf</SpecLoc>
		<MoreInfo>http://xml.coverpages.org/xacml.html</MoreInfo>
		<Definition xml:lang="en-us">XACML is an XML specification for expressing policies for information access
        over the Internet. XACML design is taking place within the OASIS technical committee.
        <br/>(Definition adapted from the original specification document)</Definition>
	</Entry>
	<Entry>
		<Acronym expansion="Information Technology Markup Language" id="ITML">ITML</Acronym>
		<SpecLoc>http://xml.coverpages.org/ITMLProvisioning20010219.pdf</SpecLoc>
		<MoreInfo>http://xml.coverpages.org/itml.html</MoreInfo>
		<Definition xml:lang="en-us">ITML is a set of specifications of protocols, message formats and best practices in the
        ASP and ASP aggregation market to provide seamless integration of partners and business processes. It is based upon
        open-standards, particularly XML and HTTP. It is an implementation of the ITML Messaging and Protocol Specification.
        <br/>(Definition adapted from the original specification document)</Definition>
	</Entry>
	<Entry>
		<Acronym expansion="Extensible Provisioning Protocol" id="EPP">EPP</Acronym>
		<SpecLoc>http://www.ietf.org/internet-drafts/draft-ietf-provreg-epp-07.txt</SpecLoc>
		<Definition xml:lang="en-us">EPP is an XML text protocol that permits multiple service providers to perform
        object provisioning operations using a shared central object repository.<br/>(Definition adapted from the original
        specification document)</Definition>
	</Entry>
	<Entry>
		<Acronym expansion="XML Common Biometric Format" id="XCBF">XCBF</Acronym>
		<SpecLoc>http://www.oasis-open.org/committees/xcbf/#documents</SpecLoc>
		<MoreInfo>http://xml.coverpages.org/xcbf.html</MoreInfo>
		<Definition xml:lang="en-us">The XCBF defines a common set of secure XML encodings for the patron formats
        specified in CBEFF<br/>(Definition adapted from the original specification document)</Definition>
	</Entry>
	<Entry>
		<Acronym expansion="Security Services Markup Language" id="S2ML">S2ML</Acronym>
		<SpecLoc>http://xml.coverpages.org/S2MLV08a.pdf</SpecLoc>
		<MoreInfo>http://xml.coverpages.org/s2ml.html</MoreInfo>
		<Definition xml:lang="en-us">S2ML is a protocol for two security services: authentication and authorization. The
        protocol consists of request and response pairs of XML documents for each service.
        <br/>(Definition adapted from the original specification document)</Definition>
	</Entry>
	<Entry>
		<Acronym expansion="XML Access Control Language" id="XACL">XACL</Acronym>
		<SpecLoc>http://www.trl.ibm.com/projects/xml/xss4j/docs/xacl-spec.html</SpecLoc>
		<MoreInfo>http://xml.coverpages.org/xacl.html</MoreInfo>
		<Definition xml:lang="en-us">XACL is used to specify an object-subject-action-condition oriented policy in the context
        of a particular XML document. The notion of subject comprises identity, group, and role. The granularity of object can be
        as fine as the one of XML nodes within the document though the current version is restricted to elements and attributes.
        Currently, there are four possible actions (read, write, create and delete), but the structure of the language is not limited to these.
        <br/>(Definition adapted from the original specification document)</Definition>
	</Entry>
	<Entry>
		<Acronym expansion="Digest Values for DOM" id="DOMHASH">DOMHASH</Acronym>
		<SpecLoc>http://xml.coverpages.org/draft-hiroshi-dom-hash-00.txt</SpecLoc>
		<Definition xml:lang="en-us">DOMHASH are digest (hash) values of XML objects</Definition>
	</Entry>
	<Entry>
		<Acronym expansion="Signed Document Markup Language" id="SDML">SDML</Acronym>
		<SpecLoc>http://www.w3.org/TR/1998/NOTE-SDML-19980619/</SpecLoc>
		<MoreInfo>http://xml.coverpages.org/sdml.html</MoreInfo>
		<Definition xml:lang="en-us">SDML is the generic document structuring and signing part of the FSML.
        <br/>(Definition adapted from the original specification document)</Definition>
	</Entry>
	<Entry>
		<Acronym expansion="Financial Services Markup Language" id="FSML">FSML</Acronym>
		<SpecLoc>http://www.echeck.org/library/ref/fsml-v1500a.pdf</SpecLoc>
		<MoreInfo>http://xml.coverpages.org/fsml.html</MoreInfo>
		<Definition xml:lang="en-us">FSML is an SGML like mark-up language designed to allow the creation of electronic
        financial documents. FSML can be used for several applications. One is to create, and sign generic financial
        (or even non-financial) documents. Another, more specific application, is to create, and process Electronic Checks,
        and their associated documents. One chapter will describe the use of FSML for generic documents.
        <br/>(Definition adapted from the original specification document)</Definition>
	</Entry>
	<Entry>
		<Acronym expansion="Open Software Description Format" id="OSD">OSD</Acronym>
		<SpecLoc>http://www.w3.org/TR/NOTE-OSD.html</SpecLoc>
		<Definition xml:lang="en-us">OSD an application of XML, is a vocabulary used for describing software packages
        and their dependencies for heterogeneous clients.<br/>(Definition adapted from the original specification document)
        </Definition>
	</Entry>
	<Entry>
		<Acronym expansion="Log Markup Language" id="LOGML">LOGML</Acronym>
		<SpecLoc>http://www.cs.rpi.edu/~puninj/LOGML/draft-logml.html</SpecLoc>
		<MoreInfo>http://xml.coverpages.org/logML.html</MoreInfo>
		<Definition xml:lang="en-us">LOGML is an XML application for describing Log Reports of Web servers.
        <br/>(Definition adapted from the original specification document)</Definition>
	</Entry>
	<Entry>
		<Acronym expansion="Extensible Log Format" id="XLF">XLF</Acronym>
		<SpecLoc>http://www.docuverse.com/xlf/NOTE-XLF-19980721-all.html</SpecLoc>
		<MoreInfo>http://www.docuverse.com/xlf/</MoreInfo>
		<Definition xml:lang="en-us">XLF is a set of DTD fragments, recommendations and API's intended to provide a
        complete, open, interoperable, and extensible logging infrastructure<br/>(Definition adapted from the original
        specification document)</Definition>
	</Entry>
	<Entry>
		<Acronym expansion="Emergency Management XML Consortium" id="EM-XML">EM-XML</Acronym>
		<AlternateForms>
			<AlternateForm>EMXML</AlternateForm>
		</AlternateForms>
		<Definition xml:lang="en-us">A organization standardizing the Common Alerting Protocol (CAP) and others.</Definition>
	</Entry>
	<Entry>
		<Acronym expansion="Aggregation and Logging of User Requests" id="ALURe">ALURe</Acronym>
		<SpecLoc>http://www.alurexml.org/W3Cproposal.htm</SpecLoc>
		<MoreInfo>http://xml.coverpages.org/alureXML.html</MoreInfo>
		<Definition xml:lang="en-us">ALURe defines a grammatical standard to satisfy the above requirement.
        ALURe can be used by User Assistance Systems to communicate how users arrive, and expect to arrive, at
        a solution using an application's User Assistance System in real time.<br/>(Definition adapted from the original
        specification document)</Definition>
	</Entry>
	<Entry>
		<Acronym expansion="XML Document Navigation Language" id="XDNL">XDNL</Acronym>
		<SpecLoc>http://www.w3.org/TR/2000/NOTE-xdnl-20000323/</SpecLoc>
		<MoreInfo>http://xml.coverpages.org/xdnl.html</MoreInfo>
		<Definition xml:lang="en-us">With the diversity of accessing devices, WWW content needs to be designed for both
        PC and non-PC devices, so that it can be appropriately navigated and rendered by each type of devices.
        This note focuses on the navigation of content which helps the user to easily browse a huge document on relatively
        small devices. The general idea of navigation is explained, and a new language, the XML Document Navigation
        Language (XDNL) was proposed.<br/>(Definition adapted from the original specification document)</Definition>
	</Entry>
	<E