<?xml version="1.0" encoding="UTF-8"?>
<bibliography>
	<reference name="kau03">
		<names type="author">
			<person>
				<givenname>Roland</givenname>
				<surname>Kaufmann</surname>
			</person>
		</names>
		<date value="2003-05"/>
		<abstract>
			<richtext>
				<p>The work presented here extends an existing algorithm for testing if an inclusion relation exists between two markup schemata, to only take into account the parts of the grammar that have been used in a given subset of its language. Statistics for this purpose are gathered in combination with validation when documents are entered and are stored along with them in the repository. This modified subtyping relation is used to determine compatibility with the current database when a schema is upgraded.</p>
			</richtext>
		</abstract>
		<address>Bergen, Norway</address>
		<publisher type="university">University of Bergen</publisher>
		<title>Efficiently Locating Schema Incompatibilities in an Extensible Markup Language</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-xmlschema" weight="0.8"/>; </p>
			</richtext>
		</annotation>
		<identifier type="uri" resourceType="application/pdf">www.ub.uib.no/elpub/2003/h/413001/Hovedoppgave.pdf</identifier>
		<howpublished>Ph.D. Thesis</howpublished>
	</reference>
	<reference name="hlo05">
		<names type="author">
			<person>
				<givenname>Pavel</givenname>
				<surname>Hlousek</surname>
			</person>
		</names>
		<date value="2005"/>
		<address>Prague, Czech Republic</address>
		<publisher type="university">Charles University</publisher>
		<title>XPath, XSLT, XQuery: Formal Approach</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-xpath" weight="0.8"/>; <keywordref type="topic-xslt2" weight="0.8"/>; <keywordref type="topic-xquery" weight="0.8"/>; </p>
			</richtext>
		</annotation>
		<identifier type="uri" resourceType="application/pdf">http://kocour.ms.mff.cuni.cz/~hlousek/papers/XSXQcomp.pdf</identifier>
		<howpublished>Ph.D. Thesis</howpublished>
	</reference>
	<reference name="lie05">
		<names type="author">
			<person>
				<givenname>Håkon Wium</givenname>
				<surname>Lie</surname>
			</person>
		</names>
		<date value="2005-03"/>
		<abstract>
			<richtext>
				<p>The topic of this thesis is style sheet languages for structured documents on the web. Due to characteristics of the web — including a screen-centric publishing model, a multitude of output devices, uncertain delivery, strong user preferences, and the possibility for later binding between content and style — the hypothesis is that the web calls for different style sheet languages than does traditional electronic publishing. Style sheet languages that were developed and used prior to the web are analyzed and compared with style sheet proposals for the web between 1993-1996. The dissertation describes the design of a web-centric style sheet language known as Cascading Style Sheets (CSS). CSS has several notable features including: cascading, pseudo-classes and pseudo-elements, forward-compatible parsing rules, support for different media types, and a strong emphasis on selectors. Problems in CSS are analyzed, and recommended future research is described.</p>
			</richtext>
		</abstract>
		<address>Oslo, Norway</address>
		<publisher type="university">University of Oslo</publisher>
		<title>Cascading Style Sheets</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-css"/>; </p>
			</richtext>
		</annotation>
		<identifier type="uri">http://people.opera.com/howcome/2006/phd/</identifier>
		<howpublished>Ph.D. Thesis</howpublished>
	</reference>
	<reference name="man03">
		<names type="author">
			<person>
				<givenname>Murali</givenname>
				<surname>Mani</surname>
			</person>
		</names>
		<date value="2003"/>
		<publisher type="university">University of California, Los Angeles</publisher>
		<title>Data Modeling using XML Schemas</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-xmlschema" weight="0.8"/>; <keywordref type="topic-erex"/>; (undefined keyword: xgrammar); </p>
			</richtext>
		</annotation>
		<identifier type="uri" resourceType="application/pdf">http://www.cs.wpi.edu/~mmani/dissertation.pdf</identifier>
		<howpublished>Ph.D. Thesis</howpublished>
	</reference>
	<reference name="doa02b">
		<names type="author">
			<person>
				<givenname>AnHai</givenname>
				<surname>Doan</surname>
			</person>
		</names>
		<date value="2002"/>
		<publisher type="university">University of Washington</publisher>
		<title>Learning to Map between Structured Representations of Data</title>
		<identifier type="uri" resourceType="application/pdf">http://anhai.cs.uiuc.edu/home/thesis/anhai-thesis.pdf</identifier>
		<howpublished>Ph.D. Thesis</howpublished>
	</reference>
	<reference name="phe98">
		<names type="author">
			<person>
				<givenname>Thomas Arthur</givenname>
				<surname>Phelps</surname>
			</person>
		</names>
		<date value="1998"/>
		<publisher type="university">University of California, Berkeley</publisher>
		<title>Multivalent Documents: Anytime, Anywhere, Any Type, Every Way User-Improvable Digital Documents and Systems</title>
		<identifier type="uri" resourceType="text/html">http://www.cs.berkeley.edu/~phelps/Multivalent/papers/dissertation-abstract.html</identifier>
		<howpublished>Ph.D. Thesis</howpublished>
	</reference>
	<reference name="fie00">
		<names type="author">
			<person>
				<givenname>Roy T.</givenname>
				<surname>Fielding</surname>
			</person>
		</names>
		<date value="2000"/>
		<abstract>
			<richtext>
				<p>The World Wide Web has succeeded in large part because its software architecture has been designed to meet the needs of an Internet-scale distributed hypermedia system. The Web has been iteratively developed over the past ten years through a series of modifications to the standards that define its architecture. In order to identify those aspects of the Web that needed improvement and avoid undesirable modifications, a model for the modern Web architecture was needed to guide its design, definition, and deployment. Software architecture research investigates methods for determining how best to partition a system, how components identify and communicate with each other, how information is communicated, how elements of a system can evolve independently, and how all of the above can be described using formal and informal notations. My work is motivated by the desire to understand and evaluate the architectural design of network-based application software through principled use of architectural constraints, thereby obtaining the functional, performance, and social properties desired of an architecture. An architectural style is a named, coordinated set of architectural constraints. This dissertation defines a framework for understanding software architecture via architectural styles and demonstrates how styles can be used to guide the architectural design of network-based application software. A survey of architectural styles for network-based applications is used to classify styles according to the architectural properties they induce on an architecture for distributed hypermedia. I then introduce the Representational State Transfer (REST) architectural style and describe how REST has been used to guide the design and development of the architecture for the modern Web. REST emphasizes scalability of component interactions, generality of interfaces, independent deployment of components, and intermediary components to reduce interaction latency, enforce security, and encapsulate legacy systems. I describe the software engineering principles guiding REST and the interaction constraints chosen to retain those principles, contrasting them to the constraints of other architectural styles. Finally, I describe the lessons learned from applying REST to the design of the Hypertext Transfer Protocol and Uniform Resource Identifier standards, and from their subsequent deployment in Web client and server software.</p>
			</richtext>
		</abstract>
		<address>Irvine, California</address>
		<publisher type="university">University of California, Irvine</publisher>
		<title>Architectural Styles and the Design of Network-based Software Architectures</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-rest"/>; </p>
			</richtext>
		</annotation>
		<identifier type="uri" resourceType="text/html">http://www.ics.uci.edu/~fielding/pubs/dissertation/top.htm</identifier>
		<howpublished>Ph.D. Thesis</howpublished>
	</reference>
	<reference name="hos01">
		<names type="author">
			<person>
				<givenname>Haruo</givenname>
				<surname>Hosoya</surname>
			</person>
		</names>
		<date value="2001-12"/>
		<publisher type="university">University of Tokyo</publisher>
		<title>Regular Expression Types for XML</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-xduce"/>; </p>
			</richtext>
		</annotation>
		<howpublished>Ph.D. Thesis</howpublished>
	</reference>
	<reference name="nah95">
		<names type="author">
			<person>
				<givenname>Klara</givenname>
				<surname>Nahrstedt</surname>
			</person>
		</names>
		<date value="1995"/>
		<address>Philadelphia, Pennsylvania</address>
		<field type="bibtex:index">QoS Broker</field>
		<publisher type="university">University of Pennsylvania</publisher>
		<field type="bibtex:src">DB</field>
		<title>An Architecture for End-to-End Quality of Service Provision and its Experimental Validation</title>
		<howpublished>Ph.D. Thesis</howpublished>
	</reference>
	<reference name="dee91">
		<names type="author">
			<person>
				<givenname>Stephen E.</givenname>
				<surname>Deering</surname>
			</person>
		</names>
		<date value="1991"/>
		<field type="bibtex:index">IP multicast, DV multicast, LS multicast</field>
		<publisher type="university">Stanford University</publisher>
		<field type="bibtex:src">DB</field>
		<title>Multicast Routing in a Datagram Internetwork</title>
		<howpublished>Ph.D. Thesis</howpublished>
	</reference>
	<reference name="lub90">
		<names type="author">
			<person>
				<givenname>Hannes P.</givenname>
				<surname>Lubich</surname>
			</person>
		</names>
		<date value="1990"/>
		<address>Zürich, Switzerland</address>
		<field type="bibtex:index">CSCW, MultimETH, OSI</field>
		<identifier type="isbn">3-7281-1740-4</identifier>
		<annotation type="bibtex:note">
			<richtext>
				<p>Diss. ETH No. 8985</p>
			</richtext>
		</annotation>
		<publisher type="university">ETH Zürich</publisher>
		<field type="bibtex:src">EW</field>
		<title>MultimETH: Ein Beitrag zur Konzeption eines Echtzeit-Multimedia-Konferenzsystems</title>
		<howpublished>Ph.D. Thesis</howpublished>
	</reference>
	<reference name="pla94b">
		<names type="author">
			<person>
				<givenname>Thomas</givenname>
				<surname>Plagemann</surname>
			</person>
		</names>
		<date value="1994"/>
		<address>Zürich, Switzerland</address>
		<field type="bibtex:index">Da CaPo, dynamic protocol configuration, high speed networks</field>
		<identifier type="isbn">3-7281-2334-X</identifier>
		<annotation type="bibtex:note">
			<richtext>
				<p>Diss. ETH No. 10830</p>
			</richtext>
		</annotation>
		<publisher type="university">ETH Zürich</publisher>
		<field type="bibtex:src">EW</field>
		<title>A Framework for Dynamic Protocol Configuration</title>
		<howpublished>Ph.D. Thesis</howpublished>
	</reference>
	<reference name="gut95b">
		<names type="author">
			<person>
				<givenname>Thomas</givenname>
				<surname>Gutekunst</surname>
			</person>
		</names>
		<date value="1995"/>
		<address>Zürich, Switzerland</address>
		<field type="bibtex:index">JVTOS, CIO, shared window systems</field>
		<annotation type="bibtex:note">
			<richtext>
				<p>Diss. ETH No. 11120</p>
			</richtext>
		</annotation>
		<publisher type="university">ETH Zürich</publisher>
		<field type="bibtex:src">EW</field>
		<title>Shared Window Systems</title>
		<howpublished>Ph.D. Thesis</howpublished>
	</reference>
	<reference name="bur96">
		<names type="author">
			<person>
				<givenname>Christoph A.</givenname>
				<surname>Burkhardt</surname>
			</person>
		</names>
		<date value="1996"/>
		<abstract>
			<richtext>
				<p>Audio conferencing is only efficient if the right tools are used and if the flow of task-inherent work processes is not disturbed by unsuited technology. Therefore, we suggest to structure the original task into two asynchronous preparation phases, one without and one with a link to the audio conference. This is followed by the actual conference and the assessment phase, which ends one itineration of processing the original task. The object-oriented audio conference software is written in C/C++ and runs on Sun workstations under SunOS 5.3 The audio mixing part is based on IBM compatible PCs running DOS. The PCs are equipped with ISDN interfaces, an analogue telephone interface, a digital signal processor board, and Ethernet interface cards allowing network access over TCP/IP. The audio conferencing service can be fully accessed and controlled over the Internet. The system is realizable with existing low-cost workstation technology, but still provides a good audio conference signal and a user-friendly interface.</p>
			</richtext>
		</abstract>
		<address>Zürich, Switzerland</address>
		<identifier type="isbn">978-3-7281-2386-2</identifier>
		<annotation type="bibtex:note">
			<richtext>
				<p>Diss. ETH No. 11600</p>
			</richtext>
		</annotation>
		<publisher type="university">ETH Zürich</publisher>
		<title>Towards Computer Supported Audio Conferencing</title>
		<annotation>
			<richtext>
				<p>Keywords: (undefined keyword: multimeth); </p>
			</richtext>
		</annotation>
		<howpublished>Ph.D. Thesis</howpublished>
	</reference>
	<reference name="jen97">
		<names type="author">
			<person>
				<givenname>Patrick</givenname>
				<surname>Jenny</surname>
			</person>
		</names>
		<date value="1997"/>
		<abstract>
			<richtext>
				<p>To study acoustic effects in premixed laminar flames the compressible Navier-Stokes equations with stiff source terms for the chemistry are numerically solved by a cell centered finite volume method. Three basic numerical problems are discussed which deal with gas mixtures, convergence acceleration for subsonic simulations and the computation of the inviscid fluxes at the volume interfaces taking the viscous terms, the source terms and 2D effects into account. Conservative Euler solvers for gas mixtures produce numerical errors, if the temperature and the ratio of specific heats are not constant. For mixtures of calorically perfect gases, a simple correction of the total energy per unit volume is proposed to avoid these errors. This is done in a physical way and only the total energy looses some of its conservativity. Numerical simulations of contact discontinuity convection, a shock tube problem and shock-interface interactions in 1D and 2D yield much more accurate solutions, if the correction is applied. The straightforward extension to 3D is outlined. As the ratio of the acoustic and entropy wave speeds is large for low Mach number flames, a lot of time steps are necessary with an explicit scheme to simulate a contact discontinuity crossing the computational domain. An easy way is shown how one can use much larger time steps with an explicit code to obtain the steady state solution. The method is based on the idea that the ratio of the acoustic and entropy wave speeds gets closer to one by subtracting a constant value from the pressure in the whole field. Only the inviscid terms of the energy equation are influenced by that pressure decrease. As long as compressibility effects remain small, the error remains small. Moreover, the error can be corrected by solving a scalar equation after each time step such that the steady state solution of the modified scheme is equal to the steady state of the non-modified scheme. Applying a conventional Riemann solver for flame simulations and even for 2D Euler simulations without source terms can lead to dramatic inaccuracies. A new approach for a flux solver is introduced, which takes viscous terms, source terms and 2D effects into account. The basic idea is to distribute the source terms, which also contain the viscous terms and 2D effects, to the corresponding volume interfaces. The price is a nonlinear algebraic system for six unknowns instead of a linear system for three unknowns to evaluate the fluxes. Simulations of premixed laminar flames in 1D and 2D and a 2D Euler simulation without source terms yield much more accurate results, if the new solver is applied. Unsteady simulations of two colliding flames producing sound show results which correspond almost precisely to the analytic solution. Thus, opposed to conventional Riemann solvers, our new flux solver is able to compute acoustic effects in flames accurately. Finally numerical results of acoustic interaction with a 2D Bunsen flame show a flattened flame shape which is at least qualitatively comparable with experimental measurements. The present approach for a flux solver is more general and can be applied to solve other systems of partial differential equations which contain inviscid terms, e.g. for the shallow water equations.</p>
			</richtext>
		</abstract>
		<address>Zürich, Switzerland</address>
		<annotation type="bibtex:note">
			<richtext>
				<p>Diss. ETH No. 12030</p>
			</richtext>
		</annotation>
		<publisher type="university">ETH Zürich</publisher>
		<title>On the Numerical Solution of the Compressible Navier-Stokes Equations for Reacting and Non-Reacting Gas Mixtures</title>
		<howpublished>Ph.D. Thesis</howpublished>
	</reference>
	<reference name="wil97b">
		<names type="author">
			<person>
				<givenname>Erik</givenname>
				<surname>Wilde</surname>
			</person>
		</names>
		<date value="1997"/>
		<abstract>
			<richtext>
				<p>This thesis deals with the design and implementation of a group and session management system for collaborative applications. The need for such a system has been identified during work on group communication systems and collaborative applications. Currently, the support for collaborative applications provided by group communication systems is not very powerful (from the point of view of designers of collaborative applications). The goal of this thesis is to develop a system which provides designers of collaborative applications with group and session management functionality that can be used to easily build group communications. The architecture of the group and session management system (GMS) consists of a component which is integrated on the user side (typically, the direct user of the group and session management system is a group communication system), and a specialized directory service which is accessed by the user-side component. The two main aspects of the group and session management system are the data model and the functional model. The data model describes the object types which can be used for group and session management and the operations which can be used with these object types. The functional model describes how the operations are carried out inside GMS, ie how GMS works internally. The GMS data model consists of six object types and a number of relations which can be established between objects of these types. The user object type represents a person or entity using GMS. Each user has an identity (a name) and one or more methods of self-authentication. The group object type is used to define groups which can consist of users and/or groups. The flow object type represents one connection for data transport. The session data type is the main metaphor for group communication. Each session is used to logically group a number of flows and to create an abstraction for management, authorization, and admission control for flows. Two additional object types are certificates and flow templates, which are used for security purposes and for storing information related to the creation of flows. GMS is a distributed system which defines two protocols: an access protocol for communicating with the distributed system, and a system protocol for communications between the distributed entities of the system. The access protocol is based on a reliable, connection-oriented transport service. The system protocol uses two different transport services: a reliable, connection-oriented service and a reliable, FIFO ordered multicast service. A prototype of GMS has been implemented on a Unix platform and a number of performance tests and evaluations have been performed. The results showed that the GMS approach to group and session management is feasible and that the system can easily be used by designers of group communication systems. However, the prototype implementation has some performance drawbacks, for which possible solutions are also suggested.</p>
			</richtext>
		</abstract>
		<address>Zürich, Switzerland</address>
		<field type="bibtex:index">GMS, GAP, GSP, GSA, GUA</field>
		<identifier type="isbn">3-8265-2411-X</identifier>
		<annotation type="bibtex:note">
			<richtext>
				<p>Diss. ETH No. 12075</p>
			</richtext>
		</annotation>
		<publisher>Shaker Verlag</publisher>
		<publisher type="university">ETH Zürich</publisher>
		<title>Group and Session Management for Collaborative Applications</title>
		<identifier type="uri">http://dret.net/netdret/publications#wil97b</identifier>
		<identifier type="uri">http://e-collection.ethbib.ethz.ch/show?type=diss&amp;nr=12075</identifier>
		<howpublished>Ph.D. Thesis</howpublished>
	</reference>
	<reference name="bau97">
		<names type="author">
			<person>
				<givenname>Daniel</givenname>
				<surname>Bauer</surname>
			</person>
		</names>
		<date value="1997"/>
		<abstract>
			<richtext>
				<p>The developments in information technology of the last years have led to major advances in high-speed networking, multimedia capabilities for workstations and also distributed multimedia applications. In particular, multimedia applications for computer supported cooperative work have been developed that allow groups of people to exchange information and to collaborate and cooperate joint work. However, existing communication systems do not provide end-to-end guarantees for multipoint communication services which are needed by these applications. In this thesis, a communication architecture is described that offers end-to-end performance guarantees in conjunction with flexible multipoint communication services. The architecture is implemented in the Multipoint Communication Framework (MCF) that extends the basic communication services of existing operating systems. It orchestrates endsystem and network resources in order to provide end-to-end performance guarantees. Furthermore, it provides multipoint communication services where participants dynamically join and leave. The communication services are implemented by protocol stacks which form a three layer hierarchy. The topmost layer is called multimedia support layer. It accesses the endsystem's multimedia devices. The transport layer implements end-to-end protocol functions that are used to forward multimedia data. The lowest layer is labelled multicast adaptation layer. It interfaces to various networks and provides a multipoint-to-multipoint communication service that is used by the transport layer. Each layer contains a set of modules that implement a single protocol function. Protocol stacks are dynamically composed out of modules. Each protocol uses a single module on each layer. Applications specify their service requirements as Quality of Service (QoS) parameters. MCF maps these QoS parameters to the above mentioned layers, where they are used to calculate the needed resources. A resource manager reserves memory, CPU and multimedia devices in the endsystem. Access to the CPU is provided by a real-time scheduler for periodic tasks, which executes the protocols. The reservation of network resources is delegated to the network resource manager. MCF orchestrates endsystem and network resources in order to provide a guaranteed service covering the whole path from multimedia device to multimedia device. The evaluation of MCF shows that the proposed architecture results in an easy to use and efficient solution. The dynamic composition of protocol stacks offers high flexibility and allows applications to transport any multimedia data over any network. Resource reservations provide the performance guarantees needed for continuous media such as audio or video.</p>
			</richtext>
		</abstract>
		<address>Zürich, Switzerland</address>
		<field type="bibtex:index">mcf[1] qos[0.8]</field>
		<identifier type="isbn">3-8265-2638-4</identifier>
		<annotation type="bibtex:note">
			<richtext>
				<p>Diss. ETH No. 12163</p>
			</richtext>
		</annotation>
		<publisher>Shaker Verlag</publisher>
		<publisher type="university">ETH Zürich</publisher>
		<title>A Multipoint Communication Architecture for End-to-End Quality of Service Guarantees</title>
		<identifier type="uri">http://e-collection.ethbib.ethz.ch/show?type=diss&amp;nr=12163</identifier>
		<howpublished>Ph.D. Thesis</howpublished>
	</reference>
	<reference name="sch99">
		<names type="author">
			<person>
				<givenname>Georg</givenname>
				<surname>Schönbächler</surname>
			</person>
		</names>
		<date value="1999"/>
		<abstract>
			<richtext>
				<p>The rise and success of the modern science, first in physics, later in biology and medicine, was based on a mechanic-linear model of causality. Its only category of explanation of natural processes is the mechanical machine. Such a point of view is reductionistic and does not justice to living organisms. As human beings using and processing signs we cannot recognize ourselves in this model. As all living creatures we perceive, interpret and answer the stimuli of the environment. To explain the behavior of organisms we need a semiotic-circular causality. Semiotics, the study of signs, try to perceive and interpret processes of signs. Language serves as a paradigmatic model. Semiotics can be subdivided in semantics, the theory of meaning, in syntax, the theory of the forms and the arrangement of the signs, and in pragmatics, the theory of the contextual rules of communication. Pragmatics as a subject of inquiry in its own right attained its scientific status in the last few decades only. Semiotics are not concerned exclusively with language, but help as so-called "biosemiotics" also to explain the network of communication on and between the different levels of organisation of molecules, cells, organs or organism. Living organisms are networks connecting these levels with each other and with the environment. The Denkstil of established pharmacology is likewise restricted to mechanic causality. Phenomena unexplained by physics are classified as unscientific. As a consequence the placebo effect is defined as 'non-specific' or 'non-characteristic'. Such negative definitions exclude concrete questions of investigation. If we accept a biosemotic view in pharmacology, that is to say that we see drugs as signs consisting of a physical vehicle equipped with meaning, then the lock-and-key-concept becomes the syntactic level and the effect on the metabolism of the cell mediated by second messengers, on the organ and on the organism becomes the semantic level. The establishment of structure-effect-relations are the only goal of the classic pharmacology, just as syntax and semantics are the only domain of the classic semiotics. But the therapy with drugs must be seen in a broader treatment context. One has to include the level of the organism of the doctor-patient-relation or the placebo effect and of the internal organismic system levels as individual response to a drug, dependent on the genetic idiosyncrasy, the environment of the cell, the recent past, the thermodynamic activity etc. The assumption of steady state conditions are unrealistically restrictive. The semiotic expansion of the pharmacology will not invalidate the achievements of classic pharmacology, but elucidates in addition a view of the pragmatic components and makes the scientific integration of the placebo phenomenon into the drug therapy possible. The placebo effect looses its inconsistency. From a biosemiotic point of view the randomized placebo controlled double blind trial must be seen as a restriction to unrealistic conditions of investigation. The pragmatic regularities and thus a scientific approach to the processes happening within the therapeutic triangle of therapist, drug and patient are excluded. The comparison of a drug with a placebo is a category-mistake. By comparing semantics with pragmatics, the investigator confounds the levels of analysis. A semiotic pharmacology expanded by pragmatics increases the number of aspects of the therapeutical situation. Pharmacology ought to pay more attention to pragmatic aspects of drug therapy.</p>
			</richtext>
		</abstract>
		<address>Zürich, Switzerland</address>
		<annotation type="bibtex:note">
			<richtext>
				<p>Diss. ETH No. 13113</p>
			</richtext>
		</annotation>
		<publisher type="university">ETH Zürich</publisher>
		<title>Zur semiotischen Rekonstruktion des Placeboeffektes</title>
		<identifier type="uri">http://e-collection.ethbib.ethz.ch/show?type=diss&amp;nr=13113</identifier>
		<howpublished>Ph.D. Thesis</howpublished>
	</reference>
	<reference name="jan00">
		<names type="author">
			<person>
				<givenname>Jörn Wilhelm</givenname>
				<surname>Janneck</surname>
			</person>
		</names>
		<date value="2000"/>
		<address>Zürich, Switzerland</address>
		<identifier type="isbn">3-8265-7688-8</identifier>
		<annotation type="bibtex:note">
			<richtext>
				<p>Diss. ETH No. 13758</p>
			</richtext>
		</annotation>
		<publisher>Shaker Verlag</publisher>
		<publisher type="university">ETH Zürich</publisher>
		<title>Syntax and Semantics of Graphs</title>
		<identifier type="uri">http://e-collection.ethbib.ethz.ch/show?type=diss&amp;nr=13758</identifier>
		<howpublished>Ph.D. Thesis</howpublished>
	</reference>
	<reference name="sch00c">
		<names type="author">
			<person>
				<givenname>Bruno</givenname>
				<surname>Schneider</surname>
			</person>
		</names>
		<date value="2000"/>
		<address>Zürich, Switzerland</address>
		<annotation type="bibtex:note">
			<richtext>
				<p>Diss. nat. Univ. Zürich</p>
			</richtext>
		</annotation>
		<publisher type="university">University of Zurich</publisher>
		<title>Structure of a Brown Trout (Salmo trutta L.) Population in a Pre-Alpine Water-System: Relationship Between Genetics and Ecology</title>
		<howpublished>Ph.D. Thesis</howpublished>
	</reference>
	<reference name="cat02">
		<names type="author">
			<person>
				<givenname>Philippe Claude</givenname>
				<surname>Cattin</surname>
			</person>
		</names>
		<date value="2002"/>
		<abstract>
			<richtext>
				<p>Biometric methods for verifying, i.e. authenticating, someone's identity are increasingly being used. Today's commercially available biometric systems show good reliability. However, they generally lack user acceptance. Users show an antipathy touching a fingerprint scanner and they dislike looking into an iris scanner that might eventually malfunction and impair their vision. In general, they favour systems with the least amount of interaction. Using gait as a biometric feature would lessen such problems since it requires no subject interaction other than walking by. Consequently, this would increase user acceptance. And since highly motivated users achieve higher recognition scores, it increases the overall recognition rate as well. This monograph describes a biometric system that uses individual characteristics of human gait for authentication. Two sensors measuring different physical properties of the walking person were used. First, a force sensor measures the Ground Reaction Force (GRF) perpendicular to the floor and second, a video sensor captures a side view of the passing person. Computationally efficient algorithms were developed to extract five different feature types, i.e. modalities, from the acquired gait data. A novel variant of the Generalised Principal Component Analysis (GPCA) was devised to reduce data dimensionality without losing, or even better, with improving person separability. Last but not least, a Bayes Risk Criterion approach is used to fuse the five modalities. In the final investigation the performance and discriminatory power of all modalities was analysed. In addition, the influence of changing clothes, shoes, backpacks, and bags on the recognition quality was investigated. It could be shown that fusing all five modalities drastically improves the overall system robustness compared to the best individual modality. Finally, an extensive discussion of the limitations and possible future improvements of the current system is included.</p>
			</richtext>
		</abstract>
		<address>Zürich, Switzerland</address>
		<annotation type="bibtex:note">
			<richtext>
				<p>Diss. ETH No. 14603</p>
			</richtext>
		</annotation>
		<publisher type="university">ETH Zürich</publisher>
		<title>Biometric Authentication System using Human Gait</title>
		<identifier type="uri">http://e-collection.ethbib.ethz.ch/show?type=diss&amp;nr=14603</identifier>
		<howpublished>Ph.D. Thesis</howpublished>
	</reference>
	<reference name="sch02c">
		<names type="author">
			<person>
				<givenname>Barbara</givenname>
				<surname>Schneider</surname>
			</person>
		</names>
		<date value="2002"/>
		<abstract>
			<richtext>
				<p>Due to technological changes in cartography, traditional paper atlases have increasingly been replaced by digital atlas information systems (AIS) during the last 20 years. AIS offer both user-friendly interfaces and high-quality multimedia visualisation techniques, yet they still lack the functionality to perform spatial analysis. This functionality, however, offers a great potential for the future development of AIS. Therefore, this dissertation investigates how GIS analysis functions can be integrated with AIS, and how these functions can be rendered accessible to a broad range of expert and non-expert users. The emphasis of this dissertation is placed on using environmental vector data sets within AIS. In the theoretical first part of the study, a new scientific approach called "GIS analysis in atlas information systems" was developed. This approach first points out that the following GIS functions are suited for AIS: measurements, queries, reclassification and aggregation, graphical and geometrical overlay, analysis of surfaces, network analysis and statistics. Since analysis of surfaces is usually not based on a vector model, it cannot be considered for AIS with environmental vector data sets. Secondly, the approach states that these GIS functions have to be easy to use, reliable (i. e., ensuring correct results), data independent and fast (i. e., performed within a short time) in order to be successful in AIS. These requirements, however, can only be met if the technical structure of the AIS is flexible enough to allow authors to individually design and develop the graphical user interface and the GIS functions. In the practical second part of the study, the scientific approach was realised by developing the application AGAIS (Analytical Geographic Atlas Information System). As examples of environmental vector data sets, the digital soil-suitability and precipitation maps of Switzerland were used. The graphical user interface was developed using the multimedia authoring system Macromedia Director, while the GIS functions were programmed with an external shared library written in C++. In accordance to the scientific approach, only those functions were implemented in AGAIS that are suited for AIS with environmental vector data and make sense for the soil-suitability and precipitation maps. The GIS functions were adapted in such a way as to meet the requirements of users not having any GIS technical knowledge. Thus, using AGAIS, it is possible to perform complex queries and reclassification without knowing the syntax of a query language. In addition, these functions ensure correct results. When two map layers are graphically overlaid, map elements can easily be compared with the two-dimensional, likewise overlaid legend. The geometrical overlay is rendered transparent to the users by progressively drawing the intersection points and the newly built polygons on the map. In so doing, users gain insight into the process of a complex GIS function. Moreover, they get the impression of a shorter waiting time. Finally, when users perform statistical analysis, they can at a glance identify the distribution and correlation pattern of attributes in coloured diagrams. This study shows that GIS functions can be successfully integrated with AIS. These functions, however, must be carefully chosen, considerably adapted, and simplified so that atlas users can understand them by intuition. Therefore, the functions and the user interface cannot be adopted from common GIS, but have to be redesigned according to the needs of atlas users. In future, integrating GIS functionality will positively influence the development of AIS and will extend their field of application. Complex spatial analysis, so far mainly performed by GIS specialists, is now available to a broader range of users. Although AIS will become more analytical in the future, they are not likely to grow together with GIS. On the contrary, they will remain independent and closed systems.</p>
			</richtext>
		</abstract>
		<address>Zürich, Switzerland</address>
		<annotation type="bibtex:note">
			<richtext>
				<p>Diss. ETH No. 14605</p>
			</richtext>
		</annotation>
		<publisher type="university">ETH Zürich</publisher>
		<title>GIS-Funktionen in Atlas-Informationssystemen</title>
		<identifier type="uri">http://e-collection.ethbib.ethz.ch/show?type=diss&amp;nr=14605</identifier>
		<howpublished>Ph.D. Thesis</howpublished>
	</reference>
	<reference name="tyl03">
		<names type="author">
			<person>
				<givenname>Niclas</givenname>
				<surname>Tylli</surname>
			</person>
		</names>
		<date value="2003"/>
		<abstract>
			<richtext>
				<p>A detailed experimental and numerical study of three-dimensional laminar flow over a backward-facing step with an expansion ratio of 2 and a downstream aspect ratio of 20 is presented. Experimental results for transitional and turbulent flow are also reported. Experiments were based on both Digital and Stereoscopic Particle Image Velocimetry; a spectral element method was used for the simulations. The focus of the present work was two-fold: (i) A passive control scheme for inducing global unsteadiness, suggested in previous work, was implemented, and the controlled flow was studied in the laminar and turbulent regimes. (ii) In the uncontrolled flow, the effects of sidewalls on the flow structure were studied at laminar, transitional, and turbulent Reynolds number values. The control scheme consisted of external flow recirculation due to suction at the step wall and blowing at the lower wall. The problem geometry was fixed and, thus, for a given Reynolds number, the flow dynamics depended only on the recirculation volume flow rate. For laminar flow, periodic vortex shedding from the step edge was observed within a range of recirculation flow rates, both in experiments and two-dimensional simulations. Global stability analysis calculations support the present simulation results. The experimental laminar flow was found to be strongly three-dimensional, exhibiting streamwise vortices in the shear layer regions. For turbulent flow, the present control scheme significantly increased mixing in the region immediately after the sudden expansion. This led to a decrease in reattachment length of the order of 70% in comparison to the non-manipulated flow. The control scheme was found to be robust to variations in the suction/blowing velocity boundary conditions. In the present study of sidewall effects, both experimental and computational results illustrated that, for laminar flow, a wall-jet is present at the channel lower wall, directed towards the channel mid-plane, in agreement with previous observations. In the present work, the development of self-similar wall-jet profiles with increasing distance from the sidewalls is demonstrated. The intensity of this secondary flow increased with Reynolds number in the laminar regime, and decreased in the transitional and turbulent regimes. The effect of sidewalls on the primary and upper wall recirculation zones is demonstrated, which explains the discrepancies in the previous literature between experiments and two-dimensional simulations.</p>
			</richtext>
		</abstract>
		<address>Zürich, Switzerland</address>
		<annotation type="bibtex:note">
			<richtext>
				<p>Diss. ETH No. 14913</p>
			</richtext>
		</annotation>
		<publisher type="university">ETH Zürich</publisher>
		<title>Induced global unsteadiness and sidewall effects in the backward-facing step flow: Experiments and numerical simulations</title>
		<identifier type="uri">http://e-collection.ethbib.ethz.ch/show?type=diss&amp;nr=14913</identifier>
		<howpublished>Ph.D. Thesis</howpublished>
	</reference>
	<reference name="gre04">
		<names type="author">
			<person>
				<givenname>Alexandre A.</givenname>
				<surname>Grêt</surname>
			</person>
		</names>
		<date value="2004"/>
		<abstract>
			<richtext>
				<p>The coda of seismic waves consists of that part of the signal after the directly arriving phases. In a finite medium, or in one that is strongly heterogeneous, the coda is dominated by waves which have repeatedly sampled the medium. Small changes in a medium which may have no detectable influence on the first arrivals are amplified by this repeated sampling and may thus be detectable in the coda. We refer to this use of multiple-sampling coda waveforms as coda wave interferometry. We have exploited ultrasonic coda waves to monitor time- varying rock-properties in a laboratory environment. We have studied the dependence of velocity on uni-axial stress in Berea sandstone, the temperature dependence of velocity in granite and in aluminum, and the change in velocity due to an increase of water saturation in sandstone. Furthermore, We applied coda wave interferometry to seismic data excited by a hammer source, collected at an experimental hard rock mine, Idaho Springs, CO. We carried out a controlled stress-change experiment in a pillar and we were able to monitor the internal stress change. We used coda wave interferometry to monitor temporal changes in the subsurface of the Mt. Erebus Volcano, Antarctica. Mt. Erebus is one of the few volcanoes known to have a convecting lava lake. The convection provides a repeating seismic source producing seismic energy that propagates through the strongly scattering geology in the volcano. There are many other possible applications of coda wave interferometry in geophysics, including dam and nuclear waste deposit monitoring, time-lapse reservoir characterization, earthquake relocation, stress monitoring in surface mining and rock physics.</p>
			</richtext>
		</abstract>
		<address>Golden, Colorado</address>
		<publisher type="university">Colorado School of Mines</publisher>
		<title>Time-lapse Monitoring with Coda Wave Interferometry</title>
		<identifier type="uri" resourceType="application/pdf">http://acoustics.mines.edu/preprints/cwi.pdf</identifier>
		<howpublished>Ph.D. Thesis</howpublished>
	</reference>
	<reference name="ana04">
		<names type="author">
			<person>
				<givenname>Sai</givenname>
				<surname>Anand</surname>
			</person>
		</names>
		<date value="2004"/>
		<abstract>
			<richtext>
				<p>Communication networks lend themselves to the study of a variety of optimization problems. A fundamental problem among them that is intensively investigated is that of call admission control, or call control for short. The problem arises in the following setting. The communication network consists of nodes (e.g. terminals, routers, et cetera) which are connected to each other via links (e.g. optical cables). These links carry data between nodes. They have a certain bandwidth capacity associated with them. A call is a communication request between any two nodes of the network. It is associated with a bandwidth requirement, i.e. the rate at which data is communicated between the nodes. A call may be accepted into the network if (i) a route connecting the two nodes exists and (ii) the bandwidth requirement of the call can be reserved along all the links of one such route. Once a call is accepted a profit is accrued by the network. The optimization problem arises due to the fact that the sum of the bandwidth requirements of calls that are routed through any link of the network should not exceed its bandwidth capacity. The call control problem is to maximize the number (or profits) of calls that can be accepted into the network such that the capacity constraints on the links are not violated. A ring topology is one in which the nodes are connected to each other forming a cycle. In all-optical networks, the ring topology is a popular configuration. Bigger networks are formed from individual rings by interconnecting them. Some top reasons that make the ring topology a favoured one are its simplicity, scalability and survivability in the presence of link failures. This thesis mainly investigates several variants of call control on ring based topologies for two reasons. Firstly, all-optical networks are in the forefront of revolutionizing communications today and the ring topology is the building block of such networks. Secondly, rings are simple topologies on which several network optimization problems have been studied in the past and there are several others which have not been resolved. The goal of our research, the outcome of which is the thesis presented here, is to address a few such problems pertaining to call control. There are two basic variants of call control that we consider, namely on- line and off-line. In the off-line version of call control, it is assumed that all the calls that occur in the network are given in advance. An algorithm for this version can decide which calls to accept and which to reject taking this overall picture into consideration. In the online version, calls arrive into the network in a sequence, one after the other. An algorithm for the on-line version makes a decision to accept a call that is presented to it only based on what decisions it made in the past and the current state of the network. In particular, it has no knowledge of the calls that might be presented to it in the future. A tree of rings is a graph obtained by connecting several disjoint rings in a "tree"-like fashion, by identifying vertices in different rings. The tree of rings topology is a natural result of interconnecting rings in all-optical networks to form larger networks. We investigate on-line call control problems on trees of rings. Non-preemptive randomized algorithms with competitive ratios that are best possible up to constant factors are given. Fixed parameter tractability is an emerging area to tackle NP-hard problems. We view call control problems from this perspective. Fixed parameter tractability results are shown for variants of the off-line call control problems on arbitrary graphs, undirected and bidirected trees of rings. To the best of our knowledge, these are the first such results for the call control problem. For two variants of off-line call control problems in rings, we present polynomial time approximation algorithms. When the route of a call can be determined by the algorithm, we present an algorithm that accepts and routes at most 3 calls fewer than what an optimal algorithm can achieve. When the routes are pre-determined we present an algorithm that achieves a profit that is at least one-half of that achieved by an optimal algorithm. For various special cases, we present optimal polynomial time algorithms or approximation schemes. We also give an indication of the difficulty of finding an optimal polynomial algorithm for the general problem. For addressing the off-line call control problem for calls with arbitrary bandwidth requirements, a starting point would be to study it on the simple topology of a line. A line is simply a set of nodes connected to form a path. We identify several restrictions for which algorithms with "nice" ratios are achievable.</p>
			</richtext>
		</abstract>
		<address>Zürich, Switzerland</address>
		<annotation type="bibtex:note">
			<richtext>
				<p>Diss. ETH No. 15441</p>
			</richtext>
		</annotation>
		<publisher type="university">ETH Zürich</publisher>
		<title>Algorithms for Call Control in Ring Based Networks</title>
		<identifier type="uri">http://e-collection.ethbib.ethz.ch/show?type=diss&amp;nr=15441</identifier>
		<howpublished>Ph.D. Thesis</howpublished>
	</reference>
	<reference name="kre05">
		<names type="author">
			<person>
				<givenname>Philippe</givenname>
				<surname>Krebs</surname>
			</person>
		</names>
		<date value="2005"/>
		<abstract>
			<richtext>
				<p>Cardiovascular diseases such as atherosclerosis, coronary heart disease, and dilated cardiomyopathy, are the principal cause of mortality in industrialized countries. Chronic inflammatory processes are of major importance in the pathogenesis of atherosclerotic disease and myocarditis. Initial injury is likely to be elicited by infectious agents that can sustain chronic immune responses and immunopathology by persisting in the cardiovascular system. Such chronic infections may eventually overcome tolerance and induce reactivity against self-antigens with exacerbation of the disease. Indeed, autoimmune reactions have been hypothesized to be involved in the pathogenesis of myocarditis and atherosclerosis. To shed light on the mechanisms behind chronic cardiovascular diseases, we used a transgenic mouse model in which autoimmunity can be specifically elicited in the heart and the aorta (SM-LacZ mice). The two first studies deal with the role and significance of B cells and their accompanying autoantibody signatures in systemic and heart-specific autoimmunity, respectively. The third and the fourth sections describe how virus elicited CD8+ T cells can either be exhausted and functionally impaired in conditions of high antigen expression in the periphery, or lead to the exacerbation of atherosclerosis and chronic immunopatholgy in a model of antigen persistence in the cardiovascular system. In the first part of this work we present a preliminary investigation on the autoimmune B cell response engendered following infection with cytopathic (vaccinia virus, VV and vesicular stomatitis virus, VSV) or non-cytopathic (lymphocytic choriomeningitis virus, LCMV) viruses. Applying the SEREX method (serological identification of recombinantly expressed antigens), we show that viruses induce antibodies against a broad panel of autoantigens. Furthermore, the different viruses triggered distinct autoantibody responses, thus suggesting that virus infections may leave specific "autoantibody fingerprints" in the infected host. The second chapter is dedicated to the characterization of the anti-self IgG response in organ-specific autoimmunity. Here the SEREX approach was used to molecularly dissect heart-specific autoimmune B cell responses that develop during the course of experimental autoimmune myocarditis (EAM). Upon immunization with a peptide derived from cardiac myosin heavy chain $\alpha$ (myhc$\alpha$) we found that the vast majority of the autoantibodies generated in BALB/c mice was specific for portions of the myosin protein that did not encompass the immunogenic peptide, hence revealing intramolecular epitope spreading. This strong focusing on myhc$\alpha$ was also a hallmark of the B cell response against heart antigens, that was induced upon myocardial damage following MCMV infection which generally precipitates a broad spectrum of anti-self antibodies. Furthermore, myocarditis severity correlated with both intra- and intermolecular epitope spreading. Therefore, evaluation of the focusing of an antibody response to disease-related self-determinants may help to assess both the susceptibility to and the progression rate of autoimmune cardiac damage. The third study investigates the fate of transgene-specific CD8+ T cells following abortive infection with a recombinant adenovirus. We found that specific CD8+ T cells expanded only in a very narrow dose range and that they were functionally impaired. Infection of SM-LacZ mice led to the deletion of these specific CD8+ T cells and, consequently, transgenic mice did not develop myocarditis. Our results suggest that the outcome of vaccination with recombinant adenoviruses is critically dependent on the antigen load in peripheral tissues. The last chapter is an immunologic analysis of the mechanisms underlying atherosclerosis in an infectious situation. Although hypercholesterolemic APOE(-/-) and APOE(-/-)$\times$SM-LacZ mice mounted comparable T cell responses to a recombinant MCMV-LacZ virus, persistent expression of the $\beta$galactosidase transgene in the vasculature, as it occurs in APOE(-/-)$\times$SM-LacZ mice, dramatically exacerbated atherosclerosis and elicited chronic cellular infiltrations in the aorta. Therefore, our data provide evidence for the role of persistent vascular infections with pathogens and the ensuing specific immunopathology in atherogenic processes.</p>
			</richtext>
		</abstract>
		<address>Zürich, Switzerland</address>
		<annotation type="bibtex:note">
			<richtext>
				<p>Diss. ETH No. 16068</p>
			</richtext>
		</annotation>
		<publisher type="university">ETH Zürich</publisher>
		<title>Immunopathology of Cardiovascular Diseases</title>
		<identifier type="uri">http://e-collection.ethbib.ethz.ch/show?type=diss&amp;nr=16068</identifier>
		<howpublished>Ph.D. Thesis</howpublished>
	</reference>
	<reference name="kut04">
		<names type="author">
			<person>
				<givenname>Philipp W.</givenname>
				<surname>Kutter</surname>
			</person>
		</names>
		<date value="2004"/>
		<address>Zürich, Switzerland</address>
		<annotation type="bibtex:note">
			<richtext>
				<p>Diss. ETH No. 15421</p>
			</richtext>
		</annotation>
		<publisher type="university">ETH Zürich</publisher>
		<title>Montages — Engineering of Computer Languages</title>
		<howpublished>Ph.D. Thesis</howpublished>
	</reference>
	<reference name="roe05">
		<names type="author">
			<person>
				<givenname>Kay</givenname>
				<surname>Römer</surname>
			</person>
		</names>
		<date value="2005"/>
		<address>Zürich, Switzerland</address>
		<annotation type="bibtex:note">
			<richtext>
				<p>Diss. ETH No. 16106</p>
			</richtext>
		</annotation>
		<publisher type="university">ETH Zürich</publisher>
		<title>Time Synchronization and Localization in Sensor Networks</title>
		<identifier type="uri">http://e-collection.ethbib.ethz.ch/show?type=diss&amp;nr=16106</identifier>
		<howpublished>Ph.D. Thesis</howpublished>
	</reference>
	<reference name="zih05">
		<names type="author">
			<person>
				<givenname>Monika Silvia</givenname>
				<surname>Zihlmann</surname>
			</person>
		</names>
		<date value="2005"/>
		<abstract>
			<richtext>
				<p>Currently more than 1'000'000 total knee arthroplasties, TKAs, are implanted world wide each year, thereof 40'000 TKAs in Switzerland. Because of higher life expectancies it is expected that the number of total knee implantations will increase in the next few years. The goals of a TKA are longevity of the implant components and high satisfactory patient rates. Today the rate of a good patient outcome is around 85%, which still leaves a significant absolute number of patients needing early revision surgery. The most common causes for revision surgery are polyethylene (PE) wear, loosening, knee instability and infection. PE wear, loosening and instability are factors associated with altered joint biomechanics after total knee replacement. The femoral component rotational alignment profoundly affects the knee joint's mechanics in flexion as well as in extension, in all six degrees of freedom. A malrotated femoral component could lead to ligament unbalancing causing lateral flexion instability and pain while standing up from a chair or walking down stairs. In order to avoid these problems a comprehensive mechanical understanding of the knee joint as regards to the alignment of the implant component in TKA is important. A three dimensional computer based model visualising the joint's kinematics during different motion patterns contributes to this understanding and makes it possible to estimate the load at the knee joint. Such a model requires accurate in vivo kinematic and kinetic data to visualise and calculate the load at the joint of different motion patterns of daily activities. Previous investigations in gait analysis used kinematic and kinetic information from skin mounted markers and force plates during level walking. The problem of this measurement technique is the large error in kinematic data acquisition caused by the movement of the skin and muscles relative to the underlying bone. Video-fluoroscopy enables the measurement of kinematics of implant components more accurately by a three-dimensional numeric reconstruction of the single plane projection view in the fluoroscopic images, thus avoiding skin movement artefacts. However, this technique is limited to the field of view of the fluoroscopic screen. This problem was solved by using a motor driven trolley built in the laboratory to carry the fluoroscopic unit (x-ray source, image intensifier, c-arm). This movable system allows the tracking of the knee joint during level walking, and a sit down task. An intensity based registration algorithm reconstructs the six degrees of freedom of the implant components relative to the focus of the fluoroscope. The three dimensional reconstruction is within a translational accuracy of 3.1 mm and a rotational accuracy of 1.6$^\circ$. Video-fluoroscopy only acquires kinematic data. This means that the loads in the knee joint can not be estimated. In this study was force plate data coupled with the moving fluoroscopic system enabling inverse dynamic calculation. The unit mover was optically tracked by VICON in order to transform the fluoroscopic coordinate system into the global coordinate system with its origin on the centre of one force plate, thereby coupling the fluoroscopic system with the force plate. This transformation was performed within an accuracy of $\pm$ 1 mm. This measuring system results in seven times more accurate inverse dynamic calculation than classic instrumented gait analysis would achieve. The local mechanics of the total knee was visualised in a three dimensional computer model. The model included TKA geometry from CAD software, and bone geometry from CT scans of the individual. It visualised the kinematics of the implant components during the activities mentioned above. Furthermore, femoral component malrotation was simulated to estimate the alternated strain at the posterior cruciate ligament, the medial, and the lateral collateral ligaments. The simulation of five different degrees of femoral component malrotation shows the relationship between the strain and forces produced by the ligaments under these conditions. The simulation shows that an internally rotated femoral component has a more profound effect on the forces in the ligaments than an external rotational malalignment. This might lead to pain on the medial side and condylar lift-off on the lateral side during a sit down task, as observed by clinicians. This work sets a basis for further investigation of TKA discussing the patient's outcome and contributing to a better mechanical understanding of the knee joint. It may help clinicians and implant developers discuss the effects of their implant design or alignment of the implant components under dynamic loading.</p>
			</richtext>
		</abstract>
		<address>Zürich, Switzerland</address>
		<annotation type="bibtex:note">
			<richtext>
				<p>Diss. ETH No. 16129</p>
			</richtext>
		</annotation>
		<publisher type="university">ETH Zürich</publisher>
		<title>Total Knee Arthroplasty: Biomechanical Reflections and Modelling, Based on Quantitative Movement Analysis</title>
		<identifier type="uri">http://e-collection.ethbib.ethz.ch/show?type=diss&amp;nr=16129</identifier>
		<howpublished>Ph.D. Thesis</howpublished>
	</reference>
	<reference name="beu05">
		<names type="author">
			<person>
				<givenname>Jan</givenname>
				<surname>Beutel</surname>
			</person>
		</names>
		<date value="2005"/>
		<abstract>
			<richtext>
				<p>The recent rise and widespread adoption of wireless networking technologies for mobile communication applications has sparked numerous visions of an ever more networked and interactive world. One such vision proposed in the late nineties are Wireless Sensor Networks (WSN), where wireless communication and computing elements are combined with integrated sensors to enable tightly coupled interaction with the physical world. As a new application domain for wireless technology, key challenges here are (i) the limited resources of the highly integrated nodes that are to be leveraged by the amount of devices deployed and the collaboration between them, (ii) the tight coupling of application, nodes and the environment and (iii) the broad usage profile by systems-experts and non-expert users alike. First medium-scale experiments and field-trials have reported that it is increasingly hard to design, develop, deploy, test and validate systems consisting of more than a hand-full of nodes, especially when situated in a real-world environment. Prototypical applications are scarce, seldom consisting of more than a few tens to a hundred nodes. Setting up large, heterogeneous, interactive and functional systems as forecast in the visions is no small task; currently more an art than a systematic engineering effort. Coordinated methods and tools for the design and deployment of wireless networked embedded systems are missing today. With this work, we contribute to the design and development of wireless networked embedded systems. The specific contributions are presented and discussed in the context of a vertical slice of the design space concerned and the relevant questions encountered: (i) Functional and qualitative requirements of a location management service for WSNs based on measurements and simulation have been developed. We present one of the earliest algorithms for the distributed computation of node location. (ii) A novel platform for fast-prototyping of WSNs has been developed. This platform has successfully served numerous researchers, among ourselves, as an underlying infrastructure for experimentation and education. (iii) The BTnode platform has been used to develop multihop networks and topology control mechanisms for Bluetooth scatternets. To our knowledge, the experiments presented are the largest connected Bluetooth scatternets reported of to date. (iv) The concept of a deployment-support network as a powerful tool for the development, deployment, test and validation of WSNs is presented in conjunction with experimental evidence on the feasibility of the approach.</p>
			</richtext>
		</abstract>
		<address>Zürich, Switzerland</address>
		<identifier type="isbn">3-8322-4760-2</identifier>
		<annotation type="bibtex:note">
			<richtext>
				<p>Diss. ETH No. 16204</p>
			</richtext>
		</annotation>
		<publisher>Shaker Verlag</publisher>
		<publisher type="university">ETH Zürich</publisher>
		<title>Design and Deployment of Wireless Networked Embedded Systems</title>
		<identifier type="uri">http://e-collection.ethbib.ethz.ch/show?type=diss&amp;nr=16204</identifier>
		<howpublished>Ph.D. Thesis</howpublished>
	</reference>
	<reference name="gre05">
		<names type="author">
			<person>
				<givenname>Danielle Christiane</givenname>
				<surname>Gretener</surname>
			</person>
		</names>
		<date value="2005-09"/>
		<abstract>
			<richtext>
				<p>Alzheimer's disease (AD) is the most common form of dementia in the elderly and affects almost 30% of the population over 85 years of age. The cause and mechanisms of the disease are still unknown, yet a large body of evidence supports the so called amyloid cascade hypothesis. According to this model, abnormal accumulation and deposition of A$\beta$ peptide lead through a series of processes to fibril formation and synaptic dysfunction, neuronal loss and finally dementia. No cure for this disease is available yet and definite diagnosis is only possible by histological analysis of post mortem brain tissue. The diagnosis of a patient is a very complicated, expensive and time-consuming process including a variety of analyses such as neuropsychological testing, neuro-imaging, and blood tests. In specialized centers the accuracy of this diagnostic workup reaches 80–90%. The aim of this study was to screen the proteome of the cerebrospinal fluid (CSF) of patients with AD, patients with other neurological disorders including other types of dementia, and healthy age-matched control subjects for differences. For the CSF proteome analysis surface enhanced laser desorption ionization time-of-flight mass spectrometry (SELDI-TOF MS) was used. This method combines a chromatographic sample prefractionation step and mass spectrometric protein analysis in one technology. The data was analyzed using classification tree software, a bio-informatics tool based on a binary recursive partitioning algorithm. A proteomic pattern for the diagnosis of Alzheimer's disease was found consisting of 5 nodes representing peaks with molecular weights of 14 kDa, 11.7 kDa, 66 kDa, 4.2 kDa, and 80 kDa. This pattern reached a sensitivity of 80% and specificities of 75% (AD versus healthy control subjects), 95% (AD versus other neurological disorders), and 85% (AD versus both other groups). These values are comparable to the diagnostic accuracy obtained by standard diagnostic procedures. However, the combination of several diagnostic patterns into a "committee of experts" analysis led to correct classification of up to 100% of the test samples. By these patterns together with univariate statistical analysis of the proteomic data seven putative bio-marker candidates were found, three of which were identified. Two of these marker candidates were shown to be different forms of transthyretin, namely the glutathionylated form and an N-terminally truncated form, whereas the third bio-marker was shown to be Apolipoprotein AI. Transthyretin is a thyroid hormone carrier protein which also binds A$\beta$ peptide and has been reported to protect neurons against A$\beta$ toxicity. Apolipoprotein AI is the major component of plasma HDL and participates in the reverse transport of cholesterol from tissues to the liver. Apolipoprotein AI therefore plays a role in cholesterol metabolism and homeostasis which is believed to play a role in the mechanism of Alzheimer's disease pathology. The putative markers not yet identified have molecular weights of 4.6 kDa, 7.7 kDa, 40 kDa and 51 kDa and seem to separate more generally the healthy status from neurological disease. In conclusion, the principle of using protein patterns in CSF for the diagnosis of Alzheimer's disease was demonstrated and three bio-marker candidates which may be interesting from a pathophysiological point of view were identified.</p>
			</richtext>
		</abstract>
		<address>Zürich, Switzerland</address>
		<annotation type="bibtex:note">
			<richtext>
				<p>Diss. ETH No. 16263</p>
			</richtext>
		</annotation>
		<publisher type="university">ETH Zürich</publisher>
		<title>A Proteomics Approach to the Diagnosis of Alzheimer's Disease</title>
		<identifier type="uri">http://e-collection.ethbib.ethz.ch/show?type=diss&amp;nr=16263</identifier>
		<howpublished>Ph.D. Thesis</howpublished>
	</reference>
	<reference name="ste06">
		<names type="author">
			<person>
				<givenname>Robert</givenname>
				<surname>Stephan</surname>
			</person>
		</names>
		<date value="2006-02"/>
		<abstract>
			<richtext>
				<p>Designing and editing XML Schemas can be simplified by the use of a conceptual model. Therefore a conceptual model, that can handle the fundamental parts of the W3C XML Schema standard has been created and implemented. In addition algorithms have been developed, that describe the derivation of an XML schema from the model (export) and the generation of a model out of an existing XML Schema (import). Furthermore a graphical editor has been developed, that supports users creating and editing the model. XML schema import and export functionalities have been integrated as well.</p>
			</richtext>
		</abstract>
		<address>Rostock, Germany</address>
		<publisher type="university">Universität Rostock</publisher>
		<title>Entwicklung und Implementierung einer Methode zum konzeptionellen Entwurf von XML-Schemata</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-emx"/>; </p>
			</richtext>
		</annotation>
		<identifier type="uri">http://dbis.informatik.uni-rostock.de/Studium/Diplomarbeiten/1124106344.13_0</identifier>
		<howpublished>Master's Thesis</howpublished>
	</reference>
	<reference name="han02">
		<names type="author">
			<person>
				<givenname>Arne</givenname>
				<surname>Handt</surname>
			</person>
		</names>
		<date value="2002-08"/>
		<address>Berlin, Germany</address>
		<publisher type="university">Institut für Softwaretechnik und Theoretische Informatik, Technische Universität Berlin</publisher>
		<title>A Transformation System for XML-based Messaging Channels</title>
		<howpublished>Master's Thesis</howpublished>
	</reference>
	<reference name="wil91a">
		<names type="author">
			<person>
				<givenname>Erik</givenname>
				<surname>Wilde</surname>
			</person>
		</names>
		<date value="1991-05"/>
		<address>Berlin, Germany</address>
		<publisher type="university">Open Communication Systems Group, Technical University Berlin</publisher>
		<title>Distributed Multimedia Documents</title>
		<identifier type="uri">http://dret.net/netdret/publications#wil91a</identifier>
		<howpublished>Master's Thesis</howpublished>
	</reference>
	<reference name="alm92">
		<names type="author">
			<person>
				<givenname>Werner</givenname>
				<surname>Almesberger</surname>
			</person>
			<person>
				<givenname>Markus</givenname>
				<surname>Wild</surname>
			</person>
		</names>
		<date value="1992-08"/>
		<address>Zürich, Switzerland</address>
		<publisher type="university">Computer Engineering and Networks Laboratory, ETH Zürich</publisher>
		<title>Entwurf und Teilimplementierung eines verteilten, multimediafähigen Editors</title>
		<identifier type="uri">http://dret.net/netdret/cv#alm92</identifier>
		<howpublished>Master's Thesis</howpublished>
	</reference>
	<reference name="bau93">
		<names type="author">
			<person>
				<givenname>Daniel</givenname>
				<surname>Bauer</surname>
			</person>
		</names>
		<date value="1993-03"/>
		<address>Zürich, Switzerland</address>
		<publisher type="university">Computer Engineering and Networks Laboratory, ETH Zürich</publisher>
		<title>Erweiterung eines verteilten, multimedialen Editors</title>
		<identifier type="uri">http://dret.net/netdret/cv#bau93</identifier>
		<howpublished>Master's Thesis</howpublished>
	</reference>
	<reference name="das94">
		<names type="author">
			<person>
				<givenname>Marcel</givenname>
				<surname>Dasen</surname>
			</person>
		</names>
		<date value="1994-08"/>
		<address>Zürich, Switzerland</address>
		<publisher type="university">Computer Engineering and Networks Laboratory, ETH Zürich</publisher>
		<title>Rekonfiguration von Protokollen in Da CaPo</title>
		<identifier type="uri">http://dret.net/netdret/cv#das94</identifier>
		<howpublished>Master's Thesis</howpublished>
	</reference>
	<reference name="rue93">
		<names type="author">
			<person>
				<givenname>Niklaus</givenname>
				<surname>Ruess</surname>
			</person>
		</names>
		<date value="1993-03"/>
		<address>Zürich, Switzerland</address>
		<publisher type="university">Computer Engineering and Networks Laboratory, ETH Zürich</publisher>
		<title>Realisierung eines RTF-Andrew-Konverters</title>
		<identifier type="uri">http://dret.net/netdret/cv#rue93</identifier>
		<howpublished>Master's Thesis</howpublished>
	</reference>
	<reference name="kel96">
		<names type="author">
			<person>
				<givenname>Ralph</givenname>
				<surname>Keller</surname>
			</person>
		</names>
		<date value="1996-08"/>
		<address>Zürich, Switzerland</address>
		<publisher type="university">Computer Engineering and Networks Laboratory, ETH Zürich</publisher>
		<title>Multipoint Communication Framework (MCF): Entwicklung eines Transportsubsystems</title>
		<identifier type="uri">http://dret.net/netdret/cv#kel96</identifier>
		<howpublished>Master's Thesis</howpublished>
	</reference>
	<reference name="nan96">
		<names type="author">
			<person>
				<givenname>Murali</givenname>
				<surname>Nanduri</surname>
			</person>
		</names>
		<date value="1996-03"/>
		<address>Zürich, Switzerland</address>
		<field type="bibtex:index">GMS, GUA, GAP</field>
		<publisher type="university">Computer Engineering and Networks Laboratory, ETH Zürich</publisher>
		<field type="bibtex:src">EW</field>
		<title>Namensverwaltung, Adressierung und Verbindungsaufbau für Gruppenkommunikation im Group and Session Management System (GMS)</title>
		<identifier type="uri">http://dret.net/netdret/cv#nan96</identifier>
		<howpublished>Master's Thesis</howpublished>
	</reference>
	<reference name="fre96">
		<names type="author">
			<person>
				<givenname>Pascal</givenname>
				<surname>Freiburghaus</surname>
			</person>
		</names>
		<date value="1996-09"/>
		<address>Zürich, Switzerland</address>
		<field type="bibtex:index">GMS, GSA, GSP</field>
		<publisher type="university">Computer Engineering and Networks Laboratory, ETH Zürich</publisher>
		<field type="bibtex:src">EW</field>
		<title>System-Protokollarchitektur für das Group and Session Management System</title>
		<identifier type="uri">http://dret.net/netdret/cv#fre96</identifier>
		<howpublished>Master's Thesis</howpublished>
	</reference>
	<reference name="kol96">
		<names type="author">
			<person>
				<givenname>Daniel</givenname>
				<surname>Koller</surname>
			</person>
		</names>
		<date value="1996-09"/>
		<address>Zürich, Switzerland</address>
		<field type="bibtex:index">GMS, GSA, GSP</field>
		<publisher type="university">Computer Engineering and Networks Laboratory, ETH Zürich</publisher>
		<field type="bibtex:src">EW</field>
		<title>System-Protokolloperationen für das Group and Session Management System</title>
		<identifier type="uri">http://dret.net/netdret/cv#kol96</identifier>
		<howpublished>Master's Thesis</howpublished>
	</reference>
	<reference name="bue97">
		<names type="author">
			<person>
				<givenname>Markus</givenname>
				<surname>Buechi</surname>
			</person>
		</names>
		<date value="1997-03"/>
		<address>Zürich, Switzerland</address>
		<field type="bibtex:index">GMS, GUA, Da CaPo</field>
		<publisher type="university">Computer Engineering and Networks Laboratory, ETH Zürich</publisher>
		<field type="bibtex:src">CC</field>
		<title>Entwurf und Implementierung einer Multicastunterstützung für Multimedia-Anwendungen</title>
		<howpublished>Master's Thesis</howpublished>
	</reference>
	<reference name="nig96">
		<names type="author">
			<person>
				<givenname>Gerhard</givenname>
				<surname>Nigg</surname>
			</person>
		</names>
		<date value="1996-03"/>
		<address>Zürich, Switzerland</address>
		<field type="bibtex:index">Da CaPo, multicast</field>
		<publisher type="university">Computer Engineering and Networks Laboratory, ETH Zürich</publisher>
		<field type="bibtex:src">DB</field>
		<title>Multicast-Module für Da CaPo</title>
		<howpublished>Master's Thesis</howpublished>
	</reference>
	<reference name="car93">
		<names type="author">
			<person>
				<givenname>Germano</givenname>
				<surname>Caronni</surname>
			</person>
		</names>
		<date value="1993-02"/>
		<address>Zürich, Switzerland</address>
		<publisher type="university">Computer Engineering and Networks Laboratory, ETH Zürich</publisher>
		<title>Konzeption und Entwicklung einer Komponente zur Dokumentenverwaltung</title>
		<identifier type="uri">http://dret.net/netdret/cv#car93</identifier>
		<howpublished>Master's Thesis</howpublished>
	</reference>
	<reference name="sel86">
		<names type="author">
			<person>
				<givenname>Robert</givenname>
				<surname>Seliger</surname>
			</person>
		</names>
		<date value="1986-01"/>
		<address>Cambridge, UK</address>
		<field type="bibtex:index">CES, collaborative editing</field>
		<annotation type="bibtex:note">
			<richtext>
				<p>MIT/LCS/TR-350</p>
			</richtext>
		</annotation>
		<publisher type="university">Massachusetts Institute of Technology</publisher>
		<field type="bibtex:src">EW</field>
		<title>Design and Implementation of a Distributed Program for Collaborative Editing</title>
		<howpublished>Master's Thesis</howpublished>
	</reference>
	<reference name="bos03">
		<names type="author">
			<person>
				<givenname>Alain C.</givenname>
				<surname>Boss</surname>
			</person>
		</names>
		<date value="2003-05"/>
		<address>Berne, Switzerland</address>
		<publisher type="university">Eduswiss</publisher>
		<title>SBA Ranking</title>
		<identifier type="uri">http://dret.net/netdret/cv#bos03</identifier>
		<howpublished>Master's Thesis</howpublished>
	</reference>
	<reference name="nab05">
		<names type="author">
			<person>
				<givenname>Nick</givenname>
				<surname>Nabholz</surname>
			</person>
		</names>
		<date value="2005-06"/>
		<address>Zürich, Switzerland</address>
		<publisher type="university">Hochschule für Technik, Wirtschaft und Verwaltung Zürich</publisher>
		<title>Ein Benutzerkonzept für kollaborative Applikationen am Beispiel von ShaRef</title>
		<identifier type="uri">http://dret.net/netdret/cv#nab05</identifier>
		<howpublished>Master's Thesis</howpublished>
	</reference>
	<reference name="bue05">
		<names type="author">
			<person>
				<givenname>Thierry</givenname>
				<surname>Bücheler</surname>
			</person>
		</names>
		<date value="2005-10"/>
		<address>Zürich, Switzerland</address>
		<publisher type="university">Computer Engineering and Networks Laboratory, ETH Zürich</publisher>
		<title>ShaRefWeb: A Web Interface for the ShaRef Service</title>
		<identifier type="uri">http://dret.net/netdret/cv#bue05</identifier>
		<howpublished>Master's Thesis</howpublished>
	</reference>
	<reference name="sin00">
		<names type="author">
			<person>
				<givenname>Felix</givenname>
				<surname>Singeisen</surname>
			</person>
		</names>
		<date value="2000-08"/>
		<address>Berne, Switzerland</address>
		<publisher type="university">Eduswiss</publisher>
		<title>Messkriterien zur qualitativen Beurteilung von WAP-Services basierend auf verschiedenen Trägerdiensten</title>
		<identifier type="uri">http://dret.net/netdret/cv#sin00</identifier>
		<howpublished>Master's Thesis</howpublished>
	</reference>
	<reference name="kue01">
		<names type="author">
			<person>
				<givenname>Simon</givenname>
				<surname>Künzli</surname>
			</person>
			<person>
				<givenname>Peter</givenname>
				<surname>Zberg</surname>
			</person>
		</names>
		<date value="2001-03"/>
		<address>Zürich, Switzerland</address>
		<publisher type="university">Computer Engineering and Networks Laboratory, ETH Zürich</publisher>
		<title>Design und Implementierung einer Benutzerschnittstelle für den XLinkbase-Zugriff</title>
		<identifier type="uri">http://dret.net/netdret/cv#kue01</identifier>
		<howpublished>Master's Thesis</howpublished>
	</reference>
	<reference name="lur01">
		<names type="author">
			<person>
				<givenname>Brenno</givenname>
				<surname>Lurati</surname>
			</person>
			<person>
				<givenname>Luca</givenname>
				<surname>Previtali</surname>
			</person>
		</names>
		<date value="2001-03"/>
		<address>Zürich, Switzerland</address>
		<publisher type="university">Computer Engineering and Networks Laboratory, ETH Zürich</publisher>
		<title>BibTeXML: Design und Implementierung einer XML-basierten Lösung für BibTeX Literaturreferenzen</title>
		<identifier type="uri">http://dret.net/netdret/cv#lur01</identifier>
		<howpublished>Master's Thesis</howpublished>
	</reference>
	<reference name="lan01">
		<names type="author">
			<person>
				<givenname>Yves</givenname>
				<surname>Langisch</surname>
			</person>
		</names>
		<date value="2001-03"/>
		<address>Zürich, Switzerland</address>
		<publisher type="university">Computer Engineering and Networks Laboratory, ETH Zürich</publisher>
		<title>Design und Implementierung von XLinkbase, einer XML-basierten Datenbank für Ressourcen-Information und ihre Kategorisierung</title>
		<identifier type="uri">http://dret.net/netdret/cv#lan01</identifier>
		<howpublished>Master's Thesis</howpublished>
	</reference>
	<reference name="dob00">
		<names type="author">
			<person>
				<givenname>Dario</givenname>
				<surname>Dobranic</surname>
			</person>
			<person>
				<givenname>Eric</givenname>
				<surname>Schreiber</surname>
			</person>
		</names>
		<date value="2000-08"/>
		<address>Zürich, Switzerland</address>
		<publisher type="university">Computer Engineering and Networks Laboratory, ETH Zürich</publisher>
		<title>Konzept und Implementierung für einen XML- und SQL-basierten Web-Server für Weiterbildungsangebote</title>
		<identifier type="uri">http://dret.net/netdret/cv#dob00</identifier>
		<howpublished>Master's Thesis</howpublished>
	</reference>
	<reference name="obe01">
		<names type="author">
			<person>
				<givenname>Glenn</givenname>
				<surname>Oberholzer</surname>
			</person>
		</names>
		<date value="2001-02"/>
		<address>Zürich, Switzerland</address>
		<publisher type="university">Computer Engineering and Networks Laboratory, ETH Zürich</publisher>
		<title>Design und Usability-Konzepte für die DHTML-basierte Präsentation von XLinks</title>
		<identifier type="uri">http://dret.net/netdret/cv#obe01</identifier>
		<howpublished>Master's Thesis</howpublished>
	</reference>
	<reference name="amr01">
		<names type="author">
			<person>
				<givenname>Marco</givenname>
				<surname>Amrein</surname>
			</person>
		</names>
		<date value="2001-02"/>
		<address>Zürich, Switzerland</address>
		<publisher type="university">Computer Engineering and Networks Laboratory, ETH Zürich</publisher>
		<title>Konzept und Design für ein XLinkbase-Schema für Nachschlagewerke sowie ihre Präsentation</title>
		<identifier type="uri">http://dret.net/netdret/cv#amr01</identifier>
		<howpublished>Master's Thesis</howpublished>
	</reference>
	<reference name="kar01a">
		<names type="author">
			<person>
				<givenname>Alexander</givenname>
				<surname>Karg</surname>
			</person>
		</names>
		<date value="2001-02"/>
		<address>Zürich, Switzerland</address>
		<publisher type="university">Computer Engineering and Networks Laboratory, ETH Zürich</publisher>
		<title>Konzept und Design für ein XLinkbase-Schema für Bildarchive sowie ihrer Präsentation</title>
		<identifier type="uri">http://dret.net/netdret/cv#kar01a</identifier>
		<howpublished>Master's Thesis</howpublished>
	</reference>
	<reference name="kar01b">
		<names type="author">
			<person>
				<givenname>Alexander</givenname>
				<surname>Karg</surname>
			</person>
		</names>
		<date value="2001-08"/>
		<address>Zürich, Switzerland</address>
		<publisher type="university">Computer Engineering and Networks Laboratory, ETH Zürich</publisher>
		<title>Konzept und Implementierung eines Programmes für die Bildarchivierung und -verwaltung</title>
		<identifier type="uri">http://dret.net/netdret/cv#kar01b</identifier>
		<howpublished>Master's Thesis</howpublished>
	</reference>
	<reference name="bas05">
		<names type="author">
			<person>
				<givenname>Marcel</givenname>
				<surname>Baschnagel</surname>
			</person>
		</names>
		<date value="2005-07"/>
		<address>Zürich, Switzerland</address>
		<publisher type="university">Computer Engineering and Networks Laboratory, ETH Zürich</publisher>
		<title>Fragment Identifiers für den text/plain MIME Type</title>
		<identifier type="uri">http://dret.net/netdret/cv#bas05</identifier>
		<howpublished>Master's Thesis</howpublished>
	</reference>
	<reference name="gig06">
		<names type="author">
			<person>
				<givenname>Kaspar</givenname>
				<surname>Giger</surname>
			</person>
		</names>
		<date value="2006-04"/>
		<address>Zürich, Switzerland</address>
		<publisher type="university">Computer Engineering and Networks Laboratory, ETH Zürich</publisher>
		<title>XPath-Unterstützung in einer Linux Shell</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-xpsh"/>; </p>
			</richtext>
		</annotation>
		<identifier type="uri">http://dret.net/netdret/cv#gig06</identifier>
		<howpublished>Master's Thesis</howpublished>
	</reference>
	<reference name="mic07">
		<names type="author">
			<person>
				<givenname>Felix</givenname>
				<surname>Michel</surname>
			</person>
		</names>
		<date value="2007-04"/>
		<address>Zürich, Switzerland</address>
		<publisher type="university">Computer Engineering and Networks Laboratory, ETH Zürich</publisher>
		<title>Visualization of XML Models and Mapping to XML Schemas</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-xmlschema" weight="0.8"/>; </p>
			</richtext>
		</annotation>
		<identifier type="uri">http://dret.net/netdret/cv#mic07</identifier>
		<howpublished>Master's Thesis</howpublished>
	</reference>
	<reference name="fei03">
		<names type="author">
			<person>
				<givenname>Michael</givenname>
				<surname>Feierabend</surname>
			</person>
			<person>
				<givenname>Thomas</givenname>
				<surname>Hägi</surname>
			</person>
		</names>
		<date value="2003-07"/>
		<address>Zürich, Switzerland</address>
		<publisher type="university">Computer Engineering and Networks Laboratory, ETH Zürich</publisher>
		<title>Aufbau und Betrieb eines Konferenzplanungssystems für die WWW2003</title>
		<identifier type="uri">http://dret.net/netdret/cv#fei03</identifier>
		<howpublished>Master's Thesis</howpublished>
	</reference>
	<reference name="gam01">
		<names type="author">
			<person>
				<givenname>Sascha</givenname>
				<surname>Gammaidoni</surname>
			</person>
			<person>
				<givenname>Christian</givenname>
				<surname>Mutti</surname>
			</person>
		</names>
		<date value="2001-08"/>
		<address>Zürich, Switzerland</address>
		<publisher type="university">Computer Engineering and Networks Laboratory, ETH Zürich</publisher>
		<title>Überabeitung und weiterer Aufbau des Servers und der Software für das BibTeXML-Projekt</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-bibtexml" weight="0.9"/>; </p>
			</richtext>
		</annotation>
		<identifier type="uri">http://dret.net/netdret/cv#gam01</identifier>
		<howpublished>Master's Thesis</howpublished>
	</reference>
	<reference name="mey01">
		<names type="author">
			<person>
				<givenname>Manfred</givenname>
				<surname>Meyer</surname>
			</person>
		</names>
		<date value="2001-08"/>
		<address>Zürich, Switzerland</address>
		<publisher type="university">Computer Engineering and Networks Laboratory, ETH Zürich</publisher>
		<title>Design und Implementierung eines Frameworks für das Message Routing &amp; Passing in einem EJB-basierten Server</title>
		<identifier type="uri">http://dret.net/netdret/cv#mey01</identifier>
		<howpublished>Master's Thesis</howpublished>
	</reference>
	<reference name="sti02">
		<names type="author">
			<person>
				<givenname>Christian</givenname>
				<surname>Stillhard</surname>
			</person>
		</names>
		<date value="2002-03"/>
		<address>Zürich, Switzerland</address>
		<publisher type="university">Computer Engineering and Networks Laboratory, ETH Zürich</publisher>
		<title>Methods for Accessing Linkbases</title>
		<identifier type="uri">http://dret.net/netdret/cv#sti02</identifier>
		<howpublished>Master's Thesis</howpublished>
	</reference>
	<reference name="sti03">
		<names type="author">
			<person>
				<givenname>Kilian</givenname>
				<surname>Stillhard</surname>
			</person>
		</names>
		<date value="2003-03"/>
		<address>Zürich, Switzerland</address>
		<publisher type="university">Computer Engineering and Networks Laboratory, ETH Zürich</publisher>
		<title>A Compact Syntax for XML Schema</title>
		<identifier type="uri">http://dret.net/netdret/cv#sti03</identifier>
		<howpublished>Master's Thesis</howpublished>
	</reference>
	<reference name="hau03">
		<names type="author">
			<person>
				<givenname>Felix</givenname>
				<surname>Hauser</surname>
			</person>
			<person>
				<givenname>Philip</givenname>
				<surname>Schaffhauser</surname>
			</person>
		</names>
		<date value="2003-03"/>
		<address>Zürich, Switzerland</address>
		<publisher type="university">Computer Engineering and Networks Laboratory, ETH Zürich</publisher>
		<title>Database-Driven XML-Enabled Bibliography Management System</title>
		<identifier type="uri">http://dret.net/netdret/cv#hau03</identifier>
		<howpublished>Master's Thesis</howpublished>
	</reference>
	<reference name="kra03">
		<names type="author">
			<person>
				<givenname>Beat</givenname>
				<surname>Krähenmann</surname>
			</person>
			<person>
				<givenname>Martin</givenname>
				<surname>Waldburger</surname>
			</person>
		</names>
		<date value="2003-03"/>
		<address>Zürich, Switzerland</address>
		<publisher type="university">Computer Engineering and Networks Laboratory, ETH Zürich</publisher>
		<title>Toolkit für Konferenzprogrammverwaltung und -personalisierung</title>
		<identifier type="uri">http://dret.net/netdret/cv#kra03</identifier>
		<howpublished>Master's Thesis</howpublished>
	</reference>
	<reference name="dce">
		<date value="1997-11"/>
		<address>Cambridge, Massachusetts</address>
		<organization>The Open Group</organization>
		<title>DCE 1.2.2 Documentation</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-dce"/>; </p>
			</richtext>
		</annotation>
	</reference>
	<reference name="truetype">
		<date value="1996-10"/>
		<address>Cupertino, California</address>
		<field type="bibtex:index">TrueType</field>
		<organization>Apple Computer, Inc.</organization>
		<title>The TrueType Reference Manual</title>
	</reference>
	<reference name="corba">
		<date value="1998-07"/>
		<address>Framingham, Massachusetts</address>
		<organization>Object Management Group</organization>
		<title>The Common Object Request Broker: Architecture and Specification — Version 2.2</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-corba"/>; <keywordref type="topic-iiop"/>; <keywordref type="topic-giop"/>; </p>
			</richtext>
		</annotation>
	</reference>
	<reference name="corba26">
		<date value="2001-12"/>
		<address>Framingham, Massachusetts</address>
		<organization>Object Management Group</organization>
		<title>The Common Object Request Broker: Architecture and Specification — Version 2.6</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-corba"/>; <keywordref type="topic-iiop"/>; <keywordref type="topic-giop"/>; </p>
			</richtext>
		</annotation>
		<associations>
			<xref type="updates" target="corba"/>
		</associations>
	</reference>
	<reference name="uml13">
		<date value="1999-06"/>
		<address>Framingham, Massachusetts</address>
		<organization>Object Management Group</organization>
		<title>OMG Unified Modeling Language Specification Version 1.3</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-uml"/>; </p>
			</richtext>
		</annotation>
	</reference>
	<reference name="uml14">
		<date value="2001-09"/>
		<address>Framingham, Massachusetts</address>
		<organization>Object Management Group</organization>
		<title>OMG Unified Modeling Language Specification Version 1.4</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-uml"/>; </p>
			</richtext>
		</annotation>
		<associations>
			<xref type="updates" target="uml13"/>
		</associations>
	</reference>
	<reference name="uml15">
		<date value="2003-03"/>
		<address>Framingham, Massachusetts</address>
		<organization>Object Management Group</organization>
		<title>OMG Unified Modeling Language Specification Version 1.5</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-uml"/>; </p>
			</richtext>
		</annotation>
		<associations>
			<xref type="updates" target="uml14"/>
		</associations>
		<identifier type="uri">http://www.omg.org/cgi-bin/doc?formal/03-03-01</identifier>
	</reference>
	<reference name="uml20super">
		<date value="2004-10"/>
		<address>Framingham, Massachusetts</address>
		<organization>Object Management Group</organization>
		<title>UML 2.0 Superstructure Specification</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-uml"/>; </p>
			</richtext>
		</annotation>
		<associations>
			<xref type="updates" target="uml15"/>
		</associations>
		<identifier type="uri">http://www.omg.org/cgi-bin/doc?ptc/2004-10-02</identifier>
	</reference>
	<reference name="mof13">
		<date value="1999-06"/>
		<address>Framingham, Massachusetts</address>
		<organization>Object Management Group</organization>
		<title>OMG Meta Object Facility Specification Version 1.3</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-mof"/>; </p>
			</richtext>
		</annotation>
	</reference>
	<reference name="mof14">
		<date value="2002-04"/>
		<organization>Object Management Group</organization>
		<title>Meta Object Facility (MOF) Specification — Version 1.4</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-mof"/>; </p>
			</richtext>
		</annotation>
		<associations>
			<xref type="updates" target="mof13"/>
		</associations>
		<identifier type="uri" resourceType="application/pdf">http://www.omg.org/docs/formal/02-04-03.pdf</identifier>
	</reference>
	<reference name="xmi11">
		<date value="1999-10"/>
		<address>Framingham, Massachusetts</address>
		<organization>Object Management Group</organization>
		<title>OMG XML Metadata Interchange (XMI) Specification Version 1.1</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-xmi"/>; </p>
			</richtext>
		</annotation>
	</reference>
	<reference name="xmi12">
		<date value="2002-01"/>
		<address>Framingham, Massachusetts</address>
		<organization>Object Management Group</organization>
		<title>OMG XML Metadata Interchange (XMI) Specification Version 1.2</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-xmi"/>; </p>
			</richtext>
		</annotation>
		<associations>
			<xref type="updates" target="xmi11"/>
		</associations>
		<identifier type="uri">http://www.omg.org/cgi-bin/doc?formal/2002-01-01</identifier>
	</reference>
	<reference name="xmi20">
		<date value="2003-05"/>
		<address>Framingham, Massachusetts</address>
		<organization>Object Management Group</organization>
		<title>OMG XML Metadata Interchange (XMI) Specification Version 2.0</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-xmi"/>; </p>
			</richtext>
		</annotation>
		<associations>
			<xref type="updates" target="xmi12"/>
		</associations>
		<identifier type="uri">http://www.omg.org/cgi-bin/doc?formal/2003-05-02</identifier>
	</reference>
	<reference name="xmi21">
		<date value="2005-09"/>
		<address>Framingham, Massachusetts</address>
		<organization>Object Management Group</organization>
		<title>MOF 2.0/XMI Mapping Specification, v2.1</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-xmi"/>; <keywordref type="topic-mof"/>; </p>
			</richtext>
		</annotation>
		<associations>
			<xref type="updates" target="xmi20"/>
			<xref type="updates" target="mof14"/>
		</associations>
		<identifier type="uri">http://www.omg.org/cgi-bin/doc?formal/2005-09-01</identifier>
	</reference>
	<reference name="mda10">
		<names type="editor">
			<person>
				<givenname>Joaquin</givenname>
				<surname>Miller</surname>
			</person>
			<person>
				<givenname>Jishnu</givenname>
				<surname>Mukerji</surname>
			</person>
		</names>
		<date value="2003-06"/>
		<address>Framingham, Massachusetts</address>
		<organization>Object Management Group</organization>
		<title>MDA Guide Version 1.0.1</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-mda"/>; </p>
			</richtext>
		</annotation>
		<identifier type="uri">http://www.omg.org/cgi-bin/doc?omg/03-06-01</identifier>
	</reference>
	<reference name="hutn">
		<date value="2002-12"/>
		<address>Needham, Massachusetts</address>
		<organization>Object Management Group</organization>
		<title>Human-Usable Textual Notation (HUTN) Specification</title>
		<annotation>
			<richtext>
				<p>Keywords: (undefined keyword: hutn); </p>
			</richtext>
		</annotation>
		<identifier type="uri" resourceType="application/pdf">http://www.dstc.edu.au/Research/Projects/Pegamento/publications/ptc-02-12-01.pdf</identifier>
	</reference>
	<reference name="xtp95">
		<date value="1995-03"/>
		<address>Santa Barbara, California</address>
		<field type="bibtex:index">XTP</field>
		<organization>XTP Forum</organization>
		<title>Xpress Transport Protocol Specification (XTP Revision 4.0)</title>
	</reference>
	<reference name="quantify">
		<date value="1995"/>
		<address>Sunnyvale, California</address>
		<organization>Pure Software Inc.</organization>
		<title>Quantify User's Guide</title>
	</reference>
	<reference name="statemate">
		<date value="1993"/>
		<address>Andover, Massachusetts</address>
		<organization>i-Logix, Inc.</organization>
		<title>Statemate Version 6.0 User Reference Manual</title>
	</reference>
	<reference name="tch03">
		<names type="author">
			<person>
				<givenname>Dmitri</givenname>
				<surname>Tcherevik</surname>
			</person>
		</names>
		<date value="2003-07"/>
		<howpublished>Computer Associates White Paper</howpublished>
		<title>Management and Security in the World of Web Services</title>
		<identifier type="uri">http://www3.ca.com/Solutions/Collateral.asp?CID=47494&amp;ID=4712</identifier>
	</reference>
	<reference name="sed03">
		<names type="author">
			<person>
				<givenname>Igor</givenname>
				<surname>Sedukhin</surname>
			</person>
		</names>
		<date value="2003-03"/>
		<howpublished>Computer Associates White Paper</howpublished>
		<title>End-to-End Security for Web Services and Services Oriented Architectures</title>
		<identifier type="uri">http://www3.ca.com/Solutions/Collateral.asp?CID=42144&amp;ID=4712</identifier>
	</reference>
	<reference name="tiff6">
		<names type="author">
			<name>Aldus Corporation</name>
		</names>
		<date value="1992-06"/>
		<howpublished>Seattle, Washington</howpublished>
		<field type="bibtex:index">TIFF</field>
		<field type="bibtex:src">EW: ~/papers/bibtex</field>
		<title>TIFF — Revision 6.0</title>
	</reference>
	<reference name="gif87">
		<names type="author">
			<name>CompuServe, Incorporated</name>
		</names>
		<date value="1987-06"/>
		<howpublished>Columbus, Ohio</howpublished>
		<field type="bibtex:src">EW: ~/papers/bibtex</field>
		<title>GIF — Graphics Interchange Format</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-gif" weight="0.9"/>; <keywordref type="topic-gif87"/>; </p>
			</richtext>
		</annotation>
	</reference>
	<reference name="gif89a">
		<names type="author">
			<name>CompuServe, Incorporated</name>
		</names>
		<date value="1990-07"/>
		<howpublished>Columbus, Ohio</howpublished>
		<field type="bibtex:src">EW: ~/papers/bibtex</field>
		<title>Graphics Interchange Format — Version 89a</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-gif" weight="0.9"/>; <keywordref type="topic-gif89a"/>; </p>
			</richtext>
		</annotation>
	</reference>
	<reference name="mar04e">
		<names type="author">
			<person>
				<givenname>Paolo</givenname>
				<surname>Marinelli</surname>
			</person>
			<person>
				<givenname>Claudio Sacerdoti</givenname>
				<surname>Coen</surname>
			</person>
			<person>
				<givenname>Fabio</givenname>
				<surname>Vitali</surname>
			</person>
		</names>
		<date value="2004-06"/>
		<abstract>
			<richtext>
				<p>In the past few years, a number of constraint languages for XML documents has been proposed. They are cumulatively called schema languages or validation languages and they comprise, among others, DTD, XML Schema, RELAX NG, Schematron, DSD, xlinkit. One major point of discrimination among schema languages is the support of co-constraints, or co-occurrence constraints, e.g., requiring that attribute A is present if and only if attribute B is (or is not) present in the same element. Although there is no way in XML Schema to express these requirements, they are in fact frequently used in many XML document types, usually only expressed in plain human-readable text, and validated by means of special code modules by the relevant applications. In this paper we propose SchemaPath, a light extension of XML Schema to handle conditional constraints on XML documents. Two new constructs have been added to XML Schema: conditions — based on XPath patterns — on type assignments for elements and attributes; and a new simple type, xsd:error, for the direct expression of negative constraints (e.g., it is prohibited for attribute A to be present if attribute B is also present). A proof-of-concept implementation is provided. A Web interface is publicly accessible for experiments and assessments of the real expressiveness of the proposed extension.</p>
			</richtext>
		</abstract>
		<address>Bologna, Italy</address>
		<publisher type="institution">University of Bologna</publisher>
		<number>UBLCS-2004-13</number>
		<title>SchemaPath: Extending XML Schema for Co-Constraints</title>
		<annotation>
			<richtext>
				<p>Keywords: (undefined keyword: schemapath); </p>
			</richtext>
		</annotation>
		<identifier type="uri" resourceType="application/pdf">http://www.cs.unibo.it/pub/TR/UBLCS/2004/2004-13.pdf</identifier>
	</reference>
	<reference name="sen03b">
		<names type="author">
			<person>
				<givenname>Arijit</givenname>
				<surname>Sengupta</surname>
			</person>
			<person>
				<givenname>Sriram</givenname>
				<surname>Mohan</surname>
			</person>
		</names>
		<date value="2003-04"/>
		<abstract>
			<richtext>
				<p>XML is universally recognized as the standard document format for the purpose of interchange and device-independent presentation. Literature shows many efforts towards the development of formal and conceptual models for XML, although no commonly accepted model exists as yet. In this paper, we present a survey of some formal and conceptual modeling techniques, and discuss the merits and shortcomings of such techniques. We then present HNR (Heterogeneous Nested Relations) a formal modeling method for representing XML, and discuss how this formal model could be used to derive many useful results on XML query language, and how this could lead to a potential conceptual modeling technique as well.</p>
			</richtext>
		</abstract>
		<address>Bloomington, Indiana</address>
		<publisher type="institution">Indiana University, Information Systems Department</publisher>
		<number>137-1</number>
		<title>Formal and Conceptual Models for XML Structures — The Past, Present, and Future</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-hnr" weight="0.9"/>; </p>
			</richtext>
		</annotation>
		<identifier type="uri" resourceType="application/pdf">http://www.indiana.edu/~isdept/research/papers/tr137-1.pdf</identifier>
	</reference>
	<reference name="hod00">
		<names type="author">
			<person>
				<givenname>Gail</givenname>
				<surname>Hodge</surname>
			</person>
		</names>
		<date value="2000-04"/>
		<abstract>
			<richtext>
				<p>This report examines the use of knowledge organization systems — schemes for organizing information and facilitating knowledge management — in a digital environment. Knowledge organization systems serve as bridges between a user's information needs and the material in a collection. Examples of such systems include term lists, such as dictionaries; classification schemes, such as Library of Congress Subject Headings; and relationship lists, such as thesauri. These and other types of knowledge organization systems, which vary in complexity, structure, and function, can improve the organization of digital libraries and facilitate access to their content.</p>
			</richtext>
		</abstract>
		<address>Washington, D.C.</address>
		<publisher type="institution">Council on Library and Information Resources</publisher>
		<identifier type="isbn">1-887334-76-9</identifier>
		<number>91</number>
		<title>Systems of Knowledge Organization for Digital Libraries: Beyond Traditional Authority Files</title>
		<identifier type="uri" resourceType="text/html">http://www.clir.org/pubs/abstract/pub91abst.html</identifier>
	</reference>
	<reference name="cob02">
		<names type="author">
			<person>
				<givenname>Grégory</givenname>
				<surname>Cobéna</surname>
			</person>
			<person>
				<givenname>Talel</givenname>
				<surname>Abdessalem</surname>
			</person>
			<person>
				<givenname>Yassine</givenname>
				<surname>Hinnach</surname>
			</person>
		</names>
		<date value="2002-07"/>
		<abstract>
			<richtext>
				<p>Change detection is an important part of version management for databases and document archives. The success of XML has recently renewed interest in change detection on trees and semi-structured data, and various algorithms have been proposed. We study here different algorithms and representations of changes based on their formal definition and on experiments conducted over XML data from the Web. Our goal is to provide an evaluation of (i) the quality of the results (ii) the performance of the tools. We also consider in which context each of these algorithms can be best used.</p>
			</richtext>
		</abstract>
		<address>Rocquencourt, France</address>
		<publisher type="institution">Institut National de Recherche en Informatique et en Automatique</publisher>
		<title>A comparative study for XML change detection</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-xml" weight="0.7"/>; </p>
			</richtext>
		</annotation>
		<identifier type="uri" resourceType="application/pdf">ftp://ftp.inria.fr/INRIA/Projects/verso/VersoReport-221.pdf</identifier>
	</reference>
	<reference name="sah02">
		<names type="author">
			<person>
				<givenname>Akhil</givenname>
				<surname>Sahai</surname>
			</person>
			<person>
				<givenname>Anna</givenname>
				<surname>Durante</surname>
			</person>
			<person>
				<givenname>Vijay</givenname>
				<surname>Machiraju</surname>
			</person>
		</names>
		<date value="2002-07"/>
		<abstract>
			<richtext>
				<p>In order to automate SLA management it is essential to specify SLAs in precise and unambiguous manner as well as keep the specification flexible. While precision will help automate the process of monitoring and metric collection, flexibility will enable extending it to unforeseen service level agreement specifications.</p>
			</richtext>
		</abstract>
		<address>Palo Alto, California</address>
		<publisher type="institution">HP Laboratories</publisher>
		<number>HPL-2001-310R1</number>
		<title>Towards Automated SLA Management for Web Services</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-wsml3"/>; </p>
			</richtext>
		</annotation>
		<identifier type="uri" resourceType="text/html">http://www.hpl.hp.com/techreports/2001/HPL-2001-310R1.html</identifier>
	</reference>
	<reference name="bak95">
		<names type="author">
			<person>
				<givenname>Shahram</givenname>
				<surname>Bakhtiari</surname>
			</person>
			<person>
				<givenname>Reihaneh</givenname>
				<surname>Safavi-Naini</surname>
			</person>
			<person>
				<givenname>Josef</givenname>
				<surname>Pieprzyk</surname>
			</person>
		</names>
		<date value="1995-07"/>
		<publisher type="institution">Department of Computer Science, University of Wollongong</publisher>
		<number>95-09</number>
		<title>Cryptographic Hash Functions: A Survey</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-chf"/>; </p>
			</richtext>
		</annotation>
	</reference>
	<reference name="pag99">
		<names type="author">
			<person>
				<givenname>Lawrence</givenname>
				<surname>Page</surname>
			</person>
			<person>
				<givenname>Sergey</givenname>
				<surname>Brin</surname>
			</person>
			<person>
				<givenname>Rajeev</givenname>
				<surname>Motwani</surname>
			</person>
			<person>
				<givenname>Terry</givenname>
				<surname>Winograd</surname>
			</person>
		</names>
		<date value="1999-11"/>
		<publisher type="institution">Stanford University</publisher>
		<number>SIDL-WP-1999-0120</number>
		<title>The PageRank Citation Ranking: Bringing Order to the Web</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-pagerank"/>; </p>
			</richtext>
		</annotation>
		<identifier type="uri">http://dbpubs.stanford.edu/pub/1999-66</identifier>
	</reference>
	<reference name="obe04">
		<names type="author">
			<person>
				<givenname>Felix</givenname>
				<surname>Oberholzer</surname>
			</person>
			<person>
				<givenname>Koleman</givenname>
				<surname>Strumpf</surname>
			</person>
		</names>
		<date value="2004-03"/>
		<address>Chapel Hill, North Carolina</address>
		<publisher type="institution">University of North Carolina</publisher>
		<title>The Effect of File Sharing on Record Sales: An Empirical Analysis</title>
		<identifier type="uri" resourceType="application/pdf">http://www.unc.edu/~cigar/papers/FileSharing_March2004.pdf</identifier>
	</reference>
	<reference name="riz01a">
		<names type="author">
			<person>
				<givenname>Romeo</givenname>
				<surname>Rizzi</surname>
			</person>
		</names>
		<date value="2001-01"/>
		<address>Trento, Italy</address>
		<publisher type="institution">Istituto Trentino di Cultura</publisher>
		<title>Complexity of Context-Free Grammars with Exceptions</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-xml" weight="0.8"/>; <keywordref type="topic-sgml" weight="0.8"/>; </p>
			</richtext>
		</annotation>
	</reference>
	<reference name="kil98">
		<names type="author">
			<person>
				<givenname>Pekka</givenname>
				<surname>Kilpeläinen</surname>
			</person>
		</names>
		<date value="1998-05"/>
		<abstract>
			<richtext>
				<p>The SGML and XML standards use a variation of regular expressions called content models for modeling the markup structures of document elements. SGML content models may include so called and groups, which are excluded from XML. An and group, which is a sequence of subexpressions separated by an &amp;-operator, denotes the sequential catenation of its subexpressions in any possible order. If one wants to shift from SGML to XML in document production, one has to translate SGML content models to corresponding XML content models. The allowed content models in both SGML and XML are restricted by a requirement of determinism, which means that a parser recognizing document element contents has to be able to decide without lookahead, which content model token to match with the current input token, while processing the document from left to right. It is known that not all SGML content models can be expressed as an equivalent XML content model. It is also known that transforming an SGML content model into an equivalent XML content model may cause an exponential growth in the length of the content model. We discuss methods of eliminating and groups and analyze the circumstances where they can be applied. We derive a tight bound of e n! on the number of symbols in the result of eliminating an and group of n symbols, where e = 2.71828... is the base of natural logarithms. We present the analysis in a pedagogical manner, emphasizing mathematical methods which are typical to the analysis of algorithms. We also show that minimal deterministic automata for recognizing an and group of n distinct element names contain 2^n states and n^{2n-1} transitions, excluding the failure state and transitions leading to it.</p>
			</richtext>
		</abstract>
		<address>Helsinki, Finland</address>
		<publisher type="institution">University of Helsinki</publisher>
		<number>Department of Computer Science Report C-1998-12</number>
		<title>SGML &amp; XML Content Models</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-xml" weight="0.8"/>; <keywordref type="topic-sgml" weight="0.8"/>; </p>
			</richtext>
		</annotation>
		<identifier type="uri" resourceType="text/html">http://citeseer.nj.nec.com/85205.html</identifier>
		<identifier type="uri">http://www.cs.helsinki.fi/TR/C-1998/12/</identifier>
	</reference>
	<reference name="kil99">
		<names type="author">
			<person>
				<givenname>Pekka</givenname>
				<surname>Kilpeläinen</surname>
			</person>
			<person>
				<givenname>Derick</givenname>
				<surname>Wood</surname>
			</person>
		</names>
		<date value="1999-01"/>
		<abstract>
			<richtext>
				<p>The Standard Generalized Markup Language (SGML) and the Extensible Markup Language (XML) allow users to define document-type definitions (DTDs), which are essentially extended context-free grammars expressed in a notation that is similar to extended Backus-Naur form. The right-hand side of a production, called a content model, is both an extended and a restricted regular expression. The semantics of content models for SGML DTDs can be modified by exceptions (XML does not allow exceptions). Inclusion exceptions allow named elements to appear anywhere within the content of a content model, and exclusion exceptions preclude named elements from appearing in the content of a content model. We give precise definitions of the semantics of exceptions, and prove that they do not increase the expressive power of SGML DTDs when we restrict DTDs according to accepted SGML practice. We prove the following results: 1. Exceptions do not increase the expressive power of extended context-free grammars. 2. For each DTD with exceptions, we can obtain a structurally equivalent extended context-free grammar. 3. For each DTD with exceptions, we can construct a structurally equivalent DTD when we restrict the DTD to adhere to accepted SGML practice. 4. Exceptions are a powerful shorthand notation — eliminating them may cause exponential growth in the size of an extended context-free grammar or of a DTD.</p>
			</richtext>
		</abstract>
		<address>Hong Kong</address>
		<publisher type="institution">Hong Kong University of Science &amp; Technology</publisher>
		<number>HKUST-TCSC-99-01</number>
		<title>SGML and XML Document Grammars and Exceptions</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-xml" weight="0.8"/>; <keywordref type="topic-sgml" weight="0.8"/>; </p>
			</richtext>
		</annotation>
		<identifier type="uri" resourceType="text/html">http://citeseer.nj.nec.com/335929.html</identifier>
		<identifier type="uri">http://portal.acm.org/citation.cfm?id=501973</identifier>
		<identifier type="uri" resourceType="application/pdf">http://xml.coverpages.org/exceptionsHK-1999-01.pdf</identifier>
	</reference>
	<reference name="sch04a">
		<names type="author">
			<person>
				<givenname>Kuno</givenname>
				<surname>Schedler</surname>
			</person>
			<person>
				<givenname>Lukas</givenname>
				<surname>Summermatter</surname>
			</person>
		</names>
		<date value="2004-02"/>
		<address>St. Gallen, Switzerland</address>
		<publisher type="institution">Institut für Öffentliche Dienstleistungen und Tourismus, Universität St. Gallen</publisher>
		<identifier type="isbn">3-9522667-2-8</identifier>
		<number>IDT-Working Paper Nr. 8a</number>
		<title>2. Bericht zum Stand von E-Government in der Schweiz 2003 — Teil Gemeinden</title>
	</reference>
	<reference name="sch04b">
		<names type="author">
			<person>
				<givenname>Kuno</givenname>
				<surname>Schedler</surname>
			</person>
			<person>
				<givenname>Lukas</givenname>
				<surname>Summermatter</surname>
			</person>
		</names>
		<date value="2004-02"/>
		<address>St. Gallen, Switzerland</address>
		<publisher type="institution">Institut für Öffentliche Dienstleistungen und Tourismus, Universität St. Gallen</publisher>
		<identifier type="isbn">3-9522667-3-6</identifier>
		<number>IDT-Working Paper Nr. 8b</number>
		<title>2. Bericht zum Stand von E-Government in der Schweiz 2003 — Teil Kantone</title>
	</reference>
	<reference name="sch04c">
		<names type="author">
			<person>
				<givenname>Kuno</givenname>
				<surname>Schedler</surname>
			</person>
			<person>
				<givenname>Lukas</givenname>
				<surname>Summermatter</surname>
			</person>
		</names>
		<date value="2004-02"/>
		<address>St. Gallen, Switzerland</address>
		<publisher type="institution">Institut für Öffentliche Dienstleistungen und Tourismus, Universität St. Gallen</publisher>
		<identifier type="isbn">3-9522667-4-4</identifier>
		<number>IDT-Working Paper Nr. 8c</number>
		<title>2. Bericht zum Stand von E-Government in der Schweiz 2003 — Teil Bund</title>
	</reference>
	<reference name="bru91">
		<names type="author">
			<person>
				<givenname>Anne</givenname>
				<surname>Brüggemann-Klein</surname>
			</person>
			<person>
				<givenname>Derick</givenname>
				<surname>Wood</surname>
			</person>
		</names>
		<date value="1991-10"/>
		<address>Freiburg, Germany</address>
		<publisher type="institution">Universität Freiburg</publisher>
		<title>Deterministic Regular Languages</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-xml" weight="0.8"/>; <keywordref type="topic-sgml" weight="0.8"/>; </p>
			</richtext>
		</annotation>
		<identifier type="uri">http://www.informatik.uni-freiburg.de/tr/1991/Report38/</identifier>
	</reference>
	<reference name="sha03">
		<names type="author">
			<person>
				<givenname>Paul</givenname>
				<surname>Shabajee</surname>
			</person>
		</names>
		<date value="2003-06"/>
		<abstract>
			<richtext>
				<p>This report is a review of personal bibliographic management software and systems — it provides a fairly comprehensive review of available systems, functionality and issues in personal bibliographic data management. It was produced as part of background research for the SWAD-E Semantic Blogging Demonstrator Research and was funded by HP Labs as part of the SWARA project based in ILRT.</p>
			</richtext>
		</abstract>
		<address>Bristol, UK</address>
		<publisher type="institution">Institute for Learning and Research Technology</publisher>
		<number>ILRT Research Report Number 1032</number>
		<title>Review of Personal Bibliographic Systems</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-bibtex" weight="0.7"/>; </p>
			</richtext>
		</annotation>
		<identifier type="uri">http://www.ilrt.bris.ac.uk/publications/researchreport/rr1032/report_html</identifier>
	</reference>
	<reference name="cod69">
		<names type="author">
			<person>
				<givenname>Edgar F.</givenname>
				<surname>Codd</surname>
			</person>
		</names>
		<date value="1969-06"/>
		<address>San Jose, California</address>
		<publisher type="institution">IBM</publisher>
		<number>IBM Research Report RJ599</number>
		<title>Derivability, Redundancy and Consistency of Relations Stored in Large Data Banks</title>
		<identifier type="uri" resourceType="text/html">http://www.informatik.uni-trier.de/~ley/db/labs/ibm/RJ599.html</identifier>
	</reference>
	<reference name="boo99">
		<names type="author">
			<person>
				<givenname>Grady</givenname>
				<surname>Booch</surname>
			</person>
			<person>
				<givenname>Magnus</givenname>
				<surname>Christerson</surname>
			</person>
			<person>
				<givenname>Matthew</givenname>
				<surname>Fuchs</surname>
			</person>
			<person>
				<givenname>Jari</givenname>
				<surname>Koistinen</surname>
			</person>
		</names>
		<date value="1999-12"/>
		<publisher type="institution">Rational Software Corp. and CommerceOne Inc.</publisher>
		<title>UML for XML Schema Mapping Specification</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-xml" weight="0.8"/>; <keywordref type="topic-uml" weight="0.8"/>; <keywordref type="topic-xmlschema" weight="0.8"/>; <keywordref type="topic-sox" weight="0.7"/>; </p>
			</richtext>
		</annotation>
		<identifier type="uri" resourceType="application/pdf">http://xml.coverpages.org/fuchs-uml_xmlschema33.pdf</identifier>
	</reference>
	<reference name="bur46">
		<names type="author">
			<person>
				<givenname>Arthur W.</givenname>
				<surname>Burks</surname>
			</person>
			<person>
				<givenname>Herman H.</givenname>
				<surname>Goldstine</surname>
			</person>
			<person>
				<givenname>John</givenname>
				<surname link="von">Neumann</surname>
			</person>
		</names>
		<date value="1946-06"/>
		<address>Princeton, New Jersey</address>
		<publisher type="institution">Institute for Advanced Study</publisher>
		<title>Preliminary Discussion of the Logical Design of an Electronic Computing Instrument</title>
		<identifier type="uri" resourceType="text/html">http://www.cs.unc.edu/~adyilie/comp265/vonNeumann.html</identifier>
	</reference>
	<reference name="cro02">
		<names type="author">
			<person>
				<givenname>Raym</givenname>
				<surname>Crow</surname>
			</person>
		</names>
		<date value="2002-08"/>
		<address>Washington, D.C.</address>
		<publisher type="institution">The Scholarly Publishing &amp; Academic Resources Coalition</publisher>
		<title>The Case for Institutional Repositories: A SPARC Position Paper</title>
		<identifier type="uri" resourceType="text/html">http://www.arl.org/sparc/IR/ir.html</identifier>
	</reference>
	<reference name="myview98">
		<names type="author">
			<person>
				<givenname>Jens E.</givenname>
				<surname>Wolff</surname>
			</person>
			<person>
				<givenname>Armin B.</givenname>
				<surname>Cremers</surname>
			</person>
		</names>
		<date value="1998-12"/>
		<address>Bonn, Germany</address>
		<field type="bibtex:index">MyView</field>
		<publisher type="institution">University of Bonn</publisher>
		<number>IAI-TR-98-13</number>
		<title>The MyView Project: From Heterogeneous Bibliographic Information Repositories to Personalized Digital Libraries</title>
	</reference>
	<reference name="sus75">
		<names type="author">
			<person>
				<givenname>Gerald Jay</givenname>
				<surname>Sussman</surname>
			</person>
			<person>
				<givenname>Guy Lewis</givenname>
				<surname>Steele</surname>
			</person>
		</names>
		<date value="1975-12"/>
		<address>Cambridge, UK</address>
		<publisher type="institution">Massachusetts Institute of Technology</publisher>
		<number>AI Memo No. 349</number>
		<title>Scheme: An Interpreter for Extended Lambda Calculus</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-scheme"/>; </p>
			</richtext>
		</annotation>
		<identifier type="uri" resourceType="application/pdf">ftp://publications.ai.mit.edu/ai-publications/pdf/AIM-349.pdf</identifier>
	</reference>
	<reference name="xpl">
		<names type="author">
			<person>
				<givenname>Erik</givenname>
				<surname>Bruchez</surname>
			</person>
		</names>
		<date value="2002-10"/>
		<address>Mountain View, California</address>
		<publisher type="institution">Orbeon, Inc.</publisher>
		<title>An Introduction to XML Pipelines</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-xpl"/>; </p>
			</richtext>
		</annotation>
	</reference>
	<reference name="xmlppm">
		<names type="author">
			<person>
				<givenname>James</givenname>
				<surname>Cheney</surname>
			</person>
		</names>
		<date value="2000-11"/>
		<address>Ithaca, New York</address>
		<publisher type="institution">Cornell University</publisher>
		<title>Compressing XML with Multiplexed Hierarchical PPM Models</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-xmlppm"/>; <keywordref type="topic-esax"/>; <keywordref type="topic-mhm"/>; <keywordref type="topic-ppm" weight="0.7"/>; <keywordref type="topic-xml" weight="0.7"/>; </p>
			</richtext>
		</annotation>
	</reference>
	<reference name="xmill">
		<names type="author">
			<person>
				<givenname>Hartmut</givenname>
				<surname>Liefke</surname>
			</person>
			<person>
				<givenname>Dan</givenname>
				<surname>Suciu</surname>
			</person>
		</names>
		<date value="1999"/>
		<address>Philadelphia, Pennsylvania</address>
		<publisher type="institution">University of Pennsylvania</publisher>
		<number>MS-CIS-99-26</number>
		<title>XMill: An Efficient Compressor for XML Data</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-xmill"/>; <keywordref type="topic-xml" weight="0.7"/>; </p>
			</richtext>
		</annotation>
	</reference>
	<reference name="j2ee13">
		<names type="author">
			<person>
				<givenname>Bill</givenname>
				<surname>Shannon</surname>
			</person>
		</names>
		<date value="2001-07"/>
		<publisher type="institution">Sun Microsystems</publisher>
		<title>Java 2 Platform Enterprise Edition Specification, v1.3</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-j2ee"/>; </p>
			</richtext>
		</annotation>
	</reference>
	<reference name="sch02b">
		<names type="author">
			<person>
				<givenname>Bob</givenname>
				<surname>Schloss</surname>
			</person>
		</names>
		<date value="2002-02"/>
		<publisher type="institution">IBM</publisher>
		<title>XML Schema Infoset API Requirements</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-xmlschema" weight="0.8"/>; <keywordref type="topic-dom" weight="0.8"/>; </p>
			</richtext>
		</annotation>
		<identifier type="uri" resourceType="text/html">http://www.research.ibm.com/XML/schema/WD-XML-Schema-Infoset-API-Req.htm</identifier>
	</reference>
	<reference name="wsfl10">
		<names type="author">
			<person>
				<givenname>Frank</givenname>
				<surname>Leymann</surname>
			</person>
		</names>
		<date value="2001-05"/>
		<publisher type="institution">IBM</publisher>
		<title>Web Services Flow Language (WSFL 1.0)</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-wsfl"/>; </p>
			</richtext>
		</annotation>
		<identifier type="uri" resourceType="application/pdf">http://www.ibm.com/software/solutions/webservices/pdf/WSFL.pdf</identifier>
	</reference>
	<reference name="jta101">
		<names type="author">
			<person>
				<givenname>Susan</givenname>
				<surname>Cheung</surname>
			</person>
			<person>
				<givenname>Vlada</givenname>
				<surname>Matena</surname>
			</person>
		</names>
		<date value="1999-04"/>
		<publisher type="institution">Sun Microsystems</publisher>
		<title>Java Transaction API (JTA) — Version 1.0.1</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-jta"/>; </p>
			</richtext>
		</annotation>
	</reference>
	<reference name="jms102">
		<names type="author">
			<person>
				<givenname>Mark</givenname>
				<surname>Hapner</surname>
			</person>
			<person>
				<givenname>Rich</givenname>
				<surname>Burridge</surname>
			</person>
			<person>
				<givenname>Rahul</givenname>
				<surname>Sharma</surname>
			</person>
			<person>
				<givenname>Joseph</givenname>
				<surname>Fialli</surname>
			</person>
		</names>
		<date value="2001-08"/>
		<publisher type="institution">Sun Microsystems</publisher>
		<title>Java Message Service — Version 1.0.2b</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-jms"/>; </p>
			</richtext>
		</annotation>
	</reference>
	<reference name="pat88">
		<names type="author">
			<person>
				<givenname>Oren</givenname>
				<surname>Patashnik</surname>
			</person>
		</names>
		<date value="1988-02"/>
		<title>BibTeXing</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-bibtex"/>; </p>
			</richtext>
		</annotation>
	</reference>
	<reference name="pat88b">
		<names type="author">
			<person>
				<givenname>Oren</givenname>
				<surname>Patashnik</surname>
			</person>
		</names>
		<date value="1988-02"/>
		<title>Designing BibTeX Styles</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-bibtex"/>; </p>
			</richtext>
		</annotation>
	</reference>
	<reference name="dig35">
		<names type="author">
			<name>Digital Imaging Group</name>
		</names>
		<date value="2000-08"/>
		<address>Millbrae, California</address>
		<title>DIG35 Specification — Metadata for Digital Images (Version 1.0)</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-metadata" weight="0.8"/>; </p>
			</richtext>
		</annotation>
	</reference>
	<reference name="car00">
		<names type="author">
			<person>
				<givenname>Leslie A.</givenname>
				<surname>Carr</surname>
			</person>
			<person>
				<givenname>Wendy</givenname>
				<surname>Hall</surname>
			</person>
			<person>
				<givenname>Timothy</givenname>
				<surname>Miles-Board</surname>
			</person>
		</names>
		<date value="2000-02"/>
		<abstract>
			<richtext>
				<p>The Web is a linked literature: we wish to discover what the authors of Web pages are choosing to link and what they are choosing to link to. It is hoped that understanding interconnectedness as it is practised in the Web through links will enable us to see what kinds of hypertext are achievable using common technologies and what is impracticable. Understanding the arrangement of the links helps us to understand the construction of the page as a whole which in turn helps us to understand the purpose of the links. This paper discusses a search for examples of good subject-based hypertext linking, the linking statistics that we drew from those pages and the linking practises that the statistics represent. We also show how the analysis of how hypertext links are written can be applied to the problem of Web page reading in non-standard and reduced-bandwidth Web browsing applications.</p>
			</richtext>
		</abstract>
		<address>Southampton, UK</address>
		<field type="bibtex:index">WWW, hypermedia</field>
		<publisher type="institution">Multimedia Research Group, University of Southampton</publisher>
		<number>ECSTR-IAM00-1</number>
		<title>Writing and Reading Hypermedia on the Web</title>
		<identifier type="uri" resourceType="text/html">http://www.bib.ecs.soton.ac.uk/cgi-bin/data/3368/html/WRWH.html</identifier>
	</reference>
	<reference name="moo97">
		<names type="author">
			<person>
				<givenname>Keith</givenname>
				<surname>Moore</surname>
			</person>
			<person>
				<givenname>Shirley</givenname>
				<surname>Browne</surname>
			</person>
			<person>
				<givenname>Jason</givenname>
				<surname>Cox</surname>
			</person>
			<person>
				<givenname>Jonathan</givenname>
				<surname>Gettler</surname>
			</person>
		</names>
		<date value="1997-01"/>
		<address>Knoxville, Tennessee</address>
		<field type="bibtex:index">RCDS</field>
		<publisher type="institution">University of Tennessee</publisher>
		<number>UT-CS-97-346</number>
		<title>Resource Cataloging and Distribution System</title>
	</reference>
	<reference name="bie96">
		<names type="author">
			<person>
				<givenname>Tim</givenname>
				<surname>Bienz</surname>
			</person>
			<person>
				<givenname>Richard</givenname>
				<surname>Cohn</surname>
			</person>
			<person>
				<givenname>James R.</givenname>
				<surname>Meehan</surname>
			</person>
		</names>
		<date value="1996-11"/>
		<address>San Jose, California</address>
		<publisher type="institution">Adobe Systems Inc.</publisher>
		<title>Portable Document Format Reference Manual — Version 1.2</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-pdf"/>; </p>
			</richtext>
		</annotation>
		<associations>
			<xref type="updates" target="bie93"/>
		</associations>
	</reference>
	<reference name="spe94b">
		<names type="author">
			<person>
				<givenname>C. Michael</givenname>
				<surname>Sperberg-McQueen</surname>
			</person>
			<person>
				<givenname>Lou</givenname>
				<surname>Burnard</surname>
			</person>
		</names>
		<date value="1994-04"/>
		<address>Chicago, Illinois</address>
		<field type="bibtex:index">TEI P3</field>
		<publisher type="institution">Text Encoding Initiative</publisher>
		<title>Guidelines for Electronic Text Encoding and Interchange (TEI P3)</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-tei"/>; </p>
			</richtext>
		</annotation>
	</reference>
	<reference name="teip4">
		<names type="author">
			<person>
				<givenname>C. Michael</givenname>
				<surname>Sperberg-McQueen</surname>
			</person>
			<person>
				<givenname>Lou</givenname>
				<surname>Burnard</surname>
			</person>
		</names>
		<date value="2002-03"/>
		<address>Oxford — Providence — Charlottesville — Bergen</address>
		<field type="bibtex:index">TEI P4</field>
		<publisher type="institution">Text Encoding Initiative</publisher>
		<title>The Text Encoding Initiative Guidelines (P4)</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-tei"/>; </p>
			</richtext>
		</annotation>
		<identifier type="uri">http://etext.lib.virginia.edu/teip4/</identifier>
	</reference>
	<reference name="riv95">
		<names type="author">
			<person>
				<givenname>Ronald L.</givenname>
				<surname>Rivest</surname>
			</person>
		</names>
		<date value="1997-03"/>
		<address>Cambridge, Massachusetts</address>
		<field type="bibtex:index">RC5</field>
		<publisher type="institution">MIT Laboratory for Computer Science</publisher>
		<title>The RC5 Encryption Algorithm</title>
	</reference>
	<reference name="ell98">
		<names type="author">
			<person>
				<givenname>Castedo</givenname>
				<surname>Ellerman</surname>
			</person>
		</names>
		<date value="1998-04"/>
		<address>Redmond, Washington</address>
		<field type="bibtex:index">CDF</field>
		<publisher type="institution">Microsoft Corporation</publisher>
		<title>Channel Definition Format (CDF) — Version 1.01</title>
	</reference>
	<reference name="mad01">
		<names type="author">
			<person>
				<givenname>Jayant</givenname>
				<surname>Madhavan</surname>
			</person>
			<person>
				<givenname>Philip A.</givenname>
				<surname>Bernstein</surname>
			</person>
			<person>
				<givenname>Erhard</givenname>
				<surname>Rahm</surname>
			</person>
		</names>
		<date value="2001-08"/>
		<abstract>
			<richtext>
				<p>Schema matching is a critical step in many applications, such as XML message mapping, data warehouse loading, and  schema integration. In this paper, we investigate algorithms for generic schema  matching, outside of any particular data model or application. We first present a taxonomy for past solutions, showing that a rich range of techniques is available. We then propose a new algorithm, Cupid, that discovers mappings between schema elements based on their names, data types, constraints,  and schema structure, using a broader set of techniques than past approaches. Some of our innovations are the integrated use of  linguistic and structural matching, context-dependent matching of shared types, and a bias toward leaf structure where much of  the schema content resides. After describing our algorithm, we present experimental results that compare Cupid to two other schema matching systems.</p>
			</richtext>
		</abstract>
		<address>Redmond, Washington</address>
		<publisher type="institution">Microsoft Corporation</publisher>
		<title>Generic Schema Matching with Cupid</title>
		<annotation>
			<richtext>
				<p>Keywords: (undefined keyword: cupid); </p>
			</richtext>
		</annotation>
		<identifier type="uri" resourceType="application/pdf">http://www.sice.umkc.edu/~leeyu/class/CS690L/Reference/Cupid.pdf</identifier>
	</reference>
	<reference name="ham92">
		<names type="author">
			<person>
				<givenname>Eric</givenname>
				<surname>Hamilton</surname>
			</person>
		</names>
		<date value="1992-09"/>
		<address>Milpitas, California</address>
		<publisher type="institution">C-Cube Microsystems</publisher>
		<field type="bibtex:src">EW: ~/papers/bibtex</field>
		<title>JPEG File Interchange Format (Version 1.02)</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-jpeg" weight="0.8"/>; <keywordref type="topic-jfif"/>; </p>
			</richtext>
		</annotation>
	</reference>
	<reference name="wau94">
		<names type="author">
			<person>
				<givenname>Andrew</givenname>
				<surname>Waugh</surname>
			</person>
		</names>
		<date value="1994-03"/>
		<address>Sydney, Australia</address>
		<field type="bibtex:index">X.500</field>
		<publisher type="institution">CSIRO, Division of Information Technology</publisher>
		<number>TR-SA-94-03</number>
		<field type="bibtex:src">EW: ~/papers/bibtex</field>
		<title>X.500 and the 1993 Standard</title>
	</reference>
	<reference name="koe96">
		<names type="author">
			<person>
				<givenname>Eckhart</givenname>
				<surname>Koerner</surname>
			</person>
		</names>
		<date value="1996-09"/>
		<address>Liège, Belgium</address>
		<field type="bibtex:index">TINA, group management, multimedia, collaboration</field>
		<publisher type="institution">Faculteé des Sciences Appliquées, Université de Liège</publisher>
		<annotation type="bibtex:note">
			<richtext>
				<p>Presented at EUNICE'96 Summer School on Telecommunications Services</p>
			</richtext>
		</annotation>
		<title>Group Management for a Multimedia Collaboration Service</title>
	</reference>
	<reference name="tre95">
		<names type="author">
			<person>
				<givenname>Gene</givenname>
				<surname>Trent</surname>
			</person>
			<person>
				<givenname>Mark</givenname>
				<surname>Sake</surname>
			</person>
		</names>
		<date value="1995-02"/>
		<address>Mountain View, California</address>
		<field type="bibtex:index">WWW, HTTP, performance evaluation, benchmark</field>
		<publisher type="institution">Silicon Graphics, Inc.</publisher>
		<title>WebSTONE: The First Generation in HTTP Server Benchmarking</title>
	</reference>
	<reference name="pad95">
		<names type="author">
			<person>
				<givenname>Venkata N.</givenname>
				<surname>Padmanabhan</surname>
			</person>
		</names>
		<date value="1995-05"/>
		<field type="bibtex:index">WWW, HTTP, prefetching</field>
		<publisher type="institution">University of California, Berkeley</publisher>
		<number>CSD-95-875</number>
		<title>Improving World Wide Web Latency</title>
	</reference>
	<reference name="sch91">
		<names type="author">
			<person>
				<givenname>Eve M.</givenname>
				<surname>Schooler</surname>
			</person>
		</names>
		<date value="1991-11"/>
		<address>Marina del Rey, California</address>
		<field type="bibtex:index">mbone</field>
		<publisher type="institution">University of Southern California, Information Sciences Institute</publisher>
		<number>ISI/RR-91-289</number>
		<field type="bibtex:src">EW: 208</field>
		<title>A Distributed Architecture for Multimedia Conference Control</title>
	</reference>
	<reference name="gre85">
		<names type="author">
			<person>
				<givenname>Irene</givenname>
				<surname>Greif</surname>
			</person>
			<person>
				<givenname>Robert</givenname>
				<surname>Seliger</surname>
			</person>
			<person>
				<givenname>William</givenname>
				<surname>Weihl</surname>
			</person>
		</names>
		<date value="1985-11"/>
		<address>Cambridge, UK</address>
		<field type="bibtex:index">CES</field>
		<publisher type="institution">Massachusetts Institute of Technology</publisher>
		<number>MIT/LCS/TM-295</number>
		<field type="bibtex:src">EW: 60</field>
		<title>Atomic Data Abstractions in a Distributed Collaborative Editing System</title>
	</reference>
	<reference name="koc95a">
		<names type="author">
			<person>
				<givenname>Michael</givenname>
				<surname>Koch</surname>
			</person>
		</names>
		<date value="1995-08"/>
		<address>Munich, Germany</address>
		<field type="bibtex:index">IRIS, groupware, collaborative editing</field>
		<publisher type="institution">Technische Universität München</publisher>
		<number>TUM-I9524</number>
		<field type="bibtex:src">EW: ~/papers/bibtex</field>
		<title>The Collaborative Multi-User Editor Project Iris</title>
	</reference>
	<reference name="hef95">
		<names type="author">
			<person>
				<givenname>Wendy</givenname>
				<surname>Heffner</surname>
			</person>
		</names>
		<date value="1995-05"/>
		<address>Berkeley, California</address>
		<field type="bibtex:copied">13.6.95</field>
		<field type="bibtex:index">Tenet, RCAP2, multicast, target sets, RSVP, ST-II, SCMP</field>
		<publisher type="institution">International Computer Science Institute</publisher>
		<number>TR-95-022</number>
		<field type="bibtex:src">EW: 155</field>
		<title>Scaling Issues in the Design and Implementation of the Tenet RCAP2 Signaling Protocol</title>
	</reference>
	<reference name="ban94">
		<names type="author">
			<person>
				<givenname>Anindo</givenname>
				<surname>Banerjea</surname>
			</person>
			<person>
				<givenname>Domenico</givenname>
				<surname>Ferrari</surname>
			</person>
			<person>
				<givenname>Bruce A.</givenname>
				<surname>Mah</surname>
			</person>
			<person>
				<givenname>Mark</givenname>
				<surname>Moran</surname>
			</person>
			<person>
				<givenname>Dinesh</givenname>
				<surname>Verma</surname>
			</person>
			<person>
				<givenname>Hui</givenname>
				<surname>Zhang</surname>
			</person>
		</names>
		<date value="1994-11"/>
		<address>Berkeley, California</address>
		<field type="bibtex:copied">8.6.95</field>
		<field type="bibtex:index">Tenet, ATM, FDDI, RTIP, RMTP, CMTP</field>
		<publisher type="institution">International Computer Science Institute</publisher>
		<number>TR-94-059</number>
		<field type="bibtex:src">EW: 150</field>
		<title>The Tenet Real-Time Protocol Suite: Design, Implementation, and Experiences</title>
	</reference>
	<reference name="szy93b">
		<names type="author">
			<person>
				<givenname>Clemens</givenname>
				<surname>Szyperski</surname>
			</person>
			<person>
				<givenname>Giorgio</givenname>
				<surname>Ventre</surname>
			</person>
		</names>
		<date value="1993-01"/>
		<address>Berkeley, California</address>
		<field type="bibtex:copied">8.6.95</field>
		<field type="bibtex:index">MIM, CSCW</field>
		<publisher type="institution">International Computer Science Institute</publisher>
		<number>TR-93-006</number>
		<field type="bibtex:src">EW: 153</field>
		<title>A Characterization of Multi-Party Interactive Multimedia Applications</title>
	</reference>
	<reference name="eff93">
		<names type="author">
			<person>
				<givenname>Wolfgang</givenname>
				<surname>Effelsberg</surname>
			</person>
			<person>
				<givenname>Eberhard</givenname>
				<surname>Müller-Menrad</surname>
			</person>
		</names>
		<date value="1993-10"/>
		<address>Berkeley, California</address>
		<field type="bibtex:copied">13.6.95</field>
		<field type="bibtex:index">Tenet, multicast, target sets, routing</field>
		<publisher type="institution">International Computer Science Institute</publisher>
		<number>TR-93-056</number>
		<field type="bibtex:src">EW: 154</field>
		<title>Dynamic Join and Leave for Real-Time Multicast</title>
	</reference>
	<reference name="sam93a">
		<names type="author">
			<person>
				<givenname>Michael</givenname>
				<surname>Sample</surname>
			</person>
		</names>
		<date value="1993-07"/>
		<address>Vancouver, Canada</address>
		<field type="bibtex:index">snacc, ASN.1</field>
		<publisher type="institution">University of British Columbia</publisher>
		<title>Snacc 1.1: A High Performance ASN.1 to C/C++ Compiler</title>
	</reference>
	<reference name="wil05g">
		<names type="author">
			<person>
				<givenname>Erik</givenname>
				<surname>Wilde</surname>
			</person>
			<person>
				<givenname>Hanspeter</givenname>
				<surname>Salvisberg</surname>
			</person>
			<person>
				<givenname>Alexander</givenname>
				<surname>Pina</surname>
			</person>
		</names>
		<date value="2005-08"/>
		<abstract>
			<richtext>
				<p>Das vorliegende Dokument beschreibt Regeln, welche bei der Benutzung von XML und von XML Schemas in eCH Standards zu berücksichtigen sind. Dabei wird das Schwergewicht auf Basismechanismen und Grundsatzüberlegungen gestellt, welche sich die Benutzern von XML Schemas in der Regel stellen.</p>
			</richtext>
		</abstract>
		<address>Berne, Switzerland</address>
		<publisher type="institution">eCH</publisher>
		<number>eCH-0018</number>
		<title>XML Best Practices</title>
		<identifier type="uri">http://dret.net/netdret/publications#wil05g</identifier>
	</reference>
	<reference name="wil05h">
		<names type="author">
			<person>
				<givenname>Erik</givenname>
				<surname>Wilde</surname>
			</person>
		</names>
		<date value="2006"/>
		<abstract>
			<richtext>
				<p>Das vorliegende Dokument beschreibt, in welcher Form XML Namespaces beschrieben werden sollten, so dass die Benutzer von XML-basierten Vokabularen im Rahmen von eCH eine einfache Quelle haben, über die sie Dokumentation zu einem XML Namespace finden können. Ausgehend von einem einfachen XML Schema können zu einer Definition eines XML Vokabulars auf diese Art auf eine einfache Art Beschreibungen zu einem XML Namespace erzeugt werden, aus denen sowohl menschen- als auch maschinenlesbare Information gewonnen werden kann.</p>
			</richtext>
		</abstract>
		<address>Berne, Switzerland</address>
		<publisher type="institution">eCH</publisher>
		<number>eCH-0033</number>
		<title>Beschreibung von XML Namespaces</title>
		<identifier type="uri">http://dret.net/netdret/publications#wil05h</identifier>
	</reference>
	<reference name="wil05i">
		<names type="author">
			<person>
				<givenname>Erik</givenname>
				<surname>Wilde</surname>
			</person>
		</names>
		<date value="2006"/>
		<abstract>
			<richtext>
				<p>Das vorliegende Dokuments behandelt die innere Struktur von XML Schemas, d.h. den Aufbau und den Zusammenhang der sogenannten "XML Schema Komponenten". Dies ist vor allem dann wichtig, wenn das Schema wiederverwendet werden soll, z.B. indem Teile in einem neuen Kontext wiederverwendet werden sollen, oder indem eine neue Version des Schemas definiert werden soll. In beiden Fällen wirkt sich die innere Struktur des Schemas stark darauf aus, wie einfach diese Aufgabe ausgeführt werden kann.</p>
			</richtext>
		</abstract>
		<address>Berne, Switzerland</address>
		<publisher type="institution">eCH</publisher>
		<number>eCH-0035</number>
		<title>Design von XML Schemas</title>
		<identifier type="uri">http://dret.net/netdret/publications#wil05i</identifier>
	</reference>
	<reference name="wil05j">
		<names type="author">
			<person>
				<givenname>Erik</givenname>
				<surname>Wilde</surname>
			</person>
		</names>
		<date value="2006"/>
		<abstract>
			<richtext>
				<p>Im vorliegenden Dokument wird beschrieben, welche Dokumentation für XML Schemas zu erstellen ist, damit die nötigen Grundlagen für die Implementierung einer Schnittstelle für den XML-basierten Datenaustausch vorhanden sind. Ausgangspunkt ist ein Datenmodell des Ausschnitts der Realität, über welchen Informationen ausgetauscht werden sollen. Davon abgeleitet werden für die jeweils interessierenden Transaktionen Datenmodelle für den Datenaustausch (Austauschmodelle). Ein Austauschmodell wiederum dient als Grundlage für eines oder auch verschiedene Schemas (Austauschschemas). Nur wenn die Modelle wohldefiniert und dokumentiert sind, und wenn die Beziehungen zwischen den Modellen (Referenz- und Austauschmodelle) und den Schemas (Austauschmodell und -schemas) wohldefiniert und dokumentiert sind, können unabhängige Implementierer die Schnittstelle korrekt umsetzen.</p>
			</richtext>
		</abstract>
		<address>Berne, Switzerland</address>
		<publisher type="institution">eCH</publisher>
		<number>eCH-0036</number>
		<title>Modellierung für den XML-orientierten Datenaustausch</title>
		<identifier type="uri">http://dret.net/netdret/publications#wil05j</identifier>
	</reference>
	<reference name="wil06a">
		<names type="author">
			<person>
				<givenname>Erik</givenname>
				<surname>Wilde</surname>
			</person>
		</names>
		<date value="2006"/>
		<abstract>
			<richtext>
				<p>Das vorliegende Dokument definiert Hilfskomponenten, die zur Definition von XML Schemas verwendet werden können. Diese Hilfskomponenten können eingesetzt werden, um wiederkehrende Aspekte von Datenmodellen auf existierende und gemeinsame XML Schema Definitionen abzubilden. Auf diese Weise müssen keine neuen XML Schema Komponenten für diese Aspekte eines Datenmodells definiert werden, und durch die Verwendung wiederverwendbarer Komponenten wird es einfacher, ein XML Schema zu verstehen, in dem diese Hilfskomponenten verwendet werden.</p>
			</richtext>
		</abstract>
		<address>Berne, Switzerland</address>
		<publisher type="institution">eCH</publisher>
		<number>eCH-0050</number>
		<title>Hilfskomponenten zur Konstruktion von XML Schemas</title>
		<identifier type="uri">http://dret.net/netdret/publications#wil06a</identifier>
	</reference>
	<reference name="wil07d">
		<names type="author">
			<person>
				<givenname>Erik</givenname>
				<surname>Wilde</surname>
			</person>
			<person>
				<givenname>Felix</givenname>
				<surname>Michel</surname>
			</person>
		</names>
		<date value="2007-02"/>
		<abstract>
			<richtext>
				<p>While the information contained in XML documents can be accessed using numerous standards and technologies, accessing the information in an XML Schema currently is only possible using proprietary technologies. XML is increasingly being used as a typed data format, and therefore it becomes more important to gain access to the type system of an XML document class, which in many cases is an XML Schema. The XML Schema Path Language (SPath) presented in this paper provides access to XML Schema components by extending the well-known XPath language to also include the domain of XML Schemas. Using SPath, XML developers gain better access to XML Schemas and thus can more easily develop software which is type- or schema-oriented.</p>
			</richtext>
		</abstract>
		<address>Berkeley, California</address>
		<publisher type="institution">School of Information, UC Berkeley</publisher>
		<number>UCB iSchool Report 2007-001</number>
		<title>SPath: A Path Language for XML Schema</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-spath"/>; </p>
			</richtext>
		</annotation>
		<identifier type="uri">http://dret.net/netdret/publications#wil07d</identifier>
	</reference>
	<reference name="wil94c">
		<names type="author">
			<person>
				<givenname>Erik</givenname>
				<surname>Wilde</surname>
			</person>
			<person>
				<givenname>Christoph A.</givenname>
				<surname>Burkhardt</surname>
			</person>
		</names>
		<date value="1994-05"/>
		<abstract>
			<richtext>
				<p>This paper presents a general model of a Group Management Service (GMS) which is designed to support collaborative interactions among groups of distributed users using different applications. There are two main benefits of such a service. Firstly, it would be easier to implement new collaborative applications because of the possibility to use an existing service. Secondly, it would be possible for different applications to share collaboration relevant information because of a common database of information about users and groups maintained by the GMS. One important property of the GMS is its flexibility with respect to the information stored. It is possible to store application-independent as well as application-dependent information. Using an object-oriented approach, applications can share the application-independent information (such as a group's members and administrative information) and can also use the GMS to store application-dependent information which can only be interpreted by a closed set of applications (those who know the syntax and semantics of the application-dependent information). The model of the GMS is very simple and consists mainly of two classes of objects, namely user and group. A small set of operations is provided for querying and modifying GMS information. The possibility to store application-dependent information is realized by allowing using application to create derived classes (ie subclasses) of the classes user and group. Thus it is possible for applications using the GMS to implement their own user and group classes without losing the ability to manage these objects with the GMS. Two applications are presented which may use the GMS to manage their users and groups. Both applications use application-specific derived classes of user and group. However, it is still possible for these applications to share the application-independent information of their users and groups.</p>
			</richtext>
		</abstract>
		<address>Zürich, Switzerland</address>
		<publisher type="institution">Computer Engineering and Networks Laboratory, ETH Zürich</publisher>
		<title>Modelling Groups for Group Communications</title>
		<identifier type="uri">http://dret.net/netdret/publications#wil94c</identifier>
	</reference>
	<reference name="wil94b">
		<names type="author">
			<person>
				<givenname>Erik</givenname>
				<surname>Wilde</surname>
			</person>
		</names>
		<date value="1994-02"/>
		<abstract>
			<richtext>
				<p>Today most CSCW systems are built on top of standard operating systems. Only a few frameworks for generic support of CSCW applications exist. These platforms mostly concentrate on the management of workflows and on the layer on top of them, the CSCW applications. Little work is done in exploring the impacts of new networks onto support for CSCW. The project described in this paper focuses on providing CSCW applications with an efficient shared information space. Efficiency in this context means the utilization of network technology which offers much better services than today's networks.</p>
			</richtext>
		</abstract>
		<address>Zürich, Switzerland</address>
		<publisher type="institution">Computer Engineering and Networks Laboratory, ETH Zürich</publisher>
		<title>Supporting CSCW Applications with an Efficient Shared Information Space</title>
		<identifier type="uri">http://dret.net/netdret/publications#wil94b</identifier>
	</reference>
	<reference name="wil92">
		<names type="author">
			<person>
				<givenname>Erik</givenname>
				<surname>Wilde</surname>
			</person>
		</names>
		<date value="1992-05"/>
		<address>Zürich, Switzerland</address>
		<publisher type="institution">Computer Engineering and Networks Laboratory, ETH Zürich</publisher>
		<title>Konzept eines mehrbenutzerfähigen Multimedia-Editors</title>
		<identifier type="uri">http://dret.net/netdret/publications#wil92</identifier>
	</reference>
	<reference name="wil01f">
		<names type="author">
			<person>
				<givenname>Erik</givenname>
				<surname>Wilde</surname>
			</person>
			<person>
				<givenname>Manfred</givenname>
				<surname>Meyer</surname>
			</person>
		</names>
		<date value="2001-12"/>
		<abstract>
			<richtext>
				<p>Asynchronous messaging between cooperating software components proves to be useful in many scenarios. One framework supporting this functionality is Sun's J2EE platform with its Message-Driven Beans (MDB) model. We present a novel way to use MDBs by providing a way to add routing information to the messages, which is then used to send a message through a given path of processing components. We call this model Routed Message-Driven Beans (RMDB), and the two main topics that are important for RMDBs are (1) the message format that is used for the routing information, and (2) the API which can be used by programmers to take advantage of the abstraction provided by RMDBs. Performance measurements show that the overhead caused by our RMDB framework is acceptable if messages are routed through several EJBs.</p>
			</richtext>
		</abstract>
		<address>Zürich, Switzerland</address>
		<publisher type="institution">Computer Engineering and Networks Laboratory, ETH Zürich</publisher>
		<number>TIK Report No. 102</number>
		<title>Routed Message Driven Beans: A new Abstraction for using EJBs</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-ejb" weight="0.8"/>; </p>
			</richtext>
		</annotation>
		<identifier type="uri">http://dret.net/netdret/publications#wil01f</identifier>
	</reference>
	<reference name="wil02b">
		<names type="author">
			<person>
				<givenname>Erik</givenname>
				<surname>Wilde</surname>
			</person>
		</names>
		<date value="2002-01"/>
		<abstract>
			<richtext>
				<p>Web technologies today go far beyond simply enabling the creation of Web pages. XML and metadata formats based on it make it possible to manage metadata in a powerful and flexible way. In this paper, we describe the concept and the prototype of an application for the management of metadata for a specific domain, metadata associated with pictures. The goal of the paper is to highlight the benefits which result from employing Web technologies instead of proprietary data formats. While we think that both application developers as well as users could benefit from such an approach, we are aware that in many real-world cases other issues (such as the ability to bind users to a certain product) also play an important role. Nevertheless, in this paper we show that open and well-documented technologies not only can make software development easier, but also open up synergies between standards-compliant products. While the prototype we present in this paper is not sophisticated enough to be released to the general public, we hope that software vendors will consider incorporating some of the concepts introduced in this paper.</p>
			</richtext>
		</abstract>
		<address>Zürich, Switzerland</address>
		<publisher type="institution">Computer Engineering and Networks Laboratory, ETH Zürich</publisher>
		<number>TIK Report No. 124</number>
		<title>Picture Metadata and its Associations: Using Web Technologies for Representing Semantics</title>
		<identifier type="uri">http://dret.net/netdret/publications#wil02b</identifier>
	</reference>
	<reference name="obe02">
		<names type="author">
			<person>
				<givenname>Glenn</givenname>
				<surname>Oberholzer</surname>
			</person>
			<person>
				<givenname>Erik</givenname>
				<surname>Wilde</surname>
			</person>
		</names>
		<date value="2002-01"/>
		<abstract>
			<richtext>
				<p>The World Wide Web is by far the most successful hypermedia system, its name often being used synonymously for the Internet. However, it is based on a rather restricted hypermedia model with limited linking functionality. Even though underlying systems may provide a richer data model, there is still the question of how to present this information in a Web-based interface in an easily understandable way. Assuming an underlying system similar to Topic Maps, which allows storing, managing, and categorizing meta data and links, we propose a presentation of extended links. We try to provide a usable way for users to handle the additional functionality. The mechanism is based on already available technologies like DHTML. It is one facet of our approach to make the Web more interconnected and to work towards a more richly and openly linked Web.</p>
			</richtext>
		</abstract>
		<address>Zürich, Switzerland</address>
		<publisher type="institution">Computer Engineering and Networks Laboratory, ETH Zürich</publisher>
		<number>TIK Report No. 125</number>
		<title>Extended Link Visualization with DHTML: The Web as an Open Hypermedia System</title>
		<identifier type="uri">http://dret.net/netdret/publications#obe02</identifier>
	</reference>
	<reference name="wil02d">
		<names type="author">
			<person>
				<givenname>Erik</givenname>
				<surname>Wilde</surname>
			</person>
			<person>
				<givenname>Christian</givenname>
				<surname>Stillhard</surname>
			</person>
		</names>
		<date value="2002-01"/>
		<abstract>
			<richtext>
				<p>In this paper, we investigate the requirements for linkbase access on the Web. The recent advancements of Web technologies (XML, XLink, and XPointer) have brought us one step closer to the vision of using the Web as an Open Hypermedia System (OHS). However, some of the pieces to make this work are still missing, and this paper discusses which they are and the status of the current work in these areas. Concentrating on one of these pieces, the access to linkbases, the paper than continues by describing the prerequisites and requirements of such an access mechanism, and closes with a list of requirements and design principles that we will use in a next step to specify and implement a linkbase access protocol.</p>
			</richtext>
		</abstract>
		<address>Zürich, Switzerland</address>
		<publisher type="institution">Computer Engineering and Networks Laboratory, ETH Zürich</publisher>
		<number>TIK Report No. 134</number>
		<title>Openly Accessing Linkbases</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-xlink" weight="0.9"/>; </p>
			</richtext>
		</annotation>
		<identifier type="uri">http://dret.net/netdret/publications#wil01d</identifier>
	</reference>
	<reference name="wil02c">
		<names type="author">
			<person>
				<givenname>Erik</givenname>
				<surname>Wilde</surname>
			</person>
		</names>
		<date value="2002-07"/>
		<abstract>
			<richtext>
				<p>We propose the Open Web, which aims at transforming the Web into an Open Hypermedia System. Based on the Extensible Linking Language (XLink), we investigate the possibilities for implementing linkbase access methods. Linkbases are collections of so-called third-party links, which are links which live outside the resources that they are linking, and thus must be found and retrieved somehow when presenting the resources that they are linking. We focus on the protocol issues of accessing linkbases, concentrating on how such a new protocol could and should be designed. In addition to our design goal of specifying a protocol for accessing the linkbase Web service, be believe that our protocol considerations can serve as a blueprint for other areas where Web access to services is required.</p>
			</richtext>
		</abstract>
		<address>Zürich, Switzerland</address>
		<publisher type="institution">Computer Engineering and Networks Laboratory, ETH Zürich</publisher>
		<number>TIK Report No. 143</number>
		<title>Protocol Considerations for Web Linkbase Access</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-xlink" weight="0.9"/>; </p>
			</richtext>
		</annotation>
		<identifier type="uri">http://dret.net/netdret/publications#wil02c</identifier>
	</reference>
	<reference name="wil02i">
		<names type="author">
			<person>
				<givenname>Erik</givenname>
				<surname>Wilde</surname>
			</person>
		</names>
		<date value="2002-08"/>
		<abstract>
			<richtext>
				<p>This report describes a proposal for a data model for XLink. It defines the data model as contributions of XLink to the XML Infoset. The data model is meant as a clarification of the link model implicitly defined by XLink. It is also meant as the foundation for future work on XLink, for example a DOM module for XLink support, a CSS module for styling XLinks, or a protocol for accessing XLink linkbases.</p>
			</richtext>
		</abstract>
		<address>Zürich, Switzerland</address>
		<publisher type="institution">Computer Engineering and Networks Laboratory, ETH Zürich</publisher>
		<number>TIK Report No. 148</number>
		<title>A Proposal for XLink Infoset Contributions</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-xlink" weight="0.9"/>; </p>
			</richtext>
		</annotation>
		<identifier type="uri">http://dret.net/netdret/publications#wil02i</identifier>
	</reference>
	<reference name="wil03c">
		<names type="author">
			<person>
				<givenname>Erik</givenname>
				<surname>Wilde</surname>
			</person>
		</names>
		<date value="2003-02"/>
		<abstract>
			<richtext>
				<p>XML and its data model, the XML Information Set, are used for a large number of applications. These applications have widely varying data models, ranging from very simple regular trees to irregularly structured graphs using many different types of nodes and vertices. While some applications are sufficiently supported by the data model provided by the XML Infoset itself, others could benefit from extensions of the data model and assistance for these extensions in supporting XML technologies (such as the DOM API or the XSLT programming language). In this paper, we describe the Extensible XML Information Set (EXIS), which is a reformulation of the XML Infoset targeted at making the Infoset easier to extend and to make these extensions usable in higher-level XML technologies. EXIS provides a framework for defining extensions to the core XML Infoset, and for identifying these extensions (using namespace names). Higher-level XML technologies (such as DOM or XPath) can then support EXIS extensions through additional interfaces, such as a dedicated DOM module, or XPath extension mechanisms (extension axes and/or functions). In order to make EXIS work, additional efforts are required in these areas of higher-level XML technologies, but EXIS itself could be used rather quickly to provide a foundation for well-defined Infoset extensions, such as XML Schema's PSVI contributions, or the reformulation of XLink as being based on a data model (rather than a syntax).</p>
			</richtext>
		</abstract>
		<address>Zürich, Switzerland</address>
		<publisher type="institution">Computer Engineering and Networks Laboratory, ETH Zürich</publisher>
		<number>TIK Report No. 160</number>
		<title>The Extensible XML Information Set</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-exis"/>; <keywordref type="topic-xmlinfoset" weight="0.8"/>; </p>
			</richtext>
		</annotation>
		<identifier type="uri">http://dret.net/netdret/publications#wil03c</identifier>
	</reference>
	<reference name="mic06a">
		<names type="author">
			<person>
				<givenname>Felix</givenname>
				<surname>Michel</surname>
			</person>
		</names>
		<date value="2006-11"/>
		<abstract>
			<richtext>
				<p>XML Schema is a very expressive grammar-based schema language that additionally supports advanced data modeling techniques, namely through its type concept, and allows for describing relationships between structural elements in an expressive and semantically meaningful way. Upcoming type-aware XML technologies like XSLT 2.0, XQuery, and XPath 2.0 increasingly strive to use this structural information, but its retrieval is difficult and only partially possible. Both a unified data model for XML Schema and a set of accessor functions are necessary for enabling new technologies to utilize XML Schema's full capabilities. We will present a function library relying on an XML-based representation of XML Schema's data model and demonstrate how this substantially enhances XPath 2.0 and XSLT 2.0 and how this proves highly beneficial to applications.</p>
			</richtext>
		</abstract>
		<address>Zürich, Switzerland</address>
		<publisher type="institution">Computer Engineering and Networks Laboratory, ETH Zürich</publisher>
		<number>TIK Report No. 264</number>
		<title>Opening XML Schema's Data Model to XPath 2.0</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-spath" weight="0.8"/>; <keywordref type="topic-scx" weight="0.9"/>; </p>
			</richtext>
		</annotation>
		<identifier type="uri" resourceType="application/pdf">ftp://ftp.tik.ee.ethz.ch/pub/publications/TIK-Report-264.pdf</identifier>
	</reference>
	<reference name="mic06b">
		<names type="author">
			<person>
				<givenname>Felix</givenname>
				<surname>Michel</surname>
			</person>
			<person>
				<givenname>Erik</givenname>
				<surname>Wilde</surname>
			</person>
		</names>
		<date value="2006-12"/>
		<abstract>
			<richtext>
				<p>XML Schema is a complex language for defining schemas for classes of XML documents, and its inherent complexity as well as its XML transfer syntax make it hard to read XML Schemas for humans. This is a problem, because in many cases XML Schemas are not only used  for validation purposes, but also as the data model for classes of XML  documents, which must be understood by developers working with these  documents. This report looks at various visualizations of XML Schemas  in existing software tools and compares them in terms of how well they  are suited to represent the data model behind the XML Schema syntax.  of today, no available tool provides a level of abstraction that  would be appropriate for a data model perspective; most of them are visualizations of the syntax rather than the model. The tools included in this report are the Eclipse XML editors, XML Spy, oXygen, Turbo XML, and Stylus Studio. This report is not a complete evaluation of these tools, it only looks at them in terms of their schema visualization and their support of a less syntax-centered view of XML Schema.</p>
			</richtext>
		</abstract>
		<address>Zürich, Switzerland</address>
		<publisher type="institution">Computer Engineering and Networks Laboratory, ETH Zürich</publisher>
		<number>TIK Report No. 265</number>
		<title>Visualization of XML Schemas</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-xmlschema" weight="0.8"/>; </p>
			</richtext>
		</annotation>
		<identifier type="uri">http://dret.net/netdret/publications#mic06b</identifier>
	</reference>
	<reference name="wil06m">
		<names type="author">
			<person>
				<givenname>Erik</givenname>
				<surname>Wilde</surname>
			</person>
		</names>
		<date value="2006-07"/>
		<abstract>
			<richtext>
				<p>XML and Service-Oriented Architectures (SOA) make it easier to develop loosely coupled systems, but they do not eliminate the fundamental necessity of communications that there must be an underlying shared model. Because of the popularity of SOA, it becomes increasingly important to be able to quickly and efficiently integrate information systems, rather than using an expensive top-down process. The XML landscape evolved bottom-up, and so far it has not yet reached a stage where XML is explicitly targeted in conceptual models. Filling this gap with guidelines and best practices thus is the most pragmatic approach. The approach presented in this paper is a structured view accompanied by guidelines for how interoperability can be achieved on the model level today.</p>
			</richtext>
		</abstract>
		<address>Zürich, Switzerland</address>
		<publisher type="institution">Computer Engineering and Networks Laboratory, ETH Zürich</publisher>
		<number>TIK Report No. 257</number>
		<title>Model Mapping in XML-Oriented Environments</title>
		<identifier type="uri">http://dret.net/netdret/publications#wil06m</identifier>
	</reference>
	<reference name="wil06f">
		<names type="author">
			<person>
				<givenname>Erik</givenname>
				<surname>Wilde</surname>
			</person>
		</names>
		<date value="2006-03"/>
		<abstract>
			<richtext>
				<p>Information today is often distributed among many different system within a complex IT environment. Using this information for creating knowledge organization systems and services thus involves using this distributed information and re-purposing it within new applications. The current trend in Web technologies to build systems not in a monolithic fashion, but rather intended as building blocks within a constantly evolving and unplanned landscape of information processing agents. This approach can be used as a foundation for building Knowledge Organization Mashups. We investigate the possibilities and challenges of this type of application, and as a case study describe a service for managing bibliographic metadata.</p>
			</richtext>
		</abstract>
		<address>Zürich, Switzerland</address>
		<publisher type="institution">Computer Engineering and Networks Laboratory, ETH Zürich</publisher>
		<number>TIK Report No. 245</number>
		<title>Knowledge Organization Mashups</title>
		<identifier type="uri">http://dret.net/netdret/publications#wil06f</identifier>
	</reference>
	<reference name="wil06d">
		<names type="author">
			<person>
				<givenname>Arijit</givenname>
				<surname>Sengupta</surname>
			</person>
			<person>
				<givenname>Erik</givenname>
				<surname>Wilde</surname>
			</person>
		</names>
		<date value="2006-02"/>
		<abstract>
			<richtext>
				<p>Because of its success, XML is increasingly used in many different application areas, and is moving towards the center of applications, evolving from an exchange format to the native data format of application components. These developments suggest that similar to other core areas of application design, XML should be designed conceptually before the implementation tasks of designing markup and writing schemas are approached. In this paper, we describe why conceptual modeling will become an important part of the XML landscape, what issues need to be addressed, and what the requirements for a conceptual modeling language for XML are.</p>
			</richtext>
		</abstract>
		<address>Zürich, Switzerland</address>
		<publisher type="institution">Computer Engineering and Networks Laboratory, ETH Zürich</publisher>
		<number>TIK Report No. 244</number>
		<title>The Case for Conceptual Modeling for XML</title>
		<identifier type="uri">http://dret.net/netdret/publications#wil06d</identifier>
	</reference>
	<reference name="wil06c">
		<names type="author">
			<person>
				<givenname>Erik</givenname>
				<surname>Wilde</surname>
			</person>
		</names>
		<date value="2006-02"/>
		<abstract>
			<richtext>
				<p>XML has become an important standard for exchanging structured data between applications, but XML increasingly penetrates applications and is thus also becoming an important part of application development. The current state of XML specifications and technologies provides support in many aspects of application development, while other aspects are still only poorly supported. We describe as an example the development of an XML-centric application and identify and describe the areas where today's support for application developers could and should be improved. This case study thus can help developers to focus on the problem areas of today's support for XML-centric application development, and may also serve as an agenda for areas where more research and tools are required to improve the development of XML-centric applications.</p>
			</richtext>
		</abstract>
		<address>Zürich, Switzerland</address>
		<publisher type="institution">Computer Engineering and Networks Laboratory, ETH Zürich</publisher>
		<number>TIK Report No. 242</number>
		<title>XML-Centric Application Development</title>
		<identifier type="uri">http://dret.net/netdret/publications#wil06c</identifier>
	</reference>
	<reference name="wil05o">
		<names type="author">
			<person>
				<givenname>Erik</givenname>
				<surname>Wilde</surname>
			</person>
		</names>
		<date value="2005-05"/>
		<abstract>
			<richtext>
				<p>The creation, management and dissemination of bibliographic information is a common task for almost all people working in a research environment, and it also is a (often weak) way of knowledge management. Current tools and methods are either centered on the process of document preparation using bibliographic references, or on the aspect of creating annotations and/or relationships describing bibliographic resources. As a result, bibliography management in many cases is still carried out with fairly simple tools and methods, and with little or no support for sharing the information. In the ShaRef project, the areas of document preparation, knowledge management, and information sharing among workgroup members are treated as equally important. As a result, ShaRef enables users to create, manage, and disseminate bibliographic information in a wide variety of use cases.</p>
			</richtext>
		</abstract>
		<address>Zürich, Switzerland</address>
		<publisher type="institution">Computer Engineering and Networks Laboratory, ETH Zürich</publisher>
		<number>TIK Report No. 224</number>
		<title>Shared Bibliographies as Hypertext</title>
		<identifier type="uri">http://dret.net/netdret/publications#wil05o</identifier>
	</reference>
	<reference name="wil05k">
		<names type="author">
			<person>
				<givenname>Erik</givenname>
				<surname>Wilde</surname>
			</person>
			<person>
				<givenname>Sai</givenname>
				<surname>Anand</surname>
			</person>
			<person>
				<givenname>Petra</givenname>
				<surname>Zimmermann</surname>
			</person>
		</names>
		<date value="2005-02"/>
		<abstract>
			<richtext>
				<p>In this paper, we describe a real-life application which has been designed around an XML data model and various XML technologies. We describe the rationale behind this design, and the benefits from the information system design point of view. We believe that XML-centric design has a lot of benefits, and that future developments in the area of XML technologies will better support this design style and help to make it even more advantageous. XML-centric design allows to leverage an ever-increasing number of XML-based technologies. We describe some of the XML technologies that helped us implementing some of the core parts of the software, and point out some others that we do not yet use, but are actively investigating for possible future developments.</p>
			</richtext>
		</abstract>
		<address>Zürich, Switzerland</address>
		<publisher type="institution">Computer Engineering and Networks Laboratory, ETH Zürich</publisher>
		<number>TIK Report No. 213</number>
		<title>ShaRef: XML-Centric Software Design</title>
		<identifier type="uri">http://dret.net/netdret/publications#wil05k</identifier>
	</reference>
	<reference name="wil05e">
		<names type="author">
			<person>
				<givenname>Erik</givenname>
				<surname>Wilde</surname>
			</person>
			<person>
				<givenname>Willy</givenname>
				<surname>Müller</surname>
			</person>
		</names>
		<date value="2005-02"/>
		<abstract>
			<richtext>
				<p>In this paper we present an approach to organize e-government schemas in Switzerland. On the political side, Switzerland is a challenging environment for any federation-wide harmonization and cooperation, because many authorities are organized independently. On the technical side, we describe an approach which aims at increasing the federation-wide cooperation through providing interested parties with a low barrier-to-entry, and with clearly visible benefits through the continuous evolution of a directory of e-government schemas. This paper describes a light-weight Semantic Web approach, enabling schema authors to create namespace descriptions that provide a minimal semantic description of the namespace's subject. Using these namespace descriptions, RDF data is extracted and serves as source for a highly interlinked directory of e-government schemas in Switzerland.</p>
			</richtext>
		</abstract>
		<address>Zürich, Switzerland</address>
		<publisher type="institution">Computer Engineering and Networks Laboratory, ETH Zürich</publisher>
		<number>TIK Report No. 212</number>
		<title>Organizing Federal E-Government Schemas</title>
		<identifier type="uri">http://dret.net/netdret/publications#wil05e</identifier>
	</reference>
	<reference name="wil04h">
		<names type="author">
			<person>
				<givenname>Erik</givenname>
				<surname>Wilde</surname>
			</person>
		</names>
		<date value="2004-06"/>
		<abstract>
			<richtext>
				<p>Collections of references are an important part of scientific and scholarly work. For many people, collections of references are the most advanced form of formal knowledge representation they are using. However, today's standards and tools for collections of references are pretty poor, providing closed environments with no or little extension mechanisms. In this paper, we describe our goal to design and implement an advanced system for collections of references. The primary goal of this system is to provide users with a tool that matches their requirements of semantic richness vs. usability, which are competing goals. As a first step towards this goal, we designed and conducted a survey among the employees of a large university, trying to find out how people are managing their references today, and what their expectations are if a new tool became available. The results of the survey are presented, followed by conclusions that are the guiding principles for the upcoming ShaRef project. The goal of this project is to design and implement a system for reference management that runs Web-based as well as stand-alone, is easy to use, supports collaborative collections of references and collection sharing, has an open and extensible data model, covers the majority of user requirements according to the 80/20 principle, and thus provides scientists and scholars with a better way to manage their collections of references.</p>
			</richtext>
		</abstract>
		<address>Zürich, Switzerland</address>
		<publisher type="institution">Computer Engineering and Networks Laboratory, ETH Zürich</publisher>
		<number>TIK Report No. 194</number>
		<title>Usage and Management of Collections of References</title>
		<identifier type="uri">http://dret.net/netdret/publications#wil04h</identifier>
	</reference>
	<reference name="wil04f">
		<names type="author">
			<person>
				<givenname>Erik</givenname>
				<surname>Wilde</surname>
			</person>
			<person>
				<givenname>Andreas</givenname>
				<surname>Steiner</surname>
			</person>
		</names>
		<date value="2004-02"/>
		<abstract>
			<richtext>
				<p>E-commerce technologies have reached a level of maturity where many businesses are no longer hampered by technological limitations. However, the adoption of e-commerce technologies is slower than anticipated. We argue one of the limitations is a psychological barrier, which is created by the perception that e-commerce technologies are a whole new set of technologies which are completely different from computer networking. By applying metaphors from basic networking technologies (such as bridges and routers), we try to (1) demonstrate that e-commerce technologies are — in many ways — comparable to computer networking, and (2) show that convincing businesses to adopt e-commerce technologies could be made easier by showing them that e-commerce is basically computer networking taken to another level. We also believe that using these metaphors will make it easier to talk about e-commerce technologies, to reuse existing knowledge about networking architectures on this new level, and to identify the areas where additional work needs to be done.</p>
			</richtext>
		</abstract>
		<address>Zürich, Switzerland</address>
		<publisher type="institution">Computer Engineering and Networks Laboratory, ETH Zürich</publisher>
		<number>TIK Report No. 190</number>
		<title>Networking Metaphors for E-Commerce</title>
		<identifier type="uri">http://dret.net/netdret/publications#wil04f</identifier>
	</reference>
	<reference name="wil03i">
		<names type="author">
			<person>
				<givenname>Erik</givenname>
				<surname>Wilde</surname>
			</person>
		</names>
		<date value="2003-06"/>
		<address>Zürich, Switzerland</address>
		<publisher type="institution">Computer Engineering and Networks Laboratory, ETH Zürich</publisher>
		<number>TIK Report No. 172</number>
		<title>Character Repertoire Validation for XML (CRVX) Version 1.0</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-crvx"/>; </p>
			</richtext>
		</annotation>
		<identifier type="uri">http://dret.net/netdret/publications#wil03i</identifier>
	</reference>
	<reference name="wil03n">
		<names type="author">
			<person>
				<givenname>Erik</givenname>
				<surname>Wilde</surname>
			</person>
		</names>
		<date value="2003-08"/>
		<address>Santa Clara, California</address>
		<title>Position Paper for the W3C Workshop on Binary Interchange of XML Information Item Sets</title>
		<identifier type="uri">http://dret.net/netdret/publications#wil03n</identifier>
	</reference>
	<reference name="sti03b">
		<names type="author">
			<person>
				<givenname>Kilian</givenname>
				<surname>Stillhard</surname>
			</person>
			<person>
				<givenname>Erik</givenname>
				<surname>Wilde</surname>
			</person>
		</names>
		<date value="2003-03"/>
		<abstract>
			<richtext>
				<p>XML Schema is a schema language for XML, providing advanced features for creating types, deriving types, and a library of built-in simple datatypes. The model behind XML Schema are XML Schema components, and XML Schema uses XML syntax for representing XML Schema components. In this report, we present an alternative syntax for XML Schema, which is defined using EBNF productions. Since the new syntax has been designed with the design goals of readability and compactness, it is called XML Schema Compact Syntax (XSCS). XSCS has been created for making XML Schema easier to read and write by humans, while XML Schema's XML syntax is better suited for automated processing of XML Schemas. Consequently, XSCS is not meant as a replacement of the XML syntax, but as a complementary syntax.</p>
			</richtext>
		</abstract>
		<address>Zürich, Switzerland</address>
		<publisher type="institution">Computer Engineering and Networks Laboratory, ETH Zürich</publisher>
		<number>TIK Report No. 166</number>
		<title>XML Schema Compact Syntax (XSCS) Version 1.0</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-xscs"/>; </p>
			</richtext>
		</annotation>
		<identifier type="uri">http://dret.net/netdret/publications#sti03b</identifier>
	</reference>
	<reference name="wil96a">
		<names type="author">
			<person>
				<givenname>Erik</givenname>
				<surname>Wilde</surname>
			</person>
		</names>
		<date value="1996-03"/>
		<abstract>
			<richtext>
				<p>Group communications require special support for name and address management, QoS support, and connection establishment. The group and session management system (GMS) is a distributed directory system which is specifically designed to support group communication infrastructures. This report briefly introduces the concepts of GMS, the data types available, and then gives a specification of GAP, the GMS access protocol. GAP is specified by state diagrams describing the behavior of two communication entities, the PDU syntax in ASN.1, and the PDU semantics in comments given for each PDU.</p>
			</richtext>
		</abstract>
		<address>Zürich, Switzerland</address>
		<field type="bibtex:index">GMS, GAP, ASN.1</field>
		<publisher type="institution">Computer Engineering and Networks Laboratory, ETH Zürich</publisher>
		<number>TIK Report No. 15</number>
		<title>Specification of GMS Access Protocol (GAP) Version 1.0</title>
		<identifier type="uri">http://dret.net/netdret/publications#wil96a</identifier>
	</reference>
	<reference name="wil96c">
		<names type="author">
			<person>
				<givenname>Erik</givenname>
				<surname>Wilde</surname>
			</person>
		</names>
		<date value="1996-09"/>
		<abstract>
			<richtext>
				<p>Group communications require special support for name and address management, QoS support, and connection establishment. The group and session management system (GMS) is a distributed directory system which is specifically designed to support group communication infrastructures. This report briefly introduces the concepts of GMS, the data types available, and then gives the specification of GSP, the GMS system protocol. This protocol is used for communication between GSAs, ie it is used for GMS's internal communication. GSP is specified by state diagrams, time sequence diagrams, textual descriptions, the PDU syntax in ASN.1, and the PDU semantics in comments given for each PDU.</p>
			</richtext>
		</abstract>
		<address>Zürich, Switzerland</address>
		<field type="bibtex:index">GMS, GSP, ASN.1</field>
		<publisher type="institution">Computer Engineering and Networks Laboratory, ETH Zürich</publisher>
		<number>TIK Report No. 19</number>
		<title>Specification of GMS System Protocol (GSP) Version 1.0</title>
		<identifier type="uri">http://dret.net/netdret/publications#wil96c</identifier>
	</reference>
	<reference name="wil94a">
		<names type="author">
			<person>
				<givenname>Erik</givenname>
				<surname>Wilde</surname>
			</person>
		</names>
		<date value="1994-02"/>
		<abstract>
			<richtext>
				<p>Multi-user multimedia editing ought to be supported by different means. Besides technical means required for editing a given document by several users simultaneously, there is also a demand for communication mechanisms which are able to support the synchronization of the users. The system presented in this paper does not only offer multi-user multimedia editing capabilities but also provides a shared workspace and an environment for communication both via terminals and via telephone. The shared workspace is a concept which allows the members of a conference to share documents and other data. Telephone communications enable members of a collaborative editing session to have conference connections and to dynamically form subgroups.</p>
			</richtext>
		</abstract>
		<address>Zürich, Switzerland</address>
		<field type="bibtex:index">MultimETH, groupware, collaborative editing</field>
		<publisher type="institution">Computer Engineering and Networks Laboratory, ETH Zürich</publisher>
		<number>TIK Report No. 18</number>
		<title>Multi-User Multimedia Editing with the MultimETH System</title>
		<identifier type="uri">http://dret.net/netdret/publications#wil94a</identifier>
	</reference>
	<reference name="lub93a">
		<names type="author">
			<person>
				<givenname>Hannes P.</givenname>
				<surname>Lubich</surname>
			</person>
			<person>
				<givenname>Christoph A.</givenname>
				<surname>Burkhardt</surname>
			</person>
			<person>
				<givenname>Erik</givenname>
				<surname>Wilde</surname>
			</person>
		</names>
		<date value="1993-09"/>
		<address>Zürich, Switzerland</address>
		<field type="bibtex:index">MultimETH</field>
		<publisher type="institution">Computer Engineering and Networks Laboratory, ETH Zürich</publisher>
		<title>Schlussbericht zum ZBF-Projekt 224Z (MultimETH): Bericht</title>
		<identifier type="uri">http://dret.net/netdret/publications#lub93a</identifier>
	</reference>
	<reference name="lub93b">
		<names type="author">
			<person>
				<givenname>Hannes P.</givenname>
				<surname>Lubich</surname>
			</person>
			<person>
				<givenname>Christoph A.</givenname>
				<surname>Burkhardt</surname>
			</person>
			<person>
				<givenname>Erik</givenname>
				<surname>Wilde</surname>
			</person>
		</names>
		<date value="1993-09"/>
		<address>Zürich, Switzerland</address>
		<field type="bibtex:index">MultimETH</field>
		<publisher type="institution">Computer Engineering and Networks Laboratory, ETH Zürich</publisher>
		<title>Schlussbericht zum ZBF-Projekt 224Z (MultimETH): Benutzerhandbuch</title>
		<identifier type="uri">http://dret.net/netdret/publications#lub93b</identifier>
	</reference>
	<reference name="lub93c">
		<names type="author">
			<person>
				<givenname>Hannes P.</givenname>
				<surname>Lubich</surname>
			</person>
			<person>
				<givenname>Christoph A.</givenname>
				<surname>Burkhardt</surname>
			</person>
			<person>
				<givenname>Erik</givenname>
				<surname>Wilde</surname>
			</person>
		</names>
		<date value="1993-09"/>
		<address>Zürich, Switzerland</address>
		<field type="bibtex:index">MultimETH</field>
		<publisher type="institution">Computer Engineering and Networks Laboratory, ETH Zürich</publisher>
		<title>Schlussbericht zum ZBF-Projekt 224Z (MultimETH): Implementationsbeschreibung</title>
		<identifier type="uri">http://dret.net/netdret/publications#lub93c</identifier>
	</reference>
	<reference name="hen94b">
		<names type="author">
			<person>
				<givenname>Lutz</givenname>
				<surname>Henckel</surname>
			</person>
		</names>
		<date value="1994-06"/>
		<address>Berlin, Germany</address>
		<field type="bibtex:index">CIO</field>
		<publisher type="institution">GMD FOKUS</publisher>
		<field type="bibtex:src">EW: ~/papers/bibtex</field>
		<title>Multipeer Connection-mode Transport Service Definition based on the Group Communication Framework</title>
	</reference>
	<reference name="mat93">
		<names type="author">
			<person>
				<givenname>Laurent</givenname>
				<surname>Mathy</surname>
			</person>
			<person>
				<givenname>Guy</givenname>
				<surname>Leduc</surname>
			</person>
			<person>
				<givenname>Olivier</givenname>
				<surname>Bonaventure</surname>
			</person>
			<person>
				<givenname>André</givenname>
				<surname>Danthine</surname>
			</person>
		</names>
		<date value="1993-12"/>
		<address>Liège, Belgium</address>
		<field type="bibtex:index">CIO</field>
		<publisher type="institution">Faculteé des Sciences Appliquées, Université de Liège</publisher>
		<number>R2060/ULg/CIO/IN/P/005</number>
		<field type="bibtex:src">EW: 187, EW: ~/papers/bibtex</field>
		<title>A Group Communication Framework</title>
	</reference>
	<reference name="mat94c">
		<names type="author">
			<person>
				<givenname>Laurent</givenname>
				<surname>Mathy</surname>
			</person>
			<person>
				<givenname>Guy</givenname>
				<surname>Leduc</surname>
			</person>
			<person>
				<givenname>Olivier</givenname>
				<surname>Bonaventure</surname>
			</person>
			<person>
				<givenname>André</givenname>
				<surname>Danthine</surname>
			</person>
		</names>
		<date value="1994-01"/>
		<address>Liège, Belgium</address>
		<field type="bibtex:index">CIO</field>
		<publisher type="institution">Faculteé des Sciences Appliquées, Université de Liège</publisher>
		<number>R2060/ULg/CIO/IN/P/007</number>
		<field type="bibtex:src">EW: ~/papers/bibtex</field>
		<title>The CIO Multipeer Broadband Transport Service and the Group Communication Framework</title>
	</reference>
	<reference name="mat94d">
		<names type="author">
			<person>
				<givenname>Laurent</givenname>
				<surname>Mathy</surname>
			</person>
			<person>
				<givenname>Guy</givenname>
				<surname>Leduc</surname>
			</person>
			<person>
				<givenname>Olivier</givenname>
				<surname>Bonaventure</surname>
			</person>
			<person>
				<givenname>André</givenname>
				<surname>Danthine</surname>
			</person>
		</names>
		<date value="1994-01"/>
		<address>Liège, Belgium</address>
		<field type="bibtex:index">CIO</field>
		<publisher type="institution">Faculteé des Sciences Appliquées, Université de Liège</publisher>
		<number>R2060/ULg/CIO/IN/P/008</number>
		<field type="bibtex:src">EW: ~/papers/bibtex</field>
		<title>The Multipeer Data Transmission Transport Service and the Group Communication Framework</title>
	</reference>
	<reference name="mat94e">
		<names type="author">
			<person>
				<givenname>Laurent</givenname>
				<surname>Mathy</surname>
			</person>
			<person>
				<givenname>Guy</givenname>
				<surname>Leduc</surname>
			</person>
			<person>
				<givenname>Olivier</givenname>
				<surname>Bonaventure</surname>
			</person>
			<person>
				<givenname>André</givenname>
				<surname>Danthine</surname>
			</person>
		</names>
		<date value="1994-01"/>
		<address>Liège, Belgium</address>
		<field type="bibtex:index">CIO, ETS</field>
		<publisher type="institution">Faculteé des Sciences Appliquées, Université de Liège</publisher>
		<number>R2060/ULg/CIO/IN/P/009</number>
		<field type="bibtex:src">EW: ~/papers/bibtex</field>
		<title>The Enhanced Transport Service and the Group Communication Framework</title>
	</reference>
	<reference name="atm96">
		<names type="author">
			<name>ATM Forum</name>
		</names>
		<date value="1996-07"/>
		<field type="bibtex:index">ATM, UNI 4.0</field>
		<publisher type="institution">ATM Forum</publisher>
		<annotation type="bibtex:note">
			<richtext>
				<p>Preliminary draft</p>
			</richtext>
		</annotation>
		<title>ATM User-Network Interface (UNI) Specification Version 4.0</title>
	</reference>
	<reference name="atm96b">
		<names type="author">
			<name>ATM Forum</name>
		</names>
		<date value="1996-04"/>
		<field type="bibtex:index">ATM</field>
		<publisher type="institution">ATM Forum</publisher>
		<title>Traffic Management Specification, Version 4.0</title>
	</reference>
	<reference name="bat91">
		<names type="author">
			<person>
				<givenname>Carlo</givenname>
				<surname>Batini</surname>
			</person>
			<person>
				<givenname>Stefano</givenname>
				<surname>Ceri</surname>
			</person>
			<person>
				<givenname>Shamkant B.</givenname>
				<surname>Navathe</surname>
			</person>
		</names>
		<date value="1991-08"/>
		<address>Reading, Massachusetts</address>
		<identifier type="isbn">0805302441</identifier>
		<publisher>Addison Wesley</publisher>
		<title>Conceptual Database Design: An Entity-Relationship Approach</title>
		<identifier type="uri">http://www.awprofessional.com/bookstore/product.asp?isbn=0805302441&amp;rl=1</identifier>
	</reference>
	<reference name="leu01">
		<names type="author">
			<person>
				<givenname>Bo</givenname>
				<surname>Leuf</surname>
			</person>
			<person>
				<givenname>Ward</givenname>
				<surname>Cunningham</surname>
			</person>
		</names>
		<date value="2001-04"/>
		<address>Reading, Massachusetts</address>
		<identifier type="isbn">020171499X</identifier>
		<publisher>Addison Wesley</publisher>
		<title>The Wiki Way: Collaboration and Sharing on the Internet</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-wiki"/>; </p>
			</richtext>
		</annotation>
		<identifier type="uri">http://www.awprofessional.com/title/020171499X</identifier>
	</reference>
	<reference name="edn03">
		<names type="author">
			<person>
				<givenname>John</givenname>
				<surname>Edney</surname>
			</person>
			<person>
				<givenname>William A.</givenname>
				<surname>Arbaugh</surname>
			</person>
		</names>
		<date value="2003-07"/>
		<address>Reading, Massachusetts</address>
		<identifier type="isbn">0321136209</identifier>
		<publisher>Addison Wesley</publisher>
		<title>Real 802.11 Security</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-wep" weight="0.8"/>; <keywordref type="topic-wpa" weight="0.8"/>; <keywordref type="topic-ieee80211i" weight="0.8"/>; <keywordref type="topic-tkip" weight="0.7"/>; <keywordref type="topic-eap" weight="0.7"/>; </p>
			</richtext>
		</annotation>
		<identifier type="uri">http://www.awprofessional.com/title/0321136209</identifier>
	</reference>
	<reference name="ray03">
		<names type="author">
			<person>
				<givenname>Erik T.</givenname>
				<surname>Ray</surname>
			</person>
		</names>
		<date value="2003-09"/>
		<abstract>
			<richtext>
				<p>In this second edition of the bestselling title, the author explains the important and relevant XML technologies and their capabilities clearly and succinctly with plenty of real-life projects and useful examples. He outlines the elements of markup — demystifying concepts such as attributes, entities, and namespaces — and provides enough depth and examples to get started. Learning XML is a reliable source for anyone who needs to know XML, but doesn't want to waste time wading through hundreds of web sites or 800 pages of bloated text.</p>
			</richtext>
		</abstract>
		<address>Sebastopol, California</address>
		<edition>2nd</edition>
		<identifier type="isbn">0-596-00420-6</identifier>
		<publisher>O'Reilly &amp; Associates</publisher>
		<title>Learning XML</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-xml" weight="0.7"/>; </p>
			</richtext>
		</annotation>
		<identifier type="uri">http://www.oreilly.com/catalog/learnxml2/</identifier>
	</reference>
	<reference name="sus04">
		<names type="author">
			<person>
				<givenname>Ben</givenname>
				<surname>Collins-Sussman</surname>
			</person>
			<person>
				<givenname>Brian W.</givenname>
				<surname>Fitzpatrick</surname>
			</person>
			<person>
				<givenname>C. Michael</givenname>
				<surname>Pilato</surname>
			</person>
		</names>
		<date value="2004-06"/>
		<abstract>
			<richtext>
				<p>Version Control with Subversion introduces the powerful new versioning tool designed to be the successor to CVS. An introduction to Subversion is followed by a guided tour of its capabilities. Later chapters cover more complex topics of branching, repository administration, and other advanced features. If you've never used version control, you'll find everything you need to get started. And if you're a seasoned CVS pro, it will help you make a painless leap into Subversion.</p>
			</richtext>
		</abstract>
		<address>Sebastopol, California</address>
		<identifier type="isbn">0-596-00448-6</identifier>
		<publisher>O'Reilly &amp; Associates</publisher>
		<title>Version Control with Subversion</title>
		<annotation>
			<richtext>
				<p>Keywords: (undefined keyword: subversion); </p>
			</richtext>
		</annotation>
		<identifier type="uri" resourceType="text/html">http://www.oreilly.com/catalog/0596004486/index.html</identifier>
	</reference>
	<reference name="ves03">
		<names type="author">
			<person>
				<givenname>Jennifer</givenname>
				<surname>Vesperman</surname>
			</person>
		</names>
		<date value="2003-06"/>
		<abstract>
			<richtext>
				<p>Essential CVS is a complete and easy-to-follow reference that helps programmers and system administrators apply order to the task of managing large quantities of documents. The book covers basic concepts and usage of CVS, and features a comprehensive reference for CVS commands — including a handy Command Reference Card for quick, on-the-job checks. The book also includes advanced information on all aspects of CVS that involved automation, logging, branching and merging, and "watches."</p>
			</richtext>
		</abstract>
		<address>Sebastopol, California</address>
		<identifier type="isbn">0-596-00459-1</identifier>
		<publisher>O'Reilly &amp; Associates</publisher>
		<title>Essential CVS</title>
		<annotation>
			<richtext>
				<p>Keywords: (undefined keyword: cvs); </p>
			</richtext>
		</annotation>
		<identifier type="uri">http://www.oreilly.com/catalog/cvs/</identifier>
	</reference>
	<reference name="zaw04">
		<names type="author">
			<person>
				<givenname>Jeremy D.</givenname>
				<surname>Zawodny</surname>
			</person>
			<person>
				<givenname>Derek J.</givenname>
				<surname>Balling</surname>
			</person>
		</names>
		<date value="2004-04"/>
		<address>Sebastopol, California</address>
		<identifier type="isbn">0596003064</identifier>
		<publisher>O'Reilly &amp; Associates</publisher>
		<title>High Performance MySQL</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-mysql" weight="0.8"/>; </p>
			</richtext>
		</annotation>
		<identifier type="uri">http://www.oreilly.com/catalog/hpmysql/</identifier>
	</reference>
	<reference name="lew00">
		<names type="author">
			<person>
				<givenname>Kevin</givenname>
				<surname>Lewis</surname>
			</person>
		</names>
		<date value="2000-06"/>
		<address>Sebastopol, California</address>
		<identifier type="isbn">1-56592-719-2</identifier>
		<publisher>O'Reilly &amp; Associates</publisher>
		<title>Creating Effective JavaHelp</title>
		<annotation>
			<richtext>
				<p>Keywords: (undefined keyword: javahelp); </p>
			</richtext>
		</annotation>
		<identifier type="uri">http://www.oreilly.com/catalog/creatingjavahelp/</identifier>
	</reference>
	<reference name="hop79">
		<names type="author">
			<person>
				<givenname>John E.</givenname>
				<surname>Hopcroft</surname>
			</person>
			<person>
				<givenname>Jeffrey D.</givenname>
				<surname>Ullman</surname>
			</person>
		</names>
		<date value="1979"/>
		<address>Reading, Massachusetts</address>
		<identifier type="isbn">020102988X</identifier>
		<publisher>Addison Wesley</publisher>
		<title>Introduction to Automata Theory, Languages, and Computation</title>
	</reference>
	<reference name="pla92b">
		<names type="author">
			<person>
				<givenname>Bernhard</givenname>
				<surname>Plattner</surname>
			</person>
			<person>
				<givenname>Cuno</givenname>
				<surname>Lanz</surname>
			</person>
			<person>
				<givenname>Hannes P.</givenname>
				<surname>Lubich</surname>
			</person>
			<person>
				<givenname>Markus</givenname>
				<surname>Müller</surname>
			</person>
			<person>
				<givenname>Thomas</givenname>
				<surname>Walter</surname>
			</person>
		</names>
		<date value="1992-11"/>
		<address>Reading, Massachusetts</address>
		<identifier type="isbn">0-201-56503-X</identifier>
		<publisher>Addison Wesley</publisher>
		<title>X.400 Message Handling: Standards, Interworking, Applications</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-x400" weight="0.9"/>; </p>
			</richtext>
		</annotation>
	</reference>
	<reference name="sin99">
		<names type="author">
			<person>
				<givenname>Simon</givenname>
				<surname>Singh</surname>
			</person>
		</names>
		<date value="1999-09"/>
		<identifier type="isbn">0-385-49531-5</identifier>
		<publisher>Doubleday</publisher>
		<title>The Code Book: The Evolution of Secrecy from Mary, Queen of Scots to Quantum Cryptography</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-cryptography"/>; <keywordref type="topic-skc"/>; <keywordref type="topic-pkc"/>; </p>
			</richtext>
		</annotation>
	</reference>
	<reference name="nie94">
		<names type="author">
			<person>
				<givenname>Jakob</givenname>
				<surname>Nielsen</surname>
			</person>
		</names>
		<date value="1994-10"/>
		<address>San Francisco, California</address>
		<field type="bibtex:index">usability</field>
		<identifier type="isbn">0125184069</identifier>
		<publisher>Morgan Kaufmann Publishers</publisher>
		<title>Usability Engineering</title>
	</reference>
	<reference name="joh03">
		<names type="author">
			<person>
				<givenname>Jeff</givenname>
				<surname>Johnson</surname>
			</person>
		</names>
		<date value="2003-04"/>
		<address>San Francisco, California</address>
		<identifier type="isbn">1558608400</identifier>
		<publisher>Morgan Kaufmann Publishers</publisher>
		<title>Web Bloopers: 60 Common Web Design Mistakes, and How to Avoid Them</title>
		<identifier type="uri">http://www.web-bloopers.com/</identifier>
	</reference>
	<reference name="joh00">
		<names type="author">
			<person>
				<givenname>Jeff</givenname>
				<surname>Johnson</surname>
			</person>
		</names>
		<date value="2000-03"/>
		<address>San Francisco, California</address>
		<identifier type="isbn">1558605827</identifier>
		<publisher>Morgan Kaufmann Publishers</publisher>
		<title>GUI Bloopers: Don'ts and Do's for Software Developers and Web Designers</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-gui" weight="0.7"/>; </p>
			</richtext>
		</annotation>
		<identifier type="uri">http://web-bloopers.com/gui-bloopers/</identifier>
	</reference>
	<reference name="nie99b">
		<names type="author">
			<person>
				<givenname>Jakob</givenname>
				<surname>Nielsen</surname>
			</person>
		</names>
		<date value="1999-11"/>
		<address>Indianapolis, Indiana</address>
		<field type="bibtex:index">WWW, usability</field>
		<publisher>New Riders</publisher>
		<title>Designing Web Usability: The Practice of Simplicity</title>
	</reference>
	<reference name="per99">
		<names type="author">
			<person>
				<givenname>Anthony B.</givenname>
				<surname>Perkins</surname>
			</person>
			<person>
				<givenname>Michael C.</givenname>
				<surname>Perkins</surname>
			</person>
		</names>
		<date value="1999-11"/>
		<address>San Francisco, California</address>
		<publisher>HarperBusiness</publisher>
		<title>The Internet Bubble</title>
	</reference>
	<reference name="lee99">
		<names type="author">
			<person>
				<givenname>Tim</givenname>
				<surname>Berners-Lee</surname>
			</person>
			<person>
				<givenname>Mark</givenname>
				<surname>Fischetti</surname>
			</person>
			<person>
				<givenname>Michael</givenname>
				<surname>Dertouzos</surname>
			</person>
		</names>
		<date value="1999-09"/>
		<address>San Francisco, California</address>
		<field type="bibtex:index">WWW</field>
		<publisher>HarperCollins</publisher>
		<title>Weaving the Web</title>
	</reference>
	<reference name="sch03">
		<names type="author">
			<person>
				<givenname>Harald</givenname>
				<surname>Schöning</surname>
			</person>
		</names>
		<date value="2003"/>
		<address>Munich, Germany</address>
		<identifier type="isbn">3446220089</identifier>
		<publisher>Carl Hanser Verlag</publisher>
		<title>XML und Datenbanken — Konzepte und Systeme</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-xdbms"/>; </p>
			</richtext>
		</annotation>
	</reference>
	<reference name="rho97">
		<names type="author">
			<person>
				<givenname>John</givenname>
				<surname>Rhoton</surname>
			</person>
		</names>
		<date value="1997-09"/>
		<address>Oxford, UK</address>
		<publisher>Digital Press</publisher>
		<title>X.400 and SMTP: Battle of the E-Mail Protocols</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-x400"/>; <keywordref type="topic-smtp"/>; </p>
			</richtext>
		</annotation>
	</reference>
	<reference name="sow98">
		<names type="author">
			<person>
				<givenname>John F.</givenname>
				<surname>Sowa</surname>
			</person>
		</names>
		<date value="1998-12"/>
		<address>Boston, Massachusetts</address>
		<publisher>PWS Publishing Company</publisher>
		<title>Knowledge Representation: Logical, Philosophical, and Computational Foundations</title>
	</reference>
	<reference name="nel93">
		<names type="author">
			<person>
				<givenname>Theodor Holm</givenname>
				<surname>Nelson</surname>
			</person>
		</names>
		<date value="1993"/>
		<address>Sausalito, California</address>
		<publisher>Mindful Press</publisher>
		<title>World Enough</title>
	</reference>
	<reference name="nel82">
		<names type="author">
			<person>
				<givenname>Theodor Holm</givenname>
				<surname>Nelson</surname>
			</person>
		</names>
		<date value="1982"/>
		<address>Sausalito, California</address>
		<field type="bibtex:index">Xanadu</field>
		<publisher>Mindful Press</publisher>
		<title>Literary Machines</title>
	</reference>
	<reference name="nel76">
		<names type="author">
			<person>
				<givenname>Theodor Holm</givenname>
				<surname>Nelson</surname>
			</person>
		</names>
		<date value="1976"/>
		<address>Sausalito, California</address>
		<field type="bibtex:index">Xanadu</field>
		<publisher>Mindful Press</publisher>
		<title>Computer Lib/Dream Machines</title>
	</reference>
	<reference name="nel87">
		<names type="author">
			<person>
				<givenname>Theodor Holm</givenname>
				<surname>Nelson</surname>
			</person>
		</names>
		<date value="1987"/>
		<address>Austin, Texas</address>
		<field type="bibtex:index">Xanadu</field>
		<annotation type="bibtex:note">
			<richtext>
				<p>Reprint of nel76</p>
			</richtext>
		</annotation>
		<publisher>Microsoft Press</publisher>
		<title>Computer Lib/Dream Machines</title>
	</reference>
	<reference name="win95">
		<names type="author">
			<name>Microsoft Corporation</name>
		</names>
		<date value="1995-07"/>
		<address>Austin, Texas</address>
		<edition>2nd</edition>
		<field type="bibtex:index">GUI</field>
		<publisher>Microsoft Press</publisher>
		<title>The Windows Interface Guidelines for Software Design: An Application Design Guide</title>
	</reference>
	<reference name="shn89">
		<names type="author">
			<person>
				<givenname>Ben</givenname>
				<surname>Shneiderman</surname>
			</person>
			<person>
				<givenname>Greg</givenname>
				<surname>Kearsley</surname>
			</person>
		</names>
		<date value="1989-05"/>
		<address>Reading, Massachusetts</address>
		<identifier type="isbn">0201151715</identifier>
		<publisher>Addison Wesley</publisher>
		<title>Hypertext Hands-On!: An Introduction to a New Way of Organizing and Accessing Information</title>
	</reference>
	<reference name="kri91">
		<names type="author">
			<person>
				<givenname>Balachander</givenname>
				<surname>Krishnamurthy</surname>
			</person>
			<person>
				<givenname>Jennifer</givenname>
				<surname>Rexford</surname>
			</person>
		</names>
		<date value="2001-05"/>
		<address>Reading, Massachusetts</address>
		<identifier type="isbn">0201710889</identifier>
		<publisher>Addison Wesley</publisher>
		<title>Web Protocols and Practice: HTTP/1.1, Networking Protocols, Caching, and Traffic Measurement</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-http" weight="0.8"/>; <keywordref type="topic-cache" weight="0.8"/>; <keywordref type="topic-ip" weight="0.6"/>; <keywordref type="topic-tcp" weight="0.6"/>; <keywordref type="topic-dns" weight="0.6"/>; </p>
			</richtext>
		</annotation>
	</reference>
	<reference name="car01d">
		<names type="author">
			<person>
				<givenname>David</givenname>
				<surname>Carlson</surname>
			</person>
		</names>
		<date value="2001-04"/>
		<address>Reading, Massachusetts</address>
		<identifier type="isbn">0201709155</identifier>
		<publisher>Addison Wesley</publisher>
		<title>Modeling XML Applications with UML: Practical e-Business Applications</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-xml" weight="0.8"/>; <keywordref type="topic-uml" weight="0.8"/>; </p>
			</richtext>
		</annotation>
	</reference>
	<reference name="fun00">
		<names type="author">
			<person>
				<givenname>Khun Yee</givenname>
				<surname>Fung</surname>
			</person>
		</names>
		<date value="2000-12"/>
		<address>Reading, Massachusetts</address>
		<identifier type="isbn">0201711036</identifier>
		<publisher>Addison Wesley</publisher>
		<title>XSLT: Working with XML and HTML</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-xml" weight="0.5"/>; <keywordref type="topic-xslt1" weight="0.8"/>; <keywordref type="topic-html" weight="0.6"/>; </p>
			</richtext>
		</annotation>
	</reference>
	<reference name="beh00">
		<names type="author">
			<person>
				<givenname>Henning</givenname>
				<surname>Behme</surname>
			</person>
			<person>
				<givenname>Stefan</givenname>
				<surname>Mintert</surname>
			</person>
		</names>
		<date value="2000-05"/>
		<address>Munich, Germany</address>
		<edition>2nd</edition>
		<identifier type="isbn">3827316367</identifier>
		<publisher>Addison Wesley</publisher>
		<title>XML in der Praxis</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-xml" weight="0.7"/>; <keywordref type="topic-xslt1" weight="0.6"/>; <keywordref type="topic-dsssl" weight="0.6"/>; </p>
			</richtext>
		</annotation>
	</reference>
	<reference name="dil04">
		<names type="editor">
			<person>
				<givenname>Andrew</givenname>
				<surname>Dillon</surname>
			</person>
		</names>
		<date value="2004-01"/>
		<abstract>
			<richtext>
				<p>Poor design and a failure to consider the user often act against the effectiveness in online communication. Designing Usable Electronic Text, Second Edition explores the human issues that underlie information usage and stresses that usability is the main barrier to the electronic medium's campaign to gain mass acceptance. The book is a revision of the successful First Edition with a new emphasis on the Web and hypertext design and their impacts. With the emergence of new uses of information, such as e-commerce and telemedicine, text presentation will take on a new and greater importance. Its focus on the design framework and its empirical approach make it a unique book.</p>
			</richtext>
		</abstract>
		<address>Boca Raton, Florida</address>
		<edition>2nd</edition>
		<identifier type="isbn">041524059X</identifier>
		<publisher>CRC Press</publisher>
		<title>Designing Usable Electronic Text</title>
		<identifier type="uri">http://www.itknowledgebase.net/ejournals/books/book_summary/summary.asp?id=1257</identifier>
	</reference>
	<reference name="che00">
		<names type="author">
			<person>
				<givenname>John</givenname>
				<surname>Cheesman</surname>
			</person>
			<person>
				<givenname>John</givenname>
				<surname>Daniels</surname>
			</person>
		</names>
		<date value="2000-10"/>
		<address>Reading, Massachusetts</address>
		<field type="bibtex:index">components</field>
		<publisher>Addison Wesley</publisher>
		<title>UML Components: A Simple Process for Specifying Component-Based Software</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-uml" weight="0.7"/>; </p>
			</richtext>
		</annotation>
	</reference>
	<reference name="war98">
		<names type="author">
			<person>
				<givenname>Jos B.</givenname>
				<surname>Warmer</surname>
			</person>
			<person>
				<givenname>Anneke G.</givenname>
				<surname>Kleppe</surname>
			</person>
		</names>
		<date value="1998-10"/>
		<address>Reading, Massachusetts</address>
		<publisher>Addison Wesley</publisher>
		<title>The Object Constraint Language: Precise Modeling With UML</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-uml" weight="0.7"/>; <keywordref type="topic-ocl" weight="0.9"/>; </p>
			</richtext>
		</annotation>
	</reference>
	<reference name="smi97">
		<names type="author">
			<person>
				<givenname>Richard E.</givenname>
				<surname>Smith</surname>
			</person>
		</names>
		<date value="1997-08"/>
		<address>Reading, Massachusetts</address>
		<field type="bibtex:index">cryptography</field>
		<identifier type="isbn">0201924803</identifier>
		<publisher>Addison Wesley</publisher>
		<title>Internet Cryptography</title>
	</reference>
	<reference name="con99">
		<names type="author">
			<person>
				<givenname>Larry L.</givenname>
				<surname>Constantine</surname>
			</person>
			<person>
				<givenname>Lucy A. D.</givenname>
				<surname>Lockwood</surname>
			</person>
		</names>
		<date value="1999-04"/>
		<address>Reading, Massachusetts</address>
		<identifier type="isbn">0201924781</identifier>
		<publisher>Addison Wesley</publisher>
		<title>Software For Use</title>
	</reference>
	<reference name="joh99">
		<names type="author">
			<person>
				<givenname>Kevin</givenname>
				<surname>Johnson</surname>
			</person>
		</names>
		<date value="1999-11"/>
		<address>Reading, Massachusetts</address>
		<field type="bibtex:index">SMTP, POP, IMAP, MIME, PGP</field>
		<identifier type="isbn">0-201-43288-9</identifier>
		<publisher>Addison Wesley</publisher>
		<title>Internet Email Protocols: A Developer's Guide</title>
	</reference>
	<reference name="kat03">
		<names type="author">
			<person>
				<givenname>Donald D.</givenname>
				<surname>Chamberlin</surname>
			</person>
			<person>
				<givenname>Denise</givenname>
				<surname>Draper</surname>
			</person>
			<person>
				<givenname>Mary F.</givenname>
				<surname>Fernández</surname>
			</person>
			<person>
				<givenname>Michael</givenname>
				<surname>Kay</surname>
			</person>
			<person>
				<givenname>Jonathan</givenname>
				<surname>Robie</surname>
			</person>
			<person>
				<givenname>Michael</givenname>
				<surname>Rys</surname>
			</person>
			<person>
				<givenname>Jérôme</givenname>
				<surname>Siméon</surname>
			</person>
			<person>
				<givenname>Jim</givenname>
				<surname>Tivy</surname>
			</person>
			<person>
				<givenname>Philip</givenname>
				<surname>Wadler</surname>
			</person>
		</names>
		<names type="editor">
			<person>
				<givenname>Howard</givenname>
				<surname>Katz</surname>
			</person>
		</names>
		<date value="2003-08"/>
		<address>Reading, Massachusetts</address>
		<identifier type="isbn">0321180607</identifier>
		<publisher>Addison Wesley</publisher>
		<title>XQuery from the Experts: A Guide to the W3C XML Query Language</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-xquery" weight="0.8"/>; </p>
			</richtext>
		</annotation>
	</reference>
	<reference name="mac93">
		<names type="author">
			<name>Apple Computer, Inc.</name>
		</names>
		<date value="1993-01"/>
		<address>Reading, Massachusetts</address>
		<identifier type="isbn">0201622165</identifier>
		<publisher>Addison Wesley</publisher>
		<title>MacIntosh Human Interface Guidelines</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-gui" weight="0.8"/>; </p>
			</richtext>
		</annotation>
	</reference>
	<reference name="tuf01">
		<names type="author">
			<person>
				<givenname>Edward R.</givenname>
				<surname>Tufte</surname>
			</person>
		</names>
		<date value="2001"/>
		<address>Cheshire, Connecticut</address>
		<edition>2nd</edition>
		<identifier type="isbn">0961392142</identifier>
		<publisher>Graphics Press</publisher>
		<title>The Visual Display of Quantitative Information</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-gui" weight="0.8"/>; </p>
			</richtext>
		</annotation>
	</reference>
	<reference name="sun99">
		<names type="author">
			<name>Sun Microsystems</name>
		</names>
		<date value="1999-07"/>
		<address>Reading, Massachusetts</address>
		<identifier type="isbn">0201615851</identifier>
		<publisher>Addison Wesley</publisher>
		<title>Java Look and Feel Design Guidelines</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-gui" weight="0.8"/>; </p>
			</richtext>
		</annotation>
	</reference>
	<reference name="buc99">
		<names type="author">
			<person>
				<givenname>Simon</givenname>
				<surname>Buckingham</surname>
			</person>
		</names>
		<date value="1999-07"/>
		<address>Newbury, UK</address>
		<publisher>Mobile Lifestreams</publisher>
		<title>Data on GPRS</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-gprs" weight="0.8"/>; </p>
			</richtext>
		</annotation>
	</reference>
	<reference name="red98">
		<names type="author">
			<person>
				<givenname>Siegmund</givenname>
				<surname>Redl</surname>
			</person>
			<person>
				<givenname>Matthias</givenname>
				<surname>Weber</surname>
			</person>
			<person>
				<givenname>Malcolm W.</givenname>
				<surname>Oliphant</surname>
			</person>
		</names>
		<date value="1998-05"/>
		<address>Norwood, Massachusetts</address>
		<identifier type="isbn">0890069573</identifier>
		<publisher>Artech House</publisher>
		<title>GSM and Personal Communications Handbook</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-gsm" weight="0.8"/>; </p>
			</richtext>
		</annotation>
	</reference>
	<reference name="fer03b">
		<names type="author">
			<person>
				<givenname>David F.</givenname>
				<surname>Ferraiolo</surname>
			</person>
			<person>
				<givenname>D. Richard</givenname>
				<surname>Kuhn</surname>
			</person>
			<person>
				<givenname>Ramaswamy</givenname>
				<surname>Chandramouli</surname>
			</person>
		</names>
		<date value="2003-04"/>
		<address>Norwood, Massachusetts</address>
		<identifier type="isbn">1580533701</identifier>
		<publisher>Artech House</publisher>
		<title>Role-Based Access Control</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-rbac" weight="0.9"/>; </p>
			</richtext>
		</annotation>
	</reference>
	<reference name="mou92">
		<names type="author">
			<person>
				<givenname>Michel</givenname>
				<surname>Mouly</surname>
			</person>
			<person>
				<givenname>Marie-Bernadette</givenname>
				<surname>Pautet</surname>
			</person>
		</names>
		<date value="1992-06"/>
		<identifier type="isbn">0945592159</identifier>
		<publisher>Telecom Publishing</publisher>
		<title>The GSM System for Mobile Communications</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-gsm" weight="0.8"/>; </p>
			</richtext>
		</annotation>
	</reference>
	<reference name="hei99">
		<names type="author">
			<person>
				<givenname>Gunnar</givenname>
				<surname>Heine</surname>
			</person>
		</names>
		<date value="1999-01"/>
		<identifier type="isbn">0890064717</identifier>
		<publisher>Artech House</publisher>
		<title>GSM Networks: Protocols, Terminology, and Implementation</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-gsm" weight="0.8"/>; </p>
			</richtext>
		</annotation>
	</reference>
	<reference name="ebe01">
		<names type="author">
			<person>
				<givenname>Jörg</givenname>
				<surname>Eberspächer</surname>
			</person>
			<person>
				<givenname>Hans-Jörg</givenname>
				<surname>Vögel</surname>
			</person>
			<person>
				<givenname>Christian</givenname>
				<surname>Bettstetter</surname>
			</person>
		</names>
		<date value="2001-04"/>
		<edition>2nd</edition>
		<identifier type="isbn">047149903X</identifier>
		<publisher>John Wiley &amp; Sons</publisher>
		<title>GSM Switching, Services, and Protocols</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-gsm" weight="0.8"/>; <keywordref type="topic-gprs" weight="0.7"/>; <keywordref type="topic-wap1" weight="0.7"/>; </p>
			</richtext>
		</annotation>
	</reference>
	<reference name="chr97">
		<names type="author">
			<person>
				<givenname>Clayton M.</givenname>
				<surname>Christensen</surname>
			</person>
		</names>
		<date value="1997-06"/>
		<address>Boston, Massachusetts</address>
		<field type="bibtex:index">disruptive technology</field>
		<identifier type="isbn">0875845851</identifier>
		<publisher>Harvard Business School Press</publisher>
		<title>The Innovator's Dilemma: When New Technologies Cause Great Firms to Fail</title>
	</reference>
	<reference name="chr03b">
		<names type="author">
			<person>
				<givenname>Clayton M.</givenname>
				<surname>Christensen</surname>
			</person>
			<person>
				<givenname>Michael E.</givenname>
				<surname>Raynor</surname>
			</person>
		</names>
		<date value="2003-09"/>
		<address>Boston, Massachusetts</address>
		<identifier type="isbn">1578518520</identifier>
		<publisher>Harvard Business School Press</publisher>
		<title>The Innovator's Solution: Creating and Sustaining Successful Growth</title>
	</reference>
	<reference name="ste97b">
		<names type="author">
			<person>
				<givenname>Lincoln D.</givenname>
				<surname>Stein</surname>
			</person>
		</names>
		<date value="1997-01"/>
		<address>Reading, Massachusetts</address>
		<edition>2nd</edition>
		<field type="bibtex:index">www[0.8]</field>
		<identifier type="isbn">0201634627</identifier>
		<publisher>Addison Wesley</publisher>
		<title>How to Set Up and Maintain a Web Site</title>
	</reference>
	<reference name="tan01">
		<names type="author">
			<person>
				<givenname>Adrienne</givenname>
				<surname>Tannenbaum</surname>
			</person>
		</names>
		<date value="2001-08"/>
		<address>Reading, Massachusetts</address>
		<identifier type="isbn">0201719762</identifier>
		<publisher>Addison Wesley</publisher>
		<title>Metadata Solutions: Using Metamodels, Repositories, XML, and Enterprise Portals to Generate Information on Demand</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-metadata" weight="0.8"/>; </p>
			</richtext>
		</annotation>
	</reference>
	<reference name="ste98">
		<names type="author">
			<person>
				<givenname>Lincoln D.</givenname>
				<surname>Stein</surname>
			</person>
		</names>
		<date value="1998-01"/>
		<address>Reading, Massachusetts</address>
		<field type="bibtex:index">WWW, security</field>
		<identifier type="isbn">0201634899</identifier>
		<publisher>Addison Wesley</publisher>
		<title>Web Security: A Step-by-Step Reference Guide</title>
	</reference>
	<reference name="kop95">
		<names type="author">
			<person>
				<givenname>Helmut</givenname>
				<surname>Kopka</surname>
			</person>
			<person>
				<givenname>Patrick W.</givenname>
				<surname>Daly</surname>
			</person>
		</names>
		<date value="1995-06"/>
		<address>Harlow, England</address>
		<edition>2nd</edition>
		<identifier type="isbn">0-201-42777-X</identifier>
		<publisher>Addison Wesley</publisher>
		<title>A Guide to LaTeXe</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-latex" weight="0.9"/>; </p>
			</richtext>
		</annotation>
	</reference>
	<reference name="goo94">
		<names type="author">
			<person>
				<givenname>Michel</givenname>
				<surname>Goossens</surname>
			</person>
			<person>
				<givenname>Frank</givenname>
				<surname>Mittelbach</surname>
			</person>
			<person>
				<givenname>Alexander</givenname>
				<surname>Samarin</surname>
			</person>
		</names>
		<date value="1994-01"/>
		<address>Reading, Massachusetts</address>
		<identifier type="isbn">0-201-54199-8</identifier>
		<publisher>Addison Wesley</publisher>
		<title>The LaTeX Companion</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-latex" weight="0.9"/>; </p>
			</richtext>
		</annotation>
	</reference>
	<reference name="knuth1">
		<names type="author">
			<person>
				<givenname>Donald Ervin</givenname>
				<surname>Knuth</surname>
			</person>
		</names>
		<date value="1997-07"/>
		<address>Reading, Massachusetts</address>
		<edition>3rd</edition>
		<identifier type="isbn">0-201-89683-4</identifier>
		<publisher>Addison Wesley</publisher>
		<title>The Art of Computer Programming: Fundamental Algorithms</title>
		<volume>1</volume>
	</reference>
	<reference name="knuth2">
		<names type="author">
			<person>
				<givenname>Donald Ervin</givenname>
				<surname>Knuth</surname>
			</person>
		</names>
		<date value="1998-11"/>
		<address>Reading, Massachusetts</address>
		<edition>3rd</edition>
		<identifier type="isbn">0-201-89684-2</identifier>
		<publisher>Addison Wesley</publisher>
		<title>The Art of Computer Programming: Seminumerical Algorithms</title>
		<volume>2</volume>
	</reference>
	<reference name="knuth3">
		<names type="author">
			<person>
				<givenname>Donald Ervin</givenname>
				<surname>Knuth</surname>
			</person>
		</names>
		<date value="1997-04"/>
		<address>Reading, Massachusetts</address>
		<edition>2nd</edition>
		<identifier type="isbn">0-201-89685-0</identifier>
		<publisher>Addison Wesley</publisher>
		<title>The Art of Computer Programming: Sorting and Searching</title>
		<volume>3</volume>
	</reference>
	<reference name="knu84">
		<names type="author">
			<person>
				<givenname>Donald Ervin</givenname>
				<surname>Knuth</surname>
			</person>
		</names>
		<date value="1984"/>
		<address>Reading, Massachusetts</address>
		<identifier type="isbn">0-201-13448-9</identifier>
		<publisher>Addison Wesley</publisher>
		<title>The TeXbook</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-tex"/>; </p>
			</richtext>
		</annotation>
	</reference>
	<reference name="knuth86a">
		<names type="author">
			<person>
				<givenname>Donald Ervin</givenname>
				<surname>Knuth</surname>
			</person>
		</names>
		<date value="1986"/>
		<address>Reading, Massachusetts</address>
		<identifier type="isbn">0-201-13447-0</identifier>
		<publisher>Addison Wesley</publisher>
		<title>Computers &amp; Typesetting: The TeXbook</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-tex"/>; </p>
			</richtext>
		</annotation>
		<associations>
			<xref type="updates" target="knu84"/>
		</associations>
		<volume>A</volume>
	</reference>
	<reference name="knuth86b">
		<names type="author">
			<person>
				<givenname>Donald Ervin</givenname>
				<surname>Knuth</surname>
			</person>
		</names>
		<date value="1986"/>
		<address>Reading, Massachusetts</address>
		<identifier type="isbn">0-201-13437-3</identifier>
		<publisher>Addison Wesley</publisher>
		<title>Computers &amp; Typesetting: TeX: The Program</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-tex"/>; </p>
			</richtext>
		</annotation>
		<volume>B</volume>
	</reference>
	<reference name="knuth86c">
		<names type="author">
			<person>
				<givenname>Donald Ervin</givenname>
				<surname>Knuth</surname>
			</person>
		</names>
		<date value="1986"/>
		<address>Reading, Massachusetts</address>
		<identifier type="isbn">0-201-13445-4</identifier>
		<publisher>Addison Wesley</publisher>
		<title>Computers &amp; Typesetting: The Metafont Book</title>
		<volume>C</volume>
	</reference>
	<reference name="knuth86d">
		<names type="author">
			<person>
				<givenname>Donald Ervin</givenname>
				<surname>Knuth</surname>
			</person>
		</names>
		<date value="1986"/>
		<address>Reading, Massachusetts</address>
		<identifier type="isbn">0-201-13438-1</identifier>
		<publisher>Addison Wesley</publisher>
		<title>Computers &amp; Typesetting: Metafont: The Program</title>
		<volume>D</volume>
	</reference>
	<reference name="knuth86e">
		<names type="author">
			<person>
				<givenname>Donald Ervin</givenname>
				<surname>Knuth</surname>
			</person>
		</names>
		<date value="1986"/>
		<address>Reading, Massachusetts</address>
		<identifier type="isbn">0-201-13446-2</identifier>
		<publisher>Addison Wesley</publisher>
		<title>Computers &amp; Typesetting: Computer Modern Typefaces</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-tex" weight="0.9"/>; </p>
			</richtext>
		</annotation>
		<volume>E</volume>
	</reference>
	<reference name="lam85">
		<names type="author">
			<person>
				<givenname>Leslie</givenname>
				<surname>Lamport</surname>
			</person>
		</names>
		<date value="1985"/>
		<address>Reading, Massachusetts</address>
		<identifier type="isbn">020115790X</identifier>
		<publisher>Addison Wesley</publisher>
		<title>LaTeX: A Document Preparation System</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-latex"/>; </p>
			</richtext>
		</annotation>
	</reference>
	<reference name="lam94">
		<names type="author">
			<person>
				<givenname>Leslie</givenname>
				<surname>Lamport</surname>
			</person>
		</names>
		<date value="1994-08"/>
		<address>Reading, Massachusetts</address>
		<edition>2nd</edition>
		<identifier type="isbn">0201529831</identifier>
		<publisher>Addison Wesley</publisher>
		<title>LaTeX: A Document Preparation System</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-latex"/>; </p>
			</richtext>
		</annotation>
		<associations>
			<xref type="updates" target="lam85"/>
		</associations>
	</reference>
	<reference name="box00">
		<names type="author">
			<person>
				<givenname>Don</givenname>
				<surname>Box</surname>
			</person>
			<person>
				<givenname>Aaron</givenname>
				<surname>Skonnard</surname>
			</person>
			<person>
				<givenname>John</givenname>
				<surname>Lam</surname>
			</person>
		</names>
		<date value="2000-07"/>
		<address>Reading, Massachusetts</address>
		<identifier type="isbn">0201709147</identifier>
		<publisher>Addison Wesley</publisher>
		<title>Essential XML: Beyond Markup</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-xmlinfoset" weight="0.8"/>; <keywordref type="topic-dom" weight="0.8"/>; <keywordref type="topic-sax" weight="0.8"/>; </p>
			</richtext>
		</annotation>
	</reference>
	<reference name="ous94">
		<names type="author">
			<person>
				<givenname>John K.</givenname>
				<surname>Ousterhout</surname>
			</person>
		</names>
		<date value="1994-05"/>
		<address>Reading, Massachusetts</address>
		<identifier type="isbn">020163337X</identifier>
		<publisher>Addison Wesley</publisher>
		<title>Tcl and the Tk Toolkit</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-tcltk" weight="0.8"/>; </p>
			</richtext>
		</annotation>
	</reference>
	<reference name="mau96">
		<names type="author">
			<person>
				<givenname>Hermann</givenname>
				<surname>Maurer</surname>
			</person>
		</names>
		<date value="1996"/>
		<address>Reading, Massachusetts</address>
		<identifier type="isbn">0201403463</identifier>
		<publisher>Addison Wesley</publisher>
		<title>HyperWave — The Next Generation Web Solution</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-hyperwave"/>; </p>
			</richtext>
		</annotation>
	</reference>
	<reference name="uni91">
		<names type="author">
			<name>Unicode Consortium</name>
		</names>
		<date value="1991-10"/>
		<address>Reading, Massachusetts</address>
		<identifier type="isbn">0201567881</identifier>
		<publisher>Addison Wesley</publisher>
		<title>The Unicode Standard: Worldwide Character Encoding</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-unicode"/>; </p>
			</richtext>
		</annotation>
	</reference>
	<reference name="uni96">
		<names type="author">
			<name>Unicode Consortium</name>
		</names>
		<date value="1996-08"/>
		<address>Reading, Massachusetts</address>
		<identifier type="isbn">0201483459</identifier>
		<publisher>Addison Wesley</publisher>
		<title>The Unicode Standard: Version 2.0</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-unicode"/>; </p>
			</richtext>
		</annotation>
		<associations>
			<xref type="updates" target="uni91"/>
		</associations>
	</reference>
	<reference name="uni00">
		<names type="author">
			<name>Unicode Consortium</name>
		</names>
		<date value="2000-02"/>
		<address>Reading, Massachusetts</address>
		<identifier type="isbn">0201616335</identifier>
		<publisher>Addison Wesley</publisher>
		<title>The Unicode Standard: Version 3.0</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-unicode"/>; </p>
			</richtext>
		</annotation>
		<associations>
			<xref type="updates" target="uni96"/>
		</associations>
	</reference>
	<reference name="unicode4">
		<names type="author">
			<name>Unicode Consortium</name>
		</names>
		<date value="2003-08"/>
		<address>Reading, Massachusetts</address>
		<identifier type="isbn">0321185781</identifier>
		<publisher>Addison Wesley</publisher>
		<title>The Unicode Standard: Version 4.0</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-unicode"/>; </p>
			</richtext>
		</annotation>
		<associations>
			<xref type="updates" target="uni00"/>
		</associations>
	</reference>
	<reference name="ps2">
		<names type="author">
			<name>Adobe Systems Inc.</name>
		</names>
		<date value="1990-12"/>
		<address>Reading, Massachusetts</address>
		<edition>2nd</edition>
		<field type="bibtex:index">PostScript 2</field>
		<identifier type="isbn">0-201-10174-2</identifier>
		<publisher>Addison Wesley</publisher>
		<title>Postscript Language Reference Manual</title>
	</reference>
	<reference name="les99">
		<names type="author">
			<person>
				<givenname>Lawrence</givenname>
				<surname>Lessig</surname>
			</person>
		</names>
		<date value="1999"/>
		<address>New York, NY</address>
		<identifier type="isbn">0465039138</identifier>
		<publisher>Basic Books</publisher>
		<title>Code and Other Laws of Cyberspace</title>
	</reference>
	<reference name="les01">
		<names type="author">
			<person>
				<givenname>Lawrence</givenname>
				<surname>Lessig</surname>
			</person>
		</names>
		<date value="2001"/>
		<address>New York, NY</address>
		<identifier type="isbn">0375726446</identifier>
		<publisher>Vintage Books</publisher>
		<title>The Future of Ideas</title>
	</reference>
	<reference name="ps3">
		<names type="author">
			<name>Adobe Systems Inc.</name>
		</names>
		<date value="1999-01"/>
		<address>Reading, Massachusetts</address>
		<edition>3rd</edition>
		<field type="bibtex:index">PostScript 3</field>
		<identifier type="isbn">0-201-37922-8</identifier>
		<publisher>Addison Wesley</publisher>
		<title>Postscript Language Reference Manual</title>
	</reference>
	<reference name="bie93">
		<names type="author">
			<person>
				<givenname>Tim</givenname>
				<surname>Bienz</surname>
			</person>
			<person>
				<givenname>Richard</givenname>
				<surname>Cohn</surname>
			</person>
		</names>
		<date value="1993-07"/>
		<address>Reading, Massachusetts</address>
		<identifier type="isbn">0-201-62628-4</identifier>
		<publisher>Addison Wesley</publisher>
		<title>Portable Document Format Reference Manual</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-pdf"/>; </p>
			</richtext>
		</annotation>
	</reference>
	<reference name="pdf13">
		<names type="author">
			<name>Adobe Systems Inc.</name>
		</names>
		<date value="2000-01"/>
		<address>Reading, Massachusetts</address>
		<edition>2nd</edition>
		<identifier type="isbn">0201615886</identifier>
		<publisher>Addison Wesley</publisher>
		<title>PDF Reference: Version 1.3</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-pdf"/>; </p>
			</richtext>
		</annotation>
		<associations>
			<xref type="updates" target="bie96"/>
		</associations>
	</reference>
	<reference name="bry97">
		<names type="author">
			<person>
				<givenname>Martin</givenname>
				<surname>Bryan</surname>
			</person>
		</names>
		<date value="1997-05"/>
		<address>Reading, Massachusetts</address>
		<edition>2nd</edition>
		<identifier type="isbn">0201403943</identifier>
		<publisher>Addison Wesley</publisher>
		<title>SGML and HTML Explained</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-sgml" weight="0.8"/>; <keywordref type="topic-html" weight="0.7"/>; </p>
			</richtext>
		</annotation>
	</reference>
	<reference name="hoe98">
		<names type="author">
			<person>
				<givenname>Alan</givenname>
				<surname>Hoenig</surname>
			</person>
		</names>
		<date value="1998-02"/>
		<address>Oxford, UK</address>
		<identifier type="isbn">019509686X</identifier>
		<publisher>Oxford University Press</publisher>
		<title>TeX Unbound: LaTeX &amp; TeX Strategies for Fonts, Graphics, and More</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-tex" weight="0.8"/>; <keywordref type="topic-latex" weight="0.8"/>; </p>
			</richtext>
		</annotation>
	</reference>
	<reference name="gol91b">
		<names type="author">
			<person>
				<givenname>Charles F.</givenname>
				<surname>Goldfarb</surname>
			</person>
		</names>
		<date value="1991-02"/>
		<address>Oxford, UK</address>
		<publisher>Oxford University Press</publisher>
		<title>The SGML Handbook</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-sgml" weight="0.9"/>; </p>
			</richtext>
		</annotation>
	</reference>
	<reference name="sch00">
		<names type="author">
			<person>
				<givenname>Keith</givenname>
				<surname>Schengili-Roberts</surname>
			</person>
		</names>
		<date value="2000-05"/>
		<address>Upper Saddle River, New Jersey</address>
		<identifier type="isbn">0130834564</identifier>
		<publisher>Prentice-Hall</publisher>
		<title>Core CSS</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-css1" weight="0.8"/>; <keywordref type="topic-css2" weight="0.8"/>; </p>
			</richtext>
		</annotation>
	</reference>
	<reference name="li96">
		<names type="author">
			<person>
				<givenname>Xia</givenname>
				<surname>Li</surname>
			</person>
			<person>
				<givenname>Nancy</givenname>
				<surname>Crane</surname>
			</person>
		</names>
		<date value="1996-09"/>
		<address>Medford, New Jersey</address>
		<identifier type="isbn">1573870277</identifier>
		<publisher>Information Today, Inc.</publisher>
		<title>Electronic Styles: A Handbook for Citing Electronic Information</title>
	</reference>
	<reference name="gen97">
		<names type="author">
			<person>
				<givenname>Gérard</givenname>
				<surname>Genette</surname>
			</person>
		</names>
		<date value="1997-03"/>
		<abstract>
			<richtext>
				<p>Paratexts are those liminal devices and conventions, both within and outside the book, that form part of the complex mediation between book, author, publisher and reader: titles, forewords, epigraphs and publishers' jacket copy are part of a book's private and public history. In this first English translation of Paratexts, Gerard Genette shows how the special pragmatic status of paratextual declaration requires a carefully calibrated analysis of their illocutionary force. With clarity, precision and an extraordinary range of reference, Paratexts constitutes an encyclopedic survey of the customs and institutions as revealed in the borderlands of the text. Genette presents a global view of these liminal mediations and the logic of their relation to the reading public by studying each element as a literary function. Richard Macksey's foreword describes how the poetics of paratexts interact with more general questions of literature as a cultural institution, and situates Gennet's work in contemporary literary theory.</p>
			</richtext>
		</abstract>
		<address>Cambridge, UK</address>
		<identifier type="isbn">0-521-41350-8</identifier>
		<publisher>Cambridge University Press</publisher>
		<title>Paratexts: Thresholds of Interpretation</title>
		<identifier type="uri">http://www.cambridge.org/uk/catalogue/catalogue.asp?isbn=0521413508</identifier>
	</reference>
	<reference name="wal98">
		<names type="author">
			<person>
				<givenname>Janice</givenname>
				<surname>Walker</surname>
			</person>
			<person>
				<givenname>Todd</givenname>
				<surname>Taylor</surname>
			</person>
		</names>
		<date value="1998-10"/>
		<address>New York, NY</address>
		<identifier type="isbn">0231107897</identifier>
		<publisher>Columbia University Press</publisher>
		<title>The Columbia Guide to Online Style</title>
		<identifier type="uri" resourceType="text/html">http://www.columbia.edu/cu/cup/catalog/data/023110/0231107889.HTM</identifier>
	</reference>
	<reference name="mey00">
		<names type="author">
			<person>
				<givenname>Bertrand</givenname>
				<surname>Meyer</surname>
			</person>
		</names>
		<date value="2000-03"/>
		<address>Upper Saddle River, New Jersey</address>
		<edition>2nd</edition>
		<identifier type="isbn">0136291554</identifier>
		<publisher>Prentice-Hall</publisher>
		<title>Object-Oriented Software Construction</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-eiffel"/>; <keywordref type="topic-oop" weight="0.9"/>; </p>
			</richtext>
		</annotation>
	</reference>
	<reference name="luo97">
		<names type="author">
			<person>
				<givenname>Ari</givenname>
				<surname>Luotonen</surname>
			</person>
		</names>
		<date value="1997-12"/>
		<address>Upper Saddle River, New Jersey</address>
		<publisher>Prentice-Hall</publisher>
		<title>Web Proxy Servers</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-http" weight="0.7"/>; <keywordref type="topic-proxy" weight="0.8"/>; </p>
			</richtext>
		</annotation>
	</reference>
	<reference name="flo99">
		<names type="author">
			<person>
				<givenname>Michael</givenname>
				<surname>Floyd</surname>
			</person>
		</names>
		<date value="1999-12"/>
		<address>Upper Saddle River, New Jersey</address>
		<publisher>Prentice-Hall</publisher>
		<title>Building Web Sites with XML</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-xml" weight="0.8"/>; </p>
			</richtext>
		</annotation>
	</reference>
	<reference name="gol98">
		<names type="author">
			<person>
				<givenname>Charles F.</givenname>
				<surname>Goldfarb</surname>
			</person>
			<person>
				<givenname>Paul</givenname>
				<surname>Prescod</surname>
			</person>
		</names>
		<date value="1998-06"/>
		<address>Upper Saddle River, New Jersey</address>
		<identifier type="isbn">0130811521</identifier>
		<publisher>Prentice-Hall</publisher>
		<title>The XML Handbook</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-xml" weight="0.8"/>; </p>
			</richtext>
		</annotation>
	</reference>
	<reference name="gol99b">
		<names type="author">
			<person>
				<givenname>Charles F.</givenname>
				<surname>Goldfarb</surname>
			</person>
			<person>
				<givenname>Paul</givenname>
				<surname>Prescod</surname>
			</person>
		</names>
		<date value="1999-11"/>
		<address>Upper Saddle River, New Jersey</address>
		<edition>2nd</edition>
		<identifier type="isbn">0130147141</identifier>
		<publisher>Prentice-Hall</publisher>
		<title>The XML Handbook</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-xml" weight="0.8"/>; </p>
			</richtext>
		</annotation>
		<associations>
			<xref type="updates" target="gol98"/>
		</associations>
	</reference>
	<reference name="gol00b">
		<names type="author">
			<person>
				<givenname>Charles F.</givenname>
				<surname>Goldfarb</surname>
			</person>
			<person>
				<givenname>Paul</givenname>
				<surname>Prescod</surname>
			</person>
		</names>
		<date value="2000-11"/>
		<address>Upper Saddle River, New Jersey</address>
		<edition>3rd</edition>
		<identifier type="isbn">013055068X</identifier>
		<publisher>Prentice-Hall</publisher>
		<title>The XML Handbook</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-xml" weight="0.8"/>; </p>
			</richtext>
		</annotation>
		<associations>
			<xref type="updates" target="gol99b"/>
		</associations>
	</reference>
	<reference name="gol01">
		<names type="author">
			<person>
				<givenname>Charles F.</givenname>
				<surname>Goldfarb</surname>
			</person>
			<person>
				<givenname>Paul</givenname>
				<surname>Prescod</surname>
			</person>
		</names>
		<date value="2001-12"/>
		<address>Upper Saddle River, New Jersey</address>
		<edition>4th</edition>
		<identifier type="isbn">0130651982</identifier>
		<publisher>Prentice-Hall</publisher>
		<title>Charles F. Goldfarb's XML Handbook</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-xml" weight="0.8"/>; </p>
			</richtext>
		</annotation>
		<associations>
			<xref type="updates" target="gol00b"/>
		</associations>
	</reference>
	<reference name="gol03">
		<names type="author">
			<person>
				<givenname>Charles F.</givenname>
				<surname>Goldfarb</surname>
			</person>
			<person>
				<givenname>Paul</givenname>
				<surname>Prescod</surname>
			</person>
		</names>
		<date value="2003-11"/>
		<address>Upper Saddle River, New Jersey</address>
		<edition>5th</edition>
		<identifier type="isbn">0130497657</identifier>
		<publisher>Prentice-Hall</publisher>
		<title>Charles F. Goldfarb's XML Handbook</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-xml" weight="0.8"/>; </p>
			</richtext>
		</annotation>
		<associations>
			<xref type="updates" target="gol01"/>
		</associations>
	</reference>
	<reference name="gar02">
		<names type="author">
			<person>
				<givenname>Lars Marius</givenname>
				<surname>Garshol</surname>
			</person>
		</names>
		<date value="2002-05"/>
		<address>Upper Saddle River, New Jersey</address>
		<identifier type="isbn">0130889024</identifier>
		<publisher>Prentice-Hall</publisher>
		<title>Definitive XML Application Development</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-xml" weight="0.8"/>; <keywordref type="topic-dom" weight="0.8"/>; <keywordref type="topic-sax" weight="0.8"/>; <keywordref type="topic-xslt1" weight="0.8"/>; </p>
			</richtext>
		</annotation>
		<identifier type="uri">http://www.garshol.priv.no/download/text/ph1/</identifier>
	</reference>
	<reference name="rub97">
		<names type="author">
			<person>
				<givenname>Yuri</givenname>
				<surname>Rubinsky</surname>
			</person>
			<person>
				<givenname>Murray</givenname>
				<surname>Maloney</surname>
			</person>
		</names>
		<date value="1997-02"/>
		<address>Upper Saddle River, New Jersey</address>
		<identifier type="isbn">0135199840</identifier>
		<publisher>Prentice-Hall</publisher>
		<title>SGML on the Web: Small Steps Beyond HTML</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-sgml" weight="0.8"/>; </p>
			</richtext>
		</annotation>
	</reference>
	<reference name="duc98">
		<names type="author">
			<person>
				<givenname>Bob</givenname>
				<surname>DuCharme</surname>
			</person>
		</names>
		<date value="1998-12"/>
		<address>Upper Saddle River, New Jersey</address>
		<publisher>Prentice-Hall</publisher>
		<title>XML: The Annotated Specification</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-xml" weight="0.9"/>; </p>
			</richtext>
		</annotation>
	</reference>
	<reference name="meg98">
		<names type="author">
			<person>
				<givenname>David</givenname>
				<surname>Megginson</surname>
			</person>
		</names>
		<date value="1998-01"/>
		<address>Upper Saddle River, New Jersey</address>
		<identifier type="isbn">0136422993</identifier>
		<publisher>Prentice-Hall</publisher>
		<title>Structuring XML Documents</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-xml" weight="0.9"/>; </p>
			</richtext>
		</annotation>
	</reference>
	<reference name="gru91">
		<names type="author">
			<person>
				<givenname>Dick</givenname>
				<surname>Grune</surname>
			</person>
			<person>
				<givenname>Ceriel Jan Hubert</givenname>
				<surname>Jacobs</surname>
			</person>
		</names>
		<date value="1991-08"/>
		<identifier type="isbn">0136514316</identifier>
		<publisher>Ellis Horwood</publisher>
		<title>Parsing Techniques: A Practical Guide</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-parser"/>; </p>
			</richtext>
		</annotation>
		<identifier type="uri" resourceType="text/html">http://www.cs.vu.nl/~dick/PTAPG.html</identifier>
	</reference>
	<reference name="mal95">
		<names type="author">
			<person>
				<givenname>Eve</givenname>
				<surname>Maler</surname>
			</person>
			<person>
				<givenname>Jeanne</givenname>
				<surname>El Andaloussi</surname>
			</person>
		</names>
		<date value="1995-12"/>
		<address>Upper Saddle River, New Jersey</address>
		<identifier type="isbn">0133098818</identifier>
		<publisher>Prentice-Hall</publisher>
		<title>Developing SGML DTDs: From Text to Model to Markup</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-sgml" weight="0.8"/>; <keywordref type="topic-dtd" weight="0.8"/>; </p>
			</richtext>
		</annotation>
	</reference>
	<reference name="dei99">
		<names type="author">
			<person>
				<givenname>Harvey M.</givenname>
				<surname>Deitel</surname>
			</person>
			<person>
				<givenname>Paul J.</givenname>
				<surname>Deitel</surname>
			</person>
			<person>
				<givenname>Tem R.</givenname>
				<surname>Nieto</surname>
			</person>
		</names>
		<date value="1999-12"/>
		<address>Upper Saddle River, New Jersey</address>
		<identifier type="isbn">0130161438</identifier>
		<publisher>Prentice-Hall</publisher>
		<title>Internet &amp; World Wide Web: How to Program</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-www"/>; </p>
			</richtext>
		</annotation>
	</reference>
	<reference name="mei03">
		<names type="author">
			<person>
				<givenname>Christoph</givenname>
				<surname>Meinel</surname>
			</person>
			<person>
				<givenname>Harald</givenname>
				<surname>Sack</surname>
			</person>
		</names>
		<date value="2003-10"/>
		<address>Berlin, Germany</address>
		<identifier type="isbn">3540442766</identifier>
		<publisher>Springer-Verlag</publisher>
		<title>WWW: Kommunikation, Internetworking, Web-Technologien</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-www"/>; </p>
			</richtext>
		</annotation>
	</reference>
	<reference name="tha00">
		<names type="author">
			<person>
				<givenname>Bernhard</givenname>
				<surname>Thalheim</surname>
			</person>
		</names>
		<date value="2000"/>
		<address>Berlin, Germany</address>
		<identifier type="isbn">3540654704</identifier>
		<publisher>Springer-Verlag</publisher>
		<title>Entity-Relationship Modeling: Foundations of Database Technology</title>
	</reference>
	<reference name="wid02">
		<names type="author">
			<person>
				<givenname>Richard</givenname>
				<surname>Widhalm</surname>
			</person>
			<person>
				<givenname>Thomas</givenname>
				<surname>Mück</surname>
			</person>
		</names>
		<date value="2001-09"/>
		<address>Berlin, Germany</address>
		<identifier type="isbn">3-540-41719-2</identifier>
		<publisher>Springer-Verlag</publisher>
		<title>Topic Maps: Semantische Suche im Internet</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-topicmaps" weight="0.8"/>; </p>
			</richtext>
		</annotation>
	</reference>
	<reference name="von05">
		<names type="author">
			<person>
				<givenname>Helmut</givenname>
				<surname>Vonhoegen</surname>
			</person>
		</names>
		<date value="2005-03"/>
		<address>Bonn, Germany</address>
		<edition>3</edition>
		<identifier type="isbn">3-89842-630-0</identifier>
		<publisher>Galileo Computing</publisher>
		<title>Einstieg in XML</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-xml" weight="0.7"/>; </p>
			</richtext>
		</annotation>
	</reference>
	<reference name="str97">
		<names type="author">
			<person>
				<givenname>Christine</givenname>
				<surname>Strothotte</surname>
			</person>
			<person>
				<givenname>Thomas</givenname>
				<surname>Strothotte</surname>
			</person>
		</names>
		<date value="1997"/>
		<address>Berlin, Germany</address>
		<identifier type="isbn">3540594175</identifier>
		<publisher>Springer-Verlag</publisher>
		<title>Seeing Between the Pixels: Pictures in Interactive Systems</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-gui" weight="0.8"/>; </p>
			</richtext>
		</annotation>
	</reference>
	<reference name="wil98">
		<names type="author">
			<person>
				<givenname>Erik</givenname>
				<surname>Wilde</surname>
			</person>
		</names>
		<date value="1998-11"/>
		<address>Berlin, Germany</address>
		<identifier type="isbn">3540642854</identifier>
		<publisher>Springer-Verlag</publisher>
		<title>Wilde's WWW — Technical Foundations of the World Wide Web</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-www"/>; </p>
			</richtext>
		</annotation>
		<identifier type="uri">http://dret.net/netdret/publications#wil98</identifier>
		<identifier type="uri">http://wildesweb.com/e1/</identifier>
	</reference>
	<reference name="wil99a">
		<names type="author">
			<person>
				<givenname>Erik</givenname>
				<surname>Wilde</surname>
			</person>
		</names>
		<date value="1999-07"/>
		<address>Berlin, Germany</address>
		<identifier type="isbn">3540647007</identifier>
		<publisher>Springer-Verlag</publisher>
		<title>World Wide Web — Technische Grundlagen</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-www"/>; </p>
			</richtext>
		</annotation>
		<identifier type="uri">http://dret.net/netdret/publications#wil99a</identifier>
		<identifier type="uri">http://wildesweb.com/g1/</identifier>
	</reference>
	<reference name="wil01a">
		<names type="author">
			<person>
				<givenname>Erik</givenname>
				<surname>Wilde</surname>
			</person>
			<person>
				<givenname>David</givenname>
				<surname>Lowe</surname>
			</person>
		</names>
		<date value="2002-07"/>
		<address>Reading, Massachusetts</address>
		<identifier type="isbn">0201703440</identifier>
		<publisher>Addison Wesley</publisher>
		<title>XPath, XLink, XPointer, and XML: A Practical Guide to Web Hyperlinking and Transclusion</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-xml" weight="0.6"/>; <keywordref type="topic-xlink" weight="0.8"/>; <keywordref type="topic-xpointer" weight="0.8"/>; <keywordref type="topic-xpath1" weight="0.7"/>; </p>
			</richtext>
		</annotation>
		<identifier type="uri">http://dret.net/netdret/publications#wil01a</identifier>
	</reference>
	<reference name="jac92">
		<names type="author">
			<person>
				<givenname>Ivar</givenname>
				<surname>Jacobson</surname>
			</person>
		</names>
		<date value="1992-06"/>
		<address>Reading, Massachusetts</address>
		<identifier type="isbn">0201544350</identifier>
		<publisher>Addison Wesley</publisher>
		<title>Object-Oriented Software Engineering: A Use Case Driven Approach</title>
	</reference>
	<reference name="boo98">
		<names type="author">
			<person>
				<givenname>Grady</givenname>
				<surname>Booch</surname>
			</person>
			<person>
				<givenname>James</givenname>
				<surname>Rumbaugh</surname>
			</person>
			<person>
				<givenname>Ivar</givenname>
				<surname>Jacobson</surname>
			</person>
		</names>
		<date value="1998-09"/>
		<address>Reading, Massachusetts</address>
		<identifier type="isbn">0201571684</identifier>
		<publisher>Addison Wesley</publisher>
		<title>The Unified Modeling Language User Guide</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-uml" weight="0.8"/>; </p>
			</richtext>
		</annotation>
	</reference>
	<reference name="boo05">
		<names type="author">
			<person>
				<givenname>Grady</givenname>
				<surname>Booch</surname>
			</person>
			<person>
				<givenname>James</givenname>
				<surname>Rumbaugh</surname>
			</person>
			<person>
				<givenname>Ivar</givenname>
				<surname>Jacobson</surname>
			</person>
		</names>
		<date value="2005-05"/>
		<address>Reading, Massachusetts</address>
		<edition>2</edition>
		<identifier type="isbn">0321267974</identifier>
		<publisher>Addison Wesley</publisher>
		<title>The Unified Modeling Language User Guide</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-uml" weight="0.8"/>; </p>
			</richtext>
		</annotation>
		<associations>
			<xref type="updates" target="boo98"/>
		</associations>
	</reference>
	<reference name="fow03">
		<names type="author">
			<person>
				<givenname>Martin</givenname>
				<surname>Fowler</surname>
			</person>
		</names>
		<date value="2003-09"/>
		<address>Reading, Massachusetts</address>
		<edition>3</edition>
		<identifier type="isbn">0321193687</identifier>
		<publisher>Addison Wesley</publisher>
		<title>UML Distilled: A Brief Guide to the Standard Object Modeling Language</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-uml" weight="0.8"/>; </p>
			</richtext>
		</annotation>
	</reference>
	<reference name="har02">
		<names type="author">
			<person>
				<givenname>Elliotte Rusty</givenname>
				<surname>Harold</surname>
			</person>
		</names>
		<date value="2002-11"/>
		<address>Reading, Massachusetts</address>
		<identifier type="isbn">0201771861</identifier>
		<publisher>Addison Wesley</publisher>
		<title>Processing XML with Java: A Guide to SAX, DOM, JDOM, JAXP, and TrAX</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-xml" weight="0.6"/>; <keywordref type="topic-java" weight="0.6"/>; <keywordref type="topic-sax" weight="0.8"/>; <keywordref type="topic-dom" weight="0.8"/>; <keywordref type="topic-jdom" weight="0.8"/>; <keywordref type="topic-jaxp" weight="0.8"/>; <keywordref type="topic-trax" weight="0.8"/>; </p>
			</richtext>
		</annotation>
		<identifier type="uri">http://www.cafeconleche.org/books/xmljava/</identifier>
	</reference>
	<reference name="rot01">
		<names type="author">
			<person>
				<givenname>Gunter</givenname>
				<surname>Rothfuss</surname>
			</person>
			<person>
				<givenname>Christian</givenname>
				<surname>Ried</surname>
			</person>
		</names>
		<date value="2001"/>
		<address>Berlin, Germany</address>
		<identifier type="isbn">3540665943</identifier>
		<publisher>Springer-Verlag</publisher>
		<series>Xpert.press</series>
		<title>Content Management mit XML</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-xml" weight="0.6"/>; </p>
			</richtext>
		</annotation>
		<identifier type="uri">http://www.xml-content.de</identifier>
	</reference>
	<reference name="eck03">
		<names type="author">
			<person>
				<givenname>Rainer</givenname>
				<surname>Eckstein</surname>
			</person>
			<person>
				<givenname>Silke</givenname>
				<surname>Eckstein</surname>
			</person>
		</names>
		<date value="2003-11"/>
		<address>Heidelberg, Germany</address>
		<identifier type="isbn">3-89864-222-4</identifier>
		<publisher>dpunkt.verlag</publisher>
		<title>XML und Datenmodellierung</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-xmlschema" weight="0.7"/>; <keywordref type="topic-rdf" weight="0.7"/>; <keywordref type="topic-xml" weight="0.7"/>; </p>
			</richtext>
		</annotation>
		<identifier type="uri" resourceType="text/html">http://www.dpunkt.de/buch/3-89864-222-4.html</identifier>
	</reference>
	<reference name="kno01">
		<names type="author">
			<person>
				<givenname>Manfred</givenname>
				<surname>Knobloch</surname>
			</person>
			<person>
				<givenname>Matthias</givenname>
				<surname>Kopp</surname>
			</person>
		</names>
		<date value="2001-02"/>
		<address>Heidelberg, Germany</address>
		<identifier type="isbn">3932588967</identifier>
		<publisher>dpunkt.verlag</publisher>
		<title>Web-Design mit XML</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-xml" weight="0.7"/>; <keywordref type="topic-xslt1" weight="0.8"/>; <keywordref type="topic-css" weight="0.8"/>; <keywordref type="topic-xsl" weight="0.7"/>; <keywordref type="topic-xpath1" weight="0.8"/>; </p>
			</richtext>
		</annotation>
	</reference>
	<reference name="tue03">
		<names type="author">
			<person>
				<givenname>Can</givenname>
				<surname>Türker</surname>
			</person>
		</names>
		<date value="2003-02"/>
		<address>Heidelberg, Germany</address>
		<identifier type="isbn">3898642194</identifier>
		<publisher>dpunkt.verlag</publisher>
		<title>SQL:1999 &amp; SQL:2003</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-sqlxml" weight="0.7"/>; <keywordref type="topic-sql" weight="0.7"/>; <keywordref type="topic-jdbc" weight="0.7"/>; <keywordref type="topic-sqlj" weight="0.7"/>; </p>
			</richtext>
		</annotation>
		<identifier type="uri" resourceType="text/html">http://www.dpunkt.de/buch/3-89864-219-4.html</identifier>
	</reference>
	<reference name="pud98">
		<names type="author">
			<person>
				<givenname>Arno</givenname>
				<surname>Puder</surname>
			</person>
			<person>
				<givenname>Kay</givenname>
				<surname>Römer</surname>
			</person>
		</names>
		<date value="1998"/>
		<address>Heidelberg, Germany</address>
		<identifier type="isbn">3932588118</identifier>
		<publisher>dpunkt.verlag</publisher>
		<title>MICO is CORBA: A CORBA 2.0 Compliant Implementation</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-corba" weight="0.8"/>; </p>
			</richtext>
		</annotation>
		<identifier type="uri">http://www.dpunkt.de/mico</identifier>
	</reference>
	<reference name="pud99">
		<names type="author">
			<person>
				<givenname>Arno</givenname>
				<surname>Puder</surname>
			</person>
			<person>
				<givenname>Kay</givenname>
				<surname>Römer</surname>
			</person>
		</names>
		<date value="1999-04"/>
		<address>Heidelberg, Germany</address>
		<edition>2nd</edition>
		<identifier type="isbn">3932588118</identifier>
		<publisher>dpunkt.verlag</publisher>
		<title>MICO is CORBA: A CORBA 2.2 Compliant Implementation</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-corba" weight="0.8"/>; </p>
			</richtext>
		</annotation>
		<associations>
			<xref type="updates" target="pud98"/>
		</associations>
		<identifier type="uri">http://www.dpunkt.de/mico</identifier>
	</reference>
	<reference name="pud00">
		<names type="author">
			<person>
				<givenname>Arno</givenname>
				<surname>Puder</surname>
			</person>
			<person>
				<givenname>Kay</givenname>
				<surname>Römer</surname>
			</person>
		</names>
		<date value="2000-03"/>
		<address>Heidelberg, Germany</address>
		<edition>3rd</edition>
		<identifier type="isbn">393258872X</identifier>
		<publisher>dpunkt.verlag</publisher>
		<title>MICO: An Open Source CORBA Implementation</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-corba" weight="0.8"/>; </p>
			</richtext>
		</annotation>
		<associations>
			<xref type="updates" target="pud99"/>
		</associations>
		<identifier type="uri">http://www.dpunkt.de/mico</identifier>
	</reference>
	<reference name="lub95">
		<names type="author">
			<person>
				<givenname>Hannes P.</givenname>
				<surname>Lubich</surname>
			</person>
		</names>
		<date value="1995"/>
		<address>Berlin, Germany</address>
		<identifier type="isbn">3540588442</identifier>
		<publisher>Springer-Verlag</publisher>
		<series>Lecture Notes in Computer Science</series>
		<field type="bibtex:src">EW</field>
		<title>Towards a CSCW Framework for Scientific Cooperation in Europe</title>
		<volume>889</volume>
	</reference>
	<reference name="het97">
		<names type="author">
			<person>
				<givenname>Paul S.</givenname>
				<surname>Hethmon</surname>
			</person>
		</names>
		<date value="1997-03"/>
		<address>Greenwich, Connecticut</address>
		<identifier type="isbn">1884777376</identifier>
		<publisher>Manning</publisher>
		<field type="bibtex:src">EW</field>
		<title>Illustrated Guide to HTTP</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-http" weight="0.9"/>; </p>
			</richtext>
		</annotation>
	</reference>
	<reference name="lig97">
		<names type="author">
			<person>
				<givenname>Richard</givenname>
				<surname>Light</surname>
			</person>
		</names>
		<date value="1997-09"/>
		<address>Indianapolis, Indiana</address>
		<identifier type="isbn">1575213346</identifier>
		<publisher>Sams.net</publisher>
		<field type="bibtex:src">EW</field>
		<title>Presenting XML</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-xml" weight="0.9"/>; </p>
			</richtext>
		</annotation>
	</reference>
	<reference name="wel01">
		<names type="author">
			<person>
				<givenname>Luke</givenname>
				<surname>Welling</surname>
			</person>
			<person>
				<givenname>Laura</givenname>
				<surname>Thomson</surname>
			</person>
		</names>
		<date value="2001-03"/>
		<address>Indianapolis, Indiana</address>
		<identifier type="isbn">0672317842</identifier>
		<publisher>Sams</publisher>
		<title>PHP and MySQL Web Development</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-php" weight="0.8"/>; <keywordref type="topic-mysql" weight="0.8"/>; </p>
			</richtext>
		</annotation>
	</reference>
	<reference name="bro02c">
		<names type="author">
			<person>
				<givenname>Bill</givenname>
				<surname>Brogden</surname>
			</person>
			<person>
				<givenname>Conrad</givenname>
				<surname>D'Cruz</surname>
			</person>
			<person>
				<givenname>Mark</givenname>
				<surname>Gaither</surname>
			</person>
		</names>
		<date value="2002-10"/>
		<address>Berkeley, California</address>
		<identifier type="isbn">0782141315</identifier>
		<publisher>Sybex</publisher>
		<title>Cocoon 2 Programming: Web Publishing with XML and Java</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-cocoon" weight="0.8"/>; </p>
			</richtext>
		</annotation>
		<identifier type="uri">http://www.sybex.com/sybexbooks.nsf/booklist/4131</identifier>
	</reference>
	<reference name="moc02">
		<names type="author">
			<person>
				<givenname>Lajos</givenname>
				<surname>Moczar</surname>
			</person>
			<person>
				<givenname>Jeremy</givenname>
				<surname>Aston</surname>
			</person>
		</names>
		<date value="2002-12"/>
		<address>Indianapolis, Indiana</address>
		<identifier type="isbn">0672322579</identifier>
		<publisher>Sams</publisher>
		<title>Cocoon: Developer's Handbook</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-cocoon" weight="0.8"/>; </p>
			</richtext>
		</annotation>
	</reference>
	<reference name="row01">
		<names type="author">
			<person>
				<givenname>Michael</givenname>
				<surname>Rowell</surname>
			</person>
		</names>
		<date value="2001-08"/>
		<address>Indianapolis, Indiana</address>
		<identifier type="isbn">0672319411</identifier>
		<publisher>Sams</publisher>
		<title>Understanding EAI: Enterprise Application Integration</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-eai" weight="0.8"/>; </p>
			</richtext>
		</annotation>
	</reference>
	<reference name="coo95">
		<names type="author">
			<person>
				<givenname>Alan</givenname>
				<surname>Cooper</surname>
			</person>
		</names>
		<date value="1995-08"/>
		<address>Boston, Massachusetts</address>
		<field type="bibtex:index">WWW, HCI, usability</field>
		<identifier type="isbn">1568843224</identifier>
		<publisher>IDG</publisher>
		<title>About Face: The Essentials of User Interface Design</title>
	</reference>
	<reference name="sie97">
		<names type="author">
			<person>
				<givenname>David</givenname>
				<surname>Siegel</surname>
			</person>
		</names>
		<date value="1997-10"/>
		<address>Indianapolis, Indiana</address>
		<edition>2nd</edition>
		<field type="bibtex:index">WWW, HTML, CSS</field>
		<identifier type="isbn">1568304331</identifier>
		<publisher>Hayden Books</publisher>
		<title>Creating Killer Web Sites</title>
	</reference>
	<reference name="web97">
		<names type="author">
			<person>
				<givenname>Timothy</givenname>
				<surname>Webster</surname>
			</person>
		</names>
		<date value="1997-06"/>
		<address>Indianapolis, Indiana</address>
		<identifier type="isbn">1568303637</identifier>
		<publisher>Hayden Books</publisher>
		<field type="bibtex:src">EW</field>
		<title>Web Designer's Guide to Graphics: PNG, GIF &amp; JPEG</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-png" weight="0.8"/>; <keywordref type="topic-gif" weight="0.8"/>; <keywordref type="topic-jpeg" weight="0.8"/>; </p>
			</richtext>
		</annotation>
	</reference>
	<reference name="cha95">
		<names type="author">
			<person>
				<givenname>D.</givenname>
				<surname>Chadwick</surname>
			</person>
		</names>
		<date value="1995"/>
		<address>London, UK</address>
		<identifier type="isbn">0412430207</identifier>
		<publisher>Chapman &amp; Hall</publisher>
		<title>Understanding X.500 — The Directory</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-x500" weight="0.8"/>; </p>
			</richtext>
		</annotation>
	</reference>
	<reference name="leo99">
		<names type="author">
			<person>
				<givenname>Alberto</givenname>
				<surname>Leon-Garcia</surname>
			</person>
			<person>
				<givenname>Indra</givenname>
				<surname>Widjaja</surname>
			</person>
		</names>
		<date value="1999-12"/>
		<address>New York, NY</address>
		<identifier type="isbn">0070228396</identifier>
		<publisher>McGraw-Hill</publisher>
		<title>Communication Networks: Fundamental Concepts and Key Architectures</title>
	</reference>
	<reference name="gor98">
		<names type="author">
			<person>
				<givenname>Walter J.</givenname>
				<surname>Goralski</surname>
			</person>
		</names>
		<date value="1998-03"/>
		<address>New York, NY</address>
		<identifier type="isbn">0070246793</identifier>
		<publisher>McGraw-Hill</publisher>
		<title>ADSL and DSL Technologies</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-dsl" weight="0.7"/>; (undefined keyword: xdsl); <keywordref type="topic-adsl" weight="0.7"/>; </p>
			</richtext>
		</annotation>
	</reference>
	<reference name="hec99">
		<names type="author">
			<person>
				<givenname>Howard</givenname>
				<surname>Hecht</surname>
			</person>
			<person>
				<givenname>John</givenname>
				<surname>Freeman</surname>
			</person>
			<person>
				<givenname>Marlis</givenname>
				<surname>Humphrey</surname>
			</person>
		</names>
		<date value="1999-03"/>
		<address>New York, NY</address>
		<identifier type="isbn">0070277354</identifier>
		<publisher>McGraw-Hill</publisher>
		<title>DSL: ADSL, RADSL, SDSL, HDSL, and VDSL</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-dsl" weight="0.7"/>; (undefined keyword: xdsl); <keywordref type="topic-adsl" weight="0.7"/>; (undefined keyword: radsl); <keywordref type="topic-sdsl" weight="0.7"/>; <keywordref type="topic-hdsl" weight="0.7"/>; <keywordref type="topic-vdsl" weight="0.7"/>; </p>
			</richtext>
		</annotation>
	</reference>
	<reference name="kor91">
		<names type="author">
			<person>
				<givenname>Henry F.</givenname>
				<surname>Korth</surname>
			</person>
			<person>
				<givenname>Abraham</givenname>
				<surname>Silberschatz</surname>
			</person>
		</names>
		<date value="1991"/>
		<address>New York, NY</address>
		<field type="bibtex:index">ERM, DBMS</field>
		<identifier type="isbn">0071008047</identifier>
		<publisher>McGraw-Hill</publisher>
		<title>Database System Concepts</title>
	</reference>
	<reference name="sil98">
		<names type="author">
			<person>
				<givenname>Abraham</givenname>
				<surname>Silberschatz</surname>
			</person>
			<person>
				<givenname>Henry F.</givenname>
				<surname>Korth</surname>
			</person>
			<person>
				<givenname>S.</givenname>
				<surname>Sudarshan</surname>
			</person>
		</names>
		<date value="1998-03"/>
		<address>New York, NY</address>
		<edition>3rd</edition>
		<field type="bibtex:index">ERM, DBMS</field>
		<identifier type="isbn">0071008047</identifier>
		<publisher>McGraw-Hill</publisher>
		<title>Database System Concepts</title>
		<associations>
			<xref type="updates" target="kor91"/>
		</associations>
	</reference>
	<reference name="kum95">
		<names type="author">
			<person>
				<givenname>Vinay</givenname>
				<surname>Kumar</surname>
			</person>
		</names>
		<date value="1995"/>
		<address>Indianapolis, Indiana</address>
		<field type="bibtex:index">mbone, multimedia</field>
		<identifier type="isbn">1562053973</identifier>
		<publisher>Macmillan Publishing</publisher>
		<title>Mbone: Interactive Multimedia on the Internet</title>
	</reference>
	<reference name="ada99">
		<names type="author">
			<person>
				<givenname>Carlisle</givenname>
				<surname>Adams</surname>
			</person>
			<person>
				<givenname>Steve</givenname>
				<surname>Lloyd</surname>
			</person>
		</names>
		<date value="1999-11"/>
		<address>Indianapolis, Indiana</address>
		<field type="bibtex:index">PKI, PKIX, X.509</field>
		<identifier type="isbn">157870166X</identifier>
		<publisher>Macmillan Publishing</publisher>
		<title>Understanding Public-Key Infrastructure: Concepts, Standards, and Deployment Considerations</title>
	</reference>
	<reference name="bau98">
		<names type="author">
			<person>
				<givenname>Michael</givenname>
				<surname>Baumgardt</surname>
			</person>
		</names>
		<date value="1998-04"/>
		<address>Berlin, Germany</address>
		<field type="bibtex:index">WWW, HTML, DHTML, CSS, JavaScript</field>
		<identifier type="isbn">354062662X</identifier>
		<publisher>Springer-Verlag</publisher>
		<field type="bibtex:src">EW</field>
		<title>Creative Web Design</title>
	</reference>
	<reference name="tra95">
		<names type="author">
			<person>
				<givenname>Brian</givenname>
				<surname>Travis</surname>
			</person>
			<person>
				<givenname>Dale</givenname>
				<surname>Waldt</surname>
			</person>
		</names>
		<date value="1995-12"/>
		<address>Berlin, Germany</address>
		<identifier type="isbn">3540577300</identifier>
		<publisher>Springer-Verlag</publisher>
		<field type="bibtex:src">EW</field>
		<title>The SGML Implementation Guide</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-sgml" weight="0.8"/>; </p>
			</richtext>
		</annotation>
	</reference>
	<reference name="san95">
		<names type="author">
			<person>
				<givenname>Adelino</givenname>
				<surname>Santos</surname>
			</person>
		</names>
		<date value="1995"/>
		<address>Berlin, Germany</address>
		<field type="bibtex:index">CoMEdiA, groupware, collaborative editing</field>
		<identifier type="isbn">3-540-60001-9</identifier>
		<publisher>Springer-Verlag</publisher>
		<field type="bibtex:src">Ethics: 764798</field>
		<title>Multimedia and Groupware for Editing</title>
	</reference>
	<reference name="gal96">
		<names type="author">
			<person>
				<givenname>Wilbert O.</givenname>
				<surname>Galitz</surname>
			</person>
		</names>
		<date value="1996-12"/>
		<address>Chichester, England</address>
		<identifier type="isbn">0471157554</identifier>
		<publisher>John Wiley &amp; Sons</publisher>
		<title>The Essential Guide to User Interface Design: An Introduction to GUI Design Principles and Techniques</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-gui" weight="0.8"/>; </p>
			</richtext>
		</annotation>
	</reference>
	<reference name="ghe97">
		<names type="author">
			<person>
				<givenname>Carlo</givenname>
				<surname>Ghezzi</surname>
			</person>
			<person>
				<givenname>Mehdi</givenname>
				<surname>Jazayeri</surname>
			</person>
		</names>
		<date value="1997-06"/>
		<address>Chichester, England</address>
		<edition>3rd</edition>
		<identifier type="isbn">0471104264</identifier>
		<publisher>John Wiley &amp; Sons</publisher>
		<title>Programming Language Concepts</title>
		<identifier type="uri">http://www.infosys.tuwien.ac.at/pl-book/</identifier>
	</reference>
	<reference name="wei97">
		<names type="author">
			<person>
				<givenname>Susan</givenname>
				<surname>Weinschenk</surname>
			</person>
			<person>
				<givenname>Pamela</givenname>
				<surname>Jamar</surname>
			</person>
			<person>
				<givenname>Sarah C.</givenname>
				<surname>Yeo</surname>
			</person>
		</names>
		<date value="1997-03"/>
		<address>Chichester, England</address>
		<identifier type="isbn">0471175498</identifier>
		<publisher>John Wiley &amp; Sons</publisher>
		<title>GUI Design Essentials</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-gui" weight="0.8"/>; </p>
			</richtext>
		</annotation>
	</reference>
	<reference name="ruh00">
		<names type="author">
			<person>
				<givenname>William A.</givenname>
				<surname>Ruh</surname>
			</person>
			<person>
				<givenname>Francis X.</givenname>
				<surname>Maginnis</surname>
			</person>
			<person>
				<givenname>William J.</givenname>
				<surname>Brown</surname>
			</person>
		</names>
		<date value="2000-10"/>
		<address>Chichester, England</address>
		<identifier type="isbn">0471376418</identifier>
		<publisher>John Wiley &amp; Sons</publisher>
		<title>Enterprise Application Integration: A Wiley Tech Brief</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-eai" weight="0.8"/>; </p>
			</richtext>
		</annotation>
	</reference>
	<reference name="low99">
		<names type="author">
			<person>
				<givenname>David</givenname>
				<surname>Lowe</surname>
			</person>
			<person>
				<givenname>Wendy</givenname>
				<surname>Hall</surname>
			</person>
		</names>
		<date value="1999-02"/>
		<address>Chichester, England</address>
		<field type="bibtex:index">WWW, hypermedia</field>
		<identifier type="isbn">0-471-98312-8</identifier>
		<publisher>John Wiley &amp; Sons</publisher>
		<series>Worldwide Series in Computer Science</series>
		<field type="bibtex:src">EW</field>
		<title>Hypermedia &amp; the Web: An Engineering Approach</title>
	</reference>
	<reference name="gra00">
		<names type="author">
			<person>
				<givenname>Ian S.</givenname>
				<surname>Graham</surname>
			</person>
		</names>
		<date value="2000-03"/>
		<address>New York, NY</address>
		<field type="bibtex:index">XHTML, CSS</field>
		<identifier type="isbn">0-471-37485-7</identifier>
		<publisher>John Wiley &amp; Sons</publisher>
		<title>XHTML 1.0 Language and Design Sourcebook: The Next Generation HTML</title>
	</reference>
	<reference name="rom99">
		<names type="author">
			<person>
				<givenname>Ed</givenname>
				<surname>Roman</surname>
			</person>
		</names>
		<date value="1999-09"/>
		<address>New York, NY</address>
		<identifier type="isbn">0471332291</identifier>
		<publisher>John Wiley &amp; Sons</publisher>
		<title>Mastering Enterprise JavaBeans and the Java 2 Platform, Enterprise Edition</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-j2ee" weight="0.8"/>; <keywordref type="topic-ejb" weight="0.8"/>; </p>
			</richtext>
		</annotation>
	</reference>
	<reference name="orf98">
		<names type="author">
			<person>
				<givenname>Robert</givenname>
				<surname>Orfali</surname>
			</person>
			<person>
				<givenname>Dan</givenname>
				<surname>Harkey</surname>
			</person>
		</names>
		<date value="1998-02"/>
		<address>New York, NY</address>
		<edition>2nd</edition>
		<field type="bibtex:index">WWW, Java, CORBA, IIOP</field>
		<identifier type="isbn">0471163511</identifier>
		<publisher>John Wiley &amp; Sons</publisher>
		<field type="bibtex:src">AA</field>
		<title>Client/Server Programming with Java and CORBA</title>
	</reference>
	<reference name="los99">
		<names type="author">
			<person>
				<givenname>Pete</givenname>
				<surname>Loshin</surname>
			</person>
		</names>
		<date value="1999-11"/>
		<address>New York, NY</address>
		<field type="bibtex:index">SMTP, IMAP, POP, MIME, PGP, iCalendar, vCard</field>
		<identifier type="isbn">0471345970</identifier>
		<publisher>John Wiley &amp; Sons</publisher>
		<title>Essential Email Standards: RFCs and Protocols Made Practical</title>
	</reference>
	<reference name="gos98">
		<names type="author">
			<person>
				<givenname>Anup K.</givenname>
				<surname>Ghosh</surname>
			</person>
		</names>
		<date value="1998-02"/>
		<address>New York, NY</address>
		<field type="bibtex:index">WWW, security</field>
		<identifier type="isbn">0471192236</identifier>
		<publisher>John Wiley &amp; Sons</publisher>
		<title>E-Commerce Security: Weak Links, Best Defenses</title>
	</reference>
	<reference name="sch95b">
		<names type="author">
			<person>
				<givenname>Bruce</givenname>
				<surname>Schneier</surname>
			</person>
		</names>
		<date value="1995-10"/>
		<address>New York, NY</address>
		<edition>2nd</edition>
		<field type="bibtex:index">cryptography</field>
		<identifier type="isbn">0471117099</identifier>
		<publisher>John Wiley &amp; Sons</publisher>
		<title>Applied Cryptography: Protocols, Algorithms, and Source Code in C</title>
	</reference>
	<reference name="sch00a">
		<names type="author">
			<person>
				<givenname>Bruce</givenname>
				<surname>Schneier</surname>
			</person>
		</names>
		<date value="2000-08"/>
		<address>New York, NY</address>
		<identifier type="isbn">0471253111</identifier>
		<publisher>John Wiley &amp; Sons</publisher>
		<title>Secrets &amp; Lies: Digital Security in a Networked World</title>
		<identifier type="uri" resourceType="text/html">http://www.schneier.com/book-sandl.html</identifier>
	</reference>
	<reference name="sch03c">
		<names type="author">
			<person>
				<givenname>Bruce</givenname>
				<surname>Schneier</surname>
			</person>
		</names>
		<date value="2003-09"/>
		<address>New York, NY</address>
		<identifier type="isbn">0387026207</identifier>
		<publisher>Copernicus</publisher>
		<title>Beyond Fear: Thinking Sensibly about Security in an Uncertain World</title>
		<identifier type="uri" resourceType="text/html">http://www.schneier.com/book-beyondfear.html</identifier>
	</reference>
	<reference name="fow02">
		<names type="author">
			<person>
				<givenname>Martin</givenname>
				<surname>Fowler</surname>
			</person>
		</names>
		<date value="2002-11"/>
		<address>Reading, Massachusetts</address>
		<identifier type="isbn">0321127420</identifier>
		<publisher>Addison Wesley</publisher>
		<title>Patterns of Enterprise Application Architecture</title>
	</reference>
	<reference name="fow99">
		<names type="author">
			<person>
				<givenname>Martin</givenname>
				<surname>Fowler</surname>
			</person>
			<person>
				<givenname>Kent</givenname>
				<surname>Beck</surname>
			</person>
			<person>
				<givenname>John</givenname>
				<surname>Brant</surname>
			</person>
			<person>
				<givenname>William</givenname>
				<surname>Opdyke</surname>
			</person>
			<person>
				<givenname>Don</givenname>
				<surname>Roberts</surname>
			</person>
		</names>
		<date value="1999-06"/>
		<address>Reading, Massachusetts</address>
		<identifier type="isbn">0201485672</identifier>
		<publisher>Addison Wesley</publisher>
		<title>Refactoring: Improving the Design of Existing Code</title>
	</reference>
	<reference name="tho96">
		<names type="author">
			<person>
				<givenname>Stephen A.</givenname>
				<surname>Thomas</surname>
			</person>
		</names>
		<date value="1996-01"/>
		<address>New York, NY</address>
		<field type="bibtex:index">IPng, RSVP, OSPF, RIP, TCP, UDP, DNS</field>
		<identifier type="isbn">1471130885</identifier>
		<publisher>John Wiley &amp; Sons</publisher>
		<field type="bibtex:src">DB</field>
		<title>IPng and the TCP/IP Protocols</title>
	</reference>
	<reference name="gra97">
		<names type="author">
			<person>
				<givenname>Ian S.</givenname>
				<surname>Graham</surname>
			</person>
		</names>
		<date value="1997-10"/>
		<address>New York, NY</address>
		<field type="bibtex:index">WWW, HTML, CSS</field>
		<identifier type="isbn">0471196649</identifier>
		<publisher>John Wiley &amp; Sons</publisher>
		<field type="bibtex:src">EW</field>
		<title>HTML Stylesheet Sourcebook</title>
	</reference>
	<reference name="hal96b">
		<names type="author">
			<person>
				<givenname>Wendy</givenname>
				<surname>Hall</surname>
			</person>
			<person>
				<givenname>Hugh C.</givenname>
				<surname>Davis</surname>
			</person>
			<person>
				<givenname>Gerard</givenname>
				<surname>Hutchings</surname>
			</person>
		</names>
		<date value="1996-05"/>
		<address>Boston, Massachusetts</address>
		<identifier type="isbn">0792396790</identifier>
		<publisher>Kluwer Academic Publishers</publisher>
		<title>Rethinking Hypermedia: The Microcosm Approach</title>
		<annotation>
			<richtext>
				<p>Keywords: (undefined keyword: microcosm); (undefined keyword: webcosm); </p>
			</richtext>
		</annotation>
	</reference>
	<reference name="der94">
		<names type="author">
			<person>
				<givenname>Steven J.</givenname>
				<surname>DeRose</surname>
			</person>
			<person>
				<givenname>David G.</givenname>
				<surname>Durand</surname>
			</person>
		</names>
		<date value="1994-05"/>
		<address>Boston, Massachusetts</address>
		<identifier type="isbn">0792394321</identifier>
		<publisher>Kluwer Academic Publishers</publisher>
		<title>Making Hypermedia Work: A User's Guide to HyTime</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-hytime" weight="0.9"/>; </p>
			</richtext>
		</annotation>
	</reference>
	<reference name="der97">
		<names type="author">
			<person>
				<givenname>Steven J.</givenname>
				<surname>DeRose</surname>
			</person>
		</names>
		<date value="1997-07"/>
		<address>Boston, Massachusetts</address>
		<identifier type="isbn">0792399439</identifier>
		<publisher>Kluwer Academic Publishers</publisher>
		<title>The SGML FAQ Book: Understanding the Foundation of HTML and XML</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-sgml" weight="0.8"/>; <keywordref type="topic-xml" weight="0.7"/>; <keywordref type="topic-html" weight="0.7"/>; </p>
			</richtext>
		</annotation>
	</reference>
	<reference name="del96">
		<names type="author">
			<person>
				<givenname>Luca</givenname>
				<surname>Delgrossi</surname>
			</person>
		</names>
		<date value="1996"/>
		<address>Boston, Massachusetts</address>
		<field type="bibtex:index">ST-II, RSVP</field>
		<identifier type="isbn">0792396693</identifier>
		<publisher>Kluwer Academic Publishers</publisher>
		<field type="bibtex:src">BS</field>
		<title>Design of Reservation Protocols for Multimedia Communication</title>
	</reference>
	<reference name="ste93">
		<names type="author">
			<person>
				<givenname>Douglas</givenname>
				<surname>Steedman</surname>
			</person>
		</names>
		<date value="1993"/>
		<address>Twickenham, UK</address>
		<identifier type="isbn">1871802067</identifier>
		<publisher>Technology Appraisals</publisher>
		<field type="bibtex:src">Ethics: 759952</field>
		<title>Abstract Syntax Notation One (ASN.1): The Tutorial and Reference</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-asn1" weight="0.8"/>; </p>
			</richtext>
		</annotation>
	</reference>
	<reference name="ste93b">
		<names type="author">
			<person>
				<givenname>Douglas</givenname>
				<surname>Steedman</surname>
			</person>
		</names>
		<date value="1993"/>
		<address>Twickenham, UK</address>
		<publisher>Technology Appraisals</publisher>
		<title>The Directory Standard and its Application</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-x500" weight="0.8"/>; </p>
			</richtext>
		</annotation>
	</reference>
	<reference name="wyb90">
		<names type="author">
			<person>
				<givenname>Dieter</givenname>
				<surname>Wybranietz</surname>
			</person>
		</names>
		<date value="1990"/>
		<address>Berlin, Germany</address>
		<identifier type="isbn">3540525513</identifier>
		<publisher>Springer-Verlag</publisher>
		<series>Informatik-Fachberichte</series>
		<field type="bibtex:src">Ethics: 714216:242</field>
		<title>Multicast-Kommunikation in Verteilten Systemen</title>
		<volume>242</volume>
	</reference>
	<reference name="alp98">
		<names type="author">
			<person>
				<givenname>Paul</givenname>
				<surname>Alpar</surname>
			</person>
		</names>
		<date value="1998"/>
		<address>Berlin, Germany</address>
		<edition>2nd</edition>
		<identifier type="isbn">3540644490</identifier>
		<publisher>Springer-Verlag</publisher>
		<title>Kommerzielle Nutzung des Internet</title>
	</reference>
	<reference name="bou00">
		<names type="author">
			<person>
				<givenname>Frank</givenname>
				<surname>Boumphrey</surname>
			</person>
			<person>
				<givenname>Cassandra</givenname>
				<surname>Greer</surname>
			</person>
			<person>
				<givenname>Dave</givenname>
				<surname>Raggett</surname>
			</person>
			<person>
				<givenname>Jenny</givenname>
				<surname>Raggett</surname>
			</person>
			<person>
				<givenname>Sebastian</givenname>
				<surname>Schnitzenbaumer</surname>
			</person>
			<person>
				<givenname>Ted</givenname>
				<surname>Wugofski</surname>
			</person>
		</names>
		<date value="2000-03"/>
		<address>Chicago, Illinois</address>
		<identifier type="isbn">1861003439</identifier>
		<publisher>Wrox Press</publisher>
		<title>Beginning XHTML</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-xhtml" weight="0.8"/>; </p>
			</richtext>
		</annotation>
	</reference>
	<reference name="ger05">
		<names type="author">
			<person>
				<givenname>Jason</givenname>
				<surname>Gerner</surname>
			</person>
			<person>
				<givenname>Morgan</givenname>
				<surname>Owens</surname>
			</person>
			<person>
				<givenname>Elizabeth</givenname>
				<surname>Naramore</surname>
			</person>
			<person>
				<givenname>Jeremy</givenname>
				<surname>Stolz</surname>
			</person>
		</names>
		<date value="2005-12"/>
		<address>Chicago, Illinois</address>
		<identifier type="isbn">076459723X</identifier>
		<publisher>Wrox Press</publisher>
		<title>Professional LAMP: Linux, Apache, MySQL and PHP Web Development</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-lamp" weight="0.9"/>; <keywordref type="topic-linux" weight="0.8"/>; <keywordref type="topic-apachehttp" weight="0.8"/>; <keywordref type="topic-mysql" weight="0.8"/>; <keywordref type="topic-php" weight="0.8"/>; </p>
			</richtext>
		</annotation>
		<identifier type="uri" resourceType="text/html">http://www.wrox.com/WileyCDA/WroxTitle/productCd-076459723X.html</identifier>
	</reference>
	<reference name="spe99">
		<names type="author">
			<person>
				<givenname>Paul</givenname>
				<surname>Spencer</surname>
			</person>
		</names>
		<date value="1999-04"/>
		<address>Chicago, Illinois</address>
		<identifier type="isbn">1861002289</identifier>
		<publisher>Wrox Press</publisher>
		<title>XML Design and Implementation</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-xml" weight="0.8"/>; </p>
			</richtext>
		</annotation>
	</reference>
	<reference name="wai99">
		<names type="author">
			<person>
				<givenname>Peter</givenname>
				<surname>Wainwright</surname>
			</person>
		</names>
		<date value="1999-11"/>
		<address>Chicago, Illinois</address>
		<identifier type="isbn">1861003021</identifier>
		<publisher>Wrox Press</publisher>
		<title>Professional Apache</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-apachehttp" weight="0.8"/>; </p>
			</richtext>
		</annotation>
	</reference>
	<reference name="kay00">
		<names type="author">
			<person>
				<givenname>Michael</givenname>
				<surname>Kay</surname>
			</person>
		</names>
		<date value="2000-04"/>
		<address>Chicago, Illinois</address>
		<identifier type="isbn">1861003129</identifier>
		<publisher>Wrox Press</publisher>
		<title>XSLT Programmer's Reference</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-xslt1" weight="0.8"/>; <keywordref type="topic-xpath1" weight="0.7"/>; </p>
			</richtext>
		</annotation>
	</reference>
	<reference name="kay01">
		<names type="author">
			<person>
				<givenname>Michael</givenname>
				<surname>Kay</surname>
			</person>
		</names>
		<date value="2001-03"/>
		<address>Chicago, Illinois</address>
		<identifier type="isbn">1861005067</identifier>
		<publisher>Wrox Press</publisher>
		<title>XSLT 1.1 Programmer's Reference</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-xslt1" weight="0.8"/>; <keywordref type="topic-xpath1" weight="0.7"/>; </p>
			</richtext>
		</annotation>
		<associations>
			<xref type="updates" target="kay00"/>
		</associations>
	</reference>
	<reference name="wes01">
		<names type="author">
			<person>
				<givenname>Duane</givenname>
				<surname>Wessels</surname>
			</person>
		</names>
		<date value="2001-06"/>
		<address>Sebastopol, California</address>
		<identifier type="isbn">156592536X</identifier>
		<publisher>O'Reilly &amp; Associates</publisher>
		<title>Web Caching</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-cache" weight="0.9"/>; </p>
			</richtext>
		</annotation>
		<identifier type="uri">http://www.oreilly.com/catalog/webcaching/</identifier>
	</reference>
	<reference name="hol01a">
		<names type="author">
			<person>
				<givenname>G. Ken</givenname>
				<surname>Holman</surname>
			</person>
		</names>
		<date value="2001-12"/>
		<address>Sebastopol, California</address>
		<identifier type="isbn">0130651966</identifier>
		<publisher>O'Reilly &amp; Associates</publisher>
		<title>Definitive XSLT and XPath</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-xslt1" weight="0.8"/>; <keywordref type="topic-xpath1" weight="0.7"/>; </p>
			</richtext>
		</annotation>
	</reference>
	<reference name="hol01b">
		<names type="author">
			<person>
				<givenname>Steven</givenname>
				<surname>Holzner</surname>
			</person>
		</names>
		<date value="2001-07"/>
		<address>Indianapolis, Indiana</address>
		<identifier type="isbn">0735711364</identifier>
		<publisher>New Riders</publisher>
		<title>Inside XSLT</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-xslt1" weight="0.8"/>; <keywordref type="topic-xpath1" weight="0.7"/>; </p>
			</richtext>
		</annotation>
	</reference>
	<reference name="zie02">
		<names type="author">
			<person>
				<givenname>Carsten</givenname>
				<surname>Ziegeler</surname>
			</person>
			<person>
				<givenname>Matthew</givenname>
				<surname>Langham</surname>
			</person>
		</names>
		<date value="2002-07"/>
		<address>Indianapolis, Indiana</address>
		<identifier type="isbn">0735712352</identifier>
		<publisher>New Riders</publisher>
		<title>Cocoon: Building XML Applications</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-cocoon" weight="0.8"/>; </p>
			</richtext>
		</annotation>
	</reference>
	<reference name="hje01">
		<names type="author">
			<person>
				<givenname>Johan</givenname>
				<surname>Hjelm</surname>
			</person>
			<person>
				<givenname>Peter</givenname>
				<surname>Stark</surname>
			</person>
		</names>
		<date value="2001-09"/>
		<address>New York, NY</address>
		<identifier type="isbn">0471406031</identifier>
		<publisher>John Wiley &amp; Sons</publisher>
		<series>Professional Developer's Guide Series</series>
		<title>XSLT: The Ultimate Guide to Transforming Web Data</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-xslt1" weight="0.8"/>; <keywordref type="topic-xpath1" weight="0.7"/>; </p>
			</richtext>
		</annotation>
	</reference>
	<reference name="ten01">
		<names type="author">
			<person>
				<givenname>Jeni</givenname>
				<surname>Tennison</surname>
			</person>
		</names>
		<date value="2001-09"/>
		<address>New York, NY</address>
		<identifier type="isbn">0764547763</identifier>
		<publisher>John Wiley &amp; Sons</publisher>
		<title>XSLT and XPath On The Edge</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-xslt1" weight="0.8"/>; <keywordref type="topic-xpath1" weight="0.8"/>; </p>
			</richtext>
		</annotation>
	</reference>
	<reference name="ten02">
		<names type="author">
			<person>
				<givenname>Jeni</givenname>
				<surname>Tennison</surname>
			</person>
		</names>
		<date value="2002-05"/>
		<address>Chicago, Illinois</address>
		<identifier type="isbn">1861005946</identifier>
		<publisher>Wrox Press</publisher>
		<title>Beginning XSLT</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-xslt1" weight="0.8"/>; <keywordref type="topic-xpath1" weight="0.7"/>; </p>
			</richtext>
		</annotation>
	</reference>
	<reference name="tid01">
		<names type="author">
			<person>
				<givenname>Doug</givenname>
				<surname>Tidwell</surname>
			</person>
		</names>
		<date value="2001-08"/>
		<address>Sebastopol, California</address>
		<identifier type="isbn">0596000537</identifier>
		<publisher>O'Reilly &amp; Associates</publisher>
		<title>XSLT</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-xslt1" weight="0.8"/>; <keywordref type="topic-xpath1" weight="0.7"/>; </p>
			</richtext>
		</annotation>
	</reference>
	<reference name="wal01">
		<names type="author">
			<person>
				<givenname>Priscilla</givenname>
				<surname>Walmsley</surname>
			</person>
		</names>
		<date value="2001-12"/>
		<address>Englewood Cliffs, New Jersey</address>
		<identifier type="isbn">0130655678</identifier>
		<publisher>Prentice-Hall</publisher>
		<title>Definitive XML Schema</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-xmlschema" weight="0.8"/>; </p>
			</richtext>
		</annotation>
	</reference>
	<reference name="bin02">
		<names type="author">
			<person>
				<givenname>Cliff</givenname>
				<surname>Binstock</surname>
			</person>
			<person>
				<givenname>David</givenname>
				<surname>Peterson</surname>
			</person>
			<person>
				<givenname>Mitchell</givenname>
				<surname>Smith</surname>
			</person>
			<person>
				<givenname>Mike</givenname>
				<surname>Wooding</surname>
			</person>
			<person>
				<givenname>Chris</givenname>
				<surname>Dix</surname>
			</person>
			<person>
				<givenname>Chris</givenname>
				<surname>Galtenberg</surname>
			</person>
		</names>
		<date value="2002-09"/>
		<address>Reading, Massachusetts</address>
		<identifier type="isbn">0672323745</identifier>
		<publisher>Addison Wesley</publisher>
		<title>The XML Schema Complete Reference</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-xmlschema" weight="0.8"/>; </p>
			</richtext>
		</annotation>
	</reference>
	<reference name="vli02c">
		<names type="author">
			<person>
				<givenname>Eric</givenname>
				<surname link="van der">Vlist</surname>
			</person>
		</names>
		<date value="2002-06"/>
		<address>Sebastopol, California</address>
		<identifier type="isbn">0596002521</identifier>
		<publisher>O'Reilly &amp; Associates</publisher>
		<title>XML Schema</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-xmlschema" weight="0.8"/>; </p>
			</richtext>
		</annotation>
	</reference>
	<reference name="dor99">
		<names type="author">
			<person>
				<givenname>Naganand</givenname>
				<surname>Doraswamy</surname>
			</person>
			<person>
				<givenname>Dan</givenname>
				<surname>Harkins</surname>
			</person>
		</names>
		<date value="1999-07"/>
		<address>Englewood Cliffs, New Jersey</address>
		<identifier type="isbn">0130118982</identifier>
		<publisher>Prentice-Hall</publisher>
		<series>Internet Infrastructure Series</series>
		<title>IPSec: The New Security Standard for the Internet, Intranets and Virtual Private Networks</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-ipsec" weight="0.8"/>; </p>
			</richtext>
		</annotation>
	</reference>
	<reference name="sta00">
		<names type="author">
			<person>
				<givenname>William</givenname>
				<surname>Stallings</surname>
			</person>
		</names>
		<date value="2000-04"/>
		<address>Englewood Cliffs, New Jersey</address>
		<field type="bibtex:index">security</field>
		<identifier type="isbn">0130160938</identifier>
		<publisher>Prentice-Hall</publisher>
		<title>Network Security Essentials: Applications and Standards</title>
	</reference>
	<reference name="sta96">
		<names type="author">
			<person>
				<givenname>William</givenname>
				<surname>Stallings</surname>
			</person>
		</names>
		<date value="1996-08"/>
		<address>Englewood Cliffs, New Jersey</address>
		<edition>5th</edition>
		<publisher>Prentice-Hall</publisher>
		<title>Data and Computer Communications</title>
	</reference>
	<reference name="sta99b">
		<names type="author">
			<person>
				<givenname>William</givenname>
				<surname>Stallings</surname>
			</person>
		</names>
		<date value="1999-09"/>
		<address>Englewood Cliffs, New Jersey</address>
		<edition>6th</edition>
		<identifier type="isbn">0130843709</identifier>
		<publisher>Prentice-Hall</publisher>
		<title>Data and Computer Communications</title>
		<associations>
			<xref type="updates" target="sta96"/>
		</associations>
	</reference>
	<reference name="sta98">
		<names type="author">
			<person>
				<givenname>William</givenname>
				<surname>Stallings</surname>
			</person>
		</names>
		<date value="1998-07"/>
		<address>Upper Saddle River, New Jersey</address>
		<edition>2nd</edition>
		<field type="bibtex:index">security, Kerberos, X.509, PGP, S/MIME, IPSec, SSL, TLS, SET</field>
		<identifier type="isbn">0138690170</identifier>
		<publisher>Prentice-Hall</publisher>
		<title>Cryptography and Network Security: Principles and Practice</title>
	</reference>
	<reference name="tan96">
		<names type="author">
			<person>
				<givenname>Andrew S.</givenname>
				<surname>Tanenbaum</surname>
			</person>
		</names>
		<date value="1996-03"/>
		<address>Englewood Cliffs, New Jersey</address>
		<edition>3rd</edition>
		<publisher>Prentice-Hall</publisher>
		<title>Computer Networks</title>
	</reference>
	<reference name="flu95">
		<names type="author">
			<person>
				<givenname>François</givenname>
				<surname>Fluckiger</surname>
			</person>
		</names>
		<date value="1995"/>
		<address>London, UK</address>
		<field type="bibtex:index">multimedia, networks</field>
		<identifier type="isbn">0131909924</identifier>
		<publisher>Prentice-Hall</publisher>
		<field type="bibtex:src">BS</field>
		<title>Understanding Networked Multimedia: Applications and Technology</title>
	</reference>
	<reference name="bor90">
		<names type="author">
			<person>
				<givenname>Nathaniel S.</givenname>
				<surname>Borenstein</surname>
			</person>
		</names>
		<date value="1990"/>
		<address>Englewood Cliffs, New Jersey</address>
		<field type="bibtex:index">multimedia, ATK</field>
		<identifier type="isbn">0130366331</identifier>
		<publisher>Prentice-Hall</publisher>
		<field type="bibtex:src">EW</field>
		<title>Multimedia Applications Development with the Andrew Toolkit</title>
	</reference>
	<reference name="atm93">
		<names type="author">
			<name>ATM Forum</name>
		</names>
		<date value="1993"/>
		<address>Englewood Cliffs, New Jersey</address>
		<field type="bibtex:index">ATM, UNI 3.0</field>
		<identifier type="isbn">0132258633</identifier>
		<publisher>Prentice-Hall</publisher>
		<field type="bibtex:src">Ethics: 759018</field>
		<title>ATM User-Network Interface Specification Version 3.0</title>
	</reference>
	<reference name="atm95">
		<names type="author">
			<name>ATM Forum</name>
		</names>
		<date value="1995"/>
		<address>Englewood Cliffs, New Jersey</address>
		<field type="bibtex:index">ATM, UNI 3.1</field>
		<identifier type="isbn">013393828X</identifier>
		<publisher>Prentice-Hall</publisher>
		<title>ATM User-Network Interface Specification Version 3.1</title>
	</reference>
	<reference name="jai90">
		<names type="author">
			<person>
				<givenname>Bijendra N.</givenname>
				<surname>Jain</surname>
			</person>
			<person>
				<givenname>Ashok K.</givenname>
				<surname>Agrawala</surname>
			</person>
		</names>
		<date value="1990"/>
		<address>Amsterdam, Netherlands</address>
		<identifier type="isbn">0444884904</identifier>
		<publisher>Elsevier</publisher>
		<title>Open Systems Interconnection: Its Architecture and Protocols</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-osi" weight="0.9"/>; </p>
			</richtext>
		</annotation>
	</reference>
	<reference name="cer02">
		<names type="author">
			<person>
				<givenname>Stefano</givenname>
				<surname>Ceri</surname>
			</person>
			<person>
				<givenname>Piero</givenname>
				<surname>Fraternali</surname>
			</person>
			<person>
				<givenname>Aldo</givenname>
				<surname>Bongio</surname>
			</person>
			<person>
				<givenname>Marco</givenname>
				<surname>Brambilla</surname>
			</person>
			<person>
				<givenname>Sara</givenname>
				<surname>Comai</surname>
			</person>
			<person>
				<givenname>Maristella</givenname>
				<surname>Matera</surname>
			</person>
		</names>
		<date value="2002-12"/>
		<address>Amsterdam, Netherlands</address>
		<identifier type="isbn">1558608435</identifier>
		<publisher>Elsevier</publisher>
		<title>Designing Data-Intensive Web Applications</title>
		<annotation>
			<richtext>
				<p>Keywords: (undefined keyword: webml); <keywordref type="topic-uml" weight="0.8"/>; </p>
			</richtext>
		</annotation>
	</reference>
	<reference name="wil91">
		<names type="author">
			<person>
				<givenname>Paul</givenname>
				<surname>Wilson</surname>
			</person>
		</names>
		<date value="1991"/>
		<address>Oxford, UK</address>
		<identifier type="isbn">1871516269</identifier>
		<publisher>intellect</publisher>
		<field type="bibtex:src">HaL</field>
		<title>Computer-Supported Cooperative Work</title>
	</reference>
	<reference name="osf92">
		<names type="author">
			<name>Open Software Foundation</name>
		</names>
		<date value="1992-07"/>
		<address>Englewood Cliffs, New Jersey</address>
		<identifier type="isbn">0134906241</identifier>
		<publisher>Prentice-Hall</publisher>
		<field type="bibtex:src">AA</field>
		<title>Introduction to OSF DCE</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-dce"/>; </p>
			</richtext>
		</annotation>
	</reference>
	<reference name="cha99">
		<names type="author">
			<person>
				<givenname>Steven</givenname>
				<surname>Champeon</surname>
			</person>
			<person>
				<givenname>David S.</givenname>
				<surname>Fox</surname>
			</person>
		</names>
		<date value="1999-05"/>
		<address>Foster City, California</address>
		<identifier type="isbn">0764532677</identifier>
		<publisher>M&amp;T Books</publisher>
		<title>Building Dynamic HTML GUIs</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-dhtml" weight="0.8"/>; <keywordref type="topic-gui" weight="0.8"/>; </p>
			</richtext>
		</annotation>
	</reference>
	<reference name="ros01">
		<names type="author">
			<person>
				<givenname>Bill</givenname>
				<surname>Rosenblatt</surname>
			</person>
			<person>
				<givenname>Bill</givenname>
				<surname>Trippe</surname>
			</person>
			<person>
				<givenname>Stephen</givenname>
				<surname>Mooney</surname>
			</person>
		</names>
		<date value="2001-11"/>
		<address>New York, NY</address>
		<identifier type="isbn">0764548891</identifier>
		<publisher>M&amp;T Books</publisher>
		<title>Digital Rights Management: Business and Technology</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-drm" weight="0.9"/>; </p>
			</richtext>
		</annotation>
	</reference>
	<reference name="ros98">
		<names type="author">
			<person>
				<givenname>Louis</givenname>
				<surname>Rosenfeld</surname>
			</person>
			<person>
				<givenname>Peter</givenname>
				<surname>Morville</surname>
			</person>
		</names>
		<date value="1998-03"/>
		<address>Sebastopol, California</address>
		<field type="bibtex:index">WWW</field>
		<identifier type="isbn">1565922824</identifier>
		<publisher>O'Reilly &amp; Associates</publisher>
		<title>Information Architecture for the World Wide Web</title>
	</reference>
	<reference name="cha99b">
		<names type="author">
			<person>
				<givenname>Robert J.</givenname>
				<surname>Chassell</surname>
			</person>
			<person>
				<givenname>Richard M.</givenname>
				<surname>Stallman</surname>
			</person>
		</names>
		<date value="1999-09"/>
		<address>Boston, Massachusetts</address>
		<identifier type="isbn">1-882114-67-1</identifier>
		<publisher>GNU Press</publisher>
		<title>Texinfo: The GNU Documentation Format</title>
		<annotation>
			<richtext>
				<p>Keywords: (undefined keyword: texinfo); </p>
			</richtext>
		</annotation>
		<identifier type="uri" resourceType="text/html">http://www.gnupress.org/book9.html</identifier>
	</reference>
	<reference name="eff98">
		<names type="author">
			<name>Electronic Frontier Foundation</name>
		</names>
		<date value="1998-05"/>
		<address>Sebastopol, California</address>
		<identifier type="isbn">1565925203</identifier>
		<publisher>O'Reilly &amp; Associates</publisher>
		<title>Cracking DES: Secrets of Encryption Research, Wiretap Politics &amp; Chip Design</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-des" weight="0.9"/>; </p>
			</richtext>
		</annotation>
	</reference>
	<reference name="fri97">
		<names type="author">
			<person>
				<givenname>Jeffrey E. F.</givenname>
				<surname>Friedl</surname>
			</person>
		</names>
		<date value="1997-01"/>
		<address>Sebastopol, California</address>
		<field type="bibtex:index">regular expressions</field>
		<identifier type="isbn">1565922573</identifier>
		<publisher>O'Reilly &amp; Associates</publisher>
		<title>Mastering Regular Expressions</title>
	</reference>
	<reference name="won00">
		<names type="author">
			<person>
				<givenname>Clinton</givenname>
				<surname>Wong</surname>
			</person>
		</names>
		<date value="2000-05"/>
		<address>Sebastopol, California</address>
		<field type="bibtex:index">HTTP</field>
		<identifier type="isbn">1565928628</identifier>
		<publisher>O'Reilly &amp; Associates</publisher>
		<title>HTTP Pocket Reference</title>
	</reference>
	<reference name="hal00a">
		<names type="author">
			<person>
				<givenname>Eric</givenname>
				<surname>Hall</surname>
			</person>
			<person>
				<givenname>Vinton G.</givenname>
				<surname>Cerf</surname>
			</person>
		</names>
		<date value="2000-02"/>
		<address>Sebastopol, California</address>
		<identifier type="isbn">1565925726</identifier>
		<publisher>O'Reilly &amp; Associates</publisher>
		<title>Internet Core Protocols: The Definitive Guide</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-ip" weight="0.8"/>; <keywordref type="topic-tcp" weight="0.8"/>; <keywordref type="topic-udp" weight="0.8"/>; </p>
			</richtext>
		</annotation>
	</reference>
	<reference name="hal00b">
		<names type="author">
			<person>
				<givenname>Eric</givenname>
				<surname>Hall</surname>
			</person>
			<person>
				<givenname>Mike</givenname>
				<surname>Loukides</surname>
			</person>
		</names>
		<date value="2000-10"/>
		<address>Sebastopol, California</address>
		<identifier type="isbn">1565926064</identifier>
		<publisher>O'Reilly &amp; Associates</publisher>
		<title>Internet Application Protocols: The Definitive Guide</title>
	</reference>
	<reference name="wal99">
		<names type="author">
			<person>
				<givenname>Norman</givenname>
				<surname>Walsh</surname>
			</person>
			<person>
				<givenname>Leonard</givenname>
				<surname>Muellner</surname>
			</person>
		</names>
		<date value="1999-07"/>
		<address>Sebastopol, California</address>
		<identifier type="isbn">1565925807</identifier>
		<publisher>O'Reilly &amp; Associates</publisher>
		<title>DocBook: The Definitive Guide</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-docbook"/>; </p>
			</richtext>
		</annotation>
		<identifier type="uri">http://www.docbook.org/</identifier>
		<identifier type="uri" resourceType="text/html">http://www.oreilly.com/catalog/docbook/chapter/book/docbook.html</identifier>
	</reference>
	<reference name="goo98">
		<names type="author">
			<person>
				<givenname>Danny</givenname>
				<surname>Goodman</surname>
			</person>
		</names>
		<date value="1998-07"/>
		<address>Sebastopol, California</address>
		<field type="bibtex:index">DHTML</field>
		<publisher>O'Reilly &amp; Associates</publisher>
		<title>Dynamic HTML: The Definitive Reference</title>
	</reference>
	<reference name="spe98">
		<names type="author">
			<person>
				<givenname>Henry</givenname>
				<surname>Spencer</surname>
			</person>
			<person>
				<givenname>David</givenname>
				<surname>Lawrence</surname>
			</person>
		</names>
		<date value="1998-01"/>
		<address>Sebastopol, California</address>
		<field type="bibtex:index">usenet</field>
		<publisher>O'Reilly &amp; Associates</publisher>
		<title>Managing Usenet</title>
	</reference>
	<reference name="ros92">
		<names type="author">
			<person>
				<givenname>Ward</givenname>
				<surname>Rosenberry</surname>
			</person>
			<person>
				<givenname>David</givenname>
				<surname>Kenney</surname>
			</person>
			<person>
				<givenname>Gerry</givenname>
				<surname>Fisher</surname>
			</person>
		</names>
		<date value="1992-09"/>
		<address>Sebastopol, California</address>
		<identifier type="isbn">1565920058</identifier>
		<publisher>O'Reilly &amp; Associates</publisher>
		<field type="bibtex:src">EW</field>
		<title>Understanding DCE</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-dce"/>; </p>
			</richtext>
		</annotation>
	</reference>
	<reference name="sch97b">
		<names type="author">
			<person>
				<givenname>Randal L.</givenname>
				<surname>Schwartz</surname>
			</person>
			<person>
				<givenname>Tom</givenname>
				<surname>Christiansen</surname>
			</person>
		</names>
		<date value="1997-07"/>
		<address>Sebastopol, California</address>
		<field type="bibtex:index">Perl</field>
		<identifier type="isbn">1565922840</identifier>
		<publisher>O'Reilly &amp; Associates</publisher>
		<title>Learning Perl</title>
	</reference>
	<reference name="wal96">
		<names type="author">
			<person>
				<givenname>Larry</givenname>
				<surname>Wall</surname>
			</person>
			<person>
				<givenname>Tom</givenname>
				<surname>Christiansen</surname>
			</person>
			<person>
				<givenname>Randal L.</givenname>
				<surname>Schwartz</surname>
			</person>
		</names>
		<date value="1996-09"/>
		<address>Sebastopol, California</address>
		<field type="bibtex:index">Perl</field>
		<identifier type="isbn">1565921496</identifier>
		<publisher>O'Reilly &amp; Associates</publisher>
		<title>Programming Perl</title>
	</reference>
	<reference name="wal00">
		<names type="author">
			<person>
				<givenname>Larry</givenname>
				<surname>Wall</surname>
			</person>
			<person>
				<givenname>Tom</givenname>
				<surname>Christiansen</surname>
			</person>
			<person>
				<givenname>Jon</givenname>
				<surname>Orwant</surname>
			</person>
		</names>
		<date value="2000-07"/>
		<address>Sebastopol, California</address>
		<edition>3rd</edition>
		<field type="bibtex:index">Perl</field>
		<identifier type="isbn">0596000278</identifier>
		<publisher>O'Reilly &amp; Associates</publisher>
		<title>Programming Perl</title>
		<associations>
			<xref type="updates" target="wal96"/>
		</associations>
	</reference>
	<reference name="lut96">
		<names type="author">
			<person>
				<givenname>Mark</givenname>
				<surname>Lutz</surname>
			</person>
		</names>
		<date value="1996-10"/>
		<address>Sebastopol, California</address>
		<identifier type="isbn">1565921976</identifier>
		<publisher>O'Reilly &amp; Associates</publisher>
		<title>Programming Python</title>
	</reference>
	<reference name="lau97">
		<names type="author">
			<person>
				<givenname>Ben</givenname>
				<surname>Laurie</surname>
			</person>
			<person>
				<givenname>Peter</givenname>
				<surname>Laurie</surname>
			</person>
		</names>
		<date value="1997-03"/>
		<address>Sebastopol, California</address>
		<field type="bibtex:index">apache</field>
		<identifier type="isbn">1-56592-250-6</identifier>
		<publisher>O'Reilly &amp; Associates</publisher>
		<field type="bibtex:src">EW</field>
		<title>Apache: The Definitive Guide</title>
	</reference>
	<reference name="lau99">
		<names type="author">
			<person>
				<givenname>Ben</givenname>
				<surname>Laurie</surname>
			</person>
			<person>
				<givenname>Peter</givenname>
				<surname>Laurie</surname>
			</person>
			<person>
				<givenname>Robert</givenname>
				<surname>Denn</surname>
			</person>
		</names>
		<date value="1999-02"/>
		<address>Sebastopol, California</address>
		<edition>2nd</edition>
		<field type="bibtex:index">apache</field>
		<identifier type="isbn">1-56592-528-9</identifier>
		<publisher>O'Reilly &amp; Associates</publisher>
		<title>Apache: The Definitive Guide</title>
		<associations>
			<xref type="updates" target="lau97"/>
		</associations>
	</reference>
	<reference name="con02">
		<names type="author">
			<person>
				<givenname>Jim</givenname>
				<surname>Conallen</surname>
			</person>
		</names>
		<date value="2002-10"/>
		<address>Reading, Massachusetts</address>
		<edition>2nd</edition>
		<identifier type="isbn">0201730383</identifier>
		<publisher>Addison Wesley</publisher>
		<title>Building Web Applications with UML</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-uml" weight="0.8"/>; </p>
			</richtext>
		</annotation>
	</reference>
	<reference name="ste97">
		<names type="author">
			<person>
				<givenname>Lincoln D.</givenname>
				<surname>Stein</surname>
			</person>
			<person>
				<givenname>Clinton</givenname>
				<surname>Wong</surname>
			</person>
			<person>
				<givenname>Shishir</givenname>
				<surname>Gundavaram</surname>
			</person>
		</names>
		<date value="1997-05"/>
		<address>Sebastopol, California</address>
		<identifier type="isbn">1-56592-265-4</identifier>
		<publisher>O'Reilly &amp; Associates</publisher>
		<title>Scripting Languages: Automating the Web</title>
	</reference>
	<reference name="alb92">
		<names type="author">
			<person>
				<givenname>Paul</givenname>
				<surname>Albitz</surname>
			</person>
			<person>
				<givenname>Cricket</givenname>
				<surname>Liu</surname>
			</person>
		</names>
		<date value="1992-01"/>
		<address>Sebastopol, California</address>
		<identifier type="isbn">1-56592-010-4</identifier>
		<publisher>O'Reilly &amp; Associates</publisher>
		<field type="bibtex:src">DD, AA</field>
		<title>DNS and BIND</title>
	</reference>
	<reference name="liu98">
		<names type="author">
			<person>
				<givenname>Cricket</givenname>
				<surname>Liu</surname>
			</person>
			<person>
				<givenname>Paul</givenname>
				<surname>Albitz</surname>
			</person>
			<person>
				<givenname>Mike</givenname>
				<surname>Loukides</surname>
			</person>
		</names>
		<date value="1998-09"/>
		<address>Sebastopol, California</address>
		<edition>3rd</edition>
		<identifier type="isbn">1-56592-512-2</identifier>
		<publisher>O'Reilly &amp; Associates</publisher>
		<title>DNS and BIND</title>
	</reference>
	<reference name="gun96">
		<names type="author">
			<person>
				<givenname>Shishir</givenname>
				<surname>Gundavaram</surname>
			</person>
		</names>
		<date value="1996-04"/>
		<address>Sebastopol, California</address>
		<field type="bibtex:index">CGI, Perl</field>
		<identifier type="isbn">1-56592-168-2</identifier>
		<publisher>O'Reilly &amp; Associates</publisher>
		<field type="bibtex:src">EW</field>
		<title>CGI Programming on the World Wide Web</title>
	</reference>
	<reference name="gue00">
		<names type="author">
			<person>
				<givenname>Scott</givenname>
				<surname>Guelich</surname>
			</person>
			<person>
				<givenname>Shishir</givenname>
				<surname>Gundavaram</surname>
			</person>
			<person>
				<givenname>Gunther</givenname>
				<surname>Birznieks</surname>
			</person>
		</names>
		<date value="2000-07"/>
		<address>Sebastopol, California</address>
		<edition>2nd</edition>
		<field type="bibtex:index">CGI, Perl</field>
		<identifier type="isbn">1565924193</identifier>
		<publisher>O'Reilly &amp; Associates</publisher>
		<title>CGI Programming with Perl</title>
		<associations>
			<xref type="updates" target="gun96"/>
		</associations>
	</reference>
	<reference name="bar91">
		<names type="author">
			<person>
				<givenname>John. A.</givenname>
				<surname>Barry</surname>
			</person>
		</names>
		<date value="1991"/>
		<address>Cambridge, Massachusetts</address>
		<identifier type="isbn">0262023334</identifier>
		<publisher>The MIT Press</publisher>
		<field type="bibtex:src">EW</field>
		<title>Technobabble</title>
	</reference>
	<reference name="har93">
		<names type="author">
			<person>
				<givenname>Brian</givenname>
				<surname>Harvey</surname>
			</person>
			<person>
				<givenname>Matthew</givenname>
				<surname>Wright</surname>
			</person>
		</names>
		<date value="1993-12"/>
		<address>Cambridge, Massachusetts</address>
		<identifier type="isbn">0262082268</identifier>
		<publisher>The MIT Press</publisher>
		<title>Simply Scheme: Introducing Computer Science</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-scheme" weight="0.8"/>; </p>
			</richtext>
		</annotation>
	</reference>
	<reference name="har99">
		<names type="author">
			<person>
				<givenname>Brian</givenname>
				<surname>Harvey</surname>
			</person>
			<person>
				<givenname>Matthew</givenname>
				<surname>Wright</surname>
			</person>
		</names>
		<date value="1999-07"/>
		<address>Cambridge, Massachusetts</address>
		<edition>2nd</edition>
		<identifier type="isbn">0262082810</identifier>
		<publisher>The MIT Press</publisher>
		<title>Simply Scheme: Introducing Computer Science</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-scheme" weight="0.8"/>; </p>
			</richtext>
		</annotation>
		<associations>
			<xref type="updates" target="har93"/>
		</associations>
	</reference>
	<reference name="abe96">
		<names type="author">
			<person>
				<givenname>Harold</givenname>
				<surname>Abelson</surname>
			</person>
			<person>
				<givenname>Gerald Jay</givenname>
				<surname>Sussman</surname>
			</person>
		</names>
		<date value="1996-07"/>
		<address>Cambridge, Massachusetts</address>
		<edition>2nd</edition>
		<identifier type="isbn">0262011530</identifier>
		<publisher>The MIT Press</publisher>
		<title>Structure and Interpretation of Computer Programs</title>
		<identifier type="uri">http://mitpress.mit.edu/sicp/</identifier>
	</reference>
	<reference name="glu05a">
		<names type="author">
			<person>
				<givenname>Robert J.</givenname>
				<surname>Glushko</surname>
			</person>
			<person>
				<givenname>Tim</givenname>
				<surname>McGrath</surname>
			</person>
		</names>
		<date value="2005-08"/>
		<abstract>
			<richtext>
				<p>Much of the business transacted on the Web today takes place through information exchanges made possible by using documents as interfaces. For example, what seems to be a simple purchase from an online bookstore actually involves at least three different business collaborations — between the customer and the online catalog to select a book; between the bookstore and a credit card authorization service to verify and charge the customer's account; and between the bookstore and the delivery service with instructions for picking up and delivering the book to the customer. Document engineering is needed to analyze, design, and implement these Internet information exchanges. This book is an introduction to the emerging field of document engineering.</p>
			</richtext>
		</abstract>
		<address>Cambridge, Massachusetts</address>
		<identifier type="isbn">0-262-07261-0</identifier>
		<publisher>The MIT Press</publisher>
		<title>Document Engineering</title>
		<identifier type="uri">http://mitpress.mit.edu/catalog/item/default.asp?ttype=2&amp;tid=10476</identifier>
		<identifier type="uri">http://www.docengineering.com/</identifier>
	</reference>
	<reference name="ant04">
		<names type="author">
			<person>
				<givenname>Grigoris</givenname>
				<surname>Antoniou</surname>
			</person>
			<person>
				<givenname>Frank</givenname>
				<surname link="van">Harmelen</surname>
			</person>
		</names>
		<date value="2004-04"/>
		<address>Cambridge, Massachusetts</address>
		<identifier type="isbn">0-262-01210-3</identifier>
		<publisher>The MIT Press</publisher>
		<title>A Semantic Web Primer</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-rdf" weight="0.7"/>; <keywordref type="topic-rdfs" weight="0.7"/>; <keywordref type="topic-owl" weight="0.7"/>; </p>
			</richtext>
		</annotation>
		<identifier type="uri">http://mitpress.mit.edu/catalog/item/default.asp?ttype=2&amp;tid=10140</identifier>
	</reference>
	<reference name="pry95">
		<names type="author">
			<person>
				<givenname>Martin de</givenname>
				<surname>Prycker</surname>
			</person>
		</names>
		<date value="1995"/>
		<address>London, UK</address>
		<edition>3rd</edition>
		<field type="bibtex:index">ATM</field>
		<identifier type="isbn">0133421716</identifier>
		<publisher>Prentice-Hall</publisher>
		<field type="bibtex:src">DB</field>
		<title>Asynchronous Transfer Mode: Solution for Broadband ISDN</title>
	</reference>
	<reference name="bla95">
		<names type="author">
			<person>
				<givenname>Uyless</givenname>
				<surname>Black</surname>
			</person>
		</names>
		<date value="1995"/>
		<address>Englewood Cliffs, New Jersey</address>
		<field type="bibtex:index">ATM</field>
		<identifier type="isbn">013297178X</identifier>
		<publisher>Prentice-Hall</publisher>
		<field type="bibtex:src">DB</field>
		<title>ATM: Foundation for Broadband Networks</title>
	</reference>
	<reference name="gor90">
		<names type="author">
			<person>
				<givenname>Walter</givenname>
				<surname>Gora</surname>
			</person>
			<person>
				<givenname>Reinhard</givenname>
				<surname>Speyerer</surname>
			</person>
		</names>
		<date value="1990"/>
		<address>Bergheim, Germany</address>
		<edition>2nd</edition>
		<field type="bibtex:index">ASN.1</field>
		<identifier type="isbn">3892380236</identifier>
		<publisher>DATACOM</publisher>
		<field type="bibtex:src">Ethics: 753548</field>
		<title>Abstract Syntax Notation One (ASN.1)</title>
	</reference>
	<reference name="ste95">
		<names type="author">
			<person>
				<givenname>Ralf</givenname>
				<surname>Steinmetz</surname>
			</person>
			<person>
				<givenname>Klara</givenname>
				<surname>Nahrstedt</surname>
			</person>
		</names>
		<date value="1995"/>
		<address>Upper Saddle River, New Jersey</address>
		<field type="bibtex:index">Multimedia</field>
		<identifier type="isbn">0133244350</identifier>
		<publisher>Prentice-Hall</publisher>
		<field type="bibtex:src">EW</field>
		<title>Multimedia: Computing, Communications, and Applications</title>
	</reference>
	<reference name="ste90">
		<names type="author">
			<person>
				<givenname>W. Richard</givenname>
				<surname>Stevens</surname>
			</person>
		</names>
		<date value="1990-04"/>
		<address>Englewood Cliffs, New Jersey</address>
		<field type="bibtex:index">Unix, TCP/IP</field>
		<identifier type="isbn">0139498761</identifier>
		<publisher>Prentice-Hall</publisher>
		<field type="bibtex:src">EW</field>
		<title>Unix Network Programming</title>
	</reference>
	<reference name="cat97">
		<names type="author">
			<person>
				<givenname>R. G. G.</givenname>
				<surname>Cattell</surname>
			</person>
			<person>
				<givenname>Douglas</givenname>
				<surname>Barry</surname>
			</person>
			<person>
				<givenname>Dirk</givenname>
				<surname>Bartels</surname>
			</person>
			<person>
				<givenname>Mark</givenname>
				<surname>Berler</surname>
			</person>
			<person>
				<givenname>Jeff</givenname>
				<surname>Eastman</surname>
			</person>
			<person>
				<givenname>Sophie</givenname>
				<surname>Gamerman</surname>
			</person>
			<person>
				<givenname>David</givenname>
				<surname>Jordan</surname>
			</person>
			<person>
				<givenname>Adam</givenname>
				<surname>Springer</surname>
			</person>
			<person>
				<givenname>Henry</givenname>
				<surname>Strickland</surname>
			</person>
			<person>
				<givenname>Drew</givenname>
				<surname>Wade</surname>
			</person>
		</names>
		<date value="1997-07"/>
		<address>San Francisco, California</address>
		<field type="bibtex:index">ODMG</field>
		<identifier type="isbn">1558604634</identifier>
		<publisher>Morgan Kaufmann Publishers</publisher>
		<title>The Object Database Standard: ODMG 2.0</title>
	</reference>
	<reference name="abi99">
		<names type="author">
			<person>
				<givenname>Serge</givenname>
				<surname>Abiteboul</surname>
			</person>
			<person>
				<givenname>Peter</givenname>
				<surname>Buneman</surname>
			</person>
			<person>
				<givenname>Dan</givenname>
				<surname>Suciu</surname>
			</person>
		</names>
		<date value="1999-10"/>
		<address>San Francisco, California</address>
		<field type="bibtex:index">WWW, DBMS, XML</field>
		<identifier type="isbn">055860622X</identifier>
		<publisher>Morgan Kaufmann Publishers</publisher>
		<title>Data on the Web: From Relations to Semistructured Data and XML</title>
	</reference>
	<reference name="bea04">
		<names type="author">
			<person>
				<givenname>James</givenname>
				<surname>Bean</surname>
			</person>
		</names>
		<date value="2004"/>
		<address>San Francisco, California</address>
		<identifier type="isbn">1-55860-907-5</identifier>
		<publisher>Morgan Kaufmann Publishers</publisher>
		<title>XML for Data Architects: Designing for Reuse and Integration</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-xml" weight="0.8"/>; <keywordref type="topic-xmlschema" weight="0.8"/>; </p>
			</richtext>
		</annotation>
	</reference>
	<reference name="hoq00">
		<names type="author">
			<person>
				<givenname>Reaz</givenname>
				<surname>Hoque</surname>
			</person>
		</names>
		<date value="2000-05"/>
		<address>San Francisco, California</address>
		<identifier type="isbn">0123555922</identifier>
		<publisher>Morgan Kaufmann Publishers</publisher>
		<title>XML for Real Programmers</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-xml" weight="0.8"/>; </p>
			</richtext>
		</annotation>
	</reference>
	<reference name="pel04">
		<names type="author">
			<person>
				<givenname>Dwight</givenname>
				<surname>Peltzer</surname>
			</person>
		</names>
		<date value="2004"/>
		<address>Boston, Massachusetts</address>
		<identifier type="isbn">0-201-77168-3</identifier>
		<publisher>Addison Wesley</publisher>
		<title>XML: Language Mechanics &amp; Applications</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-xml" weight="0.8"/>; </p>
			</richtext>
		</annotation>
	</reference>
	<reference name="pet96">
		<names type="author">
			<person>
				<givenname>Larry L.</givenname>
				<surname>Peterson</surname>
			</person>
			<person>
				<givenname>Bruce S.</givenname>
				<surname>Davie</surname>
			</person>
		</names>
		<date value="1996-04"/>
		<address>San Francisco, California</address>
		<identifier type="isbn">1558603689</identifier>
		<publisher>Morgan Kaufmann Publishers</publisher>
		<title>Computer Networks</title>
	</reference>
	<reference name="pet99">
		<names type="author">
			<person>
				<givenname>Larry L.</givenname>
				<surname>Peterson</surname>
			</person>
			<person>
				<givenname>Bruce S.</givenname>
				<surname>Davie</surname>
			</person>
		</names>
		<date value="1999-10"/>
		<address>San Francisco, California</address>
		<edition>2nd</edition>
		<identifier type="isbn">1558605142</identifier>
		<publisher>Morgan Kaufmann Publishers</publisher>
		<title>Computer Networks: A Systems Approach</title>
		<associations>
			<xref type="updates" target="pet96"/>
		</associations>
	</reference>
	<reference name="tow99">
		<names type="author">
			<person>
				<givenname>George</givenname>
				<surname>Towner</surname>
			</person>
		</names>
		<date value="1999-05"/>
		<address>San Francisco, California</address>
		<identifier type="isbn">0120596407</identifier>
		<publisher>Morgan Kaufmann Publishers</publisher>
		<title>Discovering Quicktime for Windows and MacIntosh</title>
	</reference>
	<reference name="pat94">
		<names type="author">
			<person>
				<givenname>David A.</givenname>
				<surname>Patterson</surname>
			</person>
			<person>
				<givenname>John L.</givenname>
				<surname>Hennessy</surname>
			</person>
		</names>
		<date value="1994"/>
		<address>San Francisco, California</address>
		<field type="bibtex:index">MIPS, RISC</field>
		<identifier type="isbn">1558602828</identifier>
		<publisher>Morgan Kaufmann Publishers</publisher>
		<field type="bibtex:src">BP</field>
		<title>Computer Organization &amp; Design: The Hardware/Software Interface</title>
	</reference>
	<reference name="rag98b">
		<names type="author">
			<person>
				<givenname>Dave</givenname>
				<surname>Raggett</surname>
			</person>
			<person>
				<givenname>Jenny</givenname>
				<surname>Lam</surname>
			</person>
			<person>
				<givenname>Ian</givenname>
				<surname>Alexander</surname>
			</person>
			<person>
				<givenname>Michael</givenname>
				<surname>Kmiec</surname>
			</person>
		</names>
		<date value="1998-01"/>
		<address>Harlow, England</address>
		<edition>2nd</edition>
		<field type="bibtex:index">HTML</field>
		<identifier type="isbn">0201178052</identifier>
		<publisher>Addison Wesley</publisher>
		<field type="bibtex:src">EW</field>
		<title>Raggett on HTML 4</title>
	</reference>
	<reference name="car97">
		<names type="author">
			<person>
				<givenname>Rikk</givenname>
				<surname>Carey</surname>
			</person>
			<person>
				<givenname>Gavin</givenname>
				<surname>Bell</surname>
			</person>
		</names>
		<date value="1997-06"/>
		<address>Reading, Massachusetts</address>
		<identifier type="isbn">0201419742</identifier>
		<publisher>Addison Wesley</publisher>
		<field type="bibtex:src">EW</field>
		<title>The Annotated VRML 2.0 Reference Manual</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-vrml"/>; </p>
			</richtext>
		</annotation>
	</reference>
	<reference name="lie97">
		<names type="author">
			<person>
				<givenname>Håkon Wium</givenname>
				<surname>Lie</surname>
			</person>
			<person>
				<givenname>Bert</givenname>
				<surname>Bos</surname>
			</person>
		</names>
		<date value="1997-04"/>
		<address>Harlow, England</address>
		<identifier type="isbn">020141998X</identifier>
		<publisher>Addison Wesley</publisher>
		<field type="bibtex:src">EW</field>
		<title>Cascading Style Sheets</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-css1" weight="0.8"/>; </p>
			</richtext>
		</annotation>
	</reference>
	<reference name="lie99">
		<names type="author">
			<person>
				<givenname>Håkon Wium</givenname>
				<surname>Lie</surname>
			</person>
			<person>
				<givenname>Bert</givenname>
				<surname>Bos</surname>
			</person>
		</names>
		<date value="1999-07"/>
		<address>Harlow, England</address>
		<edition>2nd</edition>
		<identifier type="isbn">0201596253</identifier>
		<publisher>Addison Wesley</publisher>
		<field type="bibtex:src">EW</field>
		<title>Cascading Style Sheets</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-css1" weight="0.8"/>; <keywordref type="topic-css2" weight="0.8"/>; </p>
			</richtext>
		</annotation>
		<associations>
			<xref type="updates" target="lie97"/>
		</associations>
	</reference>
	<reference name="cam96">
		<names type="author">
			<person>
				<givenname>Mary</givenname>
				<surname>Campione</surname>
			</person>
			<person>
				<givenname>Kathy</givenname>
				<surname>Walrath</surname>
			</person>
		</names>
		<date value="1996"/>
		<address>Reading, Massachusetts</address>
		<field type="bibtex:index">Java</field>
		<identifier type="isbn">0201634546</identifier>
		<publisher>Addison Wesley</publisher>
		<field type="bibtex:src">EW</field>
		<title>The Java Tutorial</title>
	</reference>
	<reference name="per92">
		<names type="author">
			<person>
				<givenname>Radia</givenname>
				<surname>Perlman</surname>
			</person>
		</names>
		<date value="1992"/>
		<address>Reading, Massachusetts</address>
		<field type="bibtex:index">Bridge, Router, LAN, Ethernet, Routing, TCP/IP, OSI</field>
		<identifier type="isbn">0201563320</identifier>
		<publisher>Addison Wesley</publisher>
		<field type="bibtex:src">DB</field>
		<title>Interconnections: Bridges and Routers</title>
	</reference>
	<reference name="ste94">
		<names type="author">
			<person>
				<givenname>W. Richard</givenname>
				<surname>Stevens</surname>
			</person>
		</names>
		<date value="1994"/>
		<address>Reading, Massachusetts</address>
		<field type="bibtex:index">TCP/IP</field>
		<identifier type="isbn">0-201-63346-9</identifier>
		<publisher>Addison Wesley</publisher>
		<field type="bibtex:src">DD</field>
		<title>TCP/IP Illustrated</title>
		<volume>1: The Protocols</volume>
	</reference>
	<reference name="ste95b">
		<names type="author">
			<person>
				<givenname>W. Richard</givenname>
				<surname>Stevens</surname>
			</person>
		</names>
		<date value="1995-01"/>
		<address>Reading, Massachusetts</address>
		<field type="bibtex:index">TCP/IP</field>
		<identifier type="isbn">0-201-63354-X</identifier>
		<publisher>Addison Wesley</publisher>
		<title>TCP/IP Illustrated</title>
		<volume>2: The Implementation</volume>
	</reference>
	<reference name="ste96">
		<names type="author">
			<person>
				<givenname>W. Richard</givenname>
				<surname>Stevens</surname>
			</person>
		</names>
		<date value="1996-01"/>
		<address>Reading, Massachusetts</address>
		<field type="bibtex:index">TCP/IP, TCP for Transactions, HTTP, NNTP</field>
		<identifier type="isbn">0-20-163495-3</identifier>
		<publisher>Addison Wesley</publisher>
		<title>TCP/IP Illustrated</title>
		<volume>3: TCP for Transactions, HTTP, NNTP, and the Unix Domain Protocols</volume>
	</reference>
	<reference name="com91">
		<names type="author">
			<person>
				<givenname>Douglas E.</givenname>
				<surname>Comer</surname>
			</person>
		</names>
		<date value="1991"/>
		<address>Englewood Cliffs, New Jersey</address>
		<edition>2nd</edition>
		<field type="bibtex:index">TCP/IP</field>
		<identifier type="isbn">0-13-474321-0</identifier>
		<publisher>Prentice-Hall</publisher>
		<field type="bibtex:src">EW</field>
		<title>Internetworking with TCP/IP</title>
		<volume>1: Principles, Protocols and Architecture</volume>
	</reference>
	<reference name="com00">
		<names type="author">
			<person>
				<givenname>Douglas E.</givenname>
				<surname>Comer</surname>
			</person>
		</names>
		<date value="2000-01"/>
		<address>Englewood Cliffs, New Jersey</address>
		<edition>4th</edition>
		<field type="bibtex:index">TCP/IP</field>
		<identifier type="isbn">0-13-018380-6</identifier>
		<publisher>Prentice-Hall</publisher>
		<title>Internetworking with TCP/IP</title>
		<associations>
			<xref type="updates" target="com91"/>
		</associations>
		<volume>1: Principles, Protocols and Architecture</volume>
	</reference>
	<reference name="cs91">
		<names type="author">
			<person>
				<givenname>Douglas E.</givenname>
				<surname>Comer</surname>
			</person>
			<person>
				<givenname>David L.</givenname>
				<surname>Stevens</surname>
			</person>
		</names>
		<date value="1991"/>
		<address>Englewood Cliffs, New Jersey</address>
		<field type="bibtex:index">TCP/IP</field>
		<identifier type="isbn">0-13-472242-6</identifier>
		<publisher>Prentice-Hall</publisher>
		<field type="bibtex:src">BP</field>
		<title>Internetworking with TCP/IP</title>
		<volume>2: Design, Implementation and Internals</volume>
	</reference>
	<reference name="cs98">
		<names type="author">
			<person>
				<givenname>Douglas E.</givenname>
				<surname>Comer</surname>
			</person>
			<person>
				<givenname>David L.</givenname>
				<surname>Stevens</surname>
			</person>
		</names>
		<date value="1998-06"/>
		<address>Englewood Cliffs, New Jersey</address>
		<edition>3rd</edition>
		<field type="bibtex:index">TCP/IP</field>
		<identifier type="isbn">0-13-973843-6</identifier>
		<publisher>Prentice-Hall</publisher>
		<title>Internetworking with TCP/IP</title>
		<associations>
			<xref type="updates" target="cs91"/>
		</associations>
		<volume>2: Design, Implementation and Internals</volume>
	</reference>
	<reference name="com97">
		<names type="author">
			<person>
				<givenname>Douglas E.</givenname>
				<surname>Comer</surname>
			</person>
		</names>
		<date value="1997-08"/>
		<address>Englewood Cliffs, New Jersey</address>
		<edition>2nd</edition>
		<identifier type="isbn">0138901619</identifier>
		<publisher>Prentice-Hall</publisher>
		<title>The Internet Book</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-internet" weight="0.9"/>; </p>
			</richtext>
		</annotation>
	</reference>
	<reference name="com00a">
		<names type="author">
			<person>
				<givenname>Douglas E.</givenname>
				<surname>Comer</surname>
			</person>
		</names>
		<date value="2000-03"/>
		<address>Englewood Cliffs, New Jersey</address>
		<edition>3rd</edition>
		<identifier type="isbn">0130308528</identifier>
		<publisher>Prentice-Hall</publisher>
		<title>The Internet Book</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-internet" weight="0.9"/>; </p>
			</richtext>
		</annotation>
		<associations>
			<xref type="updates" target="com97"/>
		</associations>
	</reference>
	<reference name="kau95">
		<names type="author">
			<person>
				<givenname>Charles W.</givenname>
				<surname>Kaufman</surname>
			</person>
			<person>
				<givenname>Radia</givenname>
				<surname>Perlman</surname>
			</person>
			<person>
				<givenname>Michael</givenname>
				<surname>Speciner</surname>
			</person>
		</names>
		<date value="1995-03"/>
		<address>Englewood Cliffs, New Jersey</address>
		<field type="bibtex:index">security</field>
		<identifier type="isbn">0-13-061466-1</identifier>
		<publisher>Prentice-Hall</publisher>
		<title>Network Security: Private Communication in a Public World</title>
	</reference>
	<reference name="abr98">
		<names type="author">
			<person>
				<givenname>Marc</givenname>
				<surname>Abrams</surname>
			</person>
		</names>
		<date value="1998"/>
		<address>Englewood Cliffs, New Jersey</address>
		<identifier type="isbn">0-13-954785-1</identifier>
		<publisher>Prentice-Hall</publisher>
		<title>World Wide Web: Beyond the Basics</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-www" weight="0.9"/>; </p>
			</richtext>
		</annotation>
	</reference>
	<reference name="ros90">
		<names type="author">
			<person>
				<givenname>Marshall T.</givenname>
				<surname>Rose</surname>
			</person>
		</names>
		<date value="1990"/>
		<address>Englewood Cliffs, New Jersey</address>
		<identifier type="isbn">0-13-643016-3</identifier>
		<publisher>Prentice-Hall</publisher>
		<field type="bibtex:src">HaL</field>
		<title>The Open Book</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-osi" weight="0.9"/>; </p>
			</richtext>
		</annotation>
	</reference>
	<reference name="hal92">
		<names type="author">
			<person>
				<givenname>Fred</givenname>
				<surname>Halsall</surname>
			</person>
		</names>
		<date value="1992"/>
		<address>Wokingham, England</address>
		<identifier type="isbn">0-201-56506-4</identifier>
		<publisher>Addison Wesley</publisher>
		<field type="bibtex:src">BP</field>
		<title>Data Communications, Computer Networks and Open Systems</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-osi" weight="0.9"/>; </p>
			</richtext>
		</annotation>
	</reference>
	<reference name="hal96">
		<names type="author">
			<person>
				<givenname>Fred</givenname>
				<surname>Halsall</surname>
			</person>
		</names>
		<date value="1996-01"/>
		<address>Wokingham, England</address>
		<edition>4th</edition>
		<publisher>Addison Wesley</publisher>
		<title>Data Communications, Computer Networks and Open Systems</title>
		<associations>
			<xref type="updates" target="hal92"/>
		</associations>
	</reference>
	<reference name="str92a">
		<names type="author">
			<person>
				<givenname>W. Timothy</givenname>
				<surname>Strayer</surname>
			</person>
			<person>
				<givenname>Bert J.</givenname>
				<surname>Dempsey</surname>
			</person>
			<person>
				<givenname>Alfred C.</givenname>
				<surname>Weaver</surname>
			</person>
		</names>
		<date value="1992"/>
		<address>Reading, Massachusetts</address>
		<field type="bibtex:index">XTP, multicast</field>
		<identifier type="isbn">0-201-56351-7</identifier>
		<publisher>Addison Wesley</publisher>
		<field type="bibtex:src">Ethics: 755269</field>
		<title>XTP: The Xpress Transfer Protocol</title>
	</reference>
	<reference name="lef89">
		<names type="author">
			<person>
				<givenname>Samuel J.</givenname>
				<surname>Leffler</surname>
			</person>
			<person>
				<givenname>Marshall Kirk</givenname>
				<surname>McKusick</surname>
			</person>
			<person>
				<givenname>Michael J.</givenname>
				<surname>Karels</surname>
			</person>
			<person>
				<givenname>John S.</givenname>
				<surname>Quaterman</surname>
			</person>
		</names>
		<date value="1989"/>
		<address>Reading, Massachusetts</address>
		<field type="bibtex:index">Unix 4.3BSD</field>
		<identifier type="isbn">0-201-06196-1</identifier>
		<publisher>Addison Wesley</publisher>
		<field type="bibtex:src">EW</field>
		<title>The Design and Implementation of the 4.3BSD Operating System</title>
	</reference>
	<reference name="ber87">
		<names type="author">
			<person>
				<givenname>Philip A.</givenname>
				<surname>Bernstein</surname>
			</person>
			<person>
				<givenname>Vassos</givenname>
				<surname>Hadzilacos</surname>
			</person>
			<person>
				<givenname>Nathan</givenname>
				<surname>Goodman</surname>
			</person>
		</names>
		<date value="1987"/>
		<address>Reading, Massachusetts</address>
		<identifier type="isbn">0-201-10715-5</identifier>
		<publisher>Addison Wesley</publisher>
		<field type="bibtex:src">DB</field>
		<title>Concurrency Control and Recovery in Database Systems</title>
	</reference>
	<reference name="bla91">
		<names type="author">
			<person>
				<givenname>Uyless</givenname>
				<surname>Black</surname>
			</person>
		</names>
		<date value="1991"/>
		<address>Englewood Cliffs, New Jersey</address>
		<identifier type="isbn">0-13-637133-7</identifier>
		<publisher>Prentice-Hall</publisher>
		<field type="bibtex:src">BP</field>
		<title>OSI: A Model for Computer Communication Standards</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-osi" weight="0.9"/>; </p>
			</richtext>
		</annotation>
	</reference>
	<reference name="bac93">
		<names type="author">
			<person>
				<givenname>Jean</givenname>
				<surname>Bacon</surname>
			</person>
		</names>
		<date value="1992"/>
		<address>Wokingham, England</address>
		<identifier type="isbn">0-201-41677-8</identifier>
		<publisher>Addison Wesley</publisher>
		<field type="bibtex:src">TIK: 805</field>
		<title>Concurrent Systems</title>
	</reference>
	<reference name="win93a">
		<names type="author">
			<person>
				<givenname>Jane</givenname>
				<surname>Winsor</surname>
			</person>
		</names>
		<date value="1993"/>
		<address>Emeryville, California</address>
		<identifier type="isbn">1-56276-080-7</identifier>
		<publisher>Ziff-Davis Press</publisher>
		<field type="bibtex:src">EW</field>
		<title>Solaris System Administrator's Guide</title>
	</reference>
	<reference name="win93b">
		<names type="author">
			<person>
				<givenname>Jane</givenname>
				<surname>Winsor</surname>
			</person>
		</names>
		<date value="1993"/>
		<address>Emeryville, California</address>
		<identifier type="isbn">1-56276-131-5</identifier>
		<publisher>Ziff-Davis Press</publisher>
		<field type="bibtex:src">EW</field>
		<title>Solaris Advanced System Administrator's Guide</title>
	</reference>
	<reference name="hug98">
		<names type="author">
			<person>
				<givenname>Lawrence E.</givenname>
				<surname>Hughes</surname>
			</person>
		</names>
		<date value="1998-09"/>
		<address>Norwood, Massachusetts</address>
		<publisher>Artech House</publisher>
		<title>Internet E-Mail: Protocols, Standards, and Implementation</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-smtp" weight="0.8"/>; <keywordref type="topic-pop" weight="0.8"/>; <keywordref type="topic-imap" weight="0.8"/>; <keywordref type="topic-mime" weight="0.7"/>; <keywordref type="topic-pgp" weight="0.7"/>; </p>
			</richtext>
		</annotation>
	</reference>
	<reference name="pur93">
		<names type="author">
			<person>
				<givenname>Michael</givenname>
				<surname>Purser</surname>
			</person>
		</names>
		<date value="1993"/>
		<address>Norwood, Massachusetts</address>
		<identifier type="isbn">0890066922</identifier>
		<publisher>Artech House</publisher>
		<field type="bibtex:src">Ethics: 757281</field>
		<title>Secure Data Networking</title>
	</reference>
	<reference name="str86">
		<names type="author">
			<person>
				<givenname>Bjarne</givenname>
				<surname>Stroustrup</surname>
			</person>
		</names>
		<date value="1986"/>
		<address>Reading, Massachusetts</address>
		<identifier type="isbn">020112078X</identifier>
		<publisher>Addison Wesley</publisher>
		<title>The C++ Programming Language</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-cplusplus"/>; </p>
			</richtext>
		</annotation>
	</reference>
	<reference name="str91">
		<names type="author">
			<person>
				<givenname>Bjarne</givenname>
				<surname>Stroustrup</surname>
			</person>
		</names>
		<date value="1991"/>
		<address>Reading, Massachusetts</address>
		<edition>2nd</edition>
		<identifier type="isbn">0201539926</identifier>
		<publisher>Addison Wesley</publisher>
		<title>The C++ Programming Language</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-cplusplus"/>; </p>
			</richtext>
		</annotation>
	</reference>
	<reference name="lip89">
		<names type="author">
			<person>
				<givenname>Stanley B.</givenname>
				<surname>Lippman</surname>
			</person>
		</names>
		<date value="1989"/>
		<address>Reading, Massachusetts</address>
		<identifier type="isbn">0201164876</identifier>
		<publisher>Addison Wesley</publisher>
		<title>A C++ Primer</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-cplusplus" weight="0.9"/>; </p>
			</richtext>
		</annotation>
	</reference>
	<reference name="lip91">
		<names type="author">
			<person>
				<givenname>Stanley B.</givenname>
				<surname>Lippman</surname>
			</person>
		</names>
		<date value="1991-07"/>
		<address>Reading, Massachusetts</address>
		<edition>2nd</edition>
		<identifier type="isbn">0201548488</identifier>
		<publisher>Addison Wesley</publisher>
		<title>A C++ Primer</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-cplusplus" weight="0.9"/>; </p>
			</richtext>
		</annotation>
	</reference>
	<reference name="gam95">
		<names type="author">
			<person>
				<givenname>Erich</givenname>
				<surname>Gamma</surname>
			</person>
			<person>
				<givenname>Richard</givenname>
				<surname>Helm</surname>
			</person>
			<person>
				<givenname>Ralph</givenname>
				<surname>Johnson</surname>
			</person>
			<person>
				<givenname>John</givenname>
				<surname>Vlissides</surname>
			</person>
		</names>
		<date value="1995-01"/>
		<address>Reading, Massachusetts</address>
		<identifier type="isbn">0201633612</identifier>
		<publisher>Addison Wesley</publisher>
		<title>Design Patterns: Elements of Reusable Object-Oriented Software</title>
	</reference>
	<reference name="abe98">
		<names type="author">
			<person>
				<givenname>Harold</givenname>
				<surname>Abelson</surname>
			</person>
			<person>
				<givenname>Ross</givenname>
				<surname>Anderson</surname>
			</person>
			<person>
				<givenname>Steven M.</givenname>
				<surname>Bellovin</surname>
			</person>
			<person>
				<givenname>Josh</givenname>
				<surname>Benaloh</surname>
			</person>
			<person>
				<givenname>Matt</givenname>
				<surname>Blaze</surname>
			</person>
			<person>
				<givenname>Whitfield</givenname>
				<surname>Diffie</surname>
			</person>
			<person>
				<givenname>John</givenname>
				<surname>Gilmore</surname>
			</person>
			<person>
				<givenname>Peter G.</givenname>
				<surname>Neumann</surname>
			</person>
			<person>
				<givenname>Ronald L.</givenname>
				<surname>Rivest</surname>
			</person>
			<person>
				<givenname>Jeffrey I.</givenname>
				<surname>Schiller</surname>
			</person>
			<person>
				<givenname>Bruce</givenname>
				<surname>Schneier</surname>
			</person>
		</names>
		<date value="1998"/>
		<abstract>
			<richtext>
				<p>A variety of "key recovery," "key escrow," and "trusted third-party" encryption requirements have been suggested in recent years by government agencies seeking to conduct covert surveillance within the changing environments brought about by new technologies. This report examines the fundamental properties of these requirements and attempts to outline the technical risks, costs, and implications of deploying systems that provide government access to encryption keys.</p>
			</richtext>
		</abstract>
		<howpublished>A Report by an Ad Hoc Group of Cryptographers and Computer Scientists</howpublished>
		<title>The Risks of Key Recovery, Key Escrow, and Trusted Third-Party Encryption</title>
		<identifier type="uri">http://www.cdt.org/crypto/risks98/</identifier>
	</reference>
	<reference name="srgb">
		<names type="author">
			<person>
				<givenname>Michael</givenname>
				<surname>Stokes</surname>
			</person>
			<person>
				<givenname>Matthew</givenname>
				<surname>Anderson</surname>
			</person>
			<person>
				<givenname>Srinivasan</givenname>
				<surname>Chandrasekar</surname>
			</person>
			<person>
				<givenname>Ricardo</givenname>
				<surname>Motta</surname>
			</person>
		</names>
		<date value="1996-11"/>
		<howpublished>http://www.color.org/contrib/sRGB.html</howpublished>
		<title>A Standard Default Color Space for the Internet — sRGB</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-srgb"/>; </p>
			</richtext>
		</annotation>
	</reference>
	<reference name="spe94">
		<names type="author">
			<person>
				<givenname>Simon E.</givenname>
				<surname>Spero</surname>
			</person>
		</names>
		<date value="1994-07"/>
		<howpublished>http://www.w3.org/Protocols/HTTP/1.0/HTTPPerformance.html</howpublished>
		<field type="bibtex:index">HTTP, TCP/IP</field>
		<title>Analysis of HTTP Performance problems</title>
	</reference>
	<reference name="z39">
		<names type="author">
			<name>American National Standards Institute</name>
		</names>
		<date value="1995-07"/>
		<howpublished>ANSI/NISO Z39.50-1995</howpublished>
		<title>Information Retrieval (Z39.50): Application Service Definition and Protocol Specification</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-z3950"/>; </p>
			</richtext>
		</annotation>
	</reference>
	<reference name="z39.56">
		<names type="author">
			<name>American National Standards Institute</name>
		</names>
		<date value="1996"/>
		<howpublished>ANSI/NISO Z39.56-1996</howpublished>
		<title>Serial Item and Contribution Identifier</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-sici"/>; </p>
			</richtext>
		</annotation>
	</reference>
	<reference name="z39.84">
		<names type="author">
			<name>American National Standards Institute</name>
		</names>
		<date value="2000-05"/>
		<howpublished>ANSI/NISO Z39.84-2000</howpublished>
		<title>Syntax for the Digital Object Identifier</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-doi"/>; </p>
			</richtext>
		</annotation>
		<identifier type="uri" resourceType="application/pdf">http://www.niso.org/standards/resources/Z39-84-2000.pdf</identifier>
	</reference>
	<reference name="z39.88">
		<names type="author">
			<name>American National Standards Institute</name>
		</names>
		<date value="2005-04"/>
		<abstract>
			<richtext>
				<p>The OpenURL Framework Standard defines an architecture for creating OpenURL Framework Applications. An OpenURL Framework Application is a networked service environment, in which packages of information are transported over a network. These packages have a description of a referenced resource at their core, and they are transported with the intent of obtaining context-sensitive services pertaining to the referenced resource. To enable the recipients of these packages to deliver such context-sensitive services, each package describes the referenced resource itself, the network context in which the resource is referenced, and the context in which the service request takes place. This Standard specifies how to construct these packages as Representations of abstract information constructs called ContextObjects. To this end, the OpenURL Framework Standard defines the following core components: Character Encoding, Serialization, Constraint Language, ContextObject Format, Metadata Format, and Namespace. In addition, this Standard defines Transport, a core component that enables communities to specify how to transport ContextObject Representations. Finally, this Standard specifies how a community can deploy a new OpenURL Framework Application by defining a new Community Profile, the last core component. This Standard defines the OpenURL Framework Registry and the rules that govern the usage of this Registry. The OpenURL Framework Registry contains all instances of all core components created by communities that have deployed OpenURL Framework Applications. This Standard defines and registers the initial content of the OpenURL Framework Registry, thereby deploying two distinct OpenURL Framework Applications.</p>
			</richtext>
		</abstract>
		<howpublished>ANSI/NISO Z39.88-2004</howpublished>
		<identifier type="isbn">1-880124-61-0</identifier>
		<title>The OpenURL Framework for Context-Sensitive Services</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-openurl"/>; </p>
			</richtext>
		</annotation>
		<identifier type="uri">http://www.niso.org/standards/standard_detail.cfm?std_id=783</identifier>
	</reference>
	<reference name="ascii">
		<names type="author">
			<name>American National Standards Institute</name>
		</names>
		<date value="1992"/>
		<howpublished>ANSI X3.4</howpublished>
		<title>Coded Character Set — 7-Bit American National Standard Code for Information Interchange</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-ascii"/>; </p>
			</richtext>
		</annotation>
	</reference>
	<reference name="lzs">
		<names type="author">
			<name>American National Standards Institute</name>
		</names>
		<date value="1994-08"/>
		<howpublished>ANSI X3.241</howpublished>
		<title>Data Compression Method — Adaptive Coding with Sliding Window for Information Interchange</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-lzs"/>; </p>
			</richtext>
		</annotation>
	</reference>
	<reference name="ieee754">
		<names type="author">
			<name>Institute of Electrical and Electronics Engineers</name>
		</names>
		<date value="1985"/>
		<howpublished>IEEE Std 754-1985</howpublished>
		<title>IEEE Standard for Binary Floating-Point Arithmetic</title>
	</reference>
	<reference name="midi10">
		<names type="author">
			<name>MIDI Manufacturers Association</name>
		</names>
		<date value="1996-03"/>
		<title>Complete MIDI 1.0 Detailed Specification</title>
	</reference>
	<reference name="des">
		<names type="author">
			<name>National Institute of Standards and Technology</name>
		</names>
		<date value="1993-12"/>
		<howpublished>FIPS Publication 46-2</howpublished>
		<title>Data Encryption Standard</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-des"/>; <keywordref type="topic-dea"/>; </p>
			</richtext>
		</annotation>
	</reference>
	<reference name="fips463">
		<names type="author">
			<name>National Institute of Standards and Technology</name>
		</names>
		<date value="1999-10"/>
		<howpublished>FIPS Publication 46-3</howpublished>
		<title>Data Encryption Standard (DES)</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-des"/>; <keywordref type="topic-dea"/>; <keywordref type="topic-tripledes"/>; <keywordref type="topic-tdea"/>; </p>
			</richtext>
		</annotation>
		<associations>
			<xref type="updates" target="des"/>
		</associations>
		<identifier type="uri">http://csrc.nist.gov/publications/fips/fips46-3/</identifier>
	</reference>
	<reference name="sha1">
		<names type="author">
			<name>National Institute of Standards and Technology</name>
		</names>
		<date value="1993-05"/>
		<howpublished>FIPS Publication 180</howpublished>
		<title>Secure Hash Standard (SHS)</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-shs"/>; <keywordref type="topic-sha0"/>; </p>
			</richtext>
		</annotation>
	</reference>
	<reference name="sha2">
		<names type="author">
			<name>National Institute of Standards and Technology</name>
		</names>
		<date value="1994-05"/>
		<title>Announcement of Weakness in the Secure Hash Standard</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-shs"/>; <keywordref type="topic-sha0"/>; </p>
			</richtext>
		</annotation>
	</reference>
	<reference name="dss">
		<names type="author">
			<name>National Institute of Standards and Technology</name>
		</names>
		<date value="1994-05"/>
		<howpublished>FIPS Publication 186</howpublished>
		<title>Digital Signature Standard (DSS)</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-dss"/>; <keywordref type="topic-dsa"/>; </p>
			</richtext>
		</annotation>
	</reference>
	<reference name="iec61966-2">
		<names type="author">
			<name>International Electrotechnical Commission</name>
		</names>
		<date value="1998-08"/>
		<howpublished>IEC 61966-2</howpublished>
		<title>Colour measurement and management in multimedia systems and equipment — Part 2: Colour Management in Multimedia Systems</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-srgb"/>; </p>
			</richtext>
		</annotation>
	</reference>
	<reference name="iso639">
		<names type="author">
			<name>International Organization for Standardization</name>
		</names>
		<date value="2002-07"/>
		<abstract>
			<richtext>
				<p>This part of ISO 639 provides a code consisting of language code elements comprising two-letter language identifiers for the representation of names of languages. The language identifiers according to this part of ISO 639 were devised originally for use in terminology, lexicography and linguistics, but may be adopted for any application requiring the expression of language in two-letter coded form, especially in computerized systems. The alpha-2 code was devised for practical use for most of the major languages of the world that are not only most frequently represented in the total body of the world's literature, but which also comprise a considerable volume of specialized languages and terminologies. Additional language identifiers are created when it becomes apparent that a significant body of documentation written in specialized languages and terminologies exists. Languages designed exclusively for machine use, such as computer-programming languages, are not included in this code.</p>
			</richtext>
		</abstract>
		<howpublished>ISO 639</howpublished>
		<title>Codes for the Representation of Names of Languages</title>
		<identifier type="uri">http://www.iso.ch/iso/en/CatalogueDetailPage.CatalogueDetail?CSNUMBER=22109</identifier>
	</reference>
	<reference name="iso646">
		<names type="author">
			<name>International Organization for Standardization</name>
		</names>
		<date value="1991"/>
		<abstract>
			<richtext>
				<p>Specifies a set of 128 control and graphic characters such as letters, digits and symbols with their coded representation. Applies to alphabets of the Latin script.</p>
			</richtext>
		</abstract>
		<howpublished>ISO/IEC 646</howpublished>
		<title>Information Technology — ISO 7-bit Coded Character Set for Information Interchange</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-ascii" weight="0.9"/>; </p>
			</richtext>
		</annotation>
	</reference>
	<reference name="iso690">
		<names type="author">
			<name>International Organization for Standardization</name>
		</names>
		<date value="2005-08"/>
		<abstract>
			<richtext>
				<p>Specifies the elements to be included in bibliographic references to published monographs and serials, to chapters, articles, etc. in such publications and to patent documents. Sets out a prescribed order for the elements of the reference and establishes conventions for the transcription and presentation of information derived from the source publication.</p>
			</richtext>
		</abstract>
		<howpublished>ISO 690:1987</howpublished>
		<title>Documentation — Bibliographic References — Content, Form and Structure</title>
		<identifier type="uri">http://www.iso.org/iso/en/CatalogueDetailPage.CatalogueDetail?CSNUMBER=4888</identifier>
	</reference>
	<reference name="iso690-2">
		<names type="author">
			<name>International Organization for Standardization</name>
		</names>
		<date value="2004-06"/>
		<howpublished>ISO 690-2:1997</howpublished>
		<title>Documentation — Bibliographic References — Part 2: Electronic Documents or Parts thereof</title>
		<identifier type="uri">http://www.iso.org/iso/en/CatalogueDetailPage.CatalogueDetail?CSNUMBER=25921</identifier>
	</reference>
	<reference name="iso2108">
		<names type="author">
			<name>International Organization for Standardization</name>
		</names>
		<date value="1992"/>
		<abstract>
			<richtext>
				<p>The purpose is to coordinate and standardize the use of identifying numbers so that each international standard book number is unique to a title or edition of a book or other monographic publication (serial publications excluded) published or produced by a specific publisher or producer. The standard specifies the construction of an ISBN and the location of the printed number on the publication.</p>
			</richtext>
		</abstract>
		<howpublished>ISO 2108</howpublished>
		<title>Information and Documentation — International Standard Book Numbering (ISBN)</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-isbn"/>; </p>
			</richtext>
		</annotation>
		<identifier type="uri">http://www.iso.ch/iso/en/CatalogueDetailPage.CatalogueDetail?CSNUMBER=6898</identifier>
	</reference>
	<reference name="iso2709">
		<names type="author">
			<name>International Organization for Standardization</name>
		</names>
		<date value="1996"/>
		<abstract>
			<richtext>
				<p>Specifies the requirements for a generalized exchange format suitable for bibliographic descriptions. Describes a framework for communications between data processing systems. Replaces the second edition.</p>
			</richtext>
		</abstract>
		<howpublished>ISO 2709</howpublished>
		<title>Information and Documentation — Format for Information Exchange</title>
		<identifier type="uri">http://www.iso.org/iso/en/CatalogueDetailPage.CatalogueDetail?CSNUMBER=7675</identifier>
	</reference>
	<reference name="iso2788">
		<names type="author">
			<name>International Organization for Standardization</name>
		</names>
		<date value="1986"/>
		<howpublished>ISO 2788</howpublished>
		<title>Documentation — Guidelines for the Establishment and Development of Monolingual Thesauri</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-thesaurus"/>; </p>
			</richtext>
		</annotation>
	</reference>
	<reference name="iso3297">
		<names type="author">
			<name>International Organization for Standardization</name>
		</names>
		<date value="1998"/>
		<howpublished>ISO 3297</howpublished>
		<title>Information and Documentation — International Standard Serial Number (ISSN)</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-issn"/>; </p>
			</richtext>
		</annotation>
		<identifier type="uri">http://www.iso.org/iso/en/CatalogueDetailPage.CatalogueDetail?CSNUMBER=23400</identifier>
	</reference>
	<reference name="iso3309">
		<names type="author">
			<name>International Organization for Standardization</name>
		</names>
		<date value="1993"/>
		<howpublished>ISO/IEC 3309</howpublished>
		<title>Information Technology — Telecommunications and information exchange between systems — High-level data link control (HDLC) procedures — Frame structure</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-crc" weight="0.8"/>; </p>
			</richtext>
		</annotation>
	</reference>
	<reference name="iso3166">
		<names type="author">
			<name>International Organization for Standardization</name>
		</names>
		<date value="2001-11"/>
		<howpublished>ISO 3166</howpublished>
		<title>Codes for the Representation of Names of Countries and their Subdivisions</title>
		<identifier type="uri">http://www.iso.ch/iso/en/CatalogueDetailPage.CatalogueDetail?CSNUMBER=24591</identifier>
	</reference>
	<reference name="iso4217">
		<names type="author">
			<name>International Organization for Standardization</name>
		</names>
		<date value="2001-08"/>
		<howpublished>ISO 4217</howpublished>
		<title>Codes for the Representation of Currencies and Funds</title>
		<identifier type="uri">http://www.iso.ch/iso/en/CatalogueDetailPage.CatalogueDetail?CSNUMBER=34749</identifier>
	</reference>
	<reference name="iso5964">
		<names type="author">
			<name>International Organization for Standardization</name>
		</names>
		<date value="1985"/>
		<howpublished>ISO 5964</howpublished>
		<title>Documentation — Guidelines for the Establishment and Development of Multilingual Thesauri</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-thesaurus"/>; </p>
			</richtext>
		</annotation>
	</reference>
	<reference name="iso7498">
		<names type="author">
			<name>International Organization for Standardization</name>
		</names>
		<date value="1994"/>
		<howpublished>ISO/IEC 7498 (Second Edition)</howpublished>
		<field type="bibtex:index">ITU X.200</field>
		<title>Information Processing Systems — Open Systems Interconnection (OSI) — Basic Reference Model</title>
	</reference>
	<reference name="iso8072">
		<names type="author">
			<name>International Organization for Standardization</name>
		</names>
		<date value="1996"/>
		<howpublished>ISO/IEC 8072</howpublished>
		<field type="bibtex:index">OSI, TSAP</field>
		<title>Information Technology — Open Systems Interconnection (OSI) — Transport Service Definition</title>
	</reference>
	<reference name="iso8601">
		<names type="author">
			<name>International Organization for Standardization</name>
		</names>
		<date value="2004-12"/>
		<howpublished>ISO 8601</howpublished>
		<title>Data Elements and Interchange Formats — Information Interchange — Representation of Dates and Times</title>
		<identifier type="uri">http://www.iso.org/iso/en/CatalogueDetailPage.CatalogueDetail?CSNUMBER=40874</identifier>
	</reference>
	<reference name="iso8632">
		<names type="author">
			<name>International Organization for Standardization</name>
		</names>
		<date value="1992"/>
		<howpublished>ISO/IEC 8632</howpublished>
		<field type="bibtex:index">CGM</field>
		<title>Information Technology — Computer graphics — Metafile for the Storage and Transfer of Picture Description Information</title>
	</reference>
	<reference name="iso8802-1">
		<names type="author">
			<name>International Organization for Standardization</name>
		</names>
		<date value="1994"/>
		<howpublished>ISO/IEC TR 8802-1</howpublished>
		<title>Information Technology — Telecommunications and information exchange between systems — Specific requirements — Part 1: Overview of Local Area Network Standards</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-ieee802"/>; </p>
			</richtext>
		</annotation>
	</reference>
	<reference name="iso8802-2">
		<names type="author">
			<name>International Organization for Standardization</name>
		</names>
		<date value="1998"/>
		<howpublished>ISO/IEC 8802-2</howpublished>
		<title>Information Technology — Telecommunications and information exchange between systems — Specific requirements — Part 2: Logical link control</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-ieee8022"/>; <keywordref type="topic-llc" weight="0.9"/>; </p>
			</richtext>
		</annotation>
	</reference>
	<reference name="iso8802-3">
		<names type="author">
			<name>International Organization for Standardization</name>
		</names>
		<date value="1996"/>
		<howpublished>ISO/IEC 8802-3</howpublished>
		<title>Information Technology — Telecommunications and information exchange between systems — Local and metropolitan area networks — Part 3: Carrier sense multiple access with collision detection (CSMA/CD) access method and physical layer specifications</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-ieee8023"/>; <keywordref type="topic-ethernet" weight="0.9"/>; </p>
			</richtext>
		</annotation>
	</reference>
	<reference name="iso8802-4">
		<names type="author">
			<name>International Organization for Standardization</name>
		</names>
		<date value="1990"/>
		<howpublished>ISO/IEC 8802-4</howpublished>
		<title>Information Processing Systems — Local area networks — Part 4: Token-passing bus access method and physical layer specifications</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-ieee8024"/>; <keywordref type="topic-tokenbus" weight="0.9"/>; </p>
			</richtext>
		</annotation>
	</reference>
	<reference name="iso8802-5">
		<names type="author">
			<name>International Organization for Standardization</name>
		</names>
		<date value="1998"/>
		<howpublished>ISO/IEC 8802-5</howpublished>
		<title>Information Technology — Telecommunications and information exchange between systems — Local and Metropolitan Area Networks — Specific requirements — Part 5: Token ring access method and physical layer specifications</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-ieee8025"/>; <keywordref type="topic-tokenring" weight="0.9"/>; </p>
			</richtext>
		</annotation>
	</reference>
	<reference name="iso8824">
		<names type="author">
			<name>International Organization for Standardization</name>
		</names>
		<date value="1995"/>
		<howpublished>ISO/IEC 8824</howpublished>
		<title>Information Processing Systems — Open Systems Interconnection (OSI) — Specification of Abstract Syntax Notation One (ASN.1)</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-asn1"/>; </p>
			</richtext>
		</annotation>
	</reference>
	<reference name="iso8825">
		<names type="author">
			<name>International Organization for Standardization</name>
		</names>
		<date value="1995"/>
		<howpublished>ISO/IEC 8825</howpublished>
		<field type="bibtex:index">ASN.1, BER</field>
		<title>Information Processing Systems — Open Systems Interconnection (OSI) — Specification of Basic Encoding Rules for Abstract Syntax Notation One (ASN.1)</title>
	</reference>
	<reference name="iso8859">
		<names type="author">
			<name>International Organization for Standardization</name>
		</names>
		<date value="1999"/>
		<howpublished>ISO/IEC 8859</howpublished>
		<title>Information Technology — 8-bit single-byte coded graphic character sets</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-iso8859"/>; </p>
			</richtext>
		</annotation>
	</reference>
	<reference name="iso8859-1">
		<names type="author">
			<name>International Organization for Standardization</name>
		</names>
		<date value="1998"/>
		<howpublished>ISO/IEC 8859-1</howpublished>
		<title>Information Technology — 8-bit single-byte coded graphic character sets — Part 1: Latin alphabet No. 1</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-iso8859"/>; </p>
			</richtext>
		</annotation>
	</reference>
	<reference name="iso8859-5">
		<names type="author">
			<name>International Organization for Standardization</name>
		</names>
		<date value="1999"/>
		<howpublished>ISO/IEC 8859-5</howpublished>
		<title>Information Technology — 8-bit single-byte coded graphic character sets — Part 5: Latin/Cyrillic alphabet</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-iso8859"/>; </p>
			</richtext>
		</annotation>
	</reference>
	<reference name="iso8879">
		<names type="author">
			<name>International Organization for Standardization</name>
		</names>
		<date value="1986"/>
		<howpublished>ISO 8879</howpublished>
		<title>Information Processing — Text and Office Systems — Standard Generalized Markup Language (SGML)</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-sgml"/>; </p>
			</richtext>
		</annotation>
		<identifier type="uri">http://www.iso.ch/iso/en/CatalogueDetailPage.CatalogueDetail?CSNUMBER=16387</identifier>
	</reference>
	<reference name="iso9069">
		<names type="author">
			<name>International Organization for Standardization</name>
		</names>
		<date value="1988"/>
		<howpublished>ISO 9069</howpublished>
		<title>Information Processing — SGML Support Facilities — SGML Document Interchange Format (SDIF)</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-sdif"/>; </p>
			</richtext>
		</annotation>
		<identifier type="uri">http://www.iso.ch/iso/en/CatalogueDetailPage.CatalogueDetail?CSNUMBER=16643</identifier>
	</reference>
	<reference name="iso9070">
		<names type="author">
			<name>International Organization for Standardization</name>
		</names>
		<date value="1991"/>
		<howpublished>ISO/IEC 9070</howpublished>
		<title>Information Technology — SGML Support Facilities — Registration procedures for public text owner identifiers</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-sgml"/>; </p>
			</richtext>
		</annotation>
	</reference>
	<reference name="iso9072">
		<names type="author">
			<name>International Organization for Standardization</name>
		</names>
		<date value="1989"/>
		<howpublished>ISO/IEC 9072</howpublished>
		<field type="bibtex:index">ITU X.219/X.229</field>
		<title>Information Processing Systems — Text Communication — Remote Operations</title>
	</reference>
	<reference name="iso9075">
		<names type="author">
			<name>International Organization for Standardization</name>
		</names>
		<date value="1992"/>
		<howpublished>ISO/IEC 9075</howpublished>
		<title>Information Technology — Database Languages — SQL</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-sql"/>; </p>
			</richtext>
		</annotation>
	</reference>
	<reference name="iso9075-14">
		<names type="author">
			<name>International Organization for Standardization</name>
		</names>
		<date value="2005-07"/>
		<howpublished>ISO/IEC 9075-14</howpublished>
		<title>Information Technology — Database Languages — SQL — Part 14: XML-Related Specifications (SQL/XML)</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-sqlxml"/>; </p>
			</richtext>
		</annotation>
	</reference>
	<reference name="iso9541">
		<names type="author">
			<name>International Organization for Standardization</name>
		</names>
		<date value="1994"/>
		<howpublished>ISO/IEC 9541</howpublished>
		<title>Information Technology — Font Information Interchange</title>
	</reference>
	<reference name="iso9541-1">
		<names type="author">
			<name>International Organization for Standardization</name>
		</names>
		<date value="1994"/>
		<howpublished>ISO/IEC 9541-1</howpublished>
		<title>Information Technology — Font Information Interchange — Part 1: Architecture</title>
		<identifier type="uri">http://www.iso.ch/iso/en/CatalogueDetailPage.CatalogueDetail?CSNUMBER=17277</identifier>
	</reference>
	<reference name="iso9573">
		<names type="author">
			<name>International Organization for Standardization</name>
		</names>
		<date value="1988-12"/>
		<howpublished>ISO/IEC 9573</howpublished>
		<title>Information Processing — SGML Support Facilities — Techniques for using SGML</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-sgml" weight="0.8"/>; </p>
			</richtext>
		</annotation>
		<identifier type="uri">http://www.iso.org/iso/en/CatalogueDetailPage.CatalogueDetail?CSNUMBER=17319</identifier>
	</reference>
	<reference name="iso9573-11">
		<names type="author">
			<name>International Organization for Standardization</name>
		</names>
		<date value="2004-04"/>
		<abstract>
			<richtext>
				<p>ISO/IEC TR 9573-11:2004 defines the document structures and style specifications for standards document interchange (in particular, ISO standards). Element types and attributes for ISO standards are defined and two profiles (a database-oriented profile and a document-oriented profile) are provided. The document structures are described by an SGML (ISO 8879) DTD, an XML DTD, and a RELAX NG (ISO/IEC 19757-2) schema. The style specifications are described by DSSSL (ISO/IEC 10179), XSLT, and XSL. Rendering examples and a list of processing tools are provided for information.</p>
			</richtext>
		</abstract>
		<howpublished>ISO/IEC 9573-11</howpublished>
		<title>Information Processing — SGML Support Facilities — Part 11: Structure Descriptions and Style Specifications for Standards Document Interchange</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-iso" weight="0.9"/>; </p>
			</richtext>
		</annotation>
		<identifier type="uri">http://www.iso.org/iso/en/CatalogueDetailPage.CatalogueDetail?CSNUMBER=38368</identifier>
	</reference>
	<reference name="iso9573-13">
		<names type="author">
			<name>International Organization for Standardization</name>
		</names>
		<date value="2003-07"/>
		<howpublished>ISO/IEC 9573-13</howpublished>
		<title>Information Processing — SGML Support Facilities — Techniques for using SGML — Part 13: Public Entity Sets for Mathematics and Science</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-sgml" weight="0.8"/>; </p>
			</richtext>
		</annotation>
		<identifier type="uri">http://www.iso.org/iso/en/CatalogueDetailPage.CatalogueDetail?CSNUMBER=17332</identifier>
	</reference>
	<reference name="iso9660">
		<names type="author">
			<name>International Organization for Standardization</name>
		</names>
		<date value="2005-01"/>
		<abstract>
			<richtext>
				<p>Specifies the volume and file structure of compact read-only optical disks (CD-ROM) for the information interchange between information processing systems. Defines: the attributes of the volume and the descriptors recorded on it; the relationship among volumes of a volume set; the placement of files; the attributes of the files; recorded structures intended for input or output data streams of an application program when required to be organized as sets of records; three nested levels of medium interchange; two nested levels of implementation; requirements for the processes provided within information processing systems.</p>
			</richtext>
		</abstract>
		<howpublished>ISO 9660</howpublished>
		<title>Information Processing — Volume and file structure of CD-ROM for information interchange</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-cdrom"/>; <keywordref type="topic-iso9660"/>; </p>
			</richtext>
		</annotation>
		<identifier type="uri">http://www.iso.org/iso/en/CatalogueDetailPage.CatalogueDetail?CSNUMBER=17505</identifier>
	</reference>
	<reference name="iso9753">
		<names type="author">
			<name>International Organization for Standardization</name>
		</names>
		<date value="1998"/>
		<howpublished>ISO/IS 9753</howpublished>
		<field type="bibtex:index">EDI, EDIFACT, UN/EDIFACT</field>
		<title>Electronic data interchange for administration, commerce and transport (EDIFACT) — Application level syntax rules (Syntax version number: 4)</title>
	</reference>
	<reference name="iso9945-1">
		<names type="author">
			<name>International Organization for Standardization</name>
		</names>
		<date value="1996"/>
		<howpublished>ISO/IEC 9945-1</howpublished>
		<title>Information Technology — Portable Operating System Interface (POSIX) — Part 1: System Application Program Interface (API) [C Language]</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-posix"/>; </p>
			</richtext>
		</annotation>
	</reference>
	<reference name="iso9945-2">
		<names type="author">
			<name>International Organization for Standardization</name>
		</names>
		<date value="1993"/>
		<howpublished>ISO/IEC 9945-2</howpublished>
		<title>Information Technology — Portable Operating System Interface (POSIX) — Part 2: Shell and Utilities</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-posix"/>; <keywordref type="topic-bre" weight="0.9"/>; <keywordref type="topic-ere" weight="0.9"/>; </p>
			</richtext>
		</annotation>
	</reference>
	<reference name="iso10149">
		<names type="author">
			<name>International Organization for Standardization</name>
		</names>
		<date value="1995"/>
		<howpublished>ISO/IEC 10149</howpublished>
		<title>Information Technology — Data interchange on read-only 120 mm optical data disks (CD-ROM)</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-cdrom"/>; </p>
			</richtext>
		</annotation>
	</reference>
	<reference name="iso10179">
		<names type="author">
			<name>International Organization for Standardization</name>
		</names>
		<date value="2001-08"/>
		<abstract>
			<richtext>
				<p>Specifies the processing of valid Standard Generalized Markup Language (SGML) documents. Document Style Semantics and Specification Language (DSSSL) defines the semantics, syntax, and processing model of languages for the specification of documentation processing. Provides means for externalization of style characteristics and other techniques for associating style information with an SGML document.</p>
			</richtext>
		</abstract>
		<howpublished>ISO/IEC 10179</howpublished>
		<title>Information Technology — Processing languages — Document Style Semantics and Specification Language (DSSSL)</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-dsssl"/>; (undefined keyword: sdql); </p>
			</richtext>
		</annotation>
		<identifier type="uri">http://www.iso.org/iso/en/CatalogueDetailPage.CatalogueDetail?CSNUMBER=18196</identifier>
	</reference>
	<reference name="iso10180">
		<names type="author">
			<name>International Organization for Standardization</name>
		</names>
		<date value="1995"/>
		<howpublished>ISO/IEC 10180</howpublished>
		<title>Information Technology — Processing languages — Standard Page Description Language (SPDL)</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-spdl"/>; </p>
			</richtext>
		</annotation>
	</reference>
	<reference name="iso10646">
		<names type="author">
			<name>International Organization for Standardization</name>
		</names>
		<date value="1993"/>
		<howpublished>ISO/IEC 10646</howpublished>
		<title>Information Technology — Universal Multiple-Octet Coded Character Set (UCS)</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-ucs"/>; </p>
			</richtext>
		</annotation>
	</reference>
	<reference name="iso10646-a1">
		<names type="author">
			<name>International Organization for Standardization</name>
		</names>
		<date value="1996"/>
		<howpublished>ISO/IEC 10646 (Amendment 1)</howpublished>
		<title>Transformation Format for 16 planes of group 00 (UTF-16)</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-utf16"/>; <keywordref type="topic-ucs" weight="0.8"/>; </p>
			</richtext>
		</annotation>
	</reference>
	<reference name="iso10744">
		<names type="author">
			<name>International Organization for Standardization</name>
		</names>
		<date value="1997"/>
		<howpublished>ISO/IEC 10744</howpublished>
		<title>Information Technology — Hypermedia/Time-based Structuring Language (HyTime)</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-hytime"/>; </p>
			</richtext>
		</annotation>
	</reference>
	<reference name="iso10746">
		<names type="author">
			<name>International Organization for Standardization</name>
		</names>
		<date value="1998"/>
		<howpublished>ISO/IEC 10746</howpublished>
		<title>Information Technology — Open Distributed Processing — Reference Model</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-odp"/>; </p>
			</richtext>
		</annotation>
	</reference>
	<reference name="iso10746-1">
		<names type="author">
			<name>International Organization for Standardization</name>
		</names>
		<date value="2003-02"/>
		<howpublished>ISO/IEC 10746-1:1998</howpublished>
		<title>Information Technology — Open Distributed Processing — Reference Model: Overview</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-odp"/>; </p>
			</richtext>
		</annotation>
		<identifier type="uri">http://standards.iso.org/ittf/PubliclyAvailableStandards/c020696_ISO_IEC_10746-1_1998(E).zip</identifier>
	</reference>
	<reference name="iso10746-2">
		<names type="author">
			<name>International Organization for Standardization</name>
		</names>
		<date value="2001-08"/>
		<howpublished>ISO/IEC 10746-2:1996</howpublished>
		<title>Information Technology — Open Distributed Processing — Reference Model: Foundations</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-odp"/>; </p>
			</richtext>
		</annotation>
		<identifier type="uri">http://standards.iso.org/ittf/PubliclyAvailableStandards/s018836_ISO_IEC_10746-2_1996(E).zip</identifier>
	</reference>
	<reference name="iso10746-3">
		<names type="author">
			<name>International Organization for Standardization</name>
		</names>
		<date value="2001-08"/>
		<howpublished>ISO/IEC 10746-3:1996</howpublished>
		<title>Information Technology — Open Distributed Processing — Reference Model: Architecture</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-odp"/>; </p>
			</richtext>
		</annotation>
		<identifier type="uri">http://standards.iso.org/ittf/PubliclyAvailableStandards/s020697_ISO_IEC_10746-3_1996(E).zip</identifier>
	</reference>
	<reference name="iso10746-4">
		<names type="author">
			<name>International Organization for Standardization</name>
		</names>
		<date value="2003-02"/>
		<howpublished>ISO/IEC 10746-4:1998</howpublished>
		<title>Information Technology — Open Distributed Processing — Reference Model: Architectural Semantics</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-odp"/>; </p>
			</richtext>
		</annotation>
		<identifier type="uri">http://standards.iso.org/ittf/PubliclyAvailableStandards/c020698_ISO_IEC_10746-4_1998(E).zip</identifier>
	</reference>
	<reference name="iso10918">
		<names type="author">
			<name>International Organization for Standardization</name>
		</names>
		<date value="1999"/>
		<howpublished>ISO/IEC 10918</howpublished>
		<title>Information technology — Digital compression and coding of continuous-tone still images</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-jpeg"/>; </p>
			</richtext>
		</annotation>
	</reference>
	<reference name="iso10918-1">
		<names type="author">
			<name>International Organization for Standardization</name>
		</names>
		<date value="1994"/>
		<howpublished>ISO/IEC 10918-1</howpublished>
		<title>Information technology — Digital compression and coding of continuous-tone still images: Requirements and guidelines</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-jpeg"/>; </p>
			</richtext>
		</annotation>
	</reference>
	<reference name="iso10918-2">
		<names type="author">
			<name>International Organization for Standardization</name>
		</names>
		<date value="1995"/>
		<howpublished>ISO/IEC 10918-2</howpublished>
		<title>Information technology — Digital compression and coding of continuous-tone still images: Compliance testing</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-jpeg"/>; </p>
			</richtext>
		</annotation>
	</reference>
	<reference name="iso10918-3">
		<names type="author">
			<name>International Organization for Standardization</name>
		</names>
		<date value="1997"/>
		<howpublished>ISO/IEC 10918-3</howpublished>
		<title>Information technology — Digital compression and coding of continuous-tone still images: Extensions</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-jpeg"/>; </p>
			</richtext>
		</annotation>
	</reference>
	<reference name="iso10918-4">
		<names type="author">
			<name>International Organization for Standardization</name>
		</names>
		<date value="1999"/>
		<howpublished>ISO/IEC 10918-4</howpublished>
		<title>Information technology — Digital compression and coding of continuous-tone still images: Registration of JPEG profiles, SPIFF profiles, SPIFF tags, SPIFF colour spaces, APPN markers, SPIFF compression types and Registration Authorities (REGAUT)</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-jpeg" weight="0.9"/>; <keywordref type="topic-spiff"/>; </p>
			</richtext>
		</annotation>
	</reference>
	<reference name="iso11172">
		<names type="author">
			<name>International Organization for Standardization</name>
		</names>
		<date value="1998"/>
		<howpublished>ISO/IEC 11172</howpublished>
		<title>Information technology — Coding of moving pictures and associated audio for digital storage media at up to about 1.5 Mbit/s</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-mpeg1"/>; </p>
			</richtext>
		</annotation>
	</reference>
	<reference name="iso11172-3">
		<names type="author">
			<name>International Organization for Standardization</name>
		</names>
		<date value="1999-03"/>
		<howpublished>ISO/IEC 11172-3</howpublished>
		<title>Information Technology — Coding of Poving Pictures and Associated Audio for Digital Storage Media at up to about 1.5 Mbit/s — Part 3: Audio</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-mp3"/>; <keywordref type="topic-mpeg1"/>; </p>
			</richtext>
		</annotation>
		<identifier type="uri">http://www.iso.ch/iso/en/CatalogueDetailPage.CatalogueDetail?CSNUMBER=22412</identifier>
	</reference>
	<reference name="iso11544">
		<names type="author">
			<name>International Organization for Standardization</name>
		</names>
		<date value="1993"/>
		<howpublished>ISO/IEC 11544</howpublished>
		<title>Information Technology — Coded Representation of Picture and Audio Information — Progressive Bi-level Image Compression</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-jbig"/>; </p>
			</richtext>
		</annotation>
	</reference>
	<reference name="iso11578">
		<names type="author">
			<name>International Organization for Standardization</name>
		</names>
		<date value="1996"/>
		<howpublished>ISO/IEC 11578</howpublished>
		<title>Information Technology — Open Systems Interconnection (OSI) — Remote Procedure Call (RPC)</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-isorpc" weight="0.9"/>; <keywordref type="topic-osi" weight="0.8"/>; </p>
			</richtext>
		</annotation>
	</reference>
	<reference name="iso12083">
		<names type="author">
			<name>International Organization for Standardization</name>
		</names>
		<date value="1994"/>
		<abstract>
			<richtext>
				<p>Presents four document type definitions and additional facilities conforming to ISO 8879. Intended to provide document architectures for the creation and interchange of books, articles and serial publications. Specifies the SGML declaration defining the syntax used by the document type definitions and document instances; the document type definitions for the document classes books, articles, serials; a document type definition for Mathematics which may be embedded in other SGML applications.</p>
			</richtext>
		</abstract>
		<howpublished>ISO 12083</howpublished>
		<title>Information and Documentation — Electronic Manuscript Preparation and Markup</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-mathml"/>; </p>
			</richtext>
		</annotation>
		<identifier type="uri">http://www.iso.ch/iso/en/CatalogueDetailPage.CatalogueDetail?CSNUMBER=20866</identifier>
		<identifier type="uri">http://www.techstreet.com/cgi-bin/detail?product_id=52643</identifier>
	</reference>
	<reference name="iso12234-2">
		<names type="author">
			<name>International Organization for Standardization</name>
		</names>
		<date value="2001-10"/>
		<howpublished>ISO 12234-2</howpublished>
		<title>Electronic Still-Picture Imaging — Removable Memory — Part 2: TIFF/EP Image Data Format</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-tiffep"/>; </p>
			</richtext>
		</annotation>
		<identifier type="uri">http://www.iso.org/iso/en/CatalogueDetailPage.CatalogueDetail?CSNUMBER=29377</identifier>
	</reference>
	<reference name="iso12639">
		<names type="author">
			<name>International Organization for Standardization</name>
		</names>
		<date value="2000-05"/>
		<howpublished>ISO 12639</howpublished>
		<field type="bibtex:index">TIFF, TIFF/IT</field>
		<title>Graphic Technology — Prepress Digital Data Exchange — Tag Image File Format for Image Technology (TIFF/IT)</title>
		<identifier type="uri">http://www.iso.ch/iso/en/CatalogueDetailPage.CatalogueDetail?CSNUMBER=2181</identifier>
	</reference>
	<reference name="iso13236">
		<names type="author">
			<name>International Organization for Standardization</name>
		</names>
		<date value="1998"/>
		<howpublished>ISO/IEC 13236</howpublished>
		<field type="bibtex:index">ITU Q.19/Q.2</field>
		<title>Information Technology — Quality of Service — Framework</title>
	</reference>
	<reference name="iso13250">
		<names type="author">
			<name>International Organization for Standardization</name>
		</names>
		<date value="2000"/>
		<howpublished>ISO/IEC 13250</howpublished>
		<title>Information Technology — SGML Applications — Topic Maps</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-topicmaps"/>; </p>
			</richtext>
		</annotation>
	</reference>
	<reference name="iso13346">
		<names type="author">
			<name>International Organization for Standardization</name>
		</names>
		<date value="1995"/>
		<howpublished>ISO/IEC 13346</howpublished>
		<title>Information Technology — Volume and file structure of write-once and rewritable media using non-sequential recording for information interchange</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-iso13346"/>; </p>
			</richtext>
		</annotation>
	</reference>
	<reference name="iso13818">
		<names type="author">
			<name>International Organization for Standardization</name>
		</names>
		<date value="1999"/>
		<howpublished>ISO/IEC 13818</howpublished>
		<title>Information Technology — Generic coding of moving pictures and associated audio information</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-mpeg2"/>; </p>
			</richtext>
		</annotation>
	</reference>
	<reference name="iso13818-3">
		<names type="author">
			<name>International Organization for Standardization</name>
		</names>
		<date value="1998"/>
		<howpublished>ISO/IEC 13818-3</howpublished>
		<field type="bibtex:index">MPEG-2, BC</field>
		<title>Information Technology — Generic coding of moving pictures and associated audio information — Part 3: Audio</title>
	</reference>
	<reference name="iso13818-7">
		<names type="author">
			<name>International Organization for Standardization</name>
		</names>
		<date value="1997"/>
		<howpublished>ISO/IEC 13818-7</howpublished>
		<field type="bibtex:index">MPEG-2, AAC</field>
		<title>Information Technology — Generic coding of moving pictures and associated audio information — Part 7: Advanced Audio Coding (AAC)</title>
	</reference>
	<reference name="iso14496">
		<names type="author">
			<name>International Organization for Standardization</name>
		</names>
		<date value="1998"/>
		<howpublished>ISO/IEC DIS 14496</howpublished>
		<field type="bibtex:index">MPEG-4</field>
		<title>Information Technology — Coding of audio-visual objects</title>
	</reference>
	<reference name="iso14496-3">
		<names type="author">
			<name>International Organization for Standardization</name>
		</names>
		<date value="1998"/>
		<howpublished>ISO/IEC DIS 14496-3</howpublished>
		<field type="bibtex:index">MPEG-4</field>
		<title>Information Technology — Coding of audio-visual objects — Part 3: Audio</title>
	</reference>
	<reference name="iso14750">
		<names type="author">
			<name>International Organization for Standardization</name>
		</names>
		<date value="1999"/>
		<howpublished>ISO/IEC 14750</howpublished>
		<title>Information Technology — Open Distributed Processing — Interface Definition Language</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-odp" weight="0.9"/>; <keywordref type="topic-idl"/>; </p>
			</richtext>
		</annotation>
	</reference>
	<reference name="iso14772">
		<names type="author">
			<name>International Organization for Standardization</name>
		</names>
		<date value="1997-12"/>
		<howpublished>ISO/IEC 14772</howpublished>
		<title>Information Technology — Virtual Reality Modeling Language (VRML)</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-vrml"/>; </p>
			</richtext>
		</annotation>
	</reference>
	<reference name="iso14977">
		<names type="author">
			<name>International Organization for Standardization</name>
		</names>
		<date value="2001-08"/>
		<abstract>
			<richtext>
				<p>Defines a notation, Extended BNF, for specifying the syntax of a linear sequence of symbols. It defines both the logical structure of the notation and its graphical representation.</p>
			</richtext>
		</abstract>
		<howpublished>ISO/IEC 14977</howpublished>
		<title>Information Technology — Syntactic Metalanguage — Extended BNF</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-ebnf"/>; </p>
			</richtext>
		</annotation>
		<identifier type="uri">http://www.iso.ch/iso/en/CatalogueDetailPage.CatalogueDetail?CSNUMBER=26153</identifier>
	</reference>
	<reference name="iso15022">
		<names type="author">
			<name>International Organization for Standardization</name>
		</names>
		<date value="2002-01"/>
		<howpublished>ISO 15022</howpublished>
		<title>Securities — Scheme for Messages (Data Field Dictionary)</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-uml" weight="0.7"/>; <keywordref type="topic-xmlschema" weight="0.7"/>; </p>
			</richtext>
		</annotation>
		<identifier type="uri">http://www.iso.ch/iso/en/CatalogueDetailPage.CatalogueDetail?CSNUMBER=25775</identifier>
	</reference>
	<reference name="iso15444">
		<names type="author">
			<name>International Organization for Standardization</name>
		</names>
		<date value="2002-07"/>
		<howpublished>ISO/IEC 15444</howpublished>
		<title>Information Technology — JPEG 2000 Image Coding System</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-jpeg2000"/>; </p>
			</richtext>
		</annotation>
		<identifier type="uri">http://www.iso.ch/iso/en/CatalogueDetailPage.CatalogueDetail?CSNUMBER=27687</identifier>
	</reference>
	<reference name="iso15445">
		<names type="author">
			<name>International Organization for Standardization</name>
		</names>
		<date value="2000-05"/>
		<howpublished>ISO/IEC 15445</howpublished>
		<field type="bibtex:src">EW: ~/papers/bibtex/</field>
		<title>Information Technology — Document Description and Processing Languages — HyperText Markup Language (HTML)</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-html"/>; </p>
			</richtext>
		</annotation>
		<identifier type="uri">http://www.iso.ch/iso/en/CatalogueDetailPage.CatalogueDetail?CSNUMBER=27688</identifier>
	</reference>
	<reference name="iso15836">
		<names type="author">
			<name>International Organization for Standardization</name>
		</names>
		<date value="2003-11"/>
		<abstract>
			<richtext>
				<p>ISO 15836:2003 is applicable to the Dublin Core metadata element set which deals with cross-domain information resource description. For Dublin Core applications, a resource will typically be an electronic document. ISO 15836:2003 is for the element set only, which is generally used in the context of a specific project or application. Local or community based requirements and policies may impose additional restrictions, rules, and interpretations. It is not the purpose of ISO 15836:2003 to define the detailed criteria by which the element set will be used with specific projects and applications.</p>
			</richtext>
		</abstract>
		<howpublished>ISO 15836</howpublished>
		<title>Information and Documentation — The Dublin Core Metadata Element Set</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-dublincore"/>; </p>
			</richtext>
		</annotation>
		<associations>
			<xref type="updates" target="rfc2413"/>
		</associations>
		<identifier type="uri">http://www.iso.org/iso/en/CatalogueDetailPage.CatalogueDetail?CSNUMBER=37629</identifier>
	</reference>
	<reference name="iso15948">
		<names type="author">
			<name>International Organization for Standardization</name>
		</names>
		<date value="2004-03"/>
		<abstract>
			<richtext>
				<p>ISO/IEC 15948:2004 specifies a datastream and an associated file format, Portable Network Graphics (PNG, pronounced "ping"), for a lossless, portable, compressed individual computer graphics image transmitted across the Internet. Indexed-colour, greyscale, and truecolour images are supported, with optional transparency. Sample depths range from 1 to 16 bits. PNG is fully streamable with a progressive display option. It is robust, providing both full file integrity checking and simple detection of common transmission errors. PNG can store gamma and chromaticity data as well as a full ICC colour profile for accurate colour matching on heterogenous platforms. ISO/IEC 15948:2004 defines the Internet Media type "image/png". The datastream and associated file format have value outside of the main design goal.</p>
			</richtext>
		</abstract>
		<howpublished>ISO/IEC 15948:2004</howpublished>
		<title>Information Technology — Computer Graphics and Image Processing — Portable Network Graphics (PNG): Functional specification</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-png"/>; </p>
			</richtext>
		</annotation>
		<associations>
			<xref type="updates" target="png"/>
		</associations>
		<identifier type="uri">http://www.iso.org/iso/en/CatalogueDetailPage.CatalogueDetail?CSNUMBER=29581</identifier>
	</reference>
	<reference name="iso16262">
		<names type="author">
			<name>International Organization for Standardization</name>
		</names>
		<date value="2002-06-03"/>
		<abstract>
			<richtext>
				<p>ISO/IEC 16262:2002 defines the ECMAScript scripting language.</p>
			</richtext>
		</abstract>
		<howpublished>ISO/IEC 16262</howpublished>
		<title>Information Technology — ECMAScript Language Specification</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-ecmascript"/>; </p>
			</richtext>
		</annotation>
		<identifier type="uri">http://www.iso.ch/iso/en/CatalogueDetailPage.CatalogueDetail?CSNUMBER=33835</identifier>
	</reference>
	<reference name="iso19757-1">
		<names type="author">
			<name>International Organization for Standardization</name>
		</names>
		<date value="2005-02"/>
		<howpublished>ISO/IEC 19757-1</howpublished>
		<title>Information Technology — Document Schema Definition Languages (DSDL) — Part 1: Overview</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-dsdl"/>; </p>
			</richtext>
		</annotation>
		<identifier type="uri">http://www.iso.org/iso/en/CatalogueDetailPage.CatalogueDetail?CSNUMBER=37606</identifier>
	</reference>
	<reference name="iso19115">
		<names type="author">
			<name>International Organization for Standardization</name>
		</names>
		<date value="2003-05"/>
		<abstract>
			<richtext>
				<p>ISO 19115:2003 defines the schema required for describing geographic information and services. It provides information about the identification, the extent, the quality, the spatial and temporal schema, spatial reference, and distribution of digital geographic data. ISO 19115:2003 is applicable to the cataloguing of datasets, clearinghouse activities, and the full description of datasets; geographic datasets, dataset series, and individual geographic features and feature properties. ISO 19115:2003 defines: mandatory and conditional metadata sections, metadata entities, and metadata elements; the minimum set of metadata required to serve the full range of metadata applications (data discovery, determining data fitness for use, data access, data transfer, and use of digital data); optional metadata elements — to allow for a more extensive standard description of geographic data, if required; a method for extending metadata to fit specialized needs. Though ISO 19115:2003 is applicable to digital data, its principles can be extended to many other forms of geographic data such as maps, charts, and textual documents as well as non-geographic data.</p>
			</richtext>
		</abstract>
		<howpublished>ISO 19115:2003</howpublished>
		<title>Geographic Information — Metadata</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-metadata"/>; </p>
			</richtext>
		</annotation>
		<identifier type="uri">http://www.iso.org/iso/en/CatalogueDetailPage.CatalogueDetail?CSNUMBER=26020</identifier>
	</reference>
	<reference name="iso19757-2">
		<names type="author">
			<name>International Organization for Standardization</name>
		</names>
		<date value="2003-11"/>
		<abstract>
			<richtext>
				<p>ISO/IEC 19757-2:2003 specifies RELAX NG, a schema language for XML. A RELAX NG schema specifies a pattern for the structure and content of an XML document. The pattern is specified by using a regular tree grammar. A RELAX NG schema is itself an XML document. ISO/IEC 19757-2:2003 specifies when an XML document is a correct RELAX NG schema; and when an XML document is valid with respect to a correct RELAX NG schema.</p>
			</richtext>
		</abstract>
		<howpublished>ISO/IEC 19757-2</howpublished>
		<title>Information Technology — Document Schema Definition Languages (DSDL) — Part 2: Grammar-based Validation — RELAX NG</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-relaxng"/>; </p>
			</richtext>
		</annotation>
		<identifier type="uri">http://www.iso.org/iso/en/CatalogueDetailPage.CatalogueDetail?CSNUMBER=37605</identifier>
		<identifier type="uri">http://standards.iso.org/ittf/PubliclyAvailableStandards/c037605_ISO_IEC_19757-2_2003(E).zip</identifier>
	</reference>
	<reference name="iso19757-3">
		<names type="author">
			<name>International Organization for Standardization</name>
		</names>
		<date value="2006-04"/>
		<howpublished>ISO/IEC 19757-3</howpublished>
		<title>Information Technology — Document Schema Definition Languages (DSDL) — Part 3: Rule-based Validation — Schematron</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-schematron"/>; </p>
			</richtext>
		</annotation>
		<identifier type="uri">http://www.iso.org/iso/en/CatalogueDetailPage.CatalogueDetail?CSNUMBER=40833</identifier>
		<identifier type="uri">http://standards.iso.org/ittf/PubliclyAvailableStandards/c040833_ISO_IEC_19757-3_2006(E).zip</identifier>
	</reference>
	<reference name="iso19757-4">
		<names type="author">
			<name>International Organization for Standardization</name>
		</names>
		<date value="2006-06"/>
		<howpublished>ISO/IEC 19757-4:2006</howpublished>
		<title>Information Technology — Document Schema Definition Languages (DSDL) — Part 4: Namespace-based Validation Dispatching Language — NVDL</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-nvdl"/>; </p>
			</richtext>
		</annotation>
		<identifier type="uri">http://www.iso.org/iso/en/CatalogueDetailPage.CatalogueDetail?CSNUMBER=38615</identifier>
		<identifier type="uri">http://standards.iso.org/ittf/PubliclyAvailableStandards/c038615_ISO_IEC_19757-4_2006(E).zip</identifier>
	</reference>
	<reference name="iso19757-5">
		<names type="author">
			<name>International Organization for Standardization</name>
		</names>
		<date value="2004-09"/>
		<howpublished>ISO/IEC 19757-5</howpublished>
		<title>Information Technology — Document Schema Definition Languages (DSDL) — Part 4: Datatype Library Language (DTLL)</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-dtll"/>; </p>
			</richtext>
		</annotation>
		<identifier type="uri" resourceType="text/html">http://dsdl.org/0546.htm</identifier>
	</reference>
	<reference name="iso19757-8">
		<names type="author">
			<name>International Organization for Standardization</name>
		</names>
		<date value="2004-11"/>
		<howpublished>ISO/IEC 19757-8 (under development)</howpublished>
		<title>Information Technology — Document Schema Definition Languages (DSDL) — Part 8: Document Schema Renaming Language — DSRL</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-dsrl"/>; </p>
			</richtext>
		</annotation>
	</reference>
	<reference name="iso19793">
		<names type="author">
			<name>International Organization for Standardization</name>
		</names>
		<date value="2005-05"/>
		<howpublished>ISO/IEC CD 19793</howpublished>
		<title>Information Technology — Open Distributed Processing — Use of UML for ODP System Specifications</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-odp" weight="0.9"/>; <keywordref type="topic-uml" weight="0.7"/>; </p>
			</richtext>
		</annotation>
	</reference>
	<reference name="iso21961">
		<names type="author">
			<name>International Organization for Standardization</name>
		</names>
		<date value="2003-03"/>
		<howpublished>ISO 21961</howpublished>
		<title>Space Data and Information Transfer Systems — Data Entity Dictionary Specification Language (DEDSL) — Abstract Syntax</title>
		<annotation>
			<richtext>
				<p>Keywords: (undefined keyword: desdl); </p>
			</richtext>
		</annotation>
		<identifier type="uri">http://www.iso.ch/iso/en/CatalogueDetailPage.CatalogueDetail?CSNUMBER=36036</identifier>
	</reference>
	<reference name="iso21962">
		<names type="author">
			<name>International Organization for Standardization</name>
		</names>
		<date value="2003-03"/>
		<howpublished>ISO 21962</howpublished>
		<title>Space Data and Information Transfer Systems — Data Entity Dictionary Specification Language (DEDSL) — PVL Syntax</title>
		<annotation>
			<richtext>
				<p>Keywords: (undefined keyword: desdl); (undefined keyword: pvl); </p>
			</richtext>
		</annotation>
		<identifier type="uri">http://www.iso.ch/iso/en/CatalogueDetailPage.CatalogueDetail?CSNUMBER=36037</identifier>
	</reference>
	<reference name="iso22537">
		<names type="author">
			<name>International Organization for Standardization</name>
		</names>
		<date value="2006-02"/>
		<abstract>
			<richtext>
				<p>ISO/IEC 20537:2005 defines the syntax and semantics of ECMAScript for XML (E4X), a set of programming language extensions adding native XML support to ECMAScript.</p>
			</richtext>
		</abstract>
		<howpublished>ISO/IEC 22537:2006</howpublished>
		<title>Information Technology — ECMAScript for XML (E4X) Specification</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-ecmascript" weight="0.9"/>; <keywordref type="topic-xml" weight="0.7"/>; <keywordref type="topic-e4x"/>; </p>
			</richtext>
		</annotation>
		<identifier type="uri">http://www.iso.org/iso/en/CatalogueDetailPage.CatalogueDetail?CSNUMBER=41002</identifier>
		<identifier type="uri">http://standards.iso.org/ittf/PubliclyAvailableStandards/c041002_ISO_IEC_22537_2006(E).zip</identifier>
	</reference>
	<reference name="iso22643">
		<names type="author">
			<name>International Organization for Standardization</name>
		</names>
		<date value="2003-04"/>
		<howpublished>ISO 22643</howpublished>
		<title>Space Data and Information Transfer Systems — Data Entity Dictionary Specification Language (DEDSL) — XML/DTD Syntax</title>
		<annotation>
			<richtext>
				<p>Keywords: (undefined keyword: desdl); </p>
			</richtext>
		</annotation>
		<identifier type="uri">http://www.iso.ch/iso/en/CatalogueDetailPage.CatalogueDetail?CSNUMBER=36377</identifier>
	</reference>
	<reference name="iso23950">
		<names type="author">
			<name>International Organization for Standardization</name>
		</names>
		<date value="1998"/>
		<howpublished>ISO 23950</howpublished>
		<title>Information and Documentation — Information retrieval (Z39.50) — Application service definition and protocol specification</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-z3950"/>; </p>
			</richtext>
		</annotation>
		<associations>
			<xref type="updates" target="z39"/>
		</associations>
		<identifier type="uri">http://www.iso.org/iso/en/CatalogueDetailPage.CatalogueDetail?CSNUMBER=27446</identifier>
	</reference>
	<reference name="iso24824-1">
		<names type="author">
			<name>International Organization for Standardization</name>
		</names>
		<date value="2006-05"/>
		<abstract>
			<richtext>
				<p>ISO/IEC 24824-1:2006 specifies a representation of an instance of the W3C XML Information Set using binary encodings. These binary encodings are specified using the ASN.1 notation and the ASN.1 Encoding Control Notation (ECN). The technology specified in ISO/IEC 24824-1:2006 is called Fast Infoset. This technology provides an alternative to W3C XML syntax as a means of representing instances of the W3C XML Information Set. This representation generally provides smaller encoding sizes and faster processing than a W3C XML representation. ISO/IEC 24824-1:2006 specifies the use of several techniques that minimize the size of the encodings and that maximize the speed of creating and processing Fast Infoset documents. These techniques include the use of dynamic tables (for both character strings and qualified names), initial vocabularies and external vocabularies. ISO/IEC 24824-1:2006 also specifies a Multipurpose Internet Mail Extensions (MIME) media type that identifies a Fast Infoset document.</p>
			</richtext>
		</abstract>
		<howpublished>ISO/IEC FDIS 24824-1</howpublished>
		<title>Information Technology — Generic Applications of ASN.1: Fast Infoset</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-xmlinfoset" weight="0.8"/>; </p>
			</richtext>
		</annotation>
		<identifier type="uri">http://www.iso.org/iso/en/CatalogueDetailPage.CatalogueDetail?CSNUMBER=41327</identifier>
	</reference>
	<reference name="isoects">
		<names type="author">
			<name>International Organization for Standardization</name>
		</names>
		<date value="1995-03"/>
		<address>Beppu</address>
		<howpublished>ISO/IEC JTC1/SC6</howpublished>
		<field type="bibtex:index">ECTS/ECTP</field>
		<title>First Draft of Enhanced Communications Transport Service Definition</title>
	</reference>
	<reference name="isompt">
		<names type="author">
			<name>International Organization for Standardization</name>
		</names>
		<date value="1995-03"/>
		<address>Beppu</address>
		<howpublished>ISO/IEC JTC1/SC6 N9161/IV</howpublished>
		<field type="bibtex:index">ECTS/ECTP</field>
		<title>Draft Text on the Subject of “Multi-peer Taxonomy”</title>
	</reference>
	<reference name="e123">
		<names type="author">
			<name>International Telecommunication Union</name>
		</names>
		<date value="2001-02"/>
		<howpublished>ITU-T Recommendation E.123</howpublished>
		<title>Notation for national and international telephone numbers, e-mail addresses, and Web addresses</title>
	</reference>
	<reference name="e164">
		<names type="author">
			<name>International Telecommunication Union</name>
		</names>
		<date value="1997-05"/>
		<abstract>
			<richtext>
				<p>This Recommendation provides the number structure and functionality for the three categories of numbers used for international public telecommunication — they are geographic areas, global services and Networks. For each of the categories, it details the components of the numbering structure and the digit analysis required to successfully route the calls. Annex A provides additional information on the structure and function of E.164 numbers. Annex B provides information on network identification, service parameters, calling/connected line identity, dialling procedures and addressing for geographic-based ISDN calls. Specific E.164-based applications which differ in usage are defined in separate Recommendations.</p>
			</richtext>
		</abstract>
		<howpublished>ITU-T Recommendation E.164</howpublished>
		<title>The International Public Telecommunication Numbering Plan</title>
		<identifier type="uri">http://www.itu.int/rec/recommendation.asp?type=items&amp;lang=E&amp;parent=T-REC-E.164-199705-I</identifier>
	</reference>
	<reference name="g711">
		<names type="author">
			<name>International Telecommunication Union</name>
		</names>
		<date value="1988-11"/>
		<howpublished>ITU-T Recommendation G.711</howpublished>
		<field type="bibtex:src">http://www.itu.ch/publications</field>
		<title>Pulse code modulation (PCM) of voice frequencies</title>
	</reference>
	<reference name="g726">
		<names type="author">
			<name>International Telecommunication Union</name>
		</names>
		<date value="1990-12"/>
		<howpublished>ITU-T Recommendation G.726</howpublished>
		<field type="bibtex:src">http://www.itu.ch/publications</field>
		<title>40, 32, 24, 16 kbit/s Adaptive Differential Pulse Code Modulation (ADPCM)</title>
	</reference>
	<reference name="g992">
		<names type="author">
			<name>International Telecommunication Union</name>
		</names>
		<date value="1999-06"/>
		<howpublished>ITU-T Recommendation G.992.2</howpublished>
		<field type="bibtex:src">http://www.itu.ch/publications</field>
		<title>Splitterless Asymmetric Digital Subscriber Line (ADSL) transceivers</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-glite"/>; </p>
			</richtext>
		</annotation>
	</reference>
	<reference name="h225">
		<names type="author">
			<name>International Telecommunication Union</name>
		</names>
		<date value="2003-07"/>
		<abstract>
			<richtext>
				<p>This Recommendation covers the technical requirements for narrow-band visual telephone services defined in H.200 and F.720-series Recommendations, in those situations where the transmission path includes one or more packet-based networks, each of which is configured and managed to provide a non-guaranteed Quality of Service (QoS) which is not equivalent to that of N-ISDN, such that additional protection or recovery mechanisms beyond those mandated by ITU-T Rec. H.320 need be provided in the terminals. It is noted that ITU-T Rec. H.322 addresses the use of some other LANs which are able to provide the underlying performance not assumed by the ITU-T Recs H.323 and H.225.0. This Recommendation describes how audio, video, data, and control information on a packet-based network can be managed to provide conversational services in H.323 equipment. Annex G describes methods to allow address resolution between administrative domains in H.323 systems for the purpose of completing calls between the administrative domains. An administrative domain exposes itself to other administrative domains through a type of logical element known as a border element.</p>
			</richtext>
		</abstract>
		<howpublished>ITU-T Recommendation H.225</howpublished>
		<title>Call Signalling Protocols and Media Stream Packetization for Packet-based Multimedia Communication Systems</title>
		<annotation>
			<richtext>
				<p>Keywords: (undefined keyword: h225); </p>
			</richtext>
		</annotation>
		<identifier type="uri">http://www.itu.int/rec/recommendation.asp?type=items&amp;lang=e&amp;parent=T-REC-H.225.0-200307-I</identifier>
	</reference>
	<reference name="h323">
		<names type="author">
			<name>International Telecommunication Union</name>
		</names>
		<date value="2003-07"/>
		<abstract>
			<richtext>
				<p>This Recommendation describes terminals and other entities that provide multimedia communications services over Packet Based Networks (PBN) which may not provide a guaranteed Quality of Service. H.323 entities may provide real-time audio, video and/or data communications. Support for audio is mandatory, while data and video are optional, but if supported, the ability to use a specified common mode of operation is required, so that all terminals supporting that media type can interwork. The packet based network over which H.323 entities communicate may be a point-to-point connection, a single network segment, or an internetwork having multiple segments with complex topologies. H.323 entities may be used in point-to-point, multipoint, or broadcast (as described in ITU-T Rec. H.332) configurations. They may interwork with H.310 terminals on B-ISDN, H.320 terminals on N-ISDN, H.321 terminals on B-ISDN, H.322 terminals on Guaranteed Quality of Service LANs, H.324 terminals on GSTN and wireless networks, V.70 terminals on GSTN, and voice terminals on GSTN or ISDN through the use of Gateways. H.323 entities may be integrated into personal computers or implemented in stand-alone devices such as videotelephones.</p>
			</richtext>
		</abstract>
		<howpublished>ITU-T Recommendation H.323</howpublished>
		<title>Packet-based Multimedia Communications Systems</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-h323"/>; </p>
			</richtext>
		</annotation>
		<identifier type="uri">http://www.itu.int/rec/recommendation.asp?type=items&amp;lang=E&amp;parent=T-REC-H.323-200307-I</identifier>
	</reference>
	<reference name="h350">
		<names type="author">
			<name>International Telecommunication Union</name>
		</names>
		<date value="2003-08"/>
		<abstract>
			<richtext>
				<p>This Recommendation describes a directory services architecture for multimedia conferencing using LDAP. Standardized directory services can support association of persons with endpoints, searchable white pages, and clickable dialling. Directory services can also assist in the configuration of endpoints, and user authentication based on authoritative data sources. This Recommendation describes a standardized LDAP schema to represent endpoints on the network and associate those endpoints with users. It discusses design and implementation considerations for the inter-relation of video and voice-specific directories, enterprise directories, call servers and endpoints.</p>
			</richtext>
		</abstract>
		<howpublished>ITU-T Recommendation H.350</howpublished>
		<title>Directory Services Architecture for Multimedia Conferencing</title>
		<annotation>
			<richtext>
				<p>Keywords: (undefined keyword: h350); </p>
			</richtext>
		</annotation>
		<identifier type="uri">http://www.itu.int/rec/recommendation.asp?type=items&amp;lang=E&amp;parent=T-REC-H.350-200308-I</identifier>
	</reference>
	<reference name="m687">
		<names type="author">
			<name>International Telecommunication Union</name>
		</names>
		<date value="1997-02"/>
		<howpublished>ITU-R Recommendation M.687-2</howpublished>
		<field type="bibtex:index">IMT-2000</field>
		<title>International Mobile Telecommunications 2000 (IMT-2000)</title>
	</reference>
	<reference name="q24">
		<names type="author">
			<name>International Telecommunication Union</name>
		</names>
		<date value="1988-11"/>
		<howpublished>ITU-T Recommendation Q.24</howpublished>
		<field type="bibtex:index">DTMF</field>
		<title>Multifrequency Push-Button Signal Reception</title>
	</reference>
	<reference name="q921">
		<names type="author">
			<name>International Telecommunication Union</name>
		</names>
		<date value="1988"/>
		<howpublished>ITU-T Recommendation Q.921</howpublished>
		<field type="bibtex:src">FG</field>
		<title>ISDN User-Network Interface — Data Link Layer Specification</title>
	</reference>
	<reference name="q931">
		<names type="author">
			<name>International Telecommunication Union</name>
		</names>
		<date value="1988"/>
		<howpublished>ITU-T Recommendation Q.931</howpublished>
		<field type="bibtex:src">FG</field>
		<title>ISDN User-Network Interface Layer 3 Specification for Basic Call Control</title>
	</reference>
	<reference name="q1200">
		<names type="author">
			<name>International Telecommunication Union</name>
		</names>
		<date value="1993-03"/>
		<howpublished>ITU-T Recommendation Q.1200</howpublished>
		<title>Q-Series Intelligent Network Recommendation Structure</title>
	</reference>
	<reference name="q1201">
		<names type="author">
			<name>International Telecommunication Union</name>
		</names>
		<date value="1992-10"/>
		<howpublished>ITU-T Recommendation Q.1201</howpublished>
		<title>Principles of Intelligent Network Architecture</title>
	</reference>
	<reference name="q2931">
		<names type="author">
			<name>International Telecommunication Union</name>
		</names>
		<date value="1995-02"/>
		<howpublished>ITU-T Recommendation Q.2931</howpublished>
		<field type="bibtex:src">/home/tik/doc/ITU/ps</field>
		<title>Broadband Integrated Services Digital Network (B-ISDN) — Digital subscriber signalling system no. 2 (DSS 2) — User-network interface (UNI) — Layer 3 specification for basic call/connection control</title>
	</reference>
	<reference name="q2971">
		<names type="author">
			<name>International Telecommunication Union</name>
		</names>
		<date value="1995-10"/>
		<howpublished>ITU-T Recommendation Q.2971</howpublished>
		<field type="bibtex:src">/home/tik/doc/ITU/ps</field>
		<title>Broadband Integrated Services Digital Network (B-ISDN) — Digital subscriber signalling system no. 2 (DSS 2) — User-network interface layer 3 specification for point-to-multipoint call/connection control</title>
	</reference>
	<reference name="t4">
		<names type="author">
			<name>International Telecommunication Union</name>
		</names>
		<date value="1996-07"/>
		<howpublished>ITU-T Recommendation T.4</howpublished>
		<title>Standardization of Group 3 facsimile terminals for document transmission</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-g3fax"/>; </p>
			</richtext>
		</annotation>
	</reference>
	<reference name="t6">
		<names type="author">
			<name>International Telecommunication Union</name>
		</names>
		<date value="1988-11"/>
		<howpublished>ITU-T Recommendation T.6</howpublished>
		<title>Facsimile coding schemes and coding control functions for Group 4 facsimile apparatus</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-g4fax"/>; </p>
			</richtext>
		</annotation>
	</reference>
	<reference name="t120">
		<names type="author">
			<name>International Telecommunication Union</name>
		</names>
		<date value="1996-07"/>
		<howpublished>ITU-T Recommendation T.120</howpublished>
		<field type="bibtex:src">/home/tik/doc/ITU/ps</field>
		<title>Data protocols for multimedia conferencing</title>
	</reference>
	<reference name="t121">
		<names type="author">
			<name>International Telecommunication Union</name>
		</names>
		<date value="1996-07"/>
		<howpublished>ITU-T Recommendation T.121</howpublished>
		<field type="bibtex:src">/home/tik/doc/ITU/ps</field>
		<title>Generic application template</title>
	</reference>
	<reference name="t122">
		<names type="author">
			<name>International Telecommunication Union</name>
		</names>
		<date value="1993-03"/>
		<howpublished>ITU-T Recommendation T.122</howpublished>
		<field type="bibtex:src">/home/tik/doc/ITU/ps</field>
		<title>Multipoint Communication Service for Audiographics and Audiovisual Conferencing — Service Definition</title>
	</reference>
	<reference name="t123">
		<names type="author">
			<name>International Telecommunication Union</name>
		</names>
		<date value="1994-11"/>
		<howpublished>ITU-T Recommendation T.123</howpublished>
		<field type="bibtex:src">/home/tik/doc/ITU/ps</field>
		<title>Protocol Stack for Audiographics and Audiovisual Teleconference Applications</title>
	</reference>
	<reference name="t124">
		<names type="author">
			<name>International Telecommunication Union</name>
		</names>
		<date value="1995-08"/>
		<howpublished>ITU-T Recommendation T.124</howpublished>
		<field type="bibtex:src">/home/tik/doc/ITU/ps</field>
		<title>Generic Conference Control for Audiovisual and Audiographic Terminals</title>
	</reference>
	<reference name="t125">
		<names type="author">
			<name>International Telecommunication Union</name>
		</names>
		<date value="1994-04"/>
		<howpublished>ITU-T Recommendation T.125</howpublished>
		<field type="bibtex:src">/home/tik/doc/ITU/ps</field>
		<title>Multipoint Communication Service — Protocol Specification</title>
	</reference>
	<reference name="x200">
		<names type="author">
			<name>International Telecommunication Union</name>
		</names>
		<date value="1988"/>
		<howpublished>ITU-T Recommendation X.200</howpublished>
		<field type="bibtex:index">OSI</field>
		<field type="bibtex:src">FG</field>
		<title>Reference Model of Open Systems Interconnection for CCITT Applications</title>
	</reference>
	<reference name="v90">
		<names type="author">
			<name>International Telecommunication Union</name>
		</names>
		<date value="1998-09"/>
		<howpublished>ITU-T Recommendation V.90</howpublished>
		<title>A digital modem and analogue modem pair for use on the Public Switched Telephone Network (PSTN) at data signalling rates of up to 56'000 bit/s downstream and up to 33'600 bit/s upstream</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-v90"/>; <keywordref type="topic-pstn" weight="0.8"/>; <keywordref type="topic-modem" weight="0.9"/>; </p>
			</richtext>
		</annotation>
	</reference>
	<reference name="x208">
		<names type="author">
			<name>International Telecommunication Union</name>
		</names>
		<date value="1988"/>
		<howpublished>ITU-T Recommendation X.208</howpublished>
		<field type="bibtex:src">FG</field>
		<title>Specification of Abstract Syntax Notation One (ASN.1)</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-asn1"/>; </p>
			</richtext>
		</annotation>
	</reference>
	<reference name="x209">
		<names type="author">
			<name>International Telecommunication Union</name>
		</names>
		<date value="1988"/>
		<howpublished>ITU-T Recommendation X.209</howpublished>
		<field type="bibtex:src">FG</field>
		<title>Specification of Basic Encoding Rules for Abstract Syntax Notation One (ASN.1)</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-asn1" weight="0.9"/>; <keywordref type="topic-ber"/>; </p>
			</richtext>
		</annotation>
	</reference>
	<reference name="x219">
		<names type="author">
			<name>International Telecommunication Union</name>
		</names>
		<date value="1988"/>
		<howpublished>ITU-T Recommendation X.219</howpublished>
		<field type="bibtex:index">ISO 9072-1</field>
		<field type="bibtex:src">FG</field>
		<title>Remote Operations: Model, Notation and Service Definition</title>
	</reference>
	<reference name="x227">
		<names type="author">
			<name>International Telecommunication Union</name>
		</names>
		<date value="1988"/>
		<howpublished>ITU-T Recommendation X.227</howpublished>
		<field type="bibtex:index">ISO 8650</field>
		<field type="bibtex:src">FG</field>
		<title>Association Control Protocol Specification</title>
	</reference>
	<reference name="x229">
		<names type="author">
			<name>International Telecommunication Union</name>
		</names>
		<date value="1988"/>
		<howpublished>ITU-T Recommendation X.229</howpublished>
		<field type="bibtex:index">ISO 9072-2</field>
		<field type="bibtex:src">FG</field>
		<title>Remote Operations: Protocol Specification</title>
	</reference>
	<reference name="x400">
		<names type="author">
			<name>International Telecommunication Union</name>
		</names>
		<date value="1996-07"/>
		<howpublished>ITU-T Recommendation X.400</howpublished>
		<field type="bibtex:src">FG</field>
		<title>Message Handling System and Service Overview</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-x400"/>; </p>
			</richtext>
		</annotation>
	</reference>
	<reference name="x419">
		<names type="author">
			<name>International Telecommunication Union</name>
		</names>
		<date value="1995-11"/>
		<howpublished>ITU-T Recommendation X.419</howpublished>
		<field type="bibtex:src">FG</field>
		<title>Information technology — Message Handling Systems (MHS) — Protocol specifications</title>
	</reference>
	<reference name="x500">
		<names type="author">
			<name>International Telecommunication Union</name>
		</names>
		<date value="1993-11"/>
		<howpublished>ITU-T Recommendation X.500</howpublished>
		<field type="bibtex:src">/home/tik/doc/ITU/ps</field>
		<title>The Directory — Overview of Concepts, Models and Services</title>
	</reference>
	<reference name="x501">
		<names type="author">
			<name>International Telecommunication Union</name>
		</names>
		<date value="1993-11"/>
		<howpublished>ITU-T Recommendation X.501</howpublished>
		<field type="bibtex:src">/home/tik/doc/ITU/ps</field>
		<title>The Directory — Models</title>
	</reference>
	<reference name="x509">
		<names type="author">
			<name>International Telecommunication Union</name>
		</names>
		<date value="1993-11"/>
		<howpublished>ITU-T Recommendation X.509</howpublished>
		<field type="bibtex:src">/home/tik/doc/ITU/ps</field>
		<title>The Directory — Authentication framework</title>
	</reference>
	<reference name="x511">
		<names type="author">
			<name>International Telecommunication Union</name>
		</names>
		<date value="1993-11"/>
		<howpublished>ITU-T Recommendation X.511</howpublished>
		<field type="bibtex:src">/home/tik/doc/ITU/ps</field>
		<title>The Directory — Abstract service definition</title>
	</reference>
	<reference name="x518">
		<names type="author">
			<name>International Telecommunication Union</name>
		</names>
		<date value="1993-11"/>
		<howpublished>ITU-T Recommendation X.518</howpublished>
		<field type="bibtex:src">/home/tik/doc/ITU/ps</field>
		<title>The Directory — Procedures for distributed operations</title>
	</reference>
	<reference name="x519">
		<names type="author">
			<name>International Telecommunication Union</name>
		</names>
		<date value="1993-11"/>
		<howpublished>ITU-T Recommendation X.519</howpublished>
		<field type="bibtex:src">/home/tik/doc/ITU/ps</field>
		<title>The Directory — Protocol specifications</title>
	</reference>
	<reference name="x520">
		<names type="author">
			<name>International Telecommunication Union</name>
		</names>
		<date value="1993-11"/>
		<howpublished>ITU-T Recommendation X.520</howpublished>
		<field type="bibtex:src">/home/tik/doc/ITU/ps</field>
		<title>The Directory — Selected attribute types</title>
	</reference>
	<reference name="x521">
		<names type="author">
			<name>International Telecommunication Union</name>
		</names>
		<date value="1993-11"/>
		<howpublished>ITU-T Recommendation X.521</howpublished>
		<field type="bibtex:src">/home/tik/doc/ITU/ps</field>
		<title>The Directory — Selected object classes</title>
	</reference>
	<reference name="x525">
		<names type="author">
			<name>International Telecommunication Union</name>
		</names>
		<date value="1993-11"/>
		<howpublished>ITU-T Recommendation X.525</howpublished>
		<field type="bibtex:src">/home/tik/doc/ITU/ps</field>
		<title>The Directory — Replication</title>
	</reference>
	<reference name="x680">
		<names type="author">
			<name>International Telecommunication Union</name>
		</names>
		<date value="2002-07"/>
		<abstract>
			<richtext>
				<p>This Recommendation provides a notation called Abstract Syntax Notation One (ASN.1) for defining the syntax of information data. It defines a number of simple data types and specifies a notation for referencing these types and for specifying values of these types. The ASN.1 notations can be applied whenever it is necessary to define the abstract syntax of information without constraining in any way how the information is encoded for transmission.</p>
			</richtext>
		</abstract>
		<howpublished>ITU-T Recommendation X.680</howpublished>
		<title>Information Technology — Abstract Syntax Notation One (ASN.1): Specification of Basic Notation</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-asn1"/>; </p>
			</richtext>
		</annotation>
		<associations>
			<xref type="updates" target="x208"/>
		</associations>
		<identifier type="uri" resourceType="application/pdf">http://www.itu.int/ITU-T/studygroups/com17/languages/X.680-0207.pdf</identifier>
	</reference>
	<reference name="x681">
		<names type="author">
			<name>International Telecommunication Union</name>
		</names>
		<date value="2002-07"/>
		<howpublished>ITU-T Recommendation X.681</howpublished>
		<title>Information Technology — Abstract Syntax Notation One (ASN.1): Information Object Specification</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-asn1"/>; </p>
			</richtext>
		</annotation>
		<associations>
			<xref type="updates" target="x208"/>
		</associations>
		<identifier type="uri" resourceType="application/pdf">http://www.itu.int/ITU-T/studygroups/com17/languages/X.681-0207.pdf</identifier>
	</reference>
	<reference name="x682">
		<names type="author">
			<name>International Telecommunication Union</name>
		</names>
		<date value="2002-07"/>
		<howpublished>ITU-T Recommendation X.682</howpublished>
		<title>Information Technology — Abstract Syntax Notation One (ASN.1): Constraint Specification</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-asn1"/>; </p>
			</richtext>
		</annotation>
		<associations>
			<xref type="updates" target="x208"/>
		</associations>
		<identifier type="uri" resourceType="application/pdf">http://www.itu.int/ITU-T/studygroups/com17/languages/X.682-0207.pdf</identifier>
	</reference>
	<reference name="x683">
		<names type="author">
			<name>International Telecommunication Union</name>
		</names>
		<date value="2002-07"/>
		<howpublished>ITU-T Recommendation X.683</howpublished>
		<title>Information Technology — Abstract Syntax Notation One (ASN.1): Parameterization of ASN.1 Specifications</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-asn1"/>; </p>
			</richtext>
		</annotation>
		<associations>
			<xref type="updates" target="x208"/>
		</associations>
		<identifier type="uri" resourceType="application/pdf">http://www.itu.int/ITU-T/studygroups/com17/languages/X.683-0207.pdf</identifier>
	</reference>
	<reference name="x690">
		<names type="author">
			<name>International Telecommunication Union</name>
		</names>
		<date value="2002-07"/>
		<abstract>
			<richtext>
				<p>This Recommendation defines a set of Basic Encoding Rules (BER) that may be applied to values of types defined using the ASN.1 notation. Application of these encoding rules produces a transfer syntax for such values. It is implicit in the specification of these encoding rules that they are also used for decoding. This Recommendation defines also a set of Distinguished Encoding Rules (DER) and a set of Canonical Encoding Rules (CER) both of which provide constraints on the Basic Encoding Rules (BER). The key difference between them is that DER uses the definite length form of encoding while CER uses the indefinite length form. DER is more suitable for the small encoded values, while CER is more suitable for the large ones. It is implicit in the specification of these encoding rules that they are also used for decoding.</p>
			</richtext>
		</abstract>
		<howpublished>ITU-T Recommendation X.690</howpublished>
		<title>Information Technology — ASN.1 Encoding Rules — Specification of Basic Encoding Rules (BER), Canonical Encoding Rules (CER), and Distinguished Encoding Rules (DER)</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-asn1" weight="0.9"/>; <keywordref type="topic-ber"/>; <keywordref type="topic-cer"/>; <keywordref type="topic-der"/>; </p>
			</richtext>
		</annotation>
		<associations>
			<xref type="updates" target="x209"/>
		</associations>
		<identifier type="uri" resourceType="application/pdf">http://www.itu.int/ITU-T/studygroups/com17/languages/X.690-0207.pdf</identifier>
	</reference>
	<reference name="x691">
		<names type="author">
			<name>International Telecommunication Union</name>
		</names>
		<date value="2002-07"/>
		<howpublished>ITU-T Recommendation X.691</howpublished>
		<title>Information Technology — ASN.1 Encoding Rules — Specification of Packed Encoding Rules (PER)</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-asn1" weight="0.9"/>; <keywordref type="topic-per"/>; </p>
			</richtext>
		</annotation>
		<identifier type="uri" resourceType="application/pdf">http://www.itu.int/ITU-T/studygroups/com17/languages/X.691-0207.pdf</identifier>
	</reference>
	<reference name="x692">
		<names type="author">
			<name>International Telecommunication Union</name>
		</names>
		<date value="2002-03"/>
		<howpublished>ITU-T Recommendation X.692</howpublished>
		<title>Information Technology — ASN.1 Encoding Rules — Specification of Encoding Control Notation (ECN)</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-asn1" weight="0.9"/>; (undefined keyword: ecn); </p>
			</richtext>
		</annotation>
		<identifier type="uri" resourceType="application/pdf">http://www.itu.int/ITU-T/studygroups/com17/languages/X.692-0203.pdf</identifier>
	</reference>
	<reference name="x693">
		<names type="author">
			<name>International Telecommunication Union</name>
		</names>
		<date value="2001-12"/>
		<howpublished>ITU-T Recommendation X.693</howpublished>
		<title>Information Technology — ASN.1 Encoding Rules — XML Encoding Rules (XER)</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-asn1" weight="0.9"/>; <keywordref type="topic-xer"/>; </p>
			</richtext>
		</annotation>
		<identifier type="uri" resourceType="application/pdf">http://www.itu.int/ITU-T/studygroups/com17/languages/X.693-0112.pdf</identifier>
	</reference>
	<reference name="x694">
		<names type="author">
			<name>International Telecommunication Union</name>
		</names>
		<date value="2004-01"/>
		<howpublished>ITU-T Recommendation X.694</howpublished>
		<title>Information Technology — ASN.1 Encoding Rules: Mapping W3C XML Schema Definitions into ASN.1</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-asn1" weight="0.9"/>; <keywordref type="topic-xsd" weight="0.8"/>; </p>
			</richtext>
		</annotation>
		<identifier type="uri" resourceType="application/pdf">http://www.itu.int/ITU-T/studygroups/com17/languages/X694.pdf</identifier>
	</reference>
	<reference name="pkcs1">
		<date value="1993-11"/>
		<address>Redwood City, California</address>
		<organization>RSA Laboratories</organization>
		<title>PKCS #1: RSA Encryption Standard</title>
		<annotation>
			<richtext>
				<p>Keywords: (undefined keyword: pkcs1); <keywordref type="topic-rsa"/>; </p>
			</richtext>
		</annotation>
	</reference>
	<reference name="pkcs3">
		<date value="1993-11"/>
		<address>Redwood City, California</address>
		<field type="bibtex:index">PKCS #3</field>
		<organization>RSA Laboratories</organization>
		<title>PKCS #3: Diffie-Hellman Key-Agreement Standard</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-diffiehellman" weight="0.9"/>; </p>
			</richtext>
		</annotation>
	</reference>
	<reference name="pkcs6">
		<date value="1993-11"/>
		<address>Redwood City, California</address>
		<organization>RSA Laboratories</organization>
		<title>PKCS #6: Extended-Certificate Syntax Standard</title>
		<annotation>
			<richtext>
				<p>Keywords: (undefined keyword: pkcs6); </p>
			</richtext>
		</annotation>
	</reference>
	<reference name="pkcs7">
		<date value="1997-05"/>
		<address>Redwood City, California</address>
		<organization>RSA Laboratories</organization>
		<title>PKCS #7: Cryptographic Message Syntax Standard</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-pkcs7"/>; </p>
			</richtext>
		</annotation>
	</reference>
	<reference name="pkcs12">
		<date value="1999-06"/>
		<address>Redwood City, California</address>
		<organization>RSA Laboratories</organization>
		<title>PKCS #12: Personal Information Exchange Syntax</title>
		<annotation>
			<richtext>
				<p>Keywords: (undefined keyword: pkcs12); </p>
			</richtext>
		</annotation>
	</reference>
	<reference name="ecmascript">
		<names type="author">
			<name>European Computer Manufacturers Association</name>
		</names>
		<date value="1999-12"/>
		<edition>3rd</edition>
		<howpublished>Standard ECMA-262</howpublished>
		<title>ECMAScript Language Specification</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-ecmascript"/>; </p>
			</richtext>
		</annotation>
		<identifier type="uri" resourceType="text/html">http://www.ecma-international.org/publications/standards/Ecma-262.htm</identifier>
	</reference>
	<reference name="e4x">
		<names type="author">
			<name>European Computer Manufacturers Association</name>
		</names>
		<date value="2004-06"/>
		<abstract>
			<richtext>
				<p>This standard defines the syntax and semantics of ECMAScript for XML (E4X), a set of programming language extensions adding native XML support to ECMAScript. E4X adds native XML datatypes to the ECMAScript language, extends the semantics of familiar ECMAScript operators for manipulating XML objects and adds a small set of new operators for common XML operations, such as searching and filtering. It also adds support for XML literals, namespaces, qualified names and other mechanisms to facilitate XML processing.</p>
			</richtext>
		</abstract>
		<howpublished>Standard ECMA-357</howpublished>
		<field type="bibtex:index">ecmascript[0.9] e4x[1]</field>
		<title>ECMAScript for XML (E4X) Specification</title>
		<identifier type="uri" resourceType="text/html">http://www.ecma-international.org/publications/standards/Ecma-357.htm</identifier>
	</reference>
	<reference name="ecma365">
		<names type="author">
			<name>European Computer Manufacturers Association</name>
		</names>
		<date value="2005-06"/>
		<abstract>
			<richtext>
				<p>This Ecma Standard specifies the mechanical, physical and optical characteristics of a 60 mm, read-only ODC having a maximum capacity of 1,8 Gbytes. It specifies the physical format, the quality of the recorded signals, the format of the data and its modulation method, thereby allowing for information interchange by means of such ODCs. This Ecma standard specifies two types of ODCs, Type A and Type B. Type A: Single layer disk with maximum recorded capacity of 0,9 G-bytes. Type B: Dual layer disk with maximum recorded capacity of 1,8 G-bytes. Information interchange between systems also requires, at a minimum, agreement between the interchange parties upon the interchange code(s) and the specifications of the structure and labeling of the information on the interchanged ODCs.</p>
			</richtext>
		</abstract>
		<howpublished>Standard ECMA-365</howpublished>
		<field type="bibtex:index">umd[1]</field>
		<title>Data Interchange on 60 mm Read-Only ODC — Capacity: 1,8 Gbytes (UMD)</title>
		<identifier type="uri" resourceType="text/html">http://www.ecma-international.org/publications/standards/Ecma-365.htm</identifier>
	</reference>
	<reference name="exif21">
		<names type="author">
			<name>Japan Electronic Industry Development Association</name>
		</names>
		<date value="1998-06"/>
		<title>Digital Still Camera Image File Format Standard (Exchangeable Image File Format for Digital Still Cameras: EXIF) — Version 2.1</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-exif"/>; </p>
			</richtext>
		</annotation>
	</reference>
	<reference name="exif22">
		<names type="author">
			<name>Japan Electronics and Information Technology Industries Association</name>
		</names>
		<date value="2002-04"/>
		<howpublished>JEITA CP-3451</howpublished>
		<title>Exchangeable Image File Format for Digital Still Cameras: EXIF Version 2.2</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-exif"/>; </p>
			</richtext>
		</annotation>
		<associations>
			<xref type="updates" target="exif21"/>
		</associations>
	</reference>
	<reference name="wap99a">
		<names type="author">
			<name>WAP Forum</name>
		</names>
		<date value="1999-06"/>
		<address>Mountain View, California</address>
		<howpublished>WAP white paper</howpublished>
		<title>Wireless Application Protocol</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-wap1"/>; </p>
			</richtext>
		</annotation>
	</reference>
	<reference name="wap99b">
		<names type="author">
			<name>WAP Forum</name>
		</names>
		<date value="1999-06"/>
		<address>Mountain View, California</address>
		<title>WMLScript Specification</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-wmlscript"/>; </p>
			</richtext>
		</annotation>
	</reference>
	<reference name="wap99c">
		<names type="author">
			<name>WAP Forum</name>
		</names>
		<date value="1999-06"/>
		<address>Mountain View, California</address>
		<title>WAP WML</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-wml"/>; </p>
			</richtext>
		</annotation>
	</reference>
	<reference name="wap99d">
		<names type="author">
			<name>WAP Forum</name>
		</names>
		<date value="1999-06"/>
		<address>Mountain View, California</address>
		<title>WAP Binary XML Content Format</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-wml" weight="0.7"/>; <keywordref type="topic-wbxml"/>; </p>
			</richtext>
		</annotation>
	</reference>
	<reference name="wap99e">
		<names type="author">
			<name>WAP Forum</name>
		</names>
		<date value="1999-05"/>
		<address>Mountain View, California</address>
		<field type="bibtex:index">WAP, WSP</field>
		<title>WAP WSP</title>
	</reference>
	<reference name="wap99f">
		<names type="author">
			<name>WAP Forum</name>
		</names>
		<date value="1999-06"/>
		<address>Mountain View, California</address>
		<field type="bibtex:index">WAP, WTP</field>
		<title>WAP WTP</title>
	</reference>
	<reference name="wap99g">
		<names type="author">
			<name>WAP Forum</name>
		</names>
		<date value="1999-02"/>
		<address>Mountain View, California</address>
		<field type="bibtex:index">WAP, WTLS</field>
		<title>WAP WTLS</title>
	</reference>
	<reference name="wap99h">
		<names type="author">
			<name>WAP Forum</name>
		</names>
		<date value="1999-05"/>
		<address>Mountain View, California</address>
		<field type="bibtex:index">WAP, WDP</field>
		<title>WAP WDP</title>
	</reference>
	<reference name="wap01a">
		<names type="author">
			<name>WAP Forum</name>
		</names>
		<date value="2001-08"/>
		<address>Mountain View, California</address>
		<title>Wireless Application Protocol — WAP 2.0 Technical White Paper</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-wap2"/>; </p>
			</richtext>
		</annotation>
		<associations>
			<xref type="updates" target="wap99a"/>
		</associations>
	</reference>
	<reference name="wap01b">
		<names type="author">
			<name>WAP Forum</name>
		</names>
		<date value="2001-07"/>
		<address>Mountain View, California</address>
		<howpublished>WAP-210-WAPArch-20010712</howpublished>
		<title>Wireless Application Protocol — Architecture Specification</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-wap2"/>; </p>
			</richtext>
		</annotation>
	</reference>
	<reference name="wtai">
		<names type="author">
			<name>WAP Forum</name>
		</names>
		<date value="2001-07"/>
		<address>Mountain View, California</address>
		<howpublished>WAP-268-WTAI-20010715-d</howpublished>
		<title>WAP Wireless Telephony Application Interface</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-wtai"/>; </p>
			</richtext>
		</annotation>
	</reference>
	<reference name="sdmipd">
		<names type="author">
			<name>Secure Digital Music Initiative</name>
		</names>
		<date value="1999-07"/>
		<howpublished>Document pdwg99070802</howpublished>
		<field type="bibtex:index">SDMI</field>
		<title>SDMI Portable Device Specification — Part 1, Version 1.0</title>
	</reference>
	<reference name="xtm10">
		<names type="author">
			<person>
				<givenname>Steve</givenname>
				<surname>Pepper</surname>
			</person>
			<person>
				<givenname>Graham</givenname>
				<surname>Moore</surname>
			</person>
		</names>
		<date value="2001-08"/>
		<howpublished>TopicMaps.Org Specification xtm1-20010806</howpublished>
		<title>XML Topic Maps (XTM) 1.0</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-xtm"/>; </p>
			</richtext>
		</annotation>
		<identifier type="uri" resourceType="text/html">http://www.topicmaps.org/xtm/1.0/xtm1-20010806.html</identifier>
	</reference>
	<reference name="smspp581">
		<names type="author">
			<name>European Telecommunications Standards Institute</name>
		</names>
		<date value="1998-12"/>
		<howpublished>(ETSI TS 300 901, GSM 03.40 version 5.8.1 Release 1996)</howpublished>
		<title>Digital Cellular Telecommunications System (Phase 2+); Technical realization of the Short Message Service (SMS); Point-to-Point (PP)</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-sms"/>; </p>
			</richtext>
		</annotation>
		<identifier type="uri">http://pda.etsi.org/pda/home.asp?wki_id=6822</identifier>
	</reference>
	<reference name="smspp610">
		<names type="author">
			<name>European Telecommunications Standards Institute</name>
		</names>
		<date value="1998-07"/>
		<howpublished>(TS 100 901, GSM 03.40 version 6.1.0 Release 1997)</howpublished>
		<title>Digital Cellular Telecommunications System (Phase 2+); Technical realization of the Short Message Service (SMS); Point-to-Point (PP)</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-sms"/>; </p>
			</richtext>
		</annotation>
		<associations>
			<xref type="updates" target="smspp581"/>
		</associations>
		<identifier type="uri">http://pda.etsi.org/pda/home.asp?wki_id=6491</identifier>
	</reference>
	<reference name="smspp730">
		<names type="author">
			<name>European Telecommunications Standards Institute</name>
		</names>
		<date value="1999-11"/>
		<howpublished>(TS 100 901, GSM 03.40 version 7.3.0 Release 1998)</howpublished>
		<title>Digital Cellular Telecommunications System (Phase 2+); Technical realization of the Short Message Service (SMS); Point-to-Point (PP)</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-sms"/>; </p>
			</richtext>
		</annotation>
		<associations>
			<xref type="updates" target="smspp610"/>
		</associations>
		<identifier type="uri">http://pda.etsi.org/pda/home.asp?wki_id=9942</identifier>
	</reference>
	<reference name="sms750">
		<names type="author">
			<name>European Telecommunications Standards Institute</name>
		</names>
		<date value="2001-12"/>
		<howpublished>(3GPP TS 03.40, Version 7.5.0 Release 1998)</howpublished>
		<title>3rd Generation Partnership Project; Technical Specification Group Terminals; Technical realization of the Short Message Service (SMS)</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-sms"/>; </p>
			</richtext>
		</annotation>
		<associations>
			<xref type="updates" target="smspp730"/>
		</associations>
		<identifier type="uri">http://www.3gpp.org/ftp/Specs/archive/03_series/03.40/0340-750.zip</identifier>
	</reference>
	<reference name="smsalph530">
		<names type="author">
			<name>European Telecommunications Standards Institute</name>
		</names>
		<date value="1996-07"/>
		<howpublished>(GSM 03.38 version 5.3.0)</howpublished>
		<title>Digital Cellular Telecommunications System (Phase 2+); Alphabets and language-specific information</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-sms" weight="0.9"/>; </p>
			</richtext>
		</annotation>
		<identifier type="uri">http://pda.etsi.org/pda/home.asp?wki_id=4690</identifier>
	</reference>
	<reference name="smsalph720">
		<names type="author">
			<name>European Telecommunications Standards Institute</name>
		</names>
		<date value="1999-07"/>
		<howpublished>(ETS 100 900, GSM 03.38 version 7.2.0 Release 1998)</howpublished>
		<title>Digital Cellular Telecommunications System (Phase 2+); Alphabets and language-specific information</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-sms" weight="0.9"/>; </p>
			</richtext>
		</annotation>
		<associations>
			<xref type="updates" target="smsalph530"/>
		</associations>
		<identifier type="uri">http://www.3gpp.org/ftp/Specs/archive/03_series/03.38/0338-720.zip</identifier>
	</reference>
	<reference name="ubl10">
		<names type="author">
			<person>
				<givenname>Bill</givenname>
				<surname>Meadows</surname>
			</person>
			<person>
				<givenname>Lisa</givenname>
				<surname>Seaburg</surname>
			</person>
		</names>
		<date value="2004-09"/>
		<howpublished>Organization for the Advancement of Structured Information Standards (OASIS), Committee Draft</howpublished>
		<title>Universal Business Language 1.0</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-ubl"/>; </p>
			</richtext>
		</annotation>
		<identifier type="uri">http://docs.oasis-open.org/ubl/cd-UBL-1.0/</identifier>
	</reference>
	<reference name="xmlcatalogs">
		<names type="author">
			<person>
				<givenname>Norman</givenname>
				<surname>Walsh</surname>
			</person>
		</names>
		<date value="2002-10"/>
		<abstract>
			<richtext>
				<p>The requirement that all external identifiers in XML documents must provide a system identifier has unquestionably been of tremendous short-term benefit to the XML community. It has allowed a whole generation of tools to be developed without the added complexity of explicit entity management. However, the interoperability of XML documents has been impeded in several ways by the lack of entity management facilities: (1) External identifiers may require resources that are not always available. For example, a system identifier that points to a resource on another machine may be inaccessible if a network connection is not available. (2) External identifiers may require protocols that are not accessible to all of the vendors' tools on a single computer system. An external identifier that is addressed with the ftp: protocol, for example, is not accessible to a tool that does not support that protocol. (3) It is often convenient to access resources using system identifiers that point to local resources. Exchanging documents that refer to local resources with other systems is problematic at best and impossible at worst. The problems involved with sharing documents, or packages of documents, across multiple systems are large and complex. While there are many important issues involved and a complete solution is beyond the current scope, the OASIS membership agrees upon the enclosed set of conventions to address a useful subset of the complete problem. To address these issues, this Committee Specification defines an entity catalog that maps both external identifiers and arbitrary URI references to URI references.</p>
			</richtext>
		</abstract>
		<howpublished>Organization for the Advancement of Structured Information Standards (OASIS), Committee Specification 1.0</howpublished>
		<title>XML Catalogs</title>
		<annotation>
			<richtext>
				<p>Keywords: (undefined keyword: xmlcatalogs); </p>
			</richtext>
		</annotation>
		<identifier type="uri">http://www.oasis-open.org/committees/entity/specs</identifier>
	</reference>
	<reference name="calstable">
		<names type="author">
			<person>
				<givenname>Harvey</givenname>
				<surname>Bingham</surname>
			</person>
		</names>
		<date value="1995-10"/>
		<abstract>
			<richtext>
				<p>This OASIS Technical Memorandum consists of a recommendation for an update to the CALS table model DTD model that will be submitted to the appropriate CALS authority with the expectation that it will be accepted as the next revision of the official CALS table model and that a Formal Public Identifier will be assigned to facilitate referencing of this model. Note that the set of element and attribute declarations in the markup declaration module section of this document partially defines the CALS table model. However, the model is not well-defined without the accompanying natural language description of the semantics (meanings) of these various elements, attributes, and attribute values. The semantic writeup, in the section following that containing the markup declaration module, must be used in conjunction with the element and attribute declarations.</p>
			</richtext>
		</abstract>
		<howpublished>Organization for the Advancement of Structured Information Standards, OASIS Technical Memorandum TM 9502:1995</howpublished>
		<title>CALS Table Model Document Type Definition</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-calstable"/>; </p>
			</richtext>
		</annotation>
		<identifier type="uri" resourceType="text/html">http://www.oasis-open.org/specs/a502.htm</identifier>
	</reference>
	<reference name="relaxng">
		<names type="author">
			<person>
				<givenname>James</givenname>
				<surname>Clark</surname>
			</person>
		</names>
		<date value="2001-12"/>
		<howpublished>Organization for the Advancement of Structured Information Standards (OASIS), Committee Specification</howpublished>
		<title>RELAX NG Specification</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-relaxng"/>; </p>
			</richtext>
		</annotation>
		<identifier type="uri" resourceType="text/html">http://www.oasis-open.org/committees/relax-ng/spec-20011203.html</identifier>
	</reference>
	<reference name="relaxngcompact">
		<names type="author">
			<person>
				<givenname>James</givenname>
				<surname>Clark</surname>
			</person>
		</names>
		<date value="2002-11"/>
		<howpublished>Organization for the Advancement of Structured Information Standards (OASIS), Committee Specification</howpublished>
		<title>RELAX NG Compact Syntax</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-relaxng"/>; </p>
			</richtext>
		</annotation>
		<identifier type="uri" resourceType="text/html">http://www.oasis-open.org/committees/relax-ng/compact-20021121.html</identifier>
	</reference>
	<reference name="uddi3">
		<names type="author">
			<person>
				<givenname>Luc</givenname>
				<surname>Clement</surname>
			</person>
			<person>
				<givenname>Andrew</givenname>
				<surname>Hately</surname>
			</person>
			<person>
				<givenname>Claus</givenname>
				<surname link="von">Riegen</surname>
			</person>
			<person>
				<givenname>Tony</givenname>
				<surname>Rogers</surname>
			</person>
		</names>
		<date value="2004-10"/>
		<abstract>
			<richtext>
				<p>The UDDI Version 3.0.2 Specification describes the Web services, data structures and behaviors of all instances of a UDDI registry.</p>
			</richtext>
		</abstract>
		<howpublished>Organization for the Advancement of Structured Information Standards, UDDI Spec Technical Committee Draft</howpublished>
		<title>UDDI Version 3.0.2</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-uddi"/>; </p>
			</richtext>
		</annotation>
		<identifier type="uri" resourceType="text/html">http://uddi.org/pubs/uddi-v3.0.2-20041019.htm</identifier>
	</reference>
	<reference name="exlog">
		<names type="author">
			<person>
				<givenname>Phillip M.</givenname>
				<surname>Hallam-Baker</surname>
			</person>
			<person>
				<givenname>Brian</givenname>
				<surname>Behlendorf</surname>
			</person>
		</names>
		<date value="1996-03"/>
		<abstract>
			<richtext>
				<p>An improved format for Web server log files is presented. The format is extensible, permitting a wider range of data to be captured. This proposal is motivated by the need to capture a wider range of data for demographic analysis and also the needs of proxy caches.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-logfile-960323</howpublished>
		<title>Extended Log File Format</title>
		<identifier type="uri">http://www.w3.org/TR/WD-logfile-960323</identifier>
	</reference>
	<reference name="webarch">
		<names type="author">
			<person>
				<givenname>Ian</givenname>
				<surname>Jacobs</surname>
			</person>
			<person>
				<givenname>Norman</givenname>
				<surname>Walsh</surname>
			</person>
		</names>
		<date value="2004-12"/>
		<abstract>
			<richtext>
				<p>The World Wide Web uses relatively simple technologies with sufficient scalability, efficiency and utility that they have resulted in a remarkable information space of interrelated resources, growing across languages, cultures, and media. In an effort to preserve these properties of the information space as the technologies evolve, this architecture document discusses the core design components of the Web. They are identification of resources, representation of resource state, and the protocols that support the interaction between agents and resources in the space. We relate core design components, constraints, and good practices to the principles and properties they support.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Recommendation REC-webarch-20041215</howpublished>
		<title>Architecture of the World Wide Web, Volume One</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-www"/>; </p>
			</richtext>
		</annotation>
		<identifier type="uri">http://www.w3.org/TR/2004/REC-webarch-20041215</identifier>
	</reference>
	<reference name="fry99b">
		<names type="author">
			<person>
				<givenname>Henrik</givenname>
				<surname>Frystyk Nielsen</surname>
			</person>
			<person>
				<givenname>Daniel</givenname>
				<surname>LaLiberte</surname>
			</person>
		</names>
		<date value="1999-05"/>
		<abstract>
			<richtext>
				<p>Avoiding the lost update problem has been a notorious challenge when editing documents remotely on the Web using HTTP/1.0. While WebDAV provides an extended set of services for editing the Web, HTTP/1.1 provides a minimal set of hooks for avoiding the lost problem by detecting when versions have changed so that changes aren't lost in the editing process. While simple, these hooks are fundamental to editing the Web using HTTP/1.1 and are needed in Webdav as well. This Note explains a) how to use HTTP/1.1 to detect the lost update problem using preconditions and strong etags and b) how to avoid problems with HTTP/1.0 clients that do not know about these features but only use plain HTTP PUT requests. Neither a) nor b) requires any changes to HTTP/1.1, but can be achieved using existing features. The mechanism has been implemented in Web Commander and Amaya (both using libwww), and Jigsaw — all W3C Open Source software freely available to all interested parties. Detection is only one of several ways to avoid the lost update problem and this document discusses the pros and cons of various other mechanisms including exclusive locks and immutable revisions.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium Note</howpublished>
		<title>Editing the Web: Detecting the Lost Update Problem Using Unreserved Checkout</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-webdav" weight="0.8"/>; </p>
			</richtext>
		</annotation>
		<identifier type="uri">http://www.w3.org/1999/04/Editing/01</identifier>
	</reference>
	<reference name="itsreq">
		<names type="author">
			<person>
				<givenname>Yves</givenname>
				<surname>Savourel</surname>
			</person>
		</names>
		<date value="2006-05"/>
		<abstract>
			<richtext>
				<p>When creating schemas (XML Schema, DTD, etc.), it is important to include constructs that meet the needs of content authors dealing with international audiences, and address the needs of the localization community. This document provides a list of key requirements to achieve such a goal. It will be used to provide a framework and direction for a detailed solution proposal (or set of proposals) to be developed later.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-itsreq-20060518</howpublished>
		<title>Internationalization and Localization Markup Requirements</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-i18n" weight="0.8"/>; <keywordref type="topic-l10n" weight="0.8"/>; <keywordref type="topic-its" weight="0.9"/>; </p>
			</richtext>
		</annotation>
		<identifier type="uri">http://www.w3.org/TR/2006/WD-itsreq-20060518</identifier>
	</reference>
	<reference name="its">
		<names type="author">
			<person>
				<givenname>Christian</givenname>
				<surname>Lieske</surname>
			</person>
			<person>
				<givenname>Felix</givenname>
				<surname>Sasaki</surname>
			</person>
		</names>
		<date value="2006-11"/>
		<abstract>
			<richtext>
				<p>This document defines data categories and their implementation as a set of elements and attributes called the Internationalization Tag Set (ITS). ITS is designed to be used with schemas to support the internationalization and localization of schemas and documents. An implementation is provided for three schema languages: XML DTD, XML Schema and RELAX NG.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Candidate Recommendation CR-its-20061102</howpublished>
		<title>Internationalization Tag Set (ITS) Version 1.0</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-its"/>; <keywordref type="topic-i18n" weight="0.9"/>; <keywordref type="topic-l10n" weight="0.9"/>; </p>
			</richtext>
		</annotation>
		<associations>
			<xref type="updates" target="itsreq"/>
		</associations>
		<identifier type="uri">http://www.w3.org/TR/2006/CR-its-20061102</identifier>
	</reference>
	<reference name="i18nbp">
		<names type="author">
			<person>
				<givenname>Yves</givenname>
				<surname>Savourel</surname>
			</person>
			<person>
				<givenname>Diane</givenname>
				<surname>Stoick</surname>
			</person>
		</names>
		<date value="2006-05"/>
		<abstract>
			<richtext>
				<p>This document provides a set of guidelines for developing XML documents and schemas that are internationalized properly. Following the best practices describes here allow both the developer of XML applications, as well as the author of XML content to create material in different languages. This document is still in an early draft stage. Feedback is especially appreciated on the general concept of ITS, the guidelines listed, and when applicable, the mechanisms defined for the selection of ITS specific information in XML documents.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-xml-i18n-bp-20060518</howpublished>
		<title>Best Practices for XML Internationalization</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-i18n" weight="0.9"/>; <keywordref type="topic-its" weight="0.9"/>; </p>
			</richtext>
		</annotation>
		<identifier type="uri">http://www.w3.org/TR/2006/WD-xml-i18n-bp-20060518</identifier>
	</reference>
	<reference name="ltli">
		<names type="author">
			<person>
				<givenname>Felix</givenname>
				<surname>Sasaki</surname>
			</person>
		</names>
		<date value="2006-06"/>
		<abstract>
			<richtext>
				<p>Based on "RFC3066bis" and "RFC3066bis Matching", this document describes mechanisms for identifying or selecting the language of content or locale preferences used to process information using Web technologies. It describes how document formats, specifications, and implementations should handle language tags, as well as data structures that extend these tags to describe international preferences.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-ltli-20060612</howpublished>
		<title>Language Tags and Locale Identifiers for the World Wide Web</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-i18n" weight="0.9"/>; <keywordref type="topic-l10n" weight="0.9"/>; </p>
			</richtext>
		</annotation>
		<identifier type="uri">http://www.w3.org/TR/2006/WD-ltli-20060612</identifier>
	</reference>
	<reference name="i18nframework">
		<names type="author">
			<person>
				<givenname>Richard</givenname>
				<surname>Ishida</surname>
			</person>
		</names>
		<date value="2003-03"/>
		<abstract>
			<richtext>
				<p>This is a discussion document produced by the Guidelines, Education &amp; Outreach Task Force (GEO) of the W3C Internationalization Working Group (I18N WG). It describes plans for producing documents that provide guidelines on internationalization of W3C technologies. The Task Force encourages feedback about the content of this document as well as participation in the development of the guidelines by people who have experience creating Web content that conforms to internationalization needs.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-i18n-guide-framework-20030417</howpublished>
		<title>Framework Document for i18n Guidelines 1.0</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-i18n"/>; </p>
			</richtext>
		</annotation>
		<identifier type="uri">http://www.w3.org/TR/2003/WD-i18n-guide-framework-20030417</identifier>
	</reference>
	<reference name="wsi18n">
		<names type="author">
			<person>
				<givenname>Addison P.</givenname>
				<surname>Phillips</surname>
			</person>
			<person>
				<givenname>Mary</givenname>
				<surname>Trumble</surname>
			</person>
		</names>
		<date value="2005-09"/>
		<abstract>
			<richtext>
				<p>This document (hereafter referred to as "WS-I18N") describes enhancements to SOAP messaging to provide internationalized and localized operation via locale and international preference negotiation. These mechanisms can be used to accommodate a wide variety of development models for international usage. WS I18N also provides a general-purpose mechanism for associating a "locale policy" with messages. It is designed to be extensible (e.g. support multiple international preferences and locale identifier models). By using the SOAP extensibility model, SOAP-based specifications are designed to be composed with each other to provide a rich messaging environment. By itself, WS-I18N does not ensure internationalized operation or that localized operation will occur nor does it provide a complete internationalization solution. WS-I18N is a building block that is used in conjunction with other Web service and application-specific protocols, and which can accommodate a wide variety of locale and international support models. Implementing this specification does not by itself enable international functionality in the underlying Web services or providers, but it does provide a framework for globalization that enabled products can leverage, as well as a way for enabled products to interact with systems that are not enabled.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-ws-i18n-20050914</howpublished>
		<title>Web Services Internationalization (WS-I18N)</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-i18n" weight="0.9"/>; <keywordref type="topic-soap" weight="0.9"/>; </p>
			</richtext>
		</annotation>
		<identifier type="uri">http://www.w3.org/TR/2005/WD-ws-i18n-20050914</identifier>
	</reference>
	<reference name="i18nhtmltech">
		<names type="author">
			<person>
				<givenname>Richard</givenname>
				<surname>Ishida</surname>
			</person>
		</names>
		<date value="2003-10"/>
		<abstract>
			<richtext>
				<p>This document provides HTML authors with techniques for developing internationalized HTML using XHTML 1.0 or HTML 4.01, supported by CSS1, CSS2 and some aspects of CSS3. It is produced by the Guidelines, Education &amp; Outreach Task Force (GEO) of the W3C Internationalization Working Group (I18N WG). The GEO Task Force encourages feedback about the content of this document as well as participation in the development of the techniques by people who have experience creating Web content that conforms to internationalization needs.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-i18n-html-tech-20031009</howpublished>
		<title>Authoring Techniques for XHTML &amp; HTML Internationalization 1.0</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-i18n" weight="0.9"/>; <keywordref type="topic-html" weight="0.9"/>; <keywordref type="topic-xhtml" weight="0.9"/>; </p>
			</richtext>
		</annotation>
		<identifier type="uri">http://www.w3.org/TR/2003/WD-i18n-html-tech-20031009</identifier>
	</reference>
	<reference name="i18nhtmltechbidi">
		<names type="author">
			<person>
				<givenname>Richard</givenname>
				<surname>Ishida</surname>
			</person>
		</names>
		<date value="2004-05"/>
		<abstract>
			<richtext>
				<p>This document provides advice for the use of markup and CSS to create pages for languages that use bidirectional text, such as Arabic and Hebrew. It attempts to counter many of the misunderstandings or over-complexities that currently abound. It also offers advice to those preparing content that will be localized into scripts that behave like Arabic and Hebrew. This document is one of a series of documents providing HTML authors with techniques for developing internationalized HTML using XHTML 1.0 or HTML 4.01, supported by CSS1, CSS2 and some aspects of CSS3. It focuses specifically on advice about character sets, encodings, and other character-specific matters. It is produced by the Guidelines, Education &amp; Outreach Task Force (GEO) of the W3C Internationalization Working Group (I18N WG). The GEO Task Force encourages feedback about the content of this document as well as participation in the development of the techniques by people who have experience creating Web content that conforms to internationalization needs.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-i18n-html-tech-bidi-20040509</howpublished>
		<title>Authoring Techniques for XHTML &amp; HTML Internationalization: Handling Bidirectional Text 1.0</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-i18n" weight="0.9"/>; <keywordref type="topic-html" weight="0.9"/>; <keywordref type="topic-xhtml" weight="0.9"/>; </p>
			</richtext>
		</annotation>
		<associations>
			<xref type="updates" target="i18nhtmltech"/>
		</associations>
		<identifier type="uri">http://www.w3.org/TR/2004/WD-i18n-html-tech-bidi-20040509</identifier>
	</reference>
	<reference name="i18nhtmltechchar">
		<names type="author">
			<person>
				<givenname>Richard</givenname>
				<surname>Ishida</surname>
			</person>
		</names>
		<date value="2004-05"/>
		<abstract>
			<richtext>
				<p>It is important to consider character encoding matters when producing internationalization content, and further to understand how to choose and declare encodings, how and when to use character escapes, etc. This document is one of a series of documents providing HTML authors with techniques for developing internationalized HTML using XHTML 1.0 or HTML 4.01, supported by CSS1, CSS2 and some aspects of CSS3. It focuses specifically on advice about character sets, encodings, and other character-specific matters. It is produced by the Guidelines, Education &amp; Outreach Task Force (GEO) of the W3C Internationalization Working Group (I18N WG). The GEO Task Force encourages feedback about the content of this document as well as participation in the development of the techniques by people who have experience creating Web content that conforms to internationalization needs.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-i18n-html-tech-char-20040509</howpublished>
		<title>Authoring Techniques for XHTML &amp; HTML Internationalization: Characters and Encodings 1.0</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-i18n" weight="0.9"/>; <keywordref type="topic-html" weight="0.9"/>; <keywordref type="topic-xhtml" weight="0.9"/>; </p>
			</richtext>
		</annotation>
		<associations>
			<xref type="updates" target="i18nhtmltech"/>
		</associations>
		<identifier type="uri">http://www.w3.org/TR/2004/WD-i18n-html-tech-char-20040509</identifier>
	</reference>
	<reference name="i18nhtmltechlang">
		<names type="author">
			<person>
				<givenname>Richard</givenname>
				<surname>Ishida</surname>
			</person>
		</names>
		<date value="2006-07"/>
		<abstract>
			<richtext>
				<p>Specifying the language of content is useful for a wide number of applications, from linguistically sensitive searching to applying language-specific display properties. In some cases the potential applications for language information are still waiting for implementations to catch up, whereas in others, such as detection of language by voice browsers, it is a necessity today. On the other hand, adding markup for language information to content is something that can and should be done today. Without it, it will not be possible to take advantage of any future developments. This document is one of a series of documents providing HTML authors with best practices for developing internationalized HTML using XHTML 1.0 or HTML 4.01, supported by CSS1, CSS2 and some aspects of CSS3. It focuses specifically on advice about specifying the language of content. It is produced by the Internationalization GEO (Guidelines, Education &amp; Outreach) Working Group of the W3C Internationalization Activity.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-i18n-html-tech-lang-20060721</howpublished>
		<title>Internationalization Best Practices: Specifying Language in XHTML &amp; HTML Content</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-i18n" weight="0.9"/>; <keywordref type="topic-html" weight="0.9"/>; <keywordref type="topic-xhtml" weight="0.9"/>; </p>
			</richtext>
		</annotation>
		<associations>
			<xref type="updates" target="i18nhtmltech"/>
		</associations>
		<identifier type="uri">http://www.w3.org/TR/2006/WD-i18n-html-tech-lang-20060721</identifier>
	</reference>
	<reference name="wsdl12">
		<names type="author">
			<person>
				<givenname>Roberto</givenname>
				<surname>Chinnici</surname>
			</person>
			<person>
				<givenname>Martin</givenname>
				<surname>Gudgin</surname>
			</person>
			<person>
				<givenname>Jean-Jacques</givenname>
				<surname>Moreau</surname>
			</person>
			<person>
				<givenname>Sanjiva</givenname>
				<surname>Weerawarana</surname>
			</person>
		</names>
		<date value="2003-06"/>
		<howpublished>World Wide Web Consortium, Working Draft WD-wsdl12-20030611</howpublished>
		<title>Web Services Description Language (WSDL) Version 1.2 Part 1: Core Language</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-wsdl"/>; </p>
			</richtext>
		</annotation>
		<associations>
			<xref type="updates" target="wsdl11"/>
		</associations>
		<identifier type="uri">http://www.w3.org/TR/2003/WD-wsdl12-20030611</identifier>
	</reference>
	<reference name="wsdl20primer">
		<names type="author">
			<person>
				<givenname>David</givenname>
				<surname>Booth</surname>
			</person>
			<person>
				<givenname>Canyang Kevin</givenname>
				<surname>Liu</surname>
			</person>
		</names>
		<date value="2006-03"/>
		<abstract>
			<richtext>
				<p>This document is a companion to the WSDL 2.0 specification (Web Services Description Language (WSDL) Version 2.0 Part 1: Core Language, Web Services Description Language (WSDL) Version 2.0 Part 2: Predefined Extensions, Web Services Description Language (WSDL) Version 2.0 Part 3: Bindings. It is intended for readers who wish to have an easier, less technical introduction to the main features of the language. This primer is only intended to be a starting point toward use of WSDL 2.0, and hence does not describe every feature of the language. Users are expected to consult the WSDL 2.0 specification if they wish to make use of more sophisticated features or techniques. Finally, this primer is non-normative. Any specific questions of what WSDL 2.0 requires or forbids should be referred to the WSDL 2.0 specification.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Candidate Recommendation CR-wsdl20-primer-20060327</howpublished>
		<title>Web Services Description Language (WSDL) Version 2.0 Part 0: Primer</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-wsdl" weight="0.9"/>; </p>
			</richtext>
		</annotation>
		<identifier type="uri">http://www.w3.org/TR/2006/CR-wsdl20-primer-20060327</identifier>
	</reference>
	<reference name="wsdl2">
		<names type="author">
			<person>
				<givenname>Roberto</givenname>
				<surname>Chinnici</surname>
			</person>
			<person>
				<givenname>Jean-Jacques</givenname>
				<surname>Moreau</surname>
			</person>
			<person>
				<givenname>Arthur</givenname>
				<surname>Ryman</surname>
			</person>
			<person>
				<givenname>Sanjiva</givenname>
				<surname>Weerawarana</surname>
			</person>
		</names>
		<date value="2006-03"/>
		<abstract>
			<richtext>
				<p>This document describes the Web Services Description Language Version 2.0 (WSDL 2.0), an XML language for describing Web services. This specification defines the core language which can be used to describe Web services based on an abstract model of what the service offers. It also defines criteria for a conformant processor of this language.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Candidate Recommendation CR-wsdl20-20060327</howpublished>
		<title>Web Services Description Language (WSDL) Version 2.0 Part 1: Core Language</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-wsdl"/>; </p>
			</richtext>
		</annotation>
		<associations>
			<xref type="updates" target="wsdl12"/>
		</associations>
		<identifier type="uri">http://www.w3.org/TR/2006/CR-wsdl20-20060327</identifier>
	</reference>
	<reference name="wsdl20rdf">
		<names type="author">
			<person>
				<givenname>Bijan</givenname>
				<surname>Parsia</surname>
			</person>
			<person>
				<givenname>Jacek</givenname>
				<surname>Kopecký</surname>
			</person>
		</names>
		<date value="2006-05"/>
		<abstract>
			<richtext>
				<p>Web Services Description Language (WSDL) provides a model and an XML format for describing Web services. This document describes a representation of that model in the Resource Description Language (RDF) and in the Web Ontology Language (OWL), and a mapping procedure for transforming particular WSDL descriptions into their RDF form.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-wsdl20-rdf-20060518</howpublished>
		<title>Web Services Description Language (WSDL) Version 2.0: RDF Mapping</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-wsdl" weight="0.9"/>; <keywordref type="topic-rdf" weight="0.8"/>; </p>
			</richtext>
		</annotation>
		<identifier type="uri">http://www.w3.org/TR/2006/WD-wsdl20-rdf-20060518</identifier>
	</reference>
	<reference name="sawsdlguide">
		<names type="author">
			<person>
				<givenname>Rama</givenname>
				<surname>Akkiraju</surname>
			</person>
			<person>
				<givenname>Brahmananda</givenname>
				<surname>Sapkota</surname>
			</person>
		</names>
		<date value="2007-01"/>
		<abstract>
			<richtext>
				<p>Web services provide a standards-based foundation for exchanging information between distributed software systems. The World-Wide Web Consortium (W3C) standard Web Services Description Language (WSDL) specifies a standard way to describe the interfaces of a Web Service at a syntactic level and how to invoke it. While the syntactic descriptions provide information about the structure of input and output messages of an interface and how to invoke them, semantics are needed to describe what a Web service actual does. These semantics when expressed in formal languages disambiguate the description of Web services interfaces paving the way for automatic discovery, composition and integration of software components. WSDL does not explicitly provide mechanisms to specify the semantics of a Web service. Semantic Annotations for WSDL (SAWSDL) is an effort to define mechanisms by which semantic annotations can be added to WSDL components. Many of the concepts in SAWSDL are based on an earlier effort WSDL-S, a W3C submission. This usage guide is an accompanying document to SAWSDL specification. It presents examples to illustrate how to associate semantic annotations with a Web service that could be used for classifying, discovering, matching, composing, and invoking Web services. Some of the examples illustrated in this document use RDF and OWL Web Ontology Language for representing ontologies. Some knowledge of RDF and OWL is useful for understanding this document, but not essential.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-sawsdl-guide-20070126</howpublished>
		<title>Semantic Annotations for WSDL — Usage Guide</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-wsdl" weight="0.8"/>; (undefined keyword: sawsdl); </p>
			</richtext>
		</annotation>
		<identifier type="uri">http://www.w3.org/TR/2007/WD-sawsdl-guide-20070126</identifier>
	</reference>
	<reference name="sawsdl">
		<names type="author">
			<person>
				<givenname>Joel</givenname>
				<surname>Farrell</surname>
			</person>
			<person>
				<givenname>Holger</givenname>
				<surname>Lausen</surname>
			</person>
		</names>
		<date value="2007-01"/>
		<abstract>
			<richtext>
				<p>This document defines a set of extension attributes for the Web Services Description Language (WSDL) that allow to describe additional semantics of WSDL components. The specification defines how such semantic annotation is accomplished using references to semantic models, e.g. ontologies. SAWSDL does not specify a language for representing the semantic models. Instead it provides mechanisms by which concepts from the semantic models, typically defined outside the WSDL document, can be referenced from within WSDL components using annotations.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Candidate Recommendation CR-sawsdl-20070126</howpublished>
		<title>Semantic Annotations for WSDL</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-wsdl" weight="0.8"/>; (undefined keyword: sawsdl); </p>
			</richtext>
		</annotation>
		<identifier type="uri">http://www.w3.org/TR/2007/CR-sawsdl-20070126</identifier>
	</reference>
	<reference name="altschemalangs">
		<names type="author">
			<person>
				<givenname>Amelia A.</givenname>
				<surname>Lewis</surname>
			</person>
			<person>
				<givenname>Bijan</givenname>
				<surname>Parsia</surname>
			</person>
		</names>
		<date value="2005-08"/>
		<abstract>
			<richtext>
				<p>This document captures the result of discussions by the Web Services Description Working Group regarding WSDL 2.0 type system extensibility at the time of its publication. The Working Group normatively defines the use of XML Schema 1.0 as a type system in the WSDL 2.0 Core specification. This document sketches out the basics of extensions for Document Type Definitions (DTDs) and Relax NG.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Note NOTE-wsdl20-altschemalangs-20050817</howpublished>
		<title>Discussion of Alternative Schema Languages and Type System Support in WSDL 2.0</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-wsdl" weight="0.9"/>; </p>
			</richtext>
		</annotation>
		<associations>
			<xref type="updates" target="wsdl12"/>
		</associations>
		<identifier type="uri">http://www.w3.org/TR/2005/NOTE-wsdl20-altschemalangs-20050817</identifier>
	</reference>
	<reference name="wsdl12bindings">
		<names type="author">
			<person>
				<givenname>Jean-Jacques</givenname>
				<surname>Moreau</surname>
			</person>
			<person>
				<givenname>Jeffrey C.</givenname>
				<surname>Schlimmer</surname>
			</person>
		</names>
		<date value="2003-06"/>
		<howpublished>World Wide Web Consortium, Working Draft WD-wsdl12-bindings-20030611</howpublished>
		<title>Web Services Description Language (WSDL) Version 1.2 Part 3: Bindings</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-wsdl" weight="0.9"/>; </p>
			</richtext>
		</annotation>
		<associations>
			<xref type="updates" target="wsdl11"/>
		</associations>
		<identifier type="uri">http://www.w3.org/TR/2003/WD-wsdl12-bindings-20030611</identifier>
	</reference>
	<reference name="wsdl20soap11binding">
		<names type="author">
			<person>
				<givenname>Asir S.</givenname>
				<surname>Vedamuthu</surname>
			</person>
		</names>
		<date value="2006-03"/>
		<abstract>
			<richtext>
				<p>WSDL SOAP 1.1 Binding describes the concrete details for using WSDL 2.0 in conjunction with SOAP 1.1 protocol.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-wsdl20-soap11-binding-20060327</howpublished>
		<title>Web Services Description Language (WSDL) Version 2.0 SOAP 1.1 Binding</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-wsdl" weight="0.9"/>; <keywordref type="topic-soap" weight="0.8"/>; </p>
			</richtext>
		</annotation>
		<identifier type="uri">http://www.w3.org/TR/2006/WD-wsdl20-soap11-binding-20060327</identifier>
	</reference>
	<reference name="wsdl20bindings">
		<names type="author">
			<person>
				<givenname>Hugo</givenname>
				<surname>Haas</surname>
			</person>
			<person>
				<givenname>Philippe Le</givenname>
				<surname>Hégaret</surname>
			</person>
			<person>
				<givenname>Jean-Jacques</givenname>
				<surname>Moreau</surname>
			</person>
			<person>
				<givenname>David</givenname>
				<surname>Orchard</surname>
			</person>
			<person>
				<givenname>Jeffrey C.</givenname>
				<surname>Schlimmer</surname>
			</person>
			<person>
				<givenname>Sanjiva</givenname>
				<surname>Weerawarana</surname>
			</person>
		</names>
		<date value="2004-08"/>
		<abstract>
			<richtext>
				<p>WSDL is an XML format for describing network services as a set of endpoints operating on messages containing either document-oriented or procedure-oriented information. WSDL Version 2.0 Bindings describes how to use WSDL in conjunction with SOAP 1.2 and HTTP/1.1 (as well as other versions of HTTP). This specification depends on WSDL Version 2.0.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-wsdl20-bindings-20040803</howpublished>
		<title>Web Services Description Language (WSDL) Version 2.0 Part 3: Bindings</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-wsdl" weight="0.9"/>; <keywordref type="topic-soap" weight="0.8"/>; </p>
			</richtext>
		</annotation>
		<associations>
			<xref type="updates" target="wsdl12bindings"/>
		</associations>
		<identifier type="uri">http://www.w3.org/TR/2004/WD-wsdl20-bindings-20040803</identifier>
	</reference>
	<reference name="wsdl20adjuncts">
		<names type="author">
			<person>
				<givenname>Roberto</givenname>
				<surname>Chinnici</surname>
			</person>
			<person>
				<givenname>Hugo</givenname>
				<surname>Haas</surname>
			</person>
			<person>
				<givenname>Amelia A.</givenname>
				<surname>Lewis</surname>
			</person>
			<person>
				<givenname>Jean-Jacques</givenname>
				<surname>Moreau</surname>
			</person>
			<person>
				<givenname>David</givenname>
				<surname>Orchard</surname>
			</person>
			<person>
				<givenname>Sanjiva</givenname>
				<surname>Weerawarana</surname>
			</person>
		</names>
		<date value="2006-03"/>
		<abstract>
			<richtext>
				<p>WSDL is an XML format for describing network services as a set of endpoints operating on messages containing either document-oriented or procedure-oriented information. Web Services Description Language (WSDL) Version 2.0 Part 2: Adjuncts defines predefined extensions for use in WSDL 2.0: Message exchange patterns, Operation styles, and Bindings. This specification depends on WSDL Version 2.0.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Candidate Recommendation CR-wsdl20-adjuncts-20060327</howpublished>
		<title>Web Services Description Language (WSDL) Version 2.0 Part 2: Adjuncts</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-wsdl" weight="0.9"/>; </p>
			</richtext>
		</annotation>
		<associations>
			<xref type="updates" target="wsdl20bindings"/>
			<xref type="updates" target="wsdl2extensions"/>
		</associations>
		<identifier type="uri">http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327</identifier>
	</reference>
	<reference name="wsdl12patterns">
		<names type="author">
			<person>
				<givenname>Martin</givenname>
				<surname>Gudgin</surname>
			</person>
			<person>
				<givenname>Amelia A.</givenname>
				<surname>Lewis</surname>
			</person>
			<person>
				<givenname>Jeffrey C.</givenname>
				<surname>Schlimmer</surname>
			</person>
		</names>
		<date value="2003-06"/>
		<howpublished>World Wide Web Consortium, Working Draft WD-wsdl12-patterns-20030611</howpublished>
		<title>Web Services Description Language (WSDL) Version 1.2 Part 2: Message Patterns</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-wsdl" weight="0.9"/>; </p>
			</richtext>
		</annotation>
		<associations>
			<xref type="updates" target="wsdl11"/>
		</associations>
		<identifier type="uri">http://www.w3.org/TR/2003/WD-wsdl12-patterns-20030611</identifier>
	</reference>
	<reference name="wsdl20patterns">
		<names type="author">
			<person>
				<givenname>Martin</givenname>
				<surname>Gudgin</surname>
			</person>
			<person>
				<givenname>Amelia A.</givenname>
				<surname>Lewis</surname>
			</person>
			<person>
				<givenname>Jeffrey C.</givenname>
				<surname>Schlimmer</surname>
			</person>
		</names>
		<date value="2004-03"/>
		<abstract>
			<richtext>
				<p>This document describes Web Services Description Language (WSDL) Version 2.0 message exchange patterns. These patterns are intended for use with the Web Services Description Language (WSDL).</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-wsdl20-patterns-20040326</howpublished>
		<title>Web Services Description Language (WSDL) Version 2.0 Part 2: Message Patterns</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-wsdl" weight="0.9"/>; </p>
			</richtext>
		</annotation>
		<associations>
			<xref type="updates" target="wsdl12patterns"/>
		</associations>
		<identifier type="uri">http://www.w3.org/TR/2004/WD-wsdl20-patterns-20040326</identifier>
	</reference>
	<reference name="wsdl2extensions">
		<names type="author">
			<person>
				<givenname>Martin</givenname>
				<surname>Gudgin</surname>
			</person>
			<person>
				<givenname>Amelia A.</givenname>
				<surname>Lewis</surname>
			</person>
			<person>
				<givenname>Jeffrey C.</givenname>
				<surname>Schlimmer</surname>
			</person>
		</names>
		<date value="2004-08"/>
		<abstract>
			<richtext>
				<p>This document describes extensions for the Web Services Description Language (WSDL) Version 2.0. These extensions include Message Exchange Patterns (MEPs), features, SOAP modules, and bindings of features. The Working Group has discussed and approved these extensions, and recommends their use with the Web Services Description Language (WSDL).</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-wsdl20-extensions-20040803</howpublished>
		<title>Web Services Description Language (WSDL) Version 2.0 Part 2: Predefined Extensions</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-wsdl" weight="0.9"/>; <keywordref type="topic-wsdlmep" weight="0.9"/>; </p>
			</richtext>
		</annotation>
		<associations>
			<xref type="updates" target="wsdl20patterns"/>
		</associations>
		<identifier type="uri">http://www.w3.org/TR/2004/WD-wsdl20-extensions-20040803</identifier>
	</reference>
	<reference name="wsdl11">
		<names type="author">
			<person>
				<givenname>Erik</givenname>
				<surname>Christensen</surname>
			</person>
			<person>
				<givenname>Francisco</givenname>
				<surname>Curbera</surname>
			</person>
			<person>
				<givenname>Greg</givenname>
				<surname>Meredith</surname>
			</person>
			<person>
				<givenname>Sanjiva</givenname>
				<surname>Weerawarana</surname>
			</person>
		</names>
		<date value="2001-03"/>
		<abstract>
			<richtext>
				<p>WSDL is an XML format for describing network services as a set of endpoints operating on messages containing either document-oriented or procedure-oriented information. The operations and messages are described abstractly, and then bound to a concrete network protocol and message format to define an endpoint. Related concrete endpoints are combined into abstract endpoints (services). WSDL is extensible to allow description of endpoints and their messages regardless of what message formats or network protocols are used to communicate, however, the only bindings described in this document describe how to use WSDL in conjunction with SOAP 1.1, HTTP GET/POST, and MIME.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Note NOTE-wsdl-20010315</howpublished>
		<title>Web Services Description Language (WSDL) 1.1</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-wsdl"/>; </p>
			</richtext>
		</annotation>
		<identifier type="uri">http://www.w3.org/TR/2001/NOTE-wsdl-20010315</identifier>
	</reference>
	<reference name="wsdl11elementidentifiers">
		<names type="author">
			<person>
				<givenname>David</givenname>
				<surname>Orchard</surname>
			</person>
			<person>
				<givenname>Asir S.</givenname>
				<surname>Vedamuthu</surname>
			</person>
			<person>
				<givenname>Frederick</givenname>
				<surname>Hirsch</surname>
			</person>
			<person>
				<givenname>Maryann</givenname>
				<surname>Hondo</surname>
			</person>
			<person>
				<givenname>Prasad</givenname>
				<surname>Yendluri</surname>
			</person>
			<person>
				<givenname>Toufic</givenname>
				<surname>Boubez</surname>
			</person>
			<person>
				<givenname>Ümit</givenname>
				<surname>Yalçınalp</surname>
			</person>
		</names>
		<date value="2007-01"/>
		<abstract>
			<richtext>
				<p>WSDL 1.1 Element Identifiers defines a syntax to identify individual elements in a WSDL 1.1 document.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-wsdl11elementidentifiers-20070131</howpublished>
		<title>WSDL 1.1 Element Identifiers</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-wsdl"/>; </p>
			</richtext>
		</annotation>
		<identifier type="uri">http://www.w3.org/TR/2007/WD-wsdl11elementidentifiers-20070131</identifier>
	</reference>
	<reference name="wsi18nreq">
		<names type="author">
			<person>
				<givenname>Addison P.</givenname>
				<surname>Phillips</surname>
			</person>
		</names>
		<date value="2004-11"/>
		<abstract>
			<richtext>
				<p>This document describes requirements for internationalizing Web services.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Note NOTE-ws-i18n-req-20041116</howpublished>
		<title>Requirements for the Internationalization of Web Services</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-i18n" weight="0.9"/>; </p>
			</richtext>
		</annotation>
		<identifier type="uri">http://www.w3.org/TR/2004/NOTE-ws-i18n-req-20041116</identifier>
	</reference>
	<reference name="wschorreqs">
		<names type="author">
			<person>
				<givenname>Daniel</givenname>
				<surname>Austin</surname>
			</person>
			<person>
				<givenname>Abbie</givenname>
				<surname>Barbir</surname>
			</person>
			<person>
				<givenname>Ed</givenname>
				<surname>Peters</surname>
			</person>
			<person>
				<givenname>Steve</givenname>
				<surname>Ross-Talbot</surname>
			</person>
		</names>
		<date value="2004-03"/>
		<abstract>
			<richtext>
				<p>As the momentum around Web Services grows, the need for effective mechanisms to co-ordinate the interactions among Web Services and their users becomes more pressing. The Web Services Choreography Working Group has been tasked with the development of such a mechanism in an interoperable way. This document describes a set of requirements for Web Services choreography based around a set of representative use cases, as well as general requirements for interaction among Web Services. This document is intended to be consistent with other efforts within the W3C Web Services Activity.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-ws-chor-reqs-20040311</howpublished>
		<title>Web Services Choreography Requirements 1.0</title>
		<identifier type="uri">http://www.w3.org/TR/2004/WD-ws-chor-reqs-20040311</identifier>
	</reference>
	<reference name="wschormodel">
		<names type="author">
			<person>
				<givenname>David</givenname>
				<surname>Burdett</surname>
			</person>
			<person>
				<givenname>Nickolas</givenname>
				<surname>Kavantzas</surname>
			</person>
		</names>
		<date value="2004-03"/>
		<abstract>
			<richtext>
				<p>Its purpose is to provide an information model that describes the data and the relationships between them that is needed to define a choreography that describes the sequence and conditions in which the data exchanged between two or more participants in order to meet some useful purpose.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-ws-chor-model-20040324</howpublished>
		<title>WS Choreography Model Overview</title>
		<identifier type="uri">http://www.w3.org/TR/2004/WD-ws-chor-model-20040324</identifier>
	</reference>
	<reference name="wsci10">
		<names type="author">
			<person>
				<givenname>Assaf</givenname>
				<surname>Arkin</surname>
			</person>
			<person>
				<givenname>Sid</givenname>
				<surname>Askary</surname>
			</person>
			<person>
				<givenname>Scott</givenname>
				<surname>Fordin</surname>
			</person>
			<person>
				<givenname>Wolfgang</givenname>
				<surname>Jekeli</surname>
			</person>
			<person>
				<givenname>Kohsuke</givenname>
				<surname>Kawaguchi</surname>
			</person>
			<person>
				<givenname>David</givenname>
				<surname>Orchard</surname>
			</person>
			<person>
				<givenname>Stefano</givenname>
				<surname>Pogliani</surname>
			</person>
			<person>
				<givenname>Karsten</givenname>
				<surname>Riemer</surname>
			</person>
			<person>
				<givenname>Susan</givenname>
				<surname>Struble</surname>
			</person>
			<person>
				<givenname>Pal</givenname>
				<surname>Takacsi-Nagy</surname>
			</person>
			<person>
				<givenname>Ivana</givenname>
				<surname>Trickovic</surname>
			</person>
			<person>
				<givenname>Sinisa</givenname>
				<surname>Zimek</surname>
			</person>
		</names>
		<date value="2002-08"/>
		<abstract>
			<richtext>
				<p>The Web Service Choreography Interface (WSCI) is an XML-based interface description language that describes the flow of messages exchanged by a Web Service participating in choreographed interactions with other services. WSCI describes the dynamic interface of the Web Service participating in a given message exchange by means of reusing the operations defined for a static interface. WSCI works in conjunction with the Web Service Description Language (WSDL), the basis for the W3C Web Services Description Working Group; it can, also, work with another service definition language that exhibits the same characteristics as WSDL. WSCI describes the observable behavior of a Web Service. This is expressed in terms of temporal and logical dependencies among the exchanged messages, featuring sequencing rules, correlation, exception handling, and transactions. WSCI also describes the collective message exchange among interacting Web Services, thus providing a global, message-oriented view of the interactions. WSCI does not address the definition and the implementation of the internal processes that actually drive the message exchange. Rather, the goal of WSCI is to describe the observable behavior of a Web Service by means of a message-flow oriented interface. This description enables developers, architects and tools to describe and compose a global view of the dynamic of the message exchange by understanding the interactions with the web service.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Note NOTE-wsci10-20020808</howpublished>
		<title>Web Service Choreography Interface (WSCI) 1.0</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-wsci"/>; </p>
			</richtext>
		</annotation>
		<identifier type="uri">http://www.w3.org/TR/2002/NOTE-wsci-20020808</identifier>
	</reference>
	<reference name="wscdl10">
		<names type="author">
			<person>
				<givenname>Nickolas</givenname>
				<surname>Kavantzas</surname>
			</person>
			<person>
				<givenname>David</givenname>
				<surname>Burdett</surname>
			</person>
			<person>
				<givenname>Greg</givenname>
				<surname>Ritzinger</surname>
			</person>
			<person>
				<givenname>Tony</givenname>
				<surname>Fletcher</surname>
			</person>
			<person>
				<givenname>Yves</givenname>
				<surname>Lafon</surname>
			</person>
			<person>
				<givenname>Charlton</givenname>
				<surname>Barreto</surname>
			</person>
		</names>
		<date value="2005-11"/>
		<abstract>
			<richtext>
				<p>The Web Services Choreography Description Language (WS-CDL) is an XML-based language that describes peer-to-peer collaborations of Web Services participants by defining, from a global viewpoint, their common and complementary observable behavior; where ordered message exchanges result in accomplishing a common business goal. The Web Services specifications offer a communication bridge between the heterogeneous computational environments used to develop and host applications. The future of E-Business applications requires the ability to perform long-lived, peer-to-peer collaborations between the participating services, within or across the trusted domains of an organization. The Web Services Choreography specification is targeted for composing interoperable peer-to-peer collaborations between any type of Web Service participant regardless of the supporting platform or programming model used by the implementation of the hosting environment.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Candidate Recommandation CR-ws-cdl-10-20051109</howpublished>
		<title>Web Services Choreography Description Language Version 1.0</title>
		<annotation>
			<richtext>
				<p>Keywords: <keywordref type="topic-wscdl"/>; </p>
			</richtext>
		</annotation>
		<identifier type="uri">http://www.w3.org/TR/2005/CR-ws-cdl-10-20051109</identifier>
	</reference>
	<reference name="wscdl10primer">
		<names type="author">
			<person>
				<givenname>Steve</givenname>
				<surname>Ross-Talbot</surname>
			</person>
			<person>
				<givenname>Tony</givenname>
				<surname>Fletcher</surname>
			</person>
		</names>
		<date value="2006-06"/>
		<abstract>
			<richtext>
				<p>Web Services Choreography Description Language: Primer is a non-normative document intended to provide an easy to understand tutorial on the uses and the features of the Web Services Choreography Description Language specification.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-ws-cdl-10-primer-20060619</howpublished>
		<title>Web Services Choreography Description Lang