<?xml version="1.0" encoding="UTF-8"?>
<bibliography xmlns="http://dret.net/xmlns/sharef" version="1.0">
	<reference name="cre06" src="bibtex:article" src-info="bibtex:line-468" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Fabio</givenname>
				<surname>Crestani</surname>
			</person>
			<person>
				<givenname>Monica</givenname>
				<surname>Landoni</surname>
			</person>
			<person>
				<givenname>Massimo</givenname>
				<surname>Melucci</surname>
			</person>
		</names>
		<date value="2006"/>
		<abstract>
			<richtext>
				<p>We present the results and the lessons learned from two separate and independent studies into the design, development, and evaluation of electronic books for information access: the Visual Book and the Hyper-TextBook. The Visual Book explored the importance of the visual component of the book metaphor in the production of "good" electronic books for referencing. The Hyper-TextBook concentrated on the importance of models and techniques for the automatic production of functional electronic versions of textbooks. Both studies started from similar considerations on what kinds of paper books are suitable for translation into electronic form but di.er on the prominence given to book appearance and functionalities. The results of these two research projects are critically presented in this paper, with the aim of helping designers and implementers to better integrate appearance and functional aspects of books into a more general methodology for the automatic production of electronic books for information access.</p>
			</richtext>
		</abstract>
		<title type="sharef:secondaryTitle">International Journal on Digital Libraries</title>
		<number>2</number>
		<pages>192-209</pages>
		<title type="sharef:primaryTitle">Appearance and Functionality of Electronic Books</title>
		<identifier type="sharef:uri" resourceType="text/html">http://link.springer.de/link/service/journals/00799/bibs/7001001/70010068.htm</identifier>
		<volume>6</volume>
	</reference>
	<reference name="abi97" src="bibtex:article" src-info="bibtex:line-480" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Serge</givenname>
				<surname>Abiteboul</surname>
			</person>
			<person>
				<givenname>Dallan</givenname>
				<surname>Quass</surname>
			</person>
			<person>
				<givenname>Jason</givenname>
				<surname>McHugh</surname>
			</person>
			<person>
				<givenname>Jennifer</givenname>
				<surname>Widom</surname>
			</person>
			<person>
				<givenname>Janet L.</givenname>
				<surname>Wiener</surname>
			</person>
		</names>
		<date value="1997"/>
		<abstract>
			<richtext>
				<p>We present the Lorel language, designed for querying semistructured data. Semistructured data is becoming more and more prevalent, e.g., in structured documents such as HTML and when performing simple integration of data from multiple sources. Traditional data models and query languages are inappropriate, since semistructured data often is irregular: some data is missing, similar concepts are represented using different types, heterogeneous sets are present, or object structure is not fully known. Lorel is a user-friendly language in the SQL/OQL style for querying such data effectively. For wide applicability, the simple object model underlying Lorel can be viewed as an extension of the ODMG data model and the Lorel language as an extension of OQL. The main novelties of the Lorel language are: (i) the extensive use of coercion to relieve the user from the strict typing of OQL, which is inappropriate for semistructured data; and (ii) powerful path expressions, which permit a flexible form of declarative navigational access and are particularly suitable when the details of the structure are not known to the user. Lorel also includes a declarative update language. Lorel is implemented as the query language of the Lore prototype database management system at Stanford. Information about Lore can be found at http://www-db.stanford.edu/lore. In addition to presenting the Lorel language in full, this paper briefly describes the Lore system and query processor. We also briefly discuss a second implementation of Lorel on top of a conventional object-oriented database management system, the O2 system.</p>
			</richtext>
		</abstract>
		<title type="sharef:secondaryTitle">International Journal on Digital Libraries</title>
		<number>1</number>
		<pages>68-88</pages>
		<title type="sharef:primaryTitle">The Lorel Query Language for Semistructured Data</title>
		<field type="bibtex:topic">lorel[1]</field>
		<identifier type="sharef:uri" resourceType="text/html">http://link.springer.de/link/service/journals/00799/bibs/7001001/70010068.htm</identifier>
		<volume>1</volume>
	</reference>
	<reference name="men97" src="bibtex:article" src-info="bibtex:line-493" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Alberto O.</givenname>
				<surname>Mendelzon</surname>
			</person>
			<person>
				<givenname>George A.</givenname>
				<surname>Mihaila</surname>
			</person>
			<person>
				<givenname>Tova</givenname>
				<surname>Milo</surname>
			</person>
		</names>
		<date value="1997"/>
		<abstract>
			<richtext>
				<p>The World Wide Web is a large, heterogeneous, distributed collection of documents connected by hypertext links. The most common technology currently used for searching the Web depends on sending information retrieval requests to "index servers" that index as many documents as they can find by navigating the network. One problem with this is that users must be aware of the various index servers (over a dozen of them are currently deployed on the Web), of their strengths and weaknesses, and of the peculiarities of their query interfaces. A more serious problem is that these queries cannot exploit the structure and topology of the document network. In this paper we propose a query language, WebSQL, that takes advantage of multiple index servers without requiring users to know about them, and that integrates textual retrieval with structure and topology-based queries. We give a formal semantics for WebSQL using a calculus based on a novel "virtual graph" model of a document network. We propose a new theory of query cost based on the idea of "query locality," that is, how much of the network must be visited to answer a particular query. We give an algorithm for characterizing WebSQL queries with respect to query locality. Finally, we describe a prototype implementation of WebSQL written in Java.</p>
			</richtext>
		</abstract>
		<title type="sharef:secondaryTitle">International Journal on Digital Libraries</title>
		<number>1</number>
		<pages>54-67</pages>
		<title type="sharef:primaryTitle">Querying the World Wide Web</title>
		<field type="bibtex:topic">websql[1]</field>
		<identifier type="sharef:uri" resourceType="text/html">http://link.springer.de/link/service/journals/00799/bibs/7001001/70010054.htm</identifier>
		<volume>1</volume>
	</reference>
	<reference name="kaa03" src="bibtex:article" src-info="bibtex:line-510" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Eija</givenname>
				<surname>Kaasinen</surname>
			</person>
		</names>
		<date value="2003-05"/>
		<abstract>
			<richtext>
				<p>Mobile contexts of use vary a lot, and may even be continuously changing during use. The context is much more than location, but its other elements are still difficult to identify or measure. Location information is becoming an integral part of different mobile devices. Current mobile services can be enhanced with location-aware features, thus providing the user with a smooth transition towards context-aware services. Potential application fields can be found in areas such as travel information, shopping, entertainment, event information and different mobile professions. This paper studies location-aware mobile services from the user's point of view. The paper draws conclusions about key issues related to user needs, based on user interviews, laboratory and field evaluations with users, and expert evaluations of location-aware services. The user needs are presented under five main themes: topical and comprehensive contents, smooth user interaction, personal and user-generated contents, seamless service entities and privacy issues.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1007/s00779-002-0214-7</identifier>
		<title type="sharef:secondaryTitle">Personal and Ubiquitous Computing</title>
		<number>1</number>
		<pages>70-79</pages>
		<title type="sharef:primaryTitle">User Needs for Location-Aware Mobile Services</title>
		<volume>7</volume>
	</reference>
	<reference name="kil01" src="bibtex:article" src-info="bibtex:line-527" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Pekka</givenname>
				<surname>Kilpeläinen</surname>
			</person>
			<person>
				<givenname>Derick</givenname>
				<surname>Wood</surname>
			</person>
		</names>
		<date value="2001-09"/>
		<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>
		<title type="sharef:secondaryTitle">Information and Computation</title>
		<number>2</number>
		<pages>230-251</pages>
		<title type="sharef:primaryTitle">SGML and XML Document Grammars and Exceptions</title>
		<field type="bibtex:topic">sgml[0.7] xml[0.7]</field>
		<identifier type="sharef:uri">http://portal.acm.org/citation.cfm?id=501973</identifier>
		<volume>169</volume>
	</reference>
	<reference name="zha07" src="bibtex:article" src-info="bibtex:line-545" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Bo</givenname>
				<surname>Zhao</surname>
			</person>
			<person>
				<givenname>Manchun</givenname>
				<surname>Li</surname>
			</person>
			<person>
				<givenname>Zhixin</givenname>
				<surname>Jiang</surname>
			</person>
		</names>
		<date value="2007-08"/>
		<abstract>
			<richtext>
				<p>This paper describes a number of ways to encode spatiotemporal information in RSS feeds. As RSS becomes more and more prevalent as a way to publish and share information, it becomes increasingly important that location and time is described in an interoperable manner so that applications can request, aggregate, share and map spatiotemporally tagged feeds. This paper describes the GeoRSS model and encodings. With every RSS item has a timestamp, GeoRSS can represent time property for free. There are three GeoRSS encoding standards, such as W3C Geo, GeoRSS Simple, and GeoRSS GML profile. These standards differ in the number of coordinate systems they can support, and in the number of different geometric shapes they can add to the map to show where the news or event of interest is taking place. Further more, this paper described how to add time attribute to GeoRSS and implement and visualization the GeoRSS feeds through Google Map and Timeline. A few apt illustrations were given to show the powerful functions of GeoRSS in syndicating the spatiotemporal information. GeoRSS leverages this teeming ecosystem for geospatial technology, and with OGC support, GeoRSS is on firm conceptual ground and gains exposure across the industry.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1117/12.764955</identifier>
		<title type="sharef:secondaryTitle">Proceedings of SPIE</title>
		<title type="sharef:primaryTitle">Using GeoRSS to Syndicate the Spatiotemporal Information</title>
		<field type="bibtex:topic">georss[0.8]</field>
		<volume>6754</volume>
	</reference>
	<reference name="abo92" src="bibtex:article" src-info="bibtex:line-561" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Gregory D.</givenname>
				<surname>Abowd</surname>
			</person>
			<person>
				<givenname>Alan J.</givenname>
				<surname>Dix</surname>
			</person>
		</names>
		<date value="1992-12"/>
		<abstract>
			<richtext>
				<p>In this paper, we investigate the problems associated with the provision of an undo support facility in the context of a synchronous shared or group editor. Previous work on the development of formal models of undo has been restricted to single user systems and has focused on the functionality of undo, as opposed to discussing the support that users require from any error recovery facility. Motivated by new issues that arise in the context of computer supported cooperative work, we aim to integrate formal modelling of undo with an analysis of how users understand undo facilities. Together, these combined perspectives of the system and user lead to concrete design advice for implementing an undo facility. The special issues that arise in the context of shared undo also shed light on the emphasis that should be placed on even single user undo. In particular, we come to regard undo not as a system command to be implemented, but as a user intention to be supported by the system.</p>
			</richtext>
		</abstract>
		<title type="sharef:secondaryTitle">Interacting with Computers</title>
		<number>3</number>
		<pages>317-342</pages>
		<title type="sharef:primaryTitle">Giving Undo Attention</title>
		<identifier type="sharef:uri">http://www.comp.lancs.ac.uk/~dixa/papers/undo92/</identifier>
		<volume>4</volume>
	</reference>
	<reference name="dan02" src="bibtex:article" src-info="bibtex:line-574" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>David R.</givenname>
				<surname>Danielson</surname>
			</person>
		</names>
		<date value="2002-10"/>
		<abstract>
			<richtext>
				<p>Knowledge regarding how Web information-seekers behave with respect to the structures and cues they are provided with may shed light on general principles of navigation in electronic spaces, and assist designers in making more informed structural decisions. This study examines user movement through hierarchically structured Web sites and the behavioral effects of a constantly visible, textual contents list for relatively small sites or more extensive local views than are generally used on the Web today. The site overview resulted in users abandoning fewer information-seeking tasks. Users with such context dig deeper into the site structure, make less use of the browser's Back button, and frequently make navigational movements of great hierarchical distances. Navigational correlates of success and reported confidence for users with the overview differ from those without such context. Both with and without a constant overview, the relationship between the source and destination pages may help predict the amount of time spent at the destination. Experimental reports are preceded by a review of click-stream navigation behavior research.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1016/S0953-5438(02)00024-3</identifier>
		<title type="sharef:secondaryTitle">Interacting with Computers</title>
		<number>5</number>
		<pages>601-618</pages>
		<title type="sharef:primaryTitle">Web Navigation and the Behavioral Effects of Constantly Visible Site Maps</title>
		<volume>14</volume>
	</reference>
	<reference name="wil08a" src="bibtex:article" src-info="bibtex:line-591" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Erik</givenname>
				<surname>Wilde</surname>
			</person>
		</names>
		<date value="2008"/>
		<abstract>
			<richtext>
				<p>Purpose: A growing amount of information available on the Web can be classified as "contextual information", putting already existing information into a new context rather than creating isolated new information resources. Blogs are a typical and popular example of this category. By looking at blogs from a more context-oriented view, it is possible to deconstruct them into structures which are more contextual than just focused on the content, facilitating flexible reuse of these structures. — Design/Methodology/Approach: We look at the underlying structures of blogs and blog posts, representing them as multi-ended links. This alternative representation of blogs and blog posts allows us to represent them as reusable information structures. This paper presents blogs as a popular content type, but the approach of restructuring Web 2.0 content can be extended to other classes of information, as long as they can be regarded as being mainly contextual. — Findings: By deconstructing blogs and blog posts into their essential properties, we can show how there is a simple and universal representation for blogs. This representation allows the reuse of blog information across specific blog or blogging platforms, and can even go beyond blogs by representing other Web content which provides context. — Originality/Value: The approach presented in this paper is a novel approach of mapping a popular Web content type to a simple and universal representation. The value of such a unified representation lies in exposing the structural similarities among blogs and blog posts, and making them available for reuse.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1108/14684520810889691</identifier>
		<title type="sharef:secondaryTitle">Online Information Review</title>
		<number>3</number>
		<pages>401-414</pages>
		<title type="sharef:primaryTitle">Deconstructing Blogs</title>
		<identifier type="sharef:uri">http://dret.net/netdret/publications#wil08a</identifier>
		<identifier type="sharef:uri">http://www.emeraldinsight.com/10.1108/14684520810889691</identifier>
		<volume>32</volume>
	</reference>
	<reference name="chu99" src="bibtex:article" src-info="bibtex:line-605" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Tham Yoke</givenname>
				<surname>Chun</surname>
			</person>
		</names>
		<date value="1999"/>
		<abstract>
			<richtext>
				<p>This paper traces the development of World Wide Web Robots and provides an overview of their main functions and workings. The focus is on search robots and illustrations will be drawn from two major search engines: AltaVista and Excite. In the concluding section, problems associated with the use of Web Robots and their implications for electronic publishing will be examined.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1108/14684529910334047</identifier>
		<title type="sharef:secondaryTitle">Online Information Review</title>
		<number>3</number>
		<pages>135-142</pages>
		<title type="sharef:primaryTitle">World Wide Web Robots: An Overview</title>
		<volume>23</volume>
	</reference>
	<reference name="naa05" src="bibtex:article" src-info="bibtex:line-621" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Mor</givenname>
				<surname>Naaman</surname>
			</person>
			<person>
				<givenname>Yee Jiun</givenname>
				<surname>Song</surname>
			</person>
			<person>
				<givenname>Andreas</givenname>
				<surname>Paepcke</surname>
			</person>
			<person>
				<givenname>Hector</givenname>
				<surname>Garcia-Molina</surname>
			</person>
		</names>
		<date value="2005-07"/>
		<abstract>
			<richtext>
				<p>NameSet is a system that translates a set of geographic coordinates into a textual name based on the geographic regions where the coordinates occur. One possible application of NameSet is to concisely present the geographical scope of a set of geo-referenced observations to a human user. Another application is to generate text to depict a set of coordinates that appear on a web site — text that could later be used for information retrieval applications. NameSet's computation is based on a simple algorithm, using off-the-shelf and web-based data sources. The system was proven effective in an application that automatically organizes and names sets of geo-referenced digital photographs.</p>
			</richtext>
		</abstract>
		<title type="sharef:secondaryTitle">Computers, Environment, and Urban Systems Journal</title>
		<title type="sharef:primaryTitle">Assigning Textual Names to Sets of Geographic Coordinates</title>
		<field type="bibtex:topic">nameset[1]</field>
		<identifier type="sharef:uri">http://dbpubs.stanford.edu:8090/pub/2005-18</identifier>
	</reference>
	<reference name="ram00" src="bibtex:article" src-info="bibtex:line-636" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Ramachendra P.</givenname>
				<surname>Batni</surname>
			</person>
			<person>
				<givenname>Chinmei C.</givenname>
				<surname>Lee</surname>
			</person>
			<person>
				<givenname>Douglas W.</givenname>
				<surname>Varney</surname>
			</person>
		</names>
		<date value="2000-07"/>
		<abstract>
			<richtext>
				<p>In today's highly competitive wireless marketplace, carriers have to offer user-friendly, innovative services to gain a competitive advantage. Furthermore, subscribers demand services that can be easily customized to their specific needs. The advent of the wireless application protocol (WAP) and WAP-enabled mobile phones is providing an opportunity for carriers to leverage this technology to enrich their service offerings. WAP is becoming the de facto standard for mobile subscribers who want to browse the contents in the Internet and perform e-commerce transactions. At the same time, new capabilities — such as those provided by intelligent network (IN) technology — are also being introduced into the public land mobile networks (PLMNs) to provide enhanced services. This paper discusses how the emerging WAP technology can be synergistically combined with PLMN capabilities to provide mobile subscribers with enhanced converged voice/data services in WAP-enabled wireless networks. To illustrate these concepts, this paper includes several service examples.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1002/bltj.2241</identifier>
		<title type="sharef:secondaryTitle">Bell Labs Technical Journal</title>
		<number>3</number>
		<pages>145-152</pages>
		<title type="sharef:primaryTitle">Enhanced Services in WAP-Enabled Networks</title>
		<field type="bibtex:topic">wap[0.8]</field>
		<identifier type="sharef:uri">http://www3.interscience.wiley.com/cgi-bin/abstract/97519004/</identifier>
		<volume>5</volume>
	</reference>
	<reference name="ada03b" src="bibtex:article" src-info="bibtex:line-655" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Peter M.</givenname>
				<surname>Adams</surname>
			</person>
			<person>
				<givenname>G. Wayne B.</givenname>
				<surname>Ashwell</surname>
			</person>
			<person>
				<givenname>Richard</givenname>
				<surname>Baxter</surname>
			</person>
		</names>
		<date value="2003-01"/>
		<abstract>
			<richtext>
				<p>This paper traces the history of location-based service (LBS) standards that arose from North American requirements in the work on GSM standards in the late 1990s. It also describes how interest in GSM/UMTS outside Europe led to the creation of the Third Generation Partnership Project (3GPP) for developing UMTS standards (which include standards for the 3G mobile Internet). In addition, the paper covers the role of other standards bodies and interest groups involved in the creation of LBS standards such as the new Open Mobile Alliance. Different location methods for detecting the position of mobiles are described and a summary of the current work in 3GPP on LBS-based services and architecture for UMTS is given. The paper also covers work on wireless access protocols in the old WAP Forum on LBS and also the work of the Location Interoperability Forum (LIF). Finally, the impact of these LBS standards developments on BTexact initiatives, such as project Erica, is summarised. The provision of a rich range of LBS services is considered to be very important for the future success of UMTS.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1023/A:1022572210026</identifier>
		<title type="sharef:secondaryTitle">BT Technology Journal</title>
		<number>1</number>
		<pages>34-43</pages>
		<title type="sharef:primaryTitle">Location-Based Services — An Overview of the Standards</title>
		<volume>21</volume>
	</reference>
	<reference name="roz03" src="bibtex:article" src-info="bibtex:line-668" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Thomas</givenname>
				<surname>D'Roza</surname>
			</person>
			<person>
				<givenname>George</givenname>
				<surname>Bilchev</surname>
			</person>
		</names>
		<date value="2003-01"/>
		<abstract>
			<richtext>
				<p>This paper provides an overview of terms, technologies and standards used within the location-based services field in the determination and presentation of the location of an entity. A description is provided of data formats and protocols for communicating, storing and manipulating location information and some insight is given into how location information could be used in a range of applications.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1023/A:1022491825047</identifier>
		<title type="sharef:secondaryTitle">BT Technology Journal</title>
		<number>1</number>
		<pages>20-27</pages>
		<title type="sharef:primaryTitle">An Overview of Location-Based Services</title>
		<volume>21</volume>
	</reference>
	<reference name="her05" src="bibtex:article" src-info="bibtex:line-685" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Susan C.</givenname>
				<surname>Herring</surname>
			</person>
			<person>
				<givenname>Lois Ann</givenname>
				<surname>Scheidt</surname>
			</person>
			<person>
				<givenname>Elijah</givenname>
				<surname>Wright</surname>
			</person>
			<person>
				<givenname>Sabrina</givenname>
				<surname>Bonus</surname>
			</person>
		</names>
		<date value="2005"/>
		<abstract>
			<richtext>
				<p>Purpose — Aims to describe systematically the characteristics of weblogs (blogs) — frequently modified web pages in which dated entries are listed in reverse chronological sequence and which are the latest genre of internet communication to attain widespread popularity. Design/methodology/approach — This paper presents the results of a quantitative content analysis of 203 randomly selected blogs, comparing the empirically observable features of the corpus with popular claims about the nature of blogs, and finding them to differ in a number of respects. Findings — Notably, blog authors, journalists and scholars alike exaggerate the extent to which blogs are interlinked, interactive, and oriented towards external events, and underestimate the importance of blogs as individualistic, intimate forms of self-expression. Originality/value — Based on the profile generated by the empirical analysis, considers the likely antecedents of the blog genre, situates it with respect to the dominant forms of digital communication on the internet today, and suggests possible developments of the use of blogs over time in response to changes in user behavior, technology, and the broader ecology of internet genres.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1108/09593840510601513</identifier>
		<title type="sharef:secondaryTitle">Information Technology &amp; People</title>
		<number>2</number>
		<pages>142-171</pages>
		<title type="sharef:primaryTitle">Weblogs as a Bridging Genre</title>
		<identifier type="sharef:uri">http://www.emeraldinsight.com/10.1108/09593840510601513</identifier>
		<identifier type="sharef:uri" resourceType="application/pdf">http://www.blogninja.com/it&amp;p.final.pdf</identifier>
		<volume>18</volume>
	</reference>
	<reference name="iac07" src="bibtex:article" src-info="bibtex:line-703" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Giovanni</givenname>
				<surname>Iachello</surname>
			</person>
			<person>
				<givenname>Jason</givenname>
				<surname>Hong</surname>
			</person>
		</names>
		<date value="2007"/>
		<abstract>
			<richtext>
				<p>The purpose of this article is twofold. First, we summarize research on the topic of privacy in Human-Computer Interaction (HCI), outlining current approaches, results, and trends. Practitioners and researchers can draw upon this review when working on topics related to privacy in the context of HCI and CSCW. The second purpose is that of charting future research trends and of pointing out areas of research that are timely but lagging. This work is based on a comprehensive analysis of published academic and industrial literature spanning three decades, and on the experience of both ourselves and of many of our colleagues.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1561/1100000004</identifier>
		<title type="sharef:secondaryTitle">Foundations and Trends in Human-Computer Interaction</title>
		<number>1</number>
		<pages>1-137</pages>
		<title type="sharef:primaryTitle">End-User Privacy in Human-Computer Interaction</title>
		<volume>1</volume>
	</reference>
	<reference name="coc02" src="bibtex:article" src-info="bibtex:line-719" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Andy</givenname>
				<surname>Cockburn</surname>
			</person>
			<person>
				<givenname>Bruce</givenname>
				<surname>McKenzie</surname>
			</person>
			<person>
				<givenname>Michael</givenname>
				<surname>Jason-Smith</surname>
			</person>
		</names>
		<date value="2002-11"/>
		<abstract>
			<richtext>
				<p>The Back button on web browsers is one of the world's most heavily used user interface components, yet its behaviour is commonly misunderstood. This paper describes the evaluation of a "temporal" alternative to the normal "stack-based" behaviour of Back and Forward. The main difference of the temporal scheme is that it maintains a complete list of previously visited pages. The evaluation compares the efficiency of the stack and temporal schemes in an "out of the box" scenario in which participants were asked to use a "new" version of a commercial browser without any explanation of the presence or absence of new features. This scenario allows us to predict the likely usability impact if commercial browsers were released supporting the temporal scheme. The results showed that the relative efficiency of the two schemes differed across different types of navigational task. In particular, the temporal system poorly supported backtracking to parent pages, but performed better for more distant navigation tasks. The temporal scheme also caused extreme usage patterns, with the subjects either solving tasks very efficiently or very inefficiently, depending on whether they used the Back menu. This observation indicates that adaptations of the temporal system that improve the effectiveness of the Back menu may enhance web navigation.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1006/ijhc.2002.1025</identifier>
		<title type="sharef:secondaryTitle">International Journal of Human Computer Studies</title>
		<number>5</number>
		<title type="sharef:primaryTitle">Pushing Back: Evaluating a New Behaviour for the Back and Forward Buttons in Web Browsers</title>
		<volume>57</volume>
	</reference>
	<reference name="alt77" src="bibtex:article" src-info="bibtex:line-735" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Irwin</givenname>
				<surname>Altman</surname>
			</person>
		</names>
		<date value="1977"/>
		<abstract>
			<richtext>
				<p>Examines privacy as a generic process that occurs in all cultures but that also differs among cultures in terms of the behavioral mechanisms used to regulate desired levels of privacy. Ethnographic data are examined from a variety of cultures, particularly from societies with apparently maximum privacy and minimum privacy and from analyses of various social relationships (e.g., parents and children, in-laws, husbands and wives). It is concluded that privacy is a universal process that involves culturally unique regulatory mechanisms.</p>
			</richtext>
		</abstract>
		<title type="sharef:secondaryTitle">Journal of Social Issues</title>
		<number>3</number>
		<pages>66-84</pages>
		<title type="sharef:primaryTitle">Privacy Regulation: Culturally Universal or Culturally Specific?</title>
		<volume>33</volume>
	</reference>
	<reference name="bee10a" src="bibtex:article" src-info="bibtex:line-750" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Jöran</givenname>
				<surname>Beel</surname>
			</person>
			<person>
				<givenname>Bela</givenname>
				<surname>Gipp</surname>
			</person>
			<person>
				<givenname>Erik</givenname>
				<surname>Wilde</surname>
			</person>
		</names>
		<date value="2010-01"/>
		<abstract>
			<richtext>
				<p>This article introduces and discusses the concept of academic search engine optimization (ASEO). Based on three recently conducted studies, guidelines are provided on how to optimize scholarly literature for academic search engines in general, and for Google Scholar in particular. In addition, we briefly discuss the risk of researchers' illegitimately 'over-optimizing' their articles.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1353/scp.0.0082</identifier>
		<title type="sharef:secondaryTitle">Journal of Scholarly Publishing</title>
		<number>2</number>
		<pages>176-190</pages>
		<title type="sharef:primaryTitle">Academic Search Engine Optimization (ASEO): Optimizing Scholarly Literature for Google Scholar &amp; Co.</title>
		<identifier type="sharef:uri">http://utpjournals.metapress.com/content/1g745112502611pq/</identifier>
		<identifier type="sharef:uri">http://dret.net/netdret/publications#bee10a</identifier>
		<volume>41</volume>
	</reference>
	<reference name="col92" src="bibtex:article" src-info="bibtex:line-769" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>W. Robert</givenname>
				<surname>Collins</surname>
			</person>
			<person>
				<givenname>Keith W.</givenname>
				<surname>Miller</surname>
			</person>
		</names>
		<date value="1992-01"/>
		<abstract>
			<richtext>
				<p>Most computer professionals know that difficult ethical issues may arise in their work. We believe that these professionals want to "do the right thing." They accept their responsibilities as moral agents and they recognize that their special technical skills give them power and responsibilities. However, the will to act ethically is not sufficient; computer professionals also need skills to arrive at reasonable, ethical decisions. In this article we suggest a set of guidelines to help computer professionals consider the ethical dimensions of technical decisions and offer practical advice to individuals who need to make timely decisions in an ethical manner. We call our guidelines a paramedic method to suggest a medical analogy. We use our method on two realistic ethical dilemmas facing computer professionals. We gather and analyze the data and reach conclusions much as the principals in our cases might. Our paramedic method is not a replacement for considered analysis by professional ethicists. It is a method by which computer professionals can quickly organize and view the facts of an ethical dilemma in a systematic and practical fashion.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1016/0164-1212(92)90077-W</identifier>
		<title type="sharef:secondaryTitle">Journal of Systems and Software</title>
		<number>1</number>
		<pages>23-38</pages>
		<title type="sharef:primaryTitle">Paramedic Ethics for Computer Professionals</title>
		<volume>17</volume>
	</reference>
	<reference name="mca06" src="bibtex:article" src-info="bibtex:line-786" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Andrew P.</givenname>
				<surname>McAfee</surname>
			</person>
		</names>
		<date value="2006"/>
		<abstract>
			<richtext>
				<p>There is a new wave of business communication tools including blogs, wikis and group messaging software — which the author has dubbed, collectively, Enterprise 2.0 — that allow for more spontaneous, knowledge-based collaboration. These new tools, the author contends, may well supplant other communication and knowledge management systems with their superior ability to capture tacit knowledge, best practices and relevant experiences from throughout a company and make them readily available to more users. This article offers a paradigm that highlights the salient characteristics of these new technologies, which the author refers to as SLATES (search, links, authoring, tags, extensions, signals). The resulting organizational communication patterns can lead to highly productive and highly collaborative environments by making both the practices of knowledge work and its outputs more visible. Drawing on case studies and survey data, the article offers managers a set of ground rules for implementing the new technologies. First, it is necessary to create a receptive culture in order to prepare the way for new practices. Second, a common platform must be created to allow for a collaboration infrastructure. Third, an informal rollout of the technologies may be preferred to a more formal procedural change. And fourth, managerial support and leadership is crucial. Even when implanted and implemented well, these new technologies will certainly bring with them new challenges. These tools may well reduce management's ability to exert unilateral control and to express some level of negativity. Whether a company's leaders really want this to happen and will be able to resist the temptation to silence dissent is an open question. Leaders will have to play a delicate role if they want Enterprise 2.0 technologies to succeed.</p>
			</richtext>
		</abstract>
		<title type="sharef:secondaryTitle">MIT Sloan Management Review</title>
		<number>3</number>
		<pages>21-28</pages>
		<title type="sharef:primaryTitle">Enterprise 2.0: The Dawn of Emergent Collaboration</title>
		<identifier type="sharef:uri">http://sloanreview.mit.edu/smr/issue/2006/spring/06/</identifier>
		<volume>47</volume>
	</reference>
	<reference name="ret07" src="bibtex:article" src-info="bibtex:line-798" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Cynthia</givenname>
				<surname>Rettig</surname>
			</person>
		</names>
		<date value="2007"/>
		<abstract>
			<richtext>
				<p>Drawing upon a wealth of data, informed experience, and expert opinion — from Thomas Friedman to Bjarne Stroustrup, from David Gelernter to Nicholas Carr — the author builds a case that enterprise software in large organizations has not delivered on its promise to fully integrate and intelligently control complex business processes while remaining flexible enough to adapt to changing business needs. Instead, ERP systems — including both software applications and the data they process — are variegated patchworks, containing 50 or more databases and hundreds of separate software programs installed over decades and interconnected by idiosyncratic, Byzantine, and poorly documented customized processes. To manage this growing complexity, IT departments have grown substantially: Today's IT departments spend 70% to 80% of their budgets just trying to keep existing systems running. The research shows, says the author, that the typical IT structure is so dense and extensive that it's often a miracle that it works at all. Enterprise systems that were supposed to streamline and simplify business processes instead have brought high risks, uncertainty, and a deeply worrying level of complexity. Rather than agility, they have produced rigidity and unexpected barriers to change, a veritable glut of information containing myriad hidden errors, and a cloud of questions regarding their overall benefits. How did this happen? Rettig points to the inherent limitations in the nature of software, the costs of implementation, and the vagaries of data. Indeed, she offers, enterprise software may be just too complex to deliver on its promises. She also suggests that the next new thing — service-oriented architecture (SOA) — is not likely to fare much better, for many of the same reasons. There are no easy fixes, cautions Rettig, save a large dose of sobriety, clear-eyed analysis, and emphasis on simplicity and efficiency.</p>
			</richtext>
		</abstract>
		<title type="sharef:secondaryTitle">MIT Sloan Management Review</title>
		<number>1</number>
		<pages>21-27</pages>
		<title type="sharef:primaryTitle">The Trouble with Enterprise Software</title>
		<identifier type="sharef:uri">http://sloanreview.mit.edu/smr/issue/2007/fall/01/</identifier>
		<volume>49</volume>
	</reference>
	<reference name="sim62" src="bibtex:article" src-info="bibtex:line-814" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Herbert A.</givenname>
				<surname>Simon</surname>
			</person>
		</names>
		<date value="1962-12"/>
		<title type="sharef:secondaryTitle">American Philosophical Society</title>
		<number>6</number>
		<pages>467-482</pages>
		<title type="sharef:primaryTitle">The Architecture of Complexity</title>
		<identifier type="sharef:uri">http://www.jstor.org/stable/985254</identifier>
		<volume>106</volume>
	</reference>
	<reference name="wei76" src="bibtex:article" src-info="bibtex:line-830" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Karl E.</givenname>
				<surname>Weick</surname>
			</person>
		</names>
		<date value="1976-03"/>
		<abstract>
			<richtext>
				<p>In contrast to the prevailing image that elements in organizations are coupled through dense, tight linkages, it is proposed that elements are often tied together frequently and loosely. Using educational organizations as a case in point, it is argued that the concept of loose coupling incorporates a surprising number of disparate observations about organizations, suggests novel functions, creates stubborn problems for methodologists, and generates intriguing questions for scholars. Sample studies of loose coupling are suggested and research priorities are posed to foster cumulative work with this concept.</p>
			</richtext>
		</abstract>
		<title type="sharef:secondaryTitle">Administrative Science Quarterly</title>
		<number>1</number>
		<pages>1-19</pages>
		<title type="sharef:primaryTitle">Educational Organizations as Loosely Coupled Systems</title>
		<identifier type="sharef:uri">http://www.jstor.org/stable/2391875</identifier>
		<volume>21</volume>
	</reference>
	<reference name="ort90" src="bibtex:article" src-info="bibtex:line-847" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>J. Douglas</givenname>
				<surname>Orton</surname>
			</person>
			<person>
				<givenname>Karl E.</givenname>
				<surname>Weick</surname>
			</person>
		</names>
		<date value="1990-04"/>
		<abstract>
			<richtext>
				<p>Diverse applications of the concept of loose coupling are embodied in five recurring voices that focus separately on causation, typology, effects, compensations, and outcomes. Each has a tendency to drift away from a dialectical interpretation of loose coupling toward a unidimensional interpretation of loose coupling, thereby weakening the explanatory value of the concept. The authors first use the five voices to review the loose coupling literature and then to suggest more precise and more productive uses of the concept.</p>
			</richtext>
		</abstract>
		<title type="sharef:secondaryTitle">Academy of Management Review</title>
		<number>2</number>
		<pages>203-223</pages>
		<title type="sharef:primaryTitle">Loosely Coupled Systems: A Reconceptualization</title>
		<identifier type="sharef:uri">http://www.jstor.org/stable/258154</identifier>
		<volume>15</volume>
	</reference>
	<reference name="boy07" src="bibtex:article" src-info="bibtex:line-864" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Danah M.</givenname>
				<surname>Boyd</surname>
			</person>
			<person>
				<givenname>Nicole B.</givenname>
				<surname>Ellison</surname>
			</person>
		</names>
		<date value="2007-10"/>
		<abstract>
			<richtext>
				<p>Social network sites (SNSs) are increasingly attracting the attention of academic and industry researchers intrigued by their affordances and reach. This special theme section of the Journal of Computer-Mediated Communication brings together scholarship on these emergent phenomena. In this introductory article, we describe features of SNSs and propose a comprehensive definition. We then present one perspective on the history of such sites, discussing key changes and developments. After briefly summarizing existing scholarship concerning SNSs, we discuss the articles in this special section and conclude with considerations for future research.</p>
			</richtext>
		</abstract>
		<title type="sharef:secondaryTitle">Journal of Computer-Mediated Communication</title>
		<number>1</number>
		<title type="sharef:primaryTitle">Social Network Sites: Definition, History, and Scholarship</title>
		<identifier type="sharef:uri" resourceType="text/html">http://jcmc.indiana.edu/vol13/issue1/boyd.ellison.html</identifier>
		<volume>13</volume>
	</reference>
	<reference name="got07" src="bibtex:article" src-info="bibtex:line-880" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Greg</givenname>
				<surname>Goth</surname>
			</person>
		</names>
		<date value="2007-11"/>
		<abstract>
			<richtext>
				<p>iPhone hackers, spectrum auctions, new carrier technology might doom mobile network carriers' "garden wall" restrictions on consumer choices.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1109/MDSO.2007.64</identifier>
		<title type="sharef:secondaryTitle">IEEE Distributed Systems Online</title>
		<number>11</number>
		<title type="sharef:primaryTitle">Opening the Mobile Net</title>
		<identifier type="sharef:uri">http://www.firstmonday.org/issues/issue11_10/duguid/</identifier>
		<volume>8</volume>
	</reference>
	<reference name="sha09" src="bibtex:article" src-info="bibtex:line-897" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Rajiv</givenname>
				<surname>Shah</surname>
			</person>
			<person>
				<givenname>Jay</givenname>
				<surname>Kesan</surname>
			</person>
		</names>
		<date value="2009-06"/>
		<abstract>
			<richtext>
				<p>Governments around the world are considering implementing or even mandating open standards policies. They believe these policies will provide economic, socio-political, and technical benefits. In this article, we analyze the failure of the Massachusetts's open standards policy as applied to document formats. We argue it failed due to the lack of running code. Running code refers to multiple independent, interoperable implementations of an open standard. With running code, users have choice in their adoption of a software product and consequently economic and technological benefits. We urge governments to incorporate a "running code" requirement when adopting an open standards policy.</p>
			</richtext>
		</abstract>
		<title type="sharef:secondaryTitle">First Monday</title>
		<number>6</number>
		<title type="sharef:primaryTitle">Running Code as Part of an Open Standards Policy</title>
		<identifier type="sharef:uri">http://www.uic.edu/htbin/cgiwrap/bin/ojs/index.php/fm/article/view/2414/2201</identifier>
		<volume>14</volume>
	</reference>
	<reference name="hub09" src="bibtex:article" src-info="bibtex:line-909" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Bernardo A.</givenname>
				<surname>Huberman</surname>
			</person>
			<person>
				<givenname>Daniel M.</givenname>
				<surname>Romero</surname>
			</person>
			<person>
				<givenname>Fang</givenname>
				<surname>Wu</surname>
			</person>
		</names>
		<date value="2009-01"/>
		<abstract>
			<richtext>
				<p>Scholars, advertisers and political activists see massive online social networks as a representation of social interactions that can be used to study the propagation of ideas, social bond dynamics and viral marketing, among others. But the linked structures of social networks do not reveal actual interactions among people. Scarcity of attention and the daily rhythms of life and work makes people default to interacting with those few that matter and that reciprocate their attention. A study of social interactions within Twitter reveals that the driver of usage is a sparse and hidden network of connections underlying the "declared" set of friends and followers.</p>
			</richtext>
		</abstract>
		<title type="sharef:secondaryTitle">First Monday</title>
		<number>1</number>
		<title type="sharef:primaryTitle">Social Networks That Matter: Twitter Under the Microscope</title>
		<identifier type="sharef:uri">http://firstmonday.org/htbin/cgiwrap/bin/ojs/index.php/fm/article/view/2317/2063</identifier>
		<volume>14</volume>
	</reference>
	<reference name="dug06" src="bibtex:article" src-info="bibtex:line-921" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Paul</givenname>
				<surname>Duguid</surname>
			</person>
		</names>
		<date value="2006-10"/>
		<abstract>
			<richtext>
				<p>People often implicitly ascribe the quality of peer-production projects such as Project Gutenberg or Wikipedia to what I call "laws" of quality. These are drawn from Open Source software development and it is not clear how applicable they are outside the realm of software. I look at examples from peer production projects to ask whether faith in these laws does not so much guarantee quality as hide the need for improvement.</p>
			</richtext>
		</abstract>
		<title type="sharef:secondaryTitle">First Monday</title>
		<number>10</number>
		<title type="sharef:primaryTitle">Peer Production and "Laws of Quality"</title>
		<identifier type="sharef:uri">http://www.firstmonday.org/issues/issue11_10/duguid/</identifier>
		<volume>11</volume>
	</reference>
	<reference name="bro01" src="bibtex:article" src-info="bibtex:line-933" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Barry</givenname>
				<surname>Brown</surname>
			</person>
			<person>
				<givenname>Abigail J.</givenname>
				<surname>Sellen</surname>
			</person>
		</names>
		<date value="2001-09"/>
		<abstract>
			<richtext>
				<p>While browsing the Web is a widespread everyday activity there is a shortage of detailed understanding of how users organise their Web usage. In this paper we present results from a qualitative in-depth interview study of how users browse the Web and combine browsing with their other activities. The data are  used to explore three particular problems which users have with browsing the Web. Firstly, users have problems managing their favourites, and in particular accessing their favourites through a hierarchical menu. Second, users have problems with combining information across different Web sites — what we call the "meta-task" problem. Third, users have concerns with security and privacy, although these concerns seem to change as users become more experienced with shopping on the Web. We discuss three concepts which address these problems: "home page favourites", "Web clipping" and the "Web card". These concepts are attempts at incremental improvements to the Web without affecting the Web's essential simplicity.</p>
			</richtext>
		</abstract>
		<title type="sharef:secondaryTitle">First Monday</title>
		<number>9</number>
		<title type="sharef:primaryTitle">Exploring Users' Experiences of the Web</title>
		<identifier type="sharef:uri">http://www.uic.edu/htbin/cgiwrap/bin/ojs/index.php/fm/article/view/882/791</identifier>
		<volume>6</volume>
	</reference>
	<reference name="kei04" src="bibtex:article" src-info="bibtex:line-949" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Corey</givenname>
				<surname>Keith</surname>
			</person>
		</names>
		<date value="2004"/>
		<abstract>
			<richtext>
				<p>This paper describes the MARCXML architecture implemented at the Library of Congress. It gives an overview of the component pieces of the architecture, including the MARCXML schema and the MARCXML toolkit, while giving a brief tutorial on their use. Several different applications of the architecture and tools are discussed to illustrate the features of the toolkit being developed thus far. Nearly any metadata format can take advantage of the features of the toolkit, and the process of the toolkit enabling a new format is discussed. Finally, this paper intends to foster new ideas with regards to the transformation of descriptive metadata, especially using XML tools. In this paper the following conventions will be used: MARC21 will refer to MARC 21 records in the ISO 2709 record structure used today; MARCXML will refer to MARC 21 records in an XML structure.</p>
			</richtext>
		</abstract>
		<title type="sharef:secondaryTitle">Library Hi Tech</title>
		<number>2</number>
		<pages>122-130</pages>
		<title type="sharef:primaryTitle">Using XSLT to Manipulate MARC Metadata</title>
		<field type="bibtex:topic">marc[0.7] marcxml[0.8]</field>
		<identifier type="sharef:uri">http://taddeo.emeraldinsight.com/vl=985643/cl=94/nw=1/rpsv/cgi-bin/linker?ini=emerald&amp;reqidx=/cw/mcb/07378831/v22n2/s2/p122</identifier>
		<volume>22</volume>
	</reference>
	<reference name="rus06" src="bibtex:article" src-info="bibtex:line-966" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Andrew L.</givenname>
				<surname>Russell</surname>
			</person>
		</names>
		<date value="2006"/>
		<abstract>
			<richtext>
				<p>Internet historians recognize the technical achievements but often overlook the bureaucratic innovations of Internet pioneers. The phrase, "We reject: kings, presidents, and voting. We believe in: rough consensus and running code," was coined by David Clark in 1992. This article explains how the phrase captured the technical and political values of Internet engineers during a crucial phase in the Internet's growth.</p>
			</richtext>
		</abstract>
		<title type="sharef:secondaryTitle">IEEE Annals of the History of Computing</title>
		<number>3</number>
		<pages>48-61</pages>
		<title type="sharef:primaryTitle">'Rough Consensus and Running Code' and the Internet-OSI Standards War</title>
		<identifier type="sharef:uri" resourceType="application/pdf">http://info.computer.org/portal/cms_docs_annals/annals/content/promo2.pdf</identifier>
		<volume>28</volume>
	</reference>
	<reference name="rol00" src="bibtex:article" src-info="bibtex:line-982" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Colette</givenname>
				<surname>Rolland</surname>
			</person>
			<person>
				<givenname>Naveen</givenname>
				<surname>Prakash</surname>
			</person>
		</names>
		<date value="2000"/>
		<abstract>
			<richtext>
				<p>Conceptual modelling is situated in the broader view of information systems requirements engineering. Requirements Engineering (RE) explores the objectives of different stakeholders and the activities carried out by them to meet these objectives in order to derive purposeful system requirements and therefore lead to better quality systems, i.e., systems that meet the requirements of their users. Thus RE product models use concepts for modelling these instead of concepts like data, process, events, etc., used in conceptual models. Since the former are more stable than the latter, requirements engineering manages change better. The paper gives the rationale for extending traditional conceptual models and introduces some RE product models. Furthermore, in contrast to conceptual modelling, requirements engineering lays great stress on the engineering process employed. The paper introduces some RE process models and considers their effect on tool support.</p>
			</richtext>
		</abstract>
		<title type="sharef:secondaryTitle">Annals of Software Engineering</title>
		<number>1-4</number>
		<pages>151-176</pages>
		<title type="sharef:primaryTitle">From Conceptual Modelling to Requirements Engineering</title>
		<identifier type="sharef:uri">http://springerlink.metapress.com/link.asp?id=u8k605t66123lp12</identifier>
		<volume>10</volume>
	</reference>
	<reference name="bur08" src="bibtex:article" src-info="bibtex:line-998" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Jenna</givenname>
				<surname>Burrell</surname>
			</person>
		</names>
		<date value="2008"/>
		<abstract>
			<richtext>
				<p>Internet scamming strategies associated with West Africa typically involve the creation and deployment of fictional narratives depicting political turmoil, corruption, violence, poverty, and personal tragedy set in a variety of African nations. This article examines Internet scammers complicity in promoting these creatively dramatic and yet stereotyped representations of Africa and Africans. Their approach is an example of what De Certeau describes as a 'tactic' where scammers manipulate the space of representations produced by hegemonic forces in the West to realize subversive ends. The attempts of Internet scammers highlight the difficulties of creating selfrepresentations that are both 'authentic' and persuasive underlining the complexity inherent in efforts by marginalized communities to be heard by those they perceive as powerful. This remains the case despite new mechanisms of communication, such as the Internet, that make connecting (in a purely functional sense) much easier and less expensive.</p>
			</richtext>
		</abstract>
		<title type="sharef:secondaryTitle">Information Technology and International Development</title>
		<title type="sharef:primaryTitle">Problematic Empowerment: West African Internet Scams as Strategic Misrepresentation</title>
		<identifier type="sharef:uri">http://www.mitpressjournals.org/toc/itid/</identifier>
	</reference>
	<reference name="fan03" src="bibtex:article" src-info="bibtex:line-1011" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Wenfei</givenname>
				<surname>Fan</surname>
			</person>
			<person>
				<givenname>Jérôme</givenname>
				<surname>Siméon</surname>
			</person>
		</names>
		<date value="2003-02"/>
		<abstract>
			<richtext>
				<p>Integrity constraints have proved fundamentally important in database management. The ID/IDREF mechanism provided by XML DTDs relies on a simple form of constraints to describe references. Yet, this mechanism is sufficient neither for specifying references in XML documents, nor for expressing semantic constraints commonly found in databases. In this paper, we extend XML DTDs with several classes of integrity constraints and investigate the complexity of reasoning about these constraints. The constraints range over keys, foreign keys, inverse constraints as well as ID constraints for capturing the semantics of object identities. They improve semantic specifications and provide a better reference mechanism for native XML applications. They are also useful in information exchange and data integration for preserving the semantics of data originating in relational and object-oriented databases. We establish complexity and axiomatization results for the (finite) implication problems associated with these constraints. In addition, we study implication of more general constraints, such as functional, inclusion and inverse constraints defined in terms of navigation paths.</p>
			</richtext>
		</abstract>
		<title type="sharef:secondaryTitle">Journal of Computer and System Sciences</title>
		<number>1</number>
		<pages>254-291</pages>
		<title type="sharef:primaryTitle">Integrity Constraints for XML</title>
		<identifier type="sharef:uri" resourceType="application/pdf">http://www.lfcs.inf.ed.ac.uk/research/database/publications/jcss03.pdf</identifier>
		<volume>66</volume>
	</reference>
	<reference name="deb05" src="bibtex:article" src-info="bibtex:line-1028" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Philippe</givenname>
				<surname>Debaty</surname>
			</person>
			<person>
				<givenname>Patrick</givenname>
				<surname>Goddi</surname>
			</person>
			<person>
				<givenname>Alex</givenname>
				<surname>Vorbau</surname>
			</person>
		</names>
		<date value="2005"/>
		<abstract>
			<richtext>
				<p>This work has its roots in the HP Labs Cooltown project, whose core principle is that the integration of our physical world with the Web offers unique opportunities to enable ubiquitous computing applications. This paper describes our latest results in building a model and a software architecture called the Web presence manager (WPM) to support this physical-virtual integration. This software layer implements and specifies the services and information provided by Web representations of physical entities such as people, places, or things. We detail an extensive context-enhanced media-oriented application built on top of our platform. Our application enables mobile and context-aware access to personal contents and rendering on local appliances in a variety of ubiquitous computing environments.</p>
			</richtext>
		</abstract>
		<title type="sharef:secondaryTitle">Mobile Networks and Applications</title>
		<number>4</number>
		<pages>385-394</pages>
		<title type="sharef:primaryTitle">Integrating the Physical World with the Web to Enable Context-Enhanced Mobile Services</title>
		<field type="bibtex:topic">cooltown[1]</field>
		<volume>10</volume>
	</reference>
	<reference name="kin02" src="bibtex:article" src-info="bibtex:line-1040" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Tim</givenname>
				<surname>Kindberg</surname>
			</person>
			<person>
				<givenname>John J.</givenname>
				<surname>Barton</surname>
			</person>
			<person>
				<givenname>Jeff</givenname>
				<surname>Morgan</surname>
			</person>
			<person>
				<givenname>Gene</givenname>
				<surname>Becker</surname>
			</person>
			<person>
				<givenname>Debbie</givenname>
				<surname>Caswell</surname>
			</person>
			<person>
				<givenname>Philippe</givenname>
				<surname>Debaty</surname>
			</person>
			<person>
				<givenname>Gita</givenname>
				<surname>Gopal</surname>
			</person>
			<person>
				<givenname>Marcos</givenname>
				<surname>Frid</surname>
			</person>
			<person>
				<givenname>Venky</givenname>
				<surname>Krishnan</surname>
			</person>
			<person>
				<givenname>Howard</givenname>
				<surname>Morris</surname>
			</person>
			<person>
				<givenname>John</givenname>
				<surname>Schettino</surname>
			</person>
			<person>
				<givenname>Bill</givenname>
				<surname>Serra</surname>
			</person>
			<person>
				<givenname>Mirjana</givenname>
				<surname>Spasojevic</surname>
			</person>
		</names>
		<date value="2002"/>
		<abstract>
			<richtext>
				<p>The convergence of Web technology, wireless networks, and portable client devices provides new design opportunities for computer/communications systems. In the HP Labs' "Cooltown" project we have been exploring these opportunities through an infrastructure to support "web presence" for people, places and things. We put web servers into things like printers and put information into web servers about things like artwork; we group physically related things into places embodied in web servers. Using URLs for addressing, physical URL beaconing and sensing of URLs for discovery, and localized web servers for directories, we can create a location-aware but ubiquitous system to support nomadic users. On top of this infrastructure we can leverage Internet connectivity to support communications services. Web presence bridges the World Wide Web and the physical world we inhabit, providing a model for supporting nomadic users without a central control point.</p>
			</richtext>
		</abstract>
		<title type="sharef:secondaryTitle">Mobile Networks and Applications</title>
		<number>5</number>
		<pages>365-376</pages>
		<title type="sharef:primaryTitle">People, Places, Things: Web Presence for the Real World</title>
		<field type="bibtex:topic">cooltown[1]</field>
		<volume>7</volume>
	</reference>
	<reference name="bar99" src="bibtex:article" src-info="bibtex:line-1056" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Judit</givenname>
				<surname>Bar-Ilan</surname>
			</person>
		</names>
		<date value="1999"/>
		<abstract>
			<richtext>
				<p>This paper examines the performance of search engines over time. The performance is not as expected: search engines loose information, relevant URLs that were retrieved at a given time by a certain search engine, were not retrieved by the same search engine at a later time, although they continued to exist and to be relevant. A closer examination of the these URLs revealed that not only URLs were dropped, but content was also lost for a large portion of these URLs: no other URL retrieved by the search engine contained the same information. As far as we know this aspect of the performance of search engines has not been thoroughly studied before. The problem is investigated through a case study, using the search phrase "informetrics OR informetric". The searches were carried out in one month intervals during a five months period between January and June 1998. An additional search round and comparison were carried out on June 1999. The six largest search engines at the time were examined.</p>
			</richtext>
		</abstract>
		<title type="sharef:secondaryTitle">Cybermetrics: International Journal of Scientometrics, Informetrics and Bibliometrics</title>
		<number>1</number>
		<title type="sharef:primaryTitle">Search Engine Results over Time — A Case Study on Search Engine Stability</title>
		<identifier type="sharef:uri" resourceType="text/html">http://www.cindoc.csic.es/cybermetrics/articles/v2i1p1.html</identifier>
		<volume>2/3</volume>
	</reference>
	<reference name="the01" src="bibtex:article" src-info="bibtex:line-1067" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Mike</givenname>
				<surname>Thelwall</surname>
			</person>
		</names>
		<date value="2001"/>
		<abstract>
			<richtext>
				<p>Search engines are an important tool for information foraging on the web. The broad details of how they work is, therefore, of relevance to both information seekers and providers. Yet search engines are known to only index a fraction of the web, up to a maximum of 16% in one recent study. A search engine must crawl the web periodically in order to maintain an up to date index, but, given the limitations of total coverage, how can it decide which sites to cover and which to ignore? One answer lies in research showing the importance of web links in identifying useful sources of information. This paper reports on an experiment to investigate the effect of link count on the indexing of 1000 sites in three search portals over a period of seven months. It was found that, although all engines added sites during the period of the survey, only Google showed evidence of being very responsive to the existence of links on the test site, whereas AltaVista's results were very stable over time.</p>
			</richtext>
		</abstract>
		<title type="sharef:secondaryTitle">Cybermetrics: International Journal of Scientometrics, Informetrics and Bibliometrics</title>
		<number>1</number>
		<title type="sharef:primaryTitle">The Responsiveness of Search Engine Indexes</title>
		<identifier type="sharef:uri" resourceType="text/html">http://www.cindoc.csic.es/cybermetrics/articles/v5i1p1.html</identifier>
		<volume>5</volume>
	</reference>
	<reference name="mor98" src="bibtex:article" src-info="bibtex:line-1082" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Luc</givenname>
				<surname>Moreau</surname>
			</person>
			<person>
				<givenname>Wendy</givenname>
				<surname>Hall</surname>
			</person>
		</names>
		<date value="1998"/>
		<abstract>
			<richtext>
				<p>In this paper, we study how linking mechanisms contribute to the expressiveness of hypertext systems. For this purpose, we formalize hypertext systems as abstract machines. As the primary benefit of hypertext systems is to be able to read documents non-linearly, their expressiveness is defined in terms of the ability to follow links. Then, we classify hypertext systems according to the power of the underlying automaton. The model allows us to compare embedded versus separate links and simple versus generic links. Then, we investigate history mechanisms, adaptive hypertexts and functional links. Our conclusion is that simple links, whether embedded or separate, generic links and some adaptive links all give hypertext systems the power of finite state automata. The history mechanism confers to them the power of pushdown automata, whereas the general functional links give them Turing completeness.</p>
			</richtext>
		</abstract>
		<title type="sharef:secondaryTitle">The Computer Journal</title>
		<number>7</number>
		<pages>459-473</pages>
		<title type="sharef:primaryTitle">On the Expressiveness of Links in Hypertext Systems</title>
		<identifier type="sharef:uri">http://comjnl.oxfordjournals.org/cgi/content/abstract/41/7/459</identifier>
		<volume>41</volume>
	</reference>
	<reference name="car02" src="bibtex:article" src-info="bibtex:line-1098" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Srdjan</givenname>
				<surname>Čaronapkun</surname>
			</person>
			<person>
				<givenname>Maher</givenname>
				<surname>Hamdi</surname>
			</person>
			<person>
				<givenname>Jean-Pierre</givenname>
				<surname>Hubaux</surname>
			</person>
		</names>
		<date value="2002-04"/>
		<abstract>
			<richtext>
				<p>We consider the problem of node positioning in ad hoc networks. We propose a distributed, infrastructure-free positioning algorithm that does not rely on GPS (Global Positioning System). Instead, the algorithm uses the distances between the nodes to build a relative coordinate system in which the node positions are computed in two dimensions. Despite the distance measurement errors and the motion of the nodes, the algorithm provides sufficient location information and accuracy to support basic network functions. Examples of applications where this algorithm can be used include Location Aided Routing and Geodesic Packet Forwarding. Another example are sensor networks, where mobility is less of a problem. The main contribution of this work is to define and compute relative positions of the nodes in an ad hoc network without using GPS. We further explain how the proposed approach can be applied to wide area ad hoc networks.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1023/A:1013933626682</identifier>
		<title type="sharef:secondaryTitle">Cluster Computing</title>
		<number>2</number>
		<pages>157-167</pages>
		<title type="sharef:primaryTitle">GPS-free Positioning in Mobile Ad Hoc Networks</title>
		<identifier type="sharef:uri">http://www.springerlink.com/content/xp3j7ra35hyfv474/</identifier>
		<volume>5</volume>
	</reference>
	<reference name="bat08" src="bibtex:article" src-info="bibtex:line-1116" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Robert</givenname>
				<surname>Battle</surname>
			</person>
			<person>
				<givenname>Edward</givenname>
				<surname>Benson</surname>
			</person>
		</names>
		<date value="2008"/>
		<abstract>
			<richtext>
				<p>Semantic Web technologies must integrate with Web 2.0 services for both to leverage each others strengths. We argue that the REST-based design methodologies of the web present the ideal mechanism through which to align the publication of semantic data with the existing web architecture. We present the design and implementation of two solutions that combine REST-based design and RDF data access: one solution for integrating existing web services and one server-side solution for creating RDF REST services. Both of these solutions enable SPARQL to be a unifying data access layer for aligning the Semantic Web and Web 2.0.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">doi:10.1016/j.websem.2007.11.002</identifier>
		<title type="sharef:secondaryTitle">Journal of Web Semantics</title>
		<number>1</number>
		<title type="sharef:primaryTitle">Bridging the Semantic Web and Web 2.0 with Representational State Transfer (REST)</title>
		<field type="bibtex:topic">rest[0.8] rdf[0.8] sparql[0.8]</field>
		<volume>6</volume>
	</reference>
	<reference name="fik05" src="bibtex:article" src-info="bibtex:line-1128" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Richard</givenname>
				<surname>Fikes</surname>
			</person>
			<person>
				<givenname>Patrick</givenname>
				<surname>Hayes</surname>
			</person>
			<person>
				<givenname>Ian</givenname>
				<surname>Horrocks</surname>
			</person>
		</names>
		<date value="2005"/>
		<abstract>
			<richtext>
				<p>This paper discusses the issues involved in designing a query language for the Semantic Web and presents the OWL Query Language (OWL-QL) as a candidate standard language and protocol for query-answering dialogues among Semantic Web computational agents using knowledge represented in the W3C's Ontology Web Language (OWL). OWL-QL is a formal language and precisely specifies the semantic relationships among a query, a query answer, and the knowledge base(s) used to produce the answer. Unlike standard database and Web query languages, OWL-QL supports query-answering dialogues in which the answering agent may use automated reasoning methods to derive answers to queries, as well as dialogues in which the knowledge to be used in answering a query may be in multiple knowledge bases on the Semantic Web, and/or where those knowledge bases are not specified by the querying agent. In this setting, the set of answers to a query may be of unpredictable size and may require an unpredictable amount of time to compute.</p>
			</richtext>
		</abstract>
		<title type="sharef:secondaryTitle">Journal of Web Semantics</title>
		<number>1</number>
		<title type="sharef:primaryTitle">OWL-QL — A Language for Deductive Query Answering on the Semantic Web</title>
		<field type="bibtex:topic">owl[0.8] owlql[0.9]</field>
		<identifier type="sharef:uri">http://www.websemanticsjournal.org/ps/pub/2005-7</identifier>
		<volume>2</volume>
	</reference>
	<reference name="haa05" src="bibtex:article" src-info="bibtex:line-1140" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Peter</givenname>
				<surname>Haase</surname>
			</person>
			<person>
				<givenname>Björn</givenname>
				<surname>Schnizler</surname>
			</person>
			<person>
				<givenname>Jeen</givenname>
				<surname>Broekstra</surname>
			</person>
			<person>
				<givenname>Marc</givenname>
				<surname>Ehrig</surname>
			</person>
			<person>
				<givenname>Frank</givenname>
				<surname link="van">Harmelen</surname>
			</person>
			<person>
				<givenname>Maarten</givenname>
				<surname>Menken</surname>
			</person>
			<person>
				<givenname>Peter</givenname>
				<surname>Mika</surname>
			</person>
			<person>
				<givenname>Michal</givenname>
				<surname>Plechawski</surname>
			</person>
			<person>
				<givenname>Pawel Pyszlakand Ronny</givenname>
				<surname>Siebes</surname>
			</person>
			<person>
				<givenname>Steffen</givenname>
				<surname>Staab</surname>
			</person>
			<person>
				<givenname>Christoph</givenname>
				<surname>Tempich</surname>
			</person>
		</names>
		<date value="2005"/>
		<abstract>
			<richtext>
				<p>This paper describes Bibster, a Peer-to-Peer system for exchanging bibliographic metadata among researchers. We show how Bibster exploits ontologies in data-representation, query formulation, query routing, and query result presentation. The Bibster system is freely available and is used by researchers across multiple organizations.</p>
			</richtext>
		</abstract>
		<title type="sharef:secondaryTitle">Journal of Web Semantics</title>
		<number>1</number>
		<title type="sharef:primaryTitle">Bibster — A Semantics-Based Bibliographic Peer-to-Peer System</title>
		<field type="bibtex:topic">bibster[0.9]</field>
		<identifier type="sharef:uri">http://www.websemanticsjournal.org/ps/pub/2005-8</identifier>
		<volume>2</volume>
	</reference>
	<reference name="hor04" src="bibtex:article" src-info="bibtex:line-1152" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Ian</givenname>
				<surname>Horrocks</surname>
			</person>
			<person>
				<givenname>Peter F.</givenname>
				<surname>Patel-Schneider</surname>
			</person>
			<person>
				<givenname>Frank</givenname>
				<surname link="van">Harmelen</surname>
			</person>
		</names>
		<date value="2004"/>
		<abstract>
			<richtext>
				<p>The OWL Web Ontology Language is a new formal language for representing ontologies in the Semantic Web. OWL has features from several families of representation languages, including primarily Description Logics and frames. OWL also shares many characteristics with RDF, the W3C base of the Semantic Web. In this paper we discuss how the philosophy and features of OWL can be traced back to these older formalisms, with modifications driven by several other constraints on OWL. Several interesting problems have arisen where these influences on OWL have clashed.</p>
			</richtext>
		</abstract>
		<title type="sharef:secondaryTitle">Journal of Web Semantics</title>
		<number>1</number>
		<title type="sharef:primaryTitle">From SHIQ and RDF to OWL: The Making of a Web Ontology Language</title>
		<field type="bibtex:topic">rdf[0.6] shiq[0.6] owl[0.8]</field>
		<identifier type="sharef:uri">http://www.websemanticsjournal.org/ps/pub/2004-1</identifier>
		<volume>1</volume>
	</reference>
	<reference name="del05" src="bibtex:article" src-info="bibtex:line-1164" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Dell</givenname>
				<surname>Zhang</surname>
			</person>
			<person>
				<givenname>Wee Sun</givenname>
				<surname>Lee</surname>
			</person>
		</names>
		<date value="2005"/>
		<abstract>
			<richtext>
				<p>We investigate machine learning methods for automatically integrating objects from different taxonomies into a master taxonomy. This problem is not only currently pervasive on the Web, but is also important to the emerging Semantic Web. A straightforward approach to automating this process would be to build classifiers through machine learning and then use these classifiers to classify objects from the source taxonomies into categories of the master taxonomy. However, conventional machine learning algorithms totally ignore the availability of the source taxonomies. In fact, source and master taxonomies often have common categories under different names or other more complex semantic overlaps. We introduce two techniques that exploit the semantic overlap between the source and master taxonomies to build better classifiers for the master taxonomy. The first technique, Cluster Shrinkage, biases the learning algorithm against splitting source categories by making objects in the same category appear more similar to each other. The second technique, Co-Bootstrapping, tries to facilitate the exploitation of inter-taxonomy relationships by providing category indicator functions as additional features for the objects. Our experiments with real-world Web data show that these proposed add-on techniques can enhance various machine learning algorithms to achieve substantial improvements in performance for taxonomy integration.</p>
			</richtext>
		</abstract>
		<title type="sharef:secondaryTitle">Journal of Web Semantics</title>
		<number>2</number>
		<title type="sharef:primaryTitle">Learning to Integrate Web Taxonomies</title>
		<identifier type="sharef:uri">http://www.websemanticsjournal.org/ps/pub/2005-13</identifier>
		<volume>2</volume>
	</reference>
	<reference name="sad04" src="bibtex:article" src-info="bibtex:line-1179" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>G. Sudha</givenname>
				<surname>Sadasivam</surname>
			</person>
			<person>
				<givenname>A.</givenname>
				<surname>Chitra</surname>
			</person>
		</names>
		<date value="2004-02"/>
		<abstract>
			<richtext>
				<p>The interaction between components and objects in a distributed environment should be highly efficient and transparent to the application programmer. High efficiency can be achieved by improving the inter-processor communication (IPC) mechanism in micro kernels, while transparency can be achieved through interface definition languages (IDLs). Different encoding mechanisms like Extended Data Representation (XDR), Network Data Representation (NDR) and Common Data Representation (CDR) facilitate inter-component communication transparently and efficiently. Marshalling procedures convert data in local machine representation into common network representations. Common Object Request Broker Architecture (CORBA) uses CDR representation to encode data. This paper proposes certain changes that can be incorporated in the CDR encoding mechanism, to achieve better efficiency in transmission. The changes include the following: A bit representation for the boolean array; Removing data alignment at word boundaries; Exact allocation of send and receive buffer space depending on the data type being transmitted; Adopting inlining mechanism for some primitive data types to improve efficiency.</p>
			</richtext>
		</abstract>
		<title type="sharef:secondaryTitle">Academic Open Internet Journal</title>
		<number>11</number>
		<title type="sharef:primaryTitle">Certain Improvements In Marshalling</title>
		<field type="bibtex:topic">ndr[0.8] xdr[0.8] cdr[0.8]</field>
		<identifier type="sharef:uri">http://www.acadjournal.com/2004/v11/Part5/p1/</identifier>
	</reference>
	<reference name="ken03" src="bibtex:article" src-info="bibtex:line-1195" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Jeff</givenname>
				<surname>Kenyon</surname>
			</person>
		</names>
		<date value="2003-02"/>
		<abstract>
			<richtext>
				<p>Current standards for SOAP, WSDL, and UDDI have no explicit support for the versioning and deprecation of Web services. This article introduces a means for Web service versioning and deprecation that is lightweight and flexible, and requires minimal development effort.</p>
			</richtext>
		</abstract>
		<title type="sharef:secondaryTitle">Web Services Journal</title>
		<number>2</number>
		<title type="sharef:primaryTitle">Web Service Versioning and Deprecation</title>
		<identifier type="sharef:uri">http://www.sys-con.com/webservices/article.cfm?id=467</identifier>
		<identifier type="sharef:uri">http://www.findarticles.com/p/articles/mi_m0MLV/is_2_3/ai_97467594</identifier>
		<volume>3</volume>
	</reference>
	<reference name="rah01" src="bibtex:article" src-info="bibtex:line-1212" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Erhard</givenname>
				<surname>Rahm</surname>
			</person>
			<person>
				<givenname>Philip A.</givenname>
				<surname>Bernstein</surname>
			</person>
		</names>
		<date value="2001-12"/>
		<abstract>
			<richtext>
				<p>Schema matching is a basic problem in many database application domains, such as data integration, E-business, data warehousing, and semantic query processing. In current implementations, schema matching is typically performed manually, which has significant limitations. On the other hand, previous research papers have proposed many techniques to achieve a partial automation of the match operation for specific application domains. We present a taxonomy that covers many of these existing approaches, and we describe the approaches in some detail. In particular,we distinguish between schema-level and instance-level, element-level and structure-level, and language-based and constraint-based matchers. Based on our classification we review some previous match implementations thereby indicating which part of the solution space they cover.We intend our taxonomy and review of past work to be useful when comparing different approaches to schema matching, when developing a new match algorithm, and when implementing a schema matching component.</p>
			</richtext>
		</abstract>
		<title type="sharef:secondaryTitle">The International Journal on Very Large Data Bases</title>
		<number>4</number>
		<pages>334-350</pages>
		<title type="sharef:primaryTitle">A Survey of Approaches to Automatic Schema Matching</title>
		<identifier type="sharef:uri" resourceType="application/pdf">http://research.microsoft.com/~philbe/VLDBJ-Dec2001.pdf</identifier>
		<volume>10</volume>
	</reference>
	<reference name="sha01" src="bibtex:article" src-info="bibtex:line-1225" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Jayavel</givenname>
				<surname>Shanmugasundaram</surname>
			</person>
			<person>
				<givenname>Eugene</givenname>
				<surname>Shekita</surname>
			</person>
			<person>
				<givenname>Rimon</givenname>
				<surname>Barr</surname>
			</person>
			<person>
				<givenname>Michael J.</givenname>
				<surname>Carey</surname>
			</person>
			<person>
				<givenname>Bruce</givenname>
				<surname>Lindsay</surname>
			</person>
			<person>
				<givenname>Hamid</givenname>
				<surname>Pirahesh</surname>
			</person>
			<person>
				<givenname>Berthold</givenname>
				<surname>Reinwald</surname>
			</person>
		</names>
		<date value="2001-12"/>
		<abstract>
			<richtext>
				<p>XML is rapidly emerging as a standard for exchanging business data on the World Wide Web. For the foreseeable future, however, most business data will continue to be stored in relational database systems. Consequently, if XML is to fulfill its potential, some mechanism is needed to publish relational data as XML documents. Towards that goal, one of the major challenges is finding a way to efficiently structure and tag data from one or more tables as a hierarchical XML document. Different alternatives are possible depending on when this processing takes place and how much of it is done inside the relational engine. In this paper, we characterize and study the performance of these alternatives. Among other things, we explore the use of new scalar and aggregate functions in SQL for constructing complex XML documents directly in the relational engine. We also explore different execution plans for generating the content of an XML document. The results of an experimental study show that constructing XML documents inside the relational engine can have a significant performance benefit. Our results also show the superiority of having the relational engine use what we call an "outer union plan" to generate the content of an XML document.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1007/s007780100052</identifier>
		<title type="sharef:secondaryTitle">The International Journal on Very Large Data Bases</title>
		<number>2-3</number>
		<pages>133-154</pages>
		<title type="sharef:primaryTitle">Efficiently Publishing Relational Data as XML Documents</title>
		<identifier type="sharef:uri">http://www.springerlink.com/link.asp?id=jlcbfeaylabynt2w</identifier>
		<volume>10</volume>
	</reference>
	<reference name="gol06" src="bibtex:article" src-info="bibtex:line-1243" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Scott</givenname>
				<surname>Golder</surname>
			</person>
			<person>
				<givenname>Bernardo A.</givenname>
				<surname>Huberman</surname>
			</person>
		</names>
		<date value="2006"/>
		<abstract>
			<richtext>
				<p>Collaborative tagging describes the process by which many users add metadata in the form of keywords to shared content. Recently, collaborative tagging has grown in popularity on the web, on sites that allow users to tag bookmarks, photographs and other content. In this paper we analyze the structure of collaborative tagging systems as well as their dynamical aspects. Specifically, we discovered regularities in user activity, tag frequencies, kinds of tags used, bursts of popularity in bookmarking and a remarkable stability in the relative proportions of tags within a given URL. We also present a dynamical model of collaborative tagging that predicts these stable patterns and relates them to imitation and shared knowledge.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1177/0165551506062337</identifier>
		<title type="sharef:secondaryTitle">Journal of Information Science</title>
		<number>2</number>
		<pages>198-208</pages>
		<title type="sharef:primaryTitle">The Structure of Collaborative Tagging Systems</title>
		<identifier type="sharef:uri">http://www.hpl.hp.com/research/idl/papers/tags/</identifier>
		<identifier type="sharef:uri">http://jis.sagepub.com/cgi/content/abstract/32/2/198</identifier>
		<volume>32</volume>
	</reference>
	<reference name="che06" src="bibtex:article" src-info="bibtex:line-1257" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Mu-Yen</givenname>
				<surname>Chen</surname>
			</person>
			<person>
				<givenname>An-Pin</givenname>
				<surname>Chen</surname>
			</person>
		</names>
		<date value="2006"/>
		<abstract>
			<richtext>
				<p>In this paper, the development of knowledge management (KM) was surveyed, using a literature review and classification of articles from 1995 to 2004. With a keyword  index and article abstract, we explored how KM performance evaluation has developed during this period. Based on a scope of 108 articles from 80 academic KM journals (retrieved from six online databases), we surveyed and classified methods of KM measurement, using the following eight categories: qualitative analysis,  quantitative analysis, financial indicator analysis, non-financial indicator analysis, internal performance analysis, external performance analysis, project-orientated analysis and organization-orientated analysis, together with their measurement matrices for different research and problem domains. Future development directions for KM performance evaluation are presented in our discussion. They include: (1) KM performance measurements have tended towards expertise orientation, while evaluation development is a problem-orientated domain; (2) different  information technology methodologies, such as expert systems, knowledge-based systems and case-based reasoning may be able to evaluate KM as simply another  methodology; (3) the ability to continually change and obtain new understanding is the driving power behind KM methodologies, and should be the basis of KM performance evaluations in the future.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1177/0165551506059220</identifier>
		<title type="sharef:secondaryTitle">Journal of Information Science</title>
		<number>1</number>
		<pages>17-38</pages>
		<title type="sharef:primaryTitle">Knowledge Management Performance Evaluation: A Decade Review from 1995 to 2004</title>
		<identifier type="sharef:uri">http://jis.sagepub.com/cgi/content/abstract/32/1/17</identifier>
		<volume>32</volume>
	</reference>
	<reference name="buc92" src="bibtex:article" src-info="bibtex:line-1274" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Michael K.</givenname>
				<surname>Buckland</surname>
			</person>
		</names>
		<date value="1992-05"/>
		<abstract>
			<richtext>
				<p>Vannevar Bush's famous paper "As We May Think" (1945) described an imaginary information retrieval machine, the Memex. The Memex is usually viewed, unhistorically, in relation to subsequent developments using digital computers. This paper attempts to reconstruct the little-known background of information retrieval in and before 1939 when "As We May Think" was originally written. The Memex was based on Bush's work during 1938-1940 developing an improved photoelectric microfilm selector, an electronic retrieval technology pioneered by Emanuel Goldberg of Zeiss Ikon, Dresden, in the 1920s. Visionary statements by Paul Otlet (1934) and Walter Schuermeyer (1935) and the development of electronic document retrieval technology before Bush are examined.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1002/(SICI)1097-4571(199205)43:4&lt;284::AID-ASI3&gt;3.0.CO;2-0</identifier>
		<title type="sharef:secondaryTitle">Journal of The American Society for Information Science</title>
		<number>4</number>
		<pages>284-294</pages>
		<title type="sharef:primaryTitle">Emanuel Goldberg, Electronic Document Retrieval, and Vannevar Bush's Memex</title>
		<identifier type="sharef:uri" resourceType="text/html">http://people.ischool.berkeley.edu/~buckland/goldbush.html</identifier>
		<identifier type="sharef:uri">http://www3.interscience.wiley.com/journal/10049665/abstract</identifier>
		<volume>43</volume>
	</reference>
	<reference name="day01" src="bibtex:article" src-info="bibtex:line-1293" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Ronald E.</givenname>
				<surname>Day</surname>
			</person>
		</names>
		<date value="2001"/>
		<abstract>
			<richtext>
				<p>This article presents European documentalist, critical modernist, and Autonomous Marxist influenced post-Fordist views regarding the management of knowledge in mid- and late twentieth century Western modernity and postmodernity, and the complex theoretical and ideological debates, especially concerning issues of language and community. The introduction and use for corporate, governmental, and social purposes of powerful information and communication technologies created conceptual and political tensions and theoretical debates. In this article, knowledge management, including the specific recent approach known as "Knowledge Management", is discussed as a social, cultural, political, and organizational issue, including the problematic feasibility of capturing and representing knowledge that is "tacit," "invisible," and is imperfectly representable. "Social capital" and "affective labor" are discussed as elements of "tacit" knowledge. Views of writers in the European documentalist, critical modernist, and Italian Autonomous Marxist influenced post-Fordist traditions, such as Otlet, Briet, Heidegger, Benjamin, Marazzi, and Negri, are discussed.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1002/asi.1125</identifier>
		<title type="sharef:secondaryTitle">Journal of The American Society for Information Science and Technology</title>
		<number>9</number>
		<pages>725-735</pages>
		<title type="sharef:primaryTitle">Totality and Representation: A History of Knowledge Management Through European Documentation, Critical Modernity, and Post-Fordism</title>
		<identifier type="sharef:uri">http://www3.interscience.wiley.com/journal/81502346/abstract</identifier>
		<volume>52</volume>
	</reference>
	<reference name="bar02a" src="bibtex:article" src-info="bibtex:line-1306" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Judit</givenname>
				<surname>Bar-Ilan</surname>
			</person>
		</names>
		<date value="2002"/>
		<abstract>
			<richtext>
				<p>This study introduces methods for evaluating search engine performance over a time period. Several measures are defined, which as a whole describe search engine functionality over time. The necessary setup for such studies is described, and the use of these measures is illustrated through a specific example. The set of measures introduced here may serve as a guideline for the search engines for testing and improving their functionality. We recommend setting up a standard suite of measures for evaluating search engine performance.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1002/asi.10047</identifier>
		<title type="sharef:secondaryTitle">Journal of The American Society for Information Science and Technology</title>
		<number>4</number>
		<pages>308-319</pages>
		<title type="sharef:primaryTitle">Methods for Measuring Search Engine Performance over Time</title>
		<identifier type="sharef:uri" resourceType="text/html">http://www.asis.org/Publications/JASIS/vol53n04.html</identifier>
		<volume>53</volume>
	</reference>
	<reference name="wil00a" src="bibtex:article" src-info="bibtex:line-1319" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Robert</givenname>
				<surname>Wilensky</surname>
			</person>
		</names>
		<date value="2000"/>
		<identifier type="sharef:doi">10.1002/asi.10047</identifier>
		<title type="sharef:secondaryTitle">Journal of The American Society for Information Science and Technology</title>
		<number>3</number>
		<pages>228-245</pages>
		<title type="sharef:primaryTitle">Digital Library Resources as a Basis for Collaborative Work</title>
		<volume>51</volume>
	</reference>
	<reference name="met01" src="bibtex:article" src-info="bibtex:line-1334" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Wouter</givenname>
				<surname>Mettrop</surname>
			</person>
			<person>
				<givenname>Paul</givenname>
				<surname>Nieuwenhuysen</surname>
			</person>
		</names>
		<date value="2001-09"/>
		<identifier type="sharef:doi">10.1108/EUM0000000007096</identifier>
		<title type="sharef:secondaryTitle">Journal of Documentation</title>
		<number>5</number>
		<pages>623-651</pages>
		<title type="sharef:primaryTitle">Internet Search Engines — Fluctuations in Document Accessibility</title>
		<volume>57</volume>
	</reference>
	<reference name="bra08" src="bibtex:article" src-info="bibtex:line-1350" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Claus</givenname>
				<surname>Brabrand</surname>
			</person>
			<person>
				<givenname>Anders</givenname>
				<surname>Møller</surname>
			</person>
			<person>
				<givenname>Michael I.</givenname>
				<surname>Schwartzbach</surname>
			</person>
		</names>
		<date value="2008-06"/>
		<abstract>
			<richtext>
				<p>XML is successful as a machine processable data interchange format, but it is often too verbose for human use. For this reason, many XML languages permit an alternative more legible non-XML syntax. XSLT stylesheets are often used to convert from the XML syntax to the alternative syntax; however, such transformations are not reversible since no general tool exists to automatically parse the alternative syntax back into XML. We present XSugar, which makes it possible to manage dual syntax for XML languages. An XSugar specification is built around a context-free grammar that unifies the two syntaxes of a language. Given such a specification, the XSugar tool can translate from alternative syntax to XML and vice versa. Moreover, the tool statically checks that the transformations are reversible and that all XML documents generated from the alternative syntax are valid according to a given XML schema.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1016/j.is.2008.01.006</identifier>
		<title type="sharef:secondaryTitle">Information Systems</title>
		<number>4-5</number>
		<pages>385-406</pages>
		<title type="sharef:primaryTitle">Dual Syntax for XML Languages</title>
		<field type="bibtex:topic">xsugar[1]</field>
		<identifier type="sharef:uri" resourceType="application/pdf">http://www.brics.dk/~amoeller/papers/xsugar/journal.pdf</identifier>
		<volume>33</volume>
	</reference>
	<reference name="kno01b" src="bibtex:article" src-info="bibtex:line-1369" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Craig A.</givenname>
				<surname>Knoblock</surname>
			</person>
			<person>
				<givenname>Steven</givenname>
				<surname>Minton</surname>
			</person>
			<person>
				<givenname>José Luis</givenname>
				<surname>Ambite</surname>
			</person>
			<person>
				<givenname>Naveen</givenname>
				<surname>Ashish</surname>
			</person>
			<person>
				<givenname>Ion</givenname>
				<surname>Muslea</surname>
			</person>
			<person>
				<givenname>Andrew G.</givenname>
				<surname>Philpot</surname>
			</person>
			<person>
				<givenname>Sheila</givenname>
				<surname>Tejada</surname>
			</person>
		</names>
		<date value="2001-03"/>
		<title type="sharef:secondaryTitle">International Journal of Cooperative Information Systems</title>
		<number>1 &amp; 2</number>
		<pages>145-169</pages>
		<title type="sharef:primaryTitle">The Ariadne Approach to Web-based Information Integration</title>
		<field type="bibtex:topic">ariadne[1]</field>
		<identifier type="sharef:uri" resourceType="text/html">http://www.worldscinet.com/ijcis/10/1001_02/S0218843001000291.html</identifier>
		<identifier type="sharef:uri" resourceType="application/pdf">http://www.isi.edu/info-agents/papers/knoblock00-ijcis.pdf</identifier>
		<volume>10</volume>
	</reference>
	<reference name="ber01" src="bibtex:article" src-info="bibtex:line-1387" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Tim</givenname>
				<surname>Berners-Lee</surname>
			</person>
			<person>
				<givenname>James A.</givenname>
				<surname>Hendler</surname>
			</person>
			<person>
				<givenname>Ora</givenname>
				<surname>Lassila</surname>
			</person>
		</names>
		<date value="2001-05"/>
		<title type="sharef:secondaryTitle">Scientific American</title>
		<number>5</number>
		<pages>34-43</pages>
		<title type="sharef:primaryTitle">The Semantic Web</title>
		<identifier type="sharef:uri">http://www.sciam.com/article.cfm?id=the-semantic-web</identifier>
		<volume>284</volume>
	</reference>
	<reference name="lee10a" src="bibtex:article" src-info="bibtex:line-1399" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Tim</givenname>
				<surname>Berners-Lee</surname>
			</person>
		</names>
		<date value="2010-12"/>
		<abstract>
			<richtext>
				<p>The principle of universality allows the Web to work no matter what hardware, software, network connection or language you use and to handle information of all types and qualities. This principle guides Web technology design. Technical standards that are open and royalty-free allow people to create applications without anyone's permission or having to pay. Patents, and Web services that do not use the common URIs for addresses, limit innovation. Threats to the Internet, such as companies or governments that interfere with or snoop on Internet traffic, compromise basic human network rights. Web applications, linked data and other future Web technologies will flourish only if we protect the medium's basic principles.</p>
			</richtext>
		</abstract>
		<title type="sharef:secondaryTitle">Scientific American</title>
		<number>12</number>
		<title type="sharef:primaryTitle">Long Live the Web</title>
		<identifier type="sharef:uri">http://www.scientificamerican.com/article.cfm?id=long-live-the-web</identifier>
	</reference>
	<reference name="boj08" src="bibtex:article" src-info="bibtex:line-1414" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Uldis</givenname>
				<surname>Bojārs</surname>
			</person>
			<person>
				<givenname>John G.</givenname>
				<surname>Breslin</surname>
			</person>
			<person>
				<givenname>Vassilios</givenname>
				<surname>Peristeras</surname>
			</person>
			<person>
				<givenname>Giovanni</givenname>
				<surname>Tummarello</surname>
			</person>
			<person>
				<givenname>Stefan</givenname>
				<surname>Decker</surname>
			</person>
		</names>
		<date value="2008-05"/>
		<abstract>
			<richtext>
				<p>One of the most visible trends on the Web is the emergence of Social Web sites, which help people create and gather knowledge by simplifying user contributions via blogs, tagging and folksonomies, wikis, podcasts, and online social networks. Current online-community sites are isolated from one another, like islands in a sea. Various discussions might contain complementary knowledge and discussion — parts of the answer a person is looking for — but people participating in one discussion can't readily access information about related discussions elsewhere. The potential synergies among many sites, communities, and services are expensive to exploit, and their data are difficult and cumbersome to link and reuse. The main reason for this lack of interoperation is that for the most part in the Social Web, common standards still don't exist for knowledge and information exchange and interoperation. However, the Semantic Web effort aims to provide the tools needed to define extensible, flexible standards for this purpose. The Semantic Web technology stack is well defined, enabling the creation of metadata and associated vocabularies. The Semantic Web effort is in an ideal position to make Social Web sites interoperable. Applying Semantic Web frameworks including SIOC (Semantically Interlinked Online Communities) and FOAF (Friend-of-a-Friend) to the Social Web can lead to a Social Semantic Web, creating a network of interlinked and semantically rich knowledge. This article is part of a special issue called Semantic Web Update.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1109/MIS.2008.50</identifier>
		<title type="sharef:secondaryTitle">IEEE Intelligent Systems</title>
		<number>3</number>
		<pages>29-40</pages>
		<title type="sharef:primaryTitle">Interlinking the Social Web with Semantics</title>
		<identifier type="sharef:uri">http://www.computer.org/portal/web/csdl/doi/10.1109/mis.2008.50</identifier>
		<volume>23</volume>
	</reference>
	<reference name="ber06b" src="bibtex:article" src-info="bibtex:line-1428" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Nigel</givenname>
				<surname>Shadbolt</surname>
			</person>
			<person>
				<givenname>Tim</givenname>
				<surname>Berners-Lee</surname>
			</person>
			<person>
				<givenname>Wendy</givenname>
				<surname>Hall</surname>
			</person>
		</names>
		<date value="2006-03"/>
		<abstract>
			<richtext>
				<p>The original Scientific American article on the Semantic Web appeared in 2001. It described the evolution of a Web that consisted largely of documents for humans to read to one that included data and information for computers to manipulate. The Semantic Web is a Web of actionable information — information derived from data through a semantic theory for interpreting the symbols. This simple idea, however, remains largely unrealized. Shopbots and auction bots abound on the Web, but these are essentially handcrafted for particular tasks; they have little ability to interact with heterogeneous data and information types. Because we haven't yet delivered large-scale, agent-based mediation, some commentators argue that the Semantic Web has failed to deliver. We argue that agents can only flourish when standards are well established and that the Web standards for expressing shared meaning have progressed steadily over the past five years. Furthermore, we see the use of ontologies in the e-science community presaging ultimate success for the Semantic Web — just as the use of HTTP within the CERN particle physics community led to the revolutionary success of the original Web. This article is part of a special issue on the Future of AI.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1109/MIS.2006.62</identifier>
		<title type="sharef:secondaryTitle">IEEE Intelligent Systems</title>
		<number>3</number>
		<pages>96-101</pages>
		<title type="sharef:primaryTitle">The Semantic Web Revisited</title>
		<volume>21</volume>
	</reference>
	<reference name="bou03" src="bibtex:article" src-info="bibtex:line-1445" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Niels Olof</givenname>
				<surname>Bouvin</surname>
			</person>
			<person>
				<givenname>Bent Guldbjerg</givenname>
				<surname>Christensen</surname>
			</person>
			<person>
				<givenname>Kaj</givenname>
				<surname>Grønbæk</surname>
			</person>
			<person>
				<givenname>Frank Allan</givenname>
				<surname>Hansen</surname>
			</person>
		</names>
		<date value="2003-01"/>
		<abstract>
			<richtext>
				<p>This paper introduces the notion of context-aware mobile hypermedia. Context awareness means to take the users' context such as location, time, objective, community relations, etc., into account when browsing, searching, annotating, and linking. Attributes constituting the context of the user may be sensed automatically and/or be provided by the user directly. When mobile, the user may obtain context-aware hypermedia support on a variety of small and medium sized computing platforms such as mobile phones, PDAs, tablet PCs, and laptops. This paper introduces the HyCon (HyperContext) framework with an architecture for context-aware hypermedia. The architecture includes interfaces for a sensor tier encapsulating relevant sensors and represents the hypermedia objects in structures based on the XLink and RDF standards. A prototype called the HyConExplorer created with the framework is presented, and it is illustrated how the classical hypermedia features such as browsing, searching, annotating, linking, and collaboration are supported in context-aware hypermedia. Among the features of the HyConExplorer are real-time location-based searches via Google collecting hits within a specified nimbus around the user's GPS position. Finally, the use of scenarios for and evaluation of the use of the HyConExplorer in public school projects are discussed.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1080/13614560410001725310</identifier>
		<title type="sharef:secondaryTitle">The New Review of Hypermedia and Multimedia</title>
		<number>1</number>
		<pages>59-88</pages>
		<title type="sharef:primaryTitle">HyCon: A Framework for Context-Aware Mobile Hypermedia</title>
		<field type="bibtex:topic">hycon[1]</field>
		<identifier type="sharef:uri" resourceType="application/pdf">http://www.daimi.au.dk/~bentor/papers/NRHM9-Hycon.pdf</identifier>
		<volume>9</volume>
	</reference>
	<reference name="sha48" src="bibtex:article" src-info="bibtex:line-1464" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Claude Elwood</givenname>
				<surname>Shannon</surname>
			</person>
		</names>
		<date value="1948"/>
		<title type="sharef:secondaryTitle">Bell System Technical Journal</title>
		<pages>379-423, 623-656</pages>
		<title type="sharef:primaryTitle">A Mathematical Theory of Communication</title>
		<identifier type="sharef:uri" resourceType="text/html">http://cm.bell-labs.com/cm/ms/what/shannonday/paper.html</identifier>
		<volume>27</volume>
	</reference>
	<reference name="huf52" src="bibtex:article" src-info="bibtex:line-1478" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>David A.</givenname>
				<surname>Huffman</surname>
			</person>
		</names>
		<date value="1952-09"/>
		<title type="sharef:secondaryTitle">Institute of Radio Engineers</title>
		<number>9</number>
		<pages>1098-1101</pages>
		<title type="sharef:primaryTitle">A Method for the Construction of Minimum-Redundancy Codes</title>
		<identifier type="sharef:uri" resourceType="application/pdf">http://compression.graphicon.ru/download/articles/huff/huffman_1952_minimum-redundancy-codes.pdf</identifier>
		<volume>40</volume>
	</reference>
	<reference name="mil56" src="bibtex:article" src-info="bibtex:line-1494" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>George A.</givenname>
				<surname>Miller</surname>
			</person>
		</names>
		<date value="1956-03"/>
		<field type="bibtex:index">usability</field>
		<title type="sharef:secondaryTitle">The Psychological Review</title>
		<number>2</number>
		<pages>81-97</pages>
		<title type="sharef:primaryTitle">The Magical Number Seven, Plus or Minus Two: Some Limits on Our Capacity for Processing Information</title>
		<identifier type="sharef:uri" resourceType="text/html">http://www.well.com/user/smalin/miller.html</identifier>
		<volume>63</volume>
	</reference>
	<reference name="bee93" src="bibtex:article" src-info="bibtex:line-1511" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Nelson F. H.</givenname>
				<surname>Beebe</surname>
			</person>
		</names>
		<date value="1993-12"/>
		<title type="sharef:secondaryTitle">TUGboat</title>
		<number>4</number>
		<pages>395-419</pages>
		<title type="sharef:primaryTitle">Bibliography Prettyprinting and Syntax Checking</title>
		<field type="bibtex:topic">bibtex[0.9]</field>
		<identifier type="sharef:uri" resourceType="application/pdf">http://www.math.utah.edu/~beebe/publications/1993/tugboat-14-4-395-dec-1993.pdf</identifier>
		<volume>14</volume>
	</reference>
	<reference name="rat00" src="bibtex:article" src-info="bibtex:line-1528" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Hans Holger</givenname>
				<surname>Rath</surname>
			</person>
		</names>
		<date value="2000"/>
		<title type="sharef:secondaryTitle">Markup Languages: Theory &amp; Practice</title>
		<number>1</number>
		<pages>45-64</pages>
		<title type="sharef:primaryTitle">Topic Maps: Templates, Topology, and Type Hierarchies</title>
		<field type="bibtex:topic">topicmaps[0.8]</field>
		<volume>2</volume>
	</reference>
	<reference name="riz01b" src="bibtex:article" src-info="bibtex:line-1539" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Romeo</givenname>
				<surname>Rizzi</surname>
			</person>
		</names>
		<date value="2001-12"/>
		<abstract>
			<richtext>
				<p>The Standard Generalized Markup Language (SGML) and the Extensible Markup Language (XML) allow authors to better transmit the semantics in their documents by explicitly specifying the relevant structures in a document or class of documents by means of document type definitions (DTDs). Several authors have proposed to regard DTDs as extended context-free grammars expressed in a notation similar to extended Backus-Naur form. In addition, the SGML standard allows the semantics of content models (the right-hand side of productions) to be modified by 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. Since XML does not allow exceptions, the problem of exception removal has received much interest recently. Motivated by this, Kilpeläinen and Wood have proved that exceptions do not increase the expressive power of extended context-free grammars and that for each DTD with exceptions, we can obtain a structurally equivalent extended context-free grammar. Since their argument was based on an exponential simulation, they also conjectured that an exponential blow-up in the size of the grammar is a necessary devil when purging exceptions away. We prove their conjecture under the most realistic assumption that NP-complete problems do not admit non-uniform polynomial-time algorithms. Kilpeläinen and Wood also asked whether the parsing problem for extended context-free grammars with exceptions admits efficient algorithmic solution. We show the NP-completeness of the very basic problem: given a string w and a context-free grammar G (not even extended) with exclusion exceptions (no inclusion exceptions needed), decide whether w belongs to the language generated by G. Our results and arguments point up the limitations of using extended context-free grammars as a model of SGML, especially when one is interested in understanding issues related to exceptions.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1162/109966201753537222</identifier>
		<title type="sharef:secondaryTitle">Markup Languages: Theory &amp; Practice</title>
		<number>1</number>
		<pages>107-116</pages>
		<title type="sharef:primaryTitle">Complexity of Context-free Grammars with Exceptions and the Inadequacy of Grammars as Models for XML and SGML</title>
		<field type="bibtex:topic">sgml[0.8] xml[0.8]</field>
		<field type="bibtex:updates">riz01a</field>
		<identifier type="sharef:uri">http://www.ingentaconnect.com/content/mitpress/mlang/2001/00000003/00000001/art00011</identifier>
		<volume>3</volume>
	</reference>
	<reference name="kim00" src="bibtex:article" src-info="bibtex:line-1555" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>W. Eliot</givenname>
				<surname>Kimber</surname>
			</person>
			<person>
				<givenname>John</givenname>
				<surname>Heintz</surname>
			</person>
		</names>
		<date value="2000"/>
		<title type="sharef:secondaryTitle">Markup Languages: Theory &amp; Practice</title>
		<number>3</number>
		<pages>295-320</pages>
		<title type="sharef:primaryTitle">Using UML to Define XML Document Types</title>
		<field type="bibtex:topic">uml[0.8] xml[0.8] dtd[0.8]</field>
		<identifier type="sharef:uri" resourceType="application/pdf">http://www.vico.org/aRecursosHealth/UsingUMLtodefXML.pdf</identifier>
		<volume>2</volume>
	</reference>
	<reference name="vor00" src="bibtex:article" src-info="bibtex:line-1567" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Scott</givenname>
				<surname>Vorthmann</surname>
			</person>
			<person>
				<givenname>Jonathan</givenname>
				<surname>Robie</surname>
			</person>
		</names>
		<date value="2000"/>
		<title type="sharef:secondaryTitle">Markup Languages: Theory &amp; Practice</title>
		<number>3</number>
		<pages>281-294</pages>
		<title type="sharef:primaryTitle">Beyond Schemas</title>
		<field type="bibtex:topic">saf[0.8]</field>
		<volume>2</volume>
	</reference>
	<reference name="hay95" src="bibtex:article" src-info="bibtex:line-1582" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Brian</givenname>
				<surname>Hayes</surname>
			</person>
		</names>
		<date value="1995-11"/>
		<title type="sharef:secondaryTitle">American Scientist</title>
		<number>6</number>
		<pages>504-509</pages>
		<title type="sharef:primaryTitle">Pleasures of Plication</title>
		<identifier type="sharef:uri" resourceType="text/html">http://www.sigmaxi.org/amsci/issues/comsci95/compsci95-11.html</identifier>
		<volume>83</volume>
	</reference>
	<reference name="hay05" src="bibtex:article" src-info="bibtex:line-1594" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Brian</givenname>
				<surname>Hayes</surname>
			</person>
		</names>
		<date value="2005-01"/>
		<title type="sharef:secondaryTitle">American Scientist</title>
		<number>1</number>
		<title type="sharef:primaryTitle">Naming Names</title>
		<identifier type="sharef:uri">http://www.americanscientist.org/issues/pub/naming-names</identifier>
		<volume>93</volume>
	</reference>
	<reference name="bie97" src="bibtex:article" src-info="bibtex:line-1609" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Michael</givenname>
				<surname>Bieber</surname>
			</person>
			<person>
				<givenname>Fabio</givenname>
				<surname>Vitali</surname>
			</person>
			<person>
				<givenname>Helen</givenname>
				<surname>Ashman</surname>
			</person>
			<person>
				<givenname>V.</givenname>
				<surname>Balasubramanian</surname>
			</person>
			<person>
				<givenname>Harri</givenname>
				<surname>Oinas-Kukkonen</surname>
			</person>
		</names>
		<date value="1997-07"/>
		<abstract>
			<richtext>
				<p>World Wide Web authors must cope in a hypermedia environment analogous to second-generation computing languages, building and managing most hypermedia links using simple anchors and single-step navigation. Following this analogy, sophisticated application environments on the World Wide Web will require third- and fourth-generation hypermedia features. Implementing third- and fourth-generation hypermedia involves designing both high-level hypermedia features and the high-level authoring environments system developers build for authors to specify them. We present a set of high-level hypermedia features including typed nodes and links, link attributes, structure-based query, transclusions, warm and hot links, private and public links, hypermedia access permissions, computed personalized links, external link databases, link update mechanisms, overviews, trails, guided tours, backtracking, and history-based navigation. We ground our discussion in the hypermedia research literature, and illustrate each feature both from existing implementations and a running scenario. We also give some direction for implementing these on the World Wide Web and in other information systems.</p>
			</richtext>
		</abstract>
		<title type="sharef:secondaryTitle">International Journal of Human Computer Studies</title>
		<number>1</number>
		<pages>31-65</pages>
		<title type="sharef:primaryTitle">Fourth Generation Hypermedia: Some Missing Links for the World Wide Web</title>
		<field type="bibtex:topic">www[0.8]</field>
		<identifier type="sharef:uri" resourceType="text/html">http://ijhcs.open.ac.uk/bieber/bieber.html</identifier>
		<volume>47</volume>
	</reference>
	<reference name="wil00d" src="bibtex:article" src-info="bibtex:line-1627" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Erik</givenname>
				<surname>Wilde</surname>
			</person>
		</names>
		<date value="2000-02-08"/>
		<title type="sharef:secondaryTitle">Neue Zürcher Zeitung</title>
		<title type="sharef:primaryTitle">Hypermedia-Möglichkeiten des WWW — Neue Perspektiven, aber auch neue Probleme</title>
		<identifier type="sharef:uri">http://dret.net/netdret/publications#wil00d</identifier>
		<volume>221</volume>
	</reference>
	<reference name="boy04" src="bibtex:article" src-info="bibtex:line-1642" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Robert S.</givenname>
				<surname>Boynton</surname>
			</person>
		</names>
		<date value="2004-01-05"/>
		<title type="sharef:secondaryTitle">New York Times Magazine</title>
		<title type="sharef:primaryTitle">The Tyranny of Copyright?</title>
		<identifier type="sharef:uri" resourceType="text/html">http://www.nytimes.com/2004/01/25/magazine/25COPYRIGHT.html</identifier>
	</reference>
	<reference name="wil00e" src="bibtex:article" src-info="bibtex:line-1656" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Erik</givenname>
				<surname>Wilde</surname>
			</person>
		</names>
		<date value="2000-02-05"/>
		<title type="sharef:secondaryTitle">Australian IT</title>
		<title type="sharef:primaryTitle">XML: It's only the beginning</title>
		<identifier type="sharef:uri">http://dret.net/netdret/publications#wil00e</identifier>
	</reference>
	<reference name="moo65" src="bibtex:article" src-info="bibtex:line-1670" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Gordon E.</givenname>
				<surname>Moore</surname>
			</person>
		</names>
		<date value="1965-04-09"/>
		<abstract>
			<richtext>
				<p>With unit cost falling as the number of components per circuit rises, by 1975 economics may dictate squeezing as many as 65'000 components on a single silicon chip</p>
			</richtext>
		</abstract>
		<title type="sharef:secondaryTitle">Electronics</title>
		<number>8</number>
		<title type="sharef:primaryTitle">Cramming more Components onto Integrated Circuits</title>
		<identifier type="sharef:uri" resourceType="application/pdf">http://download.intel.com/research/silicon/moorespaper.pdf</identifier>
		<volume>38</volume>
	</reference>
	<reference name="rei09b" src="bibtex:article" src-info="bibtex:line-1687" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Charles</givenname>
				<surname>Reis</surname>
			</person>
			<person>
				<givenname>Adam</givenname>
				<surname>Barth</surname>
			</person>
			<person>
				<givenname>Carlos</givenname>
				<surname>Pizano</surname>
			</person>
		</names>
		<date value="2009-06"/>
		<abstract>
			<richtext>
				<p>Google Chrome developers focused on three key problems to shield the browser from attacks.</p>
			</richtext>
		</abstract>
		<title type="sharef:secondaryTitle">ACM Queue</title>
		<number>5</number>
		<title type="sharef:primaryTitle">Browser Security: Lessons from Google Chrome</title>
		<identifier type="sharef:uri">http://queue.acm.org/detail.cfm?id=1556050</identifier>
		<volume>7</volume>
	</reference>
	<reference name="wad09" src="bibtex:article" src-info="bibtex:line-1699" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Thomas</givenname>
				<surname>Wadlow</surname>
			</person>
			<person>
				<givenname>Vlad</givenname>
				<surname>Gorelik</surname>
			</person>
		</names>
		<date value="2009-02"/>
		<abstract>
			<richtext>
				<p>Web browsers leave users vulnerable to an ever-growing number of attacks. Can we make them secure while preserving their usability?</p>
			</richtext>
		</abstract>
		<title type="sharef:secondaryTitle">ACM Queue</title>
		<number>2</number>
		<title type="sharef:primaryTitle">Security in the Browser</title>
		<identifier type="sharef:uri">http://queue.acm.org/detail.cfm?id=1516164</identifier>
		<volume>7</volume>
	</reference>
	<reference name="hyd09" src="bibtex:article" src-info="bibtex:line-1711" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Julian</givenname>
				<surname>Hyde</surname>
			</person>
		</names>
		<date value="2009-12"/>
		<abstract>
			<richtext>
				<p>Web applications produce data at colossal rates, and those rates compound every year as the Web becomes more central to our lives. Other data sources such as environmental monitoring and location-based services are a rapidly expanding part of our day-to-day experience. Even as throughput is increasing, users and business owners expect to see their data with ever-decreasing latency. Advances in computer hardware (cheaper memory, cheaper disks, and more processing cores) are helping somewhat, but not enough to keep pace with the twin demands of rising throughput and decreasing latency.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/1661785.1667562</identifier>
		<title type="sharef:secondaryTitle">ACM Queue</title>
		<number>11</number>
		<title type="sharef:primaryTitle">Data in Flight</title>
		<identifier type="sharef:uri">http://queue.acm.org/detail.cfm?id=1667562</identifier>
		<volume>7</volume>
	</reference>
	<reference name="wil08b" src="bibtex:article" src-info="bibtex:line-1724" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Erik</givenname>
				<surname>Wilde</surname>
			</person>
			<person>
				<givenname>Robert J.</givenname>
				<surname>Glushko</surname>
			</person>
		</names>
		<date value="2008-10"/>
		<abstract>
			<richtext>
				<p>The Extensible Markup Language (XML), which just celebrated its 10th birthday, is one of the big success stories of the Web. Apart from basic Web technologies (URIs, HTTP, and HTML) and the advanced scripting driving the Web 2.0 wave, XML is by far the most successful and ubiquitous Web technology. With great power, however, comes great responsibility, so while XML's success is well earned as the first truly universal standard for structured data, it must now deal with numerous problems that have grown up around it. These are not entirely the fault of XML itself, but instead can be attributed to exaggerated claims and ideas of what XML is and what it can do.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/1466443.1466454</identifier>
		<title type="sharef:secondaryTitle">ACM Queue</title>
		<number>6</number>
		<pages>46-53</pages>
		<title type="sharef:primaryTitle">XML Fever</title>
		<identifier type="sharef:uri">http://dret.net/netdret/publications#wil08b</identifier>
		<volume>6</volume>
	</reference>
	<reference name="wil08c" src="bibtex:article" src-info="bibtex:line-1738" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Robert J.</givenname>
				<surname>Glushko</surname>
			</person>
			<person>
				<givenname>Erik</givenname>
				<surname>Wilde</surname>
			</person>
		</names>
		<date value="2008"/>
		<title type="sharef:secondaryTitle">ACM Queue</title>
		<number>6</number>
		<title type="sharef:primaryTitle">Document Design Matters</title>
		<identifier type="sharef:uri">http://dret.net/netdret/publications#wil08c</identifier>
		<identifier type="sharef:uri">http://queue.acm.org/detail.cfm?id=1400195</identifier>
		<volume>6</volume>
	</reference>
	<reference name="hen06" src="bibtex:article" src-info="bibtex:line-1749" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Michi</givenname>
				<surname>Henning</surname>
			</person>
		</names>
		<date value="2006-06"/>
		<abstract>
			<richtext>
				<p>Over the span of a few years, CORBA moved from being a successful middleware that was hailed as the Internet's next-generation e-commerce infrastructure to being an obscure niche technology that is all but forgotten. This rapid decline is surprising. How can a technology that was produced by the world's largest software consortium fall from grace so quickly? Many of the reasons are technical: poor architecture, complex APIs, and lack of essential features all contributed to CORBA's downfall. However, such technical shortcomings are a symptom rather than a cause. Ultimately, CORBA failed because its standardization process virtually guarantees poor technical quality. Seeing that other standards consortia use a process that is very similar, this does not bode well for the viability of other technologies produced in this fashion.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/1142031.1142044</identifier>
		<title type="sharef:secondaryTitle">ACM Queue</title>
		<number>5</number>
		<pages>28-34</pages>
		<title type="sharef:primaryTitle">The Rise and Fall of CORBA</title>
		<field type="bibtex:topic">corba[0.9]</field>
		<identifier type="sharef:uri" resourceType="application/pdf">http://www.zeroc.com/documents/riseAndFallOfCorba.pdf</identifier>
		<volume>4</volume>
	</reference>
	<reference name="hen07" src="bibtex:article" src-info="bibtex:line-1764" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Michi</givenname>
				<surname>Henning</surname>
			</person>
		</names>
		<date value="2007-05"/>
		<identifier type="sharef:doi">10.1145/1255421.1255422</identifier>
		<title type="sharef:secondaryTitle">ACM Queue</title>
		<number>4</number>
		<pages>24-36</pages>
		<title type="sharef:primaryTitle">API Design Matters</title>
		<identifier type="sharef:uri" resourceType="application/pdf">http://www.zeroc.com/documents/APIDesign.pdf</identifier>
		<volume>5</volume>
	</reference>
	<reference name="bel04" src="bibtex:article" src-info="bibtex:line-1777" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Alex E.</givenname>
				<surname>Bell</surname>
			</person>
		</names>
		<date value="2004-03"/>
		<identifier type="sharef:doi">10.1145/984458.984495</identifier>
		<title type="sharef:secondaryTitle">ACM Queue</title>
		<number>1</number>
		<pages>72-80</pages>
		<title type="sharef:primaryTitle">Death by UML Fever</title>
		<field type="bibtex:topic">uml[0.9]</field>
		<volume>2</volume>
	</reference>
	<reference name="bel07" src="bibtex:article" src-info="bibtex:line-1790" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Alex E.</givenname>
				<surname>Bell</surname>
			</person>
		</names>
		<date value="2007-02"/>
		<identifier type="sharef:doi">10.1145/1217256.1217275</identifier>
		<title type="sharef:secondaryTitle">ACM Queue</title>
		<number>1</number>
		<pages>54-56</pages>
		<title type="sharef:primaryTitle">DOA with SOA</title>
		<field type="bibtex:topic">soa[0.9]</field>
		<identifier type="sharef:uri">http://www.acmqueue.org/modules.php?name=Content&amp;pa=showpage&amp;pid=464</identifier>
		<volume>5</volume>
	</reference>
	<reference name="glu61" src="bibtex:article" src-info="bibtex:line-1808" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Victor M.</givenname>
				<surname>Glushkov</surname>
			</person>
		</names>
		<date value="1961"/>
		<title type="sharef:secondaryTitle">Russian Mathematical Surveys</title>
		<number>5</number>
		<pages>1-53</pages>
		<title type="sharef:primaryTitle">The Abstract Theory of Automata</title>
		<identifier type="sharef:uri">http://www.turpion.org/php/paper.phtml?journal_id=rm&amp;paper_id=4112</identifier>
		<volume>16</volume>
	</reference>
	<reference name="can00" src="bibtex:article" src-info="bibtex:line-1823" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>José H.</givenname>
				<surname>Canós</surname>
			</person>
		</names>
		<date value="2000">Summer 2000</date>
		<title type="sharef:secondaryTitle">ACM Crossroads</title>
		<number>4</number>
		<title type="sharef:primaryTitle">A Bibliography Manager for Microsoft Word</title>
		<field type="bibtex:topic">bibword[0.9]</field>
		<identifier type="sharef:uri" resourceType="text/html">http://www.acm.org/crossroads/xrds6-4/bibword.html</identifier>
		<volume>6</volume>
	</reference>
	<reference name="sah00" src="bibtex:article" src-info="bibtex:line-1835" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Subhasis</givenname>
				<surname>Saha</surname>
			</person>
		</names>
		<date value="2000">Spring 2000</date>
		<title type="sharef:secondaryTitle">ACM Crossroads</title>
		<number>3</number>
		<title type="sharef:primaryTitle">Image Compression — From DCT to Wavelets: A Review</title>
		<field type="bibtex:topic">dct[0.8] wavelet[0.8]</field>
		<identifier type="sharef:uri" resourceType="text/html">http://www.acm.org/crossroads/xrds6-3/sahaimgcoding.html</identifier>
		<volume>6</volume>
	</reference>
	<reference name="duc02" src="bibtex:article" src-info="bibtex:line-1851" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Bob</givenname>
				<surname>DuCharme</surname>
			</person>
		</names>
		<date value="2002-03"/>
		<title type="sharef:secondaryTitle">xml.com</title>
		<title type="sharef:primaryTitle">XLink: Who Cares?</title>
		<field type="bibtex:topic">xlink[0.7]</field>
		<identifier type="sharef:uri" resourceType="text/html">http://www.xml.com/pub/a/2002/03/13/xlink.html</identifier>
	</reference>
	<reference name="sob06" src="bibtex:article" src-info="bibtex:line-1861" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Paul</givenname>
				<surname>Sobocinski</surname>
			</person>
		</names>
		<date value="2006-11"/>
		<title type="sharef:secondaryTitle">xml.com</title>
		<title type="sharef:primaryTitle">Migrating to XForms</title>
		<field type="bibtex:topic">xforms[0.7]</field>
		<identifier type="sharef:uri" resourceType="text/html">http://www.xml.com/pub/a/2006/11/01/migrating-to-xforms-php.html</identifier>
	</reference>
	<reference name="kle06" src="bibtex:article" src-info="bibtex:line-1871" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Paul</givenname>
				<surname>Kiel</surname>
			</person>
		</names>
		<date value="2006-09"/>
		<abstract>
			<richtext>
				<p>XML Schema is now 5 years old, having matured from a newborn into an active youngster. So what have we learned about this young one's personality? We've always known it was complex. Indeed, the original debate about whether to make it a Recommendation indicated concern. (See Last Word and Questionnaire.) This rich toolset has caused schema designers to wonder which features they should or should not use. If we analyze what people are actually implementing, perhaps we can glean some guidance. I decided to embark on a quest to see if we can put together a profile of XML Schema based on experiences thus far.</p>
			</richtext>
		</abstract>
		<title type="sharef:secondaryTitle">xml.com</title>
		<title type="sharef:primaryTitle">Profiling XML Schema</title>
		<field type="bibtex:topic">xsd[0.8]</field>
		<identifier type="sharef:uri" resourceType="text/html">http://www.xml.com/pub/a/2006/09/20/profiling-xml-schema.html</identifier>
	</reference>
	<reference name="ham02" src="bibtex:article" src-info="bibtex:line-1882" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Kip</givenname>
				<surname>Hampton</surname>
			</person>
		</names>
		<date value="2002-07"/>
		<title type="sharef:secondaryTitle">xml.com</title>
		<title type="sharef:primaryTitle">XSH, An XML Editing Shell</title>
		<field type="bibtex:topic">xsh[0.9]</field>
		<identifier type="sharef:uri" resourceType="text/html">http://www.xml.com/pub/a/2002/07/10/kip.html</identifier>
	</reference>
	<reference name="dum04" src="bibtex:article" src-info="bibtex:line-1892" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Edd</givenname>
				<surname>Dumbill</surname>
			</person>
		</names>
		<date value="2004-11"/>
		<title type="sharef:secondaryTitle">xml.com</title>
		<title type="sharef:primaryTitle">How Do I Hate Thee?</title>
		<field type="bibtex:topic">xml[0.7]</field>
		<identifier type="sharef:uri" resourceType="text/html">http://www.xml.com/pub/a/2004/11/03/deviant.html</identifier>
	</reference>
	<reference name="pil04b" src="bibtex:article" src-info="bibtex:line-1902" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Mark</givenname>
				<surname>Pilgrim</surname>
			</person>
		</names>
		<date value="2004-08"/>
		<title type="sharef:secondaryTitle">xml.com</title>
		<title type="sharef:primaryTitle">Identifying Atom</title>
		<field type="bibtex:topic">atom[0.8] uri[0.7]</field>
		<identifier type="sharef:uri" resourceType="text/html">http://www.xml.com/pub/a/2004/08/18/pilgrim.html</identifier>
	</reference>
	<reference name="pil04a" src="bibtex:article" src-info="bibtex:line-1912" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Mark</givenname>
				<surname>Pilgrim</surname>
			</person>
		</names>
		<date value="2004-07"/>
		<title type="sharef:secondaryTitle">xml.com</title>
		<title type="sharef:primaryTitle">XML on the Web Has Failed</title>
		<field type="bibtex:topic">xml[0.8] http[0.8]</field>
		<identifier type="sharef:uri" resourceType="text/html">http://www.xml.com/pub/a/2004/07/21/dive.html</identifier>
	</reference>
	<reference name="pil03" src="bibtex:article" src-info="bibtex:line-1922" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Mark</givenname>
				<surname>Pilgrim</surname>
			</person>
		</names>
		<date value="2003-01"/>
		<title type="sharef:secondaryTitle">xml.com</title>
		<title type="sharef:primaryTitle">Parsing RSS At All Costs</title>
		<field type="bibtex:topic">rss[0.8]</field>
		<identifier type="sharef:uri" resourceType="text/html">http://www.xml.com/pub/a/2003/01/22/dive-into-xml.html</identifier>
	</reference>
	<reference name="pil02" src="bibtex:article" src-info="bibtex:line-1932" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Mark</givenname>
				<surname>Pilgrim</surname>
			</person>
		</names>
		<date value="2002-12"/>
		<title type="sharef:secondaryTitle">xml.com</title>
		<title type="sharef:primaryTitle">What is RSS?</title>
		<field type="bibtex:topic">rss[0.8]</field>
		<identifier type="sharef:uri" resourceType="text/html">http://www.xml.com/pub/a/2002/12/18/dive-into-xml.html</identifier>
	</reference>
	<reference name="dod01" src="bibtex:article" src-info="bibtex:line-1942" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Leigh</givenname>
				<surname>Dodds</surname>
			</person>
		</names>
		<date value="2001-02"/>
		<title type="sharef:secondaryTitle">xml.com</title>
		<title type="sharef:primaryTitle">Answering the Namespace Riddle: An Introduction to the Resource Directory Description Language</title>
		<field type="bibtex:topic">rddl[0.8]</field>
		<identifier type="sharef:uri" resourceType="text/html">http://www.xml.com/pub/a/2001/02/28/rddl.html</identifier>
	</reference>
	<reference name="rob03" src="bibtex:article" src-info="bibtex:line-1952" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Edvard</givenname>
				<surname>Robertsson</surname>
			</person>
		</names>
		<date value="2003-11"/>
		<title type="sharef:secondaryTitle">xml.com</title>
		<title type="sharef:primaryTitle">An Introduction to Schematron</title>
		<field type="bibtex:topic">schematron[0.8]</field>
		<identifier type="sharef:uri" resourceType="text/html">http://www.xml.com/pub/a/2003/11/12/schematron.html</identifier>
	</reference>
	<reference name="rob04" src="bibtex:article" src-info="bibtex:line-1962" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Edvard</givenname>
				<surname>Robertsson</surname>
			</person>
		</names>
		<date value="2004-02"/>
		<title type="sharef:secondaryTitle">xml.com</title>
		<title type="sharef:primaryTitle">Combining RELAX NG and Schematron</title>
		<field type="bibtex:topic">schematron[0.8] relaxng[0.8]</field>
		<identifier type="sharef:uri" resourceType="text/html">http://www.xml.com/pub/a/2004/02/11/relaxtron.html</identifier>
	</reference>
	<reference name="sid02" src="bibtex:article" src-info="bibtex:line-1972" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Bilal</givenname>
				<surname>Siddiqui</surname>
			</person>
		</names>
		<date value="2002-09"/>
		<title type="sharef:secondaryTitle">xml.com</title>
		<title type="sharef:primaryTitle">XML Canonicalization</title>
		<field type="bibtex:topic">canonicalxml[0.8]</field>
		<identifier type="sharef:uri" resourceType="text/html">http://webservices.xml.com/pub/a/ws/2002/09/18/c14n.html</identifier>
	</reference>
	<reference name="bra98" src="bibtex:article" src-info="bibtex:line-1982" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Tim</givenname>
				<surname>Bray</surname>
			</person>
		</names>
		<date value="1998-09"/>
		<title type="sharef:secondaryTitle">xml.com</title>
		<title type="sharef:primaryTitle">Building the Annotated XML Specification</title>
		<field type="bibtex:topic">xml[0.9]</field>
		<identifier type="sharef:uri" resourceType="text/html">http://www.xml.com/pub/a/98/09/exexegesis-0.html</identifier>
	</reference>
	<reference name="sal02" src="bibtex:article" src-info="bibtex:line-1992" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Richard</givenname>
				<surname>Salz</surname>
			</person>
		</names>
		<date value="2002-11"/>
		<title type="sharef:secondaryTitle">xml.com</title>
		<title type="sharef:primaryTitle">XML Versus the Infoset</title>
		<field type="bibtex:topic">xml[0.8] xmlinfoset[0.8]</field>
		<identifier type="sharef:uri" resourceType="text/html">http://www.xml.com/pub/a/ws/2002/11/20/ends.html</identifier>
	</reference>
	<reference name="coa03" src="bibtex:article" src-info="bibtex:line-2002" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Anthony B.</givenname>
				<surname>Coates</surname>
			</person>
			<person>
				<givenname>Zarella</givenname>
				<surname>Rendon</surname>
			</person>
		</names>
		<date value="2003-01"/>
		<title type="sharef:secondaryTitle">xml.com</title>
		<title type="sharef:primaryTitle">Named Character Elements for XML</title>
		<field type="bibtex:topic">xml[0.7]</field>
		<identifier type="sharef:uri" resourceType="text/html">http://www.xml.com/pub/a/2003/01/02/xmlchar.html</identifier>
	</reference>
	<reference name="orc03" src="bibtex:article" src-info="bibtex:line-2012" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>David</givenname>
				<surname>Orchard</surname>
			</person>
		</names>
		<date value="2003-12"/>
		<title type="sharef:secondaryTitle">xml.com</title>
		<title type="sharef:primaryTitle">Versioning XML Vocabularies</title>
		<field type="bibtex:topic">xsd[0.8]</field>
		<identifier type="sharef:uri" resourceType="text/html">http://www.xml.com/pub/a/2003/12/03/versioning.html</identifier>
	</reference>
	<reference name="orc04" src="bibtex:article" src-info="bibtex:line-2022" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>David</givenname>
				<surname>Orchard</surname>
			</person>
		</names>
		<date value="2004-10"/>
		<title type="sharef:secondaryTitle">xml.com</title>
		<title type="sharef:primaryTitle">Extensibility, XML Vocabularies, and XML Schema</title>
		<field type="bibtex:topic">xsd[0.8]</field>
		<field type="bibtex:updates">orc03</field>
		<identifier type="sharef:uri" resourceType="text/html">http://www.xml.com/pub/a/2004/10/27/extend.html</identifier>
	</reference>
	<reference name="duc03" src="bibtex:article" src-info="bibtex:line-2033" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Bob</givenname>
				<surname>DuCharme</surname>
			</person>
		</names>
		<date value="2003-12"/>
		<title type="sharef:secondaryTitle">xml.com</title>
		<title type="sharef:primaryTitle">Trees, Temporarily</title>
		<field type="bibtex:topic">xslt1[0.8]</field>
		<identifier type="sharef:uri" resourceType="text/html">http://www.xml.com/pub/a/2003/12/03/tr.html</identifier>
	</reference>
	<reference name="oba03" src="bibtex:article" src-info="bibtex:line-2043" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Dare</givenname>
				<surname>Obasanjo</surname>
			</person>
		</names>
		<date value="2003-10"/>
		<title type="sharef:secondaryTitle">xml.com</title>
		<title type="sharef:primaryTitle">XML Schema Design Patterns: Is Complex Type Derivation Unnecessary?</title>
		<field type="bibtex:topic">xsd[0.8]</field>
		<identifier type="sharef:uri" resourceType="text/html">http://www.xml.com/pub/a/2003/10/29/derivation.html</identifier>
	</reference>
	<reference name="oba02a" src="bibtex:article" src-info="bibtex:line-2053" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Dare</givenname>
				<surname>Obasanjo</surname>
			</person>
		</names>
		<date value="2002-07"/>
		<title type="sharef:secondaryTitle">xml.com</title>
		<title type="sharef:primaryTitle">W3C XML Schema Design Patterns: Dealing With Change</title>
		<field type="bibtex:topic">xsd[0.8]</field>
		<identifier type="sharef:uri" resourceType="text/html">http://www.xml.com/pub/a/2002/07/03/schema_design.html</identifier>
	</reference>
	<reference name="oba02b" src="bibtex:article" src-info="bibtex:line-2063" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Dare</givenname>
				<surname>Obasanjo</surname>
			</person>
		</names>
		<date value="2002-11"/>
		<title type="sharef:secondaryTitle">xml.com</title>
		<title type="sharef:primaryTitle">W3C XML Schema Design Patterns: Avoiding Complexity</title>
		<field type="bibtex:topic">xsd[0.8]</field>
		<identifier type="sharef:uri" resourceType="text/html">http://www.xml.com/pub/a/2002/11/20/schemas.html</identifier>
	</reference>
	<reference name="oba02c" src="bibtex:article" src-info="bibtex:line-2073" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Dare</givenname>
				<surname>Obasanjo</surname>
			</person>
		</names>
		<date value="2002-12"/>
		<title type="sharef:secondaryTitle">xml.com</title>
		<title type="sharef:primaryTitle">A Data Model for Strongly Typed XML</title>
		<field type="bibtex:topic">xpath1[0.8]</field>
		<identifier type="sharef:uri" resourceType="text/html">http://www.xml.com/pub/a/2002/12/19/datamodel.html</identifier>
	</reference>
	<reference name="wil03k" src="bibtex:article" src-info="bibtex:line-2083" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Erik</givenname>
				<surname>Wilde</surname>
			</person>
		</names>
		<date value="2003-08"/>
		<abstract>
			<richtext>
				<p>XML Schema is a very powerful and also a rather complex schema language. One of the problems when working with XML Schema is the fact that XML Schema uses an XML syntax, which makes XML Schemas verbose and hard to read. In this article, we describe a compact text-based syntax for XML Schema, called XML Schema Compact Syntax (XSCS), which re-uses well known syntactic constructs from DTDs; and we present a Java-based implementation for converting the compact syntax to the XML syntax and vice versa.</p>
			</richtext>
		</abstract>
		<title type="sharef:secondaryTitle">xml.com</title>
		<title type="sharef:primaryTitle">A Compact Syntax for XML Schema</title>
		<field type="bibtex:topic">xscs[0.8]</field>
		<identifier type="sharef:uri">http://dret.net/netdret/publications#wil03k</identifier>
		<identifier type="sharef:uri" resourceType="text/html">http://www.xml.com/pub/a/2003/08/27/xscs.html</identifier>
	</reference>
	<reference name="wil04c" src="bibtex:article" src-info="bibtex:line-2095" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Erik</givenname>
				<surname>Wilde</surname>
			</person>
		</names>
		<date value="2004-01"/>
		<abstract>
			<richtext>
				<p>In this article, a small schema language for XML is presented which can be used to restrict the use of character repertoires in XML documents. It is called Character Repertoire Validation for XML (CRVX). CRVX restrictions can be based on structural components of an XML document, contexts, or a combination of both.</p>
			</richtext>
		</abstract>
		<title type="sharef:secondaryTitle">xml.com</title>
		<title type="sharef:primaryTitle">Character Repertoire Validation for XML</title>
		<field type="bibtex:topic">crvx[0.8]</field>
		<identifier type="sharef:uri">http://dret.net/netdret/publications#wil04c</identifier>
		<identifier type="sharef:uri" resourceType="text/html">http://www.xml.com/pub/a/2004/01/14/crv.html</identifier>
	</reference>
	<reference name="wil07g" src="bibtex:article" src-info="bibtex:line-2107" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Erik</givenname>
				<surname>Wilde</surname>
			</person>
		</names>
		<date value="2007-03"/>
		<abstract>
			<richtext>
				<p>Assembling various parts of a document before processing the assembled document is a recurring theme in document processing. XML Inclusions (XInclude) is the W3C standard which has been created to support this scenario, but since it is a standalone specification, it needs to be supported by a piece of software implementing this functionality. The XInclude Processor (XIPr) written in XSLT 2.0 implements XInclude and thus may help to reduce the dependency on numerous software packages, if XInclude should be used in an environment where XSLT 2.0 is used anyway. XIPr is implemented as a single XSLT 2.0 stylesheet and can be used standalone in a publishing pipeline, or as an imported module in some other XSLT code for integrated XInclude processing.</p>
			</richtext>
		</abstract>
		<title type="sharef:secondaryTitle">xml.com</title>
		<title type="sharef:primaryTitle">XInclude Processing in XSLT</title>
		<field type="bibtex:topic">xipr[0.9]</field>
		<identifier type="sharef:uri">http://dret.net/netdret/publications#wil07g</identifier>
		<identifier type="sharef:uri" resourceType="text/html">http://www.xml.com/pub/a/2007/03/28/xinclude-processing-in-xslt-with-xipr.html</identifier>
	</reference>
	<reference name="car01c" src="bibtex:article" src-info="bibtex:line-2119" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>David</givenname>
				<surname>Carlson</surname>
			</person>
		</names>
		<date value="2001-08"/>
		<title type="sharef:secondaryTitle">xml.com</title>
		<title type="sharef:primaryTitle">Modeling XML Vocabularies with UML</title>
		<field type="bibtex:topic">xml[0.8] uml[0.8]</field>
		<identifier type="sharef:uri" resourceType="text/html">http://www.xml.com/pub/a/2001/08/22/uml.html</identifier>
	</reference>
	<reference name="pro02" src="bibtex:article" src-info="bibtex:line-2129" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Will</givenname>
				<surname>Provost</surname>
			</person>
		</names>
		<date value="2002-08"/>
		<title type="sharef:secondaryTitle">xml.com</title>
		<title type="sharef:primaryTitle">UML for W3C XML Schema Design</title>
		<field type="bibtex:topic">xml[0.8] uml[0.8] xsd[0.8]</field>
		<identifier type="sharef:uri" resourceType="text/html">http://www.xml.com/pub/a/2002/08/07/wxs_uml.html</identifier>
	</reference>
	<reference name="pro02b" src="bibtex:article" src-info="bibtex:line-2139" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Will</givenname>
				<surname>Provost</surname>
			</person>
		</names>
		<date value="2002-10"/>
		<title type="sharef:secondaryTitle">xml.com</title>
		<title type="sharef:primaryTitle">Working with a Metaschema</title>
		<field type="bibtex:topic">xsd[0.8]</field>
		<identifier type="sharef:uri" resourceType="text/html">http://www.xml.com/pub/a/2002/10/02/metaschema.html</identifier>
	</reference>
	<reference name="nel97" src="bibtex:article" src-info="bibtex:line-2149" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Theodor Holm</givenname>
				<surname>Nelson</surname>
			</person>
		</names>
		<date value="1997-10"/>
		<title type="sharef:secondaryTitle">xml.com</title>
		<title type="sharef:primaryTitle">Embedded Markup Considered Harmful</title>
		<identifier type="sharef:uri" resourceType="text/html">http://www.xml.com/pub/a/w3j/s3.nelson.html</identifier>
	</reference>
	<reference name="wal03" src="bibtex:article" src-info="bibtex:line-2158" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Norman</givenname>
				<surname>Walsh</surname>
			</person>
		</names>
		<date value="2003-08"/>
		<title type="sharef:secondaryTitle">xml.com</title>
		<title type="sharef:primaryTitle">Escaped Markup Considered Harmful</title>
		<field type="bibtex:topic">cdata[0.7]</field>
		<identifier type="sharef:uri" resourceType="text/html">http://www.xml.com/pub/a/2003/08/20/embedded.html</identifier>
	</reference>
	<reference name="wil05p" src="bibtex:article" src-info="bibtex:line-2172" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Erik</givenname>
				<surname>Wilde</surname>
			</person>
		</names>
		<date value="2005-09"/>
		<title type="sharef:secondaryTitle">XML &amp; Web Services Magazin</title>
		<number>4</number>
		<pages>8</pages>
		<title type="sharef:primaryTitle">Buchrezension "Einstieg in XML" von Helmut Vonhoegen</title>
		<identifier type="sharef:uri">http://dret.net/netdret/publications#wil05p</identifier>
		<volume>2005</volume>
	</reference>
	<reference name="wil04b" src="bibtex:article" src-info="bibtex:line-2184" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Erik</givenname>
				<surname>Wilde</surname>
			</person>
		</names>
		<date value="2004-01"/>
		<title type="sharef:secondaryTitle">XML &amp; Web Services Magazin</title>
		<number>1</number>
		<pages>11</pages>
		<title type="sharef:primaryTitle">Buchrezension "XML Schema" von Eric van der Vlist</title>
		<identifier type="sharef:uri">http://dret.net/netdret/publications#wil03b</identifier>
		<volume>2004</volume>
	</reference>
	<reference name="wil04e" src="bibtex:article" src-info="bibtex:line-2196" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Erik</givenname>
				<surname>Wilde</surname>
			</person>
		</names>
		<date value="2004-03"/>
		<title type="sharef:secondaryTitle">XML &amp; Web Services Magazin</title>
		<number>2</number>
		<pages>11</pages>
		<title type="sharef:primaryTitle">Buchrezension "Topic Maps" von Richard Widhalm und Thomas Mück</title>
		<identifier type="sharef:uri">http://dret.net/netdret/publications#wil04e</identifier>
		<volume>2004</volume>
	</reference>
	<reference name="wil03m" src="bibtex:article" src-info="bibtex:line-2208" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Erik</givenname>
				<surname>Wilde</surname>
			</person>
		</names>
		<date value="2003-08"/>
		<title type="sharef:secondaryTitle">XML &amp; Web Services Magazin</title>
		<number>5</number>
		<pages>46-47</pages>
		<title type="sharef:primaryTitle">Tool-Unterstützung für XML Schema</title>
		<field type="bibtex:topic">xsd[0.8]</field>
		<identifier type="sharef:uri">http://dret.net/netdret/publications#wil03m</identifier>
		<volume>2003</volume>
	</reference>
	<reference name="wil03p" src="bibtex:article" src-info="bibtex:line-2221" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Erik</givenname>
				<surname>Wilde</surname>
			</person>
		</names>
		<date value="2003-10"/>
		<abstract>
			<richtext>
				<p>XML Schema bietet im Gegensatz zu DTDs eine Vielzahl an Modellierungsfeatures und damit realisierbaren Varianten. Oft ist nicht klar, auf welche Weise ein gegebenes Modell am besten als XML Schema umgesetzt werden sollte. In diesem und einem nachfolgenden Artikel wird deshalb der Frage nachgegangen, welche Varianten es gibt, wie sie sich unterscheiden, was ihre Vor- und Nachteile sind, und wie sie sich insbesondere unter dem Blickpunkt der Wiederverwendung und Erweiterbarkeit bewerten lassen.</p>
			</richtext>
		</abstract>
		<title type="sharef:secondaryTitle">XML &amp; Web Services Magazin</title>
		<number>6</number>
		<pages>46-56</pages>
		<title type="sharef:primaryTitle">Modellierungsvarianten mit XML Schema</title>
		<field type="bibtex:topic">xsd[0.8]</field>
		<identifier type="sharef:uri">http://dret.net/netdret/publications#wil03p</identifier>
		<volume>2003</volume>
	</reference>
	<reference name="wil04d" src="bibtex:article" src-info="bibtex:line-2235" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Erik</givenname>
				<surname>Wilde</surname>
			</person>
		</names>
		<date value="2004-06"/>
		<abstract>
			<richtext>
				<p>XML bietet verschiedene Möglichkeiten, erweiterbare Datenstrukturen zu definieren und zu verwenden, aber es bleibt dennoch der Umsicht und vor allem der Planung von Designern überlassen, XML tatsächlich so zu verwenden, dass es diese Vorteile ausspielen kann. In diesem Artikel betrachten wir, wieso Erweiterbarkeit bei der Verwendung von XML ein wichtiger Aspekt ist, und wie sich diese Erweiterbarkeit mit XML Schema erreichen lässt. Als weiteren Aspekt betrachten wir die Offenheit eines Schemas, also die Frage, inwieweit ein Schema Erweiterungen in Dokumenten zulässt.</p>
			</richtext>
		</abstract>
		<title type="sharef:secondaryTitle">XML &amp; Web Services Magazin</title>
		<number>3</number>
		<pages>42-47</pages>
		<title type="sharef:primaryTitle">Entwurf erweiterbarer XML Schemas</title>
		<field type="bibtex:topic">xsd[0.8]</field>
		<identifier type="sharef:uri">http://dret.net/netdret/publications#wil04d</identifier>
		<volume>2004</volume>
	</reference>
	<reference name="wil04l" src="bibtex:article" src-info="bibtex:line-2249" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Erik</givenname>
				<surname>Wilde</surname>
			</person>
		</names>
		<date value="2004-09"/>
		<abstract>
			<richtext>
				<p>Für die Versionierung von XML Schemas ist es notwendig, sich Gedanken über den Umgang mit Versionen zu machen, und zwar aus zweierlei Sicht. Die erste Sicht ist die des Schema-Entwickler, dem sich die Frage stellt, wie er die Namespaces handhabt, die für die verschiedenen Schemas verwendet werden. Die andere Sicht ist die der Software-Entwickler, die in ihre Software Wissen darum einbauen müssen, wie mit Instanzen verschiedener Versionen umgegangen wird. Beide Sichten sollten gemeinsam dazu beitragen, ein möglichst robustes und flexibles Szenario zu implementieren, in dem verschiedene Schemaversionen koexistieren können.</p>
			</richtext>
		</abstract>
		<title type="sharef:secondaryTitle">XML &amp; Web Services Magazin</title>
		<number>4</number>
		<pages>47-52</pages>
		<title type="sharef:primaryTitle">Namespaces und Versionierung von XML Schemas</title>
		<field type="bibtex:topic">xsd[0.8]</field>
		<identifier type="sharef:uri">http://dret.net/netdret/publications#wil04l</identifier>
		<volume>2004</volume>
	</reference>
	<reference name="wil05c" src="bibtex:article" src-info="bibtex:line-2263" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Erik</givenname>
				<surname>Wilde</surname>
			</person>
		</names>
		<date value="2005-03"/>
		<abstract>
			<richtext>
				<p>XML bietet zwar durchaus das allgemein akzeptierte Verfahren zum Austausch strukturierter Daten, das in vielen Anwendungen benötigt wird, ist aber dennoch nicht ausreichend, Interoperabilität zwischen Anwendungen sicherzustellen. Probleme können auf vielen verschiedenen Ebenen entstehen, beginnend bei so grundlegenden Dingen wie Zeichencodierungen, bis hin zu Problemen des inhaltlichen Verständnisses von XML Dokumenten. Im vorliegenden Artikel soll auf den letzteren Aspekt näher eingegangen werden, also die Frage, was notwendig ist, damit der Austausch von XML nicht nur syntaktisch funktioniert, sondern auch auf einem gemeinsamen Verständnis beider Seiten basiert.</p>
			</richtext>
		</abstract>
		<title type="sharef:secondaryTitle">XML &amp; Web Services Magazin</title>
		<number>2</number>
		<pages>35-38</pages>
		<title type="sharef:primaryTitle">Semantische Interoperabilität von XML Schemas</title>
		<field type="bibtex:topic">xsd[0.8]</field>
		<identifier type="sharef:uri">http://dret.net/netdret/publications#wil05c</identifier>
		<volume>2005</volume>
	</reference>
	<reference name="zoe03" src="bibtex:article" src-info="bibtex:line-2277" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Stefan</givenname>
				<surname>Zörner</surname>
			</person>
		</names>
		<date value="2003-08"/>
		<title type="sharef:secondaryTitle">XML &amp; Web Services Magazin</title>
		<number>5</number>
		<pages>55-58</pages>
		<title type="sharef:primaryTitle">DSML v2.0 — Die Directory Services Markup Language</title>
		<field type="bibtex:topic">dsml[0.8]</field>
		<volume>2003</volume>
	</reference>
	<reference name="mcf05" src="bibtex:article" src-info="bibtex:line-2293" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Nigel</givenname>
				<surname>McFarlane</surname>
			</person>
		</names>
		<date value="2005-08"/>
		<title type="sharef:secondaryTitle">Linux Magazine</title>
		<title type="sharef:primaryTitle">Fixing Web Sites with Greasemonkey</title>
		<identifier type="sharef:uri">http://www.linuxjournal.com/article/8215</identifier>
	</reference>
	<reference name="fis04" src="bibtex:article" src-info="bibtex:line-2306" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Oliver</givenname>
				<surname>Fischer</surname>
			</person>
		</names>
		<date value="2004-04"/>
		<title type="sharef:secondaryTitle">iX</title>
		<number>4</number>
		<pages>123-125</pages>
		<title type="sharef:primaryTitle">Verteilte Dokumente mit externen Entitäten</title>
		<identifier type="sharef:uri">http://www.heise.de/ix/artikel/2004/04/123/</identifier>
		<volume>17</volume>
	</reference>
	<reference name="wil00c" src="bibtex:article" src-info="bibtex:line-2318" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Erik</givenname>
				<surname>Wilde</surname>
			</person>
		</names>
		<date value="2000-06"/>
		<title type="sharef:secondaryTitle">iX</title>
		<number>6</number>
		<pages>161-162</pages>
		<title type="sharef:primaryTitle">Links: Hypermedia für XML im Entstehen</title>
		<field type="bibtex:topic">xml[0.6] xlink[0.8] xpointer[0.8] xpath1[0.8]</field>
		<identifier type="sharef:uri">http://dret.net/netdret/publications#wil00c</identifier>
		<volume>13</volume>
	</reference>
	<reference name="wil01b" src="bibtex:article" src-info="bibtex:line-2331" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Erik</givenname>
				<surname>Wilde</surname>
			</person>
		</names>
		<date value="2001-07"/>
		<title type="sharef:secondaryTitle">iX</title>
		<number>7</number>
		<pages>20</pages>
		<title type="sharef:primaryTitle">Bericht von der 10. WWW-Konferenz (WWW10) in Hong Kong</title>
		<identifier type="sharef:uri">http://dret.net/netdret/publications#wil01b</identifier>
		<volume>14</volume>
	</reference>
	<reference name="wil04k" src="bibtex:article" src-info="bibtex:line-2343" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Erik</givenname>
				<surname>Wilde</surname>
			</person>
		</names>
		<date value="2004-07"/>
		<title type="sharef:secondaryTitle">iX</title>
		<number>7</number>
		<pages>108-109</pages>
		<title type="sharef:primaryTitle">XInclude: Zusammenfügen verschiedener XML-Dokumente</title>
		<field type="bibtex:topic">xinclude[0.8]</field>
		<identifier type="sharef:uri">http://dret.net/netdret/publications#wil04k</identifier>
		<volume>17</volume>
	</reference>
	<reference name="wil03a" src="bibtex:article" src-info="bibtex:line-2356" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Erik</givenname>
				<surname>Wilde</surname>
			</person>
		</names>
		<date value="2003-02"/>
		<title type="sharef:secondaryTitle">iX</title>
		<number>2</number>
		<pages>12</pages>
		<title type="sharef:primaryTitle">Bericht von der XML 2002 in Baltimore</title>
		<identifier type="sharef:uri">http://dret.net/netdret/publications#wil03a</identifier>
		<volume>16</volume>
	</reference>
	<reference name="wil02f" src="bibtex:article" src-info="bibtex:line-2368" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Erik</givenname>
				<surname>Wilde</surname>
			</person>
		</names>
		<date value="2002-07"/>
		<title type="sharef:secondaryTitle">iX</title>
		<number>7</number>
		<pages>11</pages>
		<title type="sharef:primaryTitle">Bericht von der 11. WWW-Konferenz (WWW2002) in Honolulu</title>
		<identifier type="sharef:uri">http://dret.net/netdret/publications#wil02f</identifier>
		<volume>15</volume>
	</reference>
	<reference name="wil05m" src="bibtex:article" src-info="bibtex:line-2380" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Erik</givenname>
				<surname>Wilde</surname>
			</person>
		</names>
		<date value="2005-07"/>
		<title type="sharef:secondaryTitle">iX</title>
		<number>7</number>
		<pages>18</pages>
		<title type="sharef:primaryTitle">Bericht von der 14. WWW-Konferenz (WWW2005) in Chiba</title>
		<identifier type="sharef:uri">http://dret.net/netdret/publications#wil05m</identifier>
		<volume>18</volume>
	</reference>
	<reference name="wil05s" src="bibtex:article" src-info="bibtex:line-2392" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Thierry</givenname>
				<surname>Bücheler</surname>
			</person>
			<person>
				<givenname>Erik</givenname>
				<surname>Wilde</surname>
			</person>
		</names>
		<date value="2005-10"/>
		<title type="sharef:secondaryTitle">iX</title>
		<number>10</number>
		<pages>133-135</pages>
		<title type="sharef:primaryTitle">JSF versus Struts: Server-seitige Java-Techniken im Web</title>
		<field type="bibtex:topic">jsf[0.7] struts[0.7]</field>
		<identifier type="sharef:uri">http://dret.net/netdret/publications#wil05s</identifier>
		<volume>18</volume>
	</reference>
	<reference name="wil02g" src="bibtex:article" src-info="bibtex:line-2405" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Stefan</givenname>
				<surname>Mintert</surname>
			</person>
			<person>
				<givenname>Erik</givenname>
				<surname>Wilde</surname>
			</person>
			<person>
				<givenname>Henning</givenname>
				<surname>Behme</surname>
			</person>
		</names>
		<date value="2002-08"/>
		<title type="sharef:secondaryTitle">iX</title>
		<number>8</number>
		<pages>52-58</pages>
		<title type="sharef:primaryTitle">XML-Editoren</title>
		<field type="bibtex:topic">xml[0.7]</field>
		<identifier type="sharef:uri">http://dret.net/netdret/publications#wil02g</identifier>
		<volume>15</volume>
	</reference>
	<reference name="ple01" src="bibtex:article" src-info="bibtex:line-2418" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Christian</givenname>
				<surname>Plessl</surname>
			</person>
			<person>
				<givenname>Erik</givenname>
				<surname>Wilde</surname>
			</person>
		</names>
		<date value="2001-03"/>
		<title type="sharef:secondaryTitle">iX</title>
		<number>3</number>
		<pages>88-93</pages>
		<title type="sharef:primaryTitle">Server-Side-Techniken im Web — ein Überblick</title>
		<field type="bibtex:topic">jsp[0.7] asp[0.7] perl[0.7] cgi[0.7] servlet[0.7] php[0.7]</field>
		<identifier type="sharef:uri">http://dret.net/netdret/publications#ple01</identifier>
		<volume>14</volume>
	</reference>
	<reference name="dij71" src="bibtex:article" src-info="bibtex:line-2435" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Edsger W.</givenname>
				<surname>Dijkstra</surname>
			</person>
		</names>
		<date value="1971"/>
		<field type="bibtex:index">dining philosophers</field>
		<title type="sharef:secondaryTitle">Acta Informatica</title>
		<pages>115-138</pages>
		<title type="sharef:primaryTitle">Hierarchical Ordering of Sequential Processes</title>
		<identifier type="sharef:uri">http://www.informatik.uni-trier.de/~ley/db/journals/acta</identifier>
		<volume>1</volume>
	</reference>
	<reference name="ber02" src="bibtex:article" src-info="bibtex:line-2446" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Jean</givenname>
				<surname>Berstel</surname>
			</person>
			<person>
				<givenname>Luc</givenname>
				<surname>Boasson</surname>
			</person>
		</names>
		<date value="2002"/>
		<abstract>
			<richtext>
				<p>We consider XML documents described by a document type definition (DTD). An XML-grammar is a formal grammar that captures the syntactic features of a DTD. We investigate properties of this family of grammars. We show that every XML-language basically has a unique XML-grammar. We give two characterizations of languages generated by XML-grammars, one is set-theoretic, the other is by a kind of saturation property. We investigate decidability problems and prove that some properties that are undecidable for general context-free languages become decidable for XML-languages. We also characterize those XML-grammars that generate regular XML-languages.</p>
			</richtext>
		</abstract>
		<title type="sharef:secondaryTitle">Acta Informatica</title>
		<number>9</number>
		<pages>649-671</pages>
		<title type="sharef:primaryTitle">Formal Properties of XML Grammars and Languages</title>
		<field type="bibtex:topic">xml[0.8]</field>
		<identifier type="sharef:uri">http://www.springerlink.com/link.asp?id=ldpcelpnd61qe8n3</identifier>
		<volume>38</volume>
	</reference>
	<reference name="wan02" src="bibtex:article" src-info="bibtex:line-2463" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Yair</givenname>
				<surname>Wand</surname>
			</person>
			<person>
				<givenname>Ron</givenname>
				<surname>Weber</surname>
			</person>
		</names>
		<date value="2002-12"/>
		<abstract>
			<richtext>
				<p>Within the information systems field, the task of conceptual modeling involves building a representation of selected phenomena in some domain. High-quality conceptual modeling work is important because it facilitates early detection and correction of system development errors. It also plays an increasingly important role in activities like business process reengineering and documentation of best-practice data and process models in enterprise resource planning systems. Yet little research has been undertaken on many aspects of conceptual modeling. In this paper, we propose a framework to motivate research that addresses the following fundamental question: How can we model the world to better facilitate our developing, implementing, using, and maintaining more valuable information systems? The framework comprises four elements: conceptual-modeling grammars, conceptual-modeling methods, conceptual-modeling scripts, and conceptual-modeling contexts. We provide examples of the types of research that have already been undertaken on each element and illustrate research opportunities that exist.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1287/isre.13.4.363.69</identifier>
		<title type="sharef:secondaryTitle">Information Systems Research</title>
		<number>4</number>
		<pages>363-376</pages>
		<title type="sharef:primaryTitle">Research Commentary: Information Systems and Conceptual Modeling — A Research Agenda</title>
		<identifier type="sharef:uri">http://www.extenza-eps.com/INF/doi/abs/10.1287/isre.13.4.363.69?journalCode=isre</identifier>
		<identifier type="sharef:uri" resourceType="application/pdf">http://ewalden.ba.ttu.edu/courses/spring2003/4348/Wand%20and%20Weber%20(2002).pdf</identifier>
		<volume>13</volume>
	</reference>
	<reference name="ber06" src="bibtex:article" src-info="bibtex:line-2482" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Tim</givenname>
				<surname>Berners-Lee</surname>
			</person>
			<person>
				<givenname>Wendy</givenname>
				<surname>Hall</surname>
			</person>
			<person>
				<givenname>James A.</givenname>
				<surname>Hendler</surname>
			</person>
			<person>
				<givenname>Nigel</givenname>
				<surname>Shadbolt</surname>
			</person>
			<person>
				<givenname>Daniel J.</givenname>
				<surname>Weitzner</surname>
			</person>
		</names>
		<date value="2006-08"/>
		<identifier type="sharef:doi">10.1126/science.1126902</identifier>
		<title type="sharef:secondaryTitle">Science</title>
		<number>5788</number>
		<pages>769-771</pages>
		<title type="sharef:primaryTitle">Creating a Science of the Web</title>
		<field type="bibtex:topic">www[0.9]</field>
		<identifier type="sharef:uri">http://www.sciencemag.org/cgi/content/full/313/5788/769</identifier>
		<volume>313</volume>
	</reference>
	<reference name="law99" src="bibtex:article" src-info="bibtex:line-2500" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Steve</givenname>
				<surname>Lawrence</surname>
			</person>
			<person>
				<givenname>C. Lee</givenname>
				<surname>Giles</surname>
			</person>
		</names>
		<date value="1999-07"/>
		<title type="sharef:secondaryTitle">Nature</title>
		<number>6740</number>
		<pages>107-109</pages>
		<title type="sharef:primaryTitle">Accessibility of Information on the Web</title>
		<field type="bibtex:topic">searchengine[0.9]</field>
		<identifier type="sharef:uri" resourceType="text/html">http://www.nature.com/cgi-taf/DynaPage.taf?file=/nature/journal/v400/n6740/full/400107a0_fs.html</identifier>
		<volume>400</volume>
	</reference>
	<reference name="but00" src="bibtex:article" src-info="bibtex:line-2513" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Declan</givenname>
				<surname>Butler</surname>
			</person>
		</names>
		<date value="2000-05"/>
		<title type="sharef:secondaryTitle">Nature</title>
		<number>6783</number>
		<pages>112-115</pages>
		<title type="sharef:primaryTitle">Souped-up Search Engines</title>
		<field type="bibtex:topic">searchengine[0.9] google[0.8]</field>
		<identifier type="sharef:uri" resourceType="text/html">http://www.nature.com/cgi-taf/DynaPage.taf?file=/nature/journal/v405/n6783/full/405112a0_fs.html</identifier>
		<volume>405</volume>
	</reference>
	<reference name="law01" src="bibtex:article" src-info="bibtex:line-2526" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Steve</givenname>
				<surname>Lawrence</surname>
			</person>
		</names>
		<date value="2001-05"/>
		<title type="sharef:secondaryTitle">Nature</title>
		<number>6837</number>
		<pages>521</pages>
		<title type="sharef:primaryTitle">Free Online Availability Substantially Increases a Paper's Impact</title>
		<identifier type="sharef:uri" resourceType="text/html">http://www.nature.com/cgi-taf/DynaPage.taf?file=/nature/journal/v411/n6837/full/411521a0_fs.html</identifier>
		<volume>411</volume>
	</reference>
	<reference name="gin04a" src="bibtex:article" src-info="bibtex:line-2542" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Mark</givenname>
				<surname>Ginsburg</surname>
			</person>
		</names>
		<date value="2004">January-June 2004</date>
		<abstract>
			<richtext>
				<p>Scientific research is hindered when there are artificial barriers preventing efficient and straightforward sharing of bibliographic information. In today's computing world, the barriers take the form of incompatible bibliographic formats and constraining operating system and vendor dependencies. These incompatible platforms isolate the respective camps. In this paper, we demonstrate and discuss a new approach to unify citation management, called the Open Citation System (OCS). OCS uses open XML standards and Java component technologies. By providing converter tools to migrate citations to a centralized "hub" in BiblioML format (an XML tag set based on the UniMARC standard), we then make use of XML Topic Maps to provide an extensible framework for visualization. We take as an example the ACM Classification Code and show how the OCS system displays citations in a convenient focus + context hyperbolic tree interface. We conclude by discussing future directions planned to extend the OCS system and how open citation management can supply an important piece in our inexorable march towards a worldwide digital library.</p>
			</richtext>
		</abstract>
		<title type="sharef:secondaryTitle">Journal of IT Standards and Standardization Research</title>
		<number>1</number>
		<pages>23-41</pages>
		<title type="sharef:primaryTitle">Unified Citation Management and Visualization Using Open Standards: The Open Citation System</title>
		<field type="bibtex:topic">ocs[0.9] biblioml[0.8]</field>
		<identifier type="sharef:uri" resourceType="application/pdf">http://uaeller.eller.arizona.edu/~mginsbur/pubs/ocs.pdf</identifier>
		<volume>2</volume>
	</reference>
	<reference name="gin04b" src="bibtex:article" src-info="bibtex:line-2560" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Mark</givenname>
				<surname>Ginsburg</surname>
			</person>
		</names>
		<date value="2004-03"/>
		<abstract>
			<richtext>
				<p>Large scale research Digital Libraries (DLs) have a large array of potentially useful metadata. Yet, many popular DLs do not provide a convenient way to navigate the metadata or to visualize classification schema in the user session. For example, in the broad world of Management Information Systems (MIS) research, a high-level overview of MIS topics and their interrelationships would be useful to navigate a MIS DL before zooming in on a specific article. To address this obstacle, this paper describes a prototype, the Technical Report Visualizer System (TRV), which uses a wide variety of open standards to expose DL classification metadata in the navigation interface. The system captures MIS article metadata from the Open Archives Initiative (OAI) compliant arXiv e-Print archive at Cornell University. The OAI Protocol for Metadata Harvesting (OAI-PMH) is used to collect the topic metadata; the articles' Association for Computing Machinery's (ACM) Computing Classification System codes. We display the topic metadata in a Java hyperbolic tree and make use of XML conceptual product and implementation product standards and specifications, such as the Dublin Core and BiblioML bibliographic metadata sets, XML Topic Maps, Xalan and Xerces, to link user navigation activity to the abstracts and full text contents of the articles. We discuss the flexibility and convenience of XML standards and link this effort to related digital library visualization approaches.</p>
			</richtext>
		</abstract>
		<title type="sharef:secondaryTitle">Communications of the Association for Information Systems</title>
		<pages>336-356</pages>
		<title type="sharef:primaryTitle">Visualizing Digital Libraries with Open Standards</title>
		<field type="bibtex:topic">ocs[0.9] biblioml[0.8]</field>
		<identifier type="sharef:uri" resourceType="application/pdf">http://uaeller.eller.arizona.edu/~mginsbur/pubs/2004/cais_dl.pdf</identifier>
		<identifier type="sharef:uri">http://cais.isworld.org/articles/default.asp?vol=13&amp;art=22</identifier>
		<volume>13</volume>
	</reference>
	<reference name="car98" src="bibtex:article" src-info="bibtex:line-2578" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Leslie A.</givenname>
				<surname>Carr</surname>
			</person>
		</names>
		<date value="1998-10"/>
		<title type="sharef:secondaryTitle">InterChange — Newsletter of the International SGML/XML Users' Group</title>
		<number>4</number>
		<pages>17-22</pages>
		<title type="sharef:primaryTitle">A Simple XLink Package</title>
		<field type="bibtex:topic">xlink[0.8] xpointer[0.8]</field>
		<volume>4</volume>
	</reference>
	<reference name="ber08" src="bibtex:article" src-info="bibtex:line-2594" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Tim</givenname>
				<surname>Berners-Lee</surname>
			</person>
		</names>
		<date value="2008-01"/>
		<title type="sharef:secondaryTitle">ERCIM News</title>
		<number>72</number>
		<pages>3</pages>
		<title type="sharef:primaryTitle">The Web of Things</title>
		<identifier type="sharef:uri" resourceType="application/pdf">http://ercim-news.ercim.org/images/stories/EN72/EN72-web.pdf</identifier>
		<identifier type="sharef:uri">http://ercim-news.ercim.org/content/view/343/533/</identifier>
	</reference>
	<reference name="kum05" src="bibtex:article" src-info="bibtex:line-2610" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Ravi</givenname>
				<surname>Kumar</surname>
			</person>
			<person>
				<givenname>Jasmine</givenname>
				<surname>Novak</surname>
			</person>
			<person>
				<givenname>Prabhakar</givenname>
				<surname>Raghavan</surname>
			</person>
			<person>
				<givenname>Andrew</givenname>
				<surname>Tomkins</surname>
			</person>
		</names>
		<date value="2005-03"/>
		<abstract>
			<richtext>
				<p>We propose two new tools to address the evolution of hyperlinked corpora. First, we define time graphs to extend the traditional notion of an evolving directed graph, capturing link creation as a point phenomenon in time. Second, we develop definitions and algorithms for time-dense community tracking, to crystallize the notion of community evolution. We develop these tools in the context of Blogspace, the space of weblogs (or blogs). Our study involves approximately 750 K links among 25 K blogs. We create a time graph on these blogs by an automatic analysis of their internal time stamps. We then study the evolution of connected component structure and microscopic community structure in this time graph. We show that Blogspace underwent a transition behavior around the end of 2001, and has been rapidly expanding, not just in metrics of scale but also in metrics of community structure and connectedness. By randomizing link destinations in Blogspace, but retaining sources and timestamps, we introduce a concept of randomized Blogspace. Herein, we observe similar evolution of a giant component, but no corresponding increase in community structure. Having demonstrated the formation of micro-communities over time, we then turn to the ongoing activity within active communities. We extend recent work of Kleinberg (2002) to discover dense periods of "bursty" intra-community link creation. Furthermore, we find that the blogs that give rise to these communities are significantly more enduring than an average blog.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1007/s11280-004-4872-4</identifier>
		<title type="sharef:secondaryTitle">World Wide Web</title>
		<number>2</number>
		<pages>159-178</pages>
		<publisher>Springer-Verlag</publisher>
		<title type="sharef:primaryTitle">On the Bursty Evolution of Blogspace</title>
		<volume>8</volume>
	</reference>
	<reference name="liu01" src="bibtex:article" src-info="bibtex:line-2624" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Mengchi</givenname>
				<surname>Liu</surname>
			</person>
			<person>
				<givenname>Tok Wang</givenname>
				<surname>Ling</surname>
			</person>
		</names>
		<date value="2001-03"/>
		<abstract>
			<richtext>
				<p>Most documents available over the Web conform to the HTML specification. Such documents are hierarchically structured in nature. The existing data models for the Web either fail to capture the hierarchical structure within the documents or can only provide a very low level representation of such hierarchical structure. How to represent and query HTML documents at a higher level is an important issue. In this paper, we first propose a novel conceptual model for HTML. This conceptual model has only a few simple constructs but is able to represent the complex hierarchical structure within HTML documents at a level that is close to human conceptualization/visualization of the documents. We also describe how to convert HTML documents based on this conceptual model. Using the conceptual model and conversion method, one can capture the essence (i.e., semistructure) of HTML documents in a natural and simple way. Based on this conceptual model, we then present a rule-based language to query HTML documents over the Internet. This language provides a simple but very powerful way to query both intra-document structures and inter-document structures and allows the query results to be restructured. Being rule-based, it naturally supports negation and recursion and therefore is more expressive than SQL-based languages. A logical semantics is also provided.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1023/A:1012408428703</identifier>
		<title type="sharef:secondaryTitle">World Wide Web</title>
		<number>1-2</number>
		<pages>49-77</pages>
		<publisher>Springer-Verlag</publisher>
		<title type="sharef:primaryTitle">A Conceptual Model and Rule-Based Query Language for HTML</title>
		<identifier type="sharef:uri">http://www.springerlink.com/content/g713234846787156/</identifier>
		<volume>1</volume>
	</reference>
	<reference name="nel97b" src="bibtex:article" src-info="bibtex:line-2643" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Theodor Holm</givenname>
				<surname>Nelson</surname>
			</person>
		</names>
		<date value="1997"/>
		<title type="sharef:secondaryTitle">World Wide Web Journal</title>
		<number>4</number>
		<pages>129-134</pages>
		<title type="sharef:primaryTitle">Embedded Markup Considered Harmful</title>
		<identifier type="sharef:uri">http://portal.acm.org/citation.cfm?id=273632</identifier>
		<volume>2</volume>
	</reference>
	<reference name="con97" src="bibtex:article" src-info="bibtex:line-2654" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Dan</givenname>
				<surname>Connolly</surname>
			</person>
			<person>
				<givenname>Rohit</givenname>
				<surname>Khare</surname>
			</person>
			<person>
				<givenname>Adam</givenname>
				<surname>Rifkin</surname>
			</person>
		</names>
		<date value="1997"/>
		<title type="sharef:secondaryTitle">World Wide Web Journal</title>
		<number>4</number>
		<pages>119-128</pages>
		<title type="sharef:primaryTitle">The Evolution of Web Documents: The Ascent of XML</title>
		<field type="bibtex:topic">xml[0.9]</field>
		<identifier type="sharef:uri">http://www.w3journal.com/</identifier>
		<volume>2</volume>
	</reference>
	<reference name="car98b" src="bibtex:article" src-info="bibtex:line-2666" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Leslie A.</givenname>
				<surname>Carr</surname>
			</person>
			<person>
				<givenname>David C.</givenname>
				<surname>De Roure</surname>
			</person>
			<person>
				<givenname>Hugh C.</givenname>
				<surname>Davis</surname>
			</person>
			<person>
				<givenname>Wendy</givenname>
				<surname>Hall</surname>
			</person>
		</names>
		<date value="1998"/>
		<abstract>
			<richtext>
				<p>Links are the key element for changing a text into a hypertext, and yet the WWW provides limited linking facilities. Modeled on Open Hypermedia research the Distributed Link Service provides an independent system of link services for the World Wide Web and allows authors to create configurable navigation pathways for collections of WWW resources. This is achieved by adding links to documents as they are delivered from a WWW server, and by allowing the users to choose the sets of links that they will see according to their interests. This paper describes the development of the link service, the facilities that it adds for users of the WWW and its specific use in an Electronic Libraries project.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1023/A:1019251328413</identifier>
		<title type="sharef:secondaryTitle">World Wide Web Journal</title>
		<number>2</number>
		<pages>61-71</pages>
		<title type="sharef:primaryTitle">Implementing an Open Link Service for the World Wide Web</title>
		<identifier type="sharef:uri">http://portal.acm.org/citation.cfm?id=598705</identifier>
		<volume>1</volume>
	</reference>
	<reference name="per00a" src="bibtex:article" src-info="bibtex:line-2683" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Mike</givenname>
				<surname>Perkowitz</surname>
			</person>
			<person>
				<givenname>Oren</givenname>
				<surname>Etzioni</surname>
			</person>
		</names>
		<date value="2000-04"/>
		<abstract>
			<richtext>
				<p>Today's Web sites are intricate but not intelligent; while Web navigation is dynamic and idiosyncratic, all too often Web sites are fossils cast in HTML. In response, this paper investigates adaptive Web sites: sites that automatically improve their organization and presentation by learning from visitor access patterns. Adaptive Web sites mine the data buried in Web server logs to produce more easily navigable Web sites. To demonstrate the feasibility of adaptive Web sites, the paper considers the problem of index page synthesis and sketches a solution that relies on novel clustering and conceptual clustering techniques. Our preliminary experiments show that high-quality candidate index pages can be generated automatically, and that our techniques outperform existing methods (including the Apriori algorithm, K-means clustering, hierarchical agglomerative clustering, and COBWEB) in this domain.</p>
			</richtext>
		</abstract>
		<title type="sharef:secondaryTitle">Artifical Intelligence</title>
		<number>1-2</number>
		<pages>245-275</pages>
		<title type="sharef:primaryTitle">Towards Adaptive Web Sites: Conceptual Framework and Case Study</title>
		<identifier type="sharef:uri" resourceType="application/pdf">http://www.cs.washington.edu/research/adaptive/papers/aij.pdf</identifier>
		<volume>118</volume>
	</reference>
	<reference name="bus45" src="bibtex:article" src-info="bibtex:line-2700" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Vannevar</givenname>
				<surname>Bush</surname>
			</person>
		</names>
		<date value="1945-07"/>
		<field type="bibtex:index">hypermedia, Memex</field>
		<title type="sharef:secondaryTitle">The Atlantic Monthly</title>
		<number>1</number>
		<pages>101-108</pages>
		<title type="sharef:primaryTitle">As We May Think</title>
		<identifier type="sharef:uri" resourceType="text/html">http://www.theatlantic.com/unbound/flashbks/computer/bushf.htm</identifier>
		<identifier type="sharef:uri" resourceType="text/html">http://www.csi.uottawa.ca/~dduchier/misc/vbush/awmt.html</identifier>
		<volume>176</volume>
	</reference>
	<reference name="geoweb07" src="bibtex:article" src-info="bibtex:line-2718" type="sharef:article">
		<date value="2007-09-08"/>
		<title type="sharef:secondaryTitle">The Economist</title>
		<title type="sharef:primaryTitle">The World on Your Desktop</title>
		<identifier type="sharef:uri">http://economist.com/search/displaystory.cfm?story_id=9719045</identifier>
	</reference>
	<reference name="ste74" src="bibtex:article" src-info="bibtex:line-2731" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Wayne P.</givenname>
				<surname>Stevens</surname>
			</person>
			<person>
				<givenname>Glenford J.</givenname>
				<surname>Myers</surname>
			</person>
			<person>
				<givenname>Larry L.</givenname>
				<surname>Constantine</surname>
			</person>
		</names>
		<date value="1974"/>
		<abstract>
			<richtext>
				<p>Considerations and techniques are proposed that reduce the complexity of programs by dividing them into functional modules. This can make it possible to create complex systems from simple, independent, reusable modules. Debugging and modifying programs, reconfiguring I/O devices, and managing large programming projects can all be greatly simplified. And, as the module library grows, increasingly sophisticated programs can be implemented using less and less new code.</p>
			</richtext>
		</abstract>
		<title type="sharef:secondaryTitle">IBM Systems Journal</title>
		<number>2</number>
		<pages>115-139</pages>
		<title type="sharef:primaryTitle">Structured Design</title>
		<identifier type="sharef:uri" resourceType="application/pdf">http://www.research.ibm.com/journal/sj/382/stevens.pdf</identifier>
		<volume>13</volume>
	</reference>
	<reference name="glu08a" src="bibtex:article" src-info="bibtex:line-2743" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Robert J.</givenname>
				<surname>Glushko</surname>
			</person>
		</names>
		<date value="2008"/>
		<abstract>
			<richtext>
				<p>This paper relates our experiences at the University of California, Berkeley (UC Berkeley), designing a service science discipline. We wanted to design a discipline of service science in a principled and theoretically motivated way. We began our work by asking, "What questions would a service science have to answer?" and from that we developed a new framework for understanding service science. This framework can be visualized as a matrix whose rows are stages in a service life cycle and whose columns are disciplines that can provide answers to the questions that span the life cycle. This matrix systematically organizes the issues and challenges of service science and enables us to compare our model of a service science discipline with other definitions and curricula. This analysis identified gaps, overlaps, and opportunities that shaped the design of our curriculum and in particular a new survey course that serves as the cornerstone of service science education at UC Berkeley.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1147/sj.471.0015</identifier>
		<title type="sharef:secondaryTitle">IBM Systems Journal</title>
		<number>1</number>
		<title type="sharef:primaryTitle">Designing a Service Science Discipline with Discipline</title>
		<identifier type="sharef:uri" resourceType="text/html">http://www.research.ibm.com/journal/sj/471/glushko.html</identifier>
		<volume>47</volume>
	</reference>
	<reference name="jac02" src="bibtex:article" src-info="bibtex:line-2755" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Joseph</givenname>
				<surname>Jacobson</surname>
			</person>
			<person>
				<givenname>Barrett O.</givenname>
				<surname>Comiskey</surname>
			</person>
			<person>
				<givenname>Chris</givenname>
				<surname>Turner</surname>
			</person>
			<person>
				<givenname>Jonathan</givenname>
				<surname>Albert</surname>
			</person>
			<person>
				<givenname>Perry</givenname>
				<surname>Tsao</surname>
			</person>
		</names>
		<date value="1997"/>
		<abstract>
			<richtext>
				<p>In this paper we describe our efforts at the Massachusetts Institute of Technology Media Laboratory toward realizing an electronic book comprised of hundreds of electronically addressable display pages printed on real paper substrates. Such pages may be typeset in situ, thus giving such a book the capability to be any book. We outline the technology we are developing to bring this about and describe a number of applications that such a device enables.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1147/sj.363.0457</identifier>
		<title type="sharef:secondaryTitle">IBM Systems Journal</title>
		<number>3</number>
		<title type="sharef:primaryTitle">The Last Book</title>
		<identifier type="sharef:uri" resourceType="text/html">http://www.research.ibm.com/journal/sj/363/jacobson.html</identifier>
		<volume>36</volume>
	</reference>
	<reference name="fun02" src="bibtex:article" src-info="bibtex:line-2767" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>John E.</givenname>
				<surname>Funderbunk</surname>
			</person>
			<person>
				<givenname>Susan</givenname>
				<surname>Malaika</surname>
			</person>
			<person>
				<givenname>Berthold</givenname>
				<surname>Reinwald</surname>
			</person>
		</names>
		<date value="2002"/>
		<abstract>
			<richtext>
				<p>Most business data are stored in relational database systems, and SQL (Structured Query Language) is used for data retrieval and manipulation. With XML (Extensible Markup Language) rapidly becoming the de facto standard for retrieving and exchanging data, new functionality is expected from traditional databases. Existing SQL applications will evolve to retrieve relational data as XML data using database or SQL extensions for XML. New XML data will be stored, searched, and manipulated in the database as a "first class" citizen along with existing relational data. Furthermore, new applications will emerge that solely operate in terms of XML. These new XML applications operate on the same database using an XML query language, XQuery. In this paper, we describe an integrated database architecture that enables SQL applications with XML extensions as well as XQuery applications to operate on the same data. The architecture allows for a seamless flow from relational data to XML and back.</p>
			</richtext>
		</abstract>
		<title type="sharef:secondaryTitle">IBM Systems Journal</title>
		<number>4</number>
		<pages>642-665</pages>
		<title type="sharef:primaryTitle">XML Programming with SQL/XML and XQuery</title>
		<field type="bibtex:topic">sqlxml[0.8] xquery[0.8]</field>
		<identifier type="sharef:uri" resourceType="application/pdf">http://www.research.ibm.com/journal/sj/414/reinwald.pdf</identifier>
		<volume>41</volume>
	</reference>
	<reference name="per06" src="bibtex:article" src-info="bibtex:line-2780" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Eric</givenname>
				<surname>Perkins</surname>
			</person>
			<person>
				<givenname>Morris</givenname>
				<surname>Matsa</surname>
			</person>
			<person>
				<givenname>Margaret</givenname>
				<surname>Gaitatzes Kostoulas</surname>
			</person>
			<person>
				<givenname>Abraham</givenname>
				<surname>Heifets</surname>
			</person>
			<person>
				<givenname>Noah</givenname>
				<surname>Mendelsohn</surname>
			</person>
		</names>
		<date value="2006"/>
		<abstract>
			<richtext>
				<p>With the widespread adoption of SOAP and Web services, XML-based processing, and parsing of XML documents in particular, is becoming a performance-critical aspect of business computing. In such scenarios, XML is often constrained by an XML Schema grammar, which can be used during parsing to improve performance. Although traditional grammar-based parser generation techniques could be applied to the XML Schema grammar, the expressiveness of XML Schema does not lend itself well to the generic intermediate representations associated with these approaches. In this paper we present a method for generating efficient parsers by using the schema component model itself as the representation of the grammar. We show that the model supports the full expressive power of the XML Schema, and we present results demonstrating significant performance improvements over existing parsers.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1147/sj.452.0225</identifier>
		<title type="sharef:secondaryTitle">IBM Systems Journal</title>
		<number>2</number>
		<pages>225-244</pages>
		<title type="sharef:primaryTitle">Generation of Efficient Parsers Through Direct Compilation of XML Schema Grammars</title>
		<identifier type="sharef:uri" resourceType="text/html">http://www.research.ibm.com/journal/sj/452/perkins.html</identifier>
		<identifier type="sharef:uri" resourceType="application/pdf">http://www.research.ibm.com/journal/sj/452/perkins.pdf</identifier>
		<volume>45</volume>
	</reference>
	<reference name="rot06" src="bibtex:article" src-info="bibtex:line-2794" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Mary</givenname>
				<surname>Roth</surname>
			</person>
			<person>
				<givenname>Mauricio A.</givenname>
				<surname>Hernandez</surname>
			</person>
			<person>
				<givenname>Phil</givenname>
				<surname>Coulthard</surname>
			</person>
			<person>
				<givenname>Lingling</givenname>
				<surname>Yan</surname>
			</person>
			<person>
				<givenname>Lucian</givenname>
				<surname>Popa</surname>
			</person>
			<person>
				<givenname>Howard Ching-Tien</givenname>
				<surname>Ho</surname>
			</person>
			<person>
				<givenname>Craig C.</givenname>
				<surname>Salter</surname>
			</person>
		</names>
		<date value="2006"/>
		<abstract>
			<richtext>
				<p>Extensible Markup Language (XML) has grown rapidly over the last decade to become the de facto standard for heterogeneous data exchange. Its popularity is due in large part to the ease with which diverse kinds of information can be represented as a result of the self-describing nature and extensibility of XML itself. The ease and speed with which information can be represented does not extend, however, to exchanging such information between autonomous sources. In the absence of controlling standards, such sources will typically choose differing XML representations for the same concept, and the actual exchange of information between them requires that the representation produced by one source be transformed into a representation understood by the other. Creating this information exchange "glue" is a tedious and error-prone process, whether expressed as Extensible Stylesheet Language Transformation (XSLT), XQuery, Java, Structured Query Language (SQL), or some other format. In this paper, we present an extensible XML mapping architecture that elevates XML mapping technology to a fundamental integration component that promotes code generation, mapping reuse, and mapping as metadata.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1147/sj.452.0389</identifier>
		<title type="sharef:secondaryTitle">IBM Systems Journal</title>
		<number>2</number>
		<pages>389-409</pages>
		<title type="sharef:primaryTitle">XML Mapping Technology: Making Connections in an XML-Centric World</title>
		<identifier type="sharef:uri" resourceType="text/html">http://www.research.ibm.com/journal/sj/452/roth.html</identifier>
		<identifier type="sharef:uri" resourceType="application/pdf">http://www.research.ibm.com/journal/sj/452/roth.pdf</identifier>
		<volume>45</volume>
	</reference>
	<reference name="ros06" src="bibtex:article" src-info="bibtex:line-2808" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Kristoffer H.</givenname>
				<surname>Rose</surname>
			</person>
			<person>
				<givenname>Susan</givenname>
				<surname>Malaika</surname>
			</person>
			<person>
				<givenname>Robert J.</givenname>
				<surname>Schloss</surname>
			</person>
		</names>
		<date value="2006"/>
		<abstract>
			<richtext>
				<p>Although the Extensible Markup Language (XML) has gained in popularity and has resulted in the creation of powerful software for authoring, transforming, and querying XML-based business data, much information remains in non-XML form. In this paper we introduce an approach to virtualize data resources and thus enable applications to access both XML and non-XML sources. We describe the architectural components that enable virtual XML — a toolbox that includes a cursor model, an XML-view mechanism such as the view created with the Data Format Description Language (DFDL), and XML processing languages. We illustrate the applicability of virtual XML through a number of use cases in various environments. We discuss the products that we expect from vendors and the open-source community and the way enterprises can plan to take advantage of virtual XML developments. Finally, we outline future research directions that include a vision of virtual XML that covers large-scale structures such as entire file systems, databases, or even the World Wide Web.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1147/sj.452.0411</identifier>
		<title type="sharef:secondaryTitle">IBM Systems Journal</title>
		<number>2</number>
		<pages>411-424</pages>
		<title type="sharef:primaryTitle">Virtual XML: A Toolbox and Use Cases for the XML World View</title>
		<identifier type="sharef:uri" resourceType="text/html">http://www.research.ibm.com/journal/sj/452/rose.html</identifier>
		<identifier type="sharef:uri" resourceType="application/pdf">http://www.research.ibm.com/journal/sj/452/rose.pdf</identifier>
		<volume>45</volume>
	</reference>
	<reference name="sch92" src="bibtex:article" src-info="bibtex:line-2826" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Kjeld</givenname>
				<surname>Schmidt</surname>
			</person>
			<person>
				<givenname>Liam J.</givenname>
				<surname>Bannon</surname>
			</person>
		</names>
		<date value="1992"/>
		<abstract>
			<richtext>
				<p>The topic of Computer Supported Cooperative Work (CSCW) has attracted much attention in the last few years. While the field is obviously still in the process of development, there is a marked ambiguity about the exact focus of the field. This lack of focus may hinder its further development and lead to its dissipation. In this paper we set out an approach to CSCW as a field of research which we believe provides a coherent conceptual framework for this area, suggesting that it should be concerned with the support requirements of cooperative work arrangements. This provides a more principled, comprehensive, and, in our opinion, more useful conception of the field than that provided by the conception of CSCW as being focused on computer support for groups. We then investigate the consequences of taking this alternative conception seriously, in terms of research directions for the field. As an indication of the fruits of this approach, we discuss the concept of 'articulation work' and its relevance to CSCW. This raises a host of interesting problems that are marginalized in the work on small group support but critical to the success of CSCW systems 'in the large', i. e., that are designed to meet current work requirements in the everyday world.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:isbn">09259724</identifier>
		<title type="sharef:secondaryTitle">Computer Supported Cooperative Work</title>
		<number>1–2</number>
		<pages>7-40</pages>
		<title type="sharef:primaryTitle">Taking CSCW Seriously: Supporting Articulation Work</title>
		<field type="bibtex:topic">cscw[0.8]</field>
		<identifier type="sharef:uri" resourceType="application/pdf">http://www.itu.dk/people/schmidt/papers/cscw_seriously.pdf</identifier>
		<volume>1</volume>
	</reference>
	<reference name="rod92" src="bibtex:article" src-info="bibtex:line-2840" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Tom A.</givenname>
				<surname>Rodden</surname>
			</person>
			<person>
				<givenname>J. A.</givenname>
				<surname>Mariani</surname>
			</person>
			<person>
				<givenname>Gordon S.</givenname>
				<surname>Blair</surname>
			</person>
		</names>
		<date value="1992"/>
		<field type="bibtex:index">cooperative applications, database technology, distributed systems, groupware, systems support</field>
		<identifier type="sharef:isbn">09259724</identifier>
		<title type="sharef:secondaryTitle">Computer Supported Cooperative Work</title>
		<number>1–2</number>
		<pages>41-67</pages>
		<title type="sharef:primaryTitle">Supporting Cooperative Applications</title>
		<volume>1</volume>
	</reference>
	<reference name="koc96" src="bibtex:article" src-info="bibtex:line-2852" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Michael</givenname>
				<surname>Koch</surname>
			</person>
		</names>
		<date value="1996"/>
		<field type="bibtex:index">IRIS, groupware, collaborative editing</field>
		<identifier type="sharef:isbn">09259724</identifier>
		<title type="sharef:secondaryTitle">Computer Supported Cooperative Work</title>
		<number>1</number>
		<pages>359-378</pages>
		<title type="sharef:primaryTitle">Design Issues and Model for a Distributed Multi-User Editor</title>
		<volume>5</volume>
	</reference>
	<reference name="wag74" src="bibtex:article" src-info="bibtex:line-2868" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Robert A.</givenname>
				<surname>Wagner</surname>
			</person>
			<person>
				<givenname>Michael J.</givenname>
				<surname>Fischer</surname>
			</person>
		</names>
		<date value="1974-01"/>
		<abstract>
			<richtext>
				<p>The string-to-string correction problem is to determine the distance between two strings as measured by the minimum cost sequence of "edit operations" needed to change the one string into the other. The edit operations investigated allow changing one symbol of a string into another single symbol, deleting one symbol from a string, or inserting a single symbol into a string. An algorithm is presented which solves this problem in time proportional to the product of the lengths of the two strings. Possible applications are to the problems of automatic spelling correction and determining the longest subsequence of characters common to two strings.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/321796.321811</identifier>
		<title type="sharef:secondaryTitle">Journal of the ACM</title>
		<number>1</number>
		<pages>168-173</pages>
		<title type="sharef:primaryTitle">The String-to-String Correction Problem</title>
		<volume>21</volume>
	</reference>
	<reference name="wag75" src="bibtex:article" src-info="bibtex:line-2881" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Robert A.</givenname>
				<surname>Wagner</surname>
			</person>
			<person>
				<givenname>Roy</givenname>
				<surname>Lowrance</surname>
			</person>
		</names>
		<date value="1975-04"/>
		<identifier type="sharef:doi">10.1145/321879.321880</identifier>
		<title type="sharef:secondaryTitle">Journal of the ACM</title>
		<number>2</number>
		<pages>177-183</pages>
		<title type="sharef:primaryTitle">An Extension of the String-to-String Correction Problem</title>
		<volume>22</volume>
	</reference>
	<reference name="tai79" src="bibtex:article" src-info="bibtex:line-2893" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Kuo-Chung</givenname>
				<surname>Tai</surname>
			</person>
		</names>
		<date value="1979-07"/>
		<identifier type="sharef:doi">10.1145/322139.322143</identifier>
		<title type="sharef:secondaryTitle">Journal of the ACM</title>
		<number>3</number>
		<pages>422-433</pages>
		<title type="sharef:primaryTitle">The Tree-to-Tree Correction Problem</title>
		<volume>26</volume>
	</reference>
	<reference name="got05" src="bibtex:article" src-info="bibtex:line-2905" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Georg</givenname>
				<surname>Gottlob</surname>
			</person>
			<person>
				<givenname>Christoph</givenname>
				<surname>Koch</surname>
			</person>
			<person>
				<givenname>Reinhard</givenname>
				<surname>Pichler</surname>
			</person>
			<person>
				<givenname>Luc</givenname>
				<surname>Segoufin</surname>
			</person>
		</names>
		<date value="2005-03"/>
		<abstract>
			<richtext>
				<p>We study the complexity of two central XML processing problems. The first is XPath 1.0 query processing, which has been shown to be in PTIME in previous work. We prove that both the data complexity and the query complexity of XPath 1.0 fall into lower (highly parallelizable) complexity classes, while the combined complexity is PTIME-hard. Subsequently, we study the sources of this hardness and identify a large and practically important fragment of XPath 1.0 for which the combined complexity is LOGCFL-complete and, therefore, in the highly parallelizable complexity class NC2. The second problem is the complexity of validating XML documents against various typing schemes like Document Type Definitions (DTDs), XML Schema Definitions (XSDs), and tree automata, both with respect to data and to combined complexity. For data complexity, we prove that validation is in LOGSPACE and depends crucially on how XML data is represented. For the combined complexity, we show that the complexity ranges from LOGSPACE to LOGCFL, depending on the typing scheme.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/1059513.1059520</identifier>
		<title type="sharef:secondaryTitle">Journal of the ACM</title>
		<number>2</number>
		<pages>284-335</pages>
		<title type="sharef:primaryTitle">The Complexity of XPath Query Evaluation and XML Typing</title>
		<field type="bibtex:topic">xpath1[0.7] xsd[0.7] dtd[0.7]</field>
		<identifier type="sharef:uri">http://portal.acm.org/citation.cfm?id=1059513.1059520</identifier>
		<identifier type="sharef:uri" resourceType="application/pdf">ftp://ftp.inria.fr/INRIA/Projects/verso/gemo/GemoReport-373.pdf</identifier>
		<volume>52</volume>
	</reference>
	<reference name="nev02a" src="bibtex:article" src-info="bibtex:line-2921" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Frank</givenname>
				<surname>Neven</surname>
			</person>
			<person>
				<givenname>Jan</givenname>
				<surname>Van den Bussche</surname>
			</person>
		</names>
		<date value="2002-01"/>
		<abstract>
			<richtext>
				<p>Structured document databases can be naturally viewed as derivation trees of a context-free grammar. Under this view, the classical formalism of attribute grammars becomes a formalism for structured document query languages. From this perspective, we study the expressive power of BAGs: Boolean-valued attribute grammars with propositional logic formulas as semantic rules, and RAGs: relation-valued attribute grammars with first-order logic formulas as semantic rules. BAGs can express only unary queries; RAGs can express queries of any arity. We first show that the (unary) queries expressible by BAGs are precisely those definable in monadic second-order logic. We then show that the queries expressible by RAGs are precisely those definable by first-order inductions of linear depth, or, equivalently, those computable in linear time on a parallel machine with polynomially many processors. Further, we show that RAGs that only use synthesized attributes are strictly weaker than RAGs that use both synthesized and inherited attributes. We show that RAGs are more expressive than monadic second-order logic for queries of any arity. Finally, we discuss relational attribute grammars in the context of BAGs and RAGs. We show that in the case of BAGs this does not increase the expressive power, while different semantics for relational RAGs capture the complexity classes NP, coNP and the intersection of UP and coUP.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/505241.505245</identifier>
		<title type="sharef:secondaryTitle">Journal of the ACM</title>
		<number>1</number>
		<pages>56-100</pages>
		<title type="sharef:primaryTitle">Expressiveness of Structured Document Query Languages Based on Attribute Grammars</title>
		<field type="bibtex:topic">xml[0.8]</field>
		<identifier type="sharef:uri">http://portal.acm.org/citation.cfm?id=505245</identifier>
		<volume>49</volume>
	</reference>
	<reference name="koe04" src="bibtex:article" src-info="bibtex:line-2940" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Rob H.</givenname>
				<surname>Koenen</surname>
			</person>
			<person>
				<givenname>Jack</givenname>
				<surname>Lacy</surname>
			</person>
			<person>
				<givenname>Michael</givenname>
				<surname>MacKay</surname>
			</person>
			<person>
				<givenname>Steve</givenname>
				<surname>Mitchell</surname>
			</person>
		</names>
		<date value="2004-06"/>
		<abstract>
			<richtext>
				<p>This paper discusses interoperability of digital rights management (DRM) systems. We start by describing a basic reference model for DRM. The cause of interoperability is served by understanding and circumscribing what DRM is "in the whole." Then we outline and contrast three different approaches to achieving interoperability. One approach relies on flexible network services to provide functionality where it is needed, perhaps by bridging different systems. We describe an experimental service orchestration system (NEMO) that enables such an approach.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1109/JPROC.2004.827357</identifier>
		<title type="sharef:secondaryTitle">IEEE</title>
		<number>6</number>
		<pages>883-897</pages>
		<title type="sharef:primaryTitle">The Long March to Interoperable Digital Rights Management</title>
		<field type="bibtex:topic">drm[1]</field>
		<identifier type="sharef:uri" resourceType="application/pdf">http://www.intertrust.com/main/research/whitepapers/Interoperable_DRM.pdf</identifier>
		<volume>92</volume>
	</reference>
	<reference name="dav11" src="bibtex:article" src-info="bibtex:line-2959" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Stephen</givenname>
				<surname>Davies</surname>
			</person>
		</names>
		<date value="2011-02"/>
		<abstract>
			<richtext>
				<p>What would it take for a true personal knowledge base to generate the benefits envisioned by Vannevar Bush?</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/1897816.1897840</identifier>
		<title type="sharef:secondaryTitle">Communications of the ACM</title>
		<number>2</number>
		<pages>80-88</pages>
		<title type="sharef:primaryTitle">Still Building the Memex</title>
		<identifier type="sharef:uri">http://cacm.acm.org/magazines/2011/2/104378-still-building-the-memex</identifier>
		<volume>54</volume>
	</reference>
	<reference name="caf11" src="bibtex:article" src-info="bibtex:line-2973" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Michael J.</givenname>
				<surname>Cafarella</surname>
			</person>
			<person>
				<givenname>Alon</givenname>
				<surname>Halevy</surname>
			</person>
			<person>
				<givenname>Jayant</givenname>
				<surname>Madhavan</surname>
			</person>
		</names>
		<date value="2011-02"/>
		<abstract>
			<richtext>
				<p>Though the web is best known as a vast repository of shared documents, it also contains a significant amount of structured data covering a complete range of topics, from product to financial, public-record, scientific, hobby-related, and government. Structured data on the Web shares many similarities with the kind of data traditionally managed by commercial database systems but also reflects some unusual characteristics of its own; for example, it is embedded in textual Web pages and must be extracted prior to use; there is no centralized data design as there is in a traditional database; and, unlike traditional databases that focus on a single domain, it covers everything. Existing data-management systems do not address these challenges and assume their data is modeled within a well-defined domain.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/1897816.1897839</identifier>
		<title type="sharef:secondaryTitle">Communications of the ACM</title>
		<number>2</number>
		<pages>72-79</pages>
		<title type="sharef:primaryTitle">Structured Data on the Web</title>
		<identifier type="sharef:uri">http://cacm.acm.org/magazines/2011/2/104398-structured-data-on-the-web</identifier>
		<volume>54</volume>
	</reference>
	<reference name="jun08" src="bibtex:article" src-info="bibtex:line-2987" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Iris A.</givenname>
				<surname>Junglas</surname>
			</person>
			<person>
				<givenname>Richard T.</givenname>
				<surname>Watson</surname>
			</person>
		</names>
		<date value="2008-03"/>
		<identifier type="sharef:doi">10.1145/1325555.1325568</identifier>
		<title type="sharef:secondaryTitle">Communications of the ACM</title>
		<number>3</number>
		<pages>65-69</pages>
		<title type="sharef:primaryTitle">Location-Based Services</title>
		<volume>51</volume>
	</reference>
	<reference name="wri09" src="bibtex:article" src-info="bibtex:line-2999" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Alex</givenname>
				<surname>Wright</surname>
			</person>
		</names>
		<date value="2009-12"/>
		<abstract>
			<richtext>
				<p>Back in 1995, Netscape co-founder Marc Andreessen predicted that his fledgling Web browser would one day render Windows obsolete. Fifteen years later, Netscape is long gone, and the traditional desktop operating system (OS) remains firmly established on most personal computers. Meanwhile, Web browsers still look a lot like they did in the mid-1990s, running inside application windows. In hindsight, Andreessen may have spoken a bit too soon. But history may yet prove him right.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/1610252.1610260</identifier>
		<title type="sharef:secondaryTitle">Communications of the ACM</title>
		<number>12</number>
		<pages>16-17</pages>
		<title type="sharef:primaryTitle">Ready for a Web OS?</title>
		<identifier type="sharef:uri">http://cacm.acm.org/magazines/2009/12/52829-ready-for-a-web-os/fulltext</identifier>
		<volume>52</volume>
	</reference>
	<reference name="dif09" src="bibtex:article" src-info="bibtex:line-3013" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Whitfield</givenname>
				<surname>Diffie</surname>
			</person>
			<person>
				<givenname>Susan</givenname>
				<surname>Landau</surname>
			</person>
		</names>
		<date value="2009-11"/>
		<abstract>
			<richtext>
				<p>We all know the scene: It is the basement of an apartment building and the lights are dim. The man is wearing a trench coat and a fedora pulled down low to hide his face. Between the hat and the coat we see headphones, and he appears to be listening intently to the output of a set of alligator clips attached to a phone line. He is a detective eavesdropping on a suspect's phone calls. This is wiretapping — as it was in the film noir era of 1930s Hollywood. It doesn't have much to do with modern electronic eavesdropping, which is about bits, packets, switches, and routers.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/1592761.1592776</identifier>
		<title type="sharef:secondaryTitle">Communications of the ACM</title>
		<number>11</number>
		<pages>42-47</pages>
		<title type="sharef:primaryTitle">Communications Surveillance: Privacy and Security at Risk</title>
		<identifier type="sharef:uri">http://cacm.acm.org/magazines/2009/11/48445-communications-surveillance-privacy-and-security-at-risk/fulltext</identifier>
		<volume>52</volume>
	</reference>
	<reference name="fos08" src="bibtex:article" src-info="bibtex:line-3027" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Ian</givenname>
				<surname>Foster</surname>
			</person>
			<person>
				<givenname>Savas</givenname>
				<surname>Parastatidis</surname>
			</person>
			<person>
				<givenname>Paul</givenname>
				<surname>Watson</surname>
			</person>
			<person>
				<givenname>Mark</givenname>
				<surname>McKeown</surname>
			</person>
		</names>
		<date value="2008-09"/>
		<abstract>
			<richtext>
				<p>Many Web sites embed third-party content in frames, relying on the browser's security policy to protect against malicious content. However, frames provide insufficient isolation in browsers that let framed content navigate other frames. We evaluate existing frame navigation policies and advocate a stricter policy, which we deploy in the open-source browsers. In addition to preventing undesirable interactions, the browser's strict isolation policy also affects communication between cooperating frames. We therefore analyze two techniques for interframe communication between isolated frames. The first method, fragment identifier messaging, initially provides confidentiality without authentication, which we repair using concepts from a well-known network protocol. The second method, postMessage, initially provides authentication, but we discover an attack that breaches confidentiality. We propose improvements in the postMessage API to provide confidentiality; our proposal has been standardized and adopted in browser implementations.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/1378727.1378739</identifier>
		<title type="sharef:secondaryTitle">Communications of the ACM</title>
		<number>9</number>
		<pages>34-41</pages>
		<title type="sharef:primaryTitle">How Do I Model State? Let Me Count the Ways</title>
		<identifier type="sharef:uri">http://cacm.acm.org/magazines/2008/9/5323-how-do-i-model-state/fulltext</identifier>
		<volume>51</volume>
	</reference>
	<reference name="bar09" src="bibtex:article" src-info="bibtex:line-3041" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Adam</givenname>
				<surname>Barth</surname>
			</person>
			<person>
				<givenname>Collin</givenname>
				<surname>Jackson</surname>
			</person>
			<person>
				<givenname>John C.</givenname>
				<surname>Mitchell</surname>
			</person>
		</names>
		<date value="2009-06"/>
		<abstract>
			<richtext>
				<p>Many Web sites embed third-party content in frames, relying on the browser's security policy to protect against malicious content. However, frames provide insufficient isolation in browsers that let framed content navigate other frames. We evaluate existing frame navigation policies and advocate a stricter policy, which we deploy in the open-source browsers. In addition to preventing undesirable interactions, the browser's strict isolation policy also affects communication between cooperating frames. We therefore analyze two techniques for interframe communication between isolated frames. The first method, fragment identifier messaging, initially provides confidentiality without authentication, which we repair using concepts from a well-known network protocol. The second method, postMessage, initially provides authentication, but we discover an attack that breaches confidentiality. We propose improvements in the postMessage API to provide confidentiality; our proposal has been standardized and adopted in browser implementations.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/1516046.1516066</identifier>
		<title type="sharef:secondaryTitle">Communications of the ACM</title>
		<number>6</number>
		<pages>83-91</pages>
		<title type="sharef:primaryTitle">Securing Frame Communication in Browsers</title>
		<identifier type="sharef:uri">http://cacm.acm.org/magazines/2009/6/28500-securing-frame-communication-in-browsers/fulltext</identifier>
		<volume>52</volume>
	</reference>
	<reference name="sou08" src="bibtex:article" src-info="bibtex:line-3055" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Steve</givenname>
				<surname>Souders</surname>
			</person>
		</names>
		<date value="2008">12 2008</date>
		<abstract>
			<richtext>
				<p>Google Maps, Yahoo! Mail, Facebook, MySpace, YouTube, and Amazon are examples of Web sites built to scale. They access petabytes of data sending terabits per second to millions of users worldwide. The magnitude is awe-inspiring. Users view these large-scale Web sites from a narrower perspective. The typical user has megabytes of data that they download at a few hundred kilobits per second. Users are less interested in the massive number of requests per second being served, caring more about their individual requests. As they use these Web applications they inevitably ask the same question: "Why is this site so slow?" The answer hinges on where development teams focus their performance improvements. Performance for the sake of scalability is rightly focused on the backend. Database tuning, replicating architectures, customized data caching, and so on, allow Web servers to handle a greater number of requests. This gain in efficiency translates into reductions in hardware costs, data center rack space, and power consumption. But how much does the backend affect the user experience in terms of latency? The Web applications listed here are some of the most highly tuned in the world, and yet they still take longer to load than we'd like. It almost seems as if the high-speed storage and optimized application code on the backend have little impact on the end user's response time. Therefore, to account for these slowly loading pages we must focus on something other than the backend: we must focus on the frontend.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/1409360.1409374</identifier>
		<title type="sharef:secondaryTitle">Communications of the ACM</title>
		<number>12</number>
		<pages>36-41</pages>
		<title type="sharef:primaryTitle">High-Performance Web Sites</title>
		<volume>51</volume>
	</reference>
	<reference name="fis04b" src="bibtex:article" src-info="bibtex:line-3068" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>G.</givenname>
				<surname>Fischer</surname>
			</person>
			<person>
				<givenname>E.</givenname>
				<surname>Giaccardi</surname>
			</person>
			<person>
				<givenname>Y.</givenname>
				<surname>Ye</surname>
			</person>
			<person>
				<givenname>A. G.</givenname>
				<surname>Sutcliffe</surname>
			</person>
			<person>
				<givenname>N.</givenname>
				<surname>Mehandjiev</surname>
			</person>
		</names>
		<date value="2004-09"/>
		<abstract>
			<richtext>
				<p>End-user development (EUD) activities range from customization to component configuration and programming. Office software, such as the ubiquitous spreadsheet, provides customization facilities, while the growth of the Web has added impetus to end-user scripting for interactive functions in Web sites. In scientific and engineering domains, end users frequently develop complex systems with standard programming languages such as C++ and Java. However, only a minority of users adapt commercial off-the-shelf (COTS) software products. Indeed, composing systems from reusable components, such as enterprise resource planing (ERP) systems, defeats most end users who resort to expensive and scarce expert developers for implementation.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/1015864.1015884</identifier>
		<title type="sharef:secondaryTitle">Communications of the ACM</title>
		<number>9</number>
		<pages>33-37</pages>
		<title type="sharef:primaryTitle">Meta-Design: A Manifesto for End-User Development</title>
		<volume>47</volume>
	</reference>
	<reference name="heb07" src="bibtex:article" src-info="bibtex:line-3081" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Bin</givenname>
				<surname>He</surname>
			</person>
			<person>
				<givenname>Mitesh</givenname>
				<surname>Patel</surname>
			</person>
			<person>
				<givenname>Zhen</givenname>
				<surname>Zhang</surname>
			</person>
			<person>
				<givenname>Kevin Chen-Chuan</givenname>
				<surname>Chang</surname>
			</person>
		</names>
		<date value="2007-05"/>
		<identifier type="sharef:doi">10.1145/1230819.1241670</identifier>
		<title type="sharef:secondaryTitle">Communications of the ACM</title>
		<number>5</number>
		<pages>94-101</pages>
		<title type="sharef:primaryTitle">Accessing the Deep Web</title>
		<volume>50</volume>
	</reference>
	<reference name="che06b" src="bibtex:article" src-info="bibtex:line-3093" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Henry</givenname>
				<surname>Chesbrough</surname>
			</person>
			<person>
				<givenname>Jim</givenname>
				<surname>Spohrer</surname>
			</person>
		</names>
		<date value="2006-07"/>
		<abstract>
			<richtext>
				<p>The services sector has grown over the last 50 years to dominate economic activity in most advanced industrial economies, yet scientific understanding of modern services is rudimentary. Here, we argue for a services science discipline to integrate across academic silos and advance service innovation more rapidly.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/1139922.1139945</identifier>
		<title type="sharef:secondaryTitle">Communications of the ACM</title>
		<number>7</number>
		<pages>35-40</pages>
		<title type="sharef:primaryTitle">A Research Manifesto for Services Science</title>
		<volume>49</volume>
	</reference>
	<reference name="mag06" src="bibtex:article" src-info="bibtex:line-3106" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Paul P.</givenname>
				<surname>Maglio</surname>
			</person>
			<person>
				<givenname>Savitha</givenname>
				<surname>Srinivasan</surname>
			</person>
			<person>
				<givenname>Jeffrey T.</givenname>
				<surname>Kreulen</surname>
			</person>
			<person>
				<givenname>Jim</givenname>
				<surname>Spohrer</surname>
			</person>
		</names>
		<date value="2006-07"/>
		<abstract>
			<richtext>
				<p>Computer scientists work with formal models of algorithms and computation, and someday service scientists may work with formal models of service systems. The four examples here document some of the early efforts to establish a new academic discipline and new profession.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/1139922.1139955</identifier>
		<title type="sharef:secondaryTitle">Communications of the ACM</title>
		<number>7</number>
		<pages>81-85</pages>
		<title type="sharef:primaryTitle">Service Systems, Service Scientists, SSME, and Innovation</title>
		<volume>49</volume>
	</reference>
	<reference name="hen08c" src="bibtex:article" src-info="bibtex:line-3119" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Michi</givenname>
				<surname>Henning</surname>
			</person>
		</names>
		<date value="2008-08"/>
		<identifier type="sharef:doi">10.1145/1378704.1378718</identifier>
		<title type="sharef:secondaryTitle">Communications of the ACM</title>
		<number>8</number>
		<pages>52-57</pages>
		<title type="sharef:primaryTitle">The Rise and Fall of CORBA</title>
		<field type="bibtex:topic">corba[0.8]</field>
		<volume>51</volume>
	</reference>
	<reference name="wil08j" src="bibtex:article" src-info="bibtex:line-3132" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Erik</givenname>
				<surname>Wilde</surname>
			</person>
			<person>
				<givenname>Robert J.</givenname>
				<surname>Glushko</surname>
			</person>
		</names>
		<date value="2008-07"/>
		<abstract>
			<richtext>
				<p>The Extensible Markup Language (XML), which just celebrated its 10th birthday, is one of the big success stories of the Web. Apart from basic Web technologies (URIs, HTTP, and HTML) and the advanced scripting driving the Web 2.0 wave, XML is by far the most successful and ubiquitous Web technology. With great power, however, comes great responsibility, so while XML's success is well earned as the first truly universal standard for structured data, it must now deal with numerous problems that have grown up around it. These are not entirely the fault of XML itself, but instead can be attributed to exaggerated claims and ideas of what XML is and what it can do.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/1364782.1364795</identifier>
		<title type="sharef:secondaryTitle">Communications of the ACM</title>
		<number>7</number>
		<pages>40-46</pages>
		<title type="sharef:primaryTitle">XML Fever</title>
		<field type="bibtex:topic">xml[0.8]</field>
		<identifier type="sharef:uri">http://dret.net/netdret/publications#wil08j</identifier>
		<identifier type="sharef:uri">http://cacm.acm.org/magazines/2008/7/5363-xml-fever/fulltext</identifier>
		<volume>51</volume>
	</reference>
	<reference name="wil08m" src="bibtex:article" src-info="bibtex:line-3148" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Erik</givenname>
				<surname>Wilde</surname>
			</person>
			<person>
				<givenname>Robert J.</givenname>
				<surname>Glushko</surname>
			</person>
		</names>
		<date value="2008-10"/>
		<abstract>
			<richtext>
				<p>The classical approach to the data aspect of system design distinguishes conceptual, logical, and physical models. Models of each type or level are governed by metamodels that specify the kinds of concepts and constraints that can be used by each model; in most cases metamodels are accompanied by languages for describing models. For example, in database design, conceptual models usually conform to the Entity-Relationship (ER) metamodel (or some extension of it), the logical model maps ER models to relational tables and introduces normalization, and the physical model handles implementation issues such as possible denormalizations in the context of a particular database schema language. In this modeling methodology, there is a single hierarchy of models that rests on the assumption that one data model spans all modeling levels and applies to all the applications in some domain. The "one true model" approach assumes homogeneity, but this does not work very well for the Web. The Web as a constantly growing ecosystem of heterogeneous data and services has challenged a number of practices and theories about the design of IT landscapes. Instead of being governed by "one true model" used by everyone, the underlying assumption of top-down design, Web data and services evolve in an uncoordinated fashion. As a result, a fundamental challenge with Web data and services is matching and mapping local and often partial models that not only are different models of the same application domain, but also differ, implicitly or explicitly, in their associated metamodels.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/1400181.1400195</identifier>
		<title type="sharef:secondaryTitle">Communications of the ACM</title>
		<number>10</number>
		<pages>43-49</pages>
		<title type="sharef:primaryTitle">Document Design Matters</title>
		<field type="bibtex:topic">xml[0.8]</field>
		<identifier type="sharef:uri">http://dret.net/netdret/publications#wil08m</identifier>
		<identifier type="sharef:uri">http://cacm.acm.org/magazines/2008/10/521-document-design-matters/fulltext</identifier>
		<volume>51</volume>
	</reference>
	<reference name="hen08" src="bibtex:article" src-info="bibtex:line-3164" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>James A.</givenname>
				<surname>Hendler</surname>
			</person>
			<person>
				<givenname>Nigel</givenname>
				<surname>Shadbolt</surname>
			</person>
			<person>
				<givenname>Wendy</givenname>
				<surname>Hall</surname>
			</person>
			<person>
				<givenname>Tim</givenname>
				<surname>Berners-Lee</surname>
			</person>
			<person>
				<givenname>Daniel J.</givenname>
				<surname>Weitzner</surname>
			</person>
		</names>
		<date value="2008-07"/>
		<identifier type="sharef:doi">10.1145/1364782.1364798</identifier>
		<title type="sharef:secondaryTitle">Communications of the ACM</title>
		<number>7</number>
		<pages>80-89</pages>
		<title type="sharef:primaryTitle">Web Science: An Interdisciplinary Approach to Understanding the Web</title>
		<volume>51</volume>
	</reference>
	<reference name="ber94" src="bibtex:article" src-info="bibtex:line-3176" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Tim</givenname>
				<surname>Berners-Lee</surname>
			</person>
			<person>
				<givenname>Robert</givenname>
				<surname>Cailliau</surname>
			</person>
			<person>
				<givenname>Ari</givenname>
				<surname>Luotonen</surname>
			</person>
			<person>
				<givenname>Henrik</givenname>
				<surname>Frystyk Nielsen</surname>
			</person>
			<person>
				<givenname>Arthur</givenname>
				<surname>Secret</surname>
			</person>
		</names>
		<date value="1994-08"/>
		<identifier type="sharef:doi">10.1145/179606.179671</identifier>
		<title type="sharef:secondaryTitle">Communications of the ACM</title>
		<number>8</number>
		<pages>76-82</pages>
		<title type="sharef:primaryTitle">The World Wide Web</title>
		<volume>37</volume>
	</reference>
	<reference name="mul03" src="bibtex:article" src-info="bibtex:line-3188" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Deirdre K.</givenname>
				<surname>Mulligan</surname>
			</person>
		</names>
		<date value="2003-04"/>
		<abstract>
			<richtext>
				<p>The fair-use exceptions in U.S. copyright law are being undermined by rules programmed into consumer electronics and computers that reflect the exclusive interest of rights holders alone.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/641205.641227</identifier>
		<title type="sharef:secondaryTitle">Communications of the ACM</title>
		<number>4</number>
		<pages>30-33</pages>
		<title type="sharef:primaryTitle">Digital Rights Management and Fair Use by Design</title>
		<field type="bibtex:topic">drm[0.9]</field>
		<volume>46</volume>
	</reference>
	<reference name="pol07" src="bibtex:article" src-info="bibtex:line-3202" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Irene</givenname>
				<surname>Pollach</surname>
			</person>
		</names>
		<date value="2007-09"/>
		<abstract>
			<richtext>
				<p>Research has shown that privacy policies tend to intensify privacy concerns rather than engender trust. One way to combat this dichotomy is to redesign their content, language, and presentation format.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/1284621.1284627</identifier>
		<title type="sharef:secondaryTitle">Communications of the ACM</title>
		<number>9</number>
		<pages>103-108</pages>
		<title type="sharef:primaryTitle">What's Wrong With Online Privacy Policies?</title>
		<volume>50</volume>
	</reference>
	<reference name="hea02" src="bibtex:article" src-info="bibtex:line-3215" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Marti A.</givenname>
				<surname>Hearst</surname>
			</person>
			<person>
				<givenname>Ame</givenname>
				<surname>Elliott</surname>
			</person>
			<person>
				<givenname>Jennifer</givenname>
				<surname>English</surname>
			</person>
			<person>
				<givenname>Rashmi R.</givenname>
				<surname>Sinha</surname>
			</person>
			<person>
				<givenname>Kirsten</givenname>
				<surname>Swearingen</surname>
			</person>
			<person>
				<givenname>Ka-Ping</givenname>
				<surname>Yee</surname>
			</person>
		</names>
		<date value="2002-09"/>
		<identifier type="sharef:doi">10.1145/567498.567525</identifier>
		<title type="sharef:secondaryTitle">Communications of the ACM</title>
		<number>9</number>
		<pages>42-49</pages>
		<title type="sharef:primaryTitle">Finding the Flow in Web Site Search</title>
		<volume>45</volume>
	</reference>
	<reference name="hea06" src="bibtex:article" src-info="bibtex:line-3227" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Marti A.</givenname>
				<surname>Hearst</surname>
			</person>
		</names>
		<date value="2006-04"/>
		<title type="sharef:secondaryTitle">Communications of the ACM</title>
		<number>4</number>
		<pages>59-61</pages>
		<title type="sharef:primaryTitle">Clustering versus Faceted Categories for Information Exploration</title>
		<identifier type="sharef:uri" resourceType="application/pdf">http://people.ischool.berkeley.edu/~hearst/papers/cacm06.pdf</identifier>
		<volume>49</volume>
	</reference>
	<reference name="coh03" src="bibtex:article" src-info="bibtex:line-3239" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Julie E.</givenname>
				<surname>Cohen</surname>
			</person>
		</names>
		<date value="2003-04"/>
		<identifier type="sharef:doi">10.1145/641205.641230</identifier>
		<title type="sharef:secondaryTitle">Communications of the ACM</title>
		<number>4</number>
		<pages>47-49</pages>
		<title type="sharef:primaryTitle">DRM and Privacy</title>
		<field type="bibtex:topic">drm[0.9]</field>
		<identifier type="sharef:uri" resourceType="application/pdf">http://www.law.georgetown.edu/Faculty/jec/CommACMdrm.pdf</identifier>
		<volume>46</volume>
	</reference>
	<reference name="tho68" src="bibtex:article" src-info="bibtex:line-3253" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Ken</givenname>
				<surname>Thompson</surname>
			</person>
		</names>
		<date value="1968-06"/>
		<abstract>
			<richtext>
				<p>A method for locating specific character strings embedded in character text is described and an implementation of this method in the form of a compiler is discussed. The compiler accepts a regular expression as source language and produces an IBM 7094 program as object language. The object program then accepts the text to be searched as input and produces a signal every time an embedded string in the text matches the given regular expression. Examples, problems, and solutions are also presented.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/363347.363387</identifier>
		<title type="sharef:secondaryTitle">Communications of the ACM</title>
		<number>6</number>
		<pages>419-422</pages>
		<title type="sharef:primaryTitle">Programming Techniques: Regular Expression Search Algorithm</title>
		<field type="bibtex:topic">regex[0.9]</field>
		<volume>11</volume>
	</reference>
	<reference name="len95" src="bibtex:article" src-info="bibtex:line-3267" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Doug</givenname>
				<surname>Lenat</surname>
			</person>
			<person>
				<givenname>George A.</givenname>
				<surname>Miller</surname>
			</person>
			<person>
				<givenname>Toshio</givenname>
				<surname>Yokoi</surname>
			</person>
		</names>
		<date value="1995-11"/>
		<abstract>
			<richtext>
				<p>I applaud Miller's WordNet project and feel that there is much in common in our approaches, even though there are fundamental differences in the two expressions of that spirit. Here, I list the four differences I noted, closing with a crucial observation concerning the common spirit in our work.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/219717.219757</identifier>
		<title type="sharef:secondaryTitle">Communications of the ACM</title>
		<number>11</number>
		<pages>45-48</pages>
		<title type="sharef:primaryTitle">CYC, WordNet, and EDR: Critiques and Responses</title>
		<volume>38</volume>
	</reference>
	<reference name="sch00d" src="bibtex:article" src-info="bibtex:line-3280" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Ben</givenname>
				<surname>Shneiderman</surname>
			</person>
		</names>
		<date value="2000-05"/>
		<identifier type="sharef:doi">10.1145/332833.332843</identifier>
		<title type="sharef:secondaryTitle">Communications of the ACM</title>
		<number>5</number>
		<pages>84-91</pages>
		<title type="sharef:primaryTitle">Universal Usability</title>
		<volume>43</volume>
	</reference>
	<reference name="rao03" src="bibtex:article" src-info="bibtex:line-3292" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Bharat</givenname>
				<surname>Rao</surname>
			</person>
			<person>
				<givenname>Louis</givenname>
				<surname>Minakakis</surname>
			</person>
		</names>
		<date value="2003-12"/>
		<identifier type="sharef:doi">10.1145/953460.953490</identifier>
		<title type="sharef:secondaryTitle">Communications of the ACM</title>
		<number>12</number>
		<pages>61-65</pages>
		<title type="sharef:primaryTitle">Evolution of Mobile Location-Based Services</title>
		<identifier type="sharef:uri">http://portal.acm.org/citation.cfm?doid=953460.953490</identifier>
		<volume>46</volume>
	</reference>
	<reference name="glu99" src="bibtex:article" src-info="bibtex:line-3305" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Robert J.</givenname>
				<surname>Glushko</surname>
			</person>
			<person>
				<givenname>Jay M.</givenname>
				<surname>Tenenbaum</surname>
			</person>
			<person>
				<givenname>Bart</givenname>
				<surname>Meltzer</surname>
			</person>
		</names>
		<date value="1999-03"/>
		<abstract>
			<richtext>
				<p>CommerceNet's eCo System initiative, launched in 1996, aims to transform the World-Wide Web into an agent-based infrastructure for Internet commerce. Today's Web gives people unprecedented access to online information and services. But its information is delivered in format-oriented, handcrafted Hypertext Markup Language (HTML), making it understandable only through human eyes. Software agents and search engines have difficulty using the information because it is not semantically encoded. Clever programmers work around some of HTML's inherent limitations by using proprietary tags or software that "scrapes" Web pages to extract content. Unfortunately, such ad hoc approaches do not scale. Proprietary tags require browser plug-ins, and scraping approaches require a customized script for each Web site. These approaches balkanize the Web, making it inaccessible to agents.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/295685.295720</identifier>
		<title type="sharef:secondaryTitle">Communications of the ACM</title>
		<number>3</number>
		<pages>106-114</pages>
		<title type="sharef:primaryTitle">An XML Framework for Agent-Based E-Commerce</title>
		<identifier type="sharef:uri">http://portal.acm.org/citation.cfm?id=295720&amp;dl=ACM&amp;coll=GUIDE</identifier>
		<identifier type="sharef:uri" resourceType="application/pdf">http://www.ischool.berkeley.edu/~glushko/glushko_files/glushko_acm_framework.pdf</identifier>
		<volume>42</volume>
	</reference>
	<reference name="kum04" src="bibtex:article" src-info="bibtex:line-3320" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Ravi</givenname>
				<surname>Kumar</surname>
			</person>
			<person>
				<givenname>Jasmine</givenname>
				<surname>Novak</surname>
			</person>
			<person>
				<givenname>Prabhakar</givenname>
				<surname>Raghavan</surname>
			</person>
			<person>
				<givenname>Andrew</givenname>
				<surname>Tomkins</surname>
			</person>
		</names>
		<date value="2004-12"/>
		<abstract>
			<richtext>
				<p>Blogs constitute a remarkable artifact of the Web. Most people think of them as Web pages with reverse chronological sequences of dated entries, usually with sidebars of profile information and usually maintained and published with the help of a popular blog authoring tool. They tend to be quirky, highly personal, typically read by repeat visitors, and interwoven into a network of tight-knit but active communities. We refer to the collection of blogs and all their links as blogspace. By analyzing the structure and content of more than one million blogs worldwide, we've now unearthed some fascinating insights into blogger behavior.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/1035134.1035162</identifier>
		<title type="sharef:secondaryTitle">Communications of the ACM</title>
		<number>12</number>
		<pages>35-39</pages>
		<title type="sharef:primaryTitle">Structure and Evolution of Blogspace</title>
		<identifier type="sharef:uri">http://portal.acm.org/citation.cfm?doid=1035134.1035162</identifier>
		<identifier type="sharef:uri" resourceType="application/pdf">http://brain.hastypastry.net/blogosphere/blogosphere_structure_and_evolution.pdf</identifier>
		<volume>47</volume>
	</reference>
	<reference name="nar04" src="bibtex:article" src-info="bibtex:line-3335" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Bonnie A.</givenname>
				<surname>Nardi</surname>
			</person>
			<person>
				<givenname>Diane J.</givenname>
				<surname>Schiano</surname>
			</person>
			<person>
				<givenname>Michelle</givenname>
				<surname>Gumbrecht</surname>
			</person>
			<person>
				<givenname>Luke</givenname>
				<surname>Swartz</surname>
			</person>
		</names>
		<date value="2004-12"/>
		<abstract>
			<richtext>
				<p>Blogging is sometimes viewed as a new, grassroots form of journalism and a way to shape democracy outside the mass media and conventional party politics. Blog sites devoted to politics and punditry, as well as to sharing technical developments (such as www.slashdot.org), receive thousands of hits a day. But the vast majority of blogs are written by ordinary people for much smaller audiences. Here, we report the results of an ethnographic investigation of blogging in a sample of ordinary bloggers. We investigated blogging as a form of personal communication and expression, with a specific interest in uncovering the range of motivations driving individuals to create and maintain blogs.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/1035134.1035163</identifier>
		<title type="sharef:secondaryTitle">Communications of the ACM</title>
		<number>12</number>
		<pages>41-46</pages>
		<title type="sharef:primaryTitle">Why We Blog</title>
		<identifier type="sharef:uri">http://portal.acm.org/citation.cfm?doid=1035134.1035163</identifier>
		<volume>47</volume>
	</reference>
	<reference name="arm06" src="bibtex:article" src-info="bibtex:line-3349" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Deborah J.</givenname>
				<surname>Armstrong</surname>
			</person>
		</names>
		<date value="2006-02"/>
		<abstract>
			<richtext>
				<p>Even though object-oriented development was introduced in the late 1960s (beginning with the Simula programming language), OO development has not yet lived up to its promises. A major stumbling block to reaping the promised benefits is learning the OO approach. One reason that learning OO is so difficult may be that we do not yet thoroughly understand the fundamental concepts that define the OO approach. When reviewing the body of work on OO development, most authors simply suggest a set of concepts that characterize OO, and move on with their research or discussion. Thus, they are either taking for granted that the concepts are known or implicitly acknowledging that a universal set of concepts does not exist. Several authors, asserting there is no clear definition of the essence of OO, have called for the development of a consensus. While a few have tried to develop such a consensus, to date a thorough review of the literature and identification of the fundamental concepts of the OO approach has been lacking. The goal of this article is twofold: to identify and describe the fundamental concepts, or quarks, of object-oriented development, and identify how these concepts fit together into a coherent scheme.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/1113034.1113040</identifier>
		<title type="sharef:secondaryTitle">Communications of the ACM</title>
		<number>2</number>
		<pages>123-128</pages>
		<title type="sharef:primaryTitle">The Quarks of Object-Oriented Development</title>
		<volume>49</volume>
	</reference>
	<reference name="fur87" src="bibtex:article" src-info="bibtex:line-3362" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>George W.</givenname>
				<surname>Furnas</surname>
			</person>
			<person>
				<givenname>Thomas K.</givenname>
				<surname>Landauer</surname>
			</person>
			<person>
				<givenname>Louis M.</givenname>
				<surname>Gomez</surname>
			</person>
			<person>
				<givenname>Susan T.</givenname>
				<surname>Dumais</surname>
			</person>
		</names>
		<date value="1987-11"/>
		<abstract>
			<richtext>
				<p>In almost all computer applications, users must enter correct words for the desired objects or actions. For success without extensive training, or in first-tries for new targets, the system must recognize terms that will be chosen spontaneously. We studied spontaneous word choice for objects in five application-related domains, and found the variability to be surprisingly large. In every case two people favored the same term with probability &lt;0.20. Simulations show how this fundamental property of language limits the success of various design methodologies for vocabulary-driven interaction. For example, the popular approach in which access is via one designer's favorite single word will result in 80-90 percent failure rates in many common situations. An optimal strategy, unlimited aliasing, is derived and shown to be capable of several-fold improvements.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/32206.32212</identifier>
		<title type="sharef:secondaryTitle">Communications of the ACM</title>
		<number>11</number>
		<pages>964-971</pages>
		<title type="sharef:primaryTitle">The Vocabulary Problem in Human-System Communication</title>
		<identifier type="sharef:uri" resourceType="application/pdf">http://www.si.umich.edu/~furnas/Papers/vocab.paper.pdf</identifier>
		<volume>30</volume>
	</reference>
	<reference name="gem06" src="bibtex:article" src-info="bibtex:line-3376" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Jim</givenname>
				<surname>Gemmell</surname>
			</person>
			<person>
				<givenname>Gordon</givenname>
				<surname>Bell</surname>
			</person>
			<person>
				<givenname>Roger</givenname>
				<surname>Lueder</surname>
			</person>
		</names>
		<date value="2006-01"/>
		<identifier type="sharef:doi">10.1145/1107458.1107460</identifier>
		<title type="sharef:secondaryTitle">Communications of the ACM</title>
		<number>1</number>
		<pages>88-95</pages>
		<title type="sharef:primaryTitle">Telling Humans and Computers Apart Automatically</title>
		<volume>49</volume>
	</reference>
	<reference name="ahn04" src="bibtex:article" src-info="bibtex:line-3388" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Luis</givenname>
				<surname link="von">Ahn</surname>
			</person>
			<person>
				<givenname>Manuel</givenname>
				<surname>Blum</surname>
			</person>
			<person>
				<givenname>John</givenname>
				<surname>Langford</surname>
			</person>
		</names>
		<date value="2004-02"/>
		<identifier type="sharef:doi">10.1145/966389.966390</identifier>
		<title type="sharef:secondaryTitle">Communications of the ACM</title>
		<number>2</number>
		<pages>56-60</pages>
		<title type="sharef:primaryTitle">Telling Humans and Computers Apart Automatically</title>
		<field type="bibtex:topic">captcha[1]</field>
		<identifier type="sharef:uri" resourceType="application/pdf">http://www.cs.cmu.edu/~biglou/captcha_cacm.pdf</identifier>
		<volume>47</volume>
	</reference>
	<reference name="ken83" src="bibtex:article" src-info="bibtex:line-3402" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>William</givenname>
				<surname>Kent</surname>
			</person>
		</names>
		<date value="1983-02"/>
		<abstract>
			<richtext>
				<p>The concepts behind the five principal normal forms in relational database theory are presented in simple terms.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/975817.975845</identifier>
		<title type="sharef:secondaryTitle">Communications of the ACM</title>
		<number>2</number>
		<pages>120-125</pages>
		<title type="sharef:primaryTitle">A Simple Guide to Five Normal Forms in Relational Database Theory</title>
		<field type="bibtex:topic">firstnf[0.7] secondnf[0.7] thirdnf[0.7] fourthnf[0.7] fifthnf[0.7]</field>
		<identifier type="sharef:uri">http://portal.acm.org/citation.cfm?id=358054</identifier>
		<identifier type="sharef:uri" resourceType="text/html">http://www.bkent.net/Doc/simple5.htm</identifier>
		<volume>26</volume>
	</reference>
	<reference name="pre04" src="bibtex:article" src-info="bibtex:line-3418" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Jennifer J.</givenname>
				<surname>Preece</surname>
			</person>
		</names>
		<date value="2004-04"/>
		<identifier type="sharef:doi">10.1145/975817.975845</identifier>
		<title type="sharef:secondaryTitle">Communications of the ACM</title>
		<number>4</number>
		<pages>56-61</pages>
		<title type="sharef:primaryTitle">Etiquette Online: From Nice to Necessary</title>
		<volume>47</volume>
	</reference>
	<reference name="hol05" src="bibtex:article" src-info="bibtex:line-3430" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Andreas</givenname>
				<surname>Holzinger</surname>
			</person>
		</names>
		<date value="2005-01"/>
		<abstract>
			<richtext>
				<p>The human-computer interaction community aims to increase the awareness and acceptance of established methods among software practitioners. Indeed, awareness of the basic usability methods will drive an Information Society for all.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/1039539.1039541</identifier>
		<title type="sharef:secondaryTitle">Communications of the ACM</title>
		<number>1</number>
		<pages>71-74</pages>
		<title type="sharef:primaryTitle">Usability Engineering Methods for Software Developers</title>
		<volume>48</volume>
	</reference>
	<reference name="lam81" src="bibtex:article" src-info="bibtex:line-3443" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Leslie</givenname>
				<surname>Lamport</surname>
			</person>
		</names>
		<date value="1981-11"/>
		<identifier type="sharef:doi">10.1145/358790.358797</identifier>
		<title type="sharef:secondaryTitle">Communications of the ACM</title>
		<number>11</number>
		<pages>770-772</pages>
		<title type="sharef:primaryTitle">Password Authentication with Insecure Communication</title>
		<volume>24</volume>
	</reference>
	<reference name="hoa81" src="bibtex:article" src-info="bibtex:line-3455" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Charles Antony Richard</givenname>
				<surname>Hoare</surname>
			</person>
		</names>
		<date value="1981-02"/>
		<identifier type="sharef:doi">10.1145/358549.358561</identifier>
		<title type="sharef:secondaryTitle">Communications of the ACM</title>
		<number>2</number>
		<pages>75-83</pages>
		<title type="sharef:primaryTitle">The Emperor's Old Clothes</title>
		<volume>24</volume>
	</reference>
	<reference name="alb04" src="bibtex:article" src-info="bibtex:line-3467" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Conan C.</givenname>
				<surname>Albrecht</surname>
			</person>
		</names>
		<date value="2004-02"/>
		<abstract>
			<richtext>
				<p>If developers are not wise with its application, SOAP may lose the ability to tunnel through firewalls — an ability that represents one of its primary advantages.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/966389.966392</identifier>
		<title type="sharef:secondaryTitle">Communications of the ACM</title>
		<number>2</number>
		<pages>66-68</pages>
		<title type="sharef:primaryTitle">How Clean is the Future of SOAP?</title>
		<field type="bibtex:topic">soap[0.8]</field>
		<volume>47</volume>
	</reference>
	<reference name="par72" src="bibtex:article" src-info="bibtex:line-3481" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>David Lorge</givenname>
				<surname>Parnas</surname>
			</person>
		</names>
		<date value="1972-12"/>
		<abstract>
			<richtext>
				<p>This paper discusses modularization as a mechanism for improving the flexibility and comprehensibility of a system while allowing the shortening of its development time. The effectiveness of a "modularization" is dependent upon the criteria used in dividing the system into modules. A system design problem is presented and both a conventional and unconventional decomposition are described. It is shown that the unconventional decompositions have distinct advantages for the goals outlined. The criteria used in arriving at the decompositions are discussed. The unconventional decomposition, if implemented with the conventional assumption that a module consists of one or more subroutines, will be less efficient in most cases. An alternative approach to implementation which does not have this effect is sketched.</p>
			</richtext>
		</abstract>
		<title type="sharef:secondaryTitle">Communications of the ACM</title>
		<number>12</number>
		<pages>1053-1058</pages>
		<title type="sharef:primaryTitle">On the Criteria To Be Used in Decomposing Systems into Modules</title>
		<field type="bibtex:topic">soc[1]</field>
		<identifier type="sharef:uri">http://www.acm.org/classics/may96/</identifier>
		<volume>15</volume>
	</reference>
	<reference name="wie92" src="bibtex:article" src-info="bibtex:line-3495" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Gio</givenname>
				<surname>Wiederhold</surname>
			</person>
			<person>
				<givenname>Peter</givenname>
				<surname>Wegner</surname>
			</person>
			<person>
				<givenname>Stefano</givenname>
				<surname>Ceri</surname>
			</person>
		</names>
		<date value="1992-11"/>
		<identifier type="sharef:doi">10.1145/138844.138853</identifier>
		<title type="sharef:secondaryTitle">Communications of the ACM</title>
		<number>11</number>
		<pages>89-99</pages>
		<title type="sharef:primaryTitle">Toward Megaprogramming</title>
		<volume>35</volume>
	</reference>
	<reference name="per00b" src="bibtex:article" src-info="bibtex:line-3507" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Mike</givenname>
				<surname>Perkowitz</surname>
			</person>
			<person>
				<givenname>Oren</givenname>
				<surname>Etzioni</surname>
			</person>
		</names>
		<date value="2000-08"/>
		<identifier type="sharef:doi">10.1145/345124.345171</identifier>
		<title type="sharef:secondaryTitle">Communications of the ACM</title>
		<number>8</number>
		<pages>152-158</pages>
		<title type="sharef:primaryTitle">Adaptive Web Sites</title>
		<volume>43</volume>
	</reference>
	<reference name="haa92b" src="bibtex:article" src-info="bibtex:line-3519" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Bernard J.</givenname>
				<surname>Haan</surname>
			</person>
			<person>
				<givenname>Paul</givenname>
				<surname>Kahn</surname>
			</person>
			<person>
				<givenname>Victor A.</givenname>
				<surname>Riley</surname>
			</person>
			<person>
				<givenname>James H.</givenname>
				<surname>Coombs</surname>
			</person>
			<person>
				<givenname>Norman K.</givenname>
				<surname>Meyrowitz</surname>
			</person>
		</names>
		<date value="1992-01"/>
		<title type="sharef:secondaryTitle">Communications of the ACM</title>
		<number>1</number>
		<pages>36-51</pages>
		<title type="sharef:primaryTitle">IRIS Hypermedia Services</title>
		<field type="bibtex:topic">intermedia[1]</field>
		<identifier type="sharef:uri" resourceType="application/pdf">http://delivery.acm.org/10.1145/130000/129618/p36-haan.pdf</identifier>
		<volume>35</volume>
	</reference>
	<reference name="tho84" src="bibtex:article" src-info="bibtex:line-3532" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Ken</givenname>
				<surname>Thompson</surname>
			</person>
		</names>
		<date value="1984-08"/>
		<title type="sharef:secondaryTitle">Communications of the ACM</title>
		<number>8</number>
		<pages>761-763</pages>
		<title type="sharef:primaryTitle">Reflections on Trusting Trust</title>
		<identifier type="sharef:uri">http://www.acm.org/classics/sep95/</identifier>
		<volume>27</volume>
	</reference>
	<reference name="bel01" src="bibtex:article" src-info="bibtex:line-3544" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Gordon</givenname>
				<surname>Bell</surname>
			</person>
		</names>
		<date value="2001-01"/>
		<title type="sharef:secondaryTitle">Communications of the ACM</title>
		<number>1</number>
		<pages>86-91</pages>
		<title type="sharef:primaryTitle">A Personal Store for Everything</title>
		<identifier type="sharef:uri" resourceType="application/pdf">http://research.microsoft.com/users/GBell/CACMCyberAll0101.pdf</identifier>
		<volume>44</volume>
	</reference>
	<reference name="ada01" src="bibtex:article" src-info="bibtex:line-3556" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Lada A.</givenname>
				<surname>Adamic</surname>
			</person>
			<person>
				<givenname>Bernardo A.</givenname>
				<surname>Huberman</surname>
			</person>
		</names>
		<date value="2001-09"/>
		<title type="sharef:secondaryTitle">Communications of the ACM</title>
		<number>9</number>
		<pages>55-60</pages>
		<title type="sharef:primaryTitle">The Web's Hidden Order</title>
		<identifier type="sharef:uri" resourceType="application/pdf">http://www.hpl.hp.com/research/papers/weborder.pdf</identifier>
		<volume>44</volume>
	</reference>
	<reference name="dav95" src="bibtex:article" src-info="bibtex:line-3568" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Hugh C.</givenname>
				<surname>Davis</surname>
			</person>
		</names>
		<date value="1995-08"/>
		<title type="sharef:secondaryTitle">Communications of the ACM</title>
		<number>8</number>
		<pages>108-109</pages>
		<title type="sharef:primaryTitle">To Embed or Not to Embed</title>
		<volume>38</volume>
	</reference>
	<reference name="nel95" src="bibtex:article" src-info="bibtex:line-3579" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Theodor Holm</givenname>
				<surname>Nelson</surname>
			</person>
		</names>
		<date value="1995-08"/>
		<identifier type="sharef:doi">10.1145/208344.208353</identifier>
		<field type="bibtex:index">transclusion</field>
		<title type="sharef:secondaryTitle">Communications of the ACM</title>
		<number>8</number>
		<pages>31-33</pages>
		<title type="sharef:primaryTitle">The Heart of Connection: Hypermedia Unified by Transclusion</title>
		<identifier type="sharef:uri">http://portal.acm.org/citation.cfm?id=208353</identifier>
		<volume>38</volume>
	</reference>
	<reference name="nie99a" src="bibtex:article" src-info="bibtex:line-3593" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Jakob</givenname>
				<surname>Nielsen</surname>
			</person>
		</names>
		<date value="1999-01"/>
		<identifier type="sharef:doi">10.1145/291469.291470</identifier>
		<field type="bibtex:index">WWW, HCI, usability</field>
		<title type="sharef:secondaryTitle">Communications of the ACM</title>
		<number>1</number>
		<pages>65-72</pages>
		<title type="sharef:primaryTitle">User Interface Directions for the Web</title>
		<identifier type="sharef:uri">http://portal.acm.org/citation.cfm?id=291470</identifier>
		<volume>42</volume>
	</reference>
	<reference name="kob99" src="bibtex:article" src-info="bibtex:line-3607" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Cris</givenname>
				<surname>Kobryn</surname>
			</person>
		</names>
		<date value="1999-10"/>
		<title type="sharef:secondaryTitle">Communications of the ACM</title>
		<number>10</number>
		<pages>29-37</pages>
		<title type="sharef:primaryTitle">UML 2001: A Standardization Odyssey</title>
		<field type="bibtex:topic">uml[0.8]</field>
		<volume>42</volume>
	</reference>
	<reference name="mue99" src="bibtex:article" src-info="bibtex:line-3619" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Milton</givenname>
				<surname>Mueller</surname>
			</person>
		</names>
		<date value="1999-06"/>
		<title type="sharef:secondaryTitle">Communications of the ACM</title>
		<number>6</number>
		<pages>41-43</pages>
		<title type="sharef:primaryTitle">ICANN and Internet regulation</title>
		<field type="bibtex:topic">icann[0.8]</field>
		<volume>42</volume>
	</reference>
	<reference name="lie99b" src="bibtex:article" src-info="bibtex:line-3631" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Håkon Wium</givenname>
				<surname>Lie</surname>
			</person>
			<person>
				<givenname>Janne</givenname>
				<surname>Saarela</surname>
			</person>
		</names>
		<date value="1999-10"/>
		<title type="sharef:secondaryTitle">Communications of the ACM</title>
		<number>10</number>
		<pages>95-101</pages>
		<title type="sharef:primaryTitle">Multipurpose Web publishing using HTML, XML, and CSS</title>
		<field type="bibtex:topic">html[0.8] xml[0.8] css[0.8]</field>
		<volume>42</volume>
	</reference>
	<reference name="cod70" src="bibtex:article" src-info="bibtex:line-3643" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Edgar F.</givenname>
				<surname>Codd</surname>
			</person>
		</names>
		<date value="1970-06"/>
		<abstract>
			<richtext>
				<p>Future users of large data banks must be protected from having to know how the data is organized in the machine (the internal representation). A prompting service which supplies such information is not a satisfactory solution. Activities of users at terminals and most application programs should remain unaffected when the internal representation of data is changed and even when some aspects of the external representation are changed. Changes in data representation will often be needed as' a result of changes in query, update, and report traffic and natural growth in the types of stored information. Existing non inferential, formatted data systems provide users with tree-structured files or slightly more general network models of the data. In Section 1, inadequacies of these models are discussed. A model based on n-ary relations, a normal form for data base relations, and the concept of a universal data sub language are introduced. In Section 2, certain operations on relations (other than logical inference) are discussed and applied to the problems of redundancy and consistency in the user's model.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/362384.362685</identifier>
		<title type="sharef:secondaryTitle">Communications of the ACM</title>
		<number>6</number>
		<pages>377-387</pages>
		<title type="sharef:primaryTitle">A Relational Model of Data for Large Shared Data Banks</title>
		<field type="bibtex:topic">rdbms[1]</field>
		<identifier type="sharef:uri">http://portal.acm.org/citation.cfm?id=362685</identifier>
		<identifier type="sharef:uri">http://www.acm.org/classics/nov95/</identifier>
		<volume>13</volume>
	</reference>
	<reference name="nau60" src="bibtex:article" src-info="bibtex:line-3659" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>J. W.</givenname>
				<surname>Backus</surname>
			</person>
			<person>
				<givenname>J. H.</givenname>
				<surname>Wegstein</surname>
			</person>
			<person>
				<givenname>A.</givenname>
				<surname link="van">Wijngaarden</surname>
			</person>
			<person>
				<givenname>M.</givenname>
				<surname>Woodger</surname>
			</person>
			<person>
				<givenname>F. L.</givenname>
				<surname>Bauer</surname>
			</person>
			<person>
				<givenname>J.</givenname>
				<surname>Green</surname>
			</person>
			<person>
				<givenname>C.</givenname>
				<surname>Katz</surname>
			</person>
			<person>
				<givenname>J.</givenname>
				<surname>McCarthy</surname>
			</person>
			<person>
				<givenname>A. J.</givenname>
				<surname>Perlis</surname>
			</person>
			<person>
				<givenname>H.</givenname>
				<surname>Rutishauser</surname>
			</person>
			<person>
				<givenname>K.</givenname>
				<surname>Samelson</surname>
			</person>
			<person>
				<givenname>B.</givenname>
				<surname>Vauquois</surname>
			</person>
		</names>
		<names type="sharef:editor">
			<person>
				<givenname>Peter</givenname>
				<surname>Naur</surname>
			</person>
		</names>
		<date value="1960-05"/>
		<identifier type="sharef:doi">10.1145/367236.367262</identifier>
		<title type="sharef:secondaryTitle">Communications of the ACM</title>
		<number>5</number>
		<pages>299-314</pages>
		<title type="sharef:primaryTitle">Report on the Algorithmic Language ALGOL 60</title>
		<field type="bibtex:topic">bnf[1]</field>
		<identifier type="sharef:uri" resourceType="application/pdf">http://www.fh-jena.de/~kleine/history/languages/Algol60-ACM.pdf</identifier>
		<identifier type="sharef:uri">http://portal.acm.org/citation.cfm?id=367236.367262</identifier>
		<volume>3</volume>
	</reference>
	<reference name="nis92" src="bibtex:article" src-info="bibtex:line-3675" type="sharef:article">
		<names type="sharef:author">
			<name>National Institute of Standards and Technology</name>
		</names>
		<date value="1992-07"/>
		<title type="sharef:secondaryTitle">Communications of the ACM</title>
		<number>7</number>
		<pages>36-54</pages>
		<title type="sharef:primaryTitle">The Digital Signature Standard, proposal and discussion</title>
		<field type="bibtex:topic">dss[0.8] dsa[0.8]</field>
		<volume>35</volume>
	</reference>
	<reference name="riv78" src="bibtex:article" src-info="bibtex:line-3687" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Ronald L.</givenname>
				<surname>Rivest</surname>
			</person>
			<person>
				<givenname>Adi</givenname>
				<surname>Shamir</surname>
			</person>
			<person>
				<givenname>Leonard M.</givenname>
				<surname>Adleman</surname>
			</person>
		</names>
		<date value="1978-02"/>
		<abstract>
			<richtext>
				<p>An encryption method is presented with the novel property that publicly revealing an encryption key does not thereby reveal the corresponding decryption key. This has two important consequences: Couriers or other secure means are not needed to transmit keys, since a message can be enciphered using an encryption key publicly revealed by the intended recipient. Only he can decipher the message, since only he knows the corresponding decryption key. A message can be "signed" using a privately held decryption key. Anyone can verify this signature using the corresponding publicly revealed encryption key. Signatures cannot be forged, and a signer cannot later deny the validity of his signature. This has obvious applications in "electronic mail" and "electronic funds transfer" systems. A message is encrypted by representing it as a number M, raising M to a publicly specified power e, and then taking the remainder when the result is divided by the publicly specified product, n, of two large secret prime numbers p and q. Decryption is similar; only a different, secret, power d is used, where e * d = 1(mod (p - 1) * (q - 1)). The security of the system rests in part on the difficulty of factoring the published divisor, n.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/357980.358017</identifier>
		<title type="sharef:secondaryTitle">Communications of the ACM</title>
		<number>2</number>
		<pages>120-126</pages>
		<title type="sharef:primaryTitle">A Method for Obtaining Digital Signatures and Public-Key Cryptosystems</title>
		<field type="bibtex:topic">rsa[1]</field>
		<identifier type="sharef:uri" resourceType="application/pdf">http://theory.lcs.mit.edu/~rivest/rsapaper.pdf</identifier>
		<identifier type="sharef:uri">http://portal.acm.org/citation.cfm?id=357980.358017</identifier>
		<volume>21</volume>
	</reference>
	<reference name="res96" src="bibtex:article" src-info="bibtex:line-3703" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Paul</givenname>
				<surname>Resnick</surname>
			</person>
			<person>
				<givenname>Jim</givenname>
				<surname>Miller</surname>
			</person>
		</names>
		<date value="1996"/>
		<title type="sharef:secondaryTitle">Communications of the ACM</title>
		<pages>87-93</pages>
		<title type="sharef:primaryTitle">PICS: Internet Access Controls without Censorship</title>
		<field type="bibtex:topic">pics[0.9]</field>
		<identifier type="sharef:uri" resourceType="text/html">http://www.w3.org/PICS/iacwcv2.html</identifier>
		<volume>39</volume>
	</reference>
	<reference name="kli91" src="bibtex:article" src-info="bibtex:line-3714" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Rob</givenname>
				<surname>Kling</surname>
			</person>
		</names>
		<date value="1991"/>
		<field type="bibtex:index">computers and work, CSCW, social impacts of computing, theory of organizational interfaces</field>
		<title type="sharef:secondaryTitle">Communications of the ACM</title>
		<number>12</number>
		<pages>83-88</pages>
		<title type="sharef:primaryTitle">Cooperation, Coordination and Control in Computer-Supported Work</title>
		<volume>34</volume>
	</reference>
	<reference name="gro94" src="bibtex:article" src-info="bibtex:line-3725" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Kaj</givenname>
				<surname>Grønbæk</surname>
			</person>
			<person>
				<givenname>Jens A.</givenname>
				<surname>Hem</surname>
			</person>
			<person>
				<givenname>Ole L.</givenname>
				<surname>Madsen</surname>
			</person>
			<person>
				<givenname>Lennert</givenname>
				<surname>Sloth</surname>
			</person>
		</names>
		<date value="1994-02"/>
		<title type="sharef:secondaryTitle">Communications of the ACM</title>
		<number>2</number>
		<pages>64-74</pages>
		<title type="sharef:primaryTitle">Cooperative Hypermedia Systems: A Dexter-Based Architecture</title>
		<field type="bibtex:topic">dexter[1]</field>
		<volume>37</volume>
	</reference>
	<reference name="hal94" src="bibtex:article" src-info="bibtex:line-3737" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Frank G.</givenname>
				<surname>Halasz</surname>
			</person>
			<person>
				<givenname>Mayer</givenname>
				<surname>Schwartz</surname>
			</person>
		</names>
		<date value="1994-02"/>
		<title type="sharef:secondaryTitle">Communications of the ACM</title>
		<number>2</number>
		<pages>30-39</pages>
		<title type="sharef:primaryTitle">The Dexter Hypertext Reference Model</title>
		<field type="bibtex:topic">dexter[1]</field>
		<volume>37</volume>
	</reference>
	<reference name="che88" src="bibtex:article" src-info="bibtex:line-3749" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>David R.</givenname>
				<surname>Cheriton</surname>
			</person>
		</names>
		<date value="1988"/>
		<field type="bibtex:index">V, distributed systems</field>
		<title type="sharef:secondaryTitle">Communications of the ACM</title>
		<number>3</number>
		<pages>314-333</pages>
		<title type="sharef:primaryTitle">The V Distributed System</title>
		<volume>31</volume>
	</reference>
	<reference name="ell91" src="bibtex:article" src-info="bibtex:line-3760" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Clarence A.</givenname>
				<surname>Ellis</surname>
			</person>
			<person>
				<givenname>Simon J.</givenname>
				<surname>Gibbs</surname>
			</person>
			<person>
				<givenname>Gail L.</givenname>
				<surname>Rein</surname>
			</person>
		</names>
		<date value="1991"/>
		<field type="bibtex:index">GROVE, groupware, collaborative editing</field>
		<title type="sharef:secondaryTitle">Communications of the ACM</title>
		<number>1</number>
		<pages>38-58</pages>
		<title type="sharef:primaryTitle">Groupware — Some Issues and Experiences</title>
		<volume>34</volume>
	</reference>
	<reference name="bir82" src="bibtex:article" src-info="bibtex:line-3771" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Andrew D.</givenname>
				<surname>Birrell</surname>
			</person>
			<person>
				<givenname>Roy</givenname>
				<surname>Levin</surname>
			</person>
			<person>
				<givenname>Roger M.</givenname>
				<surname>Needham</surname>
			</person>
			<person>
				<givenname>Michael D.</givenname>
				<surname>Schroeder</surname>
			</person>
		</names>
		<date value="1982"/>
		<field type="bibtex:index">Grapevine, distributed systems, electronic mail</field>
		<title type="sharef:secondaryTitle">Communications of the ACM</title>
		<number>4</number>
		<pages>260-274</pages>
		<title type="sharef:primaryTitle">Grapevine: An Exercise in Distributed Computing</title>
		<volume>25</volume>
	</reference>
	<reference name="bir93" src="bibtex:article" src-info="bibtex:line-3782" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Kenneth P.</givenname>
				<surname>Birman</surname>
			</person>
		</names>
		<date value="1993"/>
		<field type="bibtex:index">ISIS, process groups, distributed systems</field>
		<title type="sharef:secondaryTitle">Communications of the ACM</title>
		<number>12</number>
		<pages>37-53</pages>
		<title type="sharef:primaryTitle">The Process Group Approach to Reliable Distributed Computing</title>
		<volume>36</volume>
	</reference>
	<reference name="eri94" src="bibtex:article" src-info="bibtex:line-3793" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Hans</givenname>
				<surname>Eriksson</surname>
			</person>
		</names>
		<date value="1994"/>
		<field type="bibtex:index">mbone</field>
		<title type="sharef:secondaryTitle">Communications of the ACM</title>
		<number>8</number>
		<pages>54-60</pages>
		<title type="sharef:primaryTitle">MBone: The Multicast Backbone</title>
		<volume>37</volume>
	</reference>
	<reference name="dal78" src="bibtex:article" src-info="bibtex:line-3804" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Y. K.</givenname>
				<surname>Dalal</surname>
			</person>
			<person>
				<givenname>R. M.</givenname>
				<surname>Metcalfe</surname>
			</person>
		</names>
		<date value="1978"/>
		<title type="sharef:secondaryTitle">Communications of the ACM</title>
		<number>12</number>
		<pages>1040-1048</pages>
		<title type="sharef:primaryTitle">Reverse Path Forwarding of Broadcast Packets</title>
		<volume>21</volume>
	</reference>
	<reference name="sch95a" src="bibtex:article" src-info="bibtex:line-3814" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Daniel</givenname>
				<surname>Schwabe</surname>
			</person>
			<person>
				<givenname>Gustavo</givenname>
				<surname>Rossi</surname>
			</person>
		</names>
		<date value="1995"/>
		<title type="sharef:secondaryTitle">Communications of the ACM</title>
		<number>8</number>
		<pages>45-46</pages>
		<title type="sharef:primaryTitle">The Object-Oriented Hypermedia Design Model</title>
		<volume>38</volume>
	</reference>
	<reference name="wil07b" src="bibtex:article" src-info="bibtex:line-3828" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Erik</givenname>
				<surname>Wilde</surname>
			</person>
			<person>
				<givenname>Sai</givenname>
				<surname>Anand</surname>
			</person>
			<person>
				<givenname>Thierry</givenname>
				<surname>Bücheler</surname>
			</person>
			<person>
				<givenname>Max</givenname>
				<surname>Jörg</surname>
			</person>
			<person>
				<givenname>Nick</givenname>
				<surname>Nabholz</surname>
			</person>
			<person>
				<givenname>Petra</givenname>
				<surname>Zimmermann</surname>
			</person>
		</names>
		<date value="2008-01"/>
		<abstract>
			<richtext>
				<p>In many collaborative research settings, electronic bibliographic repositories (bibliographies) are used to aggregate information about related work among researchers. These bibliographies allow for group bibliography collection, individual tracking of each user's library, and personal annotation capabilities within each user's library. However, most tools used for managing bibliographic data do not support collaboration. Given the collaborative nature of the research group, this information should be shareable between researchers within the group and potentially across larger organizational units (for example, research institutes). By using ShaRef, users can share bibliographic information and collaborate, publish and export data using a variety of output channels. ShaRef's goal is to make sharing of and collaboration with bibliographic information easier than it is today.</p>
			</richtext>
		</abstract>
		<title type="sharef:secondaryTitle">International Journal of Web Based Communities</title>
		<number>1</number>
		<pages>98-109</pages>
		<title type="sharef:primaryTitle">Collaboration Support for Bibliographic Data</title>
		<field type="bibtex:topic">sharef[0.9]</field>
		<identifier type="sharef:uri">http://dret.net/netdret/publications#wil07b</identifier>
		<volume>4</volume>
	</reference>
	<reference name="poh10a" src="bibtex:article" src-info="bibtex:line-3846" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Mikko</givenname>
				<surname>Pohja</surname>
			</person>
		</names>
		<date value="2010-09"/>
		<abstract>
			<richtext>
				<p>Server Push is an essential part of modern web applications. The ability to send relevant information to users in reaction to new events enables highly interactive applications on the WWW. User interfaces of desktop applications have had a two-way communication with underlying software since their advent, but web applications are only reaching the same state now. In addition, currently, server push is usually emulated using pull technology, as HTTP protocol alone is not sufficient to realize a real push. This paper evaluates how an instant messaging protocol, namely XMPP, can complement HTTP-based web applications. We present a communication paradigm of a push system and an implementation of it. In addition, another communication paradigm is sketched for inter-widget messaging on the Web. Based on that paradigm a new research problem is defined and presented.</p>
			</richtext>
		</abstract>
		<title type="sharef:secondaryTitle">Journal of Web Engineering</title>
		<number>3</number>
		<pages>227-242</pages>
		<title type="sharef:primaryTitle">Server Push for Web Applications via Instant Messaging</title>
		<field type="bibtex:topic">xmpp[0.9]</field>
		<volume>9</volume>
	</reference>
	<reference name="wil10c" src="bibtex:article" src-info="bibtex:line-3859" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Erik</givenname>
				<surname>Wilde</surname>
			</person>
			<person>
				<givenname>Anuradha</givenname>
				<surname>Roy</surname>
			</person>
		</names>
		<date value="2010-12"/>
		<abstract>
			<richtext>
				<p>The currently established formats for how a Web site can publish metadata about a site's pages, the robots.txt file and sitemaps, focus on how to provide information to crawlers about where to not go and where to go on a site. This is sufficient as input for crawlers, but does not allow Web sites to publish richer metadata about their site's structure, such as the navigational structure. This paper looks at the availability of Web site metadata on today's Web in terms of available information resources and quantitative aspects of their contents. Such an analysis of the available Web site metadata not only makes it easier to understand what data is available today; it also serves as the foundation for investigating what kind of information retrieval processes could be driven by that data, and what additional data could be provided by Web sites if they had richer data formats to publish metadata.</p>
			</richtext>
		</abstract>
		<title type="sharef:secondaryTitle">Journal of Web Engineering</title>
		<number>4</number>
		<pages>283-301</pages>
		<title type="sharef:primaryTitle">Web Site Metadata</title>
		<identifier type="sharef:uri">http://dret.net/netdret/publications#wil10c</identifier>
		<volume>9</volume>
	</reference>
	<reference name="wil07a" src="bibtex:article" src-info="bibtex:line-3876" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Erik</givenname>
				<surname>Wilde</surname>
			</person>
		</names>
		<date value="2007"/>
		<abstract>
			<richtext>
				<p>Personalization of services often has to cope with the conflicting goals of allowing cooperation and sharing, which require common data formats and services, and supporting individual use cases, which require as much personalization as possible. In this paper we present the ShaRef approach to personalization and sharing, which on the one hand allows users to cooperatively work with bibliographic references, and on the other hand supports the usage of this information in personalized and diverse ways. The goal of this approach is to foster as much cooperation as possible, while simultaneously supporting users with individualized ways of reusing the cooperatively managed data. This way of building applications combines the beneficial aspects of information sharing and personalization. Using this approach, applications are better suited to become building blocks in information infrastructures that are built by users in unpredictable ways.</p>
			</richtext>
		</abstract>
		<title type="sharef:secondaryTitle">Journal of Digital Information</title>
		<number>3</number>
		<title type="sharef:primaryTitle">Personalization of Shared Data: The ShaRef Approach</title>
		<field type="bibtex:topic">sharef[0.9]</field>
		<identifier type="sharef:uri">http://dret.net/netdret/publications#wil07a</identifier>
		<identifier type="sharef:uri">http://journals.tdl.org/jodi/article/view/241/194</identifier>
		<volume>8</volume>
	</reference>
	<reference name="obe04b" src="bibtex:article" src-info="bibtex:line-3889" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Hartmut</givenname>
				<surname>Obendorf</surname>
			</person>
		</names>
		<date value="2004"/>
		<abstract>
			<richtext>
				<p>Building hypertext systems to provide the required functionality to write hypertexts has always been a goal of hypertext research. The parallel development of hypertext research prototypes and the World Wide Web has resulted in repeated attempts to replace the Web or offer world-wide all-purpose services to augment the Web with "missing" functionality. The paper argues that focusing on the development of tools that offer support to hypertext authors for specific tasks is a necessary first step for the introduction of sophisticated hypertext features into the Web. Following a brief history of interaction with the Web, we demonstrate why authoring tools for the Web are a critical target for efforts to extend the use of hypertexts in the Web. We introduce indirect authoring as a label for a shared characteristic of different approaches that try to reduce the complexity and cognitive overhead involved in authoring hypertext. Drawing on this analysis, we lay out some consequences for hypertext research. We provide pointers to projects that have started to experiment with indirect authoring, and list immediate research questions. Developing a diversity of task-oriented authoring tools to reduce the cognitive overhead for authoring hypertexts could change the face of the Web.</p>
			</richtext>
		</abstract>
		<title type="sharef:secondaryTitle">Journal of Digital Information</title>
		<number>1</number>
		<title type="sharef:primaryTitle">The Indirect Authoring Paradigm — Bringing Hypertext into the Web</title>
		<identifier type="sharef:uri">http://ojfpc.ecs.soton.ac.uk/Articles/v05/i01/Obendorf/</identifier>
		<identifier type="sharef:uri">http://journals.tdl.org/jodi/article/view/jodi-134/130</identifier>
		<volume>5</volume>
	</reference>
	<reference name="nue97" src="bibtex:article" src-info="bibtex:line-3901" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Peter J.</givenname>
				<surname>Nürnberg</surname>
			</person>
			<person>
				<givenname>John J.</givenname>
				<surname>Leggett</surname>
			</person>
		</names>
		<date value="1997"/>
		<abstract>
			<richtext>
				<p>Currently, the Open Hypermedia Systems (OHS) Working Group claims three main areas of interest: scenarios, reference architectures, and protocols. The discussions over scenarios of OHS use are supposed to inform the work on OHS reference architectures, which in turn is supposed to enable the development of an Open Hypermedia Protocol (OHP) that will allow clients of one OHP-compliant OHS to use services of other OHP-compliant OHS's. In this paper, we start from existing proposals for an OHS reference architecture and an OHP. We then present a number of scenarios that motivate modifications to these existing proposals. These modifications primarily include adding the notion of an open structure processing layer to the reference architecture and adding a fixed minimal set of guaranteed services to the protocol. We then present our resultant reference architecture and protocol proposals. Our proposals are based on current working group proposals, but incorporate the modifications suggested by our scenarios. Finally, we conclude with some comments on the process we used to derive our proposals, an evaluation of current progress of the OHS Working Group, and suggestions for future directions.</p>
			</richtext>
		</abstract>
		<title type="sharef:secondaryTitle">Journal of Digital Information</title>
		<number>2</number>
		<title type="sharef:primaryTitle">A Vision for Open Hypermedia Systems</title>
		<field type="bibtex:topic">ohs[0.9]</field>
		<identifier type="sharef:uri" resourceType="text/html">http://www.csdl.tamu.edu/~leggett/leggettpubs/journals/jodi/jodi.html</identifier>
		<volume>1</volume>
	</reference>
	<reference name="gro97" src="bibtex:article" src-info="bibtex:line-3913" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Kaj</givenname>
				<surname>Grønbæk</surname>
			</person>
			<person>
				<givenname>Uffe Kock</givenname>
				<surname>Wiil</surname>
			</person>
		</names>
		<date value="1997"/>
		<abstract>
			<richtext>
				<p>This paper contributes to an ongoing effort on standardizing open hypermedia system architectures and communication interfaces. Open hypermedia systems share the property of being able to provide non-hypermedia applications with hypermedia structuring and navigation capabilities. This support is currently provided in many different ways. To be able to standardize communication interfaces, it is necessary to develop common understanding of the different architectures of existing systems and to develop a common reference architecture for open hypermedia systems. A reference architecture should provide a common language for the design of open hypermedia systems in terms of architectural elements and interfaces. The paper identifies a number of important requirements and characteristics for open hypermedia systems and examines some of the most well known open hypermedia architectures and reference models. The analysis illuminates the commonalties and differences in terminology and architectural elements. The analytical results are used to propose common terminology and a common reference architecture for open hypermedia systems (CoReArc). CoReArc identifies several different architectural elements and communication interfaces for potential interface standardization. Interface standardization may be achieved through a single physical protocol with several suites or topics or through several independent protocols. CoReArc can be used to identify and discuss the different communication interfaces of an open hypermedia system.</p>
			</richtext>
		</abstract>
		<title type="sharef:secondaryTitle">Journal of Digital Information</title>
		<number>2</number>
		<title type="sharef:primaryTitle">Towards a Common Reference Architecture for Open Hypermedia</title>
		<field type="bibtex:topic">ohs[0.9]</field>
		<identifier type="sharef:uri">http://jodi.ecs.soton.ac.uk/Articles/v01/i02/Gronbak/</identifier>
		<volume>1</volume>
	</reference>
	<reference name="hun01" src="bibtex:article" src-info="bibtex:line-3925" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Jane</givenname>
				<surname>Hunter</surname>
			</person>
		</names>
		<date value="2001"/>
		<abstract>
			<richtext>
				<p>Metadata interoperability is a fundamental requirement for access to information within networked knowledge organization systems. The Harmony international digital library project has developed a common underlying data model (the ABC model) to enable the scalable mapping of metadata descriptions across domains and media types. The ABC model provides a set of basic building blocks for metadata modeling and recognizes the importance of 'events' to describe unambiguously metadata for objects with a complex history. To test and evaluate the interoperability capabilities of this model, we applied it to some real multimedia examples and analysed the results of mapping from the ABC model to various different metadata domains using XSLT. This work revealed serious limitations in the ability of XSLT to support flexible dynamic semantic mapping. To overcome this, we developed MetaNet, a metadata term thesaurus which provides the additional semantic knowledge that is non-existent within declarative XML-encoded metadata descriptions. This paper describes MetaNet, its RDF Schema representation and a hybrid mapping approach which combines the structural and syntactic mapping capabilities of XSLT with the semantic knowledge of MetaNet, to enable flexible and dynamic mapping among metadata standards.</p>
			</richtext>
		</abstract>
		<title type="sharef:secondaryTitle">Journal of Digital Information</title>
		<number>8</number>
		<title type="sharef:primaryTitle">MetaNet — A Metadata Term Thesaurus to Enable Semantic Interoperability Between Metadata Domains</title>
		<field type="bibtex:topic">ohs[0.9]</field>
		<identifier type="sharef:uri">http://jodi.ecs.soton.ac.uk/Articles/v01/i08/Hunter/</identifier>
		<volume>1</volume>
	</reference>
	<reference name="san93a" src="bibtex:article" src-info="bibtex:line-3941" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Adelino</givenname>
				<surname>Santos</surname>
			</person>
		</names>
		<date value="1993"/>
		<field type="bibtex:index">CoMEdiA</field>
		<title type="sharef:secondaryTitle">Journal of Computer Science and Technology</title>
		<number>3</number>
		<pages>257-269</pages>
		<title type="sharef:primaryTitle">Cooperative Hypermedia Editing with CoMEdiA</title>
		<volume>8</volume>
	</reference>
	<reference name="pen01" src="bibtex:article" src-info="bibtex:line-3956" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Ed</givenname>
				<surname>Pentz</surname>
			</person>
		</names>
		<date value="2001">Winter 2001</date>
		<abstract>
			<richtext>
				<p>References are at the heart of scholarly journal publishing and therefore reference links are seen as an essential feature of online scholarly journals. Scholarly publishers created CrossRef, run by the non-profit Publishers International Linking Association, Inc., in order to make broad-based linking efficient and scalable across a wide range of primary publishers, secondary publishers, abstracting and indexing services, and libraries. CrossRef runs a system that enables publishers to assign unique identifiers — Digital Object Identifiers (DOI) — to articles and collects standardized metadata so that the identifiers can be retrieved using bibliographic data. Once the DOI for an article is known, a persistent link to the full-text article can be created. CrossRef is a milestone for the scholarly information industry.</p>
			</richtext>
		</abstract>
		<title type="sharef:secondaryTitle">Issues in Science &amp; Technology Librarianship</title>
		<number>29</number>
		<title type="sharef:primaryTitle">CrossRef: A Collaborative Linking Network</title>
		<field type="bibtex:topic">crossref[0.8]</field>
		<identifier type="sharef:uri" resourceType="text/html">http://www.istl.org/01-winter/article1.html</identifier>
	</reference>
	<reference name="wil04o" src="bibtex:article" src-info="bibtex:line-3968" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Erik</givenname>
				<surname>Wilde</surname>
			</person>
		</names>
		<date value="2004">Fall 2004</date>
		<abstract>
			<richtext>
				<p>Management of bibliographic and Web references for many researchers is the closest thing to knowledge management they will ever do. This article describes ShaRef, a new approach to reference management that focuses on the user and enhances traditional reference management approaches with collaboration features and lightweight knowledge management. While this is primarily targeted at providing individual users and user groups with a better tool, it also creates a new and interesting link to libraries, because of the features that enable users to go from their own references directly to the library through the use of OpenURL. Thus, a new task for libraries is to adjust to this new type of users, who are using new technologies to access a library.</p>
			</richtext>
		</abstract>
		<title type="sharef:secondaryTitle">Issues in Science &amp; Technology Librarianship</title>
		<number>41</number>
		<title type="sharef:primaryTitle">References as Knowledge Management</title>
		<identifier type="sharef:uri" resourceType="text/html">http://www.istl.org/04-fall/article4.html</identifier>
		<identifier type="sharef:uri">http://dret.net/netdret/publications#wil04o</identifier>
	</reference>
	<reference name="alt07" src="bibtex:article" src-info="bibtex:line-3984" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Micah</givenname>
				<surname>Altman</surname>
			</person>
			<person>
				<givenname>Gary</givenname>
				<surname>King</surname>
			</person>
		</names>
		<date value="2007-03"/>
		<abstract>
			<richtext>
				<p>An essential aspect of science is a community of scholars cooperating and competing in the pursuit of common goals. A critical component of this community is the common language of and the universal standards for scholarly citation, credit attribution, and the location and retrieval of articles and books. We propose a similar universal standard for citing quantitative data that retains the advantages of print citations, adds other components made possible by, and needed due to, the digital form and systematic nature of quantitative data sets, and is consistent with most existing subfield-specific approaches. Although the digital library field includes numerous creative ideas, we limit ourselves to only those elements that appear ready for easy practical use by scientists, journal editors, publishers, librarians, and archivists.</p>
			</richtext>
		</abstract>
		<title type="sharef:secondaryTitle">D-Lib Magazine</title>
		<number>3/4</number>
		<title type="sharef:primaryTitle">A Proposed Standard for the Scholarly Citation of Quantitative Data</title>
		<identifier type="sharef:uri" resourceType="text/html">http://www.dlib.org/dlib/march07/altman/03altman.html</identifier>
		<volume>13</volume>
	</reference>
	<reference name="phe00b" src="bibtex:article" src-info="bibtex:line-3996" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Thomas Arthur</givenname>
				<surname>Phelps</surname>
			</person>
			<person>
				<givenname>Robert</givenname>
				<surname>Wilensky</surname>
			</person>
		</names>
		<date value="2000"/>
		<abstract>
			<richtext>
				<p>We suggest that building "permissive, but robust" digital library systems and services is an attractive alternative to the library and computer science tradition of building "strict, but fragile" systems. Strict, but fragile, systems are efforts to engineer complete systems that ensure desired properties, but which often prove impractical in distributed environments without a central authority to coordinate change. In the permissive, but robust, approach, we permit individual components to change in ways that might, in fact, cause a desired property to fail to persist. However, we engineer components to be robust, so that it is likely that desired properties persist even under a great deal of uncoordinated change. We have applied the permissive, but robust, approach to two related problems of reference in distributed information systems. The first application yields robust hyperlinks, and the second, robust locations. Robust hyperlinks address the familiar issue of providing persistent reference to networked resources, such as Web pages, given changing, uncooperating services. Robust locations concern a somewhat less familiar, but, we suspect, soon-to-be just as big a problem, namely, references to changing sub-document resources. Robust locations, we suggest, provide essential grounding for next-generation web functionality, such as annotations that survive document editing. In both cases, robustness is achieved by providing multiple, independent descriptions across boundaries where change is likely to be uncoordinated. If the different descriptions are property selected, then most uncoordinated changes will be unlikely to cause all the descriptions to fail. Thus, while there is no guarantee that references will remain coherent, a single failure is unlikely to be catastrophic. Instead, the failure of one, even a primary, method will generally allow graceful recovery via other methods.</p>
			</richtext>
		</abstract>
		<title type="sharef:secondaryTitle">D-Lib Magazine</title>
		<number>7/8</number>
		<title type="sharef:primaryTitle">Robust Hyperlinks and Locations</title>
		<identifier type="sharef:uri" resourceType="text/html">http://www.dlib.org/dlib/july00/wilensky/07wilensky.html</identifier>
		<volume>6</volume>
	</reference>
	<reference name="smi03" src="bibtex:article" src-info="bibtex:line-4007" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>MacKenzie</givenname>
				<surname>Smith</surname>
			</person>
			<person>
				<givenname>Mary</givenname>
				<surname>Barton</surname>
			</person>
			<person>
				<givenname>Mick</givenname>
				<surname>Bass</surname>
			</person>
			<person>
				<givenname>Margret</givenname>
				<surname>Branschofsky</surname>
			</person>
			<person>
				<givenname>Greg</givenname>
				<surname>McClellan</surname>
			</person>
			<person>
				<givenname>Dave</givenname>
				<surname>Stuve</surname>
			</person>
			<person>
				<givenname>Robert</givenname>
				<surname>Tansley</surname>
			</person>
			<person>
				<givenname>Julie Harford</givenname>
				<surname>Walker</surname>
			</person>
		</names>
		<date value="2003-01"/>
		<abstract>
			<richtext>
				<p>For the past two years the Massachusetts Institute of Technology (MIT) Libraries and Hewlett-Packard Labs have been collaborating on the development of an open source system called DSpace that functions as a repository for the digital research and educational material produced by members of a research university or organization. Running such an institutionally-based, multidisciplinary repository is increasingly seen as a natural role for the libraries and archives of research and teaching organizations. As their constituents produce increasing amounts of original material in digital formats — much of which is never published by traditional means — the repository becomes vital to protect the significant assets of the institution and its faculty. The first part of this article describes the DSpace system including its functionality and design, and its approach to various problems in digital library and archives design. The second part discusses the implementation of DSpace at MIT, plans for federating the system, and issues of sustainability.</p>
			</richtext>
		</abstract>
		<title type="sharef:secondaryTitle">D-Lib Magazine</title>
		<number>1</number>
		<title type="sharef:primaryTitle">DSpace — An Open Source Dynamic Digital Repository</title>
		<field type="bibtex:topic">dspace[0.9]</field>
		<identifier type="sharef:uri" resourceType="text/html">http://www.dlib.org/dlib/january03/smith/01smith.html</identifier>
		<volume>9</volume>
	</reference>
	<reference name="som03" src="bibtex:article" src-info="bibtex:line-4020" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Herbert</givenname>
				<surname>Van de Sompel</surname>
			</person>
			<person>
				<givenname>Jeffrey A.</givenname>
				<surname>Young</surname>
			</person>
			<person>
				<givenname>Thomas B.</givenname>
				<surname>Hickey</surname>
			</person>
		</names>
		<date value="2003">July/August 2003</date>
		<abstract>
			<richtext>
				<p>The Open Archives Initiative's Protocol for Metadata Harvesting (OAI-PMH) was created to facilitate discovery of distributed resources. The OAI-PMH achieves this by providing a simple, yet powerful framework for metadata harvesting. Harvesters can incrementally gather records contained in OAI-PMH repositories and use them to create services covering the content of several repositories. The OAI-PMH has been widely accepted, and until recently, it has mainly been applied to make Dublin Core metadata about scholarly objects contained in distributed repositories searchable through a single user interface. This article describes innovative applications of the OAI-PMH that we have introduced in recent projects. In these projects, OAI-PMH concepts such as resource and metadata format have been interpreted in novel ways. The result of doing so illustrates the usefulness of the OAI-PMH beyond the typical resource discovery using Dublin Core metadata. Also, through the inclusion of XSL  stylesheets in protocol responses, OAI-PMH repositories have been directly overlaid with an interface that allows users to navigate the contained metadata by means of a Web browser. In addition, through the introduction of PURL2 partial redirects, complex OAI-PMH protocol requests have been turned into simple URIs that can more easily be published and used in downstream applications.</p>
			</richtext>
		</abstract>
		<title type="sharef:secondaryTitle">D-Lib Magazine</title>
		<number>7/8</number>
		<title type="sharef:primaryTitle">Using the OAI-PMH ... Differently</title>
		<field type="bibtex:topic">oaipmh[0.9]</field>
		<identifier type="sharef:uri" resourceType="text/html">http://www.dlib.org/dlib/july03/young/07young.html</identifier>
		<volume>9</volume>
	</reference>
	<reference name="wil04q" src="bibtex:article" src-info="bibtex:line-4033" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Erik</givenname>
				<surname>Wilde</surname>
			</person>
		</names>
		<date value="2004-09"/>
		<identifier type="sharef:doi">doi:10.1045/september2004-inbrief</identifier>
		<title type="sharef:secondaryTitle">D-Lib Magazine</title>
		<number>9</number>
		<title type="sharef:primaryTitle">A Tool for Bibliography Management and Sharing: The ShaRef Project</title>
		<identifier type="sharef:uri">http://dret.net/netdret/publications#wil04q</identifier>
		<identifier type="sharef:uri">http://www.dlib.org/dlib/september04/09inbrief.html#WILDE</identifier>
		<volume>10</volume>
	</reference>
	<reference name="hit02" src="bibtex:article" src-info="bibtex:line-4046" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Steve</givenname>
				<surname>Hitchcock</surname>
			</person>
			<person>
				<givenname>Donna</givenname>
				<surname>Bergmark</surname>
			</person>
			<person>
				<givenname>Tim</givenname>
				<surname>Brody</surname>
			</person>
			<person>
				<givenname>Christopher</givenname>
				<surname>Gutteridge</surname>
			</person>
			<person>
				<givenname>Leslie A.</givenname>
				<surname>Carr</surname>
			</person>
			<person>
				<givenname>Wendy</givenname>
				<surname>Hall</surname>
			</person>
			<person>
				<givenname>Carl</givenname>
				<surname>Lagoze</surname>
			</person>
			<person>
				<givenname>Stevan</givenname>
				<surname>Harnad</surname>
			</person>
		</names>
		<date value="2002-10"/>
		<title type="sharef:secondaryTitle">D-Lib Magazine</title>
		<number>10</number>
		<title type="sharef:primaryTitle">Open Citation Linking — The Way Forward</title>
		<identifier type="sharef:uri" resourceType="text/html">http://www.dlib.org/dlib/october02/hitchcock/10hitchcock.html</identifier>
		<volume>8</volume>
	</reference>
	<reference name="cap99" src="bibtex:article" src-info="bibtex:line-4057" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Priscilla</givenname>
				<surname>Caplan</surname>
			</person>
			<person>
				<givenname>William Yeo</givenname>
				<surname>Arms</surname>
			</person>
		</names>
		<date value="1999">July/August 1999</date>
		<title type="sharef:secondaryTitle">D-Lib Magazine</title>
		<number>7/8</number>
		<title type="sharef:primaryTitle">Reference Linking for Journal Articles</title>
		<identifier type="sharef:uri" resourceType="text/html">http://www.dlib.org/dlib/july99/caplan/07caplan.html</identifier>
		<volume>5</volume>
	</reference>
	<reference name="atk00" src="bibtex:article" src-info="bibtex:line-4068" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Helen</givenname>
				<surname>Atkins</surname>
			</person>
			<person>
				<givenname>Catherine</givenname>
				<surname>Lyons</surname>
			</person>
			<person>
				<givenname>Howard</givenname>
				<surname>Ratner</surname>
			</person>
			<person>
				<givenname>Carol</givenname>
				<surname>Risher</surname>
			</person>
			<person>
				<givenname>Chris</givenname>
				<surname>Shillum</surname>
			</person>
			<person>
				<givenname>David</givenname>
				<surname>Sidman</surname>
			</person>
			<person>
				<givenname>Andrew</givenname>
				<surname>Stevens</surname>
			</person>
		</names>
		<date value="2000-02"/>
		<title type="sharef:secondaryTitle">D-Lib Magazine</title>
		<number>2</number>
		<title type="sharef:primaryTitle">Reference Linking with DOIs — A Case Study</title>
		<field type="bibtex:topic">doi[0.7]</field>
		<identifier type="sharef:uri" resourceType="text/html">http://www.dlib.org/dlib/february00/02risher.html</identifier>
		<volume>6</volume>
	</reference>
	<reference name="som01b" src="bibtex:article" src-info="bibtex:line-4080" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Herbert</givenname>
				<surname>Van de Sompel</surname>
			</person>
			<person>
				<givenname>Oren</givenname>
				<surname>Beit-Arie</surname>
			</person>
		</names>
		<date value="2001">July/August 2001</date>
		<title type="sharef:secondaryTitle">D-Lib Magazine</title>
		<number>7/8</number>
		<title type="sharef:primaryTitle">Generalizing the OpenURL Framework beyond References to Scholarly Works — The Bison-Futé Model</title>
		<field type="bibtex:topic">openurl[0.8]</field>
		<identifier type="sharef:uri" resourceType="text/html">http://www.dlib.org/dlib/july01/vandesompel/07vandesompel.html</identifier>
		<volume>7</volume>
	</reference>
	<reference name="som01" src="bibtex:article" src-info="bibtex:line-4092" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Herbert</givenname>
				<surname>Van de Sompel</surname>
			</person>
			<person>
				<givenname>Oren</givenname>
				<surname>Beit-Arie</surname>
			</person>
		</names>
		<date value="2001-03"/>
		<title type="sharef:secondaryTitle">D-Lib Magazine</title>
		<number>3</number>
		<title type="sharef:primaryTitle">Open Linking in the Scholarly Information Environment Using the OpenURL Framework</title>
		<field type="bibtex:topic">openurl[0.8]</field>
		<identifier type="sharef:uri" resourceType="text/html">http://www.dlib.org/dlib/march01/vandesompel/03vandesompel.html</identifier>
		<volume>7</volume>
	</reference>
	<reference name="bra01" src="bibtex:article" src-info="bibtex:line-4104" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Amy</givenname>
				<surname>Brand</surname>
			</person>
		</names>
		<date value="2001-05"/>
		<title type="sharef:secondaryTitle">D-Lib Magazine</title>
		<number>5</number>
		<title type="sharef:primaryTitle">CrossRef Turns One</title>
		<field type="bibtex:topic">crossref[0.8]</field>
		<identifier type="sharef:uri" resourceType="text/html">http://www.dlib.org/dlib/may01/brand/05brand.html</identifier>
		<volume>7</volume>
	</reference>
	<reference name="lag96" src="bibtex:article" src-info="bibtex:line-4116" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Carl</givenname>
				<surname>Lagoze</surname>
			</person>
		</names>
		<date value="1996-07"/>
		<field type="bibtex:index">Warwick Framework</field>
		<title type="sharef:secondaryTitle">D-Lib Magazine</title>
		<number>7</number>
		<title type="sharef:primaryTitle">A Container Architecture for Diverse Sets of Metadata</title>
		<field type="bibtex:topic">metadata[0.8]</field>
		<identifier type="sharef:uri" resourceType="text/html">http://www.dlib.org/dlib/july96/lagoze/07lagoze.html</identifier>
		<volume>2</volume>
	</reference>
	<reference name="pas99" src="bibtex:article" src-info="bibtex:line-4129" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Norman</givenname>
				<surname>Paskin</surname>
			</person>
		</names>
		<date value="1999-05"/>
		<title type="sharef:secondaryTitle">D-Lib Magazine</title>
		<number>5</number>
		<title type="sharef:primaryTitle">DOI: Current Status and Outlook</title>
		<field type="bibtex:topic">doi[0.9]</field>
		<identifier type="sharef:uri">http://www.dlib.org</identifier>
		<volume>5</volume>
	</reference>
	<reference name="san93b" src="bibtex:article" src-info="bibtex:line-4145" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Adelino</givenname>
				<surname>Santos</surname>
			</person>
		</names>
		<date value="1993"/>
		<field type="bibtex:index">CoMEdiA</field>
		<title type="sharef:secondaryTitle">Computers and Graphics Magazine</title>
		<number>3</number>
		<pages>261-268</pages>
		<title type="sharef:primaryTitle">CoMEdiA: Conceptualisation and Realisation of a Cooperative Hypermedia Editing Architecture</title>
		<volume>17</volume>
	</reference>
	<reference name="bez06" src="bibtex:article" src-info="bibtex:line-4160" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Jean</givenname>
				<surname>Bézivin</surname>
			</person>
		</names>
		<date value="2005-05"/>
		<abstract>
			<richtext>
				<p>In November 2000, the OMG made public the MDA initiative, a particular variant of a new global trend called MDE (Model Driven Engineering). The basic ideas of MDA are germane to many other approaches such as generative programming, domain specific languages, model-integrated computing, generic model management, software factories, etc. MDA may be defined as the realization of MDE principles around a set of OMG standards like MOF, XMI, OCL, UML, CWM, SPEM, etc. MDE is presently making several promises about the potential benefits that could be reaped from a move from code-centric to model-based practices. When we observe these claims, we may wonder when they may be satisfied: on the short, medium or long term or even never perhaps for some of them. This paper tries to propose a vision of the development of MDE based on some lessons learnt in the past 30 years in the development of object technology. The main message is that a basic principle ("Everything is an object") was most helpful in driving the technology in the direction of simplicity, generality and power of integration. Similarly in MDE, the basic principle that "Everything is a model" has many interesting properties, among others the capacity to generate a realistic research agenda. We postulate here that two core relations (representation and conformance) are associated to this principle, as inheritance and instantiation were associated to the object unification principle in the class-based languages of the 80's. We suggest that this may be most useful in understanding many questions about MDE in general and the MDA approach in particular. We provide some illustrative examples. The personal position taken in this paper would be useful if it could generate a critical debate on the research directions in MDE.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1007/s10270-005-0079-0</identifier>
		<title type="sharef:secondaryTitle">Software and Systems Modeling</title>
		<number>2</number>
		<pages>171-188</pages>
		<title type="sharef:primaryTitle">On the Unification Power of Models</title>
		<volume>4</volume>
	</reference>
	<reference name="jar95" src="bibtex:article" src-info="bibtex:line-4177" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Matthias</givenname>
				<surname>Jarke</surname>
			</person>
			<person>
				<givenname>R.</givenname>
				<surname>Gallersdörfer</surname>
			</person>
			<person>
				<givenname>Manfred A.</givenname>
				<surname>Jeusfeld</surname>
			</person>
			<person>
				<givenname>Martin</givenname>
				<surname>Staudt</surname>
			</person>
			<person>
				<givenname>S.</givenname>
				<surname>Eherer</surname>
			</person>
		</names>
		<date value="1995"/>
		<field type="bibtex:index">ConceptBase</field>
		<title type="sharef:secondaryTitle">Journal of Intelligent Information Systems</title>
		<number>2</number>
		<pages>167-192</pages>
		<title type="sharef:primaryTitle">ConceptBase — A Deductive Object Base for Meta Data Management</title>
		<volume>4</volume>
	</reference>
	<reference name="wuw03" src="bibtex:article" src-info="bibtex:line-4188" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Vilas</givenname>
				<surname>Wuwongse</surname>
			</person>
			<person>
				<givenname>Kiyoshi</givenname>
				<surname>Akama</surname>
			</person>
			<person>
				<givenname>Chutiporn</givenname>
				<surname>Anutariya</surname>
			</person>
			<person>
				<givenname>Ekawit</givenname>
				<surname>Nantajeewarawat</surname>
			</person>
		</names>
		<date value="2003-01"/>
		<abstract>
			<richtext>
				<p>In the proposed data model for XML databases, an XML element is directly represented as a ground (variable-free) XML expression — a generalization of an XML element by incorporation of variables for representation of implicit information and enhancement of its expressive power — while a collection of XML documents as a set of ground expressions, each describing an XML element in the documents. Axioms and relationships among elements in the collection as well as structural and integrity constraints are formalized as XML clauses. An XML database, consisting of: (i) a document collection (or an extensional database), (ii) a set of axioms and relationships (or an intensional database), (iii) a set of integrity constraints, is therefore modeled as an XML declarative description comprising a set of ground XML expressions and XML clauses. Its semantics is a set of ground XML expressions, which are explicitly described by the extensional database or implicitly derived from the database, based on the defined intensional database, and satisfy all the specified set of constraints. Thus, selective and complex queries, formulated as sets of XML clauses, about information satisfying specific criteria and possibly implicit in the database, become expressible and computable. The model thereby serves as an effective and well-founded XML database management framework with succinct representational and operational uniformity, reasoning capabilities as well as complex and deductive query supports.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1023/A:1020947122751</identifier>
		<title type="sharef:secondaryTitle">Journal of Intelligent Information Systems</title>
		<number>1</number>
		<pages>63-80</pages>
		<title type="sharef:primaryTitle">A Data Model for XML Databases</title>
		<field type="bibtex:topic">xdd[1]</field>
		<identifier type="sharef:uri">http://www.springerlink.com/link.asp?id=n07346591qr37245</identifier>
		<volume>20</volume>
	</reference>
	<reference name="kni93" src="bibtex:article" src-info="bibtex:line-4207" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Michael J.</givenname>
				<surname>Knister</surname>
			</person>
			<person>
				<givenname>Atul</givenname>
				<surname>Prakash</surname>
			</person>
		</names>
		<date value="1993"/>
		<field type="bibtex:index">DistEdit, groupware, collaborative editing</field>
		<title type="sharef:secondaryTitle">Computing Systems</title>
		<number>2</number>
		<pages>135-166</pages>
		<title type="sharef:primaryTitle">Issues in the Design of a Toolkit for Supporting Multiple Group Editors</title>
		<volume>6</volume>
	</reference>
	<reference name="bru93" src="bibtex:article" src-info="bibtex:line-4222" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Anne</givenname>
				<surname>Brüggemann-Klein</surname>
			</person>
		</names>
		<date value="1993"/>
		<title type="sharef:secondaryTitle">Theoretical Computer Science</title>
		<number>2</number>
		<pages>197-213</pages>
		<title type="sharef:primaryTitle">Regular Expressions into Finite Automata</title>
		<field type="bibtex:topic">regex[0.9]</field>
		<identifier type="sharef:uri">ftp://ftp.informatik.uni-freiburg.de/documents/reports/report33/</identifier>
		<volume>120</volume>
	</reference>
	<reference name="cha99c" src="bibtex:article" src-info="bibtex:line-4238" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Jean-Marc</givenname>
				<surname>Champarnaud</surname>
			</person>
			<person>
				<givenname>Jean-Luc</givenname>
				<surname>Ponty</surname>
			</person>
			<person>
				<givenname>Djelloul</givenname>
				<surname>Ziadi</surname>
			</person>
		</names>
		<date value="1999"/>
		<abstract>
			<richtext>
				<p>There are three classical algorithms to compute a finite automaton from a regular expression. The Brzozowski algorithm yields a deterministic automaton, the Glushkov algorithm a nondeterministic one, and the general step by step method generally yields a NFA with ε-transitions. Berry and Sethi have adapted Brzozowski's algorithm to compute the Glushkov automaton of an expression. We describe a variant of the step by step construction which associates standard and trim automata to regular languages. We show that the automaton constructed by the variant and the Glushkov automaton (computed by Berry-Sethi algorithm) are isomorphic.</p>
			</richtext>
		</abstract>
		<title type="sharef:secondaryTitle">International Journal of Computer Mathematics</title>
		<number>4</number>
		<pages>415-431</pages>
		<title type="sharef:primaryTitle">From Regular Expressions to Finite Automata</title>
		<field type="bibtex:topic">regex[0.9]</field>
		<identifier type="sharef:uri">http://cat.inist.fr/?aModele=afficheN&amp;cpsidt=1242385</identifier>
		<volume>72</volume>
	</reference>
	<reference name="sen03c" src="bibtex:article" src-info="bibtex:line-4255" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Stephen D.</givenname>
				<surname>Senturia</surname>
			</person>
		</names>
		<date value="2003-06"/>
		<abstract>
			<richtext>
				<p>Based on his many years of experience, a JMEMS editor provides guidelines for authors that will, if followed, greatly reduce the risk of a devastatingly negative result from the review process. The premise is that there are certain things that rightfully anger reviewers, and, once angered, the reviewers become both negative and aggressive in their judgments — hence, the imagery of "the reviewer's axe" and how to avoid it.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1109/JMEMS.2003.814319</identifier>
		<title type="sharef:secondaryTitle">IEEE/ASME Journal of Microelectromechanical Systems</title>
		<number>3</number>
		<pages>229-232</pages>
		<title type="sharef:primaryTitle">How to Avoid the Reviewer's Axe: One Editor's View</title>
		<identifier type="sharef:uri">http://ieeexplore.ieee.org/xpls/abs_all.jsp?isnumber=27107&amp;arnumber=1203760&amp;count=17&amp;index=0</identifier>
		<identifier type="sharef:uri" resourceType="application/pdf">http://www.me.umn.edu/labs/miml/reviewer-axe.pdf</identifier>
		<volume>12</volume>
	</reference>
	<reference name="ngo89" src="bibtex:article" src-info="bibtex:line-4274" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>L. H.</givenname>
				<surname>Ngoh</surname>
			</person>
			<person>
				<givenname>T. P.</givenname>
				<surname>Hopkins</surname>
			</person>
		</names>
		<date value="1989"/>
		<field type="bibtex:index">DMIS, multicast</field>
		<title type="sharef:secondaryTitle">The Computer Journal</title>
		<number>3</number>
		<pages>252-261</pages>
		<title type="sharef:primaryTitle">Transport Protocol Requirements for Distributed Multimedia Information Systems</title>
		<volume>32</volume>
	</reference>
	<reference name="vie08" src="bibtex:article" src-info="bibtex:line-4289" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Fernanda B.</givenname>
				<surname>Viégas</surname>
			</person>
			<person>
				<givenname>Martin</givenname>
				<surname>Wattenberg</surname>
			</person>
		</names>
		<date value="2008"/>
		<identifier type="sharef:doi">10.1145/1374489.1374501</identifier>
		<title type="sharef:secondaryTitle">interactions</title>
		<number>4</number>
		<pages>49-52</pages>
		<title type="sharef:primaryTitle">Tag Clouds and the Case for Vernacular Visualization</title>
		<volume>15</volume>
	</reference>
	<reference name="sam07" src="bibtex:article" src-info="bibtex:line-4300" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Fred</givenname>
				<surname>Sampson</surname>
			</person>
		</names>
		<date value="2007"/>
		<identifier type="sharef:doi">10.1145/1242421.1242431</identifier>
		<title type="sharef:secondaryTitle">interactions</title>
		<number>3</number>
		<pages>10-11</pages>
		<title type="sharef:primaryTitle">Sense and Accessibility</title>
		<volume>14</volume>
	</reference>
	<reference name="mar03b" src="bibtex:article" src-info="bibtex:line-4311" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Aaron</givenname>
				<surname>Marcus</surname>
			</person>
		</names>
		<date value="2003-03"/>
		<abstract>
			<richtext>
				<p>User-interface design seeks to improve all human-computer communication and interaction. Increasingly, challenges for the disabled and elderly must be met. Experience gained can help solve fundamental challenges for the general population of users. A recent international conference in Japan, "Universal Design," catalogues both the accomplishments and work to be done in this worldwide arena.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/637848.637858</identifier>
		<title type="sharef:secondaryTitle">interactions</title>
		<number>3</number>
		<pages>23-27</pages>
		<title type="sharef:primaryTitle">Universal, Ubiquitous, User-Interface Design for the Disabled and Elderly</title>
		<volume>10</volume>
	</reference>
	<reference name="rit07" src="bibtex:article" src-info="bibtex:line-4328" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Paul</givenname>
				<surname>Ritchie</surname>
			</person>
		</names>
		<date value="2007-03"/>
		<abstract>
			<richtext>
				<p>Web 2.0 has become a generic phrase summing up everything that is hot and new about the Internet. However, underneath it lie some fundamental concepts, including the writeable web, increased audience participation, and a move away from traditional 'click and wait' web applications, in which input was delivered on a page by page basis. AJAX (asynchronous JavaScript and XML) is a programming mechanism that has enabled developers to deliver a better experience to web users. However, just as basic JavaScript validation mechanisms did before it, AJAX-based applications may be subject to abuse by intruders who can launch attacks designed to bypass login scripts, for example. Programmers and project managers must come to terms with the tension between a better user experience and the potential for security flaws. One way to resolve them is to use robust coding techniques to protect applications.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1016/S1353-4858(07)70025-9</identifier>
		<title type="sharef:secondaryTitle">Network Security</title>
		<number>3</number>
		<pages>4-8</pages>
		<title type="sharef:primaryTitle">The Security Risks of AJAX/Web 2.0 Applications</title>
		<volume>2007</volume>
	</reference>
	<reference name="gru08" src="bibtex:article" src-info="bibtex:line-4345" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Torsten</givenname>
				<surname>Grust</surname>
			</person>
			<person>
				<givenname>Jan</givenname>
				<surname>Rittinger</surname>
			</person>
			<person>
				<givenname>Jens</givenname>
				<surname>Teubner</surname>
			</person>
		</names>
		<date value="2008-12"/>
		<abstract>
			<richtext>
				<p>The Pathfinder project makes inventive use of relational database technology — originally developed to process data of strictly tabular shape — to construct efficient database — supported XML and XQuery processors. Pathfinder targets database engines that implement a set-oriented mode of query execution: many off-the-shelf traditional database systems make for suitable XQuery runtime environments, but a number of off-beat storage back-ends fit that bill as well. While Pathfinder has been developed with a close eye on the XQuery semantics, some of the techniques that we will review here will be generally useful to evaluate XQuery-style iterative languages on database back-ends.</p>
			</richtext>
		</abstract>
		<title type="sharef:secondaryTitle">IEEE Data Engineering Bulletin</title>
		<number>4</number>
		<pages>7-14</pages>
		<title type="sharef:primaryTitle">Pathfinder: XQuery Off the Relational Shelf</title>
		<field type="bibtex:topic">xquery[0.8]</field>
		<identifier type="sharef:uri" resourceType="application/pdf">http://sites.computer.org/debull/A08dec/pathfinder.pdf</identifier>
		<volume>31</volume>
	</reference>
	<reference name="wu08" src="bibtex:article" src-info="bibtex:line-4359" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Yuqing</givenname>
				<surname>Wu</surname>
			</person>
			<person>
				<givenname>Stelios</givenname>
				<surname>Paparizos</surname>
			</person>
			<person>
				<givenname>H. V.</givenname>
				<surname>Jagadish</surname>
			</person>
		</names>
		<date value="2008-12"/>
		<abstract>
			<richtext>
				<p>In this paper, we describe the TIMBER XML database system implemented at University of Michigan. TIMBER was one of the first native XML database systems, designed from the ground up to store and query semi-structured data. A distinctive principle of TIMBER is its algebraic underpinning. Central contributions of the TIMBER project include: (1) tree algebras that capture the structural nature of XML queries; (2) the stack-based family of algorithms to evaluate structural joins; (3) new rule-based query optimization techniques that take care of the heterogeneous nature of the intermediate results and take the schema information into consideration; (4) cost-based query optimization techniques and summary structures for result cardinality estimation; and (5) a family of structural indices for more efficient query evaluation. In this paper, we describe not only the architecture of TIMBER, its storage model, and engineering choices we made, but also present in hindsight, our retrospective on what went well and not so well with our design and engineering choices.</p>
			</richtext>
		</abstract>
		<title type="sharef:secondaryTitle">IEEE Data Engineering Bulletin</title>
		<number>4</number>
		<pages>15-24</pages>
		<title type="sharef:primaryTitle">Querying XML in TIMBER</title>
		<field type="bibtex:topic">xquery[0.8]</field>
		<identifier type="sharef:uri" resourceType="application/pdf">http://sites.computer.org/debull/A08dec/timber.pdf</identifier>
		<volume>31</volume>
	</reference>
	<reference name="ozc08" src="bibtex:article" src-info="bibtex:line-4373" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Fatma</givenname>
				<surname>Özcan</surname>
			</person>
			<person>
				<givenname>Normen</givenname>
				<surname>Seemann</surname>
			</person>
			<person>
				<givenname>Ling</givenname>
				<surname>Wang</surname>
			</person>
		</names>
		<date value="2008-12"/>
		<abstract>
			<richtext>
				<p>In this paper, we describe XQuery compilation and rewrite optimization in DB2 pureXML, a hybrid relational and XML database management system. DB2 pureXML has been designed to scale to large collections of XML data. In such a system, effective filtering of XML documents and efficient execution of XML navigation are vital for high throughput. Hence the focus of rewrite optimization is to consolidate navigation constructs as much as possible and to pushdown comparison predicates and navigation constructs into data access to enable index usage. In this paper, we describe the new rewrite transformations we have implemented specifically for XQuery and its navigational constructs. We also briefly discuss how some of the existing rewrite transformations developed for the SQL engine are extended and adapted for XQuery.</p>
			</richtext>
		</abstract>
		<title type="sharef:secondaryTitle">IEEE Data Engineering Bulletin</title>
		<number>4</number>
		<pages>25-32</pages>
		<title type="sharef:primaryTitle">XQuery Rewrite Optimization in IBM DB2 pureXML</title>
		<field type="bibtex:topic">xquery[0.8]</field>
		<identifier type="sharef:uri" resourceType="application/pdf">http://sites.computer.org/debull/A08dec/ibm.pdf</identifier>
		<volume>31</volume>
	</reference>
	<reference name="liu08b" src="bibtex:article" src-info="bibtex:line-4387" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Zhen Hua</givenname>
				<surname>Liu</surname>
			</person>
			<person>
				<givenname>Anguel</givenname>
				<surname>Novoselsky</surname>
			</person>
			<person>
				<givenname>Vikas</givenname>
				<surname>Arora</surname>
			</person>
		</names>
		<date value="2008-12"/>
		<abstract>
			<richtext>
				<p>Since the birth of XML, the processing of XML query languages like XQuery/XQueryP has been widely researched in the academic and industrial communities. Most of the approaches consider XQuery as a declarative query language similar to SQL, for which the iterator-based (stream-based), lazy evaluation processing strategy can be applied. The processing is combined with XML indexing, materialized view, XML view query rewrite over source data. An alternative approach views XQuery as a procedural programming language associated with eager, step-based evaluation, where each expression is fully evaluated by the end of the corresponding expression execution step. Usually, this approach uses a virtual machine running byte-code for compiled programs. In this paper, we share our experience of building a unified XQuery engine for the Oracle XML DB integrating both approaches. The key contribution of our approach is that the unified XQuery processor integrates both declarative and imperative XQuery/XQueryP processing paradigms. Furthermore, the processor is designed with a clean separation between the logical XML data model and the physical representation so that it can be optimized with various physical XML storages and data index and view models. We also discuss the challenges in our approach and our overall vision of the evolution of XQuery/XQueryP processors.</p>
			</richtext>
		</abstract>
		<title type="sharef:secondaryTitle">IEEE Data Engineering Bulletin</title>
		<number>4</number>
		<pages>33-40</pages>
		<title type="sharef:primaryTitle">Towards a Unified Declarative and Imperative XQuery Processor</title>
		<field type="bibtex:topic">xquery[0.8]</field>
		<identifier type="sharef:uri" resourceType="application/pdf">http://sites.computer.org/debull/A08dec/oracle.pdf</identifier>
		<volume>31</volume>
	</reference>
	<reference name="hol08" src="bibtex:article" src-info="bibtex:line-4401" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Mary</givenname>
				<surname>Holstege</surname>
			</person>
		</names>
		<date value="2008-12"/>
		<abstract>
			<richtext>
				<p>Increasingly, companies recognize that most of their important information does not exist in relational stores but in documents. For a long time, textual information has been relatively inaccessible and unusable. Database applications allow relational data to be used and re-used; the architecture of relational database systems allow such applications to function even in the face of large amounts of data. XML and XQuery now allow the creation of a new kind of application that unlocks content in a similar way: a content application. In this paper, we examine the technologies that enable content applications to operate at scale in the context of MarkLogic Server.</p>
			</richtext>
		</abstract>
		<title type="sharef:secondaryTitle">IEEE Data Engineering Bulletin</title>
		<number>4</number>
		<pages>41-48</pages>
		<title type="sharef:primaryTitle">Big, Fast XQuery: Enabling Content Applications</title>
		<field type="bibtex:topic">xquery[0.8]</field>
		<identifier type="sharef:uri" resourceType="application/pdf">http://sites.computer.org/debull/A08dec/marklogic.pdf</identifier>
		<volume>31</volume>
	</reference>
	<reference name="blo08" src="bibtex:article" src-info="bibtex:line-4415" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Michael</givenname>
				<surname>Blow</surname>
			</person>
			<person>
				<givenname>Vinayak</givenname>
				<surname>Borkar</surname>
			</person>
			<person>
				<givenname>Michael J.</givenname>
				<surname>Carey</surname>
			</person>
			<person>
				<givenname>Daniel</givenname>
				<surname>Engovatov</surname>
			</person>
			<person>
				<givenname>Dmitry</givenname>
				<surname>Lychagin</surname>
			</person>
			<person>
				<givenname>Panagiotis</givenname>
				<surname>Reveliotis</surname>
			</person>
			<person>
				<givenname>Joshua</givenname>
				<surname>Spiegel</surname>
			</person>
			<person>
				<givenname>Till</givenname>
				<surname>Westmann</surname>
			</person>
		</names>
		<date value="2008-12"/>
		<abstract>
			<richtext>
				<p>In this paper, we describe our experiences in building and evolving an XQuery engine with a focus on data and service federation use cases. The engine that we discuss is a core component of the BEA AquaLogic Data Services Platform product (recently re-released under the name Oracle Data Service Integrator). This XQuery engine was designed to provide efficient query and update capabilities over various classes of enterprise data sources, serving as the data access layer in a service-oriented architecture (SOA). The goal of this paper is to give an architectural overview of the engine, discussing some of the key implementation techniques that were employed as well as several XQuery language extensions that were introduced to address common data and service integration problems and challenges.</p>
			</richtext>
		</abstract>
		<title type="sharef:secondaryTitle">IEEE Data Engineering Bulletin</title>
		<number>4</number>
		<pages>49-56</pages>
		<title type="sharef:primaryTitle">Experiences with XQuery Processing for Data and Service Federation</title>
		<field type="bibtex:topic">xquery[0.8]</field>
		<identifier type="sharef:uri" resourceType="application/pdf">http://sites.computer.org/debull/A08dec/bea.pdf</identifier>
		<volume>31</volume>
	</reference>
	<reference name="cap08" src="bibtex:article" src-info="bibtex:line-4429" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Marc</givenname>
				<surname>Van Cappellen</surname>
			</person>
			<person>
				<givenname>Wouter</givenname>
				<surname>Cordewiner</surname>
			</person>
			<person>
				<givenname>Carlo</givenname>
				<surname>Innocenti</surname>
			</person>
		</names>
		<date value="2008-12"/>
		<abstract>
			<richtext>
				<p>Software infrastructures and applications more and more must deal with data available in a variety of different storage engines, accessible through a multitude of protocols and interfaces; and it is common that the size of the data involved requires streaming-based processing. This article shows how XQuery can leverage the XML Data Model to abstract the data physical details and to offer optimized processing allowing the development of highly scalable and performant data integration solutions.</p>
			</richtext>
		</abstract>
		<title type="sharef:secondaryTitle">IEEE Data Engineering Bulletin</title>
		<number>4</number>
		<pages>57-64</pages>
		<title type="sharef:primaryTitle">Data Aggregation, Heterogeneous Data Sources and Streaming Processing: How Can XQuery Help?</title>
		<field type="bibtex:topic">xquery[0.8]</field>
		<identifier type="sharef:uri" resourceType="application/pdf">http://sites.computer.org/debull/A08dec/datadirect.pdf</identifier>
		<volume>31</volume>
	</reference>
	<reference name="kay08" src="bibtex:article" src-info="bibtex:line-4443" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Michael</givenname>
				<surname>Kay</surname>
			</person>
		</names>
		<date value="2008-12"/>
		<abstract>
			<richtext>
				<p>This paper describes the internal features of the Saxon XQuery processor that make the most significant contribution to its speed of execution. For each of the features, an attempt is made to quantify the contribution, in most cases by comparing performance achieved when the feature is enabled or disabled.</p>
			</richtext>
		</abstract>
		<title type="sharef:secondaryTitle">IEEE Data Engineering Bulletin</title>
		<number>4</number>
		<pages>65-</pages>
		<title type="sharef:primaryTitle">Ten Reasons Why Saxon XQuery is Fast</title>
		<field type="bibtex:topic">xquery[0.8]</field>
		<identifier type="sharef:uri" resourceType="application/pdf">http://sites.computer.org/debull/A08dec/saxonica.pdf</identifier>
		<volume>31</volume>
	</reference>
	<reference name="dia06" src="bibtex:article" src-info="bibtex:line-4457" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Yanlei</givenname>
				<surname>Diao</surname>
			</person>
			<person>
				<givenname>Michael J.</givenname>
				<surname>Franklin</surname>
			</person>
		</names>
		<date value="2006"/>
		<abstract>
			<richtext>
				<p>We have developed YFilter, an XML filtering system that provides fast, on-the-fly matching of XML-encoded data to large numbers of query specifications containing constraints on both structure and content. YFilter encodes path expressions using a novel NFA-based approach that enables highly-efficient, shared processing for large numbers of XPath expressions. In this paper, we provide a brief technical overview of YFilter, focusing on the NFA model, its implementation, and its performance characteristics.</p>
			</richtext>
		</abstract>
		<title type="sharef:secondaryTitle">IEEE Data Engineering Bulletin</title>
		<number>1</number>
		<pages>41-48</pages>
		<title type="sharef:primaryTitle">High-Performance XML Filtering: An Overview of YFilter</title>
		<field type="bibtex:topic">yfilter[1]</field>
		<identifier type="sharef:uri" resourceType="application/postscript">http://sites.computer.org/debull/A03mar/yfilter.ps</identifier>
		<volume>26</volume>
	</reference>
	<reference name="wid99" src="bibtex:article" src-info="bibtex:line-4470" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Jennifer</givenname>
				<surname>Widom</surname>
			</person>
		</names>
		<date value="1999-09"/>
		<title type="sharef:secondaryTitle">IEEE Data Engineering Bulletin</title>
		<number>3</number>
		<pages>44-52</pages>
		<title type="sharef:primaryTitle">Data Management for XML: Research Directions</title>
		<field type="bibtex:topic">xml[0.8]</field>
		<identifier type="sharef:uri" resourceType="text/html">http://infolab.stanford.edu/~widom/xml-whitepaper.html</identifier>
		<volume>22</volume>
	</reference>
	<reference name="lee06" src="bibtex:article" src-info="bibtex:line-4487" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Choonhwa</givenname>
				<surname>Lee</surname>
			</person>
			<person>
				<givenname>Sumi</givenname>
				<surname>Helal</surname>
			</person>
			<person>
				<givenname>Wonjun</givenname>
				<surname>Lee</surname>
			</person>
		</names>
		<date value="2006"/>
		<abstract>
			<richtext>
				<p>A critical challenge facing the pervasive computing research community is the need to manage complex interactions among numerous interconnected computers and devices. In such a pervasive space, a given application's functionalities are partitioned and distributed across several computing devices that are spontaneously discovered and used. In recent years, researchers have devoted much attention to universal interactions with diverse devices in richly networked settings. We can categorize the numerous approaches explored into two groups: universal user interface languages and user interface remoting. We review recent noteworthy efforts for universal interactions using these two approaches. Such efforts aim to raise interoperability in interactive smart spaces by standardizing user interface languages or communication protocols.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1109/MPRV.2006.19</identifier>
		<title type="sharef:secondaryTitle">IEEE Pervasive Computing</title>
		<number>1</number>
		<pages>16-21</pages>
		<title type="sharef:primaryTitle">Universal Interactions with Smart Spaces</title>
		<identifier type="sharef:uri">http://ieeexplore.ieee.org/xpls/abs_all.jsp?arnumber=1593566</identifier>
		<volume>5</volume>
	</reference>
	<reference name="har08b" src="bibtex:article" src-info="bibtex:line-4500" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Björn</givenname>
				<surname>Hartmann</surname>
			</person>
			<person>
				<givenname>Scott</givenname>
				<surname>Doorley</surname>
			</person>
			<person>
				<givenname>Scott R.</givenname>
				<surname>Klemmer</surname>
			</person>
		</names>
		<date value="2008"/>
		<abstract>
			<richtext>
				<p>Learn about principles of opportunistic design through an interview study of 14 professional and hobbyist "mashers" from three design disciplines: Web 2.0, hardware, and ubiquitous computing.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1109/MPRV.2008.54</identifier>
		<title type="sharef:secondaryTitle">IEEE Pervasive Computing</title>
		<number>3</number>
		<pages>46-54</pages>
		<title type="sharef:primaryTitle">Hacking, Mashing, Gluing: Understanding Opportunistic Design</title>
		<identifier type="sharef:uri" resourceType="application/pdf">http://bjoern.org/papers/hartmann-pervasive2008.pdf</identifier>
		<identifier type="sharef:uri" resourceType="application/pdf">http://hci.stanford.edu/publications/2008/hackingmashinggluing.pdf</identifier>
		<volume>7</volume>
	</reference>
	<reference name="bar03b" src="bibtex:article" src-info="bibtex:line-4518" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Robert A.</givenname>
				<surname>Bartsch</surname>
			</person>
			<person>
				<givenname>Kristi M.</givenname>
				<surname>Cobern</surname>
			</person>
		</names>
		<date value="2003-06"/>
		<abstract>
			<richtext>
				<p>We investigated whether students liked and learned more from PowerPoint presentations than from overhead transparencies. Students were exposed to lectures supported by transparencies and two different types of PowerPoint presentations. At the end of the semester, students preferred PowerPoint presentations but this preference was not found on ratings taken immediately after the lectures. Students performed worse on quizzes when PowerPoint presentations included non-text items such as pictures and sound effects. A second study further examined these findings. In this study participants were shown PowerPoint slides that contained only text, contained text and a relevant picture, and contained text with a picture that was not relevant. Students performed worse on recall and recognition tasks and had greater dislike for slides with pictures that were not relevant. We conclude that PowerPoint can be beneficial, but material that is not pertinent to the presentation can be harmful to students' learning.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1016/S0360-1315(03)00027-7</identifier>
		<title type="sharef:secondaryTitle">Computers &amp; Education</title>
		<number>1</number>
		<pages>77-86</pages>
		<title type="sharef:primaryTitle">Effectiveness of PowerPoint Presentations in Lectures</title>
		<identifier type="sharef:uri">http://ieeexplore.ieee.org/xpls/abs_all.jsp?arnumber=1593566</identifier>
		<volume>41</volume>
	</reference>
	<reference name="sil06" src="bibtex:article" src-info="bibtex:line-4536" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Mário J.</givenname>
				<surname>Silva</surname>
			</person>
			<person>
				<givenname>Bruno</givenname>
				<surname>Martins</surname>
			</person>
			<person>
				<givenname>Marcirio Silveira</givenname>
				<surname>Chaves</surname>
			</person>
			<person>
				<givenname>Ana Paula</givenname>
				<surname>Afonso</surname>
			</person>
			<person>
				<givenname>Nuno</givenname>
				<surname>Cardoso</surname>
			</person>
		</names>
		<date value="2006-07"/>
		<abstract>
			<richtext>
				<p>Many web pages are rich in geographic information and primarily relevant to geographically limited communities. However, existing IR systems only recently began to offer local services and largely ignore geo-spatial information. This paper presents our work on automatically identifying the geographical scope of web documents, which provides the means to develop retrieval tools that take the geographical context into consideration. Our approach makes extensive use of an ontology of geographical concepts, and includes a system architecture for extracting geographic information from large collections of web documents. The proposed method involves recognising geographical references over the documents and assigning geographical scopes through a graph ranking algorithm. Initial evaluation results are encouraging, indicating the viability of this approach.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1016/j.compenvurbsys.2005.08.003</identifier>
		<title type="sharef:secondaryTitle">Computers, Environment and Urban Systems</title>
		<number>4</number>
		<pages>378-399</pages>
		<title type="sharef:primaryTitle">Adding Geographic Scopes to Web Resources</title>
		<volume>30</volume>
	</reference>
	<reference name="and03" src="bibtex:article" src-info="bibtex:line-4553" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Geoffrey</givenname>
				<surname>Anderson</surname>
			</person>
			<person>
				<givenname>Rafael</givenname>
				<surname>Moreno-Sanchez</surname>
			</person>
		</names>
		<date value="2003-03"/>
		<abstract>
			<richtext>
				<p>Geographic Information Systems (GIS) are moving from isolated, standalone, monolithic, proprietary systems working in a client-server architecture to smaller web-based applications and components offering specific geo-processing functionality and transparently exchanging data among them. Interoperability is at the core of this new web services model. Compliance with Open Specifications (OS) enables interoperability. Web-GIS software's high costs, complexity and special requirements have prevented many organizations from deploying their data and geo-processing capabilities over the World Wide Web. There are no-cost Open Source Software (OSS) alternatives to proprietary software for operating systems, web servers, and Relational Database Management Systems. We tested the potential of the combined use of OS and OSS to create web-based spatial information solutions. We present in detail the steps taken in creating a prototype system to support land use planning in Mexico with web-based geo-processing capabilities currently not present in commercial web-GIS products. We show that the process is straightforward and accessible to a broad audience of geographic information scientists and developers. We conclude that OS and OSS allow the development of web-based spatial information solutions that are low-cost, simple to implement, compatible with existing information technology infrastructure, and have the potential of interoperating with other systems and applications in the future.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1111/1467-9671.00158</identifier>
		<title type="sharef:secondaryTitle">Transactions in GIS</title>
		<number>4</number>
		<pages>447-466</pages>
		<title type="sharef:primaryTitle">Building Web-Based Spatial Information Solutions around Open Specifications and Open Source Software</title>
		<identifier type="sharef:uri">http://www.blackwell-synergy.com/doi/abs/10.1111/1467-9671.00158</identifier>
		<volume>7</volume>
	</reference>
	<reference name="mit04" src="bibtex:article" src-info="bibtex:line-4567" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Helena</givenname>
				<surname>Mitasova</surname>
			</person>
			<person>
				<givenname>Markus</givenname>
				<surname>Neteler</surname>
			</person>
		</names>
		<date value="2004-04"/>
		<identifier type="sharef:doi">10.1111/j.1467-9671.2004.00172.x</identifier>
		<title type="sharef:secondaryTitle">Transactions in GIS</title>
		<number>2</number>
		<pages>145-154</pages>
		<title type="sharef:primaryTitle">GRASS as Open Source Free Software GIS: Accomplishments and Perspectives</title>
		<identifier type="sharef:uri">http://www.blackwell-synergy.com/doi/abs/10.1111/j.1467-9671.2004.00172.x</identifier>
		<volume>8</volume>
	</reference>
	<reference name="dif77" src="bibtex:article" src-info="bibtex:line-4584" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Whitfield</givenname>
				<surname>Diffie</surname>
			</person>
			<person>
				<givenname>Martin E.</givenname>
				<surname>Hellman</surname>
			</person>
		</names>
		<date value="1976-11"/>
		<abstract>
			<richtext>
				<p>Two kinds of contemporary developments in cryptography are examined. Widening applications of teleprocessing have given rise to a need for new types of cryptographic systems, which minimize the need for secure key distribution channels and supply the equivalent of a written signature. This paper suggests ways to solve these currently open problems. It also discusses how the theories of communication and computation are beginning to provide the tools to solve cryptographic problems of long standing.</p>
			</richtext>
		</abstract>
		<title type="sharef:secondaryTitle">IEEE Transactions on Information Theory</title>
		<number>6</number>
		<pages>644-654</pages>
		<title type="sharef:primaryTitle">New Directions in Cryptography</title>
		<field type="bibtex:topic">diffiehellman[1]</field>
		<identifier type="sharef:uri" resourceType="application/pdf">http://www.cs.purdue.edu/homes/ninghui/courses/Fall04/lectures/diffie-hellman.pdf</identifier>
		<volume>22</volume>
	</reference>
	<reference name="ziv77" src="bibtex:article" src-info="bibtex:line-4598" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Jacob</givenname>
				<surname>Ziv</surname>
			</person>
			<person>
				<givenname>Abraham</givenname>
				<surname>Lempel</surname>
			</person>
		</names>
		<date value="1977-05"/>
		<title type="sharef:secondaryTitle">IEEE Transactions on Information Theory</title>
		<number>3</number>
		<pages>337-343</pages>
		<title type="sharef:primaryTitle">A Universal Algorithm for Sequential Data Compression</title>
		<field type="bibtex:topic">lz77[1]</field>
		<volume>23</volume>
	</reference>
	<reference name="bat93" src="bibtex:article" src-info="bibtex:line-4614" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>G. Di</givenname>
				<surname>Battista</surname>
			</person>
			<person>
				<givenname>M.</givenname>
				<surname>Lenzerini</surname>
			</person>
		</names>
		<date value="1993-06"/>
		<abstract>
			<richtext>
				<p>An entity relationship oriented model, that includes the notion of class, together with different types of assertions on classes, is presented. The assertions are used to model IS-A and disjointness relations both between entities and between relationships, part-of relations between entities and relationships, mandatory participation of an entity in a relationship, and interdependencies between the projections of relationships. The semantics of the model are defined in terms of first-order logic, and a sound and complete inference algorithm for such a model is presented. The algorithm is shown to have polynomial time complexity in the case where interdependencies on the projections of relationships are not taken into account. It is suggested that the model and the associated inference capabilities provide a suitable formal basis for designing an effective environment supporting conceptual modeling.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1109/69.224196</identifier>
		<title type="sharef:secondaryTitle">IEEE Transactions on Knowledge and Data Engineering</title>
		<number>3</number>
		<pages>439-450</pages>
		<title type="sharef:primaryTitle">Deductive Entity Relationship Modeling</title>
		<field type="bibtex:topic">er[0.9]</field>
		<identifier type="sharef:uri">http://portal.acm.org/citation.cfm?id=642848</identifier>
		<volume>5</volume>
	</reference>
	<reference name="mok06" src="bibtex:article" src-info="bibtex:line-4629" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Wai Yin</givenname>
				<surname>Mok</surname>
			</person>
			<person>
				<givenname>David W.</givenname>
				<surname>Embley</surname>
			</person>
		</names>
		<date value="2006-08"/>
		<abstract>
			<richtext>
				<p>As XML data becomes more and more prevalent and as larger quantities of data find their way into XML documents, the need for quality XML data organization will only increase. One standard way of structuring data well is to reduce and, if possible, eliminate redundancy, while at the same time making the storage structures as compact as possible. In this paper, we present a methodology to generate XML storage structures where conforming XML documents are redundancy-free, and for most practical cases, are also fully compact. Our methodology assumes the input is a conceptual-model hypergraph. For the special case that every edge in the hypergraph is binary, we present a simple algorithm, guaranteed to always generate redundancy-free storage structures. We show, however, that generating a minimum number of redundancy-free storage structures is NP-hard. We therefore provide heuristics to guide the process and observe that these heuristics result in satisfactory solutions, which are often optimal. We then present a general algorithm for n-ary edges and show that it generates redundancy-free storage structures. The general algorithm must overcome several problems that do not arise in the special case.</p>
			</richtext>
		</abstract>
		<title type="sharef:secondaryTitle">IEEE Transactions on Knowledge and Data Engineering</title>
		<number>8</number>
		<title type="sharef:primaryTitle">Generating Compact Redundancy-Free XML Documents from Conceptual-Model Hypergraphs</title>
		<field type="bibtex:topic">nnf[0.9]</field>
		<volume>18</volume>
	</reference>
	<reference name="zim80" src="bibtex:article" src-info="bibtex:line-4645" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Hubert</givenname>
				<surname>Zimmermann</surname>
			</person>
		</names>
		<date value="1980-04"/>
		<title type="sharef:secondaryTitle">IEEE Transactions on Communications</title>
		<number>4</number>
		<pages>425-432</pages>
		<title type="sharef:primaryTitle">OSI Reference Model — The ISO Model of Architecture for Open Systems Interconnection</title>
		<field type="bibtex:topic">osi[0.9]</field>
		<identifier type="sharef:uri">http://dl.comsoc.org/cocoon/comsoc/servlets/GetPublication?id=145613</identifier>
		<identifier type="sharef:uri" resourceType="application/pdf">http://www.comsoc.org/livepubs/50_journals/pdf/RightsManagement_eid=136833.pdf</identifier>
		<volume>28</volume>
	</reference>
	<reference name="cle91" src="bibtex:article" src-info="bibtex:line-4659" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>John G.</givenname>
				<surname>Cleary</surname>
			</person>
			<person>
				<givenname>Ian H.</givenname>
				<surname>Witten</surname>
			</person>
		</names>
		<date value="1984-04"/>
		<title type="sharef:secondaryTitle">IEEE Transactions on Communications</title>
		<number>4</number>
		<pages>396-402</pages>
		<title type="sharef:primaryTitle">Data Compression using Adaptive Coding and Partial String Matching</title>
		<field type="bibtex:topic">ppm[1]</field>
		<volume>32</volume>
	</reference>
	<reference name="von91" src="bibtex:article" src-info="bibtex:line-4671" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Guy</givenname>
				<surname>Vonderweit</surname>
			</person>
			<person>
				<givenname>John A.</givenname>
				<surname>Robinson</surname>
			</person>
			<person>
				<givenname>Chris</givenname>
				<surname>Toulson</surname>
			</person>
			<person>
				<givenname>Jim</givenname>
				<surname>Mastronardi</surname>
			</person>
			<person>
				<givenname>Eliot</givenname>
				<surname>Rubinov</surname>
			</person>
			<person>
				<givenname>Birendra</givenname>
				<surname>Prasada</surname>
			</person>
		</names>
		<date value="1991"/>
		<field type="bibtex:index">MICA</field>
		<title type="sharef:secondaryTitle">IEEE Transactions on Communications</title>
		<number>12</number>
		<pages>1875-1885</pages>
		<title type="sharef:primaryTitle">A Multipoint Communication Service for Interactive Applications</title>
		<volume>39</volume>
	</reference>
	<reference name="rob91" src="bibtex:article" src-info="bibtex:line-4682" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>John A.</givenname>
				<surname>Robinson</surname>
			</person>
			<person>
				<givenname>Eliot</givenname>
				<surname>Rubinov</surname>
			</person>
			<person>
				<givenname>Chris</givenname>
				<surname>Toulson</surname>
			</person>
			<person>
				<givenname>Birendra</givenname>
				<surname>Prasada</surname>
			</person>
			<person>
				<givenname>Shaker</givenname>
				<surname>Sabri</surname>
			</person>
			<person>
				<givenname>Naftaly</givenname>
				<surname>Goldberg</surname>
			</person>
			<person>
				<givenname>Guy</givenname>
				<surname>Vonderweit</surname>
			</person>
		</names>
		<date value="1991"/>
		<field type="bibtex:index">MICA</field>
		<title type="sharef:secondaryTitle">IEEE Transactions on Communications</title>
		<number>11</number>
		<pages>1698-1708</pages>
		<title type="sharef:primaryTitle">A Multimedia Interactive Conferencing Application for Personal Workstations</title>
		<volume>39</volume>
	</reference>
	<reference name="zha00" src="bibtex:article" src-info="bibtex:line-4697" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Yilin</givenname>
				<surname>Zhao</surname>
			</person>
		</names>
		<date value="2000-03"/>
		<abstract>
			<richtext>
				<p>Research and development on the technologies of locating the mobile (wireless) phone caller have been rapidly gaining momentum around the world. Once these technologies are mature enough to be deployed, they will have significant impact on automotive telematics and modern public transit systems. In this paper, we discuss why locating mobile phones becomes a hot topic among telecommunications giants, what technologies are being studied and standardized, when we are going to see the actual deployment, and what services they may provide? We then consider its potential impact on future intelligent transportation systems, including telematics and public transit systems. Many of us have already recognized how important a role the communications systems play in modern transportation. In the near future, if every mobile phone is able to determine its location, advances in our current transportation systems become inevitable</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1109/6979.869021</identifier>
		<title type="sharef:secondaryTitle">IEEE Transactions on Intelligent Transportation Systems</title>
		<number>1</number>
		<pages>55-64</pages>
		<title type="sharef:primaryTitle">Mobile Phone Location Determination and its Impact on Intelligent Transportation Systems</title>
		<volume>1</volume>
	</reference>
	<reference name="lan10" src="bibtex:article" src-info="bibtex:line-4714" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Nicholas D.</givenname>
				<surname>Lane</surname>
			</person>
			<person>
				<givenname>Emiliano</givenname>
				<surname>Miluzzo</surname>
			</person>
			<person>
				<givenname>Hong</givenname>
				<surname>Lu</surname>
			</person>
			<person>
				<givenname>Daniel</givenname>
				<surname>Peebles</surname>
			</person>
			<person>
				<givenname>Tanzeem</givenname>
				<surname>Choudhury</surname>
			</person>
			<person>
				<givenname>Andrew T.</givenname>
				<surname>Campbell</surname>
			</person>
		</names>
		<date value="2010-09"/>
		<abstract>
			<richtext>
				<p>Mobile phones or smartphones are rapidly becoming the central computer and communication device in people's lives. Application delivery channels such as the Apple AppStore are transforming mobile phones into App Phones, capable of downloading a myriad of applications in an instant. Importantly, today's smartphones are programmable and come with a growing set of cheap powerful embedded sensors, such as an accelerometer, digital compass, gyroscope, GPS, microphone, and camera, which are enabling the emergence of personal, group, and community-scale sensing applications. We believe that sensor-equipped mobile phones will revolutionize many sectors of our economy, including business, healthcare, social networks, environmental monitoring, and transportation. In this article we survey existing mobile phone sensing algorithms, applications, and systems. We discuss the emerging sensing paradigms, and formulate an architectural framework for discussing a number of the open issues and challenges emerging in the new area of mobile phone sensing research.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1109/MCOM.2010.5560598</identifier>
		<title type="sharef:secondaryTitle">IEEE Communications Magazine</title>
		<number>9</number>
		<pages>140-150</pages>
		<title type="sharef:primaryTitle">A Survey of Mobile Phone Sensing</title>
		<identifier type="sharef:uri" resourceType="application/pdf">http://www.cs.dartmouth.edu/~niclane/pubs/ieee_coms10.pdf</identifier>
		<volume>48</volume>
	</reference>
	<reference name="zha02" src="bibtex:article" src-info="bibtex:line-4728" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Yilin</givenname>
				<surname>Zhao</surname>
			</person>
		</names>
		<date value="2002-07"/>
		<abstract>
			<richtext>
				<p>Finding the location of the mobile phone is one of the important features of the 3G mobile communication system. Many valuable location-based services can be enabled by this new feature. Telecommunication managers and engineers are often puzzled by location terminologies and techniques as well as how to implement them, since location systems are not natural evolution from past generations of telecommunication systems. In this paper, we discuss briefly why locating mobile phone becomes a hot topic and what technologies are being studied. We then describe and clarify the latest standards issues surrounding the positioning methods specified for 3G systems. These include cell-ID-based, assisted GPS, and TDOA-based methods, such as OTDOA, E-OTD, and A-FLT</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1109/MCOM.2002.1018015</identifier>
		<title type="sharef:secondaryTitle">IEEE Communications Magazine</title>
		<number>7</number>
		<pages>108-116</pages>
		<title type="sharef:primaryTitle">Standardization of Mobile Phone Positioning for 3G Systems</title>
		<volume>40</volume>
	</reference>
	<reference name="ram02" src="bibtex:article" src-info="bibtex:line-4741" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Ram</givenname>
				<surname>Ramanathan</surname>
			</person>
			<person>
				<givenname>Jason</givenname>
				<surname>Redi</surname>
			</person>
		</names>
		<date value="2002-05"/>
		<identifier type="sharef:doi">10.1109/MCOM.2002.1006968</identifier>
		<title type="sharef:secondaryTitle">IEEE Communications Magazine</title>
		<number>5</number>
		<pages>20-22</pages>
		<title type="sharef:primaryTitle">A Brief Overview of Ad Hoc Networks: Challenges and Directions</title>
		<volume>40</volume>
	</reference>
	<reference name="ten97" src="bibtex:article" src-info="bibtex:line-4753" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>David L.</givenname>
				<surname>Tennenhouse</surname>
			</person>
			<person>
				<givenname>Jonathan M.</givenname>
				<surname>Smith</surname>
			</person>
			<person>
				<givenname>W. David</givenname>
				<surname>Sincoskie</surname>
			</person>
			<person>
				<givenname>David J.</givenname>
				<surname>Wetherall</surname>
			</person>
			<person>
				<givenname>Gary J.</givenname>
				<surname>Minden</surname>
			</person>
		</names>
		<date value="1997"/>
		<field type="bibtex:index">Active Networks</field>
		<title type="sharef:secondaryTitle">IEEE Communications Magazine</title>
		<number>1</number>
		<pages>80-86</pages>
		<title type="sharef:primaryTitle">A Survey of Active Network Research</title>
		<identifier type="sharef:uri" resourceType="text/html">http://citeseer.nj.nec.com/tennenhouse97survey.html</identifier>
		<volume>35</volume>
	</reference>
	<reference name="tru95" src="bibtex:article" src-info="bibtex:line-4765" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Hong Linh</givenname>
				<surname>Truong</surname>
			</person>
			<person>
				<givenname>William W.</givenname>
				<surname>Ellington</surname>
			</person>
			<person>
				<givenname>Jean-Yves</givenname>
				<surname>Le Boudec</surname>
			</person>
			<person>
				<givenname>Andreas X.</givenname>
				<surname>Meier</surname>
			</person>
			<person>
				<givenname>J. Wayne</givenname>
				<surname>Pace</surname>
			</person>
		</names>
		<date value="1995"/>
		<field type="bibtex:index">ATM, IP, multicast, LAN emulation</field>
		<title type="sharef:secondaryTitle">IEEE Communications Magazine</title>
		<number>5</number>
		<pages>70-85</pages>
		<title type="sharef:primaryTitle">LAN Emulation on an ATM Network</title>
		<volume>33</volume>
	</reference>
	<reference name="cha94" src="bibtex:article" src-info="bibtex:line-4776" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>H. Jonathan</givenname>
				<surname>Chao</surname>
			</person>
			<person>
				<givenname>Dipak</givenname>
				<surname>Ghosal</surname>
			</person>
			<person>
				<givenname>Debanjan</givenname>
				<surname>Saha</surname>
			</person>
			<person>
				<givenname>Satish K.</givenname>
				<surname>Tripathi</surname>
			</person>
		</names>
		<date value="1994"/>
		<field type="bibtex:index">ATM, IP, multicast, LAN</field>
		<title type="sharef:secondaryTitle">IEEE Communications Magazine</title>
		<number>8</number>
		<pages>52-59</pages>
		<title type="sharef:primaryTitle">IP on ATM Local Area Networks</title>
		<volume>32</volume>
	</reference>
	<reference name="cla92" src="bibtex:article" src-info="bibtex:line-4787" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>William J.</givenname>
				<surname>Clark</surname>
			</person>
		</names>
		<date value="1992"/>
		<field type="bibtex:index">MIAC, MIAS, ISDN</field>
		<title type="sharef:secondaryTitle">IEEE Communications Magazine</title>
		<number>5</number>
		<pages>44-50</pages>
		<title type="sharef:primaryTitle">Multipoint Multimedia Conferencing</title>
		<volume>30</volume>
	</reference>
	<reference name="hel78" src="bibtex:article" src-info="bibtex:line-4798" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Martin E.</givenname>
				<surname>Hellman</surname>
			</person>
		</names>
		<date value="1978-11"/>
		<title type="sharef:secondaryTitle">IEEE Communications Magazine</title>
		<number>6</number>
		<pages>24-32</pages>
		<title type="sharef:primaryTitle">An Overview of Public Key Cryptography</title>
		<field type="bibtex:topic">pkcs[1]</field>
		<identifier type="sharef:uri">http://dl.comsoc.org/cocoon/comsoc/servlets/GetPublication?id=103051</identifier>
		<identifier type="sharef:uri" resourceType="text/html">http://www.comsoc.org/livepubs/ci1/public/anniv/hellman.html</identifier>
		<identifier type="sharef:uri" resourceType="application/pdf">http://www.comsoc.org/livepubs/ci1/public/anniv/pdfs/hellman.pdf</identifier>
		<volume>16</volume>
	</reference>
	<reference name="est07" src="bibtex:article" src-info="bibtex:line-4817" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>María Ester</givenname>
				<surname>Lagos</surname>
			</person>
			<person>
				<givenname>Rosa</givenname>
				<surname>Alarcón</surname>
			</person>
			<person>
				<givenname>Miguel</givenname>
				<surname>Nussbaum</surname>
			</person>
			<person>
				<givenname>Francisca</givenname>
				<surname>Capponi</surname>
			</person>
		</names>
		<date value="2007"/>
		<abstract>
			<richtext>
				<p>The main difficulties in designing collaborative-learning applications are understanding which interactions between learners and teachers are the appropriate ones and then building software that takes such dynamics into account. Some researchers address this challenge by defining reusable components for specific learning tasks. The problems are that developers impose their particular solution, adapting components to requirement changes requires much effort, developers might lack the expertise to identify the appropriate group dynamics, and the resulting software might be used in unexpected ways. An approach based on an interaction model lets designers and educational experts specify the interactions in a learning activity. They can then define a set of reusable interaction components. The resulting flexible model is the basis for a flexible architecture that lets you create, extend, reuse, and compose diverse educational software products.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1109/MS.2007.111</identifier>
		<title type="sharef:secondaryTitle">IEEE Software</title>
		<number>4</number>
		<pages>80-89</pages>
		<title type="sharef:primaryTitle">Interaction-Based Design for Mobile Collaborative-Learning Software</title>
		<volume>24</volume>
	</reference>
	<reference name="hoh05" src="bibtex:article" src-info="bibtex:line-4829" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Gregor</givenname>
				<surname>Hohpe</surname>
			</person>
		</names>
		<date value="2005"/>
		<abstract>
			<richtext>
				<p>Asynchronous processing models can be highly efficient but are not without challenges. If the real world writes the best stories, then maybe we can learn something from Starbucks about designing successful asynchronous messaging solutions.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1109/MS.2005.52</identifier>
		<title type="sharef:secondaryTitle">IEEE Software</title>
		<number>2</number>
		<pages>64-66</pages>
		<title type="sharef:primaryTitle">Your Coffee Shop Doesn't Use Two-Phase Commit</title>
		<identifier type="sharef:uri" resourceType="application/pdf">http://www.enterpriseintegrationpatterns.com/docs/IEEE_Software_Design_2PC.pdf</identifier>
		<volume>22</volume>
	</reference>
	<reference name="fow03b" src="bibtex:article" src-info="bibtex:line-4842" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Martin</givenname>
				<surname>Fowler</surname>
			</person>
		</names>
		<date value="2003"/>
		<identifier type="sharef:doi">10.1109/MS.2003.1231144</identifier>
		<title type="sharef:secondaryTitle">IEEE Software</title>
		<number>5</number>
		<pages>11-13</pages>
		<title type="sharef:primaryTitle">Who Needs an Architect?</title>
		<identifier type="sharef:uri" resourceType="application/pdf">http://www.martinfowler.com/ieeeSoftware/whoNeedsArchitect.pdf</identifier>
		<volume>20</volume>
	</reference>
	<reference name="fow02b" src="bibtex:article" src-info="bibtex:line-4854" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Martin</givenname>
				<surname>Fowler</surname>
			</person>
		</names>
		<date value="2002"/>
		<identifier type="sharef:doi">10.1109/52.991326</identifier>
		<title type="sharef:secondaryTitle">IEEE Software</title>
		<number>2</number>
		<pages>18-19</pages>
		<title type="sharef:primaryTitle">Public versus Published Interfaces</title>
		<identifier type="sharef:uri" resourceType="application/pdf">http://martinfowler.com/ieeeSoftware/published.pdf</identifier>
		<volume>19</volume>
	</reference>
	<reference name="bor85" src="bibtex:article" src-info="bibtex:line-4866" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Alexander</givenname>
				<surname>Borgida</surname>
			</person>
		</names>
		<date value="1985"/>
		<abstract>
			<richtext>
				<p>A computer system which stores, retrieves and manipulates information about some portion of the real world can be viewed as a model of that domain of discourse. There has been considerable research recently on languages which allow one to capture more of the semantics of the real world in these computerized Information Systems — research which has variously been labelled as Semantic Data Modeling, Semantic Modeling or Conceptual Modeling. This review paper presents a list of the features which appear to distinguish these languages from those traditionally used to describe and develop database-intensive applications, and considers the motivation for these features as well as the potential advantages to be gained through their use. The paper, which is intended for those familiar with current data processing practices, also compares in greater detail four programming languages which incorporate semantic modeling facilities, and discusses some of the methodologies and tools for Information System development based on these languages.</p>
			</richtext>
		</abstract>
		<title type="sharef:secondaryTitle">IEEE Software</title>
		<number>1</number>
		<pages>63-72</pages>
		<title type="sharef:primaryTitle">Features of Languages for the Development of Information Systems at the Conceptual Level</title>
		<identifier type="sharef:uri" resourceType="application/pdf">http://www.cs.umbc.edu/771/papers/CML-features.pdf</identifier>
		<volume>2</volume>
	</reference>
	<reference name="cap05" src="bibtex:article" src-info="bibtex:line-4878" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Guy</givenname>
				<surname>Caplat</surname>
			</person>
			<person>
				<givenname>Jean-Louis</givenname>
				<surname>Sourrouille</surname>
			</person>
		</names>
		<date value="2005"/>
		<abstract>
			<richtext>
				<p>The Object Management Group's model driven architecture defines a system development approach that formally separates system specification from platform implementations — in platform-independent models and platform-specific models, respectively. According to MDA, software development involves a sequence of model mappings that transform an initial PIM to a final PSM that is precise enough for direct translation into an executable program. A mapping is a set of rules and techniques for translating one model into another. When the starting and final models are expressed in the same formalism, the mapping is said to be intralanguage; otherwise, it is interlanguage. We focus here on interlanguage mapping, showing the central role of formalism extension mechanisms in managing the abstraction-level gap between languages as well as the platform-level details of specific implementations.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1109/MS.2005.45</identifier>
		<title type="sharef:secondaryTitle">IEEE Software</title>
		<number>2</number>
		<pages>44-51</pages>
		<title type="sharef:primaryTitle">Model Mapping Using Formalism Extensions</title>
		<volume>22</volume>
	</reference>
	<reference name="won10" src="bibtex:article" src-info="bibtex:line-4894" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Angus K. Y.</givenname>
				<surname>Wong</surname>
			</person>
		</names>
		<date value="2010"/>
		<abstract>
			<richtext>
				<p>The mobile Internet and location-enabled mobile devices have become increasingly popular, inspiring a new type of communication network. This near-me area network (NAN) focuses on communication among wireless devices in close proximity, creating a new kind of application domain. This article introduces NAN and reviews existing applications and challenges.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1109/MIC.2010.49</identifier>
		<title type="sharef:secondaryTitle">IEEE Internet Computing</title>
		<number>2</number>
		<pages>74-77</pages>
		<title type="sharef:primaryTitle">The Near-Me Area Network</title>
		<volume>14</volume>
	</reference>
	<reference name="kop07" src="bibtex:article" src-info="bibtex:line-4906" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Jacek</givenname>
				<surname>Kopecký</surname>
			</person>
			<person>
				<givenname>Tomas</givenname>
				<surname>Vitvar</surname>
			</person>
			<person>
				<givenname>Carine</givenname>
				<surname>Bournez</surname>
			</person>
			<person>
				<givenname>Joel</givenname>
				<surname>Farrell</surname>
			</person>
		</names>
		<date value="2007"/>
		<abstract>
			<richtext>
				<p>Web services are important for creating distributed applications on the Web. In fact, they're a key enabler for service-oriented architectures that focus on service reuse and interoperability. The World Wide Web Consortium (W3C) has recently finished work on two important standards for describing Web services the Web Services Description Language (WSDL) 2.0 and Semantic Annotations for WSDL and XML Schema (SAWSDL). Here, the authors discuss the latter, which is the first standard for adding semantics to Web service descriptions.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1109/MIC.2007.134</identifier>
		<title type="sharef:secondaryTitle">IEEE Internet Computing</title>
		<number>6</number>
		<pages>60-67</pages>
		<title type="sharef:primaryTitle">SAWSDL: Semantic Annotations for WSDL and XML Schema</title>
		<field type="bibtex:topic">sawsdl[1] wsdl[0.9] xsd[0.9]</field>
		<volume>11</volume>
	</reference>
	<reference name="she07" src="bibtex:article" src-info="bibtex:line-4919" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Amit P.</givenname>
				<surname>Sheth</surname>
			</person>
			<person>
				<givenname>Karthik</givenname>
				<surname>Gomadam</surname>
			</person>
			<person>
				<givenname>Jon</givenname>
				<surname>Lathem</surname>
			</person>
		</names>
		<date value="2007"/>
		<abstract>
			<richtext>
				<p>Services based on the representational state transfer (REST) paradigm, a lightweight implementation of a service-oriented architecture, have found even greater success than their heavyweight siblings, which are based on the Web Services Description Language (WSDL) and SOAP. By using XML-based messaging, RESTful services can bring together discrete data from different services to create meaningful data sets; mashups such as these are extremely popular today.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1109/MIC.2007.133</identifier>
		<title type="sharef:secondaryTitle">IEEE Internet Computing</title>
		<number>6</number>
		<pages>91-94</pages>
		<title type="sharef:primaryTitle">SA-REST: Semantically Interoperable and Easier-to-Use Services and Mashups</title>
		<field type="bibtex:topic">sarest[1] rest[0.9]</field>
		<volume>11</volume>
	</reference>
	<reference name="nat09" src="bibtex:article" src-info="bibtex:line-4932" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Preethi</givenname>
				<surname>Natarajan</surname>
			</person>
			<person>
				<givenname>Fred</givenname>
				<surname>Baker</surname>
			</person>
			<person>
				<givenname>Paul D.</givenname>
				<surname>Amer</surname>
			</person>
			<person>
				<givenname>Jonathan T.</givenname>
				<surname>Leighton</surname>
			</person>
		</names>
		<date value="2009"/>
		<abstract>
			<richtext>
				<p>The Stream Control Transmission Protocol (SCTP) is a general-purpose IETF transport protocol with kernel implementations on various platforms. Similar to TCP, SCTP provides a connection-oriented, reliable, congestion and flow-controlled layer 4 channel. Unlike both TCP and UDP, however, SCTP offers new delivery options that better match diverse applications' needs.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1109/MIC.2009.114</identifier>
		<title type="sharef:secondaryTitle">IEEE Internet Computing</title>
		<number>5</number>
		<pages>81-85</pages>
		<title type="sharef:primaryTitle">SCTP: What, Why, and How</title>
		<field type="bibtex:topic">sctp[0.9]</field>
		<volume>13</volume>
	</reference>
	<reference name="wei07b" src="bibtex:article" src-info="bibtex:line-4945" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Daniel J.</givenname>
				<surname>Weitzner</surname>
			</person>
		</names>
		<date value="2007"/>
		<abstract>
			<richtext>
				<p>A new form of personal identity is emerging on the Web. Decentralized identification protocols depart from traditional distributed authentication approaches developed for the Internet. What distinguishes this new approach is its use of URIs as the underlying identifier.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1109/MIC.2007.95</identifier>
		<title type="sharef:secondaryTitle">IEEE Internet Computing</title>
		<number>4</number>
		<pages>72-76</pages>
		<title type="sharef:primaryTitle">Whose Name Is It, Anyway? Decentralized Identity Systems on the Web</title>
		<volume>11</volume>
	</reference>
	<reference name="cer02b" src="bibtex:article" src-info="bibtex:line-4957" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Stefano</givenname>
				<surname>Ceri</surname>
			</person>
			<person>
				<givenname>Piero</givenname>
				<surname>Fraternali</surname>
			</person>
			<person>
				<givenname>Maristella</givenname>
				<surname>Matera</surname>
			</person>
		</names>
		<date value="2002"/>
		<abstract>
			<richtext>
				<p>This paper provides some abstractions and roadmaps for interpreting data-intensive Web applications. This class of applications is characterized by the underlying existence of large data sets, organized within a repository or database, and therefore must obey some typical patterns and rules for the effective management of information. The purpose of this paper is to explain such patterns and rules in terms of WebML, a formal Web modeling language, for specifying the content structure of the Web application and the organization and presentation of such content in a hypertext. In particular, the paper shows that data-intensive Web sites can be abstracted as complex arrangements of elementary structures, called skeletons, which are pairs of structural diagrams (describing data organizations) and site view diagrams (describing navigational patterns). The essence of the proposed method is the classification of the role that concepts may play within the Web application information content, so that it can be abstracted and reduced to few, fundamental entities and relationships, organized according to an E/R diagram. Such a classification then feeds the identification of WebML skeletons.</p>
			</richtext>
		</abstract>
		<title type="sharef:secondaryTitle">IEEE Internet Computing</title>
		<number>4</number>
		<pages>20-30</pages>
		<title type="sharef:primaryTitle">Conceptual Modeling of Data-Intensive Web Applications</title>
		<identifier type="sharef:uri" resourceType="application/pdf">http://www.webml.org/webml/upload/ent5/1/IC.pdf</identifier>
		<volume>6</volume>
	</reference>
	<reference name="huh05" src="bibtex:article" src-info="bibtex:line-4969" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Michael N.</givenname>
				<surname>Huhns</surname>
			</person>
			<person>
				<givenname>Munindar P.</givenname>
				<surname>Singh</surname>
			</person>
		</names>
		<date value="2005"/>
		<abstract>
			<richtext>
				<p>Traditional approaches to software development — the ones embodied in CASE tools and modeling frameworks — are appropriate for building individual software components, but they are not designed to face the challenges of open environments. Service-oriented computing provides a way to create a new architecture that reflects components' trends toward autonomy and heterogeneity.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1109/MIC.2005.21</identifier>
		<title type="sharef:secondaryTitle">IEEE Internet Computing</title>
		<number>1</number>
		<pages>75-81</pages>
		<title type="sharef:primaryTitle">Service-Oriented Computing: Key Concepts and Principles</title>
		<identifier type="sharef:uri" resourceType="application/pdf">http://www.cse.sc.edu/~huhns/journalpapers/V9N1soc.pdf</identifier>
		<volume>9</volume>
	</reference>
	<reference name="say05" src="bibtex:article" src-info="bibtex:line-4982" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Robert</givenname>
				<surname>Sayre</surname>
			</person>
		</names>
		<date value="2005"/>
		<abstract>
			<richtext>
				<p>Early syndication and publishing protocols faced various problems related to interoperability, scalability, and extensibility. The Atom format and protocol builds on earlier efforts to establish an open, extensible, interoperable, and clearly specified framework for Web-logging applications. Atom has already been deployed on a wide variety of platforms. By closely examining previous syndication formats and protocols, the AtomPub working group has been able to "pave the footpaths", and design a standard built around well-known and proven usage patterns.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1109/MIC.2005.74</identifier>
		<title type="sharef:secondaryTitle">IEEE Internet Computing</title>
		<number>4</number>
		<pages>71-78</pages>
		<title type="sharef:primaryTitle">Atom: The Standard in Syndication</title>
		<field type="bibtex:topic">atom[0.9] atompub[0.9]</field>
		<volume>9</volume>
	</reference>
	<reference name="hau09a" src="bibtex:article" src-info="bibtex:line-4995" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Michael</givenname>
				<surname>Hausenblas</surname>
			</person>
		</names>
		<date value="2009"/>
		<abstract>
			<richtext>
				<p>Semantic Web technologies have been around for a while. However, such technologies have had little impact on the development of real-world Web applications to date. With linked data, this situation has changed dramatically in the past few months. This article shows how linked data sets can be exploited to build rich Web applications with little effort.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1109/MIC.2009.79</identifier>
		<title type="sharef:secondaryTitle">IEEE Internet Computing</title>
		<number>4</number>
		<pages>68-73</pages>
		<title type="sharef:primaryTitle">Exploiting Linked Data to Build Web Applications</title>
		<volume>13</volume>
	</reference>
	<reference name="vog03" src="bibtex:article" src-info="bibtex:line-5007" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Werner</givenname>
				<surname>Vogels</surname>
			</person>
		</names>
		<date value="2003-12"/>
		<abstract>
			<richtext>
				<p>Web services are frequently described as the latest incarnation of distributed object technology. This misconception, perpetuated by people from both industry and academia, seriously limits broader acceptance of the true Web services architecture. Although the architects of many distributed and Internet systems have been vocal about the differences between Web services and distributed objects, dispelling the myth that they are closely related appears difficult. Many believe that Web services is a distributed systems technology that relies on some form of distributed object technology. Unfortunately, this is not the only common misconception about Web services. We seek to clarify several widely held beliefs about the technology that are partially or completely wrong. Within the distributed technology world, it is probably more appropriate to associate Web services with messaging technologies because they share a common architectural view, although they address different application types. Web services technology will have a dramatic enabling effect on worldwide interoperable distributed computing once everyone recognizes that Web services are about interoperable document-centric computing, not distributed objects.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1109/MIC.2003.1250585</identifier>
		<title type="sharef:secondaryTitle">IEEE Internet Computing</title>
		<number>6</number>
		<pages>59-66</pages>
		<title type="sharef:primaryTitle">Web Services are not Distributed Objects</title>
		<identifier type="sharef:uri">http://ieeexplore.ieee.org/xpls/abs_all.jsp?arnumber=1250585</identifier>
		<volume>7</volume>
	</reference>
	<reference name="wil03l" src="bibtex:article" src-info="bibtex:line-5021" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Erik</givenname>
				<surname>Wilde</surname>
			</person>
		</names>
		<date value="2003-09"/>
		<abstract>
			<richtext>
				<p>XML technologies are very popular, and one of the most important reasons for this is the availability of tools and technologies for working with XML, eliminating the need to build XML processing from scratch. However, XML technologies are built on top of inherent (and not always well-defined) information models, and this may cause problems because (1) the information models of some tools may not support the required "view" of XML, or (2) there is no appropriate data model to work with the information model in question. In this article, we approach this question from the systematic side, and describe the most prominent XML technologies with regard to their information and data models.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1109/MIC.2003.1232521</identifier>
		<title type="sharef:secondaryTitle">IEEE Internet Computing</title>
		<number>5</number>
		<pages>74-78</pages>
		<title type="sharef:primaryTitle">XML Technologies Dissected</title>
		<field type="bibtex:topic">xml[0.7]</field>
		<identifier type="sharef:uri">http://dret.net/netdret/publications#wil03l</identifier>
		<identifier type="sharef:uri">http://ieeexplore.ieee.org/search/wrapper.jsp?arnumber=1232521</identifier>
		<volume>7</volume>
	</reference>
	<reference name="vin05b" src="bibtex:article" src-info="bibtex:line-5037" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Steve</givenname>
				<surname>Vinoski</surname>
			</person>
		</names>
		<date value="2005-11"/>
		<identifier type="sharef:doi">10.1109/MIC.2005.131</identifier>
		<title type="sharef:secondaryTitle">IEEE Internet Computing</title>
		<number>6</number>
		<pages>72-74</pages>
		<title type="sharef:primaryTitle">Old Measures for New Services</title>
		<identifier type="sharef:uri" resourceType="application/pdf">http://steve.vinoski.net/pdf/IEEE-Old_Measures_for_New_Services.pdf</identifier>
		<volume>9</volume>
	</reference>
	<reference name="vin08" src="bibtex:article" src-info="bibtex:line-5050" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Steve</givenname>
				<surname>Vinoski</surname>
			</person>
		</names>
		<date value="2008-01"/>
		<identifier type="sharef:doi">10.1109/MIC.2008.20</identifier>
		<title type="sharef:secondaryTitle">IEEE Internet Computing</title>
		<number>1</number>
		<pages>84-87</pages>
		<title type="sharef:primaryTitle">Serendipitous Reuse</title>
		<identifier type="sharef:uri" resourceType="application/pdf">http://steve.vinoski.net/pdf/IEEE-Serendipitous_Reuse.pdf</identifier>
		<volume>12</volume>
	</reference>
	<reference name="vin08b" src="bibtex:article" src-info="bibtex:line-5063" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Steve</givenname>
				<surname>Vinoski</surname>
			</person>
		</names>
		<date value="2008-03"/>
		<abstract>
			<richtext>
				<p>Compared to approaches such as Web services and the Web Services Description Language (WSDL), which promote specialization for each service interface, the uniform-interface constraint reduces client-server coupling and helps minimize gratuitous differences in interface and method semantics across disparate resources. REST isn't a silver bullet, but its flexibility and relative simplicity make it highly applicable not only to Web-scale systems but also to a wide variety of enterprise integration problems. The representational state transfer (REST) architectural style, on the other hand, makes very specific and highly useful trade-offs meticulously chosen to enhance the scalability, extensibility, manageability, and maintainability of distributed systems and applications.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1109/MIC.2008.33</identifier>
		<title type="sharef:secondaryTitle">IEEE Internet Computing</title>
		<number>2</number>
		<pages>87-90</pages>
		<title type="sharef:primaryTitle">Demystifying RESTful Data Coupling</title>
		<field type="bibtex:topic">rest[0.9]</field>
		<identifier type="sharef:uri" resourceType="application/pdf">http://steve.vinoski.net/pdf/IEEE-Demystifying_RESTful_Data_Coupling.pdf</identifier>
		<volume>12</volume>
	</reference>
	<reference name="vin08c" src="bibtex:article" src-info="bibtex:line-5078" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Steve</givenname>
				<surname>Vinoski</surname>
			</person>
		</names>
		<date value="2008-11"/>
		<abstract>
			<richtext>
				<p>Representational State Transfer (REST) architectural style proponents describe it as being easy, but this in no way implies that REST is trivial or simplistic, nor does it mean that RESTful systems lack sophistication. The author covers the primary areas that developers must continually consider as they design and build Web services. Tools can certainly provide reminders about these areas and help to track progress, but ultimately, developers must understand the underlying technical issues to be able to make suitable design and implementation choices.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1109/MIC.2008.130</identifier>
		<title type="sharef:secondaryTitle">IEEE Internet Computing</title>
		<number>6</number>
		<pages>94-96</pages>
		<title type="sharef:primaryTitle">RESTful Web Services Development Checklist</title>
		<field type="bibtex:topic">rest[0.9]</field>
		<identifier type="sharef:uri" resourceType="application/pdf">http://steve.vinoski.net/pdf/IEEE-RESTful_Web_Services_Development_Checklist.pdf</identifier>
		<volume>12</volume>
	</reference>
	<reference name="vin08d" src="bibtex:article" src-info="bibtex:line-5093" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Steve</givenname>
				<surname>Vinoski</surname>
			</person>
		</names>
		<date value="2008-09"/>
		<title type="sharef:secondaryTitle">IEEE Internet Computing</title>
		<number>5</number>
		<pages>92-95</pages>
		<title type="sharef:primaryTitle">RPC and REST: Dilemma, Disruption, and Displacement</title>
		<field type="bibtex:topic">rest[0.9] rpc[0.9]</field>
		<identifier type="sharef:uri" resourceType="application/pdf">http://steve.vinoski.net/pdf/IEEE-RPC_and_REST_Dilemma_Disruption_and_Displacement.pdf</identifier>
		<volume>12</volume>
	</reference>
	<reference name="vin03" src="bibtex:article" src-info="bibtex:line-5106" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Steve</givenname>
				<surname>Vinoski</surname>
			</person>
		</names>
		<date value="2003-05"/>
		<title type="sharef:secondaryTitle">IEEE Internet Computing</title>
		<number>3</number>
		<pages>88-90</pages>
		<title type="sharef:primaryTitle">It's Just a Mapping Problem</title>
		<identifier type="sharef:uri" resourceType="text/html">http://csdl.computer.org/comp/mags/ic/2003/03/w3088abs.htm</identifier>
		<volume>7</volume>
	</reference>
	<reference name="vin04a" src="bibtex:article" src-info="bibtex:line-5118" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Steve</givenname>
				<surname>Vinoski</surname>
			</person>
		</names>
		<date value="2004-03"/>
		<title type="sharef:secondaryTitle">IEEE Internet Computing</title>
		<number>2</number>
		<pages>86-90</pages>
		<title type="sharef:primaryTitle">Web Services Notifications</title>
		<field type="bibtex:topic">wseventing[0.8] wsevents[0.8]</field>
		<identifier type="sharef:uri" resourceType="application/pdf">http://www.iona.com/hyplan/vinoski/pdfs/IEEE-Web_Services_Notifications.pdf</identifier>
		<volume>8</volume>
	</reference>
	<reference name="vin04b" src="bibtex:article" src-info="bibtex:line-5131" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Steve</givenname>
				<surname>Vinoski</surname>
			</person>
		</names>
		<date value="2004-05"/>
		<title type="sharef:secondaryTitle">IEEE Internet Computing</title>
		<number>3</number>
		<pages>90-93</pages>
		<title type="sharef:primaryTitle">More Web Services Notifications</title>
		<field type="bibtex:topic">wsnotification[0.8]</field>
		<identifier type="sharef:uri" resourceType="application/pdf">http://www.iona.com/hyplan/vinoski/pdfs/IEEE-More_Web_Services_Notifications.pdf</identifier>
		<identifier type="sharef:uri" resourceType="text/html">http://dsonline.computer.org/0405/d/w3towp.htm</identifier>
		<volume>8</volume>
	</reference>
	<reference name="vin04c" src="bibtex:article" src-info="bibtex:line-5145" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Steve</givenname>
				<surname>Vinoski</surname>
			</person>
		</names>
		<date value="2004-07"/>
		<title type="sharef:secondaryTitle">IEEE Internet Computing</title>
		<number>4</number>
		<pages>81-84</pages>
		<title type="sharef:primaryTitle">Dark Matter Revisited</title>
		<field type="bibtex:topic">eai[0.8]</field>
		<identifier type="sharef:uri" resourceType="text/html">http://dsonline.computer.org/0407/d/w4tow.htm</identifier>
		<volume>8</volume>
	</reference>
	<reference name="pat03" src="bibtex:article" src-info="bibtex:line-5158" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Sanjay</givenname>
				<surname>Patil</surname>
			</person>
			<person>
				<givenname>Eric</givenname>
				<surname>Newcomer</surname>
			</person>
		</names>
		<date value="2003-05"/>
		<title type="sharef:secondaryTitle">IEEE Internet Computing</title>
		<number>3</number>
		<pages>74-82</pages>
		<title type="sharef:primaryTitle">ebXML and Web Services</title>
		<field type="bibtex:topic">ebxml[0.8]</field>
		<identifier type="sharef:uri" resourceType="text/html">http://dsonline.computer.org/0305/f/wp3spot.htm</identifier>
		<volume>7</volume>
	</reference>
	<reference name="sri03" src="bibtex:article" src-info="bibtex:line-5171" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Krishnamurthy</givenname>
				<surname>Srinivasan</surname>
			</person>
			<person>
				<givenname>Pallavi G.</givenname>
				<surname>Malu</surname>
			</person>
			<person>
				<givenname>George</givenname>
				<surname>Moakley</surname>
			</person>
		</names>
		<date value="2003-05"/>
		<title type="sharef:secondaryTitle">IEEE Internet Computing</title>
		<number>3</number>
		<pages>66-73</pages>
		<title type="sharef:primaryTitle">Automatic Multibusiness Transactions</title>
		<field type="bibtex:topic">thp[0.9]</field>
		<identifier type="sharef:uri" resourceType="text/html">http://csdl.computer.org/comp/mags/ic/2003/03/w3066abs.htm</identifier>
		<volume>7</volume>
	</reference>
	<reference name="dal03" src="bibtex:article" src-info="bibtex:line-5184" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Sanjay</givenname>
				<surname>Dalal</surname>
			</person>
			<person>
				<givenname>Sazi</givenname>
				<surname>Temel</surname>
			</person>
			<person>
				<givenname>Mark</givenname>
				<surname>Little</surname>
			</person>
			<person>
				<givenname>Mark</givenname>
				<surname>Potts</surname>
			</person>
			<person>
				<givenname>Jim</givenname>
				<surname>Webber</surname>
			</person>
		</names>
		<date value="2003-01"/>
		<title type="sharef:secondaryTitle">IEEE Internet Computing</title>
		<number>1</number>
		<pages>30-39</pages>
		<title type="sharef:primaryTitle">Coordinating Business Transactions on the Web</title>
		<field type="bibtex:topic">btp[0.9]</field>
		<identifier type="sharef:uri" resourceType="text/html">http://csdl.computer.org/comp/mags/ic/2003/01/w1030abs.htm</identifier>
		<volume>7</volume>
	</reference>
	<reference name="sim03" src="bibtex:article" src-info="bibtex:line-5197" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Fabio</givenname>
				<surname>Simeoni</surname>
			</person>
			<person>
				<givenname>David</givenname>
				<surname>Lievens</surname>
			</person>
			<person>
				<givenname>Richard</givenname>
				<surname>Connor</surname>
			</person>
			<person>
				<givenname>Paolo</givenname>
				<surname>Manghi</surname>
			</person>
		</names>
		<date value="2003-01"/>
		<title type="sharef:secondaryTitle">IEEE Internet Computing</title>
		<number>1</number>
		<pages>19-27</pages>
		<title type="sharef:primaryTitle">Language Bindings to XML</title>
		<field type="bibtex:topic">dom[0.7] sax[0.7] jaxb[0.7] snaque[0.9]</field>
		<identifier type="sharef:uri" resourceType="text/html">http://csdl.computer.org/comp/mags/ic/2003/01/w1019abs.htm</identifier>
		<identifier type="sharef:uri" resourceType="application/pdf">http://www.cis.strath.ac.uk/~david/papers/ieeeic2002.pdf</identifier>
		<volume>7</volume>
	</reference>
	<reference name="fel03" src="bibtex:article" src-info="bibtex:line-5211" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Pascal</givenname>
				<surname>Felber</surname>
			</person>
			<person>
				<givenname>Chee-Yong</givenname>
				<surname>Chan</surname>
			</person>
			<person>
				<givenname>Minos N.</givenname>
				<surname>Garofalakis</surname>
			</person>
			<person>
				<givenname>Rajeev</givenname>
				<surname>Rastogi</surname>
			</person>
		</names>
		<date value="2003-01"/>
		<title type="sharef:secondaryTitle">IEEE Internet Computing</title>
		<number>1</number>
		<pages>49-57</pages>
		<title type="sharef:primaryTitle">Scalable Filtering of XML Data for Web Services</title>
		<identifier type="sharef:uri" resourceType="text/html">http://csdl.computer.org/comp/mags/ic/2003/01/w1049abs.htm</identifier>
		<volume>7</volume>
	</reference>
	<reference name="ben03" src="bibtex:article" src-info="bibtex:line-5223" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Boualem</givenname>
				<surname>Benatallah</surname>
			</person>
			<person>
				<givenname>Quan Z.</givenname>
				<surname>Sheng</surname>
			</person>
			<person>
				<givenname>Marlon</givenname>
				<surname>Dumas</surname>
			</person>
		</names>
		<date value="2003-01"/>
		<title type="sharef:secondaryTitle">IEEE Internet Computing</title>
		<number>1</number>
		<pages>40-48</pages>
		<title type="sharef:primaryTitle">The Self-Serv Environment for Web Services Composition</title>
		<field type="bibtex:topic">selfserv[0.9]</field>
		<identifier type="sharef:uri" resourceType="text/html">http://csdl.computer.org/comp/mags/ic/2003/01/w1040abs.htm</identifier>
		<volume>7</volume>
	</reference>
	<reference name="vin05" src="bibtex:article" src-info="bibtex:line-5236" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Steve</givenname>
				<surname>Vinoski</surname>
			</person>
		</names>
		<date value="2005-09"/>
		<abstract>
			<richtext>
				<p>Despite the fact that many successful distributed systems have been built using remote procedure calls, we've also known for a while that RPC is imperfect, even fundamentally flawed. Lately, however, it seems to be taking even more heat than usual, mainly because of continuing advances in Web services and XML-based messaging.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1109/MIC.2005.108</identifier>
		<title type="sharef:secondaryTitle">IEEE Internet Computing</title>
		<number>5</number>
		<pages>93-95</pages>
		<title type="sharef:primaryTitle">RPC Under Fire</title>
		<field type="bibtex:topic">jaxrpc[0.9] rpc[0.9]</field>
		<identifier type="sharef:uri" resourceType="application/pdf">http://steve.vinoski.net/pdf/IEEE-RPC_Under_Fire.pdf</identifier>
		<volume>9</volume>
	</reference>
	<reference name="vin03b" src="bibtex:article" src-info="bibtex:line-5251" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Steve</givenname>
				<surname>Vinoski</surname>
			</person>
		</names>
		<date value="2003-01"/>
		<title type="sharef:secondaryTitle">IEEE Internet Computing</title>
		<number>1</number>
		<pages>69-71</pages>
		<title type="sharef:primaryTitle">Service Discovery 101</title>
		<identifier type="sharef:uri" resourceType="text/html">http://csdl.computer.org/comp/mags/ic/2003/01/w1069abs.htm</identifier>
		<volume>7</volume>
	</reference>
	<reference name="vin02" src="bibtex:article" src-info="bibtex:line-5263" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Steve</givenname>
				<surname>Vinoski</surname>
			</person>
		</names>
		<date value="2002-07"/>
		<abstract>
			<richtext>
				<p>As I discussed in my previous column, each different style of middleware promotes one or more interaction models that determine how applications based on that middleware communicate and work with each other. It is difficult to say what the best interaction models would be for Web services, mainly because the World Wide Web Consortium (W3C) is still developing the architecture. The author considers the use of remote procedure calls, Web services and messaging and interface complexity.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1109/MIC.2002.1020331</identifier>
		<title type="sharef:secondaryTitle">IEEE Internet Computing</title>
		<number>4</number>
		<pages>90-92</pages>
		<title type="sharef:primaryTitle">Putting the "Web" into Web Services</title>
		<identifier type="sharef:uri" resourceType="application/pdf">http://steve.vinoski.net/pdf/IEEE-Web_Services_Interaction_Models_Part_2.pdf</identifier>
		<volume>6</volume>
	</reference>
	<reference name="pas06b" src="bibtex:article" src-info="bibtex:line-5277" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>James</givenname>
				<surname>Pasley</surname>
			</person>
		</names>
		<date value="2006-05"/>
		<abstract>
			<richtext>
				<p>Developers risk negative side effects when they attempt to make Web services interfaces extensible without understanding the context in which various mechanisms are applied. Given the overuse and misapplication of the HTML example,developers often litter their interfaces with XML Schema wildcards. This increases complexity and results in ambiguous interface definitions. A more appropriate versioning strategy for Web services development can help developers avoid these problems.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1109/MIC.2006.45</identifier>
		<title type="sharef:secondaryTitle">IEEE Internet Computing</title>
		<number>3</number>
		<pages>72-79</pages>
		<title type="sharef:primaryTitle">Avoid XML Schema Wildcards For Web Service Interfaces</title>
		<field type="bibtex:topic">xsd[0.8]</field>
		<identifier type="sharef:uri">http://doi.ieeecomputersociety.org/10.1109/MIC.2006.45</identifier>
		<volume>10</volume>
	</reference>
	<reference name="pas05" src="bibtex:article" src-info="bibtex:line-5292" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>James</givenname>
				<surname>Pasley</surname>
			</person>
		</names>
		<date value="2005-05"/>
		<abstract>
			<richtext>
				<p>As the use of Web services grows, organizations are increasingly choosing the Business Process Execution Language for modeling business processes within the Web services architecture. In addition to orchestrating organizations' Web services, BPEL's strengths include asynchronous message handling, reliability, and recovery. By developing Web services with BPEL in mind, organizations can implement aspects of the service-oriented architecture that might previously have been difficult to achieve.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1109/MIC.2005.56</identifier>
		<title type="sharef:secondaryTitle">IEEE Internet Computing</title>
		<number>3</number>
		<pages>60-67</pages>
		<title type="sharef:primaryTitle">How BPEL and SOA Are Changing Web Services Development</title>
		<field type="bibtex:topic">bpel[0.8] soa[0.8]</field>
		<identifier type="sharef:uri">http://doi.ieeecomputersociety.org/10.1109/MIC.2005.56</identifier>
		<volume>9</volume>
	</reference>
	<reference name="sob03" src="bibtex:article" src-info="bibtex:line-5311" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Lionel S.</givenname>
				<surname>Sobel</surname>
			</person>
		</names>
		<date value="2003"/>
		<title type="sharef:secondaryTitle">Berkeley Technology Law Journal</title>
		<number>2</number>
		<title type="sharef:primaryTitle">DRM as an Enabler of Business Models: ISPs as Digital Retailers</title>
		<field type="bibtex:topic">drm[0.8] isp[0.7]</field>
		<volume>18</volume>
	</reference>
	<reference name="rob08" src="bibtex:article" src-info="bibtex:line-5325" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>David</givenname>
				<surname>Robinson</surname>
			</person>
			<person>
				<givenname>Harlan</givenname>
				<surname>Yu</surname>
			</person>
			<person>
				<givenname>William P.</givenname>
				<surname>Zeller</surname>
			</person>
			<person>
				<givenname>Edward W.</givenname>
				<surname>Felten</surname>
			</person>
		</names>
		<date value="2008"/>
		<abstract>
			<richtext>
				<p>If the next Presidential administration really wants to embrace the potential of Internet-enabled government transparency, it should follow a counter-intuitive but ultimately compelling strategy: reduce the federal role in presenting important government information to citizens. Today, government bodies consider their own websites to be a higher priority than technical infrastructures that open up their data for others to use. We argue that this understanding is a mistake. It would be preferable for government to understand providing reusable data, rather than providing websites, as the core of its online publishing responsibility. Rather than struggling, as it currently does, to design sites that meet each end-user need, we argue that the executive branch should focus on creating a simple, reliable and publicly accessible infrastructure that exposes the underlying data. Private actors, either nonprofit or commercial, are better suited to deliver government information to citizens and can constantly create and reshape the tools individuals use to find and leverage public data. The best way to ensure that the government allows private parties to compete on equal terms in the provision of government data is to require that federal websites themselves use the same open systems for accessing the underlying data as they make available to the public at large.</p>
			</richtext>
		</abstract>
		<title type="sharef:secondaryTitle">Yale Journal of Law &amp; Technology</title>
		<title type="sharef:primaryTitle">Government Data and the Invisible Hand</title>
		<identifier type="sharef:uri">http://ssrn.com/abstract=1138083</identifier>
		<volume>11</volume>
	</reference>
	<reference name="nis04" src="bibtex:article" src-info="bibtex:line-5339" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Helen</givenname>
				<surname>Nissenbaum</surname>
			</person>
		</names>
		<date value="2004"/>
		<abstract>
			<richtext>
				<p>The practices of public surveillance, which include the monitoring of individuals in public through a variety of media (e.g., video, data, online), are among the least understood and controversial challenges to privacy in an age of information technologies. The fragmentary nature of privacy policy in the United States reflects not only the oppositional pulls of diverse vested interests, but also the ambivalence of unsettled intuitions on mundane phenomena such as shopper cards, closed-circuit television, and biometrics. This Article, which extends earlier work on the problem of privacy in public, explains why some of the prominent theoretical approaches to privacy, which were developed over time to meet traditional privacy challenges, yield unsatisfactory conclusions in the case of public surveillance. It posits a new construct, "contextual integrity," as an alternative benchmark for privacy, to capture the nature of challenges posed by information technologies. Contextual integrity ties adequate protection for privacy to norms of specific contexts, demanding that information gathering and dissemination be appropriate to that context and obey the governing norms of distribution within it. Building on the idea of "spheres of justice," developed by political philosopher Michael Walzer, this Article argues that public surveillance violates a right to privacy because it violates contextual integrity; as such, it constitutes injustice and even tyranny.</p>
			</richtext>
		</abstract>
		<title type="sharef:secondaryTitle">Washington Law Review</title>
		<number>1</number>
		<title type="sharef:primaryTitle">Privacy as Contextual Integrity</title>
		<identifier type="sharef:uri">http://ssrn.com/abstract=534622</identifier>
		<volume>79</volume>
	</reference>
	<reference name="sur07" src="bibtex:article" src-info="bibtex:line-5354" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Harry</givenname>
				<surname>Surden</surname>
			</person>
		</names>
		<date value="2007"/>
		<abstract>
			<richtext>
				<p>This Essay challenges the view that privacy interests are protected primarily by law. Instead, I argue that much of society's privacy is protected implicitly by transaction costs. This renders a significant portion of societal privacy vulnerable when transaction-cost-reducing technologies become widely used. I first observe that society explicitly uses and implicitly relies upon transaction costs to regulate behavior in different substantive areas. I then explore how this transaction-cost-based regulation operates in the privacy realm. Based upon the understanding that society relies upon non-legal devices such as markets, norms, and structure to regulate human behavior, this Essay calls attention to a class of regulatory devices known as latent structural constraints and provides a positive account of their role in regulating privacy. Structural constraints are physical or technological barriers which regulate conduct; they can be either explicit or latent. An example of an explicit structural constraint is a fence which is designed to prevent entry onto real property, thereby effectively enforcing property rights. By contrast, latent structural constraints, are the secondary costs arising from the technological state of the world — transaction costs — which implicitly regulate conduct by making certain activities too difficult to engage in on a widespread basis. Society relies upon these latent structural constraints — or transaction costs — to reliably inhibit certain unwanted conduct in a way that is functionally comparable to its use of law. For example, society has frequently depended upon the search costs involved in aggregating and analyzing large amounts of information to effectively protect anonymity. We might think of some of these inhibited behaviors — behaviors constrained by transaction costs — as constituting implicit "structural rights." The regulatory aspect of latent structural constraints and transaction costs may be non-obvious to policymakers in most instances. This is because it is common to think of transaction costs as manifestations of inefficiency rather than as serving a functional role. A focus on structural rights — rights protected solely by the presence of transaction costs — becomes significant because such rights are vulnerable to sudden dissipation. Emerging technologies tend to lower transaction costs in the areas where they are employed. This lowering of transaction costs may have the unintended side effect of eliminating structural rights that were regulated by the presence of transaction costs. For example, the emergence of search and data aggregation technologies may have had the unintended side effect of permitting privacy intrusions that were previously impossible due to the regulatory role of previously existing transaction costs. This Essay describes a conceptual framework by which policymakers can explore this association between constrained behavior and latent structural constraints and suggests that they employ this conceptualization in order to identify non-obvious privacy interests which may be threatened by emerging technologies.</p>
			</richtext>
		</abstract>
		<title type="sharef:secondaryTitle">SMU Law Review</title>
		<pages>1605-1629</pages>
		<title type="sharef:primaryTitle">Structural Rights in Privacy</title>
		<identifier type="sharef:uri">http://ssrn.com/abstract=1004675</identifier>
		<volume>60</volume>
	</reference>
	<reference name="coh08" src="bibtex:article" src-info="bibtex:line-5369" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Julie E.</givenname>
				<surname>Cohen</surname>
			</person>
		</names>
		<date value="2008"/>
		<abstract>
			<richtext>
				<p>This essay considers the relationship between privacy and visibility in the networked information age. Visibility is an important determinant of harm to privacy, but a persistent tendency to conceptualize privacy harms and expectations in terms of visibility has created two problems. First, focusing on visibility diminishes the salience and obscures the operation of nonvisual mechanisms designed to render individual identity, behavior, and preferences transparent to third parties. The metaphoric mapping to visibility suggests that surveillance is simply passive observation, rather than the active production of categories, narratives, and, norms. Second, even a broader conception of privacy harms as a function of informational transparency is incomplete. Privacy has a spatial dimension as well as an informational dimension. The spatial dimension of the privacy interest, which I characterize as an interest in avoiding or selectively limiting exposure, concerns the structure of experienced space. It is not negated by the fact that people in public spaces expect to be visible to others present in those spaces, and it encompasses both the arrangement of physical spaces and the design of networked communications technologies. U.S. privacy law and theory currently do not recognize this interest at all. This essay argues that they should.</p>
			</richtext>
		</abstract>
		<title type="sharef:secondaryTitle">University of Chicago Law Review</title>
		<number>1</number>
		<title type="sharef:primaryTitle">Structural Rights in Privacy</title>
		<identifier type="sharef:uri">http://ssrn.com/abstract=1012068</identifier>
		<volume>75</volume>
	</reference>
	<reference name="wei06" src="bibtex:article" src-info="bibtex:line-5384" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Norbert</givenname>
				<surname>Weißenberg</surname>
			</person>
			<person>
				<givenname>Agnès</givenname>
				<surname>Voisard</surname>
			</person>
			<person>
				<givenname>Rüdiger</givenname>
				<surname>Gartmann</surname>
			</person>
		</names>
		<date value="2006-03"/>
		<abstract>
			<richtext>
				<p>Mobile devices such as personal digital assistants (PDAs) and mobile phones are in widespread use already today and converging to mobile smart phones. They enable users to access a wide range of services and information without guidance through their actual demands. Especially during mass events like the Olympic Games 2008 in Beijing — which was initially the context of our work — a large service space is expected to support all mobile visitors, being athletes, journalists, or spectators. Current approaches tackling such problems are location based, meaning that a user's location is central to service provision, and even context-aware, meaning that, beyond location, characteristics of a user's environment are taken into account. Such information obviously helps to deliver relevant information at the right time to the mobile users. Going one step further, a situation-aware system abstracts from the context dimensions by translating specific contexts into logical situations. Knowing the situation end users are in allows the system to better identify the information to be delivered to them and to choose the appropriate services with regard to their scope, which is referred to as service roaming. Even though many context frameworks have been introduced in the past few years, what is usually missing is the notion of characteristic features of contexts that are invariant during certain time intervals. This paper presents these concepts in the context of a platform development, namely FLAME2008, which is able to support its mobile users with personalized situation-aware services in push and pull mode.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1007/s10707-005-4886-9</identifier>
		<title type="sharef:secondaryTitle">GeoInformatica</title>
		<number>1</number>
		<pages>55-90</pages>
		<title type="sharef:primaryTitle">An Ontology-Based Approach to Personalized Situation-Aware Mobile Service Supply</title>
		<identifier type="sharef:uri">http://www.springerlink.com/content/4202l416768nh184/</identifier>
		<volume>10</volume>
	</reference>
	<reference name="mok05" src="bibtex:article" src-info="bibtex:line-5398" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Mohamed F.</givenname>
				<surname>Mokbel</surname>
			</person>
			<person>
				<givenname>Xiaopeng</givenname>
				<surname>Xiong</surname>
			</person>
			<person>
				<givenname>Moustafa A.</givenname>
				<surname>Hammad</surname>
			</person>
			<person>
				<givenname>Walid G.</givenname>
				<surname>Aref</surname>
			</person>
		</names>
		<date value="2005-12"/>
		<abstract>
			<richtext>
				<p>The tremendous increase in the use of cellular phones, GPS-like devices, and RFIDs results in highly dynamic environments where objects as well as queries are continuously moving. In this paper, we present a continuous query processor designed specifically for highly dynamic environments (e.g., location-aware environments). We implemented the proposed continuous query processor inside the PLACE server (Pervasive Location-Aware Computing Environments); a scalable location-aware database server developed at Purdue University. The PLACE server extends data streaming management systems to support location-aware environments. These environments are characterized by the wide variety of continuous spatio-temporal queries and the unbounded spatio-temporal streams. The proposed continuous query processor includes: (1) New incremental spatio-temporal operators to support a wide variety of continuous spatio-temporal queries, (2) Extended semantics of sliding window queries to deal with spatial sliding windows as well as temporal sliding windows, and (3) A shared-execution framework for scalable execution of a set of concurrent continuous spatio-temporal queries. Experimental evaluation shows promising performance of the continuous query processor of the PLACE server.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1007/s10707-005-4576-7</identifier>
		<title type="sharef:secondaryTitle">GeoInformatica</title>
		<number>4</number>
		<pages>343-365</pages>
		<title type="sharef:primaryTitle">Continuous Query Processing of Spatio-Temporal Data Streams in PLACE</title>
		<volume>9</volume>
	</reference>
	<reference name="cas07" src="bibtex:article" src-info="bibtex:line-5415" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Fabio</givenname>
				<surname>Casati</surname>
			</person>
		</names>
		<date value="2007"/>
		<abstract>
			<richtext>
				<p>Workflow management and service composition technologies have been around for over twenty years now (or more, depending on who you ask and how you define them). The objective of these technologies is to automate process execution across people and systems. These technologies generated an incredible hype both in the academia and in the industry, at least in the software development industry. Hundreds of process and service composition models have been defined, thousands of papers have been written on the topic, and dozens of commercial workflow/service composition systems have been developed. With all this large effort, one would imagine that such technology is in widespread use and that, if not, the key problems have been identified and that is what generates so much effort from the research community. I believe that this is not the case.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/1324960.1324961</identifier>
		<title type="sharef:secondaryTitle">ACM SIGWEB Newsletter</title>
		<number>5</number>
		<title type="sharef:primaryTitle">Service-Oriented Computing</title>
	</reference>
	<reference name="jun07a" src="bibtex:article" src-info="bibtex:line-5425" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Martin</givenname>
				<surname>Junghans</surname>
			</person>
			<person>
				<givenname>Dirk</givenname>
				<surname>Riehle</surname>
			</person>
			<person>
				<givenname>Rama</givenname>
				<surname>Gurram</surname>
			</person>
			<person>
				<givenname>Matthias</givenname>
				<surname>Kaiser</surname>
			</person>
			<person>
				<givenname>Mario</givenname>
				<surname>Lopes</surname>
			</person>
			<person>
				<givenname>Ümit</givenname>
				<surname>Yalçınalp</surname>
			</person>
		</names>
		<date value="2007"/>
		<abstract>
			<richtext>
				<p>Today's wiki engines are not interoperable. This is an unfortunate consequence of the lack of rigorously specified standards. This technical report presents a complete and validated EBNF-based grammar for Wiki Creole, a community standard for wiki markup. Wiki Creole is also the only standard currently available. Wiki Creole is being specified using prose, leading to inconsistencies and ambiguities. Our grammar uncovered those ambiguities which we fed back into the specification process. The Wiki Creole grammar presented in this report makes the creation of Wiki Creole parsers simple using parser generators, ANTLR in our case. Using a precise specification of wiki markup lets us decouple wiki editors from wiki storage from further wiki processing tools. Based on this decoupling layer we expect innovation on these different parts to proceed independently and at a faster pace than before.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/1324960.1324964</identifier>
		<title type="sharef:secondaryTitle">ACM SIGWEB Newsletter</title>
		<title type="sharef:primaryTitle">An EBNF Grammar for Wiki Creole 1.0</title>
		<field type="bibtex:topic">creole[0.9] wiki[0.8]</field>
	</reference>
	<reference name="jun07b" src="bibtex:article" src-info="bibtex:line-5435" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Martin</givenname>
				<surname>Junghans</surname>
			</person>
			<person>
				<givenname>Dirk</givenname>
				<surname>Riehle</surname>
			</person>
			<person>
				<givenname>Ümit</givenname>
				<surname>Yalçınalp</surname>
			</person>
		</names>
		<date value="2007"/>
		<abstract>
			<richtext>
				<p>Wikis have become an important application on the web and in the enterprise, yet there are no interoperability standards between different wiki engines. We present the first complete XML representation format of Wiki Creole 1.0. Wiki Creole is a community standard for wiki markup, the language used to write wiki pages. This report presents the complete XML representation format using a validating XML schema. In addition we present XSLT definitions for transforming the XML representations to XHTML on the one hand and for transforming the XML representations to Wiki Creole markup on the other hand. Our work shows how using XML technologies we can make wiki interchange, wiki upgrading, and wiki conversion independent from a specific wiki engine implementation.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/1324960.1324965</identifier>
		<title type="sharef:secondaryTitle">ACM SIGWEB Newsletter</title>
		<title type="sharef:primaryTitle">An XML Interchange Format for Wiki Creole 1.0</title>
		<field type="bibtex:topic">creole[0.9] wiki[0.8]</field>
	</reference>
	<reference name="alo02" src="bibtex:article" src-info="bibtex:line-5449" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Gustavo</givenname>
				<surname>Alonso</surname>
			</person>
		</names>
		<date value="2002-12"/>
		<title type="sharef:secondaryTitle">Bulletin of the Technical Committee on Data Engineering</title>
		<number>4</number>
		<pages>3-9</pages>
		<title type="sharef:primaryTitle">Myths around Web Services</title>
		<field type="bibtex:topic">soap[0.7] wsdl[0.7] uddi[0.7]</field>
		<identifier type="sharef:uri" resourceType="application/postscript">http://www.research.microsoft.com/research/db/debull/A02dec/alonso.ps</identifier>
		<volume>25</volume>
	</reference>
	<reference name="flo99b" src="bibtex:article" src-info="bibtex:line-5462" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Daniela</givenname>
				<surname>Florescu</surname>
			</person>
			<person>
				<givenname>Donald</givenname>
				<surname>Kossmann</surname>
			</person>
		</names>
		<date value="1999-09"/>
		<title type="sharef:secondaryTitle">Bulletin of the Technical Committee on Data Engineering</title>
		<number>3</number>
		<pages>27-34</pages>
		<title type="sharef:primaryTitle">Storing and Querying XML Data using an RDBMS</title>
		<field type="bibtex:topic">xml[0.8] rdbms[0.8]</field>
		<identifier type="sharef:uri" resourceType="application/pdf">http://www.soe.ucsc.edu/classes/cmps290s/Spring03/fk.pdf</identifier>
		<volume>22</volume>
	</reference>
	<reference name="pej95" src="bibtex:article" src-info="bibtex:line-5479" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Sassan</givenname>
				<surname>Pejhan</surname>
			</person>
			<person>
				<givenname>Alexandros</givenname>
				<surname>Eleftheriadis</surname>
			</person>
			<person>
				<givenname>Dimitris</givenname>
				<surname>Anastassiou</surname>
			</person>
		</names>
		<date value="1995"/>
		<field type="bibtex:index">multicast, MGA, SMAM, HeiMAP, DMAM</field>
		<title type="sharef:secondaryTitle">IEEE Journal on Selected Areas in Communications</title>
		<number>8</number>
		<pages>1445-1456</pages>
		<title type="sharef:primaryTitle">Distributed Multicast Address Management in the Global Internet</title>
		<volume>13</volume>
	</reference>
	<reference name="lak03" src="bibtex:article" src-info="bibtex:line-5490" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>A.</givenname>
				<surname>Lakhina</surname>
			</person>
			<person>
				<givenname>J. W.</givenname>
				<surname>Byers</surname>
			</person>
			<person>
				<givenname>Mark</givenname>
				<surname>Crovella</surname>
			</person>
			<person>
				<givenname>I.</givenname>
				<surname>Matta</surname>
			</person>
		</names>
		<date value="2003-08"/>
		<abstract>
			<richtext>
				<p>One relatively unexplored question about the Internet's physical structure concerns the geographical location of its components: routers, links, and autonomous systems (ASes). We study this question using two large inventories of Internet routers and links, collected by different methods and about two years apart. We first map each router to its geographical location using two different state-of-the-art tools. We then study the relationship between router location and population density; between geographic distance and link density; and between the size and geographic extent of ASes. Our findings are consistent across the two datasets and both mapping methods. First, as expected, router density per person varies widely over different economic regions; however, in economically homogeneous regions, router density shows a strong superlinear relationship to population density. Second, the probability that two routers are directly connected is strongly dependent on distance; our data is consistent with a model in which a majority (up to 75%-95%) of link formation is based on geographical distance (as in the Waxman (1988) topology generation method). Finally, we find that ASes show high variability in geographic size, which is correlated with other measures of AS size (degree and number of interfaces). Among small to medium ASes, ASes show wide variability in their geographic dispersal; however, all ASes exceeding a certain threshold in size are maximally dispersed geographically. These findings have many implications for the next generation of topology generators, which we envisage as producing router-level graphs annotated with attributes such as link latencies, AS identifiers, and geographical locations.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1109/JSAC.2003.814667</identifier>
		<title type="sharef:secondaryTitle">IEEE Journal on Selected Areas in Communications</title>
		<number>6</number>
		<pages>934-948</pages>
		<title type="sharef:primaryTitle">On the Geographic Location of Internet Resources</title>
		<identifier type="sharef:uri" resourceType="application/pdf">http://ieeexplore.ieee.org/Xplore/login.jsp?url=/iel5/49/27368/01217279.pdf</identifier>
		<volume>21</volume>
	</reference>
	<reference name="rob09" src="bibtex:article" src-info="bibtex:line-5508" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Valentin</givenname>
				<surname>Robu</surname>
			</person>
			<person>
				<givenname>Harry</givenname>
				<surname>Halpin</surname>
			</person>
			<person>
				<givenname>Hana</givenname>
				<surname>Shepherd</surname>
			</person>
		</names>
		<date value="2009-09"/>
		<abstract>
			<richtext>
				<p>This article uses data from the social bookmarking site del.icio.us to empirically examine the dynamics of collaborative tagging systems and to study how coherent categorization schemes emerge from unsupervised tagging by individual users. First, we study the formation of stable distributions in tagging systems, seen as an implicit form of "consensus" reached by the users of the system around the tags that best describe a resource. We show that final tag frequencies for most resources converge to power law distributions and we propose an empirical method to examine the dynamics of the convergence process, based on the Kullback-Leibler divergence measure. The convergence analysis is performed for both the most utilized tags at the top of tag distributions and the so-called long tail. Second, we study the information structures that emerge from collaborative tagging, namely tag correlation (or folksonomy) graphs. We show how community-based network techniques can be used to extract simple tag vocabularies from the tag correlation graphs by partitioning them into subsets of related tags. Furthermore, we also show, for a specialized domain, that shared vocabularies produced by collaborative tagging are richer than the vocabularies which can be extracted from large-scale query logs provided by a major search engine. Although the empirical analysis presented in this article is based on a set of tagging data obtained from del.icio.us, the methods developed are general, and the conclusions should be applicable across other websites that employ tagging.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/1594173.1594176</identifier>
		<title type="sharef:secondaryTitle">ACM Transactions on the Web</title>
		<number>4</number>
		<title type="sharef:primaryTitle">Emergence of Consensus and Shared Vocabularies in Collaborative Tagging Systems</title>
		<volume>3</volume>
	</reference>
	<reference name="rat09" src="bibtex:article" src-info="bibtex:line-5520" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Tye</givenname>
				<surname>Rattenbury</surname>
			</person>
			<person>
				<givenname>Mor</givenname>
				<surname>Naaman</surname>
			</person>
		</names>
		<date value="2009-01"/>
		<abstract>
			<richtext>
				<p>We describe an approach for extracting semantics for tags, unstructured text-labels assigned to resources on the Web, based on each tag's usage patterns. In particular, we focus on the problem of extracting place semantics for tags that are assigned to photos on Flickr, a popular-photo sharing Web site that supports location (latitude/longitude) metadata for photos. We propose the adaptation of two baseline methods, inspired by well-known burst-analysis techniques, for the task; we also describe two novel methods, TagMaps and scale-structure identification. We evaluate the methods on a subset of Flickr data. We show that our scale-structure identification method outperforms existing techniques and that a hybrid approach generates further improvements (achieving 85% precision at 81% recall). The approach and methods described in this work can be used in other domains such as geo-annotated Web pages, where text terms can be extracted and associated with usage patterns.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/1462148.1462149</identifier>
		<title type="sharef:secondaryTitle">ACM Transactions on the Web</title>
		<number>1</number>
		<title type="sharef:primaryTitle">Methods for Extracting Place Semantics from Flickr Tags</title>
		<volume>3</volume>
	</reference>
	<reference name="hei97b" src="bibtex:article" src-info="bibtex:line-5536" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>John</givenname>
				<surname>Heidemann</surname>
			</person>
			<person>
				<givenname>Katia</givenname>
				<surname>Obraczka</surname>
			</person>
			<person>
				<givenname>Joe</givenname>
				<surname>Touch</surname>
			</person>
		</names>
		<date value="1997"/>
		<title type="sharef:secondaryTitle">IEEE/ACM Transactions on Networking</title>
		<number>5</number>
		<title type="sharef:primaryTitle">Modeling the Performance of HTTP Over Several Transport Protocols</title>
		<field type="bibtex:topic">http[0.8] tcp[0.7] phttp[0.8] ttcp[0.7]</field>
		<volume>5</volume>
	</reference>
	<reference name="gut95" src="bibtex:article" src-info="bibtex:line-5546" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Thomas</givenname>
				<surname>Gutekunst</surname>
			</person>
			<person>
				<givenname>Daniel</givenname>
				<surname>Bauer</surname>
			</person>
			<person>
				<givenname>Germano</givenname>
				<surname>Caronni</surname>
			</person>
			<person>
				<surname>Hasan</surname>
			</person>
			<person>
				<givenname>Bernhard</givenname>
				<surname>Plattner</surname>
			</person>
		</names>
		<date value="1995"/>
		<field type="bibtex:index">JVTOS, CIO</field>
		<title type="sharef:secondaryTitle">IEEE/ACM Transactions on Networking</title>
		<number>1</number>
		<pages>51-62</pages>
		<title type="sharef:primaryTitle">A Distributed and Policy-Free General-Purpose Shared Window System</title>
		<volume>3</volume>
	</reference>
	<reference name="ban96" src="bibtex:article" src-info="bibtex:line-5557" type="sharef:article">
		<names type="sharef: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="1996"/>
		<field type="bibtex:index">Tenet, ATM, FDDI, RTIP, RMTP, CMTP</field>
		<title type="sharef:secondaryTitle">IEEE/ACM Transactions on Networking</title>
		<number>1</number>
		<pages>1-10</pages>
		<title type="sharef:primaryTitle">The Tenet Real-Time Protocol Suite: Design, Implementation, and Experiences</title>
		<volume>4</volume>
	</reference>
	<reference name="bro02b" src="bibtex:article" src-info="bibtex:line-5572" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Jeen</givenname>
				<surname>Broekstra</surname>
			</person>
			<person>
				<givenname>Michel</givenname>
				<surname>Klein</surname>
			</person>
			<person>
				<givenname>Stefan</givenname>
				<surname>Decker</surname>
			</person>
			<person>
				<givenname>Dieter</givenname>
				<surname>Fensel</surname>
			</person>
			<person>
				<givenname>Frank</givenname>
				<surname link="van">Harmelen</surname>
			</person>
			<person>
				<givenname>Ian</givenname>
				<surname>Horrocks</surname>
			</person>
		</names>
		<date value="2002-08"/>
		<title type="sharef:secondaryTitle">Computer Networks</title>
		<number>5</number>
		<pages>609-634</pages>
		<title type="sharef:primaryTitle">Enabling knowledge representation on the Web by extending RDF Schema</title>
		<field type="bibtex:topic">rdf[0.8] oil[0.8] daml[0.8]</field>
		<identifier type="sharef:uri">http://www.sciencedirect.com/science/article/B6VRG-45KT113-2/1/946d47a42e4d842b75ca6c255c3be47f</identifier>
		<volume>39</volume>
	</reference>
	<reference name="bro02a" src="bibtex:article" src-info="bibtex:line-5585" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Allen</givenname>
				<surname>Brown</surname>
			</person>
			<person>
				<givenname>Matthew</givenname>
				<surname>Fuchs</surname>
			</person>
			<person>
				<givenname>Jonathan</givenname>
				<surname>Robie</surname>
			</person>
			<person>
				<givenname>Philip</givenname>
				<surname>Wadler</surname>
			</person>
		</names>
		<date value="2002-08"/>
		<title type="sharef:secondaryTitle">Computer Networks</title>
		<number>5</number>
		<pages>507-521</pages>
		<title type="sharef:primaryTitle">MSL: A model for W3C XML Schema</title>
		<field type="bibtex:topic">msl[1] xsd[0.9]</field>
		<identifier type="sharef:uri">http://www.sciencedirect.com/science/article/B6VRG-45KNFVW-5/1/07e45d6a6e53a2f9cde54b551d2601ae</identifier>
		<volume>39</volume>
	</reference>
	<reference name="sun02" src="bibtex:article" src-info="bibtex:line-5598" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Neel</givenname>
				<surname>Sundaresan</surname>
			</person>
			<person>
				<givenname>Reshad</givenname>
				<surname>Moussa</surname>
			</person>
		</names>
		<date value="2002-08"/>
		<title type="sharef:secondaryTitle">Computer Networks</title>
		<number>5</number>
		<pages>681-697</pages>
		<title type="sharef:primaryTitle">Algorithms and programming models for efficient representation of XML for Internet applications</title>
		<field type="bibtex:topic">millau[1] sxml[1] sdom[1] sas[1]</field>
		<identifier type="sharef:uri">http://www.sciencedirect.com/science/article/B6VRG-45KNFVW-4/1/d2aaf6d27ee1b7febc679ad176e7bf47</identifier>
		<volume>39</volume>
	</reference>
	<reference name="bun02" src="bibtex:article" src-info="bibtex:line-5611" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Peter</givenname>
				<surname>Buneman</surname>
			</person>
			<person>
				<givenname>Susan B.</givenname>
				<surname>Davidson</surname>
			</person>
			<person>
				<givenname>Wenfei</givenname>
				<surname>Fan</surname>
			</person>
			<person>
				<givenname>Carmem S.</givenname>
				<surname>Hara</surname>
			</person>
			<person>
				<givenname>Wang-Chiew</givenname>
				<surname>Tan</surname>
			</person>
		</names>
		<date value="2002-08"/>
		<abstract>
			<richtext>
				<p>We discuss the definition of keys for XML documents, paying particular attention to the concept of a relative key, which is commonly used in hierarchically structured documents and scientific databases.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1016/S1389-1286(02)00223-2</identifier>
		<title type="sharef:secondaryTitle">Computer Networks</title>
		<number>5</number>
		<pages>473-487</pages>
		<title type="sharef:primaryTitle">Keys for XML</title>
		<field type="bibtex:topic">xml[0.8]</field>
		<identifier type="sharef:uri">http://www.sciencedirect.com/science/article/B6VRG-45KT113-4/1/dc0889d00f913fe785afa24d1b190f1c</identifier>
		<volume>39</volume>
	</reference>
	<reference name="fan02" src="bibtex:article" src-info="bibtex:line-5626" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Wenfei</givenname>
				<surname>Fan</surname>
			</person>
			<person>
				<givenname>Gabriel M.</givenname>
				<surname>Kuper</surname>
			</person>
			<person>
				<givenname>Jérôme</givenname>
				<surname>Siméon</surname>
			</person>
		</names>
		<date value="2002-08"/>
		<abstract>
			<richtext>
				<p>Integrity constraints are an essential part of modern schema definition languages. They are useful for semantic specification, update consistency control, query optimization, etc. In this paper, we propose UCM, a model of integrity constraints for XML that is both simple and expressive. Because it relies on a single notion of keys and foreign keys, the UCM model is easy to use and makes formal reasoning possible. Because it relies on a powerful type system, the UCM model is expressive, capturing in a single framework the constraints found in relational databases, object-oriented schemas and XML document type definitions. We study the problem of consistency of UCM constraints, the interaction between constraints and subtyping, and algorithms for implementing these constraints.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1016/S1389-1286(02)00219-0</identifier>
		<title type="sharef:secondaryTitle">Computer Networks</title>
		<number>5</number>
		<pages>489-505</pages>
		<title type="sharef:primaryTitle">A Unified Constraint Model for XML</title>
		<field type="bibtex:topic">xml[0.8]</field>
		<identifier type="sharef:uri">http://www.sciencedirect.com/science/article/B6VRG-45KT113-3/1/becacb93cf3007d2bdafeef4fdf7c927</identifier>
		<volume>39</volume>
	</reference>
	<reference name="kah02" src="bibtex:article" src-info="bibtex:line-5641" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>José</givenname>
				<surname>Kahan</surname>
			</person>
			<person>
				<givenname>Marja-Riitta</givenname>
				<surname>Koivunen</surname>
			</person>
			<person>
				<givenname>Eric</givenname>
				<surname>Prud'Hommeaux</surname>
			</person>
			<person>
				<givenname>Ralph R.</givenname>
				<surname>Swick</surname>
			</person>
		</names>
		<date value="2002-08"/>
		<abstract>
			<richtext>
				<p>Annotea is a Web-based shared annotation system based on a general-purpose open resource description framework (RDF) infrastructure, where annotations are modeled as a class of metadata. Annotations are viewed as statements made by an author about a Web document. Annotations are external to the documents and can be stored in one or more annotation servers. One of the goals of this project has been to re-use as much existing W3C technology as possible. We have reached it mostly by combining RDF with XPointer, XLink, and HTTP. We have also implemented an instance of our system using the Amaya editor/browser and a generic RDF database, accessible through an Apache HTTP server. In this implementation, the merging of annotations with documents takes place within the client. The paper presents the overall design of Annotea and describes some of the issues we have faced and how we have solved them.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1016/S1389-1286(02)00220-7</identifier>
		<title type="sharef:secondaryTitle">Computer Networks</title>
		<number>5</number>
		<pages>589-608</pages>
		<title type="sharef:primaryTitle">Annotea: An Open RDF Infrastructure for Shared Web Annotations</title>
		<field type="bibtex:topic">annotea[0.9]</field>
		<volume>39</volume>
	</reference>
	<reference name="myl02" src="bibtex:article" src-info="bibtex:line-5655" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Jussi</givenname>
				<surname>Myllymaki</surname>
			</person>
		</names>
		<date value="2002-08"/>
		<abstract>
			<richtext>
				<p>We describe an Extensible Markup Language (XML)-based methodology for Web data extraction that extends beyond simple "screen scraping". An ideal data extraction process can digest target Web databases that are visible only as Hypertext Markup Language (HTML) pages, and create a local replica of those databases as a result. What is needed is more than a Web crawler and set of Web site wrappers. A comprehensive data extraction process must deal with such obstacles as session identifiers, HTML forms, client-side JavaScript, incompatible datasets and vocabularies, and missing and conflicting data. Proper data extraction also requires solid data validation and error recovery to handle data extraction failures. Our ANDES software framework helps solve these problems and provides a platform for building a production-quality Web data extraction process. Key aspects of ANDES are that it uses XML technologies for data extraction, including Extensible HTML and Extensible Stylesheet Language Transformations, and provides access to the "deep Web".</p>
			</richtext>
		</abstract>
		<title type="sharef:secondaryTitle">Computer Networks</title>
		<number>5</number>
		<pages>635-644</pages>
		<title type="sharef:primaryTitle">Effective Web Data Extraction with Standard XML Technologies</title>
		<identifier type="sharef:uri">http://www.sciencedirect.com/science/article/B6VRG-45JPMD3-1/1/55eff600ee35bb83d9d1fffee7e34b22</identifier>
		<volume>39</volume>
	</reference>
	<reference name="neu92a" src="bibtex:article" src-info="bibtex:line-5672" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Gerald W.</givenname>
				<surname>Neufeld</surname>
			</person>
			<person>
				<givenname>Son</givenname>
				<surname>Vuong</surname>
			</person>
		</names>
		<date value="1992-02"/>
		<title type="sharef:secondaryTitle">Computer Networks and ISDN Systems</title>
		<number>5</number>
		<pages>393-415</pages>
		<title type="sharef:primaryTitle">Overview of ASN.1</title>
		<field type="bibtex:topic">asn1[0.9]</field>
		<volume>23</volume>
	</reference>
	<reference name="fer94" src="bibtex:article" src-info="bibtex:line-5684" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Domenico</givenname>
				<surname>Ferrari</surname>
			</person>
			<person>
				<givenname>Anindo</givenname>
				<surname>Banerjea</surname>
			</person>
			<person>
				<givenname>Hui</givenname>
				<surname>Zhang</surname>
			</person>
		</names>
		<date value="1994"/>
		<field type="bibtex:index">Tenet, RTIP, RMTP, CMTP, RCAP</field>
		<title type="sharef:secondaryTitle">Computer Networks and ISDN Systems</title>
		<pages>1267-1280</pages>
		<title type="sharef:primaryTitle">Network Support for Multimedia — A Discussion of the Tenet Approach</title>
		<volume>26</volume>
	</reference>
	<reference name="bor91" src="bibtex:article" src-info="bibtex:line-5694" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Ute</givenname>
				<surname>Bormann</surname>
			</person>
			<person>
				<givenname>Carsten</givenname>
				<surname>Bormann</surname>
			</person>
		</names>
		<date value="1991"/>
		<field type="bibtex:index">open document processing, SGML, ODA</field>
		<title type="sharef:secondaryTitle">Computer Networks and ISDN Systems</title>
		<pages>149-163</pages>
		<title type="sharef:primaryTitle">Standards for open dcoument processing: current state and future developments</title>
		<volume>21</volume>
	</reference>
	<reference name="spi91" src="bibtex:article" src-info="bibtex:line-5704" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Andy</givenname>
				<surname>Spiceley</surname>
			</person>
		</names>
		<date value="1991"/>
		<field type="bibtex:index">ODA profiles, interworking</field>
		<title type="sharef:secondaryTitle">Computer Networks and ISDN Systems</title>
		<pages>165-173</pages>
		<title type="sharef:primaryTitle">ODA profiles: application and development</title>
		<volume>21</volume>
	</reference>
	<reference name="nel91" src="bibtex:article" src-info="bibtex:line-5714" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>J.</givenname>
				<surname>Nelson</surname>
			</person>
			<person>
				<givenname>C.</givenname>
				<surname>Bathe</surname>
			</person>
			<person>
				<givenname>I.</givenname>
				<surname>Campbell-Grant</surname>
			</person>
			<person>
				<givenname>M.</givenname>
				<surname>Coon</surname>
			</person>
			<person>
				<givenname>K.</givenname>
				<surname>Fischer</surname>
			</person>
			<person>
				<givenname>Peter T.</givenname>
				<surname>Kirstein</surname>
			</person>
			<person>
				<givenname>G.</givenname>
				<surname>Krönert</surname>
			</person>
			<person>
				<givenname>Marwa</givenname>
				<surname>Mabrouk</surname>
			</person>
		</names>
		<date value="1991"/>
		<field type="bibtex:index">ODA, PODA, API, toolkit</field>
		<title type="sharef:secondaryTitle">Computer Networks and ISDN Systems</title>
		<pages>175-185</pages>
		<title type="sharef:primaryTitle">The role of the PODA project in the adoption and development of ODA</title>
		<volume>21</volume>
	</reference>
	<reference name="gol91" src="bibtex:article" src-info="bibtex:line-5724" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Seyed N.</givenname>
				<surname>Golkar</surname>
			</person>
			<person>
				<givenname>Peter T.</givenname>
				<surname>Kirstein</surname>
			</person>
			<person>
				<givenname>Afzal</givenname>
				<surname>Montaser-Kohsari</surname>
			</person>
		</names>
		<date value="1991"/>
		<field type="bibtex:index">ODA, ODIF, document architecture, multimedia documents, document interchange</field>
		<title type="sharef:secondaryTitle">Computer Networks and ISDN Systems</title>
		<pages>187-196</pages>
		<title type="sharef:primaryTitle">ODA activities at University College London</title>
		<volume>21</volume>
	</reference>
	<reference name="fil91" src="bibtex:article" src-info="bibtex:line-5734" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>W.</givenname>
				<surname>Filip</surname>
			</person>
			<person>
				<givenname>J.</givenname>
				<surname>Kämper</surname>
			</person>
			<person>
				<givenname>W.</givenname>
				<surname>Knobloch</surname>
			</person>
		</names>
		<date value="1991"/>
		<field type="bibtex:index">ODA, RFT, document interchange, document conversion</field>
		<title type="sharef:secondaryTitle">Computer Networks and ISDN Systems</title>
		<pages>197-210</pages>
		<title type="sharef:primaryTitle">Conversion between ODA Level 2 and RFT:DCA — experiences with a prototype</title>
		<volume>21</volume>
	</reference>
	<reference name="ros91" src="bibtex:article" src-info="bibtex:line-5744" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Jonathan</givenname>
				<surname>Rosenberg</surname>
			</person>
			<person>
				<givenname>Mark</givenname>
				<surname>Sherman</surname>
			</person>
			<person>
				<givenname>Ann</givenname>
				<surname>Marks</surname>
			</person>
			<person>
				<givenname>Jaap</givenname>
				<surname>Akkerhuis</surname>
			</person>
		</names>
		<date value="1991"/>
		<field type="bibtex:index">ODA, multimedia document interchange, format translation</field>
		<title type="sharef:secondaryTitle">Computer Networks and ISDN Systems</title>
		<pages>211-220</pages>
		<title type="sharef:primaryTitle">Some comments on using ODA</title>
		<volume>21</volume>
	</reference>
	<reference name="col91" src="bibtex:article" src-info="bibtex:line-5754" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Fred</givenname>
				<surname>Cole</surname>
			</person>
			<person>
				<givenname>Heather</givenname>
				<surname>Brown</surname>
			</person>
		</names>
		<date value="1991"/>
		<field type="bibtex:index">ODA extensions, document structures, layout styles</field>
		<title type="sharef:secondaryTitle">Computer Networks and ISDN Systems</title>
		<pages>221-230</pages>
		<title type="sharef:primaryTitle">ODA extensions for quality and flexibility</title>
		<volume>21</volume>
	</reference>
	<reference name="sme91" src="bibtex:article" src-info="bibtex:line-5764" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Bohdan</givenname>
				<surname>Smetaniuk</surname>
			</person>
		</names>
		<date value="1991"/>
		<field type="bibtex:index">X.500, electronic directory, OSI application, distributed systems</field>
		<title type="sharef:secondaryTitle">Computer Networks and ISDN Systems</title>
		<pages>17-40</pages>
		<title type="sharef:primaryTitle">Distributed Operation of the X.500 directory</title>
		<volume>21</volume>
	</reference>
	<reference name="lub90c" src="bibtex:article" src-info="bibtex:line-5774" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Hannes P.</givenname>
				<surname>Lubich</surname>
			</person>
		</names>
		<date value="1990"/>
		<field type="bibtex:index">X.500, electronic directory, OSI application, distributed systems</field>
		<title type="sharef:secondaryTitle">Computer Networks and ISDN Systems</title>
		<pages>215-223</pages>
		<title type="sharef:primaryTitle">MultimETH, a Collaborative Editing and Conferencing Project</title>
		<volume>19</volume>
	</reference>
	<reference name="han93" src="bibtex:article" src-info="bibtex:line-5784" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Mark J.</givenname>
				<surname>Handley</surname>
			</person>
			<person>
				<givenname>Peter T.</givenname>
				<surname>Kirstein</surname>
			</person>
			<person>
				<givenname>M. Angela</givenname>
				<surname>Sasse</surname>
			</person>
		</names>
		<date value="1993"/>
		<field type="bibtex:index">MICE</field>
		<title type="sharef:secondaryTitle">Computer Networks and ISDN Systems</title>
		<number>3</number>
		<pages>275-290</pages>
		<title type="sharef:primaryTitle">Multimedia Integrated Conferencing for European Researchers (MICE): Piloting Activities and the Conference Management and Multiplexing Centre</title>
		<volume>26</volume>
	</reference>
	<reference name="rob91a" src="bibtex:article" src-info="bibtex:line-5799" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Mike</givenname>
				<surname>Robinson</surname>
			</person>
		</names>
		<date value="1991"/>
		<field type="bibtex:index">CSCW, competence, cooperative, criteria, double-level-language, equality</field>
		<title type="sharef:secondaryTitle">AI &amp; Society</title>
		<number>1</number>
		<pages>34-60</pages>
		<title type="sharef:primaryTitle">Double-Level Languages and Co-operative Working</title>
		<volume>5</volume>
	</reference>
	<reference name="che76" src="bibtex:article" src-info="bibtex:line-5814" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Peter Pin-Shan</givenname>
				<surname>Chen</surname>
			</person>
		</names>
		<date value="1976-03"/>
		<abstract>
			<richtext>
				<p>A data model, called the entity-relationship model, is proposed. This model incorporates some of the important semantic information about the real world. A special diagrammatic technique is introduced as a tool for database design. An example of database design and description using the model and the diagrammatic technique is given. Some implications for data integrity, information retrieval, and data manipulation are discussed. The entity-relationship model can be used as a basis for unification of different views of data: the network model, the relational model, and the entity set model. Semantic ambiguities in these models are analyzed. Possible ways to derive their views of data from the entity-relationship model are presented.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/320434.320440</identifier>
		<title type="sharef:secondaryTitle">ACM Transactions on Database Systems</title>
		<number>1</number>
		<pages>9-36</pages>
		<title type="sharef:primaryTitle">The Entity-Relationship Model — Toward a Unified View of Data</title>
		<field type="bibtex:topic">er[1]</field>
		<identifier type="sharef:uri">http://portal.acm.org/citation.cfm?id=320440</identifier>
		<volume>1</volume>
	</reference>
	<reference name="fag81" src="bibtex:article" src-info="bibtex:line-5829" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Ronald</givenname>
				<surname>Fagin</surname>
			</person>
		</names>
		<date value="1981-09"/>
		<abstract>
			<richtext>
				<p>A new normal form for relational databases, called domain-key normal form (DK/NF), is defined. Also, formal definitions of insertion anomaly and deletion anomaly are presented. It is shown that a schema is in DK/NF if and only if it has no insertion or deletion anomalies. Unlike previously defined normal forms, DK/NF is not defined in terms of traditional dependencies (functional, multivalued, or join). Instead, it is defined in terms of the more primitive concepts of domain and key, along with the general concept of a "constraint." We also consider how the definitions of traditional normal forms might be modified by taking into consideration, for the first time, the combinatorial consequences of bounded domain sizes. It is shown that after this modification, these traditional normal forms are all implied by DK/NF. In particular, if all domains are infinite, then these traditional normal forms are all implied by DK/NF.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/319587.319592</identifier>
		<title type="sharef:secondaryTitle">ACM Transactions on Database Systems</title>
		<number>3</number>
		<pages>387-415</pages>
		<title type="sharef:primaryTitle">A Normal Form for Relational Databases that is based on Domains and Keys</title>
		<field type="bibtex:topic">dknf[1]</field>
		<identifier type="sharef:uri">http://portal.acm.org/citation.cfm?id=319592</identifier>
		<volume>6</volume>
	</reference>
	<reference name="gru04" src="bibtex:article" src-info="bibtex:line-5844" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Torsten</givenname>
				<surname>Grust</surname>
			</person>
			<person>
				<givenname>Jens</givenname>
				<surname>Teubner</surname>
			</person>
			<person>
				<givenname>Maurice</givenname>
				<surname link="van">Keulen</surname>
			</person>
		</names>
		<date value="2004-03"/>
		<identifier type="sharef:doi">10.1145/974750.974754</identifier>
		<title type="sharef:secondaryTitle">ACM Transactions on Database Systems</title>
		<number>1</number>
		<pages>91-131</pages>
		<title type="sharef:primaryTitle">Accelerating XPath Evaluation in Any RDBMS</title>
		<field type="bibtex:topic">xpath1[0.8]</field>
		<identifier type="sharef:uri" resourceType="application/pdf">http://www.inf.uni-konstanz.de/~grust/files/accelerating-locsteps.pdf</identifier>
		<volume>29</volume>
	</reference>
	<reference name="are04" src="bibtex:article" src-info="bibtex:line-5858" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Marcelo</givenname>
				<surname>Arenas</surname>
			</person>
			<person>
				<givenname>Leonid</givenname>
				<surname>Libkin</surname>
			</person>
		</names>
		<date value="2004-03"/>
		<abstract>
			<richtext>
				<p>This article takes a first step towards the design and normalization theory for XML documents. We show that, like relational databases, XML documents may contain redundant information, and may be prone to update anomalies. Furthermore, such problems are caused by certain functional dependencies among paths in the document. Our goal is to find away of converting an arbitrary DTD into a well-designed one, that avoids these problems. We first introduce the concept of a functional dependency for XML, and define its semantics via a relational representation of XML. We then define an XML normal form, XNF, that avoids update anomalies and redundancies. We study its properties, and show that XNF generalizes BCNF; we also discuss the relationship between XNF and normal forms for nested relations. Finally, we present a lossless algorithm for converting any DTD into one in XNF.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/974750.974757</identifier>
		<title type="sharef:secondaryTitle">ACM Transactions on Database Systems</title>
		<number>1</number>
		<pages>195-232</pages>
		<title type="sharef:primaryTitle">A Normal Form for XML Documents</title>
		<field type="bibtex:topic">xml[0.8] xnf[1]</field>
		<identifier type="sharef:uri" resourceType="application/pdf">http://www.cs.toronto.edu/~marenas/publications/xnf_tods04.pdf</identifier>
		<volume>29</volume>
	</reference>
	<reference name="rod95" src="bibtex:article" src-info="bibtex:line-5877" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>John F.</givenname>
				<surname>Roddick</surname>
			</person>
		</names>
		<date value="1995"/>
		<identifier type="sharef:doi">10.1016/0950-5849(95)91494-K</identifier>
		<title type="sharef:secondaryTitle">Information and Software Technology</title>
		<number>7</number>
		<pages>383-393</pages>
		<title type="sharef:primaryTitle">A Survey of Schema Versioning Issues for Database Systems</title>
		<volume>37</volume>
	</reference>
	<reference name="hof98" src="bibtex:article" src-info="bibtex:line-5888" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>A. H. M.</givenname>
				<surname link="ter">Hofstede</surname>
			</person>
			<person>
				<givenname>H. A.</givenname>
				<surname>Proper</surname>
			</person>
		</names>
		<date value="1998"/>
		<abstract>
			<richtext>
				<p>Although the need for formalisation of modelling techniques is generally recognised, not much literature is devoted to the actual process involved. This is comparable to the situation in mathematics where focus is on proofs but not on the process of proving. This paper tries to accommodate for this lacuna and provides essential principles for the process of formalisation in the context of modelling techniques as well as a number of small but realistic formalisation case studies.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">http://portal.acm.org/citation.cfm?id=869838</identifier>
		<title type="sharef:secondaryTitle">Information and Software Technology</title>
		<number>10</number>
		<pages>519-540</pages>
		<title type="sharef:primaryTitle">How to Formalize It? Formalization Principles for Information Systems Development Methods</title>
		<volume>40</volume>
	</reference>
	<reference name="noy04a" src="bibtex:article" src-info="bibtex:line-5904" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Natalya Fridman</givenname>
				<surname>Noy</surname>
			</person>
			<person>
				<givenname>Michel</givenname>
				<surname>Klein</surname>
			</person>
		</names>
		<date value="2004-07"/>
		<abstract>
			<richtext>
				<p>As ontology development becomes a more ubiquitous and collaborative process, ontology versioning and evolution becomes an important area of ontology research. The many similarities between database-schema evolution and ontology evolution will allow us to build on the extensive research in schema evolution. However, there are also important differences between database schemas and ontologies. The differences stem from different usage paradigms, the presence of explicit semantics, and different knowledge models. A lot of problems that existed only in theory in database research come to the forefront as practical problems in ontology evolution. These differences have important implications for the development of ontology evolution frameworks: The traditional distinction between versioning and evolution is not applicable to ontologies. There are several dimensions along which compatibility between versions must be considered. The set of change operations for ontologies is difference. We must develop automatic techniques for finding similarities and differences between versions.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1007/s10115-003-0137-2</identifier>
		<title type="sharef:secondaryTitle">Knowledge and Information Systems</title>
		<number>4</number>
		<pages>428-440</pages>
		<title type="sharef:primaryTitle">Ontology Evolution: Not the Same as Schema Evolution</title>
		<identifier type="sharef:uri" resourceType="text/html">http://smi-web.stanford.edu/pubs/SMI_Abstracts/SMI-2002-0926.html</identifier>
		<volume>6</volume>
	</reference>
	<reference name="elm85" src="bibtex:article" src-info="bibtex:line-5922" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Ramez</givenname>
				<surname>Elmasri</surname>
			</person>
			<person>
				<givenname>James A.</givenname>
				<surname>Weeldreyer</surname>
			</person>
			<person>
				<givenname>Alan R.</givenname>
				<surname>Hevner</surname>
			</person>
		</names>
		<date value="1985"/>
		<abstract>
			<richtext>
				<p>An enhanced version of the Entity-Relationship (ER) data model called the Entity-Category-Relationship (ECR) data model is presented. The principal extension is the introduction of the concept of a category. Categories permit the grouping of entities from different entity types according to the roles they play in a relationship, as well as the representation of ISA and generalization hierarchies. The structures of the ECR data model are defined, and a graphic representation technique for their display is presented. Language operations to define and use an ECR database are defined. Two realistic examples of the use of the ECR model for database design are demonstrated. The examples show how ECR structures can be directly mapped into relational and network structures. The definition of derived relationships on an ECR database gives the power to phrase higher order recursive queries in a first order query language.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1016/0169-023X(85)90027-8</identifier>
		<title type="sharef:secondaryTitle">Data &amp; Knowledge Engineering</title>
		<number>1</number>
		<pages>75-116</pages>
		<title type="sharef:primaryTitle">The Category Concept: An Extension to the Entity-Relationship Model</title>
		<field type="bibtex:topic">eer[0.8] ecr[1]</field>
		<volume>1</volume>
	</reference>
	<reference name="sch04d" src="bibtex:article" src-info="bibtex:line-5935" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Klaus-Dieter</givenname>
				<surname>Schewe</surname>
			</person>
			<person>
				<givenname>Bernhard</givenname>
				<surname>Thalheim</surname>
			</person>
		</names>
		<date value="2004-08"/>
		<abstract>
			<richtext>
				<p>This paper presents the conceptual modelling parts of a methodology for the design of large-scale data-intensive web information systems (WISs) that is based on an abstract abstraction layer model (ALM). It concentrates on the two most important layers in this model: a business layer and a conceptual layer. The major activities on the business layer deal with user profiling and storyboarding, which addresses the design of an underlying application story. The core of such a story can be expressed by a directed multi-graph, in which the vertices represent scenes and the edges actions by the users including navigation. This leads to story algebras which can then be used to personalise the WIS to the needs of a user with a particular profile. The major activities on the conceptual layer address the support of scenes by modelling media types, which combine links to databases via extended views with the generation of navigation structures, operations supporting the activities in the storyboard, hierarchical presentations, and adaptivity to users, end-devices and channels.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1016/j.datak.2004.08.005</identifier>
		<title type="sharef:secondaryTitle">Data &amp; Knowledge Engineering</title>
		<number>2</number>
		<pages>147-188</pages>
		<title type="sharef:primaryTitle">Conceptual Modelling of Web Information Systems</title>
		<volume>54</volume>
	</reference>
	<reference name="chi94b" src="bibtex:article" src-info="bibtex:line-5952" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Richard</givenname>
				<surname>Chimera</surname>
			</person>
			<person>
				<givenname>Ben</givenname>
				<surname>Shneiderman</surname>
			</person>
		</names>
		<date value="1994-10"/>
		<abstract>
			<richtext>
				<p>Three different interfaces were used to browse a large (1296 items) table of contents. A fully expanded stable interface, expand/contract interface, and multipane interface were studied in a between-groups experiment with 41 novice participants. Nine timed fact retrieval tasks were performed; each task is analyzed and discussed separately. We found that both the expand/contract and multipane interfaces produced significantly faster times than the stable interface for many tasks using this large hierarchy; other advantages of the expand/contract and multipane interfaces over the stable interface are discussed. The animation characteristics of the expand/contract interface appear to play a major role. Refinements to the multipane and expand/contract interfaces are suggested. A predictive model for measuring navigation effort of each interface is presented.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/185462.185483</identifier>
		<title type="sharef:secondaryTitle">ACM Transactions on Information Systems</title>
		<number>4</number>
		<pages>383-406</pages>
		<title type="sharef:primaryTitle">An Exploratory Evaluation of Three Interfaces for Browsing Large Hierarchical Tables of Contents</title>
		<identifier type="sharef:uri">http://portal.acm.org/citation.cfm?doid=185462.185483</identifier>
		<volume>12</volume>
	</reference>
	<reference name="fen02" src="bibtex:article" src-info="bibtex:line-5966" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Ling</givenname>
				<surname>Feng</surname>
			</person>
			<person>
				<givenname>Elizabeth</givenname>
				<surname>Chang</surname>
			</person>
			<person>
				<givenname>Tharam S.</givenname>
				<surname>Dillon</surname>
			</person>
		</names>
		<date value="2002-10"/>
		<abstract>
			<richtext>
				<p>The Extensible Markup Language (XML) is fast emerging as the dominant standard for describing and interchanging data among various systems and databases on the Internet. It offers the Document Type Definition (DTD) as a formalism for defining the syntax and structure of XML documents. The XML Schema definition language, as a replacement for the DTD, provides more rich facilities for defining and constraining the content of XML documents. However, it does not concentrate on the semantics that underlies these documents, representing a logical data model rather than a conceptual model. To enable efficient business application development in large-scale electronic commerce environments, it is necessary to describe and model real-world data semantics and their complex interrelationships. In this article, we describe a design methodology for XML documents. The aim is to enforce XML conceptual modeling power and bridge the gap between software development and XML document structures. The proposed methodology is comprised of two design levels: the semantic level and the schema level. The first level is based on a semantic network, which provides semantic modeling of XML through four major components: a set of atomic and complex nodes, representing real-world objects; a set of directed edges, representing semantic relationships between the objects; a set of labels denoting different types of semantic relationships, including aggregation, generalization, association, and of-property relationships; and finally a set of constraints defined over nodes and edges to constrain semantic relationships and object domains. The other level of the proposed methodology is concerned with detailed XML schema design, including element/attribute declarations and simple/complex type definitions. The mapping between the two design levels is proposed to transform the XML semantic model into the XML Schema, based on which XML documents can be systematically created, managed, and validated.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/582415.582417</identifier>
		<title type="sharef:secondaryTitle">ACM Transactions on Information Systems</title>
		<number>4</number>
		<pages>390-421</pages>
		<title type="sharef:primaryTitle">A Semantic Network-Based Design Methodology for XML Documents</title>
		<identifier type="sharef:uri">http://portal.acm.org/citation.cfm?id=582415.582417</identifier>
		<volume>20</volume>
	</reference>
	<reference name="mel01b" src="bibtex:article" src-info="bibtex:line-5980" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Sergey</givenname>
				<surname>Melnik</surname>
			</person>
			<person>
				<givenname>Sriram</givenname>
				<surname>Raghavan</surname>
			</person>
			<person>
				<givenname>Beverly</givenname>
				<surname>Yang</surname>
			</person>
			<person>
				<givenname>Hector</givenname>
				<surname>Garcia-Molina</surname>
			</person>
		</names>
		<date value="2001"/>
		<title type="sharef:secondaryTitle">ACM Transactions on Information Systems</title>
		<number>3</number>
		<pages>217-241</pages>
		<title type="sharef:primaryTitle">Building a Distributed Full-Text Index for the Web</title>
		<identifier type="sharef:uri" resourceType="application/pdf">http://www-db.stanford.edu/~melnik/pub/melnik_TOIS01.pdf</identifier>
		<volume>19</volume>
	</reference>
	<reference name="kim91" src="bibtex:article" src-info="bibtex:line-5991" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Won</givenname>
				<surname>Kim</surname>
			</person>
			<person>
				<givenname>Nat</givenname>
				<surname>Ballou</surname>
			</person>
			<person>
				<givenname>Jorge F.</givenname>
				<surname>Garza</surname>
			</person>
			<person>
				<givenname>Darrell</givenname>
				<surname>Woelk</surname>
			</person>
		</names>
		<date value="1991"/>
		<field type="bibtex:index">ORION-2</field>
		<title type="sharef:secondaryTitle">ACM Transactions on Information Systems</title>
		<number>1</number>
		<pages>31-51</pages>
		<title type="sharef:primaryTitle">A Distributed Object-Oriented Database System Supporting Shared and Private Databases</title>
		<volume>9</volume>
	</reference>
	<reference name="gre87" src="bibtex:article" src-info="bibtex:line-6002" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Irene</givenname>
				<surname>Greif</surname>
			</person>
			<person>
				<givenname>Sunil</givenname>
				<surname>Sarin</surname>
			</person>
		</names>
		<date value="1987"/>
		<field type="bibtex:index">RTCAL, MPCAL, CES</field>
		<title type="sharef:secondaryTitle">ACM Transactions on Information Systems</title>
		<number>2</number>
		<pages>187-211</pages>
		<title type="sharef:primaryTitle">Data Sharing in Group Work</title>
		<volume>5</volume>
	</reference>
	<reference name="pet89" src="bibtex:article" src-info="bibtex:line-6017" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Larry L.</givenname>
				<surname>Peterson</surname>
			</person>
			<person>
				<givenname>Nick C.</givenname>
				<surname>Buchholz</surname>
			</person>
			<person>
				<givenname>Richard D.</givenname>
				<surname>Schlichting</surname>
			</person>
		</names>
		<date value="1989"/>
		<title type="sharef:secondaryTitle">ACM Transactions on Computer Systems</title>
		<number>3</number>
		<pages>217-246</pages>
		<title type="sharef:primaryTitle">Preserving and Using Context Information in Interprocess Communication</title>
		<volume>7</volume>
	</reference>
	<reference name="bir84" src="bibtex:article" src-info="bibtex:line-6027" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Andrew D.</givenname>
				<surname>Birrell</surname>
			</person>
			<person>
				<givenname>Bruce Jay</givenname>
				<surname>Nelson</surname>
			</person>
		</names>
		<date value="1984"/>
		<title type="sharef:secondaryTitle">ACM Transactions on Computer Systems</title>
		<number>1</number>
		<pages>39-59</pages>
		<title type="sharef:primaryTitle">Implementing Remote Procedure Calls</title>
		<field type="bibtex:topic">rpc[1]</field>
		<volume>2</volume>
	</reference>
	<reference name="sal84" src="bibtex:article" src-info="bibtex:line-6038" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Jerome H.</givenname>
				<surname>Saltzer</surname>
			</person>
			<person>
				<givenname>Darren P.</givenname>
				<surname>Reed</surname>
			</person>
			<person>
				<givenname>David D.</givenname>
				<surname>Clark</surname>
			</person>
		</names>
		<date value="1984-11"/>
		<identifier type="sharef:doi">10.1145/357401.357402</identifier>
		<title type="sharef:secondaryTitle">ACM Transactions on Computer Systems</title>
		<number>4</number>
		<pages>277-288</pages>
		<title type="sharef:primaryTitle">End-to-end Arguments in System Design</title>
		<volume>2</volume>
	</reference>
	<reference name="mol07" src="bibtex:article" src-info="bibtex:line-6054" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Anders</givenname>
				<surname>Møller</surname>
			</person>
			<person>
				<givenname>Mads</givenname>
				<surname>Østerby Olesen</surname>
			</person>
			<person>
				<givenname>Michael I.</givenname>
				<surname>Schwartzbach</surname>
			</person>
		</names>
		<date value="2007-08"/>
		<abstract>
			<richtext>
				<p>XSL Transformations (XSLT) is a programming language for defining transformations among XML languages. The structure of these languages is formally described by schemas, for example using DTD or XML Schema, which allows individual documents to be validated. However, existing XSLT tools offer no static guarantees that, under the assumption that the input is valid relative to the input schema, the output of the transformation is valid relative to the output schema. We present a validation technique for XSLT based on the XML graph formalism introduced in the static analysis of JWIG Web services and XACT XML transformations. Being able to provide static guarantees, we can detect a large class of errors in an XSLT stylesheet at the time it is written instead of later when it has been deployed, and thereby provide benefits similar to those of static type checkers for modern programming languages. Our analysis takes a pragmatic approach that focuses its precision on the essential language features but still handles the entire XSLT language. We evaluate the analysis precision on a range of real stylesheets and demonstrate how it may be useful in practice.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/1255450.1255454</identifier>
		<title type="sharef:secondaryTitle">ACM Transactions on Programming Languages and Systems</title>
		<number>4</number>
		<title type="sharef:primaryTitle">Static Validation of XSL Transformations</title>
		<field type="bibtex:topic">xslt[0.8]</field>
		<identifier type="sharef:uri" resourceType="application/pdf">http://www.brics.dk/~amoeller/papers/xslt/xslt.pdf</identifier>
		<volume>29</volume>
	</reference>
	<reference name="hos05" src="bibtex:article" src-info="bibtex:line-6068" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Haruo</givenname>
				<surname>Hosoya</surname>
			</person>
			<person>
				<givenname>Jérôme</givenname>
				<surname>Vouillon</surname>
			</person>
			<person>
				<givenname>Benjamin C.</givenname>
				<surname>Pierce</surname>
			</person>
		</names>
		<date value="2005-01"/>
		<abstract>
			<richtext>
				<p>We propose regular expression types as a foundation for statically typed XML processing languages. Regular expression types, like most schema languages for XML, introduce regular expression notations such as repetition (*), alternation (|), etc., to describe XML documents. The novelty of our type system is a semantic presentation of subtyping, as inclusion between the sets of documents denoted by two types. We give several examples illustrating the usefulness of this form of subtyping in XML processing. The decision problem for the subtype relation reduces to the inclusion problem between tree automata, which is known to be EXPTIME-complete. To avoid this high complexity in typical cases, we develop a practical algorithm that, unlike classical algorithms based on determinization of tree automata, checks the inclusion relation by a top-down traversal of the original type expressions. The main advantage of this algorithm is that it can exploit the property that type expressions being compared often share portions of their representations. Our algorithm is a variant of Aiken and Murphy's set-inclusion constraint solver, to which are added several new implementation techniques, correctness proofs, and preliminary performance measurements on some small programs in the domain of typed XML processing.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/1053468.1053470</identifier>
		<title type="sharef:secondaryTitle">ACM Transactions on Programming Languages and Systems</title>
		<number>1</number>
		<pages>46-90</pages>
		<title type="sharef:primaryTitle">Regular Expression Types for XML</title>
		<field type="bibtex:topic">xml[0.8]</field>
		<identifier type="sharef:uri">http://repository.upenn.edu/cis_papers/82/</identifier>
		<volume>27</volume>
	</reference>
	<reference name="nen03" src="bibtex:article" src-info="bibtex:line-6087" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Christian</givenname>
				<surname>Nentwich</surname>
			</person>
			<person>
				<givenname>Wolfgang</givenname>
				<surname>Emmerich</surname>
			</person>
			<person>
				<givenname>Anthony</givenname>
				<surname>Finkelstein</surname>
			</person>
			<person>
				<givenname>Ernst</givenname>
				<surname>Ellmer</surname>
			</person>
		</names>
		<date value="2003-01"/>
		<identifier type="sharef:doi">10.1145/839268.839271</identifier>
		<title type="sharef:secondaryTitle">ACM Transactions on Software Engineering and Methodology</title>
		<number>1</number>
		<pages>28-63</pages>
		<title type="sharef:primaryTitle">Flexible Consistency Checking</title>
		<field type="bibtex:topic">xlinkit[0.9]</field>
		<identifier type="sharef:uri" resourceType="application/pdf">http://www.systemwire.com/whitepapers/flexible_consistency_checking.pdf</identifier>
		<volume>12</volume>
	</reference>
	<reference name="bri99" src="bibtex:article" src-info="bibtex:line-6105" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Lionel C.</givenname>
				<surname>Briand</surname>
			</person>
			<person>
				<givenname>John W.</givenname>
				<surname>Daly</surname>
			</person>
			<person>
				<givenname>Jürgen K.</givenname>
				<surname>Wüst</surname>
			</person>
		</names>
		<date value="1999-01"/>
		<abstract>
			<richtext>
				<p>The increasing importance being placed on software measurement has led to an increased amount of research developing new software measures. Given the importance of object-oriented development techniques, one specific area where this has occurred is coupling measurement in object-oriented systems. However, despite a very interesting and rich body of work, there is little understanding of the motivation and empirical hypotheses behind many of these new measures. It is often difficult to determine how such measures relate to one another and for which application they can be used. As a consequence, it is very difficult for practitioners and researchers to obtain a clear picture of the state-of-the-art in order to select or define measures for object-oriented systems. This situation is addressed and clarified through several different activities. First, a standardized terminology and formalism for expressing measures is provided which ensures that all measures using it are expressed in a fully consistent and operational manner. Second, to provide a structured synthesis, a review of the existing frameworks and measures for coupling measurement in object-oriented systems takes place. Third, a unified framework, based on the issues discovered in the review, is provided and all existing measures are then classified according to this framework. This paper contributes to an increased understanding of the state-of-the-art: A mechanism is provided for comparing measures and their potential use, integrating existing measures which examine the same concepts in different ways, and facilitating more rigorous decision making regarding the definition of new measures and the selection of existing measures for a specific goal of measurement. In addition, our review of the state-of-the-art highlights that many measures are not defined in a fully operational form, and relatively few of them are based on explicit empirical models, as recommended by measurement theory.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1109/32.748920</identifier>
		<title type="sharef:secondaryTitle">IEEE Transactions on Software Engineering</title>
		<number>1</number>
		<pages>91-121</pages>
		<title type="sharef:primaryTitle">A Unified Framework for Coupling Measurement in Object-Oriented Systems</title>
		<volume>25</volume>
	</reference>
	<reference name="kri01" src="bibtex:article" src-info="bibtex:line-6122" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>David M.</givenname>
				<surname>Kristol</surname>
			</person>
		</names>
		<date value="2001-11"/>
		<abstract>
			<richtext>
				<p>How did we get from a world where cookies were something you ate and where "non-techies" were unaware of "Netscape cookies" to a world where cookies are a hot-button privacy issue for many computer users? This paper will describe how HTTP "cookies" work, and how Netscape's original specification evolved into an IETF Proposed Standard. I will also offer a personal perspective on how what began as a straightforward technical specification turned into a political flashpoint when it tried to address non-technical issues such as privacy.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/502152.502153</identifier>
		<title type="sharef:secondaryTitle">ACM Transactions on Internet Technology</title>
		<number>2</number>
		<pages>151-198</pages>
		<title type="sharef:primaryTitle">HTTP Cookies: Standards, Privacy, and Politics</title>
		<field type="bibtex:topic">cookie[0.9] http[0.8]</field>
		<volume>1</volume>
	</reference>
	<reference name="fie02" src="bibtex:article" src-info="bibtex:line-6136" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Roy Thomas</givenname>
				<surname>Fielding</surname>
			</person>
			<person>
				<givenname>Richard N.</givenname>
				<surname>Taylor</surname>
			</person>
		</names>
		<date value="2002-05"/>
		<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 application. The modern Web architecture 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. In this article we introduce the Representational State Transfer (REST) architectural style, developed as an abstract model of the Web architecture and used to guide our redesign and definition of the Hypertext Transfer Protocol and Uniform Resource Identifiers. We 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. We then compare the abstract model to the currently deployed Web architecture in order to elicit mismatches between the existing protocols and the applications they are intended to support.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/337180.337228</identifier>
		<title type="sharef:secondaryTitle">ACM Transactions on Internet Technology</title>
		<number>2</number>
		<pages>115-150</pages>
		<title type="sharef:primaryTitle">Principled Design of the Modern Web Architecture</title>
		<field type="bibtex:topic">rest[1]</field>
		<volume>2</volume>
	</reference>
	<reference name="lu05" src="bibtex:article" src-info="bibtex:line-6150" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Hongjun</givenname>
				<surname>Lu</surname>
			</person>
			<person>
				<givenname>Jeffrey Xu</givenname>
				<surname>Yu</surname>
			</person>
			<person>
				<givenname>Guoren</givenname>
				<surname>Wang</surname>
			</person>
			<person>
				<givenname>Shihui</givenname>
				<surname>Zheng</surname>
			</person>
			<person>
				<givenname>Haifeng</givenname>
				<surname>Jiang</surname>
			</person>
			<person>
				<givenname>Ge</givenname>
				<surname>Yu</surname>
			</person>
			<person>
				<givenname>Aoying</givenname>
				<surname>Zhou</surname>
			</person>
		</names>
		<date value="2005-02"/>
		<title type="sharef:secondaryTitle">ACM Transactions on Internet Technology</title>
		<number>1</number>
		<title type="sharef:primaryTitle">What Makes the Differences: Benchmarking XML Database Implementations</title>
		<field type="bibtex:topic">xdbms[0.8]</field>
		<volume>5</volume>
	</reference>
	<reference name="nen02" src="bibtex:article" src-info="bibtex:line-6161" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Christian</givenname>
				<surname>Nentwich</surname>
			</person>
			<person>
				<givenname>Licia</givenname>
				<surname>Capra</surname>
			</person>
			<person>
				<givenname>Wolfgang</givenname>
				<surname>Emmerich</surname>
			</person>
			<person>
				<givenname>Anthony</givenname>
				<surname>Finkelstein</surname>
			</person>
		</names>
		<date value="2002-05"/>
		<identifier type="sharef:doi">10.1145/514183.514186</identifier>
		<title type="sharef:secondaryTitle">ACM Transactions on Internet Technology</title>
		<number>2</number>
		<pages>151-185</pages>
		<title type="sharef:primaryTitle">xlinkit: A Consistency Checking and Smart Link Generation Service</title>
		<field type="bibtex:topic">xlinkit[0.9]</field>
		<identifier type="sharef:uri" resourceType="application/pdf">http://www.systemwire.com/whitepapers/xlinkit.pdf</identifier>
		<volume>2</volume>
	</reference>
	<reference name="blu01" src="bibtex:article" src-info="bibtex:line-6175" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Marjory S.</givenname>
				<surname>Blumenthal</surname>
			</person>
			<person>
				<givenname>David D.</givenname>
				<surname>Clark</surname>
			</person>
		</names>
		<date value="2001-08"/>
		<identifier type="sharef:doi">10.1145/383034.383037</identifier>
		<title type="sharef:secondaryTitle">ACM Transactions on Internet Technology</title>
		<number>1</number>
		<pages>70-109</pages>
		<title type="sharef:primaryTitle">Rethinking the Design of the Internet: The End-to-end Arguments vs. the Brave New World</title>
		<volume>1</volume>
	</reference>
	<reference name="kho86" src="bibtex:article" src-info="bibtex:line-6191" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Setrag N.</givenname>
				<surname>Khoshafian</surname>
			</person>
			<person>
				<givenname>George P.</givenname>
				<surname>Copeland</surname>
			</person>
		</names>
		<date value="1986-11"/>
		<abstract>
			<richtext>
				<p>Identity is that property of an object which distinguishes each object from all others. Identity has been investigated almost independently in general-purpose programming languages and database languages. Its importance is growing as these two environments evolve and merge. We describe a continuum between weak and strong support of identity, and argue for the incorporation of the strong notion of identity at the conceptual level in languages for general purpose programming, database systems and their hybrids. We define a data model that can directly describe complex objects, and show that identity can easily be incorporated in it. Finally, we compare different implementation schemes for identity and argue that a surrogate-based implementation scheme is needed to support the strong notion of identity.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/960112.28739</identifier>
		<title type="sharef:secondaryTitle">ACM SIGPLAN Notices</title>
		<number>11</number>
		<pages>406-416</pages>
		<title type="sharef:primaryTitle">Object Identity</title>
		<identifier type="sharef:uri">http://portal.acm.org/citation.cfm?id=960112.28739</identifier>
		<volume>21</volume>
	</reference>
	<reference name="lis87" src="bibtex:article" src-info="bibtex:line-6205" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Barbara</givenname>
				<surname>Liskov</surname>
			</person>
		</names>
		<date value="1987-05"/>
		<identifier type="sharef:doi">10.1145/62138.62141</identifier>
		<title type="sharef:secondaryTitle">ACM SIGPLAN Notices</title>
		<number>5</number>
		<pages>17-34</pages>
		<title type="sharef:primaryTitle">Data Abstraction and Hierarchy</title>
		<field type="bibtex:topic">lsp[1]</field>
		<volume>23</volume>
	</reference>
	<reference name="lis74" src="bibtex:article" src-info="bibtex:line-6218" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Barbara</givenname>
				<surname>Liskov</surname>
			</person>
			<person>
				<givenname>Stephen</givenname>
				<surname>Zilles</surname>
			</person>
		</names>
		<date value="1974-04"/>
		<abstract>
			<richtext>
				<p>The motivation behind the work in very-high-level languages is to ease the programming task by providing the programmer with a language containing primitives or abstractions suitable to his problem area. The programmer is then able to spend his effort in the right place; he concentrates on solving his problem, and the resulting program will be more reliable as a result. Clearly, this is a worthwhile goal. Unfortunately, it is very difficult for a designer to select in advance all the abstractions which the users of his language might need. If a language is to be used at all, it is likely to be used to solve problems which its designer did not envision, and for which the abstractions embedded in the language are not sufficient. This paper presents an approach which allows the set of built-in abstractions to be augmented when the need for a new data abstraction is discovered. This approach to the handling of abstraction is an outgrowth of work on designing a language for structured programming. Relevant aspects of this language are described, and examples of the use and definitions of abstractions are given.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/942572.807045</identifier>
		<title type="sharef:secondaryTitle">ACM SIGPLAN Notices</title>
		<number>4</number>
		<pages>50-59</pages>
		<title type="sharef:primaryTitle">Programming with Abstract Data Types</title>
		<field type="bibtex:topic">adt[0.9]</field>
		<volume>9</volume>
	</reference>
	<reference name="hug88" src="bibtex:article" src-info="bibtex:line-6236" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Lawrence E.</givenname>
				<surname>Hughes</surname>
			</person>
		</names>
		<date value="1988"/>
		<field type="bibtex:index">multicast, communication primitives</field>
		<title type="sharef:secondaryTitle">Software — Practice &amp; Experience</title>
		<number>3</number>
		<pages>15-27</pages>
		<title type="sharef:primaryTitle">A Multicast Interface for UNIX 4.3</title>
		<volume>18</volume>
	</reference>
	<reference name="ger00" src="bibtex:article" src-info="bibtex:line-6251" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Ed</givenname>
				<surname>Gerck</surname>
			</person>
		</names>
		<date value="2000-07"/>
		<title type="sharef:secondaryTitle">The Bell</title>
		<number>3</number>
		<pages>8</pages>
		<title type="sharef:primaryTitle">Overview of Certification Systems: X.509, PKIX, CA, PGP and SKIP</title>
		<field type="bibtex:topic">x509[0.8] pkix[0.8] pgp[0.8] skip[0.8]</field>
		<identifier type="sharef:uri" resourceType="application/pdf">http://www.thebell.net/papers/certover.pdf</identifier>
		<volume>1</volume>
	</reference>
	<reference name="mar96a" src="bibtex:article" src-info="bibtex:line-6268" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Robert C.</givenname>
				<surname>Martin</surname>
			</person>
		</names>
		<date value="1996-01"/>
		<title type="sharef:secondaryTitle">C++ Report</title>
		<title type="sharef:primaryTitle">The Open Closed Principle</title>
		<field type="bibtex:topic">ocp[1]</field>
		<identifier type="sharef:uri" resourceType="application/pdf">http://www.objectmentor.com/resources/articles/ocp.pdf</identifier>
		<volume>8</volume>
	</reference>
	<reference name="mar96b" src="bibtex:article" src-info="bibtex:line-6279" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Robert C.</givenname>
				<surname>Martin</surname>
			</person>
		</names>
		<date value="1996-03"/>
		<title type="sharef:secondaryTitle">C++ Report</title>
		<title type="sharef:primaryTitle">The Liskov Substitution Principle</title>
		<field type="bibtex:topic">lsp[1]</field>
		<identifier type="sharef:uri" resourceType="application/pdf">http://www.objectmentor.com/resources/articles/lsp.pdf</identifier>
		<volume>8</volume>
	</reference>
	<reference name="mar96c" src="bibtex:article" src-info="bibtex:line-6290" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Robert C.</givenname>
				<surname>Martin</surname>
			</person>
		</names>
		<date value="1996-05"/>
		<title type="sharef:secondaryTitle">C++ Report</title>
		<title type="sharef:primaryTitle">The Dependency Inversion Principle</title>
		<field type="bibtex:topic">dip[1]</field>
		<identifier type="sharef:uri" resourceType="application/pdf">http://www.objectmentor.com/resources/articles/dip.pdf</identifier>
		<volume>8</volume>
	</reference>
	<reference name="mar96d" src="bibtex:article" src-info="bibtex:line-6301" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Robert C.</givenname>
				<surname>Martin</surname>
			</person>
		</names>
		<date value="1996-08"/>
		<title type="sharef:secondaryTitle">C++ Report</title>
		<title type="sharef:primaryTitle">The Interface Segregation Principle</title>
		<field type="bibtex:topic">isp[1]</field>
		<identifier type="sharef:uri" resourceType="application/pdf">http://www.objectmentor.com/resources/articles/isp.pdf</identifier>
		<volume>8</volume>
	</reference>
	<reference name="thi97" src="bibtex:article" src-info="bibtex:line-6316" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Paul</givenname>
				<surname>Thistlewaite</surname>
			</person>
		</names>
		<date value="1997"/>
		<title type="sharef:secondaryTitle">Information Processing and Management</title>
		<number>2</number>
		<pages>161-173</pages>
		<title type="sharef:primaryTitle">Automatic Construction and Management of Large Open Webs</title>
		<volume>33</volume>
	</reference>
	<reference name="dro02" src="bibtex:article" src-info="bibtex:line-6326" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>M. Carl</givenname>
				<surname>Drott</surname>
			</person>
		</names>
		<date value="2002-03"/>
		<abstract>
			<richtext>
				<p>Sixty corporate websites selected from the Fortune Global 500 companies were examined in 2000 and again in 2001 to see if they provided support for automatic indexing. In particular, use of the robots.txt and Meta tags for "keywords" and "description" was examined. Slightly fewer than half of the sites provided one or both of these aids. Among sites providing indexing aids there was a clear under-representation of Asian sites. Nearly 80% of the sites used Java, suggesting a reasonable level of technical sophistication among website creators. About one-third of the sites used cookies, raising the possibility that repeat visitors might find the navigation of the site customized to their needs. Overall an increase in the use of indexing aids, especially Meta tags, represents one way in which web robots could index sites more quickly and thus improve overall index coverage of the web.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1016/S0306-4573(01)00039-5</identifier>
		<title type="sharef:secondaryTitle">Information Processing and Management</title>
		<number>2</number>
		<pages>209-219</pages>
		<title type="sharef:primaryTitle">Indexing Aids at Corporate Websites: The Use of Robots.txt and META Tags</title>
		<volume>38</volume>
	</reference>
	<reference name="eva07" src="bibtex:article" src-info="bibtex:line-6343" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>A.J.</givenname>
				<surname>Evans</surname>
			</person>
			<person>
				<givenname>T.</givenname>
				<surname>Waters</surname>
			</person>
		</names>
		<date value="2007"/>
		<abstract>
			<richtext>
				<p>Most people do not use a formal geographical vocabulary, however they do use a wide variety of geographical terms on a daily basis. Identifiers such as 'Downtown' are components of a vernacular geography which is vastly more used than the coordinates and scientifically defined variables beloved of most professional analysts. Terms like these build into the jointly defined world-views within which we all act. Despite its importance for policymaking and quality of life, attention is rarely paid to this vernacular geography because it is hard to capture and use. This paper presents tools for capturing this geography, an example of the tools' use to define 'High Crime' areas, and an initial discussion of the issues surrounding vernacular data. While the problems involved in analysing such data are not to be underestimated, such a system aims to pull together professional and popular geographical understanding, to the advantage of both.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1504/IJTPM.2007.014547</identifier>
		<title type="sharef:secondaryTitle">International Journal of Technology, Policy and Management</title>
		<number>2</number>
		<pages>134-150</pages>
		<title type="sharef:primaryTitle">Mapping Vernacular Geography: Web-based GIS Tools for Capturing 'fuzzy' or 'vague' Entities</title>
		<volume>7</volume>
	</reference>
	<reference name="sam84" src="bibtex:article" src-info="bibtex:line-6359" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Hanan</givenname>
				<surname>Samet</surname>
			</person>
		</names>
		<date value="1984-06"/>
		<identifier type="sharef:doi">10.1145/356924.356930</identifier>
		<title type="sharef:secondaryTitle">ACM Computing Surveys</title>
		<number>2</number>
		<pages>187-260</pages>
		<title type="sharef:primaryTitle">The Quadtree and Related Hierarchical Data Structures</title>
		<volume>16</volume>
	</reference>
	<reference name="eug03" src="bibtex:article" src-info="bibtex:line-6371" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Patrick Th.</givenname>
				<surname>Eugster</surname>
			</person>
			<person>
				<givenname>Pascal A.</givenname>
				<surname>Felber</surname>
			</person>
			<person>
				<givenname>Rachid</givenname>
				<surname>Guerraoui</surname>
			</person>
			<person>
				<givenname>Anne-Marie</givenname>
				<surname>Kermarrec</surname>
			</person>
		</names>
		<date value="2003-06"/>
		<abstract>
			<richtext>
				<p>Well adapted to the loosely coupled nature of distributed interaction in large-scale applications, the publish/subscribe communication paradigm has recently received increasing attention. With systems based on the publish/subscribe interaction scheme, subscribers register their interest in an event, or a pattern of events, and are subsequently asynchronously notified of events generated by publishers. Many variants of the paradigm have recently been proposed, each variant being specifically adapted to some given application or network model. This paper factors out the common denominator underlying these variants: full decoupling of the communicating entities in time, space, and synchronization. We use these three decoupling dimensions to better identify commonalities and divergences with traditional interaction paradigms. The many variations on the theme of publish/subscribe are classified and synthesized. In particular, their respective benefits and shortcomings are discussed both in terms of interfaces and implementations.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/857076.857078</identifier>
		<title type="sharef:secondaryTitle">ACM Computing Surveys</title>
		<number>2</number>
		<pages>114-131</pages>
		<title type="sharef:primaryTitle">The Many Faces of Publish/Subscribe</title>
		<identifier type="sharef:uri">http://portal.acm.org/citation.cfm?doid=857076.857078</identifier>
		<volume>35</volume>
	</reference>
	<reference name="kel05" src="bibtex:article" src-info="bibtex:line-6385" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Caitlin</givenname>
				<surname>Kelleher</surname>
			</person>
			<person>
				<givenname>Randy</givenname>
				<surname>Pausch</surname>
			</person>
		</names>
		<date value="2005-06"/>
		<abstract>
			<richtext>
				<p>Since the early 1960's, researchers have built a number of programming languages and environments with the intention of making programming accessible to a larger number of people. This article presents a taxonomy of languages and environments designed to make programming more accessible to novice programmers of all ages. The systems are organized by their primary goal, either to teach programming or to use programming to empower their users, and then, by each system's authors' approach, to making learning to program easier for novice programmers. The article explains all categories in the taxonomy, provides a brief description of the systems in each category, and suggests some avenues for future work in novice programming environments and languages.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/1089733.1089734</identifier>
		<title type="sharef:secondaryTitle">ACM Computing Surveys</title>
		<number>2</number>
		<pages>83-137</pages>
		<title type="sharef:primaryTitle">Lowering the Barriers to Programming: A Taxonomy of Programming Environments and Languages for Novice Programmers</title>
		<identifier type="sharef:uri">http://portal.acm.org/citation.cfm?id=1089734</identifier>
		<volume>37</volume>
	</reference>
	<reference name="tol05" src="bibtex:article" src-info="bibtex:line-6399" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>William</givenname>
				<surname>Tolone</surname>
			</person>
			<person>
				<givenname>Gail-Joon</givenname>
				<surname>Ahn</surname>
			</person>
			<person>
				<givenname>Tanusree</givenname>
				<surname>Pai</surname>
			</person>
			<person>
				<givenname>Seng-Phil</givenname>
				<surname>Hong</surname>
			</person>
		</names>
		<date value="2005-03"/>
		<abstract>
			<richtext>
				<p>Balancing the competing goals of collaboration and security is a difficult, multidimensional problem. Collaborative systems often focus on building useful connections among people, tools, and information while security seeks to ensure the availability, confidentiality, and integrity of these same elements. In this article, we focus on one important dimension of this problem — access control. The article examines existing access control models as applied to collaboration, highlighting not only the benefits, but also the weaknesses of these models.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/1057977.1057979</identifier>
		<title type="sharef:secondaryTitle">ACM Computing Surveys</title>
		<number>1</number>
		<pages>29-41</pages>
		<title type="sharef:primaryTitle">Access Control in Collaborative Systems</title>
		<field type="bibtex:topic">ac[0.8] acl[0.7] rbac[0.7] tbac[0.7] tmac[0.7]</field>
		<identifier type="sharef:uri">http://portal.acm.org/citation.cfm?id=1057977.1057979</identifier>
		<volume>37</volume>
	</reference>
	<reference name="kos00" src="bibtex:article" src-info="bibtex:line-6414" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Donald</givenname>
				<surname>Kossmann</surname>
			</person>
		</names>
		<date value="2000-12"/>
		<abstract>
			<richtext>
				<p>Distributed data processing is becoming a reality. Businesses want to do it for many reasons, and they often must do it in order to stay competitive. While much of the infrastructure for distributed data processing is already there (e.g., modern network technology), a number of issues make distributed data processing still a complex undertaking: (1) distributed systems can become very large, involving thousands of heterogeneous sites including PCs and mainframe server machines; (2) the state of a distributed system changes rapidly because the load of sites varies over time and new sites are added to the system; (3) legacy systems need to be integrated — such legacy systems usually have not been designed for distributed data processing and now need to interact with other (modern) systems in a distributed environment. This paper presents the state of the art of query processing for distributed database and information systems. The paper presents the "textbook" architecture for distributed query processing and a series of techniques that are particularly useful for distributed database systems. These techniques include special join techniques, techniques to exploit intraquery parallelism, techniques to reduce communication costs, and techniques to exploit caching and replication of data. Furthermore, the paper discusses different kinds of distributed systems such as client-server, middleware (multitier), and heterogeneous database systems, and shows how query processing works in these systems.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/371578.371598</identifier>
		<title type="sharef:secondaryTitle">ACM Computing Surveys</title>
		<number>4</number>
		<pages>422-469</pages>
		<title type="sharef:primaryTitle">The State of the Art in Distributed Query Processing</title>
		<identifier type="sharef:uri">http://portal.acm.org/citation.cfm?id=371598</identifier>
		<volume>32</volume>
	</reference>
	<reference name="nel99" src="bibtex:article" src-info="bibtex:line-6428" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Theodor Holm</givenname>
				<surname>Nelson</surname>
			</person>
		</names>
		<date value="1999-12"/>
		<abstract>
			<richtext>
				<p>Project Xanadu, the original hypertext project, is often misunderstood as an attempt to create the World Wide Web. It has always been much more ambitious, proposing an entire form of literature where links do not break as versions change; where documents may be closely compared side by side and closely annotated; where it is possible to see the origins of every quotation; and in which there is a valid copyright system — a literary, legal and business arrangement — for frictionless, non-negotiated quotation at any time and in any amount. The Web trivialized this original Xanadu model, vastly but incorrectly simplifying these problems to a world of fragile ever-breaking oneway links, with no recognition of change or copyright, and no support for multiple versions or principled re-use. Fonts and glitz, rather than content connective structure, prevail. Serious electronic literature (for scholarship, detailed controversy and detailed collaboration) must support bidirectional and profuse links, which cannot be embedded; and must offer facilities for easily tracking re-use on a principled basis among versions and quotations. Xanalogical literary structure is a unique symmetrical connective system for text (and other separable media elements), with two complementary forms of connection that achieve these functions — survivable deep linkage (content links) and recognizable, visible re-use (transclusion). Both of these are easily implemented by a document model using content lists which reference stabilized media. This system of literary structure offers uniquely integrated methods for version management, side-by-side comparison and visualizable re-use, which lead to a radically beneficial and principled copyright system (endorsed in principle by the ACM). Though dauntingly far from the standards which have presently caught on, this design is still valid and may yet find a place in the evolving Internet universe.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/345966.346033</identifier>
		<field type="bibtex:index">hypermedia</field>
		<title type="sharef:secondaryTitle">ACM Computing Surveys</title>
		<number>4es</number>
		<title type="sharef:primaryTitle">Xanalogical Structure, Needed Now More Than Ever: Parallel Documents, Deep Links to Content, Deep Versioning, and Deep Re-Use</title>
		<identifier type="sharef:uri">http://portal.acm.org/citation.cfm?id=346033</identifier>
		<volume>31</volume>
	</reference>
	<reference name="dav99a" src="bibtex:article" src-info="bibtex:line-6442" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Hugh C.</givenname>
				<surname>Davis</surname>
			</person>
		</names>
		<date value="1999-12"/>
		<abstract>
			<richtext>
				<p>Hypertext links are connections between documents or parts of documents. Generally the ends of links are represented by some kind of a reference to a document or part of a document. When documents are moved or changed these references may cease to resolve to the correct places. This paper reflects on the causes of this problem and reviews techniques that may be used to maintain link integrity.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">345966.346026</identifier>
		<field type="bibtex:index">hypermedia</field>
		<title type="sharef:secondaryTitle">ACM Computing Surveys</title>
		<number>4es</number>
		<title type="sharef:primaryTitle">Hypertext Link Integrity</title>
		<identifier type="sharef:uri" resourceType="text/html">http://www.cs.brown.edu/memex/ACM_HypertextTestbed/papers/54.html</identifier>
		<identifier type="sharef:uri">http://portal.acm.org/citation.cfm?id=346026</identifier>
		<volume>31</volume>
	</reference>
	<reference name="ver99" src="bibtex:article" src-info="bibtex:line-6457" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Janet</givenname>
				<surname>Verbyla</surname>
			</person>
		</names>
		<date value="1999-12"/>
		<abstract>
			<richtext>
				<p>The aim of this review paper is to provide a "big picture snapshot" of the multiple facets of hypermedia linking. In providing this snapshot, the paper overviews key issues in both categorizing these facets and exploiting them to design effective implementations of links. The presentation is structured around the process of untying the perception of the link and its capabilities from the limitations of defining it in terms of the currently most pervasive implementation of the link, namely links in HTML. In the process, the paper draws on the work of Paul Thistlewaite on the linking issues for large volatile hyperbases.</p>
			</richtext>
		</abstract>
		<field type="bibtex:index">hypermedia</field>
		<title type="sharef:secondaryTitle">ACM Computing Surveys</title>
		<number>4es</number>
		<title type="sharef:primaryTitle">Unlinking the Link</title>
		<identifier type="sharef:uri" resourceType="text/html">http://www.cs.brown.edu/memex/ACM_HypertextTestbed/papers/61.html</identifier>
		<volume>31</volume>
	</reference>
	<reference name="weg96" src="bibtex:article" src-info="bibtex:line-6470" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Peter</givenname>
				<surname>Wegner</surname>
			</person>
		</names>
		<date value="1996-03"/>
		<identifier type="sharef:doi">10.1145/234313.234424</identifier>
		<title type="sharef:secondaryTitle">ACM Computing Surveys</title>
		<number>1</number>
		<pages>285-187</pages>
		<title type="sharef:primaryTitle">Interoperability</title>
		<volume>28</volume>
	</reference>
	<reference name="vit99" src="bibtex:article" src-info="bibtex:line-6482" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Fabio</givenname>
				<surname>Vitali</surname>
			</person>
		</names>
		<date value="1999-12"/>
		<abstract>
			<richtext>
				<p>Keeping multiple versions of the same electronic artifact is a necessity in many authoring fields, and a serious advantage in all of them. Hypermedia adds to that the issue of relationship management. This poses a few additional problems, especially conceptual ones, but it also provides a reliable and safe solution for the well-known problem of the referential integrity of links. The field of hypermedia has dealt with versioning issues for a long time, since Xanadu considered it a fundamental mechanism for its inner workings. Newer systems, and an important protocol for the WWW, WebDAV, constitute modern approaches to the problem.</p>
			</richtext>
		</abstract>
		<title type="sharef:secondaryTitle">ACM Computing Surveys</title>
		<number>4es</number>
		<title type="sharef:primaryTitle">Versioning Hypermedia</title>
		<field type="bibtex:topic">webdav[0.7]</field>
		<identifier type="sharef:uri" resourceType="text/html">http://www.cs.brown.edu/memex/ACM_HypertextTestbed/papers/50.html</identifier>
		<volume>31</volume>
	</reference>
	<reference name="car99" src="bibtex:article" src-info="bibtex:line-6495" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Leslie A.</givenname>
				<surname>Carr</surname>
			</person>
			<person>
				<givenname>Wendy</givenname>
				<surname>Hall</surname>
			</person>
			<person>
				<givenname>David C.</givenname>
				<surname>De Roure</surname>
			</person>
		</names>
		<date value="1999-12"/>
		<identifier type="sharef:doi">10.1145/345966.345989</identifier>
		<field type="bibtex:index">hypermedia</field>
		<title type="sharef:secondaryTitle">ACM Computing Surveys</title>
		<number>4es</number>
		<title type="sharef:primaryTitle">The Evolution of Hypertext Link Services</title>
		<volume>31</volume>
	</reference>
	<reference name="der99" src="bibtex:article" src-info="bibtex:line-6507" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Steven J.</givenname>
				<surname>DeRose</surname>
			</person>
		</names>
		<date value="1999-12"/>
		<identifier type="sharef:doi">10.1145/345966.346015</identifier>
		<title type="sharef:secondaryTitle">ACM Computing Surveys</title>
		<number>4es</number>
		<title type="sharef:primaryTitle">XML Linking</title>
		<field type="bibtex:topic">xlink[0.9] xpointer[0.9] xpath1[0.9]</field>
		<volume>31</volume>
	</reference>
	<reference name="cha76" src="bibtex:article" src-info="bibtex:line-6519" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Donald D.</givenname>
				<surname>Chamberlin</surname>
			</person>
		</names>
		<date value="1976-03"/>
		<abstract>
			<richtext>
				<p>The essential concepts of the relational data model are defined, and normalization, relational languages based on the model, as well as advantages and implementations of relational systems are discussed.</p>
			</richtext>
		</abstract>
		<title type="sharef:secondaryTitle">ACM Computing Surveys</title>
		<number>1</number>
		<title type="sharef:primaryTitle">Relational Data-Base Management Systems</title>
		<field type="bibtex:topic">rdbms[1]</field>
		<volume>8</volume>
	</reference>
	<reference name="cam99" src="bibtex:article" src-info="bibtex:line-6535" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Andrew T.</givenname>
				<surname>Campbell</surname>
			</person>
			<person>
				<givenname>Herman G.</givenname>
				<surname>De Meer</surname>
			</person>
			<person>
				<givenname>Michael E.</givenname>
				<surname>Kounavis</surname>
			</person>
			<person>
				<givenname>Kazuho</givenname>
				<surname>Miki</surname>
			</person>
			<person>
				<givenname>John B.</givenname>
				<surname>Vicente</surname>
			</person>
			<person>
				<givenname>Daniel</givenname>
				<surname>Villela</surname>
			</person>
		</names>
		<date value="1999-04"/>
		<title type="sharef:secondaryTitle">ACM Computer Communications Review</title>
		<number>2</number>
		<pages>7-23</pages>
		<title type="sharef:primaryTitle">A Survey of Programmable Networks</title>
		<identifier type="sharef:uri" resourceType="text/html">http://citeseer.nj.nec.com/campbell99survey.html</identifier>
		<identifier type="sharef:uri" resourceType="application/pdf">http://comet.columbia.edu/mobiware/papers/survey_ccr.pdf</identifier>
		<volume>29</volume>
	</reference>
	<reference name="tsu92" src="bibtex:article" src-info="bibtex:line-6548" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Gene</givenname>
				<surname>Tsudik</surname>
			</person>
		</names>
		<date value="1992-10"/>
		<identifier type="sharef:doi">10.1145/141809.141812</identifier>
		<title type="sharef:secondaryTitle">ACM Computer Communications Review</title>
		<number>5</number>
		<pages>29-38</pages>
		<title type="sharef:primaryTitle">Message Authentication with One-way Hash Functions</title>
		<volume>22</volume>
	</reference>
	<reference name="hei97" src="bibtex:article" src-info="bibtex:line-6560" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>John</givenname>
				<surname>Heidemann</surname>
			</person>
		</names>
		<date value="1997-04"/>
		<title type="sharef:secondaryTitle">ACM Computer Communications Review</title>
		<number>2</number>
		<pages>65-73</pages>
		<title type="sharef:primaryTitle">Performance Interactions Between P-HTTP and TCP Implementations</title>
		<field type="bibtex:topic">http[0.8] tcp[0.7] phttp[0.8]</field>
		<volume>27</volume>
	</reference>
	<reference name="mog95" src="bibtex:article" src-info="bibtex:line-6572" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Jeffrey C.</givenname>
				<surname>Mogul</surname>
			</person>
		</names>
		<date value="1995-10"/>
		<title type="sharef:secondaryTitle">ACM Computer Communications Review</title>
		<number>4</number>
		<title type="sharef:primaryTitle">The Case for Persistent-Connection HTTP</title>
		<field type="bibtex:topic">phttp[1]</field>
		<volume>25</volume>
	</reference>
	<reference name="cla95" src="bibtex:article" src-info="bibtex:line-6583" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>David D.</givenname>
				<surname>Clark</surname>
			</person>
		</names>
		<date value="1995-01"/>
		<identifier type="sharef:doi">10.1145/205447.205458</identifier>
		<title type="sharef:secondaryTitle">ACM Computer Communications Review</title>
		<number>1</number>
		<pages>102-111</pages>
		<title type="sharef:primaryTitle">The Design Philosophy of the DARPA Internet Protocols</title>
		<volume>25</volume>
	</reference>
	<reference name="mog97" src="bibtex:article" src-info="bibtex:line-6595" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Jeffrey C.</givenname>
				<surname>Mogul</surname>
			</person>
			<person>
				<givenname>Fred</givenname>
				<surname>Douglis</surname>
			</person>
			<person>
				<givenname>Anja</givenname>
				<surname>Feldmann</surname>
			</person>
			<person>
				<givenname>Balachander</givenname>
				<surname>Krishnamurthy</surname>
			</person>
		</names>
		<date value="1997-10"/>
		<title type="sharef:secondaryTitle">ACM Computer Communications Review</title>
		<number>4</number>
		<title type="sharef:primaryTitle">Potential benefits of delta-encoding and data compression for HTTP</title>
		<field type="bibtex:topic">http[0.7]</field>
		<volume>27</volume>
	</reference>
	<reference name="nie97" src="bibtex:article" src-info="bibtex:line-6606" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Henrik</givenname>
				<surname>Frystyk Nielsen</surname>
			</person>
			<person>
				<givenname>Jim</givenname>
				<surname>Gettys</surname>
			</person>
			<person>
				<givenname>Anselm</givenname>
				<surname>Baird-Smith</surname>
			</person>
			<person>
				<givenname>Eric</givenname>
				<surname>Prud'Hommeaux</surname>
			</person>
			<person>
				<givenname>Håkon Wium</givenname>
				<surname>Lie</surname>
			</person>
			<person>
				<givenname>Chris</givenname>
				<surname>Lilley</surname>
			</person>
		</names>
		<date value="1997-10"/>
		<title type="sharef:secondaryTitle">ACM Computer Communications Review</title>
		<number>4</number>
		<title type="sharef:primaryTitle">Network Performance Effects of HTTP/1.1, CSS1, and PNG</title>
		<field type="bibtex:topic">http[0.8] css[0.8] png[0.8]</field>
		<volume>27</volume>
	</reference>
	<reference name="sch92b" src="bibtex:article" src-info="bibtex:line-6617" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Eve M.</givenname>
				<surname>Schooler</surname>
			</person>
			<person>
				<givenname>Stephen L.</givenname>
				<surname>Casner</surname>
			</person>
		</names>
		<date value="1992"/>
		<field type="bibtex:index">mbone</field>
		<title type="sharef:secondaryTitle">ACM Computer Communications Review</title>
		<number>3</number>
		<title type="sharef:primaryTitle">An Architecture for Multimedia Connection Management</title>
		<volume>22</volume>
	</reference>
	<reference name="jac88" src="bibtex:article" src-info="bibtex:line-6627" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Van</givenname>
				<surname>Jacobson</surname>
			</person>
			<person>
				<givenname>Michael J.</givenname>
				<surname>Karels</surname>
			</person>
		</names>
		<date value="1988-08"/>
		<field type="bibtex:index">TCP/IP, slow start</field>
		<title type="sharef:secondaryTitle">ACM Computer Communications Review</title>
		<number>4</number>
		<pages>314-329</pages>
		<title type="sharef:primaryTitle">Congestion Avoidance and Control</title>
		<volume>18</volume>
	</reference>
	<reference name="che85" src="bibtex:article" src-info="bibtex:line-6639" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>David R.</givenname>
				<surname>Cheriton</surname>
			</person>
			<person>
				<givenname>Stephen E.</givenname>
				<surname>Deering</surname>
			</person>
		</names>
		<date value="1985"/>
		<field type="bibtex:index">multicast</field>
		<title type="sharef:secondaryTitle">ACM Computer Communications Review</title>
		<number>4</number>
		<pages>172-179</pages>
		<title type="sharef:primaryTitle">Host Groups: A Multicast Extension for Datagram Internetworks</title>
		<volume>15</volume>
	</reference>
	<reference name="ros04" src="bibtex:article" src-info="bibtex:line-6654" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Arnon</givenname>
				<surname>Rosenthal</surname>
			</person>
			<person>
				<givenname>Len</givenname>
				<surname>Seligman</surname>
			</person>
			<person>
				<givenname>Scott</givenname>
				<surname>Renner</surname>
			</person>
		</names>
		<date value="2004-12"/>
		<abstract>
			<richtext>
				<p>For meaningful information exchange or integration, providers and consumers need compatible semantics between source and target systems. It is widely recognized that achieving this semantic integration is very costly. Nearly all the published research concerns how system integrators can discover and exploit semantic knowledge in order to better share data among the systems they already have. This research is very important, but to make the greatest impact, we must go beyond after-the-fact semantic integration among existing systems, to actively guiding semantic choices in new ontologies and systems — e.g., what concepts should be used as descriptive vocabularies for existing data, or as definitions for newly built systems. The goal is to ease data sharing for both new and old systems, to ensure that needed data is actually collected, and to maximize over time the business value of an enterprise's information systems.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/1041410.1041418</identifier>
		<title type="sharef:secondaryTitle">ACM SIGMOD Record</title>
		<number>4</number>
		<title type="sharef:primaryTitle">From Semantic Integration to Semantics Management: Case Studies and a Way Forward</title>
		<volume>33</volume>
	</reference>
	<reference name="mor01" src="bibtex:article" src-info="bibtex:line-6666" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Mirella M.</givenname>
				<surname>Moro</surname>
			</person>
			<person>
				<givenname>Vanessa</givenname>
				<surname>Braganholo</surname>
			</person>
			<person>
				<givenname>Carina F.</givenname>
				<surname>Dorneles</surname>
			</person>
			<person>
				<givenname>Denio</givenname>
				<surname>Duarte</surname>
			</person>
			<person>
				<givenname>Renata M.</givenname>
				<surname>Galante</surname>
			</person>
			<person>
				<givenname>Ronaldo S.</givenname>
				<surname>Mello</surname>
			</person>
		</names>
		<date value="2009-06"/>
		<abstract>
			<richtext>
				<p>XML has been explored by both research and industry communities. More than 5500 papers were published on different aspects of XML. With so many publications, it is hard for someone to decide where to start. Hence, this paper presents some of the research topics on XML, namely: XML on relational databases, query processing, views, data matching, and schema evolution. It then summarizes some (some!) of the most relevant or traditional papers on those subjects.</p>
			</richtext>
		</abstract>
		<title type="sharef:secondaryTitle">ACM SIGMOD Record</title>
		<number>2</number>
		<pages>29-34</pages>
		<title type="sharef:primaryTitle">XML: Some Papers in a Haystack</title>
		<field type="bibtex:topic">xml[0.9]</field>
		<identifier type="sharef:uri" resourceType="application/pdf">http://www.sigmod.org/publications/sigmod-record/0906/p29.surveys.Moro.pdf</identifier>
		<volume>38</volume>
	</reference>
	<reference name="mil01" src="bibtex:article" src-info="bibtex:line-6680" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>René J.</givenname>
				<surname>Miller</surname>
			</person>
			<person>
				<givenname>Mauricio A.</givenname>
				<surname>Hernández</surname>
			</person>
			<person>
				<givenname>Laura M.</givenname>
				<surname>Haas</surname>
			</person>
			<person>
				<givenname>Lingling</givenname>
				<surname>Yan</surname>
			</person>
			<person>
				<givenname>C. T. Howard</givenname>
				<surname>Ho</surname>
			</person>
			<person>
				<givenname>Ronald</givenname>
				<surname>Fagin</surname>
			</person>
			<person>
				<givenname>Lucian</givenname>
				<surname>Popa</surname>
			</person>
		</names>
		<date value="2001-03"/>
		<abstract>
			<richtext>
				<p>Clio is a system for managing and facilitating the complex tasks of heterogeneous data transformation and integration. In Clio, we have collected together a powerful set of data management techniques that have proven invaluable in tackling these difficult problems. In this paper, we present the underlying themes of our approach and present a brief case study.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/373626.373713</identifier>
		<title type="sharef:secondaryTitle">ACM SIGMOD Record</title>
		<number>1</number>
		<pages>78-83</pages>
		<title type="sharef:primaryTitle">The Clio Project: Managing Heterogeneity</title>
		<field type="bibtex:topic">clio[1]</field>
		<volume>30</volume>
	</reference>
	<reference name="pae00" src="bibtex:article" src-info="bibtex:line-6694" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Andreas</givenname>
				<surname>Paepcke</surname>
			</person>
			<person>
				<givenname>Hector</givenname>
				<surname>Garcia-Molina</surname>
			</person>
			<person>
				<givenname>Gerard</givenname>
				<surname>Rodríguez-Mulá</surname>
			</person>
			<person>
				<givenname>Junghoo</givenname>
				<surname>Cho</surname>
			</person>
		</names>
		<date value="2000-03"/>
		<identifier type="sharef:doi">10.1145/344788.344828</identifier>
		<title type="sharef:secondaryTitle">ACM SIGMOD Record</title>
		<number>1</number>
		<pages>80-92</pages>
		<title type="sharef:primaryTitle">Beyond Document Similarity: Understanding Value-Based Search and Browsing Technologies</title>
		<volume>29</volume>
	</reference>
	<reference name="nev02b" src="bibtex:article" src-info="bibtex:line-6706" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Frank</givenname>
				<surname>Neven</surname>
			</person>
		</names>
		<date value="2002-09"/>
		<identifier type="sharef:doi">10.1145/601858.601869</identifier>
		<title type="sharef:secondaryTitle">ACM SIGMOD Record</title>
		<number>3</number>
		<pages>39-46</pages>
		<title type="sharef:primaryTitle">Automata Theory for XML Researchers</title>
		<field type="bibtex:topic">xml[0.9]</field>
		<volume>31</volume>
	</reference>
	<reference name="bon00" src="bibtex:article" src-info="bibtex:line-6719" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Angela</givenname>
				<surname>Bonifati</surname>
			</person>
			<person>
				<givenname>Stefano</givenname>
				<surname>Ceri</surname>
			</person>
		</names>
		<date value="2000-03"/>
		<field type="bibtex:index">XML, LOREL, XML-QL, XML-GL, XQL, XSL</field>
		<title type="sharef:secondaryTitle">ACM SIGMOD Record</title>
		<number>1</number>
		<pages>68-79</pages>
		<title type="sharef:primaryTitle">Comparative Analysis of Five XML Query Languages</title>
		<volume>29</volume>
	</reference>
	<reference name="lee00" src="bibtex:article" src-info="bibtex:line-6731" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Dongwon</givenname>
				<surname>Lee</surname>
			</person>
			<person>
				<givenname>Wesley W.</givenname>
				<surname>Chu</surname>
			</person>
		</names>
		<date value="2000-09"/>
		<title type="sharef:secondaryTitle">ACM SIGMOD Record</title>
		<number>3</number>
		<pages>76-87</pages>
		<title type="sharef:primaryTitle">Comparative Analysis of Six XML Schema Languages</title>
		<field type="bibtex:topic">xmlschemalanguage[0.8] xml[0.6] dtd[0.8] xsd[0.8] xdr2[0.8] sox[0.8] schematron[0.8] dsd2[0.8]</field>
		<volume>29</volume>
	</reference>
	<reference name="was03" src="bibtex:article" src-info="bibtex:line-6747" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Klaus C.</givenname>
				<surname>Wassermann</surname>
			</person>
			<person>
				<givenname>Kynan</givenname>
				<surname>Eng</surname>
			</person>
			<person>
				<givenname>Paul F. M. J.</givenname>
				<surname>Verschure</surname>
			</person>
			<person>
				<givenname>Jônatas</givenname>
				<surname>Manzolli</surname>
			</person>
		</names>
		<date value="2003-10"/>
		<abstract>
			<richtext>
				<p>We conceived "Ada: Intelligent Space" exhibit as an artificial organism, integrating a large number of sensory modalities, and let it interact with visitors using a multitude of effector systems. Ada used a language of sound and light to communicate its moods, emotions, and behaviors. Here we describe the mechanisms behind Ada's sound communication, its real-time performance, and its interpretation by human subjects.</p>
			</richtext>
		</abstract>
		<title type="sharef:secondaryTitle">IEEE MultiMedia</title>
		<number>4</number>
		<pages>82-90</pages>
		<title type="sharef:primaryTitle">Live Soundscape Composition Based on Synthetic Emotions</title>
		<identifier type="sharef:uri" resourceType="application/pdf">http://www.ini.unizh.ch/~pfmjv/_download/ieee+mult+media_82.pdf</identifier>
		<identifier type="sharef:uri" resourceType="text/html">http://csdl.computer.org/comp/mags/mu/2003/04/u4082abs.htm</identifier>
		<volume>10</volume>
	</reference>
	<reference name="bea95" src="bibtex:article" src-info="bibtex:line-6761" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Peter</givenname>
				<surname>Beadle</surname>
			</person>
		</names>
		<date value="1995"/>
		<title type="sharef:secondaryTitle">IEEE MultiMedia</title>
		<number>2</number>
		<pages>30-40</pages>
		<title type="sharef:primaryTitle">Experiments in Multipoint Multimedia Telecommunication</title>
		<volume>2</volume>
	</reference>
	<reference name="fur94" src="bibtex:article" src-info="bibtex:line-6771" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Borko</givenname>
				<surname>Furht</surname>
			</person>
		</names>
		<date value="1994"/>
		<title type="sharef:secondaryTitle">IEEE MultiMedia</title>
		<number>1</number>
		<pages>47-59</pages>
		<title type="sharef:primaryTitle">Multimedia Systems: An Overview</title>
		<volume>1</volume>
	</reference>
	<reference name="bar04c" src="bibtex:article" src-info="bibtex:line-6785" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Richard G.</givenname>
				<surname>Baraniuk</surname>
			</person>
			<person>
				<givenname>C. Sidney</givenname>
				<surname>Burrus</surname>
			</person>
			<person>
				<givenname>Don H.</givenname>
				<surname>Johnson</surname>
			</person>
			<person>
				<givenname>Douglas L.</givenname>
				<surname>Jones</surname>
			</person>
		</names>
		<date value="2004"/>
		<abstract>
			<richtext>
				<p>There is a great need for information technologies for developing and delivering quality, up-to-date educational materials that convey to all learners that knowledge is a dynamic continuum that stretches across disciplines. To address this need, an experimental, open-source/open-content initiative, called the Connexions Project, was initiated. The Connexions Project offers an alternative to the way textbooks and other learning materials are created, maintained, and used. By design, Connexions greatly impacts current modes of teaching and learning, and the development and sharing of knowledge. In combination with powerful software tools which consist of an XML language, Connexions gives learner free access to educational materials that can be readily manipulated to suit their individual learning styles as they explore links among concepts. The free software tools also foster the development, manipulation, and continuous refinement of educational material by diverse communities of authors and instructor. An overview of the philosophy and progress of the project is presented, with a particular emphasis on its application to the area of signal processing.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1109/MSP.2004.1328080</identifier>
		<title type="sharef:secondaryTitle">IEEE Signal Processing Magazine</title>
		<number>5</number>
		<pages>10-16</pages>
		<title type="sharef:primaryTitle">Sharing Knowledge and Building Communities in Signal Processing</title>
		<identifier type="sharef:uri">http://ieeexplore.ieee.org/xpls/abs_all.jsp?arnumber=1328080</identifier>
		<volume>21</volume>
	</reference>
	<reference name="ang10" src="bibtex:article" src-info="bibtex:line-6802" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Dragomir</givenname>
				<surname>Anguelov</surname>
			</person>
			<person>
				<givenname>Carole</givenname>
				<surname>Dulong</surname>
			</person>
			<person>
				<givenname>Daniel</givenname>
				<surname>Filip</surname>
			</person>
			<person>
				<givenname>Christian</givenname>
				<surname>Frueh</surname>
			</person>
			<person>
				<givenname>Stéphane</givenname>
				<surname>Lafon</surname>
			</person>
			<person>
				<givenname>Richard</givenname>
				<surname>Lyon</surname>
			</person>
			<person>
				<givenname>Abhijit</givenname>
				<surname>Ogale</surname>
			</person>
			<person>
				<givenname>Luc</givenname>
				<surname>Vincent</surname>
			</person>
			<person>
				<givenname>Josh</givenname>
				<surname>Weaver</surname>
			</person>
		</names>
		<date value="2010-06"/>
		<abstract>
			<richtext>
				<p>Street View serves millions of Google users daily with panoramic imagery captured in hundreds of cities in 20 countries across four continents. A team of Google researchers describes the technical challenges involved in capturing, processing, and serving street-level imagery on a global scale.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1109/MC.2010.170</identifier>
		<title type="sharef:secondaryTitle">IEEE Computer</title>
		<number>6</number>
		<pages>32-38</pages>
		<title type="sharef:primaryTitle">Google Street View: Capturing the World at Street Level</title>
		<identifier type="sharef:uri" resourceType="text/html">http://research.google.com/pubs/pub36899.html</identifier>
		<volume>43</volume>
	</reference>
	<reference name="smi90" src="bibtex:article" src-info="bibtex:line-6816" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Alan Jay</givenname>
				<surname>Smith</surname>
			</person>
		</names>
		<date value="1990-04"/>
		<abstract>
			<richtext>
				<p>Computer researchers have a professional obligation to referee the work of others. This article tells you how to evaluate a paper and write a report using common standards and procedures. It focuses on research papers in applied areas of computer science and engineering, such as systems architecture, hardware, communications, and performance evaluation, but most of the discussion is generally applicable; separate sections consider research proposals and survey and tutorial papers.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1109/2.55470</identifier>
		<title type="sharef:secondaryTitle">IEEE Computer</title>
		<number>4</number>
		<pages>65-71</pages>
		<title type="sharef:primaryTitle">The Task of the Referee</title>
		<volume>23</volume>
	</reference>
	<reference name="tre08" src="bibtex:article" src-info="bibtex:line-6829" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Jonathan</givenname>
				<surname>Trevor</surname>
			</person>
		</names>
		<date value="2008-02"/>
		<abstract>
			<richtext>
				<p>Pipes lets both novice and expert developers grab Web data sources from multiple formats, manipulate that data, mash it up with other data sources or services using a visual editor, and host the results on its Web page. Once a Pipe is built, anyone can use its data output however they want, wherever they want. Mobile application development continues to be challenging given the enormous number of devices and capabilities. Services like Pipes enable developers to focus on one of the keystones of such applications: getting the right data. They also make list- and map-based visualizations easy to both build and consume. A current shortcoming of many mobile Pipes is the lack of an automatic way to provide user location.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1109/MC.2008.48</identifier>
		<title type="sharef:secondaryTitle">IEEE Computer</title>
		<number>2</number>
		<pages>104-106</pages>
		<title type="sharef:primaryTitle">Doing the Mobile Mash</title>
		<volume>41</volume>
	</reference>
	<reference name="spo07" src="bibtex:article" src-info="bibtex:line-6842" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Jim</givenname>
				<surname>Spohrer</surname>
			</person>
			<person>
				<givenname>Paul P.</givenname>
				<surname>Maglio</surname>
			</person>
			<person>
				<givenname>John</givenname>
				<surname>Bailey</surname>
			</person>
			<person>
				<givenname>Daniel</givenname>
				<surname>Gruhl</surname>
			</person>
		</names>
		<date value="2007-01"/>
		<abstract>
			<richtext>
				<p>The service sector accounts for most of the world's economic activity, but it's the least-studied part of the economy. A service system comprises people and technologies that adaptively compute and adjust to a system's changing value of knowledge. A science of service systems could provide theory and practice around service innovation.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1109/MC.2007.33</identifier>
		<title type="sharef:secondaryTitle">IEEE Computer</title>
		<number>1</number>
		<pages>71-77</pages>
		<title type="sharef:primaryTitle">Steps Toward a Science of Service Systems</title>
		<identifier type="sharef:uri" resourceType="application/pdf">http://ieeexplore.ieee.org/iel5/2/4069176/04069198.pdf</identifier>
		<volume>40</volume>
	</reference>
	<reference name="bro87" src="bibtex:article" src-info="bibtex:line-6856" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Frederick P.</givenname>
				<surname>Brooks</surname>
			</person>
		</names>
		<date value="1987-04"/>
		<identifier type="sharef:doi">10.1109/MC.1987.1663532</identifier>
		<title type="sharef:secondaryTitle">IEEE Computer</title>
		<number>4</number>
		<pages>10-19</pages>
		<title type="sharef:primaryTitle">No Silver Bullet: Essence and Accidents of Software Engineering</title>
		<identifier type="sharef:uri" resourceType="application/pdf">http://www.lips.utexas.edu/ee382c-15005/Readings/Readings1/05-Broo87.pdf</identifier>
		<volume>20</volume>
	</reference>
	<reference name="law01b" src="bibtex:article" src-info="bibtex:line-6869" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Steve</givenname>
				<surname>Lawrence</surname>
			</person>
			<person>
				<givenname>Frans</givenname>
				<surname>Coetzee</surname>
			</person>
			<person>
				<givenname>Eric</givenname>
				<surname>Glover</surname>
			</person>
			<person>
				<givenname>David M.</givenname>
				<surname>Pennock</surname>
			</person>
			<person>
				<givenname>Gary</givenname>
				<surname>Flake</surname>
			</person>
			<person>
				<givenname>Finn</givenname>
				<surname>Nielsen</surname>
			</person>
			<person>
				<givenname>Robert</givenname>
				<surname>Krovetz</surname>
			</person>
			<person>
				<givenname>Andries</givenname>
				<surname>Kruger</surname>
			</person>
			<person>
				<givenname>C. Lee</givenname>
				<surname>Giles</surname>
			</person>
		</names>
		<date value="2001"/>
		<title type="sharef:secondaryTitle">IEEE Computer</title>
		<number>2</number>
		<pages>26-31</pages>
		<title type="sharef:primaryTitle">Persistence of Web References in Scientific Research</title>
		<identifier type="sharef:uri" resourceType="application/pdf">http://www.neci.nec.com/~lawrence/papers/persistence-computer01/persistence-computer01.pdf</identifier>
		<volume>34</volume>
	</reference>
	<reference name="law99b" src="bibtex:article" src-info="bibtex:line-6880" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Steve</givenname>
				<surname>Lawrence</surname>
			</person>
			<person>
				<givenname>C. Lee</givenname>
				<surname>Giles</surname>
			</person>
			<person>
				<givenname>Kurt</givenname>
				<surname>Bollacker</surname>
			</person>
		</names>
		<date value="1999"/>
		<title type="sharef:secondaryTitle">IEEE Computer</title>
		<number>6</number>
		<pages>67-71</pages>
		<title type="sharef:primaryTitle">Digital Libraries and Autonomous Citation Indexing</title>
		<identifier type="sharef:uri" resourceType="application/pdf">http://www.neci.nec.com/~lawrence/papers/aci-computer99/aci-computer99.pdf</identifier>
		<volume>32</volume>
	</reference>
	<reference name="lia90" src="bibtex:article" src-info="bibtex:line-6891" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Luping</givenname>
				<surname>Liang</surname>
			</person>
			<person>
				<givenname>Samuel T.</givenname>
				<surname>Chanson</surname>
			</person>
			<person>
				<givenname>Gerald W.</givenname>
				<surname>Neufeld</surname>
			</person>
		</names>
		<date value="1990"/>
		<field type="bibtex:index">group communications, process groups</field>
		<title type="sharef:secondaryTitle">IEEE Computer</title>
		<number>2</number>
		<pages>56-66</pages>
		<title type="sharef:primaryTitle">Process Groups and Group Communications</title>
		<volume>23</volume>
	</reference>
	<reference name="wel84" src="bibtex:article" src-info="bibtex:line-6902" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Terry A.</givenname>
				<surname>Welch</surname>
			</person>
		</names>
		<date value="1984-06"/>
		<title type="sharef:secondaryTitle">IEEE Computer</title>
		<number>6</number>
		<pages>8-19</pages>
		<title type="sharef:primaryTitle">A Technique for High Performance Data Compression</title>
		<field type="bibtex:topic">lzw[1]</field>
		<volume>17</volume>
	</reference>
	<reference name="yan85" src="bibtex:article" src-info="bibtex:line-6914" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>N.</givenname>
				<surname>Yankelovich</surname>
			</person>
			<person>
				<givenname>N.</givenname>
				<surname>Meyrowitz</surname>
			</person>
			<person>
				<givenname>N. Van</givenname>
				<surname>Dam</surname>
			</person>
		</names>
		<date value="1985-10"/>
		<title type="sharef:secondaryTitle">IEEE Computer</title>
		<number>10</number>
		<pages>15-30</pages>
		<title type="sharef:primaryTitle">Reading and writing the electronic book</title>
		<volume>18</volume>
	</reference>
	<reference name="bur06b" src="bibtex:article" src-info="bibtex:line-6929" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>William E.</givenname>
				<surname>Burr</surname>
			</person>
		</names>
		<date value="2006"/>
		<abstract>
			<richtext>
				<p>Successful attacks against the two most commonly used cryptographic hash functions, MD5 and SHA-1, have triggered a kind of feeding frenzy in the cryptographic community. Many researchers are now working on hash function attacks, and we can expect new results in this area for the next several years. This article discusses the SHA-1 attack and the US National Institute of Standards and Technology's (NIST's) plans for SHA-1 and hash functions in general.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1109/MSP.2006.37</identifier>
		<title type="sharef:secondaryTitle">IEEE Security &amp; Privacy</title>
		<number>2</number>
		<pages>88-91</pages>
		<title type="sharef:primaryTitle">Cryptographic Hash Standards: Where Do We Go from Here?</title>
		<field type="bibtex:topic">md5[0.8] sha1[0.8]</field>
		<volume>4</volume>
	</reference>
	<reference name="ram95" src="bibtex:article" src-info="bibtex:line-6946" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>K. K.</givenname>
				<surname>Ramakrishnan</surname>
			</person>
			<person>
				<givenname>Peter</givenname>
				<surname>Newman</surname>
			</person>
		</names>
		<date value="1995"/>
		<field type="bibtex:index">ATM, flow control</field>
		<title type="sharef:secondaryTitle">IEEE Network</title>
		<number>2</number>
		<pages>49-56</pages>
		<title type="sharef:primaryTitle">Integration of Rate and Credit Schemes for ATM Flow Control</title>
		<volume>9</volume>
	</reference>
	<reference name="hei94" src="bibtex:article" src-info="bibtex:line-6957" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Geert J.</givenname>
				<surname>Heijenk</surname>
			</person>
			<person>
				<givenname>Xinli</givenname>
				<surname>Hou</surname>
			</person>
			<person>
				<givenname>Ignas G.</givenname>
				<surname>Niemegeers</surname>
			</person>
		</names>
		<date value="1994"/>
		<field type="bibtex:index">group management, CSCW, group communications</field>
		<title type="sharef:secondaryTitle">IEEE Network</title>
		<number>1</number>
		<pages>34-44</pages>
		<title type="sharef:primaryTitle">Communication Systems Supporting Multimedia Multi-user Applications</title>
		<volume>8</volume>
	</reference>
	<reference name="zha93" src="bibtex:article" src-info="bibtex:line-6968" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Lixia</givenname>
				<surname>Zhang</surname>
			</person>
			<person>
				<givenname>Stephen E.</givenname>
				<surname>Deering</surname>
			</person>
			<person>
				<givenname>Deborah</givenname>
				<surname>Estrin</surname>
			</person>
			<person>
				<givenname>Scott</givenname>
				<surname>Shenker</surname>
			</person>
			<person>
				<givenname>Daniel</givenname>
				<surname>Zappala</surname>
			</person>
		</names>
		<date value="1993"/>
		<title type="sharef:secondaryTitle">IEEE Network</title>
		<number>5</number>
		<pages>8-18</pages>
		<title type="sharef:primaryTitle">RSVP: A New Resource ReSerVation Protocol</title>
		<field type="bibtex:topic">rsvp[0.9]</field>
		<volume>7</volume>
	</reference>
	<reference name="kir93" src="bibtex:article" src-info="bibtex:line-6983" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Thomas</givenname>
				<surname>Kirsche</surname>
			</person>
			<person>
				<givenname>Richard</givenname>
				<surname>Lenz</surname>
			</person>
			<person>
				<givenname>Horst</givenname>
				<surname>Lührsen</surname>
			</person>
			<person>
				<givenname>Klaus</givenname>
				<surname>Meyer-Wegener</surname>
			</person>
			<person>
				<givenname>Hartmut</givenname>
				<surname>Wedekind</surname>
			</person>
			<person>
				<givenname>M.</givenname>
				<surname>Bever</surname>
			</person>
			<person>
				<givenname>Ulrich</givenname>
				<surname>Schäffer</surname>
			</person>
			<person>
				<givenname>C.</givenname>
				<surname>Schottmüller</surname>
			</person>
		</names>
		<date value="1993"/>
		<field type="bibtex:index">group communications, cooperative work, communication supportland, CoDraft, multicast</field>
		<title type="sharef:secondaryTitle">Computer Communications</title>
		<number>9</number>
		<pages>594-602</pages>
		<title type="sharef:primaryTitle">Communication support for cooperative work</title>
		<volume>16</volume>
	</reference>
	<reference name="kar94" src="bibtex:article" src-info="bibtex:line-6994" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Achim</givenname>
				<surname>Karduck</surname>
			</person>
		</names>
		<date value="1994"/>
		<field type="bibtex:index">CSCW, team formation, informarion services, hypermedia</field>
		<title type="sharef:secondaryTitle">Computer Communications</title>
		<number>11</number>
		<pages>777-787</pages>
		<title type="sharef:primaryTitle">TeamBuilder: a CSCW tool for identifying expertise and team formation</title>
		<volume>17</volume>
	</reference>
	<reference name="wea94" src="bibtex:article" src-info="bibtex:line-7005" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Alfred C.</givenname>
				<surname>Weaver</surname>
			</person>
		</names>
		<date value="1994"/>
		<field type="bibtex:index">XTP, protocols, distributed computing, distributed applications</field>
		<title type="sharef:secondaryTitle">Computer Communications</title>
		<number>1</number>
		<pages>46-52</pages>
		<title type="sharef:primaryTitle">The Xpress Transfer Protocol</title>
		<volume>17</volume>
	</reference>
	<reference name="mog01" src="bibtex:article" src-info="bibtex:line-7016" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Jeffrey C.</givenname>
				<surname>Mogul</surname>
			</person>
		</names>
		<date value="2001-02"/>
		<title type="sharef:secondaryTitle">Computer Communications</title>
		<number>2</number>
		<pages>155-162</pages>
		<title type="sharef:primaryTitle">Server-directed Transcoding</title>
		<field type="bibtex:topic">proxy[0.7] httpserver[0.7] http[0.7]</field>
		<volume>24</volume>
	</reference>
	<reference name="liu94" src="bibtex:article" src-info="bibtex:line-7028" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Yusheng</givenname>
				<surname>Liu</surname>
			</person>
			<person>
				<givenname>Doan B.</givenname>
				<surname>Hoang</surname>
			</person>
		</names>
		<date value="1994"/>
		<title type="sharef:secondaryTitle">Computer Communications</title>
		<number>1</number>
		<pages>53-66</pages>
		<title type="sharef:primaryTitle">OSI RPC model and protocol</title>
		<field type="bibtex:topic">isorpc[0.9] osi[0.8]</field>
		<volume>17</volume>
	</reference>
	<reference name="wil94" src="bibtex:article" src-info="bibtex:line-7039" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Neil</givenname>
				<surname>Williams</surname>
			</person>
			<person>
				<givenname>Gordon S.</givenname>
				<surname>Blair</surname>
			</person>
		</names>
		<date value="1994"/>
		<field type="bibtex:index">multimedia, distributed computing</field>
		<title type="sharef:secondaryTitle">Computer Communications</title>
		<number>2</number>
		<pages>119-132</pages>
		<title type="sharef:primaryTitle">Distributed multimedia applications: A review</title>
		<volume>17</volume>
	</reference>
	<reference name="san94" src="bibtex:article" src-info="bibtex:line-7050" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Adelino</givenname>
				<surname>Santos</surname>
			</person>
			<person>
				<givenname>B.</givenname>
				<surname>Tritsch</surname>
			</person>
		</names>
		<date value="1994"/>
		<field type="bibtex:index">CoMEdiA, cooperative editing multi-user interfaces, multimedia, communication, collaborative editing</field>
		<title type="sharef:secondaryTitle">Computer Communications</title>
		<number>4</number>
		<pages>277-287</pages>
		<title type="sharef:primaryTitle">Cooperative multimedia editing tool for enhanced group communication</title>
		<volume>17</volume>
	</reference>
	<reference name="rob94" src="bibtex:article" src-info="bibtex:line-7061" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>John A.</givenname>
				<surname>Robinson</surname>
			</person>
		</names>
		<date value="1994"/>
		<field type="bibtex:index">CSCW, communications services architecture, prototype programs</field>
		<title type="sharef:secondaryTitle">Computer Communications</title>
		<number>5</number>
		<pages>339-347</pages>
		<title type="sharef:primaryTitle">Communications services architecture for CSCW</title>
		<volume>17</volume>
	</reference>
	<reference name="hen92" src="bibtex:article" src-info="bibtex:line-7072" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Pippa</givenname>
				<surname>Hennessy</surname>
			</person>
			<person>
				<givenname>Thomas</givenname>
				<surname>Kreifelts</surname>
			</person>
			<person>
				<givenname>Ute</givenname>
				<surname>Ehrlich</surname>
			</person>
		</names>
		<date value="1992"/>
		<field type="bibtex:index">distributed work management, cooperative work, activity coordination</field>
		<title type="sharef:secondaryTitle">Computer Communications</title>
		<number>8</number>
		<pages>477-488</pages>
		<title type="sharef:primaryTitle">Distributed Work Management: Activity Coordination within the EuroCoOp Project</title>
		<volume>15</volume>
	</reference>
	<reference name="ben92" src="bibtex:article" src-info="bibtex:line-7083" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Steven</givenname>
				<surname>Benford</surname>
			</person>
			<person>
				<givenname>Hugh</givenname>
				<surname>Smith</surname>
			</person>
			<person>
				<givenname>Alan</givenname>
				<surname>Shepherd</surname>
			</person>
			<person>
				<givenname>Adrian</givenname>
				<surname>Bullock</surname>
			</person>
			<person>
				<givenname>Howidy</givenname>
				<surname>Howidy</surname>
			</person>
		</names>
		<date value="1992"/>
		<field type="bibtex:index">CSCW, communication, object-orientation</field>
		<title type="sharef:secondaryTitle">Computer Communications</title>
		<number>8</number>
		<pages>502-508</pages>
		<title type="sharef:primaryTitle">Information sharing approach to CSCW: the Grace project</title>
		<volume>15</volume>
	</reference>
	<reference name="rod92b" src="bibtex:article" src-info="bibtex:line-7094" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Tom A.</givenname>
				<surname>Rodden</surname>
			</person>
			<person>
				<givenname>Gordon S.</givenname>
				<surname>Blair</surname>
			</person>
		</names>
		<date value="1992"/>
		<field type="bibtex:index">CSCW, distributed computer cooperation, transparency</field>
		<title type="sharef:secondaryTitle">Computer Communications</title>
		<number>8</number>
		<pages>527-538</pages>
		<title type="sharef:primaryTitle">Distributed systems support for computer supported cooperative work</title>
		<volume>15</volume>
	</reference>
	<reference name="nav93" src="bibtex:article" src-info="bibtex:line-7105" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Leandro</givenname>
				<surname>Navarro</surname>
			</person>
			<person>
				<givenname>Wolfgang</givenname>
				<surname>Prinz</surname>
			</person>
			<person>
				<givenname>Tom A.</givenname>
				<surname>Rodden</surname>
			</person>
		</names>
		<date value="1993"/>
		<field type="bibtex:index">CSCW, ODP, MOCCA, distributed cooperative applications</field>
		<title type="sharef:secondaryTitle">Computer Communications</title>
		<number>5</number>
		<pages>288-297</pages>
		<title type="sharef:primaryTitle">CSCW requires open systems</title>
		<volume>16</volume>
	</reference>
	<reference name="pal93" src="bibtex:article" src-info="bibtex:line-7116" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Jacob</givenname>
				<surname>Palme</surname>
			</person>
		</names>
		<date value="1993"/>
		<field type="bibtex:index">group communications, standards, computer conferencing</field>
		<title type="sharef:secondaryTitle">Computer Communications</title>
		<number>9</number>
		<pages>532-538</pages>
		<title type="sharef:primaryTitle">Standards for asynchronous group communication</title>
		<volume>16</volume>
	</reference>
	<reference name="hei93" src="bibtex:article" src-info="bibtex:line-7127" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Bernd</givenname>
				<surname>Heinrichs</surname>
			</person>
			<person>
				<givenname>Kai</givenname>
				<surname>Jakobs</surname>
			</person>
			<person>
				<givenname>Alessandro</givenname>
				<surname>Carone</surname>
			</person>
		</names>
		<date value="1993"/>
		<field type="bibtex:index">group communications, multimedia, QoS, XTP</field>
		<title type="sharef:secondaryTitle">Computer Communications</title>
		<number>9</number>
		<pages>539-547</pages>
		<title type="sharef:primaryTitle">High performance transfer services to support multimedia group communications</title>
		<volume>16</volume>
	</reference>
	<reference name="dia93" src="bibtex:article" src-info="bibtex:line-7138" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Michel</givenname>
				<surname>Diaz</surname>
			</person>
			<person>
				<givenname>Thierry</givenname>
				<surname>Villemur</surname>
			</person>
		</names>
		<date value="1993"/>
		<field type="bibtex:index">cooperative groups, cooperative work, votes, quorums, Estelle, membership algorithm</field>
		<title type="sharef:secondaryTitle">Computer Communications</title>
		<number>9</number>
		<pages>548-556</pages>
		<title type="sharef:primaryTitle">Membership services and protocols for cooperative frameworks of processes</title>
		<volume>16</volume>
	</reference>
	<reference name="mam91" src="bibtex:article" src-info="bibtex:line-7153" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Sandra A.</givenname>
				<surname>Mamrak</surname>
			</person>
			<person>
				<givenname>J. A.</givenname>
				<surname>Barnes</surname>
			</person>
		</names>
		<date value="1991-03"/>
		<abstract>
			<richtext>
				<p>The Standard Generalized Markup Language, SGML, is being adopted by various international organizations as the medium for exchange of electronically encoded documents. An exchange is accomplished by way of a Document Type Definition, DTD, that describes the content of documents targeted for an exchange. In this paper we suggest considerations for the designers of SGML DTDs. The considerations emphasize uniformity and simplicity without sacrificing expressive power. The considerations are not comprehensive: they address minimization features, attributes, inclusion and exclusion exceptions, and the CONCUR feature of SGML.</p>
			</richtext>
		</abstract>
		<title type="sharef:secondaryTitle">Electronic Publishing</title>
		<number>1</number>
		<pages>27-42</pages>
		<title type="sharef:primaryTitle">Considerations for the preparation of SGML document type definitions</title>
		<field type="bibtex:topic">sgml[0.7] dtd[0.7]</field>
		<identifier type="sharef:uri" resourceType="application/pdf">http://cajun.cs.nott.ac.uk/compsci/epo/papers/volume4/issue1/ep038sm.pdf</identifier>
		<volume>4</volume>
	</reference>
	<reference name="lub94" src="bibtex:article" src-info="bibtex:line-7171" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Hannes P.</givenname>
				<surname>Lubich</surname>
			</person>
			<person>
				<givenname>Bernhard</givenname>
				<surname>Plattner</surname>
			</person>
		</names>
		<date value="1994"/>
		<field type="bibtex:index">MultimETH</field>
		<title type="sharef:secondaryTitle">Collaborative Computing</title>
		<number>2</number>
		<pages>147-162</pages>
		<title type="sharef:primaryTitle">The MultimETH conferencing and joint editing system</title>
		<volume>1</volume>
	</reference>
	<reference name="wil97a" src="bibtex:article" src-info="bibtex:line-7186" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Erik</givenname>
				<surname>Wilde</surname>
			</person>
			<person>
				<givenname>Bernhard</givenname>
				<surname>Plattner</surname>
			</person>
		</names>
		<date value="1997"/>
		<abstract>
			<richtext>
				<p>With more and more computers gradually changing from isolated, personal tools to networked workstations, group communications is an area of research which has received much attention recently. This paper focuses on a model and the architecture of a system which supports group communications by providing group and session management functionality. The system architecture is related to DNS or X.500, however avoids their complexity by focusing on group and session management and adding functionality where necessary. New functionality is needed for the dynamics of group communications (members of a connection may change over the lifetime of the connection) and increased complexity of relations which may be established between objects. A model is described which defines six object types which represent the relevant objects. Users and groups represent real world users and their relations. Sessions and flows describe ongoing group communications. Flow templates and certificates provide mechanisms for management and security issues. The architecture presented in this paper can be used for group and session management support within different group communications platforms. A description of the implementation as well as implementation results are given in the last section.</p>
			</richtext>
		</abstract>
		<field type="bibtex:index">GMS, GSA, GUA, GAP, GSP</field>
		<title type="sharef:secondaryTitle">European Transactions on Telecommunications</title>
		<number>4</number>
		<pages>409-421</pages>
		<title type="sharef:primaryTitle">Transport-Independent Group and Session Management for Group Communication Platforms</title>
		<identifier type="sharef:uri">http://dret.net/netdret/publications#wil97a</identifier>
		<volume>8</volume>
	</reference>
	<reference name="vog93" src="bibtex:inproceedings" src-info="bibtex:line-7205" type="sharef:inproceedings" crossref="itg93">
		<names type="sharef:author">
			<person>
				<givenname>Martin</givenname>
				<surname>Vogt</surname>
			</person>
			<person>
				<givenname>Thomas</givenname>
				<surname>Plagemann</surname>
			</person>
			<person>
				<givenname>Bernhard</givenname>
				<surname>Plattner</surname>
			</person>
			<person>
				<givenname>Thomas</givenname>
				<surname>Walter</surname>
			</person>
		</names>
		<field type="bibtex:index">Da CaPo</field>
		<pages>3-17</pages>
		<title type="sharef:primaryTitle">Eine Laufzeitumgebung für Da CaPo</title>
	</reference>
	<reference name="oec93" src="bibtex:inproceedings" src-info="bibtex:line-7213" type="sharef:inproceedings" crossref="itg93">
		<names type="sharef:author">
			<person>
				<givenname>Rainer</givenname>
				<surname>Oechsle</surname>
			</person>
			<person>
				<givenname>Marcel</givenname>
				<surname>Graf</surname>
			</person>
		</names>
		<field type="bibtex:index">ATM, ST-II</field>
		<pages>76-89</pages>
		<title type="sharef:primaryTitle">ST-II über private ATM-Netze</title>
	</reference>
	<reference name="gut93" src="bibtex:inproceedings" src-info="bibtex:line-7221" type="sharef:inproceedings" crossref="itg93">
		<names type="sharef:author">
			<person>
				<givenname>Thomas</givenname>
				<surname>Gutekunst</surname>
			</person>
			<person>
				<givenname>Thomas</givenname>
				<surname>Schmidt</surname>
			</person>
			<person>
				<givenname>Günter</givenname>
				<surname>Schulze</surname>
			</person>
			<person>
				<givenname>Jean</givenname>
				<surname>Schweitzer</surname>
			</person>
			<person>
				<givenname>Michael</givenname>
				<surname>Weber</surname>
			</person>
		</names>
		<field type="bibtex:index">JVTOS, CIO, CSCW</field>
		<pages>145-159</pages>
		<title type="sharef:primaryTitle">A Distributed Multimedia Joint Viewing and Tele-Operation Service for Heterogeneous Workstation Environments</title>
	</reference>
	<reference name="kir93b" src="bibtex:inproceedings" src-info="bibtex:line-7229" type="sharef:inproceedings" crossref="itg93">
		<names type="sharef:author">
			<person>
				<givenname>Thomas</givenname>
				<surname>Kirsche</surname>
			</person>
			<person>
				<givenname>Richard</givenname>
				<surname>Lenz</surname>
			</person>
			<person>
				<givenname>Horst</givenname>
				<surname>Lührsen</surname>
			</person>
			<person>
				<givenname>Klaus</givenname>
				<surname>Meyer-Wegener</surname>
			</person>
			<person>
				<givenname>Hartmut</givenname>
				<surname>Wedekind</surname>
			</person>
		</names>
		<field type="bibtex:index">group communications, cooperative work, communication supportland, CoDraft, multicast</field>
		<pages>160-173</pages>
		<title type="sharef:primaryTitle">CoDraft: Eine verteilte Architektur zur Unterstützung von Gruppenarbeit durch Multimediale Objekte</title>
	</reference>
	<reference name="sem93" src="bibtex:inproceedings" src-info="bibtex:line-7237" type="sharef:inproceedings" crossref="itg93">
		<names type="sharef:author">
			<person>
				<givenname>Frank</givenname>
				<surname>Sembach</surname>
			</person>
			<person>
				<givenname>Kurt</givenname>
				<surname>Rothermel</surname>
			</person>
		</names>
		<field type="bibtex:index">TEATIME, CSCW</field>
		<pages>174-188</pages>
		<title type="sharef:primaryTitle">TEATIME: Gemeinsamer Arbeitsbereich für kooperativ bearbeitete multimediale Objekte</title>
	</reference>
	<reference name="itg93" src="bibtex:proceedings" src-info="bibtex:line-7245" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>Wolfgang</givenname>
				<surname>Effelsberg</surname>
			</person>
			<person>
				<givenname>Kurt</givenname>
				<surname>Rothermel</surname>
			</person>
		</names>
		<date value="1993-02"/>
		<address type="sharef:placePublished">Stuttgart, Germany</address>
		<field type="bibtex:index">GI/ITG</field>
		<identifier type="sharef:isbn">3598224079</identifier>
		<number>5</number>
		<publisher>K. G. Saur</publisher>
		<title type="sharef:seriesTitle">Praxis, Information und Kommunikation</title>
		<title type="sharef:primaryTitle">GI/ITG Arbeitstreffen Verteilte Multimedia-Systeme</title>
	</reference>
	<reference name="cla02" src="bibtex:inproceedings" src-info="bibtex:line-7263" type="sharef:inproceedings" crossref="sigcomm2002">
		<names type="sharef:author">
			<person>
				<givenname>David D.</givenname>
				<surname>Clark</surname>
			</person>
			<person>
				<givenname>John</givenname>
				<surname>Wroclawski</surname>
			</person>
			<person>
				<givenname>Karen R.</givenname>
				<surname>Sollins</surname>
			</person>
			<person>
				<givenname>Robert</givenname>
				<surname>Braden</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>The architecture of the Internet is based on a number of principles, including the self-describing datagram packet, the end to end arguments, diversity in technology and global addressing. As the Internet has moved from a research curiosity to a recognized component of mainstream society, new requirements have emerged that suggest new design principles, and perhaps suggest that we revisit some old ones. This paper explores one important reality that surrounds the Internet today: different stakeholders that are part of the Internet milieu have interests that may be adverse to each other, and these parties each vie to favor their particular interests. We call this process "the tussle". Our position is that accommodating this tussle is crucial to the evolution of the network's technical architecture. We discuss some examples of tussle, and offer some technical design principles that take it into account.</p>
			</richtext>
		</abstract>
		<pages>347-356</pages>
		<title type="sharef:primaryTitle">Tussle in Cyberspace: Defining Tomorrow's Internet</title>
	</reference>
	<reference name="sigcomm2002" src="bibtex:proceedings" src-info="bibtex:line-7271" type="sharef:proceedings">
		<date value="2002-08"/>
		<address type="sharef:placePublished">Pittsburgh, Pennsylvania</address>
		<identifier type="sharef:isbn">1-58113-570-X</identifier>
		<publisher>ACM Press</publisher>
		<title type="sharef:primaryTitle">ACM SIGCOMM 2002 Conference on Applications, Technologies, Architectures, and Protocols for Computer Communication</title>
		<identifier type="sharef:uri" resourceType="text/html">http://dblp.uni-trier.de/db/conf/sigcomm/sigcomm2002.html</identifier>
	</reference>
	<reference name="don04" src="bibtex:inproceedings" src-info="bibtex:line-7286" type="sharef:inproceedings" crossref="vldb04">
		<names type="sharef:author">
			<person>
				<givenname>Xin</givenname>
				<surname>Dong</surname>
			</person>
			<person>
				<givenname>Alon Y.</givenname>
				<surname>Halevy</surname>
			</person>
			<person>
				<givenname>Jayant</givenname>
				<surname>Madhavan</surname>
			</person>
			<person>
				<givenname>Ema</givenname>
				<surname>Nemes</surname>
			</person>
			<person>
				<givenname>Jun</givenname>
				<surname>Zhang</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Web services are loosely coupled software components, published, located, and invoked across the web. The growing number of web services available within an organization and on the Web raises a new and challenging search problem: locating desired web services. Traditional keyword search is insufficient in this context: the specific types of queries users require are not captured, the very small text fragments in web services are unsuitable for keyword search, and the underlying structure and semantics of the web services are not exploited. We describe the algorithms underlying the Woogle search engine for web services. Woogle supports similarity search for web services, such as finding similar web-service operations and finding operations that compose with a given one. We describe novel techniques to support these types of searches, and an experimental study on a collection of over 1500 web-service operations that shows the high recall and precision of our algorithms.</p>
			</richtext>
		</abstract>
		<pages>372-383</pages>
		<title type="sharef:primaryTitle">Similarity Search for Web Services</title>
		<identifier type="sharef:uri" resourceType="application/pdf">http://www.vldb.org/conf/2004/RS10P1.PDF</identifier>
	</reference>
	<reference name="vldb04" src="bibtex:proceedings" src-info="bibtex:line-7295" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>Mario A.</givenname>
				<surname>Nascimento</surname>
			</person>
			<person>
				<givenname>M. Tamer</givenname>
				<surname>Özsu</surname>
			</person>
			<person>
				<givenname>Donald</givenname>
				<surname>Kossmann</surname>
			</person>
			<person>
				<givenname>Renée J.</givenname>
				<surname>Miller</surname>
			</person>
			<person>
				<givenname>José A.</givenname>
				<surname>Blakeley</surname>
			</person>
			<person>
				<givenname>K. Bernhard</givenname>
				<surname>Schiefer</surname>
			</person>
		</names>
		<date value="2004-09"/>
		<address type="sharef:placePublished">Toronto, Canada</address>
		<field type="bibtex:index">VLDB 2004</field>
		<identifier type="sharef:isbn">0-12-088469-0</identifier>
		<publisher>ACM Press</publisher>
		<title type="sharef:primaryTitle">30th International Conference on Very Large Data Bases</title>
		<identifier type="sharef:uri" resourceType="text/html">http://www.informatik.uni-trier.de/~ley/db/conf/vldb/vldb2004.html</identifier>
	</reference>
	<reference name="jhi06" src="bibtex:inproceedings" src-info="bibtex:line-7312" type="sharef:inproceedings" crossref="vldb06">
		<names type="sharef:author">
			<person>
				<givenname>Anant</givenname>
				<surname>Jhingran</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>There is a fundamental transformation that is taking place on the web around information composition through mashups. We first describe this transformation and then assert that this will also affect enterprise architectures. Currently the state-of-the-art in enterprises around information composition is federation and other integration technologies. These scale well, and are well worth the upfront investment for enterprise class, long-lived applications. However, there are many information composition tasks that are not currently well served by these architectures. The needs of Situational Applications (i.e. applications that come together for solving some immediate business problems) are one such set of tasks. Augmenting structured data with unstructured information is another such task. Our hypothesis is that a new class of integration technologies will emerge to serve these tasks, and we call it an enterprise information mashup fabric. In the talk, we discuss the information management primitives that are needed for this fabric, the various options that exist for implementation, and pose several, currently unanswered, research questions.</p>
			</richtext>
		</abstract>
		<pages>3-4</pages>
		<title type="sharef:primaryTitle">Enterprise Information Mashups: Integrating Information, Simply</title>
		<identifier type="sharef:uri" resourceType="application/pdf">http://www.vldb.org/conf/2006/p3-jhingran.pdf</identifier>
	</reference>
	<reference name="vldb06" src="bibtex:proceedings" src-info="bibtex:line-7321" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>Umeshwar</givenname>
				<surname>Dayal</surname>
			</person>
			<person>
				<givenname>Kyu-Young</givenname>
				<surname>Whang</surname>
			</person>
			<person>
				<givenname>David B.</givenname>
				<surname>Lomet</surname>
			</person>
			<person>
				<givenname>Gustavo</givenname>
				<surname>Alonso</surname>
			</person>
			<person>
				<givenname>Guy M.</givenname>
				<surname>Lohman</surname>
			</person>
			<person>
				<givenname>Martin L.</givenname>
				<surname>Kersten</surname>
			</person>
			<person>
				<givenname>Sang Kyun</givenname>
				<surname>Cha</surname>
			</person>
			<person>
				<givenname>Young-Kuk</givenname>
				<surname>Kim</surname>
			</person>
		</names>
		<date value="2006-09"/>
		<address type="sharef:placePublished">Seoul, Korea</address>
		<field type="bibtex:index">VLDB 2006</field>
		<identifier type="sharef:isbn">1-59593-385-9</identifier>
		<publisher>ACM Press</publisher>
		<title type="sharef:primaryTitle">32nd International Conference on Very Large Data Bases</title>
		<identifier type="sharef:uri" resourceType="text/html">http://www.informatik.uni-trier.de/~ley/db/conf/vldb/vldb2006.html</identifier>
	</reference>
	<reference name="sto07" src="bibtex:inproceedings" src-info="bibtex:line-7338" type="sharef:inproceedings" crossref="vldb07">
		<names type="sharef:author">
			<person>
				<givenname>Michael</givenname>
				<surname>Stonebraker</surname>
			</person>
			<person>
				<givenname>Samuel</givenname>
				<surname>Madden</surname>
			</person>
			<person>
				<givenname>Daniel J.</givenname>
				<surname>Abadi</surname>
			</person>
			<person>
				<givenname>Stavros</givenname>
				<surname>Harizopoulos</surname>
			</person>
			<person>
				<givenname>Nabil</givenname>
				<surname>Hachem</surname>
			</person>
			<person>
				<givenname>Pat</givenname>
				<surname>Helland</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>In previous papers, some of us predicted the end of "one size fits all" as a commercial relational DBMS paradigm. These papers presented reasons and experimental evidence that showed that the major RDBMS vendors can be outperformed by 1-2 orders of magnitude by specialized engines in the data warehouse, stream processing, text, and scientific database markets. Assuming that specialized engines dominate these markets over time, the current relational DBMS code lines will be left with the business data processing (OLTP) market and hybrid markets where more than one kind of capability is required. In this paper we show that current RDBMSs can be beaten by nearly two orders of magnitude in the OLTP market as well. The experimental evidence comes from comparing a new OLTP prototype, H-Store, which we have built at M.I.T. to a popular RDBMS on the standard transactional benchmark, TPC-C. We conclude that the current RDBMS code lines, while attempting to be a "one size fits all" solution, in fact, excel at nothing. Hence, they are 25 year old legacy code lines that should be retired in favor of a collection of "from scratch" specialized engines. The DBMS vendors (and the research community) should start with a clean sheet of paper and design systems for tomorrow's requirements, not continue to push code lines and architectures designed for yesterday's needs.</p>
			</richtext>
		</abstract>
		<pages>1150-1160</pages>
		<title type="sharef:primaryTitle">The End of an Architectural Era (It's Time for a Complete Rewrite)</title>
		<identifier type="sharef:uri" resourceType="application/pdf">http://www.vldb.org/conf/2007/papers/industrial/p1150-stonebraker.pdf</identifier>
	</reference>
	<reference name="bot07" src="bibtex:inproceedings" src-info="bibtex:line-7347" type="sharef:inproceedings" crossref="vldb07">
		<names type="sharef:author">
			<person>
				<givenname>Irina</givenname>
				<surname>Botan</surname>
			</person>
			<person>
				<givenname>Donald</givenname>
				<surname>Kossmann</surname>
			</person>
			<person>
				<givenname>Peter M.</givenname>
				<surname>Fischer</surname>
			</person>
			<person>
				<givenname>Tim</givenname>
				<surname>Kraska</surname>
			</person>
			<person>
				<givenname>Dana</givenname>
				<surname>Florescu</surname>
			</person>
			<person>
				<givenname>Rokas</givenname>
				<surname>Tamosevicius</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>This paper presents two extensions for XQuery. The first extension allows the definition and processing of different kinds of windows over an input sequence; i.e., tumbling, sliding, and landmark windows. The second extension extends the XQuery data model (XDM) to support infinite sequences. This extension makes it possible to use XQuery as a language for continuous queries. Both extensions have been integrated into a Java-based open source XQuery engine. This paper gives details of this implementation and presents the results of running the Linear Road benchmark on the extended XQuery engine.</p>
			</richtext>
		</abstract>
		<pages>75-86</pages>
		<title type="sharef:primaryTitle">Extending XQuery with Window Functions</title>
		<identifier type="sharef:uri" resourceType="application/pdf">http://www.vldb.org/conf/2007/papers/research/p75-botan.pdf</identifier>
	</reference>
	<reference name="bex07" src="bibtex:inproceedings" src-info="bibtex:line-7356" type="sharef:inproceedings" crossref="vldb07">
		<names type="sharef:author">
			<person>
				<givenname>Geert Jan</givenname>
				<surname>Bex</surname>
			</person>
			<person>
				<givenname>Frank</givenname>
				<surname>Neven</surname>
			</person>
			<person>
				<givenname>Stijn</givenname>
				<surname>Vansummeren</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Although the presence of a schema enables many optimizations for operations on XML documents, recent studies have shown that many XML documents in practice either do not refer to a schema, or refer to a syntactically incorrect one. It is therefore of utmost importance to provide tools and techniques that can automatically generate schemas from sets of sample documents. While previous work in this area has mostly focused on the inference of Document Type Definitions (DTDs for short), we will consider the inference of XML Schema Definitions (XSDs for short) — the increasingly popular schema formalism that is turning DTDs obsolete. In contrast to DTDs where the content model of an element depends only on the element's name, the content model in an XSD can also depend on the context in which the element is used. Hence, while the inference of DTDs basically reduces to the inference of regular expressions from sets of sample strings, the inference of XSDs also entails identifying from a corpus of sample documents the contexts in which elements bear different content models. Since a seminal result by Gold implies that no inference algorithm can learn the complete class of XSDs from positive examples only, we focus on a class of XSDs that captures most XSDs occurring in practice. For this class, we provide a theoretically complete algorithm that always infers the correct XSD when a sufficiently large corpus of XML documents is available. In addition, we present a variant of this algorithm that works well on real-world (and therefore incomplete) data sets.</p>
			</richtext>
		</abstract>
		<pages>998-1009</pages>
		<title type="sharef:primaryTitle">Inferring XML Schema Definitions from XML Data</title>
		<field type="bibtex:topic">xsd[0.9]</field>
		<identifier type="sharef:uri" resourceType="application/pdf">http://www.vldb.org/conf/2007/papers/research/p998-bex.pdf</identifier>
	</reference>
	<reference name="vldb07" src="bibtex:proceedings" src-info="bibtex:line-7366" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>Christoph</givenname>
				<surname>Koch</surname>
			</person>
			<person>
				<givenname>Johannes</givenname>
				<surname>Gehrke</surname>
			</person>
			<person>
				<givenname>Minos N.</givenname>
				<surname>Garofalakis</surname>
			</person>
			<person>
				<givenname>Divesh</givenname>
				<surname>Srivastava</surname>
			</person>
			<person>
				<givenname>Karl</givenname>
				<surname>Aberer</surname>
			</person>
			<person>
				<givenname>Anand</givenname>
				<surname>Deshpande</surname>
			</person>
			<person>
				<givenname>Daniela</givenname>
				<surname>Florescu</surname>
			</person>
			<person>
				<givenname>Chee Yong</givenname>
				<surname>Chan</surname>
			</person>
			<person>
				<givenname>Venkatesh</givenname>
				<surname>Ganti</surname>
			</person>
			<person>
				<givenname>Carl-Christian</givenname>
				<surname>Kanne</surname>
			</person>
			<person>
				<givenname>Wolfgang</givenname>
				<surname>Klas</surname>
			</person>
			<person>
				<givenname>Erich J.</givenname>
				<surname>Neuhold</surname>
			</person>
		</names>
		<date value="2007-09"/>
		<address type="sharef:placePublished">Vienna, Austria</address>
		<field type="bibtex:index">VLDB 2007</field>
		<identifier type="sharef:isbn">978-1-59593-649-3</identifier>
		<publisher>ACM Press</publisher>
		<title type="sharef:primaryTitle">33rd International Conference on Very Large Data Bases</title>
		<identifier type="sharef:uri">http://www.vldb2007.org/</identifier>
		<identifier type="sharef:uri" resourceType="text/html">http://www.informatik.uni-trier.de/~ley/db/conf/vldb/vldb2007.html</identifier>
	</reference>
	<reference name="mad08" src="bibtex:inproceedings" src-info="bibtex:line-7384" type="sharef:inproceedings" crossref="vldb08">
		<names type="sharef:author">
			<person>
				<givenname>Jayant</givenname>
				<surname>Madhavan</surname>
			</person>
			<person>
				<givenname>David</givenname>
				<surname>Ko</surname>
			</person>
			<person>
				<givenname>Łucja</givenname>
				<surname>Kot</surname>
			</person>
			<person>
				<givenname>Vignesh</givenname>
				<surname>Ganapathy</surname>
			</person>
			<person>
				<givenname>Alex</givenname>
				<surname>Rasmussen</surname>
			</person>
			<person>
				<givenname>Alon</givenname>
				<surname>Halevy</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>The Deep Web, i.e., content hidden behind HTML forms, has long been acknowledged as a significant gap in search engine coverage. Since it represents a large portion of the structured data on the Web, accessing Deep-Web content has been a long-standing challenge for the database community. This paper describes a system for surfacing Deep-Web content, i.e., pre-computing submissions for each HTML form and adding the resulting HTML pages into a search engine index. The results of our surfacing have been incorporated into the Google search engine and today drive more than a thousand queries per second to Deep-Web content. Surfacing the Deep Web poses several challenges. First, our goal is to index the content behind many millions of HTML forms that span many languages and hundreds of domains. This necessitates an approach that is completely automatic, highly scalable, and very efficient. Second, a large number of forms have text inputs and require valid inputs values to be submitted. We present an algorithm for selecting input values for text search inputs that accept keywords and an algorithm for identifying inputs which accept only values of a specific type. Third, HTML forms often have more than one input and hence a naive strategy of enumerating the entire Cartesian product of all possible inputs can result in a very large number of URLs being generated. We present an algorithm that efficiently navigates the search space of possible input combinations to identify only those that generate URLs suitable for inclusion into our web search index. We present an extensive experimental evaluation validating the effectiveness of our algorithms.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/1454159.1454163</identifier>
		<pages>1241-1252</pages>
		<title type="sharef:primaryTitle">Google's Deep Web Crawl</title>
	</reference>
	<reference name="vldb08" src="bibtex:proceedings" src-info="bibtex:line-7393" type="sharef:proceedings">
		<date value="2008-08"/>
		<address type="sharef:placePublished">Auckland, New Zealand</address>
		<field type="bibtex:index">VLDB 2008</field>
		<publisher>ACM Press</publisher>
		<title type="sharef:primaryTitle">34th International Conference on Very Large Data Bases</title>
		<identifier type="sharef:uri" resourceType="text/html">http://dblp.uni-trier.de/db/journals/pvldb/pvldb1.html</identifier>
	</reference>
	<reference name="pre09" src="bibtex:inproceedings" src-info="bibtex:line-7408" type="sharef:inproceedings" crossref="vldb09">
		<names type="sharef:author">
			<person>
				<givenname>Nicoleta</givenname>
				<surname>Preda</surname>
			</person>
			<person>
				<givenname>Fabian M.</givenname>
				<surname>Suchanek</surname>
			</person>
			<person>
				<givenname>Gjergji</givenname>
				<surname>Kasneci</surname>
			</person>
			<person>
				<givenname>Thomas</givenname>
				<surname>Neumann</surname>
			</person>
			<person>
				<givenname>Maya</givenname>
				<surname>Ramanath</surname>
			</person>
			<person>
				<givenname>Gerhard</givenname>
				<surname>Weikum</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>We present ANGIE, a system that can answer user queries by combining knowledge from a local database with knowledge retrieved from Web services. If a user poses a query that cannot be answered by the local database alone, ANGIE calls the appropriate Web services to retrieve the missing information. This information is integrated seamlessly and transparently into the local database, so that the user can query and browse the knowledge base while appropriate Web services are called automatically in the background.</p>
			</richtext>
		</abstract>
		<pages>1570-1573</pages>
		<title type="sharef:primaryTitle">ANGIE: Active Knowledge for Interactive Exploration</title>
		<identifier type="sharef:uri" resourceType="application/pdf">http://suchanek.name/work/publications/vldb2009d.pdf</identifier>
	</reference>
	<reference name="has09" src="bibtex:inproceedings" src-info="bibtex:line-7417" type="sharef:inproceedings" crossref="vldb09">
		<names type="sharef:author">
			<person>
				<givenname>Oktie</givenname>
				<surname>Hassanzadeh</surname>
			</person>
			<person>
				<givenname>Reynold</givenname>
				<surname>Xin</surname>
			</person>
			<person>
				<givenname>Renée J.</givenname>
				<surname>Miller</surname>
			</person>
			<person>
				<givenname>Anastasios</givenname>
				<surname>Kementsietsidis</surname>
			</person>
			<person>
				<givenname>Lipyeow</givenname>
				<surname>Lim</surname>
			</person>
			<person>
				<givenname>Min</givenname>
				<surname>Wang</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>We present Linkage Query Writer (LinQuer), a system for generating SQL queries for semantic link discovery over relational data. The LinQuer framework consists of (a) LinQL, a language for specification of linkage requirements; (b) a web interface and an API for translating LinQL queries to standard SQL queries; (c) an interface that assists users in writing LinQL queries. We discuss the challenges involved in the design and implementation of a declarative and easy to use framework for discovering links between different data items in a single data source or across different data sources. We demonstrate different steps of the linkage requirements specification and discovery process in several real world scenarios and show how the LinQuer system can be used to create high-quality linked data sources.</p>
			</richtext>
		</abstract>
		<pages>1590-1593</pages>
		<title type="sharef:primaryTitle">Linkage Query Writer</title>
	</reference>
	<reference name="che09" src="bibtex:inproceedings" src-info="bibtex:line-7425" type="sharef:inproceedings" crossref="vldb09">
		<names type="sharef:author">
			<person>
				<givenname>Huajun</givenname>
				<surname>Chen</surname>
			</person>
			<person>
				<givenname>Bin</givenname>
				<surname>Lu</surname>
			</person>
			<person>
				<givenname>Yuan</givenname>
				<surname>Ni</surname>
			</person>
			<person>
				<givenname>Guo Tong</givenname>
				<surname>Xie</surname>
			</person>
			<person>
				<givenname>Chunying</givenname>
				<surname>Zhou</surname>
			</person>
			<person>
				<givenname>Jinhua</givenname>
				<surname>Mi</surname>
			</person>
			<person>
				<givenname>Zhaohui</givenname>
				<surname>Wu</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>We present sMash, a system for facilitating users to mashup Web data. The aspects emphasized by the demo are: (1) how to help novice users master data APIs and relationships amongst them easily; (2) how to inspire various users to build more amazing Web data mashups. First, a real-life data API network is constructed and visualized to enable users to surf and mashup. Second, two kinds of recommendations are generated dynamically based on a comprehensive analysis of the network, user's traces and a repository of mashups to provide navigation.</p>
			</richtext>
		</abstract>
		<pages>1602-1605</pages>
		<title type="sharef:primaryTitle">Mashup by Surfing a Web of Data APIs</title>
	</reference>
	<reference name="zha09b" src="bibtex:inproceedings" src-info="bibtex:line-7433" type="sharef:inproceedings" crossref="vldb09">
		<names type="sharef:author">
			<person>
				<givenname>Ning</givenname>
				<surname>Zhang</surname>
			</person>
			<person>
				<givenname>Nipun</givenname>
				<surname>Agarwal</surname>
			</person>
			<person>
				<givenname>Sivasankaran</givenname>
				<surname>Chandrasekar</surname>
			</person>
			<person>
				<givenname>Sam</givenname>
				<surname>Idicula</surname>
			</person>
			<person>
				<givenname>Vijay</givenname>
				<surname>Medi</surname>
			</person>
			<person>
				<givenname>Sabina</givenname>
				<surname>Petride</surname>
			</person>
			<person>
				<givenname>Balasubramanyam</givenname>
				<surname>Sthanikam</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Oracle RDBMS has supported XML data management for more than six years since version 9i. Prior to 11g, text-centric XML documents can be stored as-is in a CLOB column and schema-based data-centric documents can be shredded and stored in object-relational (OR) tables mapped from their XML Schema. However, both storage formats have intrinsic limitations — XML/CLOB has unacceptable query and update performance, and XML/OR requires XML schema. To tackle this problem, Oracle 11g introduces a native Binary XML storage format and a complete stack of data management operations. Binary XML was designed to address a wide range of real application problems encountered in XML data management — schema flexibility, amenability to XML indexes, update performance, schema evolution, just to name a few. In this paper, we introduce the Binary XML storage format based on Oracle SecureFiles System. We propose a lightweight navigational index on top of the storage and an NFA-based navigational algorithm to provide efficient streaming processing. We further optimize query processing by exploiting XML structural and schema information that are collected in database dictionary. We conducted extensive experiments to demonstrate high performance of the native Binary XML in query processing, update, and space consumption.</p>
			</richtext>
		</abstract>
		<pages>1354-1365</pages>
		<title type="sharef:primaryTitle">Binary XML Storage and Query Processing in Oracle 11g</title>
		<field type="bibtex:topic">xdbms[0.8] xml[0.8] xquery[0.8] xpath[0.8]</field>
	</reference>
	<reference name="vldb09" src="bibtex:proceedings" src-info="bibtex:line-7442" type="sharef:proceedings">
		<date value="2009-08"/>
		<address type="sharef:placePublished">Lyon, France</address>
		<field type="bibtex:index">VLDB 2009</field>
		<publisher>ACM Press</publisher>
		<title type="sharef:primaryTitle">35th International Conference on Very Large Data Bases (VLDB 2009)</title>
		<identifier type="sharef:uri" resourceType="text/html">http://www.informatik.uni-trier.de/~ley/db/journals/pvldb/pvldb2.html</identifier>
	</reference>
	<reference name="ye05" src="bibtex:inproceedings" src-info="bibtex:line-7457" type="sharef:inproceedings" crossref="icmb05">
		<names type="sharef:author">
			<person>
				<givenname>Lei</givenname>
				<surname>Ye</surname>
			</person>
			<person>
				<givenname>Henry C. B.</givenname>
				<surname>Chan</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>This paper presents an RFID-based logistics control system for business-to-business electronic commerce. In particular, two contributions are made. First, we employ an XML-based method that effectively and flexibly reads/writes RFID tags for the purpose of identifying goods. Second, we employ a Markov decision model or backward induction algorithm to find the best way to transport goods based on the information on the tags. Analytical results are presented to evaluate the effectiveness of the system.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1109/ICMB.2005.85</identifier>
		<pages>630-636</pages>
		<title type="sharef:primaryTitle">RFID-Based Logistics Control System for Business-to-Business E-Commerce</title>
		<field type="bibtex:topic">rfid[0.8]</field>
	</reference>
	<reference name="icmb05" src="bibtex:proceedings" src-info="bibtex:line-7467" type="sharef:proceedings">
		<date value="2005-07"/>
		<address type="sharef:placePublished">Sydney, Australia</address>
		<field type="bibtex:index">ICMB 2005</field>
		<identifier type="sharef:isbn">0-7695-2367-6</identifier>
		<publisher>IEEE Computer Society Press</publisher>
		<title type="sharef:primaryTitle">2005 International Conference on Mobile Business</title>
		<identifier type="sharef:uri">http://www.mbusiness2005.org/</identifier>
		<identifier type="sharef:uri" resourceType="text/html">http://www.informatik.uni-trier.de/~ley/db/conf/icmb/icmb2005.html</identifier>
	</reference>
	<reference name="wil09h" src="bibtex:inproceedings" src-info="bibtex:line-7484" type="sharef:inproceedings" crossref="fqas2009">
		<names type="sharef:author">
			<person>
				<givenname>Erik</givenname>
				<surname>Wilde</surname>
			</person>
			<person>
				<givenname>Alexandros</givenname>
				<surname>Marinos</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Managing information, access to information, and updates to relevant information on the Web has become a challenging task because of the volume and the variety of information sources and services available on the Web. This problem will only grow because of the increasing number of potential information resources, and the increasing number of services which could be driven by machine-friendly access to these resources. In this paper, we propose to use the established and simple metamodel of feeds as a proxy for information resources on the Web, and to use feed-based methods for producing, aggregating, querying, and publishing information about resources on the Web. We propose an architecture that is flexible and scalable and uses well-established RESTful methods of loose coupling. By using such an architecture, mashups and the repurposing of Web services is encouraged, and the simplicity of the underlying metamodel places no undue restrictions on the possible application areas.</p>
			</richtext>
		</abstract>
		<pages>663-674</pages>
		<title type="sharef:primaryTitle">Feed Querying as a Proxy for Querying the Web</title>
		<field type="bibtex:topic">atom[0.8]</field>
		<identifier type="sharef:uri">http://dret.net/netdret/publications#wil09g</identifier>
	</reference>
	<reference name="fqas2009" src="bibtex:proceedings" src-info="bibtex:line-7494" type="sharef:proceedings">
		<date value="2009-10"/>
		<address type="sharef:placePublished">Roskilde, Denmark</address>
		<field type="bibtex:index">FQAS 2009</field>
		<publisher>Springer-Verlag</publisher>
		<title type="sharef:seriesTitle">Lecture Notes in Artificial Intelligence</title>
		<title type="sharef:primaryTitle">Eighth International Conference on Flexible Query Answering Systems</title>
		<identifier type="sharef:uri" resourceType="text/html">http://www.informatik.uni-trier.de/~ley/db/conf/fqas/fqas2009.html</identifier>
		<volume>5822</volume>
	</reference>
	<reference name="mar05" src="bibtex:inproceedings" src-info="bibtex:line-7511" type="sharef:inproceedings" crossref="icdt05">
		<names type="sharef:author">
			<person>
				<givenname>Wim</givenname>
				<surname>Martens</surname>
			</person>
			<person>
				<givenname>Frank</givenname>
				<surname>Neven</surname>
			</person>
			<person>
				<givenname>Thomas</givenname>
				<surname>Schwentick</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>It is shown that the class of regular tree languages admitting one-pass preorder typing is exactly the class defined by restrained competition tree grammars introduced by Murata et al. In a streaming context, the former is the largest class of XSDs where every element in a document can be typed when its opening tag is met. The main technical machinery consists of semantical characterizations of restrained competition grammars and their subclasses. In particular, they can be characterized in terms of the context of nodes, closure properties, allowed patterns and guarded DTDs. It is further shown that deciding whether a schema is restrained competition is tractable. Deciding whether a schema is equivalent to a restrained competition tree grammar, or one of its subclasses, is much more difficult: it is complete for EXPTIME. We show that our semantical characterizations allow for easy optimization and minimization algorithms. Finally, we relate the notion of one-pass preorder typing to the existing XML Schema standard.</p>
			</richtext>
		</abstract>
		<pages>68-82</pages>
		<title type="sharef:primaryTitle">Which XML Schemas Admit 1-Pass Preorder Typing?</title>
		<field type="bibtex:topic">xsd[0.8]</field>
		<identifier type="sharef:uri">http://www.springerlink.com/link.asp?id=u7w84n35p36nr7ng</identifier>
	</reference>
	<reference name="icdt05" src="bibtex:proceedings" src-info="bibtex:line-7521" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>Thomas</givenname>
				<surname>Eiter</surname>
			</person>
			<person>
				<givenname>Leonid</givenname>
				<surname>Libkin</surname>
			</person>
		</names>
		<date value="2005-01"/>
		<address type="sharef:placePublished">Edinburgh, UK</address>
		<field type="bibtex:index">ICDT 2005</field>
		<identifier type="sharef:isbn">3-540-24288-0</identifier>
		<publisher>Springer-Verlag</publisher>
		<title type="sharef:seriesTitle">Lecture Notes in Computer Science</title>
		<title type="sharef:primaryTitle">10th International International Conference on Database Theory</title>
		<identifier type="sharef:uri" resourceType="text/html">http://www.informatik.uni-trier.de/~ley/db/conf/icdt/icdt2005.html</identifier>
		<volume>3363</volume>
	</reference>
	<reference name="tok07" src="bibtex:inproceedings" src-info="bibtex:line-7540" type="sharef:inproceedings" crossref="dasfaa2007">
		<names type="sharef:author">
			<person>
				<givenname>Wee Hyong</givenname>
				<surname>Tok</surname>
			</person>
			<person>
				<givenname>Stéphane</givenname>
				<surname>Bressan</surname>
			</person>
			<person>
				<givenname>Mong-Li</givenname>
				<surname>Lee</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>RSS (Really Simple Syndication) is a format used for the publication and syndication of web content. While several frameworks, techniques and algorithms have been proposed and studied for the processing of complex queries on data streams, current RSS reader and aggregator software and services do not propose advanced query facilities. We designed and implemented a prototype RSS aggregator service, called Danaïdes, for the processing of complex queries on continuously updated RSS feeds and of progressively producing results. We demonstrate the prototype and its several user-interfaces with a geographical application using geoRSS feeds. This work is a practical application of our research on progressive query processing algorithms for data streams.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1007/978-3-540-71703-4_112</identifier>
		<pages>1115-1118</pages>
		<title type="sharef:primaryTitle">Danaïdes: Continuous and Progressive Complex Queries on RSS Feeds</title>
		<field type="bibtex:topic">georss[0.8]</field>
		<identifier type="sharef:uri">http://www.springerlink.com/content/q27j82255210u877/</identifier>
	</reference>
	<reference name="dasfaa2007" src="bibtex:proceedings" src-info="bibtex:line-7551" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>Kotagiri</givenname>
				<surname>Ramamohanarao</surname>
			</person>
			<person>
				<givenname>P. Radha</givenname>
				<surname>Krishna</surname>
			</person>
			<person>
				<givenname>Mukesh K.</givenname>
				<surname>Mohania</surname>
			</person>
			<person>
				<givenname>Ekawit</givenname>
				<surname>Nantajeewarawat</surname>
			</person>
		</names>
		<date value="2007-04"/>
		<address type="sharef:placePublished">Bangkok, Thailand</address>
		<field type="bibtex:index">DASFAA 2007</field>
		<identifier type="sharef:isbn">978-3-540-71702-7</identifier>
		<publisher>Springer-Verlag</publisher>
		<title type="sharef:seriesTitle">Lecture Notes in Computer Science</title>
		<title type="sharef:primaryTitle">12th International Conference on Database Systems for Advanced Applications</title>
		<identifier type="sharef:uri" resourceType="text/html">http://www.informatik.uni-trier.de/~ley/db/conf/dasfaa/dasfaa2007.html</identifier>
		<volume>4443</volume>
	</reference>
	<reference name="bai05" src="bibtex:inproceedings" src-info="bibtex:line-7570" type="sharef:inproceedings" crossref="reasonweb05">
		<names type="sharef:author">
			<person>
				<givenname>James</givenname>
				<surname>Bailey</surname>
			</person>
			<person>
				<givenname>François</givenname>
				<surname>Bry</surname>
			</person>
			<person>
				<givenname>Tim</givenname>
				<surname>Furche</surname>
			</person>
			<person>
				<givenname>Sebastian</givenname>
				<surname>Schaffert</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>A number of techniques have been developed to facilitate powerful data retrieval on the Web and Semantic Web. Three categories of Web query languages can be distinguished, according to the format of the data they can retrieve: XML, RDF and Topic Maps. This article introduces the spectrum of languages falling into these categories and summarises their salient aspects. The languages are introduced using common sample data and query types. Key aspects of the query languages considered are stressed in a conclusion.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1007/11526988_3</identifier>
		<pages>35-133</pages>
		<title type="sharef:primaryTitle">Web and Semantic Web Query Languages: A Survey</title>
	</reference>
	<reference name="reasonweb05" src="bibtex:proceedings" src-info="bibtex:line-7579" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>Norbert</givenname>
				<surname>Eisinger</surname>
			</person>
			<person>
				<givenname>Jan</givenname>
				<surname>Małuszyński</surname>
			</person>
		</names>
		<date value="2005-07"/>
		<address type="sharef:placePublished">Misda, Malta</address>
		<identifier type="sharef:doi">10.1007/11526988</identifier>
		<identifier type="sharef:isbn">978-3-540-27828-3</identifier>
		<publisher>Springer-Verlag</publisher>
		<title type="sharef:seriesTitle">Lecture Notes in Computer Science</title>
		<title type="sharef:primaryTitle">Reasoning Web</title>
		<volume>3564</volume>
	</reference>
	<reference name="gra03" src="bibtex:inproceedings" src-info="bibtex:line-7597" type="sharef:inproceedings" crossref="esop03">
		<names type="sharef:author">
			<person>
				<givenname>Paul</givenname>
				<surname>Graunke</surname>
			</person>
			<person>
				<givenname>Robert Bruce</givenname>
				<surname>Findler</surname>
			</person>
			<person>
				<givenname>Shriram</givenname>
				<surname>Krishnamurthi</surname>
			</person>
			<person>
				<givenname>Matthias</givenname>
				<surname>Felleisen</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Programmers confront a minefield when they design interactive Web programs. Web interactions take place via Web browsers. With browsers, consumers can whimsically navigate among the various stages of a dialog and can thus confuse the most sophisticated corporate Web sites. In turn, Web services can fault in frustrating and inexplicable ways. The quickening transition from Web scripts to Web services lends these problems immediacy. To address this programming problem, we develop a foundational model of Web interactions and use it to formally describe two classes of errors. The model suggests techniques for detecting both classes of errors. For one class we present an incrementally checked record type system, which effectively eliminates these errors. For the other class, we introduce a dynamic safety check, which catches the mistakes relative to programmers' simple annotations.</p>
			</richtext>
		</abstract>
		<pages>238-252</pages>
		<title type="sharef:primaryTitle">Modeling Web Interactions</title>
		<identifier type="sharef:uri">http://www.springerlink.com/content/fc62enk0kfqltp2g</identifier>
	</reference>
	<reference name="esop03" src="bibtex:proceedings" src-info="bibtex:line-7606" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>Pierpaolo</givenname>
				<surname>Degano</surname>
			</person>
		</names>
		<date value="2003-04"/>
		<address type="sharef:placePublished">Warsaw, Poland</address>
		<field type="bibtex:index">ESOP 2003</field>
		<publisher>Springer-Verlag</publisher>
		<title type="sharef:seriesTitle">Lecture Notes in Computer Science</title>
		<title type="sharef:primaryTitle">12th European Symposium on Programming</title>
		<identifier type="sharef:uri">http://www.springerlink.com/content/j31cqhf4xtda</identifier>
		<volume>2618</volume>
	</reference>
	<reference name="haa07a" src="bibtex:inproceedings" src-info="bibtex:line-7624" type="sharef:inproceedings" crossref="icdt07">
		<names type="sharef:author">
			<person>
				<givenname>Laura M.</givenname>
				<surname>Haas</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Information integration is becoming a critical problem for businesses and individuals alike. Data volumes are sky-rocketing, and new sources and types of information are proliferating. This paper briefly reviews some of the key research accomplishments in information integration (theory and systems), then describes the current state-of-the-art in commercial practice, and the challenges (still) faced by CIOs and application developers. One critical challenge is choosing the right combination of tools and technologies to do the integration. Although each has been studied separately, we lack a unified (and certainly, a unifying) understanding of these various approaches to integration. Experience with a variety of integration projects suggests that we need a broader framework, perhaps even a theory, which explicitly takes into account requirements on the result of the integration, and considers the entire end-to-end integration process.</p>
			</richtext>
		</abstract>
		<pages>28-43</pages>
		<title type="sharef:primaryTitle">Beauty and the Beast: The Theory and Practice of Information Integration</title>
		<identifier type="sharef:uri">http://www.springerlink.com/content/9kph50v1446m662l/</identifier>
	</reference>
	<reference name="icdt07" src="bibtex:proceedings" src-info="bibtex:line-7633" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>Thomas</givenname>
				<surname>Schwentick</surname>
			</person>
			<person>
				<givenname>Dan</givenname>
				<surname>Suciu</surname>
			</person>
		</names>
		<date value="2007-01"/>
		<address type="sharef:placePublished">Barcelona, Spain</address>
		<identifier type="sharef:doi">10.1007/11965893</identifier>
		<field type="bibtex:index">ICDT 2007</field>
		<identifier type="sharef:isbn">978-3-540-69269-0</identifier>
		<publisher>Springer-Verlag</publisher>
		<title type="sharef:seriesTitle">Lecture Notes in Computer Science</title>
		<title type="sharef:primaryTitle">12th International International Conference on Database Theory</title>
		<identifier type="sharef:uri" resourceType="text/html">http://www.informatik.uni-trier.de/~ley/db/conf/icdt/icdt2007.html</identifier>
		<volume>4353</volume>
	</reference>
	<reference name="gre99" src="bibtex:inproceedings" src-info="bibtex:line-7653" type="sharef:inproceedings" crossref="hfw99">
		<names type="sharef:author">
			<person>
				<givenname>Saul</givenname>
				<surname>Greenberg</surname>
			</person>
			<person>
				<givenname>Andy</givenname>
				<surname>Cockburn</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>This paper concerns the ubiquitous Back button found in most Web browsers. First, we outline why Back is an effective method for revisiting WWW pages: a) It allows rapid return to very recently visited pages, which comprise the majority of pages a person wishes to return to; b) People can use it even with a naive model of the way it works; c) People usually keep it on permanent display because it is visually compact; and d) Back works via a simple 'click until the desired page is recognized' strategy. Second, we investigate the behavior of Back. The typical stack-based behavior underlying Back is problematic because some previously seen pages are not reachable through it. To get around this problem, we offer several alternate behaviors of the Back button, all based upon a recency model. The advantage of recency is that all previously seen pages are now available via Back. Because trade-offs exist, we present both problems and prospects of these different Back behaviors in various navigational situations.</p>
			</richtext>
		</abstract>
		<title type="sharef:primaryTitle">Getting Back to Back: Alternate Behaviors for a Web Browser's Back Button</title>
		<identifier type="sharef:uri">http://zing.ncsl.nist.gov/hfweb/proceedings/greenberg/</identifier>
	</reference>
	<reference name="hfw99" src="bibtex:proceedings" src-info="bibtex:line-7661" type="sharef:proceedings">
		<date value="1999-06"/>
		<address type="sharef:placePublished">Gaithersburg, Maryland</address>
		<title type="sharef:primaryTitle">5th Annual Human Factors and the Web Conference</title>
		<identifier type="sharef:uri" resourceType="text/html">http://zing.ncsl.nist.gov/hfweb/proceedings/proceedings.en.html</identifier>
	</reference>
	<reference name="wil04j" src="bibtex:inproceedings" src-info="bibtex:line-7674" type="sharef:inproceedings" crossref="ecows04">
		<names type="sharef:author">
			<person>
				<givenname>Erik</givenname>
				<surname>Wilde</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Web Services are designed for loosely coupled systems, which means that in many cases it is not possible to synchronously upgrade all peers of a Web Service scenario. Instead, Web Service peers should be able to coexist in different versions. Additionally, older software versions often could benefit from upgrades to the service if they were able to understand it. This paper presents a framework for semantically extensible schemas for Web Service evolution. The core idea of is to use declarative semantics to describe extensions to a service's vocabulary. These declarative semantics can be used by older software versions to understand the semantics of extensions, thus enabling older software to dynamically adapt to newer versions of the service. As long as declarative semantics are sufficient, older software can benefit from the service's extension.</p>
			</richtext>
		</abstract>
		<pages>30-45</pages>
		<title type="sharef:primaryTitle">Semantically Extensible Schemas for Web Service Evolution</title>
		<field type="bibtex:topic">xsd[0.8]</field>
		<identifier type="sharef:uri">http://dret.net/netdret/publications#wil04j</identifier>
		<identifier type="sharef:uri">http://www.springerlink.com/link.asp?id=fu72aynphvj9q4n2</identifier>
	</reference>
	<reference name="zha04" src="bibtex:inproceedings" src-info="bibtex:line-7685" type="sharef:inproceedings" crossref="ecows04">
		<names type="sharef:author">
			<person>
				<givenname>Jimmy</givenname>
				<surname>Zhang</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>As the first step of most XML processing algorithms, one usually extracts token content out of the source document into many discrete string objects. We propose a "non-extractive" tokenization approach that maintains the source document intact in memory. Using a binary encoding specification called Virtual Token Descriptor (VTD), the processing model represents tokens exclusively using starting offset and length. To create a hierarchical view of the data encapsulated in the SOAP message, the parser further indexes elements of same depths using directory-like structures we call location cache. Through a demonstration of navigating the document hierarchy using VTD and location caches, we show that it is indeed possible to create a cursor-based API that retains most of DOM's random-access capabilities at a fraction of its memory usage. Furthermore, by analyzing key design constraints of custom hardware, we reason that the memory conserving characteristics of the processing model simultaneously make possible "SOAP on a chip" and "binary-enhanced SOAP." The benchmark results show that the reference implementation of our processing model significantly outperforms Xerces DOM in terms of both memory and processing performance.</p>
			</richtext>
		</abstract>
		<field type="bibtex:index">vtd[1]</field>
		<pages>152-167</pages>
		<title type="sharef:primaryTitle">SOAP Processing: A Non-extractive Approach</title>
	</reference>
	<reference name="mar04b" src="bibtex:inproceedings" src-info="bibtex:line-7694" type="sharef:inproceedings" crossref="ecows04">
		<names type="sharef:author">
			<person>
				<givenname>Jean-Philippe</givenname>
				<surname>Martin-Flatin</surname>
			</person>
			<person>
				<givenname>Pierre-Alain</givenname>
				<surname>Doffoel</surname>
			</person>
			<person>
				<givenname>Mario</givenname>
				<surname>Jeckle</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>As evidenced by discussions in standards organizations, vendors and the user community have recently showed a growing interest in using XML technologies for management purposes. To investigate the relevance of this approach, we have added support for Web Services to JAMAP (a Java-based research prototype of a management platform) and managed a gigabit transoceanic testbed. In this paper, we present the main lessons learned during this process and attempt to draw conclusions of general interest as to the applicability of Web Services for managing IP networks and systems. Our main conclusions are that XML, WSDL and SOAP are useful, especially for configuration management, whereas UDDI is not adequate. To date, we still lack a standard way of publishing, discovering and subscribing to Web Services for the purpose of managing network devices and systems.</p>
			</richtext>
		</abstract>
		<field type="bibtex:index">jamap[0.9]</field>
		<pages>239-253</pages>
		<title type="sharef:primaryTitle">Web Services for Integrated Management: A Case Study</title>
	</reference>
	<reference name="lar04" src="bibtex:inproceedings" src-info="bibtex:line-7703" type="sharef:inproceedings" crossref="ecows04">
		<names type="sharef:author">
			<person>
				<givenname>Rubén</givenname>
				<surname>Lara</surname>
			</person>
			<person>
				<givenname>Dumitru</givenname>
				<surname>Roman</surname>
			</person>
			<person>
				<givenname>Axel</givenname>
				<surname>Polleres</surname>
			</person>
			<person>
				<givenname>Dieter</givenname>
				<surname>Fensel</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Web Services have added a new level of functionality on top of current Web, enabling the use and combination of distributed functional components within and across company boundaries. The addition of semantic information to describe Web Services, in order to enable the automatic location, combination and use of distributed functionalities, is nowadays one of the most relevant research topics due to its potential to achieve dynamic, scalable and cost-effective Enterprise Application Integration and eCommerce. In this context, two major initiatives aim to realize Semantic Web Services by providing appropriate description means that enable the effective exploitation of semantic annotations, namely: WSMO and OWL-S. In this paper, we conduct a conceptual comparison that identifies the overlaps and differences of both initiatives in order to evaluate their applicability in a real setting and their potential to become widely accepted standards.</p>
			</richtext>
		</abstract>
		<field type="bibtex:index">wsmo[0.9] owls[0.9]</field>
		<pages>254-269</pages>
		<title type="sharef:primaryTitle">A Conceptual Comparison of WSMO and OWL-S</title>
	</reference>
	<reference name="pee04" src="bibtex:inproceedings" src-info="bibtex:line-7712" type="sharef:inproceedings" crossref="ecows04">
		<names type="sharef:author">
			<person>
				<givenname>Joachim</givenname>
				<surname>Peer</surname>
			</person>
			<person>
				<givenname>Maja</givenname>
				<surname>Vukovic</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Automatic evaluation and consumption of Web services requires a comprehensive semantic information model of a Web service. One example of a language that facilitates capability-driven description of services is OWL-S. However, it imposes two limitations: (1) it offers no native support for the description of certain rule types often needed for service description and (2) it leads to very large service description documents that are difficult to read and write. In this paper, we propose an XML-based markup format that addresses these problems and allows for semantic annotation of Web services of different technical flavors. This work is inspired by OWL-S, however it makes certain design decisions aimed to increase the ease of use of semantic Web service descriptions, by presenting a significantly more compact syntax for service markup and grounding. Furthermore, the proposed description format provides support for non-deterministic service operations.</p>
			</richtext>
		</abstract>
		<field type="bibtex:index">pddl[0.7]</field>
		<pages>285-299</pages>
		<title type="sharef:primaryTitle">A Proposal for a Semantic Web Service Description Format</title>
	</reference>
	<reference name="ecows04" src="bibtex:proceedings" src-info="bibtex:line-7721" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>Liang-Jie</givenname>
				<surname>Zhang</surname>
			</person>
			<person>
				<givenname>Mario</givenname>
				<surname>Jeckle</surname>
			</person>
		</names>
		<date value="2004-09"/>
		<address type="sharef:placePublished">Erfurt, Germany</address>
		<identifier type="sharef:doi">10.1007/b100919</identifier>
		<field type="bibtex:index">ECOWS 2004</field>
		<identifier type="sharef:isbn">3540442774</identifier>
		<publisher>Springer-Verlag</publisher>
		<title type="sharef:seriesTitle">Lecture Notes in Computer Science</title>
		<title type="sharef:primaryTitle">Web Services — 2004 European Conference on Web Services</title>
		<identifier type="sharef:uri">http://www.ebai.us/ecows/2004/</identifier>
		<volume>3250</volume>
	</reference>
	<reference name="zha09" src="bibtex:inproceedings" src-info="bibtex:line-7741" type="sharef:inproceedings" crossref="icws2009">
		<names type="sharef:author">
			<person>
				<givenname>Haibo</givenname>
				<surname>Zhao</surname>
			</person>
			<person>
				<givenname>Prashant</givenname>
				<surname>Doshi</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Emerging as the popular choice for leading Internet companies to expose internal data and resources, RESTful Web services are attracting increasing attention in the industry. While automating WSDL/SOAP based Web service composition has been extensively studied in the research community, automated RESTful Web service composition in the context of service-oriented architecture (SOA), to the best of our knowledge, is less explored. As an early paper addressing this problem, this paper discusses the challenges of composing RESTful Web services and proposes a formal model for describing individual Web services and automating the composition. It demonstrates our approach by applying it to a real-world RESTful Web service composition problem. This paper represents our initial efforts towards the problem of automated RESTful Web service composition. We are hoping that it will draw interests from the research community on Web services, and engage more researchers in this challenge.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1109/ICWS.2009.111</identifier>
		<field type="bibtex:index">rest[0.7]</field>
		<pages>189-196</pages>
		<title type="sharef:primaryTitle">Towards Automated RESTful Web Service Composition</title>
	</reference>
	<reference name="mar09a" src="bibtex:inproceedings" src-info="bibtex:line-7751" type="sharef:inproceedings" crossref="icws2009">
		<names type="sharef:author">
			<person>
				<givenname>Alexandros</givenname>
				<surname>Marinos</surname>
			</person>
			<person>
				<givenname>Amir R.</givenname>
				<surname>Razavi</surname>
			</person>
			<person>
				<givenname>Sotiris</givenname>
				<surname>Moschoyiannis</surname>
			</person>
			<person>
				<givenname>Paul J.</givenname>
				<surname>Krause</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>With REST becoming a popular paradigm for Web services, more and more use cases are applied to it, including some that require transactional guarantees. We propose a RESTful transaction model that satisfies both the constraints of transactions as well as those of the REST architectural style. We provide formal proof of consistency and recoverability in the proposed framework and show the robustness of its properties in the presence of concurrent transactions.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1109/ICWS.2009.99</identifier>
		<field type="bibtex:index">rest[0.9] retro[1]</field>
		<pages>181-188</pages>
		<title type="sharef:primaryTitle">RETRO: A Consistent and Recoverable RESTful Transaction Model</title>
	</reference>
	<reference name="icws2009" src="bibtex:proceedings" src-info="bibtex:line-7761" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>Ernesto</givenname>
				<surname>Damiani</surname>
			</person>
			<person>
				<givenname>Rong</givenname>
				<surname>Chang</surname>
			</person>
			<person>
				<givenname>Jia</givenname>
				<surname>Zhang</surname>
			</person>
		</names>
		<date value="2009-07"/>
		<address type="sharef:placePublished">Los Angeles, California</address>
		<field type="bibtex:index">ICWS 2009</field>
		<identifier type="sharef:isbn">978-0-7695-3709-2</identifier>
		<publisher>IEEE Computer Society Press</publisher>
		<title type="sharef:primaryTitle">2009 IEEE International Conference on Web Services</title>
	</reference>
	<reference name="li02" src="bibtex:inproceedings" src-info="bibtex:line-7777" type="sharef:inproceedings" crossref="iswc2002">
		<names type="sharef:author">
			<person>
				<givenname>Gangmin</givenname>
				<surname>Li</surname>
			</person>
			<person>
				<givenname>Victoria</givenname>
				<surname>Uren</surname>
			</person>
			<person>
				<givenname>Enrico</givenname>
				<surname>Motta</surname>
			</person>
			<person>
				<givenname>Simon</givenname>
				<surname>Buckingham Shum</surname>
			</person>
			<person>
				<givenname>John</givenname>
				<surname>Domingue</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>The usability of research papers on the Web would be enhanced by a system that explicitly modelled the rhetorical relations between claims in related papers. We describe ClaiMaker, a system for modelling readers' interpretations of the core content of papers. ClaiMaker provides tools to build a Semantic Web representation of the claims in research papers using an ontology of relations. We demonstrate how the system can be used to make inter-document queries.</p>
			</richtext>
		</abstract>
		<pages>436-441</pages>
		<title type="sharef:primaryTitle">ClaiMaker: Weaving a Semantic Web of Research Papers</title>
		<field type="bibtex:topic">claimaker[0.9]</field>
		<identifier type="sharef:uri" resourceType="application/pdf">http://kmi.open.ac.uk/projects/scholonto/docs/ClaiMaker-ISWC2002.pdf</identifier>
	</reference>
	<reference name="iswc2002" src="bibtex:proceedings" src-info="bibtex:line-7787" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>Ian</givenname>
				<surname>Horrocks</surname>
			</person>
			<person>
				<givenname>James A.</givenname>
				<surname>Hendler</surname>
			</person>
		</names>
		<date value="2002-06"/>
		<address type="sharef:placePublished">Sardinia, Italy</address>
		<field type="bibtex:index">IWSC 2002</field>
		<publisher>Springer-Verlag</publisher>
		<title type="sharef:seriesTitle">Lecture Notes in Computer Science</title>
		<title type="sharef:primaryTitle">First International Semantic Web Conference</title>
		<identifier type="sharef:uri">http://iswc2002.semanticweb.org/</identifier>
		<volume>2342</volume>
	</reference>
	<reference name="wil10a" src="bibtex:inproceedings" src-info="bibtex:line-7805" type="sharef:inproceedings" crossref="icsoc2010">
		<names type="sharef:author">
			<person>
				<givenname>Erik</givenname>
				<surname>Wilde</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Linked Data has become a popular term and method of how to expose structured data on the Web. There currently are two school of thought when it comes to defining what Linked Data actually is, with one school of thought defining it more narrowly as a set of principles describing of how to publish data based on Semantic Web technologies, whereas the other school more generally defines it as any form of properly linked data that follows the Representational State Transfer (REST) architectural style of the Web. In this paper, we describe and compare these two schools of thoughts with a particular emphasis on how well they support principles of service orientation.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1007/978-3-642-17358-5_5</identifier>
		<pages>61-76</pages>
		<title type="sharef:primaryTitle">Linked Data and Service Orientation</title>
		<field type="bibtex:topic">soa[0.9] rest[0.8] rdf[0.8]</field>
		<identifier type="sharef:uri">http://dret.net/netdret/publications#wil10a</identifier>
		<identifier type="sharef:uri">http://www.springerlink.com/content/y21h1626v4706604/</identifier>
	</reference>
	<reference name="icsoc2010" src="bibtex:proceedings" src-info="bibtex:line-7817" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>Paul P.</givenname>
				<surname>Maglio</surname>
			</person>
			<person>
				<givenname>Mathias</givenname>
				<surname>Weske</surname>
			</person>
			<person>
				<givenname>Jian</givenname>
				<surname>Yang</surname>
			</person>
			<person>
				<givenname>Marcelo</givenname>
				<surname>Fantinato</surname>
			</person>
		</names>
		<date value="2010-12"/>
		<address type="sharef:placePublished">San Francisco, California</address>
		<identifier type="sharef:isbn">978-3-642-17357-8</identifier>
		<publisher>Springer-Verlag</publisher>
		<title type="sharef:seriesTitle">Lecture Notes in Computer Science</title>
		<title type="sharef:primaryTitle">8th International Conference on Service Oriented Computing (ICSOC 2010)</title>
		<identifier type="sharef:uri">http://icsoc10.disi.unitn.it/</identifier>
		<identifier type="sharef:uri" resourceType="text/html">http://www.informatik.uni-trier.de/~ley/db/conf/icsoc/icsoc2010.html</identifier>
		<volume>6470</volume>
	</reference>
	<reference name="haa04b" src="bibtex:inproceedings" src-info="bibtex:line-7836" type="sharef:inproceedings" crossref="iswc04">
		<names type="sharef:author">
			<person>
				<givenname>Peter</givenname>
				<surname>Haase</surname>
			</person>
			<person>
				<givenname>Jeen</givenname>
				<surname>Broekstra</surname>
			</person>
			<person>
				<givenname>Marc</givenname>
				<surname>Ehrig</surname>
			</person>
			<person>
				<givenname>Maarten</givenname>
				<surname>Menken</surname>
			</person>
			<person>
				<givenname>Peter</givenname>
				<surname>Mika</surname>
			</person>
			<person>
				<givenname>Michal</givenname>
				<surname>Plechawski</surname>
			</person>
			<person>
				<givenname>Pawel</givenname>
				<surname>Pyszlak</surname>
			</person>
			<person>
				<givenname>Björn</givenname>
				<surname>Schnizler</surname>
			</person>
			<person>
				<givenname>Ronny</givenname>
				<surname>Siebes</surname>
			</person>
			<person>
				<givenname>Steffen</givenname>
				<surname>Staab</surname>
			</person>
			<person>
				<givenname>Christoph</givenname>
				<surname>Tempich</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>This paper describes the design and implementation of Bibster, a Peer-to-Peer system for exchanging bibliographic data among Computer Science researchers. Bibster exploits ontologies in data-storage, query formulation, query-routing and answer presentation: When bibliographic entries are made available for use in Bibster, they are structured and classified according to two different ontologies. This ontological structure is then exploited to help user formulate their queries. Subsequently, the ontologies are used to improve query routing across the Peer-to-Peer network. Finally, the ontologies are used to post-process the returned answers in order to do duplicate detection. The paper describes each of these ontology-based aspects of Bibster. Bibster is fully implemented on top of the JXTA platform, and is about to be rolled out for field testing.</p>
			</richtext>
		</abstract>
		<pages>122-136</pages>
		<title type="sharef:primaryTitle">Bibster — A Semantics-Based Bibliographic Peer-to-Peer System</title>
		<field type="bibtex:topic">bibster[1]</field>
		<identifier type="sharef:uri" resourceType="application/pdf">http://bibster.semanticweb.org/publications/haase_04_bibster.pdf</identifier>
		<identifier type="sharef:uri">http://www.springerlink.com/link.asp?id=x5xxt0fuhvkc74r2</identifier>
	</reference>
	<reference name="haa04c" src="bibtex:inproceedings" src-info="bibtex:line-7847" type="sharef:inproceedings" crossref="iswc04">
		<names type="sharef:author">
			<person>
				<givenname>Peter</givenname>
				<surname>Haase</surname>
			</person>
			<person>
				<givenname>Jeen</givenname>
				<surname>Broekstra</surname>
			</person>
			<person>
				<givenname>Andreas</givenname>
				<surname>Eberhart</surname>
			</person>
			<person>
				<givenname>Raphael</givenname>
				<surname>Volz</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>The purpose of this paper is to provide a rigorous comparison of six query languages for RDF. We outline and categorize features that any RDF query language should provide and compare the individual languages along these features. We describe several practical usage examples for RDF queries and conclude with a comparison of the expressiveness of the particular query languages. The use cases, sample data and queries for the respective languages are available on the web</p>
			</richtext>
		</abstract>
		<pages>502-517</pages>
		<title type="sharef:primaryTitle">A Comparison of RDF Query Languages</title>
		<field type="bibtex:topic">rdf[0.8] rdql[0.8] serql[0.8] triple[0.8] versa[0.8] n3[0.8] rql[0.8]</field>
		<identifier type="sharef:uri">http://www.springerlink.com/link.asp?id=ftxy71qedrhb945v</identifier>
		<identifier type="sharef:uri">http://www.aifb.uni-karlsruhe.de/WBS/pha/rdf-query/</identifier>
	</reference>
	<reference name="cla04" src="bibtex:inproceedings" src-info="bibtex:line-7858" type="sharef:inproceedings" crossref="iswc04">
		<names type="sharef:author">
			<person>
				<givenname>Kendall Grant</givenname>
				<surname>Clark</surname>
			</person>
			<person>
				<givenname>Bijan</givenname>
				<surname>Parsia</surname>
			</person>
			<person>
				<givenname>Bryan</givenname>
				<surname>Thompson</surname>
			</person>
			<person>
				<givenname>Bradley</givenname>
				<surname>Bebee</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Semantic Web resources — that is, knowledge representation formalisms existing in a distributed hypermedia system — require different addressing and processing models and capacities than the typical kinds of World Wide Web resources. We describe an approach to building a Semantic Web resource protocol — a scalable, extensible logical addressing scheme and transport protocol — by using and extending existing specifications and technologies. We introduce XPointer and some infrequently used, but useful features of HTTP/1.1, in order to support addressing and server side processing of resource and subresource operations. We consider applications of the XPointer Framework for use in the Semantic Web, particularly for RDF and OWL resources and subresources. We describe two initial implementations: filtering of RSS resources by date and item range; RDF subresource selection using RDQL. Finally, we describe possible application to the problem of OWL imports.</p>
			</richtext>
		</abstract>
		<pages>564-575</pages>
		<title type="sharef:primaryTitle">A Semantic Web Resource Protocol: XPointer and HTTP</title>
		<field type="bibtex:topic">xpointer[0.8] http[0.8] rdql[0.8] rdf[0.8] owl[0.8]</field>
		<identifier type="sharef:uri">http://www.springerlink.com/link.asp?id=uphvk0wy2hfvjqqp</identifier>
	</reference>
	<reference name="iswc04" src="bibtex:proceedings" src-info="bibtex:line-7868" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>Sheila A.</givenname>
				<surname>McIlraith</surname>
			</person>
			<person>
				<givenname>Dimitris</givenname>
				<surname>Plexousakis</surname>
			</person>
			<person>
				<givenname>Frank</givenname>
				<surname link="van">Harmelen</surname>
			</person>
		</names>
		<date value="2004-11"/>
		<address type="sharef:placePublished">Hiroshima, Japan</address>
		<identifier type="sharef:doi">10.1007/b102467</identifier>
		<field type="bibtex:index">ISWC 2004</field>
		<title type="sharef:seriesTitle">Lecture Notes in Computer Science</title>
		<title type="sharef:primaryTitle">3rd International Semantic Web Conference</title>
		<identifier type="sharef:uri">http://iswc2004.semanticweb.org/</identifier>
		<identifier type="sharef:uri">http://www.springerlink.com/openurl.asp?genre=issue&amp;issn=0302-9743&amp;volume=3298&amp;issue=preprint</identifier>
		<volume>3298</volume>
	</reference>
	<reference name="aue07" src="bibtex:inproceedings" src-info="bibtex:line-7887" type="sharef:inproceedings" crossref="iswc07">
		<names type="sharef:author">
			<person>
				<givenname>Sören</givenname>
				<surname>Auer</surname>
			</person>
			<person>
				<givenname>Christian</givenname>
				<surname>Bizer</surname>
			</person>
			<person>
				<givenname>Georgi</givenname>
				<surname>Kobilarov</surname>
			</person>
			<person>
				<givenname>Jens</givenname>
				<surname>Lehmann</surname>
			</person>
			<person>
				<givenname>Richard</givenname>
				<surname>Cyganiak</surname>
			</person>
			<person>
				<givenname>Zachary</givenname>
				<surname>Ives</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>DBpedia is a community effort to extract structured information from Wikipedia and to make this information available on the Web. DBpedia allows you to ask sophisticated queries against datasets derived from Wikipedia and to link other datasets on the Web to Wikipedia data. We describe the extraction of the DBpedia datasets, and how the resulting information is published on the Web for human- and machine-consumption. We describe some emerging applications from the DBpedia community and show how website authors can facilitate DBpedia content within their sites. Finally, we present the current status of interlinking DBpedia with other open datasets on the Web and outline how DBpedia could serve as a nucleus for an emerging Web of open data.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1007/978-3-540-76298-0_52</identifier>
		<pages>722-735</pages>
		<title type="sharef:primaryTitle">DBpedia: A Nucleus for a Web of Open Data</title>
		<field type="bibtex:topic">dbpedia[1]</field>
		<identifier type="sharef:uri" resourceType="application/pdf">http://richard.cyganiak.de/2008/papers/dbpedia-iswc2007.pdf</identifier>
	</reference>
	<reference name="iswc07" src="bibtex:proceedings" src-info="bibtex:line-7898" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>Karl</givenname>
				<surname>Aberer</surname>
			</person>
			<person>
				<givenname>Key-Sun</givenname>
				<surname>Choi</surname>
			</person>
			<person>
				<givenname>Natasha Fridman</givenname>
				<surname>Noy</surname>
			</person>
			<person>
				<givenname>Dean</givenname>
				<surname>Allemang</surname>
			</person>
			<person>
				<givenname>Kyung-Il</givenname>
				<surname>Lee</surname>
			</person>
			<person>
				<givenname>Lyndon J. B.</givenname>
				<surname>Nixon</surname>
			</person>
			<person>
				<givenname>Jennifer</givenname>
				<surname>Golbeck</surname>
			</person>
			<person>
				<givenname>Peter</givenname>
				<surname>Mika</surname>
			</person>
			<person>
				<givenname>Diana</givenname>
				<surname>Maynard</surname>
			</person>
			<person>
				<givenname>Riichiro</givenname>
				<surname>Mizoguchi</surname>
			</person>
			<person>
				<givenname>Guus</givenname>
				<surname>Schreiber</surname>
			</person>
			<person>
				<givenname>Philippe</givenname>
				<surname>Cudré-Mauroux</surname>
			</person>
		</names>
		<date value="2007-11"/>
		<address type="sharef:placePublished">Busan, Korea</address>
		<identifier type="sharef:doi">10.1007/978-3-540-76298-0</identifier>
		<field type="bibtex:index">ISWC 2007</field>
		<identifier type="sharef:isbn">978-3-540-76297-3</identifier>
		<title type="sharef:seriesTitle">Lecture Notes in Computer Science</title>
		<title type="sharef:primaryTitle">6th International Semantic Web Conference (ISWC 2007)</title>
		<identifier type="sharef:uri" resourceType="text/html">http://www.informatik.uni-trier.de/~ley/db/conf/semweb/iswc2007.html</identifier>
		<volume>4825</volume>
	</reference>
	<reference name="suo07" src="bibtex:inproceedings" src-info="bibtex:line-7917" type="sharef:inproceedings" crossref="eswc07">
		<names type="sharef:author">
			<person>
				<givenname>Osma</givenname>
				<surname>Suominen</surname>
			</person>
			<person>
				<givenname>Kim</givenname>
				<surname>Viljanen</surname>
			</person>
			<person>
				<givenname>Eero</givenname>
				<surname>Hyvönen</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Many semantic portals use faceted browsing, where the facets are based on the underlying indexing ontologies of the content. However, in many cases, like in medical applications, the ontologies may be very large and complex, and do not provide the end-user with intuitive facet hierarchies for conceptualizing the content, for formulating queries, and for classifying the search results. We argue that in such cases end-user facets should be separated from the annotation ontologies, and show how to generalize the semantic view-based search paradigm to take into account this fact. A user-centric card sorting method is proposed for designing intuitive views for the end-users and a method for mapping its facets onto the indexing ontologies and search items is presented. The system has been implemented in a prototype of the semantic portal TerveSuomi.fi, a national health promotion portal in Finland.</p>
			</richtext>
		</abstract>
		<pages>356-370</pages>
		<title type="sharef:primaryTitle">User-Centric Faceted Search for Semantic Portals</title>
		<identifier type="sharef:uri">http://www.springerlink.com/content/h8479834kn50n502/</identifier>
	</reference>
	<reference name="eswc07" src="bibtex:proceedings" src-info="bibtex:line-7926" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>John</givenname>
				<surname>Davies</surname>
			</person>
			<person>
				<givenname>York</givenname>
				<surname>Sure</surname>
			</person>
			<person>
				<givenname>Holger</givenname>
				<surname>Lausen</surname>
			</person>
			<person>
				<givenname>Siegfried</givenname>
				<surname>Handschuh</surname>
			</person>
			<person>
				<givenname>Uwe</givenname>
				<surname>Keller</surname>
			</person>
			<person>
				<givenname>Stefan</givenname>
				<surname>Decker</surname>
			</person>
			<person>
				<givenname>Abraham</givenname>
				<surname>Bernstein</surname>
			</person>
			<person>
				<givenname>Pascal</givenname>
				<surname>Hitzler</surname>
			</person>
			<person>
				<givenname>Thorsten</givenname>
				<surname>Liebig</surname>
			</person>
			<person>
				<givenname>Johanna</givenname>
				<surname>Völker</surname>
			</person>
		</names>
		<date value="2007-06"/>
		<address type="sharef:placePublished">Innsbruck, Austria</address>
		<identifier type="sharef:doi">10.1007/978-3-540-72667-8</identifier>
		<field type="bibtex:index">ESWC 2007</field>
		<title type="sharef:seriesTitle">Lecture Notes in Computer Science</title>
		<title type="sharef:primaryTitle">4th European Semantic Web Conference</title>
		<identifier type="sharef:uri">http://www.springerlink.com/content/tr7816141645/?p=54002b997a8043e284f75d96899f2c4c&amp;pi=0</identifier>
		<volume>4519</volume>
	</reference>
	<reference name="huy05" src="bibtex:inproceedings" src-info="bibtex:line-7944" type="sharef:inproceedings" crossref="iswc2005">
		<names type="sharef:author">
			<person>
				<givenname>David</givenname>
				<surname>Huynh</surname>
			</person>
			<person>
				<givenname>Stefano</givenname>
				<surname>Mazzocchi</surname>
			</person>
			<person>
				<givenname>David R.</givenname>
				<surname>Karger</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>The Semantic Web Initiative envisions a Web wherein information is offered free of presentation, allowing more effective exchange and mixing across web sites and across web pages. But without substantial Semantic Web content, few tools will be written to consume it; without many such tools, there is little appeal to publish Semantic Web content. To break this chicken-and-egg problem, thus enabling more flexible information access, we have created a web browser extension called Piggy Bank that lets users make use of Semantic Web content within Web content as users browse the Web. Wherever Semantic Web content is not available, Piggy Bank can invoke screenscrapers to re-structure information within web pages into Semantic Web format. Through the use of Semantic Web technologies, Piggy Bank provides direct, immediate benefits to users in their use of the existing Web. Thus, the existence of even just a few Semantic Web-enabled sites or a few scrapers already benefits users. Piggy Bank thereby offers an easy, incremental upgrade path to users without requiring a wholesale adoption of the Semantic Web's vision. To further improve this Semantic Web experience, we have created Semantic Bank, a web server application that lets Piggy Bank users share the Semantic Web information they have collected, enabling collaborative efforts to build sophisticated Semantic Web information repositories through simple, everyday's use of Piggy Bank.</p>
			</richtext>
		</abstract>
		<pages>413-430</pages>
		<title type="sharef:primaryTitle">Piggy Bank: Experience the Semantic Web Inside Your Web Browser</title>
		<identifier type="sharef:uri" resourceType="application/pdf">http://simile.mit.edu/papers/iswc05.pdf</identifier>
	</reference>
	<reference name="iswc2005" src="bibtex:proceedings" src-info="bibtex:line-7953" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>Yolanda</givenname>
				<surname>Gil</surname>
			</person>
			<person>
				<givenname>Enrico</givenname>
				<surname>Motta</surname>
			</person>
			<person>
				<givenname>V. Richard</givenname>
				<surname>Benjamins</surname>
			</person>
			<person>
				<givenname>Mark A.</givenname>
				<surname>Musen</surname>
			</person>
		</names>
		<date value="2005-11"/>
		<address type="sharef:placePublished">Galway, Ireland</address>
		<field type="bibtex:index">ISWC 2005</field>
		<identifier type="sharef:isbn">3-540-29754-5</identifier>
		<title type="sharef:primaryTitle">4th International Semantic Web Conference (ISWC 2005)</title>
		<identifier type="sharef:uri" resourceType="text/html">http://www.informatik.uni-trier.de/~ley/db/conf/semweb/iswc2005.html</identifier>
	</reference>
	<reference name="wie05" src="bibtex:inproceedings" src-info="bibtex:line-7969" type="sharef:inproceedings" crossref="iswc2005p">
		<names type="sharef:author">
			<person>
				<givenname>Christian</givenname>
				<surname>Halaschek-Wiener</surname>
			</person>
			<person>
				<givenname>Jennifer</givenname>
				<surname>Golbeck</surname>
			</person>
			<person>
				<givenname>Andrew</givenname>
				<surname>Schain</surname>
			</person>
			<person>
				<givenname>Michael</givenname>
				<surname>Grove</surname>
			</person>
			<person>
				<givenname>Bijan</givenname>
				<surname>Parsia</surname>
			</person>
			<person>
				<givenname>James A.</givenname>
				<surname>Hendler</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>In this paper we present PhotoStuff, an annotation tool for digital images on the Semantic Web. PhotoStuff provides functionality to manually annotate images using Web ontologies, in addition to exploit pre-existing embedded image metadata for automatic annotation. Lastly, PhotoStuff is loosely coupled with a Semantic Web portal which provides image metadata management and interaction functionality.</p>
			</richtext>
		</abstract>
		<title type="sharef:primaryTitle">PhotoStuff — An Image Annotation Tool for the Semantic Web</title>
		<identifier type="sharef:uri" resourceType="application/pdf">http://www.mindswap.org/~chris/publications/PhotoStuffCR_pid83.pdf</identifier>
	</reference>
	<reference name="iswc2005p" src="bibtex:proceedings" src-info="bibtex:line-7977" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>Yolanda</givenname>
				<surname>Gil</surname>
			</person>
			<person>
				<givenname>Enrico</givenname>
				<surname>Motta</surname>
			</person>
			<person>
				<givenname>V. Richard</givenname>
				<surname>Benjamins</surname>
			</person>
			<person>
				<givenname>Mark A.</givenname>
				<surname>Musen</surname>
			</person>
		</names>
		<date value="2005-11"/>
		<address type="sharef:placePublished">Galway, Ireland</address>
		<field type="bibtex:index">ISWC 2005</field>
		<title type="sharef:primaryTitle">4th International Semantic Web Conference Posters</title>
	</reference>
	<reference name="amb09" src="bibtex:inproceedings" src-info="bibtex:line-7991" type="sharef:inproceedings" crossref="iswc2009">
		<names type="sharef:author">
			<person>
				<givenname>José Luis</givenname>
				<surname>Ambite</surname>
			</person>
			<person>
				<givenname>Sirish</givenname>
				<surname>Darbha</surname>
			</person>
			<person>
				<givenname>Aman</givenname>
				<surname>Goel</surname>
			</person>
			<person>
				<givenname>Craig A.</givenname>
				<surname>Knoblock</surname>
			</person>
			<person>
				<givenname>Kristina</givenname>
				<surname>Lerman</surname>
			</person>
			<person>
				<givenname>Rahul</givenname>
				<surname>Parundekar</surname>
			</person>
			<person>
				<givenname>Thomas</givenname>
				<surname>Russ</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>The work on integrating sources and services in the Semantic Web assumes that the data is either already represented in RDF or OWL or is available through a Semantic Web Service. In practice, there is a tremendous amount of data on the Web that is not available through the Semantic Web. In this paper we present an approach to automatically discover and create new Semantic Web Services. The idea behind this approach is to start with a set of known sources and the corresponding semantic descriptions and then discover similar sources, extract the source data, build semantic descriptions of the sources, and then turn them into Semantic Web Services. We implemented an end-to-end solution to this problem in a system called Deimos and evaluated the system across five different domains. The results demonstrate that the system can automatically discover, learn semantic descriptions, and build Semantic Web Services with only example sources and their descriptions as input.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1007/978-3-642-04930-9_2</identifier>
		<pages>17-32</pages>
		<title type="sharef:primaryTitle">Automatically Constructing Semantic Web Services from Online Sources</title>
		<field type="bibtex:topic">deimos[1]</field>
	</reference>
	<reference name="vol09b" src="bibtex:inproceedings" src-info="bibtex:line-8001" type="sharef:inproceedings" crossref="iswc2009">
		<names type="sharef:author">
			<person>
				<givenname>Julius</givenname>
				<surname>Volz</surname>
			</person>
			<person>
				<givenname>Christian</givenname>
				<surname>Bizer</surname>
			</person>
			<person>
				<givenname>Martin</givenname>
				<surname>Gaedke</surname>
			</person>
			<person>
				<givenname>Georgi</givenname>
				<surname>Kobilarov</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>The Web of Data is built upon two simple ideas: Employ the RDF data model to publish structured data on the Web and to create explicit data links between entities within different data sources. This paper presents the Silk Linking Framework, a toolkit for discovering and maintaining data links between Web data sources. Silk consists of three components: 1. A link discovery engine, which computes links between data sources based on a declarative specification of the conditions that entities must fulfill in order to be interlinked; 2. A tool for evaluating the generated data links in order to fine-tune the linking specification; 3. A protocol for maintaining data links between continuously changing data sources. The protocol allows data sources to exchange both linksets as well as detailed change information and enables continuous link recomputation. The interplay of all the components is demonstrated within a life science use case.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1007/978-3-642-04930-9_41</identifier>
		<pages>650-665</pages>
		<title type="sharef:primaryTitle">Discovering and Maintaining Links on the Web of Data</title>
		<field type="bibtex:topic">silk[1]</field>
	</reference>
	<reference name="har09" src="bibtex:inproceedings" src-info="bibtex:line-8011" type="sharef:inproceedings" crossref="iswc2009">
		<names type="sharef:author">
			<person>
				<givenname>Olaf</givenname>
				<surname>Hartig</surname>
			</person>
			<person>
				<givenname>Christian</givenname>
				<surname>Bizer</surname>
			</person>
			<person>
				<givenname>Johann-Christoph</givenname>
				<surname>Freytag</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>The Web of Linked Data forms a single, globally distributed dataspace. Due to the openness of this dataspace, it is not possible to know in advance all data sources that might be relevant for query answering. This openness poses a new challenge that is not addressed by traditional research on federated query processing. In this paper we present an approach to execute SPARQL queries over the Web of Linked Data. The main idea of our approach is to discover data that might be relevant for answering a query during the query execution itself. This discovery is driven by following RDF links between data sources based on URIs in the query and in partial results. The URIs are resolved over the HTTP protocol into RDF data which is continuously added to the queried dataset. This paper describes concepts and algorithms to implement our approach using an iterator-based pipeline. We introduce a formalization of the pipelining approach and show that classical iterators may cause blocking due to the latency of HTTP requests. To avoid blocking, we propose an extension of the iterator paradigm. The evaluation of our approach shows its strengths as well as the still existing challenges.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1007/978-3-642-04930-9_19</identifier>
		<pages>293-309</pages>
		<title type="sharef:primaryTitle">Executing SPARQL Queries over the Web of Linked Data</title>
		<field type="bibtex:topic">sparql[0.9]</field>
	</reference>
	<reference name="alo09" src="bibtex:inproceedings" src-info="bibtex:line-8021" type="sharef:inproceedings" crossref="iswc2009">
		<names type="sharef:author">
			<person>
				<givenname>Areeb</givenname>
				<surname>Alowisheq</surname>
			</person>
			<person>
				<givenname>David E.</givenname>
				<surname>Millard</surname>
			</person>
			<person>
				<givenname>Thanassis</givenname>
				<surname>Tiropanis</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Existing approaches to Semantic Web Services (SWS) require a domain ontology and a semantic description of the service. In the case of lightweight SWS approaches, such as SAWSDL, service description is achieved by semantically annotating existing web service interfaces. Other approaches such as OWL-S and WSMO describe services in a separate ontology. So, existing approaches separate service description from domain description, therefore increasing design efforts. We propose EXPRESS a lightweight approach to SWS that requires the domain ontology definition only. Its simplicity stems from the similarities between REST and the Semantic Web such as resource realization, self describing representations, and uniform interfaces. The semantics of a service is elicited from a resource's semantic description in the domain ontology and the semantics of the uniform interface, hence eliminating the need for ontologically describing services. We provide an example that illustrates EXPRESS and then discuss how it compares to SA-REST and WSMO.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1007/978-3-642-04930-9_59</identifier>
		<pages>941-948</pages>
		<title type="sharef:primaryTitle">EXPRESS: EXPressing REstful Semantic Services Using Domain Ontologies</title>
		<field type="bibtex:topic">sparql[0.9]</field>
	</reference>
	<reference name="iswc2009" src="bibtex:proceedings" src-info="bibtex:line-8031" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>Abraham</givenname>
				<surname>Bernstein</surname>
			</person>
			<person>
				<givenname>David R.</givenname>
				<surname>Karger</surname>
			</person>
			<person>
				<givenname>Tom</givenname>
				<surname>Heath</surname>
			</person>
			<person>
				<givenname>Lee</givenname>
				<surname>Feigenbaum</surname>
			</person>
			<person>
				<givenname>Diana</givenname>
				<surname>Maynard</surname>
			</person>
			<person>
				<givenname>Enrico</givenname>
				<surname>Motta</surname>
			</person>
			<person>
				<surname>Krishnaprasad</surname>
			</person>
			<person>
				<surname>Thirunarayan</surname>
			</person>
		</names>
		<date value="2009-10"/>
		<address type="sharef:placePublished">Chantilly, Virginia</address>
		<identifier type="sharef:doi">10.1007/978-3-642-04930-9</identifier>
		<field type="bibtex:index">ISWC 2009</field>
		<publisher>Springer-Verlag</publisher>
		<title type="sharef:seriesTitle">Lecture Notes in Computer Science</title>
		<title type="sharef:primaryTitle">8th International Semantic Web Conference</title>
		<identifier type="sharef:uri">http://iswc2009.semanticweb.org/</identifier>
		<volume>5823</volume>
	</reference>
	<reference name="lat07" src="bibtex:inproceedings" src-info="bibtex:line-8050" type="sharef:inproceedings" crossref="icsc2007">
		<names type="sharef:author">
			<person>
				<givenname>Jon</givenname>
				<surname>Lathem</surname>
			</person>
			<person>
				<givenname>Karthik</givenname>
				<surname>Gomadam</surname>
			</person>
			<person>
				<givenname>Amit P.</givenname>
				<surname>Sheth</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>The evolution of the Web 2.0 phenomenon has led to the increased adoption of the RESTful services paradigm. RESTful services often take the form of RSS/Atom feeds and AJAX based light weight services. The XML based messaging paradigm of RESTful services has made it possible to compose various services together. Such compositions of RESTful services is widely referred to as Mashups. In this paper, we outline the limitations in current approaches to creating mashups. We address these limitations by proposing a framework called as SA-REST. SA-REST adds semantics to RESTful services. Our proposed framework builds upon the original ideas in WSDL-S, our W3C submission, which was subsequently adapted for Semantic Annotation of WSDL (SAWSDL), now a W3C proposed recommendation. We demonstrate use of microformats for semantic annotation of RESTful services and then the use of such semantically enabled services with better support for interoperability for creating dynamic mashups called SMashups.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1109/ICSC.2007.94</identifier>
		<pages>469-476</pages>
		<title type="sharef:primaryTitle">SA-REST and (S)mashups: Adding Semantics to RESTful Services</title>
		<field type="bibtex:topic">sarest[1] rest[0.9]</field>
	</reference>
	<reference name="icsc2007" src="bibtex:proceedings" src-info="bibtex:line-8060" type="sharef:proceedings">
		<date value="2007-09"/>
		<address type="sharef:placePublished">Irvine, California</address>
		<field type="bibtex:index">ICSC 2007</field>
		<identifier type="sharef:isbn">0-7695-2997-6</identifier>
		<title type="sharef:primaryTitle">First IEEE International Conference on Semantic Computing (ICSC 2007)</title>
		<identifier type="sharef:uri">http://iswc2009.semanticweb.org/</identifier>
	</reference>
	<reference name="har09b" src="bibtex:inproceedings" src-info="bibtex:line-8075" type="sharef:inproceedings" crossref="swpm2009">
		<names type="sharef:author">
			<person>
				<givenname>Olaf</givenname>
				<surname>Hartig</surname>
			</person>
			<person>
				<givenname>Jun</givenname>
				<surname>Zhao</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>The Web of Data cannot be a trustworthy data source unless an approach for evaluating the quality of data on the Web is established and integrated as part of the data publication and access process. In this paper, we propose an approach of using provenance information about the data on the Web to assess their quality and trustworthiness. Our contributions include a model for Web data provenance and an assessment method that can be adapted for specific quality criteria. We demonstrate how this method can be used to evaluate the timeliness of data on the Web, to reflect how up-to-date the data is. We also propose a possible solution to deal with missing provenance information by associating certainty values with calculated quality values.</p>
			</richtext>
		</abstract>
		<title type="sharef:primaryTitle">Using Web Data Provenance for Quality Assessment</title>
		<identifier type="sharef:uri" resourceType="application/pdf">http://www.dbis.informatik.hu-berlin.de/fileadmin/research/papers/conferences/2009_swpm_hartig.pdf</identifier>
	</reference>
	<reference name="swpm2009" src="bibtex:proceedings" src-info="bibtex:line-8083" type="sharef:proceedings">
		<date value="2009-10"/>
		<address type="sharef:placePublished">Washington, D.C.</address>
		<title type="sharef:primaryTitle">First International Workshop on the Role of Semantic Web in Provenance Management</title>
		<identifier type="sharef:uri">http://wiki.knoesis.org/index.php/SWPM-2009</identifier>
	</reference>
	<reference name="dot10b" src="bibtex:inproceedings" src-info="bibtex:line-8096" type="sharef:inproceedings" crossref="springl2010">
		<names type="sharef:author">
			<person>
				<givenname>Nick</givenname>
				<surname>Doty</surname>
			</person>
			<person>
				<givenname>Erik</givenname>
				<surname>Wilde</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Security and privacy issues for Location-Based Services (LBS) and geolocation-capable applications often revolve around the idea of designing a User Interface (UI) which satisfies certain requirements so that users are informed about what the services or applications are doing, and have the ability to accept or decline. However, in a world where applications increasingly draw on a wide variety of LBS providers as the back-end, and where more and more applications are using small-screen or even screenless devices, UI-centered views of designing security and privacy are no longer sufficient. In this position paper, we describe the increasingly varied landscape of platforms with which users are faced today, and argue that the most important level to look at is the service level, so that security and privacy issues are described and negotiated in a machine-readable way, and can thus be adapted to new platforms and UIs more easily. While matters of UI and User Experience (UX) are important, we argue that they should be derived from a service-oriented view, instead of being designed and built for each platform individually.</p>
			</richtext>
		</abstract>
		<title type="sharef:primaryTitle">Geolocation Privacy and Application Platforms</title>
		<identifier type="sharef:uri">http://dret.net/netdret/publications#dot10b</identifier>
	</reference>
	<reference name="springl2010" src="bibtex:proceedings" src-info="bibtex:line-8104" type="sharef:proceedings">
		<date value="2010-11"/>
		<address type="sharef:placePublished">San Jose, California</address>
		<identifier type="sharef:isbn">978-1-4503-0435-1</identifier>
		<title type="sharef:primaryTitle">3rd ACM SIGSPATIAL International Workshop on Security and Privacy in GIS and LBS (SPRINGL) 2010</title>
		<identifier type="sharef:uri">http://springl2010.modap.org/</identifier>
	</reference>
	<reference name="voi06" src="bibtex:inproceedings" src-info="bibtex:line-8118" type="sharef:inproceedings" crossref="iemss2006">
		<names type="sharef:author">
			<person>
				<givenname>Alexey</givenname>
				<surname>Voinov</surname>
			</person>
			<person>
				<givenname>Raleigh R.</givenname>
				<surname>Hood</surname>
			</person>
			<person>
				<givenname>John D.</givenname>
				<surname>Daues</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>By copying information from sources and distributing it to new destinations we do not lose information at the sources. Nevertheless, exchange of information is still restricted by patent law, as well as by institutional, cultural and traditional hurdles that create protective barriers hindering the free flow of this valuable commodity. We believe that one of the greatest challenges we face in creating a new research paradigm will be building the community modeling and information sharing culture. How do we get engineers and scientists to put aside their traditional modes of doing business? How do we provide the incentives that will be required to make these changes happen? How do we get our colleagues to see that the benefits of sharing resources far outweigh the costs? We argue that timely sharing of data and information is not only in the best interest of the research community, but that it is also in the best interest of the scientist who is doing the sharing.</p>
			</richtext>
		</abstract>
		<title type="sharef:primaryTitle">Building a Community Modeling and Information Sharing Culture</title>
		<identifier type="sharef:uri" resourceType="application/pdf">http://www.iemss.org/summit/papers/w13/pp1.pdf</identifier>
	</reference>
	<reference name="iemss2006" src="bibtex:proceedings" src-info="bibtex:line-8126" type="sharef:proceedings">
		<date value="2006-07"/>
		<address type="sharef:placePublished">Burlington, Vermont</address>
		<title type="sharef:primaryTitle">3rd Biennial meeting of the International Environmental Modelling and Software Society</title>
		<identifier type="sharef:uri">http://www.iemss.org/summit/</identifier>
	</reference>
	<reference name="ree05" src="bibtex:inproceedings" src-info="bibtex:line-8139" type="sharef:inproceedings" crossref="opened2005">
		<names type="sharef:author">
			<person>
				<givenname>Ross</givenname>
				<surname>Reedstrom</surname>
			</person>
			<person>
				<givenname>Brent</givenname>
				<surname>Hendricks</surname>
			</person>
			<person>
				<givenname>Richard</givenname>
				<surname>Baraniuk</surname>
			</person>
		</names>
		<title type="sharef:primaryTitle">Growing a Reusable Repository: Keeping the Content Meaningful</title>
		<identifier type="sharef:uri">http://cosl.usu.edu/conferences/opened2005/docs/opened2005-proceedings.pdf#page=134</identifier>
	</reference>
	<reference name="opened2005" src="bibtex:proceedings" src-info="bibtex:line-8146" type="sharef:proceedings">
		<date value="2005-09"/>
		<address type="sharef:placePublished">Logan, Utah</address>
		<title type="sharef:primaryTitle">OpenEd2005 Conference</title>
		<identifier type="sharef:uri">http://cosl.usu.edu/conferences/opened2005/</identifier>
	</reference>
	<reference name="lai99" src="bibtex:inproceedings" src-info="bibtex:line-8159" type="sharef:inproceedings" crossref="acsac99">
		<names type="sharef:author">
			<person>
				<givenname>Charlie</givenname>
				<surname>Lai</surname>
			</person>
			<person>
				<givenname>Li</givenname>
				<surname>Gong</surname>
			</person>
			<person>
				<givenname>Larry</givenname>
				<surname>Koved</surname>
			</person>
			<person>
				<givenname>Anthony</givenname>
				<surname>Nadalin</surname>
			</person>
			<person>
				<givenname>Roland</givenname>
				<surname>Schemers</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Java security technology originally focused on creating a safe environment in which to run potentially untrusted code downloaded from the public network. With the latest release of the Java Platform (the Java 2 Software Development Kit, v 1.2), fine-grained access controls can be placed upon critical resources with regard to the identity of the running applets and applications, which are distinguished by where the code came from and who signed it. However, the Java platform still lacks the means to enforce access controls based on the identity of the user who runs the code. In this paper, we describe the design and implementation of the Java Authentication and Authorization Service (JAAS), a framework and programming interface that augments the Java platform with both user-based authentication and access control capabilities.</p>
			</richtext>
		</abstract>
		<pages>285-290</pages>
		<title type="sharef:primaryTitle">User Authentication and Authorization in the Java Platform</title>
		<field type="bibtex:topic">jaas[0.9]</field>
		<identifier type="sharef:uri">http://ieeexplore.ieee.org/xpl/abs_free.jsp?arNumber=816038</identifier>
		<identifier type="sharef:uri" resourceType="application/pdf">http://citeseer.ist.psu.edu/cache/papers/cs/16515/http:zSzzSzjava.sun.comzSzsecurityzSzjaaszSzdoczSzacsac.pdf/lai99user.pdf</identifier>
	</reference>
	<reference name="acsac99" src="bibtex:proceedings" src-info="bibtex:line-8170" type="sharef:proceedings">
		<date value="1999-12"/>
		<address type="sharef:placePublished">Scottsdale, Arizona</address>
		<identifier type="sharef:doi">10.1109/CSAC.1999.816038</identifier>
		<identifier type="sharef:isbn">0-7695-0346-2</identifier>
		<publisher>IEEE Computer Society Press</publisher>
		<title type="sharef:primaryTitle">15th Annual Computer Security Applications Conference</title>
		<identifier type="sharef:uri" resourceType="text/html">http://www.informatik.uni-trier.de/~ley/db/conf/acsac/acsac1999.html</identifier>
	</reference>
	<reference name="has08" src="bibtex:inproceedings" src-info="bibtex:line-8186" type="sharef:inproceedings" crossref="acsac2008">
		<names type="sharef:author">
			<person>
				<givenname>Ragib</givenname>
				<surname>Hasan</surname>
			</person>
			<person>
				<givenname>Marianne</givenname>
				<surname>Winslett</surname>
			</person>
			<person>
				<givenname>Richard</givenname>
				<surname>Conlan</surname>
			</person>
			<person>
				<givenname>Brian</givenname>
				<surname>Slesinsky</surname>
			</person>
			<person>
				<givenname>Nandakumar</givenname>
				<surname>Ramani</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Mashups have emerged as a Web 2.0 phenomenon, connecting disjoint applications together to provide unified services. However, scalable access control for mashups is difficult. To enable a mashup to gather data from legacy applications and services, users must give the mashup their login names and passwords for those services. This all-or-nothing approach violates the principle of least privilege and leaves users vulnerable to misuse of their credentials by malicious mashups. In this paper, we introduce delegation permits — a stateless approach to access rights delegation in mashups — and describe our complete implementation of a permit-based authorization delegation service. Our protocol and implementation enable fine grained, flexible, and stateless access control and authorization for distributed delegated authorization in mashups, while minimizing attackers' ability to capture and exploit users' authentication credentials.</p>
			</richtext>
		</abstract>
		<title type="sharef:primaryTitle">Please Permit Me: Stateless Delegated Authorization in Mashups</title>
		<field type="bibtex:topic">openid[0.7] oauth[0.7] authsub[0.7]</field>
		<identifier type="sharef:uri" resourceType="application/pdf">http://ragibhasan.com/publications/papers/hasan-acsac2009mashup.pdf</identifier>
	</reference>
	<reference name="acsac2008" src="bibtex:proceedings" src-info="bibtex:line-8195" type="sharef:proceedings">
		<date value="2008-12"/>
		<address type="sharef:placePublished">Anaheim, California</address>
		<publisher>IEEE Computer Society Press</publisher>
		<title type="sharef:primaryTitle">2008 Annual Computer Security Applications Conference</title>
		<identifier type="sharef:uri" resourceType="text/html">http://www.informatik.uni-trier.de/~ley/db/conf/acsac/acsac2008.html</identifier>
	</reference>
	<reference name="hag04" src="bibtex:inproceedings" src-info="bibtex:line-8209" type="sharef:inproceedings" crossref="bspc04">
		<names type="sharef:author">
			<person>
				<givenname>Amir</givenname>
				<surname>Haghighat</surname>
			</person>
			<person>
				<givenname>Cristina Videira</givenname>
				<surname>Lopes</surname>
			</person>
			<person>
				<givenname>Tony</givenname>
				<surname>Givargis</surname>
			</person>
			<person>
				<givenname>Atri</givenname>
				<surname>Mandal</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>We describe the Location-Aware Web System (LAWS), a location-aware system built on top of the Hypertext Transfer Protocol (HTTP). LAWS adds location-dependent virtual browsing experience to the users who are navigating in the physical space with any web browser-enabled roaming device (i.e.: PDA, Smartphone). The distinct characteristic about LAWS is its high degree of modularity and flexibility. By embedding the location information in HTTP requests, we can add location to the system while using existing browsers and existing web servers. This way, there is also, to some degree, independence between the overall system and the positioning system. LAWS can be used in a number of different environments using different positioning systems, and serving different purposes.</p>
			</richtext>
		</abstract>
		<title type="sharef:primaryTitle">Location-Aware Web System</title>
		<identifier type="sharef:uri" resourceType="application/pdf">http://givargis.ics.uci.edu/pubs/W1.pdf</identifier>
		<identifier type="sharef:uri" resourceType="application/pdf">http://www.ics.uci.edu/~lopes/bspc04-documents/HaghighatLopes.pdf</identifier>
	</reference>
	<reference name="bspc04" src="bibtex:proceedings" src-info="bibtex:line-8218" type="sharef:proceedings">
		<date value="2004-10"/>
		<address type="sharef:placePublished">Vancouver, Canada</address>
		<field type="bibtex:index">BSCP 2004</field>
		<title type="sharef:primaryTitle">Workshop on Building Software for Pervasive Computing at OOPSLA'04</title>
		<identifier type="sharef:uri" resourceType="text/html">http://www.ics.uci.edu/~lopes/bspc04.html</identifier>
	</reference>
	<reference name="wil08p" src="bibtex:inproceedings" src-info="bibtex:line-8232" type="sharef:inproceedings" crossref="hcir2008">
		<names type="sharef:author">
			<person>
				<givenname>Erik</givenname>
				<surname>Wilde</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>The navigation structure of Web sites can be regarded as metadata that can be used for interesting applications in User Interface (UI) design and Human-Computer Interaction (HCI), as well as for Information Retrieval (IR) tasks. However, there currently is no established format for site metadata, which makes it hard for Web sites to publish their structure in a machine-readable way, which could then be used by HCI and/or IR applications. We propose a model and a format for site metadata that is built on top of an existing format and thus could be deployed with little overhead by publishers as well as consumers. Making site metadata available as machine-readable data can be used for improving user interfaces (informing user agents about the context of the page they are displaying) and better information retrieval (allowing search engines to use sitemap information for better ranking and display of the results).</p>
			</richtext>
		</abstract>
		<title type="sharef:primaryTitle">Site Metadata on the Web</title>
		<identifier type="sharef:uri">http://dret.net/netdret/publications#wil08p</identifier>
	</reference>
	<reference name="hcir2008" src="bibtex:proceedings" src-info="bibtex:line-8240" type="sharef:proceedings">
		<date value="2008-10"/>
		<address type="sharef:placePublished">Redmond, Washington</address>
		<field type="bibtex:index">HCIR 2008</field>
		<title type="sharef:primaryTitle">Second Workshop on Human-Computer Interaction and Information Retrieval</title>
		<identifier type="sharef:uri">http://research.microsoft.com/~ryenw/hcir2008/</identifier>
	</reference>
	<reference name="bro04" src="bibtex:inproceedings" src-info="bibtex:line-8254" type="sharef:inproceedings" crossref="sempgrid04">
		<names type="sharef:author">
			<person>
				<givenname>Jeen</givenname>
				<surname>Broekstra</surname>
			</person>
			<person>
				<givenname>Marc</givenname>
				<surname>Ehrig</surname>
			</person>
			<person>
				<givenname>Peter</givenname>
				<surname>Haase</surname>
			</person>
			<person>
				<givenname>Frank</givenname>
				<surname link="van">Harmelen</surname>
			</person>
			<person>
				<givenname>Maarten</givenname>
				<surname>Menken</surname>
			</person>
			<person>
				<givenname>Peter</givenname>
				<surname>Mika</surname>
			</person>
			<person>
				<givenname>Björn</givenname>
				<surname>Schnizler</surname>
			</person>
			<person>
				<givenname>Ronny</givenname>
				<surname>Siebes</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>This paper describes the design and implementation of Bibster, a Peer-to-Peer system for exchanging bibliographic data among Computer Science researchers. Bibster exploits ontologies in data-storage, query formulation, query-routing and answer presentation: When bibliographic entries are made available for use in Bibster, they are structured and classified according to two different ontologies. This ontological structure is then exploited to help user formulate their queries. Subsequently, the ontologies are used to improve query routing across the Peer-to-Peer network. Finally, the ontologies are used to post-process the returned answers in order to do duplicate detection. The paper describes each of these ontology-based aspects of Bibster. Bibster is fully implemented on top of the JXTA platform, and is about to be rolled out for field testing.</p>
			</richtext>
		</abstract>
		<title type="sharef:primaryTitle">Bibster — A Semantics-Based Bibliographic Peer-to-Peer System</title>
		<field type="bibtex:topic">bibster[1]</field>
		<identifier type="sharef:uri" resourceType="text/html">http://www.cs.vu.nl/~frankh/abstracts/SEMPGRID04.html</identifier>
		<identifier type="sharef:uri" resourceType="application/pdf">http://www.isi.edu/~hongsuda/SemPGRID04/proceedings/Haase-sempgrid04.pdf</identifier>
	</reference>
	<reference name="sempgrid04" src="bibtex:proceedings" src-info="bibtex:line-8265" type="sharef:proceedings">
		<date value="2004-05"/>
		<address type="sharef:placePublished">New York, NY</address>
		<field type="bibtex:index">SEMPGRID 2004</field>
		<title type="sharef:primaryTitle">Second Workshop on Semantics in Peer-to-Peer and Grid Computing</title>
		<identifier type="sharef:uri">http://www.isi.edu/~hongsuda/SemPGRID04/</identifier>
	</reference>
	<reference name="nec06" src="bibtex:inproceedings" src-info="bibtex:line-8279" type="sharef:inproceedings" crossref="dateso2006">
		<names type="sharef:author">
			<person>
				<givenname>Martin</givenname>
				<surname>Nečaský</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Recently XML is the standard format used for the exchange of data between information systems and is also frequently applied as a logical database model. If we use XML as a logical database model we need a conceptual model for the description of its semantics. However, XML as a logical database model has some special characteristics which makes existing conceptual models as E-R or UML unsuitable. In this paper, the current approaches to the conceptual modeling of XML data are described in an uniform style. A list of requirements for XML conceptual models is presented and described approaches are compared on the base of the requirements.</p>
			</richtext>
		</abstract>
		<title type="sharef:primaryTitle">Conceptual Modeling for XML: A Survey</title>
		<field type="bibtex:topic">xml[0.8]</field>
		<identifier type="sharef:uri" resourceType="application/pdf">http://ftp.informatik.rwth-aachen.de/Publications/CEUR-WS/Vol-176/paper7.pdf</identifier>
	</reference>
	<reference name="dateso2006" src="bibtex:proceedings" src-info="bibtex:line-8289" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>Václav</givenname>
				<surname>Snášel</surname>
			</person>
			<person>
				<givenname>Karel</givenname>
				<surname>Richta</surname>
			</person>
			<person>
				<givenname>Jaroslav</givenname>
				<surname>Pokorný</surname>
			</person>
		</names>
		<date value="2006-04"/>
		<address type="sharef:placePublished">Desná — Černá Říčka, Czech Republic</address>
		<field type="bibtex:index">DATESO 2006</field>
		<identifier type="sharef:isbn">80-248-1025-5</identifier>
		<title type="sharef:primaryTitle">DATESO 2006 Annual International Workshop on Databases, Texts, Specifications, and Objects</title>
		<identifier type="sharef:uri">http://www.cs.vsb.cz/dateso/2006/</identifier>
		<identifier type="sharef:uri">http://www.ceur-ws.org/Vol-176/</identifier>
	</reference>
	<reference name="dem02" src="bibtex:inproceedings" src-info="bibtex:line-8306" type="sharef:inproceedings" crossref="coopis02">
		<names type="sharef:author">
			<person>
				<givenname>Jan</givenname>
				<surname>Demey</surname>
			</person>
			<person>
				<givenname>Mustafa</givenname>
				<surname>Jarrar</surname>
			</person>
			<person>
				<givenname>Robert</givenname>
				<surname>Meersman</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>The Internet creates a strong demand for standardized exchange not only of data itself but especially of data semantics, as this same internet increasingly becomes the carrier of e-business activity (e.g. using web services). One way to achieve this is in the form of communicating "rich" conceptual schemas. In this paper we adopt the well-known CM technique of ORM, which has a rich complement of business rule specification, and develop ORM-ML, an XML-based markup language for ORM. Clearly domain modeling of this kind will be closely related to work on so-called ontologies and we will briefly discuss the analogies and differences, introducing methodological patterns for designing distributed business models. Since ORM schemas are typically saved as graphical files, we designed a textual representation as a marked-up document in ORM-ML so we can save these ORM schemas in a more machine exchangeable way that suits networked environments. Moreover, we can now write style sheets to convert such schemas into another syntax, e.g. pseudo natural language, a given rule engine's language, first order logic.</p>
			</richtext>
		</abstract>
		<pages>19-35</pages>
		<title type="sharef:primaryTitle">A Conceptual Markup Language That Supports Interoperability between Business Rule Modeling Systems</title>
		<identifier type="sharef:uri">http://www.springerlink.com/link.asp?id=dc3fdjcwtcwj6dgu</identifier>
	</reference>
	<reference name="coopis02" src="bibtex:proceedings" src-info="bibtex:line-8315" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>Robert</givenname>
				<surname>Meersman</surname>
			</person>
			<person>
				<givenname>Zahir</givenname>
				<surname>Tari</surname>
			</person>
		</names>
		<date value="2002-10"/>
		<address type="sharef:placePublished">Irvine, California</address>
		<field type="bibtex:index">COOPIS 2002</field>
		<identifier type="sharef:isbn">3-540-00106-9</identifier>
		<publisher>Springer-Verlag</publisher>
		<title type="sharef:seriesTitle">Lecture Notes in Computer Science</title>
		<title type="sharef:primaryTitle">2002 Confederated International Conferences DOA, CoopIS and ODBASE</title>
		<identifier type="sharef:uri" resourceType="text/html">http://www.informatik.uni-trier.de/~ley/db/conf/coopis/coopis2002.html</identifier>
		<volume>2519</volume>
	</reference>
	<reference name="sto04" src="bibtex:inproceedings" src-info="bibtex:line-8334" type="sharef:inproceedings" crossref="coopis04">
		<names type="sharef:author">
			<person>
				<givenname>Ljiljana</givenname>
				<surname>Stojanovic</surname>
			</person>
			<person>
				<givenname>Andreas</givenname>
				<surname>Abecker</surname>
			</person>
			<person>
				<givenname>Nenad</givenname>
				<surname>Stojanovic</surname>
			</person>
			<person>
				<givenname>Rudi</givenname>
				<surname>Studer</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>The increasing complexity of E-Government services demands a correspondingly larger effort for management. Today, many system management tasks are often performed manually. This can be time consuming and error-prone. Moreover, it requires a growing number of highly skilled personnel, making E-Government systems costly. In this paper, we show how the usage of semantic technologies for describing E-Government services can improve the management of changes. We have extended our previous work in ontology evolution, in order to take into account the specificities of ontologies that are used for the description of E-Government services. Even though we use the E-Government domain as an example, the approach is general enough to be applied in other domains.</p>
			</richtext>
		</abstract>
		<pages>1080-1097</pages>
		<title type="sharef:primaryTitle">On Managing Changes in the ontology-based E-Government</title>
		<identifier type="sharef:uri">http://www.fzi.de/wim/eng/publikationen.php?id=1231</identifier>
		<identifier type="sharef:uri" resourceType="application/pdf">http://europa.eu.int/information_society/programmes/egov_rd/doc/research/ontology.pdf</identifier>
	</reference>
	<reference name="coopis04" src="bibtex:proceedings" src-info="bibtex:line-8344" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>Robert</givenname>
				<surname>Meersman</surname>
			</person>
			<person>
				<givenname>Zahir</givenname>
				<surname>Tari</surname>
			</person>
		</names>
		<date value="2004-10"/>
		<address type="sharef:placePublished">Agia Napa, Cyprus</address>
		<field type="bibtex:index">COOPIS 2004</field>
		<identifier type="sharef:isbn">3-540-23662-7</identifier>
		<publisher>Springer-Verlag</publisher>
		<title type="sharef:seriesTitle">Lecture Notes in Computer Science</title>
		<title type="sharef:primaryTitle">2004 CoopIS, DOA, and ODBASE, OTM Confederated International Conferences</title>
		<identifier type="sharef:uri" resourceType="text/html">http://www.informatik.uni-trier.de/~ley/db/conf/coopis/coopis2004-2.html</identifier>
		<volume>3291</volume>
	</reference>
	<reference name="kil96" src="bibtex:inproceedings" src-info="bibtex:line-8363" type="sharef:inproceedings" crossref="podp96">
		<names type="sharef:author">
			<person>
				<givenname>Pekka</givenname>
				<surname>Kilpeläinen</surname>
			</person>
			<person>
				<givenname>Derick</givenname>
				<surname>Wood</surname>
			</person>
		</names>
		<pages>39-49</pages>
		<title type="sharef:primaryTitle">SGML and Exceptions</title>
		<field type="bibtex:topic">sgml[0.7]</field>
		<identifier type="sharef:uri">http://portal.acm.org/citation.cfm?id=670474</identifier>
	</reference>
	<reference name="podp96" src="bibtex:proceedings" src-info="bibtex:line-8372" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>Charles K.</givenname>
				<surname>Nicholas</surname>
			</person>
			<person>
				<givenname>Derick</givenname>
				<surname>Wood</surname>
			</person>
		</names>
		<date value="1996-09"/>
		<address type="sharef:placePublished">Palo Alto, California</address>
		<field type="bibtex:index">PODP 1996</field>
		<identifier type="sharef:isbn">3-540-63620-X</identifier>
		<publisher>Springer-Verlag</publisher>
		<title type="sharef:seriesTitle">Lecture Notes in Computer Science</title>
		<title type="sharef:primaryTitle">Third International Workshop on Principles of Document Processing</title>
		<identifier type="sharef:uri" resourceType="text/html">http://www.informatik.uni-trier.de/~ley/db/conf/podp/podp96.html</identifier>
		<volume>1293</volume>
	</reference>
	<reference name="hid04" src="bibtex:inproceedings" src-info="bibtex:line-8391" type="sharef:inproceedings" crossref="xsym2004">
		<names type="sharef:author">
			<person>
				<givenname>Jan</givenname>
				<surname>Hidders</surname>
			</person>
			<person>
				<givenname>Jan</givenname>
				<surname>Paredaens</surname>
			</person>
			<person>
				<givenname>Roel</givenname>
				<surname>Vercammen</surname>
			</person>
			<person>
				<givenname>Serge</givenname>
				<surname>Demeyer</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>We give a light-weight but formal introduction to XQuery by defining a sublanguage of XQuery. We ignore typing, and don't consider namespaces, comments, programming instructions, and entities. To avoid confusion we call our version LiXQuery (Light XQuery). LiXQuery is fully downwards compatible with XQuery. Its syntax and its semantics are far less complex than that of XQuery, but the typical expressions of XQuery are included in LiXQuery. We claim that LiXQuery is an elegant and simple sublanguage of XQuery that can be used for educational and research purposes. We give the complete syntax and the formal semantics of LiXQuery.</p>
			</richtext>
		</abstract>
		<pages>5-20</pages>
		<title type="sharef:primaryTitle">A Light but Formal Introduction to XQuery</title>
		<field type="bibtex:topic">xquery[0.9]</field>
		<identifier type="sharef:uri">http://springerlink.metapress.com/openurl.asp?genre=article&amp;issn=0302-9743&amp;volume=3186&amp;spage=2</identifier>
	</reference>
	<reference name="man04" src="bibtex:inproceedings" src-info="bibtex:line-8401" type="sharef:inproceedings" crossref="xsym2004">
		<names type="sharef:author">
			<person>
				<givenname>Murali</givenname>
				<surname>Mani</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>In the last few years, XML has been widely used as a logical data model, and several database applications are modeled in XML. To model a database application in XML, we should first come up with a conceptual design for representing the application requirements, and then translate this conceptual design to XML. Existing conceptual models like the ER (Entity Relationship) model, UML and ORM do not have modeling capabilities to represent main features provided by XML, such as union types. In this work, we extend the ER model with additional features; we call our conceptual model as EReX (ER extended for XML). Translating an EReX design to XML enables us to make use of the different features provided by XML. Our approach further enables us to study a fundamental problem facing XML database community today: what structural and constraint specification should be provided in XML so that any generic database application can be modeled in XML.</p>
			</richtext>
		</abstract>
		<pages>128-142</pages>
		<title type="sharef:primaryTitle">EReX: A Conceptual Model for XML</title>
		<field type="bibtex:topic">erex[0.9]</field>
		<identifier type="sharef:uri">http://www.springerlink.com/link.asp?id=2q5t7r301and7g6u</identifier>
		<identifier type="sharef:uri" resourceType="application/pdf">http://www.cs.wpi.edu/~mmani/publications/modeling.pdf</identifier>
	</reference>
	<reference name="xsym2004" src="bibtex:proceedings" src-info="bibtex:line-8412" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>Zohra</givenname>
				<surname>Bellahsene</surname>
			</person>
			<person>
				<givenname>Tova</givenname>
				<surname>Milo</surname>
			</person>
			<person>
				<givenname>Michael</givenname>
				<surname>Rys</surname>
			</person>
			<person>
				<givenname>Dan</givenname>
				<surname>Suciu</surname>
			</person>
			<person>
				<givenname>Rainer</givenname>
				<surname>Unland</surname>
			</person>
		</names>
		<date value="2004-08"/>
		<address type="sharef:placePublished">Toronto, Canada</address>
		<field type="bibtex:index">XSym 2004</field>
		<identifier type="sharef:isbn">3-540-22969-8</identifier>
		<publisher>Springer-Verlag</publisher>
		<title type="sharef:seriesTitle">Lecture Notes in Computer Science</title>
		<title type="sharef:primaryTitle">Second International XML Database Symposium</title>
		<identifier type="sharef:uri">http://www.xsym.org/04/</identifier>
		<identifier type="sharef:uri" resourceType="text/html">http://www.informatik.uni-trier.de/~ley/db/conf/xsym/xsym2004.html</identifier>
		<volume>3186</volume>
	</reference>
	<reference name="mel03" src="bibtex:inproceedings" src-info="bibtex:line-8432" type="sharef:inproceedings" crossref="xml2003berlin">
		<names type="sharef:author">
			<person>
				<givenname>Ingo</givenname>
				<surname>Melzer</surname>
			</person>
			<person>
				<givenname>Mario</givenname>
				<surname>Jeckle</surname>
			</person>
		</names>
		<pages>292-304</pages>
		<title type="sharef:primaryTitle">A Signing Proxy for Web Services Security</title>
		<field type="bibtex:topic">soap[0.7]</field>
	</reference>
	<reference name="men03" src="bibtex:inproceedings" src-info="bibtex:line-8440" type="sharef:inproceedings" crossref="xml2003berlin">
		<names type="sharef:author">
			<person>
				<givenname>Jan</givenname>
				<surname>Mendling</surname>
			</person>
			<person>
				<givenname>Martin</givenname>
				<surname>Müller</surname>
			</person>
		</names>
		<pages>305-316</pages>
		<title type="sharef:primaryTitle">A Comparison of BPML and BPEL4WS</title>
		<field type="bibtex:topic">bpml[0.8] bpel4ws[0.8]</field>
	</reference>
	<reference name="xml2003berlin" src="bibtex:proceedings" src-info="bibtex:line-8448" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>Robert</givenname>
				<surname>Tolksdorf</surname>
			</person>
			<person>
				<givenname>Rainer</givenname>
				<surname>Eckstein</surname>
			</person>
		</names>
		<date value="2003-10"/>
		<address type="sharef:placePublished">Berlin, Germany</address>
		<identifier type="sharef:isbn">3885791161</identifier>
		<title type="sharef:primaryTitle">Berliner XML Tage 2003</title>
	</reference>
	<reference name="rob00" src="bibtex:inproceedings" src-info="bibtex:line-8462" type="sharef:inproceedings" crossref="xmleu2000">
		<names type="sharef:author">
			<person>
				<givenname>Jonathan</givenname>
				<surname>Robie</surname>
			</person>
			<person>
				<givenname>Donald D.</givenname>
				<surname>Chamberlin</surname>
			</person>
			<person>
				<givenname>Daniela</givenname>
				<surname>Florescu</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>XML is an extremely versatile markup language, capable of labeling the information content of diverse data sources including structured and semi-structured documents, relational databases, and object repositories. A query language of similar versatility is needed to realize the potential of XML as a universal medium for data interchange. Most existing proposals for XML query languages are robust for particular types of data sources but weak for other types. In this paper, the authors combine features from several sources to propose a new query language called Quilt, which is designed to be broadly applicable across all types of XML data sources.</p>
			</richtext>
		</abstract>
		<title type="sharef:primaryTitle">Quilt: An XML Query Language</title>
		<field type="bibtex:topic">quilt[1]</field>
		<identifier type="sharef:uri" resourceType="text/html">http://www.gca.org/papers/xmleurope2000/papers/s08-01.html</identifier>
	</reference>
	<reference name="lea00" src="bibtex:inproceedings" src-info="bibtex:line-8471" type="sharef:inproceedings" crossref="xmleu2000">
		<names type="sharef:author">
			<person>
				<givenname>Karen</givenname>
				<surname>Lease</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>This talk compares several mechanisms for managing compound documents, including standard external parsed entities, SGML subdocuments, and the recent W3C propositions XInclude and XLink. Based on a detailed discussion of the strengths and weaknesses of each solution, it presents a compromise proposal which leverages existing XML tools.</p>
			</richtext>
		</abstract>
		<title type="sharef:primaryTitle">External Entities and Alternatives</title>
		<field type="bibtex:topic">xlink[0.7] xinclude[0.7]</field>
		<identifier type="sharef:uri" resourceType="text/html">http://www.gca.org/papers/xmleurope2000/papers/s14-02.html</identifier>
	</reference>
	<reference name="leg00" src="bibtex:inproceedings" src-info="bibtex:line-8480" type="sharef:inproceedings" crossref="xmleu2000">
		<names type="sharef:author">
			<person>
				<givenname>Benedicte</givenname>
				<surname>Le Grand</surname>
			</person>
			<person>
				<givenname>Michel</givenname>
				<surname>Soto</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Topic maps — the new ISO standard ISO-IEC 13250 — provide a bridge between the domains of knowledge representation and information management. Topics and topic associations build a structured semantic link network above information resources. Our research aims at visualizing this semantic layer efficiently, which is a critical issue as topic maps may contain millions of topics and associations. This paper is divided into 3 parts. First, we depict briefly basic topic maps concepts. Then, we review a few graph visualization techniques. Finally, we describe the visualization tool we developed at the Laboratoire d'Informatique de Paris 6 and study how this tool may be used — and enhanced — for topic maps visualization.</p>
			</richtext>
		</abstract>
		<title type="sharef:primaryTitle">Topic Maps Visualization</title>
		<field type="bibtex:topic">topicmaps[0.8]</field>
		<identifier type="sharef:uri" resourceType="text/html">http://www.gca.org/papers/xmleurope2000/papers/s29-03.html</identifier>
	</reference>
	<reference name="nov00" src="bibtex:inproceedings" src-info="bibtex:line-8489" type="sharef:inproceedings" crossref="xmleu2000">
		<names type="sharef:author">
			<person>
				<givenname>Anguel</givenname>
				<surname>Novoselsky</surname>
			</person>
			<person>
				<givenname>K.</givenname>
				<surname>Karun</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>The emergence and popularity of XML helps facilitate the development and integration of business and application semantics. However, each enterprise defines their own data elements to better communicate the "meaning" of their data. Translation will therefore be key for interoperability. XSL standards for transformation are sufficient to allow exchange between business vocabularies. Currently there are many XSLT engine implementations. In this paper, we present a novel approach for implementing transformations using XSL. We describe a XSLT Virtual Machine (XSLTVM). XSLTVM is the software implementation of a "CPU" designed to run compiled XSLT code. A concept of virtual machine assumes a compiler compiling XSLT stylesheets to sequence of byte codes or machine instructions for the "XSLT CPU". This approach clearly separates compile-time from run-time computations and specifies an uniform way of data exchange between instructions by defining a common interface areas like stack or pipeline for example. The separation line between compile-time and run-time computations depends on the level of machine instructions. Splitting a heterogeneous, high-level instruction into number of atomic, low-level instructions exposes some run-time checks and allows compiler to take care of them. For example, a general CMP instruction checks operand types at run-time. If it is replaced with few type specific CMPs then compiler checks operand types at compile-time and generates appropriate type casting instructions if needed.</p>
			</richtext>
		</abstract>
		<field type="bibtex:index">XSLTVM</field>
		<title type="sharef:primaryTitle">XSLTVM — An XSLT Virtual Machine</title>
		<field type="bibtex:topic">xslt1[0.8]</field>
		<identifier type="sharef:uri" resourceType="text/html">http://www.gca.org/papers/xmleurope2000/papers/s35-03.html</identifier>
	</reference>
	<reference name="xmleu2000" src="bibtex:proceedings" src-info="bibtex:line-8499" type="sharef:proceedings">
		<date value="2000-06"/>
		<address type="sharef:placePublished">Paris, France</address>
		<field type="bibtex:index">XML Europe 2000</field>
		<field type="bibtex:key">XML Europe 2000</field>
		<title type="sharef:primaryTitle">XML Europe 2000</title>
		<identifier type="sharef:uri">http://www.gca.org/papers/xmleurope2000</identifier>
	</reference>
	<reference name="duh01" src="bibtex:inproceedings" src-info="bibtex:line-8514" type="sharef:inproceedings" crossref="xmleu2001">
		<names type="sharef:author">
			<person>
				<givenname>Anthony J.</givenname>
				<surname>Duhig</surname>
			</person>
		</names>
		<title type="sharef:primaryTitle">Separating Links from Content using XML, XLink and XPointer</title>
		<field type="bibtex:topic">xlink[0.8] xpointer[0.8]</field>
		<identifier type="sharef:uri" resourceType="text/html">http://www.gca.org/papers/xmleurope2001/papers/html/s16-2.html</identifier>
	</reference>
	<reference name="ram01" src="bibtex:inproceedings" src-info="bibtex:line-8522" type="sharef:inproceedings" crossref="xmleu2001">
		<names type="sharef:author">
			<person>
				<givenname>José Carlos Leite</givenname>
				<surname>Ramalho</surname>
			</person>
		</names>
		<title type="sharef:primaryTitle">Constraining Content: Specification and Processing</title>
		<field type="bibtex:topic">xcsl[0.9]</field>
		<identifier type="sharef:uri" resourceType="text/html">http://www.gca.org/papers/xmleurope2001/papers/html/s22-3.html</identifier>
	</reference>
	<reference name="xmleu2001" src="bibtex:proceedings" src-info="bibtex:line-8530" type="sharef:proceedings">
		<date value="2001-05"/>
		<address type="sharef:placePublished">Berlin, Germany</address>
		<field type="bibtex:index">XML Europe 2001</field>
		<field type="bibtex:key">XML Europe 2001</field>
		<title type="sharef:primaryTitle">XML Europe 2001</title>
		<identifier type="sharef:uri" resourceType="text/html">http://www.gca.org/papers/xmleurope2001/index.html</identifier>
	</reference>
	<reference name="rag06" src="bibtex:inproceedings" src-info="bibtex:line-8545" type="sharef:inproceedings" crossref="xtech2006">
		<names type="sharef:author">
			<person>
				<givenname>Dave</givenname>
				<surname>Raggett</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>HTML Slidy is an open source Web-based alternative to Microsoft PowerPoint based upon XHTML, CSS and JavaScript, and which runs on a wide variety of browsers. I will introduce Slidy, and describe the challenges faced in developing an accessible cross platform browser-based editor for slide presentations.</p>
			</richtext>
		</abstract>
		<title type="sharef:primaryTitle">Slidy — A Web Based Alternative to Microsoft PowerPoint</title>
		<field type="bibtex:topic">slidy[1]</field>
		<identifier type="sharef:uri">http://xtech06.usefulinc.com/schedule/paper/1</identifier>
	</reference>
	<reference name="xtech2006" src="bibtex:proceedings" src-info="bibtex:line-8554" type="sharef:proceedings">
		<date value="2006-05"/>
		<address type="sharef:placePublished">Amsterdam, Netherlands</address>
		<field type="bibtex:key">XTech 2006</field>
		<title type="sharef:primaryTitle">XTech 2006</title>
		<identifier type="sharef:uri">http://xtech06.usefulinc.com/schedule</identifier>
	</reference>
	<reference name="wil07h" src="bibtex:inproceedings" src-info="bibtex:line-8568" type="sharef:inproceedings" crossref="xtech2007">
		<names type="sharef:author">
			<person>
				<givenname>Felix</givenname>
				<surname>Michel</surname>
			</person>
			<person>
				<givenname>Erik</givenname>
				<surname>Wilde</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>The family of upcoming XML technologies, consisting of XPath 2.0, XSLT 2.0, and XQuery, no longer operates only on the Infoset, but also utilize schema information. Today, this schema information is added to the Infoset during schema-validation and commonly is referred to as PSVI contributions (PSVI for "Post-Validation Schema Infoset"). Utilizing schema information is promising, for XML Schema allows to describe relationships between structures in an expressive, semantically relevant way, e.g. through type derivation and substitution groups. This structural information can become valuable meta-data when processing instances that comply to the respective Schema. However, only a small fraction of this schema information is accessible with the aforementioned technologies. There are various reasons for this: Some schema information such as where wildcards can occur is not exposed at all, and other components (e.g. types) are only represented by QNames, lacking any possibilities to further navigate the schema information. Secondly, the PSVI specification remains vague with respect to the data model. And finally, the present data model of XML Schema is not appropriate for some application contexts. The existence of differing data models for XML Schema (e.g. in programming APIs for XML Schema) is evidence for the fact that the abstract data model as defined in the recommendation does not rule out the need for other data model perspectives. In fact, the abstract data model and its incarnations (namely the normative XML syntax) may be good for defining schemas, but it proves to be less appropriate for exploiting the structural information. Features that are convenient for definition (such as named groups and nested model groups) turn out to be problematic for retrieval and navigation, the most important ways of using the structural information. We propose an alternative data model perspective that represents the schema information in a way that meets the needs of certain classes of applications better. These applications have in common read-only access to schema information, an instance-driven perspective, the need for schema inspection at runtime, and possibly only a local scope. Our data model uses what we call "occurrences" instead of the "particles" in the normative abstract data model, and it expands what we (deliberately) consider to be notational shorthands (like occurrence constraints and named groups). Furthermore, we index all occurrences (even of the same element), as it is done in "marked expressions" in regular language theory. The structural information is not longer captured by model groups, but by a set of potential next occurrences. This is based on the idea of Brzozowski derivatives and again inspired by the anticipated needs of instance-oriented applications. We present a prototype implementation which is purely based on standard technologies. It is implemented as a XSLT 2.0 function library that reads schemas in the normative XML syntax, constructs the data model from this information, and provides various functions for accessing, navigating, and exploiting the schema information. We show that such functionality is highly beneficial, making applications more powerful, resilient, and easier to develop.</p>
			</richtext>
		</abstract>
		<title type="sharef:primaryTitle">Data Model Perspectives for XML Schema</title>
		<field type="bibtex:topic">scx[0.9] spath[0.8]</field>
		<identifier type="sharef:uri">http://dret.net/netdret/publications#wil07h</identifier>
		<identifier type="sharef:uri">http://2007.xtech.org/public/schedule/detail/159</identifier>
	</reference>
	<reference name="mur07" src="bibtex:inproceedings" src-info="bibtex:line-8578" type="sharef:inproceedings" crossref="xtech2007">
		<names type="sharef:author">
			<person>
				<givenname>Ravi</givenname>
				<surname>Murthy</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>There are many benefits of using XML as the single data model for enterprise applications. In addition to its inherent flexibility and extensibility, it reduces impedance mismatch across tiers and provides opportunity for global dependency analysis and optimization. However, XML is fundamentally a tree data model whereas real world applications truly need graphs. The XML standards provide a few primitive ways of representing relationships (links) between XML nodes, namely ID/IDREF and XLink. But the existing standards require significant enhancements to be able to express declarative constraints (metadata) about links, to configure link behavior, and to easily query/traverse across forward and reverse links. This paper details the requirements and proposes a set of enhancements to XML schema and query languages to enable building enterprise and content management applications. Further, it describes various implementation issues and optimization challenges in managing links within large XML databases. Links between XML nodes can be either intra or inter-document links, and target a fragment (using XPointer) or the entire document. New schema annotations provide declarative mechanisms to constrain the type of the link target, scope the link to a specified domain and also express acyclic link conditions. The integrity of the link wrt to the guaranteed presence of target document and link validity when the target is renamed or moved can also be configured. New query functions enable forward and reverse traversal of links within XPath, XQuery and XSLT. We discuss efficient link storage techniques in XML databases and indexes for performant bidirectional link traversal. In addition to managing links that appear in the original documents, we present mechanisms to implicitly add links into documents. Since a document is the unit of locking, versioning and access control, there are several advantages to decomposing a large XML document into smaller sub documents. Users can declaratively express the decomposition rules using XPaths and/or XML schema annotations. When the document is inserted into the system, it is implicitly shredded into multiple documents, and XInclude link elements are inserted in place of the original fragments. These inter-document links can be managed, queried and traversed as described above. Users can also recompose the original document by invoking native XInclude expansion functions.</p>
			</richtext>
		</abstract>
		<title type="sharef:primaryTitle">From Trees to Graphs: Evolving XML for Building Enterprise Applications</title>
		<field type="bibtex:topic">xlink[0.7] xinclude[0.7]</field>
		<identifier type="sharef:uri">http://2007.xtech.org/public/schedule/detail/81</identifier>
	</reference>
	<reference name="xtech2007" src="bibtex:proceedings" src-info="bibtex:line-8587" type="sharef:proceedings">
		<date value="2007-05"/>
		<address type="sharef:placePublished">Paris, France</address>
		<field type="bibtex:key">XTech 2007</field>
		<title type="sharef:primaryTitle">XTech 2007</title>
		<identifier type="sharef:uri">http://2007.xtech.org/public/schedule/full</identifier>
	</reference>
	<reference name="wil07i" src="bibtex:inproceedings" src-info="bibtex:line-8601" type="sharef:inproceedings" crossref="scc2007">
		<names type="sharef:author">
			<person>
				<givenname>Erik</givenname>
				<surname>Wilde</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>While services are widely regarded as an important new concept in IT architecture, so far there is no consolidated concept about the exact meaning of the term "service orientation". While there are many problems which are simply problems of certain technical decisions, other areas are more fundamental and lead to different perspectives and eventually implementations of service oriented systems. We argue that the current emphasis of service orientation as a collection of interface descriptions misses the critical point of services, which is that they revolve around resources. With a more resource-centered approach, the investment into a service oriented architecture can be made much more promising, because the resource-centered approach is better suited for the design of loosely coupled systems than the current interface-based approach.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1109/SCC.2007.135</identifier>
		<pages>256-261</pages>
		<title type="sharef:primaryTitle">What are you talking about?</title>
		<identifier type="sharef:uri">http://dret.net/netdret/publications#wil07i</identifier>
	</reference>
	<reference name="scc2007" src="bibtex:proceedings" src-info="bibtex:line-8611" type="sharef:proceedings">
		<date value="2007-07"/>
		<address type="sharef:placePublished">Salt Lake City, Utah</address>
		<field type="bibtex:key">2007 IEEE International Conference on Services Computing</field>
		<title type="sharef:primaryTitle">2007 IEEE International Conference on Services Computing</title>
		<identifier type="sharef:uri">http://conferences.computer.org/scc/2007/</identifier>
	</reference>
	<reference name="wil08h" src="bibtex:inproceedings" src-info="bibtex:line-8625" type="sharef:inproceedings" crossref="scc2008">
		<names type="sharef:author">
			<person>
				<givenname>Eric C.</givenname>
				<surname>Kansa</surname>
			</person>
			<person>
				<givenname>Erik</givenname>
				<surname>Wilde</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>This paper describes characteristics of information and service design by exploring the needs and motivations of tourists. Tourists are expected to be important and demanding users of location-based services. They will need customized means to filter their experience of destinations, as well as ways to meaningfully participate in the creation of narratives and histories about different places. Mobile technologies will also allow tourists to be more discriminating in their patronage of different service offerings, especially as they gain greater knowledge of so-called "backstage" processes. These demanding needs will require choreography between services offered by many different commercial, cultural, educational, and community providers. The paper suggests approaches to deliver tourist location-based services based on low barrier of entry principles of web architecture. The paper concludes with a discussion on how the erosion of backstage/frontstage distinctions in service systems impacts service innovation.</p>
			</richtext>
		</abstract>
		<title type="sharef:primaryTitle">Tourism, Peer Production, and Location-Based Service Design</title>
		<identifier type="sharef:uri">http://dret.net/netdret/publications#wil08h</identifier>
	</reference>
	<reference name="scc2008" src="bibtex:proceedings" src-info="bibtex:line-8633" type="sharef:proceedings">
		<date value="2008-07"/>
		<address type="sharef:placePublished">Honolulu, Hawaii</address>
		<field type="bibtex:key">2008 IEEE International Conference on Services Computing</field>
		<title type="sharef:primaryTitle">2008 IEEE International Conference on Services Computing</title>
		<identifier type="sharef:uri">http://conferences.computer.org/scc/2008/</identifier>
	</reference>
	<reference name="may01" src="bibtex:inproceedings" src-info="bibtex:line-8647" type="sharef:inproceedings" crossref="ideas01">
		<names type="sharef:author">
			<person>
				<givenname>Wolfgang</givenname>
				<surname>May</surname>
			</person>
		</names>
		<title type="sharef:primaryTitle">XPathLog: A Declarative, Native XML Data Manipulation Language</title>
		<field type="bibtex:topic">xpathlog[1.0]</field>
		<identifier type="sharef:uri" resourceType="application/pdf">http://cui.unige.ch/isi/cours/aftsi/articles/06-may-xpathlog.pdf</identifier>
	</reference>
	<reference name="ideas01" src="bibtex:proceedings" src-info="bibtex:line-8655" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>Michel E.</givenname>
				<surname>Adiba</surname>
			</person>
			<person>
				<givenname>Christine</givenname>
				<surname>Collet</surname>
			</person>
			<person>
				<givenname>Bipin C.</givenname>
				<surname>Desai</surname>
			</person>
		</names>
		<date value="2001-07"/>
		<address type="sharef:placePublished">Grenoble, France</address>
		<field type="bibtex:index">IDEAS 2001</field>
		<identifier type="sharef:isbn">0769511406</identifier>
		<field type="bibtex:key">International Database Engineering &amp; Applications Symposium</field>
		<publisher>IEEE Computer Society Press</publisher>
		<title type="sharef:primaryTitle">International Database Engineering &amp; Applications Symposium</title>
		<identifier type="sharef:uri" resourceType="text/html">http://csdl.computer.org/comp/proceedings/ideas/2001/1140/00/1140toc.htm</identifier>
	</reference>
	<reference name="erw00" src="bibtex:inproceedings" src-info="bibtex:line-8673" type="sharef:inproceedings" crossref="ieeevl2000">
		<names type="sharef:author">
			<person>
				<givenname>Martin</givenname>
				<surname>Erwig</surname>
			</person>
		</names>
		<pages>47-54</pages>
		<title type="sharef:primaryTitle">A Visual Language for XML</title>
		<field type="bibtex:topic">xml[0.8]</field>
		<identifier type="sharef:uri">http://web.engr.oregonstate.edu/~erwig/papers/abstracts.html#VL00</identifier>
	</reference>
	<reference name="ieeevl2000" src="bibtex:proceedings" src-info="bibtex:line-8682" type="sharef:proceedings">
		<date value="2000-09"/>
		<address type="sharef:placePublished">Seattle, Washington</address>
		<field type="bibtex:index">VL'00</field>
		<field type="bibtex:key">IEEE Symposium on Visual Languages</field>
		<title type="sharef:primaryTitle">IEEE Symposium on Visual Languages</title>
		<identifier type="sharef:uri" resourceType="text/html">http://csdl.computer.org/comp/proceedings/vl/2000/0840/00/0840toc.htm</identifier>
	</reference>
	<reference name="car01b" src="bibtex:inproceedings" src-info="bibtex:line-8697" type="sharef:inproceedings" crossref="xml2001">
		<names type="sharef:author">
			<person>
				<givenname>David</givenname>
				<surname>Carlson</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>As the use of XML matures within our systems development toolkit, we need a better approach for integrating its schema definitions with other analysis and design activities. The Unified Modeling Language (UML) is described as a useful solution that breaks down walls separating development activities and technologies. A financial derivatives trade application is described where the FpML vocabulary is imported into UML from its XML Schema source, and this is integrated with a Trading Party vocabulary imported from a SOX schema included in xCBL. These XML data definitions are then linked with a relational database schema imported into the same UML model. All of these data definitions are integrated as part of a simple portal application for trade confirmation. The iterative design approach illustrates benefits of UML for rapid analysis and design of new e-business applications that include XML content in part of their design.</p>
			</richtext>
		</abstract>
		<title type="sharef:primaryTitle">Integrating XML and non-XML Data via UML</title>
		<field type="bibtex:topic">uml[0.8] xml[0.8]</field>
		<identifier type="sharef:uri" resourceType="text/html">http://www.idealliance.org/papers/xml2001/papers/html/05-00-02.html</identifier>
	</reference>
	<reference name="gra01" src="bibtex:inproceedings" src-info="bibtex:line-8706" type="sharef:inproceedings" crossref="xml2001">
		<names type="sharef:author">
			<person>
				<givenname>Marc</givenname>
				<surname link="de">Graauw</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>With the abundance of XML vocabularies a common question is: which seemingly different elements are really the same, and which ones are really different. In business we encounter this problem in data exchange: how do I map the messages and elements from my favorite B2B-vocabulary onto the B2B-vocabulary my trading partner uses? Ontologies try to define which things we speak (or exchange data) about and how we reference them. In mapping between two ontologies we often use equivalence relationships: 'LastName = given_name', 'Thomas Mann = der Zauberer' et cetera. In the first part of the paper I want to explore some philosophical notions on equivalence: the difference between intension and extension (Frege) and the idea that meanings aren't always precise (Wittgenstein). I will also discuss the relevance for IT of these notions. In the second part I want to explore some current solutions in XML and Knowledge Management: (1) The naive approach: Let's make a new vocabulary which covers everything, then let everybody use that vocabulary. (2) Adding meta-information: This approach is used in the Context Drivers of ebXML. (3) Published Subject Identifiers (PSI): Make public libraries of unique ID's for things and map to those ID's. In the third part I will identify some problems in the current solutions and propose an enhancement: we need to capture the knowledge in mappings and we need tools to help reusing this knowledge. An open and standardized format for storing and exchanging knowledge about mappings would be a major step towards ontology interoperability.</p>
			</richtext>
		</abstract>
		<title type="sharef:primaryTitle">What is 'is'?</title>
		<identifier type="sharef:uri" resourceType="application/pdf">http://www.marcdegraauw.com/files/whatisis.pdf</identifier>
		<identifier type="sharef:uri" resourceType="text/html">http://www.idealliance.org/papers/xml2001/papers/html/05-04-01.html</identifier>
	</reference>
	<reference name="pre01" src="bibtex:inproceedings" src-info="bibtex:line-8715" type="sharef:inproceedings" crossref="xml2001">
		<names type="sharef:author">
			<person>
				<givenname>Paul</givenname>
				<surname>Prescod</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>XSLT is the only programming language standardized specifically for processing XML. Nevertheless, the XSLT specification states: "XSLT is not intended as a completely general-purpose XML transformation language." It is surely even less appropriate as a general purpose programming language. Nevertheless, some XSLT advocates have noted that more and more processing can be moved into the XSLT domain as more and more data is represented or transferred as XML. On the other hand, scripting languages are certainly general purpose. Most of the modern ones have features designed for programming in the large such as object orientation and exception handling. They also have quite solid XML support. They could certainly be used to do anything that would otherwise be done by XSLT. Advocates of these languages also see more and more processing moving from the world of traditional programming languages (e.g. C, C++ and Java) into scripting languages. Some claim that there is no need for XSLT at all. They ask why scripting languages should cede any part of the XML processing domain to XSLT. Obviously these arguments can only be both compelling if there is some substantial overlap in the problem domains of scripting languages and XSLT. This paper is intended to explore this overlap and help the reader to choose whether to learn and use one or both of these emerging technologies.</p>
			</richtext>
		</abstract>
		<title type="sharef:primaryTitle">XSLT and Scripting Languages</title>
		<field type="bibtex:topic">xslt1[0.8]</field>
		<identifier type="sharef:uri" resourceType="text/html">http://www.idealliance.org/papers/xml2001/papers/html/05-03-06.html</identifier>
	</reference>
	<reference name="xml2001" src="bibtex:proceedings" src-info="bibtex:line-8724" type="sharef:proceedings">
		<date value="2001-12"/>
		<address type="sharef:placePublished">Orlando, Florida</address>
		<field type="bibtex:index">XML 2001</field>
		<field type="bibtex:key">XML 2001</field>
		<title type="sharef:primaryTitle">XML 2001</title>
		<identifier type="sharef:uri">http://www.idealliance.org/papers/xml2001papers/</identifier>
	</reference>
	<reference name="wil04g" src="bibtex:inproceedings" src-info="bibtex:line-8739" type="sharef:inproceedings" crossref="xmleu2004">
		<names type="sharef:author">
			<person>
				<givenname>Mario</givenname>
				<surname>Jeckle</surname>
			</person>
			<person>
				<givenname>Erik</givenname>
				<surname>Wilde</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Web Services and their potential applications are currently under heavy discussion in industry, research, and standardization. As a result of evaluation and experience by early adopters, the technology is expected to mature through the advent of new standards and solutions leveraging Web Service's power. In essence, the efforts undertaken to create and complete a stack of Web Service protocols lead to a new communication architecture and extends the stack of classical network protocols. This evolving architecture could serve as a future-proof infrastructure for businesses to rely on. However the growth of the Web Service stack with respect to the addition of new layers and expansion of the resulting infrastructure has not been studied in comparison with well-established protocol suites like the ISO/OSI stack or the set of protocols constituting the Internet. Strictly speaking, industry's demand for functionality and services enhancing the basic Web Service protocols such as XML-RPC or SOAP, leads to the creation of a full-fledged layered protocol suite on-top of the existing ones. Nevertheless, the various standards, specifications, and ideas have neither been consolidated on a common terminological basis, nor been integrated in a single framework of reference. This observation also applies to the established trio of Web Service standards composing of SOAP, WSDL, and UDDI. According to the specific usage patterns of these specifications, they are not operating on one layer as the well-known triangular relationship graph suggests, but instead they are connected by means of unidirectional usage dependencies. From this point of view, the message patterns (MP) defined by WSDL 2.0 offer services to layers organized on top of WSDL which rely on the service interfaces exposed by SOAP. More precisely, not the interface definition with WSDL but the accompanying MPs act as the transport layer of the service stack. Based on this and other criteria, SOAP can be categorized as the basic low-level layer of the Web Service infrastructure corresponding to the network-dependent layers of the classical protocol suites. Based on these facts, all of the various efforts relying on the seminal Web Service protocols can be categorized at the various levels layered above the transport layer. This is especially true for specifications dealing with the management of sessions and transactions which are layered directly above the MPs. Also, security standards like XML digital signatures and XML encryption fit well into this by classifying them as part of the presentation layer. Furthermore, within the Web Service environment quite analogous application layer mechanisms (e.g. firewalls for content filtering) emerge are commonly known for classical network operation. Taking this congruency of established protocol stacks and the Web Service's one step further the analogy may serve as a valuable framework for the comparison of different architectural styles in Web Service deployment. Taking the continuing debate weighing services based on representational state transfer (REST) against those based on RPC-style SOAP as an example, both approaches reveal themselves as heterogeneous protocols. Both ideas are not mutually exclusive nor conflicting at all. Both protocols can be made interoperable by the use of bridges or gateways arbitrating between the two parties. Our analysis shows that Web Services are a true but yet incomplete protocol suite deploying classical Internet protocols as basic services by the continued addition of supplemental specifications and standards.</p>
			</richtext>
		</abstract>
		<title type="sharef:primaryTitle">Identical Principles, Higher Layers: Modeling Web Services as Protocol Stack</title>
		<identifier type="sharef:uri">http://dret.net/netdret/publications#wil04g</identifier>
		<identifier type="sharef:uri" resourceType="text/html">http://www.idealliance.org/papers/dx_xmle04/papers/03-05-04/03-05-04.html</identifier>
	</reference>
	<reference name="lit04" src="bibtex:inproceedings" src-info="bibtex:line-8748" type="sharef:inproceedings" crossref="xmleu2004">
		<names type="sharef:author">
			<person>
				<givenname>Elena</givenname>
				<surname>Litani</surname>
			</person>
			<person>
				<givenname>Lisa</givenname>
				<surname>Martin</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>This paper will provide an overview of the XML Schema API which defines interfaces to query the post-schema validation infoset (PSVI) including the XML Schema components.</p>
			</richtext>
		</abstract>
		<title type="sharef:primaryTitle">An API to Query XML Schema Components and the PSVI</title>
		<field type="bibtex:topic">xsd[0.8]</field>
		<identifier type="sharef:uri" resourceType="text/html">http://www.idealliance.org/papers/dx_xmle04/papers/02-05-02/02-05-02.html</identifier>
	</reference>
	<reference name="kay04" src="bibtex:inproceedings" src-info="bibtex:line-8757" type="sharef:inproceedings" crossref="xmleu2004">
		<names type="sharef:author">
			<person>
				<givenname>Michael</givenname>
				<surname>Kay</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>This paper describes the main techniques used by the Saxon XSLT and XQuery processor to optimize the execution of XSLT stylesheets and XPath expressions, and reviews some additional XSLT and XPath optimization techniques that are not (yet) used in Saxon. The primary focus is on XPath rather than XSLT, partly because Saxon does relatively little optimization at the XSLT level (other than in the way pattern matching works). Recent releases of Saxon support XQuery 1.0 as well as XSLT 2.0. However, the XQuery processor is an in-memory processor, not a database query engine. Optimizing database queries is an entirely different art, because it relies so heavily on rearranging queries to exploit persistent indexes. An in-memory processor does not have this opportunity, because the only indexes available are those that are constructed transiently for the duration of a transformation or query. Saxon's processing can be divided into three phases: parsing, static analysis, and run-time execution. These are described in the three main sections of this paper.</p>
			</richtext>
		</abstract>
		<title type="sharef:primaryTitle">XSLT and XPath Optimization</title>
		<field type="bibtex:topic">xpath1[0.9] xslt1[0.9]</field>
		<identifier type="sharef:uri" resourceType="text/html">http://idealliance.org/papers/dx_xmle04/papers/02-03-02/02-03-02.html</identifier>
	</reference>
	<reference name="tho04" src="bibtex:inproceedings" src-info="bibtex:line-8766" type="sharef:inproceedings" crossref="xmleu2004">
		<names type="sharef:author">
			<person>
				<givenname>Henry S.</givenname>
				<surname>Thompson</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>This paper defines a logic in which to express constraints on W3C XML Schema components and relationships between components and XML infoset items, for use in a formal rewriting of the W3C XML Schema Recommendations. The logic is essentially a constraint language over path expressions, interpreted equally with respect to an Infoset graph or a schema component graph. By 'logic' I mean the traditional three-part story comprised of a sentential form, a model theory and an interpretation.</p>
			</richtext>
		</abstract>
		<title type="sharef:primaryTitle">Towards a logical foundation for XML Schema</title>
		<field type="bibtex:topic">xsd[0.9]</field>
		<identifier type="sharef:uri" resourceType="text/html">http://www.ltg.ed.ac.uk/~ht/XML_Europe_2004.html</identifier>
		<identifier type="sharef:uri" resourceType="text/html">http://www.idealliance.org/papers/dx_xmle04/index/title/62698df164b0a5a2c4a54c8678.html</identifier>
	</reference>
	<reference name="xmleu2004" src="bibtex:proceedings" src-info="bibtex:line-8776" type="sharef:proceedings">
		<date value="2004-04"/>
		<address type="sharef:placePublished">Amsterdam, Netherlands</address>
		<field type="bibtex:index">XML Europe 2004</field>
		<field type="bibtex:key">XML Europe 2004</field>
		<title type="sharef:primaryTitle">XML Europe 2004</title>
		<identifier type="sharef:uri">http://www.xmleurope.com/2004/</identifier>
	</reference>
	<reference name="hen02" src="bibtex:inproceedings" src-info="bibtex:line-8791" type="sharef:inproceedings" crossref="xmleu2002">
		<names type="sharef:author">
			<person>
				<givenname>Marta Henriques</givenname>
				<surname>Jacinto</surname>
			</person>
			<person>
				<givenname>Giovani Rubert</givenname>
				<surname>Librelotto</surname>
			</person>
			<person>
				<givenname>José Carlos Leite</givenname>
				<surname>Ramalho</surname>
			</person>
			<person>
				<givenname>Pedro Rangel</givenname>
				<surname>Henriques</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>After being able to mark-up text and validate its structure according to a grammar, we may start thinking it would be natural to be able to validate some non-structural issues in XML documents like relationships between elements belonging to different contexts, invariants over data models, constraints over attribute values and relationships between attributes. XML Schemas are a big step in that direction. However, they only allow users to specify primitive constraints like data typing and data format. Currently, we can find two approaches that represent a complement to DTDs or XML Schemas — XCSL and Schematron — and allow us to specify constraints and to validate the instances of a family of documents against that set of rules. Both are implemented on top of XSL. Both use a kind of an XML envelope to hide XSL specification. XSLT pattern language is the core language of both systems. With all these resemblances it is easy to conclude that they are quite similar. However they differ in some fundamental concepts. These two constraint specification languages together with XML Schemas were hardly tested and benchmarked with an huge test suite. The most significant results will be discussed in this paper. We will try to answer questions like: Do they do the same job? Are there some kind of constraints that are easier to specify with one of them? Do you need different background to use the tools? Is it possible to use them in similar situations (the same DTD, the same XML instances)? May we use them to produce an equal result? How do XCSL and Schematron relate to XML Schemas? What is the intersection area of these three? What kind of constraints each one of these three is able to specify? What kind of constraints each one of these three can not specify? In this article, we will use that test suite and show, step-by-step, the way we handled several kinds of constraints in many different instances.</p>
			</richtext>
		</abstract>
		<title type="sharef:primaryTitle">Constraint Specification Languages: Comparing XCSL, Schematron and XML-Schemas</title>
		<field type="bibtex:topic">schematron[0.8] xcsl[0.8]</field>
		<identifier type="sharef:uri" resourceType="text/html">http://www.idealliance.org/papers/xmle02/dx_xmle02/index/title/d0e44608.html</identifier>
	</reference>
	<reference name="mcg02" src="bibtex:inproceedings" src-info="bibtex:line-8800" type="sharef:inproceedings" crossref="xmleu2002">
		<names type="sharef:author">
			<person>
				<givenname>Sean</givenname>
				<surname>McGrath</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>As XML proliferates, so too does the need for scalable, robust XML processing. There is no consensus as to how best to perform XML processing. SAX, DOM, XSLT all have their fervent admirers and detractors. XPipe is a methodology for XML processing that steps one degree above individual processing techniques and blends them into a single XML processing approach. Using the assembly line principle, XPipe promotes the decomposition of large processing tasks thus promoting the creation of repositories of re-usable XML processing components.</p>
			</richtext>
		</abstract>
		<title type="sharef:primaryTitle">XPipe — A Pipeline Based Approach To XML Processing</title>
		<field type="bibtex:topic">xpipe[0.9]</field>
		<identifier type="sharef:uri" resourceType="text/html">http://62.231.133.220/idea-eks-nav/xtm/xpipe%20-%20a%20pipeline%20based%20approach%20to%20xml%20processing.html</identifier>
		<identifier type="sharef:uri" resourceType="text/html">http://www.idealliance.org/papers/xmle02/dx_xmle02/index/title/d0e59584.html</identifier>
	</reference>
	<reference name="vli02a" src="bibtex:inproceedings" src-info="bibtex:line-8810" type="sharef:inproceedings" crossref="xmleu2002">
		<names type="sharef:author">
			<person>
				<givenname>Eric</givenname>
				<surname link="van der">Vlist</surname>
			</person>
		</names>
		<title type="sharef:primaryTitle">XML Schema Languages</title>
		<field type="bibtex:topic">xmlschemalanguage[0.8] xml[0.6] examplotron[0.8] xsd[0.8] sox[0.8] schematron[0.8] relaxng[0.8] dsdl[0.8] trex[0.8] relax[0.8]</field>
		<identifier type="sharef:uri" resourceType="text/html">http://62.231.133.220/idea-eks-nav/xtm/xml%20schema%20languages.html</identifier>
	</reference>
	<reference name="xmleu2002" src="bibtex:proceedings" src-info="bibtex:line-8818" type="sharef:proceedings">
		<date value="2002-05"/>
		<address type="sharef:placePublished">Barcelona, Spain</address>
		<field type="bibtex:index">XML Europe 2002</field>
		<field type="bibtex:key">XML Europe 2002</field>
		<title type="sharef:primaryTitle">XML Europe 2002</title>
		<identifier type="sharef:uri">http://www.idealliance.org/papers/xmle02/</identifier>
	</reference>
	<reference name="wil02j" src="bibtex:inproceedings" src-info="bibtex:line-8833" type="sharef:inproceedings" crossref="xml2002">
		<names type="sharef:author">
			<person>
				<givenname>Erik</givenname>
				<surname>Wilde</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>The XML Infoset defines the data model of XML, and it is used by a number of other specifications, such as XML Schema, XPath, DOM, and SAX. Currently, the Infoset defines a fixed number of Information Items and their Properties, and the only widely accepted extension of the Infoset are the Post Schema Validation Infoset (PSVI) contributions of XML Schema. XML Schema demonstrates that extending the Infoset can be very useful, and the PSVI contributions of XML Schema are being used by XPath 2.0 to access type information in a document's Infoset. In this paper, we present an approach to making the Infoset generically extensible by using the well-known Namespace mechanism. Using Namespaces, it is possible to define sets of additional Information Items and Properties which are extending the core Infoset (or other Infoset extensions, defining a possibly multi-level hierarchy of Infoset extensions). Basically, a Namespace for an Infoset extension contains a number of Information Items, which may have any number of Properties. It is also possible to define an Infoset extension containing only Properties, extending the Information Items of other Infosets. Further elaborating on this method, many of the XML technologies currently using the Infoset could be extended to support the Infoset extensions by importing Infoset extension using the extension's Namespace name. To illustrate these concepts, we give an example by defining the XML Linking Language (XLink), the XML vocabulary for hyperlinking information, in terms of Infoset extensions. We show how the proposed ways of supporting Infoset extensions in XML technologies such as XPath, DOM, and CSS could pave the path to a better support (and hopefully faster adoption) of XLink than we see today. XLink serves as one example, but the proposed extensions and techniques are not limited to this particular technology. The content of this paper is work in progress, contributing to the ongoing debate on how to deal with different XML vocabularies and their usage in other XML technologies. We believe that making the Infoset extensible would provide a robust and flexible way of making the data model of XML-based data more versatile, and creating an accepted way of making the data available through standard interfaces such as DOM and XPath.</p>
			</richtext>
		</abstract>
		<title type="sharef:primaryTitle">Making the Infoset Extensible</title>
		<field type="bibtex:topic">xmlinfoset[0.8] exis[1]</field>
		<identifier type="sharef:uri">http://dret.net/netdret/publications#wil02j</identifier>
		<identifier type="sharef:uri" resourceType="text/html">http://www.idealliance.org/papers/xml02/dx_xml02/index/title/cbb8d590b64d23aef79b09d8b1.html</identifier>
	</reference>
	<reference name="vli02b" src="bibtex:inproceedings" src-info="bibtex:line-8843" type="sharef:inproceedings" crossref="xml2002">
		<names type="sharef:author">
			<person>
				<givenname>Eric</givenname>
				<surname link="van der">Vlist</surname>
			</person>
		</names>
		<title type="sharef:primaryTitle">XML Schema Languages</title>
		<field type="bibtex:topic">xmlschemalanguage[0.8] xml[0.6] examplotron[0.8] xsd[0.8] sox[0.8] schematron[0.8] relaxng[0.8] dsdl[0.8] trex[0.8] relax[0.8]</field>
		<identifier type="sharef:uri" resourceType="text/html">http://www.idealliance.org/papers/xml02/dx_xml02/html/abstract/04-01-01.html</identifier>
	</reference>
	<reference name="stl02" src="bibtex:inproceedings" src-info="bibtex:line-8851" type="sharef:inproceedings" crossref="xml2002">
		<names type="sharef:author">
			<person>
				<givenname>Simon</givenname>
				<surname>St. Laurent</surname>
			</person>
		</names>
		<title type="sharef:primaryTitle">Getting Out-Of-Line: How Embedded Markup Can Learn From Its Detractors</title>
		<field type="bibtex:topic">ool[1]</field>
		<identifier type="sharef:uri" resourceType="text/html">http://www.idealliance.org/papers/xml02/dx_xml02/index/title/02911a0844b7a6aa14a4b9190e.html</identifier>
	</reference>
	<reference name="lub02" src="bibtex:inproceedings" src-info="bibtex:line-8859" type="sharef:inproceedings" crossref="xml2002">
		<names type="sharef:author">
			<person>
				<givenname>Joshua</givenname>
				<surname>Lubell</surname>
			</person>
		</names>
		<title type="sharef:primaryTitle">From Model to Markup</title>
		<field type="bibtex:topic">step[0.7] express[0.8]</field>
		<identifier type="sharef:uri" resourceType="text/html">http://www.idealliance.org/papers/xml02/dx_xml02/index/title/f8d35958a0b772897676d5c4dc.html</identifier>
	</reference>
	<reference name="pep02" src="bibtex:inproceedings" src-info="bibtex:line-8867" type="sharef:inproceedings" crossref="xml2002">
		<names type="sharef:author">
			<person>
				<givenname>Steve</givenname>
				<surname>Pepper</surname>
			</person>
			<person>
				<givenname>Lars Marius</givenname>
				<surname>Garshol</surname>
			</person>
		</names>
		<title type="sharef:primaryTitle">The XML Papers: Lessons on Applying Topic Maps</title>
		<field type="bibtex:topic">xmlvoc[0.8]</field>
		<identifier type="sharef:uri" resourceType="text/html">http://www.idealliance.org/papers/xml02/dx_xml02/index/keyword/ea237e84d33619bf9524f774ce.html</identifier>
	</reference>
	<reference name="xml2002" src="bibtex:proceedings" src-info="bibtex:line-8875" type="sharef:proceedings">
		<date value="2002-12"/>
		<address type="sharef:placePublished">Baltimore, Maryland</address>
		<field type="bibtex:index">XML 2002</field>
		<field type="bibtex:key">XML 2002</field>
		<title type="sharef:primaryTitle">XML 2002</title>
	</reference>
	<reference name="sen03" src="bibtex:inproceedings" src-info="bibtex:line-8889" type="sharef:inproceedings" crossref="xml2003">
		<names type="sharef:author">
			<person>
				<givenname>Arijit</givenname>
				<surname>Sengupta</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>XML is one of the premier formats for data representation and interchange. Many organizations are starting to store data in XML and using XML as an intermediate format for publication and use of these documents. Most database systems have support for storing data in XML or internally representing XML data for storage. However, XML does not have a suitable mechanism for intuitively creating a conceptual model for the data and cannot automatically or semi-automatically generate the schema for the actual data storage. The area of designing conceptual modeling techniques for XML is still not adequately explored in literature. In this paper we describe the XER (Extensible Entity-Relationship) model, a conceptual modeling approach that can describe XML document structures in a simple visual form reminiscent of the ER model, and has the capability to automatically generate XML document type definitions and schema from such structures.</p>
			</richtext>
		</abstract>
		<title type="sharef:primaryTitle">XER — Extensible Entity Relationship Modeling</title>
		<field type="bibtex:topic">xer2[0.8]</field>
		<identifier type="sharef:uri" resourceType="text/html">http://www.idealliance.org/papers/dx_xml03/papers/06-01-01/06-01-01.html</identifier>
		<identifier type="sharef:uri" resourceType="application/pdf">http://www.bus.indiana.edu/asengupt/Published/xml03.pdf</identifier>
	</reference>
	<reference name="gar03" src="bibtex:inproceedings" src-info="bibtex:line-8899" type="sharef:inproceedings" crossref="xml2003">
		<names type="sharef:author">
			<person>
				<givenname>Patrick</givenname>
				<surname>Garvey</surname>
			</person>
			<person>
				<givenname>Bill</givenname>
				<surname>French</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Many web applications collect and manipulate user input as XML documents, usually by receiving input through forms. It is natural to think of a schema for a document created by the form to be the specification for the application's user interface. This schema defines the structure and type information for the documents moving in and out of the application. Incoming documents may be treated differently by the application depending on whether they conform to a schema. Because W3C XML Schema is itself an XML vocabulary, XML Schema files can be transformed using XSLT into any number of target formats: HTML, XML, text, etc. Our goal was to transform XML Schemas into XForms user interfaces. By doing so we tie the user experience of the application directly to the application's data model. Changes in the data model are reflected in the user interface via a "push of a button", thus eliminating the need for tedious rewriting of presentation code. There have been other efforts to construct interfaces from XML Schemas, but most of those we found are limited by the types of schemas they could consume. For instance, many make assumptions that there will be no named global types, or neglect imported types and extension. To be truly generic, a schema processor should be able to identify and process types and elements from any imported schema. It should be able to recognize when a type is extending or restricting another type, and locate, in any namespace, the parent type to process its content model as well. A generic processor also must be able to handle different schema encoding styles, such as Venetian Blind or Garden of Eden. This paper will address some of the key design and implementation issues we addressed to create a generic XSD to XForms processor. We will then outline how the processor is being used today, and how it might be improved in the future.</p>
			</richtext>
		</abstract>
		<title type="sharef:primaryTitle">Generating User Interfaces from Composite Schemas</title>
		<identifier type="sharef:uri" resourceType="text/html">http://www.idealliance.org/xmlusa/03/call/xmlpapers/03-03-04.994/.03-03-04.html</identifier>
	</reference>
	<reference name="nag03" src="bibtex:inproceedings" src-info="bibtex:line-8907" type="sharef:inproceedings" crossref="xml2003">
		<names type="sharef:author">
			<person>
				<givenname>Biswadeep</givenname>
				<surname>Nag</surname>
			</person>
		</names>
		<title type="sharef:primaryTitle">A Comparison of XML Processing in .NET and J2EE</title>
		<field type="bibtex:topic">j2ee[0.8] dotnet[0.8] xml[0.7]</field>
	</reference>
	<reference name="nen03b" src="bibtex:inproceedings" src-info="bibtex:line-8914" type="sharef:inproceedings" crossref="xml2003">
		<names type="sharef:author">
			<person>
				<givenname>Christian</givenname>
				<surname>Nentwich</surname>
			</person>
		</names>
		<title type="sharef:primaryTitle">Validating FpML</title>
		<field type="bibtex:topic">fpml[0.8]</field>
	</reference>
	<reference name="tho03b" src="bibtex:inproceedings" src-info="bibtex:line-8921" type="sharef:inproceedings" crossref="xml2003">
		<names type="sharef:author">
			<person>
				<givenname>Henry S.</givenname>
				<surname>Thompson</surname>
			</person>
		</names>
		<title type="sharef:primaryTitle">Re-Interpreting the XML Pipeline Note: Adding Streaming and On-Demand Invocation</title>
		<field type="bibtex:topic">xmlpipelinedefinitionlanguage[0.8]</field>
	</reference>
	<reference name="sal03" src="bibtex:inproceedings" src-info="bibtex:line-8928" type="sharef:inproceedings" crossref="xml2003">
		<names type="sharef:author">
			<person>
				<givenname>Richard</givenname>
				<surname>Salz</surname>
			</person>
		</names>
		<title type="sharef:primaryTitle">XML Security Standards and Best Practices</title>
		<field type="bibtex:topic">xmldsig[0.7] xmlenc[0.7] xkms[0.7] wssecurity[0.7]</field>
	</reference>
	<reference name="xml2003" src="bibtex:proceedings" src-info="bibtex:line-8935" type="sharef:proceedings">
		<date value="2003-12"/>
		<address type="sharef:placePublished">Philadelphia, Pennsylvania</address>
		<field type="bibtex:index">XML 2003</field>
		<field type="bibtex:key">XML 2003</field>
		<title type="sharef:primaryTitle">XML 2003</title>
	</reference>
	<reference name="wil03b" src="bibtex:inproceedings" src-info="bibtex:line-8949" type="sharef:inproceedings" crossref="xmleu2003">
		<names type="sharef:author">
			<person>
				<givenname>Erik</givenname>
				<surname>Wilde</surname>
			</person>
			<person>
				<givenname>Kilian</givenname>
				<surname>Stillhard</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>The new schema language defined by the W3C, XML Schema, is used in a number of applications, such as Web Services and XQuery, and will probably be used by an increasing number of users in the near future. Currently, XML Schema's data model, the "XML Schema Components", can only be represented in the rather verbose XML syntax defined in the XML Schema specification itself. We propose an alternative non-XML syntax, which is (1) much more compact than the XML syntax, (2) defined by EBNF productions, (3) re-uses well-known syntactic concepts where appropriate, and (4) is easy to implement using standard parser-generating tools. Our approach is comparable to the approach of the RELAX NG schema language, which also supports two alternative syntaxes, an XML-based one, and a more compact non-XML one. We believe that XML Schema could be made easier to use by supporting a compact syntax. Currently, complex schemas are very hard to read due to the large amount of XML markup, and the various tools and GUIs that are on the market differ widely and in all cases support only a subset of the features of XML Schema. We believe that there should be a compact syntax, optimized for human users, which makes it easy to read and write XML Schemas, and which supports the full feature set of XML Schema. Obviously, a non-XML syntax makes it necessary to introduce new tools. However, generating parsers from EBNF productions is rather simple and well-supported by standard tools (such as yacc and JavaCC), and the other direction (i.e., generating non-XML syntax) can be implemented by using XML tools. Our XML Schema Compact Syntax (XSCS) is geared towards human users, by re-using language constructs known from other application areas, such as DTDs and programming languages, and making them available for XML Schema component representation. Examples for this re-use of syntactic constructs are DTD-style content models, number ranges ("[a,b]" or "(a,b]" as in standard mathematical notation), and qualifying attributes like "abstract" or "final" known from programming languages ("final abstract type { ... }"). We also believe that graphical representations of complex structures such as schemas are not always suitable because some people prefer textual representations, editing might be faster when using keyboard input instead of using click-and-point operations, and graphical representations (usually) hide some information. We fully integrate the processing of our syntax into the existing pipeline of XML-based tools by creating a parser that generates SAX events or DOM trees from the compact syntax documents. This way, we can use the existing XML Schema validation engines and XML Schema error checking facilities already implemented in validation engines like the Xerces parser. In addition, we have a serialization module to generate compact syntax documents from XML Schema DOM trees. Our overall goal is to improve XML Schema acceptance by providing a syntax that is easier to work with than the XML syntax, and tools to process this syntax.</p>
			</richtext>
		</abstract>
		<title type="sharef:primaryTitle">A Compact XML Schema Syntax</title>
		<field type="bibtex:topic">xsd[0.8] xscs[0.9]</field>
		<identifier type="sharef:uri">http://dret.net/netdret/publications#wil03b</identifier>
		<identifier type="sharef:uri" resourceType="text/html">http://www.idealliance.org/papers/dx_xmle03/index/title/88196f18683b35a8fe80839a16.html</identifier>
	</reference>
	<reference name="mor03" src="bibtex:inproceedings" src-info="bibtex:line-8959" type="sharef:inproceedings" crossref="xmleu2003">
		<names type="sharef:author">
			<person>
				<givenname>Jean-Jacques</givenname>
				<surname>Moreau</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>This paper describes the SOAP 1.2 extensibility mechanism. This mechanism is based on features and MEPs. The paper also explains how features and MEPs are likely to be supported in WSDL 1.2. Features provide reusable functionality at the middleware level. MEPs describe patterns of interactions between nodes on the network.</p>
			</richtext>
		</abstract>
		<title type="sharef:primaryTitle">Features and MEPs in SOAP 1.2 and WSDL 1.2</title>
		<field type="bibtex:topic">wsdl[0.8] soap[0.8] soapmep[0.8] wsdlmep[0.8]</field>
		<identifier type="sharef:uri" resourceType="text/html">http://www.idealliance.org/papers/dx_xmle03/index/title/eac5e2a6f02b10fa0dbcb121fe.html</identifier>
	</reference>
	<reference name="sch03a" src="bibtex:inproceedings" src-info="bibtex:line-8968" type="sharef:inproceedings" crossref="xmleu2003">
		<names type="sharef:author">
			<person>
				<givenname>Cliff</givenname>
				<surname>Schmidt</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Several XML-based standards mandate the normalization of various aspects of XML and XML-based technologies. Normalization allows for compatibility between unfamiliar systems, which is necessary to fulfill scenarios that view the Web as a single, large application. Component systems within a Web application might benefit from relying on an early normalization process, which allows them to perform operations such as collation and string-matching without having to consider multiple potential forms of the incoming data. However, universal mandatory normalization can also restrict the flexibility for systems engaged in a private contract to efficiently use XML and XML-based technologies. Web services are probably the most prevalent example of such systems. The early normalization process might require a system to perform various additional encodings and decodings simply for the ability to use XML as a transport between system components, especially if they natively use a normalization form different from the mandated one. As current XML standards continue to evolve and new standards develop, the issue of mandatory normalization will continue to require the XML community to carefully consider the balance between two important Web scenarios: enabling unfamiliar systems to make certain assumptions about each other's data, without making it impractical for familiar systems to leverage the same standards and technologies. This paper will address these concerns by focusing on the specific issues around the character normalization debate.</p>
			</richtext>
		</abstract>
		<title type="sharef:primaryTitle">XML and Unicode Normalization</title>
		<field type="bibtex:topic">xml[0.7] unicode[0.7]</field>
		<identifier type="sharef:uri" resourceType="text/html">http://www.idealliance.org/papers/dx_xmle03/index/title/ad550a0b070decdd18f035cf40.html</identifier>
	</reference>
	<reference name="tho03" src="bibtex:inproceedings" src-info="bibtex:line-8977" type="sharef:inproceedings" crossref="xmleu2003">
		<names type="sharef:author">
			<person>
				<givenname>Henry S.</givenname>
				<surname>Thompson</surname>
			</person>
			<person>
				<givenname>Richard</givenname>
				<surname>Tobin</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Implementing validation and restriction checking for W3C XML Schema content models is harder than for DTDs. This paper gives complete details on how to convert W3C XML Schema content models to Finite State Automata, including handling of numeric exponents and wildcards. Enforcing the Unique Particle Attribution constraint and implementing restriction checking in polynomial time using these FSAs is also described.</p>
			</richtext>
		</abstract>
		<title type="sharef:primaryTitle">Using Finite State Automata to Implement W3C XML Schema Content Model Validation and Restriction Checking</title>
		<field type="bibtex:topic">xsd[0.8]</field>
		<identifier type="sharef:uri" resourceType="text/html">http://www.idealliance.org/papers/dx_xmle03/index/title/06f9fe54d6aafaa358188c385b.html</identifier>
	</reference>
	<reference name="stl03" src="bibtex:inproceedings" src-info="bibtex:line-8986" type="sharef:inproceedings" crossref="xmleu2003">
		<names type="sharef:author">
			<person>
				<givenname>Simon</givenname>
				<surname>St. Laurent</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>While most developers are happy parsing their XML with off-the-shelf parsers and working with fully-cooked results, there are times when developers need a little more control over their document processing. While XML is text, applying text processing tools directly to XML has some serious drawbacks. This presentation will explore the possibilities offered by a combination of XML parsing for context with text processing to manipulate that content.</p>
			</richtext>
		</abstract>
		<title type="sharef:primaryTitle">What can you do with half a parser?</title>
		<field type="bibtex:topic">xml[0.7]</field>
		<identifier type="sharef:uri" resourceType="text/html">http://www.idealliance.org/papers/dx_xmle03/index/title/de8ee1185a9079269f648ace8d.html</identifier>
	</reference>
	<reference name="ber03" src="bibtex:inproceedings" src-info="bibtex:line-8995" type="sharef:inproceedings" crossref="xmleu2003">
		<names type="sharef:author">
			<person>
				<givenname>Robin</givenname>
				<surname>Berjon</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Binary Infosets is the generic term covering an array of different binary formats that encode serializations of XML infosets, most of which are tailored to answer the needs of constrained or high-performance environments, such as are found in the mobile, embedded, broadcast, or web services industries. This talk will start off by describing the situations in which binary infosets become sufficiently advantageous to be worth investigating, contrasted with cases in which they are not. Using that to list typical requirements for binary infoset formats, the session will carry on into a technical discussion of several binary infoset formats, how they work and how they compare.</p>
			</richtext>
		</abstract>
		<title type="sharef:primaryTitle">Binary Infosets</title>
		<field type="bibtex:topic">xmlinfo[0.8]</field>
		<identifier type="sharef:uri" resourceType="text/html">http://www.idealliance.org/papers/dx_xmle03/index/title/0ab4c5e548f992448d4149c5ab.html</identifier>
	</reference>
	<reference name="che03" src="bibtex:inproceedings" src-info="bibtex:line-9004" type="sharef:inproceedings" crossref="xmleu2003">
		<names type="sharef:author">
			<person>
				<givenname>John</givenname>
				<surname>Chelsom</surname>
			</person>
			<person>
				<givenname>Stephen</givenname>
				<surname>Katz</surname>
			</person>
			<person>
				<givenname>Andrea</givenname>
				<surname>Zisman</surname>
			</person>
			<person>
				<givenname>Ron</givenname>
				<surname>Summers</surname>
			</person>
		</names>
		<title type="sharef:primaryTitle">Information Bus</title>
		<identifier type="sharef:uri" resourceType="text/html">http://www.idealliance.org/papers/dx_xmle03/index/title/e4d1d798fb3c781f3337869372.html</identifier>
	</reference>
	<reference name="dur03" src="bibtex:inproceedings" src-info="bibtex:line-9011" type="sharef:inproceedings" crossref="xmleu2003">
		<names type="sharef:author">
			<person>
				<givenname>Patrick</givenname>
				<surname>Durusau</surname>
			</person>
			<person>
				<givenname>Matthew</givenname>
				<surname>O'Donnell</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Current markup languages and processing tools assume and even impose a hierarchical, tree-based approach to the data encoded in documents. This paper explores the benefits and gains made possible by processing documents marked up in XML syntax as definitions of sets and the relations between them. This change of understanding has implications for the relationship between data and metadata without necessitating either a new syntax or set of processing tools. The use of milestones or empty elements in XML documents has traditionally been advocated as a solution to the problem of multiple and potentially overlapping structures. One of the difficulties of processing milestones with tree-based tools is that it requires the extraction of a node (and element with child PCDATA) from a flat representation where the milestones are siblings of the PCDATA. This procedure is made more difficult by the presence of intervening elements and structures. A set-based understanding of markup syntax treats all elements as milestones, thereby 'flattening' the document and raising the PCDATA to the primary level. The virtual milestones function to mark the boundaries of a set.</p>
			</richtext>
		</abstract>
		<title type="sharef:primaryTitle">Restoring the Primacy of PCDATA</title>
		<identifier type="sharef:uri" resourceType="text/html">http://www.idealliance.org/papers/dx_xmle03/index/title/1400888f2e96a0ef3f37d184fb.html</identifier>
	</reference>
	<reference name="rig03" src="bibtex:inproceedings" src-info="bibtex:line-9019" type="sharef:inproceedings" crossref="xmleu2003">
		<names type="sharef:author">
			<person>
				<givenname>Simon</givenname>
				<surname>Riggs</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>When the pressure is on, getting the messages flowing seems to be everyone's priority. XML Security is a huge and important side topic examining the problems associated with ensuring XML messages can move untampered between clearly identified and fully authorised agents. Data Quality is the next most important issue: does the message contain valid, timely, meaningful and eventually useful data? How can we implement a data quality architecture to support these concepts? Looking at the use of XML on both individual projects and also from the perspective of enterprise architecture, the topic of data quality will be discussed from business importance through to practical guidelines.</p>
			</richtext>
		</abstract>
		<title type="sharef:primaryTitle">Data Quality and XML Validation</title>
		<identifier type="sharef:uri" resourceType="text/html">http://www.idealliance.org/papers/dx_xmle03/index/title/478e480bb3560fbb7f8914356a.html</identifier>
	</reference>
	<reference name="xmleu2003" src="bibtex:proceedings" src-info="bibtex:line-9028" type="sharef:proceedings">
		<date value="2003-05"/>
		<address type="sharef:placePublished">London, UK</address>
		<field type="bibtex:index">XML Europe 2003</field>
		<field type="bibtex:key">XML Europe 2003</field>
		<title type="sharef:primaryTitle">XML Europe 2003</title>
		<identifier type="sharef:uri">http://www.idealliance.org/papers/dx_xmle03/</identifier>
	</reference>
	<reference name="kos04" src="bibtex:inproceedings" src-info="bibtex:line-9043" type="sharef:inproceedings" crossref="xml2004">
		<names type="sharef:author">
			<person>
				<givenname>Jirka</givenname>
				<surname>Kosek</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Many electronic publishing systems built on the top of XML (e.g. DocBook) use XSLT to convert source XML document into target formats like HTML or XSL-FO (for print output). During the transformation back-of-the-book index can be generated and populated by index entries spread over the document. Creating index basically means to sort and group index entries by their first letter. However this solutions is appropriate only for some languages, English included. For other Latin based languages like Czech, Hungarian or Spanish grouping method is more sophisticated and can't be expressed in the standard XSLT 1.0. The task is even more challenging if we want to get internationalized indexes in some general stylesheet package like DocBook XSL stylesheets. These stylesheets should support as many XSLT implementations as possible what disqualifies usage of vendor extensions. This paper will show you how support for non-English index generation was implemented in the DocBook XSL stylesheets, what problems were overcame and what functionality is missing in XSLT 1.0, but can be added using EXSLT extensions. To deal with grouping problems like different accented letters belonging to the same group, multi-letter sequences denoting one group etc. solution based on XSLT keys over user defined function is provided. This function uses external localization files to lookup values which drive index generation and grouping. Method presented up to this point is sufficient for indexes in HTML output. Print output brings new problems. As the transformation and formatting phases in the XSL are separated there is no direct support for merging duplicate page numbers in XSL-FO. Fortunately many FO engine vendors provide custom extensions to deal with this issue. Integration of these extensions into the DocBook XSL stylesheet will be presented. The article also includes evaluation of XSLT 2.0 features available for index generation and proposals for further improvement of indexing method that will be able to handle CJKV languages.</p>
			</richtext>
		</abstract>
		<title type="sharef:primaryTitle">Using XSLT for getting Back-of-the-book Indexes</title>
		<identifier type="sharef:uri" resourceType="text/html">http://www.idealliance.org/proceedings/xml04/abstracts/paper77.html</identifier>
	</reference>
	<reference name="xml2004" src="bibtex:proceedings" src-info="bibtex:line-9051" type="sharef:proceedings">
		<date value="2004-11"/>
		<address type="sharef:placePublished">Washington, D.C.</address>
		<field type="bibtex:index">XML 2004</field>
		<field type="bibtex:key">XML 2004</field>
		<title type="sharef:primaryTitle">XML 2004</title>
		<identifier type="sharef:uri">http://www.idealliance.org/proceedings/xml04/</identifier>
	</reference>
	<reference name="kay10a" src="bibtex:inproceedings" src-info="bibtex:line-9066" type="sharef:inproceedings" crossref="xmlprague2010">
		<names type="sharef:author">
			<person>
				<givenname>Michael</givenname>
				<surname>Kay</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>The XSL Working Group has been studying how to extend the language to support streaming, that is, the ability to transform source documents into result documents without holding either in memory. This paper describes the current state of the work, as represented in the first Working Draft of XSLT 2.1. This paper discusses a W3C Working Draft which at the time of writing has not been published, and which is therefore not referenced in the paper. When it is published, it will be announced on the home page for the XSL Working Group at http://www.w3.org/Style/XSL/.</p>
			</richtext>
		</abstract>
		<pages>3-14</pages>
		<title type="sharef:primaryTitle">Streaming in XSLT 2.1</title>
		<field type="bibtex:topic">xslt[0.9]</field>
	</reference>
	<reference name="and10a" src="bibtex:inproceedings" src-info="bibtex:line-9075" type="sharef:inproceedings" crossref="xmlprague2010">
		<names type="sharef:author">
			<person>
				<givenname>Cezar</givenname>
				<surname>Andrei</surname>
			</person>
			<person>
				<givenname>Matthias</givenname>
				<surname>Brantner</surname>
			</person>
			<person>
				<givenname>Daniela</givenname>
				<surname>Florescu</surname>
			</person>
			<person>
				<givenname>David</givenname>
				<surname>Graf</surname>
			</person>
			<person>
				<givenname>Donald</givenname>
				<surname>Kossmann</surname>
			</person>
			<person>
				<givenname>Markos</givenname>
				<surname>Zaharioudakis</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>The standard XQuery language lacks the ability to define and manipulate persistent artifacts like collections, indexes, and integrity constraints. This paper introduces a first attempt to standardize the syntax and semantics of such extensions, and it studies the implications on the static context, dynamic context and processing model of XQuery while dealing with persistent data. The paper presents example modules that show how collections, indexes, and integrity constraints are declared, created, maintained, or accessed.</p>
			</richtext>
		</abstract>
		<pages>179-194</pages>
		<title type="sharef:primaryTitle">Extending XQuery with Collections, Indexes, and Integrity Constraints</title>
		<field type="bibtex:topic">xquery[0.9]</field>
	</reference>
	<reference name="xmlprague2010" src="bibtex:proceedings" src-info="bibtex:line-9084" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>Jirka</givenname>
				<surname>Kosek</surname>
			</person>
		</names>
		<date value="2010-03"/>
		<address type="sharef:placePublished">Prague, Czech Republic</address>
		<field type="bibtex:key">XML Prague 2010</field>
		<title type="sharef:primaryTitle">XML Prague 2010</title>
		<identifier type="sharef:uri" resourceType="application/pdf">http://www.xmlprague.cz/2010/files/XMLPrague_2010_Proceedings.pdf</identifier>
	</reference>
	<reference name="lam05" src="bibtex:inproceedings" src-info="bibtex:line-9099" type="sharef:inproceedings" crossref="xml2005">
		<names type="sharef:author">
			<person>
				<givenname>Ralf</givenname>
				<surname>Lämmel</surname>
			</person>
			<person>
				<givenname>Stan</givenname>
				<surname>Kitsis</surname>
			</person>
			<person>
				<givenname>Dave</givenname>
				<surname>Remy</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>XML schema analysis aims to extract quantitative and qualitative information from actual XML schemas. To this end, XML schemas are measured through systematic algorithms, on the basis of the intrinsic feature model of the XSD language. XML schema analysis is a derivative of software analysis (program analysis) and of software code metrics, in particular. The present article introduces essential concepts of XML schema analysis and applies them to the important problem of understanding XML schema usage in practice. Analyses for feature counts, idiosyncrasy counts, size metrics, complexity metrics, and XML schema styles are executed on a large corpus of real-world XML schemas.</p>
			</richtext>
		</abstract>
		<title type="sharef:primaryTitle">Analysis of XML Schema Usage</title>
		<field type="bibtex:topic">xsd[0.9]</field>
		<identifier type="sharef:uri" resourceType="text/html">http://www.idealliance.org/proceedings/xml05/abstracts/paper49.HTML</identifier>
	</reference>
	<reference name="tho05" src="bibtex:inproceedings" src-info="bibtex:line-9108" type="sharef:inproceedings" crossref="xml2005">
		<names type="sharef:author">
			<person>
				<givenname>Henry S.</givenname>
				<surname>Thompson</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>The construction of URIs to identify named constituents of arbitrary XML languages is explored, as a step towards managing the versioning of language definitions.</p>
			</richtext>
		</abstract>
		<title type="sharef:primaryTitle">Names, Namespaces, XML Languages and XML Definition Languages</title>
		<field type="bibtex:topic">xml[0.8]</field>
		<identifier type="sharef:uri" resourceType="text/html">http://www.idealliance.org/proceedings/xml05/abstracts/paper82.HTML</identifier>
	</reference>
	<reference name="fit05" src="bibtex:inproceedings" src-info="bibtex:line-9117" type="sharef:inproceedings" crossref="xml2005">
		<names type="sharef:author">
			<person>
				<givenname>Adam</givenname>
				<surname>FitzGerald</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>As XML documents become a central part of enterprise application design developers and architects commonly build object models based on the definitions provided by a XML document's Schema. Changes in application functionality or business requirements often lead to modifications of the XML Schema which can require a complete redesign of the enterprise application. Building applications that are tolerant of evolving XML Schema is imperative for application maintenance and lowering development costs. This session discusses which XML Schema changes effect application code and how to design applications that minimize the impact of these changes. The examples used will be based on J2EE applications and the open source Apache XMLBeans framework.</p>
			</richtext>
		</abstract>
		<title type="sharef:primaryTitle">Best Practices for XML Schema Evolution in Application Development</title>
		<field type="bibtex:topic">xsd[0.7]</field>
		<identifier type="sharef:uri" resourceType="text/html">http://www.idealliance.org/proceedings/xml05/abstracts/paper27.HTML</identifier>
	</reference>
	<reference name="fos05" src="bibtex:inproceedings" src-info="bibtex:line-9126" type="sharef:inproceedings" crossref="xml2005">
		<names type="sharef:author">
			<person>
				<givenname>Howard</givenname>
				<surname>Foster</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>This paper presents a rigorous approach to specifying, modelling, verifying and validating the behaviour of web service compositions with the goal of simplifying the task of designing coordinated distributed services and their interaction requirements. We address these issues through the use of rigorous software process analysis techniques, specifying semantics for web service composition standards and by providing an accessible, mechanical tool (as a plug-in to the Eclipse development environment), which automates the tasks involved. As web technology has evolved, an emphasis has been placed on providing ease of design for both visual content and functional services for users. Web Services however, concentrate on the view of systems inter-operating with other systems rather than that of actual human actors, yet the concepts for ease of design are highly related and desired. Firstly, this paper presents a model-based approach to the semantics of web service composition XML documents built upon formal verification, validation and simulation techniques, utilising scenario-based design and implementations built in service composition standards. Secondly, the work assigns the semantics of compositions through the use of Labelled Transition Systems (LTS) in the form of Finite State Processes (FSP). Thirdly, an environment is described forming a tool to assist in undertaking the approach.</p>
			</richtext>
		</abstract>
		<title type="sharef:primaryTitle">Web Service Compositions: From XML Syntax to Service Models</title>
		<identifier type="sharef:uri" resourceType="text/html">http://www.idealliance.org/proceedings/xml05/abstracts/paper38.HTML</identifier>
	</reference>
	<reference name="bra05" src="bibtex:inproceedings" src-info="bibtex:line-9134" type="sharef:inproceedings" crossref="xml2005">
		<names type="sharef:author">
			<person>
				<givenname>Tim</givenname>
				<surname>Bray</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Next year, the notion of building your own markup language for your own application, while still conforming to a standard, will be 20 years old. During that twenty years, a huge number of custom languages — at least hundreds, perhaps a couple of thousand — have been attempted. Almost all have been miserable failures. That is to say, the vast majority have failed to achieve wide adoption, and those that were adopted have often failed to achieve their goals, whether of reducing costs, enriching applications, or both. This paper examines this history of failure and draws conclusions about the decision process as to whether to proceed with language design, and, in the case that the design of a new language is undertaken, the trade-offs that obtain during that process.</p>
			</richtext>
		</abstract>
		<title type="sharef:primaryTitle">On Language Creation</title>
		<field type="bibtex:topic">xml[0.8]</field>
		<identifier type="sharef:uri" resourceType="text/html">http://www.idealliance.org/proceedings/xml05/abstracts/paper175.HTML</identifier>
	</reference>
	<reference name="xml2005" src="bibtex:proceedings" src-info="bibtex:line-9143" type="sharef:proceedings">
		<date value="2005-11"/>
		<address type="sharef:placePublished">Atlanta, Georgia</address>
		<field type="bibtex:index">XML 2005</field>
		<field type="bibtex:key">XML 2005</field>
		<title type="sharef:primaryTitle">XML 2005</title>
		<identifier type="sharef:uri">http://2005.xmlconference.org/</identifier>
	</reference>
	<reference name="rob06" src="bibtex:inproceedings" src-info="bibtex:line-9158" type="sharef:inproceedings" crossref="xml2006">
		<names type="sharef:author">
			<person>
				<givenname>Jonathan</givenname>
				<surname>Robie</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Many servlets do nothing more than integrate data from multiple sources to create an XML or HTML result. As an XML-oriented data integration language, XQuery is a particularly simple, productive, and efficient way to do this task. In this presentation, I show a servlet that provides a REST interface to any XQuery that a developer places in a secure deployment directory on an application server, then demonstrate the development of data services by writing XQueries that access XML, relational, and flat file formats such as EDI to create complex XML and HTML results, then copying to the deployment directory. In this environment, each XQuery inherently defines a REST interface. I will develop queries by dragging and dropping from relational, XML, and EDI (or other flat file formats) into the text of an XQuery, using a standard XQuery GUI environment, then copy queries into a deployment directory, and invoke them using a web browser. The servlet will run under Apache Tomcat. XML data is queried directly using XQuery, with an implement that uses document projection and streaming so that large XML files can be handled efficiently. Relational data is queried by converting XQuery to efficient SQL, executing the SQL, and returning the results as XML. EDI and flat file formats are queried by converting them physically to XML and querying them using the same document projection and streaming techniques used for querying XML documents. The REST interface to a query consists of the name of the servlet and URI parameters that identify the name of the query and the query's external variables. A query may also use the variable $content, which is bound to the content of an HTTP request if present. Preparing queries dramatically improves performance. Each time a query is invoked by a client, the servlet does the following: (1) If this query has been prepared and is up-to-date, the prepared query is used. If the query has not been prepared, or a more recent version of the query exists in the deployment directory, the query is prepared. (2) All URI parameters are bound to the query as external variables. (3) The query is executed, and query results are returned to the client.</p>
			</richtext>
		</abstract>
		<title type="sharef:primaryTitle">An XQuery Servlet for RESTful Data Services</title>
		<field type="bibtex:topic">rest[0.8] xquery[0.8]</field>
		<identifier type="sharef:uri" resourceType="text/html">http://2006.xmlconference.org/programme/presentations/87.html</identifier>
	</reference>
	<reference name="xml2006" src="bibtex:proceedings" src-info="bibtex:line-9167" type="sharef:proceedings">
		<date value="2006-12"/>
		<address type="sharef:placePublished">Boston, Massachusetts</address>
		<field type="bibtex:index">XML 2006</field>
		<field type="bibtex:key">XML 2006</field>
		<title type="sharef:primaryTitle">XML 2006</title>
		<identifier type="sharef:uri">http://2006.xmlconference.org/</identifier>
	</reference>
	<reference name="nor93" src="bibtex:inproceedings" src-info="bibtex:line-9182" type="sharef:inproceedings" crossref="er1993">
		<names type="sharef:author">
			<person>
				<givenname>Moira C.</givenname>
				<surname>Norrie</surname>
			</person>
		</names>
		<pages>390-401</pages>
		<title type="sharef:primaryTitle">An Extended Entity-Relationship Approach to Data Management in Object-Oriented Systems</title>
	</reference>
	<reference name="er1993" src="bibtex:proceedings" src-info="bibtex:line-9189" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>Ramez</givenname>
				<surname>Elmasri</surname>
			</person>
			<person>
				<givenname>Vram</givenname>
				<surname>Kouramajian</surname>
			</person>
			<person>
				<givenname>Bernhard</givenname>
				<surname>Thalheim</surname>
			</person>
		</names>
		<date value="1993-12"/>
		<address type="sharef:placePublished">Arlington, Texas</address>
		<field type="bibtex:index">ER 1993</field>
		<identifier type="sharef:isbn">3-540-58217-7</identifier>
		<publisher>Springer-Verlag</publisher>
		<title type="sharef:seriesTitle">Lecture Notes in Computer Science</title>
		<title type="sharef:primaryTitle">12th International Conference on the Entity-Relationship Approach</title>
		<identifier type="sharef:uri" resourceType="text/html">http://www.informatik.uni-trier.de/~ley/db/conf/er/er93.html</identifier>
		<volume>823</volume>
	</reference>
	<reference name="sis02" src="bibtex:inproceedings" src-info="bibtex:line-9208" type="sharef:inproceedings" crossref="er2002">
		<names type="sharef:author">
			<person>
				<givenname>Samira</givenname>
				<surname>Si-Said Cherfi</surname>
			</person>
			<person>
				<givenname>Jacky</givenname>
				<surname>Akoka</surname>
			</person>
			<person>
				<givenname>Isabelle</givenname>
				<surname>Comyn-Wattiau</surname>
			</person>
		</names>
		<pages>414-428</pages>
		<title type="sharef:primaryTitle">Conceptual Modeling Quality — From EER to UML Schemas Evaluation</title>
	</reference>
	<reference name="elm02" src="bibtex:inproceedings" src-info="bibtex:line-9215" type="sharef:inproceedings" crossref="er2002">
		<names type="sharef:author">
			<person>
				<givenname>Ramez</givenname>
				<surname>Elmasri</surname>
			</person>
			<person>
				<givenname>Yu-Chi</givenname>
				<surname>Wu</surname>
			</person>
			<person>
				<givenname>Babak</givenname>
				<surname>Hojabri</surname>
			</person>
			<person>
				<givenname>Charley</givenname>
				<surname>Li</surname>
			</person>
			<person>
				<givenname>Jack</givenname>
				<surname>Fu</surname>
			</person>
		</names>
		<pages>429-443</pages>
		<title type="sharef:primaryTitle">Conceptual Modeling for Customized XML Schemas</title>
		<identifier type="sharef:uri">http://portal.acm.org/citation.cfm?id=647525.726060</identifier>
	</reference>
	<reference name="low02" src="bibtex:inproceedings" src-info="bibtex:line-9223" type="sharef:inproceedings" crossref="er2002">
		<names type="sharef:author">
			<person>
				<givenname>David</givenname>
				<surname>Lowe</surname>
			</person>
			<person>
				<givenname>Brian</givenname>
				<surname>Henderson-Sellers</surname>
			</person>
			<person>
				<givenname>Alice</givenname>
				<surname>Gu</surname>
			</person>
		</names>
		<pages>105-119</pages>
		<title type="sharef:primaryTitle">Web Extensions to UML: Using the MVC Triad</title>
	</reference>
	<reference name="er2002" src="bibtex:proceedings" src-info="bibtex:line-9230" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>Stefano</givenname>
				<surname>Spaccapietra</surname>
			</person>
			<person>
				<givenname>Salvatore T.</givenname>
				<surname>March</surname>
			</person>
			<person>
				<givenname>Yahiko</givenname>
				<surname>Kambayashi</surname>
			</person>
		</names>
		<date value="2002-10"/>
		<address type="sharef:placePublished">Tampere, Finland</address>
		<field type="bibtex:index">ER 2002</field>
		<identifier type="sharef:isbn">3540442774</identifier>
		<publisher>Springer-Verlag</publisher>
		<title type="sharef:seriesTitle">Lecture Notes in Computer Science</title>
		<title type="sharef:primaryTitle">21st International Conference on Conceptual Modeling</title>
		<identifier type="sharef:uri" resourceType="text/html">http://www.informatik.uni-trier.de/%7Eley/db/conf/er/er2002.html</identifier>
		<volume>2503</volume>
	</reference>
	<reference name="cam03" src="bibtex:inproceedings" src-info="bibtex:line-9250" type="sharef:inproceedings" crossref="er2003">
		<names type="sharef:author">
			<person>
				<givenname>Sandro Daniel</givenname>
				<surname>Camillo</surname>
			</person>
			<person>
				<givenname>Carlos A.</givenname>
				<surname>Heuser</surname>
			</person>
			<person>
				<givenname>Ronaldo</givenname>
				<surname link="dos">Santos Mello</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>XML is a widespread W3C standard used by several kinds of applications for data representation and exchange over the web. In the context of a system that provides semantic integration of heterogeneous XML sources, the same information at a semantic level may have different representations in XML. However, the syntax of an XML query depends on the structure of the specific XML source. Therefore, in order to obtain the same query result, one must write a specific query for each XML source. To deal with such problem, a much better solution is to state queries against a global conceptual schema and then translate them into an XML query against each specific data source. This paper presents CXPath (Conceptual XPath), a language for querying XML sources at the conceptual level, as well as a translation mechanism that converts a CXPath query to an XPath query against a specific XML source.</p>
			</richtext>
		</abstract>
		<pages>186-199</pages>
		<title type="sharef:primaryTitle">Querying Heterogeneous XML Sources through a Conceptual Schema</title>
		<field type="bibtex:topic">cxpath[1]</field>
		<identifier type="sharef:uri">http://springerlink.metapress.com/link.asp?id=rm1nv2yg65p9wnr5</identifier>
	</reference>
	<reference name="fon03" src="bibtex:inproceedings" src-info="bibtex:line-9260" type="sharef:inproceedings" crossref="er2003">
		<names type="sharef:author">
			<person>
				<givenname>Joan</givenname>
				<surname>Fons</surname>
			</person>
			<person>
				<givenname>Vicente</givenname>
				<surname>Pelechano</surname>
			</person>
			<person>
				<givenname>Manoli</givenname>
				<surname>Albert</surname>
			</person>
			<person>
				<givenname>Oscar</givenname>
				<surname>Pastor</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>This work presents an OO software production method that defines a systematic process for conceptual modelling of web applications. The paper discusses a set of minimum primitives to capture the essentials of dynamic web applications and it discusses how to introduce them in a classical model-centered OO method that provides systematic code generation. Finally, the paper presents some ideas to extend this generation process for developing web solutions taking as an input these web enhanced conceptual schemas.</p>
			</richtext>
		</abstract>
		<pages>232-245</pages>
		<title type="sharef:primaryTitle">Development of Web Applications from Web Enhanced Conceptual Schemas</title>
		<identifier type="sharef:uri">http://springerlink.metapress.com/link.asp?id=d15wa7q7p3wdrkmg</identifier>
	</reference>
	<reference name="yan03" src="bibtex:inproceedings" src-info="bibtex:line-9269" type="sharef:inproceedings" crossref="er2003">
		<names type="sharef:author">
			<person>
				<givenname>Xia</givenname>
				<surname>Yang</surname>
			</person>
			<person>
				<givenname>Mong-Li</givenname>
				<surname>Lee</surname>
			</person>
			<person>
				<givenname>Tok Wang</givenname>
				<surname>Ling</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>While the Internet has facilitated access to information sources, the task of scalable integration of these heterogeneous data sources remains a challenge. The adoption of the Extensible Markup Language (XML) as the standard for data representation and exchange has led to an increasing number of XML data sources, both native and non-native. Recent integration work has mainly focused on developing matching techniques to find equivalent elements and attributes among the different XML sources. In this paper, we introduce a semantic approach to resolve structural conflicts in the integration of XML schemas. We employ a data model called the ORA-SS (Object-Relationship-Attribute Model for Semi-Structured Data) to capture the implicit semantics in an XML schema. We present a comprehensive algorithm to integrate XML schemas. Compared to existing methods, our algorithm adopts an n-nary integration strategy that takes into account the data semantics, importance of a source, and how the majority of the sources model their data when resolving structural conflicts such as attribute/object class conflict and ancestor-descendant conflict. Further, redundant object classes and transitive relationship sets are removed to obtain a more concise integrated schema.</p>
			</richtext>
		</abstract>
		<pages>520-533</pages>
		<title type="sharef:primaryTitle">Resolving Structural Conflicts in the Integration of XML Schemas: A Semantic Approach</title>
		<field type="bibtex:topic">orass[1]</field>
		<identifier type="sharef:uri">http://springerlink.metapress.com/link.asp?id=mjcvmt73rhpr5u1b</identifier>
	</reference>
	<reference name="sak03" src="bibtex:inproceedings" src-info="bibtex:line-9279" type="sharef:inproceedings" crossref="er2003">
		<names type="sharef:author">
			<person>
				<givenname>Bipin C.</givenname>
				<surname>Sakamuri</surname>
			</person>
			<person>
				<givenname>Sanjay Kumar</givenname>
				<surname>Madria</surname>
			</person>
			<person>
				<givenname>Kalpdrum</givenname>
				<surname>Passi</surname>
			</person>
			<person>
				<givenname>Eric</givenname>
				<surname>Chaudhry</surname>
			</person>
			<person>
				<givenname>Mukesh K.</givenname>
				<surname>Mohania</surname>
			</person>
			<person>
				<givenname>Sourav S.</givenname>
				<surname>Bhowmick</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>The availability of large amounts of heterogeneous distributed web data necessitates the integration and querying of XML data from multiple XML sources for many reasons. For example, currently many government agencies in US such as IRS, INS, FBI, CIA are integrating their system to deal with new security threats, and these different departments uses legacy database systems including relational data, flat files, spreadsheets, and html pages, and simple text data. Similarly, there are many e-commerce companies, which sell similar products but represent data using different XML schemas. When any two such companies merge, or make an effort to service customers in cooperation, there is a need for a uniform schema integration methodology. In some applications like comparison-shopping, there is a need for an illusionary centralized homogeneous information system. Such systems need a uniform data representation and access platform, which is provided by XML. However, the XML schema and data are still heterogeneous and represent their constraints differently. To avoid the overhead of system integration and system specific data access mechanisms, applications should be provided with data in an integrated form. The idea is to use XML as an intermediate medium to achieve date integration from heterogeneous data resources. There are many efforts currently on generating views or representing data in only XML format, but internally stored in legacy databases. Using wrappers, applications can view the data in XML, instead of moving the data from their original format to XML. However, wrappers fail if the structure of the data is dynamically changed. Our approach is two phase; the integration of the local XML schemas into a global schema, and the integration of the resultant XML data produced in response to the queries to the local XML data sources. A global schema eliminates data model differences by integrating local schemas. The heterogeneous XML data sources need not be represented in an integrated fashion. This is because integrating the XML data and storing it in the new integrated schema occupies extra resources, and may result in duplication, and thus, creates the problems of multiple updates and data inconsistencies. For this reason, we present a dynamic mechanism, which can interface the different XML data and can present an integrated representation of the XML sources, rather than physically integration of data.</p>
			</richtext>
		</abstract>
		<pages>576-578</pages>
		<title type="sharef:primaryTitle">AXIS: A XML Schema Integration System</title>
		<field type="bibtex:topic">axis[1]</field>
		<identifier type="sharef:uri">http://springerlink.metapress.com/link.asp?id=rg4ea04c6vkjyqaw</identifier>
	</reference>
	<reference name="psa03" src="bibtex:inproceedings" src-info="bibtex:line-9289" type="sharef:inproceedings" crossref="er2003ws">
		<names type="sharef:author">
			<person>
				<givenname>Giuseppe</givenname>
				<surname>Psaila</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>The need for managing large repositories of data coming from XML documents is increasing; in fact, XML is emerging as the standard format for documents exchanged over the internet. At University of Bergamo, recently we developed the ERX Data Management System, to study issues concerning the management of data coming from XML documents; its data model, called ERX (Entity Relationship for XML), being an extension of the classical ER model, allows to deal with concepts coming from XML documents at the conceptual level, and allows to reason about integration of data coming from different XML document classes. This paper focuses on the problem of automatically deriving Entity-Relationship Schemas (ERX Schemas) from DTDs (Document Type Definition). In fact, the derivation of such schemas from DTDs might be a hard work to do by hand, since real DTDs are very complex and large.</p>
			</richtext>
		</abstract>
		<pages>378-389</pages>
		<title type="sharef:primaryTitle">From XML DTDs to Entity-Relationship Schemas</title>
		<field type="bibtex:topic">erx[0.9] dtd[0.7] er[0.7]</field>
		<identifier type="sharef:uri">http://www.springerlink.com/link.asp?id=0wc1p4mdvc9ww5te</identifier>
	</reference>
	<reference name="lu03" src="bibtex:inproceedings" src-info="bibtex:line-9299" type="sharef:inproceedings" crossref="er2003ws">
		<names type="sharef:author">
			<person>
				<givenname>Shiyong</givenname>
				<surname>Lu</surname>
			</person>
			<person>
				<givenname>Yezhou</givenname>
				<surname>Sun</surname>
			</person>
			<person>
				<givenname>Mustafa</givenname>
				<surname>Atay</surname>
			</person>
			<person>
				<givenname>Farshad</givenname>
				<surname>Fotouhi</surname>
			</person>
		</names>
		<pages>250-260</pages>
		<title type="sharef:primaryTitle">A Sufficient and Necessary Condition for the Consistency of XML DTDs</title>
		<field type="bibtex:topic">dtd[0.8]</field>
	</reference>
	<reference name="guo03" src="bibtex:inproceedings" src-info="bibtex:line-9307" type="sharef:inproceedings" crossref="er2003ws">
		<names type="sharef:author">
			<person>
				<givenname>Zhimao</givenname>
				<surname>Guo</surname>
			</person>
			<person>
				<givenname>Zhengchuan</givenname>
				<surname>Xu</surname>
			</person>
			<person>
				<givenname>Shuigeng</givenname>
				<surname>Zhou</surname>
			</person>
			<person>
				<givenname>Aoying</givenname>
				<surname>Zhou</surname>
			</person>
			<person>
				<givenname>Ming</givenname>
				<surname>Li</surname>
			</person>
		</names>
		<pages>261-272</pages>
		<title type="sharef:primaryTitle">Index Selection for Efficient XML Path Expression Processing</title>
		<field type="bibtex:topic">xpath1[0.8]</field>
	</reference>
	<reference name="erw03" src="bibtex:inproceedings" src-info="bibtex:line-9315" type="sharef:inproceedings" crossref="er2003ws">
		<names type="sharef:author">
			<person>
				<givenname>Martin</givenname>
				<surname>Erwig</surname>
			</person>
		</names>
		<pages>342-354</pages>
		<title type="sharef:primaryTitle">Toward the Automatic Derivation of XML Transformations</title>
		<field type="bibtex:topic">xslt1[0.8]</field>
	</reference>
	<reference name="er2003" src="bibtex:proceedings" src-info="bibtex:line-9323" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>Il-Yeol</givenname>
				<surname>Song</surname>
			</person>
			<person>
				<givenname>Stephen W.</givenname>
				<surname>Liddle</surname>
			</person>
			<person>
				<givenname>Tok Wang</givenname>
				<surname>Ling</surname>
			</person>
			<person>
				<givenname>Peter</givenname>
				<surname>Scheuermann</surname>
			</person>
		</names>
		<date value="2003-10"/>
		<address type="sharef:placePublished">Chicago, Illinois</address>
		<field type="bibtex:index">ER 2003</field>
		<identifier type="sharef:isbn">3-540-20299-4</identifier>
		<publisher>Springer-Verlag</publisher>
		<title type="sharef:seriesTitle">Lecture Notes in Computer Science</title>
		<title type="sharef:primaryTitle">22nd International Conference on Conceptual Modeling</title>
		<identifier type="sharef:uri" resourceType="text/html">http://www.informatik.uni-trier.de/~ley/db/conf/er/er2003.html</identifier>
		<volume>2813</volume>
	</reference>
	<reference name="er2003ws" src="bibtex:proceedings" src-info="bibtex:line-9338" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>Manfred A.</givenname>
				<surname>Jeusfeld</surname>
			</person>
			<person>
				<givenname>Óscar</givenname>
				<surname>Pastor</surname>
			</person>
		</names>
		<date value="2003-10"/>
		<address type="sharef:placePublished">Chicago, Illinois</address>
		<field type="bibtex:index">ER 2003</field>
		<identifier type="sharef:isbn">3540202579</identifier>
		<publisher>Springer-Verlag</publisher>
		<title type="sharef:seriesTitle">Lecture Notes in Computer Science</title>
		<title type="sharef:primaryTitle">Conceptual Modeling for Novel Application Domains, ER 2003 Workshop Proceedings</title>
		<identifier type="sharef:uri">http://www.springerlink.com/link.asp?id=g0bnakutjq4b</identifier>
		<volume>2814</volume>
	</reference>
	<reference name="dav04" src="bibtex:inproceedings" src-info="bibtex:line-9357" type="sharef:inproceedings" crossref="er2004">
		<names type="sharef:author">
			<person>
				<givenname>Islay</givenname>
				<surname>Davies</surname>
			</person>
			<person>
				<givenname>Peter</givenname>
				<surname>Green</surname>
			</person>
			<person>
				<givenname>Michael</givenname>
				<surname>Rosemann</surname>
			</person>
			<person>
				<givenname>Stan</givenname>
				<surname>Gallo</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Much research has been devoted over the years to investigating and advancing the techniques and tools used by analysts when they model. As opposed to what academics, software providers and their resellers promote as should be happening, the aim of this research was to determine whether practitioners still embraced conceptual modelling seriously. In addition, what are the most popular techniques and tools used for conceptual modelling? What are the major purposes for which conceptual modelling is used? The study found that the top six most frequently used modelling techniques and methods were ER diagramming, data flow diagramming, systems flowcharting, workflow modelling, RAD, and UML. However, the primary contribution of this study was the identification of the factors that uniquely influence the continued-use decision of analysts, viz., communication (using diagrams) to/from stakeholders, internal knowledge (lack of) of techniques, user expectations management, understanding models integration into the business, and tool/software deficiencies.</p>
			</richtext>
		</abstract>
		<pages>30-42</pages>
		<title type="sharef:primaryTitle">Conceptual Modelling — What and Why in Current Practice</title>
		<identifier type="sharef:uri">http://springerlink.metapress.com/link.asp?id=ha8ekn3a123p6599</identifier>
	</reference>
	<reference name="emb04" src="bibtex:inproceedings" src-info="bibtex:line-9366" type="sharef:inproceedings" crossref="er2004">
		<names type="sharef:author">
			<person>
				<givenname>David W.</givenname>
				<surname>Embley</surname>
			</person>
			<person>
				<givenname>Stephen W.</givenname>
				<surname>Liddle</surname>
			</person>
			<person>
				<givenname>Reema</givenname>
				<surname>Al-Kamha</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>An open challenge is to integrate XML and conceptual modeling in order to satisfy large-scale enterprise needs. Because enterprises typically have many data sources using different assumptions, formats, and schemas, all expressed in — or soon to be expressed in — XML, it is easy to become lost in an avalanche of XML detail. This creates an opportunity for the conceptual modeling community to provide improved abstractions to help manage this detail. We present a vision for Conceptual XML (C-XML) that builds on the established work of the conceptual modeling community over the last several decades to bring improved modeling capabilities to XML-based development. Building on a framework such as C-XML will enable better management of enterprise-scale data and more rapid development of enterprise applications.</p>
			</richtext>
		</abstract>
		<pages>150-165</pages>
		<title type="sharef:primaryTitle">Enterprise Modeling with Conceptual XML</title>
		<field type="bibtex:topic">conceptualxml[0.9]</field>
		<identifier type="sharef:uri">http://springerlink.metapress.com/link.asp?id=wq6qpbbgrb3r53v9</identifier>
	</reference>
	<reference name="er2004" src="bibtex:proceedings" src-info="bibtex:line-9376" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>Paolo</givenname>
				<surname>Atzeni</surname>
			</person>
			<person>
				<givenname>Wesley W.</givenname>
				<surname>Chu</surname>
			</person>
			<person>
				<givenname>Hongjun</givenname>
				<surname>Lu</surname>
			</person>
			<person>
				<givenname>Shuigeng</givenname>
				<surname>Zhou</surname>
			</person>
			<person>
				<givenname>Tok Wang</givenname>
				<surname>Ling</surname>
			</person>
		</names>
		<date value="2004-11"/>
		<address type="sharef:placePublished">Shanghai</address>
		<identifier type="sharef:doi">10.1007/b101693</identifier>
		<field type="bibtex:index">ER 2004</field>
		<identifier type="sharef:isbn">3-540-23723-2</identifier>
		<publisher>Springer-Verlag</publisher>
		<title type="sharef:seriesTitle">Lecture Notes in Computer Science</title>
		<title type="sharef:primaryTitle">23rd International Conference on Conceptual Modeling</title>
		<identifier type="sharef:uri" resourceType="text/html">http://www.springeronline.com/sgw/cda/frontpage/0,11855,2-164-22-35783377-0,00.html</identifier>
		<volume>3288</volume>
	</reference>
	<reference name="sig07" src="bibtex:inproceedings" src-info="bibtex:line-9396" type="sharef:inproceedings" crossref="er2007">
		<names type="sharef:author">
			<person>
				<givenname>Beat</givenname>
				<surname>Signer</surname>
			</person>
			<person>
				<givenname>Moira C.</givenname>
				<surname>Norrie</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Many hypermedia models have been proposed, including those specifically developed to model navigational aspects of web sites. But few hypermedia systems have been implemented based on metamodelling principles familiar to the database community. Often there is no clear separation between conceptual and technical issues in the models and their implementations are not based on an explicit representation of a metamodel. This results in a loss of generality and uniformity across systems. Based on principles of metamodel-driven system development, we have implemented a platform that can support various categories of hypermedia systems through the generality and extensibility of the metamodel. We present our metamodel and show how it generalises concepts present in a range of hypermedia and link server systems.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1007/978-3-540-75563-0_25</identifier>
		<pages>359-374</pages>
		<title type="sharef:primaryTitle">As We May Link: A General Metamodel for Hypermedia Systems</title>
		<identifier type="sharef:uri">http://www.springerlink.com/content/gm0442v877705m02/</identifier>
	</reference>
	<reference name="er2007" src="bibtex:proceedings" src-info="bibtex:line-9406" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>Christine</givenname>
				<surname>Parent</surname>
			</person>
			<person>
				<givenname>Klaus-Dieter</givenname>
				<surname>Schewe</surname>
			</person>
			<person>
				<givenname>Veda C.</givenname>
				<surname>Storey</surname>
			</person>
			<person>
				<givenname>Bernhard</givenname>
				<surname>Thalheim</surname>
			</person>
		</names>
		<date value="2007-11"/>
		<address type="sharef:placePublished">Auckland, New Zealand</address>
		<field type="bibtex:index">ER 2007</field>
		<identifier type="sharef:isbn">978-3-540-75562-3</identifier>
		<publisher>Springer-Verlag</publisher>
		<title type="sharef:seriesTitle">Lecture Notes in Computer Science</title>
		<title type="sharef:primaryTitle">26th International Conference on Conceptual Modeling</title>
		<identifier type="sharef:uri" resourceType="text/html">http://www.informatik.uni-trier.de/~ley/db/conf/er/erw2007.html</identifier>
		<volume>4801</volume>
	</reference>
	<reference name="er2004ws" src="bibtex:proceedings" src-info="bibtex:line-9425" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>Shan</givenname>
				<surname>Wang</surname>
			</person>
			<person>
				<givenname>Katsumi</givenname>
				<surname>Tanaka</surname>
			</person>
			<person>
				<givenname>Shuigeng</givenname>
				<surname>Zhou</surname>
			</person>
			<person>
				<givenname>Tok Wang</givenname>
				<surname>Ling</surname>
			</person>
			<person>
				<givenname>Jihong</givenname>
				<surname>Guan</surname>
			</person>
		</names>
		<date value="2004-11"/>
		<address type="sharef:placePublished">Shanghai</address>
		<field type="bibtex:index">ER 2004</field>
		<identifier type="sharef:isbn">3-540-23722-4</identifier>
		<publisher>Springer-Verlag</publisher>
		<title type="sharef:seriesTitle">Lecture Notes in Computer Science</title>
		<title type="sharef:primaryTitle">Conceptual Modeling for Novel Application Domains, ER 2004 Workshop Proceedings</title>
		<identifier type="sharef:uri" resourceType="text/html">http://www.springeronline.com/sgw/cda/frontpage/0,11855,2-164-22-35890088-0,00.html</identifier>
		<volume>3289</volume>
	</reference>
	<reference name="alk05" src="bibtex:inproceedings" src-info="bibtex:line-9444" type="sharef:inproceedings" crossref="emisa05">
		<names type="sharef:author">
			<person>
				<givenname>Reema</givenname>
				<surname>Al-Kamha</surname>
			</person>
			<person>
				<givenname>David W.</givenname>
				<surname>Embley</surname>
			</person>
			<person>
				<givenname>Stephen W.</givenname>
				<surname>Liddle</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>XML is an effective universal data-interchange format, and XML Schema has become the preeminent mechanism for describing valid XML document structures. Generalization/specialization and its constraints are fundamental concepts in system modeling and design, but are difficult to express and enforce with XML Schema. This mismatch leads to unnecessary complexity and uncertainty in XML-based models. In this paper we describe how to translate various aspects of generalization/specialization from a conceptual model into XML Schema. We also explore what needs to be added to XML Schema to handle the other aspects of this fundamental modeling construct. If XML Schema were to include our proposed constructs, it would be fully capable of faithfully representing generalization/specialization, thus reducing the complexity of the XML models that rely on generalization/specialization.</p>
			</richtext>
		</abstract>
		<pages>93-104</pages>
		<title type="sharef:primaryTitle">Representing Generalization/Specialization in XML Schema</title>
		<field type="bibtex:topic">conceptualxml[0.8]</field>
		<identifier type="sharef:uri" resourceType="application/pdf">http://www.deg.byu.edu/papers/emisa05alkamha.pdf</identifier>
	</reference>
	<reference name="emisa05" src="bibtex:proceedings" src-info="bibtex:line-9454" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>Jörg</givenname>
				<surname>Desel</surname>
			</person>
			<person>
				<givenname>Ulrich</givenname>
				<surname>Frank</surname>
			</person>
		</names>
		<date value="2005-10"/>
		<address type="sharef:placePublished">Klagenfurt, Austria</address>
		<field type="bibtex:index">EMISA'05</field>
		<identifier type="sharef:isbn">3-88579-404-7</identifier>
		<publisher>Gesellschaft für Informatik</publisher>
		<title type="sharef:seriesTitle">Lecture Notes in Informatics</title>
		<title type="sharef:primaryTitle">Enterprise Modelling and Information Systems Architectures</title>
		<identifier type="sharef:uri">http://www.gi-ev.de/service/publikationen/gi-edition-lecture-notes-in-informatics-lni-2005/mehr-zu-diesem-buch/gi-edition-lecture-notes-in-informatics-lni-p-75/</identifier>
		<volume>75</volume>
	</reference>
	<reference name="han02b" src="bibtex:inproceedings" src-info="bibtex:line-9473" type="sharef:inproceedings" crossref="xsw2002">
		<names type="sharef:author">
			<person>
				<givenname>Arne</givenname>
				<surname>Handt</surname>
			</person>
			<person>
				<givenname>Joachim</givenname>
				<surname>Quantz</surname>
			</person>
		</names>
		<pages>93-104</pages>
		<title type="sharef:primaryTitle">XML Schema Correspondences</title>
		<field type="bibtex:topic">xsd[0.7]</field>
	</reference>
	<reference name="xsw2002" src="bibtex:proceedings" src-info="bibtex:line-9481" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>Robert</givenname>
				<surname>Tolksdorf</surname>
			</person>
			<person>
				<givenname>Rainer</givenname>
				<surname>Eckstein</surname>
			</person>
		</names>
		<date value="2002-06"/>
		<address type="sharef:placePublished">Berlin, Germany</address>
		<field type="bibtex:index">XSW 2002</field>
		<identifier type="sharef:isbn">3-88579-343-1</identifier>
		<publisher>Gesellschaft für Informatik</publisher>
		<title type="sharef:seriesTitle">Lecture Notes in Informatics</title>
		<title type="sharef:primaryTitle">XSW 2002 — XML Technologien für das Semantic Web</title>
		<identifier type="sharef:uri" resourceType="text/html">http://www.informatik.uni-trier.de/~ley/db/conf/xsw/xsw2002.html</identifier>
		<identifier type="sharef:uri">http://www.gi-ev.de/LNI/proceedings/P-14.shtml</identifier>
		<volume>14</volume>
	</reference>
	<reference name="wil04i" src="bibtex:inproceedings" src-info="bibtex:line-9501" type="sharef:inproceedings" crossref="bxml2004">
		<names type="sharef:author">
			<person>
				<givenname>Erik</givenname>
				<surname>Wilde</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>The Extensible Markup Language (XML) is based on the concept of schema languages, which are used for validation of XML documents. In most cases, the metamodeling view of XML-based application is rather simple, with XML documents being instances of some schema, which in turn is based on some schema language. In this paper, a metaschema layering approach for XML is presented, which is demonstrated in the context of various application scenarios. This approach is based on two generalizations of the standard XML schema language usage scenario: (1) it is assumed that one or more schema languages are acceptable as foundations for an XML scenario, but these schema languages should be customized by restricting, extending, or combining them; (2) for applications requiring application-specific schema languages, these schema languages can be implemented by reusing existing schema languages, thus introducing an additional metaschema layer. Metaschema layering can be used in a variety of application areas, and this paper shows some possible applications and mentions some more possibilities. XML is increasingly entering the modeling domain, since it is gradually moving from an exchange format for structured data into the applications as their inherent model. XML modeling still is in its infancy, and the metaschema layering approach presented in this paper is one contribution how to leverage the most important of XML feature's, which is the reuse of existing concepts and implementations.</p>
			</richtext>
		</abstract>
		<pages>106-120</pages>
		<title type="sharef:primaryTitle">Metaschema Layering for XML</title>
		<field type="bibtex:topic">xsd[0.7] schematron[0.7] crvx[0.7]</field>
		<identifier type="sharef:uri">http://dret.net/netdret/publications#wil04i</identifier>
	</reference>
	<reference name="gro04" src="bibtex:inproceedings" src-info="bibtex:line-9511" type="sharef:inproceedings" crossref="bxml2004">
		<names type="sharef:author">
			<person>
				<givenname>Sven</givenname>
				<surname>Groppe</surname>
			</person>
			<person>
				<givenname>Stefan</givenname>
				<surname>Böttcher</surname>
			</person>
		</names>
		<pages>53-64</pages>
		<title type="sharef:primaryTitle">Query Reformulation for the XML Standards XPath, XQuery and XSLT</title>
		<field type="bibtex:topic">xpath2[0.7] xquery[0.7] xslt2[0.7]</field>
	</reference>
	<reference name="bxml2004" src="bibtex:proceedings" src-info="bibtex:line-9519" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>Robert</givenname>
				<surname>Tolksdorf</surname>
			</person>
			<person>
				<givenname>Rainer</givenname>
				<surname>Eckstein</surname>
			</person>
		</names>
		<date value="2004-10"/>
		<address type="sharef:placePublished">Berlin, Germany</address>
		<field type="bibtex:index">XSW 2004</field>
		<identifier type="sharef:isbn">3-88597-112-6</identifier>
		<title type="sharef:primaryTitle">Berliner XML Tage 2004</title>
	</reference>
	<reference name="wil05r" src="bibtex:inproceedings" src-info="bibtex:line-9534" type="sharef:inproceedings" crossref="bxml2005">
		<names type="sharef:author">
			<person>
				<givenname>Erik</givenname>
				<surname>Wilde</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Today, XML is primarily regarded as a syntax for exchanging structured data, and therefore the question of how to develop well-designed XML models has not been studied extensively. As applications are increasingly penetrated by XML technologies, and because query and programming languages provide native XML support, it would be beneficial to use these features to work with well-designed XML models. In order to better focus on XML-oriented technologies in systems engineering and programming languages, an XML modeling language should be used, which is more focused on modeling and structure than typical XML schema languages. In this paper, we examine the current state of the art in XML schema languages and XML modeling, and present a list of requirements for a XML conceptual modeling language.</p>
			</richtext>
		</abstract>
		<pages>213-224</pages>
		<title type="sharef:primaryTitle">Towards Conceptual Modeling for XML</title>
		<field type="bibtex:topic">xml[0.7]</field>
		<identifier type="sharef:uri">http://dret.net/netdret/publications#wil05r</identifier>
	</reference>
	<reference name="bxml2005" src="bibtex:proceedings" src-info="bibtex:line-9544" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>Rainer</givenname>
				<surname>Eckstein</surname>
			</person>
			<person>
				<givenname>Robert</givenname>
				<surname>Tolksdorf</surname>
			</person>
		</names>
		<date value="2005-09"/>
		<address type="sharef:placePublished">Berlin, Germany</address>
		<identifier type="sharef:isbn">3-9810105-2-3</identifier>
		<title type="sharef:primaryTitle">Berliner XML Tage 2005</title>
		<identifier type="sharef:uri">http://www.xml-clearinghouse.de/ws/BXML2005/</identifier>
		<identifier type="sharef:uri" resourceType="text/html">http://www.informatik.uni-trier.de/~ley/db/conf/bxml/bxml2005.html</identifier>
	</reference>
	<reference name="wil07l" src="bibtex:inproceedings" src-info="bibtex:line-9560" type="sharef:inproceedings" crossref="bxml2007">
		<names type="sharef:author">
			<person>
				<givenname>Erik</givenname>
				<surname>Wilde</surname>
			</person>
			<person>
				<givenname>Philippe</givenname>
				<surname>Cattin</surname>
			</person>
			<person>
				<givenname>Felix</givenname>
				<surname>Michel</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>The management and publishing of complex presentations is poorly supported by available presentation software. This makes it hard to publish usable and accessible presentation material, and to reuse that material for continuously evolving events. XSLidy provides an XSLT-based approach to generate presentations out of a mix of general-purpose HTML and a small number of presentation-specific structural elements. Using XSLidy, the management and reuse of complex presentations becomes easier, and the results are more user-friendly in terms of usability and accessibility.</p>
			</richtext>
		</abstract>
		<title type="sharef:primaryTitle">Web-Based Presentations</title>
		<field type="bibtex:topic">xslidy[0.9]</field>
		<identifier type="sharef:uri">http://dret.net/netdret/publications#wil07l</identifier>
	</reference>
	<reference name="bxml2007" src="bibtex:proceedings" src-info="bibtex:line-9569" type="sharef:proceedings">
		<date value="2007-09"/>
		<address type="sharef:placePublished">Berlin, Germany</address>
		<title type="sharef:primaryTitle">Berliner XML Tage 2007</title>
		<identifier type="sharef:uri">http://www.xml-clearinghouse.de/ws/XMLT2007/</identifier>
	</reference>
	<reference name="kle01" src="bibtex:inproceedings" src-info="bibtex:line-9582" type="sharef:inproceedings" crossref="gi2001">
		<names type="sharef:author">
			<person>
				<givenname>Carsten</givenname>
				<surname>Kleiner</surname>
			</person>
			<person>
				<givenname>Udo W.</givenname>
				<surname>Lipeck</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>The goal of this article is to present an algorithm to simplify the automatic generation of descriptions of XML document structures. In particular we show how to obtain a DTD (document type definition) for data whose structure is described by a conceptual data model. An important objective of this translation is to preserve as much structural information from the conceptual schema as possible. This enables partial constraint checking by validating XML parsers and thus simplifies exchange of data between different databases, in particular the import of data in an XML document into another database schema. In detail we present translations of all constructs of an extended entity-relationship model to DTDs and integrate these into an algorithm. By basing the algorithm on conceptual schemas it is very general and may be customized for data in (object-)relational databases as well as data in databases of any other paradigm, e.g. native XML databases.</p>
			</richtext>
		</abstract>
		<pages>396-405</pages>
		<title type="sharef:primaryTitle">Automatic Generation of XML DTDs from Conceptual Database Schemas</title>
		<identifier type="sharef:uri" resourceType="application/pdf">http://dbs.uni-leipzig.de/webdb/wien/015.pdf</identifier>
	</reference>
	<reference name="gi2001" src="bibtex:proceedings" src-info="bibtex:line-9591" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>Kurt</givenname>
				<surname>Bauknecht</surname>
			</person>
			<person>
				<givenname>Wilfried</givenname>
				<surname>Brauer</surname>
			</person>
			<person>
				<givenname>Thomas A.</givenname>
				<surname>Mück</surname>
			</person>
		</names>
		<date value="2001-09"/>
		<address type="sharef:placePublished">Vienna, Austria</address>
		<field type="bibtex:index">GI 2001</field>
		<identifier type="sharef:isbn">3-85403-157-2</identifier>
		<title type="sharef:primaryTitle">Tagungsband der GI/OCG-Jahrestagung</title>
		<identifier type="sharef:uri" resourceType="text/html">http://www.informatik.uni-trier.de/~ley/db/conf/gi/gi2001-1.html</identifier>
	</reference>
	<reference name="psa02" src="bibtex:inproceedings" src-info="bibtex:line-9607" type="sharef:inproceedings" crossref="edbtw2002">
		<names type="sharef:author">
			<person>
				<givenname>Giuseppe</givenname>
				<surname>Psaila</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>The need for managing large repositories of data coming from XML documents is increasing, in particular to support new EDI applications and information systems which provide e-commerce functionality. In fact, XML is emerging as the standard format for documents exchanged over the internet; then information systems will have to deal with XML documents, both incoming and outcoming. This is an exciting research area, because new technologies are arising, such as XSLT, but former and rather stable technologies, such as relational DBMSs, still have to play an important role. It is clear that novel information systems will integrate different technologies, but at the moment it is not clear how. This paper reports about our experience in developing the ERX Data Management System, a system devised to collect data coming from different XML data sources, and store them into a database in a way independent of the source format; its query language, named ERX-QL, is able to query the database and generate new XML documents. We developed the ERX Data Management System to explore the possibility of integrating three different basic technologies, Relational DBMS, Java and XSLT, under a unifying framework which makes the system interoperable w.r.t. the particular adopted technology (for example Relational vs Object-Oriented database technology); hence, this framework is based on an Entity-Relationship-like Data Model (ERX), which is not tied to any specific technical and/or commercial solution. The paper discusses the architecture of the ERX system, and the adopted technical solutions.</p>
			</richtext>
		</abstract>
		<pages>242-265</pages>
		<title type="sharef:primaryTitle">ERX: An Experience in Integrating Entity-Relationship Models, Relational Databases, and XML Technologies</title>
		<field type="bibtex:topic">erx[0.9]</field>
		<identifier type="sharef:uri">http://springerlink.metapress.com/link.asp?id=xypr4brnumplh7dc</identifier>
	</reference>
	<reference name="kem02" src="bibtex:inproceedings" src-info="bibtex:line-9617" type="sharef:inproceedings" crossref="edbtw2002">
		<names type="sharef:author">
			<person>
				<givenname>Martin</givenname>
				<surname>Kempa</surname>
			</person>
			<person>
				<givenname>Volker</givenname>
				<surname>Linnemann</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>XML Schemas provide a generalization of Document Type Definitions for describing the validity of a set of XML documents. There is a growing number of applications that deal with XML documents in various respects. One area of programs is concerned with analyzing XML documents arriving, for example, over the internet. Another rapidly expanding area is best described by the term XML generators. XML generators usually are part of a WWW system, for example generators for XML documents serving as views of data bases. Although XML Schemas provide a concise means for describing the syntax of correct XML documents in a specific domain, XML generators usually treat the XML documents as unstructured strings or, in the context of the Document Object Model, as trees the nodes of which belong to an unspecific Element-interface. The syntactical correctness, i.e. the validity of the generated XML documents cannot be guaranteed at compile time but must be tested at runtime. This means that, in general, t here is no ultimate proof that an XML generator generates only valid documents according to an underlying XML schema. This paper addresses this problem by introducing a new distinct interface for each element defined within an XML schema. Each interface extends the Element-interface of the Document Object Model. This mechanism provides a generalization of a previous approach based on the weaker concept of Document Type Definitions presented by the authors.</p>
			</richtext>
		</abstract>
		<pages>67-90</pages>
		<title type="sharef:primaryTitle">XML-Based Applications Using XML Schema</title>
		<field type="bibtex:topic">xsd[0.7] vdom[0.9]</field>
		<identifier type="sharef:uri">http://springerlink.metapress.com/link.asp?id=fl6rbbfx7dltwhf5</identifier>
	</reference>
	<reference name="pan02" src="bibtex:inproceedings" src-info="bibtex:line-9627" type="sharef:inproceedings" crossref="edbtw2002">
		<names type="sharef:author">
			<person>
				<givenname>Tadeusz</givenname>
				<surname>Pankowski</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>The goal of this paper is to propose a method in which relational database system is used to process queries on semistructured data. The method uses a combination of relational and semistructured techniques to process XML documents. First, the document is entirely stored within the relational system. Next, an SQL query is evaluated over the relational data representing XML document. Finally, the resulting XML document is constructed which, in turn, can be represented in the standard way within relational database system (by means of an edge table). The proposed method is presented as the XML-SQL language. The language is described formally and by a number of examples. Some implementation solutions are described.</p>
			</richtext>
		</abstract>
		<pages>184-209</pages>
		<title type="sharef:primaryTitle">XML-SQL: An XML Query Language Based on SQL and Path Tables</title>
		<field type="bibtex:topic">xmlsql[0.9] ssx[0.9]</field>
		<identifier type="sharef:uri">http://springerlink.metapress.com/link.asp?id=tl4kv8equ3hb8yl2</identifier>
	</reference>
	<reference name="olt02" src="bibtex:inproceedings" src-info="bibtex:line-9637" type="sharef:inproceedings" crossref="edbtw2002">
		<names type="sharef:author">
			<person>
				<givenname>Dan</givenname>
				<surname>Olteanu</surname>
			</person>
			<person>
				<givenname>Holger</givenname>
				<surname>Meuss</surname>
			</person>
			<person>
				<givenname>Tim</givenname>
				<surname>Furche</surname>
			</person>
			<person>
				<givenname>François</givenname>
				<surname>Bry</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>The location path language XPath is of particular importance for XML applications since it is a core component of many XML processing standards such as XSLT or XQuery. In this paper, based on axis symmetry of XPath, equivalences of XPath 1.0 location paths involving reverse axes, such as anc and prec, are established. These equivalences are used as rewriting rules in an algorithm for transforming location paths with reverse axes into equivalent reverse-axis-free ones. Location paths without reverse axes, as generated by the presented rewriting algorithm, enable efficient SAX-like streamed data processing of XPath.</p>
			</richtext>
		</abstract>
		<pages>109-127</pages>
		<title type="sharef:primaryTitle">XPath: Looking Forward</title>
		<field type="bibtex:topic">xpath1[0.8]</field>
		<identifier type="sharef:uri">http://www.springerlink.com/link.asp?id=wx54kfaved1u8gp5</identifier>
	</reference>
	<reference name="edbtw2002" src="bibtex:proceedings" src-info="bibtex:line-9647" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>Akmal B.</givenname>
				<surname>Chaudhri</surname>
			</person>
			<person>
				<givenname>Rainer</givenname>
				<surname>Unland</surname>
			</person>
			<person>
				<givenname>Chabane</givenname>
				<surname>Djeraba</surname>
			</person>
			<person>
				<givenname>Wolfgang</givenname>
				<surname>Lindner</surname>
			</person>
		</names>
		<date value="2002-03"/>
		<address type="sharef:placePublished">Prague, Czech Republic</address>
		<field type="bibtex:index">XMLDM 2002</field>
		<identifier type="sharef:isbn">3540001301</identifier>
		<publisher>Springer-Verlag</publisher>
		<title type="sharef:seriesTitle">Lecture Notes in Computer Science</title>
		<title type="sharef:primaryTitle">International Conference on Extending Database Technology — EDBT 2002 Workshop on XML-Based Data Management (XMLDM)</title>
		<identifier type="sharef:uri" resourceType="text/html">http://www.informatik.uni-trier.de/~ley/db/conf/edbtw/edbtw2002.html</identifier>
		<volume>2490</volume>
	</reference>
	<reference name="wil11a" src="bibtex:inproceedings" src-info="bibtex:line-9666" type="sharef:inproceedings" crossref="itng2011">
		<names type="sharef:author">
			<person>
				<givenname>Erik</givenname>
				<surname>Wilde</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>E-learning often is perceived as something that, on the technical level, can be addressed by designing an e-learning system, which often is equipped with a Web-based interface. We argue that this traditional approach of e-learning system design should be reversed in today's Web-oriented environment, in the sense that e-learning applications should be designed as well-behaving Web citizens and expose their services through nothing else but the Web's loose coupling principles. This article presents a system for Web-based presentations which follows this approach in publishing presentation material in a way that is as Web-friendly as possible. We show how such a system can be used as one building block in an e-learning infrastructure; replacing the traditional view of monolithic e-learning systems with an open and loosely coupled ecosystem of cooperating e-learning Web applications.</p>
			</richtext>
		</abstract>
		<title type="sharef:primaryTitle">Open and Accessible Presentations</title>
		<identifier type="sharef:uri">http://dret.net/netdret/publications#wil11a</identifier>
	</reference>
	<reference name="itng2011" src="bibtex:proceedings" src-info="bibtex:line-9674" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>Shahram</givenname>
				<surname>Latifi</surname>
			</person>
		</names>
		<date value="2011-04"/>
		<address type="sharef:placePublished">Las Vegas, Nevada</address>
		<publisher>IEEE Computer Society Press</publisher>
		<title type="sharef:primaryTitle">8th International Conference on Information Technology: New Generations (ITNG 2011)</title>
		<identifier type="sharef:uri" resourceType="text/html">http://www.informatik.uni-trier.de/~ley/db/conf/itng/itng2011.html</identifier>
	</reference>
	<reference name="kap01" src="bibtex:inproceedings" src-info="bibtex:line-9689" type="sharef:inproceedings" crossref="ic2001">
		<names type="sharef:author">
			<person>
				<givenname>Gerti</givenname>
				<surname>Kappel</surname>
			</person>
			<person>
				<givenname>Elisabeth</givenname>
				<surname>Kapsammer</surname>
			</person>
			<person>
				<givenname>Werner</givenname>
				<surname>Retschitzegger</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Database systems are well-known for consistent storage, retrieval, and manipulation of data. At the same time, the Extensible Markup Language (XML) is generally accepted as data description language for both web-based information systems and electronic data interchange between different organizations. Since database systems form the backbone of essentially any information system, the integration of XML and database systems is a must. Data model heterogeneity and schema heterogeneity, however, makes this a challenging task, for example when mapping XML documents to relational database systems (RDBS). This paper focuses on data model heterogeneity and provides an in-depth comparison of concepts available in RDBS and XML schema specification languages, comprising XML DTD and XML Schema. Such an analysis provides the basis for developing appropriate middleware bridging the gap between XML and RDBS.</p>
			</richtext>
		</abstract>
		<pages>199-205</pages>
		<title type="sharef:primaryTitle">XML and Relational Database Systems — A Comparison of Concepts</title>
		<field type="bibtex:topic">xml[0.8] rdbms[0.8]</field>
		<identifier type="sharef:uri" resourceType="application/pdf">ftp://ftp.ifs.uni-linz.ac.at/pub/publications/2001/0501.pdf</identifier>
	</reference>
	<reference name="psa01" src="bibtex:inproceedings" src-info="bibtex:line-9699" type="sharef:inproceedings" crossref="ic2001">
		<names type="sharef:author">
			<person>
				<givenname>Giuseppe</givenname>
				<surname>Psaila</surname>
			</person>
			<person>
				<givenname>Davide</givenname>
				<surname>Brugali</surname>
			</person>
		</names>
		<pages>157-163</pages>
		<title type="sharef:primaryTitle">The ERX Data Management System</title>
		<field type="bibtex:topic">erx[0.9]</field>
	</reference>
	<reference name="ic2001" src="bibtex:proceedings" src-info="bibtex:line-9707" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>Peter</givenname>
				<surname>Graham</surname>
			</person>
			<person>
				<givenname>Muthucumaru</givenname>
				<surname>Maheswaran</surname>
			</person>
			<person>
				<givenname>M. Rasit</givenname>
				<surname>Eskicioglu</surname>
			</person>
		</names>
		<date value="2001-06"/>
		<address type="sharef:placePublished">Las Vegas, Nevada</address>
		<field type="bibtex:index">IC 2001</field>
		<identifier type="sharef:isbn">18925128X</identifier>
		<publisher>CSREA Press</publisher>
		<title type="sharef:primaryTitle">2001 International Conference on Internet Computing</title>
		<identifier type="sharef:uri" resourceType="text/html">http://www.informatik.uni-trier.de/~ley/db/conf/ic/ic2001-1.html</identifier>
	</reference>
	<reference name="rou02" src="bibtex:inproceedings" src-info="bibtex:line-9724" type="sharef:inproceedings" crossref="adc2002">
		<names type="sharef:author">
			<person>
				<givenname>Nicholas</givenname>
				<surname>Routledge</surname>
			</person>
			<person>
				<givenname>Linda</givenname>
				<surname>Bird</surname>
			</person>
			<person>
				<givenname>Andrew</givenname>
				<surname>Goodchild</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>XML is rapidly becoming the standard method for sending information across the Internet. XML Schema, since its elevation to W3C Recommendation on the 2nd May 2001, is fast becoming the preferred means of describing structured XML data. However, until recently, there has been no effective means of graphically designing XML Schemas without exposing designers to low-level implementation issues. Bird, Goodchild and Halpin (2000) proposed a method to address this shortfall using the 'Object Role Modelling' conceptual language to generate XML Schemas. This paper seeks to build on this approach by defining a mapping between the Unified Modeling Language (UML) class diagrams and XML Schema using the traditional three level database design approach (ie. using conceptual, logical and physical design levels). In our approach, the conceptual level is represented using standard UML class notation, annotated with a few additional conceptual constraints, the logical level is represented in UML, using a set of UML stereotypes, and the XML Schema itself represents the physical level. The goal of this three level design methodology is to allow conceptual level UML class models to be automatically mapped into the logical level, while minimizing redundancy and maximizing connectivity.</p>
			</richtext>
		</abstract>
		<pages>157-166</pages>
		<title type="sharef:primaryTitle">UML and XML Schema</title>
		<field type="bibtex:topic">uml[0.7] xsd[0.7]</field>
		<identifier type="sharef:uri" resourceType="application/pdf">http://titanium.dstc.edu.au/papers/adc2002.pdf</identifier>
		<identifier type="sharef:uri" resourceType="application/pdf">http://crpit.com/confpapers/CRPITV5Routledge.pdf</identifier>
	</reference>
	<reference name="adc2002" src="bibtex:proceedings" src-info="bibtex:line-9735" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>Xiaofang</givenname>
				<surname>Zhou</surname>
			</person>
		</names>
		<date value="2002-01"/>
		<address type="sharef:placePublished">Melbourne, Australia</address>
		<field type="bibtex:index">ADC 2002</field>
		<identifier type="sharef:isbn">0-909-92583-6</identifier>
		<title type="sharef:seriesTitle">Conferences in Research and Practice in Information Technology</title>
		<title type="sharef:primaryTitle">Thirteenth Australasian Database Conference</title>
		<identifier type="sharef:uri">http://www.itee.uq.edu.au/~adc02/</identifier>
		<identifier type="sharef:uri" resourceType="text/html">http://crpit.com/Vol5.html</identifier>
		<volume>5</volume>
	</reference>
	<reference name="sch05" src="bibtex:inproceedings" src-info="bibtex:line-9754" type="sharef:inproceedings" crossref="adc2005">
		<names type="sharef:author">
			<person>
				<givenname>Klaus-Dieter</givenname>
				<surname>Schewe</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>With the advent of XML and its use as a database language, dependency and normal form theory has attracted novel research interest. Several approaches to build up a dependency and normal form theory for XML databases have been published, mainly concentrating on functional dependencies and keys. XML-like database structures can be modelled by rational trees using constructors for lists and disjoint unions. This involves restructuring rules on subattributes. The absence of redundancy can be characterised by the nested list normal form. If ordering is ignored, constructors for sets or multisets have to be employed. For these the theory can be extended using counter-free functional dependencies. Finally, for keys an important research question is which systems of subattributes permit Armstrong instances. While this gives just a glimpse of a starting promising theory, a research agenda for further research will be set up.</p>
			</richtext>
		</abstract>
		<pages>7-16</pages>
		<title type="sharef:primaryTitle">Redundancy, Dependencies and Normal Forms for XML Databases</title>
		<field type="bibtex:topic">xdbms[0.7]</field>
		<identifier type="sharef:uri" resourceType="application/pdf">http://crpit.com/confpapers/CRPITV39Schewe.pdf</identifier>
	</reference>
	<reference name="adc2005" src="bibtex:proceedings" src-info="bibtex:line-9764" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>Hugh E.</givenname>
				<surname>Williams</surname>
			</person>
			<person>
				<givenname>Gillian</givenname>
				<surname>Dobbie</surname>
			</person>
		</names>
		<date value="2005-01"/>
		<address type="sharef:placePublished">Newcastle, Australia</address>
		<field type="bibtex:index">ADC 2005</field>
		<identifier type="sharef:isbn">1-920682-21-X</identifier>
		<title type="sharef:seriesTitle">Conferences in Research and Practice in Information Technology</title>
		<title type="sharef:primaryTitle">Sixteenth Australasian Database Conference</title>
		<identifier type="sharef:uri" resourceType="text/html">http://www.informatik.uni-trier.de/~ley/db/conf/adc/adc2005.html</identifier>
		<volume>39</volume>
	</reference>
	<reference name="ber03c" src="bibtex:inproceedings" src-info="bibtex:line-9782" type="sharef:inproceedings" crossref="sci2003">
		<names type="sharef:author">
			<person>
				<givenname>Martin</givenname>
				<surname>Bernauer</surname>
			</person>
			<person>
				<givenname>Gerti</givenname>
				<surname>Kappel</surname>
			</person>
			<person>
				<givenname>Gerhard</givenname>
				<surname>Kramler</surname>
			</person>
			<person>
				<givenname>Werner</givenname>
				<surname>Retschitzegger</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>With the rise of the Web as the major platform for making data and services available for both, humans and applications, interorganizational workflows became a crucial issue. Several languages for the specification of interorganizational workflows have been already proposed, each of them having different origins and pursuing different goals for dealing with the unique characteristics of interorganizational workflows. This paper compares these proposals, trying to identify their strengths and shortcomings. As a pre-requisite, a framework of requirements is suggested which categorizes the major characteristics of specification languages for interorganizational workflows into different perspectives. For each of these perspectives, a set of functional requirements is proposed thereby emphasizing the difference to traditional intraorganizational workflows. On the basis of this framework, seven representative specification languages are surveyed and compared to each other.</p>
			</richtext>
		</abstract>
		<pages>30-36</pages>
		<title type="sharef:primaryTitle">Specification of Interorganizational Workflows — A Comparison of Approaches</title>
		<field type="bibtex:topic">wsdl[0.7] wsfl[0.7] ebxml[0.7] bpml[0.7] xlang[0.7] wscl[0.7] wpdl[0.7]</field>
		<identifier type="sharef:uri" resourceType="application/pdf">http://www.big.tuwien.ac.at/research/publications/2003/0603.pdf</identifier>
	</reference>
	<reference name="sci2003" src="bibtex:proceedings" src-info="bibtex:line-9792" type="sharef:proceedings">
		<date value="2003-07"/>
		<address type="sharef:placePublished">Orlando, Florida</address>
		<field type="bibtex:index">SCI 2003</field>
		<identifier type="sharef:isbn">9806560019</identifier>
		<title type="sharef:primaryTitle">7th World Multiconference on Systemics, Cybernetics, and Informatics</title>
		<identifier type="sharef:uri">http://www.iiisci.org/sci2003/</identifier>
	</reference>
	<reference name="liu11a" src="bibtex:inproceedings" src-info="bibtex:line-9807" type="sharef:inproceedings" crossref="iconf2011">
		<names type="sharef:author">
			<person>
				<givenname>Yiming</givenname>
				<surname>Liu</surname>
			</person>
			<person>
				<givenname>Erik</givenname>
				<surname>Wilde</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Location-Based Services (LBS) are based on a combination of the inherent location information about specific data, and/or the location information supplied by LBS clients, requesting location-specific and otherwise customized services. The integration of location-annotated data with existing personal and public information and services creates opportunities for insightful new views on the world, and allows rich, personalized, and contextualized user experiences. One of the biggest constraints of current LBS is that most of them are essentially vertical services. These current designs makes it hard for users to integrate LBS from a variety of service providers, either to create intermediate value-added services such as social information sharing facilities, or to facilitate client-side aggregations and mashups across specific LBS providers. Our approach, the Tiled Feeds architecture, applies the well-established, standard Web service pattern of feeds, and extends it with query and location-based features. Using this approach, LBS on the Web can be exposed in a generalized and aggregation-friendly way. We believe this approach can be used to facilitate the creation of standardized, Web-friendly, horizontally integrated location-based services.</p>
			</richtext>
		</abstract>
		<title type="sharef:primaryTitle">Personalized Location-Based Services</title>
		<identifier type="sharef:uri">http://dret.net/netdret/publications#liu11a</identifier>
	</reference>
	<reference name="iconf2011" src="bibtex:proceedings" src-info="bibtex:line-9815" type="sharef:proceedings">
		<date value="2011-02"/>
		<address type="sharef:placePublished">Seattle, Washington</address>
		<title type="sharef:primaryTitle">iConference 2011</title>
	</reference>
	<reference name="eng68" src="bibtex:inproceedings" src-info="bibtex:line-9827" type="sharef:inproceedings" crossref="afips1968">
		<names type="sharef:author">
			<person>
				<givenname>Douglas C.</givenname>
				<surname>Engelbart</surname>
			</person>
			<person>
				<givenname>William K.</givenname>
				<surname>English</surname>
			</person>
		</names>
		<pages>395-410</pages>
		<title type="sharef:primaryTitle">A Research Center for Augmenting Human Intellect</title>
		<field type="bibtex:topic">nls[0.9]</field>
		<identifier type="sharef:uri">http://portal.acm.org/citation.cfm?id=49508</identifier>
	</reference>
	<reference name="afips1968" src="bibtex:proceedings" src-info="bibtex:line-9836" type="sharef:proceedings">
		<date value="1968-12"/>
		<address type="sharef:placePublished">San Francisco, California</address>
		<title type="sharef:primaryTitle">AFIPS Fall Joint Computer Conference</title>
	</reference>
	<reference name="lee08" src="bibtex:inproceedings" src-info="bibtex:line-9848" type="sharef:inproceedings" crossref="seke2008">
		<names type="sharef:author">
			<person>
				<givenname>Bum-Suk</givenname>
				<surname>Lee</surname>
			</person>
			<person>
				<givenname>Jin Woo</givenname>
				<surname>Im</surname>
			</person>
			<person>
				<givenname>Byung-Yeon</givenname>
				<surname>Hwang</surname>
			</person>
			<person>
				<givenname>Du</givenname>
				<surname>Zhang</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>RSS (Rich Site Summary, or Really Simple Syndication) is widely used for notifying readers of updated information on blogs and feeding news to readers quickly. RSS is very simple, and so is mostly used as a web service. However there is no satisfactory search engine which works for RSS. The reason is that RSS is continuously modified, and the structure of general search engines is ineffective to collect information from RSS sources. In this paper, we discuss a web crawling algorithm, and propose a structure for an RSS crawler which is geared toward collecting and updating RSS in the Web 2.0 environment. The proposed method (1) uses visited domain name history to predict the location of the RSS of a new seed URL, and (2) updates RSS information adaptively, based on some update-checking heuristics. These approaches can serve as cornerstones for an efficient and effective RSS search engine.</p>
			</richtext>
		</abstract>
		<pages>219-222</pages>
		<title type="sharef:primaryTitle">Design of an RSS Crawler with Adaptive Revisit Manager</title>
		<identifier type="sharef:uri" resourceType="application/pdf">http://www.aquino.kr/papers/seke08.pdf</identifier>
	</reference>
	<reference name="seke2008" src="bibtex:proceedings" src-info="bibtex:line-9857" type="sharef:proceedings">
		<date value="2008-07"/>
		<address type="sharef:placePublished">San Francisco, California</address>
		<identifier type="sharef:isbn">1-891706-22-5</identifier>
		<title type="sharef:primaryTitle">Twentieth International Conference on Software Engineering &amp; Knowledge Engineering (SEKE 2008)</title>
		<identifier type="sharef:uri" resourceType="text/html">http://www.informatik.uni-trier.de/~ley/db/conf/seke/seke2008.html</identifier>
	</reference>
	<reference name="mcb01" src="bibtex:inproceedings" src-info="bibtex:line-9871" type="sharef:inproceedings" crossref="caise2001">
		<names type="sharef:author">
			<person>
				<givenname>Peter J.</givenname>
				<surname>McBrien</surname>
			</person>
			<person>
				<givenname>Alexandra</givenname>
				<surname>Poulovassilis</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>XML is fast becoming the standard for information exchange on the WWW. As such, information expressed in XML will need to be integrated with existing information systems, which are mostly based on structured data models such as relational, object-oriented or object/relational data models. This paper shows how our previous framework for integrating heterogeneous structured data sources can also be used for integrating XML data sources with each other and/or with other structured data sources. Our framework allows constructs from multiple modelling languages to co-exist within the same intermediate schema, and allows automatic translation of data, queries and updates between semantically equivalent or overlapping heterogenous schemas.</p>
			</richtext>
		</abstract>
		<pages>330-345</pages>
		<title type="sharef:primaryTitle">A Semantic Approach to Integrating XML and Structured Data Sources</title>
		<field type="bibtex:topic">xml[0.7]</field>
		<identifier type="sharef:uri">http://www.springerlink.com/openurl.asp?genre=article&amp;issn=0302-9743&amp;volume=2068&amp;spage=330</identifier>
	</reference>
	<reference name="caise2001" src="bibtex:proceedings" src-info="bibtex:line-9881" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>Klaus R.</givenname>
				<surname>Dittrich</surname>
			</person>
			<person>
				<givenname>Andreas</givenname>
				<surname>Geppert</surname>
			</person>
			<person>
				<givenname>Moira C.</givenname>
				<surname>Norrie</surname>
			</person>
		</names>
		<date value="2001-06"/>
		<address type="sharef:placePublished">Interlaken, Switzerland</address>
		<field type="bibtex:index">CAISE 2001</field>
		<identifier type="sharef:isbn">3540422153</identifier>
		<publisher>Springer-Verlag</publisher>
		<title type="sharef:seriesTitle">Lecture Notes in Computer Science</title>
		<title type="sharef:primaryTitle">13th Conference on Advanced Information Systems Engineering</title>
		<identifier type="sharef:uri">http://www.caise01.ch/</identifier>
		<identifier type="sharef:uri" resourceType="text/html">http://www.informatik.uni-trier.de/~ley/db/conf/caise/caise2001.html</identifier>
		<volume>2068</volume>
	</reference>
	<reference name="are02" src="bibtex:inproceedings" src-info="bibtex:line-9901" type="sharef:inproceedings" crossref="dexa2002">
		<names type="sharef:author">
			<person>
				<givenname>Marcelo</givenname>
				<surname>Arenas</surname>
			</person>
			<person>
				<givenname>Wenfei</givenname>
				<surname>Fan</surname>
			</person>
			<person>
				<givenname>Leonid</givenname>
				<surname>Libkin</surname>
			</person>
		</names>
		<pages>269-278</pages>
		<title type="sharef:primaryTitle">What's Hard about XML Schema Constraints?</title>
		<field type="bibtex:topic">xsd[0.8]</field>
		<identifier type="sharef:uri">http://springerlink.metapress.com/openurl.asp?genre=article&amp;issn=0302-9743&amp;volume=2453&amp;spage=269</identifier>
	</reference>
	<reference name="dexa2002" src="bibtex:proceedings" src-info="bibtex:line-9910" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>Abdelkader</givenname>
				<surname>Hameurlain</surname>
			</person>
			<person>
				<givenname>Rosine</givenname>
				<surname>Cicchetti</surname>
			</person>
			<person>
				<givenname>Roland</givenname>
				<surname>Traunmüller</surname>
			</person>
		</names>
		<date value="2002-09"/>
		<address type="sharef:placePublished">Aix-en-Provence, France</address>
		<field type="bibtex:index">DEXA 2002</field>
		<identifier type="sharef:isbn">3540441263</identifier>
		<publisher>Springer-Verlag</publisher>
		<title type="sharef:seriesTitle">Lecture Notes in Computer Science</title>
		<title type="sharef:primaryTitle">13th International Conference on Database and Expert Systems Applications (DEXA 2002)</title>
		<identifier type="sharef:uri" resourceType="text/html">http://www.informatik.uni-trier.de/~ley/db/conf/dexa/dexa2002.html</identifier>
		<volume>2453</volume>
	</reference>
	<reference name="lee01" src="bibtex:inproceedings" src-info="bibtex:line-9929" type="sharef:inproceedings" crossref="dexa2001">
		<names type="sharef:author">
			<person>
				<givenname>Mong-Li</givenname>
				<surname>Lee</surname>
			</person>
			<person>
				<givenname>Sin Yeung</givenname>
				<surname>Lee</surname>
			</person>
			<person>
				<givenname>Tok Wang</givenname>
				<surname>Ling</surname>
			</person>
			<person>
				<givenname>Gillian</givenname>
				<surname>Dobbie</surname>
			</person>
			<person>
				<givenname>Leonid A.</givenname>
				<surname>Kalinichenko</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Semistructured data has become prevalent with the growth of the Internet. The data is usually stored in a database system or in a specialized repository. Many information providers have presented their databases on the web as semistructured data, while others are developing repositories for new applications. Designing a "good" semistructured database is important to prevent data redundancy and updating anomalies. In this paper, we propose a conceptual approach to design semistructured databases. A conceptual layer based on the Entity-Relationship model is used to remove redundancies at the semantic level. An algorithm to map an ER diagram involving composite attributes weak entity types, recursive, n-ary and ISA relationship sets, and aggregations to a semistructured schema graph (S3-Graph) is also given.</p>
			</richtext>
		</abstract>
		<pages>12-21</pages>
		<title type="sharef:primaryTitle">Designing Semistructured Databases: A Conceptual Approach</title>
		<identifier type="sharef:uri">http://www.springerlink.com/link.asp?id=wffxga8fykahxbxq</identifier>
	</reference>
	<reference name="dexa2001" src="bibtex:proceedings" src-info="bibtex:line-9938" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>Heinrich C.</givenname>
				<surname>Mayr</surname>
			</person>
			<person>
				<givenname>Jirí</givenname>
				<surname>Lazanský</surname>
			</person>
			<person>
				<givenname>Gerald</givenname>
				<surname>Quirchmayr</surname>
			</person>
			<person>
				<givenname>Pavel</givenname>
				<surname>Vogel</surname>
			</person>
		</names>
		<date value="2001-09"/>
		<address type="sharef:placePublished">Munich, Germany</address>
		<field type="bibtex:index">DEXA 2001</field>
		<identifier type="sharef:isbn">3-540-42527-6</identifier>
		<publisher>Springer-Verlag</publisher>
		<title type="sharef:seriesTitle">Lecture Notes in Computer Science</title>
		<title type="sharef:primaryTitle">12th International Conference on Database and Expert Systems Applications (DEXA 2001)</title>
		<identifier type="sharef:uri" resourceType="text/html">http://www.informatik.uni-trier.de/~ley/db/conf/dexa/dexa2001.html</identifier>
		<volume>2113</volume>
	</reference>
	<reference name="cas02" src="bibtex:inproceedings" src-info="bibtex:line-9957" type="sharef:inproceedings" crossref="dexaws2002">
		<names type="sharef:author">
			<person>
				<givenname>Silvana</givenname>
				<surname>Castano</surname>
			</person>
			<person>
				<givenname>Alfio</givenname>
				<surname>Ferrara</surname>
			</person>
			<person>
				<givenname>G. S.</givenname>
				<surname>Kuruvilla Ottathycal</surname>
			</person>
			<person>
				<givenname>Valeria</givenname>
				<surname>De Antonellis</surname>
			</person>
		</names>
		<pages>103-110</pages>
		<title type="sharef:primaryTitle">A Disciplined Approach for the Integration of Heterogeneous XML Datasources</title>
		<identifier type="sharef:uri" resourceType="text/html">http://csdl.computer.org/comp/proceedings/dexa/2002/1668/00/16680103abs.htm</identifier>
	</reference>
	<reference name="dexaws2002" src="bibtex:proceedings" src-info="bibtex:line-9965" type="sharef:proceedings">
		<date value="2002-09"/>
		<address type="sharef:placePublished">Aix-en-Provence, France</address>
		<field type="bibtex:index">DEXA 2002</field>
		<identifier type="sharef:isbn">0769516688</identifier>
		<publisher>IEEE Computer Society Press</publisher>
		<title type="sharef:primaryTitle">13th International Workhop on Database and Expert Systems Applications (DEXA 2002)</title>
		<identifier type="sharef:uri" resourceType="text/html">http://csdl.computer.org/comp/proceedings/dexa/2002/1668/00/1668toc.htm</identifier>
		<identifier type="sharef:uri" resourceType="text/html">http://www.informatik.uni-trier.de/~ley/db/conf/dexaw/dexaw2002.html</identifier>
	</reference>
	<reference name="mcb02" src="bibtex:inproceedings" src-info="bibtex:line-9982" type="sharef:inproceedings" crossref="caise2002">
		<names type="sharef:author">
			<person>
				<givenname>Peter J.</givenname>
				<surname>McBrien</surname>
			</person>
			<person>
				<givenname>Alexandra</givenname>
				<surname>Poulovassilis</surname>
			</person>
		</names>
		<pages>484-499</pages>
		<title type="sharef:primaryTitle">Schema Evolution in Heterogeneous Database Architectures, A Schema Transformation Approach</title>
	</reference>
	<reference name="caise2002" src="bibtex:proceedings" src-info="bibtex:line-9989" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>Anne Banks</givenname>
				<surname>Pidduck</surname>
			</person>
			<person>
				<givenname>John</givenname>
				<surname>Mylopoulos</surname>
			</person>
			<person>
				<givenname>Carson C.</givenname>
				<surname>Woo</surname>
			</person>
			<person>
				<givenname>M. Tamer</givenname>
				<surname>Özsu</surname>
			</person>
		</names>
		<date value="2002-05"/>
		<address type="sharef:placePublished">Toronto, Canada</address>
		<field type="bibtex:index">CAISE 2002</field>
		<identifier type="sharef:isbn">354043738X</identifier>
		<publisher>Springer-Verlag</publisher>
		<title type="sharef:seriesTitle">Lecture Notes in Computer Science</title>
		<title type="sharef:primaryTitle">14th Conference on Advanced Information Systems Engineering</title>
		<identifier type="sharef:uri">http://www.cs.toronto.edu/caise02/</identifier>
		<identifier type="sharef:uri" resourceType="text/html">http://www.informatik.uni-trier.de/~ley/db/conf/caise/caise2002.html</identifier>
		<volume>2348</volume>
	</reference>
	<reference name="ben03b" src="bibtex:inproceedings" src-info="bibtex:line-10010" type="sharef:inproceedings" crossref="caise2003">
		<names type="sharef:author">
			<person>
				<givenname>Boualem</givenname>
				<surname>Benatallah</surname>
			</person>
			<person>
				<givenname>Fabio</givenname>
				<surname>Casati</surname>
			</person>
			<person>
				<givenname>Farouk</givenname>
				<surname>Toumani</surname>
			</person>
			<person>
				<givenname>Rachid</givenname>
				<surname>Hamadi</surname>
			</person>
		</names>
		<pages>449-467</pages>
		<title type="sharef:primaryTitle">Conceptual Modeling of Web Service Conversations</title>
		<field type="bibtex:topic">selfserv[0.9]</field>
		<identifier type="sharef:uri" resourceType="text/html">http://link.springer.de/link/service/series/0558/bibs/2681/26810449.htm</identifier>
	</reference>
	<reference name="ber03b" src="bibtex:inproceedings" src-info="bibtex:line-10019" type="sharef:inproceedings" crossref="caise2003short">
		<names type="sharef:author">
			<person>
				<givenname>Martin</givenname>
				<surname>Bernauer</surname>
			</person>
			<person>
				<givenname>Gerti</givenname>
				<surname>Kappel</surname>
			</person>
			<person>
				<givenname>Gerhard</givenname>
				<surname>Kramler</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>The unique selling point of XML as standard representation of content is its ease of use thus facilitating interoperability between various partners and platforms. To overcome XML Schema's weakness concerning semantic expressiveness, tailored XML schema languages would be favorable to represent domain specific knowledge. The contribution of this paper is to identify various approaches to implementing tailored XML schema languages with XML Schema.</p>
			</richtext>
		</abstract>
		<pages>133-140</pages>
		<title type="sharef:primaryTitle">Approaches to Implementing a Tailored Metaschema in XML</title>
		<field type="bibtex:topic">xmlschemalanguage[0.8]</field>
		<identifier type="sharef:uri" resourceType="application/pdf">http://www.big.tuwien.ac.at/research/publications/2003/0203.pdf</identifier>
	</reference>
	<reference name="su03" src="bibtex:inproceedings" src-info="bibtex:line-10029" type="sharef:inproceedings" crossref="caise2003short">
		<names type="sharef:author">
			<person>
				<givenname>Xiaomeng</givenname>
				<surname>Su</surname>
			</person>
			<person>
				<givenname>Terje</givenname>
				<surname>Brasethvik</surname>
			</person>
			<person>
				<givenname>Sari</givenname>
				<surname>Hakkarainen</surname>
			</person>
		</names>
		<pages>101-104</pages>
		<title type="sharef:primaryTitle">Ontology Mapping through Analysis of Model Extension</title>
		<identifier type="sharef:uri" resourceType="application/pdf">http://www.idi.ntnu.no/~xiaomeng/paper/CaiseForum.pdf</identifier>
		<identifier type="sharef:uri" resourceType="application/pdf">http://sunsite.informatik.rwth-aachen.de/Publications/CEUR-WS/Vol-74/files/FORUM_26.pdf</identifier>
	</reference>
	<reference name="lux03" src="bibtex:inproceedings" src-info="bibtex:line-10038" type="sharef:inproceedings" crossref="caise2003short">
		<names type="sharef:author">
			<person>
				<givenname>Mathias</givenname>
				<surname>Lux</surname>
			</person>
			<person>
				<givenname>Jutta</givenname>
				<surname>Becker</surname>
			</person>
			<person>
				<givenname>Harald</givenname>
				<surname>Krottmaier</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Nowadays research and development activities are accompanied by an increasing focus on future user needs in the field of multimedia retrieval. The fast growing of multimedia data repositories is an undeniable fact, so specialized tools allowing storage, indexing and retrieval of multimedia content have to be developed, and in addition easy-to-use content exchange is needed. The transition from text to photo retrieval raises the necessity of generating, storing and visualizing additional meta-information about the content to allow semantic retrieval. "Caliph &amp; Emir", a pair of prototypes allowing semantic annotation and retrieval of digital photos , are presented as a possible new way of handling semantics in descriptions of multimedia data.</p>
			</richtext>
		</abstract>
		<pages>85-88</pages>
		<title type="sharef:primaryTitle">Semantic Annotation and Retrieval of Digital Photos</title>
		<identifier type="sharef:uri" resourceType="application/pdf">http://sunsite.informatik.rwth-aachen.de/Publications/CEUR-WS/Vol-74/files/FORUM_22.pdf</identifier>
	</reference>
	<reference name="caise2003" src="bibtex:proceedings" src-info="bibtex:line-10047" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>Johann</givenname>
				<surname>Eder</surname>
			</person>
			<person>
				<givenname>Michele</givenname>
				<surname>Missikoff</surname>
			</person>
		</names>
		<date value="2003-06"/>
		<address type="sharef:placePublished">Klagenfurt, Austria</address>
		<field type="bibtex:index">CAISE 2003</field>
		<identifier type="sharef:isbn">3540404422</identifier>
		<publisher>Springer-Verlag</publisher>
		<title type="sharef:seriesTitle">Lecture Notes in Computer Science</title>
		<title type="sharef:primaryTitle">15th Conference on Advanced Information Systems Engineering</title>
		<identifier type="sharef:uri">http://www.isys.uni-klu.ac.at/caise03/01_home/</identifier>
		<identifier type="sharef:uri" resourceType="text/html">http://www.informatik.uni-trier.de/~ley/db/conf/caise/caise2003.html</identifier>
		<volume>2681</volume>
	</reference>
	<reference name="caise2003short" src="bibtex:proceedings" src-info="bibtex:line-10063" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>Johann</givenname>
				<surname>Eder</surname>
			</person>
			<person>
				<givenname>Tatjana</givenname>
				<surname>Welzer</surname>
			</person>
		</names>
		<date value="2003-06"/>
		<address type="sharef:placePublished">Klagenfurt, Austria</address>
		<field type="bibtex:index">CAISE 2003</field>
		<identifier type="sharef:isbn">8643505498</identifier>
		<publisher>Technical University of Aachen (RWTH)</publisher>
		<title type="sharef:seriesTitle">CEUR Workshop Proceedings</title>
		<title type="sharef:primaryTitle">Short Paper 15th Conference on Advanced Information Systems Engineering</title>
		<identifier type="sharef:uri" resourceType="text/html">http://www.informatik.uni-trier.de/~ley/db/conf/caise/caisefo2003.html</identifier>
		<volume>74</volume>
	</reference>
	<reference name="bai04" src="bibtex:inproceedings" src-info="bibtex:line-10084" type="sharef:inproceedings" crossref="caise2004">
		<names type="sharef:author">
			<person>
				<givenname>Karim</givenname>
				<surname>Baïna</surname>
			</person>
			<person>
				<givenname>Boualem</givenname>
				<surname>Benatallah</surname>
			</person>
			<person>
				<givenname>Fabio</givenname>
				<surname>Casati</surname>
			</person>
			<person>
				<givenname>Farouk</givenname>
				<surname>Toumani</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Web services are emerging as a promising technology for the effective automation of inter-organizational interactions. However, despite the growing interest, several issues still need to be addressed to provide Web services with benefits similar to what traditional middleware brings to intra-organizational application integration. In this paper, we present a framework that supports the model-driven development of Web services. Specifically, we show how, starting from the external specifications of a Web service (e.g., interface and protocol specifications), we can support the generation of extensible service implementation templates as well as of complete (executable) service specifications, thereby considerably simplifying the service development work.</p>
			</richtext>
		</abstract>
		<pages>290-306</pages>
		<title type="sharef:primaryTitle">Model-Driven Web Service Development</title>
		<field type="bibtex:topic">soa[0.7]</field>
		<identifier type="sharef:uri">http://springerlink.metapress.com/openurl.asp?genre=article&amp;issn=0302-9743&amp;volume=3084&amp;spage=22</identifier>
	</reference>
	<reference name="ign04" src="bibtex:inproceedings" src-info="bibtex:line-10094" type="sharef:inproceedings" crossref="caise2004">
		<names type="sharef:author">
			<person>
				<givenname>Claudia-Lavinia</givenname>
				<surname>Ignat</surname>
			</person>
			<person>
				<givenname>Moira C.</givenname>
				<surname>Norrie</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>In software engineering as well as in any engineering domain, a way of customizing the collaborative work to various modes of collaboration, i.e. synchronous and asynchronous, and the possibility of alternating these modes along the phases of a project is required. Our goal is to develop a universal information platform that can support collaboration in a range of application domains, the basic sharing unit being the document. Since not all user groups have the same conventions and not all tasks have the same requirements, this implies that it should be possible to customize the collaborative environment at the level of both communities and individual tasks. In this paper we present the consistency maintenance models underlying the synchronous and asynchronous modes of collaboration. We highlight the importance of choosing a general structured model of the document and particularly analyze the multi-mode collaboration for two main representative types of documents: textual and graphical.</p>
			</richtext>
		</abstract>
		<pages>580-594</pages>
		<title type="sharef:primaryTitle">CoDoc: Multi-mode Collaboration over Documents</title>
		<identifier type="sharef:uri">http://www.springerlink.com/link.asp?id=mffh585tc0ntcype</identifier>
		<identifier type="sharef:uri">http://www.springerlink.com/openurl.asp?genre=article&amp;issn=0302-9743&amp;volume=3084&amp;spage=580</identifier>
	</reference>
	<reference name="eck04" src="bibtex:inproceedings" src-info="bibtex:line-10104" type="sharef:inproceedings" crossref="caise2004forum">
		<names type="sharef:author">
			<person>
				<givenname>Rainer</givenname>
				<surname>Eckstein</surname>
			</person>
			<person>
				<givenname>Silke</givenname>
				<surname>Eckstein</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>The Extensible Markup Language (XML) has found acceptance as a standard for storing and exchanging structured and semi-structured data. With its expressive power, XML enables a great variety of applications relying on such structures. As the data schema, an XML schema is a means by which documents and objects can be structured. Our approach is to model XML schemata and thus classes of documents on the basis of UML (Unified Modeling Language). We consider UML to be the connecting link between software engineering and document design, i.e., it is possible to design object-oriented software together with the necessary XML structures. For this reason, we describe how to transform the static part of UML, i.e. class diagrams, into XML schemata. The major challenge for the transformation is to define a suitable mapping reflecting the semantics of a UML specification in an XML schema correctly. Because of XML's specific properties, we slightly extend UML in a UML compliant way. Additionally, the resulting XML schema profile supports the tuning of the transformation to XML schema. Our approach provides the stepping stone to bridge the gap between object-oriented software design and the development of XML data schemata.</p>
			</richtext>
		</abstract>
		<pages>122-131</pages>
		<title type="sharef:primaryTitle">Conceptual Modeling XML Schemata Using UML</title>
	</reference>
	<reference name="boe04" src="bibtex:inproceedings" src-info="bibtex:line-10112" type="sharef:inproceedings" crossref="caise2004diweb2004">
		<names type="sharef:author">
			<person>
				<givenname>Timo</givenname>
				<surname>Böhme</surname>
			</person>
			<person>
				<givenname>Erhard</givenname>
				<surname>Rahm</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Relational database systems are increasingly used to manage XML documents, especially for data-centric XML. In this paper we present a new approach to efficiently manage document-centric XML data based on a generic relational mapping. Such a generic XML storage is especially useful in data integration systems to manage highly diverse XML documents. We focus on efficient insert operations, support of streamed data and fast retrieval of document fragments. Therefore we introduce a new numbering scheme called DLN (Dynamic Level Numbering) and several variants of it. A performance evaluation based on a prototypical implementation demonstrates the high efficiency of DLN.</p>
			</richtext>
		</abstract>
		<title type="sharef:primaryTitle">Supporting Efficient Streaming and Insertion of XML Data in RDBMS</title>
		<field type="bibtex:topic">dln[1]</field>
		<identifier type="sharef:uri" resourceType="application/pdf">http://www.doc.ic.ac.uk/~pjm/diweb2004/DIWeb2004_Part7.pdf</identifier>
		<identifier type="sharef:uri" resourceType="application/pdf">http://dbs.uni-leipzig.de/files/projekte/XML/Boehme_DLN_DIWeb_CR.pdf</identifier>
	</reference>
	<reference name="caise2004" src="bibtex:proceedings" src-info="bibtex:line-10122" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>Anne</givenname>
				<surname>Persson</surname>
			</person>
			<person>
				<givenname>Janis</givenname>
				<surname>Stirna</surname>
			</person>
		</names>
		<date value="2004-06"/>
		<address type="sharef:placePublished">Riga, Latvia</address>
		<identifier type="sharef:doi">10.1007/b98058</identifier>
		<field type="bibtex:index">CAISE 2004</field>
		<identifier type="sharef:isbn">3-540-22151-4</identifier>
		<publisher>Springer-Verlag</publisher>
		<title type="sharef:seriesTitle">Lecture Notes in Computer Science</title>
		<title type="sharef:primaryTitle">16th Conference on Advanced Information Systems Engineering</title>
		<identifier type="sharef:uri">http://www.cs.rtu.lv/caise2004/</identifier>
		<identifier type="sharef:uri">http://www.springerlink.com/openurl.asp?genre=issue&amp;issn=0302-9743&amp;volume=3084&amp;issue=preprint</identifier>
		<identifier type="sharef:uri" resourceType="text/html">http://www.informatik.uni-trier.de/~ley/db/conf/caise/caise2004.html</identifier>
		<volume>3048</volume>
	</reference>
	<reference name="caise2004forum" src="bibtex:proceedings" src-info="bibtex:line-10140" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>Janis</givenname>
				<surname>Grabis</surname>
			</person>
			<person>
				<givenname>Anne</givenname>
				<surname>Persson</surname>
			</person>
			<person>
				<givenname>Janis</givenname>
				<surname>Stirna</surname>
			</person>
		</names>
		<date value="2004-06"/>
		<address type="sharef:placePublished">Riga, Latvia</address>
		<field type="bibtex:index">CAISE 2004</field>
		<identifier type="sharef:isbn">9984-9767-0-X</identifier>
		<title type="sharef:primaryTitle">Forum 16th Conference on Advanced Information Systems Engineering</title>
	</reference>
	<reference name="caise2004diweb2004" src="bibtex:proceedings" src-info="bibtex:line-10151" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>Zohra</givenname>
				<surname>Bellehsène</surname>
			</person>
			<person>
				<givenname>Peter J.</givenname>
				<surname>McBrien</surname>
			</person>
		</names>
		<date value="2004-06"/>
		<address type="sharef:placePublished">Riga, Latvia</address>
		<field type="bibtex:index">DIWeb 2004</field>
		<title type="sharef:primaryTitle">Third International Workshop on Data Integration over the Web</title>
		<identifier type="sharef:uri">http://www.doc.ic.ac.uk/~pjm/diweb2004/</identifier>
	</reference>
	<reference name="oli05" src="bibtex:inproceedings" src-info="bibtex:line-10166" type="sharef:inproceedings" crossref="caise2005">
		<names type="sharef:author">
			<person>
				<givenname>Antoni</givenname>
				<surname>Olivé</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>The goal of automating information systems building was stated in the sixties. Forty years later it is clear that the goal has not been achieved in a satisfactory degree. One of the problems has been the lack of standards in languages and platforms. In this respect, the recent efforts on standardization provide an opportunity to revive the automation goal. This is the main purpose of this paper. We have named the goal "conceptual schema-centric development" (CSCD) in order to emphasize that the conceptual schema should be the center of the development of information systems. We show that to develop an information system it is necessary to define its conceptual schema and that, therefore, the CSCD approach does not place an extra burden on developers. In CSCD, conceptual schemas would be explicit, executable in the production environment and the basis for the system evolution. To achieve the CSCD goal it is necessary to solve many research problems. We identify and comment on a few problems that should be included in a research agenda for CSCD. Finally, we show that the CSCD goal can be qualified as a grand challenge for the information systems research community.</p>
			</richtext>
		</abstract>
		<pages>1-15</pages>
		<title type="sharef:primaryTitle">Conceptual Schema-Centric Development: A Grand Challenge for Information Systems Research</title>
		<identifier type="sharef:uri">http://www.springerlink.com/link.asp?id=wgjgj3d7k4mqtenu</identifier>
	</reference>
	<reference name="van05" src="bibtex:inproceedings" src-info="bibtex:line-10175" type="sharef:inproceedings" crossref="caise2005">
		<names type="sharef:author">
			<person>
				<givenname>Jean</givenname>
				<surname>Vanderdonckt</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>To cope with the ever increasing diversity of markup languages, programming languages, tool kits and interface development environments, conceptual modeling of user interfaces could bring a framework for specifying, designing, and developing user interfaces at a level of abstraction that is higher than the level where code is merely manipulated. For this purpose, a complete environment is presented based on conceptual modeling of user interfaces of information systems structured around three axes: the models that characterize a user interface from the end user's viewpoint and the specification language that allows designers to specify such interfaces, the method for developing interfaces in forward, reverse, and lateral engineering based on these models, and a suite of tools that support designers in applying the method based on the models. This environment is compatible with the Model-Driven Architecture recommendations in the sense that all models adhere to the principle of separation of concerns and are based on model transformation between the MDA levels. The models and the transformations of these models are all expressed in UsiXML (User Interface Extensible Markup Language) and maintained in a model repository that can be accessed by the suite of tools. Thanks to this environment, it is possible to quickly develop and deploy a wide array of user interfaces for different computing platforms, for different interaction modalities, for different markup and programming languages, and for various contexts of use.</p>
			</richtext>
		</abstract>
		<pages>16-31</pages>
		<title type="sharef:primaryTitle">A MDA-Compliant Environment for Developing User Interfaces of Information Systems</title>
		<field type="bibtex:topic">usixml[0.9]</field>
		<identifier type="sharef:uri">http://www.springerlink.com/link.asp?id=xf005tul3xyqhab3</identifier>
	</reference>
	<reference name="caise2005" src="bibtex:proceedings" src-info="bibtex:line-10185" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>Oscar</givenname>
				<surname>Pastor</surname>
			</person>
			<person>
				<givenname>João</givenname>
				<surname>Falcão e Cunha</surname>
			</person>
		</names>
		<date value="2005-06"/>
		<address type="sharef:placePublished">Porto, Portugal</address>
		<field type="bibtex:index">CAISE 2005</field>
		<identifier type="sharef:isbn">3-540-26095-1</identifier>
		<publisher>Springer-Verlag</publisher>
		<title type="sharef:seriesTitle">Lecture Notes in Computer Science</title>
		<title type="sharef:primaryTitle">16th Conference on Advanced Information Systems Engineering</title>
		<identifier type="sharef:uri" resourceType="text/html">http://www.informatik.uni-trier.de/~ley/db/conf/caise/caise2005.html</identifier>
		<volume>3520</volume>
	</reference>
	<reference name="con00" src="bibtex:inproceedings" src-info="bibtex:line-10204" type="sharef:inproceedings" crossref="er2000">
		<names type="sharef:author">
			<person>
				<givenname>Rainer</givenname>
				<surname>Conrad</surname>
			</person>
			<person>
				<givenname>Dieter</givenname>
				<surname>Scheffner</surname>
			</person>
			<person>
				<givenname>Johann Christoph</givenname>
				<surname>Freytag</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>The Extensible Markup Language (XML) is increasingly finding acceptance as a standard for storing and exchanging structured and semi-structured information. With its expressive power, XML enables a great variety of applications relying on such structures — notably product catalogs, digital libraries, and electronic data interchange (EDI). As the data schema, an XML Document Type Definition (DTD) is a means by which documents and objects can be structured. Currently, there is no suitable way to model DTDs conceptually. Our approach is to model DTDs and thus classes of documents on the basis of UML (Unified Modeling Language). We consider UML to be the connecting link between software engineering and document design, i.e., it is possible to design object-oriented software together with the necessary XML structures. For this reason, we describe how to transform the static part of UML, i.e. class diagrams, into XML DTDs. The major challenge for the transformation is to define a suitable mapping reflecting the semantics of a UML specification in a DTD correctly. Because of XML's specific properties, we slightly extend the UML language in a UML-compliant way. Our approach provides the stepping stone to bridge the gap between object-oriented software design and the development of XML data schemata.</p>
			</richtext>
		</abstract>
		<pages>558-571</pages>
		<title type="sharef:primaryTitle">XML Conceptual Modeling Using UML</title>
		<field type="bibtex:topic">uml[0.7] xsd[0.7]</field>
		<identifier type="sharef:uri" resourceType="application/pdf">ftp://ftp.dbis.informatik.hu-berlin.de/pub/papers/conferences/ER2000-CSF.pdf</identifier>
		<identifier type="sharef:uri" resourceType="text/html">http://link.springer.de/link/service/series/0558/bibs/1920/19200558.htm</identifier>
	</reference>
	<reference name="bir00" src="bibtex:inproceedings" src-info="bibtex:line-10215" type="sharef:inproceedings" crossref="er2000">
		<names type="sharef:author">
			<person>
				<givenname>Linda</givenname>
				<surname>Bird</surname>
			</person>
			<person>
				<givenname>Andrew</givenname>
				<surname>Goodchild</surname>
			</person>
			<person>
				<givenname>Terry A.</givenname>
				<surname>Halpin</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>XML is increasingly becoming the preferred method of encoding structured data for exchange over the Internet. XML-Schema, which is an emerging text-based schema definition language, promises to become the most popular method for describing these XML-documents. While text-based languages, such as XML-Schema, offer great advantages for data interchange on the Internet, graphical modelling languages are widely accepted as a more visually effective means of specifying and communicating data requirements for a human audience. With this in mind, this paper investigates the use of Object Role Modelling (ORM), a graphical, conceptual modelling technique, as a means for designing XML-Schemas. The primary benefit of using ORM is that it is much easier to get the model 'correct' by designing it in ORM first, rather than in XML. To facilitate this process we describe an algorithm that enables an XML-Schema file to be automatically generated from an ORM conceptual data model. Our approach aims to reduce data redundancy and increase the connectivity of the resulting XML instances.</p>
			</richtext>
		</abstract>
		<pages>309-322</pages>
		<title type="sharef:primaryTitle">Object Role Modelling and XML-Schema</title>
		<field type="bibtex:topic">orm[0.7] xsd[0.7]</field>
		<identifier type="sharef:uri">http://www.springerlink.com/link.asp?id=ulp47aqbr7y3rx5h</identifier>
	</reference>
	<reference name="er2000" src="bibtex:proceedings" src-info="bibtex:line-10225" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>Alberto H. F.</givenname>
				<surname>Laender</surname>
			</person>
			<person>
				<givenname>Stephen W.</givenname>
				<surname>Liddle</surname>
			</person>
			<person>
				<givenname>Veda C.</givenname>
				<surname>Storey</surname>
			</person>
		</names>
		<date value="2000-10"/>
		<address type="sharef:placePublished">Salt Lake City, Utah</address>
		<field type="bibtex:index">ER 2000</field>
		<identifier type="sharef:isbn">3-540-41072-4</identifier>
		<publisher>Springer-Verlag</publisher>
		<title type="sharef:seriesTitle">Lecture Notes in Computer Science</title>
		<title type="sharef:primaryTitle">19th International Conference on Conceptual Modeling</title>
		<identifier type="sharef:uri" resourceType="text/html">http://www.informatik.uni-trier.de/%7Eley/db/conf/er/er2000.html</identifier>
		<volume>1920</volume>
	</reference>
	<reference name="man01" src="bibtex:inproceedings" src-info="bibtex:line-10244" type="sharef:inproceedings" crossref="er2001">
		<names type="sharef:author">
			<person>
				<givenname>Murali</givenname>
				<surname>Mani</surname>
			</person>
			<person>
				<givenname>Dongwon</givenname>
				<surname>Lee</surname>
			</person>
			<person>
				<givenname>Richard R.</givenname>
				<surname>Muntz</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Most research on XML has so far largely neglected the data modeling aspects of XML schemas. In this paper, we attempt to make a systematic approach to data modeling capabilities of XML schemas. We first formalize a core set of features among a dozen competing XML schema language proposals and introduce a new notion of XGrammar. The benefits of such formal description is that it is both concise and precise. We then compare the features of XGrammar with those of the Entity-Relationship (ER) model. We especially focus on three data modeling capabilities of XGrammar: (a) the ability to represent  ordered binary relationships, (b) the ability to represent a set of semantically equivalent but structurally different types as "one" type using the closure properties, and (c) the ability to represent  recursive relationships.</p>
			</richtext>
		</abstract>
		<pages>149-163</pages>
		<title type="sharef:primaryTitle">Semantic Data Modeling Using XML Schemas</title>
		<field type="bibtex:topic">xsd[0.7] xgrammar[0.9]</field>
		<identifier type="sharef:uri" resourceType="text/html">http://link.springer.de/link/service/series/0558/bibs/2224/22240149.htm</identifier>
	</reference>
	<reference name="mel01" src="bibtex:inproceedings" src-info="bibtex:line-10254" type="sharef:inproceedings" crossref="er2001">
		<names type="sharef:author">
			<person>
				<givenname>Ronaldo</givenname>
				<surname link="dos">Santos Mello</surname>
			</person>
			<person>
				<givenname>Carlos A.</givenname>
				<surname>Heuser</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>XML is a common standard for semi-structured and structured data representation and exchange over the Web. This paper describes a  semi-automatic process for converting an XML DTD to a schema in a canonical conceptual model based on ORM/NIAM and extended ER models. This process is part of a bottom-up approach for integration of XML sources that takes a set of DTDs and generates an ontology for query purposes. A conceptual schema for a DTD simplifies the integration activity because provides a semantically rich representation of an XML source. The core of the process is a set of  conversion rules that consider the DTD structure and heuristics related to default semantic interpretations on such structure in order to generate the corresponding concepts in the canonical conceptual schema.</p>
			</richtext>
		</abstract>
		<pages>133-148</pages>
		<title type="sharef:primaryTitle">A Rule-Based Conversion of a DTD to a Conceptual Schema</title>
		<field type="bibtex:topic">dtd[0.7]</field>
		<identifier type="sharef:uri" resourceType="text/html">http://link.springer.de/link/service/series/0558/bibs/2224/22240133.htm</identifier>
	</reference>
	<reference name="emb01" src="bibtex:inproceedings" src-info="bibtex:line-10264" type="sharef:inproceedings" crossref="er2001">
		<names type="sharef:author">
			<person>
				<givenname>David W.</givenname>
				<surname>Embley</surname>
			</person>
			<person>
				<givenname>Wai Yin</givenname>
				<surname>Mok</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Many XML documents are being produced, but there are no agreed-upon standards formally defining what it means for complying XML documents to have "good" properties. In this paper we present a formal definition for a proposed canonical normal form for XML documents called XNF. XNF guarantees that complying XML documents have maximally compact connectivity while simultaneously guaranteeing that the data in complying XML documents cannot be redundant. Further, we present a conceptual-model-based methodology that automatically generates XNF-compliant DTDs and prove that the algorithms, which are part of the methodology, produce DTDs to ensure that all complying XML documents satisfy the properties of XNF.</p>
			</richtext>
		</abstract>
		<pages>426-441</pages>
		<title type="sharef:primaryTitle">Developing XML Documents with Guaranteed "Good" Properties</title>
		<field type="bibtex:topic">dtd[0.7] xnf[1]</field>
		<identifier type="sharef:uri">http://www.springerlink.com/link.asp?id=340lwwh36jm5kvhm</identifier>
	</reference>
	<reference name="er2001" src="bibtex:proceedings" src-info="bibtex:line-10274" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>Hideko S.</givenname>
				<surname>Kunii</surname>
			</person>
			<person>
				<givenname>Sushil</givenname>
				<surname>Jajodia</surname>
			</person>
			<person>
				<givenname>Arne</givenname>
				<surname>Sølvberg</surname>
			</person>
		</names>
		<date value="2001-11"/>
		<address type="sharef:placePublished">Yokohama, Japan</address>
		<field type="bibtex:index">ER 2001</field>
		<identifier type="sharef:isbn">3540428666</identifier>
		<publisher>Springer-Verlag</publisher>
		<title type="sharef:seriesTitle">Lecture Notes in Computer Science</title>
		<title type="sharef:primaryTitle">20th International Conference on Conceptual Modeling</title>
		<identifier type="sharef:uri" resourceType="text/html">http://www.informatik.uni-trier.de/%7Eley/db/conf/er/er2001.html</identifier>
		<volume>2224</volume>
	</reference>
	<reference name="mar00" src="bibtex:inproceedings" src-info="bibtex:line-10293" type="sharef:inproceedings" crossref="iccs2000">
		<names type="sharef:author">
			<person>
				<givenname>Philippe</givenname>
				<surname>Martin</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Much research has focused on the problem of knowledge accessibility, sharing and reuse. Specific languages (e.g. KIF, CG, RDF) and ontologies have been proposed. Common characteristics, conventions or ontological distinctions are beginning to emerge. Since knowledge providers (humans and software agents) must follow common conventions for the knowledge to be widely accessed and re-used, we propose lexical, structural, semantic and ontological conventions based on various knowledge representation projects and our own research. These are minimal conventions that can be followed by most and cover the most common knowledge representation cases. However, agreement and refinements are still required. We also show that a notation can be both readable and expressive by quickly presenting two notations — Formalized English (FE) and Frame-CG (FCG) — that we have derived from CG and Frame-Logics. These notations support the above conventions, and are implemented in our Web-based knowledge representation and document indexation tool, WebKB.</p>
			</richtext>
		</abstract>
		<pages>41-54</pages>
		<title type="sharef:primaryTitle">Conventions and Notations for Knowledge Representation and Retrieval</title>
		<field type="bibtex:topic">rdf[0.8] cg[0.8] kif[0.8]</field>
		<identifier type="sharef:uri" resourceType="application/pdf">http://meganesia.int.gu.edu.au/~phmartin/WebKB/doc/papers/iccs00/iccs00.pdf</identifier>
	</reference>
	<reference name="iccs2000" src="bibtex:proceedings" src-info="bibtex:line-10303" type="sharef:proceedings">
		<date value="2000-08"/>
		<address type="sharef:placePublished">Darmstadt, Germany</address>
		<field type="bibtex:index">ICCS 2000</field>
		<publisher>Springer-Verlag</publisher>
		<title type="sharef:seriesTitle">Lecture Notes in Artificial Intelligence</title>
		<title type="sharef:primaryTitle">8th International Conference on Conceptual Structures</title>
		<volume>1867</volume>
	</reference>
	<reference name="car96" src="bibtex:inproceedings" src-info="bibtex:line-10319" type="sharef:inproceedings" crossref="wetice96">
		<names type="sharef:author">
			<person>
				<givenname>Germano</givenname>
				<surname>Caronni</surname>
			</person>
			<person>
				<givenname>Hannes P.</givenname>
				<surname>Lubich</surname>
			</person>
			<person>
				<givenname>Ashar</givenname>
				<surname>Aziz</surname>
			</person>
			<person>
				<givenname>Tom</givenname>
				<surname>Markson</surname>
			</person>
			<person>
				<givenname>Rich</givenname>
				<surname>Skrenta</surname>
			</person>
		</names>
		<pages>62-67</pages>
		<title type="sharef:primaryTitle">SKIP — Securing the Internet</title>
		<field type="bibtex:topic">skip[0.9]</field>
	</reference>
	<reference name="wetice96" src="bibtex:proceedings" src-info="bibtex:line-10327" type="sharef:proceedings">
		<date value="1996-06"/>
		<address type="sharef:placePublished">Stanford, California</address>
		<field type="bibtex:index">WET ICE '96</field>
		<title type="sharef:primaryTitle">Fifth Workshop on Enabling Technologies: Infrastructures for Collaborative Enterprises</title>
	</reference>
	<reference name="hal02" src="bibtex:inproceedings" src-info="bibtex:line-10340" type="sharef:inproceedings" crossref="drm2002">
		<names type="sharef:author">
			<person>
				<givenname>John A.</givenname>
				<surname>Halderman</surname>
			</person>
		</names>
		<title type="sharef:primaryTitle">Evaluating New Copy-Prevention Techniques for Audio CDs</title>
		<field type="bibtex:topic">cdda[0.8]</field>
		<identifier type="sharef:uri" resourceType="application/pdf">http://www.cs.princeton.edu/~jhalderm/papers/drm2002.pdf</identifier>
	</reference>
	<reference name="drm2002" src="bibtex:proceedings" src-info="bibtex:line-10348" type="sharef:proceedings">
		<date value="2002-11"/>
		<address type="sharef:placePublished">Washington, D.C.</address>
		<field type="bibtex:index">DRM 2002</field>
		<title type="sharef:primaryTitle">2002 ACM Workshop on Digital Rights Management</title>
		<field type="bibtex:topic">drm[0.8]</field>
		<identifier type="sharef:uri">http://crypto.stanford.edu/DRM2002/</identifier>
	</reference>
	<reference name="mul03b" src="bibtex:inproceedings" src-info="bibtex:line-10363" type="sharef:inproceedings" crossref="drm2003">
		<names type="sharef:author">
			<person>
				<givenname>Deirdre K.</givenname>
				<surname>Mulligan</surname>
			</person>
			<person>
				<givenname>Aaron</givenname>
				<surname>Burstein</surname>
			</person>
		</names>
		<pages>137-154</pages>
		<title type="sharef:primaryTitle">Implementing Copyright Limitations in Rights Expression Languages</title>
		<field type="bibtex:topic">Drafters of rights expression languages (RELs) claim that RELs will form the basis for generic, content-neutral expressions of rights in digital objects, suitable for a broad range of contexts. Generally modeled on access control languages, RELs are structured predominantly as permission languages — meaning that no rights exist in an object until they are affirmatively and specifically granted. The permissions-based exclusivity likely to result from existing RELs and digital rights management (DRM) contrasts with the myriad limitations on exclusivity in the Copyright Act. Unless REL designers and DRM system implementers consider these limitations, DRM systems will alter the copyright balance in the direction of copyright holder exclusivity. In this paper we propose changes to RELs that would approximate the copyright balance more closely than current DRM technologies do.</field>
		<identifier type="sharef:uri">http://www.springerlink.com/content/1pywh2bce3m0712m/</identifier>
	</reference>
	<reference name="drm2003" src="bibtex:proceedings" src-info="bibtex:line-10372" type="sharef:proceedings">
		<date value="2003-11"/>
		<address type="sharef:placePublished">Washington, D.C.</address>
		<identifier type="sharef:doi">10.1007/b11725</identifier>
		<identifier type="sharef:isbn">978-3-540-40410-1</identifier>
		<publisher>Springer-Verlag</publisher>
		<title type="sharef:seriesTitle">Lecture Notes in Computer Science</title>
		<title type="sharef:primaryTitle">2003 ACM Workshop on Digital Rights Management</title>
		<volume>2696</volume>
	</reference>
	<reference name="los03" src="bibtex:inproceedings" src-info="bibtex:line-10389" type="sharef:inproceedings" crossref="widm2003">
		<names type="sharef:author">
			<person>
				<givenname>Bernadette Farias</givenname>
				<surname>Lóscio</surname>
			</person>
			<person>
				<givenname>Ana Carolina</givenname>
				<surname>Salgado</surname>
			</person>
			<person>
				<givenname>Luciano</givenname>
				<surname link="do">Rêgo Galvão</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>XML has become the standard format for representing structured and semi-structured data on the Web. To describe the structure and content of XML data, several XML schema languages have been proposed. Although being very useful for validating XML documents, an XML schema is not suitable for tasks requiring knowledge about the semantics of the represented data. For such tasks it is better to use a conceptual schema. This paper presents an extension of the Entity Relationship (ER) model, called X-Entity, for conceptual modeling of XML schemas. We also present the process of converting a schema, defined in the XML Schema language, to an X-Entity schema. The conversion process is based on a set of rules that consider element declarations and type definitions and generates the corresponding conceptual elements. Such representation provides a cleaner description for XML schemas by focusing only on semantically relevant concepts. The X-Entity model has been used in the context of a Web data integration system with the goal of providing a concise and semantic description for local schemas defined in XML Schema.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/956699.956722</identifier>
		<title type="sharef:primaryTitle">Conceptual Modeling of XML Schemas</title>
		<field type="bibtex:topic">xsd[0.7] xentity[0.9]</field>
		<identifier type="sharef:uri">http://portal.acm.org/citation.cfm?id=956699.956722</identifier>
	</reference>
	<reference name="widm2003" src="bibtex:proceedings" src-info="bibtex:line-10399" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>Roger</givenname>
				<surname>Chiang</surname>
			</person>
			<person>
				<givenname>Alberto H. F.</givenname>
				<surname>Laender</surname>
			</person>
			<person>
				<givenname>Ee-Peng</givenname>
				<surname>Lim</surname>
			</person>
		</names>
		<date value="2003-11"/>
		<address type="sharef:placePublished">New Orleans, Louisiana</address>
		<field type="bibtex:index">WIDM 2003</field>
		<identifier type="sharef:isbn">1-58113-725-7</identifier>
		<title type="sharef:primaryTitle">5th ACM International Workshop on Web Information and Data Management</title>
		<identifier type="sharef:uri">http://portal.acm.org/citation.cfm?id=956699</identifier>
		<identifier type="sharef:uri" resourceType="text/html">http://www.informatik.uni-trier.de/~ley/db/conf/widm/widm2003.html</identifier>
	</reference>
	<reference name="ame04" src="bibtex:inproceedings" src-info="bibtex:line-10416" type="sharef:inproceedings" crossref="widm2004">
		<names type="sharef:author">
			<person>
				<givenname>Sihem</givenname>
				<surname>Amer-Yahia</surname>
			</person>
			<person>
				<givenname>Fang</givenname>
				<surname>Du</surname>
			</person>
			<person>
				<givenname>Juliana</givenname>
				<surname>Freire</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>The use of relational database management systems (RDBMSs) to store and query XML data has attracted considerable interest with a view to leveraging their powerful and reliable data management services. Due to the mismatch between the relational and XML data models, it is necessary to first shred and load the XML data into relational tables, and then translate XML queries over the original data into equivalent SQL queries over the mapped tables. Although there is a rich literature on XML-relational storage, none of the existing solutions addresses all the storage problems in a single framework. Works on mapping strategies often have little or no details about query translation, and proposals for query translation often target a specific mapping strategy. XML-storage solutions provided by RDBMS also have limitations. Notably, they are tied to a specific backend and use proprietary mapping languages, which not only may require a steep learning curve, but often are unable to express certain desirable mappings. In order to address these limitations, we developed ShreX, a XML-to-relational mapping framework and system that provides the first comprehensive and end-to-end solution to the relational storage of XML data. Mappings in ShreX are defined through annotations to an XML Schema. The use of XML Schema simplifies the mapping process, since it does not require users to master a new specialized mapping language. The use of annotations allows mapping choices to be combined in many different ways. As a result, ShreX not only supports all the mapping strategies proposed in the literature, but also new useful strategies that had not been considered previously. ShreX provides generic (and automatic) document shredding and query translation capabilities; and it is portable — its mapping specifications are independent of the database backend.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">1031453.1031461</identifier>
		<field type="bibtex:index">shrex[0.9]</field>
		<pages>31-38</pages>
		<title type="sharef:primaryTitle">A Comprehensive Solution to the XML-to-Relational Mapping Problem</title>
		<identifier type="sharef:uri">http://doi.acm.org/10.1145/1031453.1031461</identifier>
	</reference>
	<reference name="widm2004" src="bibtex:proceedings" src-info="bibtex:line-10427" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>Alberto H. F.</givenname>
				<surname>Laender</surname>
			</person>
			<person>
				<givenname>Dongwon</givenname>
				<surname>Lee</surname>
			</person>
			<person>
				<givenname>Marc</givenname>
				<surname>Ronthaler</surname>
			</person>
		</names>
		<date value="2004-11"/>
		<address type="sharef:placePublished">Washington, D.C.</address>
		<field type="bibtex:index">WIDM 2004</field>
		<identifier type="sharef:isbn">1-58113-978-0</identifier>
		<title type="sharef:primaryTitle">6th ACM International Workshop on Web Information and Data Management</title>
		<identifier type="sharef:uri" resourceType="text/html">http://www.informatik.uni-trier.de/~ley/db/conf/widm/widm2004.html</identifier>
	</reference>
	<reference name="wei05" src="bibtex:inproceedings" src-info="bibtex:line-10443" type="sharef:inproceedings" crossref="widm2005">
		<names type="sharef:author">
			<person>
				<givenname>Felix</givenname>
				<surname>Weigel</surname>
			</person>
			<person>
				<givenname>Klaus U.</givenname>
				<surname>Schulz</surname>
			</person>
			<person>
				<givenname>Holger</givenname>
				<surname>Meuss</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>In XML retrieval, two distinct approaches have been established and pursued without much cross-fertilization taking place so far. On the one hand, native XML databases tailored to the semistructured data model have received considerable attention, and a wealth of index structures, join algorithms, tree encodings and query rewriting techniques for XML have been proposed. On the other hand, the question how to make XML fit the relational data model has been studied in great detail, giving rise to a multitude of storage schemes for XML in relational database systems (RDBSs). In this paper we examine how native XML indexing techniques can boost the retrieval of XML stored in an RDBS. We present the Relational CADG (RCADG), an adaptation of several native indexing approaches to the relational model, and show how it supports the evaluation of a clean formal language of conjunctive XML queries. Unlike relational storage schemes for XML, the RCADG largely preserves the underlying tree structure of the data in the RDBS, thus addressing several open problems known from the literature. Experiments show that the RCADG accelerates retrieval by up to two or even three orders of magnitude compared to both native and relational approaches.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">1097047.1097054</identifier>
		<pages>23-30</pages>
		<title type="sharef:primaryTitle">Exploiting Native XML Indexing Techniques for XML Retrieval in Relational Database Systems</title>
		<identifier type="sharef:uri">http://portal.acm.org/citation.cfm?doid=1097047.1097054</identifier>
	</reference>
	<reference name="gue05" src="bibtex:inproceedings" src-info="bibtex:line-10453" type="sharef:inproceedings" crossref="widm2005">
		<names type="sharef:author">
			<person>
				<givenname>Giovanna</givenname>
				<surname>Guerrini</surname>
			</person>
			<person>
				<givenname>Marco</givenname>
				<surname>Mesiti</surname>
			</person>
			<person>
				<givenname>Daniele</givenname>
				<surname>Rossi</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>In this paper we investigate the problem of XML Schema evolution. We first discuss the different kinds of changes that may be needed on an XML Schema. Then, we investigate how to minimize document revalidation, that is, detecting the document parts potentially invalidated by the schema changes that should be revalidated.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">1097047.1097056</identifier>
		<field type="bibtex:index">xsd[0.8]</field>
		<pages>39-44</pages>
		<title type="sharef:primaryTitle">Impact of XML Schema Evolution on Valid Documents</title>
		<identifier type="sharef:uri">http://portal.acm.org/citation.cfm?id=1097047.1097056</identifier>
	</reference>
	<reference name="widm2005" src="bibtex:proceedings" src-info="bibtex:line-10464" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>Angela</givenname>
				<surname>Bonifati</surname>
			</person>
			<person>
				<givenname>Dongwon</givenname>
				<surname>Lee</surname>
			</person>
		</names>
		<date value="2005-11"/>
		<address type="sharef:placePublished">Bremen, Germany</address>
		<field type="bibtex:index">WIDM 2005</field>
		<identifier type="sharef:isbn">1-59593-194-5</identifier>
		<title type="sharef:primaryTitle">7th ACM International Workshop on Web Information and Data Management</title>
		<identifier type="sharef:uri" resourceType="text/html">http://www.informatik.uni-trier.de/~ley/db/conf/widm/widm2005.html</identifier>
	</reference>
	<reference name="kin08" src="bibtex:inproceedings" src-info="bibtex:line-10480" type="sharef:inproceedings" crossref="widm2008">
		<names type="sharef:author">
			<person>
				<givenname>Sheila</givenname>
				<surname>Kinsella</surname>
			</person>
			<person>
				<givenname>Adriana</givenname>
				<surname>Budura</surname>
			</person>
			<person>
				<givenname>Gleb</givenname>
				<surname>Skobeltsyn</surname>
			</person>
			<person>
				<givenname>Sebastian</givenname>
				<surname>Michel</surname>
			</person>
			<person>
				<givenname>John G.</givenname>
				<surname>Breslin</surname>
			</person>
			<person>
				<givenname>Karl</givenname>
				<surname>Aberer</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>We consider the applicability of terms extracted from anchortext as a source of Web page descriptions in the form of tags. With a relatively simple and easy-to-use method, we show that anchortext significantly overlaps with tags obtained from the popular tagging portal del.icio.us. Considering the size and diversity of the user community potentially involved in social tagging, this observation is rather surprising. Furthermore, we show by an evaluation using human-created relevance assessments the general suitability of the anchortext tag generation in terms of user-perceived precision values. The awareness of this easy-to-obtain source of tags could trigger the rise of new tagging portals pushed by this automatic bootstrapping process or be applied in already existing portals to increase the number of tags per page by merely looking at the anchortext which exists anyway.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/1458502.1458516</identifier>
		<pages>79-86</pages>
		<title type="sharef:primaryTitle">From Web 1.0 to Web 2.0 and Back — How did your Grandma Use to Tag?</title>
		<identifier type="sharef:uri">http://infoscience.epfl.ch/record/126390</identifier>
	</reference>
	<reference name="widm2008" src="bibtex:proceedings" src-info="bibtex:line-10490" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>Chee Yong</givenname>
				<surname>Chan</surname>
			</person>
			<person>
				<givenname>Neoklis</givenname>
				<surname>Polyzotis</surname>
			</person>
		</names>
		<date value="2008-10"/>
		<address type="sharef:placePublished">Napa Valley, California</address>
		<field type="bibtex:index">WIDM 2008</field>
		<identifier type="sharef:isbn">978-1-60558-260-3</identifier>
		<title type="sharef:primaryTitle">10th ACM International Workshop on Web Information and Data Management</title>
		<identifier type="sharef:uri" resourceType="text/html">http://www.informatik.uni-trier.de/~ley/db/conf/widm/widm2008.html</identifier>
	</reference>
	<reference name="ash97" src="bibtex:inproceedings" src-info="bibtex:line-10506" type="sharef:inproceedings" crossref="him97">
		<names type="sharef:author">
			<person>
				<givenname>Helen</givenname>
				<surname>Ashman</surname>
			</person>
			<person>
				<givenname>Alejandra</givenname>
				<surname>Garrido</surname>
			</person>
			<person>
				<givenname>Harri</givenname>
				<surname>Oinas-Kukkonen</surname>
			</person>
		</names>
		<field type="bibtex:index">hypermedia</field>
		<pages>191-208</pages>
		<title type="sharef:primaryTitle">Hand-Made and Computed Links, Precomputed and Dynamic Links</title>
	</reference>
	<reference name="him97" src="bibtex:proceedings" src-info="bibtex:line-10514" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>Norbert</givenname>
				<surname>Fuhr</surname>
			</person>
			<person>
				<givenname>Gisbert</givenname>
				<surname>Dittrich</surname>
			</person>
			<person>
				<givenname>Klaus</givenname>
				<surname>Tochtermann</surname>
			</person>
		</names>
		<date value="1997-09"/>
		<address type="sharef:placePublished">Dortmund, Germany</address>
		<field type="bibtex:index">HIM'97</field>
		<title type="sharef:primaryTitle">Hypermedia — Information Retrieval — Multimedia 1997</title>
	</reference>
	<reference name="hel97" src="bibtex:inproceedings" src-info="bibtex:line-10528" type="sharef:inproceedings" crossref="kivs97">
		<names type="sharef:author">
			<person>
				<givenname>Tobias</givenname>
				<surname>Helbig</surname>
			</person>
			<person>
				<givenname>Dirk</givenname>
				<surname>Trossen</surname>
			</person>
		</names>
		<field type="bibtex:index">T.120</field>
		<title type="sharef:primaryTitle">Die ITU Standard-Familie T.120 als Basis für verteilte Mehrbenutzeranwendungen</title>
	</reference>
	<reference name="kivs97" src="bibtex:proceedings" src-info="bibtex:line-10535" type="sharef:proceedings">
		<date value="1997-03"/>
		<address type="sharef:placePublished">Braunschweig, Germany</address>
		<field type="bibtex:index">KiVS '97</field>
		<title type="sharef:primaryTitle">GI-Fachtagung Kommunikation in Verteilten Systemen</title>
	</reference>
	<reference name="jag01" src="bibtex:inproceedings" src-info="bibtex:line-10548" type="sharef:inproceedings" crossref="dbpl01">
		<names type="sharef:author">
			<person>
				<givenname>H. V.</givenname>
				<surname>Jagadish</surname>
			</person>
			<person>
				<givenname>Laks V. S.</givenname>
				<surname>Lakshmanan</surname>
			</person>
			<person>
				<givenname>Divesh</givenname>
				<surname>Srivastava</surname>
			</person>
			<person>
				<givenname>Keith</givenname>
				<surname>Thompson</surname>
			</person>
		</names>
		<title type="sharef:primaryTitle">TAX: A Tree Algebra for XML</title>
		<field type="bibtex:topic">tax[1]</field>
		<identifier type="sharef:uri" resourceType="application/pdf">http://www.eecs.umich.edu/db/timber/files/tax_full.pdf</identifier>
	</reference>
	<reference name="dbpl01" src="bibtex:proceedings" src-info="bibtex:line-10556" type="sharef:proceedings">
		<date value="2001-09"/>
		<address type="sharef:placePublished">Rome, Italy</address>
		<field type="bibtex:index">DBPL 2001</field>
		<title type="sharef:primaryTitle">8th International Workshop on Databases and Programming Languages</title>
	</reference>
	<reference name="kle07" src="bibtex:inproceedings" src-info="bibtex:line-10569" type="sharef:inproceedings" crossref="btw2007">
		<names type="sharef:author">
			<person>
				<givenname>Meike</givenname>
				<surname>Klettke</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Most available approaches for XML schema evolution specify the evolution steps for an XML schema or a DTD. This article will show that schema evolution can also be realized on a conceptual model. Schema evolution always requires propagating the changes to the XML documents that are already associated to the schema. This article suggests a method for conceptual schema evolution concerning all these subtasks. It is implemented in a tool called CoDEX (Conceptual Design and Evolution of XML schemas).</p>
			</richtext>
		</abstract>
		<pages>53-63</pages>
		<title type="sharef:primaryTitle">Conceptual XML Schema Evolution — The CoDEX Approach for Design and Redesign</title>
		<field type="bibtex:topic">codex[1]</field>
		<identifier type="sharef:uri" resourceType="application/pdf">http://dbs.cs.uni-duesseldorf.de/BTW2007/Klettke.pdf</identifier>
	</reference>
	<reference name="btw2007" src="bibtex:proceedings" src-info="bibtex:line-10579" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>Matthias</givenname>
				<surname>Jarke</surname>
			</person>
			<person>
				<givenname>Thomas</givenname>
				<surname>Seidl</surname>
			</person>
			<person>
				<givenname>Christoph</givenname>
				<surname>Quix</surname>
			</person>
			<person>
				<givenname>David</givenname>
				<surname>Kensche</surname>
			</person>
			<person>
				<givenname>Stefan</givenname>
				<surname>Conrad</surname>
			</person>
			<person>
				<givenname>Erhard</givenname>
				<surname>Rahm</surname>
			</person>
			<person>
				<givenname>Ralf</givenname>
				<surname>Klamma</surname>
			</person>
			<person>
				<givenname>Harald</givenname>
				<surname>Kosch</surname>
			</person>
			<person>
				<givenname>Michael</givenname>
				<surname>Granitzer</surname>
			</person>
			<person>
				<givenname>Sven</givenname>
				<surname>Apel</surname>
			</person>
			<person>
				<givenname>Marko</givenname>
				<surname>Rosenmüller</surname>
			</person>
			<person>
				<givenname>Gunter</givenname>
				<surname>Saake</surname>
			</person>
			<person>
				<givenname>Olaf</givenname>
				<surname>Spinczyk</surname>
			</person>
		</names>
		<date value="2007-03"/>
		<address type="sharef:placePublished">Aachen, Germany</address>
		<identifier type="sharef:isbn">3-86130-929-7</identifier>
		<title type="sharef:primaryTitle">Datenbanksysteme in Business, Technologie und Web (BTW 2007)</title>
		<identifier type="sharef:uri">http://www.informatik.uni-trier.de/~ley/db/conf/btw/btw2007w.html#Klettke07</identifier>
	</reference>
	<reference name="vog94" src="bibtex:inproceedings" src-info="bibtex:line-10594" type="sharef:inproceedings" crossref="itg94">
		<names type="sharef:author">
			<person>
				<givenname>Martin</givenname>
				<surname>Vogt</surname>
			</person>
			<person>
				<givenname>Thomas</givenname>
				<surname>Plagemann</surname>
			</person>
			<person>
				<givenname>Bernhard</givenname>
				<surname>Plattner</surname>
			</person>
			<person>
				<givenname>Thomas</givenname>
				<surname>Walter</surname>
			</person>
		</names>
		<field type="bibtex:index">Da CaPo, parallel processing</field>
		<title type="sharef:primaryTitle">Parallelitätsaspekte in Da CaPo</title>
	</reference>
	<reference name="itg94" src="bibtex:proceedings" src-info="bibtex:line-10601" type="sharef:proceedings">
		<date value="1994-01"/>
		<address type="sharef:placePublished">Karlsruhe, Germany</address>
		<field type="bibtex:index">GI/ITG-Fachgruppe Kommunikation und Verteilte Systeme</field>
		<title type="sharef:primaryTitle">1. GI/ITG Arbeitstreffen zur Architektur und Implementierung von Hochleistungs-Kommunikationssystemen</title>
	</reference>
	<reference name="cha00" src="bibtex:inproceedings" src-info="bibtex:line-10614" type="sharef:inproceedings" crossref="webdb2000">
		<names type="sharef:author">
			<person>
				<givenname>Donald D.</givenname>
				<surname>Chamberlin</surname>
			</person>
			<person>
				<givenname>Jonathan</givenname>
				<surname>Robie</surname>
			</person>
			<person>
				<givenname>Daniela</givenname>
				<surname>Florescu</surname>
			</person>
		</names>
		<pages>1-25</pages>
		<title type="sharef:primaryTitle">Quilt: An XML Query Language for Heterogeneous Data Sources</title>
		<field type="bibtex:topic">quilt[1]</field>
		<identifier type="sharef:uri" resourceType="application/pdf">http://link.springer-ny.com/link/service/series/0558/papers/1997/19970001.pdf</identifier>
	</reference>
	<reference name="hos00" src="bibtex:inproceedings" src-info="bibtex:line-10623" type="sharef:inproceedings" crossref="webdb2000">
		<names type="sharef:author">
			<person>
				<givenname>Haruo</givenname>
				<surname>Hosoya</surname>
			</person>
			<person>
				<givenname>Benjamin C.</givenname>
				<surname>Pierce</surname>
			</person>
		</names>
		<pages>226-244</pages>
		<title type="sharef:primaryTitle">XDuce: A Typed XML Processing Language</title>
		<field type="bibtex:topic">xduce[1]</field>
		<identifier type="sharef:uri" resourceType="application/pdf">http://link.springer-ny.com/link/service/series/0558/papers/1997/19970226.pdf</identifier>
	</reference>
	<reference name="kle00" src="bibtex:inproceedings" src-info="bibtex:line-10632" type="sharef:inproceedings" crossref="webdb2000">
		<names type="sharef:author">
			<person>
				<givenname>Meike</givenname>
				<surname>Klettke</surname>
			</person>
			<person>
				<givenname>Holger</givenname>
				<surname>Meyer</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>XML becomes the standard for the representation of structured and semi-structured data on the Web. Relational and object-relational database systems are a well understood technique for managing and querying such large sets of structured data. Using an object-relational data model and an XML datatype, we show how a relevant subset of XML documents and their implied structure can be mapped onto database structures. Besides straight-forward mappings, there are some XML structures that cannot be easily mapped onto database structures. These structures would sometimes result in large database schemas and sparsely populated databases. As a consequence, such XML document fragments should be mapped onto database attributes of type XML and kept as is. The XML datatype implementation should support evaluating path expressions and fulltext operations. We present an algorithm that finds a type of optimal mapping based on the XML Document Type Definition (DTD) and statistics. The statistics are derived from sample XML document sets and some knowledge about queries on XML document collections.</p>
			</richtext>
		</abstract>
		<pages>151-170</pages>
		<title type="sharef:primaryTitle">XML and Object-Relational Database Systems — Enhancing Structural Mappings Based on Statistics</title>
		<identifier type="sharef:uri">http://www.springerlink.com/link.asp?id=805ey87jf1pnv55f</identifier>
	</reference>
	<reference name="webdb2000" src="bibtex:proceedings" src-info="bibtex:line-10641" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>Dan</givenname>
				<surname>Suciu</surname>
			</person>
			<person>
				<givenname>Gottfried</givenname>
				<surname>Vossen</surname>
			</person>
		</names>
		<date value="2000-05"/>
		<address type="sharef:placePublished">Dallas, Texas</address>
		<field type="bibtex:index">WebDB 2000</field>
		<identifier type="sharef:isbn">3-540-41826-1</identifier>
		<publisher>Springer-Verlag</publisher>
		<title type="sharef:seriesTitle">Lecture Notes in Computer Science</title>
		<title type="sharef:primaryTitle">The World Wide Web and Databases: Third International Workshop WebDB 2000, Selected Papers</title>
		<identifier type="sharef:uri" resourceType="text/html">http://link.springer-ny.com/link/service/series/0558/tocs/t1997.htm</identifier>
		<volume>1997</volume>
	</reference>
	<reference name="wol99" src="bibtex:inproceedings" src-info="bibtex:line-10660" type="sharef:inproceedings" crossref="ngits99">
		<names type="sharef:author">
			<person>
				<givenname>Jens E.</givenname>
				<surname>Wolff</surname>
			</person>
			<person>
				<givenname>Armin B.</givenname>
				<surname>Cremers</surname>
			</person>
		</names>
		<field type="bibtex:index">myview</field>
		<pages>277-294</pages>
		<title type="sharef:primaryTitle">The MyView Project: A Data Warehousing Approach to Personalized Digital Libraries</title>
		<identifier type="sharef:uri" resourceType="application/pdf">http://link.springer-ny.com/link/service/series/0558/papers/1997/19970226.pdf</identifier>
	</reference>
	<reference name="ngits99" src="bibtex:proceedings" src-info="bibtex:line-10669" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>Ron Y.</givenname>
				<surname>Pinter</surname>
			</person>
			<person>
				<givenname>Shalom</givenname>
				<surname>Tsur</surname>
			</person>
		</names>
		<date value="1999-07"/>
		<address type="sharef:placePublished">Zikhron-Yaakov, Israel</address>
		<field type="bibtex:index">NGITS'99</field>
		<publisher>Springer-Verlag</publisher>
		<title type="sharef:seriesTitle">Lecture Notes in Computer Science</title>
		<title type="sharef:primaryTitle">Fourth International Workshop on Next Generation Information Technologies and Systems</title>
		<identifier type="sharef:uri">http://www.springer.de/cgi/svcat/search_book.pl?isbn=3-540-66225-1</identifier>
		<volume>1649</volume>
	</reference>
	<reference name="sch93" src="bibtex:inproceedings" src-info="bibtex:line-10687" type="sharef:inproceedings" crossref="fse93">
		<names type="sharef:author">
			<person>
				<givenname>Bruce</givenname>
				<surname>Schneier</surname>
			</person>
		</names>
		<pages>191-204</pages>
		<title type="sharef:primaryTitle">Description of a New Variable-Length Key, 64-Bit Block Cipher (Blowfish)</title>
	</reference>
	<reference name="fse93" src="bibtex:proceedings" src-info="bibtex:line-10694" type="sharef:proceedings">
		<date value="1993-12"/>
		<address type="sharef:placePublished">Cambridge, UK</address>
		<publisher>Springer-Verlag</publisher>
		<title type="sharef:seriesTitle">Lecture Notes in Computer Science</title>
		<title type="sharef:primaryTitle">Fast Software Encryption, Cambridge Security Workshop Proceedings</title>
		<volume>809</volume>
	</reference>
	<reference name="eck96" src="bibtex:inproceedings" src-info="bibtex:line-10709" type="sharef:inproceedings" crossref="doct96">
		<names type="sharef:author">
			<person>
				<givenname>Klaus-Peter</givenname>
				<surname>Eckert</surname>
			</person>
			<person>
				<givenname>M. Khayrat</givenname>
				<surname>Durmosch</surname>
			</person>
			<person>
				<givenname>Klaus-Dietrich</givenname>
				<surname>Engel</surname>
			</person>
			<person>
				<givenname>Peter</givenname>
				<surname>Schoo</surname>
			</person>
		</names>
		<field type="bibtex:index">TANGRAM</field>
		<title type="sharef:primaryTitle">A CORBA 2 Based Distributed Processing Environment for Telecommunication Applications</title>
	</reference>
	<reference name="doct96" src="bibtex:proceedings" src-info="bibtex:line-10716" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>A.</givenname>
				<surname>Gavras</surname>
			</person>
		</names>
		<date value="1996-10"/>
		<address type="sharef:placePublished">Frankfurt, Germany</address>
		<field type="bibtex:index">DOCT '96</field>
		<title type="sharef:primaryTitle">Distributed Object Computing for Telecom Conference</title>
	</reference>
	<reference name="lai90" src="bibtex:inproceedings" src-info="bibtex:line-10730" type="sharef:inproceedings" crossref="ecrypt90">
		<names type="sharef:author">
			<person>
				<givenname>Xuejia</givenname>
				<surname>Lai</surname>
			</person>
			<person>
				<givenname>James L.</givenname>
				<surname>Massey</surname>
			</person>
		</names>
		<field type="bibtex:index">IDEA</field>
		<pages>389-404</pages>
		<title type="sharef:primaryTitle">A Proposal for a New Block Encryption Standard</title>
	</reference>
	<reference name="ecrypt90" src="bibtex:proceedings" src-info="bibtex:line-10738" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>I. B.</givenname>
				<surname>Damgard</surname>
			</person>
		</names>
		<date value="1991-05"/>
		<address type="sharef:placePublished">Århus, Denmark</address>
		<field type="bibtex:index">EUROCRYPT '90</field>
		<identifier type="sharef:isbn">038753587X</identifier>
		<publisher>Springer-Verlag</publisher>
		<title type="sharef:seriesTitle">Lecture Notes in Computer Science</title>
		<title type="sharef:primaryTitle">EUROCRYPT '90 — Advances in cryptology</title>
		<volume>473</volume>
	</reference>
	<reference name="par02" src="bibtex:inproceedings" src-info="bibtex:line-10756" type="sharef:inproceedings" crossref="sigir02">
		<names type="sharef:author">
			<person>
				<givenname>Seung-Taek</givenname>
				<surname>Park</surname>
			</person>
			<person>
				<givenname>David M.</givenname>
				<surname>Pennock</surname>
			</person>
			<person>
				<givenname>C. Lee</givenname>
				<surname>Giles</surname>
			</person>
			<person>
				<givenname>Robert</givenname>
				<surname>Krovetz</surname>
			</person>
		</names>
		<identifier type="sharef:doi">10.1145/564376.564381</identifier>
		<pages>11-18</pages>
		<title type="sharef:primaryTitle">Analysis of Lexical Signatures for Finding Lost or Related Documents</title>
	</reference>
	<reference name="sigir02" src="bibtex:proceedings" src-info="bibtex:line-10764" type="sharef:proceedings">
		<date value="2002-08"/>
		<address type="sharef:placePublished">Tampere, Finland</address>
		<field type="bibtex:index">SIGIR 2002</field>
		<identifier type="sharef:isbn">1581135610</identifier>
		<publisher>ACM Press</publisher>
		<title type="sharef:primaryTitle">25th Annual International ACM SIGIR Conference on Research and Development in Information Retrieval</title>
		<identifier type="sharef:uri">http://portal.acm.org/toc.cfm?id=564376</identifier>
		<identifier type="sharef:uri" resourceType="text/html">http://www.informatik.uni-trier.de/~ley/db/conf/sigir/sigir2002.html</identifier>
	</reference>
	<reference name="car03" src="bibtex:inproceedings" src-info="bibtex:line-10781" type="sharef:inproceedings" crossref="sigir03">
		<names type="sharef:author">
			<person>
				<givenname>David</givenname>
				<surname>Carmel</surname>
			</person>
			<person>
				<givenname>Yoëlle S.</givenname>
				<surname>Maarek</surname>
			</person>
			<person>
				<givenname>Matan</givenname>
				<surname>Mandelbrod</surname>
			</person>
			<person>
				<givenname>Yosi</givenname>
				<surname>Mass</surname>
			</person>
			<person>
				<givenname>Aya</givenname>
				<surname>Soffer</surname>
			</person>
		</names>
		<identifier type="sharef:doi">10.1145/860435.860464</identifier>
		<pages>151-158</pages>
		<title type="sharef:primaryTitle">Searching XML documents via XML fragments</title>
		<field type="bibtex:topic">xml[0.7]</field>
	</reference>
	<reference name="asl03" src="bibtex:inproceedings" src-info="bibtex:line-10790" type="sharef:inproceedings" crossref="sigir03">
		<names type="sharef:author">
			<person>
				<givenname>Javed A.</givenname>
				<surname>Aslam</surname>
			</person>
			<person>
				<givenname>Meredith</givenname>
				<surname>Frost</surname>
			</person>
		</names>
		<identifier type="sharef:doi">10.1145/860435.860545</identifier>
		<pages>449-450</pages>
		<title type="sharef:primaryTitle">An Information-theoretic Measure for Document Similarity</title>
	</reference>
	<reference name="sigir03" src="bibtex:proceedings" src-info="bibtex:line-10798" type="sharef:proceedings">
		<date value="2003-07"/>
		<address type="sharef:placePublished">Toronto, Canada</address>
		<field type="bibtex:index">SIGIR 2003</field>
		<identifier type="sharef:isbn">1581136463</identifier>
		<publisher>ACM Press</publisher>
		<title type="sharef:primaryTitle">26th Annual International ACM SIGIR Conference on Research and Development in Information Retrieval</title>
		<identifier type="sharef:uri">http://portal.acm.org/citation.cfm?id=860435</identifier>
		<identifier type="sharef:uri" resourceType="text/html">http://www.informatik.uni-trier.de/~ley/db/conf/sigir/sigir2003.html</identifier>
	</reference>
	<reference name="ami04" src="bibtex:inproceedings" src-info="bibtex:line-10815" type="sharef:inproceedings" crossref="sigir04">
		<names type="sharef:author">
			<person>
				<givenname>Einat</givenname>
				<surname>Amitay</surname>
			</person>
			<person>
				<givenname>Nadav</givenname>
				<surname>Har'El</surname>
			</person>
			<person>
				<givenname>Ron</givenname>
				<surname>Sivan</surname>
			</person>
			<person>
				<givenname>Aya</givenname>
				<surname>Soffer</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>We describe Web-a-Where, a system for associating geography with Web pages. Web-a-Where locates mentions of places and determines the place each name refers to. In addition, it assigns to each page a geographic focus — a locality that the page discusses as a whole. The tagging process is simple and fast, aimed to be applied to large collections of Web pages and to facilitate a variety of location-based applications and data analyses. Geotagging involves arbitrating two types of ambiguities: geo/non-geo and geo/geo. A geo/non-geo ambiguity occurs when a place name also has a non-geographic meaning, such as a person name (e.g., Berlin) or a common word (Turkey). Geo/geo ambiguity arises when distinct places have the same name, as in London, England vs. London, Ontario. An implementation of the tagger within the framework of the WebFountain data mining system is described, and evaluated on several corpora of real Web pages. Precision of up to 82% on individual geotags is achieved. We also evaluate the relative contribution of various heuristics the tagger employs, and evaluate the focus-finding algorithm using a corpus pretagged with localities, showing that as many as 91% of the foci reported are correct up to the country level.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/1008992.1009040</identifier>
		<pages>273-280</pages>
		<title type="sharef:primaryTitle">Web-a-Where: Geotagging Web Content</title>
		<identifier type="sharef:uri" resourceType="application/pdf">einat.webir.org/SIGIR_2004_GeoMiner_p273-amitay.pdf</identifier>
	</reference>
	<reference name="sigir04" src="bibtex:proceedings" src-info="bibtex:line-10825" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>Mark</givenname>
				<surname>Sanderson</surname>
			</person>
			<person>
				<givenname>Kalervo</givenname>
				<surname>Järvelin</surname>
			</person>
			<person>
				<givenname>James</givenname>
				<surname>Allan</surname>
			</person>
			<person>
				<givenname>Peter</givenname>
				<surname>Bruza</surname>
			</person>
		</names>
		<date value="2004-07"/>
		<address type="sharef:placePublished">Sheffield, UK</address>
		<field type="bibtex:index">SIGIR 2004</field>
		<identifier type="sharef:isbn">1-58113-881-4</identifier>
		<publisher>ACM Press</publisher>
		<title type="sharef:primaryTitle">27th Annual International ACM SIGIR Conference on Research and Development in Information Retrieval</title>
		<identifier type="sharef:uri" resourceType="text/html">http://www.informatik.uni-trier.de/~ley/db/conf/sigir/sigir2004.html</identifier>
	</reference>
	<reference name="rat07" src="bibtex:inproceedings" src-info="bibtex:line-10842" type="sharef:inproceedings" crossref="sigir07">
		<names type="sharef:author">
			<person>
				<givenname>Tye</givenname>
				<surname>Rattenbury</surname>
			</person>
			<person>
				<givenname>Nathaniel</givenname>
				<surname>Good</surname>
			</person>
			<person>
				<givenname>Mor</givenname>
				<surname>Naaman</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>We describe an approach for extracting semantics of tags, unstructured text-labels assigned to resources on the Web, based on each tag's usage patterns. In particular, we focus on the problem of extracting place and event semantics for tags that are assigned to photos on Flickr, a popular photo sharing website that supports time and location (latitude/longitude) metadata. We analyze two methods inspired by well-known burst-analysis techniques and one novel method: Scale-structure Identification. We evaluate the methods on a subset of Flickr data, and show that our Scale-structure Identification method outperforms the existing techniques. The approach and methods described in this work can be used in other domains such as geo-annotated web pages, where text terms can be extracted and associated with usage patterns.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/1277741.1277762</identifier>
		<pages>103-110</pages>
		<title type="sharef:primaryTitle">Analysis of Lexical Signatures for Finding Lost or Related Documents</title>
		<identifier type="sharef:uri" resourceType="application/pdf">http://infolab.stanford.edu/~mor/research/sigir2007rattenburyTagSemantics.pdf</identifier>
	</reference>
	<reference name="sch07d" src="bibtex:inproceedings" src-info="bibtex:line-10852" type="sharef:inproceedings" crossref="sigir07">
		<names type="sharef:author">
			<person>
				<givenname>Steven</givenname>
				<surname>Schockaert</surname>
			</person>
			<person>
				<givenname>Martine</givenname>
				<surname>De Cock</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Geographic information retrieval (GIR) systems allow users to specify a geographic context, in addition to a more traditional query, enabling the system to pinpoint interesting search results whose relevancy is location-dependent. In particular local search services have become a widely used mechanism to find businesses, such as hotels, restaurants, and shops, which satisfy a geographical restriction. Unfortunately, many useful types of geographic restrictions are currently not supported in these systems, including restrictions that specify the neighborhood in which the business should be located. As the boundaries of city neighborhoods are not readily available, automated techniques to construct representations of the spatial extent of neighborhoods are required to support this kind of restrictions. In this paper, we propose such a technique, using fuzzy footprints to cope with the inherent vagueness of most neighborhood boundaries, and we provide experimental results that demonstrate the potential of our technique in a local search setting.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">http://doi.acm.org/10.1145/1277741.1277772</identifier>
		<pages>167-174</pages>
		<title type="sharef:primaryTitle">Neighborhood Restrictions in Geographic IR</title>
		<identifier type="sharef:uri" resourceType="application/pdf">http://www.cwi.ugent.be/martine/papers/volledig/sschockaert2007b.pdf</identifier>
	</reference>
	<reference name="sigir07" src="bibtex:proceedings" src-info="bibtex:line-10862" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>Wessel</givenname>
				<surname>Kraaij</surname>
			</person>
			<person>
				<givenname>Arjen P.</givenname>
				<surname link="de">Vries</surname>
			</person>
			<person>
				<givenname>Charles L. A.</givenname>
				<surname>Clarke</surname>
			</person>
			<person>
				<givenname>Norbert</givenname>
				<surname>Fuhr</surname>
			</person>
			<person>
				<givenname>Noriko</givenname>
				<surname>Kando</surname>
			</person>
		</names>
		<date value="2007-07"/>
		<address type="sharef:placePublished">Amsterdam, Netherlands</address>
		<field type="bibtex:index">SIGIR 2007</field>
		<identifier type="sharef:isbn">978-1-59593-597-7</identifier>
		<publisher>ACM Press</publisher>
		<title type="sharef:primaryTitle">30th Annual International ACM SIGIR Conference on Research and Development in Information Retrieval</title>
		<identifier type="sharef:uri" resourceType="text/html">http://www.informatik.uni-trier.de/~ley/db/conf/sigir/sigir2007.html</identifier>
	</reference>
	<reference name="sim03b" src="bibtex:inproceedings" src-info="bibtex:line-10879" type="sharef:inproceedings" crossref="popl03">
		<names type="sharef:author">
			<person>
				<givenname>Jérôme</givenname>
				<surname>Siméon</surname>
			</person>
			<person>
				<givenname>Philip</givenname>
				<surname>Wadler</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>The World-Wide Web Consortium (W3C) promotes XML and related standards, including XML Schema, XQuery, and XPath. This paper describes a formalization of XML Schema. A formal semantics based on these ideas is part of the official XQuery and XPath specification, one of the first uses of formal methods by a standards body. XML Schema features both named and structural types, with structure based on tree grammars. While structural types and matching have been studied in other work (notably XDuce, Relax NG, and a previous formalization of XML Schema), this is the first work to study the relation between named types and structural types, and the relation between matching and validation.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/604131.604132</identifier>
		<field type="bibtex:index">xml[0.8]</field>
		<pages>1-13</pages>
		<title type="sharef:primaryTitle">The Essence of XML</title>
		<identifier type="sharef:uri">http://portal.acm.org/citation.cfm?id=604132</identifier>
	</reference>
	<reference name="popl03" src="bibtex:proceedings" src-info="bibtex:line-10890" type="sharef:proceedings">
		<date value="2003-01"/>
		<address type="sharef:placePublished">New Orleans, Louisiana</address>
		<field type="bibtex:index">POPL 2003</field>
		<identifier type="sharef:isbn">1-58113-628-5</identifier>
		<publisher>ACM Press</publisher>
		<title type="sharef:primaryTitle">30th ACM SIGPLAN-SIGACT Symposium on Principles of Programming Languages</title>
		<identifier type="sharef:uri" resourceType="text/html">http://www.informatik.uni-trier.de/~ley/db/conf/popl/popl2003.html</identifier>
	</reference>
	<reference name="owr92" src="bibtex:inproceedings" src-info="bibtex:line-10906" type="sharef:inproceedings" crossref="cade92">
		<names type="sharef:author">
			<person>
				<givenname>Sam</givenname>
				<surname>Owre</surname>
			</person>
			<person>
				<givenname>John M.</givenname>
				<surname>Rushby</surname>
			</person>
			<person>
				<givenname>Natarajan</givenname>
				<surname>Shankar</surname>
			</person>
		</names>
		<field type="bibtex:index">pvs[1]</field>
		<pages>748-752</pages>
		<title type="sharef:primaryTitle">PVS: A Prototype Verification System</title>
		<identifier type="sharef:uri">http://www.csl.sri.com/papers/cade92-pvs/</identifier>
	</reference>
	<reference name="cade92" src="bibtex:proceedings" src-info="bibtex:line-10915" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>Deepak</givenname>
				<surname>Kapur</surname>
			</person>
		</names>
		<date value="1992-06"/>
		<address type="sharef:placePublished">Saratoga Springs, New York</address>
		<field type="bibtex:index">CADE-11</field>
		<identifier type="sharef:isbn">3-540-55602-8</identifier>
		<publisher>Springer-Verlag</publisher>
		<title type="sharef:seriesTitle">Lecture Notes in Artificial Intelligence</title>
		<title type="sharef:primaryTitle">Automated Deduction — CADE-11, 11th International Conference on Automated Deduction</title>
		<identifier type="sharef:uri" resourceType="text/html">http://www.springer.com/sgw/cda/frontpage/0,11855,5-0-22-1379329-0,00.html</identifier>
		<identifier type="sharef:uri" resourceType="text/html">http://www.informatik.uni-trier.de/~ley/db/conf/cade/cade92.html</identifier>
		<volume>607</volume>
	</reference>
	<reference name="jae82" src="bibtex:inproceedings" src-info="bibtex:line-10935" type="sharef:inproceedings" crossref="pods82">
		<names type="sharef:author">
			<person>
				<givenname>Gerhard</givenname>
				<surname>Jaeschke</surname>
			</person>
			<person>
				<givenname>Hans-Jörg</givenname>
				<surname>Schek</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Usually, the first normal form condition of the relational model of data is imposed. Presently, a broader class of data base applications like office information systems is considered where this restriction is not convenient. Therefore, an extension of the relational model is proposed consisting of Non First Normal Form (NF²) relations. The relational algebra is enriched mainly by so called nest and unnest operations which transform between NF² relations and the usual ones. We state some properties of these operations and some rules which occur in combination with the operations of the usual relational algebra. Since we propose to use the NF² model also for the internal data model these rules are important not only for theoretical reasons but also for a practical implementation.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/588111.588133</identifier>
		<field type="bibtex:index">1nf[0.8] nfnf[1]</field>
		<pages>124-138</pages>
		<title type="sharef:primaryTitle">Remarks on the Algebra of Non First Normal Form Relations</title>
		<identifier type="sharef:uri" resourceType="text/html">http://www.informatik.uni-trier.de/~ley/db/conf/pods/JaeschkeS82.html</identifier>
	</reference>
	<reference name="pods82" src="bibtex:proceedings" src-info="bibtex:line-10946" type="sharef:proceedings">
		<date value="1982-03"/>
		<address type="sharef:placePublished">Los Angeles, California</address>
		<field type="bibtex:index">PODS '82</field>
		<publisher>ACM Press</publisher>
		<title type="sharef:primaryTitle">ACM SIGACT-SIGMOD Symposium on Principles of Database Systems</title>
		<identifier type="sharef:uri" resourceType="text/html">http://www.informatik.uni-trier.de/~ley/db/conf/pods/pods82.html</identifier>
	</reference>
	<reference name="nev98" src="bibtex:inproceedings" src-info="bibtex:line-10961" type="sharef:inproceedings" crossref="pods98">
		<names type="sharef:author">
			<person>
				<givenname>Frank</givenname>
				<surname>Neven</surname>
			</person>
			<person>
				<givenname>Jan</givenname>
				<surname>Van den Bussche</surname>
			</person>
		</names>
		<identifier type="sharef:doi">10.1145/275487.275489</identifier>
		<field type="bibtex:index">xml[0.8]</field>
		<pages>11-17</pages>
		<title type="sharef:primaryTitle">Expressiveness of Structured Document Query Languages Based on Attribute Grammars</title>
	</reference>
	<reference name="pods98" src="bibtex:proceedings" src-info="bibtex:line-10970" type="sharef:proceedings">
		<date value="1998-06"/>
		<address type="sharef:placePublished">Seattle, Washington</address>
		<field type="bibtex:index">PODS '98</field>
		<identifier type="sharef:isbn">0897919963</identifier>
		<publisher>ACM Press</publisher>
		<title type="sharef:primaryTitle">Seventeenth ACM SIGACT-SIGMOD-SIGART Symposium on Principles of Database Systems</title>
		<identifier type="sharef:uri" resourceType="text/html">http://www.informatik.uni-trier.de/~ley/db/conf/pods/pods98.html</identifier>
	</reference>
	<reference name="via01" src="bibtex:inproceedings" src-info="bibtex:line-10986" type="sharef:inproceedings" crossref="pods01">
		<names type="sharef:author">
			<person>
				<givenname>Victor</givenname>
				<surname>Vianu</surname>
			</person>
		</names>
		<identifier type="sharef:doi">10.1145/375551.375554</identifier>
		<field type="bibtex:index">xml[0.9]</field>
		<pages>1-15</pages>
		<title type="sharef:primaryTitle">A Web Odyssey: From Codd to XML</title>
	</reference>
	<reference name="pods01" src="bibtex:proceedings" src-info="bibtex:line-10995" type="sharef:proceedings">
		<date value="2001-05"/>
		<address type="sharef:placePublished">Santa Barbara, California</address>
		<field type="bibtex:index">PODS 2001</field>
		<identifier type="sharef:isbn">1581133618</identifier>
		<publisher>ACM Press</publisher>
		<title type="sharef:primaryTitle">Twentieth ACM SIGACT-SIGMOD-SIGART Symposium on Principles of Database Systems</title>
		<identifier type="sharef:uri" resourceType="text/html">http://www.informatik.uni-trier.de/~ley/db/conf/pods/pods2001.html</identifier>
	</reference>
	<reference name="bab02" src="bibtex:inproceedings" src-info="bibtex:line-11011" type="sharef:inproceedings" crossref="pods02">
		<names type="sharef:author">
			<person>
				<givenname>Brian</givenname>
				<surname>Babcock</surname>
			</person>
			<person>
				<givenname>Shivnath</givenname>
				<surname>Babu</surname>
			</person>
			<person>
				<givenname>Mayur</givenname>
				<surname>Datar</surname>
			</person>
			<person>
				<givenname>Rajeev</givenname>
				<surname>Motwani</surname>
			</person>
			<person>
				<givenname>Jennifer</givenname>
				<surname>Widom</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>In this overview paper we motivate the need for and research issues arising from a new model of data processing. In this model, data does not take the form of persistent relations, but rather arrives in multiple, continuous, rapid, time-varying data streams. In addition to reviewing past work relevant to data stream systems and current projects in the area, the paper explores topics in stream query languages, new requirements and challenges in query processing, and algorithmic issues.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/543613.543615</identifier>
		<pages>1-16</pages>
		<title type="sharef:primaryTitle">Models and Issues in Data Stream Systems</title>
	</reference>
	<reference name="pods02" src="bibtex:proceedings" src-info="bibtex:line-11020" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>Lucian</givenname>
				<surname>Popa</surname>
			</person>
		</names>
		<date value="2002-06"/>
		<address type="sharef:placePublished">Madison, Wisconsin</address>
		<field type="bibtex:index">PODS 2002</field>
		<publisher>ACM Press</publisher>
		<title type="sharef:primaryTitle">Twenty-first ACM SIGACT-SIGMOD-SIGART Symposium on Principles of Database Systems</title>
		<identifier type="sharef:uri" resourceType="text/html">http://www.informatik.uni-trier.de/~ley/db/conf/pods/pods02.html</identifier>
	</reference>
	<reference name="hal06b" src="bibtex:inproceedings" src-info="bibtex:line-11036" type="sharef:inproceedings" crossref="pods06">
		<names type="sharef:author">
			<person>
				<givenname>Alon Y.</givenname>
				<surname>Halevy</surname>
			</person>
			<person>
				<givenname>Michael J.</givenname>
				<surname>Franklin</surname>
			</person>
			<person>
				<givenname>David</givenname>
				<surname>Maier</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>The most acute information management challenges today stem from organizations relying on a large number of diverse, interrelated data sources, but having no means of managing them in a convenient, integrated, or principled fashion. These challenges arise in enterprise and government data management, digital libraries, "smart" homes and personal information management. We have proposed dataspaces as a data management abstraction for these diverse applications and DataSpace Support Platforms (DSSPs) as systems that should be built to provide the required services over dataspaces. Unlike data integration systems, DSSPs do not require full semantic integration of the sources in order to provide useful services. This paper lays out specific technical challenges to realizing DSSPs and ties them to existing work in our field. We focus on query answering in DSSPs, the DSSP's ability to introspect on its content, and the use of human attention to enhance the semantic relationships in a dataspace.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/1142351.1142352</identifier>
		<pages>1-9</pages>
		<title type="sharef:primaryTitle">Principles of Dataspace Systems</title>
	</reference>
	<reference name="mei06" src="bibtex:inproceedings" src-info="bibtex:line-11045" type="sharef:inproceedings" crossref="pods06">
		<names type="sharef:author">
			<person>
				<givenname>Erik</givenname>
				<surname>Meijer</surname>
			</person>
			<person>
				<givenname>Brian</givenname>
				<surname>Beckman</surname>
			</person>
			<person>
				<givenname>Gavin</givenname>
				<surname>Bierman</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Many software applications today need to handle data from different data models; typically objects from the host programming language along with the relational and XML data models. The ROX impedance mismatch makes programs awkward to write and hard to maintain. The .NET Language-Integrated Query (LINQ) framework, proposed for the next release of the .NET framework, approaches this problem by defining a pattern of general-purpose standard query operators for traversal, filter, and projection. Based on this pattern, any .NET language can define special query comprehension syntax that is subsequently compiled into these standard operators (our code examples are in VB). Besides the general query operators, the LINQ framework also defines two domain specific APIs that work over XML (XLinq) and relational data (DLinq) respectively. The operators over XML use a lightweight and easy to use in-memory XML representation to provide XQuery-style expressiveness in the host programming language. The operators over relational data provide a simple OR mapping by leveraging remotable queries that are executed directly in the back-end relational store.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/1142473.1142552</identifier>
		<pages>706</pages>
		<title type="sharef:primaryTitle">LINQ: Reconciling Object, Relations and XML in the .NET Framework</title>
		<field type="bibtex:topic">linq[0.9]</field>
	</reference>
	<reference name="pods06" src="bibtex:proceedings" src-info="bibtex:line-11055" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>Stijn</givenname>
				<surname>Vansummeren</surname>
			</person>
		</names>
		<date value="2006-06"/>
		<address type="sharef:placePublished">Chicago, Illinois</address>
		<field type="bibtex:index">PODS 2006</field>
		<identifier type="sharef:isbn">1-59593-318-2</identifier>
		<publisher>ACM Press</publisher>
		<title type="sharef:primaryTitle">Twenty-Fifth ACM SIGACT-SIGMOD-SIGART Symposium on Principles of Database Systems (PODS 2006)</title>
		<identifier type="sharef:uri" resourceType="text/html">http://www.informatik.uni-trier.de/~ley/db/conf/pods/pods2006.html</identifier>
	</reference>
	<reference name="abi09" src="bibtex:inproceedings" src-info="bibtex:line-11072" type="sharef:inproceedings" crossref="pods09">
		<names type="sharef:author">
			<person>
				<givenname>Serge</givenname>
				<surname>Abiteboul</surname>
			</person>
			<person>
				<givenname>Georg</givenname>
				<surname>Gottlob</surname>
			</person>
			<person>
				<givenname>Marco</givenname>
				<surname>Manna</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>A distributed XML document is an XML document that spans several machines or Web repositories. We assume that a distribution design of the document tree is given, providing an XML tree some of whose leaves are "docking points", to which XML subtrees can be attached. These subtrees may be provided and controlled by peers at remote locations, or may correspond to the result of function calls, e.g., Web services. If a global type t, e.g. a DTD, is specified for a distributed document T, it would be most desirable to be able to break this type into a collection of local types, called a local typing, such that the document satisfies t if and only if each peer (or function) satisfies its local type. In this paper we lay out the fundamentals of a theory of local typing and provide formal definitions of three main variants of locality: local typing, maximal local typing, and perfect typing, the latter being the most desirable. We study the following relevant decision problems: (i) given a typing for a design, determine whether it is local, maximal local, or perfect; (ii) given a design, establish whether a (maximal) local, or perfect typing does exist. For some of these problems we provide tight complexity bounds (polynomial space), while for the others we show exponential upper bounds. A main contribution is a polynomial-space algorithm for computing a perfect typing in this context, if it exists.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/1559795.1559833</identifier>
		<pages>247-258</pages>
		<title type="sharef:primaryTitle">Distributed XML Design</title>
		<field type="bibtex:topic">xml[0.8]</field>
	</reference>
	<reference name="pods09" src="bibtex:proceedings" src-info="bibtex:line-11082" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>Jan</givenname>
				<surname>Paredaens</surname>
			</person>
			<person>
				<givenname>Jianwen</givenname>
				<surname>Su</surname>
			</person>
		</names>
		<date value="2009-06"/>
		<address type="sharef:placePublished">Providence, Rhode Island</address>
		<field type="bibtex:index">PODS 2009</field>
		<identifier type="sharef:isbn">978-1-60558-553-6</identifier>
		<publisher>ACM Press</publisher>
		<title type="sharef:primaryTitle">Twenty-Eigth ACM SIGACT-SIGMOD-SIGART Symposium on Principles of Database Systems (PODS 2009)</title>
		<identifier type="sharef:uri" resourceType="text/html">http://www.informatik.uni-trier.de/~ley/db/conf/pods/pods2009.html</identifier>
	</reference>
	<reference name="dul07" src="bibtex:inproceedings" src-info="bibtex:line-11099" type="sharef:inproceedings" crossref="sigmod07">
		<names type="sharef:author">
			<person>
				<givenname>Michael</givenname>
				<surname>Duller</surname>
			</person>
			<person>
				<givenname>Rokas</givenname>
				<surname>Tamosevicius</surname>
			</person>
			<person>
				<givenname>Gustavo</givenname>
				<surname>Alonso</surname>
			</person>
			<person>
				<givenname>Donald</givenname>
				<surname>Kossmann</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>The real usability of data stream systems depends on the practical aspect of building applications on data streams. In this demo we show two possible applications on data streams implemented on our prototype platform XTream. One application integrates VoIP and E-Mail, the other one incorporates streams in a Smart Home setting. Using these applications we try to identify and discuss the functionality that data stream management systems should provide. Those attending the demo will be able to compose their own applications.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/1247480.1247616</identifier>
		<pages>1088-1090</pages>
		<title type="sharef:primaryTitle">XTream: Personal Data Streams</title>
	</reference>
	<reference name="enn07" src="bibtex:inproceedings" src-info="bibtex:line-11108" type="sharef:inproceedings" crossref="sigmod07">
		<names type="sharef:author">
			<person>
				<givenname>Robert J.</givenname>
				<surname>Ennals</surname>
			</person>
			<person>
				<givenname>Minos N.</givenname>
				<surname>Garofalakis</surname>
			</person>
		</names>
		<identifier type="sharef:doi">10.1145/1247480.1247626</identifier>
		<pages>1116-1118</pages>
		<title type="sharef:primaryTitle">MashMaker: Mashups for the Masses</title>
	</reference>
	<reference name="sigmod07" src="bibtex:proceedings" src-info="bibtex:line-11116" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>Chee Yong</givenname>
				<surname>Chan</surname>
			</person>
			<person>
				<givenname>Beng Chin</givenname>
				<surname>Ooi</surname>
			</person>
			<person>
				<givenname>Aoying</givenname>
				<surname>Zhou</surname>
			</person>
		</names>
		<date value="2007-06"/>
		<address type="sharef:placePublished">Beijing, China</address>
		<field type="bibtex:index">SIGMOD 2007</field>
		<identifier type="sharef:isbn">978-1-59593-686-8</identifier>
		<publisher>ACM Press</publisher>
		<title type="sharef:primaryTitle">2007 ACM SIGMOD International Conference on Management of Data</title>
		<identifier type="sharef:uri" resourceType="text/html">http://www.informatik.uni-trier.de/~ley/db/conf/sigmod/sigmod2007.html</identifier>
	</reference>
	<reference name="sim08" src="bibtex:inproceedings" src-info="bibtex:line-11133" type="sharef:inproceedings" crossref="sigmod08">
		<names type="sharef:author">
			<person>
				<givenname>David E.</givenname>
				<surname>Simmen</surname>
			</person>
			<person>
				<givenname>Mehmet</givenname>
				<surname>Altinel</surname>
			</person>
			<person>
				<givenname>Volker</givenname>
				<surname>Markl</surname>
			</person>
			<person>
				<givenname>Sriram</givenname>
				<surname>Padmanabhan</surname>
			</person>
			<person>
				<givenname>Ashutosh</givenname>
				<surname>Singh</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Increasingly large numbers of situational applications are being created by enterprise business users as a by-product of solving day-to-day problems. In efforts to address the demand for such applications, corporate IT is moving toward Web 2.0 architectures. In particular, the corporate intranet is evolving into a platform of readily accessible data and services where communities of business users can assemble and deploy situational applications. Damia is a web style data integration platform being developed to address the data problem presented by such applications, which often access and combine data from a variety of sources. Damia allows business users to quickly and easily create data mashups that combine data from desktop, web, and traditional IT sources into feeds that can be consumed by AJAX, and other types of web applications. This paper describes the key features and design of Damia's data integration engine, which has been packaged with Mashup Hub, an enterprise feed server currently available for download on IBM alphaWorks. Mashup Hub exposes Damia's data integration capabilities in the form of a service that allows users to create hosted data mashups.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/1376616.1376734</identifier>
		<pages>1171-1182</pages>
		<title type="sharef:primaryTitle">Damia: Data Mashups for Intranet Applications</title>
	</reference>
	<reference name="fou08" src="bibtex:inproceedings" src-info="bibtex:line-11142" type="sharef:inproceedings" crossref="sigmod08">
		<names type="sharef:author">
			<person>
				<givenname>Ghislain</givenname>
				<surname>Fourny</surname>
			</person>
			<person>
				<givenname>Donald</givenname>
				<surname>Kossmann</surname>
			</person>
			<person>
				<givenname>Tim</givenname>
				<surname>Kraska</surname>
			</person>
			<person>
				<givenname>Markus</givenname>
				<surname>Pilman</surname>
			</person>
			<person>
				<givenname>Daniela</givenname>
				<surname>Florescu</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Over the years, the browser has become a complete runtime environment for client-side programs. The main scripting language used towards this purpose is JavaScript, which was designed so as to program the browser. A lot of extensions and new layers have been built on top of it to allow e.g. DOM navigation and manipulation. However, JavaScript has become a victim of its own success and is used way beyond its possibilities, leading to increased code complexity. We suggest to reduce programming complexity by proposing XQuery as a client-side programming language. We wrote an extension for Microsoft Internet Explorer, based on the Zorba XQuery engine, which allows execution of XQuery scripts in the browser. An extension for Firefox is on the way as well. This paper demonstrates how client-side applications in XQuery look like and what they can do within a very small amount of code.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/1376616.1376769</identifier>
		<pages>1337-1340</pages>
		<title type="sharef:primaryTitle">XQuery in the Browser</title>
	</reference>
	<reference name="sigmod08" src="bibtex:proceedings" src-info="bibtex:line-11151" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>Jason Tsong-Li</givenname>
				<surname>Wang</surname>
			</person>
		</names>
		<date value="2008-06"/>
		<address type="sharef:placePublished">Vancouver, Canada</address>
		<field type="bibtex:index">SIGMOD 2008</field>
		<identifier type="sharef:isbn">978-1-60558-102-6</identifier>
		<publisher>ACM Press</publisher>
		<title type="sharef:primaryTitle">2008 ACM SIGMOD International Conference on Management of Data</title>
		<identifier type="sharef:uri" resourceType="text/html">http://www.informatik.uni-trier.de/~ley/db/conf/sigmod/sigmod2008.html</identifier>
	</reference>
	<reference name="cha08" src="bibtex:inproceedings" src-info="bibtex:line-11168" type="sharef:inproceedings" crossref="sigkdd08">
		<names type="sharef:author">
			<person>
				<givenname>Deepayan</givenname>
				<surname>Chakrabarti</surname>
			</person>
			<person>
				<givenname>Ravi</givenname>
				<surname>Kumar</surname>
			</person>
			<person>
				<givenname>Kunal</givenname>
				<surname>Punera</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>How can a search engine automatically provide the best and most appropriate title for a result URL (link-title) so that users will be persuaded to click on the URL? We consider the problem of automatically generating link-titles for URLs and propose a general statistical framework for solving this problem. The framework is based on using information from a diverse collection of sources, each of which can be thought of as contributing one or more candidate link-titles for the URL. It can also incorporate the context in which the link-title will be used, along with constraints on its length. Our framework is applicable to several scenarios: obtaining succinct titles for displaying quicklinks, obtaining titles for URLs that lack a good title, constructing succinct sitemaps, etc. Extensive experiments show that our method is very effective, producing results that are at least 20% better than non-trivial baselines.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/1401890.1401905</identifier>
		<pages>79-87</pages>
		<title type="sharef:primaryTitle">Generating Succinct Titles for Web URLs</title>
	</reference>
	<reference name="sigkdd08" src="bibtex:proceedings" src-info="bibtex:line-11177" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>Ying</givenname>
				<surname>Li</surname>
			</person>
			<person>
				<givenname>Bing</givenname>
				<surname>Liu</surname>
			</person>
			<person>
				<givenname>Sunita</givenname>
				<surname>Sarawagi</surname>
			</person>
		</names>
		<date value="2008-08"/>
		<address type="sharef:placePublished">Las Vegas, Nevada</address>
		<field type="bibtex:index">SIGKDD 2008</field>
		<identifier type="sharef:isbn">978-1-60558-193-4</identifier>
		<publisher>ACM Press</publisher>
		<title type="sharef:primaryTitle">14th ACM SIGKDD International Conference on Knowledge Discovery and Data Mining</title>
		<identifier type="sharef:uri" resourceType="text/html">http://www.informatik.uni-trier.de/~ley/db/conf/kdd/kdd2008.html</identifier>
	</reference>
	<reference name="fuj04" src="bibtex:inproceedings" src-info="bibtex:line-11194" type="sharef:inproceedings" crossref="dagstuhl04">
		<names type="sharef:author">
			<person>
				<givenname>Jun</givenname>
				<surname>Fujima</surname>
			</person>
			<person>
				<givenname>Yuzuru</givenname>
				<surname>Tanaka</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>This paper proposes a new framework for organizing and accessing Web resources using loci defined on arbitrary Web documents. Our framework allows users to store Web resources in user-specified loci on a Web document to define a relation among them. This relation is retained as a set of tuples in a table called a Topica table. When users access such a locus, the resources associated with this locus are presented on the display screen. Each locus is associated with an attribute of the Topica table associated with this document. Our framework enables users to dynamically define such loci, called topoi, on arbitrary Web documents, and to input and/or output tuples of Web resources to and from a set of topoi defined on each of these Web documents. In addition, we propose a mechanism to access multiple related resources using a history of users' navigation through such documents.</p>
			</richtext>
		</abstract>
		<pages>88-98</pages>
		<title type="sharef:primaryTitle">Accessing Related Web Resources Through Annotated Documents</title>
	</reference>
	<reference name="dagstuhl04" src="bibtex:proceedings" src-info="bibtex:line-11202" type="sharef:proceedings">
		<date value="2004-03"/>
		<address type="sharef:placePublished">Dagstuhl, Germany</address>
		<identifier type="sharef:doi">10.1007/b104697</identifier>
		<identifier type="sharef:isbn">978-3-540-24465-3</identifier>
		<publisher>Springer-Verlag</publisher>
		<title type="sharef:seriesTitle">Lecture Notes in Computer Science</title>
		<title type="sharef:primaryTitle">Intuitive Human Interfaces for Organizing and Accessing Intellectual Assets</title>
		<identifier type="sharef:uri">http://springerlink.metapress.com/content/tnb9ngrgame2/</identifier>
		<volume>3359</volume>
	</reference>
	<reference name="fut06" src="bibtex:inproceedings" src-info="bibtex:line-11220" type="sharef:inproceedings" crossref="ipaw2006">
		<names type="sharef:author">
			<person>
				<givenname>Joe</givenname>
				<surname>Futrelle</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Managing scientific data requires tools that can track complex provenance information about digital resources and workflows. RDF triples are a convenient abstraction for combining independently-generated factual statements, including statements about provenance. Harvesting is a strategy for asynchronously acquiring distributed information for the purposes of aggregation and analysis. Harvesting typically requires that information be temporally scoped and attributed to some creator or information source. An RDF triple asserts a fact without attributing it to any actor or period of time, so the abstraction must be extended to support typical harvesting scenarios. This paper compares standard, conventional, and non-standard means of extending RDF triples to associate them with attribution and timing information. Then, it considers the implications of these techniques for harvesting and presents some implementation sketches based on a journaling strategy.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1007/11890850_8</identifier>
		<pages>64-72</pages>
		<title type="sharef:primaryTitle">Harvesting RDF Triples</title>
		<field type="bibtex:topic">rdf[0.8]</field>
		<identifier type="sharef:uri">http://www.springerlink.com/content/p0m5145723737855/</identifier>
	</reference>
	<reference name="ipaw2006" src="bibtex:proceedings" src-info="bibtex:line-11231" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>Luc</givenname>
				<surname>Moreau</surname>
			</person>
			<person>
				<givenname>Ian</givenname>
				<surname>Foster</surname>
			</person>
		</names>
		<date value="2006-05"/>
		<address type="sharef:placePublished">Chicago, Illinois</address>
		<identifier type="sharef:doi">10.1007/11890850</identifier>
		<identifier type="sharef:isbn">978-3-540-46302-3</identifier>
		<publisher>Springer-Verlag</publisher>
		<title type="sharef:seriesTitle">Lecture Notes in Computer Science</title>
		<title type="sharef:primaryTitle">International Provenance and Annotation Workshop (IPAW 2006)</title>
		<identifier type="sharef:uri">http://www.springerlink.com/content/q77362133660</identifier>
		<volume>4145</volume>
	</reference>
	<reference name="her01" src="bibtex:inproceedings" src-info="bibtex:line-11250" type="sharef:inproceedings" crossref="sigmod01">
		<names type="sharef:author">
			<person>
				<givenname>Mauricio A.</givenname>
				<surname>Hernández</surname>
			</person>
			<person>
				<givenname>René J.</givenname>
				<surname>Miller</surname>
			</person>
			<person>
				<givenname>Laura M.</givenname>
				<surname>Haas</surname>
			</person>
		</names>
		<identifier type="sharef:doi">10.1145/375663.375767</identifier>
		<field type="bibtex:index">clio[1]</field>
		<pages>607</pages>
		<title type="sharef:primaryTitle">Clio: A Semi-Automatic Tool for Schema Mapping</title>
	</reference>
	<reference name="sigmod01" src="bibtex:proceedings" src-info="bibtex:line-11259" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>Walid G.</givenname>
				<surname>Aref</surname>
			</person>
		</names>
		<date value="2001-05"/>
		<address type="sharef:placePublished">Santa Barbara, California</address>
		<field type="bibtex:index">SIGMOD 2001</field>
		<publisher>ACM Press</publisher>
		<title type="sharef:primaryTitle">2001 ACM SIGMOD International Conference on Management of Data</title>
		<identifier type="sharef:uri" resourceType="text/html">http://www.informatik.uni-trier.de/~ley/db/conf/sigmod/sigmod2001.html</identifier>
		<identifier type="sharef:uri">http://www.sigmod.org/sigmod01/eproceedings/</identifier>
	</reference>
	<reference name="haa04a" src="bibtex:inproceedings" src-info="bibtex:line-11276" type="sharef:inproceedings" crossref="icsnw04">
		<names type="sharef:author">
			<person>
				<givenname>Peter</givenname>
				<surname>Haase</surname>
			</person>
			<person>
				<givenname>Ronny</givenname>
				<surname>Siebes</surname>
			</person>
			<person>
				<givenname>Frank</givenname>
				<surname link="van">Harmelen</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Peer-to-Peer systems have proven to be an effective way of sharing data. Modern protocols are able to efficiently route a message to a given peer. However, determining the destination peer in the first place is not always trivial. We propose a model in which peers advertise their expertise in the Peer-to-Peer network. The knowledge about the expertise of other peers forms a semantic topology. Based on the semantic similarity between the subject of a query and the expertise of other peers, a peer can select appropriate peers to forward queries to, instead of broadcasting the query or sending it to a random set of peers. To calculate our semantic similarity measure we make the simplifying assumption that the peers share the same ontology. We evaluate the model in a bibliographic scenario, where peers share bibliographic descriptions of publications among each other. In simulation experiments we show how expertise based peer selection improves the performance of a Peer-to-Peer system with respect to precision, recall and the number of messages.</p>
			</richtext>
		</abstract>
		<field type="bibtex:index">bibster[0.9]</field>
		<title type="sharef:primaryTitle">Peer Selection in Peer-to-Peer Networks with Semantic Topologies</title>
		<identifier type="sharef:uri" resourceType="text/html">http://www.cs.vu.nl/~frankh/abstracts/ICSNW04.html</identifier>
		<identifier type="sharef:uri" resourceType="application/pdf">http://bibster.semanticweb.org/publications/haase_04_peer.pdf</identifier>
	</reference>
	<reference name="icsnw04" src="bibtex:proceedings" src-info="bibtex:line-11286" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>Mokrane</givenname>
				<surname>Bouzeghoub</surname>
			</person>
		</names>
		<date value="2004-06"/>
		<address type="sharef:placePublished">Paris, France</address>
		<field type="bibtex:index">IC-SNW 2004</field>
		<publisher>ACM Press</publisher>
		<title type="sharef:primaryTitle">International Conference on Semantics of a Networked World: Semantics for Grid Databases</title>
		<identifier type="sharef:uri">http://www.prism.uvsq.fr/communication/conferences/2004/IC-SNW/</identifier>
	</reference>
	<reference name="lai91" src="bibtex:inproceedings" src-info="bibtex:line-11302" type="sharef:inproceedings" crossref="ecrypt91">
		<names type="sharef:author">
			<person>
				<givenname>Xuejia</givenname>
				<surname>Lai</surname>
			</person>
			<person>
				<givenname>James L.</givenname>
				<surname>Massey</surname>
			</person>
		</names>
		<field type="bibtex:index">IDEA</field>
		<pages>17-38</pages>
		<title type="sharef:primaryTitle">Markov ciphers and differential cryptanalysis</title>
	</reference>
	<reference name="ecrypt91" src="bibtex:proceedings" src-info="bibtex:line-11310" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>D. W.</givenname>
				<surname>Davies</surname>
			</person>
		</names>
		<date value="1991-04"/>
		<address type="sharef:placePublished">Brighton, UK</address>
		<field type="bibtex:index">EUROCRYPT '91</field>
		<identifier type="sharef:isbn">3540546200</identifier>
		<publisher>Springer-Verlag</publisher>
		<title type="sharef:seriesTitle">Lecture Notes in Computer Science</title>
		<title type="sharef:primaryTitle">EUROCRYPT '91 — Advances in cryptology</title>
		<volume>547</volume>
	</reference>
	<reference name="tsi96" src="bibtex:inproceedings" src-info="bibtex:line-11328" type="sharef:inproceedings" crossref="mos96">
		<names type="sharef:author">
			<person>
				<givenname>D.</givenname>
				<surname>Tsichritzis</surname>
			</person>
		</names>
		<field type="bibtex:index">Objectworld, Kno</field>
		<pages>7-24</pages>
		<title type="sharef:primaryTitle">Objectworld</title>
	</reference>
	<reference name="che96" src="bibtex:inproceedings" src-info="bibtex:line-11336" type="sharef:inproceedings" crossref="mos96">
		<names type="sharef:author">
			<person>
				<givenname>David</givenname>
				<surname>Chess</surname>
			</person>
			<person>
				<givenname>Colin</givenname>
				<surname>Harrison</surname>
			</person>
			<person>
				<givenname>Aaron</givenname>
				<surname>Kershenbaum</surname>
			</person>
		</names>
		<field type="bibtex:index">mobile agents</field>
		<pages>25-47</pages>
		<title type="sharef:primaryTitle">Mobile Agents: Are They a Good Idea?</title>
	</reference>
	<reference name="vit96" src="bibtex:inproceedings" src-info="bibtex:line-11344" type="sharef:inproceedings" crossref="mos96">
		<names type="sharef:author">
			<person>
				<givenname>Jan</givenname>
				<surname>Vitek</surname>
			</person>
			<person>
				<givenname>Manuel</givenname>
				<surname>Serrano</surname>
			</person>
			<person>
				<givenname>Dimitri</givenname>
				<surname>Thanos</surname>
			</person>
		</names>
		<field type="bibtex:index">Security, Java, Octopus, Capsules, sealed objects</field>
		<pages>177-199</pages>
		<title type="sharef:primaryTitle">Security and Communication in Mobile Object Systems</title>
	</reference>
	<reference name="kat96" src="bibtex:inproceedings" src-info="bibtex:line-11352" type="sharef:inproceedings" crossref="mos96">
		<names type="sharef:author">
			<person>
				<givenname>Kazuhiko</givenname>
				<surname>Kato</surname>
			</person>
		</names>
		<field type="bibtex:index">Emerald, Java, Safe-Tcl, SFI, PCC, Planet</field>
		<pages>201-211</pages>
		<title type="sharef:primaryTitle">Safe and Secure Execution Mechanisms for Mobile Objects</title>
	</reference>
	<reference name="mos96" src="bibtex:proceedings" src-info="bibtex:line-11360" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>Jan</givenname>
				<surname>Vitek</surname>
			</person>
			<person>
				<givenname>Christian</givenname>
				<surname>Tschudin</surname>
			</person>
		</names>
		<date value="1996-07"/>
		<address type="sharef:placePublished">Linz, Austria</address>
		<field type="bibtex:index">MOS '96</field>
		<publisher>Springer-Verlag</publisher>
		<title type="sharef:seriesTitle">Lecture Notes in Computer Science</title>
		<title type="sharef:primaryTitle">Second International Workshop on Mobile Object Systems</title>
		<volume>1222</volume>
	</reference>
	<reference name="dur96" src="bibtex:inproceedings" src-info="bibtex:line-11377" type="sharef:inproceedings" crossref="treds96">
		<names type="sharef:author">
			<person>
				<givenname>M. Khayrat</givenname>
				<surname>Durmosch</surname>
			</person>
			<person>
				<givenname>Christian</givenname>
				<surname>Egelhaaf</surname>
			</person>
			<person>
				<givenname>Klaus-Dietrich</givenname>
				<surname>Engel</surname>
			</person>
			<person>
				<givenname>Peter</givenname>
				<surname>Schoo</surname>
			</person>
		</names>
		<field type="bibtex:index">TANGRAM</field>
		<pages>108-121</pages>
		<title type="sharef:primaryTitle">Design and Implementation of a Multimedia Communication Service in a Distributed Environment based on the TINA-C Architecture</title>
	</reference>
	<reference name="treds96" src="bibtex:proceedings" src-info="bibtex:line-11385" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>Otto</givenname>
				<surname>Spaniol</surname>
			</person>
			<person>
				<givenname>C.</givenname>
				<surname>Linnhoff-Popien</surname>
			</person>
			<person>
				<givenname>B.</givenname>
				<surname>Meyer</surname>
			</person>
		</names>
		<date value="1996-10"/>
		<address type="sharef:placePublished">Aachen, Germany</address>
		<field type="bibtex:index">TREDS '96</field>
		<publisher>Springer-Verlag</publisher>
		<title type="sharef:seriesTitle">Lecture Notes in Computer Science</title>
		<title type="sharef:primaryTitle">Conference on Trends in Distributed Systems — CORBA and Beyond</title>
		<volume>1161</volume>
	</reference>
	<reference name="wea95" src="bibtex:inproceedings" src-info="bibtex:line-11402" type="sharef:inproceedings" crossref="wfcs95">
		<names type="sharef:author">
			<person>
				<givenname>Alfred C.</givenname>
				<surname>Weaver</surname>
			</person>
		</names>
		<field type="bibtex:index">XTP</field>
		<title type="sharef:primaryTitle">Xpress Transport Protocol Version 4</title>
	</reference>
	<reference name="wfcs95" src="bibtex:proceedings" src-info="bibtex:line-11409" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>J.-D.</givenname>
				<surname>Decotignie</surname>
			</person>
		</names>
		<date value="1995-10"/>
		<address type="sharef:placePublished">Leysin, Switzerland</address>
		<field type="bibtex:index">WFCS '95</field>
		<title type="sharef:primaryTitle">IEEE International Workshop on Factory Communication Systems</title>
	</reference>
	<reference name="wil96b" src="bibtex:inproceedings" src-info="bibtex:line-11423" type="sharef:inproceedings" crossref="ecmast96">
		<names type="sharef:author">
			<person>
				<givenname>Erik</givenname>
				<surname>Wilde</surname>
			</person>
			<person>
				<givenname>Murali</givenname>
				<surname>Nanduri</surname>
			</person>
			<person>
				<givenname>Bernhard</givenname>
				<surname>Plattner</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Group communications is an area of research which has received a lot of attention recently. This paper focuses on a model and the architecture of a system which supports group communications by providing group and session management functionality. This system is an extension of directory services which are used with unicast communications. New functionality is needed for the dynamics of group communications (members of a connection may change over the lifetime of the connection) and increased complexity of relations. A model is described which defines six object types which represent the relevant objects. Users and groups represent real world users and their relations. Sessions and flows describe ongoing group communications. Flow templates and certificates provide mechanisms for management and security issues. The architecture presented in this paper is transport-independent, ie it can be used within different group communication platforms. A short sketch of the implementation is given in the last section.</p>
			</richtext>
		</abstract>
		<field type="bibtex:index">GMS, GUA, GAP</field>
		<pages>409-425</pages>
		<title type="sharef:primaryTitle">A Transport-Independent Component for a Group and Session Management Service in Group Communications Platforms</title>
		<identifier type="sharef:uri">http://dret.net/netdret/publications#wil96b</identifier>
	</reference>
	<reference name="ecmast96" src="bibtex:proceedings" src-info="bibtex:line-11433" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>Paul</givenname>
				<surname>Delogne</surname>
			</person>
			<person>
				<givenname>David</givenname>
				<surname>Hutchison</surname>
			</person>
			<person>
				<givenname>Benoît</givenname>
				<surname>Macq</surname>
			</person>
			<person>
				<givenname>Jean-Jacques</givenname>
				<surname>Quisquater</surname>
			</person>
		</names>
		<date value="1996-05"/>
		<address type="sharef:placePublished">Louvain-la-Neuve, Belgium</address>
		<field type="bibtex:index">ECMAST '96</field>
		<title type="sharef:primaryTitle">European Conference on Multimedia Applications, Services and Techniques</title>
	</reference>
	<reference name="bau96" src="bibtex:inproceedings" src-info="bibtex:line-11447" type="sharef:inproceedings" crossref="lcn96">
		<names type="sharef:author">
			<person>
				<givenname>Daniel</givenname>
				<surname>Bauer</surname>
			</person>
			<person>
				<givenname>Burkhard</givenname>
				<surname>Stiller</surname>
			</person>
			<person>
				<givenname>Bernhard</givenname>
				<surname>Plattner</surname>
			</person>
		</names>
		<field type="bibtex:index">MCF</field>
		<pages>212-221</pages>
		<title type="sharef:primaryTitle">An Error-Control Scheme for a Multicast Protocol Based on Round-Trip Time Calculations</title>
	</reference>
	<reference name="lcn96" src="bibtex:proceedings" src-info="bibtex:line-11455" type="sharef:proceedings">
		<date value="1996-10"/>
		<address type="sharef:placePublished">Minneapolis, Minnesota</address>
		<field type="bibtex:index">LCN '96</field>
		<identifier type="sharef:isbn">0818676175</identifier>
		<field type="bibtex:key">21st IEEE Conference on Local Computer Networks</field>
		<publisher>IEEE Computer Society Press</publisher>
		<title type="sharef:primaryTitle">21st IEEE Conference on Local Computer Networks</title>
	</reference>
	<reference name="kaw07" src="bibtex:inproceedings" src-info="bibtex:line-11471" type="sharef:inproceedings" crossref="inss07">
		<names type="sharef:author">
			<person>
				<givenname>Hideyuki</givenname>
				<surname>Kawashima</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>The applications of ubiquitous sensor networks require database system to support the following three functions in addition with conventional database functions. (1) continual event monitoring. Since control systems such as robots perform accurately, event monitoring must be executed in strict real-time. (2) signal processing. To recognize events in the physical world, sensor data must be processed by non traditional way such as similar sequence retrievals. (3) fast signal stream persisting. All of sensor data should be stored to consider the reason of illegal events after accidents or offline data mining. To support the requirements, we propose a new database system KRAFT. To realize (1), KRAFT controls user-level threads on FreeBSD KSE scheduler. To realize (2), KRAFT provides similar sequence retrieval operators. The operators' distance functions are Euclidean and dynamic time warping. To realize (3), KRAFT provides direct persisting, which does not execute the write ahead logging process. We describe preliminary results of experiments and show the performance of KRAFT.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1109/INSS.2007.4297414</identifier>
		<pages>163-166</pages>
		<title type="sharef:primaryTitle">KRAFT: A Real-Time Active DBMS for Signal Streams</title>
		<field type="bibtex:topic">kraft[1]</field>
	</reference>
	<reference name="inss07" src="bibtex:proceedings" src-info="bibtex:line-11481" type="sharef:proceedings">
		<date value="2007-06"/>
		<address type="sharef:placePublished">Piscataway, New Jersey</address>
		<field type="bibtex:index">INSS 2007</field>
		<field type="bibtex:key">4th International Conference on Networked Sensing Systems</field>
		<publisher>IEEE Computer Society Press</publisher>
		<title type="sharef:primaryTitle">4th International Conference on Networked Sensing Systems</title>
	</reference>
	<reference name="wil09c" src="bibtex:inproceedings" src-info="bibtex:line-11496" type="sharef:inproceedings" crossref="ipsn09">
		<names type="sharef:author">
			<person>
				<givenname>Erik</givenname>
				<surname>Wilde</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>The setup of and processing within sensor networks often requires sophisticated and specialized system designs and implementations, but the service provided by them should be as accessible and repurposable as possible. If the increasing number of available sensor-based data sources can be accessed in a simple and universal way, the network effect of aggregating, filtering, and republishing data from these sources will significantly increase their value. We propose an architecture where sensor-based data sources publish their data based on feeds, but extended with query capabilities. Using the well-known and widely supported Atom feed format and extending it with query capabilities allows us to lower the barrier-of-entry to sensor-based data sources, opening this data to a wider audience of clients.</p>
			</richtext>
		</abstract>
		<title type="sharef:primaryTitle">Making Sensor Data Available Using Web Feeds</title>
		<identifier type="sharef:uri">http://dret.net/netdret/publications#wil09c</identifier>
	</reference>
	<reference name="ipsn09" src="bibtex:proceedings" src-info="bibtex:line-11504" type="sharef:proceedings">
		<date value="2009-04"/>
		<address type="sharef:placePublished">San Francisco, California</address>
		<field type="bibtex:index">IPSN 2009</field>
		<field type="bibtex:key">8th ACM/IEEE International Conference on Information Processing in Sensor Networks</field>
		<publisher>ACM Press</publisher>
		<title type="sharef:primaryTitle">8th ACM/IEEE International Conference on Information Processing in Sensor Networks</title>
		<identifier type="sharef:uri" resourceType="text/html">http://www.informatik.uni-trier.de/~ley/db/conf/ipsn/ipsn2009.html</identifier>
	</reference>
	<reference name="kos03" src="bibtex:inproceedings" src-info="bibtex:line-11520" type="sharef:inproceedings" crossref="icme03">
		<names type="sharef:author">
			<person>
				<givenname>Ilpo</givenname>
				<surname>Koskinen</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>This paper presents evidence from two studies on the use of mobile multimedia. Mobile image has more than 1000 multimedia messages collected from a pilot in 1999-2001. Radiolinja has more than 4000 messages from a multimedia messaging (MMS) pilot in summer 2002. In Radiolinja, it was found that 32% of messages were a part of an interaction chain such as question-answer pairs, greetings, or stories. Thus, approximately 50% of traffic in the network arose from interactional needs rather than from individual, unattached messages. After the practice phase, fluctuations in use are largely explained by interactional reasons. This paper suggests that user-generated content is a key element in the success of mobile multimedia.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1109/ICME.2003.1221699</identifier>
		<pages>645-648</pages>
		<title type="sharef:primaryTitle">User-Generated Content in Mobile Multimedia: Empirical Evidence from User Studies</title>
		<identifier type="sharef:uri" resourceType="application/pdf">http://www-video.eecs.berkeley.edu/Proceedings/ICME2003/pdfs/0200645.pdf</identifier>
	</reference>
	<reference name="icme03" src="bibtex:proceedings" src-info="bibtex:line-11530" type="sharef:proceedings">
		<date value="2003-07"/>
		<address type="sharef:placePublished">Baltimore, Maryland</address>
		<field type="bibtex:index">ICME 2003</field>
		<field type="bibtex:key">2003 International Conference on Multimedia &amp; Expo</field>
		<publisher>Institute of Electrical and Electronics Engineers</publisher>
		<title type="sharef:primaryTitle">2003 International Conference on Multimedia &amp; Expo</title>
	</reference>
	<reference name="got03" src="bibtex:inproceedings" src-info="bibtex:line-11545" type="sharef:inproceedings" crossref="icde2003">
		<names type="sharef:author">
			<person>
				<givenname>Georg</givenname>
				<surname>Gottlob</surname>
			</person>
			<person>
				<givenname>Christoph</givenname>
				<surname>Koch</surname>
			</person>
			<person>
				<givenname>Reinhard</givenname>
				<surname>Pichler</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Contemporary XPath query engines evaluate queries in time exponential in the sizes of input queries, a fact that has gone unnoticed for a long time. Recently, the first main-memory evaluation algorithm for XPath 1.0 with polynomial time combined complexity, i.e., which runs in polynomial time both with respect to the size of the data and the queries, has been published. In this paper, we present several important improvements and extensions of that work, including new XPath processing algorithms with improved time and space efficiency. Moreover, we define a very large and practically relevant fragment of XPath for which a further optimized form of query evaluation is possible. Apart from its immediate relevance for XPath query processing, our work also sheds new light at those features of XPath 1.0 which are most costly relative to their practical usefulness.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1109/ICDE.2003.1260807</identifier>
		<pages>379-390</pages>
		<title type="sharef:primaryTitle">XPath Query Evaluation: Improving Time and Space Efficiency</title>
		<field type="bibtex:topic">xpath1[0.8]</field>
		<identifier type="sharef:uri" resourceType="application/pdf">http://www.dbai.tuwien.ac.at/research/xmltaskforce/icde2003.pdf</identifier>
	</reference>
	<reference name="wan03" src="bibtex:inproceedings" src-info="bibtex:line-11556" type="sharef:inproceedings" crossref="icde2003">
		<names type="sharef:author">
			<person>
				<givenname>Yuan</givenname>
				<surname>Wang</surname>
			</person>
			<person>
				<givenname>David J.</givenname>
				<surname>DeWitt</surname>
			</person>
			<person>
				<givenname>Jin</givenname>
				<surname link="yi">Cai</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>XML has become the de facto standard format for web publishing and data transportation. Since online information changes frequently, being able to quickly detect changes in XML documents is important to Internet query systems, search engines, and continuous query systems. Previous work in change detection on XML, or other hierarchically structured documents, used an ordered tree model, in which left-to-right order among siblings is important and it can affect the change result. This paper argues that an unordered model (only ancestor relationships are significant) is more suitable for most database applications. Using an unordered model, change detection is substantially harder than using the ordered model, but the change result that it generates is more accurate. This paper proposes X-Diff, an effective algorithm that integrates key XML structure characteristics with standard tree-to-tree correction techniques. The algorithm is analyzed and compared with XyDiff, a published XML diff algorithm. An experimental evaluation on both algorithms is provided.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1109/ICDE.2003.1260818</identifier>
		<pages>519-530</pages>
		<title type="sharef:primaryTitle">X-Diff: An Effective Change Detection Algorithm for XML Documents</title>
		<field type="bibtex:topic">xdiff[0.9]</field>
	</reference>
	<reference name="dav03" src="bibtex:inproceedings" src-info="bibtex:line-11566" type="sharef:inproceedings" crossref="icde2003">
		<names type="sharef:author">
			<person>
				<givenname>Susan B.</givenname>
				<surname>Davidson</surname>
			</person>
			<person>
				<givenname>Wenfei</givenname>
				<surname>Fan</surname>
			</person>
			<person>
				<givenname>Carmem S.</givenname>
				<surname>Hara</surname>
			</person>
			<person>
				<givenname>Jing</givenname>
				<surname>Qin</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>We present a technique for refining the design of relational storage for XML data based on XML key propagation. Three algorithms are presented: one checks whether a given functional dependency is propagated from XML keys via a predefined view; the others compute a minimum cover for all functional dependencies on a universal relation given XML keys. Experimental results show that these algorithms are efficient in practice. We also investigate the complexity of propagating other XML constraints to relations, and the effect of increasing the power of the transformation language. Computing XML key propagation is a first step toward establishing a connection between XML data and its relational representation at the semantic level.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1109/ICDE.2003.1260820</identifier>
		<pages>543</pages>
		<title type="sharef:primaryTitle">Propagating XML Constraints to Relations</title>
	</reference>
	<reference name="bar03" src="bibtex:inproceedings" src-info="bibtex:line-11575" type="sharef:inproceedings" crossref="icde2003">
		<names type="sharef:author">
			<person>
				<givenname>Charles</givenname>
				<surname>Barton</surname>
			</person>
			<person>
				<givenname>Philippe</givenname>
				<surname>Charles</surname>
			</person>
			<person>
				<givenname>Deepak</givenname>
				<surname>Goyal</surname>
			</person>
			<person>
				<givenname>Mukund</givenname>
				<surname>Raghavachari</surname>
			</person>
			<person>
				<givenname>Marcus</givenname>
				<surname>Fontoura</surname>
			</person>
			<person>
				<givenname>Vanja</givenname>
				<surname>Josifovski</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>We present a streaming algorithm for evaluating XPath expressions that use backward axes (parent and ancestor) and forward axes in a single document-order traversal of an XML document. Other streaming XPath processors handle only forward axes. We show through experiments that our algorithm significantly outperforms (by more than a factor of two) a traditional non-streaming XPath engine. Furthermore, our algorithm scales better because it retains only the relevant portions of the input document in memory. Our engine successfully processes documents over 1GB in size, whereas the traditional XPath engine degrades considerably in performance for documents over 100 MB in size and fails to complete for documents of size over 200 MB.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1109/ICDE.2003.1260813</identifier>
		<pages>455-466</pages>
		<title type="sharef:primaryTitle">Streaming XPath Processing with Forward and Backward Axes</title>
		<field type="bibtex:topic">xpath[0.8]</field>
	</reference>
	<reference name="rag03" src="bibtex:inproceedings" src-info="bibtex:line-11585" type="sharef:inproceedings" crossref="icde2003">
		<names type="sharef:author">
			<person>
				<givenname>Sriram</givenname>
				<surname>Raghavan</surname>
			</person>
			<person>
				<givenname>Hector</givenname>
				<surname>Garcia-Molina</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>A Web repository is a large special-purpose collection of Web pages and associated indexes. Many useful queries and computations over such repositories involve traversal and navigation of the Web graph. However, efficient traversal of huge Web graphs containing several hundred million vertices and a few billion edges is a challenging problem. An additional complication is the lack of a schema to describe the structure of Web graphs. As a result, naive graph representation schemes can significantly increase query execution time and limit the usefulness of Web repositories. We propose a novel representation for Web graphs, called an S-Node representation. We demonstrate that S-Node representations are highly space-efficient, enabling in-memory processing of very large Web graphs. In addition, we present detailed experiments that show that S-Node representations can significantly reduce query execution times when compared with other schemes for representing Web graphs.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1109/ICDE.2003.1260809</identifier>
		<pages>405-416</pages>
		<title type="sharef:primaryTitle">Representing Web Graphs</title>
		<identifier type="sharef:uri" resourceType="application/pdf">http://www.almaden.ibm.com/cs/people/rsriram/pubs/icde03.pdf</identifier>
	</reference>
	<reference name="icde2003" src="bibtex:proceedings" src-info="bibtex:line-11595" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>Umeshwar</givenname>
				<surname>Dayal</surname>
			</person>
			<person>
				<givenname>Krithi</givenname>
				<surname>Ramamritham</surname>
			</person>
			<person>
				<givenname>T. M.</givenname>
				<surname>Vijayaraman</surname>
			</person>
		</names>
		<date value="2003-03"/>
		<address type="sharef:placePublished">Bangalore, India</address>
		<field type="bibtex:index">ICDE 2003</field>
		<identifier type="sharef:isbn">0-7803-7665-X</identifier>
		<field type="bibtex:key">19th International Conference on Data Engineering</field>
		<publisher>IEEE Computer Society Press</publisher>
		<title type="sharef:primaryTitle">19th International Conference on Data Engineering</title>
		<identifier type="sharef:uri" resourceType="text/html">http://www.informatik.uni-trier.de/~ley/db/conf/icde/icde2003.html</identifier>
	</reference>
	<reference name="kri04" src="bibtex:inproceedings" src-info="bibtex:line-11613" type="sharef:inproceedings" crossref="icde2004">
		<names type="sharef:author">
			<person>
				<givenname>Rajasekar</givenname>
				<surname>Krishnamurthy</surname>
			</person>
			<person>
				<givenname>Venkatesan T.</givenname>
				<surname>Chakaravarthy</surname>
			</person>
			<person>
				<givenname>Raghav</givenname>
				<surname>Kaushik</surname>
			</person>
			<person>
				<givenname>Jeffrey F.</givenname>
				<surname>Naughton</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>We consider the problem of translating XML queries into SQL when XML documents have been stored in an RDBMS using a schema-based relational decomposition. Surprisingly, there is no published XML-to-SQL query translation algorithm for this scenario that handles recursive XML schemas. We present a generic algorithm to translate path expression queries into SQL in the presence of recursion in the schema and queries. This algorithm handles a general class of XML-to-Relational mappings, which includes all techniques proposed in literature. Some of the salient features of this algorithm are: (i) It translates a path expression query into a single SQL query, irrespective of how complex the XML schema is, (ii) It uses the "with" clause in SQL99 to handle recursive queries even over non-recursive schemas, (iii) It reconstructs recursive XML subtrees with a single SQL query and (iv) It shows that the support for linear recursion in SQL99 is sufficient for handling path expression queries over arbitrarily complex recursive XML schema.</p>
			</richtext>
		</abstract>
		<pages>42-53</pages>
		<title type="sharef:primaryTitle">Recursive XML Schemas, Recursive XML Queries, and Relational Storage: XML-to-SQL Query Translation</title>
		<field type="bibtex:topic">xsd[0.7]</field>
		<identifier type="sharef:uri" resourceType="text/html">http://csdl.computer.org/comp/proceedings/icde/2004/2065/00/20650042abs.htm</identifier>
	</reference>
	<reference name="icde2004" src="bibtex:proceedings" src-info="bibtex:line-11623" type="sharef:proceedings">
		<date value="2004-03"/>
		<address type="sharef:placePublished">Boston, Massachusetts</address>
		<field type="bibtex:index">ICDE 2004</field>
		<identifier type="sharef:isbn">0-7695-2065-0</identifier>
		<field type="bibtex:key">20th International Conference on Data Engineering</field>
		<publisher>IEEE Computer Society Press</publisher>
		<title type="sharef:primaryTitle">20th International Conference on Data Engineering</title>
	</reference>
	<reference name="sto05" src="bibtex:inproceedings" src-info="bibtex:line-11639" type="sharef:inproceedings" crossref="icde2005">
		<names type="sharef:author">
			<person>
				<givenname>Michael</givenname>
				<surname>Stonebraker</surname>
			</person>
			<person>
				<givenname>Uğur</givenname>
				<surname>Çetintemel</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>The last 25 years of commercial DBMS development can be summed up in a single phrase: "one size fits all". This phrase refers to the fact that the traditional DBMS architecture (originally designed and optimized for business data processing) has been used to support many data-centric applications with widely varying characteristics and requirements. In this paper, we argue that this concept is no longer applicable to the database market, and that the commercial world will fracture into a collection of independent database engines, some of which may be unified by a common front-end parser. We use examples from the stream-processing market and the data-warehouse market to bolster our claims. We also briefly discuss other markets for which the traditional architecture is a poor fit and argue for a critical rethinking of the current factoring of systems services into products.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1109/ICDE.2005.1</identifier>
		<pages>2-11</pages>
		<title type="sharef:primaryTitle">"One Size Fits All": An Idea Whose Time Has Come and Gone</title>
		<identifier type="sharef:uri" resourceType="application/pdf">http://www.cs.brown.edu/~ugur/fits_all.pdf</identifier>
	</reference>
	<reference name="icde2005" src="bibtex:proceedings" src-info="bibtex:line-11649" type="sharef:proceedings">
		<date value="2005-04"/>
		<address type="sharef:placePublished">Tokyo, Japan</address>
		<field type="bibtex:index">ICDE 2005</field>
		<identifier type="sharef:isbn">0-7695-2285-8</identifier>
		<field type="bibtex:key">21st International Conference on Data Engineering</field>
		<publisher>IEEE Computer Society Press</publisher>
		<title type="sharef:primaryTitle">21st International Conference on Data Engineering</title>
		<identifier type="sharef:uri" resourceType="text/html">http://www.informatik.uni-trier.de/~ley/db/conf/icde/icde2005.html</identifier>
	</reference>
	<reference name="bur06" src="bibtex:inproceedings" src-info="bibtex:line-11666" type="sharef:inproceedings" crossref="icde2006">
		<names type="sharef:author">
			<person>
				<givenname>A.</givenname>
				<surname>Burrell</surname>
			</person>
			<person>
				<givenname>Angela C.</givenname>
				<surname>Sodan</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>We consider the problem of translating XML queries into SQL when XML documents have been stored in an RDBMS using a schema-based relational decomposition. Surprisingly, there is no published XML-to-SQL query translation algorithm for this scenario that handles recursive XML schemas. We present a generic algorithm to translate path expression queries into SQL in the presence of recursion in the schema and queries. This algorithm handles a general class of XML-to-Relational mappings, which includes all techniques proposed in literature. Some of the salient features of this algorithm are: (i) It translates a path expression query into a single SQL query, irrespective of how complex the XML schema is, (ii) It uses the "with" clause in SQL99 to handle recursive queries even over non-recursive schemas, (iii) It reconstructs recursive XML subtrees with a single SQL query and (iv) It shows that the support for linear recursion in SQL99 is sufficient for handling path expression queries over arbitrarily complex recursive XML schema.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1109/ICDEW.2006.163</identifier>
		<pages>42</pages>
		<title type="sharef:primaryTitle">Web Interface Navigation Design: Which Style of Navigation-Link Menus Do Users Prefer?</title>
		<identifier type="sharef:uri">http://doi.ieeecomputersociety.org/10.1109/ICDEW.2006.163</identifier>
	</reference>
	<reference name="icde2006" src="bibtex:proceedings" src-info="bibtex:line-11676" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>Roger S.</givenname>
				<surname>Barga</surname>
			</person>
			<person>
				<givenname>Xiaofang</givenname>
				<surname>Zhou</surname>
			</person>
		</names>
		<date value="2006-04"/>
		<address type="sharef:placePublished">Atlanta, Georgia</address>
		<field type="bibtex:index">ICDE 2006</field>
		<field type="bibtex:key">22nd International Conference on Data Engineering</field>
		<publisher>IEEE Computer Society Press</publisher>
		<title type="sharef:primaryTitle">22nd International Conference on Data Engineering</title>
		<identifier type="sharef:uri" resourceType="text/html">http://www.informatik.uni-trier.de/~ley/db/conf/icde/icde2006.html</identifier>
	</reference>
	<reference name="haa07b" src="bibtex:inproceedings" src-info="bibtex:line-11693" type="sharef:inproceedings" crossref="icde2007">
		<names type="sharef:author">
			<person>
				<givenname>Laura M.</givenname>
				<surname>Haas</surname>
			</person>
			<person>
				<givenname>Steve B.</givenname>
				<surname>Cousins</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Ordinary people have access to unprecedented volumes of information today. Researchers in the fields of information management (IM) and human-computer interaction (HCI) are reacting to this challenge from their own unique perspectives. Having access to a billion records is cool, but having access to a billion people is awesome. In this paper, we look at recent research from both communities, and speculate on how interactions between the communities could enhance the user experience of information.</p>
			</richtext>
		</abstract>
		<pages>21-25</pages>
		<title type="sharef:primaryTitle">Information for People</title>
		<identifier type="sharef:uri">http://ieeexplore.ieee.org/search/wrapper.jsp?arnumber=4221650</identifier>
	</reference>
	<reference name="icde2007" src="bibtex:proceedings" src-info="bibtex:line-11702" type="sharef:proceedings">
		<date value="2007-04"/>
		<address type="sharef:placePublished">Istanbul, Turkey</address>
		<field type="bibtex:index">ICDE 2007</field>
		<field type="bibtex:key">23rd International Conference on Data Engineering</field>
		<publisher>IEEE Computer Society Press</publisher>
		<title type="sharef:primaryTitle">23rd International Conference on Data Engineering</title>
		<identifier type="sharef:uri" resourceType="text/html">http://www.informatik.uni-trier.de/~ley/db/conf/icde/icde2007.html</identifier>
	</reference>
	<reference name="ahm08" src="bibtex:inproceedings" src-info="bibtex:line-11718" type="sharef:inproceedings" crossref="icde2008">
		<names type="sharef:author">
			<person>
				<givenname>Yanif</givenname>
				<surname>Ahmad</surname>
			</person>
			<person>
				<givenname>Suman</givenname>
				<surname>Nath</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>We present COLR-Tree, an abstraction layer designed to support efficient spatio-temporal queries on live data gathered from a large collection of sensors. We use COLR-Tree in a publicly-available sensor web portal to separate the concerns of sensor data management from the web portal application. COLR-Tree uses two techniques to optimize end-to-end latencies of users' queries by minimizing expensive data collection from sensors. First, it uses a novel technique to effectively cache aggregate results computed over sensor data with different expiry times. Second, it incorporates an efficient one-pass sampling algorithm with its range lookup to utilize cached data and compensate for occasional unavailability of sensors. We evaluate our implementation of COLR-Tree on SQL Server 2005 with a real, large workload from Windows Live Local. Our experiments demonstrate that COLR-Tree significantly improves both the end-to-end query performance and the number of sensors accessed compared to existing techniques.</p>
			</richtext>
		</abstract>
		<pages>784-793</pages>
		<title type="sharef:primaryTitle">COLR-Tree: Communication-Efficient Spatio-Temporal Indexing for a Sensor Data Web Portal</title>
		<identifier type="sharef:uri">http://ieeexplore.ieee.org/search/wrapper.jsp?arnumber=4497487</identifier>
		<identifier type="sharef:uri">http://research.microsoft.com/apps/pubs/default.aspx?id=76107</identifier>
	</reference>
	<reference name="icde2008" src="bibtex:proceedings" src-info="bibtex:line-11728" type="sharef:proceedings">
		<date value="2008-04"/>
		<address type="sharef:placePublished">Cancún, Mexico</address>
		<field type="bibtex:index">ICDE 2008</field>
		<field type="bibtex:key">24th International Conference on Data Engineering</field>
		<publisher>IEEE Computer Society Press</publisher>
		<title type="sharef:primaryTitle">24th International Conference on Data Engineering</title>
		<identifier type="sharef:uri" resourceType="text/html">http://www.informatik.uni-trier.de/~ley/db/conf/icde/icde2008.html</identifier>
	</reference>
	<reference name="dou08" src="bibtex:inproceedings" src-info="bibtex:line-11744" type="sharef:inproceedings" crossref="osdi2008">
		<names type="sharef:author">
			<person>
				<givenname>John R.</givenname>
				<surname>Douceur</surname>
			</person>
			<person>
				<givenname>Jeremy</givenname>
				<surname>Elson</surname>
			</person>
			<person>
				<givenname>Jon</givenname>
				<surname>Howell</surname>
			</person>
			<person>
				<givenname>Jacob R.</givenname>
				<surname>Lorch</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Xax is a browser plugin model that enables developers to leverage existing tools, libraries, and entire programs to deliver feature-rich applications on the web. Xax employs a novel combination of mechanisms that collectively provide security, OS-independence, performance, and support for legacy code. These mechanisms include memory-isolated native code execution behind a narrow syscall interface, an abstraction layer that provides a consistent binary interface across operating systems, system services via hooks to existing browser mechanisms, and lightweight modifications to existing tool chains and code bases. We demonstrate a variety of applications and libraries from existing code bases, in several languages, produced with various tool chains, running in multiple browsers on multiple operating systems. With roughly two person-weeks of effort, we ported 3.3 million lines of code to Xax, including a PDF viewer, a Python interpreter, a speech synthesizer, and an OpenGL pipeline.</p>
			</richtext>
		</abstract>
		<pages>339-354</pages>
		<title type="sharef:primaryTitle">Leveraging Legacy Code to Deploy Desktop Applications on the Web</title>
		<field type="bibtex:topic">xax[1]</field>
		<identifier type="sharef:uri" resourceType="application/pdf">http://research.microsoft.com/pubs/72878/xax-osdi08.pdf</identifier>
		<identifier type="sharef:uri" resourceType="text/html">http://www.usenix.org/event/osdi08/tech/full_papers/douceur/douceur_html/index.html</identifier>
		<identifier type="sharef:uri" resourceType="application/pdf">http://www.usenix.org/events/osdi08/tech/full_papers/douceur/douceur.pdf</identifier>
	</reference>
	<reference name="osdi2008" src="bibtex:proceedings" src-info="bibtex:line-11756" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>Richard</givenname>
				<surname>Draves</surname>
			</person>
			<person>
				<givenname>Robbert</givenname>
				<surname link="van">Renesse</surname>
			</person>
		</names>
		<date value="2008-12"/>
		<address type="sharef:placePublished">San Diego, California</address>
		<identifier type="sharef:isbn">978-1-931971-65-2</identifier>
		<field type="bibtex:key">8th USENIX Symposium on Operating Systems Design and Implementation (OSDI 2008)</field>
		<title type="sharef:primaryTitle">8th USENIX Symposium on Operating Systems Design and Implementation (OSDI 2008)</title>
		<identifier type="sharef:uri" resourceType="text/html">http://www.informatik.uni-trier.de/~ley/db/conf/osdi/osdi2008.html</identifier>
	</reference>
	<reference name="pam95" src="bibtex:inproceedings" src-info="bibtex:line-11772" type="sharef:inproceedings" crossref="apwww95">
		<names type="sharef:author">
			<person>
				<givenname>Andrew</givenname>
				<surname>Pam</surname>
			</person>
		</names>
		<field type="bibtex:index">WWW</field>
		<title type="sharef:primaryTitle">Where World Wide Web Went Wrong</title>
	</reference>
	<reference name="apwww95" src="bibtex:proceedings" src-info="bibtex:line-11779" type="sharef:proceedings">
		<date value="1995-09"/>
		<address type="sharef:placePublished">Sydney, Australia</address>
		<field type="bibtex:index">APWWW '95</field>
		<title type="sharef:primaryTitle">Asia-Pacific World Wide Web '95 Conference</title>
		<identifier type="sharef:uri" resourceType="text/html">http://www.csu.edu.au/special/conference/WWWWW.html</identifier>
	</reference>
	<reference name="bou04" src="bibtex:inproceedings" src-info="bibtex:line-11793" type="sharef:inproceedings" crossref="apccm04">
		<names type="sharef:author">
			<person>
				<givenname>Aida</givenname>
				<surname>Boukottaya</surname>
			</person>
			<person>
				<givenname>Christine</givenname>
				<surname>Vanoirbeek</surname>
			</person>
			<person>
				<givenname>Federica</givenname>
				<surname>Paganelli</surname>
			</person>
			<person>
				<givenname>Omar</givenname>
				<surname>Abou Khaled</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>The growing use of XML mark-up language has made a large amount of heterogeneous XML documents widely available. As the number of applications that utilize heterogeneous XML documents grows, the importance of XML documents transformations increases greatly. A serious obstacle for translating directly between two XML documents, using languages like XSLT, is that a mapping between the two XML representations needs to be carefully specified by a human expert. Current research attempts to address this problem by proposing algorithms to automate aspects of XML schemas matching task. In this paper, we identify two major problems encountered when current matching algorithms are used in the context of XML documents transformations. The first problem concerns possible scalability problem due to the diversity of schema constructs. The second problem deals with the need to perform semantic matching. We argue in favor of conceptual modelling as solution to avoid such problems. We introduce a new layered model for XML schemas, called Layered Interoperability Model for XML Schemas (LIMXS). LIMXS offers a semantic view for XML schemas through the specification of concepts and semantic relationships among them. We will show how our model transforms the matching algorithm into a dynamic and incremental algorithm that provide semantic mappings and helps to automate the transformation process.</p>
			</richtext>
		</abstract>
		<pages>81-90</pages>
		<title type="sharef:primaryTitle">Automating XML Document Transformations: A Conceptual Modelling Based Approach</title>
		<field type="bibtex:topic">limxs[0.9]</field>
		<identifier type="sharef:uri" resourceType="application/pdf">http://crpit.com/confpapers/CRPITV31Boukottaya.pdf</identifier>
	</reference>
	<reference name="apccm04" src="bibtex:proceedings" src-info="bibtex:line-11803" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>Sven</givenname>
				<surname>Hartmann</surname>
			</person>
			<person>
				<givenname>John F.</givenname>
				<surname>Roddick</surname>
			</person>
		</names>
		<date value="2004-01"/>
		<address type="sharef:placePublished">Dunedin, New Zealand</address>
		<field type="bibtex:index">APCCM 2004</field>
		<identifier type="sharef:isbn">1-920682-13-9</identifier>
		<title type="sharef:primaryTitle">First Asia-Pacific Conference on Conceptual Modelling</title>
		<identifier type="sharef:uri" resourceType="text/html">http://www.informatik.uni-trier.de/~ley/db/conf/apccm/apccm2004.html</identifier>
	</reference>
	<reference name="fie05" src="bibtex:inproceedings" src-info="bibtex:line-11819" type="sharef:inproceedings" crossref="apccm05">
		<names type="sharef:author">
			<person>
				<givenname>Gunar</givenname>
				<surname>Fiedler</surname>
			</person>
			<person>
				<givenname>Thomas</givenname>
				<surname>Raak</surname>
			</person>
			<person>
				<givenname>Bernhard</givenname>
				<surname>Thalheim</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Database integration is currently solved only for the case of simple structures. Semantics is mainly neglected. It is known but often neglected that database integration cannot be automated. System integration is far more difficult. Both integrations can only be performed if a number of assumptions can be made for the integrated system. Instead of integrating systems entirely cooperation or collaboration of systems can be developed and used. We propose in this paper the extension of the view cooperation approach to database collaboration.</p>
			</richtext>
		</abstract>
		<pages>49-58</pages>
		<title type="sharef:primaryTitle">Database Collaboration Instead of Integration</title>
		<identifier type="sharef:uri" resourceType="application/pdf">http://crpit.com/confpapers/CRPITV43Fiedler.pdf</identifier>
	</reference>
	<reference name="apccm05" src="bibtex:proceedings" src-info="bibtex:line-11828" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>Sven</givenname>
				<surname>Hartmann</surname>
			</person>
			<person>
				<givenname>Markus</givenname>
				<surname>Stumptner</surname>
			</person>
		</names>
		<date value="2005-01"/>
		<address type="sharef:placePublished">Newcastle, Australia</address>
		<field type="bibtex:index">APCCM 2005</field>
		<identifier type="sharef:isbn">1-920-68225-2</identifier>
		<title type="sharef:primaryTitle">2nd Asia-Pacific Conference on Conceptual Modelling</title>
		<identifier type="sharef:uri" resourceType="text/html">http://www.informatik.uni-trier.de/~ley/db/conf/apccm/apccm2005.html</identifier>
	</reference>
	<reference name="tru07" src="bibtex:inproceedings" src-info="bibtex:line-11844" type="sharef:inproceedings" crossref="tapia2007">
		<names type="sharef:author">
			<person>
				<givenname>Beth</givenname>
				<surname>Trushkowsky</surname>
			</person>
			<person>
				<givenname>Kamaria</givenname>
				<surname>Campbell</surname>
			</person>
			<person>
				<givenname>Jeffrey</givenname>
				<surname>Forbes</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>CoBib is a system that will allow affinity groups to effectively collaborate to maximize the searching and browsing utility of an academic paper database. The system will facilitate the process of surveying literature in a specific field by using the community's annotations and referrals. The database architecture for CoBib provides users within research communities the means to collaboratively index and annotate citations by supporting both searching and browsing behavior. This extensible architecture is a novel solution that is interoperable with existing data formats and systems and incorporates recommendations gathered from the community for the discovery of new citations.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/1347787.1347790</identifier>
		<title type="sharef:primaryTitle">An Architecture for a Collaborative Bibliographic Database</title>
	</reference>
	<reference name="tapia2007" src="bibtex:proceedings" src-info="bibtex:line-11852" type="sharef:proceedings">
		<date value="2007-10"/>
		<address type="sharef:placePublished">Orlando, Florida</address>
		<identifier type="sharef:isbn">978-1-59593-866-4</identifier>
		<title type="sharef:primaryTitle">TAPIA Conference on Diversity in Computing</title>
	</reference>
	<reference name="mcb94" src="bibtex:inproceedings" src-info="bibtex:line-11865" type="sharef:inproceedings" crossref="www1">
		<names type="sharef:author">
			<person>
				<givenname>Oliver A.</givenname>
				<surname>McBryan</surname>
			</person>
		</names>
		<field type="bibtex:index">WWW, WWWW, robot</field>
		<title type="sharef:primaryTitle">GENVL and WWWW: Tools for Taming the Web</title>
	</reference>
	<reference name="dra94" src="bibtex:inproceedings" src-info="bibtex:line-11872" type="sharef:inproceedings" crossref="www1">
		<names type="sharef:author">
			<person>
				<givenname>Nikos</givenname>
				<surname>Drakos</surname>
			</person>
		</names>
		<field type="bibtex:index">LaTeX2HTML</field>
		<title type="sharef:primaryTitle">From Text to Hypertext: A Post-Hoc Rationalisation of LaTeX2HTML</title>
		<field type="bibtex:topic">html[0.8] latex[0.8]</field>
	</reference>
	<reference name="www1" src="bibtex:proceedings" src-info="bibtex:line-11880" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>Oscar</givenname>
				<surname>Nierstrasz</surname>
			</person>
		</names>
		<date value="1994-05"/>
		<address type="sharef:placePublished">Geneva, Switzerland</address>
		<field type="bibtex:index">WWW1</field>
		<title type="sharef:primaryTitle">First International World Wide Web Conference</title>
		<field type="bibtex:topic">www[0.8]</field>
		<identifier type="sharef:uri">http://www.cern.ch/WWW94</identifier>
	</reference>
	<reference name="abr95" src="bibtex:inproceedings" src-info="bibtex:line-11896" type="sharef:inproceedings" crossref="www4">
		<names type="sharef:author">
			<person>
				<givenname>Marc</givenname>
				<surname>Abrams</surname>
			</person>
			<person>
				<givenname>Charles R.</givenname>
				<surname>Standridge</surname>
			</person>
			<person>
				<givenname>Ghaleb</givenname>
				<surname>Abdulla</surname>
			</person>
			<person>
				<givenname>Stephen D.</givenname>
				<surname>Williams</surname>
			</person>
			<person>
				<givenname>Edward A.</givenname>
				<surname>Fox</surname>
			</person>
		</names>
		<field type="bibtex:index">WWW, caching</field>
		<pages>119-133</pages>
		<title type="sharef:primaryTitle">Caching Proxies: Limitations and Potentials</title>
	</reference>
	<reference name="car95" src="bibtex:inproceedings" src-info="bibtex:line-11904" type="sharef:inproceedings" crossref="www4">
		<names type="sharef:author">
			<person>
				<givenname>Leslie A.</givenname>
				<surname>Carr</surname>
			</person>
			<person>
				<givenname>David C.</givenname>
				<surname>De Roure</surname>
			</person>
			<person>
				<givenname>Wendy</givenname>
				<surname>Hall</surname>
			</person>
			<person>
				<givenname>Gary J.</givenname>
				<surname>Hill</surname>
			</person>
		</names>
		<pages>647-656</pages>
		<title type="sharef:primaryTitle">The Distributed Link Service: A Tool for Publishers, Authors and Readers</title>
		<field type="bibtex:topic">dls[1]</field>
	</reference>
	<reference name="www4" src="bibtex:proceedings" src-info="bibtex:line-11912" type="sharef:proceedings">
		<date value="1995-12"/>
		<address type="sharef:placePublished">Boston, Massachusetts</address>
		<field type="bibtex:index">WWW4</field>
		<field type="bibtex:key">Fourth International World Wide Web Conference</field>
		<title type="sharef:primaryTitle">Fourth International World Wide Web Conference</title>
		<field type="bibtex:topic">www[0.8]</field>
		<identifier type="sharef:uri">http://www.w3j.com/1/</identifier>
	</reference>
	<reference name="bol96" src="bibtex:inproceedings" src-info="bibtex:line-11928" type="sharef:inproceedings" crossref="www5">
		<names type="sharef:author">
			<person>
				<givenname>Jean-Chrysostome</givenname>
				<surname>Bolot</surname>
			</person>
			<person>
				<givenname>Philipp</givenname>
				<surname>Hoschka</surname>
			</person>
		</names>
		<field type="bibtex:index">WWW, caching</field>
		<pages>1397-1405</pages>
		<title type="sharef:primaryTitle">Performance Engineering of the World Wide Web: Application to Dimensioning and Cache Design</title>
	</reference>
	<reference name="mar96" src="bibtex:inproceedings" src-info="bibtex:line-11936" type="sharef:inproceedings" crossref="www5">
		<names type="sharef:author">
			<person>
				<givenname>Evangelos P.</givenname>
				<surname>Markatos</surname>
			</person>
		</names>
		<field type="bibtex:index">WWW, caching</field>
		<pages>893-905</pages>
		<title type="sharef:primaryTitle">Main Memory Caching of Web Documents</title>
	</reference>
	<reference name="din96" src="bibtex:inproceedings" src-info="bibtex:line-11944" type="sharef:inproceedings" crossref="www5">
		<names type="sharef:author">
			<person>
				<givenname>Adam</givenname>
				<surname>Dingle</surname>
			</person>
			<person>
				<givenname>Tomas</givenname>
				<surname>Partl</surname>
			</person>
		</names>
		<field type="bibtex:index">WWW, caching</field>
		<pages>907-920</pages>
		<title type="sharef:primaryTitle">Web Cache Coherence</title>
	</reference>
	<reference name="tha96" src="bibtex:inproceedings" src-info="bibtex:line-11952" type="sharef:inproceedings" crossref="www5">
		<names type="sharef:author">
			<person>
				<givenname>Robert</givenname>
				<surname>Thau</surname>
			</person>
		</names>
		<field type="bibtex:index">WWW, apache</field>
		<pages>1113-1122</pages>
		<title type="sharef:primaryTitle">Design Considerations for the Apache Server API</title>
	</reference>
	<reference name="woo96" src="bibtex:inproceedings" src-info="bibtex:line-11960" type="sharef:inproceedings" crossref="www5">
		<names type="sharef:author">
			<person>
				<givenname>Allison</givenname>
				<surname>Woodruff</surname>
			</person>
			<person>
				<givenname>Paul M.</givenname>
				<surname>Aoki</surname>
			</person>
			<person>
				<givenname>Eric</givenname>
				<surname>Brewer</surname>
			</person>
			<person>
				<givenname>Paul</givenname>
				<surname>Gauthier</surname>
			</person>
			<person>
				<givenname>Lawrence A.</givenname>
				<surname>Rowe</surname>
			</person>
		</names>
		<field type="bibtex:index">WWW</field>
		<pages>963-979</pages>
		<title type="sharef:primaryTitle">An Investigation of Documents from the World Wide Web</title>
	</reference>
	<reference name="bra96" src="bibtex:inproceedings" src-info="bibtex:line-11968" type="sharef:inproceedings" crossref="www5">
		<names type="sharef:author">
			<person>
				<givenname>Tim</givenname>
				<surname>Bray</surname>
			</person>
		</names>
		<field type="bibtex:index">WWW</field>
		<title type="sharef:primaryTitle">Measuring the Web</title>
	</reference>
	<reference name="www5" src="bibtex:proceedings" src-info="bibtex:line-11975" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>Mark</givenname>
				<surname>Eligh</surname>
			</person>
			<person>
				<givenname>Jan</givenname>
				<surname>Kastelein</surname>
			</person>
		</names>
		<date value="1996-05"/>
		<address type="sharef:placePublished">Paris, France</address>
		<field type="bibtex:index">WWW5</field>
		<title type="sharef:primaryTitle">Fifth International World Wide Web Conference</title>
		<field type="bibtex:topic">www[0.8]</field>
		<identifier type="sharef:uri">http://www5conf.inria.fr</identifier>
	</reference>
	<reference name="aro97" src="bibtex:inproceedings" src-info="bibtex:line-11991" type="sharef:inproceedings" crossref="www6">
		<names type="sharef:author">
			<person>
				<givenname>Gustavo O.</givenname>
				<surname>Arocena</surname>
			</person>
			<person>
				<givenname>Alberto O.</givenname>
				<surname>Mendelzon</surname>
			</person>
			<person>
				<givenname>George A.</givenname>
				<surname>Mihaila</surname>
			</person>
		</names>
		<field type="bibtex:index">WWW, WebSQL</field>
		<title type="sharef:primaryTitle">Applications of a Web Query Language</title>
	</reference>
	<reference name="woo97" src="bibtex:inproceedings" src-info="bibtex:line-11998" type="sharef:inproceedings" crossref="www6">
		<names type="sharef:author">
			<person>
				<givenname>Roland P.</givenname>
				<surname>Wooster</surname>
			</person>
			<person>
				<givenname>Marc</givenname>
				<surname>Abrams</surname>
			</person>
		</names>
		<field type="bibtex:index">WWW, caching</field>
		<pages>977-986</pages>
		<title type="sharef:primaryTitle">Proxy Caching That Estimates Page Load Delays</title>
	</reference>
	<reference name="kel97" src="bibtex:inproceedings" src-info="bibtex:line-12006" type="sharef:inproceedings" crossref="www6">
		<names type="sharef:author">
			<person>
				<givenname>Richard M.</givenname>
				<surname>Keller</surname>
			</person>
			<person>
				<givenname>Shawn R.</givenname>
				<surname>Wolfe</surname>
			</person>
			<person>
				<givenname>James R.</givenname>
				<surname>Chen</surname>
			</person>
			<person>
				<givenname>Joshua L.</givenname>
				<surname>Rabinowitz</surname>
			</person>
			<person>
				<givenname>Nathalie</givenname>
				<surname>Mathe</surname>
			</person>
		</names>
		<field type="bibtex:index">WWW, bookmark, URL</field>
		<pages>1103-1114</pages>
		<title type="sharef:primaryTitle">A Bookmarking Service for Organizing and Sharing URLs</title>
	</reference>
	<reference name="ram97" src="bibtex:inproceedings" src-info="bibtex:line-12014" type="sharef:inproceedings" crossref="www6">
		<names type="sharef:author">
			<person>
				<givenname>T. V.</givenname>
				<surname>Raman</surname>
			</person>
		</names>
		<field type="bibtex:index">WWW, CSS, speech</field>
		<title type="sharef:primaryTitle">Cascaded Speech Style Sheets</title>
	</reference>
	<reference name="bec97" src="bibtex:inproceedings" src-info="bibtex:line-12021" type="sharef:inproceedings" crossref="www6">
		<names type="sharef:author">
			<person>
				<givenname>Dave</givenname>
				<surname>Beckett</surname>
			</person>
		</names>
		<field type="bibtex:index">WWW, survey</field>
		<title type="sharef:primaryTitle">30% Accessible — A Survey of The UK Wide Web</title>
	</reference>
	<reference name="pit97" src="bibtex:inproceedings" src-info="bibtex:line-12028" type="sharef:inproceedings" crossref="www6">
		<names type="sharef:author">
			<person>
				<givenname>James</givenname>
				<surname>Pitkow</surname>
			</person>
		</names>
		<field type="bibtex:index">WWW</field>
		<title type="sharef:primaryTitle">In Search of Reliable Usage Data on the WWW</title>
	</reference>
	<reference name="sch97" src="bibtex:inproceedings" src-info="bibtex:line-12035" type="sharef:inproceedings" crossref="www6">
		<names type="sharef:author">
			<person>
				<givenname>Peter</givenname>
				<surname>Scheuermann</surname>
			</person>
			<person>
				<givenname>Junho</givenname>
				<surname>Shim</surname>
			</person>
			<person>
				<givenname>Radek</givenname>
				<surname>Vingralek</surname>
			</person>
		</names>
		<field type="bibtex:index">WWW, caching</field>
		<pages>997-1005</pages>
		<title type="sharef:primaryTitle">A Case for Delay-Conscious Caching of Web Documents</title>
	</reference>
	<reference name="gir97" src="bibtex:inproceedings" src-info="bibtex:line-12043" type="sharef:inproceedings" crossref="www6">
		<names type="sharef:author">
			<person>
				<givenname>Andreas</givenname>
				<surname>Girgensohn</surname>
			</person>
			<person>
				<givenname>Alison</givenname>
				<surname>Lee</surname>
			</person>
		</names>
		<field type="bibtex:index">WWW, caching</field>
		<pages>1531-1542</pages>
		<title type="sharef:primaryTitle">Seamless Integration of interactive forms into the Web</title>
	</reference>
	<reference name="www6" src="bibtex:proceedings" src-info="bibtex:line-12051" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>Sarah</givenname>
				<surname>Imbach</surname>
			</person>
		</names>
		<date value="1997-04"/>
		<address type="sharef:placePublished">Santa Clara, California</address>
		<field type="bibtex:index">WWW6</field>
		<title type="sharef:primaryTitle">Sixth International World Wide Web Conference</title>
		<field type="bibtex:topic">www[0.8]</field>
		<identifier type="sharef:uri">http://www.scope.gmd.de/info/www6</identifier>
	</reference>
	<reference name="rag98a" src="bibtex:inproceedings" src-info="bibtex:line-12067" type="sharef:inproceedings" crossref="www7">
		<names type="sharef:author">
			<person>
				<givenname>Dave</givenname>
				<surname>Raggett</surname>
			</person>
		</names>
		<identifier type="sharef:doi">10.1016/S0169-7552(98)00122-6</identifier>
		<field type="bibtex:index">WWW, HTML, CSS, HTML Tidy</field>
		<title type="sharef:primaryTitle">Clean up your Web pages with HP's HTML Tidy</title>
	</reference>
	<reference name="lie98" src="bibtex:inproceedings" src-info="bibtex:line-12075" type="sharef:inproceedings" crossref="www7">
		<names type="sharef:author">
			<person>
				<givenname>Olivier</givenname>
				<surname>Liechti</surname>
			</person>
			<person>
				<givenname>Mark J.</givenname>
				<surname>Sifer</surname>
			</person>
			<person>
				<givenname>Tadao</givenname>
				<surname>Ichikawa</surname>
			</person>
		</names>
		<field type="bibtex:index">WWW, XML, SGF</field>
		<title type="sharef:primaryTitle">Structured graph format: XML metadata for describing Web site structure</title>
		<field type="bibtex:topic">metadata[0.8]</field>
	</reference>
	<reference name="www7" src="bibtex:proceedings" src-info="bibtex:line-12083" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>Helen</givenname>
				<surname>Ashman</surname>
			</person>
			<person>
				<givenname>Paul</givenname>
				<surname>Thistlewaite</surname>
			</person>
		</names>
		<date value="1998-04"/>
		<address type="sharef:placePublished">Brisbane, Australia</address>
		<field type="bibtex:index">WWW7</field>
		<title type="sharef:primaryTitle">Seventh International World Wide Web Conference</title>
		<field type="bibtex:topic">www[0.8]</field>
		<identifier type="sharef:uri">http://www7.conf.au/</identifier>
	</reference>
	<reference name="zam99" src="bibtex:inproceedings" src-info="bibtex:line-12099" type="sharef:inproceedings" crossref="www8">
		<names type="sharef:author">
			<person>
				<givenname>Oren</givenname>
				<surname>Zamir</surname>
			</person>
			<person>
				<givenname>Oren</givenname>
				<surname>Etzioni</surname>
			</person>
		</names>
		<pages>283-296</pages>
		<title type="sharef:primaryTitle">Grouper: A Dynamic Clustering Interface to Web Search Results</title>
		<identifier type="sharef:uri" resourceType="text/html">http://www8.org/w8-papers/3a-search-query/dynamic/dynamic.html</identifier>
	</reference>
	<reference name="mar99" src="bibtex:inproceedings" src-info="bibtex:line-12107" type="sharef:inproceedings" crossref="www8">
		<names type="sharef:author">
			<person>
				<givenname>Philippe</givenname>
				<surname>Martin</surname>
			</person>
			<person>
				<givenname>Peter</givenname>
				<surname>Eklund</surname>
			</person>
		</names>
		<pages>325-341</pages>
		<title type="sharef:primaryTitle">Embedding Knowledge in Web documents</title>
		<field type="bibtex:topic">html[0.7] cg[0.8]</field>
	</reference>
	<reference name="gro99" src="bibtex:inproceedings" src-info="bibtex:line-12115" type="sharef:inproceedings" crossref="www8">
		<names type="sharef:author">
			<person>
				<givenname>Kaj</givenname>
				<surname>Grønbæk</surname>
			</person>
			<person>
				<givenname>Lennert</givenname>
				<surname>Sloth</surname>
			</person>
			<person>
				<givenname>Peter</givenname>
				<surname>Ørbæk</surname>
			</person>
		</names>
		<pages>253-267</pages>
		<title type="sharef:primaryTitle">Webvise: Browser and Proxy Support for Open Hypermedia Structuring Mechanisms on the World Wide Web</title>
		<field type="bibtex:topic">webvise[1]</field>
	</reference>
	<reference name="sta99" src="bibtex:inproceedings" src-info="bibtex:line-12123" type="sharef:inproceedings" crossref="www8">
		<names type="sharef:author">
			<person>
				<givenname>Dominic</givenname>
				<surname>Stanyer</surname>
			</person>
			<person>
				<givenname>Rob</givenname>
				<surname>Procter</surname>
			</person>
		</names>
		<field type="bibtex:index">WWW, usability, links</field>
		<pages>455-466</pages>
		<title type="sharef:primaryTitle">Improving Web Usability with the Link Lens</title>
	</reference>
	<reference name="abr99" src="bibtex:inproceedings" src-info="bibtex:line-12131" type="sharef:inproceedings" crossref="www8">
		<names type="sharef:author">
			<person>
				<givenname>Marc</givenname>
				<surname>Abrams</surname>
			</person>
			<person>
				<givenname>Constantinos</givenname>
				<surname>Phanouriou</surname>
			</person>
			<person>
				<givenname>Alan L.</givenname>
				<surname>Batongbacal</surname>
			</person>
			<person>
				<givenname>Stephen M.</givenname>
				<surname>Williams</surname>
			</person>
			<person>
				<givenname>Jonathan E.</givenname>
				<surname>Shuster</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Today's Internet appliances feature user interface technologies almost unknown a few years ago: touch screens, styli, handwriting and voice recognition, speech synthesis, tiny screens, and more. This richness creates problems. First, different appliances use different languages: WML for cell phones; SpeechML, JSML, and VoxML for voice enabled devices such as phones; HTML and XUL for desktop computers, and so on. Thus, developers must maintain multiple source code families to deploy interfaces to one information system on multiple appliances. Second, user interfaces differ dramatically in complexity (e.g, PC versus cell phone interfaces). Thus, developers must also manage interface content. Third, developers risk writing appliance-specific interfaces for an appliance that might not be on the market tomorrow. A solution is to build interfaces with a single, universal language free of assumptions about appliances and interface technology. This paper introduces such a language, the User Interface Markup Language (UIML), an XML-compliant language. UIML insulates the interface designer from the peculiarities of different appliances through style sheets. A measure of the power of UIML is that it can replace hand-coding of Java AWT or Swing user interfaces.</p>
			</richtext>
		</abstract>
		<pages>1695-1708</pages>
		<title type="sharef:primaryTitle">UIML: An Appliance-Independent XML User Interface Language</title>
		<field type="bibtex:topic">uiml[0.9]</field>
		<identifier type="sharef:uri" resourceType="text/html">http://www8.org/w8-papers/5b-hypertext-media/uiml/uiml.html</identifier>
	</reference>
	<reference name="www8" src="bibtex:proceedings" src-info="bibtex:line-12141" type="sharef:proceedings">
		<date value="1999-05"/>
		<address type="sharef:placePublished">Toronto, Canada</address>
		<field type="bibtex:index">WWW8</field>
		<identifier type="sharef:isbn">0444502645</identifier>
		<field type="bibtex:key">Eighth International World Wide Web Conference</field>
		<publisher>Elsevier</publisher>
		<title type="sharef:primaryTitle">Eighth International World Wide Web Conference</title>
		<field type="bibtex:topic">www[0.8]</field>
		<identifier type="sharef:uri">http://www8.org</identifier>
	</reference>
	<reference name="bha00a" src="bibtex:inproceedings" src-info="bibtex:line-12159" type="sharef:inproceedings" crossref="www9">
		<names type="sharef:author">
			<person>
				<givenname>Krishna</givenname>
				<surname>Bharat</surname>
			</person>
		</names>
		<pages>493-501</pages>
		<title type="sharef:primaryTitle">SearchPad: Explicit Capture of Search Context to Support Web Search</title>
		<field type="bibtex:topic">searchpad[1]</field>
		<identifier type="sharef:uri" resourceType="text/html">http://www9.org/w9cdrom/173/173.html</identifier>
	</reference>
	<reference name="phe00" src="bibtex:inproceedings" src-info="bibtex:line-12168" type="sharef:inproceedings" crossref="www9">
		<names type="sharef:author">
			<person>
				<givenname>Thomas Arthur</givenname>
				<surname>Phelps</surname>
			</person>
			<person>
				<givenname>Robert</givenname>
				<surname>Wilensky</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Several types of existing and next-generation hypertext functionality, including external hyperlinks, annotations, and transclusions, rely on references to locations within another resource. If the document domain cannot guarantee referential integrity, but rather is more like the World Wide Web, in which documents change regularly and without notification, potentially invalidating internal location references, it is crucial to build robustness into the intra-document location resolution mechanism, so that locations continue to function even as documents change chaotically. This paper aims to begin a process to evolve a standard for (normative) robust location descriptors and (non-normative) reattachment algorithms. We discuss criteria for evaluating the robustness of an intra-document location mechanism. Then we describe robust locations, an approach we believe meets these criteria. Robust locations include a standard minimal location descriptor and a recommended reattachment algorithm. We also suggest what can be done when the changes are so great that location resolution is problematic. Finally, we describe the implementation of robust locations within the Multivalent Document system.</p>
			</richtext>
		</abstract>
		<pages>105-118</pages>
		<title type="sharef:primaryTitle">Robust Intra-document Locations</title>
		<identifier type="sharef:uri" resourceType="text/html">http://www9.org/w9cdrom/312/312.html</identifier>
	</reference>
	<reference name="gir00" src="bibtex:inproceedings" src-info="bibtex:line-12177" type="sharef:inproceedings" crossref="www9">
		<names type="sharef:author">
			<person>
				<givenname>Marc</givenname>
				<surname>Girardot</surname>
			</person>
			<person>
				<givenname>Neel</givenname>
				<surname>Sundaresan</surname>
			</person>
		</names>
		<pages>747-765</pages>
		<title type="sharef:primaryTitle">Millau: An Encoding Format for Efficient Representation and Exchange of XML over the Web</title>
		<field type="bibtex:topic">millau[1]</field>
		<identifier type="sharef:uri" resourceType="text/html">http://www9.org/w9cdrom/154/154.html</identifier>
	</reference>
	<reference name="wei00" src="bibtex:inproceedings" src-info="bibtex:line-12186" type="sharef:inproceedings" crossref="www9">
		<names type="sharef:author">
			<person>
				<givenname>Harald</givenname>
				<surname>Weinreich</surname>
			</person>
			<person>
				<givenname>Winfried</givenname>
				<surname>Lamersdorf</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>This paper discusses methods to generate and display automatically additional hyperlink information to the users of the World Wide Web. Current Web browsers make it hard to predict what will happen if a link is being followed: users get different information than they expect, a new window may be opened, a download starts, or the destination object is just not available. Instead of giving an appropriate notification in advance, users have to follow a link, check whether the document contains the expected information, get back, try another link etc. However, usually it is possible to obtain additional hyperlink information from several sources like link anchor tags, the user's history and web servers. Furthermore, with little enhancements, Web servers may include even more additional information to the hyperlinks in Web documents. These can be displayed before users select a link to improve navigation and reduce the cognitive overhead. In this paper several types of Web hyperlink information are listed, potential methods to present these facts are compared, the prototype implementation of the proposed concept — called by us HyperScout — is presented, and further developments are discussed.</p>
			</richtext>
		</abstract>
		<pages>403-415</pages>
		<title type="sharef:primaryTitle">Concepts for Improved Visualization of Web Link Attributes</title>
		<identifier type="sharef:uri" resourceType="text/html">http://www1.www9.org/w9cdrom/319/319.html</identifier>
	</reference>
	<reference name="gro00" src="bibtex:inproceedings" src-info="bibtex:line-12195" type="sharef:inproceedings" crossref="www9">
		<names type="sharef:author">
			<person>
				<givenname>Kaj</givenname>
				<surname>Grønbæk</surname>
			</person>
			<person>
				<givenname>Lennert</givenname>
				<surname>Sloth</surname>
			</person>
			<person>
				<givenname>Niels Olof</givenname>
				<surname>Bouvin</surname>
			</person>
		</names>
		<pages>553-566</pages>
		<title type="sharef:primaryTitle">Open Hypermedia as User Controlled Meta Data for the Web</title>
		<field type="bibtex:topic">webvise[0.9]</field>
		<identifier type="sharef:uri" resourceType="text/html">http://www9.org/w9cdrom/183/183.html</identifier>
	</reference>
	<reference name="kri00" src="bibtex:inproceedings" src-info="bibtex:line-12204" type="sharef:inproceedings" crossref="www9">
		<names type="sharef:author">
			<person>
				<givenname>Balachander</givenname>
				<surname>Krishnamurthy</surname>
			</person>
			<person>
				<givenname>Craig E.</givenname>
				<surname>Wills</surname>
			</person>
		</names>
		<field type="bibtex:index">WWW, HTTP, PRO-COW</field>
		<pages>17-32</pages>
		<title type="sharef:primaryTitle">Analyzing Factors That Influence End-to-End Web Performance</title>
		<identifier type="sharef:uri" resourceType="text/html">http://www9.org/w9cdrom/371/371.html</identifier>
	</reference>
	<reference name="cer00" src="bibtex:inproceedings" src-info="bibtex:line-12213" type="sharef:inproceedings" crossref="www9">
		<names type="sharef: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>
		</names>
		<title type="sharef:primaryTitle">Web Modeling Language (WebML): A Modeling Language for Designing Web Sites</title>
		<field type="bibtex:topic">webml[1]</field>
		<identifier type="sharef:uri" resourceType="text/html">http://www9.org/w9cdrom/177/177.html</identifier>
	</reference>
	<reference name="bro00" src="bibtex:inproceedings" src-info="bibtex:line-12221" type="sharef:inproceedings" crossref="www9">
		<names type="sharef:author">
			<person>
				<givenname>Andrei</givenname>
				<surname>Broder</surname>
			</person>
			<person>
				<givenname>Ravi</givenname>
				<surname>Kumar</surname>
			</person>
			<person>
				<givenname>Farzin</givenname>
				<surname>Maghoul</surname>
			</person>
			<person>
				<givenname>Prabhakar</givenname>
				<surname>Raghavan</surname>
			</person>
			<person>
				<givenname>Sridhar</givenname>
				<surname>Rajagopalan</surname>
			</person>
			<person>
				<givenname>Raymie</givenname>
				<surname>Stata</surname>
			</person>
			<person>
				<givenname>Andrew</givenname>
				<surname>Tomkins</surname>
			</person>
			<person>
				<givenname>Janet L.</givenname>
				<surname>Wiener</surname>
			</person>
		</names>
		<field type="bibtex:index">WWW, hypermedia</field>
		<pages>309-320</pages>
		<title type="sharef:primaryTitle">Graph structure in the Web</title>
		<identifier type="sharef:uri" resourceType="text/html">http://www9.org/w9cdrom/160/160.html</identifier>
	</reference>
	<reference name="fer00" src="bibtex:inproceedings" src-info="bibtex:line-12230" type="sharef:inproceedings" crossref="www9">
		<names type="sharef:author">
			<person>
				<givenname>Mary F.</givenname>
				<surname>Fernández</surname>
			</person>
			<person>
				<givenname>Wang-Chiew</givenname>
				<surname>Tan</surname>
			</person>
			<person>
				<givenname>Dan</givenname>
				<surname>Suciu</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>XML is the standard format for data exchange between inter-enterprise applications on the Internet. To facilitate data exchange, industry groups define public document type definitions (DTDs) that specify the format of the XML data to be exchanged between their applications. In this paper, we address the problem of automating the conversion of relational data into XML. We describe SilkRoute, a general, dynamic, and efficient tool for viewing and querying relational data in XML. SilkRoute is general, because it can express mappings of relational data into XML that conforms to arbitrary DTDs. We call these mappings views. Applications express the data they need as an XML-QL query over the view. SilkRoute is dynamic, because it only materializes the fragment of an XML view needed by an application, and it is efficient, because it fully exploits the underlying RDBMs query engine whenever data items in an XML view need to be materialized.</p>
			</richtext>
		</abstract>
		<pages>723-745</pages>
		<title type="sharef:primaryTitle">SilkRoute: Trading between Relations and XML</title>
		<identifier type="sharef:uri" resourceType="text/html">http://www9.org/w9cdrom/202/202.html</identifier>
	</reference>
	<reference name="www9" src="bibtex:proceedings" src-info="bibtex:line-12239" type="sharef:proceedings">
		<date value="2000-05"/>
		<address type="sharef:placePublished">Amsterdam, Netherlands</address>
		<field type="bibtex:index">WWW9</field>
		<identifier type="sharef:isbn">0444505156</identifier>
		<field type="bibtex:key">Ninth International World Wide Web Conference</field>
		<publisher>Elsevier</publisher>
		<title type="sharef:primaryTitle">Ninth International World Wide Web Conference</title>
		<field type="bibtex:topic">www[0.8]</field>
		<identifier type="sharef:uri">http://www9.org</identifier>
	</reference>
	<reference name="kno01c" src="bibtex:inproceedings" src-info="bibtex:line-12258" type="sharef:inproceedings" crossref="www10">
		<names type="sharef:author">
			<person>
				<givenname>Craig A.</givenname>
				<surname>Knoblock</surname>
			</person>
			<person>
				<givenname>Steven</givenname>
				<surname>Minton</surname>
			</person>
			<person>
				<givenname>José Luis</givenname>
				<surname>Ambite</surname>
			</person>
			<person>
				<givenname>Maria</givenname>
				<surname>Muslea</surname>
			</person>
			<person>
				<givenname>Jean</givenname>
				<surname>Oh</surname>
			</person>
			<person>
				<givenname>Martin</givenname>
				<surname>Frank</surname>
			</person>
		</names>
		<pages>697-707</pages>
		<title type="sharef:primaryTitle">Mixed-Initiative, Multi-Source Information Assistants</title>
		<identifier type="sharef:uri" resourceType="text/html">http://www10.org/cdrom/papers/515/index.html</identifier>
	</reference>
	<reference name="kah01" src="bibtex:inproceedings" src-info="bibtex:line-12266" type="sharef:inproceedings" crossref="www10">
		<names type="sharef:author">
			<person>
				<givenname>José</givenname>
				<surname>Kahan</surname>
			</person>
			<person>
				<givenname>Marja-Riitta</givenname>
				<surname>Koivunen</surname>
			</person>
			<person>
				<givenname>Eric</givenname>
				<surname>Prud'Hommeaux</surname>
			</person>
			<person>
				<givenname>Ralph R.</givenname>
				<surname>Swick</surname>
			</person>
		</names>
		<pages>623-632</pages>
		<title type="sharef:primaryTitle">Annotea: An Open RDF Infrastructure for Shared Web Annotations</title>
		<field type="bibtex:topic">annotea[1]</field>
		<identifier type="sharef:uri" resourceType="text/html">http://www10.org/cdrom/papers/488/index.html</identifier>
	</reference>
	<reference name="agr01" src="bibtex:inproceedings" src-info="bibtex:line-12275" type="sharef:inproceedings" crossref="www10">
		<names type="sharef:author">
			<person>
				<givenname>Rakesh</givenname>
				<surname>Agrawal</surname>
			</person>
			<person>
				<givenname>Roberto J.</givenname>
				<surname>Bayardo</surname>
			</person>
			<person>
				<givenname>Daniel</givenname>
				<surname>Gruhl</surname>
			</person>
			<person>
				<givenname>Spiros</givenname>
				<surname>Papadimitriou</surname>
			</person>
		</names>
		<pages>355-365</pages>
		<title type="sharef:primaryTitle">Vinci: A Service-Oriented Architecture for Rapid Development of Web Applications</title>
		<field type="bibtex:topic">xtalk[1]</field>
		<identifier type="sharef:uri" resourceType="text/html">http://www10.org/cdrom/papers/506/index.html</identifier>
		<identifier type="sharef:uri" resourceType="text/html">http://www.almaden.ibm.com/cs/people/bayardo/vinci/vinci.html</identifier>
	</reference>
	<reference name="sun01" src="bibtex:inproceedings" src-info="bibtex:line-12285" type="sharef:inproceedings" crossref="www10">
		<names type="sharef:author">
			<person>
				<givenname>Neel</givenname>
				<surname>Sundaresan</surname>
			</person>
			<person>
				<givenname>Reshad</givenname>
				<surname>Moussa</surname>
			</person>
		</names>
		<pages>366-375</pages>
		<title type="sharef:primaryTitle">Algorithms and Programming Models for Efficient Representation of XML for Internet Applications</title>
		<field type="bibtex:topic">millau[1] sxml[1] sdom[1] sas[1]</field>
		<identifier type="sharef:uri" resourceType="text/html">http://www10.org/cdrom/papers/542/index.html</identifier>
	</reference>
	<reference name="san01" src="bibtex:inproceedings" src-info="bibtex:line-12294" type="sharef:inproceedings" crossref="www10">
		<names type="sharef:author">
			<person>
				<givenname>Elmer S.</givenname>
				<surname>Sandvad</surname>
			</person>
			<person>
				<givenname>Kaj</givenname>
				<surname>Grønbæk</surname>
			</person>
			<person>
				<givenname>Lennert</givenname>
				<surname>Sloth</surname>
			</person>
			<person>
				<givenname>Jørgen Lindskov</givenname>
				<surname>Knudsen</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>This paper presents a guided tour system for the WWW. It is a module for the Webvise open hypermedia system that implements the ideas of trails and guided tours, originating from the hypertext field. Webvise appears as an open hypermedia helper application to the user and stores the guided tours in an XML format called OHIF separated from the WWW documents included in the tour. The main advantages of the system are: (1) a browser independent format in terms of HTML and PNG-based image maps for reading the guided tours; (2) support for a familiar metaphor namely, a metro route map; (3) overview maps and route maps with indication of which stations of a tour have been visited; and finally (4) support for arbitrary web pages as stations on the tour. The paper discusses the Webvise Guided Tour System and illustrates its use in a digital library portal. The system is compared to other recent Web-based guided tour systems, and it is argued that Webvise Guided Tour System solves a number of prior system problems.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/371920.372079</identifier>
		<pages>326-333</pages>
		<title type="sharef:primaryTitle">A Metro Map Metaphor for Guided Tours on the Web: The Webvise Guided Tour System</title>
		<identifier type="sharef:uri" resourceType="text/html">http://www10.org/cdrom/papers/511/index.html</identifier>
	</reference>
	<reference name="sri01" src="bibtex:inproceedings" src-info="bibtex:line-12304" type="sharef:inproceedings" crossref="www10">
		<names type="sharef:author">
			<person>
				<givenname>Ramakrishnan</givenname>
				<surname>Srikant</surname>
			</person>
			<person>
				<givenname>Yinghui</givenname>
				<surname>Yang</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Many websites have a hierarchical organization of content. This organization may be quite different from the organization expected by visitors to the website. In particular, it is often unclear where a specific document is located. In this paper, we propose an algorithm to automatically find pages in a website whose location is different from where visitors expect to find them. The key insight is that visitors will backtrack if they do not find the information where they expect it: the point from where they backtrack is the expected location for the page. We present an algorithm for discovering such expected locations that can handle page caching by the browser. Expected locations with a significant number of hits are then presented to the website administrator. We also present algorithms for selecting expected locations (for adding navigation links) to optimize the benefit to the website or the visitor. We ran our algorithm on the Wharton business school website and found that even on this small website, there were many pages with expected locations different from their actual location.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/371920.372097</identifier>
		<pages>430-437</pages>
		<title type="sharef:primaryTitle">Mining Web Logs to Improve Website Organization</title>
		<identifier type="sharef:uri" resourceType="text/html">http://www10.org/cdrom/papers/345/index.html</identifier>
	</reference>
	<reference name="wil01d" src="bibtex:inproceedings" src-info="bibtex:line-12314" type="sharef:inproceedings" crossref="www10p">
		<names type="sharef:author">
			<person>
				<givenname>Marcel</givenname>
				<surname>Dasen</surname>
			</person>
			<person>
				<givenname>Erik</givenname>
				<surname>Wilde</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Search engines play a crucial role in the Web. Without search engines large parts of the Web becomes inaccessible for the majority of users. Search engines can make new and smaller sites accessible at low cost. Without them, other media, such as Television, would be needed to advertise the existence new site on the Web, only large commercial sites can follow this path. The Web would be endangered to become dominated by a few, well known sites. A crucial problem of search engines is to keep their index up-to-date. Especially if the index grows, the effort needed to update the index increases, since Web documents are dynamic and thus already stored data becomes obsolete. There have been various attempts to monitor the evolvement of the Web. However, we believe, that change model used in prior work over-estimates the rate of change due to an inadequate change model. Our change model has been adapted from the information retrieval field to distinguish index relevant changes from irrelevant modifications in Web documents, e.g. simple spelling corrections or dynamic advertisement links. We have monitored multiple smaller collections of documents over a time period of six month to measure the documents change.</p>
			</richtext>
		</abstract>
		<pages>202-203</pages>
		<title type="sharef:primaryTitle">Keeping Web Indices up-to-date</title>
		<identifier type="sharef:uri">http://dret.net/netdret/publications#wil01d</identifier>
	</reference>
	<reference name="wil01e" src="bibtex:inproceedings" src-info="bibtex:line-12323" type="sharef:inproceedings" crossref="www10p">
		<names type="sharef:author">
			<person>
				<givenname>Luca</givenname>
				<surname>Previtali</surname>
			</person>
			<person>
				<givenname>Brenno</givenname>
				<surname>Lurati</surname>
			</person>
			<person>
				<givenname>Erik</givenname>
				<surname>Wilde</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>BibTeXML is an XML representation of BibTeX data. It can be used to represent bibliographic data in XML. The advantage of BibTeXML over BibTeX's native syntax is that it can be easily managed using standard XML tools (in particular, XSLT style sheets), while native BibTeX data can only be manipulated using specialized tools.</p>
			</richtext>
		</abstract>
		<pages>64-65</pages>
		<title type="sharef:primaryTitle">BibTeXML: An XML Representation of BibTeX</title>
		<field type="bibtex:topic">bibtex[0.8] bibtexml[1]</field>
		<identifier type="sharef:uri">http://dret.net/netdret/publications#wil01e</identifier>
	</reference>
	<reference name="bar01" src="bibtex:inproceedings" src-info="bibtex:line-12333" type="sharef:inproceedings" crossref="www10p">
		<names type="sharef:author">
			<person>
				<givenname>Judit</givenname>
				<surname>Bar-Ilan</surname>
			</person>
		</names>
		<pages>138-139</pages>
		<title type="sharef:primaryTitle">Methods for Measuring Search Engine Performance over Time</title>
		<identifier type="sharef:uri" resourceType="application/pdf">http://www10.org/cdrom/posters/1018.pdf</identifier>
	</reference>
	<reference name="car01" src="bibtex:inproceedings" src-info="bibtex:line-12341" type="sharef:inproceedings" crossref="www10">
		<names type="sharef:author">
			<person>
				<givenname>Leslie A.</givenname>
				<surname>Carr</surname>
			</person>
			<person>
				<givenname>Sean</givenname>
				<surname>Bechhofer</surname>
			</person>
			<person>
				<givenname>Carole</givenname>
				<surname>Goble</surname>
			</person>
			<person>
				<givenname>Wendy</givenname>
				<surname>Hall</surname>
			</person>
		</names>
		<pages>334-342</pages>
		<title type="sharef:primaryTitle">Conceptual Linking: Ontology-based Open Hypermedia</title>
		<field type="bibtex:topic">ohs[0.8]</field>
		<identifier type="sharef:uri" resourceType="text/html">http://www10.org/cdrom/papers/246/index.html</identifier>
	</reference>
	<reference name="www10p" src="bibtex:proceedings" src-info="bibtex:line-12350" type="sharef:proceedings">
		<date value="2001-05"/>
		<address type="sharef:placePublished">Hong Kong</address>
		<field type="bibtex:index">WWW10</field>
		<field type="bibtex:key">Tenth International World Wide Web Conference Posters</field>
		<publisher>ACM Press</publisher>
		<title type="sharef:primaryTitle">Tenth International World Wide Web Conference Posters</title>
		<field type="bibtex:topic">www[0.8]</field>
		<identifier type="sharef:uri" resourceType="text/html">http://www10.org/cdrom/posters/frame.html</identifier>
	</reference>
	<reference name="www10" src="bibtex:proceedings" src-info="bibtex:line-12362" type="sharef:proceedings">
		<date value="2001-05"/>
		<address type="sharef:placePublished">Hong Kong</address>
		<field type="bibtex:index">WWW10</field>
		<field type="bibtex:key">Tenth International World Wide Web Conference</field>
		<publisher>ACM Press</publisher>
		<title type="sharef:primaryTitle">Tenth International World Wide Web Conference</title>
		<field type="bibtex:topic">www[0.8]</field>
		<identifier type="sharef:uri" resourceType="text/html">http://www10.org/cdrom/papers/frame.html</identifier>
	</reference>
	<reference name="flo02" src="bibtex:inproceedings" src-info="bibtex:line-12380" type="sharef:inproceedings" crossref="www2002">
		<names type="sharef:author">
			<person>
				<givenname>Daniela</givenname>
				<surname>Florescu</surname>
			</person>
			<person>
				<givenname>Andreas</givenname>
				<surname>Grünhagen</surname>
			</person>
			<person>
				<givenname>Donald</givenname>
				<surname>Kossmann</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>We present an XML programming language specially designed for the implementation of Web services. XL is portable and fully compliant with W3C standards such as XQuery, XML Protocol, and XML Schema. One of the key features of XL is that it allows programmers to concentrate on the logic of their application. XL provides high-level and declarative constructs for actions which are typically carried out in the implementation of a Web service; e.g., logging, error handling, retry of actions, workload management, events, etc. Issues such as performance tuning (e.g., caching, horizontal partitioning, etc.) should be carried out automatically by an implementation of the language. This way, the productivity of the programmers, the ability of evolution of the programs, and the chances to achieve good performance are substantially enhanced.</p>
			</richtext>
		</abstract>
		<title type="sharef:primaryTitle">XL: An XML Programming Language for Web Service Specification and Composition</title>
		<field type="bibtex:topic">xl[0.9]</field>
		<identifier type="sharef:uri" resourceType="text/html">http://www2002.org/CDROM/refereed/481/index.html</identifier>
	</reference>
	<reference name="han02c" src="bibtex:inproceedings" src-info="bibtex:line-12389" type="sharef:inproceedings" crossref="www2002">
		<names type="sharef:author">
			<person>
				<givenname>Siegfried</givenname>
				<surname>Handschuh</surname>
			</person>
			<person>
				<givenname>Steffen</givenname>
				<surname>Staab</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Richly interlinked, machine-understandable data constitute the basis for the Semantic Web. We provide a framework, CREAM, that allows for creation of metadata. While the annotation mode of CREAM allows to create metadata for existing web pages, the authoring mode lets authors create metadata — almost for free — while putting together the content of a page. As a particularity of our framework, CREAM allows to create relational metadata, i.e. metadata that instantiate interrelated definitions of classes in a domain ontology rather than a comparatively rigid template-like schema as Dublin Core. We discuss some of the requirements one has to meet when developing such an ontology-based framework, e.g. the integration of a metadata crawler, inference services, document management and a meta-ontology, and describe its implementation, viz. Ont-O-Mat, a component-based, ontology-driven Web page authoring and annotation tool.</p>
			</richtext>
		</abstract>
		<title type="sharef:primaryTitle">Authoring and Annotation of Web Pages in CREAM</title>
		<field type="bibtex:topic">cream[1]</field>
		<identifier type="sharef:uri">http://www2002.org/CDROM/refereed/506/</identifier>
	</reference>
	<reference name="bou02" src="bibtex:inproceedings" src-info="bibtex:line-12398" type="sharef:inproceedings" crossref="www2002">
		<names type="sharef:author">
			<person>
				<givenname>Niels Olof</givenname>
				<surname>Bouvin</surname>
			</person>
			<person>
				<givenname>Polle T.</givenname>
				<surname>Zellweger</surname>
			</person>
			<person>
				<givenname>Kaj</givenname>
				<surname>Grønbæk</surname>
			</person>
			<person>
				<givenname>Jock D.</givenname>
				<surname>Mackinlay</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>The Fluid Documents project has developed various research prototypes that show that powerful annotation techniques based on animated typographical changes can help readers utilize annotations more effectively. Our recently-developed Fluid Open Hypermedia prototype supports the authoring and browsing of fluid annotations on third-party Web pages. This prototype is an extension of the Arakne Environment, an open hypermedia application that can augment Web pages with externally stored hypermedia structures. This paper describes how various Web standards, including DOM, CSS, XLink, XPointer, and RDF, can be used and extended to support fluid annotations.</p>
			</richtext>
		</abstract>
		<pages>160-171</pages>
		<title type="sharef:primaryTitle">Fluid Annotations Through Open Hypermedia: Using and Extending Emerging Web Standards</title>
		<field type="bibtex:topic">arakne[0.9] fluidannotations[0.9]</field>
		<identifier type="sharef:uri" resourceType="text/html">http://www2002.org/CDROM/refereed/656/index.html</identifier>
	</reference>
	<reference name="hav02b" src="bibtex:inproceedings" src-info="bibtex:line-12408" type="sharef:inproceedings" crossref="www2002">
		<names type="sharef:author">
			<person>
				<givenname>Taher H.</givenname>
				<surname>Haveliwala</surname>
			</person>
			<person>
				<givenname>Aristades</givenname>
				<surname>Gionis</surname>
			</person>
			<person>
				<givenname>Dan</givenname>
				<surname>Klein</surname>
			</person>
			<person>
				<givenname>Piotr</givenname>
				<surname>Indyk</surname>
			</person>
		</names>
		<pages>432-442</pages>
		<title type="sharef:primaryTitle">Evaluating Strategies for Similarity Search on the Web</title>
		<identifier type="sharef:uri" resourceType="text/html">http://www2002.org/CDROM/refereed/75/index.html</identifier>
		<identifier type="sharef:uri">http://dbpubs.stanford.edu/pub/2002-7</identifier>
	</reference>
	<reference name="ko02" src="bibtex:inproceedings" src-info="bibtex:line-12417" type="sharef:inproceedings" crossref="www2002">
		<names type="sharef:author">
			<person>
				<givenname>In-Young</givenname>
				<surname>Ko</surname>
			</person>
			<person>
				<givenname>Ke-Thia</givenname>
				<surname>Yao</surname>
			</person>
			<person>
				<givenname>Robert</givenname>
				<surname>Neches</surname>
			</person>
		</names>
		<pages>355-365</pages>
		<title type="sharef:primaryTitle">Dynamic Coordination of Information Management Services for Processing Dynamic Web Content</title>
		<identifier type="sharef:uri" resourceType="text/html">http://www2002.org/CDROM/refereed/613/index.html</identifier>
	</reference>
	<reference name="leo02" src="bibtex:inproceedings" src-info="bibtex:line-12425" type="sharef:inproceedings" crossref="www2002">
		<names type="sharef:author">
			<person>
				<givenname>Jennifer</givenname>
				<surname>Leopold</surname>
			</person>
			<person>
				<givenname>Meg</givenname>
				<surname>Heimovics</surname>
			</person>
			<person>
				<givenname>Tyler</givenname>
				<surname>Palmer</surname>
			</person>
		</names>
		<pages>221-231</pages>
		<title type="sharef:primaryTitle">WebFormulate: A Web-Based Visual Continual Query System</title>
		<identifier type="sharef:uri" resourceType="text/html">http://www2002.org/CDROM/refereed/423/index.html</identifier>
	</reference>
	<reference name="jai02" src="bibtex:inproceedings" src-info="bibtex:line-12433" type="sharef:inproceedings" crossref="www2002">
		<names type="sharef:author">
			<person>
				<givenname>Sushant</givenname>
				<surname>Jain</surname>
			</person>
			<person>
				<givenname>Ratul</givenname>
				<surname>Mahajan</surname>
			</person>
			<person>
				<givenname>Dan</givenname>
				<surname>Suciu</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>We present an algorithm for translating XSLT programs into SQL. Our context is that of virtual XML publishing, in which a single XML view is defined from a relational database, and subsequently queried with XSLT programs. Each XSLT program is translated into a single SQL query and run entirely in the database engine. Our translation works for a large fragment of XSLT, which we define, that includes descendant/ancestor axis, recursive templates, modes, parameters, and aggregates. We put considerable effort in generating correct and efficient SQL queries and describe several optimization techniques to achieve this efficiency. We have tested our system on all 22 SQL queries of the TPC-H database benchmark which we represented in XSLT and then translated back to SQL using our translator.</p>
			</richtext>
		</abstract>
		<pages>616-625</pages>
		<title type="sharef:primaryTitle">Translating XSLT Programs to Efficient SQL Queries</title>
		<field type="bibtex:topic">xslt1[0.7] sql[0.7] xpath1[0.7]</field>
		<identifier type="sharef:uri" resourceType="text/html">http://www2002.org/CDROM/refereed/226/index.html</identifier>
	</reference>
	<reference name="hav02a" src="bibtex:inproceedings" src-info="bibtex:line-12443" type="sharef:inproceedings" crossref="www2002">
		<names type="sharef:author">
			<person>
				<givenname>Taher H.</givenname>
				<surname>Haveliwala</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>In the original PageRank algorithm for improving the ranking of search-query results, a single PageRank vector is computed, using the link structure of the Web, to capture the relative "importance" of Web pages, independent of any particular search query. To yield more accurate search results, we propose computing a set of PageRank vectors, biased using a set of representative topics, to capture more accurately the notion of importance with respect to a particular topic. By using these (precomputed) biased PageRank vectors to generate query-specific importance scores for pages at query time, we show that we can generate more accurate rankings than with a single, generic PageRank vector. For ordinary keyword search queries, we compute the topic-sensitive PageRank scores for pages satisfying the query using the topic of the query keywords. For searches done in context (e.g., when the search query is performed by highlighting words in a Web page), we compute the topic-sensitive PageRank scores using the topic of the context in which the query appeared.</p>
			</richtext>
		</abstract>
		<pages>517-526</pages>
		<title type="sharef:primaryTitle">Topic-Sensitive PageRank</title>
		<field type="bibtex:topic">pagerank[0.8]</field>
		<identifier type="sharef:uri" resourceType="text/html">http://www2002.org/CDROM/refereed/127/index.html</identifier>
	</reference>
	<reference name="doa02" src="bibtex:inproceedings" src-info="bibtex:line-12453" type="sharef:inproceedings" crossref="www2002">
		<names type="sharef:author">
			<person>
				<givenname>AnHai</givenname>
				<surname>Doan</surname>
			</person>
			<person>
				<givenname>Jayant</givenname>
				<surname>Madhavan</surname>
			</person>
			<person>
				<givenname>Pedro</givenname>
				<surname>Domingos</surname>
			</person>
			<person>
				<givenname>Alon</givenname>
				<surname>Halevy</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Ontologies play a prominent role on the Semantic Web. They make possible the widespread publication of machine understandable data, opening myriad opportunities for automated information processing. However, because of the Semantic Web's distributed nature, data on it will inevitably come from many different ontologies. Information processing across ontologies is not possible without knowing the semantic mappings between their elements. Manually finding such mappings is tedious, error-prone, and clearly not possible at the Web scale. Hence, the development of tools to assist in the ontology mapping process is crucial to the success of the Semantic Web. We describe GLUE, a system that employs machine learning techniques to find such mappings. Given two ontologies, for each concept in one ontology GLUE finds the most similar concept in the other ontology. We give well-founded probabilistic definitions to several practical similarity measures, and show that GLUE can work with all of them. This is in contrast to most existing approaches, which deal with a single similarity measure. Another key feature of GLUE is that it uses multiple learning strategies, each of which exploits a different type of information either in the data instances or in the taxonomic structure of the ontologies. To further improve matching accuracy, we extend GLUE to incorporate commonsense knowledge and domain constraints into the matching process. For this purpose, we show that relaxation labeling, a well-known constraint optimization technique used in computer vision and other fields, can be adapted to work efficiently in our context. Our approach is thus distinguished in that it works with a variety of well-defined similarity notions and that it efficiently incorporates multiple types of knowledge. We describe a set of experiments on several real-world domains, and show that GLUE proposes highly accurate semantic mappings.</p>
			</richtext>
		</abstract>
		<pages>662-673</pages>
		<title type="sharef:primaryTitle">Learning to Map between Ontologies on the Semantic Web</title>
		<identifier type="sharef:uri" resourceType="text/html">http://www2002.org/CDROM/refereed/232/index.html</identifier>
	</reference>
	<reference name="sch02" src="bibtex:inproceedings" src-info="bibtex:line-12462" type="sharef:inproceedings" crossref="www2002">
		<names type="sharef:author">
			<person>
				<givenname>Monica C.</givenname>
				<surname>Schraefel</surname>
			</person>
			<person>
				<givenname>Yuxiang</givenname>
				<surname>Zhu</surname>
			</person>
			<person>
				<givenname>David</givenname>
				<surname>Modjeska</surname>
			</person>
			<person>
				<givenname>Daniel</givenname>
				<surname>Wigdor</surname>
			</person>
			<person>
				<givenname>Shengdong</givenname>
				<surname>Zhao</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Hunter Gatherer is an interface that lets Web users carry out three main tasks: (1) collect components from within Web pages; (2) represent those components in a collection; (3) edit those component collections. Our research shows that while the practice of making collections of content from within Web pages is common, it is not frequent, due in large part to poor interaction support in existing tools. We engaged with users in task analysis as well as iterative design reviews in order to understand the interaction issues that are part of within-Web-page collection making and to design an interaction that would support that process. We report here on that design development, as well as on the evaluations of the tool that evolved from that process, and the future work stemming from these results, in which our critical question is: what happens to users' perceptions of web-based resources and their web-based information management practices when they can treat this information as harvestable, recontextualizable data, rather than as fixed pages?</p>
			</richtext>
		</abstract>
		<pages>172-181</pages>
		<title type="sharef:primaryTitle">Hunter Gatherer: Interaction Support for the Creation and Management of Within-Web-Page Collections</title>
		<field type="bibtex:topic">huntergatherer[1]</field>
		<identifier type="sharef:uri" resourceType="text/html">http://www2002.org/CDROM/refereed/130/index.html</identifier>
	</reference>
	<reference name="wil02e" src="bibtex:inproceedings" src-info="bibtex:line-12472" type="sharef:inproceedings" crossref="www2002p">
		<names type="sharef:author">
			<person>
				<givenname>Erik</givenname>
				<surname>Wilde</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>XML itself does not support hypermedia, but the XLink standard has been defined to make XML usable for hypermedia. One of XLink's most interesting features is its support for external links and linkbases, which makes it possible to create links between resources without having to change the resources. In order to use these links, user agents must access linkbases and query them for relevant links, and we present our approach to create a protocol for linkbase access.</p>
			</richtext>
		</abstract>
		<title type="sharef:primaryTitle">Linkbase Access Protocol Design</title>
		<field type="bibtex:topic">xlink[0.7]</field>
		<identifier type="sharef:uri">http://dret.net/netdret/publications#wil02e</identifier>
	</reference>
	<reference name="mil02" src="bibtex:inproceedings" src-info="bibtex:line-12481" type="sharef:inproceedings" crossref="www2002p">
		<names type="sharef:author">
			<person>
				<givenname>Natasa</givenname>
				<surname>Milic-Frayling</surname>
			</person>
			<person>
				<givenname>Ralph</givenname>
				<surname>Sommerer</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>SmartView is a functionality built into a document viewer that performs partitioning of an HTML document content into logical sections that can further be selected by the user and viewed independently from the rest of the document. The SmartView interface enforces the concept of a document by allowing the user to view both the document overview (e.g., a zoomed out version of the document, a document thumbnail(s), etc.) and a detailed view of the selected section of the document. The layout of the detailed view is modified to achieve the presentation that is desired by the user or is optimal for a device. The SmartView functionality is essential in cases when the document layout is optimized for displays of certain size but need to be viewed on smaller devices — a situation that requires significant document scaling and layout changes (e.g., viewing of Web pages on PDAs). It is equally important in instances when only a portion of a document needs to be displayed (e.g., showing a section of a Web page on a large screen). The current implementation of SmartView is compatible with the Microsoft Internet Explorer v.6.0.</p>
			</richtext>
		</abstract>
		<title type="sharef:primaryTitle">SmartView: Flexible Viewing of Web Page Contents</title>
		<identifier type="sharef:uri">http://www2002.org/CDROM/poster/172/</identifier>
	</reference>
	<reference name="www2002p" src="bibtex:proceedings" src-info="bibtex:line-12489" type="sharef:proceedings">
		<date value="2002-05"/>
		<address type="sharef:placePublished">Honolulu, Hawaii</address>
		<field type="bibtex:index">WWW2002</field>
		<field type="bibtex:key">Eleventh International World Wide Web Conference Posters</field>
		<title type="sharef:primaryTitle">Eleventh International World Wide Web Conference Posters</title>
		<field type="bibtex:topic">www[0.8]</field>
		<identifier type="sharef:uri">http://www2002.org/CDROM/refereed/</identifier>
	</reference>
	<reference name="www2002" src="bibtex:proceedings" src-info="bibtex:line-12501" type="sharef:proceedings">
		<date value="2002-05"/>
		<address type="sharef:placePublished">Honolulu, Hawaii</address>
		<field type="bibtex:index">WWW2002</field>
		<field type="bibtex:key">Eleventh International World Wide Web Conference</field>
		<publisher>ACM Press</publisher>
		<title type="sharef:primaryTitle">Eleventh International World Wide Web Conference</title>
		<field type="bibtex:topic">www[0.8]</field>
	</reference>
	<reference name="abe03" src="bibtex:inproceedings" src-info="bibtex:line-12518" type="sharef:inproceedings" crossref="www2003">
		<names type="sharef:author">
			<person>
				<givenname>Karl</givenname>
				<surname>Aberer</surname>
			</person>
			<person>
				<givenname>Philippe</givenname>
				<surname>Cudré-Mauroux</surname>
			</person>
			<person>
				<givenname>Manfred</givenname>
				<surname>Hauswirth</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>This paper describes a novel approach for obtaining semantic interoperability among data sources in a bottom-up, semi-automatic manner without relying on pre-existing, global semantic models. We assume that large amounts of data exist that have been organized and annotated according to local schemas. Seeing semantics as a form of agreement, our approach enables the participating data sources to incrementally develop global agreement in an evolutionary and completely decentralized process that solely relies on pair-wise, local interactions: Participants provide translations between schemas they are interested in and can learn about other translations by routing queries (gossiping). To support the participants in assessing the semantic quality of the achieved agreements we develop a formal framework that takes into account both syntactic and semantic criteria. The assessment process is incremental and the quality ratings are adjusted along with the operation of the system. Ultimately, this process results in global agreement, i.e., the semantics that all participants understand. We discuss strategies to efficiently find translations and provide results from a case study to justify our claims. Our approach applies to any system which provides a communication infrastructure (existing websites or databases, decentralized systems, P2P systems) and offers the opportunity to study semantic interoperability as a global phenomenon in a network of information sharing parties.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">http://doi.acm.org/10.1145/775152.775180</identifier>
		<pages>197-206</pages>
		<title type="sharef:primaryTitle">The Chatty Web: Emergent Semantics Through Gossiping</title>
	</reference>
	<reference name="liu03" src="bibtex:inproceedings" src-info="bibtex:line-12527" type="sharef:inproceedings" crossref="www2003">
		<names type="sharef:author">
			<person>
				<givenname>Bing</givenname>
				<surname>Liu</surname>
			</person>
			<person>
				<givenname>Chee Wee</givenname>
				<surname>Chin</surname>
			</person>
			<person>
				<givenname>Hwee Tou</givenname>
				<surname>Ng</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Traditionally, when one wants to learn about a particular topic, one reads a book or a survey paper. With the rapid expansion of the Web, learning in-depth knowledge about a topic from the Web is becoming increasingly important and popular. This is also due to the Web's convenience and its richness of information. In many cases, learning from the Web may even be essential because in our fast changing world, emerging topics appear constantly and rapidly. There is often not enough time for someone to write a book on such topics. To learn such emerging topics, one can resort to research papers. However, research papers are often hard to understand by non-researchers, and few research papers cover every aspect of the topic. In contrast, many Web pages often contain intuitive descriptions of the topic. To find such Web pages, one typically uses a search engine. However, current search techniques are not designed for in-depth learning. Top ranking pages from a search engine may not contain any description of the topic. Even if they do, the description is usually incomplete since it is unlikely that the owner of the page has good knowledge of every aspect of the topic. In this paper, we attempt a novel and challenging task, mining topic-specific knowledge on the Web. Our goal is to help people learn in-depth knowledge of a topic systematically on the Web. The proposed techniques first identify those sub-topics or salient concepts of the topic, and then find and organize those informative pages, containing definitions and descriptions of the topic and sub-topics, just like those in a book. Experimental results using 28 topics show that the proposed techniques are highly effective.</p>
			</richtext>
		</abstract>
		<pages>251-260</pages>
		<title type="sharef:primaryTitle">Mining Topic-Specific Concepts and Definitions on the Web</title>
		<identifier type="sharef:uri" resourceType="text/html">http://www2003.org/cdrom/papers/refereed/p646/p646-liu-XHTML/p646-liu.html</identifier>
	</reference>
	<reference name="gup03" src="bibtex:inproceedings" src-info="bibtex:line-12536" type="sharef:inproceedings" crossref="www2003">
		<names type="sharef:author">
			<person>
				<givenname>Suhit</givenname>
				<surname>Gupta</surname>
			</person>
			<person>
				<givenname>Gail</givenname>
				<surname>Kaiser</surname>
			</person>
			<person>
				<givenname>David</givenname>
				<surname>Neistadt</surname>
			</person>
			<person>
				<givenname>Peter</givenname>
				<surname>Grimm</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Web pages often contain clutter (such as pop-up ads, unnecessary images and extraneous links) around the body of an article that distracts a user from actual content. Extraction of "useful and relevant" content from web pages has many applications, including cell phone and PDA browsing, speech rendering for the visually impaired, and text summarization. Most approaches to removing clutter or making content more readable involve changing font size or removing HTML and data components such as images, which takes away from a webpage's inherent look and feel. Unlike "Content Reformatting", which aims to reproduce the entire webpage in a more convenient form, our solution directly addresses "Content Extraction". We have developed a framework that employs easily extensible set of techniques that incorporate advantages of previous work on content extraction. Our key insight is to work with the DOM trees, rather than with raw HTML markup. We have implemented our approach in a publicly available Web proxy to extract content from HTML web pages.</p>
			</richtext>
		</abstract>
		<pages>207-214</pages>
		<title type="sharef:primaryTitle">DOM-based Content Extraction of HTML Documents</title>
		<field type="bibtex:topic">dom[0.7] html[0.7]</field>
		<identifier type="sharef:uri" resourceType="text/html">http://www2003.org/cdrom/papers/refereed/p583/p583-gupta.html</identifier>
	</reference>
	<reference name="lim03" src="bibtex:inproceedings" src-info="bibtex:line-12546" type="sharef:inproceedings" crossref="www2003">
		<names type="sharef:author">
			<person>
				<givenname>Lipyeow</givenname>
				<surname>Lim</surname>
			</person>
			<person>
				<givenname>Min</givenname>
				<surname>Wang</surname>
			</person>
			<person>
				<givenname>Sriram</givenname>
				<surname>Padmanabhan</surname>
			</person>
			<person>
				<givenname>Jeffrey Scott</givenname>
				<surname>Vitter</surname>
			</person>
			<person>
				<givenname>Ramesh</givenname>
				<surname>Agarwal</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Recent work on incremental crawling has enabled the indexed document collection of a search engine to be more synchronized with the changing World Wide Web. However, this synchronized collection is not immediately searchable, because the keyword index is rebuilt from scratch less frequently than the collection can be refreshed. An inverted index is usually used to index documents crawled from the web. Complete index rebuild at high frequency is expensive. Previous work on incremental inverted index updates have been restricted to adding and removing documents. Updating the inverted index for previously indexed documents that have changed has not been addressed. In this paper, we propose an efficient method to update the inverted index for previously indexed documents whose contents have changed. Our method uses the idea of landmarks together with the diff algorithm to significantly reduce the number of postings in the inverted index that need to be updated. Our experiments verify that our landmark-diff method results in significant savings in the number of update operations on the inverted index.</p>
			</richtext>
		</abstract>
		<pages>102-111</pages>
		<title type="sharef:primaryTitle">Dynamic Maintenance of Web Indexes Using Landmarks</title>
		<identifier type="sharef:uri" resourceType="text/html">http://www2003.org/cdrom/papers/refereed/p656/p656-lim.html</identifier>
	</reference>
	<reference name="chr03" src="bibtex:inproceedings" src-info="bibtex:line-12555" type="sharef:inproceedings" crossref="www2003">
		<names type="sharef:author">
			<person>
				<givenname>Bent Guldbjerg</givenname>
				<surname>Christensen</surname>
			</person>
			<person>
				<givenname>Frank Allan</givenname>
				<surname>Hansen</surname>
			</person>
			<person>
				<givenname>Niels Olof</givenname>
				<surname>Bouvin</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>This paper evaluates the XLink format in comparison with other linking formats. The comparison is based on Xspect, an implementation of XLink. Xspect handles transformation between an open hypermedia format (OHIF) and XLink, and the paper discusses this isomorphic transformation and generalises it to include another open hypermedia format, FOHM. The Xspect system, based on XSLT and Javascript, provides users with an interface to browse and merge linkbases. Xspect supports navigational hypermedia in the form of links inserted on the fly into Web pages, as well as guided tours presented as SVG. Xspect has two implementations: one server-side and one running on the client. Both implementation provide the user with an interface for the creation of annotations. The main result of the paper is a critique of XLink. XLink is shown to be a format well suited for navigational hypermedia, but lacking in more advanced constructs. More problematic are the issues regarding large-scale use, such as evaluating validity and credibility of linkbases, and ensuring general support for a format as flexible as XLink.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/775152.775222</identifier>
		<pages>490-499</pages>
		<title type="sharef:primaryTitle">Xspect: Bridging Open Hypermedia and XLink</title>
		<field type="bibtex:topic">xlink[0.8] ohif[0.7] xspect[0.9]</field>
		<identifier type="sharef:uri">http://portal.acm.org/citation.cfm?doid=775152.775222</identifier>
	</reference>
	<reference name="ure03" src="bibtex:inproceedings" src-info="bibtex:line-12566" type="sharef:inproceedings" crossref="www2003">
		<names type="sharef:author">
			<person>
				<givenname>Victoria</givenname>
				<surname>Uren</surname>
			</person>
			<person>
				<givenname>Simon</givenname>
				<surname>Buckingham Shum</surname>
			</person>
			<person>
				<givenname>Gangmin</givenname>
				<surname>Li</surname>
			</person>
			<person>
				<givenname>John</givenname>
				<surname>Domingue</surname>
			</person>
			<person>
				<givenname>Enrico</givenname>
				<surname>Motta</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>The World Wide Web is opening up access to documents and data for scholars. However it has not yet impacted on one of the primary activities in research: assessing new findings in the light of current knowledge and debating it with colleagues. The ClaiMaker system uses a directed graph model with similarities to hypertext, in which new ideas are published as nodes, which other contributors can build on or challenge in a variety of ways by linking to them. Nodes and links have semantic structure to facilitate the provision of specialist services for interrogating and visualizing the emerging network. By way of example, this paper is grounded in a ClaiMaker model to illustrate how new claims can be described in this structured way.</p>
			</richtext>
		</abstract>
		<pages>244-250</pages>
		<title type="sharef:primaryTitle">Scholarly Publishing and Argument in Hyperspace</title>
		<field type="bibtex:topic">claimaker[0.9]</field>
		<identifier type="sharef:uri" resourceType="application/pdf">http://kmi.open.ac.uk/publications/papers/kmi-tr-127.pdf</identifier>
		<identifier type="sharef:uri" resourceType="text/html">http://www2003.org/cdrom/papers/refereed/p137/p137-uren.html</identifier>
	</reference>
	<reference name="obe03" src="bibtex:inproceedings" src-info="bibtex:line-12577" type="sharef:inproceedings" crossref="www2003">
		<names type="sharef:author">
			<person>
				<givenname>Hartmut</givenname>
				<surname>Obendorf</surname>
			</person>
			<person>
				<givenname>Harald</givenname>
				<surname>Weinreich</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Links are one of the most important means for navigation in the World Wide Web. However, the visualization of and the interaction with Web links have been scarcely explored, although Links have severe implications on the appearance and usability of Web pages and the World Wide Web as such. This paper presents two studies giving first insights of the effects of link visualization techniques on reading habits and performance. The first user study compares different highlighting techniques for link markers and evaluates their effect on reading performance and user acceptance. The second study examines links-on-demand, links that appear when pressing a dedicated key, and discusses their possible effects on reading and browsing habits. The findings of the conducted studies imply that the standard appearance of link markers has seriously underestimated effects on the usability of Web pages. They can significantly reduce the readability of the text, and alternatives should be carefully considered for the design of future Web browsers.</p>
			</richtext>
		</abstract>
		<pages>736-745</pages>
		<title type="sharef:primaryTitle">Comparing Link Marker Visualization Techniques — Changes in Reading Behavior</title>
		<identifier type="sharef:uri">http://portal.acm.org/citation.cfm?doid=775152.775255</identifier>
		<identifier type="sharef:uri">http://vsys-www.informatik.uni-hamburg.de/publications/viewpub.phtml/119</identifier>
		<identifier type="sharef:uri" resourceType="text/html">http://www2003.org/cdrom/papers/refereed/p391/p391-obendorf.html</identifier>
	</reference>
	<reference name="wil03e" src="bibtex:inproceedings" src-info="bibtex:line-12588" type="sharef:inproceedings" crossref="www2003p">
		<names type="sharef:author">
			<person>
				<givenname>Erik</givenname>
				<surname>Wilde</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>XML documents may contain a large diversity of characters. The Character Repertoire Validation for XML (CRVX) language is a simple schema language for specifying character repertoire constraints. These constraints can be specific for syntax- and/or context-based parts of an XML document. The constraints are based on the character classes introduced by XML Schema's regular expressions.</p>
			</richtext>
		</abstract>
		<title type="sharef:primaryTitle">Character Repertoire Validation for XML Documents</title>
		<field type="bibtex:topic">crvx[0.9]</field>
		<identifier type="sharef:uri">http://dret.net/netdret/publications#wil03e</identifier>
		<identifier type="sharef:uri" resourceType="text/html">http://www2003.org/cdrom/papers/poster/p017/p17-wilde.html</identifier>
	</reference>
	<reference name="wil03f" src="bibtex:inproceedings" src-info="bibtex:line-12598" type="sharef:inproceedings" crossref="www2003p">
		<names type="sharef:author">
			<person>
				<givenname>Erik</givenname>
				<surname>Wilde</surname>
			</person>
			<person>
				<givenname>Kilian</givenname>
				<surname>Stillhard</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>XML Schema is a rather complex schema language, partly because of its inherent complexity, and partly because of its XML syntax. In an effort to reduce the syntactic verboseness and complexity of XML Schema, we designed the XML Schema Compact Syntax (XSCS), a non-XML syntax for XML Schema. XSCS is designed for human users, and transformations from and to XML Schema XML syntax are implemented using Java-based tools.</p>
			</richtext>
		</abstract>
		<title type="sharef:primaryTitle">Making XML Schema Easier to Read and Write</title>
		<field type="bibtex:topic">xscs[0.9]</field>
		<identifier type="sharef:uri">http://dret.net/netdret/publications#wil03f</identifier>
		<identifier type="sharef:uri" resourceType="text/html">http://www2003.org/cdrom/papers/poster/p018/p18-wilde.html</identifier>
	</reference>
	<reference name="wil03g" src="bibtex:inproceedings" src-info="bibtex:line-12608" type="sharef:inproceedings" crossref="www2003p">
		<names type="sharef:author">
			<person>
				<givenname>Erik</givenname>
				<surname>Wilde</surname>
			</person>
			<person>
				<givenname>Martin</givenname>
				<surname>Waldburger</surname>
			</person>
			<person>
				<givenname>Beat</givenname>
				<surname>Krähenmann</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Conference time-tables provide information that is indispensable for all attendees. Since there are a lot of reusable data structures and tasks, we have designed the Conference Time-Table Management (CTTM) system, which is intended to be used as a reusable component in a large diversity of conference Web sites. CTTM features a flexible concept for time-tables and provides users with personalization and notification services.</p>
			</richtext>
		</abstract>
		<title type="sharef:primaryTitle">Conference Time-Table Management</title>
		<field type="bibtex:topic">cttm[0.9]</field>
		<identifier type="sharef:uri">http://dret.net/netdret/publications#wil03g</identifier>
		<identifier type="sharef:uri" resourceType="text/html">http://www2003.org/cdrom/papers/poster/p086/p86-wilde.html</identifier>
	</reference>
	<reference name="ped03" src="bibtex:inproceedings" src-info="bibtex:line-12618" type="sharef:inproceedings" crossref="www2003p">
		<names type="sharef:author">
			<person>
				<givenname>Michael</givenname>
				<surname>Pediaditakis</surname>
			</person>
			<person>
				<givenname>David</givenname>
				<surname>Shrimpton</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>XML languages are increasingly used for representations aimed to XML applications running on a variety of platforms. We have developed an architecture that automatically constructs combinations of XML processing pipelines that produce device specific representations. This is achieved by associating sets of elements and attributes of XML languages to processing pipelines according to platform capabilities.</p>
			</richtext>
		</abstract>
		<title type="sharef:primaryTitle">Device Neutral Pipelined Processing of XML Documents</title>
		<field type="bibtex:topic">xmlpipe[0.9]</field>
		<identifier type="sharef:uri" resourceType="text/html">http://www2003.org/cdrom/papers/poster/p108/p108-Pediaditakis.html</identifier>
	</reference>
	<reference name="lam03" src="bibtex:inproceedings" src-info="bibtex:line-12627" type="sharef:inproceedings" crossref="www2003p">
		<names type="sharef:author">
			<person>
				<givenname>Wai Yeung</givenname>
				<surname>Lam</surname>
			</person>
			<person>
				<givenname>Wilfred Siu Hung</givenname>
				<surname>Ng</surname>
			</person>
			<person>
				<givenname>Peter</givenname>
				<surname>Wood</surname>
			</person>
			<person>
				<givenname>Mark</givenname>
				<surname>Levene</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>We present our development of an XML compression and querying tool, which is called XML Compression and Querying System (XCQ). This system is developed based on a novel technique called DTD Tree and SAX Event Stream Parsing (DSP). This technique is designed for efficient compression of XML documents that conform to a given DTD without involving user expertise. A reasonable compression ratio, which is comparable to that of XMill, is achieved by DSP. The compressed documents in XCQ adopt a partitioned path-based data grouping which supports evaluating queries without running a full decompression. We demonstrate with examples how to query compressed documents in XCQ.</p>
			</richtext>
		</abstract>
		<title type="sharef:primaryTitle">XCQ: XML Compression and Querying System</title>
		<field type="bibtex:topic">xcq[0.9]</field>
		<identifier type="sharef:uri" resourceType="text/html">http://www2003.org/cdrom/papers/poster/p059/WWW2003_Poster_59.html</identifier>
	</reference>
	<reference name="sim03c" src="bibtex:inproceedings" src-info="bibtex:line-12636" type="sharef:inproceedings" crossref="www2003p">
		<names type="sharef:author">
			<person>
				<givenname>Hrvoje</givenname>
				<surname>Šimić</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>This paper introduces a Web site structure model called UriGraph and, using the model, describes several important patterns of site structure. Web site structure is defined as the collective information about the identity, identifier, position and composition of every resource constituting the Web site. UriGraph models the site's resource identifiers and through them the resource identity and composition, and indirectly the resource position. UriGraph is designed specifically for the Web and it is compatible with the current practice. It can be represented graphically and as an XML document.</p>
			</richtext>
		</abstract>
		<title type="sharef:primaryTitle">Modeling Web Site Structure in UriGraph</title>
		<field type="bibtex:topic">uri[0.8]</field>
		<identifier type="sharef:uri" resourceType="text/html">http://www2003.org/cdrom/papers/poster/p328/p328-simic.html</identifier>
	</reference>
	<reference name="www2003p" src="bibtex:proceedings" src-info="bibtex:line-12645" type="sharef:proceedings">
		<date value="2003-05"/>
		<address type="sharef:placePublished">Budapest, Hungary</address>
		<field type="bibtex:index">WWW2003</field>
		<field type="bibtex:key">Twelfth International World Wide Web Conference Posters</field>
		<title type="sharef:primaryTitle">Twelfth International World Wide Web Conference Posters</title>
		<field type="bibtex:topic">www[0.8]</field>
	</reference>
	<reference name="www2003" src="bibtex:proceedings" src-info="bibtex:line-12656" type="sharef:proceedings">
		<date value="2003-05"/>
		<address type="sharef:placePublished">Budapest, Hungary</address>
		<field type="bibtex:index">WWW2003</field>
		<identifier type="sharef:isbn">1581136803</identifier>
		<field type="bibtex:key">Twelfth International World Wide Web Conference</field>
		<publisher>ACM Press</publisher>
		<title type="sharef:primaryTitle">Twelfth International World Wide Web Conference</title>
		<field type="bibtex:topic">www[0.8]</field>
	</reference>
	<reference name="mil04" src="bibtex:inproceedings" src-info="bibtex:line-12674" type="sharef:inproceedings" crossref="www2004">
		<names type="sharef:author">
			<person>
				<givenname>Natasa</givenname>
				<surname>Milic-Frayling</surname>
			</person>
			<person>
				<givenname>Rachel</givenname>
				<surname>Jones</surname>
			</person>
			<person>
				<givenname>Kerry</givenname>
				<surname>Rodden</surname>
			</person>
			<person>
				<givenname>Gavin</givenname>
				<surname>Smyth</surname>
			</person>
			<person>
				<givenname>Alan F.</givenname>
				<surname>Blackwell</surname>
			</person>
			<person>
				<givenname>Ralph</givenname>
				<surname>Sommerer</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>This paper presents the design and user evaluation of SmartBack, a feature that complements the standard Back button by enabling users to jump directly to key pages in their navigation session, making common navigation activities more efficient. Defining key pages was informed by the findings of a user study that involved detailed monitoring of Web usage and analysis of Web browsing in terms of navigation trails. The pages accessible through SmartBack are determined automatically based on the structure of the user's navigation trails or page association with specific user's activities, such as search or browsing bookmarked sites. We discuss implementation decisions and present results of a usability study in which we deployed the SmartBack prototype and monitored usage for a month in both corporate and home settings. The results show that the feature brings qualitative improvement to the browsing experience of individuals who use it.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/988672.988682</identifier>
		<pages>63-71</pages>
		<title type="sharef:primaryTitle">SmartBack: Supporting Users in Back Navigation</title>
	</reference>
	<reference name="etz04a" src="bibtex:inproceedings" src-info="bibtex:line-12683" type="sharef:inproceedings" crossref="www2004">
		<names type="sharef:author">
			<person>
				<givenname>Oren</givenname>
				<surname>Etzioni</surname>
			</person>
			<person>
				<givenname>Michael</givenname>
				<surname>Cafarella</surname>
			</person>
			<person>
				<givenname>Doug</givenname>
				<surname>Downey</surname>
			</person>
			<person>
				<givenname>Stanley</givenname>
				<surname>Kok</surname>
			</person>
			<person>
				<givenname>Ana-Maria</givenname>
				<surname>Popescu</surname>
			</person>
			<person>
				<givenname>Tal</givenname>
				<surname>Shaked</surname>
			</person>
			<person>
				<givenname>Stephen</givenname>
				<surname>Soderland</surname>
			</person>
			<person>
				<givenname>Daniel S.</givenname>
				<surname>Weld</surname>
			</person>
			<person>
				<givenname>Alexander</givenname>
				<surname>Yates</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Manually querying search engines in order to accumulate a large body of factual information is a tedious, error-prone process of piecemeal search. Search engines retrieve and rank potentially relevant documents for human perusal, but do not extract facts, assess confidence, or fuse information from multiple documents. This paper introduces KnowItAll, a system that aims to automate the tedious process of extracting large collections of facts from the web in an autonomous, domain-independent, and scalable manner.The paper describes preliminary experiments in which an instance of KnowItAll, running for four days on a single machine, was able to automatically extract 54,753 facts. KnowItAll associates a probability with each fact enabling it to trade off precision and recall. The paper analyzes KnowItAll's architecture and reports on lessons learned for the design of large-scale information extraction systems.</p>
			</richtext>
		</abstract>
		<pages>100-110</pages>
		<title type="sharef:primaryTitle">Web-Scale Information Extraction in KnowItAll (Preliminary Results)</title>
		<field type="bibtex:topic">knowitall[1]</field>
		<identifier type="sharef:uri" resourceType="application/pdf">http://www2004.org/proceedings/docs/1p100.pdf</identifier>
		<identifier type="sharef:uri" resourceType="application/pdf">http://www.cs.washington.edu/homes/etzioni/papers/www04.pdf</identifier>
	</reference>
	<reference name="eir04" src="bibtex:inproceedings" src-info="bibtex:line-12694" type="sharef:inproceedings" crossref="www2004">
		<names type="sharef:author">
			<person>
				<givenname>Nadav</givenname>
				<surname>Eiron</surname>
			</person>
			<person>
				<givenname>Kevin S.</givenname>
				<surname>McCurley</surname>
			</person>
			<person>
				<givenname>John A.</givenname>
				<surname>Tomlin</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>The celebrated PageRank algorithm has proved to be a very effective paradigm for ranking results of web search algorithms. In this paper we refine this basic paradigm to take into account several evolving prominent features of the web, and propose several algorithmic innovations. First, we analyze features of the rapidly growing "frontier" of the web, namely the part of the web that crawlers are unable to cover for one reason or another. We analyze the effect of these pages and find it to be significant. We suggest ways to improve the quality of ranking by modeling the growing presence of "link rot" on the web as more sites and pages fall out of maintenance. Finally we suggest new methods of ranking that are motivated by the hierarchical structure of the web, are more efficient than PageRank, and may be more resistant to direct manipulation.</p>
			</richtext>
		</abstract>
		<pages>309-318</pages>
		<title type="sharef:primaryTitle">Ranking the Web Frontier</title>
		<field type="bibtex:topic">pagerank[0.8]</field>
		<identifier type="sharef:uri" resourceType="application/pdf">http://www2004.org/proceedings/docs/1p309.pdf</identifier>
	</reference>
	<reference name="mar04a" src="bibtex:inproceedings" src-info="bibtex:line-12704" type="sharef:inproceedings" crossref="www2004">
		<names type="sharef: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>
		<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>
		<pages>164-174</pages>
		<title type="sharef:primaryTitle">SchemaPath, a Minimal Extension to XML Schema for Conditional Constraints</title>
		<field type="bibtex:topic">xsd[0.8]</field>
		<identifier type="sharef:uri" resourceType="application/pdf">http://www2004.org/proceedings/docs/1p164.pdf</identifier>
	</reference>
	<reference name="cas04" src="bibtex:inproceedings" src-info="bibtex:line-12714" type="sharef:inproceedings" crossref="www2004">
		<names type="sharef:author">
			<person>
				<givenname>Davi</givenname>
				<surname>de Castro Reis</surname>
			</person>
			<person>
				<givenname>Paulo B.</givenname>
				<surname>Golgher</surname>
			</person>
			<person>
				<givenname>Altigran S.</givenname>
				<surname link="da">Silva</surname>
			</person>
			<person>
				<givenname>Alberto H. F.</givenname>
				<surname>Laender</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>The Web poses itself as the largest data repository ever available in the history of humankind. Major efforts have been made in order to provide efficient access to relevant information within this huge repository of data. Although several techniques have been developed to the problem of Web data extraction, their use is still not spread, mostly because of the need for high human intervention and the low quality of the extraction results. In this paper, we present a domain-oriented approach to Web data extraction and discuss its application to automatically extracting news from Web sites. Our approach is based on a highly efficient tree structure analysis that produces very effective results. We have tested our approach with several important Brazilian on-line news sites and achieved very precise results, correctly extracting 87.71% of the news in a set of 4088 pages distributed among 35 different sites.</p>
			</richtext>
		</abstract>
		<pages>502-601</pages>
		<title type="sharef:primaryTitle">Automatic Web News Extraction Using Tree Edit Distance</title>
		<identifier type="sharef:uri" resourceType="application/pdf">http://www2004.org/proceedings/docs/1p502.pdf</identifier>
	</reference>
	<reference name="gru04b" src="bibtex:inproceedings" src-info="bibtex:line-12723" type="sharef:inproceedings" crossref="www2004">
		<names type="sharef:author">
			<person>
				<givenname>Daniel</givenname>
				<surname>Gruhl</surname>
			</person>
			<person>
				<givenname>R.</givenname>
				<surname>Guha</surname>
			</person>
			<person>
				<givenname>David</givenname>
				<surname>Liben-Nowell</surname>
			</person>
			<person>
				<givenname>Andrew</givenname>
				<surname>Tomkins</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>We study the dynamics of information propagation in environments of low-overhead personal publishing, using a large collection of weblogs over time as our example domain. We characterize and model this collection at two levels. First, we present a macroscopic characterization of topic propagation through our corpus, formalizing the notion of long-running "chatter" topics consisting recursively of "spike" topics generated by outside world events, or more rarely, by resonances within the community. Second, we present a microscopic characterization of propagation from individual to individual, drawing on the theory of infectious diseases to model the flow. We propose, validate, and employ an algorithm to induce the underlying propagation network from a sequence of posts, and report on the results.</p>
			</richtext>
		</abstract>
		<pages>491-501</pages>
		<title type="sharef:primaryTitle">Information Diffusion Through Blogspace</title>
		<identifier type="sharef:uri" resourceType="application/pdf">http://people.csail.mit.edu/dln/papers/blogs/idib.pdf</identifier>
	</reference>
	<reference name="bay04" src="bibtex:inproceedings" src-info="bibtex:line-12732" type="sharef:inproceedings" crossref="www2004">
		<names type="sharef:author">
			<person>
				<givenname>Roberto J.</givenname>
				<surname>Bayardo</surname>
			</person>
			<person>
				<givenname>Daniel</givenname>
				<surname>Gruhl</surname>
			</person>
			<person>
				<givenname>Vanja</givenname>
				<surname>Josifovski</surname>
			</person>
			<person>
				<givenname>Jussi</givenname>
				<surname>Myllymaki</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>This paper provides an objective evaluation of the performance impacts of binary XML encodings, using a fast stream-based XQuery processor as our representative application. Instead of proposing one binary format and comparing it against standard XML parsers, we investigate the individual effects of several binary encoding techniques that are shared by many proposals. Our goal is to provide a deeper understanding of the performance impacts of binary XML encodings in order to clarify the ongoing and often contentious debate over their merits, particularly in the domain of high performance XML stream processing.</p>
			</richtext>
		</abstract>
		<pages>345-354</pages>
		<title type="sharef:primaryTitle">An Evaluation of Binary XML Encoding Optimizations for Fast Stream Based XML Processing</title>
		<field type="bibtex:topic">xtalk[0.9]</field>
		<identifier type="sharef:uri" resourceType="application/pdf">http://www2004.org/proceedings/docs/1p345.pdf</identifier>
		<identifier type="sharef:uri">http://wwwconf.ecs.soton.ac.uk/archive/00000603/</identifier>
	</reference>
	<reference name="par04" src="bibtex:inproceedings" src-info="bibtex:line-12743" type="sharef:inproceedings" crossref="www2004">
		<names type="sharef:author">
			<person>
				<givenname>Terence John</givenname>
				<surname>Parr</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>The mantra of every experienced web application developer is the same: thou shalt separate business logic from display. Ironically, almost all template engines allow violation of this separation principle, which is the very impetus for HTML template engine development. This situation is due mostly to a lack of formal definition of separation and fear that enforcing separation emasculates a template's power. I show that not only is strict separation a worthy design principle, but that we can enforce separation while providing a potent template engine. I demonstrate my StringTemplate engine, used to build jGuru.com and other commercial sites, at work solving some nontrivial generational tasks.My goal is to formalize the study of template engines, thus, providing a common nomenclature, a means of classifying template generational power, and a way to leverage interesting results from formal language theory. I classify three types of restricted templates analogous to Chomsky's type 1..3 grammar classes and formally define separation including the rules that embody separation.Because this paper provides a clear definition of model-view separation, template engine designers may no longer blindly claim enforcement of separation. Moreover, given theoretical arguments and empirical evidence, programmers no longer have an excuse to entangle model and view.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/988672.988703</identifier>
		<pages>224-233</pages>
		<title type="sharef:primaryTitle">Enforcing Strict Model-View Separation in Template Engines</title>
		<field type="bibtex:topic">mvc[0.9]</field>
		<identifier type="sharef:uri" resourceType="application/pdf">http://www.cs.usfca.edu/~parrt/papers/mvc.templates.pdf</identifier>
	</reference>
	<reference name="car04b" src="bibtex:inproceedings" src-info="bibtex:line-12754" type="sharef:inproceedings" crossref="www2004a">
		<names type="sharef:author">
			<person>
				<givenname>Davide</givenname>
				<surname>Carboni</surname>
			</person>
			<person>
				<givenname>Andrea</givenname>
				<surname>Piras</surname>
			</person>
			<person>
				<givenname>Stefano</givenname>
				<surname>Sanna</surname>
			</person>
			<person>
				<givenname>Sylvain</givenname>
				<surname>Giroux</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>As programmable mobile devices (such as high-end cellular phones and Personal Digital Assistants) became widely adopted, users ask for Internet access on-the-road. While upcoming technologies like UMTS and Wi-Fi provide broadband wireless communication, Web services and Web browsers do not provide any sort of location-awareness yet. As GPS receivers get cheaper, positioning devices will be embedded into commercial mobile devices. Thus, the position of the user can be used to filter and tailor the information presented to the user as already done for language preferences and user-agent.This paper describes early results of an ongoing project called GPSWeb, which aims to provide GPS support for Web browsers and an application model for Location-Based Services. It introduces the Location-Based Browsing concept that enhances the classic Webuser-Website interaction.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/1013367.1013454</identifier>
		<title type="sharef:primaryTitle">The Web Around The Corner: Augmenting the Browser with GPS</title>
		<identifier type="sharef:uri">http://portal.acm.org/citation.cfm?doid=1013367.1013454</identifier>
	</reference>
	<reference name="bar04b" src="bibtex:inproceedings" src-info="bibtex:line-12763" type="sharef:inproceedings" crossref="www2004a">
		<names type="sharef:author">
			<person>
				<givenname>Judit</givenname>
				<surname>Bar-Ilan</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>The number of Web blogs is growing extremely fast, thus this phenomenon cannot be ignored. This paper discusses the issue through monitoring a set of blogs for a two months period in September-October 2003 and characterizing these blogs based on descriptive statistics and content analysis.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/1013367.1013373</identifier>
		<title type="sharef:primaryTitle">An outsider's view on "topic-oriented blogging"</title>
		<identifier type="sharef:uri" resourceType="application/pdf">http://www2004.org/proceedings/docs/2p28.pdf</identifier>
		<identifier type="sharef:uri">http://portal.acm.org/citation.cfm?id=1013373</identifier>
	</reference>
	<reference name="kwo04" src="bibtex:inproceedings" src-info="bibtex:line-12773" type="sharef:inproceedings" crossref="www2004a">
		<names type="sharef:author">
			<person>
				<givenname>Thomas</givenname>
				<surname>Kwok</surname>
			</person>
			<person>
				<givenname>Thao</givenname>
				<surname>Nguyen</surname>
			</person>
			<person>
				<givenname>Linh</givenname>
				<surname>Lam</surname>
			</person>
			<person>
				<givenname>Kakan</givenname>
				<surname>Roy</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>It is a tedious and cumbersome process to update directly a WML document for the wireless Web because its content composes of both data and presentation. Thus, XML is used to handle the data while its XSLT stylesheet is used to extract and format the data for presentation. However, different stylesheets have to be used for different devices. An efficient and systematic method based on the idea of generating two separate sets of rules corresponding to content extracting and formatting parts of the stylesheet is described in this paper. The data extraction part is constructed from content rules while the formatting part is constructed from presentation rules. They are then combined together to form a stylesheet by an XSLT generator. A large number of stylesheets corresponding to different devices and a number of standard DTD documents or XML schemas can be generated in this way and stored in the pool during application setup stage. They will be individually selected from the pool by an XSLT engine to produce different WML documents for different devices during run time.</p>
			</richtext>
		</abstract>
		<title type="sharef:primaryTitle">An Efficient and Systematic Method to Generate XSLT Stylesheets for Different Wireless Pervasive Devices</title>
		<field type="bibtex:topic">xslt1[0.7]</field>
		<identifier type="sharef:uri" resourceType="application/pdf">http://www2004.org/proceedings/docs/2p218.pdf</identifier>
	</reference>
	<reference name="www2004a" src="bibtex:proceedings" src-info="bibtex:line-12782" type="sharef:proceedings">
		<date value="2004-05"/>
		<address type="sharef:placePublished">New York, NY</address>
		<field type="bibtex:index">WWW2004</field>
		<identifier type="sharef:isbn">158113844X</identifier>
		<field type="bibtex:key">Thirteenth International World Wide Web Conference Alternate Track Papers &amp; Posters</field>
		<publisher>ACM Press</publisher>
		<title type="sharef:primaryTitle">Thirteenth International World Wide Web Conference Alternate Track Papers &amp; Posters</title>
		<field type="bibtex:topic">www[0.8]</field>
	</reference>
	<reference name="www2004" src="bibtex:proceedings" src-info="bibtex:line-12795" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>Stuart I.</givenname>
				<surname>Feldman</surname>
			</person>
			<person>
				<givenname>Mike</givenname>
				<surname>Uretsky</surname>
			</person>
			<person>
				<givenname>Marc</givenname>
				<surname>Najork</surname>
			</person>
			<person>
				<givenname>Craig E.</givenname>
				<surname>Wills</surname>
			</person>
		</names>
		<date value="2004-05"/>
		<address type="sharef:placePublished">New York, NY</address>
		<field type="bibtex:index">WWW2004</field>
		<identifier type="sharef:isbn">1581139128</identifier>
		<field type="bibtex:key">Thirteenth International World Wide Web Conference</field>
		<publisher>ACM Press</publisher>
		<title type="sharef:primaryTitle">Thirteenth International World Wide Web Conference</title>
		<field type="bibtex:topic">www[0.8]</field>
		<identifier type="sharef:uri">http://www2004.org/</identifier>
		<identifier type="sharef:uri" resourceType="text/html">http://www.informatik.uni-trier.de/~ley/db/conf/www/www2004.html</identifier>
	</reference>
	<reference name="wil05l" src="bibtex:inproceedings" src-info="bibtex:line-12816" type="sharef:inproceedings" crossref="www2005p">
		<names type="sharef:author">
			<person>
				<givenname>Erik</givenname>
				<surname>Wilde</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Describing XML Namespaces is an open issue for many users of XML technologies, and even though namespaces are one of the foundations of XML, there is no generally accepted and widely used format for namespace descriptions. We present a framework for describing namespaces based on GRDDL using a controlled vocabulary. Using this framework, namespace descriptions can be easily generated, harvested and published in human- or machine-readable form.</p>
			</richtext>
		</abstract>
		<pages>1002-1003</pages>
		<title type="sharef:primaryTitle">Describing Namespaces with GRDDL</title>
		<field type="bibtex:topic">grddl[0.8]</field>
		<identifier type="sharef:uri">http://dret.net/netdret/publications#wil05l</identifier>
	</reference>
	<reference name="car05" src="bibtex:inproceedings" src-info="bibtex:line-12826" type="sharef:inproceedings" crossref="www2005">
		<names type="sharef:author">
			<person>
				<givenname>Jeremy J.</givenname>
				<surname>Carroll</surname>
			</person>
			<person>
				<givenname>Christian</givenname>
				<surname>Bizer</surname>
			</person>
			<person>
				<givenname>Patrick</givenname>
				<surname>Hayes</surname>
			</person>
			<person>
				<givenname>Patrick</givenname>
				<surname>Stickler</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>The Semantic Web consists of many RDF graphs nameable by URIs. This paper extends the syntax and semantics of RDF to cover such Named Graphs. This enables RDF statements that describe graphs, which is beneficial in many Semantic Web application areas. As a case study, we explore the application area of Semantic Web publishing: Named Graphs allow publishers to communicate assertional intent, and to sign their graphs; information consumers can evaluate specific graphs using task-specific trust policies, and act on information from those Named Graphs that they accept. Graphs are trusted depending on: their content; information about the graph; and the task the user is performing. The extension of RDF to Named Graphs provides a formally defined framework to be a foundation for the Semantic Web trust layer.</p>
			</richtext>
		</abstract>
		<pages>613-622</pages>
		<title type="sharef:primaryTitle">Named Graphs, Provenance and Trust</title>
		<field type="bibtex:topic">rdf[0.9]</field>
		<identifier type="sharef:uri" resourceType="application/pdf">http://www2005.org/cdrom/docs/p613.pdf</identifier>
	</reference>
	<reference name="har05" src="bibtex:inproceedings" src-info="bibtex:line-12836" type="sharef:inproceedings" crossref="www2005">
		<names type="sharef:author">
			<person>
				<givenname>Matthew</givenname>
				<surname>Harren</surname>
			</person>
			<person>
				<givenname>Mukund</givenname>
				<surname>Raghavachari</surname>
			</person>
			<person>
				<givenname>Oded</givenname>
				<surname>Shmueli</surname>
			</person>
			<person>
				<givenname>Michael G.</givenname>
				<surname>Burke</surname>
			</person>
			<person>
				<givenname>Rajesh</givenname>
				<surname>Bordawekar</surname>
			</person>
			<person>
				<givenname>Igor</givenname>
				<surname>Pechtchanski</surname>
			</person>
			<person>
				<givenname>Vivek</givenname>
				<surname>Sarkar</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>The increased importance of XML as a data representation format has led to several proposals for facilitating the development of applications that operate on XML data. These proposals range from runtime API-based interfaces to XML-based programming languages. The subject of this paper is XJ, a research language that proposes novel mechanisms for the integration of XML as a first-class construct into Java. The design goals of XJ distinguish it from past work on integrating XML support into programming languages — specifically, the XJ design adheres to the XML Schema and XPath standards. Moreover, it supports in-place updates of XML data thereby keeping with the imperative nature of Java. We have built a prototype compiler for XJ, and our preliminary experiments demonstrate that the performance of XJ programs can approach that of traditional low-level API-based interfaces, while providing a higher level of abstraction.</p>
			</richtext>
		</abstract>
		<pages>278-287</pages>
		<title type="sharef:primaryTitle">XJ: Facilitating XML Processing in Java</title>
		<field type="bibtex:topic">xj[0.9]</field>
		<identifier type="sharef:uri" resourceType="application/pdf">http://www2005.org/cdrom/docs/p278.pdf</identifier>
	</reference>
	<reference name="ana05" src="bibtex:inproceedings" src-info="bibtex:line-12846" type="sharef:inproceedings" crossref="www2005p">
		<names type="sharef:author">
			<person>
				<givenname>Sai</givenname>
				<surname>Anand</surname>
			</person>
			<person>
				<givenname>Erik</givenname>
				<surname>Wilde</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>For XML-based applications in general and B2B applications in particular, mapping between differently structured XML documents, to enable exchange of data, is a basic problem. A generic  solution to the problem is of interest and desirable both in an academic and practical sense. We present a case study of the problem that arises in an XML based project, which involves mapping of different XML schemas to each other. We describe our approach to solving the problem, its advantages and limitations. We also compare and contrast our approach with previously known approaches and commercially available software solutions.</p>
			</richtext>
		</abstract>
		<pages>888-889</pages>
		<title type="sharef:primaryTitle">Mapping XML Instances</title>
		<identifier type="sharef:uri">http://dret.net/netdret/publications#ana05</identifier>
	</reference>
	<reference name="cen05" src="bibtex:inproceedings" src-info="bibtex:line-12855" type="sharef:inproceedings" crossref="www2005p">
		<names type="sharef:author">
			<person>
				<givenname>Vicente Luque</givenname>
				<surname>Centeno</surname>
			</person>
			<person>
				<givenname>Carlos Delgado</givenname>
				<surname>Kloos</surname>
			</person>
			<person>
				<givenname>Martin</givenname>
				<surname>Gaedke</surname>
			</person>
			<person>
				<givenname>Martin</givenname>
				<surname>Nussbaumer</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Web accessibility consists on a set of checkpoints which are rather expensive to evaluate or to spot. However, using W3C technologies, this cost can be clearly minimized. This article presents a W3C formalized rule-set version for automatable checkpoints from WCAG 1.0.</p>
			</richtext>
		</abstract>
		<pages>1146-1147</pages>
		<title type="sharef:primaryTitle">WCAG Formalization with W3C Standards</title>
		<field type="bibtex:topic">wcag[0.8]</field>
	</reference>
	<reference name="bry05a" src="bibtex:inproceedings" src-info="bibtex:line-12864" type="sharef:inproceedings" crossref="www2005p">
		<names type="sharef:author">
			<person>
				<givenname>François</givenname>
				<surname>Bry</surname>
			</person>
			<person>
				<givenname>Michael</givenname>
				<surname>Eckert</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Hyperlinks are an essential feature of the World Wide Web, highly responsible for its success. XLink improves on HTML's linking capabilities in several ways. In particular, links after XLink can be "out-of-line" (i.e., not defined at a link source) and collected in (possibly several) linkbases, which considerably ease building complex link structures. Modeling of link structures and processing of linkbases under the Web's "open world linking" are aspects neglected by XLink. Adding a notion of "interface" to XLink, as suggested in this work, considerably improves modeling of link structures. When a link structure is traversed, the relevant linkbase(s) might become ambiguous. We suggest three linkbase management modes governing the binding of a linkbase to a document to resolve this ambiguity.</p>
			</richtext>
		</abstract>
		<pages>1030-1031</pages>
		<title type="sharef:primaryTitle">Processing Link Structures and Linkbases on the Web</title>
		<field type="bibtex:topic">xlink[0.8]</field>
	</reference>
	<reference name="bex05" src="bibtex:inproceedings" src-info="bibtex:line-12873" type="sharef:inproceedings" crossref="www2005">
		<names type="sharef:author">
			<person>
				<givenname>Geert Jan</givenname>
				<surname>Bex</surname>
			</person>
			<person>
				<givenname>Wim</givenname>
				<surname>Martens</surname>
			</person>
			<person>
				<givenname>Frank</givenname>
				<surname>Neven</surname>
			</person>
			<person>
				<givenname>Thomas</givenname>
				<surname>Schwentick</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>On an abstract level, XML Schema increases the limited expressive power of Document Type Definitions (DTDs) by extending them with a recursive typing mechanism. However, an investigation of the XML Schema Definitions (XSDs) occurring in practice reveals that the vast majority of them are structurally equivalent to DTDs. This might be due to the complexity of the XML Schema specification and the difficulty to understand the effect of constraints on typing and validation of schemas. To shed some light on the actual expressive power of XSDs this paper studies the impact of the Element Declarations Consistent (EDC) and the Unique Particle Attribution (UPA) rule. An equivalent formalism based on contextual patterns rather than on recursive types is proposed which might serve as a light-weight front end for XML Schema. Finally, the effect of EDC and UPA on the way XML documents can be typed is discussed. It is argued that a cleaner, more robust, stronger but equally efficient class is obtained by replacing EDC and UPA with the notion of 1-pass preorder typing: schemas that allow to determine the type of an element of a streaming document when its opening tag is met. This notion can be defined in terms of restrained competition regular expressions and there is again an equivalent syntactical formalism based on contextual patterns.</p>
			</richtext>
		</abstract>
		<pages>712-721</pages>
		<title type="sharef:primaryTitle">Expressiveness of XSDs: From Practice to Theory, There and Back Again</title>
		<field type="bibtex:topic">xsd[0.8]</field>
		<identifier type="sharef:uri" resourceType="application/pdf">http://www2005.org/cdrom/docs/p712.pdf</identifier>
	</reference>
	<reference name="fok05" src="bibtex:inproceedings" src-info="bibtex:line-12883" type="sharef:inproceedings" crossref="www2005">
		<names type="sharef:author">
			<person>
				<givenname>Achille</givenname>
				<surname>Fokoue</surname>
			</person>
			<person>
				<givenname>Kristoffer H.</givenname>
				<surname>Rose</surname>
			</person>
			<person>
				<givenname>Jérôme</givenname>
				<surname>Siméon</surname>
			</person>
			<person>
				<givenname>Lionel</givenname>
				<surname>Villard</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>As XQuery is gathering momentum as the standard query language for XML, there is a growing interest in using it as an integral part of the XML application development infrastructure. In that context, one question which is often raised is how well XQuery interoperates with other XML languages, and notably with XSLT. XQuery 1.0 and XSLT 2.0 share a lot in common: they share XPath 2.0 as a common sub-language and have the same expressiveness. However, they are based on fairly different programming paradigms. While XSLT has adopted a highly declarative template based approach, XQuery relies on a simpler, and more operational, functional approach. In this paper, we present an approach to compile XSLT 2.0 into XQuery 1.0, and a working implementation of that approach. The compilation rules explain how XSLT's template-based approach can be implemented using the functional approach of XQuery and underpins the tight connection between the two languages. The resulting compiler can be used to migrate a XSLT code base to XQuery, or to enable the use of XQuery runtimes (e.g., as will soon be provided by most relational database management systems) for XSLT users. We also identify a number of areas where compatibility between the two languages could be improved. Finally, we show experiments on actual XSLT stylesheets, demonstrating the applicability of the approach in practice.</p>
			</richtext>
		</abstract>
		<pages>682-691</pages>
		<title type="sharef:primaryTitle">Compiling XSLT 2.0 into XQuery 1.0</title>
		<field type="bibtex:topic">xslt2[0.8] xquery[0.8]</field>
		<identifier type="sharef:uri" resourceType="application/pdf">http://www2005.org/cdrom/docs/p682.pdf</identifier>
	</reference>
	<reference name="www2005p" src="bibtex:proceedings" src-info="bibtex:line-12893" type="sharef:proceedings">
		<date value="2005-05"/>
		<address type="sharef:placePublished">Chiba, Japan</address>
		<field type="bibtex:index">WWW2005</field>
		<identifier type="sharef:isbn">1-59593-051-5</identifier>
		<field type="bibtex:key">14th International World Wide Web Conference Posters</field>
		<publisher>ACM Press</publisher>
		<title type="sharef:primaryTitle">14th International World Wide Web Conference Posters</title>
		<field type="bibtex:topic">www[0.8]</field>
	</reference>
	<reference name="www2005" src="bibtex:proceedings" src-info="bibtex:line-12906" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>Allan</givenname>
				<surname>Ellis</surname>
			</person>
			<person>
				<givenname>Tatsuya</givenname>
				<surname>Hagino</surname>
			</person>
		</names>
		<date value="2005-05"/>
		<address type="sharef:placePublished">Chiba, Japan</address>
		<field type="bibtex:index">WWW2005</field>
		<identifier type="sharef:isbn">1-59593-046-9</identifier>
		<field type="bibtex:key">14th International World Wide Web Conference</field>
		<publisher>ACM Press</publisher>
		<title type="sharef:primaryTitle">14th International World Wide Web Conference</title>
		<field type="bibtex:topic">www[0.8]</field>
		<identifier type="sharef:uri">http://www2005.org/cdrom/</identifier>
	</reference>
	<reference name="kos06" src="bibtex:inproceedings" src-info="bibtex:line-12926" type="sharef:inproceedings" crossref="www2006">
		<names type="sharef:author">
			<person>
				<givenname>Margaret G.</givenname>
				<surname>Kostoulas</surname>
			</person>
			<person>
				<givenname>Morris</givenname>
				<surname>Matsa</surname>
			</person>
			<person>
				<givenname>Noah</givenname>
				<surname>Mendelsohn</surname>
			</person>
			<person>
				<givenname>Eric</givenname>
				<surname>Perkins</surname>
			</person>
			<person>
				<givenname>Abraham</givenname>
				<surname>Heifets</surname>
			</person>
			<person>
				<givenname>Martha</givenname>
				<surname>Mercaldi</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>This paper describes an experimental system in which customized high performance XML parsers are prepared using parser generation and compilation techniques. Parsing is integrated with Schema-based validation and deserialization, and the resulting validating processors are shown to be as fast as or in many cases significantly faster than traditional nonvalidating parsers. High performance is achieved by integration across layers of software that are traditionally separate, by avoiding unnecessary data copying and transformation, and by careful attention to detail in the generated code. The effect of API design on XML performance is also briefly discussed.</p>
			</richtext>
		</abstract>
		<title type="sharef:primaryTitle">XML Screamer: An Integrated Approach to High Performance XML Parsing, Validation and Deserialization</title>
		<field type="bibtex:topic">xml[0.8] xmlscreamer[1]</field>
	</reference>
	<reference name="zha06" src="bibtex:inproceedings" src-info="bibtex:line-12934" type="sharef:inproceedings" crossref="www2006">
		<names type="sharef:author">
			<person>
				<givenname>Shuohao</givenname>
				<surname>Zhang</surname>
			</person>
			<person>
				<givenname>Curtis</givenname>
				<surname>Dyreson</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Path expressions are the principal means of locating data in a hierarchical model. But path expressions are brittle because they often depend on the structure of data and break if the data is structured differently. The structure of data could be unfamiliar to a user, may differ within a data collection, or may change over time as the schema evolves. This paper proposes a novel construct that locates related nodes in an instance of an XML data model, independent of a specific structure. It can augment many XPath expressions and can be seamlessly incorporated in XQuery or XSLT.</p>
			</richtext>
		</abstract>
		<title type="sharef:primaryTitle">Symmetrically Exploiting XML</title>
		<field type="bibtex:topic">xml[0.8]</field>
	</reference>
	<reference name="fer06" src="bibtex:inproceedings" src-info="bibtex:line-12942" type="sharef:inproceedings" crossref="www2006">
		<names type="sharef:author">
			<person>
				<givenname>Paolo</givenname>
				<surname>Ferragina</surname>
			</person>
			<person>
				<givenname>Fabrizio</givenname>
				<surname>Luccio</surname>
			</person>
			<person>
				<givenname>Giovanni</givenname>
				<surname>Manzini</surname>
			</person>
			<person>
				<givenname>S.</givenname>
				<surname>Muthukrishnan</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>XML is fast becoming the standard format to store, exchange and publish over the web, and is getting embedded in applications. Two challenges in handling XML are its size (the XML representation of a document is significantly larger than its native state) and the complexity of its search (XML search involves path and content searches on labeled tree structures). We address the basic problems of compression, navigation and searching of XML documents. In particular, we adopt recently proposed theoretical algorithms for succinct tree representations to design and implement a compressed index for XML, called XBzipIndex, in which the XML document is maintained in a highly compressed format, and both navigation and searching can be done uncompressing only a tiny fraction of the data. This solution relies on compressing and indexing two arrays derived from the XML data. With detailed experiments we compare this with other compressed XML indexing and searching engines to show that XBzipIndex has compression ratio up to 35% better than the ones achievable by those other tools, and its time performance on some path and content search operations is order of magnitudes faster: few milliseconds over hundreds of MBs of XML files versus tens of seconds, on standard XML data sources.</p>
			</richtext>
		</abstract>
		<title type="sharef:primaryTitle">Compressing and Searching XML Data Via Two Zips</title>
		<field type="bibtex:topic">xml[0.8]</field>
	</reference>
	<reference name="wil06g" src="bibtex:inproceedings" src-info="bibtex:line-12950" type="sharef:inproceedings" crossref="www2006p">
		<names type="sharef:author">
			<person>
				<givenname>Erik</givenname>
				<surname>Wilde</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>XML is the predominant format for representing structured information inside documents, but it stops at the level of files. This makes it hard to use XML-oriented tools to process information which is scattered over multiple documents within a file system. File System XML (FSX) and its content integration provides a unified view of file system structure and content. FSX's adaptors map file contents to XML, which means that any file format can be integrated with an XML view in the integrated view of the file system.</p>
			</richtext>
		</abstract>
		<title type="sharef:primaryTitle">Merging Trees: File System and Content Integration</title>
		<field type="bibtex:topic">fsx[0.9] xpsh[0.8]</field>
		<identifier type="sharef:uri">http://dret.net/netdret/publications#wil06g</identifier>
	</reference>
	<reference name="wil06h" src="bibtex:inproceedings" src-info="bibtex:line-12959" type="sharef:inproceedings" crossref="www2006p">
		<names type="sharef:author">
			<person>
				<givenname>Erik</givenname>
				<surname>Wilde</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Namespaces are a central building block of XML technologies today, they provide the identification mechanism for many XML-related vocabularies. Despite their ubiquity, there is no established mechanism for describing namespaces, and in particular for describing the dependencies of namespaces. We propose a simple model for describing namespaces and their dependencies. Using these descriptions, it is possible to compile directories of namespaces providing searchable and browsable namespace descriptions.</p>
			</richtext>
		</abstract>
		<title type="sharef:primaryTitle">Structuring Namespace Descriptions</title>
		<field type="bibtex:topic">xmlns[0.8]</field>
		<identifier type="sharef:uri">http://dret.net/netdret/publications#wil06h</identifier>
	</reference>
	<reference name="wil06i" src="bibtex:inproceedings" src-info="bibtex:line-12968" type="sharef:inproceedings" crossref="www2006p">
		<names type="sharef:author">
			<person>
				<givenname>Kaspar</givenname>
				<surname>Giger</surname>
			</person>
			<person>
				<givenname>Erik</givenname>
				<surname>Wilde</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Locating files based on file system structure, file properties, and maybe even file contents is a core task of the user interface of operating systems. By adapting XPath's power to the environment of a Unix shell, it is possible to greatly increase the expressive power of the command line language. We present a concept for integrating an XPath view of the file system into a shell, which can be used to find files based on file attributes and contents in a very flexible way. The syntax of the command line language is backwards compatible with traditional shells, and the new XPath-based expressions can be easily mastered with a little bit of XPath knowledge.</p>
			</richtext>
		</abstract>
		<title type="sharef:primaryTitle">XPath Filename Expansion in a Unix Shell</title>
		<field type="bibtex:topic">xpath1[0.7] fsx[0.8] xpsh[0.9]</field>
		<identifier type="sharef:uri">http://dret.net/netdret/publications#wil06i</identifier>
	</reference>
	<reference name="wil06j" src="bibtex:inproceedings" src-info="bibtex:line-12977" type="sharef:inproceedings" crossref="www2006p">
		<names type="sharef:author">
			<person>
				<givenname>Erik</givenname>
				<surname>Wilde</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>There are principal differences between the relational model and XML's tree model. This causes problems in all cases where information from these two worlds has to be brought together. Using a few rules for mapping the incompatible aspects of the two models, it becomes easier to process data in systems which need to work with relational and tree data. The most important requirement for a good mapping is that the conceptual model is available and can thus be used for making mapping decisions.</p>
			</richtext>
		</abstract>
		<title type="sharef:primaryTitle">Tables and Trees Don't Mix (very well)</title>
		<field type="bibtex:topic">xmlinfoset[0.8] rm[0.8]</field>
		<identifier type="sharef:uri">http://dret.net/netdret/publications#wil06j</identifier>
	</reference>
	<reference name="kha06" src="bibtex:inproceedings" src-info="bibtex:line-12986" type="sharef:inproceedings" crossref="www2006p">
		<names type="sharef:author">
			<person>
				<givenname>Rohit</givenname>
				<surname>Khare</surname>
			</person>
			<person>
				<givenname>Tantek</givenname>
				<surname>Çelik</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Microformats are a clever adaptation of semantic XHTML that makes it easier to publish, index, and extract semi-structured information such as tags, calendar entries, contact information, and reviews on the Web. This makes it a pragmatic path towards achieving the vision set forth for the Semantic Web. Even though it sidesteps the existing "technology stack" of RDF, ontologies, and Artificial Intelligence-inspired processing tools, various microformats have emerged that parallel the goals of several well-known Semantic Web projects. This poster compares their prospects to the Semantic Web according to Rogers' Diffusion of Innovation model.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">http://doi.acm.org/10.1145/1135777.1135917</identifier>
		<title type="sharef:primaryTitle">Microformats: A Pragmatic Path to the Semantic Web</title>
	</reference>
	<reference name="www2006p" src="bibtex:proceedings" src-info="bibtex:line-12994" type="sharef:proceedings">
		<date value="2006-05"/>
		<address type="sharef:placePublished">Edinburgh, UK</address>
		<field type="bibtex:index">WWW2006</field>
		<field type="bibtex:key">15th International World Wide Web Conference Posters</field>
		<publisher>ACM Press</publisher>
		<title type="sharef:primaryTitle">15th International World Wide Web Conference Posters</title>
		<field type="bibtex:topic">www[0.8]</field>
		<identifier type="sharef:uri">http://www2006.org/posters/</identifier>
	</reference>
	<reference name="www2006" src="bibtex:proceedings" src-info="bibtex:line-13007" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>Leslie A.</givenname>
				<surname>Carr</surname>
			</person>
			<person>
				<givenname>David C.</givenname>
				<surname>De Roure</surname>
			</person>
			<person>
				<givenname>Arun</givenname>
				<surname>Iyengar</surname>
			</person>
			<person>
				<givenname>Carole A.</givenname>
				<surname>Goble</surname>
			</person>
			<person>
				<givenname>Michael</givenname>
				<surname>Dahlin</surname>
			</person>
		</names>
		<date value="2006-05"/>
		<address type="sharef:placePublished">Edinburgh, UK</address>
		<field type="bibtex:index">WWW2006</field>
		<identifier type="sharef:isbn">1-59593-323-9</identifier>
		<field type="bibtex:key">15th International World Wide Web Conference</field>
		<publisher>ACM Press</publisher>
		<title type="sharef:primaryTitle">15th International World Wide Web Conference</title>
		<field type="bibtex:topic">www[0.8]</field>
		<identifier type="sharef:uri">http://www2006.org/tracks/</identifier>
	</reference>
	<reference name="bar07b" src="bibtex:inproceedings" src-info="bibtex:line-13027" type="sharef:inproceedings" crossref="www2007">
		<names type="sharef:author">
			<person>
				<givenname>Luciano</givenname>
				<surname>Barbosa</surname>
			</person>
			<person>
				<givenname>Juliana</givenname>
				<surname>Freire</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>In this paper we describe new adaptive crawling strategies to efficiently locate the entry points to hidden-Web sources. The fact that hidden-Web sources are very sparsely distributed makes the problem of locating them especially challenging. We deal with this problem by using the contents of pages to focus the crawl on a topic; by prioritizing promising links within the topic; and by also following links that may not lead to immediate benefit. We propose a new framework whereby crawlers automatically learn patterns of promising links and adapt their focus as the crawl progresses, thus greatly reducing the amount of required manual setup and tuning. Our experiments over real Web pages in a representative set of domains indicate that online learning leads to significant gains in harvest rates — the adaptive crawlers retrieve up to three times as many forms as crawlers that use a fixed focus strategy.</p>
			</richtext>
		</abstract>
		<pages>471-480</pages>
		<title type="sharef:primaryTitle">An Adaptive Crawler for Locating Hidden-Web Entry Points</title>
		<identifier type="sharef:uri" resourceType="application/pdf">http://www2007.org/papers/paper429.pdf</identifier>
	</reference>
	<reference name="sim07" src="bibtex:inproceedings" src-info="bibtex:line-13036" type="sharef:inproceedings" crossref="www2007">
		<names type="sharef:author">
			<person>
				<givenname>Rainer</givenname>
				<surname>Simon</surname>
			</person>
			<person>
				<givenname>Peter</givenname>
				<surname>Fröhlich</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>In this paper we present an application framework that leverages geospatial content on the World Wide Web by enabling innovative modes of interaction and novel types of user interfaces on advanced mobile phones and PDAs. We discuss the current development steps involved in building mobile geospatial Web applications and derive three technological pre-requisites for our framework: spatial query operations based on visibility and field of view, a 2.5D environment model, and a presentation-independent data exchange format for geospatial query results. We propose the Local Visibility Model as a suitable XML-based candidate and present a prototype implementation.</p>
			</richtext>
		</abstract>
		<pages>381-390</pages>
		<title type="sharef:primaryTitle">A Mobile Application Framework for the Geospatial Web</title>
		<identifier type="sharef:uri" resourceType="application/pdf">http://www2007.org/papers/paper287.pdf</identifier>
	</reference>
	<reference name="yan07" src="bibtex:inproceedings" src-info="bibtex:line-13045" type="sharef:inproceedings" crossref="www2007">
		<names type="sharef:author">
			<person>
				<givenname>Fan</givenname>
				<surname>Yang</surname>
			</person>
			<person>
				<givenname>Nitin</givenname>
				<surname>Gupta</surname>
			</person>
			<person>
				<givenname>Nicholas</givenname>
				<surname>Gerner</surname>
			</person>
			<person>
				<givenname>Xin</givenname>
				<surname>Qi</surname>
			</person>
			<person>
				<givenname>Alan J.</givenname>
				<surname>Demers</surname>
			</person>
			<person>
				<givenname>Johannes</givenname>
				<surname>Gehrke</surname>
			</person>
			<person>
				<givenname>Jayavel</givenname>
				<surname>Shanmugasundaram</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Data-driven web applications are structured into three tiers with different programming models at each tier. This division forces developers to manually partition application functionality across the tiers, resulting in complex logic, suboptimal partitioning, and expensive re-partitioning of applications. In this paper, we introduce a unified platform for automatic partitioning of data-driven web applications. Our approach is based on Hilda, a high-level declarative programming language with a unified data and programming model for all the layers of the application. Based on run-time properties of the application, Hilda's run time system automatically partitions the application between the tiers to improve response time while adhering to memory or processing constraints at the clients. We evaluate our methodology with traces from a real application and with TPC-W, and our results show that automatic partitioning outperforms manual partitioning without the associated development overhead.</p>
			</richtext>
		</abstract>
		<pages>341-350</pages>
		<title type="sharef:primaryTitle">A Unified Platform for Data Driven Web Applications with Automatic Client-Server Partitioning</title>
		<field type="bibtex:topic">hilda[0.8]</field>
		<identifier type="sharef:uri">http://www2007.org/paper485.php</identifier>
	</reference>
	<reference name="huy07" src="bibtex:inproceedings" src-info="bibtex:line-13055" type="sharef:inproceedings" crossref="www2007">
		<names type="sharef:author">
			<person>
				<givenname>David</givenname>
				<surname>Huynh</surname>
			</person>
			<person>
				<givenname>David</givenname>
				<surname>Karger</surname>
			</person>
			<person>
				<givenname>Rob</givenname>
				<surname>Miller</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>It is no surprise that Semantic Web researchers and enthusiasts are excited to publish and accumulate semi-structured data on the Web. But looking beyond our community, we recognize that many, many other people also have structured data and want to publish it in rich browsing interfaces. These small-time authors fall into the same category as those early enthusiasts of the Web who were simply excited by the opportunity of using the new medium to share information that they cared about. With this insight, we create a lightweight structured data publishing framework called Exhibit that duplicates many factors we believe have contributed to the original growth of the Web. We argue that appealing to this segment of the Web population — addressing their publishing needs and desires at very low cost in many aspects — lets us leverage their labor to structure existing content on the Web that has previously been authored in HTML by hand and is remaining hard to harvest automatically.</p>
			</richtext>
		</abstract>
		<pages>737-746</pages>
		<title type="sharef:primaryTitle">Exhibit: Lightweight Structured Data Publishing</title>
		<field type="bibtex:topic">exhibit[1] ajax[0.7] json[0.7]</field>
		<identifier type="sharef:uri">http://www2007.org/paper161.php</identifier>
	</reference>
	<reference name="mat07" src="bibtex:inproceedings" src-info="bibtex:line-13065" type="sharef:inproceedings" crossref="www2007">
		<names type="sharef:author">
			<person>
				<givenname>Morris</givenname>
				<surname>Matsa</surname>
			</person>
			<person>
				<givenname>Eric</givenname>
				<surname>Perkins</surname>
			</person>
			<person>
				<givenname>Abraham</givenname>
				<surname>Heifets</surname>
			</person>
			<person>
				<givenname>Margaret Gaitatzes</givenname>
				<surname>Kostoulas</surname>
			</person>
			<person>
				<givenname>Daniel</givenname>
				<surname>Silva</surname>
			</person>
			<person>
				<givenname>Noah</givenname>
				<surname>Mendelsohn</surname>
			</person>
			<person>
				<givenname>Michelle</givenname>
				<surname>Leger</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>XML delivers key advantages in interoperability due to its flexibility, expressiveness, and platform-neutrality. As XML has become a performance-critical aspect of the next generation of business computing infrastructure, however, it has become increasingly clear that XML parsing often carries a heavy performance penalty, and that current, widely-used parsing technologies are unable to meet the performance demands of an XML-based computing infrastructure. Several efforts have been made to address this performance gap through the use of grammar-based parser generation. While the performance of generated parsers has been significantly improved, adoption of the technology has been hindered by the complexity of compiling and deploying the generated parsers. Through careful analysis of the operations required for parsing and validation, we have devised a set of specialized bytecodes, designed for the task of XML parsing and validation. These bytecodes are designed to engender the benefits of fine-grained composition of parsing and validation that make existing compiled parsers fast, while being coarse-grained enough to minimize interpreter overhead. This technique of using an interpretive, validating parser balances the need for performance against the requirements of simple tooling and robust scalable infrastructure. Our approach is demonstrated with a specialized schema compiler, used to generate bytecodes which in turn drive an interpretive parser. With almost as little tooling and deployment complexity as a traditional interpretive parser, the bytecode-driven parser usually demonstrates performance within 20% of the fastest fully compiled solutions.</p>
			</richtext>
		</abstract>
		<pages>1093-1102</pages>
		<title type="sharef:primaryTitle">A High-Performance Interpretive Approach to Schema-Directed Parsing</title>
		<identifier type="sharef:uri">http://www2007.org/paper507.php</identifier>
	</reference>
	<reference name="kol07" src="bibtex:inproceedings" src-info="bibtex:line-13074" type="sharef:inproceedings" crossref="www2007">
		<names type="sharef:author">
			<person>
				<givenname>Solmaz</givenname>
				<surname>Kolahi</surname>
			</person>
			<person>
				<givenname>Leonid</givenname>
				<surname>Libkin</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Design principles for XML schemas that eliminate redundancies and avoid update anomalies have been studied recently. Several normal forms, generalizing those for relational databases, have been proposed. All of them, however, are based on the assumption of a native XML storage, while in practice most of XML data is stored in relational databases. In this paper we study XML design and normalization for relational storage of XML documents. To be able to relate and compare XML and relational designs, we use an information-theoretic framework that measures information content in relations and documents, with higher values corresponding to lower levels of redundancy. We show that most common relational storage schemes preserve the notion of being well-designed (i.e., anomalies- and redundancy-free). Thus, existing XML normal forms guarantee well-designed relational storages as well. We further show that if this perfect option is not achievable, then a slight restriction on XML constraints guarantees a "second-best" relational design, according to possible values of the information-theoretic measure. We finally consider an edge-based relational representation of XML documents, and show that while it has similar information-theoretic properties with other relational representations, it can behave significantly worse in terms of enforcing integrity constraints.</p>
			</richtext>
		</abstract>
		<pages>1083-1092</pages>
		<title type="sharef:primaryTitle">XML Design for Relational Storage</title>
		<identifier type="sharef:uri">http://www2007.org/paper279.php</identifier>
	</reference>
	<reference name="che07" src="bibtex:inproceedings" src-info="bibtex:line-13083" type="sharef:inproceedings" crossref="www2007">
		<names type="sharef:author">
			<person>
				<givenname>Yih-Farn</givenname>
				<surname>Chen</surname>
			</person>
			<person>
				<givenname>Giuseppe</givenname>
				<surname>Di Fabbrizio</surname>
			</person>
			<person>
				<givenname>David</givenname>
				<surname>Gibbon</surname>
			</person>
			<person>
				<givenname>Rittwik</givenname>
				<surname>Jana</surname>
			</person>
			<person>
				<givenname>Serban</givenname>
				<surname>Jora</surname>
			</person>
			<person>
				<givenname>Bernard</givenname>
				<surname>Renger</surname>
			</person>
			<person>
				<givenname>Bin</givenname>
				<surname>Wei</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>The Web is rapidly moving towards a platform for mass collaboration in content production and consumption. Fresh content on a variety of topics, people, and places is being created and made available on the Web at breathtaking speed. Navigating the content effectively not only requires techniques such as aggregating various RSS-enabled feeds, but it also demands a new browsing paradigm. In this paper, we present novel geospatial and temporal browsing techniques that provide users with the capability of aggregating and navigating RSS-enabled content in a timely, personalized and automatic manner. In particular, we describe a system called GeoTracker that utilizes both a geospatial representation and a temporal (chronological) presentation to help users spot the most relevant updates quickly. Within the context of this work, we provide a middleware engine that supports intelligent aggregation and dissemination of RSS feeds with personalization to desktops and mobile devices. We study the navigation capabilities of this system on two kinds of data sets, namely, 2006 World Cup soccer data collected over two months and breaking news items that occur every day. We also demonstrate that the application of such technologies to the video search results returned by YouTube and Google greatly enhances a user's ability in locating and browsing videos based on his or her geographical interests. Finally, we demonstrate that the location inference performance of GeoTracker compares well against machine learning techniques used in the natural language processing/information retrieval community. Despite its algorithm simplicity, it preserves high recall percentages.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/1242572.1242579</identifier>
		<pages>41-50</pages>
		<title type="sharef:primaryTitle">GeoTracker: Geospatial and Temporal RSS Navigation</title>
		<field type="bibtex:topic">georss[0.8] rss[0.8] atom[0.8]</field>
		<identifier type="sharef:uri">http://www2007.org/paper530.php</identifier>
	</reference>
	<reference name="wil07e" src="bibtex:inproceedings" src-info="bibtex:line-13094" type="sharef:inproceedings" crossref="www2007p">
		<names type="sharef:author">
			<person>
				<givenname>Erik</givenname>
				<surname>Wilde</surname>
			</person>
			<person>
				<givenname>Felix</givenname>
				<surname>Michel</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>XML Schema's abstract data model consists of components, which are the structures that eventually define a schema as a whole. XML Schema's XML syntax, on the other hand, is not a direct representation of the schema components, and it proves to be surprisingly hard to derive a schema's components from the XML syntax. The Schema Component XML Syntax (SCX) is a representation which attempts to map schema components as faithfully as possible to XML structures. SCX serves as the starting point for applications which need access to schema components and want to do so using standardized and widely available XML technologies.</p>
			</richtext>
		</abstract>
		<pages>1351-1352</pages>
		<title type="sharef:primaryTitle">XML-Based XML Schema Access</title>
		<field type="bibtex:topic">xsd[0.9] scx[1]</field>
		<identifier type="sharef:uri">http://dret.net/netdret/publications#wil07e</identifier>
		<identifier type="sharef:uri">http://www2007.org/poster934.php</identifier>
	</reference>
	<reference name="wil07f" src="bibtex:inproceedings" src-info="bibtex:line-13105" type="sharef:inproceedings" crossref="www2007p">
		<names type="sharef:author">
			<person>
				<givenname>Erik</givenname>
				<surname>Wilde</surname>
			</person>
			<person>
				<givenname>Felix</givenname>
				<surname>Michel</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>XML is increasingly being used as a typed data format, and therefore it becomes more important to gain access to the type system; very often this 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 access to XML Schemas and thus can more easily develop software which is type- or schema-aware, and thus more robust.</p>
			</richtext>
		</abstract>
		<pages>1343-1344</pages>
		<title type="sharef:primaryTitle">SPath: A Path Language for XML Schema</title>
		<field type="bibtex:topic">xpath2[0.8] spath[1]</field>
		<identifier type="sharef:uri">http://dret.net/netdret/publications#wil07f</identifier>
		<identifier type="sharef:uri">http://www2007.org/poster904.php</identifier>
	</reference>
	<reference name="mic07b" src="bibtex:inproceedings" src-info="bibtex:line-13116" type="sharef:inproceedings" crossref="www2007p">
		<names type="sharef:author">
			<person>
				<givenname>Felix</givenname>
				<surname>Michel</surname>
			</person>
			<person>
				<givenname>Erik</givenname>
				<surname>Wilde</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>XML Schema documents are defined using an XML syntax, which means that the idea of generating schema documentation through standard XML technologies is intriguing. We present X2Doc, a framework for generating schema-documentation solely through XSLT. The framework uses SCX, an XML syntax for XML Schema components, as intermediate format and produces XML-based output formats. Using a modular set of XSLT stylesheets, X2Doc is highly configurable and carefully crafted towards extensibility. This proves especially useful for composite schemas, where additional schema information like Schematron rules are embedded into XML Schemas.</p>
			</richtext>
		</abstract>
		<pages>1339-1340</pages>
		<title type="sharef:primaryTitle">Extensible Schema Documentation with XSLT 2.0</title>
		<field type="bibtex:topic">x2doc[1] xsd[0.7]</field>
		<identifier type="sharef:uri">http://dret.net/netdret/publications#mic07b</identifier>
		<identifier type="sharef:uri">http://www2007.org/poster1047.php</identifier>
	</reference>
	<reference name="mor07" src="bibtex:inproceedings" src-info="bibtex:line-13127" type="sharef:inproceedings" crossref="www2007p">
		<names type="sharef:author">
			<person>
				<givenname>Mirella</givenname>
				<surname>Moro</surname>
			</person>
			<person>
				<givenname>Susan</givenname>
				<surname>Malaika</surname>
			</person>
			<person>
				<givenname>Lipyeow</givenname>
				<surname>Lim</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>In XML databases, new schema versions may be released as frequently as once every two weeks. This poster describes a taxonomy of changes for XML schema evolution. It examines the impact of those changes on the schema validation and query evaluation. Based on that study, it proposes guidelines for XML schema evolution and for writing queries in such a way that they continue to operate as expected across evolving schemas.</p>
			</richtext>
		</abstract>
		<pages>1341-1342</pages>
		<title type="sharef:primaryTitle">Preserving XML Queries during Schema Evolution</title>
		<field type="bibtex:topic">xquery[0.7]</field>
		<identifier type="sharef:uri">http://www2007.org/poster1000.php</identifier>
	</reference>
	<reference name="sab07" src="bibtex:inproceedings" src-info="bibtex:line-13137" type="sharef:inproceedings" crossref="www2007p">
		<names type="sharef:author">
			<person>
				<givenname>Marwan</givenname>
				<surname>Sabbouh</surname>
			</person>
			<person>
				<givenname>Jeff</givenname>
				<surname>Higginson</surname>
			</person>
			<person>
				<givenname>Salim</givenname>
				<surname>Semy</surname>
			</person>
			<person>
				<givenname>Danny</givenname>
				<surname>Gagne</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>The Web Mashup Scripting Language (WMSL) enables an end-user working from his browser, e.g. not needing any other infrastructure, to quickly write mashups that integrate any two, or more, web services on the Web. The end-user accomplishes this by writing a web page that combines HTML, metadata in the form of mapping relations, and small piece of code, or script. The mapping relations enable not only the discovery and retrieval of the WMSL pages, but also affect a new programming paradigm that abstracts many programming complexities from the script writer. Furthermore, the WMSL Web pages or scripts that disparate end-users write, can be harvested by Crawlers to automatically generate the concepts needed to build lightweight ontologies containing local semantics of a web service and its data model, to extend context ontologies or middle ontologies, and to develop links, or mappings, between these ontologies. This enables an open-source model of building ontologies based on the WMSL Web page or scripts that end users write.</p>
			</richtext>
		</abstract>
		<pages>1305-1306</pages>
		<title type="sharef:primaryTitle">Web Mashup Scripting Language</title>
		<field type="bibtex:topic">wmsl[0.9]</field>
		<identifier type="sharef:uri">http://www2007.org/poster972.php</identifier>
	</reference>
	<reference name="mei07" src="bibtex:inproceedings" src-info="bibtex:line-13147" type="sharef:inproceedings" crossref="www2007p">
		<names type="sharef:author">
			<person>
				<givenname>Johannes</givenname>
				<surname>Meinecke</surname>
			</person>
			<person>
				<givenname>Frederic</givenname>
				<surname>Majer</surname>
			</person>
			<person>
				<givenname>Martin</givenname>
				<surname>Gaedke</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>The success of many innovative Web applications is not based on the content they produce — but on how they combine and link existing content. Older Web Engineering methods lack flexibility in a sense that they rely strongly on a-priori knowledge of existing content structures and do not take into account initially unknown content sources. We propose the adoption of principles that are also found in Component-based Software Engineering, to assemble highly extensible solutions from reusable artifacts. The main contribution of our work is a support system, consisting of a central service that manages n:m relationships between arbitrary Web resources, and of Web application components that realize navigation, presentation, and interaction for the linked content.</p>
			</richtext>
		</abstract>
		<pages>1293-1294</pages>
		<title type="sharef:primaryTitle">Construction by Linking: The Linkbase Method</title>
	</reference>
	<reference name="sun07a" src="bibtex:inproceedings" src-info="bibtex:line-13155" type="sharef:inproceedings" crossref="www2007p">
		<names type="sharef:author">
			<person>
				<givenname>Yang</givenname>
				<surname>Sun</surname>
			</person>
			<person>
				<givenname>Ziming</givenname>
				<surname>Zhuang</surname>
			</person>
			<person>
				<givenname>C. Lee</givenname>
				<surname>Giles</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Search engines largely rely on Web robots to collect information from the Web. Due to the unregulated open-access nature of the Web, robot activities are extremely diverse. Such crawling activities can be regulated from the server side by deploying the Robots Exclusion Protocol in a file called robots.txt. Although it is not an enforcement standard, ethical robots (and many commercial) will follow the rules specified in robots.txt. With our focused crawler, we investigate 7,593 websites from education, government, news, and business domains. Five crawls have been conducted in succession to study the temporal changes. Through statistical analysis of the data, we present a survey of the usage of Web robots rules at the Web scale. The results also show that the usage of robots.txt has increased over time.</p>
			</richtext>
		</abstract>
		<pages>1123-1124</pages>
		<title type="sharef:primaryTitle">A Large-Scale Study of Robots.txt</title>
		<identifier type="sharef:uri" resourceType="application/pdf">http://botseer.ist.psu.edu/pp1034-sun.pdf</identifier>
	</reference>
	<reference name="bol07" src="bibtex:inproceedings" src-info="bibtex:line-13164" type="sharef:inproceedings" crossref="www2007p">
		<names type="sharef:author">
			<person>
				<givenname>Johan</givenname>
				<surname>Bollen</surname>
			</person>
			<person>
				<givenname>Marko A.</givenname>
				<surname>Rodriguez</surname>
			</person>
			<person>
				<givenname>Herbert</givenname>
				<surname>Van de Sompel</surname>
			</person>
			<person>
				<givenname>Lyudmila L.</givenname>
				<surname>Balakireva</surname>
			</person>
			<person>
				<givenname>Aric</givenname>
				<surname>Hagberg</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Scholarly entities, such as articles, journals, authors and institutions, are now mostly ranked according to expert opinion and citation data. The Andrew W. Mellon Foundation funded MESUR project at the Los Alamos National Laboratory is developing metrics of scholarly impact that can rank a wide range of scholarly entities on the basis of their usage. The MESUR project starts with the creation of a semantic network model of the scholarly community that integrates bibliographic, citation, and usage data collected from publishers and repositories world-wide. It is estimated that this scholarly semantic network will include approximately 50 million articles, 1 million authors, 10,000 journals and conference proceedings, 500 million citations, and 1 billion usage-related events; the largest scholarly semantic network ever created. The developed scholarly semantic network will then serve as a standardized platform for the definition and validation of new metrics of scholarly impact. This poster describes the MESUR project's data aggregation and processing techniques including the OWL scholarly ontology that was developed to model the scholarly communication process.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/1242572.1242789</identifier>
		<pages>1247-1248</pages>
		<title type="sharef:primaryTitle">The Largest Scholarly Semantic Network ... Ever.</title>
	</reference>
	<reference name="www2007p" src="bibtex:proceedings" src-info="bibtex:line-13173" type="sharef:proceedings">
		<date value="2007-05"/>
		<address type="sharef:placePublished">Banff, Alberta</address>
		<field type="bibtex:index">WWW2007</field>
		<field type="bibtex:key">16th International World Wide Web Conference Posters</field>
		<publisher>ACM Press</publisher>
		<title type="sharef:primaryTitle">16th International World Wide Web Conference Posters</title>
		<field type="bibtex:topic">www[0.8]</field>
		<identifier type="sharef:uri">http://www2007.org/prog-Posters.php</identifier>
	</reference>
	<reference name="www2007" src="bibtex:proceedings" src-info="bibtex:line-13186" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>Carey L.</givenname>
				<surname>Williamson</surname>
			</person>
			<person>
				<givenname>Mary Ellen</givenname>
				<surname>Zurko</surname>
			</person>
			<person>
				<givenname>Peter F.</givenname>
				<surname>Patel-Schneider</surname>
			</person>
			<person>
				<givenname>Prashant J.</givenname>
				<surname>Shenoy</surname>
			</person>
		</names>
		<date value="2007-05"/>
		<address type="sharef:placePublished">Banff, Alberta</address>
		<field type="bibtex:index">WWW2007</field>
		<field type="bibtex:key">16th International World Wide Web Conference</field>
		<publisher>ACM Press</publisher>
		<title type="sharef:primaryTitle">16th International World Wide Web Conference</title>
		<field type="bibtex:topic">www[0.8]</field>
		<identifier type="sharef:uri">http://www2007.org/prog-Papers.php</identifier>
	</reference>
	<reference name="kas07b" src="bibtex:inproceedings" src-info="bibtex:line-13203" type="sharef:inproceedings" crossref="tmsio2007">
		<names type="sharef:author">
			<person>
				<givenname>Owen</givenname>
				<surname>Kaser</surname>
			</person>
			<person>
				<givenname>Daniel</givenname>
				<surname>Lemire</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Tag clouds provide an aggregate of tag-usage statistics. They are typically sent as in-line HTML to browsers. However, display mechanisms suited for ordinary text are not ideal for tags, because font sizes may vary widely on a line. As well, the typical layout does not account for relationships that may be known between tags. This paper presents models and algorithms to improve the display of tag clouds that consist of in-line HTML, as well as algorithms that use nested tables to achieve a more general 2-dimensional layout in which tag relationships are considered. The first algorithms leverage prior work in typesetting and rectangle packing, whereas the second group of algorithms leverage prior work in Electronic Design Automation. Experiments show our algorithms can be efficiently implemented and perform well.</p>
			</richtext>
		</abstract>
		<title type="sharef:primaryTitle">Tag-Cloud Drawing: Algorithms for Cloud Visualization</title>
		<identifier type="sharef:uri" resourceType="application/pdf">http://www2007.org/workshops/paper_12.pdf</identifier>
	</reference>
	<reference name="tmsio2007" src="bibtex:proceedings" src-info="bibtex:line-13211" type="sharef:proceedings">
		<date value="2007-05"/>
		<address type="sharef:placePublished">Banff, Alberta</address>
		<field type="bibtex:key">WWW2007 Workshop on Tagging and Metadata for Social Information Organization</field>
		<title type="sharef:primaryTitle">WWW2007 Workshop on Tagging and Metadata for Social Information Organization</title>
		<identifier type="sharef:uri">http://www2007.org/workshop-W9.php</identifier>
	</reference>
	<reference name="pau08a" src="bibtex:inproceedings" src-info="bibtex:line-13226" type="sharef:inproceedings" crossref="www2008">
		<names type="sharef:author">
			<person>
				<givenname>Cesare</givenname>
				<surname>Pautasso</surname>
			</person>
			<person>
				<givenname>Olaf</givenname>
				<surname>Zimmermann</surname>
			</person>
			<person>
				<givenname>Frank</givenname>
				<surname>Leymann</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Recent technology trends in the Web Services (WS) domain indicate that a solution eliminating the presumed complexity of the WS-* standards may be in sight: advocates of REpresentational State Transfer (REST) have come to believe that their ideas explaining why the World Wide Web works are just as applicable to solve enterprise application integration problems and to simplify the plumbing required to build service-oriented architectures. In this paper we objectify the WS-* vs. REST debate by giving a quantitative technical comparison based on architectural principles and decisions. We show that the two approaches differ in the number of architectural decisions that must be made and in the number of available alternatives. This discrepancy between freedom-from-choice and freedom-of-choice explains the complexity difference perceived. However, we also show that there are significant differences in the consequences of certain decisions in terms of resulting development and maintenance costs. Our comparison helps technical decision makers to assess the two integration styles and technologies more objectively and select the one that best fits their needs: REST is well suited for basic, ad hoc integration scenarios, WS-* is more flexible and addresses advanced quality of service requirements commonly occurring in enterprise computing.</p>
			</richtext>
		</abstract>
		<pages>805-814</pages>
		<title type="sharef:primaryTitle">RESTful Web Services vs. "Big" Web Services: Making the Right Architectural Decision</title>
	</reference>
	<reference name="dmi08" src="bibtex:inproceedings" src-info="bibtex:line-13234" type="sharef:inproceedings" crossref="www2008p">
		<names type="sharef:author">
			<person>
				<givenname>Pavel</givenname>
				<surname>Dmitriev</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>This paper considers the problem of identifying on the Web compound documents (cDocs) — groups of web pages that in aggregate constitute semantically coherent information entities. Examples of cDocs are a news article consisting of several html pages, or a set of pages describing specifications, price, and reviews of a digital camera. Being able to identify cDocs would be useful in many applications including web and intranet search, user navigation, automated collection generation, and information extraction. In the past, several heuristic approaches have been proposed to identify cDocs. However, heuristics fail to capture the variety of types, styles and goals of information on the web, and do not account for the fact that the definition of a cDoc often depends on the context. This paper presents an experimental evaluation of three machine learning-based algorithms for cDoc discovery. These algorithms are responsive to the varying structure of cDocs and adaptive to their application-specific nature. Based on our previous work, this paper proposes a different scenario for discovering cDocs, and compares in this new setting the local machine learned clustering algorithm to a global purely graph based approach and a Conditional Markov Network approach previously applied to noun coreference task. The results show that the approach outperforms the other algorithms, suggesting that global relational characteristics of web sites are too noisy for cDoc identification purposes.</p>
			</richtext>
		</abstract>
		<pages>1029-1030</pages>
		<title type="sharef:primaryTitle">As We May Perceive: Finding the Boundaries of Compound Documents on the Web</title>
	</reference>
	<reference name="www2008p" src="bibtex:proceedings" src-info="bibtex:line-13242" type="sharef:proceedings">
		<date value="2008-04"/>
		<address type="sharef:placePublished">Beijing, China</address>
		<field type="bibtex:index">WWW2008</field>
		<field type="bibtex:key">17th International World Wide Web Conference Posters</field>
		<publisher>ACM Press</publisher>
		<title type="sharef:primaryTitle">17th International World Wide Web Conference Posters</title>
		<field type="bibtex:topic">www[0.8]</field>
	</reference>
	<reference name="www2008" src="bibtex:proceedings" src-info="bibtex:line-13254" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>Jinpeng</givenname>
				<surname>Huai</surname>
			</person>
			<person>
				<givenname>Robin</givenname>
				<surname>Chen</surname>
			</person>
			<person>
				<givenname>Hsiao-Wuen</givenname>
				<surname>Hon</surname>
			</person>
			<person>
				<givenname>Yunhao</givenname>
				<surname>Liu</surname>
			</person>
			<person>
				<givenname>Wei-Ying</givenname>
				<surname>Ma</surname>
			</person>
			<person>
				<givenname>Andrew</givenname>
				<surname>Tomkins</surname>
			</person>
			<person>
				<givenname>Xiaodong</givenname>
				<surname>Zhang</surname>
			</person>
		</names>
		<date value="2008-04"/>
		<address type="sharef:placePublished">Beijing, China</address>
		<field type="bibtex:index">WWW2008</field>
		<field type="bibtex:key">17th International World Wide Web Conference</field>
		<publisher>ACM Press</publisher>
		<title type="sharef:primaryTitle">17th International World Wide Web Conference</title>
		<field type="bibtex:topic">www[0.8]</field>
		<identifier type="sharef:uri" resourceType="text/html">http://www.informatik.uni-trier.de/~ley/db/conf/www/www2008.html</identifier>
	</reference>
	<reference name="wil08e" src="bibtex:inproceedings" src-info="bibtex:line-13272" type="sharef:inproceedings" crossref="wsw2008">
		<names type="sharef:author">
			<person>
				<givenname>Erik</givenname>
				<surname>Wilde</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>The Web has become a very popular starting point for many innovations targeting infrastructure, services, and applications. One of the challenges of today's vast Web landscape is to monitor ongoing developments, put them into context, and assess their chances of success. One of the main virtues of a more scientific approach towards the Web landscape would be a clear differentiation between approaches which build on top of the infrastructure of the Web, with little embedding into the landscape itself, and those that are intended to blend into the Web, becoming a part of the Web itself. One of the main challenges in this area is to understand and classify new developments, and a better understanding of various dimensions of Web technology design would make it easier to assess the chances of success of any given development. This paper presents a preliminary classification, and presents arguments how those factors influence the chance for success.</p>
			</richtext>
		</abstract>
		<pages>79-83</pages>
		<title type="sharef:primaryTitle">The Plain Web</title>
		<identifier type="sharef:uri">http://dret.net/netdret/publications#wil08e</identifier>
		<identifier type="sharef:uri">http://journal.webscience.org/46/</identifier>
	</reference>
	<reference name="bol08a" src="bibtex:inproceedings" src-info="bibtex:line-13282" type="sharef:inproceedings" crossref="wsw2008">
		<names type="sharef:author">
			<person>
				<givenname>Susanne</givenname>
				<surname>Boll</surname>
			</person>
			<person>
				<givenname>Dirk</givenname>
				<surname>Ahlers</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>The Web today is considered to be a sheer unlimited resource of interlinked information which can be explored following links or can be found employing keyword-based search engines. A feature that becomes more and more relevant for our search and use of the Web is the geospatial reference of information. In this paper, we understand the Web as a vast geospatial information space in which most of the location information is still hidden inside the Web's content. We discuss the processes of uncovering hidden spatial information on the Web to realize a multitude of geospatial user scenarios. To explore the spatial character of the Web, location information needs to be discovered, understood, and augmented. By providing location insights into the existing Web, its content becomes accessible to spatial applications and thus allow users exploring the geospatial Web.</p>
			</richtext>
		</abstract>
		<pages>40-43</pages>
		<title type="sharef:primaryTitle">A Web more Geospatial: Insights into the Location Inside</title>
		<identifier type="sharef:uri">http://journal.webscience.org/37/</identifier>
	</reference>
	<reference name="wsw2008" src="bibtex:proceedings" src-info="bibtex:line-13291" type="sharef:proceedings">
		<date value="2008-04"/>
		<address type="sharef:placePublished">Beijing, China</address>
		<field type="bibtex:index">WSW 2008</field>
		<identifier type="sharef:isbn">978-085432885-7</identifier>
		<field type="bibtex:key">First International Workshop on Understanding Web Evolution (WebEvolve2008)</field>
		<title type="sharef:primaryTitle">First International Workshop on Understanding Web Evolution (WebEvolve2008)</title>
		<field type="bibtex:topic">www[0.8]</field>
		<identifier type="sharef:uri">http://webscience.org/events/www2008/</identifier>
	</reference>
	<reference name="wil08f" src="bibtex:inproceedings" src-info="bibtex:line-13308" type="sharef:inproceedings" crossref="locweb2008">
		<names type="sharef:author">
			<person>
				<givenname>Erik</givenname>
				<surname>Wilde</surname>
			</person>
			<person>
				<givenname>Martin</givenname>
				<surname>Kofahl</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>The concept of location has become very popular in many applications on the Web, in particular for those which aim at connecting the real world with resources on the Web. However, the Web as it is today has no overall location concept, which means that applications have to introduce their own location concepts and have done so in incompatible ways. By turning the Web into a location-aware Web, which we call the "Locative Web", location-oriented applications get better support for their location concepts on the Web, and the Web becomes an information system where location-related information can be more easily shared across different applications and application areas. We describe a location concept for the Web supporting different location types, its embedding into some of the Web's core technologies, and prototype implementations of these concepts in location-enabled Web components.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/1367798.1367800</identifier>
		<pages>1-8</pages>
		<title type="sharef:primaryTitle">The Locative Web</title>
		<identifier type="sharef:uri">http://dret.net/netdret/publications#wil08f</identifier>
	</reference>
	<reference name="tan08" src="bibtex:inproceedings" src-info="bibtex:line-13318" type="sharef:inproceedings" crossref="locweb2008">
		<names type="sharef:author">
			<person>
				<givenname>Vlad</givenname>
				<surname>Tanasescu</surname>
			</person>
			<person>
				<givenname>John</givenname>
				<surname>Domingue</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>In this paper, we argue that in a local search, the what that is queried is implicitly about places and that geographic information retrieval would therefore benefit from an investigation of the semantics of place as a geographical entity. This investigation should include both the spatial and human components constitutive of the notion of place, without which the notion does not make sense. However existing knowledge representation (KR) models, such as ontologies based on logical theories, conceptual spaces, affordance or other, cannot capture in isolation all aspects of the meaning of a place. Therefore we propose to use a combination of them based on the underlying notion of difference. Differences are linked atoms of meaning. These nuances of meaning can be captured by using a variation of the technique of free association based on tagging, without committing to any KR model. Mapping to elements of different KR models can be made later to follow the requirements of a task. We demonstrate the usefulness of the approach for local search by applying it to the notion of place redefined as that location that supports a homogeneous affordance field while allowing the homogeneity of movement.</p>
			</richtext>
		</abstract>
		<pages>9-16</pages>
		<title type="sharef:primaryTitle">A Differential Notion of Place for Local Search</title>
	</reference>
	<reference name="hen08a" src="bibtex:inproceedings" src-info="bibtex:line-13326" type="sharef:inproceedings" crossref="locweb2008">
		<names type="sharef:author">
			<person>
				<givenname>Andreas</givenname>
				<surname>Henrich</surname>
			</person>
			<person>
				<givenname>Volker</givenname>
				<surname>Lüdecke</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>In typical concept@location-queries, the location is sometimes given by terms that cannot be found in gazetteers or geographic databases. Such terms range from names of vague geographical regions to more general terms such as mining or theme parks. In the present paper we describe our approach to deal with such vague location specifications. Roughly spoken, we derive a geographic representation for these location specifications from the top documents resulting from a query using the terms describing the location. These documents are parsed for toponyms and from these toponyms the region is derived. In the paper we describe an efficient process to derive the geographic representation for such situations at query time. Furthermore we present experiments depicting the performance of our approach as well as the result quality. Our approach allows for an efficient execution of queries such as camping ground near theme park or cycle path near brewery. It can also be used as a standalone-application giving a visual impression of the geographic footprint of arbitrary terms.</p>
			</richtext>
		</abstract>
		<pages>17-24</pages>
		<title type="sharef:primaryTitle">Determining Geographic Representations for Arbitrary Concepts at Query Time</title>
	</reference>
	<reference name="hen08b" src="bibtex:inproceedings" src-info="bibtex:line-13334" type="sharef:inproceedings" crossref="locweb2008">
		<names type="sharef:author">
			<person>
				<givenname>Riikka</givenname>
				<surname>Henriksson</surname>
			</person>
			<person>
				<givenname>Tomi</givenname>
				<surname>Kauppinen</surname>
			</person>
			<person>
				<givenname>Eero</givenname>
				<surname>Hyvönen</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>In this paper we examine 1) the scope of geo-ontologies used especially for the purposes of information retrieval from the Web, 2) the core geographical concepts and their mutual relations, and 3) the properties the concepts have. Furthermore, we present the Finnish geo-ontology (Suomalainen paikkaontologia, SUO) and discuss the theories and principles that have governed the development process, as well as the limitations and requirements the use of geographical dictionaries as an instance data source have imposed to the content and the structure of SUO.</p>
			</richtext>
		</abstract>
		<pages>57-60</pages>
		<title type="sharef:primaryTitle">Core Geographical Concepts: Case Finnish Geo-Ontology</title>
	</reference>
	<reference name="twa08" src="bibtex:inproceedings" src-info="bibtex:line-13342" type="sharef:inproceedings" crossref="locweb2008">
		<names type="sharef:author">
			<person>
				<givenname>Florian A.</givenname>
				<surname>Twaroch</surname>
			</person>
			<person>
				<givenname>Christopher B.</givenname>
				<surname>Jones</surname>
			</person>
			<person>
				<givenname>Alia I.</givenname>
				<surname>Abdelmoty</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Vernacular place names are names that are commonly in use to refer to geographical places. For purposes of effective information retrieval, the spatial extent associated with these names should be able to reflect people's perception of the place, even though this may differ sometimes from the administrative definition of the same place name. Due to their informal nature, vernacular place names are hard to capture, but methods to acquire and define vernacular place names are of great benefit to search engines and all kind of information services that deal with geographic data. This paper discusses the acquisition of vernacular use of place names from web sources and their representation as surface models derived by kernel density estimators.</p>
			</richtext>
		</abstract>
		<pages>61-64</pages>
		<title type="sharef:primaryTitle">Acquisition of a Vernacular Gazetteer from Web Sources</title>
	</reference>
	<reference name="sch08a" src="bibtex:inproceedings" src-info="bibtex:line-13350" type="sharef:inproceedings" crossref="locweb2008">
		<names type="sharef:author">
			<person>
				<givenname>Arno</givenname>
				<surname>Scharl</surname>
			</person>
			<person>
				<givenname>Hermann</givenname>
				<surname>Stern</surname>
			</person>
			<person>
				<givenname>Albert</givenname>
				<surname>Weichselbraun</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>This paper presents the IDIOM Media Watch on Climate Change (www.ecoresearch.net/climate), a prototypical implementation of an environmental portal that emphasizes the importance of location data for advanced Web applications. The introductory section outlines the process of retrofitting existing knowledge repositories with geographical context information, a process also referred to as geotagging. The paper then describes the portal's functionality, which aggregates, annotates and visualizes environmental articles from 150 Anglo-American news media sites. From 300,000 news media articles gathered in weekly intervals, the system selects about 10,000 focusing on environmental issues. The crawled data is indexed and stored in a central repository. Geographic location represents a central aspect of the application, but not the only dimension used to organize and filter content. Applying the concepts of location and topography to semantic similarity, the paper concludes with discussing information landscapes as alternative interface metaphor for accessing large Web repositories.</p>
			</richtext>
		</abstract>
		<pages>65-68</pages>
		<title type="sharef:primaryTitle">Annotating and Visualizing Location Data in Geospatial Web Applications</title>
	</reference>
	<reference name="ahl08" src="bibtex:inproceedings" src-info="bibtex:line-13358" type="sharef:inproceedings" crossref="locweb2008">
		<names type="sharef:author">
			<person>
				<givenname>Dirk</givenname>
				<surname>Ahlers</surname>
			</person>
			<person>
				<givenname>Susanne</givenname>
				<surname>Boll</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Local search is increasingly becoming a major focus point of research interest as a widely-recognized speciality search with a large application area. Its data is usually aggregated from a variety of sources. One as yet largely untapped source of location data is the WWW. Today, the Web does not explicitly reveal its location-relation, rather this information is hidden somewhere within pages' contents. To exploit such location information, we need to find, extract and geo-spatially index relevant Web pages. For an effective retrieval of such content, this paper examines the application of focused Web crawling to the geospatial domain. We describe our approach for a geo-aware focused crawling of urban areas and other regions with a high building density and present our experimental results that gives us insight into spatial Web information such as location density and link distance between topical pages. Our crawls and evaluations back our hypothesis that adaptive focused crawling yields good results on the urban geospatial topic.</p>
			</richtext>
		</abstract>
		<pages>25-32</pages>
		<title type="sharef:primaryTitle">Urban Web Crawling</title>
	</reference>
	<reference name="liu08" src="bibtex:inproceedings" src-info="bibtex:line-13366" type="sharef:inproceedings" crossref="locweb2008">
		<names type="sharef:author">
			<person>
				<givenname>Jiahui</givenname>
				<surname>Liu</surname>
			</person>
			<person>
				<givenname>Larry</givenname>
				<surname>Birnbaum</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>The web has become an important medium for news delivery and consumption. Fresh content about a variety of topics, events, and places is constantly being created and published on the web by news agencies around the world. As intuitively understood by readers, and studied in journalism, news articles produced by different social groups present different attitudes towards and interpretations of the same news issues. In this paper, we propose a new paradigm for aggregating news articles according to the local news sources associated with the stakeholders of the news issues. This new paradigm provides users the capability to aggregate and browse various local points of view about the news issues in which they are interested. We implement this paradigm in a system called LocalSavvy. LocalSavvy analyzes the news articles provided by users, using knowledge about locations automatically acquired from the web. Based on the analysis of the news issue, the system finds and aggregates local news articles published by official and unofficial news sources associated with the stakeholders. Moreover, opinions from those local social groups are extracted from the retrieved results, presented in the summaries and highlighted in the news web pages. We evaluate LocalSavvy with a user study. The quantitative and qualitative analysis shows that news articles aggregated by LocalSavvy present relevant and distinct local opinions, which can be clearly perceived by the subjects.</p>
			</richtext>
		</abstract>
		<pages>33-40</pages>
		<title type="sharef:primaryTitle">LocalSavvy: Aggregating Local Points of View about News Issues</title>
	</reference>
	<reference name="zhu08" src="bibtex:inproceedings" src-info="bibtex:line-13374" type="sharef:inproceedings" crossref="locweb2008">
		<names type="sharef:author">
			<person>
				<givenname>Ziming</givenname>
				<surname>Zhuang</surname>
			</person>
			<person>
				<givenname>Cliff</givenname>
				<surname>Brunk</surname>
			</person>
			<person>
				<givenname>C. Lee</givenname>
				<surname>Giles</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>The number of search queries that are associated with geographical locations, either explicitly or implicitly, has been quadrupled in recent years. For such geo-sensitive queries, the ability to accurately infer users' geographical preference greatly enhances their search experience. By mining past user clicks and constructing a geographical click probability distribution model, we address two important issues in spatial Web search: how do we determine whether a search query is geo-sensitive, and how do we detect, disambiguate, and visualize the associated geographical location(s). We present our empirical study on a large-scale dataset with about 9,000 unique queries randomly drawn from the logs of a popular commercial search engine Yahoo! Search, and about 430 million user clicks on 1.6M unique Web pages over an eight-month period. Our classification method achieved recall of 0.98 and precision of 0.75 in identifying geo-sensitive search queries. We also present our preliminary findings in using geographical click probability distributions to cluster search results for queries with geographical ambiguities.</p>
			</richtext>
		</abstract>
		<pages>73-76</pages>
		<title type="sharef:primaryTitle">Modeling and Visualizing Geo-Sensitive Queries Based on User Clicks</title>
	</reference>
	<reference name="she08" src="bibtex:inproceedings" src-info="bibtex:line-13382" type="sharef:inproceedings" crossref="locweb2008">
		<names type="sharef:author">
			<person>
				<givenname>Chang</givenname>
				<surname>Sheng</surname>
			</person>
			<person>
				<givenname>Wynne</givenname>
				<surname>Hsu</surname>
			</person>
			<person>
				<givenname>Mong Li</givenname>
				<surname>Lee</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>As the Internet continues to play an important role in many business applications, it becomes vital to increase the competitive edge by offering geographically tailored contents that reflect the common interests of the geographical region of the web visitors. In this paper, we define the problem of mining geographical-specific interests patterns. We utilize the quadtree to model the influence distributions of different features, and design an algorithm called FlexiPROBER to mine geographical-specific interests patterns that are significant in a local region. We further examine how these patterns can change over time and develop an algorithm called MineGIC to efficiently discover pattern changes. Experiment results demonstrate that the proposed algorithms are scalable and efficient. Patterns discovered from real world web click datasets reveal interesting patterns and show the evolution of the interests of people in those regions.</p>
			</richtext>
		</abstract>
		<pages>41-48</pages>
		<title type="sharef:primaryTitle">Discovering Geographical-specific Interests from Web Click Data</title>
	</reference>
	<reference name="att08" src="bibtex:inproceedings" src-info="bibtex:line-13390" type="sharef:inproceedings" crossref="locweb2008">
		<names type="sharef:author">
			<person>
				<givenname>Qingqing</givenname>
				<surname>Gan</surname>
			</person>
			<person>
				<givenname>Josh</givenname>
				<surname>Attenberg</surname>
			</person>
			<person>
				<givenname>Alexander</givenname>
				<surname>Markowetz</surname>
			</person>
			<person>
				<givenname>Torsten</givenname>
				<surname>Suel</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Geography is becoming increasingly important in web search. Search engines can often return better results to users by analyzing features such as user location or geographic terms in web pages and user queries. This is also of great commercial value as it enables location specific advertising and improved search for local businesses. As a result, major search companies have invested significant resources into geographic search technologies, also often called local search. This paper studies geographic search queries, i.e., text queries such as "hotel new york" that employ geographical terms in an attempt to restrict results to a particular region or location. Our main motivation is to identify opportunities for improving geographical search and related technologies, and we perform an analysis of 36 million queries of the recently released AOL query trace. First, we identify typical properties of geographic search (geo) queries based on a manual examination of several thousand queries. Based on these observations, we build a classifier that separates the trace into geo and non-geo queries. We then investigate the properties of geo queries in more detail, and relate them to web sites and users associated with such queries.
We also propose a new taxonomy for geographic search queries.</p>
			</richtext>
		</abstract>
		<pages>49-56</pages>
		<title type="sharef:primaryTitle">Analysis of Geographic Queries in a Search Engine Log</title>
	</reference>
	<reference name="xia08" src="bibtex:inproceedings" src-info="bibtex:line-13399" type="sharef:inproceedings" crossref="locweb2008">
		<names type="sharef:author">
			<person>
				<givenname>Xiangye</givenname>
				<surname>Xiao</surname>
			</person>
			<person>
				<givenname>Longhao</givenname>
				<surname>Wang</surname>
			</person>
			<person>
				<givenname>Xing</givenname>
				<surname>Xie</surname>
			</person>
			<person>
				<givenname>Qiong</givenname>
				<surname>Luo</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Though general query log mining has been studied for years, little work has been done to utilize geographic search logs. A geographic search request basically contains a query consisting of one or more keywords, and a location specifying the geographic search area. In this paper, we study the problem of discovering co-located queries which are frequently searched over nearby locations. One example co-located query pattern is "shopping mall", "parking". This pattern indicates that people often search "shopping mall" and "parking" over locations close to one another. We formally define co-located query patterns and propose two approaches to mine the patterns. The basic approach is based on an existing spatial mining algorithm. To find more co-located queries that only appear in specific regions, we propose a lattice based approach. It divides the geographic space into regions and mines patterns in each region. We also define a locality measure to categorize patterns into local and global. Experimental results show that the lattice based approach achieves higher performance than the basic approach in the number of patterns, the quality of patterns, and the proportion of local patterns.</p>
			</richtext>
		</abstract>
		<pages>77-84</pages>
		<title type="sharef:primaryTitle">Discovering Co-located Queries in Geographic Search Logs</title>
	</reference>
	<reference name="akc08" src="bibtex:inproceedings" src-info="bibtex:line-13407" type="sharef:inproceedings" crossref="locweb2008">
		<names type="sharef:author">
			<person>
				<givenname>Hüseyin</givenname>
				<surname>Akcan</surname>
			</person>
			<person>
				<givenname>Torsten</givenname>
				<surname>Suel</surname>
			</person>
			<person>
				<givenname>Hervé</givenname>
				<surname>Brönnimann</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>DNS is one of the most actively used distributed databases on earth, accessed by millions of people every day to transparently convert host names into IP addresses and vice versa. In order to improve their performance, DNS servers also keep temporary records of all requested domain names in their cache. While most of the DNS servers are configured to be used by their local users only, there still exist many DNS servers that respond to public queries. Querying these DNS servers reveals the recently visited domains. Exploiting the geographically distributed nature of DNS, one can gather usage statistics ranging from a single DNS server to global scale. In particular, this enables collecting statistics about geographic differences in web browsing behavior between different regions of a country or the world. In this paper, we present methods to identify these public DNS servers, discuss how to effectively crawl them, and describe our algorithm to extract usage estimations from the crawl data. We also evaluate our estimation algorithm using extensive simulations, and finally use our algorithms to crawl 150 U.S. universities for various domains, and explore the effects of location and time on the access rate of these domains.</p>
			</richtext>
		</abstract>
		<pages>85-92</pages>
		<title type="sharef:primaryTitle">Geographic Web Usage Estimation By Monitoring DNS Caches</title>
	</reference>
	<reference name="phu08" src="bibtex:inproceedings" src-info="bibtex:line-13415" type="sharef:inproceedings" crossref="locweb2008">
		<names type="sharef:author">
			<person>
				<givenname>Dinh</givenname>
				<surname>Phung</surname>
			</person>
			<person>
				<givenname>Brett</givenname>
				<surname>Adams</surname>
			</person>
			<person>
				<givenname>Svetha</givenname>
				<surname>Venkatesh</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>We present a computational framework to automatically discover high-order social patterns from very noisy and sparse location sensing information. The key idea in this work is to construct a social codebook, transform raw data into a 'book of life' — a collection of social pages, each in turn is a sequence of encoded footprints. Computable patterns are then defined as repeated structures found in these sequences. Tackling this problem poses several challenges such as how to construct the codebook, how to define patterns and extract them. In particular, extracting high-order patterns are known to be a very hard problem. We address these questions and propose a Latent Social theme Dirichlet Allocation (LSDA) model, which is a personalized version of the Ngram topic models proposed recently. This model can be viewed as a Baysian clustering method, jointly discovering temporal collocation of footprints and exploiting statistical strength across social pages. Alternatively it can be viewed as dimensionality reduction method where the reduced latent space corresponds to hidden social themes or plans of user's daily activities. Applying to a real-world noisy dataset collected over 1.5 years, we show that many useful and interesting patterns can be computed automatically.</p>
			</richtext>
		</abstract>
		<pages>69-72</pages>
		<title type="sharef:primaryTitle">Computable Social Patterns from Sparse Sensor Data</title>
	</reference>
	<reference name="locweb2008" src="bibtex:proceedings" src-info="bibtex:line-13423" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>Susanne</givenname>
				<surname>Boll</surname>
			</person>
			<person>
				<givenname>Erik</givenname>
				<surname>Wilde</surname>
			</person>
		</names>
		<date value="2008-04"/>
		<address type="sharef:placePublished">Beijing, China</address>
		<field type="bibtex:index">LocWeb 2008</field>
		<identifier type="sharef:isbn">978-1-60558-160-6</identifier>
		<field type="bibtex:key">First International Workshop on Location and the Web (LocWeb 2008)</field>
		<title type="sharef:primaryTitle">First International Workshop on Location and the Web (LocWeb 2008)</title>
		<field type="bibtex:topic">www[0.8]</field>
		<identifier type="sharef:uri">http://medien.informatik.uni-oldenburg.de/LocWeb2008/</identifier>
		<identifier type="sharef:uri">http://portal.acm.org/toc.cfm?id=1367798&amp;type=proceeding&amp;coll=ACM&amp;dl=ACM</identifier>
		<identifier type="sharef:uri" resourceType="text/html">http://www.informatik.uni-trier.de/~ley/db/conf/www/locweb2008.html</identifier>
	</reference>
	<reference name="suc09" src="bibtex:inproceedings" src-info="bibtex:line-13444" type="sharef:inproceedings" crossref="www2009">
		<names type="sharef:author">
			<person>
				<givenname>Fabian M.</givenname>
				<surname>Suchanek</surname>
			</person>
			<person>
				<givenname>Mauro</givenname>
				<surname>Sozio</surname>
			</person>
			<person>
				<givenname>Gerhard</givenname>
				<surname>Weikum</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>This paper presents SOFIE, a system for automated ontology extension. SOFIE can parse natural language documents, extract ontological facts from them and link the facts into an ontology. SOFIE uses logical reasoning on the existing knowledge and on the new knowledge in order to disambiguate words to their most probable meaning, to reason on the meaning of text patterns and to take into account world knowledge axioms. This allows SOFIE to check the plausibility of hypotheses and to avoid inconsistencies with the ontology. The framework of SOFIE unites the paradigms of pattern matching, word sense disambiguation and ontological reasoning in one unified model. Our experiments show that SOFIE delivers high-quality output, even from unstructured Internet documents.</p>
			</richtext>
		</abstract>
		<pages>911-920</pages>
		<title type="sharef:primaryTitle">SOFIE: A Self-Organizing Framework for Information Extraction</title>
		<identifier type="sharef:uri" resourceType="application/pdf">http://suchanek.name/work/publications/www2009.pdf</identifier>
		<identifier type="sharef:uri" resourceType="application/pdf">http://www2009.org/proceedings/pdf/p631.pdf</identifier>
	</reference>
	<reference name="pau09a" src="bibtex:inproceedings" src-info="bibtex:line-13454" type="sharef:inproceedings" crossref="www2009">
		<names type="sharef:author">
			<person>
				<givenname>Cesare</givenname>
				<surname>Pautasso</surname>
			</person>
			<person>
				<givenname>Erik</givenname>
				<surname>Wilde</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Loose coupling is often quoted as a desirable property of systems architectures. One of the main goals of building systems using Web technologies is to achieve loose coupling. However, given the lack of a widely accepted definition of this term, it becomes hard to use coupling as a criterion to evaluate alternative Web technology choices, as all options may exhibit, and claim to provide, some kind of "loose" coupling effects. This paper presents a systematic study of the degree of coupling found in service-oriented systems based on a multi-faceted approach. Thanks to the metric introduced in this paper, coupling is no longer a one-dimensional concept with loose coupling found somewhere in between tight coupling and no coupling. The paper shows how the metric can be applied to real-world examples in order to support and improve the design process of service-oriented systems.</p>
			</richtext>
		</abstract>
		<pages>911-920</pages>
		<title type="sharef:primaryTitle">Why is the Web Loosely Coupled? A Multi-Faceted Metric for Service Design</title>
		<field type="bibtex:topic">soa[0.9] rest[0.8] ws-star[0.8] rpc[0.8]</field>
		<identifier type="sharef:uri">http://dret.net/netdret/publications#pau09a</identifier>
		<identifier type="sharef:uri" resourceType="application/pdf">http://www2009.org/proceedings/pdf/p911.pdf</identifier>
	</reference>
	<reference name="lud09" src="bibtex:inproceedings" src-info="bibtex:line-13465" type="sharef:inproceedings" crossref="www2009">
		<names type="sharef:author">
			<person>
				<givenname>Heiko</givenname>
				<surname>Ludwig</surname>
			</person>
			<person>
				<givenname>Jim</givenname>
				<surname>Laredo</surname>
			</person>
			<person>
				<givenname>Kamal</givenname>
				<surname>Bhattacharya</surname>
			</person>
			<person>
				<givenname>Liliana</givenname>
				<surname>Pasquale</surname>
			</person>
			<person>
				<givenname>Bruno</givenname>
				<surname>Wassermann</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Applications increasingly make use of the distributed platform that the World Wide Web provides — be it as a Software-as-a-Service such as salesforce.com, an application infrastructure such as facebook.com, or a computing infrastructure such as a "cloud". A common characteristic of applications of this kind is that they are deployed on infrastructure or make use of components that reside in different management domains. Current service management approaches and systems, however, often rely on a centrally managed configuration management database (CMDB), which is the basis for centrally orchestrated service management processes, in particular change management and incident management. The distribution of management responsibility of WWW based applications requires a decentralized approach to service management. This paper proposes an approach of decentralized service management based on distributed configuration management and service process co-ordination, making use RESTful access to configuration information and ATOM-based distribution of updates as a novel foundation for service management processes.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/1526709.1526834</identifier>
		<pages>931-940</pages>
		<title type="sharef:primaryTitle">REST-based Management of Loosely Coupled Services</title>
		<identifier type="sharef:uri" resourceType="application/pdf">http://www2009.org/proceedings/pdf/p931.pdf</identifier>
	</reference>
	<reference name="kri09" src="bibtex:inproceedings" src-info="bibtex:line-13475" type="sharef:inproceedings" crossref="www2009">
		<names type="sharef:author">
			<person>
				<givenname>Balachander</givenname>
				<surname>Krishnamurthy</surname>
			</person>
			<person>
				<givenname>Craig E.</givenname>
				<surname>Wills</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>For the last few years we have studied the diffusion of private information about users as they visit various Web sites triggering data gathering aggregation by third parties. This paper reports on our longitudinal study consisting of multiple snapshots of our examination of such diffusion over four years. We examine the various technical ways by which third-party aggregators acquire data and the depth of user-related information acquired. We study techniques for protecting against this privacy diffusion as well as limitations of such techniques. We introduce the concept of secondary privacy damage. Our results show increasing aggregation of user-related data by a steadily decreasing number of entities. A handful of companies are able to track users' movement across almost all of the popular Web sites. Virtually all the protection techniques have significant limitations highlighting the seriousness of the problem and the need for alternate solutions.</p>
			</richtext>
		</abstract>
		<pages>541-550</pages>
		<title type="sharef:primaryTitle">Privacy Diffusion on the Web: A Longitudinal Perspective</title>
		<field type="bibtex:topic">cookies[0.9] javascript[0.9]</field>
		<identifier type="sharef:uri" resourceType="application/pdf">http://www2009.org/proceedings/pdf/p541.pdf</identifier>
	</reference>
	<reference name="sch09a" src="bibtex:inproceedings" src-info="bibtex:line-13485" type="sharef:inproceedings" crossref="www2009">
		<names type="sharef:author">
			<person>
				<givenname>Uri</givenname>
				<surname>Schonfeld</surname>
			</person>
			<person>
				<givenname>Narayanan</givenname>
				<surname>Shivakumar</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Comprehensive coverage of the public web is crucial to web search engines. Search engines use crawlers to retrieve pages and then discover new ones by extracting the pages' outgoing links. However, the set of pages reachable from the publicly linked web is estimated to be significantly smaller than the invisible web, the set of documents that have no incoming links and can only be retrieved through web applications and web forms. The Sitemaps protocol is a fast-growing web protocol supported jointly by major search engines to help content creators and search engines unlock this hidden data by making it available to search engines. In this paper, we perform a detailed study of how "classic" discovery crawling compares with Sitemaps, in key measures such as coverage and freshness over key representative websites as well as over billions of URLs seen at Google. We observe that Sitemaps and discovery crawling complement each other very well, and offer different tradeoffs.</p>
			</richtext>
		</abstract>
		<pages>991-1000</pages>
		<title type="sharef:primaryTitle">Sitemaps: Above and Beyond the Crawl of Duty</title>
		<identifier type="sharef:uri" resourceType="application/pdf">http://www2009.org/proceedings/pdf/p991.pdf</identifier>
	</reference>
	<reference name="bay09" src="bibtex:inproceedings" src-info="bibtex:line-13494" type="sharef:inproceedings" crossref="www2009p">
		<names type="sharef:author">
			<person>
				<givenname>Eda</givenname>
				<surname>Baykan</surname>
			</person>
			<person>
				<givenname>Monika</givenname>
				<surname>Henzinger</surname>
			</person>
			<person>
				<givenname>Ludmila</givenname>
				<surname>Marian</surname>
			</person>
			<person>
				<givenname>Ingmar</givenname>
				<surname>Weber</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Given only the URL of a web page, can we identify its topic? This is the question that we examine in this paper. Usually, web pages are classified using their content, but a URL-only classifier is preferable, (i) when speed is crucial, (ii) to enable content filtering before an (objectionable) web page is downloaded, (iii) when a page's content is hidden in images, (iv) to annotate hyperlinks in a personalized web browser, without fetching the target page, and (v) when a focused crawler wants to infer the topic of a target page before devoting bandwidth to download it. We apply a machine learning approach to the topic identification task and evaluate its performance in extensive experiments on categorized web pages from the Open Directory Project (ODP). When training separate binary classifiers for each topic, we achieve typical F-measure values between 80 and 85, and a typical precision of around 85. We also ran experiments on a small data set of university web pages. For the task of classifying these pages into faculty, student, course and project pages, our methods improve over previous approaches by 13.8 points of F-measure.</p>
			</richtext>
		</abstract>
		<pages>1109-1110</pages>
		<title type="sharef:primaryTitle">Purely URL-based Topic Classification</title>
		<identifier type="sharef:uri" resourceType="application/pdf">http://www2009.org/proceedings/pdf/p1109.pdf</identifier>
	</reference>
	<reference name="www2009p" src="bibtex:proceedings" src-info="bibtex:line-13503" type="sharef:proceedings">
		<date value="2009-04"/>
		<address type="sharef:placePublished">Madrid, Spain</address>
		<field type="bibtex:key">18th International World Wide Web Conference Posters</field>
		<publisher>ACM Press</publisher>
		<title type="sharef:primaryTitle">18th International World Wide Web Conference Posters</title>
		<field type="bibtex:topic">www[0.8]</field>
	</reference>
	<reference name="www2009" src="bibtex:proceedings" src-info="bibtex:line-13514" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>Juan</givenname>
				<surname>Quemada</surname>
			</person>
			<person>
				<givenname>Gonzalo</givenname>
				<surname>León</surname>
			</person>
			<person>
				<givenname>Yoëlle S.</givenname>
				<surname>Maarek</surname>
			</person>
			<person>
				<givenname>Wolfgang</givenname>
				<surname>Nejdl</surname>
			</person>
		</names>
		<date value="2009-04"/>
		<address type="sharef:placePublished">Madrid, Spain</address>
		<field type="bibtex:key">18th International World Wide Web Conference</field>
		<publisher>ACM Press</publisher>
		<title type="sharef:primaryTitle">18th International World Wide Web Conference</title>
		<field type="bibtex:topic">www[0.8]</field>
		<identifier type="sharef:uri" resourceType="text/html">http://www.informatik.uni-trier.de/~ley/db/conf/www/www2009.html</identifier>
	</reference>
	<reference name="kle10" src="bibtex:inproceedings" src-info="bibtex:line-13531" type="sharef:inproceedings" crossref="www2010">
		<names type="sharef:author">
			<person>
				<givenname>Max</givenname>
				<surname>Van Kleek</surname>
			</person>
			<person>
				<givenname>Brennan</givenname>
				<surname>Moore</surname>
			</person>
			<person>
				<givenname>David</givenname>
				<surname>Karger</surname>
			</person>
			<person>
				<givenname>Paul</givenname>
				<surname>André</surname>
			</person>
			<person>
				<givenname>Monica C.</givenname>
				<surname>Schraefel</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>The transition of personal information management (PIM) tools off the desktop to the Web presents an opportunity to augment these tools with capabilities provided by the wealth of real-time information readily available. In this paper, we describe a next-generation personal information assistance engine that lets end-users delegate to it various simple context- and activity-reactive tasks and reminders. Our system, Atomate, treats RSS/ATOM feeds from social networking and life-tracking sites as sensor streams, integrating information from such feeds into a simple unified RDF world model representing people, places and things and their time-varying states and activities. Combined with other information sources on the web, including the user's online calendar, web-based e-mail client, news feeds and messaging services, Atomate can be made to automatically carry out a variety of simple tasks for the user, ranging from context-aware filtering and messaging, to sharing and social coordination actions. Atomate's open architecture and world model easily accommodate new information sources and actions via the addition of feeds and web services. To make routine use of the system easy for non-programmers, Atomate provides a constrained-input natural language interface (CNLI) for behavior specification, and a direct-manipulation interface for inspecting and updating its world model.</p>
			</richtext>
		</abstract>
		<pages>951-960</pages>
		<title type="sharef:primaryTitle">Atomate It! End-user Context-Sensitive Automation using Heterogeneous Information Sources on the Web</title>
		<identifier type="sharef:uri" resourceType="application/pdf">http://people.csail.mit.edu/emax/papers/atomate-www2010-camera.pdf</identifier>
	</reference>
	<reference name="kwa10" src="bibtex:inproceedings" src-info="bibtex:line-13540" type="sharef:inproceedings" crossref="www2010">
		<names type="sharef:author">
			<person>
				<givenname>Haewoon</givenname>
				<surname>Kwak</surname>
			</person>
			<person>
				<givenname>Changhyun</givenname>
				<surname>Lee</surname>
			</person>
			<person>
				<givenname>Hosung</givenname>
				<surname>Park</surname>
			</person>
			<person>
				<givenname>Sue</givenname>
				<surname>Moon</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Twitter, a microblogging service less than three years old, commands more than 41 million users as of July 2009 and is growing fast. Twitter users tweet about any topic within the 140-character limit and follow others to receive their tweets. The goal of this paper is to study the topological characteristics of Twitter and its power as a new medium of information sharing. We have crawled the entire Twitter site and obtained 41.7 million user profiles, 1.47 billion social relations, 4,262 trending topics, and 106 million tweets. In its follower-following topology analysis we have found a non-power-law follower distribution, a short effective diameter, and low reciprocity, which all mark a deviation from known characteristics of human social networks. In order to identify influentials on Twitter, we have ranked users by the number of followers and by PageRank and found two rankings to be similar. Ranking by retweets differs from the previous two rankings, indicating a gap in influence inferred from the number of followers and that from the popularity of one's tweets. We have analyzed the tweets of top trending topics and reported on their temporal behavior and user participation. We have classified the trending topics based on the active period and the tweets and show that the majority (over 85%) of topics are headline news or persistent news in nature. A closer look at retweets reveals that any retweeted tweet is to reach an average of 1,000 users no matter what the number of followers is of the original tweet. Once retweeted, a tweet gets retweeted almost instantly on next hops, signifying fast diffusion of information after the 1st retweet. To the best of our knowledge this work is the first quantitative study on the entire Twittersphere and information diffusion on it.</p>
			</richtext>
		</abstract>
		<pages>591-600</pages>
		<title type="sharef:primaryTitle">What is Twitter, a Social Network or a News Media?</title>
		<identifier type="sharef:uri" resourceType="text/html">http://an.kaist.ac.kr/traces/WWW2010.html</identifier>
	</reference>
	<reference name="ala10a" src="bibtex:inproceedings" src-info="bibtex:line-13549" type="sharef:inproceedings" crossref="www2010">
		<names type="sharef:author">
			<person>
				<givenname>Rosa</givenname>
				<surname>Alarcón</surname>
			</person>
			<person>
				<givenname>Erik</givenname>
				<surname>Wilde</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Service descriptions allow designers to document, understand, and use services, creating new useful and complex services with aggregated business value. Unlike RPC-based services, REST characteristics require a different approach to service description. We present the Resource Linking Language (ReLL) that introduces the concepts of media types, resource types, and link types as first class citizens for a service description. A proof of concept, a crawler called RESTler that crawls RESTful services based on ReLL descriptions, is also presented.</p>
			</richtext>
		</abstract>
		<pages>1051-1052</pages>
		<title type="sharef:primaryTitle">RESTler: Crawling RESTful Services</title>
		<field type="bibtex:topic">rest[0.9] rell[0.9] restler[0.9]</field>
		<identifier type="sharef:uri">http://dret.net/netdret/publications#ala10a</identifier>
	</reference>
	<reference name="mar10a" src="bibtex:inproceedings" src-info="bibtex:line-13559" type="sharef:inproceedings" crossref="www2010">
		<names type="sharef:author">
			<person>
				<givenname>Alexandros</givenname>
				<surname>Marinos</surname>
			</person>
			<person>
				<givenname>Erik</givenname>
				<surname>Wilde</surname>
			</person>
			<person>
				<givenname>Jiannan</givenname>
				<surname>Lu</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Relational databases hold a vast quantity of information and making them accessible to the web is an big challenge. There is a need to make these databases accessible with as little difficulty as possible, opening them up to the power and serendipity of the Web. Our work presents a series of patterns that bridge the relational database model with the architecture of the Web along with an implementation of some of them. The aim is for relational databases to be made accessible with no intermediate steps and no extra metadata required. This approach can vastly increase the data available on the web, therefore making the Web itself all the more powerful, while enabling its users to seamlessly perform tasks that previously required bridging multiple domains and paradigms or were not possible.</p>
			</richtext>
		</abstract>
		<pages>1157-1158</pages>
		<title type="sharef:primaryTitle">HTTP Database Connector (HDBC): RESTful Access to Relational Databases</title>
		<field type="bibtex:topic">rest[0.9] hdbc[0.9]</field>
		<identifier type="sharef:uri">http://dret.net/netdret/publications#mar10a</identifier>
	</reference>
	<reference name="ben10" src="bibtex:inproceedings" src-info="bibtex:line-13569" type="sharef:inproceedings" crossref="www2010">
		<names type="sharef:author">
			<person>
				<givenname>Edward</givenname>
				<surname>Benson</surname>
			</person>
			<person>
				<givenname>Adam</givenname>
				<surname>Marcus</surname>
			</person>
			<person>
				<givenname>David</givenname>
				<surname>Karger</surname>
			</person>
			<person>
				<givenname>Samuel</givenname>
				<surname>Madden</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>We introduce a client-server toolkit called Sync Kit that demonstrates how client-side database storage can improve the performance of data intensive websites. Sync Kit is designed to make use of the embedded relational database defined in the upcoming HTML5 standard to offload some data storage and processing from a web server onto the web browsers to which it serves content. Our toolkit provides various strategies for synchronizing relational database tables between the browser and the web server, along with a client-side template library so that portions web applications may be executed client-side. Unlike prior work in this area, Sync Kit persists both templates and data in the browser across web sessions, increasing the number of concurrent connections a server can handle by up to a factor of four versus that of a traditional server-only web stack and a factor of three versus a recent template caching approach.</p>
			</richtext>
		</abstract>
		<pages>121-130</pages>
		<title type="sharef:primaryTitle">Sync Kit: A Persistent Client-Side Database Caching Toolkit for Data Intensive Websites</title>
		<identifier type="sharef:uri" resourceType="application/pdf">http://db.csail.mit.edu/pubs/sync-kit.pdf</identifier>
	</reference>
	<reference name="www2010" src="bibtex:proceedings" src-info="bibtex:line-13578" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>Michael</givenname>
				<surname>Rappa</surname>
			</person>
			<person>
				<givenname>Paul</givenname>
				<surname>Jones</surname>
			</person>
			<person>
				<givenname>Juliana</givenname>
				<surname>Freire</surname>
			</person>
			<person>
				<givenname>Soumen</givenname>
				<surname>Chakrabarti</surname>
			</person>
		</names>
		<date value="2010-04"/>
		<address type="sharef:placePublished">Raleigh, North Carolina</address>
		<identifier type="sharef:isbn">978-1-60558-799-8</identifier>
		<field type="bibtex:key">19th International World Wide Web Conference</field>
		<publisher>ACM Press</publisher>
		<title type="sharef:primaryTitle">19th International World Wide Web Conference</title>
		<field type="bibtex:topic">www[0.8]</field>
		<identifier type="sharef:uri" resourceType="text/html">http://www.informatik.uni-trier.de/~ley/db/conf/www/www2010.html</identifier>
	</reference>
	<reference name="ant11" src="bibtex:inproceedings" src-info="bibtex:line-13597" type="sharef:inproceedings" crossref="www2011">
		<names type="sharef:author">
			<person>
				<givenname>Demetris</givenname>
				<surname>Antoniades</surname>
			</person>
			<person>
				<givenname>Iasonas</givenname>
				<surname>Polakis</surname>
			</person>
			<person>
				<givenname>Georgios</givenname>
				<surname>Kontaxis</surname>
			</person>
			<person>
				<givenname>Elias</givenname>
				<surname>Athanasopoulos</surname>
			</person>
			<person>
				<givenname>Sotiris</givenname>
				<surname>Ioannidis</surname>
			</person>
			<person>
				<givenname>Evangelos P.</givenname>
				<surname>Markatos</surname>
			</person>
			<person>
				<givenname>Thomas</givenname>
				<surname>Karagiannis</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Short URLs have become ubiquitous. Especially popular within social networking services, short URLs have seen a significant increase in their usage over the past years, mostly due to Twitter's restriction of message length to 140 characters. In this paper, we provide a first characterization on the usage of short URLs. Specifically, our goal is to examine the content short URLs point to, how they are published, their popularity and activity over time, as well as their potential impact on the performance of the web. Our study is based on traces of short URLs as seen from two different perspectives: i) collected through a large-scale crawl of URL shortening services, and ii) collected by crawling Twitter messages. The former provides a general characterization on the usage of short URLs, while the latter provides a more focused view on how certain communities use shortening services. Our analysis highlights that domain and website popularity, as seen from short URLs, significantly differs from the distributions provided by well publicised services such as Alexa. The set of most popular websites pointed to by short URLs appears stable over time, despite the fact that short URLs have a limited high popularity lifetime. Surprisingly short URLs are not ephemeral, as a significant fraction, roughly 50%, appears active for more than three months. Overall, our study emphasizes the fact that short URLs reflect an "alternative" web and, hence, provide an additional view on web usage and content consumption complementing traditional measurement sources. Furthermore, our study reveals the need for alternative shortening architectures that will eliminate the non-negligible performance penalty imposed by today's shortening services.</p>
			</richtext>
		</abstract>
		<pages>715-724</pages>
		<title type="sharef:primaryTitle">we.b: The web of short URLs</title>
		<identifier type="sharef:uri" resourceType="application/pdf">http://www.www2011india.com/proceeding/proceedings/p715.pdf</identifier>
	</reference>
	<reference name="liu11b" src="bibtex:inproceedings" src-info="bibtex:line-13606" type="sharef:inproceedings" crossref="www2011companion">
		<names type="sharef:author">
			<person>
				<givenname>Yiming</givenname>
				<surname>Liu</surname>
			</person>
			<person>
				<givenname>Rui</givenname>
				<surname>Yang</surname>
			</person>
			<person>
				<givenname>Erik</givenname>
				<surname>Wilde</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>User now interact with multiple location-based services (LBS) through a myriad set of location-aware devices and interfaces. However, current LBS tend to be centralized silos with ad-hoc APIs, which limits potential for information sharing and reuse. Further, LBS subscriptions and user experiences are not easily portable across devices. We propose a general architecture for providing open and decentralized access to LBS, based on Tiled Feeds — a RESTful protocol for access and interactions with LBS using feeds, and Feed Subscription Management (FSM) — a generalized feed-based service management protocol. We describe two client designs, and demonstrate how they enable standardized access to LBS services, promote information sharing and mashup creation, and offer service management across various types of location-enabled devices.</p>
			</richtext>
		</abstract>
		<pages>79-80</pages>
		<title type="sharef:primaryTitle">Open and Decentralized Access across Location-Based Services</title>
		<identifier type="sharef:uri">http://dret.net/netdret/publications#liu11b</identifier>
		<identifier type="sharef:uri" resourceType="application/pdf">http://www.www2011india.com/proceeding/companion/p79.pdf</identifier>
	</reference>
	<reference name="www2011" src="bibtex:proceedings" src-info="bibtex:line-13616" type="sharef:proceedings">
		<date value="2011-03"/>
		<address type="sharef:placePublished">Hyderabad, India</address>
		<field type="bibtex:key">20th International World Wide Web Conference</field>
		<publisher>ACM Press</publisher>
		<title type="sharef:primaryTitle">20th International World Wide Web Conference</title>
		<field type="bibtex:topic">www[0.8]</field>
		<identifier type="sharef:uri" resourceType="text/html">http://www.informatik.uni-trier.de/~ley/db/conf/www/www2011.html</identifier>
		<identifier type="sharef:uri" resourceType="text/html">http://www.www2011india.com/proceeding/forms/pcontents.htm</identifier>
	</reference>
	<reference name="www2011companion" src="bibtex:proceedings" src-info="bibtex:line-13629" type="sharef:proceedings">
		<date value="2011-03"/>
		<address type="sharef:placePublished">Hyderabad, India</address>
		<field type="bibtex:key">20th International World Wide Web Conference</field>
		<publisher>ACM Press</publisher>
		<title type="sharef:primaryTitle">20th International World Wide Web Conference Companion</title>
		<field type="bibtex:topic">www[0.8]</field>
		<identifier type="sharef:uri" resourceType="text/html">http://www.www2011india.com/proceeding/forms/ccontents.htm</identifier>
	</reference>
	<reference name="coo10a" src="bibtex:inproceedings" src-info="bibtex:line-13645" type="sharef:inproceedings" crossref="websci10">
		<names type="sharef:author">
			<person>
				<givenname>Alissa</givenname>
				<surname>Cooper</surname>
			</person>
			<person>
				<givenname>Henning</givenname>
				<surname>Schulzrinne</surname>
			</person>
			<person>
				<givenname>Erik</givenname>
				<surname>Wilde</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>The Web is on its way to becoming a location-aware information system. This transition causes some technical and policy challenges in terms of both design and coordination with existing approaches in this area. In this paper we propose that managing the transition to location-awareness (and some other aspects) requires a more strategic approach than has been taken thus far.</p>
			</richtext>
		</abstract>
		<title type="sharef:primaryTitle">Challenges for the Location-Aware Web</title>
		<identifier type="sharef:uri">http://dret.net/netdret/publications#coo10a</identifier>
	</reference>
	<reference name="websci10" src="bibtex:proceedings" src-info="bibtex:line-13653" type="sharef:proceedings">
		<date value="2010-04"/>
		<address type="sharef:placePublished">Raleigh, North Carolina</address>
		<field type="bibtex:index">WebSci 2010</field>
		<field type="bibtex:key">Web Science Conference 2010 (WebSci 10)</field>
		<title type="sharef:primaryTitle">Web Science Conference 2010 (WebSci 10)</title>
		<identifier type="sharef:uri">http://www.websci10.org/</identifier>
	</reference>
	<reference name="gui09a" src="bibtex:inproceedings" src-info="bibtex:line-13668" type="sharef:inproceedings" crossref="mem2009">
		<names type="sharef:author">
			<person>
				<givenname>Dominique</givenname>
				<surname>Guinard</surname>
			</person>
			<person>
				<givenname>Vlad</givenname>
				<surname>Trifa</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>In the "Internet of Things" vision, the physical world becomes integrable with computer networks. Embedded computers or visual markers on everyday objects allow things and information about them to be accessible in the digital world. However, this integration is based on competing standards and requires custom solutions, thus requires extensive time and technical expertise. Based on the success of Web 2.0 mashup applications, we propose a similar approach for integrating real-world devices to the Web, allowing for them to be easily combined with other virtual and physical resources. In this paper we discuss possible integration method, in particular how the REST principles can be applied to embedded devices. Then we illustrate these principles with two concrete implementations: on the Sun SPOT platform and on the Ploggs wireless energy monitors. Finally, we show how RESTful interactions can be leveraged to quickly create new prototypes and mashups that combine the physical and virtual world.</p>
			</richtext>
		</abstract>
		<title type="sharef:primaryTitle">Towards the Web of Things: Web Mashups for Embedded Devices</title>
		<identifier type="sharef:uri" resourceType="application/pdf">http://www.vs.inf.ethz.ch/publ/papers/dguinard_09_WOTMashups.pdf</identifier>
	</reference>
	<reference name="mem2009" src="bibtex:proceedings" src-info="bibtex:line-13676" type="sharef:proceedings">
		<date value="2009-04"/>
		<address type="sharef:placePublished">Madrid, Spain</address>
		<field type="bibtex:key">Second Workshop on Mashups, Enterprise Mashups and Lightweight Composition on the Web</field>
		<title type="sharef:primaryTitle">Second Workshop on Mashups, Enterprise Mashups and Lightweight Composition on the Web</title>
		<identifier type="sharef:uri">http://www.integror.net/mem2009/</identifier>
	</reference>
	<reference name="gui10b" src="bibtex:inproceedings" src-info="bibtex:line-13690" type="sharef:inproceedings" crossref="wot2010">
		<names type="sharef:author">
			<person>
				<givenname>Dominique</givenname>
				<surname>Guinard</surname>
			</person>
			<person>
				<givenname>Erik</givenname>
				<surname>Wilde</surname>
			</person>
			<person>
				<givenname>Vlad</givenname>
				<surname>Trifa</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>The world of embedded devices has experienced radical changes over the past few years, as more and more everyday and real-world objects can now easily connect to the Internet. This convergence of physical computing devices (wireless sensor networks, mobile phones, embedded computers, etc.) and the Internet provides new design opportunities and challenges. The Internet of Things community has mainly focused on establishing connectivity in a variety of challenging and constrained networking environments, which is a necessary step for a more networked world. The next logical step in the evolution of pervasive computing builds on top of network connectivity by focusing on the application layer: how to develop ubiquitous computing applications on top of heterogeneous environments? The Web of Things is the vision that brings embedded devices into the Web by leveraging existing Web standards to design and build application protocols to interact with the physical world.</p>
			</richtext>
		</abstract>
		<title type="sharef:primaryTitle">Message from the Workshop Chairs</title>
		<identifier type="sharef:uri">http://www.informatik.uni-trier.de/~ley/db/conf/percom/percomw2010.html#GuinardWT10</identifier>
	</reference>
	<reference name="wot2010" src="bibtex:proceedings" src-info="bibtex:line-13698" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>Dominique</givenname>
				<surname>Guinard</surname>
			</person>
			<person>
				<givenname>Erik</givenname>
				<surname>Wilde</surname>
			</person>
			<person>
				<givenname>Vlad</givenname>
				<surname>Trifa</surname>
			</person>
		</names>
		<date value="2010-03"/>
		<address type="sharef:placePublished">Mannheim, Germany</address>
		<identifier type="sharef:doi">10.1109/PERCOMW.2010.5470588</identifier>
		<identifier type="sharef:isbn">978-1-4244-6605-4</identifier>
		<field type="bibtex:key">First International Workshop on the Web of Things (WoT 2010)</field>
		<title type="sharef:primaryTitle">First International Workshop on the Web of Things (WoT 2010)</title>
		<identifier type="sharef:uri">http://www.webofthings.com/wot/2010/</identifier>
	</reference>
	<reference name="dic08" src="bibtex:inproceedings" src-info="bibtex:line-13715" type="sharef:inproceedings" crossref="iot2008">
		<names type="sharef:author">
			<person>
				<givenname>Robert F.</givenname>
				<surname>Dickerson</surname>
			</person>
			<person>
				<givenname>Jiakang</givenname>
				<surname>Lu</surname>
			</person>
			<person>
				<givenname>Jian</givenname>
				<surname>Lu</surname>
			</person>
			<person>
				<givenname>Kamin</givenname>
				<surname>Whitehouse</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>RFIDs, cell phones, and sensor nodes produce streams of sensor data that help computers monitor, react to, and affect the changing status of the physical world. Our goal in this paper is to allow these data streams to be first-class citizens on the World Wide Web. We present a new Web primitive called stream feeds that extend traditional XML feeds such as blogs and Podcasts to accommodate the large size, high frequency, and real-time nature of sensor streams. We demonstrate that our extensions improve the scalability and efficiency over the traditional model for Web feeds such as blogs and Podcasts, particularly when feeds are being used for in-network data fusion.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1007/978-3-540-78731-0_23</identifier>
		<pages>360-375</pages>
		<title type="sharef:primaryTitle">Stream Feeds — An Abstraction for the World Wide Sensor Web</title>
		<identifier type="sharef:uri" resourceType="application/pdf">http://www.cs.virginia.edu/~whitehouse/research/streamSearch/dickerson08streamFeeds.pdf</identifier>
	</reference>
	<reference name="iot2008" src="bibtex:proceedings" src-info="bibtex:line-13725" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>Christian</givenname>
				<surname>Flörkemeier</surname>
			</person>
			<person>
				<givenname>Marc</givenname>
				<surname>Langheinrich</surname>
			</person>
			<person>
				<givenname>Elgar</givenname>
				<surname>Fleisch</surname>
			</person>
			<person>
				<givenname>Friedemann</givenname>
				<surname>Mattern</surname>
			</person>
			<person>
				<givenname>Sanjay E.</givenname>
				<surname>Sarma</surname>
			</person>
		</names>
		<date value="2008-03"/>
		<address type="sharef:placePublished">Zürich, Switzerland</address>
		<identifier type="sharef:isbn">978-3-540-78730-3</identifier>
		<field type="bibtex:key">First International Conference on the Internet of Things (IoT 2008)</field>
		<title type="sharef:primaryTitle">First International Conference on the Internet of Things (IoT 2008)</title>
		<identifier type="sharef:uri">http://www.iot2008.org/</identifier>
		<identifier type="sharef:uri" resourceType="text/html">http://www.informatik.uni-trier.de/~ley/db/conf/iot/iot2008.html</identifier>
	</reference>
	<reference name="gui10c" src="bibtex:inproceedings" src-info="bibtex:line-13742" type="sharef:inproceedings" crossref="iot2010">
		<names type="sharef:author">
			<person>
				<givenname>Dominique</givenname>
				<surname>Guinard</surname>
			</person>
			<person>
				<givenname>Vlad</givenname>
				<surname>Trifa</surname>
			</person>
			<person>
				<givenname>Erik</givenname>
				<surname>Wilde</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Many efforts are centered around networking smart things from the physical world (e.g. RFID, wireless sensor and actuator networks, embedded devices) on a larger scale. Rather than exposing real-world data and functionality through proprietary and tightly-coupled systems we propose to make them an integral part of the Web. As a result, smart things become easier to build upon. Popular Web languages (e.g. HTML, URI, JavaScript, PHP) can be used to build applications involving smart things and users can leverage well-known Web mechanisms (e.g. browsing, searching, bookmarking, caching, linking) to interact and share things. In this paper, we begin by describing a Web of Things architecture and best-practices rooted on the RESTful principles that contributed to the popular success, scalability, and evolvability of the traditional Web. We then discuss several prototypes implemented using these principles to connect environmental sensor nodes and an energy monitoring systems to the World Wide Web. We finally show how Web-enabled things can be used in lightweight ad-hoc applications called "physical mashups".</p>
			</richtext>
		</abstract>
		<title type="sharef:primaryTitle">A Resource Oriented Architecture for the Web of Things</title>
		<identifier type="sharef:uri">http://dret.net/netdret/publications#gui10c</identifier>
	</reference>
	<reference name="iot2010" src="bibtex:proceedings" src-info="bibtex:line-13750" type="sharef:proceedings">
		<date value="2010-11"/>
		<address type="sharef:placePublished">Tokyo, Japan</address>
		<field type="bibtex:key">Second International Conference on the Internet of Things (IoT 2010)</field>
		<title type="sharef:primaryTitle">Second International Conference on the Internet of Things (IoT 2010)</title>
		<identifier type="sharef:uri">http://www.iot2010.org/</identifier>
		<identifier type="sharef:uri" resourceType="text/html">http://www.informatik.uni-trier.de/~ley/db/conf/iot/iot2010.html</identifier>
	</reference>
	<reference name="sta10" src="bibtex:inproceedings" src-info="bibtex:line-13765" type="sharef:inproceedings" crossref="sfsw2010">
		<names type="sharef:author">
			<person>
				<givenname>Claus</givenname>
				<surname>Stadler</surname>
			</person>
			<person>
				<givenname>Michael</givenname>
				<surname>Martin</surname>
			</person>
			<person>
				<givenname>Jens</givenname>
				<surname>Lehmann</surname>
			</person>
			<person>
				<givenname>Sebastian</givenname>
				<surname>Hellmann</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Wikipedia is one of the largest public information spaces with a huge user community, which collaboratively works on the largest online encyclopedia. Their users add or edit up to 150 thousand wiki pages per day. The DBpedia project extracts RDF from Wikipedia and interlinks it with other knowledge bases. In the DBpedia live extraction mode, Wikipedia edits are instantly processed to update information in DBpedia. Due to the high number of edits and the growth of Wikipedia, the update process has to be very efficient and scalable. In this paper, we present different strategies to tackle this challenging problem and describe how we modified the DBpedia live extraction algorithm to work more efficiently.</p>
			</richtext>
		</abstract>
		<title type="sharef:primaryTitle">Update Strategies for DBpedia Live</title>
		<field type="bibtex:topic">dbpedia[0.9]</field>
		<identifier type="sharef:uri" resourceType="application/pdf">http://www.semanticscripting.org/SFSW2010/papers/sfsw2010_submission_5.pdf</identifier>
	</reference>
	<reference name="pas10a" src="bibtex:inproceedings" src-info="bibtex:line-13774" type="sharef:inproceedings" crossref="sfsw2010">
		<names type="sharef:author">
			<person>
				<givenname>Alexandre</givenname>
				<surname>Passant</surname>
			</person>
			<person>
				<givenname>Pablo N.</givenname>
				<surname>Mendes</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>With the growing numbers of status update websites and related wrappers, initiatives modelling sensor data in RDF, as well as the dynamic nature of many Linked Data exporters, there is a need for protocols enabling real-time notification and broadcasting of RDF data updates. In this paper we present a flexible approach that provides such notifications to be delivered in real-time to any RSS or Atom reader. Our framework enables the active delivery of SPARQL query results through the PubSubHubbub (PuSH) protocol upon the arrival of new information in RDF stores. Our open source implementation can be plugged on any SPARQL endpoint and can directly reuse PuSH hubs that are already deployed in scalable clouds (e.g. Google's).</p>
			</richtext>
		</abstract>
		<title type="sharef:primaryTitle">sparqlPuSH: Proactive notification of data updates in RDF stores using PubSubHubbub</title>
		<field type="bibtex:topic">pubsubhubbub[0.9] sparql[0.9]</field>
		<identifier type="sharef:uri" resourceType="application/pdf">http://semanticscripting.org/SFSW2010/papers/sfsw2010_submission_6.pdf</identifier>
	</reference>
	<reference name="sfsw2010" src="bibtex:proceedings" src-info="bibtex:line-13783" type="sharef:proceedings">
		<date value="2010-05"/>
		<address type="sharef:placePublished">Crete, Greece</address>
		<field type="bibtex:key">6th Workshop on Scripting and Development for the Semantic Web</field>
		<title type="sharef:primaryTitle">6th Workshop on Scripting and Development for the Semantic Web</title>
		<identifier type="sharef:uri">http://www.semanticscripting.org/SFSW2010/</identifier>
	</reference>
	<reference name="ale09" src="bibtex:inproceedings" src-info="bibtex:line-13797" type="sharef:inproceedings" crossref="ldow2009">
		<names type="sharef:author">
			<person>
				<givenname>Keith</givenname>
				<surname>Alexander</surname>
			</person>
			<person>
				<givenname>Richard</givenname>
				<surname>Cyganiak</surname>
			</person>
			<person>
				<givenname>Michael</givenname>
				<surname>Hausenblas</surname>
			</person>
			<person>
				<givenname>Jun</givenname>
				<surname>Zhaox</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>In this paper we discuss the design and implementation of voiD, the "Vocabulary Of Interlinked Datasets", a vocabulary that allows to formally describe linked RDF datasets. We report on use cases for voiD, the current state of the specification and its potential applications in the context of linked datasets.</p>
			</richtext>
		</abstract>
		<title type="sharef:primaryTitle">Describing Linked Datasets</title>
		<field type="bibtex:topic">void[0.9]</field>
		<identifier type="sharef:uri" resourceType="application/pdf">http://events.linkeddata.org/ldow2009/papers/ldow2009_paper20.pdf</identifier>
	</reference>
	<reference name="vol09" src="bibtex:inproceedings" src-info="bibtex:line-13806" type="sharef:inproceedings" crossref="ldow2009">
		<names type="sharef:author">
			<person>
				<givenname>Julius</givenname>
				<surname>Volz</surname>
			</person>
			<person>
				<givenname>Christian</givenname>
				<surname>Bizer</surname>
			</person>
			<person>
				<givenname>Martin</givenname>
				<surname>Gaedke</surname>
			</person>
			<person>
				<givenname>Georgi</givenname>
				<surname>Kobilarov</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>The Web of Data is built upon two simple ideas: Employ the RDF data model to publish structured data on the Web and to set explicit RDF links between entities within different data sources. This paper presents the Silk Link Discovery Framework, a tool for finding relationships between entities within different data sources. Data publishers can use Silk to set RDF links from their data sources to other data sources on the Web. Silk features a declarative language for specifying which types of RDF links should be discovered between data sources as well as which conditions entities must fulfill in order to be interlinked. Link conditions may be based on various similarity metrics and can take the graph around entities into account, which is addressed using a path-based selector language. Silk accesses data sources over the SPARQL protocol and can thus be used without having to replicate datasets locally.</p>
			</richtext>
		</abstract>
		<title type="sharef:primaryTitle">Silk — A Link Discovery Framework for the Web of Data</title>
		<field type="bibtex:topic">silk[1]</field>
		<identifier type="sharef:uri" resourceType="application/pdf">http://events.linkeddata.org/ldow2009/papers/ldow2009_paper13.pdf</identifier>
	</reference>
	<reference name="ldow2009" src="bibtex:proceedings" src-info="bibtex:line-13815" type="sharef:proceedings">
		<date value="2009-04"/>
		<address type="sharef:placePublished">Madrid, Spain</address>
		<field type="bibtex:key">2nd Workshop on Linked Data on the Web</field>
		<title type="sharef:primaryTitle">2nd Workshop on Linked Data on the Web</title>
		<identifier type="sharef:uri">http://events.linkeddata.org/ldow2009/</identifier>
	</reference>
	<reference name="som10a" src="bibtex:inproceedings" src-info="bibtex:line-13829" type="sharef:inproceedings" crossref="ldow2010">
		<names type="sharef:author">
			<person>
				<givenname>Herbert</givenname>
				<surname>Van de Sompel</surname>
			</person>
			<person>
				<givenname>Robert</givenname>
				<surname>Sanderson</surname>
			</person>
			<person>
				<givenname>Michael L.</givenname>
				<surname>Nelson</surname>
			</person>
			<person>
				<givenname>Lyudmila L.</givenname>
				<surname>Balakireva</surname>
			</person>
			<person>
				<givenname>Harihar</givenname>
				<surname>Shankar</surname>
			</person>
			<person>
				<givenname>Scott</givenname>
				<surname>Ainsworth</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Dereferencing a URI returns a representation of the current state of the resource identified by that URI. But, on the Web representations of prior states of a resource are also available, for example, as resource versions in Content Management Systems or archival resources in Web Archives such as the Internet Archive. This paper introduces a resource versioning mechanism that is fully based on HTTP and uses datetime as a global version indicator. The approach allows "follow your nose" style navigation both from the current time-generic resource to associated time-specific version resources as well as among version resources. The proposed versioning mechanism is congruent with the Architecture of the World Wide Web, and is based on the Memento framework that extends HTTP with transparent content negotiation in the datetime dimension. The paper shows how the versioning approach applies to Linked Data, and by means of a demonstrator built for DBpedia, it also illustrates how it can be used to conduct a time-series analysis across versions of Linked Data descriptions.</p>
			</richtext>
		</abstract>
		<title type="sharef:primaryTitle">An HTTP-Based Versioning Mechanism for Linked Data</title>
		<field type="bibtex:topic">http[0.8]</field>
		<identifier type="sharef:uri">http://arxiv.org/abs/1003.3661</identifier>
	</reference>
	<reference name="ala10b" src="bibtex:inproceedings" src-info="bibtex:line-13838" type="sharef:inproceedings" crossref="ldow2010">
		<names type="sharef:author">
			<person>
				<givenname>Rosa</givenname>
				<surname>Alarcón</surname>
			</person>
			<person>
				<givenname>Erik</givenname>
				<surname>Wilde</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>One of the main goals of the Semantic Web is to extend current human-readable Web resources with semantic information encoded in a machine-processable form. One of its most successful approaches is the Web of Data which by following the principles of Linked Data have made available several data sources compliant with the Semantic Web technologies, such as, RDF  triple stores, and SPARQL endpoints. On the other hand, the set of the architectural principles that underlie the human-readable Web has been conceptualized as the Representational State Transfer (REST) architectural style. In this paper, we distill REST concepts in order to provide a mechanism for describing REST (i.e. human-readable Web) resources and transform them into semantic resources. The strategy  allowed us to harvest already existing Web resources without requiring changes on the original sources, or ad-hoc  interfaces. We illustrate our approach with an application and expect that the presented approach may contribute to the availability of more data sources and become a further step to lower the entry barrier to semantic resources publishing.</p>
			</richtext>
		</abstract>
		<title type="sharef:primaryTitle">Linking Data from RESTful Services</title>
		<field type="bibtex:topic">rest[0.9]</field>
		<identifier type="sharef:uri" resourceType="application/pdf">http://events.linkeddata.org/ldow2009/papers/ldow2009_paper20.pdf</identifier>
	</reference>
	<reference name="umb10a" src="bibtex:inproceedings" src-info="bibtex:line-13847" type="sharef:inproceedings" crossref="ldow2010">
		<names type="sharef:author">
			<person>
				<givenname>Jürgen</givenname>
				<surname>Umbrich</surname>
			</person>
			<person>
				<givenname>Michael</givenname>
				<surname>Hausenblas</surname>
			</person>
			<person>
				<givenname>Aidan</givenname>
				<surname>Hogan</surname>
			</person>
			<person>
				<givenname>Axel</givenname>
				<surname>Polleres</surname>
			</person>
			<person>
				<givenname>Stefan</givenname>
				<surname>Decker</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Datasets in the LOD cloud are far from being static in their nature and how they are exposed. As resources are added and new links are set, applications consuming the data should be able to deal with these changes. In this paper we investigate how LOD datasets change and what sensible measures there are to accommodate dataset dynamics. We compare our findings with traditional, document-centric studies concerning the "freshness" of the document collections and propose metrics for LOD datasets.</p>
			</richtext>
		</abstract>
		<title type="sharef:primaryTitle">Towards Dataset Dynamics: Change Frequency of Linked Open Data Sources</title>
		<identifier type="sharef:uri" resourceType="application/pdf">http://axel.deri.ie/~axepol/publications/umbr-etal-2010.pdf</identifier>
	</reference>
	<reference name="ldow2010" src="bibtex:proceedings" src-info="bibtex:line-13855" type="sharef:proceedings">
		<date value="2010-04"/>
		<address type="sharef:placePublished">Raleigh, North Carolina</address>
		<field type="bibtex:key">Third Workshop on Linked Data on the Web</field>
		<title type="sharef:primaryTitle">Third Workshop on Linked Data on the Web</title>
		<identifier type="sharef:uri">http://events.linkeddata.org/ldow2010/</identifier>
	</reference>
	<reference name="wil09a" src="bibtex:inproceedings" src-info="bibtex:line-13869" type="sharef:inproceedings" crossref="locweb2009">
		<names type="sharef:author">
			<person>
				<givenname>Erik</givenname>
				<surname>Wilde</surname>
			</person>
			<person>
				<givenname>Susanne</givenname>
				<surname>Boll</surname>
			</person>
			<person>
				<givenname>Keith</givenname>
				<surname>Cheverst</surname>
			</person>
			<person>
				<givenname>Peter</givenname>
				<surname>Fröhlich</surname>
			</person>
			<person>
				<givenname>Ross</givenname>
				<surname>Purves</surname>
			</person>
			<person>
				<givenname>Johannes</givenname>
				<surname>Schöning</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Location-Aware Services are becoming increasingly Web-based, as a result of the availability of networked mobile devices and mobile Internet access. The "Location and the Web (LocWeb)" workshop targets the capabilities and constraints of Web-based location-aware services, which can be implemented as browser-based applications, or as native applications using Web services. The focus of this CHI workshop is on developing approaches to handle the complexity of location-aware services, specifically looking at location abstractions, location sharing, context-relevant information, privacy issues, and  interface design. The goal of this workshop is to serve as a starting point for better understanding how the Web has to change to embrace location as a first-level concept, and how these changes are reflected in applications and user interfaces to transform the Web into a platform for location-aware services.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/1507136.1507137</identifier>
		<pages>1-2</pages>
		<title type="sharef:primaryTitle">Second International Workshop on Location and the Web (LocWeb 2009)</title>
		<identifier type="sharef:uri">http://portal.acm.org/citation.cfm?id=1507136.1507137</identifier>
	</reference>
	<reference name="yan09" src="bibtex:inproceedings" src-info="bibtex:line-13879" type="sharef:inproceedings" crossref="locweb2009">
		<names type="sharef:author">
			<person>
				<givenname>Keiji</givenname>
				<surname>Yanai</surname>
			</person>
			<person>
				<givenname>Keita</givenname>
				<surname>Yaegashi</surname>
			</person>
			<person>
				<givenname>Bingyu</givenname>
				<surname>Qiu</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>We propose a novel method to detect cultural differences over the world automatically by using a large amount of geotagged images on the photo sharing Web sites such as Flickr. We employ the state-of-the-art object recognition technique developed in the research community of computer vision to mine representative photos of the given concept for representative local regions from a large-scale unorganized collection of consumer-generated geotagged photos. The results help us understand how objects, scenes, or events corresponding to the same given concept are visually different depending on local regions over the world.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/1507136.1507148</identifier>
		<pages>40-43</pages>
		<title type="sharef:primaryTitle">Detecting Cultural Differences using Consumer-Generated Geotagged Photos</title>
		<identifier type="sharef:uri">http://portal.acm.org/citation.cfm?id=1507136.1507148</identifier>
	</reference>
	<reference name="rei09" src="bibtex:inproceedings" src-info="bibtex:line-13889" type="sharef:inproceedings" crossref="locweb2009">
		<names type="sharef:author">
			<person>
				<givenname>Tumasch</givenname>
				<surname>Reichenbacher</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>In this position paper we describe the concept of geographic relevance and its potential for mobile location-based services employing the mobile Internet. We argue that existing LBS have a too limited concept of location and its application for filtering geographic content. We propose an approach for geographic relevance that extends LBS and location-aware web applications and aims at better supporting mobile users' decision-making based on geographic information. After a short description of an ongoing project, we discuss the different roles of location and the different conceptions of space that can be involved in assessing and representing geographic relevance. Finally we provide a few concluding statements that aim at stimulating a cross-disciplinary discussion about location and its importance for relevance.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/1507136.1507146</identifier>
		<pages>32-35</pages>
		<title type="sharef:primaryTitle">Geographic Relevance in Mobile Services</title>
		<identifier type="sharef:uri">http://portal.acm.org/citation.cfm?id=1507136.1507146</identifier>
	</reference>
	<reference name="boe09" src="bibtex:inproceedings" src-info="bibtex:line-13899" type="sharef:inproceedings" crossref="locweb2009">
		<names type="sharef:author">
			<person>
				<givenname>Matthias</givenname>
				<surname>Böhmer</surname>
			</person>
			<person>
				<givenname>Gernot</givenname>
				<surname>Bauer</surname>
			</person>
			<person>
				<givenname>Wolfgang</givenname>
				<surname>Wicht</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>While the demand for Location-based Services (LBS) is strongly increasing, technical laymen are not yet able to build and provide location-aware applications. This paper presents a radical simplification of the life-cycle of LBSs. An authoring toolkit enables non-technicians to easily develop context-aware mobile applications. In addition, an adaptive user interface makes the consumption of LBSs easier. The platform we present, in covering the whole LBS supply chain, is hiding the complexity of providing and consuming LBSs from the end-users.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/1507136.1507138</identifier>
		<pages>3-5</pages>
		<title type="sharef:primaryTitle">Hiding the Complexity of LBS</title>
		<identifier type="sharef:uri">http://portal.acm.org/citation.cfm?id=1507136.1507138</identifier>
	</reference>
	<reference name="sve09" src="bibtex:inproceedings" src-info="bibtex:line-13909" type="sharef:inproceedings" crossref="locweb2009">
		<names type="sharef:author">
			<person>
				<givenname>Eric-Oluf</givenname>
				<surname>Svee</surname>
			</person>
			<person>
				<givenname>Pedro</givenname>
				<surname>Sanches</surname>
			</person>
			<person>
				<givenname>Markus</givenname>
				<surname>Bylund</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>We propose that the concepts of Time Geography be evaluated as a framework for use within location-oriented services. Originally conceived as a system to describe patterns in human migration, Time Geography is ideally suited for providing the common language and concepts necessary for dialogue within this evolving area. Location-oriented services have been the focus of a great deal of attention, but with research occurring in many disparate disciplines, the lack of a common model that can conceptualize these ideas has not received appropriate attention. To demonstrate its applicability within location-oriented services, we present a research activity which makes explicit use of concepts from Time Geography, with the hope that it can be seen as a tractable and practical solution for several difficulties facing this fast growing area of interest.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/1507136.1507147</identifier>
		<pages>36-39</pages>
		<title type="sharef:primaryTitle">Time Geography Rediscovered: A Common Language for Location-Oriented Services</title>
		<identifier type="sharef:uri">http://portal.acm.org/citation.cfm?id=1507136.1507147</identifier>
	</reference>
	<reference name="man09" src="bibtex:inproceedings" src-info="bibtex:line-13919" type="sharef:inproceedings" crossref="locweb2009">
		<names type="sharef:author">
			<person>
				<givenname>Christian</givenname>
				<surname>Manasseh</surname>
			</person>
			<person>
				<givenname>Katherine</givenname>
				<surname>Ahern</surname>
			</person>
			<person>
				<givenname>Raja</givenname>
				<surname>Sengupta</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>In this paper we present the connected traveler architecture that allows mobile users to personalize the delivery of transportation related content. The widespread use of mobile devices and the increasing availability of wireless Internet present an opportunity for transportation engineers to deliver mobility and safety content to the drivers, pedestrians, and public transit users. Connectedtraveler.org enables this technology by combining the location of the mobile user with pre-defined personalized profiles to improve user experience.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/1507136.1507145</identifier>
		<pages>28-31</pages>
		<title type="sharef:primaryTitle">The Connected Traveler: Using Location and Personalization on Mobile Devices to Improve Transportation</title>
		<identifier type="sharef:uri">http://portal.acm.org/citation.cfm?id=1507136.1507145</identifier>
	</reference>
	<reference name="ehl09" src="bibtex:inproceedings" src-info="bibtex:line-13929" type="sharef:inproceedings" crossref="locweb2009">
		<names type="sharef:author">
			<person>
				<givenname>Patrick</givenname>
				<surname>Ehlen</surname>
			</person>
			<person>
				<givenname>Remi</givenname>
				<surname>Zajac</surname>
			</person>
			<person>
				<givenname>Kotcherlakota Bapa</givenname>
				<surname>Rao</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>In traditional information retrieval, relevance is often judged by comparing the similarity of text in a query to the text of a document returned, reflecting a context-independent relevance relation. But mobile search calls for an expanded approach to assessing similarity and relevance — an approach that is highly attuned to the context-dependent factors that occur when people leave their desks and begin requesting information from different environments and perspectives.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/1507136.1507142</identifier>
		<pages>17-19</pages>
		<title type="sharef:primaryTitle">Location and Relevance</title>
		<identifier type="sharef:uri">http://portal.acm.org/citation.cfm?id=1507136.1507142</identifier>
	</reference>
	<reference name="edw09" src="bibtex:inproceedings" src-info="bibtex:line-13939" type="sharef:inproceedings" crossref="locweb2009">
		<names type="sharef:author">
			<person>
				<givenname>Alistair J.</givenname>
				<surname>Edwardes</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>In this position paper the question of how location is employed in location based services (LBS) is considered. The importance of the notion of location is highlighted as a means of blurring the boundary between forms of experiences that are direct, and sensed in the environment, and those that are indirect, and learned from information. It is suggested that current methods for modeling location are limited by their lack of strong theoretical underpinning. To help bridge this gap the notions of Space, Place, and Region, from geographical theory, are proposed and implications of these for considering location in LBS outlined.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/1507136.1507141</identifier>
		<pages>13-16</pages>
		<title type="sharef:primaryTitle">Geographical Perspectives on Location for Location Based Services</title>
		<identifier type="sharef:uri">http://portal.acm.org/citation.cfm?id=1507136.1507141</identifier>
	</reference>
	<reference name="dot09" src="bibtex:inproceedings" src-info="bibtex:line-13949" type="sharef:inproceedings" crossref="locweb2009">
		<names type="sharef:author">
			<person>
				<givenname>Nick</givenname>
				<surname>Doty</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Microsoft has proposed an identity metasystem to standardize identity services and the principles behind them. A location metasystem can support interoperation between location services, protect users' privacy, and handle issues of granularity. The simple OAuth protocol may be a good model for working towards a location metasystem.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/1507136.1507140</identifier>
		<pages>10-12</pages>
		<title type="sharef:primaryTitle">The Case for a Location Metasystem</title>
		<identifier type="sharef:uri">http://portal.acm.org/citation.cfm?id=1507136.1507140</identifier>
	</reference>
	<reference name="mag09" src="bibtex:inproceedings" src-info="bibtex:line-13959" type="sharef:inproceedings" crossref="locweb2009">
		<names type="sharef:author">
			<person>
				<givenname>Charlotte</givenname>
				<surname>Magnusson</surname>
			</person>
			<person>
				<givenname>Stephen</givenname>
				<surname>Brewster</surname>
			</person>
			<person>
				<givenname>Tapani</givenname>
				<surname>Sarjakoski</surname>
			</person>
			<person>
				<givenname>Samuel</givenname>
				<surname>Roselier</surname>
			</person>
			<person>
				<givenname>L. Tiina</givenname>
				<surname>Sarjakoski</surname>
			</person>
			<person>
				<givenname>Konrad</givenname>
				<surname>Tollmar</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>In this article we give an overview of some challenges in how to make geospatial information more useable and accessible. We also suggest a roadmap for dealing with these challenges — and introduce a new EU project HaptiMap.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/1507136.1507144</identifier>
		<pages>24-27</pages>
		<title type="sharef:primaryTitle">Exploring Future Challenges for Haptic, Audio and Visual Interfaces for Mobile Maps and Location Based Services</title>
		<identifier type="sharef:uri">http://portal.acm.org/citation.cfm?id=1507136.1507144</identifier>
	</reference>
	<reference name="coo09" src="bibtex:inproceedings" src-info="bibtex:line-13969" type="sharef:inproceedings" crossref="locweb2009">
		<names type="sharef:author">
			<person>
				<givenname>Alissa</givenname>
				<surname>Cooper</surname>
			</person>
			<person>
				<givenname>John B.</givenname>
				<surname>Morris</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>As a tool for mitigating the potential privacy risks of gathering and transmitting location information on the Web, we suggest in this paper a model for conveying location information together with privacy rules to govern the use of that information. Binding privacy rules to the conveyance of location information is one useful tool to help developers build location-based systems and services that comport with the concept of fair information practices (FIPs) — a set of widely accepted principles that create a basis for privacy-protective systems. We offer as a model one fully developed set of standards for binding location data conveyed across IP networks to privacy rules.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/1507136.1507139</identifier>
		<pages>6-9</pages>
		<title type="sharef:primaryTitle">Binding Privacy Rules to Location on the Web</title>
		<identifier type="sharef:uri">http://portal.acm.org/citation.cfm?id=1507136.1507139</identifier>
	</reference>
	<reference name="lee09" src="bibtex:inproceedings" src-info="bibtex:line-13979" type="sharef:inproceedings" crossref="locweb2009">
		<names type="sharef:author">
			<person>
				<givenname>Ryong</givenname>
				<surname>Lee</surname>
			</person>
			<person>
				<givenname>Daisuke</givenname>
				<surname>Kitayama</surname>
			</person>
			<person>
				<givenname>Yong-Jin</givenname>
				<surname>Kwon</surname>
			</person>
			<person>
				<givenname>Kazutoshi</givenname>
				<surname>Sumiya</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Although location-based information systems can now be accessed from mobile devices, searching for information from an outdoor environment requires a significant amount of effort given the time-consuming manipulations that need to be made. Augmented-Reality (AR) based systems can help resolve these issues by reducing the physical effort required to input keywords onto a small keyboard, and the mental effort necessary to review the search results. But most AR systems do not consider media sharing environments where individual systems are not interoperable in respect of their media and browsing abilities. In this paper, we focus on a media environment for interoperable augmented-reality systems, making the assumption that such devices will become more wide spread and that many people will share individual media in a real-world space. Furthermore, we describe such emerging scenarios and new research issues. We also present a model to manage the futuristic data, making it similar to existing physical media, and show a practical example using the system we have developed.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/1507136.1507143</identifier>
		<pages>20-23</pages>
		<title type="sharef:primaryTitle">Interoperable Augmented Web Browsing for Exploring Virtual Media in Real Space</title>
		<identifier type="sharef:uri">http://portal.acm.org/citation.cfm?id=1507136.1507143</identifier>
	</reference>
	<reference name="locweb2009" src="bibtex:proceedings" src-info="bibtex:line-13989" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>Erik</givenname>
				<surname>Wilde</surname>
			</person>
			<person>
				<givenname>Susanne</givenname>
				<surname>Boll</surname>
			</person>
			<person>
				<givenname>Keith</givenname>
				<surname>Cheverst</surname>
			</person>
			<person>
				<givenname>Peter</givenname>
				<surname>Fröhlich</surname>
			</person>
			<person>
				<givenname>Ross</givenname>
				<surname>Purves</surname>
			</person>
			<person>
				<givenname>Johannes</givenname>
				<surname>Schöning</surname>
			</person>
		</names>
		<date value="2009-04"/>
		<address type="sharef:placePublished">Boston, Massachusetts</address>
		<field type="bibtex:index">LocWeb 2009</field>
		<identifier type="sharef:isbn">978-1-60558-457-7</identifier>
		<field type="bibtex:key">Second International Workshop on Location and the Web (LocWeb 2009)</field>
		<title type="sharef:primaryTitle">Second International Workshop on Location and the Web (LocWeb 2009)</title>
		<field type="bibtex:topic">www[0.8]</field>
		<identifier type="sharef:uri">http://ifgi.uni-muenster.de/locweb2009/</identifier>
		<identifier type="sharef:uri">http://portal.acm.org/toc.cfm?id=1507136</identifier>
		<identifier type="sharef:uri" resourceType="text/html">http://www.informatik.uni-trier.de/~ley/db/conf/locweb/locweb2009.html</identifier>
	</reference>
	<reference name="wil10b" src="bibtex:inproceedings" src-info="bibtex:line-14009" type="sharef:inproceedings" crossref="locweb2010">
		<names type="sharef:author">
			<person>
				<givenname>Erik</givenname>
				<surname>Wilde</surname>
			</person>
			<person>
				<givenname>Susanne</givenname>
				<surname>Boll</surname>
			</person>
			<person>
				<givenname>Johannes</givenname>
				<surname>Schöning</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>The Third International Workshop on Location and the Web (LocWeb 2010) focuses on research and development that targets the intersection of Internet-enabled location-aware and/or located devices, and services based on Web technologies and Web architecture. The rapid rise of multi-sensory mobile devices and Internet-enabled "things" equipped with sensors and ubiquitous connectivity opens new possibilities and provides the foundations to capture, share and use Web services and applications in ways which go beyond the traditional scenarios of stationary or even mobile computer-like devices. Increasingly, applications will have to bridge the physical world and the Web space, and location is one of the major connecting links. When Web services will "surround" users, designers have to address the challenges of scalability and interoperability on the Web, and designers also have to look at policy, regulatory, and legislative responses to the privacy and security challenges created by something as sensitive as location information.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/1899662.1899663</identifier>
		<pages>1-3</pages>
		<title type="sharef:primaryTitle">Third International Workshop on Location and the Web (LocWeb 2010)</title>
		<identifier type="sharef:uri">http://portal.acm.org/citation.cfm?id=1899663</identifier>
	</reference>
	<reference name="wat10" src="bibtex:inproceedings" src-info="bibtex:line-14019" type="sharef:inproceedings" crossref="locweb2010">
		<names type="sharef:author">
			<person>
				<givenname>Stephan</givenname>
				<surname link="von">Watzdorf</surname>
			</person>
			<person>
				<givenname>Florian</givenname>
				<surname>Michahelles</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>This contribution investigates how accurate location information is on smartphones. Our research is based on a data set consisting of 2289 locations gathered from a marketed iPhone application. In a first analysis, it became evident that the accuracy information differs significantly among iPhone and iPod and iPad devices. A second analysis of the accuracy values reveals clusters of accuracy values at above 1 km, at 500 meters, and at an accuracy of below 300 meters. Information with an accuracy of above 500 meters originated from Cell-ID based positioning. Finally, an analysis revealed that the accuracy is significantly reduced for locations with more than 500 meters away from the next populated area. The overall results suggest that additional Cell-ID based positioning technology allows for higher coverage at the costs of a significantly reduced accuracy. If location information is required, with an accuracy of below 300 meters, the technology should be limited to GPS and WLAN based positioning. Adding Cell-ID based positioning increases the coverage while accuracy is reduced.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/1899662.1899664</identifier>
		<pages>4-7</pages>
		<title type="sharef:primaryTitle">Precision of Positioning Data on Smartphones</title>
		<identifier type="sharef:uri">http://portal.acm.org/citation.cfm?id=1899664</identifier>
	</reference>
	<reference name="sav10" src="bibtex:inproceedings" src-info="bibtex:line-14029" type="sharef:inproceedings" crossref="locweb2010">
		<names type="sharef:author">
			<person>
				<givenname>Norma Saiph</givenname>
				<surname>Savage</surname>
			</person>
			<person>
				<givenname>Shoji</givenname>
				<surname>Nishimura</surname>
			</person>
			<person>
				<givenname>Norma Elva</givenname>
				<surname>Chavez</surname>
			</person>
			<person>
				<givenname>Xifeng</givenname>
				<surname>Yan</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>In this paper we propose a new algorithm for finding the frequent routes that a user has in his daily routine, in our method we build a grid in which we map each of the GPS data points that belong to a certain sequence. We consider that each sequence conforms a route. We then carry out an interpolation procedure that has a probabilistic basis and find a more precise description of the user's trajectory. For each trajectory we find the edges that were crossed, with the crossed edges we create a histogram in which the bins denote the crossed edges and the frequency value the number of times that edge was crossed for a certain user. We then select the K most frequent edges and combine them to create a list of the most frequent paths that a user has. We compared our results with the algorithm that was proposed in Adaptive learning of semantic locations and routes to find frequent routes of a user, and found that our implementation on the contrary of this work can discriminate directions, ie routes that go from A to B and routes that go from B to A are taken as different. Furthermore our implementation also permits the analysis of subsections of the routes,something that to our knowledge had not been carried out in previous related work.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/1899662.1899665</identifier>
		<pages>8-11</pages>
		<title type="sharef:primaryTitle">Frequent Trajectory Mining on GPS Data</title>
		<identifier type="sharef:uri">http://portal.acm.org/citation.cfm?id=1899665</identifier>
	</reference>
	<reference name="jan10" src="bibtex:inproceedings" src-info="bibtex:line-14039" type="sharef:inproceedings" crossref="locweb2010">
		<names type="sharef:author">
			<person>
				<givenname>Gwan</givenname>
				<surname>Jang</surname>
			</person>
			<person>
				<givenname>Keun-Chan</givenname>
				<surname>Park</surname>
			</person>
			<person>
				<givenname>Kyung-Min</givenname>
				<surname>Kim</surname>
			</person>
			<person>
				<givenname>Yoonjae</givenname>
				<surname>Jeong</surname>
			</person>
			<person>
				<givenname>Sung-Hyon</givenname>
				<surname>Myaeng</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>In providing a service to mobile users, it would be critical to know what types of information they would look for in association with geo-referenced entities that may be extractable from queries or contexts. While understanding high-level user intentions in accessing the Web, such as informational, navigational, and transactional, is useful, a finer-level classification of user interests would further help adapting mobile search results to user intensions. Our research focuses on understanding what aspects of geo-referenced entities are mentioned in user queries in an attempt to create a model for user intents in geo-referenced Web searching. By collecting and analyzing geo-referenced questions posed to operational question answering systems, we delineated major aspects of non-topical information that people would seek in association with geographic information. The identified aspects were further conceptualized to develop a user interest model with three dimensions, which was validated with two sets of data. The model can be a basis for identifying user.s intent in a mobile search context as well as classifying geo-related text to be retrieved for its aspectual category.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/1899662.1899666</identifier>
		<pages>12-15</pages>
		<title type="sharef:primaryTitle">What Aspects do People Search in Geo-referenced Text?</title>
		<identifier type="sharef:uri">http://portal.acm.org/citation.cfm?id=1899666</identifier>
	</reference>
	<reference name="pae10" src="bibtex:inproceedings" src-info="bibtex:line-14049" type="sharef:inproceedings" crossref="locweb2010">
		<names type="sharef:author">
			<person>
				<givenname>Johannes</givenname>
				<surname>Paefgen</surname>
			</person>
			<person>
				<givenname>Florian</givenname>
				<surname>Michahelles</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>This paper describes an experimental setup for the analysis of e-bike usage characteristics based on GPS data. Usage characteristics include parameters such as average and maximum velocity, trip lengths and distribution over daytime. Based on high resolution position measurement these parameters are extracted and compared to other studies on both e-bikes and conventional bicycles. We show that applying location technology to concurrent monitoring of a fleet of e-bikes yields higher quality in terms of resolution and accuracy (1), and is less intrusive (2) than obtaining these data by conventional user surveys. The findings form a proof-of-concept for the adoption of location technology to transportation and behavioral sciences and suggest further interdisciplinary collaboration in these fields.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/1899662.1899667</identifier>
		<pages>16-19</pages>
		<title type="sharef:primaryTitle">Inferring Usage Characteristics of Electric Bicycles from Position Information</title>
		<identifier type="sharef:uri">http://portal.acm.org/citation.cfm?id=1899667</identifier>
	</reference>
	<reference name="ste10" src="bibtex:inproceedings" src-info="bibtex:line-14059" type="sharef:inproceedings" crossref="locweb2010">
		<names type="sharef:author">
			<person>
				<givenname>Peter</givenname>
				<surname>Stephan</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Following paradigms like Ubiquitous Computing or the Internet of Things, modern factories are developing to intelligent environments in which wireless technology, sensor networks and mobile information access close the gap between the physical and the digital world. This article assumes that in such a versatile Factory of Things location information will play an important role for the transparent and efficient design of mobile and adaptive processes. Based upon a maintenance use case in the SmartFactory it will be examined how location information can contribute to the optimization of maintenance processes. As research questions regarding the development of an appropriate system architecture, the definition of a consistent data representation for location information as well as mechanisms for its semantic interpretation are focused. Finally, the desired architecture is evaluated regarding its benefits, limitations and role as an enabler for a lean information management suitable to apply in future intelligent factories.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/1899662.1899668</identifier>
		<pages>20-23</pages>
		<title type="sharef:primaryTitle">System Architecture for using Location Information for Process Optimization within a Factory of Things</title>
		<identifier type="sharef:uri">http://portal.acm.org/citation.cfm?id=1899668</identifier>
	</reference>
	<reference name="yan10" src="bibtex:inproceedings" src-info="bibtex:line-14069" type="sharef:inproceedings" crossref="locweb2010">
		<names type="sharef:author">
			<person>
				<givenname>Motoki</givenname>
				<surname>Yano</surname>
			</person>
			<person>
				<givenname>Katsuhiko</givenname>
				<surname>Kaji</surname>
			</person>
			<person>
				<givenname>Nobuo</givenname>
				<surname>Kawaguchi</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>We introduce an iPhone/iPod touch timetable application using WiFi location system named "Eki.Locky". This application adopts UGC (User Generated Content) approach to collect TimeTable information andWiFi access point (AP) information from public users. Since the service started in October 2009, Eki.Locky has been used by over 440,000 people, posted timetable information covers 98% of all stations in Japan and 350,000 WiFi AP information were collected. In addition, since June 2010, we started a new version of this application named "TimeTable.Locky" which supports any timetable such as buses and airplanes. TimeTable.Locky also has been used large number of people, and collected over 23,000 of timetable information.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/1899662.1899669</identifier>
		<pages>24-25</pages>
		<title type="sharef:primaryTitle">TimeTable.Locky : Nation Wide WiFi Location Information System based on User Contributed Information</title>
		<identifier type="sharef:uri">http://portal.acm.org/citation.cfm?id=1899669</identifier>
	</reference>
	<reference name="oli10" src="bibtex:inproceedings" src-info="bibtex:line-14079" type="sharef:inproceedings" crossref="locweb2010">
		<names type="sharef:author">
			<person>
				<givenname>João</givenname>
				<surname>Oliveirinha</surname>
			</person>
			<person>
				<givenname>Francisco</givenname>
				<surname>Pereira</surname>
			</person>
			<person>
				<givenname>Ana</givenname>
				<surname>Alves</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>During the last few years, the amount of online descriptive information about places and their dynamics has reached reasonable dimension for many cities in the world. Such enriched information can now support semantic analysis of space, particularly in which respects to what exists there and what happens there. We present a methodology to automatically label places according to events that happen there. To achieve this we use Information Extraction techniques applied to online Web 2.0 resources such as Zvents and Boston Calendar. Wikipedia is also used as a resource to semantically enrich the tag vectors initially extracted. We describe the process by which these semantic vectors are obtained, present results of experimental analysis, and validated these with Amazon Mechanical Turk and a set of algorithms. To conclude, we discuss the strengths and weaknesses of the methodology.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/1899662.1899670</identifier>
		<pages>26-33</pages>
		<title type="sharef:primaryTitle">Acquiring Semantic Context for Events from Online Resources</title>
		<identifier type="sharef:uri">http://portal.acm.org/citation.cfm?id=1899670</identifier>
	</reference>
	<reference name="kar10" src="bibtex:inproceedings" src-info="bibtex:line-14089" type="sharef:inproceedings" crossref="locweb2010">
		<names type="sharef:author">
			<person>
				<givenname>Hassan</givenname>
				<surname>Karimi</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Despite much advances in both general and targeted Social Network Services (SNS) and Location-Based Social Networks (LBSN), there is currently a void in literatures on SNS that form temporary social networks to address specific problems and employ intelligent classification of members and coordination of tasks toward goal oriented action. In this position paper, we present Genetic Location-Based Social Networks (G-LBSN) which is a new concept in social networking where temporary social networks, to address specific problems, are formed. Unique characteristics of G-LBSN include: (a) formation of temporary social networks (each network has a life time which spans from its inception until the problem is solved); (b) classification of members based on their proximity to given locations, their contribution to the solution, and their availability; (c) assignment of tasks to selected members; and (d) coordination and supervision of members activities and the progress toward a solution.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/1899662.1899671</identifier>
		<pages>34-37</pages>
		<title type="sharef:primaryTitle">Genetic Location-Based Social Networks (G-LBSN)</title>
		<identifier type="sharef:uri">http://portal.acm.org/citation.cfm?id=1899671</identifier>
	</reference>
	<reference name="sti10b" src="bibtex:inproceedings" src-info="bibtex:line-14099" type="sharef:inproceedings" crossref="locweb2010">
		<names type="sharef:author">
			<person>
				<givenname>Vlad</givenname>
				<surname>Stirbu</surname>
			</person>
			<person>
				<givenname>Petri</givenname>
				<surname>Selonen</surname>
			</person>
			<person>
				<givenname>Arto</givenname>
				<surname>Palin</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>In this paper we outline a unified architecture for representing locations of people, places and things in real or virtual worlds, called realms, on the web. Our architecture is based on the location graph that encodes web-level containment and connectedness relationships between locations. The architecture provides an information processing model that allows realm independent queries such as position, range and path, and realm specific queries, such as distance. We present existing systems that are enablers for the proposed architecture. With this architecture we enable a common way to develop location based services and applications across real or virtual realms, avoiding fragmentation.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/1899662.1899672</identifier>
		<pages>38-45</pages>
		<title type="sharef:primaryTitle">The Location Graph: Towards a Symbolic Location Architecture for the Web</title>
		<identifier type="sharef:uri">http://portal.acm.org/citation.cfm?id=1899672</identifier>
	</reference>
	<reference name="locweb2010" src="bibtex:proceedings" src-info="bibtex:line-14109" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>Erik</givenname>
				<surname>Wilde</surname>
			</person>
			<person>
				<givenname>Susanne</givenname>
				<surname>Boll</surname>
			</person>
			<person>
				<givenname>Johannes</givenname>
				<surname>Schöning</surname>
			</person>
		</names>
		<date value="2010-11"/>
		<address type="sharef:placePublished">Tokyo, Japan</address>
		<field type="bibtex:index">LocWeb 2010</field>
		<identifier type="sharef:isbn">978-1-60558-457-7</identifier>
		<field type="bibtex:key">Third International Workshop on Location and the Web (LocWeb 2010)</field>
		<title type="sharef:primaryTitle">Third International Workshop on Location and the Web (LocWeb 2010)</title>
		<field type="bibtex:topic">www[0.8]</field>
		<identifier type="sharef:uri">http://portal.acm.org/citation.cfm?id=1899662</identifier>
		<identifier type="sharef:uri">http://medien.informatik.uni-oldenburg.de/LocWeb2010/</identifier>
		<identifier type="sharef:uri" resourceType="text/html">http://www.informatik.uni-trier.de/~ley/db/conf/locweb/locweb2010.html</identifier>
	</reference>
	<reference name="wewst2006" src="bibtex:proceedings" src-info="bibtex:line-14129" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>Cesare</givenname>
				<surname>Pautasso</surname>
			</person>
			<person>
				<givenname>Christoph</givenname>
				<surname>Bussler</surname>
			</person>
		</names>
		<date value="2006-11"/>
		<address type="sharef:placePublished">Zürich, Switzerland</address>
		<field type="bibtex:index">WEWST 2007</field>
		<field type="bibtex:key">Workshop on Emerging Web Services Technology (WEWST 2006)</field>
		<title type="sharef:primaryTitle">Workshop on Emerging Web Services Technology (WEWST 2006)</title>
		<identifier type="sharef:uri">http://www.iks.ethz.ch/wewst06/</identifier>
		<identifier type="sharef:uri">http://sunsite.informatik.rwth-aachen.de/Publications/CEUR-WS/Vol-234/</identifier>
	</reference>
	<reference name="wewst2007" src="bibtex:proceedings" src-info="bibtex:line-14146" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>Cesare</givenname>
				<surname>Pautasso</surname>
			</person>
			<person>
				<givenname>Thomas</givenname>
				<surname>Gschwind</surname>
			</person>
		</names>
		<date value="2007-11"/>
		<address type="sharef:placePublished">Halle, Germany</address>
		<field type="bibtex:index">WEWST 2007</field>
		<field type="bibtex:key">2nd Workshop on Emerging Web Services Technology (WEWST 2007)</field>
		<title type="sharef:primaryTitle">2nd Workshop on Emerging Web Services Technology (WEWST 2007)</title>
		<identifier type="sharef:uri" resourceType="text/html">http://www.informatik.uni-trier.de/~ley/db/conf/ecows/wewst2007.html</identifier>
	</reference>
	<reference name="wewst2008" src="bibtex:proceedings" src-info="bibtex:line-14162" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>Walter</givenname>
				<surname>Binder</surname>
			</person>
			<person>
				<givenname>Schahram</givenname>
				<surname>Dustdar</surname>
			</person>
		</names>
		<date value="2008-11"/>
		<address type="sharef:placePublished">Dublin, Ireland</address>
		<field type="bibtex:index">WEWST 2008</field>
		<field type="bibtex:key">3rd Workshop on Emerging Web Services Technology (WEWST 2008)</field>
		<title type="sharef:primaryTitle">3rd Workshop on Emerging Web Services Technology (WEWST 2008)</title>
		<identifier type="sharef:uri" resourceType="application/pdf">http://www.inf.unisi.ch/faculty/binder/wewst08/wewst08_proceedings.pdf</identifier>
	</reference>
	<reference name="bin09" src="bibtex:inproceedings" src-info="bibtex:line-14178" type="sharef:inproceedings" crossref="wewst2009">
		<names type="sharef:author">
			<person>
				<givenname>Walter</givenname>
				<surname>Binder</surname>
			</person>
			<person>
				<givenname>Erik</givenname>
				<surname>Wilde</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>The 2009 Workshop on Emerging Web Service Technology (WEWST), collocated with the European Conference on Web Services (ECOWS), is the premier workshop for academic and industrial communities to discuss innovative ideas and research contributions advancing the state-of-the-art in Web service technologies. Although the advantages of Web services to allow businesses to interact with each other while maintaining a loose coupling are well known, there are still many challenges to be solved in this important field of research. The wide variety of tools, techniques, and technological solutions presented in WEWST share one common feature: they suggest new directions for Web service research by introducing new and sometime controversial ideas into the field. The workshop allows participants to gain new insights and to start collaborations by discussing how their own work can be used in related but different areas.</p>
			</richtext>
		</abstract>
		<pages>1-2</pages>
		<title type="sharef:primaryTitle">4th Workshop on Emerging Web Services Technology (WEWST 2009)</title>
	</reference>
	<reference name="sur09" src="bibtex:inproceedings" src-info="bibtex:line-14186" type="sharef:inproceedings" crossref="wewst2009">
		<names type="sharef:author">
			<person>
				<givenname>Niranjan</givenname>
				<surname>Suri</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Service-oriented Architectures (SoAs) have established themselves as a popular approach to building large-scale systems. They were initially motivated by organizations desiring dynamically coupled systems that would support rapid configuration, deployment, and reconfiguration. SoAs support multi-tiered architectures for enterprise backends as well as integration of multiple organizations via well defined interfaces. The success and popularity of SoAs in the Internet has driven the consideration of SoAs for tactical edge networks. However, tactical edge networks are considerably different from the Internet in terms of the type and number of nodes as well as the connectivity between the nodes. Nodes may be transient and resource constrained — battery operated and with limited processing and storage. The communications between nodes may be wireless and ad-hoc, resulting in network partitioning and unreliable, bandwidth constrained, and variable latency links. This paper describes some observations of the target environments, requirements for SoAs for such environments, and experiences with developing SoAs for tactical edge networks.</p>
			</richtext>
		</abstract>
		<pages>3-10</pages>
		<title type="sharef:primaryTitle">Dynamic Service-oriented Architectures for Tactical Edge Networks</title>
	</reference>
	<reference name="aho09" src="bibtex:inproceedings" src-info="bibtex:line-14194" type="sharef:inproceedings" crossref="wewst2009">
		<names type="sharef:author">
			<person>
				<givenname>Pekka</givenname>
				<surname>Aho</surname>
			</person>
			<person>
				<givenname>Matti</givenname>
				<surname>Mäki</surname>
			</person>
			<person>
				<givenname>Daniel</givenname>
				<surname>Pakkala</surname>
			</person>
			<person>
				<givenname>Eila</givenname>
				<surname>Ovaska</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>One of the challenges in Model Driven Architecture (MDA) is the variety of tools which are not interoperable with each other. Also, a design flow supporting different phases of MDA-based development is often missing. This paper presents a tool chain and design flow for MDA-based Web Services development. The presented tool chain covers modeling with domain-specific Unified Modeling Language (UML) profiles, transformation of the UML models into Web Services Definition Language (WSDL) files, and Java code generation. The tool chain is validated in a case study where it is used in the development of a web service called Resource Availability Service (RAS). In the validation, the tool chain worked well, since the proportion of generated code in RAS is over 95%. The residual 5% of the code includes manual integration and business logic. User experiences indicate that using the tool chain improves the developer productivity in Web Services development.</p>
			</richtext>
		</abstract>
		<pages>11-18</pages>
		<title type="sharef:primaryTitle">MDA-Based Tool Chain for Web Services Development</title>
	</reference>
	<reference name="fel09" src="bibtex:inproceedings" src-info="bibtex:line-14202" type="sharef:inproceedings" crossref="wewst2009">
		<names type="sharef:author">
			<person>
				<givenname>Marius</givenname>
				<surname>Feldmann</surname>
			</person>
			<person>
				<givenname>Gerald</givenname>
				<surname>Hübsch</surname>
			</person>
			<person>
				<givenname>Tobias</givenname>
				<surname>Nestler</surname>
			</person>
			<person>
				<givenname>Klemens</givenname>
				<surname>Muthmann</surname>
			</person>
			<person>
				<givenname>Uwe</givenname>
				<surname>Jugel</surname>
			</person>
			<person>
				<givenname>Alexander</givenname>
				<surname>Schill</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Developing Service-based interactive applications is a time consuming and nontrivial task. The idea of annotating Web Services with information fragments used for deriving parts of interactive applications automatically promises the simplification of this task, thus enabling the creation of Service-based interactive applications for end users without any implementation skills. The paper discusses a model-driven approach for generating executable Service-based interactive applications directly from the output of a visual authoring tool. Besides the introduction of details about the model-driven methodology, this paper makes two central contributions: Firstly, technical details about the developed end user enabled authoring tool are introduced. Secondly, the meta-models applied on different stages within the application generation approach are presented.</p>
			</richtext>
		</abstract>
		<pages>19-28</pages>
		<title type="sharef:primaryTitle">Overview of an End user enabled Model-driven Development Approach for Interactive Applications based on Annotated Services</title>
	</reference>
	<reference name="seg09" src="bibtex:inproceedings" src-info="bibtex:line-14210" type="sharef:inproceedings" crossref="wewst2009">
		<names type="sharef:author">
			<person>
				<givenname>Ricardo</givenname>
				<surname>Seguel</surname>
			</person>
			<person>
				<givenname>Rik</givenname>
				<surname>Eshuis</surname>
			</person>
			<person>
				<givenname>Paul</givenname>
				<surname>Grefen</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Two composed interacting services reach a deadlock if their business protocols have behavioral mismatches. A protocol adaptor can resolve deadlocks. However, existing methods build adaptors that process all messages exchanged by the protocols, even if only some messages cause a deadlock. We present an efficient, automated method to construct (if possible) a minimal adaptor for two business protocols containing parallelism and loops. First, the method finds the minimal set of messages exchanged needing adaptation, using behavioral relations on the protocol syntax to identify mismatches. Next, it generates in an efficient way an adaptor from the minimal set of messages. This minimal adaptor is compatible with the protocols, it reduces process complexity and it improves run-time performance of the automated service composition. We have implemented the method in a tool for adapting two business protocols. We apply it to an example case study from the healthcare domain.</p>
			</richtext>
		</abstract>
		<pages>29-38</pages>
		<title type="sharef:primaryTitle">Constructing Minimal Protocol Adaptors for Service Composition</title>
	</reference>
	<reference name="wil09i" src="bibtex:inproceedings" src-info="bibtex:line-14218" type="sharef:inproceedings" crossref="wewst2009">
		<names type="sharef:author">
			<person>
				<givenname>Erik</givenname>
				<surname>Wilde</surname>
			</person>
			<person>
				<givenname>Michael</givenname>
				<surname>Hausenblas</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>SPARQL is the standard query language for RDF, but currently is a read-only language defined in a way similar to SQL: Queries can be formulated, are submitted to a single processing facility, which then returns a result set. In this paper, we examine the shortcomings of this approach with regard to Web architecture, and propose a path towards a language that is more in line with basic principles of Web architecture. While this work has been done in the context of a proposed update extension for SPARQL, our focus is on how to apply the principles of Representational State Transfer (REST) to SPARQL. Our claim is that a RESTful redesign of SPARQL allows the Semantic Web to evolve in a more decentralized and openly accessible way than the current RPC-style design of SPARQL.</p>
			</richtext>
		</abstract>
		<pages>39-43</pages>
		<title type="sharef:primaryTitle">RESTful SPARQL? You Name It! — Aligning SPARQL with REST and Resource Orientation</title>
		<field type="bibtex:topic">sparql[0.8] rest[0.8]</field>
		<identifier type="sharef:uri">http://dret.net/netdret/publications#wil09i</identifier>
	</reference>
	<reference name="wewst2009" src="bibtex:proceedings" src-info="bibtex:line-14228" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>Walter</givenname>
				<surname>Binder</surname>
			</person>
			<person>
				<givenname>Erik</givenname>
				<surname>Wilde</surname>
			</person>
		</names>
		<date value="2009-11"/>
		<address type="sharef:placePublished">Eindhoven, Netherlands</address>
		<field type="bibtex:index">WEWST 2009</field>
		<field type="bibtex:key">4th Workshop on Emerging Web Services Technology (WEWST 2009)</field>
		<title type="sharef:primaryTitle">4th Workshop on Emerging Web Services Technology (WEWST 2009)</title>
		<identifier type="sharef:uri">http://portal.acm.org/toc.cfm?id=1645406</identifier>
	</reference>
	<reference name="ala10d" src="bibtex:inproceedings" src-info="bibtex:line-14244" type="sharef:inproceedings" crossref="wesoa2010">
		<names type="sharef:author">
			<person>
				<givenname>Rosa</givenname>
				<surname>Alarcón</surname>
			</person>
			<person>
				<givenname>Erik</givenname>
				<surname>Wilde</surname>
			</person>
			<person>
				<givenname>Jesus</givenname>
				<surname>Bellido</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Representational State Transfer (REST) services are gaining momentum as a lightweight approach for the provision of services on the Web. Unlike WSDL-based services, in REST the set of operations is reduced, standardized, with well known semantics, and changes the resource's state. Few attempts have been proposed to support composition models for REST, they are mainly operation-centric and fail to acknowledge the hypermedia nature of REST, that is, clients must inspect the served resource state and choose the link to follow from there. We explore RESTful service composition as it is driven by the hypermedia net that is dynamically created while a client interacts with a server resulting in a light-weight approach. We based our proposal on a hypermedia-centric REST service description, the Resource Linking Language (ReLL) and Petri Nets as a mechanism for describing the machine-client navigation.</p>
			</richtext>
		</abstract>
		<title type="sharef:primaryTitle">Hypermedia-driven RESTful Service Composition</title>
		<identifier type="sharef:uri">http://dret.net/netdret/publications#ala10d</identifier>
	</reference>
	<reference name="wesoa2010" src="bibtex:proceedings" src-info="bibtex:line-14252" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>George</givenname>
				<surname>Feuerlicht</surname>
			</person>
			<person>
				<givenname>Winfried</givenname>
				<surname>Lamersdorf</surname>
			</person>
			<person>
				<givenname>Guadalupe</givenname>
				<surname>Ortiz</surname>
			</person>
			<person>
				<givenname>Christian</givenname>
				<surname>Zirpins</surname>
			</person>
		</names>
		<date value="2010-12"/>
		<address type="sharef:placePublished">San Francisco, California</address>
		<field type="bibtex:key">6th Workshop on Engineering Service-Oriented Applications (WESOA 2010)</field>
		<title type="sharef:primaryTitle">6th Workshop on Engineering Service-Oriented Applications (WESOA 2010)</title>
		<identifier type="sharef:uri">http://wesoa.org/</identifier>
	</reference>
	<reference name="pau10a" src="bibtex:inproceedings" src-info="bibtex:line-14267" type="sharef:inproceedings" crossref="wsrest2010">
		<names type="sharef:author">
			<person>
				<givenname>Cesare</givenname>
				<surname>Pautasso</surname>
			</person>
			<person>
				<givenname>Erik</givenname>
				<surname>Wilde</surname>
			</person>
			<person>
				<givenname>Alexandros</givenname>
				<surname>Marinos</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Over the past few years, the discussion between the two major architectural styles for designing and implementing Web services, the RPC-oriented approach and the resource-oriented approach, has been mainly held outside of traditional research communities. Mailing lists, forums and developer communities have seen long and fascinating debates around the assumptions, strengths, and weaknesses of these two approaches. The First International Workshop on RESTful Design (WS-REST 2010) has the goal of getting more researchers involved in the debate by providing a forum where discussions around the resource-oriented style of Web services design take place. Representational State Transfer (REST) is an architectural style and as such can be applied in different ways, can be extended by additional constraints, or can be specialized with more specific interaction patterns. WS-REST is the premier forum for discussing research ideas, novel applications and results centered around REST at the World Wide Web conference, which provides a great setting to host this first edition of the workshop dedicated to research on the architectural style underlying the Web.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/1798354.1798375</identifier>
		<pages>1-3</pages>
		<title type="sharef:primaryTitle">First International Workshop on RESTful Design (WS-REST 2010)</title>
	</reference>
	<reference name="ric10" src="bibtex:inproceedings" src-info="bibtex:line-14276" type="sharef:inproceedings" crossref="wsrest2010">
		<names type="sharef:author">
			<person>
				<givenname>Leonard</givenname>
				<surname>Richardson</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Although desktop developers often have trouble consciously understanding RESTful concepts like "hypermedia as the engine of application state", this does not prevent them from intuitively understanding client-side tools based on these concepts. However, I encountered unexpected developer resistance after implementing a security protocol I and other web developers had thought uncontroversial: the most common mechanism for authorizing OAuth request tokens. This developer resistance has implications for many web services that share their authentication credentials with a corresponding website.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/1798354.1798377</identifier>
		<pages>4-9</pages>
		<title type="sharef:primaryTitle">Developers Like Hypermedia, But They Don't Like Web Browsers</title>
	</reference>
	<reference name="had10" src="bibtex:inproceedings" src-info="bibtex:line-14285" type="sharef:inproceedings" crossref="wsrest2010">
		<names type="sharef:author">
			<person>
				<givenname>Marc</givenname>
				<surname>Hadley</surname>
			</person>
			<person>
				<givenname>Santiago</givenname>
				<surname>Pericas-Geertsen</surname>
			</person>
			<person>
				<givenname>Paul</givenname>
				<surname>Sandoz</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>This paper describes a set of experimental extensions for Jersey that aim to simplify server-side creation and client-side consumption of hypermedia-driven services. We introduce the concept of action resources that expose workflow-related operations on a parent resource.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/1798354.1798378</identifier>
		<pages>10-15</pages>
		<title type="sharef:primaryTitle">Exploring Hypermedia Support in Jersey</title>
	</reference>
	<reference name="par10" src="bibtex:inproceedings" src-info="bibtex:line-14294" type="sharef:inproceedings" crossref="wsrest2010">
		<names type="sharef:author">
			<person>
				<givenname>Savas</givenname>
				<surname>Parastatidis</surname>
			</person>
			<person>
				<givenname>Jim</givenname>
				<surname>Webber</surname>
			</person>
			<person>
				<givenname>Guilherme</givenname>
				<surname>Silveira</surname>
			</person>
			<person>
				<givenname>Ian</givenname>
				<surname>Robinson</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>This paper discusses the role of the Representational State Transfer (REST) architectural style in the development of distributed applications. It also gives an overview of how RESTful implementations of distributed business processes and structures can be supported by a framework such as Restfulie.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/1798354.1798379</identifier>
		<pages>16-22</pages>
		<title type="sharef:primaryTitle">The Role of Hypermedia in Distributed System Development</title>
	</reference>
	<reference name="kel10" src="bibtex:inproceedings" src-info="bibtex:line-14303" type="sharef:inproceedings" crossref="wsrest2010">
		<names type="sharef:author">
			<person>
				<givenname>Mike</givenname>
				<surname>Kelly</surname>
			</person>
			<person>
				<givenname>Michael</givenname>
				<surname>Hausenblas</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Gateway caches are intermediary components for reducing demands on destination servers, and therefore operational costs of a system. At scale, particularly with the advent of on-demand infrastructures such as EC2, etc., maximising cache efficiency translates into cost efficiency, resulting in a competitive advantage. In this position paper, we initially discuss advantages and limitations of HTTP caching mechanisms. We then propose to use HTTP Link: headers to maximise the efficiency of gateway (or reverse proxy) caching mechanisms and discuss early findings.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/1798354.1798380</identifier>
		<pages>23-26</pages>
		<title type="sharef:primaryTitle">Using HTTP Link: Header for Gateway Cache Invalidation</title>
	</reference>
	<reference name="eng10" src="bibtex:inproceedings" src-info="bibtex:line-14312" type="sharef:inproceedings" crossref="wsrest2010">
		<names type="sharef:author">
			<person>
				<givenname>Charles</givenname>
				<surname>Engelke</surname>
			</person>
			<person>
				<givenname>Craig</givenname>
				<surname>Fitzgerald</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>In this paper, we describe issues encountered in designing and implementing a set of RESTful services to extend and replace web services that have been in commercial use since 1998. Applicability of REST to the service requirements, suitability of available tools, and interoperability between multiple clients and servers are discussed.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/1798354.1798381</identifier>
		<pages>27-30</pages>
		<title type="sharef:primaryTitle">Replacing Legacy Web Services with RESTful Services</title>
	</reference>
	<reference name="fer10" src="bibtex:inproceedings" src-info="bibtex:line-14321" type="sharef:inproceedings" crossref="wsrest2010">
		<names type="sharef:author">
			<person>
				<givenname>Federico</givenname>
				<surname>Fernandez</surname>
			</person>
			<person>
				<givenname>Jaime</givenname>
				<surname>Navón</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>We believe that there is a need for a practical model to visualize the structure and design rationale of REST, so researchers can study more easily the reutilization of this architectural style or parts of it, to the design of software solutions with different requirements than those of the early WWW. In this work we propose the utilization of extended influence diagrams to represent the structure and design rationale of an architectural style. The model is evaluated qualitatively by showing how a diagram of REST, populated with information extracted from the doctoral dissertation that introduced the term, is helpful to gain a better understanding of the properties and limitations of this style, and to reason about potential modifications for applications with different goals than those of the early WWW.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/1798354.1798383</identifier>
		<pages>31-38</pages>
		<title type="sharef:primaryTitle">Towards a Practical Model to Facilitate Reasoning about REST Extensions and Reuse</title>
	</reference>
	<reference name="gar10" src="bibtex:inproceedings" src-info="bibtex:line-14330" type="sharef:inproceedings" crossref="wsrest2010">
		<names type="sharef:author">
			<person>
				<givenname>Antonio Garrote</givenname>
				<surname>Hernández</surname>
			</person>
			<person>
				<givenname>María N. Moreno</givenname>
				<surname>García</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>In this article a formal model applying REST architectural principles to the description of semantic web services is introduced, including the discussion of its syntax and operational semantics. RESTful semantic resources are described using the concept of tuple spaces being manipulated by HTTP methods that are related to classical tuple space operations. On the other hand, RESTful resources creation, destruction and other dynamic aspects of distributed HTTP computations involving coordination between HTTP agents and services are modeled using process calculus style named channels and message passing mechanisms. The resulting model allows for a complete and rigorous description of resource based web systems, where agents taking part in a computation publish data encoded according to semantic standards through public triple repositories identified by well known URIs. The model can be used to describe complex interaction scenarios where coordination and composition of resources are required. One of such scenarios taken from the literature about web services choreography is analyzed from the point of view of the proposed model. Finally, possible extensions to the formalism, such as the inclusion of a description logics based type system associated to the semantic resources or possible extensions to HTTP operations are briefly explored.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/1798354.1798384</identifier>
		<pages>39-45</pages>
		<title type="sharef:primaryTitle">A Formal Definition of RESTful Semantic Web Services</title>
	</reference>
	<reference name="jac10" src="bibtex:inproceedings" src-info="bibtex:line-14339" type="sharef:inproceedings" crossref="wsrest2010">
		<names type="sharef:author">
			<person>
				<givenname>Ian</givenname>
				<surname>Jacobi</surname>
			</person>
			<person>
				<givenname>Alexey</givenname>
				<surname>Radul</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Traditionally, distributed computing problems have been solved by partitioning data into chunks small enough to be handled by commodity hardware. However, such partitioning is not possible in cases where there are a high number of dependencies or high dimensionality, such as in reasoning and expert systems, rendering such problems less tractable for distributed systems. By instead partitioning the problem, rather than the data, we can achieve a more general application of distributed computing. Partitioning the problem rather than the data may require tighter communication between members of the network, even though many networks can only be assumed to be weakly-connected. We believe that a decentralized implementation of propagator networks may resolve the problem. By placing several constraints on the merging of data transmitted over the network, we can easily synchronize information and achieve eventual convergence without implementing mechanisms needed for serialization. To this end, we present the design of a RESTful messaging mechanism, currently in the process of being implemented, that allows distributed propagator networks to be created, using mechanisms that result in eventual convergence of knowledge across a weakly-connected network. By utilizing a RESTful design of the mechanism, we can also achieve a reduction of bandwidth usage during synchronization through the use of caching.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/1798354.1798385</identifier>
		<pages>46-53</pages>
		<title type="sharef:primaryTitle">A RESTful Messaging System for Asynchronous Distributed Processing</title>
	</reference>
	<reference name="sel10" src="bibtex:inproceedings" src-info="bibtex:line-14348" type="sharef:inproceedings" crossref="wsrest2010">
		<names type="sharef:author">
			<person>
				<givenname>Petri</givenname>
				<surname>Selonen</surname>
			</person>
			<person>
				<givenname>Petros</givenname>
				<surname>Belimpasakis</surname>
			</person>
			<person>
				<givenname>Yu</givenname>
				<surname>You</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>This paper discusses the development of a RESTful Web Service platform for serving Mixed Reality content at Nokia Research Center. The paper gives an overview of the Mixed Reality domain, the requirements for the platform and its implementation. We further outline a method for developing resource oriented web services, beginning with high-level requirements, formalizing them as UML models and refining them to a RESTful API specification. The approach is demonstrated with detailed examples of designing one particular API subset for Mixed Reality annotations.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/1798354.1798387</identifier>
		<pages>54-61</pages>
		<title type="sharef:primaryTitle">Developing a RESTful Mixed Reality Web Service Platform</title>
	</reference>
	<reference name="sti10" src="bibtex:inproceedings" src-info="bibtex:line-14357" type="sharef:inproceedings" crossref="wsrest2010">
		<names type="sharef:author">
			<person>
				<givenname>Vlad</givenname>
				<surname>Stirbu</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>In this paper we introduce a practical approach to share the user interface of MVC compatible interactive applications with remote devices that have the ability to adapt the user interface to their specific look and feel. We present the system architecture and the methodology to model the user interface as a set of RESTful resources. The remote user interface and the application state are synchronized using an Web-based event-driven system.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/1798354.1798388</identifier>
		<pages>63-67</pages>
		<title type="sharef:primaryTitle">A RESTful Architecture for Adaptive and Multi-device Application Sharing</title>
	</reference>
	<reference name="wsrest2010" src="bibtex:proceedings" src-info="bibtex:line-14366" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>Cesare</givenname>
				<surname>Pautasso</surname>
			</person>
			<person>
				<givenname>Erik</givenname>
				<surname>Wilde</surname>
			</person>
			<person>
				<givenname>Alexandros</givenname>
				<surname>Marinos</surname>
			</person>
		</names>
		<date value="2010-04"/>
		<address type="sharef:placePublished">Raleigh, North Carolina</address>
		<field type="bibtex:index">WS-REST 2010</field>
		<identifier type="sharef:isbn">978-1-60558-959-6</identifier>
		<field type="bibtex:key">First International Workshop on RESTful Design (WS-REST 2010)</field>
		<title type="sharef:primaryTitle">First International Workshop on RESTful Design (WS-REST 2010)</title>
		<field type="bibtex:topic">rest[1]</field>
		<identifier type="sharef:uri">http://ws-rest.org/2010/</identifier>
		<identifier type="sharef:uri">http://portal.acm.org/citation.cfm?id=1798354</identifier>
		<identifier type="sharef:uri" resourceType="text/html">http://www.informatik.uni-trier.de/~ley/db/conf/rest/rest2010.html</identifier>
	</reference>
	<reference name="pau11a" src="bibtex:inproceedings" src-info="bibtex:line-14386" type="sharef:inproceedings" crossref="wsrest2011">
		<names type="sharef:author">
			<person>
				<givenname>Cesare</givenname>
				<surname>Pautasso</surname>
			</person>
			<person>
				<givenname>Erik</givenname>
				<surname>Wilde</surname>
			</person>
			<person>
				<givenname>Rosa</givenname>
				<surname>Alarcon</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Over the past few years, the discussion between the two major architectural styles for designing and implementing Web services, the RPC-oriented approach and the resourceoriented approach, has been mainly held outside of traditional research communities. Mailing lists, forums and developer communities have seen long and fascinating debates around the assumptions, strengths, and weaknesses of these two approaches. The Second International Workshop on RESTful Design (WS-REST 2011) has the goal of getting more researchers involved in the debate by providing a forum where discussions around the resource-oriented style of Web services design take place. Representational State Transfer (REST) is an architectural style and as such can be applied in different ways, can be extended by additional constraints, or can be specialized with more specific interaction patterns. WS-REST is the premier forum for discussing research ideas, novel applications and results centered around REST at the World Wide Web conference, which provides a great setting to host this second edition of the workshop dedicated to research on the architectural style underlying the Web.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/1967428.1967430</identifier>
		<pages>1-2</pages>
		<title type="sharef:primaryTitle">Second International Workshop on RESTful Design (WS-REST 2011)</title>
	</reference>
	<reference name="lis11" src="bibtex:inproceedings" src-info="bibtex:line-14395" type="sharef:inproceedings" crossref="wsrest2011">
		<names type="sharef:author">
			<person>
				<givenname>Olga</givenname>
				<surname>Liskin</surname>
			</person>
			<person>
				<givenname>Leif</givenname>
				<surname>Singer</surname>
			</person>
			<person>
				<givenname>Kurt</givenname>
				<surname>Schneider</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Hypermedia as the Engine of Application State, or HATEOAS, is one of the constraints of the REST architectural style. It requires service responses to link to the next valid application states. This frees clients from having to know about all the service's URLs and the details of its domain application protocol. Few services support HATEOAS, though. In most cases, client programmers need to duplicate business logic and URL schemas already present in the service. These dependencies result in clients that are more likely to break when changes occur. But existing services cannot be easily updated to support HATEOAS: Clients could cease working correctly when a service is changed. Also, client developers might not have access to the service's source code, be it for technical or political reasons. We discuss which information is needed to create a HATEOAS-compliant wrapper service for an existing service. We include a notation for modeling possible application states and transitions based on UML State Charts. We demonstrate the feasibility and advantages of our approach by comparing the clients for an existing service and its wrapped counterpart. Our approach enables client developers to wrap third-party services behind an HATEOAS-compliant layer. This moves the tight coupling away from potentially many clients to a single wrapper service that may easily be regenerated when the original service changes.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/1967428.1967432</identifier>
		<pages>3-10</pages>
		<title type="sharef:primaryTitle">Teaching Old Services New Tricks: Adding HATEOAS Support as an Afterthought</title>
	</reference>
	<reference name="ste11" src="bibtex:inproceedings" src-info="bibtex:line-14404" type="sharef:inproceedings" crossref="wsrest2011">
		<names type="sharef:author">
			<person>
				<givenname>Thomas</givenname>
				<surname>Steiner</surname>
			</person>
			<person>
				<givenname>Jan</givenname>
				<surname>Algermissen</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>One of the main REST design principles is the focus on media types as the core of contracts on the Web. However, not always is the service designer free to select the most appropriate media type for a task, sometimes a generic media type like application/rdf+xml (or in the worst case a binary format like image/png) with no defined or possible hypermedia controls at all has to be chosen. With this position paper we present a way how the hypermedia constraint of REST can still be fulfilled using a combination of Link headers, the OPTIONS method, and the HTTP Vocabulary in RDF.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/1967428.1967433</identifier>
		<pages>11-14</pages>
		<title type="sharef:primaryTitle">Fulfilling the Hypermedia Constraint via HTTP OPTIONS, the HTTP Vocabulary in RDF, and Link Headers</title>
	</reference>
	<reference name="sch11" src="bibtex:inproceedings" src-info="bibtex:line-14413" type="sharef:inproceedings" crossref="wsrest2011">
		<names type="sharef:author">
			<person>
				<givenname>Silvia</givenname>
				<surname>Schreier</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Today, Representational State Transfer (REST) is becoming more and more important. RESTful web services are an alternative to Remote Procedure Call technologies like SOAP and WS-* services. There are many frameworks for implementing RESTful applications, but there is still a lack of support for the early phases of the development process, particularly analysis and design. For building formal models of RESTful applications an appropriate metamodel is needed. After analyzing existing approaches and techniques a first version of such a REST metamodel is presented and used to model an example application. Beside enabling modeling, such a metamodel offers a vocabulary for REST in practice and the basis for model driven development.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/1967428.1967434</identifier>
		<pages>15-21</pages>
		<title type="sharef:primaryTitle">Modeling RESTful Applications</title>
	</reference>
	<reference name="pag11" src="bibtex:inproceedings" src-info="bibtex:line-14422" type="sharef:inproceedings" crossref="wsrest2011">
		<names type="sharef:author">
			<person>
				<givenname>Kevin R.</givenname>
				<surname>Page</surname>
			</person>
			<person>
				<givenname>David C. De</givenname>
				<surname>Roure</surname>
			</person>
			<person>
				<givenname>Kirk</givenname>
				<surname>Martinez</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>At a first glance there might appear to be an obvious alignment and overlap between the approaches prescribed by REST and Linked Data. On more detailed inspection divergences in scope and applicability present themselves, and for some aspects, incompatibility. In this paper we investigate these similarities and differences and suggest the coupling is worthy of a third look: in combination as a flexible environment in which the developer can focus on domain driven applications.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/1967428.1967435</identifier>
		<pages>22-25</pages>
		<title type="sharef:primaryTitle">REST and Linked Data: A Match Made for Domain Driven Development?</title>
	</reference>
	<reference name="dav11a" src="bibtex:inproceedings" src-info="bibtex:line-14431" type="sharef:inproceedings" crossref="wsrest2011">
		<names type="sharef:author">
			<person>
				<givenname>Cornelia</givenname>
				<surname>Davis</surname>
			</person>
			<person>
				<givenname>Tom</givenname>
				<surname>Maguire</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>For the last several decades the predominant architectural style for the implementation of data-centric applications has had a relational database at the core, procedural code implementing the application services and an object-oriented API. More recently the API has transitioned, via a slight detour through SOAP-based web services, to a RESTful style, however what lies beneath that interface has been slower to take a new approach. In this paper we argue that upgrading that which is under the covers to an XML-centric technology stack will result in a system that is easier to build, test and maintain. Further, these technologies are a step toward making construction of such systems available to non-programmers. We present an XML RESTful Services framework that provides mechanisms to address all of the key aspects of systems built in the RESTful architectural style.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/1967428.1967437</identifier>
		<pages>26-32</pages>
		<title type="sharef:primaryTitle">XML Technologies for RESTful Services Development</title>
	</reference>
	<reference name="dug11" src="bibtex:inproceedings" src-info="bibtex:line-14440" type="sharef:inproceedings" crossref="wsrest2011">
		<names type="sharef:author">
			<person>
				<givenname>Dave</givenname>
				<surname>Duggal</surname>
			</person>
			<person>
				<givenname>William</givenname>
				<surname>Malyk</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>The Ideate Framework is the result of a property-driven software development effort intended to improve the effectiveness and efficiency of Knowledge-work. The keys to supporting such work are identified as context-awareness and mass-customization, both of which are provided for by the framework in a practical, lightweight, scalable, and adaptable manner. Underpinning the framework is a new hybrid architecture promoting the scalability of distributed enterprise systems and the delivery of server-driven applications. The architecture shares some similarity to the Representational State Transfer (REST) style, against which it is contrasted. In addition, this paper describes the key components of the Ideate Framework, and compares the results against other related approaches.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/1967428.1967438</identifier>
		<pages>33-38</pages>
		<title type="sharef:primaryTitle">A Resource Oriented Framework for Context-Aware Enterprise Applications</title>
	</reference>
	<reference name="kay11" src="bibtex:inproceedings" src-info="bibtex:line-14449" type="sharef:inproceedings" crossref="wsrest2011">
		<names type="sharef:author">
			<person>
				<givenname>Joe</givenname>
				<surname>Kaylor</surname>
			</person>
			<person>
				<givenname>Konstantin</givenname>
				<surname>Läufer</surname>
			</person>
			<person>
				<givenname>George K.</givenname>
				<surname>Thiruvathukal</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>We have designed and implemented RestFS, a software framework that provides a uniform, configurable connector layer for mapping remote web-based resources to local filesystem-based resources, recognizing the similarity between these two types of resources. Such mappings enable programmatic access to a resource, as well as composition of two or more resources, through the local operating system's standard filesystem application programming interface (API), scriptable file-based command-line utilities, and inter-process communication (IPC) mechanisms. The framework supports automatic and manual authentication. We include several examples intended to show the utility and practicality of our framework.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/1967428.1967439</identifier>
		<pages>39-46</pages>
		<title type="sharef:primaryTitle">RestFS: Resources and Services are Filesystems, Too</title>
	</reference>
	<reference name="ath11" src="bibtex:inproceedings" src-info="bibtex:line-14458" type="sharef:inproceedings" crossref="wsrest2011">
		<names type="sharef:author">
			<person>
				<givenname>Michael</givenname>
				<surname>Athanasopoulos</surname>
			</person>
			<person>
				<givenname>Kostas</givenname>
				<surname>Kontogiannis</surname>
			</person>
			<person>
				<givenname>Chris</givenname>
				<surname>Brealey</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Interface uniformity is regarded as one of the most distinctive features of the REST architectural style among other network-based styles, because of the specific set of restrictions it imposes on the behavior paradigms of interacting components. However, in practice conforming to the REST's uniform interface constraint in Web-based services most often proves to be a difficult task, as identified by a number of researchers and practitioners. This implementation and conformance difficulty can be partly attributed to the lack of a systematic conceptual framework that could be used to interpret abstract architectural restrictions of interface uniformity to practical design decisions and strategies being generalized as interface design criteria. These criteria could be then mapped to domain-specific techniques that provide the context for guiding and/or examining the level of uniformity of a REST-based API. In this paper, we discuss such a conceptual framework and a collection of criteria that can be used to assess in a practical way as to whether a specific REST-based API conforms to the uniform interface constraint. As a proof of concept, we evaluated the proposed framework and its associated methodology by applying it to a collection of indicative public Web service APIs.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/1967428.1967440</identifier>
		<pages>47-50</pages>
		<title type="sharef:primaryTitle">Towards an Interpretation Framework for Assessing Interface Uniformity in REST</title>
	</reference>
	<reference name="gra11" src="bibtex:inproceedings" src-info="bibtex:line-14467" type="sharef:inproceedings" crossref="wsrest2011">
		<names type="sharef:author">
			<person>
				<givenname>Sebastian</givenname>
				<surname>Graf</surname>
			</person>
			<person>
				<givenname>Vyacheslav</givenname>
				<surname>Zholudev</surname>
			</person>
			<person>
				<givenname>Lukas</givenname>
				<surname>Lewandowski</surname>
			</person>
			<person>
				<givenname>Marcel</givenname>
				<surname>Waldvogel</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>The potentials of REST offers new ways for communications between louse coupled entities featured through the Web of Things [12]. The binding of the disjunct components of this architecture creates security issues, such as the centralized authorization techniques respecting the independence of the underlying entities. This results in the question how authorization is performed respecting the flexibility of REST without any knowledge about the underlying resources. Nevertheless, possible knowledge about these resources should enable the authorization workflow to offer finer-granular permissions on substructures of the resources. With our new approach - we named Hecate- we offer a framework to assure simplified handling while keeping the potentials and flexibility of REST. We have designed an architecture based on XML with a flexible authorization mechanism on the one hand and optional resource-awareness on the other hand. The flexibility within the authorization work-flow bases on permission sets respecting the HTTP-verbs. Additional in-depth knowledge of the entity optionally extends these permissions with resource-aware filters. Hecate offers not only great benefits because of its flexibility, but also because of the optional extensibility proved within the two reference implementations. With Hecate, we show that a centralized authorization mechanism combining independence and optional resource-based filtering extends the flexibility of REST rather than restricting it.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/1967428.1967442</identifier>
		<pages>51-58</pages>
		<title type="sharef:primaryTitle">Hecate, Managing Authorization with RESTful XML</title>
	</reference>
	<reference name="fie11" src="bibtex:inproceedings" src-info="bibtex:line-14476" type="sharef:inproceedings" crossref="wsrest2011">
		<names type="sharef:author">
			<person>
				<givenname>John P.</givenname>
				<surname>Field</surname>
			</person>
			<person>
				<givenname>Stephen G.</givenname>
				<surname>Graham</surname>
			</person>
			<person>
				<givenname>Tom</givenname>
				<surname>Maguire</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>An Obligation is an expression of non-functional or cross-cutting requirements, the scope of which transcends any specific service, but for which the service bears an enforcement responsibility. Example use cases include regulations imposed on handling of Electronic Health Records. We describe the concept of an Obligation, provide example use cases, and then define a general design pattern for when a REST developer should consider their use. We then describe a proof-of-concept implementation that extends the Spring Security framework to support the assertion of Obligations within a RESTful service deployment. This extension may be used to inject a range of Obligation behaviors into a REST service during the design, deployment, and post deployment phases. Our prototype is compatible with the XACML 3.0 core standard.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/1967428.1967443</identifier>
		<pages>59-66</pages>
		<title type="sharef:primaryTitle">A Framework for Obligation Fulfillment in REST Services</title>
	</reference>
	<reference name="kue11" src="bibtex:inproceedings" src-info="bibtex:line-14485" type="sharef:inproceedings" crossref="wsrest2011">
		<names type="sharef:author">
			<person>
				<givenname>Roland</givenname>
				<surname>Kübert</surname>
			</person>
			<person>
				<givenname>Gregory</givenname>
				<surname>Katsaros</surname>
			</person>
			<person>
				<givenname>Tinghe</givenname>
				<surname>Wang</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Representational State Transfer (REST) is an architectural style for distributed systems. RESTful web services have been gaining popularity in the last years. The Java API for RESTful Web Services (JAX-RS) has been specified as Java Specification Request 311 and is therefore an official part of Java; with the Jersey framework, a robust reference implementation of the specification exists. We examine in how far RESTful web services can fulfill tasks that have been defined as WS-* specifications. In particular, we investigate how a RESTful design and implementation of the WS-Agreement specification can be realized, presenting a light-weight approach to the creation and management of service level agreements.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/1967428.1967444</identifier>
		<pages>67-72</pages>
		<title type="sharef:primaryTitle">A RESTful Implementation of the WS-Agreement Specification</title>
	</reference>
	<reference name="wsrest2011" src="bibtex:proceedings" src-info="bibtex:line-14494" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>Cesare</givenname>
				<surname>Pautasso</surname>
			</person>
			<person>
				<givenname>Erik</givenname>
				<surname>Wilde</surname>
			</person>
			<person>
				<givenname>Rosa</givenname>
				<surname>Alarcón</surname>
			</person>
		</names>
		<date value="2011-03"/>
		<address type="sharef:placePublished">Hyderabad, India</address>
		<field type="bibtex:index">WS-REST 2011</field>
		<identifier type="sharef:isbn">978-1-4503-0623-2</identifier>
		<field type="bibtex:key">Second International Workshop on RESTful Design (WS-REST 2011)</field>
		<title type="sharef:primaryTitle">Second International Workshop on RESTful Design (WS-REST 2011)</title>
		<field type="bibtex:topic">rest[1]</field>
		<identifier type="sharef:uri">http://ws-rest.org/2011/</identifier>
		<identifier type="sharef:uri">http://portal.acm.org/citation.cfm?id=1967428</identifier>
		<identifier type="sharef:uri" resourceType="text/html">http://www.informatik.uni-trier.de/~ley/db/conf/rest/rest2011.html</identifier>
	</reference>
	<reference name="cac10" src="bibtex:inproceedings" src-info="bibtex:line-14514" type="sharef:inproceedings" crossref="w3cprivacy2010">
		<names type="sharef:author">
			<person>
				<givenname>Marcos</givenname>
				<surname>Cáceres</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>This paper critically evaluates the privacy aspects of Web Browsers that implement the W3C's Geolocation Specification. This paper concludes by making a number of recommendations that may be applicable to browser vendors and standards-setting bodies, such as the W3C.</p>
			</richtext>
		</abstract>
		<title type="sharef:primaryTitle">Privacy of Geolocation Implementations</title>
		<identifier type="sharef:uri" resourceType="application/pdf">http://www.w3.org/2010/api-privacy-ws/papers/privacy-ws-21.pdf</identifier>
	</reference>
	<reference name="coo10b" src="bibtex:inproceedings" src-info="bibtex:line-14522" type="sharef:inproceedings" crossref="w3cprivacy2010">
		<names type="sharef:author">
			<person>
				<givenname>Alissa</givenname>
				<surname>Cooper</surname>
			</person>
			<person>
				<givenname>John B.</givenname>
				<surname>Morris</surname>
			</person>
			<person>
				<givenname>Erica</givenname>
				<surname>Newland</surname>
			</person>
		</names>
		<title type="sharef:primaryTitle">Privacy Rulesets: A User-Empowering Approach to Privacy on the Web</title>
		<identifier type="sharef:uri" resourceType="text/html">http://www.w3.org/2010/api-privacy-ws/papers/privacy-ws-12.html</identifier>
	</reference>
	<reference name="ras10" src="bibtex:inproceedings" src-info="bibtex:line-14529" type="sharef:inproceedings" crossref="w3cprivacy2010">
		<names type="sharef:author">
			<person>
				<givenname>Aza</givenname>
				<surname>Raskin</surname>
			</person>
			<person>
				<givenname>Arun</givenname>
				<surname>Ranganathan</surname>
			</person>
		</names>
		<title type="sharef:primaryTitle">Privacy: A Pictographic Approach</title>
		<identifier type="sharef:uri" resourceType="text/plain">http://www.w3.org/2010/api-privacy-ws/papers/privacy-ws-22.txt</identifier>
	</reference>
	<reference name="fet10" src="bibtex:inproceedings" src-info="bibtex:line-14536" type="sharef:inproceedings" crossref="w3cprivacy2010">
		<names type="sharef:author">
			<person>
				<givenname>Ian</givenname>
				<surname>Fette</surname>
			</person>
			<person>
				<givenname>Jochen</givenname>
				<surname>Eisinger</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Google Chrome has implemented a number of "HTML5" APIs, including the Geolocation API and various storage APIs. In this paper we discuss some of our experiences on the Google Chrome team in implementing these APIs, as well as our thoughts around privacy for new APIs we are considering implementing. Specifically, we discuss our ideas of how providing access to things such as speech, web cameras, and filesystems can be done in ways that are understandable and in the natural flow of users.</p>
			</richtext>
		</abstract>
		<title type="sharef:primaryTitle">Practical Privacy Concerns in a Real World Browser</title>
		<identifier type="sharef:uri" resourceType="application/pdf">http://www.w3.org/2010/api-privacy-ws/papers/privacy-ws-24.pdf</identifier>
		<identifier type="sharef:uri" resourceType="text/html">http://research.google.com/pubs/pub36731.html</identifier>
	</reference>
	<reference name="due10" src="bibtex:inproceedings" src-info="bibtex:line-14545" type="sharef:inproceedings" crossref="w3cprivacy2010">
		<names type="sharef:author">
			<person>
				<givenname>Thomas</givenname>
				<surname>Dübendorfer</surname>
			</person>
			<person>
				<givenname>Christoph</givenname>
				<surname>Renner</surname>
			</person>
			<person>
				<givenname>Tyrone</givenname>
				<surname>Grandison</surname>
			</person>
			<person>
				<givenname>Michael</givenname>
				<surname>Maximilien</surname>
			</person>
			<person>
				<givenname>Mark</givenname>
				<surname>Weitzel</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>We present a social network inspired and access control list based sharing model for web resources. We have specified it as an extension for OpenSocial 1.0 and implemented a proof of concept in Orkut as well as a mobile social photo sharing application using it. The paper explains important design decisions and how the model can be leveraged to make privacy a core component and enabler for sharing resources on the web and beyond using capabilities of mobile devices.</p>
			</richtext>
		</abstract>
		<title type="sharef:primaryTitle">Making Privacy a Fundamental Component of Web Resources</title>
		<identifier type="sharef:uri" resourceType="text/html">http://research.google.com/pubs/pub36497.html</identifier>
		<identifier type="sharef:uri" resourceType="application/pdf">http://www.w3.org/2010/api-privacy-ws/papers/privacy-ws-26.pdf</identifier>
	</reference>
	<reference name="w3cprivacy2010" src="bibtex:proceedings" src-info="bibtex:line-14554" type="sharef:proceedings">
		<date value="2010-07"/>
		<address type="sharef:placePublished">London, UK</address>
		<field type="bibtex:key">W3C Workshop on Privacy for Advanced Web APIs</field>
		<title type="sharef:primaryTitle">W3C Workshop on Privacy for Advanced Web APIs</title>
		<identifier type="sharef:uri">http://www.w3.org/2010/api-privacy-ws/</identifier>
	</reference>
	<reference name="dot10c" src="bibtex:inproceedings" src-info="bibtex:line-14568" type="sharef:inproceedings" crossref="w3cpolicy">
		<names type="sharef:author">
			<person>
				<givenname>Nick</givenname>
				<surname>Doty</surname>
			</person>
			<person>
				<givenname>Erik</givenname>
				<surname>Wilde</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Relying on non-enforceable normative language to persuade Web sites to make their privacy practices clear has proven unsuccessful, and where privacy policies are present, they are notoriously unclear and unread. Various machine-readable techniques have been proposed to address this problem, but many have suffered from practical difficulties. We propose a simple standard for transmitting policy information just-in-time and enabling simple negotiation between the site and the user agent. In particular, we detail how this could improve privacy of the W3C Geolocation API, but also suggest the possibility of extension to other application areas in need of privacy and policy negotiations.</p>
			</richtext>
		</abstract>
		<title type="sharef:primaryTitle">Simple Policy Negotiation for Location Disclosure</title>
		<identifier type="sharef:uri">http://dret.net/netdret/publications#dot10c</identifier>
	</reference>
	<reference name="w3cpolicy" src="bibtex:proceedings" src-info="bibtex:line-14576" type="sharef:proceedings">
		<date value="2010-10"/>
		<address type="sharef:placePublished">Cambridge, Massachusetts</address>
		<field type="bibtex:key">W3C Workshop on Privacy and Data Usage Control</field>
		<title type="sharef:primaryTitle">W3C Workshop on Privacy and Data Usage Control</title>
		<identifier type="sharef:uri">http://www.w3.org/2010/policy-ws/</identifier>
	</reference>
	<reference name="wil08g" src="bibtex:inproceedings" src-info="bibtex:line-14590" type="sharef:inproceedings" crossref="exponwireless2008">
		<names type="sharef:author">
			<person>
				<givenname>Erik</givenname>
				<surname>Wilde</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Location-awareness, in the form of location information about clients and location-based services provided by servers, is becoming increasingly important for networked communications in general, and wireless and mobile devices in particular. The current fragmented landscape of location concepts and location-awareness, however, is not suitable for handling location information on a Web scale. Providing users with mechanisms which allow them to control how they want to expose their location information, and thus allow control over how to share location information with others and services, is a crucial step for better location management for mobile devices. This paper presents a concept for representing location vocabularies, matching and mapping them, how these vocabularies can be used to support better privacy for users of location-based services, and better location sharing between users and services. The concept is based on a language for describing place name vocabularies, which we call Place Markup Language (PlaceML), and on various ways how these vocabularies can be used in a location-aware infrastructure of networked devices.</p>
			</richtext>
		</abstract>
		<title type="sharef:primaryTitle">Location Management for Mobile Devices</title>
		<field type="bibtex:topic">placeml[0.9]</field>
		<identifier type="sharef:uri">http://dret.net/netdret/publications#wil08g</identifier>
	</reference>
	<reference name="exponwireless2008" src="bibtex:proceedings" src-info="bibtex:line-14599" type="sharef:proceedings">
		<date value="2008-06"/>
		<address type="sharef:placePublished">Newport Beach, California</address>
		<field type="bibtex:index">EXPONWIRELESS 2008</field>
		<field type="bibtex:key">3rd IEEE Workshop on Advanced Experimental Activities on Wireless Networks &amp; Systems (EXPONWIRELESS 2008)</field>
		<title type="sharef:primaryTitle">3rd IEEE Workshop on Advanced Experimental Activities on Wireless Networks &amp; Systems (EXPONWIRELESS 2008)</title>
		<identifier type="sharef:uri">http://nrl.iis.sinica.edu.tw/EXPONWIRELESS08/</identifier>
	</reference>
	<reference name="wil08n" src="bibtex:inproceedings" src-info="bibtex:line-14614" type="sharef:inproceedings" crossref="tipugg2008">
		<names type="sharef:author">
			<person>
				<givenname>Bernt</givenname>
				<surname>Wahl</surname>
			</person>
			<person>
				<givenname>Erik</givenname>
				<surname>Wilde</surname>
			</person>
		</names>
		<title type="sharef:primaryTitle">Mapping the World ... One Neighborhood at a Time</title>
		<identifier type="sharef:uri">http://dret.net/netdret/publications#wil08n</identifier>
	</reference>
	<reference name="tipugg2008" src="bibtex:proceedings" src-info="bibtex:line-14621" type="sharef:proceedings">
		<date value="2008-09"/>
		<address type="sharef:placePublished">Park City, Utah</address>
		<field type="bibtex:index">TIPUGG 2008</field>
		<field type="bibtex:key">First International Workshop on Trends in Pervasive and Ubiquitous Geotechnology and Geoinformation</field>
		<title type="sharef:primaryTitle">First International Workshop on Trends in Pervasive and Ubiquitous Geotechnology and Geoinformation</title>
		<identifier type="sharef:uri">http://ifgi.uni-muenster.de/tipugg/</identifier>
	</reference>
	<reference name="wil06b" src="bibtex:inproceedings" src-info="bibtex:line-14636" type="sharef:inproceedings" crossref="wbc2006">
		<names type="sharef:author">
			<person>
				<givenname>Erik</givenname>
				<surname>Wilde</surname>
			</person>
			<person>
				<givenname>Sai</givenname>
				<surname>Anand</surname>
			</person>
			<person>
				<givenname>Thierry</givenname>
				<surname>Bücheler</surname>
			</person>
			<person>
				<givenname>Nick</givenname>
				<surname>Nabholz</surname>
			</person>
			<person>
				<givenname>Petra</givenname>
				<surname>Zimmermann</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>In many research settings, bibliographies are a central resource for collecting information about related work, keeping track of the own research record, and annotating this information with remarks. By its very nature, this information should be shared between researchers within a research group and maybe in larger organizational units (for example research institutes) as well. However, most tools used for managing bibliographic data do not support collaboration. Using ShaRef, users can share bibliographic information, collaborate, and publish and export data using a variety of output channels. ShaRef's goal is to make sharing of and collaboration with bibliographic information easier than it is today.</p>
			</richtext>
		</abstract>
		<title type="sharef:primaryTitle">Bibliographies as Shared Resources</title>
		<identifier type="sharef:uri">http://dret.net/netdret/publications#wil06b</identifier>
	</reference>
	<reference name="wbc2006" src="bibtex:proceedings" src-info="bibtex:line-14644" type="sharef:proceedings">
		<date value="2006-02"/>
		<address type="sharef:placePublished">San Sebastián, Spain</address>
		<field type="bibtex:index">WBC 2006</field>
		<field type="bibtex:key">2006 IADIS International Conference on Web Based Communities</field>
		<title type="sharef:primaryTitle">2006 IADIS International Conference on Web Based Communities</title>
		<field type="bibtex:topic">www[0.8]</field>
		<identifier type="sharef:uri">http://www.iadis.org/WBC2006/</identifier>
	</reference>
	<reference name="wil06k" src="bibtex:inproceedings" src-info="bibtex:line-14660" type="sharef:inproceedings" crossref="gmw06">
		<names type="sharef:author">
			<person>
				<givenname>Erik</givenname>
				<surname>Wilde</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Wissensvermittlung setzt zu einem massgeblichen Teil nicht nur das Lehren von Fakten und Methoden voraus, sondern unverzichtbar auch deren Einordnung in den durch das Fachgebiet vorgegebenen Rahmen. Eine ICT Strategie wissensvermittelnder Organisationen sollte diesem weiten Fokus der Wissensvermittlung Rechnung tragen und durch strategische Zielsetzungen verhindern, dass geschlossene Insellösungen entstehen, die dem Ziel der Vermittlung vernetzten Wissens abträglich sind. Im Rahmen geeigneter strategischer und technischer Rahmenbedingungen können heutzutage basierend auf existierenden Technologien Tools entwickelt werden, die sich durch ihr modulares und offenes Konzept optimal im sich ständig ändernden ICT Umfeld einer Hochschule einsetzen lassen. Am Beispiel eines Tools zur Verwaltung von Literaturverweisen wird erläutert, wie eine offene ICT Strategie in Form technischer Lösungen umgesetzt werden kann.</p>
			</richtext>
		</abstract>
		<title type="sharef:primaryTitle">Modulare und Offene Komponenten zur Wissensverwaltung</title>
		<identifier type="sharef:uri">http://dret.net/netdret/publications#wil06k</identifier>
	</reference>
	<reference name="gmw06" src="bibtex:proceedings" src-info="bibtex:line-14668" type="sharef:proceedings">
		<date value="2006-09"/>
		<address type="sharef:placePublished">Zürich, Switzerland</address>
		<field type="bibtex:index">GMW06</field>
		<field type="bibtex:key">11. Europäische Jahrestagung der Gesellschaft für Medien in der Wissenschaft</field>
		<title type="sharef:primaryTitle">11. Europäische Jahrestagung der Gesellschaft für Medien in der Wissenschaft</title>
		<identifier type="sharef:uri">http://www.gmw06.ch/</identifier>
	</reference>
	<reference name="due01" src="bibtex:inproceedings" src-info="bibtex:line-14683" type="sharef:inproceedings" crossref="iuc19">
		<names type="sharef:author">
			<person>
				<givenname>Martin J.</givenname>
				<surname>Dürst</surname>
			</person>
		</names>
		<title type="sharef:primaryTitle">Internationalized Resource Identifiers: From Specification to Testing</title>
		<field type="bibtex:topic">iri[0.8]</field>
	</reference>
	<reference name="iuc19" src="bibtex:proceedings" src-info="bibtex:line-14690" type="sharef:proceedings">
		<date value="2001-09"/>
		<address type="sharef:placePublished">San Jose, California</address>
		<field type="bibtex:index">IUC19</field>
		<field type="bibtex:key">Nineteenth Internationalization and Unicode Conference</field>
		<title type="sharef:primaryTitle">Nineteenth Internationalization and Unicode Conference</title>
		<field type="bibtex:topic">unicode[0.8]</field>
		<identifier type="sharef:uri" resourceType="text/html">http://www.unicode.org/iuc/iuc19/program.html</identifier>
	</reference>
	<reference name="wil03h" src="bibtex:inproceedings" src-info="bibtex:line-14706" type="sharef:inproceedings" crossref="iuc24">
		<names type="sharef:author">
			<person>
				<givenname>Erik</givenname>
				<surname>Wilde</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>XML is based on Unicode, and therefore XML documents may use the full Unicode character repertoire. However, XML-based applications often use XML interfaces to legacy software which in many cases is not capable of dealing with the full Unicode character repertoire. We therefore propose a schema language for XML which is capable of limiting the character repertoire of XML documents. This schema language, called Character Repertoire Validation for XML (CRVX), has features to permit or disallow character repertoire subsets from certain parts of an XML document, for example only for element and attribute names. CRVX uses information from the Unicode Character Database (UCD) to make character repertoire specification as easy as possible. CRVX is not intended to be the only schema language in an XML application scenario, but it provides useful additional schema-based validation to protect applications from unsupported characters. XML applications typically combine different schema languages before processing XML documents, and CRVX is intended to complement other schema languages such as grammar-based languages (DTD, XML Schema) or rule-based languages (Schematron). CRVX can be implemented in various ways. One simple solution is to use XSLT to transform an CRVX schema into an XSLT program, which is then used to validate XML documents. We briefly describe such an implementation. Other (and more efficient) implementations could be based on DOM or SAX parsers.</p>
			</richtext>
		</abstract>
		<title type="sharef:primaryTitle">Validation of Character Repertoires for XML Documents</title>
		<field type="bibtex:topic">crvx[0.9]</field>
		<identifier type="sharef:uri">http://dret.net/netdret/publications#wil03h</identifier>
	</reference>
	<reference name="due03b" src="bibtex:inproceedings" src-info="bibtex:line-14715" type="sharef:inproceedings" crossref="iuc24">
		<names type="sharef:author">
			<person>
				<givenname>Martin J.</givenname>
				<surname>Dürst</surname>
			</person>
		</names>
		<title type="sharef:primaryTitle">Internationalized Resource Identifiers (IRIs): Server-side Implementation</title>
		<field type="bibtex:topic">iri[0.8]</field>
	</reference>
	<reference name="iuc24" src="bibtex:proceedings" src-info="bibtex:line-14722" type="sharef:proceedings">
		<date value="2003-09"/>
		<address type="sharef:placePublished">Atlanta, Georgia</address>
		<field type="bibtex:index">IUC24</field>
		<field type="bibtex:key">Twenty-fourth Internationalization and Unicode Conference</field>
		<title type="sharef:primaryTitle">Twenty-fourth Internationalization and Unicode Conference</title>
		<field type="bibtex:topic">unicode[0.8]</field>
		<identifier type="sharef:uri" resourceType="text/html">http://www.unicode.org/iuc/iuc24/program.html</identifier>
	</reference>
	<reference name="wil03j" src="bibtex:inproceedings" src-info="bibtex:line-14738" type="sharef:inproceedings" crossref="sinn03">
		<names type="sharef:author">
			<person>
				<givenname>Erik</givenname>
				<surname>Wilde</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Metadata usage often depends on schemas for metadata, which are important to convey the meaning of the metadata. We propose an architecture where users can extend the schema used by a system for managing referential metadata. Users can plugin new schemas and install custom filters for exporting metadata, so that users are not forced to limit their metadata to a fixed schema. The goal of this architecture is to provide users with a system that helps them managing their referatory, enables them with powerful tools to adapt the tool to their metadata, and still makes it possible to collect the metadata of several users in a central storage and exploit the common facets of the metadata. Our system is based on a specialized schema language, which has been built on top of the XML schema languages XML Schema and Schematron.</p>
			</richtext>
		</abstract>
		<title type="sharef:primaryTitle">Towards Federated Referatories</title>
		<field type="bibtex:topic">bibtexml[0.8]</field>
		<identifier type="sharef:uri">http://dret.net/netdret/publications#wil03j</identifier>
		<identifier type="sharef:uri" resourceType="text/html">http://www.isn-oldenburg.de/projects/SINN/sinn03/proceedings/wilde.html</identifier>
	</reference>
	<reference name="sinn03" src="bibtex:proceedings" src-info="bibtex:line-14748" type="sharef:proceedings">
		<date value="2003-09"/>
		<address type="sharef:placePublished">Oldenburg, Germany</address>
		<field type="bibtex:index">SINN03</field>
		<field type="bibtex:key">SINN03 Conference on Worldwide Coherent Workforce and Satisfied Users</field>
		<title type="sharef:primaryTitle">SINN03 Conference on Worldwide Coherent Workforce and Satisfied Users</title>
		<identifier type="sharef:uri" resourceType="text/html">http://www.isn-oldenburg.de/projects/SINN/sinn03/proceedings.html</identifier>
	</reference>
	<reference name="bau95" src="bibtex:inproceedings" src-info="bibtex:line-14763" type="sharef:inproceedings" crossref="tccc95">
		<names type="sharef:author">
			<person>
				<givenname>Daniel</givenname>
				<surname>Bauer</surname>
			</person>
			<person>
				<givenname>Erik</givenname>
				<surname>Wilde</surname>
			</person>
			<person>
				<givenname>Bernhard</givenname>
				<surname>Plattner</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>In the last years, networked multimedia multipoint applications have been developed in conjunction with emerging broadband networks. Experiences have shown that existing transport systems support these applications only insufficiently, since they offer no assistance for real-time multimedia and multipoint applications. In this paper, we propose a Multicast Communication Framework (MCF) which satisfies the needs of multimedia multipoint applications. MCF covers both transportation and presentation of multimedia data. It guarantees quality of service (QoS) for the complete path between multimedia sources and multimedia sinks. Furthermore, it offers a high-level abstraction of multicast communication services that hides the details of the underlying endsystems and networks.</p>
			</richtext>
		</abstract>
		<field type="bibtex:index">MCF, GMS</field>
		<title type="sharef:primaryTitle">Design Considerations for a Multicast Communication Framework</title>
		<identifier type="sharef:uri">http://dret.net/netdret/publications#bau95</identifier>
	</reference>
	<reference name="tccc95" src="bibtex:proceedings" src-info="bibtex:line-14772" type="sharef:proceedings">
		<date value="1995-09"/>
		<address type="sharef:placePublished">Eastsound, Washington</address>
		<field type="bibtex:index">TCCC '95</field>
		<title type="sharef:primaryTitle">Tenth Annual Workshop on Computer Communications</title>
	</reference>
	<reference name="fis88" src="bibtex:inproceedings" src-info="bibtex:line-14785" type="sharef:inproceedings" crossref="cois88">
		<names type="sharef:author">
			<person>
				<givenname>Robert S.</givenname>
				<surname>Fish</surname>
			</person>
			<person>
				<givenname>Robert E.</givenname>
				<surname>Kraut</surname>
			</person>
			<person>
				<givenname>Mary D. P.</givenname>
				<surname>Leland</surname>
			</person>
		</names>
		<field type="bibtex:index">Quilt, collaborative editing</field>
		<pages>30-37</pages>
		<title type="sharef:primaryTitle">Quilt: a collaborative tool for cooperative writing</title>
	</reference>
	<reference name="cois88" src="bibtex:proceedings" src-info="bibtex:line-14793" type="sharef:proceedings">
		<date value="1988-03"/>
		<address type="sharef:placePublished">Palo Alto, California</address>
		<field type="bibtex:index">COIS '88</field>
		<title type="sharef:primaryTitle">Conference on Office Information Systems</title>
	</reference>
	<reference name="pla94d" src="bibtex:inproceedings" src-info="bibtex:line-14806" type="sharef:inproceedings" crossref="pfhsn94">
		<names type="sharef:author">
			<person>
				<givenname>Thomas</givenname>
				<surname>Plagemann</surname>
			</person>
			<person>
				<givenname>Andreas</givenname>
				<surname>Gotti</surname>
			</person>
			<person>
				<givenname>Bernhard</givenname>
				<surname>Plattner</surname>
			</person>
		</names>
		<field type="bibtex:index">Da CaPo, CoRA</field>
		<title type="sharef:primaryTitle">CoRA — A Heuristic for Protocol Configuration and Resource Allocation</title>
	</reference>
	<reference name="pfhsn94" src="bibtex:proceedings" src-info="bibtex:line-14813" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>Mabo</givenname>
				<surname>Ito</surname>
			</person>
			<person>
				<givenname>Gerald W.</givenname>
				<surname>Neufeld</surname>
			</person>
		</names>
		<date value="1994-08"/>
		<address type="sharef:placePublished">Vancouver, Canada</address>
		<field type="bibtex:index">PfHSN '94</field>
		<title type="sharef:primaryTitle">4th International IFIP Workshop on Protocols for High Speed Networks</title>
	</reference>
	<reference name="pla94c" src="bibtex:inproceedings" src-info="bibtex:line-14827" type="sharef:inproceedings" crossref="hipp94">
		<names type="sharef:author">
			<person>
				<givenname>Thomas</givenname>
				<surname>Plagemann</surname>
			</person>
			<person>
				<givenname>Bernhard</givenname>
				<surname>Plattner</surname>
			</person>
		</names>
		<field type="bibtex:index">Da CaPo</field>
		<title type="sharef:primaryTitle">Evaluating Crucial Performance Issues of Protocol Configuration in Da CaPo</title>
	</reference>
	<reference name="hipp94" src="bibtex:proceedings" src-info="bibtex:line-14834" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>Jon</givenname>
				<surname>Crowcroft</surname>
			</person>
			<person>
				<givenname>Christian</givenname>
				<surname>Huitema</surname>
			</person>
		</names>
		<date value="1994-12"/>
		<address type="sharef:placePublished">Sophia Antipolis, France</address>
		<field type="bibtex:index">HIPPARCH '94</field>
		<title type="sharef:primaryTitle">First International Workshop on High Performance Protocol Architectures</title>
	</reference>
	<reference name="ber90" src="bibtex:inproceedings" src-info="bibtex:line-14848" type="sharef:inproceedings" crossref="cois90">
		<names type="sharef:author">
			<person>
				<givenname>Elisa</givenname>
				<surname>Bertino</surname>
			</person>
			<person>
				<givenname>M.</givenname>
				<surname>Negri</surname>
			</person>
			<person>
				<givenname>G.</givenname>
				<surname>Pelagatti</surname>
			</person>
			<person>
				<givenname>L.</givenname>
				<surname>Sbatella</surname>
			</person>
		</names>
		<field type="bibtex:index">COMANDOS</field>
		<pages>216-226</pages>
		<title type="sharef:primaryTitle">An Object-Oriented Data Model for Distributed Office Applications</title>
	</reference>
	<reference name="cois90" src="bibtex:proceedings" src-info="bibtex:line-14856" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>Frederick H.</givenname>
				<surname>Lochovsky</surname>
			</person>
			<person>
				<givenname>Robert B.</givenname>
				<surname>Allen</surname>
			</person>
		</names>
		<date value="1990-04"/>
		<address type="sharef:placePublished">Cambridge, Massachusetts</address>
		<field type="bibtex:index">COIS '90</field>
		<identifier type="sharef:isbn">0897913582</identifier>
		<title type="sharef:primaryTitle">Conference on Office Information Systems</title>
	</reference>
	<reference name="har91" src="bibtex:inproceedings" src-info="bibtex:line-14871" type="sharef:inproceedings" crossref="ocs91">
		<names type="sharef:author">
			<person>
				<givenname>Harrick M.</givenname>
				<surname>Vin</surname>
			</person>
			<person>
				<givenname>P. Venkat</givenname>
				<surname>Rangan</surname>
			</person>
			<person>
				<givenname>Srinivas</givenname>
				<surname>Ramanathan</surname>
			</person>
		</names>
		<field type="bibtex:index">super conferences</field>
		<pages>43-54</pages>
		<title type="sharef:primaryTitle">Hierachical Conferencing Architectures for Inter-Group Multimedia Collaboration</title>
	</reference>
	<reference name="ham91" src="bibtex:inproceedings" src-info="bibtex:line-14879" type="sharef:inproceedings" crossref="ocs91">
		<names type="sharef:author">
			<person>
				<givenname>Heikki</givenname>
				<surname>Hämmäinen</surname>
			</person>
			<person>
				<givenname>Chris</givenname>
				<surname>Condon</surname>
			</person>
		</names>
		<field type="bibtex:index">MILAN, PAGES, groupware, metaphors</field>
		<pages>95-105</pages>
		<title type="sharef:primaryTitle">Form and Room: Metaphors for Groupware</title>
	</reference>
	<reference name="new91" src="bibtex:inproceedings" src-info="bibtex:line-14887" type="sharef:inproceedings" crossref="ocs91">
		<names type="sharef:author">
			<person>
				<givenname>R. E.</givenname>
				<surname>Newman-Wolfe</surname>
			</person>
			<person>
				<givenname>Harsha K.</givenname>
				<surname>Pelimuhandiram</surname>
			</person>
		</names>
		<field type="bibtex:index">MACE, collaborative editing</field>
		<pages>240-254</pages>
		<title type="sharef:primaryTitle">MACE: A Fine Grained Concurrent Editor</title>
	</reference>
	<reference name="ocs91" src="bibtex:proceedings" src-info="bibtex:line-14895" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>Peter</givenname>
				<surname link="de">Jong</surname>
			</person>
		</names>
		<date value="1991-11"/>
		<address type="sharef:placePublished">Atlanta, Georgia</address>
		<field type="bibtex:index">OCS '91</field>
		<identifier type="sharef:isbn">0897914562</identifier>
		<title type="sharef:primaryTitle">ACM SIGOIS Conference on Organizational Computer Systems</title>
	</reference>
	<reference name="haa94" src="bibtex:inproceedings" src-info="bibtex:line-14910" type="sharef:inproceedings" crossref="hms94">
		<names type="sharef:author">
			<person>
				<givenname>Jörg M.</givenname>
				<surname>Haake</surname>
			</person>
			<person>
				<givenname>Catherine C.</givenname>
				<surname>Marshall</surname>
			</person>
			<person>
				<givenname>Uffe Kock</givenname>
				<surname>Wiil</surname>
			</person>
		</names>
		<field type="bibtex:index">collaborative hypermedia</field>
		<pages>5-11</pages>
		<title type="sharef:primaryTitle">Open Issues in Collaborative Hypermedia Systems</title>
	</reference>
	<reference name="kon94" src="bibtex:inproceedings" src-info="bibtex:line-14918" type="sharef:inproceedings" crossref="hms94">
		<names type="sharef:author">
			<person>
				<givenname>Shin'ichi</givenname>
				<surname>Konomi</surname>
			</person>
			<person>
				<givenname>Osami</givenname>
				<surname>Kagawa</surname>
			</person>
			<person>
				<givenname>Yahiko</givenname>
				<surname>Kambayashi</surname>
			</person>
		</names>
		<field type="bibtex:index">VIEW, collaborative hypermedia</field>
		<pages>30-33</pages>
		<title type="sharef:primaryTitle">VIEW Media: A Multiuser Hypermedia System for Interactive Distance Presentation</title>
	</reference>
	<reference name="hms94" src="bibtex:proceedings" src-info="bibtex:line-14926" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>Jörg M.</givenname>
				<surname>Haake</surname>
			</person>
		</names>
		<date value="1994-10"/>
		<address type="sharef:placePublished">Chapel Hill, North Carolina</address>
		<field type="bibtex:index">CSCW '94</field>
		<identifier type="sharef:isbn">3884572393</identifier>
		<publisher>Gesellschaft für Mathematik und Datenverarbeitung mbH</publisher>
		<title type="sharef:seriesTitle">GMD-Studien</title>
		<title type="sharef:primaryTitle">CSCW'94 Workshop Collaborative Hypermedia Systems</title>
		<field type="bibtex:topic">cscw[0.8]</field>
		<volume>239</volume>
	</reference>
	<reference name="kir93c" src="bibtex:inproceedings" src-info="bibtex:line-14945" type="sharef:inproceedings" crossref="inet93">
		<names type="sharef:author">
			<person>
				<givenname>Peter T.</givenname>
				<surname>Kirstein</surname>
			</person>
			<person>
				<givenname>Mark J.</givenname>
				<surname>Handley</surname>
			</person>
			<person>
				<givenname>M. Angela</givenname>
				<surname>Sasse</surname>
			</person>
		</names>
		<field type="bibtex:index">MICE</field>
		<pages>DCA-1-DCA-12</pages>
		<title type="sharef:primaryTitle">Piloting of Multimedia Integrated Communications for European Researchers (MICE)</title>
	</reference>
	<reference name="chu93" src="bibtex:inproceedings" src-info="bibtex:line-14953" type="sharef:inproceedings" crossref="inet93">
		<names type="sharef:author">
			<person>
				<givenname>S.</givenname>
				<surname>Chuang</surname>
			</person>
			<person>
				<givenname>Jon</givenname>
				<surname>Crowcroft</surname>
			</person>
			<person>
				<givenname>S.</givenname>
				<surname>Hailes</surname>
			</person>
			<person>
				<givenname>Mark J.</givenname>
				<surname>Handley</surname>
			</person>
			<person>
				<givenname>N.</givenname>
				<surname>Ismail</surname>
			</person>
			<person>
				<givenname>D.</givenname>
				<surname>Lewis</surname>
			</person>
			<person>
				<givenname>I.</givenname>
				<surname>Wakeman</surname>
			</person>
		</names>
		<field type="bibtex:index">multicast, conferencing, multimedia systems</field>
		<pages>BFB-1-BFB-9</pages>
		<title type="sharef:primaryTitle">Multimedia Application Requirements for Multicast Communications Services</title>
	</reference>
	<reference name="vog93b" src="bibtex:inproceedings" src-info="bibtex:line-14961" type="sharef:inproceedings" crossref="inet93">
		<names type="sharef:author">
			<person>
				<givenname>Martin</givenname>
				<surname>Vogt</surname>
			</person>
			<person>
				<givenname>Bernhard</givenname>
				<surname>Plattner</surname>
			</person>
			<person>
				<givenname>Thomas</givenname>
				<surname>Plagemann</surname>
			</person>
			<person>
				<givenname>Thomas</givenname>
				<surname>Walter</surname>
			</person>
		</names>
		<field type="bibtex:index">Da CaPo</field>
		<pages>BFC-1-BFC-9</pages>
		<title type="sharef:primaryTitle">A Run-time Environment for Da CaPo</title>
	</reference>
	<reference name="inet93" src="bibtex:proceedings" src-info="bibtex:line-14969" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>Barry</givenname>
				<surname>Leiner</surname>
			</person>
		</names>
		<date value="1993-08"/>
		<address type="sharef:placePublished">San Francisco, California</address>
		<field type="bibtex:index">INET '93</field>
		<title type="sharef:primaryTitle">International Networking Conference INET'93</title>
	</reference>
	<reference name="sha96" src="bibtex:inproceedings" src-info="bibtex:line-14983" type="sharef:inproceedings" crossref="inet96">
		<names type="sharef:author">
			<person>
				<givenname>Keith</givenname>
				<surname>Shafer</surname>
			</person>
			<person>
				<givenname>Stuart L.</givenname>
				<surname>Weibel</surname>
			</person>
			<person>
				<givenname>Erik</givenname>
				<surname>Jul</surname>
			</person>
			<person>
				<givenname>Jon</givenname>
				<surname>Fausey</surname>
			</person>
		</names>
		<pages>BFC-1-BFC-9</pages>
		<title type="sharef:primaryTitle">Introduction to Persistent Uniform Resource Locators</title>
		<field type="bibtex:topic">purl[1]</field>
		<identifier type="sharef:uri" resourceType="text/html">http://purl.oclc.org/docs/inet96.html</identifier>
	</reference>
	<reference name="inet96" src="bibtex:proceedings" src-info="bibtex:line-14992" type="sharef:proceedings">
		<date value="1996-06"/>
		<address type="sharef:placePublished">Montréal, Canada</address>
		<field type="bibtex:index">INET '96</field>
		<field type="bibtex:key">International Networking Conference INET'96</field>
		<title type="sharef:primaryTitle">International Networking Conference INET'96</title>
	</reference>
	<reference name="gad92" src="bibtex:inproceedings" src-info="bibtex:line-15006" type="sharef:inproceedings" crossref="icc92">
		<names type="sharef:author">
			<person>
				<givenname>Michael E.</givenname>
				<surname>Gaddis</surname>
			</person>
			<person>
				<givenname>Rick G.</givenname>
				<surname>Bubenik</surname>
			</person>
			<person>
				<givenname>John D.</givenname>
				<surname>DeHart</surname>
			</person>
		</names>
		<field type="bibtex:index">CMAP, ATM signaling, call model</field>
		<pages>609-615</pages>
		<title type="sharef:primaryTitle">A Call Model for Multipoint Communication in Switched Networks</title>
	</reference>
	<reference name="icc92" src="bibtex:proceedings" src-info="bibtex:line-15014" type="sharef:proceedings">
		<date value="1992-06"/>
		<address type="sharef:placePublished">Chicago, Illinois</address>
		<field type="bibtex:index">ICC '92</field>
		<title type="sharef:primaryTitle">IEEE International Conference on Communications</title>
	</reference>
	<reference name="mae91" src="bibtex:inproceedings" src-info="bibtex:line-15027" type="sharef:inproceedings" crossref="icc91">
		<names type="sharef:author">
			<person>
				<givenname>Kazutoshi</givenname>
				<surname>Maeno</surname>
			</person>
			<person>
				<givenname>Shiro</givenname>
				<surname>Sakata</surname>
			</person>
			<person>
				<givenname>Toyoko</givenname>
				<surname>Ohmori</surname>
			</person>
		</names>
		<field type="bibtex:index">MERMAID</field>
		<pages>520-525</pages>
		<title type="sharef:primaryTitle">Distributed Desktop Conferencing System (MERMAID) Based on Group Communication Architecture</title>
	</reference>
	<reference name="icc91" src="bibtex:proceedings" src-info="bibtex:line-15035" type="sharef:proceedings">
		<date value="1991-06"/>
		<address type="sharef:placePublished">Denver, Colorado</address>
		<field type="bibtex:index">ICC '91</field>
		<title type="sharef:primaryTitle">IEEE International Conference on Communications</title>
	</reference>
	<reference name="gre86" src="bibtex:inproceedings" src-info="bibtex:line-15048" type="sharef:inproceedings" crossref="cscw86">
		<names type="sharef:author">
			<person>
				<givenname>Irene</givenname>
				<surname>Greif</surname>
			</person>
			<person>
				<givenname>Sunil</givenname>
				<surname>Sarin</surname>
			</person>
		</names>
		<field type="bibtex:index">RTCAL, MPCAL, CES</field>
		<pages>175-183</pages>
		<title type="sharef:primaryTitle">Data Sharing in Group Work</title>
	</reference>
	<reference name="cscw86" src="bibtex:proceedings" src-info="bibtex:line-15056" type="sharef:proceedings">
		<date value="1986"/>
		<field type="bibtex:index">CSCW '86</field>
		<title type="sharef:primaryTitle">First Conference on Computer-Supported Cooperative Work</title>
		<field type="bibtex:topic">cscw[0.8]</field>
	</reference>
	<reference name="lai88" src="bibtex:inproceedings" src-info="bibtex:line-15068" type="sharef:inproceedings" crossref="cscw88">
		<names type="sharef:author">
			<person>
				<givenname>Kum-Yew</givenname>
				<surname>Lai</surname>
			</person>
			<person>
				<givenname>Thomas W.</givenname>
				<surname>Malone</surname>
			</person>
		</names>
		<field type="bibtex:index">Object Lens, Information Lens</field>
		<pages>115-124</pages>
		<title type="sharef:primaryTitle">Object Lens: A "Spreadsheet" for Cooperative Work</title>
	</reference>
	<reference name="lel88" src="bibtex:inproceedings" src-info="bibtex:line-15076" type="sharef:inproceedings" crossref="cscw88">
		<names type="sharef:author">
			<person>
				<givenname>Mary D. P.</givenname>
				<surname>Leland</surname>
			</person>
			<person>
				<givenname>Robert S.</givenname>
				<surname>Fish</surname>
			</person>
			<person>
				<givenname>Robert E.</givenname>
				<surname>Kraut</surname>
			</person>
		</names>
		<field type="bibtex:index">Quilt, collaborative editing</field>
		<pages>206-215</pages>
		<title type="sharef:primaryTitle">Collaborative Document Production using Quilt</title>
	</reference>
	<reference name="cscw88" src="bibtex:proceedings" src-info="bibtex:line-15084" type="sharef:proceedings">
		<date value="1988"/>
		<address type="sharef:placePublished">Portland, Oregon</address>
		<field type="bibtex:index">CSCW '88</field>
		<identifier type="sharef:isbn">0897912829</identifier>
		<publisher>ACM Press</publisher>
		<title type="sharef:primaryTitle">Conference on Computer-Supported Cooperative Work</title>
		<field type="bibtex:topic">cscw[0.8]</field>
	</reference>
	<reference name="ben03c" src="bibtex:inproceedings" src-info="bibtex:line-15099" type="sharef:inproceedings" crossref="icfp03">
		<names type="sharef:author">
			<person>
				<givenname>Véronique</givenname>
				<surname>Benzaken</surname>
			</person>
			<person>
				<givenname>Giuseppe</givenname>
				<surname>Castagna</surname>
			</person>
			<person>
				<givenname>Alain</givenname>
				<surname>Frisch</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>We present the functional language CDuce, discuss some design issues, and show its adequacy for working with XML documents. Distinctive features of CDuce are a powerful pattern matching, first class functions, overloaded functions, a very rich type system (arrows, sequences, pairs, records, intersections, unions, differences), precise type inference for patterns and error localization, and a natural interpretation of types as sets of values. We also outline some important implementation issues; in particular, a dispatch algorithm that demonstrates how static type information can be used to obtain very efficient compilation schemas.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/944710</identifier>
		<pages>51-63</pages>
		<title type="sharef:primaryTitle">CDuce: An XML-Centric General-Purpose Language</title>
		<field type="bibtex:topic">cduce[1]</field>
		<identifier type="sharef:uri">http://doi.acm.org/10.1145/944710</identifier>
	</reference>
	<reference name="icfp03" src="bibtex:proceedings" src-info="bibtex:line-15110" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>Colin</givenname>
				<surname>Runciman</surname>
			</person>
			<person>
				<givenname>Olin</givenname>
				<surname>Shivers</surname>
			</person>
		</names>
		<date value="2003-08"/>
		<address type="sharef:placePublished">Uppsala, Sweden</address>
		<field type="bibtex:index">ICFP 2003</field>
		<identifier type="sharef:isbn">1-58113-756-7</identifier>
		<publisher>ACM Press</publisher>
		<title type="sharef:primaryTitle">Eighth ACM SIGPLAN International Conference on Functional Programming</title>
		<identifier type="sharef:uri" resourceType="text/html">http://www.informatik.uni-trier.de/~ley/db/conf/icfp/icfp2003.html</identifier>
	</reference>
	<reference name="gen09" src="bibtex:inproceedings" src-info="bibtex:line-15127" type="sharef:inproceedings" crossref="icfp09">
		<names type="sharef:author">
			<person>
				<givenname>Pierre</givenname>
				<surname>Genevès</surname>
			</person>
			<person>
				<givenname>Nabil</givenname>
				<surname>Layaïda</surname>
			</person>
			<person>
				<givenname>Vincent</givenname>
				<surname>Quint</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>During the life cycle of an XML application, both schemas and queries may change from one version to another. Schema evolutions may affect query results and potentially the validity of produced data. Nowadays, a challenge is to assess and accommodate the impact of theses changes in rapidly evolving XML applications. This article proposes a logical framework and tool for verifying forward/backward compatibility issues involving schemas and queries. First, it allows analyzing relations between schemas. Second, it allows XML designers to identify queries that must be reformulated in order to produce the expected results across successive schema versions. Third, it allows examining more precisely the impact of schema changes over queries, therefore facilitating their reformulation.</p>
			</richtext>
		</abstract>
		<title type="sharef:primaryTitle">Ensuring Query Compatibility with Evolving XML Schemas</title>
		<identifier type="sharef:uri" resourceType="application/pdf">http://wam.inrialpes.fr/publications/2008/RR6711.pdf</identifier>
	</reference>
	<reference name="icfp09" src="bibtex:proceedings" src-info="bibtex:line-15135" type="sharef:proceedings">
		<date value="2009-08"/>
		<address type="sharef:placePublished">Edinburgh, UK</address>
		<field type="bibtex:index">ICFP 2009</field>
		<publisher>ACM Press</publisher>
		<title type="sharef:primaryTitle">14th ACM SIGPLAN International Conference on Functional Programming</title>
		<identifier type="sharef:uri" resourceType="text/html">http://www.informatik.uni-trier.de/~ley/db/conf/icfp/icfp2009.html</identifier>
	</reference>
	<reference name="sch96" src="bibtex:inproceedings" src-info="bibtex:line-15150" type="sharef:inproceedings" crossref="idms96">
		<names type="sharef:author">
			<person>
				<givenname>Henning</givenname>
				<surname>Schulzrinne</surname>
			</person>
		</names>
		<field type="bibtex:index">MUCS</field>
		<pages>143-161</pages>
		<title type="sharef:primaryTitle">Personal Mobility for Multimedia Services in the Internet</title>
	</reference>
	<reference name="mat96" src="bibtex:inproceedings" src-info="bibtex:line-15158" type="sharef:inproceedings" crossref="idms96">
		<names type="sharef:author">
			<person>
				<givenname>Laurent</givenname>
				<surname>Mathy</surname>
			</person>
		</names>
		<field type="bibtex:index">ACCOPI, AMTS</field>
		<pages>175-194</pages>
		<title type="sharef:primaryTitle">Features of the ACCOPI Multimedia Transport Service</title>
	</reference>
	<reference name="yea96" src="bibtex:inproceedings" src-info="bibtex:line-15166" type="sharef:inproceedings" crossref="idms96">
		<names type="sharef:author">
			<person>
				<givenname>Nicholas</givenname>
				<surname>Yeadon</surname>
			</person>
			<person>
				<givenname>Andreas</givenname>
				<surname>Mauthe</surname>
			</person>
			<person>
				<givenname>Francisco</givenname>
				<surname>García</surname>
			</person>
			<person>
				<givenname>David</givenname>
				<surname>Hutchison</surname>
			</person>
		</names>
		<field type="bibtex:index">QoS-A, QoS filters</field>
		<pages>227-243</pages>
		<title type="sharef:primaryTitle">QoS Filters: Addressing the Heterogeneity Gap</title>
	</reference>
	<reference name="idms96" src="bibtex:proceedings" src-info="bibtex:line-15174" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>Berthold</givenname>
				<surname>Butscher</surname>
			</person>
			<person>
				<givenname>Eckhard</givenname>
				<surname>Moeller</surname>
			</person>
			<person>
				<givenname>Herwart</givenname>
				<surname>Pusch</surname>
			</person>
		</names>
		<date value="1996-03"/>
		<address type="sharef:placePublished">Berlin, Germany</address>
		<publisher>Springer-Verlag</publisher>
		<title type="sharef:seriesTitle">Lecture Notes in Computer Science</title>
		<title type="sharef:primaryTitle">European Workshop on Interactive Distributed Multimedia Systems and Services</title>
		<volume>1045</volume>
	</reference>
	<reference name="ber88" src="bibtex:inproceedings" src-info="bibtex:line-15190" type="sharef:inproceedings" crossref="edbt88">
		<names type="sharef:author">
			<person>
				<givenname>Elisa</givenname>
				<surname>Bertino</surname>
			</person>
			<person>
				<givenname>Fausto</givenname>
				<surname>Rabitti</surname>
			</person>
			<person>
				<givenname>Costantino</givenname>
				<surname>Thanos</surname>
			</person>
		</names>
		<field type="bibtex:index">MULTOS</field>
		<pages>606-615</pages>
		<title type="sharef:primaryTitle">MULTOS: A Document Server for Distributed Office Systems</title>
	</reference>
	<reference name="edbt88" src="bibtex:proceedings" src-info="bibtex:line-15198" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>Joachim W.</givenname>
				<surname>Schmidt</surname>
			</person>
			<person>
				<givenname>Stefano</givenname>
				<surname>Ceri</surname>
			</person>
			<person>
				<givenname>Michele</givenname>
				<surname>Missikoff</surname>
			</person>
		</names>
		<date value="1988-03"/>
		<address type="sharef:placePublished">Venice, Italy</address>
		<identifier type="sharef:isbn">3540190740</identifier>
		<publisher>Springer-Verlag</publisher>
		<title type="sharef:seriesTitle">Lecture Notes in Computer Science</title>
		<title type="sharef:primaryTitle">International Conference on Extending Database Technology</title>
		<volume>303</volume>
	</reference>
	<reference name="sch00b" src="bibtex:inproceedings" src-info="bibtex:line-15215" type="sharef:inproceedings" crossref="edbt2000">
		<names type="sharef:author">
			<person>
				<givenname>Harald</givenname>
				<surname>Schöning</surname>
			</person>
			<person>
				<givenname>Jürgen</givenname>
				<surname>Wäsch</surname>
			</person>
		</names>
		<pages>383-387</pages>
		<title type="sharef:primaryTitle">Tamino — An Internet Database System</title>
		<field type="bibtex:topic">tamino[1]</field>
	</reference>
	<reference name="edbt2000" src="bibtex:proceedings" src-info="bibtex:line-15223" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>Carlo</givenname>
				<surname>Zaniolo</surname>
			</person>
			<person>
				<givenname>Peter C.</givenname>
				<surname>Lockemann</surname>
			</person>
			<person>
				<givenname>Marc H.</givenname>
				<surname>Scholl</surname>
			</person>
			<person>
				<givenname>Torsten</givenname>
				<surname>Grust</surname>
			</person>
		</names>
		<date value="2000-03"/>
		<address type="sharef:placePublished">Konstanz, Germany</address>
		<field type="bibtex:index">EDBT 2000</field>
		<identifier type="sharef:isbn">3540672273</identifier>
		<publisher>Springer-Verlag</publisher>
		<title type="sharef:seriesTitle">Lecture Notes in Computer Science</title>
		<title type="sharef:primaryTitle">Advances in Database Technology: 7th International Conference on Extending Database Technology</title>
		<identifier type="sharef:uri" resourceType="text/html">http://link.springer.de/link/service/series/0558/tocs/t1777.htm</identifier>
		<volume>1777</volume>
	</reference>
	<reference name="mei04" src="bibtex:inproceedings" src-info="bibtex:line-15242" type="sharef:inproceedings" crossref="edbt2004ws">
		<names type="sharef:author">
			<person>
				<givenname>Ulrich</givenname>
				<surname>Meissen</surname>
			</person>
			<person>
				<givenname>Stefan</givenname>
				<surname>Pfennigschmidt</surname>
			</person>
			<person>
				<givenname>Agnès</givenname>
				<surname>Voisard</surname>
			</person>
			<person>
				<givenname>Tjark</givenname>
				<surname>Wahnfried</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>In order to deliver relevant information at the right time to its mobile users, systems such as event notification systems need to be aware of the users' context, which includes the current time, their location, or the devices they use. Many context frameworks have been introduced in the past few years. However, they usually do not consider the notion of characteristic features of contexts that are invariant during certain time intervals. Knowing the current situation of a user allows the system to better target the information to be delivered. This paper presents a model to handle various contexts and situations in information logistics. A context is defined as a collection of values usually observed by sensors, e.g., location or temperature. A situation builds on this concept by introducing semantical aspects defined in an ontology. Our situation awareness proposal has been tested in two projects.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1007/b101218</identifier>
		<pages>335-344</pages>
		<title type="sharef:primaryTitle">Context- and Situation-Awareness in Information Logistics</title>
		<field type="bibtex:topic">tamino[1]</field>
		<identifier type="sharef:uri">http://www.springerlink.com/content/lkgum4wjmyuy55hu/</identifier>
	</reference>
	<reference name="edbt2004ws" src="bibtex:proceedings" src-info="bibtex:line-15253" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>Wolfgang</givenname>
				<surname>Lindner</surname>
			</person>
			<person>
				<givenname>Marco</givenname>
				<surname>Mesiti</surname>
			</person>
			<person>
				<givenname>Can</givenname>
				<surname>Türker</surname>
			</person>
			<person>
				<givenname>Yannis</givenname>
				<surname>Tzitzikas</surname>
			</person>
			<person>
				<givenname>Athena</givenname>
				<surname>Vakali</surname>
			</person>
		</names>
		<date value="2004-03"/>
		<address type="sharef:placePublished">Heraklion, Greece</address>
		<field type="bibtex:index">EDBT 2004</field>
		<identifier type="sharef:isbn">978-3-540-23305-3</identifier>
		<publisher>Springer-Verlag</publisher>
		<title type="sharef:seriesTitle">Lecture Notes in Computer Science</title>
		<title type="sharef:primaryTitle">Current Trends in Database Technology — EDBT 2004 Workshops</title>
		<identifier type="sharef:uri">http://www.springerlink.com/content/tpkb57t0qhxr</identifier>
		<volume>3268</volume>
	</reference>
	<reference name="che86" src="bibtex:inproceedings" src-info="bibtex:line-15272" type="sharef:inproceedings" crossref="networking">
		<names type="sharef:author">
			<person>
				<givenname>David R.</givenname>
				<surname>Cheriton</surname>
			</person>
		</names>
		<field type="bibtex:index">k-reliability</field>
		<pages>296-312</pages>
		<title type="sharef:primaryTitle">Request-Response and Multicast Interprocess Communication in the V Kernel</title>
	</reference>
	<reference name="networking" src="bibtex:proceedings" src-info="bibtex:line-15280" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>Günter</givenname>
				<surname>Müller</surname>
			</person>
			<person>
				<givenname>Robert P.</givenname>
				<surname>Blanc</surname>
			</person>
		</names>
		<date value="1986-08"/>
		<address type="sharef:placePublished">Oberlech, Austria</address>
		<publisher>Springer-Verlag</publisher>
		<title type="sharef:seriesTitle">Lecture Notes in Computer Science</title>
		<title type="sharef:primaryTitle">Networking in Open Systems</title>
		<volume>248</volume>
	</reference>
	<reference name="mor92" src="bibtex:inproceedings" src-info="bibtex:line-15296" type="sharef:inproceedings" crossref="nossdav92">
		<names type="sharef:author">
			<person>
				<givenname>Mark</givenname>
				<surname>Moran</surname>
			</person>
			<person>
				<givenname>Riccardo</givenname>
				<surname>Gusella</surname>
			</person>
		</names>
		<field type="bibtex:index">X11, SharedX, ACME, QuickTime, ISI/BBN, Tenet, IP multicast</field>
		<pages>143-156</pages>
		<title type="sharef:primaryTitle">System Support for Efficient Dynamically-Configurable Multi-Party Interactive Multimedia Applications</title>
	</reference>
	<reference name="pas92" src="bibtex:inproceedings" src-info="bibtex:line-15304" type="sharef:inproceedings" crossref="nossdav92">
		<names type="sharef:author">
			<person>
				<givenname>Joseph C.</givenname>
				<surname>Pasquale</surname>
			</person>
			<person>
				<givenname>George C.</givenname>
				<surname>Polyzos</surname>
			</person>
			<person>
				<givenname>Eric W.</givenname>
				<surname>Anderson</surname>
			</person>
			<person>
				<givenname>Vachaspathi P.</givenname>
				<surname>Kompella</surname>
			</person>
		</names>
		<field type="bibtex:index">MMC, multicast</field>
		<pages>197-208</pages>
		<title type="sharef:primaryTitle">The Multimedia Multicast Channel</title>
	</reference>
	<reference name="nossdav92" src="bibtex:proceedings" src-info="bibtex:line-15312" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>P. Venkat</givenname>
				<surname>Rangan</surname>
			</person>
		</names>
		<date value="1992-11"/>
		<address type="sharef:placePublished">La Jolla, California</address>
		<field type="bibtex:index">NOSSDAV '92</field>
		<identifier type="sharef:isbn">3540571833</identifier>
		<publisher>Springer-Verlag</publisher>
		<title type="sharef:seriesTitle">Lecture Notes in Computer Science</title>
		<title type="sharef:primaryTitle">3rd International Workshop on Network and Operating System Support for Digital Audio and Video</title>
		<volume>712</volume>
	</reference>
	<reference name="cam93" src="bibtex:inproceedings" src-info="bibtex:line-15330" type="sharef:inproceedings" crossref="nossdav93">
		<names type="sharef:author">
			<person>
				<givenname>Andrew T.</givenname>
				<surname>Campbell</surname>
			</person>
			<person>
				<givenname>Geoff</givenname>
				<surname>Coulson</surname>
			</person>
			<person>
				<givenname>David</givenname>
				<surname>Hutchison</surname>
			</person>
		</names>
		<field type="bibtex:index">QoS-A, QoS, METS, multimedia</field>
		<pages>124-137</pages>
		<title type="sharef:primaryTitle">A Multimedia Enhanced Transport Service in a Quality of Service Architecture</title>
	</reference>
	<reference name="del93" src="bibtex:inproceedings" src-info="bibtex:line-15338" type="sharef:inproceedings" crossref="nossdav93">
		<names type="sharef:author">
			<person>
				<givenname>Luca</givenname>
				<surname>Delgrossi</surname>
			</person>
			<person>
				<givenname>Ralf Guido</givenname>
				<surname>Herrtwich</surname>
			</person>
			<person>
				<givenname>Carsten</givenname>
				<surname>Vogt</surname>
			</person>
			<person>
				<givenname>Lars C.</givenname>
				<surname>Wolf</surname>
			</person>
		</names>
		<field type="bibtex:index">ST-II, RSVP</field>
		<pages>195-203</pages>
		<title type="sharef:primaryTitle">Reservation Protocols for Internetworks: A Comparison of ST-II and RSVP</title>
	</reference>
	<reference name="fry93" src="bibtex:inproceedings" src-info="bibtex:line-15346" type="sharef:inproceedings" crossref="nossdav93">
		<names type="sharef:author">
			<person>
				<givenname>Michael</givenname>
				<surname>Fry</surname>
			</person>
			<person>
				<givenname>Antony</givenname>
				<surname>Richards</surname>
			</person>
			<person>
				<givenname>Aruna</givenname>
				<surname>Seneviratne</surname>
			</person>
		</names>
		<field type="bibtex:index">QoS</field>
		<pages>138-148</pages>
		<title type="sharef:primaryTitle">Framework for Implementing the Next Generation of Communication Protocols</title>
	</reference>
	<reference name="nossdav93" src="bibtex:proceedings" src-info="bibtex:line-15354" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>Doug</givenname>
				<surname>Shepherd</surname>
			</person>
			<person>
				<givenname>Gordon S.</givenname>
				<surname>Blair</surname>
			</person>
			<person>
				<givenname>Geoff</givenname>
				<surname>Coulson</surname>
			</person>
			<person>
				<givenname>N.</givenname>
				<surname>Davies</surname>
			</person>
			<person>
				<givenname>Francisco</givenname>
				<surname>García</surname>
			</person>
		</names>
		<date value="1993-11"/>
		<address type="sharef:placePublished">Lancaster, UK</address>
		<field type="bibtex:index">NOSSDAV '93</field>
		<identifier type="sharef:isbn">3540584048</identifier>
		<publisher>Springer-Verlag</publisher>
		<title type="sharef:seriesTitle">Lecture Notes in Computer Science</title>
		<title type="sharef:primaryTitle">4th International Workshop on Network and Operating System Support for Digital Audio and Video</title>
		<volume>846</volume>
	</reference>
	<reference name="alm95" src="bibtex:inproceedings" src-info="bibtex:line-15372" type="sharef:inproceedings" crossref="nossdav95">
		<names type="sharef:author">
			<person>
				<givenname>Kevin C.</givenname>
				<surname>Almeroth</surname>
			</person>
			<person>
				<givenname>Mostafa H.</givenname>
				<surname>Ammar</surname>
			</person>
		</names>
		<field type="bibtex:index">VOD, multicast</field>
		<pages>251-254</pages>
		<title type="sharef:primaryTitle">The Role of Multicast Communication in the Provision of Scalable and Interactive Video-On-Demand Service</title>
	</reference>
	<reference name="fer95" src="bibtex:inproceedings" src-info="bibtex:line-15380" type="sharef:inproceedings" crossref="nossdav95">
		<names type="sharef:author">
			<person>
				<givenname>Domenico</givenname>
				<surname>Ferrari</surname>
			</person>
			<person>
				<givenname>Amit</givenname>
				<surname>Gupta</surname>
			</person>
			<person>
				<givenname>Giorgio</givenname>
				<surname>Ventre</surname>
			</person>
		</names>
		<field type="bibtex:index">multicast, Tenet</field>
		<pages>16-27</pages>
		<title type="sharef:primaryTitle">Distributed advance reservation of real-time connections</title>
	</reference>
	<reference name="bet95" src="bibtex:inproceedings" src-info="bibtex:line-15388" type="sharef:inproceedings" crossref="nossdav95">
		<names type="sharef:author">
			<person>
				<givenname>R.</givenname>
				<surname>Bettati</surname>
			</person>
			<person>
				<givenname>Domenico</givenname>
				<surname>Ferrari</surname>
			</person>
			<person>
				<givenname>Amit</givenname>
				<surname>Gupta</surname>
			</person>
			<person>
				<givenname>Wendy</givenname>
				<surname>Heffner</surname>
			</person>
			<person>
				<givenname>W.</givenname>
				<surname>Howe</surname>
			</person>
			<person>
				<givenname>Mark</givenname>
				<surname>Moran</surname>
			</person>
			<person>
				<givenname>Q.</givenname>
				<surname>Nguyen</surname>
			</person>
			<person>
				<givenname>R.</givenname>
				<surname>Yavatkar</surname>
			</person>
		</names>
		<field type="bibtex:index">Tenet, multicast, connection establishment</field>
		<pages>240-250</pages>
		<title type="sharef:primaryTitle">Connection Establishment for Multi-Party Real-Time Communication</title>
	</reference>
	<reference name="sch95" src="bibtex:inproceedings" src-info="bibtex:line-15396" type="sharef:inproceedings" crossref="nossdav95">
		<names type="sharef:author">
			<person>
				<givenname>Henning</givenname>
				<surname>Schulzrinne</surname>
			</person>
		</names>
		<field type="bibtex:index">multicast, conferencing systems, mbone, RTP, NeVoT</field>
		<pages>216-227</pages>
		<title type="sharef:primaryTitle">Dynamic Configuration of Conferencing Applications using Pattern-Matching Multicast</title>
	</reference>
	<reference name="nossdav95" src="bibtex:proceedings" src-info="bibtex:line-15404" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>Thomas D. C.</givenname>
				<surname>Little</surname>
			</person>
			<person>
				<givenname>Riccardo</givenname>
				<surname>Gusella</surname>
			</person>
		</names>
		<date value="1995-04"/>
		<address type="sharef:placePublished">Durham, New Hampshire</address>
		<field type="bibtex:index">NOSSDAV '95</field>
		<identifier type="sharef:isbn">3540606475</identifier>
		<publisher>Springer-Verlag</publisher>
		<title type="sharef:seriesTitle">Lecture Notes in Computer Science</title>
		<title type="sharef:primaryTitle">5th International Workshop on Network and Operating System Support for Digital Audio and Video</title>
		<volume>1018</volume>
	</reference>
	<reference name="mar91" src="bibtex:inproceedings" src-info="bibtex:line-15422" type="sharef:inproceedings" crossref="iwcscw91">
		<names type="sharef:author">
			<person>
				<givenname>J. A.</givenname>
				<surname>Mariani</surname>
			</person>
			<person>
				<givenname>Tom A.</givenname>
				<surname>Rodden</surname>
			</person>
		</names>
		<pages>146-161</pages>
		<title type="sharef:primaryTitle">The Impact of CSCW on Database Technology</title>
	</reference>
	<reference name="ben91" src="bibtex:inproceedings" src-info="bibtex:line-15429" type="sharef:inproceedings" crossref="iwcscw91">
		<names type="sharef:author">
			<person>
				<givenname>Steven</givenname>
				<surname>Benford</surname>
			</person>
			<person>
				<givenname>Hugh</givenname>
				<surname>Smith</surname>
			</person>
			<person>
				<givenname>Alan</givenname>
				<surname>Shepherd</surname>
			</person>
			<person>
				<givenname>Howidy</givenname>
				<surname>Howidy</surname>
			</person>
		</names>
		<pages>232-251</pages>
		<title type="sharef:primaryTitle">Information Sharing in CSCW: From Models to Architecture</title>
	</reference>
	<reference name="iwcscw91" src="bibtex:proceedings" src-info="bibtex:line-15436" type="sharef:proceedings">
		<date value="1991-04"/>
		<address type="sharef:placePublished">Berlin, Germany</address>
		<identifier type="sharef:isbn">02332582</identifier>
		<title type="sharef:primaryTitle">International Workshop on CSCW</title>
		<field type="bibtex:topic">cscw[0.8]</field>
	</reference>
	<reference name="pin94" src="bibtex:inproceedings" src-info="bibtex:line-15450" type="sharef:inproceedings" crossref="metrics94">
		<names type="sharef:author">
			<person>
				<givenname>Sridhar</givenname>
				<surname>Pingali</surname>
			</person>
			<person>
				<givenname>Don</givenname>
				<surname>Towsley</surname>
			</person>
			<person>
				<givenname>James F.</givenname>
				<surname>Kurose</surname>
			</person>
		</names>
		<field type="bibtex:index">reliable multicast</field>
		<pages>221-230</pages>
		<title type="sharef:primaryTitle">A Comparison of Sender-Initiated and Receiver-Initiated Reliable Multicast Protocols</title>
	</reference>
	<reference name="metrics94" src="bibtex:proceedings" src-info="bibtex:line-15458" type="sharef:proceedings">
		<date value="1994-05"/>
		<address type="sharef:placePublished">Nashville, Tennessee</address>
		<field type="bibtex:index">SIGMETRICS '94</field>
		<identifier type="sharef:isbn">089791659X</identifier>
		<title type="sharef:primaryTitle">ACM Sigmetrics Conference on Measurement &amp; Modeling of Computer Systems</title>
	</reference>
	<reference name="tal01" src="bibtex:inproceedings" src-info="bibtex:line-15472" type="sharef:inproceedings" crossref="metrics2001">
		<names type="sharef:author">
			<person>
				<givenname>Jerome</givenname>
				<surname>Talim</surname>
			</person>
			<person>
				<givenname>Zhen Hua</givenname>
				<surname>Liu</surname>
			</person>
			<person>
				<givenname>Philippe</givenname>
				<surname>Nain</surname>
			</person>
			<person>
				<givenname>Edward G.</givenname>
				<surname>Coffman</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Robots are deployed by a Web search engine for collecting information from different Web servers in order to maintain the currency of its data base of Web pages. In this paper, we investigate the number of robots to be used by a search engine so as to maximize the currency of the data base without putting an unnecessary load on the network. We adopt a finite-buffer queueing model to represent the system. The arrivals to the queueing system are Web pages brought by the robots; service corresponds to the indexing of these pages. Good performance requires that the number of robots, and thus the arrival rate of the queueing system, be chosen so that the indexing queue is rarely starved or saturated. Thus, we formulate a multi-criteria stochastic optimization problem with the loss rate and empty-buffer probability being the criteria. We take the common approach of reducing the problem to one with a single objective that is a linear function of the given criteria. Both static and dynamic policies can be considered. In the static setting the number of robots is held fixed; in the dynamic setting robots may be re-activated/de-activated as a function of the state. Under the assumption that arrivals form a Poisson process and that service times are independent and exponentially distributed random variables, we determine an optimal decision rule for the dynamic setting, i.e., a rule that varies the number of robots in such a way as to minimize a given linear function of the loss rate and empty-buffer probability. Our results are compared with known results for the static case. A numerical study indicates that substantial gains can be achieved by dynamically controlling the activity of the robots.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/378420.378788</identifier>
		<pages>236-244</pages>
		<title type="sharef:primaryTitle">Controlling the Robots of Web Search Engines</title>
	</reference>
	<reference name="metrics2001" src="bibtex:proceedings" src-info="bibtex:line-15481" type="sharef:proceedings">
		<date value="2001-06"/>
		<address type="sharef:placePublished">Cambridge, Massachusetts</address>
		<field type="bibtex:index">SIGMETRICS 2001</field>
		<field type="bibtex:key">2001 ACM SIGMETRICS International Conference on Measurement and Modeling of Computer Systems</field>
		<title type="sharef:primaryTitle">2001 ACM SIGMETRICS International Conference on Measurement and Modeling of Computer Systems</title>
		<identifier type="sharef:uri" resourceType="text/html">http://www.informatik.uni-trier.de/~ley/db/conf/sigmetrics/sigmetrics2001.html</identifier>
	</reference>
	<reference name="cha84" src="bibtex:inproceedings" src-info="bibtex:line-15496" type="sharef:inproceedings" crossref="sigmod84">
		<names type="sharef:author">
			<person>
				<givenname>J.-M.</givenname>
				<surname>Chang</surname>
			</person>
		</names>
		<field type="bibtex:index">distributed database, multicast, broadcast</field>
		<pages>223-233</pages>
		<title type="sharef:primaryTitle">Simplifying Distributed Database Systems Design by Using a Broadcast Network</title>
	</reference>
	<reference name="sigmod84" src="bibtex:proceedings" src-info="bibtex:line-15504" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>Beatrice</givenname>
				<surname>Yormark</surname>
			</person>
		</names>
		<date value="1984-06"/>
		<address type="sharef:placePublished">Boston, Massachusetts</address>
		<field type="bibtex:index">SIGMOD '84</field>
		<title type="sharef:primaryTitle">SIGMOD'84</title>
	</reference>
	<reference name="fuh01" src="bibtex:inproceedings" src-info="bibtex:line-15518" type="sharef:inproceedings" crossref="sigir2001">
		<names type="sharef:author">
			<person>
				<givenname>Norbert</givenname>
				<surname>Fuhr</surname>
			</person>
			<person>
				<givenname>Kai</givenname>
				<surname>Großjohann</surname>
			</person>
		</names>
		<pages>172-180</pages>
		<title type="sharef:primaryTitle">XIRQL: A Query Language for Information Retrieval in XML Documents</title>
		<field type="bibtex:topic">xirql[1]</field>
		<identifier type="sharef:uri" resourceType="application/pdf">http://patty.informatik.uni-duisburg.de/bib/fulltext/ir/Fuhr_Grossjohann:01.pdf</identifier>
	</reference>
	<reference name="sigir2001" src="bibtex:proceedings" src-info="bibtex:line-15527" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>W. Bruce</givenname>
				<surname>Croft</surname>
			</person>
			<person>
				<givenname>David J.</givenname>
				<surname>Harper</surname>
			</person>
			<person>
				<givenname>Donald H.</givenname>
				<surname>Kraft</surname>
			</person>
			<person>
				<givenname>Justin</givenname>
				<surname>Zobel</surname>
			</person>
		</names>
		<date value="2001-09"/>
		<address type="sharef:placePublished">New Orleans, Louisiana</address>
		<field type="bibtex:index">SIGIR 2001</field>
		<identifier type="sharef:isbn">1-58113-331-6</identifier>
		<title type="sharef:primaryTitle">24th Annual International Conference on Research and Development in Information Retrieval</title>
	</reference>
	<reference name="the02" src="bibtex:inproceedings" src-info="bibtex:line-15542" type="sharef:inproceedings" crossref="sigmod2002">
		<names type="sharef:author">
			<person>
				<givenname>Anja</givenname>
				<surname>Theobald</surname>
			</person>
			<person>
				<givenname>Gerhard</givenname>
				<surname>Weikum</surname>
			</person>
		</names>
		<title type="sharef:primaryTitle">The XXL Search Engine: Ranked Retrieval of XML Data Using Indexes and Ontologies</title>
		<field type="bibtex:topic">xxl[1]</field>
		<identifier type="sharef:uri" resourceType="application/pdf">http://www-dbs.cs.uni-sb.de/papers/sources/2002/tw00-sigmod02.pdf</identifier>
	</reference>
	<reference name="sigmod2002" src="bibtex:proceedings" src-info="bibtex:line-15550" type="sharef:proceedings">
		<date value="2002-06"/>
		<address type="sharef:placePublished">Madison, Wisconsin</address>
		<field type="bibtex:index">SIGMOD 2002</field>
		<title type="sharef:primaryTitle">ACM SIGMOD 2002 Conference</title>
		<identifier type="sharef:uri">http://www.acm.org/sigmod/sigmod02/eproceedings/</identifier>
	</reference>
	<reference name="hal05" src="bibtex:inproceedings" src-info="bibtex:line-15564" type="sharef:inproceedings" crossref="sigmod2005">
		<names type="sharef:author">
			<person>
				<givenname>Alon Y.</givenname>
				<surname>Halevy</surname>
			</person>
			<person>
				<givenname>Naveen</givenname>
				<surname>Ashish</surname>
			</person>
			<person>
				<givenname>Dina</givenname>
				<surname>Bitton</surname>
			</person>
			<person>
				<givenname>Michael J.</givenname>
				<surname>Carey</surname>
			</person>
			<person>
				<givenname>Denise</givenname>
				<surname>Draper</surname>
			</person>
			<person>
				<givenname>Jeff</givenname>
				<surname>Pollock</surname>
			</person>
			<person>
				<givenname>Arnon</givenname>
				<surname>Rosenthal</surname>
			</person>
			<person>
				<givenname>Vishal</givenname>
				<surname>Sikka</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>The goal of EII systems is to provide uniform access to multiple data sources without having to first load them into a data warehouse. Since the late 1990's, several EII products have appeared in the marketplace and significant experience has been accumulated from fielding such systems. This collection of articles, by individuals who were involved in this industry in various ways, describes some of these experiences and points to the challenges ahead.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/1066157.1066246</identifier>
		<pages>778-787</pages>
		<title type="sharef:primaryTitle">Enterprise Information Integration: Successes, Challenges and Controversies</title>
		<field type="bibtex:topic">eii[1]</field>
		<identifier type="sharef:uri">http://portal.acm.org/citation.cfm?doid=1066157.1066246</identifier>
	</reference>
	<reference name="sigmod2005" src="bibtex:proceedings" src-info="bibtex:line-15575" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>Fatma</givenname>
				<surname>Özcan</surname>
			</person>
		</names>
		<date value="2005-06"/>
		<address type="sharef:placePublished">Baltimore, Maryland</address>
		<field type="bibtex:index">SIGMOD 2005</field>
		<identifier type="sharef:isbn">1-59593-060-4</identifier>
		<publisher>ACM Press</publisher>
		<title type="sharef:primaryTitle">ACM SIGMOD 2005 International Conference on Management of Data</title>
		<identifier type="sharef:uri" resourceType="text/html">http://www.informatik.uni-trier.de/~ley/db/conf/sigmod/sigmod2005.html</identifier>
	</reference>
	<reference name="ger06" src="bibtex:inproceedings" src-info="bibtex:line-15592" type="sharef:inproceedings" crossref="sigmod2006">
		<names type="sharef:author">
			<person>
				<givenname>Nicholas</givenname>
				<surname>Gerner</surname>
			</person>
			<person>
				<givenname>Fan</givenname>
				<surname>Yang</surname>
			</person>
			<person>
				<givenname>Alan J.</givenname>
				<surname>Demers</surname>
			</person>
			<person>
				<givenname>Johannes</givenname>
				<surname>Gehrke</surname>
			</person>
			<person>
				<givenname>Mirek</givenname>
				<surname>Riedewald</surname>
			</person>
			<person>
				<givenname>Jayavel</givenname>
				<surname>Shanmugasundaram</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Current application development tools provide completely different programming models for the application server (e.g., Java and J2EE) and the client web browser (e.g., JavaScript and HTML). Consequently, the application developer is forced to partition the application code between the server and client at the time of writing the application. However, the partitioning of the code between the client and server may have to be changed during the evolution of the application for performance reasons (it may be better to push more functionality to the client), for correctness reasons (data that conflicts with multiple clients cannot always be pushed to clients), and for supporting clients with different computing power (browsers on desktops vs. PDAs). Since the client and server use different programming models, moving application code from client to server (and vice versa) reduces programmer productivity and also has the potential to introduce concurrency bugs. In this demonstration, we advocate an alternative solution to this problem: we propose developing applications using a unified declarative high-level language called Hilda, and show how a Hilda compiler can automatically (and correctly) partition Hilda code between the client and the server using a real Course Management System application. We illustrate our techniques using two clients: a powerful laptop machine and a less powerful PDA.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/1142473.1142580</identifier>
		<pages>760-762</pages>
		<title type="sharef:primaryTitle">Automatic Client-Server Partitioning of Data-Driven Web Applications</title>
		<identifier type="sharef:uri" resourceType="application/pdf">http://www.cs.cornell.edu/~yangf/152.pdf</identifier>
	</reference>
	<reference name="pap06" src="bibtex:inproceedings" src-info="bibtex:line-15602" type="sharef:inproceedings" crossref="sigmod2006">
		<names type="sharef:author">
			<person>
				<givenname>Olga</givenname>
				<surname>Papaemmanouil</surname>
			</person>
			<person>
				<givenname>Yanif</givenname>
				<surname>Ahmad</surname>
			</person>
			<person>
				<givenname>Uğur</givenname>
				<surname>Çetintemel</surname>
			</person>
			<person>
				<givenname>John</givenname>
				<surname>Jannotti</surname>
			</person>
			<person>
				<givenname>Yenel</givenname>
				<surname>Yildirim</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>We introduce XPORT, a profile-driven distributed data dissemination system that supports an extensible set of data types, profile types, and optimization metrics. XPORT efficiently implements a generic tree-based overlay network, which can be customized per application using a small number of methods that encapsulate application-specific data filtering, profile aggregation, and optimization logic. The clean separation between the "plumbing" and "application" enables the system to uniformly support disparate dissemination-based applications.We first provide an overview of the basic XPORT model and architecture. We then describe in detail an extensible optimization framework, based on a two-level aggregation model, that facilitates easy specification of a wide range of commonly used performance goals. We discuss distributed tree transformation protocols that allow XPORT to iteratively optimize its operation to achieve these goals under changing network and application conditions. Finally, we demonstrate the flexibility and the effectiveness of XPORT using real-world data and experimental results obtained from both prototype-based LAN emulation and deployment on PlanetLab.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/1142473.1142541</identifier>
		<pages>611-622</pages>
		<title type="sharef:primaryTitle">Extensible Optimization in Overlay Dissemination Trees</title>
		<identifier type="sharef:uri" resourceType="application/pdf">http://www.cs.brandeis.edu/~olga/Papaemmanouil/Publications_files/xport_sigmod06.pdf</identifier>
	</reference>
	<reference name="sigmod2006" src="bibtex:proceedings" src-info="bibtex:line-15612" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>Surajit</givenname>
				<surname>Chaudhuri</surname>
			</person>
			<person>
				<givenname>Vagelis</givenname>
				<surname>Hristidis</surname>
			</person>
			<person>
				<givenname>Neoklis</givenname>
				<surname>Polyzotis</surname>
			</person>
		</names>
		<date value="2006-06"/>
		<address type="sharef:placePublished">Chicago, Illinois</address>
		<field type="bibtex:index">SIGMOD 2006</field>
		<identifier type="sharef:isbn">1-59593-256-9</identifier>
		<publisher>ACM Press</publisher>
		<title type="sharef:primaryTitle">ACM SIGMOD 2006 International Conference on Management of Data</title>
		<identifier type="sharef:uri" resourceType="text/html">http://www.informatik.uni-trier.de/~ley/db/conf/sigmod/sigmod2006.html</identifier>
	</reference>
	<reference name="gou07" src="bibtex:inproceedings" src-info="bibtex:line-15629" type="sharef:inproceedings" crossref="sigmod2007">
		<names type="sharef:author">
			<person>
				<givenname>Gang</givenname>
				<surname>Gou</surname>
			</person>
			<person>
				<givenname>Rada</givenname>
				<surname>Chirkova</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>In this paper we address the problem of evaluating XPath queries over streaming XML data. We consider a practical XPath fragment called Univariate XPath, which includes the commonly used '/' and '//' axes and allows *-node tests and arbitrarily nested predicates. It is well known that this XPath fragment can be efficiently evaluated in O(|D||Q|) time in the non-streaming environment, where |D| is the document size and |Q| is the query size. However, this is not necessarily true in the streaming environment, since streaming algorithms have to satisfy stricter requirement than non-streaming algorithms, in that all data must be read sequentially in one pass. Therefore, it is not surprising that state-of-the-art stream-querying algorithms have higher time complexity than O(|D||Q|). In this paper we revisit the XPath stream-querying problem, and show that Univariate XPath can be efficiently evaluated in O|D||Q|) time in the streaming environment. Specifically, we propose two O(|D||Q|)-time stream-querying algorithms, LQ and EQ, which are based on the lazy strategy and on the eager strategy, respectively. To the best of our knowledge, LQ and EQ are the first XPath stream-querying algorithms that achieve O(|D||Q|) time performance. Further, our algorithms achieve O(|D||Q|) time performance without trading off space performance. Instead, they have better buffering-space performance than state-of-the-art stream-querying algorithms. In particular, EQ achieves optimal buffering-space performance. Our experimental results show that our algorithms have not only good theoretical complexity but also considerable practical performance advantages over existing algorithms.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/1247480.1247512</identifier>
		<pages>269-280</pages>
		<title type="sharef:primaryTitle">Efficient Algorithms for Evaluating XPath over Streams</title>
		<field type="bibtex:topic">xpath[0.9]</field>
	</reference>
	<reference name="sigmod2007" src="bibtex:proceedings" src-info="bibtex:line-15639" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>Chee Yong</givenname>
				<surname>Chan</surname>
			</person>
			<person>
				<givenname>Beng Chin</givenname>
				<surname>Ooi</surname>
			</person>
			<person>
				<givenname>Aoying</givenname>
				<surname>Zhou</surname>
			</person>
		</names>
		<date value="2007-06"/>
		<address type="sharef:placePublished">Beijing, China</address>
		<field type="bibtex:index">SIGMOD 2007</field>
		<identifier type="sharef:isbn">978-1-59593-686-8</identifier>
		<publisher>ACM Press</publisher>
		<title type="sharef:primaryTitle">ACM SIGMOD 2007 International Conference on Management of Data</title>
		<identifier type="sharef:uri" resourceType="text/html">http://www.informatik.uni-trier.de/~ley/db/conf/sigmod/sigmod2007.html</identifier>
	</reference>
	<reference name="cou07" src="bibtex:inproceedings" src-info="bibtex:line-15656" type="sharef:inproceedings" crossref="acmgis2007">
		<names type="sharef:author">
			<person>
				<givenname>Scott</givenname>
				<surname>Counts</surname>
			</person>
			<person>
				<givenname>Marc</givenname>
				<surname>Smith</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>We consider trails to be a document type of growing importance, authored in abundance as locative technologies become embedded in mobile devices carried by billions of humans. As these trail documents become annotated by communities of users, the resulting data sets can provide support for a host of services. In this paper we describe our socio-technical exploration of the devices, scenarios, and end-user interactions that will come into play as these tools become widespread. We couch this work in a discussion of the sociological impact of a shift from hyperlinks to "hyperties" — links that bridge the gap between computational media and physical world interactions. We describe a prototype hardware device for location and other sensor data capture. This device links to a complementary website for querying, sharing, and distributing the resulting route datasets. The web application allows users to find related community members via shared attributes of their contributed or annotated routes. These attributes may be generated in part by route analysis performed by systems for activity identification and classification.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/1341012.1341026</identifier>
		<pages>10-17</pages>
		<title type="sharef:primaryTitle">Where Were We: Communities for Sharing Space-Time Trails</title>
	</reference>
	<reference name="mar07" src="bibtex:inproceedings" src-info="bibtex:line-15665" type="sharef:inproceedings" crossref="acmgis2007">
		<names type="sharef:author">
			<person>
				<givenname>Sergio</givenname>
				<surname>Di Martino</surname>
			</person>
			<person>
				<givenname>Filomena</givenname>
				<surname>Ferrucci</surname>
			</person>
			<person>
				<givenname>Luca</givenname>
				<surname>Paolino</surname>
			</person>
			<person>
				<givenname>Monica</givenname>
				<surname>Sebillo</surname>
			</person>
			<person>
				<givenname>Genny</givenname>
				<surname>Tortora</surname>
			</person>
			<person>
				<givenname>Giuseppe</givenname>
				<surname>Vitiello</surname>
			</person>
			<person>
				<givenname>Giuseppe</givenname>
				<surname>Avagliano</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>In the present paper, we propose an approach for the development of Web GIS based on WebML, a high-level, formal visual language specifically conceived to design data-intensive Web applications. The proposal is motivated by the observation that Web GIS can be considered as a particular class of data-intensive Web applications. In the paper, we describe the extension of the visual formalism for modeling relevant interaction and navigation operations typical of Web GIS.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/1341012.1341081</identifier>
		<pages>57-64</pages>
		<title type="sharef:primaryTitle">Towards the Automatic Generation of Web GIS</title>
		<field type="bibtex:topic">webml[0.9]</field>
	</reference>
	<reference name="acmgis2007" src="bibtex:proceedings" src-info="bibtex:line-15675" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>Hanan</givenname>
				<surname>Samet</surname>
			</person>
			<person>
				<givenname>Cyrus</givenname>
				<surname>Shahabi</surname>
			</person>
			<person>
				<givenname>Markus</givenname>
				<surname>Schneider</surname>
			</person>
		</names>
		<date value="2007-11"/>
		<address type="sharef:placePublished">Seattle, Washington</address>
		<field type="bibtex:index">GIS 2007</field>
		<identifier type="sharef:isbn">978-1-59593-914-2</identifier>
		<publisher>ACM Press</publisher>
		<title type="sharef:primaryTitle">15th ACM International Symposium on Geographic Information Systems</title>
		<identifier type="sharef:uri" resourceType="text/html">http://www.informatik.uni-trier.de/~ley/db/conf/gis/gis2007.html</identifier>
	</reference>
	<reference name="tei08" src="bibtex:inproceedings" src-info="bibtex:line-15692" type="sharef:inproceedings" crossref="acmgis2008">
		<names type="sharef:author">
			<person>
				<givenname>Benjamin E.</givenname>
				<surname>Teitler</surname>
			</person>
			<person>
				<givenname>Michael D.</givenname>
				<surname>Lieberman</surname>
			</person>
			<person>
				<givenname>Daniele</givenname>
				<surname>Panozzo</surname>
			</person>
			<person>
				<givenname>Jagan</givenname>
				<surname>Sankaranarayanan</surname>
			</person>
			<person>
				<givenname>Hanan</givenname>
				<surname>Samet</surname>
			</person>
			<person>
				<givenname>Jon</givenname>
				<surname>Sperling</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>News articles contain a wealth of implicit geographic content that if exposed to readers improves understanding of today's news. However, most articles are not explicitly geotagged with their geographic content, and few news aggregation systems expose this content to users. A new system named NewsStand is presented that collects, analyzes, and displays news stories in a map interface, thus leveraging on their implicit geographic content. NewsStand monitors RSS feeds from thousands of online news sources and retrieves articles within minutes of publication. It then extracts geographic content from articles using a custom-built geotagger, and groups articles into story clusters using a fast online clustering algorithm. By panning and zooming in NewsStand's map interface, users can retrieve stories based on both topical significance and geographic region, and see substantially different stories depending on position and zoom level.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/1463434.1463458</identifier>
		<title type="sharef:primaryTitle">NewsStand: A New View on News</title>
		<identifier type="sharef:uri" resourceType="application/pdf">http://www.cs.umd.edu/~hjs/pubs/newsstand-acmgis2008.pdf</identifier>
	</reference>
	<reference name="acmgis2008" src="bibtex:proceedings" src-info="bibtex:line-15701" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>Walid G.</givenname>
				<surname>Aref</surname>
			</person>
			<person>
				<givenname>Mohamed F.</givenname>
				<surname>Mokbel</surname>
			</person>
			<person>
				<givenname>Markus</givenname>
				<surname>Schneider</surname>
			</person>
		</names>
		<date value="2008-11"/>
		<address type="sharef:placePublished">Irvine, California</address>
		<field type="bibtex:index">GIS 2008</field>
		<identifier type="sharef:isbn">978-1-60558-323-5</identifier>
		<publisher>ACM Press</publisher>
		<title type="sharef:primaryTitle">16th ACM SIGSPATIAL International Conference on Advances in Geographic Information Systems</title>
		<identifier type="sharef:uri" resourceType="text/html">http://www.informatik.uni-trier.de/~ley/db/conf/gis/gis2008.html</identifier>
	</reference>
	<reference name="san09" src="bibtex:inproceedings" src-info="bibtex:line-15718" type="sharef:inproceedings" crossref="acmgis2009">
		<names type="sharef:author">
			<person>
				<givenname>Jagan</givenname>
				<surname>Sankaranarayanan</surname>
			</person>
			<person>
				<givenname>Hanan</givenname>
				<surname>Samet</surname>
			</person>
			<person>
				<givenname>Benjamin E.</givenname>
				<surname>Teitler</surname>
			</person>
			<person>
				<givenname>Michael D.</givenname>
				<surname>Lieberman</surname>
			</person>
			<person>
				<givenname>Jon</givenname>
				<surname>Sperling</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Twitter is an electronic medium that allows a large user populace to communicate with each other simultaneously. Inherent to Twitter is an asymmetrical relationship between friends and followers that provides an interesting social network like structure among the users of Twitter. Twitter messages, called tweets, are restricted to 140 characters and thus are usually very focused. We investigate the use of Twitter to build a news processing system, called TwitterStand, from Twitter tweets. The idea is to capture tweets that correspond to late breaking news. The result is analogous to a distributed news wire service. The difference is that the identities of the contributors/reporters are not known in advance and there may be many of them. Furthermore, tweets are not sent according to a schedule: they occur as news is happening, and tend to be noisy while usually arriving at a high throughput rate. Some of the issues addressed include removing the noise, determining tweet clusters of interest bearing in mind that the methods must be online, and determining the relevant locations associated with the tweets.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/1653771.1653781</identifier>
		<pages>42-51</pages>
		<title type="sharef:primaryTitle">TwitterStand: News in Tweets</title>
	</reference>
	<reference name="yan09b" src="bibtex:inproceedings" src-info="bibtex:line-15727" type="sharef:inproceedings" crossref="acmgis2009">
		<names type="sharef:author">
			<person>
				<givenname>Lin</givenname>
				<surname>Yang</surname>
			</person>
			<person>
				<givenname>Xiaqing</givenname>
				<surname>Wu</surname>
			</person>
			<person>
				<givenname>Emil</givenname>
				<surname>Praun</surname>
			</person>
			<person>
				<givenname>Xiaoxu</givenname>
				<surname>Ma</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>We propose an automatic approach to tree detection from aerial imagery. First a pixel-level classifier is trained to assign a (tree, non-tree) label to each pixel in an aerial image. The pixel-level classification is then refined by a partitioning algorithm to a clean image segmentation of tree and non-tree regions. Based on the refined segmentation results, we adopt template matching followed by greedy selection to locate individual tree crowns. As training a pixel-level classifier requires manual generation of ground-truth tree masks, we propose methods for automatic model and training data selection to minimize the manual work and scale the algorithm to the entire globe. We test the algorithm on thousands of production aerial images across different countries. We demonstrate high-quality tree detection results as well as good scalability of the proposed approach.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/1653771.1653792</identifier>
		<pages>131-137</pages>
		<title type="sharef:primaryTitle">Tree Detection from Aerial Imagery</title>
	</reference>
	<reference name="acmgis2009" src="bibtex:proceedings" src-info="bibtex:line-15736" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>Ouri</givenname>
				<surname>Wolfson</surname>
			</person>
			<person>
				<givenname>Divyakant</givenname>
				<surname>Agrawal</surname>
			</person>
			<person>
				<givenname>Chang-Tien</givenname>
				<surname>Lu</surname>
			</person>
		</names>
		<date value="2009-11"/>
		<address type="sharef:placePublished">Seattle, Washington</address>
		<field type="bibtex:index">GIS 2009</field>
		<identifier type="sharef:isbn">978-1-60558-649-6</identifier>
		<publisher>ACM Press</publisher>
		<title type="sharef:primaryTitle">17th ACM SIGSPATIAL International Symposium on Advances in Geographic Information Systems</title>
		<identifier type="sharef:uri" resourceType="text/html">http://www.informatik.uni-trier.de/~ley/db/conf/gis/gis2009.html</identifier>
	</reference>
	<reference name="bie91" src="bibtex:inproceedings" src-info="bibtex:line-15753" type="sharef:inproceedings" crossref="uist91">
		<names type="sharef:author">
			<person>
				<givenname>Eric A.</givenname>
				<surname>Bier</surname>
			</person>
			<person>
				<givenname>Steven</givenname>
				<surname>Freeman</surname>
			</person>
		</names>
		<field type="bibtex:index">MMM</field>
		<pages>79-86</pages>
		<title type="sharef:primaryTitle">MMM: A User Interface Architecture for Shared Editors on a Single Screen</title>
	</reference>
	<reference name="pat91" src="bibtex:inproceedings" src-info="bibtex:line-15761" type="sharef:inproceedings" crossref="uist91">
		<names type="sharef:author">
			<person>
				<givenname>John F.</givenname>
				<surname>Patterson</surname>
			</person>
		</names>
		<field type="bibtex:index">Rendezvous</field>
		<pages>87-94</pages>
		<title type="sharef:primaryTitle">Comparing the Programming Demands of Single-User and Multi-User Applications</title>
	</reference>
	<reference name="uist91" src="bibtex:proceedings" src-info="bibtex:line-15769" type="sharef:proceedings">
		<date value="1991-11"/>
		<address type="sharef:placePublished">Hilton Head, South Carolina</address>
		<field type="bibtex:index">UIST '91</field>
		<title type="sharef:primaryTitle">Fourth ACM Symposium on User Interface Software and Technology</title>
	</reference>
	<reference name="dru06" src="bibtex:inproceedings" src-info="bibtex:line-15782" type="sharef:inproceedings" crossref="uist2006">
		<names type="sharef:author">
			<person>
				<givenname>Steve</givenname>
				<surname>Drucker</surname>
			</person>
			<person>
				<givenname>Georg</givenname>
				<surname>Petschnigg</surname>
			</person>
			<person>
				<givenname>Maneesh</givenname>
				<surname>Agrawala</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Despite the ubiquity of slide presentations, managing multiple presentations remains a challenge. Understanding how multiple versions of a presentation are related to one another, assembling new presentations from existing presentations, and collaborating to create and edit presentations are difficult tasks. In this paper, we explore techniques for comparing and managing multiple slide presentations. We propose a general comparison framework for computing similarities and differences between slides. Based on this framework we develop an interactive tool for visually comparing multiple presentations. The interactive visualization facilitates understanding how presentations have evolved over time. We show how the interactive tool can be used to assemble new presentations from a collection of older ones and to merge changes from multiple presentation authors.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/1166253.1166263</identifier>
		<pages>47-56</pages>
		<title type="sharef:primaryTitle">Comparing and Managing Multiple Versions of Slide Presentations</title>
		<identifier type="sharef:uri">http://vis.berkeley.edu/papers/pptdiff/</identifier>
	</reference>
	<reference name="uist2006" src="bibtex:proceedings" src-info="bibtex:line-15792" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>Pierre</givenname>
				<surname>Wellner</surname>
			</person>
			<person>
				<givenname>Ken</givenname>
				<surname>Hinckley</surname>
			</person>
		</names>
		<date value="2006-10"/>
		<address type="sharef:placePublished">Montreux, Switzerland</address>
		<field type="bibtex:index">UIST 2006</field>
		<identifier type="sharef:isbn">1-59593-313-1</identifier>
		<title type="sharef:primaryTitle">19th Annual ACM Symposium on User Interface Software and Technology</title>
		<identifier type="sharef:uri">http://www.acm.org/uist/uist2006/</identifier>
		<identifier type="sharef:uri" resourceType="text/html">http://www.sigmod.org/dblp/db/conf/uist/uist2006.html</identifier>
	</reference>
	<reference name="bro90" src="bibtex:inproceedings" src-info="bibtex:line-15809" type="sharef:inproceedings" crossref="cscw90">
		<names type="sharef:author">
			<person>
				<givenname>L.</givenname>
				<surname>Brothers</surname>
			</person>
			<person>
				<givenname>V.</givenname>
				<surname>Sembugamoorthy</surname>
			</person>
			<person>
				<givenname>M.</givenname>
				<surname>Muller</surname>
			</person>
		</names>
		<field type="bibtex:index">ICICLE, collaborative editing</field>
		<pages>169-181</pages>
		<title type="sharef:primaryTitle">ICICLE: Groupware for Code Inspection</title>
	</reference>
	<reference name="neu90" src="bibtex:inproceedings" src-info="bibtex:line-15817" type="sharef:inproceedings" crossref="cscw90">
		<names type="sharef:author">
			<person>
				<givenname>Christine M.</givenname>
				<surname>Neuwirth</surname>
			</person>
			<person>
				<givenname>David S.</givenname>
				<surname>Kaufer</surname>
			</person>
			<person>
				<givenname>Ravinder</givenname>
				<surname>Chandhok</surname>
			</person>
			<person>
				<givenname>James H.</givenname>
				<surname>Morris</surname>
			</person>
		</names>
		<field type="bibtex:index">PREP, collaborative editing</field>
		<pages>183-195</pages>
		<title type="sharef:primaryTitle">Issues in the Design of Computer Support for Co-authoring and Commenting</title>
	</reference>
	<reference name="pat90" src="bibtex:inproceedings" src-info="bibtex:line-15825" type="sharef:inproceedings" crossref="cscw90">
		<names type="sharef:author">
			<person>
				<givenname>John F.</givenname>
				<surname>Patterson</surname>
			</person>
			<person>
				<givenname>Ralph D.</givenname>
				<surname>Hill</surname>
			</person>
			<person>
				<givenname>Steven L.</givenname>
				<surname>Rohall</surname>
			</person>
		</names>
		<field type="bibtex:index">Rendezvous</field>
		<pages>317-328</pages>
		<title type="sharef:primaryTitle">Rendezvous: An Architecture for Synchronous Multi-User Applications</title>
	</reference>
	<reference name="cro90" src="bibtex:inproceedings" src-info="bibtex:line-15833" type="sharef:inproceedings" crossref="cscw90">
		<names type="sharef:author">
			<person>
				<givenname>Terrence</givenname>
				<surname>Crowley</surname>
			</person>
			<person>
				<givenname>Paul</givenname>
				<surname>Milazzo</surname>
			</person>
			<person>
				<givenname>Ellie</givenname>
				<surname>Baker</surname>
			</person>
			<person>
				<givenname>Harry</givenname>
				<surname>Forsdick</surname>
			</person>
			<person>
				<givenname>Raymond</givenname>
				<surname>Tomlinson</surname>
			</person>
		</names>
		<field type="bibtex:index">MMConf</field>
		<pages>329-342</pages>
		<title type="sharef:primaryTitle">MMConf: An Infrastructure for Building Shared Multimedia Applications</title>
	</reference>
	<reference name="kni90" src="bibtex:inproceedings" src-info="bibtex:line-15841" type="sharef:inproceedings" crossref="cscw90">
		<names type="sharef:author">
			<person>
				<givenname>Michael J.</givenname>
				<surname>Knister</surname>
			</person>
			<person>
				<givenname>Atul</givenname>
				<surname>Prakash</surname>
			</person>
		</names>
		<field type="bibtex:index">groupware, collaboration technology, group editors, distributed systems, DistEdit, collaborative editing</field>
		<pages>343-355</pages>
		<title type="sharef:primaryTitle">DistEdit: A Distributed Toolkit for Supporting Multiple Group Editors</title>
	</reference>
	<reference name="cscw90" src="bibtex:proceedings" src-info="bibtex:line-15849" type="sharef:proceedings">
		<date value="1990-10"/>
		<address type="sharef:placePublished">Los Angeles, California</address>
		<field type="bibtex:index">CSCW '90</field>
		<identifier type="sharef:isbn">0897914023</identifier>
		<organization>ACM</organization>
		<title type="sharef:primaryTitle">1990 Conference on Computer-Supported Cooperative Work</title>
		<field type="bibtex:topic">cscw[0.8]</field>
	</reference>
	<reference name="gre91" src="bibtex:inproceedings" src-info="bibtex:line-15865" type="sharef:inproceedings" crossref="ecscw91">
		<names type="sharef:author">
			<person>
				<givenname>Saul</givenname>
				<surname>Greenberg</surname>
			</person>
		</names>
		<pages>17-31</pages>
		<title type="sharef:primaryTitle">Personalizable groupware: Accommodating individual roles and group differences</title>
	</reference>
	<reference name="dep91b" src="bibtex:inproceedings" src-info="bibtex:line-15872" type="sharef:inproceedings" crossref="ecscw91">
		<names type="sharef:author">
			<person>
				<givenname>Flavio</givenname>
				<surname>DePaoli</surname>
			</person>
			<person>
				<givenname>Francesco</givenname>
				<surname>Tisato</surname>
			</person>
		</names>
		<field type="bibtex:index">Coordinator</field>
		<pages>203-217</pages>
		<title type="sharef:primaryTitle">A Model for Real-Time Co-operation</title>
	</reference>
	<reference name="ecscw91" src="bibtex:proceedings" src-info="bibtex:line-15880" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>Liam J.</givenname>
				<surname>Bannon</surname>
			</person>
			<person>
				<givenname>Mike</givenname>
				<surname>Robinson</surname>
			</person>
			<person>
				<givenname>Kjeld</givenname>
				<surname>Schmidt</surname>
			</person>
		</names>
		<date value="1991-09"/>
		<address type="sharef:placePublished">Amsterdam, Netherlands</address>
		<field type="bibtex:index">ECSCW '91</field>
		<identifier type="sharef:isbn">0792314395</identifier>
		<publisher>Kluwer Academic Publishers</publisher>
		<title type="sharef:primaryTitle">Second European Conference on Computer-Supported Cooperative Work</title>
		<field type="bibtex:topic">cscw[0.8]</field>
	</reference>
	<reference name="ros92b" src="bibtex:inproceedings" src-info="bibtex:line-15897" type="sharef:inproceedings" crossref="cscw92">
		<names type="sharef:author">
			<person>
				<givenname>Mark</givenname>
				<surname>Roseman</surname>
			</person>
			<person>
				<givenname>Saul</givenname>
				<surname>Greenberg</surname>
			</person>
		</names>
		<field type="bibtex:index">GroupKit</field>
		<pages>43-50</pages>
		<title type="sharef:primaryTitle">GroupKit: A Groupware Toolkit for Building Real-Time Conferencing Applications</title>
	</reference>
	<reference name="ols92" src="bibtex:inproceedings" src-info="bibtex:line-15905" type="sharef:inproceedings" crossref="cscw92">
		<names type="sharef:author">
			<person>
				<givenname>Judith S.</givenname>
				<surname>Olson</surname>
			</person>
			<person>
				<givenname>Gary M.</givenname>
				<surname>Olson</surname>
			</person>
			<person>
				<givenname>Marianne</givenname>
				<surname>Storrøsten</surname>
			</person>
			<person>
				<givenname>Mark</givenname>
				<surname>Carter</surname>
			</person>
		</names>
		<field type="bibtex:index">collaborative editing, ShrEdit</field>
		<pages>91-98</pages>
		<title type="sharef:primaryTitle">How a Group-Editor Changes the Character of a Design Meeting as well as its Outcome</title>
	</reference>
	<reference name="mcl92" src="bibtex:inproceedings" src-info="bibtex:line-15913" type="sharef:inproceedings" crossref="cscw92">
		<names type="sharef:author">
			<person>
				<givenname>Charles</givenname>
				<surname>McLaughlin Hymes</surname>
			</person>
			<person>
				<givenname>Gary M.</givenname>
				<surname>Olson</surname>
			</person>
		</names>
		<field type="bibtex:index">collaborative editing, ShrEdit</field>
		<pages>99-106</pages>
		<title type="sharef:primaryTitle">Unblocking Brainstorming Through the Use of a Simple Group Editor</title>
	</reference>
	<reference name="dou92" src="bibtex:inproceedings" src-info="bibtex:line-15921" type="sharef:inproceedings" crossref="cscw92">
		<names type="sharef:author">
			<person>
				<givenname>Paul</givenname>
				<surname>Dourish</surname>
			</person>
			<person>
				<givenname>Victoria</givenname>
				<surname>Bellotti</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Awareness of individual and group activities is critical to successful collaboration and is commonly supported in CSCW systems by active, information generation mechanisms separate from the shared workspace. These mechanisms penalise information providers, presuppose relevance to the recipient, and make access difficult, We discuss a study of shared editor use which suggests that awareness information provided and exploited passively through the shared workspace, allows users to move smoothly between close and loose collaboration, and to assign and coordinate work dynamically. Passive awareness mechanisms promise effective support for collaboration requiring this sort of behaviour, whilst avoiding problems with active approaches.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/143457.143468</identifier>
		<field type="bibtex:index">Quilt, PREP, GROVE, ShrEdit, awareness, coordination</field>
		<pages>107-114</pages>
		<title type="sharef:primaryTitle">Awareness and Coordination in Shared Workspaces</title>
		<identifier type="sharef:uri">http://portal.acm.org/citation.cfm?id=143468</identifier>
	</reference>
	<reference name="haa92" src="bibtex:inproceedings" src-info="bibtex:line-15932" type="sharef:inproceedings" crossref="cscw92">
		<names type="sharef:author">
			<person>
				<givenname>Jörg M.</givenname>
				<surname>Haake</surname>
			</person>
			<person>
				<givenname>Brian</givenname>
				<surname>Wilson</surname>
			</person>
		</names>
		<field type="bibtex:index">collaborative editing, SEPIA, HyperBase</field>
		<pages>138-146</pages>
		<title type="sharef:primaryTitle">Supporting Collaborative Writing of Hyperdocuments in SEPIA</title>
	</reference>
	<reference name="neu92" src="bibtex:inproceedings" src-info="bibtex:line-15940" type="sharef:inproceedings" crossref="cscw92">
		<names type="sharef:author">
			<person>
				<givenname>Christine M.</givenname>
				<surname>Neuwirth</surname>
			</person>
			<person>
				<givenname>Ravinder</givenname>
				<surname>Chandhok</surname>
			</person>
			<person>
				<givenname>David S.</givenname>
				<surname>Kaufer</surname>
			</person>
			<person>
				<givenname>Paul</givenname>
				<surname>Erion</surname>
			</person>
			<person>
				<givenname>James H.</givenname>
				<surname>Morris</surname>
			</person>
			<person>
				<givenname>Dale</givenname>
				<surname>Miller</surname>
			</person>
		</names>
		<field type="bibtex:index">collaborative editing, PREP, flexible diff</field>
		<pages>147-154</pages>
		<title type="sharef:primaryTitle">Flexible Diff-ing in a Collaborative Writing System</title>
	</reference>
	<reference name="cscw92" src="bibtex:proceedings" src-info="bibtex:line-15948" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>John</givenname>
				<surname>Turner</surname>
			</person>
			<person>
				<givenname>Robert</givenname>
				<surname>Kraut</surname>
			</person>
		</names>
		<date value="1992-11"/>
		<address type="sharef:placePublished">Toronto, Canada</address>
		<field type="bibtex:index">CSCW '92</field>
		<identifier type="sharef:isbn">0897915429</identifier>
		<organization>ACM</organization>
		<title type="sharef:primaryTitle">1992 Conference on Computer-Supported Cooperative Work</title>
		<field type="bibtex:topic">cscw[0.8]</field>
	</reference>
	<reference name="bel93" src="bibtex:inproceedings" src-info="bibtex:line-15965" type="sharef:inproceedings" crossref="ecscw93">
		<names type="sharef:author">
			<person>
				<givenname>Victoria</givenname>
				<surname>Bellotti</surname>
			</person>
			<person>
				<givenname>Abigail J.</givenname>
				<surname>Sellen</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Current developments in information technology are leading to increasing capture and storage of information about people and their activities. This raises serious issues about the preservation of privacy. In this paper we examine why these issues are particularly important in the introduction of ubiquitous computing technology into the working environment. Certain problems with privacy are closely related to the ways in which the technology attenuates natural mechanisms of feedback and control over information released. We describe a framework for design for privacy in ubiquitous computing environments and conclude with an example of its application.</p>
			</richtext>
		</abstract>
		<pages>77-92</pages>
		<title type="sharef:primaryTitle">Design for Privacy in Ubiquitous Computing Environments</title>
		<identifier type="sharef:uri" resourceType="application/pdf">http://research.microsoft.com/en-us/um/people/asellen/publications/design%20for%20privacy%2093.pdf</identifier>
	</reference>
	<reference name="pri93" src="bibtex:inproceedings" src-info="bibtex:line-15974" type="sharef:inproceedings" crossref="ecscw93">
		<names type="sharef:author">
			<person>
				<givenname>Wolfgang</givenname>
				<surname>Prinz</surname>
			</person>
		</names>
		<field type="bibtex:index">TOSCA</field>
		<pages>139-154</pages>
		<title type="sharef:primaryTitle">TOSCA — Provinding organisational information to CSCW Applications</title>
	</reference>
	<reference name="pat93" src="bibtex:inproceedings" src-info="bibtex:line-15982" type="sharef:inproceedings" crossref="ecscw93">
		<names type="sharef:author">
			<person>
				<givenname>Dorab</givenname>
				<surname>Patel</surname>
			</person>
			<person>
				<givenname>Scott D.</givenname>
				<surname>Kalter</surname>
			</person>
		</names>
		<field type="bibtex:index">communication channels</field>
		<pages>203-218</pages>
		<title type="sharef:primaryTitle">Low overhead, loosely coupled communication channels in collaboration</title>
	</reference>
	<reference name="min93" src="bibtex:inproceedings" src-info="bibtex:line-15990" type="sharef:inproceedings" crossref="ecscw93">
		<names type="sharef:author">
			<person>
				<givenname>S.</givenname>
				<surname>Minör</surname>
			</person>
			<person>
				<givenname>B.</givenname>
				<surname>Magnusson</surname>
			</person>
		</names>
		<field type="bibtex:index">collaborative editing</field>
		<pages>219-231</pages>
		<title type="sharef:primaryTitle">A Model for Semi-(a)Synchronous Collaborative Editing</title>
	</reference>
	<reference name="bri93" src="bibtex:inproceedings" src-info="bibtex:line-15998" type="sharef:inproceedings" crossref="ecscw93">
		<names type="sharef:author">
			<person>
				<givenname>Tom</givenname>
				<surname>Brinck</surname>
			</person>
			<person>
				<givenname>Ralph D.</givenname>
				<surname>Hill</surname>
			</person>
		</names>
		<field type="bibtex:index">Rendezvous</field>
		<pages>311-324</pages>
		<title type="sharef:primaryTitle">Building Shared Graphical Editors Using the Abstraction-Link-View Architecture</title>
	</reference>
	<reference name="ecscw93" src="bibtex:proceedings" src-info="bibtex:line-16006" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>Giorgio</givenname>
				<surname link="de">Michelis</surname>
			</person>
			<person>
				<givenname>Carla</givenname>
				<surname>Simone</surname>
			</person>
			<person>
				<givenname>Kjeld</givenname>
				<surname>Schmidt</surname>
			</person>
		</names>
		<date value="1993-09"/>
		<address type="sharef:placePublished">Milano, Italy</address>
		<field type="bibtex:index">ECSCW '93</field>
		<identifier type="sharef:isbn">0792324471</identifier>
		<publisher>Kluwer Academic Publishers</publisher>
		<title type="sharef:primaryTitle">Third European Conference on Computer-Supported Cooperative Work</title>
		<field type="bibtex:topic">cscw[0.8]</field>
	</reference>
	<reference name="edw96" src="bibtex:inproceedings" src-info="bibtex:line-16023" type="sharef:inproceedings" crossref="cscw96">
		<names type="sharef:author">
			<person>
				<givenname>W. Keith</givenname>
				<surname>Edwards</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Collaborative systems provide a rich but potentially chaotic environment for their users. This paper presents a system that allows users to control collaboration by enacting policies that serve as general guidelines to restrict and define the behavior of the system in reaction to the state of the world. Policies are described in terms of access control rights on data objects, and are assigned to groups of users called roles. Roles represent not only statically-defined collections of users, but also dynamic descriptions of users that are evaluated as applications are run. This run-time aspect of roles allows them to react flexibly to the dynamism inherent in collaboration. We present a specification language for describing roles and policies, as well as a number of common "real-world" policies that can be applied to collaborative settings.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/240080.240175</identifier>
		<pages>11-20</pages>
		<title type="sharef:primaryTitle">Policies and Roles in Collaborative Applications</title>
		<identifier type="sharef:uri">http://portal.acm.org/citation.cfm?doid=240080.240175</identifier>
	</reference>
	<reference name="har96" src="bibtex:inproceedings" src-info="bibtex:line-16033" type="sharef:inproceedings" crossref="cscw96">
		<names type="sharef:author">
			<person>
				<givenname>Steve</givenname>
				<surname>Harrison</surname>
			</person>
			<person>
				<givenname>Paul</givenname>
				<surname>Dourish</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Many collaborative and communicative environments use notions of "space" and spatial organisation to facilitate and structure interaction. We argue that a focus on spatial models is misplaced. Drawing on understandings from architecture and urban design, as well as from our own research findings, we highlight the critical distinction between "space" and "place". While designers use spatial models to support interaction, we show how it is actually a notion of "place" which frames interactive behaviour. This leads us to re-evaluate spatial systems, and discuss how "place", rather than "space", can support CSCW design.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/240080.240193</identifier>
		<pages>67-76</pages>
		<title type="sharef:primaryTitle">Re-Place-ing Space: The Roles of Place and Space in Collaborative Systems</title>
		<identifier type="sharef:uri" resourceType="text/html">http://www.ics.uci.edu/~jpd/publications/place-paper.html</identifier>
	</reference>
	<reference name="cscw96" src="bibtex:proceedings" src-info="bibtex:line-16043" type="sharef:proceedings">
		<date value="1996-11"/>
		<address type="sharef:placePublished">Boston, Massachusetts</address>
		<field type="bibtex:index">CSCW 1996</field>
		<identifier type="sharef:isbn">0-89791-765-0</identifier>
		<publisher>ACM Press</publisher>
		<title type="sharef:primaryTitle">1996 ACM Conference on Computer Supported Cooperative Work</title>
		<field type="bibtex:topic">cscw[0.8]</field>
		<identifier type="sharef:uri" resourceType="text/html">http://www.informatik.uni-trier.de/~ley/db/conf/cscw/cscw1996.html</identifier>
	</reference>
	<reference name="cad00" src="bibtex:inproceedings" src-info="bibtex:line-16060" type="sharef:inproceedings" crossref="cscw2000">
		<names type="sharef:author">
			<person>
				<givenname>J. J.</givenname>
				<surname>Cadiz</surname>
			</person>
			<person>
				<givenname>Anoop</givenname>
				<surname>Gupta</surname>
			</person>
			<person>
				<givenname>Jonathan</givenname>
				<surname>Grudin</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Digital web-accessible annotations are a compelling medium for personal comments and shared discussions around documents. Only recently supported by widely used products, "in-context" digital annotation is a relatively unexamined phenomenon. This paper presents a case study of annotations created by members of a large development team using Microsoft Office 2000 — approximately 450 people created 9,000 shared annotations on about 1,250 documents over 10 months. We present quantitative data on use, supported by interviews with users, identifying strengths and weaknesses of the existing capabilities and possibilities for improvement.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/358916.359002</identifier>
		<pages>309-318</pages>
		<title type="sharef:primaryTitle">Using Web Annotations for Asynchronous Collaboration Around Documents</title>
		<field type="bibtex:topic">webdiscussions[0.9]</field>
		<identifier type="sharef:uri">http://portal.acm.org/citation.cfm?id=359002</identifier>
	</reference>
	<reference name="cscw2000" src="bibtex:proceedings" src-info="bibtex:line-16071" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>David G.</givenname>
				<surname>Durand</surname>
			</person>
		</names>
		<date value="2000-12"/>
		<address type="sharef:placePublished">Philadelphia, Pennsylvania</address>
		<field type="bibtex:index">CSCW 2000</field>
		<identifier type="sharef:isbn">1-58113-222-0</identifier>
		<publisher>ACM Press</publisher>
		<title type="sharef:primaryTitle">2000 ACM Conference on Computer Supported Cooperative Work</title>
		<field type="bibtex:topic">cscw[0.8]</field>
	</reference>
	<reference name="lau02" src="bibtex:inproceedings" src-info="bibtex:line-16088" type="sharef:inproceedings" crossref="cscw2002">
		<names type="sharef:author">
			<person>
				<givenname>Yann</givenname>
				<surname>Laurillau</surname>
			</person>
			<person>
				<givenname>Laurence</givenname>
				<surname>Nigay</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>In this paper we present the Clover architectural model, a new conceptual architectural model for groupware. Our model results from the combination of the layer approach of Dewan's generic architecture with the functional decomposition of the Clover design model. The Clover design model defines three classes of services that a groupware application may support, namely, production, communication and coordination services. The three classes of services can be found in each functional layer of our model. Our model is illustrated with a working system, the CoVitesse system, its software being organized according to our Clover architectural model.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/587078.587112</identifier>
		<pages>236-245</pages>
		<title type="sharef:primaryTitle">Clover Architecture for Groupware</title>
		<field type="bibtex:topic">clover[0.9]</field>
		<identifier type="sharef:uri">http://portal.acm.org/citation.cfm?doid=587112</identifier>
	</reference>
	<reference name="cscw2002" src="bibtex:proceedings" src-info="bibtex:line-16099" type="sharef:proceedings">
		<date value="2002-11"/>
		<address type="sharef:placePublished">New Orleans, Louisiana</address>
		<field type="bibtex:index">CSCW 2002</field>
		<identifier type="sharef:isbn">1-58113-560-2</identifier>
		<publisher>ACM Press</publisher>
		<title type="sharef:primaryTitle">2002 ACM Conference on Computer Supported Cooperative Work</title>
		<field type="bibtex:topic">cscw[0.8]</field>
	</reference>
	<reference name="ber92" src="bibtex:inproceedings" src-info="bibtex:line-16115" type="sharef:inproceedings" crossref="jenc92">
		<names type="sharef:author">
			<person>
				<givenname>Tim</givenname>
				<surname>Berners-Lee</surname>
			</person>
			<person>
				<givenname>Robert</givenname>
				<surname>Cailliau</surname>
			</person>
			<person>
				<givenname>Jean-François</givenname>
				<surname>Groff</surname>
			</person>
		</names>
		<field type="bibtex:index">WWW</field>
		<title type="sharef:primaryTitle">The World Wide Web</title>
	</reference>
	<reference name="jenc92" src="bibtex:proceedings" src-info="bibtex:line-16122" type="sharef:proceedings">
		<date value="1992-05"/>
		<address type="sharef:placePublished">Innsbruck, Austria</address>
		<field type="bibtex:index">JENC3</field>
		<title type="sharef:primaryTitle">3rd Joint European Networking Conference</title>
	</reference>
	<reference name="wil93" src="bibtex:inproceedings" src-info="bibtex:line-16135" type="sharef:inproceedings" crossref="mcat93">
		<names type="sharef:author">
			<person>
				<givenname>Erik</givenname>
				<surname>Wilde</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Joint editing as opposed to "normal" editing is an activity carried out by several people simultaneously. It raises the problem of coordinating write access to a document. The approach described in this paper uses an editing model of reserved regions and a client/server architecture. Any region of a document may be selected and reserved (provided that it is not reserved already) and may then be changed by the owner. Other users can only read it. The software basis of the editor is the Andrew Toolkit. This allows the use of arbitrary media types within the document.</p>
			</richtext>
		</abstract>
		<field type="bibtex:index">MultimETH, collaborative editing</field>
		<pages>198-209</pages>
		<title type="sharef:primaryTitle">Multimedia Joint Editing Based on Reservations</title>
		<identifier type="sharef:uri">http://dret.net/netdret/publications#wil93</identifier>
	</reference>
	<reference name="mcat93" src="bibtex:proceedings" src-info="bibtex:line-16145" type="sharef:proceedings">
		<date value="1993-07"/>
		<address type="sharef:placePublished">Wollongong, Australia</address>
		<field type="bibtex:index">MCAT '93</field>
		<title type="sharef:primaryTitle">3rd Australian Multi-Media Communications, Applications and Technology Workshop</title>
	</reference>
	<reference name="hsn91" src="bibtex:proceedings" src-info="bibtex:line-16158" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>André</givenname>
				<surname>Danthine</surname>
			</person>
			<person>
				<givenname>Otto</givenname>
				<surname>Spaniol</surname>
			</person>
		</names>
		<date value="1991-03"/>
		<address type="sharef:placePublished">Berlin, Germany</address>
		<title type="sharef:primaryTitle">Third IFIP WG6.4 Conference on High Speed Networking</title>
	</reference>
	<reference name="leo92" src="bibtex:inproceedings" src-info="bibtex:line-16171" type="sharef:inproceedings" crossref="hsn92">
		<names type="sharef:author">
			<person>
				<givenname>Helmut</givenname>
				<surname>Leopold</surname>
			</person>
			<person>
				<givenname>Andrew T.</givenname>
				<surname>Campbell</surname>
			</person>
			<person>
				<givenname>David</givenname>
				<surname>Hutchison</surname>
			</person>
			<person>
				<givenname>Nicolaus</givenname>
				<surname>Singer</surname>
			</person>
		</names>
		<field type="bibtex:index">QoS-A, QoS, multimedia</field>
		<pages>169-182</pages>
		<title type="sharef:primaryTitle">Towards an Integrated Quality of Service Architecture (QoS-A) for Distributed Multimedia Communications</title>
	</reference>
	<reference name="der92" src="bibtex:inproceedings" src-info="bibtex:line-16179" type="sharef:inproceedings" crossref="hsn92">
		<names type="sharef:author">
			<person>
				<givenname>Gabriel</givenname>
				<surname>Dermler</surname>
			</person>
			<person>
				<givenname>Konrad</givenname>
				<surname>Froitzheim</surname>
			</person>
		</names>
		<field type="bibtex:index">JVTOS, CIO</field>
		<pages>183-197</pages>
		<title type="sharef:primaryTitle">JVTOS — A Reference Model for a New Multimedia Service</title>
	</reference>
	<reference name="hsn92" src="bibtex:proceedings" src-info="bibtex:line-16187" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>André</givenname>
				<surname>Danthine</surname>
			</person>
			<person>
				<givenname>Otto</givenname>
				<surname>Spaniol</surname>
			</person>
		</names>
		<date value="1992-12"/>
		<address type="sharef:placePublished">Liège, Belgium</address>
		<identifier type="sharef:isbn">0444814817</identifier>
		<publisher>Elsevier</publisher>
		<title type="sharef:seriesTitle">IFIP Transactions</title>
		<title type="sharef:primaryTitle">IFIP TC6/WG6.4 Fourth Conference on High Speed Networking</title>
		<volume>C-14</volume>
	</reference>
	<reference name="how04" src="bibtex:inproceedings" src-info="bibtex:line-16204" type="sharef:inproceedings" crossref="ccip04">
		<names type="sharef:author">
			<person>
				<givenname>James</givenname>
				<surname>Howison</surname>
			</person>
			<person>
				<givenname>Abby</givenname>
				<surname>Goodrum</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>This paper considers the deceptively simple question: Why can't downloaded academic papers be managed in the simple and effective manner in which digital music files are managed? We make the case that the answer is different treatments of metadata. Two key differences are identified: Firstly, digital music metadata is standardized and moves with the content file, while academic metadata is not and does not. Secondly digital music metadata lookup services are collaborative and automate the movement from a digital file to the appropriate metadata, while academic metadata services do not. To understand why these differences exist we examine the divergent evolution of metadata standards for digital music and academic papers. It is observed that the processes differ in interesting ways according to their intent. Specifically music metadata was developed primarily for personal file management, while the focus of academic metadata has been on information retrieval. We argue that lessons from MP3 metadata can assist individual academics facing their growing personal document management challenges. Our focus therefore is not on metadata for the academic publishing industry or institutional resource sharing, it is limited to the personal libraries growing on our hard-drives. This bottom-up approach to document management combined with p2p distribution radically altered the music landscape. Might such an approach have a similar impact on academic publishing? This paper outlines plans for improving the personal management of academic papers — doing academic metadata and file management the MP3 way — and considers the likelihood of success.</p>
			</richtext>
		</abstract>
		<title type="sharef:primaryTitle">Why can't I manage Academic Papers like MP3s? The Evolution and Intent of Metadata Standards</title>
		<identifier type="sharef:uri" resourceType="application/pdf">http://freelancepropaganda.com/archives/MP3vPDF.pdf</identifier>
	</reference>
	<reference name="ccip04" src="bibtex:proceedings" src-info="bibtex:line-16212" type="sharef:proceedings">
		<date value="2004-04"/>
		<address type="sharef:placePublished">College Park, Maryland</address>
		<title type="sharef:primaryTitle">2004 Colleges, Code and Intellectual Property Conference</title>
	</reference>
	<reference name="hen94" src="bibtex:inproceedings" src-info="bibtex:line-16224" type="sharef:inproceedings" crossref="hpn94">
		<names type="sharef:author">
			<person>
				<givenname>Lutz</givenname>
				<surname>Henckel</surname>
			</person>
		</names>
		<field type="bibtex:index">multimedia, multipeer, group management, CIO</field>
		<pages>167-186</pages>
		<title type="sharef:primaryTitle">Multipeer Transport Services for Multimedia Applications</title>
	</reference>
	<reference name="hpn94" src="bibtex:proceedings" src-info="bibtex:line-16232" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>Serge</givenname>
				<surname>Fdida</surname>
			</person>
		</names>
		<date value="1994-06"/>
		<address type="sharef:placePublished">Grenoble, France</address>
		<identifier type="sharef:isbn">044482023X</identifier>
		<publisher>Elsevier</publisher>
		<title type="sharef:seriesTitle">IFIP Transactions</title>
		<title type="sharef:primaryTitle">IFIP TC6/WG6.4 Fifth International Conference on High Performance Networking</title>
		<volume>C-26</volume>
	</reference>
	<reference name="pen90" src="bibtex:inproceedings" src-info="bibtex:line-16249" type="sharef:inproceedings" crossref="mui90">
		<names type="sharef:author">
			<person>
				<givenname>Mark O.</givenname>
				<surname>Pendergast</surname>
			</person>
		</names>
		<field type="bibtex:index">MULE, collaborative editing</field>
		<pages>195-206</pages>
		<title type="sharef:primaryTitle">Design and Implementation of a PC/LAN-Based Multi-User Text Editor</title>
	</reference>
	<reference name="lub90b" src="bibtex:inproceedings" src-info="bibtex:line-16257" type="sharef:inproceedings" crossref="mui90">
		<names type="sharef:author">
			<person>
				<givenname>Hannes P.</givenname>
				<surname>Lubich</surname>
			</person>
			<person>
				<givenname>Bernhard</givenname>
				<surname>Plattner</surname>
			</person>
		</names>
		<field type="bibtex:index">MultimETH</field>
		<pages>215-232</pages>
		<title type="sharef:primaryTitle">A Proposed Model and Functionality Definition for a Collaborative Editing and Conferencing System</title>
	</reference>
	<reference name="mui90" src="bibtex:proceedings" src-info="bibtex:line-16265" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>Simon J.</givenname>
				<surname>Gibbs</surname>
			</person>
			<person>
				<givenname>Alex A.</givenname>
				<surname>Verrijn-Stuart</surname>
			</person>
		</names>
		<date value="1990"/>
		<address type="sharef:placePublished">Heraklion, Greece</address>
		<identifier type="sharef:isbn">0444887601</identifier>
		<publisher>North-Holland</publisher>
		<title type="sharef:primaryTitle">IFIP WG8.4 Conference on Multi-User Interfaces and Applications</title>
	</reference>
	<reference name="odp91" src="bibtex:proceedings" src-info="bibtex:line-16279" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>Jan</givenname>
				<surname link="de">Meer</surname>
			</person>
			<person>
				<givenname>Volker</givenname>
				<surname>Heymer</surname>
			</person>
			<person>
				<givenname>Rudolf</givenname>
				<surname>Roth</surname>
			</person>
		</names>
		<date value="1991"/>
		<address type="sharef:placePublished">Berlin, Germany</address>
		<identifier type="sharef:isbn">0444893296</identifier>
		<publisher>North-Holland</publisher>
		<title type="sharef:primaryTitle">IFIP TC6/WG6.4 International Workshop on Open Distributed Processing</title>
	</reference>
	<reference name="bla93" src="bibtex:inproceedings" src-info="bibtex:line-16293" type="sharef:inproceedings" crossref="odp93">
		<names type="sharef:author">
			<person>
				<givenname>Gordon S.</givenname>
				<surname>Blair</surname>
			</person>
			<person>
				<givenname>Tom A.</givenname>
				<surname>Rodden</surname>
			</person>
		</names>
		<pages>127-140</pages>
		<title type="sharef:primaryTitle">The Challenges of CSCW for Open Distributed Processing</title>
		<field type="bibtex:topic">cscw[0.8] odp[0.8]</field>
	</reference>
	<reference name="bos93" src="bibtex:inproceedings" src-info="bibtex:line-16301" type="sharef:inproceedings" crossref="odp93">
		<names type="sharef:author">
			<person>
				<givenname>Pier Giorgio</givenname>
				<surname>Bosco</surname>
			</person>
			<person>
				<givenname>Giovanni</givenname>
				<surname>Martini</surname>
			</person>
			<person>
				<givenname>Corrado</givenname>
				<surname>Moiso</surname>
			</person>
		</names>
		<field type="bibtex:index">object-orientation, distributed processing, distributed platforms, ODIN, DCE, C++</field>
		<pages>205-216</pages>
		<title type="sharef:primaryTitle">A distributed object-oriented platform based on DCE and C++</title>
	</reference>
	<reference name="bei93" src="bibtex:inproceedings" src-info="bibtex:line-16309" type="sharef:inproceedings" crossref="odp93">
		<names type="sharef:author">
			<person>
				<givenname>A. D.</givenname>
				<surname>Beitz</surname>
			</person>
			<person>
				<givenname>P. W.</givenname>
				<surname>King</surname>
			</person>
			<person>
				<givenname>K. A.</givenname>
				<surname>Raymond</surname>
			</person>
		</names>
		<pages>217-231</pages>
		<title type="sharef:primaryTitle">Is DCE a Support Environment for ODP?</title>
		<field type="bibtex:topic">dce[0.8] odp[0.8]</field>
	</reference>
	<reference name="odp93" src="bibtex:proceedings" src-info="bibtex:line-16317" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>Jan</givenname>
				<surname link="de">Meer</surname>
			</person>
			<person>
				<givenname>Bernd</givenname>
				<surname>Mahr</surname>
			</person>
			<person>
				<givenname>Silke</givenname>
				<surname>Storp</surname>
			</person>
		</names>
		<date value="1993"/>
		<address type="sharef:placePublished">Berlin, Germany</address>
		<identifier type="sharef:isbn">0-444-81861-8</identifier>
		<publisher>North-Holland</publisher>
		<title type="sharef:primaryTitle">IFIP TC6/WG6.1 International Conference on Open Distributed Processing</title>
	</reference>
	<reference name="anu93" src="bibtex:inproceedings" src-info="bibtex:line-16331" type="sharef:inproceedings" crossref="acmmm93">
		<names type="sharef:author">
			<person>
				<givenname>Vinod</givenname>
				<surname>Anupam</surname>
			</person>
			<person>
				<givenname>Chandrajit L.</givenname>
				<surname>Bajaj</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>We address the issue of design of architectures and abstractions to implement multimedia scientific manipulation systems, and briefly describe a prototype CSCW infrastructure which we have used to implement a multi-user distributed and collaborative scientific manipulation environment on the multimedia desktop. Finally, we present example design systems to exhibit that multimedia interfaces, incorporating text, graphics, audio and video, greatly facilitate distributed and collaborative scientific design effort. SHASTRA is a distributed and collaborative geometric design and scientific manipulation environment. In this system we address the research and development of the next generation of scientific software environments where multiple users (say, a collaborative engineering design team) create, share, manipulate, analyze, simulate, and visualize complex three dimensional geometric designs over a distributed heterogeneous network of workstations and supercomputers.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/166266.168458</identifier>
		<pages>447-456</pages>
		<title type="sharef:primaryTitle">Collaborative Multimedia Scientific Design in SHASTRA</title>
	</reference>
	<reference name="alt93" src="bibtex:inproceedings" src-info="bibtex:line-16340" type="sharef:inproceedings" crossref="acmmm93">
		<names type="sharef:author">
			<person>
				<givenname>Michael</givenname>
				<surname>Altenhofen</surname>
			</person>
			<person>
				<givenname>Jürgen</givenname>
				<surname>Dittrich</surname>
			</person>
			<person>
				<givenname>Rainer</givenname>
				<surname>Hammerschmidt</surname>
			</person>
			<person>
				<givenname>Thomas</givenname>
				<surname>Käppner</surname>
			</person>
			<person>
				<givenname>Carsten</givenname>
				<surname>Kruschel</surname>
			</person>
			<person>
				<givenname>Ansgar</givenname>
				<surname>Kückes</surname>
			</person>
			<person>
				<givenname>Thomas</givenname>
				<surname>Steinig</surname>
			</person>
		</names>
		<field type="bibtex:index">BERKOM, MMT, MMM, MMC, multimedia</field>
		<pages>457-463</pages>
		<title type="sharef:primaryTitle">The BERKOM Multimedia Collaboration Service</title>
	</reference>
	<reference name="acmmm93" src="bibtex:proceedings" src-info="bibtex:line-16348" type="sharef:proceedings">
		<date value="1993"/>
		<address type="sharef:placePublished">Anaheim, California</address>
		<identifier type="sharef:isbn">0-89791-596-8</identifier>
		<publisher>ACM Press</publisher>
		<title type="sharef:primaryTitle">ACM Multimedia 93</title>
	</reference>
	<reference name="hwa07" src="bibtex:inproceedings" src-info="bibtex:line-16361" type="sharef:inproceedings" crossref="acmmm07">
		<names type="sharef:author">
			<person>
				<givenname>Amy</givenname>
				<surname>Hwang</surname>
			</person>
			<person>
				<givenname>Shane</givenname>
				<surname>Ahern</surname>
			</person>
			<person>
				<givenname>Simon</givenname>
				<surname>King</surname>
			</person>
			<person>
				<givenname>Mor</givenname>
				<surname>Naaman</surname>
			</person>
			<person>
				<givenname>Rahul</givenname>
				<surname>Nair</surname>
			</person>
			<person>
				<givenname>Jeannie Hui-I</givenname>
				<surname>Yang</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>What happens when you can access all the world's media, but the access is constrained by screen size, bandwidth, attention, and battery life? We present a novel mobile context-aware software prototype that enables access to images on the go. Our prototype utilizes the channel metaphor to give users contextual access to media of interest according to key dimensions: spatial, social, and topical. Our experimental prototype attempts to be playful and simple to use, yet provide powerful and comprehensive media access. A temporally-driven sorting scheme for media items allows quick and easy access to items of interest in any dimension. For ad-hoc tasks, we extend the application with keyword search to deliver the long tail of media and images. Elements of social interaction and communication around the photographs are built into the mobile application, to increase user engagement. The application utilizes Flickr.com as an image and social-network data source, but could easily be extended to support other websites and media formats.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/1291233.1291370</identifier>
		<pages>557-560</pages>
		<title type="sharef:primaryTitle">Zurfer: Mobile Multimedia Access in Spatial, Social and Topical Context</title>
	</reference>
	<reference name="ken07" src="bibtex:inproceedings" src-info="bibtex:line-16370" type="sharef:inproceedings" crossref="acmmm07">
		<names type="sharef:author">
			<person>
				<givenname>Lyndon</givenname>
				<surname>Kennedy</surname>
			</person>
			<person>
				<givenname>Mor</givenname>
				<surname>Naaman</surname>
			</person>
			<person>
				<givenname>Shane</givenname>
				<surname>Ahern</surname>
			</person>
			<person>
				<givenname>Rahul</givenname>
				<surname>Nair</surname>
			</person>
			<person>
				<givenname>Tye</givenname>
				<surname>Rattenbury</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>The advent of media-sharing sites like Flickr and YouTube has drastically increased the volume of community-contributed multimedia resources available on the web. These collections have a previously unimagined depth and breadth, and have generated new opportunities — and new challenges — to multimedia research. How do we analyze, understand and extract patterns from these new collections? How can we use these unstructured, unrestricted community contributions of media (and annotation) to generate "knowledge". As a test case, we study Flickr — a popular photo sharing website. Flickr supports photo, time and location metadata, as well as a light-weight annotation model. We extract information from this dataset using two different approaches. First, we employ a location-driven approach to generate aggregate knowledge in the form of "representative tags" for arbitrary areas in the world. Second, we use a tag-driven approach to automatically extract place and event semantics for Flickr tags, based on each tag's metadata patterns. With the patterns we extract from tags and metadata, vision algorithms can be employed with greater precision. In particular, we demonstrate a location-tag-vision-based approach to retrieving images of geography-related landmarks and features from the Flickr dataset. The results suggest that community-contributed media and annotation can enhance and improve our access to multimedia resources — and our understanding of the world.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/1291233.1291384</identifier>
		<pages>631-640</pages>
		<title type="sharef:primaryTitle">How Flickr Helps us Make Sense of the World: Context and Content in Community-Contributed Media Collections</title>
		<identifier type="sharef:uri" resourceType="application/pdf">http://infolab.stanford.edu/~mor/research/kennedyMM07.pdf</identifier>
	</reference>
	<reference name="acmmm07" src="bibtex:proceedings" src-info="bibtex:line-16380" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>Rainer</givenname>
				<surname>Lienhart</surname>
			</person>
			<person>
				<givenname>Anand R.</givenname>
				<surname>Prasad</surname>
			</person>
			<person>
				<givenname>Alan</givenname>
				<surname>Hanjalic</surname>
			</person>
			<person>
				<givenname>Sunghyun</givenname>
				<surname>Choi</surname>
			</person>
			<person>
				<givenname>Brian P.</givenname>
				<surname>Bailey</surname>
			</person>
			<person>
				<givenname>Nicu</givenname>
				<surname>Sebe</surname>
			</person>
		</names>
		<date value="2007"/>
		<address type="sharef:placePublished">Augsburg, Germany</address>
		<identifier type="sharef:isbn">978-1-59593-702-5</identifier>
		<publisher>ACM Press</publisher>
		<title type="sharef:primaryTitle">ACM Multimedia 2007</title>
		<identifier type="sharef:uri" resourceType="text/html">http://www.informatik.uni-trier.de/~ley/db/conf/mm/mm2007.html</identifier>
	</reference>
	<reference name="toy03" src="bibtex:inproceedings" src-info="bibtex:line-16395" type="sharef:inproceedings" crossref="acmmm03">
		<names type="sharef:author">
			<person>
				<givenname>Kentaro</givenname>
				<surname>Toyama</surname>
			</person>
			<person>
				<givenname>Ron</givenname>
				<surname>Logan</surname>
			</person>
			<person>
				<givenname>Asta</givenname>
				<surname>Roseway</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>We describe an end-to-end system that capitalizes on geographic location tags for digital photographs. The World Wide Media eXchange (WWMX) database indexes large collections of image media by several pieces of metadata including timestamp, owner, and critically, location stamp. The location where a photo was shot is important because it says much about its semantic content, while being relatively easy to acquire, index, and search.The process of building, browsing, and writing applications for such a database raises issues that have heretofore been un- addressed in either the multimedia or the GIS community. This paper brings all of these issues together, explores different options, and offers novel solutions where necessary. Topics include acquisition of location tags for image media, data structures for location tags on photos, database optimization for location-tagged image media, and an intuitive UI for browsing a massive location-tagged image database. We end by describing an application built on top of the WWMX, a lightweight travelogue-authoring tool that automatically creates appropriate context maps for a slideshow of location-tagged photographs.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/957013.957046</identifier>
		<pages>156-166</pages>
		<title type="sharef:primaryTitle">Geographic Location Tags on Digital Images</title>
	</reference>
	<reference name="acmmm03" src="bibtex:proceedings" src-info="bibtex:line-16404" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>Lawrence A.</givenname>
				<surname>Rowe</surname>
			</person>
			<person>
				<givenname>Harrick M.</givenname>
				<surname>Vin</surname>
			</person>
			<person>
				<givenname>Thomas</givenname>
				<surname>Plagemann</surname>
			</person>
			<person>
				<givenname>Prashant J.</givenname>
				<surname>Shenoy</surname>
			</person>
			<person>
				<givenname>John R.</givenname>
				<surname>Smith</surname>
			</person>
		</names>
		<date value="2003-11"/>
		<address type="sharef:placePublished">Berkeley, California</address>
		<identifier type="sharef:isbn">1-58113-722-2</identifier>
		<publisher>ACM Press</publisher>
		<title type="sharef:primaryTitle">ACM Multimedia 2003</title>
		<identifier type="sharef:uri" resourceType="text/html">http://www.informatik.uni-trier.de/~ley/db/conf/mm/mm2003.html</identifier>
	</reference>
	<reference name="rut01" src="bibtex:inproceedings" src-info="bibtex:line-16420" type="sharef:inproceedings" crossref="mmm2001">
		<names type="sharef:author">
			<person>
				<givenname>Lloyd</givenname>
				<surname>Rutledge</surname>
			</person>
			<person>
				<givenname>Patrick</givenname>
				<surname>Schmitz</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>The media components integrated into multimedia presentations are typically entire files. At times the media component desired for integration, either as a navigation destination or as coordinate presentation, is a part of a file, or what we call a fragment. Basic media fragment integration has long been implemented in hypermedia systems, but not to the degree envisioned by hypermedia research. The current emergence of several XML-based formats is beginning to extend the possibilities for media fragment integration on a large scale. This paper presents a set of requirements for media fragment integration, describes how standards currently meet some of these requirements and proposes extensions to these standards for meeting remaining requirements.</p>
			</richtext>
		</abstract>
		<title type="sharef:primaryTitle">Improving Media Fragment Integration in Emerging Web Formats</title>
		<identifier type="sharef:uri" resourceType="application/pdf">http://www.cwi.nl/~media/publications/mmm01b.pdf</identifier>
	</reference>
	<reference name="mmm2001" src="bibtex:proceedings" src-info="bibtex:line-16428" type="sharef:proceedings">
		<date value="2001-09"/>
		<address type="sharef:placePublished">Amsterdam, Netherlands</address>
		<publisher>November</publisher>
		<title type="sharef:primaryTitle">8th International Conference on Multimedia Modeling</title>
		<identifier type="sharef:uri" resourceType="text/html">http://www.comp.nus.edu.sg/~mmm/mmm2001/mmm01-main.htm</identifier>
	</reference>
	<reference name="str92b" src="bibtex:inproceedings" src-info="bibtex:line-16442" type="sharef:inproceedings" crossref="iwaca92">
		<names type="sharef:author">
			<person>
				<givenname>W. Timothy</givenname>
				<surname>Strayer</surname>
			</person>
			<person>
				<givenname>Alfred C.</givenname>
				<surname>Weaver</surname>
			</person>
		</names>
		<field type="bibtex:index">XTP, real-time systems, multicast</field>
		<pages>93-101</pages>
		<title type="sharef:primaryTitle">Is XTP Suitable for Distributed Real-Time Systems?</title>
	</reference>
	<reference name="wea92" src="bibtex:inproceedings" src-info="bibtex:line-16450" type="sharef:inproceedings" crossref="iwaca92">
		<names type="sharef:author">
			<person>
				<givenname>Alfred C.</givenname>
				<surname>Weaver</surname>
			</person>
		</names>
		<field type="bibtex:index">XTP</field>
		<pages>253-259</pages>
		<title type="sharef:primaryTitle">The Xpress Transfer Protocol</title>
	</reference>
	<reference name="ste92" src="bibtex:inproceedings" src-info="bibtex:line-16458" type="sharef:inproceedings" crossref="iwaca92">
		<names type="sharef:author">
			<person>
				<givenname>Ralf</givenname>
				<surname>Steinmetz</surname>
			</person>
			<person>
				<givenname>Thomas</givenname>
				<surname>Meyer</surname>
			</person>
		</names>
		<field type="bibtex:index">HeiTS, multimedia applications, distributed systems</field>
		<pages>337-349</pages>
		<title type="sharef:primaryTitle">Modelling Distributed Multimedia Applications</title>
	</reference>
	<reference name="sol92" src="bibtex:inproceedings" src-info="bibtex:line-16466" type="sharef:inproceedings" crossref="iwaca92">
		<names type="sharef:author">
			<person>
				<givenname>Geert</givenname>
				<surname>Solvie</surname>
			</person>
		</names>
		<field type="bibtex:index">OSI, LARS, XOSI</field>
		<pages>383-392</pages>
		<title type="sharef:primaryTitle">A Flexible Open Systems Architecture Satisfying Modern Communication Requirements</title>
	</reference>
	<reference name="iwaca92" src="bibtex:proceedings" src-info="bibtex:line-16474" type="sharef:proceedings">
		<date value="1992-03"/>
		<address type="sharef:placePublished">Munich, Germany</address>
		<field type="bibtex:index">IWACA '92</field>
		<identifier type="sharef:isbn">3-7803-0764-X</identifier>
		<title type="sharef:primaryTitle">International Workshop on Advanced Teleservices and High-Speed Communication Architectures</title>
	</reference>
	<reference name="mau94" src="bibtex:inproceedings" src-info="bibtex:line-16488" type="sharef:inproceedings" crossref="iwaca94">
		<names type="sharef:author">
			<person>
				<givenname>Andreas</givenname>
				<surname>Mauthe</surname>
			</person>
			<person>
				<givenname>David</givenname>
				<surname>Hutchison</surname>
			</person>
			<person>
				<givenname>Geoff</givenname>
				<surname>Coulson</surname>
			</person>
			<person>
				<givenname>Silvester</givenname>
				<surname>Namuye</surname>
			</person>
		</names>
		<field type="bibtex:index">GCommS, group management, group communcations</field>
		<pages>266-279</pages>
		<title type="sharef:primaryTitle">From Requirements to Services: Group Communication Support for Distributed Multimedia Systems</title>
	</reference>
	<reference name="alt94" src="bibtex:inproceedings" src-info="bibtex:line-16496" type="sharef:inproceedings" crossref="iwaca94">
		<names type="sharef:author">
			<person>
				<givenname>Michael</givenname>
				<surname>Altenhofen</surname>
			</person>
			<person>
				<givenname>Joachim</givenname>
				<surname>Schaper</surname>
			</person>
			<person>
				<givenname>Susan</givenname>
				<surname>Thomas</surname>
			</person>
		</names>
		<field type="bibtex:index">BERKOM, MMC, MMM, MMT, multimedia</field>
		<pages>237-250</pages>
		<title type="sharef:primaryTitle">The BERKOM Multimedia Teleservices</title>
	</reference>
	<reference name="roz94" src="bibtex:inproceedings" src-info="bibtex:line-16504" type="sharef:inproceedings" crossref="iwaca94">
		<names type="sharef:author">
			<person>
				<givenname>Andreas</givenname>
				<surname>Rozek</surname>
			</person>
			<person>
				<givenname>Paul</givenname>
				<surname>Christ</surname>
			</person>
		</names>
		<field type="bibtex:index">CIO, multimedia</field>
		<pages>251-265</pages>
		<title type="sharef:primaryTitle">The CIO Multimedia Communication Platform</title>
	</reference>
	<reference name="dem94" src="bibtex:inproceedings" src-info="bibtex:line-16512" type="sharef:inproceedings" crossref="iwaca94">
		<names type="sharef:author">
			<person>
				<givenname>Bert J.</givenname>
				<surname>Dempsey</surname>
			</person>
			<person>
				<givenname>Matthew T.</givenname>
				<surname>Lucas</surname>
			</person>
			<person>
				<givenname>Alfred C.</givenname>
				<surname>Weaver</surname>
			</person>
		</names>
		<field type="bibtex:index">XTP, multicast, video distribution</field>
		<pages>376-386</pages>
		<title type="sharef:primaryTitle">Design and Implementation of a High Quality Video Distribution System using XTP Reliable Multicast</title>
	</reference>
	<reference name="iwaca94" src="bibtex:proceedings" src-info="bibtex:line-16520" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>Ralf</givenname>
				<surname>Steinmetz</surname>
			</person>
		</names>
		<date value="1994-09"/>
		<address type="sharef:placePublished">Heidelberg, Germany</address>
		<field type="bibtex:index">IWACA '94</field>
		<identifier type="sharef:isbn">3-540-58494-3</identifier>
		<publisher>Springer-Verlag</publisher>
		<title type="sharef:seriesTitle">Lecture Notes in Computer Science</title>
		<title type="sharef:primaryTitle">Second International Workshop on Advanced Teleservices and High-Speed Communication Architectures</title>
		<volume>868</volume>
	</reference>
	<reference name="szy94" src="bibtex:inproceedings" src-info="bibtex:line-16538" type="sharef:inproceedings" crossref="cost94">
		<names type="sharef:author">
			<person>
				<givenname>Clemens</givenname>
				<surname>Szyperski</surname>
			</person>
			<person>
				<givenname>Giorgio</givenname>
				<surname>Ventre</surname>
			</person>
		</names>
		<field type="bibtex:index">multimedia QoS</field>
		<pages>185-198</pages>
		<title type="sharef:primaryTitle">Efficient Support for Multiparty Communication</title>
	</reference>
	<reference name="mat94b" src="bibtex:inproceedings" src-info="bibtex:line-16546" type="sharef:inproceedings" crossref="cost94">
		<names type="sharef:author">
			<person>
				<givenname>Laurent</givenname>
				<surname>Mathy</surname>
			</person>
			<person>
				<givenname>Olivier</givenname>
				<surname>Bonaventure</surname>
			</person>
		</names>
		<field type="bibtex:index">multicast QoS, OSI95</field>
		<pages>199-218</pages>
		<title type="sharef:primaryTitle">QoS Negotiation for Multicast Communications</title>
	</reference>
	<reference name="car94" src="bibtex:inproceedings" src-info="bibtex:line-16554" type="sharef:inproceedings" crossref="cost94">
		<names type="sharef:author">
			<person>
				<givenname>Georg</givenname>
				<surname>Carle</surname>
			</person>
			<person>
				<givenname>Jochen H.</givenname>
				<surname>Schiller</surname>
			</person>
			<person>
				<givenname>Claudia</givenname>
				<surname>Schmidt</surname>
			</person>
		</names>
		<field type="bibtex:index">multipoint QoS, GCS</field>
		<pages>219-240</pages>
		<title type="sharef:primaryTitle">Support for High-Performance Multipoint Multimedia Services</title>
	</reference>
	<reference name="cost94" src="bibtex:proceedings" src-info="bibtex:line-16562" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>David</givenname>
				<surname>Hutchison</surname>
			</person>
			<person>
				<givenname>André</givenname>
				<surname>Danthine</surname>
			</person>
			<person>
				<givenname>Helmut</givenname>
				<surname>Leopold</surname>
			</person>
			<person>
				<givenname>Geoff</givenname>
				<surname>Coulson</surname>
			</person>
		</names>
		<date value="1994-11"/>
		<address type="sharef:placePublished">Vienna, Austria</address>
		<field type="bibtex:index">COST 237</field>
		<identifier type="sharef:isbn">3-540-58759-4</identifier>
		<publisher>Springer-Verlag</publisher>
		<title type="sharef:seriesTitle">Lecture Notes in Computer Science</title>
		<title type="sharef:primaryTitle">Multimedia Transport and Teleservices — International COST 237 Workshop</title>
		<volume>882</volume>
	</reference>
	<reference name="mau95" src="bibtex:inproceedings" src-info="bibtex:line-16580" type="sharef:inproceedings" crossref="cost95">
		<names type="sharef:author">
			<person>
				<givenname>Andreas</givenname>
				<surname>Mauthe</surname>
			</person>
			<person>
				<givenname>Geoff</givenname>
				<surname>Coulson</surname>
			</person>
			<person>
				<givenname>David</givenname>
				<surname>Hutchison</surname>
			</person>
			<person>
				<givenname>Silvester</givenname>
				<surname>Namuye</surname>
			</person>
		</names>
		<field type="bibtex:index">group supportland, multimedia, T.120, XTP, BERKOM MMC, ITU-TSS, MICE</field>
		<pages>1-18</pages>
		<title type="sharef:primaryTitle">Group Support in Multimedia Communications Systems</title>
	</reference>
	<reference name="rez95" src="bibtex:inproceedings" src-info="bibtex:line-16588" type="sharef:inproceedings" crossref="cost95">
		<names type="sharef:author">
			<person>
				<givenname>José F.</givenname>
				<surname link="de">Rezende</surname>
			</person>
			<person>
				<givenname>Andreas</givenname>
				<surname>Mauthe</surname>
			</person>
			<person>
				<givenname>David</givenname>
				<surname>Hutchison</surname>
			</person>
			<person>
				<givenname>Serge</givenname>
				<surname>Fdida</surname>
			</person>
		</names>
		<field type="bibtex:index">M-Connection, GCommS, XTP</field>
		<pages>38-58</pages>
		<title type="sharef:primaryTitle">M-Connection Service: A Multicast Service for Distributed Multimedia Applications</title>
	</reference>
	<reference name="tou95a" src="bibtex:inproceedings" src-info="bibtex:line-16596" type="sharef:inproceedings" crossref="cost95">
		<names type="sharef:author">
			<person>
				<givenname>François</givenname>
				<surname>Toutain</surname>
			</person>
			<person>
				<givenname>Laurent</givenname>
				<surname>Toutain</surname>
			</person>
		</names>
		<field type="bibtex:index">PRISM, PTP</field>
		<pages>139-158</pages>
		<title type="sharef:primaryTitle">Network Support for Multimedia Communications Using Distributed Media Scaling</title>
	</reference>
	<reference name="mat95" src="bibtex:inproceedings" src-info="bibtex:line-16604" type="sharef:inproceedings" crossref="cost95">
		<names type="sharef:author">
			<person>
				<givenname>Laurent</givenname>
				<surname>Mathy</surname>
			</person>
			<person>
				<givenname>Olivier</givenname>
				<surname>Bonaventure</surname>
			</person>
		</names>
		<field type="bibtex:index">ACCOPI, AMTS, ATM, UNI</field>
		<pages>159-175</pages>
		<title type="sharef:primaryTitle">The ACCOPI Multimedia Transport Service over ATM</title>
	</reference>
	<reference name="cost95" src="bibtex:proceedings" src-info="bibtex:line-16612" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>David</givenname>
				<surname>Hutchison</surname>
			</person>
			<person>
				<givenname>H.</givenname>
				<surname>Christiansen</surname>
			</person>
			<person>
				<givenname>Geoff</givenname>
				<surname>Coulson</surname>
			</person>
			<person>
				<givenname>André</givenname>
				<surname>Danthine</surname>
			</person>
		</names>
		<date value="1995-11"/>
		<address type="sharef:placePublished">Copenhagen, Denmark</address>
		<field type="bibtex:index">COST 237</field>
		<identifier type="sharef:isbn">3-540-61028-6</identifier>
		<publisher>Springer-Verlag</publisher>
		<title type="sharef:seriesTitle">Lecture Notes in Computer Science</title>
		<title type="sharef:primaryTitle">Teleservices and Multimedia Communications — Second COST 237 Workshop</title>
		<volume>1052</volume>
	</reference>
	<reference name="wil96d" src="bibtex:inproceedings" src-info="bibtex:line-16630" type="sharef:inproceedings" crossref="cost96">
		<names type="sharef:author">
			<person>
				<givenname>Erik</givenname>
				<surname>Wilde</surname>
			</person>
			<person>
				<givenname>Pascal</givenname>
				<surname>Freiburghaus</surname>
			</person>
			<person>
				<givenname>Daniel</givenname>
				<surname>Koller</surname>
			</person>
			<person>
				<givenname>Bernhard</givenname>
				<surname>Plattner</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Distributed multimedia applications are very demanding with respect to support they require from the underlying group communication platform. In this paper, an approach is described which aims at providing group communication platform designers with a component which can be used for powerful group and session management functionality. This component, which can be integrated into group communication platforms, is part of a system called the group and session management system (GMS). The GMS model consists of GMS user agents, which are the components to be integrated into group communication platforms, and GMS system agents which are distributed directory agents providing the distributed database which the user agents access. Communication between these two types of agents is defined in two protocols, the GMS access protocol between user agents and system agents, and the GMS system protocol between system agents. GMS also defines a number of objects and relations which can be used to manage users, groups, and sessions on a very abstract level, thus providing both group communication platform designers and programmers of distributed multimedia application with a high-level description of group communications. This approach enables a truly integrated approach for collaborative applications, where all applications, even when using different group communication platforms, can share the same database about users, groups, and sessions. The paper also contains a short description of the ongoing implementation of GMS's components.</p>
			</richtext>
		</abstract>
		<field type="bibtex:index">GMS, GUA, GSA, GAP, GSP</field>
		<pages>1-22</pages>
		<title type="sharef:primaryTitle">A Group and Session Management System for Distributed Multimedia Applications</title>
		<identifier type="sharef:uri">http://dret.net/netdret/publications#wil96d</identifier>
	</reference>
	<reference name="wad96" src="bibtex:inproceedings" src-info="bibtex:line-16640" type="sharef:inproceedings" crossref="cost96">
		<names type="sharef:author">
			<person>
				<givenname>Daniel G.</givenname>
				<surname>Waddington</surname>
			</person>
			<person>
				<givenname>Geoff</givenname>
				<surname>Coulson</surname>
			</person>
			<person>
				<givenname>David</givenname>
				<surname>Hutchison</surname>
			</person>
		</names>
		<pages>75-103</pages>
		<title type="sharef:primaryTitle">Specifying QoS for Multimedia Communications with Distributed Programming Environments</title>
	</reference>
	<reference name="deg96" src="bibtex:inproceedings" src-info="bibtex:line-16647" type="sharef:inproceedings" crossref="cost96">
		<names type="sharef:author">
			<person>
				<givenname>Mikael</givenname>
				<surname>Degermark</surname>
			</person>
			<person>
				<givenname>Stephen</givenname>
				<surname>Pink</surname>
			</person>
		</names>
		<pages>169-182</pages>
		<title type="sharef:primaryTitle">Issues in the Design of a New Network Protocol</title>
	</reference>
	<reference name="cost96" src="bibtex:proceedings" src-info="bibtex:line-16654" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>Giorgio</givenname>
				<surname>Ventre</surname>
			</person>
			<person>
				<givenname>Jordi</givenname>
				<surname>Domingo-Pascual</surname>
			</person>
			<person>
				<givenname>André</givenname>
				<surname>Danthine</surname>
			</person>
		</names>
		<date value="1996-11"/>
		<address type="sharef:placePublished">Barcelona, Spain</address>
		<field type="bibtex:index">COST 237</field>
		<identifier type="sharef:isbn">3-540-62096-6</identifier>
		<publisher>Springer-Verlag</publisher>
		<title type="sharef:seriesTitle">Lecture Notes in Computer Science</title>
		<title type="sharef:primaryTitle">Multimedia Telecommunications and Applications — Third COST 237 Workshop</title>
		<volume>1185</volume>
	</reference>
	<reference name="var94" src="bibtex:inproceedings" src-info="bibtex:line-16672" type="sharef:inproceedings" crossref="dmsa94">
		<names type="sharef:author">
			<person>
				<givenname>Theodora A.</givenname>
				<surname>Varvarigou</surname>
			</person>
			<person>
				<givenname>Venkatesh</givenname>
				<surname>Krishnaswamy</surname>
			</person>
		</names>
		<field type="bibtex:index">DARTS</field>
		<pages>73-77</pages>
		<title type="sharef:primaryTitle">Distributed Architecture for Telecommunication Services</title>
	</reference>
	<reference name="pla94" src="bibtex:inproceedings" src-info="bibtex:line-16680" type="sharef:inproceedings" crossref="dmsa94">
		<names type="sharef:author">
			<person>
				<givenname>Thomas</givenname>
				<surname>Plagemann</surname>
			</person>
			<person>
				<givenname>Janusz</givenname>
				<surname>Waclawczyk</surname>
			</person>
			<person>
				<givenname>Bernhard</givenname>
				<surname>Plattner</surname>
			</person>
		</names>
		<field type="bibtex:index">Da CaPo, multimedia</field>
		<pages>78-81</pages>
		<title type="sharef:primaryTitle">Management of Configurable Protocols for Multimedia Applications</title>
	</reference>
	<reference name="jon94" src="bibtex:inproceedings" src-info="bibtex:line-16688" type="sharef:inproceedings" crossref="dmsa94">
		<names type="sharef:author">
			<person>
				<givenname>Karl</givenname>
				<surname>Jonas</surname>
			</person>
			<person>
				<givenname>Manfred</givenname>
				<surname>Kaul</surname>
			</person>
			<person>
				<givenname>Klaus</givenname>
				<surname>Rebensburg</surname>
			</person>
			<person>
				<givenname>Frank</givenname>
				<surname>Ruge</surname>
			</person>
		</names>
		<field type="bibtex:index">BERKOM, MMC, MMM, MMT, GLASS, POLIKOM, TeleCAD, EDGE, TUBKOM, JVTOS, VoD, RTBs</field>
		<pages>109-113</pages>
		<title type="sharef:primaryTitle">Distributed Multimedia Research Projects and Applications in Germany</title>
	</reference>
	<reference name="voj94" src="bibtex:inproceedings" src-info="bibtex:line-16696" type="sharef:inproceedings" crossref="dmsa94">
		<names type="sharef:author">
			<person>
				<givenname>Franz</givenname>
				<surname>Vojik</surname>
			</person>
		</names>
		<field type="bibtex:index">IRIS, groupware, collaborative editing</field>
		<pages>277-280</pages>
		<title type="sharef:primaryTitle">Video Support for the Distributed Multi-User Editor IRIS</title>
	</reference>
	<reference name="dmsa94" src="bibtex:proceedings" src-info="bibtex:line-16704" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>Borko</givenname>
				<surname>Furht</surname>
			</person>
		</names>
		<date value="1994-08"/>
		<address type="sharef:placePublished">Honolulu, Hawaii</address>
		<identifier type="sharef:isbn">0-88986-194-3</identifier>
		<title type="sharef:primaryTitle">Distributed Multimedia Systems and Applications — IASTED/ISMM International Conference</title>
	</reference>
	<reference name="ver92" src="bibtex:inproceedings" src-info="bibtex:line-16718" type="sharef:inproceedings" crossref="dcs92">
		<names type="sharef:author">
			<person>
				<givenname>Paulo</givenname>
				<surname>Veríssimo</surname>
			</person>
			<person>
				<givenname>Luís</givenname>
				<surname>Rodrigues</surname>
			</person>
		</names>
		<field type="bibtex:index">group orientation, distributed systems, CSCW, distributed computer control, multicast, management</field>
		<pages>57-63</pages>
		<title type="sharef:primaryTitle">Group Orientation: A Paradigm for Distributed Systems of the Nineties</title>
	</reference>
	<reference name="nav92" src="bibtex:inproceedings" src-info="bibtex:line-16726" type="sharef:inproceedings" crossref="dcs92">
		<names type="sharef:author">
			<person>
				<givenname>Leandro</givenname>
				<surname>Navarro</surname>
			</person>
			<person>
				<givenname>Wolfgang</givenname>
				<surname>Prinz</surname>
			</person>
			<person>
				<givenname>Tom A.</givenname>
				<surname>Rodden</surname>
			</person>
		</names>
		<pages>4-10</pages>
		<title type="sharef:primaryTitle">Towards Open CSCW Systems</title>
	</reference>
	<reference name="pop92" src="bibtex:inproceedings" src-info="bibtex:line-16733" type="sharef:inproceedings" crossref="dcs92">
		<names type="sharef:author">
			<person>
				<givenname>Radu</givenname>
				<surname>Popescu-Zeletin</surname>
			</person>
			<person>
				<givenname>Volker</givenname>
				<surname>Tschammer</surname>
			</person>
			<person>
				<givenname>Michael</givenname>
				<surname>Tschichholz</surname>
			</person>
		</names>
		<pages>11-17</pages>
		<title type="sharef:primaryTitle">A Service Platform for Distributed Applications</title>
	</reference>
	<reference name="pla92" src="bibtex:inproceedings" src-info="bibtex:line-16740" type="sharef:inproceedings" crossref="dcs92">
		<names type="sharef:author">
			<person>
				<givenname>Thomas</givenname>
				<surname>Plagemann</surname>
			</person>
			<person>
				<givenname>Bernhard</givenname>
				<surname>Plattner</surname>
			</person>
			<person>
				<givenname>Martin</givenname>
				<surname>Vogt</surname>
			</person>
			<person>
				<givenname>Thomas</givenname>
				<surname>Walter</surname>
			</person>
		</names>
		<field type="bibtex:index">Da CaPo</field>
		<pages>100-106</pages>
		<title type="sharef:primaryTitle">A Model for Dynamic Configuration of Light-Weight Protocols</title>
	</reference>
	<reference name="dcs92" src="bibtex:proceedings" src-info="bibtex:line-16748" type="sharef:proceedings">
		<date value="1992"/>
		<address type="sharef:placePublished">Taipei, Taiwan</address>
		<field type="bibtex:index">DCS '92</field>
		<identifier type="sharef:isbn">0-8186-2755-7</identifier>
		<field type="bibtex:key">Third Workshop on Future Trends of Distributed Computing Systems</field>
		<publisher>IEEE Computer Society Press</publisher>
		<title type="sharef:primaryTitle">Third Workshop on Future Trends of Distributed Computing Systems</title>
	</reference>
	<reference name="bub91" src="bibtex:inproceedings" src-info="bibtex:line-16763" type="sharef:inproceedings" crossref="infocom91">
		<names type="sharef:author">
			<person>
				<givenname>Rick G.</givenname>
				<surname>Bubenik</surname>
			</person>
			<person>
				<givenname>John D.</givenname>
				<surname>DeHart</surname>
			</person>
			<person>
				<givenname>Michael E.</givenname>
				<surname>Gaddis</surname>
			</person>
		</names>
		<field type="bibtex:index">CMAP, ATM signaling</field>
		<pages>59-68</pages>
		<title type="sharef:primaryTitle">Multipoint Connection Management in High Speed Networks</title>
	</reference>
	<reference name="infocom91" src="bibtex:proceedings" src-info="bibtex:line-16771" type="sharef:proceedings">
		<date value="1991"/>
		<address type="sharef:placePublished">Bal Harbour, Florida</address>
		<field type="bibtex:index">INFOCOM '91</field>
		<publisher>IEEE Computer Society Press</publisher>
		<title type="sharef:primaryTitle">IEEE INFOCOM '91 Conference on Computer Communications</title>
	</reference>
	<reference name="bub92" src="bibtex:inproceedings" src-info="bibtex:line-16784" type="sharef:inproceedings" crossref="infocom92">
		<names type="sharef:author">
			<person>
				<givenname>Rick G.</givenname>
				<surname>Bubenik</surname>
			</person>
			<person>
				<givenname>Michael E.</givenname>
				<surname>Gaddis</surname>
			</person>
			<person>
				<givenname>John D.</givenname>
				<surname>DeHart</surname>
			</person>
		</names>
		<field type="bibtex:index">ATM, VC, virtual channels, VP, virtual paths</field>
		<pages>1035-1042</pages>
		<title type="sharef:primaryTitle">Communicating with Virtual Paths and Virtual Channels</title>
	</reference>
	<reference name="infocom92" src="bibtex:proceedings" src-info="bibtex:line-16792" type="sharef:proceedings">
		<date value="1992"/>
		<address type="sharef:placePublished">Firenze, Italy</address>
		<field type="bibtex:index">INFOCOM '92</field>
		<publisher>IEEE Computer Society Press</publisher>
		<title type="sharef:primaryTitle">IEEE INFOCOM '92 Conference on Computer Communications</title>
	</reference>
	<reference name="par07" src="bibtex:inproceedings" src-info="bibtex:line-16805" type="sharef:inproceedings" crossref="esec2007">
		<names type="sharef:author">
			<person>
				<givenname>Fernando Silva</givenname>
				<surname>Parreiras</surname>
			</person>
			<person>
				<givenname>Steffen</givenname>
				<surname>Staab</surname>
			</person>
			<person>
				<givenname>Andreas</givenname>
				<surname>Winter</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>In software engineering, the use of models and metamodeling approaches (e.g., MDA with MOF/UML) for purposes such as software design or software validation is an established practice. Ontologies constitute domain models formalized using expressive logic languages for class definitions and rules. Hence, when seen from an abstract point of view, the two paradigms and their various technological spaces seem closely related. However, in the state-of-the-art research and practice the two technologies are just beginning to converge and the relationship between the two is still under exploration. In this paper, we give an outline of current ontology technologies, such as the Semantic Web standards for a Web Ontology Language (OWL). Then, we describe a domain analysis of the different technical spaces, explaining the features of the different paradigms. Eventually, we describe some avenues for integrating various ontological technical spaces into metamodeling technical spaces.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/1287624.1287687</identifier>
		<title type="sharef:primaryTitle">On Marrying Ontological and Metamodeling Technical Spaces</title>
	</reference>
	<reference name="kla07" src="bibtex:inproceedings" src-info="bibtex:line-16813" type="sharef:inproceedings" crossref="esec2007">
		<names type="sharef:author">
			<person>
				<givenname>Felix</givenname>
				<surname>Klar</surname>
			</person>
			<person>
				<givenname>Alexander</givenname>
				<surname>Königs</surname>
			</person>
			<person>
				<givenname>Andy</givenname>
				<surname>Schürr</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Current rule-based model transformation approaches as the Query/View/Transformation (QVT) standard or Triple Graph Grammars (TGGs) disregard means for structuring model transformation specifications. As a result large scale model transformation specifications are hard to understand and to maintain. Furthermore, these specifications cannot utilize reusing mechanisms which would reduce the size of the specifications and improve their readability. In this paper we discuss how to transfer means for structuring huge metamodels and models as provided by common modeling languages to the world of model transformation languages. We focus on generalization issues as well as on package dependencies. As a result we come up with an extension to our TGG approach that enables the user to specify structured bidirectional model transformations in a declarative way.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/1287624.1287664</identifier>
		<title type="sharef:primaryTitle">Model Transformation in the Large</title>
	</reference>
	<reference name="ere07" src="bibtex:inproceedings" src-info="bibtex:line-16821" type="sharef:inproceedings" crossref="esec2007">
		<names type="sharef:author">
			<person>
				<givenname>Justin R.</givenname>
				<surname>Erenkrantz</surname>
			</person>
			<person>
				<givenname>Michael</givenname>
				<surname>Gorlick</surname>
			</person>
			<person>
				<givenname>Girish</givenname>
				<surname>Suryanarayana</surname>
			</person>
			<person>
				<givenname>Richard N.</givenname>
				<surname>Taylor</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Representational State Transfer (REST) guided the creation and expansion of the modern web. What began as an internet-scale distributed hypermedia system is now a vast sea of shared and interdependent services. However, despite the expressive power of REST, not all of its benefits are consistently realized by working systems. To resolve the dissonance between the promise of REST and the reality of fielded systems, we critically examine numerous web architectures. Our investigation yields a set of extensions to REST, an architectural style called Computational REST (CREST), that not only offers additional design guidance, but pinpoints, in many cases, the root cause of the apparent dissonance between style and implementation. Furthermore, CREST explains emerging web architectures (such as mashups) and points to novel computational structures.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/1287624.1287660</identifier>
		<title type="sharef:primaryTitle">From Representations to Computations: The Evolution of Web Architectures</title>
		<field type="bibtex:topic">rest[0.9] crest[1]</field>
	</reference>
	<reference name="esec2007" src="bibtex:proceedings" src-info="bibtex:line-16830" type="sharef:proceedings">
		<date value="2007-09"/>
		<address type="sharef:placePublished">Dubrovnik, Croatia</address>
		<identifier type="sharef:isbn">978-1-59593-811-4</identifier>
		<publisher>ACM Press</publisher>
		<title type="sharef:primaryTitle">6th Joint Meeting of the European Software Engineering Conference and the ACM SIGSOFT Symposium on The foundations of Software Engineering</title>
		<identifier type="sharef:uri" resourceType="text/html">http://www.informatik.uni-trier.de/~ley/db/conf/sigsoft/fse2007.html</identifier>
	</reference>
	<reference name="and02" src="bibtex:inproceedings" src-info="bibtex:line-16845" type="sharef:inproceedings" crossref="icse2002">
		<names type="sharef:author">
			<person>
				<givenname>Kenneth M.</givenname>
				<surname>Anderson</surname>
			</person>
			<person>
				<givenname>Susanne A.</givenname>
				<surname>Sherba</surname>
			</person>
			<person>
				<givenname>William V.</givenname>
				<surname>Lepthien</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Software engineers confront many challenges during software development. One challenge is managing the relationships that exist between software artifacts. We refer to this task as information integration, since establishing a relationship between documents typically implies that an engineer must integrate information from each of the documents to perform a development task. In the past, we have applied open hypermedia techniques and technology to address this challenge. We now extend this work with the development of an information integration environment. We present the design of our environment along with details of its first prototype implementation. Furthermore, we describe our efforts to evaluate the utility of our approach. Our first experiment involves the discovery of keyword relationships between text-based software artifacts. Our second experiment examines the code of an open source project and generates a report on how its module relationships have evolved over time. Finally, our third experiment develops the capability to link code claiming to implement W3C standards with the XHTML representation of the standards themselves. These experiments combine to demonstrate the promise of our approach. We conclude by asserting that the process of software development can be significantly enhanced if more tools made their relationships available for integration.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/581339.581403</identifier>
		<title type="sharef:primaryTitle">Towards Large-Scale Information Integration</title>
	</reference>
	<reference name="icse2002" src="bibtex:proceedings" src-info="bibtex:line-16853" type="sharef:proceedings">
		<date value="2002-05"/>
		<address type="sharef:placePublished">Orlando, Florida</address>
		<field type="bibtex:index">ICSE 2002</field>
		<identifier type="sharef:isbn">0-7695-0493-0</identifier>
		<publisher>ACM Press</publisher>
		<title type="sharef:primaryTitle">22nd International Conference on Software Engineering</title>
		<identifier type="sharef:uri" resourceType="text/html">http://www.informatik.uni-trier.de/~ley/db/conf/icse/icse2002.html</identifier>
	</reference>
	<reference name="kha04" src="bibtex:inproceedings" src-info="bibtex:line-16869" type="sharef:inproceedings" crossref="icse2004">
		<names type="sharef:author">
			<person>
				<givenname>Rohit</givenname>
				<surname>Khare</surname>
			</person>
			<person>
				<givenname>Richard N.</givenname>
				<surname>Taylor</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Because it takes time and trust to establish agreement, traditional consensus-based architectural styles cannot safely accommodate resources that change faster than it takes to transmit notification of that change, nor resources that must be shared across independent agencies. The alternative is decentralization: permitting independent agencies to make their own decisions. Our definition contrasts with that of distribution, in which several agents share control of a single decision. Ultimately, the physical limits of network latency and the social limits of independent agency call for solutions that can accommodate multiple values for the same variable. Our approach to this challenge is architectural: proposing constraints on the configuration of components and connectors to induce particular desired properties of the whole application. Specifically, we present, implement, and evaluate variations of the World Wide Web's Representational State Transfer (REST) architectural style that support distributed and decentralized systems.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1109/ICSE.2004.1317465</identifier>
		<title type="sharef:primaryTitle">Extending the Representational State Transfer (REST) Architectural Style for Decentralized Systems</title>
		<identifier type="sharef:uri" resourceType="application/pdf">http://www.ics.uci.edu/~rohit/ARRESTED-ICSE.pdf</identifier>
	</reference>
	<reference name="icse2004" src="bibtex:proceedings" src-info="bibtex:line-16878" type="sharef:proceedings">
		<date value="2004-05"/>
		<address type="sharef:placePublished">Edinburgh, UK</address>
		<field type="bibtex:index">ICSE 2004</field>
		<identifier type="sharef:isbn">0-7695-2163-0</identifier>
		<publisher>ACM Press</publisher>
		<title type="sharef:primaryTitle">26th International Conference on Software Engineering</title>
		<identifier type="sharef:uri" resourceType="text/html">http://www.informatik.uni-trier.de/~ley/db/conf/icse/icse2004.html</identifier>
	</reference>
	<reference name="wil00b" src="bibtex:inproceedings" src-info="bibtex:line-16894" type="sharef:inproceedings" crossref="hicss33">
		<names type="sharef:author">
			<person>
				<givenname>Erik</givenname>
				<surname>Wilde</surname>
			</person>
			<person>
				<givenname>David</givenname>
				<surname>Lowe</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Influenced by the linking model which is implicit in HTML, today's publishing model on the Web is content-centered, with the emphasis of publishing on content rather than links. With the growing amount of information available on the Web, and the more powerful hypermedia architectures made possible by new Web technologies, putting the content into context will become increasingly important. In this paper, a new way of structuring publishing systems for information providers is presented in an attempt to shift the emphasis in Web-based publishing from content to an improved balance between content and links. After a description of the architecture of a link-based publishing system, a strategy for implementing such a system is described. Finally, a number of challenges associated with such a fundamental transition in the publishing model are described, in the technical as well as in the organizational domain.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1109/HICSS.2000.926692</identifier>
		<pages>3009-3018</pages>
		<title type="sharef:primaryTitle">From Content-Centered Publishing to a Link-Based View of Information Resources</title>
		<identifier type="sharef:uri">http://dret.net/netdret/publications#wil00b</identifier>
		<identifier type="sharef:uri" resourceType="application/pdf">http://www.computer.org/proceedings/hicss/0493/04933/04933009.pdf</identifier>
		<identifier type="sharef:uri">http://portal.acm.org/citation.cfm?id=820265</identifier>
	</reference>
	<reference name="hicss33" src="bibtex:proceedings" src-info="bibtex:line-16906" type="sharef:proceedings">
		<date value="2000-01"/>
		<address type="sharef:placePublished">Maui, Hawaii</address>
		<field type="bibtex:index">HICSS-33</field>
		<identifier type="sharef:isbn">0-7695-0493-0</identifier>
		<publisher>IEEE Computer Society Press</publisher>
		<title type="sharef:primaryTitle">33rd Hawaii International Conference on System Sciences</title>
		<identifier type="sharef:uri" resourceType="text/html">http://www.computer.org/proceedings/hicss/0493/04933/0493toc.htm</identifier>
	</reference>
	<reference name="goe01" src="bibtex:inproceedings" src-info="bibtex:line-16922" type="sharef:inproceedings" crossref="hicss34">
		<names type="sharef:author">
			<person>
				<givenname>Karl Michael</givenname>
				<surname>Göschka</surname>
			</person>
			<person>
				<givenname>Robert</givenname>
				<surname>Smeikal</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Modern E-Commerce Applications tend to have a lot of different user interfaces, most important today are Java and HTML but also emerging technologies like Agents or WAP cellular phones or even three dimensional environments (VRML). The difficulty is to make all those interfaces work together with the same application in an almost similar and transparent way and to keep them synchronized with each other during the lifetime of the application. Our approach is to describe the interactions of an UI rather than the elements or components with an XML description called IML — Interaction Markup Language. Unlike UIML (User Interface Markup Language) those interactions are then assigned to technology specific interactions first, which in turn are then finally assigned to a particular implementation. An IML description is also stable against future developments: To enable the application for a new device, only the IML renderer has to be implemented.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1109/HICSS.2001.927106</identifier>
		<title type="sharef:primaryTitle">Interaction Markup Language — An Open Interface for Device Independent Interaction with E-Commerce Applications</title>
		<identifier type="sharef:uri">http://ieeexplore.ieee.org/xpls/abs_all.jsp?arnumber=927106</identifier>
	</reference>
	<reference name="mck01" src="bibtex:inproceedings" src-info="bibtex:line-16931" type="sharef:inproceedings" crossref="hicss34">
		<names type="sharef:author">
			<person>
				<givenname>Bruce</givenname>
				<surname>McKenzie</surname>
			</person>
			<person>
				<givenname>Andy</givenname>
				<surname>Cockburn</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>There is a surprising lack of empirical research into user interaction with the web. This paper reports the results of an analysis of four months of logged data describing web use. The results update and extend earlier studies carried out in 1994 and 1995. We found that web page revisitation is a much more prevalent activity than previously reported (approximately 80 percent of pages have been previously visited by the user), that most pages are visited for a surprisingly short period, and that users maintain large (and possibly overwhelming) bookmark collections.</p>
			</richtext>
		</abstract>
		<title type="sharef:primaryTitle">An Emprical Analysis of Web Page Revisitation</title>
		<identifier type="sharef:uri" resourceType="application/pdf">http://www.hicss.hawaii.edu/HICSS_34/PDFs/ETWFW03.pdf</identifier>
	</reference>
	<reference name="hicss34" src="bibtex:proceedings" src-info="bibtex:line-16939" type="sharef:proceedings">
		<date value="2001-01"/>
		<address type="sharef:placePublished">Maui, Hawaii</address>
		<field type="bibtex:index">HICSS-34</field>
		<publisher>IEEE Computer Society Press</publisher>
		<title type="sharef:primaryTitle">34th Hawaii International Conference on System Sciences</title>
		<identifier type="sharef:uri" resourceType="text/html">http://www.computer.org/proceedings/hicss/0493/04933/0493toc.htm</identifier>
		<identifier type="sharef:uri" resourceType="text/html">http://www.informatik.uni-trier.de/~ley/db/conf/hicss/hicss2001-7.html</identifier>
	</reference>
	<reference name="tra03" src="bibtex:inproceedings" src-info="bibtex:line-16955" type="sharef:inproceedings" crossref="hicss36">
		<names type="sharef:author">
			<person>
				<givenname>Bernard</givenname>
				<surname>Traversat</surname>
			</person>
			<person>
				<givenname>Mohamed</givenname>
				<surname>Abdelaziz</surname>
			</person>
			<person>
				<givenname>Dave</givenname>
				<surname>Doolin</surname>
			</person>
			<person>
				<givenname>Mike</givenname>
				<surname>Duigou</surname>
			</person>
			<person>
				<givenname>Jean-Christophe</givenname>
				<surname>Hugly</surname>
			</person>
			<person>
				<givenname>Eric</givenname>
				<surname>Pouyoul</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>The Web, the collection of all devices connected to the Internet, is on the verge of experiencing a massive evolution from a Web of Computers to a Web of Things as new devices such as phones, beepers, sensors, wearable computers, telemetry sensors, and tracking agents connect to the Internet. The open-source Project JXTA was initiated a year ago to specify a standard set of protocols for ad-hoc, pervasive, peer-to-peer computing as a foundation of the upcoming Web of Things. The following paper presents an up-to-date overview of the JXTA protocols and describes the latest implementation of the JXTA protocols in the "C" programming language. The paper discusses the overall architecture and trade off made to allow the JXTA-C implementation to run on a wide range of devices including supercomputers, servers, PCs, and memory-constrained embedded devices. The JXTA-C implementation delivers a small and efficient implementation of the JXTA protocols stack allowing the JXTA protocols to be embedded at the system level rather than the Java Virtual Machine (JVM) level for optimized performance and capabilities.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1109/HICSS.2003.1174816</identifier>
		<title type="sharef:primaryTitle">Project JXTA-C: Enabling a Web of Things</title>
	</reference>
	<reference name="hicss36" src="bibtex:proceedings" src-info="bibtex:line-16963" type="sharef:proceedings">
		<date value="2003-01"/>
		<address type="sharef:placePublished">Big Island, Hawaii</address>
		<field type="bibtex:index">HICSS-36</field>
		<publisher>IEEE Computer Society Press</publisher>
		<title type="sharef:primaryTitle">36th Hawaii International Conference on System Sciences</title>
	</reference>
	<reference name="rao04" src="bibtex:inproceedings" src-info="bibtex:line-16977" type="sharef:inproceedings" crossref="hicss37">
		<names type="sharef:author">
			<person>
				<givenname>Bharat</givenname>
				<surname>Rao</surname>
			</person>
			<person>
				<givenname>Louis</givenname>
				<surname>Minakakis</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Location based services are a growth area for service providers looking to fulfill new customer needs, and network operators looking to augment their revenues. While the idea of using information about customer location to deliver focused services may be extremely appealing, there are significant risks and challenges to be faced. In addition to the technical hurdles, understanding and catering to customer experience is critical for success. In this paper, we will describe recent developments in the area of LBS, and propose a model to address customer experience issues in this domain. In particular, we will describe the types of revenue models and niche applications that might be profitably targeted by LBS providers.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1109/HICSS.2004.1265228</identifier>
		<title type="sharef:primaryTitle">Assessing the Business Impact of Location Based Services</title>
		<identifier type="sharef:uri" resourceType="application/pdf">http://csdl2.computer.org/comp/proceedings/hicss/2004/2056/03/205630078c.pdf</identifier>
	</reference>
	<reference name="kli04" src="bibtex:inproceedings" src-info="bibtex:line-16986" type="sharef:inproceedings" crossref="hicss37">
		<names type="sharef:author">
			<person>
				<givenname>Ralf</givenname>
				<surname>Klischewski</surname>
			</person>
			<person>
				<givenname>Martti</givenname>
				<surname>Jeenicke</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>This article examines a case of developing a prototype for an ontology-driven e-government application based on Semantic Web technologies in order to learn more about how to interrelate systems development with the tasks of information and knowledge management related to e-government service provision. The focus of evaluation is set by analyzing the information management challenges specific to the administrative domain and by the need for taking into account the increased granularity of informational resources and the manifold semantic differences in dealing with those resources. Following the different tasks and problems within the development process the authors identify what appeared to be critical issues: requirements analysis, choice and mastering of Semantic Web technologies, representation of ontology and informational resources, creating interfaces for users and other services. Based on the project analysis, the article concludes by suggesting an agenda for the cooperation of administrative information managers and systems developers as a prerequisite for successful Semantic Web projects in e-government.</p>
			</richtext>
		</abstract>
		<title type="sharef:primaryTitle">Semantic Web Technologies for Information Management within e-Government Services</title>
		<identifier type="sharef:uri" resourceType="application/pdf">http://csdl.computer.org/comp/proceedings/hicss/2004/2056/05/205650119b.pdf</identifier>
		<identifier type="sharef:uri">http://swt-www.informatik.uni-hamburg.de/publications/details.php?id=275</identifier>
	</reference>
	<reference name="hicss37" src="bibtex:proceedings" src-info="bibtex:line-16995" type="sharef:proceedings">
		<date value="2004-01"/>
		<address type="sharef:placePublished">Big Island, Hawaii</address>
		<field type="bibtex:index">HICSS-37</field>
		<publisher>IEEE Computer Society Press</publisher>
		<title type="sharef:primaryTitle">37th Hawaii International Conference on System Sciences</title>
		<identifier type="sharef:uri" resourceType="text/html">http://csdl.computer.org/comp/proceedings/hicss/2004/2056/00/2056toc.htm</identifier>
	</reference>
	<reference name="fal07" src="bibtex:inproceedings" src-info="bibtex:line-17010" type="sharef:inproceedings" crossref="hicss40">
		<names type="sharef:author">
			<person>
				<givenname>Jürgen</givenname>
				<surname>Falb</surname>
			</person>
			<person>
				<givenname>Roman</givenname>
				<surname>Popp</surname>
			</person>
			<person>
				<givenname>Thomas</givenname>
				<surname>Röck</surname>
			</person>
			<person>
				<givenname>Helmut</givenname>
				<surname>Jelinek</surname>
			</person>
			<person>
				<givenname>Edin</givenname>
				<surname>Arnautovic</surname>
			</person>
			<person>
				<givenname>Hermann</givenname>
				<surname>Kaindl</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>The problems involved in the development of user interfaces become even more severe through the ubiquitous use of a variety of devices such as PCs, mobile phones and PDAs. Each of these devices has its own specifics that require a special user interface. Therefore, we developed and implemented an approach to generate user interfaces for multiple devices fully automatically from a high-level model. In contrast to previous approaches focusing on abstracting the user interface per se, we make use of speech act theory from the philosophy of language for the specification of desired intentions in interactions. Our new approach of using communicative acts in high-level models of user interfaces allows their creation with less technical knowledge, since such models are easier to provide than user-interface code in a usual programming language. From one such high-level model, multiple user interfaces for diverse devices are rendered fully automatically using a number of heuristics. A generated user interface for a PDA is already in real-world use and its usability was informally evaluated as good.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1109/HICSS.2007.236</identifier>
		<title type="sharef:primaryTitle">Semantic Web Technologies for Information Management within e-Government Services</title>
	</reference>
	<reference name="hicss40" src="bibtex:proceedings" src-info="bibtex:line-17018" type="sharef:proceedings">
		<date value="2007-01"/>
		<address type="sharef:placePublished">Big Island, Hawaii</address>
		<field type="bibtex:index">HICSS-40</field>
		<publisher>IEEE Computer Society Press</publisher>
		<title type="sharef:primaryTitle">40th Hawaii International Conference on System Sciences</title>
		<identifier type="sharef:uri" resourceType="text/html">http://www.informatik.uni-trier.de/~ley/db/conf/hicss/hicss2007.html</identifier>
	</reference>
	<reference name="hea08" src="bibtex:inproceedings" src-info="bibtex:line-17033" type="sharef:inproceedings" crossref="hicss41">
		<names type="sharef:author">
			<person>
				<givenname>Marti A.</givenname>
				<surname>Hearst</surname>
			</person>
			<person>
				<givenname>Daniela</givenname>
				<surname>Rosner</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>We examine the recent information visualization phenomenon known as tag clouds, which are an interesting combination of data visualization, web design element, and social marker. Using qualitative methods, we find evidence that those who use tag clouds do so primarily because they are perceived as having an inherently social or personal component, in that they suggest what a person or a group of people is doing or is interested in, and to some degree how that changes over time; they are visually dynamic and thus suggest activity; they are a compact alternative to a long list; they signal that a site has tags; and they are perceived as being fun, popular, and/or hip. The primary reasons people object to tag clouds are their visual aesthetics, their questionable usability, their popularity among certain design circles, and what is perceived as a bias towards popular ideas and the downgrading of alternative views.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1109/HICSS.2008.422</identifier>
		<pages>160</pages>
		<title type="sharef:primaryTitle">Tag Clouds: Data Analysis Tool or Social Signaller?</title>
	</reference>
	<reference name="glu08b" src="bibtex:inproceedings" src-info="bibtex:line-17042" type="sharef:inproceedings" crossref="hicss41">
		<names type="sharef:author">
			<person>
				<givenname>Robert J.</givenname>
				<surname>Glushko</surname>
			</person>
			<person>
				<givenname>Lindsay</givenname>
				<surname>Tabas</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Service management and design has thus far primarily focused on the interactions between employees and customers. This perspective holds that the quality of the "service experience" is determined by the customer during this final "service encounter" that takes place in the "front stage." This emphasis discounts the contribution of the activities in the "back stage" of the service value chain where materials or information needed by the front stage are processed.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1109/HICSS.2008.77</identifier>
		<pages>106</pages>
		<title type="sharef:primaryTitle">Bridging the "Front Stage" and "Back Stage" in Service System Design</title>
	</reference>
	<reference name="hicss41" src="bibtex:proceedings" src-info="bibtex:line-17051" type="sharef:proceedings">
		<date value="2008-01"/>
		<address type="sharef:placePublished">Big Island, Hawaii</address>
		<field type="bibtex:index">HICSS-41</field>
		<publisher>IEEE Computer Society Press</publisher>
		<title type="sharef:primaryTitle">41st Hawaii International Conference on System Sciences</title>
		<identifier type="sharef:uri" resourceType="text/html">http://www.informatik.uni-trier.de/~ley/db/conf/hicss/hicss2008.html</identifier>
	</reference>
	<reference name="hei09" src="bibtex:inproceedings" src-info="bibtex:line-17066" type="sharef:inproceedings" crossref="hicss42">
		<names type="sharef:author">
			<person>
				<givenname>Andreas</givenname>
				<surname>Heil</surname>
			</person>
			<person>
				<givenname>Martin</givenname>
				<surname>Gaedke</surname>
			</person>
			<person>
				<givenname>Johannes</givenname>
				<surname>Meinecke</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Over the last years, the need to interconnect businesses has significantly affected the Web. The Web has moved constantly from a static source of documents to a dynamic platform for distributed applications. The communication infrastructure of the Web links together applications, e.g. by exposing functionality through Web services in different architectural styles. The current strife between SOA and REST leads one to the issue which approach to choose. Supported by a formal model, we show an integrative way to incorporate service orientation and resource orientation in federated systems as a foundation for future agreements rather than a separation of the approaches.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1109/HICSS.2009.826</identifier>
		<title type="sharef:primaryTitle">Modeling Resources in a Service-Oriented World</title>
	</reference>
	<reference name="hicss42" src="bibtex:proceedings" src-info="bibtex:line-17074" type="sharef:proceedings">
		<date value="2009-01"/>
		<address type="sharef:placePublished">Big Island, Hawaii</address>
		<field type="bibtex:index">HICSS-42</field>
		<publisher>IEEE Computer Society Press</publisher>
		<title type="sharef:primaryTitle">42nd Hawaii International Conference on System Sciences</title>
		<identifier type="sharef:uri" resourceType="text/html">http://www.informatik.uni-trier.de/~ley/db/conf/hicss/hicss2009.html</identifier>
	</reference>
	<reference name="ber03d" src="bibtex:inproceedings" src-info="bibtex:line-17089" type="sharef:inproceedings" crossref="cidr2003">
		<names type="sharef:author">
			<person>
				<givenname>Philip A.</givenname>
				<surname>Bernstein</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Model management is a new approach to meta data management that offers a higher level programming interface than current techniques. The main abstractions are models (e.g., schemas, interface definitions) and mappings between models. It treats these abstractions as bulk objects and offers such operators as Match, Merge, Diff, Compose, Apply, and ModelGen. This paper extends earlier treatments of these operators and applies them to three classical meta data management problems: schema integration, schema evolution, and round-trip engineering.</p>
			</richtext>
		</abstract>
		<title type="sharef:primaryTitle">Applying Model Management to Classical Meta Data Problems</title>
		<identifier type="sharef:uri" resourceType="application/pdf">http://www.research.microsoft.com/~philbe/PBernsteinCIDR12ext.pdf</identifier>
		<identifier type="sharef:uri" resourceType="application/pdf">http://www-db.cs.wisc.edu/cidr2003/program/p19.pdf</identifier>
	</reference>
	<reference name="cidr2003" src="bibtex:proceedings" src-info="bibtex:line-17098" type="sharef:proceedings">
		<date value="2003-01"/>
		<address type="sharef:placePublished">Asilomar, California</address>
		<field type="bibtex:index">CIDR 2003</field>
		<title type="sharef:primaryTitle">First Biennial Conference on Innovative Data Systems Research</title>
		<identifier type="sharef:uri" resourceType="text/html">http://www.informatik.uni-trier.de/~ley/db/conf/cidr/cidr2003.html</identifier>
		<identifier type="sharef:uri">http://www.cidrdb.org/cidr2003/</identifier>
	</reference>
	<reference name="arm09" src="bibtex:inproceedings" src-info="bibtex:line-17113" type="sharef:inproceedings" crossref="cidr2009">
		<names type="sharef:author">
			<person>
				<givenname>Michael</givenname>
				<surname>Armbrust</surname>
			</person>
			<person>
				<givenname>Armando</givenname>
				<surname>Fox</surname>
			</person>
			<person>
				<givenname>David A.</givenname>
				<surname>Patterson</surname>
			</person>
			<person>
				<givenname>Nick</givenname>
				<surname>Lanham</surname>
			</person>
			<person>
				<givenname>Beth</givenname>
				<surname>Trushkowsky</surname>
			</person>
			<person>
				<givenname>Jesse</givenname>
				<surname>Trutna</surname>
			</person>
			<person>
				<givenname>Haruki</givenname>
				<surname>Oh</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Collaborative web applications such as Facebook, Flickr and Yelp present new challenges for storing and querying large amounts of data. As users and developers are focused more on performance than single copy consistency or the ability to perform ad-hoc queries, there exists an opportunity for a highly-scalable system tailored specifically for relaxed consistency and pre-computed queries. The Web 2.0 development model demands the ability to both rapidly deploy new features and automatically scale with the number of users. There have been many successful distributed key-value stores, but so far none provide as rich a query language as SQL.We propose a new architecture, SCADS, that allows the developer to declaratively state application specific consistency requirements, takes advantage of utility computing to provide cost effective scale-up and scale-down, and will use machine learning models to introspectively anticipate performance problems and predict the resource requirements of new queries before execution.</p>
			</richtext>
		</abstract>
		<title type="sharef:primaryTitle">SCADS: Scale-Independent Storage for Social Computing Applications</title>
		<identifier type="sharef:uri" resourceType="application/pdf">http://www-db.cs.wisc.edu/cidr/cidr2009/Paper_86.pdf</identifier>
	</reference>
	<reference name="cidr2009" src="bibtex:proceedings" src-info="bibtex:line-17121" type="sharef:proceedings">
		<date value="2009-01"/>
		<address type="sharef:placePublished">Asilomar, California</address>
		<field type="bibtex:index">CIDR 2009</field>
		<title type="sharef:primaryTitle">Fourth Biennial Conference on Innovative Data Systems Research</title>
		<identifier type="sharef:uri" resourceType="text/html">http://www.informatik.uni-trier.de/~ley/db/conf/cidr/cidr2009.html</identifier>
		<identifier type="sharef:uri">http://www.cidrdb.org/cidr2009/</identifier>
	</reference>
	<reference name="low01" src="bibtex:inproceedings" src-info="bibtex:line-17136" type="sharef:inproceedings" crossref="openpub01">
		<names type="sharef:author">
			<person>
				<givenname>David</givenname>
				<surname>Lowe</surname>
			</person>
			<person>
				<givenname>Erik</givenname>
				<surname>Wilde</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Although the Web has continuously grown and evolved since its introduction in 1989, the technical foundations have remained relatively unchanged. Of the basic technologies, URLs and HTTP has remained stable for some time now, and only HTML has changed more frequently. However, the introduction of XML has heralded a substantial change in the way in which content can be managed. One of the most significant of these changes is with respect to the greatly enhanced model for linking functionality that is enabled by the emerging XLink and XPointer standards. These standards have the capacity to fundamentally change the way in which we utilise the Web, especially with respect to the way in which users interact with information. In this paper, we will discuss some of the richer linking functionality that XLink and XPointer enable — particularly with respect to aspects such as content transclusion, multiple source and destination links, generic linking, and the use of linkbases to add links into content over which the author has no control. The discussions will be illustrated with example XLink code fragments, and will emphasise the particular uses to which these linking concepts can be put.</p>
			</richtext>
		</abstract>
		<title type="sharef:primaryTitle">Improving Web Linking Using XLink</title>
		<field type="bibtex:topic">xlink[0.8] xpointer[0.8]</field>
		<identifier type="sharef:uri">http://dret.net/netdret/publications#low01</identifier>
		<identifier type="sharef:uri" resourceType="application/pdf">http://www.binarything.com/binarything/openpublish/DavidLowe1.pdf</identifier>
	</reference>
	<reference name="openpub01" src="bibtex:proceedings" src-info="bibtex:line-17146" type="sharef:proceedings">
		<date value="2001-07"/>
		<address type="sharef:placePublished">Sydney, Australia</address>
		<field type="bibtex:index">Open Publish 2001</field>
		<title type="sharef:primaryTitle">Open Publish 2001</title>
	</reference>
	<reference name="wil06l" src="bibtex:inproceedings" src-info="bibtex:line-17159" type="sharef:inproceedings" crossref="elpub2006">
		<names type="sharef:author">
			<person>
				<givenname>Erik</givenname>
				<surname>Wilde</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>XML as the most successful data representation format makes it easy to start working with structured data because of the simplicity of XML documents and DTDs, and because of the general availability of tools. This paper first describes the origin and features of XML as a markup language. In a second part, the question of how to use the features provided by XML for structuring content is addressed. Data modeling for electronic publishing and document engineering is an research field with many open issues, the most important open question being what to use as the modeling language for XML-based applications. While the paper does not provide a solution to the modeling language question, it provides guidelines for how to design schemas once the model has been defined.</p>
			</richtext>
		</abstract>
		<title type="sharef:primaryTitle">Structuring Content with XML</title>
		<field type="bibtex:topic">xml[0.8]</field>
		<identifier type="sharef:uri">http://dret.net/netdret/publications#wil06l</identifier>
	</reference>
	<reference name="elpub2006" src="bibtex:proceedings" src-info="bibtex:line-17168" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>Klaus</givenname>
				<surname>Kreulich</surname>
			</person>
			<person>
				<givenname>Peter</givenname>
				<surname>Linde</surname>
			</person>
			<person>
				<givenname>Stefan</givenname>
				<surname>Pletschacher</surname>
			</person>
			<person>
				<givenname>Arved</givenname>
				<surname>Hübler</surname>
			</person>
		</names>
		<date value="2006-06"/>
		<address type="sharef:placePublished">Bansko, Bulgaria</address>
		<field type="bibtex:index">ElPub 2006</field>
		<identifier type="sharef:isbn">954-16-0040-9</identifier>
		<title type="sharef:primaryTitle">Supplement to the 10th International Conference on Electronic Publishing</title>
		<identifier type="sharef:uri">http://info.tuwien.ac.at/elpub2006/</identifier>
	</reference>
	<reference name="sam93b" src="bibtex:inproceedings" src-info="bibtex:line-17184" type="sharef:inproceedings" crossref="infocom93">
		<names type="sharef:author">
			<person>
				<givenname>Michael</givenname>
				<surname>Sample</surname>
			</person>
			<person>
				<givenname>Gerald W.</givenname>
				<surname>Neufeld</surname>
			</person>
		</names>
		<field type="bibtex:index">snacc</field>
		<pages>1144-1153</pages>
		<title type="sharef:primaryTitle">Implementing Efficient Encoders and Decoders For Network Data Representations</title>
		<field type="bibtex:topic">asn1[0.9]</field>
	</reference>
	<reference name="infocom93" src="bibtex:proceedings" src-info="bibtex:line-17193" type="sharef:proceedings">
		<date value="1993"/>
		<address type="sharef:placePublished">San Francisco, California</address>
		<field type="bibtex:index">INFOCOM '93</field>
		<identifier type="sharef:isbn">0-8186-3582-7</identifier>
		<publisher>IEEE Computer Society Press</publisher>
		<title type="sharef:primaryTitle">IEEE INFOCOM '93 Conference on Computer Communications</title>
	</reference>
	<reference name="mit94" src="bibtex:inproceedings" src-info="bibtex:line-17207" type="sharef:inproceedings" crossref="infocom94">
		<names type="sharef:author">
			<person>
				<givenname>Danny J.</givenname>
				<surname>Mitzel</surname>
			</person>
			<person>
				<givenname>Deborah</givenname>
				<surname>Estrin</surname>
			</person>
			<person>
				<givenname>Scott</givenname>
				<surname>Shenker</surname>
			</person>
			<person>
				<givenname>Lixia</givenname>
				<surname>Zhang</surname>
			</person>
		</names>
		<field type="bibtex:index">ST-II, RSVP</field>
		<pages>716-725</pages>
		<title type="sharef:primaryTitle">An Architectural Comparison of ST-II and RSVP</title>
	</reference>
	<reference name="infocom94" src="bibtex:proceedings" src-info="bibtex:line-17215" type="sharef:proceedings">
		<date value="1994"/>
		<address type="sharef:placePublished">Toronto, Canada</address>
		<field type="bibtex:index">INFOCOM '94</field>
		<identifier type="sharef:isbn">0-8186-5570-4</identifier>
		<publisher>IEEE Computer Society Press</publisher>
		<title type="sharef:primaryTitle">Networking for Global Communications — IEEE INFOCOM '94 Conference on Computer Communications</title>
	</reference>
	<reference name="ele95" src="bibtex:inproceedings" src-info="bibtex:line-17229" type="sharef:inproceedings" crossref="infocom95">
		<names type="sharef:author">
			<person>
				<givenname>Alexandros</givenname>
				<surname>Eleftheriadis</surname>
			</person>
			<person>
				<givenname>Sassan</givenname>
				<surname>Pejhan</surname>
			</person>
			<person>
				<givenname>Dimitris</givenname>
				<surname>Anastassiou</surname>
			</person>
		</names>
		<field type="bibtex:index">multicast, address management</field>
		<pages>386-393</pages>
		<title type="sharef:primaryTitle">Address Management and Connection Control for Multicast Communication Applications</title>
	</reference>
	<reference name="infocom95" src="bibtex:proceedings" src-info="bibtex:line-17237" type="sharef:proceedings">
		<date value="1995"/>
		<address type="sharef:placePublished">Boston, Massachusetts</address>
		<field type="bibtex:index">INFOCOM '95</field>
		<identifier type="sharef:isbn">0-8186-6990-X</identifier>
		<publisher>IEEE Computer Society Press</publisher>
		<title type="sharef:primaryTitle">Bringing Information to People — IEEE INFOCOM '95 Conference on Computer Communications</title>
	</reference>
	<reference name="mah97" src="bibtex:inproceedings" src-info="bibtex:line-17251" type="sharef:inproceedings" crossref="infocom97">
		<names type="sharef:author">
			<person>
				<givenname>Bruce A.</givenname>
				<surname>Mah</surname>
			</person>
		</names>
		<pages>593-601</pages>
		<title type="sharef:primaryTitle">Techniques for Developing and Measuring High-Performance Web Servers over High Speed Networks</title>
		<field type="bibtex:topic">httpserver[0.9] http[0.7]</field>
	</reference>
	<reference name="infocom97" src="bibtex:proceedings" src-info="bibtex:line-17259" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>Miki</givenname>
				<surname>Yamamoto</surname>
			</person>
			<person>
				<givenname>Joseph</givenname>
				<surname>Bannister</surname>
			</person>
		</names>
		<date value="1997-04"/>
		<address type="sharef:placePublished">Kobe, Japan</address>
		<field type="bibtex:index">INFOCOM '97</field>
		<publisher>IEEE Computer Society Press</publisher>
		<title type="sharef:primaryTitle">IEEE INFOCOM '97 Conference on Computer Communications</title>
	</reference>
	<reference name="cro98" src="bibtex:inproceedings" src-info="bibtex:line-17274" type="sharef:inproceedings" crossref="infocom98">
		<names type="sharef:author">
			<person>
				<givenname>Mark</givenname>
				<surname>Crovella</surname>
			</person>
			<person>
				<givenname>Paul</givenname>
				<surname>Barford</surname>
			</person>
		</names>
		<field type="bibtex:index">WWW, prefetching</field>
		<pages>1232-1239</pages>
		<title type="sharef:primaryTitle">The Network Effects of Prefetching</title>
	</reference>
	<reference name="jhu98" src="bibtex:inproceedings" src-info="bibtex:line-17282" type="sharef:inproceedings" crossref="infocom98">
		<names type="sharef:author">
			<person>
				<givenname>James C.</givenname>
				<surname>Hu</surname>
			</person>
			<person>
				<givenname>Sumedh</givenname>
				<surname>Mungee</surname>
			</person>
			<person>
				<givenname>Douglas C.</givenname>
				<surname>Schmidt</surname>
			</person>
		</names>
		<field type="bibtex:index">WWW, HTTP, server</field>
		<pages>1222-1231</pages>
		<title type="sharef:primaryTitle">Techniques for Developing and Measuring High-Performance Web Servers over High Speed Networks</title>
	</reference>
	<reference name="infocom98" src="bibtex:proceedings" src-info="bibtex:line-17290" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>Abhijit K.</givenname>
				<surname>Choudhury</surname>
			</person>
		</names>
		<date value="1998-03"/>
		<address type="sharef:placePublished">San Francisco, California</address>
		<field type="bibtex:index">INFOCOM '98</field>
		<publisher>IEEE Computer Society Press</publisher>
		<title type="sharef:primaryTitle">IEEE INFOCOM '98 Conference on Computer Communications</title>
	</reference>
	<reference name="fel99" src="bibtex:inproceedings" src-info="bibtex:line-17305" type="sharef:inproceedings" crossref="infocom99">
		<names type="sharef:author">
			<person>
				<givenname>Anja</givenname>
				<surname>Feldmann</surname>
			</person>
			<person>
				<givenname>Ramon</givenname>
				<surname>Caceres</surname>
			</person>
			<person>
				<givenname>Fred</givenname>
				<surname>Douglis</surname>
			</person>
			<person>
				<givenname>Gideon</givenname>
				<surname>Glass</surname>
			</person>
			<person>
				<givenname>Michael</givenname>
				<surname>Rabinovich</surname>
			</person>
		</names>
		<field type="bibtex:index">WWW</field>
		<pages>107-116</pages>
		<title type="sharef:primaryTitle">Performance of Web Proxy Caching in Heterogeneous Bandwidth Environments</title>
	</reference>
	<reference name="infocom99" src="bibtex:proceedings" src-info="bibtex:line-17313" type="sharef:proceedings">
		<date value="1999-03"/>
		<address type="sharef:placePublished">New York, NY</address>
		<field type="bibtex:index">INFOCOM '99</field>
		<publisher>IEEE Computer Society Press</publisher>
		<title type="sharef:primaryTitle">IEEE INFOCOM '99 Conference on Computer Communications</title>
	</reference>
	<reference name="san93c" src="bibtex:inproceedings" src-info="bibtex:line-17327" type="sharef:inproceedings" crossref="dcs93">
		<names type="sharef:author">
			<person>
				<givenname>Adelino</givenname>
				<surname>Santos</surname>
			</person>
			<person>
				<givenname>A.</givenname>
				<surname>Marcos</surname>
			</person>
		</names>
		<field type="bibtex:index">CoMEdiA, cooperative multimedia systems, distributed architectures, distributed algorithms, collaborative editing</field>
		<pages>2-7</pages>
		<title type="sharef:primaryTitle">An Algorithm and Architecture to Support Cooperative Multimedia Editing</title>
	</reference>
	<reference name="der93" src="bibtex:inproceedings" src-info="bibtex:line-17335" type="sharef:inproceedings" crossref="dcs93">
		<names type="sharef:author">
			<person>
				<givenname>Gabriel</givenname>
				<surname>Dermler</surname>
			</person>
			<person>
				<givenname>Thomas</givenname>
				<surname>Gutekunst</surname>
			</person>
			<person>
				<givenname>Bernhard</givenname>
				<surname>Plattner</surname>
			</person>
			<person>
				<givenname>Edgar</givenname>
				<surname>Ostrowski</surname>
			</person>
			<person>
				<givenname>Frank</givenname>
				<surname>Ruge</surname>
			</person>
			<person>
				<givenname>Michael</givenname>
				<surname>Weber</surname>
			</person>
		</names>
		<field type="bibtex:index">JVTOS, CIO</field>
		<pages>8-15</pages>
		<title type="sharef:primaryTitle">Constructing a Distributed Multimedia Joint Viewing and Tele-Operation Service for Heterogeneous Workstation Environments</title>
	</reference>
	<reference name="ver93" src="bibtex:inproceedings" src-info="bibtex:line-17343" type="sharef:inproceedings" crossref="dcs93">
		<names type="sharef:author">
			<person>
				<givenname>Paulo</givenname>
				<surname>Veríssimo</surname>
			</person>
			<person>
				<givenname>Werner</givenname>
				<surname>Vogels</surname>
			</person>
		</names>
		<field type="bibtex:index">group orientation</field>
		<pages>119-127</pages>
		<title type="sharef:primaryTitle">The Changing Face of Technology in Distributed Systems</title>
	</reference>
	<reference name="ant93" src="bibtex:inproceedings" src-info="bibtex:line-17351" type="sharef:inproceedings" crossref="dcs93">
		<names type="sharef:author">
			<person>
				<givenname>Pedro</givenname>
				<surname>Antes</surname>
			</person>
			<person>
				<givenname>Nuno</givenname>
				<surname>Guimaraes</surname>
			</person>
		</names>
		<field type="bibtex:index">xAMp, MBus, MUI, ConversationBuilder</field>
		<pages>143-149</pages>
		<title type="sharef:primaryTitle">A Distributed Model and Architecture for Interactive Cooperation</title>
	</reference>
	<reference name="szy93" src="bibtex:inproceedings" src-info="bibtex:line-17359" type="sharef:inproceedings" crossref="dcs93">
		<names type="sharef:author">
			<person>
				<givenname>Clemens</givenname>
				<surname>Szyperski</surname>
			</person>
			<person>
				<givenname>Giorgio</givenname>
				<surname>Ventre</surname>
			</person>
		</names>
		<pages>150-156</pages>
		<title type="sharef:primaryTitle">Efficient Group Communication with Guaranteed Quality of Service</title>
	</reference>
	<reference name="kam93" src="bibtex:inproceedings" src-info="bibtex:line-17366" type="sharef:inproceedings" crossref="dcs93">
		<names type="sharef:author">
			<person>
				<givenname>Nabil</givenname>
				<surname>Kamel</surname>
			</person>
		</names>
		<field type="bibtex:index">MERMAID</field>
		<pages>157-163</pages>
		<title type="sharef:primaryTitle">An Integrated Approach to Shared Synchronous Groupware Workspaces</title>
	</reference>
	<reference name="dcs93" src="bibtex:proceedings" src-info="bibtex:line-17374" type="sharef:proceedings">
		<date value="1993"/>
		<address type="sharef:placePublished">Lisbon, Portugal</address>
		<field type="bibtex:index">DCS '93</field>
		<identifier type="sharef:isbn">0-8186-4430-3</identifier>
		<field type="bibtex:key">Fourth Workshop on Future Trends of Distributed Computing Systems</field>
		<publisher>IEEE Computer Society Press</publisher>
		<title type="sharef:primaryTitle">Fourth Workshop on Future Trends of Distributed Computing Systems</title>
	</reference>
	<reference name="bog88" src="bibtex:inproceedings" src-info="bibtex:line-17389" type="sharef:inproceedings" crossref="eut88">
		<names type="sharef:author">
			<person>
				<givenname>Manfred</givenname>
				<surname>Bogen</surname>
			</person>
			<person>
				<givenname>Karl-Heinz</givenname>
				<surname>Weiss</surname>
			</person>
		</names>
		<pages>111-128</pages>
		<title type="sharef:primaryTitle">Group Co-ordination in a Distributed Environment</title>
	</reference>
	<reference name="eut88" src="bibtex:proceedings" src-info="bibtex:line-17396" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>Rolf</givenname>
				<surname>Speth</surname>
			</person>
		</names>
		<date value="1988"/>
		<address type="sharef:placePublished">Vienna, Austria</address>
		<field type="bibtex:index">EUTECO '88</field>
		<identifier type="sharef:isbn">0-444-70428-0</identifier>
		<publisher>North-Holland</publisher>
		<title type="sharef:primaryTitle">Research into Networks and Distributed Applications: EUTECO'88 Conference</title>
	</reference>
	<reference name="ell89" src="bibtex:inproceedings" src-info="bibtex:line-17411" type="sharef:inproceedings" crossref="hci89">
		<names type="sharef:author">
			<person>
				<givenname>Clarence A.</givenname>
				<surname>Ellis</surname>
			</person>
			<person>
				<givenname>Simon J.</givenname>
				<surname>Gibbs</surname>
			</person>
			<person>
				<givenname>Gail L.</givenname>
				<surname>Rein</surname>
			</person>
		</names>
		<field type="bibtex:index">GROVE, groupware, collaborative editing</field>
		<pages>13-28</pages>
		<title type="sharef:primaryTitle">Design and Use of a Group Editor</title>
	</reference>
	<reference name="hci89" src="bibtex:proceedings" src-info="bibtex:line-17419" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>G.</givenname>
				<surname>Cockton</surname>
			</person>
		</names>
		<date value="1989"/>
		<address type="sharef:placePublished">Napa Valley, California</address>
		<identifier type="sharef:isbn">0-444-88342-8</identifier>
		<publisher>Elsevier</publisher>
		<title type="sharef:primaryTitle">IFIP TC2/WG2.7 Working Conference on Engineering for Human-Computer Interaction</title>
	</reference>
	<reference name="pri87" src="bibtex:inproceedings" src-info="bibtex:line-17433" type="sharef:inproceedings" crossref="mhs87">
		<names type="sharef:author">
			<person>
				<givenname>Wolfgang</givenname>
				<surname>Prinz</surname>
			</person>
			<person>
				<givenname>Rolf</givenname>
				<surname>Speth</surname>
			</person>
		</names>
		<field type="bibtex:index">AMIGO</field>
		<pages>207-223</pages>
		<title type="sharef:primaryTitle">Group Communication and Related Aspects in Office Automation</title>
	</reference>
	<reference name="mhs87" src="bibtex:proceedings" src-info="bibtex:line-17441" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>Rolf</givenname>
				<surname>Speth</surname>
			</person>
		</names>
		<date value="1987"/>
		<address type="sharef:placePublished">Munich, Germany</address>
		<identifier type="sharef:isbn">0-444-70402-7</identifier>
		<publisher>North-Holland</publisher>
		<title type="sharef:primaryTitle">IFIP TC6/WG6.5 Working Conference on Message Handling Systems</title>
	</reference>
	<reference name="dep91a" src="bibtex:inproceedings" src-info="bibtex:line-17455" type="sharef:inproceedings" crossref="glo91">
		<names type="sharef:author">
			<person>
				<givenname>Flavio</givenname>
				<surname>DePaoli</surname>
			</person>
			<person>
				<givenname>Francesco</givenname>
				<surname>Tisato</surname>
			</person>
		</names>
		<field type="bibtex:index">Coordinator</field>
		<pages>2049-2053</pages>
		<title type="sharef:primaryTitle">Coordinator: A Basic Building Block for Multimedia Conferencing Systems</title>
	</reference>
	<reference name="heb91" src="bibtex:inproceedings" src-info="bibtex:line-17463" type="sharef:inproceedings" crossref="glo91">
		<names type="sharef:author">
			<person>
				<givenname>P.</givenname>
				<surname>Hebrard</surname>
			</person>
			<person>
				<givenname>A.</givenname>
				<surname>Karmouch</surname>
			</person>
			<person>
				<givenname>N. D.</givenname>
				<surname>Georganas</surname>
			</person>
		</names>
		<field type="bibtex:index">Coordinator</field>
		<pages>2054-2058</pages>
		<title type="sharef:primaryTitle">Management in Multimedia Cooperative Applications</title>
	</reference>
	<reference name="glo91" src="bibtex:proceedings" src-info="bibtex:line-17471" type="sharef:proceedings">
		<date value="1991"/>
		<address type="sharef:placePublished">Phoenix, Arizona</address>
		<field type="bibtex:index">GLOBECOM '91</field>
		<identifier type="sharef:isbn">0879426977</identifier>
		<publisher>IEEE Computer Society Press</publisher>
		<title type="sharef:primaryTitle">GLOBECOM'91 Conference</title>
	</reference>
	<reference name="kic97" src="bibtex:inproceedings" src-info="bibtex:line-17485" type="sharef:inproceedings" crossref="ecoop97">
		<names type="sharef:author">
			<person>
				<givenname>Gregor</givenname>
				<surname>Kiczales</surname>
			</person>
			<person>
				<givenname>John</givenname>
				<surname>Lamping</surname>
			</person>
			<person>
				<givenname>Anurag</givenname>
				<surname>Mendhekar</surname>
			</person>
			<person>
				<givenname>Chris</givenname>
				<surname>Maeda</surname>
			</person>
			<person>
				<givenname>Cristina Videira</givenname>
				<surname>Lopes</surname>
			</person>
			<person>
				<givenname>Jean-Marc</givenname>
				<surname>Loingtier</surname>
			</person>
			<person>
				<givenname>John</givenname>
				<surname>Irwin</surname>
			</person>
		</names>
		<pages>220-242</pages>
		<title type="sharef:primaryTitle">Aspect-Oriented Programming</title>
		<field type="bibtex:topic">aop[1]</field>
		<identifier type="sharef:uri" resourceType="application/pdf">http://www.cs.ubc.ca/~gregor/kiczales-ECOOP1997-AOP.pdf</identifier>
	</reference>
	<reference name="ecoop97" src="bibtex:proceedings" src-info="bibtex:line-17494" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>Mehmet</givenname>
				<surname>Aksit</surname>
			</person>
			<person>
				<givenname>Satoshi</givenname>
				<surname>Matsuoka</surname>
			</person>
		</names>
		<date value="1997-06"/>
		<address type="sharef:placePublished">Jyväskylä, Finland</address>
		<field type="bibtex:index">ECOOP 97</field>
		<identifier type="sharef:isbn">3540630899</identifier>
		<publisher>Springer-Verlag</publisher>
		<title type="sharef:seriesTitle">Lecture Notes in Computer Science</title>
		<title type="sharef:primaryTitle">11th European Conference on Object-Oriented Programming</title>
		<field type="bibtex:topic">oop[0.8]</field>
		<identifier type="sharef:uri" resourceType="text/html">http://www.informatik.uni-trier.de/~ley/db/conf/ecoop/ecoop97.html</identifier>
		<volume>1241</volume>
	</reference>
	<reference name="jun00" src="bibtex:inproceedings" src-info="bibtex:line-17514" type="sharef:inproceedings" crossref="ecoopws00">
		<names type="sharef:author">
			<person>
				<givenname>Matthias</givenname>
				<surname>Jung</surname>
			</person>
			<person>
				<givenname>Ernst W.</givenname>
				<surname>Biersack</surname>
			</person>
		</names>
		<title type="sharef:primaryTitle">How Layering Protocol Software Violates Separation of Concerns</title>
		<field type="bibtex:topic">soc[0.9]</field>
		<identifier type="sharef:uri" resourceType="application/pdf">http://trese.cs.utwente.nl/Workshops/adc2000/papers/Jung.pdf</identifier>
	</reference>
	<reference name="ecoopws00" src="bibtex:proceedings" src-info="bibtex:line-17522" type="sharef:proceedings">
		<date value="2000-06"/>
		<address type="sharef:placePublished">Cannes, France</address>
		<title type="sharef:primaryTitle">ECOOP 2000 Workshop on Aspects and Dimensions of Concerns</title>
		<identifier type="sharef:uri" resourceType="text/html">http://ecoop2000.unice.fr/Program/Technical/Workshops/w21.html</identifier>
		<identifier type="sharef:uri">http://trese.cs.utwente.nl/adc2000/</identifier>
	</reference>
	<reference name="che92" src="bibtex:inproceedings" src-info="bibtex:line-17536" type="sharef:inproceedings" crossref="glo92">
		<names type="sharef:author">
			<person>
				<givenname>Mon-Song</givenname>
				<surname>Chen</surname>
			</person>
			<person>
				<givenname>Harrick M.</givenname>
				<surname>Vin</surname>
			</person>
			<person>
				<givenname>Tsipora P.</givenname>
				<surname>Barzilai</surname>
			</person>
		</names>
		<field type="bibtex:index">DiCE, multimedia communications</field>
		<pages>213-219</pages>
		<title type="sharef:primaryTitle">Designing a Distributed Collaborative Environment</title>
	</reference>
	<reference name="che92b" src="bibtex:inproceedings" src-info="bibtex:line-17544" type="sharef:inproceedings" crossref="glo92">
		<names type="sharef:author">
			<person>
				<givenname>Mon-Song</givenname>
				<surname>Chen</surname>
			</person>
			<person>
				<givenname>Zon-Yin</givenname>
				<surname>Shae</surname>
			</person>
			<person>
				<givenname>Dilip D.</givenname>
				<surname>Kandlur</surname>
			</person>
			<person>
				<givenname>Tsipora P.</givenname>
				<surname>Barzilai</surname>
			</person>
			<person>
				<givenname>Harrick M.</givenname>
				<surname>Vin</surname>
			</person>
		</names>
		<field type="bibtex:index">VAS, MMVA, MMT</field>
		<pages>739-746</pages>
		<title type="sharef:primaryTitle">A Multimedia Desktop Collaboration System</title>
	</reference>
	<reference name="glo92" src="bibtex:proceedings" src-info="bibtex:line-17552" type="sharef:proceedings">
		<date value="1992-12"/>
		<address type="sharef:placePublished">Orlando, Florida</address>
		<field type="bibtex:index">GLOBECOM '92</field>
		<identifier type="sharef:isbn">0-7803-0608-2</identifier>
		<publisher>IEEE Computer Society Press</publisher>
		<title type="sharef:primaryTitle">GLOBECOM'92 Conference</title>
	</reference>
	<reference name="kar04" src="bibtex:inproceedings" src-info="bibtex:line-17567" type="sharef:inproceedings" crossref="glo04">
		<names type="sharef:author">
			<person>
				<givenname>Thomas</givenname>
				<surname>Karagiannis</surname>
			</person>
			<person>
				<givenname>Andre</givenname>
				<surname>Broido</surname>
			</person>
			<person>
				<givenname>Nevil</givenname>
				<surname>Brownlee</surname>
			</person>
			<person>
				<givenname>Kimberly C.</givenname>
				<surname>Claffy</surname>
			</person>
			<person>
				<givenname>Michalis</givenname>
				<surname>Faloutsos</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Recent reports in the popular media suggest a significant decrease in peer-to-peer (P2P) file-sharing traffic, attributed to the public's response to legal threats. Have we reached the end of the P2P revolution? In pursuit of legitimate data to verify this hypothesis, we embark on a more accurate measurement effort of P2P traffic at the link level. In contrast to previous efforts we introduce two novel elements in our methodology. First, we measure traffic of all known popular P2P protocols. Second, we go beyond the "known port" limitation by reverse engineering the protocols and identifying characteristic strings in the payload. We find that, if measured accurately, P2P traffic has never declined; indeed we have never seen the proportion of p2p traffic decrease over time (any change is an increase) in any of our data sources</p>
			</richtext>
		</abstract>
		<title type="sharef:primaryTitle">Is P2P dying or just hiding?</title>
		<field type="bibtex:topic">p2p[0.7]</field>
		<identifier type="sharef:uri">http://www.caida.org/outreach/papers/2004/p2p-dying/</identifier>
	</reference>
	<reference name="glo04" src="bibtex:proceedings" src-info="bibtex:line-17576" type="sharef:proceedings">
		<date value="2004-11"/>
		<address type="sharef:placePublished">Dallas, Texas</address>
		<field type="bibtex:index">GLOBECOM 2004</field>
		<publisher>IEEE Computer Society Press</publisher>
		<title type="sharef:primaryTitle">GLOBECOM 2004 Conference</title>
		<identifier type="sharef:uri">http://www.globecom2004.org/</identifier>
	</reference>
	<reference name="ban90" src="bibtex:inproceedings" src-info="bibtex:line-17591" type="sharef:inproceedings" crossref="uug90">
		<names type="sharef:author">
			<person>
				<givenname>Thomas</givenname>
				<surname>Bannon</surname>
			</person>
			<person>
				<givenname>Ivor</givenname>
				<surname>Page</surname>
			</person>
		</names>
		<field type="bibtex:index">distributed group specification, management service, distributed service, collaborative interaction, computer users, group membership</field>
		<pages>61-76</pages>
		<title type="sharef:primaryTitle">group: A Distributed Group Specification and Management Service</title>
	</reference>
	<reference name="uug90" src="bibtex:proceedings" src-info="bibtex:line-17599" type="sharef:proceedings">
		<date value="1990"/>
		<address type="sharef:placePublished">Buntingford, UK</address>
		<field type="bibtex:index">UKUUG '90</field>
		<identifier type="sharef:isbn">0-9513181-7-9</identifier>
		<publisher>UKUUG</publisher>
		<title type="sharef:primaryTitle">UNIX — The Legend Evolves. Summer 1990 UKUUG Conference</title>
	</reference>
	<reference name="kop89" src="bibtex:inproceedings" src-info="bibtex:line-17613" type="sharef:inproceedings" crossref="dca89">
		<names type="sharef:author">
			<person>
				<givenname>H.</givenname>
				<surname>Kopetz</surname>
			</person>
			<person>
				<givenname>G.</givenname>
				<surname>Grünsteidl</surname>
			</person>
			<person>
				<givenname>J.</givenname>
				<surname>Reisinger</surname>
			</person>
		</names>
		<field type="bibtex:index">membership protocol, atomic multicast, real-time, fault-tolerance, distributed systems</field>
		<pages>411-429</pages>
		<title type="sharef:primaryTitle">Fault-Tolerant Membership Service in a Synchronous Distributed Real-Time System</title>
	</reference>
	<reference name="dca89" src="bibtex:proceedings" src-info="bibtex:line-17621" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>Algirdas</givenname>
				<surname>Avižienis</surname>
			</person>
			<person>
				<givenname>Jean-Claude</givenname>
				<surname>Laprie</surname>
			</person>
		</names>
		<date value="1989"/>
		<address type="sharef:placePublished">Santa Barbara, California</address>
		<identifier type="sharef:isbn">3-211-82249-6</identifier>
		<publisher>Springer-Verlag</publisher>
		<title type="sharef:primaryTitle">IFIP WG10.4 International Working Conference on Dependable Computing for Critical Applications</title>
	</reference>
	<reference name="wil07j" src="bibtex:inproceedings" src-info="bibtex:line-17635" type="sharef:inproceedings" crossref="iri2007">
		<names type="sharef:author">
			<person>
				<givenname>Erik</givenname>
				<surname>Wilde</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Web 2.0 applications have become popular as drivers of new types of Web content, but they have also introduced a new level of interface design in Web development; they are focusing on richer interfaces, user-generated content, and better interworking of Web-based applications. The current foundations of the Web 2.0, however, are strictly imperative in nature, which makes it difficult to develop applications which are robust, interoperable, and backwards compatible. Using a declarative approach for Web 2.0 applications, this new wave of applications can be built on a more robust foundation which is more in line with the Web's style of using declarative methods whenever possible. We show a path how today's imperative Web 2.0 applications can be regarded as a testbed as well as a first implementation for a revised version of Web 2.0 technologies, which will be based on declarative markup rather than imperative code.</p>
			</richtext>
		</abstract>
		<pages>612-617</pages>
		<title type="sharef:primaryTitle">Declarative Web 2.0</title>
		<identifier type="sharef:uri">http://dret.net/netdret/publications#wil07j</identifier>
	</reference>
	<reference name="iri2007" src="bibtex:proceedings" src-info="bibtex:line-17644" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>Weide</givenname>
				<surname>Chang</surname>
			</person>
			<person>
				<givenname>James B. D.</givenname>
				<surname>Joshi</surname>
			</person>
		</names>
		<date value="2007-08"/>
		<address type="sharef:placePublished">Las Vegas, Nevada</address>
		<identifier type="sharef:isbn">1-4244-1499-7</identifier>
		<title type="sharef:primaryTitle">2007 IEEE International Conference on Information Reuse and Integration</title>
		<identifier type="sharef:uri">http://www.sis.pitt.edu/~iri07/</identifier>
		<identifier type="sharef:uri" resourceType="text/html">http://www.informatik.uni-trier.de/~ley/db/conf/iri/iri2007.html</identifier>
	</reference>
	<reference name="wil08i" src="bibtex:inproceedings" src-info="bibtex:line-17660" type="sharef:inproceedings" crossref="iri2008">
		<names type="sharef:author">
			<person>
				<givenname>Erik</givenname>
				<surname>Wilde</surname>
			</person>
			<person>
				<givenname>Yiming</givenname>
				<surname>Liu</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Much of the Web's success rests with its role in enabling information reuse and integration across various boundaries. Hyperlinked Web resources represent a rich information tapestry of content and context, instrumental in effective knowledge sharing and further knowledge development. However, the Web's simple linking model has become increasingly inadequate for effective content discovery and reuse. At the same time, rigorous but heavyweight solutions such as the Semantic Web have yet to garner critical mass in adoption. This paper analyzes the relative strengths and shortcomings of existing linked data approaches. It proposes a novel, lightweight architecture for the modeling, aggregation, retrieval, management, and sharing of contextual information for Web resources, based on established standards and designed to encourage more efficient and robust information reuse on the Web.</p>
			</richtext>
		</abstract>
		<title type="sharef:primaryTitle">Lightweight Linked Data</title>
		<identifier type="sharef:uri">http://dret.net/netdret/publications#wil08i</identifier>
	</reference>
	<reference name="iri2008" src="bibtex:proceedings" src-info="bibtex:line-17668" type="sharef:proceedings">
		<date value="2008-07"/>
		<address type="sharef:placePublished">Las Vegas, Nevada</address>
		<title type="sharef:primaryTitle">2008 IEEE International Conference on Information Reuse and Integration</title>
		<identifier type="sharef:uri">http://iri2008.cpsc.ucalgary.ca/</identifier>
		<identifier type="sharef:uri" resourceType="text/html">http://www.informatik.uni-trier.de/~ley/db/conf/iri/iri2008.html</identifier>
	</reference>
	<reference name="wil08l" src="bibtex:inproceedings" src-info="bibtex:line-17682" type="sharef:inproceedings" crossref="visions2008">
		<names type="sharef:author">
			<person>
				<givenname>Erik</givenname>
				<surname>Wilde</surname>
			</person>
			<person>
				<givenname>Martin</givenname>
				<surname>Gaedke</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>We propose "Web Engineering 2.0" to not focus anymore on "how to engineer for the Web", but "how to engineer the Web". Web Engineering has become one of the core disciplines for building Web-oriented applications. This paper proposes to reposition Web engineering to be more specific to what the Web is, by which we mean not only an interface technology, but an information system, into which Web-oriented applications have to be embedded. More traditional Web applications often are just user interfaces to data silos, whereas the last years have shown that well-designed Web-oriented applications can essentially start with no data, and derive all their value from being open and attracting users on a large scale. Such an approach to Web engineering not only leads to a more disciplined way of engineering the Web, it also allows computer science to better integrate the special properties of the Web, most importantly the loosely coupled nature of the Web, and the importance of the social systems driving the Web.</p>
			</richtext>
		</abstract>
		<title type="sharef:primaryTitle">Web Engineering Revisited</title>
		<identifier type="sharef:uri">http://dret.net/netdret/publications#wil08l</identifier>
		<identifier type="sharef:uri">http://www.bcs.org/server.php?show=ConWebDoc.22847</identifier>
	</reference>
	<reference name="visions2008" src="bibtex:proceedings" src-info="bibtex:line-17691" type="sharef:proceedings">
		<date value="2008-09"/>
		<address type="sharef:placePublished">London, UK</address>
		<title type="sharef:primaryTitle">2008 British Computer Society (BCS) Conference on Visions of Computer Science</title>
		<identifier type="sharef:uri">http://www.bcs.org/server.php?show=nav.9878</identifier>
	</reference>
	<reference name="sun07b" src="bibtex:inproceedings" src-info="bibtex:line-17704" type="sharef:inproceedings" crossref="wi2007">
		<names type="sharef:author">
			<person>
				<givenname>Yang</givenname>
				<surname>Sun</surname>
			</person>
			<person>
				<givenname>Ziming</givenname>
				<surname>Zhuang</surname>
			</person>
			<person>
				<givenname>Isaac G.</givenname>
				<surname>Councill</surname>
			</person>
			<person>
				<givenname>C. Lee</givenname>
				<surname>Giles</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Search engines largely rely on robots (i.e., crawlers or spiders) to collect information from the Web. Such crawling activities can be regulated from the server side by deploying the Robots Exclusion Protocol in a file called robots.txt. Ethical robots will follow the rules specified in robots.txt. Websites can explicitly specify an access preference for each robot by name. Such biases may lead to a "rich get richer" situation, in which a few popular search engines ultimately dominate the Web because they have preferred access to resources that are inaccessible to others. This issue is seldom addressed, although the robots.txt convention has become a de facto standard for robot regulation and search engines have become an indispensable tool for information access. We propose a metric to evaluate the degree of bias to which specific robots are subjected. We have investigated 7,593 websites covering education, government, news, and business domains, and collected 2,925 distinct robots.txt files. Results of content and statistical analysis of the data confirm that the robots of popular search engines and information portals, such as Google, Yahoo, and MSN, are generally favored by most of the websites we have sampled. The results also show a strong correlation between the search engine market share and the bias toward particular search engine robots.</p>
			</richtext>
		</abstract>
		<pages>149-155</pages>
		<title type="sharef:primaryTitle">Determining Bias to Search Engines from Robots.txt</title>
		<identifier type="sharef:uri" resourceType="application/pdf">http://botseer.ist.psu.edu/wi2007robotbias.pdf</identifier>
	</reference>
	<reference name="wi2007" src="bibtex:proceedings" src-info="bibtex:line-17713" type="sharef:proceedings">
		<date value="2007-11"/>
		<address type="sharef:placePublished">Silicon Valley, California</address>
		<identifier type="sharef:isbn">0-7695-3026-5</identifier>
		<title type="sharef:primaryTitle">2007 IEEE/WIC/ACM International Conference on Web Intelligence</title>
		<identifier type="sharef:uri" resourceType="text/html">http://www.sigmod.org/dblp/db/conf/webi/webi2007.html</identifier>
	</reference>
	<reference name="kop08" src="bibtex:inproceedings" src-info="bibtex:line-17727" type="sharef:inproceedings" crossref="wi2008">
		<names type="sharef:author">
			<person>
				<givenname>Jacek</givenname>
				<surname>Kopecký</surname>
			</person>
			<person>
				<givenname>Karthik</givenname>
				<surname>Gomadam</surname>
			</person>
			<person>
				<givenname>Tomas</givenname>
				<surname>Vitvar</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>The Web 2.0 wave brings, among other aspects, the Programmable Web: increasing numbers of Web sites provide machine-oriented APIs and Web services. However, most APIs are only described with text in HTML documents. The lack of machine-readable API descriptions affects the feasibility of tool support for developers who use these services. We propose a microformat called hRESTS (HTML for RESTful Services) for machine-readable descriptions of Web APIs, backed by a simple service model. The hRESTS microformat describes main aspects of services, such as operations, inputs and outputs. We also present two extensions of hRESTS: SA-REST, which captures the facets of public APIs important for mashup developers, and MicroWSMO, which provides support for semantic automation.</p>
			</richtext>
		</abstract>
		<pages>619-625</pages>
		<title type="sharef:primaryTitle">hRESTS: An HTML Microformat for Describing RESTful Web Services</title>
		<field type="bibtex:topic">hrests[1] sarest[1] wsmo[0.8] microwsmo[1]</field>
		<identifier type="sharef:uri" resourceType="application/pdf">http://www.vitvar.com/doc/WI2008-KopeckyGV.pdf</identifier>
	</reference>
	<reference name="wi2008" src="bibtex:proceedings" src-info="bibtex:line-17737" type="sharef:proceedings">
		<date value="2008-12"/>
		<address type="sharef:placePublished">Sydney, Australia</address>
		<identifier type="sharef:doi">10.1109/WIIAT.2008.469</identifier>
		<identifier type="sharef:isbn">978-0-7695-3496-1</identifier>
		<title type="sharef:primaryTitle">2008 IEEE/WIC/ACM International Conference on Web Intelligence</title>
		<identifier type="sharef:uri" resourceType="text/html">http://www.sigmod.org/dblp/db/conf/webi/webi2008.html</identifier>
	</reference>
	<reference name="sun08" src="bibtex:inproceedings" src-info="bibtex:line-17752" type="sharef:inproceedings" crossref="icwe2008">
		<names type="sharef:author">
			<person>
				<givenname>Yang</givenname>
				<surname>Sun</surname>
			</person>
			<person>
				<givenname>Isaac G.</givenname>
				<surname>Councill</surname>
			</person>
			<person>
				<givenname>C. Lee</givenname>
				<surname>Giles</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Robots.txt files are vital to the web since they are supposed to regulate what search engines can and cannot crawl. We present BotSeer, a Web-based information system and search tool that provides resources and services for researching Web robots and trends in Robot Exclusion Protocol deployment and adherence. BotSeer currently indexes and analyzes 2.2 million robots.txt files obtained from 13.2 million websites, as well as a large Web server log of real-world robot behavior and related analyses. BotSeer provides three major services including robots.txt searching, robot bias analysis, and robot-generated log analysis. BotSeer serves as a resource for studying the regulation and behavior of Web robots as well as a tool to inform the creation of effective robots.txt files and crawler implementations.</p>
			</richtext>
		</abstract>
		<title type="sharef:primaryTitle">BotSeer: An Automated Information System for Analyzing Web Robots</title>
		<identifier type="sharef:uri" resourceType="application/pdf">http://botseer.ist.psu.edu/sun-botseer.pdf</identifier>
	</reference>
	<reference name="icwe2008" src="bibtex:proceedings" src-info="bibtex:line-17760" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>Daniel</givenname>
				<surname>Schwabe</surname>
			</person>
			<person>
				<givenname>Francisco</givenname>
				<surname>Curbera</surname>
			</person>
			<person>
				<givenname>Paul</givenname>
				<surname>Dantzig</surname>
			</person>
		</names>
		<date value="2008-07"/>
		<address type="sharef:placePublished">Yorktown Heights, NY</address>
		<identifier type="sharef:isbn">978-0-7695-3261-5</identifier>
		<title type="sharef:primaryTitle">8th International Conference on Web Engineering</title>
		<identifier type="sharef:uri">http://icwe2008.webengineering.org/</identifier>
		<identifier type="sharef:uri" resourceType="text/html">http://www.informatik.uni-trier.de/~ley/db/conf/icwe/icwe2008.html</identifier>
	</reference>
	<reference name="wil09f" src="bibtex:inproceedings" src-info="bibtex:line-17776" type="sharef:inproceedings" crossref="icwe2009">
		<names type="sharef:author">
			<person>
				<givenname>Erik</givenname>
				<surname>Wilde</surname>
			</person>
			<person>
				<givenname>Anuradha</givenname>
				<surname>Roy</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Understanding the availability of site metadata on the Web is a foundation for any system or application that wants to work with the pages published by Web sites, and also wants to understand a Web site's structure. There is little information available about how much information Web sites make available about themselves, and this paper presents data addressing this question. Based on this analysis of available Web site metadata, it is easier for Web-oriented applications to be based on statistical analysis rather than assumptions when relying on Web site metadata. Our study of robots.txt files and sitemaps can be used as a starting point for Web-oriented applications wishing to work with Web site metadata.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1007/978-3-642-02818-2_25</identifier>
		<pages>300-314</pages>
		<title type="sharef:primaryTitle">Web Site Metadata</title>
		<identifier type="sharef:uri">http://dret.net/netdret/publications#wil09f</identifier>
		<identifier type="sharef:uri">http://www.springerlink.com/content/ap63560553261517/</identifier>
	</reference>
	<reference name="raz09" src="bibtex:inproceedings" src-info="bibtex:line-17787" type="sharef:inproceedings" crossref="icwe2009">
		<names type="sharef:author">
			<person>
				<givenname>Amir R.</givenname>
				<surname>Razavi</surname>
			</person>
			<person>
				<givenname>Alexandros</givenname>
				<surname>Marinos</surname>
			</person>
			<person>
				<givenname>Sotiris</givenname>
				<surname>Moschoyiannis</surname>
			</person>
			<person>
				<givenname>Paul J.</givenname>
				<surname>Krause</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>With REST becoming the dominant architectural paradigm for web services in distributed systems, more and more use cases are applied to it, including use cases that require transactional guarantees. We propose a RESTful transaction model that satisfies both the constraints of transactions and those of the REST architectural style. We then apply the isolation theorems to prove the robustness of its properties on a formal level.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1007/978-3-642-02818-2_32</identifier>
		<pages>394-409</pages>
		<title type="sharef:primaryTitle">RESTful Transactions Supported by the Isolation Theorems</title>
		<field type="bibtex:topic">RETRO[1] REST[0.8]</field>
		<identifier type="sharef:uri">http://www.springerlink.com/content/t720m1222t81n12g/</identifier>
	</reference>
	<reference name="icwe2009" src="bibtex:proceedings" src-info="bibtex:line-17798" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>Martin</givenname>
				<surname>Gaedke</surname>
			</person>
			<person>
				<givenname>Michael</givenname>
				<surname>Grossniklaus</surname>
			</person>
			<person>
				<givenname>Oscar</givenname>
				<surname>Díaz</surname>
			</person>
		</names>
		<date value="2009-06"/>
		<address type="sharef:placePublished">San Sebastián, Spain</address>
		<identifier type="sharef:doi">10.1007/978-3-642-02818-2</identifier>
		<identifier type="sharef:isbn">978-3-642-02817-5</identifier>
		<publisher>Springer-Verlag</publisher>
		<title type="sharef:seriesTitle">Lecture Notes in Computer Science</title>
		<title type="sharef:primaryTitle">9th International Conference on Web Engineering (ICWE 2009)</title>
		<identifier type="sharef:uri">http://icwe2009.webengineering.org/</identifier>
		<identifier type="sharef:uri" resourceType="text/html">http://www.informatik.uni-trier.de/~ley/db/conf/icwe/icwe2009.html</identifier>
		<volume>5648</volume>
	</reference>
	<reference name="liu10a" src="bibtex:inproceedings" src-info="bibtex:line-17818" type="sharef:inproceedings" crossref="icwe2010">
		<names type="sharef:author">
			<person>
				<givenname>Yiming</givenname>
				<surname>Liu</surname>
			</person>
			<person>
				<givenname>Erik</givenname>
				<surname>Wilde</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Web-based access to services increasingly moves to location-oriented scenarios, with either the client being mobile and requesting relevant information for the current location, or with a mobile or stationary client accessing a service which provides access to location-based information. The Web currently has no specific support for this kind of service pattern, and many scenarios use proprietary solutions which result in vertical designs with little possibility to share and mix information across various services. This papers describes an architecture for providing access to location-oriented services which is based on the principles of Representational State Transfer (REST) and uses a tiling scheme to allow clients to uniformly access location-oriented services. Based on these Tiled Feeds, lightweight access to location-oriented services can be implemented in a uniform and scalable way, and by using feeds, established patterns of information aggregation, filtering, and republishing can be easily applied.</p>
			</richtext>
		</abstract>
		<pages>307-321</pages>
		<title type="sharef:primaryTitle">Scalable and Mashable Location-Oriented Web Services</title>
		<identifier type="sharef:uri">http://dret.net/netdret/publications#liu10a</identifier>
	</reference>
	<reference name="icwe2010" src="bibtex:proceedings" src-info="bibtex:line-17827" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>Boualem</givenname>
				<surname>Benatallah</surname>
			</person>
			<person>
				<givenname>Fabio</givenname>
				<surname>Casati</surname>
			</person>
			<person>
				<givenname>Gerti</givenname>
				<surname>Kappel</surname>
			</person>
			<person>
				<givenname>Gustavo</givenname>
				<surname>Rossi</surname>
			</person>
		</names>
		<date value="2010-07"/>
		<address type="sharef:placePublished">Vienna, Austria</address>
		<identifier type="sharef:isbn">3-642-13910-8</identifier>
		<identifier type="sharef:isbn">978-3-642-13910-8</identifier>
		<publisher>Springer-Verlag</publisher>
		<title type="sharef:seriesTitle">Lecture Notes in Computer Science</title>
		<title type="sharef:primaryTitle">10th International Conference on Web Engineering (ICWE 2010)</title>
		<identifier type="sharef:uri">http://icwe2010.webengineering.org/</identifier>
		<identifier type="sharef:uri" resourceType="text/html">http://www.informatik.uni-trier.de/~ley/db/conf/icwe/icwe2010.html</identifier>
		<volume>6189</volume>
	</reference>
	<reference name="pau09b" src="bibtex:inproceedings" src-info="bibtex:line-17847" type="sharef:inproceedings" crossref="sc2009">
		<names type="sharef:author">
			<person>
				<givenname>Cesare</givenname>
				<surname>Pautasso</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>The REST architectural style is emerging as an alternative technology platform for the realization of service-oriented architectures. In this paper, we apply the notion of composition to RESTful services and derive a set of language features that are required by composition languages for RESTful services: dynamic late binding, dynamic typing, content-type negotiation, state inspection, and compliance with the uniform interface principle. To show how such requirements can be satisfied by an existing composition language, we include a case-study using the JOpera visual composition language. In it, we present how to build a composite application (DoodleMap) out of some well-known, public and currently existing RESTful service APIs.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1007/978-3-642-02655-3_11</identifier>
		<pages>142-159</pages>
		<title type="sharef:primaryTitle">Composing RESTful Services with JOpera</title>
		<identifier type="sharef:uri">http://www.jopera.org/docs/publications/2009/doodlemap</identifier>
	</reference>
	<reference name="sc2009" src="bibtex:proceedings" src-info="bibtex:line-17857" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>Alexandre</givenname>
				<surname>Bergel</surname>
			</person>
			<person>
				<givenname>Johan</givenname>
				<surname>Fabry</surname>
			</person>
		</names>
		<date value="2009-07"/>
		<address type="sharef:placePublished">Zürich, Switzerland</address>
		<identifier type="sharef:doi">10.1007/978-3-642-02654-6</identifier>
		<identifier type="sharef:isbn">978-3-642-02654-6</identifier>
		<publisher>Springer-Verlag</publisher>
		<title type="sharef:seriesTitle">Lecture Notes in Computer Science</title>
		<title type="sharef:primaryTitle">International Conference on Software Composition 2009</title>
		<volume>5634</volume>
	</reference>
	<reference name="sho78" src="bibtex:inproceedings" src-info="bibtex:line-17875" type="sharef:inproceedings" crossref="compcon78">
		<names type="sharef:author">
			<person>
				<givenname>John F.</givenname>
				<surname>Shoch</surname>
			</person>
		</names>
		<field type="bibtex:index">naming, addressing, routing</field>
		<pages>72-79</pages>
		<title type="sharef:primaryTitle">Inter-Network Naming, Addressing, and Routing</title>
	</reference>
	<reference name="compcon78" src="bibtex:proceedings" src-info="bibtex:line-17883" type="sharef:proceedings">
		<date value="1978"/>
		<address type="sharef:placePublished">Washington, D.C.</address>
		<field type="bibtex:index">COMPCON '78</field>
		<title type="sharef:primaryTitle">Seventeenth IEEE Conference on Computer Communication Networks</title>
	</reference>
	<reference name="fla88" src="bibtex:inproceedings" src-info="bibtex:line-17895" type="sharef:inproceedings" crossref="ftc88">
		<names type="sharef:author">
			<person>
				<givenname>Flaviu</givenname>
				<surname>Cristian</surname>
			</person>
		</names>
		<pages>206-211</pages>
		<title type="sharef:primaryTitle">Agreeing on Who is Present and Who is Absent in a Synchronous Distributed System</title>
	</reference>
	<reference name="ftc88" src="bibtex:proceedings" src-info="bibtex:line-17902" type="sharef:proceedings">
		<date value="1988"/>
		<address type="sharef:placePublished">Tokyo, Japan</address>
		<identifier type="sharef:isbn">0-8186-0867-6</identifier>
		<publisher>IEEE Computer Society Press</publisher>
		<title type="sharef:primaryTitle">18th IEEE International Symposium on Fault-Tolerant Computing</title>
	</reference>
	<reference name="mil00" src="bibtex:inproceedings" src-info="bibtex:line-17915" type="sharef:inproceedings" crossref="ohs6">
		<names type="sharef:author">
			<person>
				<givenname>David E.</givenname>
				<surname>Millard</surname>
			</person>
			<person>
				<givenname>Hugh C.</givenname>
				<surname>Davis</surname>
			</person>
			<person>
				<givenname>Luc</givenname>
				<surname>Moreau</surname>
			</person>
		</names>
		<pages>3-12</pages>
		<title type="sharef:primaryTitle">Standardizing Hypertext: Where Next for OHP?</title>
		<field type="bibtex:topic">ohp[0.9] fohm[0.8]</field>
	</reference>
	<reference name="ohs6" src="bibtex:proceedings" src-info="bibtex:line-17923" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>Siegfried</givenname>
				<surname>Reich</surname>
			</person>
			<person>
				<givenname>Kenneth M.</givenname>
				<surname>Anderson</surname>
			</person>
		</names>
		<date value="2000-06"/>
		<address type="sharef:placePublished">San Antonio, Texas</address>
		<field type="bibtex:index">OHS-6</field>
		<identifier type="sharef:isbn">3540410848</identifier>
		<publisher>Springer-Verlag</publisher>
		<title type="sharef:seriesTitle">Lecture Notes in Computer Science</title>
		<title type="sharef:primaryTitle">6th Workshop on Open Hypermedia Systems and Structural Computing</title>
		<field type="bibtex:topic">ohs[0.8]</field>
		<identifier type="sharef:uri">http://www.springer.de/cgi-bin/search_book.pl?isbn=3-540-41084-8</identifier>
		<volume>1903</volume>
	</reference>
	<reference name="cho94" src="bibtex:inproceedings" src-info="bibtex:line-17943" type="sharef:inproceedings" crossref="ictl94">
		<names type="sharef:author">
			<person>
				<givenname>Jan</givenname>
				<surname>Chomicki</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>We define formal notions of temporal domain and temporal database, and use them to survey a wide spectrum of temporal query languages. We distinguish between an abstract temporal database and its concrete representations, and accordingly between abstract and concrete temporal query languages. We also address the issue of incomplete temporal information.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1007/BFb0014006</identifier>
		<pages>506-534</pages>
		<title type="sharef:primaryTitle">Temporal Query Languages: A Survey</title>
	</reference>
	<reference name="ictl94" src="bibtex:book" src-info="bibtex:line-17952" type="sharef:book">
		<names type="sharef:editor">
			<person>
				<givenname>Dov M.</givenname>
				<surname>Gabbay</surname>
			</person>
			<person>
				<givenname>Hans Jürgen</givenname>
				<surname>Ohlbach</surname>
			</person>
		</names>
		<date value="1994-07"/>
		<address type="sharef:placePublished">Bonn, Germany</address>
		<identifier type="sharef:doi">10.1007/BFb0013976</identifier>
		<field type="bibtex:index">ICTL 1994</field>
		<identifier type="sharef:isbn">978-3-540-58241-0</identifier>
		<publisher>Springer-Verlag</publisher>
		<title type="sharef:seriesTitle">Lecture Notes in Computer Science</title>
		<title type="sharef:primaryTitle">First International Conference on Temporal Logic</title>
		<volume>827</volume>
	</reference>
	<reference name="and01b" src="bibtex:inproceedings" src-info="bibtex:line-17971" type="sharef:inproceedings" crossref="ohs7">
		<names type="sharef:author">
			<person>
				<givenname>Kenneth M.</givenname>
				<surname>Anderson</surname>
			</person>
			<person>
				<givenname>Susanne A.</givenname>
				<surname>Sherba</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Software engineers face a difficult task in managing the many different types of relationships that exist between the documents of a software development project. We refer to this task as  information integration, since establishing a relationship between two documents typically means that some part of the information in each document is semantically related. A key challenge in information integration is providing techniques and tools that manage and evolve these relationships over time. The structural computing domain provides a set of principles to derive new techniques and tools to help with these tasks of relationship management and evolution. We present a prototype information integration environment, InfiniTe, and describe how we are exploiting structural computing principles in the design of its infrastructure services.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">http://www.springerlink.com/content/prmrb11wvlxrcxpp/</identifier>
		<pages>151-159</pages>
		<title type="sharef:primaryTitle">Using Structural Computing to Support Information Integration</title>
	</reference>
	<reference name="and01" src="bibtex:inproceedings" src-info="bibtex:line-17980" type="sharef:inproceedings" crossref="ohs7">
		<names type="sharef:author">
			<person>
				<givenname>Kenneth M.</givenname>
				<surname>Anderson</surname>
			</person>
			<person>
				<givenname>Susanne A.</givenname>
				<surname>Sherba</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>The task of information integration challenges software engineers on a daily basis. Software artifacts, produced during software development, contain many implicit and explicit relationships whose sheer numbers quickly overwhelm a software team's ability to understand, manipulate, and evolve them. We are developing an information integration environment to aid software engineers in tackling this difficult task and are making use of open hypermedia techniques to enable critical characteristics of the environment, such as third-party tool integration, typed links, and a partitioned information space through the use of contexts, traditionally referred to as composites. We describe our prototype implementation of the information integration environment, focusing on how open hypermedia has either influenced the design of the environment, or contributed directly to its functional capabilities.</p>
			</richtext>
		</abstract>
		<pages>8-16</pages>
		<title type="sharef:primaryTitle">Using Open Hypermedia to Support Information Integration</title>
		<field type="bibtex:topic">ohs[0.8]</field>
		<identifier type="sharef:uri" resourceType="application/pdf">http://link.springer.de/link/service/series/0558/papers/2266/22660008.pdf</identifier>
	</reference>
	<reference name="wii01" src="bibtex:inproceedings" src-info="bibtex:line-17990" type="sharef:inproceedings" crossref="ohs7">
		<names type="sharef:author">
			<person>
				<givenname>Uffe Kock</givenname>
				<surname>Wiil</surname>
			</person>
			<person>
				<givenname>David L.</givenname>
				<surname>Hicks</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>The World Wide Web is one of the most successful software systems. The web provides a simple, extensible, and standardized hypermedia platform with millions of users that have access to millions of servers holding billions of documents. Hence, an increasing number of researchers and developers are making their systems and services available on the web. In conformance with this trend, this paper describes the first important results in the ongoing effort to provide the Construct structural computing services on the web. The paper is organized into five parts: an introduction to the research area, a brief overview of the Construct structural computing environment, a detailed description of the completed development effort to provide the Construct metadata services on the web, a quick overview of ongoing and future work in this area, and finally, our conclusions.</p>
			</richtext>
		</abstract>
		<pages>160-171</pages>
		<title type="sharef:primaryTitle">Providing Structural Computing Services on the World Wide Web</title>
		<identifier type="sharef:uri">http://www.springerlink.com/content/qccg4h3tbwnauq</identifier>
	</reference>
	<reference name="ohs7" src="bibtex:proceedings" src-info="bibtex:line-17999" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>Siegfried</givenname>
				<surname>Reich</surname>
			</person>
			<person>
				<givenname>Manolis M.</givenname>
				<surname>Tzagarakis</surname>
			</person>
			<person>
				<givenname>Paul M. E.</givenname>
				<surname>De Bra</surname>
			</person>
		</names>
		<date value="2001-08"/>
		<address type="sharef:placePublished">Århus, Denmark</address>
		<field type="bibtex:index">OHS-7</field>
		<publisher>Springer-Verlag</publisher>
		<title type="sharef:seriesTitle">Lecture Notes in Computer Science</title>
		<title type="sharef:primaryTitle">Hypermedia: Openness, Structural Awareness, and Adaptivity — International Workshops OHS-7, SC-3, and AH-3</title>
		<field type="bibtex:topic">ohs[0.8]</field>
		<identifier type="sharef:uri" resourceType="text/html">http://link.springer.de/link/service/series/0558/tocs/t2266.htm</identifier>
		<volume>2266</volume>
	</reference>
	<reference name="chr02" src="bibtex:inproceedings" src-info="bibtex:line-18018" type="sharef:inproceedings" crossref="ohs2002">
		<names type="sharef:author">
			<person>
				<givenname>Bent Guldbjerg</givenname>
				<surname>Christensen</surname>
			</person>
			<person>
				<givenname>Frank Allan</givenname>
				<surname>Hansen</surname>
			</person>
		</names>
		<title type="sharef:primaryTitle">XLink — Linking the Web and Open Hypermedia</title>
		<field type="bibtex:topic">xlink[0.8] ohs[0.8]</field>
		<identifier type="sharef:uri" resourceType="application/pdf">http://www.ecs.soton.ac.uk/~dem/workshops/ohs2002/positions/Christensen.pdf</identifier>
	</reference>
	<reference name="viv02" src="bibtex:inproceedings" src-info="bibtex:line-18026" type="sharef:inproceedings" crossref="ohs2002">
		<names type="sharef:author">
			<person>
				<givenname>Sanjay M.</givenname>
				<surname>Vivekanandan</surname>
			</person>
			<person>
				<givenname>David C.</givenname>
				<surname>De Roure</surname>
			</person>
		</names>
		<title type="sharef:primaryTitle">Workflow Description for Open Hypermedia Systems</title>
		<field type="bibtex:topic">ohs[0.8]</field>
		<identifier type="sharef:uri" resourceType="application/pdf">http://www.ecs.soton.ac.uk/~dem/workshops/ohs2002/positions/Vivekanandan2.pdf</identifier>
	</reference>
	<reference name="ohs2002" src="bibtex:proceedings" src-info="bibtex:line-18034" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>David E.</givenname>
				<surname>Millard</surname>
			</person>
			<person>
				<givenname>Jörg M.</givenname>
				<surname>Haake</surname>
			</person>
			<person>
				<givenname>Siegfried</givenname>
				<surname>Reich</surname>
			</person>
		</names>
		<date value="2002-06"/>
		<address type="sharef:placePublished">College Park, Maryland</address>
		<field type="bibtex:index">OHS2002</field>
		<title type="sharef:primaryTitle">2002 Workshop on Open Hypermedia Systems</title>
		<field type="bibtex:topic">ohs[0.8]</field>
	</reference>
	<reference name="pau03" src="bibtex:inproceedings" src-info="bibtex:line-18049" type="sharef:inproceedings" crossref="hcc2003">
		<names type="sharef:author">
			<person>
				<givenname>Cesare</givenname>
				<surname>Pautasso</surname>
			</person>
			<person>
				<givenname>Gustavo</givenname>
				<surname>Alonso</surname>
			</person>
		</names>
		<title type="sharef:primaryTitle">Visual Composition of Web Services</title>
		<field type="bibtex:topic">bfl[0.8]</field>
		<identifier type="sharef:uri" resourceType="text/html">http://www.iks.inf.ethz.ch/publications/publications/bio03v.html</identifier>
	</reference>
	<reference name="hcc2003" src="bibtex:proceedings" src-info="bibtex:line-18057" type="sharef:proceedings">
		<date value="2003-10"/>
		<address type="sharef:placePublished">Auckland, New Zealand</address>
		<field type="bibtex:index">HCC 2003</field>
		<title type="sharef:primaryTitle">2003 IEEE Symposia on Human Centric Computing Languages and Environments</title>
		<identifier type="sharef:uri">http://www.cs.dal.ca/HCC03/</identifier>
	</reference>
	<reference name="rod92c" src="bibtex:inproceedings" src-info="bibtex:line-18071" type="sharef:inproceedings" crossref="rds92">
		<names type="sharef:author">
			<person>
				<givenname>Luís</givenname>
				<surname>Rodrigues</surname>
			</person>
			<person>
				<givenname>Paulo</givenname>
				<surname>Veríssimo</surname>
			</person>
		</names>
		<field type="bibtex:index">xAMp, group orientation</field>
		<pages>112-121</pages>
		<title type="sharef:primaryTitle">xAMp: a Multi-primitive Group Communications Service</title>
	</reference>
	<reference name="rds92" src="bibtex:proceedings" src-info="bibtex:line-18079" type="sharef:proceedings">
		<date value="1992"/>
		<address type="sharef:placePublished">Houston, Texas</address>
		<identifier type="sharef:isbn">0-8186-2890-1</identifier>
		<publisher>IEEE Computer Society Press</publisher>
		<title type="sharef:primaryTitle">11th Symposium on Reliable Distributed Systems</title>
	</reference>
	<reference name="pet98" src="bibtex:inproceedings" src-info="bibtex:line-18092" type="sharef:inproceedings" crossref="krdb98">
		<names type="sharef:author">
			<person>
				<givenname>Brian J.</givenname>
				<surname>Peterson</surname>
			</person>
			<person>
				<givenname>William A.</givenname>
				<surname>Andersen</surname>
			</person>
			<person>
				<givenname>Joshua</givenname>
				<surname>Engel</surname>
			</person>
		</names>
		<pages>2.1-2.10</pages>
		<title type="sharef:primaryTitle">Knowledge Bus: Generating Application-focused Databases from Large Ontologies</title>
		<identifier type="sharef:uri" resourceType="text/html">http://www.informatik.uni-trier.de/~ley/db/conf/krdb/PetersonAE98.html</identifier>
	</reference>
	<reference name="krdb98" src="bibtex:proceedings" src-info="bibtex:line-18100" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>Alexander</givenname>
				<surname>Borgida</surname>
			</person>
			<person>
				<givenname>Vinay K.</givenname>
				<surname>Chaudhri</surname>
			</person>
			<person>
				<givenname>Martin</givenname>
				<surname>Staudt</surname>
			</person>
		</names>
		<date value="1998-05"/>
		<address type="sharef:placePublished">Seattle, Washington</address>
		<title type="sharef:primaryTitle">5th International Workshop on Knowledge Representation Meets Databases</title>
		<identifier type="sharef:uri" resourceType="text/html">http://www.informatik.uni-trier.de/~ley/db/conf/krdb/krdb98.html</identifier>
	</reference>
	<reference name="arb97" src="bibtex:inproceedings" src-info="bibtex:line-18114" type="sharef:inproceedings" crossref="ieeessp97">
		<names type="sharef:author">
			<person>
				<givenname>William A.</givenname>
				<surname>Arbaugh</surname>
			</person>
			<person>
				<givenname>David J.</givenname>
				<surname>Farber</surname>
			</person>
			<person>
				<givenname>Jonathan M.</givenname>
				<surname>Smith</surname>
			</person>
		</names>
		<pages>65-71</pages>
		<title type="sharef:primaryTitle">A Secure and Reliable Bootstrap Architecture</title>
		<field type="bibtex:topic">aegis[1]</field>
		<identifier type="sharef:uri" resourceType="text/html">http://www.computer.org/proceedings/sp/7828/78280065abs.htm</identifier>
	</reference>
	<reference name="ieeessp97" src="bibtex:proceedings" src-info="bibtex:line-18123" type="sharef:proceedings">
		<date value="1997-05"/>
		<address type="sharef:placePublished">Oakland, California</address>
		<publisher>IEEE Computer Society Press</publisher>
		<title type="sharef:primaryTitle">IEEE Symposium on Security and Privacy</title>
		<identifier type="sharef:uri" resourceType="text/html">http://www.computer.org/proceedings/sp/7828/7828toc.htm</identifier>
	</reference>
	<reference name="ecdl2001" src="bibtex:proceedings" src-info="bibtex:line-18137" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>Panos</givenname>
				<surname>Constantopoulos</surname>
			</person>
			<person>
				<givenname>Ingeborg Torvik</givenname>
				<surname>Sølvberg</surname>
			</person>
		</names>
		<date value="2001-09"/>
		<address type="sharef:placePublished">Darmstadt, Germany</address>
		<field type="bibtex:index">ECDL 2001</field>
		<identifier type="sharef:isbn">3540425373</identifier>
		<publisher>Springer-Verlag</publisher>
		<title type="sharef:seriesTitle">Lecture Notes in Computer Science</title>
		<title type="sharef:primaryTitle">Research and Advanced Technology for Digital Technology: 5th European Conference on Digital Libraries</title>
		<identifier type="sharef:uri" resourceType="text/html">http://www.informatik.uni-trier.de/~ley/db/conf/ercimdl/ecdl2001.html</identifier>
		<volume>2163</volume>
	</reference>
	<reference name="wit02a" src="bibtex:inproceedings" src-info="bibtex:line-18156" type="sharef:inproceedings" crossref="ecdl2002">
		<names type="sharef:author">
			<person>
				<givenname>Ian H.</givenname>
				<surname>Witten</surname>
			</person>
			<person>
				<givenname>David</givenname>
				<surname>Bainbridge</surname>
			</person>
			<person>
				<givenname>Gordon</givenname>
				<surname>Paynter</surname>
			</person>
			<person>
				<givenname>Stefan</givenname>
				<surname>Boddie</surname>
			</person>
		</names>
		<pages>390-405</pages>
		<title type="sharef:primaryTitle">Importing Documents and Metadata into Digital Libraries: Requirements Analysis and an Extensible Architecture</title>
		<identifier type="sharef:uri" resourceType="application/pdf">http://link.springer.de/link/service/series/0558/papers/2458/24580390.pdf</identifier>
	</reference>
	<reference name="som02" src="bibtex:inproceedings" src-info="bibtex:line-18164" type="sharef:inproceedings" crossref="ecdl2002">
		<names type="sharef:author">
			<person>
				<givenname>Herbert</givenname>
				<surname>Van de Sompel</surname>
			</person>
			<person>
				<givenname>Carl</givenname>
				<surname>Lagoze</surname>
			</person>
		</names>
		<pages>144-157</pages>
		<title type="sharef:primaryTitle">Notes from the Interoperability Front: A Progress Report on the Open Archives Initiative</title>
		<field type="bibtex:topic">oai[0.9]</field>
	</reference>
	<reference name="ecdl2002" src="bibtex:proceedings" src-info="bibtex:line-18172" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>Maristella</givenname>
				<surname>Agosti</surname>
			</person>
			<person>
				<givenname>Costantino</givenname>
				<surname>Thanos</surname>
			</person>
		</names>
		<date value="2002-09"/>
		<address type="sharef:placePublished">Rome, Italy</address>
		<field type="bibtex:index">ECDL 2002</field>
		<identifier type="sharef:isbn">3540441786</identifier>
		<publisher>Springer-Verlag</publisher>
		<title type="sharef:seriesTitle">Lecture Notes in Computer Science</title>
		<title type="sharef:primaryTitle">Research and Advanced Technology for Digital Technology: 6th European Conference on Digital Libraries</title>
		<identifier type="sharef:uri" resourceType="text/html">http://link.springer.de/link/service/series/0558/tocs/t2458.htm</identifier>
		<volume>2458</volume>
	</reference>
	<reference name="ste03" src="bibtex:inproceedings" src-info="bibtex:line-18191" type="sharef:inproceedings" crossref="ecdl2003">
		<names type="sharef:author">
			<person>
				<givenname>Jela</givenname>
				<surname>Steinerová</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>The paper provides preliminary results from a major study of the academic and research libraries users in Slovakia. The study is part of a larger research project on interaction of man and information environment. The goal of the research is to identify patterns of interaction of individuals and groups with information resources, derive models and information styles. The methodological model for questionnaire survey of users is described. The first results confirm the need to support user strategies, collaboration, different stages of information seeking and knowledge states, closer links with learning and problem solving, easy and flexible access, human creative processes of analysis, synthesis, interpretation, and the need to develop new knowledge organization structures.</p>
			</richtext>
		</abstract>
		<pages>13-23</pages>
		<title type="sharef:primaryTitle">In Search for Patterns of User Interaction for Digital Libraries</title>
		<identifier type="sharef:uri">http://springerlink.metapress.com/link.asp?id=htajhhgyh9vmm3d0</identifier>
	</reference>
	<reference name="ecdl2003" src="bibtex:proceedings" src-info="bibtex:line-18200" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>Traugott</givenname>
				<surname>Koch</surname>
			</person>
			<person>
				<givenname>Ingeborg Torvik</givenname>
				<surname>Sølvberg</surname>
			</person>
		</names>
		<date value="2003-08"/>
		<address type="sharef:placePublished">Trondheim, Norway</address>
		<identifier type="sharef:doi">10.1007/b11967</identifier>
		<field type="bibtex:index">ECDL 2003</field>
		<identifier type="sharef:isbn">354040726X</identifier>
		<publisher>Springer-Verlag</publisher>
		<title type="sharef:seriesTitle">Lecture Notes in Computer Science</title>
		<title type="sharef:primaryTitle">Research and Advanced Technology for Digital Libraries: 7th European Conference on Digital Libraries</title>
		<identifier type="sharef:uri" resourceType="text/html">http://www.springeronline.com/sgw/cda/frontpage/0,10735,5-40109-22-7042117-0,00.html</identifier>
		<identifier type="sharef:uri" resourceType="text/html">http://www.informatik.uni-trier.de/~ley/db/conf/ercimdl/ecdl2003.html</identifier>
		<volume>2769</volume>
	</reference>
	<reference name="ago04" src="bibtex:inproceedings" src-info="bibtex:line-18221" type="sharef:inproceedings" crossref="ecdl2004">
		<names type="sharef:author">
			<person>
				<givenname>Maristella</givenname>
				<surname>Agosti</surname>
			</person>
			<person>
				<givenname>Nicola</givenname>
				<surname>Ferro</surname>
			</person>
			<person>
				<givenname>Ingo</givenname>
				<surname>Frommholz</surname>
			</person>
			<person>
				<givenname>Ulrich</givenname>
				<surname>Thiel</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>This paper presents the results of our study regarding the different facets and ways of using annotations in both digital libraries and collaboratories. This study represents an innovative attempt at gathering methodological tools and synergies from both fields in order to effectively define a comprehensive model for annotations. Thus we propose a conceptual model for annotations in order to develop an annotation service that can be plugged into digital libraries and collaboratories. Finally, starting from our model, we introduce a search strategy for exploiting annotations in order to search and retrieve relevant documents for a user query.</p>
			</richtext>
		</abstract>
		<pages>244-255</pages>
		<title type="sharef:primaryTitle">Annotations in Digital Libraries and Collaboratories — Facets, Models and Usage</title>
		<identifier type="sharef:uri">http://www.springerlink.com/link.asp?id=ah229da5je3ka8y7</identifier>
	</reference>
	<reference name="mal04" src="bibtex:inproceedings" src-info="bibtex:line-18230" type="sharef:inproceedings" crossref="ecdl2004">
		<names type="sharef:author">
			<person>
				<givenname>Kurt</givenname>
				<surname>Maly</surname>
			</person>
			<person>
				<givenname>Michael L.</givenname>
				<surname>Nelson</surname>
			</person>
			<person>
				<givenname>Mohammad</givenname>
				<surname>Zubair</surname>
			</person>
			<person>
				<givenname>Ashraf</givenname>
				<surname>Amrou</surname>
			</person>
			<person>
				<givenname>Sathish</givenname>
				<surname>Kothamasa</surname>
			</person>
			<person>
				<givenname>Lan</givenname>
				<surname>Wang</surname>
			</person>
			<person>
				<givenname>Richard</givenname>
				<surname>Luce</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Kepler is an attempt to bridge the gap between established, organization-backed digital libraries and groups of researchers that wish to publish their findings under their control, anytime, anywhere yet have the advantages of an OAI-compliant digital library. We describe an architecture and implementation of the Kepler system that allows an archivelet to be installed in the order of minutes by an author on a personal machine and a group server in less than an hour. The group server will harvest from all archivelets and make the union of all published papers available for search to a community. We describe how a group administrator can provide an XML schema for the metadata and how the Kepler engine will validate against them when an author publishes a paper and completes the metadata. We have demonstrated that we can surmount the technical difficulties for authors to publish as easy as to a website yet produce OAI-compliant digital libraries.</p>
			</richtext>
		</abstract>
		<pages>317-328</pages>
		<title type="sharef:primaryTitle">Enhancing Kepler Usability and Performance</title>
		<identifier type="sharef:uri">http://springerlink.metapress.com/link.asp?id=m0p9cv1utnxvf9ku</identifier>
	</reference>
	<reference name="kor04" src="bibtex:inproceedings" src-info="bibtex:line-18239" type="sharef:inproceedings" crossref="ecdl2004">
		<names type="sharef:author">
			<person>
				<givenname>Mark</givenname>
				<surname>Kornbluh</surname>
			</person>
			<person>
				<givenname>Michael</givenname>
				<surname>Fegan</surname>
			</person>
			<person>
				<givenname>Dean</givenname>
				<surname>Rehberger</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>This paper argues for the necessity of digital libraries to increase access to their holdings and have greater impact on e-learning and education by facilitating the creation of secondary repositories. These repositories will provide discipline/community specific metadata and applications and will allow users to find, use, manipulate and analyze digital objects more easily. To this end, MATRIX has developed Media Matrix 1.0 an online, easy to use server-side suite of tools that allows users to locate specific media and streaming media files found in digital repositories and segment, annotate and organize this media online. This application provides users with an environment both to work with and personalize digital media, and also to share and discuss their findings with a community of users. Through creating a secondary repository of usage statistics and user-generated materials/metadata to supplement both traditional cataloging records and discipline-specific online indexes, tools like Media Matrix can help extend the usefulness of digital libraries without increasing costs to the libraries.</p>
			</richtext>
		</abstract>
		<pages>329-340</pages>
		<title type="sharef:primaryTitle">Media Matrix: Creating Secondary Repositories</title>
		<identifier type="sharef:uri">http://springerlink.metapress.com/link.asp?id=u68l1ct0ck36wv4k</identifier>
	</reference>
	<reference name="ecdl2004" src="bibtex:proceedings" src-info="bibtex:line-18248" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>Rachel</givenname>
				<surname>Heery</surname>
			</person>
			<person>
				<givenname>Liz</givenname>
				<surname>Lyon</surname>
			</person>
		</names>
		<date value="2004-09"/>
		<address type="sharef:placePublished">Bath, UK</address>
		<identifier type="sharef:doi">10.1007/b100389</identifier>
		<field type="bibtex:index">ECDL 2004</field>
		<identifier type="sharef:isbn">3-540-23013-0</identifier>
		<publisher>Springer-Verlag</publisher>
		<title type="sharef:seriesTitle">Lecture Notes in Computer Science</title>
		<title type="sharef:primaryTitle">Research and Advanced Technology for Digital Libraries: 8th European Conference on Digital Libraries</title>
		<identifier type="sharef:uri" resourceType="text/html">http://www.informatik.uni-trier.de/~ley/db/conf/ercimdl/ecdl2004.html</identifier>
		<volume>3232</volume>
	</reference>
	<reference name="ama05" src="bibtex:inproceedings" src-info="bibtex:line-18268" type="sharef:inproceedings" crossref="ecdl2005">
		<names type="sharef:author">
			<person>
				<givenname>Giuseppe</givenname>
				<surname>Amato</surname>
			</person>
			<person>
				<givenname>Franca</givenname>
				<surname>Debole</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>XML is becoming the standard representation format for metadata. Metadata for multimedia documents, as for instance MPEG-7, require approximate match search functionalities to be supported in addition to exact match search. As an example, consider image search performed by using MPEG-7 visual descriptors. It does not make sense to search for images that are exactly equal to a query image. Rather, images similar to a query image are more likely to be searched. We present the architecture of an XML search engine where special techniques are used to integrate approximate and exact match search functionalities.</p>
			</richtext>
		</abstract>
		<pages>69-80</pages>
		<title type="sharef:primaryTitle">A Native XML Database Supporting Approximate Match Search</title>
		<identifier type="sharef:uri">http://www.springerlink.com/link.asp?id=5v9rt0qn6w09t64t</identifier>
	</reference>
	<reference name="san05" src="bibtex:inproceedings" src-info="bibtex:line-18277" type="sharef:inproceedings" crossref="ecdl2005">
		<names type="sharef:author">
			<person>
				<givenname>Enrique Sánchez</givenname>
				<surname>Villamil</surname>
			</person>
			<person>
				<givenname>Carlos González</givenname>
				<surname>Muñoz</surname>
			</person>
			<person>
				<givenname>Rafael C.</givenname>
				<surname>Carrasco</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>The increase in the amount of data available in digital libraries calls for the development of search engines that allow the users to find quickly and effectively what they are looking for. The XML tagging makes possible the addition of structural information in digitized content. These metadata offer new opportunities to a wide variety of new services. This paper describes the requirements that a search engine inside a digital library should fulfill and it also presents a specific XML search engine architecture. This architecture is designed to index a large amount of text with structural tagging and to be web-available. The architecture has been developed and successfully tested at the Miguel de Cervantes Digital Library.</p>
			</richtext>
		</abstract>
		<pages>81-91</pages>
		<title type="sharef:primaryTitle">XMLibrary Search: An XML Search Engine Oriented to Digital Libraries</title>
		<identifier type="sharef:uri">http://www.springerlink.com/link.asp?id=bvd7hxjkarhurupy</identifier>
	</reference>
	<reference name="cha05" src="bibtex:inproceedings" src-info="bibtex:line-18286" type="sharef:inproceedings" crossref="ecdl2005">
		<names type="sharef:author">
			<person>
				<givenname>Jean-Pierre</givenname>
				<surname>Chanod</surname>
			</person>
			<person>
				<givenname>Boris</givenname>
				<surname>Chidlovskii</surname>
			</person>
			<person>
				<givenname>Hervé</givenname>
				<surname>Déjean</surname>
			</person>
			<person>
				<givenname>Olivier</givenname>
				<surname>Fambon</surname>
			</person>
			<person>
				<givenname>Jérôme</givenname>
				<surname>Fuselier</surname>
			</person>
			<person>
				<givenname>Thierry</givenname>
				<surname>Jacquin</surname>
			</person>
			<person>
				<givenname>Jean-Luc</givenname>
				<surname>Meunier</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>We present an integrated framework for the document conversion from legacy formats to XML format. We describe the LegDoC project, aimed at automating the conversion of layout annotations layout-oriented formats like PDF, PS and HTML to semantic-oriented annotations. A toolkit of different components covers complementary techniques the logical document analysis and semantic annotations with the methods of machine learning. We use a real case conversion project as a driving example to exemplify different techniques implemented in the project.</p>
			</richtext>
		</abstract>
		<pages>92-103</pages>
		<title type="sharef:primaryTitle">From Legacy Documents to XML: A Conversion Framework</title>
		<identifier type="sharef:uri">http://www.springerlink.com/link.asp?id=5xnqptg4hrdqmy3g</identifier>
	</reference>
	<reference name="mul05" src="bibtex:inproceedings" src-info="bibtex:line-18295" type="sharef:inproceedings" crossref="ecdl2005">
		<names type="sharef:author">
			<person>
				<givenname>Uwe</givenname>
				<surname>Müller</surname>
			</person>
			<person>
				<givenname>Manuel</givenname>
				<surname>Klatt</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>One of the objectives of the Open Access movement is to establish institutional repositories at universities and other research institutions in order to support self-archiving. Although a lot of software solutions have already been presented in recent years they lack a seamless integration of authoring tools, support for authors, and other technical publication tools. This paper presents a formal approach to describe software components applied in publishing processes. Additionally it is depicted how this formal description leads to the technological basis for SCOPE (Service Core for Open Publishing Environments) — a publishing platform for XML based publishing models. SCOPE is a framework intended for the integration of different publication components into a single platform.</p>
			</richtext>
		</abstract>
		<pages>104-115</pages>
		<title type="sharef:primaryTitle">SCOPE — A Generic Framework for XML Based Publishing Processes</title>
		<identifier type="sharef:uri">http://www.springerlink.com/link.asp?id=8ypp69ufqxl2fjd6</identifier>
	</reference>
	<reference name="wil05n" src="bibtex:inproceedings" src-info="bibtex:line-18304" type="sharef:inproceedings" crossref="ecdl2005">
		<names type="sharef: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>
		<abstract>
			<richtext>
				<p>Managing bibliographic data is a requirement for many researchers, and in the group setting within which the majority of research takes place, the managing and sharing of bibliographic data is an important facet of organizing the research work. Managing and sharing bibliographies has to balance different levels of shared access (public catalogs, closed research group bibliographies, and personal bibliographies), and the sharing platform should integrate as seamlessly as possible into diverse environments in terms of operating systems, document processing, and other information management tools. The ShaRef system presented in this paper has been designed to fill the gap between public libraries and personal bibliographies, and provides an open platform for sharing bibliographic data among user groups. Through its simple and flexible data model and system architecture, ShaRef adapts to many settings and requirements, and can be used to increase collaboration and information flow within groups.</p>
			</richtext>
		</abstract>
		<pages>479-480</pages>
		<title type="sharef:primaryTitle">Management and Sharing of Bibliographies</title>
		<identifier type="sharef:uri">http://dret.net/netdret/publications#wil05n</identifier>
		<identifier type="sharef:uri">http://www.springerlink.com/link.asp?id=8eneh1urq3egf8ct</identifier>
	</reference>
	<reference name="ecdl2005" src="bibtex:proceedings" src-info="bibtex:line-18314" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>Andreas</givenname>
				<surname>Rauber</surname>
			</person>
			<person>
				<givenname>Stavros</givenname>
				<surname>Christodoulakis</surname>
			</person>
			<person>
				<givenname>A.</givenname>
				<surname>Min Tjoa</surname>
			</person>
		</names>
		<date value="2005-09"/>
		<address type="sharef:placePublished">Vienna, Austria</address>
		<field type="bibtex:index">ECDL 2005</field>
		<publisher>Springer-Verlag</publisher>
		<title type="sharef:seriesTitle">Lecture Notes in Computer Science</title>
		<title type="sharef:primaryTitle">9th European Conference on Digital Libraries</title>
		<volume>3652</volume>
	</reference>
	<reference name="wil04m" src="bibtex:inproceedings" src-info="bibtex:line-18331" type="sharef:inproceedings" crossref="icete2004">
		<names type="sharef:author">
			<person>
				<givenname>Erik</givenname>
				<surname>Wilde</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>While XML-based Web Service architectures are successfully turning the Web into an infrastructure for cooperating applications, not all problems with respect to interoperability problems have yet been solved. XML-based data exchange has the ability to carry the full Unicode character repertoire, which is approaching 100'000 characters. Many legacy application are being Web-Service-enabled rather than being re-built from scratch, and therefore still have the same limitations. A frequently seen limitation is the inability to handle the full Unicode character repertoire. We describe an architectural approach and a schema language to address this issue. The architectural approach proposes to establish validation as basic Web Service functionality, which should be built into a Web Services architecture rather than applications. Based on this vision of modular an infrastructure-based validation, we propose a schema language for character repertoire validation. Lessons learned from the first implementation and possible improvements of the schema language conclude the paper.</p>
			</richtext>
		</abstract>
		<pages>144-151</pages>
		<title type="sharef:primaryTitle">Protecting Legacy Applications from Unicode</title>
		<identifier type="sharef:uri">http://dret.net/netdret/publications#wil04m</identifier>
	</reference>
	<reference name="wil04n" src="bibtex:inproceedings" src-info="bibtex:line-18340" type="sharef:inproceedings" crossref="icete2004">
		<names type="sharef:author">
			<person>
				<givenname>Erik</givenname>
				<surname>Wilde</surname>
			</person>
			<person>
				<givenname>Jacqueline</givenname>
				<surname>Schwerzmann</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>The music industry is an interesting example for how business models from the pre-Internet area can get into trouble in the new Internet-based economy. Since 2000, the music industry has suffered declining sales, and very often this is attributed to the advent of the Internet-based peer-to-peer file sharing programs. We argue that this explanation is only one of several possible explanations, and that the general decrease in the economic indicators is a more reasonable way to explain the declining sales. Whatever the reason for the declining sales may be, the question remains what the music industry could and should do to stop the decline in revenue. The current strategy of the music industry is centered around protecting their traditional business model through technical measures and in parallel working towards legally protecting the technical measures. It remains to be seen whether this approach is successful, and whether the resulting landscape of tightly controlled digital content distribution is technically feasible and accepted by the consumers. We argue that the search for new business models is the better way to go, even though it may take some time and effort to identify these business models.</p>
			</richtext>
		</abstract>
		<pages>48-54</pages>
		<title type="sharef:primaryTitle">When Business Models Go Bad: The Music Industry's Future</title>
		<identifier type="sharef:uri">http://dret.net/netdret/publications#wil04n</identifier>
	</reference>
	<reference name="icete2004" src="bibtex:proceedings" src-info="bibtex:line-18349" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>João</givenname>
				<surname>Ascenso</surname>
			</person>
			<person>
				<givenname>Carlos</givenname>
				<surname>Belo</surname>
			</person>
			<person>
				<givenname>Luminita</givenname>
				<surname>Vasiu</surname>
			</person>
			<person>
				<givenname>Mónica</givenname>
				<surname>Saramago</surname>
			</person>
			<person>
				<givenname>Helder</givenname>
				<surname>Coelhas</surname>
			</person>
		</names>
		<date value="2004-08"/>
		<address type="sharef:placePublished">Setúbal, Portugal</address>
		<field type="bibtex:index">ICETE 2004</field>
		<identifier type="sharef:isbn">972-8865-15-5</identifier>
		<publisher>INSTICC Press</publisher>
		<title type="sharef:primaryTitle">International Conference on E-Business and Telecommunication Networks</title>
		<identifier type="sharef:uri">http://www.icete.org/</identifier>
	</reference>
	<reference name="wil05t" src="bibtex:inproceedings" src-info="bibtex:line-18366" type="sharef:inproceedings" crossref="iawtic2005">
		<names type="sharef:author">
			<person>
				<givenname>Erik</givenname>
				<surname>Wilde</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Providing users with help and other documentation is essential for any software targeted at end users. Authoring help and documentation in a platform-independent way is hard, because different help systems have different conventions for structuring and organizing the documents. The Help System Generator (HSG) presented in this paper provides an easy and platform-independent way of preparing and publishing help and documentation. Using HSG, software creators can easily author, reuse, and publish help and documentation for different platforms.</p>
			</richtext>
		</abstract>
		<pages>251-255</pages>
		<title type="sharef:primaryTitle">Augmenting XHTML for Help and Documentation</title>
		<identifier type="sharef:uri">http://dret.net/netdret/publications#wil05t</identifier>
	</reference>
	<reference name="wil05u" src="bibtex:inproceedings" src-info="bibtex:line-18375" type="sharef:inproceedings" crossref="iawtic2005">
		<names type="sharef:author">
			<person>
				<givenname>Erik</givenname>
				<surname>Wilde</surname>
			</person>
			<person>
				<givenname>Nick</givenname>
				<surname>Nabholz</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Access control for shared resources is a complex and challenging task, in particular if the access control policy should be able to cope with different kind of sharing and collaboration. The reason for this is that traditional access control system often depend on administrators to set up the foundations of the access control mechanism, in most cases users and their group memberships. The access control model presented in this paper approaches this problem by supporting two different kinds of groups, named groups and resource-based groups. Using the implementation of this model in our application allows to to support a wide variety of sharing and collaboration types between the application's users.</p>
			</richtext>
		</abstract>
		<pages>256-260</pages>
		<title type="sharef:primaryTitle">Access Control for Shared Resources</title>
		<identifier type="sharef:uri">http://dret.net/netdret/publications#wil05u</identifier>
	</reference>
	<reference name="iawtic2005" src="bibtex:proceedings" src-info="bibtex:line-18384" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>Masoud</givenname>
				<surname>Mohammadian</surname>
			</person>
		</names>
		<date value="2005-11"/>
		<address type="sharef:placePublished">Vienna, Austria</address>
		<field type="bibtex:index">IAWTIC 2005</field>
		<identifier type="sharef:isbn">0-7695-2504-0</identifier>
		<publisher>IEEE Computer Society Press</publisher>
		<title type="sharef:primaryTitle">International Conference on Intelligent Agents, Web Technology and Internet Commerce</title>
	</reference>
	<reference name="che05" src="bibtex:inproceedings" src-info="bibtex:line-18400" type="sharef:inproceedings" crossref="icebe2005">
		<names type="sharef:author">
			<person>
				<givenname>Shyh-Kwei</givenname>
				<surname>Chen</surname>
			</person>
			<person>
				<givenname>Hui</givenname>
				<surname>Lei</surname>
			</person>
			<person>
				<givenname>Michael</givenname>
				<surname>Walher</surname>
			</person>
			<person>
				<givenname>Henry</givenname>
				<surname>Chang</surname>
			</person>
			<person>
				<givenname>Kumar</givenname>
				<surname>Bhaskaran</surname>
			</person>
			<person>
				<givenname>Joachim</givenname>
				<surname>Frank</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>As XML formats have been widely adopted for representing business documents both within and across enterprises, XML to XML translation becomes a common and critical component for business process integration. Due to limitations of popular approaches such as XSLT for XML translations, we designed a model driven development framework for XML to XML translation with the additional benefits of code re-use and strong built-in model validation. We further applied this framework to the domain of business performance management, converting documents from human-readable XML format to machine-readable XMI format.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1109/ICEBE.2005.10</identifier>
		<pages>71-78</pages>
		<title type="sharef:primaryTitle">A Model Driven XML Transformation Framework for Business Performance Management</title>
	</reference>
	<reference name="kon05" src="bibtex:inproceedings" src-info="bibtex:line-18409" type="sharef:inproceedings" crossref="icebe2005">
		<names type="sharef:author">
			<person>
				<givenname>Xiaoying</givenname>
				<surname>Kong</surname>
			</person>
			<person>
				<givenname>Li</givenname>
				<surname>Liu</surname>
			</person>
			<person>
				<givenname>David</givenname>
				<surname>Lowe</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Existing design methods used for developing webcentric systems are mostly adapted from methods for designing traditional software systems. Web-centric systems however differ from traditional software systems, in terms of both organizational and technical characteristics. Effective design methods for webcentric systems need to address these characteristics specific to web-centric systems. This paper proposes a design method for web-centric systems. The de-sign process comprises three steps: prototyping, information modeling and system architecture design. The method is differentiated from existing design methods in that the design process commences from user interface prototyping. Information modeling activities are further enhanced in this method. To cope with the complexity of web systems, each design step is partitioned into both structural modeling and behavioral modeling. The design method is illustrated by applying the method to the design of a commercial web application.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1109/ICEBE.2005.116</identifier>
		<pages>63-70</pages>
		<title type="sharef:primaryTitle">Supporting Web User Interface Prototyping through Information Modeling and System Architecting</title>
	</reference>
	<reference name="icebe2005" src="bibtex:proceedings" src-info="bibtex:line-18418" type="sharef:proceedings">
		<date value="2005-10"/>
		<address type="sharef:placePublished">Beijing, China</address>
		<field type="bibtex:index">ICEBE 2005</field>
		<identifier type="sharef:isbn">972-8865-15-5</identifier>
		<publisher>IEEE Computer Society Press</publisher>
		<title type="sharef:primaryTitle">IEEE International Conference on E-Business Engineering</title>
		<identifier type="sharef:uri">http://www.cs.hku.hk/icebe2005/</identifier>
		<identifier type="sharef:uri" resourceType="text/html">http://www.informatik.uni-trier.de/~ley/db/conf/icebe/icebe2005.html</identifier>
	</reference>
	<reference name="pas06" src="bibtex:inproceedings" src-info="bibtex:line-18435" type="sharef:inproceedings" crossref="otm2006">
		<names type="sharef:author">
			<person>
				<givenname>Jason</givenname>
				<surname>Pascoe</surname>
			</person>
			<person>
				<givenname>Helena</givenname>
				<surname>Rodrigues</surname>
			</person>
			<person>
				<givenname>César</givenname>
				<surname>Ariza</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>If a mobile device is to offer rich context-aware behaviour it must have a good knowledge of the world around us. This paper explores the concept of universal context model, able to represent any form of context information and therefore be an enabler to the full spectrum of context-aware applications. It explores how such a model may accurately represent — as far as practically possible — the multitude of different objects we encounter in our surrounding environment and their many states and interrelationships. Three key propositions are that the context model should be of an object-oriented nature, that location is most appropriately and flexibly represented as a relationship between two objects rather than being considered as a special type of object unto itself, and finally, that objects may be coupled with observer-dependent validity rules that determine if the object is visible within the model.</p>
			</richtext>
		</abstract>
		<pages>1884-1893</pages>
		<title type="sharef:primaryTitle">An Investigation into a Universal Context Model to Support Context-Aware Applications</title>
		<identifier type="sharef:uri">http://www.springerlink.com/content/77626337252w6q75/</identifier>
	</reference>
	<reference name="otm2006" src="bibtex:proceedings" src-info="bibtex:line-18444" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>Robert</givenname>
				<surname>Meersman</surname>
			</person>
			<person>
				<givenname>Zahir</givenname>
				<surname>Tari</surname>
			</person>
			<person>
				<givenname>Pilar</givenname>
				<surname>Herrero</surname>
			</person>
		</names>
		<date value="2006-11"/>
		<address type="sharef:placePublished">Montpellier, France</address>
		<identifier type="sharef:doi">10.1007/11915072</identifier>
		<field type="bibtex:index">OTM 2006</field>
		<identifier type="sharef:isbn">978-3-540-48273-4</identifier>
		<publisher>Springer-Verlag</publisher>
		<title type="sharef:seriesTitle">Lecture Notes in Computer Science</title>
		<title type="sharef:primaryTitle">OTM Confederated International Workshops and Posters</title>
		<identifier type="sharef:uri">http://www.springerlink.com/content/978-3-540-48273-4/</identifier>
		<volume>4278</volume>
	</reference>
	<reference name="ada03" src="bibtex:inproceedings" src-info="bibtex:line-18464" type="sharef:inproceedings" crossref="egov2003">
		<names type="sharef:author">
			<person>
				<givenname>Otmar</givenname>
				<surname>Adam</surname>
			</person>
			<person>
				<givenname>Dirk</givenname>
				<surname>Werth</surname>
			</person>
			<person>
				<givenname>Fabrice</givenname>
				<surname>Zangl</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>One of the main strategic goals of the European Union is a borderless Europe. In reality there are yet a lot of steps to achieve this ambitious goal. An impediment to this mobility is the lack of integration in pan-European administrative processes. To solve the problems these business processes have to be made transparent to the citizen and public services need to be integrated. To do so, public administrations have to interact seamlessly vertically (Europe, nation, region, municipality) as well as horizontally (between countries) with each other. This implies not only the use of standards for data exchange but also the interoperability of business processes. InfoCitizen is a "proof-of-concept" e-government project in the context of the EU IST Framework Program 5 with a budget of more than three million Euros. Within InfoCitizen a European Information Architecture dealing with the interoperability problem has been developed. Based on these blueprints a prototype has been implemented and currently user-partners are evaluating the concepts and the system in interacting local showcases. In this paper the results of the project are shown by summarising the project so far. Findings are used to map out future tasks.</p>
			</richtext>
		</abstract>
		<pages>135-138</pages>
		<title type="sharef:primaryTitle">Conceiving and Implementing Pan-european Integrated Public Services</title>
		<identifier type="sharef:uri">http://springerlink.metapress.com/openurl.asp?genre=article&amp;issn=0302-9743&amp;volume=2739&amp;spage=24</identifier>
	</reference>
	<reference name="gam03" src="bibtex:inproceedings" src-info="bibtex:line-18473" type="sharef:inproceedings" crossref="egov2003">
		<names type="sharef:author">
			<person>
				<givenname>Johann</givenname>
				<surname>Gamper</surname>
			</person>
			<person>
				<givenname>Nikolaus</givenname>
				<surname>Augsten</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Since a few years digital government is becoming an active research area with lots of promises to revolutionise government and its interaction with citizens and businesses. A crucial point for the success of e-government is the integration and sharing of services and information provided by different authorities. We argue that Web services are a promising technology to solve this problem. The work has been done in the framework of the "eBZ-Digital City" project, which is funded by the Municipality of Bozen-Bolzano.</p>
			</richtext>
		</abstract>
		<pages>161-166</pages>
		<title type="sharef:primaryTitle">The Role of Web Services in Digital Government</title>
		<identifier type="sharef:uri">http://springerlink.metapress.com/openurl.asp?genre=article&amp;issn=0302-9743&amp;volume=2739&amp;spage=30</identifier>
	</reference>
	<reference name="egov2003" src="bibtex:proceedings" src-info="bibtex:line-18482" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>Roland</givenname>
				<surname>Traunmüller</surname>
			</person>
		</names>
		<date value="2003-09"/>
		<address type="sharef:placePublished">Prague, Czech Republic</address>
		<identifier type="sharef:doi">10.1007/b11827</identifier>
		<field type="bibtex:index">EGov 2003</field>
		<identifier type="sharef:isbn">3-540-40845-2</identifier>
		<publisher>Springer-Verlag</publisher>
		<title type="sharef:seriesTitle">Lecture Notes in Computer Science</title>
		<title type="sharef:primaryTitle">3rd International Workshop on Knowledge Management in e-Government</title>
		<identifier type="sharef:uri" resourceType="text/html">http://www.informatik.uni-trier.de/~ley/db/conf/egov/egov2003.html</identifier>
		<volume>2739</volume>
	</reference>
	<reference name="qui02" src="bibtex:inproceedings" src-info="bibtex:line-18502" type="sharef:inproceedings" crossref="kmgov2002">
		<names type="sharef:author">
			<person>
				<givenname>Gerald</givenname>
				<surname>Quirchmayr</surname>
			</person>
			<person>
				<givenname>Roger</givenname>
				<surname>Tagg</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Advances in Business-to-Business electronic commerce now offer opportunities for improved efficiency and profitability in the commercial sector. But similar opportunities are not yet commonplace for inter-administration situations. Differences in goals mean that packaged software solutions do not carry across well to administrative computing. However processes, shared where appropriate, are still the core element of inter-organizational knowledge, although in administration there is a greater emphasis on rules and legislation, and the payoffs to cooperating administrative units are not always clear. In this paper a layered architecture, derived from one previously proposed for virtual enterprises, is introduced. This architecture includes a high level service request layer, process guidance agents, context-aware work environments and the concept of "just enough" structuring.</p>
			</richtext>
		</abstract>
		<pages>67-77</pages>
		<title type="sharef:primaryTitle">An Architectural Concept for Knowledge Integration in Inter-Administration Computing</title>
		<identifier type="sharef:uri" resourceType="application/pdf">http://falcon.ifs.uni-linz.ac.at/KMGov2002/kmgov2.pdf</identifier>
	</reference>
	<reference name="kmgov2002" src="bibtex:proceedings" src-info="bibtex:line-18511" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>Maria A.</givenname>
				<surname>Wimmer</surname>
			</person>
		</names>
		<date value="2002-05"/>
		<address type="sharef:placePublished">Copenhagen, Denmark</address>
		<field type="bibtex:index">KMGov 2002</field>
		<identifier type="sharef:isbn">3-85487-409-X</identifier>
		<publisher>Trauner Verlag</publisher>
		<title type="sharef:seriesTitle">Schriftenreihe Informatik</title>
		<title type="sharef:primaryTitle">3rd International Workshop on Knowledge Management in e-Government</title>
		<identifier type="sharef:uri" resourceType="text/html">http://falcon.ifs.uni-linz.ac.at/KMGov2002/content.html</identifier>
		<identifier type="sharef:uri" resourceType="application/pdf">http://falcon.ifs.uni-linz.ac.at/KMGov2002/kmgov2.pdf</identifier>
		<volume>7</volume>
	</reference>
	<reference name="joi03" src="bibtex:inproceedings" src-info="bibtex:line-18531" type="sharef:inproceedings" crossref="kmgov2003">
		<names type="sharef:author">
			<person>
				<givenname>Luiz Antonio</givenname>
				<surname>Joia</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Electronic Government has proven a watershed in the domain of Public Administration, despite being difficult to pin down precisely. Indeed, the Government-to-Government arena is one of the least studied aspects of this newly established field of knowledge, despite its importance in fostering co-operation and collaboration between government agencies, mainly with respect to the management of their knowledge, in order to increase the effectiveness of Public Administration. This paper aims to present the key success factors needed to implement government-to-government endeavours effectively. The research design used in this article was largely drawn from a Government-to-Government case study successfully implemented in Brazil.</p>
			</richtext>
		</abstract>
		<pages>76-81</pages>
		<title type="sharef:primaryTitle">Key Success Factors for Electronic Inter-organisational Co-operation between Government Agencies</title>
		<identifier type="sharef:uri" resourceType="text/html">http://link.springer.de/link/service/series/0558/bibs/2645/26450076.htm</identifier>
	</reference>
	<reference name="ger03" src="bibtex:inproceedings" src-info="bibtex:line-18540" type="sharef:inproceedings" crossref="kmgov2003">
		<names type="sharef:author">
			<person>
				<givenname>Stelios</givenname>
				<surname>Gerogiannakis</surname>
			</person>
			<person>
				<givenname>Marios</givenname>
				<surname>Sintichakis</surname>
			</person>
			<person>
				<givenname>Nikos</givenname>
				<surname>Achilleopoulos</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Corporate memories (stored information and internal processes) in both private and public organizations grow at an exponential rate. This growth is not only quantitative but also qualitative, in the form of increasing interdependencies between processes and information bits. Although the quantitative growth is relatively easy to handle, increasing information complexity is constantly pushing existing information systems to their limits. It is slowly becoming a self-proving fact that organizations will have to transition from the traditional model of searchable/updatable repositories of "facts and figures" to self-organizing, self-adapting corporate knowledge management systems. Ontologies and Semantic Web principles are the most promising relevant technology, now entering their mature age, allowing the creation of extensible vocabularies able to describe any semantic area. Project ONTO-LOGGING is an attempt to harness the full potential of ontologies as a flexible tool of knowledge management within any knowledge-driven organization, such as corporations and public ad-ministrations.</p>
			</richtext>
		</abstract>
		<pages>127-138</pages>
		<title type="sharef:primaryTitle">Collaborative Knowledge Management and Ontologies: The ONTO-LOGGING Platform</title>
		<identifier type="sharef:uri" resourceType="text/html">http://link.springer.de/link/service/series/0558/bibs/2645/26450127.htm</identifier>
	</reference>
	<reference name="kmgov2003" src="bibtex:proceedings" src-info="bibtex:line-18549" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>Maria A.</givenname>
				<surname>Wimmer</surname>
			</person>
		</names>
		<date value="2003-05"/>
		<address type="sharef:placePublished">Rhodes, Greece</address>
		<field type="bibtex:index">KMGov 2003</field>
		<identifier type="sharef:isbn">3-540-40145-8</identifier>
		<publisher>Springer-Verlag</publisher>
		<title type="sharef:seriesTitle">Lecture Notes in Computer Science</title>
		<title type="sharef:primaryTitle">4th IFIP International Working Conference on Knowledge Management in Electronic Government</title>
		<identifier type="sharef:uri" resourceType="text/html">http://www.informatik.uni-trier.de/~ley/db/conf/kmgov/kmgov2003.html</identifier>
		<volume>2645</volume>
	</reference>
	<reference name="han04" src="bibtex:inproceedings" src-info="bibtex:line-18568" type="sharef:inproceedings" crossref="kmgov2004">
		<names type="sharef:author">
			<person>
				<givenname>Meliha</givenname>
				<surname>Handzic</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>This paper explores the role of knowledge mapping in electronic government. It begins by outlining the rationale for knowledge mapping. It then reviews different conceptualisations of knowledge maps. These include concept, competency and process based maps. Then, it illustrates the application of these maps in a series of examples from the Australian government websites. The paper concludes by identifying some major issues and challenges for the future of knowledge mapping in electronic government.</p>
			</richtext>
		</abstract>
		<pages>9-17</pages>
		<title type="sharef:primaryTitle">The Role of Knowledge Mapping in Electronic Government</title>
		<identifier type="sharef:uri">http://springerlink.metapress.com/openurl.asp?genre=article&amp;issn=0302-9743&amp;volume=3035&amp;spage=2</identifier>
	</reference>
	<reference name="kmgov2004" src="bibtex:proceedings" src-info="bibtex:line-18577" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>Maria A.</givenname>
				<surname>Wimmer</surname>
			</person>
		</names>
		<date value="2004-05"/>
		<address type="sharef:placePublished">Krems, Austria</address>
		<identifier type="sharef:doi">10.1007/b97726</identifier>
		<field type="bibtex:index">KMGov 2004</field>
		<identifier type="sharef:isbn">3-540-22002-X</identifier>
		<publisher>Springer-Verlag</publisher>
		<title type="sharef:seriesTitle">Lecture Notes in Computer Science</title>
		<title type="sharef:primaryTitle">5th IFIP International Working Conference on Knowledge Management in Electronic Government</title>
		<identifier type="sharef:uri" resourceType="text/html">http://www.informatik.uni-trier.de/~ley/db/conf/kmgov/kmgov2004.html</identifier>
		<volume>3035</volume>
	</reference>
	<reference name="goh00" src="bibtex:inproceedings" src-info="bibtex:line-18597" type="sharef:inproceedings" crossref="dl2000">
		<names type="sharef:author">
			<person>
				<givenname>Dion</givenname>
				<surname>Goh</surname>
			</person>
			<person>
				<givenname>John J.</givenname>
				<surname>Leggett</surname>
			</person>
		</names>
		<identifier type="sharef:doi">10.1145/336597.336656</identifier>
		<pages>153-163</pages>
		<title type="sharef:primaryTitle">Patron-Augmented Digital Libraries</title>
	</reference>
	<reference name="wol00" src="bibtex:inproceedings" src-info="bibtex:line-18605" type="sharef:inproceedings" crossref="dl2000">
		<names type="sharef:author">
			<person>
				<givenname>Joanna L.</givenname>
				<surname>Wolfe</surname>
			</person>
		</names>
		<identifier type="sharef:doi">10.1145/336597.336620</identifier>
		<pages>19-26</pages>
		<title type="sharef:primaryTitle">Effects of Annotations on Student Readers and Writers</title>
	</reference>
	<reference name="dl2000" src="bibtex:proceedings" src-info="bibtex:line-18613" type="sharef:proceedings">
		<date value="2000-06"/>
		<address type="sharef:placePublished">San Antonio, Texas</address>
		<identifier type="sharef:isbn">158113231X</identifier>
		<publisher>ACM Press</publisher>
		<title type="sharef:primaryTitle">Fifth ACM Conference on Digital Libraries</title>
		<identifier type="sharef:uri">http://portal.acm.org/citation.cfm?id=336597&amp;coll=GUIDE&amp;dl=GUIDE&amp;CFID=8009143&amp;CFTOKEN=15786869</identifier>
	</reference>
	<reference name="fra01" src="bibtex:inproceedings" src-info="bibtex:line-18628" type="sharef:inproceedings" crossref="jcdl2001">
		<names type="sharef:author">
			<person>
				<givenname>Luis</givenname>
				<surname>Francisco-Revilla</surname>
			</person>
			<person>
				<givenname>Frank M.</givenname>
				<surname>Shipman</surname>
			</person>
			<person>
				<givenname>Richard</givenname>
				<surname>Furuta</surname>
			</person>
			<person>
				<givenname>Unmil</givenname>
				<surname>Karadkar</surname>
			</person>
			<person>
				<givenname>Avital</givenname>
				<surname>Arora</surname>
			</person>
		</names>
		<identifier type="sharef:doi">10.1145/379437.379973</identifier>
		<pages>67-76</pages>
		<title type="sharef:primaryTitle">Managing Change on the Web</title>
	</reference>
	<reference name="jcdl2001" src="bibtex:proceedings" src-info="bibtex:line-18636" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>Edward A.</givenname>
				<surname>Fox</surname>
			</person>
			<person>
				<givenname>Christine L.</givenname>
				<surname>Borgman</surname>
			</person>
		</names>
		<date value="2001-06"/>
		<address type="sharef:placePublished">Roanoke, Virginia</address>
		<field type="bibtex:index">JCDL 2001</field>
		<identifier type="sharef:isbn">1581133456</identifier>
		<publisher>ACM Press</publisher>
		<title type="sharef:primaryTitle">First ACM/IEEE-CS Joint Conference on Digital Libraries</title>
		<identifier type="sharef:uri">http://www.acm.org/pubs/contents/proceedings/dl/379437/</identifier>
	</reference>
	<reference name="bar02" src="bibtex:inproceedings" src-info="bibtex:line-18653" type="sharef:inproceedings" crossref="jcdl2002">
		<names type="sharef:author">
			<person>
				<givenname>Bruce R.</givenname>
				<surname>Barkstrom</surname>
			</person>
			<person>
				<givenname>Melinda</givenname>
				<surname>Finch</surname>
			</person>
			<person>
				<givenname>Michelle</givenname>
				<surname>Ferebee</surname>
			</person>
			<person>
				<givenname>Calvin</givenname>
				<surname>Mackey</surname>
			</person>
		</names>
		<identifier type="sharef:doi">10.1145/544220.544272</identifier>
		<pages>242-243</pages>
		<title type="sharef:primaryTitle">Adapting Digital Libraries to Continual Evolution</title>
	</reference>
	<reference name="kel02" src="bibtex:inproceedings" src-info="bibtex:line-18661" type="sharef:inproceedings" crossref="jcdl2002">
		<names type="sharef:author">
			<person>
				<givenname>Anna</givenname>
				<surname>Keller Gold</surname>
			</person>
			<person>
				<givenname>Karen S.</givenname>
				<surname>Baker</surname>
			</person>
			<person>
				<givenname>Jean-Yves</givenname>
				<surname>LeMeur</surname>
			</person>
			<person>
				<givenname>Kim</givenname>
				<surname>Baldridge</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Individuals, teams, organizations, and networks can be thought of as tiers or classes within the complex grid of technology and practice in which research documentation is both consumed and generated. The panoply of possible classes share with the others a common need for document management tools and practices. The distinctive document management tools and practices used within each represent boundaries across which information could flow openly if technology and metadata standards were to provide an accessible digital framework. The CERN Document Server (CDS), implemented by a research partnership at the San Diego Supercomputer Center (SDSC), establishes a prototype tiered repository system for such a panoply. Research suggests modifications to enable cross-domain information flow and is represented as a metadata grid.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/544220.544286</identifier>
		<pages>287-288</pages>
		<title type="sharef:primaryTitle">Building FLOW: Federating Libraries on the Web</title>
		<field type="bibtex:topic">flow[0.9]</field>
	</reference>
	<reference name="wit02b" src="bibtex:inproceedings" src-info="bibtex:line-18672" type="sharef:inproceedings" crossref="jcdl2002">
		<names type="sharef:author">
			<person>
				<givenname>Ian H.</givenname>
				<surname>Witten</surname>
			</person>
			<person>
				<givenname>David</givenname>
				<surname>Bainbridge</surname>
			</person>
			<person>
				<givenname>Gordon</givenname>
				<surname>Paynter</surname>
			</person>
			<person>
				<givenname>Stefan</givenname>
				<surname>Boddie</surname>
			</person>
		</names>
		<identifier type="sharef:doi">10.1145/544220.544285</identifier>
		<pages>285-286</pages>
		<title type="sharef:primaryTitle">The Greenstone Plugin Architecture</title>
	</reference>
	<reference name="jcdl2002" src="bibtex:proceedings" src-info="bibtex:line-18680" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>Gary</givenname>
				<surname>Marchionini</surname>
			</person>
		</names>
		<date value="2002-07"/>
		<address type="sharef:placePublished">Portland, Oregon</address>
		<field type="bibtex:index">JCDL 2002</field>
		<identifier type="sharef:isbn">1581135130</identifier>
		<publisher>ACM Press</publisher>
		<title type="sharef:primaryTitle">Second ACM/IEEE-CS Joint Conference on Digital Libraries</title>
		<identifier type="sharef:uri">http://portal.acm.org/toc.cfm?id=544220&amp;type=proceeding&amp;coll=GUIDE&amp;dl=GUIDE&amp;CFID=4159161&amp;CFTOKEN=57059566</identifier>
	</reference>
	<reference name="ren03" src="bibtex:inproceedings" src-info="bibtex:line-18697" type="sharef:inproceedings" crossref="jcdl2003">
		<names type="sharef:author">
			<person>
				<givenname>Allen</givenname>
				<surname>Renear</surname>
			</person>
			<person>
				<givenname>David</givenname>
				<surname>Dubin</surname>
			</person>
			<person>
				<givenname>C. Michael</givenname>
				<surname>Sperberg-McQueen</surname>
			</person>
			<person>
				<givenname>Claus</givenname>
				<surname>Huitfeldt</surname>
			</person>
		</names>
		<pages>303-305</pages>
		<title type="sharef:primaryTitle">XML Semantics and Digital Libraries</title>
		<identifier type="sharef:uri">http://portal.acm.org/citation.cfm?id=827192&amp;coll=GUIDE&amp;dl=ACM&amp;CFID=15973361&amp;CFTOKEN=72837831</identifier>
	</reference>
	<reference name="bak03" src="bibtex:inproceedings" src-info="bibtex:line-18705" type="sharef:inproceedings" crossref="jcdl2003">
		<names type="sharef:author">
			<person>
				<givenname>Karen S.</givenname>
				<surname>Baker</surname>
			</person>
			<person>
				<givenname>Anna</givenname>
				<surname>Keller Gold</surname>
			</person>
			<person>
				<givenname>Frank</givenname>
				<surname>Sudholt</surname>
			</person>
		</names>
		<pages>397</pages>
		<title type="sharef:primaryTitle">FLOW: Co-constructing Low Barrier Repository Infrastructure in Support of Heterogeneous Knowledge Collection(s)</title>
		<field type="bibtex:topic">flow[0.9]</field>
		<identifier type="sharef:uri">http://portal.acm.org/citation.cfm?id=827228&amp;coll=Portal&amp;dl=ACM&amp;CFID=15973361&amp;CFTOKEN=72837831</identifier>
	</reference>
	<reference name="jcdl2003" src="bibtex:proceedings" src-info="bibtex:line-18714" type="sharef:proceedings">
		<date value="2003-05"/>
		<address type="sharef:placePublished">Houston, Texas</address>
		<field type="bibtex:index">JCDL 2003</field>
		<identifier type="sharef:isbn">0769519393</identifier>
		<publisher>ACM Press</publisher>
		<title type="sharef:primaryTitle">Third ACM/IEEE-CS Joint Conference on Digital Libraries</title>
		<identifier type="sharef:uri" resourceType="text/html">http://www.informatik.uni-trier.de/~ley/db/conf/jcdl/jcdl2003.html</identifier>
		<identifier type="sharef:uri">http://portal.acm.org/toc.cfm?id=827140&amp;type=proceeding&amp;coll=Portal&amp;dl=ACM&amp;CFID=15973361&amp;CFTOKEN=72837831</identifier>
	</reference>
	<reference name="mar04c" src="bibtex:inproceedings" src-info="bibtex:line-18731" type="sharef:inproceedings" crossref="jcdl2004">
		<names type="sharef:author">
			<person>
				<givenname>Catherine C.</givenname>
				<surname>Marshall</surname>
			</person>
			<person>
				<givenname>Sara A.</givenname>
				<surname>Bly</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>As part of a more extensive study of reading-related practices, we have explored how people share information they encounter in their everyday reading as a complement to the more traditional digital library focus on sharing intentionally retrieved materials. In twenty contextual interviews in home and work place settings, we investigated how people encounter and save published material in the form of paper and electronic clippings. We found that sharing forms a significant use for encountered materials. Furthermore, the function of these clippings extends far beyond a simple exchange of content to inform the recipient; in fact, the content itself may have little immediate value to the recipient. We also found the practice to be ubiquitous: all of our participants had both shared clippings with others and received them themselves. Specifically, this paper reports on: (1) how sharing encountered items fits into the broader spectrum of clipping practices; (2) the function and value of the shared information; and (3) the social role of sharing the encountered information. We conclude that from a technological standpoint, we should think beyond an email model for sharing encountered information and, from a social perspective, we should attend to how sharing this sort of material contributes to the strength of social ties outside of a traditional information needs framework.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/996401</identifier>
		<pages>218-227</pages>
		<title type="sharef:primaryTitle">Sharing Encountered Information: Digital Libraries get a Social Life</title>
		<identifier type="sharef:uri">http://portal.acm.org/citation.cfm?doid=996401</identifier>
	</reference>
	<reference name="mar04d" src="bibtex:inproceedings" src-info="bibtex:line-18741" type="sharef:inproceedings" crossref="jcdl2004">
		<names type="sharef:author">
			<person>
				<givenname>Catherine C.</givenname>
				<surname>Marshall</surname>
			</person>
			<person>
				<givenname>A. J. Bernheim</givenname>
				<surname>Brush</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Today people typically read and annotate printed documents even if they are obtained from electronic sources like digital libraries. If there is a reason for them to share these personal annotations online, they must re-enter them. Given the advent of better computer support for reading and annotation, including tablet interfaces, will people ever share their personal digital ink annotations as is, or will they make substantial changes to them? What can we do to anticipate and support the transition from personal to public annotations? To investigate these questions, we performed a study to characterize and compare students' personal annotations as they read assigned papers with those they shared with each other using an online system. By analyzing over 1, 700 annotations, we confirmed three hypotheses: (1) only a small fraction of annotations made while reading are directly related to those shared in discussion; (2) some types of annotations — those that consist of anchors in the text coupled with margin notes — are more apt to be the basis of public commentary than other types of annotations; and (3) personal annotations undergo dramatic changes when they are shared in discussion, both in content and in how they are anchored to the source document. We then use these findings to explore ways to support the transition from personal to public annotations.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/996432</identifier>
		<pages>349-357</pages>
		<title type="sharef:primaryTitle">Exploring the Relationship between Personal and Public Annotations</title>
		<identifier type="sharef:uri">http://portal.acm.org/citation.cfm?doid=996432</identifier>
	</reference>
	<reference name="naa04" src="bibtex:inproceedings" src-info="bibtex:line-18751" type="sharef:inproceedings" crossref="jcdl2004">
		<names type="sharef:author">
			<person>
				<givenname>Mor</givenname>
				<surname>Naaman</surname>
			</person>
			<person>
				<givenname>Yee Jiun</givenname>
				<surname>Song</surname>
			</person>
			<person>
				<givenname>Andreas</givenname>
				<surname>Paepcke</surname>
			</person>
			<person>
				<givenname>Hector</givenname>
				<surname>Garcia-Molina</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>We describe PhotoCompas, a system that utilizes the time and location information embedded in digital photographs to automatically organize a personal photo collection. PhotoCompas produces browseable location and event hierarchies for the collection. These hierarchies are created using algorithms that interleave time and location to produce an organization that mimics the way people think about their photo collections. In addition, our algorithm annotates the generated hierarchy with geographical names. We tested our approach in case studies of three real-world collections and verified that the results are meaningful and useful for the collection owners.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/996350.996366</identifier>
		<pages>53-62</pages>
		<title type="sharef:primaryTitle">Automatic Organization for Digital Photographs with Geographic Coordinates</title>
	</reference>
	<reference name="jcdl2004" src="bibtex:proceedings" src-info="bibtex:line-18760" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>Hsinchun</givenname>
				<surname>Chen</surname>
			</person>
			<person>
				<givenname>Howard D.</givenname>
				<surname>Wactlar</surname>
			</person>
			<person>
				<givenname>Ching</givenname>
				<surname link="chih">Chen</surname>
			</person>
			<person>
				<givenname>Ee-Peng</givenname>
				<surname>Lim</surname>
			</person>
			<person>
				<givenname>Michael G.</givenname>
				<surname>Christel</surname>
			</person>
		</names>
		<date value="2004-06"/>
		<address type="sharef:placePublished">Tucson, Arizona</address>
		<field type="bibtex:index">JCDL 2004</field>
		<identifier type="sharef:isbn">1-58113-832-6</identifier>
		<publisher>ACM Press</publisher>
		<title type="sharef:primaryTitle">Fourth ACM/IEEE Joint Conference on Digital Libraries</title>
		<identifier type="sharef:uri" resourceType="text/html">http://www.informatik.uni-trier.de/~ley/db/conf/jcdl/jcdl2004.html</identifier>
	</reference>
	<reference name="iac05a" src="bibtex:inproceedings" src-info="bibtex:line-18777" type="sharef:inproceedings" crossref="jcdl2005">
		<names type="sharef:author">
			<person>
				<givenname>Ionut Emil</givenname>
				<surname>Iacob</surname>
			</person>
			<person>
				<givenname>Alex</givenname>
				<surname>Dekhtyar</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>The process of authoring document-centric XML documents in humanities disciplines is very different from the approach espoused by the standard XML editing software with the data-centric view of XML. Where data-centric XML is generated by first describing a tree structure of the encoding and then providing the content for the leaf elements, document-centric encodings start with content which is then marked up. In the paper we describe our approach to authoring document-centric XML documents and the tool, xTagger, originally developed for this purpose within the Electronic Boethius project, otherwise enhanced within the ARCHway project, an interdisciplinary project devoted to development of methods and software for preparation of image-based electronic editions of historic manuscripts.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/1065395</identifier>
		<pages>44-45</pages>
		<title type="sharef:primaryTitle">xTagger: A New Approach to Authoring Document-Centric XML</title>
		<identifier type="sharef:uri">http://portal.acm.org/citation.cfm?doid=1065395</identifier>
	</reference>
	<reference name="iac05b" src="bibtex:inproceedings" src-info="bibtex:line-18787" type="sharef:inproceedings" crossref="jcdl2005">
		<names type="sharef:author">
			<person>
				<givenname>Ionut Emil</givenname>
				<surname>Iacob</surname>
			</person>
			<person>
				<givenname>Alex</givenname>
				<surname>Dekhtyar</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>The problem of overlapping markup hierarchies, first mentioned in the context of SGML, often occurs in XML text encoding applications for humanities. Previous solutions to the problem rely on manual maintenance of the markup and address only the problem of representing overlapping features in XML, leaving the issues of automated maintenance and querying open. As a consequence, traditional XML tools are of little practical use when dealing with overlapping markup. In this work we demonstrate the implementation of our framework for management of concurrent XML hierarchies from a computer science perspective. We propose an underlying model, data structures, APIs, and algorithms so that the most of the burden of managing concurrent XML hierarchies would be born by the software.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/1065513</identifier>
		<pages>409</pages>
		<title type="sharef:primaryTitle">Processing XML Documents with Overlapping Hierarchies</title>
		<field type="bibtex:topic">goddag[0.8]</field>
		<identifier type="sharef:uri">http://portal.acm.org/citation.cfm?doid=1065513</identifier>
	</reference>
	<reference name="jcdl2005" src="bibtex:proceedings" src-info="bibtex:line-18798" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>Mary</givenname>
				<surname>Marlino</surname>
			</person>
			<person>
				<givenname>Tamara</givenname>
				<surname>Sumner</surname>
			</person>
			<person>
				<givenname>Frank M.</givenname>
				<surname>Shipman</surname>
			</person>
		</names>
		<date value="2005-06"/>
		<address type="sharef:placePublished">Denver, Colorado</address>
		<field type="bibtex:index">JCDL 2005</field>
		<identifier type="sharef:isbn">1-58113-876-8</identifier>
		<publisher>ACM Press</publisher>
		<title type="sharef:primaryTitle">Fifth ACM/IEEE Joint Conference on Digital Libraries</title>
		<identifier type="sharef:uri" resourceType="text/html">http://www.informatik.uni-trier.de/~ley/db/conf/jcdl/jcdl2005.html</identifier>
	</reference>
	<reference name="car06" src="bibtex:inproceedings" src-info="bibtex:line-18815" type="sharef:inproceedings" crossref="jcdl2006">
		<names type="sharef:author">
			<person>
				<givenname>Moisés G.</givenname>
				<surname link="de">Carvalho</surname>
			</person>
			<person>
				<givenname>Marcos André</givenname>
				<surname>Gonçalves</surname>
			</person>
			<person>
				<givenname>Alberto H. F.</givenname>
				<surname>Laender</surname>
			</person>
			<person>
				<givenname>Altigran S.</givenname>
				<surname link="da">Silva</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Identifying record replicas in Digital Libraries and other types of digital repositories is fundamental to improve the quality of their content and services as well as to yield eventual sharing efforts. Several deduplication strategies are available, but most of them rely on manually chosen settings to combine evidence used to identify records as being replicas. In this paper, we present the results of experiments we have carried out with a novel Machine Learning approach we have proposed for the deduplication problem. This approach, based on Genetic Programming (GP), is able to automatically generate similarity functions to identify record replicas in a given repository. The generated similarity functions properly combine and weight the best evidence available among the record fields in order to tell when two distinct records represent the same real-world entity. The results of the experiments show that our approach outperforms the baseline method by Fellegi and Sunter by more than 12% when identifying replicas in a data set containing researcher's personal data, and by more than 7%, in a data set with article citation data.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/1141753.1141760</identifier>
		<pages>41-50</pages>
		<title type="sharef:primaryTitle">Learning to Deduplicate</title>
	</reference>
	<reference name="jcdl2006" src="bibtex:proceedings" src-info="bibtex:line-18824" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>Gary</givenname>
				<surname>Marchionini</surname>
			</person>
			<person>
				<givenname>Michael L.</givenname>
				<surname>Nelson</surname>
			</person>
			<person>
				<givenname>Catherine C.</givenname>
				<surname>Marshall</surname>
			</person>
		</names>
		<date value="2006-06"/>
		<address type="sharef:placePublished">Chapel Hill, North Carolina</address>
		<field type="bibtex:index">JCDL 2006</field>
		<identifier type="sharef:isbn">1-59593-354-9</identifier>
		<publisher>ACM Press</publisher>
		<title type="sharef:primaryTitle">Sixth ACM/IEEE Joint Conference on Digital Libraries</title>
		<identifier type="sharef:uri" resourceType="text/html">http://www.informatik.uni-trier.de/~ley/db/conf/jcdl/jcdl2006.html</identifier>
	</reference>
	<reference name="phe01" src="bibtex:inproceedings" src-info="bibtex:line-18841" type="sharef:inproceedings" crossref="doceng01">
		<names type="sharef:author">
			<person>
				<givenname>Thomas Arthur</givenname>
				<surname>Phelps</surname>
			</person>
			<person>
				<givenname>Robert</givenname>
				<surname>Wilensky</surname>
			</person>
		</names>
		<field type="bibtex:index">http://www.cs.berkeley.edu/~phelps/Multivalent/papers/doceng2001.pdf</field>
		<title type="sharef:primaryTitle">The Multivalent Browser: A Platform for New Ideas</title>
	</reference>
	<reference name="toz01" src="bibtex:inproceedings" src-info="bibtex:line-18848" type="sharef:inproceedings" crossref="doceng01">
		<names type="sharef:author">
			<person>
				<givenname>Akihiko</givenname>
				<surname>Tozawa</surname>
			</person>
		</names>
		<identifier type="sharef:doi">10.1145/502187.502191</identifier>
		<title type="sharef:primaryTitle">Towards Static Type Checking for XSLT</title>
		<field type="bibtex:topic">xslt1[0.9]</field>
	</reference>
	<reference name="doceng01" src="bibtex:proceedings" src-info="bibtex:line-18856" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>Ethan V.</givenname>
				<surname>Munson</surname>
			</person>
		</names>
		<date value="2001-11"/>
		<address type="sharef:placePublished">Atlanta, Georgia</address>
		<field type="bibtex:index">DocEng '01</field>
		<title type="sharef:primaryTitle">Document Engineering 2001</title>
	</reference>
	<reference name="ren02" src="bibtex:inproceedings" src-info="bibtex:line-18870" type="sharef:inproceedings" crossref="doceng2002">
		<names type="sharef:author">
			<person>
				<givenname>Allen</givenname>
				<surname>Renear</surname>
			</person>
			<person>
				<givenname>David</givenname>
				<surname>Dubin</surname>
			</person>
			<person>
				<givenname>C. Michael</givenname>
				<surname>Sperberg-McQueen</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Although XML Document Type Definitions provide a mechanism for specifying, in machine-readable form, the syntax of an XML markup language, there is no comparable mechanism for specifying the semantics of an XML vocabulary. That is, there is no way to characterize the meaning of XML markup so that the facts and relationships represented by the occurrence of XML constructs can be explicitly, comprehensively, and mechanically identified. This has serious practical and theoretical consequences. On the positive side, XML constructs can be assigned arbitrary semantics and used in application areas not foreseen by the original designers. On the less positive side, both content developers and application engineers must rely upon prose documentation, or, worse, conjectures about the intention of the markup language designer — a process that is time-consuming, error-prone, incomplete, and unverifiable, even when the language designer properly documents the language. In addition, the lack of a substantial body of research in markup semantics means that digital document processing is undertheorized as an engineering application area. Although there are some related projects underway (XML Schema, RDF, the Semantic Web) which provide relevant results, none of these projects directly and comprehensively address the core problems of XML markup semantics. This paper (i) summarizes the history of the concept of markup meaning, (ii) characterizes the specific problems that motivate the need for a formal semantics for XML and (iii) describes an ongoing research project — the BECHAMEL Markup Semantics Project — that is attempting to develop such a semantics.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/585058.585081</identifier>
		<pages>119-126</pages>
		<title type="sharef:primaryTitle">Towards a Semantics for XML Markup</title>
		<identifier type="sharef:uri">http://portal.acm.org/citation.cfm?id=827192</identifier>
	</reference>
	<reference name="cia02" src="bibtex:inproceedings" src-info="bibtex:line-18880" type="sharef:inproceedings" crossref="doceng2002">
		<names type="sharef:author">
			<person>
				<givenname>Paolo</givenname>
				<surname>Ciancarini</surname>
			</person>
			<person>
				<givenname>Federico</givenname>
				<surname>Folli</surname>
			</person>
			<person>
				<givenname>Davide</givenname>
				<surname>Rossi</surname>
			</person>
			<person>
				<givenname>Fabio</givenname>
				<surname>Vitali</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>In the linking model of the World Wide Web each link is stored in the referring document within an attribute of the A tag. All the hyperlink defined this way can reference a single resource or a single fragment. With the evolution of Web technologies more powerful linking languages (XLink and XPointer) have been proposed. Here we introduce XLinkProxy, a Web application that allows sophisticated hyperlink (defined using XLink and XPointer) to be defined outside referring documents, giving users the chance to build dynamic multidestination, multidirectional links databases. XLinkProxy has been designed in order to be used with standard Web browsers and is implemented as a filtering HTTP proxy.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/585058.585070</identifier>
		<pages>57-65</pages>
		<title type="sharef:primaryTitle">XLinkProxy: External Linkbases with XLink</title>
		<field type="bibtex:topic">xlink[0.7]</field>
	</reference>
	<reference name="glu02" src="bibtex:inproceedings" src-info="bibtex:line-18890" type="sharef:inproceedings" crossref="doceng2002">
		<names type="sharef:author">
			<person>
				<givenname>Robert J.</givenname>
				<surname>Glushko</surname>
			</person>
			<person>
				<givenname>Tim</givenname>
				<surname>McGrath</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>It can be said that "document exchange" is the "mother of all patterns" for business (and for e-business). Yet, by itself this view isn't sufficiently prescriptive. In this paper, we present additional perspectives or frameworks that make this abstraction more rigorous and useful. We describe an approach to artifact-driven analysis, model refinement, and implementation for document-intensive systems that unifies the "document analysis" approach from publishing and the "data analysis" approach from information systems. These traditionally contrasting approaches to understanding documents are unified in an "Analysis Spectrum" in which presentational, structural, and content components assume different weights or status. Our methodology emphasizes reuse with a "Reuse Matrix," in which both business process (or document exchange) patterns and document schema patterns are organized by different levels of abstraction and scope. Enterprise-level patterns like "supply chain" and "marketplace" can fit into this matrix along with process patterns like "RosettaNet PIP" and document patterns like the "XML Common Business Library." Taken together, these concepts form the foundation of a new discipline: "Document Engineering for e-Business.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/585058.585067</identifier>
		<pages>42-48</pages>
		<title type="sharef:primaryTitle">Document Engineering for E-Business</title>
		<identifier type="sharef:uri" resourceType="application/pdf">http://www.ischool.berkeley.edu/~glushko/glushko_files/p12-glushko.pdf</identifier>
	</reference>
	<reference name="doceng2002" src="bibtex:proceedings" src-info="bibtex:line-18900" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>Ethan V.</givenname>
				<surname>Munson</surname>
			</person>
			<person>
				<givenname>Richard</givenname>
				<surname>Furuta</surname>
			</person>
			<person>
				<givenname>Jonathan I.</givenname>
				<surname>Maletic</surname>
			</person>
		</names>
		<date value="2002-11"/>
		<address type="sharef:placePublished">McLean, Virginia</address>
		<publisher>ACM Press</publisher>
		<title type="sharef:primaryTitle">2002 ACM Symposium on Document Engineering</title>
		<identifier type="sharef:uri">http://portal.acm.org/toc.cfm?id=585058&amp;type=proceeding&amp;coll=GUIDE&amp;dl=ACM&amp;CFID=15973361&amp;CFTOKEN=72837831</identifier>
	</reference>
	<reference name="ghe03" src="bibtex:inproceedings" src-info="bibtex:line-18915" type="sharef:inproceedings" crossref="sosp03">
		<names type="sharef:author">
			<person>
				<givenname>Sanjay</givenname>
				<surname>Ghemawat</surname>
			</person>
			<person>
				<givenname>Howard</givenname>
				<surname>Gobioff</surname>
			</person>
			<person>
				<givenname>Shun-Tak</givenname>
				<surname>Leung</surname>
			</person>
		</names>
		<identifier type="sharef:doi">10.1145/945450</identifier>
		<pages>29-43</pages>
		<title type="sharef:primaryTitle">The Google File System</title>
		<field type="bibtex:topic">google[1]</field>
		<identifier type="sharef:uri" resourceType="application/pdf">http://www.cs.rochester.edu/sosp2003/papers/p125-ghemawat.pdf</identifier>
	</reference>
	<reference name="sosp03" src="bibtex:proceedings" src-info="bibtex:line-18925" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>Cécile</givenname>
				<surname>Roisin</surname>
			</person>
			<person>
				<givenname>Ethan V.</givenname>
				<surname>Munson</surname>
			</person>
			<person>
				<givenname>Christine</givenname>
				<surname>Vanoirbeek</surname>
			</person>
		</names>
		<date value="2003-10"/>
		<address type="sharef:placePublished">Bolton Landing, New York</address>
		<field type="bibtex:index">SOSP 2003</field>
		<title type="sharef:primaryTitle">19th ACM Symposium on Operating Systems Principles</title>
		<identifier type="sharef:uri">http://www.cs.rochester.edu/sosp2003/</identifier>
		<identifier type="sharef:uri" resourceType="text/html">http://www.informatik.uni-trier.de/~ley/db/conf/sosp/sosp2003.html</identifier>
	</reference>
	<reference name="oki93" src="bibtex:inproceedings" src-info="bibtex:line-18941" type="sharef:inproceedings" crossref="sosp93">
		<names type="sharef:author">
			<person>
				<givenname>Brian M.</givenname>
				<surname>Oki</surname>
			</person>
			<person>
				<givenname>Manfred</givenname>
				<surname>Pflügl</surname>
			</person>
			<person>
				<givenname>Alex</givenname>
				<surname>Siegel</surname>
			</person>
			<person>
				<givenname>Dale</givenname>
				<surname>Skeen</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Research can rarely be performed on large-scale, distributed systems at the level of thousands of workstations. In this paper, we describe the motivating constraints, design principles, and architecture for an extensible, distributed system operating in such an environment. The constraints include continuous operation, dynamic system evolution, and integration with extant systems. The Information Bus, our solution, is a novel synthesis of four design principles: core communication protocols have minimal semantics, objects are self-describing, types can be dynamically defined, and communication is anonymous. The current implementation provides both flexibility and high performance, and has been proven in several commercial environments, including integrated circuit fabrication plants and brokerage/trading floors.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/168619.168624</identifier>
		<pages>58-68</pages>
		<title type="sharef:primaryTitle">The Information Bus: An Architecture for Extensible Distributed Systems</title>
	</reference>
	<reference name="sosp93" src="bibtex:proceedings" src-info="bibtex:line-18950" type="sharef:proceedings">
		<date value="1993-12"/>
		<address type="sharef:placePublished">Asheville, North Carolina</address>
		<field type="bibtex:index">SOSP 1993</field>
		<title type="sharef:primaryTitle">14th ACM Symposium on Operating Systems Principles</title>
		<identifier type="sharef:uri" resourceType="text/html">http://www.informatik.uni-trier.de/~ley/db/conf/sosp/sosp93.html</identifier>
	</reference>
	<reference name="fer03" src="bibtex:inproceedings" src-info="bibtex:line-18964" type="sharef:inproceedings" crossref="doceng03">
		<names type="sharef:author">
			<person>
				<givenname>Christer</givenname>
				<surname>Fernstrom</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>We discuss how references and citations within a document to particular sources can be verified and guaranteed. When a document refers through a quotation to another document, the reader should be able to verify that the reference is correct and that any quotation correctly represents the original text. The mechanism we describe enables the authentication of such quotations. It consists of:A notation to be used when expressing quotations. This notation allows a controlled degree of freedom to make alterations from the original text. Different means to check the correctness of such quotations with respect to the cited documents and to quotation rules.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/958220.958263</identifier>
		<title type="sharef:primaryTitle">Management of Trusted Citations</title>
	</reference>
	<reference name="jan03" src="bibtex:inproceedings" src-info="bibtex:line-18972" type="sharef:inproceedings" crossref="doceng03">
		<names type="sharef:author">
			<person>
				<givenname>William C.</givenname>
				<surname>Janssen</surname>
			</person>
			<person>
				<givenname>Kris</givenname>
				<surname>Popat</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>We describe the design and use of a personal digital library system, UpLib. The system consists of a full-text indexed repository accessed through an active agent via a Web interface. It is suitable for personal collections comprising tens of thousands of documents (including papers, books, photos, receipts, email, etc.), and provides for ease of document entry and access as well as high levels of security and privacy. Unlike many other systems of the sort, user access to the document collection is assured even if the UpLib system is unavailable. It is "universal" in the sense that documents are canonically represented as projections into the text and image domains, and uses a predominantly visual user interface based on page images. UpLib can thus handle any document format which can be rendered as pages. Provision is made for alternative representations existing alongside the text-domain and image-domain representation, either stored or generated on demand. The system is highly extensible through user scripting, and is intended to be used as a platform for further work in document engineering. UpLib is assembled largely from open-source components (the current exception being the OCR engine, which is proprietary).</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/958220.958262</identifier>
		<title type="sharef:primaryTitle">UpLib: A Universal Personal Digital Library System</title>
	</reference>
	<reference name="doceng03" src="bibtex:proceedings" src-info="bibtex:line-18980" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>Cécile</givenname>
				<surname>Roisin</surname>
			</person>
			<person>
				<givenname>Ethan V.</givenname>
				<surname>Munson</surname>
			</person>
			<person>
				<givenname>Christine</givenname>
				<surname>Vanoirbeek</surname>
			</person>
		</names>
		<date value="2003-11"/>
		<address type="sharef:placePublished">Grenoble, France</address>
		<field type="bibtex:index">DocEng 2003</field>
		<title type="sharef:primaryTitle">2003 ACM Symposium on Document Engineering</title>
		<identifier type="sharef:uri" resourceType="text/html">http://wam.inrialpes.fr/doceng2003/accepted.html</identifier>
	</reference>
	<reference name="lin04" src="bibtex:inproceedings" src-info="bibtex:line-18995" type="sharef:inproceedings" crossref="doceng04">
		<names type="sharef:author">
			<person>
				<givenname>Tancred</givenname>
				<surname>Lindholm</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Three-way merging is a technique that may be employed for reintegrating changes to a document in cases where multiple independently modified copies have been made. While tools for three-way merge of ASCII text files exist in the form of the ubiquitous diff and patch tools these are of limited applicability to XML documents. We present a method for three-way merging of XML which is targeted at merging XML formats that model human-authored documents as ordered trees (e.g. rich text formats structured text drawings etc.). To this end we investigate a number of use cases on XML merging (collaborative editing propagating changes across document variants) from which we derive a set of high-level merge rules. Our merge is based on these rules. We propose that our merge is easy to both understand and implement yet sufficiently expressive to handle several important cases of merging on document structure that are beyond the capabilities of traditional text-based tools. In order to justify these claims we applied our merging method to the merging tasks contained in the use cases. The overall performance of the merge was found to be satisfactory. The key contributions of this work are: a set of merge rules derived from use cases on XML merging a compact and versatile XML merge in accordance with these rules and a classification of conflicts in the context of that merge.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/1030397.1030399</identifier>
		<pages>1-10</pages>
		<title type="sharef:primaryTitle">A Three-way Merge for XML Documents</title>
	</reference>
	<reference name="kil04" src="bibtex:inproceedings" src-info="bibtex:line-19004" type="sharef:inproceedings" crossref="doceng04">
		<names type="sharef:author">
			<person>
				<givenname>Pekka</givenname>
				<surname>Kilpeläinen</surname>
			</person>
			<person>
				<givenname>Rauno</givenname>
				<surname>Tuhkanen</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>XML Schema uses an extension of traditional regular expressions for describing allowed contents of document elements. Iteration is described through numeric attributes minOccurs and maxOccurs attached to content-describing elements such as sequence, choice, and element. These numeric occurrence indicators are a challenge to standard automata-based solutions. Straightforward solutions require space that is exponential with respect to the length of the expressions. We describe a strategy to implement unambiguous content model expressions as counter automata, which are of linear size only.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/1030397.1030441</identifier>
		<pages>239-241</pages>
		<title type="sharef:primaryTitle">Towards Efficient Implementation of XML Schema Content Models</title>
		<field type="bibtex:topic">xsd[0.7]</field>
		<identifier type="sharef:uri">http://portal.acm.org/citation.cfm?doid=1030441</identifier>
	</reference>
	<reference name="qui04" src="bibtex:inproceedings" src-info="bibtex:line-19015" type="sharef:inproceedings" crossref="doceng04">
		<names type="sharef:author">
			<person>
				<givenname>Vincent</givenname>
				<surname>Quint</surname>
			</person>
			<person>
				<givenname>Irène</givenname>
				<surname>Vatton</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>This paper reviews the main innovations of XML and considers their impact on the editing techniques for structured documents. Namespaces open the way to compound documents; well-formedness brings more freedom in the editing task; CSS allows style to be associated easily with structured documents. In addition to these innovative features the wide deployment of XML introduces structured documents in many new applications including applications where text is not the dominant content type. In languages such as SVG or SMIL for instance XML is used to represent vector graphics or multimedia presentations. This is a challenging situation for authoring tools. Traditional methods for editing structured documents are not sufficient to address the new requirements. New techniques must be developed or adapted to allow more users to efficiently create advanced XML documents. These techniques include multiple views semantic-driven editing direct manipulation concurrent manipulation of style and structure and integrated multi-language editing. They have been implemented and experimented in the Amaya editor and in some other tools.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/1030397.1030422</identifier>
		<pages>115-123</pages>
		<title type="sharef:primaryTitle">Techniques for Authoring Complex XML Documents</title>
		<identifier type="sharef:uri">http://portal.acm.org/citation.cfm?doid=1030422</identifier>
	</reference>
	<reference name="kin04b" src="bibtex:inproceedings" src-info="bibtex:line-19025" type="sharef:inproceedings" crossref="doceng04">
		<names type="sharef:author">
			<person>
				<givenname>Peter R.</givenname>
				<surname>King</surname>
			</person>
			<person>
				<givenname>Patrick</givenname>
				<surname>Schmitz</surname>
			</person>
			<person>
				<givenname>Simon</givenname>
				<surname>Thompson</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>XML and its associated languages are emerging as powerful authoring tools for multimedia and hypermedia web content. Furthermore, intelligent presentation generation engines have begun to appear, as have models and platforms for adaptive presentations. However, XML-based models are limited by their lack of expressiveness in presentation and animation. As a result, authors of dynamic, adaptive web content must often use considerable amounts of script or code. The use of such script or code has two serious drawbacks. First, such code undermines the declarative description possible in the original presentation language, and second, the scripting/coding approach does not readily lend itself to authoring by non-programmers. In this paper we describe a set of XML language extensions, inspired by features from the functional programming world, which are designed to widen the class of reactive systems which could be described in languages such as SMIL. The described features extend the power of declarative modeling for the web by allowing the introduction of web media items which may dynamically react to continuously varying inputs, both in a continuous way and by triggering discrete, user-defined, events. The two extensions described herein are discussed in the context of SMIL Animation and SVG, but could be applied to many XML-based languages.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/1030397.1030411</identifier>
		<pages>57-66</pages>
		<title type="sharef:primaryTitle">Behavioral Reactivity and Real Time Programming in XML: Functional Programming meets SMIL Animation</title>
		<identifier type="sharef:uri" resourceType="application/pdf">http://www.ludicrum.org/plsWork/papers/DocEng2004.pdf</identifier>
		<identifier type="sharef:uri">http://portal.acm.org/citation.cfm?doid=1030397.1030411</identifier>
	</reference>
	<reference name="doceng04" src="bibtex:proceedings" src-info="bibtex:line-19036" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>Ethan V.</givenname>
				<surname>Munson</surname>
			</person>
			<person>
				<givenname>Jean-Yves</givenname>
				<surname>Vion-Dury</surname>
			</person>
		</names>
		<date value="2004-10"/>
		<address type="sharef:placePublished">Milwaukee, Wisconsin</address>
		<field type="bibtex:index">DocEng 2004</field>
		<identifier type="sharef:isbn">1-58113-938-1</identifier>
		<publisher>ACM Press</publisher>
		<title type="sharef:primaryTitle">2004 ACM Symposium on Document Engineering</title>
		<identifier type="sharef:uri" resourceType="text/html">http://www.informatik.uni-trier.de/~ley/db/conf/doceng/doceng2004.html</identifier>
		<identifier type="sharef:uri">http://www.sdml.info/doceng2004/</identifier>
	</reference>
	<reference name="man05" src="bibtex:inproceedings" src-info="bibtex:line-19054" type="sharef:inproceedings" crossref="doceng05">
		<names type="sharef:author">
			<person>
				<givenname>Kenji</givenname>
				<surname>Manaka</surname>
			</person>
			<person>
				<givenname>Hiroyuki</givenname>
				<surname>Sato</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>The increasing popularity of XSLT brings up the requirement of more efficient performance. In this paper, we propose two optimization techniques based on template caller-callee analysis. One is the template instantiation optimization which analyzes a stylesheet and identifies the templates to be instantiated before transformation. The other is the static lazy XML parsing optimization that constructs a pruned XML tree by statically identifying the nodes that are actually referred. Furthermore, we have implemented both our optimizations on Saxon and have evaluated its performance. In these experiments, we have proved both of them to be practically useful and to improve XSLT performance.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/1096601.1096618</identifier>
		<pages>55-57</pages>
		<title type="sharef:primaryTitle">Static Optimization of XSLT Stylesheets: Template Instantiation Optimization and Lazy XML Parsing</title>
		<identifier type="sharef:uri">http://doi.acm.org/10.1145/1096601.1096618</identifier>
	</reference>
	<reference name="hur05" src="bibtex:inproceedings" src-info="bibtex:line-19064" type="sharef:inproceedings" crossref="doceng05">
		<names type="sharef:author">
			<person>
				<givenname>Nathan</givenname>
				<surname>Hurst</surname>
			</person>
			<person>
				<givenname>Kim</givenname>
				<surname>Marriott</surname>
			</person>
			<person>
				<givenname>Peter</givenname>
				<surname>Moulder</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Tables are provided in virtually all document formatting systems and are one of the most powerful and useful design elements in current web document standards. Unfortunately, optimal layout of tables which contain text is NP-hard for reasonable layout requirements such as minimizing table height for a given width. We present two new independently-applicable techniques for table layout. The first technique is to solve a continuous approximation to the original layout problem by using a constant-area approximation of the cell content combined with a minimum width and height for the cell. The second technique starts by setting each column to its narrowest possible width and then iteratively reduces the height of the table by judiciously widening its columns. This second technique uses the actual text and line-break rules rather than the constant-area approximation used by the first technique. We also investigate two hybrid approaches both of which use iterative column widening to improve the quality of an initial solution found using a different technique. In the first hybrid approach we use the continuous approximation technique to compute the initial column widths while in the second hybrid approach a modification of the HTML table layout algorithm is used to compute the initial widths. We found that all four techniques are reasonably fast and give significantly more compact layout than that of HTML layout engines.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/1096601.1096623</identifier>
		<pages>74-83</pages>
		<title type="sharef:primaryTitle">Toward Tighter Tables</title>
		<identifier type="sharef:uri">http://doi.acm.org/10.1145/1096601.1096623</identifier>
	</reference>
	<reference name="doceng05" src="bibtex:proceedings" src-info="bibtex:line-19074" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>Anthony</givenname>
				<surname>Wiley</surname>
			</person>
			<person>
				<givenname>Peter R.</givenname>
				<surname>King</surname>
			</person>
		</names>
		<date value="2006-10"/>
		<address type="sharef:placePublished">Bristol, UK</address>
		<field type="bibtex:index">DocEng 2005</field>
		<identifier type="sharef:isbn">1-59593-240-2</identifier>
		<publisher>ACM Press</publisher>
		<title type="sharef:primaryTitle">2005 ACM Symposium on Document Engineering</title>
		<identifier type="sharef:uri" resourceType="text/html">http://www.informatik.uni-trier.de/~ley/db/conf/doceng/doceng2005.html</identifier>
	</reference>
	<reference name="gen06" src="bibtex:inproceedings" src-info="bibtex:line-19090" type="sharef:inproceedings" crossref="doceng06">
		<names type="sharef:author">
			<person>
				<givenname>Pierre</givenname>
				<surname>Genevès</surname>
			</person>
			<person>
				<givenname>Nabil</givenname>
				<surname>Layaïda</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>XPath is the standard declarative language for navigating XML data and returning a set of matching nodes. In the context of XSLT/XQuery analysis, query optimization, and XML type checking, XPath decision problems arise naturally. They notably include XPath comparisons such as equivalence (whether two queries always return the same result), and containment (whether for any tree the result of a particular query is included in the result of a second one). XPath decision problems have attracted a lot of research attention, especially for studying the computational complexity of various XPath fragments. However, what is missing at present is the constructive use of an expressive logic which would allow capturing these decision problems, while providing practically effective decision procedures. In this paper, we propose a logic-based framework for the static analysis of XPath. Specifically, we propose the alternation free modal µ-calculus with converse as the appropriate logic for effectively solving XPath decision problems. We present a translation of a large XPath fragment into µ-calculus, together with practical experiments on the containment using a state-of-the-art EXPTIME decision procedure for µ-calculus satisfiability. These preliminary experiments shed light, for the first time, on the cost of checking the containment in practice. We believe they reveal encouraging results for further static analysis of XML transformations.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/1166160.1166182</identifier>
		<pages>65-74</pages>
		<title type="sharef:primaryTitle">Comparing XML Path Expressions</title>
		<field type="bibtex:topic">xpath[0.8]</field>
		<identifier type="sharef:uri">http://portal.acm.org/citation.cfm?doid=1166160.1166182</identifier>
	</reference>
	<reference name="lin06" src="bibtex:inproceedings" src-info="bibtex:line-19101" type="sharef:inproceedings" crossref="doceng06">
		<names type="sharef:author">
			<person>
				<givenname>Tancred</givenname>
				<surname>Lindholm</surname>
			</person>
			<person>
				<givenname>Jaakko</givenname>
				<surname>Kangasharju</surname>
			</person>
			<person>
				<givenname>Sasu</givenname>
				<surname>Tarkoma</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>With the advent of XML we have seen a renewed interest in methods for computing the difference between trees. Methods that include heuristic elements play an important role in practical applications due to the inherent complexity of the problem. We present a method for differencing XML as ordered trees based on mapping the problem to the domain of sequence alignment, applying simple and efficient heuristics in this domain, and transforming back to the tree domain. Our approach provides a method to quickly compute changes that are meaningful transformations on the XML tree level, and includes subtree move as a primitive operation. We evaluate the feasibility of our approach and benchmark it against a selection of existing differencing tools. The results show our approach to be feasible and to have the potential to perform on par with tools of a more complex design in terms of both output size and execution time.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/1166160.1166183</identifier>
		<pages>75-84</pages>
		<title type="sharef:primaryTitle">Fast and Simple XML Tree Differencing by Sequence Alignment</title>
		<field type="bibtex:topic">xml[0.8]</field>
		<identifier type="sharef:uri">http://doi.acm.org/10.1145/1166160.1166183</identifier>
	</reference>
	<reference name="qel06" src="bibtex:inproceedings" src-info="bibtex:line-19112" type="sharef:inproceedings" crossref="doceng06">
		<names type="sharef:author">
			<person>
				<givenname>Ermir</givenname>
				<surname>Qeli</surname>
			</person>
			<person>
				<givenname>Julinda</givenname>
				<surname>Gllavata</surname>
			</person>
			<person>
				<givenname>Bernd</givenname>
				<surname>Freisleben</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Change detection in XML documents is an important task in the context of query systems. In this paper, we present CustX-Diff, a customizable change detection approach for XML documents based on X-Diff. CustX-Diff performs the change detection operation simultaneously with the XPath based filtering of XML document parts. The class of XPath expressions used is the tree patterns subset of XPath. For the embedding of simple paths into XPath expressions during the difference operation, a dynamic programming approach is proposed. Comparative performance results with respect to the original X-Diff approach demonstrate the efficiency of the proposed method.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/1166160.1166185</identifier>
		<pages>88-90</pages>
		<title type="sharef:primaryTitle">Customizable Detection of Changes for XML Documents using XPath Expressions</title>
		<field type="bibtex:topic">xml[0.8] xpath[0.8] xdiff[0.8]</field>
		<identifier type="sharef:uri">http://doi.acm.org/10.1145/1166160.1166185</identifier>
	</reference>
	<reference name="bru06" src="bibtex:inproceedings" src-info="bibtex:line-19123" type="sharef:inproceedings" crossref="doceng06">
		<names type="sharef:author">
			<person>
				<givenname>Emmanuel</givenname>
				<surname>Bruno</surname>
			</person>
			<person>
				<givenname>Elisabeth</givenname>
				<surname>Murisasco</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Our work aims at representing and querying hierarchical XML structures defined over the same textual data. We call such data "multistructured textual documents". Our objectives are twofold. First, we shall define a suitable — XML compatible — data model enabling (1) to describe several independent hierarchical structures over the same textual data (represented by several XML structured documents) (2) to consider user annotations added in each structured document. Our proposal is based on the use of hedges (the foundation of the grammar language RelaxNG). Secondly, we shall propose an extension of XQuery in order to query structures and content in a concurrent way. We shall apply our proposals using a literary text written in old French.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/1166160.1166199</identifier>
		<pages>147-154</pages>
		<title type="sharef:primaryTitle">Describing and Querying Hierarchical XML Structures Defined over the Same Textual Data</title>
		<identifier type="sharef:uri">http://doi.acm.org/10.1145/1166160.1166199</identifier>
	</reference>
	<reference name="doceng06" src="bibtex:proceedings" src-info="bibtex:line-19133" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>Dick C. A.</givenname>
				<surname>Bulterman</surname>
			</person>
			<person>
				<givenname>David F.</givenname>
				<surname>Brailsford</surname>
			</person>
		</names>
		<date value="2006-10"/>
		<address type="sharef:placePublished">Amsterdam, Netherlands</address>
		<field type="bibtex:index">DocEng 2006</field>
		<identifier type="sharef:isbn">1-59593-515-0</identifier>
		<publisher>ACM Press</publisher>
		<title type="sharef:primaryTitle">2006 ACM Symposium on Document Engineering</title>
		<identifier type="sharef:uri" resourceType="text/html">http://www.informatik.uni-trier.de/~ley/db/conf/doceng/doceng2006.html</identifier>
	</reference>
	<reference name="wei07" src="bibtex:inproceedings" src-info="bibtex:line-19150" type="sharef:inproceedings" crossref="doceng07">
		<names type="sharef:author">
			<person>
				<givenname>Nadir</givenname>
				<surname>Weibel</surname>
			</person>
			<person>
				<givenname>Moira C.</givenname>
				<surname>Norrie</surname>
			</person>
			<person>
				<givenname>Beat</givenname>
				<surname>Signer</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>The first steps towards bridging the paper-digital divide have been achieved with the development of a range of technologies that allow printed documents to be linked to digital content and services. However, the static nature of paper and limited structural information encoded in classical paginated formats make it difficult to map between parts of a printed instance of a document and logical elements of a digital instance of the same document, especially taking document revisions into account. We present a solution to this problem based on a model that combines metadata of the digital and printed instances to enable a seamless mapping between digital documents and their physical counterparts on paper. We also describe how the model was used to develop iDoc, a framework that supports the authoring and publishing of interactive paper documents.</p>
			</richtext>
		</abstract>
		<title type="sharef:primaryTitle">A Model for Mapping between Printed and Digital Document Instances</title>
	</reference>
	<reference name="tho07" src="bibtex:inproceedings" src-info="bibtex:line-19157" type="sharef:inproceedings" crossref="doceng07">
		<names type="sharef:author">
			<person>
				<givenname>Simon</givenname>
				<surname>Thompson</surname>
			</person>
			<person>
				<givenname>Peter R.</givenname>
				<surname>King</surname>
			</person>
			<person>
				<givenname>Patrick</givenname>
				<surname>Schmitz</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>We present a set of XML language extensions that bring notions from functional programming to web authors, extending the power of declarative modelling for the web. Our previous work discussed expressions and user-defined events. In this paper, we discuss how one may extend XML by adding definitions and parameterization; complex data and data types; and reactivity, events and continuous "behaviours". We consider these extensions in the light of World Wide Web Consortium standards, and illustrate their utility by a variety of use cases.</p>
			</richtext>
		</abstract>
		<title type="sharef:primaryTitle">Declarative Extensions of XML Languages</title>
	</reference>
	<reference name="wil07m" src="bibtex:inproceedings" src-info="bibtex:line-19164" type="sharef:inproceedings" crossref="doceng07">
		<names type="sharef:author">
			<person>
				<givenname>Erik</givenname>
				<surname>Wilde</surname>
			</person>
			<person>
				<givenname>Philippe</givenname>
				<surname>Cattin</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>The management and publishing of complex presentations is poorly supported by available presentation software. This makes it hard to publish usable and accessible presentation material, and to reuse that material for continuously evolving events. XSLidy provides a XSLT-based approach to generate presentations out of a mix of HTML and structural elements. Using XSLidy, the management and reuse of complex presentations becomes easier, and the results are more user-friendly in terms of usability and accessibility.</p>
			</richtext>
		</abstract>
		<title type="sharef:primaryTitle">Presenting in HTML</title>
		<field type="bibtex:topic">xslidy[0.9]</field>
		<identifier type="sharef:uri">http://dret.net/netdret/publications#wil07m</identifier>
	</reference>
	<reference name="doceng07" src="bibtex:proceedings" src-info="bibtex:line-19173" type="sharef:proceedings">
		<date value="2007-08"/>
		<address type="sharef:placePublished">Winnipeg, Manitoba</address>
		<field type="bibtex:index">DocEng 2007</field>
		<publisher>ACM Press</publisher>
		<title type="sharef:primaryTitle">2007 ACM Symposium on Document Engineering</title>
		<identifier type="sharef:uri">http://doceng07.cs.umanitoba.ca/</identifier>
		<identifier type="sharef:uri" resourceType="text/html">http://www.informatik.uni-trier.de/~ley/db/conf/doceng/doceng2007.html</identifier>
	</reference>
	<reference name="shn87" src="bibtex:inproceedings" src-info="bibtex:line-19189" type="sharef:inproceedings" crossref="acmht87">
		<names type="sharef:author">
			<person>
				<givenname>Ben</givenname>
				<surname>Shneiderman</surname>
			</person>
		</names>
		<field type="bibtex:index">Hyperties</field>
		<pages>189-194</pages>
		<title type="sharef:primaryTitle">User Interface Design for the Hyperties Electronic Encyclopedia</title>
	</reference>
	<reference name="acmht87" src="bibtex:proceedings" src-info="bibtex:line-19197" type="sharef:proceedings">
		<date value="1987-11"/>
		<address type="sharef:placePublished">Chapel Hill, North Carolina</address>
		<identifier type="sharef:isbn">089791340X</identifier>
		<publisher>ACM Press</publisher>
		<title type="sharef:primaryTitle">1987 ACM Conference on Hypertext</title>
		<identifier type="sharef:uri" resourceType="text/html">http://www.informatik.uni-trier.de/~ley/db/conf/ht/ht87.html</identifier>
	</reference>
	<reference name="glu89" src="bibtex:inproceedings" src-info="bibtex:line-19212" type="sharef:inproceedings" crossref="acmht89">
		<names type="sharef:author">
			<person>
				<givenname>Robert J.</givenname>
				<surname>Glushko</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Vannevar Bush conceived of hypertext as the "computer glue" that binds information from a wide variety of books, documents, communications, and other artifacts to enhance its accessibility and usefulness. However, most of the recent hyper-activity in research labs and in the marketplace falls short of Bush's vision. Most hypertext software is oriented toward hypertext as a new form of writing via incremental combination of bits and pieces of information. These hypertext programs typically provide little support for converting existing information from its more linear printed form, Where hypertexts have been created from existing text, they generally have been converted from a single encyclopedia, a single reference document, or a single system's documentation. Hypertexts that integrate the complete contents of more than one book or large document seem nonexistent, even though the expected benefits from such multi-document hypertexts were the original motivation for the concept.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/74224.74229</identifier>
		<pages>51-60</pages>
		<title type="sharef:primaryTitle">Design Issues for Multi-Document Hypertexts</title>
	</reference>
	<reference name="acmht89" src="bibtex:proceedings" src-info="bibtex:line-19221" type="sharef:proceedings">
		<date value="1989-11"/>
		<address type="sharef:placePublished">Pittsburgh, Pennsylvania</address>
		<identifier type="sharef:isbn">0-89791-339-6</identifier>
		<publisher>ACM Press</publisher>
		<title type="sharef:primaryTitle">1989 ACM Conference on Hypertext</title>
		<identifier type="sharef:uri" resourceType="text/html">http://www.informatik.uni-trier.de/~ley/db/conf/ht/ht89.html</identifier>
	</reference>
	<reference name="mal91" src="bibtex:inproceedings" src-info="bibtex:line-19236" type="sharef:inproceedings" crossref="acmht91">
		<names type="sharef:author">
			<person>
				<givenname>Kathryn C.</givenname>
				<surname>Malcolm</surname>
			</person>
			<person>
				<givenname>Steven E.</givenname>
				<surname>Poltrock</surname>
			</person>
			<person>
				<givenname>Douglas</givenname>
				<surname>Schuler</surname>
			</person>
		</names>
		<pages>13-24</pages>
		<title type="sharef:primaryTitle">Industrial Strength Hypermedia: Requirements for a Large Engineering Enterprise</title>
		<field type="bibtex:topic">ohs[1]</field>
	</reference>
	<reference name="acmht91" src="bibtex:proceedings" src-info="bibtex:line-19244" type="sharef:proceedings">
		<date value="1991-12"/>
		<address type="sharef:placePublished">San Antonio, Texas</address>
		<identifier type="sharef:isbn">089791547X</identifier>
		<publisher>ACM Press</publisher>
		<title type="sharef:primaryTitle">Third ACM Conference on Hypertext</title>
	</reference>
	<reference name="dav92" src="bibtex:inproceedings" src-info="bibtex:line-19258" type="sharef:inproceedings" crossref="acmht92">
		<names type="sharef:author">
			<person>
				<givenname>Hugh C.</givenname>
				<surname>Davis</surname>
			</person>
			<person>
				<givenname>Wendy</givenname>
				<surname>Hall</surname>
			</person>
			<person>
				<givenname>Ian</givenname>
				<surname>Heath</surname>
			</person>
			<person>
				<givenname>Gary J.</givenname>
				<surname>Hill</surname>
			</person>
			<person>
				<givenname>Robert J.</givenname>
				<surname>Wilkins</surname>
			</person>
		</names>
		<pages>181-190</pages>
		<title type="sharef:primaryTitle">Towards an Integrated Information Environment with Open Hypermedia Systems</title>
		<field type="bibtex:topic">microcosm[1]</field>
		<identifier type="sharef:uri">http://www.mmrg.ecs.soton.ac.uk/publications/archive/davis1992</identifier>
	</reference>
	<reference name="acmht92" src="bibtex:proceedings" src-info="bibtex:line-19267" type="sharef:proceedings">
		<date value="1992-11"/>
		<address type="sharef:placePublished">Milano, Italy</address>
		<field type="bibtex:index">ECHT '92</field>
		<publisher>ACM Press</publisher>
		<title type="sharef:primaryTitle">Fourth ACM Conference on Hypertext</title>
	</reference>
	<reference name="sch96a" src="bibtex:inproceedings" src-info="bibtex:line-19281" type="sharef:inproceedings" crossref="acmht96">
		<names type="sharef:author">
			<person>
				<givenname>Daniel</givenname>
				<surname>Schwabe</surname>
			</person>
			<person>
				<givenname>Gustavo</givenname>
				<surname>Rossi</surname>
			</person>
			<person>
				<givenname>Simone D. J.</givenname>
				<surname>Barbosa</surname>
			</person>
		</names>
		<pages>116-128</pages>
		<title type="sharef:primaryTitle">Systematic Hypermedia Application Design with OOHDM</title>
		<identifier type="sharef:uri" resourceType="text/html">http://www-di.inf.puc-rio.br/~schwabe//HT96WWW/section1.html</identifier>
	</reference>
	<reference name="acmht96" src="bibtex:proceedings" src-info="bibtex:line-19289" type="sharef:proceedings">
		<date value="1996-03"/>
		<address type="sharef:placePublished">Washington, D.C.</address>
		<publisher>ACM Press</publisher>
		<title type="sharef:primaryTitle">1996 ACM Conference on Hypertext</title>
	</reference>
	<reference name="nue97b" src="bibtex:inproceedings" src-info="bibtex:line-19303" type="sharef:inproceedings" crossref="acmht97">
		<names type="sharef:author">
			<person>
				<givenname>Peter J.</givenname>
				<surname>Nürnberg</surname>
			</person>
			<person>
				<givenname>John J.</givenname>
				<surname>Leggett</surname>
			</person>
			<person>
				<givenname>Erich R.</givenname>
				<surname>Schneider</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>The hypermedia field has long realized the need for first-class structural abstractions. However, we have failed to generalize the concept of ubiquitous structure management to problem domains other than navigation of information spaces. In this paper, we argue for the recognition of such a generalization, called structural computing, in which we assert the primacy of structure over data. We provide examples of four problem domains that are more naturally modeled with structure than data. We argue that support for structural computing must come in the form of new models, operating systems, and programming languages. We also assert that the experience gained by hypermedia researchers over the last decade may be naturally extended to form the basis of the new field of structural computing, and furthermore, the broadening of the applicability of our work is necessary for the continued vitality of our research community.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/267437.267448</identifier>
		<pages>96-101</pages>
		<title type="sharef:primaryTitle">As We Should Have Thought</title>
	</reference>
	<reference name="gro97b" src="bibtex:inproceedings" src-info="bibtex:line-19312" type="sharef:inproceedings" crossref="acmht97">
		<names type="sharef:author">
			<person>
				<givenname>Kaj</givenname>
				<surname>Grønbæk</surname>
			</person>
			<person>
				<givenname>Niels Olof</givenname>
				<surname>Bouvin</surname>
			</person>
			<person>
				<givenname>Lennert</givenname>
				<surname>Sloth</surname>
			</person>
		</names>
		<pages>146-156</pages>
		<title type="sharef:primaryTitle">Designing Dexter-based Hypermedia Services for the World Wide Web</title>
		<field type="bibtex:topic">dexter[0.9]</field>
	</reference>
	<reference name="and97" src="bibtex:inproceedings" src-info="bibtex:line-19320" type="sharef:inproceedings" crossref="acmht97">
		<names type="sharef:author">
			<person>
				<givenname>Kenneth M.</givenname>
				<surname>Anderson</surname>
			</person>
		</names>
		<pages>157-166</pages>
		<title type="sharef:primaryTitle">Integrating Open Hypermedia Systems with the World Wide Web</title>
		<field type="bibtex:topic">ohs[0.8] www[0.7] chimera[0.9]</field>
		<identifier type="sharef:uri" resourceType="application/pdf">http://journals.ecs.soton.ac.uk/~lac/ht97/pdfs/anderson.pdf</identifier>
	</reference>
	<reference name="rut97" src="bibtex:inproceedings" src-info="bibtex:line-19329" type="sharef:inproceedings" crossref="ohs97">
		<names type="sharef:author">
			<person>
				<givenname>Lloyd</givenname>
				<surname>Rutledge</surname>
			</person>
			<person>
				<givenname>Lynda</givenname>
				<surname>Hardman</surname>
			</person>
			<person>
				<givenname>Jacco</givenname>
				<surname link="van">Ossenbruggen</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>The proposed Open Hypermedia Protocol communicates the resolution of link traversals. This protocol includes the LocSpec construct, which specifies the location of a link's anchor. The details of LocSpec have not yet been specified. HyTime is an ISO standard that defines the structure of hypermedia documents. It includes a variety of means for establishing link anchor locations. This position paper considers this HyTime-defined model as a basis for developing the Open Hypermedia Protocol LocSpec.</p>
			</richtext>
		</abstract>
		<title type="sharef:primaryTitle">Applying the HyTime Model to the Open Hypermedia Protocol LocSpec</title>
		<field type="bibtex:topic">ohp[0.7] hytime[0.7]</field>
		<identifier type="sharef:uri" resourceType="text/html">http://www.sigweb.org/resources/OHS/ohs97/Papers/rutledge.html</identifier>
	</reference>
	<reference name="acmht97" src="bibtex:proceedings" src-info="bibtex:line-19338" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>Mark</givenname>
				<surname>Bernstein</surname>
			</person>
			<person>
				<givenname>Leslie A.</givenname>
				<surname>Carr</surname>
			</person>
			<person>
				<givenname>Kasper</givenname>
				<surname>Østerbye</surname>
			</person>
		</names>
		<date value="1997-04"/>
		<address type="sharef:placePublished">Southampton, UK</address>
		<publisher>ACM Press</publisher>
		<title type="sharef:primaryTitle">1997 ACM Conference on Hypertext</title>
		<identifier type="sharef:uri" resourceType="text/html">http://journals.ecs.soton.ac.uk/~lac/ht97/techpapers.html</identifier>
	</reference>
	<reference name="ohs97" src="bibtex:proceedings" src-info="bibtex:line-19349" type="sharef:proceedings">
		<date value="1997-04"/>
		<address type="sharef:placePublished">Southampton, UK</address>
		<title type="sharef:primaryTitle">3rd Workshop on Open Hypermedia Systems</title>
		<identifier type="sharef:uri">http://www.sigweb.org/resources/OHS/ohs97/</identifier>
	</reference>
	<reference name="pri98" src="bibtex:inproceedings" src-info="bibtex:line-19362" type="sharef:inproceedings" crossref="acmht98">
		<names type="sharef:author">
			<person>
				<givenname>Morgan N.</givenname>
				<surname>Price</surname>
			</person>
			<person>
				<givenname>Gene</givenname>
				<surname>Golovchinsky</surname>
			</person>
			<person>
				<givenname>Bill N.</givenname>
				<surname>Schilit</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>"Linking by inking" is a new interface for reader-directed link construction that bridges reading and browsing activities. We are developing linking by inking in XLibris, a hypertext system based on the paper document metaphor. Readers use a pen computer to annotate page images with free-form ink, much as they would on paper, and the computer constructs hypertext links based on the ink marks. This paper proposes two kinds of readerdirected links: automatic and manual. Automatic links are created in response to readers' annotations. The system extracts the text near free-form ink marks, uses these terms to construct queries, executes queries against a collection of documents, and unobtrusively displays links to related documents in the margin or as "further reading lists." We also present a design for manual (ad hoc) linking: circling an ink symbol generates a multi-way link to other instances of the same symbol."</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/276627.276631</identifier>
		<pages>30-39</pages>
		<title type="sharef:primaryTitle">Linking By Inking: Trailblazing in a Paper-like Hypertext</title>
		<field type="bibtex:topic">xlibris[1]</field>
		<identifier type="sharef:uri" resourceType="application/pdf">http://www.fxpal.com/publications/FXPAL-PR-98-112.pdf</identifier>
	</reference>
	<reference name="dav98" src="bibtex:inproceedings" src-info="bibtex:line-19373" type="sharef:inproceedings" crossref="acmht98">
		<names type="sharef:author">
			<person>
				<givenname>Hugh C.</givenname>
				<surname>Davis</surname>
			</person>
		</names>
		<identifier type="sharef:doi">10.1145/276627.276650</identifier>
		<pages>207-216</pages>
		<title type="sharef:primaryTitle">Referential Integrity of Links in Open Hypermedia Systems</title>
		<identifier type="sharef:uri">http://portal.acm.org/citation.cfm?id=276650</identifier>
	</reference>
	<reference name="mar98" src="bibtex:inproceedings" src-info="bibtex:line-19382" type="sharef:inproceedings" crossref="acmht98">
		<names type="sharef:author">
			<person>
				<givenname>Catherine C.</givenname>
				<surname>Marshall</surname>
			</person>
		</names>
		<pages>40-49</pages>
		<title type="sharef:primaryTitle">Toward an Ecology of Hypertext Annotation</title>
		<identifier type="sharef:uri" resourceType="application/pdf">http://www.csdl.tamu.edu/~marshall/ht98-final.pdf</identifier>
	</reference>
	<reference name="acmht98" src="bibtex:proceedings" src-info="bibtex:line-19390" type="sharef:proceedings">
		<date value="1998-06"/>
		<address type="sharef:placePublished">Pittsburgh, Pennsylvania</address>
		<publisher>ACM Press</publisher>
		<title type="sharef:primaryTitle">9th ACM Conference on Hypertext</title>
		<identifier type="sharef:uri" resourceType="text/html">http://www.informatik.uni-trier.de/~ley/db/conf/ht/ht98.html</identifier>
	</reference>
	<reference name="dav99b" src="bibtex:inproceedings" src-info="bibtex:line-19404" type="sharef:inproceedings" crossref="acmht99">
		<names type="sharef:author">
			<person>
				<givenname>Hugh C.</givenname>
				<surname>Davis</surname>
			</person>
			<person>
				<givenname>David E.</givenname>
				<surname>Millard</surname>
			</person>
			<person>
				<givenname>Siegfried</givenname>
				<surname>Reich</surname>
			</person>
			<person>
				<givenname>Niels Olof</givenname>
				<surname>Bouvin</surname>
			</person>
			<person>
				<givenname>Kaj</givenname>
				<surname>Grønbæk</surname>
			</person>
			<person>
				<givenname>Peter J.</givenname>
				<surname>Nürnberg</surname>
			</person>
			<person>
				<givenname>Lennert</givenname>
				<surname>Sloth</surname>
			</person>
			<person>
				<givenname>Uffe Kock</givenname>
				<surname>Wiil</surname>
			</person>
			<person>
				<givenname>Kenneth M.</givenname>
				<surname>Anderson</surname>
			</person>
		</names>
		<pages>201-202</pages>
		<title type="sharef:primaryTitle">Interoperability between Hypermedia Systems: The Standardisation Work of the OHSWG</title>
		<field type="bibtex:topic">ohp[0.9]</field>
		<identifier type="sharef:uri" resourceType="application/pdf">http://cs.aue.auc.dk/~kock/Publications/OHS/ohstb99.pdf</identifier>
	</reference>
	<reference name="bou99" src="bibtex:inproceedings" src-info="bibtex:line-19413" type="sharef:inproceedings" crossref="acmht99">
		<names type="sharef:author">
			<person>
				<givenname>Niels Olof</givenname>
				<surname>Bouvin</surname>
			</person>
		</names>
		<pages>91-100</pages>
		<title type="sharef:primaryTitle">Unifying Strategies for Web Augmentation</title>
		<field type="bibtex:topic">arakne[0.9]</field>
		<identifier type="sharef:uri" resourceType="application/pdf">http://www.daimi.aau.dk/~bouvin/ht99.pdf</identifier>
	</reference>
	<reference name="rei99" src="bibtex:inproceedings" src-info="bibtex:line-19422" type="sharef:inproceedings" crossref="acmht99">
		<names type="sharef:author">
			<person>
				<givenname>Siegfried</givenname>
				<surname>Reich</surname>
			</person>
			<person>
				<givenname>David E.</givenname>
				<surname>Millard</surname>
			</person>
			<person>
				<givenname>Hugh C.</givenname>
				<surname>Davis</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Naming is a key issue in any distributed system. In particular, with the Open Hypermedia Systems Working Group's efforts towards openness and interoperability in Open Hypermedia Systems (OHS) resulting in the need for (globally) valid names for all types of resources the issue of naming has become increasingly important. In this position paper we examine the issues involved in naming and a present a proposal for naming to be used within the Open Hypermedia Protocol (OHP).</p>
			</richtext>
		</abstract>
		<pages>43-47</pages>
		<title type="sharef:primaryTitle">Naming in OHP</title>
		<field type="bibtex:topic">ohp[0.9]</field>
		<identifier type="sharef:uri">http://eprints.ecs.soton.ac.uk/822/</identifier>
	</reference>
	<reference name="acmht99" src="bibtex:proceedings" src-info="bibtex:line-19432" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>Klaus</givenname>
				<surname>Tochtermann</surname>
			</person>
			<person>
				<givenname>Jörg</givenname>
				<surname>Westbomke</surname>
			</person>
			<person>
				<givenname>Uffe Kock</givenname>
				<surname>Wiil</surname>
			</person>
			<person>
				<givenname>John J.</givenname>
				<surname>Leggett</surname>
			</person>
		</names>
		<date value="1999-02"/>
		<address type="sharef:placePublished">Darmstadt, Germany</address>
		<publisher>ACM Press</publisher>
		<title type="sharef:primaryTitle">10th ACM Conference on Hypertext</title>
	</reference>
	<reference name="der00" src="bibtex:inproceedings" src-info="bibtex:line-19446" type="sharef:inproceedings" crossref="acmht00">
		<names type="sharef:author">
			<person>
				<givenname>David C.</givenname>
				<surname>De Roure</surname>
			</person>
			<person>
				<givenname>Nigel G.</givenname>
				<surname>Walker</surname>
			</person>
			<person>
				<givenname>Leslie A.</givenname>
				<surname>Carr</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Variations on the Distributed Link Service have now been deployed across a spectrum of hypermedia and multimedia projects. Although some implementations have utilised standard database technologies and hypermedia tools behind the scenes, most of the network services have been proprietary implementations. In this paper we discuss the motivation and requirements for a large scale, dynamic and open distributed link service using third party components, and explore the use of off-the-shelf services to provide the distributed infrastructure for link services. In particular we investigate HTTP, LDAP and Whois++ as candidate technologies.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/336296.336325</identifier>
		<pages>151-160</pages>
		<title type="sharef:primaryTitle">Investigating Link Service Infrastructures</title>
		<field type="bibtex:topic">dls[0.9]</field>
		<identifier type="sharef:uri">http://eprints.ecs.soton.ac.uk/2694/</identifier>
	</reference>
	<reference name="hal00" src="bibtex:inproceedings" src-info="bibtex:line-19457" type="sharef:inproceedings" crossref="acmht00">
		<names type="sharef:author">
			<person>
				<givenname>Brent</givenname>
				<surname>Halsey</surname>
			</person>
			<person>
				<givenname>Kenneth M.</givenname>
				<surname>Anderson</surname>
			</person>
		</names>
		<identifier type="sharef:doi">10.1145/336296.336367</identifier>
		<pages>212-213</pages>
		<title type="sharef:primaryTitle">XLink and Open Hypermedia Systems: A Preliminary Investigation</title>
		<field type="bibtex:topic">xlink[0.7] chimera[0.8]</field>
		<identifier type="sharef:uri">http://portal.acm.org/citation.cfm?id=336296.336367</identifier>
	</reference>
	<reference name="tza00" src="bibtex:inproceedings" src-info="bibtex:line-19467" type="sharef:inproceedings" crossref="acmht00">
		<names type="sharef:author">
			<person>
				<givenname>Manolis M.</givenname>
				<surname>Tzagarakis</surname>
			</person>
			<person>
				<givenname>Nikos</givenname>
				<surname>Karousos</surname>
			</person>
			<person>
				<givenname>Dimitris</givenname>
				<surname>Christodoulakis</surname>
			</person>
			<person>
				<givenname>Siegfried</givenname>
				<surname>Reich</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Names play a key role in distributed hypertext systems, for two main reasons: Firstly, because accessing and managing system services require finding and locating the relevant components. Secondly, because managing structures between hypertext resources, such as nodes, anchors and links, requires that these resources are named and addressed. We argue that naming services are endemic to hypertext systems and therefore, form a core part of any hypertext system's infrastructure. In particular, the current move towards interoperable component-based Open Hypermedia Systems (CB-OHS) demonstrates the need for naming components.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/336296.336338</identifier>
		<pages>103-112</pages>
		<title type="sharef:primaryTitle">Naming as a Fundamental Concept of Open Hypermedia Systems</title>
		<field type="bibtex:topic">ohs[0.8]</field>
		<identifier type="sharef:uri">http://portal.acm.org/citation.cfm?id=336338</identifier>
	</reference>
	<reference name="acmht00" src="bibtex:proceedings" src-info="bibtex:line-19478" type="sharef:proceedings">
		<date value="2000-05"/>
		<address type="sharef:placePublished">San Antonio, Texas</address>
		<field type="bibtex:index">HT'00</field>
		<publisher>ACM Press</publisher>
		<title type="sharef:primaryTitle">11th ACM Conference on Hypertext and Hypermedia</title>
	</reference>
	<reference name="can02" src="bibtex:inproceedings" src-info="bibtex:line-19492" type="sharef:inproceedings" crossref="dolmen03">
		<names type="sharef:author">
			<person>
				<givenname>José H.</givenname>
				<surname>Canós</surname>
			</person>
			<person>
				<givenname>Eduardo</givenname>
				<surname>Mena</surname>
			</person>
		</names>
		<title type="sharef:primaryTitle">BibShare: An Interoperable System to Access and Maintain Bibliographic References</title>
		<field type="bibtex:topic">bibshare[0.9]</field>
		<identifier type="sharef:uri">http://sol1.cps.unizar.es:5080/PUBLICATIONS/POSTSCRIPTS/dolmen02.ps.gz</identifier>
		<identifier type="sharef:uri">http://www.um.es/giisw/dolmen3/papers/21.zip</identifier>
	</reference>
	<reference name="gar02b" src="bibtex:inproceedings" src-info="bibtex:line-19501" type="sharef:inproceedings" crossref="dolmen03">
		<names type="sharef:author">
			<person>
				<givenname>Lina</givenname>
				<surname>García-Cabrera</surname>
			</person>
			<person>
				<givenname>María José</givenname>
				<surname>Rodríguez-Fórtiz</surname>
			</person>
			<person>
				<givenname>José Parets</givenname>
				<surname>Llorca</surname>
			</person>
		</names>
		<title type="sharef:primaryTitle">Evolving Hypermedia Systems: A Layered Software Architecture</title>
		<field type="bibtex:topic">semhp[0.9]</field>
		<identifier type="sharef:uri">http://www.um.es/giisw/dolmen3/papers/05.zip</identifier>
	</reference>
	<reference name="dolmen03" src="bibtex:proceedings" src-info="bibtex:line-19509" type="sharef:proceedings">
		<date value="2002-11"/>
		<address type="sharef:placePublished">Madrid, Spain</address>
		<title type="sharef:primaryTitle">III Jornadas de Trabajo DOLMEN</title>
		<identifier type="sharef:uri" resourceType="text/html">http://www.um.es/giisw/dolmen3/docs.htm</identifier>
	</reference>
	<reference name="zel01" src="bibtex:inproceedings" src-info="bibtex:line-19522" type="sharef:inproceedings" crossref="acmht01">
		<names type="sharef:author">
			<person>
				<givenname>Polle T.</givenname>
				<surname>Zellweger</surname>
			</person>
			<person>
				<givenname>Niels Olof</givenname>
				<surname>Bouvin</surname>
			</person>
			<person>
				<givenname>Henning</givenname>
				<surname>Jehøj</surname>
			</person>
			<person>
				<givenname>Jock D.</givenname>
				<surname>Mackinlay</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Fluid Documents use animated typographical changes to provide a novel and appealing user experience for hypertext browsing and for viewing document annotations in context. This paper describes an effort to broaden the utility of Fluid Documents by using the open hypermedia Arakne Environment to layer fluid annotations and links on top of arbitrary HTML pages on the World Wide Web. Changes to both Fluid Documents and Arakne are required.</p>
			</richtext>
		</abstract>
		<pages>9-18</pages>
		<title type="sharef:primaryTitle">Fluid Annotations in an Open World</title>
		<field type="bibtex:topic">arakne[0.9] fluidannotations[0.9]</field>
		<identifier type="sharef:uri" resourceType="application/pdf">http://www.parc.xerox.com/istl/groups/gir/papers/fluid-open-ht01.pdf</identifier>
	</reference>
	<reference name="wei01" src="bibtex:inproceedings" src-info="bibtex:line-19532" type="sharef:inproceedings" crossref="acmht01">
		<names type="sharef:author">
			<person>
				<givenname>Harald</givenname>
				<surname>Weinreich</surname>
			</person>
			<person>
				<givenname>Hartmut</givenname>
				<surname>Obendorf</surname>
			</person>
			<person>
				<givenname>Winfried</givenname>
				<surname>Lamersdorf</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>The design of hypertext systems has been subject to intense research. Apparently, one topic was mostly neglected: how to visualize and interact with link markers. This paper presents an overview of pragmatic historical approaches, and discusses problems evolving from sophisticated hypertext linking features. Blending the potential of an XLink-enhanced Web with old ideas and recent GUI techniques, a vision for browser link interfaces of the future is being developed. We hope to stimulate the development of a standard for hyperlink marker interfaces, which is easy-to-use, feasible for extended linking features, and more consistent than current approaches.</p>
			</richtext>
		</abstract>
		<pages>19-28</pages>
		<title type="sharef:primaryTitle">The Look of the Link — Concepts for the User Interface of Extended Hyperlinks</title>
		<identifier type="sharef:uri">http://vsys-www.informatik.uni-hamburg.de/publications/viewpub.phtml/87</identifier>
	</reference>
	<reference name="elb01" src="bibtex:inproceedings" src-info="bibtex:line-19541" type="sharef:inproceedings" crossref="acmht01">
		<names type="sharef:author">
			<person>
				<givenname>Samhaa</givenname>
				<surname>El-Beltagy</surname>
			</person>
			<person>
				<givenname>Wendy</givenname>
				<surname>Hall</surname>
			</person>
			<person>
				<givenname>David C.</givenname>
				<surname>De Roure</surname>
			</person>
			<person>
				<givenname>Leslie A.</givenname>
				<surname>Carr</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>This paper explores the idea of dynamically adding multi-destination links to Web pages, based on the context of the pages and users, as a way of assisting Web users in their information finding and navigation activities. The work does not make any preconceived assumptions about the information needs of its users. Instead it presents a method for generating links by adapting to the information needs of a community of users and for utilizing these in assisting users within this community based on their individual needs. The implementation of this work is carried out within a multi-agent framework where concepts from open hypermedia are extended and exploited. In this paper, the entities involved in the process of generating and using 'context links' as well as the techniques they employ to achieve their tasks, are described. The result of an experiment carried out to investigate the implications of linking in context on information finding, is also provided.</p>
			</richtext>
		</abstract>
		<pages>151-160</pages>
		<title type="sharef:primaryTitle">Linking in Context</title>
		<identifier type="sharef:uri">http://www.bib.ecs.soton.ac.uk/records/6884</identifier>
	</reference>
	<reference name="dal01" src="bibtex:inproceedings" src-info="bibtex:line-19550" type="sharef:inproceedings" crossref="acmht01">
		<names type="sharef:author">
			<person>
				<givenname>Rune</givenname>
				<surname>Dalgaard</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>With the Web, hypertext has become the paradigmatic rhetorical structure of a global and distributed archive. This paper argues that the scholarly archive is going though a process of hypertextualization that is not adequately accounted for in theories on hypertext. A methodological approach based on Gerard Genettes theory of transtextuality is proposed for a study of the hypertextualized archive. This involves a rejection of the reductionist opposition of hypertext and the fixed linear text, in favor of a study of the intertexts, paratexts and metatexts that work at the interface between texts and archive. I refer to this as second-order textuality.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/504216.504262</identifier>
		<pages>175-184</pages>
		<title type="sharef:primaryTitle">Hypertext and the Scholarly Archive: Intertexts, Paratexts and Metatexts at Work</title>
		<identifier type="sharef:uri">http://portal.acm.org/citation.cfm?doid=504216.504262</identifier>
		<identifier type="sharef:uri" resourceType="application/pdf">http://imv.au.dk/~runed/pub/dalgaard_acmht01.pdf</identifier>
	</reference>
	<reference name="acmht01" src="bibtex:proceedings" src-info="bibtex:line-19561" type="sharef:proceedings">
		<date value="2001-08"/>
		<address type="sharef:placePublished">Århus, Denmark</address>
		<field type="bibtex:index">HT'01</field>
		<field type="bibtex:key">12th ACM Conference on Hypertext and Hypermedia</field>
		<publisher>ACM Press</publisher>
		<title type="sharef:primaryTitle">12th ACM Conference on Hypertext and Hypermedia</title>
	</reference>
	<reference name="mar02" src="bibtex:inproceedings" src-info="bibtex:line-19576" type="sharef:inproceedings" crossref="acmht02">
		<names type="sharef:author">
			<person>
				<givenname>Duncan</givenname>
				<surname>Martin</surname>
			</person>
			<person>
				<givenname>Helen</givenname>
				<surname>Ashman</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>In this paper, we introduce a platform independent mechanism for implementing both XLink and bespoke linking standards. The paper considers HTML linking as a low-level linking language, and how it can be used to provide a base for high-level linking services. Finally, the paper describes Goate, a HTTP proxy that allows high-level linking to be used with ordinary HTML browsers.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/513338.513375</identifier>
		<pages>142-143</pages>
		<title type="sharef:primaryTitle">Goate: XLink and Beyond</title>
		<field type="bibtex:topic">xlink[0.8]</field>
		<identifier type="sharef:uri">http://portal.acm.org/citation.cfm?doid=513338.513375</identifier>
	</reference>
	<reference name="vit02" src="bibtex:inproceedings" src-info="bibtex:line-19587" type="sharef:inproceedings" crossref="acmht02">
		<names type="sharef:author">
			<person>
				<givenname>Fabio</givenname>
				<surname>Vitali</surname>
			</person>
			<person>
				<givenname>Federico</givenname>
				<surname>Folli</surname>
			</person>
			<person>
				<givenname>Claudio</givenname>
				<surname>Tasso</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>We report on two different projects being developed at the University of Bologna, both of which make use of the new XPointer language, for which two different implementations were deemed necessary. The first project is an HTTP proxy for providing external linkbases expressed in XLink. The second is an extension to XSLT to express transformations on string patterns as well as node patterns. Both libraries have been implemented with ease and efficiency, demonstrating the usefulness and reasonableness of the language.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/513338.513376</identifier>
		<pages>145-146</pages>
		<title type="sharef:primaryTitle">Two Implementations of XPointer</title>
		<field type="bibtex:topic">xpointer[0.7]</field>
		<identifier type="sharef:uri">http://portal.acm.org/citation.cfm?doid=513338.513376</identifier>
	</reference>
	<reference name="acmht02" src="bibtex:proceedings" src-info="bibtex:line-19598" type="sharef:proceedings">
		<date value="2002-06"/>
		<address type="sharef:placePublished">College Park, Maryland</address>
		<field type="bibtex:index">HT'02</field>
		<identifier type="sharef:isbn">1-58113-477-0</identifier>
		<field type="bibtex:key">13th ACM Conference on Hypertext and Hypermedia</field>
		<publisher>ACM Press</publisher>
		<title type="sharef:primaryTitle">13th ACM Conference on Hypertext and Hypermedia</title>
		<identifier type="sharef:uri" resourceType="text/html">http://informatik.uni-trier.de/~ley/db/conf/ht/ht2002.html</identifier>
	</reference>
	<reference name="mar03" src="bibtex:inproceedings" src-info="bibtex:line-19615" type="sharef:inproceedings" crossref="acmht03">
		<names type="sharef:author">
			<person>
				<givenname>Catherine C.</givenname>
				<surname>Marshall</surname>
			</person>
			<person>
				<givenname>Frank M.</givenname>
				<surname>Shipman</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Through scenarios in the popular press and technical papers in the research literature, the promise of the Semantic Web has raised a number of different expectations. These expectations can be traced to three different perspectives on the Semantic Web. The Semantic Web is portrayed as: (1) a universal library, to be readily accessed and used by humans in a variety of information use contexts; (2) the backdrop for the work of computational agents completing sophisticated activities on behalf of their human counterparts; and (3) a method for federating particular knowledge bases and databases to perform anticipated tasks for humans and their agents. Each of these perspectives has both theoretical and pragmatic entailments, and a wealth of past experiences to guide and temper our expectations. In this paper, we examine all three perspectives from rhetorical, theoretical, and pragmatic viewpoints with an eye toward possible outcomes as Semantic Web efforts move forward.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/900051.900063</identifier>
		<pages>57-66</pages>
		<title type="sharef:primaryTitle">Which Semantic Web?</title>
		<identifier type="sharef:uri">http://portal.acm.org/citation.cfm?doid=900063</identifier>
	</reference>
	<reference name="wuh03" src="bibtex:inproceedings" src-info="bibtex:line-19625" type="sharef:inproceedings" crossref="acmht03">
		<names type="sharef:author">
			<person>
				<givenname>Harris</givenname>
				<surname>Wu</surname>
			</person>
			<person>
				<givenname>Michael D.</givenname>
				<surname>Gordon</surname>
			</person>
			<person>
				<givenname>Kurt</givenname>
				<surname>DeMaagd</surname>
			</person>
			<person>
				<givenname>Nathan</givenname>
				<surname>Bos</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>We present an ongoing research project utilizing navigation and hyperlink data to aid collaborative knowledge building. We allow collaborators to personally organize documents and other research resources and make references to them. We combine their personal organizations and references to develop a unified, hierarchical categorization of these resources. We analyze collaborators' navigations to identify prominent research activities as well as the key documents related to these activities. We examine prominence over time to identify research trends.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/900051.900098</identifier>
		<pages>216-217</pages>
		<title type="sharef:primaryTitle">Link Analysis for Collaborative Knowledge Building</title>
		<identifier type="sharef:uri">http://portal.acm.org/citation.cfm?doid=900098</identifier>
	</reference>
	<reference name="acmht03" src="bibtex:proceedings" src-info="bibtex:line-19635" type="sharef:proceedings">
		<date value="2003-08"/>
		<address type="sharef:placePublished">Nottingham, UK</address>
		<field type="bibtex:index">HT'03</field>
		<identifier type="sharef:isbn">1-58113-704-4</identifier>
		<field type="bibtex:key">14th ACM Conference on Hypertext and Hypermedia</field>
		<publisher>ACM Press</publisher>
		<title type="sharef:primaryTitle">14th ACM Conference on Hypertext and Hypermedia</title>
		<identifier type="sharef:uri" resourceType="text/html">http://informatik.uni-trier.de/~ley/db/conf/ht/ht2003.html</identifier>
	</reference>
	<reference name="han04b" src="bibtex:inproceedings" src-info="bibtex:line-19652" type="sharef:inproceedings" crossref="acmht04">
		<names type="sharef:author">
			<person>
				<givenname>Frank Allan</givenname>
				<surname>Hansen</surname>
			</person>
			<person>
				<givenname>Niels Olof</givenname>
				<surname>Bouvin</surname>
			</person>
			<person>
				<givenname>Bent Guldbjerg</givenname>
				<surname>Christensen</surname>
			</person>
			<person>
				<givenname>Kaj</givenname>
				<surname>Grønbæk</surname>
			</person>
			<person>
				<givenname>Torben Bach</givenname>
				<surname>Pedersen</surname>
			</person>
			<person>
				<givenname>Jevgenij</givenname>
				<surname>Gagach</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>This paper presents applications of HyCon, a framework for context aware hypermedia systems. The HyCon framework encompasses annotations, links, and guided tours associating locations and RFID- or Bluetooth-tagged objects with maps, Web pages, and collections of resources. The user-created annotations, links and guided tours, are represented as XLink structures, and HyCon introduces the use of XLink for the representation of recorded geographical paths with annotations and links. The HyCon architecture extends upon earlier location based hypermedia systems by supporting authoring in the field and by providing access to browsing and searching information through a novel geo-based search (GBS) interface for the Web. Interface-wise, the HyCon prototype utilizes SVG on an interface level, for graphics as well as for user interface widgets on tablet PCs and mobile phones.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/1012807.1012837</identifier>
		<pages>98-107</pages>
		<title type="sharef:primaryTitle">Integrating the Web and the World: Contextual Trails on the Move</title>
		<identifier type="sharef:uri">http://portal.acm.org/citation.cfm?id=1012837</identifier>
	</reference>
	<reference name="car04" src="bibtex:inproceedings" src-info="bibtex:line-19662" type="sharef:inproceedings" crossref="acmht04">
		<names type="sharef:author">
			<person>
				<givenname>Leslie A.</givenname>
				<surname>Carr</surname>
			</person>
			<person>
				<givenname>Timothy</givenname>
				<surname>Miles-Board</surname>
			</person>
			<person>
				<givenname>Gary</givenname>
				<surname>Wills</surname>
			</person>
			<person>
				<givenname>Guillermo</givenname>
				<surname>Power</surname>
			</person>
			<person>
				<givenname>Christopher</givenname>
				<surname>Bailey</surname>
			</person>
			<person>
				<givenname>Wendy</givenname>
				<surname>Hall</surname>
			</person>
			<person>
				<givenname>Simon</givenname>
				<surname>Grange</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>A digital library, together with its users and its contents, does not exist in isolated splendour; nor in hypertext terms is it merely the intertextual relationships between its texts. There is a cycle of activities which provides the context for the library's existence, and which the library supports through its various roles of information access, discovery, storage, dissemination and preservation. This paper describes the role of digital library systems in the undertaking of science, and in particular in the context of the recent developments of the Grid for computer-supported scientific collaboration and Virtual Universities for computer-supported education. This paper focuses on a specific framework, the Dynamic Review Journal, which supports the development and dissemination of documents by assisting authors in collating and analysing experimental results, organising internal project discussions, and producing papers. By bridging the gap between the undertaking of experimental work and the dissemination of its results through electronic publication, this work addresses the cycle of activity in which a digital library rests.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/1012807.1012813</identifier>
		<pages>12-21</pages>
		<title type="sharef:primaryTitle">Extending the Role of the Digital Library: Computer Support for Creating Articles</title>
		<identifier type="sharef:uri">http://portal.acm.org/citation.cfm?doid=1012813</identifier>
	</reference>
	<reference name="kim04" src="bibtex:inproceedings" src-info="bibtex:line-19672" type="sharef:inproceedings" crossref="acmht04">
		<names type="sharef:author">
			<person>
				<givenname>Sunghun</givenname>
				<surname>Kim</surname>
			</person>
			<person>
				<givenname>E. James</givenname>
				<surname>Whitehead</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>We propose a new method to find related papers using an input paper and its hyperlinked citation relationships rather than keywords. Such related papers are especially useful as background reading for researchers new to a research field. In this paper we introduce the background reading paper extractor (BPE), and show various properties of academic paper references.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/1012807.1012824</identifier>
		<pages>44-45</pages>
		<title type="sharef:primaryTitle">Properties of Academic Paper References</title>
		<identifier type="sharef:uri">http://portal.acm.org/citation.cfm?doid=1012824</identifier>
	</reference>
	<reference name="kin04" src="bibtex:inproceedings" src-info="bibtex:line-19682" type="sharef:inproceedings" crossref="acmht04">
		<names type="sharef:author">
			<person>
				<givenname>James C.</givenname>
				<surname>King</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>We explain how the Portable Document Format was designed based upon some specific design criteria that were developed to make an advance beyond previous technology. The environmental variables (computing power, business climate) that affected the design are also discussed.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/1012807.1012810</identifier>
		<pages>95-97</pages>
		<title type="sharef:primaryTitle">A Format Design Case Study: PDF</title>
		<field type="bibtex:topic">pdf[0.8]</field>
		<identifier type="sharef:uri">http://portal.acm.org/citation.cfm?doid=1012810</identifier>
	</reference>
	<reference name="nue04" src="bibtex:inproceedings" src-info="bibtex:line-19693" type="sharef:inproceedings" crossref="acmht04">
		<names type="sharef:author">
			<person>
				<givenname>Peter J.</givenname>
				<surname>Nürnberg</surname>
			</person>
			<person>
				<givenname>Uffe Kock</givenname>
				<surname>Wiil</surname>
			</person>
			<person>
				<givenname>David L.</givenname>
				<surname>Hicks</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Structural computing asserts the primacy of structure over data. This has often been understood to mean that all levels of a structural computing system architecture should exhibit structure awareness, leading to data models centered around so-called "structural atoms." While systems based upon structural atoms do provide ubiquitous first-class structural abstractions, they also freeze the "granularity" of the structuring process throughout their architectures at design-time. That is, decisions regarding representations of structures in structural computing architectures based upon atoms cannot be recast at run-time. In this paper, we examine an alternative to atom-based models for structural computing systems that allows exactly such recasting. We demonstrate how this alternative model, which we call EAD, is superior to atom-based models for certain important applications, and describe our initial prototypical implementations.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/1012807.1012868</identifier>
		<pages>239-246</pages>
		<title type="sharef:primaryTitle">Rethinking Structural Computing Infrastructures</title>
	</reference>
	<reference name="acmht04" src="bibtex:proceedings" src-info="bibtex:line-19702" type="sharef:proceedings">
		<date value="2004-08"/>
		<address type="sharef:placePublished">Santa Cruz, California</address>
		<field type="bibtex:index">HT'04</field>
		<identifier type="sharef:isbn">1-58113-848-2</identifier>
		<field type="bibtex:key">15th ACM Conference on Hypertext and Hypermedia</field>
		<publisher>ACM Press</publisher>
		<title type="sharef:primaryTitle">15th ACM Conference on Hypertext and Hypermedia</title>
		<identifier type="sharef:uri" resourceType="text/html">http://informatik.uni-trier.de/~ley/db/conf/ht/ht2004.html</identifier>
	</reference>
	<reference name="wii05" src="bibtex:inproceedings" src-info="bibtex:line-19719" type="sharef:inproceedings" crossref="acmht05">
		<names type="sharef:author">
			<person>
				<givenname>Uffe Kock</givenname>
				<surname>Wiil</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Hypermedia is about structure. Right from the beginning in 1945 when Vannevar Bush described the Memory Extender (Memex), hypermedia researchers have envisioned the use of hypermedia technology to help support knowledge workers in their knowledge organization tasks. Although much has been achieved since 1945, there is still a long way to go before we have achieved the full potential of hypermedia technology for knowledge workers. This paper presents a quick view of the history of hypermedia technology for knowledge workers, identifies some issues with respect to the current work, and presents a vision of the future as well as a call for a joint community effort.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/1083356.1083358</identifier>
		<pages>4-6</pages>
		<title type="sharef:primaryTitle">Hypermedia Technology for Knowledge Workers: A Vision of the Future</title>
	</reference>
	<reference name="wil05q" src="bibtex:inproceedings" src-info="bibtex:line-19728" type="sharef:inproceedings" crossref="acmht05">
		<names type="sharef:author">
			<person>
				<givenname>Erik</givenname>
				<surname>Wilde</surname>
			</person>
			<person>
				<givenname>Marcel</givenname>
				<surname>Baschnagel</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Hypermedia systems like the Web heavily depend on their ability to link resources. One of the key features of the Web's URIs is their ability to not only specify a resource, but to also identify a subresource within that resource, by using a fragment identifier. Fragment identification enables user to create better hypermedia. We present a proposal for fragment identifiers for plain text files, which makes it possible to identify character or line ranges, or subresources identified by regular expressions. Using these fragment identifiers, it is possible to create more specific hyperlinks, by not only linking to a complete plain text resource, but only the relevant part of it. Along with this proposal, a prototype implementation is described which can be used both as a server-side testbed and as a client-side extension for the Firefox browser.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/1083356.1083398</identifier>
		<pages>211-213</pages>
		<title type="sharef:primaryTitle">Fragment Identifiers for Plain Text Files</title>
		<identifier type="sharef:uri">http://dret.net/netdret/publications#wil05q</identifier>
	</reference>
	<reference name="bry05b" src="bibtex:inproceedings" src-info="bibtex:line-19738" type="sharef:inproceedings" crossref="acmht05">
		<names type="sharef:author">
			<person>
				<givenname>François</givenname>
				<surname>Bry</surname>
			</person>
			<person>
				<givenname>Michael</givenname>
				<surname>Eckert</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Hyperlinks are an essential feature of the World Wide Web, highly responsible for its success. XLink improves on HTML's linking capabilities in several ways. In particular, links after XLink can be "out-of-line" (i.e., not depend at a link source) and collected in (possibly several) linkbases, which considerably ease building complex link structures. Regarding its architecture as a distributed and open system, the Web differs significantly from traditional hypermedia systems. Modeling of link structures and processing of linkbases under the Web's "open world linking" require rethinking the traditional approaches. This, unfortunately, has been rather neglected in the design of XLink. Adding a notion of "interface" to XLink, as suggested in this work, can considerably improve modeling of link structures. When a link structure is traversed, the relevant linkbase(s) might become ambiguous. We suggest three linkbase management modes governing the binding of a linkbase to a document to resolve this ambiguity.</p>
			</richtext>
		</abstract>
		<pages>135-144</pages>
		<title type="sharef:primaryTitle">Processing Link Structures and Linkbases in the Web's Open World Linking</title>
		<field type="bibtex:topic">xlink[0.8]</field>
		<identifier type="sharef:uri" resourceType="application/pdf">http://www.pms.ifi.lmu.de/publikationen/PMS-FB/PMS-FB-2005-22.pdf</identifier>
	</reference>
	<reference name="mou05" src="bibtex:inproceedings" src-info="bibtex:line-19748" type="sharef:inproceedings" crossref="acmht05">
		<names type="sharef:author">
			<person>
				<givenname>Stuart</givenname>
				<surname>Moulthrop</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Recent theories of hypertext usefully emphasize continuity with earlier media; but in the general social environment, this continuity is not well understood, and may even be opposed in some quarters. The paper argues that we should define hypertext as the basis for a new version of general literacy and place greater emphasis on teaching in our agenda for applications and research.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/1083356.1083402</identifier>
		<pages>227-231</pages>
		<title type="sharef:primaryTitle">What the Geeks Know: Hypertext and the Problem of Literacy</title>
	</reference>
	<reference name="han05" src="bibtex:inproceedings" src-info="bibtex:line-19757" type="sharef:inproceedings" crossref="acmht05">
		<names type="sharef:author">
			<person>
				<givenname>Frank Allan</givenname>
				<surname>Hansen</surname>
			</person>
			<person>
				<givenname>Bent Guldbjerg</givenname>
				<surname>Christensen</surname>
			</person>
			<person>
				<givenname>Niels Olof</givenname>
				<surname>Bouvin</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>This paper describes how the XML based RSS syndication formats used in weblogs can be utilized as the distribution medium for geo-spatial hypermedia, and how this approach can be used to create a highly distributed multi-user annotation system for geo-spatial hypermedia. It is demonstrated, how the HyCon annotation model can be formulated as a RSS 2.0 feed and how such feeds allow annotation threads to be distributed across multiple weblogs and servers.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/1083356.1083410</identifier>
		<pages>254-256</pages>
		<title type="sharef:primaryTitle">RSS as a Distribution Medium for Geo-Spatial Hypermedia</title>
		<field type="bibtex:topic">hycon[0.9]</field>
	</reference>
	<reference name="mil05" src="bibtex:inproceedings" src-info="bibtex:line-19767" type="sharef:inproceedings" crossref="acmht05">
		<names type="sharef:author">
			<person>
				<givenname>David E.</givenname>
				<surname>Millard</surname>
			</person>
			<person>
				<givenname>Nicholas</givenname>
				<surname>Gibbins</surname>
			</person>
			<person>
				<givenname>Danius T.</givenname>
				<surname>Michaelides</surname>
			</person>
			<person>
				<givenname>Mark J.</givenname>
				<surname>Weal</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Hypertext can be seen as a logic representation, where semantics are encoded in both the textual nodes and the graph of links. Systems that have a very formal representation of these semantics are able to manipulate the hypertexts in a sophisticated way; for example by adapting them or sculpting them at run-time. However, hypertext systems which require the author to write in terms of structures with explicit semantics are difficult/costly to write in, and can be seen as too restrictive by certain authors because they do not allow the playful ambiguity often associated with literary hypertext. In this paper we present a vector-based model of the formality of semantics in hypertext systems, where the vectors represent the translation of semantics from author to system and from system to reader. We categorise a variety of existing systems and draw out some general conclusions about the profiles they share. We believe that our model will help hypertext system designers analyse how their own systems formalise semantics, and will warn them when they need to mind the Semantic Gap between authors and readers.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/1083356.1083367</identifier>
		<pages>54-62</pages>
		<title type="sharef:primaryTitle">Mind the Semantic Gap</title>
		<identifier type="sharef:uri" resourceType="application/pdf">http://eprints.ecs.soton.ac.uk/12020/1/mind-the-semantic-gap.pdf</identifier>
	</reference>
	<reference name="dmi05" src="bibtex:inproceedings" src-info="bibtex:line-19777" type="sharef:inproceedings" crossref="acmht05">
		<names type="sharef:author">
			<person>
				<givenname>Pavel</givenname>
				<surname>Dmitriev</surname>
			</person>
			<person>
				<givenname>Carl</givenname>
				<surname>Lagoze</surname>
			</person>
			<person>
				<givenname>Boris</givenname>
				<surname>Suchkov</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>In recent years, many algorithms for the Web have been developed that work with information units distinct from individual web pages. These include segments of web pages or aggregation of web pages into web communities. Such logical information units improve a variety of web algorithms and provide the building blocks for the construction of organized information spaces such as digital libraries. In this paper, we focus on a type of logical information units called "compound documents". We argue that the ability to identify compound documents can improve information retrieval, automatic metadata generation, and navigation on the Web. We propose a unified framework for identifying the boundaries of compound documents, which combines both structural and content features of constituent web pages. The framework is based on a combination of machine learning and clustering algorithms, with the former algorithm supervising the latter one. We also propose a new method for evaluating quality of clusterings, based on a user behavior model. Experiments on a collection of educational web sites show that our approach can reliably identify most of the compound documents on these sites.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/1083356.1083370</identifier>
		<pages>66-74</pages>
		<title type="sharef:primaryTitle">As We May Perceive: Inferring Logical Documents from Hypertext</title>
	</reference>
	<reference name="acmht05" src="bibtex:proceedings" src-info="bibtex:line-19786" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>Siegfried</givenname>
				<surname>Reich</surname>
			</person>
			<person>
				<givenname>Manolis M.</givenname>
				<surname>Tzagarakis</surname>
			</person>
		</names>
		<date value="2005-08"/>
		<address type="sharef:placePublished">Salzburg, Austria</address>
		<field type="bibtex:index">HT'05</field>
		<identifier type="sharef:isbn">1-59593-168-6</identifier>
		<field type="bibtex:key">Sixteenth ACM Conference on Hypertext and Hypermedia</field>
		<publisher>ACM Press</publisher>
		<title type="sharef:primaryTitle">Sixteenth ACM Conference on Hypertext and Hypermedia</title>
		<identifier type="sharef:uri" resourceType="text/html">http://informatik.uni-trier.de/~ley/db/conf/ht/ht2005.html</identifier>
		<identifier type="sharef:uri">http://portal.acm.org/toc.cfm?id=1083356</identifier>
	</reference>
	<reference name="and06" src="bibtex:inproceedings" src-info="bibtex:line-19805" type="sharef:inproceedings" crossref="acmht06">
		<names type="sharef:author">
			<person>
				<givenname>Kenneth M.</givenname>
				<surname>Anderson</surname>
			</person>
			<person>
				<givenname>Frank Allan</givenname>
				<surname>Hansen</surname>
			</person>
			<person>
				<givenname>Niels Olof</givenname>
				<surname>Bouvin</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>This paper presents a new definition of context for context-aware computing based on a model that relies on dynamic queries over structured objects. This new model enables developers to flexibly specify the relationship between context and context data for their context-aware applications. We discuss a framework, HyConSC, that implements this model and describe how it can be used to build new contextual hypermedia systems. Our framework aids the developer in the iterative development of contextual queries (via a dynamic query browser) and offers support for context matching, a key feature of contextual hypermedia. We have tested the framework with data and sensors taken from the HyCon contextual hypermedia system and are now migrating HyCon to this new framework.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/1149941.1149961</identifier>
		<pages>99-110</pages>
		<title type="sharef:primaryTitle">Templates and Queries in Contextual Hypermedia</title>
		<field type="bibtex:topic">hycon[0.9]</field>
	</reference>
	<reference name="chi06" src="bibtex:inproceedings" src-info="bibtex:line-19815" type="sharef:inproceedings" crossref="acmht06">
		<names type="sharef:author">
			<person>
				<givenname>Alvin</givenname>
				<surname>Chin</surname>
			</person>
			<person>
				<givenname>Mark</givenname>
				<surname>Chignell</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Blogging has become the newest communication medium for creating a virtual community, a set of blogs linking back and forth to one another's postings, while discussing common topics. In this paper, we examine how communities can be discovered through interconnected blogs as a form of social hypertext. We propose a method and model that detects structures of community in the social network of blogs by integrating McMillan and Chavis' sense of community along with network analysis. From the model, we measure community in the blogs by aligning centrality measures from social network analysis with measures of sense of community obtained using behavioural surveys. We then illustrate the use of this approach with a case study built around an independent music blog. The strength of community measures were found to be well aligned with the network structure, based on centrality measures. Even though the sample size from the case study was small, once the structure and measure of communities are calibrated according to our social hypertext model, communities can be automatically found and measured for other blogs without the need for behavioural surveys.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/1149941.1149945</identifier>
		<pages>11-22</pages>
		<title type="sharef:primaryTitle">A Social Hypertext Model for Finding Community in Blogs</title>
	</reference>
	<reference name="mar06" src="bibtex:inproceedings" src-info="bibtex:line-19824" type="sharef:inproceedings" crossref="acmht06">
		<names type="sharef:author">
			<person>
				<givenname>Cameron</givenname>
				<surname>Marlow</surname>
			</person>
			<person>
				<givenname>Mor</givenname>
				<surname>Naaman</surname>
			</person>
			<person>
				<givenname>Danah M.</givenname>
				<surname>Boyd</surname>
			</person>
			<person>
				<givenname>Marc</givenname>
				<surname>Davis</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>In recent years, tagging systems have become increasingly popular. These systems enable users to add keywords (i.e., "tags") to Internet resources (e.g., web pages, images, videos) without relying on a controlled vocabulary. Tagging systems have the potential to improve search, spam detection, reputation systems, and personal organization while introducing new modalities of social communication and opportunities for data mining. This potential is largely due to the social structure that underlies many of the current systems. Despite the rapid expansion of applications that support tagging of resources, tagging systems are still not well studied or understood. In this paper, we provide a short description of the academic related work to date. We offer a model of tagging systems, specifically in the context of web-based systems, to help us illustrate the possible benefits of these tools. Since many such systems already exist, we provide a taxonomy of tagging systems to help inform their analysis and design, and thus enable researchers to frame and compare evidence for the sustainability of such systems. We also provide a simple taxonomy of incentives and contribution models to inform potential evaluative frameworks. While this work does not present comprehensive empirical results, we present a preliminary study of the photo-sharing and tagging system Flickr to demonstrate our model and explore some of the issues in one sample system. This analysis helps us outline and motivate possible future directions of research in tagging systems.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/1149941.1149949</identifier>
		<pages>31-40</pages>
		<title type="sharef:primaryTitle">HT06, Tagging Paper, Taxonomy, Flickr, Academic Article, To Read</title>
	</reference>
	<reference name="wu06" src="bibtex:inproceedings" src-info="bibtex:line-19833" type="sharef:inproceedings" crossref="acmht06">
		<names type="sharef:author">
			<person>
				<givenname>Harris</givenname>
				<surname>Wu</surname>
			</person>
			<person>
				<givenname>Mohammad</givenname>
				<surname>Zubair</surname>
			</person>
			<person>
				<givenname>Kurt</givenname>
				<surname>Maly</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Collaborative tagging systems, or folksonomies, have the potential of becoming technological infrastructure to support knowledge management activities in an organization or a society. There are many challenges, however. This paper presents designs that enhance collaborative tagging systems to meet some key challenges: community identification, ontology generation, user and document recommendation. Design prototypes, evaluation methodology and selected preliminary results are presented.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/1149941.1149962</identifier>
		<pages>111-114</pages>
		<title type="sharef:primaryTitle">Harvesting Social Knowledge from Folksonomies</title>
	</reference>
	<reference name="mer06" src="bibtex:inproceedings" src-info="bibtex:line-19842" type="sharef:inproceedings" crossref="acmht06">
		<names type="sharef:author">
			<person>
				<givenname>Robert</givenname>
				<surname>Mertens</surname>
			</person>
			<person>
				<givenname>Rosta</givenname>
				<surname>Farzan</surname>
			</person>
			<person>
				<givenname>Peter</givenname>
				<surname>Brusilovsky</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Web lectures are a form of educational content that differs from classic hypertext in a number of ways. Web lectures are easier to produce and therefore large amounts of material become accumulated in a short time. The recordings are significantly less structured than traditional web based learning content and they are time based media. Both the lack of structure and their time based nature pose difficulties for navigation in web lectures. The approach presented in this paper applies the basic concept of social navigation to facilitate navigation in web lectures. Social navigation support has been successfully employed for hypertext and picture augmented hypertext in the education domain. This paper describes how social navigation can be implemented for web lectures and how it can be used to augment existent navigation features.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/1149941.1149950</identifier>
		<pages>41-44</pages>
		<title type="sharef:primaryTitle">Social Navigation in Web Lectures</title>
	</reference>
	<reference name="wan06" src="bibtex:inproceedings" src-info="bibtex:line-19851" type="sharef:inproceedings" crossref="acmht06">
		<names type="sharef:author">
			<person>
				<givenname>Weigang</givenname>
				<surname>Wang</surname>
			</person>
			<person>
				<givenname>Jessica</givenname>
				<surname>Rubart</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Creating shared knowledge structures using cooperative hypermedia is a joint activity. The knowledge structures created should fit into the real world environment and reflect the common ground reached and evolved in the cooperation process of the knowledge workers. In order to facilitate the development of shared understanding among knowledge workers, Herbert Clark's theory on language use and Jean Piaget's cognitive theory are applied to the use of hypermedia language in cooperative work settings. To make the theories easier to apply, a conceptual framework is derived from them, which can inform the design and comparison of cooperative hypermedia systems and the use of hypermedia in cooperative settings.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/1149941.1149953</identifier>
		<pages>53-56</pages>
		<title type="sharef:primaryTitle">A Cognitive and Social Framework for Shared Understanding in Cooperative Hypermedia Authoring</title>
	</reference>
	<reference name="han06" src="bibtex:inproceedings" src-info="bibtex:line-19860" type="sharef:inproceedings" crossref="acmht06">
		<names type="sharef:author">
			<person>
				<givenname>Frank Allan</givenname>
				<surname>Hansen</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Ubiquitous annotation systems allow users to annotate physical places, objects, and persons with digital information. Especially in the field of location based information systems much work has been done to implement adaptive and context-aware systems, but few efforts have focused on the general requirements for linking information to objects in both physical and digital space. This paper surveys annotation techniques from open hypermedia systems, Web based annotation systems, and mobile and augmented reality systems to illustrate different approaches to four central challenges ubiquitous annotation systems have to deal with: anchoring, structuring, presentation, and authoring. Through a number of examples each challenge is discussed and HyCon, a context-aware hypermedia framework developed at the University of Aarhus, Denmark, is used to illustrate an integrated approach to ubiquitous annotations. Finally, a taxonomy of annotation systems is presented. The taxonomy can be used both to categorize system based on the way they present annotations and to choose the right technology for interfacing with annotations when implementing new systems.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/1149941.1149967</identifier>
		<pages>121-132</pages>
		<title type="sharef:primaryTitle">Ubiquitous Annotation Systems: Technologies and Challenges</title>
		<field type="bibtex:topic">hycon[0.8]</field>
	</reference>
	<reference name="mil06" src="bibtex:inproceedings" src-info="bibtex:line-19870" type="sharef:inproceedings" crossref="acmht06">
		<names type="sharef:author">
			<person>
				<givenname>David E.</givenname>
				<surname>Millard</surname>
			</person>
			<person>
				<givenname>Martin</givenname>
				<surname>Ross</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Web 2.0 is the popular name of a new generation of Web applications, sites and companies that emphasis openness, community and interaction. Examples include technologies such as Blogs and Wikis, and sites such as Flickr. In this paper we compare these next generation tools to the aspirations of the early Hypertext pioneers to see if their aims have finally been realized.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/1149941.1149947</identifier>
		<pages>27-30</pages>
		<title type="sharef:primaryTitle">Web 2.0: Hypertext by Any Other Name?</title>
	</reference>
	<reference name="acmht06" src="bibtex:proceedings" src-info="bibtex:line-19879" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>Uffe Kock</givenname>
				<surname>Wiil</surname>
			</person>
			<person>
				<givenname>Peter J.</givenname>
				<surname>Nürnberg</surname>
			</person>
			<person>
				<givenname>Jessica</givenname>
				<surname>Rubart</surname>
			</person>
		</names>
		<date value="2006-08"/>
		<address type="sharef:placePublished">Odense, Denmark</address>
		<field type="bibtex:index">HT'06</field>
		<identifier type="sharef:isbn">1-59593-417-0</identifier>
		<field type="bibtex:key">Seventeenth ACM Conference on Hypertext and Hypermedia</field>
		<publisher>ACM Press</publisher>
		<title type="sharef:primaryTitle">Seventeenth ACM Conference on Hypertext and Hypermedia</title>
		<identifier type="sharef:uri" resourceType="text/html">http://informatik.uni-trier.de/~ley/db/conf/ht/ht2006.html</identifier>
	</reference>
	<reference name="kol08" src="bibtex:inproceedings" src-info="bibtex:line-19897" type="sharef:inproceedings" crossref="acmht08">
		<names type="sharef:author">
			<person>
				<givenname>Okan</givenname>
				<surname>Kolak</surname>
			</person>
			<person>
				<givenname>Bill N.</givenname>
				<surname>Schilit</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Scanning books, magazines, and newspapers has become a widespread activity because people believe that much of the worlds information still resides off-line. In general after works are scanned they are indexed for search and processed to add links. This paper describes a new approach to automatically add links by mining popularly quoted passages. Our technique connects elements that are semantically rich, so strong relations are made. Moreover, link targets point within a work, facilitating navigation. This paper makes three contributions. We describe a scalable algorithm for mining repeated word sequences from extremely large text corpora. Second, we present techniques that filter and rank the repeated sequences for quotations. Third, we present a new user interface for navigating across and within works in the collection using quotation links. Our system has been run on a digital library of over 1 million books and has been used by thousands of people.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/1379092.1379117</identifier>
		<pages>117-126</pages>
		<title type="sharef:primaryTitle">Generating Links by Mining Quotations</title>
	</reference>
	<reference name="acmht08" src="bibtex:proceedings" src-info="bibtex:line-19906" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>Peter</givenname>
				<surname>Brusilovsky</surname>
			</person>
			<person>
				<givenname>Hugh C.</givenname>
				<surname>Davis</surname>
			</person>
		</names>
		<date value="2008-06"/>
		<address type="sharef:placePublished">Pittsburgh, Pennsylvania</address>
		<field type="bibtex:index">Hypertext '08</field>
		<identifier type="sharef:isbn">978-1-59593-985-2</identifier>
		<field type="bibtex:key">Nineteenth ACM Conference on Hypertext and Hypermedia (Hypertext '08)</field>
		<publisher>ACM Press</publisher>
		<title type="sharef:primaryTitle">Nineteenth ACM Conference on Hypertext and Hypermedia (Hypertext '08)</title>
		<identifier type="sharef:uri" resourceType="text/html">http://www.informatik.uni-trier.de/~ley/db/conf/ht/ht2008.html</identifier>
	</reference>
	<reference name="hal02b" src="bibtex:inproceedings" src-info="bibtex:line-19924" type="sharef:inproceedings" crossref="compdoc02">
		<names type="sharef:author">
			<person>
				<givenname>Kari L.</givenname>
				<surname>Halsted</surname>
			</person>
			<person>
				<givenname>James H.</givenname>
				<surname>Roberts</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>In this paper, we discuss the theoretical and practical elements of designing an open source User Assistance (UA) System. Specifically, we introduce UCD requirements, including those to accommodate different user modes for UA architectures and complex document integration. We then detail how these requirements were delivered in the open source Eclipse project.</p>
			</richtext>
		</abstract>
		<pages>49-59</pages>
		<title type="sharef:primaryTitle">Eclipse Help System: An Open Source User Assistance Offering</title>
		<field type="bibtex:topic">eclipse[0.8]</field>
		<identifier type="sharef:uri">http://portal.acm.org/citation.cfm?id=584955.584964</identifier>
	</reference>
	<reference name="compdoc02" src="bibtex:proceedings" src-info="bibtex:line-19934" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>Kathy</givenname>
				<surname>Haramundanis</surname>
			</person>
			<person>
				<givenname>Michael</givenname>
				<surname>Priestley</surname>
			</person>
		</names>
		<date value="2002-10"/>
		<address type="sharef:placePublished">Toronto, Canada</address>
		<identifier type="sharef:isbn">1-58113-543-2</identifier>
		<field type="bibtex:key">20th Annual International Conference on Computer Documentation</field>
		<publisher>ACM Press</publisher>
		<title type="sharef:primaryTitle">20th Annual International Conference on Computer Documentation</title>
		<identifier type="sharef:uri" resourceType="text/html">http://www.informatik.uni-trier.de/~ley/db/conf/sigdoc/sigdoc2002.html</identifier>
	</reference>
	<reference name="gra02" src="bibtex:inproceedings" src-info="bibtex:line-19951" type="sharef:inproceedings" crossref="cikm2002">
		<names type="sharef:author">
			<person>
				<givenname>Torsten</givenname>
				<surname>Grabs</surname>
			</person>
			<person>
				<givenname>Klemens</givenname>
				<surname>Böhm</surname>
			</person>
			<person>
				<givenname>Hans-Jörg</givenname>
				<surname>Schek</surname>
			</person>
		</names>
		<identifier type="sharef:doi">10.1145/584792.584819</identifier>
		<pages>142-152</pages>
		<title type="sharef:primaryTitle">Efficient Transaction Management for XML Documents</title>
		<field type="bibtex:topic">xmltm[1]</field>
		<identifier type="sharef:uri">http://www.dbs.ethz.ch/cgi-bin/pap_detail.cgi?205</identifier>
	</reference>
	<reference name="lee02" src="bibtex:inproceedings" src-info="bibtex:line-19961" type="sharef:inproceedings" crossref="cikm2002">
		<names type="sharef:author">
			<person>
				<givenname>Dongwon</givenname>
				<surname>Lee</surname>
			</person>
			<person>
				<givenname>Murali</givenname>
				<surname>Mani</surname>
			</person>
			<person>
				<givenname>Frank</givenname>
				<surname>Chiu</surname>
			</person>
			<person>
				<givenname>Wesley W.</givenname>
				<surname>Chu</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Two algorithms, called NeT and CoT, to translate relational schemas to XML schemas using various semantic constraints are presented. The XML schema representation we use is a language-independent formalism named XSchema, that is both precise and concise. A given XSchema can be mapped to a schema in any of the existing XML schema language proposals. Our proposed algorithms have the following characteristics: (1) NeT derives a nested structure from a flat relational model by repeatedly applying the nest operator on each table so that the resulting XML schema becomes hierarchical, and (2) CoT considers not only the structure of relational schemas, but also semantic constraints such as inclusion dependencies during the translation. It takes as input a relational schema where multiple tables are interconnected through inclusion dependencies and converts it into a good XSchema. To validate our proposals, we present experimental results using both real schemas from the UCI repository and synthetic schemas from TPC-H.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/584792.584840</identifier>
		<pages>282-291</pages>
		<title type="sharef:primaryTitle">NeT &amp; CoT: Translating Relational Schemas to XML Schemas using Semantic Constraints</title>
		<field type="bibtex:topic">xschema[1]</field>
	</reference>
	<reference name="cikm2002" src="bibtex:proceedings" src-info="bibtex:line-19971" type="sharef:proceedings">
		<date value="2002-11"/>
		<address type="sharef:placePublished">McLean, Virginia</address>
		<field type="bibtex:index">CIKM 2002</field>
		<identifier type="sharef:isbn">1-58113-492-4</identifier>
		<publisher>ACM Press</publisher>
		<title type="sharef:primaryTitle">CIKM 2002: Eleventh International Conference on Information and Knowledge Management</title>
		<identifier type="sharef:uri" resourceType="text/html">http://www.informatik.uni-trier.de/~ley/db/conf/cikm/cikm2002.html</identifier>
	</reference>
	<reference name="hol92" src="bibtex:inproceedings" src-info="bibtex:line-19987" type="sharef:inproceedings" crossref="chi92">
		<names type="sharef:author">
			<person>
				<givenname>Jim</givenname>
				<surname>Hollan</surname>
			</person>
			<person>
				<givenname>Scott</givenname>
				<surname>Stornetta</surname>
			</person>
		</names>
		<field type="bibtex:index">telecommunications, CSCW</field>
		<pages>119-125</pages>
		<title type="sharef:primaryTitle">Beyond Being There</title>
	</reference>
	<reference name="chi92" src="bibtex:proceedings" src-info="bibtex:line-19995" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>Penny</givenname>
				<surname>Bauersfeld</surname>
			</person>
			<person>
				<givenname>John</givenname>
				<surname>Bennett</surname>
			</person>
			<person>
				<givenname>Gene</givenname>
				<surname>Lynch</surname>
			</person>
		</names>
		<date value="1992"/>
		<address type="sharef:placePublished">Monterey, California</address>
		<field type="bibtex:index">CHI '92</field>
		<identifier type="sharef:isbn">0-201-53344-X</identifier>
		<publisher>ACM Press</publisher>
		<title type="sharef:primaryTitle">CHI '92: ACM Conference on Human Factors and Computing Systems</title>
	</reference>
	<reference name="haa93" src="bibtex:inproceedings" src-info="bibtex:line-20010" type="sharef:inproceedings" crossref="chi93">
		<names type="sharef:author">
			<person>
				<givenname>Anja</givenname>
				<surname>Haake</surname>
			</person>
			<person>
				<givenname>Jörg M.</givenname>
				<surname>Haake</surname>
			</person>
		</names>
		<field type="bibtex:index">CSCW, versioning, cooperation modes, alternative object states, group awareness, hypermedia, CoVer, SEPIA, collaborative editing</field>
		<pages>406-413</pages>
		<title type="sharef:primaryTitle">Take CoVer: Exploiting Version Support in Cooperative Systems</title>
	</reference>
	<reference name="chi93" src="bibtex:proceedings" src-info="bibtex:line-20018" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>Stacey</givenname>
				<surname>Ashlund</surname>
			</person>
			<person>
				<givenname>Austin</givenname>
				<surname>Henderson</surname>
			</person>
			<person>
				<givenname>Erik</givenname>
				<surname>Hollnagel</surname>
			</person>
			<person>
				<givenname>Kevin</givenname>
				<surname>Mullet</surname>
			</person>
			<person>
				<givenname>Ted</givenname>
				<surname>White</surname>
			</person>
		</names>
		<date value="1993"/>
		<address type="sharef:placePublished">Amsterdam, Netherlands</address>
		<field type="bibtex:index">INTERCHI '93</field>
		<identifier type="sharef:isbn">90-5199-133-9</identifier>
		<publisher>IOS Press</publisher>
		<title type="sharef:primaryTitle">INTERCHI '93: Conference on Human Factors and Computing Systems</title>
	</reference>
	<reference name="sto94" src="bibtex:inproceedings" src-info="bibtex:line-20033" type="sharef:inproceedings" crossref="chi94">
		<names type="sharef:author">
			<person>
				<givenname>Maureen C.</givenname>
				<surname>Stone</surname>
			</person>
			<person>
				<givenname>Ken</givenname>
				<surname>Fishkin</surname>
			</person>
			<person>
				<givenname>Eric A.</givenname>
				<surname>Bier</surname>
			</person>
		</names>
		<field type="bibtex:index">Magic Lens</field>
		<pages>306-312</pages>
		<title type="sharef:primaryTitle">The Movable Filter as a User Interface Tool</title>
	</reference>
	<reference name="chi94" src="bibtex:proceedings" src-info="bibtex:line-20041" type="sharef:proceedings">
		<date value="1994-04"/>
		<address type="sharef:placePublished">Boston, Massachusetts</address>
		<field type="bibtex:index">CHI '94</field>
		<publisher>ACM Press</publisher>
		<title type="sharef:primaryTitle">CHI '94: ACM Conference on Human Factors and Computing Systems</title>
	</reference>
	<reference name="con95" src="bibtex:inproceedings" src-info="bibtex:line-20055" type="sharef:inproceedings" crossref="chi95">
		<names type="sharef:author">
			<person>
				<givenname>Sunny</givenname>
				<surname>Consolvo</surname>
			</person>
			<person>
				<givenname>Ian E.</givenname>
				<surname>Smith</surname>
			</person>
			<person>
				<givenname>Tara</givenname>
				<surname>Matthews</surname>
			</person>
			<person>
				<givenname>Anthony</givenname>
				<surname>LaMarca</surname>
			</person>
			<person>
				<givenname>Jason</givenname>
				<surname>Tabert</surname>
			</person>
			<person>
				<givenname>Pauline</givenname>
				<surname>Powledge</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Advances in location-enhanced technology are making it easier for us to be located by others. These new technologies present a difficult privacy tradeoff, as disclosing one's location to another person or service could be risky, yet valuable. To explore whether and what users are willing to disclose about their location to social relations, we conducted a three-phased formative study. Our results show that the most important factors were who was requesting, why the requester wanted the participant's location, and what level of detail would be most useful to the requester. After determining these, participants were typically willing to disclose either the most useful detail or nothing about their location. From our findings, we reflect on the decision process for location disclosure. With these results, we hope to influence the design of future location-enhanced applications and services.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/1054972.1054985</identifier>
		<pages>81-90</pages>
		<title type="sharef:primaryTitle">Location Disclosure to Social Relations: Why, When, &amp; What People Want to Share</title>
	</reference>
	<reference name="pat95" src="bibtex:inproceedings" src-info="bibtex:line-20064" type="sharef:inproceedings" crossref="chi95">
		<names type="sharef:author">
			<person>
				<givenname>Sameer</givenname>
				<surname>Patil</surname>
			</person>
			<person>
				<givenname>Jennifer</givenname>
				<surname>Lai</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>We report on a study (N=36) of user preferences for balancing awareness with privacy. Participants defined permissions for sharing of location, availability, calendar information and instant messaging (IM) activity within an application called mySpace. MySpace is an interactive visualization of the physical workplace that provides dynamic information about people, places and equipment. We found a significant preference for defining privacy permissions at the group level. While "family" received high levels of awareness sharing, interestingly, "team" was granted comparable levels during business hours at work. Surprisingly, presenting participants with a detailed list of all pieces of personal context to which the system had access, did not result in more conservative privacy settings. Although location was the most sensitive aspect of awareness, participants were comfortable disclosing room-level location information to their team members at work. Our findings suggest utilizing grouping mechanisms to balance privacy control with configuration burden, and argue for increased system transparency to build trust.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/1054972.1054987</identifier>
		<pages>101-110</pages>
		<title type="sharef:primaryTitle">Who Gets to Know What When: Configuring Privacy Permissions in an Awareness Application</title>
	</reference>
	<reference name="lam95" src="bibtex:inproceedings" src-info="bibtex:line-20073" type="sharef:inproceedings" crossref="chi95">
		<names type="sharef:author">
			<person>
				<givenname>John</givenname>
				<surname>Lamping</surname>
			</person>
			<person>
				<givenname>Ramana</givenname>
				<surname>Rao</surname>
			</person>
			<person>
				<givenname>Peter</givenname>
				<surname>Pirolli</surname>
			</person>
		</names>
		<field type="bibtex:index">hyperbolic trees</field>
		<pages>401-408</pages>
		<title type="sharef:primaryTitle">A Focus+Context Technique Based on Hyperbolic Geometry for Visualizing Large Hierarchies</title>
		<identifier type="sharef:uri" resourceType="text/html">http://www.acm.org/sigchi/chi95/proceedings/papers/jl_bdy.htm</identifier>
	</reference>
	<reference name="chi95" src="bibtex:proceedings" src-info="bibtex:line-20082" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>Irvin R.</givenname>
				<surname>Katz</surname>
			</person>
			<person>
				<givenname>Robert L.</givenname>
				<surname>Mack</surname>
			</person>
			<person>
				<givenname>Linn</givenname>
				<surname>Marks</surname>
			</person>
			<person>
				<givenname>Mary Beth</givenname>
				<surname>Rosson</surname>
			</person>
			<person>
				<givenname>Jakob</givenname>
				<surname>Nielsen</surname>
			</person>
		</names>
		<date value="1995-05"/>
		<address type="sharef:placePublished">Denver, Colorado</address>
		<field type="bibtex:index">CHI '95</field>
		<identifier type="sharef:isbn">0897916948</identifier>
		<publisher>ACM Press</publisher>
		<title type="sharef:primaryTitle">CHI '95: ACM Conference on Human Factors and Computing Systems</title>
		<identifier type="sharef:uri" resourceType="text/html">http://www.acm.org/sigchi/chi95/proceedings/top.html</identifier>
		<identifier type="sharef:uri" resourceType="text/html">http://www.informatik.uni-trier.de/~ley/db/conf/chi/chi95.html</identifier>
	</reference>
	<reference name="sch98" src="bibtex:inproceedings" src-info="bibtex:line-20100" type="sharef:inproceedings" crossref="chi98">
		<names type="sharef:author">
			<person>
				<givenname>Bill N.</givenname>
				<surname>Schilit</surname>
			</person>
			<person>
				<givenname>Gene</givenname>
				<surname>Golovchinsky</surname>
			</person>
			<person>
				<givenname>Morgan N.</givenname>
				<surname>Price</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Reading frequently involves not just looking at words on a page, but also underlining, highlighting and commenting, either on the text or in a separate notebook. This combination of reading with critical thinking and learning is called active reading. To explore the premise that computation can enhance active reading we have built the XLibris "active reading machine." XLibris uses a commercial high-resolution pen tablet display along with a paper-like user interface to support the key affordances of paper for active reading: the reader can hold a scanned image of a page in his lap and mark on it with digital ink. To go beyond paper, XLibris monitors the free-form ink annotations made while reading, and uses these to organize and to search for information. Readers can review, sort and filter clippings of their annotated text in a "Reader's Notebook." XLibris also searches for material related to the annotated text, and displays links to similar documents unobtrusively in the margin. XLibris demonstrates that computers can help active readers organize and find information while retaining many of the advantages of reading on paper.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/274644.274680</identifier>
		<pages>249-256</pages>
		<title type="sharef:primaryTitle">Beyond Paper: Supporting Active Reading with Free Form Digital Ink Annotations</title>
		<field type="bibtex:topic">xlibris[1]</field>
		<identifier type="sharef:uri" resourceType="application/pdf">http://www.fxpal.com/publications/FXPAL-PR-98-053.pdf</identifier>
	</reference>
	<reference name="chi98" src="bibtex:proceedings" src-info="bibtex:line-20111" type="sharef:proceedings">
		<date value="1998-04"/>
		<address type="sharef:placePublished">Los Angeles, California</address>
		<field type="bibtex:index">CHI '98</field>
		<publisher>ACM Press</publisher>
		<title type="sharef:primaryTitle">Proceeding of the CHI 98 Conference on Human Factors in Computing Systems</title>
		<identifier type="sharef:uri">http://acm.org/sigchi/chi98/</identifier>
		<identifier type="sharef:uri" resourceType="text/html">http://www.informatik.uni-trier.de/~ley/db/conf/chi/chi98.html</identifier>
	</reference>
	<reference name="bou00a" src="bibtex:inproceedings" src-info="bibtex:line-20127" type="sharef:inproceedings" crossref="chi2000">
		<names type="sharef:author">
			<person>
				<givenname>Anna</givenname>
				<surname>Bouch</surname>
			</person>
			<person>
				<givenname>Nina</givenname>
				<surname>Bhatti</surname>
			</person>
			<person>
				<givenname>Allan</givenname>
				<surname>Kuchinsky</surname>
			</person>
		</names>
		<pages>297-304</pages>
		<title type="sharef:primaryTitle">Quality is in the Eye of the Beholder: Meeting Users' Requirements for Internet Quality of Service</title>
		<identifier type="sharef:uri">http://portal.acm.org/citation.cfm?id=332447</identifier>
	</reference>
	<reference name="zel00" src="bibtex:inproceedings" src-info="bibtex:line-20135" type="sharef:inproceedings" crossref="chi2000">
		<names type="sharef:author">
			<person>
				<givenname>Polle T.</givenname>
				<surname>Zellweger</surname>
			</person>
			<person>
				<givenname>Susan Harkness</givenname>
				<surname>Regli</surname>
			</person>
			<person>
				<givenname>Jock D.</givenname>
				<surname>Mackinlay</surname>
			</person>
			<person>
				<givenname>Bay-Wei</givenname>
				<surname>Chang</surname>
			</person>
		</names>
		<pages>249-256</pages>
		<title type="sharef:primaryTitle">The Impact of Fluid Documents on Reading and Browsing: An Observational Study</title>
		<identifier type="sharef:uri">http://portal.acm.org/citation.cfm?id=332440</identifier>
	</reference>
	<reference name="chi2000" src="bibtex:proceedings" src-info="bibtex:line-20143" type="sharef:proceedings">
		<date value="2000-04"/>
		<address type="sharef:placePublished">Amsterdam, Netherlands</address>
		<field type="bibtex:index">CHI 2000</field>
		<publisher>ACM Press</publisher>
		<title type="sharef:primaryTitle">ACM Conference on Human Factors and Computing Systems (CHI 2000)</title>
	</reference>
	<reference name="bru02" src="bibtex:inproceedings" src-info="bibtex:line-20158" type="sharef:inproceedings" crossref="chi2002">
		<names type="sharef:author">
			<person>
				<givenname>A. J. Bernheim</givenname>
				<surname>Brush</surname>
			</person>
			<person>
				<givenname>David</givenname>
				<surname>Bargeron</surname>
			</person>
			<person>
				<givenname>Jonathan</givenname>
				<surname>Grudin</surname>
			</person>
			<person>
				<givenname>Anoop</givenname>
				<surname>Gupta</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Notification and shared annotations go hand-in-hand. Notification of activity in a shared document system is known to support awareness and improve asynchronous collaboration, but few studies have examined user needs and explored design tradeoffs. We examined large-scale use of notifications in a commercial system and found it lacking. We designed and deployed enhancements to the system, then conducted a field study to gauge their effect. We found that providing more information in notification messages, supporting multiple communication channels through which notifications can be received, and allowing customization of notification messages are particularly important. Overall awareness of annotation activity on software specifications increased with our enhancements.</p>
			</richtext>
		</abstract>
		<pages>89-96</pages>
		<title type="sharef:primaryTitle">Notification for Shared Annotation of Digital Documents</title>
		<identifier type="sharef:uri">http://portal.acm.org/citation.cfm?doid=503376.503393</identifier>
	</reference>
	<reference name="pel02" src="bibtex:inproceedings" src-info="bibtex:line-20167" type="sharef:inproceedings" crossref="chi2002a">
		<names type="sharef:author">
			<person>
				<givenname>Etienne</givenname>
				<surname>Pelaprat</surname>
			</person>
			<person>
				<givenname>R. Benjamin</givenname>
				<surname>Shapiro</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Current software interfaces fail to incorporate historical data from user interaction into their design. While some systems exhibit a minimalist use of history in the form of undo and redo, selective menu items, and other static elements, there has been a lack of use of history in the dynamic elements of interaction. We propose a more widespread use of historical data from user-software interaction to augment the desktop and application environment. We believe the use of historical data can improve the user's experience at many different levels. Our approach begins by assuming that everything the user is doing on the desktop is important to them, and that it will be important again in the future.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/506443.506643</identifier>
		<pages>876-877</pages>
		<title type="sharef:primaryTitle">User Activity Histories</title>
	</reference>
	<reference name="eng02" src="bibtex:inproceedings" src-info="bibtex:line-20176" type="sharef:inproceedings" crossref="chi2002a">
		<names type="sharef:author">
			<person>
				<givenname>Jennifer</givenname>
				<surname>English</surname>
			</person>
			<person>
				<givenname>Marti A.</givenname>
				<surname>Hearst</surname>
			</person>
			<person>
				<givenname>Rashmi R.</givenname>
				<surname>Sinha</surname>
			</person>
			<person>
				<givenname>Kirsten</givenname>
				<surname>Swearingen</surname>
			</person>
			<person>
				<givenname>Ka-Ping</givenname>
				<surname>Yee</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>One of the most pressing usability issues in the design of large web sites is that of the organization of search results. A previous study on a moderate-sized web site indicated that users understood and preferred dynamically organized faceted metadata over standard search. We are now examining how to scale this approach to very large collections, since it is difficult to present hierarchical faceted metadata in a manner appealing and understandable to general users. We have iteratively designed and tested interfaces that address these design challenges; the most recent version is receiving enthusiastic responses in ongoing usability studies.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/506443.506517</identifier>
		<pages>628-639</pages>
		<title type="sharef:primaryTitle">Hierarchical Faceted Metadata in Site Search Interfaces</title>
	</reference>
	<reference name="chi2002" src="bibtex:proceedings" src-info="bibtex:line-20185" type="sharef:proceedings">
		<date value="2002-04"/>
		<address type="sharef:placePublished">Minneapolis, Minnesota</address>
		<field type="bibtex:index">CHI 2002</field>
		<publisher>ACM Press</publisher>
		<title type="sharef:primaryTitle">SIGCHI Conference on Human Factors and Computing Systems (CHI 2002)</title>
		<identifier type="sharef:uri" resourceType="text/html">http://www.informatik.uni-trier.de/~ley/db/conf/chi/chi2002.html</identifier>
	</reference>
	<reference name="chi2002a" src="bibtex:proceedings" src-info="bibtex:line-20196" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>Loren G.</givenname>
				<surname>Terveen</surname>
			</person>
			<person>
				<givenname>Dennis R.</givenname>
				<surname>Wixon</surname>
			</person>
		</names>
		<date value="2002-04"/>
		<address type="sharef:placePublished">Minneapolis, Minnesota</address>
		<field type="bibtex:index">CHI 2002</field>
		<publisher>ACM Press</publisher>
		<title type="sharef:primaryTitle">Extended Abstracts of the 2002 Conference on Human Factors in Computing Systems (CHI 2002)</title>
		<identifier type="sharef:uri" resourceType="text/html">http://www.informatik.uni-trier.de/~ley/db/conf/chi/chi2002a.html</identifier>
	</reference>
	<reference name="rod03" src="bibtex:inproceedings" src-info="bibtex:line-20212" type="sharef:inproceedings" crossref="chi2003">
		<names type="sharef:author">
			<person>
				<givenname>Kerry</givenname>
				<surname>Rodden</surname>
			</person>
			<person>
				<givenname>Kenneth R.</givenname>
				<surname>Wood</surname>
			</person>
		</names>
		<pages>409-416</pages>
		<title type="sharef:primaryTitle">How do People manage their Digital Photographs?</title>
		<identifier type="sharef:uri">http://portal.acm.org/citation.cfm?id=642682</identifier>
	</reference>
	<reference name="pal03" src="bibtex:inproceedings" src-info="bibtex:line-20220" type="sharef:inproceedings" crossref="chi2003">
		<names type="sharef:author">
			<person>
				<givenname>Leysia</givenname>
				<surname>Palen</surname>
			</person>
			<person>
				<givenname>Paul</givenname>
				<surname>Dourish</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Although privacy is broadly recognized as a dominant concern for the development of novel interactive technologies, our ability to reason analytically about privacy in real settings is limited. A lack of conceptual interpretive frameworks makes it difficult to unpack interrelated privacy issues in settings where information technology is also present. Building on theory developed by social psychologist Irwin Altman, we outline a model of privacy as a dynamic, dialectic process. We discuss three tensions that govern interpersonal privacy management in everyday life, and use these to explore select technology case studies drawn from the research literature. These suggest new ways for thinking about privacy in socio-technical environments as a practical matter.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/642611.642635</identifier>
		<pages>129-136</pages>
		<title type="sharef:primaryTitle">Unpacking 'Privacy' for a Networked World</title>
		<identifier type="sharef:uri" resourceType="application/pdf">http://www.cs.colorado.edu/~palen/Papers/palen-dourish.pdf</identifier>
	</reference>
	<reference name="chi2003" src="bibtex:proceedings" src-info="bibtex:line-20230" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>Gilbert</givenname>
				<surname>Cockton</surname>
			</person>
			<person>
				<givenname>Panu</givenname>
				<surname>Korhonen</surname>
			</person>
		</names>
		<date value="2003-04"/>
		<address type="sharef:placePublished">Fort Lauderdale, Florida</address>
		<field type="bibtex:index">CHI 2003</field>
		<identifier type="sharef:isbn">1581136307</identifier>
		<publisher>ACM Press</publisher>
		<title type="sharef:primaryTitle">Conference on Human Factors and Computing Systems (CHI 2003)</title>
		<identifier type="sharef:uri">http://portal.acm.org/toc.cfm?id=642611</identifier>
		<identifier type="sharef:uri" resourceType="text/html">http://www.informatik.uni-trier.de/~ley/db/conf/chi/chi2003.html</identifier>
	</reference>
	<reference name="wuh04" src="bibtex:inproceedings" src-info="bibtex:line-20248" type="sharef:inproceedings" crossref="chi2004ea">
		<names type="sharef:author">
			<person>
				<givenname>Harris</givenname>
				<surname>Wu</surname>
			</person>
			<person>
				<givenname>Michael D.</givenname>
				<surname>Gordon</surname>
			</person>
			<person>
				<givenname>Kurt</givenname>
				<surname>DeMaagd</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>We introduce the concept of "document co-organization" and describe such a system. By document co-organization we mean that individuals are allowed to hierarchically organize documents personally and share their hierarchies with others, while the system generates a "consensus" hierarchy from these personal hierarchies, which provides a full, common, and emergent view of all documents. By allowing users to retrieve documents from their own organization (hierarchy), another user's, the consensus hierarchy, or a time-based hierarchy, we provide access corresponding to different characteristics of knowledge tasks: they are personal, collective, social, and time-sensitive. In a class website experiment, we show that for a complex knowledge task, hierarchies are used more frequently than search. One surprising finding is how often students use others' personal hierarchies.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/985921.986026</identifier>
		<pages>1211-1214</pages>
		<title type="sharef:primaryTitle">Document Co-Organization in an Online Knowledge Community</title>
		<identifier type="sharef:uri">http://portal.acm.org/citation.cfm?doid=986026</identifier>
	</reference>
	<reference name="chi2004ea" src="bibtex:proceedings" src-info="bibtex:line-20258" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>Elizabeth</givenname>
				<surname>Dykstra-Erickson</surname>
			</person>
			<person>
				<givenname>Manfred</givenname>
				<surname>Tscheligi</surname>
			</person>
		</names>
		<date value="2004-04"/>
		<address type="sharef:placePublished">Vienna, Austria</address>
		<field type="bibtex:index">CHI 2004</field>
		<identifier type="sharef:isbn">1-58113-703-6</identifier>
		<publisher>ACM Press</publisher>
		<title type="sharef:primaryTitle">Extended abstracts of the 2004 Conference on Human Factors in Computing Systems</title>
		<identifier type="sharef:uri" resourceType="text/html">http://informatik.uni-trier.de/~ley/db/conf/chi/chi2004a.html</identifier>
	</reference>
	<reference name="aga06" src="bibtex:inproceedings" src-info="bibtex:line-20275" type="sharef:inproceedings" crossref="chi2006">
		<names type="sharef:author">
			<person>
				<givenname>Anand</givenname>
				<surname>Agarawala</surname>
			</person>
			<person>
				<givenname>Ravin</givenname>
				<surname>Balakrishnan</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>We explore making virtual desktops behave in a more physically realistic manner by adding physics simulation and using piling instead of filing as the fundamental organizational structure. Objects can be casually dragged and tossed around, influenced by physical characteristics such as friction and mass, much like we would manipulate lightweight objects in the real world. We present a prototype, called BumpTop, that coherently integrates a variety of interaction and visualization techniques optimized for pen input we have developed to support this new style of desktop organization.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/1124772.1124965</identifier>
		<pages>1283-1292</pages>
		<title type="sharef:primaryTitle">Keepin' it Real: Pushing the Desktop Metaphor with Physics, Piles and the Pen</title>
		<identifier type="sharef:uri" resourceType="application/pdf">http://honeybrown.ca/Pubs/BumpTop.pdf</identifier>
	</reference>
	<reference name="mil06b" src="bibtex:inproceedings" src-info="bibtex:line-20285" type="sharef:inproceedings" crossref="chi2006">
		<names type="sharef:author">
			<person>
				<givenname>David R.</givenname>
				<surname>Millen</surname>
			</person>
			<person>
				<givenname>Jonathan</givenname>
				<surname>Feinberg</surname>
			</person>
			<person>
				<givenname>Bernard</givenname>
				<surname>Kerr</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>We describe a social bookmarking service de-signed for a large enterprise. We discuss design principles addressing online identity, privacy, information discovery (including search and pivot browsing), and service extensibility based on a web-friendly architectural style. In addition we describe the key design features of our implementation. We provide the results of an eight week field trial of this enterprise social bookmarking service, including a description of user activities, based on log file analysis. We share the results of a user survey focused on the benefits of the service. The feedback from the user trial, comprising survey results, log file analysis and informal communications, is quite positive and suggests several promising enhancements to the service. Finally, we discuss potential extension and integration of social bookmarking services with other corporate collaborative applications.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/1124772.1124792</identifier>
		<pages>111-120</pages>
		<title type="sharef:primaryTitle">Dogear: Social bookmarking in the Enterprise</title>
		<field type="bibtex:topic">dogear[1]</field>
	</reference>
	<reference name="chi2006" src="bibtex:proceedings" src-info="bibtex:line-20295" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>Rebecca E.</givenname>
				<surname>Grinter</surname>
			</person>
			<person>
				<givenname>Tom A.</givenname>
				<surname>Rodden</surname>
			</person>
			<person>
				<givenname>Paul M.</givenname>
				<surname>Aoki</surname>
			</person>
			<person>
				<givenname>Edward</givenname>
				<surname>Cutrell</surname>
			</person>
			<person>
				<givenname>Robin</givenname>
				<surname>Jeffries</surname>
			</person>
			<person>
				<givenname>Gary M.</givenname>
				<surname>Olson</surname>
			</person>
		</names>
		<date value="2006-04"/>
		<address type="sharef:placePublished">Montréal, Canada</address>
		<field type="bibtex:index">CHI 2006</field>
		<identifier type="sharef:isbn">1-59593-372-7</identifier>
		<publisher>ACM Press</publisher>
		<title type="sharef:primaryTitle">2006 Conference on Human Factors in Computing Systems (CHI 2006)</title>
		<identifier type="sharef:uri" resourceType="text/html">http://www.informatik.uni-trier.de/~ley/db/conf/chi/chi2006.html</identifier>
	</reference>
	<reference name="ben07" src="bibtex:inproceedings" src-info="bibtex:line-20312" type="sharef:inproceedings" crossref="chi2007">
		<names type="sharef:author">
			<person>
				<givenname>Frank</givenname>
				<surname>Bentley</surname>
			</person>
			<person>
				<givenname>Crysta J.</givenname>
				<surname>Metcalf</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>We present the Motion Presence application, an augmented phone book style application that allows close friends and family to view each other's current motion status ("moving" or "not moving") on their mobile phones. We performed a two week long field trial with 10 participants to observe usage and investigate any privacy concerns that might arise. We found that our participants used the motion information to infer location and activity as well as to plan communication, to help in coordinating in-person get-togethers, and to stay connected to patterns in each others' lives. Participants saw the motion data as mostly confirming their existing thoughts about the locations and activities of others and expressed few privacy concerns. In fact, they frequently asked for more information to be shared to make the application more compelling.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/1240624.1240831</identifier>
		<pages>1361-1370</pages>
		<title type="sharef:primaryTitle">Sharing Motion Information with Close Family and Friends</title>
		<identifier type="sharef:uri" resourceType="application/pdf">http://web.mit.edu/bentley/www/papers/paper724-bentley.pdf</identifier>
	</reference>
	<reference name="lud07" src="bibtex:inproceedings" src-info="bibtex:line-20322" type="sharef:inproceedings" crossref="chi2007">
		<names type="sharef:author">
			<person>
				<givenname>Pamela J.</givenname>
				<surname>Ludford</surname>
			</person>
			<person>
				<givenname>Reid</givenname>
				<surname>Priedhorsky</surname>
			</person>
			<person>
				<givenname>Ken</givenname>
				<surname>Reily</surname>
			</person>
			<person>
				<givenname>Loren G.</givenname>
				<surname>Terveen</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>With new technology, people can share information about everyday places they go; the resulting data helps others find and evaluate places. Recent applications like Dodgeball and Sharescape repurpose everyday place information: users create local place data for personal use, and the systems display it for public use. We explore both the opportunities — new local knowledge, and concerns — privacy risks, raised by this implicit information sharing. We conduct two empirical studies: subjects create place data when using PlaceMail, a location-based reminder system, and elect whether to share it on Sharescape, a community map-building system. We contribute by: (1) showing location-based reminders yield new local knowledge about a variety of places, (2) identifying heuristics people use when deciding what place-related information to share (and their prevalence), (3) detailing how these decision heuristics can inform local knowledge sharing system design, and (4) identifying new uses of shared place information, notably opportunistic errand planning.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/1240624.1240811</identifier>
		<pages>1235-1244</pages>
		<title type="sharef:primaryTitle">Capturing, Sharing, and Using Local Place Information</title>
	</reference>
	<reference name="ame07" src="bibtex:inproceedings" src-info="bibtex:line-20331" type="sharef:inproceedings" crossref="chi2007">
		<names type="sharef:author">
			<person>
				<givenname>Morgan</givenname>
				<surname>Ames</surname>
			</person>
			<person>
				<givenname>Mor</givenname>
				<surname>Naaman</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Why do people tag? Users have mostly avoided annotating media such as photos — both in desktop and mobile environments — despite the many potential uses for annotations, including recall and retrieval. We investigate the incentives for annotation in Flickr, a popular web-based photo-sharing system, and ZoneTag, a cameraphone photo capture and annotation tool that uploads images to Flickr. In Flickr, annotation (as textual tags) serves both personal and social purposes, increasing incentives for tagging and resulting in a relatively high number of annotations. ZoneTag, in turn, makes it easier to tag cameraphone photos that are uploaded to Flickr by allowing annotation and suggesting relevant tags immediately after capture. A qualitative study of ZoneTag/Flickr users exposed various tagging patterns and emerging motivations for photo annotation. We offer a taxonomy of motivations for annotation in this system along two dimensions (sociality and function), and explore the various factors that people consider when tagging their photos. Our findings suggest implications for the design of digital photo organization and sharing applications, as well as other applications that incorporate user-based annotation.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/1240624.1240772</identifier>
		<pages>971-980</pages>
		<title type="sharef:primaryTitle">Why We Tag: Motivations for Annotation in Mobile and Online Media</title>
	</reference>
	<reference name="obe07" src="bibtex:inproceedings" src-info="bibtex:line-20340" type="sharef:inproceedings" crossref="chi2007">
		<names type="sharef:author">
			<person>
				<givenname>Hartmut</givenname>
				<surname>Obendorf</surname>
			</person>
			<person>
				<givenname>Harald</givenname>
				<surname>Weinreich</surname>
			</person>
			<person>
				<givenname>Eelco</givenname>
				<surname>Herder</surname>
			</person>
			<person>
				<givenname>Matthias</givenname>
				<surname>Mayer</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>This paper presents results of an extensive long-term click-stream study of Web browser usage. Focusing on character and challenges of page revisitation, previous findings from seven to thirteen years ago are updated. The term page re-visit had to be differentiated, since the recurrence rate — the key measure for the share of page revisits — turns out to strongly depend on interpretation. We identify different types of revisitation that allow assessing the quality of current user support and developing concepts for new tools. Individual navigation strategies differ dramatically and are strongly influenced by personal habits and type of site visited. Based on user action logs and interviews, we distinguished short-term revisits (backtrack or undo) from medium-term (re-utilize or observe) and long-term revisits (rediscover). We analyze current problems and provide suggestions for improving support for different revisitation types.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/1240624.1240719</identifier>
		<pages>597-606</pages>
		<title type="sharef:primaryTitle">Web Page Revisitation Revisited: Implications of a Long-term Click-stream Study of Browser Usage</title>
	</reference>
	<reference name="riv07" src="bibtex:inproceedings" src-info="bibtex:line-20349" type="sharef:inproceedings" crossref="chi2007">
		<names type="sharef:author">
			<person>
				<givenname>A. W.</givenname>
				<surname>Rivadeneira</surname>
			</person>
			<person>
				<givenname>Daniel M.</givenname>
				<surname>Gruen</surname>
			</person>
			<person>
				<givenname>Michael J.</givenname>
				<surname>Muller</surname>
			</person>
			<person>
				<givenname>David R.</givenname>
				<surname>Millen</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Tagclouds are visual presentations of a set of words, typically a set of "tags" selected by some rationale, in which attributes of the text such as size, weight, or color are used to represent features, such as frequency, of the associated terms. This note describes two studies to evaluate the effectiveness of differently constructed tagclouds for the various tasks they can be used to support, including searching, browsing, impression formation and recognition. Based on these studies, we propose a paradigm for evaluating tagclouds and ultimately guidelines for tagcloud construction.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/1240624.1240775</identifier>
		<pages>995-998</pages>
		<title type="sharef:primaryTitle">Getting our Head in the Clouds: Toward Evaluation Studies of Tagclouds</title>
		<field type="bibtex:topic">dogear[0.9]</field>
	</reference>
	<reference name="tab07" src="bibtex:inproceedings" src-info="bibtex:line-20359" type="sharef:inproceedings" crossref="chi2007">
		<names type="sharef:author">
			<person>
				<givenname>Aurélien</givenname>
				<surname>Tabard</surname>
			</person>
			<person>
				<givenname>Wendy E.</givenname>
				<surname>Mackay</surname>
			</person>
			<person>
				<givenname>Nicolas</givenname>
				<surname>Roussel</surname>
			</person>
			<person>
				<givenname>Catherine</givenname>
				<surname>Letondal</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>PageLinker is a browser extension that allows to contextualise navigation by linking web pages together and to navigate through a network of related web pages without prior planning. The design is based on extensive interviews with biologists, which highlighted their difficulties finding previously visited web pages. They found current browser tools inadequate, resulting in poorly organised bookmarks and rarely used history lists. In a four-week controlled field experiment, PageLinker significantly reduced time, page loads and mouse clicks. By presenting links in context, PageLinker facilitates web page revisitation, is less prone to bookmark overload and is highly robust to change.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/1240624.1240680</identifier>
		<pages>337-346</pages>
		<title type="sharef:primaryTitle">PageLinker: Integrating Contextual Bookmarks within a Browser</title>
	</reference>
	<reference name="chi2007" src="bibtex:proceedings" src-info="bibtex:line-20368" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>Mary Beth</givenname>
				<surname>Rosson</surname>
			</person>
			<person>
				<givenname>David J.</givenname>
				<surname>Gilmore</surname>
			</person>
		</names>
		<date value="2007-04"/>
		<address type="sharef:placePublished">San Jose, California</address>
		<field type="bibtex:index">CHI 2007</field>
		<identifier type="sharef:isbn">978-1-59593-593-9</identifier>
		<publisher>ACM Press</publisher>
		<title type="sharef:primaryTitle">2007 Conference on Human Factors in Computing Systems (CHI 2007)</title>
		<identifier type="sharef:uri" resourceType="text/html">http://www.informatik.uni-trier.de/~ley/db/conf/chi/chi2007.html</identifier>
	</reference>
	<reference name="tsa09" src="bibtex:inproceedings" src-info="bibtex:line-20385" type="sharef:inproceedings" crossref="chi2009">
		<names type="sharef:author">
			<person>
				<givenname>Janice Y.</givenname>
				<surname>Tsai</surname>
			</person>
			<person>
				<givenname>Patrick</givenname>
				<surname>Kelley</surname>
			</person>
			<person>
				<givenname>Paul</givenname>
				<surname>Drielsma</surname>
			</person>
			<person>
				<givenname>Lorrie Faith</givenname>
				<surname>Cranor</surname>
			</person>
			<person>
				<givenname>Jason</givenname>
				<surname>Hong</surname>
			</person>
			<person>
				<givenname>Norman</givenname>
				<surname>Sadeh</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Feedback is viewed as an essential element of ubiquitous computing systems in the HCI literature for helping people manage their privacy. However, the success of online social networks and existing commercial systems for mobile location sharing which do not incorporate feedback would seem to call the importance of feedback into question. We investigated this issue in the context of a mobile location sharing system. Specifically, we report on the findings of a field deployment of Locyoution, a mobile location sharing system. In our study of 56 users, one group was given feedback in the form of a history of location requests, and a second group was given no feedback at all. Our major contribution has been to show that feedback is an important contributing factor towards improving user comfort levels and allaying privacy concerns. Participants' privacy concerns were reduced after using the mobile location sharing system. Additionally,our study suggests that peer opinion and technical savviness contribute most to whether or not participants thought they would continue to use a mobile location technology.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1145/1518701.1519005</identifier>
		<pages>2003-2012</pages>
		<title type="sharef:primaryTitle">Who's Viewed You?: The Impact of Feedback in a Mobile Location-Sharing Application</title>
	</reference>
	<reference name="chi2009" src="bibtex:proceedings" src-info="bibtex:line-20394" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>Dan R.</givenname>
				<surname>Olsen</surname>
			</person>
			<person>
				<givenname>Richard B.</givenname>
				<surname>Arthur</surname>
			</person>
			<person>
				<givenname>Ken</givenname>
				<surname>Hinckley</surname>
			</person>
			<person>
				<givenname>Meredith Ringel</givenname>
				<surname>Morris</surname>
			</person>
			<person>
				<givenname>Scott E.</givenname>
				<surname>Hudson</surname>
			</person>
			<person>
				<givenname>Saul</givenname>
				<surname>Greenberg</surname>
			</person>
		</names>
		<date value="2009-04"/>
		<address type="sharef:placePublished">Boston, Massachusetts</address>
		<field type="bibtex:index">CHI 2009</field>
		<identifier type="sharef:isbn">978-1-60558-246-7</identifier>
		<publisher>ACM Press</publisher>
		<title type="sharef:primaryTitle">2009 Conference on Human Factors in Computing Systems (CHI 2009)</title>
		<identifier type="sharef:uri" resourceType="text/html">http://www.informatik.uni-trier.de/~ley/db/conf/chi/chi2009.html</identifier>
	</reference>
	<reference name="leo93" src="bibtex:inproceedings" src-info="bibtex:line-20411" type="sharef:inproceedings" crossref="bbi93">
		<names type="sharef:author">
			<person>
				<givenname>Helmut</givenname>
				<surname>Leopold</surname>
			</person>
			<person>
				<givenname>Geoff</givenname>
				<surname>Coulson</surname>
			</person>
			<person>
				<givenname>Kwaku</givenname>
				<surname>Frimpong-Ansah</surname>
			</person>
			<person>
				<givenname>David</givenname>
				<surname>Hutchison</surname>
			</person>
			<person>
				<givenname>Nicolaus</givenname>
				<surname>Singer</surname>
			</person>
		</names>
		<field type="bibtex:index">OSI, ODP, ULA, trading, QoS, binding, ODP</field>
		<pages>77-92</pages>
		<title type="sharef:primaryTitle">The Evolving Relationship Between OSI and ODP in the New Communications Environment</title>
	</reference>
	<reference name="gut93b" src="bibtex:inproceedings" src-info="bibtex:line-20419" type="sharef:inproceedings" crossref="bbi93">
		<names type="sharef:author">
			<person>
				<givenname>Thomas</givenname>
				<surname>Gutekunst</surname>
			</person>
			<person>
				<givenname>Bernhard</givenname>
				<surname>Plattner</surname>
			</person>
		</names>
		<field type="bibtex:index">JVTOS, CIO</field>
		<pages>173-191</pages>
		<title type="sharef:primaryTitle">Sharing Multimedia Applications Among Heterogeneous Workstations</title>
	</reference>
	<reference name="bbi93" src="bibtex:proceedings" src-info="bibtex:line-20427" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>Otto</givenname>
				<surname>Spaniol</surname>
			</person>
			<person>
				<givenname>Fiona</givenname>
				<surname>Williams</surname>
			</person>
		</names>
		<date value="1993-06"/>
		<address type="sharef:placePublished">Athens, Greece</address>
		<identifier type="sharef:isbn">0-444-81710-7</identifier>
		<publisher>North-Holland</publisher>
		<title type="sharef:primaryTitle">Broadband Islands '93: Towards Integration</title>
	</reference>
	<reference name="mat94a" src="bibtex:inproceedings" src-info="bibtex:line-20442" type="sharef:inproceedings" crossref="bbi94">
		<names type="sharef: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>
		<pages>167-178</pages>
		<title type="sharef:primaryTitle">A Group Communication Framework</title>
	</reference>
	<reference name="bbi94" src="bibtex:proceedings" src-info="bibtex:line-20449" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>Wulf</givenname>
				<surname>Bauerfeld</surname>
			</person>
			<person>
				<givenname>Otto</givenname>
				<surname>Spaniol</surname>
			</person>
			<person>
				<givenname>Fiona</givenname>
				<surname>Williams</surname>
			</person>
		</names>
		<date value="1994-06"/>
		<address type="sharef:placePublished">Hamburg, Germany</address>
		<identifier type="sharef:isbn">0-444-81905-3</identifier>
		<publisher>North-Holland</publisher>
		<title type="sharef:primaryTitle">Broadband Islands '94: Connecting with the End-User</title>
	</reference>
	<reference name="mat95b" src="bibtex:inproceedings" src-info="bibtex:line-20464" type="sharef:inproceedings" crossref="bbi95">
		<names type="sharef:author">
			<person>
				<givenname>Laurent</givenname>
				<surname>Mathy</surname>
			</person>
		</names>
		<pages>67-75</pages>
		<title type="sharef:primaryTitle">On the Design of a Transport Service to Support Multimedia Applications</title>
	</reference>
	<reference name="bbi95" src="bibtex:proceedings" src-info="bibtex:line-20471" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>Fiona</givenname>
				<surname>Williams</surname>
			</person>
			<person>
				<givenname>H.</givenname>
				<surname>Bräke</surname>
			</person>
			<person>
				<givenname>J.</givenname>
				<surname>Nolan</surname>
			</person>
		</names>
		<date value="1995-09"/>
		<address type="sharef:placePublished">Dublin, Ireland</address>
		<publisher>North-Holland</publisher>
		<title type="sharef:primaryTitle">Broadband Islands '95: Connecting with the End-User</title>
	</reference>
	<reference name="ace94" src="bibtex:inproceedings" src-info="bibtex:line-20485" type="sharef:inproceedings" crossref="ulpaa94">
		<names type="sharef:author">
			<person>
				<givenname>José Jesús</givenname>
				<surname>Acebrón</surname>
			</person>
			<person>
				<givenname>Jaime</givenname>
				<surname>Delgado</surname>
			</person>
		</names>
		<field type="bibtex:index">ODA, DODS, information storage, distributed documents, information search and retrieval, DFR, DTAM, DOAM</field>
		<pages>209-219</pages>
		<title type="sharef:primaryTitle">Design of a Distributed Document System Based on ODA: DODS</title>
	</reference>
	<reference name="del94" src="bibtex:inproceedings" src-info="bibtex:line-20493" type="sharef:inproceedings" crossref="ulpaa94">
		<names type="sharef:author">
			<person>
				<givenname>Jaime</givenname>
				<surname>Delgado</surname>
			</person>
			<person>
				<givenname>Francisco</givenname>
				<surname>Jordan</surname>
			</person>
			<person>
				<givenname>Xavier</givenname>
				<surname>Perramon</surname>
			</person>
		</names>
		<field type="bibtex:index">FODATEC, distributed documents, ODA, ODIF, DTAM</field>
		<pages>221-234</pages>
		<title type="sharef:primaryTitle">FODATEC: An Open Document Manipulation System</title>
	</reference>
	<reference name="sch94" src="bibtex:inproceedings" src-info="bibtex:line-20501" type="sharef:inproceedings" crossref="ulpaa94">
		<names type="sharef:author">
			<person>
				<givenname>Ulrich</givenname>
				<surname>Schäffer</surname>
			</person>
		</names>
		<field type="bibtex:index">MPPS, OSI, group communications</field>
		<pages>237-250</pages>
		<title type="sharef:primaryTitle">MPPS — A Multiparty Presentation Service</title>
	</reference>
	<reference name="lub94b" src="bibtex:inproceedings" src-info="bibtex:line-20509" type="sharef:inproceedings" crossref="ulpaa94">
		<names type="sharef:author">
			<person>
				<givenname>Hannes P.</givenname>
				<surname>Lubich</surname>
			</person>
		</names>
		<field type="bibtex:index">multimedia, shared whiteboard, MultimETH, OSI</field>
		<pages>251-260</pages>
		<title type="sharef:primaryTitle">A Small Conferencing System and Shared Whiteboard as a Testbed for Distributed Multimedia Applications Using OSI Protocols</title>
	</reference>
	<reference name="bur94" src="bibtex:inproceedings" src-info="bibtex:line-20517" type="sharef:inproceedings" crossref="ulpaa94">
		<names type="sharef:author">
			<person>
				<givenname>Christoph A.</givenname>
				<surname>Burkhardt</surname>
			</person>
			<person>
				<givenname>Hannes P.</givenname>
				<surname>Lubich</surname>
			</person>
		</names>
		<field type="bibtex:index">MultimETH, CSCW, audio conferencing</field>
		<pages>261-274</pages>
		<title type="sharef:primaryTitle">Audio Support for Synchronous Cooperative Work</title>
	</reference>
	<reference name="ben94" src="bibtex:inproceedings" src-info="bibtex:line-20525" type="sharef:inproceedings" crossref="ulpaa94">
		<names type="sharef:author">
			<person>
				<givenname>Steven</givenname>
				<surname>Benford</surname>
			</person>
			<person>
				<givenname>Ok-Ki</givenname>
				<surname>Lee</surname>
			</person>
		</names>
		<field type="bibtex:index">naming, group management, CSCW, group communications</field>
		<pages>347-360</pages>
		<title type="sharef:primaryTitle">A Naming Model for Distributed Group Communication</title>
	</reference>
	<reference name="ulpaa94" src="bibtex:proceedings" src-info="bibtex:line-20533" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>Manuel</givenname>
				<surname>Medina</surname>
			</person>
			<person>
				<givenname>Nathaniel S.</givenname>
				<surname>Borenstein</surname>
			</person>
		</names>
		<date value="1994"/>
		<address type="sharef:placePublished">Barcelona, Spain</address>
		<field type="bibtex:index">ULPAA '94</field>
		<title type="sharef:primaryTitle">IFIP International Working Conference on Upper Layer Protocols, Architectures &amp; Applications</title>
	</reference>
	<reference name="mer04" src="bibtex:inproceedings" src-info="bibtex:line-20546" type="sharef:inproceedings" crossref="uixml2004">
		<names type="sharef:author">
			<person>
				<givenname>Roland</givenname>
				<surname>Merrick</surname>
			</person>
			<person>
				<givenname>Brian</givenname>
				<surname>Wood</surname>
			</person>
			<person>
				<givenname>William</givenname>
				<surname>Krebs</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>The ever increasing variety of devices available to users means that it is not economically viable to develop tailored user interfaces for each device. This paper describes an XML Vocabulary, Abstract User Interface Markup Language (AUIML), which has been developed to allow some classes of interactive application to be developed once and adapted to run on a wide variety of device types. The language does not take the lowest common denominator approach while using abstraction to describe the user interface. This allows device dependent adaptation to take place when rendering.</p>
			</richtext>
		</abstract>
		<title type="sharef:primaryTitle">Abstract User Interface Markup Language</title>
		<field type="bibtex:topic">auiml[1]</field>
	</reference>
	<reference name="uixml2004" src="bibtex:proceedings" src-info="bibtex:line-20554" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>Kris</givenname>
				<surname>Luyten</surname>
			</person>
			<person>
				<givenname>Marc</givenname>
				<surname>Abrams</surname>
			</person>
			<person>
				<givenname>Jean</givenname>
				<surname>Vanderdonckt</surname>
			</person>
			<person>
				<givenname>Quentin</givenname>
				<surname>Limbourg</surname>
			</person>
		</names>
		<date value="2004-05"/>
		<address type="sharef:placePublished">Gallipoli, Italy</address>
		<field type="bibtex:index">UIXML 2004</field>
		<title type="sharef:primaryTitle">Workshop on Developing User Interfaces with XML: Advances on User Interface Description Languages</title>
		<identifier type="sharef:uri">http://www.edm.luc.ac.be/uixml2004/</identifier>
	</reference>
	<reference name="ber05" src="bibtex:inproceedings" src-info="bibtex:line-20569" type="sharef:inproceedings" crossref="gvd2005">
		<names type="sharef:author">
			<person>
				<givenname>Sacha</givenname>
				<surname>Berger</surname>
			</person>
			<person>
				<givenname>François</givenname>
				<surname>Bry</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>This article reports on a research project investigating the following two complementary issues: (1) improving how the structure of XML and HTML can be specified, (2) using structure specification (of XML and HTML documents) for static type checking of Web (and Semantic Web) query programs. The first step towards this goal is to provide a schema language like DTD, XML Schema or Relax-NG with better support of graph structured data.</p>
			</richtext>
		</abstract>
		<pages>28-32</pages>
		<title type="sharef:primaryTitle">Towards Static Type Checking of Web Query Language</title>
		<field type="bibtex:topic">r2g2[1]</field>
		<identifier type="sharef:uri">http://www.pms.ifi.lmu.de/publikationen#PMS-FB-2005-12</identifier>
	</reference>
	<reference name="gvd2005" src="bibtex:proceedings" src-info="bibtex:line-20579" type="sharef:proceedings">
		<names type="sharef:editor">
			<person>
				<givenname>Stefan</givenname>
				<surname>Brass</surname>
			</person>
			<person>
				<givenname>Christian</givenname>
				<surname>Goldberg</surname>
			</person>
		</names>
		<date value="2005-05"/>
		<address type="sharef:placePublished">Wörlitz, Germany</address>
		<field type="bibtex:index">GvD 2005</field>
		<title type="sharef:primaryTitle">17th GI-Workshop on the Foundations of Databases</title>
		<identifier type="sharef:uri" resourceType="text/html">http://dbs.informatik.uni-halle.de/GvD2005/tagungsband.html</identifier>
	</reference>
	<reference name="cas01" src="bibtex:inproceedings" src-info="bibtex:line-20594" type="sharef:inproceedings" crossref="xmarkup2001">
		<names type="sharef:author">
			<person>
				<givenname>Paolo</givenname>
				<surname>Casarini</surname>
			</person>
			<person>
				<givenname>Luca</givenname>
				<surname>Padovani</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>The widespread use of Web technologies and, in particular, the ever growing number of applications adopting XML as the standard language for the encoding of any piece of structured information, naturally calls for efficient implementations of DOM, the standard interface to access the internal structure of documents. The DOM level 2 API, which has been conceived as a suitable hierarchy of classes, has its most natural mapping in object-oriented languages such as C++ and Java. This is also testified by the already existing implementations in those languages. However, as of today, most applications are commonly developed in C, because of its standardization, flexibility, efficiency and availability. In this paper we describe the current state of Gdome2, which provides a DOM implementation for the C programming language. The library is meant to become a key module of the Gnome architecture, supplying a range of facilities for an efficient, portable, and easy management of XML documents in the Gnome way. We conclude with a comparison between Gdome2 and Xerces, one of the more advanced and actively developed DOM implementations.</p>
			</richtext>
		</abstract>
		<title type="sharef:primaryTitle">The Gnome DOM Engine</title>
		<field type="bibtex:topic">dom[0.8]</field>
		<identifier type="sharef:uri" resourceType="text/html">http://www.mulberrytech.com/Extreme/Proceedings/html/2001/Casarini01/EML2001Casarini01-toc.html</identifier>
	</reference>
	<reference name="mur01" src="bibtex:inproceedings" src-info="bibtex:line-20603" type="sharef:inproceedings" crossref="xmarkup2001">
		<names type="sharef:author">
			<person>
				<givenname>Makoto</givenname>
				<surname>Murata</surname>
			</person>
			<person>
				<givenname>Dongwon</givenname>
				<surname>Lee</surname>
			</person>
			<person>
				<givenname>Murali</givenname>
				<surname>Mani</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>On the basis of regular tree languages, we present a formal framework for XML schema languages. This framework helps to describe, compare, and implement such schema languages. Our main results are as follows: (1) four classes of tree languages, namely "local", "single-type", "restrained competition" and "regular"; (2) document validation algorithms for these classes; and (3) classification and comparison of schema languages: DTD, XML-Schema, DSD, XDuce, RELAX Core, and TREX.</p>
			</richtext>
		</abstract>
		<title type="sharef:primaryTitle">Taxonomy of XML Schema Languages Using Formal Language Theory</title>
		<field type="bibtex:topic">dtd[0.7] xsd[0.7] dsd2[0.7] xduce[0.7] relax[0.7] trex[0.7]</field>
		<identifier type="sharef:uri" resourceType="text/html">http://www.mulberrytech.com/Extreme/Proceedings/html/2001/Murata01/EML2001Murata01-toc.html</identifier>
	</reference>
	<reference name="xmarkup2001" src="bibtex:proceedings" src-info="bibtex:line-20612" type="sharef:proceedings">
		<date value="2001-08"/>
		<address type="sharef:placePublished">Montréal, Canada</address>
		<field type="bibtex:key">2001 Extreme Markup Languages Conference</field>
		<title type="sharef:primaryTitle">2001 Extreme Markup Languages Conference</title>
		<identifier type="sharef:uri" resourceType="text/html">http://www.mulberrytech.com/Extreme/Proceedings/index.html</identifier>
		<identifier type="sharef:uri">http://www.extrememarkup.com/extreme/2001/</identifier>
	</reference>
	<reference name="pre02" src="bibtex:inproceedings" src-info="bibtex:line-20627" type="sharef:inproceedings" crossref="xmarkup2002">
		<names type="sharef:author">
			<person>
				<givenname>Paul</givenname>
				<surname>Prescod</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>In order to communicate over networks we need standardized data formats and protocols. But how do we move forward toward this goal? One popular debate centers around the best way to define new data formats. XML dominates this area and so the primary question left is how and whether to use schemas and if so, what schema language to use. This paper will address a different question: How will we standardize the protocols used to transport the XML documents? This paper will describe three different strategies and attempt to summarize their strengths and weaknesses from an admittedly partisan point of view.</p>
			</richtext>
		</abstract>
		<title type="sharef:primaryTitle">Roots of the REST/SOAP Debate</title>
		<field type="bibtex:topic">rest[0.8] soap[0.8]</field>
		<identifier type="sharef:uri" resourceType="text/html">http://www.mulberrytech.com/Extreme/Proceedings/html/2002/Prescod01/EML2002Prescod01.html</identifier>
		<identifier type="sharef:uri">http://www.prescod.net/rest/rest_vs_soap_overview/</identifier>
	</reference>
	<reference name="dur02" src="bibtex:inproceedings" src-info="bibtex:line-20637" type="sharef:inproceedings" crossref="xmarkup2002">
		<names type="sharef:author">
			<person>
				<givenname>Patrick</givenname>
				<surname>Durusau</surname>
			</person>
			<person>
				<givenname>Matthew</givenname>
				<surname>Brook O'Donnell</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Recording multiple possible encodings for a text has been treated as a problem of syntax (CONCUR, milestones, stand-off markup, Bottom-Up Virtual Hierarchies, Layered Markup and Annotation Language, MECS/TexMECS, etc.) and as a problem of parsing (Earley's algorithm, active chart parsing, tree-adjoining grammars). While offering various advantages and shortcomings, these efforts fall short of isolating the fundamental difficulty that gives rise to the problem. The simple tree model, which XML enforces, is a symptom and not the cause of this problem. Descriptive markup divides texts into content and markup. Or as previously stated by the authors, "Markup is metadata about #PCDATA." The fundamental problem is that all prior methods treat markup as static trees of metadata about #PCDATA. If that changes to: Trees are assertions about metadata, the fundamental difficulty of representing multiple trees in a single document instance resolves into a processing issue.</p>
			</richtext>
		</abstract>
		<title type="sharef:primaryTitle">Just-In-Time-Trees (JITTs): Next Step in the Evolution of Markup?</title>
		<field type="bibtex:topic">jitt[1]</field>
		<identifier type="sharef:uri" resourceType="text/html">http://www.sbl-site2.org/Extreme2002/JITTs.html</identifier>
	</reference>
	<reference name="ten02b" src="bibtex:inproceedings" src-info="bibtex:line-20646" type="sharef:inproceedings" crossref="xmarkup2002">
		<names type="sharef:author">
			<person>
				<givenname>Jeni</givenname>
				<surname>Tennison</surname>
			</person>
			<person>
				<givenname>Wendell</givenname>
				<surname>Piez</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Representing multiple hierarchies within a single document has always been a problem for XML. To try to address the problems of representing multiple hierarchies and of annotating existing tree structures with type information (as in the PSVI), we have developed a layered data model based on the Core Range Algebra presented at Extreme 2002 by Gavin Nichol. This data model views documents as strings over which span a number of named ranges, each of which can themselves have associated metaranges with their own internal structure. To aid our experimentation with this data model, we developed a markup notation to reflect it, the Layered Markup and Annotation Language (LMNL), and have constructed several prototype applications to facilitate the extraction of single views, as XML structures, from LMNL documents. This paper outlines LMNL and discusses how its development has made us reflect on the nature of XML, schema and query languages.</p>
			</richtext>
		</abstract>
		<title type="sharef:primaryTitle">The Layered Markup and Annotation Language</title>
		<field type="bibtex:topic">lmnl[1]</field>
		<identifier type="sharef:uri" resourceType="text/html">http://xml.coverpages.org/LMNL-Abstract.html</identifier>
	</reference>
	<reference name="xmarkup2002" src="bibtex:proceedings" src-info="bibtex:line-20655" type="sharef:proceedings">
		<date value="2002-08"/>
		<address type="sharef:placePublished">Montréal, Canada</address>
		<field type="bibtex:key">2002 Extreme Markup Languages Conference</field>
		<title type="sharef:primaryTitle">2002 Extreme Markup Languages Conference</title>
		<identifier type="sharef:uri" resourceType="text/html">http://www.mulberrytech.com/Extreme/Proceedings/index.html</identifier>
	</reference>
	<reference name="ten03" src="bibtex:inproceedings" src-info="bibtex:line-20669" type="sharef:inproceedings" crossref="xmarkup2003">
		<names type="sharef:author">
			<person>
				<givenname>Jeni</givenname>
				<surname>Tennison</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Of all the new features in XSLT 2.0, the ones that have caused the most contention — and worry — amongst existing XSLT authors are those involving typing: strong typing, static typing, and validation against schemas. These features have been introduced due to two general requirements: the requirement to align with W3C XML Schema, which entails using XML Schema's type system and validation methods; and the requirement to support analysis of queries prior to their execution and warn authors of potential problems with them. When XSLT authors express their concern about these changes, they are generally assured that, at the end of the day, if they don't want to use the new type-related features that XPath 2.0 brings, they can always ignore them by using processors that are not schema aware and do not carry out static type checking. In this paper, I'll look at the extent to which this assurance is true: to what extent is it possible to ignore the new typing features in XPath 2.0? If they can't be ignored, what are the kinds of changes that XSLT authors will have to get used to? And most importantly, do these changes offer users any real benefits?</p>
			</richtext>
		</abstract>
		<title type="sharef:primaryTitle">Typing in Transformations</title>
		<field type="bibtex:topic">xslt2[0.9]</field>
		<identifier type="sharef:uri" resourceType="text/html">http://www.mulberrytech.com/Extreme/Proceedings/html/2003/Tennison01/EML2003Tennison01-toc.html</identifier>
	</reference>
	<reference name="kim03" src="bibtex:inproceedings" src-info="bibtex:line-20678" type="sharef:inproceedings" crossref="xmarkup2003">
		<names type="sharef:author">
			<person>
				<givenname>W. Eliot</givenname>
				<surname>Kimber</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>This paper describes and explains the XIndirect facility, a W3C Note. The XIndirect Note defines a simple mechanism for representing indirect addresses that can be used with other XML-based linking and addressing facilities, such as XLink and XInclude. XIndirect is motivated primarily by the requirements of XML authoring in which the management of pointers among systems of documents under constant revision cannot be easily satisfied by the direct pointers provided by XLink and XInclude. Indirect addressing is inherently expensive to implement because of both the processing demands of multi-step pointers and the increased system complexity required to do the processing. XLink and XPointer (and by extension, XInclude) explicitly and appropriately avoid indirection in order to provide the simplest possible solution for the delivery of hyperlinked documents, especially in the context of essentially unbounded systems, such as the World Wide Web. XIndirect enables indirect addressing when needed without adding complexity to the existing XML linking and addressing facilities — by defining indirection as a separate, independent facility, processors that only need to support delivery of documents are not required to support indirection simply in order to support XLink or XInclude. Rather, when indirection management is required, developers of XML information management systems can limit the support for indirection to closed systems of controlled scope where indirection is practical to implement. This paper illustrates some of the key use cases that motivate the need for the XIndirect facility, describes the facility itself, and discusses a reference implementation of the XIndirect facility.</p>
			</richtext>
		</abstract>
		<title type="sharef:primaryTitle">Indirect Addressing for XML</title>
		<field type="bibtex:topic">xindirect[0.9]</field>
		<identifier type="sharef:uri" resourceType="text/html">http://www.mulberrytech.com/Extreme/Proceedings/html/2003/Kimber01/EML2003Kimber01-toc.html</identifier>
	</reference>
	<reference name="vit03" src="bibtex:inproceedings" src-info="bibtex:line-20687" type="sharef:inproceedings" crossref="xmarkup2003">
		<names type="sharef:author">
			<person>
				<givenname>Fabio</givenname>
				<surname>Vitali</surname>
			</person>
			<person>
				<givenname>Nicola</givenname>
				<surname>Amorosi</surname>
			</person>
			<person>
				<givenname>Nicola</givenname>
				<surname>Gessa</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>DTDs and XML Schema are important validation languages for XML documents. They lie at opposite ends of a spectrum of validation languages in terms of expressive power and readability. Differently from other proposals for validation languages, DTD++ provides a DTD-like syntax to XML Schema constructs, thereby enriching the ease of use and reading of DTDs with the expressive power of XML Schema. An implementation as a pre-processor of a Schema-validating XML parser aids in ensuring wide support for the language.</p>
			</richtext>
		</abstract>
		<title type="sharef:primaryTitle">Datatype- and Namespace-Aware DTDs: A Minimal Extension</title>
		<field type="bibtex:topic">dtdplusplus[0.9]</field>
		<identifier type="sharef:uri" resourceType="text/html">http://www.mulberrytech.com/Extreme/Proceedings/html/2003/Gessa01/EML2003Gessa01-toc.html</identifier>
	</reference>
	<reference name="xmarkup2003" src="bibtex:proceedings" src-info="bibtex:line-20696" type="sharef:proceedings">
		<date value="2003-08"/>
		<address type="sharef:placePublished">Montréal, Canada</address>
		<field type="bibtex:key">2003 Extreme Markup Languages Conference</field>
		<title type="sharef:primaryTitle">2003 Extreme Markup Languages Conference</title>
		<identifier type="sharef:uri" resourceType="text/html">http://www.mulberrytech.com/Extreme/Proceedings/index.html</identifier>
	</reference>
	<reference name="kle04" src="bibtex:inproceedings" src-info="bibtex:line-20710" type="sharef:inproceedings" crossref="xmarkup2004">
		<names type="sharef:author">
			<person>
				<givenname>Anne</givenname>
				<surname>Brüggemann-Klein</surname>
			</person>
			<person>
				<givenname>Derick</givenname>
				<surname>Wood</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>The XML community generally takes trees and hedges as the model for XML document instances and element content. In contrast, Berstel and Boasson have discussed XML documents in the framework of extended context-free grammar, modeling XML documents as Dyck strings and schemas as balanced grammars. How can these two models be brought closer together? We examine the close relationship between Dyck strings and hedges, observing that trees and hedges are higher level abstractions than are Dyck primes and Dyck strings. We then argue that hedge grammars are effecively identical to balanced grammars and that balanced languages are identical to regular hedge languages, modulo encoding. From the close relationship between Dyck strings and hedges, we obtain a two-phase architecture for the parsing of balanced languages. We propose caterpillar automata with an additional pushdown stack as a new computational model for the second phase; that is, for the validation of XML documents.</p>
			</richtext>
		</abstract>
		<title type="sharef:primaryTitle">Balanced Context-Free Grammars, Hedge Grammars and Pushdown Caterpillar Automata</title>
		<identifier type="sharef:uri" resourceType="text/html">http://www.mulberrytech.com/Extreme/Proceedings/html/2004/Bruggemann-Klein01/EML2004Bruggemann-Klein01-toc.html</identifier>
	</reference>
	<reference name="fuc04" src="bibtex:inproceedings" src-info="bibtex:line-20718" type="sharef:inproceedings" crossref="xmarkup2004">
		<names type="sharef:author">
			<person>
				<givenname>Matthew</givenname>
				<surname>Fuchs</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>The appearance of the element() predicate and the ability to return source tree nodes from templates provides XSLT 2.0 with mechanisms to support extensibility and reuse in ways not available in XSLT 1.0. We present a significant example of these involving both vertical and horizontal changes, where a single stylesheet exploiting these features can be applied to incompatible but similar versions of a schema as well as to derived schemas created through using XSD's inheritance mechanisms.</p>
			</richtext>
		</abstract>
		<title type="sharef:primaryTitle">Achieving Extensibility and Reuse for XSLT 2.0 Stylesheets</title>
		<field type="bibtex:topic">xslt2[0.8]</field>
		<identifier type="sharef:uri" resourceType="text/html">http://www.mulberrytech.com/Extreme/Proceedings/html/2004/Fuchs01/EML2004Fuchs01-toc.html</identifier>
	</reference>
	<reference name="lau04" src="bibtex:inproceedings" src-info="bibtex:line-20727" type="sharef:inproceedings" crossref="xmarkup2004">
		<names type="sharef:author">
			<person>
				<givenname>Simon</givenname>
				<surname>St. Laurent</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>General parsed entities seemed like one of the simplest parts of XML when it first appeared, easy to create and use, and more predictable than their SGML counterparts. In the years since, however, parsed entities have become a malingering reminder that DTDs are not yet dead, continuing to demonstrate periodically that XML hasn't even resolved all of the interoperability issues at the markup level. Entities solved a problem, and then became a problem themselves. The world is still waiting for a solution to the problems that entities create, though many of the solutions proposed (including my own) are either partial or create new problems. Fortunately, years of implementation experience in this area, in both SGML and XML, may provide guidance for ways forward.</p>
			</richtext>
		</abstract>
		<title type="sharef:primaryTitle">General Parsed Entities: Unfinished Business</title>
		<identifier type="sharef:uri" resourceType="text/html">http://www.mulberrytech.com/Extreme/Proceedings/html/2004/StLaurent01/EML2004StLaurent01-toc.html</identifier>
	</reference>
	<reference name="sch04e" src="bibtex:inproceedings" src-info="bibtex:line-20735" type="sharef:inproceedings" crossref="xmarkup2004">
		<names type="sharef:author">
			<person>
				<givenname>Sebastian</givenname>
				<surname>Schaffert</surname>
			</person>
			<person>
				<givenname>François</givenname>
				<surname>Bry</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>This article gives a practical introduction into the language Xcerpt, guided by many examples for illustrating language constructs and usage. Xcerpt is a rule-based, declarative query and transformation language for XML data. In Xcerpt, queries and the (re-)structuring of answer (also called "constructions") are expressed in terms of patterns instead of path navigations (like in XSLT and XQuery). Pattern queries are evaluated against XML documents using a non-standard form of unification (called "simulation unification"). Furthermore, Xcerpt supports so-called rule chaining (with recursion), which makes it suitable even for complex query programs. Due to its foundations in logic programming, Xcerpt can also serve to implement reasoning algorithms for the Semantic Web.</p>
			</richtext>
		</abstract>
		<title type="sharef:primaryTitle">Querying the Web Reconsidered: A Practical Introduction to Xcerpt</title>
		<field type="bibtex:topic">xcerpt[0.9]</field>
		<identifier type="sharef:uri" resourceType="text/html">http://www.mulberrytech.com/Extreme/Proceedings/html/2004/Schaffert01/EML2004Schaffert01-toc.html</identifier>
	</reference>
	<reference name="spe04" src="bibtex:inproceedings" src-info="bibtex:line-20744" type="sharef:inproceedings" crossref="xmarkup2004">
		<names type="sharef:author">
			<person>
				<givenname>C. Michael</givenname>
				<surname>Sperberg-McQueen</surname>
			</person>
			<person>
				<givenname>Eric</givenname>
				<surname>Miller</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>XML vocabularies can be characterized as those designed for the convenience of authors or software developers, called colloquial, and those designed to have a trivial mapping to a non-XML data structure, which we call non-colloquial. Mapping colloquial vocabularies into other formats (e.g., symbolic logic or RDF) is a powerful tool for making colloquial XML tractable. Specifying this mapping is a way of documenting what the elements and attributes are supposed to mean and how they are to be used. If this is done only in English prose, humans can make use of it, but not machines. If machine-readable syntax is used to specify a mapping from the XML vocabulary into some well-known target syntax, the mapping can benefit both humans and machines. Simple examples illustrate how mappings can be defined using XSLT and how they can be attached to the schema defining the XML vocabulary.</p>
			</richtext>
		</abstract>
		<title type="sharef:primaryTitle">On mapping from colloquial XML to RDF using XSLT</title>
		<identifier type="sharef:uri" resourceType="text/html">http://www.mulberrytech.com/Extreme/Proceedings/html/2004/Sperberg-McQueen01/EML2004Sperberg-McQueen01-toc.html</identifier>
	</reference>
	<reference name="xmarkup2004" src="bibtex:proceedings" src-info="bibtex:line-20752" type="sharef:proceedings">
		<date value="2004-08"/>
		<address type="sharef:placePublished">Montréal, Canada</address>
		<field type="bibtex:key">2004 Extreme Markup Languages Conference</field>
		<title type="sharef:primaryTitle">2004 Extreme Markup Languages Conference</title>
		<identifier type="sharef:uri" resourceType="text/html">http://www.mulberrytech.com/Extreme/Proceedings/index.html</identifier>
	</reference>
	<reference name="sch05b" src="bibtex:inproceedings" src-info="bibtex:line-20766" type="sharef:inproceedings" crossref="xmarkup2005">
		<names type="sharef:author">
			<person>
				<givenname>Erich</givenname>
				<surname>Schubert</surname>
			</person>
			<person>
				<givenname>Sebastian</givenname>
				<surname>Schaffert</surname>
			</person>
			<person>
				<givenname>François</givenname>
				<surname>Bry</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Current XML differencing applications usually try to find a minimal sequence of edit operations that transform one XML document to another XML document (the so-called "edit script"). In our conviction, this approach often produces increments that are unintuitive for human readers and do not reflect the actual changes. We therefore propose in this article a different approach trying to maximize the retained structure instead of minimizing the edit sequence. Structure is thereby not limited to the usual tree structure of XML — any kind of structural relations can be considered (like parent-child, ancestor-descendant, sibling, document order). In our opinion, this approach is very flexible and able to adapt to the user's requirements. It produces more readable results while still retaining a reasonably small edit sequence.</p>
			</richtext>
		</abstract>
		<title type="sharef:primaryTitle">Structure-Preserving Difference Search for XML Documents</title>
		<identifier type="sharef:uri" resourceType="text/html">http://www.mulberrytech.com/Extreme/Proceedings/html/2005/Schaffert01/EML2005Schaffert01.html</identifier>
	</reference>
	<reference name="vit05" src="bibtex:inproceedings" src-info="bibtex:line-20774" type="sharef:inproceedings" crossref="xmarkup2005">
		<names type="sharef:author">
			<person>
				<givenname>Fabio</givenname>
				<surname>Vitali</surname>
			</person>
			<person>
				<givenname>Angelo</givenname>
				<surname>Di Iorio</surname>
			</person>
			<person>
				<givenname>Daniele</givenname>
				<surname>Gubellini</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Existing schema languages can lead to overdesign. They offer more choices than are necessary for purely descriptive (as contrasted with prescriptive) situations. A potential solution is to design based on "patterns" from real DTDs. Using three example situations, alternatives, repeatable homogeneous elements, and mixed content models, we derived a group of patterns sufficient to express all required structures in a descriptive environment. To provide a meaningful example, we propose a new instance-based schema language, DTD–, that derives schemas from tagged sample instances according to the patterns. Since there are few patterns, every document can be represented by a simple grammar where grammar rules can be directly inferred from the document, without any ambiguity.</p>
			</richtext>
		</abstract>
		<title type="sharef:primaryTitle">Design Patterns for Descriptive Document Substructures</title>
		<field type="bibtex:topic">dtdminusminus[0.9]</field>
		<identifier type="sharef:uri" resourceType="text/html">http://www.mulberrytech.com/Extreme/Proceedings/html/2005/Vitali01/EML2005Vitali01.html</identifier>
	</reference>
	<reference name="hil05" src="bibtex:inproceedings" src-info="bibtex:line-20783" type="sharef:inproceedings" crossref="xmarkup2005">
		<names type="sharef:author">
			<person>
				<givenname>Mirco</givenname>
				<surname>Hilbert</surname>
			</person>
			<person>
				<givenname>Oliver</givenname>
				<surname>Schonefeld</surname>
			</person>
			<person>
				<givenname>Andreas</givenname>
				<surname>Witt</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>The SGML feature CONCUR allowed for a document to be simultaneously marked up in multiple conflicting hierarchical tagsets but validated and interpreted in one tagset at a time. Alas, CONCUR was rarely implemented, and XML does not address the problem of conflicting hierarchies at all. The MuLaX document syntax is a non-XML syntax that enables multiply-encoded hierarchies by distinguishing different "layers" in the hierarchy by adding a layer ID as a prefix to the element names. The IDs tie all the elements in a single hierarchy together in an "annotation layer". Extraction of a single annotation layer results in a well-formed XML document, and each annotation layer may be associated with an XML schema. The MuLaX processing model works on the nodes of one annotation layer at a time through XPath-like navigation. CONCUR lives!</p>
			</richtext>
		</abstract>
		<title type="sharef:primaryTitle">Making CONCUR Work</title>
		<field type="bibtex:topic">mulax[0.9]</field>
		<identifier type="sharef:uri">http://www.mulberrytech.com/Extreme/Proceedings/html/2005/Witt01/EML2005Witt01.xml</identifier>
	</reference>
	<reference name="gar05" src="bibtex:inproceedings" src-info="bibtex:line-20792" type="sharef:inproceedings" crossref="xmarkup2005">
		<names type="sharef:author">
			<person>
				<givenname>Lars Marius</givenname>
				<surname>Garshol</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>This paper describes a formal model for topic maps called Q, and structurally similar representations of topic maps and RDF in this formal model.</p>
			</richtext>
		</abstract>
		<title type="sharef:primaryTitle">Q: A Model for Topic Maps — Unifying RDF and Topic Maps</title>
		<field type="bibtex:topic">topicmaps[0.7] rdf[0.7]</field>
		<identifier type="sharef:uri" resourceType="text/html">http://www.mulberrytech.com/Extreme/Proceedings/html/2005/Garshol01/EML2005Garshol01.html</identifier>
	</reference>
	<reference name="xmarkup2005" src="bibtex:proceedings" src-info="bibtex:line-20801" type="sharef:proceedings">
		<date value="2005-08"/>
		<address type="sharef:placePublished">Montréal, Canada</address>
		<field type="bibtex:key">2005 Extreme Markup Languages Conference</field>
		<title type="sharef:primaryTitle">2005 Extreme Markup Languages Conference</title>
		<identifier type="sharef:uri" resourceType="text/html">http://www.mulberrytech.com/Extreme/Proceedings/index.html</identifier>
	</reference>
	<reference name="hal06" src="bibtex:inproceedings" src-info="bibtex:line-20815" type="sharef:inproceedings" crossref="xmarkup2006">
		<names type="sharef:author">
			<person>
				<givenname>Harry</givenname>
				<surname>Halpin</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>As XML becomes ubiquitous and mature, the problem of versioning is increasingly significant. While XML itself has a clear versioning scheme through the version attribute in the prolog, XML-based languages such as Atom do not have a standardized versioning mechanism. We propose namespace documents as the logical solution. It could be claimed that such an approach is not needed by current markup practice in XML. However, as shown by the recent confusion the introduction of the xml:id name caused, at least seems some clarification of the gap between what W3C Recommendations actually define about namespaces and what many people think they define (as well as W3C good practice) is in order. Once we understand namespaces, XMLVS shows that the namespace document is both an effective and practical solution for maintaining XML languages. The XML-based language XMLVS (XML Versioning System) makes the maintaining, documenting, and versioning of XML languages easier by automatically producing best-practice human and machine-readable namespace documents for XML languages.</p>
			</richtext>
		</abstract>
		<title type="sharef:primaryTitle">XMLVS: Using Namespace Documents for XML Versioning</title>
		<field type="bibtex:topic">xmlvs[0.9]</field>
		<identifier type="sharef:uri" resourceType="text/html">http://www.ibiblio.org/hhalpin/homepage/notes/xvspaper.html</identifier>
	</reference>
	<reference name="spe06" src="bibtex:inproceedings" src-info="bibtex:line-20824" type="sharef:inproceedings" crossref="xmarkup2006">
		<names type="sharef:author">
			<person>
				<givenname>C. Michael</givenname>
				<surname>Sperberg-McQueen</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Recent work on markup has emphasized the importance of overlapping structures, but little progress has been made toward validation of such structures: the state of the art in validation of overlap remains where it was in 1986 with the CONCUR feature of SGML. Like CONCUR, rabbit/duck grammars manage validation by means of several context-free grammars, but rabbit/duck grammars offer some improvements over CONCUR: within a document grammar written for one hierarchical subset of the markup vocabulary, the start- and end-tags of other hierarchies may be made visible; rabbit/duck grammars thus make it possible to constrain the interactions of different hierarchies in ways not possible with CONCUR. Rabbit/duck grammars also provide a more principled account of self-overlap (i.e. overlap of two elements with the same generic identifier) than CONCUR. Documents can be validated against rabbit/duck grammars either by validating individually against each grammar or by a single pass through the document which validates against all grammars simultaneously. An implementation of this single-pass approach using Brzozowski derivatives is sketched out.</p>
			</richtext>
		</abstract>
		<title type="sharef:primaryTitle">Rabbit/Duck Grammars: A Validation Method for Overlapping Structures</title>
		<identifier type="sharef:uri" resourceType="text/html">http://www.idealliance.org/papers/extreme/proceedings/html/2006/SperbergMcQueen01/EML2006SperbergMcQueen01.html</identifier>
	</reference>
	<reference name="mar06b" src="bibtex:inproceedings" src-info="bibtex:line-20832" type="sharef:inproceedings" crossref="xmarkup2006">
		<names type="sharef:author">
			<person>
				<givenname>Yves</givenname>
				<surname>Marcoux</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Writing valid XML can be viewed as a collaborative process in which (roughly speaking) the modeler supplies the structure (markup), and the author the contents. When an information management chain includes document creation by a human, failure to mobilize and properly support the author in his task may result in errors or loss of valuable information. In this paper, we first argue that the usual pragmatical approaches to specifying the semantics of XML models do not allow authoring environments to easily provide sufficient semantic support to authors, whereas syntactic support is profusely available. Then, we sketch a semantic framework (provisionally called intertextual semantics), which we think could allow modelers to specify the semantics of their models in a form that can be turned into semantic support to authors in authoring environments. We discuss the pros and cons of the proposed framework, as well as avenues for further work.</p>
			</richtext>
		</abstract>
		<title type="sharef:primaryTitle">A natural-language approach to modeling: Why is some XML so difficult to write?</title>
		<identifier type="sharef:uri" resourceType="text/html">http://www.idealliance.org/papers/extreme/proceedings/html/2006/Marcoux01/EML2006Marcoux01.html</identifier>
		<identifier type="sharef:uri" resourceType="application/pdf">http://www.idealliance.org/papers/extreme/proceedings/xslfo-pdf/2006/marcoux01/eml2006marcoux01.pdf</identifier>
	</reference>
	<reference name="xmarkup2006" src="bibtex:proceedings" src-info="bibtex:line-20841" type="sharef:proceedings">
		<date value="2006-08"/>
		<address type="sharef:placePublished">Montréal, Canada</address>
		<field type="bibtex:key">2006 Extreme Markup Languages Conference</field>
		<title type="sharef:primaryTitle">2006 Extreme Markup Languages Conference</title>
		<identifier type="sharef:uri" resourceType="text/html">http://www.mulberrytech.com/Extreme/Proceedings/index.html</identifier>
	</reference>
	<reference name="wil95" src="bibtex:inproceedings" src-info="bibtex:line-20855" type="sharef:inproceedings" crossref="ulpaa95">
		<names type="sharef:author">
			<person>
				<givenname>Erik</givenname>
				<surname>Wilde</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>In this paper, an architecture for communication support for collaborative applications is described. The motivation for the design of this architecture is the observation that generic support for group communications is an area which received not much attention until now. The design is based on two components, a Group Management System (GMS) and Group Communication Support (GCS). The GMS is responsible for managing the name space of the support platform. Users and groups are the two entities of the name space, and two different relationships between them (membership and manager) can be established. This way it is possible to reflect the structure of collaborative workers inside the GMS. The GCS component is responsible for establishing connections between collaborative applications using the GMS/GCS and for hiding the details of the multicast transport infrastructure from the application. It is possible to bind users and groups to specific applications and multicast transport services. This way any group can be used by different applications using different transport services. The main advantages of GMS/GCS are reduced implementation costs, a shared name space of users and groups, and a simple interface to different multicast transport services.</p>
			</richtext>
		</abstract>
		<title type="sharef:primaryTitle">Group Management and Communication Support for Collaborative Applications</title>
		<identifier type="sharef:uri">http://dret.net/netdret/publications#wil95</identifier>
	</reference>
	<reference name="ulpaa95" src="bibtex:proceedings" src-info="bibtex:line-20863" type="sharef:proceedings">
		<date value="1995-12"/>
		<address type="sharef:placePublished">Sydney, Australia</address>
		<field type="bibtex:index">ULPAA '95</field>
		<field type="bibtex:key">IFIP International Working Conference on Upper Layer Protocols, Architectures &amp; Applications</field>
		<title type="sharef:primaryTitle">IFIP International Working Conference on Upper Layer Protocols, Architectures &amp; Applications</title>
	</reference>
	<reference name="ban91" src="bibtex:incollection" src-info="bibtex:line-20879" type="sharef:incollection" crossref="bow91">
		<names type="sharef:author">
			<person>
				<givenname>Liam J.</givenname>
				<surname>Bannon</surname>
			</person>
			<person>
				<givenname>Kjeld</givenname>
				<surname>Schmidt</surname>
			</person>
		</names>
		<pages>3-17</pages>
		<title type="sharef:primaryTitle">CSCW: Four Characters in Search of a Context</title>
		<field type="bibtex:topic">cscw[0.8]</field>
	</reference>
	<reference name="bon91" src="bibtex:incollection" src-info="bibtex:line-20887" type="sharef:incollection" crossref="bow91">
		<names type="sharef:author">
			<person>
				<givenname>A.</givenname>
				<surname>Bonfiglio</surname>
			</person>
			<person>
				<givenname>G.</givenname>
				<surname>Malatesta</surname>
			</person>
			<person>
				<givenname>Francesco</givenname>
				<surname>Tisato</surname>
			</person>
		</names>
		<field type="bibtex:index">Conference Toolkit</field>
		<pages>63-77</pages>
		<title type="sharef:primaryTitle">Conference Toolkit: A Framework for Real-Time Conferencing</title>
	</reference>
	<reference name="hah91" src="bibtex:incollection" src-info="bibtex:line-20895" type="sharef:incollection" crossref="bow91">
		<names type="sharef:author">
			<person>
				<givenname>Udo</givenname>
				<surname>Hahn</surname>
			</person>
			<person>
				<givenname>Matthias</givenname>
				<surname>Jarke</surname>
			</person>
			<person>
				<givenname>Stefan</givenname>
				<surname>Ehrer</surname>
			</person>
			<person>
				<givenname>Klaus</givenname>
				<surname>Kreplin</surname>
			</person>
		</names>
		<field type="bibtex:index">CoAUTHOR, collaborative editing</field>
		<pages>79-100</pages>
		<title type="sharef:primaryTitle">CoAUTHOR — A Hypermedia Group Authoring Environment</title>
	</reference>
	<reference name="dol91" src="bibtex:incollection" src-info="bibtex:line-20903" type="sharef:incollection" crossref="bow91">
		<names type="sharef:author">
			<person>
				<givenname>J.</givenname>
				<surname>Dollimore</surname>
			</person>
			<person>
				<givenname>S.</givenname>
				<surname>Wilbur</surname>
			</person>
		</names>
		<field type="bibtex:index">COSMOS</field>
		<pages>173-181</pages>
		<title type="sharef:primaryTitle">Experiences in Building Configurable CSCW Applications</title>
	</reference>
	<reference name="rob91b" src="bibtex:incollection" src-info="bibtex:line-20911" type="sharef:incollection" crossref="bow91">
		<names type="sharef:author">
			<person>
				<givenname>Mike</givenname>
				<surname>Robinson</surname>
			</person>
		</names>
		<pages>235-248</pages>
		<title type="sharef:primaryTitle">Pay Bargaining in a Shared Information Space</title>
	</reference>
	<reference name="pri91" src="bibtex:incollection" src-info="bibtex:line-20918" type="sharef:incollection" crossref="bow91">
		<names type="sharef:author">
			<person>
				<givenname>Wolfgang</givenname>
				<surname>Prinz</surname>
			</person>
			<person>
				<givenname>Paola</givenname>
				<surname>Pennelli</surname>
			</person>
		</names>
		<pages>267-283</pages>
		<title type="sharef:primaryTitle">Relevance of the X.500 Directory to CSCW Applications</title>
	</reference>
	<reference name="bow91" src="bibtex:book" src-info="bibtex:line-20925" type="sharef:book">
		<names type="sharef:editor">
			<person>
				<givenname>John M.</givenname>
				<surname>Bowers</surname>
			</person>
			<person>
				<givenname>Steven D.</givenname>
				<surname>Benford</surname>
			</person>
		</names>
		<date value="1991"/>
		<address type="sharef:placePublished">Amsterdam, Netherlands</address>
		<identifier type="sharef:isbn">0-444-88811-X</identifier>
		<publisher>North-Holland</publisher>
		<title type="sharef:seriesTitle">Human Factors in Information Technology</title>
		<title type="sharef:primaryTitle">Studies in Computer Supported Cooperative Work</title>
		<volume>8</volume>
	</reference>
	<reference name="gui11a" src="bibtex:incollection" src-info="bibtex:line-20941" type="sharef:incollection" crossref="aiot2011">
		<names type="sharef:author">
			<person>
				<givenname>Dominique</givenname>
				<surname>Guinard</surname>
			</person>
			<person>
				<givenname>Vlad</givenname>
				<surname>Trifa</surname>
			</person>
			<person>
				<givenname>Friedemann</givenname>
				<surname>Mattern</surname>
			</person>
			<person>
				<givenname>Erik</givenname>
				<surname>Wilde</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Creating networks of "smart things" found in the physical world (e.g., with RFID, wireless sensor and actuator networks, embedded devices) on a large scale has become the goal of a variety of recent research activities. Rather than exposing real-world data and functionality through vertical system designs, we propose to make them an integral part of the Web. As a result, smart things become easier to build upon. In such an architecture, popular Web technologies (e.g., HTML, JavaScript, Ajax, PHP, Ruby) can be used to build applications involving smart things, and users can leverage well-known Web mechanisms (e.g., browsing, searching, bookmarking, caching, linking) to interact with and share these devices. In this chapter, we describe the Web of Things (WoT) architecture and best practices based on the RESTful principles that have already contributed to the popular success, scalability, and evolvability of the Web. We discuss several prototypes using these principles, which connect environmental sensor nodes, energy monitoring systems, and RFID-tagged objects to the Web. We also show how Web-enabled smart things can be used in lightweight ad-hoc applications, called "physical mashups", and discuss some of the remaining challenges towards the global World Wide Web of Things.</p>
			</richtext>
		</abstract>
		<pages>97-129</pages>
		<title type="sharef:primaryTitle">From the Internet of Things to the Web of Things: Resource-Oriented Architecture and Best Practices</title>
		<identifier type="sharef:uri">http://dret.net/netdret/publications#gui11a</identifier>
		<identifier type="sharef:uri">https://springerlink3.metapress.com/content/p314x13322qnw276/resource-secured/?target=fulltext.pdf&amp;sid=xvp14ka21jb0nl55yuhw0uud&amp;sh=www.springerlink.com</identifier>
	</reference>
	<reference name="aiot2011" src="bibtex:book" src-info="bibtex:line-20951" type="sharef:book">
		<names type="sharef:editor">
			<person>
				<givenname>Dieter</givenname>
				<surname>Uckelmann</surname>
			</person>
			<person>
				<givenname>Mark</givenname>
				<surname>Harrison</surname>
			</person>
			<person>
				<givenname>Florian</givenname>
				<surname>Michahelles</surname>
			</person>
		</names>
		<date value="2011-05"/>
		<abstract>
			<richtext>
				<p>Many of the initial developments towards the Internet of Things have focused on the combination of Auto-ID and networked infrastructures in business-to-business logistics and product lifecycle applications. However, the Internet of Things is more than a business tool for managing business processes more efficiently and more effectively — it will also enable a more convenient way of life. Since the term "Internet of Things" first came to attention when the Auto-ID Center launched their initial vision for the EPC network for automatically identifying and tracing the flow of goods within supply-chains, increasing numbers of researchers and practitioners have further developed this vision. The authors in this book provide a research perspective on current and future developments in the Internet of Things. The different chapters cover a broad range of topics from system design aspects and core architectural approaches to end-user participation, business perspectives and applications.</p>
			</richtext>
		</abstract>
		<address type="sharef:placePublished">Heidelberg, Germany</address>
		<identifier type="sharef:doi">10.1007/978-3-642-19157-2_5</identifier>
		<identifier type="sharef:isbn">978-3-642-19156-5</identifier>
		<publisher>Springer-Verlag</publisher>
		<title type="sharef:primaryTitle">Architecting the Internet of Things</title>
		<identifier type="sharef:uri">http://www.springer.com/engineering/production+eng/book/978-3-642-19156-5</identifier>
	</reference>
	<reference name="rest2011" src="bibtex:book" src-info="bibtex:line-20969" type="sharef:book">
		<names type="sharef:editor">
			<person>
				<givenname>Erik</givenname>
				<surname>Wilde</surname>
			</person>
			<person>
				<givenname>Cesare</givenname>
				<surname>Pautasso</surname>
			</person>
		</names>
		<date value="2011"/>
		<address type="sharef:placePublished">Heidelberg, Germany</address>
		<identifier type="sharef:isbn">978-1-4419-8302-2</identifier>
		<publisher>Springer-Verlag</publisher>
		<title type="sharef:primaryTitle">REST: From Research to Practice</title>
		<identifier type="sharef:uri">http://ws-rest.org/book/</identifier>
		<identifier type="sharef:uri">http://www.springer.com/engineering/signals/book/978-1-4419-8302-2</identifier>
	</reference>
	<reference name="kof09" src="bibtex:incollection" src-info="bibtex:line-20985" type="sharef:incollection" crossref="weaving2009">
		<names type="sharef:author">
			<person>
				<givenname>Martin</givenname>
				<surname>Kofahl</surname>
			</person>
			<person>
				<givenname>Erik</givenname>
				<surname>Wilde</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>The concept of location has become very popular in many applications on the Web, in particular for those which aim at connecting the real world with resources on the Web. However, the Web as it is today has no overall location concept, which means that applications have to introduce their own location concepts and have done so in incompatible ways. On the other hand, there are a number of interfaces and techniques that make location information available to networked devices. By turning the Web into a location-aware Web location-oriented applications get better support for their location concepts on the Web, and the Web becomes an information system where location-related information can be more easily shared across different applications and application areas. This chapter describes a location concept for the Web supporting different location types and its embedding into some of the Web's core technologies.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:doi">10.1007/978-3-642-00570-1_8</identifier>
		<pages>147-168</pages>
		<title type="sharef:primaryTitle">Location Concepts for the Web</title>
		<identifier type="sharef:uri">http://www.springerlink.com/content/ph72768077428knt</identifier>
		<identifier type="sharef:uri">http://dret.net/netdret/publications#kof09</identifier>
	</reference>
	<reference name="weaving2009" src="bibtex:book" src-info="bibtex:line-20996" type="sharef:book">
		<names type="sharef:editor">
			<person>
				<givenname>Irwin</givenname>
				<surname>King</surname>
			</person>
			<person>
				<givenname>Ricardo</givenname>
				<surname>Baeza-Yates</surname>
			</person>
		</names>
		<date value="2009-08"/>
		<address type="sharef:placePublished">Heidelberg, Germany</address>
		<identifier type="sharef:doi">10.1007/978-3-642-00570-1</identifier>
		<identifier type="sharef:isbn">978-3-642-00570-1</identifier>
		<publisher>Springer-Verlag</publisher>
		<title type="sharef:primaryTitle">Weaving Services and People on the World Wide Web</title>
		<identifier type="sharef:uri">http://www.springerlink.com/content/978-3-642-00569-5</identifier>
	</reference>
	<reference name="her06" src="bibtex:incollection" src-info="bibtex:line-21013" type="sharef:incollection" crossref="tre06">
		<names type="sharef:author">
			<person>
				<givenname>Susan C.</givenname>
				<surname>Herring</surname>
			</person>
			<person>
				<givenname>Lois Ann</givenname>
				<surname>Scheidt</surname>
			</person>
			<person>
				<givenname>Inna</givenname>
				<surname>Kouper</surname>
			</person>
			<person>
				<givenname>Elijah</givenname>
				<surname>Wright</surname>
			</person>
		</names>
		<pages>3-20</pages>
		<title type="sharef:primaryTitle">A Longitudinal Content Analysis of Weblogs: 2003-2004</title>
	</reference>
	<reference name="tre06" src="bibtex:book" src-info="bibtex:line-21020" type="sharef:book">
		<names type="sharef:editor">
			<person>
				<givenname>Mark</givenname>
				<surname>Tremayne</surname>
			</person>
		</names>
		<date value="2006-11"/>
		<address type="sharef:placePublished">London, UK</address>
		<identifier type="sharef:isbn">0415979404</identifier>
		<publisher>Routledge</publisher>
		<title type="sharef:primaryTitle">Blogging, Citizenship and the Future of Media</title>
	</reference>
	<reference name="fla08" src="bibtex:incollection" src-info="bibtex:line-21035" type="sharef:incollection" crossref="hov08">
		<names type="sharef:author">
			<person>
				<givenname>Mary</givenname>
				<surname>Flanagan</surname>
			</person>
			<person>
				<givenname>Daniel C.</givenname>
				<surname>Howe</surname>
			</person>
			<person>
				<givenname>Helen</givenname>
				<surname>Nissenbaum</surname>
			</person>
		</names>
		<section type="sharef:chapter">16</section>
		<pages>322-353</pages>
		<title type="sharef:primaryTitle">Embodying Values in Technology: Theory and Practice</title>
	</reference>
	<reference name="hov08" src="bibtex:book" src-info="bibtex:line-21043" type="sharef:book">
		<names type="sharef:editor">
			<person>
				<givenname>Jeroen</givenname>
				<surname link="van den">Hoven</surname>
			</person>
			<person>
				<givenname>John</givenname>
				<surname>Weckert</surname>
			</person>
		</names>
		<date value="2008-03"/>
		<identifier type="sharef:isbn">0521855497</identifier>
		<publisher>Cambridge University Press</publisher>
		<title type="sharef:primaryTitle">Information Technology and Moral Philosophy</title>
	</reference>
	<reference name="bar04" src="bibtex:incollection" src-info="bibtex:line-21057" type="sharef:incollection" crossref="arist04">
		<names type="sharef:author">
			<person>
				<givenname>Judit</givenname>
				<surname>Bar-Ilan</surname>
			</person>
		</names>
		<pages>231-288</pages>
		<title type="sharef:primaryTitle">The Use of Web Search Engines in Information Science Research</title>
	</reference>
	<reference name="arist04" src="bibtex:book" src-info="bibtex:line-21064" type="sharef:book">
		<names type="sharef:editor">
			<person>
				<givenname>Blaise</givenname>
				<surname>Cronin</surname>
			</person>
		</names>
		<date value="2004"/>
		<address type="sharef:placePublished">Medford, New Jersey</address>
		<identifier type="sharef:isbn">1573871850</identifier>
		<publisher>Information Today, Inc.</publisher>
		<title type="sharef:primaryTitle">Annual Review of Information Science and Technology</title>
		<identifier type="sharef:uri" resourceType="text/html">http://www.asis.org/Publications/ARIST/vol38.html</identifier>
		<volume>38</volume>
	</reference>
	<reference name="sch01" src="bibtex:incollection" src-info="bibtex:line-21080" type="sharef:incollection" crossref="imkbxii">
		<names type="sharef:author">
			<person>
				<givenname>Klaus-Dieter</givenname>
				<surname>Schewe</surname>
			</person>
		</names>
		<pages>185-202</pages>
		<title type="sharef:primaryTitle">UML: A Modern Dinosaur? A Critical Analysis of the Unified Modelling Language</title>
		<field type="bibtex:topic">uml[0.7]</field>
		<identifier type="sharef:uri" resourceType="application/postscript">http://infosys.massey.ac.nz/~kdschewe/pub/articles/EJC00.ps</identifier>
	</reference>
	<reference name="imkbxii" src="bibtex:book" src-info="bibtex:line-21089" type="sharef:book">
		<names type="sharef:editor">
			<person>
				<givenname>Hannu</givenname>
				<surname>Jaakkola</surname>
			</person>
			<person>
				<givenname>Hannu</givenname>
				<surname>Kangassalo</surname>
			</person>
			<person>
				<givenname>Eiji</givenname>
				<surname>Kawaguchi</surname>
			</person>
		</names>
		<date value="2001"/>
		<address type="sharef:placePublished">Medford, New Jersey</address>
		<identifier type="sharef:isbn">1-58603-163-5</identifier>
		<publisher>IOS Press</publisher>
		<title type="sharef:seriesTitle">Frontiers in Artificial Intelligence and Applications</title>
		<title type="sharef:primaryTitle">Information Modelling and Knowledge Bases XII</title>
		<identifier type="sharef:uri">http://www.iospress.nl/loadtop/load.php?isbn=1586031635</identifier>
		<identifier type="sharef:uri" resourceType="text/html">http://www.informatik.uni-trier.de/~ley/db/conf/ejc/ejc2000.html</identifier>
		<volume>67</volume>
	</reference>
	<reference name="ols93" src="bibtex:incollection" src-info="bibtex:line-21107" type="sharef:incollection" crossref="bas93">
		<names type="sharef:author">
			<person>
				<givenname>Gary M.</givenname>
				<surname>Olson</surname>
			</person>
			<person>
				<givenname>Lola J.</givenname>
				<surname>McGuffin</surname>
			</person>
			<person>
				<givenname>Eiji</givenname>
				<surname>Kuwana</surname>
			</person>
			<person>
				<givenname>Judith S.</givenname>
				<surname>Olson</surname>
			</person>
		</names>
		<pages>129-148</pages>
		<title type="sharef:primaryTitle">Designing Software for a Group's Needs: A Functional Analysis of Synchronous Groupware</title>
	</reference>
	<reference name="dew93" src="bibtex:incollection" src-info="bibtex:line-21114" type="sharef:incollection" crossref="bas93">
		<names type="sharef:author">
			<person>
				<givenname>Prasun</givenname>
				<surname>Dewan</surname>
			</person>
		</names>
		<pages>149-174</pages>
		<title type="sharef:primaryTitle">Tools for Implementing Multiuser User Interfaces</title>
	</reference>
	<reference name="bas93" src="bibtex:book" src-info="bibtex:line-21121" type="sharef:book">
		<names type="sharef:editor">
			<person>
				<givenname>Len</givenname>
				<surname>Bass</surname>
			</person>
			<person>
				<givenname>Prasun</givenname>
				<surname>Dewan</surname>
			</person>
		</names>
		<date value="1993"/>
		<address type="sharef:placePublished">Chichester, England</address>
		<identifier type="sharef:isbn">0471937843</identifier>
		<publisher>John Wiley &amp; Sons</publisher>
		<title type="sharef:seriesTitle">Trends in Software</title>
		<title type="sharef:primaryTitle">User Interface Software</title>
		<volume>1</volume>
	</reference>
	<reference name="wil03o" src="bibtex:incollection" src-info="bibtex:line-21137" type="sharef:incollection" crossref="phic">
		<names type="sharef:author">
			<person>
				<givenname>Erik</givenname>
				<surname>Wilde</surname>
			</person>
		</names>
		<section type="sharef:chapter">23</section>
		<pages>23-1-23-18</pages>
		<title type="sharef:primaryTitle">XML Core Technologies</title>
		<field type="bibtex:topic">xml[0.7] xmlns[0.7] xmlinfoset[0.7] dtd[0.7] xsd[0.7] relaxng[0.7] dsdl[0.7] xpath1[0.7]</field>
		<identifier type="sharef:uri">http://dret.net/netdret/publications#wil03o</identifier>
	</reference>
	<reference name="wil03d" src="bibtex:incollection" src-info="bibtex:line-21147" type="sharef:incollection" crossref="phic">
		<names type="sharef:author">
			<person>
				<givenname>Erik</givenname>
				<surname>Wilde</surname>
			</person>
		</names>
		<section type="sharef:chapter">24</section>
		<pages>24-1-24-10</pages>
		<title type="sharef:primaryTitle">Advanced XML Technologies</title>
		<field type="bibtex:topic">css[0.7] xsl[0.7] xslt1[0.7] dom[0.7] sax[0.7] xquery[0.7]</field>
		<identifier type="sharef:uri">http://dret.net/netdret/publications#wil03d</identifier>
	</reference>
	<reference name="sch03b" src="bibtex:incollection" src-info="bibtex:line-21157" type="sharef:incollection" crossref="phic">
		<names type="sharef:author">
			<person>
				<givenname>Jacqueline</givenname>
				<surname>Schwerzmann</surname>
			</person>
		</names>
		<section type="sharef:chapter">57</section>
		<pages>drm[0.8]</pages>
		<title type="sharef:primaryTitle">Intellectual Property, Liability, and Contract</title>
	</reference>
	<reference name="phic" src="bibtex:book" src-info="bibtex:line-21165" type="sharef:book">
		<names type="sharef:editor">
			<person>
				<givenname>Munindar P.</givenname>
				<surname>Singh</surname>
			</person>
		</names>
		<date value="2004-09"/>
		<abstract>
			<richtext>
				<p>The Practical Handbook of Internet Computing analyzes a broad array of technologies and concerns related to the Internet, including corporate intranets. Fresh and insightful articles by recognized experts address the key challenges facing Internet users, designers, integrators, and policymakers. In addition to discussing major applications, it also covers the architectures, enabling technologies, software utilities, and engineering techniques that are necessary to conduct distributed computing and take advantage of Web-based services.The Handbook provides practical advice based upon experience, standards, and theory. It examines all aspects of Internet computing in wide-area and enterprise settings, ranging from innovative applications to systems and utilities, enabling technologies, and engineering and management. Content includes articles that explore the components that make Internet computing work, including storage, servers, and other systems and utilities. Additional articles examine the technologies and structures that support the Internet, such as directory services, agents, and policies. The volume also discusses the multidimensional aspects of Internet applications, including mobility, collaboration, and pervasive computing. It concludes with an examination of the Internet as a holistic entity, with considerations of privacy and law combined with technical content.</p>
			</richtext>
		</abstract>
		<address type="sharef:placePublished">Boca Raton, Florida</address>
		<identifier type="sharef:isbn">1584883812</identifier>
		<publisher>CRC Press</publisher>
		<title type="sharef:primaryTitle">The Practical Handbook of Internet Computing</title>
		<identifier type="sharef:uri">http://www.crcpress.com/shopping_cart/products/product_detail.asp?sku=C3812&amp;parent_id=&amp;pc=</identifier>
	</reference>
	<reference name="wil07c" src="bibtex:incollection" src-info="bibtex:line-21182" type="sharef:incollection" crossref="metalogue">
		<names type="sharef:author">
			<person>
				<givenname>Erik</givenname>
				<surname>Wilde</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Das Ziel des ShaRef (Shared References)-Projektes ist, einen Dienst zur Verfügung zu stellen, mit dessen Hilfe Referenzinformationen (normalerweise Referenzen auf bibliographische Ressourcen wie Bücher oder Artikel in Fachzeitschriften) verwaltet und gemeinsam genutzt werden können. Ausgangspunkt des Projektes war die Beobachtung, dass der Umgang mit Referenzinformationen eine Tätigkeit ist, die in allen Disziplinen wissenschaftlichen Arbeitens notwendig ist, und dass diese Informationen oftmals in verschiedenen Gruppen gemeinsam genutzt werden. ShaRef ist als Web-basierter Dienst aufgebaut, der als Komponente in die ICT-Landschaft einer Hochschule integriert werden kann. Die Konzeption von ShaRef sieht vor, dass Anbindungen an andere Komponenten oder Applikationen einfach vorgenommen werden können. Dies wird dadurch erreicht, dass über XML ein offenes Datenmodell unterstützt wird, und dass der Aufwand zur Implementierung und Integration neuer Schnittstellen so gering wie möglich gehalten wird. ShaRef wird momentan als produktiver Dienst aufgebaut und wird als Komponente in die ICT-Landschaft der ETH Zürich integriert werden.</p>
			</richtext>
		</abstract>
		<section type="sharef:chapter">3.3</section>
		<pages>285-298</pages>
		<title type="sharef:primaryTitle">ShaRef: Bibliographien als Wissensspeicher</title>
		<field type="bibtex:topic">sharef[1]</field>
		<identifier type="sharef:uri">http://dret.net/netdret/publications#wil07c</identifier>
	</reference>
	<reference name="metalogue" src="bibtex:book" src-info="bibtex:line-21193" type="sharef:book">
		<names type="sharef:editor">
			<person>
				<givenname>Verena</givenname>
				<surname>Friedrich</surname>
			</person>
			<person>
				<givenname>Christoph</givenname>
				<surname>Clases</surname>
			</person>
			<person>
				<givenname>Theo</givenname>
				<surname>Wehner</surname>
			</person>
		</names>
		<date value="2007-03"/>
		<abstract>
			<richtext>
				<p>Seit etwa Mitte der 1990er Jahre wurden im Hochschulkontext eine Vielfalt von Programminitiativen mit dem Ziel lanciert, den Einsatz und die Nutzung von Informations- und Kommunikationstechnologien (IKT) in unterschiedlichen universitären Bereichen voranzutreiben. Meist stand die Unterstützung von Lehr- und Lernaktivitäten im Vordergrund, aber teilweise wurde die Perspektive auch auf Forschung, Administration und Informationsbeschaffung und -aufbereitung ausgeweitet. Wo stehen die Hochschulen heute in der programmatischen Umsetzung? Dieses Buch beantwortet die Frage anhand von zwei Beispielen der ETH Zürich: dem auf breite, info-strukturelle Veränderungen ausgerichteten Programm ETH World und dem auf die Förderung innovativer Lehre bezogenen Fonds filep. Visionen der Hochschulentwicklung werden ebenso diskutiert wie die Problematik der Evaluation komplexer Programme. Unter arbeitspsychologischer Perspektive werden Veränderungen analysiert, die sich mit dem Einsatz neuer Technologien für den Arbeitsplatz Hochschule ergeben, und verschiedene Projektberichte zeigen auf, wie der innovative Einsatz neuer Technologien in den unterschiedlichen Bereichen einer Hochschule (Administration, Bibliothek, Lehre, Forschung und Infrastruktur) gelingen kann. Das Ziel dieses Herausgeberbandes ist es, die komplexe Dynamik aufgabenbezogener, sozialer und institutioneller Faktoren bei der Umsetzung technologiebezogener Innovationsprozesse zu zeigen und damit auch Möglichkeiten der zukünftigen Gestaltung von Programminitiativen zur Einbindung von IKT in universitäres Arbeiten zu diskutieren.</p>
			</richtext>
		</abstract>
		<address type="sharef:placePublished">Zürich, Switzerland</address>
		<identifier type="sharef:isbn">978-3-7281-3079-2</identifier>
		<publisher>vdf Verlag</publisher>
		<title type="sharef:primaryTitle">Hochschule im info-strukturellen Wandel</title>
		<identifier type="sharef:uri">http://www.vdf.ethz.ch/info/showDetails.asp?isbnNr=3079</identifier>
	</reference>
	<reference name="moh05" src="bibtex:incollection" src-info="bibtex:line-21210" type="sharef:incollection" crossref="dbidm">
		<names type="sharef:author">
			<person>
				<givenname>Sriram</givenname>
				<surname>Mohan</surname>
			</person>
			<person>
				<givenname>Arijit</givenname>
				<surname>Sengupta</surname>
			</person>
		</names>
		<section type="sharef:chapter">X</section>
		<pages>293-322</pages>
		<title type="sharef:primaryTitle">Conceptual Modeling for XML — A Myth or a Reality?</title>
	</reference>
	<reference name="dbidm" src="bibtex:book" src-info="bibtex:line-21218" type="sharef:book">
		<names type="sharef:editor">
			<person>
				<givenname>Zongmin</givenname>
				<surname>Ma</surname>
			</person>
		</names>
		<date value="2005-12"/>
		<address type="sharef:placePublished">Hershey, Pennsylvania</address>
		<identifier type="sharef:isbn">1-59140-684-6</identifier>
		<publisher>Idea Group Inc.</publisher>
		<title type="sharef:primaryTitle">Database Modeling for Industrial Data Management: Emerging Technologies and Applications</title>
		<identifier type="sharef:uri">http://www.idea-group.com/books/details.asp?ID=5410</identifier>
	</reference>
	<reference name="phi04" src="bibtex:incollection" src-info="bibtex:line-21234" type="sharef:incollection" crossref="bow04">
		<names type="sharef:author">
			<person>
				<givenname>Ronnie J.</givenname>
				<surname>Phillips</surname>
			</person>
			<person>
				<givenname>Richard D.</givenname>
				<surname>Johnson</surname>
			</person>
		</names>
		<title type="sharef:primaryTitle">The Music Industry</title>
		<identifier type="sharef:uri" resourceType="application/pdf">http://lamar.colostate.edu/~rphillip/research/TheMusicIndustry.pdf</identifier>
	</reference>
	<reference name="bow04" src="bibtex:book" src-info="bibtex:line-21241" type="sharef:book">
		<names type="sharef:editor">
			<person>
				<givenname>Simon</givenname>
				<surname>Bowmaker</surname>
			</person>
		</names>
		<date value="2004"/>
		<address type="sharef:placePublished">Northampton, Massachusetts</address>
		<identifier type="sharef:isbn">1843763621</identifier>
		<publisher>Edward Elgar Publishing</publisher>
		<title type="sharef:primaryTitle">Economics Uncut: A Complete Guide to Life, Death, and Misadventure</title>
	</reference>
	<reference name="hab03" src="bibtex:incollection" src-info="bibtex:line-21255" type="sharef:incollection" crossref="bec03">
		<names type="sharef:author">
			<person>
				<givenname>Stuart</givenname>
				<surname>Haber</surname>
			</person>
			<person>
				<givenname>Bill</givenname>
				<surname>Horne</surname>
			</person>
			<person>
				<givenname>Joe</givenname>
				<surname>Pato</surname>
			</person>
			<person>
				<givenname>Tomas</givenname>
				<surname>Sander</surname>
			</person>
			<person>
				<givenname>Robert Endre</givenname>
				<surname>Tarjan</surname>
			</person>
		</names>
		<section type="sharef:chapter">2.8</section>
		<pages>224-233</pages>
		<title type="sharef:primaryTitle">If Piracy Is the Problem, Is DRM the Answer?</title>
		<field type="bibtex:topic">drm[0.9]</field>
	</reference>
	<reference name="bau03" src="bibtex:incollection" src-info="bibtex:line-21264" type="sharef:incollection" crossref="bec03">
		<names type="sharef:author">
			<person>
				<givenname>Tobias</givenname>
				<surname>Bauckhage</surname>
			</person>
		</names>
		<section type="sharef:chapter">3.1</section>
		<pages>234-249</pages>
		<title type="sharef:primaryTitle">The Basic Economic Theory of Copying</title>
	</reference>
	<reference name="fet03" src="bibtex:incollection" src-info="bibtex:line-21272" type="sharef:incollection" crossref="bec03">
		<names type="sharef:author">
			<person>
				<givenname>Marc</givenname>
				<surname>Fetscherin</surname>
			</person>
		</names>
		<section type="sharef:chapter">3.5</section>
		<pages>301-320</pages>
		<title type="sharef:primaryTitle">Evaluating Consumer Acceptance for Protected Digital Content</title>
	</reference>
	<reference name="cle03" src="bibtex:incollection" src-info="bibtex:line-21280" type="sharef:incollection" crossref="bec03">
		<names type="sharef:author">
			<person>
				<givenname>Michel</givenname>
				<surname>Clement</surname>
			</person>
		</names>
		<section type="sharef:chapter">3.6</section>
		<pages>321-333</pages>
		<title type="sharef:primaryTitle">Lessons from Content-for-free Distribution Channels</title>
	</reference>
	<reference name="bre03" src="bibtex:incollection" src-info="bibtex:line-21288" type="sharef:incollection" crossref="bec03">
		<names type="sharef:author">
			<person>
				<givenname>Oliver</givenname>
				<surname>Becker</surname>
			</person>
			<person>
				<givenname>Willms</givenname>
				<surname>Buhse</surname>
			</person>
		</names>
		<section type="sharef:chapter">3.7</section>
		<pages>334-343</pages>
		<title type="sharef:primaryTitle">Standardization in DRM — Trends and Recommendations</title>
		<field type="bibtex:topic">drm[0.9]</field>
	</reference>
	<reference name="bid03" src="bibtex:incollection" src-info="bibtex:line-21297" type="sharef:incollection" crossref="bec03">
		<names type="sharef:author">
			<person>
				<givenname>Peter</givenname>
				<surname>Biddle</surname>
			</person>
			<person>
				<givenname>Paul</givenname>
				<surname>England</surname>
			</person>
			<person>
				<givenname>Marcus</givenname>
				<surname>Peinado</surname>
			</person>
			<person>
				<givenname>Bryan</givenname>
				<surname>Willman</surname>
			</person>
		</names>
		<section type="sharef:chapter">3.8</section>
		<pages>344-365</pages>
		<title type="sharef:primaryTitle">The Darknet and the Future of Content Protection</title>
	</reference>
	<reference name="bec03" src="bibtex:book" src-info="bibtex:line-21305" type="sharef:book">
		<names type="sharef:editor">
			<person>
				<givenname>Eberhard</givenname>
				<surname>Becker</surname>
			</person>
			<person>
				<givenname>Willms</givenname>
				<surname>Buhse</surname>
			</person>
			<person>
				<givenname>Dirk</givenname>
				<surname>Günnewig</surname>
			</person>
			<person>
				<givenname>Niels</givenname>
				<surname>Rump</surname>
			</person>
		</names>
		<date value="2003-11"/>
		<address type="sharef:placePublished">Berlin, Germany</address>
		<identifier type="sharef:isbn">3540404651</identifier>
		<publisher>Springer-Verlag</publisher>
		<title type="sharef:seriesTitle">Lecture Notes in Computer Science</title>
		<title type="sharef:primaryTitle">Digital Rights Management — Technological, Economic, Legal and Political Aspects</title>
		<field type="bibtex:topic">drm[0.9]</field>
		<volume>2770</volume>
	</reference>
	<reference name="pan04" src="bibtex:incollection" src-info="bibtex:line-21323" type="sharef:incollection" crossref="webdynamics">
		<names type="sharef:author">
			<person>
				<givenname>Gautam</givenname>
				<surname>Pant</surname>
			</person>
			<person>
				<givenname>Padmini</givenname>
				<surname>Srinivasan</surname>
			</person>
			<person>
				<givenname>Filippo</givenname>
				<surname>Menczer</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>The large size and the dynamic nature of the Web highlight the need for continuous support and updating of Web based information retrieval systems. Crawlers facilitate the process by following the hyperlinks in Web pages to automatically download a partial snapshot of the Web. While some systems rely on crawlers that exhaustively crawl the Web, others incorporate "focus" within their crawlers to harvest application or topic specific collections. We discuss the basic issues related with developing a crawling infrastructure. This is followed by a review of several topical crawling algorithms, and evaluation metrics that may be used to judge their performance. While many innovative applications of Web crawling are still being invented, we take a brief look at some developed in the past.</p>
			</richtext>
		</abstract>
		<pages>153-178</pages>
		<title type="sharef:primaryTitle">Crawling the Web</title>
		<identifier type="sharef:uri" resourceType="application/pdf">http://dollar.biz.uiowa.edu/~pant/Papers/crawling.pdf</identifier>
	</reference>
	<reference name="webdynamics" src="bibtex:book" src-info="bibtex:line-21332" type="sharef:book">
		<names type="sharef:editor">
			<person>
				<givenname>Mark</givenname>
				<surname>Levene</surname>
			</person>
			<person>
				<givenname>Alexandra</givenname>
				<surname>Poulovassilis</surname>
			</person>
		</names>
		<date value="2004-11"/>
		<address type="sharef:placePublished">Berlin, Germany</address>
		<identifier type="sharef:isbn">978-3-540-40676-1</identifier>
		<publisher>Springer-Verlag</publisher>
		<title type="sharef:primaryTitle">Web Dynamics: Adapting to Change in Content, Size, Topology and Use</title>
		<identifier type="sharef:uri">http://www.springer.com/computer/database+management+&amp;+information+retrieval/book/978-3-540-40676-1</identifier>
	</reference>
	<reference name="bru07" src="bibtex:incollection" src-info="bibtex:line-21348" type="sharef:incollection" crossref="adaptiveweb">
		<names type="sharef:author">
			<person>
				<givenname>Peter</givenname>
				<surname>Brusilovsky</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>Adaptive navigation support is a specific group of technologies that support user navigation in hyperspace, by adapting to the goals, preferences and knowledge of the individual user. These technologies, originally developed in the field of adaptive hypermedia, are becoming increasingly important in several adaptive Web applications, ranging from Web-based adaptive hypermedia to adaptive virtual reality. This chapter provides a brief introduction to adaptive navigation support, reviews major adaptive navigation support technologies and mechanisms, and illustrates these with a range of examples.</p>
			</richtext>
		</abstract>
		<section type="sharef:chapter">8</section>
		<identifier type="sharef:doi">10.1007/978-3-540-72079-9_8</identifier>
		<pages>263-290</pages>
		<title type="sharef:primaryTitle">Adaptive Navigation Support</title>
	</reference>
	<reference name="mic07c" src="bibtex:incollection" src-info="bibtex:line-21358" type="sharef:incollection" crossref="adaptiveweb">
		<names type="sharef:author">
			<person>
				<givenname>Alessandro</givenname>
				<surname>Micarelli</surname>
			</person>
			<person>
				<givenname>Filippo</givenname>
				<surname>Sciarrone</surname>
			</person>
			<person>
				<givenname>Mauro</givenname>
				<surname>Marinilli</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>A very common issue of adaptive Web-Based systems is the modeling of documents. Such documents represent domain-specific information for a number of purposes. Application areas such as Information Search, Focused Crawling and Content Adaptation (among many others) benefit from several techniques and approaches to model documents effectively. For example, a document usually needs preliminary processing in order to obtain the relevant information in an effective and useful format, so as to be automatically processed by the system. The objective of this chapter is to support other chapters, providing a basic overview of the most common and useful techniques and approaches related with document modeling. This chapter describes high-level techniques to model Web documents, such as the Vector Space Model and a number of AI approaches, such as Semantic Networks, Neural Networks and Bayesian Networks. This chapter is not meant to act as a substitute of more comprehensive discussions about the topics presented. Rather, it provides a brief and informal introduction to the main concepts of document modeling, also focusing on the systems that are presented in the rest of the book as concrete examples of the related concepts.</p>
			</richtext>
		</abstract>
		<section type="sharef:chapter">5</section>
		<identifier type="sharef:doi">10.1007/978-3-540-72079-9_5</identifier>
		<pages>155-192</pages>
		<title type="sharef:primaryTitle">Web Document Modeling</title>
	</reference>
	<reference name="sch07b" src="bibtex:incollection" src-info="bibtex:line-21368" type="sharef:incollection" crossref="adaptiveweb">
		<names type="sharef:author">
			<person>
				<givenname>J. Ben</givenname>
				<surname>Schafer</surname>
			</person>
			<person>
				<givenname>Dan</givenname>
				<surname>Frankowski</surname>
			</person>
			<person>
				<givenname>Jon</givenname>
				<surname>Herlocker</surname>
			</person>
			<person>
				<givenname>Shilad</givenname>
				<surname>Sen</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>One of the potent personalization technologies powering the adaptive web is collaborative filtering. Collaborative filtering (CF) is the process of filtering or evaluating items through the opinions of other people. CF technology brings together the opinions of large interconnected communities on the web, supporting filtering of substantial quantities of data. In this chapter we introduce the core concepts of collaborative filtering, its primary uses for users of the adaptive web, the theory and practice of CF algorithms, and design decisions regarding rating systems and acquisition of ratings. We also discuss how to evaluate CF systems, and the evolution of rich interaction interfaces. We close the chapter with discussions of the challenges of privacy particular to a CF recommendation service and important open research questions in the field.</p>
			</richtext>
		</abstract>
		<section type="sharef:chapter">9</section>
		<identifier type="sharef:doi">10.1007/978-3-540-72079-9_9</identifier>
		<pages>291-324</pages>
		<title type="sharef:primaryTitle">Collaborative Filtering Recommender Systems</title>
	</reference>
	<reference name="paz07" src="bibtex:incollection" src-info="bibtex:line-21378" type="sharef:incollection" crossref="adaptiveweb">
		<names type="sharef:author">
			<person>
				<givenname>Michael J.</givenname>
				<surname>Pazzani</surname>
			</person>
			<person>
				<givenname>Daniel</givenname>
				<surname>Billsus</surname>
			</person>
		</names>
		<abstract>
			<richtext>
				<p>This chapter discusses content-based recommendation systems, i.e., systems that recommend an item to a user based upon a description of the item and a profile of the user's interests. Content-based recommendation systems may be used in a variety of domains ranging from recommending web pages, news articles, restaurants, television programs, and items for sale. Although the details of various systems differ, content-based recommendation systems share in common a means for describing the items that may be recommended, a means for creating a profile of the user that describes the types of items the user likes, and a means of comparing items to the user profile to determine what to re commend. The profile is often created and updated automatically in response to feedback on the desirability of items that have been presented to the user.</p>
			</richtext>
		</abstract>
		<section type="sharef:chapter">10</section>
		<identifier type="sharef:doi">10.1007/978-3-540-72079-9_10</identifier>
		<pages>325-341</pages>
		<title type="sharef:primaryTitle">Content-Based Recommendation Systems</title>
	</reference>
	<reference name="adaptiveweb" src="bibtex:book" src-info="bibtex:line-21388" type="sharef:book">
		<names type="sharef:editor">
			<person>
				<givenname>Peter</givenname>
				<surname>Brusilovsky</surname>
			</person>
			<person>
				<givenname>Alfred</givenname>
				<surname>Kobsa</surname>
			</person>
			<person>
				<givenname>Wolfgang</givenname>
				<surname>Nejdl</surname>
			</person>
		</names>
		<date value="2007-05"/>
		<address type="sharef:placePublished">Berlin, Germany</address>
		<identifier type="sharef:doi">10.1007/978-3-540-72079-9</identifier>
		<identifier type="sharef:isbn">978-3-540-72078-2</identifier>
		<publisher>Springer-Verlag</publisher>
		<title type="sharef:seriesTitle">Lecture Notes in Computer Science</title>
		<title type="sharef:primaryTitle">The Adaptive Web</title>
		<identifier type="sharef:uri">http://www.springerlink.com/content/x646782t122p/</identifier>
		<volume>4321</volume>
	</reference>
	<reference name="mil98" src="bibtex:incollection" src-info="bibtex:line-21407" type="sharef:incollection" crossref="bru98">
		<names type="sharef:author">
			<person>
				<givenname>Michael</givenname>
				<surname>Miller</surname>
			</person>
			<person>
				<givenname>L. Jay</givenname>
				<surname>Wantz</surname>
			</person>
		</names>
		<field type="bibtex:index">WWW, COOL</field>
		<title type="sharef:primaryTitle">Computed Web Links: The COOL Link Model</title>
		<identifier type="sharef:uri" resourceType="text/html">http://wwwis.win.tue.nl/ah98/Miller.html</identifier>
	</reference>
	<reference name="bru98" src="bibtex:book" src-info="bibtex:line-21415" type="sharef:book">
		<names type="sharef:editor">
			<person>
				<givenname>Peter</givenname>
				<surname>Brusilovsky</surname>
			</person>
			<person>
				<givenname>Alfred</givenname>
				<surname>Kobsa</surname>
			</person>
			<person>
				<givenname>Julita</givenname>
				<surname>Vassileva</surname>
			</person>
		</names>
		<date value="1998-06"/>
		<address type="sharef:placePublished">Pittsburgh, Pennsylvania</address>
		<identifier type="sharef:isbn">0792348435</identifier>
		<publisher>Kluwer Academic Publishers</publisher>
		<title type="sharef:primaryTitle">Adaptive Hypertext and Hypermedia</title>
	</reference>
	<reference name="hef03" src="bibtex:incollection" src-info="bibtex:line-21430" type="sharef:incollection" crossref="fen03">
		<names type="sharef:author">
			<person>
				<givenname>Jeff</givenname>
				<surname>Heflin</surname>
			</person>
			<person>
				<givenname>James A.</givenname>
				<surname>Hendler</surname>
			</person>
			<person>
				<givenname>Sean</givenname>
				<surname>Luke</surname>
			</person>
		</names>
		<pages>29-64</pages>
		<title type="sharef:primaryTitle">SHOE: A Blueprint for the Semantic Web</title>
		<field type="bibtex:topic">shoe[0.8]</field>
	</reference>
	<reference name="mcg03" src="bibtex:incollection" src-info="bibtex:line-21438" type="sharef:incollection" crossref="fen03">
		<names type="sharef:author">
			<person>
				<givenname>Deborah L.</givenname>
				<surname>McGuinness</surname>
			</person>
			<person>
				<givenname>Richard</givenname>
				<surname>Fikes</surname>
			</person>
			<person>
				<givenname>Lynn Andrea</givenname>
				<surname>Stein</surname>
			</person>
			<person>
				<givenname>James A.</givenname>
				<surname>Hendler</surname>
			</person>
		</names>
		<pages>65-94</pages>
		<title type="sharef:primaryTitle">DAML-ONT: An Ontology Language for the Semantic Web</title>
		<field type="bibtex:topic">damlont[0.8]</field>
	</reference>
	<reference name="ome03" src="bibtex:incollection" src-info="bibtex:line-21446" type="sharef:incollection" crossref="fen03">
		<names type="sharef:author">
			<person>
				<givenname>Borys</givenname>
				<surname>Omelayenko</surname>
			</person>
			<person>
				<givenname>Monica</givenname>
				<surname>Crubézy</surname>
			</person>
			<person>
				<givenname>Dieter</givenname>
				<surname>Fensel</surname>
			</person>
			<person>
				<givenname>Richard</givenname>
				<surname>Benjamins</surname>
			</person>
			<person>
				<givenname>Bob</givenname>
				<surname>Wielinga</surname>
			</person>
			<person>
				<givenname>Enrico</givenname>
				<surname>Motta</surname>
			</person>
			<person>
				<givenname>Mark</givenname>
				<surname>Musen</surname>
			</person>
			<person>
				<givenname>Ying</givenname>
				<surname>Ding</surname>
			</person>
		</names>
		<pages>141-170</pages>
		<title type="sharef:primaryTitle">UPML: The Language and Tool Support for Making the Semantic Web Alive</title>
		<field type="bibtex:topic">upml[0.8]</field>
	</reference>
	<reference name="fen03" src="bibtex:book" src-info="bibtex:line-21454" type="sharef:book">
		<names type="sharef:editor">
			<person>
				<givenname>Dieter</givenname>
				<surname>Fensel</surname>
			</person>
			<person>
				<givenname>James A.</givenname>
				<surname>Hendler</surname>
			</person>
			<person>
				<givenname>Henry</givenname>
				<surname>Lieberman</surname>
			</person>
			<person>
				<givenname>Wolfgang</givenname>
				<surname>Wahlster</surname>
			</person>
		</names>
		<date value="2003-02"/>
		<address type="sharef:placePublished">Cambridge, Massachusetts</address>
		<identifier type="sharef:isbn">0262062321</identifier>
		<publisher>The MIT Press</publisher>
		<title type="sharef:primaryTitle">Spinning the Semantic Web: Bringing the World Wide Web to Its Full Potential</title>
		<identifier type="sharef:uri">http://mitpress.mit.edu/catalog/item/default.asp?sid=7728223F-89EE-45F3-9A3C-83DE01C154AE&amp;ttype=2&amp;tid=9182</identifier>
	</reference>
	<reference name="gol99a" src="bibtex:incollection" src-info="bibtex:line-21470" type="sharef:incollection" crossref="moe99">
		<names type="sharef:author">
			<person>
				<givenname>Charles F.</givenname>
				<surname>Goldfarb</surname>
			</person>
		</names>
		<pages>3-26</pages>
		<title type="sharef:primaryTitle">Future Directions in SGML/XML</title>
		<field type="bibtex:topic">sgml[0.9] xml[0.9]</field>
	</reference>
	<reference name="moe99" src="bibtex:book" src-info="bibtex:line-21478" type="sharef:book">
		<names type="sharef:editor">
			<person>
				<givenname>Wiebke</givenname>
				<surname>Möhr</surname>
			</person>
			<person>
				<givenname>Ingrid</givenname>
				<surname>Schmid</surname>
			</person>
		</names>
		<date value="1999"/>
		<address type="sharef:placePublished">Berlin, Germany</address>
		<identifier type="sharef:isbn">3-540-65543-3</identifier>
		<publisher>Springer-Verlag</publisher>
		<title type="sharef:primaryTitle">SGML und XML: Anwendungen und Perspektiven</title>
	</reference>
	<reference name="bec93" src="bibtex:incollection" src-info="bibtex:line-21492" type="sharef:incollection" crossref="sha93">
		<names type="sharef:author">
			<person>
				<givenname>E. E.</givenname>
				<surname>Beck</surname>
			</person>
		</names>
		<field type="bibtex:index">survey, collaborative writing</field>
		<pages>87-112</pages>
		<title type="sharef:primaryTitle">A Survey of Experiences of Collaborative Writing</title>
	</reference>
	<reference name="sha93" src="bibtex:book" src-info="bibtex:line-21500" type="sharef:book">
		<names type="sharef:editor">
			<person>
				<givenname>Mike</givenname>
				<surname>Sharples</surname>
			</person>
		</names>
		<date value="1993"/>
		<address type="sharef:placePublished">London, UK</address>
		<identifier type="sharef:isbn">3540197826</identifier>
		<publisher>Springer-Verlag</publisher>
		<title type="sharef:seriesTitle">Computer Supported Cooperative Work</title>
		<title type="sharef:primaryTitle">Computer Supported Collaborative Writing</title>
	</reference>
	<reference name="leo94" src="bibtex:incollection" src-info="bibtex:line-21515" type="sharef:incollection" crossref="dan94">
		<names type="sharef:author">
			<person>
				<givenname>Helmut</givenname>
				<surname>Leopold</surname>
			</person>
			<person>
				<givenname>Andrew T.</givenname>
				<surname>Campbell</surname>
			</person>
			<person>
				<givenname>David</givenname>
				<surname>Hutchison</surname>
			</person>
			<person>
				<givenname>Nicolaus</givenname>
				<surname>Singer</surname>
			</person>
		</names>
		<field type="bibtex:index">group communication, multimedia, distributed applications, collaborative applications</field>
		<pages>64-81</pages>
		<title type="sharef:primaryTitle">Distributed Multimedia Communication System Requirements</title>
	</reference>
	<reference name="cam94" src="bibtex:incollection" src-info="bibtex:line-21523" type="sharef:incollection" crossref="dan94">
		<names type="sharef:author">
			<person>
				<givenname>Andrew T.</givenname>
				<surname>Campbell</surname>
			</person>
			<person>
				<givenname>Geoff</givenname>
				<surname>Coulson</surname>
			</person>
			<person>
				<givenname>Francisco</givenname>
				<surname>García</surname>
			</person>
			<person>
				<givenname>David</givenname>
				<surname>Hutchison</surname>
			</person>
		</names>
		<field type="bibtex:index">QoS-A</field>
		<pages>101-122</pages>
		<title type="sharef:primaryTitle">Integrated Quality of Service for Multimedia Communications</title>
	</reference>
	<reference name="dan94b" src="bibtex:incollection" src-info="bibtex:line-21531" type="sharef:incollection" crossref="dan94">
		<names type="sharef:author">
			<person>
				<givenname>André</givenname>
				<surname>Danthine</surname>
			</person>
			<person>
				<givenname>Olivier</givenname>
				<surname>Bonaventure</surname>
			</person>
			<person>
				<givenname>Guy</givenname>
				<surname>Leduc</surname>
			</person>
		</names>
		<field type="bibtex:index">QoS, OSI95</field>
		<pages>124-150</pages>
		<title type="sharef:primaryTitle">The QoS Enhancements in OSI95</title>
	</reference>
	<reference name="dan94" src="bibtex:book" src-info="bibtex:line-21539" type="sharef:book">
		<names type="sharef:editor">
			<person>
				<givenname>André</givenname>
				<surname>Danthine</surname>
			</person>
		</names>
		<date value="1994"/>
		<address type="sharef:placePublished">Berlin, Germany</address>
		<identifier type="sharef:isbn">3540583165</identifier>
		<publisher>Springer-Verlag</publisher>
		<title type="sharef:seriesTitle">Research Reports ESPRIT (Project 5341, OSI95, volume 1)</title>
		<title type="sharef:primaryTitle">The OSI95 Transport Service with Multimedia Support</title>
	</reference>
	<reference name="had93" src="bibtex:incollection" src-info="bibtex:line-21554" type="sharef:incollection" crossref="mul93">
		<names type="sharef:author">
			<person>
				<givenname>Vassos</givenname>
				<surname>Hadzilacos</surname>
			</person>
			<person>
				<givenname>Sam</givenname>
				<surname>Toueg</surname>
			</person>
		</names>
		<section type="sharef:chapter">5</section>
		<field type="bibtex:index">multicast, broadcast, reliability, ordering</field>
		<pages>97-145</pages>
		<title type="sharef:primaryTitle">Fault-Tolerant Broadcasts and Related Problems</title>
	</reference>
	<reference name="mul93" src="bibtex:book" src-info="bibtex:line-21563" type="sharef:book">
		<names type="sharef:editor">
			<person>
				<givenname>Sape</givenname>
				<surname>Mullender</surname>
			</person>
		</names>
		<date value="1993"/>
		<address type="sharef:placePublished">New York, NY</address>
		<edition>2nd</edition>
		<identifier type="sharef:isbn">0201624273</identifier>
		<publisher>ACM Press</publisher>
		<title type="sharef:primaryTitle">Distributed Systems</title>
	</reference>
	<reference name="eng88" src="bibtex:incollection" src-info="bibtex:line-21578" type="sharef:incollection" crossref="gol88">
		<names type="sharef:author">
			<person>
				<givenname>Douglas C.</givenname>
				<surname>Engelbart</surname>
			</person>
		</names>
		<pages>187-236</pages>
		<title type="sharef:primaryTitle">The Augmented Knowledge Workshop</title>
	</reference>
	<reference name="gol88" src="bibtex:book" src-info="bibtex:line-21585" type="sharef:book">
		<names type="sharef:editor">
			<person>
				<givenname>Adele</givenname>
				<surname>Goldberg</surname>
			</person>
		</names>
		<date value="1988-08"/>
		<address type="sharef:placePublished">New York, NY</address>
		<identifier type="sharef:isbn">0201112590</identifier>
		<publisher>ACM Press</publisher>
		<title type="sharef:primaryTitle">History of Personal Workstations</title>
	</reference>
	<reference name="green91" src="bibtex:book" src-info="bibtex:line-21600" type="sharef:book">
		<names type="sharef:editor">
			<person>
				<givenname>Saul</givenname>
				<surname>Greenberg</surname>
			</person>
		</names>
		<date value="1991"/>
		<address type="sharef:placePublished">London, UK</address>
		<identifier type="sharef:isbn">0122992202</identifier>
		<publisher>Academic Press</publisher>
		<title type="sharef:seriesTitle">Computers and People Series</title>
		<title type="sharef:primaryTitle">Computer-supported Cooperative Work and Groupware</title>
	</reference>
	<reference name="gre88" src="bibtex:book" src-info="bibtex:line-21615" type="sharef:book">
		<names type="sharef:editor">
			<person>
				<givenname>Irene</givenname>
				<surname>Greif</surname>
			</person>
		</names>
		<date value="1988"/>
		<address type="sharef:placePublished">San Mateo, California</address>
		<identifier type="sharef:isbn">0934613575</identifier>
		<publisher>Morgan Kaufmann Publishers</publisher>
		<title type="sharef:primaryTitle">Computer-Supported Cooperative Work: A Book of Readings</title>
		<field type="bibtex:topic">cscw[0.8]</field>
	</reference>
	<reference name="pan89" src="bibtex:book" src-info="bibtex:line-21630" type="sharef:book">
		<names type="sharef:editor">
			<person>
				<givenname>Uta</givenname>
				<surname>Pankoke-Babatz</surname>
			</person>
		</names>
		<date value="1989"/>
		<address type="sharef:placePublished">Chichester, England</address>
		<field type="bibtex:index">AMIGO, AAM, group communication models, group communication systems</field>
		<identifier type="sharef:isbn">0745806945</identifier>
		<publisher>Ellis Horwood</publisher>
		<title type="sharef:seriesTitle">Books in Information Technology</title>
		<title type="sharef:primaryTitle">Computer-Based Group Communication — The AMIGO Activity Model</title>
	</reference>
	<reference name="mot08a" src="bibtex:phdthesis" src-info="bibtex:line-21647" type="sharef:thesis">
		<names type="sharef:author">
			<person>
				<givenname>Luca</givenname>
				<surname>Mottola</surname>
			</person>
		</names>
		<date value="2008"/>
		<address type="sharef:placePublished">Milano, Italy</address>
		<publisher type="sharef:university">Politecnico di Milano</publisher>
		<title type="sharef:primaryTitle">Programming Wireless Sensor Networks: From Physical to Logical Neighborhoods</title>
		<identifier type="sharef:uri" resourceType="application/pdf">http://www.sics.se/~luca/theses/mottola08programming.pdf</identifier>
		<howpublished>Ph.D. Thesis</howpublished>
	</reference>
	<reference name="kau03" src="bibtex:phdthesis" src-info="bibtex:line-21656" type="sharef:thesis">
		<names type="sharef: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 type="sharef:placePublished">Bergen, Norway</address>
		<publisher type="sharef:university">University of Bergen</publisher>
		<title type="sharef:primaryTitle">Efficiently Locating Schema Incompatibilities in an Extensible Markup Language</title>
		<field type="bibtex:topic">xsd[0.8]</field>
		<identifier type="sharef:uri" resourceType="application/pdf">www.ub.uib.no/elpub/2003/h/413001/Hovedoppgave.pdf</identifier>
		<howpublished>Ph.D. Thesis</howpublished>
	</reference>
	<reference name="hlo05" src="bibtex:phdthesis" src-info="bibtex:line-21668" type="sharef:thesis">
		<names type="sharef:author">
			<person>
				<givenname>Pavel</givenname>
				<surname>Hloušek</surname>
			</person>
		</names>
		<date value="2005"/>
		<address type="sharef:placePublished">Prague, Czech Republic</address>
		<publisher type="sharef:university">Charles University</publisher>
		<title type="sharef:primaryTitle">XPath, XSLT, XQuery: Formal Approach</title>
		<field type="bibtex:topic">xpath[0.8] xslt2[0.8] xquery[0.8]</field>
		<identifier type="sharef:uri" resourceType="application/pdf">http://kocour.ms.mff.cuni.cz/~hlousek/papers/XSXQcomp.pdf</identifier>
		<howpublished>Ph.D. Thesis</howpublished>
	</reference>
	<reference name="bou00b" src="bibtex:phdthesis" src-info="bibtex:line-21678" type="sharef:thesis">
		<names type="sharef:author">
			<person>
				<givenname>Niels Olof</givenname>
				<surname>Bouvin</surname>
			</person>
		</names>
		<date value="2000-11"/>
		<address type="sharef:placePublished">Århus, Denmark</address>
		<publisher type="sharef:university">University of Århus</publisher>
		<title type="sharef:primaryTitle">Augmenting the Web through Open Hypermedia</title>
		<field type="bibtex:topic">arakne[1]</field>
		<identifier type="sharef:uri" resourceType="application/pdf">http://www.daimi.au.dk/~bouvin/Arakne/thesis.pdf</identifier>
		<howpublished>Ph.D. Thesis</howpublished>
	</reference>
	<reference name="lie05" src="bibtex:phdthesis" src-info="bibtex:line-21689" type="sharef:thesis">
		<names type="sharef: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 type="sharef:placePublished">Oslo, Norway</address>
		<publisher type="sharef:university">University of Oslo</publisher>
		<title type="sharef:primaryTitle">Cascading Style Sheets</title>
		<field type="bibtex:topic">css[1]</field>
		<identifier type="sharef:uri">http://people.opera.com/howcome/2006/phd/</identifier>
		<howpublished>Ph.D. Thesis</howpublished>
	</reference>
	<reference name="man03" src="bibtex:phdthesis" src-info="bibtex:line-21701" type="sharef:thesis">
		<names type="sharef:author">
			<person>
				<givenname>Murali</givenname>
				<surname>Mani</surname>
			</person>
		</names>
		<date value="2003"/>
		<publisher type="sharef:university">University of California, Los Angeles</publisher>
		<title type="sharef:primaryTitle">Data Modeling using XML Schemas</title>
		<field type="bibtex:topic">xsd[0.8] erex[1] xgrammar[0.9]</field>
		<identifier type="sharef:uri" resourceType="application/pdf">http://www.cs.wpi.edu/~mmani/dissertation.pdf</identifier>
		<howpublished>Ph.D. Thesis</howpublished>
	</reference>
	<reference name="doa02b" src="bibtex:phdthesis" src-info="bibtex:line-21710" type="sharef:thesis">
		<names type="sharef:author">
			<person>
				<givenname>AnHai</givenname>
				<surname>Doan</surname>
			</person>
		</names>
		<date value="2002"/>
		<publisher type="sharef:university">University of Washington</publisher>
		<title type="sharef:primaryTitle">Learning to Map between Structured Representations of Data</title>
		<identifier type="sharef:uri" resourceType="application/pdf">http://anhai.cs.uiuc.edu/home/thesis/anhai-thesis.pdf</identifier>
		<howpublished>Ph.D. Thesis</howpublished>
	</reference>
	<reference name="phe98" src="bibtex:phdthesis" src-info="bibtex:line-21718" type="sharef:thesis">
		<names type="sharef:author">
			<person>
				<givenname>Thomas Arthur</givenname>
				<surname>Phelps</surname>
			</person>
		</names>
		<date value="1998"/>
		<publisher type="sharef:university">University of California, Berkeley</publisher>
		<title type="sharef:primaryTitle">Multivalent Documents: Anytime, Anywhere, Any Type, Every Way User-Improvable Digital Documents and Systems</title>
		<identifier type="sharef: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" src="bibtex:phdthesis" src-info="bibtex:line-21726" type="sharef:thesis">
		<names type="sharef:author">
			<person>
				<givenname>Roy Thomas</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 type="sharef:placePublished">Irvine, California</address>
		<publisher type="sharef:university">University of California, Irvine</publisher>
		<title type="sharef:primaryTitle">Architectural Styles and the Design of Network-based Software Architectures</title>
		<field type="bibtex:topic">rest[1]</field>
		<identifier type="sharef:uri" resourceType="text/html">http://www.ics.uci.edu/~fielding/pubs/dissertation/top.htm</identifier>
		<howpublished>Ph.D. Thesis</howpublished>
	</reference>
	<reference name="hos01" src="bibtex:phdthesis" src-info="bibtex:line-21737" type="sharef:thesis">
		<names type="sharef:author">
			<person>
				<givenname>Haruo</givenname>
				<surname>Hosoya</surname>
			</person>
		</names>
		<date value="2001-12"/>
		<publisher type="sharef:university">University of Tokyo</publisher>
		<title type="sharef:primaryTitle">Regular Expression Types for XML</title>
		<field type="bibtex:topic">xduce[1]</field>
		<howpublished>Ph.D. Thesis</howpublished>
	</reference>
	<reference name="nah95" src="bibtex:phdthesis" src-info="bibtex:line-21746" type="sharef:thesis">
		<names type="sharef:author">
			<person>
				<givenname>Klara</givenname>
				<surname>Nahrstedt</surname>
			</person>
		</names>
		<date value="1995"/>
		<address type="sharef:placePublished">Philadelphia, Pennsylvania</address>
		<field type="bibtex:index">QoS Broker</field>
		<publisher type="sharef:university">University of Pennsylvania</publisher>
		<title type="sharef:primaryTitle">An Architecture for End-to-End Quality of Service Provision and its Experimental Validation</title>
		<howpublished>Ph.D. Thesis</howpublished>
	</reference>
	<reference name="dee91" src="bibtex:phdthesis" src-info="bibtex:line-21755" type="sharef:thesis">
		<names type="sharef: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="sharef:university">Stanford University</publisher>
		<title type="sharef:primaryTitle">Multicast Routing in a Datagram Internetwork</title>
		<howpublished>Ph.D. Thesis</howpublished>
	</reference>
	<reference name="lub90" src="bibtex:phdthesis" src-info="bibtex:line-21763" type="sharef:thesis">
		<names type="sharef:author">
			<person>
				<givenname>Hannes P.</givenname>
				<surname>Lubich</surname>
			</person>
		</names>
		<date value="1990"/>
		<address type="sharef:placePublished">Zürich, Switzerland</address>
		<field type="bibtex:index">CSCW, MultimETH, OSI</field>
		<identifier type="sharef:isbn">3-7281-1740-4</identifier>
		<annotation type="bibtex:note">
			<richtext>
				<p>Diss. ETH No. 8985</p>
			</richtext>
		</annotation>
		<publisher type="sharef:university">ETH Zürich</publisher>
		<title type="sharef:primaryTitle">MultimETH: Ein Beitrag zur Konzeption eines Echtzeit-Multimedia-Konferenzsystems</title>
		<howpublished>Ph.D. Thesis</howpublished>
	</reference>
	<reference name="pla94b" src="bibtex:phdthesis" src-info="bibtex:line-21774" type="sharef:thesis">
		<names type="sharef:author">
			<person>
				<givenname>Thomas</givenname>
				<surname>Plagemann</surname>
			</person>
		</names>
		<date value="1994"/>
		<address type="sharef:placePublished">Zürich, Switzerland</address>
		<field type="bibtex:index">Da CaPo, dynamic protocol configuration, high speed networks</field>
		<identifier type="sharef:isbn">3-7281-2334-X</identifier>
		<annotation type="bibtex:note">
			<richtext>
				<p>Diss. ETH No. 10830</p>
			</richtext>
		</annotation>
		<publisher type="sharef:university">ETH Zürich</publisher>
		<title type="sharef:primaryTitle">A Framework for Dynamic Protocol Configuration</title>
		<howpublished>Ph.D. Thesis</howpublished>
	</reference>
	<reference name="gut95b" src="bibtex:phdthesis" src-info="bibtex:line-21785" type="sharef:thesis">
		<names type="sharef:author">
			<person>
				<givenname>Thomas</givenname>
				<surname>Gutekunst</surname>
			</person>
		</names>
		<date value="1995"/>
		<address type="sharef:placePublished">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="sharef:university">ETH Zürich</publisher>
		<title type="sharef:primaryTitle">Shared Window Systems</title>
		<howpublished>Ph.D. Thesis</howpublished>
	</reference>
	<reference name="bur96" src="bibtex:phdthesis" src-info="bibtex:line-21795" type="sharef:thesis">
		<names type="sharef: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 type="sharef:placePublished">Zürich, Switzerland</address>
		<identifier type="sharef:isbn">978-3-7281-2386-2</identifier>
		<annotation type="bibtex:note">
			<richtext>
				<p>Diss. ETH No. 11600</p>
			</richtext>
		</annotation>
		<publisher type="sharef:university">ETH Zürich</publisher>
		<title type="sharef:primaryTitle">Towards Computer Supported Audio Conferencing</title>
		<field type="bibtex:topic">multimeth[0.9]</field>
		<howpublished>Ph.D. Thesis</howpublished>
	</reference>
	<reference name="jen97" src="bibtex:phdthesis" src-info="bibtex:line-21807" type="sharef:thesis">
		<names type="sharef: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 type="sharef:placePublished">Zürich, Switzerland</address>
		<annotation type="bibtex:note">
			<richtext>
				<p>Diss. ETH No. 12030</p>
			</richtext>
		</annotation>
		<publisher type="sharef:university">ETH Zürich</publisher>
		<title type="sharef:primaryTitle">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" src="bibtex:phdthesis" src-info="bibtex:line-21817" type="sharef:thesis">
		<names type="sharef: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 type="sharef:placePublished">Zürich, Switzerland</address>
		<field type="bibtex:index">GMS, GAP, GSP, GSA, GUA</field>
		<identifier type="sharef: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="sharef:university">ETH Zürich</publisher>
		<title type="sharef:primaryTitle">Group and Session Management for Collaborative Applications</title>
		<identifier type="sharef:uri">http://dret.net/netdret/publications#wil97b</identifier>
		<identifier type="sharef:uri">http://e-collection.ethbib.ethz.ch/show?type=diss&amp;nr=12075</identifier>
		<howpublished>Ph.D. Thesis</howpublished>
	</reference>
	<reference name="bau97" src="bibtex:phdthesis" src-info="bibtex:line-21832" type="sharef:thesis">
		<names type="sharef: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 type="sharef:placePublished">Zürich, Switzerland</address>
		<field type="bibtex:index">mcf[1] qos[0.8]</field>
		<identifier type="sharef: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="sharef:university">ETH Zürich</publisher>
		<title type="sharef:primaryTitle">A Multipoint Communication Architecture for End-to-End Quality of Service Guarantees</title>
		<identifier type="sharef:uri">http://e-collection.ethbib.ethz.ch/show?type=diss&amp;nr=12163</identifier>
		<howpublished>Ph.D. Thesis</howpublished>
	</reference>
	<reference name="sch99" src="bibtex:phdthesis" src-info="bibtex:line-21846" type="sharef:thesis">
		<names type="sharef: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 type="sharef:placePublished">Zürich, Switzerland</address>
		<annotation type="bibtex:note">
			<richtext>
				<p>Diss. ETH No. 13113</p>
			</richtext>
		</annotation>
		<publisher type="sharef:university">ETH Zürich</publisher>
		<title type="sharef:primaryTitle">Zur semiotischen Rekonstruktion des Placeboeffektes</title>
		<identifier type="sharef:uri">http://e-collection.ethbib.ethz.ch/show?type=diss&amp;nr=13113</identifier>
		<howpublished>Ph.D. Thesis</howpublished>
	</reference>
	<reference name="jan00" src="bibtex:phdthesis" src-info="bibtex:line-21857" type="sharef:thesis">
		<names type="sharef:author">
			<person>
				<givenname>Jörn Wilhelm</givenname>
				<surname>Janneck</surname>
			</person>
		</names>
		<date value="2000"/>
		<address type="sharef:placePublished">Zürich, Switzerland</address>
		<identifier type="sharef: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="sharef:university">ETH Zürich</publisher>
		<title type="sharef:primaryTitle">Syntax and Semantics of Graphs</title>
		<identifier type="sharef:uri">http://e-collection.ethbib.ethz.ch/show?type=diss&amp;nr=13758</identifier>
		<howpublished>Ph.D. Thesis</howpublished>
	</reference>
	<reference name="sig05" src="bibtex:phdthesis" src-info="bibtex:line-21869" type="sharef:thesis">
		<names type="sharef:author">
			<person>
				<givenname>Beat</givenname>
				<surname>Signer</surname>
			</person>
		</names>
		<date value="2005"/>
		<abstract>
			<richtext>
				<p>While there have been dramatic increases in the use of digital technologies for information storage, processing and delivery over the last twenty years, the affordances of paper have ensured its retention as a key information medium. Despite predictions of the paperless office, paper is ever more present in our daily work as reflected by the continuously increasing worldwide paper consumption. Many researchers have argued for the retention of paper as an information resource and its integration into cross-media environments as opposed to its replacement. This has resulted in a wide variety of projects and technological developments for digitally augmented paper documents over the past decade. However, the majority of the realised projects focus on technical advances in terms of hardware but pay less attention to the very fundamental information integration and cross-media information management issues. Our information-centric approach for a tight integration of paper and digital information is based on extending an object-oriented database management system with functionality for cross-media information management. The resulting iServer platform introduces fundamental link concepts at an abstract level. The iServer's core link management functionality is available across different multimedia resources. Only the media-specific portion of these general concepts, for example the specification of a link's source anchor, has to be implemented in the form of a plug-in to support new resource types. This resource plug-in mechanism results in a flexible and extensible system where new types of digital as well as physical resources can easily be integrated and, more importantly, cross-linked to the growing set of supported multimedia resources. In addition to the associative linking of information, our solution allows for the integration of semantic metadata and supports multiple classification of information units. iServer can, not only link between various static information entities, but also link to active content and this has proven to be very effective in enabling more complex interaction design. As part of the European project Paper++, under the Disappearing Computer Programme, an iServer plug-in for interactive paper has been implemented to fully integrate paper and digital media, thereby gaining the best of the physical and the digital worlds. It not only supports linking from physical paper to digital information, but also enables links from digital content to physical paper or even paper to paper links. This multi-mode user interface results in highly interactive systems where users can easily switch back and forth between paper and digital information. The definition of an abstract input device interface further provides flexibility for supporting emerging technologies for paper link definition in addition to the hardware solutions for paper link definition and activation that were developed within the Paper++ project. We introduce different approaches for cross-media information authoring where information is either compiled by established publishers with an expertise in a specific domain or by individuals who produce their own cross-media information environments. Preauthored information can be combined with personally aggregated information. A distributed peer-to-peer version of the iServer platform supports collaborative authoring and the sharing of link knowledge within a community of users. The associations between different types of resources as well as other application-specific information can be visualised on different output channels. Universal access to the iServer's information space is granted using the eXtensible Information Management Architecture (XIMA), our publishing platform for multi-channel access. Our fundamental concepts for interactive paper and cross-media information management have been designed independently of particular hardware solutions and modes of interaction which enables the iServer platform to easily adapt to both new technologies and applications. Finally, the information infrastructure that we have developed has great potential as an experimental platform for the investigation of emerging multimedia resources in general and interactive paper with its possible applications in particular.</p>
			</richtext>
		</abstract>
		<address type="sharef:placePublished">Zürich, Switzerland</address>
		<annotation type="bibtex:note">
			<richtext>
				<p>Diss. ETH No. 16218</p>
			</richtext>
		</annotation>
		<publisher type="sharef:university">ETH Zürich</publisher>
		<title type="sharef:primaryTitle">Fundamental Concepts for Interactive Paper and Cross-Media Information Spaces</title>
		<identifier type="sharef:uri">http://www.globis.ethz.ch/script/publication/download?docid=411</identifier>
		<identifier type="sharef:uri">http://e-collection.ethbib.ethz.ch/cgi-bin/show.pl?type=diss&amp;nr=16218</identifier>
		<howpublished>Ph.D. Thesis</howpublished>
	</reference>
	<reference name="sch00c" src="bibtex:phdthesis" src-info="bibtex:line-21881" type="sharef:thesis">
		<names type="sharef:author">
			<person>
				<givenname>Bruno</givenname>
				<surname>Schneider</surname>
			</person>
		</names>
		<date value="2000"/>
		<address type="sharef:placePublished">Zürich, Switzerland</address>
		<annotation type="bibtex:note">
			<richtext>
				<p>Diss. nat. Univ. Zürich</p>
			</richtext>
		</annotation>
		<publisher type="sharef:university">University of Zurich</publisher>
		<title type="sharef:primaryTitle">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="sch07c" src="bibtex:phdthesis" src-info="bibtex:line-21890" type="sharef:thesis">
		<names type="sharef:author">
			<person>
				<givenname>Alexandra</givenname>
				<surname>Schaller</surname>
			</person>
		</names>
		<date value="2007-12"/>
		<abstract>
			<richtext>
				<p>This thesis is a contribution to the academic literature regarding post-trade activities in the foreign exchange market. The international foreign exchange market is the largest market in the world. Its volume is six times the trading volume of the second largest market, the U.S. Treasury securities market. Since there are always two parties to each foreign exchange transaction, the volume to be settled is even twice the trading volume. In foreign exchange trading, it is not uncommon for two banks to owe each other 2 billion US Dollar overnight because settlement has not yet been completed. The figures make clear that reliability and resilience of the settlement processes are essential. Interruptions or delays may have disastrous consequences for the financial industry. During the past years, financial authorities have started to realize the system's vulnerability and increasingly paid attention to post trade activities in general and to settlement practices of foreign exchange in particular. In the nineties, several publications have highlighted that most banks had tremendous overnight credit risk exposures due to current settlement and reconciliation practices at that time. Regulators called on the financial industry to take appropriate action to measure and reduce the settlement risks in the foreign exchange market. Since then, the international financial industry has heavily invested in operations and technology to comply with regulators' requests. The most important result from these common industry efforts is the implementation of the Continuous Linked Settlement (CLS) system. Briefly, CLS is specifically designed to eliminate credit risk on foreign exchange transactions that it settles. A payment-versus-payment settlement mechanism combined with a number of risk management provisions eliminates credit risk exposures. The elimination of credit risk, however, brought a number of other changes to the market. This thesis deals with the most important aspects of the CLS system in general and its implications for the market. It provides an in depth description of CLS's functionality, documents the history of its implementation, and looks into its transaction structure. The goal of this thesis can thus be split in four parts: (1) Provide a description of CLS' history, (2) deliver an in depth description of its functionality, (3) assess CLS's achievement in reducing credit risk, and (4) analyze the evolvement of its transaction structure and pick up some liquidity issues. These four parts together form a comprehensive overview of the CLS system. It must be mentioned that this thesis does not explicitly focus on operational risks or corporate governance issues nor on systemic risk aspects. They may be a component part of the thesis but are not addressed separately. The thesis concludes that CLS is a success story. Once running, the system proved its resilience and was able to successfully penetrate the market. Around 60 percent of global foreign exchange turnover is estimated to be settled in CLS. If this equals a 60 percent credit risk reduction, the urge of the Bank for International Settlements may be considered to be well fulfilled. The empirical part of the thesis offers insights into the trading structure among CLS members. Substantial differences in the structure of settlement member and third party relationships were found. Settlement members are highly connected among each other and do not show significant changes over time. The connectivity of third parties is much lower and shows the development of power law characteristics. Statistics and visualized network graphs suggest that new third parties tend to be smaller than the existing ones. This means that a relatively small group of members generates an increasing part of the business. In terms of liquidity, the analysis was based on the bilateral net sell position. The fact that these positions did in average not lower during the past years, indicates that simply increasing the number of members does not automatically lead to lower bilateral net sell positions. In contrast, cross sectional regression suggests that there is a certain dependency between the level of the bilateral net sell position and the type of trade relation. It seems that trade relations between members with high relative connectivity lead to lower bilateral net sell positions. If and how these results may be implemented in a practical context is yet unclear.</p>
			</richtext>
		</abstract>
		<address type="sharef:placePublished">Zürich, Switzerland</address>
		<publisher type="sharef:university">University of Zurich</publisher>
		<title type="sharef:primaryTitle">Continuous Linked Settlement: History and Implications</title>
		<identifier type="sharef:uri">http://opac.nebis.ch/F/?local_base=NEBIS&amp;con_lng=GER&amp;func=find-b&amp;find_code=SYS&amp;request=005544233</identifier>
		<howpublished>Ph.D. Thesis</howpublished>
	</reference>
	<reference name="cat02" src="bibtex:phdthesis" src-info="bibtex:line-21901" type="sharef:thesis">
		<names type="sharef:author">
			<person>
				<givenname>Philippe</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 type="sharef:placePublished">Zürich, Switzerland</address>
		<annotation type="bibtex:note">
			<richtext>
				<p>Diss. ETH No. 14603</p>
			</richtext>
		</annotation>
		<publisher type="sharef:university">ETH Zürich</publisher>
		<title type="sharef:primaryTitle">Biometric Authentication System using Human Gait</title>
		<identifier type="sharef:uri">http://e-collection.ethbib.ethz.ch/show?type=diss&amp;nr=14603</identifier>
		<howpublished>Ph.D. Thesis</howpublished>
	</reference>
	<reference name="sch02c" src="bibtex:phdthesis" src-info="bibtex:line-21912" type="sharef:thesis">
		<names type="sharef: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 type="sharef:placePublished">Zürich, Switzerland</address>
		<annotation type="bibtex:note">
			<richtext>
				<p>Diss. ETH No. 14605</p>
			</richtext>
		</annotation>
		<publisher type="sharef:university">ETH Zürich</publisher>
		<title type="sharef:primaryTitle">GIS-Funktionen in Atlas-Informationssystemen</title>
		<identifier type="sharef:uri">http://e-collection.ethbib.ethz.ch/show?type=diss&amp;nr=14605</identifier>
		<howpublished>Ph.D. Thesis</howpublished>
	</reference>
	<reference name="tyl03" src="bibtex:phdthesis" src-info="bibtex:line-21923" type="sharef:thesis">
		<names type="sharef: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 type="sharef:placePublished">Zürich, Switzerland</address>
		<annotation type="bibtex:note">
			<richtext>
				<p>Diss. ETH No. 14913</p>
			</richtext>
		</annotation>
		<publisher type="sharef:university">ETH Zürich</publisher>
		<title type="sharef:primaryTitle">Induced Global Unsteadiness and Sidewall Effects in the Backward-Facing Step Flow: Experiments and Numerical Simulations</title>
		<identifier type="sharef:uri">http://e-collection.ethbib.ethz.ch/show?type=diss&amp;nr=14913</identifier>
		<howpublished>Ph.D. Thesis</howpublished>
	</reference>
	<reference name="stei97" src="bibtex:phdthesis" src-info="bibtex:line-21934" type="sharef:thesis">
		<names type="sharef:author">
			<person>
				<givenname>Andreas</givenname>
				<surname>Steiner</surname>
			</person>
		</names>
		<date value="1997-11"/>
		<abstract>
			<richtext>
				<p>Non-temporal data models and their implementations as database management systems (DBMS) capture a single state of the real world, usually the current one. They support modification operations which facilitate the transition from one consistent database state to another. For queries, they assume that the data is synchronous, meaning that all the facts stored in the database are valid at the time instant a query is evaluated. There exist many application domains, however, where it is necessary to reconstruct earlier database states or even store future database states (e. g. for planning, budgets) in parallel. The different database states are stored as temporal data. Such temporal data arises, for example, in financial and insurance applications, in reservation systems and in medical information management. Of course, it is also possible in practice to store timestamps in classical DBMS and model the temporal aspects mentioned above in this way. However, such an approach does not cater for the special semantics of time. Thus, there are many proposals for both relational and object-oriented models as to how the non-temporal data models can be enhanced to support the management of temporal data. Their focus is mainly on extending the data structures and/or the query language. Hardly any of these temporal data models were implemented, even in the form of prototype systems. A more systematic way to define temporal data models is based on generalising a non-temporal data model into a temporal one. Using generalisation means that all constructs of the underlying non-temporal data model — its data structures, operations and integrity constraints — are enhanced to support the management of time-varying data. To show the power of the generalisation approach, this thesis investigates three approaches to managing temporal data, along with the corresponding prototype implementations. The first approach timestamps data by extending the data structures with special timestamp attributes, but, in contrast to existing proposals, uses a generalised query, data definition and data manipulation language. The second approach fully generalises a non-temporal object data model into a temporal one. The resulting temporal object data model TOM does not extend the data structures, but rather uses the notion of temporal object identifiers to timestamp data. In TOM, not only the user data can be timestamped, but also constructs supported by the data model such as collections of objects, types, integrity constraints and so on, since they are also considered to be objects. This temporal data model was implemented as a single-user prototype system. The third approach demonstrates how the extensible nature of object-oriented DBMS can be used directly to support temporal applications through the use of abstract data types. It is shown that while temporal data structures and operations can be accommodated in this way, support for generalised data models and query languages is restricted. These approaches show that a generalised temporal data model is better suited to the modeling and management of temporal data than an extended one, and that generalised data models are implementable. By presenting an evolutionary path from temporal first normal form relations to temporal nested relations, temporal complex objects and temporal object-oriented data models, it is shown that the temporal object data model TOM actually subsumes the extended temporal data models.</p>
			</richtext>
		</abstract>
		<address type="sharef:placePublished">Zürich, Switzerland</address>
		<annotation type="bibtex:note">
			<richtext>
				<p>Diss. ETH No. 12434</p>
			</richtext>
		</annotation>
		<publisher type="sharef:university">ETH Zürich</publisher>
		<title type="sharef:primaryTitle">A Generalisation Approach to Temporal Data Models and their Implementations</title>
		<identifier type="sharef:uri" resourceType="application/pdf">http://www.timeconsult.com/Publications/diss.pdf</identifier>
		<howpublished>Ph.D. Thesis</howpublished>
	</reference>
	<reference name="gre04" src="bibtex:phdthesis" src-info="bibtex:line-21946" type="sharef:thesis">
		<names type="sharef: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 type="sharef:placePublished">Golden, Colorado</address>
		<publisher type="sharef:university">Colorado School of Mines</publisher>
		<title type="sharef:primaryTitle">Time-lapse Monitoring with Coda Wave Interferometry</title>
		<identifier type="sharef:uri" resourceType="application/pdf">http://acoustics.mines.edu/preprints/cwi.pdf</identifier>
		<howpublished>Ph.D. Thesis</howpublished>
	</reference>
	<reference name="gre07b" src="bibtex:phdthesis" src-info="bibtex:line-21956" type="sharef:thesis">
		<names type="sharef:author">
			<person>
				<givenname>Adrienne</givenname>
				<surname>Grêt-Regamey</surname>
			</person>
		</names>
		<date value="2007"/>
		<abstract>
			<richtext>
				<p>Economic development relies crucially on natural resources and on the productivity of natural Systems. Economic actors, however, do not have to pay for these production factors because most of the environmental benefits natural resources provide are not marketed and therefore do not command market price. Does accounting for ecosystem goods and Services (ES) in landscape planning help secure long-term economic benefits? Within several building blocks, the value of ES for the regional economy of a mountainous region — the Landschaft Davos (Grisons, Switzerland) — is studied, and a framework to account for ES in landscape planning is suggested. In a first step, a study was designed focusing on the valuation of an important ecosystem Service for a tourism region, namely scenic beauty (Paper I). A prototypical technique to predict preferences for views using GIS (Geographic Information System)-based variables was developed. Data on scenic preferences for landscape changes were gathered using a web-based survey. The relationship between the portion of the field of view, which was taken by different land-uses changes were found to be correlated with the willingness-to-pay responses, and was used to predict changes in scenic values for another view in the region. In a second step, a GIS modeling platform was developed to value changes in the Provision of a set of selected ES (Paper II). We compared the impacts of a human development scenario and a climate scenario on the ES values. The framework helped quantify and visualize the negative impacts of urban expansion and tourist infrastructure developments on scenic beauty and habitats. We showed that forest expansion, predictable under a climate change scenario, favors natural avalanche protection and habitats, and that the loss of ES due to new tourist infrastructures diminished the benefits of the development by 70%. Yet, the framework suggested in Paper II did not include the explicit quantification of the uncertainties related to the quantification and valuation procedure. Especially the use of monetary valuation is known to be associated with many uncertainties,which we discussed in Paper I. Bayesian networks (BN) are know to facilitate the explicit modeling of the involved uncertainties in a probabilistic framework. As natural protection from avalanches was identified as an important ES in the case study region, we linked a BN to a GIS for avalanche risk assessment (Paper III). The study showed that such an approach allows quantifying and visualizing uncertainties in a spatially explicit manner. We could map areas with high uncertainties, located at the border of the avalanche run-out areas, and identify the variables responsible for these uncertainties.While avalanche pressure was identified as having a large influence on the cost values, we applied a Bayesian inference to determine a probabilistic model of the variables influencing the calculated avalanche pressure using observations of past avalanches (Paper IV). Applied to the avalanche risk assessment in Paper III, we found a difference of a factor of two when comparing the resulting annual risks to that calculated using the traditional semi-empirical avalanche hazard model. The question of the contribution of the value of ES to the regional economy was addressed by integrating the regionally valued ES on the supply side of an Input- Output Table (Paper V). Using several different indicators based on this IOT, we discussed the benefits of the ES for regional development. While the considered ES "avalanche protection","carbon Sequestration", and "wood production" added only 2% to the annual regional production volume, the model helped identify which economic sectors benefit most from the use of ES and how important they are for different industries. We showed that, if we abandon using the landscape for economic production, it loses its value not only for the industry formerly using the land (e.g. agriculture), but also for the entire regional production and supply chains linked with this industry. To counteract this effect, we demonstrated that the use of ES had to be intensified: Economic activities should encourage using the ES more intensively, while landscape development should aim at providing the required Services. Based on the knowledge acquired in the first five papers, we addressed the question of the significance of accounting for ES values in landscape planning (Paper VI). We showed that by linking a BN with a GIS, we could identify optimal locations for new settlement areas in regard to impacts to ES. A large part of the optimal areas matched already existing plans to expand the golf course at the entry of the Dischma Valley. The BN allowed explicitly addressing the uncertainties at all levels of the quantification and valuation procedure, and supported a structured approach to the interdisciplinary task requiring information from different specialist fields. While the value of the ES diminished the benefits of a new settlement area by just 30% in 2050, we showed that their relative impact increased in the long-term: If preferences for preserving ES are low nowadays, the expected benefits of a settlement expansion decrease significantly. Thus, incorporating ES values in planning will not bring about sustainability unless each generation is committed to transferring to the next sufficient natural resources to make development sustainable. Considering the importance of the explicit consideration of the uncertainties in the quantification and valuation of ES, BN linked to a GIS are supportive for presenting credible information to planners in a spatially explicit manner. The approach allows unifying human expertise and quantitative knowledge in a coherent framework, which overcomes a major limitation of previous approaches. While the GIS-based flexible framework allows integrating additional ES and different valuation data, more research needs to be conducted to investigate the transferability of such an approach to other areas providing other ES.</p>
			</richtext>
		</abstract>
		<address type="sharef:placePublished">Zürich, Switzerland</address>
		<annotation type="bibtex:note">
			<richtext>
				<p>Diss. ETH No. 17250</p>
			</richtext>
		</annotation>
		<publisher type="sharef:university">ETH Zürich</publisher>
		<title type="sharef:primaryTitle">Spatially Explicit Valuation of Ecosystem Goods and Services in the Alps as a Support Tool for Regional Decision Making</title>
		<identifier type="sharef:uri">http://e-collection.ethbib.ethz.ch/view/eth:29696</identifier>
		<howpublished>Ph.D. Thesis</howpublished>
	</reference>
	<reference name="ana04" src="bibtex:phdthesis" src-info="bibtex:line-21967" type="sharef:thesis">
		<names type="sharef: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 type="sharef:placePublished">Zürich, Switzerland</address>
		<annotation type="bibtex:note">
			<richtext>
				<p>Diss. ETH No. 15441</p>
			</richtext>
		</annotation>
		<publisher type="sharef:university">ETH Zürich</publisher>
		<title type="sharef:primaryTitle">Algorithms for Call Control in Ring Based Networks</title>
		<identifier type="sharef:uri">http://e-collection.ethbib.ethz.ch/show?type=diss&amp;nr=15441</identifier>
		<howpublished>Ph.D. Thesis</howpublished>
	</reference>
	<reference name="kre05" src="bibtex:phdthesis" src-info="bibtex:line-21978" type="sharef:thesis">
		<names type="sharef: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 α (myhcα) 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α 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(-/-)×SM-LacZ mice mounted comparable T cell responses to a recombinant MCMV-LacZ virus, persistent expression of the βgalactosidase transgene in the vasculature, as it occurs in APOE(-/-)×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 type="sharef:placePublished">Zürich, Switzerland</address>
		<annotation type="bibtex:note">
			<richtext>
				<p>Diss. ETH No. 16068</p>
			</richtext>
		</annotation>
		<publisher type="sharef:university">ETH Zürich</publisher>
		<title type="sharef:primaryTitle">Immunopathology of Cardiovascular Diseases</title>
		<identifier type="sharef:uri">http://e-collection.ethbib.ethz.ch/show?type=diss&amp;nr=16068</identifier>
		<howpublished>Ph.D. Thesis</howpublished>
	</reference>
	<reference name="kut04" src="bibtex:phdthesis" src-info="bibtex:line-21989" type="sharef:thesis">
		<names type="sharef:author">
			<person>
				<givenname>Philipp W.</givenname>
				<surname>Kutter</surname>
			</person>
		</names>
		<date value="2004"/>
		<abstract>
			<richtext>
				<p>In this thesis we elaborate a language description formalism called Montages. The Montages formalism can be used to engineer domain specific languages (DSLs), which are computer languages specially tailored and typically restricted to solve problems of specific domains. We focus on DSLs which have some algorithmic flavor and are intended to be used in corporate environments where main-stream state-based programming and modeling formalisms1 prevail. For engineering such DSLs it is important that the designs of the existing, well known general purpose languages (GPLs) can be described as well, and that this descriptions are easily reused as basic building blocks to design new DSLs. Using the Montages tool support Gem-Mex, such a new designs can be composed in an integrated semantics environment, and from the descriptions an interpreter and a specialized visual debugger is generated for the new language. We restrict our research to sequential languages and the technical part of the thesis tries to contribute to the improvement of the DSL design process by focusing on ease of specification and ease of reuse for programming language constructs from well known GPL designs. For the sake of shortness we do not present detailed case studies for DSLs and refer the reader to the literature. Finally, we mainly look at exact reuse of specification modules, and we have not elaborated the means for incremental design by reusing specifications in the sense of object oriented programming. Of course these means are needed as well and we assume the existence of such reuse features without formalizing them. The technical part of the thesis provides the basic specification patterns for introducing all features of an object oriented style of reuse, and applying these patterns to Montages in order to make it an object-oriented specification formalism is left for future work. The focus and contribution of this thesis is the design and elaboration of a language engineering discipline based on widely-spread state-based intuition of algorithms and programming. This approach opens the possibility to apply DSL technology in typical corporate environments, where the beneficial properties of smaller, and therefore by nature more secure and more focused computer languages are most leveraged. The thesis does not cover the equally important topic how to formalize these beneficial properties by means of declarative formalisms and how to apply mechanized reasoning and formal software engineering to DSLs. The thesis is structured in three parts. In the first part the requirements for a language engineering approach are analyzed and the language definition formalism Montages is introduced. In the second part the formal semantics and system architecture of Montages is given. The third part consists of a number of small example languages, each of them designed to show the Montages solution for specifying a well-known feature of main-stream object oriented programming languages such as Java. The single description modules of these example languages can be used to assemble a full object-oriented language, or a small subset of them can be combined with some high-level domain-specific features into a DSL. In the following we summarize for each part and its chapters their content and relation to each other.</p>
			</richtext>
		</abstract>
		<address type="sharef:placePublished">Zürich, Switzerland</address>
		<annotation type="bibtex:note">
			<richtext>
				<p>Diss. ETH No. 15421</p>
			</richtext>
		</annotation>
		<publisher type="sharef:university">ETH Zürich</publisher>
		<title type="sharef:primaryTitle">Montages — Engineering of Computer Languages</title>
		<identifier type="sharef:uri" resourceType="application/pdf">ftp://ftp.tik.ee.ethz.ch/pub/people/thiele/paper/KutterDiss.pdf</identifier>
		<howpublished>Ph.D. Thesis</howpublished>
	</reference>
	<reference name="roe05" src="bibtex:phdthesis" src-info="bibtex:line-22000" type="sharef:thesis">
		<names type="sharef:author">
			<person>
				<givenname>Kay</givenname>
				<surname>Römer</surname>
			</person>
		</names>
		<date value="2005"/>
		<abstract>
			<richtext>
				<p>So-called sensor nodes combine means for sensing environmental parameters, processors, wireless communication capabilities, and autonomous power supply in a single compact device. Networks of these untethered devices can be deployed unobtrusively in the physical environment in order to monitor a wide variety of real-world phenomena with unprecedented quality and scale while only marginally disturbing the observed physical processes. Due to the close integration of sensor networks with the real world, the categories time and location are fundamental for many applications of sensor networks, for example to interpret sensing results (e.g., where and when did an event occur) or for coordination among sensor nodes (e.g., which nodes can when be switched to idle mode). Hence, time synchronization and sensor node localization are fundamental and closely related services in sensor networks. Existing solutions for these two basic services have been based on a rather narrow notion of a sensor network as a large-scale, ad hoc, multi-hop, unpartitioned network of largely homogeneous, tiny, resource-constrained, mostly immobile sensor nodes that would be randomly deployed in the area of interest. However, recently developed prototypical applications indicate that this narrow definition does not cover a significant portion of the application domain of wireless sensor networks. Our thesis is that applications of sensor networks span a whole design space with many important dimensions. Existing solutions for time synchronization and node localization do not cover important parts of this design space. Substantially different approaches are required to support these regions adequately. Such solutions can actually be provided. We support this thesis by proposing a design space of wireless sensor networks where concrete applications can be located at different points of the space. We identify two important regions in the design space that are not appropriately supported by existing methods for time synchronization and node localization. We also propose, implement, and evaluate new solutions that cover these regions. The practical feasibility of our approaches is demonstrated by means of a typical sensor network application which requires time synchronization and node localization. Our approach to time synchronization supports applications where network connectivity is intermittent. The idea underlying our Time-Stamp Synchronization method is to avoid proactive synchronization of the clocks of all nodes in a network. Instead, the clocks of the sensor nodes run unsynchronized, each defining its own local time scale. Only if clock readings are exchanged among nodes as time stamps contained in network messages, these time stamps are transformed from the time scale of the sender to the time scale of the receiver. This approach is scalable, since time is only synchronized on demand where and when needed by the application. The approach is also resource efficient, since it piggybacks on existing message exchanges. Our approach to node localization supports tiny sensor nodes known as Smart Dust. The Lighthouse Location System is based on a single beacon device that emits particular optical signal patterns. Sensor nodes can autonomously infer their location by passively observing these signals. This approach is scalable, since each node infers its location independent of other nodes. A single beacon device emits long-range signals in broadcast mode and can support arbitrary network densities. The approach is resource efficient, since the sensor nodes do not actively emit any signals. Only a tiny, energy-efficient optical receiver is needed to infer locations.</p>
			</richtext>
		</abstract>
		<address type="sharef:placePublished">Zürich, Switzerland</address>
		<annotation type="bibtex:note">
			<richtext>
				<p>Diss. ETH No. 16106</p>
			</richtext>
		</annotation>
		<publisher type="sharef:university">ETH Zürich</publisher>
		<title type="sharef:primaryTitle">Time Synchronization and Localization in Sensor Networks</title>
		<identifier type="sharef:uri">http://e-collection.ethbib.ethz.ch/show?type=diss&amp;nr=16106</identifier>
		<identifier type="sharef:uri" resourceType="application/pdf">http://www.inf.ethz.ch/personal/roemer/papers/diss.pdf</identifier>
		<howpublished>Ph.D. Thesis</howpublished>
	</reference>
	<reference name="lan05" src="bibtex:phdthesis" src-info="bibtex:line-22012" type="sharef:thesis">
		<names type="sharef:author">
			<person>
				<givenname>Marc</givenname>
				<surname>Langheinrich</surname>
			</person>
		</names>
		<date value="2005"/>
		<abstract>
			<richtext>
				<p>Visions of future computing environments involve integrating tiny microelectronic processors and sensors into everyday objects in order to make them "smart." Smart things can explore their environment, communicate with other smart things, and interact with humans, therefore helping users to cope with their tasks in new, intuitive ways. However, this digitization of our everyday lives will not only allow computers to better "understand" our actions and goals, but also allow others to inspect and search such electronic records, potentially creating a comprehensive surveillance network of unprecedented scale. How should these developments affect our notion of privacy, our "right to be let alone," our freedom to determine for ourselves when, how, and to what extend information about us is communicated to others? Should we give up our solitude and anonymity in light of these new technological realities and create a "transparent society," in which nothing can be kept secret anymore, for better or for worse? Or do we need to surround ourselves with better security mechanisms that will make our communications and our presence untraceable to anyone but the most determined observer? This thesis argues for a third alternative, a middle ground between the two extremes of abandoning privacy and attempting full-scale anonymity. It proposes an architecture to facilitate the upfront notices of data collections in future computer environments, means to automatically process such announcements and individually configure the available collection parameters, processes to store and subsequently process any such collected data automatically according to the given notices, and tools for individuals to control and inspect their state of privacy in an ever connected world. In particular, this thesis provides for a method to announce privacy policies in smart environments via privacy beacons and personal privacy assistants, a method to reason and act upon such policies by automatically configuring the available services with the help of privacy proxies, and a method to store the collected information and enforce their respective collection and usage policies through privacy-aware databases. Taken together, these mechanisms can provide the technical foundations for future privacy frameworks that provide a level of privacy protection suitable for smart environments: anytime, anywhere, effortless privacy.</p>
			</richtext>
		</abstract>
		<address type="sharef:placePublished">Zürich, Switzerland</address>
		<annotation type="bibtex:note">
			<richtext>
				<p>Diss. ETH No. 16100</p>
			</richtext>
		</annotation>
		<publisher type="sharef:university">ETH Zürich</publisher>
		<title type="sharef:primaryTitle">Personal Privacy in Ubiquitous Computing: Tools and System Support</title>
		<identifier type="sharef:uri">http://e-collection.ethbib.ethz.ch/show?type=diss&amp;nr=16100</identifier>
		<identifier type="sharef:uri" resourceType="application/pdf">http://www.vs.inf.ethz.ch/publ/papers/langheinrich-phd-2005.pdf</identifier>
		<howpublished>Ph.D. Thesis</howpublished>
	</reference>
	<reference name="zih05" src="bibtex:phdthesis" src-info="bibtex:line-22024" type="sharef:thesis">
		<names type="sharef: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°. 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 ± 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 type="sharef:placePublished">Zürich, Switzerland</address>
		<annotation type="bibtex:note">
			<richtext>
				<p>Diss. ETH No. 16129</p>
			</richtext>
		</annotation>
		<publisher type="sharef:university">ETH Zürich</publisher>
		<title type="sharef:primaryTitle">Total Knee Arthroplasty: Biomechanical Reflections and Modelling, Based on Quantitative Movement Analysis</title>
		<identifier type="sharef:uri">http://e-collection.ethbib.ethz.ch/show?type=diss&amp;nr=16129</identifier>
		<howpublished>Ph.D. Thesis</howpublished>
	</reference>
	<reference name="beu05" src="bibtex:phdthesis" src-info="bibtex:line-22035" type="sharef:thesis">
		<names type="sharef:author">
			<person>
				<givenname>Jan</givenname>
				<surname>Beutel</surname>
			</person>
		</names>
		<date value="2005-08"/>
		<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 type="sharef:placePublished">Zürich, Switzerland</address>
		<identifier type="sharef: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="sharef:university">ETH Zürich</publisher>
		<title type="sharef:primaryTitle">Design and Deployment of Wireless Networked Embedded Systems</title>
		<identifier type="sharef:uri">http://e-collection.ethbib.ethz.ch/show?type=diss&amp;nr=16204</identifier>
		<identifier type="sharef:uri" resourceType="application/pdf">ftp://ftp.tik.ee.ethz.ch/pub/people/thiele/paper/diss_beutel.pdf</identifier>
		<howpublished>Ph.D. Thesis</howpublished>
	</reference>
	<reference name="mei05" src="bibtex:phdthesis" src-info="bibtex:line-22050" type="sharef:thesis">
		<names type="sharef:author">
			<person>
				<givenname>Lennart</givenname>
				<surname>Meier</surname>
			</person>
		</names>
		<date value="2005-12"/>
		<abstract>
			<richtext>
				<p>In this thesis, we make a case for the use of guaranteed intervals for time synchronization in mobile ad-hoc networks. In particular, we look at wireless sensor networks (WSNs), a specific class of mobile ad-hoc networks. WSNs are envisioned to comprise a large number of small, inexpensive devices that operate on a very constrained energy budget. Time synchronization is an important service in WSNs. Approaches developed in the distributed-systems field typically cannot be applied directly because of the limiting characteristics of WSNs: (a) There is no guarantee of stable connectivity between nodes. (b) Energy is a very scarce resource. Communication, which is needed to achieve and maintain synchronization, is expensive in terms of energy and hence has to be kept short. (c) Communication bandwidth is limited. (d) There is no a-priori configuration or infrastructure. In particular, there are few or even no reference clocks available. In this thesis, we make a number of contributions to the state of the art in the field of time synchronization for mobile ad-hoc networks. Our main claim is that interval-based time synchronization is particularly suited for these networks. Specifically, our contributions are the following: We present a new system model for the analysis of interval-based time synchronization in mobile ad-hoc networks. We justify why our abstractions are well chosen for this class of networks. Using our system model, we derive worst-case bounds on the quality of interval-based synchronization and show the worst-case-optimality of a very simple algorithm. The simple, worst-case-optimal algorithm is not optimal in the average case. We present three algorithms that are also worst-case-optimal but achieve better synchronization quality in the average case.We show that two of the algorithms achieve optimal synchronization, albeit at the cost of high memory and communication overhead. We describe how limiting the amount of data that is stored and communicated affects the synchronization quality. We show that interval-based synchronization does not need particular communication patterns such as trees or clustered hierarchies. Hence, interval-based synchronization is resilient to mobility; our simulation results show that mobility actually improves it. Finally, we derive a lower bound on the error of gradient clock synchronization in our system model.</p>
			</richtext>
		</abstract>
		<address type="sharef:placePublished">Zürich, Switzerland</address>
		<annotation type="bibtex:note">
			<richtext>
				<p>Diss. ETH No. 16435</p>
			</richtext>
		</annotation>
		<publisher type="sharef:university">ETH Zürich</publisher>
		<title type="sharef:primaryTitle">Interval-Based Time Synchronization for Mobile Ad-Hoc Networks</title>
		<identifier type="sharef:uri">http://e-collection.ethbib.ethz.ch/show?type=diss&amp;nr=16435</identifier>
		<identifier type="sharef:uri" resourceType="application/pdf">ftp://ftp.tik.ee.ethz.ch/pub/people/thiele/paper/diss_meier.pdf</identifier>
		<howpublished>Ph.D. Thesis</howpublished>
	</reference>
	<reference name="gre05" src="bibtex:phdthesis" src-info="bibtex:line-22063" type="sharef:thesis">
		<names type="sharef: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β 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β peptide and has been reported to protect neurons against Aβ 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 type="sharef:placePublished">Zürich, Switzerland</address>
		<annotation type="bibtex:note">
			<richtext>
				<p>Diss. ETH No. 16263</p>
			</richtext>
		</annotation>
		<publisher type="sharef:university">ETH Zürich</publisher>
		<title type="sharef:primaryTitle">A Proteomics Approach to the Diagnosis of Alzheimer's Disease</title>
		<identifier type="sharef:uri">http://e-collection.ethbib.ethz.ch/show?type=diss&amp;nr=16263</identifier>
		<howpublished>Ph.D. Thesis</howpublished>
	</reference>
	<reference name="kas07" src="bibtex:phdthesis" src-info="bibtex:line-22075" type="sharef:thesis">
		<names type="sharef:author">
			<person>
				<givenname>Oliver</givenname>
				<surname>Kasten</surname>
			</person>
		</names>
		<date value="2007"/>
		<abstract>
			<richtext>
				<p>Sensor nodes are small, inexpensive, and programmable devices that combine an autonomous power supply with computing, sensing, and wireless communication capabilities. Networks of sensor nodes can be deployed in the environment at a large scale to unobtrusively monitor phenomena of the real world. Wireless sensor networks are an emerging field of research with many potential applications. So far, however, only few applications have actually been realized. This is in part due to the lack of appropriate programming support, which makes the development of sensor-network applications tedious and error prone. This dissertation contributes a novel programming model and development environment for the efficient, modular, and well structured programming of wireless sensor nodes. Today there are two principal programming models used for sensor nodes, the multi-threaded model and the event-driven model. The multi-threaded model requires system support that is often considered too heavy for sensor nodes that operate at the low end of the resource spectrum. To cope with this issue, the event-driven model has been proposed. It requires very little runtime support by the system software and can thus be implemented even on the most constrained sensor nodes. The simple and lightweight approach to system software, however, tends to make event-driven applications in turn quite memory inefficient: Since the event-driven model limits the use of local variables, programmers need to store temporary data in global variables. The memory of global variables, however, cannot easily and automatically be reused, hence the memory inefficiency. To counter this effect, programmers can resort to manual memory management, though this significantly affects program correctness and code modularity. In addition to its drawback of memory inefficiency, event-driven programming requires developers to manually keep track of the current program-state, which makes code modularization and debugging difficult, and leads to unstructured code. The key contribution of this dissertation is to show that the inadequacies of the event-driven model can be remedied without impairing its positive aspects, particularly its memory-efficient realization in sensor-node system software. Concretely, we present the Object State Model (OSM), a programming model that extends the event-driven programming paradigm with a notion of hierarchical and concurrent program states. Our thesis is that such a state-based model allows to specify well-structured, modular, and memory-efficient programs, yet requires as few runtime-resources as the event-driven model. To support this claim, we also present a programming environment based on the OSM model (including a programming language and compiler), as well as a sensor-node operating system capable of executing OSM programs. The main idea behind OSM is to explicitly model sensor-node programs as state machines, where variables are associated with states and computational operations are associated with state transitions. In OSM, states serve three purposes. Firstly, states are used as scoping mechanism for variables. The scope and lifetime of variables attached to a state is confined to that state and all of its substates. The memory for storing a state's variables is automatically reclaimed by the runtime system as the program leaves the corresponding state. State variables can be thought of as the local variables of OSM. As such they represent a great advancement over event-driven programming, where the majority of variables effectively have global scope and lifetime. By modeling temporary data with state variables, the use of OSM can significantly increase a program's memory efficiency. Secondly, the explicit notion of program states allows to model the structure and control flow of a program on a high abstraction level. Specifically, programs can be initially specified in terms of coarse modules (i.e., states), which can be subsequently refined (with substates), leading to modular and readable program code. The third purpose of states is to provide a context for computational operations. States clearly define which variables are visible, and at what point in the control flow the program resides when an operation is executed. In the event-driven model, in contrast, the program's context has to be maintained manually, which typically constitutes a significant fraction of the code, thus making the program hard to read and error prone. The OSM programming language captures the three concepts described above in order to foster memory efficient, modular, and well-structured programs. A compiler for the proposed language transforms state-based OSM programs back into an event-driven program notation, adding code for automatic memory management of state variables and code for automatic control-flow management. The compiler-generated code is very lean and does not impose additional requirements on the system software, such as dynamic memory management. Rather, the transformed programs are directly executable on our event-driven system software for resource-constrained sensor nodes. Our language, compiler, and sensor-node system software form the basis of our thesis and constitute a complete state-based programming environment for resource-constrained sensor nodes based on OSM.</p>
			</richtext>
		</abstract>
		<address type="sharef:placePublished">Zürich, Switzerland</address>
		<annotation type="bibtex:note">
			<richtext>
				<p>Diss. ETH No. 17397</p>
			</richtext>
		</annotation>
		<publisher type="sharef:university">ETH Zürich</publisher>
		<title type="sharef:primaryTitle">A State-Based Programming Model for Wireless Sensor Networks</title>
		<identifier type="sharef:uri">http://e-collection.ethbib.ethz.ch/show?type=diss&amp;nr=17397</identifier>
		<howpublished>Ph.D. Thesis</howpublished>
	</reference>
	<reference name="ste06" src="bibtex:mastersthesis" src-info="bibtex:line-22090" type="sharef:thesis">
		<names type="sharef: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 type="sharef:placePublished">Rostock, Germany</address>
		<publisher type="sharef:university">Universität Rostock</publisher>
		<title type="sharef:primaryTitle">Entwicklung und Implementierung einer Methode zum konzeptionellen Entwurf von XML-Schemata</title>
		<field type="bibtex:topic">emx[1]</field>
		<identifier type="sharef:uri">http://dbis.informatik.uni-rostock.de/Studium/Diplomarbeiten/1124106344.13_0</identifier>
		<howpublished>Master's Thesis</howpublished>
	</reference>
	<reference name="han02" src="bibtex:mastersthesis" src-info="bibtex:line-22102" type="sharef:thesis">
		<names type="sharef:author">
			<person>
				<givenname>Arne</givenname>
				<surname>Handt</surname>
			</person>
		</names>
		<date value="2002-08"/>
		<address type="sharef:placePublished">Berlin, Germany</address>
		<publisher type="sharef:university">Institut für Softwaretechnik und Theoretische Informatik, Technische Universität Berlin</publisher>
		<title type="sharef:primaryTitle">A Transformation System for XML-based Messaging Channels</title>
		<howpublished>Master's Thesis</howpublished>
	</reference>
	<reference name="wil91a" src="bibtex:mastersthesis" src-info="bibtex:line-22111" type="sharef:thesis">
		<names type="sharef:author">
			<person>
				<givenname>Erik</givenname>
				<surname>Wilde</surname>
			</person>
		</names>
		<date value="1991-05"/>
		<address type="sharef:placePublished">Berlin, Germany</address>
		<publisher type="sharef:university">Open Communication Systems Group, Technical University Berlin</publisher>
		<title type="sharef:primaryTitle">Distributed Multimedia Documents</title>
		<identifier type="sharef:uri">http://dret.net/netdret/publications#wil91a</identifier>
		<howpublished>Master's Thesis</howpublished>
	</reference>
	<reference name="alm92" src="bibtex:mastersthesis" src-info="bibtex:line-22121" type="sharef:thesis">
		<names type="sharef:author">
			<person>
				<givenname>Werner</givenname>
				<surname>Almesberger</surname>
			</person>
			<person>
				<givenname>Markus</givenname>
				<surname>Wild</surname>
			</person>
		</names>
		<date value="1992-08"/>
		<address type="sharef:placePublished">Zürich, Switzerland</address>
		<publisher type="sharef:university">Computer Engineering and Networks Laboratory, ETH Zürich</publisher>
		<title type="sharef:primaryTitle">Entwurf und Teilimplementierung eines verteilten, multimediafähigen Editors</title>
		<identifier type="sharef:uri">http://dret.net/netdret/cv#alm92</identifier>
		<howpublished>Master's Thesis</howpublished>
	</reference>
	<reference name="bau93" src="bibtex:mastersthesis" src-info="bibtex:line-22131" type="sharef:thesis">
		<names type="sharef:author">
			<person>
				<givenname>Daniel</givenname>
				<surname>Bauer</surname>
			</person>
		</names>
		<date value="1993-03"/>
		<address type="sharef:placePublished">Zürich, Switzerland</address>
		<publisher type="sharef:university">Computer Engineering and Networks Laboratory, ETH Zürich</publisher>
		<title type="sharef:primaryTitle">Erweiterung eines verteilten, multimedialen Editors</title>
		<identifier type="sharef:uri">http://dret.net/netdret/cv#bau93</identifier>
		<howpublished>Master's Thesis</howpublished>
	</reference>
	<reference name="das94" src="bibtex:mastersthesis" src-info="bibtex:line-22141" type="sharef:thesis">
		<names type="sharef:author">
			<person>
				<givenname>Marcel</givenname>
				<surname>Dasen</surname>
			</person>
		</names>
		<date value="1994-08"/>
		<address type="sharef:placePublished">Zürich, Switzerland</address>
		<publisher type="sharef:university">Computer Engineering and Networks Laboratory, ETH Zürich</publisher>
		<title type="sharef:primaryTitle">Rekonfiguration von Protokollen in Da CaPo</title>
		<identifier type="sharef:uri">http://dret.net/netdret/cv#das94</identifier>
		<howpublished>Master's Thesis</howpublished>
	</reference>
	<reference name="rue93" src="bibtex:mastersthesis" src-info="bibtex:line-22151" type="sharef:thesis">
		<names type="sharef:author">
			<person>
				<givenname>Niklaus</givenname>
				<surname>Ruess</surname>
			</person>
		</names>
		<date value="1993-03"/>
		<address type="sharef:placePublished">Zürich, Switzerland</address>
		<publisher type="sharef:university">Computer Engineering and Networks Laboratory, ETH Zürich</publisher>
		<title type="sharef:primaryTitle">Realisierung eines RTF-Andrew-Konverters</title>
		<identifier type="sharef:uri">http://dret.net/netdret/cv#rue93</identifier>
		<howpublished>Master's Thesis</howpublished>
	</reference>
	<reference name="kel96" src="bibtex:mastersthesis" src-info="bibtex:line-22161" type="sharef:thesis">
		<names type="sharef:author">
			<person>
				<givenname>Ralph</givenname>
				<surname>Keller</surname>
			</person>
		</names>
		<date value="1996-08"/>
		<address type="sharef:placePublished">Zürich, Switzerland</address>
		<publisher type="sharef:university">Computer Engineering and Networks Laboratory, ETH Zürich</publisher>
		<title type="sharef:primaryTitle">Multipoint Communication Framework (MCF): Entwicklung eines Transportsubsystems</title>
		<identifier type="sharef:uri">http://dret.net/netdret/cv#kel96</identifier>
		<howpublished>Master's Thesis</howpublished>
	</reference>
	<reference name="nan96" src="bibtex:mastersthesis" src-info="bibtex:line-22171" type="sharef:thesis">
		<names type="sharef:author">
			<person>
				<givenname>Murali</givenname>
				<surname>Nanduri</surname>
			</person>
		</names>
		<date value="1996-03"/>
		<address type="sharef:placePublished">Zürich, Switzerland</address>
		<field type="bibtex:index">GMS, GUA, GAP</field>
		<publisher type="sharef:university">Computer Engineering and Networks Laboratory, ETH Zürich</publisher>
		<title type="sharef:primaryTitle">Namensverwaltung, Adressierung und Verbindungsaufbau für Gruppenkommunikation im Group and Session Management System (GMS)</title>
		<identifier type="sharef:uri">http://dret.net/netdret/cv#nan96</identifier>
		<howpublished>Master's Thesis</howpublished>
	</reference>
	<reference name="fre96" src="bibtex:mastersthesis" src-info="bibtex:line-22182" type="sharef:thesis">
		<names type="sharef:author">
			<person>
				<givenname>Pascal</givenname>
				<surname>Freiburghaus</surname>
			</person>
		</names>
		<date value="1996-09"/>
		<address type="sharef:placePublished">Zürich, Switzerland</address>
		<field type="bibtex:index">GMS, GSA, GSP</field>
		<publisher type="sharef:university">Computer Engineering and Networks Laboratory, ETH Zürich</publisher>
		<title type="sharef:primaryTitle">System-Protokollarchitektur für das Group and Session Management System</title>
		<identifier type="sharef:uri">http://dret.net/netdret/cv#fre96</identifier>
		<howpublished>Master's Thesis</howpublished>
	</reference>
	<reference name="kol96" src="bibtex:mastersthesis" src-info="bibtex:line-22193" type="sharef:thesis">
		<names type="sharef:author">
			<person>
				<givenname>Daniel</givenname>
				<surname>Koller</surname>
			</person>
		</names>
		<date value="1996-09"/>
		<address type="sharef:placePublished">Zürich, Switzerland</address>
		<field type="bibtex:index">GMS, GSA, GSP</field>
		<publisher type="sharef:university">Computer Engineering and Networks Laboratory, ETH Zürich</publisher>
		<title type="sharef:primaryTitle">System-Protokolloperationen für das Group and Session Management System</title>
		<identifier type="sharef:uri">http://dret.net/netdret/cv#kol96</identifier>
		<howpublished>Master's Thesis</howpublished>
	</reference>
	<reference name="bue97" src="bibtex:mastersthesis" src-info="bibtex:line-22204" type="sharef:thesis">
		<names type="sharef:author">
			<person>
				<givenname>Markus</givenname>
				<surname>Buechi</surname>
			</person>
		</names>
		<date value="1997-03"/>
		<address type="sharef:placePublished">Zürich, Switzerland</address>
		<field type="bibtex:index">GMS, GUA, Da CaPo</field>
		<publisher type="sharef:university">Computer Engineering and Networks Laboratory, ETH Zürich</publisher>
		<title type="sharef:primaryTitle">Entwurf und Implementierung einer Multicastunterstützung für Multimedia-Anwendungen</title>
		<howpublished>Master's Thesis</howpublished>
	</reference>
	<reference name="nig96" src="bibtex:mastersthesis" src-info="bibtex:line-22214" type="sharef:thesis">
		<names type="sharef:author">
			<person>
				<givenname>Gerhard</givenname>
				<surname>Nigg</surname>
			</person>
		</names>
		<date value="1996-03"/>
		<address type="sharef:placePublished">Zürich, Switzerland</address>
		<field type="bibtex:index">Da CaPo, multicast</field>
		<publisher type="sharef:university">Computer Engineering and Networks Laboratory, ETH Zürich</publisher>
		<title type="sharef:primaryTitle">Multicast-Module für Da CaPo</title>
		<howpublished>Master's Thesis</howpublished>
	</reference>
	<reference name="car93" src="bibtex:mastersthesis" src-info="bibtex:line-22224" type="sharef:thesis">
		<names type="sharef:author">
			<person>
				<givenname>Germano</givenname>
				<surname>Caronni</surname>
			</person>
		</names>
		<date value="1993-02"/>
		<address type="sharef:placePublished">Zürich, Switzerland</address>
		<publisher type="sharef:university">Computer Engineering and Networks Laboratory, ETH Zürich</publisher>
		<title type="sharef:primaryTitle">Konzeption und Entwicklung einer Komponente zur Dokumentenverwaltung</title>
		<identifier type="sharef:uri">http://dret.net/netdret/cv#car93</identifier>
		<howpublished>Master's Thesis</howpublished>
	</reference>
	<reference name="sel86" src="bibtex:mastersthesis" src-info="bibtex:line-22234" type="sharef:thesis">
		<names type="sharef:author">
			<person>
				<givenname>Robert</givenname>
				<surname>Seliger</surname>
			</person>
		</names>
		<date value="1986-01"/>
		<address type="sharef:placePublished">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="sharef:university">Massachusetts Institute of Technology</publisher>
		<title type="sharef:primaryTitle">Design and Implementation of a Distributed Program for Collaborative Editing</title>
		<howpublished>Master's Thesis</howpublished>
	</reference>
	<reference name="bos03" src="bibtex:mastersthesis" src-info="bibtex:line-22245" type="sharef:thesis">
		<names type="sharef:author">
			<person>
				<givenname>Alain C.</givenname>
				<surname>Boss</surname>
			</person>
		</names>
		<date value="2003-05"/>
		<address type="sharef:placePublished">Berne, Switzerland</address>
		<publisher type="sharef:university">Eduswiss</publisher>
		<title type="sharef:primaryTitle">SBA Ranking</title>
		<identifier type="sharef:uri">http://dret.net/netdret/cv#bos03</identifier>
		<howpublished>Master's Thesis</howpublished>
	</reference>
	<reference name="nab05" src="bibtex:mastersthesis" src-info="bibtex:line-22255" type="sharef:thesis">
		<names type="sharef:author">
			<person>
				<givenname>Nick</givenname>
				<surname>Nabholz</surname>
			</person>
		</names>
		<date value="2005-06"/>
		<address type="sharef:placePublished">Zürich, Switzerland</address>
		<publisher type="sharef:university">Hochschule für Technik, Wirtschaft und Verwaltung Zürich</publisher>
		<title type="sharef:primaryTitle">Ein Benutzerkonzept für kollaborative Applikationen am Beispiel von ShaRef</title>
		<identifier type="sharef:uri">http://dret.net/netdret/cv#nab05</identifier>
		<howpublished>Master's Thesis</howpublished>
	</reference>
	<reference name="bue05" src="bibtex:mastersthesis" src-info="bibtex:line-22265" type="sharef:thesis">
		<names type="sharef:author">
			<person>
				<givenname>Thierry</givenname>
				<surname>Bücheler</surname>
			</person>
		</names>
		<date value="2005-10"/>
		<address type="sharef:placePublished">Zürich, Switzerland</address>
		<publisher type="sharef:university">Computer Engineering and Networks Laboratory, ETH Zürich</publisher>
		<title type="sharef:primaryTitle">ShaRefWeb: A Web Interface for the ShaRef Service</title>
		<identifier type="sharef:uri">http://dret.net/netdret/cv#bue05</identifier>
		<howpublished>Master's Thesis</howpublished>
	</reference>
	<reference name="sin00" src="bibtex:mastersthesis" src-info="bibtex:line-22275" type="sharef:thesis">
		<names type="sharef:author">
			<person>
				<givenname>Felix</givenname>
				<surname>Singeisen</surname>
			</person>
		</names>
		<date value="2000-08"/>
		<address type="sharef:placePublished">Berne, Switzerland</address>
		<publisher type="sharef:university">Eduswiss</publisher>
		<title type="sharef:primaryTitle">Messkriterien zur qualitativen Beurteilung von WAP-Services basierend auf verschiedenen Trägerdiensten</title>
		<identifier type="sharef:uri">http://dret.net/netdret/cv#sin00</identifier>
		<howpublished>Master's Thesis</howpublished>
	</reference>
	<reference name="kue01" src="bibtex:mastersthesis" src-info="bibtex:line-22285" type="sharef:thesis">
		<names type="sharef:author">
			<person>
				<givenname>Simon</givenname>
				<surname>Künzli</surname>
			</person>
			<person>
				<givenname>Peter</givenname>
				<surname>Zberg</surname>
			</person>
		</names>
		<date value="2001-03"/>
		<address type="sharef:placePublished">Zürich, Switzerland</address>
		<publisher type="sharef:university">Computer Engineering and Networks Laboratory, ETH Zürich</publisher>
		<title type="sharef:primaryTitle">Design und Implementierung einer Benutzerschnittstelle für den XLinkbase-Zugriff</title>
		<identifier type="sharef:uri">http://dret.net/netdret/cv#kue01</identifier>
		<howpublished>Master's Thesis</howpublished>
	</reference>
	<reference name="lur01" src="bibtex:mastersthesis" src-info="bibtex:line-22295" type="sharef:thesis">
		<names type="sharef:author">
			<person>
				<givenname>Brenno</givenname>
				<surname>Lurati</surname>
			</person>
			<person>
				<givenname>Luca</givenname>
				<surname>Previtali</surname>
			</person>
		</names>
		<date value="2001-03"/>
		<address type="sharef:placePublished">Zürich, Switzerland</address>
		<publisher type="sharef:university">Computer Engineering and Networks Laboratory, ETH Zürich</publisher>
		<title type="sharef:primaryTitle">BibTeXML: Design und Implementierung einer XML-basierten Lösung für BibTeX Literaturreferenzen</title>
		<identifier type="sharef:uri">http://dret.net/netdret/cv#lur01</identifier>
		<howpublished>Master's Thesis</howpublished>
	</reference>
	<reference name="lan01" src="bibtex:mastersthesis" src-info="bibtex:line-22305" type="sharef:thesis">
		<names type="sharef:author">
			<person>
				<givenname>Yves</givenname>
				<surname>Langisch</surname>
			</person>
		</names>
		<date value="2001-03"/>
		<address type="sharef:placePublished">Zürich, Switzerland</address>
		<publisher type="sharef:university">Computer Engineering and Networks Laboratory, ETH Zürich</publisher>
		<title type="sharef:primaryTitle">Design und Implementierung von XLinkbase, einer XML-basierten Datenbank für Ressourcen-Information und ihre Kategorisierung</title>
		<identifier type="sharef:uri">http://dret.net/netdret/cv#lan01</identifier>
		<howpublished>Master's Thesis</howpublished>
	</reference>
	<reference name="dob00" src="bibtex:mastersthesis" src-info="bibtex:line-22315" type="sharef:thesis">
		<names type="sharef:author">
			<person>
				<givenname>Dario</givenname>
				<surname>Dobranic</surname>
			</person>
			<person>
				<givenname>Eric</givenname>
				<surname>Schreiber</surname>
			</person>
		</names>
		<date value="2000-08"/>
		<address type="sharef:placePublished">Zürich, Switzerland</address>
		<publisher type="sharef:university">Computer Engineering and Networks Laboratory, ETH Zürich</publisher>
		<title type="sharef:primaryTitle">Konzept und Implementierung für einen XML- und SQL-basierten Web-Server für Weiterbildungsangebote</title>
		<identifier type="sharef:uri">http://dret.net/netdret/cv#dob00</identifier>
		<howpublished>Master's Thesis</howpublished>
	</reference>
	<reference name="obe01" src="bibtex:mastersthesis" src-info="bibtex:line-22325" type="sharef:thesis">
		<names type="sharef:author">
			<person>
				<givenname>Glenn</givenname>
				<surname>Oberholzer</surname>
			</person>
		</names>
		<date value="2001-02"/>
		<address type="sharef:placePublished">Zürich, Switzerland</address>
		<publisher type="sharef:university">Computer Engineering and Networks Laboratory, ETH Zürich</publisher>
		<title type="sharef:primaryTitle">Design und Usability-Konzepte für die DHTML-basierte Präsentation von XLinks</title>
		<identifier type="sharef:uri">http://dret.net/netdret/cv#obe01</identifier>
		<howpublished>Master's Thesis</howpublished>
	</reference>
	<reference name="amr01" src="bibtex:mastersthesis" src-info="bibtex:line-22335" type="sharef:thesis">
		<names type="sharef:author">
			<person>
				<givenname>Marco</givenname>
				<surname>Amrein</surname>
			</person>
		</names>
		<date value="2001-02"/>
		<address type="sharef:placePublished">Zürich, Switzerland</address>
		<publisher type="sharef:university">Computer Engineering and Networks Laboratory, ETH Zürich</publisher>
		<title type="sharef:primaryTitle">Konzept und Design für ein XLinkbase-Schema für Nachschlagewerke sowie ihre Präsentation</title>
		<identifier type="sharef:uri">http://dret.net/netdret/cv#amr01</identifier>
		<howpublished>Master's Thesis</howpublished>
	</reference>
	<reference name="kar01a" src="bibtex:mastersthesis" src-info="bibtex:line-22345" type="sharef:thesis">
		<names type="sharef:author">
			<person>
				<givenname>Alexander</givenname>
				<surname>Karg</surname>
			</person>
		</names>
		<date value="2001-02"/>
		<address type="sharef:placePublished">Zürich, Switzerland</address>
		<publisher type="sharef:university">Computer Engineering and Networks Laboratory, ETH Zürich</publisher>
		<title type="sharef:primaryTitle">Konzept und Design für ein XLinkbase-Schema für Bildarchive sowie ihrer Präsentation</title>
		<identifier type="sharef:uri">http://dret.net/netdret/cv#kar01a</identifier>
		<howpublished>Master's Thesis</howpublished>
	</reference>
	<reference name="kar01b" src="bibtex:mastersthesis" src-info="bibtex:line-22355" type="sharef:thesis">
		<names type="sharef:author">
			<person>
				<givenname>Alexander</givenname>
				<surname>Karg</surname>
			</person>
		</names>
		<date value="2001-08"/>
		<address type="sharef:placePublished">Zürich, Switzerland</address>
		<publisher type="sharef:university">Computer Engineering and Networks Laboratory, ETH Zürich</publisher>
		<title type="sharef:primaryTitle">Konzept und Implementierung eines Programmes für die Bildarchivierung und -verwaltung</title>
		<identifier type="sharef:uri">http://dret.net/netdret/cv#kar01b</identifier>
		<howpublished>Master's Thesis</howpublished>
	</reference>
	<reference name="bas05" src="bibtex:mastersthesis" src-info="bibtex:line-22365" type="sharef:thesis">
		<names type="sharef:author">
			<person>
				<givenname>Marcel</givenname>
				<surname>Baschnagel</surname>
			</person>
		</names>
		<date value="2005-07"/>
		<address type="sharef:placePublished">Zürich, Switzerland</address>
		<publisher type="sharef:university">Computer Engineering and Networks Laboratory, ETH Zürich</publisher>
		<title type="sharef:primaryTitle">Fragment Identifiers für den text/plain MIME Type</title>
		<identifier type="sharef:uri">http://dret.net/netdret/cv#bas05</identifier>
		<howpublished>Master's Thesis</howpublished>
	</reference>
	<reference name="gig06" src="bibtex:mastersthesis" src-info="bibtex:line-22374" type="sharef:thesis">
		<names type="sharef:author">
			<person>
				<givenname>Kaspar</givenname>
				<surname>Giger</surname>
			</person>
		</names>
		<date value="2006-04"/>
		<address type="sharef:placePublished">Zürich, Switzerland</address>
		<publisher type="sharef:university">Computer Engineering and Networks Laboratory, ETH Zürich</publisher>
		<title type="sharef:primaryTitle">XPath-Unterstützung in einer Linux Shell</title>
		<field type="bibtex:topic">xpsh[1]</field>
		<identifier type="sharef:uri">http://dret.net/netdret/cv#gig06</identifier>
		<howpublished>Master's Thesis</howpublished>
	</reference>
	<reference name="mic07" src="bibtex:mastersthesis" src-info="bibtex:line-22384" type="sharef:thesis">
		<names type="sharef:author">
			<person>
				<givenname>Felix</givenname>
				<surname>Michel</surname>
			</person>
		</names>
		<date value="2007-03"/>
		<address type="sharef:placePublished">Zürich, Switzerland</address>
		<publisher type="sharef:university">Computer Engineering and Networks Laboratory, ETH Zürich</publisher>
		<title type="sharef:primaryTitle">Representation of XML Schema Components</title>
		<field type="bibtex:topic">xsd[0.8]</field>
		<identifier type="sharef:uri">http://dret.net/netdret/cv#mic07</identifier>
		<howpublished>Master's Thesis</howpublished>
	</reference>
	<reference name="fei03" src="bibtex:mastersthesis" src-info="bibtex:line-22394" type="sharef:thesis">
		<names type="sharef:author">
			<person>
				<givenname>Michael</givenname>
				<surname>Feierabend</surname>
			</person>
			<person>
				<givenname>Thomas</givenname>
				<surname>Hägi</surname>
			</person>
		</names>
		<date value="2003-07"/>
		<address type="sharef:placePublished">Zürich, Switzerland</address>
		<publisher type="sharef:university">Computer Engineering and Networks Laboratory, ETH Zürich</publisher>
		<title type="sharef:primaryTitle">Aufbau und Betrieb eines Konferenzplanungssystems für die WWW2003</title>
		<identifier type="sharef:uri">http://dret.net/netdret/cv#fei03</identifier>
		<howpublished>Master's Thesis</howpublished>
	</reference>
	<reference name="gam01" src="bibtex:mastersthesis" src-info="bibtex:line-22404" type="sharef:thesis">
		<names type="sharef:author">
			<person>
				<givenname>Sascha</givenname>
				<surname>Gammaidoni</surname>
			</person>
			<person>
				<givenname>Christian</givenname>
				<surname>Mutti</surname>
			</person>
		</names>
		<date value="2001-08"/>
		<address type="sharef:placePublished">Zürich, Switzerland</address>
		<publisher type="sharef:university">Computer Engineering and Networks Laboratory, ETH Zürich</publisher>
		<title type="sharef:primaryTitle">Überabeitung und weiterer Aufbau des Servers und der Software für das BibTeXML-Projekt</title>
		<field type="bibtex:topic">bibtexml[0.9]</field>
		<identifier type="sharef:uri">http://dret.net/netdret/cv#gam01</identifier>
		<howpublished>Master's Thesis</howpublished>
	</reference>
	<reference name="mey01" src="bibtex:mastersthesis" src-info="bibtex:line-22415" type="sharef:thesis">
		<names type="sharef:author">
			<person>
				<givenname>Manfred</givenname>
				<surname>Meyer</surname>
			</person>
		</names>
		<date value="2001-08"/>
		<address type="sharef:placePublished">Zürich, Switzerland</address>
		<publisher type="sharef:university">Computer Engineering and Networks Laboratory, ETH Zürich</publisher>
		<title type="sharef:primaryTitle">Design und Implementierung eines Frameworks für das Message Routing &amp; Passing in einem EJB-basierten Server</title>
		<identifier type="sharef:uri">http://dret.net/netdret/cv#mey01</identifier>
		<howpublished>Master's Thesis</howpublished>
	</reference>
	<reference name="sti02" src="bibtex:mastersthesis" src-info="bibtex:line-22425" type="sharef:thesis">
		<names type="sharef:author">
			<person>
				<givenname>Christian</givenname>
				<surname>Stillhard</surname>
			</person>
		</names>
		<date value="2002-03"/>
		<address type="sharef:placePublished">Zürich, Switzerland</address>
		<publisher type="sharef:university">Computer Engineering and Networks Laboratory, ETH Zürich</publisher>
		<title type="sharef:primaryTitle">Methods for Accessing Linkbases</title>
		<identifier type="sharef:uri">http://dret.net/netdret/cv#sti02</identifier>
		<howpublished>Master's Thesis</howpublished>
	</reference>
	<reference name="sti03" src="bibtex:mastersthesis" src-info="bibtex:line-22435" type="sharef:thesis">
		<names type="sharef:author">
			<person>
				<givenname>Kilian</givenname>
				<surname>Stillhard</surname>
			</person>
		</names>
		<date value="2003-03"/>
		<address type="sharef:placePublished">Zürich, Switzerland</address>
		<publisher type="sharef:university">Computer Engineering and Networks Laboratory, ETH Zürich</publisher>
		<title type="sharef:primaryTitle">A Compact Syntax for XML Schema</title>
		<identifier type="sharef:uri">http://dret.net/netdret/cv#sti03</identifier>
		<howpublished>Master's Thesis</howpublished>
	</reference>
	<reference name="hau03" src="bibtex:mastersthesis" src-info="bibtex:line-22445" type="sharef:thesis">
		<names type="sharef:author">
			<person>
				<givenname>Felix</givenname>
				<surname>Hauser</surname>
			</person>
			<person>
				<givenname>Philip</givenname>
				<surname>Schaffhauser</surname>
			</person>
		</names>
		<date value="2003-03"/>
		<address type="sharef:placePublished">Zürich, Switzerland</address>
		<publisher type="sharef:university">Computer Engineering and Networks Laboratory, ETH Zürich</publisher>
		<title type="sharef:primaryTitle">Database-Driven XML-Enabled Bibliography Management System</title>
		<identifier type="sharef:uri">http://dret.net/netdret/cv#hau03</identifier>
		<howpublished>Master's Thesis</howpublished>
	</reference>
	<reference name="kra03" src="bibtex:mastersthesis" src-info="bibtex:line-22455" type="sharef:thesis">
		<names type="sharef:author">
			<person>
				<givenname>Beat</givenname>
				<surname>Krähenmann</surname>
			</person>
			<person>
				<givenname>Martin</givenname>
				<surname>Waldburger</surname>
			</person>
		</names>
		<date value="2003-03"/>
		<address type="sharef:placePublished">Zürich, Switzerland</address>
		<publisher type="sharef:university">Computer Engineering and Networks Laboratory, ETH Zürich</publisher>
		<title type="sharef:primaryTitle">Toolkit für Konferenzprogrammverwaltung und -personalisierung</title>
		<identifier type="sharef:uri">http://dret.net/netdret/cv#kra03</identifier>
		<howpublished>Master's Thesis</howpublished>
	</reference>
	<reference name="dce" src="bibtex:manual" src-info="bibtex:line-22469" type="sharef:manual">
		<date value="1997-11"/>
		<address type="sharef:placePublished">Cambridge, Massachusetts</address>
		<organization>The Open Group</organization>
		<title type="sharef:primaryTitle">DCE 1.2.2 Documentation</title>
		<field type="bibtex:topic">dce[1]</field>
	</reference>
	<reference name="truetype" src="bibtex:manual" src-info="bibtex:line-22478" type="sharef:manual">
		<date value="1996-10"/>
		<address type="sharef:placePublished">Cupertino, California</address>
		<organization>Apple Computer, Inc.</organization>
		<title type="sharef:primaryTitle">The TrueType Reference Manual</title>
		<field type="bibtex:topic">truetype[1]</field>
	</reference>
	<reference name="sbvr10" src="bibtex:manual" src-info="bibtex:line-22487" type="sharef:manual">
		<date value="2008-01"/>
		<address type="sharef:placePublished">Framingham, Massachusetts</address>
		<organization>Object Management Group</organization>
		<title type="sharef:primaryTitle">Semantics of Business Vocabulary and Business Rules (SBVR) — Version 1.0</title>
		<field type="bibtex:topic">sbvr[1]</field>
	</reference>
	<reference name="corba" src="bibtex:manual" src-info="bibtex:line-22496" type="sharef:manual">
		<date value="1998-07"/>
		<address type="sharef:placePublished">Framingham, Massachusetts</address>
		<organization>Object Management Group</organization>
		<title type="sharef:primaryTitle">The Common Object Request Broker: Architecture and Specification — Version 2.2</title>
		<field type="bibtex:topic">corba[1] iiop[1] giop[1]</field>
	</reference>
	<reference name="corba26" src="bibtex:manual" src-info="bibtex:line-22505" type="sharef:manual">
		<date value="2001-12"/>
		<address type="sharef:placePublished">Framingham, Massachusetts</address>
		<organization>Object Management Group</organization>
		<title type="sharef:primaryTitle">The Common Object Request Broker: Architecture and Specification — Version 2.6</title>
		<field type="bibtex:topic">corba[1] iiop[1] giop[1]</field>
		<field type="bibtex:updates">corba</field>
	</reference>
	<reference name="uml13" src="bibtex:manual" src-info="bibtex:line-22515" type="sharef:manual">
		<date value="1999-06"/>
		<address type="sharef:placePublished">Framingham, Massachusetts</address>
		<organization>Object Management Group</organization>
		<title type="sharef:primaryTitle">OMG Unified Modeling Language Specification Version 1.3</title>
		<field type="bibtex:topic">uml[1]</field>
	</reference>
	<reference name="uml14" src="bibtex:manual" src-info="bibtex:line-22524" type="sharef:manual">
		<date value="2001-09"/>
		<address type="sharef:placePublished">Framingham, Massachusetts</address>
		<organization>Object Management Group</organization>
		<title type="sharef:primaryTitle">OMG Unified Modeling Language Specification Version 1.4</title>
		<field type="bibtex:topic">uml[1]</field>
		<field type="bibtex:updates">uml13</field>
	</reference>
	<reference name="uml15" src="bibtex:manual" src-info="bibtex:line-22534" type="sharef:manual">
		<date value="2003-03"/>
		<address type="sharef:placePublished">Framingham, Massachusetts</address>
		<organization>Object Management Group</organization>
		<title type="sharef:primaryTitle">OMG Unified Modeling Language Specification Version 1.5</title>
		<field type="bibtex:topic">uml[1]</field>
		<field type="bibtex:updates">uml14</field>
		<identifier type="sharef:uri">http://www.omg.org/cgi-bin/doc?formal/03-03-01</identifier>
	</reference>
	<reference name="uml20super" src="bibtex:manual" src-info="bibtex:line-22545" type="sharef:manual">
		<date value="2004-10"/>
		<address type="sharef:placePublished">Framingham, Massachusetts</address>
		<organization>Object Management Group</organization>
		<title type="sharef:primaryTitle">UML 2.0 Superstructure Specification</title>
		<field type="bibtex:topic">uml[1]</field>
		<field type="bibtex:updates">uml15</field>
		<identifier type="sharef:uri">http://www.omg.org/cgi-bin/doc?ptc/2004-10-02</identifier>
	</reference>
	<reference name="mof13" src="bibtex:manual" src-info="bibtex:line-22556" type="sharef:manual">
		<date value="1999-06"/>
		<address type="sharef:placePublished">Framingham, Massachusetts</address>
		<organization>Object Management Group</organization>
		<title type="sharef:primaryTitle">OMG Meta Object Facility Specification Version 1.3</title>
		<field type="bibtex:topic">mof[1]</field>
	</reference>
	<reference name="mof14" src="bibtex:manual" src-info="bibtex:line-22565" type="sharef:manual">
		<date value="2002-04"/>
		<organization>Object Management Group</organization>
		<title type="sharef:primaryTitle">Meta Object Facility (MOF) Specification — Version 1.4</title>
		<field type="bibtex:topic">mof[1]</field>
		<field type="bibtex:updates">mof13</field>
		<identifier type="sharef:uri" resourceType="application/pdf">http://www.omg.org/docs/formal/02-04-03.pdf</identifier>
	</reference>
	<reference name="xmi11" src="bibtex:manual" src-info="bibtex:line-22575" type="sharef:manual">
		<date value="1999-10"/>
		<address type="sharef:placePublished">Framingham, Massachusetts</address>
		<organization>Object Management Group</organization>
		<title type="sharef:primaryTitle">OMG XML Metadata Interchange (XMI) Specification Version 1.1</title>
		<field type="bibtex:topic">xmi[1]</field>
	</reference>
	<reference name="xmi12" src="bibtex:manual" src-info="bibtex:line-22584" type="sharef:manual">
		<date value="2002-01"/>
		<address type="sharef:placePublished">Framingham, Massachusetts</address>
		<organization>Object Management Group</organization>
		<title type="sharef:primaryTitle">OMG XML Metadata Interchange (XMI) Specification Version 1.2</title>
		<field type="bibtex:topic">xmi[1]</field>
		<field type="bibtex:updates">xmi11</field>
		<identifier type="sharef:uri">http://www.omg.org/cgi-bin/doc?formal/2002-01-01</identifier>
	</reference>
	<reference name="xmi20" src="bibtex:manual" src-info="bibtex:line-22595" type="sharef:manual">
		<date value="2003-05"/>
		<address type="sharef:placePublished">Framingham, Massachusetts</address>
		<organization>Object Management Group</organization>
		<title type="sharef:primaryTitle">OMG XML Metadata Interchange (XMI) Specification Version 2.0</title>
		<field type="bibtex:topic">xmi[1]</field>
		<field type="bibtex:updates">xmi12</field>
		<identifier type="sharef:uri">http://www.omg.org/cgi-bin/doc?formal/2003-05-02</identifier>
	</reference>
	<reference name="xmi21" src="bibtex:manual" src-info="bibtex:line-22606" type="sharef:manual">
		<date value="2005-09"/>
		<address type="sharef:placePublished">Framingham, Massachusetts</address>
		<organization>Object Management Group</organization>
		<title type="sharef:primaryTitle">MOF 2.0/XMI Mapping Specification, v2.1</title>
		<field type="bibtex:topic">xmi[1] mof[1]</field>
		<field type="bibtex:updates">xmi20 mof14</field>
		<identifier type="sharef:uri">http://www.omg.org/cgi-bin/doc?formal/2005-09-01</identifier>
	</reference>
	<reference name="mda10" src="bibtex:manual" src-info="bibtex:line-22617" type="sharef:manual">
		<names type="sharef:editor">
			<person>
				<givenname>Joaquin</givenname>
				<surname>Miller</surname>
			</person>
			<person>
				<givenname>Jishnu</givenname>
				<surname>Mukerji</surname>
			</person>
		</names>
		<date value="2003-06"/>
		<address type="sharef:placePublished">Framingham, Massachusetts</address>
		<organization>Object Management Group</organization>
		<title type="sharef:primaryTitle">MDA Guide Version 1.0.1</title>
		<field type="bibtex:topic">mda[1]</field>
		<identifier type="sharef:uri">http://www.omg.org/cgi-bin/doc?omg/03-06-01</identifier>
	</reference>
	<reference name="hutn" src="bibtex:manual" src-info="bibtex:line-22628" type="sharef:manual">
		<date value="2002-12"/>
		<address type="sharef:placePublished">Needham, Massachusetts</address>
		<organization>Object Management Group</organization>
		<title type="sharef:primaryTitle">Human-Usable Textual Notation (HUTN) Specification</title>
		<field type="bibtex:topic">hutn[1]</field>
		<identifier type="sharef:uri" resourceType="application/pdf">http://www.dstc.edu.au/Research/Projects/Pegamento/publications/ptc-02-12-01.pdf</identifier>
	</reference>
	<reference name="xtp95" src="bibtex:manual" src-info="bibtex:line-22638" type="sharef:manual">
		<date value="1995-03"/>
		<address type="sharef:placePublished">Santa Barbara, California</address>
		<field type="bibtex:index">XTP</field>
		<organization>XTP Forum</organization>
		<title type="sharef:primaryTitle">Xpress Transport Protocol Specification (XTP Revision 4.0)</title>
	</reference>
	<reference name="quantify" src="bibtex:manual" src-info="bibtex:line-22647" type="sharef:manual">
		<date value="1995"/>
		<address type="sharef:placePublished">Sunnyvale, California</address>
		<organization>Pure Software Inc.</organization>
		<title type="sharef:primaryTitle">Quantify User's Guide</title>
	</reference>
	<reference name="statemate" src="bibtex:manual" src-info="bibtex:line-22654" type="sharef:manual">
		<date value="1993"/>
		<address type="sharef:placePublished">Andover, Massachusetts</address>
		<organization>i-Logix, Inc.</organization>
		<title type="sharef:primaryTitle">Statemate Version 6.0 User Reference Manual</title>
	</reference>
	<reference name="ccrel10" src="bibtex:misc" src-info="bibtex:line-22665" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Hal</givenname>
				<surname>Abelson</surname>
			</person>
			<person>
				<givenname>Ben</givenname>
				<surname>Adida</surname>
			</person>
			<person>
				<givenname>Mike</givenname>
				<surname>Linksvayer</surname>
			</person>
			<person>
				<givenname>Nathan</givenname>
				<surname>Yergler</surname>
			</person>
		</names>
		<date value="2008-03"/>
		<title type="sharef:primaryTitle">ccREL: The Creative Commons Rights Expression Language</title>
		<field type="bibtex:topic">ccrel[1]</field>
		<identifier type="sharef:uri" resourceType="application/pdf">http://wiki.creativecommons.org/images/d/d6/Ccrel-1.0.pdf</identifier>
	</reference>
	<reference name="gro05" src="bibtex:misc" src-info="bibtex:line-22674" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Joshua</givenname>
				<surname>Grossnickle</surname>
			</person>
			<person>
				<givenname>Todd</givenname>
				<surname>Board</surname>
			</person>
			<person>
				<givenname>Brian</givenname>
				<surname>Pickens</surname>
			</person>
			<person>
				<givenname>Mike</givenname>
				<surname>Bellmont</surname>
			</person>
		</names>
		<date value="2005-10"/>
		<howpublished>Yahoo! White Paper</howpublished>
		<title type="sharef:primaryTitle">RSS — Crossing into the Mainstream</title>
		<field type="bibtex:topic">rss[0.8] atom[0.8]</field>
		<identifier type="sharef:uri" resourceType="application/pdf">http://publisher.yahoo.com/rss/RSS_whitePaper1004.pdf</identifier>
	</reference>
	<reference name="tch03" src="bibtex:misc" src-info="bibtex:line-22684" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Dmitri</givenname>
				<surname>Tcherevik</surname>
			</person>
		</names>
		<date value="2003-07"/>
		<howpublished>Computer Associates White Paper</howpublished>
		<title type="sharef:primaryTitle">Management and Security in the World of Web Services</title>
		<identifier type="sharef:uri">http://www3.ca.com/Solutions/Collateral.asp?CID=47494&amp;ID=4712</identifier>
	</reference>
	<reference name="sed03" src="bibtex:misc" src-info="bibtex:line-22693" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Igor</givenname>
				<surname>Sedukhin</surname>
			</person>
		</names>
		<date value="2003-03"/>
		<howpublished>Computer Associates White Paper</howpublished>
		<title type="sharef:primaryTitle">End-to-End Security for Web Services and Services Oriented Architectures</title>
		<identifier type="sharef:uri">http://www3.ca.com/Solutions/Collateral.asp?CID=42144&amp;ID=4712</identifier>
	</reference>
	<reference name="tiff6" src="bibtex:misc" src-info="bibtex:line-22706" type="bibtex:misc">
		<names type="sharef:author">
			<name>Aldus Corporation</name>
		</names>
		<date value="1992-06"/>
		<howpublished>Seattle, Washington</howpublished>
		<field type="bibtex:index">TIFF</field>
		<title type="sharef:primaryTitle">TIFF — Revision 6.0</title>
	</reference>
	<reference name="gif87" src="bibtex:misc" src-info="bibtex:line-22715" type="bibtex:misc">
		<names type="sharef:author">
			<name>CompuServe, Incorporated</name>
		</names>
		<date value="1987-06"/>
		<howpublished>Columbus, Ohio</howpublished>
		<title type="sharef:primaryTitle">GIF — Graphics Interchange Format</title>
		<field type="bibtex:topic">gif[0.9] gif87[1]</field>
	</reference>
	<reference name="gif89a" src="bibtex:misc" src-info="bibtex:line-22724" type="bibtex:misc">
		<names type="sharef:author">
			<name>CompuServe, Incorporated</name>
		</names>
		<date value="1990-07"/>
		<howpublished>Columbus, Ohio</howpublished>
		<title type="sharef:primaryTitle">Graphics Interchange Format — Version 89a</title>
		<field type="bibtex:topic">gif[0.9] gif89a[1]</field>
	</reference>
	<reference name="gui10a" src="bibtex:techreport" src-info="bibtex:line-22737" type="sharef:report">
		<names type="sharef:author">
			<person>
				<givenname>Dominique</givenname>
				<surname>Guinard</surname>
			</person>
			<person>
				<givenname>Vlad</givenname>
				<surname>Trifa</surname>
			</person>
			<person>
				<givenname>Erik</givenname>
				<surname>Wilde</surname>
			</person>
		</names>
		<date value="2010-02"/>
		<abstract>
			<richtext>
				<p>Many efforts are currently going towards networking smart things from the physical world (e.g. RFID, wireless sensor and actuator networks, embedded devices) networked on a larger scale. Rather than exposing real-world data and functionality through proprietary and tightly-coupled systems we propose to make them an integral part of the Web. As a result, smart things become easier to build upon. Popular Web languages (e.g. HTML, URI, JavaScript, PHP) can be used to build applications involving smart things and users can leverage well-known Web mechanisms (e.g. browsing, searching, bookmarking, caching, linking) to interact and share things. In this paper, we begin by describing a Web of Things architecture and best practices rooted on the RESTful principles that contributed to the popular success, scalability, and evolvability of the traditional Web. We then discuss several prototypes implemented using these principles to connect environmental sensor nodes, energy monitoring systems and RFID tagged objects to the World Wide Web. We finally show how Web-enabled things can be used in lightweight ad-hoc applications called "physical mashups".</p>
			</richtext>
		</abstract>
		<address type="sharef:placePublished">Zürich, Switzerland</address>
		<publisher type="sharef:institution">Institute for Pervasive Computing, ETH Zürich</publisher>
		<number>663</number>
		<title type="sharef:primaryTitle">Architecting a Mashable Open World Wide Web of Things</title>
		<field type="bibtex:topic">rest[0.8]</field>
		<identifier type="sharef:uri">https://www.inf.ethz.ch/research/disstechreps/techreports/show?serial=663&amp;lang=en</identifier>
		<identifier type="sharef:uri">http://dret.net/netdret/publications#gui10a</identifier>
	</reference>
	<reference name="ber09a" src="bibtex:techreport" src-info="bibtex:line-22751" type="sharef:report">
		<names type="sharef:author">
			<person>
				<givenname>Tim</givenname>
				<surname>Berners-Lee</surname>
			</person>
			<person>
				<givenname>Richard</givenname>
				<surname>Cyganiak</surname>
			</person>
			<person>
				<givenname>Michael</givenname>
				<surname>Hausenblas</surname>
			</person>
			<person>
				<givenname>Joe</givenname>
				<surname>Presbrey</surname>
			</person>
			<person>
				<givenname>Oshani</givenname>
				<surname>Seneviratne</surname>
			</person>
			<person>
				<givenname>Oana-Elena</givenname>
				<surname>Ureche</surname>
			</person>
		</names>
		<date value="2009-08"/>
		<abstract>
			<richtext>
				<p>The current Web of Data, including linked datasets, RDFa content, and GRDDL-enabled microformats is a read-only Web. Although this read-only Web of Data enables data integration, faceted browsing and structured queries over large datasets, we lack a general concept for a read-write Web of Data. That is, we need to understand how to create, update and delete RDF data. Starting from the experience we have gathered with Tabulator Redux — a single-triple update system based on a data Wiki — we review necessary components to realize a read-write Web of Data. We propose a form-based editing approach for RDF graphs along with the integration of site-specific APIs. Further, we present a concept of a uniform architecture for a read-write Web of Data, including a demonstration. Eventually, our work reveals issues and challenges of the proposed architecture and discusses future steps.</p>
			</richtext>
		</abstract>
		<address type="sharef:placePublished">Galway, Ireland</address>
		<publisher type="sharef:institution">Digital Enterprise Research Institute</publisher>
		<number>2009-08-14</number>
		<title type="sharef:primaryTitle">On Integration Issues of Site-Specific APIs into the Web of Data</title>
		<identifier type="sharef:uri" resourceType="application/pdf">http://richard.cyganiak.de/2008/papers/rwwod-tr-deri2009.pdf</identifier>
	</reference>
	<reference name="umb09" src="bibtex:techreport" src-info="bibtex:line-22763" type="sharef:report">
		<names type="sharef:author">
			<person>
				<givenname>Jürgen</givenname>
				<surname>Umbrich</surname>
			</person>
			<person>
				<givenname>Michael</givenname>
				<surname>Hausenblas</surname>
			</person>
			<person>
				<givenname>Phil</givenname>
				<surname>Archer</surname>
			</person>
			<person>
				<givenname>Eran</givenname>
				<surname>Hammer-Lahav</surname>
			</person>
			<person>
				<givenname>Erik</givenname>
				<surname>Wilde</surname>
			</person>
		</names>
		<date value="2009-08"/>
		<abstract>
			<richtext>
				<p>Discovering information on the Web in a scalable and reliable way is an important but often underestimated task. Research on discovery itself is quite a young field. Hence, to date not many Web-compliant discovery mechanism exist. Firstly, we introduce a layered Abstract Discovery Model and discuss its features. Then, driven by use cases and requirements, we review three promising discovery proposals in the context of the Web of Data and the Web of Documents: XRD, POWDER, and voiD.</p>
			</richtext>
		</abstract>
		<address type="sharef:placePublished">Galway, Ireland</address>
		<publisher type="sharef:institution">Digital Enterprise Research Institute</publisher>
		<number>2009-08-04</number>
		<title type="sharef:primaryTitle">Discovering Resources on the Web</title>
		<field type="bibtex:topic">xrd[0.8] powder[0.8] void[0.8] xlink[0.8]</field>
		<identifier type="sharef:uri">http://linkeddata.deri.ie/tr/2009-discovery</identifier>
		<identifier type="sharef:uri">http://dret.net/netdret/publications#umb09</identifier>
	</reference>
	<reference name="ohm09" src="bibtex:techreport" src-info="bibtex:line-22777" type="sharef:report">
		<names type="sharef:author">
			<person>
				<givenname>Paul</givenname>
				<surname>Ohm</surname>
			</person>
		</names>
		<date value="2009-08"/>
		<abstract>
			<richtext>
				<p>Computer scientists have recently undermined our faith in the privacy-protecting power of anonymization, the name for techniques for protecting the privacy of individuals in large databases by deleting information like names and social security numbers. These scientists have demonstrated they can often 'reidentify' or 'deanonymize' individuals hidden in anonymized data with astonishing ease. By understanding this research, we will realize we have made a mistake, labored beneath a fundamental misunderstanding, which has assured us much less privacy than we have assumed. This mistake pervades nearly every information privacy law, regulation, and debate, yet regulators and legal scholars have paid it scant attention. We must respond to the surprising failure of anonymization, and this article provides the tools to do so.</p>
			</richtext>
		</abstract>
		<address type="sharef:placePublished">Boulder, Colorado</address>
		<publisher type="sharef:institution">University of Colorado</publisher>
		<number>09-12</number>
		<title type="sharef:primaryTitle">Broken Promises of Privacy: Responding to the Surprising Failure of Anonymization</title>
		<identifier type="sharef:uri">http://ssrn.com/abstract=1450006</identifier>
	</reference>
	<reference name="kin08b" src="bibtex:techreport" src-info="bibtex:line-22789" type="sharef:report">
		<names type="sharef:author">
			<person>
				<givenname>Jennifer</givenname>
				<surname>King</surname>
			</person>
			<person>
				<givenname>Chris Jay</givenname>
				<surname>Hoofnagle</surname>
			</person>
		</names>
		<date value="2008-04"/>
		<abstract>
			<richtext>
				<p>While law enforcement increasingly locates individuals by gaining access to wireless phone records, a supermajority of Californians supports judicial intervention and informing suspects before law enforcement acquires retrospective (historical) location data on individuals from wireless phone companies. A majority of Californians understands that wireless phones can track their location, and that there is broad support for location tracking in emergency situations. When compared with Professor Alan Westin's three privacy segments, "Fundamentalists," "Pragmatists," and the "Unconcerned," Californians are more likely to be privacy pragmatists or fundamentalists, and less likely to be unconcerned about privacy. Generally, Westin's segmentation was not predictive of Californians' attitudes towards law enforcement access to wireless location data.</p>
			</richtext>
		</abstract>
		<address type="sharef:placePublished">Berkeley, California</address>
		<publisher type="sharef:institution">School of Law, UC Berkeley</publisher>
		<title type="sharef:primaryTitle">A Supermajority of Californians Supports Limits on Law Enforcement Access to Cell Phone Location Information</title>
		<identifier type="sharef:uri">http://ssrn.com/abstract=1137988</identifier>
	</reference>
	<reference name="boz07" src="bibtex:techreport" src-info="bibtex:line-22800" type="sharef:report">
		<names type="sharef:author">
			<person>
				<givenname>Engin</givenname>
				<surname>Bozdag</surname>
			</person>
			<person>
				<givenname>Ali</givenname>
				<surname>Mesbah</surname>
			</person>
			<person>
				<givenname>Arie</givenname>
				<surname link="van">Deursen</surname>
			</person>
		</names>
		<date value="2007"/>
		<abstract>
			<richtext>
				<p>AJAX applications are designed to have high user interactivity and low user-perceived latency. Real-time dynamic web data such as news headlines, stock tickers, and auction updates need to be propagated to the users as soon as possible. However, AJAX still suffers from the limitations of the Web's request/response architecture which prevents servers from pushing real-time dynamic web data. Such applications usually use a pull style to obtain the latest updates, where the client actively requests the changes based on a predefined interval. It is possible to overcome this limitation by adopting a push style of interaction where the server broadcasts data when a change occurs on the server side. Both these options have their own trade-offs. This paper explores the fundamental limits of browser-based applications and analyzes push solutions for AJAX technology. It also shows the results of an empirical study comparing push and pull.</p>
			</richtext>
		</abstract>
		<address type="sharef:placePublished">Delft, Netherlands</address>
		<publisher type="sharef:institution">Delft University of Technology, Software Engineering Research Group</publisher>
		<number>TUD-SERG-2007-016a</number>
		<title type="sharef:primaryTitle">A Comparison of Push and Pull Techniques for AJAX</title>
		<identifier type="sharef:uri" resourceType="application/pdf">http://swerl.tudelft.nl/twiki/pub/Main/TechnicalReports/TUD-SERG-2007-016.pdf</identifier>
	</reference>
	<reference name="mot08b" src="bibtex:techreport" src-info="bibtex:line-22811" type="sharef:report">
		<names type="sharef:author">
			<person>
				<givenname>Luca</givenname>
				<surname>Mottola</surname>
			</person>
			<person>
				<givenname>Gian Pietro</givenname>
				<surname>Picco</surname>
			</person>
		</names>
		<date value="2008-11"/>
		<abstract>
			<richtext>
				<p>Wireless sensor networks (WSNs) are composed of tiny devices equipped with computation, communication, and sensing/actuating capabilities. These networks recently attracted great interest in a number of application domains concerned with monitoring and control of physical phenomena, as they enable dense and untethered deployments at low cost and with unprecedented flexibility. However, application development is still the main hurdle to a wide adoption of WSN technology. Programming is typically carried out very close to the operating system, therefore requiring the programmer to focus on low-level system issues. This not only shifts the focus of the programmer away from the application logic, but also requires a technical background that is rarely found among application domain experts. The need for appropriate high-level programming abstractions, capable to simplify the programming chore without sacrificing efficiency, has been long recognized and several solutions have been hitherto proposed, which differ along many dimensions. In this paper, we survey the state-of-the-art in programming approaches for WSNs. We begin with a characterization of WSN applications, to identify the fundamental requirements programming platforms must deal with. Then, we introduce a taxonomy of WSN programming abstractions which captures the fundamental differences among existing approaches, and constitutes the core contribution of this paper. Our presentation style relies on concrete examples and code snippets taken from programming platforms representative of the taxonomy dimensions being discussed. We use the taxonomy to provide an exhaustive classification of existing approaches. Moreover, we also map existing approaches back to the application requirements, therefore providing not only a complete view of the state-of-the-art, but also useful insights for selecting the programming abstraction most appropriate to the application at hand.</p>
			</richtext>
		</abstract>
		<address type="sharef:placePublished">Milano, Italy</address>
		<publisher type="sharef:institution">Politecnico di Milano</publisher>
		<title type="sharef:primaryTitle">Programming Wireless Sensor Networks: Fundamental Concepts and State of the Art</title>
		<identifier type="sharef:uri" resourceType="application/pdf">http://www.sics.se/~luca/techRep/surveywsn.pdf</identifier>
	</reference>
	<reference name="gol08" src="bibtex:techreport" src-info="bibtex:line-22822" type="sharef:report">
		<names type="sharef:author">
			<person>
				<givenname>Daniel W.</givenname>
				<surname>Goldberg</surname>
			</person>
		</names>
		<date value="2008-11"/>
		<abstract>
			<richtext>
				<p>The advent of geographic information science and the accompanying technologies (geo-graphic information systems, global positioning systems, remote sensing, and more recently location-based services) have forever changed the ways in which people conceive of and navigate planet Earth. Geocoding is a key bridge linking the old and the new — a world in which streets and street addresses served as the primary location identifiers and the modern world in which more precise representations are possible and needed to explore, analyze, and visualize geographic patterns, their drivers, and their consequences. Geocoding, viewed from this perspective, brings together the knowledge and work of the geographer and the computer scientist. The author, Daniel Goldberg, has done an excellent job in laying out the fundamentals of geocoding as a process using the best contributions from both of these once-disparate fields. This book will serve as a rich reference manual for those who want to inject more science and less art (uncertainty) into their geocoding tasks. This is particularly important for medical geography and epidemiology applications, as recent research findings point to environmental conditions that may contribute to and/or exacerbate health problems that vary over distances of hundreds and even tens of meters (i.e., as happens with proximity to free-ways). These findings call for much better and more deliberate geocoding practices than many practitioners have used to date and bring the contents of this best practices manual to the fore. This book provides a long overdue summary of the state-of-the-art of geocoding and will be essential reading for those that wish and/or need to generate detailed and accurate geographic positions from street addresses and the like.</p>
			</richtext>
		</abstract>
		<address type="sharef:placePublished">Los Angeles, California</address>
		<publisher type="sharef:institution">University of Southern California, GIS Research Laboratory</publisher>
		<title type="sharef:primaryTitle">A Geocoding Best Practices Guide</title>
		<identifier type="sharef:uri" resourceType="application/pdf">http://www.naaccr.org/filesystem/pdf/Geocoding_Best_Practices.pdf</identifier>
	</reference>
	<reference name="mat04" src="bibtex:techreport" src-info="bibtex:line-22833" type="sharef:report">
		<names type="sharef:author">
			<person>
				<givenname>Adam</givenname>
				<surname>Mathes</surname>
			</person>
		</names>
		<date value="2004-12"/>
		<abstract>
			<richtext>
				<p>This paper examines user-generated metadata as implemented and applied in two web services designed to share and organize digital media to better understand grassroots classification. Metadata — data about data — allows systems to collocate related information, and helps users find relevant information. The creation of metadata has generally been approached in two ways: professional creation and author creation. In libraries and other organizations, creating metadata, primarily in the form of catalog records, has traditionally been the domain of dedicated professionals working with complex, detailed rule sets and vocabularies. The primary problem with this approach is scalability and its impracticality for the vast amounts of content being produced and used, especially on the World Wide Web. The apparatus and tools built around professional cataloging systems are generally too complicated for anyone without specialized training and knowledge. A second approach is for metadata to be created by authors. The movement towards creator described documents was heralded by SGML, the WWW, and the Dublin Core Metadata Initiative. There are problems with this approach as well — often due to inadequate or inaccurate description, or outright deception. This paper examines a third approach: user-created metadata, where users of the documents and media create metadata for their own individual use that is also shared throughout a community.</p>
			</richtext>
		</abstract>
		<address type="sharef:placePublished">Urbana-Champaign, Illinois</address>
		<publisher type="sharef:institution">University of Illinois</publisher>
		<number>LIS590CMC</number>
		<title type="sharef:primaryTitle">Folksonomies — Cooperative Classification and Communication Through Shared Metadata</title>
		<identifier type="sharef:uri" resourceType="text/html">http://www.adammathes.com/academic/computer-mediated-communication/folksonomies.html</identifier>
	</reference>
	<reference name="lou05" src="bibtex:techreport" src-info="bibtex:line-22845" type="sharef:report">
		<names type="sharef:author">
			<person>
				<givenname>Steve</givenname>
				<surname>Loughran</surname>
			</person>
			<person>
				<givenname>Edmund</givenname>
				<surname>Smith</surname>
			</person>
		</names>
		<date value="2005-05-07"/>
		<abstract>
			<richtext>
				<p>This paper examines the current SOAP APIs in Java, and in particular the Java API for XML-based RPC, commonly known as JAX-RPC, which is effectively the standard API for SOAP on the Java platform. We claim that JAX-RPC, and indeed any SOAP API that relies upon a perfect two-way mapping between XML data and native language objects is fundamentally flawed. Furthermore, we claim that the attempt JAX-RPC makes to extend the remote method invocation metaphor to SOAP services is counterproductive. We base our argument both upon experience with JAX-RPC and SOAP, and upon experience of previous distributed computing technologies. We argue that JAX-RPC is not capable of delivering on the SOAP design goals, but conclude by suggesting an alternate system, Alpine, which is free from many known flaws of existing systems, and should prove better able to deliver upon the promise of SOAP.</p>
			</richtext>
		</abstract>
		<address type="sharef:placePublished">Bristol, UK</address>
		<publisher type="sharef:institution">HP Laboratories</publisher>
		<number>HPL-2005-83</number>
		<title type="sharef:primaryTitle">Rethinking the Java SOAP Stack</title>
		<field type="bibtex:topic">soap[0.8] java[0.8]</field>
		<identifier type="sharef:uri" resourceType="text/html">http://www.hpl.hp.com/techreports/2005/HPL-2005-83.html</identifier>
	</reference>
	<reference name="car03b" src="bibtex:techreport" src-info="bibtex:line-22859" type="sharef:report">
		<names type="sharef:author">
			<person>
				<givenname>Jeremy J.</givenname>
				<surname>Carroll</surname>
			</person>
			<person>
				<givenname>Patrick</givenname>
				<surname>Stickler</surname>
			</person>
		</names>
		<date value="2003-02-01"/>
		<abstract>
			<richtext>
				<p>Many approaches to writing RDF in XML have been proposed. The revised standard RDF/XML still has many known problems. It is not intrinsically difficult to have a clear serialization of RDF in XML, and we present a simple solution. We add the ability to name graphs, noting that in practice this is already widely used. We use XSLT as a general syntactic extensibility mechanism to provide human friendly macros for our syntax.</p>
			</richtext>
		</abstract>
		<address type="sharef:placePublished">Bristol, UK</address>
		<publisher type="sharef:institution">HP Laboratories</publisher>
		<number>HPL-2003-268</number>
		<title type="sharef:primaryTitle">RDF Triples in XML</title>
		<field type="bibtex:topic">trix[1] rdf[0.9]</field>
		<identifier type="sharef:uri" resourceType="text/html">http://www.hpl.hp.com/techreports/2003/HPL-2003-268.html</identifier>
	</reference>
	<reference name="car04c" src="bibtex:techreport" src-info="bibtex:line-22873" type="sharef:report">
		<names type="sharef:author">
			<person>
				<givenname>Jeremy J.</givenname>
				<surname>Carroll</surname>
			</person>
			<person>
				<givenname>Patrick</givenname>
				<surname>Stickler</surname>
			</person>
		</names>
		<date value="2004-05-03"/>
		<abstract>
			<richtext>
				<p>Many approaches to writing RDF in XML have been proposed. The revised standard RDF/XML still has many known problems. It is not intrinsically difficult to have a clear serialization of RDF in XML, and we present a simple solution. We add the ability to name graphs, noting that in practice this is already widely used. We use XSLT as a general syntactic extensibility mechanism to provide human friendly macros for our syntax.</p>
			</richtext>
		</abstract>
		<address type="sharef:placePublished">Bristol, UK</address>
		<publisher type="sharef:institution">HP Laboratories</publisher>
		<number>HPL-2004-56</number>
		<title type="sharef:primaryTitle">TriX: RDF Triples in XML</title>
		<field type="bibtex:topic">trix[1] rdf[0.9]</field>
		<field type="bibtex:updates">car03b</field>
		<identifier type="sharef:uri" resourceType="text/html">http://www.hpl.hp.com/techreports/2004/HPL-2004-56.html</identifier>
	</reference>
	<reference name="mar04e" src="bibtex:techreport" src-info="bibtex:line-22888" type="sharef:report">
		<names type="sharef: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 type="sharef:placePublished">Bologna, Italy</address>
		<publisher type="sharef:institution">University of Bologna</publisher>
		<number>UBLCS-2004-13</number>
		<title type="sharef:primaryTitle">SchemaPath: Extending XML Schema for Co-Constraints</title>
		<field type="bibtex:topic">schemapath[1]</field>
		<identifier type="sharef:uri" resourceType="application/pdf">http://www.cs.unibo.it/pub/TR/UBLCS/2004/2004-13.pdf</identifier>
	</reference>
	<reference name="sen03b" src="bibtex:techreport" src-info="bibtex:line-22901" type="sharef:report">
		<names type="sharef: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 type="sharef:placePublished">Bloomington, Indiana</address>
		<publisher type="sharef:institution">Indiana University, Information Systems Department</publisher>
		<number>137-1</number>
		<title type="sharef:primaryTitle">Formal and Conceptual Models for XML Structures — The Past, Present, and Future</title>
		<field type="bibtex:topic">hnr[0.9]</field>
		<identifier type="sharef:uri" resourceType="application/pdf">http://www.indiana.edu/~isdept/research/papers/tr137-1.pdf</identifier>
	</reference>
	<reference name="hod00" src="bibtex:techreport" src-info="bibtex:line-22914" type="sharef:report">
		<names type="sharef: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 type="sharef:placePublished">Washington, D.C.</address>
		<publisher type="sharef:institution">Council on Library and Information Resources</publisher>
		<identifier type="sharef:isbn">1-887334-76-9</identifier>
		<number>91</number>
		<title type="sharef:primaryTitle">Systems of Knowledge Organization for Digital Libraries: Beyond Traditional Authority Files</title>
		<identifier type="sharef:uri" resourceType="text/html">http://www.clir.org/pubs/abstract/pub91abst.html</identifier>
	</reference>
	<reference name="kel99" src="bibtex:techreport" src-info="bibtex:line-22927" type="sharef:report">
		<names type="sharef: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="1999-07"/>
		<abstract>
			<richtext>
				<p>This document is the final report for the WebWatch project. The aim of the project was to develop and use robot software for analysing and profiling Web sites within various UK communities and to report on the findings. This document reviews the original bid, gives a background to robot software, describes the robot software used by the WebWatch project, and summaries the conclusions gained from the WebWatch trawls. A list of recommendations for further work in this area is given. The appendices include a number of the reports which have been produced which describe the main trawls carried out by the project.</p>
			</richtext>
		</abstract>
		<publisher type="sharef:institution">British Library Research and Innovation Centre</publisher>
		<number>British Library Research and Innovation Report 146</number>
		<title type="sharef:primaryTitle">WebWatching UK Web Communities: Final Report For The WebWatch Project</title>
		<identifier type="sharef:uri" resourceType="text/html">http://www.ukoln.ac.uk/web-focus/webwatch/reports/final/rtf-html/single/report.html</identifier>
	</reference>
	<reference name="cob02" src="bibtex:techreport" src-info="bibtex:line-22938" type="sharef:report">
		<names type="sharef: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 type="sharef:placePublished">Rocquencourt, France</address>
		<publisher type="sharef:institution">Institut National de Recherche en Informatique et en Automatique</publisher>
		<title type="sharef:primaryTitle">A comparative study for XML change detection</title>
		<field type="bibtex:topic">xml[0.7]</field>
		<identifier type="sharef:uri" resourceType="application/pdf">ftp://ftp.inria.fr/INRIA/Projects/verso/VersoReport-221.pdf</identifier>
	</reference>
	<reference name="sah02" src="bibtex:techreport" src-info="bibtex:line-22950" type="sharef:report">
		<names type="sharef: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 type="sharef:placePublished">Palo Alto, California</address>
		<publisher type="sharef:institution">HP Laboratories</publisher>
		<number>HPL-2001-310R1</number>
		<title type="sharef:primaryTitle">Towards Automated SLA Management for Web Services</title>
		<field type="bibtex:topic">wsml3[1]</field>
		<identifier type="sharef:uri" resourceType="text/html">http://www.hpl.hp.com/techreports/2001/HPL-2001-310R1.html</identifier>
	</reference>
	<reference name="bak95" src="bibtex:techreport" src-info="bibtex:line-22963" type="sharef:report">
		<names type="sharef: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="sharef:institution">Department of Computer Science, University of Wollongong</publisher>
		<number>95-09</number>
		<title type="sharef:primaryTitle">Cryptographic Hash Functions: A Survey</title>
		<field type="bibtex:topic">chf[1]</field>
	</reference>
	<reference name="pag99" src="bibtex:techreport" src-info="bibtex:line-22973" type="sharef:report">
		<names type="sharef: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="sharef:institution">Stanford University</publisher>
		<number>SIDL-WP-1999-0120</number>
		<title type="sharef:primaryTitle">The PageRank Citation Ranking: Bringing Order to the Web</title>
		<field type="bibtex:topic">pagerank[1]</field>
		<identifier type="sharef:uri">http://dbpubs.stanford.edu/pub/1999-66</identifier>
	</reference>
	<reference name="obe04" src="bibtex:techreport" src-info="bibtex:line-22984" type="sharef:report">
		<names type="sharef:author">
			<person>
				<givenname>Felix</givenname>
				<surname>Oberholzer</surname>
			</person>
			<person>
				<givenname>Koleman</givenname>
				<surname>Strumpf</surname>
			</person>
		</names>
		<date value="2004-03"/>
		<address type="sharef:placePublished">Chapel Hill, North Carolina</address>
		<publisher type="sharef:institution">University of North Carolina</publisher>
		<title type="sharef:primaryTitle">The Effect of File Sharing on Record Sales: An Empirical Analysis</title>
		<identifier type="sharef:uri" resourceType="application/pdf">http://www.unc.edu/~cigar/papers/FileSharing_March2004.pdf</identifier>
	</reference>
	<reference name="riz01a" src="bibtex:techreport" src-info="bibtex:line-22994" type="sharef:report">
		<names type="sharef:author">
			<person>
				<givenname>Romeo</givenname>
				<surname>Rizzi</surname>
			</person>
		</names>
		<date value="2001-01"/>
		<address type="sharef:placePublished">Trento, Italy</address>
		<publisher type="sharef:institution">Istituto Trentino di Cultura</publisher>
		<title type="sharef:primaryTitle">Complexity of Context-Free Grammars with Exceptions</title>
		<field type="bibtex:topic">xml[0.8] sgml[0.8]</field>
	</reference>
	<reference name="kil98" src="bibtex:techreport" src-info="bibtex:line-23004" type="sharef:report">
		<names type="sharef: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 type="sharef:placePublished">Helsinki, Finland</address>
		<publisher type="sharef:institution">University of Helsinki</publisher>
		<number>Department of Computer Science Report C-1998-12</number>
		<title type="sharef:primaryTitle">SGML &amp; XML Content Models</title>
		<field type="bibtex:topic">xml[0.8] sgml[0.8]</field>
		<identifier type="sharef:uri" resourceType="text/html">http://citeseer.nj.nec.com/85205.html</identifier>
		<identifier type="sharef:uri">http://www.cs.helsinki.fi/TR/C-1998/12/</identifier>
	</reference>
	<reference name="kil99" src="bibtex:techreport" src-info="bibtex:line-23018" type="sharef:report">
		<names type="sharef: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 type="sharef:placePublished">Hong Kong</address>
		<publisher type="sharef:institution">Hong Kong University of Science &amp; Technology</publisher>
		<number>HKUST-TCSC-99-01</number>
		<title type="sharef:primaryTitle">SGML and XML Document Grammars and Exceptions</title>
		<field type="bibtex:topic">xml[0.8] sgml[0.8]</field>
		<identifier type="sharef:uri" resourceType="text/html">http://citeseer.nj.nec.com/335929.html</identifier>
		<identifier type="sharef:uri">http://portal.acm.org/citation.cfm?id=501973</identifier>
		<identifier type="sharef:uri" resourceType="application/pdf">http://xml.coverpages.org/exceptionsHK-1999-01.pdf</identifier>
	</reference>
	<reference name="sch04a" src="bibtex:techreport" src-info="bibtex:line-23033" type="sharef:report">
		<names type="sharef:author">
			<person>
				<givenname>Kuno</givenname>
				<surname>Schedler</surname>
			</person>
			<person>
				<givenname>Lukas</givenname>
				<surname>Summermatter</surname>
			</person>
		</names>
		<date value="2004-02"/>
		<address type="sharef:placePublished">St. Gallen, Switzerland</address>
		<publisher type="sharef:institution">Institut für Öffentliche Dienstleistungen und Tourismus, Universität St. Gallen</publisher>
		<identifier type="sharef:isbn">3-9522667-2-8</identifier>
		<number>IDT-Working Paper Nr. 8a</number>
		<title type="sharef:primaryTitle">2. Bericht zum Stand von E-Government in der Schweiz 2003 — Teil Gemeinden</title>
	</reference>
	<reference name="sch04b" src="bibtex:techreport" src-info="bibtex:line-23044" type="sharef:report">
		<names type="sharef:author">
			<person>
				<givenname>Kuno</givenname>
				<surname>Schedler</surname>
			</person>
			<person>
				<givenname>Lukas</givenname>
				<surname>Summermatter</surname>
			</person>
		</names>
		<date value="2004-02"/>
		<address type="sharef:placePublished">St. Gallen, Switzerland</address>
		<publisher type="sharef:institution">Institut für Öffentliche Dienstleistungen und Tourismus, Universität St. Gallen</publisher>
		<identifier type="sharef:isbn">3-9522667-3-6</identifier>
		<number>IDT-Working Paper Nr. 8b</number>
		<title type="sharef:primaryTitle">2. Bericht zum Stand von E-Government in der Schweiz 2003 — Teil Kantone</title>
	</reference>
	<reference name="sch04c" src="bibtex:techreport" src-info="bibtex:line-23055" type="sharef:report">
		<names type="sharef:author">
			<person>
				<givenname>Kuno</givenname>
				<surname>Schedler</surname>
			</person>
			<person>
				<givenname>Lukas</givenname>
				<surname>Summermatter</surname>
			</person>
		</names>
		<date value="2004-02"/>
		<address type="sharef:placePublished">St. Gallen, Switzerland</address>
		<publisher type="sharef:institution">Institut für Öffentliche Dienstleistungen und Tourismus, Universität St. Gallen</publisher>
		<identifier type="sharef:isbn">3-9522667-4-4</identifier>
		<number>IDT-Working Paper Nr. 8c</number>
		<title type="sharef:primaryTitle">2. Bericht zum Stand von E-Government in der Schweiz 2003 — Teil Bund</title>
	</reference>
	<reference name="bru91" src="bibtex:techreport" src-info="bibtex:line-23066" type="sharef:report">
		<names type="sharef: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 type="sharef:placePublished">Freiburg, Germany</address>
		<publisher type="sharef:institution">Universität Freiburg</publisher>
		<title type="sharef:primaryTitle">Deterministic Regular Languages</title>
		<field type="bibtex:topic">xml[0.8] sgml[0.8]</field>
		<identifier type="sharef:uri">http://www.informatik.uni-freiburg.de/tr/1991/Report38/</identifier>
	</reference>
	<reference name="sha03" src="bibtex:techreport" src-info="bibtex:line-23077" type="sharef:report">
		<names type="sharef: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 type="sharef:placePublished">Bristol, UK</address>
		<publisher type="sharef:institution">Institute for Learning and Research Technology</publisher>
		<number>ILRT Research Report Number 1032</number>
		<title type="sharef:primaryTitle">Review of Personal Bibliographic Systems</title>
		<field type="bibtex:topic">bibtex[0.7]</field>
		<identifier type="sharef:uri">http://www.ilrt.bris.ac.uk/publications/researchreport/rr1032/report_html</identifier>
	</reference>
	<reference name="mat09" src="bibtex:techreport" src-info="bibtex:line-23090" type="sharef:report">
		<names type="sharef:author">
			<person>
				<givenname>Tara</givenname>
				<surname>Matthews</surname>
			</person>
			<person>
				<givenname>Jeffrey</givenname>
				<surname>Pierce</surname>
			</person>
			<person>
				<givenname>John</givenname>
				<surname>Tang</surname>
			</person>
		</names>
		<date value="2009-09"/>
		<abstract>
			<richtext>
				<p>We interviewed 21 people both before and after they acquired an iPhone 3G or T-Mobile G1 to assess how next-generation smart phones impact user behavior. We focused on exploring what motivates people to use their smart phones, what applications they use, what information they access or produce, when and for how long they interact with their phones, and how this usage relates to other tasks and devices. Our results suggest that the use of next-generation mobile phones depends heavily on contexts, particularly users' other devices and the places and situations users encounter. We observed that users employ their mobile phones in concert with, not independent of, their other computers. Rather than just mimicking desktop use, however, they employ their phones in different ways and for new tasks. The places and situations in which users employ their phones shape the tasks they undertake and how they make time to use their devices, fill idle time with them, or defer tasks to their other devices. We draw on our observations to offer design implications, focusing on how to support mobile phone use in the context of other devices and different places and situations.</p>
			</richtext>
		</abstract>
		<publisher type="sharef:institution">IBM</publisher>
		<number>IBM Research Report RJ10452</number>
		<title type="sharef:primaryTitle">No Smart Phone Is an Island: The Impact of Places, Situations, and Other Devices on Smart Phone Use</title>
		<identifier type="sharef:uri" resourceType="application/pdf">http://domino.research.ibm.com/library/cyberdig.nsf/papers/36B5FDFA5ED24C2D852576A9005796C0/$File/rj10458.pdf</identifier>
	</reference>
	<reference name="cod69" src="bibtex:techreport" src-info="bibtex:line-23101" type="sharef:report">
		<names type="sharef:author">
			<person>
				<givenname>Edgar F.</givenname>
				<surname>Codd</surname>
			</person>
		</names>
		<date value="1969-06"/>
		<abstract>
			<richtext>
				<p>The large, integrated data banks of the future will contain many relations of various degrees in stored form. It will not be unusual for this set of stored relations to be redundant. Two types of redundancy are defined and discussed. One type may be employed to improve accessibility of certain kinds of information which happen to be in great demand. When either type of redundancy exists, those responsible for control of the data bank should know about it and have some means of detecting any "logical" inconsistencies in the total set of stored relations. Consistency checking might be helpful in tracking down unauthorized (and possibly fraudulent) changes in the data bank contents.</p>
			</richtext>
		</abstract>
		<address type="sharef:placePublished">San Jose, California</address>
		<publisher type="sharef:institution">IBM</publisher>
		<number>IBM Research Report RJ599</number>
		<title type="sharef:primaryTitle">Derivability, Redundancy and Consistency of Relations Stored in Large Data Banks</title>
		<identifier type="sharef:uri" resourceType="text/html">http://www.informatik.uni-trier.de/~ley/db/labs/ibm/RJ599.html</identifier>
		<identifier type="sharef:uri" resourceType="application/pdf">http://www.liberidu.com/blog/images/rj599.pdf</identifier>
	</reference>
	<reference name="boo99" src="bibtex:techreport" src-info="bibtex:line-23114" type="sharef:report">
		<names type="sharef: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="sharef:institution">Rational Software Corp. and CommerceOne Inc.</publisher>
		<title type="sharef:primaryTitle">UML for XML Schema Mapping Specification</title>
		<field type="bibtex:topic">xml[0.8] uml[0.8] xsd[0.8] sox[0.7]</field>
		<identifier type="sharef:uri" resourceType="application/pdf">http://xml.coverpages.org/fuchs-uml_xmlschema33.pdf</identifier>
	</reference>
	<reference name="bur46" src="bibtex:techreport" src-info="bibtex:line-23124" type="sharef:report">
		<names type="sharef: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 type="sharef:placePublished">Princeton, New Jersey</address>
		<publisher type="sharef:institution">Institute for Advanced Study</publisher>
		<title type="sharef:primaryTitle">Preliminary Discussion of the Logical Design of an Electronic Computing Instrument</title>
		<identifier type="sharef:uri" resourceType="text/html">http://www.cs.unc.edu/~adyilie/comp265/vonNeumann.html</identifier>
	</reference>
	<reference name="cro02" src="bibtex:techreport" src-info="bibtex:line-23134" type="sharef:report">
		<names type="sharef:author">
			<person>
				<givenname>Raym</givenname>
				<surname>Crow</surname>
			</person>
		</names>
		<date value="2002-08"/>
		<address type="sharef:placePublished">Washington, D.C.</address>
		<publisher type="sharef:institution">The Scholarly Publishing &amp; Academic Resources Coalition</publisher>
		<title type="sharef:primaryTitle">The Case for Institutional Repositories: A SPARC Position Paper</title>
		<identifier type="sharef:uri" resourceType="text/html">http://www.arl.org/sparc/IR/ir.html</identifier>
	</reference>
	<reference name="myview98" src="bibtex:techreport" src-info="bibtex:line-23144" type="sharef:report">
		<names type="sharef: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 type="sharef:placePublished">Bonn, Germany</address>
		<field type="bibtex:index">MyView</field>
		<publisher type="sharef:institution">University of Bonn</publisher>
		<number>IAI-TR-98-13</number>
		<title type="sharef:primaryTitle">The MyView Project: From Heterogeneous Bibliographic Information Repositories to Personalized Digital Libraries</title>
	</reference>
	<reference name="sus75" src="bibtex:techreport" src-info="bibtex:line-23155" type="sharef:report">
		<names type="sharef: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 type="sharef:placePublished">Cambridge, UK</address>
		<publisher type="sharef:institution">Massachusetts Institute of Technology</publisher>
		<number>AI Memo No. 349</number>
		<title type="sharef:primaryTitle">Scheme: An Interpreter for Extended Lambda Calculus</title>
		<field type="bibtex:topic">scheme[1]</field>
		<identifier type="sharef:uri" resourceType="application/pdf">ftp://publications.ai.mit.edu/ai-publications/pdf/AIM-349.pdf</identifier>
	</reference>
	<reference name="xpl" src="bibtex:techreport" src-info="bibtex:line-23167" type="sharef:report">
		<names type="sharef:author">
			<person>
				<givenname>Erik</givenname>
				<surname>Bruchez</surname>
			</person>
		</names>
		<date value="2002-10"/>
		<address type="sharef:placePublished">Mountain View, California</address>
		<publisher type="sharef:institution">Orbeon, Inc.</publisher>
		<title type="sharef:primaryTitle">An Introduction to XML Pipelines</title>
		<field type="bibtex:topic">xpl[1]</field>
	</reference>
	<reference name="xmlppm" src="bibtex:techreport" src-info="bibtex:line-23177" type="sharef:report">
		<names type="sharef:author">
			<person>
				<givenname>James</givenname>
				<surname>Cheney</surname>
			</person>
		</names>
		<date value="2000-11"/>
		<address type="sharef:placePublished">Ithaca, New York</address>
		<publisher type="sharef:institution">Cornell University</publisher>
		<title type="sharef:primaryTitle">Compressing XML with Multiplexed Hierarchical PPM Models</title>
		<field type="bibtex:topic">xmlppm[1] esax[1] mhm[1] ppm[0.7] xml[0.7]</field>
	</reference>
	<reference name="xmill" src="bibtex:techreport" src-info="bibtex:line-23187" type="sharef:report">
		<names type="sharef:author">
			<person>
				<givenname>Hartmut</givenname>
				<surname>Liefke</surname>
			</person>
			<person>
				<givenname>Dan</givenname>
				<surname>Suciu</surname>
			</person>
		</names>
		<date value="1999"/>
		<address type="sharef:placePublished">Philadelphia, Pennsylvania</address>
		<publisher type="sharef:institution">University of Pennsylvania</publisher>
		<number>MS-CIS-99-26</number>
		<title type="sharef:primaryTitle">XMill: An Efficient Compressor for XML Data</title>
		<field type="bibtex:topic">xmill[1] xml[0.7]</field>
	</reference>
	<reference name="j2ee13" src="bibtex:techreport" src-info="bibtex:line-23197" type="sharef:report">
		<names type="sharef:author">
			<person>
				<givenname>Bill</givenname>
				<surname>Shannon</surname>
			</person>
		</names>
		<date value="2001-07"/>
		<publisher type="sharef:institution">Sun Microsystems</publisher>
		<title type="sharef:primaryTitle">Java 2 Platform Enterprise Edition Specification, v1.3</title>
		<field type="bibtex:topic">j2ee[1]</field>
	</reference>
	<reference name="wal94" src="bibtex:techreport" src-info="bibtex:line-23206" type="sharef:report">
		<names type="sharef:author">
			<person>
				<givenname>Jim</givenname>
				<surname>Waldo</surname>
			</person>
			<person>
				<givenname>Geoff</givenname>
				<surname>Wyant</surname>
			</person>
			<person>
				<givenname>Ann</givenname>
				<surname>Wollrath</surname>
			</person>
			<person>
				<givenname>Samuel C.</givenname>
				<surname>Kendall</surname>
			</person>
		</names>
		<date value="1994-11"/>
		<abstract>
			<richtext>
				<p>We argue that objects that interact in a distributed system need to be dealt with in ways that are intrinsically different from objects that interact in a single address space. These differences are required because distributed systems require that the programmer be aware of latency, have a different model of memory access, and take into account issues of concurrency and partial failure. We look at a number of distributed systems that have attempted to paper over the distinction between local and remote objects, and show that such systems fail to support basic requirements of robustness and reliability. These failures have been masked in the past by the small size of the distributed systems that have been built. In the enterprise-wide distributed systems foreseen in the near future, however, such a masking will be impossible. We conclude by discussing what is required of both systems-level and application-level programmers and designers if one is to take distribution seriously.</p>
			</richtext>
		</abstract>
		<publisher type="sharef:institution">Sun Microsystems</publisher>
		<number>TR-94-29</number>
		<title type="sharef:primaryTitle">A Note on Distributed Computing</title>
		<field type="bibtex:topic">corba[0.8] rpc[0.8] nfs[0.8]</field>
		<identifier type="sharef:uri" resourceType="text/html">http://research.sun.com/techrep/1994/abstract-29.html</identifier>
	</reference>
	<reference name="wadl" src="bibtex:techreport" src-info="bibtex:line-23218" type="sharef:report">
		<names type="sharef:author">
			<person>
				<givenname>Marc</givenname>
				<surname>Hadley</surname>
			</person>
		</names>
		<date value="2006-04"/>
		<abstract>
			<richtext>
				<p>This article describes the Web Application Description Language (WADL). An increasing number of Web-based enterprises (Google, Yahoo, Amazon, Flickr — to name but a few) are developing HTTP-based applications that provide access to their internal data using XML. Typically these applications are described using a combination of textual protocol descriptions combined with XML schema-based data format descriptions; WADL is designed to provide a machine processable protocol description format for use with such HTTP-based Web applications, especially those using XML.</p>
			</richtext>
		</abstract>
		<publisher type="sharef:institution">Sun Microsystems</publisher>
		<number>TR-2006-153</number>
		<title type="sharef:primaryTitle">Web Application Description Language (WADL)</title>
		<field type="bibtex:topic">wadl[1]</field>
		<identifier type="sharef:uri" resourceType="text/html">http://research.sun.com/techrep/2006/abstract-153.html</identifier>
	</reference>
	<reference name="sch02b" src="bibtex:techreport" src-info="bibtex:line-23230" type="sharef:report">
		<names type="sharef:author">
			<person>
				<givenname>Robert J.</givenname>
				<surname>Schloss</surname>
			</person>
		</names>
		<date value="2002-02"/>
		<publisher type="sharef:institution">IBM</publisher>
		<title type="sharef:primaryTitle">XML Schema Infoset API Requirements</title>
		<field type="bibtex:topic">xsd[0.8] dom[0.8]</field>
		<identifier type="sharef:uri" resourceType="text/html">http://www.research.ibm.com/XML/schema/WD-XML-Schema-Infoset-API-Req.htm</identifier>
	</reference>
	<reference name="wsfl10" src="bibtex:techreport" src-info="bibtex:line-23240" type="sharef:report">
		<names type="sharef:author">
			<person>
				<givenname>Frank</givenname>
				<surname>Leymann</surname>
			</person>
		</names>
		<date value="2001-05"/>
		<publisher type="sharef:institution">IBM</publisher>
		<title type="sharef:primaryTitle">Web Services Flow Language (WSFL 1.0)</title>
		<field type="bibtex:topic">wsfl[1]</field>
		<identifier type="sharef:uri" resourceType="application/pdf">http://www.ibm.com/software/solutions/webservices/pdf/WSFL.pdf</identifier>
	</reference>
	<reference name="jta101" src="bibtex:techreport" src-info="bibtex:line-23250" type="sharef:report">
		<names type="sharef:author">
			<person>
				<givenname>Susan</givenname>
				<surname>Cheung</surname>
			</person>
			<person>
				<givenname>Vlada</givenname>
				<surname>Matena</surname>
			</person>
		</names>
		<date value="1999-04"/>
		<publisher type="sharef:institution">Sun Microsystems</publisher>
		<title type="sharef:primaryTitle">Java Transaction API (JTA) — Version 1.0.1</title>
		<field type="bibtex:topic">jta[1]</field>
	</reference>
	<reference name="jms102" src="bibtex:techreport" src-info="bibtex:line-23259" type="sharef:report">
		<names type="sharef: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="sharef:institution">Sun Microsystems</publisher>
		<title type="sharef:primaryTitle">Java Message Service — Version 1.0.2b</title>
		<field type="bibtex:topic">jms[1]</field>
	</reference>
	<reference name="pat88" src="bibtex:techreport" src-info="bibtex:line-23268" type="sharef:report">
		<names type="sharef:author">
			<person>
				<givenname>Oren</givenname>
				<surname>Patashnik</surname>
			</person>
		</names>
		<date value="1988-02"/>
		<title type="sharef:primaryTitle">BibTeXing</title>
		<field type="bibtex:topic">bibtex[1]</field>
	</reference>
	<reference name="pat88b" src="bibtex:techreport" src-info="bibtex:line-23276" type="sharef:report">
		<names type="sharef:author">
			<person>
				<givenname>Oren</givenname>
				<surname>Patashnik</surname>
			</person>
		</names>
		<date value="1988-02"/>
		<title type="sharef:primaryTitle">Designing BibTeX Styles</title>
		<field type="bibtex:topic">bibtex[1]</field>
	</reference>
	<reference name="dig35" src="bibtex:techreport" src-info="bibtex:line-23284" type="sharef:report">
		<names type="sharef:author">
			<name>Digital Imaging Group</name>
		</names>
		<date value="2000-08"/>
		<address type="sharef:placePublished">Millbrae, California</address>
		<title type="sharef:primaryTitle">DIG35 Specification — Metadata for Digital Images (Version 1.0)</title>
		<field type="bibtex:topic">metadata[0.8]</field>
	</reference>
	<reference name="car00" src="bibtex:techreport" src-info="bibtex:line-23293" type="sharef:report">
		<names type="sharef: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 type="sharef:placePublished">Southampton, UK</address>
		<field type="bibtex:index">WWW, hypermedia</field>
		<publisher type="sharef:institution">Multimedia Research Group, University of Southampton</publisher>
		<number>ECSTR-IAM00-1</number>
		<title type="sharef:primaryTitle">Writing and Reading Hypermedia on the Web</title>
		<identifier type="sharef:uri" resourceType="text/html">http://www.bib.ecs.soton.ac.uk/cgi-bin/data/3368/html/WRWH.html</identifier>
	</reference>
	<reference name="moo97" src="bibtex:techreport" src-info="bibtex:line-23306" type="sharef:report">
		<names type="sharef: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 type="sharef:placePublished">Knoxville, Tennessee</address>
		<field type="bibtex:index">RCDS</field>
		<publisher type="sharef:institution">University of Tennessee</publisher>
		<number>UT-CS-97-346</number>
		<title type="sharef:primaryTitle">Resource Cataloging and Distribution System</title>
	</reference>
	<reference name="bie96" src="bibtex:techreport" src-info="bibtex:line-23317" type="sharef:report">
		<names type="sharef: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 type="sharef:placePublished">San Jose, California</address>
		<publisher type="sharef:institution">Adobe Systems Inc.</publisher>
		<title type="sharef:primaryTitle">Portable Document Format Reference Manual — Version 1.2</title>
		<field type="bibtex:topic">pdf[1]</field>
		<field type="bibtex:updates">bie93</field>
	</reference>
	<reference name="spe94b" src="bibtex:techreport" src-info="bibtex:line-23328" type="sharef:report">
		<names type="sharef: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 type="sharef:placePublished">Chicago, Illinois</address>
		<field type="bibtex:index">TEI P3</field>
		<publisher type="sharef:institution">Text Encoding Initiative</publisher>
		<title type="sharef:primaryTitle">Guidelines for Electronic Text Encoding and Interchange (TEI P3)</title>
		<field type="bibtex:topic">tei[1]</field>
	</reference>
	<reference name="teip4" src="bibtex:techreport" src-info="bibtex:line-23339" type="sharef:report">
		<names type="sharef: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 type="sharef:placePublished">Oxford — Providence — Charlottesville — Bergen</address>
		<field type="bibtex:index">TEI P4</field>
		<publisher type="sharef:institution">Text Encoding Initiative</publisher>
		<title type="sharef:primaryTitle">The Text Encoding Initiative Guidelines (P4)</title>
		<field type="bibtex:topic">tei[1]</field>
		<identifier type="sharef:uri">http://etext.lib.virginia.edu/teip4/</identifier>
	</reference>
	<reference name="riv95" src="bibtex:techreport" src-info="bibtex:line-23351" type="sharef:report">
		<names type="sharef:author">
			<person>
				<givenname>Ronald L.</givenname>
				<surname>Rivest</surname>
			</person>
		</names>
		<date value="1997-03"/>
		<address type="sharef:placePublished">Cambridge, Massachusetts</address>
		<field type="bibtex:index">RC5</field>
		<publisher type="sharef:institution">MIT Laboratory for Computer Science</publisher>
		<title type="sharef:primaryTitle">The RC5 Encryption Algorithm</title>
	</reference>
	<reference name="ell98" src="bibtex:techreport" src-info="bibtex:line-23361" type="sharef:report">
		<names type="sharef:author">
			<person>
				<givenname>Castedo</givenname>
				<surname>Ellerman</surname>
			</person>
		</names>
		<date value="1998-04"/>
		<address type="sharef:placePublished">Redmond, Washington</address>
		<field type="bibtex:index">CDF</field>
		<publisher type="sharef:institution">Microsoft Corporation</publisher>
		<title type="sharef:primaryTitle">Channel Definition Format (CDF) — Version 1.01</title>
	</reference>
	<reference name="mad01" src="bibtex:techreport" src-info="bibtex:line-23371" type="sharef:report">
		<names type="sharef: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 type="sharef:placePublished">Redmond, Washington</address>
		<publisher type="sharef:institution">Microsoft Corporation</publisher>
		<title type="sharef:primaryTitle">Generic Schema Matching with Cupid</title>
		<field type="bibtex:topic">cupid[1]</field>
		<identifier type="sharef:uri" resourceType="application/pdf">http://www.sice.umkc.edu/~leeyu/class/CS690L/Reference/Cupid.pdf</identifier>
	</reference>
	<reference name="ham92" src="bibtex:techreport" src-info="bibtex:line-23383" type="sharef:report">
		<names type="sharef:author">
			<person>
				<givenname>Eric</givenname>
				<surname>Hamilton</surname>
			</person>
		</names>
		<date value="1992-09"/>
		<address type="sharef:placePublished">Milpitas, California</address>
		<publisher type="sharef:institution">C-Cube Microsystems</publisher>
		<title type="sharef:primaryTitle">JPEG File Interchange Format (Version 1.02)</title>
		<field type="bibtex:topic">jpeg[0.8] jfif[1]</field>
	</reference>
	<reference name="wau94" src="bibtex:techreport" src-info="bibtex:line-23393" type="sharef:report">
		<names type="sharef:author">
			<person>
				<givenname>Andrew</givenname>
				<surname>Waugh</surname>
			</person>
		</names>
		<date value="1994-03"/>
		<address type="sharef:placePublished">Sydney, Australia</address>
		<field type="bibtex:index">X.500</field>
		<publisher type="sharef:institution">CSIRO, Division of Information Technology</publisher>
		<number>TR-SA-94-03</number>
		<title type="sharef:primaryTitle">X.500 and the 1993 Standard</title>
	</reference>
	<reference name="koe96" src="bibtex:techreport" src-info="bibtex:line-23404" type="sharef:report">
		<names type="sharef:author">
			<person>
				<givenname>Eckhart</givenname>
				<surname>Koerner</surname>
			</person>
		</names>
		<date value="1996-09"/>
		<address type="sharef:placePublished">Liège, Belgium</address>
		<field type="bibtex:index">TINA, group management, multimedia, collaboration</field>
		<publisher type="sharef: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 type="sharef:primaryTitle">Group Management for a Multimedia Collaboration Service</title>
	</reference>
	<reference name="tre95" src="bibtex:techreport" src-info="bibtex:line-23415" type="sharef:report">
		<names type="sharef:author">
			<person>
				<givenname>Gene</givenname>
				<surname>Trent</surname>
			</person>
			<person>
				<givenname>Mark</givenname>
				<surname>Sake</surname>
			</person>
		</names>
		<date value="1995-02"/>
		<address type="sharef:placePublished">Mountain View, California</address>
		<field type="bibtex:index">WWW, HTTP, performance evaluation, benchmark</field>
		<publisher type="sharef:institution">Silicon Graphics, Inc.</publisher>
		<title type="sharef:primaryTitle">WebSTONE: The First Generation in HTTP Server Benchmarking</title>
	</reference>
	<reference name="pad95" src="bibtex:techreport" src-info="bibtex:line-23425" type="sharef:report">
		<names type="sharef: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="sharef:institution">University of California, Berkeley</publisher>
		<number>CSD-95-875</number>
		<title type="sharef:primaryTitle">Improving World Wide Web Latency</title>
	</reference>
	<reference name="sch91" src="bibtex:techreport" src-info="bibtex:line-23435" type="sharef:report">
		<names type="sharef:author">
			<person>
				<givenname>Eve M.</givenname>
				<surname>Schooler</surname>
			</person>
		</names>
		<date value="1991-11"/>
		<address type="sharef:placePublished">Marina del Rey, California</address>
		<field type="bibtex:index">mbone</field>
		<publisher type="sharef:institution">University of Southern California, Information Sciences Institute</publisher>
		<number>ISI/RR-91-289</number>
		<title type="sharef:primaryTitle">A Distributed Architecture for Multimedia Conference Control</title>
	</reference>
	<reference name="gre85" src="bibtex:techreport" src-info="bibtex:line-23446" type="sharef:report">
		<names type="sharef: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 type="sharef:placePublished">Cambridge, UK</address>
		<field type="bibtex:index">CES</field>
		<publisher type="sharef:institution">Massachusetts Institute of Technology</publisher>
		<number>MIT/LCS/TM-295</number>
		<title type="sharef:primaryTitle">Atomic Data Abstractions in a Distributed Collaborative Editing System</title>
	</reference>
	<reference name="koc95a" src="bibtex:techreport" src-info="bibtex:line-23457" type="sharef:report">
		<names type="sharef:author">
			<person>
				<givenname>Michael</givenname>
				<surname>Koch</surname>
			</person>
		</names>
		<date value="1995-08"/>
		<address type="sharef:placePublished">Munich, Germany</address>
		<field type="bibtex:index">IRIS, groupware, collaborative editing</field>
		<publisher type="sharef:institution">Technische Universität München</publisher>
		<number>TUM-I9524</number>
		<title type="sharef:primaryTitle">The Collaborative Multi-User Editor Project Iris</title>
	</reference>
	<reference name="hef95" src="bibtex:techreport" src-info="bibtex:line-23468" type="sharef:report">
		<names type="sharef:author">
			<person>
				<givenname>Wendy</givenname>
				<surname>Heffner</surname>
			</person>
		</names>
		<date value="1995-05"/>
		<address type="sharef:placePublished">Berkeley, California</address>
		<field type="bibtex:index">Tenet, RCAP2, multicast, target sets, RSVP, ST-II, SCMP</field>
		<publisher type="sharef:institution">International Computer Science Institute</publisher>
		<number>TR-95-022</number>
		<title type="sharef:primaryTitle">Scaling Issues in the Design and Implementation of the Tenet RCAP2 Signaling Protocol</title>
	</reference>
	<reference name="ban94" src="bibtex:techreport" src-info="bibtex:line-23479" type="sharef:report">
		<names type="sharef: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 type="sharef:placePublished">Berkeley, California</address>
		<field type="bibtex:index">Tenet, ATM, FDDI, RTIP, RMTP, CMTP</field>
		<publisher type="sharef:institution">International Computer Science Institute</publisher>
		<number>TR-94-059</number>
		<title type="sharef:primaryTitle">The Tenet Real-Time Protocol Suite: Design, Implementation, and Experiences</title>
	</reference>
	<reference name="szy93b" src="bibtex:techreport" src-info="bibtex:line-23490" type="sharef:report">
		<names type="sharef:author">
			<person>
				<givenname>Clemens</givenname>
				<surname>Szyperski</surname>
			</person>
			<person>
				<givenname>Giorgio</givenname>
				<surname>Ventre</surname>
			</person>
		</names>
		<date value="1993-01"/>
		<address type="sharef:placePublished">Berkeley, California</address>
		<field type="bibtex:index">MIM, CSCW</field>
		<publisher type="sharef:institution">International Computer Science Institute</publisher>
		<number>TR-93-006</number>
		<title type="sharef:primaryTitle">A Characterization of Multi-Party Interactive Multimedia Applications</title>
	</reference>
	<reference name="eff93" src="bibtex:techreport" src-info="bibtex:line-23501" type="sharef:report">
		<names type="sharef: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 type="sharef:placePublished">Berkeley, California</address>
		<field type="bibtex:index">Tenet, multicast, target sets, routing</field>
		<publisher type="sharef:institution">International Computer Science Institute</publisher>
		<number>TR-93-056</number>
		<title type="sharef:primaryTitle">Dynamic Join and Leave for Real-Time Multicast</title>
	</reference>
	<reference name="sam93a" src="bibtex:techreport" src-info="bibtex:line-23512" type="sharef:report">
		<names type="sharef:author">
			<person>
				<givenname>Michael</givenname>
				<surname>Sample</surname>
			</person>
		</names>
		<date value="1993-07"/>
		<address type="sharef:placePublished">Vancouver, Canada</address>
		<field type="bibtex:index">snacc, ASN.1</field>
		<publisher type="sharef:institution">University of British Columbia</publisher>
		<title type="sharef:primaryTitle">Snacc 1.1: A High Performance ASN.1 to C/C++ Compiler</title>
	</reference>
	<reference name="wil05g" src="bibtex:techreport" src-info="bibtex:line-23522" type="sharef:report">
		<names type="sharef: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 type="sharef:placePublished">Berne, Switzerland</address>
		<publisher type="sharef:institution">eCH</publisher>
		<number>eCH-0018</number>
		<title type="sharef:primaryTitle">XML Best Practices</title>
		<identifier type="sharef:uri">http://dret.net/netdret/publications#wil05g</identifier>
	</reference>
	<reference name="wil05h" src="bibtex:techreport" src-info="bibtex:line-23534" type="sharef:report">
		<names type="sharef:author">
			<person>
				<givenname>Erik</givenname>
				<surname>Wilde</surname>
			</person>
		</names>
		<date value="2006-11"/>
		<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 type="sharef:placePublished">Berne, Switzerland</address>
		<publisher type="sharef:institution">eCH</publisher>
		<number>eCH-0033</number>
		<title type="sharef:primaryTitle">Beschreibung von XML Namespaces</title>
		<identifier type="sharef:uri">http://dret.net/netdret/publications#wil05h</identifier>
	</reference>
	<reference name="wil05i" src="bibtex:techreport" src-info="bibtex:line-23546" type="sharef:report">
		<names type="sharef:author">
			<person>
				<givenname>Erik</givenname>
				<surname>Wilde</surname>
			</person>
		</names>
		<date value="2006-12"/>
		<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 type="sharef:placePublished">Berne, Switzerland</address>
		<publisher type="sharef:institution">eCH</publisher>
		<number>eCH-0035</number>
		<title type="sharef:primaryTitle">Design von XML Schemas</title>
		<identifier type="sharef:uri">http://dret.net/netdret/publications#wil05i</identifier>
	</reference>
	<reference name="wil05j" src="bibtex:techreport" src-info="bibtex:line-23558" type="sharef:report">
		<names type="sharef:author">
			<person>
				<givenname>Erik</givenname>
				<surname>Wilde</surname>
			</person>
		</names>
		<date value="2007-03"/>
		<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 type="sharef:placePublished">Berne, Switzerland</address>
		<publisher type="sharef:institution">eCH</publisher>
		<number>eCH-0036</number>
		<title type="sharef:primaryTitle">Modellierung für den XML-orientierten Datenaustausch</title>
		<identifier type="sharef:uri">http://dret.net/netdret/publications#wil05j</identifier>
	</reference>
	<reference name="wil06a" src="bibtex:techreport" src-info="bibtex:line-23570" type="sharef:report">
		<names type="sharef: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 type="sharef:placePublished">Berne, Switzerland</address>
		<publisher type="sharef:institution">eCH</publisher>
		<number>eCH-0050</number>
		<title type="sharef:primaryTitle">Hilfskomponenten zur Konstruktion von XML Schemas</title>
		<identifier type="sharef:uri">http://dret.net/netdret/publications#wil06a</identifier>
	</reference>
	<reference name="wil07d" src="bibtex:techreport" src-info="bibtex:line-23581" type="sharef:report">
		<names type="sharef: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 type="sharef:placePublished">Berkeley, California</address>
		<publisher type="sharef:institution">School of Information, UC Berkeley</publisher>
		<number>2007-001</number>
		<title type="sharef:primaryTitle">SPath: A Path Language for XML Schema</title>
		<field type="bibtex:topic">spath[1]</field>
		<identifier type="sharef:uri">http://dret.net/netdret/publications#wil07d</identifier>
		<identifier type="sharef:uri">http://repositories.cdlib.org/ischool/2007-001</identifier>
	</reference>
	<reference name="wil07n" src="bibtex:techreport" src-info="bibtex:line-23595" type="sharef:report">
		<names type="sharef:author">
			<person>
				<givenname>Erik</givenname>
				<surname>Wilde</surname>
			</person>
		</names>
		<date value="2007-11"/>
		<abstract>
			<richtext>
				<p>Integrating resources into the Web is an important aspect of making them accessible as part of this global information system. The integration of physical things into the Web so far has not been done on a large scale, which makes it harder to realize network effects that could emerge by the combination of today's Web content, and the integration of physical things into the Web. This paper presents a path towards a Web where physical objects are made available through RESTful principles. By using this architectural style for pervasive and ubiquitous computing scenarios, they will scale better, integrate better with other applications, and pave the path towards a "Web of Things" that seamlessly integrates conceptual and physical resources.</p>
			</richtext>
		</abstract>
		<address type="sharef:placePublished">Berkeley, California</address>
		<publisher type="sharef:institution">School of Information, UC Berkeley</publisher>
		<number>2007-015</number>
		<title type="sharef:primaryTitle">Putting Things to REST</title>
		<identifier type="sharef:uri">http://repositories.cdlib.org/ischool/2007-015</identifier>
		<identifier type="sharef:uri">http://dret.net/netdret/publications#wil07n</identifier>
	</reference>
	<reference name="wil08o" src="bibtex:techreport" src-info="bibtex:line-23608" type="sharef:report">
		<names type="sharef:author">
			<person>
				<givenname>Erik</givenname>
				<surname>Wilde</surname>
			</person>
		</names>
		<date value="2008-08"/>
		<abstract>
			<richtext>
				<p>Location concepts are still not part of today's Web architecture, which means that applications must rely on higher-level specifications to use and provide location-oriented services. This problem can be approached in two different approaches, the first being a tightly coupled approach for scenarios targeting an integrated system architecture, and the second being a loosely coupled approach, being centered around cooperating services in the open world of the Web. This paper argues that the current specifications for location-oriented services cater mainly for the tightly coupled approach, whereas the loosely coupled approach is not yet addressed by available specifications. A more lightweight and loosely coupled approach to location-oriented services is the central issue for making the valuable data in geographic information systems better available on the Web. Only if location-oriented services can be used easily and cooperatively, today's rapidly evolving infrastructure of wireless data services and mobile devices can take full advantage of these services.</p>
			</richtext>
		</abstract>
		<address type="sharef:placePublished">Berkeley, California</address>
		<publisher type="sharef:institution">School of Information, UC Berkeley</publisher>
		<number>2008-026</number>
		<title type="sharef:primaryTitle">Open Location-Oriented Services for the Web</title>
		<identifier type="sharef:uri">http://repositories.cdlib.org/ischool/2008-026</identifier>
		<identifier type="sharef:uri">http://dret.net/netdret/publications#wil08o</identifier>
	</reference>
	<reference name="wil08d" src="bibtex:techreport" src-info="bibtex:line-23621" type="sharef:report">
		<names type="sharef:author">
			<person>
				<givenname>Erik</givenname>
				<surname>Wilde</surname>
			</person>
		</names>
		<date value="2008-02"/>
		<abstract>
			<richtext>
				<p>Location-awareness, in the form of location information about clients and location-based services provided by servers, is becoming increasingly important for networked communications in general, and wireless and mobile devices in particular. The current fragmented landscape of location concepts and location-awareness, however, is not suitable for handling location information on a Web scale. Providing users with mechanisms which allow them to control how they want to expose their location information, and thus allow control over how to share location information with others and services, is a crucial step for better location management for mobile devices. This paper presents a concept for representing location vocabularies, matching and mapping them, how these vocabularies can be used to support better privacy for users of location-based services, and better location sharing between users and services. The concept is based on a language for describing place name vocabularies, which we call "Place Markup Language (PlaceML)", and on various ways how these vocabularies can be used in a location-aware infrastructure of networked devices.</p>
			</richtext>
		</abstract>
		<address type="sharef:placePublished">Berkeley, California</address>
		<publisher type="sharef:institution">School of Information, UC Berkeley</publisher>
		<number>2008-016</number>
		<title type="sharef:primaryTitle">Location Management for Mobile Devices</title>
		<identifier type="sharef:uri">http://repositories.cdlib.org/ischool/2008-016</identifier>
		<identifier type="sharef:uri">http://dret.net/netdret/publications#wil08d</identifier>
	</reference>
	<reference name="wil08k" src="bibtex:techreport" src-info="bibtex:line-23634" type="sharef:report">
		<names type="sharef:author">
			<person>
				<givenname>Erik</givenname>
				<surname>Wilde</surname>
			</person>
			<person>
				<givenname>Igor</givenname>
				<surname>Pesenson</surname>
			</person>
		</names>
		<date value="2008-05"/>
		<abstract>
			<richtext>
				<p>Feeds have become an important information channel on the Web, but the management of feed metadata so far has received little attention. It is hard for feed publishers to manage and publish their feed information in a unified format, and for feed consumers to manage and use their feed subscription data across various feed readers, and to share it with other users. We present a system for managing feed metadata using feeds, which we call "feed feeds". Because these feeds are Atom feeds, the widely deployed Atom and AtomPub standards can be used to manage feed metadata, making feed management available through an established API.</p>
			</richtext>
		</abstract>
		<address type="sharef:placePublished">Berkeley, California</address>
		<publisher type="sharef:institution">School of Information, UC Berkeley</publisher>
		<number>2008-025</number>
		<title type="sharef:primaryTitle">Feed Feeds: Managing Feeds Using Feeds</title>
		<identifier type="sharef:uri">http://repositories.cdlib.org/ischool/2008-025</identifier>
		<identifier type="sharef:uri">http://dret.net/netdret/publications#wil08k</identifier>
	</reference>
	<reference name="wil09b" src="bibtex:techreport" src-info="bibtex:line-23647" type="sharef:report">
		<names type="sharef:author">
			<person>
				<givenname>Erik</givenname>
				<surname>Wilde</surname>
			</person>
			<person>
				<givenname>Anuradha</givenname>
				<surname>Roy</surname>
			</person>
		</names>
		<date value="2009-02"/>
		<abstract>
			<richtext>
				<p>The currently established formats for how a Web site can publish metadata about a site's pages, the robots.txt file and sitemaps, focus on how to provide information to crawlers about where to not go and where to go on a site. This is sufficient as input for crawlers, but does not allow Web sites to publish richer metadata about their site's structure, such as the navigational structure. This paper looks at the availability of Web site metadata on today's Web in terms of available information resources and quantitative aspects of their contents. Such an analysis of the available Web site metadata not only makes it easier to understand what data is available today; it also serves as the foundation for investigating what kind of information retrieval processes could be driven by that data, and what additional data could be provided by Web sites if they had richer data formats to publish metadata.</p>
			</richtext>
		</abstract>
		<address type="sharef:placePublished">Berkeley, California</address>
		<publisher type="sharef:institution">School of Information, UC Berkeley</publisher>
		<number>2009-028</number>
		<title type="sharef:primaryTitle">Web Site Metadata</title>
		<identifier type="sharef:uri">http://repositories.cdlib.org/ischool/2009-028</identifier>
		<identifier type="sharef:uri">http://dret.net/netdret/publications#wil09b</identifier>
	</reference>
	<reference name="wil09d" src="bibtex:techreport" src-info="bibtex:line-23660" type="sharef:report">
		<names type="sharef:author">
			<person>
				<givenname>Erik</givenname>
				<surname>Wilde</surname>
			</person>
			<person>
				<givenname>Eric C.</givenname>
				<surname>Kansa</surname>
			</person>
			<person>
				<givenname>Raymond</givenname>
				<surname>Yee</surname>
			</person>
		</names>
		<date value="2009-03"/>
		<abstract>
			<richtext>
				<p>The "Initial Implementing Guidance for the American Recovery and Reinvestment Act of 2009" provides guidance for a feed-based information dissemination architecture. In this report, we suggest some improvements and refinements of the initial guidelines, in the hope of paving the path for a more transparent and useful feed-based architecture. This report is meant as a preliminary guide to how the current guidelines could be made more specific and provide better guidance for providers and consumers of recovery act spending information. It is by no means intended as a complete or final set of recommendations.</p>
			</richtext>
		</abstract>
		<address type="sharef:placePublished">Berkeley, California</address>
		<publisher type="sharef:institution">School of Information, UC Berkeley</publisher>
		<number>2009-029</number>
		<title type="sharef:primaryTitle">Proposed Guideline Clarifications for American Recovery and Reinvestment Act of 2009</title>
		<identifier type="sharef:uri">http://repositories.cdlib.org/ischool/2009-029</identifier>
		<identifier type="sharef:uri">http://dret.net/netdret/publications#wil09d</identifier>
	</reference>
	<reference name="ala10c" src="bibtex:techreport" src-info="bibtex:line-23673" type="sharef:report">
		<names type="sharef:author">
			<person>
				<givenname>Rosa</givenname>
				<surname>Alarcón</surname>
			</person>
			<person>
				<givenname>Erik</givenname>
				<surname>Wilde</surname>
			</person>
		</names>
		<date value="2010-06"/>
		<abstract>
			<richtext>
				<p>RESTful services on the Web expose information through retrievable resource representations that represent self-describing descriptions of resources, and through the way how these resources are interlinked through the hyperlinks that can be found in those representations. This basic design of RESTful services means that for extracting the most useful information from a service, it is necessary to understand a service's representations, which means both the semantics in terms of describing a resource, and also its semantics in terms of describing its linkage with other resources. Based on the Resource Linking Language (ReLL), this paper describes a framework for how RESTful services can be described, and how these descriptions can then be used to harvest information from these services. Building on this framework, a layered model of RESTful service semantics allows to represent a service's information in RDF/OWL. Because REST is based on the linkage between resources, the same model can be used for aggregating and interlinking multiple services for extracting RDF data from sets of RESTful services.</p>
			</richtext>
		</abstract>
		<address type="sharef:placePublished">Berkeley, California</address>
		<publisher type="sharef:institution">School of Information, UC Berkeley</publisher>
		<number>2010-041</number>
		<title type="sharef:primaryTitle">From RESTful Services to RDF: Connecting the Web and the Semantic Web</title>
		<identifier type="sharef:uri">http://www.escholarship.org/uc/item/3425p9s7</identifier>
		<identifier type="sharef:uri">http://dret.net/netdret/publications#ala10c</identifier>
		<identifier type="sharef:uri">http://arxiv.org/abs/1006.2718v1</identifier>
	</reference>
	<reference name="yee10a" src="bibtex:techreport" src-info="bibtex:line-23687" type="sharef:report">
		<names type="sharef:author">
			<person>
				<givenname>Raymond</givenname>
				<surname>Yee</surname>
			</person>
			<person>
				<givenname>Eric C.</givenname>
				<surname>Kansa</surname>
			</person>
			<person>
				<givenname>Erik</givenname>
				<surname>Wilde</surname>
			</person>
		</names>
		<date value="2010-05"/>
		<abstract>
			<richtext>
				<p>Information about federal spending can affect national priorities and government processes, having impacts on society that few other data sources can rival. However, building effective open government and transparency mechanisms holds a host of technical, conceptual, and organizational challenges. To help guide development and deployment of future federal spending transparency systems, this paper explores the effectiveness of accountability measures deployed for the American Recovery and Reinvestment Act of 2009 ("Recovery Act" or "ARRA"). The Recovery Act provides an excellent case study to better understand the general requirements for designing and deploying "Open Government" systems. In this document, we show specific examples of how problems in data quality, service design, and systems architecture limit the effectiveness of ARRA's promised transparency. We also highlight organizational and incentive issues that impede transparency, and point to design processes as well as general architectural principles needed to better realize the goals advanced by open government advocates.</p>
			</richtext>
		</abstract>
		<address type="sharef:placePublished">Berkeley, California</address>
		<publisher type="sharef:institution">School of Information, UC Berkeley</publisher>
		<number>2010-040</number>
		<title type="sharef:primaryTitle">Improving Federal Spending Transparency: Lessons Drawn from Recovery.gov</title>
		<identifier type="sharef:uri">http://escholarship.org/uc/item/7tw2w9wx</identifier>
		<identifier type="sharef:uri">http://dret.net/netdret/publications#yee10a</identifier>
	</reference>
	<reference name="wil09g" src="bibtex:techreport" src-info="bibtex:line-23700" type="sharef:report">
		<names type="sharef:author">
			<person>
				<givenname>Erik</givenname>
				<surname>Wilde</surname>
			</person>
			<person>
				<givenname>Eric C.</givenname>
				<surname>Kansa</surname>
			</person>
			<person>
				<givenname>Raymond</givenname>
				<surname>Yee</surname>
			</person>
		</names>
		<date value="2009-10"/>
		<abstract>
			<richtext>
				<p>One of the main goals of the Recovery.gov Web site is provide information about how the money for the American Recovery and Reinvestment Act (ARRA) of 2009 is allocated and spent. In this report, we propose a reporting architecture that would focus on the reporting services rather than the Web site and page design, and the uses these Web services to build the user-facing part of ARRA reporting. Our proposed architecture is based on simple and well-established Web technologies, and the main goal of this architecture is to provide citizens and watchdog groups simple and easy access to machine-readable data. Our architecture uses a more sophisticated than simple downloads of data files, and is based on the principles of Representational State Transfer (REST) and uses established and widely supported Web technologies such as feeds and XML. We argue that such an architecture is easy to design and implement, easy to understand for users, and easy to work with for those who want to access ARRA reporting data in a machine-readable way.</p>
			</richtext>
		</abstract>
		<address type="sharef:placePublished">Berkeley, California</address>
		<publisher type="sharef:institution">School of Information, UC Berkeley</publisher>
		<number>2009-035</number>
		<title type="sharef:primaryTitle">Web Services for Recovery.gov</title>
		<identifier type="sharef:uri">http://repositories.cdlib.org/ischool/2009-035</identifier>
		<identifier type="sharef:uri">http://dret.net/netdret/publications#wil09g</identifier>
	</reference>
	<reference name="gom09" src="bibtex:techreport" src-info="bibtex:line-23713" type="sharef:report">
		<names type="sharef:author">
			<person>
				<givenname>Joshua</givenname>
				<surname>Gomez</surname>
			</person>
			<person>
				<givenname>Travis</givenname>
				<surname>Pinnick</surname>
			</person>
			<person>
				<givenname>Ashkan</givenname>
				<surname>Soltani</surname>
			</person>
		</names>
		<date value="2009-10"/>
		<abstract>
			<richtext>
				<p>Online privacy and behavioral profiling are of growing concern among both consumers and government officials. In this report, we examine both the data handling practices of popular websites and the concerns of consumers in an effort to identify problematic practices. We analyze the policies of the 50 most visited websites to better understand disclosures about the types of data collected about users, how that information is used, and with whom it is shared. We also look at specific practices such as sharing information with affiliates and third-party tracking. To understand user concerns and knowledge of data collection we look at surveys and polls conducted by previous privacy researchers. We look at records of complaints and inquiries filed with privacy watchdog organizations such as the Federal Trade Commission, the Privacy Rights Clearinghouse, The California Office of Privacy Protection, and TRUSTe. Finally, to gain some insight into what aspects of data collection users are being made aware of, we look at news articles from three major newspapers for topics related to Internet privacy. Based on our findings we make recommendations for website operators, government regulators, as well as technology developers.</p>
			</richtext>
		</abstract>
		<address type="sharef:placePublished">Berkeley, California</address>
		<publisher type="sharef:institution">School of Information, UC Berkeley</publisher>
		<number>2009-037</number>
		<title type="sharef:primaryTitle">KnowPrivacy</title>
		<identifier type="sharef:uri">http://repositories.cdlib.org/ischool/2009-037</identifier>
	</reference>
	<reference name="dot10a" src="bibtex:techreport" src-info="bibtex:line-23725" type="sharef:report">
		<names type="sharef:author">
			<person>
				<givenname>Nick</givenname>
				<surname>Doty</surname>
			</person>
			<person>
				<givenname>Deirdre K.</givenname>
				<surname>Mulligan</surname>
			</person>
			<person>
				<givenname>Erik</givenname>
				<surname>Wilde</surname>
			</person>
		</names>
		<date value="2010-02"/>
		<abstract>
			<richtext>
				<p>The W3C's Geolocation API may rapidly standardize the transmission of location information on the Web, but, in dealing with such sensitive information, it also raises serious privacy concerns. We analyze the manner and extent to which the current W3C Geolocation API provides mechanisms to support privacy. We propose a privacy framework for the consideration of location information and use it to evaluate the W3C Geolocation API, both the specification and its use in the wild, and recommend some modifications to the API as a result of our analysis.</p>
			</richtext>
		</abstract>
		<address type="sharef:placePublished">Berkeley, California</address>
		<publisher type="sharef:institution">School of Information, UC Berkeley</publisher>
		<number>2010-038</number>
		<title type="sharef:primaryTitle">Privacy Issues of the W3C Geolocation API</title>
		<identifier type="sharef:uri">http://escholarship.org/uc/item/0rp834wf</identifier>
		<identifier type="sharef:uri">http://dret.net/netdret/publications#dot10a</identifier>
		<identifier type="sharef:uri">http://arxiv.org/abs/1003.1775v1</identifier>
	</reference>
	<reference name="wil09e" src="bibtex:techreport" src-info="bibtex:line-23739" type="sharef:report">
		<names type="sharef:author">
			<person>
				<givenname>Erik</givenname>
				<surname>Wilde</surname>
			</person>
		</names>
		<date value="2009-04"/>
		<abstract>
			<richtext>
				<p>Many Web-based data sources and services are available as feeds, a model that provides consumers with a loosely coupled way of interacting with providers. The current feed model is limited in its capabilities, however. Though it is simple to implement and scales well, it cannot be transferred to a wider range of application scenarios. This paper conceptualizes feeds as a way to serialize query results, describes the current hardcoded query semantics of such a perspective, and surveys the ways in which extensions of this hardcoded model have been proposed or implemented. Our generalized view of feeds as query result serializations has implications for the applicability of feeds as a generic Web service for any collection that is providing access to individual information items. As one interesting and compelling class of applications, we describe a simple way in which a query-based approach to feeds can be used to support location-based services.</p>
			</richtext>
		</abstract>
		<address type="sharef:placePublished">Berkeley, California</address>
		<publisher type="sharef:institution">School of Information, UC Berkeley</publisher>
		<number>2009-030</number>
		<title type="sharef:primaryTitle">Feeds as Query Result Serializations</title>
		<identifier type="sharef:uri">http://repositories.cdlib.org/ischool/2009-030</identifier>
		<identifier type="sharef:uri">http://dret.net/netdret/publications#wil09e</identifier>
		<identifier type="sharef:uri">http://arxiv.org/abs/0911.2193v1</identifier>
	</reference>
	<reference name="wil07k" src="bibtex:techreport" src-info="bibtex:line-23753" type="sharef:report">
		<names type="sharef:author">
			<person>
				<givenname>Ryan</givenname>
				<surname>Shaw</surname>
			</person>
			<person>
				<givenname>Erik</givenname>
				<surname>Wilde</surname>
			</person>
		</names>
		<date value="2007-08"/>
		<abstract>
			<richtext>
				<p>Annotation of multimedia resources supports a wide range of applications, ranging from associating metadata with multimedia resources or parts of these resources, to the collaborative use of multimedia resources through the act of distributed authoring and annotation of resources. Most annotation frameworks, however, are based on a closed approach, where the annotations data is limited to the annotation framework, and cannot readily be reused in other application scenarios. We present a declarative approach to multimedia annotations, which represents the annotations in an XML format independent from the multimedia resources. Using this declarative approach, multimedia annotations can be used in an easier and more flexible way, enabling application scenarios such as third-party annotations and annotation aggregation and filtering.</p>
			</richtext>
		</abstract>
		<address type="sharef:placePublished">Berkeley, California</address>
		<publisher type="sharef:institution">School of Information, UC Berkeley</publisher>
		<number>2007-014</number>
		<title type="sharef:primaryTitle">Web-Style Multimedia Annotations</title>
		<identifier type="sharef:uri">http://repositories.cdlib.org/ischool/2007-014</identifier>
		<identifier type="sharef:uri">http://dret.net/netdret/publications#wil07k</identifier>
	</reference>
	<reference name="wil94c" src="bibtex:techreport" src-info="bibtex:line-23766" type="sharef:report">
		<names type="sharef: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 type="sharef:placePublished">Zürich, Switzerland</address>
		<publisher type="sharef:institution">Computer Engineering and Networks Laboratory, ETH Zürich</publisher>
		<title type="sharef:primaryTitle">Modelling Groups for Group Communications</title>
		<identifier type="sharef:uri">http://dret.net/netdret/publications#wil94c</identifier>
	</reference>
	<reference name="wil94b" src="bibtex:techreport" src-info="bibtex:line-23777" type="sharef:report">
		<names type="sharef: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 type="sharef:placePublished">Zürich, Switzerland</address>
		<publisher type="sharef:institution">Computer Engineering and Networks Laboratory, ETH Zürich</publisher>
		<title type="sharef:primaryTitle">Supporting CSCW Applications with an Efficient Shared Information Space</title>
		<identifier type="sharef:uri">http://dret.net/netdret/publications#wil94b</identifier>
	</reference>
	<reference name="wil92" src="bibtex:techreport" src-info="bibtex:line-23788" type="sharef:report">
		<names type="sharef:author">
			<person>
				<givenname>Erik</givenname>
				<surname>Wilde</surname>
			</person>
		</names>
		<date value="1992-05"/>
		<address type="sharef:placePublished">Zürich, Switzerland</address>
		<publisher type="sharef:institution">Computer Engineering and Networks Laboratory, ETH Zürich</publisher>
		<title type="sharef:primaryTitle">Konzept eines mehrbenutzerfähigen Multimedia-Editors</title>
		<identifier type="sharef:uri">http://dret.net/netdret/publications#wil92</identifier>
	</reference>
	<reference name="wil01f" src="bibtex:techreport" src-info="bibtex:line-23798" type="sharef:report">
		<names type="sharef: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 type="sharef:placePublished">Zürich, Switzerland</address>
		<publisher type="sharef:institution">Computer Engineering and Networks Laboratory, ETH Zürich</publisher>
		<number>TIK Report 102</number>
		<title type="sharef:primaryTitle">Routed Message Driven Beans: A new Abstraction for using EJBs</title>
		<field type="bibtex:topic">ejb[0.8]</field>
		<identifier type="sharef:uri">http://dret.net/netdret/publications#wil01f</identifier>
	</reference>
	<reference name="wil02b" src="bibtex:techreport" src-info="bibtex:line-23811" type="sharef:report">
		<names type="sharef: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 type="sharef:placePublished">Zürich, Switzerland</address>
		<publisher type="sharef:institution">Computer Engineering and Networks Laboratory, ETH Zürich</publisher>
		<number>TIK Report 124</number>
		<title type="sharef:primaryTitle">Picture Metadata and its Associations: Using Web Technologies for Representing Semantics</title>
		<identifier type="sharef:uri">http://dret.net/netdret/publications#wil02b</identifier>
	</reference>
	<reference name="obe02" src="bibtex:techreport" src-info="bibtex:line-23823" type="sharef:report">
		<names type="sharef: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 type="sharef:placePublished">Zürich, Switzerland</address>
		<publisher type="sharef:institution">Computer Engineering and Networks Laboratory, ETH Zürich</publisher>
		<number>TIK Report 125</number>
		<title type="sharef:primaryTitle">Extended Link Visualization with DHTML: The Web as an Open Hypermedia System</title>
		<identifier type="sharef:uri">http://dret.net/netdret/publications#obe02</identifier>
	</reference>
	<reference name="wil02d" src="bibtex:techreport" src-info="bibtex:line-23835" type="sharef:report">
		<names type="sharef: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 type="sharef:placePublished">Zürich, Switzerland</address>
		<publisher type="sharef:institution">Computer Engineering and Networks Laboratory, ETH Zürich</publisher>
		<number>TIK Report 134</number>
		<title type="sharef:primaryTitle">Openly Accessing Linkbases</title>
		<field type="bibtex:topic">xlink[0.9]</field>
		<identifier type="sharef:uri">http://dret.net/netdret/publications#wil01d</identifier>
	</reference>
	<reference name="wil02c" src="bibtex:techreport" src-info="bibtex:line-23848" type="sharef:report">
		<names type="sharef: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 type="sharef:placePublished">Zürich, Switzerland</address>
		<publisher type="sharef:institution">Computer Engineering and Networks Laboratory, ETH Zürich</publisher>
		<number>TIK Report 143</number>
		<title type="sharef:primaryTitle">Protocol Considerations for Web Linkbase Access</title>
		<field type="bibtex:topic">xlink[0.9]</field>
		<identifier type="sharef:uri">http://dret.net/netdret/publications#wil02c</identifier>
	</reference>
	<reference name="wil02i" src="bibtex:techreport" src-info="bibtex:line-23861" type="sharef:report">
		<names type="sharef: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 type="sharef:placePublished">Zürich, Switzerland</address>
		<publisher type="sharef:institution">Computer Engineering and Networks Laboratory, ETH Zürich</publisher>
		<number>TIK Report 148</number>
		<title type="sharef:primaryTitle">A Proposal for XLink Infoset Contributions</title>
		<field type="bibtex:topic">xlink[0.9]</field>
		<identifier type="sharef:uri">http://dret.net/netdret/publications#wil02i</identifier>
	</reference>
	<reference name="wil02k" src="bibtex:techreport" src-info="bibtex:line-23874" type="sharef:report">
		<names type="sharef:author">
			<person>
				<givenname>Erik</givenname>
				<surname>Wilde</surname>
			</person>
		</names>
		<date value="2002-05"/>
		<abstract>
			<richtext>
				<p>PDF in its current for has rather weak support for annotations. This paper describes a usage scenario and how advanced annotations support could make using PDF (and possibly other Adobe applications) more productive. Starting from these observations, different problems are described which could be solved based on different evolutionary steps of the annotation architecture, which has been dubbed "Adobe Advanced Annotations (A³)". Following this scenario, some design approaches and a number of implementation issues are discussed.</p>
			</richtext>
		</abstract>
		<publisher type="sharef:institution">Computer Engineering and Networks Laboratory, ETH Zürich</publisher>
		<title type="sharef:primaryTitle">Adobe Advanced Annotations (A³)</title>
		<field type="bibtex:topic">xlink[0.7] pdf[0.8]</field>
		<identifier type="sharef:uri">http://dret.net/netdret/publications#wil02k</identifier>
	</reference>
	<reference name="wil03c" src="bibtex:techreport" src-info="bibtex:line-23885" type="sharef:report">
		<names type="sharef: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 type="sharef:placePublished">Zürich, Switzerland</address>
		<publisher type="sharef:institution">Computer Engineering and Networks Laboratory, ETH Zürich</publisher>
		<number>TIK Report 160</number>
		<title type="sharef:primaryTitle">The Extensible XML Information Set</title>
		<field type="bibtex:topic">exis[1] xmlinfoset[0.8]</field>
		<identifier type="sharef:uri">http://dret.net/netdret/publications#wil03c</identifier>
	</reference>
	<reference name="mic06a" src="bibtex:techreport" src-info="bibtex:line-23898" type="sharef:report">
		<names type="sharef: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 type="sharef:placePublished">Zürich, Switzerland</address>
		<publisher type="sharef:institution">Computer Engineering and Networks Laboratory, ETH Zürich</publisher>
		<number>TIK Report 264</number>
		<title type="sharef:primaryTitle">Opening XML Schema's Data Model to XPath 2.0</title>
		<field type="bibtex:topic">spath[0.8] scx[0.9]</field>
		<identifier type="sharef:uri" resourceType="application/pdf">ftp://ftp.tik.ee.ethz.ch/pub/publications/TIK-Report-264.pdf</identifier>
	</reference>
	<reference name="mic06b" src="bibtex:techreport" src-info="bibtex:line-23911" type="sharef:report">
		<names type="sharef: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. As 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 type="sharef:placePublished">Zürich, Switzerland</address>
		<publisher type="sharef:institution">Computer Engineering and Networks Laboratory, ETH Zürich</publisher>
		<number>TIK Report 265</number>
		<title type="sharef:primaryTitle">XML Schema Editors — A Comparison of Real-World XML Schema Visualizations</title>
		<field type="bibtex:topic">xsd[0.8]</field>
		<identifier type="sharef:uri">http://dret.net/netdret/publications#mic06b</identifier>
	</reference>
	<reference name="wil06m" src="bibtex:techreport" src-info="bibtex:line-23924" type="sharef:report">
		<names type="sharef: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 type="sharef:placePublished">Zürich, Switzerland</address>
		<publisher type="sharef:institution">Computer Engineering and Networks Laboratory, ETH Zürich</publisher>
		<number>TIK Report 257</number>
		<title type="sharef:primaryTitle">Model Mapping in XML-Oriented Environments</title>
		<identifier type="sharef:uri">http://dret.net/netdret/publications#wil06m</identifier>
	</reference>
	<reference name="wil06f" src="bibtex:techreport" src-info="bibtex:line-23936" type="sharef:report">
		<names type="sharef: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 type="sharef:placePublished">Zürich, Switzerland</address>
		<publisher type="sharef:institution">Computer Engineering and Networks Laboratory, ETH Zürich</publisher>
		<number>TIK Report 245</number>
		<title type="sharef:primaryTitle">Knowledge Organization Mashups</title>
		<identifier type="sharef:uri">http://dret.net/netdret/publications#wil06f</identifier>
	</reference>
	<reference name="wil06d" src="bibtex:techreport" src-info="bibtex:line-23948" type="sharef:report">
		<names type="sharef: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 type="sharef:placePublished">Zürich, Switzerland</address>
		<publisher type="sharef:institution">Computer Engineering and Networks Laboratory, ETH Zürich</publisher>
		<number>TIK Report 244</number>
		<title type="sharef:primaryTitle">The Case for Conceptual Modeling for XML</title>
		<identifier type="sharef:uri">http://dret.net/netdret/publications#wil06d</identifier>
	</reference>
	<reference name="wil06c" src="bibtex:techreport" src-info="bibtex:line-23960" type="sharef:report">
		<names type="sharef: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 type="sharef:placePublished">Zürich, Switzerland</address>
		<publisher type="sharef:institution">Computer Engineering and Networks Laboratory, ETH Zürich</publisher>
		<number>TIK Report 242</number>
		<title type="sharef:primaryTitle">XML-Centric Application Development</title>
		<identifier type="sharef:uri">http://dret.net/netdret/publications#wil06c</identifier>
	</reference>
	<reference name="wil05o" src="bibtex:techreport" src-info="bibtex:line-23972" type="sharef:report">
		<names type="sharef: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 type="sharef:placePublished">Zürich, Switzerland</address>
		<publisher type="sharef:institution">Computer Engineering and Networks Laboratory, ETH Zürich</publisher>
		<number>TIK Report 224</number>
		<title type="sharef:primaryTitle">Shared Bibliographies as Hypertext</title>
		<identifier type="sharef:uri">http://dret.net/netdret/publications#wil05o</identifier>
	</reference>
	<reference name="wil05k" src="bibtex:techreport" src-info="bibtex:line-23984" type="sharef:report">
		<names type="sharef: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 type="sharef:placePublished">Zürich, Switzerland</address>
		<publisher type="sharef:institution">Computer Engineering and Networks Laboratory, ETH Zürich</publisher>
		<number>TIK Report 213</number>
		<title type="sharef:primaryTitle">ShaRef: XML-Centric Software Design</title>
		<identifier type="sharef:uri">http://dret.net/netdret/publications#wil05k</identifier>
	</reference>
	<reference name="wil05e" src="bibtex:techreport" src-info="bibtex:line-23996" type="sharef:report">
		<names type="sharef: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 type="sharef:placePublished">Zürich, Switzerland</address>
		<publisher type="sharef:institution">Computer Engineering and Networks Laboratory, ETH Zürich</publisher>
		<number>TIK Report 212</number>
		<title type="sharef:primaryTitle">Organizing Federal E-Government Schemas</title>
		<identifier type="sharef:uri">http://dret.net/netdret/publications#wil05e</identifier>
	</reference>
	<reference name="wil04h" src="bibtex:techreport" src-info="bibtex:line-24008" type="sharef:report">
		<names type="sharef: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 type="sharef:placePublished">Zürich, Switzerland</address>
		<publisher type="sharef:institution">Computer Engineering and Networks Laboratory, ETH Zürich</publisher>
		<number>TIK Report 194</number>
		<title type="sharef:primaryTitle">Usage and Management of Collections of References</title>
		<identifier type="sharef:uri">http://dret.net/netdret/publications#wil04h</identifier>
	</reference>
	<reference name="wil04f" src="bibtex:techreport" src-info="bibtex:line-24020" type="sharef:report">
		<names type="sharef: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 type="sharef:placePublished">Zürich, Switzerland</address>
		<publisher type="sharef:institution">Computer Engineering and Networks Laboratory, ETH Zürich</publisher>
		<number>TIK Report 190</number>
		<title type="sharef:primaryTitle">Networking Metaphors for E-Commerce</title>
		<identifier type="sharef:uri">http://dret.net/netdret/publications#wil04f</identifier>
	</reference>
	<reference name="wil03i" src="bibtex:techreport" src-info="bibtex:line-24032" type="sharef:report">
		<names type="sharef:author">
			<person>
				<givenname>Erik</givenname>
				<surname>Wilde</surname>
			</person>
		</names>
		<date value="2003-06"/>
		<address type="sharef:placePublished">Zürich, Switzerland</address>
		<publisher type="sharef:institution">Computer Engineering and Networks Laboratory, ETH Zürich</publisher>
		<number>TIK Report 172</number>
		<title type="sharef:primaryTitle">Character Repertoire Validation for XML (CRVX) Version 1.0</title>
		<field type="bibtex:topic">crvx[1]</field>
		<identifier type="sharef:uri">http://dret.net/netdret/publications#wil03i</identifier>
	</reference>
	<reference name="wil03n" src="bibtex:techreport" src-info="bibtex:line-24044" type="sharef:report">
		<names type="sharef:author">
			<person>
				<givenname>Erik</givenname>
				<surname>Wilde</surname>
			</person>
		</names>
		<date value="2003-08"/>
		<address type="sharef:placePublished">Santa Clara, California</address>
		<publisher type="sharef:institution">Computer Engineering and Networks Laboratory, ETH Zürich</publisher>
		<title type="sharef:primaryTitle">Position Paper for the W3C Workshop on Binary Interchange of XML Information Item Sets</title>
		<identifier type="sharef:uri">http://dret.net/netdret/publications#wil03n</identifier>
	</reference>
	<reference name="sti03b" src="bibtex:techreport" src-info="bibtex:line-24054" type="sharef:report">
		<names type="sharef: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 type="sharef:placePublished">Zürich, Switzerland</address>
		<publisher type="sharef:institution">Computer Engineering and Networks Laboratory, ETH Zürich</publisher>
		<number>TIK Report 166</number>
		<title type="sharef:primaryTitle">XML Schema Compact Syntax (XSCS) Version 1.0</title>
		<field type="bibtex:topic">xscs[1]</field>
		<identifier type="sharef:uri">http://dret.net/netdret/publications#sti03b</identifier>
	</reference>
	<reference name="wil96a" src="bibtex:techreport" src-info="bibtex:line-24067" type="sharef:report">
		<names type="sharef: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 type="sharef:placePublished">Zürich, Switzerland</address>
		<field type="bibtex:index">GMS, GAP, ASN.1</field>
		<publisher type="sharef:institution">Computer Engineering and Networks Laboratory, ETH Zürich</publisher>
		<number>TIK Report 15</number>
		<title type="sharef:primaryTitle">Specification of GMS Access Protocol (GAP) Version 1.0</title>
		<identifier type="sharef:uri">http://dret.net/netdret/publications#wil96a</identifier>
	</reference>
	<reference name="wil96c" src="bibtex:techreport" src-info="bibtex:line-24080" type="sharef:report">
		<names type="sharef: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 type="sharef:placePublished">Zürich, Switzerland</address>
		<field type="bibtex:index">GMS, GSP, ASN.1</field>
		<publisher type="sharef:institution">Computer Engineering and Networks Laboratory, ETH Zürich</publisher>
		<number>TIK Report 19</number>
		<title type="sharef:primaryTitle">Specification of GMS System Protocol (GSP) Version 1.0</title>
		<identifier type="sharef:uri">http://dret.net/netdret/publications#wil96c</identifier>
	</reference>
	<reference name="wil94a" src="bibtex:techreport" src-info="bibtex:line-24093" type="sharef:report">
		<names type="sharef: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 type="sharef:placePublished">Zürich, Switzerland</address>
		<field type="bibtex:index">MultimETH, groupware, collaborative editing</field>
		<publisher type="sharef:institution">Computer Engineering and Networks Laboratory, ETH Zürich</publisher>
		<number>TIK Report 18</number>
		<title type="sharef:primaryTitle">Multi-User Multimedia Editing with the MultimETH System</title>
		<identifier type="sharef:uri">http://dret.net/netdret/publications#wil94a</identifier>
	</reference>
	<reference name="rho07" src="bibtex:techreport" src-info="bibtex:line-24106" type="sharef:report">
		<names type="sharef:author">
			<person>
				<givenname>Katrina</givenname>
				<surname>Rhoads Lindholm</surname>
			</person>
		</names>
		<date value="2007-02"/>
		<abstract>
			<richtext>
				<p>Over the last several years we have seen a dramatic increase in the number of software applications offered over the internet. The ability to release user interface changes on a potentially daily basis has forced user experience professionals to rethink their traditional linear methodologies. With a new set of internet-based usability techniques as well as the remarkable ability to receive real-time, continuous feedback from end users, designers today have the potential to create the most usable and competitive software user interfaces to date.</p>
			</richtext>
		</abstract>
		<address type="sharef:placePublished">Berkeley, California</address>
		<publisher type="sharef:institution">School of Information, UC Berkeley</publisher>
		<number>2007-005</number>
		<title type="sharef:primaryTitle">The User Experience of Software-as-a-Service Applications</title>
		<field type="bibtex:topic">saas[0.9]</field>
		<identifier type="sharef:uri">http://repositories.cdlib.org/ischool/2007-005</identifier>
	</reference>
	<reference name="glu07a" src="bibtex:techreport" src-info="bibtex:line-24119" type="sharef:report">
		<names type="sharef:author">
			<person>
				<givenname>Robert J.</givenname>
				<surname>Glushko</surname>
			</person>
			<person>
				<givenname>Lindsay</givenname>
				<surname>Tabas</surname>
			</person>
		</names>
		<date value="2007-06"/>
		<abstract>
			<richtext>
				<p>Service management and design has thus far primarily focused on the interactions between employees and customers. This perspective holds that the quality of the "service experience" is determined by the customer during this final "service encounter" that takes place in the "front stage." This emphasis discounts the contribution of the activities in the "back stage" of the service value chain where materials or information needed by the front stage are processed. However, the vast increase in web-driven consumer self-service applications and other automated services requires new thinking about service design and service quality. It is essential to consider the entire network of services that comprise the back and front stages as complementary parts of a "service system." We need new concepts and methods in service design that recognize how back stage information and processes can improve the front stage experience. This paper envisions a methodology for designing service systems that synthesizes (front-stage-oriented) user-centered design techniques with (back-stage) methods for designing information-intensive applications.</p>
			</richtext>
		</abstract>
		<address type="sharef:placePublished">Berkeley, California</address>
		<publisher type="sharef:institution">School of Information, UC Berkeley</publisher>
		<number>2007-013</number>
		<title type="sharef:primaryTitle">Bridging the "Front Stage" and "Back Stage" in Service System Design</title>
		<identifier type="sharef:uri">http://repositories.cdlib.org/ischool/2007-013</identifier>
	</reference>
	<reference name="lub93a" src="bibtex:techreport" src-info="bibtex:line-24131" type="sharef:report">
		<names type="sharef: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 type="sharef:placePublished">Zürich, Switzerland</address>
		<field type="bibtex:index">MultimETH</field>
		<publisher type="sharef:institution">Computer Engineering and Networks Laboratory, ETH Zürich</publisher>
		<title type="sharef:primaryTitle">Schlussbericht zum ZBF-Projekt 224Z (MultimETH): Bericht</title>
		<identifier type="sharef:uri">http://dret.net/netdret/publications#lub93a</identifier>
	</reference>
	<reference name="lub93b" src="bibtex:techreport" src-info="bibtex:line-24142" type="sharef:report">
		<names type="sharef: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 type="sharef:placePublished">Zürich, Switzerland</address>
		<field type="bibtex:index">MultimETH</field>
		<publisher type="sharef:institution">Computer Engineering and Networks Laboratory, ETH Zürich</publisher>
		<title type="sharef:primaryTitle">Schlussbericht zum ZBF-Projekt 224Z (MultimETH): Benutzerhandbuch</title>
		<identifier type="sharef:uri">http://dret.net/netdret/publications#lub93b</identifier>
	</reference>
	<reference name="lub93c" src="bibtex:techreport" src-info="bibtex:line-24153" type="sharef:report">
		<names type="sharef: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 type="sharef:placePublished">Zürich, Switzerland</address>
		<field type="bibtex:index">MultimETH</field>
		<publisher type="sharef:institution">Computer Engineering and Networks Laboratory, ETH Zürich</publisher>
		<title type="sharef:primaryTitle">Schlussbericht zum ZBF-Projekt 224Z (MultimETH): Implementationsbeschreibung</title>
		<identifier type="sharef:uri">http://dret.net/netdret/publications#lub93c</identifier>
	</reference>
	<reference name="hen94b" src="bibtex:techreport" src-info="bibtex:line-24164" type="sharef:report">
		<names type="sharef:author">
			<person>
				<givenname>Lutz</givenname>
				<surname>Henckel</surname>
			</person>
		</names>
		<date value="1994-06"/>
		<address type="sharef:placePublished">Berlin, Germany</address>
		<field type="bibtex:index">CIO</field>
		<publisher type="sharef:institution">GMD FOKUS</publisher>
		<title type="sharef:primaryTitle">Multipeer Connection-mode Transport Service Definition based on the Group Communication Framework</title>
	</reference>
	<reference name="mat93" src="bibtex:techreport" src-info="bibtex:line-24174" type="sharef:report">
		<names type="sharef: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 type="sharef:placePublished">Liège, Belgium</address>
		<field type="bibtex:index">CIO</field>
		<publisher type="sharef:institution">Faculteé des Sciences Appliquées, Université de Liège</publisher>
		<number>R2060/ULg/CIO/IN/P/005</number>
		<title type="sharef:primaryTitle">A Group Communication Framework</title>
	</reference>
	<reference name="mat94c" src="bibtex:techreport" src-info="bibtex:line-24185" type="sharef:report">
		<names type="sharef: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 type="sharef:placePublished">Liège, Belgium</address>
		<field type="bibtex:index">CIO</field>
		<publisher type="sharef:institution">Faculteé des Sciences Appliquées, Université de Liège</publisher>
		<number>R2060/ULg/CIO/IN/P/007</number>
		<title type="sharef:primaryTitle">The CIO Multipeer Broadband Transport Service and the Group Communication Framework</title>
	</reference>
	<reference name="mat94d" src="bibtex:techreport" src-info="bibtex:line-24196" type="sharef:report">
		<names type="sharef: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 type="sharef:placePublished">Liège, Belgium</address>
		<field type="bibtex:index">CIO</field>
		<publisher type="sharef:institution">Faculteé des Sciences Appliquées, Université de Liège</publisher>
		<number>R2060/ULg/CIO/IN/P/008</number>
		<title type="sharef:primaryTitle">The Multipeer Data Transmission Transport Service and the Group Communication Framework</title>
	</reference>
	<reference name="mat94e" src="bibtex:techreport" src-info="bibtex:line-24207" type="sharef:report">
		<names type="sharef: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 type="sharef:placePublished">Liège, Belgium</address>
		<field type="bibtex:index">CIO, ETS</field>
		<publisher type="sharef:institution">Faculteé des Sciences Appliquées, Université de Liège</publisher>
		<number>R2060/ULg/CIO/IN/P/009</number>
		<title type="sharef:primaryTitle">The Enhanced Transport Service and the Group Communication Framework</title>
	</reference>
	<reference name="atm96" src="bibtex:techreport" src-info="bibtex:line-24218" type="sharef:report">
		<names type="sharef:author">
			<name>ATM Forum</name>
		</names>
		<date value="1996-07"/>
		<field type="bibtex:index">ATM, UNI 4.0</field>
		<publisher type="sharef:institution">ATM Forum</publisher>
		<annotation type="bibtex:note">
			<richtext>
				<p>Preliminary draft</p>
			</richtext>
		</annotation>
		<title type="sharef:primaryTitle">ATM User-Network Interface (UNI) Specification Version 4.0</title>
	</reference>
	<reference name="atm96b" src="bibtex:techreport" src-info="bibtex:line-24228" type="sharef:report">
		<names type="sharef:author">
			<name>ATM Forum</name>
		</names>
		<date value="1996-04"/>
		<field type="bibtex:index">ATM</field>
		<publisher type="sharef:institution">ATM Forum</publisher>
		<title type="sharef:primaryTitle">Traffic Management Specification, Version 4.0</title>
	</reference>
	<reference name="sam90a" src="bibtex:book" src-info="bibtex:line-24241" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Hanan</givenname>
				<surname>Samet</surname>
			</person>
		</names>
		<date value="1990"/>
		<address type="sharef:placePublished">Reading, Massachusetts</address>
		<identifier type="sharef:isbn">0201502550</identifier>
		<publisher>Addison Wesley</publisher>
		<title type="sharef:primaryTitle">The Design and Analysis of Spatial Data Structures</title>
	</reference>
	<reference name="sam90b" src="bibtex:book" src-info="bibtex:line-24250" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Hanan</givenname>
				<surname>Samet</surname>
			</person>
		</names>
		<date value="1990"/>
		<address type="sharef:placePublished">Reading, Massachusetts</address>
		<identifier type="sharef:isbn">020150300X</identifier>
		<publisher>Addison Wesley</publisher>
		<title type="sharef:primaryTitle">Applications of Spatial Data Structures: Computer Graphics, Image Processing, and GIS</title>
	</reference>
	<reference name="bat91" src="bibtex:book" src-info="bibtex:line-24259" type="sharef:book">
		<names type="sharef: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 type="sharef:placePublished">Reading, Massachusetts</address>
		<identifier type="sharef:isbn">0805302441</identifier>
		<publisher>Addison Wesley</publisher>
		<title type="sharef:primaryTitle">Conceptual Database Design: An Entity-Relationship Approach</title>
		<identifier type="sharef:uri">http://www.awprofessional.com/bookstore/product.asp?isbn=0805302441&amp;rl=1</identifier>
	</reference>
	<reference name="leu01" src="bibtex:book" src-info="bibtex:line-24270" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Bo</givenname>
				<surname>Leuf</surname>
			</person>
			<person>
				<givenname>Ward</givenname>
				<surname>Cunningham</surname>
			</person>
		</names>
		<date value="2001-04"/>
		<address type="sharef:placePublished">Reading, Massachusetts</address>
		<identifier type="sharef:isbn">020171499X</identifier>
		<publisher>Addison Wesley</publisher>
		<title type="sharef:primaryTitle">The Wiki Way: Collaboration and Sharing on the Internet</title>
		<field type="bibtex:topic">wiki[1]</field>
		<identifier type="sharef:uri">http://www.awprofessional.com/title/020171499X</identifier>
	</reference>
	<reference name="edn03" src="bibtex:book" src-info="bibtex:line-24282" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>John</givenname>
				<surname>Edney</surname>
			</person>
			<person>
				<givenname>William A.</givenname>
				<surname>Arbaugh</surname>
			</person>
		</names>
		<date value="2003-07"/>
		<address type="sharef:placePublished">Reading, Massachusetts</address>
		<identifier type="sharef:isbn">0321136209</identifier>
		<publisher>Addison Wesley</publisher>
		<title type="sharef:primaryTitle">Real 802.11 Security</title>
		<field type="bibtex:topic">wep[0.8] wpa[0.8] ieee80211i[0.8] tkip[0.7] eap[0.7]</field>
		<identifier type="sharef:uri">http://www.awprofessional.com/title/0321136209</identifier>
	</reference>
	<reference name="ray01" src="bibtex:book" src-info="bibtex:line-24294" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Eric Steven</givenname>
				<surname>Raymond</surname>
			</person>
		</names>
		<date value="2001-01"/>
		<address type="sharef:placePublished">Sebastopol, California</address>
		<identifier type="sharef:isbn">0-596-00108-8</identifier>
		<publisher>O'Reilly &amp; Associates</publisher>
		<title type="sharef:primaryTitle">The Cathedral &amp; the Bazaar</title>
		<identifier type="sharef:uri">http://www.catb.org/~esr/writings/cathedral-bazaar/</identifier>
	</reference>
	<reference name="all10" src="bibtex:book" src-info="bibtex:line-24305" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Subbu</givenname>
				<surname>Allamaraju</surname>
			</person>
		</names>
		<date value="2010-02"/>
		<abstract>
			<richtext>
				<p>While the REST design philosophy has captured the imagination of web and enterprise developers alike, using this approach to develop real web services is no picnic. This cookbook includes more than 100 recipes to help you take advantage of REST, HTTP, and the infrastructure of the Web. You'll learn ways to design RESTful web services for client and server applications that meet performance, scalability, reliability, and security goals, no matter what programming language and development framework you use.</p>
			</richtext>
		</abstract>
		<address type="sharef:placePublished">Sebastopol, California</address>
		<identifier type="sharef:isbn">978-0-596-80168-7</identifier>
		<publisher>O'Reilly &amp; Associates</publisher>
		<title type="sharef:primaryTitle">RESTful Web Services Cookbook</title>
		<field type="bibtex:topic">rest[0.9] http[0.8]</field>
		<identifier type="sharef:uri">http://oreilly.com/catalog/9780596801694</identifier>
	</reference>
	<reference name="web10" src="bibtex:book" src-info="bibtex:line-24318" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Jim</givenname>
				<surname>Webber</surname>
			</person>
			<person>
				<givenname>Savas</givenname>
				<surname>Parastatidis</surname>
			</person>
			<person>
				<givenname>Ian</givenname>
				<surname>Robinson</surname>
			</person>
		</names>
		<date value="2010-09"/>
		<abstract>
			<richtext>
				<p>REST continues to gain momentum as the best method for building web services, leaving many web architects to consider whether and how to include this approach in their SOA and SOAP-dominated world. In this insightful book, three SOA experts provide a down-to-earth explanation of REST and demonstrate how you can develop simple and elegant distributed hypermedia systems by applying the Web's guiding principles to common enterprise computing problems. You'll learn techniques for implementing specific Web technologies and patterns to solve the needs of a typical company as it grows from modest beginnings to become a global enterprise.</p>
			</richtext>
		</abstract>
		<address type="sharef:placePublished">Sebastopol, California</address>
		<identifier type="sharef:isbn">978-0-596-80582-1</identifier>
		<publisher>O'Reilly &amp; Associates</publisher>
		<title type="sharef:primaryTitle">REST in Practice: Hypermedia and Systems Architecture</title>
		<field type="bibtex:topic">rest[0.9] http[0.8]</field>
		<identifier type="sharef:uri">http://oreilly.com/catalog/9780596805838</identifier>
	</reference>
	<reference name="cra02" src="bibtex:book" src-info="bibtex:line-24331" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Lorrie Faith</givenname>
				<surname>Cranor</surname>
			</person>
		</names>
		<date value="2002-09"/>
		<abstract>
			<richtext>
				<p>The W3C's Platform for Privacy Preferences (P3P) provides a standard way for web sites to communicate about their privacy practices. Many of the most popular web sites use P3P, and software to view P3P policies is built into popular web browsers. Web Privacy with P3P delivers practical advice and insider tips on configuring sites for P3P compliance. The book explains the inner workings of the P3P protocol while maintaining a hands-on implementation approach. Software developers, privacy consultants, corporate decision-makers, lawyers, public policy-makers, and any individual interested in online privacy issues will find this book indispensable.</p>
			</richtext>
		</abstract>
		<address type="sharef:placePublished">Sebastopol, California</address>
		<identifier type="sharef:isbn">0-59600-371-4</identifier>
		<publisher>O'Reilly &amp; Associates</publisher>
		<title type="sharef:primaryTitle">Web Privacy with P3P</title>
		<field type="bibtex:topic">p3p[0.9]</field>
		<identifier type="sharef:uri">http://p3pbook.com/</identifier>
	</reference>
	<reference name="pil05" src="bibtex:book" src-info="bibtex:line-24344" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Mark</givenname>
				<surname>Pilgrim</surname>
			</person>
		</names>
		<date value="2005-11"/>
		<abstract>
			<richtext>
				<p>Greasemonkey — the new Firefox extension that allows you to write scripts that alter the web pages you visit — allows you to alter site appearance, fix bugs, or even combine data from different web sites to meet your own needs. Some people are content to receive information from websites passively; some people want to control it. For those who prefer to customize and control their content, Greasemonkey Hacks provides the expertise you need to take command of any web page you view.</p>
			</richtext>
		</abstract>
		<address type="sharef:placePublished">Sebastopol, California</address>
		<identifier type="sharef:isbn">0-596-10165-1</identifier>
		<publisher>O'Reilly &amp; Associates</publisher>
		<title type="sharef:primaryTitle">Greasemonkey Hacks</title>
		<identifier type="sharef:uri">http://www.oreilly.com/catalog/greasemonkeyhks/</identifier>
	</reference>
	<reference name="ric07" src="bibtex:book" src-info="bibtex:line-24356" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Leonard</givenname>
				<surname>Richardson</surname>
			</person>
			<person>
				<givenname>Sam</givenname>
				<surname>Ruby</surname>
			</person>
		</names>
		<date value="2007-05"/>
		<abstract>
			<richtext>
				<p>You've built web sites that can be used by humans. But can you also build web sites that are usable by machines? That's where the future lies, and that's what this book shows you how to do. Today's web service technologies have lost sight of the simplicity that made the Web successful. This book explains how to put the "Web" back into web services with REST, the architectural style that drives the Web.</p>
			</richtext>
		</abstract>
		<address type="sharef:placePublished">Sebastopol, California</address>
		<identifier type="sharef:isbn">0-596-52926-0</identifier>
		<publisher>O'Reilly &amp; Associates</publisher>
		<title type="sharef:primaryTitle">RESTful Web Services</title>
		<field type="bibtex:topic">rest[0.9]</field>
		<identifier type="sharef:uri">http://www.oreilly.com/catalog/9780596529260/</identifier>
	</reference>
	<reference name="bur09" src="bibtex:book" src-info="bibtex:line-24369" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Bill</givenname>
				<surname>Burke</surname>
			</person>
		</names>
		<date value="2009-11"/>
		<abstract>
			<richtext>
				<p>Learn how to design and develop distributed web services in Java using RESTful architectural principals and the JAX-RS specification in Java EE 6. With this hands-on reference, you'll focus on implementation rather than theory, and discover why the RESTful method is far better than technologies like CORBA and SOAP. You'll get step-by-step instructions for installing, configuring, and running several working JAX-RS examples using the JBoss RESTEasy implementation of JAX-RS.</p>
			</richtext>
		</abstract>
		<address type="sharef:placePublished">Sebastopol, California</address>
		<identifier type="sharef:isbn">978-0-596-15804-0</identifier>
		<publisher>O'Reilly &amp; Associates</publisher>
		<title type="sharef:primaryTitle">RESTful Java with JAX-RS</title>
		<field type="bibtex:topic">rest[0.9] jaxrs[0.9]</field>
		<identifier type="sharef:uri">http://oreilly.com/catalog/9780596809300</identifier>
	</reference>
	<reference name="ray03" src="bibtex:book" src-info="bibtex:line-24382" type="sharef:book">
		<names type="sharef: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 type="sharef:placePublished">Sebastopol, California</address>
		<edition>2nd</edition>
		<identifier type="sharef:isbn">0-596-00420-6</identifier>
		<publisher>O'Reilly &amp; Associates</publisher>
		<title type="sharef:primaryTitle">Learning XML</title>
		<field type="bibtex:topic">xml[0.7]</field>
		<identifier type="sharef:uri">http://www.oreilly.com/catalog/learnxml2/</identifier>
	</reference>
	<reference name="sus04" src="bibtex:book" src-info="bibtex:line-24396" type="sharef:book">
		<names type="sharef: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 type="sharef:placePublished">Sebastopol, California</address>
		<identifier type="sharef:isbn">0-596-00448-6</identifier>
		<publisher>O'Reilly &amp; Associates</publisher>
		<title type="sharef:primaryTitle">Version Control with Subversion</title>
		<field type="bibtex:topic">subversion[0.8]</field>
		<identifier type="sharef:uri" resourceType="text/html">http://www.oreilly.com/catalog/0596004486/index.html</identifier>
	</reference>
	<reference name="ves03" src="bibtex:book" src-info="bibtex:line-24409" type="sharef:book">
		<names type="sharef: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 type="sharef:placePublished">Sebastopol, California</address>
		<identifier type="sharef:isbn">0-596-00459-1</identifier>
		<publisher>O'Reilly &amp; Associates</publisher>
		<title type="sharef:primaryTitle">Essential CVS</title>
		<field type="bibtex:topic">cvs[0.8]</field>
		<identifier type="sharef:uri">http://www.oreilly.com/catalog/cvs/</identifier>
	</reference>
	<reference name="zaw04" src="bibtex:book" src-info="bibtex:line-24422" type="sharef:book">
		<names type="sharef: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 type="sharef:placePublished">Sebastopol, California</address>
		<identifier type="sharef:isbn">0596003064</identifier>
		<publisher>O'Reilly &amp; Associates</publisher>
		<title type="sharef:primaryTitle">High Performance MySQL</title>
		<field type="bibtex:topic">mysql[0.8]</field>
		<identifier type="sharef:uri">http://www.oreilly.com/catalog/hpmysql/</identifier>
	</reference>
	<reference name="lew00" src="bibtex:book" src-info="bibtex:line-24434" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Kevin</givenname>
				<surname>Lewis</surname>
			</person>
		</names>
		<date value="2000-06"/>
		<address type="sharef:placePublished">Sebastopol, California</address>
		<identifier type="sharef:isbn">1-56592-719-2</identifier>
		<publisher>O'Reilly &amp; Associates</publisher>
		<title type="sharef:primaryTitle">Creating Effective JavaHelp</title>
		<field type="bibtex:topic">javahelp[0.8]</field>
		<identifier type="sharef:uri">http://www.oreilly.com/catalog/creatingjavahelp/</identifier>
	</reference>
	<reference name="hop79" src="bibtex:book" src-info="bibtex:line-24446" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>John E.</givenname>
				<surname>Hopcroft</surname>
			</person>
			<person>
				<givenname>Jeffrey D.</givenname>
				<surname>Ullman</surname>
			</person>
		</names>
		<date value="1979"/>
		<address type="sharef:placePublished">Reading, Massachusetts</address>
		<identifier type="sharef:isbn">020102988X</identifier>
		<publisher>Addison Wesley</publisher>
		<title type="sharef:primaryTitle">Introduction to Automata Theory, Languages, and Computation</title>
	</reference>
	<reference name="pla92b" src="bibtex:book" src-info="bibtex:line-24455" type="sharef:book">
		<names type="sharef: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 type="sharef:placePublished">Reading, Massachusetts</address>
		<identifier type="sharef:isbn">0-201-56503-X</identifier>
		<publisher>Addison Wesley</publisher>
		<title type="sharef:primaryTitle">X.400 Message Handling: Standards, Interworking, Applications</title>
		<field type="bibtex:topic">x400[0.9]</field>
	</reference>
	<reference name="sin99" src="bibtex:book" src-info="bibtex:line-24466" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Simon</givenname>
				<surname>Singh</surname>
			</person>
		</names>
		<date value="1999-09"/>
		<identifier type="sharef:isbn">0-385-49531-5</identifier>
		<publisher>Doubleday</publisher>
		<title type="sharef:primaryTitle">The Code Book: The Evolution of Secrecy from Mary, Queen of Scots to Quantum Cryptography</title>
		<field type="bibtex:topic">cryptography[1] skc[1] pkc[1]</field>
	</reference>
	<reference name="sur04" src="bibtex:book" src-info="bibtex:line-24476" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>James</givenname>
				<surname>Surowiecki</surname>
			</person>
		</names>
		<date value="2004-05"/>
		<identifier type="sharef:isbn">0316861731</identifier>
		<publisher>Doubleday</publisher>
		<title type="sharef:primaryTitle">The Wisdom of Crowds</title>
	</reference>
	<reference name="bey98" src="bibtex:book" src-info="bibtex:line-24485" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Hugh</givenname>
				<surname>Beyer</surname>
			</person>
			<person>
				<givenname>Karen</givenname>
				<surname>Holtzblatt</surname>
			</person>
		</names>
		<date value="1998"/>
		<address type="sharef:placePublished">San Francisco, California</address>
		<field type="bibtex:index">usability</field>
		<identifier type="sharef:isbn">1-55680-411-1</identifier>
		<publisher>Morgan Kaufmann Publishers</publisher>
		<title type="sharef:primaryTitle">Contextual Design: Defining Customer-Centered Systems</title>
	</reference>
	<reference name="all08" src="bibtex:book" src-info="bibtex:line-24495" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Dean</givenname>
				<surname>Allemang</surname>
			</person>
			<person>
				<givenname>James A.</givenname>
				<surname>Hendler</surname>
			</person>
		</names>
		<date value="2008-05"/>
		<field type="bibtex:index">rdf[0.9] rdfs[0.9] owl[0.9]</field>
		<identifier type="sharef:isbn">0123735564</identifier>
		<publisher>Morgan Kaufmann Publishers</publisher>
		<title type="sharef:primaryTitle">Semantic Web for the Working Ontologist</title>
		<identifier type="sharef:uri">http://workingontologist.org/</identifier>
	</reference>
	<reference name="nie94" src="bibtex:book" src-info="bibtex:line-24506" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Jakob</givenname>
				<surname>Nielsen</surname>
			</person>
		</names>
		<date value="1994-10"/>
		<address type="sharef:placePublished">San Francisco, California</address>
		<field type="bibtex:index">usability</field>
		<identifier type="sharef:isbn">0125184069</identifier>
		<publisher>Morgan Kaufmann Publishers</publisher>
		<title type="sharef:primaryTitle">Usability Engineering</title>
	</reference>
	<reference name="joh03" src="bibtex:book" src-info="bibtex:line-24517" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Jeff</givenname>
				<surname>Johnson</surname>
			</person>
		</names>
		<date value="2003-04"/>
		<address type="sharef:placePublished">San Francisco, California</address>
		<identifier type="sharef:isbn">1558608400</identifier>
		<publisher>Morgan Kaufmann Publishers</publisher>
		<title type="sharef:primaryTitle">Web Bloopers: 60 Common Web Design Mistakes, and How to Avoid Them</title>
		<identifier type="sharef:uri">http://www.web-bloopers.com/</identifier>
	</reference>
	<reference name="joh00" src="bibtex:book" src-info="bibtex:line-24528" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Jeff</givenname>
				<surname>Johnson</surname>
			</person>
		</names>
		<date value="2000-03"/>
		<address type="sharef:placePublished">San Francisco, California</address>
		<identifier type="sharef:isbn">1558605827</identifier>
		<publisher>Morgan Kaufmann Publishers</publisher>
		<title type="sharef:primaryTitle">GUI Bloopers: Don'ts and Do's for Software Developers and Web Designers</title>
		<field type="bibtex:topic">gui[0.7]</field>
		<identifier type="sharef:uri">http://web-bloopers.com/gui-bloopers/</identifier>
	</reference>
	<reference name="kay03" src="bibtex:book" src-info="bibtex:line-24540" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Doug</givenname>
				<surname>Kaye</surname>
			</person>
		</names>
		<date value="2003-08"/>
		<identifier type="sharef:isbn">0321384016</identifier>
		<publisher>RDS Press</publisher>
		<title type="sharef:primaryTitle">Loosely Coupled: The Missing Pieces of Web Services</title>
	</reference>
	<reference name="gre06b" src="bibtex:book" src-info="bibtex:line-24549" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Adam</givenname>
				<surname>Greenfield</surname>
			</person>
		</names>
		<date value="2006-03"/>
		<address type="sharef:placePublished">Indianapolis, Indiana</address>
		<identifier type="sharef:isbn">1881378241</identifier>
		<publisher>New Riders</publisher>
		<title type="sharef:primaryTitle">Everyware: The Dawning Age of Ubiquitous Computing</title>
	</reference>
	<reference name="nie99b" src="bibtex:book" src-info="bibtex:line-24559" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Jakob</givenname>
				<surname>Nielsen</surname>
			</person>
		</names>
		<date value="1999-11"/>
		<address type="sharef:placePublished">Indianapolis, Indiana</address>
		<field type="bibtex:index">WWW, usability</field>
		<publisher>New Riders</publisher>
		<title type="sharef:primaryTitle">Designing Web Usability: The Practice of Simplicity</title>
	</reference>
	<reference name="per99" src="bibtex:book" src-info="bibtex:line-24569" type="sharef:book">
		<names type="sharef: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 type="sharef:placePublished">San Francisco, California</address>
		<publisher>HarperBusiness</publisher>
		<title type="sharef:primaryTitle">The Internet Bubble</title>
	</reference>
	<reference name="lee99" src="bibtex:book" src-info="bibtex:line-24578" type="sharef:book">
		<names type="sharef: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 type="sharef:placePublished">San Francisco, California</address>
		<field type="bibtex:index">WWW</field>
		<publisher>HarperCollins</publisher>
		<title type="sharef:primaryTitle">Weaving the Web</title>
	</reference>
	<reference name="sch03" src="bibtex:book" src-info="bibtex:line-24588" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Harald</givenname>
				<surname>Schöning</surname>
			</person>
		</names>
		<date value="2003"/>
		<address type="sharef:placePublished">Munich, Germany</address>
		<identifier type="sharef:isbn">3446220089</identifier>
		<publisher>Carl Hanser Verlag</publisher>
		<title type="sharef:primaryTitle">XML und Datenbanken — Konzepte und Systeme</title>
		<field type="bibtex:topic">xdbms[1]</field>
	</reference>
	<reference name="rho97" src="bibtex:book" src-info="bibtex:line-24598" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>John</givenname>
				<surname>Rhoton</surname>
			</person>
		</names>
		<date value="1997-09"/>
		<address type="sharef:placePublished">Oxford, UK</address>
		<publisher>Digital Press</publisher>
		<title type="sharef:primaryTitle">X.400 and SMTP: Battle of the E-Mail Protocols</title>
		<field type="bibtex:topic">x400[1] smtp[1]</field>
	</reference>
	<reference name="luh64" src="bibtex:book" src-info="bibtex:line-24608" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Marshall</givenname>
				<surname>McLuhan</surname>
			</person>
		</names>
		<date value="1964"/>
		<address type="sharef:placePublished">New York, NY</address>
		<publisher>McGraw-Hill</publisher>
		<title type="sharef:primaryTitle">Understanding Media: The Extensions of Man</title>
	</reference>
	<reference name="tho67" src="bibtex:book" src-info="bibtex:line-24616" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>James D.</givenname>
				<surname>Thompson</surname>
			</person>
		</names>
		<date value="1967-06"/>
		<address type="sharef:placePublished">New York, NY</address>
		<identifier type="sharef:isbn">0070643806</identifier>
		<publisher>McGraw-Hill</publisher>
		<title type="sharef:primaryTitle">Organizations in Action: Social Science Bases of Administrative Theory</title>
	</reference>
	<reference name="sow98" src="bibtex:book" src-info="bibtex:line-24626" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>John F.</givenname>
				<surname>Sowa</surname>
			</person>
		</names>
		<date value="1998-12"/>
		<address type="sharef:placePublished">Boston, Massachusetts</address>
		<publisher>PWS Publishing Company</publisher>
		<title type="sharef:primaryTitle">Knowledge Representation: Logical, Philosophical, and Computational Foundations</title>
	</reference>
	<reference name="otl35" src="bibtex:book" src-info="bibtex:line-24635" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Paul</givenname>
				<surname>Otlet</surname>
			</person>
		</names>
		<date value="1935"/>
		<address type="sharef:placePublished">Brussels, Belgium</address>
		<publisher>Éditiones Mundaneum</publisher>
		<title type="sharef:primaryTitle">Monde: Essai d'universalisme: Connaissances du monde, sentiments du monde, action organisée et plan du monde</title>
	</reference>
	<reference name="nel93" src="bibtex:book" src-info="bibtex:line-24643" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Theodor Holm</givenname>
				<surname>Nelson</surname>
			</person>
		</names>
		<date value="1993"/>
		<address type="sharef:placePublished">Sausalito, California</address>
		<publisher>Mindful Press</publisher>
		<title type="sharef:primaryTitle">World Enough</title>
	</reference>
	<reference name="nel82" src="bibtex:book" src-info="bibtex:line-24651" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Theodor Holm</givenname>
				<surname>Nelson</surname>
			</person>
		</names>
		<date value="1982"/>
		<address type="sharef:placePublished">Sausalito, California</address>
		<field type="bibtex:index">Xanadu</field>
		<publisher>Mindful Press</publisher>
		<title type="sharef:primaryTitle">Literary Machines</title>
	</reference>
	<reference name="nel76" src="bibtex:book" src-info="bibtex:line-24660" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Theodor Holm</givenname>
				<surname>Nelson</surname>
			</person>
		</names>
		<date value="1976"/>
		<address type="sharef:placePublished">Sausalito, California</address>
		<field type="bibtex:index">Xanadu</field>
		<publisher>Mindful Press</publisher>
		<title type="sharef:primaryTitle">Computer Lib/Dream Machines</title>
	</reference>
	<reference name="nel87" src="bibtex:book" src-info="bibtex:line-24669" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Theodor Holm</givenname>
				<surname>Nelson</surname>
			</person>
		</names>
		<date value="1987"/>
		<address type="sharef:placePublished">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 type="sharef:primaryTitle">Computer Lib/Dream Machines</title>
	</reference>
	<reference name="win95" src="bibtex:book" src-info="bibtex:line-24679" type="sharef:book">
		<names type="sharef:author">
			<name>Microsoft Corporation</name>
		</names>
		<date value="1995-07"/>
		<address type="sharef:placePublished">Austin, Texas</address>
		<edition>2nd</edition>
		<field type="bibtex:index">GUI</field>
		<publisher>Microsoft Press</publisher>
		<title type="sharef:primaryTitle">The Windows Interface Guidelines for Software Design: An Application Design Guide</title>
	</reference>
	<reference name="shn89" src="bibtex:book" src-info="bibtex:line-24690" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Ben</givenname>
				<surname>Shneiderman</surname>
			</person>
			<person>
				<givenname>Greg</givenname>
				<surname>Kearsley</surname>
			</person>
		</names>
		<date value="1989-05"/>
		<address type="sharef:placePublished">Reading, Massachusetts</address>
		<identifier type="sharef:isbn">0201151715</identifier>
		<publisher>Addison Wesley</publisher>
		<title type="sharef:primaryTitle">Hypertext Hands-On!: An Introduction to a New Way of Organizing and Accessing Information</title>
	</reference>
	<reference name="kri91" src="bibtex:book" src-info="bibtex:line-24700" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Balachander</givenname>
				<surname>Krishnamurthy</surname>
			</person>
			<person>
				<givenname>Jennifer</givenname>
				<surname>Rexford</surname>
			</person>
		</names>
		<date value="2001-05"/>
		<address type="sharef:placePublished">Reading, Massachusetts</address>
		<identifier type="sharef:isbn">0201710889</identifier>
		<publisher>Addison Wesley</publisher>
		<title type="sharef:primaryTitle">Web Protocols and Practice: HTTP/1.1, Networking Protocols, Caching, and Traffic Measurement</title>
		<field type="bibtex:topic">http[0.8] cache[0.8] ip[0.6] tcp[0.6] dns[0.6]</field>
	</reference>
	<reference name="car01d" src="bibtex:book" src-info="bibtex:line-24711" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>David</givenname>
				<surname>Carlson</surname>
			</person>
		</names>
		<date value="2001-04"/>
		<address type="sharef:placePublished">Reading, Massachusetts</address>
		<identifier type="sharef:isbn">0201709155</identifier>
		<publisher>Addison Wesley</publisher>
		<title type="sharef:primaryTitle">Modeling XML Applications with UML: Practical e-Business Applications</title>
		<field type="bibtex:topic">xml[0.8] uml[0.8]</field>
	</reference>
	<reference name="fun00" src="bibtex:book" src-info="bibtex:line-24722" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Khun Yee</givenname>
				<surname>Fung</surname>
			</person>
		</names>
		<date value="2000-12"/>
		<address type="sharef:placePublished">Reading, Massachusetts</address>
		<identifier type="sharef:isbn">0201711036</identifier>
		<publisher>Addison Wesley</publisher>
		<title type="sharef:primaryTitle">XSLT: Working with XML and HTML</title>
		<field type="bibtex:topic">xml[0.5] xslt1[0.8] html[0.6]</field>
	</reference>
	<reference name="beh00" src="bibtex:book" src-info="bibtex:line-24733" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Henning</givenname>
				<surname>Behme</surname>
			</person>
			<person>
				<givenname>Stefan</givenname>
				<surname>Mintert</surname>
			</person>
		</names>
		<date value="2000-05"/>
		<address type="sharef:placePublished">Munich, Germany</address>
		<edition>2nd</edition>
		<identifier type="sharef:isbn">3827316367</identifier>
		<publisher>Addison Wesley</publisher>
		<title type="sharef:primaryTitle">XML in der Praxis</title>
		<field type="bibtex:topic">xml[0.7] xslt1[0.6] dsssl[0.6]</field>
	</reference>
	<reference name="dil04" src="bibtex:book" src-info="bibtex:line-24745" type="sharef:book">
		<names type="sharef: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 type="sharef:placePublished">Boca Raton, Florida</address>
		<edition>2nd</edition>
		<identifier type="sharef:isbn">041524059X</identifier>
		<publisher>CRC Press</publisher>
		<title type="sharef:primaryTitle">Designing Usable Electronic Text</title>
		<identifier type="sharef:uri">http://www.itknowledgebase.net/ejournals/books/book_summary/summary.asp?id=1257</identifier>
	</reference>
	<reference name="che00" src="bibtex:book" src-info="bibtex:line-24758" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>John</givenname>
				<surname>Cheesman</surname>
			</person>
			<person>
				<givenname>John</givenname>
				<surname>Daniels</surname>
			</person>
		</names>
		<date value="2000-10"/>
		<address type="sharef:placePublished">Reading, Massachusetts</address>
		<field type="bibtex:index">components</field>
		<publisher>Addison Wesley</publisher>
		<title type="sharef:primaryTitle">UML Components: A Simple Process for Specifying Component-Based Software</title>
		<field type="bibtex:topic">uml[0.7]</field>
	</reference>
	<reference name="war98" src="bibtex:book" src-info="bibtex:line-24769" type="sharef:book">
		<names type="sharef: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 type="sharef:placePublished">Reading, Massachusetts</address>
		<publisher>Addison Wesley</publisher>
		<title type="sharef:primaryTitle">The Object Constraint Language: Precise Modeling With UML</title>
		<field type="bibtex:topic">uml[0.7] ocl[0.9]</field>
	</reference>
	<reference name="smi97" src="bibtex:book" src-info="bibtex:line-24779" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Richard E.</givenname>
				<surname>Smith</surname>
			</person>
		</names>
		<date value="1997-08"/>
		<address type="sharef:placePublished">Reading, Massachusetts</address>
		<field type="bibtex:index">cryptography</field>
		<identifier type="sharef:isbn">0201924803</identifier>
		<publisher>Addison Wesley</publisher>
		<title type="sharef:primaryTitle">Internet Cryptography</title>
	</reference>
	<reference name="con99" src="bibtex:book" src-info="bibtex:line-24790" type="sharef:book">
		<names type="sharef: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 type="sharef:placePublished">Reading, Massachusetts</address>
		<identifier type="sharef:isbn">0201924781</identifier>
		<publisher>Addison Wesley</publisher>
		<title type="sharef:primaryTitle">Software For Use</title>
	</reference>
	<reference name="joh99" src="bibtex:book" src-info="bibtex:line-24800" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Kevin</givenname>
				<surname>Johnson</surname>
			</person>
		</names>
		<date value="1999-11"/>
		<address type="sharef:placePublished">Reading, Massachusetts</address>
		<field type="bibtex:index">SMTP, POP, IMAP, MIME, PGP</field>
		<identifier type="sharef:isbn">0-201-43288-9</identifier>
		<publisher>Addison Wesley</publisher>
		<title type="sharef:primaryTitle">Internet Email Protocols: A Developer's Guide</title>
	</reference>
	<reference name="kat03" src="bibtex:book" src-info="bibtex:line-24811" type="sharef:book">
		<names type="sharef: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="sharef:editor">
			<person>
				<givenname>Howard</givenname>
				<surname>Katz</surname>
			</person>
		</names>
		<date value="2003-08"/>
		<address type="sharef:placePublished">Reading, Massachusetts</address>
		<identifier type="sharef:isbn">0321180607</identifier>
		<publisher>Addison Wesley</publisher>
		<title type="sharef:primaryTitle">XQuery from the Experts: A Guide to the W3C XML Query Language</title>
		<field type="bibtex:topic">xquery[0.8]</field>
	</reference>
	<reference name="mac93" src="bibtex:book" src-info="bibtex:line-24823" type="sharef:book">
		<names type="sharef:author">
			<name>Apple Computer, Inc.</name>
		</names>
		<date value="1993-01"/>
		<address type="sharef:placePublished">Reading, Massachusetts</address>
		<identifier type="sharef:isbn">0201622165</identifier>
		<publisher>Addison Wesley</publisher>
		<title type="sharef:primaryTitle">MacIntosh Human Interface Guidelines</title>
		<field type="bibtex:topic">gui[0.8]</field>
	</reference>
	<reference name="tuf01" src="bibtex:book" src-info="bibtex:line-24834" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Edward R.</givenname>
				<surname>Tufte</surname>
			</person>
		</names>
		<date value="2001"/>
		<address type="sharef:placePublished">Cheshire, Connecticut</address>
		<edition>2nd</edition>
		<identifier type="sharef:isbn">0961392142</identifier>
		<publisher>Graphics Press</publisher>
		<title type="sharef:primaryTitle">The Visual Display of Quantitative Information</title>
		<field type="bibtex:topic">gui[0.8]</field>
	</reference>
	<reference name="sun99" src="bibtex:book" src-info="bibtex:line-24845" type="sharef:book">
		<names type="sharef:author">
			<name>Sun Microsystems</name>
		</names>
		<date value="1999-07"/>
		<address type="sharef:placePublished">Reading, Massachusetts</address>
		<identifier type="sharef:isbn">0201615851</identifier>
		<publisher>Addison Wesley</publisher>
		<title type="sharef:primaryTitle">Java Look and Feel Design Guidelines</title>
		<field type="bibtex:topic">gui[0.8]</field>
	</reference>
	<reference name="buc99" src="bibtex:book" src-info="bibtex:line-24856" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Simon</givenname>
				<surname>Buckingham Shum</surname>
			</person>
		</names>
		<date value="1999-07"/>
		<address type="sharef:placePublished">Newbury, UK</address>
		<publisher>Mobile Lifestreams</publisher>
		<title type="sharef:primaryTitle">Data on GPRS</title>
		<field type="bibtex:topic">gprs[0.8]</field>
	</reference>
	<reference name="red98" src="bibtex:book" src-info="bibtex:line-24866" type="sharef:book">
		<names type="sharef: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 type="sharef:placePublished">Norwood, Massachusetts</address>
		<identifier type="sharef:isbn">0890069573</identifier>
		<publisher>Artech House</publisher>
		<title type="sharef:primaryTitle">GSM and Personal Communications Handbook</title>
		<field type="bibtex:topic">gsm[0.8]</field>
	</reference>
	<reference name="fer03b" src="bibtex:book" src-info="bibtex:line-24877" type="sharef:book">
		<names type="sharef: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 type="sharef:placePublished">Norwood, Massachusetts</address>
		<identifier type="sharef:isbn">1580533701</identifier>
		<publisher>Artech House</publisher>
		<title type="sharef:primaryTitle">Role-Based Access Control</title>
		<field type="bibtex:topic">rbac[0.9]</field>
	</reference>
	<reference name="mou92" src="bibtex:book" src-info="bibtex:line-24888" type="sharef:book">
		<names type="sharef: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="sharef:isbn">0945592159</identifier>
		<publisher>Telecom Publishing</publisher>
		<title type="sharef:primaryTitle">The GSM System for Mobile Communications</title>
		<field type="bibtex:topic">gsm[0.8]</field>
	</reference>
	<reference name="hei99" src="bibtex:book" src-info="bibtex:line-24898" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Gunnar</givenname>
				<surname>Heine</surname>
			</person>
		</names>
		<date value="1999-01"/>
		<identifier type="sharef:isbn">0890064717</identifier>
		<publisher>Artech House</publisher>
		<title type="sharef:primaryTitle">GSM Networks: Protocols, Terminology, and Implementation</title>
		<field type="bibtex:topic">gsm[0.8]</field>
	</reference>
	<reference name="blo06" src="bibtex:book" src-info="bibtex:line-24908" type="sharef:book">
		<names type="sharef:editor">
			<person>
				<givenname>Jason</givenname>
				<surname>Bloomberg</surname>
			</person>
			<person>
				<givenname>Ronald</givenname>
				<surname>Schmelzer</surname>
			</person>
		</names>
		<date value="2006-03"/>
		<address type="sharef:placePublished">New York, NY</address>
		<identifier type="sharef:isbn">978-0471768586</identifier>
		<publisher>John Wiley &amp; Sons</publisher>
		<title type="sharef:primaryTitle">Service Orient or Be Doomed!</title>
	</reference>
	<reference name="lon05" src="bibtex:book" src-info="bibtex:line-24918" type="sharef:book">
		<names type="sharef:editor">
			<person>
				<givenname>Paul A.</givenname>
				<surname>Longley</surname>
			</person>
			<person>
				<givenname>Michael F.</givenname>
				<surname>Goodchild</surname>
			</person>
			<person>
				<givenname>David J.</givenname>
				<surname>Maguire</surname>
			</person>
			<person>
				<givenname>David W.</givenname>
				<surname>Rhind</surname>
			</person>
		</names>
		<date value="2005"/>
		<address type="sharef:placePublished">New York, NY</address>
		<edition>2</edition>
		<identifier type="sharef:isbn">0470870001</identifier>
		<publisher>John Wiley &amp; Sons</publisher>
		<title type="sharef:primaryTitle">Geographic Information Systems and Science</title>
		<identifier type="sharef:uri">http://www.wiley.com/legacy/wileychi/longley/</identifier>
		<identifier type="sharef:uri">http://www.wiley.com/legacy/wileychi/gis/</identifier>
	</reference>
	<reference name="nie94b" src="bibtex:book" src-info="bibtex:line-24930" type="sharef:book">
		<names type="sharef:editor">
			<person>
				<givenname>Jakob</givenname>
				<surname>Nielsen</surname>
			</person>
			<person>
				<givenname>Robert L.</givenname>
				<surname>Mack</surname>
			</person>
		</names>
		<date value="1994"/>
		<address type="sharef:placePublished">New York, NY</address>
		<identifier type="sharef:isbn">0-471-01877-5</identifier>
		<publisher>John Wiley &amp; Sons</publisher>
		<title type="sharef:primaryTitle">Usability Inspection Methods</title>
		<identifier type="sharef:uri" resourceType="text/html">http://www.useit.com/jakob/inspectbook.html</identifier>
	</reference>
	<reference name="ebe01" src="bibtex:book" src-info="bibtex:line-24940" type="sharef:book">
		<names type="sharef: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="sharef:isbn">047149903X</identifier>
		<publisher>John Wiley &amp; Sons</publisher>
		<title type="sharef:primaryTitle">GSM Switching, Services, and Protocols</title>
		<field type="bibtex:topic">gsm[0.8] gprs[0.7] wap1[0.7]</field>
	</reference>
	<reference name="sha98" src="bibtex:book" src-info="bibtex:line-24951" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Carl</givenname>
				<surname>Shapiro</surname>
			</person>
			<person>
				<givenname>Hal R.</givenname>
				<surname>Varian</surname>
			</person>
		</names>
		<date value="1998-11"/>
		<address type="sharef:placePublished">Boston, Massachusetts</address>
		<identifier type="sharef:isbn">087584863X</identifier>
		<publisher>Harvard Business School Press</publisher>
		<title type="sharef:primaryTitle">Information Rules: A Strategic Guide to the Network Economy</title>
	</reference>
	<reference name="han09" src="bibtex:book" src-info="bibtex:line-24961" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Morton T.</givenname>
				<surname>Hansen</surname>
			</person>
		</names>
		<date value="2009-05"/>
		<address type="sharef:placePublished">Boston, Massachusetts</address>
		<identifier type="sharef:isbn">1422115151</identifier>
		<publisher>Harvard Business School Press</publisher>
		<title type="sharef:primaryTitle">Collaboration: How Leaders Avoid the Traps, Create Unity, and Reap Big Results</title>
		<identifier type="sharef:uri">http://www.thecollaborationbook.com/</identifier>
	</reference>
	<reference name="chr97" src="bibtex:book" src-info="bibtex:line-24972" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Clayton M.</givenname>
				<surname>Christensen</surname>
			</person>
		</names>
		<date value="1997-06"/>
		<address type="sharef:placePublished">Boston, Massachusetts</address>
		<field type="bibtex:index">disruptive technology</field>
		<identifier type="sharef:isbn">0875845851</identifier>
		<publisher>Harvard Business School Press</publisher>
		<title type="sharef:primaryTitle">The Innovator's Dilemma: When New Technologies Cause Great Firms to Fail</title>
	</reference>
	<reference name="chr03b" src="bibtex:book" src-info="bibtex:line-24983" type="sharef:book">
		<names type="sharef: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 type="sharef:placePublished">Boston, Massachusetts</address>
		<identifier type="sharef:isbn">1578518520</identifier>
		<publisher>Harvard Business School Press</publisher>
		<title type="sharef:primaryTitle">The Innovator's Solution: Creating and Sustaining Successful Growth</title>
	</reference>
	<reference name="ste97b" src="bibtex:book" src-info="bibtex:line-24993" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Lincoln D.</givenname>
				<surname>Stein</surname>
			</person>
		</names>
		<date value="1997-01"/>
		<address type="sharef:placePublished">Reading, Massachusetts</address>
		<edition>2nd</edition>
		<field type="bibtex:index">www[0.8]</field>
		<identifier type="sharef:isbn">0201634627</identifier>
		<publisher>Addison Wesley</publisher>
		<title type="sharef:primaryTitle">How to Set Up and Maintain a Web Site</title>
	</reference>
	<reference name="tan01" src="bibtex:book" src-info="bibtex:line-25005" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Adrienne</givenname>
				<surname>Tannenbaum</surname>
			</person>
		</names>
		<date value="2001-08"/>
		<address type="sharef:placePublished">Reading, Massachusetts</address>
		<identifier type="sharef:isbn">0201719762</identifier>
		<publisher>Addison Wesley</publisher>
		<title type="sharef:primaryTitle">Metadata Solutions: Using Metamodels, Repositories, XML, and Enterprise Portals to Generate Information on Demand</title>
		<field type="bibtex:topic">metadata[0.8]</field>
	</reference>
	<reference name="ste98" src="bibtex:book" src-info="bibtex:line-25016" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Lincoln D.</givenname>
				<surname>Stein</surname>
			</person>
		</names>
		<date value="1998-01"/>
		<address type="sharef:placePublished">Reading, Massachusetts</address>
		<field type="bibtex:index">WWW, security</field>
		<identifier type="sharef:isbn">0201634899</identifier>
		<publisher>Addison Wesley</publisher>
		<title type="sharef:primaryTitle">Web Security: A Step-by-Step Reference Guide</title>
	</reference>
	<reference name="kop95" src="bibtex:book" src-info="bibtex:line-25027" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Helmut</givenname>
				<surname>Kopka</surname>
			</person>
			<person>
				<givenname>Patrick W.</givenname>
				<surname>Daly</surname>
			</person>
		</names>
		<date value="1995-06"/>
		<address type="sharef:placePublished">Harlow, England</address>
		<edition>2nd</edition>
		<identifier type="sharef:isbn">0-201-42777-X</identifier>
		<publisher>Addison Wesley</publisher>
		<title type="sharef:primaryTitle">A Guide to LaTeXe</title>
		<field type="bibtex:topic">latex[0.9]</field>
	</reference>
	<reference name="goo94" src="bibtex:book" src-info="bibtex:line-25039" type="sharef:book">
		<names type="sharef: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 type="sharef:placePublished">Reading, Massachusetts</address>
		<identifier type="sharef:isbn">0-201-54199-8</identifier>
		<publisher>Addison Wesley</publisher>
		<title type="sharef:primaryTitle">The LaTeX Companion</title>
		<field type="bibtex:topic">latex[0.9]</field>
	</reference>
	<reference name="knuth1" src="bibtex:book" src-info="bibtex:line-25050" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Donald Ervin</givenname>
				<surname>Knuth</surname>
			</person>
		</names>
		<date value="1997-07"/>
		<address type="sharef:placePublished">Reading, Massachusetts</address>
		<edition>3rd</edition>
		<identifier type="sharef:isbn">0-201-89683-4</identifier>
		<publisher>Addison Wesley</publisher>
		<title type="sharef:primaryTitle">The Art of Computer Programming: Fundamental Algorithms</title>
		<volume>1</volume>
	</reference>
	<reference name="knuth2" src="bibtex:book" src-info="bibtex:line-25062" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Donald Ervin</givenname>
				<surname>Knuth</surname>
			</person>
		</names>
		<date value="1998-11"/>
		<address type="sharef:placePublished">Reading, Massachusetts</address>
		<edition>3rd</edition>
		<identifier type="sharef:isbn">0-201-89684-2</identifier>
		<publisher>Addison Wesley</publisher>
		<title type="sharef:primaryTitle">The Art of Computer Programming: Seminumerical Algorithms</title>
		<volume>2</volume>
	</reference>
	<reference name="knuth3" src="bibtex:book" src-info="bibtex:line-25074" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Donald Ervin</givenname>
				<surname>Knuth</surname>
			</person>
		</names>
		<date value="1997-04"/>
		<address type="sharef:placePublished">Reading, Massachusetts</address>
		<edition>2nd</edition>
		<identifier type="sharef:isbn">0-201-89685-0</identifier>
		<publisher>Addison Wesley</publisher>
		<title type="sharef:primaryTitle">The Art of Computer Programming: Sorting and Searching</title>
		<volume>3</volume>
	</reference>
	<reference name="knu84" src="bibtex:book" src-info="bibtex:line-25086" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Donald Ervin</givenname>
				<surname>Knuth</surname>
			</person>
		</names>
		<date value="1984"/>
		<address type="sharef:placePublished">Reading, Massachusetts</address>
		<identifier type="sharef:isbn">0-201-13448-9</identifier>
		<publisher>Addison Wesley</publisher>
		<title type="sharef:primaryTitle">The TeXbook</title>
		<field type="bibtex:topic">tex[1]</field>
	</reference>
	<reference name="knuth86a" src="bibtex:book" src-info="bibtex:line-25096" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Donald Ervin</givenname>
				<surname>Knuth</surname>
			</person>
		</names>
		<date value="1986"/>
		<address type="sharef:placePublished">Reading, Massachusetts</address>
		<identifier type="sharef:isbn">0-201-13447-0</identifier>
		<publisher>Addison Wesley</publisher>
		<title type="sharef:primaryTitle">Computers &amp; Typesetting: The TeXbook</title>
		<field type="bibtex:topic">tex[1]</field>
		<field type="bibtex:updates">knu84</field>
		<volume>A</volume>
	</reference>
	<reference name="knuth86b" src="bibtex:book" src-info="bibtex:line-25108" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Donald Ervin</givenname>
				<surname>Knuth</surname>
			</person>
		</names>
		<date value="1986"/>
		<address type="sharef:placePublished">Reading, Massachusetts</address>
		<identifier type="sharef:isbn">0-201-13437-3</identifier>
		<publisher>Addison Wesley</publisher>
		<title type="sharef:primaryTitle">Computers &amp; Typesetting: TeX: The Program</title>
		<field type="bibtex:topic">tex[1]</field>
		<volume>B</volume>
	</reference>
	<reference name="knuth86c" src="bibtex:book" src-info="bibtex:line-25119" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Donald Ervin</givenname>
				<surname>Knuth</surname>
			</person>
		</names>
		<date value="1986"/>
		<address type="sharef:placePublished">Reading, Massachusetts</address>
		<identifier type="sharef:isbn">0-201-13445-4</identifier>
		<publisher>Addison Wesley</publisher>
		<title type="sharef:primaryTitle">Computers &amp; Typesetting: The Metafont Book</title>
		<volume>C</volume>
	</reference>
	<reference name="knuth86d" src="bibtex:book" src-info="bibtex:line-25129" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Donald Ervin</givenname>
				<surname>Knuth</surname>
			</person>
		</names>
		<date value="1986"/>
		<address type="sharef:placePublished">Reading, Massachusetts</address>
		<identifier type="sharef:isbn">0-201-13438-1</identifier>
		<publisher>Addison Wesley</publisher>
		<title type="sharef:primaryTitle">Computers &amp; Typesetting: Metafont: The Program</title>
		<volume>D</volume>
	</reference>
	<reference name="knuth86e" src="bibtex:book" src-info="bibtex:line-25139" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Donald Ervin</givenname>
				<surname>Knuth</surname>
			</person>
		</names>
		<date value="1986"/>
		<address type="sharef:placePublished">Reading, Massachusetts</address>
		<identifier type="sharef:isbn">0-201-13446-2</identifier>
		<publisher>Addison Wesley</publisher>
		<title type="sharef:primaryTitle">Computers &amp; Typesetting: Computer Modern Typefaces</title>
		<field type="bibtex:topic">tex[0.9]</field>
		<volume>E</volume>
	</reference>
	<reference name="lam85" src="bibtex:book" src-info="bibtex:line-25150" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Leslie</givenname>
				<surname>Lamport</surname>
			</person>
		</names>
		<date value="1985"/>
		<address type="sharef:placePublished">Reading, Massachusetts</address>
		<identifier type="sharef:isbn">020115790X</identifier>
		<publisher>Addison Wesley</publisher>
		<title type="sharef:primaryTitle">LaTeX: A Document Preparation System</title>
		<field type="bibtex:topic">latex[1]</field>
	</reference>
	<reference name="lam94" src="bibtex:book" src-info="bibtex:line-25160" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Leslie</givenname>
				<surname>Lamport</surname>
			</person>
		</names>
		<date value="1994-08"/>
		<address type="sharef:placePublished">Reading, Massachusetts</address>
		<edition>2nd</edition>
		<identifier type="sharef:isbn">0201529831</identifier>
		<publisher>Addison Wesley</publisher>
		<title type="sharef:primaryTitle">LaTeX: A Document Preparation System</title>
		<field type="bibtex:topic">latex[1]</field>
		<field type="bibtex:updates">lam85</field>
	</reference>
	<reference name="box00" src="bibtex:book" src-info="bibtex:line-25173" type="sharef:book">
		<names type="sharef: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 type="sharef:placePublished">Reading, Massachusetts</address>
		<identifier type="sharef:isbn">0201709147</identifier>
		<publisher>Addison Wesley</publisher>
		<title type="sharef:primaryTitle">Essential XML: Beyond Markup</title>
		<field type="bibtex:topic">xmlinfoset[0.8] dom[0.8] sax[0.8]</field>
	</reference>
	<reference name="ous94" src="bibtex:book" src-info="bibtex:line-25184" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>John K.</givenname>
				<surname>Ousterhout</surname>
			</person>
		</names>
		<date value="1994-05"/>
		<address type="sharef:placePublished">Reading, Massachusetts</address>
		<identifier type="sharef:isbn">020163337X</identifier>
		<publisher>Addison Wesley</publisher>
		<title type="sharef:primaryTitle">Tcl and the Tk Toolkit</title>
		<field type="bibtex:topic">tcltk[0.8]</field>
	</reference>
	<reference name="mau96" src="bibtex:book" src-info="bibtex:line-25195" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Hermann</givenname>
				<surname>Maurer</surname>
			</person>
		</names>
		<date value="1996"/>
		<address type="sharef:placePublished">Reading, Massachusetts</address>
		<identifier type="sharef:isbn">0201403463</identifier>
		<publisher>Addison Wesley</publisher>
		<title type="sharef:primaryTitle">HyperWave — The Next Generation Web Solution</title>
		<field type="bibtex:topic">hyperwave[1]</field>
	</reference>
	<reference name="uni91" src="bibtex:book" src-info="bibtex:line-25205" type="sharef:book">
		<names type="sharef:author">
			<name>Unicode Consortium</name>
		</names>
		<date value="1991-10"/>
		<address type="sharef:placePublished">Reading, Massachusetts</address>
		<identifier type="sharef:isbn">0201567881</identifier>
		<publisher>Addison Wesley</publisher>
		<title type="sharef:primaryTitle">The Unicode Standard: Worldwide Character Encoding</title>
		<field type="bibtex:topic">unicode[1]</field>
	</reference>
	<reference name="uni96" src="bibtex:book" src-info="bibtex:line-25216" type="sharef:book">
		<names type="sharef:author">
			<name>Unicode Consortium</name>
		</names>
		<date value="1996-08"/>
		<address type="sharef:placePublished">Reading, Massachusetts</address>
		<identifier type="sharef:isbn">0201483459</identifier>
		<publisher>Addison Wesley</publisher>
		<title type="sharef:primaryTitle">The Unicode Standard: Version 2.0</title>
		<field type="bibtex:topic">unicode[1]</field>
		<field type="bibtex:updates">uni91</field>
	</reference>
	<reference name="uni00" src="bibtex:book" src-info="bibtex:line-25228" type="sharef:book">
		<names type="sharef:author">
			<name>Unicode Consortium</name>
		</names>
		<date value="2000-02"/>
		<address type="sharef:placePublished">Reading, Massachusetts</address>
		<identifier type="sharef:isbn">0201616335</identifier>
		<publisher>Addison Wesley</publisher>
		<title type="sharef:primaryTitle">The Unicode Standard: Version 3.0</title>
		<field type="bibtex:topic">unicode[1]</field>
		<field type="bibtex:updates">uni96</field>
	</reference>
	<reference name="unicode4" src="bibtex:book" src-info="bibtex:line-25240" type="sharef:book">
		<names type="sharef:author">
			<name>Unicode Consortium</name>
		</names>
		<date value="2003-08"/>
		<address type="sharef:placePublished">Reading, Massachusetts</address>
		<identifier type="sharef:isbn">0321185781</identifier>
		<publisher>Addison Wesley</publisher>
		<title type="sharef:primaryTitle">The Unicode Standard: Version 4.0</title>
		<field type="bibtex:topic">unicode[1]</field>
		<field type="bibtex:updates">uni00</field>
	</reference>
	<reference name="ps2" src="bibtex:book" src-info="bibtex:line-25252" type="sharef:book">
		<names type="sharef:author">
			<name>Adobe Systems Inc.</name>
		</names>
		<date value="1990-12"/>
		<address type="sharef:placePublished">Reading, Massachusetts</address>
		<edition>2nd</edition>
		<field type="bibtex:index">PostScript 2</field>
		<identifier type="sharef:isbn">0-201-10174-2</identifier>
		<publisher>Addison Wesley</publisher>
		<title type="sharef:primaryTitle">Postscript Language Reference Manual</title>
	</reference>
	<reference name="les99" src="bibtex:book" src-info="bibtex:line-25264" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Lawrence</givenname>
				<surname>Lessig</surname>
			</person>
		</names>
		<date value="1999"/>
		<address type="sharef:placePublished">New York, NY</address>
		<identifier type="sharef:isbn">0465039138</identifier>
		<publisher>Basic Books</publisher>
		<title type="sharef:primaryTitle">Code and Other Laws of Cyberspace</title>
	</reference>
	<reference name="les01" src="bibtex:book" src-info="bibtex:line-25273" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Lawrence</givenname>
				<surname>Lessig</surname>
			</person>
		</names>
		<date value="2001"/>
		<address type="sharef:placePublished">New York, NY</address>
		<identifier type="sharef:isbn">0375726446</identifier>
		<publisher>Vintage Books</publisher>
		<title type="sharef:primaryTitle">The Future of Ideas</title>
	</reference>
	<reference name="ps3" src="bibtex:book" src-info="bibtex:line-25282" type="sharef:book">
		<names type="sharef:author">
			<name>Adobe Systems Inc.</name>
		</names>
		<date value="1999-01"/>
		<address type="sharef:placePublished">Reading, Massachusetts</address>
		<edition>3rd</edition>
		<field type="bibtex:index">PostScript 3</field>
		<identifier type="sharef:isbn">0-201-37922-8</identifier>
		<publisher>Addison Wesley</publisher>
		<title type="sharef:primaryTitle">Postscript Language Reference Manual</title>
	</reference>
	<reference name="bie93" src="bibtex:book" src-info="bibtex:line-25294" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Tim</givenname>
				<surname>Bienz</surname>
			</person>
			<person>
				<givenname>Richard</givenname>
				<surname>Cohn</surname>
			</person>
		</names>
		<date value="1993-07"/>
		<address type="sharef:placePublished">Reading, Massachusetts</address>
		<identifier type="sharef:isbn">0-201-62628-4</identifier>
		<publisher>Addison Wesley</publisher>
		<title type="sharef:primaryTitle">Portable Document Format Reference Manual</title>
		<field type="bibtex:topic">pdf[1]</field>
	</reference>
	<reference name="pdf13" src="bibtex:book" src-info="bibtex:line-25305" type="sharef:book">
		<names type="sharef:author">
			<name>Adobe Systems Inc.</name>
		</names>
		<date value="2000-01"/>
		<address type="sharef:placePublished">Reading, Massachusetts</address>
		<edition>2nd</edition>
		<identifier type="sharef:isbn">0201615886</identifier>
		<publisher>Addison Wesley</publisher>
		<title type="sharef:primaryTitle">PDF Reference: Version 1.3</title>
		<field type="bibtex:topic">pdf[1]</field>
		<field type="bibtex:updates">bie96</field>
		<identifier type="sharef:uri" resourceType="application/pdf">http://www.adobe.com/devnet/pdf/pdfs/PDFReference13.pdf</identifier>
	</reference>
	<reference name="pdf14" src="bibtex:book" src-info="bibtex:line-25319" type="sharef:book">
		<names type="sharef:author">
			<name>Adobe Systems Inc.</name>
		</names>
		<date value="2002-01"/>
		<address type="sharef:placePublished">Reading, Massachusetts</address>
		<edition>3rd</edition>
		<identifier type="sharef:isbn">0201758393</identifier>
		<publisher>Addison Wesley</publisher>
		<title type="sharef:primaryTitle">PDF Reference: Version 1.4</title>
		<field type="bibtex:topic">pdf[1]</field>
		<field type="bibtex:updates">pdf13</field>
		<identifier type="sharef:uri" resourceType="application/pdf">http://www.adobe.com/devnet/pdf/pdfs/PDFReference.pdf</identifier>
	</reference>
	<reference name="pdf15" src="bibtex:book" src-info="bibtex:line-25333" type="sharef:book">
		<names type="sharef:author">
			<name>Adobe Systems Inc.</name>
		</names>
		<date value="2003-08"/>
		<edition>5th</edition>
		<title type="sharef:primaryTitle">PDF Reference: Version 1.5</title>
		<field type="bibtex:topic">pdf[1]</field>
		<field type="bibtex:updates">pdf14</field>
		<identifier type="sharef:uri" resourceType="application/pdf">http://www.adobe.com/devnet/pdf/pdfs/PDFReference15_v6.pdf</identifier>
	</reference>
	<reference name="pdf16" src="bibtex:book" src-info="bibtex:line-25344" type="sharef:book">
		<names type="sharef:author">
			<name>Adobe Systems Inc.</name>
		</names>
		<date value="2004-11"/>
		<address type="sharef:placePublished">Reading, Massachusetts</address>
		<edition>5th</edition>
		<identifier type="sharef:isbn">0321304748</identifier>
		<publisher>Addison Wesley</publisher>
		<title type="sharef:primaryTitle">PDF Reference: Version 1.6</title>
		<field type="bibtex:topic">pdf[1]</field>
		<field type="bibtex:updates">pdf15</field>
		<identifier type="sharef:uri" resourceType="application/pdf">http://www.adobe.com/devnet/pdf/pdfs/PDFReference16.pdf</identifier>
	</reference>
	<reference name="pdf17" src="bibtex:book" src-info="bibtex:line-25358" type="sharef:book">
		<names type="sharef:author">
			<name>Adobe Systems Inc.</name>
		</names>
		<date value="2006-11"/>
		<edition>6th</edition>
		<title type="sharef:primaryTitle">PDF Reference: Version 1.7</title>
		<field type="bibtex:topic">pdf[1]</field>
		<field type="bibtex:updates">pdf16</field>
		<identifier type="sharef:uri" resourceType="application/pdf">http://www.adobe.com/devnet/acrobat/pdfs/pdf_reference_1-7.pdf</identifier>
	</reference>
	<reference name="bry97" src="bibtex:book" src-info="bibtex:line-25369" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Martin</givenname>
				<surname>Bryan</surname>
			</person>
		</names>
		<date value="1997-05"/>
		<address type="sharef:placePublished">Reading, Massachusetts</address>
		<edition>2nd</edition>
		<identifier type="sharef:isbn">0201403943</identifier>
		<publisher>Addison Wesley</publisher>
		<title type="sharef:primaryTitle">SGML and HTML Explained</title>
		<field type="bibtex:topic">sgml[0.8] html[0.7]</field>
	</reference>
	<reference name="hoe98" src="bibtex:book" src-info="bibtex:line-25381" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Alan</givenname>
				<surname>Hoenig</surname>
			</person>
		</names>
		<date value="1998-02"/>
		<address type="sharef:placePublished">Oxford, UK</address>
		<identifier type="sharef:isbn">019509686X</identifier>
		<publisher>Oxford University Press</publisher>
		<title type="sharef:primaryTitle">TeX Unbound: LaTeX &amp; TeX Strategies for Fonts, Graphics, and More</title>
		<field type="bibtex:topic">tex[0.8] latex[0.8]</field>
	</reference>
	<reference name="gol91b" src="bibtex:book" src-info="bibtex:line-25392" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Charles F.</givenname>
				<surname>Goldfarb</surname>
			</person>
		</names>
		<date value="1991-02"/>
		<address type="sharef:placePublished">Oxford, UK</address>
		<publisher>Oxford University Press</publisher>
		<title type="sharef:primaryTitle">The SGML Handbook</title>
		<field type="bibtex:topic">sgml[0.9]</field>
	</reference>
	<reference name="sch00" src="bibtex:book" src-info="bibtex:line-25402" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Keith</givenname>
				<surname>Schengili-Roberts</surname>
			</person>
		</names>
		<date value="2000-05"/>
		<address type="sharef:placePublished">Upper Saddle River, New Jersey</address>
		<identifier type="sharef:isbn">0130834564</identifier>
		<publisher>Prentice-Hall</publisher>
		<title type="sharef:primaryTitle">Core CSS</title>
		<field type="bibtex:topic">css1[0.8] css2[0.8]</field>
	</reference>
	<reference name="ozs99" src="bibtex:book" src-info="bibtex:line-25413" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>M. Tamer</givenname>
				<surname>Özsu</surname>
			</person>
			<person>
				<givenname>Patrick</givenname>
				<surname>Valduriez</surname>
			</person>
		</names>
		<date value="1999-01"/>
		<address type="sharef:placePublished">Upper Saddle River, New Jersey</address>
		<edition>2nd</edition>
		<identifier type="sharef:isbn">978-0136597070</identifier>
		<publisher>Prentice-Hall</publisher>
		<title type="sharef:primaryTitle">Principles of Distributed Database Systems</title>
	</reference>
	<reference name="li96" src="bibtex:book" src-info="bibtex:line-25424" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Xia</givenname>
				<surname>Li</surname>
			</person>
			<person>
				<givenname>Nancy</givenname>
				<surname>Crane</surname>
			</person>
		</names>
		<date value="1996-09"/>
		<address type="sharef:placePublished">Medford, New Jersey</address>
		<identifier type="sharef:isbn">1573870277</identifier>
		<publisher>Information Today, Inc.</publisher>
		<title type="sharef:primaryTitle">Electronic Styles: A Handbook for Citing Electronic Information</title>
	</reference>
	<reference name="gen97" src="bibtex:book" src-info="bibtex:line-25434" type="sharef:book">
		<names type="sharef: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 type="sharef:placePublished">Cambridge, UK</address>
		<identifier type="sharef:isbn">0-521-41350-8</identifier>
		<publisher>Cambridge University Press</publisher>
		<title type="sharef:primaryTitle">Paratexts: Thresholds of Interpretation</title>
		<identifier type="sharef:uri">http://www.cambridge.org/uk/catalogue/catalogue.asp?isbn=0521413508</identifier>
	</reference>
	<reference name="wal98" src="bibtex:book" src-info="bibtex:line-25446" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Janice</givenname>
				<surname>Walker</surname>
			</person>
			<person>
				<givenname>Todd</givenname>
				<surname>Taylor</surname>
			</person>
		</names>
		<date value="1998-10"/>
		<address type="sharef:placePublished">New York, NY</address>
		<identifier type="sharef:isbn">0231107897</identifier>
		<publisher>Columbia University Press</publisher>
		<title type="sharef:primaryTitle">The Columbia Guide to Online Style</title>
		<identifier type="sharef:uri" resourceType="text/html">http://www.columbia.edu/cu/cup/catalog/data/023110/0231107889.HTM</identifier>
	</reference>
	<reference name="coa91" src="bibtex:book" src-info="bibtex:line-25457" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Peter</givenname>
				<surname>Coad</surname>
			</person>
			<person>
				<givenname>Edward</givenname>
				<surname>Yourdon</surname>
			</person>
		</names>
		<date value="1991-10"/>
		<address type="sharef:placePublished">Upper Saddle River, New Jersey</address>
		<edition>2nd</edition>
		<identifier type="sharef:isbn">0136299814</identifier>
		<publisher>Prentice-Hall</publisher>
		<title type="sharef:primaryTitle">Object-Oriented Analysis</title>
		<field type="bibtex:topic">ooa[1]</field>
	</reference>
	<reference name="mey00" src="bibtex:book" src-info="bibtex:line-25469" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Bertrand</givenname>
				<surname>Meyer</surname>
			</person>
		</names>
		<date value="2000-03"/>
		<address type="sharef:placePublished">Upper Saddle River, New Jersey</address>
		<edition>2nd</edition>
		<identifier type="sharef:isbn">0136291554</identifier>
		<publisher>Prentice-Hall</publisher>
		<title type="sharef:primaryTitle">Object-Oriented Software Construction</title>
		<field type="bibtex:topic">eiffel[1] oop[0.9]</field>
	</reference>
	<reference name="luo97" src="bibtex:book" src-info="bibtex:line-25481" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Ari</givenname>
				<surname>Luotonen</surname>
			</person>
		</names>
		<date value="1997-12"/>
		<address type="sharef:placePublished">Upper Saddle River, New Jersey</address>
		<publisher>Prentice-Hall</publisher>
		<title type="sharef:primaryTitle">Web Proxy Servers</title>
		<field type="bibtex:topic">http[0.7] proxy[0.8]</field>
	</reference>
	<reference name="flo99" src="bibtex:book" src-info="bibtex:line-25491" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Michael</givenname>
				<surname>Floyd</surname>
			</person>
		</names>
		<date value="1999-12"/>
		<address type="sharef:placePublished">Upper Saddle River, New Jersey</address>
		<publisher>Prentice-Hall</publisher>
		<title type="sharef:primaryTitle">Building Web Sites with XML</title>
		<field type="bibtex:topic">xml[0.8]</field>
	</reference>
	<reference name="gol98" src="bibtex:book" src-info="bibtex:line-25501" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Charles F.</givenname>
				<surname>Goldfarb</surname>
			</person>
			<person>
				<givenname>Paul</givenname>
				<surname>Prescod</surname>
			</person>
		</names>
		<date value="1998-06"/>
		<address type="sharef:placePublished">Upper Saddle River, New Jersey</address>
		<identifier type="sharef:isbn">0130811521</identifier>
		<publisher>Prentice-Hall</publisher>
		<title type="sharef:primaryTitle">The XML Handbook</title>
		<field type="bibtex:topic">xml[0.8]</field>
	</reference>
	<reference name="gol99b" src="bibtex:book" src-info="bibtex:line-25512" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Charles F.</givenname>
				<surname>Goldfarb</surname>
			</person>
			<person>
				<givenname>Paul</givenname>
				<surname>Prescod</surname>
			</person>
		</names>
		<date value="1999-11"/>
		<address type="sharef:placePublished">Upper Saddle River, New Jersey</address>
		<edition>2nd</edition>
		<identifier type="sharef:isbn">0130147141</identifier>
		<publisher>Prentice-Hall</publisher>
		<title type="sharef:primaryTitle">The XML Handbook</title>
		<field type="bibtex:topic">xml[0.8]</field>
		<field type="bibtex:updates">gol98</field>
	</reference>
	<reference name="gol00b" src="bibtex:book" src-info="bibtex:line-25525" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Charles F.</givenname>
				<surname>Goldfarb</surname>
			</person>
			<person>
				<givenname>Paul</givenname>
				<surname>Prescod</surname>
			</person>
		</names>
		<date value="2000-11"/>
		<address type="sharef:placePublished">Upper Saddle River, New Jersey</address>
		<edition>3rd</edition>
		<identifier type="sharef:isbn">013055068X</identifier>
		<publisher>Prentice-Hall</publisher>
		<title type="sharef:primaryTitle">The XML Handbook</title>
		<field type="bibtex:topic">xml[0.8]</field>
		<field type="bibtex:updates">gol99b</field>
	</reference>
	<reference name="gol01" src="bibtex:book" src-info="bibtex:line-25538" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Charles F.</givenname>
				<surname>Goldfarb</surname>
			</person>
			<person>
				<givenname>Paul</givenname>
				<surname>Prescod</surname>
			</person>
		</names>
		<date value="2001-12"/>
		<address type="sharef:placePublished">Upper Saddle River, New Jersey</address>
		<edition>4th</edition>
		<identifier type="sharef:isbn">0130651982</identifier>
		<publisher>Prentice-Hall</publisher>
		<title type="sharef:primaryTitle">Charles F. Goldfarb's XML Handbook</title>
		<field type="bibtex:topic">xml[0.8]</field>
		<field type="bibtex:updates">gol00b</field>
	</reference>
	<reference name="gol03" src="bibtex:book" src-info="bibtex:line-25551" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Charles F.</givenname>
				<surname>Goldfarb</surname>
			</person>
			<person>
				<givenname>Paul</givenname>
				<surname>Prescod</surname>
			</person>
		</names>
		<date value="2003-11"/>
		<address type="sharef:placePublished">Upper Saddle River, New Jersey</address>
		<edition>5th</edition>
		<identifier type="sharef:isbn">0130497657</identifier>
		<publisher>Prentice-Hall</publisher>
		<title type="sharef:primaryTitle">Charles F. Goldfarb's XML Handbook</title>
		<field type="bibtex:topic">xml[0.8]</field>
		<field type="bibtex:updates">gol01</field>
	</reference>
	<reference name="jel98" src="bibtex:book" src-info="bibtex:line-25564" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Rick</givenname>
				<surname>Jelliffe</surname>
			</person>
		</names>
		<date value="1998"/>
		<address type="sharef:placePublished">Upper Saddle River, New Jersey</address>
		<identifier type="sharef:isbn">0-13-614223-0</identifier>
		<publisher>Prentice-Hall</publisher>
		<title type="sharef:primaryTitle">The XML &amp; SGML Cookbook</title>
		<field type="bibtex:topic">xml[0.8] sgml[0.8]</field>
	</reference>
	<reference name="gar02" src="bibtex:book" src-info="bibtex:line-25574" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Lars Marius</givenname>
				<surname>Garshol</surname>
			</person>
		</names>
		<date value="2002-05"/>
		<address type="sharef:placePublished">Upper Saddle River, New Jersey</address>
		<identifier type="sharef:isbn">0130889024</identifier>
		<publisher>Prentice-Hall</publisher>
		<title type="sharef:primaryTitle">Definitive XML Application Development</title>
		<field type="bibtex:topic">xml[0.8] dom[0.8] sax[0.8] xslt1[0.8]</field>
		<identifier type="sharef:uri">http://www.garshol.priv.no/download/text/ph1/</identifier>
	</reference>
	<reference name="rub97" src="bibtex:book" src-info="bibtex:line-25586" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Yuri</givenname>
				<surname>Rubinsky</surname>
			</person>
			<person>
				<givenname>Murray</givenname>
				<surname>Maloney</surname>
			</person>
		</names>
		<date value="1997-02"/>
		<address type="sharef:placePublished">Upper Saddle River, New Jersey</address>
		<identifier type="sharef:isbn">0135199840</identifier>
		<publisher>Prentice-Hall</publisher>
		<title type="sharef:primaryTitle">SGML on the Web: Small Steps Beyond HTML</title>
		<field type="bibtex:topic">sgml[0.8]</field>
	</reference>
	<reference name="duc98" src="bibtex:book" src-info="bibtex:line-25597" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Bob</givenname>
				<surname>DuCharme</surname>
			</person>
		</names>
		<date value="1998-12"/>
		<address type="sharef:placePublished">Upper Saddle River, New Jersey</address>
		<publisher>Prentice-Hall</publisher>
		<title type="sharef:primaryTitle">XML: The Annotated Specification</title>
		<field type="bibtex:topic">xml[0.9]</field>
	</reference>
	<reference name="meg98" src="bibtex:book" src-info="bibtex:line-25607" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>David</givenname>
				<surname>Megginson</surname>
			</person>
		</names>
		<date value="1998-01"/>
		<address type="sharef:placePublished">Upper Saddle River, New Jersey</address>
		<identifier type="sharef:isbn">0136422993</identifier>
		<publisher>Prentice-Hall</publisher>
		<title type="sharef:primaryTitle">Structuring XML Documents</title>
		<field type="bibtex:topic">xml[0.9]</field>
	</reference>
	<reference name="gru91" src="bibtex:book" src-info="bibtex:line-25618" type="sharef:book">
		<names type="sharef: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="sharef:isbn">0136514316</identifier>
		<publisher>Ellis Horwood</publisher>
		<title type="sharef:primaryTitle">Parsing Techniques: A Practical Guide</title>
		<field type="bibtex:topic">parser[1]</field>
		<identifier type="sharef:uri" resourceType="text/html">http://www.cs.vu.nl/~dick/PTAPG.html</identifier>
	</reference>
	<reference name="mal95" src="bibtex:book" src-info="bibtex:line-25629" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Eve</givenname>
				<surname>Maler</surname>
			</person>
			<person>
				<givenname>Jeanne</givenname>
				<surname>El Andaloussi</surname>
			</person>
		</names>
		<date value="1995-12"/>
		<address type="sharef:placePublished">Upper Saddle River, New Jersey</address>
		<identifier type="sharef:isbn">0133098818</identifier>
		<publisher>Prentice-Hall</publisher>
		<title type="sharef:primaryTitle">Developing SGML DTDs: From Text to Model to Markup</title>
		<field type="bibtex:topic">sgml[0.8] dtd[0.8]</field>
	</reference>
	<reference name="dei99" src="bibtex:book" src-info="bibtex:line-25640" type="sharef:book">
		<names type="sharef: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 type="sharef:placePublished">Upper Saddle River, New Jersey</address>
		<identifier type="sharef:isbn">0130161438</identifier>
		<publisher>Prentice-Hall</publisher>
		<title type="sharef:primaryTitle">Internet &amp; World Wide Web: How to Program</title>
		<field type="bibtex:topic">www[1]</field>
	</reference>
	<reference name="alo03" src="bibtex:book" src-info="bibtex:line-25651" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Gustavo</givenname>
				<surname>Alonso</surname>
			</person>
			<person>
				<givenname>Fabio</givenname>
				<surname>Casati</surname>
			</person>
			<person>
				<givenname>Harumi</givenname>
				<surname>Kuno</surname>
			</person>
			<person>
				<givenname>Vijay</givenname>
				<surname>Machiraju</surname>
			</person>
		</names>
		<date value="2003-10"/>
		<address type="sharef:placePublished">Berlin, Germany</address>
		<identifier type="sharef:isbn">3-540-44008-9</identifier>
		<publisher>Springer-Verlag</publisher>
		<title type="sharef:primaryTitle">Web Services: Concepts, Architectures and Applications</title>
		<identifier type="sharef:uri">http://www.inf.ethz.ch/personal/alonso/WebServicesBook</identifier>
	</reference>
	<reference name="han03" src="bibtex:book" src-info="bibtex:line-25662" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Uwe</givenname>
				<surname>Hansmann</surname>
			</person>
			<person>
				<givenname>Lothar</givenname>
				<surname>Merk</surname>
			</person>
			<person>
				<givenname>Martin Scott</givenname>
				<surname>Nicklous</surname>
			</person>
			<person>
				<givenname>Thomas</givenname>
				<surname>Stober</surname>
			</person>
		</names>
		<date value="2003-08"/>
		<address type="sharef:placePublished">Berlin, Germany</address>
		<edition>2nd</edition>
		<identifier type="sharef:isbn">3540002189</identifier>
		<publisher>Springer-Verlag</publisher>
		<title type="sharef:primaryTitle">Pervasive Computing: The Mobile World</title>
	</reference>
	<reference name="mei03" src="bibtex:book" src-info="bibtex:line-25673" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Christoph</givenname>
				<surname>Meinel</surname>
			</person>
			<person>
				<givenname>Harald</givenname>
				<surname>Sack</surname>
			</person>
		</names>
		<date value="2003-10"/>
		<address type="sharef:placePublished">Berlin, Germany</address>
		<identifier type="sharef:isbn">3540442766</identifier>
		<publisher>Springer-Verlag</publisher>
		<title type="sharef:primaryTitle">WWW: Kommunikation, Internetworking, Web-Technologien</title>
		<field type="bibtex:topic">www[1]</field>
	</reference>
	<reference name="tha00" src="bibtex:book" src-info="bibtex:line-25684" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Bernhard</givenname>
				<surname>Thalheim</surname>
			</person>
		</names>
		<date value="2000"/>
		<address type="sharef:placePublished">Berlin, Germany</address>
		<identifier type="sharef:isbn">3540654704</identifier>
		<publisher>Springer-Verlag</publisher>
		<title type="sharef:primaryTitle">Entity-Relationship Modeling: Foundations of Database Technology</title>
	</reference>
	<reference name="wid02" src="bibtex:book" src-info="bibtex:line-25693" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Richard</givenname>
				<surname>Widhalm</surname>
			</person>
			<person>
				<givenname>Thomas</givenname>
				<surname>Mück</surname>
			</person>
		</names>
		<date value="2001-09"/>
		<address type="sharef:placePublished">Berlin, Germany</address>
		<identifier type="sharef:isbn">3-540-41719-2</identifier>
		<publisher>Springer-Verlag</publisher>
		<title type="sharef:primaryTitle">Topic Maps: Semantische Suche im Internet</title>
		<field type="bibtex:topic">topicmaps[0.8]</field>
	</reference>
	<reference name="von05" src="bibtex:book" src-info="bibtex:line-25704" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Helmut</givenname>
				<surname>Vonhoegen</surname>
			</person>
		</names>
		<date value="2005-03"/>
		<address type="sharef:placePublished">Bonn, Germany</address>
		<edition>3rd</edition>
		<identifier type="sharef:isbn">3-89842-630-0</identifier>
		<publisher>Galileo Computing</publisher>
		<title type="sharef:primaryTitle">Einstieg in XML</title>
		<field type="bibtex:topic">xml[0.7]</field>
	</reference>
	<reference name="str97" src="bibtex:book" src-info="bibtex:line-25716" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Christine</givenname>
				<surname>Strothotte</surname>
			</person>
			<person>
				<givenname>Thomas</givenname>
				<surname>Strothotte</surname>
			</person>
		</names>
		<date value="1997"/>
		<address type="sharef:placePublished">Berlin, Germany</address>
		<identifier type="sharef:isbn">3540594175</identifier>
		<publisher>Springer-Verlag</publisher>
		<title type="sharef:primaryTitle">Seeing Between the Pixels: Pictures in Interactive Systems</title>
		<field type="bibtex:topic">gui[0.8]</field>
	</reference>
	<reference name="wil98" src="bibtex:book" src-info="bibtex:line-25726" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Erik</givenname>
				<surname>Wilde</surname>
			</person>
		</names>
		<date value="1998-11"/>
		<address type="sharef:placePublished">Berlin, Germany</address>
		<identifier type="sharef:isbn">3540642854</identifier>
		<publisher>Springer-Verlag</publisher>
		<title type="sharef:primaryTitle">Wilde's WWW — Technical Foundations of the World Wide Web</title>
		<field type="bibtex:topic">www[1]</field>
		<identifier type="sharef:uri">http://dret.net/netdret/publications#wil98</identifier>
		<identifier type="sharef:uri">http://wildesweb.com/e1/</identifier>
	</reference>
	<reference name="wil99a" src="bibtex:book" src-info="bibtex:line-25739" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Erik</givenname>
				<surname>Wilde</surname>
			</person>
		</names>
		<date value="1999-07"/>
		<address type="sharef:placePublished">Berlin, Germany</address>
		<identifier type="sharef:isbn">3540647007</identifier>
		<publisher>Springer-Verlag</publisher>
		<title type="sharef:primaryTitle">World Wide Web — Technische Grundlagen</title>
		<field type="bibtex:topic">www[1]</field>
		<identifier type="sharef:uri">http://dret.net/netdret/publications#wil99a</identifier>
		<identifier type="sharef:uri">http://wildesweb.com/g1/</identifier>
	</reference>
	<reference name="wil01a" src="bibtex:book" src-info="bibtex:line-25752" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Erik</givenname>
				<surname>Wilde</surname>
			</person>
			<person>
				<givenname>David</givenname>
				<surname>Lowe</surname>
			</person>
		</names>
		<date value="2002-07"/>
		<address type="sharef:placePublished">Reading, Massachusetts</address>
		<identifier type="sharef:isbn">0201703440</identifier>
		<publisher>Addison Wesley</publisher>
		<title type="sharef:primaryTitle">XPath, XLink, XPointer, and XML: A Practical Guide to Web Hyperlinking and Transclusion</title>
		<field type="bibtex:topic">xml[0.6] xlink[0.8] xpointer[0.8] xpath1[0.7]</field>
		<identifier type="sharef:uri">http://dret.net/netdret/publications#wil01a</identifier>
	</reference>
	<reference name="jac92" src="bibtex:book" src-info="bibtex:line-25764" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Ivar</givenname>
				<surname>Jacobson</surname>
			</person>
		</names>
		<date value="1992-06"/>
		<address type="sharef:placePublished">Reading, Massachusetts</address>
		<identifier type="sharef:isbn">0201544350</identifier>
		<publisher>Addison Wesley</publisher>
		<title type="sharef:primaryTitle">Object-Oriented Software Engineering: A Use Case Driven Approach</title>
	</reference>
	<reference name="boo98" src="bibtex:book" src-info="bibtex:line-25774" type="sharef:book">
		<names type="sharef: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 type="sharef:placePublished">Reading, Massachusetts</address>
		<identifier type="sharef:isbn">0201571684</identifier>
		<publisher>Addison Wesley</publisher>
		<title type="sharef:primaryTitle">The Unified Modeling Language User Guide</title>
		<field type="bibtex:topic">uml[0.8]</field>
	</reference>
	<reference name="boo05" src="bibtex:book" src-info="bibtex:line-25785" type="sharef:book">
		<names type="sharef: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 type="sharef:placePublished">Reading, Massachusetts</address>
		<edition>2nd</edition>
		<identifier type="sharef:isbn">0321267974</identifier>
		<publisher>Addison Wesley</publisher>
		<title type="sharef:primaryTitle">The Unified Modeling Language User Guide</title>
		<field type="bibtex:topic">uml[0.8]</field>
		<field type="bibtex:updates">boo98</field>
	</reference>
	<reference name="fow03" src="bibtex:book" src-info="bibtex:line-25798" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Martin</givenname>
				<surname>Fowler</surname>
			</person>
		</names>
		<date value="2003-09"/>
		<address type="sharef:placePublished">Reading, Massachusetts</address>
		<edition>3rd</edition>
		<identifier type="sharef:isbn">0321193687</identifier>
		<publisher>Addison Wesley</publisher>
		<title type="sharef:primaryTitle">UML Distilled: A Brief Guide to the Standard Object Modeling Language</title>
		<field type="bibtex:topic">uml[0.8]</field>
	</reference>
	<reference name="har02" src="bibtex:book" src-info="bibtex:line-25810" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Elliotte Rusty</givenname>
				<surname>Harold</surname>
			</person>
		</names>
		<date value="2002-11"/>
		<address type="sharef:placePublished">Reading, Massachusetts</address>
		<identifier type="sharef:isbn">0201771861</identifier>
		<publisher>Addison Wesley</publisher>
		<title type="sharef:primaryTitle">Processing XML with Java: A Guide to SAX, DOM, JDOM, JAXP, and TrAX</title>
		<field type="bibtex:topic">xml[0.6] java[0.6] sax[0.8] dom[0.8] jdom[0.8] jaxp[0.8] trax[0.8]</field>
		<identifier type="sharef:uri">http://www.cafeconleche.org/books/xmljava/</identifier>
	</reference>
	<reference name="har04" src="bibtex:book" src-info="bibtex:line-25822" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Elliotte Rusty</givenname>
				<surname>Harold</surname>
			</person>
		</names>
		<date value="2003-10"/>
		<address type="sharef:placePublished">Reading, Massachusetts</address>
		<identifier type="sharef:isbn">0-321-15040-6</identifier>
		<publisher>Addison Wesley</publisher>
		<title type="sharef:primaryTitle">Effective XML: 50 Specific Ways to Improve Your XML</title>
		<field type="bibtex:topic">xml[0.9]</field>
		<identifier type="sharef:uri">http://www.cafeconleche.org/books/effectivexml/</identifier>
	</reference>
	<reference name="har08" src="bibtex:book" src-info="bibtex:line-25834" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Elliotte Rusty</givenname>
				<surname>Harold</surname>
			</person>
		</names>
		<date value="2008-05"/>
		<address type="sharef:placePublished">Reading, Massachusetts</address>
		<identifier type="sharef:isbn">0321503635</identifier>
		<publisher>Addison Wesley</publisher>
		<title type="sharef:primaryTitle">Refactoring XML: Improving the Design of Existing Web Applications</title>
		<field type="bibtex:topic">html[0.9] xhtml[0.9] css[0.8]</field>
	</reference>
	<reference name="rot01" src="bibtex:book" src-info="bibtex:line-25845" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Gunter</givenname>
				<surname>Rothfuss</surname>
			</person>
			<person>
				<givenname>Christian</givenname>
				<surname>Ried</surname>
			</person>
		</names>
		<date value="2001"/>
		<address type="sharef:placePublished">Berlin, Germany</address>
		<identifier type="sharef:isbn">3540665943</identifier>
		<publisher>Springer-Verlag</publisher>
		<title type="sharef:seriesTitle">Xpert.press</title>
		<title type="sharef:primaryTitle">Content Management mit XML</title>
		<field type="bibtex:topic">xml[0.6]</field>
		<identifier type="sharef:uri">http://www.xml-content.de</identifier>
	</reference>
	<reference name="eck03" src="bibtex:book" src-info="bibtex:line-25857" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Rainer</givenname>
				<surname>Eckstein</surname>
			</person>
			<person>
				<givenname>Silke</givenname>
				<surname>Eckstein</surname>
			</person>
		</names>
		<date value="2003-11"/>
		<address type="sharef:placePublished">Heidelberg, Germany</address>
		<identifier type="sharef:isbn">3-89864-222-4</identifier>
		<publisher>dpunkt.verlag</publisher>
		<title type="sharef:primaryTitle">XML und Datenmodellierung</title>
		<field type="bibtex:topic">xsd[0.7] rdf[0.7] xml[0.7]</field>
		<identifier type="sharef:uri" resourceType="text/html">http://www.dpunkt.de/buch/3-89864-222-4.html</identifier>
	</reference>
	<reference name="til09" src="bibtex:book" src-info="bibtex:line-25869" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Stefan</givenname>
				<surname>Tilkov</surname>
			</person>
		</names>
		<date value="2009-07"/>
		<address type="sharef:placePublished">Heidelberg, Germany</address>
		<identifier type="sharef:isbn">3-89864-583-5</identifier>
		<publisher>dpunkt.verlag</publisher>
		<title type="sharef:primaryTitle">REST und HTTP: Einsatz der Architektur des Web für Integrationsszenarien</title>
		<field type="bibtex:topic">rest[0.9] http[0.9] soa[0.8]</field>
	</reference>
	<reference name="kno01" src="bibtex:book" src-info="bibtex:line-25880" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Manfred</givenname>
				<surname>Knobloch</surname>
			</person>
			<person>
				<givenname>Matthias</givenname>
				<surname>Kopp</surname>
			</person>
		</names>
		<date value="2001-02"/>
		<address type="sharef:placePublished">Heidelberg, Germany</address>
		<identifier type="sharef:isbn">3932588967</identifier>
		<publisher>dpunkt.verlag</publisher>
		<title type="sharef:primaryTitle">Web-Design mit XML</title>
		<field type="bibtex:topic">xml[0.7] xslt1[0.8] css[0.8] xsl[0.7] xpath1[0.8]</field>
	</reference>
	<reference name="tue03" src="bibtex:book" src-info="bibtex:line-25891" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Can</givenname>
				<surname>Türker</surname>
			</person>
		</names>
		<date value="2003-02"/>
		<address type="sharef:placePublished">Heidelberg, Germany</address>
		<identifier type="sharef:isbn">3898642194</identifier>
		<publisher>dpunkt.verlag</publisher>
		<title type="sharef:primaryTitle">SQL:1999 &amp; SQL:2003</title>
		<field type="bibtex:topic">sqlxml[0.7] sql[0.7] jdbc[0.7] sqlj[0.7]</field>
		<identifier type="sharef:uri" resourceType="text/html">http://www.dpunkt.de/buch/3-89864-219-4.html</identifier>
	</reference>
	<reference name="pud98" src="bibtex:book" src-info="bibtex:line-25903" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Arno</givenname>
				<surname>Puder</surname>
			</person>
			<person>
				<givenname>Kay</givenname>
				<surname>Römer</surname>
			</person>
		</names>
		<date value="1998"/>
		<address type="sharef:placePublished">Heidelberg, Germany</address>
		<identifier type="sharef:isbn">3932588118</identifier>
		<publisher>dpunkt.verlag</publisher>
		<title type="sharef:primaryTitle">MICO is CORBA: A CORBA 2.0 Compliant Implementation</title>
		<field type="bibtex:topic">corba[0.8]</field>
		<identifier type="sharef:uri">http://www.dpunkt.de/mico</identifier>
	</reference>
	<reference name="pud99" src="bibtex:book" src-info="bibtex:line-25914" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Arno</givenname>
				<surname>Puder</surname>
			</person>
			<person>
				<givenname>Kay</givenname>
				<surname>Römer</surname>
			</person>
		</names>
		<date value="1999-04"/>
		<address type="sharef:placePublished">Heidelberg, Germany</address>
		<edition>2nd</edition>
		<identifier type="sharef:isbn">3932588118</identifier>
		<publisher>dpunkt.verlag</publisher>
		<title type="sharef:primaryTitle">MICO is CORBA: A CORBA 2.2 Compliant Implementation</title>
		<field type="bibtex:topic">corba[0.8]</field>
		<field type="bibtex:updates">pud98</field>
		<identifier type="sharef:uri">http://www.dpunkt.de/mico</identifier>
	</reference>
	<reference name="pud00" src="bibtex:book" src-info="bibtex:line-25928" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Arno</givenname>
				<surname>Puder</surname>
			</person>
			<person>
				<givenname>Kay</givenname>
				<surname>Römer</surname>
			</person>
		</names>
		<date value="2000-03"/>
		<address type="sharef:placePublished">Heidelberg, Germany</address>
		<edition>3rd</edition>
		<identifier type="sharef:isbn">393258872X</identifier>
		<publisher>dpunkt.verlag</publisher>
		<title type="sharef:primaryTitle">MICO: An Open Source CORBA Implementation</title>
		<field type="bibtex:topic">corba[0.8]</field>
		<field type="bibtex:updates">pud99</field>
		<identifier type="sharef:uri">http://www.dpunkt.de/mico</identifier>
	</reference>
	<reference name="lub95" src="bibtex:book" src-info="bibtex:line-25942" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Hannes P.</givenname>
				<surname>Lubich</surname>
			</person>
		</names>
		<date value="1995"/>
		<address type="sharef:placePublished">Berlin, Germany</address>
		<identifier type="sharef:isbn">3540588442</identifier>
		<publisher>Springer-Verlag</publisher>
		<title type="sharef:seriesTitle">Lecture Notes in Computer Science</title>
		<title type="sharef:primaryTitle">Towards a CSCW Framework for Scientific Cooperation in Europe</title>
		<volume>889</volume>
	</reference>
	<reference name="het97" src="bibtex:book" src-info="bibtex:line-25953" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Paul S.</givenname>
				<surname>Hethmon</surname>
			</person>
		</names>
		<date value="1997-03"/>
		<address type="sharef:placePublished">Greenwich, Connecticut</address>
		<identifier type="sharef:isbn">1884777376</identifier>
		<publisher>Manning</publisher>
		<title type="sharef:primaryTitle">Illustrated Guide to HTTP</title>
		<field type="bibtex:topic">http[0.9]</field>
	</reference>
	<reference name="lig97" src="bibtex:book" src-info="bibtex:line-25964" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Richard</givenname>
				<surname>Light</surname>
			</person>
		</names>
		<date value="1997-09"/>
		<address type="sharef:placePublished">Indianapolis, Indiana</address>
		<identifier type="sharef:isbn">1575213346</identifier>
		<publisher>Sams.net</publisher>
		<title type="sharef:primaryTitle">Presenting XML</title>
		<field type="bibtex:topic">xml[0.9]</field>
	</reference>
	<reference name="wel01" src="bibtex:book" src-info="bibtex:line-25975" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Luke</givenname>
				<surname>Welling</surname>
			</person>
			<person>
				<givenname>Laura</givenname>
				<surname>Thomson</surname>
			</person>
		</names>
		<date value="2001-03"/>
		<address type="sharef:placePublished">Indianapolis, Indiana</address>
		<identifier type="sharef:isbn">0672317842</identifier>
		<publisher>Sams</publisher>
		<title type="sharef:primaryTitle">PHP and MySQL Web Development</title>
		<field type="bibtex:topic">php[0.8] mysql[0.8]</field>
	</reference>
	<reference name="sul04" src="bibtex:book" src-info="bibtex:line-25986" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Dan</givenname>
				<surname>O'Sullivan</surname>
			</person>
			<person>
				<givenname>Tom</givenname>
				<surname>Igoe</surname>
			</person>
		</names>
		<date value="2004-05"/>
		<abstract>
			<richtext>
				<p>The computer revolution has made it easy for people with little to no technical training to use a computer for such everyday tasks as typing a letter, saving files, or recording data. But what about more imaginative purposes such as starting your car, opening a door, or tracking the contents of your refrigerator? "Physical Computing" will not only change the way you use your computer, it will change the way you think about your computer-how you view its capabilities, how you interact with it, and how you put it to work for you. It's time to bridge the gap between the physical and the virtual-time to use more than just your fingers to interact with your computer. Step outside of the confines of the basic computer and into the broader world of computing.</p>
			</richtext>
		</abstract>
		<address type="sharef:placePublished">Boston, Massachusetts</address>
		<identifier type="sharef:isbn">1-59200-346-X</identifier>
		<publisher>Thomson Course Technology</publisher>
		<title type="sharef:primaryTitle">Physical Computing: Sensing and Controlling the Physical World with Computers</title>
	</reference>
	<reference name="yee08" src="bibtex:book" src-info="bibtex:line-25997" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Raymond</givenname>
				<surname>Yee</surname>
			</person>
		</names>
		<date value="2008-02"/>
		<address type="sharef:placePublished">Berkeley, California</address>
		<identifier type="sharef:isbn">1-59059-858-X</identifier>
		<identifier type="sharef:isbn">978-1-59059-858-0</identifier>
		<publisher>Apress</publisher>
		<title type="sharef:primaryTitle">Pro Web 2.0 Mashups: Remixing Data and Web Services</title>
		<identifier type="sharef:uri">http://www.apress.com/book/view/9781590598580</identifier>
	</reference>
	<reference name="tap06" src="bibtex:book" src-info="bibtex:line-26009" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Don</givenname>
				<surname>Tapscott</surname>
			</person>
			<person>
				<givenname>Anthony D.</givenname>
				<surname>Williams</surname>
			</person>
		</names>
		<date value="2006-12"/>
		<address type="sharef:placePublished">New York, NY</address>
		<identifier type="sharef:isbn">978-1591841388</identifier>
		<publisher>Portfolio</publisher>
		<title type="sharef:primaryTitle">Wikinomics: How Mass Collaboration Changes Everything</title>
		<identifier type="sharef:uri">http://www.wikinomics.com/book/</identifier>
	</reference>
	<reference name="bro02c" src="bibtex:book" src-info="bibtex:line-26020" type="sharef:book">
		<names type="sharef: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 type="sharef:placePublished">Berkeley, California</address>
		<identifier type="sharef:isbn">0782141315</identifier>
		<publisher>Sybex</publisher>
		<title type="sharef:primaryTitle">Cocoon 2 Programming: Web Publishing with XML and Java</title>
		<field type="bibtex:topic">cocoon[0.8]</field>
		<identifier type="sharef:uri">http://www.sybex.com/sybexbooks.nsf/booklist/4131</identifier>
	</reference>
	<reference name="moc02" src="bibtex:book" src-info="bibtex:line-26032" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Lajos</givenname>
				<surname>Moczar</surname>
			</person>
			<person>
				<givenname>Jeremy</givenname>
				<surname>Aston</surname>
			</person>
		</names>
		<date value="2002-12"/>
		<address type="sharef:placePublished">Indianapolis, Indiana</address>
		<identifier type="sharef:isbn">0672322579</identifier>
		<publisher>Sams</publisher>
		<title type="sharef:primaryTitle">Cocoon: Developer's Handbook</title>
		<field type="bibtex:topic">cocoon[0.8]</field>
	</reference>
	<reference name="row01" src="bibtex:book" src-info="bibtex:line-26043" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Michael</givenname>
				<surname>Rowell</surname>
			</person>
		</names>
		<date value="2001-08"/>
		<address type="sharef:placePublished">Indianapolis, Indiana</address>
		<identifier type="sharef:isbn">0672319411</identifier>
		<publisher>Sams</publisher>
		<title type="sharef:primaryTitle">Understanding EAI: Enterprise Application Integration</title>
		<field type="bibtex:topic">eai[0.8]</field>
	</reference>
	<reference name="coo95" src="bibtex:book" src-info="bibtex:line-26054" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Alan</givenname>
				<surname>Cooper</surname>
			</person>
		</names>
		<date value="1995-08"/>
		<address type="sharef:placePublished">Boston, Massachusetts</address>
		<field type="bibtex:index">WWW, HCI, usability</field>
		<identifier type="sharef:isbn">1568843224</identifier>
		<publisher>IDG</publisher>
		<title type="sharef:primaryTitle">About Face: The Essentials of User Interface Design</title>
	</reference>
	<reference name="sie97" src="bibtex:book" src-info="bibtex:line-26065" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>David</givenname>
				<surname>Siegel</surname>
			</person>
		</names>
		<date value="1997-10"/>
		<address type="sharef:placePublished">Indianapolis, Indiana</address>
		<edition>2nd</edition>
		<field type="bibtex:index">WWW, HTML, CSS</field>
		<identifier type="sharef:isbn">1568304331</identifier>
		<publisher>Hayden Books</publisher>
		<title type="sharef:primaryTitle">Creating Killer Web Sites</title>
	</reference>
	<reference name="web97" src="bibtex:book" src-info="bibtex:line-26077" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Timothy</givenname>
				<surname>Webster</surname>
			</person>
		</names>
		<date value="1997-06"/>
		<address type="sharef:placePublished">Indianapolis, Indiana</address>
		<identifier type="sharef:isbn">1568303637</identifier>
		<publisher>Hayden Books</publisher>
		<title type="sharef:primaryTitle">Web Designer's Guide to Graphics: PNG, GIF &amp; JPEG</title>
		<field type="bibtex:topic">png[0.8] gif[0.8] jpeg[0.8]</field>
	</reference>
	<reference name="cha95" src="bibtex:book" src-info="bibtex:line-26088" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>D.</givenname>
				<surname>Chadwick</surname>
			</person>
		</names>
		<date value="1995"/>
		<address type="sharef:placePublished">London, UK</address>
		<identifier type="sharef:isbn">0412430207</identifier>
		<publisher>Chapman &amp; Hall</publisher>
		<title type="sharef:primaryTitle">Understanding X.500 — The Directory</title>
		<field type="bibtex:topic">x500[0.8]</field>
	</reference>
	<reference name="leo99" src="bibtex:book" src-info="bibtex:line-26098" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Alberto</givenname>
				<surname>Leon-Garcia</surname>
			</person>
			<person>
				<givenname>Indra</givenname>
				<surname>Widjaja</surname>
			</person>
		</names>
		<date value="1999-12"/>
		<address type="sharef:placePublished">New York, NY</address>
		<identifier type="sharef:isbn">0070228396</identifier>
		<publisher>McGraw-Hill</publisher>
		<title type="sharef:primaryTitle">Communication Networks: Fundamental Concepts and Key Architectures</title>
	</reference>
	<reference name="gor98" src="bibtex:book" src-info="bibtex:line-26108" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Walter J.</givenname>
				<surname>Goralski</surname>
			</person>
		</names>
		<date value="1998-03"/>
		<address type="sharef:placePublished">New York, NY</address>
		<identifier type="sharef:isbn">0070246793</identifier>
		<publisher>McGraw-Hill</publisher>
		<title type="sharef:primaryTitle">ADSL and DSL Technologies</title>
		<field type="bibtex:topic">dsl[0.7] xdsl[0.7] adsl[0.7]</field>
	</reference>
	<reference name="hec99" src="bibtex:book" src-info="bibtex:line-26119" type="sharef:book">
		<names type="sharef: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 type="sharef:placePublished">New York, NY</address>
		<identifier type="sharef:isbn">0070277354</identifier>
		<publisher>McGraw-Hill</publisher>
		<title type="sharef:primaryTitle">DSL: ADSL, RADSL, SDSL, HDSL, and VDSL</title>
		<field type="bibtex:topic">dsl[0.7] xdsl[0.7] adsl[0.7] radsl[0.7] sdsl[0.7] hdsl[0.7] vdsl[0.7]</field>
	</reference>
	<reference name="kor91" src="bibtex:book" src-info="bibtex:line-26130" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Henry F.</givenname>
				<surname>Korth</surname>
			</person>
			<person>
				<givenname>Abraham</givenname>
				<surname>Silberschatz</surname>
			</person>
		</names>
		<date value="1991"/>
		<address type="sharef:placePublished">New York, NY</address>
		<field type="bibtex:index">ERM, DBMS</field>
		<identifier type="sharef:isbn">0071008047</identifier>
		<publisher>McGraw-Hill</publisher>
		<title type="sharef:primaryTitle">Database System Concepts</title>
	</reference>
	<reference name="sil98" src="bibtex:book" src-info="bibtex:line-26141" type="sharef:book">
		<names type="sharef: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 type="sharef:placePublished">New York, NY</address>
		<edition>3rd</edition>
		<field type="bibtex:index">ERM, DBMS</field>
		<identifier type="sharef:isbn">0071008047</identifier>
		<publisher>McGraw-Hill</publisher>
		<title type="sharef:primaryTitle">Database System Concepts</title>
		<field type="bibtex:updates">kor91</field>
	</reference>
	<reference name="kum95" src="bibtex:book" src-info="bibtex:line-26154" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Vinay</givenname>
				<surname>Kumar</surname>
			</person>
		</names>
		<date value="1995"/>
		<address type="sharef:placePublished">Indianapolis, Indiana</address>
		<field type="bibtex:index">mbone, multimedia</field>
		<identifier type="sharef:isbn">1562053973</identifier>
		<publisher>Macmillan Publishing</publisher>
		<title type="sharef:primaryTitle">Mbone: Interactive Multimedia on the Internet</title>
	</reference>
	<reference name="ada99" src="bibtex:book" src-info="bibtex:line-26164" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Carlisle</givenname>
				<surname>Adams</surname>
			</person>
			<person>
				<givenname>Steve</givenname>
				<surname>Lloyd</surname>
			</person>
		</names>
		<date value="1999-11"/>
		<address type="sharef:placePublished">Indianapolis, Indiana</address>
		<field type="bibtex:index">PKI, PKIX, X.509</field>
		<identifier type="sharef:isbn">157870166X</identifier>
		<publisher>Macmillan Publishing</publisher>
		<title type="sharef:primaryTitle">Understanding Public-Key Infrastructure: Concepts, Standards, and Deployment Considerations</title>
	</reference>
	<reference name="bau98" src="bibtex:book" src-info="bibtex:line-26175" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Michael</givenname>
				<surname>Baumgardt</surname>
			</person>
		</names>
		<date value="1998-04"/>
		<address type="sharef:placePublished">Berlin, Germany</address>
		<field type="bibtex:index">WWW, HTML, DHTML, CSS, JavaScript</field>
		<identifier type="sharef:isbn">354062662X</identifier>
		<publisher>Springer-Verlag</publisher>
		<title type="sharef:primaryTitle">Creative Web Design</title>
	</reference>
	<reference name="tra95" src="bibtex:book" src-info="bibtex:line-26186" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Brian</givenname>
				<surname>Travis</surname>
			</person>
			<person>
				<givenname>Dale</givenname>
				<surname>Waldt</surname>
			</person>
		</names>
		<date value="1995-12"/>
		<address type="sharef:placePublished">Berlin, Germany</address>
		<identifier type="sharef:isbn">3540577300</identifier>
		<publisher>Springer-Verlag</publisher>
		<title type="sharef:primaryTitle">The SGML Implementation Guide</title>
		<field type="bibtex:topic">sgml[0.8]</field>
	</reference>
	<reference name="san95" src="bibtex:book" src-info="bibtex:line-26197" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Adelino</givenname>
				<surname>Santos</surname>
			</person>
		</names>
		<date value="1995"/>
		<address type="sharef:placePublished">Berlin, Germany</address>
		<field type="bibtex:index">CoMEdiA, groupware, collaborative editing</field>
		<identifier type="sharef:isbn">3-540-60001-9</identifier>
		<publisher>Springer-Verlag</publisher>
		<title type="sharef:primaryTitle">Multimedia and Groupware for Editing</title>
	</reference>
	<reference name="gal96" src="bibtex:book" src-info="bibtex:line-26207" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Wilbert O.</givenname>
				<surname>Galitz</surname>
			</person>
		</names>
		<date value="1996-12"/>
		<address type="sharef:placePublished">Chichester, England</address>
		<identifier type="sharef:isbn">0471157554</identifier>
		<publisher>John Wiley &amp; Sons</publisher>
		<title type="sharef:primaryTitle">The Essential Guide to User Interface Design: An Introduction to GUI Design Principles and Techniques</title>
		<field type="bibtex:topic">gui[0.8]</field>
	</reference>
	<reference name="ghe97" src="bibtex:book" src-info="bibtex:line-26218" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Carlo</givenname>
				<surname>Ghezzi</surname>
			</person>
			<person>
				<givenname>Mehdi</givenname>
				<surname>Jazayeri</surname>
			</person>
		</names>
		<date value="1997-06"/>
		<address type="sharef:placePublished">Chichester, England</address>
		<edition>3rd</edition>
		<identifier type="sharef:isbn">0471104264</identifier>
		<publisher>John Wiley &amp; Sons</publisher>
		<title type="sharef:primaryTitle">Programming Language Concepts</title>
		<identifier type="sharef:uri">http://www.infosys.tuwien.ac.at/pl-book/</identifier>
	</reference>
	<reference name="wei97" src="bibtex:book" src-info="bibtex:line-26230" type="sharef:book">
		<names type="sharef: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 type="sharef:placePublished">Chichester, England</address>
		<identifier type="sharef:isbn">0471175498</identifier>
		<publisher>John Wiley &amp; Sons</publisher>
		<title type="sharef:primaryTitle">GUI Design Essentials</title>
		<field type="bibtex:topic">gui[0.8]</field>
	</reference>
	<reference name="ruh00" src="bibtex:book" src-info="bibtex:line-26241" type="sharef:book">
		<names type="sharef: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 type="sharef:placePublished">Chichester, England</address>
		<identifier type="sharef:isbn">0471376418</identifier>
		<publisher>John Wiley &amp; Sons</publisher>
		<title type="sharef:primaryTitle">Enterprise Application Integration: A Wiley Tech Brief</title>
		<field type="bibtex:topic">eai[0.8]</field>
	</reference>
	<reference name="low99" src="bibtex:book" src-info="bibtex:line-26252" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>David</givenname>
				<surname>Lowe</surname>
			</person>
			<person>
				<givenname>Wendy</givenname>
				<surname>Hall</surname>
			</person>
		</names>
		<date value="1999-02"/>
		<address type="sharef:placePublished">Chichester, England</address>
		<field type="bibtex:index">WWW, hypermedia</field>
		<identifier type="sharef:isbn">0-471-98312-8</identifier>
		<publisher>John Wiley &amp; Sons</publisher>
		<title type="sharef:seriesTitle">Worldwide Series in Computer Science</title>
		<title type="sharef:primaryTitle">Hypermedia &amp; the Web: An Engineering Approach</title>
	</reference>
	<reference name="gra00" src="bibtex:book" src-info="bibtex:line-26264" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Ian S.</givenname>
				<surname>Graham</surname>
			</person>
		</names>
		<date value="2000-03"/>
		<address type="sharef:placePublished">New York, NY</address>
		<field type="bibtex:index">XHTML, CSS</field>
		<identifier type="sharef:isbn">0-471-37485-7</identifier>
		<publisher>John Wiley &amp; Sons</publisher>
		<title type="sharef:primaryTitle">XHTML 1.0 Language and Design Sourcebook: The Next Generation HTML</title>
	</reference>
	<reference name="rom99" src="bibtex:book" src-info="bibtex:line-26275" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Ed</givenname>
				<surname>Roman</surname>
			</person>
		</names>
		<date value="1999-09"/>
		<address type="sharef:placePublished">New York, NY</address>
		<identifier type="sharef:isbn">0471332291</identifier>
		<publisher>John Wiley &amp; Sons</publisher>
		<title type="sharef:primaryTitle">Mastering Enterprise JavaBeans and the Java 2 Platform, Enterprise Edition</title>
		<field type="bibtex:topic">j2ee[0.8] ejb[0.8]</field>
	</reference>
	<reference name="orf98" src="bibtex:book" src-info="bibtex:line-26286" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Robert</givenname>
				<surname>Orfali</surname>
			</person>
			<person>
				<givenname>Dan</givenname>
				<surname>Harkey</surname>
			</person>
		</names>
		<date value="1998-02"/>
		<address type="sharef:placePublished">New York, NY</address>
		<edition>2nd</edition>
		<field type="bibtex:index">WWW, Java, CORBA, IIOP</field>
		<identifier type="sharef:isbn">0471163511</identifier>
		<publisher>John Wiley &amp; Sons</publisher>
		<title type="sharef:primaryTitle">Client/Server Programming with Java and CORBA</title>
	</reference>
	<reference name="los99" src="bibtex:book" src-info="bibtex:line-26298" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Pete</givenname>
				<surname>Loshin</surname>
			</person>
		</names>
		<date value="1999-11"/>
		<address type="sharef:placePublished">New York, NY</address>
		<field type="bibtex:index">SMTP, IMAP, POP, MIME, PGP, iCalendar, vCard</field>
		<identifier type="sharef:isbn">0471345970</identifier>
		<publisher>John Wiley &amp; Sons</publisher>
		<title type="sharef:primaryTitle">Essential Email Standards: RFCs and Protocols Made Practical</title>
	</reference>
	<reference name="gos98" src="bibtex:book" src-info="bibtex:line-26309" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Anup K.</givenname>
				<surname>Ghosh</surname>
			</person>
		</names>
		<date value="1998-02"/>
		<address type="sharef:placePublished">New York, NY</address>
		<field type="bibtex:index">WWW, security</field>
		<identifier type="sharef:isbn">0471192236</identifier>
		<publisher>John Wiley &amp; Sons</publisher>
		<title type="sharef:primaryTitle">E-Commerce Security: Weak Links, Best Defenses</title>
	</reference>
	<reference name="sch95b" src="bibtex:book" src-info="bibtex:line-26320" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Bruce</givenname>
				<surname>Schneier</surname>
			</person>
		</names>
		<date value="1995-10"/>
		<address type="sharef:placePublished">New York, NY</address>
		<edition>2nd</edition>
		<field type="bibtex:index">cryptography</field>
		<identifier type="sharef:isbn">0471117099</identifier>
		<publisher>John Wiley &amp; Sons</publisher>
		<title type="sharef:primaryTitle">Applied Cryptography: Protocols, Algorithms, and Source Code in C</title>
	</reference>
	<reference name="sch00a" src="bibtex:book" src-info="bibtex:line-26332" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Bruce</givenname>
				<surname>Schneier</surname>
			</person>
		</names>
		<date value="2000-08"/>
		<address type="sharef:placePublished">New York, NY</address>
		<identifier type="sharef:isbn">0471253111</identifier>
		<publisher>John Wiley &amp; Sons</publisher>
		<title type="sharef:primaryTitle">Secrets &amp; Lies: Digital Security in a Networked World</title>
		<identifier type="sharef:uri" resourceType="text/html">http://www.schneier.com/book-sandl.html</identifier>
	</reference>
	<reference name="sch03c" src="bibtex:book" src-info="bibtex:line-26343" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Bruce</givenname>
				<surname>Schneier</surname>
			</person>
		</names>
		<date value="2003-09"/>
		<address type="sharef:placePublished">New York, NY</address>
		<identifier type="sharef:isbn">0387026207</identifier>
		<publisher>Copernicus</publisher>
		<title type="sharef:primaryTitle">Beyond Fear: Thinking Sensibly about Security in an Uncertain World</title>
		<identifier type="sharef:uri" resourceType="text/html">http://www.schneier.com/book-beyondfear.html</identifier>
	</reference>
	<reference name="fow02" src="bibtex:book" src-info="bibtex:line-26354" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Martin</givenname>
				<surname>Fowler</surname>
			</person>
		</names>
		<date value="2002-11"/>
		<address type="sharef:placePublished">Reading, Massachusetts</address>
		<identifier type="sharef:isbn">0321127420</identifier>
		<publisher>Addison Wesley</publisher>
		<title type="sharef:primaryTitle">Patterns of Enterprise Application Architecture</title>
	</reference>
	<reference name="fow99" src="bibtex:book" src-info="bibtex:line-26364" type="sharef:book">
		<names type="sharef: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 type="sharef:placePublished">Reading, Massachusetts</address>
		<identifier type="sharef:isbn">0201485672</identifier>
		<publisher>Addison Wesley</publisher>
		<title type="sharef:primaryTitle">Refactoring: Improving the Design of Existing Code</title>
	</reference>
	<reference name="tho96" src="bibtex:book" src-info="bibtex:line-26374" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Stephen A.</givenname>
				<surname>Thomas</surname>
			</person>
		</names>
		<date value="1996-01"/>
		<address type="sharef:placePublished">New York, NY</address>
		<field type="bibtex:index">IPng, RSVP, OSPF, RIP, TCP, UDP, DNS</field>
		<identifier type="sharef:isbn">1471130885</identifier>
		<publisher>John Wiley &amp; Sons</publisher>
		<title type="sharef:primaryTitle">IPng and the TCP/IP Protocols</title>
	</reference>
	<reference name="gra97" src="bibtex:book" src-info="bibtex:line-26385" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Ian S.</givenname>
				<surname>Graham</surname>
			</person>
		</names>
		<date value="1997-10"/>
		<address type="sharef:placePublished">New York, NY</address>
		<field type="bibtex:index">WWW, HTML, CSS</field>
		<identifier type="sharef:isbn">0471196649</identifier>
		<publisher>John Wiley &amp; Sons</publisher>
		<title type="sharef:primaryTitle">HTML Stylesheet Sourcebook</title>
	</reference>
	<reference name="hal96b" src="bibtex:book" src-info="bibtex:line-26396" type="sharef:book">
		<names type="sharef: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 type="sharef:placePublished">Boston, Massachusetts</address>
		<identifier type="sharef:isbn">0792396790</identifier>
		<publisher>Kluwer Academic Publishers</publisher>
		<title type="sharef:primaryTitle">Rethinking Hypermedia: The Microcosm Approach</title>
		<field type="bibtex:topic">microcosm[1] webcosm[1]</field>
	</reference>
	<reference name="der94" src="bibtex:book" src-info="bibtex:line-26407" type="sharef:book">
		<names type="sharef: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 type="sharef:placePublished">Boston, Massachusetts</address>
		<identifier type="sharef:isbn">0792394321</identifier>
		<publisher>Kluwer Academic Publishers</publisher>
		<title type="sharef:primaryTitle">Making Hypermedia Work: A User's Guide to HyTime</title>
		<field type="bibtex:topic">hytime[0.9]</field>
	</reference>
	<reference name="der97" src="bibtex:book" src-info="bibtex:line-26418" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Steven J.</givenname>
				<surname>DeRose</surname>
			</person>
		</names>
		<date value="1997-07"/>
		<address type="sharef:placePublished">Boston, Massachusetts</address>
		<identifier type="sharef:isbn">0792399439</identifier>
		<publisher>Kluwer Academic Publishers</publisher>
		<title type="sharef:primaryTitle">The SGML FAQ Book: Understanding the Foundation of HTML and XML</title>
		<field type="bibtex:topic">sgml[0.8] xml[0.7] html[0.7]</field>
	</reference>
	<reference name="del96" src="bibtex:book" src-info="bibtex:line-26429" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Luca</givenname>
				<surname>Delgrossi</surname>
			</person>
		</names>
		<date value="1996"/>
		<address type="sharef:placePublished">Boston, Massachusetts</address>
		<field type="bibtex:index">ST-II, RSVP</field>
		<identifier type="sharef:isbn">0792396693</identifier>
		<publisher>Kluwer Academic Publishers</publisher>
		<title type="sharef:primaryTitle">Design of Reservation Protocols for Multimedia Communication</title>
	</reference>
	<reference name="ste93" src="bibtex:book" src-info="bibtex:line-26439" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Douglas</givenname>
				<surname>Steedman</surname>
			</person>
		</names>
		<date value="1993"/>
		<address type="sharef:placePublished">Twickenham, UK</address>
		<identifier type="sharef:isbn">1871802067</identifier>
		<publisher>Technology Appraisals</publisher>
		<title type="sharef:primaryTitle">Abstract Syntax Notation One (ASN.1): The Tutorial and Reference</title>
		<field type="bibtex:topic">asn1[0.8]</field>
	</reference>
	<reference name="ste93b" src="bibtex:book" src-info="bibtex:line-26449" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Douglas</givenname>
				<surname>Steedman</surname>
			</person>
		</names>
		<date value="1993"/>
		<address type="sharef:placePublished">Twickenham, UK</address>
		<publisher>Technology Appraisals</publisher>
		<title type="sharef:primaryTitle">The Directory Standard and its Application</title>
		<field type="bibtex:topic">x500[0.8]</field>
	</reference>
	<reference name="wyb90" src="bibtex:book" src-info="bibtex:line-26458" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Dieter</givenname>
				<surname>Wybranietz</surname>
			</person>
		</names>
		<date value="1990"/>
		<address type="sharef:placePublished">Berlin, Germany</address>
		<identifier type="sharef:isbn">3540525513</identifier>
		<publisher>Springer-Verlag</publisher>
		<title type="sharef:seriesTitle">Informatik-Fachberichte</title>
		<title type="sharef:primaryTitle">Multicast-Kommunikation in Verteilten Systemen</title>
		<volume>242</volume>
	</reference>
	<reference name="alp98" src="bibtex:book" src-info="bibtex:line-26469" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Paul</givenname>
				<surname>Alpar</surname>
			</person>
		</names>
		<date value="1998"/>
		<address type="sharef:placePublished">Berlin, Germany</address>
		<edition>2nd</edition>
		<identifier type="sharef:isbn">3540644490</identifier>
		<publisher>Springer-Verlag</publisher>
		<title type="sharef:primaryTitle">Kommerzielle Nutzung des Internet</title>
	</reference>
	<reference name="bou00" src="bibtex:book" src-info="bibtex:line-26479" type="sharef:book">
		<names type="sharef: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 type="sharef:placePublished">Chicago, Illinois</address>
		<identifier type="sharef:isbn">1861003439</identifier>
		<publisher>Wrox Press</publisher>
		<title type="sharef:primaryTitle">Beginning XHTML</title>
		<field type="bibtex:topic">xhtml[0.8]</field>
	</reference>
	<reference name="hun07" src="bibtex:book" src-info="bibtex:line-26490" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>David</givenname>
				<surname>Hunter</surname>
			</person>
			<person>
				<givenname>Jeff</givenname>
				<surname>Rafter</surname>
			</person>
			<person>
				<givenname>Joe</givenname>
				<surname>Fawcett</surname>
			</person>
			<person>
				<givenname>Eric</givenname>
				<surname link="van der">Vlist</surname>
			</person>
			<person>
				<givenname>Danny</givenname>
				<surname>Ayers</surname>
			</person>
			<person>
				<givenname>Jon</givenname>
				<surname>Duckett</surname>
			</person>
			<person>
				<givenname>Andrew</givenname>
				<surname>Watt</surname>
			</person>
			<person>
				<givenname>Linda</givenname>
				<surname>McKinnon</surname>
			</person>
		</names>
		<date value="2007"/>
		<address type="sharef:placePublished">Chicago, Illinois</address>
		<edition>4th</edition>
		<identifier type="sharef:isbn">978-0-470-11487-2</identifier>
		<publisher>Wrox Press</publisher>
		<title type="sharef:primaryTitle">Beginning XML</title>
	</reference>
	<reference name="ger05" src="bibtex:book" src-info="bibtex:line-26500" type="sharef:book">
		<names type="sharef: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 type="sharef:placePublished">Chicago, Illinois</address>
		<identifier type="sharef:isbn">076459723X</identifier>
		<publisher>Wrox Press</publisher>
		<title type="sharef:primaryTitle">Professional LAMP: Linux, Apache, MySQL and PHP Web Development</title>
		<field type="bibtex:topic">lamp[0.9] linux[0.8] apachehttp[0.8] mysql[0.8] php[0.8]</field>
		<identifier type="sharef:uri" resourceType="text/html">http://www.wrox.com/WileyCDA/WroxTitle/productCd-076459723X.html</identifier>
	</reference>
	<reference name="spe99" src="bibtex:book" src-info="bibtex:line-26512" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Paul</givenname>
				<surname>Spencer</surname>
			</person>
		</names>
		<date value="1999-04"/>
		<address type="sharef:placePublished">Chicago, Illinois</address>
		<identifier type="sharef:isbn">1861002289</identifier>
		<publisher>Wrox Press</publisher>
		<title type="sharef:primaryTitle">XML Design and Implementation</title>
		<field type="bibtex:topic">xml[0.8]</field>
	</reference>
	<reference name="wai99" src="bibtex:book" src-info="bibtex:line-26523" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Peter</givenname>
				<surname>Wainwright</surname>
			</person>
		</names>
		<date value="1999-11"/>
		<address type="sharef:placePublished">Chicago, Illinois</address>
		<identifier type="sharef:isbn">1861003021</identifier>
		<publisher>Wrox Press</publisher>
		<title type="sharef:primaryTitle">Professional Apache</title>
		<field type="bibtex:topic">apachehttp[0.8]</field>
	</reference>
	<reference name="kay00" src="bibtex:book" src-info="bibtex:line-26534" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Michael</givenname>
				<surname>Kay</surname>
			</person>
		</names>
		<date value="2000-04"/>
		<address type="sharef:placePublished">Chicago, Illinois</address>
		<identifier type="sharef:isbn">1861003129</identifier>
		<publisher>Wrox Press</publisher>
		<title type="sharef:primaryTitle">XSLT Programmer's Reference</title>
		<field type="bibtex:topic">xslt1[0.8] xpath1[0.7]</field>
	</reference>
	<reference name="kay01" src="bibtex:book" src-info="bibtex:line-26545" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Michael</givenname>
				<surname>Kay</surname>
			</person>
		</names>
		<date value="2001-03"/>
		<address type="sharef:placePublished">Chicago, Illinois</address>
		<identifier type="sharef:isbn">1861005067</identifier>
		<publisher>Wrox Press</publisher>
		<title type="sharef:primaryTitle">XSLT 1.1 Programmer's Reference</title>
		<field type="bibtex:topic">xslt1[0.8] xpath1[0.7]</field>
		<field type="bibtex:updates">kay00</field>
	</reference>
	<reference name="wes01" src="bibtex:book" src-info="bibtex:line-26557" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Duane</givenname>
				<surname>Wessels</surname>
			</person>
		</names>
		<date value="2001-06"/>
		<address type="sharef:placePublished">Sebastopol, California</address>
		<identifier type="sharef:isbn">156592536X</identifier>
		<publisher>O'Reilly &amp; Associates</publisher>
		<title type="sharef:primaryTitle">Web Caching</title>
		<field type="bibtex:topic">cache[0.9]</field>
		<identifier type="sharef:uri">http://www.oreilly.com/catalog/webcaching/</identifier>
	</reference>
	<reference name="hol01a" src="bibtex:book" src-info="bibtex:line-26569" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>G. Ken</givenname>
				<surname>Holman</surname>
			</person>
		</names>
		<date value="2001-12"/>
		<address type="sharef:placePublished">Sebastopol, California</address>
		<identifier type="sharef:isbn">0130651966</identifier>
		<publisher>O'Reilly &amp; Associates</publisher>
		<title type="sharef:primaryTitle">Definitive XSLT and XPath</title>
		<field type="bibtex:topic">xslt1[0.8] xpath1[0.7]</field>
	</reference>
	<reference name="hol01b" src="bibtex:book" src-info="bibtex:line-26580" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Steven</givenname>
				<surname>Holzner</surname>
			</person>
		</names>
		<date value="2001-07"/>
		<address type="sharef:placePublished">Indianapolis, Indiana</address>
		<identifier type="sharef:isbn">0735711364</identifier>
		<publisher>New Riders</publisher>
		<title type="sharef:primaryTitle">Inside XSLT</title>
		<field type="bibtex:topic">xslt1[0.8] xpath1[0.7]</field>
	</reference>
	<reference name="zie02" src="bibtex:book" src-info="bibtex:line-26591" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Carsten</givenname>
				<surname>Ziegeler</surname>
			</person>
			<person>
				<givenname>Matthew</givenname>
				<surname>Langham</surname>
			</person>
		</names>
		<date value="2002-07"/>
		<address type="sharef:placePublished">Indianapolis, Indiana</address>
		<identifier type="sharef:isbn">0735712352</identifier>
		<publisher>New Riders</publisher>
		<title type="sharef:primaryTitle">Cocoon: Building XML Applications</title>
		<field type="bibtex:topic">cocoon[0.8]</field>
	</reference>
	<reference name="hje01" src="bibtex:book" src-info="bibtex:line-26602" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Johan</givenname>
				<surname>Hjelm</surname>
			</person>
			<person>
				<givenname>Peter</givenname>
				<surname>Stark</surname>
			</person>
		</names>
		<date value="2001-09"/>
		<address type="sharef:placePublished">New York, NY</address>
		<identifier type="sharef:isbn">0471406031</identifier>
		<publisher>John Wiley &amp; Sons</publisher>
		<title type="sharef:seriesTitle">Professional Developer's Guide Series</title>
		<title type="sharef:primaryTitle">XSLT: The Ultimate Guide to Transforming Web Data</title>
		<field type="bibtex:topic">xslt1[0.8] xpath1[0.7]</field>
	</reference>
	<reference name="ten01" src="bibtex:book" src-info="bibtex:line-26614" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Jeni</givenname>
				<surname>Tennison</surname>
			</person>
		</names>
		<date value="2001-09"/>
		<address type="sharef:placePublished">New York, NY</address>
		<identifier type="sharef:isbn">0764547763</identifier>
		<publisher>John Wiley &amp; Sons</publisher>
		<title type="sharef:primaryTitle">XSLT and XPath On The Edge</title>
		<field type="bibtex:topic">xslt1[0.8] xpath1[0.8]</field>
	</reference>
	<reference name="ten02" src="bibtex:book" src-info="bibtex:line-26625" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Jeni</givenname>
				<surname>Tennison</surname>
			</person>
		</names>
		<date value="2002-05"/>
		<address type="sharef:placePublished">Chicago, Illinois</address>
		<identifier type="sharef:isbn">1861005946</identifier>
		<publisher>Wrox Press</publisher>
		<title type="sharef:primaryTitle">Beginning XSLT</title>
		<field type="bibtex:topic">xslt1[0.8] xpath1[0.7]</field>
	</reference>
	<reference name="tid01" src="bibtex:book" src-info="bibtex:line-26636" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Doug</givenname>
				<surname>Tidwell</surname>
			</person>
		</names>
		<date value="2001-08"/>
		<address type="sharef:placePublished">Sebastopol, California</address>
		<identifier type="sharef:isbn">0596000537</identifier>
		<publisher>O'Reilly &amp; Associates</publisher>
		<title type="sharef:primaryTitle">XSLT</title>
		<field type="bibtex:topic">xslt1[0.8] xpath1[0.7]</field>
	</reference>
	<reference name="wal01" src="bibtex:book" src-info="bibtex:line-26647" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Priscilla</givenname>
				<surname>Walmsley</surname>
			</person>
		</names>
		<date value="2001-12"/>
		<address type="sharef:placePublished">Englewood Cliffs, New Jersey</address>
		<identifier type="sharef:isbn">0130655678</identifier>
		<publisher>Prentice-Hall</publisher>
		<title type="sharef:primaryTitle">Definitive XML Schema</title>
		<field type="bibtex:topic">xsd[0.8]</field>
	</reference>
	<reference name="bin02" src="bibtex:book" src-info="bibtex:line-26658" type="sharef:book">
		<names type="sharef: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 type="sharef:placePublished">Reading, Massachusetts</address>
		<identifier type="sharef:isbn">0672323745</identifier>
		<publisher>Addison Wesley</publisher>
		<title type="sharef:primaryTitle">The XML Schema Complete Reference</title>
		<field type="bibtex:topic">xsd[0.8]</field>
	</reference>
	<reference name="vli02c" src="bibtex:book" src-info="bibtex:line-26669" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Eric</givenname>
				<surname link="van der">Vlist</surname>
			</person>
		</names>
		<date value="2002-06"/>
		<address type="sharef:placePublished">Sebastopol, California</address>
		<identifier type="sharef:isbn">0596002521</identifier>
		<publisher>O'Reilly &amp; Associates</publisher>
		<title type="sharef:primaryTitle">XML Schema</title>
		<field type="bibtex:topic">xsd[0.8]</field>
	</reference>
	<reference name="dor99" src="bibtex:book" src-info="bibtex:line-26680" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Naganand</givenname>
				<surname>Doraswamy</surname>
			</person>
			<person>
				<givenname>Dan</givenname>
				<surname>Harkins</surname>
			</person>
		</names>
		<date value="1999-07"/>
		<address type="sharef:placePublished">Englewood Cliffs, New Jersey</address>
		<identifier type="sharef:isbn">0130118982</identifier>
		<publisher>Prentice-Hall</publisher>
		<title type="sharef:seriesTitle">Internet Infrastructure Series</title>
		<title type="sharef:primaryTitle">IPSec: The New Security Standard for the Internet, Intranets and Virtual Private Networks</title>
		<field type="bibtex:topic">ipsec[0.8]</field>
	</reference>
	<reference name="sta00" src="bibtex:book" src-info="bibtex:line-26692" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>William</givenname>
				<surname>Stallings</surname>
			</person>
		</names>
		<date value="2000-04"/>
		<address type="sharef:placePublished">Englewood Cliffs, New Jersey</address>
		<field type="bibtex:index">security</field>
		<identifier type="sharef:isbn">0130160938</identifier>
		<publisher>Prentice-Hall</publisher>
		<title type="sharef:primaryTitle">Network Security Essentials: Applications and Standards</title>
	</reference>
	<reference name="sta96" src="bibtex:book" src-info="bibtex:line-26703" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>William</givenname>
				<surname>Stallings</surname>
			</person>
		</names>
		<date value="1996-08"/>
		<address type="sharef:placePublished">Englewood Cliffs, New Jersey</address>
		<edition>5th</edition>
		<publisher>Prentice-Hall</publisher>
		<title type="sharef:primaryTitle">Data and Computer Communications</title>
	</reference>
	<reference name="sta99b" src="bibtex:book" src-info="bibtex:line-26713" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>William</givenname>
				<surname>Stallings</surname>
			</person>
		</names>
		<date value="1999-09"/>
		<address type="sharef:placePublished">Englewood Cliffs, New Jersey</address>
		<edition>6th</edition>
		<identifier type="sharef:isbn">0130843709</identifier>
		<publisher>Prentice-Hall</publisher>
		<title type="sharef:primaryTitle">Data and Computer Communications</title>
		<field type="bibtex:updates">sta96</field>
	</reference>
	<reference name="sta98" src="bibtex:book" src-info="bibtex:line-26725" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>William</givenname>
				<surname>Stallings</surname>
			</person>
		</names>
		<date value="1998-07"/>
		<address type="sharef:placePublished">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="sharef:isbn">0138690170</identifier>
		<publisher>Prentice-Hall</publisher>
		<title type="sharef:primaryTitle">Cryptography and Network Security: Principles and Practice</title>
	</reference>
	<reference name="tan94" src="bibtex:book" src-info="bibtex:line-26737" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Andrew S.</givenname>
				<surname>Tanenbaum</surname>
			</person>
		</names>
		<date value="1994-09"/>
		<address type="sharef:placePublished">Englewood Cliffs, New Jersey</address>
		<identifier type="sharef:isbn">0132199084</identifier>
		<publisher>Prentice-Hall</publisher>
		<title type="sharef:primaryTitle">Distributed Operating Systems</title>
	</reference>
	<reference name="tan96" src="bibtex:book" src-info="bibtex:line-26747" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Andrew S.</givenname>
				<surname>Tanenbaum</surname>
			</person>
		</names>
		<date value="1996-03"/>
		<address type="sharef:placePublished">Englewood Cliffs, New Jersey</address>
		<edition>3rd</edition>
		<publisher>Prentice-Hall</publisher>
		<title type="sharef:primaryTitle">Computer Networks</title>
	</reference>
	<reference name="flu95" src="bibtex:book" src-info="bibtex:line-26757" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>François</givenname>
				<surname>Fluckiger</surname>
			</person>
		</names>
		<date value="1995"/>
		<address type="sharef:placePublished">London, UK</address>
		<field type="bibtex:index">multimedia, networks</field>
		<identifier type="sharef:isbn">0131909924</identifier>
		<publisher>Prentice-Hall</publisher>
		<title type="sharef:primaryTitle">Understanding Networked Multimedia: Applications and Technology</title>
	</reference>
	<reference name="bor90" src="bibtex:book" src-info="bibtex:line-26767" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Nathaniel S.</givenname>
				<surname>Borenstein</surname>
			</person>
		</names>
		<date value="1990"/>
		<address type="sharef:placePublished">Englewood Cliffs, New Jersey</address>
		<field type="bibtex:index">multimedia, ATK</field>
		<identifier type="sharef:isbn">0130366331</identifier>
		<publisher>Prentice-Hall</publisher>
		<title type="sharef:primaryTitle">Multimedia Applications Development with the Andrew Toolkit</title>
	</reference>
	<reference name="atm93" src="bibtex:book" src-info="bibtex:line-26777" type="sharef:book">
		<names type="sharef:author">
			<name>ATM Forum</name>
		</names>
		<date value="1993"/>
		<address type="sharef:placePublished">Englewood Cliffs, New Jersey</address>
		<field type="bibtex:index">ATM, UNI 3.0</field>
		<identifier type="sharef:isbn">0132258633</identifier>
		<publisher>Prentice-Hall</publisher>
		<title type="sharef:primaryTitle">ATM User-Network Interface Specification Version 3.0</title>
	</reference>
	<reference name="atm95" src="bibtex:book" src-info="bibtex:line-26787" type="sharef:book">
		<names type="sharef:author">
			<name>ATM Forum</name>
		</names>
		<date value="1995"/>
		<address type="sharef:placePublished">Englewood Cliffs, New Jersey</address>
		<field type="bibtex:index">ATM, UNI 3.1</field>
		<identifier type="sharef:isbn">013393828X</identifier>
		<publisher>Prentice-Hall</publisher>
		<title type="sharef:primaryTitle">ATM User-Network Interface Specification Version 3.1</title>
	</reference>
	<reference name="jai90" src="bibtex:book" src-info="bibtex:line-26797" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Bijendra N.</givenname>
				<surname>Jain</surname>
			</person>
			<person>
				<givenname>Ashok K.</givenname>
				<surname>Agrawala</surname>
			</person>
		</names>
		<date value="1990"/>
		<address type="sharef:placePublished">Amsterdam, Netherlands</address>
		<identifier type="sharef:isbn">0444884904</identifier>
		<publisher>Elsevier</publisher>
		<title type="sharef:primaryTitle">Open Systems Interconnection: Its Architecture and Protocols</title>
		<field type="bibtex:topic">osi[0.9]</field>
	</reference>
	<reference name="cer02" src="bibtex:book" src-info="bibtex:line-26807" type="sharef:book">
		<names type="sharef: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 type="sharef:placePublished">Amsterdam, Netherlands</address>
		<identifier type="sharef:isbn">1558608435</identifier>
		<publisher>Elsevier</publisher>
		<title type="sharef:primaryTitle">Designing Data-Intensive Web Applications</title>
		<field type="bibtex:topic">webml[0.9] uml[0.8]</field>
	</reference>
	<reference name="wil91" src="bibtex:book" src-info="bibtex:line-26818" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Paul</givenname>
				<surname>Wilson</surname>
			</person>
		</names>
		<date value="1991"/>
		<address type="sharef:placePublished">Oxford, UK</address>
		<identifier type="sharef:isbn">1871516269</identifier>
		<publisher>intellect</publisher>
		<title type="sharef:primaryTitle">Computer-Supported Cooperative Work</title>
	</reference>
	<reference name="osf92" src="bibtex:book" src-info="bibtex:line-26827" type="sharef:book">
		<names type="sharef:author">
			<name>Open Software Foundation</name>
		</names>
		<date value="1992-07"/>
		<address type="sharef:placePublished">Englewood Cliffs, New Jersey</address>
		<identifier type="sharef:isbn">0134906241</identifier>
		<publisher>Prentice-Hall</publisher>
		<title type="sharef:primaryTitle">Introduction to OSF DCE</title>
		<field type="bibtex:topic">dce[1]</field>
	</reference>
	<reference name="cha99" src="bibtex:book" src-info="bibtex:line-26838" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Steven</givenname>
				<surname>Champeon</surname>
			</person>
			<person>
				<givenname>David S.</givenname>
				<surname>Fox</surname>
			</person>
		</names>
		<date value="1999-05"/>
		<address type="sharef:placePublished">Foster City, California</address>
		<identifier type="sharef:isbn">0764532677</identifier>
		<publisher>M&amp;T Books</publisher>
		<title type="sharef:primaryTitle">Building Dynamic HTML GUIs</title>
		<field type="bibtex:topic">dhtml[0.8] gui[0.8]</field>
	</reference>
	<reference name="ros01" src="bibtex:book" src-info="bibtex:line-26849" type="sharef:book">
		<names type="sharef: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 type="sharef:placePublished">New York, NY</address>
		<identifier type="sharef:isbn">0764548891</identifier>
		<publisher>M&amp;T Books</publisher>
		<title type="sharef:primaryTitle">Digital Rights Management: Business and Technology</title>
		<field type="bibtex:topic">drm[0.9]</field>
	</reference>
	<reference name="ros98" src="bibtex:book" src-info="bibtex:line-26860" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Louis</givenname>
				<surname>Rosenfeld</surname>
			</person>
			<person>
				<givenname>Peter</givenname>
				<surname>Morville</surname>
			</person>
		</names>
		<date value="1998-03"/>
		<address type="sharef:placePublished">Sebastopol, California</address>
		<field type="bibtex:index">WWW</field>
		<identifier type="sharef:isbn">1565922824</identifier>
		<publisher>O'Reilly &amp; Associates</publisher>
		<title type="sharef:primaryTitle">Information Architecture for the World Wide Web</title>
	</reference>
	<reference name="cha99b" src="bibtex:book" src-info="bibtex:line-26871" type="sharef:book">
		<names type="sharef: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 type="sharef:placePublished">Boston, Massachusetts</address>
		<identifier type="sharef:isbn">1-882114-67-1</identifier>
		<publisher>GNU Press</publisher>
		<title type="sharef:primaryTitle">Texinfo: The GNU Documentation Format</title>
		<field type="bibtex:topic">texinfo[0.9]</field>
		<identifier type="sharef:uri" resourceType="text/html">http://www.gnupress.org/book9.html</identifier>
	</reference>
	<reference name="eff98" src="bibtex:book" src-info="bibtex:line-26883" type="sharef:book">
		<names type="sharef:author">
			<name>Electronic Frontier Foundation</name>
		</names>
		<date value="1998-05"/>
		<address type="sharef:placePublished">Sebastopol, California</address>
		<identifier type="sharef:isbn">1565925203</identifier>
		<publisher>O'Reilly &amp; Associates</publisher>
		<title type="sharef:primaryTitle">Cracking DES: Secrets of Encryption Research, Wiretap Politics &amp; Chip Design</title>
		<field type="bibtex:topic">des[0.9]</field>
	</reference>
	<reference name="fri97" src="bibtex:book" src-info="bibtex:line-26894" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Jeffrey E. F.</givenname>
				<surname>Friedl</surname>
			</person>
		</names>
		<date value="1997-01"/>
		<address type="sharef:placePublished">Sebastopol, California</address>
		<field type="bibtex:index">regular expressions</field>
		<identifier type="sharef:isbn">1565922573</identifier>
		<publisher>O'Reilly &amp; Associates</publisher>
		<title type="sharef:primaryTitle">Mastering Regular Expressions</title>
	</reference>
	<reference name="won00" src="bibtex:book" src-info="bibtex:line-26905" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Clinton</givenname>
				<surname>Wong</surname>
			</person>
		</names>
		<date value="2000-05"/>
		<address type="sharef:placePublished">Sebastopol, California</address>
		<field type="bibtex:index">HTTP</field>
		<identifier type="sharef:isbn">1565928628</identifier>
		<publisher>O'Reilly &amp; Associates</publisher>
		<title type="sharef:primaryTitle">HTTP Pocket Reference</title>
	</reference>
	<reference name="hal00a" src="bibtex:book" src-info="bibtex:line-26916" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Eric</givenname>
				<surname>Hall</surname>
			</person>
			<person>
				<givenname>Vinton G.</givenname>
				<surname>Cerf</surname>
			</person>
		</names>
		<date value="2000-02"/>
		<address type="sharef:placePublished">Sebastopol, California</address>
		<identifier type="sharef:isbn">1565925726</identifier>
		<publisher>O'Reilly &amp; Associates</publisher>
		<title type="sharef:primaryTitle">Internet Core Protocols: The Definitive Guide</title>
		<field type="bibtex:topic">ip[0.8] tcp[0.8] udp[0.8]</field>
	</reference>
	<reference name="hal00b" src="bibtex:book" src-info="bibtex:line-26927" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Eric</givenname>
				<surname>Hall</surname>
			</person>
			<person>
				<givenname>Mike</givenname>
				<surname>Loukides</surname>
			</person>
		</names>
		<date value="2000-10"/>
		<address type="sharef:placePublished">Sebastopol, California</address>
		<identifier type="sharef:isbn">1565926064</identifier>
		<publisher>O'Reilly &amp; Associates</publisher>
		<title type="sharef:primaryTitle">Internet Application Protocols: The Definitive Guide</title>
	</reference>
	<reference name="wal99" src="bibtex:book" src-info="bibtex:line-26937" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Norman</givenname>
				<surname>Walsh</surname>
			</person>
			<person>
				<givenname>Leonard</givenname>
				<surname>Muellner</surname>
			</person>
		</names>
		<date value="1999-07"/>
		<address type="sharef:placePublished">Sebastopol, California</address>
		<identifier type="sharef:isbn">1565925807</identifier>
		<publisher>O'Reilly &amp; Associates</publisher>
		<title type="sharef:primaryTitle">DocBook: The Definitive Guide</title>
		<field type="bibtex:topic">docbook[1]</field>
		<identifier type="sharef:uri">http://www.docbook.org/</identifier>
		<identifier type="sharef:uri" resourceType="text/html">http://www.oreilly.com/catalog/docbook/chapter/book/docbook.html</identifier>
	</reference>
	<reference name="goo98" src="bibtex:book" src-info="bibtex:line-26950" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Danny</givenname>
				<surname>Goodman</surname>
			</person>
		</names>
		<date value="1998-07"/>
		<address type="sharef:placePublished">Sebastopol, California</address>
		<field type="bibtex:index">DHTML</field>
		<publisher>O'Reilly &amp; Associates</publisher>
		<title type="sharef:primaryTitle">Dynamic HTML: The Definitive Reference</title>
	</reference>
	<reference name="spe98" src="bibtex:book" src-info="bibtex:line-26960" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Henry</givenname>
				<surname>Spencer</surname>
			</person>
			<person>
				<givenname>David</givenname>
				<surname>Lawrence</surname>
			</person>
		</names>
		<date value="1998-01"/>
		<address type="sharef:placePublished">Sebastopol, California</address>
		<field type="bibtex:index">usenet</field>
		<publisher>O'Reilly &amp; Associates</publisher>
		<title type="sharef:primaryTitle">Managing Usenet</title>
	</reference>
	<reference name="ros92" src="bibtex:book" src-info="bibtex:line-26970" type="sharef:book">
		<names type="sharef: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 type="sharef:placePublished">Sebastopol, California</address>
		<identifier type="sharef:isbn">1565920058</identifier>
		<publisher>O'Reilly &amp; Associates</publisher>
		<title type="sharef:primaryTitle">Understanding DCE</title>
		<field type="bibtex:topic">dce[1]</field>
	</reference>
	<reference name="sch97b" src="bibtex:book" src-info="bibtex:line-26981" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Randal L.</givenname>
				<surname>Schwartz</surname>
			</person>
			<person>
				<givenname>Tom</givenname>
				<surname>Christiansen</surname>
			</person>
		</names>
		<date value="1997-07"/>
		<address type="sharef:placePublished">Sebastopol, California</address>
		<field type="bibtex:index">Perl</field>
		<identifier type="sharef:isbn">1565922840</identifier>
		<publisher>O'Reilly &amp; Associates</publisher>
		<title type="sharef:primaryTitle">Learning Perl</title>
	</reference>
	<reference name="wal96" src="bibtex:book" src-info="bibtex:line-26992" type="sharef:book">
		<names type="sharef: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 type="sharef:placePublished">Sebastopol, California</address>
		<field type="bibtex:index">Perl</field>
		<identifier type="sharef:isbn">1565921496</identifier>
		<publisher>O'Reilly &amp; Associates</publisher>
		<title type="sharef:primaryTitle">Programming Perl</title>
	</reference>
	<reference name="wal00" src="bibtex:book" src-info="bibtex:line-27003" type="sharef:book">
		<names type="sharef: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 type="sharef:placePublished">Sebastopol, California</address>
		<edition>3rd</edition>
		<field type="bibtex:index">Perl</field>
		<identifier type="sharef:isbn">0596000278</identifier>
		<publisher>O'Reilly &amp; Associates</publisher>
		<title type="sharef:primaryTitle">Programming Perl</title>
		<field type="bibtex:updates">wal96</field>
	</reference>
	<reference name="lut96" src="bibtex:book" src-info="bibtex:line-27016" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Mark</givenname>
				<surname>Lutz</surname>
			</person>
		</names>
		<date value="1996-10"/>
		<address type="sharef:placePublished">Sebastopol, California</address>
		<identifier type="sharef:isbn">1565921976</identifier>
		<publisher>O'Reilly &amp; Associates</publisher>
		<title type="sharef:primaryTitle">Programming Python</title>
	</reference>
	<reference name="lau97" src="bibtex:book" src-info="bibtex:line-27026" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Ben</givenname>
				<surname>Laurie</surname>
			</person>
			<person>
				<givenname>Peter</givenname>
				<surname>Laurie</surname>
			</person>
		</names>
		<date value="1997-03"/>
		<address type="sharef:placePublished">Sebastopol, California</address>
		<field type="bibtex:index">apache</field>
		<identifier type="sharef:isbn">1-56592-250-6</identifier>
		<publisher>O'Reilly &amp; Associates</publisher>
		<title type="sharef:primaryTitle">Apache: The Definitive Guide</title>
	</reference>
	<reference name="lau99" src="bibtex:book" src-info="bibtex:line-27037" type="sharef:book">
		<names type="sharef: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 type="sharef:placePublished">Sebastopol, California</address>
		<edition>2nd</edition>
		<field type="bibtex:index">apache</field>
		<identifier type="sharef:isbn">1-56592-528-9</identifier>
		<publisher>O'Reilly &amp; Associates</publisher>
		<title type="sharef:primaryTitle">Apache: The Definitive Guide</title>
		<field type="bibtex:updates">lau97</field>
	</reference>
	<reference name="con02" src="bibtex:book" src-info="bibtex:line-27050" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Jim</givenname>
				<surname>Conallen</surname>
			</person>
		</names>
		<date value="2002-10"/>
		<address type="sharef:placePublished">Reading, Massachusetts</address>
		<edition>2nd</edition>
		<identifier type="sharef:isbn">0201730383</identifier>
		<publisher>Addison Wesley</publisher>
		<title type="sharef:primaryTitle">Building Web Applications with UML</title>
		<field type="bibtex:topic">uml[0.8]</field>
	</reference>
	<reference name="ste97" src="bibtex:book" src-info="bibtex:line-27062" type="sharef:book">
		<names type="sharef: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 type="sharef:placePublished">Sebastopol, California</address>
		<identifier type="sharef:isbn">1-56592-265-4</identifier>
		<publisher>O'Reilly &amp; Associates</publisher>
		<title type="sharef:primaryTitle">Scripting Languages: Automating the Web</title>
	</reference>
	<reference name="alb92" src="bibtex:book" src-info="bibtex:line-27072" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Paul</givenname>
				<surname>Albitz</surname>
			</person>
			<person>
				<givenname>Cricket</givenname>
				<surname>Liu</surname>
			</person>
		</names>
		<date value="1992-01"/>
		<address type="sharef:placePublished">Sebastopol, California</address>
		<identifier type="sharef:isbn">1-56592-010-4</identifier>
		<publisher>O'Reilly &amp; Associates</publisher>
		<title type="sharef:primaryTitle">DNS and BIND</title>
	</reference>
	<reference name="liu98" src="bibtex:book" src-info="bibtex:line-27082" type="sharef:book">
		<names type="sharef: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 type="sharef:placePublished">Sebastopol, California</address>
		<edition>3rd</edition>
		<identifier type="sharef:isbn">1-56592-512-2</identifier>
		<publisher>O'Reilly &amp; Associates</publisher>
		<title type="sharef:primaryTitle">DNS and BIND</title>
	</reference>
	<reference name="gun96" src="bibtex:book" src-info="bibtex:line-27093" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Shishir</givenname>
				<surname>Gundavaram</surname>
			</person>
		</names>
		<date value="1996-04"/>
		<address type="sharef:placePublished">Sebastopol, California</address>
		<field type="bibtex:index">CGI, Perl</field>
		<identifier type="sharef:isbn">1-56592-168-2</identifier>
		<publisher>O'Reilly &amp; Associates</publisher>
		<title type="sharef:primaryTitle">CGI Programming on the World Wide Web</title>
	</reference>
	<reference name="gue00" src="bibtex:book" src-info="bibtex:line-27104" type="sharef:book">
		<names type="sharef: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 type="sharef:placePublished">Sebastopol, California</address>
		<edition>2nd</edition>
		<field type="bibtex:index">CGI, Perl</field>
		<identifier type="sharef:isbn">1565924193</identifier>
		<publisher>O'Reilly &amp; Associates</publisher>
		<title type="sharef:primaryTitle">CGI Programming with Perl</title>
		<field type="bibtex:updates">gun96</field>
	</reference>
	<reference name="bar91" src="bibtex:book" src-info="bibtex:line-27117" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>John. A.</givenname>
				<surname>Barry</surname>
			</person>
		</names>
		<date value="1991"/>
		<address type="sharef:placePublished">Cambridge, Massachusetts</address>
		<identifier type="sharef:isbn">0262023334</identifier>
		<publisher>The MIT Press</publisher>
		<title type="sharef:primaryTitle">Technobabble</title>
	</reference>
	<reference name="sve00" src="bibtex:book" src-info="bibtex:line-27126" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Elaine</givenname>
				<surname>Svenonius</surname>
			</person>
		</names>
		<date value="2000-04"/>
		<abstract>
			<richtext>
				<p>Instant electronic access to digital information is the single most distinguishing attribute of the information age. The elaborate retrieval mechanisms that support such access are a product of technology. But technology is not enough. The effectiveness of a system for accessing information is a direct function of the intelligence put into organizing it. Just as the practical field of engineering has theoretical physics as its underlying base, the design of systems for organizing information rests on an intellectual foundation. The subject of this book is the systematized body of knowledge that constitutes this foundation. Integrating the disparate disciplines of descriptive cataloging, subject cataloging, indexing, and classification, the book adopts a conceptual framework that views the process of organizing information as the use of a special language of description called a bibliographic language. The book is divided into two parts. The first part is an analytic discussion of the intellectual foundation of information organization. The second part moves from generalities to particulars, presenting an overview of three bibliographic languages: work languages, document languages, and subject languages. It looks at these languages in terms of their vocabulary, semantics, and syntax. The book is written in an exceptionally clear style, at a level that makes it understandable to those outside the discipline of library and information science.</p>
			</richtext>
		</abstract>
		<address type="sharef:placePublished">Cambridge, Massachusetts</address>
		<identifier type="sharef:isbn">0-262-19433-3</identifier>
		<publisher>The MIT Press</publisher>
		<title type="sharef:primaryTitle">The Intellectual Foundation of Information Organization</title>
		<identifier type="sharef:uri">http://mitpress.mit.edu/catalog/item/default.asp?ttype=2&amp;tid=3792</identifier>
	</reference>
	<reference name="sel03" src="bibtex:book" src-info="bibtex:line-27138" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Abigail J.</givenname>
				<surname>Sellen</surname>
			</person>
			<person>
				<givenname>Richard H. R.</givenname>
				<surname>Harper</surname>
			</person>
		</names>
		<date value="2003"/>
		<abstract>
			<richtext>
				<p>Over the past thirty years, many people have proclaimed the imminent arrival of the paperless office. Yet even the World Wide Web, which allows almost any computer to read and display another computer's documents, has only increased the amount of printing done by computer users. The use of e-mail in an organization increases paper consumption by an average of 40 percent. In The Myth of the Paperless Office, Abigail Sellen and Richard Harper study paper usage as a way to understand the work that people do and the reasons they do it the way they do. Using the tools of enthnography and cognitive psychology, they look at paper use from the level of the individual up to that of organizational culture. Central to Sellen and Harper's investigation is the concept of "affordances" — the activities that an object allows, or affords. The physical properties of paper (its being thin, light, porous, opaque, and flexible) afford the human actions of grasping, carrying, folding, writing, and so on. The concept of affordance allows us to compare the affordances of paper with those of existing digital devices. We can then ask what kinds of devices or systems would make new kinds of activities possible or better support current activities. The authors argue that paper will continue to play an important role in office life. Rather than pursue the ideal of the paperless office, we should work toward a future in which paper and electronic document tools work in concert and organizational processes make optimal use of both.</p>
			</richtext>
		</abstract>
		<address type="sharef:placePublished">Cambridge, Massachusetts</address>
		<identifier type="sharef:isbn">026269283X</identifier>
		<publisher>The MIT Press</publisher>
		<title type="sharef:primaryTitle">The Myth of the Paperless Office</title>
	</reference>
	<reference name="har93" src="bibtex:book" src-info="bibtex:line-27148" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Brian</givenname>
				<surname>Harvey</surname>
			</person>
			<person>
				<givenname>Matthew</givenname>
				<surname>Wright</surname>
			</person>
		</names>
		<date value="1993-12"/>
		<address type="sharef:placePublished">Cambridge, Massachusetts</address>
		<identifier type="sharef:isbn">0262082268</identifier>
		<publisher>The MIT Press</publisher>
		<title type="sharef:primaryTitle">Simply Scheme: Introducing Computer Science</title>
		<field type="bibtex:topic">scheme[0.8]</field>
	</reference>
	<reference name="har99" src="bibtex:book" src-info="bibtex:line-27159" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Brian</givenname>
				<surname>Harvey</surname>
			</person>
			<person>
				<givenname>Matthew</givenname>
				<surname>Wright</surname>
			</person>
		</names>
		<date value="1999-07"/>
		<address type="sharef:placePublished">Cambridge, Massachusetts</address>
		<edition>2nd</edition>
		<identifier type="sharef:isbn">0262082810</identifier>
		<publisher>The MIT Press</publisher>
		<title type="sharef:primaryTitle">Simply Scheme: Introducing Computer Science</title>
		<field type="bibtex:topic">scheme[0.8]</field>
		<field type="bibtex:updates">har93</field>
	</reference>
	<reference name="abe96" src="bibtex:book" src-info="bibtex:line-27172" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Harold</givenname>
				<surname>Abelson</surname>
			</person>
			<person>
				<givenname>Gerald Jay</givenname>
				<surname>Sussman</surname>
			</person>
		</names>
		<date value="1996-07"/>
		<address type="sharef:placePublished">Cambridge, Massachusetts</address>
		<edition>2nd</edition>
		<identifier type="sharef:isbn">0262011530</identifier>
		<publisher>The MIT Press</publisher>
		<title type="sharef:primaryTitle">Structure and Interpretation of Computer Programs</title>
		<identifier type="sharef:uri">http://mitpress.mit.edu/sicp/</identifier>
	</reference>
	<reference name="glu05a" src="bibtex:book" src-info="bibtex:line-27184" type="sharef:book">
		<names type="sharef: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 type="sharef:placePublished">Cambridge, Massachusetts</address>
		<identifier type="sharef:isbn">0-262-07261-0</identifier>
		<publisher>The MIT Press</publisher>
		<title type="sharef:primaryTitle">Document Engineering</title>
		<identifier type="sharef:uri">http://mitpress.mit.edu/catalog/item/default.asp?ttype=2&amp;tid=10476</identifier>
		<identifier type="sharef:uri">http://www.docengineering.com/</identifier>
	</reference>
	<reference name="hil06" src="bibtex:book" src-info="bibtex:line-27197" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Linda L.</givenname>
				<surname>Hill</surname>
			</person>
		</names>
		<date value="2006-09"/>
		<abstract>
			<richtext>
				<p>Georeferencing — relating information to geographic location — has been incorporated into today's information systems in various ways. We use online services to map our route from one place to another; science, business, and government increasingly use geographic information systems (GIS) to hold and analyze data. Most georeferenced information searches using today's information systems are done by text query. But text searches for placenames fall short–when, for example, a place is known by several names (or by none). In addition, text searches don't cover all sources of geographic data; maps are traditionally accessed only through special indexes, filing systems, and agency contacts; data from remote sensing images or aerial photography is indexed by geospatial location (mathematical coordinates such as longitude and latitude). In this book, Linda Hill describes the advantages of integrating placename-based and geospatial referencing, introducing an approach to "unified georeferencing" that uses placename and geospatial referencing interchangeably across all types of information storage and retrieval systems. After a brief overview of relevant material from cognitive psychology on how humans perceive and respond to geographic space, Hill introduces the reader to basic information about geospatial information objects, concepts of geospatial referencing, the role of gazetteer data, the ways in which geospatial referencing has been included in metadata structures, and methods for the implementation of geographic information retrieval (GIR). Georeferencing will be a valuable reference for librarians, archivists, scientific data managers, information managers, designers of online services, and any information professional who deals with place-based information.</p>
			</richtext>
		</abstract>
		<address type="sharef:placePublished">Cambridge, Massachusetts</address>
		<identifier type="sharef:isbn">0-262-08354-X</identifier>
		<publisher>The MIT Press</publisher>
		<title type="sharef:primaryTitle">Georeferencing: The Geographic Associations of Information</title>
		<identifier type="sharef:uri">http://mitpress.mit.edu/catalog/item/default.asp?ttype=2&amp;tid=11007</identifier>
	</reference>
	<reference name="ant04" src="bibtex:book" src-info="bibtex:line-27209" type="sharef:book">
		<names type="sharef: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 type="sharef:placePublished">Cambridge, Massachusetts</address>
		<identifier type="sharef:isbn">0-262-01210-3</identifier>
		<publisher>The MIT Press</publisher>
		<title type="sharef:primaryTitle">A Semantic Web Primer</title>
		<field type="bibtex:topic">rdf[0.7] rdfs[0.7] owl[0.7]</field>
		<identifier type="sharef:uri">http://mitpress.mit.edu/catalog/item/default.asp?ttype=2&amp;tid=10140</identifier>
	</reference>
	<reference name="pry95" src="bibtex:book" src-info="bibtex:line-27221" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Martin</givenname>
				<surname link="de">Prycker</surname>
			</person>
		</names>
		<date value="1995"/>
		<address type="sharef:placePublished">London, UK</address>
		<edition>3rd</edition>
		<field type="bibtex:index">ATM</field>
		<identifier type="sharef:isbn">0133421716</identifier>
		<publisher>Prentice-Hall</publisher>
		<title type="sharef:primaryTitle">Asynchronous Transfer Mode: Solution for Broadband ISDN</title>
	</reference>
	<reference name="bla95" src="bibtex:book" src-info="bibtex:line-27232" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Uyless</givenname>
				<surname>Black</surname>
			</person>
		</names>
		<date value="1995"/>
		<address type="sharef:placePublished">Englewood Cliffs, New Jersey</address>
		<field type="bibtex:index">ATM</field>
		<identifier type="sharef:isbn">013297178X</identifier>
		<publisher>Prentice-Hall</publisher>
		<title type="sharef:primaryTitle">ATM: Foundation for Broadband Networks</title>
	</reference>
	<reference name="gor90" src="bibtex:book" src-info="bibtex:line-27242" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Walter</givenname>
				<surname>Gora</surname>
			</person>
			<person>
				<givenname>Reinhard</givenname>
				<surname>Speyerer</surname>
			</person>
		</names>
		<date value="1990"/>
		<address type="sharef:placePublished">Bergheim, Germany</address>
		<edition>2nd</edition>
		<field type="bibtex:index">ASN.1</field>
		<identifier type="sharef:isbn">3892380236</identifier>
		<publisher>DATACOM</publisher>
		<title type="sharef:primaryTitle">Abstract Syntax Notation One (ASN.1)</title>
	</reference>
	<reference name="ste95" src="bibtex:book" src-info="bibtex:line-27253" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Ralf</givenname>
				<surname>Steinmetz</surname>
			</person>
			<person>
				<givenname>Klara</givenname>
				<surname>Nahrstedt</surname>
			</person>
		</names>
		<date value="1995"/>
		<address type="sharef:placePublished">Upper Saddle River, New Jersey</address>
		<field type="bibtex:index">Multimedia</field>
		<identifier type="sharef:isbn">0133244350</identifier>
		<publisher>Prentice-Hall</publisher>
		<title type="sharef:primaryTitle">Multimedia: Computing, Communications, and Applications</title>
	</reference>
	<reference name="ste90" src="bibtex:book" src-info="bibtex:line-27263" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>W. Richard</givenname>
				<surname>Stevens</surname>
			</person>
		</names>
		<date value="1990-04"/>
		<address type="sharef:placePublished">Englewood Cliffs, New Jersey</address>
		<field type="bibtex:index">Unix, TCP/IP</field>
		<identifier type="sharef:isbn">0139498761</identifier>
		<publisher>Prentice-Hall</publisher>
		<title type="sharef:primaryTitle">Unix Network Programming</title>
	</reference>
	<reference name="cat97" src="bibtex:book" src-info="bibtex:line-27274" type="sharef:book">
		<names type="sharef: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 type="sharef:placePublished">San Francisco, California</address>
		<field type="bibtex:index">ODMG</field>
		<identifier type="sharef:isbn">1558604634</identifier>
		<publisher>Morgan Kaufmann Publishers</publisher>
		<title type="sharef:primaryTitle">The Object Database Standard: ODMG 2.0</title>
	</reference>
	<reference name="abi99" src="bibtex:book" src-info="bibtex:line-27285" type="sharef:book">
		<names type="sharef: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 type="sharef:placePublished">San Francisco, California</address>
		<field type="bibtex:index">WWW, DBMS, XML</field>
		<identifier type="sharef:isbn">055860622X</identifier>
		<publisher>Morgan Kaufmann Publishers</publisher>
		<title type="sharef:primaryTitle">Data on the Web: From Relations to Semistructured Data and XML</title>
	</reference>
	<reference name="bea04" src="bibtex:book" src-info="bibtex:line-27296" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>James</givenname>
				<surname>Bean</surname>
			</person>
		</names>
		<date value="2004"/>
		<address type="sharef:placePublished">San Francisco, California</address>
		<identifier type="sharef:isbn">1-55860-907-5</identifier>
		<publisher>Morgan Kaufmann Publishers</publisher>
		<title type="sharef:primaryTitle">XML for Data Architects: Designing for Reuse and Integration</title>
		<field type="bibtex:topic">xml[0.8] xsd[0.8]</field>
	</reference>
	<reference name="hoq00" src="bibtex:book" src-info="bibtex:line-27306" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Reaz</givenname>
				<surname>Hoque</surname>
			</person>
		</names>
		<date value="2000-05"/>
		<address type="sharef:placePublished">San Francisco, California</address>
		<identifier type="sharef:isbn">0123555922</identifier>
		<publisher>Morgan Kaufmann Publishers</publisher>
		<title type="sharef:primaryTitle">XML for Real Programmers</title>
		<field type="bibtex:topic">xml[0.8]</field>
	</reference>
	<reference name="pel04" src="bibtex:book" src-info="bibtex:line-27317" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Dwight</givenname>
				<surname>Peltzer</surname>
			</person>
		</names>
		<date value="2004"/>
		<address type="sharef:placePublished">Boston, Massachusetts</address>
		<identifier type="sharef:isbn">0-201-77168-3</identifier>
		<publisher>Addison Wesley</publisher>
		<title type="sharef:primaryTitle">XML: Language Mechanics &amp; Applications</title>
		<field type="bibtex:topic">xml[0.8]</field>
	</reference>
	<reference name="pet96" src="bibtex:book" src-info="bibtex:line-27327" type="sharef:book">
		<names type="sharef: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 type="sharef:placePublished">San Francisco, California</address>
		<identifier type="sharef:isbn">1558603689</identifier>
		<publisher>Morgan Kaufmann Publishers</publisher>
		<title type="sharef:primaryTitle">Computer Networks</title>
	</reference>
	<reference name="pet99" src="bibtex:book" src-info="bibtex:line-27337" type="sharef:book">
		<names type="sharef: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 type="sharef:placePublished">San Francisco, California</address>
		<edition>2nd</edition>
		<identifier type="sharef:isbn">1558605142</identifier>
		<publisher>Morgan Kaufmann Publishers</publisher>
		<title type="sharef:primaryTitle">Computer Networks: A Systems Approach</title>
		<field type="bibtex:updates">pet96</field>
	</reference>
	<reference name="tow99" src="bibtex:book" src-info="bibtex:line-27349" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>George</givenname>
				<surname>Towner</surname>
			</person>
		</names>
		<date value="1999-05"/>
		<address type="sharef:placePublished">San Francisco, California</address>
		<identifier type="sharef:isbn">0120596407</identifier>
		<publisher>Morgan Kaufmann Publishers</publisher>
		<title type="sharef:primaryTitle">Discovering Quicktime for Windows and MacIntosh</title>
	</reference>
	<reference name="pat94" src="bibtex:book" src-info="bibtex:line-27359" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>David A.</givenname>
				<surname>Patterson</surname>
			</person>
			<person>
				<givenname>John L.</givenname>
				<surname>Hennessy</surname>
			</person>
		</names>
		<date value="1994"/>
		<address type="sharef:placePublished">San Francisco, California</address>
		<field type="bibtex:index">MIPS, RISC</field>
		<identifier type="sharef:isbn">1558602828</identifier>
		<publisher>Morgan Kaufmann Publishers</publisher>
		<title type="sharef:primaryTitle">Computer Organization &amp; Design: The Hardware/Software Interface</title>
	</reference>
	<reference name="sch04f" src="bibtex:book" src-info="bibtex:line-27369" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Jochen H.</givenname>
				<surname>Schiller</surname>
			</person>
			<person>
				<givenname>Agnès</givenname>
				<surname>Voisard</surname>
			</person>
		</names>
		<date value="2004"/>
		<abstract>
			<richtext>
				<p>Location-based services (LBS) are a new concept integrating a users geographic location with the general notion of services, such as dialing an emergency number from a cell phone or using a navigation system in a car. Incorporating both mobile communication and spatial data, these applications represent a novel challenge both conceptually and technically. The purpose of this book is to describe, in an accessible fashion, the various concepts underlying mobile location-based services. These range from general application-related ideas to technical aspects. Each chapter starts with a high level of abstraction and drills down to the technical details. Contributors examine each application from all necessary perspectives, namely, requirements, services, data, and scalability. An illustrative example begins early in the book and runs throughout, serving as a reference.</p>
			</richtext>
		</abstract>
		<address type="sharef:placePublished">San Francisco, California</address>
		<identifier type="sharef:isbn">1558609296</identifier>
		<publisher>Morgan Kaufmann Publishers</publisher>
		<title type="sharef:primaryTitle">Location-Based Services</title>
		<identifier type="sharef:uri">http://books.google.com/books?id=wj19b5wVfXAC</identifier>
	</reference>
	<reference name="rag98b" src="bibtex:book" src-info="bibtex:line-27380" type="sharef:book">
		<names type="sharef: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 type="sharef:placePublished">Harlow, England</address>
		<edition>2nd</edition>
		<field type="bibtex:index">HTML</field>
		<identifier type="sharef:isbn">0201178052</identifier>
		<publisher>Addison Wesley</publisher>
		<title type="sharef:primaryTitle">Raggett on HTML 4</title>
	</reference>
	<reference name="car97" src="bibtex:book" src-info="bibtex:line-27392" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Rikk</givenname>
				<surname>Carey</surname>
			</person>
			<person>
				<givenname>Gavin</givenname>
				<surname>Bell</surname>
			</person>
		</names>
		<date value="1997-06"/>
		<address type="sharef:placePublished">Reading, Massachusetts</address>
		<identifier type="sharef:isbn">0201419742</identifier>
		<publisher>Addison Wesley</publisher>
		<title type="sharef:primaryTitle">The Annotated VRML 2.0 Reference Manual</title>
		<field type="bibtex:topic">vrml[1]</field>
	</reference>
	<reference name="lie97" src="bibtex:book" src-info="bibtex:line-27403" type="sharef:book">
		<names type="sharef: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 type="sharef:placePublished">Harlow, England</address>
		<identifier type="sharef:isbn">020141998X</identifier>
		<publisher>Addison Wesley</publisher>
		<title type="sharef:primaryTitle">Cascading Style Sheets</title>
		<field type="bibtex:topic">css1[0.8]</field>
	</reference>
	<reference name="lie99" src="bibtex:book" src-info="bibtex:line-27414" type="sharef:book">
		<names type="sharef: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 type="sharef:placePublished">Harlow, England</address>
		<edition>2nd</edition>
		<identifier type="sharef:isbn">0201596253</identifier>
		<publisher>Addison Wesley</publisher>
		<title type="sharef:primaryTitle">Cascading Style Sheets</title>
		<field type="bibtex:topic">css1[0.8] css2[0.8]</field>
		<field type="bibtex:updates">lie97</field>
	</reference>
	<reference name="cam96" src="bibtex:book" src-info="bibtex:line-27427" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Mary</givenname>
				<surname>Campione</surname>
			</person>
			<person>
				<givenname>Kathy</givenname>
				<surname>Walrath</surname>
			</person>
		</names>
		<date value="1996"/>
		<address type="sharef:placePublished">Reading, Massachusetts</address>
		<field type="bibtex:index">Java</field>
		<identifier type="sharef:isbn">0201634546</identifier>
		<publisher>Addison Wesley</publisher>
		<title type="sharef:primaryTitle">The Java Tutorial</title>
	</reference>
	<reference name="per92" src="bibtex:book" src-info="bibtex:line-27437" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Radia</givenname>
				<surname>Perlman</surname>
			</person>
		</names>
		<date value="1992"/>
		<address type="sharef:placePublished">Reading, Massachusetts</address>
		<field type="bibtex:index">Bridge, Router, LAN, Ethernet, Routing, TCP/IP, OSI</field>
		<identifier type="sharef:isbn">0201563320</identifier>
		<publisher>Addison Wesley</publisher>
		<title type="sharef:primaryTitle">Interconnections: Bridges and Routers</title>
	</reference>
	<reference name="ste94" src="bibtex:book" src-info="bibtex:line-27447" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>W. Richard</givenname>
				<surname>Stevens</surname>
			</person>
		</names>
		<date value="1994"/>
		<address type="sharef:placePublished">Reading, Massachusetts</address>
		<field type="bibtex:index">TCP/IP</field>
		<identifier type="sharef:isbn">0-201-63346-9</identifier>
		<publisher>Addison Wesley</publisher>
		<title type="sharef:primaryTitle">TCP/IP Illustrated</title>
		<volume>1: The Protocols</volume>
	</reference>
	<reference name="ste95b" src="bibtex:book" src-info="bibtex:line-27458" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>W. Richard</givenname>
				<surname>Stevens</surname>
			</person>
		</names>
		<date value="1995-01"/>
		<address type="sharef:placePublished">Reading, Massachusetts</address>
		<field type="bibtex:index">TCP/IP</field>
		<identifier type="sharef:isbn">0-201-63354-X</identifier>
		<publisher>Addison Wesley</publisher>
		<title type="sharef:primaryTitle">TCP/IP Illustrated</title>
		<volume>2: The Implementation</volume>
	</reference>
	<reference name="ste96" src="bibtex:book" src-info="bibtex:line-27470" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>W. Richard</givenname>
				<surname>Stevens</surname>
			</person>
		</names>
		<date value="1996-01"/>
		<address type="sharef:placePublished">Reading, Massachusetts</address>
		<field type="bibtex:index">TCP/IP, TCP for Transactions, HTTP, NNTP</field>
		<identifier type="sharef:isbn">0-20-163495-3</identifier>
		<publisher>Addison Wesley</publisher>
		<title type="sharef:primaryTitle">TCP/IP Illustrated</title>
		<volume>3: TCP for Transactions, HTTP, NNTP, and the Unix Domain Protocols</volume>
	</reference>
	<reference name="com91" src="bibtex:book" src-info="bibtex:line-27482" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Douglas E.</givenname>
				<surname>Comer</surname>
			</person>
		</names>
		<date value="1991"/>
		<address type="sharef:placePublished">Englewood Cliffs, New Jersey</address>
		<edition>2nd</edition>
		<field type="bibtex:index">TCP/IP</field>
		<identifier type="sharef:isbn">0-13-474321-0</identifier>
		<publisher>Prentice-Hall</publisher>
		<title type="sharef:primaryTitle">Internetworking with TCP/IP</title>
		<volume>1: Principles, Protocols and Architecture</volume>
	</reference>
	<reference name="com00" src="bibtex:book" src-info="bibtex:line-27494" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Douglas E.</givenname>
				<surname>Comer</surname>
			</person>
		</names>
		<date value="2000-01"/>
		<address type="sharef:placePublished">Englewood Cliffs, New Jersey</address>
		<edition>4th</edition>
		<field type="bibtex:index">TCP/IP</field>
		<identifier type="sharef:isbn">0-13-018380-6</identifier>
		<publisher>Prentice-Hall</publisher>
		<title type="sharef:primaryTitle">Internetworking with TCP/IP</title>
		<field type="bibtex:updates">com91</field>
		<volume>1: Principles, Protocols and Architecture</volume>
	</reference>
	<reference name="cs91" src="bibtex:book" src-info="bibtex:line-27508" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Douglas E.</givenname>
				<surname>Comer</surname>
			</person>
			<person>
				<givenname>David L.</givenname>
				<surname>Stevens</surname>
			</person>
		</names>
		<date value="1991"/>
		<address type="sharef:placePublished">Englewood Cliffs, New Jersey</address>
		<field type="bibtex:index">TCP/IP</field>
		<identifier type="sharef:isbn">0-13-472242-6</identifier>
		<publisher>Prentice-Hall</publisher>
		<title type="sharef:primaryTitle">Internetworking with TCP/IP</title>
		<volume>2: Design, Implementation and Internals</volume>
	</reference>
	<reference name="cs98" src="bibtex:book" src-info="bibtex:line-27519" type="sharef:book">
		<names type="sharef: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 type="sharef:placePublished">Englewood Cliffs, New Jersey</address>
		<edition>3rd</edition>
		<field type="bibtex:index">TCP/IP</field>
		<identifier type="sharef:isbn">0-13-973843-6</identifier>
		<publisher>Prentice-Hall</publisher>
		<title type="sharef:primaryTitle">Internetworking with TCP/IP</title>
		<field type="bibtex:updates">cs91</field>
		<volume>2: Design, Implementation and Internals</volume>
	</reference>
	<reference name="com97" src="bibtex:book" src-info="bibtex:line-27533" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Douglas E.</givenname>
				<surname>Comer</surname>
			</person>
		</names>
		<date value="1997-08"/>
		<address type="sharef:placePublished">Englewood Cliffs, New Jersey</address>
		<edition>2nd</edition>
		<identifier type="sharef:isbn">0138901619</identifier>
		<publisher>Prentice-Hall</publisher>
		<title type="sharef:primaryTitle">The Internet Book</title>
		<field type="bibtex:topic">internet[0.9]</field>
	</reference>
	<reference name="com00a" src="bibtex:book" src-info="bibtex:line-27545" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Douglas E.</givenname>
				<surname>Comer</surname>
			</person>
		</names>
		<date value="2000-03"/>
		<address type="sharef:placePublished">Englewood Cliffs, New Jersey</address>
		<edition>3rd</edition>
		<identifier type="sharef:isbn">0130308528</identifier>
		<publisher>Prentice-Hall</publisher>
		<title type="sharef:primaryTitle">The Internet Book</title>
		<field type="bibtex:topic">internet[0.9]</field>
		<field type="bibtex:updates">com97</field>
	</reference>
	<reference name="kau95" src="bibtex:book" src-info="bibtex:line-27558" type="sharef:book">
		<names type="sharef: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 type="sharef:placePublished">Englewood Cliffs, New Jersey</address>
		<field type="bibtex:index">security</field>
		<identifier type="sharef:isbn">0-13-061466-1</identifier>
		<publisher>Prentice-Hall</publisher>
		<title type="sharef:primaryTitle">Network Security: Private Communication in a Public World</title>
	</reference>
	<reference name="abr98" src="bibtex:book" src-info="bibtex:line-27569" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Marc</givenname>
				<surname>Abrams</surname>
			</person>
		</names>
		<date value="1998"/>
		<address type="sharef:placePublished">Englewood Cliffs, New Jersey</address>
		<identifier type="sharef:isbn">0-13-954785-1</identifier>
		<publisher>Prentice-Hall</publisher>
		<title type="sharef:primaryTitle">World Wide Web: Beyond the Basics</title>
		<field type="bibtex:topic">www[0.9]</field>
	</reference>
	<reference name="ros90" src="bibtex:book" src-info="bibtex:line-27579" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Marshall T.</givenname>
				<surname>Rose</surname>
			</person>
		</names>
		<date value="1990"/>
		<address type="sharef:placePublished">Englewood Cliffs, New Jersey</address>
		<identifier type="sharef:isbn">0-13-643016-3</identifier>
		<publisher>Prentice-Hall</publisher>
		<title type="sharef:primaryTitle">The Open Book</title>
		<field type="bibtex:topic">osi[0.9]</field>
	</reference>
	<reference name="hal92" src="bibtex:book" src-info="bibtex:line-27589" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Fred</givenname>
				<surname>Halsall</surname>
			</person>
		</names>
		<date value="1992"/>
		<address type="sharef:placePublished">Wokingham, England</address>
		<identifier type="sharef:isbn">0-201-56506-4</identifier>
		<publisher>Addison Wesley</publisher>
		<title type="sharef:primaryTitle">Data Communications, Computer Networks and Open Systems</title>
		<field type="bibtex:topic">osi[0.9]</field>
	</reference>
	<reference name="hal96" src="bibtex:book" src-info="bibtex:line-27599" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Fred</givenname>
				<surname>Halsall</surname>
			</person>
		</names>
		<date value="1996-01"/>
		<address type="sharef:placePublished">Wokingham, England</address>
		<edition>4th</edition>
		<publisher>Addison Wesley</publisher>
		<title type="sharef:primaryTitle">Data Communications, Computer Networks and Open Systems</title>
		<field type="bibtex:updates">hal92</field>
	</reference>
	<reference name="str92a" src="bibtex:book" src-info="bibtex:line-27610" type="sharef:book">
		<names type="sharef: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 type="sharef:placePublished">Reading, Massachusetts</address>
		<field type="bibtex:index">XTP, multicast</field>
		<identifier type="sharef:isbn">0-201-56351-7</identifier>
		<publisher>Addison Wesley</publisher>
		<title type="sharef:primaryTitle">XTP: The Xpress Transfer Protocol</title>
	</reference>
	<reference name="lef89" src="bibtex:book" src-info="bibtex:line-27620" type="sharef:book">
		<names type="sharef: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 type="sharef:placePublished">Reading, Massachusetts</address>
		<field type="bibtex:index">Unix 4.3BSD</field>
		<identifier type="sharef:isbn">0-201-06196-1</identifier>
		<publisher>Addison Wesley</publisher>
		<title type="sharef:primaryTitle">The Design and Implementation of the 4.3BSD Operating System</title>
	</reference>
	<reference name="ber87" src="bibtex:book" src-info="bibtex:line-27630" type="sharef:book">
		<names type="sharef: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 type="sharef:placePublished">Reading, Massachusetts</address>
		<identifier type="sharef:isbn">0-201-10715-5</identifier>
		<publisher>Addison Wesley</publisher>
		<title type="sharef:primaryTitle">Concurrency Control and Recovery in Database Systems</title>
	</reference>
	<reference name="bla91" src="bibtex:book" src-info="bibtex:line-27639" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Uyless</givenname>
				<surname>Black</surname>
			</person>
		</names>
		<date value="1991"/>
		<address type="sharef:placePublished">Englewood Cliffs, New Jersey</address>
		<identifier type="sharef:isbn">0-13-637133-7</identifier>
		<publisher>Prentice-Hall</publisher>
		<title type="sharef:primaryTitle">OSI: A Model for Computer Communication Standards</title>
		<field type="bibtex:topic">osi[0.9]</field>
	</reference>
	<reference name="bac93" src="bibtex:book" src-info="bibtex:line-27649" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Jean</givenname>
				<surname>Bacon</surname>
			</person>
		</names>
		<date value="1992"/>
		<address type="sharef:placePublished">Wokingham, England</address>
		<identifier type="sharef:isbn">0-201-41677-8</identifier>
		<publisher>Addison Wesley</publisher>
		<title type="sharef:primaryTitle">Concurrent Systems</title>
	</reference>
	<reference name="win93a" src="bibtex:book" src-info="bibtex:line-27658" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Jane</givenname>
				<surname>Winsor</surname>
			</person>
		</names>
		<date value="1993"/>
		<address type="sharef:placePublished">Emeryville, California</address>
		<identifier type="sharef:isbn">1-56276-080-7</identifier>
		<publisher>Ziff-Davis Press</publisher>
		<title type="sharef:primaryTitle">Solaris System Administrator's Guide</title>
	</reference>
	<reference name="win93b" src="bibtex:book" src-info="bibtex:line-27667" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Jane</givenname>
				<surname>Winsor</surname>
			</person>
		</names>
		<date value="1993"/>
		<address type="sharef:placePublished">Emeryville, California</address>
		<identifier type="sharef:isbn">1-56276-131-5</identifier>
		<publisher>Ziff-Davis Press</publisher>
		<title type="sharef:primaryTitle">Solaris Advanced System Administrator's Guide</title>
	</reference>
	<reference name="hug98" src="bibtex:book" src-info="bibtex:line-27676" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Lawrence E.</givenname>
				<surname>Hughes</surname>
			</person>
		</names>
		<date value="1998-09"/>
		<address type="sharef:placePublished">Norwood, Massachusetts</address>
		<publisher>Artech House</publisher>
		<title type="sharef:primaryTitle">Internet E-Mail: Protocols, Standards, and Implementation</title>
		<field type="bibtex:topic">smtp[0.8] pop[0.8] imap[0.8] mime[0.7] pgp[0.7]</field>
	</reference>
	<reference name="pur93" src="bibtex:book" src-info="bibtex:line-27686" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Michael</givenname>
				<surname>Purser</surname>
			</person>
		</names>
		<date value="1993"/>
		<address type="sharef:placePublished">Norwood, Massachusetts</address>
		<identifier type="sharef:isbn">0890066922</identifier>
		<publisher>Artech House</publisher>
		<title type="sharef:primaryTitle">Secure Data Networking</title>
	</reference>
	<reference name="str86" src="bibtex:book" src-info="bibtex:line-27695" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Bjarne</givenname>
				<surname>Stroustrup</surname>
			</person>
		</names>
		<date value="1986"/>
		<address type="sharef:placePublished">Reading, Massachusetts</address>
		<identifier type="sharef:isbn">020112078X</identifier>
		<publisher>Addison Wesley</publisher>
		<title type="sharef:primaryTitle">The C++ Programming Language</title>
		<field type="bibtex:topic">cplusplus[1]</field>
	</reference>
	<reference name="str91" src="bibtex:book" src-info="bibtex:line-27705" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Bjarne</givenname>
				<surname>Stroustrup</surname>
			</person>
		</names>
		<date value="1991"/>
		<address type="sharef:placePublished">Reading, Massachusetts</address>
		<edition>2nd</edition>
		<identifier type="sharef:isbn">0201539926</identifier>
		<publisher>Addison Wesley</publisher>
		<title type="sharef:primaryTitle">The C++ Programming Language</title>
		<field type="bibtex:topic">cplusplus[1]</field>
	</reference>
	<reference name="lip89" src="bibtex:book" src-info="bibtex:line-27716" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Stanley B.</givenname>
				<surname>Lippman</surname>
			</person>
		</names>
		<date value="1989"/>
		<address type="sharef:placePublished">Reading, Massachusetts</address>
		<identifier type="sharef:isbn">0201164876</identifier>
		<publisher>Addison Wesley</publisher>
		<title type="sharef:primaryTitle">A C++ Primer</title>
		<field type="bibtex:topic">cplusplus[0.9]</field>
	</reference>
	<reference name="lip91" src="bibtex:book" src-info="bibtex:line-27726" type="sharef:book">
		<names type="sharef:author">
			<person>
				<givenname>Stanley B.</givenname>
				<surname>Lippman</surname>
			</person>
		</names>
		<date value="1991-07"/>
		<address type="sharef:placePublished">Reading, Massachusetts</address>
		<edition>2nd</edition>
		<identifier type="sharef:isbn">0201548488</identifier>
		<publisher>Addison Wesley</publisher>
		<title type="sharef:primaryTitle">A C++ Primer</title>
		<field type="bibtex:topic">cplusplus[0.9]</field>
	</reference>
	<reference name="gam95" src="bibtex:book" src-info="bibtex:line-27738" type="sharef:book">
		<names type="sharef: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 type="sharef:placePublished">Reading, Massachusetts</address>
		<identifier type="sharef:isbn">0201633612</identifier>
		<publisher>Addison Wesley</publisher>
		<title type="sharef:primaryTitle">Design Patterns: Elements of Reusable Object-Oriented Software</title>
	</reference>
	<reference name="abe98" src="bibtex:misc" src-info="bibtex:line-27752" type="bibtex:misc">
		<names type="sharef: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 type="sharef:primaryTitle">The Risks of Key Recovery, Key Escrow, and Trusted Third-Party Encryption</title>
		<identifier type="sharef:uri">http://www.cdt.org/crypto/risks98/</identifier>
	</reference>
	<reference name="ale04" src="bibtex:misc" src-info="bibtex:line-27761" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Kim</givenname>
				<surname>Alexander</surname>
			</person>
			<person>
				<givenname>Keith</givenname>
				<surname>Mills</surname>
			</person>
		</names>
		<date value="2004-05"/>
		<title type="sharef:primaryTitle">Voter Privacy in the Digital Age</title>
		<identifier type="sharef:uri" resourceType="application/pdf">http://www.calvoter.org/issues/votprivacy/pub/0504voterprivacy.pdf</identifier>
	</reference>
	<reference name="mor03b" src="bibtex:misc" src-info="bibtex:line-27769" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>John B.</givenname>
				<surname>Morris</surname>
			</person>
			<person>
				<givenname>Alan</givenname>
				<surname>Davidson</surname>
			</person>
		</names>
		<date value="2003-08"/>
		<title type="sharef:primaryTitle">Policy Impact Assessments: Considering the Public Interest in Internet Standards Development</title>
		<identifier type="sharef:uri" resourceType="application/pdf">http://www.cdt.org/publications/pia.pdf</identifier>
	</reference>
	<reference name="oecd80" src="bibtex:misc" src-info="bibtex:line-27777" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<surname>Organisation for Economic Co-Operation and Development (OECD)</surname>
			</person>
		</names>
		<date value="1980-08"/>
		<title type="sharef:primaryTitle">Guidelines on the Protection of Privacy and Transborder Flows of Personal Data</title>
		<identifier type="sharef:uri" resourceType="text/html">http://www.oecd.org/document/18/0,3343,en_2649_34255_1815186_1_1_1_1,00.html</identifier>
	</reference>
	<reference name="srgb" src="bibtex:misc" src-info="bibtex:line-27785" type="bibtex:misc">
		<names type="sharef: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 type="sharef:primaryTitle">A Standard Default Color Space for the Internet — sRGB</title>
		<field type="bibtex:topic">srgb[1]</field>
	</reference>
	<reference name="spe94" src="bibtex:misc" src-info="bibtex:line-27794" type="bibtex:misc">
		<names type="sharef: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 type="sharef:primaryTitle">Analysis of HTTP Performance problems</title>
	</reference>
	<reference name="oeb99" src="bibtex:misc" src-info="bibtex:line-27807" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<surname>Open eBook Authoring Group</surname>
			</person>
		</names>
		<date value="1999-09"/>
		<title type="sharef:primaryTitle">Open eBook Publication Structure 1.0</title>
		<field type="bibtex:topic">oeb[1]</field>
	</reference>
	<reference name="oeb01" src="bibtex:misc" src-info="bibtex:line-27815" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<surname>Open eBook Forum</surname>
			</person>
		</names>
		<date value="2001-07"/>
		<title type="sharef:primaryTitle">Open eBook Publication Structure 1.0.1</title>
		<field type="bibtex:topic">oeb[1]</field>
		<field type="bibtex:updates">oeb99</field>
		<identifier type="sharef:uri" resourceType="text/html">http://www.openebook.org/oebps/oebps1.0.1/download/index.htm</identifier>
	</reference>
	<reference name="z39" src="bibtex:misc" src-info="bibtex:line-27829" type="bibtex:misc">
		<names type="sharef:author">
			<name>American National Standards Institute</name>
		</names>
		<date value="1995-07"/>
		<howpublished>ANSI/NISO Z39.50-1995</howpublished>
		<title type="sharef:primaryTitle">Information Retrieval (Z39.50): Application Service Definition and Protocol Specification</title>
		<field type="bibtex:topic">z3950[1]</field>
	</reference>
	<reference name="z39.56" src="bibtex:misc" src-info="bibtex:line-27838" type="bibtex:misc">
		<names type="sharef:author">
			<name>American National Standards Institute</name>
		</names>
		<date value="1996"/>
		<howpublished>ANSI/NISO Z39.56-1996</howpublished>
		<title type="sharef:primaryTitle">Serial Item and Contribution Identifier</title>
		<field type="bibtex:topic">sici[1]</field>
	</reference>
	<reference name="z39.84" src="bibtex:misc" src-info="bibtex:line-27846" type="bibtex:misc">
		<names type="sharef:author">
			<name>American National Standards Institute</name>
		</names>
		<date value="2000-05"/>
		<howpublished>ANSI/NISO Z39.84-2000</howpublished>
		<title type="sharef:primaryTitle">Syntax for the Digital Object Identifier</title>
		<field type="bibtex:topic">doi[1]</field>
		<identifier type="sharef:uri" resourceType="application/pdf">http://www.niso.org/standards/resources/Z39-84-2000.pdf</identifier>
	</reference>
	<reference name="z39.88" src="bibtex:misc" src-info="bibtex:line-27856" type="bibtex:misc">
		<names type="sharef: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="sharef:isbn">1-880124-61-0</identifier>
		<title type="sharef:primaryTitle">The OpenURL Framework for Context-Sensitive Services</title>
		<field type="bibtex:topic">openurl[1]</field>
		<identifier type="sharef:uri">http://www.niso.org/standards/standard_detail.cfm?std_id=783</identifier>
	</reference>
	<reference name="ascii" src="bibtex:misc" src-info="bibtex:line-27868" type="bibtex:misc">
		<names type="sharef:author">
			<name>American National Standards Institute</name>
		</names>
		<date value="1992"/>
		<howpublished>ANSI X3.4</howpublished>
		<title type="sharef:primaryTitle">Coded Character Set — 7-Bit American National Standard Code for Information Interchange</title>
		<field type="bibtex:topic">ascii[1]</field>
	</reference>
	<reference name="lzs" src="bibtex:misc" src-info="bibtex:line-27876" type="bibtex:misc">
		<names type="sharef:author">
			<name>American National Standards Institute</name>
		</names>
		<date value="1994-08"/>
		<howpublished>ANSI X3.241</howpublished>
		<title type="sharef:primaryTitle">Data Compression Method — Adaptive Coding with Sliding Window for Information Interchange</title>
		<field type="bibtex:topic">lzs[1]</field>
	</reference>
	<reference name="ieee754" src="bibtex:misc" src-info="bibtex:line-27889" type="bibtex:misc">
		<names type="sharef:author">
			<name>Institute of Electrical and Electronics Engineers</name>
		</names>
		<date value="1985"/>
		<howpublished>IEEE Std 754-1985</howpublished>
		<title type="sharef:primaryTitle">IEEE Standard for Binary Floating-Point Arithmetic</title>
	</reference>
	<reference name="ieee80216e" src="bibtex:misc" src-info="bibtex:line-27896" type="bibtex:misc">
		<names type="sharef:author">
			<name>Institute of Electrical and Electronics Engineers</name>
		</names>
		<date value="2006-02"/>
		<howpublished>IEEE Std 802.16e-2005</howpublished>
		<title type="sharef:primaryTitle">IEEE Standard for Local and Metropolitan Area Networks — Part 16: Air Interface for Fixed and Mobile Broadband Wireless Access Systems</title>
		<field type="bibtex:topic">wimax[1]</field>
		<identifier type="sharef:uri" resourceType="application/pdf">http://standards.ieee.org/getieee802/download/802.16e-2005.pdf</identifier>
	</reference>
	<reference name="midi10" src="bibtex:misc" src-info="bibtex:line-27910" type="bibtex:misc">
		<names type="sharef:author">
			<name>MIDI Manufacturers Association</name>
		</names>
		<date value="1996-03"/>
		<title type="sharef:primaryTitle">Complete MIDI 1.0 Detailed Specification</title>
	</reference>
	<reference name="ombm0910" src="bibtex:misc" src-info="bibtex:line-27921" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Peter R.</givenname>
				<surname>Orszag</surname>
			</person>
		</names>
		<date value="2009-02-08"/>
		<address type="sharef:placePublished">Washington, D.C.</address>
		<howpublished>Office of Management and Budget Memorandum M-09-10</howpublished>
		<title type="sharef:primaryTitle">Initial Implementing Guidance for the American Recovery and Reinvestment Act of 2009</title>
		<identifier type="sharef:uri">http://www.whitehouse.gov/omb/asset.aspx?AssetId=703</identifier>
	</reference>
	<reference name="ombm0915" src="bibtex:misc" src-info="bibtex:line-27932" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Peter R.</givenname>
				<surname>Orszag</surname>
			</person>
		</names>
		<date value="2009-04-03"/>
		<address type="sharef:placePublished">Washington, D.C.</address>
		<howpublished>Office of Management and Budget Memorandum M-09-15</howpublished>
		<title type="sharef:primaryTitle">Updated Implementing Guidance for the American Recovery and Reinvestment Act of 2009</title>
		<field type="bibtex:updates">ombm0910</field>
		<identifier type="sharef:uri">http://www.recovery.gov/?q=node/317</identifier>
		<identifier type="sharef:uri">http://www.whitehouse.gov/omb/asset.aspx?AssetId=1067</identifier>
	</reference>
	<reference name="ombm0921" src="bibtex:misc" src-info="bibtex:line-27945" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Peter R.</givenname>
				<surname>Orszag</surname>
			</person>
		</names>
		<date value="2009-06-02"/>
		<address type="sharef:placePublished">Washington, D.C.</address>
		<howpublished>Office of Management and Budget Memorandum M-09-21</howpublished>
		<title type="sharef:primaryTitle">Implementing Guidance for the Reports on Use of Funds Pursuant to the American Recovery and Reinvestment Act of 2009</title>
		<field type="bibtex:updates">ombm0915</field>
		<identifier type="sharef:uri">http://www.whitehouse.gov/omb/asset.aspx?AssetId=1412</identifier>
	</reference>
	<reference name="ombm0919" src="bibtex:misc" src-info="bibtex:line-27957" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Vivek</givenname>
				<surname>Kundra</surname>
			</person>
		</names>
		<date value="2009-06-01"/>
		<address type="sharef:placePublished">Washington, D.C.</address>
		<howpublished>Office of Management and Budget Memorandum M-09-19</howpublished>
		<title type="sharef:primaryTitle">Guidance on Data Submission under the Federal Funding Accountability and Transparency Act (FFATA)</title>
		<field type="bibtex:updates">ombm0812</field>
		<identifier type="sharef:uri" resourceType="application/pdf">http://www.whitehouse.gov/omb/assets/memoranda_fy2009/m09-19.pdf</identifier>
	</reference>
	<reference name="zie10" src="bibtex:misc" src-info="bibtex:line-27969" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Jeffrey D.</givenname>
				<surname>Zients</surname>
			</person>
		</names>
		<date value="2010-04-06"/>
		<address type="sharef:placePublished">Washington, D.C.</address>
		<howpublished>Office of Management and Budget Memorandum</howpublished>
		<title type="sharef:primaryTitle">Memorandum for Senior Accountable Officials Over the Quality of Federal Spending Information</title>
		<identifier type="sharef:uri" resourceType="application/pdf">http://www.whitehouse.gov/omb/assets/open_gov/OpenGovernmentDirective_04062010.pdf</identifier>
	</reference>
	<reference name="des" src="bibtex:misc" src-info="bibtex:line-27984" type="bibtex:misc">
		<names type="sharef:author">
			<name>National Institute of Standards and Technology</name>
		</names>
		<date value="1993-12"/>
		<howpublished>FIPS Publication 46-2</howpublished>
		<title type="sharef:primaryTitle">Data Encryption Standard</title>
		<field type="bibtex:topic">des[1] dea[1]</field>
	</reference>
	<reference name="fips463" src="bibtex:misc" src-info="bibtex:line-27993" type="bibtex:misc">
		<names type="sharef:author">
			<name>National Institute of Standards and Technology</name>
		</names>
		<date value="1999-10"/>
		<howpublished>FIPS Publication 46-3</howpublished>
		<title type="sharef:primaryTitle">Data Encryption Standard (DES)</title>
		<field type="bibtex:topic">des[1] dea[1] tripledes[1] tdea[1]</field>
		<field type="bibtex:updates">des</field>
		<identifier type="sharef:uri">http://csrc.nist.gov/publications/fips/fips46-3/</identifier>
	</reference>
	<reference name="sha1" src="bibtex:misc" src-info="bibtex:line-28004" type="bibtex:misc">
		<names type="sharef:author">
			<name>National Institute of Standards and Technology</name>
		</names>
		<date value="1993-05"/>
		<howpublished>FIPS Publication 180</howpublished>
		<title type="sharef:primaryTitle">Secure Hash Standard (SHS)</title>
		<field type="bibtex:topic">shs[1] sha0[1]</field>
	</reference>
	<reference name="sha2" src="bibtex:misc" src-info="bibtex:line-28013" type="bibtex:misc">
		<names type="sharef:author">
			<name>National Institute of Standards and Technology</name>
		</names>
		<date value="1994-05"/>
		<title type="sharef:primaryTitle">Announcement of Weakness in the Secure Hash Standard</title>
		<field type="bibtex:topic">shs[1] sha0[1]</field>
	</reference>
	<reference name="dss" src="bibtex:misc" src-info="bibtex:line-28021" type="bibtex:misc">
		<names type="sharef:author">
			<name>National Institute of Standards and Technology</name>
		</names>
		<date value="1994-05"/>
		<howpublished>FIPS Publication 186</howpublished>
		<title type="sharef:primaryTitle">Digital Signature Standard (DSS)</title>
		<field type="bibtex:topic">dss[1] dsa[1]</field>
	</reference>
	<reference name="iec61966-2" src="bibtex:misc" src-info="bibtex:line-28034" type="bibtex:misc">
		<names type="sharef:author">
			<name>International Electrotechnical Commission</name>
		</names>
		<date value="1998-08"/>
		<howpublished>IEC 61966-2</howpublished>
		<title type="sharef:primaryTitle">Colour measurement and management in multimedia systems and equipment — Part 2: Colour Management in Multimedia Systems</title>
		<field type="bibtex:topic">srgb[1]</field>
	</reference>
	<reference name="dcmiam" src="bibtex:misc" src-info="bibtex:line-28047" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Andy</givenname>
				<surname>Powell</surname>
			</person>
			<person>
				<givenname>Mikael</givenname>
				<surname>Nilsson</surname>
			</person>
			<person>
				<givenname>Ambjörn</givenname>
				<surname>Naeve</surname>
			</person>
			<person>
				<givenname>Pete</givenname>
				<surname>Johnston</surname>
			</person>
			<person>
				<givenname>Thomas</givenname>
				<surname>Baker</surname>
			</person>
		</names>
		<date value="2007-06"/>
		<abstract>
			<richtext>
				<p>This document specifies an abstract model for Dublin Core metadata. The primary purpose of this document is to specify the components and constructs used in Dublin Core metadata. It defines the nature of the components used and describes how those components are combined to create information structures. It provides an information model which is independent of any particular encoding syntax. Such an information model allows us to gain a better understanding of the kinds of descriptions that we are encoding and facilitates the development of better mappings and cross-syntax translations. This document is primarily aimed at the developers of software applications that support Dublin Core metadata, people involved in developing new syntax encoding guidelines for Dublin Core metadata and people developing metadata application profiles based on DCMI vocabularies or on other compatible vocabularies. The DCMI Abstract Model builds on work undertaken by the World Wide Web Consortium (W3C) on the Resource Description Framework (RDF). The use of concepts from RDF is summarized below in Section 5. The DCMI Abstract Model is represented here using UML class diagrams. Readers that are not familiar with UML class diagrams should note that lines ending in a block-arrow should be read as 'is' or 'is a' (for example, "a value is a resource") and that lines starting with a block-diamond should be read as 'contains a' or 'has a' (for example, "a statement contains a property URI"). Other relationships are labeled appropriately. In this document, words and phrases in italics are defined in Section 7, Terminology.</p>
			</richtext>
		</abstract>
		<howpublished>DCMI Recommendation</howpublished>
		<title type="sharef:primaryTitle">DCMI Abstract Model</title>
		<field type="bibtex:topic">dcmi[1]</field>
		<identifier type="sharef:uri">http://dublincore.org/documents/2007/06/04/abstract-model/</identifier>
	</reference>
	<reference name="kml22" src="bibtex:misc" src-info="bibtex:line-28062" type="bibtex:misc">
		<names type="sharef:author">
			<name>Open Geospatial Consortium</name>
		</names>
		<names type="sharef:editor">
			<person>
				<givenname>Tim</givenname>
				<surname>Wilson</surname>
			</person>
		</names>
		<date value="2008-04"/>
		<howpublished>OGC 07-147r2, Version 2.2.0</howpublished>
		<title type="sharef:primaryTitle">OGC KML</title>
		<field type="bibtex:topic">kml[1]</field>
	</reference>
	<reference name="olscore11" src="bibtex:misc" src-info="bibtex:line-28072" type="bibtex:misc">
		<names type="sharef:author">
			<name>Open Geospatial Consortium</name>
		</names>
		<names type="sharef:editor">
			<person>
				<givenname>Marwa</givenname>
				<surname>Mabrouk</surname>
			</person>
		</names>
		<date value="2005-05"/>
		<howpublished>OGC 05-016, Version 1.1</howpublished>
		<title type="sharef:primaryTitle">OpenGIS Location Services (OpenLS): Core Services</title>
		<field type="bibtex:topic">openls[1]</field>
	</reference>
	<reference name="wps100" src="bibtex:misc" src-info="bibtex:line-28082" type="bibtex:misc">
		<names type="sharef:author">
			<name>Open Geospatial Consortium</name>
		</names>
		<names type="sharef:editor">
			<person>
				<givenname>Peter</givenname>
				<surname>Schut</surname>
			</person>
		</names>
		<date value="2007-06"/>
		<howpublished>OGC 05-007r7, Version 1.0.0</howpublished>
		<title type="sharef:primaryTitle">OpenGIS Web Processing Service</title>
		<field type="bibtex:topic">wps[1] opengis[0.9]</field>
		<identifier type="sharef:uri">http://portal.opengeospatial.org/files/?artifact_id=24151</identifier>
	</reference>
	<reference name="wms130" src="bibtex:misc" src-info="bibtex:line-28093" type="bibtex:misc">
		<names type="sharef:author">
			<name>Open Geospatial Consortium</name>
		</names>
		<names type="sharef:editor">
			<person>
				<givenname>Jeff</givenname>
				<surname link="de la">Beaujardiere</surname>
			</person>
		</names>
		<date value="2004-01"/>
		<howpublished>OGC 03-109r1, Version 1.3.0</howpublished>
		<title type="sharef:primaryTitle">OGC Web Map Service Interface</title>
		<field type="bibtex:topic">wms[1] opengis[0.9]</field>
		<identifier type="sharef:uri">http://portal.opengeospatial.org/files/?artifact_id=4756</identifier>
	</reference>
	<reference name="sfa120" src="bibtex:misc" src-info="bibtex:line-28104" type="bibtex:misc">
		<names type="sharef:author">
			<name>Open Geospatial Consortium</name>
		</names>
		<names type="sharef:editor">
			<person>
				<givenname>John R.</givenname>
				<surname>Herring</surname>
			</person>
		</names>
		<date value="2006-10"/>
		<howpublished>OGC 06-103r3, Version 1.2.0</howpublished>
		<title type="sharef:primaryTitle">OGC Simple Feature Access</title>
		<field type="bibtex:topic">sfa[1] opengis[0.9]</field>
		<identifier type="sharef:uri">http://portal.opengeospatial.org/files/?artifact_id=18241</identifier>
	</reference>
	<reference name="wmsis130" src="bibtex:misc" src-info="bibtex:line-28115" type="bibtex:misc">
		<names type="sharef:author">
			<name>Open Geospatial Consortium</name>
		</names>
		<names type="sharef:editor">
			<person>
				<givenname>Jeff</givenname>
				<surname link="de la">Beaujardiere</surname>
			</person>
		</names>
		<date value="2006-03"/>
		<howpublished>OGC 06-042, Version 1.3.0</howpublished>
		<title type="sharef:primaryTitle">OpenGIS Web Map Server Implementation Specification</title>
		<field type="bibtex:topic">wms[1] opengis[0.9]</field>
	</reference>
	<reference name="ogccommon110" src="bibtex:misc" src-info="bibtex:line-28125" type="bibtex:misc">
		<names type="sharef:author">
			<name>Open Geospatial Consortium</name>
		</names>
		<names type="sharef:editor">
			<person>
				<givenname>Arliss</givenname>
				<surname>Whiteside</surname>
			</person>
		</names>
		<date value="2007-02"/>
		<howpublished>OGC 06-121r3, Version: 1.1.0</howpublished>
		<title type="sharef:primaryTitle">OGC Web Services Common Specification</title>
		<field type="bibtex:topic">opengis[0.9]</field>
	</reference>
	<reference name="wcs112" src="bibtex:misc" src-info="bibtex:line-28135" type="bibtex:misc">
		<names type="sharef:author">
			<name>Open Geospatial Consortium</name>
		</names>
		<names type="sharef:editor">
			<person>
				<givenname>Arliss</givenname>
				<surname>Whiteside</surname>
			</person>
			<person>
				<givenname>John D.</givenname>
				<surname>Evans</surname>
			</person>
		</names>
		<date value="2008-03"/>
		<howpublished>OGC 07-067r5, Version: 1.1.2</howpublished>
		<title type="sharef:primaryTitle">Web Coverage Service (WCS) Implementation Standard</title>
		<field type="bibtex:topic">wcs[1] opengis[0.9]</field>
	</reference>
	<reference name="wfs110" src="bibtex:misc" src-info="bibtex:line-28145" type="bibtex:misc">
		<names type="sharef:author">
			<name>Open Geospatial Consortium</name>
		</names>
		<names type="sharef:editor">
			<person>
				<givenname>Panagiotis A.</givenname>
				<surname>Vretanos</surname>
			</person>
		</names>
		<date value="2005-05"/>
		<howpublished>OGC 04-094, Version 1.1.0</howpublished>
		<title type="sharef:primaryTitle">Web Feature Service Implementation Specification</title>
		<field type="bibtex:topic">wfs[1] opengis[0.9]</field>
		<identifier type="sharef:uri">http://portal.opengeospatial.org/files/?artifact_id=8339</identifier>
	</reference>
	<reference name="gml31" src="bibtex:misc" src-info="bibtex:line-28156" type="bibtex:misc">
		<names type="sharef:author">
			<name>Open Geospatial Consortium</name>
		</names>
		<names type="sharef:editor">
			<person>
				<givenname>Simon</givenname>
				<surname>Cox</surname>
			</person>
			<person>
				<givenname>Paul</givenname>
				<surname>Daisey</surname>
			</person>
			<person>
				<givenname>Ron</givenname>
				<surname>Lake</surname>
			</person>
			<person>
				<givenname>Clemens</givenname>
				<surname>Portele</surname>
			</person>
			<person>
				<givenname>Arliss</givenname>
				<surname>Whiteside</surname>
			</person>
		</names>
		<date value="2004-02"/>
		<howpublished>OGC 03-105r1, Version 3.1.1</howpublished>
		<title type="sharef:primaryTitle">OpenGIS Geography Markup Language (GML) Encoding Specification</title>
		<field type="bibtex:topic">gml[1] opengis[0.9]</field>
		<identifier type="sharef:uri">http://portal.opengeospatial.org/files/?artifact_id=4700</identifier>
	</reference>
	<reference name="gml32" src="bibtex:misc" src-info="bibtex:line-28167" type="bibtex:misc">
		<names type="sharef:author">
			<name>Open Geospatial Consortium</name>
		</names>
		<names type="sharef:editor">
			<person>
				<givenname>Clemens</givenname>
				<surname>Portele</surname>
			</person>
		</names>
		<date value="2007-08"/>
		<howpublished>OGC 07-036, Version 3.2.1</howpublished>
		<title type="sharef:primaryTitle">OpenGIS Geography Markup Language (GML) Encoding Specification</title>
		<field type="bibtex:topic">gml[1] opengis[0.9]</field>
		<identifier type="sharef:uri">http://portal.opengeospatial.org/files/?artifact_id=20509</identifier>
	</reference>
	<reference name="georss" src="bibtex:misc" src-info="bibtex:line-28178" type="bibtex:misc">
		<names type="sharef:author">
			<name>Open Geospatial Consortium</name>
		</names>
		<names type="sharef:editor">
			<person>
				<givenname>Carl</givenname>
				<surname>Reed</surname>
			</person>
		</names>
		<date value="2006-07"/>
		<abstract>
			<richtext>
				<p>This document describes GeoRSS: Geographically Encoded Objects for RSS feeds. GeoRSS is simple proposal for geo-enabling, or tagging, "really simple syndication" (RSS) feeds with location information. GeoRSS proposes a standardized way in which location is encoded with enough simplicity and descriptive power to satisfy most needs to describe the location of Web content. GeoRSS may not work for every use, but it should serve as an easy-to-use geotagging encoding that is brief and simple with useful defaults but extensible and upwardly-compatible with more sophisticated encoding standards such as the OGC (Open Geospatial Consortium) GML (Geography Markup Language). Currently, there are two GeoRSS serializations: GeoRSS GML and GeoRSS Simple. GeoRSS GML is a formal GML Profile, and supports a greater range of features than GeoRSS Simple, notably coordinate reference systems other than WGS84 latitude/longitude. GeoRSS is designed for use with Atom 1.0, RSS 2.0 and RSS 1.0, although it can be used just as easily in non-RSS XML encodings. GeoRSS Simple has greater brevity, but also has limited extensibility.</p>
			</richtext>
		</abstract>
		<howpublished>OGC 06-050r3</howpublished>
		<title type="sharef:primaryTitle">An Introduction to GeoRSS: A Standards Based Approach for Geo-enabling RSS feeds</title>
		<field type="bibtex:topic">georss[0.9]</field>
		<identifier type="sharef:uri">http://www.opengeospatial.org/pt/06-050r3</identifier>
	</reference>
	<reference name="wgs84" src="bibtex:misc" src-info="bibtex:line-28194" type="bibtex:misc">
		<names type="sharef:author">
			<name>National Imagery and Mapping Agency</name>
		</names>
		<date value="2000-01"/>
		<howpublished>NIMA TR8350.2, Third Edition</howpublished>
		<title type="sharef:primaryTitle">Department of Defense World Geodetic System 1984</title>
		<field type="bibtex:topic">wgs84[1]</field>
		<identifier type="sharef:uri" resourceType="application/pdf">http://earth-info.nga.mil/GandG/publications/tr8350.2/wgs84fin.pdf</identifier>
	</reference>
	<reference name="egm96" src="bibtex:misc" src-info="bibtex:line-28204" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>F. G.</givenname>
				<surname>Lemoine</surname>
			</person>
			<person>
				<givenname>S. C.</givenname>
				<surname>Kenyon</surname>
			</person>
			<person>
				<givenname>J. K.</givenname>
				<surname>Factor</surname>
			</person>
			<person>
				<givenname>R.G.</givenname>
				<surname>Trimmer</surname>
			</person>
			<person>
				<givenname>N. K.</givenname>
				<surname>Pavlis</surname>
			</person>
			<person>
				<givenname>D. S.</givenname>
				<surname>Chinn</surname>
			</person>
			<person>
				<givenname>C. M.</givenname>
				<surname>Cox</surname>
			</person>
			<person>
				<givenname>S. M.</givenname>
				<surname>Klosko</surname>
			</person>
			<person>
				<givenname>S. B.</givenname>
				<surname>Luthcke</surname>
			</person>
			<person>
				<givenname>M. H.</givenname>
				<surname>Torrence</surname>
			</person>
			<person>
				<givenname>Y. M.</givenname>
				<surname>Wang</surname>
			</person>
			<person>
				<givenname>R. G.</givenname>
				<surname>Williamson</surname>
			</person>
			<person>
				<givenname>E. C.</givenname>
				<surname>Pavlis</surname>
			</person>
			<person>
				<givenname>R. H.</givenname>
				<surname>Rapp</surname>
			</person>
			<person>
				<givenname>T. R.</givenname>
				<surname>Olson</surname>
			</person>
		</names>
		<date value="1998-07"/>
		<abstract>
			<richtext>
				<p>The NASA Goddard Space Flight Center (GSFC), the National Imagery and Mapping Agency (NIMA), and the Ohio State University (OSU) have collaborated to develop an improved spherical harmonic model of the Earth's gravitational potential to degree 360. The new model, Earth Gravitational Model 1996 (EGM96) incorporates improved surface gravity data, altimeter-derived anomalies from ERS-1 and from the GEOSAT Geodetic Mission (GM), extensive satellite tracking data — including new data from Satellite laser ranging (SLR), the Global Positioning System (GPS), NASA's Tracking and Data Relay Satellite System (TDRSS), the French DORIS system, and the US Navy TRANET Doppler tracking system — as well as direct altimeter ranges from TOPEX/POSEIDON (T/P), ERS-1, and GEOSAT. The final solution blends a low-degree combiantion model to degree 70, a block-diagonal solution from degree 71 to 359, and a quadrature solution at degree 360. The model was used to compute geoid undulations accurate to better than one meter (with the exception of areas void of dense and accurate surface gravity data) and realize WGS84 as a true three-dimensional reference system. Additional results from the EGM96 solution include models of the dynamic ocean topography to degree 20 from T/P and ERS-1 together, and GEOSAT separately, and improved orbit determination for Earth-orbiting satellites.</p>
			</richtext>
		</abstract>
		<howpublished>NASA/TP-1998-206861</howpublished>
		<title type="sharef:primaryTitle">The Development of the Joint NASA GSFC and the NIMA Geopotential Model EGM96</title>
		<field type="bibtex:topic">egm96[1]</field>
		<identifier type="sharef:uri">http://cddis.nasa.gov/926/egm96/</identifier>
	</reference>
	<reference name="iso639" src="bibtex:misc" src-info="bibtex:line-28219" type="bibtex:misc">
		<names type="sharef:author">
			<name>International Organization for Standardization</name>
		</names>
		<date value="2002-07"/>
		<howpublished>ISO 639</howpublished>
		<title type="sharef:primaryTitle">Codes for the Representation of Names of Languages</title>
		<identifier type="sharef:uri">http://www.iso.ch/iso/en/CatalogueDetailPage.CatalogueDetail?CSNUMBER=22109</identifier>
	</reference>
	<reference name="iso639-1" src="bibtex:misc" src-info="bibtex:line-28228" type="bibtex:misc">
		<names type="sharef: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-1:2002</howpublished>
		<title type="sharef:primaryTitle">Codes for the Representation of Names of Languages — Part 1: Alpha-2 code</title>
		<identifier type="sharef:uri">http://www.iso.ch/iso/en/CatalogueDetailPage.CatalogueDetail?CSNUMBER=22109</identifier>
	</reference>
	<reference name="iso639-2" src="bibtex:misc" src-info="bibtex:line-28238" type="bibtex:misc">
		<names type="sharef:author">
			<name>International Organization for Standardization</name>
		</names>
		<date value="2003-07"/>
		<howpublished>ISO 639-2:1998</howpublished>
		<title type="sharef:primaryTitle">Codes for the Representation of Names of Languages — Part 2: Alpha-3 code</title>
		<identifier type="sharef:uri">http://www.iso.ch/iso/en/CatalogueDetailPage.CatalogueDetail?CSNUMBER=4767</identifier>
	</reference>
	<reference name="iso646" src="bibtex:misc" src-info="bibtex:line-28247" type="bibtex:misc">
		<names type="sharef: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 type="sharef:primaryTitle">Information Technology — ISO 7-bit Coded Character Set for Information Interchange</title>
		<field type="bibtex:topic">ascii[0.9]</field>
	</reference>
	<reference name="iso690" src="bibtex:misc" src-info="bibtex:line-28256" type="bibtex:misc">
		<names type="sharef: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 type="sharef:primaryTitle">Documentation — Bibliographic References — Content, Form and Structure</title>
		<identifier type="sharef:uri">http://www.iso.org/iso/en/CatalogueDetailPage.CatalogueDetail?CSNUMBER=4888</identifier>
	</reference>
	<reference name="iso690-2" src="bibtex:misc" src-info="bibtex:line-28266" type="bibtex:misc">
		<names type="sharef:author">
			<name>International Organization for Standardization</name>
		</names>
		<date value="2004-06"/>
		<howpublished>ISO 690-2:1997</howpublished>
		<title type="sharef:primaryTitle">Documentation — Bibliographic References — Part 2: Electronic Documents or Parts thereof</title>
		<identifier type="sharef:uri">http://www.iso.org/iso/en/CatalogueDetailPage.CatalogueDetail?CSNUMBER=25921</identifier>
	</reference>
	<reference name="iso2108" src="bibtex:misc" src-info="bibtex:line-28275" type="bibtex:misc">
		<names type="sharef: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 type="sharef:primaryTitle">Information and Documentation — International Standard Book Numbering (ISBN)</title>
		<field type="bibtex:topic">isbn[1]</field>
		<identifier type="sharef:uri">http://www.iso.ch/iso/en/CatalogueDetailPage.CatalogueDetail?CSNUMBER=6898</identifier>
	</reference>
	<reference name="iso2709" src="bibtex:misc" src-info="bibtex:line-28285" type="bibtex:misc">
		<names type="sharef: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 type="sharef:primaryTitle">Information and Documentation — Format for Information Exchange</title>
		<identifier type="sharef:uri">http://www.iso.org/iso/en/CatalogueDetailPage.CatalogueDetail?CSNUMBER=7675</identifier>
	</reference>
	<reference name="iso2788" src="bibtex:misc" src-info="bibtex:line-28294" type="bibtex:misc">
		<names type="sharef:author">
			<name>International Organization for Standardization</name>
		</names>
		<date value="1986"/>
		<howpublished>ISO 2788</howpublished>
		<title type="sharef:primaryTitle">Documentation — Guidelines for the Establishment and Development of Monolingual Thesauri</title>
		<field type="bibtex:topic">thesaurus[1]</field>
	</reference>
	<reference name="iso3297" src="bibtex:misc" src-info="bibtex:line-28302" type="bibtex:misc">
		<names type="sharef:author">
			<name>International Organization for Standardization</name>
		</names>
		<date value="1998"/>
		<howpublished>ISO 3297</howpublished>
		<title type="sharef:primaryTitle">Information and Documentation — International Standard Serial Number (ISSN)</title>
		<field type="bibtex:topic">issn[1]</field>
		<identifier type="sharef:uri">http://www.iso.org/iso/en/CatalogueDetailPage.CatalogueDetail?CSNUMBER=23400</identifier>
	</reference>
	<reference name="iso3309" src="bibtex:misc" src-info="bibtex:line-28311" type="bibtex:misc">
		<names type="sharef:author">
			<name>International Organization for Standardization</name>
		</names>
		<date value="1993"/>
		<howpublished>ISO/IEC 3309</howpublished>
		<title type="sharef:primaryTitle">Information Technology — Telecommunications and information exchange between systems — High-level data link control (HDLC) procedures — Frame structure</title>
		<field type="bibtex:topic">crc[0.8]</field>
	</reference>
	<reference name="iso3166" src="bibtex:misc" src-info="bibtex:line-28319" type="bibtex:misc">
		<names type="sharef:author">
			<name>International Organization for Standardization</name>
		</names>
		<date value="2001-11"/>
		<howpublished>ISO 3166</howpublished>
		<title type="sharef:primaryTitle">Codes for the Representation of Names of Countries and their Subdivisions</title>
		<identifier type="sharef:uri">http://www.iso.ch/iso/en/CatalogueDetailPage.CatalogueDetail?CSNUMBER=24591</identifier>
	</reference>
	<reference name="iso4217" src="bibtex:misc" src-info="bibtex:line-28328" type="bibtex:misc">
		<names type="sharef:author">
			<name>International Organization for Standardization</name>
		</names>
		<date value="2001-08"/>
		<howpublished>ISO 4217</howpublished>
		<title type="sharef:primaryTitle">Codes for the Representation of Currencies and Funds</title>
		<identifier type="sharef:uri">http://www.iso.ch/iso/en/CatalogueDetailPage.CatalogueDetail?CSNUMBER=34749</identifier>
	</reference>
	<reference name="iso5964" src="bibtex:misc" src-info="bibtex:line-28337" type="bibtex:misc">
		<names type="sharef:author">
			<name>International Organization for Standardization</name>
		</names>
		<date value="1985"/>
		<howpublished>ISO 5964</howpublished>
		<title type="sharef:primaryTitle">Documentation — Guidelines for the Establishment and Development of Multilingual Thesauri</title>
		<field type="bibtex:topic">thesaurus[1]</field>
	</reference>
	<reference name="iso7498" src="bibtex:misc" src-info="bibtex:line-28345" type="bibtex:misc">
		<names type="sharef: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 type="sharef:primaryTitle">Information Processing Systems — Open Systems Interconnection (OSI) — Basic Reference Model</title>
	</reference>
	<reference name="iso8072" src="bibtex:misc" src-info="bibtex:line-28353" type="bibtex:misc">
		<names type="sharef:author">
			<name>International Organization for Standardization</name>
		</names>
		<date value="1996"/>
		<howpublished>ISO/IEC 8072</howpublished>
		<field type="bibtex:index">OSI, TSAP</field>
		<title type="sharef:primaryTitle">Information Technology — Open Systems Interconnection (OSI) — Transport Service Definition</title>
	</reference>
	<reference name="iso8601" src="bibtex:misc" src-info="bibtex:line-28361" type="bibtex:misc">
		<names type="sharef:author">
			<name>International Organization for Standardization</name>
		</names>
		<date value="2004-12"/>
		<howpublished>ISO 8601</howpublished>
		<title type="sharef:primaryTitle">Data Elements and Interchange Formats — Information Interchange — Representation of Dates and Times</title>
		<identifier type="sharef:uri">http://www.iso.org/iso/en/CatalogueDetailPage.CatalogueDetail?CSNUMBER=40874</identifier>
	</reference>
	<reference name="iso8632" src="bibtex:misc" src-info="bibtex:line-28370" type="bibtex:misc">
		<names type="sharef:author">
			<name>International Organization for Standardization</name>
		</names>
		<date value="1992"/>
		<howpublished>ISO/IEC 8632</howpublished>
		<field type="bibtex:index">CGM</field>
		<title type="sharef:primaryTitle">Information Technology — Computer graphics — Metafile for the Storage and Transfer of Picture Description Information</title>
	</reference>
	<reference name="iso8802-1" src="bibtex:misc" src-info="bibtex:line-28378" type="bibtex:misc">
		<names type="sharef:author">
			<name>International Organization for Standardization</name>
		</names>
		<date value="1994"/>
		<howpublished>ISO/IEC TR 8802-1</howpublished>
		<title type="sharef:primaryTitle">Information Technology — Telecommunications and information exchange between systems — Specific requirements — Part 1: Overview of Local Area Network Standards</title>
		<field type="bibtex:topic">ieee802[1]</field>
	</reference>
	<reference name="iso8802-2" src="bibtex:misc" src-info="bibtex:line-28386" type="bibtex:misc">
		<names type="sharef:author">
			<name>International Organization for Standardization</name>
		</names>
		<date value="1998"/>
		<howpublished>ISO/IEC 8802-2</howpublished>
		<title type="sharef:primaryTitle">Information Technology — Telecommunications and information exchange between systems — Specific requirements — Part 2: Logical link control</title>
		<field type="bibtex:topic">ieee8022[1] llc[0.9]</field>
	</reference>
	<reference name="iso8802-3" src="bibtex:misc" src-info="bibtex:line-28394" type="bibtex:misc">
		<names type="sharef:author">
			<name>International Organization for Standardization</name>
		</names>
		<date value="1996"/>
		<howpublished>ISO/IEC 8802-3</howpublished>
		<title type="sharef:primaryTitle">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>
		<field type="bibtex:topic">ieee8023[1] ethernet[0.9]</field>
	</reference>
	<reference name="iso8802-4" src="bibtex:misc" src-info="bibtex:line-28402" type="bibtex:misc">
		<names type="sharef:author">
			<name>International Organization for Standardization</name>
		</names>
		<date value="1990"/>
		<howpublished>ISO/IEC 8802-4</howpublished>
		<title type="sharef:primaryTitle">Information Processing Systems — Local area networks — Part 4: Token-passing bus access method and physical layer specifications</title>
		<field type="bibtex:topic">ieee8024[1] tokenbus[0.9]</field>
	</reference>
	<reference name="iso8802-5" src="bibtex:misc" src-info="bibtex:line-28410" type="bibtex:misc">
		<names type="sharef:author">
			<name>International Organization for Standardization</name>
		</names>
		<date value="1998"/>
		<howpublished>ISO/IEC 8802-5</howpublished>
		<title type="sharef:primaryTitle">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>
		<field type="bibtex:topic">ieee8025[1] tokenring[0.9]</field>
	</reference>
	<reference name="iso8824" src="bibtex:misc" src-info="bibtex:line-28418" type="bibtex:misc">
		<names type="sharef:author">
			<name>International Organization for Standardization</name>
		</names>
		<date value="1995"/>
		<howpublished>ISO/IEC 8824</howpublished>
		<title type="sharef:primaryTitle">Information Processing Systems — Open Systems Interconnection (OSI) — Specification of Abstract Syntax Notation One (ASN.1)</title>
		<field type="bibtex:topic">asn1[1]</field>
	</reference>
	<reference name="iso8825" src="bibtex:misc" src-info="bibtex:line-28426" type="bibtex:misc">
		<names type="sharef: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 type="sharef:primaryTitle">Information Processing Systems — Open Systems Interconnection (OSI) — Specification of Basic Encoding Rules for Abstract Syntax Notation One (ASN.1)</title>
	</reference>
	<reference name="iso8859" src="bibtex:misc" src-info="bibtex:line-28434" type="bibtex:misc">
		<names type="sharef:author">
			<name>International Organization for Standardization</name>
		</names>
		<date value="1999"/>
		<howpublished>ISO/IEC 8859</howpublished>
		<title type="sharef:primaryTitle">Information Technology — 8-bit single-byte coded graphic character sets</title>
		<field type="bibtex:topic">iso8859[1]</field>
	</reference>
	<reference name="iso8859-1" src="bibtex:misc" src-info="bibtex:line-28442" type="bibtex:misc">
		<names type="sharef:author">
			<name>International Organization for Standardization</name>
		</names>
		<date value="1998"/>
		<howpublished>ISO/IEC 8859-1</howpublished>
		<title type="sharef:primaryTitle">Information Technology — 8-bit single-byte coded graphic character sets — Part 1: Latin alphabet No. 1</title>
		<field type="bibtex:topic">iso8859[1]</field>
	</reference>
	<reference name="iso8859-5" src="bibtex:misc" src-info="bibtex:line-28451" type="bibtex:misc">
		<names type="sharef:author">
			<name>International Organization for Standardization</name>
		</names>
		<date value="1999"/>
		<howpublished>ISO/IEC 8859-5</howpublished>
		<title type="sharef:primaryTitle">Information Technology — 8-bit single-byte coded graphic character sets — Part 5: Latin/Cyrillic alphabet</title>
		<field type="bibtex:topic">iso8859[1]</field>
	</reference>
	<reference name="iso8879" src="bibtex:misc" src-info="bibtex:line-28460" type="bibtex:misc">
		<names type="sharef:author">
			<name>International Organization for Standardization</name>
		</names>
		<date value="1986"/>
		<howpublished>ISO 8879</howpublished>
		<title type="sharef:primaryTitle">Information Processing — Text and Office Systems — Standard Generalized Markup Language (SGML)</title>
		<field type="bibtex:topic">sgml[1]</field>
		<identifier type="sharef:uri">http://www.iso.ch/iso/en/CatalogueDetailPage.CatalogueDetail?CSNUMBER=16387</identifier>
	</reference>
	<reference name="iso9069" src="bibtex:misc" src-info="bibtex:line-28469" type="bibtex:misc">
		<names type="sharef:author">
			<name>International Organization for Standardization</name>
		</names>
		<date value="1988"/>
		<howpublished>ISO 9069</howpublished>
		<title type="sharef:primaryTitle">Information Processing — SGML Support Facilities — SGML Document Interchange Format (SDIF)</title>
		<field type="bibtex:topic">sdif[1]</field>
		<identifier type="sharef:uri">http://www.iso.ch/iso/en/CatalogueDetailPage.CatalogueDetail?CSNUMBER=16643</identifier>
	</reference>
	<reference name="iso9070" src="bibtex:misc" src-info="bibtex:line-28478" type="bibtex:misc">
		<names type="sharef:author">
			<name>International Organization for Standardization</name>
		</names>
		<date value="1991"/>
		<howpublished>ISO/IEC 9070</howpublished>
		<title type="sharef:primaryTitle">Information Technology — SGML Support Facilities — Registration procedures for public text owner identifiers</title>
		<field type="bibtex:topic">sgml[1]</field>
	</reference>
	<reference name="iso9072" src="bibtex:misc" src-info="bibtex:line-28486" type="bibtex:misc">
		<names type="sharef: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 type="sharef:primaryTitle">Information Processing Systems — Text Communication — Remote Operations</title>
	</reference>
	<reference name="iso9075" src="bibtex:misc" src-info="bibtex:line-28494" type="bibtex:misc">
		<names type="sharef:author">
			<name>International Organization for Standardization</name>
		</names>
		<date value="1992"/>
		<howpublished>ISO/IEC 9075</howpublished>
		<title type="sharef:primaryTitle">Information Technology — Database Languages — SQL</title>
		<field type="bibtex:topic">sql[1]</field>
	</reference>
	<reference name="iso9075-1:2008" src="bibtex:misc" src-info="bibtex:line-28502" type="bibtex:misc">
		<names type="sharef:author">
			<name>International Organization for Standardization</name>
		</names>
		<date value="2009-01"/>
		<abstract>
			<richtext>
				<p>ISO/IEC 9075 defines the SQL language. The scope of the SQL language is the definition of data structure and the operations on data stored in that structure. ISO/IEC 9075-1:2008, ISO/IEC 9075-2:2008 and ISO/IEC 9075-11:2008 encompass the minimum requirements of the language. Other parts define extensions. ISO/IEC 9075-1:2008 specifies the conceptual framework used in other parts of ISO/IEC 9075 to specify the grammar of SQL and the result of processing statements in that language by an SQL-implementation.</p>
			</richtext>
		</abstract>
		<howpublished>ISO/IEC 9075-1:2008</howpublished>
		<title type="sharef:primaryTitle">Information Technology — Database Languages — SQL — Part 1: Framework (SQL/Framework)</title>
		<field type="bibtex:topic">sqlxml[1]</field>
	</reference>
	<reference name="iso9075-14" src="bibtex:misc" src-info="bibtex:line-28512" type="bibtex:misc">
		<names type="sharef:author">
			<name>International Organization for Standardization</name>
		</names>
		<date value="2005-07"/>
		<howpublished>ISO/IEC 9075-14</howpublished>
		<title type="sharef:primaryTitle">Information Technology — Database Languages — SQL — Part 14: XML-Related Specifications (SQL/XML)</title>
		<field type="bibtex:topic">sqlxml[1]</field>
	</reference>
	<reference name="iso9541" src="bibtex:misc" src-info="bibtex:line-28521" type="bibtex:misc">
		<names type="sharef:author">
			<name>International Organization for Standardization</name>
		</names>
		<date value="1994"/>
		<howpublished>ISO/IEC 9541</howpublished>
		<title type="sharef:primaryTitle">Information Technology — Font Information Interchange</title>
	</reference>
	<reference name="iso9541-1" src="bibtex:misc" src-info="bibtex:line-28528" type="bibtex:misc">
		<names type="sharef:author">
			<name>International Organization for Standardization</name>
		</names>
		<date value="1994"/>
		<howpublished>ISO/IEC 9541-1</howpublished>
		<title type="sharef:primaryTitle">Information Technology — Font Information Interchange — Part 1: Architecture</title>
		<identifier type="sharef:uri">http://www.iso.ch/iso/en/CatalogueDetailPage.CatalogueDetail?CSNUMBER=17277</identifier>
	</reference>
	<reference name="iso9573" src="bibtex:misc" src-info="bibtex:line-28536" type="bibtex:misc">
		<names type="sharef:author">
			<name>International Organization for Standardization</name>
		</names>
		<date value="1988-12"/>
		<howpublished>ISO/IEC 9573</howpublished>
		<title type="sharef:primaryTitle">Information Processing — SGML Support Facilities — Techniques for using SGML</title>
		<field type="bibtex:topic">sgml[0.8]</field>
		<identifier type="sharef:uri">http://www.iso.org/iso/en/CatalogueDetailPage.CatalogueDetail?CSNUMBER=17319</identifier>
	</reference>
	<reference name="iso9573-11" src="bibtex:misc" src-info="bibtex:line-28546" type="bibtex:misc">
		<names type="sharef: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 type="sharef:primaryTitle">Information Processing — SGML Support Facilities — Part 11: Structure Descriptions and Style Specifications for Standards Document Interchange</title>
		<field type="bibtex:topic">iso[0.9]</field>
		<identifier type="sharef:uri">http://www.iso.org/iso/en/CatalogueDetailPage.CatalogueDetail?CSNUMBER=38368</identifier>
	</reference>
	<reference name="iso9573-13" src="bibtex:misc" src-info="bibtex:line-28557" type="bibtex:misc">
		<names type="sharef:author">
			<name>International Organization for Standardization</name>
		</names>
		<date value="2003-07"/>
		<howpublished>ISO/IEC 9573-13</howpublished>
		<title type="sharef:primaryTitle">Information Processing — SGML Support Facilities — Techniques for using SGML — Part 13: Public Entity Sets for Mathematics and Science</title>
		<field type="bibtex:topic">sgml[0.8]</field>
		<identifier type="sharef:uri">http://www.iso.org/iso/en/CatalogueDetailPage.CatalogueDetail?CSNUMBER=17332</identifier>
	</reference>
	<reference name="iso9660" src="bibtex:misc" src-info="bibtex:line-28567" type="bibtex:misc">
		<names type="sharef: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 type="sharef:primaryTitle">Information Processing — Volume and file structure of CD-ROM for information interchange</title>
		<field type="bibtex:topic">cdrom[1] iso9660[1]</field>
		<identifier type="sharef:uri">http://www.iso.org/iso/en/CatalogueDetailPage.CatalogueDetail?CSNUMBER=17505</identifier>
	</reference>
	<reference name="iso9753" src="bibtex:misc" src-info="bibtex:line-28578" type="bibtex:misc">
		<names type="sharef: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 type="sharef:primaryTitle">Electronic data interchange for administration, commerce and transport (EDIFACT) — Application level syntax rules (Syntax version number: 4)</title>
	</reference>
	<reference name="iso9945-1" src="bibtex:misc" src-info="bibtex:line-28586" type="bibtex:misc">
		<names type="sharef:author">
			<name>International Organization for Standardization</name>
		</names>
		<date value="1996"/>
		<howpublished>ISO/IEC 9945-1</howpublished>
		<title type="sharef:primaryTitle">Information Technology — Portable Operating System Interface (POSIX) — Part 1: System Application Program Interface (API) [C Language]</title>
		<field type="bibtex:topic">posix[1]</field>
	</reference>
	<reference name="iso9945-2" src="bibtex:misc" src-info="bibtex:line-28594" type="bibtex:misc">
		<names type="sharef:author">
			<name>International Organization for Standardization</name>
		</names>
		<date value="1993"/>
		<howpublished>ISO/IEC 9945-2</howpublished>
		<title type="sharef:primaryTitle">Information Technology — Portable Operating System Interface (POSIX) — Part 2: Shell and Utilities</title>
		<field type="bibtex:topic">posix[1] bre[0.9] ere[0.9]</field>
	</reference>
	<reference name="iso10149" src="bibtex:misc" src-info="bibtex:line-28602" type="bibtex:misc">
		<names type="sharef:author">
			<name>International Organization for Standardization</name>
		</names>
		<date value="1995"/>
		<howpublished>ISO/IEC 10149</howpublished>
		<title type="sharef:primaryTitle">Information Technology — Data interchange on read-only 120 mm optical data disks (CD-ROM)</title>
		<field type="bibtex:topic">cdrom[1]</field>
	</reference>
	<reference name="iso10179" src="bibtex:misc" src-info="bibtex:line-28610" type="bibtex:misc">
		<names type="sharef: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 type="sharef:primaryTitle">Information Technology — Processing languages — Document Style Semantics and Specification Language (DSSSL)</title>
		<field type="bibtex:topic">dsssl[1] sdql[1]</field>
		<identifier type="sharef:uri">http://www.iso.org/iso/en/CatalogueDetailPage.CatalogueDetail?CSNUMBER=18196</identifier>
	</reference>
	<reference name="iso10180" src="bibtex:misc" src-info="bibtex:line-28621" type="bibtex:misc">
		<names type="sharef:author">
			<name>International Organization for Standardization</name>
		</names>
		<date value="1995"/>
		<howpublished>ISO/IEC 10180</howpublished>
		<title type="sharef:primaryTitle">Information Technology — Processing languages — Standard Page Description Language (SPDL)</title>
		<field type="bibtex:topic">spdl[1]</field>
	</reference>
	<reference name="iso10646" src="bibtex:misc" src-info="bibtex:line-28629" type="bibtex:misc">
		<names type="sharef:author">
			<name>International Organization for Standardization</name>
		</names>
		<date value="1993"/>
		<howpublished>ISO/IEC 10646</howpublished>
		<title type="sharef:primaryTitle">Information Technology — Universal Multiple-Octet Coded Character Set (UCS)</title>
		<field type="bibtex:topic">ucs[1]</field>
	</reference>
	<reference name="iso10646-a1" src="bibtex:misc" src-info="bibtex:line-28637" type="bibtex:misc">
		<names type="sharef:author">
			<name>International Organization for Standardization</name>
		</names>
		<date value="1996"/>
		<howpublished>ISO/IEC 10646 (Amendment 1)</howpublished>
		<title type="sharef:primaryTitle">Transformation Format for 16 planes of group 00 (UTF-16)</title>
		<field type="bibtex:topic">utf16[1] ucs[0.8]</field>
	</reference>
	<reference name="iso10744" src="bibtex:misc" src-info="bibtex:line-28645" type="bibtex:misc">
		<names type="sharef:author">
			<name>International Organization for Standardization</name>
		</names>
		<date value="1997"/>
		<howpublished>ISO/IEC 10744</howpublished>
		<title type="sharef:primaryTitle">Information Technology — Hypermedia/Time-based Structuring Language (HyTime)</title>
		<field type="bibtex:topic">hytime[1]</field>
	</reference>
	<reference name="iso10746" src="bibtex:misc" src-info="bibtex:line-28653" type="bibtex:misc">
		<names type="sharef:author">
			<name>International Organization for Standardization</name>
		</names>
		<date value="1998"/>
		<howpublished>ISO/IEC 10746</howpublished>
		<title type="sharef:primaryTitle">Information Technology — Open Distributed Processing — Reference Model</title>
		<field type="bibtex:topic">odp[1]</field>
	</reference>
	<reference name="iso10746-1" src="bibtex:misc" src-info="bibtex:line-28661" type="bibtex:misc">
		<names type="sharef:author">
			<name>International Organization for Standardization</name>
		</names>
		<date value="2003-02"/>
		<howpublished>ISO/IEC 10746-1:1998</howpublished>
		<title type="sharef:primaryTitle">Information Technology — Open Distributed Processing — Reference Model: Overview</title>
		<field type="bibtex:topic">odp[1]</field>
		<identifier type="sharef:uri">http://standards.iso.org/ittf/PubliclyAvailableStandards/c020696_ISO_IEC_10746-1_1998(E).zip</identifier>
	</reference>
	<reference name="iso10746-2" src="bibtex:misc" src-info="bibtex:line-28671" type="bibtex:misc">
		<names type="sharef:author">
			<name>International Organization for Standardization</name>
		</names>
		<date value="2001-08"/>
		<howpublished>ISO/IEC 10746-2:1996</howpublished>
		<title type="sharef:primaryTitle">Information Technology — Open Distributed Processing — Reference Model: Foundations</title>
		<field type="bibtex:topic">odp[1]</field>
		<identifier type="sharef:uri">http://standards.iso.org/ittf/PubliclyAvailableStandards/s018836_ISO_IEC_10746-2_1996(E).zip</identifier>
	</reference>
	<reference name="iso10746-3" src="bibtex:misc" src-info="bibtex:line-28681" type="bibtex:misc">
		<names type="sharef:author">
			<name>International Organization for Standardization</name>
		</names>
		<date value="2001-08"/>
		<howpublished>ISO/IEC 10746-3:1996</howpublished>
		<title type="sharef:primaryTitle">Information Technology — Open Distributed Processing — Reference Model: Architecture</title>
		<field type="bibtex:topic">odp[1]</field>
		<identifier type="sharef:uri">http://standards.iso.org/ittf/PubliclyAvailableStandards/s020697_ISO_IEC_10746-3_1996(E).zip</identifier>
	</reference>
	<reference name="iso10746-4" src="bibtex:misc" src-info="bibtex:line-28691" type="bibtex:misc">
		<names type="sharef:author">
			<name>International Organization for Standardization</name>
		</names>
		<date value="2003-02"/>
		<howpublished>ISO/IEC 10746-4:1998</howpublished>
		<title type="sharef:primaryTitle">Information Technology — Open Distributed Processing — Reference Model: Architectural Semantics</title>
		<field type="bibtex:topic">odp[1]</field>
		<identifier type="sharef:uri">http://standards.iso.org/ittf/PubliclyAvailableStandards/c020698_ISO_IEC_10746-4_1998(E).zip</identifier>
	</reference>
	<reference name="iso10918" src="bibtex:misc" src-info="bibtex:line-28701" type="bibtex:misc">
		<names type="sharef:author">
			<name>International Organization for Standardization</name>
		</names>
		<date value="1999"/>
		<howpublished>ISO/IEC 10918</howpublished>
		<title type="sharef:primaryTitle">Information technology — Digital compression and coding of continuous-tone still images</title>
		<field type="bibtex:topic">jpeg[1]</field>
	</reference>
	<reference name="iso10918-1" src="bibtex:misc" src-info="bibtex:line-28709" type="bibtex:misc">
		<names type="sharef:author">
			<name>International Organization for Standardization</name>
		</names>
		<date value="1994"/>
		<howpublished>ISO/IEC 10918-1</howpublished>
		<title type="sharef:primaryTitle">Information technology — Digital compression and coding of continuous-tone still images: Requirements and guidelines</title>
		<field type="bibtex:topic">jpeg[1]</field>
	</reference>
	<reference name="iso10918-2" src="bibtex:misc" src-info="bibtex:line-28717" type="bibtex:misc">
		<names type="sharef:author">
			<name>International Organization for Standardization</name>
		</names>
		<date value="1995"/>
		<howpublished>ISO/IEC 10918-2</howpublished>
		<title type="sharef:primaryTitle">Information technology — Digital compression and coding of continuous-tone still images: Compliance testing</title>
		<field type="bibtex:topic">jpeg[1]</field>
	</reference>
	<reference name="iso10918-3" src="bibtex:misc" src-info="bibtex:line-28725" type="bibtex:misc">
		<names type="sharef:author">
			<name>International Organization for Standardization</name>
		</names>
		<date value="1997"/>
		<howpublished>ISO/IEC 10918-3</howpublished>
		<title type="sharef:primaryTitle">Information technology — Digital compression and coding of continuous-tone still images: Extensions</title>
		<field type="bibtex:topic">jpeg[1]</field>
	</reference>
	<reference name="iso10918-4" src="bibtex:misc" src-info="bibtex:line-28733" type="bibtex:misc">
		<names type="sharef:author">
			<name>International Organization for Standardization</name>
		</names>
		<date value="1999"/>
		<howpublished>ISO/IEC 10918-4</howpublished>
		<title type="sharef:primaryTitle">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>
		<field type="bibtex:topic">jpeg[0.9] spiff[1]</field>
	</reference>
	<reference name="iso11172" src="bibtex:misc" src-info="bibtex:line-28741" type="bibtex:misc">
		<names type="sharef:author">
			<name>International Organization for Standardization</name>
		</names>
		<date value="1998"/>
		<howpublished>ISO/IEC 11172</howpublished>
		<title type="sharef:primaryTitle">Information technology — Coding of moving pictures and associated audio for digital storage media at up to about 1.5 Mbit/s</title>
		<field type="bibtex:topic">mpeg1[1]</field>
	</reference>
	<reference name="iso11172-3" src="bibtex:misc" src-info="bibtex:line-28749" type="bibtex:misc">
		<names type="sharef:author">
			<name>International Organization for Standardization</name>
		</names>
		<date value="1999-03"/>
		<howpublished>ISO/IEC 11172-3</howpublished>
		<title type="sharef:primaryTitle">Information Technology — Coding of Moving Pictures and Associated Audio for Digital Storage Media at up to about 1.5 Mbit/s — Part 3: Audio</title>
		<field type="bibtex:topic">mp3[1] mpeg1[1]</field>
		<identifier type="sharef:uri">http://www.iso.ch/iso/en/CatalogueDetailPage.CatalogueDetail?CSNUMBER=22412</identifier>
	</reference>
	<reference name="iso11179-1" src="bibtex:misc" src-info="bibtex:line-28759" type="bibtex:misc">
		<names type="sharef:author">
			<name>International Organization for Standardization</name>
		</names>
		<date value="2004-09"/>
		<abstract>
			<richtext>
				<p>ISO/IEC 11179 specifies the kind and quality of metadata necessary to describe data, and it specifies the management and administration of that metadata in a metadata registry (MDR). It applies to the formulation of data representations, concepts, meanings, and relationships between them to be shared among people and machines, independent of the organization that produces the data. It does not apply to the physical representation of data as bits and bytes at the machine level. In ISO/IEC 11179, metadata refers to descriptions of data. ISO/IEC 11179 does not contain a general treatment of metadata. ISO/IEC 11179-1:2004 provides the means for understanding and associating the individual parts of ISO/IEC 11179 and is the foundation for a conceptual understanding of metadata and metadata registries.</p>
			</richtext>
		</abstract>
		<howpublished>ISO/IEC 11179-1:2004</howpublished>
		<title type="sharef:primaryTitle">Information Technology — Metadata Registries (MDR) — Part 1: Framework</title>
		<field type="bibtex:topic">mdr[1]</field>
		<identifier type="sharef:uri">http://www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_detail.htm?csnumber=35343</identifier>
	</reference>
	<reference name="iso11544" src="bibtex:misc" src-info="bibtex:line-28770" type="bibtex:misc">
		<names type="sharef:author">
			<name>International Organization for Standardization</name>
		</names>
		<date value="1993"/>
		<howpublished>ISO/IEC 11544</howpublished>
		<title type="sharef:primaryTitle">Information Technology — Coded Representation of Picture and Audio Information — Progressive Bi-level Image Compression</title>
		<field type="bibtex:topic">jbig[1]</field>
	</reference>
	<reference name="iso11578" src="bibtex:misc" src-info="bibtex:line-28778" type="bibtex:misc">
		<names type="sharef:author">
			<name>International Organization for Standardization</name>
		</names>
		<date value="1996"/>
		<howpublished>ISO/IEC 11578</howpublished>
		<title type="sharef:primaryTitle">Information Technology — Open Systems Interconnection (OSI) — Remote Procedure Call (RPC)</title>
		<field type="bibtex:topic">isorpc[0.9] osi[0.8]</field>
	</reference>
	<reference name="iso12083" src="bibtex:misc" src-info="bibtex:line-28786" type="bibtex:misc">
		<names type="sharef: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 type="sharef:primaryTitle">Information and Documentation — Electronic Manuscript Preparation and Markup</title>
		<field type="bibtex:topic">mathml[1]</field>
		<identifier type="sharef:uri">http://www.iso.ch/iso/en/CatalogueDetailPage.CatalogueDetail?CSNUMBER=20866</identifier>
		<identifier type="sharef:uri">http://www.techstreet.com/cgi-bin/detail?product_id=52643</identifier>
	</reference>
	<reference name="iso12234-2" src="bibtex:misc" src-info="bibtex:line-28797" type="bibtex:misc">
		<names type="sharef:author">
			<name>International Organization for Standardization</name>
		</names>
		<date value="2001-10"/>
		<howpublished>ISO 12234-2</howpublished>
		<title type="sharef:primaryTitle">Electronic Still-Picture Imaging — Removable Memory — Part 2: TIFF/EP Image Data Format</title>
		<field type="bibtex:topic">tiffep[1]</field>
		<identifier type="sharef:uri">http://www.iso.org/iso/en/CatalogueDetailPage.CatalogueDetail?CSNUMBER=29377</identifier>
	</reference>
	<reference name="iso12639" src="bibtex:misc" src-info="bibtex:line-28807" type="bibtex:misc">
		<names type="sharef: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 type="sharef:primaryTitle">Graphic Technology — Prepress Digital Data Exchange — Tag Image File Format for Image Technology (TIFF/IT)</title>
		<identifier type="sharef:uri">http://www.iso.ch/iso/en/CatalogueDetailPage.CatalogueDetail?CSNUMBER=2181</identifier>
	</reference>
	<reference name="iso13236" src="bibtex:misc" src-info="bibtex:line-28817" type="bibtex:misc">
		<names type="sharef: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 type="sharef:primaryTitle">Information Technology — Quality of Service — Framework</title>
	</reference>
	<reference name="iso13250" src="bibtex:misc" src-info="bibtex:line-28825" type="bibtex:misc">
		<names type="sharef:author">
			<name>International Organization for Standardization</name>
		</names>
		<date value="2000"/>
		<howpublished>ISO/IEC 13250</howpublished>
		<title type="sharef:primaryTitle">Information Technology — SGML Applications — Topic Maps</title>
		<field type="bibtex:topic">topicmaps[1]</field>
	</reference>
	<reference name="iso13346" src="bibtex:misc" src-info="bibtex:line-28833" type="bibtex:misc">
		<names type="sharef:author">
			<name>International Organization for Standardization</name>
		</names>
		<date value="1995"/>
		<howpublished>ISO/IEC 13346</howpublished>
		<title type="sharef:primaryTitle">Information Technology — Volume and file structure of write-once and rewritable media using non-sequential recording for information interchange</title>
		<field type="bibtex:topic">iso13346[1]</field>
	</reference>
	<reference name="iso13818" src="bibtex:misc" src-info="bibtex:line-28841" type="bibtex:misc">
		<names type="sharef:author">
			<name>International Organization for Standardization</name>
		</names>
		<date value="1999"/>
		<howpublished>ISO/IEC 13818</howpublished>
		<title type="sharef:primaryTitle">Information Technology — Generic coding of moving pictures and associated audio information</title>
		<field type="bibtex:topic">mpeg2[1]</field>
	</reference>
	<reference name="iso13818-3" src="bibtex:misc" src-info="bibtex:line-28849" type="bibtex:misc">
		<names type="sharef: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 type="sharef:primaryTitle">Information Technology — Generic coding of moving pictures and associated audio information — Part 3: Audio</title>
	</reference>
	<reference name="iso13818-7" src="bibtex:misc" src-info="bibtex:line-28857" type="bibtex:misc">
		<names type="sharef: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 type="sharef:primaryTitle">Information Technology — Generic coding of moving pictures and associated audio information — Part 7: Advanced Audio Coding (AAC)</title>
	</reference>
	<reference name="iso14496" src="bibtex:misc" src-info="bibtex:line-28865" type="bibtex:misc">
		<names type="sharef: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 type="sharef:primaryTitle">Information Technology — Coding of audio-visual objects</title>
	</reference>
	<reference name="iso14496-3" src="bibtex:misc" src-info="bibtex:line-28873" type="bibtex:misc">
		<names type="sharef: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 type="sharef:primaryTitle">Information Technology — Coding of audio-visual objects — Part 3: Audio</title>
	</reference>
	<reference name="iso14496-22" src="bibtex:misc" src-info="bibtex:line-28881" type="bibtex:misc">
		<names type="sharef:author">
			<name>International Organization for Standardization</name>
		</names>
		<date value="2009-07"/>
		<abstract>
			<richtext>
				<p>ISO/IEC 14496-22:2009 specifies the Open Font Format (OFF) specification, the TrueType and Compact Font Format (CFF) outline formats, and the TrueType hinting language. It makes references to both TrueType and PostScript, as Open Font Format fonts combine the two technologies. Multimedia applications require a broad range of media-related standards. In addition to the typical audio and video applications, multimedia presentations include scalable 2D graphics and text supporting all languages of the world. Faithful reproduction of scalable multimedia content requires additional components including scalable font technology. The Open Font Format is an extension of the TrueType font format, adding support for PostScript font data. OFF fonts and the operating system services which support OFF fonts provide users with a simple way to install and use fonts, whether the fonts contain TrueType outlines or CFF (PostScript) outlines. The Open Font Format addresses the following goals: broader multi-platform support; excellent support for international character sets; excellent protection for font data; smaller file sizes to make font distribution more efficient; excellent support for advanced typographic control. PostScript data included in OFF fonts may be directly rasterized or converted to the TrueType outline format for rendering, depending on which rasterizers have been installed in the host operating system. But the user model is the same: OFF fonts just work. Users will not need to be aware of the type of outline data in OFF fonts. And font creators can use whichever outline format they feel provides the best set of features for their work, without worrying about limiting a font's usability. OFF fonts can include the OFF Layout tables, which allow font creators to design broader international and high-end typographic fonts. The OFF Layout tables contain information on glyph substitution, glyph positioning, justification, and baseline positioning, enabling text-processing applications to improve text layout. As with TrueType fonts, OFF fonts allow the handling of large glyph sets using Unicode encoding. Such encoding allows broad international support, as well as support for typographic glyph variants. Additionally, OFF fonts may contain digital signatures, which enable operating systems and browsing applications to identify the source and integrity of font files, including embedded font files obtained in web documents, before using them. Also, font developers can encode embedding restrictions in OFF fonts which cannot be altered in a font signed by the developer.</p>
			</richtext>
		</abstract>
		<howpublished>ISO/IEC 14496-22:2009</howpublished>
		<title type="sharef:primaryTitle">Information Technology — Coding of audio-visual objects — Part 22: Open Font Format</title>
		<field type="bibtex:topic">off[1] truetype[0.9] cff[0.9]</field>
	</reference>
	<reference name="iso14750" src="bibtex:misc" src-info="bibtex:line-28891" type="bibtex:misc">
		<names type="sharef:author">
			<name>International Organization for Standardization</name>
		</names>
		<date value="1999"/>
		<howpublished>ISO/IEC 14750</howpublished>
		<title type="sharef:primaryTitle">Information Technology — Open Distributed Processing — Interface Definition Language</title>
		<field type="bibtex:topic">odp[0.9] idl[1]</field>
	</reference>
	<reference name="iso14772" src="bibtex:misc" src-info="bibtex:line-28899" type="bibtex:misc">
		<names type="sharef:author">
			<name>International Organization for Standardization</name>
		</names>
		<date value="1997-12"/>
		<howpublished>ISO/IEC 14772</howpublished>
		<title type="sharef:primaryTitle">Information Technology — Virtual Reality Modeling Language (VRML)</title>
		<field type="bibtex:topic">vrml[1]</field>
	</reference>
	<reference name="iso14977" src="bibtex:misc" src-info="bibtex:line-28908" type="bibtex:misc">
		<names type="sharef: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 type="sharef:primaryTitle">Information Technology — Syntactic Metalanguage — Extended BNF</title>
		<field type="bibtex:topic">ebnf[1]</field>
		<identifier type="sharef:uri">http://www.iso.ch/iso/en/CatalogueDetailPage.CatalogueDetail?CSNUMBER=26153</identifier>
	</reference>
	<reference name="iso15000-1" src="bibtex:misc" src-info="bibtex:line-28919" type="bibtex:misc">
		<names type="sharef:author">
			<name>International Organization for Standardization</name>
		</names>
		<date value="2004-05"/>
		<abstract>
			<richtext>
				<p>ISO 15000-1:2004 specifies the requirements for a collaboration-protocol profile (CPP), and a collaboration-protocol agreement (CPA). The CPP describes a trading partner's technical capabilities for performing electronic business. The CPA describes the agreement between two trading partners on the technical capabilities they will use for a specific electronic-business collaboration. Included in the CPP and CPA are details of transport, messaging (using ISO 15000-2:2004), security constraints, and binding to a business-process-specification document that contains the definition of the interactions between the two parties while engaging in a specified electronic business collaboration. ISO 15000-1:2004 defines the mark-up language vocabulary for creating the electronic CPPs and CPAs and includes examples of a pair of CPPs and a CPA derived from them, the process specification document referenced by the CPPs and CPA, and the XML schema governing the structures of CPPs and CPAs. A prospective trading partner may publish one or more CPPs. A CPA for a business collaboration between two trading partners is derived by combining one CPP from each trading partner. The "legal" terms and conditions of a Business agreement are outside the scope of ISO 15000-1:2004.</p>
			</richtext>
		</abstract>
		<howpublished>ISO/TS 15000-1:2004</howpublished>
		<title type="sharef:primaryTitle">Electronic Business Extensible Markup Language (ebXML) — Part 1: Collaboration-Protocol Profile and Agreement Specification (ebCPP)</title>
		<field type="bibtex:topic">ebxml[1] ebcpp[1]</field>
		<identifier type="sharef:uri">http://www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_detail.htm?csnumber=39972</identifier>
	</reference>
	<reference name="iso15000-2" src="bibtex:misc" src-info="bibtex:line-28930" type="bibtex:misc">
		<names type="sharef:author">
			<name>International Organization for Standardization</name>
		</names>
		<date value="2004-05"/>
		<abstract>
			<richtext>
				<p>ISO 15000-2:2004 addresses the requirements for an ebXML message service handler for the eBusiness community. ISO 15000-2:2004 defines a communications-protocol neutral method for exchanging electronic business messages and defines specific enveloping constructs supporting reliable, secure delivery of business information. ISO 15000-2:2004 includes a flexible enveloping technique permitting messages that is independent of the payload, the communications protocol used, and also of any format type. The versatility ensures legacy electronic business systems employing traditional syntaxes (i.e., UN/EDIFACT, ASCX12, or HL7) can leverage the ebXML infrastructure along with users of emerging technologies. Examples using these specifications with HTTP (RFC2616) and SMTP (RFC2821) are included.</p>
			</richtext>
		</abstract>
		<howpublished>ISO/TS 15000-2:2004</howpublished>
		<title type="sharef:primaryTitle">Electronic business Extensible Markup Language (ebXML) — Part 2: Message Service Specification (ebMS)</title>
		<field type="bibtex:topic">ebxml[1] ebms[1]</field>
		<identifier type="sharef:uri">http://www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_detail.htm?csnumber=39973</identifier>
	</reference>
	<reference name="iso15000-3" src="bibtex:misc" src-info="bibtex:line-28942" type="bibtex:misc">
		<names type="sharef:author">
			<name>International Organization for Standardization</name>
		</names>
		<date value="2004-05"/>
		<abstract>
			<richtext>
				<p>ISO 15000-3:2004 defines the requirements for the information model for the ebXML registry. The ebXML registry describes objects that reside in a repository for storage and safekeeping. The information model does not deal with the actual content of the repository. All elements of the information model represent metadata about the content stored in the repository. Such information is used to facilitate ebXML-based Business-to-Business partnerships and transactions. The registry information model provides a high-level schema for the ebXML registry. It provides information on the type of metadata that are stored in the registry as well as the relationships among metadata classes. The registry information model defines what types of objects are stored and defines how stored objects are organized. The abstract registry is implemented using one or both of the following concrete bindings: a SOAP binding using the HTTP protocol, or an ebXML messaging service binding. These specifications are compatible with other ebXML specifications.</p>
			</richtext>
		</abstract>
		<howpublished>ISO/TS 15000-3:2004</howpublished>
		<title type="sharef:primaryTitle">Electronic business Extensible Markup Language (ebXML) — Part 3: Registry Information Model Specification (ebRIM)</title>
		<field type="bibtex:topic">ebxml[1] ebrim[1]</field>
		<identifier type="sharef:uri">http://www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_detail.htm?csnumber=39974</identifier>
	</reference>
	<reference name="iso15000-4" src="bibtex:misc" src-info="bibtex:line-28953" type="bibtex:misc">
		<names type="sharef:author">
			<name>International Organization for Standardization</name>
		</names>
		<date value="2004-05"/>
		<abstract>
			<richtext>
				<p>ISO 15000-4:2004 defines the interface between the registry and the registry clients, as well as the interaction protocols, message definitions and XML schema. The interface is intended to function as the basis for a more complete definition of the ebXML registry requirements in the future. The ebXML Registry provides a set of services that enable sharing of information between interested parties for the purpose of enabling business process integration between such parties based on the ebXML specifications. The shared information is maintained as objects in a repository and managed by the ebXML Registry Services defined in this document.</p>
			</richtext>
		</abstract>
		<howpublished>ISO/TS 15000-4:2004</howpublished>
		<title type="sharef:primaryTitle">Electronic business Extensible Markup Language (ebXML) — Part 4: Registry Services Specification (ebRS)</title>
		<field type="bibtex:topic">ebxml[1] ebrs[1]</field>
		<identifier type="sharef:uri">http://www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_detail.htm?csnumber=39975</identifier>
	</reference>
	<reference name="iso15000-5" src="bibtex:misc" src-info="bibtex:line-28964" type="bibtex:misc">
		<names type="sharef:author">
			<name>International Organization for Standardization</name>
		</names>
		<date value="2004-05"/>
		<abstract>
			<richtext>
				<p>ISO/TS 15000-5:2005 can be employed wherever business information is being shared or exchanged amongst and between enterprises, governmental agencies, and/or other organisations in an open and worldwide environment. ISO/TS 15000-5:2005 will form the basis for standards development work of business analysts, business users and information technology specialists supplying the content of and implementing applications that will employ the UN/CEFACT Core Component Library (CCL). The Core Component Library will be stored in a UN/CEFACT repository and identified in an ebXML compliant registry. Due to the evolving nature of the UN/CEFACT Core Component Library, ISO/TS 15000-5:2005 includes material that focuses on the business community doing further discovery and analysis work. Some of the contents of ISO/TS 15000-5:2005 are not typical of this type of technical document. However, they are critical for successful adoption and standardization in this area to move forward.</p>
			</richtext>
		</abstract>
		<howpublished>ISO/TS 15000-5:2005</howpublished>
		<title type="sharef:primaryTitle">Electronic business Extensible Markup Language (ebXML) — Part 5: ebXML Core Components Technical Specification, Version 2.01 (ebCCTS)</title>
		<field type="bibtex:topic">ebxml[1] ccts[1]</field>
		<identifier type="sharef:uri">http://www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_detail.htm?csnumber=41022</identifier>
	</reference>
	<reference name="iso15022" src="bibtex:misc" src-info="bibtex:line-28975" type="bibtex:misc">
		<names type="sharef:author">
			<name>International Organization for Standardization</name>
		</names>
		<date value="2002-01"/>
		<howpublished>ISO 15022</howpublished>
		<title type="sharef:primaryTitle">Securities — Scheme for Messages (Data Field Dictionary)</title>
		<field type="bibtex:topic">uml[0.7] xsd[0.7]</field>
		<identifier type="sharef:uri">http://www.iso.ch/iso/en/CatalogueDetailPage.CatalogueDetail?CSNUMBER=25775</identifier>
	</reference>
	<reference name="iso15444" src="bibtex:misc" src-info="bibtex:line-28985" type="bibtex:misc">
		<names type="sharef:author">
			<name>International Organization for Standardization</name>
		</names>
		<date value="2002-07"/>
		<howpublished>ISO/IEC 15444</howpublished>
		<title type="sharef:primaryTitle">Information Technology — JPEG 2000 Image Coding System</title>
		<field type="bibtex:topic">jpeg2000[1]</field>
		<identifier type="sharef:uri">http://www.iso.ch/iso/en/CatalogueDetailPage.CatalogueDetail?CSNUMBER=27687</identifier>
	</reference>
	<reference name="iso15444-1" src="bibtex:misc" src-info="bibtex:line-28995" type="bibtex:misc">
		<names type="sharef:author">
			<name>International Organization for Standardization</name>
		</names>
		<date value="2004-10"/>
		<abstract>
			<richtext>
				<p>ISO/IEC 15444-1:2004 defines a set of lossless (bit-preserving) and lossy compression methods for coding bi-level, continuous-tone grey-scale, palletized colour, or continuous-tone colour digital still images. ISO/IEC 15444-1:2004 specifies decoding processes for converting compressed image data to reconstructed image data; specifies a codestream syntax containing information for interpreting the compressed image data; specifies a file format; provides guidance on encoding processes for converting source image data to compressed image data; provides guidance on how to implement these processes in practice.</p>
			</richtext>
		</abstract>
		<howpublished>ISO/IEC 15444-1:2004</howpublished>
		<title type="sharef:primaryTitle">Information Technology — JPEG 2000 Image Coding System — Part 1: Core Coding System</title>
		<field type="bibtex:topic">jpeg2000[1] jp2[1]</field>
		<identifier type="sharef:uri">http://www.iso.ch/iso/en/CatalogueDetailPage.CatalogueDetail?CSNUMBER=37674</identifier>
	</reference>
	<reference name="iso15444-2" src="bibtex:misc" src-info="bibtex:line-29006" type="bibtex:misc">
		<names type="sharef:author">
			<name>International Organization for Standardization</name>
		</names>
		<date value="2004-05"/>
		<abstract>
			<richtext>
				<p>ISO/IEC 15444-2:2004 defines a set of lossless (bit-preserving) and lossy compression methods for coding continuous-tone, bi-level, grey-scale, colour digital still images, or multi-component images. ISO/IEC 15444-2:2004 specifies extended decoding processes for converting compressed image data to reconstructed image data; specifies an extended codestream syntax containing information for interpreting the compressed image data; specifies an extended file format; specifies a container to store image metadata; defines a standard set of image metadata; provides guidance on extended encoding processes for converting source image data to compressed image data; provides guidance on how to implement these processes in practice.</p>
			</richtext>
		</abstract>
		<howpublished>ISO/IEC 15444-2:2004</howpublished>
		<title type="sharef:primaryTitle">Information Technology — JPEG 2000 Image Coding System — Extensions</title>
		<field type="bibtex:topic">jpeg2000[1] jpx[1]</field>
		<identifier type="sharef:uri">http://www.iso.ch/iso/en/CatalogueDetailPage.CatalogueDetail?CSNUMBER=33160</identifier>
	</reference>
	<reference name="iso15444-9" src="bibtex:misc" src-info="bibtex:line-29017" type="bibtex:misc">
		<names type="sharef:author">
			<name>International Organization for Standardization</name>
		</names>
		<date value="2005-11"/>
		<abstract>
			<richtext>
				<p>ISO/IEC 15444-9:2005 defines, in an extensible manner, syntaxes and methods for the remote interrogation and optional modification of JPEG 2000 codestreams and files in accordance with their definition in the following parts of ISO/IEC 15444: (1) ISO/IEC 15444-1 and its definition of a JPEG 2000 codestream and JP2 file format; and (2) the JPEG 2000 family of file formats as defined in further parts of ISO/IEC 15444. In ISO/IEC 15444-9:2005, the defined syntaxes and methods are referred to as the JPEG 2000 Interactive Protocol, "JPIP", and interactive applications using JPIP are referred to as "JPIP systems".</p>
			</richtext>
		</abstract>
		<howpublished>ISO/IEC 15444-9:2005</howpublished>
		<title type="sharef:primaryTitle">Information Technology — JPEG 2000 Image Coding System — Interactivity Tools, APIs and Protocols</title>
		<field type="bibtex:topic">jpeg2000[0.9] jpip[1]</field>
		<identifier type="sharef:uri">http://www.iso.ch/iso/en/CatalogueDetailPage.CatalogueDetail?CSNUMBER=39413</identifier>
	</reference>
	<reference name="iso15445" src="bibtex:misc" src-info="bibtex:line-29028" type="bibtex:misc">
		<names type="sharef:author">
			<name>International Organization for Standardization</name>
		</names>
		<date value="2000-05"/>
		<howpublished>ISO/IEC 15445</howpublished>
		<title type="sharef:primaryTitle">Information Technology — Document Description and Processing Languages — HyperText Markup Language (HTML)</title>
		<field type="bibtex:topic">html[1]</field>
		<identifier type="sharef:uri">http://www.iso.ch/iso/en/CatalogueDetailPage.CatalogueDetail?CSNUMBER=27688</identifier>
	</reference>
	<reference name="iso15836" src="bibtex:misc" src-info="bibtex:line-29038" type="bibtex:misc">
		<names type="sharef: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 type="sharef:primaryTitle">Information and Documentation — The Dublin Core Metadata Element Set</title>
		<field type="bibtex:topic">dublincore[1]</field>
		<field type="bibtex:updates">rfc2413</field>
		<identifier type="sharef:uri">http://www.iso.org/iso/en/CatalogueDetailPage.CatalogueDetail?CSNUMBER=37629</identifier>
	</reference>
	<reference name="iso15929" src="bibtex:misc" src-info="bibtex:line-29050" type="bibtex:misc">
		<names type="sharef:author">
			<name>International Organization for Standardization</name>
		</names>
		<date value="2002"/>
		<abstract>
			<richtext>
				<p>This International Standard specifies the guidelines and principles that serve as the basis for the development of the parts of ISO 15930 that define the use of the Portable Document Format (PDF) in various graphic technology applications.</p>
			</richtext>
		</abstract>
		<howpublished>ISO 15929:2002</howpublished>
		<title type="sharef:primaryTitle">Graphic Technology — Prepress Digital Data Exchange — Guidelines and Principles for the Development of PDF/X Standards</title>
		<field type="bibtex:topic">pdfx[1]</field>
		<identifier type="sharef:uri">http://www.iso.org/iso/en/CatalogueDetailPage.CatalogueDetail?CSNUMBER=37629</identifier>
	</reference>
	<reference name="iso15930-1" src="bibtex:misc" src-info="bibtex:line-29060" type="bibtex:misc">
		<names type="sharef:author">
			<name>International Organization for Standardization</name>
		</names>
		<date value="2006-08"/>
		<howpublished>ISO 15930-1:2001</howpublished>
		<title type="sharef:primaryTitle">Graphic Technology — Prepress Digital Data Exchange — Use of PDF — Part 1: Complete Exchange Using CMYK Data (PDF/X-1 and PDF/X-1a)</title>
		<field type="bibtex:topic">pdfx[1] pdfx1[1]</field>
	</reference>
	<reference name="iso15948" src="bibtex:misc" src-info="bibtex:line-29069" type="bibtex:misc">
		<names type="sharef: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 type="sharef:primaryTitle">Information Technology — Computer Graphics and Image Processing — Portable Network Graphics (PNG): Functional specification</title>
		<field type="bibtex:topic">png[1]</field>
		<field type="bibtex:updates">png</field>
		<identifier type="sharef:uri">http://www.iso.org/iso/en/CatalogueDetailPage.CatalogueDetail?CSNUMBER=29581</identifier>
	</reference>
	<reference name="iso16022" src="bibtex:misc" src-info="bibtex:line-29081" type="bibtex:misc">
		<names type="sharef:author">
			<name>International Organization for Standardization</name>
		</names>
		<date value="2006-09"/>
		<abstract>
			<richtext>
				<p>ISO/IEC 16022:2006 defines the requirements for the symbology known as Data Matrix. It specifies the Data Matrix symbology characteristics, data character encodation, symbol formats, dimensions and print quality requirements, error correction rules, decoding algorithm, and user-selectable application parameters. It applies to all Data Matrix symbols produced by any printing or marking technology. Data Matrix is a two-dimensional matrix symbology which is made up of nominally square modules arranged within a perimeter finder pattern. Though primarily shown and described in ISO/IEC 16022:2006 as a dark symbol on light background, Data Matrix symbols can also be printed to appear as light on dark. Manufacturers of bar code equipment and users of the technology require publicly available standard symbology specifications to which they can refer when developing equipment and application standards. The publication of standardized symbology specifications is designed to achieve this.</p>
			</richtext>
		</abstract>
		<howpublished>ISO/IEC 16022:2006</howpublished>
		<title type="sharef:primaryTitle">Information Technology — Automatic Identification and Data Capture Techniques — Data Matrix Bar Code Symbology Specification</title>
		<field type="bibtex:topic">datamatrix[1]</field>
		<identifier type="sharef:uri">http://www.iso.org/iso/iso_catalogue/catalogue_ics/catalogue_detail_ics.htm?csnumber=44230</identifier>
	</reference>
	<reference name="iso16262" src="bibtex:misc" src-info="bibtex:line-29092" type="bibtex:misc">
		<names type="sharef:author">
			<name>International Organization for Standardization</name>
		</names>
		<date value="2002-06"/>
		<abstract>
			<richtext>
				<p>ISO/IEC 16262:2002 defines the ECMAScript scripting language.</p>
			</richtext>
		</abstract>
		<howpublished>ISO/IEC 16262</howpublished>
		<title type="sharef:primaryTitle">Information Technology — ECMAScript Language Specification</title>
		<field type="bibtex:topic">ecmascript[1]</field>
		<identifier type="sharef:uri">http://www.iso.ch/iso/en/CatalogueDetailPage.CatalogueDetail?CSNUMBER=33835</identifier>
	</reference>
	<reference name="iso18004" src="bibtex:misc" src-info="bibtex:line-29103" type="bibtex:misc">
		<names type="sharef:author">
			<name>International Organization for Standardization</name>
		</names>
		<date value="2006"/>
		<howpublished>ISO/IEC 18004:2006</howpublished>
		<title type="sharef:primaryTitle">Information Technology — Automatic Identification and Data Capture Techniques — QR Code 2005 Bar Code Symbology Specification</title>
		<field type="bibtex:topic">qr[1]</field>
		<identifier type="sharef:uri">http://www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_detail.htm?csnumber=43655</identifier>
	</reference>
	<reference name="iso19005-1" src="bibtex:misc" src-info="bibtex:line-29112" type="bibtex:misc">
		<names type="sharef:author">
			<name>International Organization for Standardization</name>
		</names>
		<date value="2008-07"/>
		<howpublished>ISO 19005-1:2005</howpublished>
		<title type="sharef:primaryTitle">Document management — Electronic Document File Format for Long-Term Preservation — Part 1: Use of PDF 1.4 (PDF/A-1)</title>
		<field type="bibtex:topic">pdfa[1]</field>
		<identifier type="sharef:uri">ISO</identifier>
		<identifier type="sharef:uri">19005-1:2005</identifier>
		<identifier type="sharef:uri">specifies</identifier>
		<identifier type="sharef:uri">how</identifier>
		<identifier type="sharef:uri">to</identifier>
		<identifier type="sharef:uri">use</identifier>
		<identifier type="sharef:uri">the</identifier>
		<identifier type="sharef:uri">Portable</identifier>
		<identifier type="sharef:uri">Document</identifier>
		<identifier type="sharef:uri">Format</identifier>
		<identifier type="sharef:uri">(PDF)</identifier>
		<identifier type="sharef:uri">1.4</identifier>
		<identifier type="sharef:uri">for</identifier>
		<identifier type="sharef:uri">long-term</identifier>
		<identifier type="sharef:uri">preservation</identifier>
		<identifier type="sharef:uri">of</identifier>
		<identifier type="sharef:uri">electronic</identifier>
		<identifier type="sharef:uri">documents.</identifier>
		<identifier type="sharef:uri">It</identifier>
		<identifier type="sharef:uri">is</identifier>
		<identifier type="sharef:uri">applicable</identifier>
		<identifier type="sharef:uri">to</identifier>
		<identifier type="sharef:uri">documents</identifier>
		<identifier type="sharef:uri">containing</identifier>
		<identifier type="sharef:uri">combinations</identifier>
		<identifier type="sharef:uri">of</identifier>
		<identifier type="sharef:uri">character,</identifier>
		<identifier type="sharef:uri">raster</identifier>
		<identifier type="sharef:uri">and</identifier>
		<identifier type="sharef:uri">vector</identifier>
		<identifier type="sharef:uri">data.</identifier>
	</reference>
	<reference name="iso19103" src="bibtex:misc" src-info="bibtex:line-29122" type="bibtex:misc">
		<names type="sharef:author">
			<name>International Organization for Standardization</name>
		</names>
		<date value="2006-10"/>
		<abstract>
			<richtext>
				<p>ISO TS 19103:2005 provides rules and guidelines for the use of a conceptual schema language within the ISO geographic information standards. The chosen conceptual schema language is the Unified Modeling Language (UML). ISO TS 19103:2005 provides a profile of UML for use with geographic information. In addition, it provides guidelines on how UML should be used to create standardized geographic information and service models.</p>
			</richtext>
		</abstract>
		<howpublished>ISO/IEC 19103:2005</howpublished>
		<title type="sharef:primaryTitle">Geographic Information — Conceptual Schema Language</title>
		<field type="bibtex:topic">uml[0.8]</field>
		<identifier type="sharef:uri">http://www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_detail.htm?csnumber=37800</identifier>
	</reference>
	<reference name="iso19115" src="bibtex:misc" src-info="bibtex:line-29133" type="bibtex:misc">
		<names type="sharef: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 type="sharef:primaryTitle">Geographic Information — Metadata</title>
		<field type="bibtex:topic">metadata[1]</field>
		<identifier type="sharef:uri">http://www.iso.org/iso/en/CatalogueDetailPage.CatalogueDetail?CSNUMBER=26020</identifier>
	</reference>
	<reference name="iso19501" src="bibtex:misc" src-info="bibtex:line-29144" type="bibtex:misc">
		<names type="sharef:author">
			<name>International Organization for Standardization</name>
		</names>
		<date value="2005-04"/>
		<abstract>
			<richtext>
				<p>ISO/IEC 19501:2005 describes the Unified Modeling Language (UML), a graphical language for visualizing, specifying, constructing and documenting the artifacts of a software-intensive system. The UML offers a standard way to write a system's blueprints, including conceptual things such as business processes and system functions, as well as concrete things such as programming language statements, database schemas, and reusable software components.</p>
			</richtext>
		</abstract>
		<howpublished>ISO/IEC 19501:2005</howpublished>
		<title type="sharef:primaryTitle">Information Technology — Open Distributed Processing — Unified Modeling Language (UML) Version 1.4.2</title>
		<field type="bibtex:topic">uml[1]</field>
		<identifier type="sharef:uri">http://www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_detail.htm?csnumber=32620</identifier>
	</reference>
	<reference name="iso19757-1" src="bibtex:misc" src-info="bibtex:line-29155" type="bibtex:misc">
		<names type="sharef:author">
			<name>International Organization for Standardization</name>
		</names>
		<date value="2005-02"/>
		<howpublished>ISO/IEC 19757-1</howpublished>
		<title type="sharef:primaryTitle">Information Technology — Document Schema Definition Languages (DSDL) — Part 1: Overview</title>
		<field type="bibtex:topic">dsdl[1]</field>
		<identifier type="sharef:uri">http://www.iso.org/iso/en/CatalogueDetailPage.CatalogueDetail?CSNUMBER=37606</identifier>
	</reference>
	<reference name="iso19757-2" src="bibtex:misc" src-info="bibtex:line-29165" type="bibtex:misc">
		<names type="sharef: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 type="sharef:primaryTitle">Information Technology — Document Schema Definition Languages (DSDL) — Part 2: Grammar-based Validation — RELAX NG</title>
		<field type="bibtex:topic">relaxng[1]</field>
		<identifier type="sharef:uri">http://www.iso.org/iso/en/CatalogueDetailPage.CatalogueDetail?CSNUMBER=37605</identifier>
		<identifier type="sharef:uri">http://standards.iso.org/ittf/PubliclyAvailableStandards/c037605_ISO_IEC_19757-2_2003(E).zip</identifier>
	</reference>
	<reference name="iso19757-3" src="bibtex:misc" src-info="bibtex:line-29177" type="bibtex:misc">
		<names type="sharef:author">
			<name>International Organization for Standardization</name>
		</names>
		<date value="2006-04"/>
		<howpublished>ISO/IEC 19757-3</howpublished>
		<title type="sharef:primaryTitle">Information Technology — Document Schema Definition Languages (DSDL) — Part 3: Rule-based Validation — Schematron</title>
		<field type="bibtex:topic">schematron[1]</field>
		<identifier type="sharef:uri">http://www.iso.org/iso/en/CatalogueDetailPage.CatalogueDetail?CSNUMBER=40833</identifier>
		<identifier type="sharef:uri">http://standards.iso.org/ittf/PubliclyAvailableStandards/c040833_ISO_IEC_19757-3_2006(E).zip</identifier>
	</reference>
	<reference name="iso19757-4" src="bibtex:misc" src-info="bibtex:line-29188" type="bibtex:misc">
		<names type="sharef:author">
			<name>International Organization for Standardization</name>
		</names>
		<date value="2006-06"/>
		<howpublished>ISO/IEC 19757-4:2006</howpublished>
		<title type="sharef:primaryTitle">Information Technology — Document Schema Definition Languages (DSDL) — Part 4: Namespace-based Validation Dispatching Language — NVDL</title>
		<field type="bibtex:topic">nvdl[1]</field>
		<identifier type="sharef:uri">http://www.iso.org/iso/en/CatalogueDetailPage.CatalogueDetail?CSNUMBER=38615</identifier>
		<identifier type="sharef:uri">http://standards.iso.org/ittf/PubliclyAvailableStandards/c038615_ISO_IEC_19757-4_2006(E).zip</identifier>
	</reference>
	<reference name="iso19757-5" src="bibtex:misc" src-info="bibtex:line-29199" type="bibtex:misc">
		<names type="sharef:author">
			<name>International Organization for Standardization</name>
		</names>
		<date value="2004-09"/>
		<howpublished>ISO/IEC 19757-5</howpublished>
		<title type="sharef:primaryTitle">Information Technology — Document Schema Definition Languages (DSDL) — Part 4: Datatype Library Language (DTLL)</title>
		<field type="bibtex:topic">dtll[1]</field>
		<identifier type="sharef:uri" resourceType="text/html">http://dsdl.org/0546.htm</identifier>
	</reference>
	<reference name="iso19757-8" src="bibtex:misc" src-info="bibtex:line-29209" type="bibtex:misc">
		<names type="sharef:author">
			<name>International Organization for Standardization</name>
		</names>
		<date value="2004-11"/>
		<howpublished>ISO/IEC 19757-8 (under development)</howpublished>
		<title type="sharef:primaryTitle">Information Technology — Document Schema Definition Languages (DSDL) — Part 8: Document Schema Renaming Language — DSRL</title>
		<field type="bibtex:topic">dsrl[1]</field>
	</reference>
	<reference name="iso19793" src="bibtex:misc" src-info="bibtex:line-29218" type="bibtex:misc">
		<names type="sharef:author">
			<name>International Organization for Standardization</name>
		</names>
		<date value="2005-05"/>
		<howpublished>ISO/IEC CD 19793</howpublished>
		<title type="sharef:primaryTitle">Information Technology — Open Distributed Processing — Use of UML for ODP System Specifications</title>
		<field type="bibtex:topic">odp[0.9] uml[0.7]</field>
	</reference>
	<reference name="iso20943-1" src="bibtex:misc" src-info="bibtex:line-29227" type="bibtex:misc">
		<names type="sharef:author">
			<name>International Organization for Standardization</name>
		</names>
		<date value="2003-07"/>
		<abstract>
			<richtext>
				<p>An ISO/IEC 11179-based metadata registry (MDR) (hereafter referred to as a "registry") is a tool for the management of shareable data; a comprehensive, authoritative source of reference information about data. It supports the standardization and harmonization processes by recording and disseminating data standards, which facilitates data sharing among organizations and users. It provides links to documents that refer to data elements and to information systems where data elements are used. When used in conjunction with an information database, the registry enables users to better understand the information obtained. A registry does not contain data itself. It contains the metadata that is necessary to clearly describe, inventory, analyze, and classify data. It provides an understanding of the meaning, representation, and identification of units of data. The standard identifies the information elements that need to be available for determining the meaning of a data element (DE) to be shared between systems. The purpose of ISO/IEC TR 20943-1:2003 is to describe a set of procedures for the consistent registration of data elements and their attributes in a registry. ISO/IEC TR 20943-1:2003 is not a data entry manual, but a user's guide for conceptualizing a data element and its associated metadata items for the purpose of consistently establishing good quality data elements. An organization may adapt and/or add to these procedures as necessary. The scope of ISO/IEC TR 20943-1:2003 is limited to the associated items of a data element: the data element identifier, names and definitions in particular contexts, and examples; data element concept; conceptual domain with its value meanings; and value domain with its permissible values. There is a choice when registering code sets and other value domains in an ISO/IEC 11179 metadata registry. Some Registration Authorities treat these sets as value domains, and others treat them as data elements. For the purposes of ISO/IEC TR 20943-1:2003, the choice will always be to treat the sets as data elements unless explicitly stated. This choice is made to help illustrate the way to register many different kinds of data elements, including examples for registering standard code sets as data elements.</p>
			</richtext>
		</abstract>
		<howpublished>ISO/IEC TR 20943-1:2003</howpublished>
		<title type="sharef:primaryTitle">Information Technology — Procedures for Achieving Metadata Registry Content Consistency — Part 1: Data Elements</title>
		<field type="bibtex:topic">mdr[0.9]</field>
		<identifier type="sharef:uri">http://www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_detail.htm?csnumber=41112</identifier>
	</reference>
	<reference name="iso21000-2" src="bibtex:misc" src-info="bibtex:line-29238" type="bibtex:misc">
		<names type="sharef:author">
			<name>International Organization for Standardization</name>
		</names>
		<date value="2005-10"/>
		<abstract>
			<richtext>
				<p>ISO/IEC 21000-2:2005 specifies: Model: The Digital Item Declaration Model describes a set of abstract terms and concepts to form a useful model for defining Digital Items; Representation: The Digital Item Declaration Language (DIDL) is based upon the terms and concepts defined in the above model. It contains the normative description of the syntax and semantics of each of the DIDL elements, as represented in XML; Schema: Informative XML schemas illustrating complete grammars for representation of the DID in XML conforming to the normative representation; Detailed Examples: Illustrative (non-normative) examples of DIDL documents are provided to aid in understanding the use of the specification and its potential applications. The ISO/IEC 21000 (MPEG-21) series of International Standards defines an open framework for multimedia delivery and consumption, with both the content creator and content consumer as focal points. The vision for MPEG-21 is to define a multimedia framework to enable transparent and augmented use of multimedia resources across a wide range of networks and devices used by different communities. This second part of MPEG-21 (ISO/IEC 21000-2:2005) specifies a uniform and flexible abstraction and interoperable representation for declaring the structure and makeup of Digital Items. A Digital Item Declaration (DID) involves specifying the resources, metadata, and their interrelationships for a Digital Item. A DID is done using the Digital Item Declaration Language (DIDL).</p>
			</richtext>
		</abstract>
		<howpublished>ISO/IEC 21000-2:2005</howpublished>
		<title type="sharef:primaryTitle">Information Technology — Multimedia Framework (MPEG-21) — Part 2: Digital Item Declaration</title>
		<field type="bibtex:topic">didl[1]</field>
		<identifier type="sharef:uri">http://www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_detail.htm?csnumber=41112</identifier>
	</reference>
	<reference name="iso21127" src="bibtex:misc" src-info="bibtex:line-29249" type="bibtex:misc">
		<names type="sharef:author">
			<name>International Organization for Standardization</name>
		</names>
		<date value="2006-09"/>
		<abstract>
			<richtext>
				<p>ISO 21127:2006 establishes guidelines for the exchange of information between cultural heritage institutions. In simple terms this can be defined as the curated knowledge of museums. A more detailed definition can be articulated by defining both the intended scope, a broad and maximally inclusive definition of general principles, and the practical scope, which is defined by reference to a set of specific museum documentation standards and practices. The intended scope of ISO 21127:2006 is defined as the exchange and integration of heterogeneous scientific documentation relating to museum collections. This definition requires further elaboration: The term "scientific documentation" is intended to convey the requirement that the depth and quality of descriptive information that can be handled by ISO 21127:2006 need be sufficient for serious academic research. This does not mean that information intended for presentation to members of the general public is excluded, but rather that ISO 21127:2006 is intended to provide the level of detail and precision expected and required by museum professionals and researchers in the field. The term "museum collections" is intended to cover all types of material collected and displayed by museums and related institutions, as defined by ICOM. This includes collections, sites, and monuments relating to fields such as social history, ethnography, archaeology, fine and applied arts, natural history, history of sciences and technology. The documentation of collections includes the detailed description of individual items within collections, groups of items and collections as a whole. ISO 21127:2006 is specifically intended to cover contextual information (i.e. the historical, geographical, and theoretical background that gives museum collections much of their cultural significance and value). The exchange of relevant information with libraries and archives, and harmonization with their models, falls within the intended scope of ISO 21127:2006. Information required solely for the administration and management of cultural institutions, such as information relating to personnel, accounting, and visitor statistics, falls outside the intended scope of ISO 21127:2006. The practical scope of ISO 21127:2006 is the set of reference standards for museum documentation that have been used to guide and validate its development. ISO 21127:2006 covers the same domain of discourse as the union of these reference documents; this means that data correctly encoded according to any of these reference documents can be expressed in a compatible form, without any loss of meaning.</p>
			</richtext>
		</abstract>
		<howpublished>ISO 21127:2006</howpublished>
		<title type="sharef:primaryTitle">Information and Documentation — A Reference Ontology for the Interchange of Cultural Heritage Information</title>
		<field type="bibtex:topic">cidoc[1]</field>
		<identifier type="sharef:uri">http://www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_detail.htm?csnumber=34424</identifier>
	</reference>
	<reference name="iso21961" src="bibtex:misc" src-info="bibtex:line-29260" type="bibtex:misc">
		<names type="sharef:author">
			<name>International Organization for Standardization</name>
		</names>
		<date value="2003-03"/>
		<howpublished>ISO 21961</howpublished>
		<title type="sharef:primaryTitle">Space Data and Information Transfer Systems — Data Entity Dictionary Specification Language (DEDSL) — Abstract Syntax</title>
		<field type="bibtex:topic">desdl[1]</field>
		<identifier type="sharef:uri">http://www.iso.ch/iso/en/CatalogueDetailPage.CatalogueDetail?CSNUMBER=36036</identifier>
	</reference>
	<reference name="iso21962" src="bibtex:misc" src-info="bibtex:line-29270" type="bibtex:misc">
		<names type="sharef:author">
			<name>International Organization for Standardization</name>
		</names>
		<date value="2003-03"/>
		<howpublished>ISO 21962</howpublished>
		<title type="sharef:primaryTitle">Space Data and Information Transfer Systems — Data Entity Dictionary Specification Language (DEDSL) — PVL Syntax</title>
		<field type="bibtex:topic">desdl[1] pvl[1]</field>
		<identifier type="sharef:uri">http://www.iso.ch/iso/en/CatalogueDetailPage.CatalogueDetail?CSNUMBER=36037</identifier>
	</reference>
	<reference name="iso22537" src="bibtex:misc" src-info="bibtex:line-29280" type="bibtex:misc">
		<names type="sharef: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 type="sharef:primaryTitle">Information Technology — ECMAScript for XML (E4X) Specification</title>
		<field type="bibtex:topic">ecmascript[0.9] xml[0.7] e4x[1]</field>
		<identifier type="sharef:uri">http://www.iso.org/iso/en/CatalogueDetailPage.CatalogueDetail?CSNUMBER=41002</identifier>
		<identifier type="sharef:uri">http://standards.iso.org/ittf/PubliclyAvailableStandards/c041002_ISO_IEC_22537_2006(E).zip</identifier>
	</reference>
	<reference name="iso22643" src="bibtex:misc" src-info="bibtex:line-29292" type="bibtex:misc">
		<names type="sharef:author">
			<name>International Organization for Standardization</name>
		</names>
		<date value="2003-04"/>
		<howpublished>ISO 22643</howpublished>
		<title type="sharef:primaryTitle">Space Data and Information Transfer Systems — Data Entity Dictionary Specification Language (DEDSL) — XML/DTD Syntax</title>
		<field type="bibtex:topic">desdl[1]</field>
		<identifier type="sharef:uri">http://www.iso.ch/iso/en/CatalogueDetailPage.CatalogueDetail?CSNUMBER=36377</identifier>
	</reference>
	<reference name="iso23950" src="bibtex:misc" src-info="bibtex:line-29302" type="bibtex:misc">
		<names type="sharef:author">
			<name>International Organization for Standardization</name>
		</names>
		<date value="1998"/>
		<howpublished>ISO 23950</howpublished>
		<title type="sharef:primaryTitle">Information and Documentation — Information retrieval (Z39.50) — Application service definition and protocol specification</title>
		<field type="bibtex:topic">z3950[1]</field>
		<field type="bibtex:updates">z39</field>
		<identifier type="sharef:uri">http://www.iso.org/iso/en/CatalogueDetailPage.CatalogueDetail?CSNUMBER=27446</identifier>
	</reference>
	<reference name="iso24517-1" src="bibtex:misc" src-info="bibtex:line-29312" type="bibtex:misc">
		<names type="sharef:author">
			<name>International Organization for Standardization</name>
		</names>
		<date value="2008-05"/>
		<howpublished>ISO 24517-1:2008</howpublished>
		<title type="sharef:primaryTitle">Document Management — Engineering Document Format using PDF — Part 1: Use of PDF 1.6 (PDF/E-1)</title>
		<field type="bibtex:topic">pdfe[1]</field>
		<identifier type="sharef:uri">ISO</identifier>
		<identifier type="sharef:uri">24517-1:2008</identifier>
		<identifier type="sharef:uri">specifies</identifier>
		<identifier type="sharef:uri">the</identifier>
		<identifier type="sharef:uri">use</identifier>
		<identifier type="sharef:uri">of</identifier>
		<identifier type="sharef:uri">the</identifier>
		<identifier type="sharef:uri">Portable</identifier>
		<identifier type="sharef:uri">Document</identifier>
		<identifier type="sharef:uri">Format</identifier>
		<identifier type="sharef:uri">(PDF)</identifier>
		<identifier type="sharef:uri">Version</identifier>
		<identifier type="sharef:uri">1.6</identifier>
		<identifier type="sharef:uri">for</identifier>
		<identifier type="sharef:uri">the</identifier>
		<identifier type="sharef:uri">creation</identifier>
		<identifier type="sharef:uri">of</identifier>
		<identifier type="sharef:uri">documents</identifier>
		<identifier type="sharef:uri">used</identifier>
		<identifier type="sharef:uri">in</identifier>
		<identifier type="sharef:uri">engineering</identifier>
		<identifier type="sharef:uri">workflows.</identifier>
		<identifier type="sharef:uri">ISO</identifier>
		<identifier type="sharef:uri">24517-1:2008</identifier>
		<identifier type="sharef:uri">does</identifier>
		<identifier type="sharef:uri">not</identifier>
		<identifier type="sharef:uri">define</identifier>
		<identifier type="sharef:uri">the</identifier>
		<identifier type="sharef:uri">following:</identifier>
		<identifier type="sharef:uri">method</identifier>
		<identifier type="sharef:uri">of</identifier>
		<identifier type="sharef:uri">electronic</identifier>
		<identifier type="sharef:uri">distribution;</identifier>
		<identifier type="sharef:uri">method</identifier>
		<identifier type="sharef:uri">of</identifier>
		<identifier type="sharef:uri">creation</identifier>
		<identifier type="sharef:uri">or</identifier>
		<identifier type="sharef:uri">conversion</identifier>
		<identifier type="sharef:uri">from</identifier>
		<identifier type="sharef:uri">paper</identifier>
		<identifier type="sharef:uri">or</identifier>
		<identifier type="sharef:uri">electronic</identifier>
		<identifier type="sharef:uri">documents</identifier>
		<identifier type="sharef:uri">to</identifier>
		<identifier type="sharef:uri">the</identifier>
		<identifier type="sharef:uri">PDF/E</identifier>
		<identifier type="sharef:uri">format;</identifier>
		<identifier type="sharef:uri">specific</identifier>
		<identifier type="sharef:uri">technical</identifier>
		<identifier type="sharef:uri">design,</identifier>
		<identifier type="sharef:uri">user</identifier>
		<identifier type="sharef:uri">interface,</identifier>
		<identifier type="sharef:uri">or</identifier>
		<identifier type="sharef:uri">implementation;</identifier>
		<identifier type="sharef:uri">required</identifier>
		<identifier type="sharef:uri">computer</identifier>
		<identifier type="sharef:uri">hardware</identifier>
		<identifier type="sharef:uri">and/operating</identifier>
		<identifier type="sharef:uri">systems;</identifier>
		<identifier type="sharef:uri">or</identifier>
		<identifier type="sharef:uri">methods</identifier>
		<identifier type="sharef:uri">for</identifier>
		<identifier type="sharef:uri">validating</identifier>
		<identifier type="sharef:uri">the</identifier>
		<identifier type="sharef:uri">conformance</identifier>
		<identifier type="sharef:uri">of</identifier>
		<identifier type="sharef:uri">PDF/E</identifier>
		<identifier type="sharef:uri">files</identifier>
		<identifier type="sharef:uri">or</identifier>
		<identifier type="sharef:uri">readers.</identifier>
	</reference>
	<reference name="iso24824-1" src="bibtex:misc" src-info="bibtex:line-29322" type="bibtex:misc">
		<names type="sharef: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 type="sharef:primaryTitle">Information Technology — Generic Applications of ASN.1: Fast Infoset</title>
		<field type="bibtex:topic">xmlinfoset[0.8]</field>
		<identifier type="sharef:uri">http://www.iso.org/iso/en/CatalogueDetailPage.CatalogueDetail?CSNUMBER=41327</identifier>
	</reference>
	<reference name="iso26300" src="bibtex:misc" src-info="bibtex:line-29333" type="bibtex:misc">
		<names type="sharef:author">
			<name>International Organization for Standardization</name>
		</names>
		<date value="2006-11"/>
		<abstract>
			<richtext>
				<p>ISO/IEC 26300:2006 defines an XML schema for office applications and its semantics. The schema is suitable for office documents, including text documents, spreadsheets, charts and graphical documents like drawings or presentations, but is not restricted to these kinds of documents. ISO/IEC 26300:2006 provides for high-level information suitable for editing documents. It defines suitable XML structures for office documents and is friendly to transformations using XSLT or similar XML-based tools. ISO/IEC 26300:2006 first provides an introduction to the OpenDocument format and explains the structure of documents that conform to the OpenDocument specification. It describes the meta information that can be contained in such documents, and their text and paragraph content. Text Fields and text indices are described. ISO/IEC 26300:2006 describes the table content of a document in OpenDocument format, its graphical content, its chart content and its form content. It also describes content that is common to all documents. It describes the integration of SMIL animation markup into the OpenDocument schema. It explains style information content and specifies formatting properties that can be used within styles. The data types used by the OpenDocument schema are described. The OpenDocument format makes use of a package concept; these packages are described.</p>
			</richtext>
		</abstract>
		<howpublished>ISO/IEC 26300:2006</howpublished>
		<title type="sharef:primaryTitle">Information Technology — Open Document Format for Office Applications (OpenDocument) v1.0</title>
		<field type="bibtex:topic">odf[1]</field>
		<identifier type="sharef:uri">http://standards.iso.org/ittf/PubliclyAvailableStandards/c043485_ISO_IEC_26300_2006(E).zip</identifier>
	</reference>
	<reference name="iso29500-1" src="bibtex:misc" src-info="bibtex:line-29344" type="bibtex:misc">
		<names type="sharef:author">
			<name>International Organization for Standardization</name>
		</names>
		<date value="2008-11"/>
		<abstract>
			<richtext>
				<p>ISO/IEC 29500-1:2008 defines a set of XML vocabularies for representing word-processing documents, spreadsheets and presentations, based on the Microsoft Office 2008 applications. It specifies requirements for Office Open XML consumers and producers that comply to the strict conformance category.</p>
			</richtext>
		</abstract>
		<howpublished>ISO/IEC 29500-1:2008</howpublished>
		<title type="sharef:primaryTitle">Information Technology — Document Description and Processing Languages — Office Open XML File Formats — Part 1: Fundamentals and Markup Language Reference</title>
		<field type="bibtex:topic">ooxml[1]</field>
		<identifier type="sharef:uri">http://standards.iso.org/ittf/PubliclyAvailableStandards/c051463_ISOIEC%2029500-1_2008(E).zip</identifier>
	</reference>
	<reference name="iso29500-2" src="bibtex:misc" src-info="bibtex:line-29355" type="bibtex:misc">
		<names type="sharef:author">
			<name>International Organization for Standardization</name>
		</names>
		<date value="2008-11"/>
		<abstract>
			<richtext>
				<p>ISO/IEC 29500-2:2008 defines a general-purpose file/component packaging facility, which is built on top of the widely used ZIP file structure.</p>
			</richtext>
		</abstract>
		<howpublished>ISO/IEC 29500-2:2008</howpublished>
		<title type="sharef:primaryTitle">Information Technology — Document Description and Processing Languages — Office Open XML File Formats — Part 2: Open Packaging Conventions</title>
		<field type="bibtex:topic">ooxml[0.9] opc[1]</field>
		<identifier type="sharef:uri">http://standards.iso.org/ittf/PubliclyAvailableStandards/c051459_ISOIEC%2029500-2_2008_Electronic_inserts.zip</identifier>
	</reference>
	<reference name="iso29500-3" src="bibtex:misc" src-info="bibtex:line-29366" type="bibtex:misc">
		<names type="sharef:author">
			<name>International Organization for Standardization</name>
		</names>
		<date value="2008-11"/>
		<abstract>
			<richtext>
				<p>ISO/IEC 29500-3:2008 defines a general-purpose mechanism to extend an XML vocabulary.</p>
			</richtext>
		</abstract>
		<howpublished>ISO/IEC 29500-3:2008</howpublished>
		<title type="sharef:primaryTitle">Information Technology — Document Description and Processing Languages — Office Open XML File Formats — Part 3: Markup Compatibility and Extensibility</title>
		<field type="bibtex:topic">ooxml[1]</field>
		<identifier type="sharef:uri">http://standards.iso.org/ittf/PubliclyAvailableStandards/c051461_ISOIEC%2029500-3_2008(E).zip</identifier>
	</reference>
	<reference name="iso29500-4" src="bibtex:misc" src-info="bibtex:line-29377" type="bibtex:misc">
		<names type="sharef:author">
			<name>International Organization for Standardization</name>
		</names>
		<date value="2008-11"/>
		<abstract>
			<richtext>
				<p>ISO/IEC 29500-4:2008 defines a set of XML elements and attributes, over and above those defined by ISO/IEC 29500-1, that provide support for legacy Microsoft Office applications; that is, those prior to the 2008 release. It specifies requirements for Office Open XML consumers and producers that comply to the transitional conformance category.</p>
			</richtext>
		</abstract>
		<howpublished>ISO/IEC 29500-4:2008</howpublished>
		<title type="sharef:primaryTitle">Information Technology — Document Description and Processing Languages — Office Open XML File Formats — Part 4: Transitional Migration Features</title>
		<field type="bibtex:topic">ooxml[1]</field>
		<identifier type="sharef:uri">http://standards.iso.org/ittf/PubliclyAvailableStandards/c051462_ISOIEC%2029500-4_2008(E).zip</identifier>
	</reference>
	<reference name="iso32000-1" src="bibtex:misc" src-info="bibtex:line-29388" type="bibtex:misc">
		<names type="sharef:author">
			<name>International Organization for Standardization</name>
		</names>
		<date value="2008-07"/>
		<abstract>
			<richtext>
				<p>ISO 32000-1:2008 specifies a digital form for representing electronic documents to enable users to exchange and view electronic documents independent of the environment in which they were created or the environment in which they are viewed or printed. It is intended for the developer of software that creates PDF files (conforming writers), software that reads existing PDF files and interprets their contents for display and interaction (conforming readers) and PDF products that read and/or write PDF files for a variety of other purposes (conforming products). ISO 32000-1:2008 does not specify the following: specific processes for converting paper or electronic documents to the PDF format; specific technical design, user interface or implementation or operational details of rendering; specific physical methods of storing these documents such as media and storage conditions; methods for validating the conformance of PDF files or readers; required computer hardware and/or operating system.</p>
			</richtext>
		</abstract>
		<howpublished>ISO 32000-1:2008</howpublished>
		<title type="sharef:primaryTitle">Document Management — Portable Document Format — Part 1: PDF 1.7</title>
		<field type="bibtex:topic">pdf[1]</field>
		<identifier type="sharef:uri">http://www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_detail.htm?csnumber=51502</identifier>
	</reference>
	<reference name="isoects" src="bibtex:misc" src-info="bibtex:line-29399" type="bibtex:misc">
		<names type="sharef:author">
			<name>International Organization for Standardization</name>
		</names>
		<date value="1995-03"/>
		<address type="sharef:placePublished">Beppu</address>
		<howpublished>ISO/IEC JTC1/SC6</howpublished>
		<field type="bibtex:index">ECTS/ECTP</field>
		<title type="sharef:primaryTitle">First Draft of Enhanced Communications Transport Service Definition</title>
	</reference>
	<reference name="isompt" src="bibtex:misc" src-info="bibtex:line-29409" type="bibtex:misc">
		<names type="sharef:author">
			<name>International Organization for Standardization</name>
		</names>
		<date value="1995-03"/>
		<address type="sharef:placePublished">Beppu</address>
		<howpublished>ISO/IEC JTC1/SC6 N9161/IV</howpublished>
		<field type="bibtex:index">ECTS/ECTP</field>
		<title type="sharef:primaryTitle">Draft Text on the Subject of "Multi-peer Taxonomy"</title>
	</reference>
	<reference name="e123" src="bibtex:misc" src-info="bibtex:line-29423" type="bibtex:misc">
		<names type="sharef:author">
			<name>International Telecommunication Union</name>
		</names>
		<date value="2001-02"/>
		<howpublished>ITU-T Recommendation E.123</howpublished>
		<title type="sharef:primaryTitle">Notation for national and international telephone numbers, e-mail addresses, and Web addresses</title>
	</reference>
	<reference name="e164" src="bibtex:misc" src-info="bibtex:line-29431" type="bibtex:misc">
		<names type="sharef: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 type="sharef:primaryTitle">The International Public Telecommunication Numbering Plan</title>
		<identifier type="sharef: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" src="bibtex:misc" src-info="bibtex:line-29441" type="bibtex:misc">
		<names type="sharef:author">
			<name>International Telecommunication Union</name>
		</names>
		<date value="1988-11"/>
		<howpublished>ITU-T Recommendation G.711</howpublished>
		<title type="sharef:primaryTitle">Pulse code modulation (PCM) of voice frequencies</title>
	</reference>
	<reference name="g726" src="bibtex:misc" src-info="bibtex:line-29449" type="bibtex:misc">
		<names type="sharef:author">
			<name>International Telecommunication Union</name>
		</names>
		<date value="1990-12"/>
		<howpublished>ITU-T Recommendation G.726</howpublished>
		<title type="sharef:primaryTitle">40, 32, 24, 16 kbit/s Adaptive Differential Pulse Code Modulation (ADPCM)</title>
	</reference>
	<reference name="g992" src="bibtex:misc" src-info="bibtex:line-29457" type="bibtex:misc">
		<names type="sharef:author">
			<name>International Telecommunication Union</name>
		</names>
		<date value="1999-06"/>
		<howpublished>ITU-T Recommendation G.992.2</howpublished>
		<title type="sharef:primaryTitle">Splitterless Asymmetric Digital Subscriber Line (ADSL) transceivers</title>
		<field type="bibtex:topic">glite[1]</field>
	</reference>
	<reference name="h225" src="bibtex:misc" src-info="bibtex:line-29466" type="bibtex:misc">
		<names type="sharef: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 type="sharef:primaryTitle">Call Signalling Protocols and Media Stream Packetization for Packet-based Multimedia Communication Systems</title>
		<field type="bibtex:topic">h225[1]</field>
		<identifier type="sharef: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" src="bibtex:misc" src-info="bibtex:line-29477" type="bibtex:misc">
		<names type="sharef: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 type="sharef:primaryTitle">Packet-based Multimedia Communications Systems</title>
		<field type="bibtex:topic">h323[1]</field>
		<identifier type="sharef: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" src="bibtex:misc" src-info="bibtex:line-29488" type="bibtex:misc">
		<names type="sharef: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 type="sharef:primaryTitle">Directory Services Architecture for Multimedia Conferencing</title>
		<field type="bibtex:topic">h350[1]</field>
		<identifier type="sharef: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" src="bibtex:misc" src-info="bibtex:line-29499" type="bibtex:misc">
		<names type="sharef: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 type="sharef:primaryTitle">International Mobile Telecommunications 2000 (IMT-2000)</title>
	</reference>
	<reference name="q24" src="bibtex:misc" src-info="bibtex:line-29508" type="bibtex:misc">
		<names type="sharef: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 type="sharef:primaryTitle">Multifrequency Push-Button Signal Reception</title>
	</reference>
	<reference name="q921" src="bibtex:misc" src-info="bibtex:line-29517" type="bibtex:misc">
		<names type="sharef:author">
			<name>International Telecommunication Union</name>
		</names>
		<date value="1988"/>
		<howpublished>ITU-T Recommendation Q.921</howpublished>
		<title type="sharef:primaryTitle">ISDN User-Network Interface — Data Link Layer Specification</title>
	</reference>
	<reference name="q931" src="bibtex:misc" src-info="bibtex:line-29524" type="bibtex:misc">
		<names type="sharef:author">
			<name>International Telecommunication Union</name>
		</names>
		<date value="1988"/>
		<howpublished>ITU-T Recommendation Q.931</howpublished>
		<title type="sharef:primaryTitle">ISDN User-Network Interface Layer 3 Specification for Basic Call Control</title>
	</reference>
	<reference name="q1200" src="bibtex:misc" src-info="bibtex:line-29531" type="bibtex:misc">
		<names type="sharef:author">
			<name>International Telecommunication Union</name>
		</names>
		<date value="1993-03"/>
		<howpublished>ITU-T Recommendation Q.1200</howpublished>
		<title type="sharef:primaryTitle">Q-Series Intelligent Network Recommendation Structure</title>
	</reference>
	<reference name="q1201" src="bibtex:misc" src-info="bibtex:line-29539" type="bibtex:misc">
		<names type="sharef:author">
			<name>International Telecommunication Union</name>
		</names>
		<date value="1992-10"/>
		<howpublished>ITU-T Recommendation Q.1201</howpublished>
		<title type="sharef:primaryTitle">Principles of Intelligent Network Architecture</title>
	</reference>
	<reference name="q2931" src="bibtex:misc" src-info="bibtex:line-29547" type="bibtex:misc">
		<names type="sharef:author">
			<name>International Telecommunication Union</name>
		</names>
		<date value="1995-02"/>
		<howpublished>ITU-T Recommendation Q.2931</howpublished>
		<title type="sharef:primaryTitle">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" src="bibtex:misc" src-info="bibtex:line-29555" type="bibtex:misc">
		<names type="sharef:author">
			<name>International Telecommunication Union</name>
		</names>
		<date value="1995-10"/>
		<howpublished>ITU-T Recommendation Q.2971</howpublished>
		<title type="sharef:primaryTitle">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" src="bibtex:misc" src-info="bibtex:line-29563" type="bibtex:misc">
		<names type="sharef:author">
			<name>International Telecommunication Union</name>
		</names>
		<date value="1996-07"/>
		<howpublished>ITU-T Recommendation T.4</howpublished>
		<title type="sharef:primaryTitle">Standardization of Group 3 facsimile terminals for document transmission</title>
		<field type="bibtex:topic">g3fax[1]</field>
	</reference>
	<reference name="t6" src="bibtex:misc" src-info="bibtex:line-29572" type="bibtex:misc">
		<names type="sharef:author">
			<name>International Telecommunication Union</name>
		</names>
		<date value="1988-11"/>
		<howpublished>ITU-T Recommendation T.6</howpublished>
		<title type="sharef:primaryTitle">Facsimile coding schemes and coding control functions for Group 4 facsimile apparatus</title>
		<field type="bibtex:topic">g4fax[1]</field>
	</reference>
	<reference name="t120" src="bibtex:misc" src-info="bibtex:line-29581" type="bibtex:misc">
		<names type="sharef:author">
			<name>International Telecommunication Union</name>
		</names>
		<date value="1996-07"/>
		<howpublished>ITU-T Recommendation T.120</howpublished>
		<title type="sharef:primaryTitle">Data protocols for multimedia conferencing</title>
	</reference>
	<reference name="t121" src="bibtex:misc" src-info="bibtex:line-29589" type="bibtex:misc">
		<names type="sharef:author">
			<name>International Telecommunication Union</name>
		</names>
		<date value="1996-07"/>
		<howpublished>ITU-T Recommendation T.121</howpublished>
		<title type="sharef:primaryTitle">Generic application template</title>
	</reference>
	<reference name="t122" src="bibtex:misc" src-info="bibtex:line-29597" type="bibtex:misc">
		<names type="sharef:author">
			<name>International Telecommunication Union</name>
		</names>
		<date value="1993-03"/>
		<howpublished>ITU-T Recommendation T.122</howpublished>
		<title type="sharef:primaryTitle">Multipoint Communication Service for Audiographics and Audiovisual Conferencing — Service Definition</title>
	</reference>
	<reference name="t123" src="bibtex:misc" src-info="bibtex:line-29605" type="bibtex:misc">
		<names type="sharef:author">
			<name>International Telecommunication Union</name>
		</names>
		<date value="1994-11"/>
		<howpublished>ITU-T Recommendation T.123</howpublished>
		<title type="sharef:primaryTitle">Protocol Stack for Audiographics and Audiovisual Teleconference Applications</title>
	</reference>
	<reference name="t124" src="bibtex:misc" src-info="bibtex:line-29613" type="bibtex:misc">
		<names type="sharef:author">
			<name>International Telecommunication Union</name>
		</names>
		<date value="1995-08"/>
		<howpublished>ITU-T Recommendation T.124</howpublished>
		<title type="sharef:primaryTitle">Generic Conference Control for Audiovisual and Audiographic Terminals</title>
	</reference>
	<reference name="t125" src="bibtex:misc" src-info="bibtex:line-29621" type="bibtex:misc">
		<names type="sharef:author">
			<name>International Telecommunication Union</name>
		</names>
		<date value="1994-04"/>
		<howpublished>ITU-T Recommendation T.125</howpublished>
		<title type="sharef:primaryTitle">Multipoint Communication Service — Protocol Specification</title>
	</reference>
	<reference name="x200" src="bibtex:misc" src-info="bibtex:line-29629" type="bibtex:misc">
		<names type="sharef:author">
			<name>International Telecommunication Union</name>
		</names>
		<date value="1988"/>
		<howpublished>ITU-T Recommendation X.200</howpublished>
		<field type="bibtex:index">OSI</field>
		<title type="sharef:primaryTitle">Reference Model of Open Systems Interconnection for CCITT Applications</title>
	</reference>
	<reference name="v90" src="bibtex:misc" src-info="bibtex:line-29637" type="bibtex:misc">
		<names type="sharef:author">
			<name>International Telecommunication Union</name>
		</names>
		<date value="1998-09"/>
		<howpublished>ITU-T Recommendation V.90</howpublished>
		<title type="sharef:primaryTitle">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>
		<field type="bibtex:topic">v90[1] pstn[0.8] modem[0.9]</field>
	</reference>
	<reference name="x208" src="bibtex:misc" src-info="bibtex:line-29646" type="bibtex:misc">
		<names type="sharef:author">
			<name>International Telecommunication Union</name>
		</names>
		<date value="1988"/>
		<howpublished>ITU-T Recommendation X.208</howpublished>
		<title type="sharef:primaryTitle">Specification of Abstract Syntax Notation One (ASN.1)</title>
		<field type="bibtex:topic">asn1[1]</field>
	</reference>
	<reference name="x209" src="bibtex:misc" src-info="bibtex:line-29654" type="bibtex:misc">
		<names type="sharef:author">
			<name>International Telecommunication Union</name>
		</names>
		<date value="1988"/>
		<howpublished>ITU-T Recommendation X.209</howpublished>
		<title type="sharef:primaryTitle">Specification of Basic Encoding Rules for Abstract Syntax Notation One (ASN.1)</title>
		<field type="bibtex:topic">asn1[0.9] ber[1]</field>
	</reference>
	<reference name="x219" src="bibtex:misc" src-info="bibtex:line-29662" type="bibtex:misc">
		<names type="sharef: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>
		<title type="sharef:primaryTitle">Remote Operations: Model, Notation and Service Definition</title>
	</reference>
	<reference name="x227" src="bibtex:misc" src-info="bibtex:line-29670" type="bibtex:misc">
		<names type="sharef:author">
			<name>International Telecommunication Union</name>
		</names>
		<date value="1988"/>
		<howpublished>ITU-T Recommendation X.227</howpublished>
		<field type="bibtex:index">ISO 8650</field>
		<title type="sharef:primaryTitle">Association Control Protocol Specification</title>
	</reference>
	<reference name="x229" src="bibtex:misc" src-info="bibtex:line-29678" type="bibtex:misc">
		<names type="sharef: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>
		<title type="sharef:primaryTitle">Remote Operations: Protocol Specification</title>
	</reference>
	<reference name="x400" src="bibtex:misc" src-info="bibtex:line-29686" type="bibtex:misc">
		<names type="sharef:author">
			<name>International Telecommunication Union</name>
		</names>
		<date value="1996-07"/>
		<howpublished>ITU-T Recommendation X.400</howpublished>
		<title type="sharef:primaryTitle">Message Handling System and Service Overview</title>
		<field type="bibtex:topic">x400[1]</field>
	</reference>
	<reference name="x419" src="bibtex:misc" src-info="bibtex:line-29695" type="bibtex:misc">
		<names type="sharef:author">
			<name>International Telecommunication Union</name>
		</names>
		<date value="1995-11"/>
		<howpublished>ITU-T Recommendation X.419</howpublished>
		<title type="sharef:primaryTitle">Information technology — Message Handling Systems (MHS) — Protocol specifications</title>
	</reference>
	<reference name="x500" src="bibtex:misc" src-info="bibtex:line-29703" type="bibtex:misc">
		<names type="sharef:author">
			<name>International Telecommunication Union</name>
		</names>
		<date value="1993-11"/>
		<howpublished>ITU-T Recommendation X.500</howpublished>
		<title type="sharef:primaryTitle">The Directory — Overview of Concepts, Models and Services</title>
	</reference>
	<reference name="x501" src="bibtex:misc" src-info="bibtex:line-29711" type="bibtex:misc">
		<names type="sharef:author">
			<name>International Telecommunication Union</name>
		</names>
		<date value="1993-11"/>
		<howpublished>ITU-T Recommendation X.501</howpublished>
		<title type="sharef:primaryTitle">The Directory — Models</title>
	</reference>
	<reference name="x509" src="bibtex:misc" src-info="bibtex:line-29719" type="bibtex:misc">
		<names type="sharef:author">
			<name>International Telecommunication Union</name>
		</names>
		<date value="1993-11"/>
		<howpublished>ITU-T Recommendation X.509</howpublished>
		<title type="sharef:primaryTitle">The Directory — Authentication framework</title>
	</reference>
	<reference name="x511" src="bibtex:misc" src-info="bibtex:line-29727" type="bibtex:misc">
		<names type="sharef:author">
			<name>International Telecommunication Union</name>
		</names>
		<date value="1993-11"/>
		<howpublished>ITU-T Recommendation X.511</howpublished>
		<title type="sharef:primaryTitle">The Directory — Abstract service definition</title>
	</reference>
	<reference name="x518" src="bibtex:misc" src-info="bibtex:line-29735" type="bibtex:misc">
		<names type="sharef:author">
			<name>International Telecommunication Union</name>
		</names>
		<date value="1993-11"/>
		<howpublished>ITU-T Recommendation X.518</howpublished>
		<title type="sharef:primaryTitle">The Directory — Procedures for distributed operations</title>
	</reference>
	<reference name="x519" src="bibtex:misc" src-info="bibtex:line-29743" type="bibtex:misc">
		<names type="sharef:author">
			<name>International Telecommunication Union</name>
		</names>
		<date value="1993-11"/>
		<howpublished>ITU-T Recommendation X.519</howpublished>
		<title type="sharef:primaryTitle">The Directory — Protocol specifications</title>
	</reference>
	<reference name="x520" src="bibtex:misc" src-info="bibtex:line-29751" type="bibtex:misc">
		<names type="sharef:author">
			<name>International Telecommunication Union</name>
		</names>
		<date value="1993-11"/>
		<howpublished>ITU-T Recommendation X.520</howpublished>
		<title type="sharef:primaryTitle">The Directory — Selected attribute types</title>
	</reference>
	<reference name="x521" src="bibtex:misc" src-info="bibtex:line-29759" type="bibtex:misc">
		<names type="sharef:author">
			<name>International Telecommunication Union</name>
		</names>
		<date value="1993-11"/>
		<howpublished>ITU-T Recommendation X.521</howpublished>
		<title type="sharef:primaryTitle">The Directory — Selected object classes</title>
	</reference>
	<reference name="x525" src="bibtex:misc" src-info="bibtex:line-29767" type="bibtex:misc">
		<names type="sharef:author">
			<name>International Telecommunication Union</name>
		</names>
		<date value="1993-11"/>
		<howpublished>ITU-T Recommendation X.525</howpublished>
		<title type="sharef:primaryTitle">The Directory — Replication</title>
	</reference>
	<reference name="x680" src="bibtex:misc" src-info="bibtex:line-29775" type="bibtex:misc">
		<names type="sharef: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 type="sharef:primaryTitle">Information Technology — Abstract Syntax Notation One (ASN.1): Specification of Basic Notation</title>
		<field type="bibtex:topic">asn1[1]</field>
		<field type="bibtex:updates">x208</field>
		<identifier type="sharef:uri" resourceType="application/pdf">http://www.itu.int/ITU-T/studygroups/com17/languages/X.680-0207.pdf</identifier>
	</reference>
	<reference name="x681" src="bibtex:misc" src-info="bibtex:line-29787" type="bibtex:misc">
		<names type="sharef:author">
			<name>International Telecommunication Union</name>
		</names>
		<date value="2002-07"/>
		<howpublished>ITU-T Recommendation X.681</howpublished>
		<title type="sharef:primaryTitle">Information Technology — Abstract Syntax Notation One (ASN.1): Information Object Specification</title>
		<field type="bibtex:topic">asn1[1]</field>
		<field type="bibtex:updates">x208</field>
		<identifier type="sharef:uri" resourceType="application/pdf">http://www.itu.int/ITU-T/studygroups/com17/languages/X.681-0207.pdf</identifier>
	</reference>
	<reference name="x682" src="bibtex:misc" src-info="bibtex:line-29798" type="bibtex:misc">
		<names type="sharef:author">
			<name>International Telecommunication Union</name>
		</names>
		<date value="2002-07"/>
		<howpublished>ITU-T Recommendation X.682</howpublished>
		<title type="sharef:primaryTitle">Information Technology — Abstract Syntax Notation One (ASN.1): Constraint Specification</title>
		<field type="bibtex:topic">asn1[1]</field>
		<field type="bibtex:updates">x208</field>
		<identifier type="sharef:uri" resourceType="application/pdf">http://www.itu.int/ITU-T/studygroups/com17/languages/X.682-0207.pdf</identifier>
	</reference>
	<reference name="x683" src="bibtex:misc" src-info="bibtex:line-29809" type="bibtex:misc">
		<names type="sharef:author">
			<name>International Telecommunication Union</name>
		</names>
		<date value="2002-07"/>
		<howpublished>ITU-T Recommendation X.683</howpublished>
		<title type="sharef:primaryTitle">Information Technology — Abstract Syntax Notation One (ASN.1): Parameterization of ASN.1 Specifications</title>
		<field type="bibtex:topic">asn1[1]</field>
		<field type="bibtex:updates">x208</field>
		<identifier type="sharef:uri" resourceType="application/pdf">http://www.itu.int/ITU-T/studygroups/com17/languages/X.683-0207.pdf</identifier>
	</reference>
	<reference name="x690" src="bibtex:misc" src-info="bibtex:line-29820" type="bibtex:misc">
		<names type="sharef: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 type="sharef:primaryTitle">Information Technology — ASN.1 Encoding Rules — Specification of Basic Encoding Rules (BER), Canonical Encoding Rules (CER), and Distinguished Encoding Rules (DER)</title>
		<field type="bibtex:topic">asn1[0.9] ber[1] cer[1] der[1]</field>
		<field type="bibtex:updates">x209</field>
		<identifier type="sharef:uri" resourceType="application/pdf">http://www.itu.int/ITU-T/studygroups/com17/languages/X.690-0207.pdf</identifier>
	</reference>
	<reference name="x691" src="bibtex:misc" src-info="bibtex:line-29832" type="bibtex:misc">
		<names type="sharef:author">
			<name>International Telecommunication Union</name>
		</names>
		<date value="2002-07"/>
		<howpublished>ITU-T Recommendation X.691</howpublished>
		<title type="sharef:primaryTitle">Information Technology — ASN.1 Encoding Rules — Specification of Packed Encoding Rules (PER)</title>
		<field type="bibtex:topic">asn1[0.9] per[1]</field>
		<identifier type="sharef:uri" resourceType="application/pdf">http://www.itu.int/ITU-T/studygroups/com17/languages/X.691-0207.pdf</identifier>
	</reference>
	<reference name="x692" src="bibtex:misc" src-info="bibtex:line-29842" type="bibtex:misc">
		<names type="sharef:author">
			<name>International Telecommunication Union</name>
		</names>
		<date value="2002-03"/>
		<howpublished>ITU-T Recommendation X.692</howpublished>
		<title type="sharef:primaryTitle">Information Technology — ASN.1 Encoding Rules — Specification of Encoding Control Notation (ECN)</title>
		<field type="bibtex:topic">asn1[0.9] ecn[1]</field>
		<identifier type="sharef:uri" resourceType="application/pdf">http://www.itu.int/ITU-T/studygroups/com17/languages/X.692-0203.pdf</identifier>
	</reference>
	<reference name="x693" src="bibtex:misc" src-info="bibtex:line-29852" type="bibtex:misc">
		<names type="sharef:author">
			<name>International Telecommunication Union</name>
		</names>
		<date value="2001-12"/>
		<howpublished>ITU-T Recommendation X.693</howpublished>
		<title type="sharef:primaryTitle">Information Technology — ASN.1 Encoding Rules — XML Encoding Rules (XER)</title>
		<field type="bibtex:topic">asn1[0.9] xer[1]</field>
		<identifier type="sharef:uri" resourceType="application/pdf">http://www.itu.int/ITU-T/studygroups/com17/languages/X.693-0112.pdf</identifier>
	</reference>
	<reference name="x694" src="bibtex:misc" src-info="bibtex:line-29862" type="bibtex:misc">
		<names type="sharef:author">
			<name>International Telecommunication Union</name>
		</names>
		<date value="2004-01"/>
		<howpublished>ITU-T Recommendation X.694</howpublished>
		<title type="sharef:primaryTitle">Information Technology — ASN.1 Encoding Rules: Mapping W3C XML Schema Definitions into ASN.1</title>
		<field type="bibtex:topic">asn1[0.9] xsd[0.8]</field>
		<identifier type="sharef:uri" resourceType="application/pdf">http://www.itu.int/ITU-T/studygroups/com17/languages/X694.pdf</identifier>
	</reference>
	<reference name="pkcs1" src="bibtex:manual" src-info="bibtex:line-29876" type="sharef:manual">
		<date value="1993-11"/>
		<address type="sharef:placePublished">Redwood City, California</address>
		<organization>RSA Laboratories</organization>
		<title type="sharef:primaryTitle">PKCS #1: RSA Encryption Standard</title>
		<field type="bibtex:topic">pkcs1[1] rsa[1]</field>
	</reference>
	<reference name="pkcs3" src="bibtex:manual" src-info="bibtex:line-29885" type="sharef:manual">
		<date value="1993-11"/>
		<address type="sharef:placePublished">Redwood City, California</address>
		<field type="bibtex:index">PKCS #3</field>
		<organization>RSA Laboratories</organization>
		<title type="sharef:primaryTitle">PKCS #3: Diffie-Hellman Key-Agreement Standard</title>
		<field type="bibtex:topic">diffiehellman[0.9]</field>
	</reference>
	<reference name="pkcs6" src="bibtex:manual" src-info="bibtex:line-29895" type="sharef:manual">
		<date value="1993-11"/>
		<address type="sharef:placePublished">Redwood City, California</address>
		<organization>RSA Laboratories</organization>
		<title type="sharef:primaryTitle">PKCS #6: Extended-Certificate Syntax Standard</title>
		<field type="bibtex:topic">pkcs6[1]</field>
	</reference>
	<reference name="pkcs7" src="bibtex:manual" src-info="bibtex:line-29904" type="sharef:manual">
		<date value="1997-05"/>
		<address type="sharef:placePublished">Redwood City, California</address>
		<organization>RSA Laboratories</organization>
		<title type="sharef:primaryTitle">PKCS #7: Cryptographic Message Syntax Standard</title>
		<field type="bibtex:topic">pkcs7[1]</field>
	</reference>
	<reference name="pkcs12" src="bibtex:manual" src-info="bibtex:line-29913" type="sharef:manual">
		<date value="1999-06"/>
		<address type="sharef:placePublished">Redwood City, California</address>
		<organization>RSA Laboratories</organization>
		<title type="sharef:primaryTitle">PKCS #12: Personal Information Exchange Syntax</title>
		<field type="bibtex:topic">pkcs12[1]</field>
	</reference>
	<reference name="xps" src="bibtex:misc" src-info="bibtex:line-29926" type="bibtex:misc">
		<names type="sharef:author">
			<name>Ecma International</name>
		</names>
		<date value="2008-11"/>
		<howpublished>Working Draft 1.3</howpublished>
		<title type="sharef:primaryTitle">XML Paper Specification — XPS Specification and Reference Guide</title>
		<field type="bibtex:topic">xps[1]</field>
		<identifier type="sharef:uri" resourceType="application/pdf">http://www.ecma-international.org/activities/XML%20Paper%20Specification/XPS%20Standard%20WD%201.3.pdf</identifier>
	</reference>
	<reference name="ecmascript" src="bibtex:misc" src-info="bibtex:line-29936" type="bibtex:misc">
		<names type="sharef:author">
			<name>Ecma International</name>
		</names>
		<date value="1999-12"/>
		<edition>3rd</edition>
		<howpublished>Standard ECMA-262</howpublished>
		<title type="sharef:primaryTitle">ECMAScript Language Specification</title>
		<field type="bibtex:topic">ecmascript[1]</field>
		<identifier type="sharef:uri" resourceType="text/html">http://www.ecma-international.org/publications/standards/ecma-262.htm</identifier>
	</reference>
	<reference name="ecmascript5th" src="bibtex:misc" src-info="bibtex:line-29947" type="bibtex:misc">
		<names type="sharef:author">
			<name>Ecma International</name>
		</names>
		<date value="2009-12"/>
		<edition>5th</edition>
		<howpublished>Standard ECMA-262</howpublished>
		<title type="sharef:primaryTitle">ECMAScript Language Specification</title>
		<field type="bibtex:topic">ecmascript[1]</field>
		<field type="bibtex:updates">ecmascript</field>
		<identifier type="sharef:uri" resourceType="text/html">http://www.ecma-international.org/publications/standards/Ecma-262.htm</identifier>
	</reference>
	<reference name="e4x" src="bibtex:misc" src-info="bibtex:line-29959" type="bibtex:misc">
		<names type="sharef:author">
			<name>Ecma International</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 type="sharef:primaryTitle">ECMAScript for XML (E4X) Specification</title>
		<identifier type="sharef:uri" resourceType="text/html">http://www.ecma-international.org/publications/standards/Ecma-357.htm</identifier>
	</reference>
	<reference name="ecma365" src="bibtex:misc" src-info="bibtex:line-29970" type="bibtex:misc">
		<names type="sharef:author">
			<name>Ecma International</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 type="sharef:primaryTitle">Data Interchange on 60 mm Read-Only ODC — Capacity: 1,8 Gbytes (UMD)</title>
		<identifier type="sharef:uri" resourceType="text/html">http://www.ecma-international.org/publications/standards/Ecma-365.htm</identifier>
	</reference>
	<reference name="exif21" src="bibtex:misc" src-info="bibtex:line-29985" type="bibtex:misc">
		<names type="sharef:author">
			<name>Japan Electronic Industry Development Association</name>
		</names>
		<date value="1998-06"/>
		<title type="sharef:primaryTitle">Digital Still Camera Image File Format Standard (Exchangeable Image File Format for Digital Still Cameras: EXIF) — Version 2.1</title>
		<field type="bibtex:topic">exif[1]</field>
	</reference>
	<reference name="exif22" src="bibtex:misc" src-info="bibtex:line-29993" type="bibtex:misc">
		<names type="sharef:author">
			<name>Japan Electronics and Information Technology Industries Association</name>
		</names>
		<date value="2002-04"/>
		<howpublished>JEITA CP-3451</howpublished>
		<title type="sharef:primaryTitle">Exchangeable Image File Format for Digital Still Cameras: EXIF Version 2.2</title>
		<field type="bibtex:topic">exif[1]</field>
		<field type="bibtex:updates">exif21</field>
	</reference>
	<reference name="wap99a" src="bibtex:misc" src-info="bibtex:line-30007" type="bibtex:misc">
		<names type="sharef:author">
			<name>WAP Forum</name>
		</names>
		<date value="1999-06"/>
		<address type="sharef:placePublished">Mountain View, California</address>
		<howpublished>WAP White Paper</howpublished>
		<title type="sharef:primaryTitle">Wireless Application Protocol</title>
		<field type="bibtex:topic">wap1[1]</field>
	</reference>
	<reference name="wap99b" src="bibtex:misc" src-info="bibtex:line-30017" type="bibtex:misc">
		<names type="sharef:author">
			<name>WAP Forum</name>
		</names>
		<date value="1999-06"/>
		<address type="sharef:placePublished">Mountain View, California</address>
		<title type="sharef:primaryTitle">WMLScript Specification</title>
		<field type="bibtex:topic">wmlscript[1]</field>
	</reference>
	<reference name="wap99c" src="bibtex:misc" src-info="bibtex:line-30026" type="bibtex:misc">
		<names type="sharef:author">
			<name>WAP Forum</name>
		</names>
		<date value="1999-06"/>
		<address type="sharef:placePublished">Mountain View, California</address>
		<title type="sharef:primaryTitle">WAP WML</title>
		<field type="bibtex:topic">wml[1]</field>
	</reference>
	<reference name="wap99d" src="bibtex:misc" src-info="bibtex:line-30035" type="bibtex:misc">
		<names type="sharef:author">
			<name>WAP Forum</name>
		</names>
		<date value="1999-06"/>
		<address type="sharef:placePublished">Mountain View, California</address>
		<title type="sharef:primaryTitle">WAP Binary XML Content Format</title>
		<field type="bibtex:topic">wml[0.7] wbxml[1]</field>
	</reference>
	<reference name="wap99e" src="bibtex:misc" src-info="bibtex:line-30044" type="bibtex:misc">
		<names type="sharef:author">
			<name>WAP Forum</name>
		</names>
		<date value="1999-05"/>
		<address type="sharef:placePublished">Mountain View, California</address>
		<field type="bibtex:index">WAP, WSP</field>
		<title type="sharef:primaryTitle">WAP WSP</title>
	</reference>
	<reference name="wap99f" src="bibtex:misc" src-info="bibtex:line-30053" type="bibtex:misc">
		<names type="sharef:author">
			<name>WAP Forum</name>
		</names>
		<date value="1999-06"/>
		<address type="sharef:placePublished">Mountain View, California</address>
		<field type="bibtex:index">WAP, WTP</field>
		<title type="sharef:primaryTitle">WAP WTP</title>
	</reference>
	<reference name="wap99g" src="bibtex:misc" src-info="bibtex:line-30062" type="bibtex:misc">
		<names type="sharef:author">
			<name>WAP Forum</name>
		</names>
		<date value="1999-02"/>
		<address type="sharef:placePublished">Mountain View, California</address>
		<field type="bibtex:index">WAP, WTLS</field>
		<title type="sharef:primaryTitle">WAP WTLS</title>
	</reference>
	<reference name="wap99h" src="bibtex:misc" src-info="bibtex:line-30071" type="bibtex:misc">
		<names type="sharef:author">
			<name>WAP Forum</name>
		</names>
		<date value="1999-05"/>
		<address type="sharef:placePublished">Mountain View, California</address>
		<field type="bibtex:index">WAP, WDP</field>
		<title type="sharef:primaryTitle">WAP WDP</title>
	</reference>
	<reference name="wap01a" src="bibtex:misc" src-info="bibtex:line-30080" type="bibtex:misc">
		<names type="sharef:author">
			<name>WAP Forum</name>
		</names>
		<date value="2001-08"/>
		<address type="sharef:placePublished">Mountain View, California</address>
		<title type="sharef:primaryTitle">Wireless Application Protocol — WAP 2.0 Technical White Paper</title>
		<field type="bibtex:topic">wap2[1]</field>
		<field type="bibtex:updates">wap99a</field>
	</reference>
	<reference name="wap01b" src="bibtex:misc" src-info="bibtex:line-30090" type="bibtex:misc">
		<names type="sharef:author">
			<name>WAP Forum</name>
		</names>
		<date value="2001-07"/>
		<address type="sharef:placePublished">Mountain View, California</address>
		<howpublished>WAP-210-WAPArch-20010712</howpublished>
		<title type="sharef:primaryTitle">Wireless Application Protocol — Architecture Specification</title>
		<field type="bibtex:topic">wap2[1]</field>
	</reference>
	<reference name="wap2locprot" src="bibtex:misc" src-info="bibtex:line-30100" type="bibtex:misc">
		<names type="sharef:author">
			<name>WAP Forum</name>
		</names>
		<date value="2001-09"/>
		<address type="sharef:placePublished">Mountain View, California</address>
		<howpublished>WAP-257-LOCPROT-20010912-a</howpublished>
		<title type="sharef:primaryTitle">Wireless Application Protocol — Location Protocols</title>
		<field type="bibtex:topic">wap2[1]</field>
	</reference>
	<reference name="wtai" src="bibtex:misc" src-info="bibtex:line-30110" type="bibtex:misc">
		<names type="sharef:author">
			<name>WAP Forum</name>
		</names>
		<date value="2001-07"/>
		<address type="sharef:placePublished">Mountain View, California</address>
		<howpublished>WAP-268-WTAI-20010715-d</howpublished>
		<title type="sharef:primaryTitle">WAP Wireless Telephony Application Interface</title>
		<field type="bibtex:topic">wtai[1]</field>
	</reference>
	<reference name="sdmipd" src="bibtex:misc" src-info="bibtex:line-30124" type="bibtex:misc">
		<names type="sharef:author">
			<name>Secure Digital Music Initiative</name>
		</names>
		<date value="1999-07"/>
		<howpublished>Document pdwg99070802</howpublished>
		<field type="bibtex:index">SDMI</field>
		<title type="sharef:primaryTitle">SDMI Portable Device Specification — Part 1, Version 1.0</title>
	</reference>
	<reference name="xtm10" src="bibtex:misc" src-info="bibtex:line-30137" type="bibtex:misc">
		<names type="sharef: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 type="sharef:primaryTitle">XML Topic Maps (XTM) 1.0</title>
		<field type="bibtex:topic">xtm[1]</field>
		<identifier type="sharef:uri" resourceType="text/html">http://www.topicmaps.org/xtm/1.0/xtm1-20010806.html</identifier>
	</reference>
	<reference name="smspp581" src="bibtex:misc" src-info="bibtex:line-30151" type="bibtex:misc">
		<names type="sharef: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 type="sharef:primaryTitle">Digital Cellular Telecommunications System (Phase 2+); Technical realization of the Short Message Service (SMS); Point-to-Point (PP)</title>
		<field type="bibtex:topic">sms[1]</field>
		<identifier type="sharef:uri">http://pda.etsi.org/pda/home.asp?wki_id=6822</identifier>
	</reference>
	<reference name="smspp610" src="bibtex:misc" src-info="bibtex:line-30161" type="bibtex:misc">
		<names type="sharef: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 type="sharef:primaryTitle">Digital Cellular Telecommunications System (Phase 2+); Technical realization of the Short Message Service (SMS); Point-to-Point (PP)</title>
		<field type="bibtex:topic">sms[1]</field>
		<field type="bibtex:updates">smspp581</field>
		<identifier type="sharef:uri">http://pda.etsi.org/pda/home.asp?wki_id=6491</identifier>
	</reference>
	<reference name="smspp730" src="bibtex:misc" src-info="bibtex:line-30172" type="bibtex:misc">
		<names type="sharef: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 type="sharef:primaryTitle">Digital Cellular Telecommunications System (Phase 2+); Technical realization of the Short Message Service (SMS); Point-to-Point (PP)</title>
		<field type="bibtex:topic">sms[1]</field>
		<field type="bibtex:updates">smspp610</field>
		<identifier type="sharef:uri">http://pda.etsi.org/pda/home.asp?wki_id=9942</identifier>
	</reference>
	<reference name="sms750" src="bibtex:misc" src-info="bibtex:line-30183" type="bibtex:misc">
		<names type="sharef: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 type="sharef:primaryTitle">3rd Generation Partnership Project; Technical Specification Group Terminals; Technical realization of the Short Message Service (SMS)</title>
		<field type="bibtex:topic">sms[1]</field>
		<field type="bibtex:updates">smspp730</field>
		<identifier type="sharef:uri">http://www.3gpp.org/ftp/Specs/archive/03_series/03.40/0340-750.zip</identifier>
	</reference>
	<reference name="smsalph530" src="bibtex:misc" src-info="bibtex:line-30194" type="bibtex:misc">
		<names type="sharef:author">
			<name>European Telecommunications Standards Institute</name>
		</names>
		<date value="1996-07"/>
		<howpublished>(GSM 03.38 version 5.3.0)</howpublished>
		<title type="sharef:primaryTitle">Digital Cellular Telecommunications System (Phase 2+); Alphabets and language-specific information</title>
		<field type="bibtex:topic">sms[0.9]</field>
		<identifier type="sharef:uri">http://pda.etsi.org/pda/home.asp?wki_id=4690</identifier>
	</reference>
	<reference name="smsalph720" src="bibtex:misc" src-info="bibtex:line-30204" type="bibtex:misc">
		<names type="sharef: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 type="sharef:primaryTitle">Digital Cellular Telecommunications System (Phase 2+); Alphabets and language-specific information</title>
		<field type="bibtex:topic">sms[0.9]</field>
		<field type="bibtex:updates">smsalph530</field>
		<identifier type="sharef:uri">http://www.3gpp.org/ftp/Specs/archive/03_series/03.38/0338-720.zip</identifier>
	</reference>
	<reference name="wsbpel20" src="bibtex:misc" src-info="bibtex:line-30219" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Diane</givenname>
				<surname>Jordan</surname>
			</person>
			<person>
				<givenname>John</givenname>
				<surname>Evdemon</surname>
			</person>
		</names>
		<date value="2007-04"/>
		<abstract>
			<richtext>
				<p>This document defines a language for specifying business process behavior based on Web Services. This language is called Web Services Business Process Execution Language (abbreviated to WS-BPEL in the rest of this document). Processes in WS-BPEL export and import functionality by using Web Service interfaces exclusively. Business processes can be described in two ways. Executable business processes model actual behavior of a participant in a business interaction. Abstract business processes are partially specified processes that are not intended to be executed. An Abstract Process may hide some of the required concrete operational details. Abstract Processes serve a descriptive role, with more than one possible use case, including observable behavior and process template. WS-BPEL is meant to be used to model the behavior of both Executable and Abstract Processes. WS-BPEL provides a language for the specification of Executable and Abstract business processes. By doing so, it extends the Web Services interaction model and enables it to support business transactions. WS-BPEL defines an interoperable integration model that should facilitate the expansion of automated process integration in both the intra-corporate and the business-to-business spaces.</p>
			</richtext>
		</abstract>
		<howpublished>OASIS Standard</howpublished>
		<title type="sharef:primaryTitle">Web Services Business Process Execution Language Version 2.0</title>
		<field type="bibtex:topic">wsbpel[1]</field>
		<identifier type="sharef:uri">http://docs.oasis-open.org/wsbpel/2.0/</identifier>
	</reference>
	<reference name="xrisyntax20" src="bibtex:misc" src-info="bibtex:line-30230" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Drummond</givenname>
				<surname>Reed</surname>
			</person>
			<person>
				<givenname>Dave</givenname>
				<surname>McAlpin</surname>
			</person>
		</names>
		<date value="2005-11"/>
		<abstract>
			<richtext>
				<p>This document is the normative technical specification for XRI generic syntax. For a non-normative introduction to the uses and features of XRIs, see Introduction to XRIs.</p>
			</richtext>
		</abstract>
		<howpublished>Organization for the Advancement of Structured Information Standards (OASIS), Committee Specification</howpublished>
		<title type="sharef:primaryTitle">Extensible Resource Identifier (XRI) Syntax V2.0</title>
		<field type="bibtex:topic">xri[1]</field>
		<identifier type="sharef:uri">http://www.oasis-open.org/committees/download.php/15376</identifier>
	</reference>
	<reference name="ubl10" src="bibtex:misc" src-info="bibtex:line-30241" type="bibtex:misc">
		<names type="sharef: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 type="sharef:primaryTitle">Universal Business Language 1.0</title>
		<field type="bibtex:topic">ubl[1]</field>
		<identifier type="sharef:uri">http://docs.oasis-open.org/ubl/cd-UBL-1.0/</identifier>
	</reference>
	<reference name="ubl20" src="bibtex:misc" src-info="bibtex:line-30251" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Jon</givenname>
				<surname>Bosak</surname>
			</person>
			<person>
				<givenname>Tim</givenname>
				<surname>McGrath</surname>
			</person>
			<person>
				<givenname>G. Ken</givenname>
				<surname>Holman</surname>
			</person>
		</names>
		<date value="2006-12"/>
		<howpublished>Organization for the Advancement of Structured Information Standards (OASIS), Standard</howpublished>
		<title type="sharef:primaryTitle">Universal Business Language v2.0</title>
		<field type="bibtex:topic">ubl[1]</field>
		<field type="bibtex:updates">ubl10</field>
		<identifier type="sharef:uri">http://docs.oasis-open.org/ubl/os-UBL-2.0/</identifier>
	</reference>
	<reference name="xmlcatalogs" src="bibtex:misc" src-info="bibtex:line-30262" type="bibtex:misc">
		<names type="sharef: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 type="sharef:primaryTitle">XML Catalogs</title>
		<field type="bibtex:topic">xmlcatalogs[1]</field>
		<identifier type="sharef:uri">http://www.oasis-open.org/committees/entity/specs</identifier>
	</reference>
	<reference name="calstable" src="bibtex:misc" src-info="bibtex:line-30273" type="bibtex:misc">
		<names type="sharef: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 type="sharef:primaryTitle">CALS Table Model Document Type Definition</title>
		<field type="bibtex:topic">calstable[1]</field>
		<identifier type="sharef:uri" resourceType="text/html">http://www.oasis-open.org/specs/a502.htm</identifier>
	</reference>
	<reference name="relaxng" src="bibtex:misc" src-info="bibtex:line-30284" type="bibtex:misc">
		<names type="sharef: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 type="sharef:primaryTitle">RELAX NG Specification</title>
		<field type="bibtex:topic">relaxng[1]</field>
		<identifier type="sharef:uri" resourceType="text/html">http://www.oasis-open.org/committees/relax-ng/spec-20011203.html</identifier>
	</reference>
	<reference name="relaxngcompact" src="bibtex:misc" src-info="bibtex:line-30294" type="bibtex:misc">
		<names type="sharef: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 type="sharef:primaryTitle">RELAX NG Compact Syntax</title>
		<field type="bibtex:topic">relaxng[1]</field>
		<identifier type="sharef:uri" resourceType="text/html">http://www.oasis-open.org/committees/relax-ng/compact-20021121.html</identifier>
	</reference>
	<reference name="uddi3" src="bibtex:misc" src-info="bibtex:line-30304" type="bibtex:misc">
		<names type="sharef: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 type="sharef:primaryTitle">UDDI Version 3.0.2</title>
		<field type="bibtex:topic">uddi[1]</field>
		<identifier type="sharef:uri" resourceType="text/html">http://uddi.org/pubs/uddi-v3.0.2-20041019.htm</identifier>
	</reference>
	<reference name="oasissoarm10" src="bibtex:misc" src-info="bibtex:line-30315" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>C. Matthew</givenname>
				<surname>MacKenzie</surname>
			</person>
			<person>
				<givenname>Ken</givenname>
				<surname>Laskey</surname>
			</person>
			<person>
				<givenname>Francis</givenname>
				<surname>McCabe</surname>
			</person>
			<person>
				<givenname>Peter F.</givenname>
				<surname>Brown</surname>
			</person>
			<person>
				<givenname>Rebekah</givenname>
				<surname>Metz</surname>
			</person>
		</names>
		<date value="2006-10"/>
		<abstract>
			<richtext>
				<p>This Reference Model for Service Oriented Architecture is an abstract framework for understanding significant entities and relationships between them within a service-oriented environment, and for the development of consistent standards or specifications supporting that environment. It is based on unifying concepts of SOA and may be used by architects developing specific service oriented architectures or in training and explaining SOA. A reference model is not directly tied to any standards, technologies or other concrete implementation details. It does seek to provide a common semantics that can be used unambiguously across and between different implementations. The relationship between the Reference Model and particular architectures, technologies and other aspects of SOA is illustrated in Figure 1. While service-orientation may be a popular concept found in a broad variety of applications, this reference model focuses on the field of software architecture. The concepts and relationships described may apply to other "service" environments; however, this specification makes no attempt to completely account for use outside of the software domain.</p>
			</richtext>
		</abstract>
		<howpublished>Organization for the Advancement of Structured Information Standards, OASIS Standard</howpublished>
		<title type="sharef:primaryTitle">Reference Model for Service Oriented Architecture 1.0</title>
		<field type="bibtex:topic">soa[1]</field>
		<identifier type="sharef:uri" resourceType="application/pdf">http://docs.oasis-open.org/soa-rm/v1.0/soa-rm.pdf</identifier>
	</reference>
	<reference name="webapplications10" src="bibtex:misc" src-info="bibtex:line-30330" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Ian</givenname>
				<surname>Hickson</surname>
			</person>
		</names>
		<date value="2007-09"/>
		<abstract>
			<richtext>
				<p>This specification introduces features to HTML and the DOM that ease the authoring of Web-based applications. Additions include the context menus, a direct-mode graphics canvas, inline popup windows, and server-sent events.</p>
			</richtext>
		</abstract>
		<howpublished>Web Hypertext Application Technology Working Group, Working Draft</howpublished>
		<title type="sharef:primaryTitle">Web Applications 1.0</title>
		<identifier type="sharef:uri">http://www.whatwg.org/specs/web-apps/current-work/</identifier>
	</reference>
	<reference name="webforms20" src="bibtex:misc" src-info="bibtex:line-30340" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Ian</givenname>
				<surname>Hickson</surname>
			</person>
		</names>
		<date value="2006-10"/>
		<abstract>
			<richtext>
				<p>This specification defines Web Forms 2.0, an extension to the forms features found in HTML 4's Forms chapter and the corresponding DOM2 HTML interfaces. Web Forms 2.0 applies to both HTML and XHTML user agents. It provides new strongly-typed input fields, new attributes for defining constraints, a repeating model for declarative repeating of form sections, new DOM interfaces, new DOM events for validation and dependency tracking, and XML submission and initialization of forms. It also standardises and codifies existing practice in areas that have not been previously documented, and clarifies some of the interactions of HTML form controls and CSS. HTML 4, XHTML 1.1, and the DOM are thus extended in a manner that has a clear migration path from existing HTML forms, leveraging the knowledge authors have built up with their experience with HTML so far.</p>
			</richtext>
		</abstract>
		<howpublished>Web Hypertext Application Technology Working Group, Working Draft</howpublished>
		<title type="sharef:primaryTitle">Web Forms 2.0</title>
		<identifier type="sharef:uri">http://www.whatwg.org/specs/web-forms/current-work/</identifier>
	</reference>
	<reference name="webcontrols10" src="bibtex:misc" src-info="bibtex:line-30350" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Ian</givenname>
				<surname>Hickson</surname>
			</person>
		</names>
		<date value="2004-11"/>
		<abstract>
			<richtext>
				<p>This document is the result of a loose collaboration between interested parties in the context of the Web hypertext application technology working group. To become involved in the development of this document, please send comments to the address given above. Your input will be taken into consideration. This is a working draft and may therefore be updated, replaced or rendered obsolete by other documents at any time. It is inappropriate to use Working Drafts as reference material or to cite them as other than "work in progress". This draft may contain namespaces that use the data: URI scheme. These are temporary and will be changed before this specification is ready to be implemented.</p>
			</richtext>
		</abstract>
		<howpublished>Web Hypertext Application Technology Working Group, Working Draft</howpublished>
		<title type="sharef:primaryTitle">Web Controls 1.0</title>
		<identifier type="sharef:uri">http://www.whatwg.org/specs/web-controls/current-work/</identifier>
	</reference>
	<reference name="exlog" src="bibtex:misc" src-info="bibtex:line-30364" type="bibtex:misc">
		<names type="sharef: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 type="sharef:primaryTitle">Extended Log File Format</title>
		<identifier type="sharef:uri">http://www.w3.org/TR/WD-logfile-960323</identifier>
	</reference>
	<reference name="webarch" src="bibtex:misc" src-info="bibtex:line-30374" type="bibtex:misc">
		<names type="sharef: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 type="sharef:primaryTitle">Architecture of the World Wide Web, Volume One</title>
		<field type="bibtex:topic">www[1]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2004/REC-webarch-20041215</identifier>
	</reference>
	<reference name="fry99b" src="bibtex:misc" src-info="bibtex:line-30385" type="bibtex:misc">
		<names type="sharef: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 type="sharef:primaryTitle">Editing the Web: Detecting the Lost Update Problem Using Unreserved Checkout</title>
		<field type="bibtex:topic">webdav[0.8]</field>
		<identifier type="sharef:uri">http://www.w3.org/1999/04/Editing/01</identifier>
	</reference>
	<reference name="itsreq" src="bibtex:misc" src-info="bibtex:line-30396" type="bibtex:misc">
		<names type="sharef: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 type="sharef:primaryTitle">Internationalization and Localization Markup Requirements</title>
		<field type="bibtex:topic">i18n[0.8] l10n[0.8] its[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2006/WD-itsreq-20060518</identifier>
	</reference>
	<reference name="its" src="bibtex:misc" src-info="bibtex:line-30407" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Christian</givenname>
				<surname>Lieske</surname>
			</person>
			<person>
				<givenname>Felix</givenname>
				<surname>Sasaki</surname>
			</person>
		</names>
		<date value="2007-04"/>
		<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, Recommendation REC-its-20070403</howpublished>
		<title type="sharef:primaryTitle">Internationalization Tag Set (ITS) Version 1.0</title>
		<field type="bibtex:topic">its[1] i18n[0.9] l10n[0.9]</field>
		<field type="bibtex:updates">itsreq</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2007/REC-its-20070403</identifier>
	</reference>
	<reference name="i18nbp" src="bibtex:misc" src-info="bibtex:line-30419" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Yves</givenname>
				<surname>Savourel</surname>
			</person>
			<person>
				<givenname>Jirka</givenname>
				<surname>Kosek</surname>
			</person>
			<person>
				<givenname>Richard</givenname>
				<surname>Ishida</surname>
			</person>
		</names>
		<date value="2008-02"/>
		<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.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Note NOTE-xml-i18n-bp-20080213</howpublished>
		<title type="sharef:primaryTitle">Best Practices for XML Internationalization</title>
		<field type="bibtex:topic">i18n[0.9] its[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2008/NOTE-xml-i18n-bp-20080213</identifier>
	</reference>
	<reference name="ltli" src="bibtex:misc" src-info="bibtex:line-30430" type="bibtex:misc">
		<names type="sharef: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 type="sharef:primaryTitle">Language Tags and Locale Identifiers for the World Wide Web</title>
		<field type="bibtex:topic">i18n[0.9] l10n[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2006/WD-ltli-20060612</identifier>
	</reference>
	<reference name="i18nframework" src="bibtex:misc" src-info="bibtex:line-30441" type="bibtex:misc">
		<names type="sharef: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 type="sharef:primaryTitle">Framework Document for i18n Guidelines 1.0</title>
		<field type="bibtex:topic">i18n[1]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2003/WD-i18n-guide-framework-20030417</identifier>
	</reference>
	<reference name="wsi18n" src="bibtex:misc" src-info="bibtex:line-30452" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Addison P.</givenname>
				<surname>Phillips</surname>
			</person>
			<person>
				<givenname>Mary</givenname>
				<surname>Trumble</surname>
			</person>
			<person>
				<givenname>Felix</givenname>
				<surname>Sasaki</surname>
			</person>
		</names>
		<date value="2008-04"/>
		<abstract>
			<richtext>
				<p>This document (hereafter referred to as "WS-I18N") describes enhancements to SOAP messaging to provide internationalized and localized operations using locale and international preferences. These mechanisms can be used to accommodate a wide variety of development models for international usage. 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 services 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 a Web services interaction, 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-20080415</howpublished>
		<title type="sharef:primaryTitle">Web Services Internationalization (WS-I18N)</title>
		<field type="bibtex:topic">i18n[0.9] soap[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2008/WD-ws-i18n-20080415</identifier>
	</reference>
	<reference name="i18nhtmltech" src="bibtex:misc" src-info="bibtex:line-30463" type="bibtex:misc">
		<names type="sharef: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 type="sharef:primaryTitle">Authoring Techniques for XHTML &amp; HTML Internationalization 1.0</title>
		<field type="bibtex:topic">i18n[0.9] html[0.9] xhtml[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2003/WD-i18n-html-tech-20031009</identifier>
	</reference>
	<reference name="i18nhtmltechbidi" src="bibtex:misc" src-info="bibtex:line-30474" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Richard</givenname>
				<surname>Ishida</surname>
			</person>
		</names>
		<date value="2009-09"/>
		<abstract>
			<richtext>
				<p>This document provides advice for the use of HTML markup and CSS style sheets to create pages for languages that use right-to-left scripts, such as Arabic, Hebrew, Persian, Thaana, Urdu, etc. It explains how to create content in right-to-left scripts that builds on but goes beyond the Unicode bidirectional algorithm, as well as how to prepare content for localization into right-to-left scripts.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Note NOTE-i18n-html-tech-bidi-20090908</howpublished>
		<title type="sharef:primaryTitle">Authoring HTML: Handling Right-to-left Scripts</title>
		<field type="bibtex:topic">i18n[0.9] html[0.9] xhtml[0.9]</field>
		<field type="bibtex:updates">i18nhtmltech</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2009/NOTE-i18n-html-tech-bidi-20090908</identifier>
	</reference>
	<reference name="htmlbidi" src="bibtex:misc" src-info="bibtex:line-30486" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Aharon</givenname>
				<surname>Lanin</surname>
			</person>
		</names>
		<date value="2010-03"/>
		<abstract>
			<richtext>
				<p>Authoring a web app that needs to support both right-to-left and left-to-right interfaces, or to take as input and display both left-to-right and right-to-left data, usually presents a number of challenges that make it an especially laborious and bug-prone task. Some of these are due to browser bugs, but some can be traced to a gap in the specification of the bidirectional aspects of a given HTML feature. And some of these challenges could be greatly simplified by adding a few strategically placed new HTML features. This document proposes fixes for some of the most repetitive pain points.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-html-bidi-20100304</howpublished>
		<title type="sharef:primaryTitle">Additional Requirements for Bidi in HTML</title>
		<field type="bibtex:topic">i18n[0.9] html[0.9] xhtml[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2010/WD-html-bidi-20100304</identifier>
	</reference>
	<reference name="jlreq" src="bibtex:misc" src-info="bibtex:line-30497" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Yasuhiro</givenname>
				<surname>Anan</surname>
			</person>
			<person>
				<givenname>Hiroyuki</givenname>
				<surname>Chiba</surname>
			</person>
			<person>
				<givenname>Junsaburo</givenname>
				<surname>Edamoto</surname>
			</person>
			<person>
				<givenname>Richard</givenname>
				<surname>Ishida</surname>
			</person>
			<person>
				<givenname>Keiichiro</givenname>
				<surname>Ishino</surname>
			</person>
			<person>
				<givenname>Tatsuo</givenname>
				<surname>Kobayashi</surname>
			</person>
			<person>
				<givenname>Toshi</givenname>
				<surname>Kobayashi</surname>
			</person>
			<person>
				<givenname>Kenzou</givenname>
				<surname>Onozawa</surname>
			</person>
			<person>
				<givenname>Felix</givenname>
				<surname>Sasaki</surname>
			</person>
		</names>
		<date value="2009-06"/>
		<abstract>
			<richtext>
				<p>This document describes requirements for general Japanese layout realized with technologies like CSS, SVG and XSL-FO. The document is mainly based on a standard for Japanese layout, JIS X 4051, however, it also addresses areas which are not covered by JIS X 4051.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Note NOTE-jlreq-20090604</howpublished>
		<title type="sharef:primaryTitle">Requirements for Japanese Text Layout</title>
		<field type="bibtex:topic">i18n[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2009/NOTE-jlreq-20090604</identifier>
	</reference>
	<reference name="i18nhtmltechchar" src="bibtex:misc" src-info="bibtex:line-30508" type="bibtex:misc">
		<names type="sharef: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 type="sharef:primaryTitle">Authoring Techniques for XHTML &amp; HTML Internationalization: Characters and Encodings 1.0</title>
		<field type="bibtex:topic">i18n[0.9] html[0.9] xhtml[0.9]</field>
		<field type="bibtex:updates">i18nhtmltech</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2004/WD-i18n-html-tech-char-20040509</identifier>
	</reference>
	<reference name="i18nhtmltechlang" src="bibtex:misc" src-info="bibtex:line-30520" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Richard</givenname>
				<surname>Ishida</surname>
			</person>
		</names>
		<date value="2007-04"/>
		<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.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Note NOTE-i18n-html-tech-lang-20070412</howpublished>
		<title type="sharef:primaryTitle">Internationalization Best Practices: Specifying Language in XHTML &amp; HTML Content</title>
		<field type="bibtex:topic">i18n[0.9] html[0.9] xhtml[0.9]</field>
		<field type="bibtex:updates">i18nhtmltech</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2007/NOTE-i18n-html-tech-lang-20070412</identifier>
	</reference>
	<reference name="dfaui" src="bibtex:misc" src-info="bibtex:line-30532" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Arthur</givenname>
				<surname>Barstow</surname>
			</person>
		</names>
		<date value="2007-09"/>
		<abstract>
			<richtext>
				<p>The Charter of the Web Application Formats Working Group includes a deliverable titled Specification of a declarative format for applications and user interfaces. This document includes the status of this deliverable and a recommendation that the Working Group stop formal work on this deliverable and consider this Note as the one and only publication for this deliverable. This Note also includes some potential options if W3C Members choose to do related work.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Note NOTE-dfaui-20070912</howpublished>
		<title type="sharef:primaryTitle">Declarative Formats for Applications and User Interfaces</title>
		<identifier type="sharef:uri">http://www.w3.org/TR/2007/NOTE-dfaui-20070912</identifier>
	</reference>
	<reference name="wsdl12" src="bibtex:misc" src-info="bibtex:line-30542" type="bibtex:misc">
		<names type="sharef: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"/>
		<abstract>
			<richtext>
				<p>This document describes the Web Services Description Language (WSDL) Version 1.2, 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.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-wsdl12-20030611</howpublished>
		<title type="sharef:primaryTitle">Web Services Description Language (WSDL) Version 1.2 Part 1: Core Language</title>
		<field type="bibtex:topic">wsdl[1]</field>
		<field type="bibtex:updates">wsdl11</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2003/WD-wsdl12-20030611</identifier>
	</reference>
	<reference name="wsdl20primer" src="bibtex:misc" src-info="bibtex:line-30554" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>David</givenname>
				<surname>Booth</surname>
			</person>
			<person>
				<givenname>Canyang Kevin</givenname>
				<surname>Liu</surname>
			</person>
		</names>
		<date value="2007-06"/>
		<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, Recommendation REC-wsdl20-primer-20070626</howpublished>
		<title type="sharef:primaryTitle">Web Services Description Language (WSDL) Version 2.0 Part 0: Primer</title>
		<field type="bibtex:topic">wsdl[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2007/REC-wsdl20-primer-20070626</identifier>
	</reference>
	<reference name="wsdl2" src="bibtex:misc" src-info="bibtex:line-30565" type="bibtex:misc">
		<names type="sharef: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="2007-06"/>
		<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, Recommendation REC-wsdl20-20070626</howpublished>
		<title type="sharef:primaryTitle">Web Services Description Language (WSDL) Version 2.0 Part 1: Core Language</title>
		<field type="bibtex:topic">wsdl[1]</field>
		<field type="bibtex:updates">wsdl12</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2007/REC-wsdl20-20070626</identifier>
	</reference>
	<reference name="wsdl20rdf" src="bibtex:misc" src-info="bibtex:line-30577" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Jacek</givenname>
				<surname>Kopecký</surname>
			</person>
		</names>
		<date value="2007-06"/>
		<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, Note NOTE-wsdl20-rdf-20070626</howpublished>
		<title type="sharef:primaryTitle">Web Services Description Language (WSDL) Version 2.0: RDF Mapping</title>
		<field type="bibtex:topic">wsdl[0.9] rdf[0.8]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2007/NOTE-wsdl20-rdf-20070626</identifier>
	</reference>
	<reference name="sawsdlguide" src="bibtex:misc" src-info="bibtex:line-30588" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Rama</givenname>
				<surname>Akkiraju</surname>
			</person>
			<person>
				<givenname>Brahmananda</givenname>
				<surname>Sapkota</surname>
			</person>
		</names>
		<date value="2007-08"/>
		<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, Note NOTE-sawsdl-guide-20070828</howpublished>
		<title type="sharef:primaryTitle">Semantic Annotations for WSDL and XML Schema — Usage Guide</title>
		<field type="bibtex:topic">wsdl[0.8] sawsdl[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2007/NOTE-sawsdl-guide-20070828</identifier>
	</reference>
	<reference name="sawsdl" src="bibtex:misc" src-info="bibtex:line-30599" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Joel</givenname>
				<surname>Farrell</surname>
			</person>
			<person>
				<givenname>Holger</givenname>
				<surname>Lausen</surname>
			</person>
		</names>
		<date value="2007-08"/>
		<abstract>
			<richtext>
				<p>This document defines a set of extension attributes for the Web Services Description Language and XML Schema definition language that allows description of additional semantics of WSDL components. The specification defines how semantic annotation is accomplished using references to semantic models, e.g. ontologies. Semantic Annotations for WSDL and XML Schema (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 and XML Schema components using annotations.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Recommendation REC-sawsdl-20070828</howpublished>
		<title type="sharef:primaryTitle">Semantic Annotations for WSDL and XML Schema</title>
		<field type="bibtex:topic">wsdl[0.8] sawsdl[1]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2007/REC-sawsdl-20070828</identifier>
	</reference>
	<reference name="altschemalangs" src="bibtex:misc" src-info="bibtex:line-30610" type="bibtex:misc">
		<names type="sharef: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 type="sharef:primaryTitle">Discussion of Alternative Schema Languages and Type System Support in WSDL 2.0</title>
		<field type="bibtex:topic">wsdl[0.9]</field>
		<field type="bibtex:updates">wsdl12</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2005/NOTE-wsdl20-altschemalangs-20050817</identifier>
	</reference>
	<reference name="wsdl12bindings" src="bibtex:misc" src-info="bibtex:line-30622" type="bibtex:misc">
		<names type="sharef: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 type="sharef:primaryTitle">Web Services Description Language (WSDL) Version 1.2 Part 3: Bindings</title>
		<field type="bibtex:topic">wsdl[0.9]</field>
		<field type="bibtex:updates">wsdl11</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2003/WD-wsdl12-bindings-20030611</identifier>
	</reference>
	<reference name="wsdl20soap11binding" src="bibtex:misc" src-info="bibtex:line-30633" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Asir S.</givenname>
				<surname>Vedamuthu</surname>
			</person>
		</names>
		<date value="2007-06"/>
		<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, Note NOTE-wsdl20-soap11-binding-20070626</howpublished>
		<title type="sharef:primaryTitle">Web Services Description Language (WSDL) Version 2.0 SOAP 1.1 Binding</title>
		<field type="bibtex:topic">wsdl[0.9] soap[0.8]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2007/NOTE-wsdl20-soap11-binding-20070626</identifier>
	</reference>
	<reference name="wsdl20bindings" src="bibtex:misc" src-info="bibtex:line-30644" type="bibtex:misc">
		<names type="sharef: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 type="sharef:primaryTitle">Web Services Description Language (WSDL) Version 2.0 Part 3: Bindings</title>
		<field type="bibtex:topic">wsdl[0.9] soap[0.8]</field>
		<field type="bibtex:updates">wsdl12bindings</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2004/WD-wsdl20-bindings-20040803</identifier>
	</reference>
	<reference name="wsdl20adjuncts" src="bibtex:misc" src-info="bibtex:line-30656" type="bibtex:misc">
		<names type="sharef: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="2007-06"/>
		<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, Recommendation REC-wsdl20-adjuncts-20070626</howpublished>
		<title type="sharef:primaryTitle">Web Services Description Language (WSDL) Version 2.0 Part 2: Adjuncts</title>
		<field type="bibtex:topic">wsdl[0.9]</field>
		<field type="bibtex:updates">wsdl20bindings wsdl2extensions</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2007/REC-wsdl20-adjuncts-20070626</identifier>
	</reference>
	<reference name="wsdl12patterns" src="bibtex:misc" src-info="bibtex:line-30668" type="bibtex:misc">
		<names type="sharef: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 type="sharef:primaryTitle">Web Services Description Language (WSDL) Version 1.2 Part 2: Message Patterns</title>
		<field type="bibtex:topic">wsdl[0.9]</field>
		<field type="bibtex:updates">wsdl11</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2003/WD-wsdl12-patterns-20030611</identifier>
	</reference>
	<reference name="wsdl20patterns" src="bibtex:misc" src-info="bibtex:line-30679" type="bibtex:misc">
		<names type="sharef: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 type="sharef:primaryTitle">Web Services Description Language (WSDL) Version 2.0 Part 2: Message Patterns</title>
		<field type="bibtex:topic">wsdl[0.9]</field>
		<field type="bibtex:updates">wsdl12patterns</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2004/WD-wsdl20-patterns-20040326</identifier>
	</reference>
	<reference name="wsdl20additionalmeps" src="bibtex:misc" src-info="bibtex:line-30691" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Amelia A.</givenname>
				<surname>Lewis</surname>
			</person>
		</names>
		<date value="2007-06"/>
		<abstract>
			<richtext>
				<p>This specification defines additional message exchange patterns (MEPs) to be used in WSDL 2.0 and are provided as examples of the extensibility of WSDL 2.0.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Note NOTE-wsdl20-additional-meps-20070626</howpublished>
		<title type="sharef:primaryTitle">Web Services Description Language (WSDL) Version 2.0: Additional MEPs</title>
		<field type="bibtex:topic">wsdl[0.9]</field>
		<field type="bibtex:updates">wsdl12patterns</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2007/NOTE-wsdl20-additional-meps-20070626</identifier>
	</reference>
	<reference name="wsdl2extensions" src="bibtex:misc" src-info="bibtex:line-30703" type="bibtex:misc">
		<names type="sharef: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 type="sharef:primaryTitle">Web Services Description Language (WSDL) Version 2.0 Part 2: Predefined Extensions</title>
		<field type="bibtex:topic">wsdl[0.9] wsdlmep[0.9]</field>
		<field type="bibtex:updates">wsdl20patterns</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2004/WD-wsdl20-extensions-20040803</identifier>
	</reference>
	<reference name="wsdl11" src="bibtex:misc" src-info="bibtex:line-30715" type="bibtex:misc">
		<names type="sharef: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 type="sharef:primaryTitle">Web Services Description Language (WSDL) 1.1</title>
		<field type="bibtex:topic">wsdl[1]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2001/NOTE-wsdl-20010315</identifier>
	</reference>
	<reference name="wsdl11elementidentifiers" src="bibtex:misc" src-info="bibtex:line-30726" type="bibtex:misc">
		<names type="sharef: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-07"/>
		<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, Note NOTE-wsdl11elementidentifiers-20070720</howpublished>
		<title type="sharef:primaryTitle">WSDL 1.1 Element Identifiers</title>
		<field type="bibtex:topic">wsdl[1]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2007/NOTE-wsdl11elementidentifiers-20070720</identifier>
	</reference>
	<reference name="wsi18nreq" src="bibtex:misc" src-info="bibtex:line-30737" type="bibtex:misc">
		<names type="sharef: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 type="sharef:primaryTitle">Requirements for the Internationalization of Web Services</title>
		<field type="bibtex:topic">i18n[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2004/NOTE-ws-i18n-req-20041116</identifier>
	</reference>
	<reference name="wschorreqs" src="bibtex:misc" src-info="bibtex:line-30748" type="bibtex:misc">
		<names type="sharef: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 type="sharef:primaryTitle">Web Services Choreography Requirements 1.0</title>
		<identifier type="sharef:uri">http://www.w3.org/TR/2004/WD-ws-chor-reqs-20040311</identifier>
	</reference>
	<reference name="wschormodel" src="bibtex:misc" src-info="bibtex:line-30758" type="bibtex:misc">
		<names type="sharef: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 type="sharef:primaryTitle">WS Choreography Model Overview</title>
		<identifier type="sharef:uri">http://www.w3.org/TR/2004/WD-ws-chor-model-20040324</identifier>
	</reference>
	<reference name="wsci10" src="bibtex:misc" src-info="bibtex:line-30768" type="bibtex:misc">
		<names type="sharef: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 type="sharef:primaryTitle">Web Service Choreography Interface (WSCI) 1.0</title>
		<field type="bibtex:topic">wsci[1]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2002/NOTE-wsci-20020808</identifier>
	</reference>
	<reference name="wscdl10" src="bibtex:misc" src-info="bibtex:line-30779" type="bibtex:misc">
		<names type="sharef: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 Recommendation CR-ws-cdl-10-20051109</howpublished>
		<title type="sharef:primaryTitle">Web Services Choreography Description Language Version 1.0</title>
		<field type="bibtex:topic">wscdl[1]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2005/CR-ws-cdl-10-20051109</identifier>
	</reference>
	<reference name="wscdl10primer" src="bibtex:misc" src-info="bibtex:line-30790" type="bibtex:misc">
		<names type="sharef: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 type="sharef:primaryTitle">Web Services Choreography Description Language: Primer</title>
		<field type="bibtex:topic">wscdl[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2006/WD-ws-cdl-10-primer-20060619</identifier>
	</reference>
	<reference name="wscl10" src="bibtex:misc" src-info="bibtex:line-30801" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Arindam</givenname>
				<surname>Banerji</surname>
			</person>
			<person>
				<givenname>Claudio</givenname>
				<surname>Bartolini</surname>
			</person>
			<person>
				<givenname>Dorothea</givenname>
				<surname>Beringer</surname>
			</person>
			<person>
				<givenname>Venkatesh</givenname>
				<surname>Chopella</surname>
			</person>
			<person>
				<givenname>Kannan</givenname>
				<surname>Govindarajan</surname>
			</person>
			<person>
				<givenname>Alan</givenname>
				<surname>Karp</surname>
			</person>
			<person>
				<givenname>Harumi</givenname>
				<surname>Kuno</surname>
			</person>
			<person>
				<givenname>Mike</givenname>
				<surname>Lemon</surname>
			</person>
			<person>
				<givenname>Gregory</givenname>
				<surname>Pogossiants</surname>
			</person>
			<person>
				<givenname>Shamik</givenname>
				<surname>Sharma</surname>
			</person>
			<person>
				<givenname>Scott</givenname>
				<surname>Williams</surname>
			</person>
		</names>
		<date value="2002-03"/>
		<howpublished>World Wide Web Consortium, Note NOTE-wscl10-20020314</howpublished>
		<title type="sharef:primaryTitle">Web Services Conversation Language (WSCL) 1.0</title>
		<field type="bibtex:topic">wscl[1]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2002/NOTE-wscl10-20020314</identifier>
	</reference>
	<reference name="wstransfer" src="bibtex:misc" src-info="bibtex:line-30811" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Doug</givenname>
				<surname>Davis</surname>
			</person>
			<person>
				<givenname>Ashok</givenname>
				<surname>Malhotra</surname>
			</person>
			<person>
				<givenname>Katy</givenname>
				<surname>Warr</surname>
			</person>
			<person>
				<givenname>Wu</givenname>
				<surname>Chou</surname>
			</person>
		</names>
		<date value="2010-08"/>
		<abstract>
			<richtext>
				<p>This specification describes a general SOAP-based protocol for accessing XML representations of Web service-based resources.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-ws-transfer-20100805</howpublished>
		<title type="sharef:primaryTitle">Web Services Transfer (WS-Transfer)</title>
		<field type="bibtex:topic">wstransfer[1]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2010/WD-ws-transfer-20100805</identifier>
	</reference>
	<reference name="wsresourcetransfer" src="bibtex:misc" src-info="bibtex:line-30822" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Doug</givenname>
				<surname>Davis</surname>
			</person>
			<person>
				<givenname>Ashok</givenname>
				<surname>Malhotra</surname>
			</person>
			<person>
				<givenname>Katy</givenname>
				<surname>Warr</surname>
			</person>
			<person>
				<givenname>Wu</givenname>
				<surname>Chou</surname>
			</person>
		</names>
		<date value="2010-07"/>
		<abstract>
			<richtext>
				<p>This specification defines extensions to WS-Transfer primarily to provide fragment-based access to resources.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Note NOTE-ws-resource-transfer-20100713</howpublished>
		<title type="sharef:primaryTitle">Web Services Resource Transfer (WS-RT)</title>
		<field type="bibtex:topic">wsrt[1] wstransfer[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2010/NOTE-ws-resource-transfer-20100713</identifier>
	</reference>
	<reference name="wsfragment" src="bibtex:misc" src-info="bibtex:line-30833" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Doug</givenname>
				<surname>Davis</surname>
			</person>
			<person>
				<givenname>Ashok</givenname>
				<surname>Malhotra</surname>
			</person>
			<person>
				<givenname>Katy</givenname>
				<surname>Warr</surname>
			</person>
			<person>
				<givenname>Wu</givenname>
				<surname>Chou</surname>
			</person>
		</names>
		<date value="2010-08"/>
		<abstract>
			<richtext>
				<p>This specification defines how metadata associated with a Web service endpoint can be represented as WS-Transfer resources or HTTP resources, how metadata can be embedded in WS-Addressing endpoint references, and how metadata could be retrieved from a metadata resource, and how metadata associated with implicit features can be advertised.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-ws-fragment-20100805</howpublished>
		<title type="sharef:primaryTitle">Web Services Fragment (WS-Fragment)</title>
		<field type="bibtex:topic">wsfragment[1] wstransfer[0.9]</field>
		<field type="bibtex:updates">wsresourcetransfer</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2010/WD-ws-fragment-20100805</identifier>
	</reference>
	<reference name="wsmetadataexchange" src="bibtex:misc" src-info="bibtex:line-30845" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Doug</givenname>
				<surname>Davis</surname>
			</person>
			<person>
				<givenname>Ashok</givenname>
				<surname>Malhotra</surname>
			</person>
			<person>
				<givenname>Katy</givenname>
				<surname>Warr</surname>
			</person>
			<person>
				<givenname>Wu</givenname>
				<surname>Chou</surname>
			</person>
		</names>
		<date value="2010-08"/>
		<abstract>
			<richtext>
				<p>This specification defines how metadata associated with a Web service endpoint can be represented as WS-Transfer resources or HTTP resources, how metadata can be embedded in WS-Addressing endpoint references, how metadata could be retrieved from a metadata resource, and how metadata associated with implicit features can be advertised.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-ws-metadata-exchange-20100805</howpublished>
		<title type="sharef:primaryTitle">Web Services Metadata Exchange (WS-MetadataExchange)</title>
		<field type="bibtex:topic">wsmetadataexchange[1] wstransfer[0.9] wsaddressing[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2010/WD-ws-metadata-exchange-20100805</identifier>
	</reference>
	<reference name="wseventing" src="bibtex:misc" src-info="bibtex:line-30856" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Doug</givenname>
				<surname>Davis</surname>
			</person>
			<person>
				<givenname>Ashok</givenname>
				<surname>Malhotra</surname>
			</person>
			<person>
				<givenname>Katy</givenname>
				<surname>Warr</surname>
			</person>
			<person>
				<givenname>Wu</givenname>
				<surname>Chou</surname>
			</person>
		</names>
		<date value="2010-08"/>
		<abstract>
			<richtext>
				<p>This specification describes a protocol that allows Web services to subscribe to or accept subscriptions for notification messages.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-ws-eventing-20100805</howpublished>
		<title type="sharef:primaryTitle">Web Services Eventing (WS-Eventing)</title>
		<field type="bibtex:topic">wseventing[1]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2010/WD-ws-eventing-20100805</identifier>
	</reference>
	<reference name="wseventdescriptions" src="bibtex:misc" src-info="bibtex:line-30867" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Doug</givenname>
				<surname>Davis</surname>
			</person>
			<person>
				<givenname>Ashok</givenname>
				<surname>Malhotra</surname>
			</person>
			<person>
				<givenname>Katy</givenname>
				<surname>Warr</surname>
			</person>
			<person>
				<givenname>Wu</givenname>
				<surname>Chou</surname>
			</person>
		</names>
		<date value="2010-08"/>
		<abstract>
			<richtext>
				<p>This specification describes a mechanism by which an endpoint can advertise the structure and contents of the events it might generate.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-ws-event-descriptions-20100805</howpublished>
		<title type="sharef:primaryTitle">Web Services Event Descriptions (WS-EventDescriptions)</title>
		<field type="bibtex:topic">wseventing[1]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2010/WD-ws-event-descriptions-20100805</identifier>
	</reference>
	<reference name="wsenumeration" src="bibtex:misc" src-info="bibtex:line-30878" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Doug</givenname>
				<surname>Davis</surname>
			</person>
			<person>
				<givenname>Ashok</givenname>
				<surname>Malhotra</surname>
			</person>
			<person>
				<givenname>Katy</givenname>
				<surname>Warr</surname>
			</person>
			<person>
				<givenname>Wu</givenname>
				<surname>Chou</surname>
			</person>
		</names>
		<date value="2010-08"/>
		<abstract>
			<richtext>
				<p>This specification describes a general SOAP-based protocol for enumerating a sequence of XML elements from a SOAP enabled information source.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-ws-enumeration-20100805</howpublished>
		<title type="sharef:primaryTitle">Web Services Enumeration (WS-Enumeration)</title>
		<field type="bibtex:topic">wstransfer[1]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2010/WD-ws-enumeration-20100805</identifier>
	</reference>
	<reference name="egovimproving" src="bibtex:misc" src-info="bibtex:line-30889" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Suzanne</givenname>
				<surname>Acar</surname>
			</person>
			<person>
				<givenname>José M.</givenname>
				<surname>Alonso</surname>
			</person>
			<person>
				<givenname>Kevin</givenname>
				<surname>Novak</surname>
			</person>
		</names>
		<date value="2009-05"/>
		<abstract>
			<richtext>
				<p>Current Web technology allows governments to share with the public a variety of information in unlimited quantities on demand. Technology is also available to allow citizens to bring issues of concern to the attention of local, regional and national governments. However, exploiting these capabilities within government systems is a challenge that encompasses environmental, policy, legal, and cultural issues. Establishing effective eGovernment requires openness, transparency, collaboration and skill in taking advantage of the capabilities of the World Wide Web. The rich potential for two-way dialogue between citizens and government creates a need for global leadership. The W3C has an opportunity to provide guidance in support of eGovernment objectives by promoting existing open Web standards and noting the challenges external to the Web and technology. There is also role for the W3C to facilitate the development and vetting of new open Web standards needed by governments in context. This document is an attempt to describe, but not yet solve, the variety of issues and challenges faced by governments in their efforts to apply 21st century capabilities to eGovernment initiatives. Detail and useful examples of existing, applicable open Web standards are provided. Where government needs in the development of eGovernment services are not currently met by existing standards, those gaps are noted.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Note NOTE-egov-improving-20090512</howpublished>
		<title type="sharef:primaryTitle">Improving Access to Government through Better Use of the Web</title>
		<identifier type="sharef:uri">http://www.w3.org/TR/2009/NOTE-egov-improving-20090512</identifier>
	</reference>
	<reference name="govdata" src="bibtex:misc" src-info="bibtex:line-30899" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Daniel</givenname>
				<surname>Bennett</surname>
			</person>
			<person>
				<givenname>Adam</givenname>
				<surname>Harvey</surname>
			</person>
		</names>
		<date value="2009-09"/>
		<abstract>
			<richtext>
				<p>Every day, governments and government agencies publish more data on the Internet. Sharing this data enables greater transparency; delivers more efficient public services; and encourages greater public and commercial use and re-use of government information. Some governments have even created catalogs or portals (such as data.gov) to make it easy for the public to find and use this data. Although the reasons may vary, the logistics and practicalities of opening government data are the same. To help governments open and share their data, the W3C eGov Interest Group has developed the following guidelines. These straightforward steps emphasize standards and methodologies to encourage publication of government data, allowing the public to use this data in new and innovative ways.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-gov-data-20090908</howpublished>
		<title type="sharef:primaryTitle">Publishing Open Government Data</title>
		<identifier type="sharef:uri">http://www.w3.org/TR/2009/WD-gov-data-20090908</identifier>
	</reference>
	<reference name="sml11" src="bibtex:misc" src-info="bibtex:line-30909" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Bhalchandra</givenname>
				<surname>Pandit</surname>
			</person>
			<person>
				<givenname>Valentina</givenname>
				<surname>Popescu</surname>
			</person>
			<person>
				<givenname>Virginia</givenname>
				<surname>Smith</surname>
			</person>
		</names>
		<date value="2009-05"/>
		<abstract>
			<richtext>
				<p>This specification defines the Service Modeling Language, Version 1.1 (SML) used to model complex services and systems, including their structure, constraints, policies, and best practices. SML uses XML Schema and Schematron.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Recommendation REC-sml-20090512</howpublished>
		<title type="sharef:primaryTitle">Service Modeling Language, Version 1.1</title>
		<field type="bibtex:topic">sml[1]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2009/REC-sml-20090512</identifier>
	</reference>
	<reference name="smlif11" src="bibtex:misc" src-info="bibtex:line-30920" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Bhalchandra</givenname>
				<surname>Pandit</surname>
			</person>
			<person>
				<givenname>Valentina</givenname>
				<surname>Popescu</surname>
			</person>
			<person>
				<givenname>Virginia</givenname>
				<surname>Smith</surname>
			</person>
		</names>
		<date value="2009-05"/>
		<abstract>
			<richtext>
				<p>This specification defines the interchange format for Service Modeling Language, Version 1.1 (SML) models. This format identifies the model being interchanged, distinguishes between model definition documents and model instance documents, and defines the binding of rule documents with other documents in the interchange model.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Recommendation REC-sml-if-20090512</howpublished>
		<title type="sharef:primaryTitle">Service Modeling Language Interchange Format Version 1.1</title>
		<field type="bibtex:topic">sml[1]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2009/REC-sml-if-20090512</identifier>
	</reference>
	<reference name="smlxlink" src="bibtex:misc" src-info="bibtex:line-30931" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Pratul</givenname>
				<surname>Dublish</surname>
			</person>
			<person>
				<givenname>Len</givenname>
				<surname>Charest</surname>
			</person>
			<person>
				<givenname>Virginia</givenname>
				<surname>Smith</surname>
			</person>
		</names>
		<date value="2009-10"/>
		<abstract>
			<richtext>
				<p>The Service Modeling Language (SML) specification extends the Extensible Markup Language (XML) and XML Schema with a mechanism for incorporating into XML documents references to other documents or document fragments. This technical note addresses the construction of an SML reference scheme based on the XML Linking Language (XLink).</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Note NOTE-sml-xlink-ref-scheme-20091023</howpublished>
		<title type="sharef:primaryTitle">The SML XLink Reference Scheme</title>
		<field type="bibtex:topic">sml[0.9] xlink[0.8]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2009/NOTE-sml-xlink-ref-scheme-20091023</identifier>
	</reference>
	<reference name="smlepr" src="bibtex:misc" src-info="bibtex:line-30942" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Kirk</givenname>
				<surname>Wilson</surname>
			</person>
		</names>
		<date value="2009-06"/>
		<abstract>
			<richtext>
				<p>The Service Modeling Language (SML) specification extends the Extensible Markup Language (XML) and XML Schema with a mechanism for incorporating into XML documents references to other documents or document fragments. This technical note addresses the construction of SML reference schemes for document or document fragment references that employ WS-Addressing (WS-A) endpoint references (EPRs).</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Note NOTE-sml-epr-ref-scheme-20090630</howpublished>
		<title type="sharef:primaryTitle">Framework for SML EPR-Based Reference Schemes</title>
		<field type="bibtex:topic">sml[0.9] wsaddr[0.8]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2009/NOTE-sml-epr-ref-scheme-20090630</identifier>
	</reference>
	<reference name="wsareq" src="bibtex:misc" src-info="bibtex:line-30953" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Daniel</givenname>
				<surname>Austin</surname>
			</person>
			<person>
				<givenname>Abbie</givenname>
				<surname>Barbir</surname>
			</person>
			<person>
				<givenname>Christopher</givenname>
				<surname>Ferris</surname>
			</person>
			<person>
				<givenname>Sharad</givenname>
				<surname>Garg</surname>
			</person>
		</names>
		<date value="2004-02"/>
		<howpublished>World Wide Web Consortium, Note NOTE-wsa-reqs-20040211</howpublished>
		<title type="sharef:primaryTitle">Web Services Architecture Requirements</title>
		<identifier type="sharef:uri">http://www.w3.org/TR/2004/NOTE-wsa-reqs-20040211</identifier>
	</reference>
	<reference name="wspolicy" src="bibtex:misc" src-info="bibtex:line-30962" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Asir S.</givenname>
				<surname>Vedamuthu</surname>
			</person>
			<person>
				<givenname>David</givenname>
				<surname>Orchard</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-09"/>
		<abstract>
			<richtext>
				<p>The Web Services Policy 1.5 — Framework provides a general purpose model and corresponding syntax to describe the policies of entities in a Web services-based system. Web Services Policy Framework defines a base set of constructs that can be used and extended by other Web services specifications to describe a broad range of service requirements and capabilities.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Recommendation REC-ws-policy-20070904</howpublished>
		<title type="sharef:primaryTitle">Web Services Policy 1.5 — Framework</title>
		<identifier type="sharef:uri">http://www.w3.org/TR/2007/REC-ws-policy-20070904</identifier>
	</reference>
	<reference name="wspolicyattach" src="bibtex:misc" src-info="bibtex:line-30972" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Asir S.</givenname>
				<surname>Vedamuthu</surname>
			</person>
			<person>
				<givenname>David</givenname>
				<surname>Orchard</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-09"/>
		<abstract>
			<richtext>
				<p>This specification, Web Services Policy 1.5 — Attachment, defines two general-purpose mechanisms for associating policies, as defined in Web Services Policy 1.5 — Framework, with the subjects to which they apply. This specification also defines how these general-purpose mechanisms may be used to associate policies with WSDL and UDDI descriptions.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Recommendation REC-ws-policy-attach-20070904</howpublished>
		<title type="sharef:primaryTitle">Web Services Policy 1.5 — Attachment</title>
		<identifier type="sharef:uri">http://www.w3.org/TR/2007/REC-ws-policy-attach-20070904</identifier>
	</reference>
	<reference name="wspolicyprimer" src="bibtex:misc" src-info="bibtex:line-30982" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Asir S.</givenname>
				<surname>Vedamuthu</surname>
			</person>
			<person>
				<givenname>David</givenname>
				<surname>Orchard</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-11"/>
		<abstract>
			<richtext>
				<p>Web Services Policy 1.5 — Primer is an introductory description of the Web Services Policy language. This document describes the policy language features using numerous examples. The associated Web Services Policy 1.5 — Framework and Web Services Policy 1.5 — Attachment specifications provide the complete normative description of the Web Services Policy language.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Note NOTE-ws-policy-primer-20071112</howpublished>
		<title type="sharef:primaryTitle">Web Services Policy 1.5 — Primer</title>
		<identifier type="sharef:uri">http://www.w3.org/TR/2007/NOTE-ws-policy-primer-20071112</identifier>
	</reference>
	<reference name="wspolicyguidelines" src="bibtex:misc" src-info="bibtex:line-30992" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Asir S.</givenname>
				<surname>Vedamuthu</surname>
			</person>
			<person>
				<givenname>David</givenname>
				<surname>Orchard</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-11"/>
		<abstract>
			<richtext>
				<p>Web Services Policy 1.5 — Guidelines for Policy Assertion Authors is intended to provide guidance for assertion authors that will work with the Web Services Policy 1.5 — Framework and Web Services Policy 1.5 — Attachment specifications to create domain specific assertions. The focus of this document is to provide best practices and patterns to follow as well as illustrate the care needed in using WS-Policy to achieve the best possible results for interoperability. It is a complementary guide to using the specifications.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Note NOTE-ws-policy-guidelines-20071112</howpublished>
		<title type="sharef:primaryTitle">Web Services Policy 1.5 — Guidelines for Policy Assertion Authors</title>
		<identifier type="sharef:uri">http://www.w3.org/TR/2007/NOTE-ws-policy-guidelines-20071112</identifier>
	</reference>
	<reference name="wssoapassertions" src="bibtex:misc" src-info="bibtex:line-31002" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Doug</givenname>
				<surname>Davis</surname>
			</person>
			<person>
				<givenname>Ashok</givenname>
				<surname>Malhotra</surname>
			</person>
			<person>
				<givenname>Katy</givenname>
				<surname>Warr</surname>
			</person>
			<person>
				<givenname>Wu</givenname>
				<surname>Chou</surname>
			</person>
		</names>
		<date value="2010-08"/>
		<abstract>
			<richtext>
				<p>This specification defines two WS-Policy assertions that can be used to advertise the requirement to use a certain version of SOAP in message exchanges.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-ws-soap-assertions-20100805</howpublished>
		<title type="sharef:primaryTitle">Web Services SOAP Assertions (WS-SOAPAssertions)</title>
		<identifier type="sharef:uri">http://www.w3.org/TR/2010/WD-ws-soap-assertions-20100805</identifier>
	</reference>
	<reference name="wsarch" src="bibtex:misc" src-info="bibtex:line-31012" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>David</givenname>
				<surname>Booth</surname>
			</person>
			<person>
				<givenname>Hugo</givenname>
				<surname>Haas</surname>
			</person>
			<person>
				<givenname>Francis</givenname>
				<surname>McCabe</surname>
			</person>
			<person>
				<givenname>Eric</givenname>
				<surname>Newcomer</surname>
			</person>
			<person>
				<givenname>Mike</givenname>
				<surname>Champion</surname>
			</person>
			<person>
				<givenname>Christopher</givenname>
				<surname>Ferris</surname>
			</person>
			<person>
				<givenname>David</givenname>
				<surname>Orchard</surname>
			</person>
		</names>
		<date value="2004-02"/>
		<abstract>
			<richtext>
				<p>This document defines the Web Services Architecture. It identifies the functional components and defines the relationships among those components to effect the desired properties of the overall architecture.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Note NOTE-ws-arch-20040211</howpublished>
		<title type="sharef:primaryTitle">Web Services Architecture</title>
		<identifier type="sharef:uri">http://www.w3.org/TR/2004/NOTE-ws-arch-20040211</identifier>
	</reference>
	<reference name="wslc" src="bibtex:misc" src-info="bibtex:line-31022" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Hao</givenname>
				<surname>He</surname>
			</person>
			<person>
				<givenname>Mark</givenname>
				<surname>Potts</surname>
			</person>
			<person>
				<givenname>Igor</givenname>
				<surname>Sedukhin</surname>
			</person>
		</names>
		<date value="2004-02"/>
		<howpublished>World Wide Web Consortium, Note NOTE-wslc-20040211</howpublished>
		<title type="sharef:primaryTitle">Web Service Management: Service Life Cycle</title>
		<identifier type="sharef:uri">http://www.w3.org/TR/2004/NOTE-wslc-20040211</identifier>
	</reference>
	<reference name="wsgloss" src="bibtex:misc" src-info="bibtex:line-31031" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Allen</givenname>
				<surname>Brown</surname>
			</person>
			<person>
				<givenname>Hugo</givenname>
				<surname>Haas</surname>
			</person>
		</names>
		<date value="2004-02"/>
		<howpublished>World Wide Web Consortium, Note NOTE-ws-gloss-20040211</howpublished>
		<title type="sharef:primaryTitle">Web Services Glossary</title>
		<identifier type="sharef:uri">http://www.w3.org/TR/2004/NOTE-ws-gloss-20040211</identifier>
	</reference>
	<reference name="wsdreq" src="bibtex:misc" src-info="bibtex:line-31040" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Jeffrey C.</givenname>
				<surname>Schlimmer</surname>
			</person>
		</names>
		<date value="2002-10"/>
		<howpublished>World Wide Web Consortium, Working Draft WD-ws-desc-reqs-20021028</howpublished>
		<title type="sharef:primaryTitle">Web Service Description Requirements</title>
		<identifier type="sharef:uri">http://www.w3.org/TR/2002/WD-ws-desc-reqs-20021028</identifier>
	</reference>
	<reference name="wsduse" src="bibtex:misc" src-info="bibtex:line-31049" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Waqar</givenname>
				<surname>Sadiq</surname>
			</person>
			<person>
				<givenname>Sandeep</givenname>
				<surname>Kumar</surname>
			</person>
		</names>
		<date value="2002-06"/>
		<howpublished>World Wide Web Consortium, Working Draft WD-ws-desc-usecases-20020604</howpublished>
		<title type="sharef:primaryTitle">Web Service Description Usage Scenarios</title>
		<identifier type="sharef:uri">http://www.w3.org/TR/2002/WD-ws-desc-usecases-20020604</identifier>
	</reference>
	<reference name="wsi18nscen" src="bibtex:misc" src-info="bibtex:line-31058" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Debasish</givenname>
				<surname>Banerjee</surname>
			</person>
			<person>
				<givenname>Martin J.</givenname>
				<surname>Dürst</surname>
			</person>
			<person>
				<givenname>Mike</givenname>
				<surname>McKenna</surname>
			</person>
			<person>
				<givenname>Addison P.</givenname>
				<surname>Phillips</surname>
			</person>
			<person>
				<givenname>Takao</givenname>
				<surname>Suzuki</surname>
			</person>
			<person>
				<givenname>Tex</givenname>
				<surname>Texin</surname>
			</person>
			<person>
				<givenname>Mary</givenname>
				<surname>Trumble</surname>
			</person>
			<person>
				<givenname>Andrea</givenname>
				<surname>Vine</surname>
			</person>
			<person>
				<givenname>Kentaroh</givenname>
				<surname>Noji</surname>
			</person>
		</names>
		<date value="2004-07"/>
		<abstract>
			<richtext>
				<p>This document describes internationalization usage patterns and scenarios for Web services. It also provides guidance for implementers of Web service technologies, suggesting methods for dealing with general international interoperability issues in services and service descriptions. One goal of this document is to provide a template for Web service designers to implement international capabilities in their services.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Note NOTE-ws-i18n-scenarios-20040730</howpublished>
		<title type="sharef:primaryTitle">Web Services Internationalization Usage Scenarios</title>
		<field type="bibtex:topic">i18n[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2004/NOTE-ws-i18n-scenarios-20040730</identifier>
	</reference>
	<reference name="wsarchscen" src="bibtex:misc" src-info="bibtex:line-31069" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Hao</givenname>
				<surname>He</surname>
			</person>
			<person>
				<givenname>Hugo</givenname>
				<surname>Haas</surname>
			</person>
			<person>
				<givenname>David</givenname>
				<surname>Orchard</surname>
			</person>
		</names>
		<date value="2004-02"/>
		<abstract>
			<richtext>
				<p>This document describes the Web Service Architecture use cases and Usage Scenarios. It is a collection of use cases and usage scenarios which illustrate the use of Web services. They are used to generate requirements for the Web services architecture, as well as to evaluate existing technologies.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Note NOTE-ws-arch-scenarios-20040211</howpublished>
		<title type="sharef:primaryTitle">Web Services Architecture Usage Scenarios</title>
		<identifier type="sharef:uri">http://www.w3.org/TR/2004/NOTE-ws-arch-scenarios-20040211</identifier>
	</reference>
	<reference name="wsaddrcore" src="bibtex:misc" src-info="bibtex:line-31079" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Martin</givenname>
				<surname>Gudgin</surname>
			</person>
			<person>
				<givenname>Marc</givenname>
				<surname>Hadley</surname>
			</person>
			<person>
				<givenname>Tony</givenname>
				<surname>Rogers</surname>
			</person>
		</names>
		<date value="2006-05"/>
		<abstract>
			<richtext>
				<p>Web Services Addressing provides transport-neutral mechanisms to address Web services and messages. Web Services Addressing 1.0 — Core (this document) defines a set of abstract properties and an XML Infoset representation thereof to reference Web services and to facilitate end-to-end addressing of endpoints in messages. This specification enables messaging systems to support message transmission through networks that include processing nodes such as endpoint managers, firewalls, and gateways in a transport-neutral manner.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Recommendation REC-ws-addr-core-20060509</howpublished>
		<title type="sharef:primaryTitle">Web Services Addressing 1.0 — Core</title>
		<field type="bibtex:topic">wsaddr[1]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2006/REC-ws-addr-core-20060509</identifier>
	</reference>
	<reference name="wsaddrsoap" src="bibtex:misc" src-info="bibtex:line-31090" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Martin</givenname>
				<surname>Gudgin</surname>
			</person>
			<person>
				<givenname>Marc</givenname>
				<surname>Hadley</surname>
			</person>
			<person>
				<givenname>Tony</givenname>
				<surname>Rogers</surname>
			</person>
		</names>
		<date value="2006-05"/>
		<abstract>
			<richtext>
				<p>Web Services Addressing provides transport-neutral mechanisms to address Web services and messages. Web Services Addressing 1.0 — SOAP Binding (this document) defines the binding of the abstract properties defined in Web Services Addressing 1.0 — Core to SOAP Messages.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Recommendation REC-ws-addr-soap-20060509</howpublished>
		<title type="sharef:primaryTitle">Web Services Addressing 1.0 — SOAP Binding</title>
		<field type="bibtex:topic">soap[0.8] wsaddr[1]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2006/REC-ws-addr-soap-20060509</identifier>
	</reference>
	<reference name="wsaddrmetadata" src="bibtex:misc" src-info="bibtex:line-31101" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Martin</givenname>
				<surname>Gudgin</surname>
			</person>
			<person>
				<givenname>Marc</givenname>
				<surname>Hadley</surname>
			</person>
			<person>
				<givenname>Tony</givenname>
				<surname>Rogers</surname>
			</person>
			<person>
				<givenname>Ümit</givenname>
				<surname>Yalçınalp</surname>
			</person>
		</names>
		<date value="2007-09"/>
		<abstract>
			<richtext>
				<p>Web Services Addressing provides transport-neutral mechanisms to address Web services and messages. Web Services Addressing 1.0 — Metadata (this document) defines how the abstract properties defined in Web Services Addressing 1.0 — Core are described using WSDL, how to include WSDL metadata in endpoint references, and how WS-Policy can be used to indicate the support of WS-Addressing by a Web service.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Recommendation REC-ws-addr-metadata-20070904</howpublished>
		<title type="sharef:primaryTitle">Web Services Addressing 1.0 — Metadata</title>
		<field type="bibtex:topic">wsdl[0.8] wsaddr[1]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2007/REC-ws-addr-metadata-20070904</identifier>
	</reference>
	<reference name="rifoverview" src="bibtex:misc" src-info="bibtex:line-31112" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Michael</givenname>
				<surname>Kifer</surname>
			</person>
			<person>
				<givenname>Harold</givenname>
				<surname>Boley</surname>
			</person>
		</names>
		<date value="2010-06"/>
		<abstract>
			<richtext>
				<p>This document is an overview of the Rule Interchange Format (RIF). It provides a high-level explanation of RIF concepts and architecture as well as a general survey of RIF documents.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Note NOTE-rif-overview-20100622</howpublished>
		<title type="sharef:primaryTitle">RIF Overview</title>
		<field type="bibtex:topic">rif[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2010/NOTE-rif-overview-20100622</identifier>
	</reference>
	<reference name="rifucr" src="bibtex:misc" src-info="bibtex:line-31123" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Adrian</givenname>
				<surname>Paschke</surname>
			</person>
			<person>
				<givenname>David</givenname>
				<surname>Hirtle</surname>
			</person>
			<person>
				<givenname>Allen</givenname>
				<surname>Ginsberg</surname>
			</person>
			<person>
				<givenname>Paula-Lavinia</givenname>
				<surname>Patranjan</surname>
			</person>
			<person>
				<givenname>Frank</givenname>
				<surname>McCabe</surname>
			</person>
		</names>
		<date value="2008-12"/>
		<abstract>
			<richtext>
				<p>This document, developed by the Rule Interchange Format (RIF) Working Group, specifies use cases and requirements for the W3C Rule Interchange Format, a family of rule interchange dialects that allows rules to be translated between rule languages and thus transferred between rule systems.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-rif-ucr-20081218</howpublished>
		<title type="sharef:primaryTitle">RIF Use Cases and Requirements</title>
		<field type="bibtex:topic">rif[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2008/WD-rif-ucr-20081218</identifier>
	</reference>
	<reference name="rifcore" src="bibtex:misc" src-info="bibtex:line-31134" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Harold</givenname>
				<surname>Boley</surname>
			</person>
			<person>
				<givenname>Gary</givenname>
				<surname>Hallmark</surname>
			</person>
			<person>
				<givenname>Michael</givenname>
				<surname>Kifer</surname>
			</person>
			<person>
				<givenname>Adrian</givenname>
				<surname>Paschke</surname>
			</person>
			<person>
				<givenname>Axel</givenname>
				<surname>Polleres</surname>
			</person>
			<person>
				<givenname>Dave</givenname>
				<surname>Reynolds</surname>
			</person>
		</names>
		<date value="2010-06"/>
		<abstract>
			<richtext>
				<p>This document, developed by the Rule Interchange Format (RIF) Working Group, specifies RIF-Core, a common subset of RIF-BLD and RIF-PRD based on RIF-DTB 1.0. The RIF-Core presentation syntax and semantics are specified by restriction in two different ways. First, RIF-Core is specified by restricting the syntax and semantics of RIF-BLD, and second, by restricting RIF-PRD. The XML serialization syntax of RIF-Core is specified by a mapping from the presentation syntax. A normative XML schema is also provided.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Recommendation REC-rif-core-20100622</howpublished>
		<title type="sharef:primaryTitle">RIF Core Dialect</title>
		<field type="bibtex:topic">rif[1]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2010/REC-rif-core-20100622</identifier>
	</reference>
	<reference name="riffld" src="bibtex:misc" src-info="bibtex:line-31145" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Harold</givenname>
				<surname>Boley</surname>
			</person>
			<person>
				<givenname>Michael</givenname>
				<surname>Kifer</surname>
			</person>
		</names>
		<date value="2010-06"/>
		<abstract>
			<richtext>
				<p>This document, developed by the Rule Interchange Format (RIF) Working Group, defines a general RIF Framework for Logic Dialects (RIF-FLD). The framework describes mechanisms for specifying the syntax and semantics of logic RIF dialects through a number of generic concepts such as signatures, symbol spaces, semantic structures, and so on. The actual dialects should specialize this framework to produce their syntaxes and semantics.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Recommendation REC-rif-fld-20100622</howpublished>
		<title type="sharef:primaryTitle">RIF Framework for Logic Dialects</title>
		<field type="bibtex:topic">rif[0.9] riffld[1]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2010/REC-rif-fld-20100622</identifier>
	</reference>
	<reference name="rifbld" src="bibtex:misc" src-info="bibtex:line-31156" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Harold</givenname>
				<surname>Boley</surname>
			</person>
			<person>
				<givenname>Michael</givenname>
				<surname>Kifer</surname>
			</person>
		</names>
		<date value="2010-06"/>
		<abstract>
			<richtext>
				<p>This document, developed by the Rule Interchange Format (RIF) Working Group, specifies the Basic Logic Dialect, RIF-BLD, a format that allows logic rules to be exchanged between rule systems. The RIF-BLD presentation syntax and semantics are specified both directly and as specializations of the RIF Framework for Logic Dialects, or RIF-FLD. The XML serialization syntax of RIF-BLD is specified via a mapping from the presentation syntax. A normative XML schema is also provided.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Recommendation REC-rif-bld-20100622</howpublished>
		<title type="sharef:primaryTitle">RIF Basic Logic Dialect</title>
		<field type="bibtex:topic">rif[1]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2010/REC-rif-bld-20100622</identifier>
	</reference>
	<reference name="rifdtb" src="bibtex:misc" src-info="bibtex:line-31167" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Axel</givenname>
				<surname>Polleres</surname>
			</person>
			<person>
				<givenname>Harold</givenname>
				<surname>Boley</surname>
			</person>
			<person>
				<givenname>Michael</givenname>
				<surname>Kifer</surname>
			</person>
		</names>
		<date value="2010-06"/>
		<abstract>
			<richtext>
				<p>This document, developed by the Rule Interchange Format (RIF) Working Group, specifies a list of datatypes, built-in functions and built-in predicates expected to be supported by RIF dialects such as the RIF Core Dialect, the RIF Basic Logic Dialect, and the RIF Production Rules Dialect. Each dialect supporting a superset or subset of the datatypes, built-in functions and built-in predicates defined here shall specify these additions or restrictions. Some of the datatypes are adapted from [XML Schema Datatypes]. A large part of the definitions of the listed functions and operators are adapted from [XPath-Functions]. The rdf:PlainLiteral datatype as well as functions and operators associated with that datatype are adopted from [RDF-PLAINLITERAL].</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Recommendation REC-rif-dtb-20100622</howpublished>
		<title type="sharef:primaryTitle">RIF Datatypes and Built-Ins 1.0</title>
		<field type="bibtex:topic">rif[1]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2010/REC-rif-dtb-20100622</identifier>
	</reference>
	<reference name="riftest" src="bibtex:misc" src-info="bibtex:line-31178" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Stella</givenname>
				<surname>Mitchell</surname>
			</person>
			<person>
				<givenname>Leora</givenname>
				<surname>Morgenstern</surname>
			</person>
			<person>
				<givenname>Adrian</givenname>
				<surname>Paschke</surname>
			</person>
		</names>
		<date value="2010-06"/>
		<abstract>
			<richtext>
				<p>This document describes the test cases developed by the Rule Interchange Format (RIF) Working Group in accordance with the Working Group's Charter. These test cases are intended to aid in the conformance evaluation of RIF implementations and thus promote interoperability.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-rif-test-20100622</howpublished>
		<title type="sharef:primaryTitle">RIF Test Cases</title>
		<field type="bibtex:topic">rif[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2010/WD-rif-test-20100622</identifier>
	</reference>
	<reference name="rifrdfowl" src="bibtex:misc" src-info="bibtex:line-31189" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Jos</givenname>
				<surname link="de">Bruijn</surname>
			</person>
		</names>
		<date value="2010-06"/>
		<abstract>
			<richtext>
				<p>Rules interchanged using the Rule Interchange Format RIF may depend on or be used in combination with RDF data and RDF Schema or OWL ontologies. This document, developed by the Rule Interchange Format (RIF) Working Group, specifies the interoperation between RIF and the data and ontology languages RDF, RDF Schema, and OWL.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Recommendation REC-rif-rdf-owl-20100622</howpublished>
		<title type="sharef:primaryTitle">RIF RDF and OWL Compatibility</title>
		<field type="bibtex:topic">rif[0.9] owl[0.9] rdf[0.9] rdfs[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2010/REC-rif-rdf-owl-20100622</identifier>
	</reference>
	<reference name="rifowlrl" src="bibtex:misc" src-info="bibtex:line-31200" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Dave</givenname>
				<surname>Reynolds</surname>
			</person>
		</names>
		<date value="2010-06"/>
		<abstract>
			<richtext>
				<p>This document shows how OWL 2 RL can be implemented using RIF. It provides an analysis of how to represent OWL 2 RL inference rules within RIF Core. The OWL 2 RL inference rules can be implemented both via a fixed RIF Core rule set (Appendix 7) and via a mapping algorithm which converts an OWL 2 RL ontology to a customized RIF Core rule set (Appendix 8).</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Note NOTE-rif-owl-rl-20100622</howpublished>
		<title type="sharef:primaryTitle">OWL 2 RL in RIF</title>
		<field type="bibtex:topic">rif[0.9] owl[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2010/NOTE-rif-owl-rl-20100622</identifier>
	</reference>
	<reference name="rifinrdf" src="bibtex:misc" src-info="bibtex:line-31211" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Sandro</givenname>
				<surname>Hawke</surname>
			</person>
		</names>
		<date value="2010-06"/>
		<abstract>
			<richtext>
				<p>This document specifies a reversible mapping (or transformation) from Rule Interchange Format (RIF) XML documents to Resource Description Framework (RDF) graphs. This mapping allows the contents of RIF documents to be interoperably stored and processed as RDF triples, using existing serializations and tools for RDF. When used with the standard mapping from RDF triples to RIF frames, this also provides a "reflection" or "introspection" mechanism, an interoperable way for RIF rules to operate on RIF documents.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-rif-in-rdf-20100622</howpublished>
		<title type="sharef:primaryTitle">RIF In RDF</title>
		<field type="bibtex:topic">rif[0.9] rdf[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2010/WD-rif-in-rdf-20100622</identifier>
	</reference>
	<reference name="rifxmldata" src="bibtex:misc" src-info="bibtex:line-31222" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Christian</givenname>
				<surname link="de">Sainte Marie</surname>
			</person>
		</names>
		<date value="2010-06"/>
		<abstract>
			<richtext>
				<p>This document, developed by the Rule Interchange Format (RIF) Working Group, specifies how a RIF document can be combined with XML data.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-rif-xml-data-20100622</howpublished>
		<title type="sharef:primaryTitle">RIF Combination with XML data</title>
		<field type="bibtex:topic">rif[0.9] xml[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2010/WD-rif-xml-data-20100622</identifier>
	</reference>
	<reference name="rifprd" src="bibtex:misc" src-info="bibtex:line-31233" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Christian</givenname>
				<surname link="de">Sainte Marie</surname>
			</person>
			<person>
				<givenname>Adrian</givenname>
				<surname>Paschke</surname>
			</person>
			<person>
				<givenname>Gary</givenname>
				<surname>Hallmark</surname>
			</person>
		</names>
		<date value="2010-06"/>
		<abstract>
			<richtext>
				<p>This document, developed by the Rule Interchange Format (RIF) Working Group, specifies the production rule dialect of the W3C rule interchange format (RIF-PRD), a standard XML serialization format for production rule languages.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Recommendation REC-rif-prd-20100622</howpublished>
		<title type="sharef:primaryTitle">RIF Production Rule Dialect</title>
		<field type="bibtex:topic">rif[0.9] rifprd[1]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2010/REC-rif-prd-20100622</identifier>
	</reference>
	<reference name="rexreqs" src="bibtex:misc" src-info="bibtex:line-31244" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Robin</givenname>
				<surname>Berjon</surname>
			</person>
		</names>
		<date value="2006-02"/>
		<abstract>
			<richtext>
				<p>This document lists the requirements for an XML grammar intended for representing events as they are defined in DOM3 Events, primarily but not exclusively for purposes of transmission or synchronisation of remote documents. Such a vocabulary would enable one endpoint to interact remotely with another endpoint holding a DOM representation by sending it DOM Events as if they had occurred directly at the same location.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Note NOTE-rex-reqs-20060202</howpublished>
		<title type="sharef:primaryTitle">Remote Events for XML (REX) Requirements</title>
		<field type="bibtex:topic">rex[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2006/NOTE-rex-reqs-20060202</identifier>
	</reference>
	<reference name="rex10" src="bibtex:misc" src-info="bibtex:line-31255" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Robin</givenname>
				<surname>Berjon</surname>
			</person>
		</names>
		<date value="2006-10"/>
		<abstract>
			<richtext>
				<p>Remote Events for XML (REX) 1.0 is an XML grammar for representing events as they are defined in DOM 3 Events, primarily but not exclusively for purposes of transmission. It enables one endpoint to interact remotely with another endpoint holding a DOM representation by sending it DOM Events as if they had occurred directly at the same location.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-rex-20061013</howpublished>
		<title type="sharef:primaryTitle">Remote Events for XML (REX) 1.0</title>
		<field type="bibtex:topic">rex[1] dom[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2006/WD-rex-20061013</identifier>
	</reference>
	<reference name="mediaaccessevents" src="bibtex:misc" src-info="bibtex:line-31266" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Ola</givenname>
				<surname>Andersson</surname>
			</person>
			<person>
				<givenname>Jean-Claude</givenname>
				<surname>Dufourd</surname>
			</person>
			<person>
				<givenname>Roland</givenname>
				<surname>Lundblad</surname>
			</person>
		</names>
		<date value="2006-10"/>
		<abstract>
			<richtext>
				<p>This specification defines a set of DOM 3 Events compatible events and DOM APIs related to media access. The defined events and APIs enables detailed monitoring of media stream buffering and initialization. They are designed to be easily combined with the SVG Tiny 1.2 uDOM but can equally well be combined with other, larger DOM APIs.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-MediaAccessEvents-20061013</howpublished>
		<title type="sharef:primaryTitle">Media Access Events</title>
		<field type="bibtex:topic">dom[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2006/WD-MediaAccessEvents-20061013</identifier>
	</reference>
	<reference name="timezone" src="bibtex:misc" src-info="bibtex:line-31277" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Addison P.</givenname>
				<surname>Phillips</surname>
			</person>
			<person>
				<givenname>Felix</givenname>
				<surname>Sasaki</surname>
			</person>
			<person>
				<givenname>Mark</givenname>
				<surname>Davis</surname>
			</person>
			<person>
				<givenname>Martin J.</givenname>
				<surname>Dürst</surname>
			</person>
		</names>
		<date value="2005-10"/>
		<abstract>
			<richtext>
				<p>This document discusses some of the problems encountered when working with the date, time, and dateTime values from XML Schema when those value include (or omit) time zone offsets. Many W3C technologies rely on date and time types. Examples include the XQuery 1.0 and XPath 2.0 Functions and Operators specification, since it is the basis for XQuery and XSLT processing of date/time values, but the concepts affect any date/time processing.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Note NOTE-timezone-20051013</howpublished>
		<title type="sharef:primaryTitle">Working with Time Zones</title>
		<identifier type="sharef:uri">http://www.w3.org/TR/2005/NOTE-timezone-20051013</identifier>
	</reference>
	<reference name="stts3" src="bibtex:misc" src-info="bibtex:line-31287" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Daniel</givenname>
				<surname>Glazman</surname>
			</person>
		</names>
		<date value="1998-11"/>
		<howpublished>World Wide Web Consortium, Note NOTE-STTS3-19981111</howpublished>
		<title type="sharef:primaryTitle">Simple Tree Transformation Sheets 3</title>
		<field type="bibtex:topic">stts[1]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/1998/NOTE-STTS3-19981111</identifier>
	</reference>
	<reference name="ddml10" src="bibtex:misc" src-info="bibtex:line-31297" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Ronald</givenname>
				<surname>Bourret</surname>
			</person>
			<person>
				<givenname>John</givenname>
				<surname>Cowan</surname>
			</person>
			<person>
				<givenname>Ingo</givenname>
				<surname>Macherius</surname>
			</person>
			<person>
				<givenname>Simon</givenname>
				<surname>St. Laurent</surname>
			</person>
		</names>
		<date value="1999-01"/>
		<howpublished>World Wide Web Consortium, Note NOTE-ddml-19990119</howpublished>
		<title type="sharef:primaryTitle">Document Definition Markup Language (DDML) Specification, Version 1.0</title>
		<field type="bibtex:topic">ddml[1]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/1999/NOTE-ddml-19990119</identifier>
	</reference>
	<reference name="testmetadata" src="bibtex:misc" src-info="bibtex:line-31307" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Patrick</givenname>
				<surname>Curran</surname>
			</person>
			<person>
				<givenname>Karl</givenname>
				<surname>Dubost</surname>
			</person>
		</names>
		<date value="2005-09"/>
		<abstract>
			<richtext>
				<p>The definition and provision of metadata has proved helpful in a variety of ways during the test development and test execution processes. This document defines a minimal set of metadata elements that can usefully be applied to tests that are intended for publication within a test suite.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Note NOTE-test-metadata-20050914</howpublished>
		<title type="sharef:primaryTitle">Test Metadata</title>
		<identifier type="sharef:uri">http://www.w3.org/TR/2005/NOTE-test-metadata-20050914</identifier>
	</reference>
	<reference name="wbxml" src="bibtex:misc" src-info="bibtex:line-31317" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Bruce</givenname>
				<surname>Martin</surname>
			</person>
			<person>
				<givenname>Bashar</givenname>
				<surname>Jano</surname>
			</person>
		</names>
		<date value="1999-06"/>
		<abstract>
			<richtext>
				<p>Wireless Application Protocol (WAP) is a result of continuous work to define an industry-wide specification for developing applications that operate over wireless communication networks. The scope of the WAP Forum is to define a set of specifications to be used by service applications. The wireless market is growing very quickly and reaching new customers and services. To enable operators and manufacturers to meet the challenges in advanced services, differentiation and fast/flexible service creation, WAP defines a set of protocols in transport, session and application layers. For additional information on the WAP architecture, refer to "Wireless Application Protocol Architecture Specification" (WAP). This specification defines a compact binary representation of the Extensible Markup Language (XML). The binary XML content format is designed to reduce the transmission size of XML documents, allowing more effective use of XML data on narrowband communication channels. Refer to the WML specification for one example use of the binary XML content format. The binary format was designed to allow for compact transmission with no loss of functionality or semantic information. The format is designed to preserve the element structure of XML, allowing a browser to skip unknown elements or attributes. The binary format encodes the parsed physical form of an XML document, i.e., the structure and content of the document entities. Meta-information, including the document type definition and conditional sections, is removed when the document is converted to the binary format.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Note NOTE-wbxml-19990624</howpublished>
		<title type="sharef:primaryTitle">WAP Binary XML Content Format</title>
		<field type="bibtex:topic">wbxml[1]</field>
		<identifier type="sharef:uri">http://www.w3.org/1999/06/NOTE-wbxml-19990624</identifier>
	</reference>
	<reference name="ian01" src="bibtex:misc" src-info="bibtex:line-31328" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Renato</givenname>
				<surname>Iannella</surname>
			</person>
		</names>
		<date value="2001-02"/>
		<abstract>
			<richtext>
				<p>This note specifies a Resource Description Framework (RDF) encoding of the vCard profile defined by RFC 2426 and to provide equivalent functionality to its standard format. The motivation is to enable the common and consistent description of persons (using the existing semantics of vCard) and to encode these in RDF/XML.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Note NOTE-vcard-rdf-20010222</howpublished>
		<title type="sharef:primaryTitle">Representing vCard Objects in RDF/XML</title>
		<field type="bibtex:topic">vcard[0.9]</field>
	</reference>
	<reference name="chtml1" src="bibtex:misc" src-info="bibtex:line-31338" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Tomihisa</givenname>
				<surname>Kamada</surname>
			</person>
		</names>
		<date value="1998-02"/>
		<abstract>
			<richtext>
				<p>The Internet infrastructure has been developed all over the world, and nowadays there are a variety of devices equipped with the Internet-access function, from TV sets to wireless cellular phones. The HyperText Markup Language (HTML) is widely accepted and spread as the standard of the WWW(World Wide Web) document format. The "Compact HTML" proposed here defines a subset of HTML for small information appliances such as smart phones, smart communicators, mobile PDAs, and etc. Such a certain level of HTML is strongly required as a guideline from the manufacturers of small information devices, service providers, carriers, and software developers. Since "Compact HTML" is completely based on the HTML recommendations, we can use millions of HTML-based content resources, various software tools, and public materials (textbooks, magazines, and web information).</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Note NOTE-compactHTML-19980209</howpublished>
		<title type="sharef:primaryTitle">Compact HTML for Small Information Appliances</title>
		<field type="bibtex:topic">chtml[1]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/1998/NOTE-compactHTML-19980209</identifier>
	</reference>
	<reference name="webontreq" src="bibtex:misc" src-info="bibtex:line-31349" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Jeff</givenname>
				<surname>Heflin</surname>
			</person>
		</names>
		<date value="2004-02"/>
		<howpublished>World Wide Web Consortium, Recommendation REC-webont-req-20040210</howpublished>
		<title type="sharef:primaryTitle">Web Ontology Language (OWL) Use Cases and Requirements</title>
		<field type="bibtex:topic">owl[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2004/REC-webont-req-20040210</identifier>
	</reference>
	<reference name="owlref" src="bibtex:misc" src-info="bibtex:line-31359" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Sean</givenname>
				<surname>Bechhofer</surname>
			</person>
			<person>
				<givenname>Frank</givenname>
				<surname link="van">Harmelen</surname>
			</person>
			<person>
				<givenname>James A.</givenname>
				<surname>Hendler</surname>
			</person>
			<person>
				<givenname>Ian</givenname>
				<surname>Horrocks</surname>
			</person>
			<person>
				<givenname>Deborah L.</givenname>
				<surname>McGuinness</surname>
			</person>
			<person>
				<givenname>Peter F.</givenname>
				<surname>Patel-Schneider</surname>
			</person>
			<person>
				<givenname>Lynn Andrea</givenname>
				<surname>Stein</surname>
			</person>
		</names>
		<names type="sharef:editor">
			<person>
				<givenname>Mike</givenname>
				<surname>Dean</surname>
			</person>
			<person>
				<givenname>Guus</givenname>
				<surname>Schreiber</surname>
			</person>
		</names>
		<date value="2004-02"/>
		<abstract>
			<richtext>
				<p>The Web Ontology Language OWL is a semantic markup language for publishing and sharing ontologies on the World Wide Web. OWL is developed as a vocabulary extension of RDF (the Resource Description Framework) and is derived from the DAML+OIL Web Ontology Language. This document contains a structured informal description of the full set of OWL language constructs and is meant to serve as a reference for OWL users who want to construct OWL ontologies.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Recommendation REC-owl-ref-20040210</howpublished>
		<title type="sharef:primaryTitle">OWL Web Ontology Language Reference</title>
		<field type="bibtex:topic">owl[1]</field>
		<field type="bibtex:updates">webontreq</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2004/REC-owl-ref-20040210</identifier>
	</reference>
	<reference name="owlguide" src="bibtex:misc" src-info="bibtex:line-31372" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Michael K.</givenname>
				<surname>Smith</surname>
			</person>
			<person>
				<givenname>Chris</givenname>
				<surname>Welty</surname>
			</person>
			<person>
				<givenname>Deborah L.</givenname>
				<surname>McGuinness</surname>
			</person>
		</names>
		<date value="2004-02"/>
		<abstract>
			<richtext>
				<p>The World Wide Web as it is currently constituted resembles a poorly mapped geography. Our insight into the documents and capabilities available are based on keyword searches, abetted by clever use of document connectivity and usage patterns. The sheer mass of this data is unmanageable without powerful tool support. In order to map this terrain more precisely, computational agents require machine-readable descriptions of the content and capabilities of Web accessible resources. These descriptions must be in addition to the human-readable versions of that information. The OWL Web Ontology Language is intended to provide a language that can be used to describe the classes and relations between them that are inherent in Web documents and applications. This document demonstrates the use of the OWL language to (1) formalize a domain by defining classes and properties of those classes, (2) define individuals and assert properties about them, and (3) reason about these classes and individuals to the degree permitted by the formal semantics of the OWL language. The sections are organized to present an incremental definition of a set of classes, properties and individuals, beginning with the fundamentals and proceeding to more complex language components.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Recommendation REC-owl-guide-20040210</howpublished>
		<title type="sharef:primaryTitle">OWL Web Ontology Language Guide</title>
		<field type="bibtex:topic">owl[1]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2004/REC-owl-guide-20040210</identifier>
	</reference>
	<reference name="owlabsyn" src="bibtex:misc" src-info="bibtex:line-31383" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Peter F.</givenname>
				<surname>Patel-Schneider</surname>
			</person>
			<person>
				<givenname>Ian</givenname>
				<surname>Horrocks</surname>
			</person>
			<person>
				<givenname>Frank</givenname>
				<surname link="van">Harmelen</surname>
			</person>
		</names>
		<date value="2002-07"/>
		<howpublished>World Wide Web Consortium, Working Draft WD-owl-absyn-20020729</howpublished>
		<title type="sharef:primaryTitle">OWL Web Ontology Language 1.0 Abstract Syntax</title>
		<field type="bibtex:topic">owl[1]</field>
		<field type="bibtex:updates">webontreq</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2002/WD-owl-absyn-20020729</identifier>
	</reference>
	<reference name="owlsemantics" src="bibtex:misc" src-info="bibtex:line-31394" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Peter F.</givenname>
				<surname>Patel-Schneider</surname>
			</person>
			<person>
				<givenname>Patrick</givenname>
				<surname>Hayes</surname>
			</person>
			<person>
				<givenname>Ian</givenname>
				<surname>Horrocks</surname>
			</person>
		</names>
		<date value="2004-02"/>
		<howpublished>World Wide Web Consortium, Recommendation REC-owl-semantics-20040210</howpublished>
		<title type="sharef:primaryTitle">OWL Web Ontology Language Semantics and Abstract Syntax</title>
		<field type="bibtex:topic">owl[1]</field>
		<field type="bibtex:updates">owlabsyn</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2004/REC-owl-semantics-20040210</identifier>
	</reference>
	<reference name="owlxmlsyntax" src="bibtex:misc" src-info="bibtex:line-31405" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Masahiro</givenname>
				<surname>Hori</surname>
			</person>
			<person>
				<givenname>Jérôme</givenname>
				<surname>Euzenat</surname>
			</person>
			<person>
				<givenname>Peter F.</givenname>
				<surname>Patel-Schneider</surname>
			</person>
		</names>
		<date value="2003-06"/>
		<howpublished>World Wide Web Consortium, Note NOTE-owl-xmlsyntax-20030611</howpublished>
		<title type="sharef:primaryTitle">OWL Web Ontology Language XML Presentation Syntax</title>
		<field type="bibtex:topic">owl[1]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2003/NOTE-owl-xmlsyntax-20030611</identifier>
	</reference>
	<reference name="owlfeatures" src="bibtex:misc" src-info="bibtex:line-31415" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Deborah L.</givenname>
				<surname>McGuinness</surname>
			</person>
			<person>
				<givenname>Frank</givenname>
				<surname link="van">Harmelen</surname>
			</person>
		</names>
		<date value="2004-02"/>
		<howpublished>World Wide Web Consortium, Recommendation REC-owl-features-20040210</howpublished>
		<title type="sharef:primaryTitle">OWL Web Ontology Language Overview</title>
		<field type="bibtex:topic">owl[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2004/REC-owl-features-20040210</identifier>
	</reference>
	<reference name="owltest" src="bibtex:misc" src-info="bibtex:line-31425" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Jeremy J.</givenname>
				<surname>Carroll</surname>
			</person>
			<person>
				<givenname>Jos</givenname>
				<surname>De Roo</surname>
			</person>
		</names>
		<date value="2004-02"/>
		<howpublished>World Wide Web Consortium, Recommendation REC-owl-test-20040210</howpublished>
		<title type="sharef:primaryTitle">OWL Web Ontology Language Test Cases</title>
		<field type="bibtex:topic">owl[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2004/REC-owl-test-20040210</identifier>
	</reference>
	<reference name="owlparsing" src="bibtex:misc" src-info="bibtex:line-31435" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Sean</givenname>
				<surname>Bechhofer</surname>
			</person>
		</names>
		<date value="2004-01"/>
		<howpublished>World Wide Web Consortium, Note NOTE-owl-parsing-20040121</howpublished>
		<title type="sharef:primaryTitle">Parsing OWL in RDF/XML</title>
		<field type="bibtex:topic">owl[0.9] rdf[0.7]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2004/NOTE-owl-parsing-20040121</identifier>
	</reference>
	<reference name="owltime" src="bibtex:misc" src-info="bibtex:line-31445" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Jerry R.</givenname>
				<surname>Hobbs</surname>
			</person>
			<person>
				<givenname>Feng</givenname>
				<surname>Pan</surname>
			</person>
		</names>
		<date value="2006-09"/>
		<abstract>
			<richtext>
				<p>This document presents an ontology of temporal concepts, OWL-Time (formerly DAML-Time), for describing the temporal content of Web pages and the temporal properties of Web services. The ontology provides a vocabulary for expressing facts about topological relations among instants and intervals, together with information about durations, and about datetime information. We also demonstrate in detail, using the Congo.com and Bravo Air examples from OWL-S, how this time ontology can be used to support OWL-S, including use cases for defining input parameters and (conditional) output parameters. A use case for meeting scheduling is also shown. In the appendix we also describe a time zone resource in OWL we developed for not only the US but also the entire world, including the time zone ontology, the US time zone instances, and the world time zone instances.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-owl-time-20060927</howpublished>
		<title type="sharef:primaryTitle">Time Ontology in OWL</title>
		<field type="bibtex:topic">owl[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2006/WD-owl-time-20060927</identifier>
	</reference>
	<reference name="owl11syntax" src="bibtex:misc" src-info="bibtex:line-31456" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Boris</givenname>
				<surname>Motik</surname>
			</person>
			<person>
				<givenname>Peter F.</givenname>
				<surname>Patel-Schneider</surname>
			</person>
			<person>
				<givenname>Ian</givenname>
				<surname>Horrocks</surname>
			</person>
		</names>
		<date value="2008-01"/>
		<abstract>
			<richtext>
				<p>OWL 1.1 extends the W3C OWL Web Ontology Language with a small but useful set of features that have been requested by users, for which effective reasoning algorithms are now available, and that OWL tool developers are willing to support. The new features include extra syntactic sugar, additional property and qualified cardinality constructors, extended datatype support, simple metamodeling, and extended annotations. This document defines a functional-style syntax for OWL 1.1, and provides an informal discussion of the meaning of the additional constructs. As well, an informational structural specification of OWL 1.1 ontologies is provided.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-owl11-syntax-20080108</howpublished>
		<title type="sharef:primaryTitle">OWL 1.1 Web Ontology Language: Structural Specification and Functional-Style Syntax</title>
		<field type="bibtex:topic">owl[1]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2008/WD-owl11-syntax-20080108</identifier>
	</reference>
	<reference name="owl11semantics" src="bibtex:misc" src-info="bibtex:line-31467" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Bernardo Cuenca</givenname>
				<surname>Grau</surname>
			</person>
			<person>
				<givenname>Boris</givenname>
				<surname>Motik</surname>
			</person>
		</names>
		<date value="2008-01"/>
		<abstract>
			<richtext>
				<p>OWL 1.1 extends the W3C OWL Web Ontology Language with a small but useful set of features that have been requested by users, for which effective reasoning algorithms are now available, and that OWL tool developers are willing to support. The new features include extra syntactic sugar, additional property and qualified cardinality constructors, extended datatype support, simple metamodeling, and extended annotations. This document provides a model-theoretic semantics for OWL 1.1.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-owl11-semantics-20080108</howpublished>
		<title type="sharef:primaryTitle">OWL 1.1 Web Ontology Language: Model-Theoretic Semantics</title>
		<field type="bibtex:topic">owl[1]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2008/WD-owl11-semantics-20080108</identifier>
	</reference>
	<reference name="owl11mappingtordf" src="bibtex:misc" src-info="bibtex:line-31478" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Bernardo Cuenca</givenname>
				<surname>Grau</surname>
			</person>
			<person>
				<givenname>Boris</givenname>
				<surname>Motik</surname>
			</person>
		</names>
		<date value="2008-01"/>
		<abstract>
			<richtext>
				<p>OWL 1.1 extends the W3C OWL Web Ontology Language with a small but useful set of features that have been requested by users, for which effective reasoning algorithms are now available, and that OWL tool developers are willing to support. The new features include extra syntactic sugar, additional property and qualified cardinality constructors, extended datatype support, simple metamodeling, and extended annotations. This document provides a mapping from the functional-style syntax of OWL 1.1 to the RDF exchange syntax for OWL 1.1, and vice versa.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-owl11-mapping-to-rdf-20080108</howpublished>
		<title type="sharef:primaryTitle">OWL 1.1 Web Ontology Language: Mapping to RDF Graphs</title>
		<field type="bibtex:topic">owl[0.9] rdf[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2008/WD-owl11-mapping-to-rdf-20080108</identifier>
	</reference>
	<reference name="owl2newfeatures" src="bibtex:misc" src-info="bibtex:line-31489" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Christine</givenname>
				<surname>Golbreich</surname>
			</person>
			<person>
				<givenname>Evan K.</givenname>
				<surname>Wallace</surname>
			</person>
		</names>
		<date value="2009-10"/>
		<abstract>
			<richtext>
				<p>The OWL 2 Web Ontology Language, informally OWL 2, is an ontology language for the Semantic Web with formally defined meaning. OWL 2 ontologies provide classes, properties, individuals, and data values and are stored as Semantic Web documents. OWL 2 ontologies can be used along with information written in RDF, and OWL 2 ontologies themselves are primarily exchanged as RDF documents. The OWL 2 Document Overview describes the overall state of OWL 2, and should be read before other OWL 2 documents. This document is a simple introduction to the new features of the OWL 2 Web Ontology Language, including an explanation of the differences between the initial version of OWL and OWL 2. The document also presents the requirements that have motivated the design of the main new features, and their rationale from a theoretical and implementation perspective.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Recommendation REC-owl2-new-features-20091027</howpublished>
		<title type="sharef:primaryTitle">OWL 2 Web Ontology Language — New Features and Rationale</title>
		<field type="bibtex:topic">owl[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2009/REC-owl2-new-features-20091027</identifier>
	</reference>
	<reference name="owl2overview" src="bibtex:misc" src-info="bibtex:line-31500" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<surname>W3C OWL Working Group</surname>
			</person>
		</names>
		<date value="2009-10"/>
		<abstract>
			<richtext>
				<p>The OWL 2 Web Ontology Language, informally OWL 2, is an ontology language for the Semantic Web with formally defined meaning. OWL 2 ontologies provide classes, properties, individuals, and data values and are stored as Semantic Web documents. OWL 2 ontologies can be used along with information written in RDF, and OWL 2 ontologies themselves are primarily exchanged as RDF documents. This document serves as an introduction to OWL 2 and the various other OWL 2 documents. It describes the syntaxes for OWL 2, the different kinds of semantics, the available profiles (sub-languages), and the relationship between OWL 1 and OWL 2.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Recommendation REC-owl2-overview-20091027</howpublished>
		<title type="sharef:primaryTitle">OWL 2 Web Ontology Language — Document Overview</title>
		<field type="bibtex:topic">owl[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2009/REC-owl2-overview-20091027</identifier>
	</reference>
	<reference name="owl2syntax" src="bibtex:misc" src-info="bibtex:line-31511" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Boris</givenname>
				<surname>Motik</surname>
			</person>
			<person>
				<givenname>Peter F.</givenname>
				<surname>Patel-Schneider</surname>
			</person>
			<person>
				<givenname>Bijan</givenname>
				<surname>Parsia</surname>
			</person>
		</names>
		<date value="2009-10"/>
		<abstract>
			<richtext>
				<p>The OWL 2 Web Ontology Language, informally OWL 2, is an ontology language for the Semantic Web with formally defined meaning. OWL 2 ontologies provide classes, properties, individuals, and data values and are stored as Semantic Web documents. OWL 2 ontologies can be used along with information written in RDF, and OWL 2 ontologies themselves are primarily exchanged as RDF documents. The OWL 2 Document Overview describes the overall state of OWL 2, and should be read before other OWL 2 documents. The meaningful constructs provided by OWL 2 are defined in terms of their structure. As well, a functional-style syntax is defined for these constructs, with examples and informal descriptions. One can reason with OWL 2 ontologies under either the RDF-Based Semantics or the Direct Semantics. If certain restrictions on OWL 2 ontologies are satisfied and the ontology is in OWL 2 DL, reasoning under the Direct Semantics can be implemented using techniques well known in the literature.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Recommendation REC-owl2-syntax-20091027</howpublished>
		<title type="sharef:primaryTitle">OWL 2 Web Ontology Language — Structural Specification and Functional-Style Syntax</title>
		<field type="bibtex:topic">owl[1]</field>
		<field type="bibtex:updates">owl11syntax</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2009/REC-owl2-syntax-20091027</identifier>
	</reference>
	<reference name="owl2manchestersyntax" src="bibtex:misc" src-info="bibtex:line-31523" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Matthew</givenname>
				<surname>Horridge</surname>
			</person>
			<person>
				<givenname>Peter F.</givenname>
				<surname>Patel-Schneider</surname>
			</person>
		</names>
		<date value="2009-10"/>
		<abstract>
			<richtext>
				<p>The OWL 2 Web Ontology Language, informally OWL 2, is an ontology language for the Semantic Web with formally defined meaning. OWL 2 ontologies provide classes, properties, individuals, and data values and are stored as Semantic Web documents. OWL 2 ontologies can be used along with information written in RDF, and OWL 2 ontologies themselves are primarily exchanged as RDF documents. The OWL 2 Document Overview describes the overall state of OWL 2, and should be read before other OWL 2 documents. The Manchester syntax is a user-friendly compact syntax for OWL 2 ontologies; it is frame-based, as opposed to the axiom-based other syntaxes for OWL 2. The Manchester Syntax is used in the OWL 2 Primer, and this document provides the language used there. It is expected that tools will extend the Manchester Syntax for their own purposes, and tool builders may collaboratively extend the common language.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Note NOTE-owl2-manchester-syntax-20091027</howpublished>
		<title type="sharef:primaryTitle">OWL 2 Web Ontology Language — Manchester Syntax</title>
		<field type="bibtex:topic">owl[1]</field>
		<field type="bibtex:updates">owl11syntax</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2009/NOTE-owl2-manchester-syntax-20091027</identifier>
	</reference>
	<reference name="owl2semantics" src="bibtex:misc" src-info="bibtex:line-31535" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Boris</givenname>
				<surname>Motik</surname>
			</person>
			<person>
				<givenname>Peter F.</givenname>
				<surname>Patel-Schneider</surname>
			</person>
			<person>
				<givenname>Bernardo Cuenca</givenname>
				<surname>Grau</surname>
			</person>
		</names>
		<date value="2009-10"/>
		<abstract>
			<richtext>
				<p>The OWL 2 Web Ontology Language, informally OWL 2, is an ontology language for the Semantic Web with formally defined meaning. OWL 2 ontologies provide classes, properties, individuals, and data values and are stored as Semantic Web documents. OWL 2 ontologies can be used along with information written in RDF, and OWL 2 ontologies themselves are primarily exchanged as RDF documents. The OWL 2 Document Overview describes the overall state of OWL 2, and should be read before other OWL 2 documents. This document provides the direct model-theoretic semantics for OWL 2, which is compatible with the description logic SROIQ. Furthermore, this document defines the most common inference problems for OWL 2.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Recommendation REC-owl2-direct-semantics-20091027</howpublished>
		<title type="sharef:primaryTitle">OWL 2 Web Ontology Language — Direct Semantics</title>
		<field type="bibtex:topic">owl[1]</field>
		<field type="bibtex:updates">owl11semantics</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2009/REC-owl2-direct-semantics-20091027</identifier>
	</reference>
	<reference name="owl2rdfbasedsemantics" src="bibtex:misc" src-info="bibtex:line-31547" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Michael</givenname>
				<surname>Schneider</surname>
			</person>
		</names>
		<date value="2009-10"/>
		<abstract>
			<richtext>
				<p>The OWL 2 Web Ontology Language, informally OWL 2, is an ontology language for the Semantic Web with formally defined meaning. OWL 2 ontologies provide classes, properties, individuals, and data values and are stored as Semantic Web documents. OWL 2 ontologies can be used along with information written in RDF, and OWL 2 ontologies themselves are primarily exchanged as RDF documents. The OWL 2 Document Overview describes the overall state of OWL 2, and should be read before other OWL 2 documents. This document defines the RDF-compatible model-theoretic semantics of OWL 2.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Recommendation REC-owl2-rdf-based-semantics-20091027</howpublished>
		<title type="sharef:primaryTitle">OWL 2 Web Ontology Language — RDF-Based Semantics</title>
		<field type="bibtex:topic">owl[0.9] rdf[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2009/REC-owl2-rdf-based-semantics-20091027</identifier>
	</reference>
	<reference name="owl2test" src="bibtex:misc" src-info="bibtex:line-31558" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Michael K.</givenname>
				<surname>Smith</surname>
			</person>
			<person>
				<givenname>Ian</givenname>
				<surname>Horrocks</surname>
			</person>
			<person>
				<givenname>Markus</givenname>
				<surname>Krötzsch</surname>
			</person>
			<person>
				<givenname>Birte</givenname>
				<surname>Glimm</surname>
			</person>
		</names>
		<date value="2009-10"/>
		<abstract>
			<richtext>
				<p>The OWL 2 Web Ontology Language, informally OWL 2, is an ontology language for the Semantic Web with formally defined meaning. OWL 2 ontologies provide classes, properties, individuals, and data values and are stored as Semantic Web documents. OWL 2 ontologies can be used along with information written in RDF, and OWL 2 ontologies themselves are primarily exchanged as RDF documents. The OWL 2 Document Overview describes the overall state of OWL 2, and should be read before other OWL 2 documents. This document describes the conditions that OWL 2 tools must satisfy in order to be conformant with the language specification. It also presents a common format for OWL 2 test cases that both illustrate the features of the language and can be used for testing conformance.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Recommendation REC-owl2-conformance-20091027</howpublished>
		<title type="sharef:primaryTitle">OWL 2 Web Ontology Language — Conformance</title>
		<field type="bibtex:topic">owl[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2009/REC-owl2-conformance-20091027</identifier>
	</reference>
	<reference name="owl2mappingtordf" src="bibtex:misc" src-info="bibtex:line-31569" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Peter F.</givenname>
				<surname>Patel-Schneider</surname>
			</person>
			<person>
				<givenname>Boris</givenname>
				<surname>Motik</surname>
			</person>
		</names>
		<date value="2009-10"/>
		<abstract>
			<richtext>
				<p>The OWL 2 Web Ontology Language, informally OWL 2, is an ontology language for the Semantic Web with formally defined meaning. OWL 2 ontologies provide classes, properties, individuals, and data values and are stored as Semantic Web documents. OWL 2 ontologies can be used along with information written in RDF, and OWL 2 ontologies themselves are primarily exchanged as RDF documents. The OWL 2 Document Overview describes the overall state of OWL 2, and should be read before other OWL 2 documents. This document defines the mapping of OWL 2 ontologies into RDF graphs, and vice versa.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Recommendation REC-owl2-mapping-to-rdf-20091027</howpublished>
		<title type="sharef:primaryTitle">OWL 2 Web Ontology Language — Mapping to RDF Graphs</title>
		<field type="bibtex:topic">owl[0.9] rdf[0.9]</field>
		<field type="bibtex:updates">owl11mappingtordf</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2009/REC-owl2-mapping-to-rdf-20091027</identifier>
	</reference>
	<reference name="owl2xmlserialization" src="bibtex:misc" src-info="bibtex:line-31581" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Boris</givenname>
				<surname>Motik</surname>
			</person>
			<person>
				<givenname>Bijan</givenname>
				<surname>Parsia</surname>
			</person>
			<person>
				<givenname>Peter F.</givenname>
				<surname>Patel-Schneider</surname>
			</person>
		</names>
		<date value="2009-10"/>
		<abstract>
			<richtext>
				<p>The OWL 2 Web Ontology Language, informally OWL 2, is an ontology language for the Semantic Web with formally defined meaning. OWL 2 ontologies provide classes, properties, individuals, and data values and are stored as Semantic Web documents. OWL 2 ontologies can be used along with information written in RDF, and OWL 2 ontologies themselves are primarily exchanged as RDF documents. The OWL 2 Document Overview describes the overall state of OWL 2, and should be read before other OWL 2 documents. This document specifies an XML serialization for OWL 2 that mirrors its structural specification. An XML schema defines this syntax and is available as a separate document, as well as being included here.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Recommendation REC-owl2-xml-serialization-20091027</howpublished>
		<title type="sharef:primaryTitle">OWL 2 Web Ontology Language — XML Serialization</title>
		<field type="bibtex:topic">owl[0.9] xml[0.8]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2009/REC-owl2-xml-serialization-20091027</identifier>
	</reference>
	<reference name="owl2profiles" src="bibtex:misc" src-info="bibtex:line-31592" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Boris</givenname>
				<surname>Motik</surname>
			</person>
			<person>
				<givenname>Bernardo Cuenca</givenname>
				<surname>Grau</surname>
			</person>
			<person>
				<givenname>Ian</givenname>
				<surname>Horrocks</surname>
			</person>
			<person>
				<givenname>Zhe</givenname>
				<surname>Wu</surname>
			</person>
			<person>
				<givenname>Achille</givenname>
				<surname>Fokoue</surname>
			</person>
			<person>
				<givenname>Carsten</givenname>
				<surname>Lutz</surname>
			</person>
		</names>
		<date value="2009-10"/>
		<abstract>
			<richtext>
				<p>The OWL 2 Web Ontology Language, informally OWL 2, is an ontology language for the Semantic Web with formally defined meaning. OWL 2 ontologies provide classes, properties, individuals, and data values and are stored as Semantic Web documents. OWL 2 ontologies can be used along with information written in RDF, and OWL 2 ontologies themselves are primarily exchanged as RDF documents. The OWL 2 Document Overview describes the overall state of OWL 2, and should be read before other OWL 2 documents. This document provides a specification of several profiles of OWL 2 which can be more simply and/or efficiently implemented. In logic, profiles are often called fragments. Most profiles are defined by placing restrictions on the structure of OWL 2 ontologies. These restrictions have been specified by modifying the productions of the functional-style syntax.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Recommendation REC-owl2-profiles-20091027</howpublished>
		<title type="sharef:primaryTitle">OWL 2 Web Ontology Language — Profiles</title>
		<field type="bibtex:topic">owl[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2009/REC-owl2-profiles-20091027</identifier>
	</reference>
	<reference name="owl2primer" src="bibtex:misc" src-info="bibtex:line-31603" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Pascal</givenname>
				<surname>Hitzler</surname>
			</person>
			<person>
				<givenname>Markus</givenname>
				<surname>Krötzsch</surname>
			</person>
			<person>
				<givenname>Bijan</givenname>
				<surname>Parsia</surname>
			</person>
			<person>
				<givenname>Peter F.</givenname>
				<surname>Patel-Schneider</surname>
			</person>
			<person>
				<givenname>Sebastian</givenname>
				<surname>Rudolph</surname>
			</person>
		</names>
		<date value="2009-10"/>
		<abstract>
			<richtext>
				<p>The OWL 2 Web Ontology Language, informally OWL 2, is an ontology language for the Semantic Web with formally defined meaning. OWL 2 ontologies provide classes, properties, individuals, and data values and are stored as Semantic Web documents. OWL 2 ontologies can be used along with information written in RDF, and OWL 2 ontologies themselves are primarily exchanged as RDF documents. The OWL 2 Document Overview describes the overall state of OWL 2, and should be read before other OWL 2 documents. This primer provides an approachable introduction to OWL 2, including orientation for those coming from other disciplines, a running example showing how OWL 2 can be used to represent first simple information and then more complex information, how OWL 2 manages ontologies, and finally the distinctions between the various sublanguages of OWL 2.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Recommendation REC-owl2-primer-20091027</howpublished>
		<title type="sharef:primaryTitle">OWL 2 Web Ontology Language — Primer</title>
		<field type="bibtex:topic">owl[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2009/REC-owl2-primer-20091027</identifier>
	</reference>
	<reference name="owl2quickreference" src="bibtex:misc" src-info="bibtex:line-31614" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Jie</givenname>
				<surname>Bao</surname>
			</person>
			<person>
				<givenname>Elisa F.</givenname>
				<surname>Kendall</surname>
			</person>
			<person>
				<givenname>Deborah L.</givenname>
				<surname>McGuinness</surname>
			</person>
			<person>
				<givenname>Peter F.</givenname>
				<surname>Patel-Schneider</surname>
			</person>
		</names>
		<date value="2009-10"/>
		<abstract>
			<richtext>
				<p>The OWL 2 Web Ontology Language, informally OWL 2, is an ontology language for the Semantic Web with formally defined meaning. OWL 2 ontologies provide classes, properties, individuals, and data values and are stored as Semantic Web documents. OWL 2 ontologies can be used along with information written in RDF, and OWL 2 ontologies themselves are primarily exchanged as RDF documents. The OWL 2 Document Overview describes the overall state of OWL 2, and should be read before other OWL 2 documents. This document provides a non-normative quick reference guide to the OWL 2 language. It also provides links to other documents, including the OWL 2 Primer for language introduction and examples, the OWL 2 Structural Specification and Functional Syntax document for more details of the functional syntax, and the OWL 2 New Features and Rationale document for new feature descriptions.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Recommendation REC-owl2-quick-reference-20091027</howpublished>
		<title type="sharef:primaryTitle">OWL 2 Web Ontology Language — Quick Reference Guide</title>
		<field type="bibtex:topic">owl[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2009/REC-owl2-quick-reference-20091027</identifier>
	</reference>
	<reference name="owl2drlinear" src="bibtex:misc" src-info="bibtex:line-31625" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Bijan</givenname>
				<surname>Parsia</surname>
			</person>
			<person>
				<givenname>Uli</givenname>
				<surname>Sattler</surname>
			</person>
		</names>
		<date value="2009-10"/>
		<abstract>
			<richtext>
				<p>The OWL 2 Web Ontology Language, informally OWL 2, is an ontology language for the Semantic Web with formally defined meaning. OWL 2 ontologies provide classes, properties, individuals, and data values and are stored as Semantic Web documents. OWL 2 ontologies can be used along with information written in RDF, and OWL 2 ontologies themselves are primarily exchanged as RDF documents. The OWL 2 Document Overview describes the overall state of OWL 2, and should be read before other OWL 2 documents. This document specifies a syntax and semantics for incorporating linear equations with rational coefficients solved in the reals in OWL 2.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Note NOTE-owl2-dr-linear-20091027</howpublished>
		<title type="sharef:primaryTitle">OWL 2 Web Ontology Language — Data Range Extension: Linear Equations</title>
		<field type="bibtex:topic">owl[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2009/NOTE-owl2-dr-linear-20091027</identifier>
	</reference>
	<reference name="rdftext" src="bibtex:misc" src-info="bibtex:line-31636" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Jie</givenname>
				<surname>Bao</surname>
			</person>
			<person>
				<givenname>Axel</givenname>
				<surname>Polleres</surname>
			</person>
			<person>
				<givenname>Boris</givenname>
				<surname>Motik</surname>
			</person>
		</names>
		<date value="2009-10"/>
		<abstract>
			<richtext>
				<p>This document presents the specification of a primitive datatype for the plain literals of RDF.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Recommendation REC-rdf-plain-literal-20091027</howpublished>
		<title type="sharef:primaryTitle">rdf:PlainLiteral: A Datatype for RDF Plain Literals</title>
		<field type="bibtex:topic">rif[0.8] owl[0.8]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2009/REC-rdf-plain-literal-20091027</identifier>
	</reference>
	<reference name="wordnetrdf" src="bibtex:misc" src-info="bibtex:line-31647" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Mark</givenname>
				<surname link="van">Assem</surname>
			</person>
			<person>
				<givenname>Aldo</givenname>
				<surname>Gangemi</surname>
			</person>
			<person>
				<givenname>Guus</givenname>
				<surname>Schreiber</surname>
			</person>
		</names>
		<date value="2006-06"/>
		<abstract>
			<richtext>
				<p>This document presents a standard conversion of Princeton WordNet to RDF/OWL. It describes how it was converted and gives examples of how it may be queried for use in Semantic Web applications.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-wordnet-rdf-20060619</howpublished>
		<title type="sharef:primaryTitle">RDF/OWL Representation of WordNet</title>
		<field type="bibtex:topic">owl[0.9] rdf[0.7] wordnet[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2006/WD-wordnet-rdf-20060619</identifier>
	</reference>
	<reference name="rdftmsurvey" src="bibtex:misc" src-info="bibtex:line-31658" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Steve</givenname>
				<surname>Pepper</surname>
			</person>
			<person>
				<givenname>Fabio</givenname>
				<surname>Vitali</surname>
			</person>
			<person>
				<givenname>Lars Marius</givenname>
				<surname>Garshol</surname>
			</person>
			<person>
				<givenname>Nicola</givenname>
				<surname>Gessa</surname>
			</person>
			<person>
				<givenname>Valentina</givenname>
				<surname>Presutti</surname>
			</person>
		</names>
		<date value="2006-02"/>
		<abstract>
			<richtext>
				<p>The Resource Description Framework (RDF) is a model developed by the W3C for representing information about resources in the World Wide Web. Topic Maps is a standard for knowledge integration developed by the ISO. This document contains a survey of existing proposals for integrating RDF and Topic Maps data and is intended to be a starting point for establishing standard guidelines for RDF/Topic Maps interoperability.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Note NOTE-rdftm-survey-20060210</howpublished>
		<title type="sharef:primaryTitle">A Survey of RDF/Topic Maps Interoperability Proposals</title>
		<field type="bibtex:topic">rdf[0.8] topicmaps[0.8]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2006/NOTE-rdftm-survey-20060210</identifier>
	</reference>
	<reference name="swbpclassesasvalues" src="bibtex:misc" src-info="bibtex:line-31669" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Natalya Fridman</givenname>
				<surname>Noy</surname>
			</person>
		</names>
		<date value="2005-04"/>
		<abstract>
			<richtext>
				<p>This document addresses the issue of using classes as property values in OWL and RDF Schema. It is often convenient to put a class (e.g., Animal) as a property value (e.g., topic or book subject) when building an ontology. While OWL Full and RDF Schema do not put any restriction on using classes as property values, in OWL DL and OWL Lite most properties cannot have classes as their values. We illustrate the direct approach for representing classes as property values in OWL-Full and RDF Schema. We present various alternative mechanisms for representing the required information in OWL DL and OWL Lite. For each approach, we discuss various considerations that the users should keep in mind when choosing the best approach for their purposes.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Note NOTE-swbp-classes-as-values-20050405</howpublished>
		<title type="sharef:primaryTitle">Representing Classes As Property Values on the Semantic Web</title>
		<field type="bibtex:topic">owl[0.8] rdfs[0.8]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2005/NOTE-swbp-classes-as-values-20050405</identifier>
	</reference>
	<reference name="swbpnaryrelations" src="bibtex:misc" src-info="bibtex:line-31680" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Natalya Fridman</givenname>
				<surname>Noy</surname>
			</person>
			<person>
				<givenname>Alan</givenname>
				<surname>Rector</surname>
			</person>
		</names>
		<date value="2006-04"/>
		<abstract>
			<richtext>
				<p>In Semantic Web languages, such as RDF and OWL, a property is a binary relation: it is used to link two individuals or an individual and a value. However, in some cases, the natural and convenient way to represent certain concepts is to use relations to link an individual to more than just one individual or value. These relations are called n-ary relations. For example, we may want to represent properties of a relation, such as our certainty about it, severity or strength of a relation, relevance of a relation, and so on. Another example is representing relations among multiple individuals, such as a buyer, a seller, and an object that was bought when describing a purchase of a book. This document presents ontology patterns for representing n-ary relations in RDF and OWL and discusses what users must consider when choosing these patterns.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Note NOTE-swbp-n-aryRelations-20060412</howpublished>
		<title type="sharef:primaryTitle">Defining N-ary Relations on the Semantic Web</title>
		<field type="bibtex:topic">owl[0.8] rdfs[0.8]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2006/NOTE-swbp-n-aryRelations-20060412</identifier>
	</reference>
	<reference name="swbpimageannotation" src="bibtex:misc" src-info="bibtex:line-31691" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Raphaël</givenname>
				<surname>Troncy</surname>
			</person>
			<person>
				<givenname>Jacco</givenname>
				<surname link="van">Ossenbruggen</surname>
			</person>
			<person>
				<givenname>Jeff Z.</givenname>
				<surname>Pan</surname>
			</person>
			<person>
				<givenname>Giorgos</givenname>
				<surname>Stamou</surname>
			</person>
		</names>
		<date value="2007-08"/>
		<abstract>
			<richtext>
				<p>Many applications that process multimedia assets make use of some form of metadata that describe the multimedia content. The goals of this document are to explain the advantages of using Semantic Web languages and technologies for the creation, storage, manipulation, interchange and processing of image metadata. In addition, it provides guidelines for Semantic Web-based image annotation, illustrated by use cases. Relevant RDF and OWL vocabularies are discussed, along with a short overview of publicly available tools.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Incubator Group Report XGR-image-annotation-20070814</howpublished>
		<title type="sharef:primaryTitle">Image Annotation on the Semantic Web</title>
		<field type="bibtex:topic">imageformat[0.7]</field>
		<identifier type="sharef:uri">http://www.w3.org/2005/Incubator/mmsem/XGR-image-annotation-20070814</identifier>
	</reference>
	<reference name="swoosdprimer" src="bibtex:misc" src-info="bibtex:line-31702" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Holger</givenname>
				<surname>Knublauch</surname>
			</person>
			<person>
				<givenname>Daniel</givenname>
				<surname>Oberle</surname>
			</person>
			<person>
				<givenname>Phil</givenname>
				<surname>Tetlow</surname>
			</person>
			<person>
				<givenname>Evan</givenname>
				<surname>Wallace</surname>
			</person>
		</names>
		<date value="2006-03"/>
		<abstract>
			<richtext>
				<p>Domain models play a central role throughout the software development cycle, from requirements analysis to design, through implementation and beyond. As such, great progress has been made in the consistent use of models throughout this process. Modern software development tools with support for the UML and code generation as well as Model-Driven Architectures allow for developers to synchronize and verify technical implementation with user requirements using models. However, the reusability of domain models is often limited because they are, by definition, domain specific and only take into consideration abstractions needed to make possible a solution within the confines of their own individual problem space. But the Web is broader than that and provides a multidimensional solution space capable of referencing an almost limitless set of domains. While much of our software becomes increasingly embedded in the Web, our development processes do not fully exploit the potential of model reuse from the Web yet. This note therefore introduces Semantic Web languages such as RDF Schema and OWL, and shows how they can be used in tandem with mainstream object-oriented languages. We show that the Semantic Web can serve as a platform on which domain models can be created, shared and reused.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Note NOTE-sw-oosd-primer-20060309</howpublished>
		<title type="sharef:primaryTitle">A Semantic Web Primer for Object-Oriented Software Developers</title>
		<identifier type="sharef:uri">http://www.w3.org/TR/2006/NOTE-sw-oosd-primer-20060309</identifier>
	</reference>
	<reference name="swbpspecifiedvalues" src="bibtex:misc" src-info="bibtex:line-31712" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Alan</givenname>
				<surname>Rector</surname>
			</person>
		</names>
		<date value="2005-05"/>
		<abstract>
			<richtext>
				<p>Modelling various descriptive "features" (also known variously as "qualities", "attributes" or "modifiers") is a frequent requirement when creating ontologies. For example: "size" may describe persons or other physical objects and be constrained to take the values "small", "medium" or "large"; rank may describe military officers and restricted to a specific list of values depending on the military organisation. In OWL such descriptive features are modelled as properties whose range specifies the constraints on the values that the property can take on. This document describes two methods to represent such features and their specified values: 1) as partitions of classes; and 2) as enumerations of individuals. It does not discuss the use of datatypes to represent lists of values.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Note NOTE-swbp-specified-values-20050517</howpublished>
		<title type="sharef:primaryTitle">Representing Specified Values in OWL: "value partitions" and "value sets"</title>
		<field type="bibtex:topic">owl[0.8]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2005/NOTE-swbp-specified-values-20050517</identifier>
	</reference>
	<reference name="swbpxschdatatypes" src="bibtex:misc" src-info="bibtex:line-31723" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Jeremy J.</givenname>
				<surname>Carroll</surname>
			</person>
			<person>
				<givenname>Jeff Z.</givenname>
				<surname>Pan</surname>
			</person>
		</names>
		<date value="2006-03"/>
		<abstract>
			<richtext>
				<p>The RDF and OWL Recommendations use the simple types from XML Schema. This document discusses three questions left unanswered by these Recommendations: What URIref should be used to refer to a user defined datatype? Which values of which XML Schema simple types are the same? How to use the problematic xsd:duration in RDF and OWL? In addition, we further describe how to integrate OWL DL with user defined datatypes.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Note NOTE-swbp-xsch-datatypes-20060314</howpublished>
		<title type="sharef:primaryTitle">XML Schema Datatypes in RDF and OWL</title>
		<field type="bibtex:topic">owl[0.8] rdf[0.8] xsd[0.7]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2006/NOTE-swbp-xsch-datatypes-20060314</identifier>
	</reference>
	<reference name="swbpvocabpub" src="bibtex:misc" src-info="bibtex:line-31734" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Diego</givenname>
				<surname>Berrueta</surname>
			</person>
			<person>
				<givenname>Jon</givenname>
				<surname>Phipps</surname>
			</person>
		</names>
		<date value="2008-08"/>
		<abstract>
			<richtext>
				<p>This document describes best practice recipes for publishing vocabularies or ontologies on the Web (in RDF Schema or OWL). The features of each recipe are described in detail, so that vocabulary designers may choose the recipe best suited to their needs. Each recipe introduces general principles and an example configuration for use with an Apache HTTP server (which may be adapted to other environments). The recipes are all designed to be consistent with the architecture of the Web as currently specified, although the associated example configurations have been kept intentionally simple.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Note NOTE-swbp-vocab-pub-20080828</howpublished>
		<title type="sharef:primaryTitle">Best Practice Recipes for Publishing RDF Vocabularies</title>
		<field type="bibtex:topic">rdfs[0.8] owl[0.8]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2008/NOTE-swbp-vocab-pub-20080828</identifier>
	</reference>
	<reference name="swbpthesauruspubguide" src="bibtex:misc" src-info="bibtex:line-31745" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Alistair</givenname>
				<surname>Miles</surname>
			</person>
		</names>
		<date value="2005-05"/>
		<abstract>
			<richtext>
				<p>This document describes in brief how to express the content and structure of a thesaurus, and metadata about a thesaurus, in RDF. Using RDF allows data to be linked to and/or merged with other RDF data by semantic web applications. The Semantic Web, which is based on the Resource Description Framework (RDF), provides a common framework that allows data to be shared and reused across application, enterprise, and community boundaries.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-swbp-thesaurus-pubguide-20050517</howpublished>
		<title type="sharef:primaryTitle">Quick Guide to Publishing a Thesaurus on the Semantic Web</title>
		<identifier type="sharef:uri">http://www.w3.org/TR/2005/WD-swbp-thesaurus-pubguide-20050517</identifier>
	</reference>
	<reference name="swbpskoscoreguide" src="bibtex:misc" src-info="bibtex:line-31755" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Alistair</givenname>
				<surname>Miles</surname>
			</person>
			<person>
				<givenname>Dan</givenname>
				<surname>Brickley</surname>
			</person>
		</names>
		<date value="2005-11"/>
		<abstract>
			<richtext>
				<p>SKOS Core provides a model for expressing the basic structure and content of concept schemes (thesauri, classification schemes, subject heading lists, taxonomies, terminologies, glossaries and other types of controlled vocabulary). The SKOS Core Vocabulary is an application of the Resource Description Framework (RDF), that can be used to express a concept scheme as an RDF graph. Using RDF allows data to be linked to and/or merged with other RDF data by semantic web applications. This document is a guide using the SKOS Core Vocabulary, for readers who already have a basic understanding of RDF concepts. This edition of the SKOS Core Guide is a W3C Public Working Draft. It is the authoritative guide to recommended usage of the SKOS Core Vocabulary at the time of publication.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-swbp-skos-core-guide-20051102</howpublished>
		<title type="sharef:primaryTitle">SKOS Core Guide</title>
		<field type="bibtex:topic">skos[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2005/WD-swbp-skos-core-guide-20051102</identifier>
	</reference>
	<reference name="swbpskoscorespec" src="bibtex:misc" src-info="bibtex:line-31766" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Alistair</givenname>
				<surname>Miles</surname>
			</person>
			<person>
				<givenname>Dan</givenname>
				<surname>Brickley</surname>
			</person>
		</names>
		<date value="2005-11"/>
		<abstract>
			<richtext>
				<p>SKOS Core is a model for expressing the structure and content of concept schemes (thesauri, classification schemes, subject heading lists, taxonomies, terminologies, glossaries and other types of controlled vocabulary). The SKOS Core Vocabulary is an application of the Resource Description Framework (RDF), that can be used to express a concept scheme as an RDF graph. Using RDF allows data to be linked to and/or merged with other RDF data by semantic web applications. This document gives a reference-style overview of the SKOS Core Vocabulary as it stands at the time of publication. It also describes the policies for ownership, naming, persistence and change by which the SKOS Core Vocabulary is managed. This edition of the SKOS Core Vocabulary Specification is a W3C Public Working Draft. It is the authoritative human-readable account of the SKOS Core Vocabulary at the time of publication.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-swbp-skos-core-spec-20051102</howpublished>
		<title type="sharef:primaryTitle">SKOS Core Vocabulary Specification</title>
		<field type="bibtex:topic">skos[1]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2005/WD-swbp-skos-core-spec-20051102</identifier>
	</reference>
	<reference name="skosreference" src="bibtex:misc" src-info="bibtex:line-31777" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Alistair</givenname>
				<surname>Miles</surname>
			</person>
			<person>
				<givenname>Sean</givenname>
				<surname>Bechhofer</surname>
			</person>
		</names>
		<date value="2009-08"/>
		<abstract>
			<richtext>
				<p>This document defines the Simple Knowledge Organization System (SKOS), a common data model for sharing and linking knowledge organization systems via the Web. Many knowledge organization systems, such as thesauri, taxonomies, classification schemes and subject heading systems, share a similar structure, and are used in similar applications. SKOS captures much of this similarity and makes it explicit, to enable data and technology sharing across diverse applications. The SKOS data model provides a standard, low-cost migration path for porting existing knowledge organization systems to the Semantic Web. SKOS also provides a light weight, intuitive language for developing and sharing new knowledge organization systems. It may be used on its own, or in combination with formal knowledge representation languages such as the Web Ontology language (OWL). This document is the normative specification of the Simple Knowledge Organization System. It is intended for readers who are involved in the design and implementation of information systems, and who already have a good understanding of Semantic Web technology, especially RDF and OWL.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Recommendation REC-skos-reference-20090818</howpublished>
		<title type="sharef:primaryTitle">SKOS Simple Knowledge Organization System Reference</title>
		<field type="bibtex:topic">skos[1]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2009/REC-skos-reference-20090818</identifier>
	</reference>
	<reference name="skosprimer" src="bibtex:misc" src-info="bibtex:line-31788" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Antoine</givenname>
				<surname>Isaac</surname>
			</person>
			<person>
				<givenname>Ed</givenname>
				<surname>Summers</surname>
			</person>
		</names>
		<date value="2009-08"/>
		<abstract>
			<richtext>
				<p>SKOS — Simple Knowledge Organization System — provides a model for expressing the basic structure and content of concept schemes such as thesauri, classification schemes, subject heading lists, taxonomies, folksonomies, and other similar types of controlled vocabulary. As an application of the Resource Description Framework (RDF), SKOS allows concepts to be composed and published on the World Wide Web, linked with data on the Web and integrated into other concept schemes. This document is a user guide for those who would like to represent their concept scheme using SKOS. In basic SKOS, conceptual resources (concepts) are identified with URIs, labeled with strings in one or more natural languages, documented with various types of note, semantically related to each other in informal hierarchies and association networks, and aggregated into concept schemes. In advanced SKOS, conceptual resources can be mapped across concept schemes and grouped into labeled or ordered collections. Relationships between concept labels can be specified. Finally, the SKOS vocabulary itself can be extended to suit the needs of particular communities of practice or combined with other modeling vocabularies. This document is a companion to the SKOS Reference, which gives the normative reference on SKOS.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Note NOTE-skos-primer-20090818</howpublished>
		<title type="sharef:primaryTitle">SKOS Simple Knowledge Organization System Primer</title>
		<field type="bibtex:topic">skos[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2009/NOTE-skos-primer-20090818</identifier>
	</reference>
	<reference name="vbireqs" src="bibtex:misc" src-info="bibtex:line-31799" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Kenneth G.</givenname>
				<surname>Rehor</surname>
			</person>
		</names>
		<date value="2002-08"/>
		<howpublished>World Wide Web Consortium, Working Draft WD-vbi-reqs-20020808</howpublished>
		<title type="sharef:primaryTitle">Voice Browser Interoperation: Requirements</title>
		<identifier type="sharef:uri">http://www.w3.org/TR/2002/WD-vbi-reqs-20020808</identifier>
	</reference>
	<reference name="ccxml10" src="bibtex:misc" src-info="bibtex:line-31808" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>R. J.</givenname>
				<surname>Auburn</surname>
			</person>
		</names>
		<date value="2010-04"/>
		<abstract>
			<richtext>
				<p>This document describes CCXML, or the Call Control Extensible Markup Language. CCXML is designed to provide telephony call control support for dialog systems, such as VoiceXML. While CCXML can be used with any dialog systems capable of handling media, CCXML has been designed to complement and integrate with a VoiceXML interpreter. Because of this there are many references to VoiceXML's capabilities and limitations. There are also details on how VoiceXML and CCXML can be integrated. However, it should be noted that the two languages are separate and are not required in an implementation of either language. For example, CCXML could be integrated with a more traditional Interactive Voice Response (IVR) system or a 3GPP Media Resource Function (MRF), and VoiceXML or other dialog systems could be integrated with other call control systems.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Candidate Recommendation CR-ccxml-20100401</howpublished>
		<title type="sharef:primaryTitle">Voice Browser Call Control: CCXML Version 1.0</title>
		<field type="bibtex:topic">ccxml[1]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2010/CR-ccxml-20100401</identifier>
	</reference>
	<reference name="scxml" src="bibtex:misc" src-info="bibtex:line-31819" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Jim</givenname>
				<surname>Barnett</surname>
			</person>
			<person>
				<givenname>Rahul</givenname>
				<surname>Akolkar</surname>
			</person>
			<person>
				<givenname>R. J.</givenname>
				<surname>Auburn</surname>
			</person>
			<person>
				<givenname>Michael</givenname>
				<surname>Bodell</surname>
			</person>
			<person>
				<givenname>Daniel C.</givenname>
				<surname>Burnett</surname>
			</person>
			<person>
				<givenname>Jerry</givenname>
				<surname>Carter</surname>
			</person>
			<person>
				<givenname>Scott</givenname>
				<surname>McGlashan</surname>
			</person>
			<person>
				<givenname>Torbjörn</givenname>
				<surname>Lager</surname>
			</person>
			<person>
				<givenname>No'am</givenname>
				<surname>Rosenthal</surname>
			</person>
		</names>
		<date value="2010-12"/>
		<abstract>
			<richtext>
				<p>This document describes SCXML, or the "State Chart Extensible Markup Language". SCXML provides a generic state-machine based execution environment based on CCXML and Harel State Tables.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-scxml-20101216</howpublished>
		<title type="sharef:primaryTitle">State Chart XML (SCXML): State Machine Notation for Control Abstraction</title>
		<field type="bibtex:topic">scxml[1]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2010/WD-scxml-20101216</identifier>
	</reference>
	<reference name="xmcl" src="bibtex:misc" src-info="bibtex:line-31830" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Jeffrey</givenname>
				<surname>Ayars</surname>
			</person>
		</names>
		<date value="2002-09"/>
		<howpublished>World Wide Web Consortium, Note NOTE-xmcl-20020919</howpublished>
		<title type="sharef:primaryTitle">XMCL — The Extensible Media Commerce Language</title>
		<field type="bibtex:topic">xmcl[1]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2002/NOTE-xmcl-20020919</identifier>
	</reference>
	<reference name="odrl11" src="bibtex:misc" src-info="bibtex:line-31840" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Renato</givenname>
				<surname>Iannella</surname>
			</person>
		</names>
		<date value="2002-09"/>
		<howpublished>World Wide Web Consortium, Note NOTE-odrl-20020919</howpublished>
		<title type="sharef:primaryTitle">Open Digital Rights Language (ODRL) Version 1.1</title>
		<field type="bibtex:topic">odrl[1]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2002/NOTE-odrl-20020919</identifier>
	</reference>
	<reference name="voicexml10" src="bibtex:misc" src-info="bibtex:line-31850" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Linda</givenname>
				<surname>Boyer</surname>
			</person>
			<person>
				<givenname>Peter</givenname>
				<surname>Danielsen</surname>
			</person>
			<person>
				<givenname>Jim</givenname>
				<surname>Ferrans</surname>
			</person>
			<person>
				<givenname>Gerald</givenname>
				<surname>Karam</surname>
			</person>
			<person>
				<givenname>David</givenname>
				<surname>Ladd</surname>
			</person>
			<person>
				<givenname>Bruce</givenname>
				<surname>Lucas</surname>
			</person>
			<person>
				<givenname>Kenneth G.</givenname>
				<surname>Rehor</surname>
			</person>
		</names>
		<date value="2000-05"/>
		<abstract>
			<richtext>
				<p>This document specifies VoiceXML, the Voice Extensible Markup Language. VoiceXML is designed for creating audio dialogs that feature synthesized speech, digitized audio, recognition of spoken and DTMF key input, recording of spoken input, telephony, and mixed-initiative conversations. Its major goal is to bring the advantages of web-based development and content delivery to interactive voice response applications.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Note NOTE-voicexml-20000505</howpublished>
		<title type="sharef:primaryTitle">Voice Extensible Markup Language (VoiceXML) Version 1.0</title>
		<field type="bibtex:topic">voicexml[1]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2000/NOTE-voicexml-20000505</identifier>
	</reference>
	<reference name="voicexml20" src="bibtex:misc" src-info="bibtex:line-31861" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Scott</givenname>
				<surname>McGlashan</surname>
			</person>
			<person>
				<givenname>Daniel C.</givenname>
				<surname>Burnett</surname>
			</person>
			<person>
				<givenname>Jerry</givenname>
				<surname>Carter</surname>
			</person>
			<person>
				<givenname>Peter</givenname>
				<surname>Danielsen</surname>
			</person>
			<person>
				<givenname>Jim</givenname>
				<surname>Ferrans</surname>
			</person>
			<person>
				<givenname>Andrew</givenname>
				<surname>Hunt</surname>
			</person>
			<person>
				<givenname>Bruce</givenname>
				<surname>Lucas</surname>
			</person>
			<person>
				<givenname>Brad</givenname>
				<surname>Porter</surname>
			</person>
			<person>
				<givenname>Kenneth G.</givenname>
				<surname>Rehor</surname>
			</person>
			<person>
				<givenname>Steph</givenname>
				<surname>Tryphonas</surname>
			</person>
		</names>
		<date value="2004-03"/>
		<abstract>
			<richtext>
				<p>This document specifies VoiceXML, the Voice Extensible Markup Language. VoiceXML is designed for creating audio dialogs that feature synthesized speech, digitized audio, recognition of spoken and DTMF key input, recording of spoken input, telephony, and mixed initiative conversations. Its major goal is to bring the advantages of Web-based development and content delivery to interactive voice response applications.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Recommendation REC-voicexml20-20040316</howpublished>
		<title type="sharef:primaryTitle">Voice Extensible Markup Language (VoiceXML) Version 2.0</title>
		<field type="bibtex:topic">voicexml[1]</field>
		<field type="bibtex:updates">voicexml10</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2004/REC-voicexml20-20040316</identifier>
	</reference>
	<reference name="voicexml21" src="bibtex:misc" src-info="bibtex:line-31873" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Matt</givenname>
				<surname>Oshry</surname>
			</person>
			<person>
				<givenname>R. J.</givenname>
				<surname>Auburn</surname>
			</person>
			<person>
				<givenname>Paolo</givenname>
				<surname>Baggia</surname>
			</person>
			<person>
				<givenname>Michael</givenname>
				<surname>Bodell</surname>
			</person>
			<person>
				<givenname>David</givenname>
				<surname>Burke</surname>
			</person>
			<person>
				<givenname>Daniel C.</givenname>
				<surname>Burnett</surname>
			</person>
			<person>
				<givenname>Emily</givenname>
				<surname>Candell</surname>
			</person>
			<person>
				<givenname>Hakan</givenname>
				<surname>Kilic</surname>
			</person>
			<person>
				<givenname>Jeff</givenname>
				<surname>Kusnitz</surname>
			</person>
			<person>
				<givenname>Scott</givenname>
				<surname>McGlashan</surname>
			</person>
			<person>
				<givenname>Alex</givenname>
				<surname>Lee</surname>
			</person>
			<person>
				<givenname>Brad</givenname>
				<surname>Porter</surname>
			</person>
			<person>
				<givenname>Kenneth G.</givenname>
				<surname>Rehor</surname>
			</person>
		</names>
		<date value="2007-06"/>
		<abstract>
			<richtext>
				<p>VoiceXML 2.1 specifies a set of features commonly implemented by Voice Extensible Markup Language platforms. This specification is designed to be fully backwards-compatible with VoiceXML 2.0. This specification describes only the set of additional features.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Recommendation REC-voicexml21-20070619</howpublished>
		<title type="sharef:primaryTitle">Voice Extensible Markup Language (VoiceXML) 2.1</title>
		<field type="bibtex:topic">voicexml[1]</field>
		<field type="bibtex:updates">voicexml20</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2007/REC-voicexml21-20070619</identifier>
	</reference>
	<reference name="vxml30reqs" src="bibtex:misc" src-info="bibtex:line-31885" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Jeff</givenname>
				<surname>Hoepfinger</surname>
			</person>
			<person>
				<givenname>Emily</givenname>
				<surname>Candell</surname>
			</person>
		</names>
		<date value="2008-08"/>
		<abstract>
			<richtext>
				<p>The W3C Voice Browser working group aims to develop specifications to enable access to the Web using spoken interaction. This document is part of a set of requirement studies for voice browsers, and provides details of the requirements for marking up spoken dialogs.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-vxml30reqs-20080808</howpublished>
		<title type="sharef:primaryTitle">Voice Extensible Markup Language (VoiceXML) 3.0 Requirements</title>
		<field type="bibtex:topic">voicexml[0.9]</field>
		<field type="bibtex:updates">voicexml21</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2008/WD-vxml30reqs-20080808</identifier>
	</reference>
	<reference name="voicexml30" src="bibtex:misc" src-info="bibtex:line-31897" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Scott</givenname>
				<surname>McGlashan</surname>
			</person>
			<person>
				<givenname>Daniel C.</givenname>
				<surname>Burnett</surname>
			</person>
			<person>
				<givenname>Rahul</givenname>
				<surname>Akolkar</surname>
			</person>
			<person>
				<givenname>R. J.</givenname>
				<surname>Auburn</surname>
			</person>
			<person>
				<givenname>Paolo</givenname>
				<surname>Baggia</surname>
			</person>
			<person>
				<givenname>Jim</givenname>
				<surname>Barnett</surname>
			</person>
			<person>
				<givenname>Michael</givenname>
				<surname>Bodell</surname>
			</person>
			<person>
				<givenname>Jerry</givenname>
				<surname>Carter</surname>
			</person>
			<person>
				<givenname>Mangesh</givenname>
				<surname>Deshmukh</surname>
			</person>
			<person>
				<givenname>Matt</givenname>
				<surname>Oshry</surname>
			</person>
			<person>
				<givenname>Kenneth G.</givenname>
				<surname>Rehor</surname>
			</person>
			<person>
				<givenname>Xu</givenname>
				<surname>Yang</surname>
			</person>
			<person>
				<givenname>Milan</givenname>
				<surname>Young</surname>
			</person>
		</names>
		<date value="2010-12"/>
		<abstract>
			<richtext>
				<p>This document specifies VoiceXML 3.0, a modular XML language for creating interactive media dialogs that feature synthesized speech, recognition of spoken and DTMF key input, telephony, mixed initiative conversations, and recording and presentation of a variety of media formats including digitized audio, and digitized video. Its major goal is to bring the advantages of Web-based development and content delivery to interactive voice response applications.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-voicexml30-20101216</howpublished>
		<title type="sharef:primaryTitle">Voice Extensible Markup Language (VoiceXML) 3.0</title>
		<field type="bibtex:topic">voicexml[1]</field>
		<field type="bibtex:updates">voicexml21 vxml30reqs</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2010/WD-voicexml30-20101216</identifier>
	</reference>
	<reference name="semspeechreg" src="bibtex:misc" src-info="bibtex:line-31909" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Luc Van</givenname>
				<surname>Tichelen</surname>
			</person>
			<person>
				<givenname>David</givenname>
				<surname>Burke</surname>
			</person>
		</names>
		<date value="2007-04"/>
		<abstract>
			<richtext>
				<p>This document defines the process of Semantic Interpretation for Speech Recognition and the syntax and semantics of semantic interpretation tags that can be added to speech recognition grammars to compute information to return to an application on the basis of rules and tokens that were matched by the speech recognizer. In particular, it defines the syntax and semantics of the contents of Tags in the Speech Recognition Grammar Specification (SRGS). The results of semantic interpretation describe the meaning of a natural language utterance. The current specification represents this information as an ECMAScript object, and defines a mechanism to serialize the result into XML. The W3C Multimodal Interaction Activity (MMI) is defining an XML data format (EMMA) for containing and annotating the information in user utterances. It is expected that the EMMA language will be able to integrate results generated by Semantic Interpretation for Speech Recognition. Semantic Interpretation may be useful in combination with other specifications, such as Stochastic Language Models, but their use with N-grams has not yet been studied.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Recommendation REC-semantic-interpretation-20070405</howpublished>
		<title type="sharef:primaryTitle">Semantic Interpretation for Speech Recognition (SISR) Version 1.0</title>
		<field type="bibtex:topic">sisr[1] srgs[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2007/REC-semantic-interpretation-20070405</identifier>
	</reference>
	<reference name="speechml" src="bibtex:misc" src-info="bibtex:line-31920" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Daniel C.</givenname>
				<surname>Burnett</surname>
			</person>
			<person>
				<givenname>Mark R.</givenname>
				<surname>Walker</surname>
			</person>
			<person>
				<givenname>Andrew</givenname>
				<surname>Hunt</surname>
			</person>
		</names>
		<date value="2004-09"/>
		<abstract>
			<richtext>
				<p>The Voice Browser Working Group has sought to develop standards to enable access to the Web using spoken interaction. The Speech Synthesis Markup Language Specification is one of these standards and is designed to provide a rich, XML-based markup language for assisting the generation of synthetic speech in Web and other applications. The essential role of the markup language is to provide authors of synthesizable content a standard way to control aspects of speech such as pronunciation, volume, pitch, rate, etc. across different synthesis-capable platforms.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Recommendation REC-speech-synthesis-20040907</howpublished>
		<title type="sharef:primaryTitle">Speech Synthesis Markup Language Version 1.0</title>
		<field type="bibtex:topic">ssml[1]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2004/REC-speech-synthesis-20040907</identifier>
	</reference>
	<reference name="ssml11reqs" src="bibtex:misc" src-info="bibtex:line-31931" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Scott</givenname>
				<surname>McGlashan</surname>
			</person>
			<person>
				<givenname>Andrew</givenname>
				<surname>Wahbe</surname>
			</person>
			<person>
				<givenname>Hairong</givenname>
				<surname>Xia</surname>
			</person>
			<person>
				<givenname>Yan</givenname>
				<surname>Jun</surname>
			</person>
			<person>
				<givenname>Zhiyong</givenname>
				<surname>Wu</surname>
			</person>
		</names>
		<names type="sharef:editor">
			<person>
				<givenname>Daniel C.</givenname>
				<surname>Burnett</surname>
			</person>
			<person>
				<givenname>Zhi Wei</givenname>
				<surname>Shuang</surname>
			</person>
		</names>
		<date value="2007-06"/>
		<abstract>
			<richtext>
				<p>In 2005, 2006, and 2007 the W3C held workshops to understand the ways, if any, in which the design of SSML 1.0 limited its usefulness for authors of applications in Asian, Eastern European, and Middle Eastern languages. In 2006 an SSML subgroup of the W3C Voice Browser Working Group was formed to review this input and develop requirements for changes necessary to support those languages. This document contains those requirements.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-ssml11reqs-20070611</howpublished>
		<title type="sharef:primaryTitle">Speech Synthesis Markup Language Version 1.1 Requirements</title>
		<field type="bibtex:topic">ssml[0.9]</field>
		<field type="bibtex:updates">speechml</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2007/WD-ssml11reqs-20070611</identifier>
	</reference>
	<reference name="ssml11" src="bibtex:misc" src-info="bibtex:line-31944" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Paolo</givenname>
				<surname>Baggia</surname>
			</person>
			<person>
				<givenname>Paul</givenname>
				<surname>Bagshaw</surname>
			</person>
			<person>
				<givenname>Michael</givenname>
				<surname>Bodell</surname>
			</person>
			<person>
				<givenname>De Zhi</givenname>
				<surname>Huang</surname>
			</person>
			<person>
				<givenname>Lou</givenname>
				<surname>Xiaoyan</surname>
			</person>
			<person>
				<givenname>Scott</givenname>
				<surname>McGlashan</surname>
			</person>
			<person>
				<givenname>JianHua</givenname>
				<surname>Tao</surname>
			</person>
			<person>
				<givenname>Yan</givenname>
				<surname>Jun</surname>
			</person>
			<person>
				<givenname>Hu</givenname>
				<surname>Fang</surname>
			</person>
			<person>
				<givenname>Yongguo</givenname>
				<surname>Kang</surname>
			</person>
			<person>
				<givenname>Helen</givenname>
				<surname>Meng</surname>
			</person>
			<person>
				<givenname>Wang</givenname>
				<surname>Xia</surname>
			</person>
			<person>
				<givenname>Xia</givenname>
				<surname>Hairong</surname>
			</person>
			<person>
				<givenname>Zhiyong</givenname>
				<surname>Wu</surname>
			</person>
		</names>
		<names type="sharef:editor">
			<person>
				<givenname>Daniel C.</givenname>
				<surname>Burnett</surname>
			</person>
			<person>
				<givenname>Zhi Wei</givenname>
				<surname>Shuang</surname>
			</person>
		</names>
		<date value="2010-09"/>
		<abstract>
			<richtext>
				<p>The Voice Browser Working Group has sought to develop standards to enable access to the Web using spoken interaction. The Speech Synthesis Markup Language Specification is one of these standards and is designed to provide a rich, XML-based markup language for assisting the generation of synthetic speech in Web and other applications. The essential role of the markup language is to provide authors of synthesizable content a standard way to control aspects of speech such as pronunciation, volume, pitch, rate, etc. across different synthesis-capable platforms.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Recommendation REC-speech-synthesis11-20100907</howpublished>
		<title type="sharef:primaryTitle">Speech Synthesis Markup Language (SSML) Version 1.1</title>
		<field type="bibtex:topic">ssml[1]</field>
		<field type="bibtex:updates">ssml11reqs</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2010/REC-speech-synthesis11-20100907</identifier>
	</reference>
	<reference name="ssmlsayas" src="bibtex:misc" src-info="bibtex:line-31957" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Daniel C.</givenname>
				<surname>Burnett</surname>
			</person>
			<person>
				<givenname>Paolo</givenname>
				<surname>Baggia</surname>
			</person>
			<person>
				<givenname>James</givenname>
				<surname>Barnett</surname>
			</person>
			<person>
				<givenname>An</givenname>
				<surname>Buyle</surname>
			</person>
			<person>
				<givenname>Ellen</givenname>
				<surname>Eide</surname>
			</person>
			<person>
				<givenname>Luc</givenname>
				<surname>Van Tichelen</surname>
			</person>
		</names>
		<date value="2005-05"/>
		<abstract>
			<richtext>
				<p>The say-as element in SSML 1.0 is considered one of the most useful elements of the language. However, SSML 1.0 does not define the values of the attributes of this element. This Note provides definitions for these attributes that cover many of the most common use cases for the say-as element.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Note NOTE-ssml-sayas-20050526</howpublished>
		<title type="sharef:primaryTitle">SSML 1.0 say-as Attribute Values</title>
		<field type="bibtex:topic">ssml[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2005/NOTE-ssml-sayas-20050526</identifier>
	</reference>
	<reference name="speechgrammar" src="bibtex:misc" src-info="bibtex:line-31968" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Andrew</givenname>
				<surname>Hunt</surname>
			</person>
			<person>
				<givenname>Scott</givenname>
				<surname>McGlashan</surname>
			</person>
		</names>
		<date value="2004-03"/>
		<abstract>
			<richtext>
				<p>This document defines syntax for representing grammars for use in speech recognition so that developers can specify the words and patterns of words to be listened for by a speech recognizer. The syntax of the grammar format is presented in two forms, an Augmented BNF Form and an XML Form. The specification makes the two representations mappable to allow automatic transformations between the two forms.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Recommendation REC-speech-grammar-20040316</howpublished>
		<title type="sharef:primaryTitle">Speech Recognition Grammar Specification Version 1.0</title>
		<field type="bibtex:topic">srgs[1]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2004/REC-speech-grammar-20040316</identifier>
	</reference>
	<reference name="lexiconreqs" src="bibtex:misc" src-info="bibtex:line-31979" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Paolo</givenname>
				<surname>Baggia</surname>
			</person>
			<person>
				<givenname>Frank</givenname>
				<surname>Scahill</surname>
			</person>
		</names>
		<date value="2004-10"/>
		<abstract>
			<richtext>
				<p>The W3C Voice Browser Working Group aims to develop specifications to enable access to the Web using spoken interaction. This document is part of a set of requirements studies for voice browsers, and provides details of the requirements for markup used for specifying application specific pronunciation lexicons. Application specific pronunciation lexicons are required in many situations where the default lexicon supplied with a speech recognition or speech synthesis processor does not cover the vocabulary of the application. A pronunciation lexicon is a collection of words or phrases together with their pronunciations specified using an appropriate pronunciation alphabet.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-lexicon-reqs-20041029</howpublished>
		<title type="sharef:primaryTitle">Pronunciation Lexicon Specification (PLS) Version 1.0 Requirements</title>
		<field type="bibtex:topic">pls[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2004/WD-lexicon-reqs-20041029</identifier>
	</reference>
	<reference name="pronunciationlexicon" src="bibtex:misc" src-info="bibtex:line-31990" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Paul</givenname>
				<surname>Bagshaw</surname>
			</person>
			<person>
				<givenname>Daniel C.</givenname>
				<surname>Burnett</surname>
			</person>
			<person>
				<givenname>Jerry</givenname>
				<surname>Carter</surname>
			</person>
			<person>
				<givenname>Frank</givenname>
				<surname>Scahill</surname>
			</person>
		</names>
		<names type="sharef:editor">
			<person>
				<givenname>Paolo</givenname>
				<surname>Baggia</surname>
			</person>
		</names>
		<date value="2008-10"/>
		<abstract>
			<richtext>
				<p>This document defines the syntax for specifying pronunciation lexicons to be used by Automatic Speech Recognition and Speech Synthesis engines in voice browser applications.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Recommendation REC-pronunciation-lexicon-20081014</howpublished>
		<title type="sharef:primaryTitle">Pronunciation Lexicon Specification (PLS) Version 1.0</title>
		<field type="bibtex:topic">pls[1]</field>
		<field type="bibtex:updates">lexiconreqs</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2008/REC-pronunciation-lexicon-20081014</identifier>
	</reference>
	<reference name="hdml" src="bibtex:misc" src-info="bibtex:line-32003" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Peter R.</givenname>
				<surname>King</surname>
			</person>
			<person>
				<givenname>Tim</givenname>
				<surname>Hyland</surname>
			</person>
		</names>
		<date value="1997-05"/>
		<howpublished>World Wide Web Consortium, Note NOTE-Submission-HDML-spec</howpublished>
		<title type="sharef:primaryTitle">Handheld Device Markup Language Specification</title>
		<field type="bibtex:topic">hdml[1]</field>
		<identifier type="sharef:uri" resourceType="text/html">http://www.w3.org/pub/WWW/TR/NOTE-Submission-HDML-spec.html</identifier>
	</reference>
	<reference name="xmsg" src="bibtex:misc" src-info="bibtex:line-32013" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>R. Alexander</givenname>
				<surname>Milowski</surname>
			</person>
		</names>
		<date value="2000-10"/>
		<abstract>
			<richtext>
				<p>XMSG is a specification for using XML to send messages that contain a set of XML documents, embedded non-XML data, and references to non-XML documents in a fashion that supports scalable transactions and operates on a participant model.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Note NOTE-xmsg-20001013</howpublished>
		<title type="sharef:primaryTitle">XMSG — XML Messaging Specification</title>
		<field type="bibtex:topic">xmsg[1]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2000/NOTE-xmsg-20001013</identifier>
	</reference>
	<reference name="uclp" src="bibtex:misc" src-info="bibtex:line-32024" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Kenneth</givenname>
				<surname>Laskey</surname>
			</person>
		</names>
		<date value="1999-01"/>
		<howpublished>World Wide Web Consortium, Note NOTE-uclp-19990120</howpublished>
		<title type="sharef:primaryTitle">Universal Commerce Language and Protocol (UCLP) Version 3.0</title>
		<field type="bibtex:topic">uclp[1]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/1999/NOTE-uclp-19990120</identifier>
	</reference>
	<reference name="w3cpatentpolicy" src="bibtex:misc" src-info="bibtex:line-32034" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Daniel J.</givenname>
				<surname>Weitzner</surname>
			</person>
		</names>
		<date value="2003-03"/>
		<howpublished>World Wide Web Consortium, Working Draft WD-patent-policy-20030319</howpublished>
		<title type="sharef:primaryTitle">Patent Policy Working Group Royalty-Free Patent Policy</title>
		<identifier type="sharef:uri">http://www.w3.org/TR/2003/WD-patent-policy-20030319</identifier>
	</reference>
	<reference name="ccppst" src="bibtex:misc" src-info="bibtex:line-32043" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Franklin</givenname>
				<surname>Reynolds</surname>
			</person>
			<person>
				<givenname>Chris</givenname>
				<surname>Woodrow</surname>
			</person>
			<person>
				<givenname>Hidetaka</givenname>
				<surname>Ohto</surname>
			</person>
		</names>
		<date value="2000-07"/>
		<howpublished>World Wide Web Consortium, Working Draft WD-CCPP-struct-20000721</howpublished>
		<title type="sharef:primaryTitle">Composite Capability/Preference Profiles (CC/PP): Structure</title>
		<field type="bibtex:topic">ccpp[1]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2000/WD-CCPP-struct-20000721</identifier>
	</reference>
	<reference name="ccppav" src="bibtex:misc" src-info="bibtex:line-32053" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Graham</givenname>
				<surname>Klyne</surname>
			</person>
		</names>
		<date value="2000-07"/>
		<howpublished>World Wide Web Consortium, Working Draft WD-CCPP-vocab-20000721</howpublished>
		<title type="sharef:primaryTitle">CC/PP Attribute Vocabularies</title>
		<field type="bibtex:topic">ccpp[1]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2000/WD-CCPP-struct-20000721</identifier>
	</reference>
	<reference name="ccppsv" src="bibtex:misc" src-info="bibtex:line-32063" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Graham</givenname>
				<surname>Klyne</surname>
			</person>
			<person>
				<givenname>Franklin</givenname>
				<surname>Reynolds</surname>
			</person>
			<person>
				<givenname>Chris</givenname>
				<surname>Woodrow</surname>
			</person>
			<person>
				<givenname>Hidetaka</givenname>
				<surname>Ohto</surname>
			</person>
			<person>
				<givenname>Johan</givenname>
				<surname>Hjelm</surname>
			</person>
			<person>
				<givenname>Mark H.</givenname>
				<surname>Butler</surname>
			</person>
			<person>
				<givenname>Luu</givenname>
				<surname>Tran</surname>
			</person>
		</names>
		<date value="2004-01"/>
		<howpublished>World Wide Web Consortium, Recommendation REC-CCPP-struct-vocab-20040115</howpublished>
		<title type="sharef:primaryTitle">Composite Capability/Preference Profiles (CC/PP): Structure and Vocabularies</title>
		<field type="bibtex:topic">ccpp[1]</field>
		<field type="bibtex:updates">ccppst ccppav</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2004/REC-CCPP-struct-vocab-20040115</identifier>
	</reference>
	<reference name="ccppsv20" src="bibtex:misc" src-info="bibtex:line-32074" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Cédric</givenname>
				<surname>Kiss</surname>
			</person>
		</names>
		<date value="2007-05"/>
		<abstract>
			<richtext>
				<p>This document describes CC/PP (Composite Capabilities/Preference Profiles) Structure and Vocabularies 2.0. A CC/PP profile is a description of device capabilities and user preferences. This is often referred to as a device's delivery context and can be used to guide the adaptation of content presented to that device. The Resource Description Framework (RDF) is used to create profiles that describe user agent capabilities and preferences. The structure of a profile is discussed. Topics include structure of client capability and preference descriptions, use of RDF classes to distinguish different elements of a profile, so that a schema-aware RDF processor can handle CC/PP profiles embedded in other XML document types. Version 2.0 of CC/PP ensures its alignment with the latest version of RDF. CC/PP vocabulary is identifiers (URIs) used to refer to specific capabilities and preferences, and covers the types of values to which CC/PP attributes may refer, an appendix describing how to introduce new vocabularies, an appendix giving an example small client vocabulary covering print and display capabilities, and an appendix providing a survey of existing work from which new vocabularies may be derived.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-CCPP-struct-vocab2-20070430</howpublished>
		<title type="sharef:primaryTitle">Composite Capability/Preference Profiles (CC/PP): Structure and Vocabularies 2.0</title>
		<field type="bibtex:topic">ccpp[1]</field>
		<field type="bibtex:updates">ccppsv</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2007/WD-CCPP-struct-vocab2-20070430</identifier>
	</reference>
	<reference name="ccppta" src="bibtex:misc" src-info="bibtex:line-32086" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Mikael</givenname>
				<surname>Nilsson</surname>
			</person>
		</names>
		<date value="2000-07"/>
		<howpublished>World Wide Web Consortium, Working Draft WD-CCPP-ta-20000721</howpublished>
		<title type="sharef:primaryTitle">Composite Capability/Preference Profiles: Terminology and Abbreviations</title>
		<field type="bibtex:topic">ccpp[1]</field>
	</reference>
	<reference name="ccppra" src="bibtex:misc" src-info="bibtex:line-32095" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Mikael</givenname>
				<surname>Nilsson</surname>
			</person>
			<person>
				<givenname>Johan</givenname>
				<surname>Hjelm</surname>
			</person>
			<person>
				<givenname>Hidetaka</givenname>
				<surname>Ohto</surname>
			</person>
		</names>
		<date value="2000-07"/>
		<howpublished>World Wide Web Consortium, Working Draft WD-CCPP-ra-20000721</howpublished>
		<title type="sharef:primaryTitle">Composite Capability/Preference Profiles: Requirements and Architecture</title>
		<field type="bibtex:topic">ccpp[1]</field>
	</reference>
	<reference name="ccppep" src="bibtex:misc" src-info="bibtex:line-32104" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Hidetaka</givenname>
				<surname>Ohto</surname>
			</person>
			<person>
				<givenname>Johan</givenname>
				<surname>Hjelm</surname>
			</person>
		</names>
		<date value="1999-06"/>
		<howpublished>World Wide Web Consortium, Note NOTE-CCPPexchange-19990624</howpublished>
		<title type="sharef:primaryTitle">CC/PP exchange protocol based on HTTP Extension Framework</title>
		<field type="bibtex:topic">ccpp[1]</field>
	</reference>
	<reference name="ccppcoord" src="bibtex:misc" src-info="bibtex:line-32113" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Johan</givenname>
				<surname>Hjelm</surname>
			</person>
			<person>
				<givenname>Lalitha</givenname>
				<surname>Suryanarayana</surname>
			</person>
		</names>
		<date value="2001-12"/>
		<abstract>
			<richtext>
				<p>This document describes how existing vocabularies for different classes of devices and user agents can be used in CC/PP components, and how to create schemas that encapsulate existing vocabularies. It discusses the results of the coordination with the IETF CONNEG Working Group, as well as the WAP Forum UAPROF Working Group and several other groups, which have related activities. It contains a number of schemas and software examples which has been contributed voluntarily by individuals. It also gives an example of heuristics, which can be used to adapt content to a CC/PP profile, thus giving some guidelines for those who want to use CC/PP to implement content adaptation. It also serves to provide vocabulary and schema designers with key guidelines regarding extensions to existing vocabularies or development of new ones.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Note NOTE-CCPP-COORDINATION-20011220</howpublished>
		<title type="sharef:primaryTitle">CC/PP Implementors Guide: Harmonization with Existing Vocabularies and Content Transformation Heuristics</title>
		<field type="bibtex:topic">ccpp[0.9] fipa[0.9] wap1[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2001/NOTE-CCPP-COORDINATION-20011220</identifier>
	</reference>
	<reference name="ccpptrust" src="bibtex:misc" src-info="bibtex:line-32124" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Hidetaka</givenname>
				<surname>Ohto</surname>
			</person>
			<person>
				<givenname>Lalitha</givenname>
				<surname>Suryanarayana</surname>
			</person>
			<person>
				<givenname>Johan</givenname>
				<surname>Hjelm</surname>
			</person>
		</names>
		<date value="2001-12"/>
		<abstract>
			<richtext>
				<p>This document gives implementors advice on how to protect the privacy of a CC/PP user, and outlines how this can be applied using P3P in HTTP with the CC/PP Exchange protocol.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-CCPP-trust-20011220</howpublished>
		<title type="sharef:primaryTitle">CC/PP Implementors Guide: Privacy and Protocols</title>
		<field type="bibtex:topic">ccpp[1]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2001/WD-CCPP-trust-20011220</identifier>
	</reference>
	<reference name="ccpp" src="bibtex:misc" src-info="bibtex:line-32135" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Franklin</givenname>
				<surname>Reynolds</surname>
			</person>
			<person>
				<givenname>Johan</givenname>
				<surname>Hjelm</surname>
			</person>
			<person>
				<givenname>Spencer</givenname>
				<surname>Dawkins</surname>
			</person>
			<person>
				<givenname>Sandeep</givenname>
				<surname>Singhal</surname>
			</person>
		</names>
		<date value="1999-07"/>
		<abstract>
			<richtext>
				<p>In this note we describe a method for using RDF, the Resource Description Format of the W3C, to create a general, yet extensible framework for describing user preferences and device capabilities. This information can be provided by the user to servers and content providers. The servers can use this information describing the user's preferences to customize the service or content provided. The ability of RDF to reference profile information via URLs assists in minimizing the number of network transactions required to adapt content to a device, while the framework fits well into the current and future protocols being developed a the W3C and the WAP Forum.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Note NOTE-CCPP-19990727</howpublished>
		<field type="bibtex:index">CC/PP, metadata, RDF, content negotiation</field>
		<title type="sharef:primaryTitle">Composite Capability/Preference Profiles (CC/PP): A user side framework for content negotiation</title>
		<identifier type="sharef:uri">http://www.w3.org/1999/07/NOTE-CCPP-19990727</identifier>
	</reference>
	<reference name="ddecosystem" src="bibtex:misc" src-info="bibtex:line-32146" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Rotan</givenname>
				<surname>Hanrahan</surname>
			</person>
		</names>
		<date value="2007-10"/>
		<abstract>
			<richtext>
				<p>This W3C Note describes the business models surrounding the creation, maintenance and use of device descriptions. It identifies the main actors in the current model, explores their motivations for participating, identifies the costs associated with participation and the benefits that accrue to participants. It is shown in this Note that the current model is incomplete, partly because of the absence of a common repository that can address the needs of the various actors. A complete model is postulated, on the assumption of the existence of a common repository, from which is derived some key requirements upon such a repository to ensure the success of the model. This Note should be read in conjunction with the DDWG Landscape document, which provides details of the particular technologies and actors currently engaged in work related to device descriptions. This Note, together with the Landscape document, provides input to the DDWG Requirements document.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Note NOTE-dd-ecosystem-20071031</howpublished>
		<title type="sharef:primaryTitle">Device Description Ecosystem</title>
		<identifier type="sharef:uri">http://www.w3.org/TR/2007/NOTE-dd-ecosystem-20071031</identifier>
	</reference>
	<reference name="ddlandscape" src="bibtex:misc" src-info="bibtex:line-32156" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Eman</givenname>
				<surname>Nkeze</surname>
			</person>
			<person>
				<givenname>James</givenname>
				<surname>Pearce</surname>
			</person>
			<person>
				<givenname>Matt</givenname>
				<surname>Womer</surname>
			</person>
		</names>
		<date value="2007-10"/>
		<abstract>
			<richtext>
				<p>Developing Web content for mobile devices is more challenging than developing for the desktop Web. Compared to desktop Web clients, mobile Web devices come in a much wider range of shapes, sizes and capabilities. The mobile Web developer relies upon accurate device descriptions in order to dynamically adapt content to suit the client. This Note describes what efforts the W3C and other organizations are doing in order to provide accurate device descriptions. This Note should be read in conjunction with the DDWG Ecosystem document. This Note, together with the Ecosystem document, provides input to the proposed DDWG Requirements document as described in the DDWG Charter.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Note NOTE-dd-landscape-20071031</howpublished>
		<title type="sharef:primaryTitle">Device Description Landscape</title>
		<identifier type="sharef:uri">http://www.w3.org/TR/2007/NOTE-dd-landscape-20071031</identifier>
	</reference>
	<reference name="ddrrequirements" src="bibtex:misc" src-info="bibtex:line-32166" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Kevin</givenname>
				<surname>Smith</surname>
			</person>
			<person>
				<givenname>David</givenname>
				<surname>Sanders</surname>
			</person>
		</names>
		<date value="2007-12"/>
		<abstract>
			<richtext>
				<p>This W3C Working Draft specifies the requirements for a logical reference repository for device descriptions. This document does not specify a definitive list of device descriptions rather it specifies requirements not only on the reference device descriptions repository itself but also on the provision and management of device descriptions, and the discovery and access to the repository and its device descriptions. This document forms one of three W3C notes within the scope of the W3C Mobile Web Initiative, Device Description Working Group (DDWG). The requirements in this document are not only derived from the described use-cases but also build on the information described in the DDWG Landscape and Ecosystem documents.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Note NOTE-DDR-requirements-20071217</howpublished>
		<title type="sharef:primaryTitle">Device Description Repository Requirements 1.0</title>
		<identifier type="sharef:uri">http://www.w3.org/TR/2007/NOTE-DDR-requirements-20071217</identifier>
	</reference>
	<reference name="ddrcorevocabulary" src="bibtex:misc" src-info="bibtex:line-32176" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Jo</givenname>
				<surname>Rabin</surname>
			</person>
			<person>
				<givenname>Andrea</givenname>
				<surname>Trasatti</surname>
			</person>
			<person>
				<givenname>Rotan</givenname>
				<surname>Hanrahan</surname>
			</person>
		</names>
		<date value="2008-04"/>
		<abstract>
			<richtext>
				<p>This document describes the Device Description Repository Core Vocabulary for Content Adaptation in the Mobile Web, described in the charter of the Device Descriptions Working Group, as well as the process by which the Vocabulary was defined.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Note NOTE-ddr-core-vocabulary-20080414</howpublished>
		<title type="sharef:primaryTitle">Device Description Repository Core Vocabulary</title>
		<identifier type="sharef:uri">http://www.w3.org/TR/2008/NOTE-ddr-core-vocabulary-20080414</identifier>
	</reference>
	<reference name="ddrsimpleapi" src="bibtex:misc" src-info="bibtex:line-32186" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Jo</givenname>
				<surname>Rabin</surname>
			</person>
			<person>
				<givenname>José Manuel Cantera</givenname>
				<surname>Fonseca</surname>
			</person>
			<person>
				<givenname>Rotan</givenname>
				<surname>Hanrahan</surname>
			</person>
			<person>
				<givenname>Ignacio</givenname>
				<surname>Marín</surname>
			</person>
		</names>
		<date value="2008-12"/>
		<abstract>
			<richtext>
				<p>Web content delivered to mobile devices usually benefits from being tailored to take into account a range of factors such as screen size, markup language support and image format support. Such information is stored in "Device Description Repositories" (DDRs). This document describes a simple API for access to DDRs, in order to ease and promote the development of Web content that adapts to its Delivery Context.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Recommendation REC-DDR-Simple-API-20081205</howpublished>
		<title type="sharef:primaryTitle">Device Description Repository Simple API</title>
		<identifier type="sharef:uri">http://www.w3.org/TR/2008/REC-DDR-Simple-API-20081205</identifier>
	</reference>
	<reference name="ddstructures" src="bibtex:misc" src-info="bibtex:line-32196" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>José Manuel Cantera</givenname>
				<surname>Fonseca</surname>
			</person>
		</names>
		<date value="2008-12"/>
		<abstract>
			<richtext>
				<p>Content Adaptation on the Mobile Web can be simplified by creating groups for those devices that share common characteristics. This WG Note defines an XML format, a group definition syntax and an extension to the DDR Simple API that can be used in the development of adaptive Mobile Web sites that exploit grouping.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-dd-structures-20081205</howpublished>
		<title type="sharef:primaryTitle">Device Description Structures</title>
		<identifier type="sharef:uri">http://www.w3.org/TR/2008/WD-dd-structures-20081205</identifier>
	</reference>
	<reference name="xprocrequirements" src="bibtex:misc" src-info="bibtex:line-32206" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>R. Alexander</givenname>
				<surname>Milowski</surname>
			</person>
		</names>
		<date value="2006-04"/>
		<abstract>
			<richtext>
				<p>This document contains requirements for the development of an XML Processing Model and Language, which are intended to describe and specify the processing relationships between XML resources.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-xproc-requirements-20060411</howpublished>
		<title type="sharef:primaryTitle">XML Processing Model Requirements and Use Cases</title>
		<field type="bibtex:topic">xml[0.8] xproc[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2006/WD-xproc-requirements-20060411</identifier>
	</reference>
	<reference name="xproc" src="bibtex:misc" src-info="bibtex:line-32217" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Norman</givenname>
				<surname>Walsh</surname>
			</person>
			<person>
				<givenname>R. Alexander</givenname>
				<surname>Milowski</surname>
			</person>
			<person>
				<givenname>Henry S.</givenname>
				<surname>Thompson</surname>
			</person>
		</names>
		<date value="2010-05"/>
		<abstract>
			<richtext>
				<p>This specification describes the syntax and semantics of XProc: An XML Pipeline Language, a language for describing operations to be performed on XML documents. An XML Pipeline specifies a sequence of operations to be performed on zero or more XML documents. Pipelines generally accept zero or more XML documents as input and produce zero or more XML documents as output. Pipelines are made up of simple steps which perform atomic operations on XML documents and constructs similar to conditionals, iteration, and exception handlers which control which steps are executed.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Recommendation REC-xproc-20100511</howpublished>
		<title type="sharef:primaryTitle">XProc: An XML Pipeline Language</title>
		<field type="bibtex:topic">xml[0.8] xproc[1]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2010/REC-xproc-20100511</identifier>
	</reference>
	<reference name="xproctemplate" src="bibtex:misc" src-info="bibtex:line-32228" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Norman</givenname>
				<surname>Walsh</surname>
			</person>
		</names>
		<date value="2011-01"/>
		<abstract>
			<richtext>
				<p>This note describes two new XProc steps designed to make it easier to construct documents within an XProc pipeline using values computed by that pipeline.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Note NOTE-xproc-template-20110125</howpublished>
		<title type="sharef:primaryTitle">Document Templating Steps for XProc</title>
		<field type="bibtex:topic">xml[0.8] xproc[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2011/NOTE-xproc-template-20110125</identifier>
	</reference>
	<reference name="htmlroad" src="bibtex:misc" src-info="bibtex:line-32239" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Steven</givenname>
				<surname>Pemberton</surname>
			</person>
			<person>
				<givenname>Dave</givenname>
				<surname>Raggett</surname>
			</person>
		</names>
		<date value="2000-07"/>
		<abstract>
			<richtext>
				<p>This note describes the time line for deliverables of the HTML working group. It will be updated from time to time.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Note NOTE-xhtml-roadmap-20000721</howpublished>
		<title type="sharef:primaryTitle">HTML Working Group Roadmap</title>
		<field type="bibtex:topic">html[0.9] xhtml[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2000/NOTE-xhtml-roadmap-20000721</identifier>
	</reference>
	<reference name="accesscontrol" src="bibtex:misc" src-info="bibtex:line-32250" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Anne</givenname>
				<surname link="van">Kesteren</surname>
			</person>
		</names>
		<date value="2010-07"/>
		<abstract>
			<richtext>
				<p>This document defines a mechanism to enable client-side cross-site requests. Specifications that want to enable cross-site requests in an API they define can use the algorithms defined by this specification. If such an API is used on http://example.org resources, a resource on http://hello-world.example can opt in using the mechanism described by this specification (e.g., specifying Access-Control-Allow-Origin: http://example.org as response header), which would allow that resource to be fetched cross-site from http://example.org.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-cors-20100727</howpublished>
		<title type="sharef:primaryTitle">Cross-Origin Resource Sharing</title>
		<field type="bibtex:topic">api[0.7] http[0.7] javascript[0.7] cors[1]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2010/WD-cors-20100727</identifier>
	</reference>
	<reference name="ump" src="bibtex:misc" src-info="bibtex:line-32261" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Tyler</givenname>
				<surname>Close</surname>
			</person>
			<person>
				<givenname>Mark</givenname>
				<surname>Miller</surname>
			</person>
		</names>
		<date value="2010-01"/>
		<abstract>
			<richtext>
				<p>The Uniform Messaging Policy (UMP) enables cross-site messaging that avoids Cross-Site-Request-Forgery and similar attacks that abuse HTTP cookies and other credentials. For example, content from customer.example.org can safely specify requests to resources determined by service.example.com. Rather than restricting information retrieval to a single origin, as the Same Origin Policy almost does, the Uniform Messaging Policy supports origin independent messaging.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-UMP-20100126</howpublished>
		<title type="sharef:primaryTitle">Uniform Messaging Policy, Level One</title>
		<field type="bibtex:topic">api[0.7] http[0.7] javascript[0.7] ump[1]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2010/WD-UMP-20100126</identifier>
	</reference>
	<reference name="xformsreq" src="bibtex:misc" src-info="bibtex:line-32272" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Micah</givenname>
				<surname>Dubinko</surname>
			</person>
			<person>
				<givenname>Sebastian</givenname>
				<surname>Schnitzenbaumer</surname>
			</person>
			<person>
				<givenname>Malte</givenname>
				<surname>Wedel</surname>
			</person>
			<person>
				<givenname>Dave</givenname>
				<surname>Raggett</surname>
			</person>
		</names>
		<date value="2000-08"/>
		<abstract>
			<richtext>
				<p>Forms were introduced into HTML in 1993. Since then they have gone on to become a critical part of the Web. The existing mechanisms in HTML for forms are now outdated, and W3C has started work on developing an effective replacement. This document outlines the requirements for "XForms", W3C's name for the next generation of Web forms.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-xhtml-forms-req-20000821</howpublished>
		<title type="sharef:primaryTitle">XForms Requirements</title>
		<field type="bibtex:topic">xforms[0.8]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2000/WD-xhtml-forms-req-20000821</identifier>
	</reference>
	<reference name="xforms10data" src="bibtex:misc" src-info="bibtex:line-32283" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Micah</givenname>
				<surname>Dubinko</surname>
			</person>
			<person>
				<givenname>Sebastian</givenname>
				<surname>Schnitzenbaumer</surname>
			</person>
			<person>
				<givenname>Dave</givenname>
				<surname>Raggett</surname>
			</person>
		</names>
		<date value="2000-08"/>
		<abstract>
			<richtext>
				<p>"XForms" is the name for W3C's work on the next generation of Web forms. This work was started in a subgroup of the HTML Working Group and recently spun off into an independent Working Group, with a broadened focus. The Working Group is currently studying how to support forms where the data model is defined by an XML Schema plus form specific properties. The previous version of the XForms Data Model is being obsoleted while this work is underway. The plan is for the next revision to this Working Draft to provide a description of the functional requirements for the XForms data model and logic, together with proposals for meeting these requirements using XML Schema plus XForms property annotations, and an alternative lighter weight syntax aimed at HTML authors. Later specifications will focus on the user interface aspects of XForms, and the means to submit, suspend and resume forms. For more information on the goals of work on XForms, please look at the XForms Requirements.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-xforms-datamodel-20000815</howpublished>
		<field type="bibtex:index">XML, XForms</field>
		<title type="sharef:primaryTitle">XForms 1.0: Data Model</title>
		<field type="bibtex:topic">xforms[1]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2000/WD-xforms-datamodel-20000815</identifier>
	</reference>
	<reference name="xforms10" src="bibtex:misc" src-info="bibtex:line-32295" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Micah</givenname>
				<surname>Dubinko</surname>
			</person>
			<person>
				<givenname>Leigh L.</givenname>
				<surname>Klotz</surname>
			</person>
			<person>
				<givenname>Roland</givenname>
				<surname>Merrick</surname>
			</person>
			<person>
				<givenname>T. V.</givenname>
				<surname>Raman</surname>
			</person>
		</names>
		<date value="2003-10"/>
		<abstract>
			<richtext>
				<p>XForms is an XML application that represents the next generation of forms for the Web. By splitting traditional XHTML forms into three parts — XForms model, instance data, and user interface — it separates presentation from content, allows reuse, gives strong typing — reducing the number of round-trips to the server, as well as offering device independence and a reduced need for scripting. XForms is not a free-standing document type, but is intended to be integrated into other markup languages, such as XHTML or SVG.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Recommendation REC-xforms-20031014</howpublished>
		<title type="sharef:primaryTitle">XForms 1.0</title>
		<field type="bibtex:topic">xforms[1]</field>
		<field type="bibtex:updates">xforms10data</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2003/REC-xforms-20031014</identifier>
	</reference>
	<reference name="xforms10sec" src="bibtex:misc" src-info="bibtex:line-32307" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>John M.</givenname>
				<surname>Boyer</surname>
			</person>
			<person>
				<givenname>David</givenname>
				<surname>Landwehr</surname>
			</person>
			<person>
				<givenname>Roland</givenname>
				<surname>Merrick</surname>
			</person>
			<person>
				<givenname>T. V.</givenname>
				<surname>Raman</surname>
			</person>
		</names>
		<date value="2006-03"/>
		<abstract>
			<richtext>
				<p>XForms is an XML application that represents the next generation of forms for the Web. By splitting traditional XHTML forms into three parts — XForms model, instance data, and user interface — it separates presentation from content, allows reuse, gives strong typing — reducing the number of round-trips to the server, as well as offering device independence and a reduced need for scripting. XForms is not a free-standing document type, but is intended to be integrated into other markup languages, such as XHTML or SVG.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Recommendation REC-xforms-20060314</howpublished>
		<title type="sharef:primaryTitle">XForms 1.0 (Second Edition)</title>
		<field type="bibtex:topic">xforms[1]</field>
		<field type="bibtex:updates">xforms10</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2006/REC-xforms-20060314</identifier>
	</reference>
	<reference name="xforms10third" src="bibtex:misc" src-info="bibtex:line-32319" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>John M.</givenname>
				<surname>Boyer</surname>
			</person>
		</names>
		<date value="2007-10"/>
		<abstract>
			<richtext>
				<p>XForms is an XML application that represents the next generation of forms for the Web. By splitting traditional XHTML forms into three parts — XForms model, instance data, and user interface — it separates presentation from content, allows reuse, gives strong typing — reducing the number of round-trips to the server, as well as offering device independence and a reduced need for scripting. XForms is not a free-standing document type, but is intended to be integrated into other markup languages, such as XHTML or SVG.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Recommendation REC-xforms-20071029</howpublished>
		<title type="sharef:primaryTitle">XForms 1.0 (Third Edition)</title>
		<field type="bibtex:topic">xforms[1]</field>
		<field type="bibtex:updates">xforms10sec</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2007/REC-xforms-20071029</identifier>
	</reference>
	<reference name="xforms10basic" src="bibtex:misc" src-info="bibtex:line-32331" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Micah</givenname>
				<surname>Dubinko</surname>
			</person>
			<person>
				<givenname>T. V.</givenname>
				<surname>Raman</surname>
			</person>
		</names>
		<date value="2003-10"/>
		<abstract>
			<richtext>
				<p>The XForms Basic Profile describes a minimal level of XForms processing tailored to the needs of constrained devices and environments.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Candidate Recommendation CR-xforms-basic-20031014</howpublished>
		<title type="sharef:primaryTitle">XForms 1.0 Basic Profile</title>
		<field type="bibtex:topic">xforms[1]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2003/CR-xforms-basic-20031014</identifier>
	</reference>
	<reference name="xforms11req" src="bibtex:misc" src-info="bibtex:line-32342" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>John M.</givenname>
				<surname>Boyer</surname>
			</person>
			<person>
				<givenname>Roland</givenname>
				<surname>Merrick</surname>
			</person>
		</names>
		<date value="2004-08"/>
		<abstract>
			<richtext>
				<p>XForms is an XML application that represents the next generation of forms for the Web. This document specifies the requirements for XForms 1.1.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Note NOTE-xforms-11-req-20040831</howpublished>
		<title type="sharef:primaryTitle">XForms 1.1 Requirements</title>
		<field type="bibtex:topic">xforms[1]</field>
		<field type="bibtex:updates">xforms10</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2004/NOTE-xforms-11-req-20040831</identifier>
	</reference>
	<reference name="xforms11" src="bibtex:misc" src-info="bibtex:line-32354" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>John M.</givenname>
				<surname>Boyer</surname>
			</person>
		</names>
		<date value="2009-10"/>
		<abstract>
			<richtext>
				<p>XForms is an XML application that represents the next generation of forms for the Web. XForms is not a free-standing document type, but is intended to be integrated into other markup languages, such as XHTML, ODF or SVG. An XForms-based web form gathers and processes XML data using an architecture that separates presentation, purpose and content. The underlying data of a form is organized into instances of data schema (though formal schema definitions are not required). An XForm allows processing of data to occur using three mechanisms: (1) A declarative model composed of formulae for data calculations and constraints, data type and other property declarations, and data submission parameters. (2) A view layer composed of intent-based user interface controls. (3) An imperative controller for orchestrating data manipulations, interactions between the model and view layers, and data submissions. Thus, XForms accommodates form component reuse, fosters strong data type validation, eliminates unnecessary round-trips to the server, offers device independence and reduces the need for scripting. XForms 1.1 refines the XML processing platform introduced by XForms 1.0 by adding several new submission capabilities, action handlers, utility functions, user interface improvements, and helpful datatypes as well as a more powerful action processing facility, including conditional, iterated and background execution, the ability to manipulate data arbitrarily and to access event context information.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Recommendation REC-xforms-20091020</howpublished>
		<title type="sharef:primaryTitle">XForms 1.1</title>
		<field type="bibtex:topic">xforms[1]</field>
		<field type="bibtex:updates">xforms11req</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2009/REC-xforms-20091020</identifier>
	</reference>
	<reference name="xformsforhtml" src="bibtex:misc" src-info="bibtex:line-32366" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>John M.</givenname>
				<surname>Boyer</surname>
			</person>
		</names>
		<date value="2008-12"/>
		<abstract>
			<richtext>
				<p>XForms for HTML provides a set of attributes and script methods that can be used by the tags or elements of an HTML or XHTML web page to simplify the integration of data-intensive interactive processing capabilities from XForms. The semantics of the attributes are mapped to the rich XForms model-view-controller-connector architecture, thereby allowing web application authors a smoother, selective migration path to the higher-order behaviors available from the full element markup available in modules of XForms.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-XForms-for-HTML-20081219</howpublished>
		<title type="sharef:primaryTitle">XForms for HTML</title>
		<field type="bibtex:topic">xforms[0.9] html[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2008/WD-XForms-for-HTML-20081219</identifier>
	</reference>
	<reference name="webforms2" src="bibtex:misc" src-info="bibtex:line-32377" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Ian</givenname>
				<surname>Hickson</surname>
			</person>
		</names>
		<date value="2006-08"/>
		<abstract>
			<richtext>
				<p>This specification defines Web Forms 2.0, an extension to the forms features found in HTML 4's Forms chapter and the corresponding DOM2 HTML interfaces. Web Forms 2.0 applies to both HTML and XHTML user agents. It provides new strongly-typed input fields, new attributes for defining constraints, a repeating model for declarative repeating of form sections, new DOM interfaces, new DOM events for validation and dependency tracking, and XML submission and initialization of forms. It also standardizes and codifies existing practice in areas that have not been previously documented, and clarifies some of the interactions of HTML form controls and CSS. HTML 4, XHTML 1.1, and the DOM are thus extended in a manner that has a clear migration path from existing HTML forms, leveraging the knowledge authors have built up with their experience with HTML so far.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-web-forms-2-20060821</howpublished>
		<title type="sharef:primaryTitle">Web Forms 2.0</title>
		<field type="bibtex:topic">htmlforms[1]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2006/WD-web-forms-2-20060821</identifier>
	</reference>
	<reference name="xmlqdata" src="bibtex:misc" src-info="bibtex:line-32388" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Mary F.</givenname>
				<surname>Fernández</surname>
			</person>
			<person>
				<givenname>Ashok</givenname>
				<surname>Malhotra</surname>
			</person>
			<person>
				<givenname>Jonathan</givenname>
				<surname>Marsh</surname>
			</person>
			<person>
				<givenname>Marton</givenname>
				<surname>Nagy</surname>
			</person>
			<person>
				<givenname>Norman</givenname>
				<surname>Walsh</surname>
			</person>
		</names>
		<date value="2007-01"/>
		<abstract>
			<richtext>
				<p>This document defines the W3C XQuery 1.0 and XPath 2.0 Data Model (XDM), which is the data model of at least XPath 2.0, XSLT 2.0, and XQuery, and any other specifications that reference it. This data model is based on the XPath 1.0 data model and earlier work on an XML Query Data Model. This document is the result of joint work by the XSL Working Group and the XML Query Working Group.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Recommendation REC-xpath-datamodel-20070123</howpublished>
		<title type="sharef:primaryTitle">XQuery 1.0 and XPath 2.0 Data Model (XDM)</title>
		<field type="bibtex:topic">xquery[0.9] xpath2[0.9] xdm[1]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2007/REC-xpath-datamodel-20070123</identifier>
	</reference>
	<reference name="xmlqdata2nd" src="bibtex:misc" src-info="bibtex:line-32399" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Anders</givenname>
				<surname>Berglund</surname>
			</person>
			<person>
				<givenname>Mary F.</givenname>
				<surname>Fernández</surname>
			</person>
			<person>
				<givenname>Ashok</givenname>
				<surname>Malhotra</surname>
			</person>
			<person>
				<givenname>Jonathan</givenname>
				<surname>Marsh</surname>
			</person>
			<person>
				<givenname>Marton</givenname>
				<surname>Nagy</surname>
			</person>
			<person>
				<givenname>Norman</givenname>
				<surname>Walsh</surname>
			</person>
		</names>
		<date value="2010-12"/>
		<abstract>
			<richtext>
				<p>This document defines the W3C XQuery 1.0 and XPath 2.0 Data Model (XDM), which is the data model of XML Path Language (XPath) 2.0 (Second Edition), XSLT 2.0 (Second Edition), and XQuery, and any other specifications that reference it. This data model is based on the XPath 1.0 data model and earlier work on an XML Query Data Model. This document is the result of joint work by the XSL Working Group and the XML Query Working Group.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Recommendation REC-xpath-datamodel-20101214</howpublished>
		<title type="sharef:primaryTitle">XQuery 1.0 and XPath 2.0 Data Model (XDM) (Second Edition)</title>
		<field type="bibtex:topic">xquery[0.9] xpath2[0.9] xdm[1]</field>
		<field type="bibtex:updates">xmlqdata</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2010/REC-xpath-datamodel-20101214</identifier>
	</reference>
	<reference name="xmlqdata11" src="bibtex:misc" src-info="bibtex:line-32411" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Norman</givenname>
				<surname>Walsh</surname>
			</person>
			<person>
				<givenname>Anders</givenname>
				<surname>Berglund</surname>
			</person>
			<person>
				<givenname>John</givenname>
				<surname>Snelson</surname>
			</person>
		</names>
		<date value="2009-12"/>
		<abstract>
			<richtext>
				<p>This document defines the XQuery and XPath Data Model 1.1, which is the data model of XML Path Language (XPath) 2.1, XSL Transformations (XSLT) Version 2.1, and XQuery 1.1: An XML Query Language, and any other specifications that reference it. This document is the result of joint work by the XSL Working Group and the XML Query Working Group.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-xpath-datamodel-11-20091215</howpublished>
		<title type="sharef:primaryTitle">XQuery and XPath Data Model 1.1</title>
		<field type="bibtex:topic">xquery[0.9] xpath2[0.9]</field>
		<field type="bibtex:updates">xmlqdata2nd</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2009/WD-xpath-datamodel-11-20091215</identifier>
	</reference>
	<reference name="xpathdatamodel30" src="bibtex:misc" src-info="bibtex:line-32423" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Norman</givenname>
				<surname>Walsh</surname>
			</person>
			<person>
				<givenname>Anders</givenname>
				<surname>Berglund</surname>
			</person>
			<person>
				<givenname>John</givenname>
				<surname>Snelson</surname>
			</person>
		</names>
		<date value="2010-12"/>
		<abstract>
			<richtext>
				<p>This document defines the XQuery and XPath Data Model 3.0, which is the data model of XML Path Language (XPath) 3.0, XSL Transformations (XSLT) Version 3.0, and XQuery 3.0: An XML Query Language, and any other specifications that reference it. This document is the result of joint work by the XSL Working Group and the XML Query Working Group.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-xpath-datamodel-30-20101214</howpublished>
		<title type="sharef:primaryTitle">XQuery and XPath Data Model 3.0</title>
		<field type="bibtex:topic">xquery[0.9] xpath2[0.9]</field>
		<field type="bibtex:updates">xmlqdata11</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2010/WD-xpath-datamodel-30-20101214</identifier>
	</reference>
	<reference name="xmlqalg" src="bibtex:misc" src-info="bibtex:line-32435" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Peter</givenname>
				<surname>Fankhauser</surname>
			</person>
			<person>
				<givenname>Mary F.</givenname>
				<surname>Fernández</surname>
			</person>
			<person>
				<givenname>Ashok</givenname>
				<surname>Malhotra</surname>
			</person>
			<person>
				<givenname>Michael</givenname>
				<surname>Rys</surname>
			</person>
			<person>
				<givenname>Jérôme</givenname>
				<surname>Siméon</surname>
			</person>
			<person>
				<givenname>Philip</givenname>
				<surname>Wadler</surname>
			</person>
		</names>
		<date value="2001-02"/>
		<howpublished>World Wide Web Consortium, Working Draft WD-query-algebra-20010215</howpublished>
		<title type="sharef:primaryTitle">The XML Query Algebra</title>
		<field type="bibtex:topic">xquery[1]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2001/WD-query-algebra-20010215</identifier>
	</reference>
	<reference name="xquerysem" src="bibtex:misc" src-info="bibtex:line-32445" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Denise</givenname>
				<surname>Draper</surname>
			</person>
			<person>
				<givenname>Peter</givenname>
				<surname>Fankhauser</surname>
			</person>
			<person>
				<givenname>Mary F.</givenname>
				<surname>Fernández</surname>
			</person>
			<person>
				<givenname>Ashok</givenname>
				<surname>Malhotra</surname>
			</person>
			<person>
				<givenname>Kristoffer H.</givenname>
				<surname>Rose</surname>
			</person>
			<person>
				<givenname>Michael</givenname>
				<surname>Rys</surname>
			</person>
			<person>
				<givenname>Jérôme</givenname>
				<surname>Siméon</surname>
			</person>
			<person>
				<givenname>Philip</givenname>
				<surname>Wadler</surname>
			</person>
		</names>
		<date value="2007-01"/>
		<abstract>
			<richtext>
				<p>This document defines formally the semantics of XQuery 1.0 and XPath 2.0.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Recommendation REC-xquery-semantics-20070123</howpublished>
		<title type="sharef:primaryTitle">XQuery 1.0 and XPath 2.0 Formal Semantics</title>
		<field type="bibtex:topic">xquery[1] xpath2[1]</field>
		<field type="bibtex:updates">xmlqalg</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2007/REC-xquery-semantics-20070123</identifier>
	</reference>
	<reference name="xquerysem2nd" src="bibtex:misc" src-info="bibtex:line-32457" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Denise</givenname>
				<surname>Draper</surname>
			</person>
			<person>
				<givenname>Michael</givenname>
				<surname>Dyck</surname>
			</person>
			<person>
				<givenname>Peter</givenname>
				<surname>Fankhauser</surname>
			</person>
			<person>
				<givenname>Mary F.</givenname>
				<surname>Fernández</surname>
			</person>
			<person>
				<givenname>Ashok</givenname>
				<surname>Malhotra</surname>
			</person>
			<person>
				<givenname>Kristoffer H.</givenname>
				<surname>Rose</surname>
			</person>
			<person>
				<givenname>Michael</givenname>
				<surname>Rys</surname>
			</person>
			<person>
				<givenname>Jérôme</givenname>
				<surname>Siméon</surname>
			</person>
			<person>
				<givenname>Philip</givenname>
				<surname>Wadler</surname>
			</person>
		</names>
		<date value="2010-12"/>
		<abstract>
			<richtext>
				<p>This document defines formally the semantics of XQuery 1.0 (Second Edition) and XPath 2.0 (Second Edition).</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Recommendation REC-xquery-semantics-20101214</howpublished>
		<title type="sharef:primaryTitle">XQuery 1.0 and XPath 2.0 Formal Semantics (Second Edition)</title>
		<field type="bibtex:topic">xquery[1] xpath2[1]</field>
		<field type="bibtex:updates">xquerysem</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2010/REC-xquery-semantics-20101214</identifier>
	</reference>
	<reference name="xmlqreq" src="bibtex:misc" src-info="bibtex:line-32469" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Donald D.</givenname>
				<surname>Chamberlin</surname>
			</person>
			<person>
				<givenname>Peter</givenname>
				<surname>Fankhauser</surname>
			</person>
			<person>
				<givenname>Massimo</givenname>
				<surname>Marchiori</surname>
			</person>
			<person>
				<givenname>Jonathan</givenname>
				<surname>Robie</surname>
			</person>
		</names>
		<date value="2007-03"/>
		<abstract>
			<richtext>
				<p>This document specifies goals, requirements, and usage scenarios for the W3C XML Query (XQuery) data model and query language. It also includes, for each requirement, a corresponding status, indicating the current situation of the requirement in the XML Query family of specifications.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Note NOTE-xquery-requirements-20070323</howpublished>
		<title type="sharef:primaryTitle">XML Query (XQuery) Requirements</title>
		<field type="bibtex:topic">xquery[0.7]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2007/NOTE-xquery-requirements-20070323</identifier>
	</reference>
	<reference name="xquery11requirements" src="bibtex:misc" src-info="bibtex:line-32480" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Daniel</givenname>
				<surname>Engovatov</surname>
			</person>
			<person>
				<givenname>Jonathan</givenname>
				<surname>Robie</surname>
			</person>
		</names>
		<date value="2009-12"/>
		<abstract>
			<richtext>
				<p>This document specifies goals and requirements for XML Query (XQuery) 1.1.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-xquery-11-requirements-20091215</howpublished>
		<title type="sharef:primaryTitle">XML Query (XQuery) 1.1 Requirements</title>
		<field type="bibtex:topic">xquery[0.7]</field>
		<field type="bibtex:updates">xquery</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2009/WD-xquery-11-requirements-20091215</identifier>
	</reference>
	<reference name="xqueryupdatereq" src="bibtex:misc" src-info="bibtex:line-32492" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Donald D.</givenname>
				<surname>Chamberlin</surname>
			</person>
			<person>
				<givenname>Jonathan</givenname>
				<surname>Robie</surname>
			</person>
		</names>
		<date value="2011-01"/>
		<abstract>
			<richtext>
				<p>This document specifies goals and requirements for the XQuery Update Facility.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Note NOTE-xquery-update-10-requirements-20110125</howpublished>
		<title type="sharef:primaryTitle">XQuery Update Facility 1.0 Requirements</title>
		<field type="bibtex:topic">xquery[0.7]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2011/NOTE-xquery-update-10-requirements-20110125</identifier>
	</reference>
	<reference name="xqupdateusecases" src="bibtex:misc" src-info="bibtex:line-32503" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Ioana</givenname>
				<surname>Manolescu</surname>
			</person>
			<person>
				<givenname>Jonathan</givenname>
				<surname>Robie</surname>
			</person>
		</names>
		<date value="2011-01"/>
		<abstract>
			<richtext>
				<p>This document specifies usage scenarios for the XQuery Update Facility.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Note NOTE-xquery-update-10-use-cases-20110125</howpublished>
		<title type="sharef:primaryTitle">XQuery Update Facility 1.0 Use Cases</title>
		<field type="bibtex:topic">xquery[0.7]</field>
		<field type="bibtex:updates">xqueryupdatereq</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2011/NOTE-xquery-update-10-use-cases-20110125</identifier>
	</reference>
	<reference name="xqupdate" src="bibtex:misc" src-info="bibtex:line-32515" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Jonathan</givenname>
				<surname>Robie</surname>
			</person>
			<person>
				<givenname>Donald D.</givenname>
				<surname>Chamberlin</surname>
			</person>
			<person>
				<givenname>Michael</givenname>
				<surname>Dyck</surname>
			</person>
			<person>
				<givenname>Daniela</givenname>
				<surname>Florescu</surname>
			</person>
			<person>
				<givenname>Jim</givenname>
				<surname>Melton</surname>
			</person>
			<person>
				<givenname>Jérôme</givenname>
				<surname>Siméon</surname>
			</person>
		</names>
		<date value="2011-03"/>
		<abstract>
			<richtext>
				<p>This document defines an update facility that extends the XML Query language, XQuery. The XQuery Update Facility provides expressions that can be used to make persistent changes to instances of the XQuery 1.0 and XPath 2.0 Data Model.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Recommendation REC-xquery-update-10-20110317</howpublished>
		<title type="sharef:primaryTitle">XQuery Update Facility 1.0</title>
		<field type="bibtex:topic">xquery[0.9]</field>
		<field type="bibtex:updates">xqupdateusecases</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2011/REC-xquery-update-10-20110317</identifier>
	</reference>
	<reference name="xmlqusecase" src="bibtex:misc" src-info="bibtex:line-32527" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Donald D.</givenname>
				<surname>Chamberlin</surname>
			</person>
			<person>
				<givenname>Peter</givenname>
				<surname>Fankhauser</surname>
			</person>
			<person>
				<givenname>Daniela</givenname>
				<surname>Florescu</surname>
			</person>
			<person>
				<givenname>Massimo</givenname>
				<surname>Marchiori</surname>
			</person>
			<person>
				<givenname>Jonathan</givenname>
				<surname>Robie</surname>
			</person>
		</names>
		<date value="2007-03"/>
		<abstract>
			<richtext>
				<p>This document specifies usage scenarios for XQuery.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Note NOTE-xquery-use-cases-20070323</howpublished>
		<title type="sharef:primaryTitle">XML Query Use Cases</title>
		<field type="bibtex:topic">xquery[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2007/NOTE-xquery-use-cases-20070323</identifier>
	</reference>
	<reference name="xquery" src="bibtex:misc" src-info="bibtex:line-32538" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Scott</givenname>
				<surname>Boag</surname>
			</person>
			<person>
				<givenname>Donald D.</givenname>
				<surname>Chamberlin</surname>
			</person>
			<person>
				<givenname>Mary F.</givenname>
				<surname>Fernández</surname>
			</person>
			<person>
				<givenname>Daniela</givenname>
				<surname>Florescu</surname>
			</person>
			<person>
				<givenname>Jonathan</givenname>
				<surname>Robie</surname>
			</person>
			<person>
				<givenname>Jérôme</givenname>
				<surname>Siméon</surname>
			</person>
		</names>
		<date value="2007-01"/>
		<abstract>
			<richtext>
				<p>XML is a versatile markup language, capable of labeling the information content of diverse data sources including structured and semi-structured documents, relational databases, and object repositories. A query language that uses the structure of XML intelligently can express queries across all these kinds of data, whether physically stored in XML or viewed as XML via middleware. This specification describes a query language called XQuery, which is designed to be broadly applicable across many types of XML data sources.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Recommendation REC-xquery-20070123</howpublished>
		<title type="sharef:primaryTitle">XQuery 1.0: An XML Query Language</title>
		<field type="bibtex:topic">xquery[1]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2007/REC-xquery-20070123</identifier>
	</reference>
	<reference name="xquery2nd" src="bibtex:misc" src-info="bibtex:line-32549" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Scott</givenname>
				<surname>Boag</surname>
			</person>
			<person>
				<givenname>Donald D.</givenname>
				<surname>Chamberlin</surname>
			</person>
			<person>
				<givenname>Mary F.</givenname>
				<surname>Fernández</surname>
			</person>
			<person>
				<givenname>Daniela</givenname>
				<surname>Florescu</surname>
			</person>
			<person>
				<givenname>Jonathan</givenname>
				<surname>Robie</surname>
			</person>
			<person>
				<givenname>Jérôme</givenname>
				<surname>Siméon</surname>
			</person>
		</names>
		<date value="2010-12"/>
		<abstract>
			<richtext>
				<p>XML is a versatile markup language, capable of labeling the information content of diverse data sources including structured and semi-structured documents, relational databases, and object repositories. A query language that uses the structure of XML intelligently can express queries across all these kinds of data, whether physically stored in XML or viewed as XML via middleware. This specification describes a query language called XQuery, which is designed to be broadly applicable across many types of XML data sources.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Recommendation REC-xquery-20101214</howpublished>
		<title type="sharef:primaryTitle">XQuery 1.0: An XML Query Language (Second Edition)</title>
		<field type="bibtex:topic">xquery[1]</field>
		<field type="bibtex:updates">xquery</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2010/REC-xquery-20101214</identifier>
	</reference>
	<reference name="xquerysx10requirements" src="bibtex:misc" src-info="bibtex:line-32561" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Daniel</givenname>
				<surname>Engovatov</surname>
			</person>
			<person>
				<givenname>Daniela</givenname>
				<surname>Florescu</surname>
			</person>
			<person>
				<givenname>Giorgio</givenname>
				<surname>Ghelli</surname>
			</person>
		</names>
		<date value="2007-03"/>
		<abstract>
			<richtext>
				<p>This document specifies goals and requirements for the XQuery Scripting Extension.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-xquery-sx-10-requirements-20070323</howpublished>
		<title type="sharef:primaryTitle">XQuery Scripting Extension 1.0 Requirements</title>
		<field type="bibtex:topic">xquery[0.8] xquerysx[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2007/WD-xquery-sx-10-requirements-20070323</identifier>
	</reference>
	<reference name="xquerysx10usecases" src="bibtex:misc" src-info="bibtex:line-32572" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>John</givenname>
				<surname>Snelson</surname>
			</person>
		</names>
		<date value="2008-12"/>
		<abstract>
			<richtext>
				<p>This document specifies usage scenarios for the XQuery Scripting Extension.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-xquery-sx-10-use-cases-20081203</howpublished>
		<title type="sharef:primaryTitle">XQuery Scripting Extension 1.0 Use Cases</title>
		<field type="bibtex:topic">xquerysx[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2008/WD-xquery-sx-10-use-cases-20081203</identifier>
	</reference>
	<reference name="xquerysx10" src="bibtex:misc" src-info="bibtex:line-32583" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>John</givenname>
				<surname>Snelson</surname>
			</person>
			<person>
				<givenname>Don</givenname>
				<surname>Chamberlin</surname>
			</person>
			<person>
				<givenname>Daniel</givenname>
				<surname>Engovatov</surname>
			</person>
			<person>
				<givenname>Dana</givenname>
				<surname>Florescu</surname>
			</person>
			<person>
				<givenname>Giorgio</givenname>
				<surname>Ghelli</surname>
			</person>
			<person>
				<givenname>Jim</givenname>
				<surname>Melton</surname>
			</person>
			<person>
				<givenname>Jérôme</givenname>
				<surname>Siméon</surname>
			</person>
		</names>
		<date value="2010-04"/>
		<abstract>
			<richtext>
				<p>This specification defines an extension to XQuery 1.0 and XQuery Update Facility. Expressions can be evaluated in a specific order, with later expressions seeing the effects of the expressions that came before them. This specification introduces several new kinds of expression, including the apply, assignment, while, and exit expression, and a block expression with local variable declarations.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-xquery-sx-10-20100408</howpublished>
		<title type="sharef:primaryTitle">XQuery Scripting Extension 1.0</title>
		<field type="bibtex:topic">xquery[0.9] xquerysx[1]</field>
		<field type="bibtex:updates">xquerysx10requirements</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2010/WD-xquery-sx-10-20100408</identifier>
	</reference>
	<reference name="xquery11usecases" src="bibtex:misc" src-info="bibtex:line-32595" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Tim</givenname>
				<surname>Kraska</surname>
			</person>
		</names>
		<date value="2008-12"/>
		<abstract>
			<richtext>
				<p>This document specifies usage scenarios for XML Query (XQuery) 1.1.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-xquery-11-use-cases-20081203</howpublished>
		<title type="sharef:primaryTitle">XML Query (XQuery) 1.1 Use Cases</title>
		<field type="bibtex:topic">xquery[0.9]</field>
		<field type="bibtex:updates">xquery xmlqusecase</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2008/WD-xquery-11-use-cases-20081203</identifier>
	</reference>
	<reference name="xquery30usecases" src="bibtex:misc" src-info="bibtex:line-32607" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Tim</givenname>
				<surname>Kraska</surname>
			</person>
		</names>
		<date value="2010-12"/>
		<abstract>
			<richtext>
				<p>This document specifies usage scenarios for XML Query (XQuery) 3.0.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-xquery-30-use-cases-20101214</howpublished>
		<title type="sharef:primaryTitle">XQuery 3.0 Use Cases</title>
		<field type="bibtex:topic">xquery[0.9]</field>
		<field type="bibtex:updates">xquery11usecases</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2010/WD-xquery-30-use-cases-20101214</identifier>
	</reference>
	<reference name="xquery11" src="bibtex:misc" src-info="bibtex:line-32619" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Jonathan</givenname>
				<surname>Robie</surname>
			</person>
			<person>
				<givenname>Don</givenname>
				<surname>Chamberlin</surname>
			</person>
			<person>
				<givenname>Michael</givenname>
				<surname>Dyck</surname>
			</person>
			<person>
				<givenname>John</givenname>
				<surname>Snelson</surname>
			</person>
		</names>
		<date value="2009-12"/>
		<abstract>
			<richtext>
				<p>XML is a versatile markup language, capable of labeling the information content of diverse data sources including structured and semi-structured documents, relational databases, and object repositories. A query language that uses the structure of XML intelligently can express queries across all these kinds of data, whether physically stored in XML or viewed as XML via middleware. This specification describes a query language called XQuery, which is designed to be broadly applicable across many types of XML data sources. XQuery 1.1 is an extended version of the XQuery 1.0 Recommendation published on 23 January 2007. A list of changes made since XQuery 1.0 can be found in K Revision Log. Here are some of the new features in XQuery 1.1: 1. group by clause in FLWOR Expressions (3.8.7 Group By Clause). 2. tumbling window and sliding window in FLWOR Expressions (3.8.4 Window Clause). 3. count clause in FLWOR Expressions (3.8.6 Count Clause). 4. allowing empty in 3.8.2 For Clause, for functionality similar to outer joins in SQL. 5. try/catch expressions (3.13 Try/Catch Expressions). 6. Dynamic function invocation (3.1.8 Dynamic Function Invocation). 7. Inline functions (3.1.7 Inline Functions). 8. Private functions (4.17 Function Declaration). 9. Nondeterministic functions (4.17 Function Declaration) 10. Switch expressions (3.11 Switch Expression) 11. Computed namespace constructors (3.7.3.7 Computed Namespace Constructors). 12. Output declarations (2.2.4 Serialization).</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-xquery-11-20091215</howpublished>
		<title type="sharef:primaryTitle">XQuery 1.1: An XML Query Language</title>
		<field type="bibtex:topic">xquery[1]</field>
		<field type="bibtex:updates">xquery</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2009/WD-xquery-11-20091215</identifier>
	</reference>
	<reference name="xquery30" src="bibtex:misc" src-info="bibtex:line-32631" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Jonathan</givenname>
				<surname>Robie</surname>
			</person>
			<person>
				<givenname>Don</givenname>
				<surname>Chamberlin</surname>
			</person>
			<person>
				<givenname>Michael</givenname>
				<surname>Dyck</surname>
			</person>
			<person>
				<givenname>John</givenname>
				<surname>Snelson</surname>
			</person>
		</names>
		<date value="2010-12"/>
		<abstract>
			<richtext>
				<p>XML is a versatile markup language, capable of labeling the information content of diverse data sources including structured and semi-structured documents, relational databases, and object repositories. A query language that uses the structure of XML intelligently can express queries across all these kinds of data, whether physically stored in XML or viewed as XML via middleware. This specification describes a query language called XQuery, which is designed to be broadly applicable across many types of XML data sources. XQuery 3.0 is an extended version of the XQuery 1.0 Recommendation published on 23 January 2007.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-xquery-30-20101214</howpublished>
		<title type="sharef:primaryTitle">XQuery 3.0: An XML Query Language</title>
		<field type="bibtex:topic">xquery[1]</field>
		<field type="bibtex:updates">xquery11</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2010/WD-xquery-30-20101214</identifier>
	</reference>
	<reference name="xq10xp20fo" src="bibtex:misc" src-info="bibtex:line-32643" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Ashok</givenname>
				<surname>Malhotra</surname>
			</person>
			<person>
				<givenname>Jim</givenname>
				<surname>Melton</surname>
			</person>
			<person>
				<givenname>Norman</givenname>
				<surname>Walsh</surname>
			</person>
		</names>
		<date value="2007-01"/>
		<abstract>
			<richtext>
				<p>This document defines constructor functions, operators and functions on the datatypes defined in "XML Schema Part 2: Datatypes Second Edition" and the datatypes defined in "XQuery 1.0 and XPath 2.0 Data Model". It also discusses functions and operators on nodes and node sequences as defined in XDM. These functions and operators are defined for use in XPath) 2.0, XQuery 1.0 and XSLT 2.0 and other related XML standards. The signatures and summaries of functions defined in this document are available at: http://www.w3.org/2006/xpath-functions.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Recommendation REC-xpath-functions-20070123</howpublished>
		<title type="sharef:primaryTitle">XQuery 1.0 and XPath 2.0 Functions and Operators</title>
		<field type="bibtex:topic">xquery[1] xpath2[1] xdm[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2007/REC-xpath-functions-20070123</identifier>
	</reference>
	<reference name="xq10xp20fo2nd" src="bibtex:misc" src-info="bibtex:line-32654" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Ashok</givenname>
				<surname>Malhotra</surname>
			</person>
			<person>
				<givenname>Jim</givenname>
				<surname>Melton</surname>
			</person>
			<person>
				<givenname>Norman</givenname>
				<surname>Walsh</surname>
			</person>
			<person>
				<givenname>Michael</givenname>
				<surname>Kay</surname>
			</person>
		</names>
		<date value="2010-12"/>
		<abstract>
			<richtext>
				<p>This document defines constructor functions, operators and functions on the datatypes defined in "XML Schema Part 2: Datatypes Second Edition" and the datatypes defined in "XQuery 1.0 and XPath 2.0 Data Model". It also discusses functions and operators on nodes and node sequences as defined in XDM. These functions and operators are defined for use in XPath) 2.0, XQuery 1.0 and XSLT 2.0 and other related XML standards. The signatures and summaries of functions defined in this document are available at: http://www.w3.org/2006/xpath-functions.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Recommendation REC-xpath-functions-20101214</howpublished>
		<title type="sharef:primaryTitle">XQuery 1.0 and XPath 2.0 Functions and Operators (Second Edition)</title>
		<field type="bibtex:topic">xquery[1] xpath2[1] xdm[0.9]</field>
		<field type="bibtex:updates">xq10xp20fo</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2010/REC-xpath-functions-20101214</identifier>
	</reference>
	<reference name="xq10xp20fo11" src="bibtex:misc" src-info="bibtex:line-32666" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Michael</givenname>
				<surname>Kay</surname>
			</person>
		</names>
		<date value="2009-12"/>
		<abstract>
			<richtext>
				<p>This document defines constructor functions, operators, and functions on the datatypes defined in XML Schema Part 2: Datatypes Second Edition and the datatypes defined in XQuery and XPath Data Model (XDM) 1.1. It also defines functions and operators on nodes and node sequences as defined in the XQuery and XPath Data Model (XDM) 1.1. These functions and operators are defined for use in XML Path Language (XPath) 2.1, XQuery 1.1: An XML Query Language and XSL Transformations (XSLT) Version 2.1 and other related XML standards. The signatures and summaries of functions defined in this document are available at: http://www.w3.org/2005/xpath-functions. This is the third version of the specification of this function library. The first version was included as an intrinsic part of the XML Path Language (XPath) Version 1.0 specification published on 16 November 1999. The second version was published under the title XQuery 1.0 and XPath 2.0 Functions and Operators on 23 January 2007. This third version is the first to carry its own version number, which has been arbitrarily set at 1.1 to align with version numbering for XQuery.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-xpath-functions-11-20091215</howpublished>
		<title type="sharef:primaryTitle">XPath and XQuery Functions and Operators 1.1</title>
		<field type="bibtex:topic">xquery[1] xpath2[1] xdm[0.9]</field>
		<field type="bibtex:updates">xq10xp20fo2nd</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2009/WD-xpath-functions-11-20091215</identifier>
	</reference>
	<reference name="xpathfunctions30" src="bibtex:misc" src-info="bibtex:line-32678" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Michael</givenname>
				<surname>Kay</surname>
			</person>
		</names>
		<date value="2010-12"/>
		<abstract>
			<richtext>
				<p>This is a draft for internal review. Change markings are relative to the Recommendation of 23 January 2007. This document defines constructor functions, operators, and functions on the datatypes defined in XML Schema Part 2: Datatypes Second Edition and the datatypes defined in XQuery and XPath Data Model (XDM) 3.0. It also defines functions and operators on nodes and node sequences as defined in the XQuery and XPath Data Model (XDM) 3.0. These functions and operators are defined for use in XML Path Language (XPath) 3.0, XQuery 3.0: An XML Query Language and XSL Transformations (XSLT) Version 3.0 and other related XML standards. The signatures and summaries of functions defined in this document are available at: http://www.w3.org/2005/xpath-functions/. This is the third version of the specification of this function library. The first version was included as an intrinsic part of the XML Path Language (XPath) Version 1.0 specification published on 16 November 1999. The second version was published under the title XQuery 1.0 and XPath 2.0 Functions and Operators on 23 January 2007. This third version is the first to carry its own version number, which has been set at 3.0 to align with version numbering for XPath, XQuery, and XSLT. A previous draft of this version of the specification carried the version number 1.1.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-xpath-functions-30-20101214</howpublished>
		<title type="sharef:primaryTitle">XPath and XQuery Functions and Operators 3.0</title>
		<field type="bibtex:topic">xquery[1] xpath2[1] xdm[0.9]</field>
		<field type="bibtex:updates">xq10xp20fo11</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2010/WD-xpath-functions-30-20101214</identifier>
	</reference>
	<reference name="xpathfullusecase" src="bibtex:misc" src-info="bibtex:line-32690" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Pat</givenname>
				<surname>Case</surname>
			</person>
			<person>
				<givenname>Sihem</givenname>
				<surname>Amer-Yahia</surname>
			</person>
		</names>
		<date value="2011-01"/>
		<abstract>
			<richtext>
				<p>This document specifies usage scenarios for full-text queries as part of XQuery 1.0 and XPath 2.0.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Note NOTE-xpath-full-text-10-use-cases-20110125</howpublished>
		<title type="sharef:primaryTitle">XQuery 1.0 and XPath 2.0 Full-Text 1.0 Use Cases</title>
		<field type="bibtex:topic">xquery[1] xpath2[1]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2011/NOTE-xpath-full-text-10-use-cases-20110125</identifier>
	</reference>
	<reference name="xpathfullreq" src="bibtex:misc" src-info="bibtex:line-32701" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Stephen</givenname>
				<surname>Buxton</surname>
			</person>
			<person>
				<givenname>Pat</givenname>
				<surname>Case</surname>
			</person>
			<person>
				<givenname>Michael</givenname>
				<surname>Rys</surname>
			</person>
		</names>
		<date value="2011-01"/>
		<abstract>
			<richtext>
				<p>The document specifies requirements for Full-Text Search for use in XQuery 1.0 and XPath 2.0.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Note NOTE-xpath-full-text-10-requirements-20110125</howpublished>
		<title type="sharef:primaryTitle">XQuery 1.0 and XPath 2.0 Full-Text 1.0 Requirements</title>
		<field type="bibtex:topic">xquery[1] xpath2[1]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2011/NOTE-xpath-full-text-10-requirements-20110125</identifier>
	</reference>
	<reference name="xpathfulltext" src="bibtex:misc" src-info="bibtex:line-32712" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Pat</givenname>
				<surname>Case</surname>
			</person>
			<person>
				<givenname>Michael</givenname>
				<surname>Dyck</surname>
			</person>
			<person>
				<givenname>Mary</givenname>
				<surname>Holstege</surname>
			</person>
			<person>
				<givenname>Sihem</givenname>
				<surname>Amer-Yahia</surname>
			</person>
			<person>
				<givenname>Chavdar</givenname>
				<surname>Botev</surname>
			</person>
			<person>
				<givenname>Stephen</givenname>
				<surname>Buxton</surname>
			</person>
			<person>
				<givenname>Jochen</givenname>
				<surname>Dörre</surname>
			</person>
			<person>
				<givenname>Jim</givenname>
				<surname>Melton</surname>
			</person>
			<person>
				<givenname>Michael</givenname>
				<surname>Rys</surname>
			</person>
			<person>
				<givenname>Jayavel</givenname>
				<surname>Shanmugasundaram</surname>
			</person>
		</names>
		<date value="2011-03"/>
		<abstract>
			<richtext>
				<p>This document defines the syntax and formal semantics of XQuery and XPath Full Text 1.0, which is a language that extends XQuery 1.0 and XPath 2.0 with full-text search capabilities.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Recommendation REC-xpath-full-text-10-20110317</howpublished>
		<title type="sharef:primaryTitle">XQuery and XPath Full Text 1.0</title>
		<field type="bibtex:topic">xquery[1] xpath2[1]</field>
		<field type="bibtex:updates">xpathfullusecase xpathfullreq</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2011/REC-xpath-full-text-10-20110317</identifier>
	</reference>
	<reference name="xmlsigsp" src="bibtex:misc" src-info="bibtex:line-32724" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Donald E.</givenname>
				<surname>Eastlake</surname>
			</person>
			<person>
				<givenname>Joseph M.</givenname>
				<surname>Reagle</surname>
			</person>
			<person>
				<givenname>David</givenname>
				<surname>Solo</surname>
			</person>
		</names>
		<date value="2002-02"/>
		<abstract>
			<richtext>
				<p>This document specifies XML digital signature processing rules and syntax. XML Signatures provide integrity, message authentication, and/or signer authentication services for data of any type, whether located within the XML that includes the signature or elsewhere.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Recommendation REC-xmldsig-core-20020212</howpublished>
		<title type="sharef:primaryTitle">XML-Signature Syntax and Processing</title>
		<field type="bibtex:topic">xmldsig[1]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2002/REC-xmldsig-core-20020212</identifier>
	</reference>
	<reference name="xmldsigcore2" src="bibtex:misc" src-info="bibtex:line-32735" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Mark</givenname>
				<surname>Bartel</surname>
			</person>
			<person>
				<givenname>John</givenname>
				<surname>Boyer</surname>
			</person>
			<person>
				<givenname>Barb</givenname>
				<surname>Fox</surname>
			</person>
			<person>
				<givenname>Brian</givenname>
				<surname>LaMacchia</surname>
			</person>
			<person>
				<givenname>Ed</givenname>
				<surname>Simon</surname>
			</person>
		</names>
		<names type="sharef:editor">
			<person>
				<givenname>Donald E.</givenname>
				<surname>Eastlake</surname>
			</person>
			<person>
				<givenname>Joseph M.</givenname>
				<surname>Reagle</surname>
			</person>
			<person>
				<givenname>David</givenname>
				<surname>Solo</surname>
			</person>
			<person>
				<givenname>Frederick</givenname>
				<surname>Hirsch</surname>
			</person>
			<person>
				<givenname>Thomas</givenname>
				<surname>Roessler</surname>
			</person>
			<person>
				<givenname>Kelvin</givenname>
				<surname>Yiu</surname>
			</person>
			<person>
				<givenname>Pratik</givenname>
				<surname>Datta</surname>
			</person>
		</names>
		<date value="2010-08"/>
		<abstract>
			<richtext>
				<p>This document specifies XML digital signature processing rules and syntax. XML Signatures provide integrity, message authentication, and/or signer authentication services for data of any type, whether located within the XML that includes the signature or elsewhere.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-xmldsig-core2-20100831</howpublished>
		<title type="sharef:primaryTitle">XML Signature Syntax and Processing Version 2.0</title>
		<field type="bibtex:topic">xmldsig[1] xpath1[0.7]</field>
		<field type="bibtex:updates">xmlsigsp xmldsigsimplify</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2010/WD-xmldsig-core2-20100831</identifier>
	</reference>
	<reference name="xmldsigxpath" src="bibtex:misc" src-info="bibtex:line-32748" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Pratik</givenname>
				<surname>Datta</surname>
			</person>
		</names>
		<date value="2010-08"/>
		<abstract>
			<richtext>
				<p>This document defines a streamable profile of XPath 1.0 suitable for use with XML Signature 2.0.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-xmldsig-xpath-20100831</howpublished>
		<title type="sharef:primaryTitle">XML Signature Streaming Profile of XPath 1.0</title>
		<field type="bibtex:topic">xmldsig[0.9] xpath1[0.8]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2010/WD-xmldsig-xpath-20100831</identifier>
	</reference>
	<reference name="xmldsigbestpractices" src="bibtex:misc" src-info="bibtex:line-32759" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Frederick</givenname>
				<surname>Hirsch</surname>
			</person>
			<person>
				<givenname>Pratik</givenname>
				<surname>Datta</surname>
			</person>
		</names>
		<date value="2010-08"/>
		<abstract>
			<richtext>
				<p>This document collects best practices for implementors and users of the XML Signature specification. Most of these best practices are related to improving security and mitigating attacks, yet others are for best practices in the practical use of XML Signature, such as signing XML that doesn't use namespaces, for example.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-xmldsig-bestpractices-20100831</howpublished>
		<title type="sharef:primaryTitle">XML Signature Best Practices</title>
		<field type="bibtex:topic">xmldsig[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2010/WD-xmldsig-bestpractices-20100831</identifier>
	</reference>
	<reference name="xmldsigcore2nd" src="bibtex:misc" src-info="bibtex:line-32770" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Mark</givenname>
				<surname>Bartel</surname>
			</person>
			<person>
				<givenname>John</givenname>
				<surname>Boyer</surname>
			</person>
			<person>
				<givenname>Barb</givenname>
				<surname>Fox</surname>
			</person>
			<person>
				<givenname>Brian</givenname>
				<surname>LaMacchia</surname>
			</person>
			<person>
				<givenname>Ed</givenname>
				<surname>Simon</surname>
			</person>
		</names>
		<names type="sharef:editor">
			<person>
				<givenname>Donald</givenname>
				<surname>Eastlake</surname>
			</person>
			<person>
				<givenname>Joseph</givenname>
				<surname>Reagle</surname>
			</person>
			<person>
				<givenname>David</givenname>
				<surname>Solo</surname>
			</person>
			<person>
				<givenname>Frederick</givenname>
				<surname>Hirsch</surname>
			</person>
			<person>
				<givenname>Thomas</givenname>
				<surname>Roessler</surname>
			</person>
		</names>
		<date value="2008-06"/>
		<abstract>
			<richtext>
				<p>This document specifies XML digital signature processing rules and syntax. XML Signatures provide integrity, message authentication, and/or signer authentication services for data of any type, whether located within the XML that includes the signature or elsewhere.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Recommendation REC-xmldsig-core-20080610</howpublished>
		<title type="sharef:primaryTitle">XML Signature Syntax and Processing (Second Edition)</title>
		<field type="bibtex:topic">xmldsig[1]</field>
		<field type="bibtex:updates">xmlsigsp</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2008/REC-xmldsig-core-20080610</identifier>
	</reference>
	<reference name="xmldsig2edtests" src="bibtex:misc" src-info="bibtex:line-32783" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Juan Carlos</givenname>
				<surname>Cruellas</surname>
			</person>
			<person>
				<givenname>Konrad</givenname>
				<surname>Lanz</surname>
			</person>
			<person>
				<givenname>Sean</givenname>
				<surname>Mullan</surname>
			</person>
		</names>
		<date value="2008-06"/>
		<abstract>
			<richtext>
				<p>This document defines interoperability test cases for Canonical XML 1.1 and XML Signature Syntax and Processing, Second Edition. The changes tested include C14N11 handling of attributes in the XML namespace, including xml:id and xml:base, appropriate C14N11 nodeset to octet stream transform processing, modifications to RFC 3986 dot segment processing for C14N11, and RFC 4514 string encoding of Distinguished Names. The tests include standalone C14N11 tests as well as tests integrated with XML signature generation and validation. This document also includes earlier test cases used in XML Signature for regression testing.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Note NOTE-xmldsig2ed-tests-20080610</howpublished>
		<title type="sharef:primaryTitle">Test Cases for C14N 1.1 and XMLDSig Interoperability</title>
		<field type="bibtex:topic">xmldsig[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2008/NOTE-xmldsig2ed-tests-20080610</identifier>
	</reference>
	<reference name="xmldsigcore1" src="bibtex:misc" src-info="bibtex:line-32794" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Donald E.</givenname>
				<surname>Eastlake</surname>
			</person>
			<person>
				<givenname>Joseph M.</givenname>
				<surname>Reagle</surname>
			</person>
			<person>
				<givenname>David</givenname>
				<surname>Solo</surname>
			</person>
			<person>
				<givenname>Frederick</givenname>
				<surname>Hirsch</surname>
			</person>
			<person>
				<givenname>Magnus</givenname>
				<surname>Nyström</surname>
			</person>
			<person>
				<givenname>Thomas</givenname>
				<surname>Roessler</surname>
			</person>
			<person>
				<givenname>Kelvin</givenname>
				<surname>Yiu</surname>
			</person>
		</names>
		<date value="2011-03"/>
		<abstract>
			<richtext>
				<p>This document specifies XML digital signature processing rules and syntax. XML Signatures provide integrity, message authentication, and/or signer authentication services for data of any type, whether located within the XML that includes the signature or elsewhere.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Candidate Recommendation CR-xmldsig-core1-20110303</howpublished>
		<title type="sharef:primaryTitle">XML Signature Syntax and Processing Version 1.1</title>
		<field type="bibtex:topic">xmldsig[1]</field>
		<field type="bibtex:updates">xmldsigcore2nd</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2011/CR-xmldsig-core1-20110303</identifier>
	</reference>
	<reference name="xmldsigproperties" src="bibtex:misc" src-info="bibtex:line-32806" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Frederick</givenname>
				<surname>Hirsch</surname>
			</person>
		</names>
		<date value="2011-03"/>
		<abstract>
			<richtext>
				<p>This document outlines proposed standard XML Signature Properties syntax and processing rules and an associated namespace for these properties. The intent is these can be composed with any version of XML Signature using the XML SignatureProperties element. These properties are intended to meet code signing requirements.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Candidate Recommendation CR-xmldsig-properties-20110303</howpublished>
		<title type="sharef:primaryTitle">XML Signature Properties</title>
		<field type="bibtex:topic">xmldsig[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2011/CR-xmldsig-properties-20110303</identifier>
	</reference>
	<reference name="xmldsigsimplify" src="bibtex:misc" src-info="bibtex:line-32817" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Frederick</givenname>
				<surname>Hirsch</surname>
			</person>
			<person>
				<givenname>Pratik</givenname>
				<surname>Datta</surname>
			</person>
		</names>
		<date value="2010-02"/>
		<abstract>
			<richtext>
				<p>This document outlines a proposed simplification of the XML Signature Transform mechanism, intended to enhance security, performance, streamability and to ease adoption.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Note NOTE-xmldsig-simplify-20100204</howpublished>
		<title type="sharef:primaryTitle">XML Signature Transform Simplification: Requirements and Design</title>
		<field type="bibtex:topic">xmldsig[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2010/NOTE-xmldsig-simplify-20100204</identifier>
	</reference>
	<reference name="dsigusage" src="bibtex:misc" src-info="bibtex:line-32828" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Thomas</givenname>
				<surname>Roessler</surname>
			</person>
		</names>
		<date value="2006-12"/>
		<abstract>
			<richtext>
				<p>This technical note describes how to use the XML Digital Signature Recommendation in a way consistent with the present (fall 2006) XML environment. In particular, this note takes into account the recent xml:id Version 1.0 and Canonical XML Version 1.1 Recommendations. This note suggests constraints on the use of XML Signature, and relies on extension points present in the XML Digital Signature Recommendation. This note does not override any aspect of that Recommendation.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Note NOTE-DSig-usage-20061220</howpublished>
		<title type="sharef:primaryTitle">Using XML Digital Signatures in the 2006 XML Environment</title>
		<field type="bibtex:topic">xmldsig[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2006/NOTE-DSig-usage-20061220</identifier>
	</reference>
	<reference name="xmldsigfilter" src="bibtex:misc" src-info="bibtex:line-32839" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>John M.</givenname>
				<surname>Boyer</surname>
			</person>
			<person>
				<givenname>Merlin</givenname>
				<surname>Hughes</surname>
			</person>
			<person>
				<givenname>Joseph M.</givenname>
				<surname>Reagle</surname>
			</person>
		</names>
		<date value="2002-11"/>
		<abstract>
			<richtext>
				<p>XML Signature recommends a standard means for specifying information content to be digitally signed and for representing the resulting digital signatures in XML. Some applications require the ability to specify a subset of a given XML document as the information content to be signed. The XML Signature specification meets this requirement with the XPath transform. However, this transform can be difficult to implement efficiently with existing technologies. This specification defines a new XML Signature transform to facilitate the development of efficient document subsetting implementations that interoperate under similar performance profiles.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Recommendation REC-xmldsig-filter2-20021108</howpublished>
		<title type="sharef:primaryTitle">XML-Signature XPath Filter 2.0</title>
		<field type="bibtex:topic">xmldsig[1] xpath1[0.7]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2002/REC-xmldsig-filter2-20021108</identifier>
	</reference>
	<reference name="xmlsig" src="bibtex:misc" src-info="bibtex:line-32850" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Joseph M.</givenname>
				<surname>Reagle</surname>
			</person>
		</names>
		<date value="1999-06"/>
		<howpublished>World Wide Web Consortium, Draft Note xml-dsig-requirements-990601</howpublished>
		<title type="sharef:primaryTitle">XML-Signature Requirements</title>
		<field type="bibtex:topic">xmldsig[0.9]</field>
	</reference>
	<reference name="xmlenc" src="bibtex:misc" src-info="bibtex:line-32859" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Joseph M.</givenname>
				<surname>Reagle</surname>
			</person>
		</names>
		<date value="2001-10"/>
		<howpublished>World Wide Web Consortium, Working Draft WD-xml-encryption-req-20011018</howpublished>
		<title type="sharef:primaryTitle">XML Encryption Requirements</title>
		<field type="bibtex:topic">xmlenc[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2001/WD-xml-encryption-req-20011018</identifier>
	</reference>
	<reference name="xmlencsynproc" src="bibtex:misc" src-info="bibtex:line-32869" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Donald E.</givenname>
				<surname>Eastlake</surname>
			</person>
			<person>
				<givenname>Joseph M.</givenname>
				<surname>Reagle</surname>
			</person>
			<person>
				<givenname>Takeshi</givenname>
				<surname>Imamura</surname>
			</person>
			<person>
				<givenname>Blair</givenname>
				<surname>Dillaway</surname>
			</person>
			<person>
				<givenname>Ed</givenname>
				<surname>Simon</surname>
			</person>
		</names>
		<date value="2002-12"/>
		<abstract>
			<richtext>
				<p>This document specifies a process for encrypting data and representing the result in XML. The data may be arbitrary data (including an XML document), an XML element, or XML element content. The result of encrypting data is an XML Encryption element which contains or references the cipher data.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Recommendation REC-xmlenc-core-20021210</howpublished>
		<title type="sharef:primaryTitle">XML Encryption Syntax and Processing</title>
		<field type="bibtex:topic">xmlenc[1]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2002/REC-xmlenc-core-20021210</identifier>
	</reference>
	<reference name="xmlenccore1" src="bibtex:misc" src-info="bibtex:line-32880" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Takeshi</givenname>
				<surname>Imamura</surname>
			</person>
			<person>
				<givenname>Blair</givenname>
				<surname>Dillaway</surname>
			</person>
			<person>
				<givenname>Ed</givenname>
				<surname>Simon</surname>
			</person>
			<person>
				<givenname>Kelvin</givenname>
				<surname>Yiu</surname>
			</person>
			<person>
				<givenname>Magnus</givenname>
				<surname>Nyström</surname>
			</person>
		</names>
		<names type="sharef:editor">
			<person>
				<givenname>Donald E.</givenname>
				<surname>Eastlake</surname>
			</person>
			<person>
				<givenname>Joseph M.</givenname>
				<surname>Reagle</surname>
			</person>
			<person>
				<givenname>Frederick</givenname>
				<surname>Hirsch</surname>
			</person>
			<person>
				<givenname>Thomas</givenname>
				<surname>Roessler</surname>
			</person>
		</names>
		<date value="2011-03"/>
		<abstract>
			<richtext>
				<p>This document specifies a process for encrypting data and representing the result in XML. The data may be in a variety of formats, including octet streams and other unstructured data, or structured data formats such as XML documents, an XML element, or XML element content. The result of encrypting data is an XML Encryption element that contains or references the cipher data.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Candidate Recommendation CR-xmlenc-core1-20110303</howpublished>
		<title type="sharef:primaryTitle">XML Encryption Syntax and Processing Version 1.1</title>
		<field type="bibtex:topic">xmlenc[1]</field>
		<field type="bibtex:updates">xmlencsynproc xmlsecderivedkeys</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2011/CR-xmlenc-core1-20110303</identifier>
	</reference>
	<reference name="xmlsecderivedkeys" src="bibtex:misc" src-info="bibtex:line-32893" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Magnus</givenname>
				<surname>Nyström</surname>
			</person>
		</names>
		<date value="2009-07"/>
		<abstract>
			<richtext>
				<p>Key derivation is a well-established mechanism for generating new cryptographic keys material from some existing, original ("master") key material and potentially other information. This document augments XML Signature and XML Encryption by defining XML types and elements necessary to enable use of derived keys in XML security applications.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Note NOTE-xmlsec-derivedkeys-20090730</howpublished>
		<title type="sharef:primaryTitle">XML Security Derived Keys</title>
		<field type="bibtex:topic">xmlenc[0.9] xmldsig[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2009/NOTE-xmlsec-derivedkeys-20090730</identifier>
	</reference>
	<reference name="xmlsecrngschema" src="bibtex:misc" src-info="bibtex:line-32904" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Makoto</givenname>
				<surname>Murata</surname>
			</person>
			<person>
				<givenname>Frederick</givenname>
				<surname>Hirsch</surname>
			</person>
		</names>
		<date value="2011-03"/>
		<abstract>
			<richtext>
				<p>This document serves to publish RELAX NG schemas for XML Security specifications, including XML Signature 1.1, and XML Signature Properties.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-xmlsec-rngschema-20110303</howpublished>
		<title type="sharef:primaryTitle">XML Security RELAX NG Schemas</title>
		<field type="bibtex:topic">xmldsig[0.9] relaxng[0.8]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2011/WD-xmlsec-rngschema-20110303</identifier>
	</reference>
	<reference name="xmlsecalgorithms" src="bibtex:misc" src-info="bibtex:line-32915" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Frederick</givenname>
				<surname>Hirsch</surname>
			</person>
			<person>
				<givenname>Thomas</givenname>
				<surname>Roessler</surname>
			</person>
			<person>
				<givenname>Kelvin</givenname>
				<surname>Yiu</surname>
			</person>
		</names>
		<date value="2010-05"/>
		<abstract>
			<richtext>
				<p>This Note summarizes XML Security algorithm URI identifiers and the specifications associated with them.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-xmlsec-algorithms-20100513</howpublished>
		<title type="sharef:primaryTitle">XML Security Algorithm Cross-Reference</title>
		<field type="bibtex:topic">xmldsig[0.9] xmlenc[0.9] dsa[0.8] rsa[0.8] hmac[0.8] md5[0.8] sha[0.8] des[0.8]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2010/WD-xmlsec-algorithms-20100513</identifier>
	</reference>
	<reference name="xmlsecgenerichybrid" src="bibtex:misc" src-info="bibtex:line-32926" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Magnus</givenname>
				<surname>Nyström</surname>
			</person>
			<person>
				<givenname>Frederick</givenname>
				<surname>Hirsch</surname>
			</person>
		</names>
		<date value="2011-03"/>
		<abstract>
			<richtext>
				<p>Generic hybrid ciphers allow for a consistent treatment of asymmetric ciphers when encrypting data and consist of a key encapsulation algorithm with associated parameters and a data encapsulation algorithm with associated parameters. Further, the key encapsulation algorithms introduced in this specification have attractive security properties. This document augments XML Encryption Version 1.1 by defining algorithms, XML types and elements necessary to enable use of generic hybrid ciphers in XML Security applications.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Candidate Recommendation CR-xmlsec-generic-hybrid-20110303</howpublished>
		<title type="sharef:primaryTitle">XML Security Generic Hybrid Ciphers</title>
		<field type="bibtex:topic">xmldsig[0.9] xmlenc[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2011/CR-xmlsec-generic-hybrid-20110303</identifier>
	</reference>
	<reference name="xmldecrypt" src="bibtex:misc" src-info="bibtex:line-32937" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Merlin</givenname>
				<surname>Hughes</surname>
			</person>
			<person>
				<givenname>Takeshi</givenname>
				<surname>Imamura</surname>
			</person>
			<person>
				<givenname>Hiroshi</givenname>
				<surname>Maruyama</surname>
			</person>
		</names>
		<date value="2002-12"/>
		<abstract>
			<richtext>
				<p>This document specifies an XML Signature "decryption transform" that enables XML Signature applications to distinguish between those XML Encryption structures that were encrypted before signing (and must not be decrypted) and those that were encrypted after signing (and must be decrypted) for the signature to validate.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Recommendation REC-xmlenc-decrypt-20021210</howpublished>
		<title type="sharef:primaryTitle">Decryption Transform for XML Signature</title>
		<field type="bibtex:topic">xmldsig[0.8]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2002/REC-xmlenc-decrypt-20021210</identifier>
	</reference>
	<reference name="xmlsecreqs" src="bibtex:misc" src-info="bibtex:line-32948" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Frederick</givenname>
				<surname>Hirsch</surname>
			</person>
			<person>
				<givenname>Thomas</givenname>
				<surname>Roessler</surname>
			</person>
		</names>
		<date value="2011-03"/>
		<abstract>
			<richtext>
				<p>This Note summarizes scenarios, design decisions, and requirements for the XML Signature and Canonical XML specifications, to guide ongoing W3C work to revise these specifications.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-xmlsec-reqs-20110303</howpublished>
		<title type="sharef:primaryTitle">XML Security 1.1 Requirements and Design Considerations</title>
		<field type="bibtex:topic">xmldisg[0.8] xmlenc[0.8]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2011/WD-xmlsec-reqs-20110303</identifier>
	</reference>
	<reference name="xmlsecreqs2" src="bibtex:misc" src-info="bibtex:line-32959" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Frederick</givenname>
				<surname>Hirsch</surname>
			</person>
			<person>
				<givenname>Pratik</givenname>
				<surname>Datta</surname>
			</person>
		</names>
		<date value="2010-02"/>
		<abstract>
			<richtext>
				<p>This document outlines use cases, requirements and design choices for XML Security 2.0, specifically Canonical XML 2.0 and XML Signature 2.0. It includes a proposed simplification of the XML Signature Transform mechanism, intended to enhance security, performance, streamability and to ease adoption.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-xmlsec-reqs2-20100204</howpublished>
		<title type="sharef:primaryTitle">XML Security 2.0 Requirements and Design Considerations</title>
		<field type="bibtex:topic">xmldisg[0.8] xmlenc[0.8]</field>
		<field type="bibtex:updates">xmlsecreqs xmldsigsimplify</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2010/WD-xmlsec-reqs2-20100204</identifier>
	</reference>
	<reference name="xades" src="bibtex:misc" src-info="bibtex:line-32971" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Juan Carlos</givenname>
				<surname>Cruellas</surname>
			</person>
			<person>
				<givenname>Gregor</givenname>
				<surname>Karlinger</surname>
			</person>
			<person>
				<givenname>Denis</givenname>
				<surname>Pinkas</surname>
			</person>
			<person>
				<givenname>John</givenname>
				<surname>Ross</surname>
			</person>
		</names>
		<date value="2003-02"/>
		<abstract>
			<richtext>
				<p>This note (XAdES) extends the IETF/W3CXML-Signature Syntax and Processing specification into the domain of non-repudiation by defining XML formats for advanced electronic signatures that remain valid over long periods and are compliant with the European "Directive 1999/93/EC of the European Parliament and of the Council of 13 December 1999 on a Community framework for electronic signatures" (also denoted as "the Directive" or the "European Directive" in the rest of the present document) and incorporate additional useful information in common uses cases. This includes evidence as to its validity even if the signer or verifying party later attempts to deny (repudiates) the validity of the signature. An advanced electronic signature aligned with the present document can, in consequence, be used for arbitration in case of a dispute between the signer and verifier, which may occur at some later time, even years later.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Note NOTE-XAdES-20030220</howpublished>
		<title type="sharef:primaryTitle">XML Advanced Electronic Signatures (XAdES)</title>
		<field type="bibtex:topic">xades[1]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2003/NOTE-XAdES-20030220</identifier>
	</reference>
	<reference name="delang" src="bibtex:misc" src-info="bibtex:line-32982" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Eero</givenname>
				<surname>Lempinen</surname>
			</person>
			<person>
				<givenname>Harri</givenname>
				<surname>Saarikoski</surname>
			</person>
		</names>
		<date value="2001-10"/>
		<abstract>
			<richtext>
				<p>This document outlines the Data Extraction Language. DEL is an XML format for describing data conversion processes from other data formats to XML. A DEL script specifies how to locate and extract fragments from input data and where to insert them in the resulting XML format. The DEL processor executing the DEL script can use the extracted data to either create a new XML document or modify an existing XML document by creating new elements and attributes at locations specified with XPath expressions.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Note NOTE-data-extraction-20011031</howpublished>
		<title type="sharef:primaryTitle">DEL — Data Extraction Language</title>
		<field type="bibtex:topic">del[1]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2001/NOTE-data-extraction-20011031</identifier>
	</reference>
	<reference name="picslabel" src="bibtex:misc" src-info="bibtex:line-32993" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Tim</givenname>
				<surname>Krauskopf</surname>
			</person>
			<person>
				<givenname>Jim</givenname>
				<surname>Miller</surname>
			</person>
			<person>
				<givenname>Paul</givenname>
				<surname>Resnick</surname>
			</person>
			<person>
				<givenname>Win</givenname>
				<surname>Treese</surname>
			</person>
		</names>
		<date value="1996-10"/>
		<abstract>
			<richtext>
				<p>This document has been prepared for the technical subcommittee of PICS (Platform for Internet Content Selection). It defines a general format for labels and three methods by which these labels may be transmitted: (1) In an HTML document. (2) With a document transported via a protocol that uses RFC 822 headers. (3) Separately from the document.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Recommendation REC-PICS-labels-961031</howpublished>
		<title type="sharef:primaryTitle">PICS Label Distribution — Label Syntax and Communication Protocols</title>
		<field type="bibtex:topic">pics[1]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/REC-PICS-labels-961031</identifier>
	</reference>
	<reference name="picsservices" src="bibtex:misc" src-info="bibtex:line-33004" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Jim</givenname>
				<surname>Miller</surname>
			</person>
			<person>
				<givenname>Paul</givenname>
				<surname>Resnick</surname>
			</person>
			<person>
				<givenname>David</givenname>
				<surname>Singer</surname>
			</person>
		</names>
		<date value="1996-10"/>
		<abstract>
			<richtext>
				<p>This document, which has been prepared for the technical subcommittee of PICS (Platform for Internet Content Selection), defines a language for describing rating services. Software programs will read service descriptions written in this language, in order to interpret content labels and assist end-users in configuring selection software.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Recommendation REC-PICS-services-961031</howpublished>
		<title type="sharef:primaryTitle">Rating Services and Rating Systems (and their Machine Readable Descriptions)</title>
		<field type="bibtex:topic">pics[1]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/REC-PICS-services-961031</identifier>
	</reference>
	<reference name="picsrules" src="bibtex:misc" src-info="bibtex:line-33015" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Martin</givenname>
				<surname>Presler-Marshall</surname>
			</person>
			<person>
				<givenname>Christopher</givenname>
				<surname>Evans</surname>
			</person>
			<person>
				<givenname>Clive D.W.</givenname>
				<surname>Feather</surname>
			</person>
			<person>
				<givenname>Alex</givenname>
				<surname>Hopmann</surname>
			</person>
			<person>
				<givenname>Martin</givenname>
				<surname>Presler-Marshall</surname>
			</person>
			<person>
				<givenname>Paul</givenname>
				<surname>Resnick</surname>
			</person>
		</names>
		<date value="1997-12"/>
		<abstract>
			<richtext>
				<p>This document defines a language for writing profiles, which are filtering rules that allow or block access to URLs based on PICS labels that describe those URLs. This language is intended as a transmission format; individual implementations must be able to read and write their specifications in this language, but need not use this format internally.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Recommendation REC-PICSRules-971229</howpublished>
		<title type="sharef:primaryTitle">PICSRules 1.1</title>
		<field type="bibtex:topic">pics[1]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/REC-PICSRules-971229</identifier>
	</reference>
	<reference name="waipa" src="bibtex:misc" src-info="bibtex:line-33026" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Gregg</givenname>
				<surname>Vanderheiden</surname>
			</person>
			<person>
				<givenname>Wendy</givenname>
				<surname>Chisholm</surname>
			</person>
			<person>
				<givenname>Ian</givenname>
				<surname>Jacobs</surname>
			</person>
		</names>
		<date value="1998-02"/>
		<abstract>
			<richtext>
				<p>This document is a list of markup guidelines that HTML authors should follow in order to make their pages more accessible. Following the list of guidelines is a checklist that authors and Web masters should use to verify page accessibility. Tools that generate documents in HTML (authoring tools, file conversion packages or other products) should produce documents that follow these guidelines. This document is part of a series of accessibility documents published by the Web Accessibility Initiative.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-WAI-PAGEAUTH-0203</howpublished>
		<title type="sharef:primaryTitle">WAI Accessibility Guidelines: Page Authoring</title>
		<field type="bibtex:topic">wai[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/1998/WD-WAI-PAGEAUTH-0203</identifier>
	</reference>
	<reference name="waiageliterature" src="bibtex:misc" src-info="bibtex:line-33037" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Andrew</givenname>
				<surname>Arch</surname>
			</person>
		</names>
		<date value="2008-05"/>
		<abstract>
			<richtext>
				<p>This document provides a review and analysis of guidelines and articles relating to the needs of older people with Web accessibility needs due to ageing, and compares these with the needs of people with disabilities as already addressed in WAI guidelines. The focus is particularly on Europe but applies internationally as well. This review is being undertaken in order to inform the development of educational materials which can better promote the needs of people who have accessibility needs due to ageing, and potential development of profiles and/or extensions on WAI guidelines.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-wai-age-literature-20080514</howpublished>
		<title type="sharef:primaryTitle">Web Accessibility for Older Users: A Literature Review</title>
		<field type="bibtex:topic">wai[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2008/WD-wai-age-literature-20080514</identifier>
	</reference>
	<reference name="waica" src="bibtex:misc" src-info="bibtex:line-33048" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Wendy</givenname>
				<surname>Chisholm</surname>
			</person>
			<person>
				<givenname>Gregg</givenname>
				<surname>Vanderheiden</surname>
			</person>
			<person>
				<givenname>Ian</givenname>
				<surname>Jacobs</surname>
			</person>
		</names>
		<date value="1999-05"/>
		<howpublished>World Wide Web Consortium, Recommendation WAI-WEBCONTENT-19990505</howpublished>
		<title type="sharef:primaryTitle">Web Content Accessibility Guidelines 1.0</title>
		<field type="bibtex:topic">wai[0.9] wcag[1]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/1999/WAI-WEBCONTENT-19990505</identifier>
	</reference>
	<reference name="wcag20" src="bibtex:misc" src-info="bibtex:line-33058" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Ben</givenname>
				<surname>Caldwell</surname>
			</person>
			<person>
				<givenname>Michael</givenname>
				<surname>Cooper</surname>
			</person>
			<person>
				<givenname>Loretta Guarino</givenname>
				<surname>Reid</surname>
			</person>
			<person>
				<givenname>Gregg</givenname>
				<surname>Vanderheiden</surname>
			</person>
		</names>
		<date value="2008-12"/>
		<abstract>
			<richtext>
				<p>Web Content Accessibility Guidelines (WCAG) 2.0 covers a wide range of recommendations for making Web content more accessible. Following these guidelines will make content accessible to a wider range of people with disabilities, including blindness and low vision, deafness and hearing loss, learning disabilities, cognitive limitations, limited movement, speech disabilities, photosensitivity and combinations of these. Following these guidelines will also often make your Web content more usable to users in general. WCAG 2.0 success criteria are written as testable statements that are not technology-specific. Guidance about satisfying the success criteria in specific technologies, as well as general information about interpreting the success criteria, is provided in separate documents. See Web Content Accessibility Guidelines (WCAG) Overview for an introduction and links to WCAG technical and educational material. WCAG 2.0 succeeds Web Content Accessibility Guidelines 1.0, which was published as a W3C Recommendation May 1999. Although it is possible to conform either to WCAG 1.0 or to WCAG 2.0 (or both), the W3C recommends that new and updated content use WCAG 2.0. The W3C also recommends that Web accessibility policies reference WCAG 2.0.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Recommendation REC-WCAG20-20081211</howpublished>
		<title type="sharef:primaryTitle">Web Content Accessibility Guidelines 2.0</title>
		<field type="bibtex:topic">wai[0.9] wcag[1]</field>
		<field type="bibtex:updates">waica</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2008/REC-WCAG20-20081211</identifier>
	</reference>
	<reference name="understandingwcag20" src="bibtex:misc" src-info="bibtex:line-33070" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Michael</givenname>
				<surname>Cooper</surname>
			</person>
			<person>
				<givenname>Loretta Guarino</givenname>
				<surname>Reid</surname>
			</person>
			<person>
				<givenname>Gregg</givenname>
				<surname>Vanderheiden</surname>
			</person>
			<person>
				<givenname>Ben</givenname>
				<surname>Caldwell</surname>
			</person>
		</names>
		<date value="2010-10"/>
		<abstract>
			<richtext>
				<p>This document, "Understanding WCAG 2.0," is an essential guide to understanding and using Web Content Accessibility Guidelines (WCAG) 2.0. It is part of a series of documents that support WCAG 2.0. Please note that the contents of this document are informative (they provide guidance), and not normative (they do not set requirements for conforming to WCAG 2.0). See Web Content Accessibility Guidelines (WCAG) Overview for an introduction to WCAG, supporting technical documents, and educational material. WCAG 2.0 establishes a set of Success Criteria to define conformance to the WCAG 2.0 Guidelines. A Success Criterion is a testable statement that will be either true or false when applied to specific Web content. "Understanding WCAG 2.0" provides detailed information about each Success Criterion, including its intent, the key terms that are used in the Success Criterion, and how the Success Criteria in WCAG 2.0 help people with different types of disabilities. This document also provides examples of Web content that meet the success criterion using various Web technologies (for instance, HTML, CSS, XML), and common examples of Web content that does not meet the success criterion. This document indicates specific techniques to meet each Success Criterion. Details for how to implement each technique are available in "Techniques for WCAG 2.0", but "Understanding WCAG 2.0" provides the information about the relationship of each technique to the Success Criteria. Techniques are categorized by the level of support they provide for the Success Criteria. "Sufficient techniques" are sufficient to meet a particular Success Criterion (either by themselves or in combination with other techniques), while other techniques are advisory and therefore optional. None of the techniques are required to meet WCAG 2.0, although some may be the only known method if a particular technology is used. "Advisory techniques" are not sufficient to meet the Success Criteria on their own (because they are not testable or provide incomplete support) but it is encouraged that authors follow them when possible to provide enhanced accessibility. Another support category is "Common Failures", which describe authoring practices known to cause Web content not to conform to WCAG 2.0. Although failures provide advisory information about certain authoring practices, authors must avoid those practices in order to meet the WCAG 2.0 Success Criteria. This document is part of a series of documents published by the W3C Web Accessibility Initiative (WAI) to support WCAG 2.0. This document was published as a Working Group Note at the same time WCAG 2.0 was published as a W3C Recommendation. Unlike WCAG 2.0, is expected that the information in Understanding WCAG 2.0 will be updated from time to time. See Web Content Accessibility Guidelines (WCAG) Overview for an introduction to WCAG, supporting technical documents, and educational material.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Note NOTE-UNDERSTANDING-WCAG20-20101014</howpublished>
		<title type="sharef:primaryTitle">Understanding WCAG 2.0</title>
		<field type="bibtex:topic">wcag[0.8]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2010/NOTE-UNDERSTANDING-WCAG20-20101014</identifier>
	</reference>
	<reference name="wcag20techs" src="bibtex:misc" src-info="bibtex:line-33081" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Michael</givenname>
				<surname>Cooper</surname>
			</person>
			<person>
				<givenname>Loretta Guarino</givenname>
				<surname>Reid</surname>
			</person>
			<person>
				<givenname>Gregg</givenname>
				<surname>Vanderheiden</surname>
			</person>
			<person>
				<givenname>Ben</givenname>
				<surname>Caldwell</surname>
			</person>
		</names>
		<date value="2010-10"/>
		<abstract>
			<richtext>
				<p>"Techniques for WCAG 2.0" provides information to Web content developers who wish to satisfy the success criteria of Web Content Accessibility Guidelines (WCAG) 2.0. Techniques are specific authoring practices that may be used in support of the WCAG 2.0 success criteria. This document provides "General Techniques" that describe basic practices that are applicable to any technology, and technology-specific techniques that provide information applicable to specific technologies. Use of the techniques provided in this document makes it easier for Web content to demonstrate conformance to WCAG 2.0 success criteria than if these techniques are not used. Besides the techniques provided in this document, there may be other techniques that can be used to implement conformance to WCAG 2.0. The WCAG WG encourages submission of such techniques so they can be considered for inclusion in this document, in order to make the set of techniques maintained by the WCAG WG as comprehensive as possible. Please submit techniques for consideration using the "Techniques Submission Form." This document is part of a series of documents published by the W3C Web Accessibility Initiative (WAI) to support WCAG 2.0. This document was published as a Working Group Note at the same time WCAG 2.0 was published as a W3C Recommendation. Unlike WCAG 2.0, it is expected that the information in Understanding WCAG 2.0 will be updated from time to time. See Web Content Accessibility Guidelines (WCAG) Overview for an introduction to WCAG, supporting technical documents, and educational material.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Note NOTE-WCAG20-TECHS-20101014</howpublished>
		<title type="sharef:primaryTitle">Techniques for WCAG 2.0</title>
		<field type="bibtex:topic">wai[0.9] wcag[1]</field>
		<field type="bibtex:updates">wcag20techreq</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2010/NOTE-WCAG20-TECHS-20101014</identifier>
	</reference>
	<reference name="wcag20checklist" src="bibtex:misc" src-info="bibtex:line-33093" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Ben</givenname>
				<surname>Caldwell</surname>
			</person>
		</names>
		<date value="2005-06"/>
		<abstract>
			<richtext>
				<p>The Web Content Accessibility Guidelines 2.0 Checklist serves as an appendix to Web Content Accessibility Guidelines 2.0. It lists all of the success criteria from WCAG 2.0 in a checkable list. The level of each success criterion is provided as well as a link to WCAG 2.0 for more information for each success criterion. For many readers, the Checklist provides a quick reference and overview to the information in WCAG 2.0.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-WCAG20-20050630/checklist</howpublished>
		<title type="sharef:primaryTitle">Web Content Accessibility Guidelines 2.0 Checklist</title>
		<field type="bibtex:topic">wai[0.9] wcag[1]</field>
		<field type="bibtex:updates">wcag20techreq</field>
		<identifier type="sharef:uri" resourceType="text/html">http://www.w3.org/TR/2005/WD-WCAG20-20050630/checklist.html</identifier>
	</reference>
	<reference name="wcag20req" src="bibtex:misc" src-info="bibtex:line-33105" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Gregg</givenname>
				<surname>Vanderheiden</surname>
			</person>
			<person>
				<givenname>John</givenname>
				<surname>Slatin</surname>
			</person>
			<person>
				<givenname>Wendy</givenname>
				<surname>Chisholm</surname>
			</person>
		</names>
		<date value="2006-04"/>
		<abstract>
			<richtext>
				<p>This document outlines the requirements that the Web Content Accessibility Guidelines Working Group (WCAG WG) has set for development of Web Content Accessibility Guidelines 2.0. These requirements are based on feedback from the use of WCAG 1.0 and will be used to determine if the WCAG WG has met its goals as WCAG 2.0 advances through the W3C Recommendation Track Process.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Note wcag2-req-20060425</howpublished>
		<title type="sharef:primaryTitle">Requirements for WCAG 2.0</title>
		<field type="bibtex:topic">wai[0.9] wcag[1]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2006/NOTE-wcag2-req-20060425</identifier>
	</reference>
	<reference name="wcag20techreq" src="bibtex:misc" src-info="bibtex:line-33116" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Michael</givenname>
				<surname>Cooper</surname>
			</person>
		</names>
		<date value="2003-02"/>
		<howpublished>World Wide Web Consortium, Workig Draft WD-wcag2-tech-req-20030207</howpublished>
		<title type="sharef:primaryTitle">Requirements for WCAG 2.0 Checklists and Techniques</title>
		<field type="bibtex:topic">wai[0.9] wcag[1]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2003/WD-wcag2-tech-req-20030207</identifier>
	</reference>
	<reference name="waitca" src="bibtex:misc" src-info="bibtex:line-33126" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Wendy</givenname>
				<surname>Chisholm</surname>
			</person>
			<person>
				<givenname>Gregg</givenname>
				<surname>Vanderheiden</surname>
			</person>
			<person>
				<givenname>Ian</givenname>
				<surname>Jacobs</surname>
			</person>
		</names>
		<date value="1999-05"/>
		<howpublished>World Wide Web Consortium, Note WAI-WEBCONTENT-TECHS-19990505</howpublished>
		<title type="sharef:primaryTitle">Techniques for Web Content Accessibility Guidelines 1.0</title>
		<field type="bibtex:topic">wai[0.9] wcag[1]</field>
	</reference>
	<reference name="wcag10css" src="bibtex:misc" src-info="bibtex:line-33135" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Wendy</givenname>
				<surname>Chisholm</surname>
			</person>
			<person>
				<givenname>Gregg</givenname>
				<surname>Vanderheiden</surname>
			</person>
			<person>
				<givenname>Ian</givenname>
				<surname>Jacobs</surname>
			</person>
		</names>
		<date value="2000-11"/>
		<howpublished>World Wide Web Consortium, Note NOTE-WCAG10-CSS-TECHS-20001106</howpublished>
		<title type="sharef:primaryTitle">CSS Techniques for Web Content Accessibility Guidelines 1.0</title>
		<field type="bibtex:topic">wai[0.9] wcag[1] css[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2000/NOTE-WCAG10-CSS-TECHS-20001106</identifier>
	</reference>
	<reference name="wcag10html" src="bibtex:misc" src-info="bibtex:line-33145" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Wendy</givenname>
				<surname>Chisholm</surname>
			</person>
			<person>
				<givenname>Gregg</givenname>
				<surname>Vanderheiden</surname>
			</person>
			<person>
				<givenname>Ian</givenname>
				<surname>Jacobs</surname>
			</person>
		</names>
		<date value="2000-11"/>
		<howpublished>World Wide Web Consortium, Note NOTE-WCAG10-HTML-TECHS-20001106</howpublished>
		<title type="sharef:primaryTitle">HTML Techniques for Web Content Accessibility Guidelines 1.0</title>
		<field type="bibtex:topic">wai[0.9] wcag[1] html[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2000/NOTE-WCAG10-HTML-TECHS-20001106</identifier>
	</reference>
	<reference name="wcag20html" src="bibtex:misc" src-info="bibtex:line-33155" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Michael</givenname>
				<surname>Cooper</surname>
			</person>
		</names>
		<date value="2005-11"/>
		<abstract>
			<richtext>
				<p>This document provides information to Web content developers who wish to satisfy the success criteria of "Web Content Accessibility Guidelines 2.0" (currently a W3C Working Draft). The techniques in this document are specific to Hypertext Markup Language content (HTML/XHTML) although some techniques contain Cascading Style Sheet (CSS) and ECMAScript solutions. Use of the illustrative techniques provided in this document may make it more likely for Web content to demonstrate conformance to WCAG 2.0 success criteria (by passing the relevant tests in the WCAG 2.0 test suite — to be developed) than if these illustrative techniques are not used. There may be other techniques besides those provided in this document that may be used to demonstrate conformance to WCAG 2.0; in that case, it is encouraged to submit those techniques to the WCAG WG for consideration for inclusion in this document, so that the set of techniques maintained by the WCAG WG is as comprehensive as possible. Deprecated examples illustrate techniques that the Working Group no longer recommends, but may be applicable in some cases.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-WCAG20-HTML-TECHS-20051123</howpublished>
		<title type="sharef:primaryTitle">HTML Techniques for WCAG 2.0</title>
		<field type="bibtex:topic">wai[0.9] wcag[1] html[0.9]</field>
		<field type="bibtex:updates">wcag10html</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2005/WD-WCAG20-HTML-TECHS-20051123</identifier>
	</reference>
	<reference name="wcag20css" src="bibtex:misc" src-info="bibtex:line-33167" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Wendy</givenname>
				<surname>Chisholm</surname>
			</person>
			<person>
				<givenname>Becky</givenname>
				<surname>Gibson</surname>
			</person>
		</names>
		<date value="2005-06"/>
		<abstract>
			<richtext>
				<p>This document provides information to Web content developers who wish to satisfy the success criteria of "Web Content Accessibility Guidelines 2.0" (currently a W3C Working Draft). The techniques in this document are specific to Cascading Style Sheet content, although some techniques contain Hypertext Markup Language content and ECMAScript solutions. Use of the illustrative techniques provided in this document may make it more likely for Web content to demonstrate conformance to WCAG 2.0 success criteria (by passing the relevant tests in the WCAG 2.0 test suite — to be developed) than if these illustrative techniques are not used. There may be other techniques besides those provided in this document that may be used to demonstrate conformance to WCAG 2.0; in that case, it is encouraged to submit those techniques to the WCAG WG for consideration for inclusion in this document, so that the set of techniques maintained by the WCAG WG is as comprehensive as possible. Deprecated examples illustrate techniques that the Working Group no longer recommends, but may be applicable in some cases. This document is part of a series of documents published by the W3C Web Accessibility Initiative (WAI) to support WCAG 2.0.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-WCAG20-CSS-TECHS-20050630</howpublished>
		<title type="sharef:primaryTitle">CSS Techniques for WCAG 2.0</title>
		<field type="bibtex:topic">wai[0.9] wcag[1] css[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2005/WD-WCAG20-CSS-TECHS-20050630</identifier>
	</reference>
	<reference name="wcag20script" src="bibtex:misc" src-info="bibtex:line-33178" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Matt</givenname>
				<surname>May</surname>
			</person>
			<person>
				<givenname>Becky</givenname>
				<surname>Gibson</surname>
			</person>
		</names>
		<date value="2005-06"/>
		<abstract>
			<richtext>
				<p>This document provides information to Web content developers who wish to satisfy the success criteria of "Web Content Accessibility Guidelines 2.0" (currently a W3C Working Draft). The techniques in this document are specific to ECMAScript although some techniques contain Cascading Style Sheet and Hypertext Markup Language content solutions. Use of the illustrative techniques provided in this document may make it more likely for Web content to demonstrate conformance to WCAG 2.0 success criteria (by passing the relevant tests in the WCAG 2.0 test suite — to be developed) than if these illustrative techniques are not used. There may be other techniques besides those provided in this document that may be used to demonstrate conformance to WCAG 2.0; in that case, it is encouraged to submit those techniques to the WCAG WG for consideration for inclusion in this document, so that the set of techniques maintained by the WCAG WG is as comprehensive as possible. Deprecated examples illustrate techniques that the Working Group no longer recommends, but may be applicable in some cases. Some techniques may have errors that we have been unable to correct since the 19 November 2004 Working Draft since the WCAG WG has been focusing on guidelines and success criterion for this set of Working Drafts. This document is part of a series of documents published by the W3C Web Accessibility Initiative (WAI) to support WCAG 2.0.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-WCAG20-SCRIPT-TECHS-20050630</howpublished>
		<title type="sharef:primaryTitle">Client-side Scripting Techniques for WCAG 2.0</title>
		<field type="bibtex:topic">wai[0.9] wcag[1] ecmascript[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2005/WD-WCAG20-SCRIPT-TECHS-20050630</identifier>
	</reference>
	<reference name="wcag20gateway" src="bibtex:misc" src-info="bibtex:line-33189" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Tom</givenname>
				<surname>Croucher</surname>
			</person>
			<person>
				<givenname>John</givenname>
				<surname>Slatin</surname>
			</person>
		</names>
		<date value="2004-07"/>
		<abstract>
			<richtext>
				<p>This document is intended to help authors of Web content who wish to claim conformance to "Web Content Accessibility Guidelines 2.0". The techniques in this document are neither guarantees of conformance nor the only way an author might produce conforming content. This document has two purposes: (1) It provides examples and general guidance to meet the success criteria in WCAG 2.0. (2) It is also a gateway to technology-specific documents that provide examples and guidance specific to CSS and HTML for meeting the success criteria in WCAG 2.0.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-WCAG20-GATEWAY-20040730</howpublished>
		<title type="sharef:primaryTitle">Gateway to Techniques for WCAG 2.0</title>
		<field type="bibtex:topic">wai[0.9] wcag[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2004/WD-WCAG20-GATEWAY-20040730</identifier>
	</reference>
	<reference name="wcag20general" src="bibtex:misc" src-info="bibtex:line-33200" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>John</givenname>
				<surname>Slatin</surname>
			</person>
		</names>
		<date value="2005-06"/>
		<abstract>
			<richtext>
				<p>This document provides information to Web content developers who wish to satisfy the success criteria of "Web Content Accessibility Guidelines 2.0" (currently a W3C Working Draft). The techniques in this document can be applied to a wide range of Web technologies. Use of the illustrative techniques provided in this document may make it more likely for Web content to demonstrate conformance to WCAG 2.0 success criteria (by passing the relevant tests in the WCAG 2.0 test suite — to be developed) than if these illustrative techniques are not used. There may be other techniques besides those provided in this document that may be used to demonstrate conformance to WCAG 2.0; in that case, it is encouraged to submit those techniques to the WCAG WG for consideration for inclusion in this document, so that the set of techniques maintained by the WCAG WG is as comprehensive as possible. Deprecated examples illustrate techniques that the Working Group no longer recommends, but may be applicable in some cases. This document is part of a series of documents published by the W3C Web Accessibility Initiative (WAI) to support WCAG 2.0.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-WCAG20-GENERAL-20050630</howpublished>
		<title type="sharef:primaryTitle">General Techniques for WCAG 2.0</title>
		<field type="bibtex:topic">wai[0.9] wcag[0.9]</field>
		<field type="bibtex:updates">wcag20gateway</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2005/WD-WCAG20-GENERAL-20050630</identifier>
	</reference>
	<reference name="wcag10core" src="bibtex:misc" src-info="bibtex:line-33212" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Wendy</givenname>
				<surname>Chisholm</surname>
			</person>
			<person>
				<givenname>Gregg</givenname>
				<surname>Vanderheiden</surname>
			</person>
			<person>
				<givenname>Ian</givenname>
				<surname>Jacobs</surname>
			</person>
		</names>
		<date value="2000-11"/>
		<abstract>
			<richtext>
				<p>This document describes techniques for authoring accessible content that apply across technologies. It is intended to help authors of Web content who wish to claim conformance to "Web Content Accessibility Guidelines 1.0". While the techniques in this document should help people author Web content that conforms to "Web Content Accessibility Guidelines 1.0", these techniques are neither guarantees of conformance nor the only way an author might produce conforming content. This document is part of a series of documents about techniques for authoring accessible Web content. For information about the other documents in the series, please refer to "Techniques for Web Content Accessibility Guidelines 1.0".</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Note NOTE-WCAG10-CORE-TECHS-20001106</howpublished>
		<title type="sharef:primaryTitle">Core Techniques for Web Content Accessibility Guidelines 1.0</title>
		<field type="bibtex:topic">wai[0.9] wcag[1]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2000/NOTE-WCAG10-CORE-TECHS-20001106</identifier>
	</reference>
	<reference name="wcag10" src="bibtex:misc" src-info="bibtex:line-33223" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Wendy</givenname>
				<surname>Chisholm</surname>
			</person>
			<person>
				<givenname>Gregg</givenname>
				<surname>Vanderheiden</surname>
			</person>
			<person>
				<givenname>Ian</givenname>
				<surname>Jacobs</surname>
			</person>
		</names>
		<date value="2000-11"/>
		<abstract>
			<richtext>
				<p>This document is the gateway to a series of related documents that provide techniques for satisfying the requirements defined in "Web Content Accessibility Guidelines 1.0". This series includes: 1. "Techniques for Web Content Accessibility Guidelines 1.0", the current document, which is the gateway to the other documents. 2. "Core Techniques for Web Content Accessibility Guidelines 1.0", which discusses the accessibility themes and general techniques that apply across technologies (e.g., validation, testing, etc.). 3. "HTML Techniques for Web Content Accessibility Guidelines 1.0", which provides examples and strategies for authoring accessible Hypertext Markup Language (HTML) content. 4. "CSS Techniques for Web Content Accessibility Guidelines 1.0", which provides examples and strategies to help authors write Cascading Style Sheets (CSS) as part of accessible content design.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Note NOTE-WCAG10-TECHS-20001106</howpublished>
		<title type="sharef:primaryTitle">Techniques for Web Content Accessibility Guidelines 1.0</title>
		<field type="bibtex:topic">wai[0.9] wcag[1]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2000/NOTE-WCAG10-TECHS-20001106</identifier>
	</reference>
	<reference name="waiat" src="bibtex:misc" src-info="bibtex:line-33234" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Jutta</givenname>
				<surname>Treviranus</surname>
			</person>
			<person>
				<givenname>Jan</givenname>
				<surname>Richards</surname>
			</person>
			<person>
				<givenname>Ian</givenname>
				<surname>Jacobs</surname>
			</person>
			<person>
				<givenname>Charles</givenname>
				<surname>McCathieNevile</surname>
			</person>
		</names>
		<date value="2000-02"/>
		<abstract>
			<richtext>
				<p>This specification provides guidelines for Web authoring tool developers. Its purpose is two-fold: to assist developers in designing authoring tools that produce accessible Web content and to assist developers in creating an accessible authoring interface. Authoring tools can enable, encourage, and assist users ("authors") in the creation of accessible Web content through prompts, alerts, checking and repair functions, help files and automated tools. It is just as important that all people be able to author content as it is for all people to have access to it. The tools used to create this information must therefore be accessible themselves. Adoption of these guidelines will contribute to the proliferation of Web content that can be read by a broader range of readers and authoring tools that can be used by a broader range of authors. This document is part of a series of accessibility documents published by the W3C Web Accessibility Initiative (WAI).</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Recommendation REC-ATAG10-20000203</howpublished>
		<title type="sharef:primaryTitle">Authoring Tool Accessibility Guidelines 1.0</title>
		<field type="bibtex:topic">wai[0.9] atag[1]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2000/REC-ATAG10-20000203</identifier>
	</reference>
	<reference name="ariaroadmap" src="bibtex:misc" src-info="bibtex:line-33245" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Richard</givenname>
				<surname>Schwerdtfeger</surname>
			</person>
		</names>
		<date value="2008-02"/>
		<abstract>
			<richtext>
				<p>The Roadmap for Accessible Rich Internet Applications addresses the accessibility of dynamic Web content for people with disabilities. The roadmap introduces the technologies to map controls, Ajax live regions, and events to accessibility APIs, including custom controls used for Rich Internet Applications. The roadmap also describes new navigation techniques to mark common Web structures as menus, primary content, secondary content, banner information and other types of Web structures. These new technologies can be used to improve the accessibility and usability of Web resources by people with disabilities, without extensive modification to existing libraries of Web resources. This document is part of the WAI-ARIA suite described in the ARIA Overview.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-wai-aria-roadmap-20080204</howpublished>
		<title type="sharef:primaryTitle">Roadmap for Accessible Rich Internet Applications (WAI-ARIA Roadmap)</title>
		<field type="bibtex:topic">aria[0.9] ajax[0.8]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2008/WD-wai-aria-roadmap-20080204</identifier>
	</reference>
	<reference name="ariastate" src="bibtex:misc" src-info="bibtex:line-33256" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Lisa</givenname>
				<surname>Seeman</surname>
			</person>
			<person>
				<givenname>Michael</givenname>
				<surname>Cooper</surname>
			</person>
		</names>
		<date value="2007-10"/>
		<abstract>
			<richtext>
				<p>The attributes defined in this specification enable XML languages to add information about the behavior of an element. States and Properties are mapped to accessibility frameworks (such as a screen reader) that use this information to provide alternative access solutions. Similarly, States and Properties can be used to change the rendering of content dynamically using different style sheet properties. The result is an interoperable method for associating behaviors with document-level markup. This document and the Roles for Accessible Rich Internet Applications (WAI-ARIA Roles) fill information gaps identified by the Roadmap for Accessible Rich Internet Applications (WAI-ARIA Roadmap) to enable accessible dynamic Web content and applications. The WAI-ARIA Roadmap performs the gap analysis identifying what technology is needed to keep the new, richly interactive Web universally accessible. The WAI-ARIA Roles specification sets out an abstract model of building blocks for accessible interfaces. This includes interactive widgets, navigable structures, and an extension mechanism. This specification creates a language module implementing the functional requirements of the abstract model that is ready for incorporation in content format profiles that follow the methods of XHTML Modularization. It also introduces one such profile for the use of this module in XHTML.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-aria-state-20071019</howpublished>
		<title type="sharef:primaryTitle">States and Properties Module for Accessible Rich Internet Applications (WAI-ARIA States and Properties) Version 1.0 — Syntax for Adding Accessible State Information and Author Settable Properties for XML</title>
		<field type="bibtex:topic">aria[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2007/WD-aria-state-20071019</identifier>
	</reference>
	<reference name="ariarole" src="bibtex:misc" src-info="bibtex:line-33267" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Lisa</givenname>
				<surname>Seeman</surname>
			</person>
			<person>
				<givenname>Michael</givenname>
				<surname>Cooper</surname>
			</person>
		</names>
		<date value="2007-10"/>
		<abstract>
			<richtext>
				<p>Accessibility is often dependent on Assistive Technology (AT), tools that provide alternate modes of access for people with disabilities by transforming complex user interfaces into an alternate presentation. This transformation requires information about the role, state, and other semantics of specific portions of a document to be able to transform them appropriately. Rich Web applications typically rely on hybrid technologies such as DHTML and AJAX that combine multiple technologies: SVG, HTML and JavaScript for example. The various technologies provide much but not all of the information needed to support AT adequately. This specification provides a Web-standard way to identify roles in dynamic Web content. The result is an interoperable way to associate behaviors and structure with existing markup. This document and the States and Properties Module for Accessible Rich Internet Applications (WAI-ARIA States and Properties) fill information gaps identified by the Roadmap for Accessible Rich Internet Applications (WAI-ARIA Roadmap). The role attribute defined in the XHTML Role Attribute Module is the preferred way to expose these roles in XHTML applications.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-aria-role-20071019</howpublished>
		<title type="sharef:primaryTitle">Roles for Accessible Rich Internet Applications (WAI-ARIA Roles) Version 1.0 — An RDF Role Taxonomy with QName Support for Accessible Adaptable XML Applications</title>
		<field type="bibtex:topic">aria[1]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2007/WD-aria-role-20071019</identifier>
	</reference>
	<reference name="ariaprimer" src="bibtex:misc" src-info="bibtex:line-33278" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Lisa</givenname>
				<surname>Pappas</surname>
			</person>
			<person>
				<givenname>Richard</givenname>
				<surname>Schwerdtfeger</surname>
			</person>
			<person>
				<givenname>Michael</givenname>
				<surname>Cooper</surname>
			</person>
		</names>
		<date value="2010-09"/>
		<abstract>
			<richtext>
				<p>The WAI-WAI-ARIA Primer introduces developers to the use of WAI-ARIA for addressing the accessibility of dynamic Web content for people with disabilities. This primer explains the accessibility problems posed by hybrid technologies such as Dynamic Hypertext Markup Language (DHTML) and Asynchronous Java and XML (Ajax). It introduces the technologies to map controls, Ajax live regions, and events to accessibility application programming interfaces (APIs), including custom controls used for Rich Internet Applications. The primer also describes new navigation techniques to mark common Web elements with roles such as menus, primary content, secondary content, banner information and other types of Web structures. These new technologies can be used to improve the accessibility and usability of Web resources by people with disabilities, without extensive modification to existing libraries of Web resources. This document is part of the WAI-ARIA suite described in the WAI-ARIA Overview.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-wai-aria-primer-20100916</howpublished>
		<title type="sharef:primaryTitle">WAI-ARIA 1.0 Primer</title>
		<field type="bibtex:topic">aria[1]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2010/WD-wai-aria-primer-20100916</identifier>
	</reference>
	<reference name="ariapractices" src="bibtex:misc" src-info="bibtex:line-33289" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Lisa</givenname>
				<surname>Pappas</surname>
			</person>
			<person>
				<givenname>Michael</givenname>
				<surname>Cooper</surname>
			</person>
			<person>
				<givenname>Richard</givenname>
				<surname>Schwerdtfeger</surname>
			</person>
		</names>
		<date value="2010-09"/>
		<abstract>
			<richtext>
				<p>This WAI-ARIA Authoring Practices Guide provides readers with an understanding of how to use WAI-ARIA to create accessible rich internet applications. It describes considerations that might not be evident to most authors from the WAI-ARIA specification alone and recommends approaches to make widgets, navigation, and behaviors accessible using WAI-ARIA roles, states, and properties. This document is directed primarily to Web application developers, but the guidance is also useful for user agent and assistive technology developers. This document is part of the WAI-ARIA suite described in the WAI-ARIA Overview.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-wai-aria-practices-20100916</howpublished>
		<title type="sharef:primaryTitle">WAI-ARIA 1.0 Authoring Practices</title>
		<field type="bibtex:topic">aria[1]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2010/WD-wai-aria-practices-20100916</identifier>
	</reference>
	<reference name="aria" src="bibtex:misc" src-info="bibtex:line-33300" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>James</givenname>
				<surname>Craig</surname>
			</person>
			<person>
				<givenname>Michael</givenname>
				<surname>Cooper</surname>
			</person>
		</names>
		<date value="2011-01"/>
		<abstract>
			<richtext>
				<p>Accessibility of web content requires semantic information about widgets, structures, and behaviors, in order to allow assistive technologies to convey appropriate information to persons with disabilities. This specification provides an ontology of roles, states, and properties that define accessible user interface elements and can be used to improve the accessibility and interoperability of web content and applications. These semantics are designed to allow an author to properly convey user interface behaviors and structural information to assistive technologies in document-level markup. This document is part of the WAI-ARIA suite described in the WAI-ARIA Overview.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Candidate Recommendation CR-wai-aria-20110118</howpublished>
		<title type="sharef:primaryTitle">Accessible Rich Internet Applications (WAI-ARIA) 1.0</title>
		<field type="bibtex:topic">aria[1]</field>
		<field type="bibtex:updates">ariastate ariarole</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2011/CR-wai-aria-20110118</identifier>
	</reference>
	<reference name="ariaimplementation" src="bibtex:misc" src-info="bibtex:line-33312" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Andi</givenname>
				<surname>Snow-Weaver</surname>
			</person>
			<person>
				<givenname>Michael</givenname>
				<surname>Cooper</surname>
			</person>
		</names>
		<date value="2010-09"/>
		<abstract>
			<richtext>
				<p>This document describes how user agents should support keyboard navigation and respond to roles, states, and properties provided in Web content via WAI-ARIA. These features are used by authors creating accessible rich internet applications. Users often access the content using assistive technologies that rely on platform accessibility APIs to obtain and interact with information from the page. The WAI-ARIA User Agent Implementation Guide defines how implementations should expose content to accessibility APIs, helping to ensure that this information appears in a manner consistent with author intent. This document is part of the WAI-ARIA suite described in the WAI-ARIA Overview.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-wai-aria-implementation-20100916</howpublished>
		<title type="sharef:primaryTitle">WAI-ARIA 1.0 User Agent Implementation Guide</title>
		<field type="bibtex:topic">aria[1]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2010/WD-wai-aria-implementation-20100916</identifier>
	</reference>
	<reference name="rwabackplane" src="bibtex:misc" src-info="bibtex:line-33323" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Mark</givenname>
				<surname>Birbeck</surname>
			</person>
			<person>
				<givenname>John</givenname>
				<surname>Boyer</surname>
			</person>
			<person>
				<givenname>Al</givenname>
				<surname>Gilman</surname>
			</person>
			<person>
				<givenname>Kevin</givenname>
				<surname>Kelly</surname>
			</person>
			<person>
				<givenname>Steven</givenname>
				<surname>Pemberton</surname>
			</person>
			<person>
				<givenname>Charlie</givenname>
				<surname>Wiecha</surname>
			</person>
		</names>
		<date value="2006-11"/>
		<abstract>
			<richtext>
				<p>This paper introduces the concept of a "Rich Web Application Backplane" — a set of common building blocks for web applications. We argue that submission, data models, model-view binding and behavior, and web components can provide a common infrastructure for multiple markup formats. Further, we propose a common infrastructure for both declarative and imperative web programming languages. By aligning APIs and their declarative representations, we hope to support both implementation approaches and increase interoperability between them.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Note NOTE-backplane-20061116</howpublished>
		<title type="sharef:primaryTitle">Rich Web Application Backplane</title>
		<identifier type="sharef:uri">http://www.w3.org/TR/2006/NOTE-backplane-20061116</identifier>
	</reference>
	<reference name="clipboardapis" src="bibtex:misc" src-info="bibtex:line-33333" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Hallvord R. M.</givenname>
				<surname>Steen</surname>
			</person>
		</names>
		<date value="2011-04"/>
		<abstract>
			<richtext>
				<p>This document describes APIs for clipboard operations such as copy, cut and paste in web applications.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-clipboard-apis-20110412</howpublished>
		<title type="sharef:primaryTitle">Clipboard API and vEents</title>
		<identifier type="sharef:uri">http://www.w3.org/TR/2011/WD-clipboard-apis-20110412</identifier>
	</reference>
	<reference name="fileupload" src="bibtex:misc" src-info="bibtex:line-33343" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Robin</givenname>
				<surname>Berjon</surname>
			</person>
		</names>
		<date value="2006-10"/>
		<abstract>
			<richtext>
				<p>This specification provides an API  used to prompt the user with a file selection dialogue and obtain the data contained in files on the user's file system.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-file-upload-20061018</howpublished>
		<title type="sharef:primaryTitle">File Upload</title>
		<identifier type="sharef:uri">http://www.w3.org/TR/2006/WD-file-upload-20061018</identifier>
	</reference>
	<reference name="atag20" src="bibtex:misc" src-info="bibtex:line-33353" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Jutta</givenname>
				<surname>Treviranus</surname>
			</person>
			<person>
				<givenname>Jan</givenname>
				<surname>Richards</surname>
			</person>
			<person>
				<givenname>Jeanne</givenname>
				<surname>Spellman</surname>
			</person>
		</names>
		<date value="2010-07"/>
		<abstract>
			<richtext>
				<p>This specification provides guidelines for designing web content authoring tools that are both (1) more accessible for authors with disabilities and (2) designed to enable, support, and promote the production of accessible web content by all authors. The "Authoring Tool Accessibility Guidelines 2.0" (ATAG 2.0) is part of a series of accessibility guidelines published by the W3C Web Accessibility Initiative (WAI).</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-ATAG20-20100708</howpublished>
		<title type="sharef:primaryTitle">Authoring Tool Accessibility Guidelines (ATAG) 2.0</title>
		<field type="bibtex:topic">wai[0.9] atag[1]</field>
		<field type="bibtex:updates">waiat</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2010/WD-ATAG20-20100708</identifier>
	</reference>
	<reference name="atag20techs" src="bibtex:misc" src-info="bibtex:line-33365" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Jutta</givenname>
				<surname>Treviranus</surname>
			</person>
			<person>
				<givenname>Jan</givenname>
				<surname>Richards</surname>
			</person>
			<person>
				<givenname>Jeanne</givenname>
				<surname>Spellman</surname>
			</person>
		</names>
		<date value="2010-07"/>
		<abstract>
			<richtext>
				<p>This specification provides guidelines for designing web content authoring tools that are both (1) more accessible to authors with disabilities and (2) designed to enable, support, and promote the production of accessible web content by all authors. The "Authoring Tool Accessibility Guidelines 2.0" (ATAG 2.0) is part of a series of accessibility guidelines published by the W3C Web Accessibility Initiative (WAI).</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-IMPLEMENTING-ATAG20-20100708</howpublished>
		<title type="sharef:primaryTitle">Implementing ATAG 2.0</title>
		<field type="bibtex:topic">wai[0.9] atag[1]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2010/WD-IMPLEMENTING-ATAG20-20100708</identifier>
	</reference>
	<reference name="waitat" src="bibtex:misc" src-info="bibtex:line-33376" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Jutta</givenname>
				<surname>Treviranus</surname>
			</person>
			<person>
				<givenname>Charles</givenname>
				<surname>McCathieNevile</surname>
			</person>
			<person>
				<givenname>Jan</givenname>
				<surname>Richards</surname>
			</person>
			<person>
				<givenname>Gregory</givenname>
				<surname>Rosmaita</surname>
			</person>
		</names>
		<date value="2002-10"/>
		<howpublished>World Wide Web Consortium, Note NOTE-ATAG10-TECHS-20021029</howpublished>
		<title type="sharef:primaryTitle">Techniques for Authoring Tool Accessibility Guidelines 1.0</title>
		<field type="bibtex:topic">wai[0.9] atag[1]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2002/NOTE-ATAG10-TECHS-20021029</identifier>
	</reference>
	<reference name="waiua" src="bibtex:misc" src-info="bibtex:line-33386" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Ian</givenname>
				<surname>Jacobs</surname>
			</person>
			<person>
				<givenname>Jon</givenname>
				<surname>Gunderson</surname>
			</person>
			<person>
				<givenname>Eric</givenname>
				<surname>Hansen</surname>
			</person>
		</names>
		<date value="2002-12"/>
		<abstract>
			<richtext>
				<p>This document provides guidelines for designing user agents that lower barriers to Web accessibility for people with disabilities (visual, hearing, physical, cognitive, and neurological). User agents include HTML browsers and other types of software that retrieve and render Web content. A user agent that conforms to these guidelines will promote accessibility through its own user interface and through other internal facilities, including its ability to communicate with other technologies (especially assistive technologies). Furthermore, all users, not just users with disabilities, should find conforming user agents to be more usable. In addition to helping developers of HTML browsers and media players, this document will also benefit developers of assistive technologies because it explains what types of information and control an assistive technology may expect from a conforming user agent. Technologies not addressed directly by this document (e.g., technologies for braille rendering) will be essential to ensuring Web access for some users with disabilities.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Recommendation REC-UAAG10-20021217</howpublished>
		<title type="sharef:primaryTitle">User Agent Accessibility Guidelines 1.0</title>
		<field type="bibtex:topic">wai[0.9] uaag[1]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2002/REC-UAAG10-20021217</identifier>
	</reference>
	<reference name="waitua" src="bibtex:misc" src-info="bibtex:line-33397" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Ian</givenname>
				<surname>Jacobs</surname>
			</person>
			<person>
				<givenname>Jon</givenname>
				<surname>Gunderson</surname>
			</person>
			<person>
				<givenname>Eric</givenname>
				<surname>Hansen</surname>
			</person>
		</names>
		<date value="2002-12"/>
		<abstract>
			<richtext>
				<p>This document provides techniques for satisfying the checkpoints defined in "User Agent Accessibility Guidelines 1.0". These techniques address key aspects of the accessibility of user interfaces, content rendering, application programming interfaces (APIs), and languages such as the Hypertext Markup Language (HTML), Cascading Style Sheets (CSS) and the Synchronized Multimedia Integration Language (SMIL). The techniques listed in this document are not required for conformance to the Guidelines. These techniques are not necessarily the only way of satisfying the checkpoint, nor are they a definitive set of requirements for satisfying a checkpoint.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft NOTE-UAAG10-TECHS-20021217</howpublished>
		<title type="sharef:primaryTitle">Techniques for User Agent Accessibility Guidelines 1.0</title>
		<field type="bibtex:topic">wai[0.9] uaag[1]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2002/NOTE-UAAG10-TECHS-20021217</identifier>
	</reference>
	<reference name="uaag20reqs" src="bibtex:misc" src-info="bibtex:line-33408" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Jim</givenname>
				<surname>Allan</surname>
			</person>
			<person>
				<givenname>Jan</givenname>
				<surname>Richards</surname>
			</person>
		</names>
		<date value="2007-10"/>
		<abstract>
			<richtext>
				<p>This First Public Working Draft outlines the requirements that the User Agent Accessibility Guidelines Working Group (UAWG) has set for development of User Agent Accessibility Guidelines 2.0 (UAAG 2.0). These requirements are based on feedback from the use of UAAG 1.0 and will be used to determine if the UAWG has met its goals as UAAG 2.0 advances through the W3C Recommendation Track Process.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-UAAG20-requirements-20071031</howpublished>
		<title type="sharef:primaryTitle">User Agent Accessibility Guidelines 2.0 Requirements</title>
		<field type="bibtex:topic">wai[0.9] uaag[1]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2007/WD-UAAG20-requirements-20071031</identifier>
	</reference>
	<reference name="uaag20" src="bibtex:misc" src-info="bibtex:line-33419" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Jim</givenname>
				<surname>Allan</surname>
			</person>
			<person>
				<givenname>Kelly</givenname>
				<surname>Ford</surname>
			</person>
			<person>
				<givenname>Jan</givenname>
				<surname>Richards</surname>
			</person>
			<person>
				<givenname>Jeanne</givenname>
				<surname>Spellman</surname>
			</person>
		</names>
		<date value="2010-06"/>
		<abstract>
			<richtext>
				<p>This document provides guidelines for designing user agents that lower barriers to Web accessibility for people with disabilities. User agents include browsers and other types of software that retrieve and render Web content. A user agent that conforms to these guidelines will promote accessibility through its own user interface and through other internal facilities, including its ability to communicate with other technologies (especially assistive technologies). Furthermore, all users, not just users with disabilities, should find conforming user agents to be more usable. In addition to helping developers of browsers and media players, this document will also benefit developers of assistive technologies because it explains what types of information and control an assistive technology may expect from a conforming user agent. Technologies not addressed directly by this document (e.g., technologies for braille rendering) will be essential to ensuring Web access for some users with disabilities. The "User Agent Accessibility Guidelines 2.0" (UAAG 2.0) is part of a series of accessibility guidelines published by the W3C Web Accessibility Initiative (WAI).</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-UAAG20-20100311</howpublished>
		<title type="sharef:primaryTitle">User Agent Accessibility Guidelines 2.0</title>
		<field type="bibtex:topic">wai[0.9] uaag[1]</field>
		<field type="bibtex:updates">uaag20reqs</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2010/WD-UAAG20-20100311</identifier>
	</reference>
	<reference name="uaag20guide" src="bibtex:misc" src-info="bibtex:line-33431" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Jim</givenname>
				<surname>Allan</surname>
			</person>
			<person>
				<givenname>Kelly</givenname>
				<surname>Ford</surname>
			</person>
			<person>
				<givenname>Jan</givenname>
				<surname>Richards</surname>
			</person>
			<person>
				<givenname>Jeanne</givenname>
				<surname>Spellman</surname>
			</person>
		</names>
		<date value="2010-06"/>
		<abstract>
			<richtext>
				<p>This document provides supporting information for the User Agent Accessibility Guidelines (UAAG) 2.0 for designing user agents that lower barriers to Web accessibility for people with disabilities. User agents include browsers and other types of software that retrieve and render Web content. A user agent that conforms  to these guidelines will promote accessibility through its own user interface and through other internal facilities, including its ability to communicate with other technologies (especially assistive technologies). Furthermore, all users, not just users with disabilities, should find conforming user agents to be more usable. In addition to helping developers of browsers and media players, this document will also benefit developers of assistive technologies because it explains what types of information and control an assistive technology may expect from a conforming user agent. Technologies not addressed directly by this document (e.g., technologies for braille rendering) will be essential to ensuring Web access for some users with disabilities. This document provides explanation of the intent of UAAG 2.0 success criteria, examples of implementation of the guidelines, best practice recommendations and additional resources for the guideline. The "User Agent Accessibility Guidelines 2.0" (UAAG 2.0) is part of a series of accessibility guidelines published by the W3C Web Accessibility Initiative (WAI).</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-IMPLEMENTING-UAAG20-20100617</howpublished>
		<title type="sharef:primaryTitle">Implementing UAAG 2.0: A guide to understanding and implementing User Agent Accessibility Guidelines 2.0</title>
		<field type="bibtex:topic">wai[0.9] uaag[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2010/WD-IMPLEMENTING-UAAG20-20100617</identifier>
	</reference>
	<reference name="xmlagl" src="bibtex:misc" src-info="bibtex:line-33442" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Daniel</givenname>
				<surname>Dardailler</surname>
			</person>
			<person>
				<givenname>Sean B.</givenname>
				<surname>Palmer</surname>
			</person>
			<person>
				<givenname>Charles</givenname>
				<surname>McCathieNevile</surname>
			</person>
		</names>
		<date value="2001-10"/>
		<abstract>
			<richtext>
				<p>This document provides guidelines for designing Extensible Markup Language (XML) applications that lower barriers to Web accessibility for people with disabilities (visual, hearing, physical, cognitive, and neurological). XML, used to design applications such as XHTML, SMIL, and SVG, provides no intrinsic guarantee of the accessibility of those applications. This document explains how to include features in XML applications that promote accessibility.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-xag-20021003</howpublished>
		<title type="sharef:primaryTitle">XML Accessibility Guidelines</title>
		<field type="bibtex:topic">wai[0.9] xml[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2002/WD-xag-20021003</identifier>
	</reference>
	<reference name="cssp" src="bibtex:misc" src-info="bibtex:line-33453" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Robert</givenname>
				<surname>Stevahn</surname>
			</person>
			<person>
				<givenname>Scott</givenname>
				<surname>Furman</surname>
			</person>
			<person>
				<givenname>Scott</givenname>
				<surname>Isaacs</surname>
			</person>
		</names>
		<date value="1997-08"/>
		<abstract>
			<richtext>
				<p>The HyperText Markup Language (HTML) is a simple markup language used to create hypertext documents that are portable from one platform to another. HTML documents are SGML documents with generic semantics that are appropriate for representing information from a wide range of applications. CSS (Cascading Style Sheets) is a style sheets language that can be applied to HTML to control the style of a document: which fonts and colors to use, how much white space to insert, etc. The following specification extends CSS to support the positioning and visibility of HTML elements in three-dimensional space. Familiarity with both CSS1 and HTML 3.2 are assumed.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-positioning-19970819</howpublished>
		<title type="sharef:primaryTitle">Positioning HTML Elements with Cascading Style Sheets</title>
		<field type="bibtex:topic">css[0.9] cssp[1]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/WD-positioning-19970819</identifier>
	</reference>
	<reference name="cuap" src="bibtex:misc" src-info="bibtex:line-33464" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Karl</givenname>
				<surname>Dubost</surname>
			</person>
		</names>
		<date value="2003-01"/>
		<abstract>
			<richtext>
				<p>This document explains some common mistakes in user agents due to incorrect or incomplete implementation of specifications, and suggests remedies. It also suggests some "good behavior" where specifications themselves do not specify any particular behavior (e.g., in the face of error conditions). This document is not a complete set of guidelines for good user agent behavior. This document does not incriminate specific user agents. W3C does not generally track bugs or errors in implementations. That information is generally tracked by the vendors themselves or third parties.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Note NOTE-cuap-20030128</howpublished>
		<title type="sharef:primaryTitle">Common User Agent Problems</title>
		<field type="bibtex:topic">httpclient[0.9] browser[0.9] http[0.9] html[0.9] css[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2003/NOTE-cuap-20030128</identifier>
	</reference>
	<reference name="chips" src="bibtex:misc" src-info="bibtex:line-33475" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Olivier</givenname>
				<surname>Théreaux</surname>
			</person>
		</names>
		<date value="2003-01"/>
		<abstract>
			<richtext>
				<p>This document is a set of good practices to improve implementations of HTTP and related standards as well as their use. It explains a few basic concepts, points out common mistakes and misbehaviors, and suggests "best practices". This document does not incriminate any specific product. W3C does not track bugs or errors in implementations. That information is generally tracked by the vendors themselves, or third parties.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Note NOTE-chips-20030128</howpublished>
		<title type="sharef:primaryTitle">Common HTTP Implementation Problems</title>
		<field type="bibtex:topic">httpserver[0.9] httpclient[0.9] http[0.8]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2003/NOTE-chips-20030128</identifier>
	</reference>
	<reference name="httpinrdf" src="bibtex:misc" src-info="bibtex:line-33486" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Johannes</givenname>
				<surname>Koch</surname>
			</person>
			<person>
				<givenname>Carlos A.</givenname>
				<surname>Velasco</surname>
			</person>
		</names>
		<date value="2009-10"/>
		<abstract>
			<richtext>
				<p>The identification of resources on the Web by a Uniform Resource Identifier(URI) alone may not be sufficient, as other factors such as HTTP content negotiation might come into play. This issue is particularly significant for quality assurance testing, conformance claims, and reporting languages like the W3C Evaluation And Report Language (EARL). This document provides a representation of the HTTP vocabulary in the Resource Description Framework (RDF), to allow quality assurance tools to record the HTTP headers that have been exchanged between a client and a server. The RDF terms defined by this document represent the core HTTP specification defined by RFC 2616, as well as additional HTTP headers registered by the Internet Assigned Numbers Authority (IANA). These terms can also be used to record HTTPS exchanges.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-HTTP-in-RDF10-20091029</howpublished>
		<title type="sharef:primaryTitle">HTTP Vocabulary in RDF 1.0</title>
		<field type="bibtex:topic">http[0.8] rdf[0.8]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2009/WD-HTTP-in-RDF10-20091029</identifier>
	</reference>
	<reference name="contentinrdf" src="bibtex:misc" src-info="bibtex:line-33497" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Johannes</givenname>
				<surname>Koch</surname>
			</person>
			<person>
				<givenname>Carlos A.</givenname>
				<surname>Velasco</surname>
			</person>
		</names>
		<date value="2009-10"/>
		<abstract>
			<richtext>
				<p>This document is a specification for a vocabulary to represent content in the Resource Description Framework (RDF). This vocabulary is intended to provide a flexible framework within different usage scenarios to semantically represent any type of content, be it on the Web or in local storage media. For example, it can be used by Web quality assurance tools such as Web accessibility evaluation tools to record a representation of the assessed Web content, included text, images, or other types of formats. In many cases it can be used together with HTTP Vocabulary in RDF 1.0, which allows quality assurance tools to record the HTTP headers that have been exchanged between a client and a server. This is particularly useful for quality assurance testing, conformance claims, and reporting languages like the W3C Evaluation And Report Language (EARL).</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-Content-in-RDF10-20091029</howpublished>
		<title type="sharef:primaryTitle">Representing Content in RDF 1.0</title>
		<field type="bibtex:topic">http[0.8] rdf[0.8]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2009/WD-Content-in-RDF10-20091029</identifier>
	</reference>
	<reference name="poix" src="bibtex:misc" src-info="bibtex:line-33508" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Hiroyuki</givenname>
				<surname>Kanemitsu</surname>
			</person>
			<person>
				<givenname>Tomihisa</givenname>
				<surname>Kamada</surname>
			</person>
		</names>
		<date value="1999-06"/>
		<abstract>
			<richtext>
				<p>The Internet is rapidly growing toward wireless and mobile environment beyond the wired world. Nowadays, various types of mobile devices including PDAs and car navigation systems can access to the Internet. These devices are required to exchange the location-related information such as position data on the map. The "POIX" proposed here defines a general-purpose specification language for describing location information, which is an application of XML (Extensible Markup Language). POIX is a common baseline for exchanging location data via e-mail and embedding location data in HTML and XML documents. This specification can be used by mobile device developers, location-related service providers, and server software developers.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Note NOTE-poix-19990624</howpublished>
		<title type="sharef:primaryTitle">POIX: Point Of Interest eXchange Language Specification</title>
		<field type="bibtex:topic">poix[1]</field>
		<identifier type="sharef:uri">http://www.w3.org/1999/06/NOTE-poix-19990624</identifier>
	</reference>
	<reference name="srml" src="bibtex:misc" src-info="bibtex:line-33519" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Steven W.</givenname>
				<surname>Reichenthal</surname>
			</person>
		</names>
		<date value="2002-12"/>
		<howpublished>World Wide Web Consortium, Note NOTE-SRML-20021218</howpublished>
		<title type="sharef:primaryTitle">SRML — Simulation Reference Markup Language</title>
		<field type="bibtex:topic">srml[1]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2002/NOTE-SRML-20021218</identifier>
	</reference>
	<reference name="egix" src="bibtex:misc" src-info="bibtex:line-33529" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Akira</givenname>
				<surname>Kawamata</surname>
			</person>
		</names>
		<date value="2002-12"/>
		<howpublished>World Wide Web Consortium, Note NOTE-EGIX-20021220</howpublished>
		<title type="sharef:primaryTitle">Embedding Glyph Identifiers in XML Documents</title>
		<identifier type="sharef:uri">http://www.w3.org/TR/2002/NOTE-EGIX-20021220</identifier>
	</reference>
	<reference name="p3prdf" src="bibtex:misc" src-info="bibtex:line-33538" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Brian</givenname>
				<surname>McBride</surname>
			</person>
			<person>
				<givenname>Rigo</givenname>
				<surname>Wenning</surname>
			</person>
			<person>
				<givenname>Lorrie Faith</givenname>
				<surname>Cranor</surname>
			</person>
		</names>
		<date value="2002-01"/>
		<howpublished>World Wide Web Consortium, Note NOTE-p3p-rdfschema-20020125</howpublished>
		<title type="sharef:primaryTitle">An RDF Schema for P3P</title>
		<field type="bibtex:topic">p3p[0.9] rdf[0.7]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2002/NOTE-p3p-rdfschema-20020125</identifier>
	</reference>
	<reference name="appel" src="bibtex:misc" src-info="bibtex:line-33548" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Lorrie Faith</givenname>
				<surname>Cranor</surname>
			</person>
			<person>
				<givenname>Marc</givenname>
				<surname>Langheinrich</surname>
			</person>
			<person>
				<givenname>Massimo</givenname>
				<surname>Marchiori</surname>
			</person>
		</names>
		<date value="2002-04"/>
		<howpublished>World Wide Web Consortium, Working Draft WD-P3P-preferences-20020415</howpublished>
		<title type="sharef:primaryTitle">A P3P Preference Exchange Language 1.0 (APPEL 1.0)</title>
		<field type="bibtex:topic">p3p[0.9] appel[1]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2002/WD-P3P-preferences-20020415</identifier>
	</reference>
	<reference name="p3pdepl" src="bibtex:misc" src-info="bibtex:line-33558" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Martin</givenname>
				<surname>Presler-Marshall</surname>
			</person>
		</names>
		<date value="2002-02"/>
		<howpublished>World Wide Web Consortium, Note NOTE-p3pdeployment-20020211</howpublished>
		<title type="sharef:primaryTitle">The Platform for Privacy Preferences 1.0 Deployment Guide</title>
		<field type="bibtex:topic">p3p[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2002/NOTE-p3pdeployment-20020211</identifier>
	</reference>
	<reference name="p3p" src="bibtex:misc" src-info="bibtex:line-33568" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Lorrie Faith</givenname>
				<surname>Cranor</surname>
			</person>
			<person>
				<givenname>Marc</givenname>
				<surname>Langheinrich</surname>
			</person>
			<person>
				<givenname>Massimo</givenname>
				<surname>Marchiori</surname>
			</person>
			<person>
				<givenname>Martin</givenname>
				<surname>Presler-Marshall</surname>
			</person>
			<person>
				<givenname>Joseph M.</givenname>
				<surname>Reagle</surname>
			</person>
		</names>
		<date value="2002-04"/>
		<abstract>
			<richtext>
				<p>This is the specification of the Platform for Privacy Preferences (P3P). This document, along with its normative references, includes all the specification necessary for the implementation of interoperable P3P applications.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Recommendation REC-P3P-20020416</howpublished>
		<title type="sharef:primaryTitle">The Platform for Privacy Preferences 1.0 (P3P1.0) Specification</title>
		<field type="bibtex:topic">p3p[1]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2002/REC-P3P-20020416</identifier>
	</reference>
	<reference name="cra97" src="bibtex:misc" src-info="bibtex:line-33579" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Lorrie Faith</givenname>
				<surname>Cranor</surname>
			</person>
			<person>
				<givenname>Joseph M.</givenname>
				<surname>Reagle</surname>
			</person>
		</names>
		<date value="1997-11"/>
		<abstract>
			<richtext>
				<p>The Platform for Privacy Preferences Project (P3P), under development by the World Wide Web Consortium (W3C), enables users and Web sites to reach explicit agreements regarding sites' data privacy practices. The options chosen in developing the protocols, grammar, and vocabulary needed for an agreement lead the authors to a number of generalizations regarding the development of technology designed for "social" purposes. In this paper we will explain the goals of P3P; discuss the importance of simplicity, layering, and defaults in the development of social protocols; and examine the sometimes-difficult relationship between technical and policy decisions in this domain.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Note NOTE-TPRC-970930</howpublished>
		<title type="sharef:primaryTitle">Designing a Social Protocol: Lessons Learned from the Platform for Privacy Preferences</title>
		<field type="bibtex:topic">p3p[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/NOTE-TPRC-970930</identifier>
	</reference>
	<reference name="p3p11" src="bibtex:misc" src-info="bibtex:line-33590" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Lorrie Faith</givenname>
				<surname>Cranor</surname>
			</person>
			<person>
				<givenname>Brooks</givenname>
				<surname>Dobbs</surname>
			</person>
			<person>
				<givenname>Serge</givenname>
				<surname>Egelman</surname>
			</person>
			<person>
				<givenname>Giles</givenname>
				<surname>Hogben</surname>
			</person>
			<person>
				<givenname>Jack</givenname>
				<surname>Humphrey</surname>
			</person>
			<person>
				<givenname>Marc</givenname>
				<surname>Langheinrich</surname>
			</person>
			<person>
				<givenname>Massimo</givenname>
				<surname>Marchiori</surname>
			</person>
			<person>
				<givenname>Martin</givenname>
				<surname>Presler-Marshall</surname>
			</person>
			<person>
				<givenname>Joseph M.</givenname>
				<surname>Reagle</surname>
			</person>
			<person>
				<givenname>Matthias</givenname>
				<surname>Schunter</surname>
			</person>
			<person>
				<givenname>David A.</givenname>
				<surname>Stampley</surname>
			</person>
			<person>
				<givenname>Rigo</givenname>
				<surname>Wenning</surname>
			</person>
		</names>
		<date value="2006-11"/>
		<abstract>
			<richtext>
				<p>This is the specification of the Platform for Privacy Preferences 1.1 (P3P 1.1). This document, along with its normative references, includes all the specification necessary for the implementation of interoperable P3P 1.1 applications. P3P 1.1 is based on the P3P 1.0 Recommendation and adds some features using the P3P 1.0 Extension mechanism. It also contains a new binding mechanism that can be used to bind policies for XML Applications beyond HTTP transactions.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Note NOTE-P3P11-20061113</howpublished>
		<title type="sharef:primaryTitle">The Platform for Privacy Preferences 1.1 (P3P1.1) Specification</title>
		<field type="bibtex:topic">p3p[1]</field>
		<field type="bibtex:updates">p3p</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2006/NOTE-P3P11-20061113</identifier>
	</reference>
	<reference name="pgml" src="bibtex:misc" src-info="bibtex:line-33602" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Nabeel</givenname>
				<surname>Al-Shamma</surname>
			</person>
			<person>
				<givenname>Robert</givenname>
				<surname>Ayers</surname>
			</person>
			<person>
				<givenname>Richard</givenname>
				<surname>Cohn</surname>
			</person>
			<person>
				<givenname>Jon</givenname>
				<surname>Ferraiolo</surname>
			</person>
			<person>
				<givenname>Martin</givenname>
				<surname>Newell</surname>
			</person>
			<person>
				<givenname>Roger K.</givenname>
				<surname link="de">Bry</surname>
			</person>
			<person>
				<givenname>Kevin</givenname>
				<surname>McCluskey</surname>
			</person>
			<person>
				<givenname>Jerry</givenname>
				<surname>Evans</surname>
			</person>
		</names>
		<date value="1998-04"/>
		<abstract>
			<richtext>
				<p>This document is the specification for the Precision Graphics Markup Language (PGML). PGML is a 2D scalable graphics language designed to meet both the simple vector graphics needs of casual users and the precision needs of graphics artists. PGML uses the imaging model common to the PostScript language and Portable Document Format (PDF); it also contains additional features to satisfy the needs of Web applications.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Note NOTE-PGML-19980410</howpublished>
		<title type="sharef:primaryTitle">Precision Graphics Markup Language (PGML)</title>
		<field type="bibtex:topic">pgml[1]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/1998/NOTE-PGML-19980410</identifier>
	</reference>
	<reference name="vml" src="bibtex:misc" src-info="bibtex:line-33613" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Brian</givenname>
				<surname>Mathews</surname>
			</person>
			<person>
				<givenname>Daniel T.</givenname>
				<surname>Lee</surname>
			</person>
			<person>
				<givenname>Brian</givenname>
				<surname>Dister</surname>
			</person>
			<person>
				<givenname>John</givenname>
				<surname>Bowler</surname>
			</person>
			<person>
				<givenname>Howard</givenname>
				<surname>Cooperstein</surname>
			</person>
			<person>
				<givenname>Ajay</givenname>
				<surname>Jindal</surname>
			</person>
			<person>
				<givenname>Tuan</givenname>
				<surname>Nguyen</surname>
			</person>
			<person>
				<givenname>Peter</givenname>
				<surname>Wu</surname>
			</person>
			<person>
				<givenname>Troy</givenname>
				<surname>Sandal</surname>
			</person>
		</names>
		<date value="1998-05"/>
		<abstract>
			<richtext>
				<p>This document defines the Vector Markup Language (VML). VML is an application of Extensible Markup Language (XML) 1.0 which defines a format for the encoding of vector information together with additional markup to describe how that information may be displayed and edited. The first part of this document is an introduction, which gives an overview of the way VML is organized and how it interacts with both XML and HTML as defined by the HTML 4.0 Specification. This is followed by detailed technical definition of the behavior of every VML element and the permitted and recommended behaviors for all applications. The introduction to this document is intended to be appropriate reading for someone who wishes to gain an overview of VML. The technical specification is intended for authors of application software which might use VML and for people who wish to assess the suitability of VML for a particular application. It may also be used by people who need to hand-author VML content. However it is anticipated that most such authoring will proceed by copy and paste of existing VML — VML is intended to be treated in this way.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Note NOTE-VML-19980513</howpublished>
		<title type="sharef:primaryTitle">Vector Markup Language (VML)</title>
		<field type="bibtex:topic">vml[1]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/1998/NOTE-VML-19980513</identifier>
	</reference>
	<reference name="webcgm" src="bibtex:misc" src-info="bibtex:line-33624" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>David</givenname>
				<surname>Cruikshank</surname>
			</person>
			<person>
				<givenname>John</givenname>
				<surname>Gebhardt</surname>
			</person>
			<person>
				<givenname>Lofton</givenname>
				<surname>Henderson</surname>
			</person>
			<person>
				<givenname>Roy</givenname>
				<surname>Platon</surname>
			</person>
			<person>
				<givenname>Dieter</givenname>
				<surname>Weidenbrück</surname>
			</person>
		</names>
		<date value="1999-01"/>
		<howpublished>World Wide Web Consortium, Recommendation REC-WebCGM-19990121</howpublished>
		<title type="sharef:primaryTitle">WebCGM Profile</title>
		<field type="bibtex:topic">webcgm[1]</field>
	</reference>
	<reference name="webcgm2nd" src="bibtex:misc" src-info="bibtex:line-33633" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>David</givenname>
				<surname>Cruikshank</surname>
			</person>
			<person>
				<givenname>John</givenname>
				<surname>Gebhardt</surname>
			</person>
			<person>
				<givenname>Lofton</givenname>
				<surname>Henderson</surname>
			</person>
			<person>
				<givenname>Roy</givenname>
				<surname>Platon</surname>
			</person>
			<person>
				<givenname>Dieter</givenname>
				<surname>Weidenbrück</surname>
			</person>
		</names>
		<date value="2001-12"/>
		<abstract>
			<richtext>
				<p>CGM (Computer Graphics Metafile) has been an ISO standard for vector and composite vector/raster picture definition since 1987. It has been a registered MIME type since 1995. CGM has a significant following in technical illustration, electronic documentation, geophysical data visualization, amongst other application areas. WebCGM is a profile for the effective application of CGM in Web electronic documents. WebCGM has been a joint effort of the CGM Open Consortium, in collaboration with W3C staff and supported by the European Commission Esprit project. It represents an important interoperability agreement amongst major users and implementors of CGM, and thereby unifies current diverse approaches to CGM utilization in Web document applications. WebCGM's clear and unambiguous conformance requirements will enhance interoperability of implementations, and it should be possible to leverage existing CGM validation tools, test suites, and the product certification testing services for application to WebCGM. While WebCGM is a binary file format and is not "stylable", nevertheless WebCGM follows published W3C requirements for a scalable graphics format where such are applicable. The design criteria for the graphical content of WebCGM aimed at a balance between graphical expressive power on the one hand, and simplicity and implementability on the other. A small but powerful set of metadata elements is standardized in WebCGM, to support the functionalities of: hyperlinking and document navigation; picture structuring and layering; and, search and query on WebCGM picture content.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Recommendation REC-WebCGM-20011217</howpublished>
		<title type="sharef:primaryTitle">WebCGM 1.0 Second Release</title>
		<field type="bibtex:topic">webcgm[1]</field>
		<field type="bibtex:updates">webcgm</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2001/REC-WebCGM-20011217</identifier>
	</reference>
	<reference name="webcgm20" src="bibtex:misc" src-info="bibtex:line-33645" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Benoit</givenname>
				<surname>Bezaire</surname>
			</person>
			<person>
				<givenname>David</givenname>
				<surname>Cruikshank</surname>
			</person>
			<person>
				<givenname>Lofton</givenname>
				<surname>Henderson</surname>
			</person>
		</names>
		<date value="2007-01"/>
		<abstract>
			<richtext>
				<p>Computer Graphics Metafile (CGM) is an ISO standard, defined by ISO/IEC 8632:1999, for the interchange of 2D vector and mixed vector/raster graphics. WebCGM is a profile of CGM, which adds Web linking and is optimized for Web applications in technical illustration, electronic documentation, geophysical data visualization, and similar fields. First published (1.0) in 1999 and followed by a second (errata) release in 2001, WebCGM unifies potentially diverse approaches to CGM utilization in Web document applications. It therefore represents a significant interoperability agreement amongst major users and implementers of the ISO CGM standard. WebCGM 2.0 adds a DOM (API) specification for programmatic access to WebCGM objects, and a specification of an XML Companion File (XCF) architecture, for externalization of non-graphical metadata. WebCGM 2.0, in addition, builds upon and extends the graphical and intelligent content of WebCGM 1.0, delivering functionality that was forecast for WebCGM 1.0, but was postponed in order to get the standard and its implementations to users expeditiously. The design criteria for WebCGM aim at a balance between graphical expressive power on the one hand, and simplicity and implementability on the other. A small but powerful set of standardized metadata elements supports the functionalities of hyperlinking and document navigation, picture structuring and layering, and enabling search and query of WebCGM picture content.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Recommendation REC-webcgm20-20070130</howpublished>
		<title type="sharef:primaryTitle">WebCGM 2.0</title>
		<field type="bibtex:topic">webcgm[1] xcf[1]</field>
		<field type="bibtex:updates">webcgm2nd</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2007REC-webcgm20-20070130</identifier>
	</reference>
	<reference name="webcgm21" src="bibtex:misc" src-info="bibtex:line-33657" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Benoit</givenname>
				<surname>Bezaire</surname>
			</person>
			<person>
				<givenname>Lofton</givenname>
				<surname>Henderson</surname>
			</person>
		</names>
		<date value="2010-03"/>
		<abstract>
			<richtext>
				<p>Computer Graphics Metafile (CGM) is an ISO standard, defined by ISO/IEC 8632:1999, for the interchange of 2D vector and mixed vector/raster graphics. WebCGM is a profile of CGM, which adds Web linking and is optimized for Web applications in technical illustration, electronic documentation, geophysical data visualization, and similar fields. First published (1.0) in 1999, WebCGM unifies potentially diverse approaches to CGM utilization in Web document applications. It therefore represents a significant interoperability agreement amongst major users and implementers of the ISO CGM standard. The design criteria for WebCGM aim to balance graphical expressive power on the one hand, versus simplicity and implementability on the other. A small but powerful set of standardized metadata elements supports the functionalities of hyperlinking and document navigation, picture structuring and layering, and enabling search and query of WebCGM picture content. The present version, WebCGM 2.1, refines and completes the features of the major WebCGM 2.0 release. WebCGM 2.0 added a DOM (API) specification for programmatic access to WebCGM objects, a specification of an XML Companion File (XCF) architecture, and extended the graphical and intelligent content of WebCGM 1.0.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Recommendation REC-webcgm21-20100301</howpublished>
		<title type="sharef:primaryTitle">WebCGM 2.1</title>
		<field type="bibtex:topic">webcgm[1] xcf[1]</field>
		<field type="bibtex:updates">webcgm20</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2010/REC-webcgm21-20100301</identifier>
	</reference>
	<reference name="xhtmlrdfaprimer" src="bibtex:misc" src-info="bibtex:line-33669" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Ben</givenname>
				<surname>Adida</surname>
			</person>
			<person>
				<givenname>Mark</givenname>
				<surname>Birbeck</surname>
			</person>
		</names>
		<date value="2008-10"/>
		<abstract>
			<richtext>
				<p>Today's web is built predominantly for human consumption. Even as machine-readable data begins to appear on the web, it is typically distributed in a separate file, with a separate format, and no correspondence between the human and machine versions. As a result, web browsers can provide only minimal assistance to humans in parsing and processing web data: browsers only see presentation information. We introduce RDFa, which provides a set of HTML attributes to augment visual data with machine-readable hints. We show how to express simple and more complex datasets using RDFa, and in particular how to turn the existing human-visible text and links into machine-readable data without repeating content. This document provides only a Primer to RDFa. The normative specification of RDFa can be found in the RDFa Syntax.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Note NOTE-xhtml-rdfa-primer-20081014</howpublished>
		<title type="sharef:primaryTitle">RDFa Primer — Bridging the Human and Data Webs</title>
		<field type="bibtex:topic">rdfa[0.8] xhtml[0.8]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2008/NOTE-xhtml-rdfa-primer-20081014</identifier>
	</reference>
	<reference name="rdfasyntax" src="bibtex:misc" src-info="bibtex:line-33680" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Ben</givenname>
				<surname>Adida</surname>
			</person>
			<person>
				<givenname>Mark</givenname>
				<surname>Birbeck</surname>
			</person>
			<person>
				<givenname>Shane</givenname>
				<surname>McCarron</surname>
			</person>
			<person>
				<givenname>Steven</givenname>
				<surname>Pemberton</surname>
			</person>
		</names>
		<date value="2008-10"/>
		<abstract>
			<richtext>
				<p>The current Web is primarily made up of an enormous number of documents that have been created using HTML. These documents contain significant amounts of structured data, which is largely unavailable to tools and applications. When publishers can express this data more completely, and when tools can read it, a new world of user functionality becomes available, letting users transfer structured data between applications and web sites, and allowing browsing applications to improve the user experience: an event on a web page can be directly imported into a user's desktop calendar; a license on a document can be detected so that users can be informed of their rights automatically; a photo's creator, camera setting information, resolution, location and topic can be published as easily as the original photo itself, enabling structured search and sharing. RDFa is a specification for attributes to express structured data in any markup language. This document specifies how to use RDFa with XHTML. The rendered, hypertext data of XHTML is reused by the RDFa markup, so that publishers don't need to repeat significant data in the document content. The underlying abstract representation is RDF, which lets publishers build their own vocabulary, extend others, and evolve their vocabulary with maximal interoperability over time. The expressed structure is closely tied to the data, so that rendered data can be copied and pasted along with its relevant structure. The rules for interpreting the data are generic, so that there is no need for different rules for different formats; this allows authors and publishers of data to define their own formats without having to update software, register formats via a central authority, or worry that two formats may interfere with each other. RDFa shares some use cases with microformats. Whereas microformats specify both a syntax for embedding structured data into HTML documents and a vocabulary of specific terms for each microformat, RDFa specifies only a syntax and relies on independent specification of terms (often called vocabularies or taxonomies) by others. RDFa allows terms from multiple independently-developed vocabularies to be freely intermixed and is designed such that the language can be parsed without knowledge of the specific term vocabulary being used. This document is a detailed syntax specification for RDFa, aimed at: those looking to create an RDFa parser, and who therefore need a detailed description of the parsing rules; those looking to recommend the use of RDFa within their organisation, and who would like to create some guidelines for their users; anyone familiar with RDF, and who wants to understand more about what is happening 'under the hood', when an RDFa parser runs. For those looking for an introduction to the use of RDFa and some real-world examples, please consult the RDFa Primer.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Recommendation REC-rdfa-syntax-20081014</howpublished>
		<title type="sharef:primaryTitle">RDFa in XHTML: Syntax and Processing — A Collection of Attributes and Processing Rules for Extending XHTML to Support RDF</title>
		<field type="bibtex:topic">rdfa[1] xhtml[0.8]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2008/REC-rdfa-syntax-20081014</identifier>
	</reference>
	<reference name="xhtmlrdfascenarios" src="bibtex:misc" src-info="bibtex:line-33691" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Ben</givenname>
				<surname>Adida</surname>
			</person>
			<person>
				<givenname>Michael</givenname>
				<surname>Hausenblas</surname>
			</person>
		</names>
		<date value="2007-03"/>
		<abstract>
			<richtext>
				<p>Current web pages, written in HTML, contain significant inherent structured data. When publishers can express this data more completely, and when tools can read it, a new world of user functionality becomes available, letting users transfer structured data between applications and web sites. An event on a web page can be directly imported into a user's desktop calendar. A license on a document can be detected so that the user is informed of his rights automatically. A photo's creator, camera setting information, resolution, and topic can be published as easily as the original photo itself, enabling structured search and sharing. RDFa is a syntax for expressing RDF structured data in HTML. This document provides use case scenarios for RDFa. An introduction to implementing RDFa is provided in the RDFa Primer, while the details of the syntax are explained in the RDFa Syntax (to be published).</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-xhtml-rdfa-scenarios-20070330</howpublished>
		<title type="sharef:primaryTitle">RDFa Use Cases: Scenarios for Embedding RDF in HTML</title>
		<field type="bibtex:topic">rdfa[0.8] html[0.8]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2007/WD-xhtml-rdfa-scenarios-20070330</identifier>
	</reference>
	<reference name="rdfacore" src="bibtex:misc" src-info="bibtex:line-33702" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Ben</givenname>
				<surname>Adida</surname>
			</person>
			<person>
				<givenname>Mark</givenname>
				<surname>Birbeck</surname>
			</person>
			<person>
				<givenname>Shane</givenname>
				<surname>McCarron</surname>
			</person>
			<person>
				<givenname>Ivan</givenname>
				<surname>Herman</surname>
			</person>
		</names>
		<date value="2011-03"/>
		<abstract>
			<richtext>
				<p>The current Web is primarily made up of an enormous number of documents that have been created using HTML. These documents contain significant amounts of structured data, which is largely unavailable to tools and applications. When publishers can express this data more completely, and when tools can read it, a new world of user functionality becomes available, letting users transfer structured data between applications and web sites, and allowing browsing applications to improve the user experience: an event on a web page can be directly imported into a user's desktop calendar; a license on a document can be detected so that users can be informed of their rights automatically; a photo's creator, camera setting information, resolution, location and topic can be published as easily as the original photo itself, enabling structured search and sharing. RDFa Core is a specification for attributes to express structured data in any markup language. The embedded data already available in the markup language (e.g., XHTML) can often be reused by the RDFa markup, so that publishers don't need to repeat significant data in the document content. The underlying abstract representation is RDF, which lets publishers build their own vocabulary, extend others, and evolve their vocabulary with maximal interoperability over time. The expressed structure is closely tied to the data, so that rendered data can be copied and pasted along with its relevant structure. The rules for interpreting the data are generic, so that there is no need for different rules for different formats; this allows authors and publishers of data to define their own formats without having to update software, register formats via a central authority, or worry that two formats may interfere with each other. RDFa shares some of the same goals with microformats. Whereas microformats specify both a syntax for embedding structured data into HTML documents and a vocabulary of specific terms for each microformat, RDFa specifies only a syntax and relies on independent specification of terms (often called vocabularies or taxonomies) by others. RDFa allows terms from multiple independently-developed vocabularies to be freely intermixed and is designed such that the language can be parsed without knowledge of the specific vocabulary being used. This document is a detailed syntax specification for RDFa, aimed at: those looking to create an RDFa Processor, and who therefore need a detailed description of the parsing rules; those looking to integrate RDFa into a new markup language; those looking to recommend the use of RDFa within their organization, and who would like to create some guidelines for their users; anyone familiar with RDF, and who wants to understand more about what is happening 'under the hood', when an RDFa Processor runs. For those looking for an introduction to the use of RDFa and some real-world examples, please consult the RDFa Primer.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-rdfa-core-20110331</howpublished>
		<title type="sharef:primaryTitle">RDFa Core 1.1: Syntax and Processing Rules for Embedding RDF through Attributes</title>
		<field type="bibtex:topic">rdfa[1]</field>
		<field type="bibtex:updates">rdfasyntax</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2011/WD-rdfa-core-20110331</identifier>
	</reference>
	<reference name="rdfainhtml" src="bibtex:misc" src-info="bibtex:line-33714" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Ben</givenname>
				<surname>Adida</surname>
			</person>
			<person>
				<givenname>Mark</givenname>
				<surname>Birbeck</surname>
			</person>
			<person>
				<givenname>Steven</givenname>
				<surname>Pemberton</surname>
			</person>
		</names>
		<names type="sharef:editor">
			<person>
				<givenname>Manu</givenname>
				<surname>Sporny</surname>
			</person>
			<person>
				<givenname>Shane</givenname>
				<surname>McCarron</surname>
			</person>
		</names>
		<date value="2011-04"/>
		<abstract>
			<richtext>
				<p>This specification defines rules and guidelines for adapting the RDFa Core 1.1 specification for use in HTML5 and XHTML5. The rules defined in this specification not only apply to HTML5 documents in non-XML and XML mode, but also to HTML4 and XHTML documents interpreted through the HTML5 parsing rules.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-rdfa-in-html-20110405</howpublished>
		<title type="sharef:primaryTitle">HTML+RDFa: A Mechanism for Embedding RDF in HTML</title>
		<field type="bibtex:topic">rdfa[0.9] html[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2011/WD-rdfa-in-html-20110405</identifier>
	</reference>
	<reference name="microdata" src="bibtex:misc" src-info="bibtex:line-33726" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Ian</givenname>
				<surname>Hickson</surname>
			</person>
		</names>
		<date value="2011-04"/>
		<abstract>
			<richtext>
				<p>This specification defines the HTML microdata mechanism. This mechanism allows machine-readable data to be embedded in HTML documents in an easy-to-write manner, with an unambiguous parsing model. It is compatible with numerous other data formats including RDF and JSON.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-microdata-20110405</howpublished>
		<title type="sharef:primaryTitle">HTML Microdata</title>
		<field type="bibtex:topic">html[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2011/WD-microdata-20110405</identifier>
	</reference>
	<reference name="xhtmlrdfa" src="bibtex:misc" src-info="bibtex:line-33737" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Shane</givenname>
				<surname>McCarron</surname>
			</person>
		</names>
		<date value="2011-03"/>
		<abstract>
			<richtext>
				<p>RDFa Core 1.1 defines attributes and syntax for embedding semantic markup in Host Languages. This document defines one such Host Language. This language is a superset of XHTML 1.1, integrating the attributes as defined in RDFa Core 1.1. This document is intended for authors who want to create XHTML-Family documents that embed rich semantic markup.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-xhtml-rdfa-20110331</howpublished>
		<title type="sharef:primaryTitle">XHTML+RDFa 1.1: Support for RDFa via XHTML Modularization</title>
		<field type="bibtex:topic">rdfa[0.9] xhtml[0.9]</field>
		<field type="bibtex:updates">rdfasyntax</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2011/WD-xhtml-rdfa-20110331</identifier>
	</reference>
	<reference name="roleattribute" src="bibtex:misc" src-info="bibtex:line-33749" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Ben</givenname>
				<surname>Adida</surname>
			</person>
			<person>
				<givenname>Mark</givenname>
				<surname>Birbeck</surname>
			</person>
			<person>
				<givenname>T. V.</givenname>
				<surname>Raman</surname>
			</person>
			<person>
				<givenname>Richard</givenname>
				<surname>Schwerdtfeger</surname>
			</person>
		</names>
		<date value="2011-01"/>
		<abstract>
			<richtext>
				<p>The Role Attribute defined in this specification allows the author to annotate markup languages with machine-extractable semantic information about the purpose of an element. Use cases include accessibility, device adaptation, server-side processing, and complex data description. This attribute can be integrated into any markup language. In particular, schema implementations are provided to facilitate with languages based upon XHTML Modularization.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-role-attribute-20110113</howpublished>
		<title type="sharef:primaryTitle">Role Attribute 1.0</title>
		<field type="bibtex:topic">rdfa[0.9] xhtml[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2011/WD-role-attribute-20110113</identifier>
	</reference>
	<reference name="rdfaapi" src="bibtex:misc" src-info="bibtex:line-33760" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Manu</givenname>
				<surname>Sporny</surname>
			</person>
			<person>
				<givenname>Benjamin</givenname>
				<surname>Adrian</surname>
			</person>
			<person>
				<givenname>Mark</givenname>
				<surname>Birbeck</surname>
			</person>
		</names>
		<date value="2010-09"/>
		<abstract>
			<richtext>
				<p>RDFa enables authors to publish structured information that is both human- and machine-readable. Concepts that have traditionally been difficult for machines to detect, like people, places, events, music, movies, and recipes, are now easily marked up in Web documents. While publishing this data is vital to the growth of Linked Data, using the information to improve the collective utility of the Web for humankind is the true goal. To accomplish this goal, it must be simple for Web developers to extract and utilize structured information from a Web document. This document details such a mechanism; an RDFa Application Programming Interface (RDFa API) that allows simple extraction and usage of structured information from a Web document.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-rdfa-api-20100923</howpublished>
		<title type="sharef:primaryTitle">RDFa API</title>
		<field type="bibtex:topic">rdfa[0.9] dom[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2010/WD-rdfa-api-20100923</identifier>
	</reference>
	<reference name="rdf" src="bibtex:misc" src-info="bibtex:line-33771" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Ora</givenname>
				<surname>Lassila</surname>
			</person>
			<person>
				<givenname>Ralph R.</givenname>
				<surname>Swick</surname>
			</person>
		</names>
		<date value="1999-02"/>
		<howpublished>World Wide Web Consortium, Recommendation REC-rdf-syntax-19990222</howpublished>
		<title type="sharef:primaryTitle">Resource Description Framework (RDF) Model and Syntax Specification</title>
		<field type="bibtex:topic">rdf[1]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/1999/REC-rdf-syntax-19990222</identifier>
	</reference>
	<reference name="rdfprimer" src="bibtex:misc" src-info="bibtex:line-33781" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Frank</givenname>
				<surname>Manola</surname>
			</person>
			<person>
				<givenname>Eric</givenname>
				<surname>Miller</surname>
			</person>
		</names>
		<date value="2004-02"/>
		<abstract>
			<richtext>
				<p>The Resource Description Framework (RDF) is a language for representing information about resources in the World Wide Web. This Primer is designed to provide the reader with the basic knowledge required to effectively use RDF. It introduces the basic concepts of RDF and describes its XML syntax. It describes how to define RDF vocabularies using the RDF Vocabulary Description Language, and gives an overview of some deployed RDF applications. It also describes the content and purpose of other RDF specification documents.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Recommendation REC-rdf-primer-20040210</howpublished>
		<title type="sharef:primaryTitle">RDF Primer</title>
		<field type="bibtex:topic">rdf[0.9]</field>
		<field type="bibtex:updates">rdf</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2004/REC-rdf-primer-20040210</identifier>
	</reference>
	<reference name="rdfconcepts" src="bibtex:misc" src-info="bibtex:line-33793" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Graham</givenname>
				<surname>Klyne</surname>
			</person>
			<person>
				<givenname>Jeremy J.</givenname>
				<surname>Carroll</surname>
			</person>
		</names>
		<date value="2004-02"/>
		<abstract>
			<richtext>
				<p>The Resource Description Framework (RDF) is a framework for representing information in the Web. RDF Concepts and Abstract Syntax defines an abstract syntax on which RDF is based, and which serves to link its concrete syntax to its formal semantics. It also includes discussion of design goals, key concepts, datatyping, character normalization and handling of URI references.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Recommendation REC-rdf-concepts-20040210</howpublished>
		<title type="sharef:primaryTitle">Resource Description Framework (RDF): Concepts and Abstract Syntax</title>
		<field type="bibtex:topic">rdf[1]</field>
		<field type="bibtex:updates">rdf</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2004/REC-rdf-concepts-20040210</identifier>
	</reference>
	<reference name="refacrdf" src="bibtex:misc" src-info="bibtex:line-33805" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Dave</givenname>
				<surname>Beckett</surname>
			</person>
		</names>
		<date value="2004-02"/>
		<abstract>
			<richtext>
				<p>The Resource Description Framework (RDF) is a general-purpose language for representing information in the Web. This document defines an XML syntax for RDF called RDF/XML in terms of Namespaces in XML, the XML Information Set and XML Base. The formal grammar for the syntax is annotated with actions generating triples of the RDF graph as defined in RDF Concepts and Abstract Syntax. The triples are written using the N-Triples RDF graph serializing format which enables more precise recording of the mapping in a machine processable form. The mappings are recorded as tests cases, gathered and published in RDF Test Cases.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Recommendation REC-rdf-syntax-grammar-20040210</howpublished>
		<title type="sharef:primaryTitle">RDF/XML Syntax Specification (Revised)</title>
		<field type="bibtex:topic">rdf[0.9] rdfxml[1]</field>
		<field type="bibtex:updates">rdf</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2004/REC-rdf-syntax-grammar-20040210</identifier>
	</reference>
	<reference name="rdfsch" src="bibtex:misc" src-info="bibtex:line-33817" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Dan</givenname>
				<surname>Brickley</surname>
			</person>
			<person>
				<givenname>Ramanathan V.</givenname>
				<surname>Guha</surname>
			</person>
		</names>
		<date value="2004-02"/>
		<abstract>
			<richtext>
				<p>The Resource Description Framework (RDF) is a general-purpose language for representing information in the Web. This specification describes how to use RDF to describe RDF vocabularies. This specification defines a vocabulary for this purpose and defines other built-in RDF vocabulary initially specified in the RDF Model and Syntax Specification.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Recommendation REC-rdf-schema-20040210</howpublished>
		<title type="sharef:primaryTitle">RDF Vocabulary Description Language 1.0: RDF Schema</title>
		<field type="bibtex:topic">rdf[1]</field>
		<field type="bibtex:updates">rdf</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2004/REC-rdf-schema-20040210</identifier>
	</reference>
	<reference name="rdftheory" src="bibtex:misc" src-info="bibtex:line-33829" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Patrick</givenname>
				<surname>Hayes</surname>
			</person>
		</names>
		<date value="2004-02"/>
		<abstract>
			<richtext>
				<p>This is a specification of a precise semantics, and corresponding complete systems of inference rules, for the Resource Description Framework (RDF) and RDF Schema (RDFS).</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Recommendation REC-rdf-mt-20040210</howpublished>
		<title type="sharef:primaryTitle">RDF Semantics</title>
		<field type="bibtex:topic">rdf[0.9] rdfs[0.9]</field>
		<field type="bibtex:updates">rdf</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2004/REC-rdf-mt-20040210</identifier>
	</reference>
	<reference name="rdftest" src="bibtex:misc" src-info="bibtex:line-33841" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Jan</givenname>
				<surname>Grant</surname>
			</person>
			<person>
				<givenname>Dave</givenname>
				<surname>Beckett</surname>
			</person>
		</names>
		<date value="2004-02"/>
		<howpublished>World Wide Web Consortium, Recommendation REC-rdf-testcases-20040210</howpublished>
		<title type="sharef:primaryTitle">RDF Test Cases</title>
		<field type="bibtex:topic">rdf[0.9]</field>
		<field type="bibtex:updates">rdf</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2004/REC-rdf-testcases-20040210</identifier>
	</reference>
	<reference name="rdfdawguc" src="bibtex:misc" src-info="bibtex:line-33852" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Kendall Grant</givenname>
				<surname>Clark</surname>
			</person>
		</names>
		<date value="2005-03"/>
		<abstract>
			<richtext>
				<p>This document specifies use cases, requirements, and objectives for an RDF query language and data access protocol. It suggests how an RDF query language and data access protocol could be used in the construction of novel, useful Semantic Web applications in areas like web publishing, personal information management, transportation, and tourism.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-rdf-dawg-uc-20050325</howpublished>
		<title type="sharef:primaryTitle">RDF Data Access Use Cases and Requirements</title>
		<field type="bibtex:topic">rdf[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2005/WD-rdf-dawg-uc-20050325</identifier>
	</reference>
	<reference name="rdb2rdfucr" src="bibtex:misc" src-info="bibtex:line-33863" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Eric</givenname>
				<surname>Prud'hommeaux</surname>
			</person>
			<person>
				<givenname>Michael</givenname>
				<surname>Hausenblas</surname>
			</person>
		</names>
		<date value="2010-06"/>
		<abstract>
			<richtext>
				<p>The need to share data with collaborators motivates custodians and users of relational databases (RDB) to expose relational data on the Web of Data. This document examines a set of use cases from science and industry, taking relational data and exposing it in patterns conforming to shared RDF schemata. These use cases expose a set of functional requirements for exposing relational data as RDF in the RDB2RDF Mapping Language (R2RML).</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-rdb2rdf-ucr-20100608</howpublished>
		<title type="sharef:primaryTitle">Use Cases and Requirements for Mapping Relational Databases to RDF</title>
		<field type="bibtex:topic">rdf[0.8] rdbms[0.8] r2rml[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2010/WD-rdb2rdf-ucr-20100608</identifier>
	</reference>
	<reference name="r2rml" src="bibtex:misc" src-info="bibtex:line-33874" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Souripriya</givenname>
				<surname>Das</surname>
			</person>
			<person>
				<givenname>Seema</givenname>
				<surname>Sundara</surname>
			</person>
			<person>
				<givenname>Richard</givenname>
				<surname>Cyganiak</surname>
			</person>
		</names>
		<date value="2011-03"/>
		<abstract>
			<richtext>
				<p>This document describes R2RML, a language for expressing customized mappings from relational databases to RDF datasets. Such mappings provide the ability to view existing relational data in the RDF data model, expressed in a structure and target vocabulary of the mapping author's choice. R2RML mappings are themselves RDF graphs and written down in Turtle syntax. R2RML enables different types of mapping implementations: processors could, for example, offer a virtual SPARQL endpoint over the mapped relational data, or generate RDF dumps, or offer a Linked Data interface.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-r2rml-20110324</howpublished>
		<title type="sharef:primaryTitle">R2RML: RDB to RDF Mapping Language</title>
		<field type="bibtex:topic">rdf[0.8] rdbms[0.8] r2rml[1]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2011/WD-r2rml-20110324</identifier>
	</reference>
	<reference name="rdbdirectmapping" src="bibtex:misc" src-info="bibtex:line-33885" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Marcelo</givenname>
				<surname>Arenas</surname>
			</person>
			<person>
				<givenname>Eric</givenname>
				<surname>Prud'hommeaux</surname>
			</person>
			<person>
				<givenname>Juan</givenname>
				<surname>Sequeda</surname>
			</person>
		</names>
		<date value="2011-03"/>
		<abstract>
			<richtext>
				<p>The need to share data with collaborators motivates custodians and users of relational databases (RDB) to expose relational data on the Web of Data. This document defines a direct mapping from relational data to RDF. This definition provides extension points for refinements within and outside of this document.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-rdb-direct-mapping-20110324</howpublished>
		<title type="sharef:primaryTitle">A Direct Mapping of Relational Data to RDF</title>
		<field type="bibtex:topic">rdf[0.8] rdbms[0.8]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2011/WD-rdb-direct-mapping-20110324</identifier>
	</reference>
	<reference name="cooluris" src="bibtex:misc" src-info="bibtex:line-33896" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Leo</givenname>
				<surname>Sauermann</surname>
			</person>
			<person>
				<givenname>Richard</givenname>
				<surname>Cyganiak</surname>
			</person>
		</names>
		<date value="2008-12"/>
		<abstract>
			<richtext>
				<p>The Resource Description Framework RDF allows users to describe both Web documents and concepts from the real world — people, organisations, topics, things — in a computer-processable way. Publishing such descriptions on the Web creates the Semantic Web. URIs (Uniform Resource Identifiers) are very important, providing both the core of the framework itself and the link between RDF and the Web. This document presents guidelines for their effective use. It discusses two strategies, called 303 URIs and hash URIs. It gives pointers to several Web sites that use these solutions, and briefly discusses why several other proposals have problems.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Note NOTE-cooluris-20081203</howpublished>
		<title type="sharef:primaryTitle">Cool URIs for the Semantic Web</title>
		<field type="bibtex:topic">uri[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2008/NOTE-cooluris-20081203</identifier>
	</reference>
	<reference name="void" src="bibtex:misc" src-info="bibtex:line-33907" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Keith</givenname>
				<surname>Alexander</surname>
			</person>
			<person>
				<givenname>Richard</givenname>
				<surname>Cyganiak</surname>
			</person>
			<person>
				<givenname>Michael</givenname>
				<surname>Hausenblas</surname>
			</person>
			<person>
				<givenname>Jun</givenname>
				<surname>Zhao</surname>
			</person>
		</names>
		<date value="2011-03"/>
		<abstract>
			<richtext>
				<p>VoID is an RDF Schema vocabulary for expressing metadata about RDF datasets. It is intended as a bridge between the publishers and users of RDF data, with applications ranging from data discovery to cataloging and archiving of datasets. This document is a detailed guide to the VoID vocabulary. It describes how VoID can be used to express general metadata based on Dublin Core, access metadata, structural metadata, and links between datasets. It also provides deployment advice and discusses the discovery of VoID descriptions.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Note NOTE-void-20110303</howpublished>
		<title type="sharef:primaryTitle">Describing Linked Datasets with the VoID Vocabulary</title>
		<field type="bibtex:topic">void[1]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2011/NOTE-void-20110303</identifier>
	</reference>
	<reference name="charreq" src="bibtex:misc" src-info="bibtex:line-33918" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Martin J.</givenname>
				<surname>Dürst</surname>
			</person>
		</names>
		<date value="2009-09"/>
		<abstract>
			<richtext>
				<p>This document describes requirements for some important aspects of the character model for W3C specifications. The two aspects discussed are string identity matching and string indexing. Both aspects are considered to be vital for the seamless interaction of many components of the current and future web architecture.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Note NOTE-charreq-20090915</howpublished>
		<title type="sharef:primaryTitle">Requirements for String Identity Matching and String Indexing</title>
		<identifier type="sharef:uri">http://www.w3.org/TR/2009/NOTE-charreq-20090915</identifier>
	</reference>
	<reference name="urispace" src="bibtex:misc" src-info="bibtex:line-33928" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Mark</givenname>
				<surname>Nottingham</surname>
			</person>
		</names>
		<date value="2001-02"/>
		<abstract>
			<richtext>
				<p>URISpace provides a flexible mechanism for assigning metadata to a group of resources, based on the namespace described by their URIs.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Note NOTE-urispace-20010215</howpublished>
		<title type="sharef:primaryTitle">URISpace 1.0</title>
		<field type="bibtex:topic">uri[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2001/NOTE-urispace-20010215</identifier>
	</reference>
	<reference name="skosucr" src="bibtex:misc" src-info="bibtex:line-33939" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Antoine</givenname>
				<surname>Isaac</surname>
			</person>
			<person>
				<givenname>Jon</givenname>
				<surname>Phipps</surname>
			</person>
			<person>
				<givenname>Daniel</givenname>
				<surname>Rubin</surname>
			</person>
		</names>
		<date value="2009-08"/>
		<abstract>
			<richtext>
				<p>Knowledge organization systems, such as taxonomies, thesauri or subject heading lists, play a fundamental role in information structuring and access. The Semantic Web Deployment Working Group aims at providing a model for representing such vocabularies on the Semantic Web: SKOS (Simple Knowledge Organization System). This document presents the preparatory work for the 2009 version of SKOS. It lists representative use cases, which were obtained after a dedicated questionnaire was sent to a wide audience. It also features a set of fundamental or secondary requirements derived from these use cases, that have been used to guide the design of SKOS. This document is a companion to the SKOS Reference and the SKOS Primer, which respectively provide the normative reference on SKOS and a user guide for those who would like to represent their concept scheme using SKOS.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Note NOTE-skos-ucr-20090818</howpublished>
		<title type="sharef:primaryTitle">SKOS Use Cases and Requirements</title>
		<field type="bibtex:topic">skos[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2009/NOTE-skos-ucr-20090818</identifier>
	</reference>
	<reference name="sparqlquery" src="bibtex:misc" src-info="bibtex:line-33950" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Eric</givenname>
				<surname>Prud'Hommeaux</surname>
			</person>
			<person>
				<givenname>Andy</givenname>
				<surname>Seaborne</surname>
			</person>
		</names>
		<date value="2008-01"/>
		<abstract>
			<richtext>
				<p>RDF is a directed, labeled graph data format for representing information in the Web. This specification defines the syntax and semantics of the SPARQL query language for RDF. SPARQL can be used to express queries across diverse data sources, whether the data is stored natively as RDF or viewed as RDF via middleware. SPARQL contains capabilities for querying required and optional graph patterns along with their conjunctions and disjunctions. SPARQL also supports extensible value testing and constraining queries by source RDF graph. The results of SPARQL queries can be results sets or RDF graphs.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Recommendation REC-rdf-sparql-query-20080115</howpublished>
		<title type="sharef:primaryTitle">SPARQL Query Language for RDF</title>
		<field type="bibtex:topic">sparql[1] rdf[0.8]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2008/REC-rdf-sparql-query-20080115</identifier>
	</reference>
	<reference name="sparql11query" src="bibtex:misc" src-info="bibtex:line-33961" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Steve</givenname>
				<surname>Harris</surname>
			</person>
			<person>
				<givenname>Andy</givenname>
				<surname>Seaborne</surname>
			</person>
		</names>
		<date value="2010-10"/>
		<abstract>
			<richtext>
				<p>RDF is a directed, labeled graph data format for representing information in the Web. This specification defines the syntax and semantics of the SPARQL query language for RDF. SPARQL can be used to express queries across diverse data sources, whether the data is stored natively as RDF or viewed as RDF via middleware. SPARQL contains capabilities for querying required and optional graph patterns along with their conjunctions and disjunctions. SPARQL also supports aggregation, subqueries, creating values by complex expressions, extensible value testing, and constraining queries by source RDF graph. The results of SPARQL queries can be results sets or RDF graphs.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-sparql11-query-20101014</howpublished>
		<title type="sharef:primaryTitle">SPARQL 1.1 Query Language</title>
		<field type="bibtex:topic">sparql[1] rdf[0.8]</field>
		<field type="bibtex:updates">sparqlquery</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2010/WD-sparql11-query-20101014</identifier>
	</reference>
	<reference name="sparql11servicedescription" src="bibtex:misc" src-info="bibtex:line-33973" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Gregory Todd</givenname>
				<surname>Williams</surname>
			</person>
		</names>
		<date value="2010-10"/>
		<abstract>
			<richtext>
				<p>This document describes SPARQL Service Description, a method for discovering and vocabulary for describing SPARQL services made available via the SPARQL Protocol for RDF. Such a description is intended to provide a mechanism by which a client or end user can discover information about the SPARQL implementation/service such as supported extension functions and details about the available dataset.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-sparql11-service-description-20101014</howpublished>
		<title type="sharef:primaryTitle">SPARQL 1.1 Service Description</title>
		<field type="bibtex:topic">sparql[1]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2010/WD-sparql11-service-description-20101014</identifier>
	</reference>
	<reference name="sparql11update" src="bibtex:misc" src-info="bibtex:line-33984" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Simon</givenname>
				<surname>Schenk</surname>
			</person>
			<person>
				<givenname>Paul</givenname>
				<surname>Gearon</surname>
			</person>
			<person>
				<givenname>Alexandre</givenname>
				<surname>Passant</surname>
			</person>
		</names>
		<date value="2010-10"/>
		<abstract>
			<richtext>
				<p>This document describes SPARQL 1.1 Update, an update language for RDF graphs. It uses a syntax derived from the SPARQL Query Language for RDF. Update operations are performed on a collection of graphs in a Graph Store. Operations are provided to change existing RDF graphs as well as create and remove graphs in the Graph Store.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-sparql11-update-20101014</howpublished>
		<title type="sharef:primaryTitle">SPARQL 1.1 Update</title>
		<field type="bibtex:topic">sparql[1] rdf[0.8]</field>
		<field type="bibtex:updates">sparqlquery</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2010/WD-sparql11-update-20101014</identifier>
	</reference>
	<reference name="sparql11httprdfupdate" src="bibtex:misc" src-info="bibtex:line-33996" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Chimezie</givenname>
				<surname>Ogbuji</surname>
			</person>
		</names>
		<date value="2010-10"/>
		<abstract>
			<richtext>
				<p>SPARQL provides a standard way to query RDF data. The SPARQL Update allows a user to update RDF graphs in a Graph Store at various levels of granularity, including individual RDF statements. The protocol described here is meant to provide a minimal set of uniform, colloquial HTTP operations for managing a semantic web of mutable, named RDF graphs at a strictly large level of granularity.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-sparql11-http-rdf-update-20101014</howpublished>
		<title type="sharef:primaryTitle">SPARQL 1.1 Uniform HTTP Protocol for Managing RDF Graphs</title>
		<field type="bibtex:topic">sparql[1] rdf[0.8] http[0.8]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2010/WD-sparql11-http-rdf-update-20101014</identifier>
	</reference>
	<reference name="sparqljson" src="bibtex:misc" src-info="bibtex:line-34007" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Kendall Grant</givenname>
				<surname>Clark</surname>
			</person>
			<person>
				<givenname>Lee</givenname>
				<surname>Feigenbaum</surname>
			</person>
			<person>
				<givenname>Elias</givenname>
				<surname>Torres</surname>
			</person>
		</names>
		<date value="2007-06"/>
		<abstract>
			<richtext>
				<p>SPARQL is a query language and a protocol for RDF developed by the W3C's RDF Data Access Working Group. Included in that work is an XML vocabulary for serializing the results of two SPARQL query forms, SELECT and ASK. This document defines an alternative means of serializing the results of those SPARQL query forms using JSON, a lightweight representation format which emphasizes concision and legibility.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Note NOTE-rdf-sparql-json-res-20070618</howpublished>
		<title type="sharef:primaryTitle">Serializing SPARQL Query Results in JSON</title>
		<field type="bibtex:topic">sparql[0.9] json[0.8]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2007/NOTE-rdf-sparql-json-res-20070618</identifier>
	</reference>
	<reference name="sparqlxmlres" src="bibtex:misc" src-info="bibtex:line-34018" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Dave</givenname>
				<surname>Beckett</surname>
			</person>
			<person>
				<givenname>Jeen</givenname>
				<surname>Broekstra</surname>
			</person>
		</names>
		<date value="2008-01"/>
		<abstract>
			<richtext>
				<p>RDF is a flexible, extensible way to represent information about World Wide Web resources. It is used to represent, among other things, personal information, social networks, metadata about digital artifacts like music and images, as well as provide a means of integration over disparate sources of information. A standardized query language for RDF data with multiple implementations offers developers and end users a way to write and to consume the results of queries across this wide range of information. This document describes an XML format for the variable binding results format provided by the SPARQL query language for RDF, developed by the W3C RDF Data Access Working Group (DAWG), part of the Semantic Web Activity as described in the activity statement.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Recommendation REC-rdf-sparql-XMLres-20080115</howpublished>
		<title type="sharef:primaryTitle">SPARQL Query Results XML Format</title>
		<field type="bibtex:topic">sparql[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2008/REC-rdf-sparql-XMLres-20080115</identifier>
	</reference>
	<reference name="sparqlprotocol" src="bibtex:misc" src-info="bibtex:line-34029" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Kendall Grant</givenname>
				<surname>Clark</surname>
			</person>
			<person>
				<givenname>Lee</givenname>
				<surname>Feigenbaum</surname>
			</person>
			<person>
				<givenname>Elias</givenname>
				<surname>Torres</surname>
			</person>
		</names>
		<date value="2008-01"/>
		<abstract>
			<richtext>
				<p>The SPARQL Protocol and RDF Query Language (SPARQL) is a query language and protocol for RDF. This document specifies the SPARQL Protocol; it uses WSDL 2.0 to describe a means for conveying SPARQL queries to an SPARQL query processing service and returning the query results to the entity that requested them. This protocol was developed by the W3C RDF Data Access Working Group (DAWG), part of the Semantic Web Activity as described in the activity statement.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Recommendation REC-rdf-sparql-protocol-20080115</howpublished>
		<title type="sharef:primaryTitle">SPARQL Protocol for RDF</title>
		<field type="bibtex:topic">sparql[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2008/REC-rdf-sparql-protocol-20080115</identifier>
	</reference>
	<reference name="sparql11protocol" src="bibtex:misc" src-info="bibtex:line-34040" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>David</givenname>
				<surname>Charboneau</surname>
			</person>
			<person>
				<givenname>Lee</givenname>
				<surname>Feigenbaum</surname>
			</person>
		</names>
		<date value="2010-01"/>
		<abstract>
			<richtext>
				<p>The SPARQL Protocol and RDF Query Language (SPARQL) is a query language and protocol for RDF. This document specifies the SPARQL Protocol; it uses WSDL 2.0 to describe a means for conveying SPARQL queries to an SPARQL query processing service and returning the query results to the entity that requested them. This protocol was developed by the W3C SPARQL Working Group, part of the Semantic Web Activity as described in the activity statement.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-sparql11-protocol-20100126</howpublished>
		<title type="sharef:primaryTitle">SPARQL 1.1 Protocol for RDF</title>
		<field type="bibtex:topic">sparql[0.9]</field>
		<field type="bibtex:updates">sparqlprotocol</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2010/WD-sparql11-protocol-20100126</identifier>
	</reference>
	<reference name="sparql11propertypaths" src="bibtex:misc" src-info="bibtex:line-34052" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Andy</givenname>
				<surname>Seaborne</surname>
			</person>
		</names>
		<date value="2010-01"/>
		<abstract>
			<richtext>
				<p>This document describes SPARQL Property Paths. Property Paths give a more succinct way to write parts of basic graph patterns and also extend matching of triple pattern to arbitrary length paths. Property paths do not invalidate or change any existing SPARQL query. Property paths are a time-permitting feature.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-sparql11-property-paths-20100126</howpublished>
		<title type="sharef:primaryTitle">SPARQL 1.1 Property Paths</title>
		<field type="bibtex:topic">sparql[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2010/WD-sparql11-property-paths-20100126</identifier>
	</reference>
	<reference name="sprot11" src="bibtex:misc" src-info="bibtex:line-34063" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Lee</givenname>
				<surname>Feigenbaum</surname>
			</person>
			<person>
				<givenname>Andy</givenname>
				<surname>Seaborne</surname>
			</person>
			<person>
				<givenname>Elias</givenname>
				<surname>Torres</surname>
			</person>
		</names>
		<date value="2005-10"/>
		<abstract>
			<richtext>
				<p>The RDF Data Access Working Group normatively defines the SPARQL Protocol for RDF via a Web Services Description Language version 2.0 (WSDL 2.0) definition. This document presents a non-normative WSDL 1.1 document defining the same protocol.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-sprot11-20051024</howpublished>
		<title type="sharef:primaryTitle">SPARQL Protocol for RDF Using WSDL 1.1</title>
		<field type="bibtex:topic">sparql[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2005/WD-sprot11-20051024</identifier>
	</reference>
	<reference name="sparqlfeatures" src="bibtex:misc" src-info="bibtex:line-34074" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Kjetil</givenname>
				<surname>Kjernsmo</surname>
			</person>
			<person>
				<givenname>Alexandre</givenname>
				<surname>Passant</surname>
			</person>
		</names>
		<date value="2009-07"/>
		<abstract>
			<richtext>
				<p>SPARQL is a query language for RDF data on the Semantic Web with formally defined meaning. This document is a simple introduction to the new features of the language, including an explanation of its differences with respect to the previous SPARQL Query Language Recommendation. It also presents the requirements that have motivated the design of the main new features, and their rationale from a theoretical and implementation perspective.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-sparql-features-20090702</howpublished>
		<title type="sharef:primaryTitle">SPARQL New Features and Rationale</title>
		<field type="bibtex:topic">sparql[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2009/WD-sparql-features-20090702</identifier>
	</reference>
	<reference name="sparql11entailment" src="bibtex:misc" src-info="bibtex:line-34085" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Birte</givenname>
				<surname>Glimm</surname>
			</person>
			<person>
				<givenname>Chimezie</givenname>
				<surname>Ogbuji</surname>
			</person>
		</names>
		<date value="2010-10"/>
		<abstract>
			<richtext>
				<p>SPARQL is a query language for data that is stored natively as RDF or viewed as RDF via middleware. The main mechanism for computing query results in SPARQL is subgraph matching: RDF triples in both the queried RDF data and the query pattern are interpreted as nodes and edges of directed graphs, and the resulting query graph is matched to the data graph using variables as wild cards. Various W3C standards, including RDF and OWL, provide semantic interpretations for RDF graphs that allow additional RDF statements to be inferred from explicitly given assertions. It is desirable to utilize SPARQL as a query language in these cases as well, but this requires basic graph pattern matching to be defined using semantic entailment relations instead of explicitly given graph structures. Such extensions of the SPARQL semantics are called entailment regimes within this document and entailment regimes for standard entailment relations in the semantic web such as RDF entailment, RDFS entailment, etc. are defined in this document.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-sparql11-entailment-20101014</howpublished>
		<title type="sharef:primaryTitle">SPARQL 1.1 Entailment Regimes</title>
		<field type="bibtex:topic">sparql[1]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2010/WD-sparql11-entailment-20101014</identifier>
	</reference>
	<reference name="sparql11federatedquery" src="bibtex:misc" src-info="bibtex:line-34096" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Eric</givenname>
				<surname>Prud'hommeaux</surname>
			</person>
		</names>
		<date value="2010-06"/>
		<abstract>
			<richtext>
				<p>RDF is a directed, labeled graph data format for representing information in the Web. SPARQL can be used to express queries across diverse data sources, whether the data is stored natively as RDF or viewed as RDF via middleware. This specification defines the syntax and semantics of a SPARQL 1.1 Query extension to for executing distributed queries.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-sparql11-federated-query-20100601</howpublished>
		<title type="sharef:primaryTitle">SPARQL 1.1 Federation Extensions</title>
		<field type="bibtex:topic">sparql[1]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2010/WD-sparql11-federated-query-20100601</identifier>
	</reference>
	<reference name="rdfcal" src="bibtex:misc" src-info="bibtex:line-34107" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Dan</givenname>
				<surname>Connolly</surname>
			</person>
			<person>
				<givenname>Libby</givenname>
				<surname>Miller</surname>
			</person>
		</names>
		<date value="2005-09"/>
		<abstract>
			<richtext>
				<p>This report discusses an effort to apply the Resource Description Framework (RDF) to iCalendar data in order to integrate calendar data with other Semantic Web data such as social networking data, syndicated content, and multimedia meta-data. We demonstrate the effectiveness of a test-driven approach to vocabulary development and we discuss a number of social as well as technical issues.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Note NOTE-rdfcal-20050929</howpublished>
		<title type="sharef:primaryTitle">RDF Calendar — An Application of the Resource Description Framework to iCalendar Data</title>
		<field type="bibtex:topic">rdf[0.7] icalendar[0.8]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2005/NOTE-rdfcal-20050929</identifier>
	</reference>
	<reference name="hclskb" src="bibtex:misc" src-info="bibtex:line-34118" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>M. Scott</givenname>
				<surname>Marshall</surname>
			</person>
			<person>
				<givenname>Eric</givenname>
				<surname>Prud'hommeaux</surname>
			</person>
		</names>
		<date value="2008-06"/>
		<abstract>
			<richtext>
				<p>The prototype we describe is a biomedical knowledge base, constructed for a demonstration at Banff WWW2007 , that integrates 15 distinct data sources using currently available Semantic Web technologies such as the W3C standard Web Ontology Language and Resource Description Framework. This report outlines which resources were integrated, how the knowledge base was constructed using free and open source triple store technology, how it can be queried using the W3C Recommended RDF query language SPARQL, and what resources and inferences are involved in answering complex queries. While the utility of the knowledge base is illustrated by identifying a set of genes involved in Alzheimer's Disease, the approach described here can be applied to any use case that integrates data from multiple domains.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Note NOTE-hcls-kb-20080604</howpublished>
		<title type="sharef:primaryTitle">HCLS Knowledgebase</title>
		<identifier type="sharef:uri">http://www.w3.org/TR/2008/NOTE-hcls-kb-20080604</identifier>
	</reference>
	<reference name="hclsenselab" src="bibtex:misc" src-info="bibtex:line-34128" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Matthias</givenname>
				<surname>Samwald</surname>
			</person>
			<person>
				<givenname>Kei-Hoi</givenname>
				<surname>Cheung</surname>
			</person>
		</names>
		<date value="2008-06"/>
		<abstract>
			<richtext>
				<p>One of the challenges facing Semantic Web for Health Care and Life Sciences is that of converting relational databases into Semantic Web format. The issues and the steps involved in such a conversion have not been well documented. To this end, we have created this document to describe the process of converting SenseLab databases into OWL. SenseLab is a collection of relational (Oracle) databases for neuroscientific research. The conversion of these databases into RDF/OWL format is an important step towards realizing the benefits of Semantic Web in integrative neuroscience research. This document describes how we represented some of the SenseLab databases in Resource Description Framework (RDF) and Web Ontology Language (OWL), and discusses the advantages and disadvantages of these representations. Our OWL representation is based on the reuse and extension of existing standard OWL ontologies developed in the biomedical ontology communities. The purpose of this document is to share our implementation experience with the community.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Note NOTE-hcls-senselab-20080604</howpublished>
		<title type="sharef:primaryTitle">Experiences with the Conversion of SenseLab Databases to RDF/OWL</title>
		<identifier type="sharef:uri">http://www.w3.org/TR/2008/NOTE-hcls-senselab-20080604</identifier>
	</reference>
	<reference name="lbase" src="bibtex:misc" src-info="bibtex:line-34138" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Ramanathan V.</givenname>
				<surname>Guha</surname>
			</person>
			<person>
				<givenname>Patrick</givenname>
				<surname>Hayes</surname>
			</person>
		</names>
		<date value="2003-10"/>
		<abstract>
			<richtext>
				<p>This document presents a framework for specifying the semantics for the languages of the Semantic Web. Some of these languages (notably RDF and OWL) are currently in various stages of development and we expect others to be developed in the future. This framework is intended to provide a framework for specifying the semantics of all of these languages in a uniform and coherent way. The strategy is to translate the various languages into a common 'base' language thereby providing them with a single coherent model theory. We describe a mechanism for providing a precise semantics for the Semantic Web Languages (referred to as SWELs from now on). The purpose of this is to define clearly the consequences and allowed inferences from constructs in these languages.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Note NOTE-lbase-20031010</howpublished>
		<title type="sharef:primaryTitle">LBase: Semantics for Languages of the Semantic Web</title>
		<field type="bibtex:topic">rdf[0.7] owl[0.7]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2003/NOTE-lbase-20031010</identifier>
	</reference>
	<reference name="damloil" src="bibtex:misc" src-info="bibtex:line-34149" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Dan</givenname>
				<surname>Connolly</surname>
			</person>
			<person>
				<givenname>Frank</givenname>
				<surname link="van">Harmelen</surname>
			</person>
			<person>
				<givenname>Ian</givenname>
				<surname>Horrocks</surname>
			</person>
			<person>
				<givenname>Deborah L.</givenname>
				<surname>McGuinness</surname>
			</person>
			<person>
				<givenname>Peter F.</givenname>
				<surname>Patel-Schneider</surname>
			</person>
			<person>
				<givenname>Lynn Andrea</givenname>
				<surname>Stein</surname>
			</person>
		</names>
		<date value="2001-12"/>
		<howpublished>World Wide Web Consortium, Note NOTE-daml+oil-reference-20011218</howpublished>
		<title type="sharef:primaryTitle">DAML+OIL (March 2001) Reference Description</title>
		<field type="bibtex:topic">daml[1] oil[1]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2001/NOTE-daml+oil-reference-20011218</identifier>
	</reference>
	<reference name="rdfdamloilaxsem" src="bibtex:misc" src-info="bibtex:line-34159" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Richard</givenname>
				<surname>Fikes</surname>
			</person>
			<person>
				<givenname>Deborah L.</givenname>
				<surname>McGuinness</surname>
			</person>
		</names>
		<date value="2001-12"/>
		<abstract>
			<richtext>
				<p>This document provides an axiomatization for the Resource Description Framework (RDF), RDF Schema (RDF-S), and DAML+OIL by specifying a mapping of a set of descriptions in any one of these languages into a logical theory expressed in first-order predicate calculus. The basic claim of this paper is that the logical theory produced by the mapping specified herein of a set of such descriptions is logically equivalent to the intended meaning of that set of descriptions. Providing a means of translating RDF, RDF-S, and DAML+OIL descriptions into a first-order predicate calculus logical theory not only specifies the intended meaning of the descriptions, but also produces a representation of the descriptions from which inferences can automatically be made using traditional automatic theorem provers and problem solvers. For example, the DAML+OIL axioms enable a reasoner to infer from the two statements "Class Male and class Female are disjointWith." and "John is type Male." that the statement "John is type Female." is false. The mapping into predicate calculus consists of a simple rule for translating RDF statements into first-order relational sentences and a set of first-order logic axioms that restrict the allowable interpretations of the non-logical symbols (i.e., relations, functions, and constants) in each language. Since RDF Schema and DAML+OIL are both vocabularies of non-logical symbols added to RDF, the translation of RDF statements is sufficient for translating RDF Schema and DAML+OIL as well. The axioms are written in ANSI Knowledge Interchange Format (KIF)), which is a proposed ANSI standard. The axiomatic semantics are updated as daml+oil evolves and updated versions are available from http://www.ksl.stanford.edu/people/dlm/daml-semantics/abstract-axiomatic-semantics.html. In order to support additional operational usability of the document, we include two additional files: one containing all of the kif axioms and kif theorems in the document.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Note NOTE-daml+oil-axioms-20011218</howpublished>
		<title type="sharef:primaryTitle">An Axiomatic Semantics for RDF, RDF-S, and DAML+OIL (March 2001)</title>
		<field type="bibtex:topic">daml[1] oil[1] rdf[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2001/NOTE-daml+oil-axioms-20011218</identifier>
	</reference>
	<reference name="damloilmodsem" src="bibtex:misc" src-info="bibtex:line-34170" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Frank</givenname>
				<surname link="van">Harmelen</surname>
			</person>
			<person>
				<givenname>Ian</givenname>
				<surname>Horrocks</surname>
			</person>
			<person>
				<givenname>Peter F.</givenname>
				<surname>Patel-Schneider</surname>
			</person>
		</names>
		<date value="2001-12"/>
		<howpublished>World Wide Web Consortium, Note NOTE-daml+oil-model-20011218</howpublished>
		<title type="sharef:primaryTitle">A Model-Theoretic Semantics for DAML+OIL (March 2001)</title>
		<field type="bibtex:topic">daml[1] oil[1]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2001/NOTE-daml+oil-model-20011218</identifier>
	</reference>
	<reference name="damloilmarkup" src="bibtex:misc" src-info="bibtex:line-34180" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Dan</givenname>
				<surname>Connolly</surname>
			</person>
			<person>
				<givenname>Frank</givenname>
				<surname link="van">Harmelen</surname>
			</person>
			<person>
				<givenname>Ian</givenname>
				<surname>Horrocks</surname>
			</person>
			<person>
				<givenname>Deborah L.</givenname>
				<surname>McGuinness</surname>
			</person>
			<person>
				<givenname>Peter F.</givenname>
				<surname>Patel-Schneider</surname>
			</person>
			<person>
				<givenname>Lynn Andrea</givenname>
				<surname>Stein</surname>
			</person>
		</names>
		<date value="2001-12"/>
		<howpublished>World Wide Web Consortium, Note NOTE-daml+oil-walkthru-20011218</howpublished>
		<title type="sharef:primaryTitle">Annotated DAML+OIL Ontology Markup</title>
		<field type="bibtex:topic">daml[0.9] oil[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2001/NOTE-daml+oil-walkthru-20011218</identifier>
	</reference>
	<reference name="xmlschemareq" src="bibtex:misc" src-info="bibtex:line-34190" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Ashok</givenname>
				<surname>Malhotra</surname>
			</person>
			<person>
				<givenname>Murray</givenname>
				<surname>Maloney</surname>
			</person>
		</names>
		<date value="1999-02"/>
		<abstract>
			<richtext>
				<p>This document specifies the purpose, basic usage scenarios, design principles, and base requirements for an XML schema language.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Note NOTE-xml-schema-req</howpublished>
		<title type="sharef:primaryTitle">XML Schema Requirements</title>
		<field type="bibtex:topic">xsd[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/NOTE-xml-schema-req</identifier>
	</reference>
	<reference name="xmlsch0" src="bibtex:misc" src-info="bibtex:line-34201" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>David C.</givenname>
				<surname>Fallside</surname>
			</person>
		</names>
		<date value="2001-05"/>
		<howpublished>World Wide Web Consortium, Recommendation REC-xmlschema-0-20010502</howpublished>
		<title type="sharef:primaryTitle">XML Schema Part 0: Primer</title>
		<field type="bibtex:topic">xsd[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2001/REC-xmlschema-0-20010502</identifier>
	</reference>
	<reference name="xmlsch1" src="bibtex:misc" src-info="bibtex:line-34211" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Henry S.</givenname>
				<surname>Thompson</surname>
			</person>
			<person>
				<givenname>David</givenname>
				<surname>Beech</surname>
			</person>
			<person>
				<givenname>Murray</givenname>
				<surname>Maloney</surname>
			</person>
			<person>
				<givenname>Noah</givenname>
				<surname>Mendelsohn</surname>
			</person>
		</names>
		<date value="2001-05"/>
		<howpublished>World Wide Web Consortium, Recommendation REC-xmlschema-1-20010502</howpublished>
		<title type="sharef:primaryTitle">XML Schema Part 1: Structures</title>
		<field type="bibtex:topic">xsd[1]</field>
		<field type="bibtex:updates">xmlschemareq</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2001/REC-xmlschema-1-20010502</identifier>
	</reference>
	<reference name="xmlsch2" src="bibtex:misc" src-info="bibtex:line-34222" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Paul V.</givenname>
				<surname>Biron</surname>
			</person>
			<person>
				<givenname>Ashok</givenname>
				<surname>Malhotra</surname>
			</person>
		</names>
		<date value="2001-05"/>
		<howpublished>World Wide Web Consortium, Recommendation REC-xmlschema-2-20010502</howpublished>
		<title type="sharef:primaryTitle">XML Schema Part 2: Datatypes</title>
		<field type="bibtex:topic">xsd[1]</field>
		<field type="bibtex:updates">xmlschemareq</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2001/REC-xmlschema-2-20010502</identifier>
	</reference>
	<reference name="xmlschema0sec" src="bibtex:misc" src-info="bibtex:line-34233" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>David C.</givenname>
				<surname>Fallside</surname>
			</person>
			<person>
				<givenname>Priscilla</givenname>
				<surname>Walmsley</surname>
			</person>
		</names>
		<date value="2004-10"/>
		<abstract>
			<richtext>
				<p>XML Schema Part 0: Primer is a non-normative document intended to provide an easily readable description of the XML Schema facilities, and is oriented towards quickly understanding how to create schemas using the XML Schema language. XML Schema Part 1: Structures and XML Schema Part 2: Datatypes provide the complete normative description of the XML Schema language. This primer describes the language features through numerous examples which are complemented by extensive references to the normative texts.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Recommendation REC-xmlschema-0-20041028</howpublished>
		<title type="sharef:primaryTitle">XML Schema Part 0: Primer Second Edition</title>
		<field type="bibtex:topic">xsd[0.9]</field>
		<field type="bibtex:updates">xmlsch0</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2004/REC-xmlschema-0-20041028</identifier>
	</reference>
	<reference name="xmlschema1sec" src="bibtex:misc" src-info="bibtex:line-34245" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Henry S.</givenname>
				<surname>Thompson</surname>
			</person>
			<person>
				<givenname>David</givenname>
				<surname>Beech</surname>
			</person>
			<person>
				<givenname>Murray</givenname>
				<surname>Maloney</surname>
			</person>
			<person>
				<givenname>Noah</givenname>
				<surname>Mendelsohn</surname>
			</person>
		</names>
		<date value="2004-10"/>
		<abstract>
			<richtext>
				<p>XML Schema: Structures specifies the XML Schema definition language, which offers facilities for describing the structure and constraining the contents of XML 1.0 documents, including those which exploit the XML Namespace facility. The schema language, which is itself represented in XML 1.0 and uses namespaces, substantially reconstructs and considerably extends the capabilities found in XML 1.0 document type definitions (DTDs). This specification depends on XML Schema Part 2: Datatypes.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Recommendation REC-xmlschema-1-20041028</howpublished>
		<title type="sharef:primaryTitle">XML Schema Part 1: Structures Second Edition</title>
		<field type="bibtex:topic">xsd[1]</field>
		<field type="bibtex:updates">xmlsch1</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2004/REC-xmlschema-1-20041028</identifier>
	</reference>
	<reference name="xmlschema2sec" src="bibtex:misc" src-info="bibtex:line-34257" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Paul V.</givenname>
				<surname>Biron</surname>
			</person>
			<person>
				<givenname>Ashok</givenname>
				<surname>Malhotra</surname>
			</person>
		</names>
		<date value="2004-10"/>
		<abstract>
			<richtext>
				<p>XML Schema: Datatypes is part 2 of the specification of the XML Schema language. It defines facilities for defining datatypes to be used in XML Schemas as well as other XML specifications. The datatype language, which is itself represented in XML 1.0, provides a superset of the capabilities found in XML 1.0 document type definitions (DTDs) for specifying datatypes on elements and attributes.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Recommendation REC-xmlschema-2-20041028</howpublished>
		<title type="sharef:primaryTitle">XML Schema Part 2: Datatypes Second Edition</title>
		<field type="bibtex:topic">xsd[1]</field>
		<field type="bibtex:updates">xmlsch2</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2004/REC-xmlschema-2-20041028</identifier>
	</reference>
	<reference name="xml11schema10" src="bibtex:misc" src-info="bibtex:line-34269" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Henry S.</givenname>
				<surname>Thompson</surname>
			</person>
		</names>
		<date value="2005-05"/>
		<abstract>
			<richtext>
				<p>XML Schema 1.0 did not anticipate new versions of XML, and mandated XML 1.0 documents as the starting point for schema-validity assessment. Some users and specifications would like to use XML Schema processors which process XML 1.1 documents, and some implementors of XML Schema processors would like to provide XML 1.1 support. This Note suggests an implementation strategy for implementors to adopt to enable users and specifications to get such support in a consistent way. All aspects of XML Schema which are liable to re-interpretation as a result of changes in XML 1.1 are discussed. An implementation of schema-validity assessment employing such a strategy is strictly speaking non-conformant to the current version of the XML Schema specification. The XML Schema WG none-the-less believes that interoperability will best be served by such non-conformant processors being made available to users, until such time as a subsequent version of XML Schema addressing this issue normatively is approved.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Note NOTE-xml11schema10-20050511</howpublished>
		<title type="sharef:primaryTitle">Processing XML 1.1 Documents with XML Schema 1.0 Processors</title>
		<field type="bibtex:topic">xsd[0.8] xml[0.8]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2005/NOTE-xml11schema10-20050511</identifier>
	</reference>
	<reference name="xmlschemaref" src="bibtex:misc" src-info="bibtex:line-34280" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Mary</givenname>
				<surname>Holstege</surname>
			</person>
			<person>
				<givenname>Asir S.</givenname>
				<surname>Vedamuthu</surname>
			</person>
		</names>
		<date value="2008-11"/>
		<abstract>
			<richtext>
				<p>XML Schema: Component Designators defines a scheme for identifying XML Schema components as specified by "XML Schema Part 1: Structures" and "XML Schema Part 2: Datatypes".</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-xmlschema-ref-20081117</howpublished>
		<title type="sharef:primaryTitle">W3C XML Schema Definition Language (XSD): Component Designators</title>
		<field type="bibtex:topic">xsd[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2008/WD-xmlschema-ref-20081117</identifier>
	</reference>
	<reference name="xmlschemapatterns" src="bibtex:misc" src-info="bibtex:line-34291" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Jonathan</givenname>
				<surname>Calladine</surname>
			</person>
			<person>
				<givenname>George</givenname>
				<surname>Cowe</surname>
			</person>
			<person>
				<givenname>Paul</givenname>
				<surname>Downey</surname>
			</person>
			<person>
				<givenname>Yves</givenname>
				<surname>Lafon</surname>
			</person>
		</names>
		<date value="2009-05"/>
		<abstract>
			<richtext>
				<p>This specification provides a set of basic XML Schema 1.0 patterns known to be interoperable between state of the art databinding implementations. The patterns may be used to describe XML 1.0 representations of commonly used data structures. The data structures described are intended to be independent of any particular programming language, database or modelling environment.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Note NOTE-xmlschema-patterns-20090505</howpublished>
		<title type="sharef:primaryTitle">Basic XML Schema Patterns for Databinding Version 1.0</title>
		<field type="bibtex:topic">xsd[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2009/NOTE-xmlschema-patterns-20090505</identifier>
	</reference>
	<reference name="xmlschemapatternsadvanced" src="bibtex:misc" src-info="bibtex:line-34302" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Jonathan</givenname>
				<surname>Calladine</surname>
			</person>
			<person>
				<givenname>George</givenname>
				<surname>Cowe</surname>
			</person>
			<person>
				<givenname>Paul</givenname>
				<surname>Downey</surname>
			</person>
			<person>
				<givenname>Yves</givenname>
				<surname>Lafon</surname>
			</person>
		</names>
		<date value="2009-05"/>
		<abstract>
			<richtext>
				<p>This specification provides a set of commonly used XML Schema 1.0 patterns known to cause issues with some state of the art databinding implementations. The patterns in conjunction with the Basic Patterns may be used to describe XML representations of commonly used data structures. The data structures described are intended to be independent of any particular programming language, database or modelling environment.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Note NOTE-xmlschema-patterns-advanced-20090505</howpublished>
		<title type="sharef:primaryTitle">Advanced XML Schema Patterns for Databinding Version 1.0</title>
		<field type="bibtex:topic">xsd[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2009/NOTE-xmlschema-patterns-advanced-20090505</identifier>
	</reference>
	<reference name="xmlschema11req" src="bibtex:misc" src-info="bibtex:line-34313" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Charles</givenname>
				<surname>Campbell</surname>
			</person>
			<person>
				<givenname>Ashok</givenname>
				<surname>Malhotra</surname>
			</person>
			<person>
				<givenname>Priscilla</givenname>
				<surname>Walmsley</surname>
			</person>
		</names>
		<date value="2003-01"/>
		<howpublished>World Wide Web Consortium, Working Draft WD-xmlschema-11-req-20030121</howpublished>
		<title type="sharef:primaryTitle">Requirements for XML Schema 1.1</title>
		<field type="bibtex:topic">xsd[1]</field>
		<field type="bibtex:updates">xmlsch1 xmlsch2</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2003/WD-xmlschema-11-req-20030121</identifier>
	</reference>
	<reference name="xmlschema11-1" src="bibtex:misc" src-info="bibtex:line-34324" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Shudi</givenname>
				<surname>Gao</surname>
			</person>
			<person>
				<givenname>C. Michael</givenname>
				<surname>Sperberg-McQueen</surname>
			</person>
			<person>
				<givenname>Henry S.</givenname>
				<surname>Thompson</surname>
			</person>
			<person>
				<givenname>Noah</givenname>
				<surname>Mendelsohn</surname>
			</person>
			<person>
				<givenname>David</givenname>
				<surname>Beech</surname>
			</person>
			<person>
				<givenname>Murray</givenname>
				<surname>Maloney</surname>
			</person>
		</names>
		<date value="2009-12"/>
		<abstract>
			<richtext>
				<p>This document specifies the XML Schema Definition Language, which offers facilities for describing the structure and constraining the contents of XML documents, including those which exploit the XML Namespace facility. The schema language, which is itself represented in an XML vocabulary and uses namespaces, substantially reconstructs and considerably extends the capabilities found in XML document type definitions (DTDs). This specification depends on XML Schema Definition Language 1.1 Part 2: Datatypes.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-xmlschema11-1-20091203</howpublished>
		<title type="sharef:primaryTitle">W3C XML Schema Definition Language (XSD) 1.1 Part 1: Structures</title>
		<field type="bibtex:topic">xsd[1]</field>
		<field type="bibtex:updates">xmlschema11req xmlschema1sec</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2009/WD-xmlschema11-1-20091203</identifier>
	</reference>
	<reference name="xmlschema11-2" src="bibtex:misc" src-info="bibtex:line-34336" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>David</givenname>
				<surname>Peterson</surname>
			</person>
			<person>
				<givenname>Shudi</givenname>
				<surname>Gao</surname>
			</person>
			<person>
				<givenname>Ashok</givenname>
				<surname>Malhotra</surname>
			</person>
			<person>
				<givenname>C. Michael</givenname>
				<surname>Sperberg-McQueen</surname>
			</person>
			<person>
				<givenname>Henry S.</givenname>
				<surname>Thompson</surname>
			</person>
		</names>
		<date value="2009-12"/>
		<abstract>
			<richtext>
				<p>XML Schema: Datatypes is part 2 of the specification of the XML Schema language. It defines facilities for defining datatypes to be used in XML Schemas as well as other XML specifications. The datatype language, which is itself represented in XML, provides a superset of the capabilities found in XML document type definitions (DTDs) for specifying datatypes on elements and attributes.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-xmlschema11-2-20091203</howpublished>
		<title type="sharef:primaryTitle">W3C XML Schema Definition Language (XSD) 1.1 Part 2: Datatypes</title>
		<field type="bibtex:topic">xsd[1]</field>
		<field type="bibtex:updates">xmlschema11req xmlschema2sec</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2009/WD-xmlschema11-2-20091203</identifier>
	</reference>
	<reference name="xmlschf" src="bibtex:misc" src-info="bibtex:line-34348" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Allen</givenname>
				<surname>Brown</surname>
			</person>
			<person>
				<givenname>Matthew</givenname>
				<surname>Fuchs</surname>
			</person>
			<person>
				<givenname>Jonathan</givenname>
				<surname>Robie</surname>
			</person>
			<person>
				<givenname>Philip</givenname>
				<surname>Wadler</surname>
			</person>
		</names>
		<date value="2001-09"/>
		<abstract>
			<richtext>
				<p>XML Schema: Formal Description is a formal description of XML types and validity as specified by XML Schema Part 1: Structures.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-xmlschema-formal-20010925</howpublished>
		<title type="sharef:primaryTitle">XML Schema: Formal Description</title>
		<field type="bibtex:topic">xsd[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2001/WD-xmlschema-formal-20010925</identifier>
	</reference>
	<reference name="xmlinfo" src="bibtex:misc" src-info="bibtex:line-34359" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>John</givenname>
				<surname>Cowan</surname>
			</person>
			<person>
				<givenname>Richard</givenname>
				<surname>Tobin</surname>
			</person>
		</names>
		<date value="2001-10"/>
		<abstract>
			<richtext>
				<p>This specification provides a set of definitions for use in other specifications that need to refer to the information in an XML document.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Recommendation REC-xml-infoset-20011024</howpublished>
		<title type="sharef:primaryTitle">XML Information Set</title>
		<field type="bibtex:topic">xmlinfoset[1]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2001/REC-xml-infoset-20011024</identifier>
	</reference>
	<reference name="xmlinfoset" src="bibtex:misc" src-info="bibtex:line-34370" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>John</givenname>
				<surname>Cowan</surname>
			</person>
			<person>
				<givenname>Richard</givenname>
				<surname>Tobin</surname>
			</person>
		</names>
		<date value="2004-02"/>
		<abstract>
			<richtext>
				<p>This specification provides a set of definitions for use in other specifications that need to refer to the information in an XML document.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Recommendation REC-xml-infoset-20040204</howpublished>
		<title type="sharef:primaryTitle">XML Information Set (Second Edition)</title>
		<field type="bibtex:topic">xmlinfoset[1]</field>
		<field type="bibtex:updates">xmlinfo</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2004/REC-xml-infoset-20040204</identifier>
	</reference>
	<reference name="infosetrdf" src="bibtex:misc" src-info="bibtex:line-34382" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Richard</givenname>
				<surname>Tobin</surname>
			</person>
		</names>
		<date value="2001-04"/>
		<abstract>
			<richtext>
				<p>This W3C Note defines an RDF schema for the XML Infoset.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Note NOTE-xml-infoset-rdfs-20010406</howpublished>
		<title type="sharef:primaryTitle">An RDF Schema for the XML Information Set</title>
		<field type="bibtex:topic">xmlinfoset[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2001/NOTE-xml-infoset-rdfs-20010406</identifier>
	</reference>
	<reference name="xfdl" src="bibtex:misc" src-info="bibtex:line-34393" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>John M.</givenname>
				<surname>Boyer</surname>
			</person>
			<person>
				<givenname>Tim</givenname>
				<surname>Bray</surname>
			</person>
			<person>
				<givenname>Maureen</givenname>
				<surname>Gordon</surname>
			</person>
		</names>
		<date value="1998-09"/>
		<abstract>
			<richtext>
				<p>This document describes an XML syntax for the Extensible Forms Description Language (XFDL). The purpose of XFDL is to solve the body of problems associated with digitally representing complex forms such as those found in business and government. The requirements include support for high precision layout, supporting documentation, integrated computations and input validation, multiple overlapping digital signatures, and legally binding auditable transaction records, by maintaining the whole form as a single unit such that digital signatures can capture the entire context of transactions.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Note NOTE-XFDL-19980902</howpublished>
		<title type="sharef:primaryTitle">Extensible Forms Description Language (XFDL) 4.0</title>
		<field type="bibtex:topic">xfdl[1]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/1998/NOTE-XFDL-19980902</identifier>
	</reference>
	<reference name="xmlcanon" src="bibtex:misc" src-info="bibtex:line-34404" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>John M.</givenname>
				<surname>Boyer</surname>
			</person>
		</names>
		<date value="2001-03"/>
		<abstract>
			<richtext>
				<p>Any XML document is part of a set of XML documents that are logically equivalent within an application context, but which vary in physical representation based on syntactic changes permitted by XML 1.0 and Namespaces in XML. This specification describes a method for generating a physical representation, the canonical form, of an XML document that accounts for the permissible changes. Except for limitations regarding a few unusual cases, if two documents have the same canonical form, then the two documents are logically equivalent within the given application context. Note that two documents may have differing canonical forms yet still be equivalent in a given context based on application-specific equivalence rules for which no generalized XML specification could account.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Recommendation REC-xml-c14n-20010315</howpublished>
		<title type="sharef:primaryTitle">Canonical XML Version 1.0</title>
		<field type="bibtex:topic">canonicalxml[1]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2001/REC-xml-c14n-20010315</identifier>
	</reference>
	<reference name="c14n10issues" src="bibtex:misc" src-info="bibtex:line-34415" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>José</givenname>
				<surname>Kahan</surname>
			</person>
			<person>
				<givenname>Konrad</givenname>
				<surname>Lanz</surname>
			</person>
		</names>
		<date value="2006-12"/>
		<abstract>
			<richtext>
				<p>This technical note addresses some of the issues related to inheritance of the XML attributes xml:base and xml:id and the W3C Recommendation for Canonical XML Version 1.0 (Errata). Shortcomings of C14N/1.0 are noted out and the use of a new C14N/1.1 recommendation with the XML Digital Signature 1.0 Recommendation is discussed.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Note NOTE-C14N-issues-20061220</howpublished>
		<title type="sharef:primaryTitle">Known Issues with Canonical XML 1.0 (C14N/1.0)</title>
		<field type="bibtex:topic">canonicalxml[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2006/NOTE-C14N-issues-20061220</identifier>
	</reference>
	<reference name="xmlcanon11" src="bibtex:misc" src-info="bibtex:line-34426" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>John M.</givenname>
				<surname>Boyer</surname>
			</person>
			<person>
				<givenname>Glenn</givenname>
				<surname>Marcy</surname>
			</person>
		</names>
		<date value="2008-05"/>
		<abstract>
			<richtext>
				<p>Canonical XML Version 1.1 is a revision to Canonical XML Version 1.0 to address issues related to inheritance of attributes in the XML namespace when canonicalizing document subsets, including the requirement not to inherit xml:id, and to treat xml:base URI path processing properly. Any XML document is part of a set of XML documents that are logically equivalent within an application context, but which vary in physical representation based on syntactic changes permitted by XML 1.0 and Namespaces in XML 1.0. This specification describes a method for generating a physical representation, the canonical form, of an XML document that accounts for the permissible changes. Except for limitations regarding a few unusual cases, if two documents have the same canonical form, then the two documents are logically equivalent within the given application context. Note that two documents may have differing canonical forms yet still be equivalent in a given context based on application-specific equivalence rules for which no generalized XML specification could account. Canonical XML Version 1.1 is applicable to XML 1.0 and defined in terms of the XPath 1.0 data model. It is not defined for XML 1.1.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Recommendation REC-xml-c14n11-20080502</howpublished>
		<title type="sharef:primaryTitle">Canonical XML 1.1</title>
		<field type="bibtex:topic">canonicalxml[1]</field>
		<field type="bibtex:updates">xmlcanon c14n10issues</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2008/REC-xml-c14n11-20080502</identifier>
	</reference>
	<reference name="xmlexcanon" src="bibtex:misc" src-info="bibtex:line-34438" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>John M.</givenname>
				<surname>Boyer</surname>
			</person>
			<person>
				<givenname>Donald E.</givenname>
				<surname>Eastlake</surname>
			</person>
			<person>
				<givenname>Joseph M.</givenname>
				<surname>Reagle</surname>
			</person>
		</names>
		<date value="2002-07"/>
		<abstract>
			<richtext>
				<p>Canonical XML specifies a standard serialization of XML that, when applied to a subdocument, includes the subdocument's ancestor context including all of the namespace declarations and attributes in the "xml:" namespace. However, some applications require a method which, to the extent practical, excludes ancestor context from a canonicalized subdocument. For example, one might require a digital signature over an XML payload (subdocument) in an XML message that will not break when that subdocument is removed from its original message and/or inserted into a different context. This requirement is satisfied by Exclusive XML Canonicalization.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Recommendation REC-xml-exc-c14n-20020718</howpublished>
		<title type="sharef:primaryTitle">Exclusive XML Canonicalization Version 1.0</title>
		<field type="bibtex:topic">canonicalxml[1]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2002/REC-xml-exc-c14n-20020718</identifier>
	</reference>
	<reference name="xmlc14n2" src="bibtex:misc" src-info="bibtex:line-34449" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>John M.</givenname>
				<surname>Boyer</surname>
			</person>
			<person>
				<givenname>Glenn</givenname>
				<surname>Marcy</surname>
			</person>
			<person>
				<givenname>Pratik</givenname>
				<surname>Datta</surname>
			</person>
			<person>
				<givenname>Frederick</givenname>
				<surname>Hirsch</surname>
			</person>
		</names>
		<date value="2010-08"/>
		<abstract>
			<richtext>
				<p>Canonical XML Version 2.0 is a major rewrite of Canonical XML Version 1.1 and Exclusive Canonical XML 1.0 to address issues around performance, streaming, hardware implementation, robustness, minimizing attack surface, determining what is signed and more. It combines inclusive and exclusive canonicalization algorithms into a single algorithm, that takes the canonicalization mode as a parameter. Any XML document is part of a set of XML documents that are logically equivalent within an application context, but which vary in physical representation based on syntactic changes permitted by XML 1.0 and Namespaces in XML 1.0. This specification describes a method for generating a physical representation, the canonical form, of an XML document that accounts for the permissible changes. Except for limitations regarding a few unusual cases, if two documents have the same canonical form, then the two documents are logically equivalent within the given application context. Note that two documents may have differing canonical forms yet still be equivalent in a given context based on application-specific equivalence rules for which no generalized XML specification could account. Canonical XML Version 2.0 is applicable to XML 1.0. It is not defined for XML 1.1.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-xml-c14n2-20100831</howpublished>
		<title type="sharef:primaryTitle">Canonical XML Version 2.0</title>
		<field type="bibtex:topic">canonicalxml[1]</field>
		<field type="bibtex:updates">xmlcanon11 xmlexcanon xmldsigsimplify</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2010/WD-xml-c14n2-20100831</identifier>
	</reference>
	<reference name="cdrreqs" src="bibtex:misc" src-info="bibtex:line-34461" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Daniel</givenname>
				<surname>Appelquist</surname>
			</person>
			<person>
				<givenname>Timur</givenname>
				<surname>Mehrvarz</surname>
			</person>
			<person>
				<givenname>Antoine</givenname>
				<surname>Quint</surname>
			</person>
		</names>
		<date value="2005-12"/>
		<abstract>
			<richtext>
				<p>This document describes the use cases for a framework that combines documents by reference and the set of requirements for such a framework.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Note NOTE-CDRReqs-20051219</howpublished>
		<title type="sharef:primaryTitle">Compound Document by Reference Use Cases and Requirements Version 1.0</title>
		<identifier type="sharef:uri">http://www.w3.org/TR/2005/NOTE-CDRReqs-20051219</identifier>
	</reference>
	<reference name="cdfreqs" src="bibtex:misc" src-info="bibtex:line-34471" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Steve</givenname>
				<surname>Speicher</surname>
			</person>
			<person>
				<givenname>Petri</givenname>
				<surname>Vuorimaa</surname>
			</person>
		</names>
		<date value="2005-12"/>
		<abstract>
			<richtext>
				<p>This document describes the use cases for a framework that combines documents and the set of requirements for such a framework.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-CDFReqs-20051219</howpublished>
		<title type="sharef:primaryTitle">Compound Document Use Cases and Requirements Version 2.0</title>
		<field type="bibtex:updates">cdrreqs</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2005/WD-CDFReqs-20051219</identifier>
	</reference>
	<reference name="wicd10core" src="bibtex:misc" src-info="bibtex:line-34482" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Timur</givenname>
				<surname>Mehrvarz</surname>
			</person>
			<person>
				<givenname>Lasse</givenname>
				<surname>Pajunen</surname>
			</person>
			<person>
				<givenname>Julien</givenname>
				<surname>Quint</surname>
			</person>
			<person>
				<givenname>Daniel</givenname>
				<surname>Appelquist</surname>
			</person>
		</names>
		<date value="2010-08"/>
		<abstract>
			<richtext>
				<p>This document specifies WICD Core 1.0, a device independent Compound Document profile based on XHTML, CSS and SVG. Compound Document is the W3C term for a document that combines multiple formats. WICD stands for Web Integration Compound Document and is based on the idea of integrating existing markup language formats in preference to inventing new markup.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Note NOTE-WICD-20100819</howpublished>
		<title type="sharef:primaryTitle">WICD Core 1.0</title>
		<field type="bibtex:topic">wicd[1]</field>
		<field type="bibtex:updates">cdfreqs</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2010/NOTE-WICD-20100819</identifier>
	</reference>
	<reference name="wicd10mobile" src="bibtex:misc" src-info="bibtex:line-34494" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Timur</givenname>
				<surname>Mehrvarz</surname>
			</person>
			<person>
				<givenname>Lasse</givenname>
				<surname>Pajunen</surname>
			</person>
			<person>
				<givenname>Julien</givenname>
				<surname>Quint</surname>
			</person>
			<person>
				<givenname>Daniel</givenname>
				<surname>Appelquist</surname>
			</person>
		</names>
		<date value="2010-08"/>
		<abstract>
			<richtext>
				<p>Compound Document is the W3C term for a document that combines multiple formats. The CDF Working Group has defined CDRF 1.0 as a framework to describe such documents. This document specifies WICD Mobile 1.0, a Compound Document profile based on XHTML, CSS, SVG and DOM, which conforms to CDRF 1.0 and WICD Core 1.0. WICD Mobile 1.0 is targeted at mobile agents and is a subset of WICD Full 1.0. WICD stands for Web Integration Compound Document.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Note NOTE-WICDMobile-20100819</howpublished>
		<title type="sharef:primaryTitle">WICD Mobile 1.0</title>
		<field type="bibtex:topic">wicd[1]</field>
		<field type="bibtex:updates">cdfreqs</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2010/NOTE-WICDMobile-20100819</identifier>
	</reference>
	<reference name="wicd10full" src="bibtex:misc" src-info="bibtex:line-34506" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Timur</givenname>
				<surname>Mehrvarz</surname>
			</person>
			<person>
				<givenname>Lasse</givenname>
				<surname>Pajunen</surname>
			</person>
			<person>
				<givenname>Julien</givenname>
				<surname>Quint</surname>
			</person>
			<person>
				<givenname>Daniel</givenname>
				<surname>Appelquist</surname>
			</person>
		</names>
		<date value="2010-08"/>
		<abstract>
			<richtext>
				<p>Compound Document is the W3C term for a document that combines multiple formats. The CDF Working Group has defined CDRF 1.0 as a framework to describe such documents. This document specifies WICD Full 1.0, a Compound Document profile based on XHTML, CSS, SVG and DOM, which conforms to CDRF 1.0 and WICD Core 1.0. WICD Full 1.0 is targeted at desktop agents and is a superset of WICD Mobile 1.0. WICD stands for Web Integration Compound Document.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Note NOTE-WICDFull-20100819</howpublished>
		<title type="sharef:primaryTitle">WICD Full 1.0</title>
		<field type="bibtex:topic">wicd[1]</field>
		<field type="bibtex:updates">cdfreqs</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2010/NOTE-WICDFull-20100819</identifier>
	</reference>
	<reference name="cdr" src="bibtex:misc" src-info="bibtex:line-34518" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Timur</givenname>
				<surname>Mehrvarz</surname>
			</person>
			<person>
				<givenname>Lasse</givenname>
				<surname>Pajunen</surname>
			</person>
			<person>
				<givenname>Julien</givenname>
				<surname>Quint</surname>
			</person>
			<person>
				<givenname>Daniel</givenname>
				<surname>Appelquist</surname>
			</person>
		</names>
		<date value="2010-08"/>
		<abstract>
			<richtext>
				<p>This document specifies the Compound Document by Reference Framework 1.0. When combining separate markup languages, specific problems have to be resolved that are not addressed by their individual language specifications, such as the propagation of events across namespaces, the combination of rendering or the user interaction model. Compound Document is the W3C term for a document that combines multiple formats.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Note NOTE-CDR-20100819</howpublished>
		<title type="sharef:primaryTitle">Compound Document by Reference Framework 1.0</title>
		<field type="bibtex:updates">cdfreqs</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2010/NOTE-CDR-20100819</identifier>
	</reference>
	<reference name="xmlfrag" src="bibtex:misc" src-info="bibtex:line-34529" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Paul</givenname>
				<surname>Grosso</surname>
			</person>
			<person>
				<givenname>Daniel</givenname>
				<surname>Veillard</surname>
			</person>
		</names>
		<date value="2001-02"/>
		<abstract>
			<richtext>
				<p>The XML standard supports logical documents composed of possibly several entities. It may be desirable to view or edit one or more of the entities or parts of entities while having no interest, need, or ability to view or edit the entire document. The problem, then, is how to provide to a recipient of such a fragment the appropriate information about the context that fragment had in the larger document that is not available to the recipient. The XML Fragment WG is chartered with defining a way to send fragments of an XML document — regardless of whether the fragments are predetermined entities or not — without having to send all of the containing document up to the part in question. This document defines Version 1.0 of the [eventual] W3C Recommendation that addresses this issue.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Candidate Recommendation CR-xml-fragment-20010212</howpublished>
		<field type="bibtex:index">XML, XML Fragment Interchange</field>
		<title type="sharef:primaryTitle">XML Fragment Interchange</title>
		<identifier type="sharef:uri">http://www.w3.org/TR/2001/CR-xml-fragment-20010212</identifier>
	</reference>
	<reference name="xinclude" src="bibtex:misc" src-info="bibtex:line-34540" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Jonathan</givenname>
				<surname>Marsh</surname>
			</person>
			<person>
				<givenname>David</givenname>
				<surname>Orchard</surname>
			</person>
		</names>
		<date value="2004-12"/>
		<abstract>
			<richtext>
				<p>This document specifies a processing model and syntax for general purpose inclusion. Inclusion is accomplished by merging a number of XML information sets into a single composite infoset. Specification of the XML documents (infosets) to be merged and control over the merging process is expressed in XML-friendly syntax (elements, attributes, URI references).</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Recommendation REC-xinclude-20041220</howpublished>
		<title type="sharef:primaryTitle">XML Inclusions (XInclude) Version 1.0</title>
		<field type="bibtex:topic">xinclude[1] xml[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2004/REC-xinclude-20041220</identifier>
	</reference>
	<reference name="xinclude2nd" src="bibtex:misc" src-info="bibtex:line-34551" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Jonathan</givenname>
				<surname>Marsh</surname>
			</person>
			<person>
				<givenname>David</givenname>
				<surname>Orchard</surname>
			</person>
			<person>
				<givenname>Daniel</givenname>
				<surname>Veillard</surname>
			</person>
		</names>
		<date value="2006-11"/>
		<abstract>
			<richtext>
				<p>This document specifies a processing model and syntax for general purpose inclusion. Inclusion is accomplished by merging a number of XML information sets into a single composite infoset. Specification of the XML documents (infosets) to be merged and control over the merging process is expressed in XML-friendly syntax (elements, attributes, URI references).</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Recommendation REC-xinclude-20061115</howpublished>
		<title type="sharef:primaryTitle">XML Inclusions (XInclude) Version 1.0 (Second Edition)</title>
		<field type="bibtex:topic">xinclude[1] xml[0.9]</field>
		<field type="bibtex:updates">xinclude</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2006/REC-xinclude-20061115</identifier>
	</reference>
	<reference name="grddl" src="bibtex:misc" src-info="bibtex:line-34563" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Dan</givenname>
				<surname>Connolly</surname>
			</person>
		</names>
		<date value="2007-09"/>
		<abstract>
			<richtext>
				<p>GRDDL is a mechanism for Gleaning Resource Descriptions from Dialects of Languages. This GRDDL specification introduces markup for declaring that an XML document includes gleanable data and for linking to an algorithm, typically represented in XSLT, for gleaning the resource descriptions from the document. The markup includes a namespace-qualified attribute for use in general-purpose XML documents and a profile-qualified link relationship for use in valid XHTML documents. The GRDDL mechanism also allows an XML namespace document (or XHTML profile document) to declare that every document associated with that namespace (or profile) includes gleanable data and for linking to an algorithm for gleaning the data. A corresponding GRDDL Use Case Working Draft provides motivating examples. A GRDDL Primer demonstrates the mechanism on XHTML documents which include widely-deployed dialects, more recently known as microformats. A GRDDL Test Cases document illustrates specific issues in this design and provides materials to aid in test-driven development of GRDDL-aware agents.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Recommendation REC-grddl-20070911</howpublished>
		<title type="sharef:primaryTitle">Gleaning Resource Descriptions from Dialects of Languages (GRDDL)</title>
		<field type="bibtex:topic">grddl[1] rdf[0.8]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2007/REC-grddl-20070911</identifier>
	</reference>
	<reference name="grddlprimer" src="bibtex:misc" src-info="bibtex:line-34574" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Harry</givenname>
				<surname>Halpin</surname>
			</person>
			<person>
				<givenname>Ian</givenname>
				<surname>Davis</surname>
			</person>
		</names>
		<date value="2007-06"/>
		<abstract>
			<richtext>
				<p>GRDDL is a mechanism for Gleaning Resource Descriptions from Dialects of Languages. It is a technique for obtaining RDF data from XML documents and in particular XHTML pages. Authors may explicitly associate documents with transformation algorithms, typically represented in XSLT, using a link element in the head of the document. Alternatively, the information needed to obtain the transformation may be held in an associated metadata profile document or namespace document. Clients reading the document can follow links across the Web using techniques described in the GRDDL specification to discover the appropriate transformations. This document uses a number of examples from the GRDDL Use Cases document to illustrate, in detail, the techniques GRDDL provides for associating documents with appropriate instructions for extracting any embedded data.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Note NOTE-grddl-primer-20070628</howpublished>
		<title type="sharef:primaryTitle">GRDDL Primer</title>
		<field type="bibtex:topic">grddl[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2007/NOTE-grddl-primer-20070628</identifier>
	</reference>
	<reference name="grddlusecases" src="bibtex:misc" src-info="bibtex:line-34585" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Fabien</givenname>
				<surname>Gandon</surname>
			</person>
		</names>
		<date value="2007-04"/>
		<abstract>
			<richtext>
				<p>GRDDL is a mechanism for Gleaning Resource Descriptions from Dialects of Languages. The GRDDL specification introduces markup for declaring that an XML document includes gleanable data and for linking to an algorithm, typically represented in XSLT, for gleaning the RDF data from the document. The markup includes a namespace-qualified attribute for use in general-purpose XML documents and a profile-qualified link relationship for use in valid XHTML documents. The GRDDL mechanism also allows an XML namespace document (or XHTML profile document) to declare that every document associated with that namespace (or profile) includes gleanable data and for linking to an algorithm for gleaning the data. A corresponding GRDDL specification provides complete technical details. A GRDDL Primer demonstrates the mechanism on XHTML documents which include widely-deployed dialects, more recently known as microformats.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Note NOTE-grddl-scenarios-20070406</howpublished>
		<title type="sharef:primaryTitle">GRDDL Use Cases: Scenarios of Extracting RDF Data from XML Documents</title>
		<field type="bibtex:topic">grddl[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2007/NOTE-grddl-scenarios-20070406</identifier>
	</reference>
	<reference name="grddltestcases" src="bibtex:misc" src-info="bibtex:line-34596" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Chimezie</givenname>
				<surname>Ogbuji</surname>
			</person>
		</names>
		<date value="2007-09"/>
		<abstract>
			<richtext>
				<p>This document describes and includes test cases for software agents that extract RDF from XML source documents by following the set of mechanisms outlined in the Gleaning Resource Description from Dialects of Language (GRDDL) specification. They demonstrate the expected behavior of a GRDDL-aware agent by specifying one (or more) RDF graph serializations which are the GRDDL results associated with a single source document.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Recommendation REC-grddl-tests-20070911</howpublished>
		<title type="sharef:primaryTitle">GRDDL Test Cases</title>
		<field type="bibtex:topic">grddl[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2007/REC-grddl-tests-20070911</identifier>
	</reference>
	<reference name="xmluni" src="bibtex:misc" src-info="bibtex:line-34607" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Martin J.</givenname>
				<surname>Dürst</surname>
			</person>
			<person>
				<givenname>Asmus</givenname>
				<surname>Freytag</surname>
			</person>
		</names>
		<date value="2007-05"/>
		<abstract>
			<richtext>
				<p>This document contains guidelines on the use of the Unicode Standard in conjunction with markup languages such as XML.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Note NOTE-unicode-xml-20070516</howpublished>
		<title type="sharef:primaryTitle">Unicode in XML and other Markup Languages</title>
		<field type="bibtex:topic">xml[0.9] unicode[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2007/NOTE-unicode-xml-20070516</identifier>
	</reference>
	<reference name="webchar10" src="bibtex:misc" src-info="bibtex:line-34618" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Martin J.</givenname>
				<surname>Dürst</surname>
			</person>
			<person>
				<givenname>François</givenname>
				<surname>Yergeau</surname>
			</person>
			<person>
				<givenname>Richard</givenname>
				<surname>Ishida</surname>
			</person>
			<person>
				<givenname>Misha</givenname>
				<surname>Wolf</surname>
			</person>
			<person>
				<givenname>Tex</givenname>
				<surname>Texin</surname>
			</person>
		</names>
		<date value="2003-08"/>
		<howpublished>World Wide Web Consortium, Working Draft WD-charmod-20030822</howpublished>
		<title type="sharef:primaryTitle">Character Model for the World Wide Web 1.0</title>
		<field type="bibtex:topic">www[0.9] unicode[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2003/WD-charmod-20030822</identifier>
	</reference>
	<reference name="webchar10fund" src="bibtex:misc" src-info="bibtex:line-34628" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Martin J.</givenname>
				<surname>Dürst</surname>
			</person>
			<person>
				<givenname>François</givenname>
				<surname>Yergeau</surname>
			</person>
			<person>
				<givenname>Richard</givenname>
				<surname>Ishida</surname>
			</person>
			<person>
				<givenname>Misha</givenname>
				<surname>Wolf</surname>
			</person>
			<person>
				<givenname>Tex</givenname>
				<surname>Texin</surname>
			</person>
		</names>
		<date value="2005-02"/>
		<abstract>
			<richtext>
				<p>This Architectural Specification provides authors of specifications, software developers, and content developers with a common reference for interoperable text manipulation on the World Wide Web, building on the Universal Character Set, defined jointly by the Unicode Standard and ISO/IEC 10646. Topics addressed include use of the terms 'character', 'encoding' and 'string', a reference processing model, choice and identification of character encodings, character escaping, and string indexing. For normalization and string identity matching, see the companion document "Character Model for the World Wide Web 1.0: Normalization". For resource identifiers, see the companion document "Character Model for the World Wide Web 1.0: Resource Identifiers".</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Recommendation REC-charmod-20050215</howpublished>
		<title type="sharef:primaryTitle">Character Model for the World Wide Web 1.0: Fundamentals</title>
		<field type="bibtex:topic">www[0.9] unicode[0.9]</field>
		<field type="bibtex:updates">webchar10</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2005/REC-charmod-20050215</identifier>
	</reference>
	<reference name="webchar10resid" src="bibtex:misc" src-info="bibtex:line-34640" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Martin J.</givenname>
				<surname>Dürst</surname>
			</person>
			<person>
				<givenname>François</givenname>
				<surname>Yergeau</surname>
			</person>
			<person>
				<givenname>Richard</givenname>
				<surname>Ishida</surname>
			</person>
			<person>
				<givenname>Misha</givenname>
				<surname>Wolf</surname>
			</person>
			<person>
				<givenname>Tex</givenname>
				<surname>Texin</surname>
			</person>
		</names>
		<date value="2004-11"/>
		<abstract>
			<richtext>
				<p>This Architectural Specification provides authors of specifications, software developers, and content developers with a common reference for the use of resource identifiers building on the Universal Character Set, defined jointly by the Unicode Standard and ISO/IEC 10646.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Proposed Recommendation CR-charmod-resid-20041122</howpublished>
		<title type="sharef:primaryTitle">Character Model for the World Wide Web 1.0: Resource Identifiers</title>
		<field type="bibtex:topic">www[0.9] unicode[0.9] iri[0.9]</field>
		<field type="bibtex:updates">webchar10</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2004/CR-charmod-resid-20041122</identifier>
	</reference>
	<reference name="webchar10norm" src="bibtex:misc" src-info="bibtex:line-34652" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>François</givenname>
				<surname>Yergeau</surname>
			</person>
			<person>
				<givenname>Martin J.</givenname>
				<surname>Dürst</surname>
			</person>
			<person>
				<givenname>Richard</givenname>
				<surname>Ishida</surname>
			</person>
			<person>
				<givenname>Addison P.</givenname>
				<surname>Phillips</surname>
			</person>
			<person>
				<givenname>Misha</givenname>
				<surname>Wolf</surname>
			</person>
			<person>
				<givenname>Tex</givenname>
				<surname>Texin</surname>
			</person>
		</names>
		<date value="2005-10"/>
		<abstract>
			<richtext>
				<p>Based on "Character Model for the World Wide Web 1.0: Fundamentals", this Architectural Specification provides authors of specifications, software developers, and content developers with a common reference for early uniform normalization and string identity matching to improve interoperable text manipulation on the World Wide Web.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft charmod-norm-20051027</howpublished>
		<title type="sharef:primaryTitle">Character Model for the World Wide Web 1.0: Normalization</title>
		<field type="bibtex:topic">www[0.9] unicode[0.9]</field>
		<field type="bibtex:updates">webchar10</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2005/charmod-norm-20051027</identifier>
	</reference>
	<reference name="leiri" src="bibtex:misc" src-info="bibtex:line-34664" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Henry S.</givenname>
				<surname>Thompson</surname>
			</person>
			<person>
				<givenname>Richard</givenname>
				<surname>Tobin</surname>
			</person>
			<person>
				<givenname>Norman</givenname>
				<surname>Walsh</surname>
			</person>
		</names>
		<date value="2008-11"/>
		<abstract>
			<richtext>
				<p>For historic reasons, some formats have allowed variants of IRIs that are somewhat less restricted in syntax, for example XML system identifiers and W3C XML Schema anyURIs. This document provides a definition and a name (Legacy Extended IRI or LEIRI) for these variants for easy reference. These variants have to be used with care; they require further processing before being fully interchangeable as IRIs. New protocols and formats should not use Legacy Extended IRIs.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Note NOTE-leiri-20081103</howpublished>
		<title type="sharef:primaryTitle">Legacy Extended IRIs for XML Resource Identification</title>
		<field type="bibtex:topic">leiri[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2008/NOTE-leiri-20081103</identifier>
	</reference>
	<reference name="xmlss" src="bibtex:misc" src-info="bibtex:line-34675" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>James</givenname>
				<surname>Clark</surname>
			</person>
		</names>
		<date value="1999-06"/>
		<abstract>
			<richtext>
				<p>This document allows a style sheet to be associated with an XML document by including one or more processing instructions with a target of xml-stylesheet in the document's prolog.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Recommendation REC-xml-stylesheet-19990629</howpublished>
		<field type="bibtex:index">http://www.w3.org/1999/06/REC-xml-stylesheet-19990629</field>
		<title type="sharef:primaryTitle">Associating Style Sheets with XML Documents</title>
		<field type="bibtex:topic">xml[0.9]</field>
	</reference>
	<reference name="xmlss2nd" src="bibtex:misc" src-info="bibtex:line-34686" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>James</givenname>
				<surname>Clark</surname>
			</person>
			<person>
				<givenname>Simon</givenname>
				<surname>Pieters</surname>
			</person>
			<person>
				<givenname>Henry S.</givenname>
				<surname>Thompson</surname>
			</person>
		</names>
		<date value="2010-10"/>
		<abstract>
			<richtext>
				<p>This document allows style sheets to be associated with an XML document by including one or more processing instructions with a target of xml-stylesheet in the document's prolog.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Recommendation REC-xml-stylesheet-20101028</howpublished>
		<field type="bibtex:index">http://www.w3.org/TR/2010/REC-xml-stylesheet-20101028</field>
		<title type="sharef:primaryTitle">Associating Style Sheets with XML documents 1.0 (Second Edition)</title>
		<field type="bibtex:topic">xml[0.9]</field>
		<field type="bibtex:updates">xmlss</field>
	</reference>
	<reference name="xmlmodel" src="bibtex:misc" src-info="bibtex:line-34698" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Paul</givenname>
				<surname>Grosso</surname>
			</person>
			<person>
				<givenname>Jirka</givenname>
				<surname>Kosek</surname>
			</person>
		</names>
		<date value="2010-04"/>
		<abstract>
			<richtext>
				<p>This document allows schemas using any schema definition language to be associated with an XML document by including one or more processing instructions with a target of xml-model in the document's prolog.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Note NOTE-xml-model-20100415</howpublished>
		<field type="bibtex:index">http://www.w3.org/TR/2010/NOTE-xml-model-20100415</field>
		<title type="sharef:primaryTitle">Associating Schemas with XML documents 1.0 (First Edition)</title>
		<field type="bibtex:topic">xml[0.9] xmlschemalanguage[0.9]</field>
	</reference>
	<reference name="ttaf10req" src="bibtex:misc" src-info="bibtex:line-34709" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Glenn</givenname>
				<surname>Adams</surname>
			</person>
		</names>
		<date value="2006-04"/>
		<abstract>
			<richtext>
				<p>This document specifies usage scenarios and requirements for a timed text authoring format. A timed text authoring format is a content type that represents timed text media for the purpose of interchange among authoring systems. Timed text is textual information that is intrinsically or extrinsically associated with timing information.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Note NOTE-ttaf1-req-20060427</howpublished>
		<title type="sharef:primaryTitle">Timed Text (TT) Authoring Format 1.0 Use Cases and Requirements</title>
		<field type="bibtex:topic">ttaf[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2006/NOTE-ttaf1-req-20060427</identifier>
	</reference>
	<reference name="ttaf1dfxp" src="bibtex:misc" src-info="bibtex:line-34720" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Mike</givenname>
				<surname>Dolan</surname>
			</person>
			<person>
				<givenname>Geoff</givenname>
				<surname>Freed</surname>
			</person>
			<person>
				<givenname>Sean</givenname>
				<surname>Hayes</surname>
			</person>
			<person>
				<givenname>Erik</givenname>
				<surname>Hodge</surname>
			</person>
			<person>
				<givenname>David</givenname>
				<surname>Kirby</surname>
			</person>
			<person>
				<givenname>Thierry</givenname>
				<surname>Michel</surname>
			</person>
			<person>
				<givenname>David</givenname>
				<surname>Singer</surname>
			</person>
		</names>
		<names type="sharef:editor">
			<person>
				<givenname>Glenn</givenname>
				<surname>Adams</surname>
			</person>
		</names>
		<date value="2010-11"/>
		<abstract>
			<richtext>
				<p>This document specifies the Timed Text Markup Language (TTML) in terms of a vocabulary and semantics thereof. The Timed Text Markup Language is a content type that represents timed text media for the purpose of interchange among authoring systems. Timed text is textual information that is intrinsically or extrinsically associated with timing information. It is intended to be used for the purpose of transcoding or exchanging timed text information among legacy distribution content formats presently in use for subtitling and captioning functions. In addition to being used for interchange among legacy distribution content formats, TTML content may be used directly as a distribution format, for example, providing a standard content format to reference from a &lt;text&gt; or &lt;textstream&gt; media object element in a SMIL 2.1 document.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Recommendation REC-ttaf1-dfxp-20101118</howpublished>
		<title type="sharef:primaryTitle">Timed Text Markup Language (TTML) 1.0</title>
		<field type="bibtex:topic">ttml[1]</field>
		<field type="bibtex:updates">ttaf10req</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2010/REC-ttaf1-dfxp-20101118</identifier>
	</reference>
	<reference name="smil" src="bibtex:misc" src-info="bibtex:line-34733" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Philipp</givenname>
				<surname>Hoschka</surname>
			</person>
		</names>
		<date value="1998-06"/>
		<howpublished>World Wide Web Consortium, Recommendation REC-smil-19980615</howpublished>
		<title type="sharef:primaryTitle">Synchronized Multimedia Integration Language (SMIL) 1.0 Specification</title>
		<field type="bibtex:topic">xml[0.4] smil[1] hypermedia[0.8]</field>
	</reference>
	<reference name="boston" src="bibtex:misc" src-info="bibtex:line-34742" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Jeffrey</givenname>
				<surname>Ayars</surname>
			</person>
			<person>
				<givenname>Dick C. A.</givenname>
				<surname>Bulterman</surname>
			</person>
			<person>
				<givenname>Aaron</givenname>
				<surname>Cohen</surname>
			</person>
			<person>
				<givenname>Erik</givenname>
				<surname>Hodge</surname>
			</person>
			<person>
				<givenname>Philipp</givenname>
				<surname>Hoschka</surname>
			</person>
			<person>
				<givenname>Eric</givenname>
				<surname>Hyche</surname>
			</person>
			<person>
				<givenname>Ken</givenname>
				<surname>Day</surname>
			</person>
			<person>
				<givenname>Kenichi</givenname>
				<surname>Kubota</surname>
			</person>
			<person>
				<givenname>Robert</givenname>
				<surname>Lanphier</surname>
			</person>
			<person>
				<givenname>Nabil</givenname>
				<surname>Layaïda</surname>
			</person>
			<person>
				<givenname>Philippe</givenname>
				<surname>Le Hégaret</surname>
			</person>
			<person>
				<givenname>Thierry</givenname>
				<surname>Michel</surname>
			</person>
			<person>
				<givenname>Muriel</givenname>
				<surname>Jourdan</surname>
			</person>
			<person>
				<givenname>Jacco</givenname>
				<surname link="van">Ossenbruggen</surname>
			</person>
			<person>
				<givenname>Lloyd</givenname>
				<surname>Rutledge</surname>
			</person>
			<person>
				<givenname>Bridie</givenname>
				<surname>Saccocio</surname>
			</person>
			<person>
				<givenname>Patrick</givenname>
				<surname>Schmitz</surname>
			</person>
			<person>
				<givenname>Warner</givenname>
				<surname link="ten">Kate</surname>
			</person>
			<person>
				<givenname>Ted</givenname>
				<surname>Wugofski</surname>
			</person>
		</names>
		<date value="2000-06"/>
		<abstract>
			<richtext>
				<p>This document specifies the "Boston" version of the Synchronized Multimedia Integration Language (SMIL, pronounced "smile"). SMIL Boston has the following two design goals: (1) Define a simple XML-based language that allows authors to write interactive multimedia presentations. Using SMIL Boston, an author can describe the temporal behavior of a multimedia presentation, associate hyperlinks with media objects and describe the layout of the presentation on a screen. (2) Allow reusing of SMIL syntax and semantics in other XML-based languages, in particular those who need to represent timing and synchronization. For example, SMIL Boston components should be used for integrating timing into XHTML.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-smil-boston-20000622</howpublished>
		<title type="sharef:primaryTitle">Synchronized Multimedia Integration Language (SMIL) Boston Specification</title>
		<field type="bibtex:topic">xml[0.4] smil[1] hypermedia[0.8]</field>
		<field type="bibtex:updates">smil</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2000/WD-smil-boston-20000622</identifier>
	</reference>
	<reference name="smil20" src="bibtex:misc" src-info="bibtex:line-34754" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Jeffrey</givenname>
				<surname>Ayars</surname>
			</person>
			<person>
				<givenname>Dick C. A.</givenname>
				<surname>Bulterman</surname>
			</person>
			<person>
				<givenname>Aaron</givenname>
				<surname>Cohen</surname>
			</person>
			<person>
				<givenname>Ken</givenname>
				<surname>Day</surname>
			</person>
			<person>
				<givenname>Erik</givenname>
				<surname>Hodge</surname>
			</person>
			<person>
				<givenname>Philipp</givenname>
				<surname>Hoschka</surname>
			</person>
			<person>
				<givenname>Eric</givenname>
				<surname>Hyche</surname>
			</person>
			<person>
				<givenname>Muriel</givenname>
				<surname>Jourdan</surname>
			</person>
			<person>
				<givenname>Kenichi</givenname>
				<surname>Kubota</surname>
			</person>
			<person>
				<givenname>Robert</givenname>
				<surname>Lanphier</surname>
			</person>
			<person>
				<givenname>Nabil</givenname>
				<surname>Layaïda</surname>
			</person>
			<person>
				<givenname>Philippe</givenname>
				<surname>Le Hégaret</surname>
			</person>
			<person>
				<givenname>Thierry</givenname>
				<surname>Michel</surname>
			</person>
			<person>
				<givenname>Debbie</givenname>
				<surname>Newman</surname>
			</person>
			<person>
				<givenname>Jacco</givenname>
				<surname link="van">Ossenbruggen</surname>
			</person>
			<person>
				<givenname>Lloyd</givenname>
				<surname>Rutledge</surname>
			</person>
			<person>
				<givenname>Bridie</givenname>
				<surname>Saccocio</surname>
			</person>
			<person>
				<givenname>Patrick</givenname>
				<surname>Schmitz</surname>
			</person>
			<person>
				<givenname>Warner</givenname>
				<surname link="ten">Kate</surname>
			</person>
		</names>
		<date value="2005-01"/>
		<abstract>
			<richtext>
				<p>This document specifies the second version of the Synchronized Multimedia Integration Language (SMIL, pronounced "smile"). SMIL 2.0 has the following two design goals: (1) Define an XML-based language that allows authors to write interactive multimedia presentations. Using SMIL 2.0, an author can describe the temporal behavior of a multimedia presentation, associate hyperlinks with media objects and describe the layout of the presentation on a screen. (2) Allow reusing of SMIL syntax and semantics in other XML-based languages, in particular those who need to represent timing and synchronization. For example, SMIL 2.0 components are used for integrating timing into XHTML and into SVG.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Recommendation REC-SMIL2-20050107</howpublished>
		<title type="sharef:primaryTitle">Synchronized Multimedia Integration Language (SMIL 2.0) Specification — Second Edition</title>
		<field type="bibtex:topic">xml[0.4] smil[1] hypermedia[0.8]</field>
		<field type="bibtex:updates">boston</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2004/REC-SMIL2-20050107</identifier>
	</reference>
	<reference name="smil21" src="bibtex:misc" src-info="bibtex:line-34766" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Dick C. A.</givenname>
				<surname>Bulterman</surname>
			</person>
			<person>
				<givenname>Guido</givenname>
				<surname>Grassel</surname>
			</person>
			<person>
				<givenname>Jack</givenname>
				<surname>Jansen</surname>
			</person>
			<person>
				<givenname>Antti</givenname>
				<surname>Koivisto</surname>
			</person>
			<person>
				<givenname>Nabil</givenname>
				<surname>Layaïda</surname>
			</person>
			<person>
				<givenname>Thierry</givenname>
				<surname>Michel</surname>
			</person>
			<person>
				<givenname>Sjoerd</givenname>
				<surname>Mullender</surname>
			</person>
			<person>
				<givenname>Daniel F.</givenname>
				<surname>Zucker</surname>
			</person>
		</names>
		<date value="2005-12"/>
		<abstract>
			<richtext>
				<p>This document specifies the second version of the Synchronized Multimedia Integration Language (SMIL, pronounced "smile"). SMIL 2.1 has the following design goals: (1) Define an XML-based language that allows authors to write interactive multimedia presentations. Using SMIL, an author can describe the temporal behaviour of a multimedia presentation, associate hyperlinks with media objects and describe the layout of the presentation on a screen. (2) Allow reusing of SMIL syntax and semantics in other XML-based languages, in particular those who need to represent timing and synchronization. For example, SMIL components are used for integrating timing into XHTML and into SVG. (3) Extend the functionalities contained in the SMIL 2.0 into new or revised SMIL 2.1 modules. (4) Define new SMIL 2.1 Mobile Profiles incorporating features useful within the mobile industry.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Recommendation REC-SMIL2-20051213</howpublished>
		<title type="sharef:primaryTitle">Synchronized Multimedia Integration Language (SMIL 2.1)</title>
		<field type="bibtex:topic">xml[0.4] smil[1] hypermedia[0.8]</field>
		<field type="bibtex:updates">smil20</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2005/REC-SMIL2-20051213</identifier>
	</reference>
	<reference name="smil30" src="bibtex:misc" src-info="bibtex:line-34778" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Dick C. A.</givenname>
				<surname>Bulterman</surname>
			</person>
			<person>
				<givenname>Jack</givenname>
				<surname>Jansen</surname>
			</person>
			<person>
				<givenname>Pablo</givenname>
				<surname>Cesar</surname>
			</person>
			<person>
				<givenname>Sjoerd</givenname>
				<surname>Mullender</surname>
			</person>
			<person>
				<givenname>Marisa</givenname>
				<surname>DeMeglio</surname>
			</person>
			<person>
				<givenname>Julien</givenname>
				<surname>Quint</surname>
			</person>
			<person>
				<givenname>Petri</givenname>
				<surname>Vuorimaa</surname>
			</person>
			<person>
				<givenname>Samuel</givenname>
				<surname>Cruz-Lara</surname>
			</person>
			<person>
				<givenname>Hiroshi</givenname>
				<surname>Kawamura</surname>
			</person>
			<person>
				<givenname>Daniel</givenname>
				<surname>Weck</surname>
			</person>
			<person>
				<givenname>Eric</givenname>
				<surname>Hyche</surname>
			</person>
			<person>
				<givenname>Xabiel García</givenname>
				<surname>Pañeda</surname>
			</person>
			<person>
				<givenname>David</givenname>
				<surname>Melendi</surname>
			</person>
			<person>
				<givenname>Thierry</givenname>
				<surname>Michel</surname>
			</person>
			<person>
				<givenname>Daniel F.</givenname>
				<surname>Zucker</surname>
			</person>
		</names>
		<date value="2008-12"/>
		<abstract>
			<richtext>
				<p>This document specifies the third version of the Synchronized Multimedia Integration Language (SMIL, pronounced "smile"). SMIL 3.0 has the following design goals: (1) Define an XML-based language that allows authors to write interactive multimedia presentations. Using SMIL, an author may describe the temporal behaviour of a multimedia presentation, associate hyperlinks with media objects and describe the layout of the presentation on a screen. (2) Allow reusing of SMIL syntax and semantics in other XML-based languages, in particular those who need to represent timing and synchronization. For example, SMIL components are used for integrating timing into XHTML and into SVG. (3) Extend the functionalities contained in the SMIL 2.1 into new or revised SMIL 3.0 modules. (4) Define new SMIL 3.0 Profiles incorporating features useful within the industry.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Recommendation REC-SMIL3-20081201</howpublished>
		<title type="sharef:primaryTitle">Synchronized Multimedia Integration Language (SMIL 3.0)</title>
		<field type="bibtex:topic">xml[0.4] smil[1] hypermedia[0.8]</field>
		<field type="bibtex:updates">smil21</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2008/REC-SMIL3-20081201</identifier>
	</reference>
	<reference name="smiltimesheets" src="bibtex:misc" src-info="bibtex:line-34790" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Petri</givenname>
				<surname>Vuorimaa</surname>
			</person>
			<person>
				<givenname>Dick C. A.</givenname>
				<surname>Bulterman</surname>
			</person>
			<person>
				<givenname>Pablo</givenname>
				<surname>Cesar</surname>
			</person>
		</names>
		<date value="2008-01"/>
		<abstract>
			<richtext>
				<p>This document defines an XML timing language that makes SMIL 3.0 element and attribute timing control available to a wide range of other XML languages. This language allows SMIL timing to be integrated into a wide variety of a-temporal languages, even when several such languages are combined in a compound document. Because of its similarity with external style and positioning descriptions in the Cascading Style Sheet (CSS) language, this functionality has been termed SMIL Timesheets.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-timesheets-20080110</howpublished>
		<title type="sharef:primaryTitle">SMIL Timesheets 1.0</title>
		<field type="bibtex:topic">smil[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2008/WD-timesheets-20080110</identifier>
	</reference>
	<reference name="smilanim" src="bibtex:misc" src-info="bibtex:line-34801" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Patrick</givenname>
				<surname>Schmitz</surname>
			</person>
			<person>
				<givenname>Aaron</givenname>
				<surname>Cohen</surname>
			</person>
		</names>
		<date value="2001-09"/>
		<abstract>
			<richtext>
				<p>This is a W3C Recommendation of a specification of animation functionality for XML documents. It describes an animation framework as well as a set of base XML animation elements suitable for integration with XML documents. It is based upon the SMIL 1.0 timing model, with some extensions, and is a true subset of SMIL 2.0. This provides an intermediate stepping stone in terms of implementation complexity, for applications that wish to have SMIL-compatible animation but do not need or want time containers.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Recommendation REC-smil-animation-20010904</howpublished>
		<title type="sharef:primaryTitle">SMIL Animation</title>
		<field type="bibtex:topic">smil[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2001/REC-smil-animation-20010904</identifier>
	</reference>
	<reference name="smil2authext" src="bibtex:misc" src-info="bibtex:line-34812" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Yoshihisa</givenname>
				<surname>Gonno</surname>
			</person>
		</names>
		<date value="2003-05"/>
		<howpublished>World Wide Web Consortium, Note NOTE-SMIL2-AuthExt-20030512</howpublished>
		<title type="sharef:primaryTitle">SMIL 2.0 Extension for Professional Multimedia Authoring — Preliminary Investigation</title>
		<field type="bibtex:topic">smil[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2003/NOTE-SMIL2-AuthExt-20030512</identifier>
	</reference>
	<reference name="mediaannotreqs" src="bibtex:misc" src-info="bibtex:line-34822" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>WonSuk</givenname>
				<surname>Lee</surname>
			</person>
			<person>
				<givenname>Tobias</givenname>
				<surname>Bürger</surname>
			</person>
			<person>
				<givenname>Felix</givenname>
				<surname>Sasaki</surname>
			</person>
			<person>
				<givenname>Véronique</givenname>
				<surname>Malaisé</surname>
			</person>
		</names>
		<date value="2010-01"/>
		<abstract>
			<richtext>
				<p>This document specifies use cases and requirements as an input for the development of the "Ontology for Media Resource 1.0" and the "API for Media Resource 1.0". The ontology will be a simple ontology to support cross-community data integration of information related to media resources on the Web. The API will provide read access and potentially write access to media resources, relying on the definitions from the ontology. The main scope of this document are videos. Metadata for other media resources like audio or images will be taken into account if it is applicable for videos as well.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-media-annot-reqs-20100121</howpublished>
		<title type="sharef:primaryTitle">Use Cases and Requirements for Ontology and API for Media Resource 1.0</title>
		<identifier type="sharef:uri">http://www.w3.org/TR/2010/WD-media-annot-reqs-20100121</identifier>
	</reference>
	<reference name="xhtmlsmil" src="bibtex:misc" src-info="bibtex:line-34832" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Debbie</givenname>
				<surname>Newman</surname>
			</person>
			<person>
				<givenname>Aaron</givenname>
				<surname>Patterson</surname>
			</person>
			<person>
				<givenname>Patrick</givenname>
				<surname>Schmitz</surname>
			</person>
		</names>
		<date value="2002-01"/>
		<howpublished>World Wide Web Consortium, Note NOTE-XHTMLplusSMIL-20020131</howpublished>
		<title type="sharef:primaryTitle">XHTML+SMIL Profile</title>
		<field type="bibtex:topic">smil[0.9] xhtml[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2002/NOTE-XHTMLplusSMIL-20020131</identifier>
	</reference>
	<reference name="xhtmlvoice" src="bibtex:misc" src-info="bibtex:line-34842" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Jonny</givenname>
				<surname>Axelsson</surname>
			</person>
			<person>
				<givenname>Chris</givenname>
				<surname>Cross</surname>
			</person>
			<person>
				<givenname>Håkon Wium</givenname>
				<surname>Lie</surname>
			</person>
			<person>
				<givenname>Gerald</givenname>
				<surname>McCobb</surname>
			</person>
			<person>
				<givenname>T. V.</givenname>
				<surname>Raman</surname>
			</person>
			<person>
				<givenname>Les</givenname>
				<surname>Wilson</surname>
			</person>
		</names>
		<date value="2001-12"/>
		<howpublished>World Wide Web Consortium, Note NOTE-xhtml+voice-20011221</howpublished>
		<title type="sharef:primaryTitle">XHTML+Voice Profile 1.0</title>
		<field type="bibtex:topic">xhtml[0.9] voicexml[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2001/NOTE-xhtml+voice-20011221</identifier>
	</reference>
	<reference name="earl10req" src="bibtex:misc" src-info="bibtex:line-34852" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Michael</givenname>
				<surname>Squillace</surname>
			</person>
			<person>
				<givenname>Shadi</givenname>
				<surname>Abou-Zahra</surname>
			</person>
		</names>
		<date value="2009-10"/>
		<abstract>
			<richtext>
				<p>This document describes the requirements for the scope, design, and features of the Evaluation and Report Language (EARL) 1.0. EARL is a vocabulary, the terms of which are defined across a set of specifications and technical notes, and that is used to describe test results. The primary motivation for developing this vocabulary is to facilitate the exchange of test results between Web accessibility evaluation tools in a vendor-neutral and platform-independent format. It also provides reusable terms for generic quality assurance and validation purposes. The terms of EARL are defined by Evaluation and Report Language (EARL) 1.0 Schema, HTTP Vocabulary in RDF 1.0, Representing Content in RDF 1.0, and Pointer methods in RDF 1.0. A companion document, Evaluation and Report Language (EARL) 1.0 Guide, describes the motivations for EARL and provides an introduction to its uses. An Evaluation and Report Language (EARL) Overview is also available.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-EARL10-Requirements-20091029</howpublished>
		<title type="sharef:primaryTitle">Requirements for the Evaluation and Report Language (EARL) 1.0</title>
		<field type="bibtex:topic">earl[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2009/WD-EARL10-Requirements-20091029</identifier>
	</reference>
	<reference name="earl10" src="bibtex:misc" src-info="bibtex:line-34863" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Wendy</givenname>
				<surname>Chisholm</surname>
			</person>
			<person>
				<givenname>Sean B.</givenname>
				<surname>Palmer</surname>
			</person>
		</names>
		<date value="2002-12"/>
		<abstract>
			<richtext>
				<p>This is a W3C Working Draft produced by the Evaluation and Repair Tools Working Group (ERT WG). The purpose of this document is to explain how and why to use Evaluation and Report Language (EARL) 1.0. The ERT Working Group encourages feedback about this document as well as implementation of the language in authoring tools, testing tools, search engines, and other relevant tools. Evaluation and Report Language (EARL) is a general-purpose language for expressing test results. This specification describes how to use EARL to describe test results and defines a basic vocabulary for this purpose.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-EARL10-20021206</howpublished>
		<title type="sharef:primaryTitle">Evaluation and Report Language (EARL) 1.0</title>
		<field type="bibtex:topic">earl[1]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2002/WD-EARL10-20021206</identifier>
	</reference>
	<reference name="earl10schema" src="bibtex:misc" src-info="bibtex:line-34874" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Shadi</givenname>
				<surname>Abou-Zahra</surname>
			</person>
			<person>
				<givenname>Michael</givenname>
				<surname>Squillace</surname>
			</person>
		</names>
		<date value="2009-10"/>
		<abstract>
			<richtext>
				<p>This document describes the formal schema of the Evaluation and Report Language (EARL) 1.0. EARL is a vocabulary, the terms of which are defined across a set of specifications and technical notes, and that is used to describe test results. The primary motivation for developing this vocabulary is to facilitate the exchange of test results between Web accessibility evaluation tools in a vendor-neutral and platform-independent format. It also provides reusable terms for generic quality assurance and validation purposes.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-EARL10-Schema-20091029</howpublished>
		<title type="sharef:primaryTitle">Evaluation and Report Language (EARL) 1.0 Schema</title>
		<field type="bibtex:topic">earl[1]</field>
		<field type="bibtex:updates">earl10</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2009/WD-EARL10-Schema-20091029</identifier>
	</reference>
	<reference name="earl10guide" src="bibtex:misc" src-info="bibtex:line-34886" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Carlos A</givenname>
				<surname>Velasco</surname>
			</person>
			<person>
				<givenname>Johannes</givenname>
				<surname>Koch</surname>
			</person>
		</names>
		<date value="2009-10"/>
		<abstract>
			<richtext>
				<p>This document is an introductory guide to the Evaluation and Report Language (EARL) 1.0. EARL is a vocabulary, the terms of which are defined across a set of specifications and technical notes, that is used to describe test results. The primary motivation for developing this vocabulary is to facilitate the exchange of test results between Web accessibility evaluation tools in a vendor-neutral and platform-independent format. It also provides reusable terms for generic quality assurance and validation purposes. While this document describes the motivations for EARL and provides an introduction to its uses, other specifications define the core terms of the vocabulary, Evaluation and Report Language (EARL) 1.0 Schema, and provide additional terms for representing HTTP exchanges between clients and servers, HTTP Vocabulary in RDF 1.0, for representing web content itself, Representing Content in RDF 1.0, or for specifying particular locations within or sections of content, Pointer methods in RDF 1.0. An Evaluation and Report Language (EARL) Overview is also available.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-EARL10-Guide-20091029</howpublished>
		<title type="sharef:primaryTitle">Evaluation and Report Language (EARL) 1.0 Guide</title>
		<field type="bibtex:topic">earl[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2009/WD-EARL10-Guide-20091029</identifier>
	</reference>
	<reference name="svg" src="bibtex:misc" src-info="bibtex:line-34897" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Jon</givenname>
				<surname>Ferraiolo</surname>
			</person>
		</names>
		<date value="2001-09"/>
		<abstract>
			<richtext>
				<p>This specification defines the features and syntax for Scalable Vector Graphics (SVG), a language for describing two-dimensional vector and mixed vector/raster graphics in XML.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Recommendation REC-SVG-20010904</howpublished>
		<title type="sharef:primaryTitle">Scalable Vector Graphics (SVG) 1.0 Specification</title>
		<field type="bibtex:topic">svg[1]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2001/REC-SVG-20010904</identifier>
	</reference>
	<reference name="svg11" src="bibtex:misc" src-info="bibtex:line-34908" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Jon</givenname>
				<surname>Ferraiolo</surname>
			</person>
			<person>
				<givenname>Jun</givenname>
				<surname>Fujisawa</surname>
			</person>
			<person>
				<givenname>Dean</givenname>
				<surname>Jackson</surname>
			</person>
		</names>
		<date value="2003-01"/>
		<abstract>
			<richtext>
				<p>This specification defines the features and syntax for Scalable Vector Graphics (SVG) Version 1.1, a modularized language for describing two-dimensional vector and mixed vector/raster graphics in XML.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Recommendation REC-SVG11-20030114</howpublished>
		<title type="sharef:primaryTitle">Scalable Vector Graphics (SVG) 1.1 Specification</title>
		<field type="bibtex:topic">svg[1]</field>
		<field type="bibtex:updates">svg</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2003/REC-SVG11-20030114</identifier>
	</reference>
	<reference name="svg11second" src="bibtex:misc" src-info="bibtex:line-34920" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Erik</givenname>
				<surname>Dahlström</surname>
			</person>
			<person>
				<givenname>Jon</givenname>
				<surname>Ferraiolo</surname>
			</person>
			<person>
				<givenname>Jun</givenname>
				<surname>Fujisawa</surname>
			</person>
			<person>
				<givenname>Anthony</givenname>
				<surname>Grasso</surname>
			</person>
			<person>
				<givenname>Dean</givenname>
				<surname>Jackson</surname>
			</person>
			<person>
				<givenname>Chris</givenname>
				<surname>Lilley</surname>
			</person>
			<person>
				<givenname>Cameron</givenname>
				<surname>McCormack</surname>
			</person>
			<person>
				<givenname>Doug</givenname>
				<surname>Schepers</surname>
			</person>
			<person>
				<givenname>Jonathan</givenname>
				<surname>Watt</surname>
			</person>
			<person>
				<givenname>Patrick</givenname>
				<surname>Dengler</surname>
			</person>
		</names>
		<date value="2010-06"/>
		<abstract>
			<richtext>
				<p>This specification defines the features and syntax for Scalable Vector Graphics (SVG) Version 1.1, a modularized language for describing two-dimensional vector and mixed vector/raster graphics in XML.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-SVG11-20100622</howpublished>
		<title type="sharef:primaryTitle">Scalable Vector Graphics (SVG) 1.1 (Second Edition)</title>
		<field type="bibtex:topic">svg[1]</field>
		<field type="bibtex:updates">svg11</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2010/WD-SVG11-20100622</identifier>
	</reference>
	<reference name="svg12" src="bibtex:misc" src-info="bibtex:line-34932" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Dean</givenname>
				<surname>Jackson</surname>
			</person>
			<person>
				<givenname>Craig</givenname>
				<surname>Northway</surname>
			</person>
		</names>
		<date value="2005-04"/>
		<abstract>
			<richtext>
				<p>This specification is a placeholder for an updated draft of the Scalable Vector Graphics (SVG) Full, Version 1.2 specification. SVG is a modularized XML language for describing two-dimensional graphics with animation and interactivity, and a set of APIs upon which to build graphics-based applications. The next draft of SVG 1.2 Full will structured as a superset of the SVG 1.2 Tiny language extending the declarative, interactive and API functionality available.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-SVG12-20050413</howpublished>
		<title type="sharef:primaryTitle">Scalable Vector Graphics (SVG) Full 1.2 Specification</title>
		<field type="bibtex:topic">svg[1] rcc[1]</field>
		<field type="bibtex:updates">svg11</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2005/WD-SVG12-20050413</identifier>
	</reference>
	<reference name="svg12colorprimer" src="bibtex:misc" src-info="bibtex:line-34944" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Chris</givenname>
				<surname>Lilley</surname>
			</person>
			<person>
				<givenname>Anthony</givenname>
				<surname>Grasso</surname>
			</person>
		</names>
		<date value="2009-10"/>
		<abstract>
			<richtext>
				<p>This Working Draft is a primer for use of the Scalable Vector Graphics (SVG) Language for color managed workflows. It explains the technical background and gives guidelines on how to use the SVG Color specification with SVG 1.2 Tiny and SVG 1.2 Full modules. It is purely informative and has no conformance statements.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-SVGColorPrimer12-20091001</howpublished>
		<title type="sharef:primaryTitle">SVG Color 1.2, Part 1: Primer</title>
		<field type="bibtex:topic">svg[1]</field>
		<field type="bibtex:updates">svg12</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2009/WD-SVGColorPrimer12-20091001</identifier>
	</reference>
	<reference name="svg12color" src="bibtex:misc" src-info="bibtex:line-34956" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Chris</givenname>
				<surname>Lilley</surname>
			</person>
			<person>
				<givenname>Anthony</givenname>
				<surname>Grasso</surname>
			</person>
		</names>
		<date value="2009-10"/>
		<abstract>
			<richtext>
				<p>This Working Draft defines features of the Scalable Vector Graphics (SVG) Language that are specifically for color-managed environments.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-SVGColor12-20091001</howpublished>
		<title type="sharef:primaryTitle">SVG Color 1.2, Part 2: Language</title>
		<field type="bibtex:topic">svg[1]</field>
		<field type="bibtex:updates">svg12</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2009/WD-SVGColor12-20091001</identifier>
	</reference>
	<reference name="svg2req" src="bibtex:misc" src-info="bibtex:line-34968" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Dean</givenname>
				<surname>Jackson</surname>
			</person>
		</names>
		<date value="2002-04"/>
		<howpublished>World Wide Web Consortium, Working Draft WD-SVG2Reqs-20020422</howpublished>
		<title type="sharef:primaryTitle">SVG 1.1/1.2/2.0 Requirements</title>
		<field type="bibtex:topic">svg[1]</field>
		<field type="bibtex:updates">svg11</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2002/WD-SVG2Reqs-20020422</identifier>
	</reference>
	<reference name="svgprintreq" src="bibtex:misc" src-info="bibtex:line-34979" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Jun</givenname>
				<surname>Fujisawa</surname>
			</person>
			<person>
				<givenname>Lee</givenname>
				<surname>Klosterman</surname>
			</person>
			<person>
				<givenname>Craig</givenname>
				<surname>Brown</surname>
			</person>
			<person>
				<givenname>Alex</givenname>
				<surname>Danilo</surname>
			</person>
		</names>
		<date value="2003-02"/>
		<howpublished>World Wide Web Consortium, Working Draft WD-SVGPrintReqs-20030218</howpublished>
		<title type="sharef:primaryTitle">SVG Printing Requirements</title>
		<field type="bibtex:topic">svg[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2003/WD-SVGPrintReqs-20030218</identifier>
	</reference>
	<reference name="svgprint" src="bibtex:misc" src-info="bibtex:line-34989" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Alex</givenname>
				<surname>Danilo</surname>
			</person>
		</names>
		<date value="2003-07"/>
		<abstract>
			<richtext>
				<p>This Working Draft specifies use of the Scalable Vector Graphics (SVG) Language for printing environments.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-SVGPrint-20030715</howpublished>
		<title type="sharef:primaryTitle">SVG Print</title>
		<field type="bibtex:topic">svg[0.9]</field>
		<field type="bibtex:updates">svgprintreq</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2003/WD-SVGPrint-20030715</identifier>
	</reference>
	<reference name="svgprint12" src="bibtex:misc" src-info="bibtex:line-35001" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Alex</givenname>
				<surname>Danilo</surname>
			</person>
			<person>
				<givenname>Craig</givenname>
				<surname>Northway</surname>
			</person>
			<person>
				<givenname>Andrew</givenname>
				<surname>Shellshear</surname>
			</person>
			<person>
				<givenname>Anthony</givenname>
				<surname>Grasso</surname>
			</person>
			<person>
				<givenname>Chris</givenname>
				<surname>Lilley</surname>
			</person>
		</names>
		<date value="2007-12"/>
		<abstract>
			<richtext>
				<p>This Working Draft defines features of the Scalable Vector Graphics (SVG) Language that are specifically for printing environments.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-SVGPrint12-20071221</howpublished>
		<title type="sharef:primaryTitle">SVG Print 1.2, Part 2: Language</title>
		<field type="bibtex:topic">svg[0.9]</field>
		<field type="bibtex:updates">svgprint</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2007/WD-SVGPrint12-20071221</identifier>
	</reference>
	<reference name="svgprintprimer12" src="bibtex:misc" src-info="bibtex:line-35013" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Anthony</givenname>
				<surname>Grasso</surname>
			</person>
			<person>
				<givenname>Andrew</givenname>
				<surname>Shellshear</surname>
			</person>
			<person>
				<givenname>Chris</givenname>
				<surname>Lilley</surname>
			</person>
		</names>
		<date value="2007-12"/>
		<abstract>
			<richtext>
				<p>This Working Draft is a primer for use of the Scalable Vector Graphics (SVG) Language for printing environments. It explains the technical background and gives guidelines on how to use the SVG Print specification with SVG 1.2 Tiny and SVG 1.2 Full modules for printing. It is purely informative and has no conformance statements.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-SVGPrintPrimer12-20071221</howpublished>
		<title type="sharef:primaryTitle">SVG Print 1.2, Part 1: Primer</title>
		<field type="bibtex:topic">svg[0.8]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2007/WD-SVGPrintPrimer12-20071221</identifier>
	</reference>
	<reference name="svgfilterreqs" src="bibtex:misc" src-info="bibtex:line-35024" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Erik</givenname>
				<surname>Dahlström</surname>
			</person>
		</names>
		<date value="2007-05"/>
		<abstract>
			<richtext>
				<p>This document lists the design principles and requirements for the creation of a SVG specification related to filters.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-SVGFilterReqs12-20070501</howpublished>
		<title type="sharef:primaryTitle">SVG Filter Requirements</title>
		<field type="bibtex:topic">svg[0.8]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2007/WD-SVGFilterReqs12-20070501</identifier>
	</reference>
	<reference name="svgfilterprimer12" src="bibtex:misc" src-info="bibtex:line-35035" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Erik</givenname>
				<surname>Dahlström</surname>
			</person>
		</names>
		<date value="2007-05"/>
		<abstract>
			<richtext>
				<p>SVG is language for describing vector graphics, however it's typically rendered on raster displays. SVG filter effects is a way of processing the generated raster image before it's displayed. Although originally designed for use in SVG, filter effects are defined in XML and are accessed via a presentation property, and therefore could be used in other environments, such as HTML styled with CSS and XSL:FO. This document introduces the features used by SVG filters.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-SVGFilterPrimer12-20070501</howpublished>
		<title type="sharef:primaryTitle">SVG Filters 1.2, Part 1: Primer</title>
		<field type="bibtex:topic">svg[0.8]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2007/WD-SVGFilterPrimer12-20070501</identifier>
	</reference>
	<reference name="svgfilter12" src="bibtex:misc" src-info="bibtex:line-35046" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Erik</givenname>
				<surname>Dahlström</surname>
			</person>
		</names>
		<date value="2007-05"/>
		<abstract>
			<richtext>
				<p>SVG is language for describing vector graphics, however it's typically rendered on raster displays. SVG filter effects is a way of processing the generated raster image before it's displayed. Although originally designed for use in SVG, filter effects are defined in XML and are accessed via a presentation property, and therefore could be used in other environments, such as HTML styled with CSS and XSL:FO. This document defines the markup used by SVG filters.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-SVGFilter12-20070501</howpublished>
		<title type="sharef:primaryTitle">SVG Filters 1.2, Part 2: Language</title>
		<field type="bibtex:topic">svg[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2007/WD-SVGFilter12-20070501</identifier>
	</reference>
	<reference name="svgmobile" src="bibtex:misc" src-info="bibtex:line-35057" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Tolga</givenname>
				<surname>Capin</surname>
			</person>
		</names>
		<date value="2003-01"/>
		<howpublished>World Wide Web Consortium, Recommendation REC-SVGMobile-20030114</howpublished>
		<title type="sharef:primaryTitle">Mobile SVG Profiles: SVG Tiny and SVG Basic</title>
		<field type="bibtex:topic">svg[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2003/REC-SVGMobile-20030114</identifier>
	</reference>
	<reference name="svgtiny12reqs" src="bibtex:misc" src-info="bibtex:line-35067" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Andrew</givenname>
				<surname>Emmons</surname>
			</person>
		</names>
		<date value="2006-08"/>
		<abstract>
			<richtext>
				<p>This document specifies requirements for SVG Tiny 1.2, a backwardly-compatible update of SVG Tiny 1.1 which adds some new features from SVG 1.2 add adds other features based on implementor and designer feedback on SVG Tiny 1.1.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-SVGTiny12Reqs-20060810</howpublished>
		<title type="sharef:primaryTitle">SVG Tiny Version 1.2 Requirements</title>
		<field type="bibtex:topic">svg[0.9]</field>
		<field type="bibtex:updates">svgmobile</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2006/WD-SVGTiny12Reqs-20060810</identifier>
	</reference>
	<reference name="svgmobile12" src="bibtex:misc" src-info="bibtex:line-35079" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Ola</givenname>
				<surname>Andersson</surname>
			</person>
			<person>
				<givenname>Robin</givenname>
				<surname>Berjon</surname>
			</person>
			<person>
				<givenname>Erik</givenname>
				<surname>Dahlström</surname>
			</person>
			<person>
				<givenname>Andrew</givenname>
				<surname>Emmons</surname>
			</person>
			<person>
				<givenname>Jon</givenname>
				<surname>Ferraiolo</surname>
			</person>
			<person>
				<givenname>Anthony</givenname>
				<surname>Grasso</surname>
			</person>
			<person>
				<givenname>Vincent</givenname>
				<surname>Hardy</surname>
			</person>
			<person>
				<givenname>Scott</givenname>
				<surname>Hayman</surname>
			</person>
			<person>
				<givenname>Dean</givenname>
				<surname>Jackson</surname>
			</person>
			<person>
				<givenname>Chris</givenname>
				<surname>Lilley</surname>
			</person>
			<person>
				<givenname>Cameron</givenname>
				<surname>McCormack</surname>
			</person>
			<person>
				<givenname>Andreas</givenname>
				<surname>Neumann</surname>
			</person>
			<person>
				<givenname>Craig</givenname>
				<surname>Northway</surname>
			</person>
			<person>
				<givenname>Antoine</givenname>
				<surname>Quint</surname>
			</person>
			<person>
				<givenname>Nandini</givenname>
				<surname>Ramani</surname>
			</person>
			<person>
				<givenname>Doug</givenname>
				<surname>Schepers</surname>
			</person>
			<person>
				<givenname>Andrew</givenname>
				<surname>Shellshear</surname>
			</person>
		</names>
		<date value="2008-12"/>
		<abstract>
			<richtext>
				<p>This specification defines the features and syntax for Scalable Vector Graphics (SVG) Tiny, Version 1.2, a language for describing two-dimensional vector graphics in XML, combined with raster graphics and multimedia. Its goal is to provide the ability to create a whole range of graphical content, from static images to animations to interactive Web applications. SVG 1.2 Tiny is a profile of SVG intended for implementation on a range of devices, from cellphones and PDAs to laptop and desktop computers, and thus includes a subset of the features included in SVG 1.1 Full, along with new features to extend the capabilities of SVG. Further extensions are planned in the form of modules which will be compatible with SVG 1.2 Tiny, and which when combined with this specification, will match and exceed the capabilities of SVG 1.1 Full.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Recommendation REC-SVGTiny12-20081222</howpublished>
		<title type="sharef:primaryTitle">Scalable Vector Graphics (SVG) Tiny 1.2 Specification</title>
		<field type="bibtex:topic">svg[1]</field>
		<field type="bibtex:updates">svgmobile svgtiny12reqs</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2008/REC-SVGTiny12-20081222</identifier>
	</reference>
	<reference name="sxbl" src="bibtex:misc" src-info="bibtex:line-35091" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Jon</givenname>
				<surname>Ferraiolo</surname>
			</person>
			<person>
				<givenname>Ian</givenname>
				<surname>Hickson</surname>
			</person>
			<person>
				<givenname>David</givenname>
				<surname>Hyatt</surname>
			</person>
		</names>
		<date value="2005-08"/>
		<abstract>
			<richtext>
				<p>This working draft describes SVG's XML Binding Language (sXBL). sXBL is a mechanism for defining the presentation and interactive behavior of elements described in a namespace other than SVG's. sXBL is intended to be used to enable XML vocabularies (tag sets) to be implemented in terms of SVG elements. For instance, a tag set describing a flowchart could be mapped to low-level SVG path and text elements, possibly including interactivity and animation. sXBL is intended to be an SVG-specific first version of a more general-purpose XBL specification (e.g., "XBL 2.0"). The intent is that, in the future, a general-purpose and modularly-defined XBL specification will be developed which will replace this specification and will define additional features that are necessary to support scenarios beyond SVG, such as integration into web browsers that support CSS. Once a general-purpose XBL is defined, sXBL would just become an SVG-specific subset (i.e., a profile) of the larger XBL specification.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-sXBL-20050815</howpublished>
		<title type="sharef:primaryTitle">SVG's XML Binding Language (sXBL)</title>
		<field type="bibtex:topic">svg[0.9] sxbl[1] xbl[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2005/WD-sXBL-20050815</identifier>
	</reference>
	<reference name="svgtransforms" src="bibtex:misc" src-info="bibtex:line-35102" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Jun</givenname>
				<surname>Fujisawa</surname>
			</person>
			<person>
				<givenname>Anthony</givenname>
				<surname>Grasso</surname>
			</person>
		</names>
		<date value="2009-03"/>
		<abstract>
			<richtext>
				<p>This working draft defines features of the Scalable Vector Graphics (SVG) Language that are specifically for display environments. This document defines the markup used by SVG Transforms. SVG Transforms allows two-dimensional objects to be transformed using three-dimensional transformations. Although originally designed for use in SVG, some aspects of this specification are defined in XML and are accessed via presentation properties, and therefore could be used in other environments, such as HTML styled with CSS and XSL-FO. This document defines the markup used by SVG Transforms.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-SVG-Transforms-20090320</howpublished>
		<title type="sharef:primaryTitle">SVG Transforms 1.0, Part 2: Language</title>
		<field type="bibtex:topic">svg[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2009/WD-SVG-Transforms-20090320</identifier>
	</reference>
	<reference name="svgparamprimer" src="bibtex:misc" src-info="bibtex:line-35113" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Doug</givenname>
				<surname>Schepers</surname>
			</person>
		</names>
		<date value="2009-06"/>
		<abstract>
			<richtext>
				<p>The SVG Parameters specification is an SVG 2.0 Module to provide a declarative way to incorporate parameter values into SVG content. Often, users may wish to create a single resource, and reuse it several times with specified variations, and this specification provides a means to do so without the use of script. Although originally designed for use in SVG, some aspects of this specification are defined in XML and are accessed via presentation properties, and therefore could be used in other environments, such as HTML styled with CSS and XSL:FO. This document introduces the features used by SVG Parameters, for the use of the average developer or author.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-SVGParamPrimer-20090616</howpublished>
		<title type="sharef:primaryTitle">SVG Referenced Parameter Variables 1.0, Part 1: Primer</title>
		<field type="bibtex:topic">svg[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2009/WD-SVGParamPrimer-20090616</identifier>
	</reference>
	<reference name="svgparam" src="bibtex:misc" src-info="bibtex:line-35124" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Doug</givenname>
				<surname>Schepers</surname>
			</person>
		</names>
		<date value="2009-06"/>
		<abstract>
			<richtext>
				<p>The SVG Parameters specification is an SVG 2.0 Module to provide a declarative way to incorporate parameter values into SVG content. Often, users may wish to create a single resource, and reuse it several times with specified variations, and this specification provides a means to do so without the use of script. Although originally designed for use in SVG, some aspects of this specification are defined in XML and are accessed via presentation properties, and therefore could be used in other environments, such as HTML styled with CSS and XSL:FO. This document defines the markup and interfaces used by SVG Parameters.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-SVGParam-20090616</howpublished>
		<title type="sharef:primaryTitle">SVG Referenced Parameter Variables 1.0, Part 2: Language</title>
		<field type="bibtex:topic">svg[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2009/WD-SVGParam-20090616</identifier>
	</reference>
	<reference name="svgcompositing" src="bibtex:misc" src-info="bibtex:line-35135" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Anthony</givenname>
				<surname>Grasso</surname>
			</person>
		</names>
		<date value="2011-03"/>
		<abstract>
			<richtext>
				<p>SVG is a language for describing vector graphics, but it is typically rendered to a display or some form of print medium. The SVG Compositing module adds support for the full range of Porter and Duff operators and blending modes. The module allows for raster and vector objects to be combined to produce eye catching effects. This document defines the markup used by SVG Compositing for display and printing environments. It explains the technical background and gives guidelines on how to use the SVG Compositing specification with the SVG 1.1 Full and SVG 1.2 Tiny specifications and other SVG modules.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-SVGCompositing-20110315</howpublished>
		<title type="sharef:primaryTitle">SVG Compositing Specification</title>
		<field type="bibtex:topic">svg[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2011/WD-SVGCompositing-20110315</identifier>
	</reference>
	<reference name="xbl" src="bibtex:misc" src-info="bibtex:line-35146" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>David</givenname>
				<surname>Hyatt</surname>
			</person>
		</names>
		<date value="2001-02"/>
		<abstract>
			<richtext>
				<p>This note outlines the XML Binding Language. XBL is a markup language for describing bindings that can be attached to elements in other documents. Bindings can be attached to elements using either cascading stylesheets (CSS) or the document object model (DOM). The element that the binding is attached to, called the bound element, acquires the new behavior specified by the binding. Bindings can contain event handlers that are registered on the bound element, an implementation of new methods and properties that become accessible from the bound element, and anonymous content that is inserted underneath the bound element.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Note NOTE-xbl-20010223</howpublished>
		<title type="sharef:primaryTitle">XBL — XML Binding Language</title>
		<field type="bibtex:topic">xbl[1]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2001/NOTE-xbl-20010223</identifier>
	</reference>
	<reference name="xbl20" src="bibtex:misc" src-info="bibtex:line-35157" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Ian</givenname>
				<surname>Hickson</surname>
			</person>
		</names>
		<date value="2007-03"/>
		<abstract>
			<richtext>
				<p>This specification describes the ability to map elements to script, event handlers, CSS, and more complex content models. This can be used to re-order and wrap content so that, for instance, simple HTML or XHTML markup can have complex CSS styles applied without requiring that the markup be polluted with multiple semantically neutral div elements. It can also be used to implement new DOM interfaces, and, in conjunction with other specifications, enables arbitrary tag sets to be implemented as widgets. For example, XBL could in theory be used to implement XForms.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Candidate Recommendation CR-xbl-20070316</howpublished>
		<title type="sharef:primaryTitle">XML Binding Language (XBL) 2.0</title>
		<field type="bibtex:topic">xbl[1]</field>
		<field type="bibtex:updates">xbl</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2007/CR-xbl-20070316</identifier>
	</reference>
	<reference name="xblprimer" src="bibtex:misc" src-info="bibtex:line-35169" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Lachlan</givenname>
				<surname>Hunt</surname>
			</person>
			<person>
				<givenname>Marcos</givenname>
				<surname>Cáceres</surname>
			</person>
		</names>
		<date value="2007-07"/>
		<abstract>
			<richtext>
				<p>This practical guide provides you with the knowledge required to effectively use the XML Binding Language 2.0. It introduces both the basic and advanced concepts of XBL and describes its syntax and scenarios that should be considered best-practice. It also describes the purpose of the language elements described in the XBL 2.0 specification. XBL describes the ability to associate elements in one document with script, event handlers, styles, and more complex content models in another document. You can use XBL to re-order and wrap content so that, for instance, simple HTML or XHTML markup can have complex CSS styles applied without requiring that the markup be polluted with multiple div elements. In addition, if you are a programmer, you can use XBL to implement new DOM interfaces, and, in conjunction with other specifications, it enables arbitrary XML tag sets to be treated as "widgets" (pluggable user interface components).</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-xbl-primer-20070718</howpublished>
		<title type="sharef:primaryTitle">XBL 2.0 Primer: An Introduction for Developers</title>
		<field type="bibtex:topic">xbl[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2007/WD-xbl-primer-20070718</identifier>
	</reference>
	<reference name="mathml" src="bibtex:misc" src-info="bibtex:line-35180" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Patrick</givenname>
				<surname>Ion</surname>
			</person>
			<person>
				<givenname>Robert</givenname>
				<surname>Miner</surname>
			</person>
		</names>
		<date value="1999-07"/>
		<howpublished>World Wide Web Consortium, Recommendation REC-MathML-19990707</howpublished>
		<title type="sharef:primaryTitle">Mathematical Markup Language (MathML) 1.01 Specification</title>
		<field type="bibtex:topic">xml[0.4] mathml[1]</field>
		<identifier type="sharef:uri">http://www.w3.org/1999/07/REC-MathML-19990707</identifier>
	</reference>
	<reference name="mathml2" src="bibtex:misc" src-info="bibtex:line-35190" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>David</givenname>
				<surname>Carlisle</surname>
			</person>
			<person>
				<givenname>Patrick</givenname>
				<surname>Ion</surname>
			</person>
			<person>
				<givenname>Robert</givenname>
				<surname>Miner</surname>
			</person>
			<person>
				<givenname>Nico</givenname>
				<surname>Poppelier</surname>
			</person>
		</names>
		<date value="2001-02"/>
		<abstract>
			<richtext>
				<p>This specification defines the Mathematical Markup Language, or MathML. MathML is an XML application for describing mathematical notation and capturing both its structure and content. The goal of MathML is to enable mathematics to be served, received, and processed on the World Wide Web, just as HTML has enabled this functionality for text. This specification of the markup language MathML is intended primarily for a readership consisting of those who will be developing or implementing renderers or editors using it, or software that will communicate using MathML as a protocol for input or output. It is not a User's Guide but rather a reference document. This document begins with background information on mathematical notation, the problems it poses, and the philosophy underlying the solutions MathML 2.0 proposes. MathML can be used to encode both mathematical notation and mathematical content. About thirty of the MathML tags describe abstract notational structures, while another about one hundred and fifty provide a way of unambiguously specifying the intended meaning of an expression. Additional chapters discuss how the MathML content and presentation elements interact, and how MathML renderers might be implemented and should interact with browsers. Finally, this document addresses the issue of MathML characters and their relation to fonts. While MathML is human-readable, it is anticipated that, in all but the simplest cases, authors will use equation editors, conversion programs, and other specialized software tools to generate MathML. Several early versions of such MathML tools already exist, and a number of others, both freely available software and commercial products, are under development.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Recommendation REC-MathML2-20010221</howpublished>
		<title type="sharef:primaryTitle">Mathematical Markup Language (MathML) Version 2.0</title>
		<field type="bibtex:topic">xml[0.4] mathml[1]</field>
		<field type="bibtex:updates">mathml</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2001/REC-MathML2-20010221</identifier>
	</reference>
	<reference name="mathml2sec" src="bibtex:misc" src-info="bibtex:line-35202" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Ron</givenname>
				<surname>Ausbrooks</surname>
			</person>
			<person>
				<givenname>Stephen</givenname>
				<surname>Buswell</surname>
			</person>
			<person>
				<givenname>David</givenname>
				<surname>Carlisle</surname>
			</person>
			<person>
				<givenname>Stéphane</givenname>
				<surname>Dalmas</surname>
			</person>
			<person>
				<givenname>Stan</givenname>
				<surname>Devitt</surname>
			</person>
			<person>
				<givenname>Angel</givenname>
				<surname>Diaz</surname>
			</person>
			<person>
				<givenname>Max</givenname>
				<surname>Froumentin</surname>
			</person>
			<person>
				<givenname>Roger</givenname>
				<surname>Hunter</surname>
			</person>
			<person>
				<givenname>Patrick</givenname>
				<surname>Ion</surname>
			</person>
			<person>
				<givenname>Michael</givenname>
				<surname>Kohlhase</surname>
			</person>
			<person>
				<givenname>Robert</givenname>
				<surname>Miner</surname>
			</person>
			<person>
				<givenname>Nico</givenname>
				<surname>Poppelier</surname>
			</person>
			<person>
				<givenname>Bruce</givenname>
				<surname>Smith</surname>
			</person>
			<person>
				<givenname>Neil</givenname>
				<surname>Soiffer</surname>
			</person>
			<person>
				<givenname>Robert</givenname>
				<surname>Sutor</surname>
			</person>
			<person>
				<givenname>Stephen M.</givenname>
				<surname>Watt</surname>
			</person>
		</names>
		<names type="sharef:editor">
			<person>
				<givenname>David</givenname>
				<surname>Carlisle</surname>
			</person>
			<person>
				<givenname>Patrick</givenname>
				<surname>Ion</surname>
			</person>
			<person>
				<givenname>Robert</givenname>
				<surname>Miner</surname>
			</person>
			<person>
				<givenname>Nico</givenname>
				<surname>Poppelier</surname>
			</person>
		</names>
		<date value="2003-10"/>
		<abstract>
			<richtext>
				<p>This specification defines the Mathematical Markup Language, or MathML. MathML is an XML application for describing mathematical notation and capturing both its structure and content. The goal of MathML is to enable mathematics to be served, received, and processed on the World Wide Web, just as HTML has enabled this functionality for text. This specification of the markup language MathML is intended primarily for a readership consisting of those who will be developing or implementing renderers or editors using it, or software that will communicate using MathML as a protocol for input or output. It is not a User's Guide but rather a reference document. This document begins with background information on mathematical notation, the problems it poses, and the philosophy underlying the solutions MathML 2.0 proposes. MathML can be used to encode both mathematical notation and mathematical content. About thirty of the MathML tags describe abstract notational structures, while another about one hundred and fifty provide a way of unambiguously specifying the intended meaning of an expression. Additional chapters discuss how the MathML content and presentation elements interact, and how MathML renderers might be implemented and should interact with browsers. Finally, this document addresses the issue of MathML characters and their relation to fonts. While MathML is human-readable, it is anticipated that, in all but the simplest cases, authors will use equation editors, conversion programs, and other specialized software tools to generate MathML. Several versions of such MathML tools already exist, and a number of others, both freely available software and commercial products, are under development.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Recommendation REC-MathML2-20031021</howpublished>
		<title type="sharef:primaryTitle">Mathematical Markup Language (MathML) Version 2.0 (2nd Edition)</title>
		<field type="bibtex:topic">xml[0.4] mathml[1]</field>
		<field type="bibtex:updates">mathml2</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2003/REC-MathML2-20031021</identifier>
	</reference>
	<reference name="mathml3" src="bibtex:misc" src-info="bibtex:line-35215" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>David</givenname>
				<surname>Carlisle</surname>
			</person>
			<person>
				<givenname>Patrick</givenname>
				<surname>Ion</surname>
			</person>
			<person>
				<givenname>Robert</givenname>
				<surname>Miner</surname>
			</person>
		</names>
		<date value="2010-10"/>
		<abstract>
			<richtext>
				<p>This specification defines the Mathematical Markup Language, or MathML. MathML is an XML application for describing mathematical notation and capturing both its structure and content. The goal of MathML is to enable mathematics to be served, received, and processed on the World Wide Web, just as HTML has enabled this functionality for text. This specification of the markup language MathML is intended primarily for a readership consisting of those who will be developing or implementing renderers or editors using it, or software that will communicate using MathML as a protocol for input or output. It is not a User's Guide but rather a reference document. MathML can be used to encode both mathematical notation and mathematical content. About thirty-eight of the MathML tags describe abstract notational structures, while another about one hundred and seventy provide a way of unambiguously specifying the intended meaning of an expression. Additional chapters discuss how the MathML content and presentation elements interact, and how MathML renderers might be implemented and should interact with browsers. Finally, this document addresses the issue of special characters used for mathematics, their handling in MathML, their presence in Unicode, and their relation to fonts. While MathML is human-readable, authors typically will use equation editors, conversion programs, and other specialized software tools to generate MathML. Several versions of such MathML tools exist, both freely available software and commercial products, and more are under development.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Recommendation REC-MathML3-20101021</howpublished>
		<title type="sharef:primaryTitle">Mathematical Markup Language (MathML) Version 3.0</title>
		<field type="bibtex:topic">mathml[1]</field>
		<field type="bibtex:updates">mathml2sec</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2010/REC-MathML3-20101021</identifier>
	</reference>
	<reference name="mathmlforcss" src="bibtex:misc" src-info="bibtex:line-35227" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Bert</givenname>
				<surname>Bos</surname>
			</person>
			<person>
				<givenname>David</givenname>
				<surname>Carlisle</surname>
			</person>
			<person>
				<givenname>George</givenname>
				<surname>Chavchanidze</surname>
			</person>
			<person>
				<givenname>Patrick D. F.</givenname>
				<surname>Ion</surname>
			</person>
			<person>
				<givenname>Bruce R.</givenname>
				<surname>Miller</surname>
			</person>
		</names>
		<date value="2010-08"/>
		<abstract>
			<richtext>
				<p>This document describes a profile of MathML 3.0 that admits formatting with Cascading Style Sheets.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Proposed Recommendation PR-mathml-for-css-20100810</howpublished>
		<title type="sharef:primaryTitle">A MathML for CSS Profile</title>
		<field type="bibtex:topic">mathml[0.8]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2010/PR-mathml-for-css-20100810</identifier>
	</reference>
	<reference name="mathmltypes" src="bibtex:misc" src-info="bibtex:line-35238" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Stan</givenname>
				<surname>Devitt</surname>
			</person>
			<person>
				<givenname>Michael</givenname>
				<surname>Kohlhase</surname>
			</person>
			<person>
				<givenname>Max</givenname>
				<surname>Froumentin</surname>
			</person>
		</names>
		<date value="2003-11"/>
		<abstract>
			<richtext>
				<p>This Note discusses the facilities that are available in the MathML 2.0 Recommendation to facilitate the capturing of mathematical type information. It demonstrates how a combination of these features can be systematically used to provide support for general mathematical types.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Note NOTE-mathml-types-20031110</howpublished>
		<title type="sharef:primaryTitle">Structured Types in MathML 2.0</title>
		<field type="bibtex:topic">mathml[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2003/NOTE-mathml-types-20031110</identifier>
	</reference>
	<reference name="mathmlunits" src="bibtex:misc" src-info="bibtex:line-35249" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Douglas Wilhelm</givenname>
				<surname>Harder</surname>
			</person>
			<person>
				<givenname>Stan</givenname>
				<surname>Devitt</surname>
			</person>
		</names>
		<date value="2003-11"/>
		<howpublished>World Wide Web Consortium, Note NOTE-mathml-units-20031110</howpublished>
		<title type="sharef:primaryTitle">Units in MathML</title>
		<field type="bibtex:topic">mathml[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2003/NOTE-mathml-units-20031110</identifier>
	</reference>
	<reference name="mathmlbvar" src="bibtex:misc" src-info="bibtex:line-35259" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Stan</givenname>
				<surname>Devitt</surname>
			</person>
			<person>
				<givenname>Michael</givenname>
				<surname>Kohlhase</surname>
			</person>
		</names>
		<date value="2003-11"/>
		<howpublished>World Wide Web Consortium, Note NOTE-mathml-bvar-20031110</howpublished>
		<title type="sharef:primaryTitle">Bound Variables in MathML</title>
		<field type="bibtex:topic">mathml[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2003/NOTE-mathml-bvar-20031110</identifier>
	</reference>
	<reference name="arabicmath" src="bibtex:misc" src-info="bibtex:line-35269" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Azzeddine</givenname>
				<surname>Lazrek</surname>
			</person>
			<person>
				<givenname>Mustapha</givenname>
				<surname>Eddahibi</surname>
			</person>
			<person>
				<givenname>Khalid</givenname>
				<surname>Sami</surname>
			</person>
			<person>
				<givenname>Bruce R.</givenname>
				<surname>Miller</surname>
			</person>
		</names>
		<date value="2006-01"/>
		<abstract>
			<richtext>
				<p>This Note analyzes potential problems with the use of MathML for the presentation of mathematics in the notations customarily used with Arabic, and related languages. The goal is to clarify avoidable implementation details that hinder such presentation, as well as to uncover genuine limitations in the specification. These limitations in the MathML specification may require extensions in future versions of the specification.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Note NOTE-arabic-math-20060131</howpublished>
		<title type="sharef:primaryTitle">Arabic Mathematical Notation</title>
		<field type="bibtex:topic">mathml[0.7]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2006/NOTE-arabic-math-20060131</identifier>
	</reference>
	<reference name="xmlentitynames" src="bibtex:misc" src-info="bibtex:line-35280" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>David</givenname>
				<surname>Carlisle</surname>
			</person>
			<person>
				<givenname>Patrick</givenname>
				<surname>Ion</surname>
			</person>
		</names>
		<date value="2010-04"/>
		<abstract>
			<richtext>
				<p>This document defines several sets of names, so that to each name is assigned a Unicode character or sequence of characters. Each of these sets is expressed as a file of XML entity declarations.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Recommendation REC-xml-entity-names-20100401</howpublished>
		<title type="sharef:primaryTitle">XML Entity Definitions for Characters</title>
		<field type="bibtex:topic">xml[0.8] unicode[0.8]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2010/REC-xml-entity-names-20100401</identifier>
	</reference>
	<reference name="xlinknaming" src="bibtex:misc" src-info="bibtex:line-35291" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Eve</givenname>
				<surname>Maler</surname>
			</person>
			<person>
				<givenname>Daniel</givenname>
				<surname>Veillard</surname>
			</person>
			<person>
				<givenname>Henry S.</givenname>
				<surname>Thompson</surname>
			</person>
		</names>
		<date value="2000-12"/>
		<abstract>
			<richtext>
				<p>This document proposes a possible XML Schema-based solution to the need to use XLink in XML-based languages such as XHTML 1.0.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Note NOTE-xlink-naming-20001220</howpublished>
		<title type="sharef:primaryTitle">XLink Markup Name Control</title>
		<field type="bibtex:topic">xml[0.6] xlink[0.8] xsd[0.7]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2000/NOTE-xlink-naming-20001220</identifier>
	</reference>
	<reference name="xlinkstyle" src="bibtex:misc" src-info="bibtex:line-35302" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Norman</givenname>
				<surname>Walsh</surname>
			</person>
		</names>
		<date value="2001-06"/>
		<abstract>
			<richtext>
				<p>The interaction of XLink linking elements and styling has not previously been carefully described. This note, the result of an XML Linking/XSL joint task force, attempts to rectify that oversight by providing a clear conceptual model for linking and styling and suggestions for the practical application of that model using current W3C Recommendations (and Working Drafts, Candidate Recommendations, and Proposed Recommendations).</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Note NOTE-xml-link-style-20010605</howpublished>
		<title type="sharef:primaryTitle">XML Linking and Style</title>
		<field type="bibtex:topic">xml[0.6] xlink[0.8] xsl[0.8]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2001/NOTE-xml-link-style-20010605</identifier>
	</reference>
	<reference name="xlinkrdf" src="bibtex:misc" src-info="bibtex:line-35313" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Ron</givenname>
				<surname>Daniel</surname>
			</person>
		</names>
		<date value="2000-09"/>
		<abstract>
			<richtext>
				<p>Both XLink and RDF provide a way of asserting relations between resources. RDF is primarily for describing resources and their relations, while XLink is primarily for specifying and traversing hyperlinks. However, the overlap between the two is sufficient that a mapping from XLink links to statements in an RDF model can be defined. Such a mapping allows XLink elements to be harvested as a source of RDF statements. XLink links (hereafter, "links") thus provide an alternate syntax for RDF information that may be useful in some situations. This Note specifies such a mapping, so that links can be harvested and RDF statements generated. The purpose of this harvesting is to create RDF models that, in some sense, represent the intent of the XML document. The purpose is not to represent the XLink structure in enough detail that a set of links could be round-tripped through an RDF model.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Note NOTE-xlink2rdf-20000929</howpublished>
		<title type="sharef:primaryTitle">Harvesting RDF Statements from XLinks</title>
		<field type="bibtex:topic">xlink[0.9] rdf[0.8]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2000/NOTE-xlink2rdf-20000929</identifier>
	</reference>
	<reference name="xlink" src="bibtex:misc" src-info="bibtex:line-35324" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Steven J.</givenname>
				<surname>DeRose</surname>
			</person>
			<person>
				<givenname>Eve</givenname>
				<surname>Maler</surname>
			</person>
			<person>
				<givenname>David</givenname>
				<surname>Orchard</surname>
			</person>
		</names>
		<date value="2001-06"/>
		<abstract>
			<richtext>
				<p>This specification defines the XML Linking Language (XLink), which allows elements to be inserted into XML documents in order to create and describe links between resources. It uses XML syntax to create structures that can describe links similar to the simple unidirectional hyperlinks of today's HTML, as well as more sophisticated links.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Recommendation REC-xlink-20010627</howpublished>
		<title type="sharef:primaryTitle">XML Linking Language (XLink) Version 1.0</title>
		<field type="bibtex:topic">xml[0.6] xlink[1]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2001/REC-xlink-20010627</identifier>
	</reference>
	<reference name="xlink10ext" src="bibtex:misc" src-info="bibtex:line-35335" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Norman</givenname>
				<surname>Walsh</surname>
			</person>
		</names>
		<date value="2005-01"/>
		<abstract>
			<richtext>
				<p>This document describes some useful changes that could be incorporated into an XLink 1.1 Specification.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Group Note NOTE-xlink10-ext-20050127</howpublished>
		<title type="sharef:primaryTitle">Extending XLink 1.0</title>
		<field type="bibtex:topic">xlink[0.9]</field>
		<field type="bibtex:updates">xlink</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2005/NOTE-xlink10-ext-20050127</identifier>
	</reference>
	<reference name="xlink11" src="bibtex:misc" src-info="bibtex:line-35347" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Steven J.</givenname>
				<surname>DeRose</surname>
			</person>
			<person>
				<givenname>Eve</givenname>
				<surname>Maler</surname>
			</person>
			<person>
				<givenname>David</givenname>
				<surname>Orchard</surname>
			</person>
			<person>
				<givenname>Norman</givenname>
				<surname>Walsh</surname>
			</person>
		</names>
		<date value="2010-02"/>
		<abstract>
			<richtext>
				<p>This specification defines the XML Linking Language (XLink) Version 1.1, which allows elements to be inserted into XML documents in order to create and describe links between resources. It uses XML syntax to create structures that can describe links similar to the simple unidirectional hyperlinks of today's HTML, as well as more sophisticated links.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft PR-xlink11-20100225</howpublished>
		<title type="sharef:primaryTitle">XML Linking Language (XLink) Version 1.1</title>
		<field type="bibtex:topic">xlink[1]</field>
		<field type="bibtex:updates">xlink</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2010/PR-xlink11-20100225</identifier>
	</reference>
	<reference name="hlink" src="bibtex:misc" src-info="bibtex:line-35359" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Steven</givenname>
				<surname>Pemberton</surname>
			</person>
			<person>
				<givenname>Masayasu</givenname>
				<surname>Ishikawa</surname>
			</person>
		</names>
		<date value="2010-12"/>
		<abstract>
			<richtext>
				<p>The HLink module defined in this specification provides XHTML Family Members with the ability to specify which attributes of elements represent Hyperlinks, and how those hyperlinks should be traversed, and extends XLink use to a wider class of languages than those restricted to the syntactic style allowed by XLink.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Note NOTE-hlink-20101216</howpublished>
		<title type="sharef:primaryTitle">HLink: Link recognition for the XHTML Family</title>
		<field type="bibtex:topic">hlink[1]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2010/NOTE-hlink-20101216</identifier>
	</reference>
	<reference name="xindirect" src="bibtex:misc" src-info="bibtex:line-35370" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>W. Eliot</givenname>
				<surname>Kimber</surname>
			</person>
		</names>
		<date value="2003-06"/>
		<abstract>
			<richtext>
				<p>XIndirect is a simple mechanism for using XML to represent indirect addresses in order to augment the core functionality of XLink and XPointer without requiring either of those specifications to themselves require support for indirect addresses. The facilities defined are specifically designed to meet the requirements for systems that support the authoring and management of complex systems of documents.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Note NOTE-XIndirect-20030612</howpublished>
		<title type="sharef:primaryTitle">XML Indirection Facility</title>
		<field type="bibtex:topic">xindirect[1]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2003/NOTE-XIndirect-20030612</identifier>
	</reference>
	<reference name="xptr" src="bibtex:misc" src-info="bibtex:line-35381" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Paul</givenname>
				<surname>Grosso</surname>
			</person>
			<person>
				<givenname>Eve</givenname>
				<surname>Maler</surname>
			</person>
			<person>
				<givenname>Jonathan</givenname>
				<surname>Marsh</surname>
			</person>
			<person>
				<givenname>Norman</givenname>
				<surname>Walsh</surname>
			</person>
		</names>
		<date value="2003-03"/>
		<abstract>
			<richtext>
				<p>This specification defines the XML Pointer Language (XPointer) Framework, an extensible system for XML addressing that underlies additional XPointer scheme specifications. The framework is intended to be used as a basis for fragment identifiers for any resource whose Internet media type is one of text/xml, application/xml, text/xml-external-parsed-entity, or application/xml-external-parsed-entity. Other XML-based media types are also encouraged to use this framework in defining their own fragment identifier languages.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Recommendation REC-xptr-framework-20030325</howpublished>
		<title type="sharef:primaryTitle">XPointer Framework</title>
		<field type="bibtex:topic">xml[0.6] xpointer[1] xpath1[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2003/REC-xptr-framework-20030325</identifier>
	</reference>
	<reference name="xptrxmlns" src="bibtex:misc" src-info="bibtex:line-35392" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Steven J.</givenname>
				<surname>DeRose</surname>
			</person>
			<person>
				<givenname>Ron</givenname>
				<surname>Daniel</surname>
			</person>
			<person>
				<givenname>Eve</givenname>
				<surname>Maler</surname>
			</person>
			<person>
				<givenname>Jonathan</givenname>
				<surname>Marsh</surname>
			</person>
		</names>
		<date value="2003-03"/>
		<abstract>
			<richtext>
				<p>The XPointer xmlns() scheme is intended to be used with the XPointer Framework to allow correct interpretation of namespace prefixes in pointers, for instance, namespace-qualified scheme names and namespace-qualified element or attribute names appearing within scheme data.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Recommendation REC-xptr-xmlns-20030325</howpublished>
		<title type="sharef:primaryTitle">XPointer xmlns() Scheme</title>
		<field type="bibtex:topic">xpointer[1] xmlns[0.8]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2003/REC-xptr-xmlns-20030325</identifier>
	</reference>
	<reference name="xptrxpointer" src="bibtex:misc" src-info="bibtex:line-35403" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Steven J.</givenname>
				<surname>DeRose</surname>
			</person>
			<person>
				<givenname>Eve</givenname>
				<surname>Maler</surname>
			</person>
			<person>
				<givenname>Ron</givenname>
				<surname>Daniel</surname>
			</person>
		</names>
		<date value="2002-12"/>
		<abstract>
			<richtext>
				<p>The XPointer xpointer()  scheme is intended to be used with the XPointer Framework to provide a high level of functionality for addressing portions of XML documents. It is based on XPath, and adds the ability to address strings, points, and ranges in accordance with definitions provided in DOM 2: Range.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-xptr-xpointer-20021219</howpublished>
		<title type="sharef:primaryTitle">XPointer xpointer() Scheme</title>
		<field type="bibtex:topic">xpointer[1]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2002/WD-xptr-xpointer-20021219</identifier>
	</reference>
	<reference name="xptrelement" src="bibtex:misc" src-info="bibtex:line-35414" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Paul</givenname>
				<surname>Grosso</surname>
			</person>
			<person>
				<givenname>Eve</givenname>
				<surname>Maler</surname>
			</person>
			<person>
				<givenname>Jonathan</givenname>
				<surname>Marsh</surname>
			</person>
			<person>
				<givenname>Norman</givenname>
				<surname>Walsh</surname>
			</person>
		</names>
		<date value="2003-03"/>
		<abstract>
			<richtext>
				<p>The XPointer element() scheme is intended to be used with the XPointer Framework to allow basic addressing of XML elements.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Recommendation REC-xptr-element-20030325</howpublished>
		<title type="sharef:primaryTitle">XPointer element() Scheme</title>
		<field type="bibtex:topic">xpointer[1]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2003/REC-xptr-element-20030325</identifier>
	</reference>
	<reference name="xmlfragid" src="bibtex:misc" src-info="bibtex:line-35425" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Paul</givenname>
				<surname>Grosso</surname>
			</person>
		</names>
		<date value="2003-09"/>
		<abstract>
			<richtext>
				<p>A URI reference may include an optional fragment identifier that consists of additional reference information to be interpreted by the user agent after the URI has been successfully retrieved. The format and interpretation of fragment identifiers is dependent on the media type of the retrieval result. The XML media type can therefore specify a fragment identifier syntax that takes advantage of the XML structure to define ways to point into an XML resource. This document recommends the adoption of a specific fragment identifier syntax for use with XML resources.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Note NOTE-xml-fragid-20030912</howpublished>
		<title type="sharef:primaryTitle">Proposal for XML Fragment Identifier Syntax 0.9</title>
		<field type="bibtex:topic">xpointer[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2003/NOTE-xml-fragid-20030912</identifier>
	</reference>
	<reference name="xbase" src="bibtex:misc" src-info="bibtex:line-35436" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Jonathan</givenname>
				<surname>Marsh</surname>
			</person>
		</names>
		<date value="2001-06"/>
		<abstract>
			<richtext>
				<p>This document proposes a facility, similar to that of HTML BASE, for defining base URIs for parts of XML documents.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Recommendation REC-xmlbase-20010627</howpublished>
		<title type="sharef:primaryTitle">XML Base</title>
		<field type="bibtex:topic">xml[0.8] xmlbase[1]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2001/REC-xmlbase-20010627</identifier>
	</reference>
	<reference name="xmlbase2nd" src="bibtex:misc" src-info="bibtex:line-35447" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Jonathan</givenname>
				<surname>Marsh</surname>
			</person>
			<person>
				<givenname>Richard</givenname>
				<surname>Tobin</surname>
			</person>
		</names>
		<date value="2009-01"/>
		<abstract>
			<richtext>
				<p>This document proposes a facility, similar to that of HTML BASE, for defining base URIs for parts of XML documents.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Recommendation REC-xmlbase-20090128</howpublished>
		<title type="sharef:primaryTitle">XML Base (Second Edition)</title>
		<field type="bibtex:topic">xml[0.8] xmlbase[1]</field>
		<field type="bibtex:updates">xbase</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2009/REC-xmlbase-20090128</identifier>
	</reference>
	<reference name="xmlbasesec" src="bibtex:misc" src-info="bibtex:line-35459" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Jonathan</givenname>
				<surname>Marsh</surname>
			</person>
			<person>
				<givenname>Richard</givenname>
				<surname>Tobin</surname>
			</person>
		</names>
		<date value="2008-03"/>
		<abstract>
			<richtext>
				<p>This document describes a facility, similar to that of HTML BASE, for defining base URIs for parts of XML documents.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Proposed Edited Recommendation PER-xmlbase-20080320</howpublished>
		<title type="sharef:primaryTitle">XML Base (Second Edition)</title>
		<field type="bibtex:topic">xml[0.8] xmlbase[1]</field>
		<field type="bibtex:updates">xbase</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2008/PER-xmlbase-20080320</identifier>
	</reference>
	<reference name="xpath" src="bibtex:misc" src-info="bibtex:line-35471" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>James</givenname>
				<surname>Clark</surname>
			</person>
			<person>
				<givenname>Steven J.</givenname>
				<surname>DeRose</surname>
			</person>
		</names>
		<date value="1999-11"/>
		<abstract>
			<richtext>
				<p>XPath is a language for addressing parts of an XML document, designed to be used by both XSLT and XPointer.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Recommendation REC-xpath-19991116</howpublished>
		<title type="sharef:primaryTitle">XML Path Language (XPath) Version 1.0</title>
		<field type="bibtex:topic">xml[0.7] xpath1[1]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/1999/REC-xpath-19991116</identifier>
	</reference>
	<reference name="xpath2req" src="bibtex:misc" src-info="bibtex:line-35482" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Mary F.</givenname>
				<surname>Fernández</surname>
			</person>
			<person>
				<givenname>K.</givenname>
				<surname>Karun</surname>
			</person>
			<person>
				<givenname>Mark</givenname>
				<surname>Scardina</surname>
			</person>
		</names>
		<date value="2005-06"/>
		<abstract>
			<richtext>
				<p>This document describes the requirements for the XPath 2.0 specification and is annotated with their resolution in XPath 2.0 or XQuery 1.0 and XPath 2.0 Functions and Operators and the XQuery 1.0 and XPath 2.0 Data Model specifications.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-xpath20req-20050603</howpublished>
		<title type="sharef:primaryTitle">XPath Requirements Version 2.0</title>
		<field type="bibtex:topic">xml[0.6] xpath2[1]</field>
		<field type="bibtex:updates">xpath</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2005/WD-xpath20req-20050603</identifier>
	</reference>
	<reference name="xpath20" src="bibtex:misc" src-info="bibtex:line-35494" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Anders</givenname>
				<surname>Berglund</surname>
			</person>
			<person>
				<givenname>Scott</givenname>
				<surname>Boag</surname>
			</person>
			<person>
				<givenname>Donald D.</givenname>
				<surname>Chamberlin</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>Jérôme</givenname>
				<surname>Siméon</surname>
			</person>
		</names>
		<date value="2007-01"/>
		<abstract>
			<richtext>
				<p>XPath 2.0 is an expression language that allows the processing of values conforming to the data model defined in the XQuery 1.0 and XPath 2.0 Data Model (XDM). The data model provides a tree representation of XML documents as well as atomic values such as integers, strings, and booleans, and sequences that may contain both references to nodes in an XML document and atomic values. The result of an XPath expression may be a selection of nodes from the input documents, or an atomic value, or more generally, any sequence allowed by the data model. The name of the language derives from its most distinctive feature, the path expression, which provides a means of hierarchic addressing of the nodes in an XML tree. XPath 2.0 is a superset of XPath 1.0, with the added capability to support a richer set of data types, and to take advantage of the type information that becomes available when documents are validated using XML Schema. A backwards compatibility mode is provided to ensure that nearly all XPath 1.0 expressions continue to deliver the same result with XPath 2.0; exceptions to this policy are noted in Section I (Backwards Compatibility with XPath 1.0).</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Recommendation REC-xpath20-20070123</howpublished>
		<title type="sharef:primaryTitle">XML Path Language (XPath) 2.0</title>
		<field type="bibtex:topic">xml[0.6] xpath2[1]</field>
		<field type="bibtex:updates">xpath2req</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2007/REC-xpath20-20070123</identifier>
	</reference>
	<reference name="xpath20second" src="bibtex:misc" src-info="bibtex:line-35506" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Anders</givenname>
				<surname>Berglund</surname>
			</person>
			<person>
				<givenname>Scott</givenname>
				<surname>Boag</surname>
			</person>
			<person>
				<givenname>Donald D.</givenname>
				<surname>Chamberlin</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>Jérôme</givenname>
				<surname>Siméon</surname>
			</person>
		</names>
		<date value="2010-12"/>
		<abstract>
			<richtext>
				<p>XPath 2.0 is an expression language that allows the processing of values conforming to the data model defined in XQuery 1.0 and XPath 2.0 Data Model (Second Edition). The data model provides a tree representation of XML documents as well as atomic values such as integers, strings, and booleans, and sequences that may contain both references to nodes in an XML document and atomic values. The result of an XPath expression may be a selection of nodes from the input documents, or an atomic value, or more generally, any sequence allowed by the data model. The name of the language derives from its most distinctive feature, the path expression, which provides a means of hierarchic addressing of the nodes in an XML tree. XPath 2.0 is a superset of XPath 1.0, with the added capability to support a richer set of data types, and to take advantage of the type information that becomes available when documents are validated using XML Schema. A backwards compatibility mode is provided to ensure that nearly all XPath 1.0 expressions continue to deliver the same result with XPath 2.0; exceptions to this policy are noted in Backwards Compatibility with XPath 1.0.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Recommendation REC-xpath20-20101214</howpublished>
		<title type="sharef:primaryTitle">XML Path Language (XPath) 2.0 (Second Edition)</title>
		<field type="bibtex:topic">xml[0.6] xpath2[1]</field>
		<field type="bibtex:updates">xpath20</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2010/REC-xpath20-20101214</identifier>
	</reference>
	<reference name="xpath21" src="bibtex:misc" src-info="bibtex:line-35518" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Jonathan</givenname>
				<surname>Robie</surname>
			</person>
			<person>
				<givenname>Don</givenname>
				<surname>Chamberlin</surname>
			</person>
			<person>
				<givenname>Michael</givenname>
				<surname>Dyck</surname>
			</person>
			<person>
				<givenname>John</givenname>
				<surname>Snelson</surname>
			</person>
		</names>
		<date value="2009-12"/>
		<abstract>
			<richtext>
				<p>XPath 2.0 is an expression language that allows the processing of values conforming to the data model defined in [XQuery and XPath Data Model (XDM) 1.1]. The data model provides a tree representation of XML documents as well as atomic values such as integers, strings, and booleans, and sequences that may contain both references to nodes in an XML document and atomic values. The result of an XPath expression may be a selection of nodes from the input documents, or an atomic value, or more generally, any sequence allowed by the data model. The name of the language derives from its most distinctive feature, the path expression, which provides a means of hierarchic addressing of the nodes in an XML tree. XPath 2.0 is a superset of [XML Path Language (XPath) Version 1.0], with the added capability to support a richer set of data types, and to take advantage of the type information that becomes available when documents are validated using XML Schema. A backwards compatibility mode is provided to ensure that nearly all XPath 1.0 expressions continue to deliver the same result with XPath 2.0; exceptions to this policy are noted in [I Backwards Compatibility with XPath 1.0].</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-xpath-21-20091215</howpublished>
		<title type="sharef:primaryTitle">XML Path Language (XPath) 2.1</title>
		<field type="bibtex:topic">xml[0.6] xpath2[1]</field>
		<field type="bibtex:updates">xpath20second</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2009/WD-xpath-21-20091215</identifier>
	</reference>
	<reference name="xpath30" src="bibtex:misc" src-info="bibtex:line-35530" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Jonathan</givenname>
				<surname>Robie</surname>
			</person>
			<person>
				<givenname>Don</givenname>
				<surname>Chamberlin</surname>
			</person>
			<person>
				<givenname>Michael</givenname>
				<surname>Dyck</surname>
			</person>
			<person>
				<givenname>John</givenname>
				<surname>Snelson</surname>
			</person>
		</names>
		<date value="2010-12"/>
		<abstract>
			<richtext>
				<p>XPath 3.0 is an expression language that allows the processing of values conforming to the data model defined in XQuery and XPath Data Model (XDM) 3.0. The data model provides a tree representation of XML documents as well as atomic values such as integers, strings, and booleans, and sequences that may contain both references to nodes in an XML document and atomic values. The result of an XPath expression may be a selection of nodes from the input documents, or an atomic value, or more generally, any sequence allowed by the data model. The name of the language derives from its most distinctive feature, the path expression, which provides a means of hierarchic addressing of the nodes in an XML tree. XPath 3.0 is a superset of XML Path Language (XPath) Version 1.0, with the added capability to support a richer set of data types, and to take advantage of the type information that becomes available when documents are validated using XML Schema. A backwards compatibility mode is provided to ensure that nearly all XPath 1.0 expressions continue to deliver the same result with XPath 3.0; exceptions to this policy are noted in Backwards Compatibility with XPath 1.0.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-xpath-30-20101214</howpublished>
		<title type="sharef:primaryTitle">XML Path Language (XPath) 3.0</title>
		<field type="bibtex:topic">xml[0.6] xpath2[1]</field>
		<field type="bibtex:updates">xpath21</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2010/WD-xpath-30-20101214</identifier>
	</reference>
	<reference name="xqxpparsing" src="bibtex:misc" src-info="bibtex:line-35542" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Scott</givenname>
				<surname>Boag</surname>
			</person>
		</names>
		<date value="2005-04"/>
		<abstract>
			<richtext>
				<p>This document describes possible strategies for tokenizing the "XML Path Language (XPath) 2.0" and "XQuery 1.0: An XML Query Language" languages, and is provided as a helpful guide to those who are designing an implementation for these languages, and as background material for the normative EBNF found in the language specifications. In the future this document may be expanded to cover more general parsing strategies.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-xquery-xpath-parsing-20050404</howpublished>
		<title type="sharef:primaryTitle">Building a Tokenizer for XPath or XQuery</title>
		<field type="bibtex:topic">xpath2[0.8] xquery[0.8]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2005/WD-xquery-xpath-parsing-20050404</identifier>
	</reference>
	<reference name="xns" src="bibtex:misc" src-info="bibtex:line-35553" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Tim</givenname>
				<surname>Bray</surname>
			</person>
			<person>
				<givenname>Dave</givenname>
				<surname>Hollander</surname>
			</person>
			<person>
				<givenname>Andrew</givenname>
				<surname>Layman</surname>
			</person>
		</names>
		<date value="1999-01"/>
		<abstract>
			<richtext>
				<p>XML namespaces provide a simple method for qualifying element and attribute names used in Extensible Markup Language documents by associating them with namespaces identified by URI references.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Recommendation REC-xml-names-19990114</howpublished>
		<title type="sharef:primaryTitle">Namespaces in XML</title>
		<field type="bibtex:topic">xml[0.8] xmlns[1]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/1999/REC-xml-names-19990114</identifier>
	</reference>
	<reference name="xmlns10sec" src="bibtex:misc" src-info="bibtex:line-35564" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Tim</givenname>
				<surname>Bray</surname>
			</person>
			<person>
				<givenname>Dave</givenname>
				<surname>Hollander</surname>
			</person>
			<person>
				<givenname>Andrew</givenname>
				<surname>Layman</surname>
			</person>
			<person>
				<givenname>Richard</givenname>
				<surname>Tobin</surname>
			</person>
		</names>
		<date value="2006-08"/>
		<abstract>
			<richtext>
				<p>XML namespaces provide a simple method for qualifying element and attribute names used in Extensible Markup Language documents by associating them with namespaces identified by URI references.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Recommendation REC-xml-names-20060816</howpublished>
		<title type="sharef:primaryTitle">Namespaces in XML 1.0 (Second Edition)</title>
		<field type="bibtex:topic">xml[0.8] xmlns[1]</field>
		<field type="bibtex:updates">xns</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2006/REC-xml-names-20060816</identifier>
	</reference>
	<reference name="xmlns10third" src="bibtex:misc" src-info="bibtex:line-35576" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Tim</givenname>
				<surname>Bray</surname>
			</person>
			<person>
				<givenname>Dave</givenname>
				<surname>Hollander</surname>
			</person>
			<person>
				<givenname>Andrew</givenname>
				<surname>Layman</surname>
			</person>
			<person>
				<givenname>Richard</givenname>
				<surname>Tobin</surname>
			</person>
			<person>
				<givenname>Henry S.</givenname>
				<surname>Thompson</surname>
			</person>
		</names>
		<date value="2009-12"/>
		<abstract>
			<richtext>
				<p>XML namespaces provide a simple method for qualifying element and attribute names used in Extensible Markup Language documents by associating them with namespaces identified by URI references.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Recommendation REC-xml-names-20091208</howpublished>
		<title type="sharef:primaryTitle">Namespaces in XML 1.0 (Third Edition)</title>
		<field type="bibtex:topic">xml[0.8] xmlns[1]</field>
		<field type="bibtex:updates">xmlns10sec</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2009/REC-xml-names-20091208</identifier>
	</reference>
	<reference name="namespacestate" src="bibtex:misc" src-info="bibtex:line-35588" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Norman</givenname>
				<surname>Walsh</surname>
			</person>
		</names>
		<date value="2006-03"/>
		<abstract>
			<richtext>
				<p>A finding of the W3C Technical Architecture Group (TAG), this document addresses the question of whether or not adding new names to a (published) namespace is a sound practice.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-namespaceState-20060329</howpublished>
		<title type="sharef:primaryTitle">The Disposition of Names in an XML Namespace</title>
		<field type="bibtex:topic">xmlns[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2006/WD-namespaceState-20060329</identifier>
	</reference>
	<reference name="xmlns11req" src="bibtex:misc" src-info="bibtex:line-35599" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Jonathan</givenname>
				<surname>Marsh</surname>
			</person>
		</names>
		<date value="2002-04"/>
		<abstract>
			<richtext>
				<p>This document contains requirements on the development of Namespaces in XML version 1.1, which is intended to have a single new feature — the ability to undeclare namespaces. In addition, all errata of version 1.0 will be incorporated.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-xml-names11-req-20020403</howpublished>
		<title type="sharef:primaryTitle">Namespaces in XML 1.1 Requirements</title>
		<field type="bibtex:topic">xml[0.8] xmlns[0.9]</field>
		<field type="bibtex:updates">xns</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2002/WD-xml-names11-req-20020403</identifier>
	</reference>
	<reference name="xmlns11" src="bibtex:misc" src-info="bibtex:line-35611" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Tim</givenname>
				<surname>Bray</surname>
			</person>
			<person>
				<givenname>Dave</givenname>
				<surname>Hollander</surname>
			</person>
			<person>
				<givenname>Andrew</givenname>
				<surname>Layman</surname>
			</person>
			<person>
				<givenname>Richard</givenname>
				<surname>Tobin</surname>
			</person>
		</names>
		<date value="2004-02"/>
		<abstract>
			<richtext>
				<p>XML namespaces provide a simple method for qualifying element and attribute names used in Extensible Markup Language documents by associating them with namespaces identified by IRI references.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Recommendation REC-xml-names11-20040204</howpublished>
		<title type="sharef:primaryTitle">Namespaces in XML 1.1</title>
		<field type="bibtex:topic">xml[0.8] xmlns[1]</field>
		<field type="bibtex:updates">xmlns11req</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2004/REC-xml-names11-20040204</identifier>
	</reference>
	<reference name="xmlns11sec" src="bibtex:misc" src-info="bibtex:line-35623" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Tim</givenname>
				<surname>Bray</surname>
			</person>
			<person>
				<givenname>Dave</givenname>
				<surname>Hollander</surname>
			</person>
			<person>
				<givenname>Andrew</givenname>
				<surname>Layman</surname>
			</person>
			<person>
				<givenname>Richard</givenname>
				<surname>Tobin</surname>
			</person>
		</names>
		<date value="2006-08"/>
		<abstract>
			<richtext>
				<p>XML namespaces provide a simple method for qualifying element and attribute names used in Extensible Markup Language documents by associating them with namespaces identified by IRI references.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Recommendation REC-xml-names11-20060816</howpublished>
		<title type="sharef:primaryTitle">Namespaces in XML 1.1 (Second Edition)</title>
		<field type="bibtex:topic">xml[0.8] xmlns[1]</field>
		<field type="bibtex:updates">xmlns11</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2006/REC-xml-names11-20060816</identifier>
	</reference>
	<reference name="xsl" src="bibtex:misc" src-info="bibtex:line-35635" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Sharon</givenname>
				<surname>Adler</surname>
			</person>
			<person>
				<givenname>Anders</givenname>
				<surname>Berglund</surname>
			</person>
			<person>
				<givenname>Jeff</givenname>
				<surname>Caruso</surname>
			</person>
			<person>
				<givenname>Stephen</givenname>
				<surname>Deach</surname>
			</person>
			<person>
				<givenname>Paul</givenname>
				<surname>Grosso</surname>
			</person>
			<person>
				<givenname>Eduardo</givenname>
				<surname>Gutentag</surname>
			</person>
			<person>
				<givenname>R. Alexander</givenname>
				<surname>Milowski</surname>
			</person>
			<person>
				<givenname>Scott</givenname>
				<surname>Parnell</surname>
			</person>
			<person>
				<givenname>Jeremy</givenname>
				<surname>Richman</surname>
			</person>
			<person>
				<givenname>Stephen</givenname>
				<surname>Zilles</surname>
			</person>
		</names>
		<date value="2001-10"/>
		<howpublished>World Wide Web Consortium, Recommendation REC-xsl-20011015</howpublished>
		<title type="sharef:primaryTitle">Extensible Stylesheet Language (XSL) Version 1.0</title>
		<field type="bibtex:topic">xsl[0.9] xslfo[1]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2001/REC-xsl-20011015</identifier>
	</reference>
	<reference name="xsl11req" src="bibtex:misc" src-info="bibtex:line-35645" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Paul</givenname>
				<surname>Grosso</surname>
			</person>
		</names>
		<date value="2003-12"/>
		<abstract>
			<richtext>
				<p>The XSL 1.0 specification  defines the features and syntax for the Extensible Stylesheet Language (XSL), a language for expressing stylesheets. This document enumerates the collected requirements for a 1.1 version of XSL.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-xsl11-req-20031217</howpublished>
		<title type="sharef:primaryTitle">Extensible Stylesheet Language (XSL) Version 1.1 Requirements</title>
		<field type="bibtex:topic">xsl[0.8] xslfo[0.9]</field>
		<field type="bibtex:updates">xsl</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2003/WD-xsl11-req-20031217</identifier>
	</reference>
	<reference name="xsl11" src="bibtex:misc" src-info="bibtex:line-35657" type="bibtex:misc">
		<names type="sharef:editor">
			<person>
				<givenname>Anders</givenname>
				<surname>Berglund</surname>
			</person>
		</names>
		<date value="2006-12"/>
		<abstract>
			<richtext>
				<p>This specification defines the features and syntax for the Extensible Stylesheet Language (XSL), a language for expressing stylesheets. It consists of two parts: (1) a language for transforming XML documents (XSLT), and (2) an XML vocabulary for specifying formatting semantics. An XSL stylesheet specifies the presentation of a class of XML documents by describing how an instance of the class is transformed into an XML document that uses the formatting vocabulary.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Recommendation REC-xsl11-20061205</howpublished>
		<title type="sharef:primaryTitle">Extensible Stylesheet Language (XSL) Version 1.1</title>
		<field type="bibtex:topic">xsl[0.9] xslfo[1]</field>
		<field type="bibtex:updates">xsl11req</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2006/REC-xsl11-20061205</identifier>
	</reference>
	<reference name="xslfo20req" src="bibtex:misc" src-info="bibtex:line-35669" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Klaas</givenname>
				<surname>Bals</surname>
			</person>
		</names>
		<date value="2008-03"/>
		<abstract>
			<richtext>
				<p>The XSL 1.1 specification defines the features and syntax for the Extensible Stylesheet Language (XSL), a language for expressing stylesheets. This document enumerates the collected requirements for a 2.0 version of XSL. There are two parts to XSL: XSL Transformations (XSLT) for transformation of documents and XSL Formatting Objects (XSL-FO) for formatting of documents. This is the requirements document for XSL-FO and not for XSLT.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-xslfo20-req-20080326</howpublished>
		<title type="sharef:primaryTitle">Extensible Stylesheet Language (XSL) Requirements Version 2.0</title>
		<field type="bibtex:topic">xsl[0.8] xslfo[0.9]</field>
		<field type="bibtex:updates">xsl11</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2008/WD-xslfo20-req-20080326</identifier>
	</reference>
	<reference name="xslfo20dn" src="bibtex:misc" src-info="bibtex:line-35681" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Liam R. E.</givenname>
				<surname>Quin</surname>
			</person>
		</names>
		<date value="2010-12"/>
		<abstract>
			<richtext>
				<p>The Extensible Stylesheet Language (XSL) has two parts: 1. a language for transforming XML documents (XSLT), and 2. an XML vocabulary for specifying formatting semantics (XSL-FO). This document describes features and changes introduced for version 2.0 of the XSL-FO part of XSL.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-xslfo20-20101216</howpublished>
		<title type="sharef:primaryTitle">Design Notes for Extensible Stylesheet Language (XSL) 2.0</title>
		<field type="bibtex:topic">xsl[0.8] xslfo[0.9]</field>
		<field type="bibtex:updates">xsl11</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2010/WD-xslfo20-20101216</identifier>
	</reference>
	<reference name="xslt" src="bibtex:misc" src-info="bibtex:line-35693" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>James</givenname>
				<surname>Clark</surname>
			</person>
		</names>
		<date value="1999-11"/>
		<abstract>
			<richtext>
				<p>This specification defines the syntax and semantics of XSLT, which is a language for transforming XML documents into other XML documents. XSLT is designed for use as part of XSL, which is a stylesheet language for XML. In addition to XSLT, XSL includes an XML vocabulary for specifying formatting. XSL specifies the styling of an XML document by using XSLT to describe how the document is transformed into another XML document that uses the formatting vocabulary. XSLT is also designed to be used independently of XSL. However, XSLT is not intended as a completely general-purpose XML transformation language. Rather it is designed primarily for the kinds of transformations that are needed when XSLT is used as part of XSL.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Recommendation REC-xslt-19991116</howpublished>
		<title type="sharef:primaryTitle">XSL Transformations (XSLT) Version 1.0</title>
		<field type="bibtex:topic">xslt1[1]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/1999/REC-xslt-19991116</identifier>
	</reference>
	<reference name="xslt11" src="bibtex:misc" src-info="bibtex:line-35705" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>James</givenname>
				<surname>Clark</surname>
			</person>
		</names>
		<date value="2001-08"/>
		<abstract>
			<richtext>
				<p>This specification defines the syntax and semantics of XSLT, which is a language for transforming XML documents into other XML documents. XSLT is designed for use as part of XSL, which is a stylesheet language for XML. In addition to XSLT, XSL includes an XML vocabulary for specifying formatting. XSL specifies the styling of an XML document by using XSLT to describe how the document is transformed into another XML document that uses the formatting vocabulary. XSLT is also designed to be used independently of XSL. However, XSLT is not intended as a completely general-purpose XML transformation language. Rather it is designed primarily for the kinds of transformations that are needed when XSLT is used as part of XSL.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-xslt11-20010824</howpublished>
		<title type="sharef:primaryTitle">XSL Transformations (XSLT) Version 1.1</title>
		<field type="bibtex:topic">xslt1[1]</field>
		<field type="bibtex:updates">xslt11req</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2001/WD-xslt11-20010824</identifier>
	</reference>
	<reference name="xslt11req" src="bibtex:misc" src-info="bibtex:line-35717" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Steve</givenname>
				<surname>Muench</surname>
			</person>
		</names>
		<date value="2000-08"/>
		<abstract>
			<richtext>
				<p>This document describes the requirements for the XSLT 1.1 specification.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-xslt11req-20000825</howpublished>
		<title type="sharef:primaryTitle">XSL Transformations Requirements Version 1.1</title>
		<field type="bibtex:topic">xslt1[1]</field>
		<field type="bibtex:updates">xslt</field>
	</reference>
	<reference name="xslt2req" src="bibtex:misc" src-info="bibtex:line-35728" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Steve</givenname>
				<surname>Muench</surname>
			</person>
			<person>
				<givenname>Mark</givenname>
				<surname>Scardina</surname>
			</person>
		</names>
		<date value="2001-02"/>
		<abstract>
			<richtext>
				<p>This document describes the requirements for the XSLT 2.0 specification.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-xslt20req-20010214</howpublished>
		<title type="sharef:primaryTitle">XSL Transformations Requirements Version 2.0</title>
		<field type="bibtex:topic">xslt2[1]</field>
		<field type="bibtex:updates">xslt11</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2001/WD-xslt20req-20010214</identifier>
	</reference>
	<reference name="xslt20" src="bibtex:misc" src-info="bibtex:line-35740" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Michael</givenname>
				<surname>Kay</surname>
			</person>
		</names>
		<date value="2007-01"/>
		<abstract>
			<richtext>
				<p>This specification defines the syntax and semantics of XSLT 2.0, a language for transforming XML documents into other XML documents. XSLT 2.0 is a revised version of the XSLT 1.0 Recommendation published on 16 November 1999. The changes made in this document are designed to meet the requirements for XSLT 2.0 described in XSLT 2.0 Requirements. The way in which each requirement has been addressed is outlined in I Checklist of Requirements. A summary of the changes since XSLT 1.0 is included in Changes from XSLT 1.0. XSLT 2.0 is designed to be used in conjunction with XPath 2.0. XSLT shares the same data model as XPath 2.0, which is defined in the XPath 2.0 Data Model, and it uses the library of functions and operators defined in XPath 2.0 Functions and Operators. XSLT 2.0 also includes optional facilities to serialize the results of a transformation, by means of an interface to the serialization component described in XSLT and XQuery Serialization.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Recommendation REC-xslt20-20070123</howpublished>
		<title type="sharef:primaryTitle">XSL Transformations (XSLT) Version 2.0</title>
		<field type="bibtex:topic">xslt2[1]</field>
		<field type="bibtex:updates">xslt2req</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2007/REC-xslt20-20070123</identifier>
	</reference>
	<reference name="xslt20sec" src="bibtex:misc" src-info="bibtex:line-35752" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Michael</givenname>
				<surname>Kay</surname>
			</person>
		</names>
		<date value="2009-04"/>
		<abstract>
			<richtext>
				<p>This specification defines the syntax and semantics of XSLT 2.0, a language for transforming XML documents into other XML documents. XSLT 2.0 is a revised version of the XSLT 1.0 Recommendation published on 16 November 1999. The changes made in this document are designed to meet the requirements for XSLT 2.0 described in XSLT 2.0 Requirements. The way in which each requirement has been addressed is outlined in I Checklist of Requirements. A summary of the changes since XSLT 1.0 is included in Changes from XSLT 1.0. XSLT 2.0 is designed to be used in conjunction with XPath 2.0. XSLT shares the same data model as XPath 2.0, which is defined in the XPath 2.0 Data Model, and it uses the library of functions and operators defined in XPath 2.0 Functions and Operators. XSLT 2.0 also includes optional facilities to serialize the results of a transformation, by means of an interface to the serialization component described in XSLT and XQuery Serialization.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Proposed Edited Recommendation PER-xslt20-20090421</howpublished>
		<title type="sharef:primaryTitle">XSL Transformations (XSLT) Version 2.0</title>
		<field type="bibtex:topic">xslt2[1]</field>
		<field type="bibtex:updates">xslt20</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2009/PER-xslt20-20090421</identifier>
	</reference>
	<reference name="xslt21requirements" src="bibtex:misc" src-info="bibtex:line-35764" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Petr</givenname>
				<surname>Cimprich</surname>
			</person>
		</names>
		<date value="2010-06"/>
		<abstract>
			<richtext>
				<p>This document is a characterization of requirements and use cases for Transformations (XSLT) Version 2.1. The Requirements lists enhancements requested over time that may be addressed in XSLT 2.1.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-xslt-21-requirements-20100610</howpublished>
		<title type="sharef:primaryTitle">Requirements and Use Cases for XSLT 2.1</title>
		<field type="bibtex:topic">xslt2[1]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2010/WD-xslt-21-requirements-20100610</identifier>
	</reference>
	<reference name="xslt21" src="bibtex:misc" src-info="bibtex:line-35775" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Michael</givenname>
				<surname>Kay</surname>
			</person>
		</names>
		<date value="2010-05"/>
		<abstract>
			<richtext>
				<p>This specification defines the syntax and semantics of XSLT 2.1, a language for transforming XML documents into other XML documents. XSLT 2.1 is a revised version of the XSLT 2.0 Recommendation published on 23 January 2007. The primary purpose of the changes in this version of the language is to enable transformations to be performed in streaming mode, where neither the source document nor the result document is ever held in memory in its entirety. XSLT 2.1 is designed to be used in conjunction with XPath 2.1, which is defined in XPath 2.1. XSLT shares the same data model as XPath 2.1, and it uses the library of functions and operators defined in Functions and Operators. XPath 2.1 and the underlying function library introduce a number of enhancements, for example the availability of higher-order functions. Some of the functions that were previously defined in the XSLT 2.0 specification, such as the format-date and format-number functions, are now defined in the standard function library to make them available to other host languages. XSLT 2.1 also includes optional facilities to serialize the results of a transformation, by means of an interface to the serialization component described in XSLT and XQuery Serialization. This document contains hyperlinks to specific sections or definitions within other documents in this family of specifications. These links are indicated visually by a superscript identifying the target specification: for example XP for XPath, DM for the XDM data model, FO for Functions and Operators.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-xslt-21-20100511</howpublished>
		<title type="sharef:primaryTitle">XSL Transformations (XSLT) Version 2.1</title>
		<field type="bibtex:topic">xslt2[1]</field>
		<field type="bibtex:updates">xslt20sec</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2010/WD-xslt-21-20100511</identifier>
	</reference>
	<reference name="xsltxqueryserialize" src="bibtex:misc" src-info="bibtex:line-35787" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Scott</givenname>
				<surname>Boag</surname>
			</person>
			<person>
				<givenname>Michael</givenname>
				<surname>Kay</surname>
			</person>
			<person>
				<givenname>Joanne</givenname>
				<surname>Tong</surname>
			</person>
			<person>
				<givenname>Norman</givenname>
				<surname>Walsh</surname>
			</person>
			<person>
				<givenname>Henry</givenname>
				<surname>Zongaro</surname>
			</person>
		</names>
		<date value="2007-01"/>
		<abstract>
			<richtext>
				<p>This document defines serialization of an instance of the data model as defined in "XQuery 1.0 and XPath 2.0 Data Model" into a sequence of octets. Serialization is designed to be a component of a expanded a host language such as "XSL Transformations (XSLT) Version 2.0" or "XQuery 1.0: An XML Query Language".</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Recommendation REC-xslt-xquery-serialization-20070123</howpublished>
		<title type="sharef:primaryTitle">XSLT 2.0 and XQuery 1.0 Serialization</title>
		<field type="bibtex:topic">xslt2[0.9] xquery[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2007/REC-xslt-xquery-serialization-20070123</identifier>
	</reference>
	<reference name="xsltxqueryserialize2nd" src="bibtex:misc" src-info="bibtex:line-35798" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Scott</givenname>
				<surname>Boag</surname>
			</person>
			<person>
				<givenname>Michael</givenname>
				<surname>Kay</surname>
			</person>
			<person>
				<givenname>Joanne</givenname>
				<surname>Tong</surname>
			</person>
			<person>
				<givenname>Norman</givenname>
				<surname>Walsh</surname>
			</person>
			<person>
				<givenname>Henry</givenname>
				<surname>Zongaro</surname>
			</person>
		</names>
		<date value="2010-12"/>
		<abstract>
			<richtext>
				<p>This document defines serialization of an instance of the data model as defined in "XQuery 1.0 and XPath 2.0 Data Model" into a sequence of octets. Serialization is designed to be a component of a expanded a host language such as "XSL Transformations (XSLT) Version 2.0" or "XQuery 1.0: An XML Query Language".</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Recommendation REC-xslt-xquery-serialization-20101214</howpublished>
		<title type="sharef:primaryTitle">XSLT 2.0 and XQuery 1.0 Serialization (Second Edition)</title>
		<field type="bibtex:topic">xslt2[0.9] xquery[0.9]</field>
		<field type="bibtex:updates">xsltxqueryserialize</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2010/REC-xslt-xquery-serialization-20101214</identifier>
	</reference>
	<reference name="xsltxqueryserialization11" src="bibtex:misc" src-info="bibtex:line-35810" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Henry</givenname>
				<surname>Zongaro</surname>
			</person>
		</names>
		<date value="2009-12"/>
		<abstract>
			<richtext>
				<p>This document defines serialization of an instance of the data model as defined in the XQuery and XPath Data Model 1.1 into a sequence of octets. Serialization is designed to be a component that can be used by other specifications such as XSL Transformations (XSLT) Version 2.1 or XQuery 1.1: An XML Query Language.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-xslt-xquery-serialization-11-20091215</howpublished>
		<title type="sharef:primaryTitle">XSLT and XQuery Serialization 1.1</title>
		<field type="bibtex:topic">xslt2[0.9] xquery[0.9]</field>
		<field type="bibtex:updates">xsltxqueryserialize2nd</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2009/WD-xslt-xquery-serialization-11-20091215</identifier>
	</reference>
	<reference name="xsltxqueryserialization30" src="bibtex:misc" src-info="bibtex:line-35822" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Henry</givenname>
				<surname>Zongaro</surname>
			</person>
		</names>
		<date value="2010-12"/>
		<abstract>
			<richtext>
				<p>This document defines serialization of an instance of the data model as defined in XQuery and XPath Data Model (XDM) 3.0 into a sequence of octets. Serialization is designed to be a component that can be used by other specifications such as XSL Transformations (XSLT) Version 3.0 or XQuery 3.0: An XML Query Language.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-xslt-xquery-serialization-30-20101214</howpublished>
		<title type="sharef:primaryTitle">XSLT and XQuery Serialization 3.0</title>
		<field type="bibtex:topic">xslt3[0.9] xquery3[0.9]</field>
		<field type="bibtex:updates">xsltxqueryserialization11</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2010/WD-xslt-xquery-serialization-30-20101214</identifier>
	</reference>
	<reference name="xqueryx" src="bibtex:misc" src-info="bibtex:line-35834" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Jim</givenname>
				<surname>Melton</surname>
			</person>
			<person>
				<givenname>Subramanian</givenname>
				<surname>Muralidhar</surname>
			</person>
		</names>
		<date value="2007-01"/>
		<abstract>
			<richtext>
				<p>This document defines an XML Syntax for XQuery 1.0: An XML Query Language.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Recommendation REC-xqueryx-20070123</howpublished>
		<title type="sharef:primaryTitle">XML Syntax for XQuery 1.0 (XQueryX)</title>
		<field type="bibtex:topic">xqueryx[1] xquery[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2007/REC-xqueryx-20070123</identifier>
	</reference>
	<reference name="xqueryx2nd" src="bibtex:misc" src-info="bibtex:line-35845" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Jim</givenname>
				<surname>Melton</surname>
			</person>
			<person>
				<givenname>Subramanian</givenname>
				<surname>Muralidhar</surname>
			</person>
		</names>
		<date value="2010-12"/>
		<abstract>
			<richtext>
				<p>This document defines an XML Syntax for XQuery 1.0: An XML Query Language (Second Edition).</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Recommendation REC-xqueryx-20101214</howpublished>
		<title type="sharef:primaryTitle">XML Syntax for XQuery 1.0 (XQueryX) (Second Edition)</title>
		<field type="bibtex:topic">xqueryx[1] xquery[0.9]</field>
		<field type="bibtex:updates">xqueryx</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2010/REC-xqueryx-20101214</identifier>
	</reference>
	<reference name="xqueryx11" src="bibtex:misc" src-info="bibtex:line-35857" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Jim</givenname>
				<surname>Melton</surname>
			</person>
		</names>
		<date value="2008-12"/>
		<abstract>
			<richtext>
				<p>This document defines an XML Syntax for XQuery 1.1.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-xqueryx-11-20081203</howpublished>
		<title type="sharef:primaryTitle">XQueryX 1.1</title>
		<field type="bibtex:topic">xqueryx[1] xquery[0.9]</field>
		<field type="bibtex:updates">xqueryx2nd</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2008/WD-xqueryx-11-20081203</identifier>
	</reference>
	<reference name="xqueryx30" src="bibtex:misc" src-info="bibtex:line-35869" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Jim</givenname>
				<surname>Melton</surname>
			</person>
		</names>
		<date value="2010-12"/>
		<abstract>
			<richtext>
				<p>This document defines an XML Syntax for XQuery 3.0: An XML Query Language.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-xqueryx-30-20101214</howpublished>
		<title type="sharef:primaryTitle">XQueryX 3.0</title>
		<field type="bibtex:topic">xqueryx[1] xquery3[0.9]</field>
		<field type="bibtex:updates">xqueryx11</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2010/WD-xqueryx-30-20101214</identifier>
	</reference>
	<reference name="xbulk" src="bibtex:misc" src-info="bibtex:line-35881" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Merlin</givenname>
				<surname>Hughes</surname>
			</person>
		</names>
		<date value="2002-03"/>
		<howpublished>World Wide Web Consortium, Working Draft WD-xkms2-xbulk-20020318</howpublished>
		<title type="sharef:primaryTitle">XML Key Management Specification Bulk Operation (X-BULK)</title>
		<field type="bibtex:topic">xbulk[1] xkms[1]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2002/WD-xkms2-xbulk-20020318</identifier>
	</reference>
	<reference name="xkms20" src="bibtex:misc" src-info="bibtex:line-35891" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Phillip M.</givenname>
				<surname>Hallam-Baker</surname>
			</person>
			<person>
				<givenname>Shivaram H.</givenname>
				<surname>Mysore</surname>
			</person>
		</names>
		<date value="2005-06"/>
		<abstract>
			<richtext>
				<p>This document specifies protocols for distributing and registering public keys, suitable for use in conjunction with the W3C Recommendations for XML Signature and XML Encryption. The XML Key Management Specification (XKMS) comprises two parts — the XML Key Information Service Specification (X-KISS) and the XML Key Registration Service Specification (X-KRSS).</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Recommendation REC-xkms2-20050628</howpublished>
		<title type="sharef:primaryTitle">XML Key Management Specification (XKMS) — Version 2.0</title>
		<field type="bibtex:topic">xkms[1]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2005/REC-xkms2-20050628</identifier>
	</reference>
	<reference name="xkmspgp" src="bibtex:misc" src-info="bibtex:line-35902" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Tommy</givenname>
				<surname>Lindberg</surname>
			</person>
			<person>
				<givenname>José</givenname>
				<surname>Kahan</surname>
			</person>
		</names>
		<date value="2005-12"/>
		<abstract>
			<richtext>
				<p>The XML Key Management Specification (XKMS 2.0) aims at providing a PKI independent interface to key management. XKMS services comprise discovery and validation of keys as well as support for certain aspects of the key life cycle management, including registration, reissuance and revocation. XKMS employs XML Signature for the purpose of providing message security in the form of authentication and integrity. In addition, XKMS is based on the use of the &lt;ds:KeyInfo&gt; element as a means of transporting key information used as templates for the various operations it specifies. This technical note addresses some of the issues related to the use of XKMS in conjunction with PGP.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Note NOTE-xkms-pgp-20051219</howpublished>
		<title type="sharef:primaryTitle">Using XKMS with PGP</title>
		<field type="bibtex:topic">xkms[0.8] pgp[0.8]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2005/NOTE-xkms-pgp-20051219</identifier>
	</reference>
	<reference name="xkms2req" src="bibtex:misc" src-info="bibtex:line-35913" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Frederick</givenname>
				<surname>Hirsch</surname>
			</person>
			<person>
				<givenname>Mike</givenname>
				<surname>Just</surname>
			</person>
		</names>
		<date value="2003-05"/>
		<howpublished>World Wide Web Consortium, Note NOTE-xkms2-req-20030505</howpublished>
		<title type="sharef:primaryTitle">XML Key Management (2.0) Requirements</title>
		<field type="bibtex:topic">xkms[1]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2003/NOTE-xkms2-req-20030505</identifier>
	</reference>
	<reference name="xkms2bindings" src="bibtex:misc" src-info="bibtex:line-35923" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Phillip M.</givenname>
				<surname>Hallam-Baker</surname>
			</person>
			<person>
				<givenname>Shivaram H.</givenname>
				<surname>Mysore</surname>
			</person>
		</names>
		<date value="2005-06"/>
		<abstract>
			<richtext>
				<p>This document specifies protocol bindings with security characteristics for the XML Key Management Specification (XKMS).</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Recommendation REC-xkms2-bindings-20050628</howpublished>
		<title type="sharef:primaryTitle">XML Key Management Specification (XKMS) Bindings — Version 2.0</title>
		<field type="bibtex:topic">xkms[1]</field>
		<field type="bibtex:updates">xkms2req</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2005/REC-xkms2-bindings-20050628</identifier>
	</reference>
	<reference name="xkmswsdl" src="bibtex:misc" src-info="bibtex:line-35935" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Richard</givenname>
				<surname>Salz</surname>
			</person>
			<person>
				<givenname>Yunhao</givenname>
				<surname>Zhang</surname>
			</person>
		</names>
		<date value="2005-11"/>
		<abstract>
			<richtext>
				<p>The XML Key Management Specification (XKMS 2.0) is a  W3C Recommendation that specifies protocols for distributing and registering public keys. The XML Key Management Service (XKMS) Working Group has defined a Web Service to handle conventional PKI (public-key infrastructure) functions such as registration, revocation and status, as well as related functions such as retrieval. This note provides a sample Web Services Description Language (WSDL) 1.1 description for an XKMS service. It is intended that XKMS developers use this as a "first draft" for developing their own version. Conversion to WSDL 2.0 should be fairly straightforward, once that specification completes its Last Call.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Note NOTE-xkms-wsdl-20051118</howpublished>
		<title type="sharef:primaryTitle">A WSDL 1.1 description for XKMS</title>
		<field type="bibtex:topic">xkms[0.9] wsdl[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2005/NOTE-xkms-wsdl-20051118</identifier>
	</reference>
	<reference name="wscusecases" src="bibtex:misc" src-info="bibtex:line-35946" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Tyler</givenname>
				<surname>Close</surname>
			</person>
		</names>
		<date value="2008-03"/>
		<abstract>
			<richtext>
				<p>This Note refines the objectives for the Web Security Context Working Group deliverables. It elaborates upon the group's Charter to explain what the group aims to achieve, what technologies may be used and how technical proposals will be evaluated. This elaboration is limited to the group's technical work and does not cover additional activities the group intends to engage in, such as ongoing outreach and education. This Note also includes an initial collection of use cases that the group expects will drive its technical work. Since this Note discusses the assumptions, goals, and processes the group will use to develop its recommendations, the intended audience is similar to that of the charter of the Working Group; group members, the W3C community, developers of web user agents, web content providers (server administrators), and parties interested and engaged in what the Web Security Context Working Group's plans and directions are. It is explicitly not targeted at the presumed beneficiaries of the group's work, the users of the web, and it is not expected that an average user would be able to read this document and understand it.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Note NOTE-wsc-usecases-20080306</howpublished>
		<title type="sharef:primaryTitle">Web Security Experience, Indicators and Trust: Scope and Use Cases</title>
		<identifier type="sharef:uri">http://www.w3.org/TR/2008/NOTE-wsc-usecases-20080306</identifier>
	</reference>
	<reference name="wscui" src="bibtex:misc" src-info="bibtex:line-35956" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Thomas</givenname>
				<surname>Roessler</surname>
			</person>
			<person>
				<givenname>Anil</givenname>
				<surname>Saldhana</surname>
			</person>
		</names>
		<date value="2010-08"/>
		<abstract>
			<richtext>
				<p>This specification defines guidelines and requirements for the presentation and communication of Web security context information to end-users.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Recommendation REC-wsc-ui-20100812</howpublished>
		<title type="sharef:primaryTitle">Web Security Context: User Interface Guidelines</title>
		<identifier type="sharef:uri">http://www.w3.org/TR/2010/REC-wsc-ui-20100812</identifier>
	</reference>
	<reference name="wscthreats" src="bibtex:misc" src-info="bibtex:line-35966" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Thomas</givenname>
				<surname>Roessler</surname>
			</person>
		</names>
		<date value="2007-11"/>
		<abstract>
			<richtext>
				<p>This Note includes threat trees used to analyze the threats that WSC-XIT responds to. It is a companion document to WSC-USECASES.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Note NOTE-wsc-threats-20071101</howpublished>
		<title type="sharef:primaryTitle">Web User Interaction: Threat Trees</title>
		<identifier type="sharef:uri">http://www.w3.org/TR/2007/NOTE-wsc-threats-20071101</identifier>
	</reference>
	<reference name="dsig" src="bibtex:misc" src-info="bibtex:line-35976" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Yang-Hua</givenname>
				<surname>Chu</surname>
			</person>
			<person>
				<givenname>Philip</givenname>
				<surname>DesAutels</surname>
			</person>
			<person>
				<givenname>Brian</givenname>
				<surname>LaMacchia</surname>
			</person>
			<person>
				<givenname>Peter</givenname>
				<surname>Lipp</surname>
			</person>
		</names>
		<date value="1998-05"/>
		<howpublished>World Wide Web Consortium, Recommendation REC-DSig-label-19980527</howpublished>
		<field type="bibtex:index">DSig, PICS</field>
		<title type="sharef:primaryTitle">PICS Signed Labels (DSig) 1.0 Specification</title>
		<identifier type="sharef:uri">http://www.w3.org/TR/1998/REC-DSig-label-19980527</identifier>
	</reference>
	<reference name="windowobject" src="bibtex:misc" src-info="bibtex:line-35986" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Ian</givenname>
				<surname>Davis</surname>
			</person>
			<person>
				<givenname>Maciej</givenname>
				<surname>Stachowiak</surname>
			</person>
		</names>
		<date value="2006-04"/>
		<abstract>
			<richtext>
				<p>This specification defines the Window object, which provides the global namespace for web scripting languages, access to other documents in a compound document by reference, navigation to other locations, and timers. The Window object is a long-standing de facto standard for HTML user agents. However, it should not be assumed based on this or the name "Window" that it is limited to HTML or to visual user agents.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-Window-20060407</howpublished>
		<title type="sharef:primaryTitle">Window Object 1.0</title>
		<field type="bibtex:topic">dom[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2006/WD-Window-20060407</identifier>
	</reference>
	<reference name="xmlhttprequest" src="bibtex:misc" src-info="bibtex:line-35997" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Anne</givenname>
				<surname link="van">Kesteren</surname>
			</person>
		</names>
		<date value="2010-08"/>
		<abstract>
			<richtext>
				<p>The XMLHttpRequest specification defines an API that provides scripted client functionality for transferring data between a client and a server.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Candidate Recommendation CR-XMLHttpRequest-20100803</howpublished>
		<title type="sharef:primaryTitle">The XMLHttpRequest Object</title>
		<field type="bibtex:topic">ajax[1] dom[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2010/CR-XMLHttpRequest-20100803</identifier>
	</reference>
	<reference name="xmlhttprequest2" src="bibtex:misc" src-info="bibtex:line-36008" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Anne</givenname>
				<surname link="van">Kesteren</surname>
			</person>
		</names>
		<date value="2010-09"/>
		<abstract>
			<richtext>
				<p>The XMLHttpRequest Level 2 specification enhances the XMLHttpRequest object with new features, such as cross-origin requests, progress events, and the handling of byte streams for both sending and receiving.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-XMLHttpRequest2-20100907</howpublished>
		<title type="sharef:primaryTitle">XMLHttpRequest Level 2</title>
		<field type="bibtex:topic">ajax[1] dom[0.9]</field>
		<field type="bibtex:updates">xmlhttprequest</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2010/WD-XMLHttpRequest2-20100907</identifier>
	</reference>
	<reference name="geolocationapi" src="bibtex:misc" src-info="bibtex:line-36020" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Andrei</givenname>
				<surname>Popescu</surname>
			</person>
		</names>
		<date value="2010-09"/>
		<abstract>
			<richtext>
				<p>This specification defines an API that provides scripted access to geographical location information associated with the hosting device.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Candidate Recommendation CR-geolocation-API-20100907</howpublished>
		<title type="sharef:primaryTitle">Geolocation API Specification</title>
		<field type="bibtex:topic">dom[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2010/CR-geolocation-API-20100907</identifier>
	</reference>
	<reference name="messagingapi" src="bibtex:misc" src-info="bibtex:line-36031" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Suresh</givenname>
				<surname>Chitturi</surname>
			</person>
			<person>
				<givenname>Daniel</givenname>
				<surname>Coloma</surname>
			</person>
			<person>
				<givenname>Max</givenname>
				<surname>Froumentin</surname>
			</person>
			<person>
				<givenname>Maria Angeles</givenname>
				<surname>Oteo</surname>
			</person>
			<person>
				<givenname>Niklas</givenname>
				<surname>Widell</surname>
			</person>
		</names>
		<date value="2011-01"/>
		<abstract>
			<richtext>
				<p>This specification defines an API that provides access to messaging functionality in the device, including SMS, MMS and email.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-messaging-api-20110120</howpublished>
		<title type="sharef:primaryTitle">The Messaging API</title>
		<field type="bibtex:topic">dom[0.9] sms[0.9] mms[0.9] smtp[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2011/WD-messaging-api-20110120</identifier>
	</reference>
	<reference name="webmessaging" src="bibtex:misc" src-info="bibtex:line-36042" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Ian</givenname>
				<surname>Hickson</surname>
			</person>
		</names>
		<date value="2011-03"/>
		<abstract>
			<richtext>
				<p>This specification defines two mechanism for communicating between browsing contexts in HTML documents.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-webmessaging-20110317</howpublished>
		<title type="sharef:primaryTitle">HTML5 Web Messaging</title>
		<field type="bibtex:topic">dom[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2011/WD-webmessaging-20110317</identifier>
	</reference>
	<reference name="captureapi" src="bibtex:misc" src-info="bibtex:line-36053" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Dzung D.</givenname>
				<surname>Tran</surname>
			</person>
			<person>
				<givenname>Ilkka</givenname>
				<surname>Oksanen</surname>
			</person>
			<person>
				<givenname>Ingmar</givenname>
				<surname>Kliche</surname>
			</person>
		</names>
		<date value="2010-09"/>
		<abstract>
			<richtext>
				<p>This specification defines an Application Programming Interface (API) that provides access to the audio, image and video capture capabilities of the device.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-media-capture-api-20100928</howpublished>
		<title type="sharef:primaryTitle">The Media Capture API</title>
		<field type="bibtex:topic">dom[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2010/WD-media-capture-api-20100928</identifier>
	</reference>
	<reference name="htmlmediacapture" src="bibtex:misc" src-info="bibtex:line-36064" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Ilkka</givenname>
				<surname>Oksanen</surname>
			</person>
			<person>
				<givenname>Dominique</givenname>
				<surname>Hazaël-Massieux</surname>
			</person>
		</names>
		<date value="2010-09"/>
		<abstract>
			<richtext>
				<p>This specification defines HTML form enhancements that provide access to the audio, image and video capture capabilities of the device.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-html-media-capture-20100928</howpublished>
		<title type="sharef:primaryTitle">HTML Media Capture</title>
		<field type="bibtex:topic">html[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2010/WD-html-media-capture-20100928</identifier>
	</reference>
	<reference name="progressevents" src="bibtex:misc" src-info="bibtex:line-36075" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Anne</givenname>
				<surname link="van">Kesteren</surname>
			</person>
		</names>
		<date value="2011-03"/>
		<abstract>
			<richtext>
				<p>The Progress Events specification defines an abstract event interface that can be used for measuring progress; e.g. HTTP entity body transfers.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-progress-events-20110310</howpublished>
		<title type="sharef:primaryTitle">Progress Events</title>
		<field type="bibtex:topic">ajax[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2011/WD-progress-events-20110310</identifier>
	</reference>
	<reference name="dom3req" src="bibtex:misc" src-info="bibtex:line-36086" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Ben</givenname>
				<surname>Chang</surname>
			</person>
			<person>
				<givenname>Mike</givenname>
				<surname>Champion</surname>
			</person>
			<person>
				<givenname>James</givenname>
				<surname>Davidson</surname>
			</person>
			<person>
				<givenname>Angel</givenname>
				<surname>Diaz</surname>
			</person>
			<person>
				<givenname>Andy</givenname>
				<surname>Heninger</surname>
			</person>
			<person>
				<givenname>Joe</givenname>
				<surname>Kesselman</surname>
			</person>
			<person>
				<givenname>Philippe</givenname>
				<surname>Le Hégaret</surname>
			</person>
			<person>
				<givenname>Arnaud</givenname>
				<surname>Le Hors</surname>
			</person>
			<person>
				<givenname>Tom</givenname>
				<surname>Pixley</surname>
			</person>
			<person>
				<givenname>Jared</givenname>
				<surname>Sorensen</surname>
			</person>
			<person>
				<givenname>Ray</givenname>
				<surname>Whitmer</surname>
			</person>
			<person>
				<givenname>Lauren</givenname>
				<surname>Wood</surname>
			</person>
		</names>
		<date value="2004-02"/>
		<howpublished>World Wide Web Consortium, Note NOTE-DOM-Requirements-20040226</howpublished>
		<title type="sharef:primaryTitle">Document Object Model (DOM) Requirements</title>
		<field type="bibtex:topic">dom3[1]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2004/NOTE-DOM-Requirements-20040226</identifier>
	</reference>
	<reference name="webidl" src="bibtex:misc" src-info="bibtex:line-36096" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Cameron</givenname>
				<surname>McCormack</surname>
			</person>
		</names>
		<date value="2010-10"/>
		<abstract>
			<richtext>
				<p>This document defines an interface definition language, Web IDL, that can be used to describe interfaces that are intended to be implemented in web browsers. Web IDL is an IDL variant with a number of features that allow the behavior of common script objects in the web platform to be specified more readily. How interfaces described with Web IDL correspond to constructs within ECMAScript and Java execution environments is also detailed.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-WebIDL-20101021</howpublished>
		<title type="sharef:primaryTitle">Web IDL</title>
		<field type="bibtex:topic">dom[0.9] webidl[1] idl[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2010/WD-WebIDL-20101021</identifier>
	</reference>
	<reference name="dom" src="bibtex:misc" src-info="bibtex:line-36107" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Vidur</givenname>
				<surname>Apparao</surname>
			</person>
			<person>
				<givenname>Steven</givenname>
				<surname>Byrne</surname>
			</person>
			<person>
				<givenname>Mike</givenname>
				<surname>Champion</surname>
			</person>
			<person>
				<givenname>Scott</givenname>
				<surname>Isaacs</surname>
			</person>
			<person>
				<givenname>Ian</givenname>
				<surname>Jacobs</surname>
			</person>
			<person>
				<givenname>Arnaud</givenname>
				<surname>Le Hors</surname>
			</person>
			<person>
				<givenname>Gavin Thomas</givenname>
				<surname>Nicol</surname>
			</person>
			<person>
				<givenname>Jonathan</givenname>
				<surname>Robie</surname>
			</person>
			<person>
				<givenname>Robert</givenname>
				<surname>Sutor</surname>
			</person>
			<person>
				<givenname>Chris</givenname>
				<surname>Wilson</surname>
			</person>
			<person>
				<givenname>Lauren</givenname>
				<surname>Wood</surname>
			</person>
		</names>
		<date value="1998-10"/>
		<abstract>
			<richtext>
				<p>This specification defines the Document Object Model Level 1, a platform- and language-neutral interface that allows programs and scripts to dynamically access and update the content, structure and style of documents. The Document Object Model provides a standard set of objects for representing HTML and XML documents, a standard model of how these objects can be combined, and a standard interface for accessing and manipulating them. Vendors can support the DOM as an interface to their proprietary data structures and APIs, and content authors can write to the standard DOM interfaces rather than product-specific APIs, thus increasing interoperability on the Web. The goal of the DOM specification is to define a programmatic interface for XML and HTML. The DOM Level 1 specification is separated into two parts: Core and HTML. The Core DOM Level 1 section provides a low-level set of fundamental interfaces that can represent any structured document, as well as defining extended interfaces for representing an XML document. These extended XML interfaces need not be implemented by a DOM implementation that only provides access to HTML documents; all of the fundamental interfaces in the Core section must be implemented. A compliant DOM implementation that implements the extended XML interfaces is required to also implement the fundamental Core interfaces, but not the HTML interfaces. The HTML Level 1 section provides additional, higher-level interfaces that are used with the fundamental interfaces defined in the Core Level 1 section to provide a more convenient view of an HTML document. A compliant implementation of the HTML DOM implements all of the fundamental Core interfaces as well as the HTML interfaces.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Recommendation REC-DOM-Level-1-19981001</howpublished>
		<title type="sharef:primaryTitle">Document Object Model (DOM) Level 1 Specification</title>
		<field type="bibtex:topic">dom1[1]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/1998/REC-DOM-Level-1-19981001</identifier>
	</reference>
	<reference name="dom1sec" src="bibtex:misc" src-info="bibtex:line-36118" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Lauren</givenname>
				<surname>Wood</surname>
			</person>
			<person>
				<givenname>Arnaud</givenname>
				<surname>Le Hors</surname>
			</person>
			<person>
				<givenname>Vidur</givenname>
				<surname>Apparao</surname>
			</person>
			<person>
				<givenname>Steven</givenname>
				<surname>Byrne</surname>
			</person>
			<person>
				<givenname>Mike</givenname>
				<surname>Champion</surname>
			</person>
			<person>
				<givenname>Scott</givenname>
				<surname>Isaacs</surname>
			</person>
			<person>
				<givenname>Ian</givenname>
				<surname>Jacobs</surname>
			</person>
			<person>
				<givenname>Gavin Thomas</givenname>
				<surname>Nicol</surname>
			</person>
			<person>
				<givenname>Jonathan</givenname>
				<surname>Robie</surname>
			</person>
			<person>
				<givenname>Robert</givenname>
				<surname>Sutor</surname>
			</person>
			<person>
				<givenname>Chris</givenname>
				<surname>Wilson</surname>
			</person>
		</names>
		<date value="2000-09"/>
		<howpublished>World Wide Web Consortium, Working Draft WD-DOM-Level-1-20000929</howpublished>
		<title type="sharef:primaryTitle">Document Object Model (DOM) Level 1 Specification (Second Edition)</title>
		<field type="bibtex:topic">dom1[1]</field>
		<field type="bibtex:updates">dom</field>
	</reference>
	<reference name="dom2" src="bibtex:misc" src-info="bibtex:line-36128" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Lauren</givenname>
				<surname>Wood</surname>
			</person>
			<person>
				<givenname>Arnaud</givenname>
				<surname>Le Hors</surname>
			</person>
			<person>
				<givenname>Vidur</givenname>
				<surname>Apparao</surname>
			</person>
			<person>
				<givenname>Laurence</givenname>
				<surname>Cable</surname>
			</person>
			<person>
				<givenname>Mike</givenname>
				<surname>Champion</surname>
			</person>
			<person>
				<givenname>Joe</givenname>
				<surname>Kesselman</surname>
			</person>
			<person>
				<givenname>Philippe</givenname>
				<surname>Le Hégaret</surname>
			</person>
			<person>
				<givenname>Tom</givenname>
				<surname>Pixley</surname>
			</person>
			<person>
				<givenname>Jonathan</givenname>
				<surname>Robie</surname>
			</person>
			<person>
				<givenname>Peter</givenname>
				<surname>Sharpe</surname>
			</person>
			<person>
				<givenname>Chris</givenname>
				<surname>Wilson</surname>
			</person>
		</names>
		<date value="2000-05"/>
		<howpublished>World Wide Web Consortium, Candidate Recommendation CR-DOM-Level-2-20000510</howpublished>
		<title type="sharef:primaryTitle">Document Object Model (DOM) Level 2 Specification</title>
		<field type="bibtex:topic">dom2[1]</field>
		<field type="bibtex:updates">dom1sec</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2000/CR-DOM-Level-2-20000510</identifier>
	</reference>
	<reference name="dom2core" src="bibtex:misc" src-info="bibtex:line-36139" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Arnaud</givenname>
				<surname>Le Hors</surname>
			</person>
			<person>
				<givenname>Philippe</givenname>
				<surname>Le Hégaret</surname>
			</person>
			<person>
				<givenname>Lauren</givenname>
				<surname>Wood</surname>
			</person>
			<person>
				<givenname>Gavin Thomas</givenname>
				<surname>Nicol</surname>
			</person>
			<person>
				<givenname>Jonathan</givenname>
				<surname>Robie</surname>
			</person>
			<person>
				<givenname>Mike</givenname>
				<surname>Champion</surname>
			</person>
			<person>
				<givenname>Steven</givenname>
				<surname>Byrne</surname>
			</person>
		</names>
		<date value="2000-11"/>
		<howpublished>World Wide Web Consortium, Recommendation REC-DOM-Level-2-Core-20001113</howpublished>
		<title type="sharef:primaryTitle">Document Object Model (DOM) Level 2 Core Specification</title>
		<field type="bibtex:topic">dom2[1]</field>
		<field type="bibtex:updates">dom2</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2000/REC-DOM-Level-2-Core-20001113</identifier>
	</reference>
	<reference name="dom2views" src="bibtex:misc" src-info="bibtex:line-36150" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Arnaud</givenname>
				<surname>Le Hors</surname>
			</person>
			<person>
				<givenname>Laurence</givenname>
				<surname>Cable</surname>
			</person>
		</names>
		<date value="2000-11"/>
		<howpublished>World Wide Web Consortium, Recommendation REC-DOM-Level-2-Views-20001113</howpublished>
		<title type="sharef:primaryTitle">Document Object Model (DOM) Level 2 Views Specification</title>
		<field type="bibtex:topic">dom2[1]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2000/REC-DOM-Level-2-Views-20001113</identifier>
	</reference>
	<reference name="dom2style" src="bibtex:misc" src-info="bibtex:line-36160" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Chris</givenname>
				<surname>Wilson</surname>
			</person>
			<person>
				<givenname>Philippe</givenname>
				<surname>Le Hégaret</surname>
			</person>
			<person>
				<givenname>Vidur</givenname>
				<surname>Apparao</surname>
			</person>
		</names>
		<date value="2000-11"/>
		<howpublished>World Wide Web Consortium, Recommendation REC-DOM-Level-2-Style-20001113</howpublished>
		<title type="sharef:primaryTitle">Document Object Model (DOM) Level 2 Style Specification</title>
		<field type="bibtex:topic">dom2[1] css[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2000/REC-DOM-Level-2-Style-20001113</identifier>
	</reference>
	<reference name="dom2events" src="bibtex:misc" src-info="bibtex:line-36170" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Tom</givenname>
				<surname>Pixley</surname>
			</person>
		</names>
		<date value="2000-11"/>
		<howpublished>World Wide Web Consortium, Recommendation REC-DOM-Level-2-Events-20001113</howpublished>
		<title type="sharef:primaryTitle">Document Object Model (DOM) Level 2 Events Specification</title>
		<field type="bibtex:topic">dom2[1]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2000/REC-DOM-Level-2-Events-20001113</identifier>
	</reference>
	<reference name="dom2traverse" src="bibtex:misc" src-info="bibtex:line-36180" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Joe</givenname>
				<surname>Kesselman</surname>
			</person>
			<person>
				<givenname>Jonathan</givenname>
				<surname>Robie</surname>
			</person>
			<person>
				<givenname>Mike</givenname>
				<surname>Champion</surname>
			</person>
			<person>
				<givenname>Peter</givenname>
				<surname>Sharpe</surname>
			</person>
			<person>
				<givenname>Vidur</givenname>
				<surname>Apparao</surname>
			</person>
			<person>
				<givenname>Lauren</givenname>
				<surname>Wood</surname>
			</person>
		</names>
		<date value="2000-11"/>
		<howpublished>World Wide Web Consortium, Recommendation REC-DOM-Level-2-Traversal-Range-20001113</howpublished>
		<title type="sharef:primaryTitle">Document Object Model (DOM) Level 2 Traversal and Range Specification</title>
		<field type="bibtex:topic">dom2[1]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2000/REC-DOM-Level-2-Traversal-Range-20001113</identifier>
	</reference>
	<reference name="dom2html" src="bibtex:misc" src-info="bibtex:line-36190" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Johnny</givenname>
				<surname>Stenback</surname>
			</person>
			<person>
				<givenname>Philippe</givenname>
				<surname>Le Hégaret</surname>
			</person>
			<person>
				<givenname>Arnaud</givenname>
				<surname>Le Hors</surname>
			</person>
		</names>
		<date value="2003-01"/>
		<howpublished>World Wide Web Consortium, Recommendation REC-DOM-Level-2-HTML-20030109</howpublished>
		<title type="sharef:primaryTitle">Document Object Model (DOM) Level 2 HTML Specification</title>
		<field type="bibtex:topic">dom2[1] html[0.8]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2003/REC-DOM-Level-2-HTML-20030109</identifier>
	</reference>
	<reference name="dom3cor" src="bibtex:misc" src-info="bibtex:line-36200" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Arnaud</givenname>
				<surname>Le Hors</surname>
			</person>
			<person>
				<givenname>Philippe</givenname>
				<surname>Le Hégaret</surname>
			</person>
			<person>
				<givenname>Lauren</givenname>
				<surname>Wood</surname>
			</person>
			<person>
				<givenname>Gavin Thomas</givenname>
				<surname>Nicol</surname>
			</person>
			<person>
				<givenname>Jonathan</givenname>
				<surname>Robie</surname>
			</person>
			<person>
				<givenname>Mike</givenname>
				<surname>Champion</surname>
			</person>
			<person>
				<givenname>Steven</givenname>
				<surname>Byrne</surname>
			</person>
		</names>
		<date value="2004-04"/>
		<abstract>
			<richtext>
				<p>This specification defines the Document Object Model Core Level 3, a platform- and language-neutral interface that allows programs and scripts to dynamically access and update the content, structure and style of documents. The Document Object Model Core Level 3 builds on the Document Object Model Core Level 2. This version enhances DOM Level 2 Core by completing the mapping between DOM and the XML Information Set, including the support for XML Base, adding the ability to attach user information to DOM Nodes or to bootstrap a DOM implementation, providing mechanisms to resolve namespace prefixes or to manipulate "ID" attributes, giving to type information, etc.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Recommendation REC-DOM-Level-3-Core-20040407</howpublished>
		<title type="sharef:primaryTitle">Document Object Model (DOM) Level 3 Core Specification</title>
		<field type="bibtex:topic">dom3[1]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2004/REC-DOM-Level-3-Core-20040407</identifier>
	</reference>
	<reference name="webdomcore" src="bibtex:misc" src-info="bibtex:line-36211" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Anne</givenname>
				<surname link="van">Kesteren</surname>
			</person>
		</names>
		<date value="2010-10"/>
		<abstract>
			<richtext>
				<p>Web DOM Core defines the DOM Core part of the Web platform. The DOM is a language- and platform neutral interface that allows programs and scripts to dynamically access and update the content and structure of documents.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-domcore-20101007</howpublished>
		<title type="sharef:primaryTitle">Web DOM Core</title>
		<field type="bibtex:topic">dom3[0.9] html5[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2010/WD-domcore-20101007</identifier>
	</reference>
	<reference name="dom3con" src="bibtex:misc" src-info="bibtex:line-36222" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Ben</givenname>
				<surname>Chang</surname>
			</person>
			<person>
				<givenname>Andy</givenname>
				<surname>Heninger</surname>
			</person>
			<person>
				<givenname>Joe</givenname>
				<surname>Kesselman</surname>
			</person>
			<person>
				<givenname>Rezaur</givenname>
				<surname>Rahman</surname>
			</person>
		</names>
		<date value="2001-02"/>
		<howpublished>World Wide Web Consortium, Working Draft WD-DOM-Level-3-CMLS-20010209</howpublished>
		<title type="sharef:primaryTitle">Document Object Model (DOM) Level 3 Content Models and Load and Save Specification</title>
		<field type="bibtex:topic">dom3[1]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2001/WD-DOM-Level-3-CMLS-20010209</identifier>
	</reference>
	<reference name="dom3ev" src="bibtex:misc" src-info="bibtex:line-36232" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Doug</givenname>
				<surname>Schepers</surname>
			</person>
			<person>
				<givenname>Björn</givenname>
				<surname>Höhrmann</surname>
			</person>
			<person>
				<givenname>Philippe</givenname>
				<surname>Le Hégaret</surname>
			</person>
			<person>
				<givenname>Tom</givenname>
				<surname>Pixley</surname>
			</person>
		</names>
		<date value="2010-09"/>
		<abstract>
			<richtext>
				<p>This specification defines the Document Object Model Events Level 3, a generic platform- and language-neutral event system which allows registration of event handlers, describes event flow through a tree structure, and provides basic contextual information for each event. The Document Object Model Events Level 3 builds on the Document Object Model Events Level 2.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-DOM-Level-3-Events-20100907</howpublished>
		<title type="sharef:primaryTitle">Document Object Model (DOM) Level 3 Events Specification</title>
		<field type="bibtex:topic">dom3[1]</field>
		<field type="bibtex:updates">dom2events</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2010/WD-DOM-Level-3-Events-20100907</identifier>
	</reference>
	<reference name="dom3view" src="bibtex:misc" src-info="bibtex:line-36244" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Ray</givenname>
				<surname>Whitmer</surname>
			</person>
		</names>
		<date value="2004-02"/>
		<howpublished>World Wide Web Consortium, Note NOTE-DOM-Level-3-Views-20040226</howpublished>
		<title type="sharef:primaryTitle">Document Object Model (DOM) Level 3 Views and Formatting Specification</title>
		<field type="bibtex:topic">dom3[1]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2004/NOTE-DOM-Level-3-Views-20040226</identifier>
	</reference>
	<reference name="dom3xpath" src="bibtex:misc" src-info="bibtex:line-36254" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Ray</givenname>
				<surname>Whitmer</surname>
			</person>
		</names>
		<date value="2004-02"/>
		<howpublished>World Wide Web Consortium, Note NOTE-DOM-Level-3-XPath-20040226</howpublished>
		<title type="sharef:primaryTitle">Document Object Model (DOM) Level 3 XPath Specification</title>
		<field type="bibtex:topic">dom3[1] xpath1[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2004/NOTE-DOM-Level-3-XPath-20040226</identifier>
	</reference>
	<reference name="dom3asls" src="bibtex:misc" src-info="bibtex:line-36264" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Ben</givenname>
				<surname>Chang</surname>
			</person>
			<person>
				<givenname>Elena</givenname>
				<surname>Litani</surname>
			</person>
			<person>
				<givenname>Jeroen</givenname>
				<surname link="van">Rotterdam</surname>
			</person>
			<person>
				<givenname>Johnny</givenname>
				<surname>Stenback</surname>
			</person>
			<person>
				<givenname>Andy</givenname>
				<surname>Heninger</surname>
			</person>
			<person>
				<givenname>Joe</givenname>
				<surname>Kesselman</surname>
			</person>
			<person>
				<givenname>Rezaur</givenname>
				<surname>Rahman</surname>
			</person>
		</names>
		<date value="2002-04"/>
		<howpublished>World Wide Web Consortium, Working Draft WD-DOM-Level-3-ASLS-20020409</howpublished>
		<title type="sharef:primaryTitle">Document Object Model (DOM) Level 3 Abstract Schemas and Load and Save Specification</title>
		<field type="bibtex:topic">dom3[1]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2002/WD-DOM-Level-3-ASLS-20020409</identifier>
	</reference>
	<reference name="dom3val" src="bibtex:misc" src-info="bibtex:line-36274" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Ben</givenname>
				<surname>Chang</surname>
			</person>
			<person>
				<givenname>Joe</givenname>
				<surname>Kesselman</surname>
			</person>
			<person>
				<givenname>Rezaur</givenname>
				<surname>Rahman</surname>
			</person>
		</names>
		<date value="2004-01"/>
		<howpublished>World Wide Web Consortium, Recommendation REC-DOM-Level-3-Val-20040127</howpublished>
		<title type="sharef:primaryTitle">Document Object Model (DOM) Level 3 Validation Specification</title>
		<field type="bibtex:topic">dom3[1]</field>
		<field type="bibtex:updates">dom3asls</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2004/REC-DOM-Level-3-Val-20040127</identifier>
	</reference>
	<reference name="dom3ls" src="bibtex:misc" src-info="bibtex:line-36285" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Johnny</givenname>
				<surname>Stenback</surname>
			</person>
			<person>
				<givenname>Andy</givenname>
				<surname>Heninger</surname>
			</person>
		</names>
		<date value="2004-04"/>
		<howpublished>World Wide Web Consortium, Recommendation REC-DOM-Level-3-LS-20040407</howpublished>
		<title type="sharef:primaryTitle">Document Object Model (DOM) Level 3 Load and Save Specification</title>
		<field type="bibtex:topic">dom3[1]</field>
		<field type="bibtex:updates">dom3asls</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2004/REC-DOM-Level-3-LS-20040407</identifier>
	</reference>
	<reference name="dom3as" src="bibtex:misc" src-info="bibtex:line-36296" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Ben</givenname>
				<surname>Chang</surname>
			</person>
			<person>
				<givenname>Elena</givenname>
				<surname>Litani</surname>
			</person>
			<person>
				<givenname>Joe</givenname>
				<surname>Kesselman</surname>
			</person>
			<person>
				<givenname>Rezaur</givenname>
				<surname>Rahman</surname>
			</person>
		</names>
		<date value="2002-07"/>
		<howpublished>World Wide Web Consortium, Note NOTE-DOM-Level-3-AS-20020725</howpublished>
		<title type="sharef:primaryTitle">Document Object Model (DOM) Level 3 Abstract Schemas Specification</title>
		<field type="bibtex:topic">dom3[1]</field>
		<field type="bibtex:updates">dom3asls</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2002/NOTE-DOM-Level-3-AS-20020725</identifier>
	</reference>
	<reference name="elementtraversal" src="bibtex:misc" src-info="bibtex:line-36307" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Doug</givenname>
				<surname>Schepers</surname>
			</person>
			<person>
				<givenname>Robin</givenname>
				<surname>Berjon</surname>
			</person>
		</names>
		<date value="2008-12"/>
		<abstract>
			<richtext>
				<p>This specification defines the ElementTraversal interface, which allows script navigation of the elements of a DOM tree, excluding all other nodes in the DOM, such as text nodes. It also provides a property to expose the number of child elements of an element. It is intended to provide a more convenient alternative to existing DOM navigation interfaces, with a low implementation footprint.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Recommendation REC-ElementTraversal-20081222</howpublished>
		<title type="sharef:primaryTitle">Element Traversal Specification</title>
		<field type="bibtex:topic">dom3[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2008/REC-ElementTraversal-20081222</identifier>
	</reference>
	<reference name="navigationtiming" src="bibtex:misc" src-info="bibtex:line-36318" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Zhiheng</givenname>
				<surname>Wang</surname>
			</person>
		</names>
		<date value="2011-03"/>
		<abstract>
			<richtext>
				<p>This specification defines an interface for web applications to access timing information related to navigation and elements.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Candidate Recommendation CR-navigation-timing-20110315</howpublished>
		<title type="sharef:primaryTitle">Navigation Timing</title>
		<field type="bibtex:topic">dom3[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2011/CR-navigation-timing-20110315</identifier>
	</reference>
	<reference name="qaframeintro" src="bibtex:misc" src-info="bibtex:line-36329" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Lofton</givenname>
				<surname>Henderson</surname>
			</person>
			<person>
				<givenname>Lynne</givenname>
				<surname>Rosenthal</surname>
			</person>
		</names>
		<date value="2003-09"/>
		<howpublished>World Wide Web Consortium, Note NOTE-qaframe-intro-20030912</howpublished>
		<title type="sharef:primaryTitle">QA Framework: Introduction</title>
		<identifier type="sharef:uri">http://www.w3.org/TR/2003/NOTE-qaframe-intro-20030912</identifier>
	</reference>
	<reference name="qaframeops" src="bibtex:misc" src-info="bibtex:line-36338" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Lofton</givenname>
				<surname>Henderson</surname>
			</person>
			<person>
				<givenname>Dominique</givenname>
				<surname>Hazaël-Massieux</surname>
			</person>
			<person>
				<givenname>Lynne</givenname>
				<surname>Rosenthal</surname>
			</person>
			<person>
				<givenname>Kirill</givenname>
				<surname>Gavrylyuk</surname>
			</person>
		</names>
		<date value="2003-09"/>
		<howpublished>World Wide Web Consortium, Candidate Recommendation CR-qaframe-ops-20030922</howpublished>
		<title type="sharef:primaryTitle">QA Framework: Operational Guidelines</title>
		<identifier type="sharef:uri">http://www.w3.org/TR/2003/CR-qaframe-ops-20030922</identifier>
	</reference>
	<reference name="qahandbook" src="bibtex:misc" src-info="bibtex:line-36347" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Daniel</givenname>
				<surname>Dardailler</surname>
			</person>
			<person>
				<givenname>Dimitris</givenname>
				<surname>Dimitriadis</surname>
			</person>
			<person>
				<givenname>Karl</givenname>
				<surname>Dubost</surname>
			</person>
			<person>
				<givenname>Dominique</givenname>
				<surname>Hazaël-Massieux</surname>
			</person>
			<person>
				<givenname>Lofton</givenname>
				<surname>Henderson</surname>
			</person>
			<person>
				<givenname>David</givenname>
				<surname>Marston</surname>
			</person>
			<person>
				<givenname>Patrick</givenname>
				<surname>Curran</surname>
			</person>
			<person>
				<givenname>Lynne</givenname>
				<surname>Rosenthal</surname>
			</person>
			<person>
				<givenname>Mark</givenname>
				<surname>Skall</surname>
			</person>
			<person>
				<givenname>Andrew</givenname>
				<surname>Thackrah</surname>
			</person>
			<person>
				<givenname>Olivier</givenname>
				<surname>Théreaux</surname>
			</person>
			<person>
				<givenname>Jeremy J.</givenname>
				<surname>Carroll</surname>
			</person>
			<person>
				<givenname>Richard</givenname>
				<surname>Kennedy</surname>
			</person>
			<person>
				<givenname>Tim</givenname>
				<surname>Boland</surname>
			</person>
		</names>
		<names type="sharef:editor">
			<person>
				<givenname>Lofton</givenname>
				<surname>Henderson</surname>
			</person>
		</names>
		<date value="2005-09"/>
		<abstract>
			<richtext>
				<p>The QA Handbook (QAH) is a non-normative handbook about the process and operational aspects of certain quality assurance practices of W3C's Working Groups, with particular focus on testability and test topics. It is intended for Working Group chairs and team contacts. It aims to help them to avoid known pitfalls and benefit from experiences gathered from the W3C Working Groups themselves. It provides techniques, tools, and templates that should facilitate and accelerate their work. This document is one of the QA Framework (QAF) family of documents of the Quality Assurance (QA) Activity. QAF includes the other in-progress specification, Specification Guidelines, plus a handful of test- and other QA-related notes, advanced topics, and Wiki page collections.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Note NOTE-qa-handbook-20050906</howpublished>
		<title type="sharef:primaryTitle">The QA Handbook</title>
		<field type="bibtex:updates">qaframeintro qaframeops</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2005/NOTE-qa-handbook-20050906</identifier>
	</reference>
	<reference name="qaframespec" src="bibtex:misc" src-info="bibtex:line-36359" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Karl</givenname>
				<surname>Dubost</surname>
			</person>
			<person>
				<givenname>Lynne</givenname>
				<surname>Rosenthal</surname>
			</person>
			<person>
				<givenname>Dominique</givenname>
				<surname>Hazaël-Massieux</surname>
			</person>
			<person>
				<givenname>Lofton</givenname>
				<surname>Henderson</surname>
			</person>
		</names>
		<date value="2005-08"/>
		<abstract>
			<richtext>
				<p>The goal of this document is to help W3C editors write better specifications, by making a specification easier to interpret without ambiguity and clearer as to what is required in order to conform. It focuses on how to define and specify conformance. It also addresses how a specification might allow variation among conforming implementations. The document presents guidelines or requirements, supplemented with good practices, examples and techniques.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Recommendation REC-qaframe-spec-20050817</howpublished>
		<title type="sharef:primaryTitle">QA Framework: Specification Guidelines</title>
		<identifier type="sharef:uri">http://www.w3.org/TR/2005/REC-qaframe-spec-20050817</identifier>
	</reference>
	<reference name="specvariability" src="bibtex:misc" src-info="bibtex:line-36369" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Dominique</givenname>
				<surname>Hazaël-Massieux</surname>
			</person>
			<person>
				<givenname>Lynne</givenname>
				<surname>Rosenthal</surname>
			</person>
		</names>
		<date value="2005-08"/>
		<abstract>
			<richtext>
				<p>This document details and deepens some of the most important concepts related to conformance when designing a specification. It is a companion document of QA Specification Guidelines. It analyzes how design decisions of a specification's conformance model may affect its implementability and the interoperability of its implementations.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Note NOTE-spec-variability-20050831</howpublished>
		<title type="sharef:primaryTitle">Variability in Specifications</title>
		<identifier type="sharef:uri">http://www.w3.org/TR/2005/NOTE-spec-variability-20050831</identifier>
	</reference>
	<reference name="testmethodology" src="bibtex:misc" src-info="bibtex:line-36379" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Dominique</givenname>
				<surname>Hazaël-Massieux</surname>
			</person>
			<person>
				<givenname>Marcos</givenname>
				<surname>Cáceres</surname>
			</person>
		</names>
		<date value="2010-01"/>
		<abstract>
			<richtext>
				<p>In this document we present a method for writing, marking-up, and analyzing conformance requirements in technical specifications.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Note NOTE-test-methodology-20100128</howpublished>
		<title type="sharef:primaryTitle">A Method for Writing Testable Conformance Requirements</title>
		<identifier type="sharef:uri">http://www.w3.org/TR/2010/NOTE-test-methodology-20100128</identifier>
	</reference>
	<reference name="qaframeopex" src="bibtex:misc" src-info="bibtex:line-36389" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Lofton</givenname>
				<surname>Henderson</surname>
			</person>
			<person>
				<givenname>Lynne</givenname>
				<surname>Rosenthal</surname>
			</person>
			<person>
				<givenname>Dimitris</givenname>
				<surname>Dimitriadis</surname>
			</person>
			<person>
				<givenname>Kirill</givenname>
				<surname>Gavrylyuk</surname>
			</person>
		</names>
		<date value="2002-12"/>
		<abstract>
			<richtext>
				<p>This document is part of the of the Quality Assurance (QA) Activity. It presents examples and describes the techniques of operational aspects of quality practices within the W3C's Working Groups. It complements QA Framework: Operational Guidelines, by specifying or illustrating how Working Groups might meet the operational and process-related checkpoints of that document.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Note NOTE-qaframe-ops-extech-20021202</howpublished>
		<title type="sharef:primaryTitle">QA Framework: Operational Examples &amp; Techniques</title>
		<identifier type="sharef:uri">http://www.w3.org/TR/2002/NOTE-qaframe-ops-extech-20021202</identifier>
	</reference>
	<reference name="qaframetest" src="bibtex:misc" src-info="bibtex:line-36399" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Patrick</givenname>
				<surname>Curran</surname>
			</person>
			<person>
				<givenname>Dimitris</givenname>
				<surname>Dimitriadis</surname>
			</person>
		</names>
		<date value="2004-08"/>
		<abstract>
			<richtext>
				<p>The principal goal of QA Framework: Test Guidelines is to help W3C Working Groups to develop more useful and usable test materials. The material is to be presented as a set of principles and good practices. This document is one in a family of QA Framework documents of the Quality Assurance (QA) Activity. The other existing or in-progress specifications are: The QA Handbook, and Specification Guidelines.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-qaframe-test-20040820</howpublished>
		<title type="sharef:primaryTitle">QA Framework: Test Guidelines</title>
		<identifier type="sharef:uri">http://www.w3.org/TR/2004/WD-qaframe-test-20040820</identifier>
	</reference>
	<reference name="mmireqs" src="bibtex:misc" src-info="bibtex:line-36409" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Stéphane H.</givenname>
				<surname>Maes</surname>
			</person>
			<person>
				<givenname>Vijay</givenname>
				<surname>Saraswat</surname>
			</person>
		</names>
		<date value="2003-01"/>
		<abstract>
			<richtext>
				<p>This document describes fundamental requirements for the specifications under development in the W3C Multimodal Interaction Activity. These requirements were derived from use case studies as discussed in Appendix A. They have been developed for use by the Multimodal Interaction Working Group (W3C Members only), but may also be relevant to other W3C working groups and related external standard activities. The requirements cover general issues, inputs, outputs, architecture, integration, synchronization points, runtimes and deployments, but this document does not address application or deployment conformance rules.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Note NOTE-mmi-reqs-20030108</howpublished>
		<title type="sharef:primaryTitle">Multimodal Interaction Requirements</title>
		<identifier type="sharef:uri">http://www.w3.org/TR/2003/NOTE-mmi-reqs-20030108</identifier>
	</reference>
	<reference name="mmisuggestions" src="bibtex:misc" src-info="bibtex:line-36419" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Jim</givenname>
				<surname>Larson</surname>
			</person>
		</names>
		<date value="2006-09"/>
		<abstract>
			<richtext>
				<p>This document is based on the accumulated experience of several years of developing multimodal applications. It provides a collection of common sense advice for developers of multimodal user interfaces.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Note NOTE-mmi-suggestions-20060911</howpublished>
		<title type="sharef:primaryTitle">Common Sense Suggestions for Developing Multimodal User Interfaces</title>
		<identifier type="sharef:uri">http://www.w3.org/TR/2006/NOTE-mmi-suggestions-20060911</identifier>
	</reference>
	<reference name="mmiauth" src="bibtex:misc" src-info="bibtex:line-36429" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Ingmar</givenname>
				<surname>Kliche</surname>
			</person>
		</names>
		<date value="2008-07"/>
		<abstract>
			<richtext>
				<p>This document describes a multimodal system which implements the W3C Multimodal Architecture and gives an example of a simple multimodal application authored using various W3C markup languages, including SCXML, CCXML, VoiceXML 2.1 and HTML.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Note NOTE-mmi-auth-20080702</howpublished>
		<title type="sharef:primaryTitle">Authoring Applications for the Multimodal Architecture</title>
		<identifier type="sharef:uri">http://www.w3.org/TR/2008/NOTE-mmi-auth-20080702</identifier>
	</reference>
	<reference name="mmimcbp" src="bibtex:misc" src-info="bibtex:line-36439" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Deborah</givenname>
				<surname>Dahl</surname>
			</person>
			<person>
				<givenname>James A.</givenname>
				<surname>Larson</surname>
			</person>
			<person>
				<givenname>B. Helena</givenname>
				<surname>Rodriguez</surname>
			</person>
			<person>
				<givenname>Muthuselvam</givenname>
				<surname>Selvaraj</surname>
			</person>
		</names>
		<names type="sharef:editor">
			<person>
				<givenname>Ingmar</givenname>
				<surname>Kliche</surname>
			</person>
		</names>
		<date value="2011-03"/>
		<abstract>
			<richtext>
				<p>This document describes Modality Components in the MMI Architecture which are responsible for controlling the various input and output modalities on various devices by providing guidelines and suggestions for designing Modality Components. Also this document shows several possible examples of Modality Components, (1) face identification, (2) form-filling using handwriting recognition and (3) video display.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Note NOTE-mmi-mcbp-20110301</howpublished>
		<title type="sharef:primaryTitle">Best Practices for Creating MMI Modality Components</title>
		<identifier type="sharef:uri">http://www.w3.org/TR/2011/NOTE-mmi-mcbp-20110301</identifier>
	</reference>
	<reference name="sysenv" src="bibtex:misc" src-info="bibtex:line-36450" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Keith</givenname>
				<surname>Waters</surname>
			</person>
			<person>
				<givenname>Rafah A.</givenname>
				<surname>Hosn</surname>
			</person>
			<person>
				<givenname>Dave</givenname>
				<surname>Raggett</surname>
			</person>
		</names>
		<date value="2004-07"/>
		<abstract>
			<richtext>
				<p>The W3C Multimodal Interaction working group aims to develop specifications to enable access to the Web using multiple modes of interaction, such as speech, pen, keypad, bitmapped displays etc. This document is part of a suite of specifications for multimodal systems, and provides details of a platform and language neutral software interface that enables applications to dynamically determine and respond to changes in device capabilities, device configuration, user preferences and environmental conditions, such as low battery alerts or loss of network connectivity.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-sysenv-20040728</howpublished>
		<title type="sharef:primaryTitle">System and Environment Framework</title>
		<identifier type="sharef:uri">http://www.w3.org/TR/2004/WD-sysenv-20040728</identifier>
	</reference>
	<reference name="systeminfoapi" src="bibtex:misc" src-info="bibtex:line-36460" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Dzung D.</givenname>
				<surname>Tran</surname>
			</person>
			<person>
				<givenname>Max</givenname>
				<surname>Froumentin</surname>
			</person>
		</names>
		<date value="2010-01"/>
		<abstract>
			<richtext>
				<p>This specification defines an API to provide Web applications with access to various properties of the system which they are running on. Specifically, properties pertaining to the device hardware are addressed. Examples include battery status, current network bandwidth. Additionally, some of those properties offer access to the environment around the device, such as ambient brightness or atmospheric pressure.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-system-info-api-20100202</howpublished>
		<title type="sharef:primaryTitle">The System Information API</title>
		<identifier type="sharef:uri">http://www.w3.org/TR/2010/WD-system-info-api-20100202</identifier>
	</reference>
	<reference name="dpf" src="bibtex:misc" src-info="bibtex:line-36470" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Keith</givenname>
				<surname>Waters</surname>
			</person>
			<person>
				<givenname>Rafah A.</givenname>
				<surname>Hosn</surname>
			</person>
			<person>
				<givenname>Dave</givenname>
				<surname>Raggett</surname>
			</person>
			<person>
				<givenname>Sailesh</givenname>
				<surname>Sathish</surname>
			</person>
			<person>
				<givenname>Matt</givenname>
				<surname>Womer</surname>
			</person>
			<person>
				<givenname>Max</givenname>
				<surname>Froumentin</surname>
			</person>
			<person>
				<givenname>Rhys</givenname>
				<surname>Lewis</surname>
			</person>
			<person>
				<givenname>Keith</givenname>
				<surname>Rosenblatt</surname>
			</person>
		</names>
		<date value="2007-12"/>
		<abstract>
			<richtext>
				<p>This document defines platform and language neutral interfaces that provide Web applications with access to a hierarchy of dynamic properties representing device capabilities, configurations, user preferences and environmental conditions.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Candidate Recommendation CR-DPF-20071221</howpublished>
		<title type="sharef:primaryTitle">Delivery Context: Client Interfaces (DCCI) 1.0 — Accessing Static and Dynamic Delivery Context Properties</title>
		<field type="bibtex:topic">dpf[1] dci[1]</field>
		<field type="bibtex:updates">sysenv</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2007/CR-DPF-20071221</identifier>
	</reference>
	<reference name="modalityinterface" src="bibtex:misc" src-info="bibtex:line-36482" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Jonny</givenname>
				<surname>Axelsson</surname>
			</person>
			<person>
				<givenname>Stephen</givenname>
				<surname>Potter</surname>
			</person>
			<person>
				<givenname>T. V.</givenname>
				<surname>Raman</surname>
			</person>
			<person>
				<givenname>Dave</givenname>
				<surname>Raggett</surname>
			</person>
		</names>
		<names type="sharef:editor">
			<person>
				<givenname>Brad</givenname>
				<surname>Porter</surname>
			</person>
		</names>
		<date value="2004-05"/>
		<abstract>
			<richtext>
				<p>This document describes the DOM capabilities needed to support a heterogeneous multimodal environment and the current state of DOM interfaces supporting those capabilities. These DOM interfaces are used between modality components and their host environment in the W3C Multimodal Interaction Framework as proposed by the W3C Multimodal Interaction Activity. The Multimodal Interaction Framework separates multimodal systems into a set of functional units, including Input and Output components, an Interaction Manager, Session Components, System and Environment, and Application Functions. In order for those functional components to interact with each other to form an application interpreter, the browser implementation must allow for communication and coordination between those components. This DOM interface identifies the DOM APIs used to communicate and coordinate at the browser implementation level. Multimodal browsers can be stand-alone or distributed systems.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Note NOTE-modality-interface-20040510</howpublished>
		<title type="sharef:primaryTitle">Modality Component to Host Environment DOM Requirements and Capabilities Assessment</title>
		<identifier type="sharef:uri">http://www.w3.org/TR/2004/NOTE-modality-interface-20040510</identifier>
	</reference>
	<reference name="emmareqs" src="bibtex:misc" src-info="bibtex:line-36493" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Stéphane H.</givenname>
				<surname>Maes</surname>
			</person>
			<person>
				<givenname>Stephen</givenname>
				<surname>Potter</surname>
			</person>
		</names>
		<date value="2003-01"/>
		<abstract>
			<richtext>
				<p>This document describes requirements for the Extensible MultiModal Annotation language (EMMA) specification under development in the W3C Multimodal Interaction Activity. EMMA is intended as a data format for the interface between input processors and interaction management systems. It will define the means for recognizers to annotate application specific data with information such as confidence scores, time stamps, input mode (e.g. key strokes, speech or pen), alternative recognition hypotheses, and partial recognition results, etc. EMMA is a target data format for the semantic interpretation specification being developed in the Voice Browser Activity, and which describes annotations to speech grammars for extracting application specific data as a result of speech recognition. EMMA supersedes earlier work on the natural language semantics markup language in the Voice Browser Activity.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Note NOTE-EMMAreqs-20030113</howpublished>
		<title type="sharef:primaryTitle">Requirements for EMMA</title>
		<field type="bibtex:topic">emma[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2003/NOTE-EMMAreqs-20030113</identifier>
	</reference>
	<reference name="emma" src="bibtex:misc" src-info="bibtex:line-36504" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Paolo</givenname>
				<surname>Baggia</surname>
			</person>
			<person>
				<givenname>Daniel C.</givenname>
				<surname>Burnett</surname>
			</person>
			<person>
				<givenname>Jerry</givenname>
				<surname>Carter</surname>
			</person>
			<person>
				<givenname>Deborah A.</givenname>
				<surname>Dahl</surname>
			</person>
			<person>
				<givenname>Gerald</givenname>
				<surname>McCobb</surname>
			</person>
			<person>
				<givenname>Dave</givenname>
				<surname>Raggett</surname>
			</person>
		</names>
		<names type="sharef:editor">
			<person>
				<givenname>Michael</givenname>
				<surname>Johnston</surname>
			</person>
		</names>
		<date value="2009-02"/>
		<abstract>
			<richtext>
				<p>The W3C Multimodal Interaction Working Group aims to develop specifications to enable access to the Web using multi-modal interaction. This document is part of a set of specifications for multi-modal systems, and provides details of an XML markup language for describing the interpretation of user input. Examples of interpretation of user input are a transcription into words of a raw signal, for instance derived from speech, pen or keystroke input, a set of attribute/value pairs describing their meaning, or a set of attribute/value pairs describing a gesture. The interpretation of the user's input is expected to be generated by signal interpretation processes, such as speech and ink recognition, semantic interpreters, and other types of processors for use by components that act on the user's inputs such as interaction managers.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Recommendation REC-emma-20090210</howpublished>
		<title type="sharef:primaryTitle">EMMA: Extensible MultiModal Annotation Markup Language</title>
		<field type="bibtex:topic">emma[1]</field>
		<field type="bibtex:updates">emmareqs</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2009/REC-emma-20090210</identifier>
	</reference>
	<reference name="mmidevfeedback" src="bibtex:misc" src-info="bibtex:line-36517" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Andrew</givenname>
				<surname>Wahbe</surname>
			</person>
			<person>
				<givenname>Gerald</givenname>
				<surname>McCobb</surname>
			</person>
			<person>
				<givenname>Klaus</givenname>
				<surname>Reifenrath</surname>
			</person>
			<person>
				<givenname>Raj</givenname>
				<surname>Tumuluri</surname>
			</person>
			<person>
				<givenname>Sunil</givenname>
				<surname>Kumar</surname>
			</person>
		</names>
		<date value="2006-04"/>
		<abstract>
			<richtext>
				<p>Several years of multimodal application development in various business areas and on various device platforms has provided developers enough experience to provide detailed feedback about what they like, dislike, and want to see improve and continue. This experience is provided here as an input to the specifications under development in the W3C Multimodal Interaction and Voice Browser Activities.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Note NOTE-mmi-dev-feedback-20060414</howpublished>
		<title type="sharef:primaryTitle">Multimodal Application Developer Feedback</title>
		<identifier type="sharef:uri">http://www.w3.org/TR/2006/NOTE-mmi-dev-feedback-20060414</identifier>
	</reference>
	<reference name="mmiframe" src="bibtex:misc" src-info="bibtex:line-36527" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>James A.</givenname>
				<surname>Larson</surname>
			</person>
			<person>
				<givenname>T. V.</givenname>
				<surname>Raman</surname>
			</person>
			<person>
				<givenname>Dave</givenname>
				<surname>Raggett</surname>
			</person>
		</names>
		<date value="2003-05"/>
		<abstract>
			<richtext>
				<p>This document introduces the W3C Multimodal Interaction Framework, and identifies the major components for multimodal systems. Each component represents a set of related functions. The framework identifies the markup languages used to describe information required by components and for data flowing among components. The W3C Multimodal Interaction Framework describes input and output modes widely used today and can be extended to include additional modes of user input and output as they become available.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Note NOTE-mmi-framework-20030506</howpublished>
		<title type="sharef:primaryTitle">W3C Multimodal Interaction Framework</title>
		<identifier type="sharef:uri">http://www.w3.org/TR/2003/NOTE-mmi-framework-20030506</identifier>
	</reference>
	<reference name="mmiusecases" src="bibtex:misc" src-info="bibtex:line-36537" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Emily</givenname>
				<surname>Candell</surname>
			</person>
			<person>
				<givenname>Dave</givenname>
				<surname>Raggett</surname>
			</person>
		</names>
		<date value="2002-12"/>
		<abstract>
			<richtext>
				<p>The W3C Multimodal Interaction Activity is developing specifications as a basis for a new breed of Web applications in which you can interact using multiple modes of interaction, for instance, using speech, hand writing, and key presses for input, and spoken prompts, audio and visual displays for output. This document describes several use cases for multimodal interaction and presents them in terms of varying device capabilities and the events needed by each use case to couple different components of a multimodal application.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Note NOTE-mmi-use-cases-20021204</howpublished>
		<title type="sharef:primaryTitle">Multimodal Interaction Use Cases</title>
		<identifier type="sharef:uri">http://www.w3.org/TR/2002/NOTE-mmi-use-cases-20021204</identifier>
	</reference>
	<reference name="mmiarch" src="bibtex:misc" src-info="bibtex:line-36547" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Michael</givenname>
				<surname>Bodell</surname>
			</person>
			<person>
				<givenname>Deborah A.</givenname>
				<surname>Dahl</surname>
			</person>
			<person>
				<givenname>Ingmar</givenname>
				<surname>Kliche</surname>
			</person>
			<person>
				<givenname>Jim</givenname>
				<surname>Larson</surname>
			</person>
			<person>
				<givenname>Raj</givenname>
				<surname>Tumuluri</surname>
			</person>
			<person>
				<givenname>Moshe</givenname>
				<surname>Yudkowsky</surname>
			</person>
			<person>
				<givenname>Muthuselvam</givenname>
				<surname>Selvaraj</surname>
			</person>
			<person>
				<givenname>Brad</givenname>
				<surname>Porter</surname>
			</person>
			<person>
				<givenname>Dave</givenname>
				<surname>Raggett</surname>
			</person>
			<person>
				<givenname>T. V.</givenname>
				<surname>Raman</surname>
			</person>
			<person>
				<givenname>Andrew</givenname>
				<surname>Wahbe</surname>
			</person>
		</names>
		<names type="sharef:editor">
			<person>
				<givenname>James</givenname>
				<surname>Barnett</surname>
			</person>
		</names>
		<date value="2011-01"/>
		<abstract>
			<richtext>
				<p>This document describes a loosely coupled architecture for multimodal user interfaces, which allows for co-resident and distributed implementations, and focuses on the role of markup and scripting, and the use of well defined interfaces between its constituents.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-mmi-arch-20110125</howpublished>
		<title type="sharef:primaryTitle">Multimodal Architecture and Interfaces</title>
		<identifier type="sharef:uri">http://www.w3.org/TR/2011/WD-mmi-arch-20110125</identifier>
	</reference>
	<reference name="ctguidelines" src="bibtex:misc" src-info="bibtex:line-36558" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Jo</givenname>
				<surname>Rabin</surname>
			</person>
		</names>
		<date value="2010-10"/>
		<abstract>
			<richtext>
				<p>This document provides guidance to Content Transformation proxies as to whether and how to transform Web content. Content Transformation proxies alter requests sent by user agents to servers and responses returned by servers so that the appearance, structure or control flow of Web applications are modified. Content Transformation proxies are mostly used to convert Web sites designed for desktop computers to a form suitable for mobile devices. Based on current practice and standards, this document specifies mechanisms with which Content Transformation proxies should make their presence known to other parties, present the outcome of alterations performed on HTTP traffic, and react to indications set by clients or servers to constrain these alterations. The objective is to reduce undesirable effects on Web applications, especially mobile-ready ones, and to limit the diversity in the modes of operation of Content Transformation proxies, while at the same time allowing proxies to alter content that would otherwise not display successfully on mobile devices. Important considerations regarding the impact on security are highlighted.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Note NOTE-ct-guidelines-20101026</howpublished>
		<title type="sharef:primaryTitle">Guidelines for Web Content Transformation Proxies 1.0</title>
		<identifier type="sharef:uri">http://www.w3.org/TR/2010/NOTE-ct-guidelines-20101026</identifier>
	</reference>
	<reference name="inkreqs" src="bibtex:misc" src-info="bibtex:line-36568" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Yi-Min</givenname>
				<surname>Chee</surname>
			</person>
			<person>
				<givenname>Sai</givenname>
				<surname>Prasad</surname>
			</person>
		</names>
		<date value="2003-01"/>
		<abstract>
			<richtext>
				<p>This document describes requirements for the Ink Markup Language that will be used in the multimodal interaction framework as proposed by the W3C Multimodal Interaction Working Group. The Ink Markup Language will serve as the data format for representing ink entered with an electronic pen or stylus in a multimodal system. The markup will allow for the input and processing of handwriting, gestures, sketches, music and other notational languages in web-based multimodal applications. In the context of the W3C Multimodal Interaction Framework, the markup provides a common format for the exchange of ink data between components such as handwriting and gesture recognizers, signature verifiers, and other ink-aware modules.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Note NOTE-inkreqs-20030122</howpublished>
		<title type="sharef:primaryTitle">Requirements for the Ink Markup Language</title>
		<identifier type="sharef:uri">http://www.w3.org/TR/2003/NOTE-inkreqs-20030122</identifier>
	</reference>
	<reference name="smux" src="bibtex:misc" src-info="bibtex:line-36578" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Jim</givenname>
				<surname>Gettys</surname>
			</person>
			<person>
				<givenname>Henrik</givenname>
				<surname>Frystyk Nielsen</surname>
			</person>
		</names>
		<date value="1998-07"/>
		<abstract>
			<richtext>
				<p>This document defines the experimental multiplexing protocol referred to as "SMUX". SMUX is a session management protocol separating the underlying transport from the upper level application protocols. It provides a lightweight communication channel to the application layer by multiplexing data streams on top of a reliable stream oriented transport. By supporting coexistence of multiple application level protocols (e.g. HTTP and HTTP/NG), SMUX should ease transitions to future Web protocols, and communications of client applets using private protocols with servers over the same TCP connection as the HTTP conversation.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-mux-19980708</howpublished>
		<title type="sharef:primaryTitle">SMUX Protocol Specification</title>
		<field type="bibtex:topic">smux[1]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/1998/WD-mux-19980710</identifier>
	</reference>
	<reference name="sox" src="bibtex:misc" src-info="bibtex:line-36589" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Andrew</givenname>
				<surname>Davidson</surname>
			</person>
			<person>
				<givenname>Matthew</givenname>
				<surname>Fuchs</surname>
			</person>
			<person>
				<givenname>Mette</givenname>
				<surname>Hedin</surname>
			</person>
			<person>
				<givenname>Mudita</givenname>
				<surname>Jain</surname>
			</person>
			<person>
				<givenname>Jari</givenname>
				<surname>Koistinen</surname>
			</person>
			<person>
				<givenname>Chris</givenname>
				<surname>Lloyd</surname>
			</person>
			<person>
				<givenname>Murray</givenname>
				<surname>Maloney</surname>
			</person>
			<person>
				<givenname>Kelly</givenname>
				<surname>Schwarzhof</surname>
			</person>
		</names>
		<date value="1999-07"/>
		<abstract>
			<richtext>
				<p>This document describes SOX 2.0, the second version of the Schema for Object-Oriented XML. SOX is a schema language (or metagrammar) for defining the syntactic structure and partial semantics of XML document types. As such, SOX is an alternative to XML DTDs and can be used to define the same class of document types (with the exception of external parsed entities). However, SOX extends the language of DTDs by supporting: 1. An extensive (and extensible) set of datatypes; 2. Inheritance among element types; 3. Namespaces; 4. Polymorphic content; 5. Embedded documentation; 6. Features to enable robust distributed schema management. All of these features are supported with strong type-checking and validation. A SOX schema is also a valid XML instance according to the SOX DTD, enabling the application of XML content management tools to schema management. SOX was initially developed to support the development of large-scale, distributed electronic commerce applications but is applicable across the whole range of applications of markup. As compared to XML DTDs, SOX dramatically decreases the complexity of supporting interoperation among heterogenous applications by facilitating software mapping of XML data structures, expressing domain abstractions and common relationships directly and explicitly, enabling reuse at the document design and the application programming levels, and supporting the generation of common application components. Although SOX 2.0 retains many of the features of SOX 1.0, it represents an additional year of actual implementation experience. Commerce One has a working implementation of this language and will be releasing products based on it. Our goals in releasing this second version are two-fold: 1. Ensure that the public record accurately reflects the evolution of SOX. Members of the community wishing to understand SOX, build tools using SOX, or interoperate with SOX applications, need access to the current version of the language. 2. Expose some of the fruits of our implementation experience to the general community, particularly to assist in the ongoing work at the W3C to develop an official XML Schema language. From the markup world, the SOX proposal is informed by the XML 1.0 specification as well as the XML-Data submission and the Document Content Description submission. However many of SOX' requirements come from the distributed computing world and SOX features have been heavily influenced by the Java programming language.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Note NOTE-SOX</howpublished>
		<title type="sharef:primaryTitle">Schema for Object-Oriented XML 2.0</title>
		<field type="bibtex:topic">sox[1]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/NOTE-SOX</identifier>
	</reference>
	<reference name="httpng" src="bibtex:misc" src-info="bibtex:line-36600" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Bill</givenname>
				<surname>Janssen</surname>
			</person>
			<person>
				<givenname>Henrik</givenname>
				<surname>Frystyk Nielsen</surname>
			</person>
			<person>
				<givenname>Mike</givenname>
				<surname>Spreitzer</surname>
			</person>
		</names>
		<date value="1998-07"/>
		<howpublished>World Wide Web Consortium, Working Draft WD-HTTP-NG-architecture-19980710</howpublished>
		<field type="bibtex:index">HTTP-NG</field>
		<title type="sharef:primaryTitle">HTTP-ng Architectural Model</title>
		<identifier type="sharef:uri">http://www.w3.org/TR/1998/WD-HTTP-NG-architecture-19980710</identifier>
	</reference>
	<reference name="widgets10reqs" src="bibtex:misc" src-info="bibtex:line-36610" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Marcos</givenname>
				<surname>Cáceres</surname>
			</person>
		</names>
		<date value="2010-10"/>
		<abstract>
			<richtext>
				<p>This document lists the design goals and requirements that specifications would need to address in order to standardize various aspects of widgets. A Widget is an interactive single purpose application for displaying and/or updating local data or data on the Web, packaged in a way to allow a single download and installation on a user's machine or mobile device. Typical examples of widgets include clocks, CPU gauges, sticky notes, battery-life indicators, games, and widgets that make use of Web services, like weather forecasters, news readers, e-mail checkers, photo albums and currency converters.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-widgets-reqs-20101026</howpublished>
		<title type="sharef:primaryTitle">Widgets 1.0: Requirements</title>
		<identifier type="sharef:uri">http://www.w3.org/TR/2010/WD-widgets-reqs-20101026</identifier>
	</reference>
	<reference name="widgets10" src="bibtex:misc" src-info="bibtex:line-36620" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Marcos</givenname>
				<surname>Cáceres</surname>
			</person>
		</names>
		<date value="2011-03"/>
		<abstract>
			<richtext>
				<p>This specification standardizes a packaging format and metadata for a class of software known as widgets. Unlike traditional user interface widgets (e.g., buttons, input boxes, toolbars, etc.), widgets as specified in this document are full-fledged client-side applications that are authored using technologies such as HTML5 and then packaged for distribution. Examples range from simple clocks, stock tickers, news casters, games and weather forecasters, to complex applications that pull data from multiple sources to be "mashed-up" and presented to a user in some interesting and useful way. The specification relies on PKWare's Zip specification as the archive format, XML as a configuration document format, and a series of steps that runtimes follow when processing and verifying various aspects of a package. The packaging format acts as a container for files used by a widget. The configuration document is an XML vocabulary that declares metadata and configuration parameters for a widget. The steps for processing a widget package describe the expected behavior and means of error handling for runtimes while processing the packaging format, configuration document, and other relevant files. This specification is part of the Widgets family of specifications, which together standardize widgets as a whole.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-widgets-20110322</howpublished>
		<title type="sharef:primaryTitle">Widget Packaging and Configuration</title>
		<identifier type="sharef:uri">http://www.w3.org/TR/2011/WD-widgets-20110322</identifier>
	</reference>
	<reference name="widgets10land" src="bibtex:misc" src-info="bibtex:line-36630" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Marcos</givenname>
				<surname>Cáceres</surname>
			</person>
		</names>
		<date value="2008-04"/>
		<abstract>
			<richtext>
				<p>This document surveys a group of market-leading widget user agents with the aim to inform the requirements of the Widgets 1.0: Requirements document. The survey exposes commonalities and fragmentation across widget user agents, and discusses how fragmentation currently affects, amongst other things, authoring, security, distribution and deployment, internationalization and the device-independence of widgets. The document concludes by making a set of recommendations on what aspects of widgets require standardization to reduce fragmentation to ultimately standardize a cross-platform widget solution.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-widgets-land-20080414</howpublished>
		<title type="sharef:primaryTitle">Widgets 1.0: The Widget Landscape (Q1 2008)</title>
		<identifier type="sharef:uri">http://www.w3.org/TR/2008/WD-widgets-land-20080414</identifier>
	</reference>
	<reference name="widgets10digsig" src="bibtex:misc" src-info="bibtex:line-36640" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Frederick</givenname>
				<surname>Hirsch</surname>
			</person>
			<person>
				<givenname>Marcos</givenname>
				<surname>Cáceres</surname>
			</person>
			<person>
				<givenname>Mark</givenname>
				<surname>Priestley</surname>
			</person>
		</names>
		<date value="2010-06"/>
		<abstract>
			<richtext>
				<p>This document defines a profile of the XML Signature Syntax and Processing 1.1 specification to allow a widget package to be digitally signed. Widget authors and distributors can digitally sign widgets as a mechanism to ensure continuity of authorship and distributorship. Prior to instantiation, a user agent can use the digital signature to verify the integrity of the widget package and to confirm the signing key(s). This document specifies conformance requirements on both widget packages and user agents.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Candidate Recommendation CR-widgets-digsig-20100624</howpublished>
		<title type="sharef:primaryTitle">Digital Signatures for Widgets</title>
		<field type="bibtex:topic">xmldsig[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2010/CR-widgets-digsig-20100624</identifier>
	</reference>
	<reference name="widgets10updates" src="bibtex:misc" src-info="bibtex:line-36651" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Marcos</givenname>
				<surname>Cáceres</surname>
			</person>
			<person>
				<givenname>Richard</givenname>
				<surname>Tibbett</surname>
			</person>
			<person>
				<givenname>Robin</givenname>
				<surname>Berjon</surname>
			</person>
		</names>
		<date value="2010-09"/>
		<abstract>
			<richtext>
				<p>This specification defines a process and a document format to allow a user agent to update an installed widget package with different version of a widget package. A widget cannot update itself; instead, a widget relies on the user agent to manage the update process. A user agent can perform an update over HTTP and from non-HTTP sources (e.g., directly from a device's memory card or hard disk).</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft /WD-widgets-updates-20100928</howpublished>
		<title type="sharef:primaryTitle">Widget Updates</title>
		<identifier type="sharef:uri">http://www.w3.org/TR/2010//WD-widgets-updates-20100928</identifier>
	</reference>
	<reference name="widgets10vmmf" src="bibtex:misc" src-info="bibtex:line-36661" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Marcin</givenname>
				<surname>Hanclik</surname>
			</person>
			<person>
				<givenname>Robin</givenname>
				<surname>Berjon</surname>
			</person>
			<person>
				<givenname>Arve</givenname>
				<surname>Bersvendsen</surname>
			</person>
			<person>
				<givenname>Marcos</givenname>
				<surname>Cáceres</surname>
			</person>
		</names>
		<date value="2009-10"/>
		<abstract>
			<richtext>
				<p>This specification defines a media feature and visual presentation modes of the document. Multiple view modes are specified that allow for accommodation of various content presentation use cases. This document builds upon the Media Queries and Widgets-Packaging specifications.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-widgets-vmmf-20091006</howpublished>
		<title type="sharef:primaryTitle">Widgets 1.0: View Modes Media Feature</title>
		<identifier type="sharef:uri">http://www.w3.org/TR/2009/WD-widgets-vmmf-20091006</identifier>
	</reference>
	<reference name="viewmode" src="bibtex:misc" src-info="bibtex:line-36671" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Robin</givenname>
				<surname>Berjon</surname>
			</person>
			<person>
				<givenname>Arve</givenname>
				<surname>Bersvendsen</surname>
			</person>
			<person>
				<givenname>Marcos</givenname>
				<surname>Cáceres</surname>
			</person>
			<person>
				<givenname>Marcin</givenname>
				<surname>Hanclik</surname>
			</person>
		</names>
		<date value="2010-06"/>
		<abstract>
			<richtext>
				<p>This specification defines a media feature to match the different visual presentation modes that can be applied to web applications and thereby apply different styling based on these different modes using CSS Media Queries.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Candidate Recommendation CR-view-mode-20100624</howpublished>
		<title type="sharef:primaryTitle">The 'view-mode' Media Feature</title>
		<field type="bibtex:updates">widgets10vmmf</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2010/CR-view-mode-20100624</identifier>
	</reference>
	<reference name="dapapireqs" src="bibtex:misc" src-info="bibtex:line-36682" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Robin</givenname>
				<surname>Berjon</surname>
			</person>
			<person>
				<givenname>Daniel</givenname>
				<surname>Coloma</surname>
			</person>
			<person>
				<givenname>Max</givenname>
				<surname>Froumentin</surname>
			</person>
			<person>
				<givenname>Marcin</givenname>
				<surname>Hanclik</surname>
			</person>
			<person>
				<givenname>Jere</givenname>
				<surname>Käpyaho</surname>
			</person>
			<person>
				<givenname>Kangchan</givenname>
				<surname>Lee</surname>
			</person>
			<person>
				<givenname>Bryan</givenname>
				<surname>Sullivan</surname>
			</person>
			<person>
				<givenname>Dzung</givenname>
				<surname>Tran</surname>
			</person>
		</names>
		<date value="2009-10"/>
		<abstract>
			<richtext>
				<p>These are the requirements intended to be met in the development of client-side APIs that enable the creation of Web Applications and Web Widgets that interact with devices services such as Calendar, Contacts, Camera, etc.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Note NOTE-dap-api-reqs-20091015</howpublished>
		<title type="sharef:primaryTitle">Device APIs Requirements</title>
		<identifier type="sharef:uri">http://www.w3.org/TR/2009/NOTE-dap-api-reqs-20091015</identifier>
	</reference>
	<reference name="dappolicyreqs" src="bibtex:misc" src-info="bibtex:line-36692" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Laura</givenname>
				<surname>Arribas</surname>
			</person>
			<person>
				<givenname>Frederick</givenname>
				<surname>Hirsch</surname>
			</person>
			<person>
				<givenname>Dominique</givenname>
				<surname>Hazaël-Massieux</surname>
			</person>
		</names>
		<date value="2011-03"/>
		<abstract>
			<richtext>
				<p>With the emergence of numerous new APIs in Web browsers and runtime engines, the need to control which Web sites and applications can make use of these APIs increases. This document describes use cases and requirements for controlling access to these APIs.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Note NOTE-dap-policy-reqs-20110317</howpublished>
		<title type="sharef:primaryTitle">Device API Access Control Use Cases and Requirements</title>
		<identifier type="sharef:uri">http://www.w3.org/TR/2011/NOTE-dap-policy-reqs-20110317</identifier>
	</reference>
	<reference name="apiperms" src="bibtex:misc" src-info="bibtex:line-36702" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Paddy</givenname>
				<surname>Byers</surname>
			</person>
			<person>
				<givenname>Frederick</givenname>
				<surname>Hirsch</surname>
			</person>
			<person>
				<givenname>Dominique</givenname>
				<surname>Hazaël-Massieux</surname>
			</person>
		</names>
		<date value="2010-10"/>
		<abstract>
			<richtext>
				<p>This document identifies the permissions that are needed to use specific client-side APIs which grant access to sensitive data and operations.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-api-perms-20101005</howpublished>
		<title type="sharef:primaryTitle">Permissions for Device API Access</title>
		<field type="bibtex:updates">dappolicyreqs</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2010/WD-api-perms-20101005</identifier>
	</reference>
	<reference name="dapprivacyreqs" src="bibtex:misc" src-info="bibtex:line-36713" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Alissa</givenname>
				<surname>Cooper</surname>
			</person>
			<person>
				<givenname>Frederick</givenname>
				<surname>Hirsch</surname>
			</person>
			<person>
				<givenname>John B.</givenname>
				<surname>Morris</surname>
			</person>
		</names>
		<date value="2010-06"/>
		<abstract>
			<richtext>
				<p>This document provides definitions, use cases, and requirements for making device APIs more privacy-friendly.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Note NOTE-dap-privacy-reqs-20100629</howpublished>
		<title type="sharef:primaryTitle">Device API Privacy Requirements</title>
		<identifier type="sharef:uri">http://www.w3.org/TR/2010/NOTE-dap-privacy-reqs-20100629</identifier>
	</reference>
	<reference name="widgetsapis" src="bibtex:misc" src-info="bibtex:line-36723" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Marcos</givenname>
				<surname>Cáceres</surname>
			</person>
			<person>
				<givenname>Robin</givenname>
				<surname>Berjon</surname>
			</person>
			<person>
				<givenname>Arve</givenname>
				<surname>Bersvendsen</surname>
			</person>
		</names>
		<date value="2010-09"/>
		<abstract>
			<richtext>
				<p>This specification defines an application programming interface (API) for widgets that provides, amongst other things, functionality for accessing a widget's metadata and persistently storing data.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Wokring Draft WD-widgets-apis-20100907</howpublished>
		<title type="sharef:primaryTitle">The Widget Interface</title>
		<identifier type="sharef:uri">http://www.w3.org/TR/2010/WD-widgets-apis-20100907</identifier>
	</reference>
	<reference name="widgetsaccess" src="bibtex:misc" src-info="bibtex:line-36733" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Robin</givenname>
				<surname>Berjon</surname>
			</person>
		</names>
		<date value="2010-04"/>
		<abstract>
			<richtext>
				<p>This specification defines the security model controlling network access from within a widget, as well as a method for widget authors to request that the user agent grant access to certain network resources or sets thereof.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Candidate Recommendation CR-widgets-access-20100420</howpublished>
		<title type="sharef:primaryTitle">Widgets 1.0: Access Requests Policy</title>
		<identifier type="sharef:uri">http://www.w3.org/TR/2010/CR-widgets-access-20100420</identifier>
	</reference>
	<reference name="widgetsuri" src="bibtex:misc" src-info="bibtex:line-36743" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Robin</givenname>
				<surname>Berjon</surname>
			</person>
		</names>
		<date value="2009-10"/>
		<abstract>
			<richtext>
				<p>This specification defines the widget URI scheme that is used to address resources inside a widget package.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-widgets-uri-20091008</howpublished>
		<title type="sharef:primaryTitle">Widgets 1.0: Widget URIs</title>
		<identifier type="sharef:uri">http://www.w3.org/TR/2009/WD-widgets-uri-20091008</identifier>
	</reference>
	<reference name="png" src="bibtex:misc" src-info="bibtex:line-36753" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Thomas</givenname>
				<surname>Boutell</surname>
			</person>
			<person>
				<givenname>Tom</givenname>
				<surname>Lane</surname>
			</person>
		</names>
		<date value="1996-10"/>
		<abstract>
			<richtext>
				<p>This document describes PNG (Portable Network Graphics), an extensible file format for the lossless, portable, well-compressed storage of raster images. PNG provides a patent-free replacement for GIF and can also replace many common uses of TIFF. Indexed-color, grayscale, and truecolor images are supported, plus an optional alpha channel. Sample depths range from 1 to 16 bits. PNG is designed to work well in online viewing applications, such as the World Wide Web, so it is fully streamable with a progressive display option. PNG is robust, providing both full file integrity checking and simple detection of common transmission errors. Also, PNG can store gamma and chromaticity data for improved color matching on heterogeneous platforms. This specification defines a proposed Internet Media Type image/png.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Recommendation REC-png-961001</howpublished>
		<title type="sharef:primaryTitle">PNG (Portable Network Graphics) Specification</title>
		<field type="bibtex:topic">png[1]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/REC-png-961001</identifier>
	</reference>
	<reference name="png2nd" src="bibtex:misc" src-info="bibtex:line-36764" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>David</givenname>
				<surname>Duce</surname>
			</person>
		</names>
		<date value="2003-11"/>
		<abstract>
			<richtext>
				<p>This document describes PNG (Portable Network Graphics), an extensible file format for the lossless, portable, well-compressed storage of raster images. PNG provides a patent-free replacement for GIF and can also replace many common uses of TIFF. Indexed-color, grayscale, and truecolor images are supported, plus an optional alpha channel. Sample depths range from 1 to 16 bits. PNG is designed to work well in online viewing applications, such as the World Wide Web, so it is fully streamable with a progressive display option. PNG is robust, providing both full file integrity checking and simple detection of common transmission errors. Also, PNG can store gamma and chromaticity data for improved color matching on heterogeneous platforms. This specification defines an Internet Media Type image/png.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Recommendation REC-PNG-20031110</howpublished>
		<title type="sharef:primaryTitle">Portable Network Graphics (PNG) Specification (Second Edition)</title>
		<field type="bibtex:topic">png[1]</field>
		<field type="bibtex:updates">png</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2003/REC-PNG-20031110</identifier>
	</reference>
	<reference name="sac" src="bibtex:misc" src-info="bibtex:line-36776" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Bert</givenname>
				<surname>Bos</surname>
			</person>
			<person>
				<givenname>Philippe</givenname>
				<surname>Le Hégaret</surname>
			</person>
		</names>
		<date value="2000-07"/>
		<howpublished>World Wide Web Consortium, Note NOTE-SAC-20000728</howpublished>
		<title type="sharef:primaryTitle">SAC: Simple API for CSS</title>
		<field type="bibtex:topic">css[0.9] sac[1]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2000/NOTE-SAC-20000728</identifier>
	</reference>
	<reference name="css1" src="bibtex:misc" src-info="bibtex:line-36786" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Håkon Wium</givenname>
				<surname>Lie</surname>
			</person>
			<person>
				<givenname>Bert</givenname>
				<surname>Bos</surname>
			</person>
		</names>
		<date value="1999-01"/>
		<howpublished>World Wide Web Consortium, Recommendation REC-CSS1-19990111</howpublished>
		<title type="sharef:primaryTitle">Cascading Style Sheets, level 1</title>
		<field type="bibtex:topic">css1[1]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/1999/REC-CSS1-19990111</identifier>
	</reference>
	<reference name="css2" src="bibtex:misc" src-info="bibtex:line-36796" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Bert</givenname>
				<surname>Bos</surname>
			</person>
			<person>
				<givenname>Håkon Wium</givenname>
				<surname>Lie</surname>
			</person>
			<person>
				<givenname>Chris</givenname>
				<surname>Lilley</surname>
			</person>
			<person>
				<givenname>Ian</givenname>
				<surname>Jacobs</surname>
			</person>
		</names>
		<date value="1998-05"/>
		<howpublished>World Wide Web Consortium, Recommendation REC-CSS2-19980512</howpublished>
		<title type="sharef:primaryTitle">CSS2 Specification</title>
		<field type="bibtex:topic">css2[1]</field>
		<field type="bibtex:updates">css1</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/1998/REC-CSS2-19980512</identifier>
	</reference>
	<reference name="css21" src="bibtex:misc" src-info="bibtex:line-36807" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Bert</givenname>
				<surname>Bos</surname>
			</person>
			<person>
				<givenname>Tantek</givenname>
				<surname>Çelik</surname>
			</person>
			<person>
				<givenname>Ian</givenname>
				<surname>Hickson</surname>
			</person>
			<person>
				<givenname>Håkon Wium</givenname>
				<surname>Lie</surname>
			</person>
		</names>
		<date value="2010-12"/>
		<abstract>
			<richtext>
				<p>This specification defines Cascading Style Sheets, level 2 revision 1 (CSS 2.1). CSS 2.1 is a style sheet language that allows authors and users to attach style (e.g., fonts and spacing) to structured documents (e.g., HTML documents and XML applications). By separating the presentation style of documents from the content of documents, CSS 2.1 simplifies Web authoring and site maintenance. CSS 2.1 builds on CSS2 which builds on CSS1. It supports media-specific style sheets so that authors may tailor the presentation of their documents to visual browsers, aural devices, printers, braille devices, handheld devices, etc. It also supports content positioning, table layout, features for internationalization and some properties related to user interface. CSS 2.1 corrects a few errors in CSS2 (the most important being a new definition of the height/width of absolutely positioned elements, more influence for HTML's "style" attribute and a new calculation of the 'clip' property), and adds a few highly requested features which have already been widely implemented. But most of all CSS 2.1 represents a "snapshot" of CSS usage: it consists of all CSS features that are implemented interoperably at the date of publication of the Recommendation. CSS 2.1 is derived from and is intended to replace CSS2. Some parts of CSS2 are unchanged in CSS 2.1, some parts have been altered, and some parts removed. The removed portions may be used in a future CSS3 specification. Future specs should refer to CSS 2.1 (unless they need features from CSS2 which have been dropped in CSS 2.1, and then they should only reference CSS2 for those features, or preferably reference such feature(s) in the respective CSS3 Module that includes those feature(s)).</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-CSS2-20101207</howpublished>
		<title type="sharef:primaryTitle">Cascading Style Sheets Level 2 Revision 1 (CSS 2.1) Specification</title>
		<field type="bibtex:topic">css2[1]</field>
		<field type="bibtex:updates">css2</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2010/WD-CSS2-20101207</identifier>
	</reference>
	<reference name="cssmobprof10" src="bibtex:misc" src-info="bibtex:line-36819" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Ted</givenname>
				<surname>Wugofski</surname>
			</person>
			<person>
				<givenname>Doug</givenname>
				<surname>Dominiak</surname>
			</person>
			<person>
				<givenname>Peter</givenname>
				<surname>Stark</surname>
			</person>
			<person>
				<givenname>Tapas</givenname>
				<surname>Roy</surname>
			</person>
		</names>
		<date value="2002-07"/>
		<howpublished>World Wide Web Consortium, Candidate Recommendation CR-css-mobile-20020725</howpublished>
		<title type="sharef:primaryTitle">CSS Mobile Profile 1.0</title>
		<field type="bibtex:topic">css[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2002/CR-css-mobile-20020725</identifier>
	</reference>
	<reference name="cssmobprof20" src="bibtex:misc" src-info="bibtex:line-36829" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Svante</givenname>
				<surname>Schubert</surname>
			</person>
		</names>
		<date value="2008-12"/>
		<abstract>
			<richtext>
				<p>This specification defines in general a subset of CSS 2.1 that is to be considered a baseline for interoperability between implementations of CSS on constrained devices (e.g. mobile phones). Its intent is not to produce a profile of CSS incompatible with the complete specification, but rather to ensure that implementations that due to platform limitations cannot support the entire specification implement a common subset that is interoperable not only amongst constrained implementations but also with complete ones. Additionally, this specification aligns itself as much as possible with the OMA Wireless CSS 1.1 specification. At the same time, OMA is doing alignment work in OMA  Wireless CSS 1.2. It is aimed at aligning the mandatory compliance items between CSS Mobile Profile 2.0 and OMA Wireless CSS 1.2.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Candidate Recommendation CR-css-mobile-20081210</howpublished>
		<title type="sharef:primaryTitle">CSS Mobile Profile 2.0</title>
		<field type="bibtex:topic">css[0.9]</field>
		<field type="bibtex:updates">cssmobprof10</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2008/CR-css-mobile-20081210</identifier>
	</reference>
	<reference name="csstvprof10" src="bibtex:misc" src-info="bibtex:line-36841" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Sean</givenname>
				<surname>Hayes</surname>
			</person>
			<person>
				<givenname>Glenn</givenname>
				<surname>Adams</surname>
			</person>
			<person>
				<givenname>Tantek</givenname>
				<surname>Çelik</surname>
			</person>
			<person>
				<givenname>Håkon Wium</givenname>
				<surname>Lie</surname>
			</person>
		</names>
		<date value="2003-05"/>
		<howpublished>World Wide Web Consortium, Candidate Recommendation CR-css-tv-20030514</howpublished>
		<title type="sharef:primaryTitle">CSS TV Profile 1.0</title>
		<field type="bibtex:topic">css[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2003/CR-css-tv-20030514</identifier>
	</reference>
	<reference name="csshtml" src="bibtex:misc" src-info="bibtex:line-36851" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Tantek</givenname>
				<surname>Çelik</surname>
			</person>
			<person>
				<givenname>Elika J.</givenname>
				<surname>Etemad</surname>
			</person>
		</names>
		<date value="2010-10"/>
		<abstract>
			<richtext>
				<p>Markup languages such as HTML and SVG provide a style attribute on most elements, to hold inline style information that applies to those elements. One of the possible style sheet languages is CSS. This draft describes the syntax and interpretation of the CSS fragment that can be used in such style attributes.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Candidate Recommendation CR-css-style-attr-20101012</howpublished>
		<title type="sharef:primaryTitle">CSS Style Attributes</title>
		<field type="bibtex:topic">css[1] html[1]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2010/CR-css-style-attr-20101012</identifier>
	</reference>
	<reference name="css3intro" src="bibtex:misc" src-info="bibtex:line-36862" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Eric A.</givenname>
				<surname>Meyer</surname>
			</person>
			<person>
				<givenname>Bert</givenname>
				<surname>Bos</surname>
			</person>
		</names>
		<date value="2001-05"/>
		<howpublished>World Wide Web Consortium, Working Draft WD-css3-roadmap-20010523</howpublished>
		<title type="sharef:primaryTitle">CSS3 Introduction</title>
		<field type="bibtex:topic">css3[1]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2001/WD-css3-roadmap-20010523</identifier>
	</reference>
	<reference name="css3syntax" src="bibtex:misc" src-info="bibtex:line-36872" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>L. David</givenname>
				<surname>Baron</surname>
			</person>
		</names>
		<date value="2003-08"/>
		<howpublished>World Wide Web Consortium, Working Draft WD-css3-syntax-20030813</howpublished>
		<title type="sharef:primaryTitle">CSS3 module: Syntax</title>
		<field type="bibtex:topic">css3[1]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2003/WD-css3-syntax-20030813</identifier>
	</reference>
	<reference name="css3preslev" src="bibtex:misc" src-info="bibtex:line-36882" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Ian</givenname>
				<surname>Hickson</surname>
			</person>
			<person>
				<givenname>Håkon Wium</givenname>
				<surname>Lie</surname>
			</person>
		</names>
		<date value="2003-08"/>
		<howpublished>World Wide Web Consortium, Working Draft WD-css3-preslev-20030813</howpublished>
		<title type="sharef:primaryTitle">CSS3 module: Presentation Levels</title>
		<field type="bibtex:topic">css3[1]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2003/WD-css3-preslev-20030813</identifier>
	</reference>
	<reference name="css3print" src="bibtex:misc" src-info="bibtex:line-36892" type="bibtex:misc">
		<names type="sharef:editor">
			<person>
				<givenname>Melinda</givenname>
				<surname>Grant</surname>
			</person>
		</names>
		<date value="2006-10"/>
		<abstract>
			<richtext>
				<p>This specification defines a subset of Cascading Style Sheets Level 2, revision 1 and CSS3 Module: Paged Media for printing to low-cost devices. It is designed for printing in situations where it is not feasible or desirable to install a printer-specific driver, and for situations were some variability in the output is acceptable. This profile is designed to work in conjunction with XHTML-Print and defines a minimum level of conformance as well as an extension set that provides stronger layout control for the printing of mixed text and images, tables and image collections.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-css-print-20061013</howpublished>
		<title type="sharef:primaryTitle">CSS Print Profile</title>
		<field type="bibtex:topic">css3[1]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2006/WD-css-print-20061013</identifier>
	</reference>
	<reference name="cssbeijing" src="bibtex:misc" src-info="bibtex:line-36903" type="bibtex:misc">
		<names type="sharef:editor">
			<person>
				<givenname>Elika J.</givenname>
				<surname>Etemad</surname>
			</person>
		</names>
		<date value="2010-07"/>
		<abstract>
			<richtext>
				<p>This document collects together into one definition all the specs that together form the current state of Cascading Style Sheets (CSS) as of 2007. The primary audience is CSS implementors, not CSS authors, as this definition includes modules by specification stability, not Web browser adoption rate.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-css-beijing-20100727</howpublished>
		<title type="sharef:primaryTitle">Cascading Style Sheets (CSS) Snapshot 2007</title>
		<field type="bibtex:topic">css[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2010/WD-css-beijing-20100727</identifier>
	</reference>
	<reference name="css2010" src="bibtex:misc" src-info="bibtex:line-36914" type="bibtex:misc">
		<names type="sharef:editor">
			<person>
				<givenname>Elika J.</givenname>
				<surname>Etemad</surname>
			</person>
		</names>
		<date value="2010-12"/>
		<abstract>
			<richtext>
				<p>This document collects together into one definition all the specs that together form the current state of Cascading Style Sheets (CSS) as of 2010. The primary audience is CSS implementors, not CSS authors, as this definition includes modules by specification stability, not Web browser adoption rate.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-css-2010-20101202</howpublished>
		<title type="sharef:primaryTitle">Cascading Style Sheets (CSS) Snapshot 2010</title>
		<field type="bibtex:topic">css[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2010/WD-css-2010-20101202</identifier>
	</reference>
	<reference name="cssomview" src="bibtex:misc" src-info="bibtex:line-36925" type="bibtex:misc">
		<names type="sharef:editor">
			<person>
				<givenname>Anne</givenname>
				<surname link="van">Kesteren</surname>
			</person>
		</names>
		<date value="2009-08"/>
		<abstract>
			<richtext>
				<p>The APIs introduced by this specification provide authors with a way to inspect and manipulate the visual view of a document. This includes getting the position of element layout boxes, obtaining the width of the viewport through script, and also scrolling an element. The CSSOM View Module also supercedes DOM Level 2 Views and therefore defines the AbstractView and DocumentView interfaces and extensions for them.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-cssom-view-20090804</howpublished>
		<title type="sharef:primaryTitle">CSSOM View Module</title>
		<field type="bibtex:topic">css[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2009/WD-cssom-view-20090804/</identifier>
	</reference>
	<reference name="becss" src="bibtex:misc" src-info="bibtex:line-36936" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Ian</givenname>
				<surname>Hickson</surname>
			</person>
		</names>
		<date value="2007-10"/>
		<abstract>
			<richtext>
				<p>Behavioral Extensions provide a way to link to binding technologies, such as XBL, from CSS style sheets. This allows bindings to be selected using the CSS cascade, and thus enables bindings to transparently benefit from the user style sheet mechanism, media selection, and alternate style sheets.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-becss-20071019</howpublished>
		<title type="sharef:primaryTitle">Behavioral Extensions to CSS</title>
		<field type="bibtex:topic">css3[1]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2007/WD-becss-20071019</identifier>
	</reference>
	<reference name="css3ruby" src="bibtex:misc" src-info="bibtex:line-36947" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Michel</givenname>
				<surname>Suignard</surname>
			</person>
		</names>
		<date value="2003-05"/>
		<howpublished>World Wide Web Consortium, Candidate Recommendation CR-css3-ruby-20030514</howpublished>
		<title type="sharef:primaryTitle">CSS3 Module: Ruby</title>
		<field type="bibtex:topic">css3[1]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2003/CR-css3-ruby-20030514</identifier>
	</reference>
	<reference name="css3ui" src="bibtex:misc" src-info="bibtex:line-36957" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Tantek</givenname>
				<surname>Çelik</surname>
			</person>
			<person>
				<givenname>Peter</givenname>
				<surname>Linss</surname>
			</person>
			<person>
				<givenname>Sho</givenname>
				<surname>Kuwamoto</surname>
			</person>
		</names>
		<date value="2000-04"/>
		<howpublished>World Wide Web Consortium, Working Draft WD-css3-userint-20000216</howpublished>
		<title type="sharef:primaryTitle">User Interface for CSS3</title>
		<field type="bibtex:topic">css3[1]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2000/WD-css3-userint-20000216</identifier>
	</reference>
	<reference name="css3ui2" src="bibtex:misc" src-info="bibtex:line-36967" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Tantek</givenname>
				<surname>Çelik</surname>
			</person>
		</names>
		<date value="2004-05"/>
		<howpublished>World Wide Web Consortium, Candidate Recommendation CR-css3-ui-20040511</howpublished>
		<title type="sharef:primaryTitle">CSS3 Module: Basic User Interface</title>
		<field type="bibtex:topic">css3[1]</field>
		<field type="bibtex:updates">css3ui</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2004/CR-css3-ui-20040511</identifier>
	</reference>
	<reference name="i18nformat" src="bibtex:misc" src-info="bibtex:line-36978" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Michel</givenname>
				<surname>Suignard</surname>
			</person>
			<person>
				<givenname>Takao</givenname>
				<surname>Suzuki</surname>
			</person>
			<person>
				<givenname>Chris</givenname>
				<surname>Wilson</surname>
			</person>
		</names>
		<names type="sharef:editor">
			<person>
				<givenname>Marcin</givenname>
				<surname>Sawicki</surname>
			</person>
		</names>
		<date value="1999-09"/>
		<abstract>
			<richtext>
				<p>The HyperText Markup Language (HTML) is a simple markup language used to create hypertext documents that are portable from one platform to another. HTML documents are SGML documents with generic semantics that are appropriate for representing information from a wide range of applications. CSS is a style sheets language that can be applied to HTML to control the style of a document: which fonts and colors to use, how much white space to insert, etc. The following specification extends CSS to support East Asian and Bi-directional text formatting. Familiarity with both CSS 2 and HTML 4.0 is assumed.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-i18n-format-19990910</howpublished>
		<title type="sharef:primaryTitle">International Layout</title>
		<field type="bibtex:updates">i18nformat</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/1999/WD-i18n-format-19990910</identifier>
	</reference>
	<reference name="css3text" src="bibtex:misc" src-info="bibtex:line-36990" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Elika J.</givenname>
				<surname>Etemad</surname>
			</person>
			<person>
				<givenname>Koji</givenname>
				<surname>Ishii</surname>
			</person>
			<person>
				<givenname>Shinyu</givenname>
				<surname>Murakami</surname>
			</person>
		</names>
		<date value="2011-04"/>
		<abstract>
			<richtext>
				<p>This CSS3 module defines properties for text manipulation and specifies their processing model. It covers line breaking, justification and alignment, white space handling, text decoration and text transformation.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-css3-text-20110412</howpublished>
		<title type="sharef:primaryTitle">CSS Text Level 3</title>
		<field type="bibtex:topic">css3[1]</field>
		<field type="bibtex:updates">i18nformat</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2011/WD-css3-text-20110412</identifier>
	</reference>
	<reference name="css3writingmodes" src="bibtex:misc" src-info="bibtex:line-37002" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Elika J.</givenname>
				<surname>Etemad</surname>
			</person>
			<person>
				<givenname>Koji</givenname>
				<surname>Ishii</surname>
			</person>
			<person>
				<givenname>Shinyu</givenname>
				<surname>Murakami</surname>
			</person>
		</names>
		<date value="2011-02"/>
		<abstract>
			<richtext>
				<p>CSS3 Writing Modes defines CSS features to support for various international writing modes, such as left-to-right (e.g. Latin or Indic), right-to-left (e.g. Hebrew or Arabic), bidirectional (e.g. mixed Latin and Arabic) and vertical (e.g. Asian scripts). Inherently bottom-to-top scripts are not handled in this version. See Unicode Technical Note #22 for an explanation of relevant issues.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-css3-writing-modes-20110201</howpublished>
		<title type="sharef:primaryTitle">CSS Writing Modes Module Level 3</title>
		<field type="bibtex:topic">css3[1]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2011/WD-css3-writing-modes-20110201</identifier>
	</reference>
	<reference name="css3page" src="bibtex:misc" src-info="bibtex:line-37013" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Håkon Wium</givenname>
				<surname>Lie</surname>
			</person>
			<person>
				<givenname>Melinda</givenname>
				<surname>Grant</surname>
			</person>
		</names>
		<date value="2006-10"/>
		<abstract>
			<richtext>
				<p>This module describes the page model that partitions a flow into pages. It builds on the  Box model module and introduces and defines the page model and paged media. It adds functionality for pagination, page margins, page size and orientation, headers and footers, widows and orphans, and image orientation. Finally it extends generated content to enable page numbering and running headers/footers.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-css3-page-20061010</howpublished>
		<title type="sharef:primaryTitle">CSS3 Module: Paged Media</title>
		<field type="bibtex:topic">css3[1]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2006/WD-css3-page-20061010</identifier>
	</reference>
	<reference name="css3gcpm" src="bibtex:misc" src-info="bibtex:line-37024" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Håkon Wium</givenname>
				<surname>Lie</surname>
			</person>
		</names>
		<date value="2010-06"/>
		<abstract>
			<richtext>
				<p>This module describes features often used in printed publications. Most of the specified functionality involves some sort of generated content where content from the document is adorned, replicated, or moved in the final presentation of the document. Along with two other CSS3 modules — multi-column layout and paged media — this module offers advanced functionality for presenting structured documents on paged media. This specification only applies to the 'print' media type.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-css3-gcpm-20100608</howpublished>
		<title type="sharef:primaryTitle">CSS Generated Content for Paged Media Module</title>
		<field type="bibtex:topic">css3[1]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2007/WD-css3-gcpm-20100608</identifier>
	</reference>
	<reference name="css3speech" src="bibtex:misc" src-info="bibtex:line-37035" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Dave</givenname>
				<surname>Raggett</surname>
			</person>
			<person>
				<givenname>Daniel</givenname>
				<surname>Glazman</surname>
			</person>
			<person>
				<givenname>Claudio</givenname>
				<surname>Santambrogio</surname>
			</person>
		</names>
		<date value="2004-12"/>
		<abstract>
			<richtext>
				<p>CSS (Cascading Style Sheets) is a language for describing the rendering of HTML and XML documents on screen, on paper, in speech, etc. CSS defines aural properties that give control over rendering XML to speech. This draft describes the text to speech properties proposed for CSS level 3. These are designed for match the model described in the Speech Synthesis Markup Language (SSML) Version 1.0.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-css3-speech-20041216</howpublished>
		<title type="sharef:primaryTitle">CSS3 Speech Module</title>
		<field type="bibtex:topic">css3[1] ssml[0.8]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2004/WD-css3-speech-20041216</identifier>
	</reference>
	<reference name="css3content" src="bibtex:misc" src-info="bibtex:line-37046" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Ian</givenname>
				<surname>Hickson</surname>
			</person>
		</names>
		<date value="2003-05"/>
		<abstract>
			<richtext>
				<p>This CSS3 Module describes how to insert and move content around a document, in order to create footnotes, endnotes, section notes. Inserted content can also introduce counters and strings, which can be used for running headers and footers, section numbering, and lists. Finally, techniques for declaring replaced images, as well as scaling and cropping them using CSS, are described.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-css3-content-20030514</howpublished>
		<title type="sharef:primaryTitle">CSS3 Generated and Replaced Content Module</title>
		<field type="bibtex:topic">css3[1]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2003/WD-css3-content-20030514</identifier>
	</reference>
	<reference name="css3line" src="bibtex:misc" src-info="bibtex:line-37057" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Michel</givenname>
				<surname>Suignard</surname>
			</person>
			<person>
				<givenname>Eric A.</givenname>
				<surname>Meyer</surname>
			</person>
		</names>
		<date value="2002-05"/>
		<abstract>
			<richtext>
				<p>This document presents a set of CSS line formatting properties. It also includes baseline alignment features as well as related functions like initial line and initial letter effect. It extends on the CSS 2 model.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-css3-linebox-20020515</howpublished>
		<title type="sharef:primaryTitle">CSS3 Module: Line</title>
		<field type="bibtex:topic">css3[1]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2002/WD-css3-linebox-20020515</identifier>
	</reference>
	<reference name="css3reader" src="bibtex:misc" src-info="bibtex:line-37068" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Bert</givenname>
				<surname>Bos</surname>
			</person>
		</names>
		<date value="2004-02"/>
		<abstract>
			<richtext>
				<p>'Reader' is a keyword for use in Media Queries. When a Media Query that includes the 'reader' keyword is attached to (a link to) a style sheet, it indicates that that style sheet is designed to be used by a "reader" device (typically a screen reader), that both displays and speaks a document at the same time. It may also display the document and render it in braille at the same time, or do all three. Media Queries (and thus 'reader') can be used in documents in HTML, XML, SVG, CSS and other formats, wherever they link to a style sheet, and potentially also in links to other resources. (But the latter is not treated in this specification.)</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-css3-reader-20040224</howpublished>
		<title type="sharef:primaryTitle">The CSS 'Reader' Media Type</title>
		<field type="bibtex:topic">css3[1]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2004/WD-css3-reader-20040224</identifier>
	</reference>
	<reference name="css3hyperlinks" src="bibtex:misc" src-info="bibtex:line-37079" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Tantek</givenname>
				<surname>Çelik</surname>
			</person>
			<person>
				<givenname>Bert</givenname>
				<surname>Bos</surname>
			</person>
			<person>
				<givenname>Daniel</givenname>
				<surname>Glazman</surname>
			</person>
		</names>
		<date value="2004-02"/>
		<abstract>
			<richtext>
				<p>CSS (Cascading Style Sheets) is a simple language for describing the presentation of documents. This specification is a module of level 3 of CSS and contains the functionality required to describe the presentation of hyperlink source anchors and the effects of hyperlink activation.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-css3-hyperlinks-20040224</howpublished>
		<title type="sharef:primaryTitle">CSS3 Hyperlink Presentation Module</title>
		<field type="bibtex:topic">css3[1]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2004/WD-css3-hyperlinks-20040224</identifier>
	</reference>
	<reference name="css3multi" src="bibtex:misc" src-info="bibtex:line-37090" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Håkon Wium</givenname>
				<surname>Lie</surname>
			</person>
		</names>
		<date value="2011-04"/>
		<abstract>
			<richtext>
				<p>This specification describes multi-column layouts in CSS, a style sheet language for the web. Using functionality described in the specification, content can be flowed into multiple columns with a gap and a rule between them.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Candidate Recommendation CR-css3-multicol-20110412</howpublished>
		<title type="sharef:primaryTitle">CSS Multi-column Layout Module</title>
		<field type="bibtex:topic">css3[1]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2011/CR-css3-multicol-20110412</identifier>
	</reference>
	<reference name="css3color" src="bibtex:misc" src-info="bibtex:line-37101" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Tantek</givenname>
				<surname>Çelik</surname>
			</person>
			<person>
				<givenname>Chris</givenname>
				<surname>Lilley</surname>
			</person>
			<person>
				<givenname>L. David</givenname>
				<surname>Baron</surname>
			</person>
		</names>
		<date value="2010-10"/>
		<abstract>
			<richtext>
				<p>CSS (Cascading Style Sheets) is a language for describing the rendering of HTML and XML documents on screen, on paper, in speech, etc. It uses color-related properties and values to color the text, backgrounds, borders, and other parts of elements in a document. This specification describes color values and properties for foreground color and group opacity. These include properties and values from CSS level 2 and new values.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Proposed Recommendation PR-css3-color-20101028</howpublished>
		<title type="sharef:primaryTitle">CSS Color Module Level 3</title>
		<field type="bibtex:topic">css3[1]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2010/PR-css3-color-20101028</identifier>
	</reference>
	<reference name="css3bg" src="bibtex:misc" src-info="bibtex:line-37112" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Tim</givenname>
				<surname>Boland</surname>
			</person>
			<person>
				<givenname>Bert</givenname>
				<surname>Bos</surname>
			</person>
		</names>
		<date value="2002-08"/>
		<abstract>
			<richtext>
				<p>CSS (Cascading Style Sheets) is a language for describing the rendering of structured documents (such as HTML and XML) on screen, on paper, in speech, etc. This draft describes the functionality that is proposed for CSS level 3 to describe backgrounds, such as background colors and background images. It includes and extends the functionality of CSS level 2, which builds on CSS Level 1.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-css3-background-20020802</howpublished>
		<title type="sharef:primaryTitle">CSS3 Module: Backgrounds</title>
		<field type="bibtex:topic">css3[1]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2002/WD-css3-background-20020802</identifier>
	</reference>
	<reference name="css3background" src="bibtex:misc" src-info="bibtex:line-37123" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Bert</givenname>
				<surname>Bos</surname>
			</person>
			<person>
				<givenname>Elika J.</givenname>
				<surname>Etemad</surname>
			</person>
			<person>
				<givenname>Brad</givenname>
				<surname>Kemper</surname>
			</person>
		</names>
		<date value="2011-02"/>
		<abstract>
			<richtext>
				<p>CSS is a language for describing the rendering of structured documents (such as HTML and XML) on screen, on paper, in speech, etc. This draft contains the features of CSS level 3 relating to borders and backgrounds. It includes and extends the functionality of CSS level 2, which builds on CSS level 1. The main extensions compared to level 2 are borders consisting of images, boxes with multiple backgrounds, boxes with rounded corners and boxes with shadows. This module replaces two earlier drafts: CSS3 Backgrounds and CSS3 Border.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Candidate Recommendation CR-css3-background-20110215</howpublished>
		<title type="sharef:primaryTitle">CSS Backgrounds and Borders Module Level 3</title>
		<field type="bibtex:topic">css3[1]</field>
		<field type="bibtex:updates">css3border css3bg</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2011/CR-css3-background-20110215</identifier>
	</reference>
	<reference name="css3sel" src="bibtex:misc" src-info="bibtex:line-37135" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Tantek</givenname>
				<surname>Çelik</surname>
			</person>
			<person>
				<givenname>Elika J.</givenname>
				<surname>Etemad</surname>
			</person>
			<person>
				<givenname>Daniel</givenname>
				<surname>Glazman</surname>
			</person>
			<person>
				<givenname>Ian</givenname>
				<surname>Hickson</surname>
			</person>
			<person>
				<givenname>Peter</givenname>
				<surname>Linss</surname>
			</person>
			<person>
				<givenname>John</givenname>
				<surname>Williams</surname>
			</person>
		</names>
		<date value="2009-12"/>
		<abstract>
			<richtext>
				<p>Selectors are patterns that match against elements in a tree, and as such form one of several technologies that can be used to select nodes in an XML document. Selectors have been optimized for use with HTML and XML, and are designed to be usable in performance-critical code. CSS (Cascading Style Sheets) is a language for describing the rendering of HTML and XML documents on screen, on paper, in speech, etc. CSS uses Selectors for binding style properties to elements in the document. This document describes the selectors that already exist in CSS1 and CSS2, and further introduces new selectors for CSS3 and other languages that may need them. Selectors define the following function: expression * element -&gt; boolean. That is, given an element and a selector, this specification defines whether that element matches the selector. These expressions can also be used, for instance, to select a set of elements, or a single element from a set of elements, by evaluating the expression across all the elements in a subtree. STTS (Simple Tree Transformation Sheets), a language for transforming XML trees, uses this mechanism.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Proposed Recommendation PR-css3-selectors-20091215</howpublished>
		<title type="sharef:primaryTitle">Selectors Level 3</title>
		<field type="bibtex:topic">css3[1]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2009/PR-css3-selectors-20091215</identifier>
	</reference>
	<reference name="selectorsapi" src="bibtex:misc" src-info="bibtex:line-37146" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Anne</givenname>
				<surname link="van">Kesteren</surname>
			</person>
			<person>
				<givenname>Lachlan</givenname>
				<surname>Hunt</surname>
			</person>
		</names>
		<date value="2009-12"/>
		<abstract>
			<richtext>
				<p>Selectors, which are widely used in CSS, are patterns that match against elements in a tree structure. The Selectors API specification defines methods for retrieving Element nodes from the DOM by matching against a group of selectors. It is often desirable to perform DOM operations on a specific set of elements in a document. These methods simplify the process of acquiring specific elements, especially compared with the more verbose techniques defined and used in the past.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Candidate Recommendation CR-selectors-api-20091222</howpublished>
		<title type="sharef:primaryTitle">Selectors API</title>
		<field type="bibtex:topic">css3[0.9] dom[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2009/CR-selectors-api-20091222</identifier>
	</reference>
	<reference name="selectorsapi2" src="bibtex:misc" src-info="bibtex:line-37157" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Lachlan</givenname>
				<surname>Hunt</surname>
			</person>
		</names>
		<date value="2010-01"/>
		<abstract>
			<richtext>
				<p>Selectors, which are widely used in CSS, are patterns that match against elements in a tree structure. The Selectors API specification defines methods for retrieving Element nodes from the DOM by matching against a group of selectors, and for testing if a given element matches a particular selector. It is often desirable to perform DOM operations on a specific set of elements in a document. These methods simplify the process of acquiring and testing specific elements, especially compared with the more verbose techniques defined and used in the past.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-selectors-api2-20100119</howpublished>
		<title type="sharef:primaryTitle">Selectors API Level 2</title>
		<field type="bibtex:topic">css3[0.9] dom[0.9]</field>
		<field type="bibtex:updates">selectorsapi</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2010/WD-selectors-api2-20100119</identifier>
	</reference>
	<reference name="css3cas" src="bibtex:misc" src-info="bibtex:line-37169" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Håkon Wium</givenname>
				<surname>Lie</surname>
			</person>
		</names>
		<date value="2005-12"/>
		<abstract>
			<richtext>
				<p>This CSS3 module describes how values are assigned to properties. CSS allows several style sheets to influence the rendering of a document, and the process of combining these style sheets is called "cascading". If no value can be found through cascading, a value can be inherited from the parent element or the property's initial value is used.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-css3-cascade-20051215</howpublished>
		<title type="sharef:primaryTitle">CSS3 Module: Cascading and Inheritance</title>
		<field type="bibtex:topic">css3[1]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2005/WD-css3-cascade-20051215</identifier>
	</reference>
	<reference name="css3layout" src="bibtex:misc" src-info="bibtex:line-37180" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Bert</givenname>
				<surname>Bos</surname>
			</person>
			<person>
				<givenname>César</givenname>
				<surname>Acebal</surname>
			</person>
		</names>
		<date value="2010-04"/>
		<abstract>
			<richtext>
				<p>CSS is a simple, declarative language for creating style sheets that specify the rendering of HTML and other structured documents. This specification is part of level 3 of CSS ("CSS3") and contains features to describe layouts at a high level, meant for tasks such as the positioning and alignment of "widgets" in a graphical user interface or the layout grid for a page or a window, in particular when the desired visual order is different from the order of the elements in the source document. Other CSS3 modules contain properties to specify fonts, colors, text alignment, list numbering, tables, etc. The features in this module are described together for easier reading, but are usually not implemented as a group. CSS3 modules often depend on other modules or contain features for several media types. Implementers should look at the various "profiles" of CSS, which list consistent sets of features for each type of media.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-css3-layout-20100429</howpublished>
		<title type="sharef:primaryTitle">CSS Template Layout Module</title>
		<field type="bibtex:topic">css3[1]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2010/WD-css3-layout-20100429</identifier>
	</reference>
	<reference name="css3grid" src="bibtex:misc" src-info="bibtex:line-37191" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Alex</givenname>
				<surname>Mogilevsky</surname>
			</person>
			<person>
				<givenname>Markus</givenname>
				<surname>Mielke</surname>
			</person>
		</names>
		<date value="2007-09"/>
		<abstract>
			<richtext>
				<p>This module describes integration of grid-based layout (similar to the grids traditionally used in books and newspapers) with CSS sizing and positioning.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-css3-grid-20070905</howpublished>
		<title type="sharef:primaryTitle">CSS Grid Positioning Module Level 3</title>
		<field type="bibtex:topic">css3[1]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2007/WD-css3-grid-20070905</identifier>
	</reference>
	<reference name="css3flexbox" src="bibtex:misc" src-info="bibtex:line-37202" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>L. David</givenname>
				<surname>Baron</surname>
			</person>
		</names>
		<date value="2009-07"/>
		<abstract>
			<richtext>
				<p>The draft describes a CSS box model optimized for interface design. It provides an additional layout system alongside the ones already in CSS. In this new box model, the children of a box are laid out either horizontally or vertically, and unused space can be assigned to a particular child or distributed among the children by assignment of "flex" to the children that should expand. Nesting of these boxes (horizontal inside vertical, or vertical inside horizontal) can be used to build layouts in two dimensions. This model is based on the box model in the XUL user-interface language used for the user interface of many Mozilla-based applications (such as Firefox).</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-css3-flexbox-20090723</howpublished>
		<title type="sharef:primaryTitle">Flexible Box Layout Module</title>
		<field type="bibtex:topic">css3[1]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2009/WD-css3-flexbox-20090723</identifier>
	</reference>
	<reference name="css3imagevalues" src="bibtex:misc" src-info="bibtex:line-37213" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Elika J.</givenname>
				<surname>Etemad</surname>
			</person>
		</names>
		<date value="2009-07"/>
		<abstract>
			<richtext>
				<p>This CSS Image Values module defines the syntax for &lt;image&gt; values in CSS. &lt;image&gt; values can be a single URI to an image, a list of URIs denoting a series of fallbacks, sprites (image slices), or gradients.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-css3-images-20090723</howpublished>
		<title type="sharef:primaryTitle">CSS Image Values Module Level 3</title>
		<field type="bibtex:topic">css3[1]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2009/WD-css3-images-20090723</identifier>
	</reference>
	<reference name="css3images" src="bibtex:misc" src-info="bibtex:line-37224" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Elika J.</givenname>
				<surname>Etemad</surname>
			</person>
			<person>
				<givenname>Tab</givenname>
				<surname>Atkins</surname>
			</person>
		</names>
		<date value="2011-02"/>
		<abstract>
			<richtext>
				<p>This CSS Image Values and Replaced Content module has two parts: First, it defines the syntax for &lt;image&gt; values in CSS. &lt;image&gt; values can be a single URI to an image, a list of URIs denoting a series of fallbacks, a reference to an element in the document, or gradients. Second, it defines properties used to control the interaction of replaced content and the CSS layout algorithms. These properties can affect the used image resolution for bitmaps, the replaced object's orientation, and whether and how to preserve the object's aspect ratio.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-css3-images-20110217</howpublished>
		<title type="sharef:primaryTitle">CSS Image Values and Replaced Content Module Level 3</title>
		<field type="bibtex:topic">css3[1]</field>
		<field type="bibtex:updates">css3imagevalues css3content</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2011/WD-css3-images-20110217</identifier>
	</reference>
	<reference name="css3val" src="bibtex:misc" src-info="bibtex:line-37236" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Håkon Wium</givenname>
				<surname>Lie</surname>
			</person>
			<person>
				<givenname>Chris</givenname>
				<surname>Lilley</surname>
			</person>
		</names>
		<date value="2006-09"/>
		<abstract>
			<richtext>
				<p>This CSS3 module describes the various values and units that CSS properties accept. Also, it describes how values are computed from "specified" (which is what the cascading process yields) through "computed" and "used" into "actual" values. The main purpose of this module is to define common values and units in one specification which can be referred to by other modules. As such, it does not make sense to claim conformance with this module alone.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-css3-values-20060919</howpublished>
		<title type="sharef:primaryTitle">CSS3 Values and Units</title>
		<field type="bibtex:topic">css3[1]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2006/WD-css3-values-20060919</identifier>
	</reference>
	<reference name="css3box" src="bibtex:misc" src-info="bibtex:line-37247" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Bert</givenname>
				<surname>Bos</surname>
			</person>
		</names>
		<date value="2008-12"/>
		<abstract>
			<richtext>
				<p>CSS describes the rendering of documents on various media. When documents (e.g., HTML) are laid out on visual media (e.g., screen or print) and the contents of some element are too large for a given area, CSS allows the designer to specify whether and how the overflow is displayed. One way, available on certain devices, is the "marquee" effect: the content is animated and moves automatically back and forth. This module defines the properties to control that effect.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Candidate Recommendation CR-css3-marquee-20081205</howpublished>
		<title type="sharef:primaryTitle">CSS Basic Box Model</title>
		<field type="bibtex:topic">css3[1]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2008/CR-css3-marquee-20081205</identifier>
	</reference>
	<reference name="css3webfonts" src="bibtex:misc" src-info="bibtex:line-37258" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Michel</givenname>
				<surname>Suignard</surname>
			</person>
			<person>
				<givenname>Chris</givenname>
				<surname>Lilley</surname>
			</person>
		</names>
		<date value="2002-08"/>
		<abstract>
			<richtext>
				<p>This document presents a set of properties allowing font description by a user agent. This specification is very close to the similar section in CSS 2. Only errata have been applied.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-css3-webfonts-20020802</howpublished>
		<title type="sharef:primaryTitle">CSS3 Module: Web Fonts</title>
		<field type="bibtex:topic">css3[1]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2002/WD-css3-webfonts-20020802</identifier>
	</reference>
	<reference name="css3fontprops" src="bibtex:misc" src-info="bibtex:line-37269" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Michel</givenname>
				<surname>Suignard</surname>
			</person>
			<person>
				<givenname>Chris</givenname>
				<surname>Lilley</surname>
			</person>
		</names>
		<date value="2002-08"/>
		<abstract>
			<richtext>
				<p>This document presents a set of properties allowing font specification by a user agent as well as additional font decoration properties like font effects, emphasis, smoothing, etc. The font specification is very close to the similar section in CSS 2. The font decoration properties are new to CSS3.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-css3-fonts-20020802</howpublished>
		<title type="sharef:primaryTitle">CSS3 Module: Fonts</title>
		<field type="bibtex:topic">css3[1]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2002/WD-css3-fonts-20020802</identifier>
	</reference>
	<reference name="css3fonts" src="bibtex:misc" src-info="bibtex:line-37280" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>John</givenname>
				<surname>Daggett</surname>
			</person>
		</names>
		<date value="2011-03"/>
		<abstract>
			<richtext>
				<p>This CSS3 module describes how font properties are specified and how font resources are loaded dynamically. The contents of this specification are a consolidation of content previously divided into CSS3 Fonts and CSS3 Web Fonts modules.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-css3-fonts-20110324</howpublished>
		<title type="sharef:primaryTitle">CSS3 Module: Fonts</title>
		<field type="bibtex:topic">css3[1]</field>
		<field type="bibtex:updates">css3fonts css3webfonts</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2011/WD-css3-fonts-20110324</identifier>
	</reference>
	<reference name="woff" src="bibtex:misc" src-info="bibtex:line-37292" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Jonathan</givenname>
				<surname>Kew</surname>
			</person>
			<person>
				<givenname>Tal</givenname>
				<surname>Leming</surname>
			</person>
			<person>
				<givenname>Erik</givenname>
				<surname link="van">Blokland</surname>
			</person>
		</names>
		<date value="2010-11"/>
		<abstract>
			<richtext>
				<p>This document specifies the WOFF font packaging format. This format was designed to provide lightweight, easy-to-implement compression of font data, suitable for use with CSS @font-face rules. Any properly licensed TrueType/OpenType/Open Font Format file can be packaged in WOFF format for Web use. User agents decode the WOFF file to restore the font data such that it will display identically to the input font. The WOFF format also allows additional metadata to be attached to the file; this can be used by font designers or vendors to include licensing or other information, beyond that present in the original font. Such metadata does not affect the rendering of the font in any way, but may be displayed to the user on request. The WOFF format is not intended to replace other formats such as TrueType/OpenType/Open Font Format or SVG fonts, but provides an alternative solution for use cases where these formats may be less optimal, or where licensing considerations make their use less acceptable.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-WOFF-20101116</howpublished>
		<title type="sharef:primaryTitle">WOFF File Format 1.0</title>
		<field type="bibtex:topic">woff[1] off[0.9] truetype[0.9] opentype[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2010/WD-WOFF-20101116</identifier>
	</reference>
	<reference name="css3lists" src="bibtex:misc" src-info="bibtex:line-37303" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Ian</givenname>
				<surname>Hickson</surname>
			</person>
			<person>
				<givenname>Tantek</givenname>
				<surname>Çelik</surname>
			</person>
		</names>
		<date value="2002-11"/>
		<abstract>
			<richtext>
				<p>This CSS level 3 module describes how lists are styled.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-css3-lists-20021107</howpublished>
		<title type="sharef:primaryTitle">CSS3 Module: Lists</title>
		<field type="bibtex:topic">css3[1]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2002/WD-css3-lists-20021107</identifier>
	</reference>
	<reference name="css3border" src="bibtex:misc" src-info="bibtex:line-37314" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Tapas</givenname>
				<surname>Roy</surname>
			</person>
		</names>
		<date value="2002-11"/>
		<abstract>
			<richtext>
				<p>CSS (Cascading Style Sheets) is a language for describing the rendering of structured documents (such as HTML and XML) on screen, on paper, in speech, etc. This draft describes the functionality that is proposed for CSS level 3 to describe borders, such as border styles, border colors and border images. It includes and extends the functionality of CSS level 2, which builds on CSS Level 1.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-css3-border-20021107</howpublished>
		<title type="sharef:primaryTitle">CSS3 Module: Border</title>
		<field type="bibtex:topic">css3[1]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2002/WD-css3-border-20021107</identifier>
	</reference>
	<reference name="css3namespace" src="bibtex:misc" src-info="bibtex:line-37325" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Elika J.</givenname>
				<surname>Etemad</surname>
			</person>
			<person>
				<givenname>Anne</givenname>
				<surname link="van">Kesteren</surname>
			</person>
		</names>
		<date value="2008-05"/>
		<abstract>
			<richtext>
				<p>This CSS Namespaces module defines the syntax for using namespaces in CSS. It defines the @namespace rule for declaring the default namespace and binding namespaces to namespace prefixes, and it also defines a syntax that other specifications can adopt for using those prefixes in namespace-qualified names.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Candidate Recommendation CR-css3-namespace-20080523</howpublished>
		<title type="sharef:primaryTitle">CSS Namespaces Module</title>
		<field type="bibtex:topic">css3[1]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2008/CR-css3-namespace-20080523</identifier>
	</reference>
	<reference name="css3transitions" src="bibtex:misc" src-info="bibtex:line-37336" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Dean</givenname>
				<surname>Jackson</surname>
			</person>
			<person>
				<givenname>David</givenname>
				<surname>Hyatt</surname>
			</person>
			<person>
				<givenname>Chris</givenname>
				<surname>Marrin</surname>
			</person>
		</names>
		<date value="2009-12"/>
		<abstract>
			<richtext>
				<p>CSS Transitions allows property changes in CSS values to occur smoothly over a specified duration.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-css3-transitions-20091201</howpublished>
		<title type="sharef:primaryTitle">CSS Transitions Module Level 3</title>
		<field type="bibtex:topic">css3[1]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2009/WD-css3-transitions-20091201</identifier>
	</reference>
	<reference name="css3animations" src="bibtex:misc" src-info="bibtex:line-37347" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Dean</givenname>
				<surname>Jackson</surname>
			</person>
			<person>
				<givenname>David</givenname>
				<surname>Hyatt</surname>
			</person>
			<person>
				<givenname>Chris</givenname>
				<surname>Marrin</surname>
			</person>
		</names>
		<date value="2009-03"/>
		<abstract>
			<richtext>
				<p>CSS Animations allow an author to modify CSS property values over time.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-css3-animations-20090320</howpublished>
		<title type="sharef:primaryTitle">CSS Animations Module Level 3</title>
		<field type="bibtex:topic">css3[1]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2009/WD-css3-animations-20090320</identifier>
	</reference>
	<reference name="css32dtransforms" src="bibtex:misc" src-info="bibtex:line-37358" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Dean</givenname>
				<surname>Jackson</surname>
			</person>
			<person>
				<givenname>David</givenname>
				<surname>Hyatt</surname>
			</person>
			<person>
				<givenname>Chris</givenname>
				<surname>Marrin</surname>
			</person>
		</names>
		<date value="2009-12"/>
		<abstract>
			<richtext>
				<p>CSS 2D Transforms allows elements rendered by CSS to be transformed in two-dimensional space.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-css3-2d-transforms-20091201</howpublished>
		<title type="sharef:primaryTitle">CSS 2D Transforms Module Level 3</title>
		<field type="bibtex:topic">css3[1]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2009/WD-css3-2d-transforms-20091201</identifier>
	</reference>
	<reference name="css33dtransforms" src="bibtex:misc" src-info="bibtex:line-37369" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Dean</givenname>
				<surname>Jackson</surname>
			</person>
			<person>
				<givenname>David</givenname>
				<surname>Hyatt</surname>
			</person>
			<person>
				<givenname>Chris</givenname>
				<surname>Marrin</surname>
			</person>
		</names>
		<date value="2009-03"/>
		<abstract>
			<richtext>
				<p>CSS 3D Transforms extends CSS Transforms to allow elements rendered by CSS to be transformed in three-dimensional space.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-css3-3d-transforms-20090320</howpublished>
		<title type="sharef:primaryTitle">CSS 3D Transforms Module Level 3</title>
		<field type="bibtex:topic">css3[1]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2009/WD-css3-3d-transforms-20090320</identifier>
	</reference>
	<reference name="cpcreq" src="bibtex:misc" src-info="bibtex:line-37380" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Roger</givenname>
				<surname>Gimson</surname>
			</person>
			<person>
				<givenname>Lalitha</givenname>
				<surname>Suryanarayana</surname>
			</person>
			<person>
				<givenname>Markus</givenname>
				<surname>Lauff</surname>
			</person>
		</names>
		<date value="2003-05"/>
		<howpublished>World Wide Web Consortium, Working Draft WD-cpc-req-20030510</howpublished>
		<title type="sharef:primaryTitle">Core Presentation Characteristics: Requirements and Use Cases</title>
		<identifier type="sharef:uri">http://www.w3.org/TR/2003/WD-cpc-req-20030510</identifier>
	</reference>
	<reference name="xsdversioningusecases" src="bibtex:misc" src-info="bibtex:line-37389" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Hoylen</givenname>
				<surname>Sue</surname>
			</person>
		</names>
		<date value="2006-01"/>
		<abstract>
			<richtext>
				<p>This document describes use cases where XML Schemas are being versioned. These are situations when there are more than one XML Schema, and those schemas are related to each other in some way. The use cases describe the desired behaviour from XML Schema processors when they encounter the different versions of schemas and the instances defined by them. This document has been produced by the W3C XML Schema Working Group, to serve as input to the Working Group's work on the versioning of XML Schemas. It is used to define what types of versioning situations that XML Schema should addressing. The use cases illustrate the types of versioning problems that should be solved by versioning mechanisms that might be added to XML Schema. XML Schema might not be able to solve all the use cases, but it is hoped that it can solve a majority of them.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, XML Schema Working Group</howpublished>
		<title type="sharef:primaryTitle">XML Schema Versioning Use Cases</title>
		<field type="bibtex:topic">xsd[0.8]</field>
		<identifier type="sharef:uri" resourceType="text/html">http://www.w3.org/XML/2005/xsd-versioning-use-cases/2006-01-31.html</identifier>
	</reference>
	<reference name="hashinuri" src="bibtex:misc" src-info="bibtex:line-37400" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>T. V.</givenname>
				<surname>Raman</surname>
			</person>
		</names>
		<date value="2009-04"/>
		<abstract>
			<richtext>
				<p>Designers of URIs have traditionally used ? to encode server-side parameters. At its inception, the Web also introduced fragment identifiers (preceded by #) as a means of addressing specific locations in a document. As highly interactive applications get built using Web parts (HTML, CSS and JavaScript component resources that are themselves Web addressable, there is an increasing need for encoding interaction state as part of the URI. The Web is beginning to discover and codify design patterns based on fragment identifiers for many of these use cases. This draft finding is being prepared in response to TAG issue #60. This document explores the issues that arise in this context, and attempts to define best practices that help create URIs for intermediate pages in a Web application so that the back button does the right thing, and enable clients to address into specific points in a stream of content, e.g., video. The goal of this finding is to initially collect the various usage scenarios that are leading to innovative uses of client-side URI parameters, along with the solutions that have been developed by the Web community. When this exercise is complete, this finding will conclude by ensuring that these design patterns are mutually compatible. If some of these usage patterns are identified as being in conflict, we will recommend best practices that help side-step such conflicts. We encourage the wider Web community to point us at emerging usage scenarios and design patterns so that we maximize our chances of arriving at a final finding that helps move forward the architecture of the Web in a self-consistent manner.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-hash-in-uri-20090415</howpublished>
		<title type="sharef:primaryTitle">Usage Patterns For Client-Side URI Parameters</title>
		<field type="bibtex:topic">uri[0.8]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2009/WD-hash-in-uri-20090415</identifier>
	</reference>
	<reference name="selfdescribingdocuments" src="bibtex:misc" src-info="bibtex:line-37411" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Noah</givenname>
				<surname>Mendelsohn</surname>
			</person>
		</names>
		<date value="2009-02"/>
		<abstract>
			<richtext>
				<p>The Web is designed to support flexible exploration of information by human users and by automated agents. For such exploration to be productive, information published by many different sources and for a variety of purposes must be comprehensible to a wide range of Web client software, and to users of that software. HTTP and other Web technologies can be used to deploy resource representations that are self-describing: information about the encodings used for each representation is provided explicitly within the representation. Starting with a URI, there is a standard algorithm that a user agent can apply to retrieve and interpret such representations. Furthermore, representations can be what we refer to as grounded in the Web, by ensuring that specifications required to interpret them are determined unambiguously based on the URI, and that explicit references connect the pertinent specifications to each other. Web-grounding ensures that the specifications needed to interpret information on the Web can be identified unambiguously. When such self-describing, Web-grounded resources are linked together, the Web as a whole can support reliable, ad hoc discovery of information. This finding describes how document formats, markup conventions, attribute values, and other data formats can be designed to facilitate the deployment of self-describing, Web-grounded Web content.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, TAG Finding 07 February 2009</howpublished>
		<title type="sharef:primaryTitle">The Self-Describing Web</title>
		<field type="bibtex:topic">atom[0.8] xml[0.8] rdfa[0.8] rdf[0.8] uri[0.8] http[0.8]</field>
		<identifier type="sharef:uri">http://www.w3.org/2001/tag/doc/selfDescribingDocuments-2009-02-07</identifier>
	</reference>
	<reference name="xmlversioning" src="bibtex:misc" src-info="bibtex:line-37422" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>David</givenname>
				<surname>Orchard</surname>
			</person>
		</names>
		<date value="2007-03"/>
		<abstract>
			<richtext>
				<p>This document provides terminology for discussing language versioning, a number of questions that language designers must answer, and a variety of version identification strategies. A separate document contains schema language specific discussion.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Draft TAG Finding</howpublished>
		<title type="sharef:primaryTitle">Extending and Versioning Languages Part 1</title>
		<field type="bibtex:topic">xml[0.8]</field>
		<identifier type="sharef:uri" resourceType="text/html">http://www.w3.org/2001/tag/doc/versioning-20070326.html</identifier>
	</reference>
	<reference name="mediafragsreqs" src="bibtex:misc" src-info="bibtex:line-37433" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Raphaël</givenname>
				<surname>Troncy</surname>
			</person>
			<person>
				<givenname>Erik</givenname>
				<surname>Mannens</surname>
			</person>
		</names>
		<date value="2009-12"/>
		<abstract>
			<richtext>
				<p>This document describes use cases and requirements for the development of the Media Fragments 1.0 specification. It includes a technology survey for addressing fragments of multimedia document.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-media-frags-reqs-20091217</howpublished>
		<title type="sharef:primaryTitle">Use cases and requirements for Media Fragments</title>
		<field type="bibtex:topic">uri[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2009/WD-media-frags-reqs-20091217</identifier>
	</reference>
	<reference name="mediafrags" src="bibtex:misc" src-info="bibtex:line-37444" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Raphaël</givenname>
				<surname>Troncy</surname>
			</person>
			<person>
				<givenname>Erik</givenname>
				<surname>Mannens</surname>
			</person>
			<person>
				<givenname>Silvia</givenname>
				<surname>Pfeiffer</surname>
			</person>
			<person>
				<givenname>Davy</givenname>
				<surname>Van Deursen</surname>
			</person>
		</names>
		<date value="2011-03"/>
		<abstract>
			<richtext>
				<p>This document describes the Media Fragments 1.0 specification. It specifies the syntax for constructing media fragment URIs and explains how to handle them when used over the HTTP protocol. The syntax is based on the specification of particular name-value pairs that can be used in URI fragment and URI query requests to restrict a media resource to a certain fragment.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-media-frags-20110317</howpublished>
		<title type="sharef:primaryTitle">Media Fragments URI 1.0</title>
		<field type="bibtex:topic">uri[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2011/WD-media-frags-20110317</identifier>
	</reference>
	<reference name="mediaont10" src="bibtex:misc" src-info="bibtex:line-37455" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>WonSuk</givenname>
				<surname>Lee</surname>
			</person>
			<person>
				<givenname>Werner</givenname>
				<surname>Bailer</surname>
			</person>
			<person>
				<givenname>Tobias</givenname>
				<surname>Bürger</surname>
			</person>
			<person>
				<givenname>Véronique</givenname>
				<surname>Malaisé</surname>
			</person>
			<person>
				<givenname>Thierry</givenname>
				<surname>Michel</surname>
			</person>
			<person>
				<givenname>Felix</givenname>
				<surname>Sasaki</surname>
			</person>
			<person>
				<givenname>Joakim</givenname>
				<surname>Söderberg</surname>
			</person>
			<person>
				<givenname>Florian</givenname>
				<surname>Stegmaier</surname>
			</person>
			<person>
				<givenname>John</givenname>
				<surname>Strassner</surname>
			</person>
		</names>
		<date value="2011-03"/>
		<abstract>
			<richtext>
				<p>This document defines the Ontology for Media Resources 1.0. The term "Ontology" is used in its broadest possible definition: a core vocabulary. The intent of this vocabulary is to bridge the different descriptions of media resources, and provide a core set of descriptive properties. This document defines a core set of metadata properties for media resources, along with their mappings to elements from a set of existing metadata formats. Besides that, the document presents a Semantic Web compatible implementation of the abstract ontology using RDF/OWL. The document is mostly targeted towards media resources available on the Web, as opposed to media resources that are only accessible in local archives or museums.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-mediaont-10-20110308</howpublished>
		<title type="sharef:primaryTitle">Ontology for Media Resources 1.0</title>
		<identifier type="sharef:uri">http://www.w3.org/TR/2011/WD-mediaont-10-20110308</identifier>
	</reference>
	<reference name="mediaontapi10" src="bibtex:misc" src-info="bibtex:line-37465" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>WonSuk</givenname>
				<surname>Lee</surname>
			</person>
			<person>
				<givenname>Florian</givenname>
				<surname>Stegmaier</surname>
			</person>
			<person>
				<givenname>Chris</givenname>
				<surname>Poppe</surname>
			</person>
		</names>
		<date value="2010-06"/>
		<abstract>
			<richtext>
				<p>This specification defines a client-side API to access metadata information related to media resources on the Web. The overall purpose of the API is to provide developers with a convenient access to metadata information stored in different metadata formats. The API is described using the interface definition language Web IDL. Thereby, the Media Ontology Core Properties will be used as a pivot vocabulary in the API.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-mediaont-api-1.0-20100608</howpublished>
		<title type="sharef:primaryTitle">API for Media Resource 1.0</title>
		<identifier type="sharef:uri">http://www.w3.org/TR/2010/WD-mediaont-api-1.0-20100608</identifier>
	</reference>
	<reference name="xmlschemaguide2versioning" src="bibtex:misc" src-info="bibtex:line-37475" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>David</givenname>
				<surname>Orchard</surname>
			</person>
		</names>
		<date value="2007-07"/>
		<abstract>
			<richtext>
				<p>This document is a guide to versioning XML languages using new XML Schema 1.1 mechanisms. It shows many of the new Schema 1.1 mechanisms, provides context above the schema 1.1 WD, and solicits reader input.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-xmlschema-guide2versioning-20070720</howpublished>
		<title type="sharef:primaryTitle">Guide to Versioning XML Languages using new XML Schema 1.1 features</title>
		<field type="bibtex:topic">xml[0.7] xsd[0.9]</field>
		<field type="bibtex:updates">xmlversioning</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2007/WD-xmlschema-guide2versioning-20070720</identifier>
	</reference>
	<reference name="nsdocuments" src="bibtex:misc" src-info="bibtex:line-37487" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Henry S.</givenname>
				<surname>Thompson</surname>
			</person>
			<person>
				<givenname>Norman</givenname>
				<surname>Walsh</surname>
			</person>
		</names>
		<date value="2007-06"/>
		<abstract>
			<richtext>
				<p>This Finding addresses the question of how ancillary information (schemas, stylesheets, documentation, etc.) can be associated with a namespace.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, TAG Finding</howpublished>
		<title type="sharef:primaryTitle">Associating Resources with Namespaces</title>
		<field type="bibtex:topic">xmlns[0.9] rddl[0.8] grddl[0.8]</field>
		<identifier type="sharef:uri">http://www.w3.org/2001/tag/doc/nsDocuments-2008-06-25</identifier>
	</reference>
	<reference name="whentouseget" src="bibtex:misc" src-info="bibtex:line-37498" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Ian</givenname>
				<surname>Jacobs</surname>
			</person>
		</names>
		<date value="2004-03"/>
		<abstract>
			<richtext>
				<p>An important principle of Web architecture is that all important resources be identifiable by URI. The finding discusses the relationship between the URI addressability of a resource and the choice between HTTP GET and POST methods with HTTP URIs. HTTP GET promotes URI addressability so, designers should adopt it for safe operations such as simple queries. POST is appropriate for other types of applications where a user request has the potential to change the state of the resource (or of related resources). The finding explains how to choose between HTTP GET and POST for an application taking into account architectural, security, and practical considerations. This finding does not discuss URI schemes other than "http" or protocols other than HTTP/1.1.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, TAG Finding</howpublished>
		<title type="sharef:primaryTitle">URIs, Addressability, and the use of HTTP GET and POST</title>
		<field type="bibtex:topic">http[0.9] uri[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/2001/tag/doc/whenToUseGet-20040321</identifier>
	</reference>
	<reference name="leastpower" src="bibtex:misc" src-info="bibtex:line-37509" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Tim</givenname>
				<surname>Berners-Lee</surname>
			</person>
			<person>
				<givenname>Noah</givenname>
				<surname>Mendelsohn</surname>
			</person>
		</names>
		<date value="2006-02"/>
		<abstract>
			<richtext>
				<p>When designing computer systems, one is often faced with a choice between using a more or less powerful language for publishing information, for expressing constraints, or for solving some problem. This finding explores tradeoffs relating the choice of language to reusability of information. The "Rule of Least Power" suggests choosing the least powerful language suitable for a given purpose.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, TAG Finding</howpublished>
		<title type="sharef:primaryTitle">The Rule of Least Power</title>
		<identifier type="sharef:uri">http://www.w3.org/2001/tag/doc/leastPower-2006-02-23</identifier>
	</reference>
	<reference name="deeplinking" src="bibtex:misc" src-info="bibtex:line-37519" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Tim</givenname>
				<surname>Bray</surname>
			</person>
		</names>
		<date value="2003-02"/>
		<abstract>
			<richtext>
				<p>The community of Web users has been engaged in discussion and litigation concerning the practice of "deep linking." This document is designed to provide input to this discussion based on the architecture of the underlying technology.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, TAG Finding</howpublished>
		<title type="sharef:primaryTitle">"Deep Linking" in the World Wide Web</title>
		<identifier type="sharef:uri">http://www.w3.org/2001/tag/doc/deeplinking-20030217</identifier>
	</reference>
	<reference name="alternativesdiscovery" src="bibtex:misc" src-info="bibtex:line-37529" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>T. V.</givenname>
				<surname>Raman</surname>
			</person>
		</names>
		<date value="2006-11"/>
		<abstract>
			<richtext>
				<p>Content creators wishing to publish multiple versions of a given resource on the Web face a number of questions with respect to how such URIs are created, published and discovered. Questions include given a resource http://example.com/ubiquity/ that can be delivered in a multiplicity of representations, how should one publish the relevant URIs to enable automatic discovery of these representations (AKA specific resources); and how does one ensure that the alternative relationship amongst these various representations is available in a machine readable form, and consequently discoverable; and here, multiple representations might include representations appropriate for different delivery contexts; alternative formats of the resource distinguished by Content-type; different versions of the resource e.g., either by language or date; and representations in different languages. This document explores the issues that arise in this context, and attempts to define best practices that help preserve the One Web while enabling content publishing to a multiplicity of delivery contexts; enable the creation of RESTful URIs that remain representation agnostic while delivering the correct end-user experience; enable automatic discovery of the available representations; and enable web crawlers discover the relationship between a given generic resource and the specific resources that correspond to its various alternatives. This will help search engines build better Web indices and avoid the need to index all available alternatives of a given resource.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, TAG Finding</howpublished>
		<title type="sharef:primaryTitle">On Linking Alternative Representations To Enable Discovery And Publishing</title>
		<identifier type="sharef:uri" resourceType="text/html">http://www.w3.org/2001/tag/doc/alternatives-discovery-20061101.html</identifier>
	</reference>
	<reference name="urnsandregistries" src="bibtex:misc" src-info="bibtex:line-37539" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Henry S.</givenname>
				<surname>Thompson</surname>
			</person>
			<person>
				<givenname>David</givenname>
				<surname>Orchard</surname>
			</person>
		</names>
		<date value="2006-08"/>
		<abstract>
			<richtext>
				<p>This finding addresses the questions "When should URNs or URIs with novel URI schemes be used to name information resources for the Web?" and "Should registries be provided for such identifiers?". The answers given are "Rarely if ever" and "Probably not". Common arguments in favor of such novel naming schemas are examined, and their properties compared with those of the existing http: URI scheme. Three case studies are then presented, illustrating how the http: URI scheme can be used to achieve many of the stated requirements for new URI schemes.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Draft TAG Finding</howpublished>
		<title type="sharef:primaryTitle">URNs, Namespaces and Registries</title>
		<field type="bibtex:topic">urn[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/2001/tag/doc/URNsAndRegistries-50-2006-08-17</identifier>
	</reference>
	<reference name="schemeProtocols" src="bibtex:misc" src-info="bibtex:line-37550" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Noah</givenname>
				<surname>Mendelsohn</surname>
			</person>
		</names>
		<date value="2005-11"/>
		<abstract>
			<richtext>
				<p>This document discusses the deployment of protocols and URI schemes on the World Wide Web. Implications for correct configuration of user agents, servers and proxy gateways are discussed. Guidelines are also provided for deciding whether a new protocol or scheme is merited, and for maximizing interoperability of new protocols with those that are already deployed.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Draft TAG Finding</howpublished>
		<title type="sharef:primaryTitle">URI Schemes and Web Protocols</title>
		<field type="bibtex:topic">uri[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/2001/tag/doc/schemeProtocols-2005-11-21</identifier>
	</reference>
	<reference name="metaDataInURI" src="bibtex:misc" src-info="bibtex:line-37561" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Noah</givenname>
				<surname>Mendelsohn</surname>
			</person>
			<person>
				<givenname>Stuart</givenname>
				<surname>Williams</surname>
			</person>
		</names>
		<date value="2007-01"/>
		<abstract>
			<richtext>
				<p>This finding addresses several questions regarding Uniform Resource Identifiers (URIs). Specifically, what information about a resource can or should be embedded in its URI? What metadata can be reliably determined from a URI, and in what circumstances is it appropriate to rely on the correctness of such information? In what circumstances is it appropriate to use information from a URI as a hint as to the nature of a resource or its representations? Simple examples are used to explain the tradeoffs involved in employing such metadata in URIs.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, TAG Finding</howpublished>
		<title type="sharef:primaryTitle">The use of Metadata in URIs</title>
		<field type="bibtex:topic">uri[0.9]</field>
		<identifier type="sharef:uri" resourceType="text/html">http://www.w3.org/2001/tag/doc/metaDataInURI-31-20070102.html</identifier>
	</reference>
	<reference name="html32" src="bibtex:misc" src-info="bibtex:line-37572" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Dave</givenname>
				<surname>Raggett</surname>
			</person>
		</names>
		<date value="1997-01"/>
		<abstract>
			<richtext>
				<p>This document has been reviewed by W3C members and other interested parties and has been endorsed by the Director as a W3C Recommendation. It is a stable document and may be used as reference material or cited as a normative reference from another document. W3C's role in making the Recommendation is to draw attention to the specification and to promote its widespread deployment. This enhances the functionality and interoperability of the Web.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Recommendation REC-html32</howpublished>
		<title type="sharef:primaryTitle">HTML 3.2 Reference Specification</title>
		<field type="bibtex:topic">html[1]</field>
		<field type="bibtex:updates">rfc1866</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/REC-html32</identifier>
	</reference>
	<reference name="html40" src="bibtex:misc" src-info="bibtex:line-37584" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Dave</givenname>
				<surname>Raggett</surname>
			</person>
			<person>
				<givenname>Arnaud</givenname>
				<surname>Le Hors</surname>
			</person>
			<person>
				<givenname>Ian</givenname>
				<surname>Jacobs</surname>
			</person>
		</names>
		<date value="1998-04"/>
		<abstract>
			<richtext>
				<p>This specification defines the HyperText Markup Language (HTML), version 4.0, the publishing language of the World Wide Web. In addition to the text, multimedia, and hyperlink features of the previous versions of HTML, HTML 4.0 supports more multimedia options, scripting languages, style sheets, better printing facilities, and documents that are more accessible to users with disabilities. HTML 4.0 also takes great strides towards the internationalization of documents, with the goal of making the Web truly World Wide. HTML 4.0 is an SGML application conforming to International Standard ISO 8879 — Standard Generalized Markup Language.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Recommendation REC-html40-19980424</howpublished>
		<title type="sharef:primaryTitle">HTML 4.0 Specification</title>
		<field type="bibtex:topic">html[1]</field>
		<field type="bibtex:updates">html32</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/1998/REC-html40-19980424</identifier>
	</reference>
	<reference name="html401" src="bibtex:misc" src-info="bibtex:line-37596" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Dave</givenname>
				<surname>Raggett</surname>
			</person>
			<person>
				<givenname>Arnaud</givenname>
				<surname>Le Hors</surname>
			</person>
			<person>
				<givenname>Ian</givenname>
				<surname>Jacobs</surname>
			</person>
		</names>
		<date value="1999-12"/>
		<abstract>
			<richtext>
				<p>This specification defines the HyperText Markup Language (HTML), the publishing language of the World Wide Web. This specification defines HTML 4.01, which is a subversion of HTML 4. In addition to the text, multimedia, and hyperlink features of the previous versions of HTML (HTML 3.2 and HTML 2.0), HTML 4 supports more multimedia options, scripting languages, style sheets, better printing facilities, and documents that are more accessible to users with disabilities. HTML 4 also takes great strides towards the internationalization of documents, with the goal of making the Web truly World Wide. HTML 4 is an SGML application conforming to International Standard ISO 8879 — Standard Generalized Markup Language.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Recommendation REC-html401-19991224</howpublished>
		<title type="sharef:primaryTitle">HTML 4.01 Specification</title>
		<field type="bibtex:topic">html[1]</field>
		<field type="bibtex:updates">html40</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/1999/REC-html401-19991224</identifier>
	</reference>
	<reference name="htmldesignprinciples" src="bibtex:misc" src-info="bibtex:line-37608" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Anne</givenname>
				<surname link="van">Kesteren</surname>
			</person>
			<person>
				<givenname>Maciej</givenname>
				<surname>Stachowiak</surname>
			</person>
		</names>
		<date value="2007-11"/>
		<abstract>
			<richtext>
				<p>HTML5 defines the fifth major revision of the core language of the World Wide Web, HTML. This document describes the set of guiding principles used by the HTML Working Group for the development of HTML5. The principles offer guidance for the design of HTML in the areas of compatibility, utility and interoperability.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-html-design-principles-20071126</howpublished>
		<title type="sharef:primaryTitle">HTML Design Principles</title>
		<field type="bibtex:topic">html[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2007/WD-html-design-principles-20071126</identifier>
	</reference>
	<reference name="html5" src="bibtex:misc" src-info="bibtex:line-37619" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Ian</givenname>
				<surname>Hickson</surname>
			</person>
		</names>
		<date value="2011-04"/>
		<abstract>
			<richtext>
				<p>This specification defines the 5th major revision of the core language of the World Wide Web: the Hypertext Markup Language (HTML). In this version, new features are introduced to help Web application authors, new elements are introduced based on research into prevailing authoring practices, and special attention has been given to defining clear conformance criteria for user agents in an effort to improve interoperability.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-html5-20110405</howpublished>
		<title type="sharef:primaryTitle">HTML5 — A Vocabulary and Associated APIs for HTML and XHTML</title>
		<field type="bibtex:topic">html[1]</field>
		<field type="bibtex:updates">html401</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2011/WD-html5-20110405</identifier>
	</reference>
	<reference name="htmlpolyglot" src="bibtex:misc" src-info="bibtex:line-37631" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Eliot</givenname>
				<surname>Graff</surname>
			</person>
		</names>
		<date value="2011-04"/>
		<abstract>
			<richtext>
				<p>A document that uses polyglot markup is document that is a stream of bytes that parses into identical document trees (with the exception of the xmlns attribute on the root element) when processed as HTML and when processed as XML. Polyglot markup that meets a well defined set of constraints is interpreted as compatible, regardless of whether they are processed as HTML or as XHTML, per the HTML5 specification. Polyglot markup uses a specific DOCTYPE, namespace declarations, and a specific case — normally lower case but occasionally camel case — for element and attribute names. Polyglot markup uses lower case for certain attribute values. Further constraints include those on empty elements, named entity references, and the use of scripts and style.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-html-polyglot-20110405</howpublished>
		<title type="sharef:primaryTitle">Polyglot Markup: HTML-Compatible XHTML Documents</title>
		<field type="bibtex:topic">html[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2011/WD-html-polyglot-20110405</identifier>
	</reference>
	<reference name="html5language" src="bibtex:misc" src-info="bibtex:line-37642" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Michael K.</givenname>
				<surname>Smith</surname>
			</person>
		</names>
		<date value="2011-04"/>
		<abstract>
			<richtext>
				<p>This non-normative reference describes the HTML markup language and provides details to help producers of HTML content create documents that conform to the language. It is intended to complement the normative conformance criteria defined in the HTML5: A vocabulary and associated APIs for HTML and XHTML  specification, as well as information in related deliverables published by the HTML Working Group and from other sources. By design, this reference does not describe related APIs in detail, nor attempt to explain how implementations that are consumers of HTML content are meant to process documents (those areas are covered by the HTML5 specification  itself), nor attempt to also be a tutorial or "how to" authoring guide.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-html-markup-20110405</howpublished>
		<title type="sharef:primaryTitle">HTML: The Markup Language Reference</title>
		<field type="bibtex:topic">html[1]</field>
		<field type="bibtex:updates">html401</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2011/WD-html-markup-20110405</identifier>
	</reference>
	<reference name="html5pubnotes" src="bibtex:misc" src-info="bibtex:line-37654" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Michael K.</givenname>
				<surname>Smith</surname>
			</person>
		</names>
		<date value="2008-06"/>
		<abstract>
			<richtext>
				<p>This document provides supplemental information on the 10 June 2008 working draft of the HTML5 specification. It primarily documents changes that have been made to the HTML5 draft specification since the time of its 22 January 2008 publication as a First Public Working Draft.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Note NOTE-html5-pubnotes-20080610</howpublished>
		<title type="sharef:primaryTitle">HTML5 Publication Notes</title>
		<field type="bibtex:topic">html[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2008/NOTE-html5-pubnotes-20080610</identifier>
	</reference>
	<reference name="html5diff" src="bibtex:misc" src-info="bibtex:line-37665" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Anne</givenname>
				<surname link="van">Kesteren</surname>
			</person>
		</names>
		<date value="2011-04"/>
		<abstract>
			<richtext>
				<p>HTML5 defines the fifth major revision of the core language of the World Wide Web, HTML. "HTML5 differences from HTML 4" describes the differences between HTML 4 and HTML5 and provides some of the rationale for the changes. This document may not provide accurate information as the HTML5 specification is still actively in development. When in doubt, always check the HTML5 specification itself.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-html5-diff-20110405</howpublished>
		<title type="sharef:primaryTitle">HTML5 Differences from HTML 4</title>
		<field type="bibtex:topic">html[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2011/WD-html5-diff-20110405</identifier>
	</reference>
	<reference name="eventsource" src="bibtex:misc" src-info="bibtex:line-37676" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Ian</givenname>
				<surname>Hickson</surname>
			</person>
		</names>
		<date value="2011-03"/>
		<abstract>
			<richtext>
				<p>This specification defines an API for opening an HTTP connection for receiving push notifications from a server in the form of DOM events. The API is designed such that it can be extended to work with other push notification schemes such as Push SMS.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-eventsource-20110310</howpublished>
		<title type="sharef:primaryTitle">Server-Sent Events</title>
		<field type="bibtex:topic">html[0.9] http[0.8] dom[0.8]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2011/WD-eventsource-20110310</identifier>
	</reference>
	<reference name="webnotifications" src="bibtex:misc" src-info="bibtex:line-37687" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>John</givenname>
				<surname>Gregg</surname>
			</person>
		</names>
		<date value="2011-03"/>
		<abstract>
			<richtext>
				<p>This document defines an API for displaying simple notifications to the user.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-notifications-20110301</howpublished>
		<title type="sharef:primaryTitle">Web Notifications</title>
		<field type="bibtex:topic">html[0.9] dom[0.8]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2011/WD-notifications-20110301</identifier>
	</reference>
	<reference name="htmlalttechniques" src="bibtex:misc" src-info="bibtex:line-37698" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Steve</givenname>
				<surname>Faulkner</surname>
			</person>
		</names>
		<date value="2011-04"/>
		<abstract>
			<richtext>
				<p>This document contains author conformance requirements for use of the alt attribute in HTML5 and best practice guidance for authors of HTML documents on providing text alternatives for images.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-html-alt-techniques-20110405</howpublished>
		<title type="sharef:primaryTitle">HTML5: Techniques for Providing Useful Text Alternatives</title>
		<field type="bibtex:topic">html[0.8]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2011/WD-html-alt-techniques-20110405</identifier>
	</reference>
	<reference name="websockets" src="bibtex:misc" src-info="bibtex:line-37709" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Ian</givenname>
				<surname>Hickson</surname>
			</person>
		</names>
		<date value="2009-12"/>
		<abstract>
			<richtext>
				<p>This specification defines an API that enables Web pages to use the Web Sockets protocol for two-way communication with a remote host.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-websockets-20091222</howpublished>
		<title type="sharef:primaryTitle">The Web Sockets API</title>
		<field type="bibtex:topic">dom[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2009/WD-websockets-20091222</identifier>
	</reference>
	<reference name="webstorage" src="bibtex:misc" src-info="bibtex:line-37720" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Ian</givenname>
				<surname>Hickson</surname>
			</person>
		</names>
		<date value="2011-02"/>
		<abstract>
			<richtext>
				<p>This specification defines an API for persistent data storage of key-value pair data in Web clients.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-webstorage-20110208</howpublished>
		<title type="sharef:primaryTitle">Web Storage</title>
		<field type="bibtex:topic">dom[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2011/WD-webstorage-20110208</identifier>
	</reference>
	<reference name="webdatabase" src="bibtex:misc" src-info="bibtex:line-37731" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Ian</givenname>
				<surname>Hickson</surname>
			</person>
		</names>
		<date value="2010-11"/>
		<abstract>
			<richtext>
				<p>This specification defines an API for storing data in databases that can be queried using a variant of SQL.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Note NOTE-webdatabase-20101118</howpublished>
		<title type="sharef:primaryTitle">Web SQL Database</title>
		<field type="bibtex:topic">dom[0.9] sql[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2010/NOTE-webdatabase-20101118</identifier>
	</reference>
	<reference name="2dcontext" src="bibtex:misc" src-info="bibtex:line-37742" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Ian</givenname>
				<surname>Hickson</surname>
			</person>
		</names>
		<date value="2011-04"/>
		<abstract>
			<richtext>
				<p>This specification defines the 2D Context for the HTML canvas element.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-2dcontext-20110405</howpublished>
		<title type="sharef:primaryTitle">HTML Canvas 2D Context</title>
		<field type="bibtex:topic">dom[0.9] html[1]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2011/WD-2dcontext-20110405</identifier>
	</reference>
	<reference name="webworkers" src="bibtex:misc" src-info="bibtex:line-37753" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Ian</givenname>
				<surname>Hickson</surname>
			</person>
		</names>
		<date value="2011-03"/>
		<abstract>
			<richtext>
				<p>This specification defines an API that allows Web application authors to spawn background workers running scripts in parallel to their main page. This allows for thread-like operation with message-passing as the coordination mechanism.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-workers-20110310</howpublished>
		<title type="sharef:primaryTitle">Web Workers</title>
		<field type="bibtex:topic">dom[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2011/WD-workers-20110310</identifier>
	</reference>
	<reference name="fileapi" src="bibtex:misc" src-info="bibtex:line-37764" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Arun</givenname>
				<surname>Ranganathan</surname>
			</person>
			<person>
				<givenname>Jonas</givenname>
				<surname>Sicking</surname>
			</person>
		</names>
		<date value="2010-10"/>
		<abstract>
			<richtext>
				<p>This specification provides an API  for representing file objects in web applications, as well as programmatically selecting them and accessing their data. This includes: A FileList sequence, which represents an array of individually selected files from the underlying system. The user interface for selection can be invoked via &lt;input type="file"&gt;, i.e. when the input element is in the File Upload state; A Blob interface, which represents raw binary data, and allows access to ranges of bytes within the Blob object; A File interface, which includes readonly informational attributes about a file such as its name and the date of the last modification (on disk) of the file; A FileReader interface, which provides methods to read a File or a Blob, and an event model to obtain the results of these reads; A FileError interface and a FileException exception which define error conditions used by this specification; A URI scheme for use with binary data such as files, so that they can be referenced within web applications. Additionally, this specification defines objects to be used within threaded web applications for the synchronous reading of files. The section on Requirements and Use Cases covers the motivation behind this specification. This API is designed to be used in conjunction with other APIs and elements on the web platform, notably: XMLHttpRequest (e.g. with an overloaded send() method for File or Blob objects), postMessage, DataTransfer (part of the drag and drop API defined in HTML5) and Web Workers. Additionally, it should be possible to programmatically obtain a list of files from the input element when it is in the File Upload state. These kinds of behaviors are defined in the appropriate affiliated specifications.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-FileAPI-20101026</howpublished>
		<title type="sharef:primaryTitle">File API</title>
		<field type="bibtex:topic">dom[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2010/WD-FileAPI-20101026</identifier>
	</reference>
	<reference name="filewriterapi" src="bibtex:misc" src-info="bibtex:line-37775" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Eric</givenname>
				<surname>Uhrhane</surname>
			</person>
		</names>
		<date value="2010-10"/>
		<abstract>
			<richtext>
				<p>This specification defines an API for writing to files from web applications. This API is designed to be used in conjunction with, and depends on definitions in, other APIs and elements on the web platform. Most relevant among these are File API and Web Workers. This API includes: A BlobBuilder interface, which enables one to build a Blob from a String; A FileSaver interface, which provides methods to write a Blob to a file, and an event model to monitor the progress of those writes; A FileWriter interface, which expands on FileSaver to add a richer set of output options; A FileWriterSync interface, which provides methods to write and modify files synchronously in a Web Worker.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-file-writer-api-20101026</howpublished>
		<title type="sharef:primaryTitle">File API: Writer</title>
		<field type="bibtex:topic">dom[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2010/WD-file-writer-api-20101026</identifier>
	</reference>
	<reference name="filesystemapi" src="bibtex:misc" src-info="bibtex:line-37786" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Eric</givenname>
				<surname>Uhrhane</surname>
			</person>
		</names>
		<date value="2010-10"/>
		<abstract>
			<richtext>
				<p>This specification defines an API to navigate file system hierarchies, and defines a means by which a user agent may expose sandboxed sections of a user's local filesystem to web applications. It builds on File API Writer, which in turn built on File API, each adding a different kind of functionality.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-file-system-api-20101026</howpublished>
		<title type="sharef:primaryTitle">File API: Directories and System</title>
		<field type="bibtex:topic">dom[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2010/WD-file-system-api-20101026</identifier>
	</reference>
	<reference name="offlinewebapps" src="bibtex:misc" src-info="bibtex:line-37797" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Anne</givenname>
				<surname link="van">Kesteren</surname>
			</person>
			<person>
				<givenname>Ian</givenname>
				<surname>Hickson</surname>
			</person>
		</names>
		<date value="2008-05"/>
		<abstract>
			<richtext>
				<p>HTML5 contains several features that address the challenge of building Web applications that work while offline. This document highlights these features (SQL, offline application caching APIs as well as online/offline events, status, and the localStorage API) from HTML5 and provides brief tutorials on how these features might be used to create Web applications that work offline.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Note NOTE-offline-webapps-20080530</howpublished>
		<title type="sharef:primaryTitle">Offline Web Applications</title>
		<field type="bibtex:topic">html[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2008/NOTE-offline-webapps-20080530</identifier>
	</reference>
	<reference name="websimpledbapi" src="bibtex:misc" src-info="bibtex:line-37808" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Nikunj R.</givenname>
				<surname>Mehta</surname>
			</person>
		</names>
		<date value="2009-09"/>
		<abstract>
			<richtext>
				<p>This document defines APIs for storing and retrieving ordered key-value pairs in a transactional database.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-WebSimpleDB-20090929</howpublished>
		<title type="sharef:primaryTitle">WebSimpleDB API</title>
		<field type="bibtex:topic">dom[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2009/WD-WebSimpleDB-20090929</identifier>
	</reference>
	<reference name="indexeddb" src="bibtex:misc" src-info="bibtex:line-37819" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Nikunj R.</givenname>
				<surname>Mehta</surname>
			</person>
			<person>
				<givenname>Jonas</givenname>
				<surname>Sicking</surname>
			</person>
			<person>
				<givenname>Eliot</givenname>
				<surname>Graff</surname>
			</person>
			<person>
				<givenname>Andrei</givenname>
				<surname>Popescu</surname>
			</person>
		</names>
		<date value="2010-08"/>
		<abstract>
			<richtext>
				<p>This document defines APIs for a database of records holding simple values and hierarchical objects. Each record consists of a key and some value. Moreover, the database maintains indexes over records it stores. An application developer directly uses an API to locate records either by their key or by using an index. A query language can be layered on this API. An indexed database can be implemented using a persistent B-tree data structure.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-IndexedDB-20100819</howpublished>
		<title type="sharef:primaryTitle">Indexed Database API</title>
		<field type="bibtex:topic">dom[0.9]</field>
		<field type="bibtex:updates">websimpledbapi</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2010/WD-IndexedDB-20100819</identifier>
	</reference>
	<reference name="datacache" src="bibtex:misc" src-info="bibtex:line-37831" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Nikunj R.</givenname>
				<surname>Mehta</surname>
			</person>
		</names>
		<date value="2011-03"/>
		<abstract>
			<richtext>
				<p>This document defines APIs for off-line serving of requests to HTTP resources using static and dynamic responses. It extends the function of application caches defined in HTML5.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Note NOTE-DataCache-20110329</howpublished>
		<title type="sharef:primaryTitle">Programmable HTTP Caching and Serving</title>
		<field type="bibtex:topic">dom[0.9] http[0.8]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2011/NOTE-DataCache-20110329</identifier>
	</reference>
	<reference name="contactsapi" src="bibtex:misc" src-info="bibtex:line-37842" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Richard</givenname>
				<surname>Tibbett</surname>
			</person>
		</names>
		<date value="2010-12"/>
		<abstract>
			<richtext>
				<p>The Contacts API defines the high-level interfaces required to provide read access to a user's unified address book. Methods to manipulate a user's unified address book, to add and remove contact information, are being developed in an accompanying specification.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-contacts-api-20101209</howpublished>
		<title type="sharef:primaryTitle">The Contacts API</title>
		<field type="bibtex:topic">dom[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2010/WD-contacts-api-20101209</identifier>
	</reference>
	<reference name="xhtml10" src="bibtex:misc" src-info="bibtex:line-37853" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Steven</givenname>
				<surname>Pemberton</surname>
			</person>
		</names>
		<date value="2000-01"/>
		<abstract>
			<richtext>
				<p>This specification defines XHTML 1.0, a reformulation of HTML 4 as an XML 1.0 application, and three DTDs corresponding to the ones defined by HTML 4. The semantics of the elements and their attributes are defined in the W3C Recommendation for HTML 4. These semantics provide the foundation for future extensibility of XHTML. Compatibility with existing HTML user agents is possible by following a small set of guidelines.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Recommendation REC-xhtml1-20000126</howpublished>
		<title type="sharef:primaryTitle">XHTML 1.0: The Extensible HyperText Markup Language</title>
		<field type="bibtex:topic">xml[0.5] html[0.7] xhtml[1]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2000/REC-xhtml1-20000126</identifier>
	</reference>
	<reference name="xhtml10sec" src="bibtex:misc" src-info="bibtex:line-37864" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Steven</givenname>
				<surname>Pemberton</surname>
			</person>
		</names>
		<date value="2002-08"/>
		<abstract>
			<richtext>
				<p>This specification defines the Second Edition of XHTML 1.0, a reformulation of HTML 4 as an XML 1.0 application, and three DTDs corresponding to the ones defined by HTML 4. The semantics of the elements and their attributes are defined in the W3C Recommendation for HTML 4. These semantics provide the foundation for future extensibility of XHTML. Compatibility with existing HTML user agents is possible by following a small set of guidelines.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Recommendation REC-xhtml1-20020801</howpublished>
		<title type="sharef:primaryTitle">XHTML 1.0: The Extensible HyperText Markup Language (Second Edition)</title>
		<field type="bibtex:topic">xml[0.5] html[0.7] xhtml[1]</field>
		<field type="bibtex:updates">xhtml10</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2002/REC-xhtml1-20020801</identifier>
	</reference>
	<reference name="xhtml10third" src="bibtex:misc" src-info="bibtex:line-37876" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Steven</givenname>
				<surname>Pemberton</surname>
			</person>
		</names>
		<date value="2009-05"/>
		<abstract>
			<richtext>
				<p>This specification defines the Third Edition of XHTML 1.0, a reformulation of HTML 4 as an XML 1.0 application, and three DTDs corresponding to the ones defined by HTML 4. The semantics of the elements and their attributes are defined in the W3C Recommendation for HTML 4. These semantics provide the foundation for future extensibility of XHTML. Compatibility with existing HTML user agents is possible by following a small set of guidelines.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Proposed Edited Recommendation PER-xhtml1-20090507</howpublished>
		<title type="sharef:primaryTitle">XHTML 1.0: The Extensible HyperText Markup Language (Third Edition)</title>
		<field type="bibtex:topic">xml[0.5] html[0.7] xhtml[1]</field>
		<field type="bibtex:updates">xhtml10sec</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2009/PER-xhtml1-20090507</identifier>
	</reference>
	<reference name="xhtmlbasic" src="bibtex:misc" src-info="bibtex:line-37888" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Mark A.</givenname>
				<surname>Baker</surname>
			</person>
			<person>
				<givenname>Masayasu</givenname>
				<surname>Ishikawa</surname>
			</person>
			<person>
				<givenname>Shinichi</givenname>
				<surname>Matsui</surname>
			</person>
			<person>
				<givenname>Peter</givenname>
				<surname>Stark</surname>
			</person>
			<person>
				<givenname>Ted</givenname>
				<surname>Wugofski</surname>
			</person>
			<person>
				<givenname>Toshihiko</givenname>
				<surname>Yamakami</surname>
			</person>
		</names>
		<date value="2000-12"/>
		<abstract>
			<richtext>
				<p>The XHTML Basic document type includes the minimal set of modules required to be an XHTML host language document type, and in addition it includes images, forms, basic tables, and object support. It is designed for Web clients that do not support the full set of XHTML features; for example, Web clients such as mobile phones, PDAs, pagers, and settop boxes. The document type is rich enough for content authoring. XHTML Basic is designed as a common base that may be extended. For example, an event module that is more generic than the traditional HTML 4 event system could be added or it could be extended by additional modules from XHTML Modularization such as the Scripting Module. The goal of XHTML Basic is to serve as a common language supported by various kinds of user agents. The document type definition is implemented using XHTML modules as defined in "Modularization of XHTML".</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Recommendation REC-xhtml-basic-20001219</howpublished>
		<title type="sharef:primaryTitle">XHTML Basic</title>
		<field type="bibtex:topic">xml[0.5] html[0.7] xhtml[1]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2000/REC-xhtml-basic-20001219</identifier>
	</reference>
	<reference name="xhtmlbasic11" src="bibtex:misc" src-info="bibtex:line-37899" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Shane</givenname>
				<surname>McCarron</surname>
			</person>
			<person>
				<givenname>Masayasu</givenname>
				<surname>Ishikawa</surname>
			</person>
		</names>
		<date value="2008-07"/>
		<abstract>
			<richtext>
				<p>The XHTML Basic document type includes the minimal set of modules required to be an XHTML host language document type, and in addition it includes images, forms, basic tables, and object support. It is designed for Web clients that do not support the full set of XHTML features; for example, Web clients such as mobile phones, PDAs, pagers, and settop boxes. The document type is rich enough for content authoring. XHTML Basic is designed as a common base that may be extended. The goal of XHTML Basic is to serve as a common language supported by various kinds of user agents. This revision, 1.1, supercedes version 1.0 as defined in http://www.w3.org/TR/2000/REC-xhtml-basic-20001219. In this revision, several new features have been incorporated into the language in order to better serve the small-device community that is this language's major user: 1. XHTML Forms; 2. Intrinsic Events; 3. The value attribute for the li element; 4. The target attribute; 5. The style element; 6. The style attribute; 7. XHTML Presentation module; 8. The inputmode attribute. The document type definition is implemented using XHTML modules as defined in "XHTML Modularization".</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Recommendation REC-xhtml-basic-20080729</howpublished>
		<title type="sharef:primaryTitle">XHTML Basic 1.1</title>
		<field type="bibtex:topic">xml[0.5] html[0.7] xhtml[1]</field>
		<field type="bibtex:updates">xhtmlbasic</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2008/REC-xhtml-basic-20080729</identifier>
	</reference>
	<reference name="xhtmlbasic11sec" src="bibtex:misc" src-info="bibtex:line-37911" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Shane</givenname>
				<surname>McCarron</surname>
			</person>
			<person>
				<givenname>Masayasu</givenname>
				<surname>Ishikawa</surname>
			</person>
		</names>
		<date value="2010-11"/>
		<abstract>
			<richtext>
				<p>The XHTML Basic document type includes the minimal set of modules required to be an XHTML host language document type, and in addition it includes images, forms, basic tables, and object support. It is designed for Web clients that do not support the full set of XHTML features; for example, Web clients such as mobile phones, PDAs, pagers, and settop boxes. The document type is rich enough for content authoring. XHTML Basic is designed as a common base that may be extended. The goal of XHTML Basic is to serve as a common language supported by various kinds of user agents. This revision, 1.1 Second Edition, supercedes version 1.1. In this revision, an XML Schema implementation and the lang attribute have been added. In the update from version 1.0 to version 1.1, several new features were incorporated into the language in order to better serve the small-device community that is this language's major user: 1. XHTML Forms; 2. Intrinsic Events; 3. The value attribute for the li element; 4. The target attribute; 5. The style element; 6. The style attribute; 7. XHTML Presentation module; 8. The inputmode attribute. The document type definition is implemented using XHTML modules as defined in "XHTML Modularization".</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Recommendation REC-xhtml-basic-20101123</howpublished>
		<title type="sharef:primaryTitle">XHTML Basic 1.1 — Second Edition</title>
		<field type="bibtex:topic">xml[0.5] html[0.7] xhtml[1]</field>
		<field type="bibtex:updates">xhtmlbasic11</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2010/REC-xhtml-basic-20101123</identifier>
	</reference>
	<reference name="xhtml11" src="bibtex:misc" src-info="bibtex:line-37923" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Murray</givenname>
				<surname>Altheim</surname>
			</person>
			<person>
				<givenname>Shane</givenname>
				<surname>McCarron</surname>
			</person>
		</names>
		<date value="2001-05"/>
		<abstract>
			<richtext>
				<p>This Recommendation defines a new XHTML document type that is based upon the module framework and modules defined in Modularization of XHTML. The purpose of this document type is to serve as the basis for future extended XHTML 'family' document types, and to provide a consistent, forward-looking document type cleanly separated from the deprecated, legacy functionality of HTML 4 that was brought forward into the XHTML 1.0 document types. This document type is essentially a reformulation of XHTML 1.0 Strict using XHTML Modules. This means that many facilities available in other XHTML Family document types (e.g., XHTML Frames) are not available in this document type. These other facilities are available through modules defined in Modularization of XHTML, and document authors are free to define document types based upon XHTML 1.1 that use these facilities.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Recommendation REC-xhtml11-20010531</howpublished>
		<title type="sharef:primaryTitle">XHTML 1.1 — Module-based XHTML</title>
		<field type="bibtex:topic">xml[0.5] html[0.7] xhtml[1]</field>
		<field type="bibtex:updates">xhtml10</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2001/REC-xhtml11-20010531</identifier>
	</reference>
	<reference name="xhtml11sec" src="bibtex:misc" src-info="bibtex:line-37935" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Shane</givenname>
				<surname>McCarron</surname>
			</person>
		</names>
		<date value="2010-11"/>
		<abstract>
			<richtext>
				<p>This document defines an XHTML document type that is based upon the module framework and modules defined in XHTML Modularization. The purpose of this document type is to serve as the basis for future extended XHTML 'family' document types, and to provide a consistent, forward-looking document type cleanly separated from the deprecated, legacy functionality of HTML 4 that was brought forward into the XHTML 1.0 document types. This document type is most similar to XHTML 1.0 Strict, built using XHTML Modules. This means that many facilities available in other XHTML Family document types (e.g., XHTML Frames) are not available in this document type. These other facilities are available through modules defined in XHTML Modularization, and document authors are free to define document types based upon XHTML 1.1 that use these facilities.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Recommendation REC-xhtml11-20101123</howpublished>
		<title type="sharef:primaryTitle">XHTML 1.1 — Module-based XHTML — Second Edition</title>
		<field type="bibtex:topic">xml[0.5] html[0.7] xhtml[1]</field>
		<field type="bibtex:updates">xhtml11</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2010/REC-xhtml11-20101123</identifier>
	</reference>
	<reference name="xhtmlbuild" src="bibtex:misc" src-info="bibtex:line-37947" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Murray</givenname>
				<surname>Altheim</surname>
			</person>
			<person>
				<givenname>Shane</givenname>
				<surname>McCarron</surname>
			</person>
		</names>
		<date value="2000-01"/>
		<abstract>
			<richtext>
				<p>This working draft defines the mechanism for defining markup language modules that are compatible with the modularization framework used by XHTML. This includes a definition of the way in which an abstract module is specified, the way in which this abstraction is mapped into an XML DTD, and the way in which the resulting DTD module can be combined with other XHTML DTD modules to create new markup languages. In the future, it is expected that instructions will also be provided for mapping the abstract specifications into an XML Schema. Note that the materials in this document were formerly part of the Modularization of XHTML document, but have been separated out for editorial purposes.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-xhtml-building-20000105</howpublished>
		<title type="sharef:primaryTitle">Building XHTML Modules</title>
		<field type="bibtex:topic">xml[0.5] html[0.7] xhtml[1]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2000/WD-xhtml-building-20000105</identifier>
	</reference>
	<reference name="xhtmlmod" src="bibtex:misc" src-info="bibtex:line-37958" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Murray</givenname>
				<surname>Altheim</surname>
			</person>
			<person>
				<givenname>Frank</givenname>
				<surname>Boumphrey</surname>
			</person>
			<person>
				<givenname>Sam</givenname>
				<surname>Dooley</surname>
			</person>
			<person>
				<givenname>Shane</givenname>
				<surname>McCarron</surname>
			</person>
			<person>
				<givenname>Sebastian</givenname>
				<surname>Schnitzenbaumer</surname>
			</person>
			<person>
				<givenname>Ted</givenname>
				<surname>Wugofski</surname>
			</person>
		</names>
		<date value="2001-04"/>
		<abstract>
			<richtext>
				<p>This Recommendation specifies an abstract modularization of XHTML and an implementation of the abstraction using XML Document Type Definitions (DTDs). This modularization provides a means for subsetting and extending XHTML, a feature needed for extending XHTML's reach onto emerging platforms.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Recommendation REC-xhtml-modularization-20010410</howpublished>
		<title type="sharef:primaryTitle">Modularization of XHTML</title>
		<field type="bibtex:topic">xml[0.5] html[0.7] xhtml[1]</field>
		<field type="bibtex:updates">xhtmlbuild</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2001/REC-xhtml-modularization-20010410</identifier>
	</reference>
	<reference name="xhtmlmodsch" src="bibtex:misc" src-info="bibtex:line-37970" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Daniel</givenname>
				<surname>Austin</surname>
			</person>
			<person>
				<givenname>Subramanian</givenname>
				<surname>Peruvemba</surname>
			</person>
			<person>
				<givenname>Shane</givenname>
				<surname>McCarron</surname>
			</person>
			<person>
				<givenname>Masayasu</givenname>
				<surname>Ishikawa</surname>
			</person>
		</names>
		<date value="2003-10"/>
		<abstract>
			<richtext>
				<p>This document describes a methodology for modularization of XHTML using XML Schema. The document also provides a XML Schema implementation of the abstract modules defined in Modularization of XHTML.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-xhtml-m12n-schema-20031003</howpublished>
		<title type="sharef:primaryTitle">Modularization of XHTML in XML Schema</title>
		<field type="bibtex:topic">xhtml[0.9] xsd[0.7]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2003/WD-xhtml-m12n-schema-20031003</identifier>
	</reference>
	<reference name="xhtmlmodsec" src="bibtex:misc" src-info="bibtex:line-37981" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Daniel</givenname>
				<surname>Austin</surname>
			</person>
			<person>
				<givenname>Subramanian</givenname>
				<surname>Peruvemba</surname>
			</person>
			<person>
				<givenname>Shane</givenname>
				<surname>McCarron</surname>
			</person>
			<person>
				<givenname>Masayasu</givenname>
				<surname>Ishikawa</surname>
			</person>
			<person>
				<givenname>Mark</givenname>
				<surname>Birbeck</surname>
			</person>
		</names>
		<date value="2008-08"/>
		<abstract>
			<richtext>
				<p>This document is version 1.1 of XHTML Modularization, an abstract modularization of XHTML and implementations of the abstraction using XML Document Type Definitions (DTDs), and XML Schemas. This modularization provides a means for subsetting and extending XHTML, a feature needed for extending XHTML's reach onto emerging platforms. This specification is intended for use by language designers as they construct new XHTML Family Markup Languages. This specification does not define the semantics of elements and attributes, only how those elements and attributes are assembled into modules, and from those modules into markup languages. This second version of this specification includes several minor updates to provide clarifications and address errors found in the first version. It also provides an implementation using XML Schemas.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Recommendation REC-xhtml-modularization-20081008</howpublished>
		<title type="sharef:primaryTitle">XHTML Modularization 1.1</title>
		<field type="bibtex:topic">xml[0.5] html[0.7] xhtml[1]</field>
		<field type="bibtex:updates">xhtmlmod xhtmlmodsch</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2008/REC-xhtml-modularization-20081008</identifier>
	</reference>
	<reference name="xhtmlmod2nd" src="bibtex:misc" src-info="bibtex:line-37993" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Shane</givenname>
				<surname>McCarron</surname>
			</person>
		</names>
		<date value="2010-07"/>
		<abstract>
			<richtext>
				<p>This document is the second edition of version 1.1 of XHTML Modularization, an abstract modularization of XHTML and implementations of the abstraction using XML Document Type Definitions (DTDs) and XML Schemas. This modularization provides a means for subsetting and extending XHTML, a feature needed for extending XHTML's reach onto emerging platforms. This specification is intended for use by language designers as they construct new XHTML Family Markup Languages. This specification does not define the semantics of elements and attributes, only how those elements and attributes are assembled into modules, and from those modules into markup languages. This update includes several minor updates to provide clarifications and address errors found in version 1.1.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Recommendation REC-xhtml-modularization-20100729</howpublished>
		<title type="sharef:primaryTitle">XHTML Modularization 1.1 — Second Edition</title>
		<field type="bibtex:topic">xml[0.5] html[0.7] xhtml[1]</field>
		<field type="bibtex:updates">xhtmlmodsec</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2010/REC-xhtml-modularization-20100729</identifier>
	</reference>
	<reference name="xhtmlev" src="bibtex:misc" src-info="bibtex:line-38005" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Shane</givenname>
				<surname>McCarron</surname>
			</person>
			<person>
				<givenname>T. V.</givenname>
				<surname>Raman</surname>
			</person>
		</names>
		<date value="2001-06"/>
		<abstract>
			<richtext>
				<p>The XHTML Events module defined in this specification provides XHTML host languages the ability to uniformly integrate event listeners and associated event handlers with Document Object Model (DOM) Level 2 event interfaces. The result is to provide XHTML based languages an interoperable way of associating behaviors with document-level markup. In addition, this specification defines a subset of the XHTML Events module called basic events for use on simpler client devices. Finally, the XHTML Event Types Module defines the XHTML language event types.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-xhtml-events-20010608</howpublished>
		<title type="sharef:primaryTitle">XHTML Events — An updated events syntax for XHTML and friends</title>
		<field type="bibtex:topic">xhtml[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2001/WD-xhtml-events-20010608</identifier>
	</reference>
	<reference name="xhtmlrole" src="bibtex:misc" src-info="bibtex:line-38016" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Mark</givenname>
				<surname>Birbeck</surname>
			</person>
			<person>
				<givenname>Shane</givenname>
				<surname>McCarron</surname>
			</person>
			<person>
				<givenname>Steven</givenname>
				<surname>Pemberton</surname>
			</person>
			<person>
				<givenname>T. V.</givenname>
				<surname>Raman</surname>
			</person>
			<person>
				<givenname>Richard</givenname>
				<surname>Schwerdtfeger</surname>
			</person>
		</names>
		<date value="2010-12"/>
		<abstract>
			<richtext>
				<p>The XHTML Role Attribute defined in this specification allows the author to annotate XML Languages with machine-extractable semantic information about the purpose of an element. Use cases include accessibility, device adaptation, server-side processing, and complex data description. This attribute can be integrated into any markup language based upon XHTML Modularization.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Note NOTE-xhtml-role-20101216</howpublished>
		<title type="sharef:primaryTitle">XHTML Role Attribute Module</title>
		<field type="bibtex:topic">xhtml[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2010/NOTE-xhtml-role-20101216</identifier>
	</reference>
	<reference name="xhtmlaccess" src="bibtex:misc" src-info="bibtex:line-38027" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Mark</givenname>
				<surname>Birbeck</surname>
			</person>
			<person>
				<givenname>Shane</givenname>
				<surname>McCarron</surname>
			</person>
			<person>
				<givenname>Steven</givenname>
				<surname>Pemberton</surname>
			</person>
			<person>
				<givenname>T. V.</givenname>
				<surname>Raman</surname>
			</person>
			<person>
				<givenname>Richard</givenname>
				<surname>Schwerdtfeger</surname>
			</person>
		</names>
		<date value="2010-12"/>
		<abstract>
			<richtext>
				<p>The XHTML Access module defines an element that, when used in conjunction with other XHTML modules in XHTML Family Markup Languages, enables a more robust accessibility model than is presently possible.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Note NOTE-xhtml-access-20101216</howpublished>
		<title type="sharef:primaryTitle">XHTML Access Module</title>
		<field type="bibtex:topic">xhtml[0.8]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2010/NOTE-xhtml-access-20101216</identifier>
	</reference>
	<reference name="xhtmlmathmlsvg" src="bibtex:misc" src-info="bibtex:line-38038" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Masayasu</givenname>
				<surname>Ishikawa</surname>
			</person>
		</names>
		<date value="2002-08"/>
		<abstract>
			<richtext>
				<p>An XHTML+MathML+SVG profile is a profile that combines XHTML 1.1, MathML 2.0, and SVG 1.1 together. This profile enables mixing XHTML, MathML and SVG in the same document using XML namespaces mechanism, while allowing validation of such a mixed-namespace document. An XHTML 1.1 + MathML 2.0 + SVG 1.1 DTD driver is provided. An XHTML version of this document is conforming to this DTD.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-XHTMLplusMathMLplusSVG-20020809</howpublished>
		<title type="sharef:primaryTitle">An XHTML + MathML + SVG Profile</title>
		<field type="bibtex:topic">xhtml[0.8] mathml[0.8] svg[0.8]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2002/WD-XHTMLplusMathMLplusSVG-20020809</identifier>
	</reference>
	<reference name="xhtmlprint" src="bibtex:misc" src-info="bibtex:line-38049" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Melinda</givenname>
				<surname>Grant</surname>
			</person>
			<person>
				<givenname>Jim</givenname>
				<surname>Bigelow</surname>
			</person>
		</names>
		<date value="2006-09"/>
		<abstract>
			<richtext>
				<p>XHTML-Print is member of the family of XHTML languages defined by the Modularization of XHTML. It is designed to be appropriate for printing from mobile devices to low-cost printers that might not have a full-page buffer and that generally print from top-to-bottom and left-to-right with the paper in a portrait orientation. XHTML-Print is also targeted at printing in environments where it is not feasible or desirable to install a printer-specific driver and where some variability in the formatting of the output is acceptable.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Recommendation REC-xhtml-print-20060920</howpublished>
		<title type="sharef:primaryTitle">XHTML-Print</title>
		<field type="bibtex:topic">xhtml[0.8]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2006/REC-xhtml-print-20060920</identifier>
	</reference>
	<reference name="xhtmlprintsec" src="bibtex:misc" src-info="bibtex:line-38060" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Shane</givenname>
				<surname>McCarron</surname>
			</person>
		</names>
		<date value="2010-11"/>
		<abstract>
			<richtext>
				<p>XHTML-Print is a member of the family of XHTML languages defined by the Modularization of XHTML. It is designed to be appropriate for printing from mobile devices to low-cost printers that might not have a full-page buffer and that generally print from top-to-bottom and left-to-right with the paper in a portrait orientation. XHTML-Print is also targeted at printing in environments where it is not feasible or desirable to install a printer-specific driver and where some variability in the formatting of the output is acceptable.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Recommendation REC-xhtml-print-20101123</howpublished>
		<title type="sharef:primaryTitle">XHTML-Print — Second Edition</title>
		<field type="bibtex:topic">xhtml[0.8]</field>
		<field type="bibtex:updates">xhtmlprint</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2010/REC-xhtml-print-20101123</identifier>
	</reference>
	<reference name="xmlmediatypes" src="bibtex:misc" src-info="bibtex:line-38072" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Anish</givenname>
				<surname>Karmarkar</surname>
			</person>
			<person>
				<givenname>Ümit</givenname>
				<surname>Yalçınalp</surname>
			</person>
		</names>
		<date value="2005-05"/>
		<abstract>
			<richtext>
				<p>This document addresses the need to indicate the media type associated with binary element content in an XML document and the need to specify, in XML Schema, the expected media type(s) associated with binary element content. It is expected that the additional information about the media type will be used for optimizing the handling of binary data that is part of a Web services message.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Note NOTE-xml-media-types-20050504</howpublished>
		<title type="sharef:primaryTitle">Assigning Media Types to Binary Data in XML</title>
		<field type="bibtex:topic">xml[0.8] mime[0.8]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2005/NOTE-xml-media-types-20050504</identifier>
	</reference>
	<reference name="xhtmlmediatypes" src="bibtex:misc" src-info="bibtex:line-38083" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Masayasu</givenname>
				<surname>Ishikawa</surname>
			</person>
		</names>
		<date value="2002-08"/>
		<howpublished>World Wide Web Consortium, Note NOTE-xhtml-media-types-20020801</howpublished>
		<title type="sharef:primaryTitle">XHTML Media Types</title>
		<field type="bibtex:topic">xhtml[0.9] mime[0.8]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2002/NOTE-xhtml-media-types-20020801</identifier>
	</reference>
	<reference name="xhtmlmediatypes2nd" src="bibtex:misc" src-info="bibtex:line-38093" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Shane</givenname>
				<surname>McCarron</surname>
			</person>
		</names>
		<date value="2009-01"/>
		<abstract>
			<richtext>
				<p>Many people want to use XHTML to author their web pages, but are confused about the best ways to deliver those pages in such a way that they will be processed correctly by various user agents. This Note contains suggestions about how to format XHTML to ensure it is maximally portable, and how to deliver XHTML to various user agents — even those that do not yet support XHTML natively. This document is intended to be used by document authors who want to use XHTML today, but want to be confident that their XHTML content is going to work in the greatest number of environments. The suggestions in this document are relevant to all XHTML Family Recommendations at the time of its publication.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Note NOTE-xhtml-media-types-20090116</howpublished>
		<title type="sharef:primaryTitle">XHTML Media Types — Second Edition</title>
		<field type="bibtex:topic">xhtml[0.9] mime[0.8]</field>
		<field type="bibtex:updates">xhtmlmediatypes</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2009/NOTE-xhtml-media-types-20090116</identifier>
	</reference>
	<reference name="xhtml1xmlschema" src="bibtex:misc" src-info="bibtex:line-38105" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Masayasu</givenname>
				<surname>Ishikawa</surname>
			</person>
		</names>
		<date value="2002-09"/>
		<howpublished>World Wide Web Consortium, Note NOTE-xhtml1-schema-20020902</howpublished>
		<title type="sharef:primaryTitle">XHTML 1.0 in XML Schema</title>
		<field type="bibtex:topic">xhtml[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2002/NOTE-xhtml1-schema-20020902</identifier>
	</reference>
	<reference name="xhtml2" src="bibtex:misc" src-info="bibtex:line-38115" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Mark</givenname>
				<surname>Birbeck</surname>
			</person>
			<person>
				<givenname>Markus</givenname>
				<surname>Gylling</surname>
			</person>
			<person>
				<givenname>Shane</givenname>
				<surname>McCarron</surname>
			</person>
			<person>
				<givenname>Steven</givenname>
				<surname>Pemberton</surname>
			</person>
		</names>
		<date value="2010-12"/>
		<abstract>
			<richtext>
				<p>XHTML 2 is a general-purpose markup language designed to represent documents for a wide range of purposes across the World Wide Web. To this end it does not attempt to be all things to all people, supplying every possible markup idiom, but to supply a generally useful set of elements.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Note NOTE-xhtml2-20101216</howpublished>
		<title type="sharef:primaryTitle">XHTML 2.0</title>
		<field type="bibtex:topic">xml[0.5] html[0.7] xhtml[1]</field>
		<field type="bibtex:updates">xhtml11</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2010/NOTE-xhtml2-20101216</identifier>
	</reference>
	<reference name="xframes" src="bibtex:misc" src-info="bibtex:line-38127" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Steven</givenname>
				<surname>Pemberton</surname>
			</person>
			<person>
				<givenname>Masayasu</givenname>
				<surname>Ishikawa</surname>
			</person>
		</names>
		<date value="2010-12"/>
		<abstract>
			<richtext>
				<p>XFrames is an XML application for composing documents together, replacing HTML Frames. By being a separate application from XHTML, it allows content negotiation to determine if the user agent accepts frames; by encoding the 'population' of frames in the URI, it allows framesets to be bookmarked.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Note NOTE-xframes-20101216</howpublished>
		<title type="sharef:primaryTitle">XFrames</title>
		<identifier type="sharef:uri">http://www.w3.org/TR/2010/NOTE-xframes-20101216</identifier>
	</reference>
	<reference name="dviprinc" src="bibtex:misc" src-info="bibtex:line-38137" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Shlomit</givenname>
				<surname>Ritz</surname>
			</person>
			<person>
				<givenname>Stéphane H.</givenname>
				<surname>Maes</surname>
			</person>
			<person>
				<givenname>Lalitha</givenname>
				<surname>Suryanarayana</surname>
			</person>
		</names>
		<names type="sharef:editor">
			<person>
				<givenname>Roger</givenname>
				<surname>Gimson</surname>
			</person>
		</names>
		<date value="2003-09"/>
		<howpublished>World Wide Web Consortium, Note NOTE-di-princ-20030901</howpublished>
		<title type="sharef:primaryTitle">Device Independence Principles</title>
		<identifier type="sharef:uri">http://www.w3.org/TR/2003/NOTE-di-princ-20030901</identifier>
	</reference>
	<reference name="dial" src="bibtex:misc" src-info="bibtex:line-38147" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Kevin</givenname>
				<surname>Smith</surname>
			</person>
		</names>
		<date value="2007-07"/>
		<abstract>
			<richtext>
				<p>The purpose of the Device Independent Authoring Language (DIAL) is to provide a markup language for the filtering and presentation of Web page content available across different delivery contexts. This will facilitate an optimal user experience following adaptation of the DIAL instance document. Please refer to the DIAL Primer for an introduction to the profile and its purpose. DIAL is a language profile based on existing W3C XML vocabularies and CSS modules. These provide standard mechanisms for representing Web page structure, presentation and form interaction. The DIAL also makes use of the DISelect metadata vocabulary for overcoming the authoring challenges inherent in authoring for multiple delivery contexts. DIAL is part of the Authoring for Device Independence work category of the DIWG. This encompasses a number of work items associated with authoring Web sites and applications that support access from a wide range of devices with a variety of delivery contexts. These include work on Authoring Challenges, Authoring Techniques, and Scenarios and Extension Markup.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-dial-20070727</howpublished>
		<title type="sharef:primaryTitle">Device Independent Authoring Language (DIAL)</title>
		<field type="bibtex:topic">dial[1]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2007/WD-dial-20070727</identifier>
	</reference>
	<reference name="dialprimer" src="bibtex:misc" src-info="bibtex:line-38158" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Kevin</givenname>
				<surname>Smith</surname>
			</person>
		</names>
		<date value="2007-11"/>
		<abstract>
			<richtext>
				<p>This document provides an introduction to, and the benefits of, DIAL (the Device Independent Authoring Language). It summarizes the concept of device independence, the scenarios in which it could be used, and the considerations in order to achieve that goal. It then describes the role of DIAL in ensuring the delivery of content suitable for the user, device and inherent circumstances in which it was requested.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-dial-primer-20071101</howpublished>
		<title type="sharef:primaryTitle">DIAL Part 0: Primer</title>
		<field type="bibtex:topic">dial[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2007/WD-dial-primer-20071101</identifier>
	</reference>
	<reference name="diselect" src="bibtex:misc" src-info="bibtex:line-38169" type="bibtex:misc">
		<names type="sharef:editor">
			<person>
				<givenname>Rhys</givenname>
				<surname>Lewis</surname>
			</person>
			<person>
				<givenname>Roland</givenname>
				<surname>Merrick</surname>
			</person>
			<person>
				<givenname>Max</givenname>
				<surname>Froumentin</surname>
			</person>
		</names>
		<date value="2007-07"/>
		<abstract>
			<richtext>
				<p>This document specifies a syntax and processing model for general purpose content selection or filtering. Selection involves conditional processing of various parts of an XML information set according to the results of the evaluation of expressions. Using this mechanism some parts of the information set can be selected for further processing and others can be suppressed. The specification of the parts of the infoset affected and the expressions that govern processing is by means of XML-friendly syntax. This includes elements, attributes and XPath expressions. This document specifies how these components work together to provide general purpose selection.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Candidate Recommendation CR-cselection-20070725</howpublished>
		<title type="sharef:primaryTitle">Content Selection for Device Independence (DISelect) 1.0</title>
		<field type="bibtex:topic">diselect[1]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2007/CR-cselection-20070725</identifier>
	</reference>
	<reference name="cselectionprimer" src="bibtex:misc" src-info="bibtex:line-38180" type="bibtex:misc">
		<names type="sharef:editor">
			<person>
				<givenname>Rhys</givenname>
				<surname>Lewis</surname>
			</person>
			<person>
				<givenname>Roland</givenname>
				<surname>Merrick</surname>
			</person>
		</names>
		<date value="2007-01"/>
		<abstract>
			<richtext>
				<p>Content Selection for Device Independence (DISelect) is a specification that allows authors to choose between different versions of content for use in different circumstances. This Primer is designed to provide the reader with the basic knowledge required to make effective use of this markup. It positions DISelect in relation to other methods of content selection. It also describes the features of DISelect and illustrates how they can be used in a variety of scenarios using a number of examples.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-cselection-primer-20070109</howpublished>
		<title type="sharef:primaryTitle">Content Selection Primer 1.0</title>
		<field type="bibtex:topic">diselect[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2007/WD-cselection-primer-20070109</identifier>
	</reference>
	<reference name="cselectionxaf" src="bibtex:misc" src-info="bibtex:line-38191" type="bibtex:misc">
		<names type="sharef:editor">
			<person>
				<givenname>Rhys</givenname>
				<surname>Lewis</surname>
			</person>
			<person>
				<givenname>Roland</givenname>
				<surname>Merrick</surname>
			</person>
		</names>
		<date value="2007-07"/>
		<abstract>
			<richtext>
				<p>This document specifies a set of XPath functions that can be used to manipulate the Delivery Context associated with a request for an item of content. These functions have been designed to satisfy the requirements to adapt content based on the Delivery Context. While designed to work with Device Independent Content Selection (DISelect) it can be used in any XPath processor. There is a companion document which provides introductory information concerned with this specification.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Candidate Recommendation CR-cselection-xaf-20070725</howpublished>
		<title type="sharef:primaryTitle">Delivery Context: XPath Access Functions 1.0</title>
		<field type="bibtex:topic">diselect[0.9] xpath[0.7]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2007/CR-cselection-xaf-20070725</identifier>
	</reference>
	<reference name="didco" src="bibtex:misc" src-info="bibtex:line-38202" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Roger</givenname>
				<surname>Gimson</surname>
			</person>
			<person>
				<givenname>Rhys</givenname>
				<surname>Lewis</surname>
			</person>
			<person>
				<givenname>Sailesh</givenname>
				<surname>Sathish</surname>
			</person>
		</names>
		<date value="2006-03"/>
		<abstract>
			<richtext>
				<p>This document provides an overview of the role of delivery context in achieving a device independent Web. It describes the kind of information that may be included in the delivery context, and how it may be used. It surveys current techniques for conveying delivery context information, and identifies further developments that would enhance the ability to adapt content for different access mechanisms. This document is one of a series produced by the W3C Device Independence Working Group. Other documents in the series address the implementation of solutions to the requirements raised here. For example, there are documents in the series reviewing current techniques that can be used to address these requirements and exploring how future versions of existing W3C specifications can provide solutions. Details of the entire series of documents can be found on the W3C Device Independence Activity home page.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Group Note NOTE-di-dco-20060320</howpublished>
		<title type="sharef:primaryTitle">Delivery Context Overview for Device Independence</title>
		<identifier type="sharef:uri">http://www.w3.org/TR/2006/NOTE-di-dco-20060320</identifier>
	</reference>
	<reference name="dcontology" src="bibtex:misc" src-info="bibtex:line-38212" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>José Manuel Cantera</givenname>
				<surname>Fonseca</surname>
			</person>
			<person>
				<givenname>Rhys</givenname>
				<surname>Lewis</surname>
			</person>
		</names>
		<date value="2009-06"/>
		<abstract>
			<richtext>
				<p>The Delivery Context Ontology provides a formal model of the characteristics of the environment in which devices interact with the Web or other services. The Delivery Context includes the characteristics of the Device, the software used to access the service and the Network providing the connection among others. The Delivery Context is an important source of information that can be exploited to create context-aware applications, thus providing a compelling user experience. The ontology is formally specified in the Web Ontology Language (OWL). This document describes the ontology and gives details of each term that it contains. The normative definition of the ontology terms is generated automatically from the OWL file.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-dcontology-20090616</howpublished>
		<title type="sharef:primaryTitle">Delivery Context Ontology</title>
		<identifier type="sharef:uri">http://www.w3.org/TR/2009/WD-dcontology-20090616</identifier>
	</reference>
	<reference name="acdi" src="bibtex:misc" src-info="bibtex:line-38222" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Rhys</givenname>
				<surname>Lewis</surname>
			</person>
		</names>
		<date value="2003-09"/>
		<abstract>
			<richtext>
				<p>This document discusses the challenges that authors commonly face when building web content and applications that can be accessed by users via a wide variety of different devices with different capabilities. The document examines the effects on authors and the implications for authoring techniques that assist in the preparation of sites that can support a wide variety of devices. As a consequence, it also derives a set of requirements for such techniques. This document is one of a series produced by the Device Independence Working Group, part of the W3C Device Independence Activity. The DIWG activity statement can be seen at http://www.w3.org/2001/di/Activity. Other documents in the series address the implementation of solutions to the requirements raised here. For example, there are documents in the series reviewing current techniques that can be used to address these requirements and exploring how future versions of existing W3C specifications can provide solutions.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Note NOTE-acdi-20030901</howpublished>
		<title type="sharef:primaryTitle">Authoring Challenges for Device Independence</title>
		<identifier type="sharef:uri">http://www.w3.org/TR/2003/NOTE-acdi-20030901</identifier>
	</reference>
	<reference name="atdi" src="bibtex:misc" src-info="bibtex:line-38232" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Rotan</givenname>
				<surname>Hanrahan</surname>
			</person>
			<person>
				<givenname>Roland</givenname>
				<surname>Merrick</surname>
			</person>
			<person>
				<givenname>Candy</givenname>
				<surname>Wong</surname>
			</person>
			<person>
				<givenname>Michael</givenname>
				<surname>Wasmund</surname>
			</person>
			<person>
				<givenname>Rhys</givenname>
				<surname>Lewis</surname>
			</person>
			<person>
				<givenname>Tayeb</givenname>
				<surname>Lemlouma</surname>
			</person>
		</names>
		<names type="sharef:editor">
			<person>
				<givenname>Rotan</givenname>
				<surname>Hanrahan</surname>
			</person>
			<person>
				<givenname>Roland</givenname>
				<surname>Merrick</surname>
			</person>
		</names>
		<date value="2004-02"/>
		<abstract>
			<richtext>
				<p>The document provides a summary of several techniques and best practices that Web site authors and solution providers may employ when creating and delivering content to a diverse set of access mechanisms.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Note NOTE-di-atdi-20040218</howpublished>
		<title type="sharef:primaryTitle">Authoring Techniques for Device Independence</title>
		<identifier type="sharef:uri">http://www.w3.org/TR/2004/NOTE-di-atdi-20040218</identifier>
	</reference>
	<reference name="digloss" src="bibtex:misc" src-info="bibtex:line-38243" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Rhys</givenname>
				<surname>Lewis</surname>
			</person>
		</names>
		<date value="2005-01"/>
		<abstract>
			<richtext>
				<p>This document is a glossary of terms used in other documents produced by the Device Independence Working Group (DIWG). Details of the entire series of documents can be found on the W3C Device Independence Activity home page.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-di-gloss-20050118</howpublished>
		<title type="sharef:primaryTitle">Glossary of Terms for Device Independence</title>
		<identifier type="sharef:uri">http://www.w3.org/TR/2005/WD-di-gloss-20050118</identifier>
	</reference>
	<reference name="ditest" src="bibtex:misc" src-info="bibtex:line-38253" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Dominique</givenname>
				<surname>Hazaël-Massieux</surname>
			</person>
			<person>
				<givenname>Carmelo</givenname>
				<surname>Montanez</surname>
			</person>
		</names>
		<date value="2009-05"/>
		<abstract>
			<richtext>
				<p>As support for Web technologies grows, it is important that tests writers develop test suites that will work as well as possible across devices. This document offers guidance in the form of simple guidelines to follow to create device-independent tests.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Note NOTE-di-testing-20090512</howpublished>
		<title type="sharef:primaryTitle">Guidelines for writing device independent tests</title>
		<identifier type="sharef:uri">http://www.w3.org/TR/2009/NOTE-di-testing-20090512</identifier>
	</reference>
	<reference name="ruby" src="bibtex:misc" src-info="bibtex:line-38263" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Marcin</givenname>
				<surname>Sawicki</surname>
			</person>
			<person>
				<givenname>Michel</givenname>
				<surname>Suignard</surname>
			</person>
			<person>
				<givenname>Masayasu</givenname>
				<surname>Ishikawa</surname>
			</person>
			<person>
				<givenname>Martin J.</givenname>
				<surname>Dürst</surname>
			</person>
			<person>
				<givenname>Tex</givenname>
				<surname>Texin</surname>
			</person>
		</names>
		<date value="2001-05"/>
		<howpublished>World Wide Web Consortium, Recommendation REC-ruby-20010531</howpublished>
		<field type="bibtex:index">XHTML, ruby</field>
		<title type="sharef:primaryTitle">Ruby Annotation</title>
	</reference>
	<reference name="xpreq" src="bibtex:misc" src-info="bibtex:line-38272" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Vidur</givenname>
				<surname>Apparao</surname>
			</person>
			<person>
				<givenname>Alex</givenname>
				<surname>Ceponkus</surname>
			</person>
			<person>
				<givenname>Paul</givenname>
				<surname>Cotton</surname>
			</person>
			<person>
				<givenname>David</givenname>
				<surname>Ezell</surname>
			</person>
			<person>
				<givenname>David C.</givenname>
				<surname>Fallside</surname>
			</person>
			<person>
				<givenname>Martin</givenname>
				<surname>Gudgin</surname>
			</person>
			<person>
				<givenname>Oisin</givenname>
				<surname>Hurley</surname>
			</person>
			<person>
				<givenname>John</givenname>
				<surname>Ibbotson</surname>
			</person>
			<person>
				<givenname>R. Alexander</givenname>
				<surname>Milowski</surname>
			</person>
			<person>
				<givenname>Kevin</givenname>
				<surname>Mitchell</surname>
			</person>
			<person>
				<givenname>Jean-Jacques</givenname>
				<surname>Moreau</surname>
			</person>
			<person>
				<givenname>Eric</givenname>
				<surname>Newcomer</surname>
			</person>
			<person>
				<givenname>Henrik</givenname>
				<surname>Frystyk Nielsen</surname>
			</person>
			<person>
				<givenname>Bob</givenname>
				<surname>Lojek</surname>
			</person>
			<person>
				<givenname>Mark</givenname>
				<surname>Nottingham</surname>
			</person>
			<person>
				<givenname>Waqar</givenname>
				<surname>Sadiq</surname>
			</person>
			<person>
				<givenname>Stuart</givenname>
				<surname>Williams</surname>
			</person>
			<person>
				<givenname>Amr</givenname>
				<surname>Yassin</surname>
			</person>
		</names>
		<date value="2003-07"/>
		<abstract>
			<richtext>
				<p>This document describes the XML Protocol Working Group's requirements for the XML Protocol (XMLP) specification.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Note NOTE-xmlp-reqs-20030728</howpublished>
		<title type="sharef:primaryTitle">XML Protocol (XMLP) Requirements</title>
		<field type="bibtex:topic">xmlp[1]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2003/NOTE-xmlp-reqs-20030728</identifier>
	</reference>
	<reference name="xmlprocmodelreq" src="bibtex:misc" src-info="bibtex:line-38283" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Dmitry</givenname>
				<surname>Lenkov</surname>
			</person>
			<person>
				<givenname>Norman</givenname>
				<surname>Walsh</surname>
			</person>
		</names>
		<date value="2004-04"/>
		<abstract>
			<richtext>
				<p>This document contains requirements for the development of XML Processing Model and Language, which are intended to describe and specify the processing relationships between XML resources.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Note NOTE-proc-model-req-20040405</howpublished>
		<title type="sharef:primaryTitle">XML Processing Model Requirements</title>
		<field type="bibtex:topic">xml[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2004/NOTE-proc-model-req-20040405</identifier>
	</reference>
	<reference name="xmlpam" src="bibtex:misc" src-info="bibtex:line-38294" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Stuart</givenname>
				<surname>Williams</surname>
			</person>
			<person>
				<givenname>Mark</givenname>
				<surname>Jones</surname>
			</person>
		</names>
		<date value="2003-02"/>
		<abstract>
			<richtext>
				<p>This document describes an Abstract Model of XML Protocol. The challenge of crafting a protocol specification is to create a description of behaviour that is not tied to any particular approach to implementation. There is a need to abstract away from some of the messy implementation details of buffer management, data representation and specific APIs. However, in order to describe the behaviour of a protocol one has to establish a set of (useful) concepts that can be used in that description. An abstract model is one way to establish a consistent set of concepts. An abstract model is a tool for the description of complex behaviour — it is not a template for an implementation... although it should not stray so far away from reality that it is impossible to recognise how the required behaviours would be implemented.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-xmlp-am-20030220</howpublished>
		<title type="sharef:primaryTitle">XML Protocol Abstract Model</title>
		<field type="bibtex:topic">xmlp[1]</field>
		<field type="bibtex:updates">xpreq</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2003/WD-xmlp-am-20030220</identifier>
	</reference>
	<reference name="xmlpscen" src="bibtex:misc" src-info="bibtex:line-38306" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>John</givenname>
				<surname>Ibbotson</surname>
			</person>
		</names>
		<date value="2003-07"/>
		<abstract>
			<richtext>
				<p>This document describes the SOAP Usage Scenarios and how they may be implemented using the SOAP 1.2 specification.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Note NOTE-xmlp-scenarios-20030730</howpublished>
		<title type="sharef:primaryTitle">SOAP Version 1.2 Usage Scenarios</title>
		<field type="bibtex:topic">xmlp[0.9] soap[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2003/NOTE-xmlp-scenarios-20030730</identifier>
	</reference>
	<reference name="mobilebpscope" src="bibtex:misc" src-info="bibtex:line-38317" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Phil</givenname>
				<surname>Archer</surname>
			</person>
			<person>
				<givenname>Ed</givenname>
				<surname>Mitukiewicz</surname>
			</person>
		</names>
		<date value="2005-12"/>
		<abstract>
			<richtext>
				<p>Web access from mobile devices suffers from problems that make the Web unattractive for most mobile users. W3C's Mobile Web Initiative (MWI) proposes to address these issues through a concerted effort of key players in the mobile value chain, including authoring tool vendors, content providers, handset manufacturers, browser vendors and mobile operators. To help frame the development of "best practices" for the mobile Web this document — created by the members of the Mobile Web Initiative Best Practices Working Group (BPWG) as an elaboration of its charter — identifies the nature of problems to be solved, outlines the scope of work to be undertaken and specifies the assumptions regarding the target audience and the anticipated deliverables. The BPWG has recently published the first public working drafts of its initial Mobile Web Best Practices recommendations.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Note NOTE-mobile-bp-scope-20051220</howpublished>
		<title type="sharef:primaryTitle">Scope of Mobile Web Best Practices</title>
		<field type="bibtex:topic">mwbp[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2005/NOTE-mobile-bp-scope-20051220</identifier>
	</reference>
	<reference name="mobilebp" src="bibtex:misc" src-info="bibtex:line-38328" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Jo</givenname>
				<surname>Rabin</surname>
			</person>
			<person>
				<givenname>Charles</givenname>
				<surname>McCathieNevile</surname>
			</person>
		</names>
		<date value="2008-07"/>
		<abstract>
			<richtext>
				<p>This document specifies Best Practices for delivering Web content to mobile devices. The principal objective is to improve the user experience of the Web when accessed from such devices. The recommendations refer to delivered content and not to the processes by which it is created, nor to the devices or user agents to which it is delivered. It is primarily directed at creators, maintainers and operators of Web sites. Readers of this document are expected to be familiar with the creation of Web sites, and to have a general familiarity with the technologies involved, such as Web servers and HTTP. Readers are not expected to have a background in mobile-specific technologies.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Recommendation REC-mobile-bp-20080729</howpublished>
		<title type="sharef:primaryTitle">Mobile Web Best Practices 1.0 — Basic Guidelines</title>
		<field type="bibtex:topic">mwbp[1]</field>
		<field type="bibtex:updates">mobilebpscope</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2008/REC-mobile-bp-20080729</identifier>
	</reference>
	<reference name="mwbpguidelines" src="bibtex:misc" src-info="bibtex:line-38340" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Kai</givenname>
				<surname>Scheppe</surname>
			</person>
		</names>
		<date value="2009-10"/>
		<abstract>
			<richtext>
				<p>This document supplements W3C Mobile Web Best Practices 1.0 by providing additional evaluations of conformance to Best Practice statements and by providing additional interpretations of Best Practice statements.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Note NOTE-mwbp-guidelines-20091020</howpublished>
		<title type="sharef:primaryTitle">Extended Guidelines for Mobile Web Best Practices 1.0</title>
		<field type="bibtex:topic">mwbp[1]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2009/NOTE-mwbp-guidelines-20091020</identifier>
	</reference>
	<reference name="mwbpwcag" src="bibtex:misc" src-info="bibtex:line-38351" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Alan</givenname>
				<surname>Chuter</surname>
			</person>
			<person>
				<givenname>Yeliz</givenname>
				<surname>Yesilada</surname>
			</person>
		</names>
		<date value="2009-07"/>
		<abstract>
			<richtext>
				<p>This technical report describes the similarities and differences between the requirements in Web Content Accessibility Guidelines (WCAG) and Mobile Web Best Practices 1.0 (MWBP). Introductory information and links to related documents are in Web Content Accessibility and Mobile Web: Making a Web Site Accessible Both for People with Disabilities and for Mobile Devices.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Note NOTE-mwbp-wcag-20090709</howpublished>
		<title type="sharef:primaryTitle">Relationship between Mobile Web Best Practices (MWBP) and Web Content Accessibility Guidelines (WCAG)</title>
		<field type="bibtex:topic">wcag[0.9] mwbp[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2009/NOTE-mwbp-wcag-20090709</identifier>
	</reference>
	<reference name="uwapersonalizationroadmap" src="bibtex:misc" src-info="bibtex:line-38362" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Andy</givenname>
				<surname>Heath</surname>
			</person>
			<person>
				<givenname>Richard</givenname>
				<surname>Schwerdtfeger</surname>
			</person>
		</names>
		<date value="2009-04"/>
		<abstract>
			<richtext>
				<p>This document describes an activity of integrating personalization with device context for the delivery of content materials and interface components that are customized to meet both individual personal needs and preferences and delivery context. It brings together the work of separate standards and specifications organizations and working groups, notably W3C Ubiquitous Web Applications working group, IMS Global Learning Consortium Accessibility Special Interest group, ISO/IEC JTC1 SC36 Information Technology for Learning, Education and Training: Human Diversity and Access For All working group and associated working groups in SC36. The document should be viewed as a roadmap for the work to be undertaken and includes description of the basis for the work, the organizational context, the likely technologies and a partially complete description of how the technologies fit together.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft NOTE-UWA-personalization-roadmap-20090409</howpublished>
		<title type="sharef:primaryTitle">W3C Personalization Roadmap: Ubiquitous Web Integration of AccessForAll 1.0</title>
		<identifier type="sharef:uri">http://www.w3.org/TR/2009/NOTE-UWA-personalization-roadmap-20090409</identifier>
	</reference>
	<reference name="mwabp" src="bibtex:misc" src-info="bibtex:line-38372" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Adam</givenname>
				<surname>Connors</surname>
			</person>
			<person>
				<givenname>Bryan</givenname>
				<surname>Sullivan</surname>
			</person>
		</names>
		<date value="2010-12"/>
		<abstract>
			<richtext>
				<p>The goal of this document is to aid the development of rich and dynamic mobile Web applications. It collects the most relevant engineering practices, promoting those that enable a better user experience and warning against those that are considered harmful.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Recommendation REC-mwabp-20101214</howpublished>
		<title type="sharef:primaryTitle">Mobile Web Application Best Practices</title>
		<field type="bibtex:topic">mwbp[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2010/REC-mwabp-20101214</identifier>
	</reference>
	<reference name="mobileok10" src="bibtex:misc" src-info="bibtex:line-38383" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Jo</givenname>
				<surname>Rabin</surname>
			</person>
			<person>
				<givenname>Phil</givenname>
				<surname>Archer</surname>
			</person>
		</names>
		<date value="2009-08"/>
		<abstract>
			<richtext>
				<p>The mobileOK scheme allows content providers to promote their content as being suitable for use on very basic mobile devices. This document provides an overview of the scheme and references the documentation that composes it.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Note NOTE-mobileOK-20090825</howpublished>
		<title type="sharef:primaryTitle">W3C mobileOK Scheme 1.0</title>
		<field type="bibtex:topic">mobileok[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2009/NOTE-mobileOK-20090825</identifier>
	</reference>
	<reference name="mobileok10basic10tests" src="bibtex:misc" src-info="bibtex:line-38394" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Sean</givenname>
				<surname>Owen</surname>
			</person>
			<person>
				<givenname>Jo</givenname>
				<surname>Rabin</surname>
			</person>
		</names>
		<date value="2008-12"/>
		<abstract>
			<richtext>
				<p>This document defines the tests that provide the basis for making a claim of W3C mobileOK Basic conformance and are based on W3C Mobile Web Best Practices. The details of how to claim mobileOK conformance will be described separately. Providers of content which passes the tests have taken some steps to provide a functional user experience for users of basic mobile devices whose capabilities at least match those of the Default Delivery Context (DDC). mobileOK Basic primarily assesses basic usability, efficiency and interoperability. It does not address the important goal of assessing whether users of more advanced devices enjoy a richer user experience than is possible using the DDC.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Recommendation REC-mobileOK-basic10-tests-20081208</howpublished>
		<title type="sharef:primaryTitle">W3C mobileOK Basic Tests 1.0</title>
		<field type="bibtex:topic">mobileok[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2008/REC-mobileOK-basic10-tests-20081208</identifier>
	</reference>
	<reference name="mw4droadmap" src="bibtex:misc" src-info="bibtex:line-38405" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Stéphane</givenname>
				<surname>Boyera</surname>
			</person>
		</names>
		<date value="2009-12"/>
		<abstract>
			<richtext>
				<p>This document is the heart of the MW4D IG work. Its purpose is to understand the current challenges of deploying development-oriented services on mobile phones, evaluate existing technologies, and identify the most promising directions to lower the barriers of developing, deploying and accessing services on mobile phones and thereby creating an enabling environment for more social-oriented services to appear. This document is divided into two major parts. The first part presents the major challenges today for both developing and accessing mobile services, potential ways to bridge them with existing tools, technologies and infrastructure, and potential research directions to follow to provide a more comprehensive resolution or solution. The second part focuses on presenting the major technologies and the major options existing today to deploy content and applications on mobile phones. For each of these technologies, the document presents a short analysis of the technology's potential and the requirements in terms of infrastructure, devices, targeted end-users, and costs associated with implementation and delivery.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Note NOTE-mw4d-roadmap-20091208</howpublished>
		<title type="sharef:primaryTitle">Mobile Web for Social Development Roadmap</title>
		<identifier type="sharef:uri">http://www.w3.org/TR/2009/NOTE-mw4d-roadmap-20091208</identifier>
	</reference>
	<reference name="ctlandscape" src="bibtex:misc" src-info="bibtex:line-38415" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Jo</givenname>
				<surname>Rabin</surname>
			</person>
			<person>
				<givenname>Andrew</givenname>
				<surname>Swainston</surname>
			</person>
		</names>
		<date value="2009-10"/>
		<abstract>
			<richtext>
				<p>This document identifies the issues surrounding use of transforming proxies in the delivery of Web content. It does not comment on the techniques that cause these issues, it merely identifies them in order to inform the requirements of the Content Transformation Guidelines document. That document is to offer recommendations as to how components of the delivery context can cooperate to achieve, at a minimum, a functional user experience. In this revision the document is largely historical — the Content Transformation Guidelines document, published under the title "Guidelines for Web Content Transformation Proxies" was initially inspired by the set of requirements identified in this document, but has subsequently evolved based on available technologies and feedback.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft NOTE-ct-landscape-20091027</howpublished>
		<title type="sharef:primaryTitle">Content Transformation Landscape 1.0</title>
		<identifier type="sharef:uri">http://www.w3.org/TR/2009/NOTE-ct-landscape-20091027</identifier>
	</reference>
	<reference name="powderusecases" src="bibtex:misc" src-info="bibtex:line-38425" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Phil</givenname>
				<surname>Archer</surname>
			</person>
		</names>
		<date value="2007-10"/>
		<abstract>
			<richtext>
				<p>This document sets out the use cases and requirements that have motivated the development of the Protocol for Web Description Resources (POWDER). The use cases address social and commercial needs to provide information about groups of Web resources, such as those available from a Web site, to aid the annotation and/or personalization of content for end users in varying delivery contexts.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Note NOTE-powder-use-cases-20071031</howpublished>
		<title type="sharef:primaryTitle">POWDER: Use Cases and Requirements</title>
		<field type="bibtex:topic">powder[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2007/NOTE-powder-use-cases-20071031</identifier>
	</reference>
	<reference name="powdergrouping" src="bibtex:misc" src-info="bibtex:line-38436" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Phil</givenname>
				<surname>Archer</surname>
			</person>
			<person>
				<givenname>Andrea</givenname>
				<surname>Perego</surname>
			</person>
			<person>
				<givenname>Kevin</givenname>
				<surname>Smith</surname>
			</person>
		</names>
		<date value="2009-09"/>
		<abstract>
			<richtext>
				<p>The Protocol for Web Description Resources (POWDER) facilitates the publication of descriptions of multiple resources such as all those available from a Web site. This document describes how sets of IRIs can be defined such that descriptions or other data can be applied to the resources obtained by dereferencing IRIs that are elements of the set. IRI sets are defined as XML elements with relatively loose operational semantics. This is underpinned by the formal semantics of POWDER which include a semantic extension, defined separately. A GRDDL transform is associated with the POWDER namespace that maps the operational to the formal semantics.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Recommendation REC-powder-grouping-20090901</howpublished>
		<title type="sharef:primaryTitle">Protocol for Web Description Resources (POWDER): Grouping of Resources</title>
		<field type="bibtex:topic">powder[1]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2009/REC-powder-grouping-20090901</identifier>
	</reference>
	<reference name="powderdr" src="bibtex:misc" src-info="bibtex:line-38447" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Phil</givenname>
				<surname>Archer</surname>
			</person>
			<person>
				<givenname>Kevin</givenname>
				<surname>Smith</surname>
			</person>
			<person>
				<givenname>Andrea</givenname>
				<surname>Perego</surname>
			</person>
		</names>
		<date value="2009-09"/>
		<abstract>
			<richtext>
				<p>The purpose of the Protocol for Web Description Resources (POWDER) is to provide a means for individuals or organizations to describe a group of resources through the publication of machine-readable metadata, as motivated by the POWDER Use Cases. This document details the creation and lifecycle of Description Resources (DRs), which encapsulate such metadata. These are typically represented in a highly constrained XML dialect that is relatively human-readable. The meaning of such DRs are underpinned by formal semantics, accessible by performing a GRDDL Transform.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Recommendation REC-powder-dr-20090901</howpublished>
		<title type="sharef:primaryTitle">Protocol for Web Description Resources (POWDER): Description Resources</title>
		<field type="bibtex:topic">powder[1]</field>
		<field type="bibtex:updates">xhtmlev</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2009/REC-powder-dr-20090901</identifier>
	</reference>
	<reference name="powderxsd" src="bibtex:misc" src-info="bibtex:line-38459" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Andrea</givenname>
				<surname>Perego</surname>
			</person>
			<person>
				<givenname>Phil</givenname>
				<surname>Archer</surname>
			</person>
			<person>
				<givenname>Kevin</givenname>
				<surname>Smith</surname>
			</person>
		</names>
		<date value="2007-09"/>
		<abstract>
			<richtext>
				<p>This is the namespace document for the XML schema used in the Protocol for Web Description resources (POWDER). It defines the datatypes used and the structure for Description Resources where these are serialized in XML.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-powder-xsd-20070925</howpublished>
		<title type="sharef:primaryTitle">Protocol for Web Description Resources (POWDER): Web Description Resources Datatypes (WDRD)</title>
		<field type="bibtex:topic">powder[0.9] wdrd[1]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2007/WD-powder-xsd-20070925</identifier>
	</reference>
	<reference name="powderformal" src="bibtex:misc" src-info="bibtex:line-38470" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Stasinos</givenname>
				<surname>Konstantopoulos</surname>
			</person>
			<person>
				<givenname>Phil</givenname>
				<surname>Archer</surname>
			</person>
		</names>
		<date value="2009-09"/>
		<abstract>
			<richtext>
				<p>This document underpins the Protocol for Web Description Resources (POWDER). It describes how the relatively simple operational format of a POWDER document can be transformed through two stages, first into a more tightly constrained XML format (POWDER-BASE), and then into an RDF/OWL encoding (POWDER-S) that may be processed by Semantic Web tools. Such processing is only possible, however, if tools implement the semantic extension defined within this document. The formal semantics of POWDER are best understood after the reader is acquainted with the Description Resources and Grouping of Resources documents.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Recommendation REC-powder-formal-20090901</howpublished>
		<title type="sharef:primaryTitle">Protocol for Web Description Resources (POWDER): Formal Semantics</title>
		<field type="bibtex:topic">powder[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2009/REC-powder-formal-20090901</identifier>
	</reference>
	<reference name="powdertest" src="bibtex:misc" src-info="bibtex:line-38481" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Antonis</givenname>
				<surname>Kukurikos</surname>
			</person>
			<person>
				<givenname>Phil</givenname>
				<surname>Archer</surname>
			</person>
		</names>
		<date value="2009-09"/>
		<abstract>
			<richtext>
				<p>The document describes and presents test cases for the Protocol for Web Description Resources (POWDER). The test cases aim to indicate the correct formats of POWDER documents and illustrate various crucial aspects on the usage of POWDER documents, such as locating a document and infering information from it.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Note NOTE-powder-test-20090910</howpublished>
		<title type="sharef:primaryTitle">Protocol for Web Description Resources (POWDER): Test Suite</title>
		<field type="bibtex:topic">powder[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2009/NOTE-powder-test-20090910</identifier>
	</reference>
	<reference name="powderprimer" src="bibtex:misc" src-info="bibtex:line-38492" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Kai</givenname>
				<surname>Scheppe</surname>
			</person>
		</names>
		<date value="2009-09"/>
		<abstract>
			<richtext>
				<p>POWDER — Protocol for Web Description Resources — provides a mechanism to describe and discover web resources and helps the users to make a decision whether the resource is of interest. There are a variety of use cases: from providing a better means to describing web resources and creating trustmarks to aiding in content discovery, child protection and semantic web searches. There are two varieties of POWDER: a complex, semantically rich variety, called POWDER-S, and a much simpler version, just called POWDER, which is intended as the primary transport mechanism for Description Resources. POWDER-S can be generated automatically from POWDER.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Note NOTE-powder-primer-20090901</howpublished>
		<title type="sharef:primaryTitle">Protocol for Web Description Resources (POWDER): Primer</title>
		<field type="bibtex:topic">powder[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2009/NOTE-powder-primer-20090901</identifier>
	</reference>
	<reference name="pointersinrdf" src="bibtex:misc" src-info="bibtex:line-38503" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Carlos</givenname>
				<surname>Iglesias</surname>
			</person>
			<person>
				<givenname>Mike</givenname>
				<surname>Squillace</surname>
			</person>
		</names>
		<date value="2009-10"/>
		<abstract>
			<richtext>
				<p>This specification contains a framework for representing pointers — entities that permit identifying a portion or segment of a piece of content — making use of the Resource Description Framework (RDF). It also describes a number of specific types of pointers that permit portions of a document to be referred to in different ways. When referring to a specific part of, say, a piece of Web content, it is useful to be able to have a consistent manner by which to refer to a particular segment of a Web document, to have a variety of ways by which to refer to that same segment, and to make the reference robust in the face of changes to that document. This specification is part of the W3C Evaluation And Report Language (EARL) but can be reused in other contexts too.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-Pointers-in-RDF10-20091029</howpublished>
		<title type="sharef:primaryTitle">Pointer Methods in RDF 1.0</title>
		<field type="bibtex:topic">xml[0.8] rdf[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2009/WD-Pointers-in-RDF10-20091029</identifier>
	</reference>
	<reference name="xmlevents" src="bibtex:misc" src-info="bibtex:line-38514" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Shane</givenname>
				<surname>McCarron</surname>
			</person>
			<person>
				<givenname>Steven</givenname>
				<surname>Pemberton</surname>
			</person>
			<person>
				<givenname>T. V.</givenname>
				<surname>Raman</surname>
			</person>
		</names>
		<date value="2003-10"/>
		<abstract>
			<richtext>
				<p>The XML Events module defined in this specification provides XML languages with the ability to uniformly integrate event listeners and associated event handlers with Document Object Model (DOM) Level 2 event interfaces. The result is to provide an interoperable way of associating behaviors with document-level markup.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Recommendation REC-xml-events-20031014</howpublished>
		<title type="sharef:primaryTitle">XML Events — An Events Syntax for XML</title>
		<field type="bibtex:topic">xml[0.8] dom2[0.9]</field>
		<field type="bibtex:updates">xhtmlev</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2003/REC-xml-events-20031014</identifier>
	</reference>
	<reference name="xmlevents2" src="bibtex:misc" src-info="bibtex:line-38526" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Shane</givenname>
				<surname>McCarron</surname>
			</person>
			<person>
				<givenname>Mark</givenname>
				<surname>Birbeck</surname>
			</person>
			<person>
				<givenname>Roland</givenname>
				<surname>Merrick</surname>
			</person>
		</names>
		<date value="2010-12"/>
		<abstract>
			<richtext>
				<p>This specification defines three modules: XML Events to define events and their characteristics; XML Handlers to define mappings between events and actions; and XML Scripting to assist in defining functions to support the handlers. These modules work together to provide XML languages with the ability to uniformly integrate event listeners and associated event handlers with Document Object Model (DOM) Level 3 event interfaces. The result is to provide an interoperable way of associating behaviors with document-level markup.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Note NOTE-xml-events-20101216</howpublished>
		<title type="sharef:primaryTitle">XML Events 2</title>
		<field type="bibtex:topic">xml[0.8] dom2[0.9]</field>
		<field type="bibtex:updates">xmlevents</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2010/NOTE-xml-events-20101216</identifier>
	</reference>
	<reference name="xml" src="bibtex:misc" src-info="bibtex:line-38538" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Tim</givenname>
				<surname>Bray</surname>
			</person>
			<person>
				<givenname>Jean</givenname>
				<surname>Paoli</surname>
			</person>
			<person>
				<givenname>C. Michael</givenname>
				<surname>Sperberg-McQueen</surname>
			</person>
		</names>
		<date value="1998-02"/>
		<abstract>
			<richtext>
				<p>The Extensible Markup Language (XML) is a subset of SGML that is completely described in this document. Its goal is to enable generic SGML to be served, received, and processed on the Web in the way that is now possible with HTML. XML has been designed for ease of implementation and for interoperability with both SGML and HTML.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Recommendation REC-xml-19980210</howpublished>
		<title type="sharef:primaryTitle">Extensible Markup Language (XML) 1.0</title>
		<field type="bibtex:topic">xml[1] dtd[1]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/1998/REC-xml-19980210</identifier>
	</reference>
	<reference name="xml10sec" src="bibtex:misc" src-info="bibtex:line-38549" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Tim</givenname>
				<surname>Bray</surname>
			</person>
			<person>
				<givenname>Jean</givenname>
				<surname>Paoli</surname>
			</person>
			<person>
				<givenname>C. Michael</givenname>
				<surname>Sperberg-McQueen</surname>
			</person>
			<person>
				<givenname>Eve</givenname>
				<surname>Maler</surname>
			</person>
		</names>
		<date value="2000-10"/>
		<abstract>
			<richtext>
				<p>The Extensible Markup Language (XML) is a subset of SGML that is completely described in this document. Its goal is to enable generic SGML to be served, received, and processed on the Web in the way that is now possible with HTML. XML has been designed for ease of implementation and for interoperability with both SGML and HTML.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Recommendation REC-xml-20001006</howpublished>
		<title type="sharef:primaryTitle">Extensible Markup Language (XML) 1.0 (Second Edition)</title>
		<field type="bibtex:topic">xml[1] dtd[1]</field>
		<field type="bibtex:updates">xml</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2000/REC-xml-20001006</identifier>
	</reference>
	<reference name="xml10third" src="bibtex:misc" src-info="bibtex:line-38561" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Tim</givenname>
				<surname>Bray</surname>
			</person>
			<person>
				<givenname>Jean</givenname>
				<surname>Paoli</surname>
			</person>
			<person>
				<givenname>C. Michael</givenname>
				<surname>Sperberg-McQueen</surname>
			</person>
			<person>
				<givenname>Eve</givenname>
				<surname>Maler</surname>
			</person>
			<person>
				<givenname>François</givenname>
				<surname>Yergeau</surname>
			</person>
		</names>
		<date value="2004-02"/>
		<abstract>
			<richtext>
				<p>The Extensible Markup Language (XML) is a subset of SGML that is completely described in this document. Its goal is to enable generic SGML to be served, received, and processed on the Web in the way that is now possible with HTML. XML has been designed for ease of implementation and for interoperability with both SGML and HTML.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Recommendation REC-xml-20040204</howpublished>
		<title type="sharef:primaryTitle">Extensible Markup Language (XML) 1.0 (Third Edition)</title>
		<field type="bibtex:topic">xml[1] dtd[1]</field>
		<field type="bibtex:updates">xml10sec</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2004/REC-xml-20040204</identifier>
	</reference>
	<reference name="xml10fourth" src="bibtex:misc" src-info="bibtex:line-38573" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Tim</givenname>
				<surname>Bray</surname>
			</person>
			<person>
				<givenname>Jean</givenname>
				<surname>Paoli</surname>
			</person>
			<person>
				<givenname>C. Michael</givenname>
				<surname>Sperberg-McQueen</surname>
			</person>
			<person>
				<givenname>Eve</givenname>
				<surname>Maler</surname>
			</person>
			<person>
				<givenname>François</givenname>
				<surname>Yergeau</surname>
			</person>
		</names>
		<date value="2006-08"/>
		<abstract>
			<richtext>
				<p>The Extensible Markup Language (XML) is a subset of SGML that is completely described in this document. Its goal is to enable generic SGML to be served, received, and processed on the Web in the way that is now possible with HTML. XML has been designed for ease of implementation and for interoperability with both SGML and HTML.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Recommendation REC-xml-20060816</howpublished>
		<title type="sharef:primaryTitle">Extensible Markup Language (XML) 1.0 (Fourth Edition)</title>
		<field type="bibtex:topic">xml[1] dtd[1]</field>
		<field type="bibtex:updates">xml10third</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2006/REC-xml-20060816</identifier>
	</reference>
	<reference name="xml10fifth" src="bibtex:misc" src-info="bibtex:line-38585" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Tim</givenname>
				<surname>Bray</surname>
			</person>
			<person>
				<givenname>Jean</givenname>
				<surname>Paoli</surname>
			</person>
			<person>
				<givenname>C. Michael</givenname>
				<surname>Sperberg-McQueen</surname>
			</person>
			<person>
				<givenname>Eve</givenname>
				<surname>Maler</surname>
			</person>
			<person>
				<givenname>François</givenname>
				<surname>Yergeau</surname>
			</person>
		</names>
		<date value="2008-11"/>
		<abstract>
			<richtext>
				<p>The Extensible Markup Language (XML) is a subset of SGML that is completely described in this document. Its goal is to enable generic SGML to be served, received, and processed on the Web in the way that is now possible with HTML. XML has been designed for ease of implementation and for interoperability with both SGML and HTML.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Recommendation REC-xml-20081126</howpublished>
		<title type="sharef:primaryTitle">Extensible Markup Language (XML) 1.0 (Fifth Edition)</title>
		<field type="bibtex:topic">xml[1] dtd[1]</field>
		<field type="bibtex:updates">xml10fourth</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2008/REC-xml-20081126</identifier>
	</reference>
	<reference name="xmlprocprofiles" src="bibtex:misc" src-info="bibtex:line-38597" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Henry S.</givenname>
				<surname>Thompson</surname>
			</person>
			<person>
				<givenname>Norman</givenname>
				<surname>Walsh</surname>
			</person>
		</names>
		<date value="2011-04"/>
		<abstract>
			<richtext>
				<p>This specification defines several XML processor profiles, each of which fully determines a data model for any given XML document. It is intended as a resource for other specifications, which can by a single normative reference establish precisely what input processing they require.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-xml-proc-profiles-20110412</howpublished>
		<title type="sharef:primaryTitle">XML Processor Profiles</title>
		<field type="bibtex:topic">xml[1]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2011/WD-xml-proc-profiles-20110412</identifier>
	</reference>
	<reference name="xml10blue" src="bibtex:misc" src-info="bibtex:line-38608" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>John</givenname>
				<surname>Cowan</surname>
			</person>
		</names>
		<date value="2001-09"/>
		<abstract>
			<richtext>
				<p>This document lists the design principles and requirements for the Blueberry revision of the XML Recommendation, a limited revision of XML 1.0 being developed by the World Wide Web Consortium's XML Core Working Group solely to address character set issues.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-xml-blueberry-req-20010921</howpublished>
		<title type="sharef:primaryTitle">XML Blueberry Requirements</title>
		<field type="bibtex:topic">xml[1] dtd[1]</field>
		<field type="bibtex:updates">xml</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2001/WD-xml-blueberry-req-20010921</identifier>
	</reference>
	<reference name="xml11" src="bibtex:misc" src-info="bibtex:line-38620" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Tim</givenname>
				<surname>Bray</surname>
			</person>
			<person>
				<givenname>Jean</givenname>
				<surname>Paoli</surname>
			</person>
			<person>
				<givenname>C. Michael</givenname>
				<surname>Sperberg-McQueen</surname>
			</person>
			<person>
				<givenname>Eve</givenname>
				<surname>Maler</surname>
			</person>
			<person>
				<givenname>François</givenname>
				<surname>Yergeau</surname>
			</person>
			<person>
				<givenname>John</givenname>
				<surname>Cowan</surname>
			</person>
		</names>
		<date value="2004-02"/>
		<abstract>
			<richtext>
				<p>The Extensible Markup Language (XML) is a subset of SGML that is completely described in this document. Its goal is to enable generic SGML to be served, received, and processed on the Web in the way that is now possible with HTML. XML has been designed for ease of implementation and for interoperability with both SGML and HTML.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Recommendation REC-xml11-20040204</howpublished>
		<title type="sharef:primaryTitle">Extensible Markup Language (XML) 1.1</title>
		<field type="bibtex:topic">xml[1] dtd[1]</field>
		<field type="bibtex:updates">xml10blue</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2004/REC-xml11-20040204</identifier>
	</reference>
	<reference name="xml11sec" src="bibtex:misc" src-info="bibtex:line-38632" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Tim</givenname>
				<surname>Bray</surname>
			</person>
			<person>
				<givenname>Jean</givenname>
				<surname>Paoli</surname>
			</person>
			<person>
				<givenname>C. Michael</givenname>
				<surname>Sperberg-McQueen</surname>
			</person>
			<person>
				<givenname>Eve</givenname>
				<surname>Maler</surname>
			</person>
			<person>
				<givenname>François</givenname>
				<surname>Yergeau</surname>
			</person>
			<person>
				<givenname>John</givenname>
				<surname>Cowan</surname>
			</person>
		</names>
		<date value="2006-08"/>
		<abstract>
			<richtext>
				<p>The Extensible Markup Language (XML) is a subset of SGML that is completely described in this document. Its goal is to enable generic SGML to be served, received, and processed on the Web in the way that is now possible with HTML. XML has been designed for ease of implementation and for interoperability with both SGML and HTML.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Recommendation REC-xml11-20060816</howpublished>
		<title type="sharef:primaryTitle">Extensible Markup Language (XML) 1.1 (Second Edition)</title>
		<field type="bibtex:topic">xml[1] dtd[1]</field>
		<field type="bibtex:updates">xml11</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2006/REC-xml11-20060816</identifier>
	</reference>
	<reference name="xmlidreq" src="bibtex:misc" src-info="bibtex:line-38644" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Jonathan</givenname>
				<surname>Marsh</surname>
			</person>
		</names>
		<date value="2003-08"/>
		<abstract>
			<richtext>
				<p>Since XML 1.0, the ability of processors to identify an XML element by an explicit identifier ("IDness") has depended upon validation. Both DTDs and XML Schema have mechanisms to identify the structures containing unique identifiers. But neither XML Schema nor DTDs are required by all processors. A common processor type does not perform validation, nor fetch external resources for the purpose of acertaining whether the document contains unique identifiers. This document sets out the requirements for a mechanism for determining "IDness" applicable to all classes of XML processors.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-xml-id-req-20030806</howpublished>
		<title type="sharef:primaryTitle">xml:id Requirements</title>
		<field type="bibtex:topic">xml[0.9] xmlid[1]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2003/WD-xml-id-req-20030806</identifier>
	</reference>
	<reference name="xmlid" src="bibtex:misc" src-info="bibtex:line-38655" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Jonathan</givenname>
				<surname>Marsh</surname>
			</person>
			<person>
				<givenname>Daniel</givenname>
				<surname>Veillard</surname>
			</person>
			<person>
				<givenname>Norman</givenname>
				<surname>Walsh</surname>
			</person>
		</names>
		<date value="2005-09"/>
		<abstract>
			<richtext>
				<p>This document defines the meaning of the attribute xml:id as a universal spelling for ID attributes in XML documents and defines processing of this attribute to identify IDs in the absence of validation, without fetching external resources, and without relying on an internal subset.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Recommendation REC-xml-id-20050909</howpublished>
		<title type="sharef:primaryTitle">xml:id Version 1.0</title>
		<field type="bibtex:topic">xml[0.9] xmlid[1]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2005/REC-xml-id-20050909</identifier>
	</reference>
	<reference name="turingtest" src="bibtex:misc" src-info="bibtex:line-38666" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Matt</givenname>
				<surname>May</surname>
			</person>
		</names>
		<date value="2005-11"/>
		<abstract>
			<richtext>
				<p>A common method of limiting access to services made available over the Web is visual verification of a bitmapped image. This presents a major problem to users who are blind, have low vision, or have a learning disability such as dyslexia. This document examines a number of potential solutions that allow systems to test for human users while preserving access by users with disabilities.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft NOTE-turingtest-20051123</howpublished>
		<title type="sharef:primaryTitle">Inaccessibility of CAPTCHA</title>
		<field type="bibtex:topic">captcha[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2005/NOTE-turingtest-20051123</identifier>
	</reference>
	<reference name="inkml" src="bibtex:misc" src-info="bibtex:line-38677" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Yi-Min</givenname>
				<surname>Chee</surname>
			</person>
			<person>
				<givenname>Katrin</givenname>
				<surname>Franke</surname>
			</person>
			<person>
				<givenname>Max</givenname>
				<surname>Froumentin</surname>
			</person>
			<person>
				<givenname>Sriganesh</givenname>
				<surname>Madhvanath</surname>
			</person>
			<person>
				<givenname>Jose-Antonio</givenname>
				<surname>Magaña</surname>
			</person>
			<person>
				<givenname>Grégory</givenname>
				<surname>Pakosz</surname>
			</person>
			<person>
				<givenname>Gregory</givenname>
				<surname>Russell</surname>
			</person>
			<person>
				<givenname>Muthuselvam</givenname>
				<surname>Selvaraj</surname>
			</person>
			<person>
				<givenname>Giovanni</givenname>
				<surname>Seni</surname>
			</person>
			<person>
				<givenname>Christopher</givenname>
				<surname>Tremblay</surname>
			</person>
			<person>
				<givenname>Larry</givenname>
				<surname>Yaeger</surname>
			</person>
		</names>
		<names type="sharef:editor">
			<person>
				<givenname>Stephen M.</givenname>
				<surname>Watt</surname>
			</person>
			<person>
				<givenname>Tom</givenname>
				<surname>Underhill</surname>
			</person>
		</names>
		<date value="2011-01"/>
		<abstract>
			<richtext>
				<p>This document describes the syntax and semantics for the Ink Markup Language. The Ink Markup Language serves as the data format for representing ink entered with an electronic pen or stylus. The markup allows for the input and processing of handwriting, gestures, sketches, music and other notational languages in applications. It provides a common format for the exchange of ink data between components such as handwriting and gesture recognizers, signature verifiers, and other ink-aware modules. It may be used in the W3C Multimodal Interaction Framework as proposed by the W3C Multimodal Interaction Activity.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Candidate Recommendation CR-InkML-20110111</howpublished>
		<title type="sharef:primaryTitle">Ink Markup Language</title>
		<field type="bibtex:topic">inkml[1]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2011/CR-InkML-20110111</identifier>
	</reference>
	<reference name="emotionml" src="bibtex:misc" src-info="bibtex:line-38689" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Paolo</givenname>
				<surname>Baggia</surname>
			</person>
			<person>
				<givenname>Felix</givenname>
				<surname>Burkhardt</surname>
			</person>
			<person>
				<givenname>Catherine</givenname>
				<surname>Pelachaud</surname>
			</person>
			<person>
				<givenname>Christian</givenname>
				<surname>Peter</surname>
			</person>
			<person>
				<givenname>Enrico</givenname>
				<surname>Zovato</surname>
			</person>
		</names>
		<names type="sharef:editor">
			<person>
				<givenname>Marc</givenname>
				<surname>Schröder</surname>
			</person>
		</names>
		<date value="2011-04"/>
		<abstract>
			<richtext>
				<p>As the web is becoming ubiquitous, interactive, and multimodal, technology needs to deal increasingly with human factors, including emotions. The specification of Emotion Markup Language 1.0 aims to strike a balance between practical applicability and scientific well-foundedness. The language is conceived as a "plug-in" language suitable for use in three different areas: (1) manual annotation of data; (2) automatic recognition of emotion-related states from user behavior; and (3) generation of emotion-related system behavior.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-emotionml-20110407</howpublished>
		<title type="sharef:primaryTitle">Emotion Markup Language (EmotionML) 1.0</title>
		<field type="bibtex:topic">emotionml[1]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2011/WD-emotionml-20110407</identifier>
	</reference>
	<reference name="emotionvoc" src="bibtex:misc" src-info="bibtex:line-38701" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Kazuyuki</givenname>
				<surname>Ashimura</surname>
			</person>
			<person>
				<givenname>Paolo</givenname>
				<surname>Baggia</surname>
			</person>
			<person>
				<givenname>Felix</givenname>
				<surname>Burkhardt</surname>
			</person>
			<person>
				<givenname>Alessandro</givenname>
				<surname>Oltramari</surname>
			</person>
			<person>
				<givenname>Christian</givenname>
				<surname>Peter</surname>
			</person>
			<person>
				<givenname>Enrico</givenname>
				<surname>Zovato</surname>
			</person>
		</names>
		<names type="sharef:editor">
			<person>
				<givenname>Marc</givenname>
				<surname>Schröder</surname>
			</person>
			<person>
				<givenname>Catherine</givenname>
				<surname>Pelachaud</surname>
			</person>
		</names>
		<date value="2011-04"/>
		<abstract>
			<richtext>
				<p>This document provides a list of emotion vocabularies that can be used with EmotionML to represent emotions and related states. EmotionML provides mechanisms to represent emotions in terms of scientifically valid descriptors: categories, dimensions, appraisals, and action tendencies. Given the lack of agreement in the community, EmotionML does not provide a single vocabulary of emotion terms, but gives users a choice to select the most suitable emotion vocabulary in their annotations. In order to promote interoperability, publicly defined vocabularies should be used where possible and reasonable from the point of view of the target application. The present document provides a number of emotion vocabularies that can be used for this purpose.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-emotion-voc-20110407</howpublished>
		<title type="sharef:primaryTitle">Vocabularies for EmotionML</title>
		<field type="bibtex:topic">emotionml[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2011/WD-emotion-voc-20110407</identifier>
	</reference>
	<reference name="xmlpipeline10" src="bibtex:misc" src-info="bibtex:line-38713" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Norman</givenname>
				<surname>Walsh</surname>
			</person>
			<person>
				<givenname>Eve</givenname>
				<surname>Maler</surname>
			</person>
		</names>
		<date value="2002-02"/>
		<abstract>
			<richtext>
				<p>This Note describes the features and syntax for XML Pipeline Definition Language. Pipeline is an XML vocabulary for describing the processing relationships between XML resources. A pipeline document specifies the inputs and outputs to XML processes and a pipeline controller uses this document to figure out the chain of processing that must be executed in order to get a particular result.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Note NOTE-xml-pipeline-20020228</howpublished>
		<title type="sharef:primaryTitle">XML Pipeline Definition Language Version 1.0</title>
		<field type="bibtex:topic">xmlpipelinedefinitionlanguage[1]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2002/NOTE-xml-pipeline-20020228</identifier>
	</reference>
	<reference name="xmlsgml" src="bibtex:misc" src-info="bibtex:line-38724" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>James</givenname>
				<surname>Clark</surname>
			</person>
		</names>
		<date value="1997-12"/>
		<abstract>
			<richtext>
				<p>This document provides a detailed comparison of SGML (ISO 8879) and XML.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Note NOTE-sgml-xml-97121</howpublished>
		<title type="sharef:primaryTitle">Comparison of SGML and XML</title>
		<field type="bibtex:topic">xml[0.9] sgml[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/NOTE-sgml-xml-971215</identifier>
	</reference>
	<reference name="dcd" src="bibtex:misc" src-info="bibtex:line-38735" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Tim</givenname>
				<surname>Bray</surname>
			</person>
			<person>
				<givenname>Charles</givenname>
				<surname>Frankston</surname>
			</person>
			<person>
				<givenname>Ashok</givenname>
				<surname>Malhotra</surname>
			</person>
		</names>
		<date value="1998-07"/>
		<abstract>
			<richtext>
				<p>This document proposes a structural schema facility, Document Content Description (DCD), for specifying rules covering the structure and content of XML documents. The DCD proposal incorporates a subset of the XML-Data Submission and expresses it in a way which is consistent with the ongoing W3C RDF (Resource Description Framework) effort; in particular, DCD is an RDF vocabulary. DCD is intended to define document constraints in an XML syntax; these constraints may be used in the same fashion as traditional XML DTDs. DCD also provides additional properties, such as basic datatypes.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Note NOTE-dcd-19980731</howpublished>
		<title type="sharef:primaryTitle">Document Content Description for XML</title>
		<field type="bibtex:topic">dcd[1]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/1998/NOTE-dcd-19980731</identifier>
	</reference>
	<reference name="uriclari" src="bibtex:misc" src-info="bibtex:line-38746" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Anthony B.</givenname>
				<surname>Coates</surname>
			</person>
			<person>
				<givenname>Dan</givenname>
				<surname>Connolly</surname>
			</person>
			<person>
				<givenname>Diana</givenname>
				<surname>Dack</surname>
			</person>
			<person>
				<givenname>Leslie L.</givenname>
				<surname>Daigle</surname>
			</person>
			<person>
				<givenname>Ray</givenname>
				<surname>Denenberg</surname>
			</person>
			<person>
				<givenname>Martin J.</givenname>
				<surname>Dürst</surname>
			</person>
			<person>
				<givenname>Paul</givenname>
				<surname>Grosso</surname>
			</person>
			<person>
				<givenname>Sandro</givenname>
				<surname>Hawke</surname>
			</person>
			<person>
				<givenname>Renato</givenname>
				<surname>Iannella</surname>
			</person>
			<person>
				<givenname>Graham</givenname>
				<surname>Klyne</surname>
			</person>
			<person>
				<givenname>Larry</givenname>
				<surname>Masinter</surname>
			</person>
			<person>
				<givenname>Michael</givenname>
				<surname>Mealling</surname>
			</person>
			<person>
				<givenname>Mark</givenname>
				<surname>Needleman</surname>
			</person>
			<person>
				<givenname>Norman</givenname>
				<surname>Walsh</surname>
			</person>
		</names>
		<date value="2001-09"/>
		<abstract>
			<richtext>
				<p>This paper addresses and attempts to clarify two issues pertaining to URIs, and presents recommendations. Section 1 addresses how URI space is partitioned and the relationship between URIs, URLs, and URNs. Section 2 describes how URI schemes and URN namespace ids are registered. Section 3 mentions additional unresolved issues not considered by this paper and section 4 presents recommendations.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Note NOTE-uri-clarification-20010921</howpublished>
		<title type="sharef:primaryTitle">URIs, URLs, and URNs: Clarifications and Recommendations 1.0</title>
		<field type="bibtex:topic">uri[0.9] url[0.9] urn[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2001/NOTE-uri-clarification-20010921</identifier>
	</reference>
	<reference name="curie" src="bibtex:misc" src-info="bibtex:line-38757" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Mark</givenname>
				<surname>Birbeck</surname>
			</person>
			<person>
				<givenname>Shane</givenname>
				<surname>McCarron</surname>
			</person>
		</names>
		<date value="2010-12"/>
		<abstract>
			<richtext>
				<p>This document defines a generic, abbreviated syntax for expressing URIs. This syntax is intended to be used as a common element by language designers. Target languages include, but are not limited to, XML languages. The intended audience for this document is Language designers, not the users of those Languages.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Note NOTE-curie-20101216</howpublished>
		<title type="sharef:primaryTitle">CURIE Syntax 1.0 — A Syntax for Expressing Compact URIs</title>
		<field type="bibtex:topic">uri[0.9] curie[1] iri[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2010/NOTE-curie-20101216</identifier>
	</reference>
	<reference name="soap11" src="bibtex:misc" src-info="bibtex:line-38768" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Don</givenname>
				<surname>Box</surname>
			</person>
			<person>
				<givenname>David</givenname>
				<surname>Ehnebuske</surname>
			</person>
			<person>
				<givenname>Gopal</givenname>
				<surname>Kakivaya</surname>
			</person>
			<person>
				<givenname>Andrew</givenname>
				<surname>Layman</surname>
			</person>
			<person>
				<givenname>Noah</givenname>
				<surname>Mendelsohn</surname>
			</person>
			<person>
				<givenname>Henrik</givenname>
				<surname>Frystyk Nielsen</surname>
			</person>
			<person>
				<givenname>Satish</givenname>
				<surname>Thatte</surname>
			</person>
			<person>
				<givenname>Dave</givenname>
				<surname>Winer</surname>
			</person>
		</names>
		<date value="2000-05"/>
		<abstract>
			<richtext>
				<p>SOAP is a lightweight protocol for exchange of information in a decentralized, distributed environment. It is an XML based protocol that consists of three parts: an envelope that defines a framework for describing what is in a message and how to process it, a set of encoding rules for expressing instances of application-defined datatypes, and a convention for representing remote procedure calls and responses. SOAP can potentially be used in combination with a variety of other protocols; however, the only bindings defined in this document describe how to use SOAP in combination with HTTP and HTTP Extension Framework.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Note NOTE-SOAP-20000508</howpublished>
		<title type="sharef:primaryTitle">Simple Object Access Protocol (SOAP) 1.1</title>
		<field type="bibtex:topic">soap[1]</field>
		<field type="bibtex:updates">box99</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2000/NOTE-SOAP-20000508</identifier>
	</reference>
	<reference name="soap11rorhttpbinding" src="bibtex:misc" src-info="bibtex:line-38780" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>David</givenname>
				<surname>Orchard</surname>
			</person>
		</names>
		<date value="2006-03"/>
		<abstract>
			<richtext>
				<p>SOAP Version 1.1 provides an HTTP binding for exchanging a request and a response. This binding provides a "request optional response" refinement that enables an HTTP response with status code 202 to have a SOAP envelope or to be empty.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Note NOTE-soap11-ror-httpbinding-20060321</howpublished>
		<title type="sharef:primaryTitle">SOAP 1.1 Request Optional Response HTTP Binding</title>
		<field type="bibtex:topic">soap[0.8] http[0.8]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2006/NOTE-soap11-ror-httpbinding-20060321</identifier>
	</reference>
	<reference name="soapjms" src="bibtex:misc" src-info="bibtex:line-38791" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Phil</givenname>
				<surname>Adams</surname>
			</person>
			<person>
				<givenname>Peter</givenname>
				<surname>Easton</surname>
			</person>
			<person>
				<givenname>Eric</givenname>
				<surname>Johnson</surname>
			</person>
			<person>
				<givenname>Roland</givenname>
				<surname>Merrick</surname>
			</person>
			<person>
				<givenname>Mark</givenname>
				<surname>Phillips</surname>
			</person>
		</names>
		<date value="2009-10"/>
		<abstract>
			<richtext>
				<p>This document specifies how SOAP binds to a messaging system that supports the Java Message Service (JMS). Binding is specified for both SOAP 1.1 and SOAP 1.2 using the SOAP 1.2 Protocol Binding Framework. This specification also describes how to use WSDL documents to indicate and control the use of this binding.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-soapjms-20101026</howpublished>
		<title type="sharef:primaryTitle">SOAP over Java Message Service 1.0</title>
		<field type="bibtex:topic">soap[0.9] jms[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2010/WD-soapjms-20101026</identifier>
	</reference>
	<reference name="photordf" src="bibtex:misc" src-info="bibtex:line-38802" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Yves</givenname>
				<surname>Lafon</surname>
			</person>
			<person>
				<givenname>Bert</givenname>
				<surname>Bos</surname>
			</person>
		</names>
		<date value="2002-04"/>
		<abstract>
			<richtext>
				<p>This note describes a project for describing &amp; retrieving (digitized) photos with (RDF) metadata. It describes the RDF schemas, a data-entry program for quickly entering metadata for large numbers of photos, a way to serve the photos and the metadata over HTTP, and some suggestions for search methods to retrieve photos based on their descriptions. The data-entry program has been implemented in Java, a specific Jigsaw frame has been done to retrieve the RDF from the image through HTTP. The RDF schema uses the Dublin Core schema as well as additional schemas for technical data. We already have a demo site and there is sample source code available for download. The system can be useful for collections of holiday snapshots as well as for more ambitious photo collections.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Note NOTE-photo-rdf-20020419</howpublished>
		<title type="sharef:primaryTitle">Describing and retrieving photos using RDF and HTTP</title>
		<field type="bibtex:topic">rdf[0.6] http[0.6]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2002/NOTE-photo-rdf-20020419</identifier>
	</reference>
	<reference name="soapattach" src="bibtex:misc" src-info="bibtex:line-38813" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>John J.</givenname>
				<surname>Barton</surname>
			</person>
			<person>
				<givenname>Satish</givenname>
				<surname>Thatte</surname>
			</person>
			<person>
				<givenname>Henrik</givenname>
				<surname>Frystyk Nielsen</surname>
			</person>
		</names>
		<date value="2000-12"/>
		<abstract>
			<richtext>
				<p>This document defines a binding for a SOAP 1.1 message to be carried within a MIME multipart/related message in such a way that the processing rules for the SOAP 1.1 message are preserved. The MIME multipart mechanism for encapsulation of compound documents can be used to bundle entities related to the SOAP 1.1 message such as attachments. Rules for the usage of URI references to refer to entities bundled within the MIME package are specified.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Note NOTE-SOAP-attachments-20001211</howpublished>
		<title type="sharef:primaryTitle">SOAP Messages with Attachments</title>
		<field type="bibtex:topic">soap[0.9] mime[0.7] swa[1]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2000/NOTE-SOAP-attachments-20001211</identifier>
	</reference>
	<reference name="soap12email" src="bibtex:misc" src-info="bibtex:line-38824" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Highland Mary</givenname>
				<surname>Mountain</surname>
			</person>
			<person>
				<givenname>Jacek</givenname>
				<surname>Kopecký</surname>
			</person>
			<person>
				<givenname>Stuart</givenname>
				<surname>Williams</surname>
			</person>
			<person>
				<givenname>Glen</givenname>
				<surname>Daniels</surname>
			</person>
			<person>
				<givenname>Noah</givenname>
				<surname>Mendelsohn</surname>
			</person>
		</names>
		<date value="2002-07"/>
		<abstract>
			<richtext>
				<p>This document is meant to be an illustration of the SOAP 1.2 Protocol Binding Framework applied to a well known internet transport mechanism, Email, specifically RFC 2822.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Note NOTE-soap12-email-20020703</howpublished>
		<title type="sharef:primaryTitle">SOAP Version 1.2 Email Binding</title>
		<field type="bibtex:topic">soap[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2002/NOTE-soap12-email-20020703</identifier>
	</reference>
	<reference name="soap12rep" src="bibtex:misc" src-info="bibtex:line-38835" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Anish</givenname>
				<surname>Karmarkar</surname>
			</person>
			<person>
				<givenname>Martin</givenname>
				<surname>Gudgin</surname>
			</person>
			<person>
				<givenname>Yves</givenname>
				<surname>Lafon</surname>
			</person>
		</names>
		<date value="2005-01"/>
		<abstract>
			<richtext>
				<p>This document describes the semantics and serialization of a SOAP header block for carrying resource representations in SOAP messages</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Recommendation REC-soap12-rep-20050125</howpublished>
		<title type="sharef:primaryTitle">Resource Representation SOAP Header Block</title>
		<field type="bibtex:topic">soap[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2005/REC-soap12-rep-20050125</identifier>
	</reference>
	<reference name="soap12af" src="bibtex:misc" src-info="bibtex:line-38846" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Henrik</givenname>
				<surname>Frystyk Nielsen</surname>
			</person>
			<person>
				<givenname>Hervé</givenname>
				<surname>Ruellan</surname>
			</person>
		</names>
		<date value="2004-06"/>
		<abstract>
			<richtext>
				<p>This document defines a SOAP feature that represents an abstract model for SOAP attachments. It provides the basis for the creation of SOAP bindings that transmit such attachments along with a SOAP envelope, and provides for reference of those attachments from the envelope. SOAP attachments are described using the notion of a compound document structure consisting of a primary SOAP message part and zero or more related documents parts known as attachments.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Note NOTE-soap12-af-20040608</howpublished>
		<title type="sharef:primaryTitle">SOAP 1.2 Attachment Feature</title>
		<field type="bibtex:topic">soap[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2004/NOTE-soap12-af-20040608</identifier>
	</reference>
	<reference name="soap12" src="bibtex:misc" src-info="bibtex:line-38857" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Martin</givenname>
				<surname>Gudgin</surname>
			</person>
			<person>
				<givenname>Marc</givenname>
				<surname>Hadley</surname>
			</person>
			<person>
				<givenname>Jean-Jacques</givenname>
				<surname>Moreau</surname>
			</person>
			<person>
				<givenname>Henrik</givenname>
				<surname>Frystyk Nielsen</surname>
			</person>
		</names>
		<date value="2001-07"/>
		<howpublished>World Wide Web Consortium, Working Draft WD-soap12-20010709</howpublished>
		<title type="sharef:primaryTitle">SOAP Version 1.2</title>
		<field type="bibtex:topic">soap[1]</field>
		<field type="bibtex:updates">soap11</field>
	</reference>
	<reference name="soap12-0" src="bibtex:misc" src-info="bibtex:line-38867" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Nilo</givenname>
				<surname>Mitra</surname>
			</person>
		</names>
		<date value="2003-06"/>
		<abstract>
			<richtext>
				<p>SOAP Version 1.2 Part 0: Primer is a non-normative document intended to provide an easily understandable tutorial on the features of the SOAP Version 1.2 specifications. In particular, it describes the features through various usage scenarios, and is intended to complement the normative text contained in Part 1 and Part 2 of the SOAP 1.2 specifications.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Recommendation REC-soap12-part0-20030624</howpublished>
		<title type="sharef:primaryTitle">SOAP Version 1.2 Part 0: Primer</title>
		<field type="bibtex:topic">soap[0.9]</field>
		<field type="bibtex:updates">soap12</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2003/REC-soap12-part0-20030624</identifier>
	</reference>
	<reference name="soap12-0sec" src="bibtex:misc" src-info="bibtex:line-38879" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Nilo</givenname>
				<surname>Mitra</surname>
			</person>
			<person>
				<givenname>Yves</givenname>
				<surname>Lafon</surname>
			</person>
		</names>
		<date value="2007-04"/>
		<abstract>
			<richtext>
				<p>SOAP Version 1.2 Part 0: Primer (Second Edition) is a non-normative document intended to provide an easily understandable tutorial on the features of SOAP Version 1.2. In particular, it describes the features through various usage scenarios, and is intended to complement the normative text contained in Part 1 and Part 2 of the SOAP 1.2 specifications. This second edition includes additional material on the SOAP Message Transmission Optimization Mechanism (MTOM), the XML-binary Optimized Packaging (XOP) and the Resource Representation SOAP Header Block (RRSHB) specifications.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Recommendation REC-soap12-part0-20070427</howpublished>
		<title type="sharef:primaryTitle">SOAP Version 1.2 Part 0: Primer (Second Edition)</title>
		<field type="bibtex:topic">soap[0.9] mtom[0.9] xop[0.9] rrshb[0.9]</field>
		<field type="bibtex:updates">soap12-0</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2007/REC-soap12-part0-20070427</identifier>
	</reference>
	<reference name="soap12-1" src="bibtex:misc" src-info="bibtex:line-38891" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Martin</givenname>
				<surname>Gudgin</surname>
			</person>
			<person>
				<givenname>Marc</givenname>
				<surname>Hadley</surname>
			</person>
			<person>
				<givenname>Noah</givenname>
				<surname>Mendelsohn</surname>
			</person>
			<person>
				<givenname>Jean-Jacques</givenname>
				<surname>Moreau</surname>
			</person>
			<person>
				<givenname>Henrik</givenname>
				<surname>Frystyk Nielsen</surname>
			</person>
		</names>
		<date value="2003-06"/>
		<abstract>
			<richtext>
				<p>SOAP Version 1.2 is a lightweight protocol intended for exchanging structured information in a decentralized, distributed environment. "Part 1: Messaging Framework" defines, using XML technologies, an extensible messaging framework containing a message construct that can be exchanged over a variety of underlying protocols.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Recommendation REC-soap12-part1-20030624</howpublished>
		<title type="sharef:primaryTitle">SOAP Version 1.2 Part 1: Messaging Framework</title>
		<field type="bibtex:topic">soap[1]</field>
		<field type="bibtex:updates">soap12</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2003/REC-soap12-part1-20030624</identifier>
	</reference>
	<reference name="soap12-1sec" src="bibtex:misc" src-info="bibtex:line-38903" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Martin</givenname>
				<surname>Gudgin</surname>
			</person>
			<person>
				<givenname>Marc</givenname>
				<surname>Hadley</surname>
			</person>
			<person>
				<givenname>Noah</givenname>
				<surname>Mendelsohn</surname>
			</person>
			<person>
				<givenname>Jean-Jacques</givenname>
				<surname>Moreau</surname>
			</person>
			<person>
				<givenname>Henrik</givenname>
				<surname>Frystyk Nielsen</surname>
			</person>
			<person>
				<givenname>Anish</givenname>
				<surname>Karmarkar</surname>
			</person>
			<person>
				<givenname>Yves</givenname>
				<surname>Lafon</surname>
			</person>
		</names>
		<date value="2007-04"/>
		<abstract>
			<richtext>
				<p>SOAP Version 1.2 is a lightweight protocol intended for exchanging structured information in a decentralized, distributed environment. "Part 1: Messaging Framework" defines, using XML technologies, an extensible messaging framework containing a message construct that can be exchanged over a variety of underlying protocols.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Recommendation REC-soap12-part1-20070427</howpublished>
		<title type="sharef:primaryTitle">SOAP Version 1.2 Part 1: Messaging Framework (Second Edition)</title>
		<field type="bibtex:topic">soap[1]</field>
		<field type="bibtex:updates">soap12-1</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2007/REC-soap12-part1-20070427</identifier>
	</reference>
	<reference name="soap12-2" src="bibtex:misc" src-info="bibtex:line-38915" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Martin</givenname>
				<surname>Gudgin</surname>
			</person>
			<person>
				<givenname>Marc</givenname>
				<surname>Hadley</surname>
			</person>
			<person>
				<givenname>Noah</givenname>
				<surname>Mendelsohn</surname>
			</person>
			<person>
				<givenname>Jean-Jacques</givenname>
				<surname>Moreau</surname>
			</person>
			<person>
				<givenname>Henrik</givenname>
				<surname>Frystyk Nielsen</surname>
			</person>
		</names>
		<date value="2003-06"/>
		<abstract>
			<richtext>
				<p>SOAP Version 1.2 is a lightweight protocol intended for exchanging structured information in a decentralized, distributed environment. SOAP Version 1.2 Part 2: Adjuncts defines a set of adjuncts that may be used with SOAP Version 1.2 Part 1: Messaging Framework. This specification depends on SOAP Version 1.2 Part 1: Messaging Framework.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Recommendation REC-soap12-part2-20030624</howpublished>
		<title type="sharef:primaryTitle">SOAP Version 1.2 Part 2: Adjuncts</title>
		<field type="bibtex:topic">soap[1]</field>
		<field type="bibtex:updates">soap12</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2003/REC-soap12-part2-20030624</identifier>
	</reference>
	<reference name="soap12-2sec" src="bibtex:misc" src-info="bibtex:line-38927" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Martin</givenname>
				<surname>Gudgin</surname>
			</person>
			<person>
				<givenname>Marc</givenname>
				<surname>Hadley</surname>
			</person>
			<person>
				<givenname>Noah</givenname>
				<surname>Mendelsohn</surname>
			</person>
			<person>
				<givenname>Jean-Jacques</givenname>
				<surname>Moreau</surname>
			</person>
			<person>
				<givenname>Henrik</givenname>
				<surname>Frystyk Nielsen</surname>
			</person>
			<person>
				<givenname>Anish</givenname>
				<surname>Karmarkar</surname>
			</person>
			<person>
				<givenname>Yves</givenname>
				<surname>Lafon</surname>
			</person>
		</names>
		<date value="2007-04"/>
		<abstract>
			<richtext>
				<p>SOAP Version 1.2 is a lightweight protocol intended for exchanging structured information in a decentralized, distributed environment. SOAP Version 1.2 Part 2: Adjuncts defines a set of adjuncts that may be used with SOAP Version 1.2 Part 1: Messaging Framework. This specification depends on SOAP Version 1.2 Part 1: Messaging Framework.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Recommendation REC-soap12-part2-20070427</howpublished>
		<title type="sharef:primaryTitle">SOAP Version 1.2 Part 2: Adjuncts (Second Edition)</title>
		<field type="bibtex:topic">soap[1]</field>
		<field type="bibtex:updates">soap12-2</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2007/REC-soap12-part2-20070427</identifier>
	</reference>
	<reference name="soap12-3" src="bibtex:misc" src-info="bibtex:line-38939" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>David</givenname>
				<surname>Orchard</surname>
			</person>
		</names>
		<date value="2007-07"/>
		<abstract>
			<richtext>
				<p>SOAP Version 1.2 Part 2 provides a request-response MEP and a response-only MEP. This, the SOAP 1.2 Part 3, provides a one-way MEP.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Note NOTE-soap12-part3-20070702</howpublished>
		<title type="sharef:primaryTitle">SOAP 1.2 Part 3: One-Way MEP</title>
		<field type="bibtex:topic">soap[1]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2007/NOTE-soap12-part3-20070702</identifier>
	</reference>
	<reference name="soap12test" src="bibtex:misc" src-info="bibtex:line-38950" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Hugo</givenname>
				<surname>Haas</surname>
			</person>
			<person>
				<givenname>Oisin</givenname>
				<surname>Hurley</surname>
			</person>
			<person>
				<givenname>Anish</givenname>
				<surname>Karmarkar</surname>
			</person>
			<person>
				<givenname>Jeff</givenname>
				<surname>Mischkinsky</surname>
			</person>
			<person>
				<givenname>Mark</givenname>
				<surname>Jones</surname>
			</person>
			<person>
				<givenname>Lynne</givenname>
				<surname>Thompson</surname>
			</person>
			<person>
				<givenname>Richard</givenname>
				<surname>Martin</surname>
			</person>
		</names>
		<date value="2003-06"/>
		<abstract>
			<richtext>
				<p>This document draws on assertions found in the SOAP Version 1.2 specifications, and provides a set of tests in order to show whether the assertions are implemented in a SOAP processor. A SOAP 1.2 implementation that passes all of the tests specified in this document may claim to conform to the SOAP 1.2 Test Suite, 2003 06 24. It is incorrect to claim to be compliant with the SOAP Version 1.2 specifications merely by passing successfully all the tests provided in this test suite. It is also incorrect to claim that an implementation is non compliant with the SOAP Version 1.2 specifications based on its failure to pass one or more of the tests in this test suite.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Recommendation REC-soap12-testcollection-20030624</howpublished>
		<title type="sharef:primaryTitle">SOAP Version 1.2 Specification Assertions and Test Collection</title>
		<field type="bibtex:topic">soap[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2003/REC-soap12-testcollection-20030624</identifier>
	</reference>
	<reference name="soap12testsec" src="bibtex:misc" src-info="bibtex:line-38961" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Hugo</givenname>
				<surname>Haas</surname>
			</person>
			<person>
				<givenname>Oisin</givenname>
				<surname>Hurley</surname>
			</person>
			<person>
				<givenname>Anish</givenname>
				<surname>Karmarkar</surname>
			</person>
			<person>
				<givenname>Jeff</givenname>
				<surname>Mischkinsky</surname>
			</person>
			<person>
				<givenname>Mark</givenname>
				<surname>Jones</surname>
			</person>
			<person>
				<givenname>Lynne</givenname>
				<surname>Thompson</surname>
			</person>
			<person>
				<givenname>Richard</givenname>
				<surname>Martin</surname>
			</person>
		</names>
		<date value="2007-04"/>
		<abstract>
			<richtext>
				<p>This document draws on assertions found in the SOAP Version 1.2 specifications, and provides a set of tests in order to show whether the assertions are implemented in a SOAP processor. A SOAP 1.2 implementation that passes all of the tests specified in this document may claim to conform to the SOAP 1.2 Test Suite, 2006 12 19. It is incorrect to claim to be compliant with the SOAP Version 1.2 specifications merely by passing successfully all the tests provided in this test suite. It is also incorrect to claim that an implementation is non compliant with the SOAP Version 1.2 specifications based on its failure to pass one or more of the tests in this test suite.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Recommendation REC-soap12-testcollection-20070427</howpublished>
		<title type="sharef:primaryTitle">SOAP Version 1.2 Specification Assertions and Test Collection (Second Edition)</title>
		<field type="bibtex:topic">soap[0.9]</field>
		<field type="bibtex:updates">soap12test</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2007/REC-soap12-testcollection-20070427</identifier>
	</reference>
	<reference name="soap12n11n" src="bibtex:misc" src-info="bibtex:line-38973" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Martin</givenname>
				<surname>Gudgin</surname>
			</person>
			<person>
				<givenname>Marc</givenname>
				<surname>Hadley</surname>
			</person>
		</names>
		<date value="2003-10"/>
		<abstract>
			<richtext>
				<p>SOAP 1.2 intermediaries have some license when reserializing messages that pass through them. This document defines a transformation algorithm that renders all semantically equivalent SOAP messages identically. The transformation may be used in conjunction with an XML canonicalization algorithm prior to the generation of a message digest in producing XML digital signatures that are sufficiently robust to survive passage through one or more SOAP intermediaries.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Note NOTE-soap12-n11n-20031008</howpublished>
		<title type="sharef:primaryTitle">SOAP Version 1.2 Message Normalization</title>
		<field type="bibtex:topic">soap[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2003/NOTE-soap12-n11n-20031008</identifier>
	</reference>
	<reference name="soap12mtom" src="bibtex:misc" src-info="bibtex:line-38984" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Martin</givenname>
				<surname>Gudgin</surname>
			</person>
			<person>
				<givenname>Noah</givenname>
				<surname>Mendelsohn</surname>
			</person>
			<person>
				<givenname>Mark</givenname>
				<surname>Nottingham</surname>
			</person>
			<person>
				<givenname>Hervé</givenname>
				<surname>Ruellan</surname>
			</person>
		</names>
		<date value="2005-01"/>
		<abstract>
			<richtext>
				<p>This document describes an abstract feature and a concrete implementation of it for optimizing the transmission and/or wire format of SOAP messages. The concrete implementation relies on the XOP format for carrying SOAP messages.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Recommendation REC-soap12-mtom-20050125</howpublished>
		<title type="sharef:primaryTitle">SOAP Message Transmission Optimization Mechanism</title>
		<field type="bibtex:topic">soap[0.9] mtom[1]</field>
		<field type="bibtex:updates">soap12af</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2005/REC-soap12-mtom-20050125</identifier>
	</reference>
	<reference name="soap12mtompolicy" src="bibtex:misc" src-info="bibtex:line-38996" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Christopher</givenname>
				<surname>Ferris</surname>
			</person>
			<person>
				<givenname>Yves</givenname>
				<surname>Lafon</surname>
			</person>
		</names>
		<date value="2007-09"/>
		<abstract>
			<richtext>
				<p>This specification describes a domain-specific policy assertion that indicates endpoint support of the optimized MIME multipart/related serialization of SOAP messages defined in section 3 of the SOAP Message Transmission Optimization Mechanism specification. This policy assertion can be specified within a policy alternative as defined in Web Services Policy 1.5 —Framework and attached to a WSDL description as defined in Web Services Policy 1.5 — Attachment.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-soap12-mtom-policy-20070918</howpublished>
		<title type="sharef:primaryTitle">MTOM Serialization Policy Assertion 1.1</title>
		<field type="bibtex:topic">mtom[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2007/WD-soap12-mtom-policy-20070918</identifier>
	</reference>
	<reference name="xop10" src="bibtex:misc" src-info="bibtex:line-39007" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Martin</givenname>
				<surname>Gudgin</surname>
			</person>
			<person>
				<givenname>Noah</givenname>
				<surname>Mendelsohn</surname>
			</person>
			<person>
				<givenname>Mark</givenname>
				<surname>Nottingham</surname>
			</person>
			<person>
				<givenname>Hervé</givenname>
				<surname>Ruellan</surname>
			</person>
		</names>
		<date value="2005-01"/>
		<abstract>
			<richtext>
				<p>This document defines the XML-binary Optimized Packaging (XOP) convention, a means of more efficiently serializing XML Infosets that have certain types of content.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Recommendation REC-xop10-20050125</howpublished>
		<title type="sharef:primaryTitle">XML-binary Optimized Packaging</title>
		<field type="bibtex:topic">xop[1]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2005/REC-xop10-20050125</identifier>
	</reference>
	<reference name="xopincfaq" src="bibtex:misc" src-info="bibtex:line-39018" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Michael</givenname>
				<surname>Mahan</surname>
			</person>
		</names>
		<date value="2004-06"/>
		<howpublished>World Wide Web Consortium, Note NOTE-xopinc-FAQ-20040608</howpublished>
		<title type="sharef:primaryTitle">XOP Inclusion Mechanism — Frequently Asked Questions</title>
		<field type="bibtex:topic">xop[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2004/NOTE-xopinc-FAQ-20040608</identifier>
	</reference>
	<reference name="soap12osucr" src="bibtex:misc" src-info="bibtex:line-39028" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Tony</givenname>
				<surname>Graham</surname>
			</person>
			<person>
				<givenname>Anish</givenname>
				<surname>Karmarkar</surname>
			</person>
			<person>
				<givenname>Mark</givenname>
				<surname>Jones</surname>
			</person>
		</names>
		<date value="2004-06"/>
		<howpublished>World Wide Web Consortium, Working Draft WD-soap12-os-ucr-20040608</howpublished>
		<title type="sharef:primaryTitle">SOAP Optimized Serialization Use Cases and Requirements</title>
		<field type="bibtex:topic">soap[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2004/WD-soap12-os-ucr-20040608</identifier>
	</reference>
	<reference name="xbcusecases" src="bibtex:misc" src-info="bibtex:line-39038" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Mike</givenname>
				<surname>Cokus</surname>
			</person>
			<person>
				<givenname>Santiago</givenname>
				<surname>Pericas-Geertsen</surname>
			</person>
		</names>
		<date value="2005-03"/>
		<abstract>
			<richtext>
				<p>This document describes use cases for evaluating the potential benefits of an alternate serialization for XML. The use cases are documented here to understand the constraints involved in environments for which XML employment is currently problematic because of one or more inherent inefficiencies in XML 1.x. Desirable properties of alternate XML serializations to address the use cases are derived and discussed in a separate publication of the XML Binary Characterization Working Group (XBC WG).</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Note NOTE-xbc-use-cases-20050331</howpublished>
		<title type="sharef:primaryTitle">XML Binary Characterization Use Cases</title>
		<identifier type="sharef:uri">http://www.w3.org/TR/2005/NOTE-xbc-use-cases-20050331</identifier>
	</reference>
	<reference name="xbcproperties" src="bibtex:misc" src-info="bibtex:line-39048" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Mike</givenname>
				<surname>Cokus</surname>
			</person>
			<person>
				<givenname>Santiago</givenname>
				<surname>Pericas-Geertsen</surname>
			</person>
		</names>
		<date value="2005-03"/>
		<abstract>
			<richtext>
				<p>This document is the result of a study to identify desirable properties in an XML format. An XML format is a format that is capable of representing the information in an XML document. The properties have been derived from requirements induced by use cases collected in the "XBC Use Cases" document. Properties are divided into two categories: algorithmic and format. Besides these two categories, Section 6 Additional Considerations lists additional considerations which, because of the difficulty to establish an accurate measurement, have not been listed as properties but are nonetheless relevant for an accurate comparison between different proposals.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Note NOTE-xbc-properties-20050331</howpublished>
		<title type="sharef:primaryTitle">XML Binary Characterization Properties</title>
		<identifier type="sharef:uri">http://www.w3.org/TR/2005/NOTE-xbc-properties-20050331</identifier>
	</reference>
	<reference name="xbcmeasurement" src="bibtex:misc" src-info="bibtex:line-39058" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Stephen D.</givenname>
				<surname>Williams</surname>
			</person>
			<person>
				<givenname>Peter</givenname>
				<surname>Haggar</surname>
			</person>
		</names>
		<date value="2005-03"/>
		<abstract>
			<richtext>
				<p>This document describes measurement aspects, methods, caveats, test data, and test scenarios for evaluating the potential benefits of a candidate binary XML format.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Note NOTE-xbc-measurement-20050331</howpublished>
		<title type="sharef:primaryTitle">XML Binary Characterization Measurement Methodologies</title>
		<identifier type="sharef:uri">http://www.w3.org/TR/2005/NOTE-xbc-measurement-20050331</identifier>
	</reference>
	<reference name="xbcchar" src="bibtex:misc" src-info="bibtex:line-39068" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Oliver</givenname>
				<surname>Goldman</surname>
			</person>
			<person>
				<givenname>Dmitry</givenname>
				<surname>Lenkov</surname>
			</person>
		</names>
		<date value="2005-03"/>
		<abstract>
			<richtext>
				<p>This document describes the processes and results of the XML Binary Characterization Working Group in evaluating the need and feasibility of a "binary XML" recommendation. It includes an analysis of which properties such a format must possess. It recommends that the W3C produce a "binary XML" recommendation and enumerates the minimum requirements which this "binary XML" recommendation must meet.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Note NOTE-xbc-characterization-20050331</howpublished>
		<title type="sharef:primaryTitle">XML Binary Characterization</title>
		<identifier type="sharef:uri">http://www.w3.org/TR/2005/NOTE-xbc-characterization-20050331</identifier>
	</reference>
	<reference name="eximeasurements" src="bibtex:misc" src-info="bibtex:line-39078" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Greg</givenname>
				<surname>White</surname>
			</person>
			<person>
				<givenname>Jaakko</givenname>
				<surname>Kangasharju</surname>
			</person>
			<person>
				<givenname>Don</givenname>
				<surname>Brutzman</surname>
			</person>
			<person>
				<givenname>Stephen D.</givenname>
				<surname>Williams</surname>
			</person>
		</names>
		<date value="2007-07"/>
		<abstract>
			<richtext>
				<p>This Working Group Note presents measurement results of various high-performance XML interchange encoding formats and their associated processors, made by the Efficient XML Interchange (EXI) Working Group. The measurements have been conducted following the recommendations of the XML Binary Characterization (XBC) Working Group. In particular, this draft covers measurements of the properties of "compactness", "processing efficiency" and "roundtrip support", as defined by the XBC WG. We start by describing the context in which this analysis is being made, and the position of an efficient format in the landscape of high performance XML strategies. Then we describe the measured quantities in detail and the test framework in which they were made, and give a short description of each format. Finally, a summary of the results and the conclusions of the group are included. The full measurements and analysis are included in an appendix and supporting documents. As a result of the measurements described here, the working group selected "Efficient XML" to be the basis for the proposed encoding specification to be prepared as a candidate W3C Recommendation. Follow up work has centered around integrating some features from the other measured format technologies, particularly variations for both more efficient structural and value encodings.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-exi-measurements-20070725</howpublished>
		<title type="sharef:primaryTitle">Efficient XML Interchange Measurements Note</title>
		<field type="bibtex:topic">exi[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2007/WD-exi-measurements-20070725</identifier>
	</reference>
	<reference name="exi" src="bibtex:misc" src-info="bibtex:line-39089" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>John</givenname>
				<surname>Schneider</surname>
			</person>
			<person>
				<givenname>Takuki</givenname>
				<surname>Kamiya</surname>
			</person>
		</names>
		<date value="2011-03"/>
		<abstract>
			<richtext>
				<p>This document is the specification of the Efficient XML Interchange (EXI) format. EXI is a very compact representation for the Extensible Markup Language (XML) Information Set that is intended to simultaneously optimize performance and the utilization of computational resources. The EXI format uses a hybrid approach drawn from the information and formal language theories, plus practical techniques verified by measurements, for entropy encoding XML information. Using a relatively simple algorithm, which is amenable to fast and compact implementation, and a small set of datatype representations, it reliably produces efficient encodings of XML event streams. The grammar production system and format definition of EXI are presented.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Recommendation REC-exi-20110310</howpublished>
		<title type="sharef:primaryTitle">Efficient XML Interchange (EXI) Format 1.0</title>
		<field type="bibtex:topic">exi[1]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2011/REC-exi-20110310</identifier>
	</reference>
	<reference name="exiprimer" src="bibtex:misc" src-info="bibtex:line-39100" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Daniel</givenname>
				<surname>Peintner</surname>
			</person>
			<person>
				<givenname>Santiago</givenname>
				<surname>Pericas-Geertsen</surname>
			</person>
		</names>
		<date value="2009-12"/>
		<abstract>
			<richtext>
				<p>This is a non-normative document intended to provide an easily readable technical background on the Efficient XML Interchange (EXI) format. It is oriented towards quickly understanding how the EXI format can be used in practice and how options can be set to achieve specific needs. Section 2. Concepts describes the structure and content of an EXI document and introduces the notions of EXI header, EXI body, and EXI grammar which are fundamental to the understanding of the EXI format. Furthermore, additional details about data type representation, compression, and their interaction with other format features are presented. Finally, Section 3. Efficient XML Interchange by Example provides a detailed, bit-level description of both, a schema-less and a schema-informed example.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-exi-primer-20091208</howpublished>
		<title type="sharef:primaryTitle">Efficient XML Interchange (EXI) Primer</title>
		<field type="bibtex:topic">exi[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2009/WD-exi-primer-20091208</identifier>
	</reference>
	<reference name="exibestpractices" src="bibtex:misc" src-info="bibtex:line-39111" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Mike</givenname>
				<surname>Cokus</surname>
			</person>
			<person>
				<givenname>Daniel</givenname>
				<surname>Vogelheim</surname>
			</person>
		</names>
		<date value="2007-12"/>
		<abstract>
			<richtext>
				<p>The purpose of this document is to provide guidelines for the interoperable deployment of the Efficient XML Interchange (EXI) format. It provides explanations of format features and techniques to support interoperable information exchanges using EXI. While intended primarily as a practical guide for systems architects and programmers, it also presents information suitable for the general reader interested in EXI's intended role in the expanding Web.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-exi-best-practices-20071219</howpublished>
		<title type="sharef:primaryTitle">Efficient XML Interchange (EXI) Best Practices</title>
		<field type="bibtex:topic">exi[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2007/WD-exi-best-practices-20071219</identifier>
	</reference>
	<reference name="exievaluation" src="bibtex:misc" src-info="bibtex:line-39122" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Carine</givenname>
				<surname>Bournez</surname>
			</person>
		</names>
		<date value="2009-04"/>
		<abstract>
			<richtext>
				<p>This Working Group Note is an evaluation of the Efficient XML Interchange (EXI) Format 1.0 with reference to the Properties identified by the XML Binary Characterization (XBC) Working Group, relative to XML, gzipped XML and ASN.1 PER. It is conducted using the XBC Measurement methodology. For the "compactness" and "processing efficiency" Properties, the performance is measured with EXI Measurement framework, over the test data collected for the EXI measurements, representing XBC Use Cases.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-exi-evaluation-20090407</howpublished>
		<title type="sharef:primaryTitle">Efficient XML Interchange Evaluation</title>
		<field type="bibtex:topic">exi[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2009/WD-exi-evaluation-20090407</identifier>
	</reference>
	<reference name="exiimpacts" src="bibtex:misc" src-info="bibtex:line-39133" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Jaakko</givenname>
				<surname>Kangasharju</surname>
			</person>
		</names>
		<date value="2008-09"/>
		<abstract>
			<richtext>
				<p>The Efficient XML Interchange (EXI) format defines a new representation for the Extensible Markup Language (XML) Information Set. The introduction of such a format may cause disruption in systems that have so far been able to assume XML as the only representation of XML Information Set data. This document reviews areas where the introduction of EXI may disrupt or otherwise have an impact on existing XML technologies, XML processors, and applications. It also describes EXI design features and steps that may be taken by implementors to reduce or eliminate disruption and impacts.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-exi-impacts-20080903</howpublished>
		<title type="sharef:primaryTitle">Efficient XML Interchange (EXI) Impacts</title>
		<field type="bibtex:topic">exi[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2008/WD-exi-impacts-20080903</identifier>
	</reference>
	<reference name="mqueries" src="bibtex:misc" src-info="bibtex:line-39144" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Håkon Wium</givenname>
				<surname>Lie</surname>
			</person>
			<person>
				<givenname>Tantek</givenname>
				<surname>Çelik</surname>
			</person>
			<person>
				<givenname>Daniel</givenname>
				<surname>Glazman</surname>
			</person>
			<person>
				<givenname>Anne</givenname>
				<surname link="van">Kesteren</surname>
			</person>
		</names>
		<date value="2010-07"/>
		<abstract>
			<richtext>
				<p>HTML4 and CSS2 currently support media-dependent style sheets tailored for different media types. For example, a document may use sans-serif fonts when displayed on a screen and serif fonts when printed. 'screen' and 'print' are two media types that have been defined. Media queries extend the functionality of media types by allowing more precise labeling of style sheets. A media query consists of a media type and zero or more expressions that check for the conditions of particular media features. Among the media features that can be used in media queries are 'width', 'height', and 'color'. By using media queries, presentations can be tailored to a specific range of output devices without changing the content itself.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Candidate Recommendation CR-css3-mediaqueries-20100727</howpublished>
		<title type="sharef:primaryTitle">Media Queries</title>
		<field type="bibtex:topic">css[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2010/CR-css3-mediaqueries-20100727</identifier>
	</reference>
	<reference name="css3gridlayout" src="bibtex:misc" src-info="bibtex:line-39155" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Alex</givenname>
				<surname>Mogilevsky</surname>
			</person>
			<person>
				<givenname>Phil</givenname>
				<surname>Cupp</surname>
			</person>
			<person>
				<givenname>Markus</givenname>
				<surname>Mielke</surname>
			</person>
			<person>
				<givenname>Daniel</givenname>
				<surname>Glazman</surname>
			</person>
		</names>
		<date value="2011-04"/>
		<abstract>
			<richtext>
				<p>Grid Layout contains features targeted at web application authors. The Grid can be used to achieve many different layouts. It excels at dividing up space for major regions of an application, or defining the relationship in terms of size, position, and layer between parts of a control built from HTML primitives. Like tables, the Grid enables an author to align elements into columns and rows, but unlike tables, the Grid doesn't have content structure, and thus enables a wide variety of layouts not possible with tables. For example, the children of the Grid can position themselves with Grid Lines such that they overlap and layer similar to positioned elements. In addition, the absence of content structure in the Grid helps to manage changes to layout by using fluid and source order independent lay out techniques. By combining media queries with the CSS properties that control layout of the Grid and its children, authors can adapt their layout to changes in device form factors, orientation, and available space, without needing to alter the semantic nature of their content.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Working Draft WD-css3-grid-layout-20110407</howpublished>
		<title type="sharef:primaryTitle">Grid Layout</title>
		<field type="bibtex:topic">css[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2011/WD-css3-grid-layout-20110407</identifier>
	</reference>
	<reference name="xup" src="bibtex:misc" src-info="bibtex:line-39166" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Jin</givenname>
				<surname>Yu</surname>
			</person>
			<person>
				<givenname>Jun</givenname>
				<surname>Chen</surname>
			</person>
		</names>
		<date value="2002-05"/>
		<abstract>
			<richtext>
				<p>The Extensible User Interface Protocol (XUP) is a SOAP-based protocol for communicating user interface events and updates on the web. It paves a foundation for developing and consuming highly interactive web applications and services. XUP may be used with any user interface model or any event model with an XML-based representation.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Note NOTE-xup-20020528</howpublished>
		<title type="sharef:primaryTitle">XUP — Extensible User Interface Protocol</title>
		<field type="bibtex:topic">xup[1]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2002/NOTE-xup-20020528</identifier>
	</reference>
	<reference name="dt4dtd" src="bibtex:misc" src-info="bibtex:line-39177" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Lee</givenname>
				<surname>Buck</surname>
			</person>
			<person>
				<givenname>Charles F.</givenname>
				<surname>Goldfarb</surname>
			</person>
			<person>
				<givenname>Paul</givenname>
				<surname>Prescod</surname>
			</person>
		</names>
		<date value="2000-01"/>
		<abstract>
			<richtext>
				<p>The presented specification allows legacy systems that may presently be unable to convert their DTD markup declarations to XML Schema, to utilize XML Schema conformant datatypes. With it, DTD creators can specify datatypes for attribute values and data content, thereby providing the foundation for a smoother future transition path.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Note NOTE-dt4dtd-20000113</howpublished>
		<title type="sharef:primaryTitle">Datatypes for DTDs (DT4DTD) 1.0</title>
		<field type="bibtex:topic">dt4dtd[1]</field>
		<identifier type="sharef:uri">http://www.w3.org/TR/2000/NOTE-dt4dtd-20000113</identifier>
	</reference>
	<reference name="xmlschemaapi" src="bibtex:misc" src-info="bibtex:line-39188" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Elena</givenname>
				<surname>Litani</surname>
			</person>
		</names>
		<date value="2004-03"/>
		<abstract>
			<richtext>
				<p>This specification defines an XML Schema API, a platform- and language-neutral interface that allows programs and scripts to dynamically access and query the Post-Schema-Validation Infoset (PSVI) defined in Contributions to the Post-Schema-Validation Infoset (Appendix C.2). This specification also defines interfaces for loading XML schema documents. This specification is implemented in Apache Xerces2 Java Parser. There is also a C++ binding and implementation for this specification in Apache Xerces C++ Parser.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Member Submission SUBM-xmlschema-api-20040309</howpublished>
		<title type="sharef:primaryTitle">XML Schema API</title>
		<field type="bibtex:topic">xsd[0.9]</field>
		<identifier type="sharef:uri">http://www.w3.org/Submission/2004/SUBM-xmlschema-api-20040309</identifier>
	</reference>
	<reference name="rdql" src="bibtex:misc" src-info="bibtex:line-39199" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Andy</givenname>
				<surname>Seaborne</surname>
			</person>
		</names>
		<date value="2004-01"/>
		<abstract>
			<richtext>
				<p>The document describes RDQL (RDF Data Query Language) which has been implemented in a number of RDF systems for extracting information from RDF graphs. First, there is a brief introduction to the language, then a more formal description of the grammar.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Member Submission SUBM-RDQL-20040109</howpublished>
		<title type="sharef:primaryTitle">RDQL — A Query Language for RDF</title>
		<field type="bibtex:topic">rdql[1]</field>
		<identifier type="sharef:uri">http://www.w3.org/Submission/2004/SUBM-RDQL-20040109</identifier>
	</reference>
	<reference name="wadlsubm" src="bibtex:misc" src-info="bibtex:line-39210" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Marc</givenname>
				<surname>Hadley</surname>
			</person>
		</names>
		<date value="2009-08"/>
		<abstract>
			<richtext>
				<p>This specification describes the Web Application Description Language (WADL). An increasing number of Web-based enterprises (Google, Yahoo, Amazon, Flickr to name but a few) are developing HTTP-based applications that provide programmatic access to their internal data. Typically these applications are described using textual documentation that is sometimes supplemented with more formal specifications such as XML schema for XML-based data formats. WADL is designed to provide a machine process-able description of such HTTP-based Web applications.</p>
			</richtext>
		</abstract>
		<howpublished>World Wide Web Consortium, Member Submission SUBM-wadl-20090831</howpublished>
		<title type="sharef:primaryTitle">Web Application Description Language</title>
		<field type="bibtex:topic">wadl[1]</field>
		<identifier type="sharef:uri">http://www.w3.org/Submission/2009/SUBM-wadl-20090831</identifier>
	</reference>
	<reference name="dab09" src="bibtex:misc" src-info="bibtex:line-39225" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Cyrus</givenname>
				<surname>Daboo</surname>
			</person>
			<person>
				<givenname>Mike</givenname>
				<surname>Douglass</surname>
			</person>
			<person>
				<givenname>Steven</givenname>
				<surname>Lees</surname>
			</person>
		</names>
		<date value="2010-10"/>
		<abstract>
			<richtext>
				<p>This specification defines "xCal", an XML format for iCalendar data.</p>
			</richtext>
		</abstract>
		<howpublished>Internet Draft draft-daboo-et-al-icalendar-in-xml-07</howpublished>
		<title type="sharef:primaryTitle">iCalendar XML Representation</title>
		<field type="bibtex:topic">icalendar[0.9] xcalendar[1]</field>
		<identifier type="sharef:uri">http://ietfreport.isoc.org/idref/draft-daboo-et-al-icalendar-in-xml/</identifier>
	</reference>
	<reference name="har05b" src="bibtex:misc" src-info="bibtex:line-39236" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Tim</givenname>
				<surname>Hare</surname>
			</person>
		</names>
		<date value="2005-05"/>
		<abstract>
			<richtext>
				<p>This memo defines a guideline for using XML to represent calendaring information that corresponds to the iCalendar, Internet Calendaring and Scheduling Core Object Specification defined by RFC 2445 and the protocols defined by RFC2446, RFC2447 and CAP. This memo applies to all RFC 2445 extensions and modifications.</p>
			</richtext>
		</abstract>
		<howpublished>Internet Draft draft-hare-xcalendar-03</howpublished>
		<title type="sharef:primaryTitle">Guideline for use of XML with iCalendar elements</title>
		<field type="bibtex:topic">icalendar[0.9] xcalendar[1]</field>
		<identifier type="sharef:uri">http://ietfreport.isoc.org/idref/draft-hare-xcalendar/</identifier>
	</reference>
	<reference name="bar09c" src="bibtex:misc" src-info="bibtex:line-39247" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Richard</givenname>
				<surname>Barnes</surname>
			</person>
			<person>
				<givenname>Matthew</givenname>
				<surname>Lepinski</surname>
			</person>
			<person>
				<givenname>Alissa</givenname>
				<surname>Cooper</surname>
			</person>
			<person>
				<givenname>John B.</givenname>
				<surname>Morris</surname>
			</person>
			<person>
				<givenname>Hannes</givenname>
				<surname>Tschofenig</surname>
			</person>
			<person>
				<givenname>Henning</givenname>
				<surname>Schulzrinne</surname>
			</person>
		</names>
		<date value="2009-07"/>
		<abstract>
			<richtext>
				<p>Location-based services (such as navigation applications, emergency services, management of equipment in the field) need geographic location information about Internet hosts, their users, and other related entities. These applications need to securely gather and transfer location information for location services, and at the same time protect the privacy of the individuals involved. This document describes an architecture for privacy-preserving location-based services in the Internet, focusing on authorization, security, and privacy requirements for the data formats and protocols used by these services.</p>
			</richtext>
		</abstract>
		<howpublished>Internet Draft draft-barnes-geopriv-lo-sec-05</howpublished>
		<title type="sharef:primaryTitle">An Architecture for Location and Location Privacy in Internet Applications</title>
		<field type="bibtex:topic">oauth[1]</field>
		<identifier type="sharef:uri">http://tools.ietf.org/html/draft-barnes-geopriv-lo-sec</identifier>
	</reference>
	<reference name="bar09b" src="bibtex:misc" src-info="bibtex:line-39258" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Richard</givenname>
				<surname>Barnes</surname>
			</person>
			<person>
				<givenname>Matthew</givenname>
				<surname>Lepinski</surname>
			</person>
		</names>
		<date value="2009-07"/>
		<abstract>
			<richtext>
				<p>This document describes the security model for the OAuth authorization system, which allows a party that holds some authorization to delegate a subset of that authorization to another party, without requiring either party to disclose its credentials to the other. In this document, we describe a set of design constraints, a high-level work flow for establishing authorizations subject to those constraints, and set of security requirements for protocols that implement this model.</p>
			</richtext>
		</abstract>
		<howpublished>Internet Draft draft-barnes-oauth-model-01</howpublished>
		<title type="sharef:primaryTitle">The OAuth Security Model for Delegated Authorization</title>
		<field type="bibtex:topic">oauth[1]</field>
		<identifier type="sharef:uri">https://datatracker.ietf.org/drafts/draft-barnes-oauth-model</identifier>
	</reference>
	<reference name="ham09b" src="bibtex:misc" src-info="bibtex:line-39269" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Eran</givenname>
				<surname>Hammer-Lahav</surname>
			</person>
			<person>
				<givenname>Blaine</givenname>
				<surname>Cook</surname>
			</person>
		</names>
		<date value="2009-03"/>
		<abstract>
			<richtext>
				<p>This document specifies the OAuth core protocol. OAuth provides a method for clients to access server resources on behalf of another party (such a different client or an end user). It also provides a redirection-based user agent process for end users to authorize access to clients by substituting their credentials (typically, a username and password pair) with a different set of delegation-specific credentials.</p>
			</richtext>
		</abstract>
		<howpublished>Internet Draft draft-hammer-oauth-02</howpublished>
		<title type="sharef:primaryTitle">The OAuth Core Protocol</title>
		<field type="bibtex:topic">oauth[1]</field>
		<identifier type="sharef:uri">https://datatracker.ietf.org/drafts/draft-hammer-oauth</identifier>
	</reference>
	<reference name="bar07" src="bibtex:misc" src-info="bibtex:line-39280" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Mary</givenname>
				<surname>Barnes</surname>
			</person>
		</names>
		<date value="2009-08"/>
		<abstract>
			<richtext>
				<p>A Layer 7 Location Configuration Protocol (L7 LCP) is described that is used for retrieving location information from a server within an access network. The protocol includes options for retrieving location information in two forms: by value and by reference. The protocol is an extensible application-layer protocol that is independent of session-layer. This document describes the use of HyperText Transfer Protocol (HTTP) and HTTP over Transport Layer Security (HTTP/TLS) as transports for the protocol.</p>
			</richtext>
		</abstract>
		<howpublished>Internet Draft draft-ietf-geopriv-http-location-delivery-16</howpublished>
		<title type="sharef:primaryTitle">HTTP Enabled Location Delivery (HELD)</title>
		<field type="bibtex:topic">held[1]</field>
		<identifier type="sharef:uri">https://datatracker.ietf.org/drafts/draft-ietf-geopriv-http-location-delivery</identifier>
	</reference>
	<reference name="sch07" src="bibtex:misc" src-info="bibtex:line-39291" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Henning</givenname>
				<surname>Schulzrinne</surname>
			</person>
			<person>
				<givenname>Hannes</givenname>
				<surname>Tschofenig</surname>
			</person>
			<person>
				<givenname>John B.</givenname>
				<surname>Morris</surname>
			</person>
			<person>
				<givenname>Jorge R.</givenname>
				<surname>Cuellar</surname>
			</person>
			<person>
				<givenname>James M.</givenname>
				<surname>Polk</surname>
			</person>
		</names>
		<date value="2008-06"/>
		<abstract>
			<richtext>
				<p>This document defines an authorization policy language for controlling access to location information. It extends the Common Policy authorization framework to provide location-specific access control. More specifically, this document defines condition elements specific to location information in order to restrict access based on the current location of the Target. Furthermore, it offers location-specific transformation elements to reduce the granularity of the returned location information.</p>
			</richtext>
		</abstract>
		<howpublished>Internet Draft draft-ietf-geopriv-policy-17</howpublished>
		<title type="sharef:primaryTitle">Geolocation Policy: A Document Format for Expressing Privacy Preferences for Location Information</title>
		<identifier type="sharef:uri">https://datatracker.ietf.org/drafts/draft-ietf-geopriv-policy</identifier>
	</reference>
	<reference name="bar09d" src="bibtex:misc" src-info="bibtex:line-39301" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Richard</givenname>
				<surname>Barnes</surname>
			</person>
			<person>
				<givenname>Matt</givenname>
				<surname>Lepinski</surname>
			</person>
			<person>
				<givenname>Alissa</givenname>
				<surname>Cooper</surname>
			</person>
			<person>
				<givenname>John B.</givenname>
				<surname>Morris</surname>
			</person>
			<person>
				<givenname>Hannes</givenname>
				<surname>Tschofenig</surname>
			</person>
			<person>
				<givenname>Henning</givenname>
				<surname>Schulzrinne</surname>
			</person>
		</names>
		<date value="2009-10"/>
		<abstract>
			<richtext>
				<p>Location-based services (such as navigation applications, emergency services, management of equipment in the field) need geographic location information about Internet hosts, their users, and other related entities. These applications need to securely gather and transfer location information for location services, and at the same time protect the privacy of the individuals involved. This document describes an architecture for privacy-preserving location-based services in the Internet, focusing on authorization, security, and privacy requirements for the data formats and protocols used by these services.</p>
			</richtext>
		</abstract>
		<howpublished>Internet Draft draft-ietf-geopriv-arch-01</howpublished>
		<title type="sharef:primaryTitle">An Architecture for Location and Location Privacy in Internet Applications</title>
		<identifier type="sharef:uri">https://datatracker.ietf.org/drafts/draft-ietf-geopriv-arch</identifier>
	</reference>
	<reference name="may07" src="bibtex:misc" src-info="bibtex:line-39311" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Alexander</givenname>
				<surname>Mayrhofer</surname>
			</person>
			<person>
				<givenname>Christian</givenname>
				<surname>Spanring</surname>
			</person>
		</names>
		<date value="2008-02"/>
		<abstract>
			<richtext>
				<p>This document specifies an Uniform Resource Identifier (URI) for geographic areas using the 'geo' scheme name. A 'geo' URI provides a compact, human-readable, and protocol independent way to identify an area by means of a hierarchical tiling scheme.</p>
			</richtext>
		</abstract>
		<howpublished>Internet Draft draft-mayrhofer-geo-uri-02</howpublished>
		<title type="sharef:primaryTitle">A Uniform Resource Identifier for Geographic Locations ('geo' URI)</title>
		<identifier type="sharef:uri">https://datatracker.ietf.org/drafts/draft-mayrhofer-geo-uri</identifier>
	</reference>
	<reference name="may09" src="bibtex:misc" src-info="bibtex:line-39321" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Alexander</givenname>
				<surname>Mayrhofer</surname>
			</person>
			<person>
				<givenname>Christian</givenname>
				<surname>Spanring</surname>
			</person>
		</names>
		<date value="2009-11"/>
		<abstract>
			<richtext>
				<p>This document specifies a Uniform Resource Identifier (URI) for geographic locations using the 'geo' scheme name. A 'geo' URI identifies a physical location in a two- or three-dimensional coordinate reference system in a compact, simple, human-readable, and protocol-independent way. The default coordinate reference system used is WGS-84.</p>
			</richtext>
		</abstract>
		<howpublished>Internet Draft draft-ietf-geopriv-geo-uri-04</howpublished>
		<title type="sharef:primaryTitle">A Uniform Resource Identifier for Geographic Locations ('geo' URI)</title>
		<field type="bibtex:updates">may07</field>
		<identifier type="sharef:uri">https://datatracker.ietf.org/drafts/draft-ietf-geopriv-geo-uri</identifier>
	</reference>
	<reference name="dav03c" src="bibtex:misc" src-info="bibtex:line-39332" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Andrew</givenname>
				<surname>Daviel</surname>
			</person>
			<person>
				<givenname>Felix A.</givenname>
				<surname>Kägi</surname>
			</person>
		</names>
		<date value="2007-10"/>
		<abstract>
			<richtext>
				<p>This memo describes a method of registering HTML documents with a specific geographic location through means of embedded META tags. The content of the META tags gives the geographic position of the resource described by the HTML document in terms of Latitude, Longitude, and optionally Elevation in a simple, machine-readable manner. This information may be used for automated resource discovery by means of an HTML indexing agent or search engine.</p>
			</richtext>
		</abstract>
		<howpublished>Internet Draft draft-daviel-html-geo-tag-08</howpublished>
		<title type="sharef:primaryTitle">Geographic Registration of HTML Documents</title>
		<identifier type="sharef:uri">https://datatracker.ietf.org/drafts/draft-daviel-html-geo-tag</identifier>
	</reference>
	<reference name="dav03b" src="bibtex:misc" src-info="bibtex:line-39342" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Andrew</givenname>
				<surname>Daviel</surname>
			</person>
			<person>
				<givenname>Felix A.</givenname>
				<surname>Kägi</surname>
			</person>
			<person>
				<givenname>Martin</givenname>
				<surname>Kofahl</surname>
			</person>
		</names>
		<date value="2007-12"/>
		<abstract>
			<richtext>
				<p>This memo describes a method of adding simple geographic position or region information to HTTP transactions using extension headers. It allows location-based services on the World Wide Web, without the additional overhead of geographic query requests and possibly graphical input. Extension headers transmit predefined or detected position information to reflect a location that the requesting agent is interested in. This information may be used by a server to present appropriate position-dependent responses, such as search engine results or weather maps.</p>
			</richtext>
		</abstract>
		<howpublished>Internet Draft draft-daviel-http-geo-header-05</howpublished>
		<title type="sharef:primaryTitle">Geographic Extensions for HTTP Transactions</title>
		<identifier type="sharef:uri">https://datatracker.ietf.org/drafts/draft-daviel-http-geo-header</identifier>
	</reference>
	<reference name="goo07" src="bibtex:misc" src-info="bibtex:line-39352" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>J.</givenname>
				<surname>Goodwin</surname>
			</person>
			<person>
				<givenname>H.</givenname>
				<surname>Apel</surname>
			</person>
		</names>
		<date value="2007-09"/>
		<abstract>
			<richtext>
				<p>This document describes a Uniform Resource Name Namespace Identification (URN NID) for the International Organization for Standardization (ISO). This URN NID is intended for use for the identification of persistent resources published by the ISO standards body (including documents, document metadata, extracted resources such as standard schemata and standard value sets, and other resources).</p>
			</richtext>
		</abstract>
		<howpublished>Internet Draft draft-goodwin-iso-urn-02</howpublished>
		<title type="sharef:primaryTitle">A Uniform Resource Name (URN) Namespace for the International Organization for Standardization (ISO)</title>
		<identifier type="sharef:uri">https://datatracker.ietf.org/drafts/draft-goodwin-iso-urn</identifier>
	</reference>
	<reference name="pfe05" src="bibtex:misc" src-info="bibtex:line-39362" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Silvia</givenname>
				<surname>Pfeiffer</surname>
			</person>
			<person>
				<givenname>Conrad D.</givenname>
				<surname>Parker</surname>
			</person>
			<person>
				<givenname>Andre T.</givenname>
				<surname>Pang</surname>
			</person>
		</names>
		<date value="2005-03"/>
		<abstract>
			<richtext>
				<p>This document specifies a syntax for addressing time intervals within time-based Web resources through URI queries and fragments. This scheme is particularly used for Annodex and CMML. Web resources, though it could be picked up by any other time-based Web resource format. Temporal addressing enables, e.g., direct access to a clip inside a video stored on a Web Server, or direct jumps to a specific event within a piece of music. The syntax is not restricted to audio or video Web resources though, but covers all kinds of Web resources that contain time-continuous information. When a server (e.g. a Web Server) supports the URI query syntax, it is able to extract the given time subsections from the base resource and serve them as another resource of the same type. Specifying a time point or interval through a URI fragment in contrast does not deliver a subpart of the resource — instead it is up to the user agent and the resource type as to what action is invoked. Examples are a fast forward to a time point, or a zoom into a time interval.</p>
			</richtext>
		</abstract>
		<howpublished>Internet Draft draft-pfeiffer-temporal-fragments-03</howpublished>
		<title type="sharef:primaryTitle">Specifying Time Intervals in URI Queries and Fragments of Time-Based Web Resources</title>
		<identifier type="sharef:uri" resourceType="text/html">http://www.annodex.net/TR/draft-pfeiffer-temporal-fragments-03.html</identifier>
	</reference>
	<reference name="kos96" src="bibtex:misc" src-info="bibtex:line-39372" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Martijn</givenname>
				<surname>Koster</surname>
			</person>
		</names>
		<date value="1996-12"/>
		<abstract>
			<richtext>
				<p>This memo defines a method for administrators of sites on the World- Wide Web to give instructions to visiting Web robots, most importantly what areas of the site are to be avoided. This document provides a more rigid specification of the Standard for Robots Exclusion, which is currently in wide-spread use by the Web community since 1994.</p>
			</richtext>
		</abstract>
		<howpublished>Internet Draft draft-koster-robots-00</howpublished>
		<title type="sharef:primaryTitle">A Method for Web Robots Control</title>
		<identifier type="sharef:uri" resourceType="text/html">http://www.robotstxt.org/wc/norobots-rfc.html</identifier>
	</reference>
	<reference name="rfc2396bis" src="bibtex:misc" src-info="bibtex:line-39382" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Tim</givenname>
				<surname>Berners-Lee</surname>
			</person>
			<person>
				<givenname>Roy Thomas</givenname>
				<surname>Fielding</surname>
			</person>
			<person>
				<givenname>Larry</givenname>
				<surname>Masinter</surname>
			</person>
		</names>
		<date value="2004-09"/>
		<abstract>
			<richtext>
				<p>A Uniform Resource Identifier (URI) is a compact sequence of characters for identifying an abstract or physical resource. This specification defines the generic URI syntax and a process for resolving URI references that might be in relative form, along with guidelines and security considerations for the use of URIs on the Internet. The URI syntax defines a grammar that is a superset of all valid URIs, such that an implementation can parse the common components of a URI reference without knowing the scheme-specific requirements of every possible identifier. This specification does not define a generative grammar for URIs; that task is performed by the individual specifications of each URI scheme.</p>
			</richtext>
		</abstract>
		<howpublished>Internet Draft draft-fielding-uri-rfc2396bis-07</howpublished>
		<title type="sharef:primaryTitle">Uniform Resource Identifier (URI): Generic Syntax</title>
		<field type="bibtex:topic">uri[1]</field>
		<field type="bibtex:updates">rfc2396</field>
		<identifier type="sharef:uri" resourceType="text/plain">ftp://ftp.rfc-editor.org/in-notes/internet-drafts/draft-fielding-uri-rfc2396bis-07.txt</identifier>
	</reference>
	<reference name="bra03" src="bibtex:misc" src-info="bibtex:line-39394" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Tim</givenname>
				<surname>Bray</surname>
			</person>
			<person>
				<givenname>John</givenname>
				<surname>Cowan</surname>
			</person>
		</names>
		<date value="2003-10"/>
		<howpublished>Internet Draft draft-tbray-utf8+names-01</howpublished>
		<title type="sharef:primaryTitle">The UTF-8+names Unicode Encoding Form</title>
		<field type="bibtex:topic">xml[0.7]</field>
		<identifier type="sharef:uri" resourceType="text/html">http://tbray.org/tag/utf-8+names.html</identifier>
	</reference>
	<reference name="gol00" src="bibtex:misc" src-info="bibtex:line-39404" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Yaron Y.</givenname>
				<surname>Goland</surname>
			</person>
			<person>
				<givenname>Jeffrey C.</givenname>
				<surname>Schlimmer</surname>
			</person>
		</names>
		<date value="2000-06"/>
		<howpublished>Internet Draft draft-goland-fxpp-01</howpublished>
		<title type="sharef:primaryTitle">Flexible XML Processing Profile (FXPP)</title>
		<field type="bibtex:topic">xml[0.7] fxpp[1]</field>
		<identifier type="sharef:uri" resourceType="text/plain">http://www.upnp.org/download/draft-goland-fxpp-01.txt</identifier>
	</reference>
	<reference name="daw98" src="bibtex:misc" src-info="bibtex:line-39414" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Frank</givenname>
				<surname>Dawson</surname>
			</person>
		</names>
		<date value="1998-06"/>
		<howpublished>Internet Draft draft-dawson-vcard-xml-dtd-03</howpublished>
		<title type="sharef:primaryTitle">The vCard v3.0 XML DTD</title>
		<field type="bibtex:topic">vcard[0.9]</field>
		<identifier type="sharef:uri" resourceType="text/plain">http://www.watersprings.org/pub/id/draft-dawson-vcard-xml-dtd-03.txt</identifier>
	</reference>
	<reference name="gre07" src="bibtex:misc" src-info="bibtex:line-39424" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Joe</givenname>
				<surname>Gregorio</surname>
			</person>
		</names>
		<date value="2010-03"/>
		<abstract>
			<richtext>
				<p>A URI Template is a compact sequence of characters for describing a range of Uniform Resource Identifiers through variable expansion. This specification defines the URI Template syntax and the process for expanding a URI Template into a URI, along with guidelines for the use of URI Templates on the Internet.</p>
			</richtext>
		</abstract>
		<howpublished>Internet Draft draft-gregorio-uritemplate-04</howpublished>
		<title type="sharef:primaryTitle">URI Template</title>
		<field type="bibtex:topic">uri[0.8]</field>
		<identifier type="sharef:uri">https://datatracker.ietf.org/drafts/draft-gregorio-uritemplate/</identifier>
	</reference>
	<reference name="wil02h" src="bibtex:misc" src-info="bibtex:line-39435" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Erik</givenname>
				<surname>Wilde</surname>
			</person>
			<person>
				<givenname>Martin J.</givenname>
				<surname>Dürst</surname>
			</person>
		</names>
		<date value="2007-11"/>
		<abstract>
			<richtext>
				<p>This memo defines URI fragment identifiers for text/plain resources. These fragment identifiers make it possible to refer to parts of a text resource, identified by character count or range, line count or range, or a regular expression. These identification methods can be combined to identify more than one sub-resource of a text/plain resource.</p>
			</richtext>
		</abstract>
		<howpublished>Internet Draft draft-wilde-text-fragment-09</howpublished>
		<title type="sharef:primaryTitle">URI Fragment Identifiers for the text/plain Media Type</title>
		<field type="bibtex:topic">uri[0.8] mime[0.8]</field>
		<identifier type="sharef:uri">http://dret.net/netdret/publications#wil02h</identifier>
		<identifier type="sharef:uri">https://datatracker.ietf.org/drafts/draft-wilde-text-fragment/</identifier>
	</reference>
	<reference name="wil01g" src="bibtex:misc" src-info="bibtex:line-39447" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Erik</givenname>
				<surname>Wilde</surname>
			</person>
		</names>
		<date value="2006-03"/>
		<abstract>
			<richtext>
				<p>This memo describes the registration of the Short Message Service (SMS) as a registered IANA service selector for Global Switched Telephone Network (GSTN) numbers. SMS is not available for all GSTN subscribers, but it has proven very popular with users of the Global System for Mobile Communications (GSM), and has also been adapted to other telephone network technologies such as the Integrated Services Digital Network (ISDN).</p>
			</richtext>
		</abstract>
		<howpublished>Internet Draft draft-wilde-sms-service-12</howpublished>
		<title type="sharef:primaryTitle">Registration of GSTN SMS Service Qualifier</title>
		<field type="bibtex:topic">sms[0.9]</field>
		<identifier type="sharef:uri">http://dret.net/netdret/publications#wil01g</identifier>
		<identifier type="sharef:uri">https://datatracker.ietf.org/drafts/draft-wilde-sms-service/</identifier>
	</reference>
	<reference name="wil02a" src="bibtex:misc" src-info="bibtex:line-39459" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Erik</givenname>
				<surname>Wilde</surname>
			</person>
			<person>
				<givenname>Antti</givenname>
				<surname>Vähä-Sipilä</surname>
			</person>
		</names>
		<date value="2009-10"/>
		<abstract>
			<richtext>
				<p>This memo specifies the Uniform Resource Identifier (URI) scheme "sms" for specifying one or more recipients for an SMS message. SMS messages are two-way paging messages that can be sent from and received by a mobile phone or a suitably equipped networked device.</p>
			</richtext>
		</abstract>
		<howpublished>Internet Draft draft-wilde-sms-uri-20</howpublished>
		<title type="sharef:primaryTitle">URI scheme for GSM Short Message Service</title>
		<field type="bibtex:topic">sms[0.9] uri[0.8]</field>
		<field type="bibtex:updates">wil01g wil06e</field>
		<identifier type="sharef:uri">http://dret.net/netdret/publications#wil02a</identifier>
		<identifier type="sharef:uri">https://datatracker.ietf.org/drafts/draft-wilde-sms-uri/</identifier>
	</reference>
	<reference name="wil06e" src="bibtex:misc" src-info="bibtex:line-39472" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Erik</givenname>
				<surname>Wilde</surname>
			</person>
		</names>
		<date value="2006-03"/>
		<abstract>
			<richtext>
				<p>This memo requests the registration of the Universal Resource Identifier (URI) scheme "sms" for specifying a recipient (and optionally a gateway) for an SMS message. SMS messages are two-way paging messages that can be sent from and received by a mobile phone or a suitably equipped computer.</p>
			</richtext>
		</abstract>
		<howpublished>Internet Draft draft-wilde-sms-uri-registration-00</howpublished>
		<title type="sharef:primaryTitle">Registration Request for SMS URI Scheme</title>
		<field type="bibtex:topic">uri[0.8] mime[0.8]</field>
		<identifier type="sharef:uri">http://dret.net/netdret/publications#wil06e</identifier>
		<identifier type="sharef:uri">https://datatracker.ietf.org/drafts/draft-wilde-sms-uri-registration/</identifier>
	</reference>
	<reference name="mas00" src="bibtex:misc" src-info="bibtex:line-39484" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Larry</givenname>
				<surname>Masinter</surname>
			</person>
		</names>
		<date value="2000-03"/>
		<howpublished>Internet Draft</howpublished>
		<title type="sharef:primaryTitle">Internationalized Uniform Resource Identifiers (IURI)</title>
		<field type="bibtex:topic">iuri[1]</field>
	</reference>
	<reference name="mas01" src="bibtex:misc" src-info="bibtex:line-39493" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Larry</givenname>
				<surname>Masinter</surname>
			</person>
			<person>
				<givenname>Martin J.</givenname>
				<surname>Dürst</surname>
			</person>
		</names>
		<date value="2001-01"/>
		<howpublished>Internet Draft draft-masinter-url-i18n-07</howpublished>
		<title type="sharef:primaryTitle">Internationalized Resource Identifiers (IRI)</title>
		<field type="bibtex:topic">iri[1] i18n[0.9]</field>
		<field type="bibtex:updates">mas00</field>
	</reference>
	<reference name="mas10" src="bibtex:misc" src-info="bibtex:line-39503" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Larry</givenname>
				<surname>Masinter</surname>
			</person>
		</names>
		<date value="2010-10"/>
		<abstract>
			<richtext>
				<p>This document describes some of the ways in which parts of the MIME system, originally designed for electronic mail, have been used in the Web, and some of the ways in which those uses have resulted in difficulties. Given this background and justification, this document then goes on to outline requirements for changes to MIME registries and practices for their use within W3C and IETF, in order to address those difficulties. Within IETF, a companion Best Current Practice document will be developed to specifically make some changes to the Internet Media Types and Charset registries.</p>
			</richtext>
		</abstract>
		<howpublished>Internet Draft draft-masinter-mime-web-info-01</howpublished>
		<title type="sharef:primaryTitle">MIME and the Web</title>
		<field type="bibtex:topic">mime[0.9]</field>
	</reference>
	<reference name="mas10b" src="bibtex:misc" src-info="bibtex:line-39513" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Larry</givenname>
				<surname>Masinter</surname>
			</person>
		</names>
		<date value="2010-10"/>
		<abstract>
			<richtext>
				<p>This document defines two URI schemes. The first, 'duri' (standing for "dated URI"), allows indicating a URI as of a particular date (and time). This allows explicit reference to the "time of retrieval", similar to the way in which bibliographic references containing URIs are used. The second scheme, 'tdb' ( standing for "Thing Described By"), provides a way of using a way of minting URIs for anything that can be described, with the ability to fix the description to a given date or time. The 'tdb' URI scheme may reduce the need to define define new URN namespaces merely for the purpose of creating stable identifiers for concepts or abstractions: it provides a ready means for identifying "non-information resources" by semantic indirection — a way of creating a URI for anything.</p>
			</richtext>
		</abstract>
		<howpublished>Internet Draft draft-masinter-dated-uri-07</howpublished>
		<title type="sharef:primaryTitle">The 'tdb' and 'duri' URI schemes, based on dated URIs</title>
		<field type="bibtex:topic">uri[0.9]</field>
	</reference>
	<reference name="due03" src="bibtex:misc" src-info="bibtex:line-39523" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Martin J.</givenname>
				<surname>Dürst</surname>
			</person>
			<person>
				<givenname>Michel</givenname>
				<surname>Suignard</surname>
			</person>
		</names>
		<date value="2004-11"/>
		<abstract>
			<richtext>
				<p>This document defines a new protocol element, the Internationalized Resource Identifier (IRI), as a complement to the Uniform Resource Identifier (URI). An IRI is a sequence of characters from the Universal Character Set (Unicode/ISO 10646). A mapping from IRIs to URIs is defined, which means that IRIs can be used instead of URIs where appropriate to identify resources. The approach of defining a new protocol element was chosen, instead of extending or changing the definition of URIs, to allow a clear distinction and to avoid incompatibilities with existing software. Guidelines for the use and deployment of IRIs in various protocols, formats, and software components that now deal with URIs are provided.</p>
			</richtext>
		</abstract>
		<howpublished>Internet Draft draft-duerst-iri-11</howpublished>
		<title type="sharef:primaryTitle">Internationalized Resource Identifiers (IRIs)</title>
		<field type="bibtex:topic">iri[1]</field>
		<field type="bibtex:updates">mas01</field>
	</reference>
	<reference name="due08" src="bibtex:misc" src-info="bibtex:line-39534" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Martin J.</givenname>
				<surname>Dürst</surname>
			</person>
			<person>
				<givenname>Larry</givenname>
				<surname>Masinter</surname>
			</person>
			<person>
				<givenname>Jamie</givenname>
				<surname>Zawinski</surname>
			</person>
		</names>
		<date value="2008-01"/>
		<abstract>
			<richtext>
				<p>This document defines the format of Uniform Resource Identifiers (URI) to identify resources that are reached using Internet mail. It updates the syntax of 'mailto' URIs from RFC 2368 for better internationalization and compatibility with IRIs ([RFC3987]).</p>
			</richtext>
		</abstract>
		<howpublished>Internet Draft draft-duerst-mailto-bis-04</howpublished>
		<title type="sharef:primaryTitle">The 'mailto' URI Scheme</title>
		<field type="bibtex:topic">uri[0.8]</field>
		<field type="bibtex:updates">rfc2368</field>
	</reference>
	<reference name="due07" src="bibtex:misc" src-info="bibtex:line-39545" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Martin J.</givenname>
				<surname>Dürst</surname>
			</person>
			<person>
				<givenname>Michel</givenname>
				<surname>Suignard</surname>
			</person>
		</names>
		<date value="2007-12"/>
		<abstract>
			<richtext>
				<p>This document defines a new protocol element, the Internationalized Resource Identifier (IRI), as a complement to the Uniform Resource Identifier (URI). An IRI is a sequence of characters from the Universal Character Set (Unicode/ISO 10646). A mapping from IRIs to URIs is defined, which means that IRIs can be used instead of URIs, where appropriate, to identify resources. The approach of defining a new protocol element was chosen instead of extending or changing the definition of URIs. This was done in order to allow a clear distinction and to avoid incompatibilities with existing software. Guidelines are provided for the use and deployment of IRIs in various protocols, formats, and software components that currently deal with URIs.</p>
			</richtext>
		</abstract>
		<howpublished>Internet Draft draft-duerst-iri-bis-02</howpublished>
		<title type="sharef:primaryTitle">Internationalized Resource Identifiers (IRIs)</title>
		<field type="bibtex:topic">iri[1] leiri[1]</field>
		<field type="bibtex:updates">rfc3987</field>
	</reference>
	<reference name="gre06" src="bibtex:misc" src-info="bibtex:line-39556" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Joe</givenname>
				<surname>Gregorio</surname>
			</person>
			<person>
				<givenname>Bill</givenname>
				<surname link="de">Hóra</surname>
			</person>
		</names>
		<date value="2007-07"/>
		<abstract>
			<richtext>
				<p>The Atom Publishing Protocol (APP) is an application-level protocol for publishing and editing Web resources. The protocol is based on HTTP transport of Atom-formatted representations. The Atom format is documented in the Atom Syndication Format.</p>
			</richtext>
		</abstract>
		<howpublished>Internet Draft draft-ietf-atompub-protocol-17</howpublished>
		<title type="sharef:primaryTitle">The Atom Publishing Protocol</title>
		<field type="bibtex:topic">atompub[1] atom[0.9]</field>
		<identifier type="sharef:uri">https://datatracker.ietf.org/drafts/draft-ietf-atompub-protocol/</identifier>
	</reference>
	<reference name="bry09" src="bibtex:misc" src-info="bibtex:line-39567" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Anthony</givenname>
				<surname>Bryan</surname>
			</person>
			<person>
				<givenname>Tatsuhiro</givenname>
				<surname>Tsujikawa</surname>
			</person>
			<person>
				<givenname>Neil</givenname>
				<surname>McNab</surname>
			</person>
			<person>
				<givenname>Peter</givenname>
				<surname>Poeml</surname>
			</person>
		</names>
		<date value="2009-12"/>
		<abstract>
			<richtext>
				<p>This document specifies Metalink, an XML-based download description format. Metalink describes download locations (mirrors), checksums, and other information. Clients can transparently use this information to reliably transfer files.</p>
			</richtext>
		</abstract>
		<howpublished>Internet Draft draft-bryan-metalink-24</howpublished>
		<title type="sharef:primaryTitle">The Metalink Download Description Format</title>
		<field type="bibtex:topic">metalink[1]</field>
		<identifier type="sharef:uri">https://datatracker.ietf.org/drafts/draft-bryan-metalink/</identifier>
	</reference>
	<reference name="ham09a" src="bibtex:misc" src-info="bibtex:line-39578" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Eran</givenname>
				<surname>Hammer-Lahav</surname>
			</person>
		</names>
		<date value="2009-03"/>
		<abstract>
			<richtext>
				<p>This memo describes LRDD (pronounced 'lard'), a process for obtaining information about a resource identified by a URI. The 'information about a resource', a resource descriptor, provides machine-readable information that aims to increase interoperability and enhance the interaction with the resource. This memo only defines the process for locating and obtaining the descriptor, but leaves the descriptor format and its interpretation out of scope.</p>
			</richtext>
		</abstract>
		<howpublished>Internet Draft draft-hammer-discovery-03</howpublished>
		<title type="sharef:primaryTitle">Link-based Resource Descriptor Discovery</title>
		<field type="bibtex:topic">lrrd[1]</field>
		<identifier type="sharef:uri">https://datatracker.ietf.org/drafts/draft-hammer-discovery/</identifier>
	</reference>
	<reference name="not08b" src="bibtex:misc" src-info="bibtex:line-39589" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Mark</givenname>
				<surname>Nottingham</surname>
			</person>
			<person>
				<givenname>Dave</givenname>
				<surname>Beckett</surname>
			</person>
		</names>
		<date value="2008-06"/>
		<abstract>
			<richtext>
				<p>This specification describes AtomTriples, a set of Atom extension elements for embedding RDF statements in Atom documents (both element and feed), and declaring how they can be derived from existing content.</p>
			</richtext>
		</abstract>
		<howpublished>Internet Draft draft-nottingham-atomtriples-00</howpublished>
		<title type="sharef:primaryTitle">AtomTriples: Embedding RDF Statements in Atom</title>
		<field type="bibtex:topic">atom[0.8] rdf[0.8]</field>
		<identifier type="sharef:uri">https://datatracker.ietf.org/drafts/draft-nottingham-atomtriples</identifier>
	</reference>
	<reference name="not09a" src="bibtex:misc" src-info="bibtex:line-39600" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Mark</givenname>
				<surname>Nottingham</surname>
			</person>
			<person>
				<givenname>Eran</givenname>
				<surname>Hammer-Lahav</surname>
			</person>
		</names>
		<date value="2009-07"/>
		<abstract>
			<richtext>
				<p>This memo defines a path prefix for "well-known locations" in URIs.</p>
			</richtext>
		</abstract>
		<howpublished>Internet Draft draft-nottingham-site-meta-02</howpublished>
		<title type="sharef:primaryTitle">Defining Well-Known URIs</title>
		<identifier type="sharef:uri">https://datatracker.ietf.org/drafts/draft-nottingham-site-meta/</identifier>
	</reference>
	<reference name="sne09c" src="bibtex:misc" src-info="bibtex:line-39610" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>James M.</givenname>
				<surname>Snell</surname>
			</person>
		</names>
		<date value="2009-06"/>
		<abstract>
			<richtext>
				<p>This document specifies a format for packaging multiple, independent HTTP requests into a single multipart payload.</p>
			</richtext>
		</abstract>
		<howpublished>Internet Draft draft-snell-http-batch-00</howpublished>
		<title type="sharef:primaryTitle">HTTP Multipart Batched Request Format</title>
		<field type="bibtex:topic">http[0.9]</field>
		<identifier type="sharef:uri">https://datatracker.ietf.org/drafts/draft-snell-http-batch/</identifier>
	</reference>
	<reference name="dus09" src="bibtex:misc" src-info="bibtex:line-39621" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Lisa</givenname>
				<surname>Dusseault</surname>
			</person>
			<person>
				<givenname>James M.</givenname>
				<surname>Snell</surname>
			</person>
		</names>
		<date value="2009-10"/>
		<abstract>
			<richtext>
				<p>Several applications extending the Hypertext Transfer Protocol (HTTP) require a feature to do partial resource modification. The existing HTTP PUT method only allows a complete replacement of a document. This proposal adds a new HTTP method, PATCH, to modify an existing HTTP resource.</p>
			</richtext>
		</abstract>
		<howpublished>Internet Draft draft-dusseault-http-patch-15</howpublished>
		<title type="sharef:primaryTitle">PATCH Method for HTTP</title>
		<field type="bibtex:topic">http[0.9]</field>
		<identifier type="sharef:uri">https://datatracker.ietf.org/drafts/draft-dusseault-http-patch/</identifier>
	</reference>
	<reference name="not08" src="bibtex:misc" src-info="bibtex:line-39632" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Mark</givenname>
				<surname>Nottingham</surname>
			</person>
		</names>
		<date value="2010-05"/>
		<abstract>
			<richtext>
				<p>This document specifies relation types for Web links, and defines a registry for them. It also defines how to send such links in HTTP headers with the Link header-field.</p>
			</richtext>
		</abstract>
		<howpublished>Internet Draft draft-nottingham-http-link-header-10</howpublished>
		<title type="sharef:primaryTitle">Web Linking</title>
		<field type="bibtex:topic">http[0.9] atompub[0.8] atom[0.8] html[0.8]</field>
		<identifier type="sharef:uri">https://datatracker.ietf.org/drafts/draft-nottingham-http-link-header/</identifier>
	</reference>
	<reference name="bro09" src="bibtex:misc" src-info="bibtex:line-39643" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Al</givenname>
				<surname>Brown</surname>
			</person>
			<person>
				<givenname>Geoffrey</givenname>
				<surname>Clemm</surname>
			</person>
			<person>
				<givenname>Julian F.</givenname>
				<surname>Reschke</surname>
			</person>
		</names>
		<date value="2010-01"/>
		<abstract>
			<richtext>
				<p>This specification defines a set of link relation types that may be used on Web resources for navigation between a resource and and other resources related to version control, such as past versions and working copies.</p>
			</richtext>
		</abstract>
		<howpublished>Internet Draft draft-brown-versioning-link-relations-07</howpublished>
		<title type="sharef:primaryTitle">Link Relation Types for Simple Version Navigation between Web Resources</title>
		<field type="bibtex:topic">http[0.9] atompub[0.8] atom[0.8] html[0.8]</field>
		<identifier type="sharef:uri">https://datatracker.ietf.org/drafts/draft-brown-versioning-link-relations/</identifier>
	</reference>
	<reference name="not07b" src="bibtex:misc" src-info="bibtex:line-39654" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Mark</givenname>
				<surname>Nottingham</surname>
			</person>
		</names>
		<date value="2007-12"/>
		<abstract>
			<richtext>
				<p>The Feed Item Query Language is a simple but flexible, URI-friendly syntax for expressing filters across the entries in a Web feed. It also specifies a mechanism to allow feeds to indicate what types of queries are supported.</p>
			</richtext>
		</abstract>
		<howpublished>Internet Draft draft-nottingham-atompub-fiql-00</howpublished>
		<title type="sharef:primaryTitle">FIQL: The Feed Item Query Language</title>
		<field type="bibtex:topic">atompub[0.9] atom[0.9] fiql[1]</field>
		<identifier type="sharef:uri">https://datatracker.ietf.org/drafts/draft-nottingham-atompub-fiql/</identifier>
	</reference>
	<reference name="not07" src="bibtex:misc" src-info="bibtex:line-39665" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Mark</givenname>
				<surname>Nottingham</surname>
			</person>
		</names>
		<date value="2007-06"/>
		<abstract>
			<richtext>
				<p>This specification defines three types of syndicated Web feeds that enable publication of entries across one or more feed documents. This includes "paged" feeds for piecemeal access, "archived" feeds that allow reconstruction of the feed's contents, and feeds that are explicitly "complete".</p>
			</richtext>
		</abstract>
		<howpublished>Internet Draft draft-nottingham-atompub-feed-history-11</howpublished>
		<title type="sharef:primaryTitle">Feed Paging and Archiving</title>
		<field type="bibtex:topic">atompub[0.9] atom[0.9]</field>
		<identifier type="sharef:uri">https://datatracker.ietf.org/drafts/draft-nottingham-atompub-feed-history</identifier>
	</reference>
	<reference name="sai07" src="bibtex:misc" src-info="bibtex:line-39676" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Peter</givenname>
				<surname>Saint-Andre</surname>
			</person>
			<person>
				<givenname>Joe</givenname>
				<surname>Hildebrand</surname>
			</person>
			<person>
				<givenname>Bob</givenname>
				<surname>Wyman</surname>
			</person>
		</names>
		<date value="2007-10"/>
		<abstract>
			<richtext>
				<p>This memo describes a method for notifying interested parties about changes in syndicated information encapsulated in the Atom feed format, where such notifications are delivered via an extension to the Extensible Messaging and Presence Protocol (XMPP) for publish- subscribe functionality.</p>
			</richtext>
		</abstract>
		<howpublished>Internet Draft draft-saintandre-atompub-notify-06</howpublished>
		<title type="sharef:primaryTitle">Transporting Atom Notifications over the Extensible Messaging and Presence Protocol (XMPP)</title>
		<field type="bibtex:topic">xmpp[0.9] atom[0.9]</field>
		<identifier type="sharef:uri">https://datatracker.ietf.org/drafts/draft-saintandre-atompub-notify/</identifier>
	</reference>
	<reference name="meh09a" src="bibtex:misc" src-info="bibtex:line-39687" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Nikunj R.</givenname>
				<surname>Mehta</surname>
			</person>
		</names>
		<date value="2009-06"/>
		<abstract>
			<richtext>
				<p>This specification defines mechanisms for in-lining representations of linked resources in Atom documents.</p>
			</richtext>
		</abstract>
		<howpublished>Internet Draft draft-mehta-atom-inline-00</howpublished>
		<title type="sharef:primaryTitle">In-lining Extensions for Atom</title>
		<field type="bibtex:topic">atom[0.9]</field>
		<identifier type="sharef:uri">https://datatracker.ietf.org/drafts/draft-mehta-atom-inline/</identifier>
	</reference>
	<reference name="div09a" src="bibtex:misc" src-info="bibtex:line-39698" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Colm</givenname>
				<surname>Divilly</surname>
			</person>
			<person>
				<givenname>Nikunj R.</givenname>
				<surname>Mehta</surname>
			</person>
		</names>
		<date value="2009-05"/>
		<abstract>
			<richtext>
				<p>This specification defines a mechanism to create and remove AtomPub collections using the AtomPub protocol as well as to express hierarchies of feeds within the Atom Syndication Format.</p>
			</richtext>
		</abstract>
		<howpublished>Internet Draft draft-divilly-atompub-hierarchy-00</howpublished>
		<title type="sharef:primaryTitle">Hierarchy Extensions to Atom Feeds</title>
		<field type="bibtex:topic">atom[0.9]</field>
		<identifier type="sharef:uri">https://datatracker.ietf.org/drafts/draft-divilly-atompub-hierarchy/</identifier>
	</reference>
	<reference name="div09b" src="bibtex:misc" src-info="bibtex:line-39709" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Colm</givenname>
				<surname>Divilly</surname>
			</person>
			<person>
				<givenname>Nikunj R.</givenname>
				<surname>Mehta</surname>
			</person>
		</names>
		<date value="2009-06"/>
		<abstract>
			<richtext>
				<p>This specification defines mechanisms for hierarchical navigation among Atom feeds and entries.</p>
			</richtext>
		</abstract>
		<howpublished>Internet Draft draft-divilly-atom-hierarchy-02</howpublished>
		<title type="sharef:primaryTitle">Hierarchy Extensions for Atom</title>
		<field type="bibtex:topic">atom[0.9]</field>
		<field type="bibtex:updates">div09a</field>
		<identifier type="sharef:uri">https://datatracker.ietf.org/drafts/draft-divilly-atom-hierarchy/</identifier>
	</reference>
	<reference name="div09c" src="bibtex:misc" src-info="bibtex:line-39721" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Colm</givenname>
				<surname>Divilly</surname>
			</person>
			<person>
				<givenname>Nikunj R.</givenname>
				<surname>Mehta</surname>
			</person>
		</names>
		<date value="2009-05"/>
		<abstract>
			<richtext>
				<p>This document recommends best practices for discovering AtomPub Collection resources as applicable to various content representation formats.</p>
			</richtext>
		</abstract>
		<howpublished>Internet Draft draft-divilly-atompub-discovery-00</howpublished>
		<title type="sharef:primaryTitle">AtomPub Guidelines for Collection Discovery</title>
		<field type="bibtex:topic">atom[0.9] atompub[0.9]</field>
		<identifier type="sharef:uri">https://datatracker.ietf.org/drafts/draft-divilly-atompub-discovery/</identifier>
	</reference>
	<reference name="sne09b" src="bibtex:misc" src-info="bibtex:line-39732" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Geoffrey</givenname>
				<surname>Sneddon</surname>
			</person>
		</names>
		<date value="2009-05"/>
		<abstract>
			<richtext>
				<p>This document specifies a method of using the Atom Syndication Format as an export format.</p>
			</richtext>
		</abstract>
		<howpublished>Internet Draft draft-sneddon-atom-export-01</howpublished>
		<title type="sharef:primaryTitle">Atom Export Format</title>
		<field type="bibtex:topic">atom[0.9]</field>
		<identifier type="sharef:uri">https://datatracker.ietf.org/drafts/draft-sneddon-atom-export/</identifier>
	</reference>
	<reference name="sne09a" src="bibtex:misc" src-info="bibtex:line-39743" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>James M.</givenname>
				<surname>Snell</surname>
			</person>
		</names>
		<date value="2010-12"/>
		<abstract>
			<richtext>
				<p>This specification adds mechanisms to the Atom Syndication Format which Atom Feed publishers can use to explicitly identify Atom entries that have been removed from an Atom feed.</p>
			</richtext>
		</abstract>
		<howpublished>Internet Draft draft-snell-atompub-tombstones-12</howpublished>
		<title type="sharef:primaryTitle">The Atom "deleted-entry" Element</title>
		<field type="bibtex:topic">atom[0.9]</field>
		<identifier type="sharef:uri">https://datatracker.ietf.org/drafts/draft-snell-atompub-tombstones/</identifier>
	</reference>
	<reference name="sne07a" src="bibtex:misc" src-info="bibtex:line-39754" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>James M.</givenname>
				<surname>Snell</surname>
			</person>
		</names>
		<date value="2007-10"/>
		<abstract>
			<richtext>
				<p>This document adds a new attribute to the Atom Syndication Format used to indicate the base directionality of directionally-neutral characters.</p>
			</richtext>
		</abstract>
		<howpublished>Internet Draft draft-snell-atompub-bidi-05</howpublished>
		<title type="sharef:primaryTitle">Atom Bidirectional Attribute</title>
		<field type="bibtex:topic">atom[0.9]</field>
		<identifier type="sharef:uri">https://datatracker.ietf.org/drafts/draft-snell-atompub-bidi/</identifier>
	</reference>
	<reference name="gar09" src="bibtex:misc" src-info="bibtex:line-39765" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Lars Marius</givenname>
				<surname>Garshol</surname>
			</person>
		</names>
		<date value="2009-11"/>
		<abstract>
			<richtext>
				<p>This document describes a media type (application/xtm+xml) for serialization of Topic Maps into Extensible Markup Language (XML). Topic Maps is a technology for encoding knowledge and connecting this encoded knowledge to relevant information resources. Topic maps are organized around topics, which represent subjects of discourse; associations, representing relationships between the subjects; and occurrences, which connect the subjects to pertinent information resources. Topic Maps is an ISO standard (ISO 13250).</p>
			</richtext>
		</abstract>
		<howpublished>Internet Draft draft-garshol-applicationxtmxml-00</howpublished>
		<title type="sharef:primaryTitle">application/xtm+xml Media Type Registration</title>
		<field type="bibtex:topic">xtm[1] topicmaps[0.9]</field>
		<identifier type="sharef:uri">https://datatracker.ietf.org/drafts/draft-garshol-applicationxtmxml/</identifier>
	</reference>
	<reference name="sne07c" src="bibtex:misc" src-info="bibtex:line-39776" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>James M.</givenname>
				<surname>Snell</surname>
			</person>
		</names>
		<date value="2008-02"/>
		<abstract>
			<richtext>
				<p>This specification defines a new HTTP header that can be used by a client to request that certain behaviors be implemented by a server while processing a request.</p>
			</richtext>
		</abstract>
		<howpublished>Internet Draft draft-snell-http-prefer-02</howpublished>
		<title type="sharef:primaryTitle">Prefer Header for HTTP</title>
		<field type="bibtex:topic">http[0.9]</field>
		<identifier type="sharef:uri">https://datatracker.ietf.org/drafts/draft-snell-http-prefer/</identifier>
	</reference>
	<reference name="sne06" src="bibtex:misc" src-info="bibtex:line-39787" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>James M.</givenname>
				<surname>Snell</surname>
			</person>
			<person>
				<givenname>Andreas</givenname>
				<surname>Sewe</surname>
			</person>
		</names>
		<date value="2006-08"/>
		<abstract>
			<richtext>
				<p>This document defines an Atom Syndication Format extension for numerically ranking entries within a syndication feed.</p>
			</richtext>
		</abstract>
		<howpublished>Internet Draft draft-snell-atompub-feed-index-10</howpublished>
		<title type="sharef:primaryTitle">Atom Ranking Extensions</title>
		<field type="bibtex:topic">atom[0.9]</field>
		<identifier type="sharef:uri">https://datatracker.ietf.org/drafts/draft-snell-atompub-feed-index/</identifier>
	</reference>
	<reference name="sne07b" src="bibtex:misc" src-info="bibtex:line-39798" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>James M.</givenname>
				<surname>Snell</surname>
			</person>
		</names>
		<date value="2007-10"/>
		<abstract>
			<richtext>
				<p>This document introduces extensions to the Atom Publishing Protocol Service Document format for expressing metadata about the behaviors, functions and capabilities supported by an Atom Publishing Protocol collection.</p>
			</richtext>
		</abstract>
		<howpublished>Internet Draft draft-snell-atompub-feature-12</howpublished>
		<title type="sharef:primaryTitle">Atom Publishing Protocol Feature Discovery</title>
		<field type="bibtex:topic">atompub[0.9] atom[0.9]</field>
		<identifier type="sharef:uri">https://datatracker.ietf.org/drafts/draft-snell-atompub-feature/</identifier>
	</reference>
	<reference name="cro07" src="bibtex:misc" src-info="bibtex:line-39809" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Adrien</givenname>
				<surname link="de">Croy</surname>
			</person>
		</names>
		<date value="2007-10"/>
		<abstract>
			<richtext>
				<p>This document specifies extensions to HTTP to allow progress messages for user-agents during lengthy transactions.</p>
			</richtext>
		</abstract>
		<howpublished>Internet Draft draft-decroy-http-progress-03</howpublished>
		<title type="sharef:primaryTitle">Progress notifications for HTTP</title>
		<field type="bibtex:topic">http[0.9]</field>
		<identifier type="sharef:uri">https://datatracker.ietf.org/drafts/draft-decroy-http-progress/</identifier>
	</reference>
	<reference name="mea00" src="bibtex:misc" src-info="bibtex:line-39820" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Michael</givenname>
				<surname>Mealling</surname>
			</person>
		</names>
		<date value="2000-07"/>
		<howpublished>Internet Draft</howpublished>
		<title type="sharef:primaryTitle">Dynamic Delegation Discovery System (DDDS)</title>
		<field type="bibtex:topic">ddds[1]</field>
	</reference>
	<reference name="kri99" src="bibtex:misc" src-info="bibtex:line-39829" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>David M.</givenname>
				<surname>Kristol</surname>
			</person>
			<person>
				<givenname>Lou</givenname>
				<surname>Montulli</surname>
			</person>
		</names>
		<date value="1999-08"/>
		<howpublished>Internet Draft</howpublished>
		<title type="sharef:primaryTitle">HTTP State Management Mechanism</title>
		<field type="bibtex:topic">http[0.8] cookie[1]</field>
		<field type="bibtex:updates">cookie</field>
	</reference>
	<reference name="pop00" src="bibtex:misc" src-info="bibtex:line-39839" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Nicolas</givenname>
				<surname>Popp</surname>
			</person>
			<person>
				<givenname>Michael</givenname>
				<surname>Mealling</surname>
			</person>
			<person>
				<givenname>Marshall</givenname>
				<surname>Moseley</surname>
			</person>
		</names>
		<date value="2000-06"/>
		<howpublished>Internet Draft</howpublished>
		<title type="sharef:primaryTitle">CNRP Protocol Specification</title>
		<field type="bibtex:topic">cnrp[1]</field>
	</reference>
	<reference name="box99" src="bibtex:misc" src-info="bibtex:line-39848" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Don</givenname>
				<surname>Box</surname>
			</person>
			<person>
				<givenname>Gopal</givenname>
				<surname>Kavivaya</surname>
			</person>
			<person>
				<givenname>Andrew</givenname>
				<surname>Layman</surname>
			</person>
			<person>
				<givenname>Satish</givenname>
				<surname>Thatte</surname>
			</person>
			<person>
				<givenname>Dave</givenname>
				<surname>Winer</surname>
			</person>
		</names>
		<date value="1999-11"/>
		<howpublished>Internet Draft draft-box-http-soap-01</howpublished>
		<title type="sharef:primaryTitle">SOAP: Simple Object Access Protocol</title>
		<field type="bibtex:topic">soap[1]</field>
	</reference>
	<reference name="fry99a" src="bibtex:misc" src-info="bibtex:line-39857" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Henrik</givenname>
				<surname>Frystyk Nielsen</surname>
			</person>
			<person>
				<givenname>Paul J.</givenname>
				<surname>Leach</surname>
			</person>
			<person>
				<givenname>Scott D.</givenname>
				<surname>Lawrence</surname>
			</person>
		</names>
		<date value="1999-05"/>
		<howpublished>Internet Draft</howpublished>
		<title type="sharef:primaryTitle">HTTP Extension Framework</title>
		<field type="bibtex:topic">httpef[1]</field>
		<field type="bibtex:updates">pep</field>
	</reference>
	<reference name="moh98" src="bibtex:misc" src-info="bibtex:line-39867" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>G.</givenname>
				<surname>Mohr</surname>
			</person>
			<person>
				<givenname>Sonu</givenname>
				<surname>Aggarwal</surname>
			</person>
			<person>
				<givenname>Mark</givenname>
				<surname>Day</surname>
			</person>
			<person>
				<givenname>A.</givenname>
				<surname>Houri</surname>
			</person>
			<person>
				<givenname>Y.</givenname>
				<surname>Kohda</surname>
			</person>
			<person>
				<givenname>D.</givenname>
				<surname>Marvit</surname>
			</person>
		</names>
		<date value="1998-08"/>
		<howpublished>Internet Draft</howpublished>
		<title type="sharef:primaryTitle">PIP-DEMO: An Interoperable Presence Information Protocol</title>
		<field type="bibtex:topic">pip[1]</field>
	</reference>
	<reference name="mea98a" src="bibtex:misc" src-info="bibtex:line-39876" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Michael</givenname>
				<surname>Mealling</surname>
			</person>
			<person>
				<givenname>Ron</givenname>
				<surname>Daniel</surname>
			</person>
		</names>
		<date value="1998-03"/>
		<howpublished>Internet Draft, Uniform resource names working group</howpublished>
		<field type="bibtex:index">URN, URI</field>
		<title type="sharef:primaryTitle">URI Resolution Services Necessary for URN Resolution</title>
	</reference>
	<reference name="mea98b" src="bibtex:misc" src-info="bibtex:line-39885" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Michael</givenname>
				<surname>Mealling</surname>
			</person>
		</names>
		<date value="1998-06"/>
		<howpublished>Internet Draft, Uniform resource names working group</howpublished>
		<field type="bibtex:index">DNS, URN</field>
		<title type="sharef:primaryTitle">Assignment Procedures for the URI Resolution using DNS</title>
	</reference>
	<reference name="dai98" src="bibtex:misc" src-info="bibtex:line-39894" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Leslie L.</givenname>
				<surname>Daigle</surname>
			</person>
			<person>
				<givenname>Dirk-Willem</givenname>
				<surname link="van">Gulik</surname>
			</person>
			<person>
				<givenname>Renato</givenname>
				<surname>Iannella</surname>
			</person>
			<person>
				<givenname>Patrik</givenname>
				<surname>Faltstrom</surname>
			</person>
		</names>
		<date value="1998-03"/>
		<howpublished>Internet Draft, Uniform resource names working group</howpublished>
		<title type="sharef:primaryTitle">URN Namespace Definition Mechanisms</title>
		<field type="bibtex:topic">urn[0.9]</field>
	</reference>
	<reference name="dcom" src="bibtex:misc" src-info="bibtex:line-39903" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Nat</givenname>
				<surname>Brown</surname>
			</person>
			<person>
				<givenname>Charlie</givenname>
				<surname>Kindel</surname>
			</person>
		</names>
		<date value="1998-01"/>
		<howpublished>Internet Draft, Network working group</howpublished>
		<field type="bibtex:index">DCOM</field>
		<title type="sharef:primaryTitle">Distributed Component Object Model Protocol — DCOM/1.0</title>
	</reference>
	<reference name="https" src="bibtex:misc" src-info="bibtex:line-39912" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Eric</givenname>
				<surname>Rescorla</surname>
			</person>
		</names>
		<date value="1999-10"/>
		<howpublished>Internet Draft, TLS working group</howpublished>
		<title type="sharef:primaryTitle">HTTP over TLS</title>
		<field type="bibtex:topic">tls[0.9] http[0.9] https[1]</field>
	</reference>
	<reference name="tls" src="bibtex:misc" src-info="bibtex:line-39921" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Tim</givenname>
				<surname>Dierks</surname>
			</person>
			<person>
				<givenname>Christopher</givenname>
				<surname>Allen</surname>
			</person>
		</names>
		<date value="1997-11"/>
		<howpublished>Internet Draft, TLS working group</howpublished>
		<field type="bibtex:index">SSL, TLS</field>
		<title type="sharef:primaryTitle">The TLS Protocol Version 1.0</title>
	</reference>
	<reference name="cookie" src="bibtex:misc" src-info="bibtex:line-39930" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>David M.</givenname>
				<surname>Kristol</surname>
			</person>
			<person>
				<givenname>Lou</givenname>
				<surname>Montulli</surname>
			</person>
		</names>
		<date value="1998-02"/>
		<howpublished>Internet Draft, HTTP working group</howpublished>
		<title type="sharef:primaryTitle">HTTP State Management Mechanism</title>
		<field type="bibtex:topic">http[0.8] cookie[1]</field>
	</reference>
	<reference name="smime1" src="bibtex:misc" src-info="bibtex:line-39939" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Steven</givenname>
				<surname>Dusse</surname>
			</person>
			<person>
				<givenname>Paul E.</givenname>
				<surname>Hoffman</surname>
			</person>
			<person>
				<givenname>Blake</givenname>
				<surname>Ramsdell</surname>
			</person>
			<person>
				<givenname>Jeff</givenname>
				<surname>Weinstein</surname>
			</person>
		</names>
		<date value="1997-11"/>
		<howpublished>Internet Draft</howpublished>
		<title type="sharef:primaryTitle">S/MIME Version 2 Certificate Handling</title>
		<field type="bibtex:topic">smime[1]</field>
	</reference>
	<reference name="smime2" src="bibtex:misc" src-info="bibtex:line-39948" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Steven</givenname>
				<surname>Dusse</surname>
			</person>
			<person>
				<givenname>Paul E.</givenname>
				<surname>Hoffman</surname>
			</person>
			<person>
				<givenname>Blake</givenname>
				<surname>Ramsdell</surname>
			</person>
			<person>
				<givenname>Laurence</givenname>
				<surname>Lundblade</surname>
			</person>
			<person>
				<givenname>Lisa</givenname>
				<surname>Repka</surname>
			</person>
		</names>
		<date value="1997-11"/>
		<howpublished>Internet Draft</howpublished>
		<title type="sharef:primaryTitle">S/MIME Version 2 Message Specification</title>
		<field type="bibtex:topic">smime[1]</field>
	</reference>
	<reference name="cms" src="bibtex:misc" src-info="bibtex:line-39957" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Russell</givenname>
				<surname>Housley</surname>
			</person>
		</names>
		<date value="1998-03"/>
		<howpublished>Internet Draft</howpublished>
		<title type="sharef:primaryTitle">Cryptographic Message Syntax</title>
		<field type="bibtex:topic">cms[1]</field>
	</reference>
	<reference name="luo98" src="bibtex:misc" src-info="bibtex:line-39966" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Ari</givenname>
				<surname>Luotonen</surname>
			</person>
		</names>
		<date value="1998-08"/>
		<howpublished>Internet Draft</howpublished>
		<title type="sharef:primaryTitle">Tunneling TCP based protocols through Web proxy servers</title>
	</reference>
	<reference name="xuri" src="bibtex:misc" src-info="bibtex:line-39974" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Tim</givenname>
				<surname>Berners-Lee</surname>
			</person>
			<person>
				<givenname>Roy Thomas</givenname>
				<surname>Fielding</surname>
			</person>
			<person>
				<givenname>Larry</givenname>
				<surname>Masinter</surname>
			</person>
		</names>
		<date value="1998-06"/>
		<howpublished>Work in progress</howpublished>
		<title type="sharef:primaryTitle">Uniform Resource Identifiers (URI): Generic Syntax and Semantics</title>
	</reference>
	<reference name="ssl30" src="bibtex:misc" src-info="bibtex:line-39982" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Alan O.</givenname>
				<surname>Freier</surname>
			</person>
			<person>
				<givenname>Philip</givenname>
				<surname>Karlton</surname>
			</person>
			<person>
				<givenname>Paul C.</givenname>
				<surname>Kocher</surname>
			</person>
		</names>
		<date value="1996-11"/>
		<howpublished>Internet Draft, Transport Layer Security Working Group</howpublished>
		<title type="sharef:primaryTitle">The SSL Protocol — Version 3.0</title>
		<field type="bibtex:topic">ssl[1]</field>
	</reference>
	<reference name="sun97" src="bibtex:misc" src-info="bibtex:line-39991" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Sam X.</givenname>
				<surname>Sun</surname>
			</person>
		</names>
		<date value="1997-11"/>
		<howpublished>Internet Draft, Network Working Group</howpublished>
		<title type="sharef:primaryTitle">Handle System: A Persistent Global Naming Service — Overview and Syntax</title>
		<field type="bibtex:topic">handlesystem[1]</field>
	</reference>
	<reference name="elz97" src="bibtex:misc" src-info="bibtex:line-40000" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Robert</givenname>
				<surname>Elz</surname>
			</person>
			<person>
				<givenname>Randy</givenname>
				<surname>Bush</surname>
			</person>
		</names>
		<date value="1997-01"/>
		<howpublished>Internet Draft, Network Working Group</howpublished>
		<title type="sharef:primaryTitle">Clarifications to the DNS Specification</title>
	</reference>
	<reference name="igmpmib" src="bibtex:misc" src-info="bibtex:line-40008" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Keith</givenname>
				<surname>McCloghrie</surname>
			</person>
			<person>
				<givenname>Dino</givenname>
				<surname>Farinacci</surname>
			</person>
		</names>
		<date value="1994-07"/>
		<howpublished>Internet Draft, IDMR Working Group</howpublished>
		<title type="sharef:primaryTitle">Internet Group Management Protocol MIB</title>
	</reference>
	<reference name="ipmrmib" src="bibtex:misc" src-info="bibtex:line-40016" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Keith</givenname>
				<surname>McCloghrie</surname>
			</person>
			<person>
				<givenname>Dino</givenname>
				<surname>Farinacci</surname>
			</person>
		</names>
		<date value="1994-07"/>
		<howpublished>Internet Draft, IDMR Working Group</howpublished>
		<title type="sharef:primaryTitle">Internet Multicast Routing MIB</title>
	</reference>
	<reference name="pimmib" src="bibtex:misc" src-info="bibtex:line-40024" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Keith</givenname>
				<surname>McCloghrie</surname>
			</person>
			<person>
				<givenname>Dino</givenname>
				<surname>Farinacci</surname>
			</person>
		</names>
		<date value="1994-07"/>
		<howpublished>Internet Draft, IDMR Working Group</howpublished>
		<title type="sharef:primaryTitle">Protocol Independent Multicast MIB</title>
	</reference>
	<reference name="skip" src="bibtex:misc" src-info="bibtex:line-40032" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Ashar</givenname>
				<surname>Aziz</surname>
			</person>
			<person>
				<givenname>Tom</givenname>
				<surname>Markson</surname>
			</person>
			<person>
				<givenname>Hemma</givenname>
				<surname>Prafullchandra</surname>
			</person>
		</names>
		<date value="1996-08"/>
		<howpublished>Internet Draft</howpublished>
		<title type="sharef:primaryTitle">Simple Key-Management for Internet Protocols</title>
	</reference>
	<reference name="skipmc" src="bibtex:misc" src-info="bibtex:line-40040" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Ashar</givenname>
				<surname>Aziz</surname>
			</person>
			<person>
				<givenname>Tom</givenname>
				<surname>Markson</surname>
			</person>
			<person>
				<givenname>Hemma</givenname>
				<surname>Prafullchandra</surname>
			</person>
		</names>
		<date value="1996-08"/>
		<howpublished>Internet Draft</howpublished>
		<title type="sharef:primaryTitle">SKIP Extensions for IP Multicast</title>
	</reference>
	<reference name="shttp" src="bibtex:misc" src-info="bibtex:line-40048" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Eric</givenname>
				<surname>Rescorla</surname>
			</person>
			<person>
				<givenname>Allan M.</givenname>
				<surname>Schiffman</surname>
			</person>
		</names>
		<date value="1997-11"/>
		<howpublished>Internet Draft</howpublished>
		<title type="sharef:primaryTitle">The Secure HyperText Transfer Protocol</title>
		<field type="bibtex:topic">shttp[1]</field>
	</reference>
	<reference name="jsonschema" src="bibtex:misc" src-info="bibtex:line-40057" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Kris</givenname>
				<surname>Zyp</surname>
			</person>
		</names>
		<date value="2009-12"/>
		<abstract>
			<richtext>
				<p>JSON (JavaScript Object Notation) Schema defines the media type application/schema+json, a JSON based format for defining the structure of JSON data. JSON Schema provides a contract for what JSON data is required for a given application and how to interact with it. JSON Schema is intended to define validation, documentation, hyperlink navigation, and interaction control of JSON data.</p>
			</richtext>
		</abstract>
		<howpublished>Internet Draft draft-zyp-json-schema-01</howpublished>
		<title type="sharef:primaryTitle">A JSON Media Type for Describing the Structure and Meaning of JSON Documents</title>
		<field type="bibtex:topic">json[0.9] jsonschema[1]</field>
		<identifier type="sharef:uri">https://datatracker.ietf.org/drafts/draft-zyp-json-schema/</identifier>
	</reference>
	<reference name="sdpv2" src="bibtex:misc" src-info="bibtex:line-40068" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Mark J.</givenname>
				<surname>Handley</surname>
			</person>
			<person>
				<givenname>Van</givenname>
				<surname>Jacobson</surname>
			</person>
		</names>
		<date value="1996-11"/>
		<howpublished>Internet Draft, MMUSIC Working Group</howpublished>
		<field type="bibtex:index">SDP v2, RTP, SDAP</field>
		<title type="sharef:primaryTitle">SDP: Session Description Protocol</title>
	</reference>
	<reference name="confar" src="bibtex:misc" src-info="bibtex:line-40077" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Mark J.</givenname>
				<surname>Handley</surname>
			</person>
			<person>
				<givenname>Jon</givenname>
				<surname>Crowcroft</surname>
			</person>
			<person>
				<givenname>Carsten</givenname>
				<surname>Bormann</surname>
			</person>
		</names>
		<date value="1996-02"/>
		<howpublished>Internet Draft, MMUSIC Working Group</howpublished>
		<field type="bibtex:index">RSVP, HTTP, SMTP, SDP v2, RTP, RTCP, SDAP</field>
		<title type="sharef:primaryTitle">The Internet Multimedia Conferencing Architecture</title>
	</reference>
	<reference name="sccp" src="bibtex:misc" src-info="bibtex:line-40086" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Carsten</givenname>
				<surname>Bormann</surname>
			</person>
			<person>
				<givenname>Jörg</givenname>
				<surname>Ott</surname>
			</person>
			<person>
				<givenname>Christoph</givenname>
				<surname>Reichert</surname>
			</person>
		</names>
		<date value="1996-06"/>
		<howpublished>Internet Draft, MMUSIC Working Group</howpublished>
		<field type="bibtex:index">SCCP, SDP v2, RTP, T.120</field>
		<title type="sharef:primaryTitle">Simple Conference Control Protocol</title>
	</reference>
	<reference name="sip" src="bibtex:misc" src-info="bibtex:line-40095" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Mark J.</givenname>
				<surname>Handley</surname>
			</person>
			<person>
				<givenname>Eve M.</givenname>
				<surname>Schooler</surname>
			</person>
		</names>
		<date value="1996-02"/>
		<howpublished>Internet Draft, MMUSIC Working Group</howpublished>
		<field type="bibtex:index">SIP, SDP, SDAP</field>
		<title type="sharef:primaryTitle">Session Invitation Protocol</title>
	</reference>
	<reference name="scip" src="bibtex:misc" src-info="bibtex:line-40104" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Henning</givenname>
				<surname>Schulzrinne</surname>
			</person>
		</names>
		<date value="1996-02"/>
		<howpublished>Internet Draft, MMUSIC Working Group</howpublished>
		<title type="sharef:primaryTitle">Simple Conference Invitation Protocol</title>
		<field type="bibtex:topic">scip[1]</field>
	</reference>
	<reference name="sip2" src="bibtex:misc" src-info="bibtex:line-40113" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Mark J.</givenname>
				<surname>Handley</surname>
			</person>
			<person>
				<givenname>Henning</givenname>
				<surname>Schulzrinne</surname>
			</person>
			<person>
				<givenname>Eve M.</givenname>
				<surname>Schooler</surname>
			</person>
		</names>
		<date value="1996-12"/>
		<howpublished>Internet Draft, MMUSIC Working Group</howpublished>
		<title type="sharef:primaryTitle">Session Initiation Protocol</title>
		<field type="bibtex:topic">sip[1]</field>
	</reference>
	<reference name="mog97b" src="bibtex:misc" src-info="bibtex:line-40122" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Jeffrey C.</givenname>
				<surname>Mogul</surname>
			</person>
			<person>
				<givenname>Paul J.</givenname>
				<surname>Leach</surname>
			</person>
		</names>
		<date value="1997-01"/>
		<howpublished>Internet Draft, HTTP Working Group</howpublished>
		<title type="sharef:primaryTitle">Simple Hit-Metering for HTTP</title>
		<field type="bibtex:topic">http[0.9]</field>
	</reference>
	<reference name="pep" src="bibtex:misc" src-info="bibtex:line-40131" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Henrik</givenname>
				<surname>Frystyk Nielsen</surname>
			</person>
			<person>
				<givenname>Dan</givenname>
				<surname>Connolly</surname>
			</person>
			<person>
				<givenname>Rohit</givenname>
				<surname>Khare</surname>
			</person>
			<person>
				<givenname>Eric</givenname>
				<surname>Prud'Hommeaux</surname>
			</person>
		</names>
		<date value="1997-12"/>
		<howpublished>Internet Draft, HTTP Working Group</howpublished>
		<title type="sharef:primaryTitle">PEP — an Extension Mechanism for HTTP</title>
		<field type="bibtex:topic">pep[1]</field>
	</reference>
	<reference name="http113" src="bibtex:misc" src-info="bibtex:line-40140" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Roy Thomas</givenname>
				<surname>Fielding</surname>
			</person>
			<person>
				<givenname>Jim</givenname>
				<surname>Gettys</surname>
			</person>
			<person>
				<givenname>Jeffrey C.</givenname>
				<surname>Mogul</surname>
			</person>
			<person>
				<givenname>Larry</givenname>
				<surname>Masinter</surname>
			</person>
			<person>
				<givenname>Paul J.</givenname>
				<surname>Leach</surname>
			</person>
			<person>
				<givenname>Henrik</givenname>
				<surname>Frystyk Nielsen</surname>
			</person>
			<person>
				<givenname>Tim</givenname>
				<surname>Berners-Lee</surname>
			</person>
		</names>
		<date value="1998-03"/>
		<howpublished>Internet Draft, HTTP Working Group</howpublished>
		<field type="bibtex:index">HTTP, HTTP/1.1</field>
		<title type="sharef:primaryTitle">Hypertext Transfer Protocol — HTTP/1.1</title>
	</reference>
	<reference name="http111" src="bibtex:misc" src-info="bibtex:line-40149" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Roy Thomas</givenname>
				<surname>Fielding</surname>
			</person>
			<person>
				<givenname>Jim</givenname>
				<surname>Gettys</surname>
			</person>
			<person>
				<givenname>Jeffrey C.</givenname>
				<surname>Mogul</surname>
			</person>
			<person>
				<givenname>Larry</givenname>
				<surname>Masinter</surname>
			</person>
			<person>
				<givenname>Paul J.</givenname>
				<surname>Leach</surname>
			</person>
			<person>
				<givenname>Henrik</givenname>
				<surname>Frystyk Nielsen</surname>
			</person>
			<person>
				<givenname>Tim</givenname>
				<surname>Berners-Lee</surname>
			</person>
		</names>
		<date value="1997-11"/>
		<howpublished>Internet Draft, HTTP Working Group</howpublished>
		<field type="bibtex:index">HTTP, HTTP/1.1</field>
		<title type="sharef:primaryTitle">Hypertext Transfer Protocol — HTTP/1.1</title>
	</reference>
	<reference name="bur99" src="bibtex:misc" src-info="bibtex:line-40158" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>David</givenname>
				<surname>Burdett</surname>
			</person>
		</names>
		<date value="1999-10"/>
		<howpublished>Internet Draft</howpublished>
		<title type="sharef:primaryTitle">Internet Open Trading Protocol (IOTP) — Version 1.0</title>
		<field type="bibtex:topic">iotp[1]</field>
	</reference>
	<reference name="eas99" src="bibtex:misc" src-info="bibtex:line-40167" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Donald E.</givenname>
				<surname>Eastlake</surname>
			</person>
			<person>
				<givenname>Chris J.</givenname>
				<surname>Smith</surname>
			</person>
			<person>
				<givenname>David M.</givenname>
				<surname>Soroka</surname>
			</person>
		</names>
		<date value="1999-08"/>
		<howpublished>Internet Draft</howpublished>
		<field type="bibtex:index">HTTP, MIME</field>
		<title type="sharef:primaryTitle">HTTP MIME Type Handler Detection</title>
	</reference>
	<reference name="jsr005" src="bibtex:misc" src-info="bibtex:line-40180" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Rajiv</givenname>
				<surname>Mordani</surname>
			</person>
		</names>
		<date value="2000-03"/>
		<abstract>
			<richtext>
				<p>The Java API for XML Parsing (JAXP) allows developers to easily use XML Parsers in their applications via the industry standard SAX and DOM APIs.</p>
			</richtext>
		</abstract>
		<howpublished>Java Specification Request (JSR) 5</howpublished>
		<title type="sharef:primaryTitle">XML Parsing Specification</title>
		<field type="bibtex:topic">jaxp[1]</field>
		<identifier type="sharef:uri">http://www.jcp.org/en/jsr/detail?id=5</identifier>
	</reference>
	<reference name="jsr031" src="bibtex:misc" src-info="bibtex:line-40191" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Joe</givenname>
				<surname>Fialli</surname>
			</person>
			<person>
				<givenname>Sekhar</givenname>
				<surname>Vajjhala</surname>
			</person>
		</names>
		<date value="2003-01"/>
		<abstract>
			<richtext>
				<p>A facility for compiling an XML schema into one or more Java classes which can parse, generate, and validate documents that follow the schema.</p>
			</richtext>
		</abstract>
		<howpublished>Java Specification Request (JSR) 31</howpublished>
		<title type="sharef:primaryTitle">XML Data Binding Specification</title>
		<field type="bibtex:topic">jaxb[1]</field>
		<identifier type="sharef:uri">http://www.jcp.org/en/jsr/detail?id=31</identifier>
	</reference>
	<reference name="jsr054" src="bibtex:misc" src-info="bibtex:line-40202" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Lance</givenname>
				<surname>Andersen</surname>
			</person>
		</names>
		<date value="2002-05"/>
		<abstract>
			<richtext>
				<p>The proposed specification will update the JDBC specification to reflect changes in the SQL specification and Java platform.</p>
			</richtext>
		</abstract>
		<howpublished>Java Specification Request (JSR) 54</howpublished>
		<title type="sharef:primaryTitle">JDBC 3.0 Specification</title>
		<field type="bibtex:topic">jdbc[1]</field>
		<identifier type="sharef:uri">http://www.jcp.org/en/jsr/detail?id=54</identifier>
	</reference>
	<reference name="jsr063" src="bibtex:misc" src-info="bibtex:line-40213" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Rajiv</givenname>
				<surname>Mordani</surname>
			</person>
		</names>
		<date value="2002-09"/>
		<abstract>
			<richtext>
				<p>The proposed specification will define a set of implementation independent portable APIs supporting XML Processing.</p>
			</richtext>
		</abstract>
		<howpublished>Java Specification Request (JSR) 63</howpublished>
		<title type="sharef:primaryTitle">Java API for XML Processing 1.1</title>
		<field type="bibtex:topic">jaxp[1]</field>
		<field type="bibtex:updates">jsr005</field>
		<identifier type="sharef:uri">http://www.jcp.org/en/jsr/detail?id=63</identifier>
	</reference>
	<reference name="jsr102" src="bibtex:misc" src-info="bibtex:line-40225" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Jason</givenname>
				<surname>Hunter</surname>
			</person>
		</names>
		<date value="2001-02"/>
		<abstract>
			<richtext>
				<p>JDOM is a way to represent an XML document for easy and efficient reading, manipulation, and writing.</p>
			</richtext>
		</abstract>
		<howpublished>Java Specification Request (JSR) 102</howpublished>
		<title type="sharef:primaryTitle">JDOM 1.0</title>
		<field type="bibtex:topic">jdom[1]</field>
		<identifier type="sharef:uri">http://www.jcp.org/en/jsr/detail?id=102</identifier>
	</reference>
	<reference name="jsr127" src="bibtex:misc" src-info="bibtex:line-40236" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Ed</givenname>
				<surname>Burns</surname>
			</person>
			<person>
				<givenname>Craig R.</givenname>
				<surname>McClanahan</surname>
			</person>
		</names>
		<date value="2004-05"/>
		<abstract>
			<richtext>
				<p>This specification defines an architecture and APIs which simplify the creation and maintenance of Java Server application GUIs.</p>
			</richtext>
		</abstract>
		<howpublished>Java Specification Request (JSR) 127</howpublished>
		<title type="sharef:primaryTitle">JavaServer Faces</title>
		<field type="bibtex:topic">jsf[1]</field>
		<identifier type="sharef:uri">http://www.jcp.org/en/jsr/detail?id=127</identifier>
	</reference>
	<reference name="jsr168" src="bibtex:misc" src-info="bibtex:line-40247" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Martin Scott</givenname>
				<surname>Nicklous</surname>
			</person>
		</names>
		<date value="2003-10"/>
		<abstract>
			<richtext>
				<p>To enable interoperability between Portlets and Portals, this specification will define a set of APIs for Portal computing addressing the areas of aggregation, personalization, presentation and security.</p>
			</richtext>
		</abstract>
		<howpublished>Java Specification Request (JSR) 168</howpublished>
		<title type="sharef:primaryTitle">Portlet Specification</title>
		<field type="bibtex:topic">portlet[1]</field>
		<identifier type="sharef:uri">http://www.jcp.org/en/jsr/detail?id=168</identifier>
	</reference>
	<reference name="jsr170" src="bibtex:misc" src-info="bibtex:line-40258" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>David</givenname>
				<surname>Nuescheler</surname>
			</person>
		</names>
		<date value="2006-04"/>
		<abstract>
			<richtext>
				<p>Specifies a standard API to access content repositories in Java 2 independently of implementation.</p>
			</richtext>
		</abstract>
		<howpublished>Java Specification Request (JSR) 170</howpublished>
		<title type="sharef:primaryTitle">Content Repository for Java technology API</title>
		<field type="bibtex:topic">jcr[1]</field>
		<identifier type="sharef:uri">http://www.jcp.org/en/jsr/detail?id=170</identifier>
	</reference>
	<reference name="jsr173" src="bibtex:misc" src-info="bibtex:line-40269" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Ron</givenname>
				<surname>Benson</surname>
			</person>
		</names>
		<date value="2004-03"/>
		<abstract>
			<richtext>
				<p>The Streaming API for XML (StAX) is a Java based API for pull-parsing XML.</p>
			</richtext>
		</abstract>
		<howpublished>Java Specification Request (JSR) 173</howpublished>
		<title type="sharef:primaryTitle">Streaming API for XML</title>
		<field type="bibtex:topic">stax[1]</field>
		<identifier type="sharef:uri">http://www.jcp.org/en/jsr/detail?id=173</identifier>
	</reference>
	<reference name="jsr205" src="bibtex:misc" src-info="bibtex:line-40280" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Jochen</givenname>
				<surname>Sauter</surname>
			</person>
		</names>
		<date value="2004-05"/>
		<howpublished>Java Specification Request (JSR) 205</howpublished>
		<title type="sharef:primaryTitle">Wireless Messaging API 2.0</title>
		<field type="bibtex:topic">wma[1]</field>
		<identifier type="sharef:uri">http://www.jcp.org/en/jsr/detail?id=205</identifier>
	</reference>
	<reference name="jsr206" src="bibtex:misc" src-info="bibtex:line-40290" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Jeff</givenname>
				<surname>Suttor</surname>
			</person>
			<person>
				<givenname>Norman</givenname>
				<surname>Walsh</surname>
			</person>
		</names>
		<date value="2004-09"/>
		<abstract>
			<richtext>
				<p>JAXP 1.3 is the next version of JAXP, an implementation independent portable API for processing XML with Java.</p>
			</richtext>
		</abstract>
		<howpublished>Java Specification Request (JSR) 206</howpublished>
		<title type="sharef:primaryTitle">Java API for XML Processing (JAXP) 1.3</title>
		<field type="bibtex:topic">jaxp[1]</field>
		<field type="bibtex:updates">jsr063</field>
		<identifier type="sharef:uri">http://www.jcp.org/en/jsr/detail?id=206</identifier>
	</reference>
	<reference name="jsr221" src="bibtex:misc" src-info="bibtex:line-40302" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Lance</givenname>
				<surname>Andersen</surname>
			</person>
		</names>
		<date value="2006-12"/>
		<abstract>
			<richtext>
				<p>This specification seeks to improve Java application access to SQL data stores by the provision of ease-of-development focused features and improvements at both the utility and API level.</p>
			</richtext>
		</abstract>
		<howpublished>Java Specification Request (JSR) 221</howpublished>
		<title type="sharef:primaryTitle">JDBC 4.0 API Specification</title>
		<field type="bibtex:topic">jdbc[1]</field>
		<field type="bibtex:updates">jsr054</field>
		<identifier type="sharef:uri">http://www.jcp.org/en/jsr/detail?id=221</identifier>
	</reference>
	<reference name="jsr222" src="bibtex:misc" src-info="bibtex:line-40314" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Joe</givenname>
				<surname>Fialli</surname>
			</person>
			<person>
				<givenname>Sekhar</givenname>
				<surname>Vajjhala</surname>
			</person>
		</names>
		<date value="2005-10"/>
		<abstract>
			<richtext>
				<p>JAXB 2.0 is the next version of JAXB, The Java Architecture for XML Binding. This JSR proposes additional functionality while retaining ease of development as a key goal.</p>
			</richtext>
		</abstract>
		<howpublished>Java Specification Request (JSR) 222</howpublished>
		<title type="sharef:primaryTitle">Java Architecture for XML Binding (JAXB) 2.0</title>
		<field type="bibtex:topic">jaxb[1]</field>
		<field type="bibtex:updates">jsr031</field>
		<identifier type="sharef:uri">http://www.jcp.org/en/jsr/detail?id=222</identifier>
	</reference>
	<reference name="jsr225" src="bibtex:misc" src-info="bibtex:line-40326" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Andrew</givenname>
				<surname>Eisenberg</surname>
			</person>
			<person>
				<givenname>Jim</givenname>
				<surname>Melton</surname>
			</person>
		</names>
		<date value="2007-11"/>
		<abstract>
			<richtext>
				<p>Develop a common API that allows an application to submit queries conforming to the W3C XQuery 1.0 specification and to process the results of such queries.</p>
			</richtext>
		</abstract>
		<howpublished>Java Specification Request (JSR) 225</howpublished>
		<title type="sharef:primaryTitle">XQuery API for Java (XQJ)</title>
		<field type="bibtex:topic">xqj[1]</field>
		<identifier type="sharef:uri">http://www.jcp.org/en/jsr/detail?id=225</identifier>
	</reference>
	<reference name="jsr232" src="bibtex:misc" src-info="bibtex:line-40337" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Venkat</givenname>
				<surname>Amirisetty</surname>
			</person>
			<person>
				<givenname>Erkki</givenname>
				<surname>Rysa</surname>
			</person>
		</names>
		<date value="2008-01"/>
		<abstract>
			<richtext>
				<p>Create a predictable management environment for mobile devices capable of installing, executing, profiling, updating, and removing Java and associated native components in the J2ME Connected Device Configuration.</p>
			</richtext>
		</abstract>
		<howpublished>Java Specification Request (JSR) 232</howpublished>
		<title type="sharef:primaryTitle">Mobile Operational Management</title>
		<field type="bibtex:topic">osgi[0.9]</field>
		<identifier type="sharef:uri">http://www.jcp.org/en/jsr/detail?id=232</identifier>
	</reference>
	<reference name="jsr252" src="bibtex:misc" src-info="bibtex:line-40348" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Ed</givenname>
				<surname>Burns</surname>
			</person>
			<person>
				<givenname>Roger</givenname>
				<surname>Kitain</surname>
			</person>
		</names>
		<date value="2006-02"/>
		<abstract>
			<richtext>
				<p>This JSR is an update to the 1.1 version of the JavaServer Faces specification. Its scope goes beyond a JCP maintenance release, but is short of a new feature release.</p>
			</richtext>
		</abstract>
		<howpublished>Java Specification Request (JSR) 252</howpublished>
		<title type="sharef:primaryTitle">JavaServer Faces 1.2</title>
		<field type="bibtex:topic">jsf[1]</field>
		<field type="bibtex:updates">jsr127</field>
		<identifier type="sharef:uri">http://www.jcp.org/en/jsr/detail?id=252</identifier>
	</reference>
	<reference name="jsr261" src="bibtex:misc" src-info="bibtex:line-40360" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Mike</givenname>
				<surname>Grogan</surname>
			</person>
			<person>
				<givenname>Arun</givenname>
				<surname>Gupta</surname>
			</person>
		</names>
		<date value="2006-06"/>
		<abstract>
			<richtext>
				<p>The Java API for XML Web Services Addressing (JAX-WSA) 1.0 specification will define APIs and a framework for supporting transport-neutral addressing of Web services.</p>
			</richtext>
		</abstract>
		<howpublished>Java Specification Request (JSR) 261</howpublished>
		<title type="sharef:primaryTitle">Java API for XML Web Services Addressing (JAX-WSA)</title>
		<field type="bibtex:topic">jaxwsa[1]</field>
		<identifier type="sharef:uri">http://www.jcp.org/en/jsr/detail?id=261</identifier>
	</reference>
	<reference name="jsr279" src="bibtex:misc" src-info="bibtex:line-40371" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Pia</givenname>
				<surname>Niemela</surname>
			</person>
			<person>
				<givenname>Jens</givenname>
				<surname>Paetzold</surname>
			</person>
		</names>
		<date value="2007-12"/>
		<abstract>
			<richtext>
				<p>A new high-level API for connection services via frameworks supporting identity based services, discovery, and authentication. The API supports Service Oriented Architectures (SOA) and other similar network service application models.</p>
			</richtext>
		</abstract>
		<howpublished>Java Specification Request (JSR) 279</howpublished>
		<title type="sharef:primaryTitle">Service Connection API for Java ME</title>
		<field type="bibtex:topic">javame[0.8]</field>
		<identifier type="sharef:uri">http://www.jcp.org/en/jsr/detail?id=279</identifier>
	</reference>
	<reference name="jsr280" src="bibtex:misc" src-info="bibtex:line-40382" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Pia</givenname>
				<surname>Niemela</surname>
			</person>
			<person>
				<givenname>Ellen</givenname>
				<surname>Siegel</surname>
			</person>
		</names>
		<date value="2005-08"/>
		<abstract>
			<richtext>
				<p>This JSR provides a common general purpose XML API for the next generation of mobile devices.</p>
			</richtext>
		</abstract>
		<howpublished>Java Specification Request (JSR) 280</howpublished>
		<title type="sharef:primaryTitle">XML API for Java ME</title>
		<field type="bibtex:topic">javame[0.8]</field>
		<identifier type="sharef:uri">http://www.jcp.org/en/jsr/detail?id=280</identifier>
	</reference>
	<reference name="jsr291" src="bibtex:misc" src-info="bibtex:line-40393" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Thomas</givenname>
				<surname>Watson</surname>
			</person>
		</names>
		<date value="2007-08"/>
		<abstract>
			<richtext>
				<p>Establish a JCP specification for a dynamic component framework supporting existing Java SE environments based on the OSGi dynamic component model specifications.</p>
			</richtext>
		</abstract>
		<howpublished>Java Specification Request (JSR) 291</howpublished>
		<title type="sharef:primaryTitle">Dynamic Component Support for Java SE</title>
		<field type="bibtex:topic">javase[0.8] osgi[0.9]</field>
		<identifier type="sharef:uri">http://www.jcp.org/en/jsr/detail?id=291</identifier>
	</reference>
	<reference name="jsr311" src="bibtex:misc" src-info="bibtex:line-40404" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Marc</givenname>
				<surname>Hadley</surname>
			</person>
			<person>
				<givenname>Paul</givenname>
				<surname>Sandoz</surname>
			</person>
		</names>
		<date value="2009-03"/>
		<abstract>
			<richtext>
				<p>This JSR will develop an API for providing support for RESTful(Representational State Transfer) Web Services in the Java Platform.</p>
			</richtext>
		</abstract>
		<howpublished>Java Specification Request (JSR) 311</howpublished>
		<title type="sharef:primaryTitle">JAX-RS: The Java API for RESTful Web Services</title>
		<field type="bibtex:topic">rest[0.8] jaxrs[1]</field>
		<identifier type="sharef:uri">http://www.jcp.org/en/jsr/detail?id=311</identifier>
	</reference>
	<reference name="rfc20" src="bibtex:misc" src-info="bibtex:line-40419" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Vinton G.</givenname>
				<surname>Cerf</surname>
			</person>
		</names>
		<date value="1969-10"/>
		<howpublished>Internet RFC 20</howpublished>
		<title type="sharef:primaryTitle">ASCII Format for Network Interchange</title>
		<field type="bibtex:topic">ascii[0.9]</field>
	</reference>
	<reference name="rfc707" src="bibtex:misc" src-info="bibtex:line-40428" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>James E.</givenname>
				<surname>White</surname>
			</person>
		</names>
		<date value="1975-12"/>
		<abstract>
			<richtext>
				<p>The principal goal of all resource-sharing computer networks, including the now international ARPA Network (the ARPANET), is to usefully interconnect geographically distributed hardware, software, and human resources. Achieving this goal requires the design and implementation of various levels of support software within each constituent computer, and the specification of network-wide "protocols" (that is, conventions regarding the format and the relative timing of network messages) governing their interaction. This paper outlines an alternative to the approach that ARPANET system builders have been taking since work in this area began in 1970, and suggests a strategy for modeling distributed systems within any large computer network. The first section of this paper describes the prevailing ARPANET protocol strategy, which involves specifying a family of application-dependent protocols with a network-wide inter-process communication facility as their common foundation. In the second section, the application-independent command/response discipline that characterizes this protocol family is identified and its isolation as a separate protocol proposed. Such isolation would reduce the work of the applications programmer by allowing the software that implements the protocol to be factored out of each applications program and supplied as a single, installation-maintained module. The final section of this paper proposes an extensible model for this class of network interaction that in itself would even further encourage the use of network resources.</p>
			</richtext>
		</abstract>
		<howpublished>Internet RFC 707</howpublished>
		<title type="sharef:primaryTitle">A High-Level Framework for Network-Based Resource Sharing</title>
		<field type="bibtex:topic">rpc[1]</field>
	</reference>
	<reference name="rfc768" src="bibtex:misc" src-info="bibtex:line-40438" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Jon B.</givenname>
				<surname>Postel</surname>
			</person>
		</names>
		<date value="1980-08"/>
		<howpublished>Internet RFC 768</howpublished>
		<field type="bibtex:index">UDP</field>
		<title type="sharef:primaryTitle">User Datagram Protocol</title>
	</reference>
	<reference name="rfc791" src="bibtex:misc" src-info="bibtex:line-40447" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Jon B.</givenname>
				<surname>Postel</surname>
			</person>
		</names>
		<date value="1981-09"/>
		<howpublished>Internet RFC 791</howpublished>
		<field type="bibtex:index">IP</field>
		<title type="sharef:primaryTitle">Internet Protocol</title>
	</reference>
	<reference name="rfc793" src="bibtex:misc" src-info="bibtex:line-40456" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Jon B.</givenname>
				<surname>Postel</surname>
			</person>
		</names>
		<date value="1981-09"/>
		<howpublished>Internet RFC 793</howpublished>
		<title type="sharef:primaryTitle">Transmission Control Protocol</title>
		<field type="bibtex:topic">tcp[1]</field>
	</reference>
	<reference name="rfc821" src="bibtex:misc" src-info="bibtex:line-40465" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Jon B.</givenname>
				<surname>Postel</surname>
			</person>
		</names>
		<date value="1982-08"/>
		<howpublished>Internet RFC 821</howpublished>
		<title type="sharef:primaryTitle">Simple Mail Transfer Protocol</title>
		<field type="bibtex:topic">smtp[1]</field>
	</reference>
	<reference name="rfc822" src="bibtex:misc" src-info="bibtex:line-40474" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>David H.</givenname>
				<surname>Crocker</surname>
			</person>
		</names>
		<date value="1982-08"/>
		<howpublished>Internet RFC 822</howpublished>
		<title type="sharef:primaryTitle">Standard for the Format of ARPA Internet Text Messages</title>
	</reference>
	<reference name="rfc854" src="bibtex:misc" src-info="bibtex:line-40482" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Jon B.</givenname>
				<surname>Postel</surname>
			</person>
		</names>
		<date value="1983-05"/>
		<howpublished>Internet RFC 854</howpublished>
		<field type="bibtex:index">Telnet</field>
		<title type="sharef:primaryTitle">Telnet Protocol Specification</title>
	</reference>
	<reference name="rfc868" src="bibtex:misc" src-info="bibtex:line-40491" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Jon B.</givenname>
				<surname>Postel</surname>
			</person>
			<person>
				<givenname>Ken</givenname>
				<surname>Harrenstien</surname>
			</person>
		</names>
		<date value="1983-05"/>
		<howpublished>Internet RFC 868</howpublished>
		<field type="bibtex:index">Time Protocol</field>
		<title type="sharef:primaryTitle">Time Protocol</title>
	</reference>
	<reference name="rfc903" src="bibtex:misc" src-info="bibtex:line-40500" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Ross</givenname>
				<surname>Finlayson</surname>
			</person>
			<person>
				<givenname>Timothy</givenname>
				<surname>Mann</surname>
			</person>
			<person>
				<givenname>Jeffrey C.</givenname>
				<surname>Mogul</surname>
			</person>
			<person>
				<givenname>Marvin</givenname>
				<surname>Theimer</surname>
			</person>
		</names>
		<date value="1984-06"/>
		<howpublished>Internet RFC 903</howpublished>
		<title type="sharef:primaryTitle">Reverse Address Resolution Protocol</title>
		<field type="bibtex:topic">rarp[1]</field>
	</reference>
	<reference name="rfc920" src="bibtex:misc" src-info="bibtex:line-40509" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Jon B.</givenname>
				<surname>Postel</surname>
			</person>
			<person>
				<givenname>Joyce K.</givenname>
				<surname>Reynolds</surname>
			</person>
		</names>
		<date value="1984-10"/>
		<howpublished>Internet RFC 920</howpublished>
		<title type="sharef:primaryTitle">Domain Requirements</title>
		<field type="bibtex:topic">dns[0.9]</field>
	</reference>
	<reference name="rfc931" src="bibtex:misc" src-info="bibtex:line-40518" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Michael</givenname>
				<surname>St. Johns</surname>
			</person>
		</names>
		<date value="1985-01"/>
		<howpublished>Internet RFC 931</howpublished>
		<field type="bibtex:index">ident</field>
		<title type="sharef:primaryTitle">Authentication Server</title>
	</reference>
	<reference name="rfc955" src="bibtex:misc" src-info="bibtex:line-40527" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Robert</givenname>
				<surname>Braden</surname>
			</person>
		</names>
		<date value="1985-09"/>
		<howpublished>Internet RFC 955</howpublished>
		<field type="bibtex:index">transaction processing, T/TCP</field>
		<title type="sharef:primaryTitle">Towards a Transport Service for Transaction Processing Applications</title>
	</reference>
	<reference name="rfc959" src="bibtex:misc" src-info="bibtex:line-40536" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Jon B.</givenname>
				<surname>Postel</surname>
			</person>
			<person>
				<givenname>Joyce K.</givenname>
				<surname>Reynolds</surname>
			</person>
		</names>
		<date value="1985-10"/>
		<howpublished>Internet RFC 959</howpublished>
		<title type="sharef:primaryTitle">File Transfer Protocol (FTP)</title>
		<field type="bibtex:topic">ftp[1]</field>
	</reference>
	<reference name="rfc974" src="bibtex:misc" src-info="bibtex:line-40545" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Craig</givenname>
				<surname>Partridge</surname>
			</person>
		</names>
		<date value="1986-01"/>
		<howpublished>Internet RFC 974</howpublished>
		<title type="sharef:primaryTitle">Mail Routing and the Domain System</title>
	</reference>
	<reference name="rfc977" src="bibtex:misc" src-info="bibtex:line-40553" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Brian</givenname>
				<surname>Kantor</surname>
			</person>
			<person>
				<givenname>Phil</givenname>
				<surname>Lapsley</surname>
			</person>
		</names>
		<date value="1986-02"/>
		<howpublished>Internet RFC 977</howpublished>
		<title type="sharef:primaryTitle">Network News Transfer Protocol</title>
		<field type="bibtex:topic">nntp[1]</field>
	</reference>
	<reference name="rfc1006" src="bibtex:misc" src-info="bibtex:line-40562" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Marshall T.</givenname>
				<surname>Rose</surname>
			</person>
			<person>
				<givenname>Dwight E.</givenname>
				<surname>Cass</surname>
			</person>
		</names>
		<date value="1987-05"/>
		<howpublished>Internet RFC 1006</howpublished>
		<field type="bibtex:index">TCP, ISO, TSAP</field>
		<title type="sharef:primaryTitle">ISO Transport Service on top of the TCP</title>
	</reference>
	<reference name="rfc1034" src="bibtex:misc" src-info="bibtex:line-40571" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Paul</givenname>
				<surname>Mockapetris</surname>
			</person>
		</names>
		<date value="1987-11"/>
		<howpublished>Internet RFC 1034</howpublished>
		<field type="bibtex:index">DNS</field>
		<title type="sharef:primaryTitle">Domain Names — Concepts and Facilities</title>
	</reference>
	<reference name="rfc1035" src="bibtex:misc" src-info="bibtex:line-40580" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Paul</givenname>
				<surname>Mockapetris</surname>
			</person>
		</names>
		<date value="1987-11"/>
		<howpublished>Internet RFC 1035</howpublished>
		<field type="bibtex:index">DNS</field>
		<title type="sharef:primaryTitle">Domain Names — Implementation and Specification</title>
	</reference>
	<reference name="rfc1036" src="bibtex:misc" src-info="bibtex:line-40589" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Mark</givenname>
				<surname>Horton</surname>
			</person>
			<person>
				<givenname>Rick</givenname>
				<surname>Adams</surname>
			</person>
		</names>
		<date value="1987-12"/>
		<howpublished>Internet RFC 1036</howpublished>
		<title type="sharef:primaryTitle">Standard for Interchange of USENET Messages</title>
		<field type="bibtex:topic">usenetnews[1]</field>
	</reference>
	<reference name="rfc1055" src="bibtex:misc" src-info="bibtex:line-40598" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>J.</givenname>
				<surname>Romkey</surname>
			</person>
		</names>
		<date value="1988-06"/>
		<howpublished>Internet RFC 1055</howpublished>
		<title type="sharef:primaryTitle">A Nonstandard for Transmission of IP Datagrams over Serial Lines: SLIP</title>
		<field type="bibtex:topic">slip[1]</field>
	</reference>
	<reference name="rfc1056" src="bibtex:misc" src-info="bibtex:line-40607" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>M.</givenname>
				<surname>Lambert</surname>
			</person>
		</names>
		<date value="1988-06"/>
		<howpublished>Internet RFC 1056</howpublished>
		<field type="bibtex:index">DMSP</field>
		<title type="sharef:primaryTitle">PCMAIL: A Distributed Mail System for Personal Computers</title>
	</reference>
	<reference name="rfc1075" src="bibtex:misc" src-info="bibtex:line-40616" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>David</givenname>
				<surname>Waitzman</surname>
			</person>
			<person>
				<givenname>Craig</givenname>
				<surname>Partridge</surname>
			</person>
			<person>
				<givenname>Stephen E.</givenname>
				<surname>Deering</surname>
			</person>
		</names>
		<date value="1988-11"/>
		<howpublished>Internet RFC 1075</howpublished>
		<title type="sharef:primaryTitle">Distance Vector Multicast Routing Protocol</title>
		<field type="bibtex:topic">dvmrp[1]</field>
	</reference>
	<reference name="rfc1112" src="bibtex:misc" src-info="bibtex:line-40625" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Stephen E.</givenname>
				<surname>Deering</surname>
			</person>
		</names>
		<date value="1989-08"/>
		<howpublished>Internet RFC 1112</howpublished>
		<field type="bibtex:index">IP multicast</field>
		<title type="sharef:primaryTitle">Host Extensions for IP Multicasting</title>
	</reference>
	<reference name="rfc1122" src="bibtex:misc" src-info="bibtex:line-40634" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Robert</givenname>
				<surname>Braden</surname>
			</person>
		</names>
		<date value="1989-10"/>
		<howpublished>Internet RFC 1122</howpublished>
		<field type="bibtex:index">IP, TCP</field>
		<title type="sharef:primaryTitle">Requirements for Internet Hosts — Communication Layer</title>
	</reference>
	<reference name="rfc1123" src="bibtex:misc" src-info="bibtex:line-40643" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Robert</givenname>
				<surname>Braden</surname>
			</person>
		</names>
		<date value="1989-10"/>
		<howpublished>Internet RFC 1123</howpublished>
		<field type="bibtex:index">DNS, FTP, Telnet, SMTP</field>
		<title type="sharef:primaryTitle">Requirements for Internet Hosts — Application and Support</title>
	</reference>
	<reference name="rfc1138" src="bibtex:misc" src-info="bibtex:line-40652" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Steve</givenname>
				<surname>Kille</surname>
			</person>
		</names>
		<date value="1989-12"/>
		<abstract>
			<richtext>
				<p>This document specifies a mapping between two protocols. This specification should be used when this mapping is performed on the Internet or in the UK Academic Community. This specification may be modified in the light of implementation experience, but no substantial changes are expected.</p>
			</richtext>
		</abstract>
		<howpublished>Internet RFC 1138</howpublished>
		<title type="sharef:primaryTitle">Mapping between X.400(1988) / ISO 10021 and RFC 822</title>
	</reference>
	<reference name="rfc1183" src="bibtex:misc" src-info="bibtex:line-40661" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Craig F.</givenname>
				<surname>Everhart</surname>
			</person>
			<person>
				<givenname>Louis A.</givenname>
				<surname>Mamakos</surname>
			</person>
			<person>
				<givenname>Robert</givenname>
				<surname>Ullmann</surname>
			</person>
			<person>
				<givenname>Paul</givenname>
				<surname>Mockapetris</surname>
			</person>
		</names>
		<date value="1990-10"/>
		<howpublished>Internet RFC 1183</howpublished>
		<title type="sharef:primaryTitle">New DNS RR Definitions</title>
		<field type="bibtex:topic">dns[0.9]</field>
		<field type="bibtex:updates">rfc1034 rfc1035</field>
	</reference>
	<reference name="rfc1279" src="bibtex:misc" src-info="bibtex:line-40671" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Steven</givenname>
				<surname>Hardcastle-Kille</surname>
			</person>
		</names>
		<date value="1991-11"/>
		<howpublished>Internet RFC 1279</howpublished>
		<field type="bibtex:index">DNS, X.500</field>
		<title type="sharef:primaryTitle">X.500 and Domains</title>
	</reference>
	<reference name="rfc1296" src="bibtex:misc" src-info="bibtex:line-40680" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Mark K.</givenname>
				<surname>Lottor</surname>
			</person>
		</names>
		<date value="1992-01"/>
		<howpublished>Internet RFC 1296</howpublished>
		<field type="bibtex:index">DNS</field>
		<title type="sharef:primaryTitle">Internet Growth (1981-1991)</title>
	</reference>
	<reference name="rfc1305" src="bibtex:misc" src-info="bibtex:line-40689" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>David L.</givenname>
				<surname>Mills</surname>
			</person>
		</names>
		<date value="1992-03"/>
		<howpublished>Internet RFC 1305</howpublished>
		<title type="sharef:primaryTitle">Network Time Protocol (Version 3) — Specification, Implementation and Analysis</title>
		<field type="bibtex:topic">ntp[1]</field>
	</reference>
	<reference name="rfc1310" src="bibtex:misc" src-info="bibtex:line-40698" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>A. Lyman</givenname>
				<surname>Chapin</surname>
			</person>
		</names>
		<date value="1992-03"/>
		<howpublished>Internet RFC 1310</howpublished>
		<title type="sharef:primaryTitle">The Internet Standards Process</title>
		<field type="bibtex:topic">rfc[1]</field>
	</reference>
	<reference name="rfc1319" src="bibtex:misc" src-info="bibtex:line-40707" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Burton S.</givenname>
				<surname>Kaliski</surname>
			</person>
		</names>
		<date value="1992-04"/>
		<howpublished>Internet RFC 1319</howpublished>
		<field type="bibtex:index">MD2</field>
		<title type="sharef:primaryTitle">The MD2 Message-Digest Algorithm</title>
	</reference>
	<reference name="rfc1320" src="bibtex:misc" src-info="bibtex:line-40716" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Ronald L.</givenname>
				<surname>Rivest</surname>
			</person>
		</names>
		<date value="1992-04"/>
		<howpublished>Internet RFC 1320</howpublished>
		<field type="bibtex:index">MD4</field>
		<title type="sharef:primaryTitle">The MD4 Message-Digest Algorithm</title>
	</reference>
	<reference name="rfc1321" src="bibtex:misc" src-info="bibtex:line-40725" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Ronald L.</givenname>
				<surname>Rivest</surname>
			</person>
		</names>
		<date value="1992-04"/>
		<howpublished>Internet RFC 1321</howpublished>
		<title type="sharef:primaryTitle">The MD5 Message-Digest Algorithm</title>
		<field type="bibtex:topic">md5[1]</field>
	</reference>
	<reference name="rfc1334" src="bibtex:misc" src-info="bibtex:line-40734" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Brian</givenname>
				<surname>Lloyd</surname>
			</person>
			<person>
				<givenname>William Allen</givenname>
				<surname>Simpson</surname>
			</person>
		</names>
		<date value="1992-10"/>
		<howpublished>Internet RFC 1334</howpublished>
		<title type="sharef:primaryTitle">PPP Authentication Protocols</title>
		<field type="bibtex:topic">ppp[0.9] pap[1] chap[1]</field>
	</reference>
	<reference name="rfc1341" src="bibtex:misc" src-info="bibtex:line-40743" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Nathaniel S.</givenname>
				<surname>Borenstein</surname>
			</person>
			<person>
				<givenname>Ned</givenname>
				<surname>Freed</surname>
			</person>
		</names>
		<date value="1992-06"/>
		<howpublished>Internet RFC 1341</howpublished>
		<field type="bibtex:index">MIME</field>
		<title type="sharef:primaryTitle">MIME (Multipurpose Internet Mail Extensions): Mechanisms for Specifying and Describing the Format of Internet Message Bodies</title>
	</reference>
	<reference name="rfc1363" src="bibtex:misc" src-info="bibtex:line-40752" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Craig</givenname>
				<surname>Partridge</surname>
			</person>
		</names>
		<date value="1992-09"/>
		<howpublished>Internet RFC 1363</howpublished>
		<field type="bibtex:index">flow spec</field>
		<title type="sharef:primaryTitle">A Proposed Flow Specification</title>
	</reference>
	<reference name="rfc1379" src="bibtex:misc" src-info="bibtex:line-40761" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Robert</givenname>
				<surname>Braden</surname>
			</person>
		</names>
		<date value="1992-11"/>
		<howpublished>Internet RFC 1379</howpublished>
		<field type="bibtex:index">T/TCP</field>
		<title type="sharef:primaryTitle">Extending TCP for Transactions — Concepts</title>
	</reference>
	<reference name="rfc1413" src="bibtex:misc" src-info="bibtex:line-40770" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Michael</givenname>
				<surname>St. Johns</surname>
			</person>
		</names>
		<date value="1993-02"/>
		<howpublished>Internet RFC 1413</howpublished>
		<field type="bibtex:index">ident</field>
		<title type="sharef:primaryTitle">Identification Protocol</title>
	</reference>
	<reference name="rfc1421" src="bibtex:misc" src-info="bibtex:line-40779" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>John</givenname>
				<surname>Linn</surname>
			</person>
		</names>
		<date value="1993-02"/>
		<howpublished>Internet RFC 1421</howpublished>
		<field type="bibtex:index">PEM</field>
		<title type="sharef:primaryTitle">Privacy Enhancement for Internet Electronic Mail — Part I: Message Encryption and Authentication Procedures</title>
	</reference>
	<reference name="rfc1422" src="bibtex:misc" src-info="bibtex:line-40788" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Stephen</givenname>
				<surname>Kent</surname>
			</person>
		</names>
		<date value="1993-02"/>
		<howpublished>Internet RFC 1422</howpublished>
		<field type="bibtex:index">PEM</field>
		<title type="sharef:primaryTitle">Privacy Enhancement for Internet Electronic Mail — Part II: Certificate-Based Key Management</title>
	</reference>
	<reference name="rfc1423" src="bibtex:misc" src-info="bibtex:line-40797" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>David</givenname>
				<surname>Balenson</surname>
			</person>
		</names>
		<date value="1993-02"/>
		<howpublished>Internet RFC 1423</howpublished>
		<field type="bibtex:index">PEM</field>
		<title type="sharef:primaryTitle">Privacy Enhancement for Internet Electronic Mail — Part III: Algorithms, Modes, and Identifiers</title>
	</reference>
	<reference name="rfc1424" src="bibtex:misc" src-info="bibtex:line-40806" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Burton S.</givenname>
				<surname>Kaliski</surname>
			</person>
		</names>
		<date value="1993-02"/>
		<howpublished>Internet RFC 1424</howpublished>
		<field type="bibtex:index">PEM</field>
		<title type="sharef:primaryTitle">Privacy Enhancement for Internet Electronic Mail — Part IV: Key Certification and Related Services</title>
	</reference>
	<reference name="rfc1436" src="bibtex:misc" src-info="bibtex:line-40815" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Farhad</givenname>
				<surname>Anklesaria</surname>
			</person>
			<person>
				<givenname>Mark</givenname>
				<surname>McCahill</surname>
			</person>
			<person>
				<givenname>Paul</givenname>
				<surname>Lindner</surname>
			</person>
			<person>
				<givenname>David</givenname>
				<surname>Johnson</surname>
			</person>
			<person>
				<givenname>Daniel</givenname>
				<surname>Torrey</surname>
			</person>
			<person>
				<givenname>Bob</givenname>
				<surname>Alberti</surname>
			</person>
		</names>
		<date value="1993-03"/>
		<howpublished>Internet RFC 1436</howpublished>
		<title type="sharef:primaryTitle">The Internet Gopher Protocol</title>
		<field type="bibtex:topic">gopher[1]</field>
	</reference>
	<reference name="rfc1438" src="bibtex:misc" src-info="bibtex:line-40824" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>A. Lyman</givenname>
				<surname>Chapin</surname>
			</person>
			<person>
				<givenname>Christian</givenname>
				<surname>Huitema</surname>
			</person>
		</names>
		<date value="1993-04"/>
		<howpublished>Internet RFC 1438</howpublished>
		<title type="sharef:primaryTitle">Internet Engineering Task Force Statements Of Boredom (SOBs)</title>
	</reference>
	<reference name="rfc1458" src="bibtex:misc" src-info="bibtex:line-40832" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Robert</givenname>
				<surname>Braudes</surname>
			</person>
			<person>
				<givenname>Steven</givenname>
				<surname>Zabele</surname>
			</person>
		</names>
		<date value="1993-05"/>
		<howpublished>Internet RFC 1458</howpublished>
		<field type="bibtex:index">multicast, IP multicast, XTP, ST-II, MTP, QoS</field>
		<title type="sharef:primaryTitle">Requirements for Multicast Protocols</title>
	</reference>
	<reference name="rfc1459" src="bibtex:misc" src-info="bibtex:line-40841" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Jarkko</givenname>
				<surname>Oikarinen</surname>
			</person>
			<person>
				<givenname>Darren P.</givenname>
				<surname>Reed</surname>
			</person>
		</names>
		<date value="1993-05"/>
		<howpublished>Internet RFC 1459</howpublished>
		<field type="bibtex:index">IRC</field>
		<title type="sharef:primaryTitle">Internet Relay Chat Protocol</title>
	</reference>
	<reference name="rfc1487" src="bibtex:misc" src-info="bibtex:line-40850" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Wengyik</givenname>
				<surname>Yeong</surname>
			</person>
			<person>
				<givenname>Tim</givenname>
				<surname>Howes</surname>
			</person>
			<person>
				<givenname>Steven</givenname>
				<surname>Kille</surname>
			</person>
		</names>
		<date value="1993-07"/>
		<howpublished>Internet RFC 1487</howpublished>
		<title type="sharef:primaryTitle">Lightweight Directory Access Protocol</title>
		<field type="bibtex:topic">ldap[1]</field>
	</reference>
	<reference name="rfc1488" src="bibtex:misc" src-info="bibtex:line-40859" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Tim</givenname>
				<surname>Howes</surname>
			</person>
			<person>
				<givenname>Steven</givenname>
				<surname>Kille</surname>
			</person>
			<person>
				<givenname>Wengyik</givenname>
				<surname>Yeong</surname>
			</person>
			<person>
				<givenname>Colin</givenname>
				<surname>Robbins</surname>
			</person>
		</names>
		<date value="1993-07"/>
		<howpublished>Internet RFC 1488</howpublished>
		<title type="sharef:primaryTitle">The X.500 String Representation of Standard Attribute Syntaxes</title>
		<field type="bibtex:topic">ldap[1]</field>
	</reference>
	<reference name="rfc1498" src="bibtex:misc" src-info="bibtex:line-40868" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Jerome H.</givenname>
				<surname>Saltzer</surname>
			</person>
		</names>
		<date value="1993-08"/>
		<howpublished>Internet RFC 1498</howpublished>
		<field type="bibtex:index">naming, addressing, binding</field>
		<title type="sharef:primaryTitle">On the Naming and Binding of Network Destinations</title>
	</reference>
	<reference name="rfc1521" src="bibtex:misc" src-info="bibtex:line-40877" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Nathaniel S.</givenname>
				<surname>Borenstein</surname>
			</person>
			<person>
				<givenname>Ned</givenname>
				<surname>Freed</surname>
			</person>
		</names>
		<date value="1993-09"/>
		<howpublished>Internet RFC 1521</howpublished>
		<title type="sharef:primaryTitle">MIME (Multipurpose Internet Mail Extensions) — Part One: Mechanisms for Specifying and Describing the Format of Internet Message Bodies</title>
		<field type="bibtex:topic">mime[1] base64[1]</field>
	</reference>
	<reference name="rfc1522" src="bibtex:misc" src-info="bibtex:line-40886" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Keith</givenname>
				<surname>Moore</surname>
			</person>
		</names>
		<date value="1993-09"/>
		<howpublished>Internet RFC 1522</howpublished>
		<title type="sharef:primaryTitle">MIME (Multipurpose Internet Mail Extensions) — Part Two: Message Header Extensions for Non-ASCII Text</title>
	</reference>
	<reference name="rfc1524" src="bibtex:misc" src-info="bibtex:line-40894" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Nathaniel S.</givenname>
				<surname>Borenstein</surname>
			</person>
		</names>
		<date value="1993-09"/>
		<howpublished>Internet RFC 1524</howpublished>
		<field type="bibtex:index">MIME, mailcap</field>
		<title type="sharef:primaryTitle">A User Agent Configuration Mechanism For Multimedia Mail Format Information</title>
	</reference>
	<reference name="rfc1546" src="bibtex:misc" src-info="bibtex:line-40903" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Craig</givenname>
				<surname>Partridge</surname>
			</person>
			<person>
				<givenname>T.</givenname>
				<surname>Mendez</surname>
			</person>
			<person>
				<givenname>W.</givenname>
				<surname>Milliken</surname>
			</person>
		</names>
		<date value="1993-11"/>
		<howpublished>Internet RFC 1546</howpublished>
		<field type="bibtex:index">anycast</field>
		<title type="sharef:primaryTitle">Host Anycasting Service</title>
	</reference>
	<reference name="rfc1591" src="bibtex:misc" src-info="bibtex:line-40912" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Jon B.</givenname>
				<surname>Postel</surname>
			</person>
		</names>
		<date value="1994-03"/>
		<howpublished>Internet RFC 1591</howpublished>
		<field type="bibtex:index">DNS, TLD, gTLD</field>
		<title type="sharef:primaryTitle">Domain Name System Structure and Delegation</title>
	</reference>
	<reference name="rfc1594" src="bibtex:misc" src-info="bibtex:line-40921" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>April N.</givenname>
				<surname>Marine</surname>
			</person>
			<person>
				<givenname>Joyce K.</givenname>
				<surname>Reynolds</surname>
			</person>
			<person>
				<givenname>Gary Scott</givenname>
				<surname>Malkin</surname>
			</person>
		</names>
		<date value="1994-03"/>
		<howpublished>Internet RFC 1594</howpublished>
		<field type="bibtex:index">IP, gopher, DNS</field>
		<title type="sharef:primaryTitle">FYI on Questions and Answers — Answers to Commonly asked "New Internet User" Questions</title>
	</reference>
	<reference name="rfc1602" src="bibtex:misc" src-info="bibtex:line-40930" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Christian</givenname>
				<surname>Huitema</surname>
			</person>
			<person>
				<givenname>Phill</givenname>
				<surname>Gross</surname>
			</person>
		</names>
		<date value="1994-03"/>
		<howpublished>Internet RFC 1602</howpublished>
		<title type="sharef:primaryTitle">The Internet Standards Process — Revision 2</title>
		<field type="bibtex:topic">rfc[1]</field>
		<field type="bibtex:updates">rfc1310</field>
	</reference>
	<reference name="rfc1625" src="bibtex:misc" src-info="bibtex:line-40940" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Margaret</givenname>
				<surname>St. Pierre</surname>
			</person>
			<person>
				<givenname>Jim</givenname>
				<surname>Fullton</surname>
			</person>
			<person>
				<givenname>Kevin</givenname>
				<surname>Gamiel</surname>
			</person>
			<person>
				<givenname>Jonathan</givenname>
				<surname>Goldman</surname>
			</person>
			<person>
				<givenname>Brewster</givenname>
				<surname>Kahle</surname>
			</person>
			<person>
				<givenname>John A.</givenname>
				<surname>Kunze</surname>
			</person>
			<person>
				<givenname>Harry</givenname>
				<surname>Morris</surname>
			</person>
			<person>
				<givenname>François</givenname>
				<surname>Schiettecatte</surname>
			</person>
		</names>
		<date value="1994-06"/>
		<howpublished>Internet RFC 1625</howpublished>
		<title type="sharef:primaryTitle">WAIS over Z39.50-1988</title>
		<field type="bibtex:topic">wais[0.9] z3950[0.7]</field>
	</reference>
	<reference name="rfc1630" src="bibtex:misc" src-info="bibtex:line-40949" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Tim</givenname>
				<surname>Berners-Lee</surname>
			</person>
		</names>
		<date value="1994-06"/>
		<howpublished>Internet RFC 1630</howpublished>
		<field type="bibtex:index">URI</field>
		<title type="sharef:primaryTitle">Universal Resource Identifiers in WWW</title>
	</reference>
	<reference name="rfc1644" src="bibtex:misc" src-info="bibtex:line-40958" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Robert</givenname>
				<surname>Braden</surname>
			</person>
		</names>
		<date value="1994-07"/>
		<howpublished>Internet RFC 1644</howpublished>
		<field type="bibtex:index">T/TCP</field>
		<title type="sharef:primaryTitle">T/TCP — TCP Extensions for Transactions Functional Specification</title>
	</reference>
	<reference name="rfc1661" src="bibtex:misc" src-info="bibtex:line-40967" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>William Allen</givenname>
				<surname>Simpson</surname>
			</person>
		</names>
		<date value="1994-07"/>
		<howpublished>Internet RFC 1661</howpublished>
		<title type="sharef:primaryTitle">The Point-to-Point Protocol (PPP)</title>
		<field type="bibtex:topic">ppp[1]</field>
	</reference>
	<reference name="rfc1715" src="bibtex:misc" src-info="bibtex:line-40976" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Christian</givenname>
				<surname>Huitema</surname>
			</person>
		</names>
		<date value="1994-11"/>
		<howpublished>Internet RFC 1715</howpublished>
		<title type="sharef:primaryTitle">The H Ratio for Address Assignment Efficiency</title>
	</reference>
	<reference name="rfc1734" src="bibtex:misc" src-info="bibtex:line-40984" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>John Gardiner</givenname>
				<surname>Myers</surname>
			</person>
		</names>
		<date value="1994-12"/>
		<howpublished>Internet RFC 1734</howpublished>
		<field type="bibtex:index">POP</field>
		<title type="sharef:primaryTitle">POP3 AUTHentication command</title>
	</reference>
	<reference name="rfc1737" src="bibtex:misc" src-info="bibtex:line-40993" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Karen R.</givenname>
				<surname>Sollins</surname>
			</person>
			<person>
				<givenname>Larry</givenname>
				<surname>Masinter</surname>
			</person>
		</names>
		<date value="1994-12"/>
		<howpublished>Internet RFC 1737</howpublished>
		<field type="bibtex:index">URN</field>
		<title type="sharef:primaryTitle">Functional Requirements for Uniform Resource Names</title>
	</reference>
	<reference name="rfc1738" src="bibtex:misc" src-info="bibtex:line-41002" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Tim</givenname>
				<surname>Berners-Lee</surname>
			</person>
			<person>
				<givenname>Larry</givenname>
				<surname>Masinter</surname>
			</person>
			<person>
				<givenname>Mark</givenname>
				<surname>McCahill</surname>
			</person>
		</names>
		<date value="1994-12"/>
		<howpublished>Internet RFC 1738</howpublished>
		<field type="bibtex:index">URL</field>
		<title type="sharef:primaryTitle">Uniform Resource Locators (URL)</title>
	</reference>
	<reference name="rfc1752" src="bibtex:misc" src-info="bibtex:line-41011" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Scott O.</givenname>
				<surname>Bradner</surname>
			</person>
			<person>
				<givenname>Allison</givenname>
				<surname>Mankin</surname>
			</person>
		</names>
		<date value="1995-01"/>
		<howpublished>Internet RFC 1752</howpublished>
		<field type="bibtex:index">IPng</field>
		<title type="sharef:primaryTitle">The Recommendation for the IP Next Generation Protocol</title>
	</reference>
	<reference name="rfc1760" src="bibtex:misc" src-info="bibtex:line-41020" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Neil</givenname>
				<surname>Haller</surname>
			</person>
		</names>
		<date value="1995-02"/>
		<howpublished>Internet RFC 1760</howpublished>
		<title type="sharef:primaryTitle">The S/KEY One-Time Password System</title>
		<field type="bibtex:topic">skey[1]</field>
	</reference>
	<reference name="rfc1766" src="bibtex:misc" src-info="bibtex:line-41029" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Harald Tveit</givenname>
				<surname>Alvestrand</surname>
			</person>
		</names>
		<date value="1995-03"/>
		<howpublished>Internet RFC 1766</howpublished>
		<title type="sharef:primaryTitle">Tags for the Identification of Languages</title>
	</reference>
	<reference name="rfc1777" src="bibtex:misc" src-info="bibtex:line-41037" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Wengyik</givenname>
				<surname>Yeong</surname>
			</person>
			<person>
				<givenname>Tim</givenname>
				<surname>Howes</surname>
			</person>
			<person>
				<givenname>Steven</givenname>
				<surname>Kille</surname>
			</person>
		</names>
		<date value="1995-03"/>
		<howpublished>Internet RFC 1777</howpublished>
		<title type="sharef:primaryTitle">Lightweight Directory Access Protocol</title>
		<field type="bibtex:topic">ldap[1]</field>
		<field type="bibtex:updates">rfc1487</field>
	</reference>
	<reference name="rfc1778" src="bibtex:misc" src-info="bibtex:line-41047" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Tim</givenname>
				<surname>Howes</surname>
			</person>
			<person>
				<givenname>Steven</givenname>
				<surname>Kille</surname>
			</person>
			<person>
				<givenname>Wengyik</givenname>
				<surname>Yeong</surname>
			</person>
			<person>
				<givenname>Colin</givenname>
				<surname>Robbins</surname>
			</person>
		</names>
		<date value="1995-03"/>
		<howpublished>Internet RFC 1778</howpublished>
		<title type="sharef:primaryTitle">The String Representation of Standard Attribute Syntaxes</title>
		<field type="bibtex:topic">ldap[1]</field>
		<field type="bibtex:updates">rfc1488</field>
	</reference>
	<reference name="rfc1779" src="bibtex:misc" src-info="bibtex:line-41057" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Steven</givenname>
				<surname>Kille</surname>
			</person>
		</names>
		<date value="1995-03"/>
		<howpublished>Internet RFC 1779</howpublished>
		<title type="sharef:primaryTitle">A String Representation of Distinguished Names</title>
		<field type="bibtex:topic">ldap[0.9]</field>
	</reference>
	<reference name="rfc1781" src="bibtex:misc" src-info="bibtex:line-41066" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Steven</givenname>
				<surname>Kille</surname>
			</person>
		</names>
		<date value="1995-03"/>
		<howpublished>Internet RFC 1781</howpublished>
		<field type="bibtex:index">naming, addressing, Directory</field>
		<title type="sharef:primaryTitle">Using the OSI Directory to Achieve User Friendly Naming</title>
	</reference>
	<reference name="rfc1796" src="bibtex:misc" src-info="bibtex:line-41075" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Christian</givenname>
				<surname>Huitema</surname>
			</person>
			<person>
				<givenname>Jon B.</givenname>
				<surname>Postel</surname>
			</person>
			<person>
				<givenname>Steven</givenname>
				<surname>Crocker</surname>
			</person>
		</names>
		<date value="1995-04"/>
		<howpublished>Internet RFC 1796</howpublished>
		<title type="sharef:primaryTitle">Not All RFCs are Standards</title>
		<field type="bibtex:topic">rfc[0.9]</field>
	</reference>
	<reference name="rfc1798" src="bibtex:misc" src-info="bibtex:line-41084" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Alan</givenname>
				<surname>Young</surname>
			</person>
		</names>
		<date value="1995-06"/>
		<howpublished>Internet RFC 1798</howpublished>
		<title type="sharef:primaryTitle">Connection-less Lightweight X.500 Directory Access Protocol</title>
		<field type="bibtex:topic">cldap[1]</field>
	</reference>
	<reference name="rfc1808" src="bibtex:misc" src-info="bibtex:line-41093" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Roy Thomas</givenname>
				<surname>Fielding</surname>
			</person>
		</names>
		<date value="1995-06"/>
		<howpublished>Internet RFC 1808</howpublished>
		<field type="bibtex:index">relative URL</field>
		<title type="sharef:primaryTitle">Relative Uniform Resource Locators</title>
	</reference>
	<reference name="rfc1830" src="bibtex:misc" src-info="bibtex:line-41102" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Gregory M.</givenname>
				<surname>Vaudreuil</surname>
			</person>
		</names>
		<date value="1995-08"/>
		<abstract>
			<richtext>
				<p>This memo defines two extensions to the SMTP service. The first service enables a SMTP client and server to negotiate the use of an alternate DATA command "BDAT" for efficiently sending large MIME messages. The second extension takes advantage of the BDAT command to permit the negotiated sending of unencoded binary data. This memo defines an Experimental Protocol for the Internet community.</p>
			</richtext>
		</abstract>
		<howpublished>Internet RFC 1830</howpublished>
		<title type="sharef:primaryTitle">SMTP Service Extensions for Transmission of Large and Binary MIME Messages</title>
		<field type="bibtex:topic">esmtp[0.9] mime[0.9]</field>
	</reference>
	<reference name="rfc1832" src="bibtex:misc" src-info="bibtex:line-41112" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Raj</givenname>
				<surname>Srinivasan</surname>
			</person>
		</names>
		<date value="1995-08"/>
		<abstract>
			<richtext>
				<p>This document describes the External Data Representation Standard (XDR) protocol as it is currently deployed and accepted.</p>
			</richtext>
		</abstract>
		<howpublished>Internet RFC 1832</howpublished>
		<title type="sharef:primaryTitle">XDR: External Data Representation Standard</title>
		<field type="bibtex:topic">xdr1[1]</field>
	</reference>
	<reference name="rfc1845" src="bibtex:misc" src-info="bibtex:line-41122" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>David H.</givenname>
				<surname>Crocker</surname>
			</person>
			<person>
				<givenname>Ned</givenname>
				<surname>Freed</surname>
			</person>
		</names>
		<date value="1995-09"/>
		<howpublished>Internet RFC 1845</howpublished>
		<field type="bibtex:index">ESMTP, checkpoint, restart</field>
		<title type="sharef:primaryTitle">SMTP Service Extension for Checkpoint/Restart</title>
	</reference>
	<reference name="rfc1847" src="bibtex:misc" src-info="bibtex:line-41131" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Jim</givenname>
				<surname>Galvin</surname>
			</person>
			<person>
				<givenname>Sandy</givenname>
				<surname>Murphy</surname>
			</person>
			<person>
				<givenname>Steven</givenname>
				<surname>Crocker</surname>
			</person>
			<person>
				<givenname>Ned</givenname>
				<surname>Freed</surname>
			</person>
		</names>
		<date value="1995-10"/>
		<howpublished>Internet RFC 1847</howpublished>
		<title type="sharef:primaryTitle">Security Multiparts for MIME: Multipart/Signed and Multipart/Encrypted</title>
		<field type="bibtex:topic">moss[1]</field>
	</reference>
	<reference name="rfc1848" src="bibtex:misc" src-info="bibtex:line-41140" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Steven</givenname>
				<surname>Crocker</surname>
			</person>
			<person>
				<givenname>Ned</givenname>
				<surname>Freed</surname>
			</person>
			<person>
				<givenname>Jim</givenname>
				<surname>Galvin</surname>
			</person>
			<person>
				<givenname>Sandy</givenname>
				<surname>Murphy</surname>
			</person>
		</names>
		<date value="1995-10"/>
		<howpublished>Internet RFC 1848</howpublished>
		<title type="sharef:primaryTitle">MIME Object Security Services</title>
		<field type="bibtex:topic">moss[1]</field>
	</reference>
	<reference name="rfc1864" src="bibtex:misc" src-info="bibtex:line-41149" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>John Gardiner</givenname>
				<surname>Myers</surname>
			</person>
			<person>
				<givenname>Marshall T.</givenname>
				<surname>Rose</surname>
			</person>
		</names>
		<date value="1995-10"/>
		<howpublished>Internet RFC 1864</howpublished>
		<title type="sharef:primaryTitle">The Content-MD5 Header Field</title>
		<field type="bibtex:topic">md5[1]</field>
	</reference>
	<reference name="rfc1866" src="bibtex:misc" src-info="bibtex:line-41158" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Tim</givenname>
				<surname>Berners-Lee</surname>
			</person>
			<person>
				<givenname>Dan</givenname>
				<surname>Connolly</surname>
			</person>
		</names>
		<date value="1995-11"/>
		<howpublished>Internet RFC 1866</howpublished>
		<title type="sharef:primaryTitle">Hypertext Markup Language — 2.0</title>
		<field type="bibtex:topic">html[1]</field>
	</reference>
	<reference name="rfc1867" src="bibtex:misc" src-info="bibtex:line-41167" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Ernesto</givenname>
				<surname>Nebel</surname>
			</person>
			<person>
				<givenname>Larry</givenname>
				<surname>Masinter</surname>
			</person>
		</names>
		<date value="1995-11"/>
		<howpublished>Internet RFC 1867</howpublished>
		<title type="sharef:primaryTitle">Form-based File Upload in HTML</title>
		<field type="bibtex:topic">htmlforms[1] html[0.8]</field>
	</reference>
	<reference name="rfc1869" src="bibtex:misc" src-info="bibtex:line-41176" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>John C.</givenname>
				<surname>Klensin</surname>
			</person>
			<person>
				<givenname>Ned</givenname>
				<surname>Freed</surname>
			</person>
			<person>
				<givenname>Marshall T.</givenname>
				<surname>Rose</surname>
			</person>
			<person>
				<givenname>Einar A.</givenname>
				<surname>Stefferud</surname>
			</person>
			<person>
				<givenname>David H.</givenname>
				<surname>Crocker</surname>
			</person>
		</names>
		<date value="1995-11"/>
		<howpublished>Internet RFC 1869</howpublished>
		<title type="sharef:primaryTitle">SMTP Service Extensions</title>
		<field type="bibtex:topic">smtp[0.8] esmtp[1]</field>
	</reference>
	<reference name="rfc1870" src="bibtex:misc" src-info="bibtex:line-41185" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>John C.</givenname>
				<surname>Klensin</surname>
			</person>
			<person>
				<givenname>Ned</givenname>
				<surname>Freed</surname>
			</person>
			<person>
				<givenname>Keith</givenname>
				<surname>Moore</surname>
			</person>
		</names>
		<date value="1995-11"/>
		<howpublished>Internet RFC 1870</howpublished>
		<field type="bibtex:index">ESMTP, size declaration</field>
		<title type="sharef:primaryTitle">SMTP Service Extension for Message Size Declaration</title>
	</reference>
	<reference name="rfc1874" src="bibtex:misc" src-info="bibtex:line-41194" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Edward</givenname>
				<surname>Levinson</surname>
			</person>
		</names>
		<date value="1995-11"/>
		<howpublished>Internet RFC 1874</howpublished>
		<title type="sharef:primaryTitle">SGML Media Types</title>
		<field type="bibtex:topic">sgml[0.9] mime[0.8]</field>
	</reference>
	<reference name="rfc1883" src="bibtex:misc" src-info="bibtex:line-41203" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Stephen E.</givenname>
				<surname>Deering</surname>
			</person>
			<person>
				<givenname>Robert M.</givenname>
				<surname>Hinden</surname>
			</person>
		</names>
		<date value="1995-12"/>
		<howpublished>Internet RFC 1883</howpublished>
		<field type="bibtex:index">IPv6</field>
		<title type="sharef:primaryTitle">Internet Protocol, Version 6 (IPv6) Specification</title>
	</reference>
	<reference name="rfc1889" src="bibtex:misc" src-info="bibtex:line-41212" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Henning</givenname>
				<surname>Schulzrinne</surname>
			</person>
			<person>
				<givenname>Stephen L.</givenname>
				<surname>Casner</surname>
			</person>
			<person>
				<givenname>Ron</givenname>
				<surname>Frederick</surname>
			</person>
			<person>
				<givenname>Van</givenname>
				<surname>Jacobson</surname>
			</person>
		</names>
		<date value="1996-01"/>
		<howpublished>Internet RFC 1889</howpublished>
		<title type="sharef:primaryTitle">RTP: A Transport Protocol for Real-Time Applications</title>
		<field type="bibtex:topic">rtp[1]</field>
	</reference>
	<reference name="rfc1900" src="bibtex:misc" src-info="bibtex:line-41221" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Brian E.</givenname>
				<surname>Carpenter</surname>
			</person>
			<person>
				<givenname>Yakov</givenname>
				<surname>Rekhter</surname>
			</person>
		</names>
		<date value="1996-02"/>
		<howpublished>Internet RFC 1900</howpublished>
		<field type="bibtex:index">IP, DNS</field>
		<title type="sharef:primaryTitle">Renumbering Needs Work</title>
	</reference>
	<reference name="rfc1911" src="bibtex:misc" src-info="bibtex:line-41230" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Gregory M.</givenname>
				<surname>Vaudreuil</surname>
			</person>
		</names>
		<date value="1996-02"/>
		<howpublished>Internet RFC 1911</howpublished>
		<title type="sharef:primaryTitle">Voice Profile for Internet Mail</title>
	</reference>
	<reference name="rfc1938" src="bibtex:misc" src-info="bibtex:line-41238" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Neil</givenname>
				<surname>Haller</surname>
			</person>
			<person>
				<givenname>Craig</givenname>
				<surname>Metz</surname>
			</person>
		</names>
		<date value="1996-05"/>
		<howpublished>Internet RFC 1938</howpublished>
		<title type="sharef:primaryTitle">A One-Time Password System</title>
		<field type="bibtex:topic">otp[1]</field>
		<field type="bibtex:updates">rfc1760</field>
	</reference>
	<reference name="rfc1939" src="bibtex:misc" src-info="bibtex:line-41248" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>John Gardiner</givenname>
				<surname>Myers</surname>
			</person>
			<person>
				<givenname>Marshall T.</givenname>
				<surname>Rose</surname>
			</person>
		</names>
		<date value="1996-05"/>
		<howpublished>Internet RFC 1939</howpublished>
		<title type="sharef:primaryTitle">Post Office Protocol — Version 3</title>
		<field type="bibtex:topic">pop[1] apop[1]</field>
	</reference>
	<reference name="rfc1942" src="bibtex:misc" src-info="bibtex:line-41257" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Dave</givenname>
				<surname>Raggett</surname>
			</person>
		</names>
		<date value="1996-05"/>
		<howpublished>Internet RFC 1942</howpublished>
		<title type="sharef:primaryTitle">HTML Tables</title>
		<field type="bibtex:topic">html[0.8]</field>
	</reference>
	<reference name="rfc1945" src="bibtex:misc" src-info="bibtex:line-41266" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Tim</givenname>
				<surname>Berners-Lee</surname>
			</person>
			<person>
				<givenname>Roy Thomas</givenname>
				<surname>Fielding</surname>
			</person>
			<person>
				<givenname>Henrik</givenname>
				<surname>Frystyk Nielsen</surname>
			</person>
		</names>
		<date value="1996-05"/>
		<howpublished>Internet RFC 1945</howpublished>
		<title type="sharef:primaryTitle">Hypertext Transfer Protocol — HTTP/1.0</title>
		<field type="bibtex:topic">http[1]</field>
	</reference>
	<reference name="rfc1950" src="bibtex:misc" src-info="bibtex:line-41275" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>L. Peter</givenname>
				<surname>Deutsch</surname>
			</person>
			<person>
				<givenname>Jean-Loup</givenname>
				<surname>Gailly</surname>
			</person>
		</names>
		<date value="1996-05"/>
		<howpublished>Internet RFC 1950</howpublished>
		<field type="bibtex:index">zlib</field>
		<title type="sharef:primaryTitle">ZLIB Compressed Data Format Specification version 3.3</title>
	</reference>
	<reference name="rfc1951" src="bibtex:misc" src-info="bibtex:line-41284" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>L. Peter</givenname>
				<surname>Deutsch</surname>
			</person>
		</names>
		<date value="1996-05"/>
		<howpublished>Internet RFC 1951</howpublished>
		<title type="sharef:primaryTitle">DEFLATE Compressed Data Format Specification version 1.3</title>
		<field type="bibtex:topic">deflate[1]</field>
	</reference>
	<reference name="rfc1952" src="bibtex:misc" src-info="bibtex:line-41293" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>L. Peter</givenname>
				<surname>Deutsch</surname>
			</person>
		</names>
		<date value="1996-05"/>
		<howpublished>Internet RFC 1952</howpublished>
		<field type="bibtex:index">gzip</field>
		<title type="sharef:primaryTitle">GZIP file format specification version 4.3</title>
	</reference>
	<reference name="rfc1957" src="bibtex:misc" src-info="bibtex:line-41302" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Russell</givenname>
				<surname>Nelson</surname>
			</person>
		</names>
		<date value="1996-06"/>
		<howpublished>Internet RFC 1957</howpublished>
		<title type="sharef:primaryTitle">Some Observations on Implementations of the Post Office Protocol (POP3)</title>
		<field type="bibtex:topic">pop[0.9]</field>
	</reference>
	<reference name="rfc1959" src="bibtex:misc" src-info="bibtex:line-41311" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Tim</givenname>
				<surname>Howes</surname>
			</person>
			<person>
				<givenname>Mark</givenname>
				<surname>Smith</surname>
			</person>
		</names>
		<date value="1996-06"/>
		<howpublished>Internet RFC 1959</howpublished>
		<title type="sharef:primaryTitle">An LDAP URL Format</title>
		<field type="bibtex:topic">ldap[0.9] url[0.8]</field>
	</reference>
	<reference name="rfc1962" src="bibtex:misc" src-info="bibtex:line-41320" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Dave</givenname>
				<surname>Rand</surname>
			</person>
		</names>
		<date value="1996-06"/>
		<howpublished>Internet RFC 1962</howpublished>
		<title type="sharef:primaryTitle">The PPP Compression Control Protocol (CCP)</title>
		<field type="bibtex:topic">ccp[1] ppp[0.9]</field>
	</reference>
	<reference name="rfc1980" src="bibtex:misc" src-info="bibtex:line-41329" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>James L.</givenname>
				<surname>Seidman</surname>
			</person>
		</names>
		<date value="1996-08"/>
		<howpublished>Internet RFC 1980</howpublished>
		<title type="sharef:primaryTitle">A Proposed Extension to HTML: Client-Side Image Maps</title>
		<field type="bibtex:topic">html[0.9]</field>
	</reference>
	<reference name="rfc1994" src="bibtex:misc" src-info="bibtex:line-41338" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>William Allen</givenname>
				<surname>Simpson</surname>
			</person>
		</names>
		<date value="1996-08"/>
		<howpublished>Internet RFC 1994</howpublished>
		<title type="sharef:primaryTitle">PPP Challenge Handshake Authentication Protocol (CHAP)</title>
		<field type="bibtex:topic">ppp[0.9] chap[1]</field>
	</reference>
	<reference name="rfc1996" src="bibtex:misc" src-info="bibtex:line-41347" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Paul</givenname>
				<surname>Vixie</surname>
			</person>
		</names>
		<date value="1996-08"/>
		<howpublished>Internet RFC 1996</howpublished>
		<title type="sharef:primaryTitle">A Mechanism for Prompt Notification of Zone Changes (DNS NOTIFY)</title>
		<field type="bibtex:topic">dns[0.9]</field>
	</reference>
	<reference name="rfc2000" src="bibtex:misc" src-info="bibtex:line-41356" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Jon B.</givenname>
				<surname>Postel</surname>
			</person>
		</names>
		<date value="1997-02"/>
		<howpublished>Internet RFC 2000</howpublished>
		<title type="sharef:primaryTitle">Internet Official Protocol Standards</title>
		<field type="bibtex:topic">rfc[0.9]</field>
	</reference>
	<reference name="rfc2001" src="bibtex:misc" src-info="bibtex:line-41365" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>W. Richard</givenname>
				<surname>Stevens</surname>
			</person>
		</names>
		<date value="1997-01"/>
		<howpublished>Internet RFC 2001</howpublished>
		<title type="sharef:primaryTitle">TCP Slow Start, Congestion Avoidance, Fast Retransmit, and Fast Recovery Algorithms</title>
		<field type="bibtex:topic">tcp[0.9]</field>
	</reference>
	<reference name="rfc2026" src="bibtex:misc" src-info="bibtex:line-41374" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Scott O.</givenname>
				<surname>Bradner</surname>
			</person>
		</names>
		<date value="1996-03"/>
		<howpublished>Internet RFC 2026</howpublished>
		<title type="sharef:primaryTitle">The Internet Standards Process — Revision 3</title>
		<field type="bibtex:topic">rfc[1]</field>
		<field type="bibtex:updates">rfc1602</field>
	</reference>
	<reference name="rfc2030" src="bibtex:misc" src-info="bibtex:line-41384" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>David L.</givenname>
				<surname>Mills</surname>
			</person>
		</names>
		<date value="1996-10"/>
		<howpublished>Internet RFC 2030</howpublished>
		<title type="sharef:primaryTitle">Simple Network Time Protocol (SNTP) Version 4 for IPv4, IPv6 and OSI</title>
		<field type="bibtex:topic">sntp[1]</field>
	</reference>
	<reference name="rfc2045" src="bibtex:misc" src-info="bibtex:line-41393" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Ned</givenname>
				<surname>Freed</surname>
			</person>
			<person>
				<givenname>Nathaniel S.</givenname>
				<surname>Borenstein</surname>
			</person>
		</names>
		<date value="1996-11"/>
		<howpublished>Internet RFC 2045</howpublished>
		<title type="sharef:primaryTitle">Multipurpose Internet Mail Extensions (MIME) — Part One: Format of Internet Message Bodies</title>
		<field type="bibtex:topic">mime[1]</field>
		<field type="bibtex:updates">rfc1521 rfc1522</field>
	</reference>
	<reference name="rfc2046" src="bibtex:misc" src-info="bibtex:line-41403" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Ned</givenname>
				<surname>Freed</surname>
			</person>
			<person>
				<givenname>Nathaniel S.</givenname>
				<surname>Borenstein</surname>
			</person>
		</names>
		<date value="1996-11"/>
		<howpublished>Internet RFC 2046</howpublished>
		<title type="sharef:primaryTitle">Multipurpose Internet Mail Extensions (MIME) — Part Two: Media Types</title>
		<field type="bibtex:topic">mime[1] base64[1]</field>
		<field type="bibtex:updates">rfc1521 rfc1522</field>
	</reference>
	<reference name="rfc2047" src="bibtex:misc" src-info="bibtex:line-41413" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Keith</givenname>
				<surname>Moore</surname>
			</person>
		</names>
		<date value="1996-11"/>
		<howpublished>Internet RFC 2047</howpublished>
		<title type="sharef:primaryTitle">Multipurpose Internet Mail Extensions (MIME) — Part Three: Message Header Extensions for Non-ASCII Text</title>
		<field type="bibtex:topic">mime[1]</field>
		<field type="bibtex:updates">rfc1521 rfc1522</field>
	</reference>
	<reference name="rfc2048" src="bibtex:misc" src-info="bibtex:line-41423" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Ned</givenname>
				<surname>Freed</surname>
			</person>
			<person>
				<givenname>John C.</givenname>
				<surname>Klensin</surname>
			</person>
			<person>
				<givenname>Jon B.</givenname>
				<surname>Postel</surname>
			</person>
		</names>
		<date value="1996-11"/>
		<howpublished>Internet RFC 2048</howpublished>
		<title type="sharef:primaryTitle">Multipurpose Internet Mail Extensions (MIME) — Part Four: Registration Procedures</title>
		<field type="bibtex:topic">mime[1]</field>
		<field type="bibtex:updates">rfc1521 rfc1522</field>
	</reference>
	<reference name="rfc2049" src="bibtex:misc" src-info="bibtex:line-41433" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Ned</givenname>
				<surname>Freed</surname>
			</person>
			<person>
				<givenname>Nathaniel S.</givenname>
				<surname>Borenstein</surname>
			</person>
		</names>
		<date value="1996-11"/>
		<howpublished>Internet RFC 2049</howpublished>
		<title type="sharef:primaryTitle">Multipurpose Internet Mail Extensions (MIME) — Part Five: Conformance Criteria and Examples</title>
		<field type="bibtex:topic">mime[1]</field>
		<field type="bibtex:updates">rfc1521 rfc1522</field>
	</reference>
	<reference name="rfc2056" src="bibtex:misc" src-info="bibtex:line-41443" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Ray</givenname>
				<surname>Denenberg</surname>
			</person>
			<person>
				<givenname>John A.</givenname>
				<surname>Kunze</surname>
			</person>
			<person>
				<givenname>Denis</givenname>
				<surname>Lynch</surname>
			</person>
		</names>
		<date value="1996-11"/>
		<howpublished>Internet RFC 2056</howpublished>
		<title type="sharef:primaryTitle">Uniform Resource Locators for Z39.50</title>
		<field type="bibtex:topic">url[0.9] z3950[0.9]</field>
	</reference>
	<reference name="rfc2058" src="bibtex:misc" src-info="bibtex:line-41452" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Carl</givenname>
				<surname>Rigney</surname>
			</person>
			<person>
				<givenname>Allan C.</givenname>
				<surname>Rubens</surname>
			</person>
			<person>
				<givenname>William Allen</givenname>
				<surname>Simpson</surname>
			</person>
			<person>
				<givenname>Steve</givenname>
				<surname>Willens</surname>
			</person>
		</names>
		<date value="1997-01"/>
		<howpublished>Internet RFC 2058</howpublished>
		<title type="sharef:primaryTitle">Remote Authentication Dial In User Service (RADIUS)</title>
		<field type="bibtex:topic">radius[1]</field>
	</reference>
	<reference name="rfc2059" src="bibtex:misc" src-info="bibtex:line-41461" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Carl</givenname>
				<surname>Rigney</surname>
			</person>
		</names>
		<date value="1997-01"/>
		<howpublished>Internet RFC 2059</howpublished>
		<title type="sharef:primaryTitle">RADIUS Accounting</title>
		<field type="bibtex:topic">radius[0.9]</field>
	</reference>
	<reference name="rfc2060" src="bibtex:misc" src-info="bibtex:line-41470" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Mark R.</givenname>
				<surname>Crispin</surname>
			</person>
		</names>
		<date value="1996-12"/>
		<howpublished>Internet RFC 2060</howpublished>
		<title type="sharef:primaryTitle">Internet Message Access Protocol — Version 4rev1</title>
		<field type="bibtex:topic">imap[1]</field>
	</reference>
	<reference name="rfc2065" src="bibtex:misc" src-info="bibtex:line-41479" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Donald E.</givenname>
				<surname>Eastlake</surname>
			</person>
			<person>
				<givenname>Charles W.</givenname>
				<surname>Kaufman</surname>
			</person>
		</names>
		<date value="1997-01"/>
		<howpublished>Internet RFC 2065</howpublished>
		<field type="bibtex:index">DNS</field>
		<title type="sharef:primaryTitle">Domain Name System Security Extensions</title>
	</reference>
	<reference name="rfc2068" src="bibtex:misc" src-info="bibtex:line-41488" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Roy Thomas</givenname>
				<surname>Fielding</surname>
			</person>
			<person>
				<givenname>Jim</givenname>
				<surname>Gettys</surname>
			</person>
			<person>
				<givenname>Jeffrey C.</givenname>
				<surname>Mogul</surname>
			</person>
			<person>
				<givenname>Henrik</givenname>
				<surname>Frystyk Nielsen</surname>
			</person>
			<person>
				<givenname>Tim</givenname>
				<surname>Berners-Lee</surname>
			</person>
		</names>
		<date value="1998-11"/>
		<howpublished>Internet RFC 2068</howpublished>
		<title type="sharef:primaryTitle">Hypertext Transfer Protocol — HTTP/1.1</title>
		<field type="bibtex:topic">http[1]</field>
		<field type="bibtex:updates">rfc1945</field>
	</reference>
	<reference name="rfc2069" src="bibtex:misc" src-info="bibtex:line-41498" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>John</givenname>
				<surname>Franks</surname>
			</person>
			<person>
				<givenname>Phillip M.</givenname>
				<surname>Hallam-Baker</surname>
			</person>
			<person>
				<givenname>Jeffery L.</givenname>
				<surname>Hostetler</surname>
			</person>
			<person>
				<givenname>Paul J.</givenname>
				<surname>Leach</surname>
			</person>
			<person>
				<givenname>Ari</givenname>
				<surname>Luotonen</surname>
			</person>
			<person>
				<givenname>Eric W.</givenname>
				<surname>Sink</surname>
			</person>
			<person>
				<givenname>Lawrence C.</givenname>
				<surname>Stewart</surname>
			</person>
		</names>
		<date value="1997-01"/>
		<howpublished>Internet RFC 2069</howpublished>
		<title type="sharef:primaryTitle">An Extension to HTTP: Digest Access Authentication</title>
		<field type="bibtex:topic">http[0.9] daauth[1]</field>
	</reference>
	<reference name="rfc2070" src="bibtex:misc" src-info="bibtex:line-41507" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>François</givenname>
				<surname>Yergeau</surname>
			</person>
			<person>
				<givenname>Gavin Thomas</givenname>
				<surname>Nicol</surname>
			</person>
			<person>
				<givenname>Glenn</givenname>
				<surname>Adams</surname>
			</person>
			<person>
				<givenname>Martin J.</givenname>
				<surname>Dürst</surname>
			</person>
		</names>
		<date value="1997-01"/>
		<howpublished>Internet RFC 2070</howpublished>
		<title type="sharef:primaryTitle">Internationalization of the Hypertext Markup Language</title>
		<field type="bibtex:topic">html[0.9] i18n[0.9]</field>
	</reference>
	<reference name="rfc2077" src="bibtex:misc" src-info="bibtex:line-41516" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>S.</givenname>
				<surname>Nelson</surname>
			</person>
			<person>
				<givenname>C.</givenname>
				<surname>Parks</surname>
			</person>
		</names>
		<date value="1997-01"/>
		<howpublished>Internet RFC 2077</howpublished>
		<field type="bibtex:index">MIME, VRML</field>
		<title type="sharef:primaryTitle">The Model Primary Content Type for Multipurpose Internet Mail Extensions</title>
	</reference>
	<reference name="rfc2083" src="bibtex:misc" src-info="bibtex:line-41525" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Thomas</givenname>
				<surname>Boutell</surname>
			</person>
		</names>
		<date value="1997-03"/>
		<howpublished>Internet RFC 2083</howpublished>
		<field type="bibtex:index">PNG</field>
		<title type="sharef:primaryTitle">PNG (Portable Network Graphics) Specification — Version 1.0</title>
	</reference>
	<reference name="rfc2104" src="bibtex:misc" src-info="bibtex:line-41534" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Hugo</givenname>
				<surname>Krawczyk</surname>
			</person>
			<person>
				<givenname>Mihir</givenname>
				<surname>Bellare</surname>
			</person>
			<person>
				<givenname>Ran</givenname>
				<surname>Canetti</surname>
			</person>
		</names>
		<date value="1997-02"/>
		<howpublished>Internet RFC 2104</howpublished>
		<title type="sharef:primaryTitle">HMAC: Keyed-Hashing for Message Authentication</title>
		<field type="bibtex:topic">hmac[1]</field>
		<identifier type="sharef:uri" resourceType="text/html">http://www-cse.ucsd.edu/users/mihir/papers/hmac.html</identifier>
	</reference>
	<reference name="rfc2109" src="bibtex:misc" src-info="bibtex:line-41544" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>David M.</givenname>
				<surname>Kristol</surname>
			</person>
			<person>
				<givenname>Lou</givenname>
				<surname>Montulli</surname>
			</person>
		</names>
		<date value="1997-02"/>
		<howpublished>Internet RFC 2109</howpublished>
		<title type="sharef:primaryTitle">HTTP State Management Mechanism</title>
		<field type="bibtex:topic">http[0.9] cookie[1]</field>
		<field type="bibtex:updates">kri99</field>
	</reference>
	<reference name="rfc2110" src="bibtex:misc" src-info="bibtex:line-41554" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Jacob</givenname>
				<surname>Palme</surname>
			</person>
			<person>
				<givenname>Alex</givenname>
				<surname>Hopmann</surname>
			</person>
		</names>
		<date value="1997-03"/>
		<howpublished>Internet RFC 2110</howpublished>
		<title type="sharef:primaryTitle">MIME E-mail Encapsulation of Aggregate Documents, such as HTML (MHTML)</title>
		<field type="bibtex:topic">mhtml[1] mime[0.7] html[0.7]</field>
	</reference>
	<reference name="rfc2111" src="bibtex:misc" src-info="bibtex:line-41563" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Edward</givenname>
				<surname>Levinson</surname>
			</person>
		</names>
		<date value="1997-03"/>
		<howpublished>Internet RFC 2111</howpublished>
		<title type="sharef:primaryTitle">Content-ID and Message-ID Uniform Resource Locators</title>
		<field type="bibtex:topic">url[0.9]</field>
	</reference>
	<reference name="rfc2119" src="bibtex:misc" src-info="bibtex:line-41572" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Scott O.</givenname>
				<surname>Bradner</surname>
			</person>
		</names>
		<date value="1997-03"/>
		<howpublished>Internet RFC 2119</howpublished>
		<title type="sharef:primaryTitle">Key Words for use in RFCs to Indicate Requirement Levels</title>
		<field type="bibtex:topic">rfc[0.9]</field>
	</reference>
	<reference name="rfc2136" src="bibtex:misc" src-info="bibtex:line-41581" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Paul</givenname>
				<surname>Vixie</surname>
			</person>
			<person>
				<givenname>Susan</givenname>
				<surname>Thomson</surname>
			</person>
			<person>
				<givenname>Yakov</givenname>
				<surname>Rekhter</surname>
			</person>
			<person>
				<givenname>Jim</givenname>
				<surname>Bound</surname>
			</person>
		</names>
		<date value="1997-04"/>
		<howpublished>Internet RFC 2136</howpublished>
		<title type="sharef:primaryTitle">Dynamic Updates in the Domain Name System (DNS UPDATE)</title>
		<field type="bibtex:topic">dns[1]</field>
	</reference>
	<reference name="rfc2137" src="bibtex:misc" src-info="bibtex:line-41590" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Donald E.</givenname>
				<surname>Eastlake</surname>
			</person>
		</names>
		<date value="1997-04"/>
		<howpublished>Internet RFC 2137</howpublished>
		<title type="sharef:primaryTitle">Secure Domain Name System Dynamic Update</title>
		<field type="bibtex:topic">dns[1]</field>
	</reference>
	<reference name="rfc2138" src="bibtex:misc" src-info="bibtex:line-41599" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Carl</givenname>
				<surname>Rigney</surname>
			</person>
			<person>
				<givenname>Allan C.</givenname>
				<surname>Rubens</surname>
			</person>
			<person>
				<givenname>William Allen</givenname>
				<surname>Simpson</surname>
			</person>
			<person>
				<givenname>Steve</givenname>
				<surname>Willens</surname>
			</person>
		</names>
		<date value="1997-04"/>
		<howpublished>Internet RFC 2138</howpublished>
		<title type="sharef:primaryTitle">Remote Authentication Dial In User Service (RADIUS)</title>
		<field type="bibtex:topic">radius[1]</field>
		<field type="bibtex:updates">rfc2058</field>
	</reference>
	<reference name="rfc2139" src="bibtex:misc" src-info="bibtex:line-41609" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Carl</givenname>
				<surname>Rigney</surname>
			</person>
		</names>
		<date value="1997-04"/>
		<howpublished>Internet RFC 2139</howpublished>
		<title type="sharef:primaryTitle">RADIUS Accounting</title>
		<field type="bibtex:topic">radius[0.9]</field>
		<field type="bibtex:updates">rfc2059</field>
	</reference>
	<reference name="rfc2141" src="bibtex:misc" src-info="bibtex:line-41619" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Ryan</givenname>
				<surname>Moats</surname>
			</person>
		</names>
		<date value="1997-05"/>
		<howpublished>Internet RFC 2141</howpublished>
		<title type="sharef:primaryTitle">URN Syntax</title>
		<field type="bibtex:topic">urn[1]</field>
	</reference>
	<reference name="rfc2143" src="bibtex:misc" src-info="bibtex:line-41628" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Ben</givenname>
				<surname>Elliston</surname>
			</person>
		</names>
		<date value="1997-05"/>
		<howpublished>Internet RFC 2143</howpublished>
		<title type="sharef:primaryTitle">Encapsulating IP with the Small Computer System Interface</title>
		<field type="bibtex:topic">scsi[0.7] ip[0.7]</field>
	</reference>
	<reference name="rfc2145" src="bibtex:misc" src-info="bibtex:line-41637" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Jeffrey C.</givenname>
				<surname>Mogul</surname>
			</person>
			<person>
				<givenname>Roy Thomas</givenname>
				<surname>Fielding</surname>
			</person>
			<person>
				<givenname>Jim</givenname>
				<surname>Gettys</surname>
			</person>
			<person>
				<givenname>Henrik</givenname>
				<surname>Frystyk Nielsen</surname>
			</person>
		</names>
		<date value="1997-05"/>
		<abstract>
			<richtext>
				<p>HTTP request and response messages include an HTTP protocol version number. Some confusion exists concerning the proper use and interpretation of HTTP version numbers, and concerning interoperability of HTTP implementations of different protocol versions. This document is an attempt to clarify the situation. It is not a modification of the intended meaning of the existing HTTP/1.0 and HTTP/1.1 documents, but it does describe the intention of the authors of those documents, and can be considered definitive when there is any ambiguity in those documents concerning HTTP version numbers, for all versions of HTTP.</p>
			</richtext>
		</abstract>
		<howpublished>Internet RFC 2145</howpublished>
		<title type="sharef:primaryTitle">Use and Interpretation of HTTP Version Numbers</title>
		<field type="bibtex:topic">http[0.9]</field>
	</reference>
	<reference name="rfc2152" src="bibtex:misc" src-info="bibtex:line-41647" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>David</givenname>
				<surname>Goldsmith</surname>
			</person>
			<person>
				<givenname>Mark</givenname>
				<surname>Davis</surname>
			</person>
		</names>
		<date value="1997-05"/>
		<abstract>
			<richtext>
				<p>The Unicode Standard, version 2.0, and ISO/IEC 10646-1:1993(E) (as amended) jointly define a character set (hereafter referred to as Unicode) which encompasses most of the world's writing systems. However, Internet mail (STD 11, RFC 822) currently supports only 7-bit US ASCII as a character set. MIME (RFC 2045 through 2049) extends Internet mail to support different media types and character sets, and thus could support Unicode in mail messages. MIME neither defines Unicode as a permitted character set nor specifies how it would be encoded, although it does provide for the registration of additional character sets over time. This document describes a transformation format of Unicode that contains only 7-bit ASCII octets and is intended to be readable by humans in the limiting case that the document consists of characters from the US-ASCII repertoire. It also specifies how this transformation format is used in the context of MIME and RFC 1641, "Using Unicode with MIME".</p>
			</richtext>
		</abstract>
		<howpublished>Internet RFC 2152</howpublished>
		<title type="sharef:primaryTitle">UTF-7: A Mail-Safe Transformation Format of Unicode</title>
		<field type="bibtex:topic">utf7[1] unicode[0.8]</field>
	</reference>
	<reference name="rfc2168" src="bibtex:misc" src-info="bibtex:line-41657" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Ron</givenname>
				<surname>Daniel</surname>
			</person>
			<person>
				<givenname>Michael</givenname>
				<surname>Mealling</surname>
			</person>
		</names>
		<date value="1997-06"/>
		<howpublished>Internet RFC 2168</howpublished>
		<field type="bibtex:index">URN, DNS</field>
		<title type="sharef:primaryTitle">Resolution of Uniform Resource Identifiers using the Domain Name System</title>
	</reference>
	<reference name="rfc2169" src="bibtex:misc" src-info="bibtex:line-41666" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Ron</givenname>
				<surname>Daniel</surname>
			</person>
		</names>
		<date value="1997-06"/>
		<howpublished>Internet RFC 2169</howpublished>
		<title type="sharef:primaryTitle">A Trivial Convention for using HTTP in URN Resolution</title>
		<field type="bibtex:topic">thttp[1] urn[0.7]</field>
	</reference>
	<reference name="rfc2181" src="bibtex:misc" src-info="bibtex:line-41675" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Robert</givenname>
				<surname>Elz</surname>
			</person>
			<person>
				<givenname>Randy</givenname>
				<surname>Bush</surname>
			</person>
		</names>
		<date value="1997-07"/>
		<abstract>
			<richtext>
				<p>This document considers some areas that have been identified as problems with the specification of the Domain Name System, and proposes remedies for the defects identified. Eight separate issues are considered: (1) IP packet header address usage from multi-homed servers, (2) TTLs in sets of records with the same name, class, and type, (3) correct handling of zone cuts, (4) three minor issues concerning SOA records and their use, (5) the precise definition of the Time to Live (TTL) (6) Use of the TC (truncated) header bit (7) the issue of what is an authoritative, or canonical, name, (8) and the issue of what makes a valid DNS label. The first six of these are areas where the correct behaviour has been somewhat unclear, we seek to rectify that. The other two are already adequately specified, however the specifications seem to be sometimes ignored. We seek to reinforce the existing specifications.</p>
			</richtext>
		</abstract>
		<howpublished>Internet RFC 2181</howpublished>
		<title type="sharef:primaryTitle">Clarifications to the DNS Specification</title>
		<field type="bibtex:topic">dns[0.8]</field>
	</reference>
	<reference name="rfc2183" src="bibtex:misc" src-info="bibtex:line-41685" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Rens</givenname>
				<surname>Troost</surname>
			</person>
			<person>
				<givenname>Steve</givenname>
				<surname>Dorner</surname>
			</person>
			<person>
				<givenname>Keith</givenname>
				<surname>Moore</surname>
			</person>
		</names>
		<date value="1997-08"/>
		<howpublished>Internet RFC 2183</howpublished>
		<title type="sharef:primaryTitle">Communicating Presentation Information in Internet Messages: The Content-Disposition Header Field</title>
		<field type="bibtex:topic">mime[0.8]</field>
	</reference>
	<reference name="rfc2192" src="bibtex:misc" src-info="bibtex:line-41694" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Chris</givenname>
				<surname>Newman</surname>
			</person>
		</names>
		<date value="1997-09"/>
		<howpublished>Internet RFC 2192</howpublished>
		<title type="sharef:primaryTitle">IMAP URL scheme</title>
		<field type="bibtex:topic">url[0.8] imap[0.9]</field>
	</reference>
	<reference name="rfc2231" src="bibtex:misc" src-info="bibtex:line-41703" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Ned</givenname>
				<surname>Freed</surname>
			</person>
			<person>
				<givenname>Keith</givenname>
				<surname>Moore</surname>
			</person>
		</names>
		<date value="1997-11"/>
		<howpublished>Internet RFC 2231</howpublished>
		<title type="sharef:primaryTitle">MIME Parameter Value and Encoded Word Extensions: Character Sets, Languages, and Continuations</title>
		<field type="bibtex:topic">mime[0.8]</field>
		<field type="bibtex:updates">rfc2183 rfc2045 rfc2047</field>
	</reference>
	<reference name="rfc2234" src="bibtex:misc" src-info="bibtex:line-41713" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>David H.</givenname>
				<surname>Crocker</surname>
			</person>
			<person>
				<givenname>Paul</givenname>
				<surname>Overell</surname>
			</person>
		</names>
		<date value="1997-11"/>
		<howpublished>Internet RFC 2234</howpublished>
		<title type="sharef:primaryTitle">Augmented BNF for Syntax Specifications: ABNF</title>
		<field type="bibtex:topic">abnf[1]</field>
	</reference>
	<reference name="rfc2235" src="bibtex:misc" src-info="bibtex:line-41722" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Robert H.</givenname>
				<surname>Zakon</surname>
			</person>
		</names>
		<date value="1997-11"/>
		<howpublished>Internet RFC 2235</howpublished>
		<field type="bibtex:index">Internet</field>
		<title type="sharef:primaryTitle">Hobbes' Internet Timeline</title>
	</reference>
	<reference name="rfc2244" src="bibtex:misc" src-info="bibtex:line-41731" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Chris</givenname>
				<surname>Newman</surname>
			</person>
			<person>
				<givenname>John Gardiner</givenname>
				<surname>Myers</surname>
			</person>
		</names>
		<date value="1997-11"/>
		<howpublished>Internet RFC 2244</howpublished>
		<field type="bibtex:index">ACAP</field>
		<title type="sharef:primaryTitle">ACAP — Application Configuration Access Protocol</title>
	</reference>
	<reference name="rfc2246" src="bibtex:misc" src-info="bibtex:line-41740" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Christopher</givenname>
				<surname>Allen</surname>
			</person>
			<person>
				<givenname>Tim</givenname>
				<surname>Dierks</surname>
			</person>
		</names>
		<date value="1999-01"/>
		<abstract>
			<richtext>
				<p>This document specifies Version 1.0 of the Transport Layer Security (TLS) protocol. The TLS protocol provides communications privacy over the Internet. The protocol allows client/server applications to communicate in a way that is designed to prevent eavesdropping, tampering, or message forgery.</p>
			</richtext>
		</abstract>
		<howpublished>Internet RFC 2246</howpublished>
		<title type="sharef:primaryTitle">The TLS Protocol — Version 1.0</title>
		<field type="bibtex:topic">tls[1]</field>
	</reference>
	<reference name="rfc2251" src="bibtex:misc" src-info="bibtex:line-41750" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Mark</givenname>
				<surname>Wahl</surname>
			</person>
			<person>
				<givenname>Tim</givenname>
				<surname>Howes</surname>
			</person>
			<person>
				<givenname>Steven</givenname>
				<surname>Kille</surname>
			</person>
		</names>
		<date value="1997-12"/>
		<howpublished>Internet RFC 2251</howpublished>
		<title type="sharef:primaryTitle">Lightweight Directory Access Protocol (v3)</title>
		<field type="bibtex:topic">ldap[1]</field>
		<field type="bibtex:updates">rfc1777</field>
	</reference>
	<reference name="rfc2252" src="bibtex:misc" src-info="bibtex:line-41760" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Mark</givenname>
				<surname>Wahl</surname>
			</person>
			<person>
				<givenname>Andy</givenname>
				<surname>Coulbeck</surname>
			</person>
			<person>
				<givenname>Tim</givenname>
				<surname>Howes</surname>
			</person>
			<person>
				<givenname>Steven</givenname>
				<surname>Kille</surname>
			</person>
		</names>
		<date value="1997-12"/>
		<howpublished>Internet RFC 2252</howpublished>
		<title type="sharef:primaryTitle">Lightweight Directory Access Protocol (v3): Attribute Syntax Definitions</title>
		<field type="bibtex:topic">ldap[1]</field>
		<field type="bibtex:updates">rfc1778</field>
	</reference>
	<reference name="rfc2253" src="bibtex:misc" src-info="bibtex:line-41770" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Mark</givenname>
				<surname>Wahl</surname>
			</person>
			<person>
				<givenname>Steven</givenname>
				<surname>Kille</surname>
			</person>
			<person>
				<givenname>Tim</givenname>
				<surname>Howes</surname>
			</person>
		</names>
		<date value="1997-12"/>
		<howpublished>Internet RFC 2253</howpublished>
		<title type="sharef:primaryTitle">Lightweight Directory Access Protocol (v3): UTF-8 String Representation of Distinguished Names</title>
		<field type="bibtex:topic">ldap[0.9]</field>
		<field type="bibtex:updates">rfc1779</field>
	</reference>
	<reference name="rfc2255" src="bibtex:misc" src-info="bibtex:line-41780" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Tim</givenname>
				<surname>Howes</surname>
			</person>
			<person>
				<givenname>Mark</givenname>
				<surname>Smith</surname>
			</person>
		</names>
		<date value="1997-12"/>
		<howpublished>Internet RFC 2255</howpublished>
		<title type="sharef:primaryTitle">The LDAP URL Format</title>
		<field type="bibtex:topic">ldap[0.9] url[0.8]</field>
		<field type="bibtex:updates">rfc1959</field>
	</reference>
	<reference name="rfc2276" src="bibtex:misc" src-info="bibtex:line-41790" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Karen R.</givenname>
				<surname>Sollins</surname>
			</person>
		</names>
		<date value="1998-01"/>
		<howpublished>Internet RFC 2276</howpublished>
		<field type="bibtex:index">URI, URN, URL, URC</field>
		<title type="sharef:primaryTitle">Architectural Principles of Uniform Resource Name Resolution</title>
	</reference>
	<reference name="rfc2279" src="bibtex:misc" src-info="bibtex:line-41799" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>François</givenname>
				<surname>Yergeau</surname>
			</person>
		</names>
		<date value="1998-01"/>
		<howpublished>Internet RFC 2279</howpublished>
		<title type="sharef:primaryTitle">UTF-8, a transformation format of ISO 10646</title>
		<field type="bibtex:topic">utf8[1] ucs[0.8]</field>
	</reference>
	<reference name="rfc2284" src="bibtex:misc" src-info="bibtex:line-41808" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Larry J.</givenname>
				<surname>Blunk</surname>
			</person>
			<person>
				<givenname>John R.</givenname>
				<surname>Vollbrecht</surname>
			</person>
		</names>
		<date value="1998-03"/>
		<howpublished>Internet RFC 2284</howpublished>
		<title type="sharef:primaryTitle">PPP Extensible Authentication Protocol (EAP)</title>
		<field type="bibtex:topic">eap[1] ppp[0.9]</field>
	</reference>
	<reference name="rfc2288" src="bibtex:misc" src-info="bibtex:line-41817" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Clifford</givenname>
				<surname>Lynch</surname>
			</person>
			<person>
				<givenname>Cecilia</givenname>
				<surname>Preston</surname>
			</person>
			<person>
				<givenname>Ron</givenname>
				<surname>Daniel</surname>
			</person>
		</names>
		<date value="1998-02"/>
		<howpublished>Internet RFC 2288</howpublished>
		<title type="sharef:primaryTitle">Using Existing Bibliographic Identifiers as Uniform Resource Names</title>
		<field type="bibtex:topic">urn[0.7] isbn[0.8] issn[0.8] sici[0.8]</field>
	</reference>
	<reference name="rfc2289" src="bibtex:misc" src-info="bibtex:line-41826" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Neil</givenname>
				<surname>Haller</surname>
			</person>
			<person>
				<givenname>Craig</givenname>
				<surname>Metz</surname>
			</person>
			<person>
				<givenname>Philip J.</givenname>
				<surname>Nesser</surname>
			</person>
			<person>
				<givenname>Mike</givenname>
				<surname>Straw</surname>
			</person>
		</names>
		<date value="1998-02"/>
		<howpublished>Internet RFC 2289</howpublished>
		<title type="sharef:primaryTitle">A One-Time Password System</title>
		<field type="bibtex:topic">otp[1]</field>
		<field type="bibtex:updates">rfc1938</field>
	</reference>
	<reference name="rfc2291" src="bibtex:misc" src-info="bibtex:line-41836" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Judith</givenname>
				<surname>Slein</surname>
			</person>
			<person>
				<givenname>Fabio</givenname>
				<surname>Vitali</surname>
			</person>
			<person>
				<givenname>E. James</givenname>
				<surname>Whitehead</surname>
			</person>
			<person>
				<givenname>David G.</givenname>
				<surname>Durand</surname>
			</person>
		</names>
		<date value="1998-02"/>
		<howpublished>Internet RFC 2291</howpublished>
		<title type="sharef:primaryTitle">Requirements for a Distributed Authoring and Versioning Protocol for the World Wide Web</title>
		<field type="bibtex:topic">webdav[0.9]</field>
	</reference>
	<reference name="rfc2295" src="bibtex:misc" src-info="bibtex:line-41845" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Koen</givenname>
				<surname>Holtman</surname>
			</person>
			<person>
				<givenname>Andrew H.</givenname>
				<surname>Mutz</surname>
			</person>
		</names>
		<date value="1998-03"/>
		<howpublished>Internet RFC 2295</howpublished>
		<field type="bibtex:index">HTTP, content negotiation</field>
		<title type="sharef:primaryTitle">Transparent Content Negotiation in HTTP</title>
	</reference>
	<reference name="rfc2296" src="bibtex:misc" src-info="bibtex:line-41854" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Koen</givenname>
				<surname>Holtman</surname>
			</person>
			<person>
				<givenname>Andrew H.</givenname>
				<surname>Mutz</surname>
			</person>
		</names>
		<date value="1998-03"/>
		<howpublished>Internet RFC 2296</howpublished>
		<field type="bibtex:index">HTTP, RVSA</field>
		<title type="sharef:primaryTitle">HTTP Remote Variant Selection Algorithm — RVSA/1.0</title>
	</reference>
	<reference name="rfc2298" src="bibtex:misc" src-info="bibtex:line-41863" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Roger</givenname>
				<surname>Fajman</surname>
			</person>
		</names>
		<date value="1998-03"/>
		<howpublished>Internet RFC 2298</howpublished>
		<title type="sharef:primaryTitle">An Extensible Message Format for Message Disposition Notifications</title>
		<field type="bibtex:topic">mime[0.9]</field>
	</reference>
	<reference name="rfc2300" src="bibtex:misc" src-info="bibtex:line-41872" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Jon B.</givenname>
				<surname>Postel</surname>
			</person>
		</names>
		<date value="1998-03"/>
		<howpublished>Internet RFC 2300</howpublished>
		<title type="sharef:primaryTitle">Internet Official Protocol Standards</title>
		<field type="bibtex:topic">internet[1]</field>
	</reference>
	<reference name="rfc2302" src="bibtex:misc" src-info="bibtex:line-41881" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Glenn W.</givenname>
				<surname>Parsons</surname>
			</person>
			<person>
				<givenname>James</givenname>
				<surname>Rafferty</surname>
			</person>
			<person>
				<givenname>Stephen</givenname>
				<surname>Zilles</surname>
			</person>
		</names>
		<date value="1998-03"/>
		<howpublished>Internet RFC 2302</howpublished>
		<title type="sharef:primaryTitle">Tag Image File Format (TIFF) — image/tiff, MIME Sub-type Registration</title>
		<field type="bibtex:topic">mime[0.8] tiff[0.9]</field>
	</reference>
	<reference name="rfc2308" src="bibtex:misc" src-info="bibtex:line-41890" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Mark</givenname>
				<surname>Andrews</surname>
			</person>
		</names>
		<date value="1998-03"/>
		<howpublished>Internet RFC 2308</howpublished>
		<field type="bibtex:index">DNS</field>
		<title type="sharef:primaryTitle">Negative Caching of DNS Queries (DNS NCACHE)</title>
	</reference>
	<reference name="rfc2310" src="bibtex:misc" src-info="bibtex:line-41899" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Koen</givenname>
				<surname>Holtman</surname>
			</person>
		</names>
		<date value="1998-04"/>
		<howpublished>Internet RFC 2310</howpublished>
		<field type="bibtex:index">HTTP</field>
		<title type="sharef:primaryTitle">The Safe Response Header Field</title>
	</reference>
	<reference name="rfc2311" src="bibtex:misc" src-info="bibtex:line-41908" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Steven</givenname>
				<surname>Dusse</surname>
			</person>
			<person>
				<givenname>Paul E.</givenname>
				<surname>Hoffman</surname>
			</person>
			<person>
				<givenname>Blake</givenname>
				<surname>Ramsdell</surname>
			</person>
			<person>
				<givenname>Laurence</givenname>
				<surname>Lundblade</surname>
			</person>
			<person>
				<givenname>Lisa</givenname>
				<surname>Repka</surname>
			</person>
		</names>
		<date value="1998-03"/>
		<howpublished>Internet RFC 2311</howpublished>
		<title type="sharef:primaryTitle">S/MIME Version 2 Message Specification</title>
		<field type="bibtex:topic">smime[1]</field>
		<field type="bibtex:updates">smime2</field>
	</reference>
	<reference name="rfc2312" src="bibtex:misc" src-info="bibtex:line-41918" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Steven</givenname>
				<surname>Dusse</surname>
			</person>
			<person>
				<givenname>Paul E.</givenname>
				<surname>Hoffman</surname>
			</person>
			<person>
				<givenname>Blake</givenname>
				<surname>Ramsdell</surname>
			</person>
			<person>
				<givenname>Jeff</givenname>
				<surname>Weinstein</surname>
			</person>
		</names>
		<date value="1998-03"/>
		<howpublished>Internet RFC 2312</howpublished>
		<title type="sharef:primaryTitle">S/MIME Version 2 Certificate Specification</title>
		<field type="bibtex:topic">smime[1]</field>
		<field type="bibtex:updates">smime1</field>
	</reference>
	<reference name="rfc2314" src="bibtex:misc" src-info="bibtex:line-41928" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Burton S.</givenname>
				<surname>Kaliski</surname>
			</person>
		</names>
		<date value="1998-03"/>
		<howpublished>Internet RFC 2314</howpublished>
		<field type="bibtex:index">PKCS #10</field>
		<title type="sharef:primaryTitle">PKCS #10: Certification Request Syntax Version 1.5</title>
	</reference>
	<reference name="rfc2315" src="bibtex:misc" src-info="bibtex:line-41937" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Burton S.</givenname>
				<surname>Kaliski</surname>
			</person>
		</names>
		<date value="1998-03"/>
		<howpublished>Internet RFC 2315</howpublished>
		<title type="sharef:primaryTitle">PKCS #7: Cryptographic Message Syntax Version 1.5</title>
		<field type="bibtex:topic">pkcs7[1]</field>
	</reference>
	<reference name="rfc2318" src="bibtex:misc" src-info="bibtex:line-41946" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Håkon Wium</givenname>
				<surname>Lie</surname>
			</person>
			<person>
				<givenname>Bert</givenname>
				<surname>Bos</surname>
			</person>
			<person>
				<givenname>Chris</givenname>
				<surname>Lilley</surname>
			</person>
		</names>
		<date value="1998-03"/>
		<howpublished>Internet RFC 2318</howpublished>
		<title type="sharef:primaryTitle">The text/css Media Type</title>
		<field type="bibtex:topic">css[0.9] mime[0.8]</field>
	</reference>
	<reference name="rfc2326" src="bibtex:misc" src-info="bibtex:line-41955" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Henning</givenname>
				<surname>Schulzrinne</surname>
			</person>
			<person>
				<givenname>Anup</givenname>
				<surname>Rao</surname>
			</person>
			<person>
				<givenname>Robert</givenname>
				<surname>Lanphier</surname>
			</person>
		</names>
		<date value="1998-04"/>
		<howpublished>Internet RFC 2326</howpublished>
		<title type="sharef:primaryTitle">Real Time Streaming Protocol (RTSP)</title>
		<field type="bibtex:topic">rtsp[1]</field>
	</reference>
	<reference name="rfc2328" src="bibtex:misc" src-info="bibtex:line-41964" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>John</givenname>
				<surname>Moy</surname>
			</person>
		</names>
		<date value="1998-04"/>
		<howpublished>Internet RFC 2328</howpublished>
		<title type="sharef:primaryTitle">OSPF Version 2</title>
		<field type="bibtex:topic">ospf[1]</field>
	</reference>
	<reference name="rfc2368" src="bibtex:misc" src-info="bibtex:line-41973" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Paul E.</givenname>
				<surname>Hoffman</surname>
			</person>
			<person>
				<givenname>Larry</givenname>
				<surname>Masinter</surname>
			</person>
			<person>
				<givenname>Jamie</givenname>
				<surname>Zawinski</surname>
			</person>
		</names>
		<date value="1998-06"/>
		<howpublished>Internet RFC 2368</howpublished>
		<title type="sharef:primaryTitle">The mailto URL scheme</title>
		<field type="bibtex:topic">url[0.8]</field>
	</reference>
	<reference name="rfc2373" src="bibtex:misc" src-info="bibtex:line-41982" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Robert M.</givenname>
				<surname>Hinden</surname>
			</person>
			<person>
				<givenname>Stephen E.</givenname>
				<surname>Deering</surname>
			</person>
		</names>
		<date value="1998-07"/>
		<howpublished>Internet RFC 2373</howpublished>
		<title type="sharef:primaryTitle">IP Version 6 Addressing Architecture</title>
	</reference>
	<reference name="rfc2376" src="bibtex:misc" src-info="bibtex:line-41990" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>E. James</givenname>
				<surname>Whitehead</surname>
			</person>
			<person>
				<givenname>Makoto</givenname>
				<surname>Murata</surname>
			</person>
		</names>
		<date value="1998-07"/>
		<howpublished>Internet RFC 2376</howpublished>
		<title type="sharef:primaryTitle">XML Media Types</title>
		<field type="bibtex:topic">xml[0.9] mime[0.8]</field>
	</reference>
	<reference name="rfc2384" src="bibtex:misc" src-info="bibtex:line-41999" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Randall</givenname>
				<surname>Gellens</surname>
			</person>
		</names>
		<date value="1998-08"/>
		<howpublished>Internet RFC 2384</howpublished>
		<title type="sharef:primaryTitle">POP URL Scheme</title>
		<field type="bibtex:topic">pop[0.9] url[0.8]</field>
	</reference>
	<reference name="rfc2387" src="bibtex:misc" src-info="bibtex:line-42008" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Edward</givenname>
				<surname>Levinson</surname>
			</person>
		</names>
		<date value="1998-08"/>
		<howpublished>Internet RFC 2387</howpublished>
		<field type="bibtex:index">MIME</field>
		<title type="sharef:primaryTitle">The MIME Multipart/Related Content-Type</title>
	</reference>
	<reference name="rfc2388" src="bibtex:misc" src-info="bibtex:line-42017" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Larry</givenname>
				<surname>Masinter</surname>
			</person>
		</names>
		<date value="1998-08"/>
		<howpublished>Internet RFC 2388</howpublished>
		<field type="bibtex:index">HTML, MIME, forms</field>
		<title type="sharef:primaryTitle">Returning Values from Forms: multipart/form-data</title>
	</reference>
	<reference name="rfc2393" src="bibtex:misc" src-info="bibtex:line-42026" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Abraham</givenname>
				<surname>Shacham</surname>
			</person>
			<person>
				<givenname>Robert</givenname>
				<surname>Monsour</surname>
			</person>
			<person>
				<givenname>Roy</givenname>
				<surname>Pereira</surname>
			</person>
			<person>
				<givenname>Matt</givenname>
				<surname>Thomas</surname>
			</person>
		</names>
		<date value="1998-12"/>
		<howpublished>Internet RFC 2393</howpublished>
		<title type="sharef:primaryTitle">IP Payload Compression Protocol (IPComp)</title>
		<field type="bibtex:topic">ipcomp[1]</field>
	</reference>
	<reference name="rfc2394" src="bibtex:misc" src-info="bibtex:line-42035" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Roy</givenname>
				<surname>Pereira</surname>
			</person>
		</names>
		<date value="1998-12"/>
		<howpublished>Internet RFC 2394</howpublished>
		<title type="sharef:primaryTitle">IP Payload Compression Using DEFLATE</title>
		<field type="bibtex:topic">ipcomp[0.9] deflate[0.8]</field>
	</reference>
	<reference name="rfc2395" src="bibtex:misc" src-info="bibtex:line-42044" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Robert</givenname>
				<surname>Friend</surname>
			</person>
			<person>
				<givenname>Robert</givenname>
				<surname>Monsour</surname>
			</person>
		</names>
		<date value="1998-12"/>
		<howpublished>Internet RFC 2395</howpublished>
		<title type="sharef:primaryTitle">IP Payload Compression Using LZS</title>
		<field type="bibtex:topic">ipcomp[0.9] lzs[0.8]</field>
	</reference>
	<reference name="rfc2396" src="bibtex:misc" src-info="bibtex:line-42053" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Tim</givenname>
				<surname>Berners-Lee</surname>
			</person>
			<person>
				<givenname>Roy Thomas</givenname>
				<surname>Fielding</surname>
			</person>
			<person>
				<givenname>Larry</givenname>
				<surname>Masinter</surname>
			</person>
		</names>
		<date value="1998-08"/>
		<abstract>
			<richtext>
				<p>A Uniform Resource Identifier (URI) is a compact string of characters for identifying an abstract or physical resource. This document defines the generic syntax of URI, including both absolute and relative forms, and guidelines for their use; it revises and replaces the generic definitions in RFC 1738 and RFC 1808. This document defines a grammar that is a superset of all valid URI, such that an implementation can parse the common components of a URI reference without knowing the scheme-specific requirements of every possible identifier type. This document does not define a generative grammar for URI; that task will be performed by the individual specifications of each URI scheme.</p>
			</richtext>
		</abstract>
		<howpublished>Internet RFC 2396</howpublished>
		<title type="sharef:primaryTitle">Uniform Resource Identifiers (URI): Generic Syntax</title>
		<field type="bibtex:topic">uri[1]</field>
		<field type="bibtex:updates">rfc1630</field>
	</reference>
	<reference name="rfc2397" src="bibtex:misc" src-info="bibtex:line-42064" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Larry</givenname>
				<surname>Masinter</surname>
			</person>
		</names>
		<date value="1998-08"/>
		<abstract>
			<richtext>
				<p>A new URL scheme, "data", is defined. It allows inclusion of small data items as "immediate" data, as if it had been included externally.</p>
			</richtext>
		</abstract>
		<howpublished>Internet RFC 2397</howpublished>
		<title type="sharef:primaryTitle">The "data" URL scheme</title>
		<field type="bibtex:topic">url[0.8]</field>
	</reference>
	<reference name="rfc2400" src="bibtex:misc" src-info="bibtex:line-42074" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Jon B.</givenname>
				<surname>Postel</surname>
			</person>
			<person>
				<givenname>Joyce K.</givenname>
				<surname>Reynolds</surname>
			</person>
		</names>
		<date value="1998-09"/>
		<howpublished>Internet RFC 2400</howpublished>
		<title type="sharef:primaryTitle">Internet Official Protocol Standards</title>
		<field type="bibtex:topic">internet[1]</field>
		<field type="bibtex:updates">rfc2300</field>
	</reference>
	<reference name="rfc2401" src="bibtex:misc" src-info="bibtex:line-42084" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Stephen</givenname>
				<surname>Kent</surname>
			</person>
			<person>
				<givenname>Randall</givenname>
				<surname>Atkinson</surname>
			</person>
		</names>
		<date value="1998-09"/>
		<howpublished>Internet RFC 2401</howpublished>
		<title type="sharef:primaryTitle">Security Architecture for the Internet Protocol</title>
		<field type="bibtex:topic">ipsec[1]</field>
	</reference>
	<reference name="rfc2411" src="bibtex:misc" src-info="bibtex:line-42093" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Rodney</givenname>
				<surname>Thayer</surname>
			</person>
			<person>
				<givenname>Naganand</givenname>
				<surname>Doraswamy</surname>
			</person>
			<person>
				<givenname>Rob</givenname>
				<surname>Glenn</surname>
			</person>
		</names>
		<date value="1998-11"/>
		<howpublished>Internet RFC 2411</howpublished>
		<title type="sharef:primaryTitle">IP Security Document Roadmap</title>
		<field type="bibtex:topic">ipsec[1]</field>
	</reference>
	<reference name="rfc2413" src="bibtex:misc" src-info="bibtex:line-42102" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Stuart L.</givenname>
				<surname>Weibel</surname>
			</person>
			<person>
				<givenname>John A.</givenname>
				<surname>Kunze</surname>
			</person>
			<person>
				<givenname>Carl</givenname>
				<surname>Lagoze</surname>
			</person>
			<person>
				<givenname>Misha</givenname>
				<surname>Wolf</surname>
			</person>
		</names>
		<date value="1998-09"/>
		<howpublished>Internet RFC 2413</howpublished>
		<title type="sharef:primaryTitle">Dublin Core Metadata for Resource Discovery</title>
		<field type="bibtex:topic">dublincore[1] metadata[0.8]</field>
	</reference>
	<reference name="rfc2420" src="bibtex:misc" src-info="bibtex:line-42111" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Holger</givenname>
				<surname>Kummert</surname>
			</person>
		</names>
		<date value="1998-09"/>
		<howpublished>Internet RFC 2420</howpublished>
		<title type="sharef:primaryTitle">The PPP Triple-DES Encryption Protocol (3DESE)</title>
		<field type="bibtex:topic">tripledese[1] ppp[0.9]</field>
	</reference>
	<reference name="rfc2422" src="bibtex:misc" src-info="bibtex:line-42120" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Glenn W.</givenname>
				<surname>Parsons</surname>
			</person>
			<person>
				<givenname>Gregory M.</givenname>
				<surname>Vaudreuil</surname>
			</person>
		</names>
		<date value="1998-09"/>
		<howpublished>Internet RFC 2422</howpublished>
		<title type="sharef:primaryTitle">Toll Quality Voice — 32 kbit/s ADPCM, MIME Sub-type Registration</title>
	</reference>
	<reference name="rfc2424" src="bibtex:misc" src-info="bibtex:line-42128" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Glenn W.</givenname>
				<surname>Parsons</surname>
			</person>
			<person>
				<givenname>Gregory M.</givenname>
				<surname>Vaudreuil</surname>
			</person>
		</names>
		<date value="1998-09"/>
		<howpublished>Internet RFC 2424</howpublished>
		<title type="sharef:primaryTitle">Content Duration MIME Header Definition</title>
		<field type="bibtex:topic">mime[0.9]</field>
	</reference>
	<reference name="rfc2425" src="bibtex:misc" src-info="bibtex:line-42137" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Tim</givenname>
				<surname>Howes</surname>
			</person>
			<person>
				<givenname>Mark</givenname>
				<surname>Smith</surname>
			</person>
			<person>
				<givenname>Frank</givenname>
				<surname>Dawson</surname>
			</person>
		</names>
		<date value="1998-09"/>
		<howpublished>Internet RFC 2425</howpublished>
		<title type="sharef:primaryTitle">A MIME Content-Type for Directory Information</title>
		<field type="bibtex:topic">vcard[0.9] mime[0.8]</field>
	</reference>
	<reference name="rfc2426" src="bibtex:misc" src-info="bibtex:line-42146" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Frank</givenname>
				<surname>Dawson</surname>
			</person>
			<person>
				<givenname>Tim</givenname>
				<surname>Howes</surname>
			</person>
		</names>
		<date value="1998-09"/>
		<howpublished>Internet RFC 2426</howpublished>
		<title type="sharef:primaryTitle">vCard MIME Directory Profile</title>
		<field type="bibtex:topic">vcard[0.9]</field>
	</reference>
	<reference name="rfc2433" src="bibtex:misc" src-info="bibtex:line-42155" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Glen</givenname>
				<surname>Zorn</surname>
			</person>
			<person>
				<givenname>Steve</givenname>
				<surname>Cobb</surname>
			</person>
		</names>
		<date value="1998-10"/>
		<howpublished>Internet RFC 2433</howpublished>
		<title type="sharef:primaryTitle">Microsoft PPP CHAP Extensions</title>
		<field type="bibtex:topic">ppp[0.9] chap[1]</field>
	</reference>
	<reference name="rfc2434" src="bibtex:misc" src-info="bibtex:line-42164" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Thomas</givenname>
				<surname>Narten</surname>
			</person>
			<person>
				<givenname>Harald Tveit</givenname>
				<surname>Alvestrand</surname>
			</person>
		</names>
		<date value="1998-10"/>
		<howpublished>Internet RFC 2434</howpublished>
		<title type="sharef:primaryTitle">Guidelines for Writing an IANA Considerations Section in RFCs</title>
		<field type="bibtex:topic">rfc[0.9]</field>
	</reference>
	<reference name="rfc2437" src="bibtex:misc" src-info="bibtex:line-42173" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Burton S.</givenname>
				<surname>Kaliski</surname>
			</person>
			<person>
				<givenname>Jessica</givenname>
				<surname>Staddon</surname>
			</person>
		</names>
		<date value="1998-10"/>
		<howpublished>Internet RFC 2437</howpublished>
		<field type="bibtex:index">PKCS #1</field>
		<title type="sharef:primaryTitle">PKCS #1: RSA Cryptography Specifications Version 2.0</title>
	</reference>
	<reference name="rfc2440" src="bibtex:misc" src-info="bibtex:line-42182" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Jon</givenname>
				<surname>Callas</surname>
			</person>
			<person>
				<givenname>Lutz</givenname>
				<surname>Donnerhacke</surname>
			</person>
			<person>
				<givenname>Hal</givenname>
				<surname>Finney</surname>
			</person>
			<person>
				<givenname>Rodney</givenname>
				<surname>Thayer</surname>
			</person>
		</names>
		<date value="1998-11"/>
		<abstract>
			<richtext>
				<p>This document is maintained in order to publish all necessary information needed to develop interoperable applications based on the OpenPGP format. It is not a step-by-step cookbook for writing an application. It describes only the format and methods needed to read, check, generate, and write conforming packets crossing any network. It does not deal with storage and implementation questions. It does, however, discuss implementation issues necessary to avoid security flaws. Open-PGP software uses a combination of strong public-key and symmetric cryptography to provide security services for electronic communications and data storage. These services include confidentiality, key management, authentication, and digital signatures. This document specifies the message formats used in OpenPGP.</p>
			</richtext>
		</abstract>
		<howpublished>Internet RFC 2440</howpublished>
		<title type="sharef:primaryTitle">OpenPGP Message Format</title>
		<field type="bibtex:topic">pgp[0.9]</field>
	</reference>
	<reference name="rfc2445" src="bibtex:misc" src-info="bibtex:line-42192" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Frank</givenname>
				<surname>Dawson</surname>
			</person>
			<person>
				<givenname>Derik</givenname>
				<surname>Stenerson</surname>
			</person>
		</names>
		<date value="1998-11"/>
		<abstract>
			<richtext>
				<p>There is a clear need to provide and deploy interoperable calendaring and scheduling services for the Internet. Current group scheduling and Personal Information Management (PIM) products are being extended for use across the Internet, today, in proprietary ways. This memo has been defined to provide the definition of a common format for openly exchanging calendaring and scheduling information across the Internet. This memo is formatted as a registration for a MIME media type. However, the format in this memo is equally applicable for use outside of a MIME message content type. The proposed media type value is 'text/calendar'. This string would label a media type containing calendaring and scheduling information encoded as text characters formatted in a manner outlined below. This MIME media type provides a standard content type for capturing calendar event, to-do and journal entry information. It also can be used to convey free/busy time information. The content type is suitable as a MIME message entity that can be transferred over MIME based email systems, using HTTP or some other Internet transport. In addition, the content type is useful as an object for interactions between desktop applications using the operating system clipboard, drag/drop or file systems capabilities. This memo is based on the earlier work of the vCalendar specification for the exchange of personal calendaring and scheduling information. In order to avoid confusion with this referenced work, this memo is to be known as the iCalendar specification. This memo defines the format for specifying iCalendar object methods. An iCalendar object method is a set of usage constraints for the iCalendar object. For example, these methods might define scheduling messages that request an event be scheduled, reply to an event request, send a cancelation notice for an event, modify or replace the definition of an event, provide a counter proposal for an original event request, delegate an event request to another individual, request free or busy time, reply to a free or busy time request, or provide similar scheduling messages for a to-do or journal entry calendar component. The iCalendar Transport-independent Interoperability Protocol (iTIP) is one such scheduling protocol.</p>
			</richtext>
		</abstract>
		<howpublished>Internet RFC 2445</howpublished>
		<title type="sharef:primaryTitle">Internet Calendaring and Scheduling Core Object Specification (iCalendar)</title>
		<field type="bibtex:topic">icalendar[1]</field>
	</reference>
	<reference name="rfc2446" src="bibtex:misc" src-info="bibtex:line-42202" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Steven</givenname>
				<surname>Silverberg</surname>
			</person>
			<person>
				<givenname>Steven</givenname>
				<surname>Mansour</surname>
			</person>
			<person>
				<givenname>Frank</givenname>
				<surname>Dawson</surname>
			</person>
			<person>
				<givenname>Ross</givenname>
				<surname>Hopson</surname>
			</person>
		</names>
		<date value="1998-11"/>
		<howpublished>Internet RFC 2446</howpublished>
		<title type="sharef:primaryTitle">iCalendar Transport-Independent Interoperability Protocol (iTIP)</title>
		<field type="bibtex:topic">icalendar[0.9] itip[1]</field>
	</reference>
	<reference name="rfc2447" src="bibtex:misc" src-info="bibtex:line-42211" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Frank</givenname>
				<surname>Dawson</surname>
			</person>
			<person>
				<givenname>Steven</givenname>
				<surname>Mansour</surname>
			</person>
			<person>
				<givenname>Steven</givenname>
				<surname>Silverberg</surname>
			</person>
		</names>
		<date value="1998-11"/>
		<howpublished>Internet RFC 2447</howpublished>
		<title type="sharef:primaryTitle">iCalendar Message-Based Interoperability Protocol (iMIP)</title>
		<field type="bibtex:topic">icalendar[0.9] imip[1]</field>
	</reference>
	<reference name="rfc2449" src="bibtex:misc" src-info="bibtex:line-42220" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Randall</givenname>
				<surname>Gellens</surname>
			</person>
			<person>
				<givenname>Chris</givenname>
				<surname>Newman</surname>
			</person>
			<person>
				<givenname>Laurence</givenname>
				<surname>Lundblade</surname>
			</person>
		</names>
		<date value="1998-11"/>
		<howpublished>Internet RFC 2449</howpublished>
		<title type="sharef:primaryTitle">POP3 Extension Mechanism</title>
		<field type="bibtex:topic">pop[1]</field>
	</reference>
	<reference name="rfc2483" src="bibtex:misc" src-info="bibtex:line-42229" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Michael</givenname>
				<surname>Mealling</surname>
			</person>
			<person>
				<givenname>Ron</givenname>
				<surname>Daniel</surname>
			</person>
		</names>
		<date value="1999-01"/>
		<howpublished>Internet RFC 2483</howpublished>
		<field type="bibtex:index">URI, URN, URL, URC</field>
		<title type="sharef:primaryTitle">URI Resolution Services Necessary for URN Resolution</title>
	</reference>
	<reference name="rfc2500" src="bibtex:misc" src-info="bibtex:line-42238" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Joyce K.</givenname>
				<surname>Reynolds</surname>
			</person>
			<person>
				<givenname>Robert</givenname>
				<surname>Braden</surname>
			</person>
		</names>
		<date value="1999-06"/>
		<howpublished>Internet RFC 2500</howpublished>
		<title type="sharef:primaryTitle">Internet Official Protocol Standards</title>
		<field type="bibtex:topic">internet[1]</field>
		<field type="bibtex:updates">rfc2400</field>
	</reference>
	<reference name="rfc2506" src="bibtex:misc" src-info="bibtex:line-42248" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Koen</givenname>
				<surname>Holtman</surname>
			</person>
			<person>
				<givenname>Andrew H.</givenname>
				<surname>Mutz</surname>
			</person>
			<person>
				<givenname>Ted</givenname>
				<surname>Hardie</surname>
			</person>
		</names>
		<date value="1999-03"/>
		<howpublished>Internet RFC 2506</howpublished>
		<title type="sharef:primaryTitle">Media Feature Tag Registration Procedure</title>
	</reference>
	<reference name="rfc2509" src="bibtex:misc" src-info="bibtex:line-42256" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Mathias</givenname>
				<surname>Engan</surname>
			</person>
			<person>
				<givenname>Stephen L.</givenname>
				<surname>Casner</surname>
			</person>
			<person>
				<givenname>Carsten</givenname>
				<surname>Bormann</surname>
			</person>
		</names>
		<date value="1999-02"/>
		<howpublished>Internet RFC 2509</howpublished>
		<title type="sharef:primaryTitle">IP Header Compression over PPP</title>
		<field type="bibtex:topic">ip[0.9] ppp[0.9]</field>
	</reference>
	<reference name="rfc2510" src="bibtex:misc" src-info="bibtex:line-42265" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Carlisle</givenname>
				<surname>Adams</surname>
			</person>
			<person>
				<givenname>Stephen</givenname>
				<surname>Farrell</surname>
			</person>
		</names>
		<date value="1999-03"/>
		<howpublished>Internet RFC 2510</howpublished>
		<field type="bibtex:index">certificate, X.509, PKI</field>
		<title type="sharef:primaryTitle">Internet X.509 Public-Key Infrastructure — Certificate Management Protocols</title>
	</reference>
	<reference name="rfc2516" src="bibtex:misc" src-info="bibtex:line-42274" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Louis</givenname>
				<surname>Mamakos</surname>
			</person>
			<person>
				<givenname>Kurt</givenname>
				<surname>Lidl</surname>
			</person>
			<person>
				<givenname>Jeff</givenname>
				<surname>Evarts</surname>
			</person>
			<person>
				<givenname>David</givenname>
				<surname>Carrel</surname>
			</person>
			<person>
				<givenname>Dan</givenname>
				<surname>Simone</surname>
			</person>
			<person>
				<givenname>Ross</givenname>
				<surname>Wheeler</surname>
			</person>
		</names>
		<date value="1999-02"/>
		<howpublished>Internet RFC 2516</howpublished>
		<title type="sharef:primaryTitle">A Method for Transmitting PPP Over Ethernet (PPPoE)</title>
		<field type="bibtex:topic">pppoe[1]</field>
	</reference>
	<reference name="rfc2518" src="bibtex:misc" src-info="bibtex:line-42283" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Yaron Y.</givenname>
				<surname>Goland</surname>
			</person>
			<person>
				<givenname>E. James</givenname>
				<surname>Whitehead</surname>
			</person>
			<person>
				<givenname>A.</givenname>
				<surname>Faizi</surname>
			</person>
			<person>
				<givenname>S.</givenname>
				<surname>Carter</surname>
			</person>
			<person>
				<givenname>D.</givenname>
				<surname>Jensen</surname>
			</person>
		</names>
		<date value="1999-02"/>
		<howpublished>Internet RFC 2518</howpublished>
		<title type="sharef:primaryTitle">HTTP Extensions for Distributed Authoring — WebDAV</title>
		<field type="bibtex:topic">http[0.9] webdav[1]</field>
	</reference>
	<reference name="rfc2527" src="bibtex:misc" src-info="bibtex:line-42292" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Santosh</givenname>
				<surname>Chokhani</surname>
			</person>
			<person>
				<givenname>Warwick</givenname>
				<surname>Ford</surname>
			</person>
		</names>
		<date value="1999-03"/>
		<howpublished>Internet RFC 2527</howpublished>
		<title type="sharef:primaryTitle">Internet X.509 Public Key Infrastructure Certificate Policy and Certification Practices Framework</title>
		<field type="bibtex:topic">x509[1]</field>
	</reference>
	<reference name="rfc2528" src="bibtex:misc" src-info="bibtex:line-42301" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Russell</givenname>
				<surname>Housley</surname>
			</person>
			<person>
				<givenname>Tim</givenname>
				<surname>Polk</surname>
			</person>
		</names>
		<date value="1999-03"/>
		<howpublished>Internet RFC 2528</howpublished>
		<title type="sharef:primaryTitle">Representation of Key Exchange Algorithm (KEA) Keys in Internet X.509 Public Key Infrastructure Certificates</title>
		<field type="bibtex:topic">pkix[0.9] kea[1]</field>
	</reference>
	<reference name="rfc2533" src="bibtex:misc" src-info="bibtex:line-42310" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Graham</givenname>
				<surname>Klyne</surname>
			</person>
		</names>
		<date value="1999-03"/>
		<howpublished>Internet RFC 2533</howpublished>
		<title type="sharef:primaryTitle">A Syntax for Describing Media Feature Sets</title>
	</reference>
	<reference name="rfc2534" src="bibtex:misc" src-info="bibtex:line-42318" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Larry</givenname>
				<surname>Masinter</surname>
			</person>
			<person>
				<givenname>Dan</givenname>
				<surname>Wing</surname>
			</person>
			<person>
				<givenname>Andrew H.</givenname>
				<surname>Mutz</surname>
			</person>
			<person>
				<givenname>Koen</givenname>
				<surname>Holtman</surname>
			</person>
		</names>
		<date value="1999-03"/>
		<howpublished>Internet RFC 2534</howpublished>
		<title type="sharef:primaryTitle">Media Features for Display, Print, and Fax</title>
		<field type="bibtex:topic">fax[0.8] displaystd[0.8] colorspace[0.8]</field>
	</reference>
	<reference name="rfc2543" src="bibtex:misc" src-info="bibtex:line-42327" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Mark J.</givenname>
				<surname>Handley</surname>
			</person>
			<person>
				<givenname>Henning</givenname>
				<surname>Schulzrinne</surname>
			</person>
			<person>
				<givenname>Eve M.</givenname>
				<surname>Schooler</surname>
			</person>
			<person>
				<givenname>Jonathan</givenname>
				<surname>Rosenberg</surname>
			</person>
		</names>
		<date value="1999-03"/>
		<abstract>
			<richtext>
				<p>The Session Initiation Protocol (SIP) is an application-layer control (signaling) protocol for creating, modifying and terminating sessions with one or more participants. These sessions include Internet multimedia conferences, Internet telephone calls and multimedia distribution. Members in a session can communicate via multicast or via a mesh of unicast relations, or a combination of these. SIP invitations used to create sessions carry session descriptions which allow participants to agree on a set of compatible media types. SIP supports user mobility by proxying and redirecting requests to the user's current location. Users can register their current location. SIP is not tied to any particular conference control protocol. SIP is designed to be independent of the lower-layer transport protocol and can be extended with additional capabilities.</p>
			</richtext>
		</abstract>
		<howpublished>Internet RFC 2543</howpublished>
		<title type="sharef:primaryTitle">SIP: Session Initiation Protocol</title>
		<field type="bibtex:topic">sip[1]</field>
		<field type="bibtex:updates">sip2</field>
	</reference>
	<reference name="rfc2557" src="bibtex:misc" src-info="bibtex:line-42338" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Jacob</givenname>
				<surname>Palme</surname>
			</person>
			<person>
				<givenname>Alex</givenname>
				<surname>Hopmann</surname>
			</person>
			<person>
				<givenname>Nick</givenname>
				<surname>Shelness</surname>
			</person>
		</names>
		<date value="1999-03"/>
		<howpublished>Internet RFC 2557</howpublished>
		<field type="bibtex:index">MIME, HTML</field>
		<title type="sharef:primaryTitle">MIME Encapsulation of Aggregate Documents, such as HTML (MHTML)</title>
		<field type="bibtex:topic">mhtml[1]</field>
		<field type="bibtex:updates">rfc2110</field>
	</reference>
	<reference name="rfc2560" src="bibtex:misc" src-info="bibtex:line-42349" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Michael</givenname>
				<surname>Myers</surname>
			</person>
			<person>
				<givenname>Rich</givenname>
				<surname>Ankney</surname>
			</person>
			<person>
				<givenname>Ambarish</givenname>
				<surname>Malpani</surname>
			</person>
			<person>
				<givenname>Slava</givenname>
				<surname>Galperin</surname>
			</person>
			<person>
				<givenname>Carlisle</givenname>
				<surname>Adams</surname>
			</person>
		</names>
		<date value="1999-06"/>
		<howpublished>Internet RFC 2560</howpublished>
		<field type="bibtex:index">X.509, OCSP, PKI, certificate</field>
		<title type="sharef:primaryTitle">X.509 Internet Public-Key Infrastructure — Online Certificate Status Protocol (OCSP)</title>
	</reference>
	<reference name="rfc2585" src="bibtex:misc" src-info="bibtex:line-42358" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Russell</givenname>
				<surname>Housley</surname>
			</person>
			<person>
				<givenname>Paul E.</givenname>
				<surname>Hoffman</surname>
			</person>
		</names>
		<date value="1999-05"/>
		<howpublished>Internet RFC 2585</howpublished>
		<field type="bibtex:index">X.509, certificate, PKI</field>
		<title type="sharef:primaryTitle">Internet X.509 Public-Key Infrastructure — Operational Protocols: FTP and HTTP</title>
	</reference>
	<reference name="rfc2586" src="bibtex:misc" src-info="bibtex:line-42367" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>James</givenname>
				<surname>Salsman</surname>
			</person>
			<person>
				<givenname>Harald Tveit</givenname>
				<surname>Alvestrand</surname>
			</person>
		</names>
		<date value="1999-05"/>
		<howpublished>Internet RFC 2586</howpublished>
		<field type="bibtex:index">MIME, audio, WAV, AIFF, L16</field>
		<title type="sharef:primaryTitle">The Audio/L16 MIME content type</title>
	</reference>
	<reference name="rfc2600" src="bibtex:misc" src-info="bibtex:line-42376" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Joyce K.</givenname>
				<surname>Reynolds</surname>
			</person>
			<person>
				<givenname>Robert</givenname>
				<surname>Braden</surname>
			</person>
		</names>
		<date value="2000-03"/>
		<howpublished>Internet RFC 2600</howpublished>
		<title type="sharef:primaryTitle">Internet Official Protocol Standards</title>
		<field type="bibtex:topic">internet[1]</field>
		<field type="bibtex:updates">rfc2500</field>
	</reference>
	<reference name="rfc2606" src="bibtex:misc" src-info="bibtex:line-42386" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Donald E.</givenname>
				<surname>Eastlake</surname>
			</person>
			<person>
				<givenname>Aliza R.</givenname>
				<surname>Panitz</surname>
			</person>
		</names>
		<date value="1999-06"/>
		<howpublished>Internet RFC 2606</howpublished>
		<title type="sharef:primaryTitle">Reserved Top Level DNS Names</title>
		<field type="bibtex:topic">dns[0.8]</field>
	</reference>
	<reference name="rfc2611" src="bibtex:misc" src-info="bibtex:line-42395" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Leslie L.</givenname>
				<surname>Daigle</surname>
			</person>
			<person>
				<givenname>Dirk-Willem</givenname>
				<surname link="van">Gulik</surname>
			</person>
			<person>
				<givenname>Renato</givenname>
				<surname>Iannella</surname>
			</person>
			<person>
				<givenname>Patrik</givenname>
				<surname>Faltstrom</surname>
			</person>
		</names>
		<date value="1999-06"/>
		<howpublished>Internet RFC 2611</howpublished>
		<title type="sharef:primaryTitle">URN Namespace Definition Mechanisms</title>
		<field type="bibtex:topic">urn[1]</field>
		<field type="bibtex:updates">dai98</field>
	</reference>
	<reference name="rfc2616" src="bibtex:misc" src-info="bibtex:line-42405" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Roy Thomas</givenname>
				<surname>Fielding</surname>
			</person>
			<person>
				<givenname>Jim</givenname>
				<surname>Gettys</surname>
			</person>
			<person>
				<givenname>Jeffrey C.</givenname>
				<surname>Mogul</surname>
			</person>
			<person>
				<givenname>Henrik</givenname>
				<surname>Frystyk Nielsen</surname>
			</person>
			<person>
				<givenname>Larry</givenname>
				<surname>Masinter</surname>
			</person>
			<person>
				<givenname>Paul J.</givenname>
				<surname>Leach</surname>
			</person>
			<person>
				<givenname>Tim</givenname>
				<surname>Berners-Lee</surname>
			</person>
		</names>
		<date value="1999-06"/>
		<howpublished>Internet RFC 2616</howpublished>
		<title type="sharef:primaryTitle">Hypertext Transfer Protocol — HTTP/1.1</title>
		<field type="bibtex:topic">http[1]</field>
	</reference>
	<reference name="rfc2617" src="bibtex:misc" src-info="bibtex:line-42414" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>John</givenname>
				<surname>Franks</surname>
			</person>
			<person>
				<givenname>Phillip M.</givenname>
				<surname>Hallam-Baker</surname>
			</person>
			<person>
				<givenname>Jeffery L.</givenname>
				<surname>Hostetler</surname>
			</person>
			<person>
				<givenname>Scott D.</givenname>
				<surname>Lawrence</surname>
			</person>
			<person>
				<givenname>Paul J.</givenname>
				<surname>Leach</surname>
			</person>
			<person>
				<givenname>Ari</givenname>
				<surname>Luotonen</surname>
			</person>
			<person>
				<givenname>Lawrence C.</givenname>
				<surname>Stewart</surname>
			</person>
		</names>
		<date value="1999-06"/>
		<howpublished>Internet RFC 2617</howpublished>
		<title type="sharef:primaryTitle">HTTP Authentication: Basic and Digest Access Authentication</title>
		<field type="bibtex:topic">bauth[1] daauth[1] http[0.9]</field>
		<field type="bibtex:updates">rfc2069</field>
	</reference>
	<reference name="rfc2629" src="bibtex:misc" src-info="bibtex:line-42424" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Marshall T.</givenname>
				<surname>Rose</surname>
			</person>
		</names>
		<date value="1999-06"/>
		<howpublished>Internet RFC 2629</howpublished>
		<title type="sharef:primaryTitle">Writing I-Ds and RFCs using XML</title>
		<field type="bibtex:topic">rfc[0.9] xml[0.6]</field>
	</reference>
	<reference name="rfc2630" src="bibtex:misc" src-info="bibtex:line-42433" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Russell</givenname>
				<surname>Housley</surname>
			</person>
		</names>
		<date value="1999-06"/>
		<howpublished>Internet RFC 2630</howpublished>
		<title type="sharef:primaryTitle">Cryptographic Message Syntax</title>
		<field type="bibtex:topic">cms[1]</field>
		<field type="bibtex:updates">cms</field>
	</reference>
	<reference name="rfc2631" src="bibtex:misc" src-info="bibtex:line-42443" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Eric</givenname>
				<surname>Rescorla</surname>
			</person>
		</names>
		<date value="1999-06"/>
		<howpublished>Internet RFC 2631</howpublished>
		<title type="sharef:primaryTitle">Diffie-Hellman Key Agreement Method</title>
		<field type="bibtex:topic">diffiehellman[1]</field>
	</reference>
	<reference name="rfc2632" src="bibtex:misc" src-info="bibtex:line-42452" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Blake</givenname>
				<surname>Ramsdell</surname>
			</person>
		</names>
		<date value="1999-06"/>
		<howpublished>Internet RFC 2632</howpublished>
		<title type="sharef:primaryTitle">S/MIME Version 3 Certificate Specification</title>
		<field type="bibtex:topic">smime[1]</field>
	</reference>
	<reference name="rfc2633" src="bibtex:misc" src-info="bibtex:line-42461" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Blake</givenname>
				<surname>Ramsdell</surname>
			</person>
		</names>
		<date value="1999-06"/>
		<howpublished>Internet RFC 2633</howpublished>
		<title type="sharef:primaryTitle">S/MIME Version 3 Message Specification</title>
		<field type="bibtex:topic">smime[1]</field>
	</reference>
	<reference name="rfc2637" src="bibtex:misc" src-info="bibtex:line-42470" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Kory</givenname>
				<surname>Hamzeh</surname>
			</person>
			<person>
				<givenname>Gurdeep Singh</givenname>
				<surname>Pall</surname>
			</person>
			<person>
				<givenname>William</givenname>
				<surname>Verthein</surname>
			</person>
			<person>
				<givenname>Jeff</givenname>
				<surname>Taarud</surname>
			</person>
			<person>
				<givenname>W. Andrew</givenname>
				<surname>Little</surname>
			</person>
			<person>
				<givenname>Glen</givenname>
				<surname>Zorn</surname>
			</person>
		</names>
		<date value="1999-07"/>
		<howpublished>Internet RFC 2637</howpublished>
		<title type="sharef:primaryTitle">Point-to-Point Tunneling Protocol (PPTP)</title>
		<field type="bibtex:topic">pptp[1]</field>
	</reference>
	<reference name="rfc2646" src="bibtex:misc" src-info="bibtex:line-42479" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Randall</givenname>
				<surname>Gellens</surname>
			</person>
		</names>
		<date value="1999-08"/>
		<howpublished>Internet RFC 2646</howpublished>
		<title type="sharef:primaryTitle">The Text/Plain Format Parameter</title>
	</reference>
	<reference name="rfc2648" src="bibtex:misc" src-info="bibtex:line-42487" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Ryan</givenname>
				<surname>Moats</surname>
			</person>
		</names>
		<date value="1999-08"/>
		<howpublished>Internet RFC 2648</howpublished>
		<title type="sharef:primaryTitle">A URN Namespace for IETF Documents</title>
		<field type="bibtex:topic">urn[0.7] ietf[0.8]</field>
	</reference>
	<reference name="rfc2660" src="bibtex:misc" src-info="bibtex:line-42496" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Eric</givenname>
				<surname>Rescorla</surname>
			</person>
			<person>
				<givenname>Allan M.</givenname>
				<surname>Schiffman</surname>
			</person>
		</names>
		<date value="1999-08"/>
		<howpublished>Internet RFC 2660</howpublished>
		<title type="sharef:primaryTitle">The Secure HyperText Transfer Protocol</title>
		<field type="bibtex:topic">shttp[1]</field>
		<field type="bibtex:updates">shttp</field>
	</reference>
	<reference name="rfc2661" src="bibtex:misc" src-info="bibtex:line-42506" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>W. Mark</givenname>
				<surname>Townsley</surname>
			</person>
			<person>
				<givenname>Andrew J.</givenname>
				<surname>Valencia</surname>
			</person>
			<person>
				<givenname>Allan C.</givenname>
				<surname>Rubens</surname>
			</person>
			<person>
				<givenname>Gurdeep Singh</givenname>
				<surname>Pall</surname>
			</person>
			<person>
				<givenname>Glen</givenname>
				<surname>Zorn</surname>
			</person>
			<person>
				<givenname>Bill</givenname>
				<surname>Palter</surname>
			</person>
		</names>
		<date value="1999-08"/>
		<howpublished>Internet RFC 2661</howpublished>
		<title type="sharef:primaryTitle">Layer Two Tunneling Protocol "L2TP"</title>
		<field type="bibtex:topic">l2tp[1]</field>
	</reference>
	<reference name="rfc2664" src="bibtex:misc" src-info="bibtex:line-42515" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Raymond</givenname>
				<surname>Plzak</surname>
			</person>
			<person>
				<givenname>Amy T.</givenname>
				<surname>Wells</surname>
			</person>
			<person>
				<givenname>Ed</givenname>
				<surname>Krol</surname>
			</person>
		</names>
		<date value="1999-08"/>
		<howpublished>Internet RFC 2664</howpublished>
		<field type="bibtex:index">IP, gopher, DNS</field>
		<title type="sharef:primaryTitle">FYI on Questions and Answers — Answers to Commonly asked "New Internet User" Questions</title>
	</reference>
	<reference name="rfc2700" src="bibtex:misc" src-info="bibtex:line-42524" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Joyce K.</givenname>
				<surname>Reynolds</surname>
			</person>
			<person>
				<givenname>Robert</givenname>
				<surname>Braden</surname>
			</person>
		</names>
		<date value="2000-08"/>
		<howpublished>Internet RFC 2700</howpublished>
		<title type="sharef:primaryTitle">Internet Official Protocol Standards</title>
		<field type="bibtex:topic">internet[1]</field>
		<field type="bibtex:updates">rfc2600</field>
	</reference>
	<reference name="rfc2703" src="bibtex:misc" src-info="bibtex:line-42534" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Graham</givenname>
				<surname>Klyne</surname>
			</person>
		</names>
		<date value="1999-09"/>
		<howpublished>Internet RFC 2703</howpublished>
		<field type="bibtex:index">content negotiation</field>
		<title type="sharef:primaryTitle">Protocol-independent Content Negotiation Framework</title>
	</reference>
	<reference name="rfc2706" src="bibtex:misc" src-info="bibtex:line-42543" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Donald E.</givenname>
				<surname>Eastlake</surname>
			</person>
			<person>
				<givenname>Ted</givenname>
				<surname>Goldstein</surname>
			</person>
		</names>
		<date value="1999-10"/>
		<howpublished>Internet RFC 2706</howpublished>
		<title type="sharef:primaryTitle">ECML v1: Field Names for E-Commerce</title>
		<field type="bibtex:topic">ecml[1]</field>
	</reference>
	<reference name="rfc2716" src="bibtex:misc" src-info="bibtex:line-42552" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Bernard</givenname>
				<surname>Aboba</surname>
			</person>
			<person>
				<givenname>Dan</givenname>
				<surname>Simon</surname>
			</person>
		</names>
		<date value="1999-10"/>
		<howpublished>Internet RFC 2716</howpublished>
		<title type="sharef:primaryTitle">PPP EAP TLS Authentication Protocol</title>
		<field type="bibtex:topic">eap[1] ppp[0.9] tls[0.9]</field>
	</reference>
	<reference name="rfc2717" src="bibtex:misc" src-info="bibtex:line-42561" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Rich</givenname>
				<surname>Petke</surname>
			</person>
			<person>
				<givenname>Ian</givenname>
				<surname>King</surname>
			</person>
		</names>
		<date value="1999-11"/>
		<howpublished>Internet RFC 2717</howpublished>
		<title type="sharef:primaryTitle">Registration Procedures for URL Scheme Names</title>
		<field type="bibtex:topic">url[0.9]</field>
	</reference>
	<reference name="rfc2718" src="bibtex:misc" src-info="bibtex:line-42570" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Larry</givenname>
				<surname>Masinter</surname>
			</person>
			<person>
				<givenname>Harald Tveit</givenname>
				<surname>Alvestrand</surname>
			</person>
			<person>
				<givenname>Dan</givenname>
				<surname>Zigmond</surname>
			</person>
			<person>
				<givenname>Rich</givenname>
				<surname>Petke</surname>
			</person>
		</names>
		<date value="1999-11"/>
		<howpublished>Internet RFC 2718</howpublished>
		<title type="sharef:primaryTitle">Guidelines for new URL Schemes</title>
		<field type="bibtex:topic">url[0.9]</field>
	</reference>
	<reference name="rfc2730" src="bibtex:misc" src-info="bibtex:line-42579" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Stephen R.</givenname>
				<surname>Hanna</surname>
			</person>
			<person>
				<givenname>Baiju V.</givenname>
				<surname>Patel</surname>
			</person>
			<person>
				<givenname>Munil</givenname>
				<surname>Shah</surname>
			</person>
		</names>
		<date value="1999-12"/>
		<howpublished>Internet RFC 2730</howpublished>
		<title type="sharef:primaryTitle">Multicast Address Dynamic Client Allocation Protocol (MADCAP)</title>
		<field type="bibtex:topic">madcap[1]</field>
	</reference>
	<reference name="rfc2731" src="bibtex:misc" src-info="bibtex:line-42588" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>John A.</givenname>
				<surname>Kunze</surname>
			</person>
		</names>
		<date value="1999-12"/>
		<howpublished>Internet RFC 2731</howpublished>
		<title type="sharef:primaryTitle">Encoding Dublin Core Metadata in HTML</title>
		<field type="bibtex:topic">html[0.8] dublincore[0.9] metadata[0.8]</field>
	</reference>
	<reference name="rfc2732" src="bibtex:misc" src-info="bibtex:line-42597" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Robert M.</givenname>
				<surname>Hinden</surname>
			</person>
			<person>
				<givenname>Brian E.</givenname>
				<surname>Carpenter</surname>
			</person>
			<person>
				<givenname>Larry</givenname>
				<surname>Masinter</surname>
			</person>
		</names>
		<date value="1999-12"/>
		<howpublished>Internet RFC 2732</howpublished>
		<field type="bibtex:index">URI, URL, IPv6</field>
		<title type="sharef:primaryTitle">Format for Literal IPv6 Addresses in URLs</title>
	</reference>
	<reference name="rfc2738" src="bibtex:misc" src-info="bibtex:line-42606" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Graham</givenname>
				<surname>Klyne</surname>
			</person>
		</names>
		<date value="1999-12"/>
		<howpublished>Internet RFC 2738</howpublished>
		<title type="sharef:primaryTitle">Corrections to "A Syntax for Describing Media Feature Sets"</title>
	</reference>
	<reference name="rfc2756" src="bibtex:misc" src-info="bibtex:line-42614" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Paul</givenname>
				<surname>Vixie</surname>
			</person>
			<person>
				<givenname>Duane</givenname>
				<surname>Wessels</surname>
			</person>
		</names>
		<date value="2000-01"/>
		<howpublished>Internet RFC 2756</howpublished>
		<title type="sharef:primaryTitle">Hypertext Caching Protocol (HTCP/0.0)</title>
		<field type="bibtex:topic">htcp[1]</field>
	</reference>
	<reference name="rfc2759" src="bibtex:misc" src-info="bibtex:line-42623" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Glen</givenname>
				<surname>Zorn</surname>
			</person>
		</names>
		<date value="2000-01"/>
		<howpublished>Internet RFC 2759</howpublished>
		<title type="sharef:primaryTitle">Microsoft PPP CHAP Extensions, Version 2</title>
		<field type="bibtex:topic">ppp[0.9] chap[1]</field>
	</reference>
	<reference name="rfc2774" src="bibtex:misc" src-info="bibtex:line-42632" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Henrik</givenname>
				<surname>Frystyk Nielsen</surname>
			</person>
			<person>
				<givenname>Paul J.</givenname>
				<surname>Leach</surname>
			</person>
			<person>
				<givenname>Scott D.</givenname>
				<surname>Lawrence</surname>
			</person>
		</names>
		<date value="2000-02"/>
		<howpublished>Internet RFC 2774</howpublished>
		<title type="sharef:primaryTitle">An HTTP Extension Framework</title>
		<field type="bibtex:topic">httpef[1]</field>
		<field type="bibtex:updates">fry99a</field>
	</reference>
	<reference name="rfc2778" src="bibtex:misc" src-info="bibtex:line-42642" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Mark</givenname>
				<surname>Day</surname>
			</person>
			<person>
				<givenname>Jonathan</givenname>
				<surname>Rosenberg</surname>
			</person>
			<person>
				<givenname>Hiroyasu</givenname>
				<surname>Sugano</surname>
			</person>
		</names>
		<date value="2000-02"/>
		<howpublished>Internet RFC 2778</howpublished>
		<title type="sharef:primaryTitle">A Model for Presence and Instant Messaging</title>
		<field type="bibtex:topic">impp[1]</field>
	</reference>
	<reference name="rfc2779" src="bibtex:misc" src-info="bibtex:line-42651" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Mark</givenname>
				<surname>Day</surname>
			</person>
			<person>
				<givenname>Sonu</givenname>
				<surname>Aggarwal</surname>
			</person>
			<person>
				<givenname>Jesse</givenname>
				<surname>Vincent</surname>
			</person>
		</names>
		<date value="2000-02"/>
		<howpublished>Internet RFC 2779</howpublished>
		<title type="sharef:primaryTitle">Instant Messaging and Presence Protocol Requirements</title>
		<field type="bibtex:topic">impp[1]</field>
	</reference>
	<reference name="rfc2781" src="bibtex:misc" src-info="bibtex:line-42660" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Paul E.</givenname>
				<surname>Hoffman</surname>
			</person>
			<person>
				<givenname>François</givenname>
				<surname>Yergeau</surname>
			</person>
		</names>
		<date value="2000-02"/>
		<howpublished>Internet RFC 2781</howpublished>
		<title type="sharef:primaryTitle">UTF-16, an encoding of ISO 10646</title>
		<field type="bibtex:topic">utf16[1] ucs[0.8]</field>
	</reference>
	<reference name="rfc2782" src="bibtex:misc" src-info="bibtex:line-42669" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Arnt</givenname>
				<surname>Gulbrandsen</surname>
			</person>
			<person>
				<givenname>Paul</givenname>
				<surname>Vixie</surname>
			</person>
			<person>
				<givenname>Levon</givenname>
				<surname>Esibov</surname>
			</person>
		</names>
		<date value="2000-02"/>
		<howpublished>Internet RFC 2782</howpublished>
		<field type="bibtex:index">DNS</field>
		<title type="sharef:primaryTitle">A DNS RR for specifying the location of services (DNS SRV)</title>
	</reference>
	<reference name="rfc2800" src="bibtex:misc" src-info="bibtex:line-42678" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Joyce K.</givenname>
				<surname>Reynolds</surname>
			</person>
			<person>
				<givenname>Robert</givenname>
				<surname>Braden</surname>
			</person>
			<person>
				<givenname>Sandy</givenname>
				<surname>Ginoza</surname>
			</person>
		</names>
		<date value="2001-05"/>
		<howpublished>Internet RFC 2800</howpublished>
		<title type="sharef:primaryTitle">Internet Official Protocol Standards</title>
		<field type="bibtex:topic">internet[1]</field>
		<field type="bibtex:updates">rfc2700</field>
	</reference>
	<reference name="rfc2801" src="bibtex:misc" src-info="bibtex:line-42688" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>David</givenname>
				<surname>Burdett</surname>
			</person>
		</names>
		<date value="2000-04"/>
		<howpublished>Internet RFC 2801</howpublished>
		<title type="sharef:primaryTitle">Internet Open Trading Protocol (IOTP) — Version 1.0</title>
		<field type="bibtex:topic">iotp[1]</field>
		<field type="bibtex:updates">bur99</field>
	</reference>
	<reference name="rfc2802" src="bibtex:misc" src-info="bibtex:line-42698" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Kent M.</givenname>
				<surname>Davidson</surname>
			</person>
			<person>
				<givenname>Yoshiaki</givenname>
				<surname>Kawatsura</surname>
			</person>
		</names>
		<date value="2000-04"/>
		<howpublished>Internet RFC 2802</howpublished>
		<title type="sharef:primaryTitle">Digital Signatures for the v1.0 Internet Open Trading Protocol (IOTP)</title>
		<field type="bibtex:topic">iotp[0.9]</field>
	</reference>
	<reference name="rfc2803" src="bibtex:misc" src-info="bibtex:line-42707" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Hiroshi</givenname>
				<surname>Maruyama</surname>
			</person>
			<person>
				<givenname>Kent</givenname>
				<surname>Tamura</surname>
			</person>
			<person>
				<givenname>Naohiko</givenname>
				<surname>Uramoto</surname>
			</person>
		</names>
		<date value="2000-04"/>
		<howpublished>Internet RFC 2803</howpublished>
		<field type="bibtex:index">DOM, XML, hash, DOMHASH</field>
		<title type="sharef:primaryTitle">Digest Values for DOM (DOMHASH)</title>
	</reference>
	<reference name="rfc2806" src="bibtex:misc" src-info="bibtex:line-42716" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Antti</givenname>
				<surname>Vähä-Sipilä</surname>
			</person>
		</names>
		<date value="2000-04"/>
		<howpublished>Internet RFC 2806</howpublished>
		<title type="sharef:primaryTitle">URLs for Telephone Calls</title>
		<field type="bibtex:topic">url[0.7] pstn[0.8]</field>
	</reference>
	<reference name="rfc2810" src="bibtex:misc" src-info="bibtex:line-42725" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Christophe</givenname>
				<surname>Kalt</surname>
			</person>
		</names>
		<date value="2000-04"/>
		<howpublished>Internet RFC 2810</howpublished>
		<title type="sharef:primaryTitle">Internet Relay Chat: Architecture</title>
		<field type="bibtex:topic">irc[1]</field>
	</reference>
	<reference name="rfc2811" src="bibtex:misc" src-info="bibtex:line-42734" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Christophe</givenname>
				<surname>Kalt</surname>
			</person>
		</names>
		<date value="2000-04"/>
		<howpublished>Internet RFC 2811</howpublished>
		<title type="sharef:primaryTitle">Internet Relay Chat: Channel Management</title>
		<field type="bibtex:topic">irc[1]</field>
	</reference>
	<reference name="rfc2812" src="bibtex:misc" src-info="bibtex:line-42743" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Christophe</givenname>
				<surname>Kalt</surname>
			</person>
		</names>
		<date value="2000-04"/>
		<howpublished>Internet RFC 2812</howpublished>
		<title type="sharef:primaryTitle">Internet Relay Chat: Client Protocol</title>
		<field type="bibtex:topic">irc[1]</field>
	</reference>
	<reference name="rfc2813" src="bibtex:misc" src-info="bibtex:line-42752" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Christophe</givenname>
				<surname>Kalt</surname>
			</person>
		</names>
		<date value="2000-04"/>
		<howpublished>Internet RFC 2813</howpublished>
		<title type="sharef:primaryTitle">Internet Relay Chat: Server Protocol</title>
		<field type="bibtex:topic">irc[1]</field>
	</reference>
	<reference name="rfc2817" src="bibtex:misc" src-info="bibtex:line-42761" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Rohit</givenname>
				<surname>Khare</surname>
			</person>
			<person>
				<givenname>Scott D.</givenname>
				<surname>Lawrence</surname>
			</person>
		</names>
		<date value="2000-05"/>
		<howpublished>Internet RFC 2817</howpublished>
		<title type="sharef:primaryTitle">Upgrading to TLS Within HTTP/1.1</title>
		<field type="bibtex:topic">tls[0.9] http[0.9] https[1]</field>
	</reference>
	<reference name="rfc2818" src="bibtex:misc" src-info="bibtex:line-42770" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Eric</givenname>
				<surname>Rescorla</surname>
			</person>
		</names>
		<date value="2000-05"/>
		<howpublished>Internet RFC 2818</howpublished>
		<title type="sharef:primaryTitle">HTTP over TLS</title>
		<field type="bibtex:topic">tls[0.9] http[0.9] https[1]</field>
		<field type="bibtex:updates">https</field>
	</reference>
	<reference name="rfc2821" src="bibtex:misc" src-info="bibtex:line-42780" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>John C.</givenname>
				<surname>Klensin</surname>
			</person>
		</names>
		<date value="2001-04"/>
		<abstract>
			<richtext>
				<p>This document is a self-contained specification of the basic protocol for the Internet electronic mail transport. It consolidates, updates and clarifies, but doesn't add new or change existing functionality of the following: The original SMTP (Simple Mail Transfer Protocol) specification of RFC 821, domain name system requirements and implications for mail transport from RFC 1035 and RFC 974, the clarifications and applicability statements in RFC 1123, and material drawn from the SMTP Extension mechanisms. It obsoletes RFC 821, RFC 974, and updates RFC 1123 (replaces the mail transport materials of RFC 1123). However, RFC 821 specifies some features that were not in significant use in the Internet by the mid-1990s and (in appendices) some additional transport models. Those sections are omitted here in the interest of clarity and brevity; readers needing them should refer to RFC 821. It also includes some additional material from RFC 1123 that required amplification. This material has been identified in multiple ways, mostly by tracking flaming on various lists and newsgroups and problems of unusual readings or interpretations that have appeared as the SMTP extensions have been deployed. Where this specification moves beyond consolidation and actually differs from earlier documents, it supersedes them technically as well as textually. Although SMTP was designed as a mail transport and delivery protocol, this specification also contains information that is important to its use as a 'mail submission' protocol, as recommended for POP and IMAP. Additional submission issues are discussed in RFC 2476. Section 2.3 provides definitions of terms specific to this document. Except when the historical terminology is necessary for clarity, this document uses the current 'client' and 'server' terminology to identify the sending and receiving SMTP processes, respectively. A companion document discusses message headers, message bodies and formats and structures for them, and their relationship.</p>
			</richtext>
		</abstract>
		<howpublished>Internet RFC 2821</howpublished>
		<title type="sharef:primaryTitle">Simple Mail Transfer Protocol</title>
		<field type="bibtex:topic">smtp[1] pop[0.9] imap[0.9] dns[0.9]</field>
		<field type="bibtex:updates">rfc821 rfc974 rfc1869 rfc1123</field>
	</reference>
	<reference name="rfc2822" src="bibtex:misc" src-info="bibtex:line-42791" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Peter W.</givenname>
				<surname>Resnick</surname>
			</person>
		</names>
		<date value="2001-04"/>
		<howpublished>Internet RFC 2822</howpublished>
		<title type="sharef:primaryTitle">Internet Message Format</title>
		<field type="bibtex:updates">rfc822</field>
	</reference>
	<reference name="rfc2825" src="bibtex:misc" src-info="bibtex:line-42800" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Leslie L.</givenname>
				<surname>Daigle</surname>
			</person>
		</names>
		<date value="2000-05"/>
		<howpublished>Internet RFC 2825</howpublished>
		<title type="sharef:primaryTitle">A Tangled Web: Issues of I18N, Domain Names, and the other Internet Protocols</title>
		<field type="bibtex:topic">dns[0.7] i18n[0.9]</field>
	</reference>
	<reference name="rfc2828" src="bibtex:misc" src-info="bibtex:line-42809" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Robert W.</givenname>
				<surname>Shirey</surname>
			</person>
		</names>
		<date value="2000-05"/>
		<howpublished>Internet RFC 2828</howpublished>
		<field type="bibtex:index">security</field>
		<title type="sharef:primaryTitle">Internet Security Glossary</title>
	</reference>
	<reference name="rfc2838" src="bibtex:misc" src-info="bibtex:line-42818" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Dan</givenname>
				<surname>Zigmond</surname>
			</person>
			<person>
				<givenname>Mark</givenname>
				<surname>Vickers</surname>
			</person>
		</names>
		<date value="2000-05"/>
		<howpublished>Internet RFC 2838</howpublished>
		<title type="sharef:primaryTitle">Uniform Resource Identifiers for Television Broadcasts</title>
		<field type="bibtex:topic">uri[0.8]</field>
	</reference>
	<reference name="rfc2849" src="bibtex:misc" src-info="bibtex:line-42827" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Gordon</givenname>
				<surname>Good</surname>
			</person>
		</names>
		<date value="2000-06"/>
		<howpublished>Internet RFC 2849</howpublished>
		<title type="sharef:primaryTitle">The LDAP Data Interchange Format (LDIF) — Technical Specification</title>
		<field type="bibtex:topic">ldif[1]</field>
	</reference>
	<reference name="rfc2850" src="bibtex:misc" src-info="bibtex:line-42836" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Brian E.</givenname>
				<surname>Carpenter</surname>
			</person>
		</names>
		<date value="2000-05"/>
		<howpublished>Internet RFC 2850</howpublished>
		<title type="sharef:primaryTitle">Charter of the Internet Architecture Board (IAB)</title>
		<field type="bibtex:topic">iab[1]</field>
	</reference>
	<reference name="rfc2851" src="bibtex:misc" src-info="bibtex:line-42845" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Mike</givenname>
				<surname>Daniele</surname>
			</person>
			<person>
				<givenname>Brian</givenname>
				<surname>Haberman</surname>
			</person>
			<person>
				<givenname>Shawn A.</givenname>
				<surname>Routhier</surname>
			</person>
			<person>
				<givenname>Jürgen</givenname>
				<surname>Schönwälder</surname>
			</person>
		</names>
		<date value="2000-06"/>
		<howpublished>Internet RFC 2851</howpublished>
		<title type="sharef:primaryTitle">Textual Conventions for Internet Network Addresses</title>
		<field type="bibtex:topic">ip[0.8] dns[0.8]</field>
	</reference>
	<reference name="rfc2854" src="bibtex:misc" src-info="bibtex:line-42854" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Dan</givenname>
				<surname>Connolly</surname>
			</person>
			<person>
				<givenname>Larry</givenname>
				<surname>Masinter</surname>
			</person>
		</names>
		<date value="2000-06"/>
		<abstract>
			<richtext>
				<p>This document summarizes the history of HTML development, and defines the "text/html" MIME type by pointing to the relevant W3C recommendations; it is intended to obsolete the previous IETF documents defining HTML, including RFC 1866, RFC 1867, RFC 1980, RFC 1942 and RFC 2070, and to remove HTML from IETF Standards Track.</p>
			</richtext>
		</abstract>
		<howpublished>Internet RFC 2854</howpublished>
		<title type="sharef:primaryTitle">The 'text/html' Media Type</title>
		<field type="bibtex:topic">html[0.9] mime[0.8]</field>
	</reference>
	<reference name="rfc2865" src="bibtex:misc" src-info="bibtex:line-42864" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Carl</givenname>
				<surname>Rigney</surname>
			</person>
			<person>
				<givenname>Allan C.</givenname>
				<surname>Rubens</surname>
			</person>
			<person>
				<givenname>William Allen</givenname>
				<surname>Simpson</surname>
			</person>
			<person>
				<givenname>Steve</givenname>
				<surname>Willens</surname>
			</person>
		</names>
		<date value="2000-06"/>
		<howpublished>Internet RFC 2865</howpublished>
		<title type="sharef:primaryTitle">Remote Authentication Dial In User Service (RADIUS)</title>
		<field type="bibtex:topic">radius[1]</field>
		<field type="bibtex:updates">rfc2138</field>
	</reference>
	<reference name="rfc2866" src="bibtex:misc" src-info="bibtex:line-42874" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Carl</givenname>
				<surname>Rigney</surname>
			</person>
		</names>
		<date value="2000-06"/>
		<howpublished>Internet RFC 2866</howpublished>
		<title type="sharef:primaryTitle">RADIUS Accounting</title>
		<field type="bibtex:topic">radius[0.9]</field>
		<field type="bibtex:updates">rfc2139</field>
	</reference>
	<reference name="rfc2869" src="bibtex:misc" src-info="bibtex:line-42884" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Pat R.</givenname>
				<surname>Calhoun</surname>
			</person>
			<person>
				<givenname>Allan C.</givenname>
				<surname>Rubens</surname>
			</person>
			<person>
				<givenname>Bernard</givenname>
				<surname>Aboba</surname>
			</person>
		</names>
		<date value="2000-06"/>
		<howpublished>Internet RFC 2869</howpublished>
		<title type="sharef:primaryTitle">RADIUS Extensions</title>
		<field type="bibtex:topic">radius[0.8] eap[0.8]</field>
	</reference>
	<reference name="rfc2898" src="bibtex:misc" src-info="bibtex:line-42893" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Burton S.</givenname>
				<surname>Kaliski</surname>
			</person>
		</names>
		<date value="2000-09"/>
		<howpublished>Internet RFC 2898</howpublished>
		<title type="sharef:primaryTitle">PKCS #5: Password-Based Cryptography Specification Version 2.0</title>
		<field type="bibtex:topic">pkcs5[1]</field>
	</reference>
	<reference name="rfc2910" src="bibtex:misc" src-info="bibtex:line-42902" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Scott A.</givenname>
				<surname>Isaacson</surname>
			</person>
			<person>
				<givenname>Thomas N.</givenname>
				<surname>Hastings</surname>
			</person>
			<person>
				<givenname>Robert</givenname>
				<surname>Herriot</surname>
			</person>
			<person>
				<givenname>Roger</givenname>
				<surname>deBry</surname>
			</person>
			<person>
				<givenname>Patrick</givenname>
				<surname>Powell</surname>
			</person>
		</names>
		<date value="2000-09"/>
		<howpublished>Internet RFC 2910</howpublished>
		<title type="sharef:primaryTitle">Internet Printing Protocol/1.1: Encoding and Transport</title>
		<field type="bibtex:topic">ipp[1]</field>
	</reference>
	<reference name="rfc2911" src="bibtex:misc" src-info="bibtex:line-42911" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Robert</givenname>
				<surname>Herriot</surname>
			</person>
			<person>
				<givenname>Sylvan</givenname>
				<surname>Butler</surname>
			</person>
			<person>
				<givenname>Paul</givenname>
				<surname>Moore</surname>
			</person>
			<person>
				<givenname>Randy</givenname>
				<surname>Turner</surname>
			</person>
			<person>
				<givenname>John</givenname>
				<surname>Wenn</surname>
			</person>
		</names>
		<date value="2000-09"/>
		<howpublished>Internet RFC 2911</howpublished>
		<title type="sharef:primaryTitle">Internet Printing Protocol/1.1: Model and Semantics</title>
		<field type="bibtex:topic">ipp[1]</field>
	</reference>
	<reference name="rfc2929" src="bibtex:misc" src-info="bibtex:line-42920" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Donald E.</givenname>
				<surname>Eastlake</surname>
			</person>
			<person>
				<givenname>Eric</givenname>
				<surname>Brunner-Williams</surname>
			</person>
			<person>
				<givenname>Bill</givenname>
				<surname>Manning</surname>
			</person>
		</names>
		<date value="2000-09"/>
		<howpublished>Internet RFC 2929</howpublished>
		<title type="sharef:primaryTitle">Domain Name System (DNS) IANA Considerations</title>
	</reference>
	<reference name="rfc2960" src="bibtex:misc" src-info="bibtex:line-42928" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Randall R.</givenname>
				<surname>Stewart</surname>
			</person>
			<person>
				<givenname>Qiaobing</givenname>
				<surname>Xie</surname>
			</person>
			<person>
				<givenname>Ken</givenname>
				<surname>Morneault</surname>
			</person>
			<person>
				<givenname>Chip</givenname>
				<surname>Sharp</surname>
			</person>
			<person>
				<givenname>Hanns Jürgen</givenname>
				<surname>Schwarzbauer</surname>
			</person>
			<person>
				<givenname>Tom</givenname>
				<surname>Taylor</surname>
			</person>
			<person>
				<givenname>Ian</givenname>
				<surname>Rytina</surname>
			</person>
			<person>
				<givenname>Malleswar</givenname>
				<surname>Kalla</surname>
			</person>
			<person>
				<givenname>Lixia</givenname>
				<surname>Zhang</surname>
			</person>
			<person>
				<givenname>Vern</givenname>
				<surname>Paxson</surname>
			</person>
		</names>
		<date value="2000-10"/>
		<howpublished>Internet RFC 2960</howpublished>
		<title type="sharef:primaryTitle">Stream Control Transmission Protocol</title>
		<field type="bibtex:topic">sctp[1]</field>
	</reference>
	<reference name="rfc2964" src="bibtex:misc" src-info="bibtex:line-42937" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Keith</givenname>
				<surname>Moore</surname>
			</person>
			<person>
				<givenname>Ned</givenname>
				<surname>Freed</surname>
			</person>
		</names>
		<date value="2000-10"/>
		<howpublished>Internet RFC 2964</howpublished>
		<title type="sharef:primaryTitle">Use of HTTP State Management Mechanism</title>
		<field type="bibtex:topic">http[0.8] cookie[1]</field>
	</reference>
	<reference name="rfc2965" src="bibtex:misc" src-info="bibtex:line-42946" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>David M.</givenname>
				<surname>Kristol</surname>
			</person>
			<person>
				<givenname>Lou</givenname>
				<surname>Montulli</surname>
			</person>
		</names>
		<date value="2000-10"/>
		<howpublished>Internet RFC 2965</howpublished>
		<title type="sharef:primaryTitle">HTTP State Management Mechanism</title>
		<field type="bibtex:topic">http[0.8] cookie[1]</field>
		<field type="bibtex:updates">rfc2109</field>
	</reference>
	<reference name="rfc2972" src="bibtex:misc" src-info="bibtex:line-42956" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Larry</givenname>
				<surname>Masinter</surname>
			</person>
			<person>
				<givenname>Michael</givenname>
				<surname>Mealling</surname>
			</person>
			<person>
				<givenname>Nicolas</givenname>
				<surname>Popp</surname>
			</person>
			<person>
				<givenname>Karen R.</givenname>
				<surname>Sollins</surname>
			</person>
		</names>
		<date value="2000-10"/>
		<howpublished>Internet RFC 2972</howpublished>
		<title type="sharef:primaryTitle">Context and Goals for Common Name Resolution</title>
		<field type="bibtex:topic">cnrp[1]</field>
		<field type="bibtex:updates">pop00</field>
	</reference>
	<reference name="rfc2978" src="bibtex:misc" src-info="bibtex:line-42966" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Ned</givenname>
				<surname>Freed</surname>
			</person>
			<person>
				<givenname>Jon B.</givenname>
				<surname>Postel</surname>
			</person>
		</names>
		<date value="2000-11"/>
		<howpublished>Internet RFC 2978</howpublished>
		<field type="bibtex:index">IANA, MIME</field>
		<title type="sharef:primaryTitle">IANA Charset Registration Procedures</title>
	</reference>
	<reference name="rfc2985" src="bibtex:misc" src-info="bibtex:line-42975" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Magnus</givenname>
				<surname>Nystrom</surname>
			</person>
			<person>
				<givenname>Burton S.</givenname>
				<surname>Kaliski</surname>
			</person>
		</names>
		<date value="2000-11"/>
		<howpublished>Internet RFC 2985</howpublished>
		<title type="sharef:primaryTitle">PKCS #9: Selected Object Classes and Attribute Types Version 2.0</title>
		<field type="bibtex:topic">pkcs9[1]</field>
	</reference>
	<reference name="rfc2986" src="bibtex:misc" src-info="bibtex:line-42984" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Magnus</givenname>
				<surname>Nystrom</surname>
			</person>
			<person>
				<givenname>Burton S.</givenname>
				<surname>Kaliski</surname>
			</person>
		</names>
		<date value="2000-11"/>
		<howpublished>Internet RFC 2986</howpublished>
		<title type="sharef:primaryTitle">PKCS #10: Certification Request Syntax Specification Version 1.7</title>
		<field type="bibtex:topic">pkcs10[1]</field>
	</reference>
	<reference name="rfc2987" src="bibtex:misc" src-info="bibtex:line-42993" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Paul E.</givenname>
				<surname>Hoffman</surname>
			</person>
		</names>
		<date value="2000-11"/>
		<howpublished>Internet RFC 2987</howpublished>
		<title type="sharef:primaryTitle">Registration of Charset and Language Media Features Tags</title>
		<field type="bibtex:topic">mime[0.8]</field>
	</reference>
	<reference name="rfc3001" src="bibtex:misc" src-info="bibtex:line-43002" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Michael</givenname>
				<surname>Mealling</surname>
			</person>
		</names>
		<date value="2000-11"/>
		<howpublished>Internet RFC 3001</howpublished>
		<title type="sharef:primaryTitle">A URN Namespace of Object Identifiers</title>
		<field type="bibtex:topic">urn[0.7] oid[0.8]</field>
	</reference>
	<reference name="rfc3003" src="bibtex:misc" src-info="bibtex:line-43011" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Martin</givenname>
				<surname>Nilsson</surname>
			</person>
		</names>
		<date value="2000-11"/>
		<howpublished>Internet RFC 3003</howpublished>
		<title type="sharef:primaryTitle">The audio/mpeg Media Type</title>
		<field type="bibtex:topic">mime[0.8] mp3[0.9]</field>
	</reference>
	<reference name="rfc3023" src="bibtex:misc" src-info="bibtex:line-43020" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Makoto</givenname>
				<surname>Murata</surname>
			</person>
			<person>
				<givenname>Simon</givenname>
				<surname>St. Laurent</surname>
			</person>
			<person>
				<givenname>Dan</givenname>
				<surname>Kohn</surname>
			</person>
		</names>
		<date value="2001-01"/>
		<howpublished>Internet RFC 3023</howpublished>
		<title type="sharef:primaryTitle">XML Media Types</title>
		<field type="bibtex:topic">xml[0.9] dtd[0.9] mathml[0.9] xslt[0.9] rdf[0.9] svg[0.9] mime[0.8] xpointer[0.9]</field>
		<field type="bibtex:updates">rfc2376</field>
	</reference>
	<reference name="rfc3030" src="bibtex:misc" src-info="bibtex:line-43030" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Gregory M.</givenname>
				<surname>Vaudreuil</surname>
			</person>
		</names>
		<date value="2001-01"/>
		<abstract>
			<richtext>
				<p>This memo defines two extensions to the SMTP (Simple Mail Transfer Protocol) service.</p>
			</richtext>
		</abstract>
		<howpublished>Internet RFC 3030</howpublished>
		<title type="sharef:primaryTitle">SMTP Service Extensions for Transmission of Large and Binary MIME Messages</title>
		<field type="bibtex:topic">esmtp[0.9] mime[0.9]</field>
		<field type="bibtex:updates">rfc1830</field>
	</reference>
	<reference name="rfc3031" src="bibtex:misc" src-info="bibtex:line-43041" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Eric C.</givenname>
				<surname>Rosen</surname>
			</person>
			<person>
				<givenname>Arun</givenname>
				<surname>Viswanathan</surname>
			</person>
			<person>
				<givenname>Ross</givenname>
				<surname>Callon</surname>
			</person>
		</names>
		<date value="2001-01"/>
		<howpublished>Internet RFC 3031</howpublished>
		<title type="sharef:primaryTitle">Multiprotocol Label Switching Architecture</title>
		<field type="bibtex:topic">mpls[1]</field>
	</reference>
	<reference name="rfc3039" src="bibtex:misc" src-info="bibtex:line-43050" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Stefan</givenname>
				<surname>Santesson</surname>
			</person>
			<person>
				<givenname>Tim</givenname>
				<surname>Polk</surname>
			</person>
			<person>
				<givenname>Petra</givenname>
				<surname>Barzin</surname>
			</person>
			<person>
				<givenname>Magnus</givenname>
				<surname>Nystrom</surname>
			</person>
		</names>
		<date value="2001-01"/>
		<howpublished>Internet RFC 3039</howpublished>
		<title type="sharef:primaryTitle">Internet X.509 Public Key Infrastructure: Qualified Certificates Profile</title>
		<field type="bibtex:topic">pkix[0.9]</field>
	</reference>
	<reference name="rfc3043" src="bibtex:misc" src-info="bibtex:line-43059" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Michael</givenname>
				<surname>Mealling</surname>
			</person>
		</names>
		<date value="2001-01"/>
		<howpublished>Internet RFC 3043</howpublished>
		<title type="sharef:primaryTitle">The Network Solutions Personal Internet Name (PIN): A URN Namespace for People and Organizations</title>
		<field type="bibtex:topic">urn[0.7]</field>
	</reference>
	<reference name="rfc3044" src="bibtex:misc" src-info="bibtex:line-43068" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Slawek</givenname>
				<surname>Rozenfeld</surname>
			</person>
		</names>
		<date value="2001-01"/>
		<howpublished>Internet RFC 3044</howpublished>
		<title type="sharef:primaryTitle">Using The ISSN (International Serial Standard Number) as URN (Uniform Resource Names) within an ISSN-URN Namespace</title>
		<field type="bibtex:topic">urn[0.7] issn[0.8]</field>
	</reference>
	<reference name="rfc3061" src="bibtex:misc" src-info="bibtex:line-43077" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Michael</givenname>
				<surname>Mealling</surname>
			</person>
		</names>
		<date value="2000-02"/>
		<howpublished>Internet RFC 3061</howpublished>
		<title type="sharef:primaryTitle">A URN Namespace of Object Identifiers</title>
		<field type="bibtex:topic">urn[0.7] oid[0.8]</field>
		<field type="bibtex:updates">rfc3001</field>
	</reference>
	<reference name="rfc3066" src="bibtex:misc" src-info="bibtex:line-43087" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Harald Tveit</givenname>
				<surname>Alvestrand</surname>
			</person>
		</names>
		<date value="2001-01"/>
		<howpublished>Internet RFC 3066</howpublished>
		<title type="sharef:primaryTitle">Tags for the Identification of Languages</title>
		<field type="bibtex:topic">i18n[0.9]</field>
		<field type="bibtex:updates">rfc1766</field>
	</reference>
	<reference name="rfc3072" src="bibtex:misc" src-info="bibtex:line-43097" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Max</givenname>
				<surname>Wildgrube</surname>
			</person>
		</names>
		<date value="2001-03"/>
		<howpublished>Internet RFC 3072</howpublished>
		<title type="sharef:primaryTitle">Structured Data Exchange Format (SDXF)</title>
		<field type="bibtex:topic">sdxf[1]</field>
	</reference>
	<reference name="rfc3085" src="bibtex:misc" src-info="bibtex:line-43106" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Anthony B.</givenname>
				<surname>Coates</surname>
			</person>
			<person>
				<givenname>David</givenname>
				<surname>Allen</surname>
			</person>
			<person>
				<givenname>Daniel</givenname>
				<surname>Rivers-Moore</surname>
			</person>
		</names>
		<date value="2001-03"/>
		<howpublished>Internet RFC 3085</howpublished>
		<title type="sharef:primaryTitle">URN Namespace for NewsML Resources</title>
		<field type="bibtex:topic">urn[0.7] newsml[0.8]</field>
	</reference>
	<reference name="rfc3106" src="bibtex:misc" src-info="bibtex:line-43115" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Donald E.</givenname>
				<surname>Eastlake</surname>
			</person>
			<person>
				<givenname>Ted</givenname>
				<surname>Goldstein</surname>
			</person>
		</names>
		<date value="2001-04"/>
		<howpublished>Internet RFC 3106</howpublished>
		<title type="sharef:primaryTitle">ECML v1.1: Field Specifications for E-Commerce</title>
		<field type="bibtex:topic">ecml[1]</field>
		<field type="bibtex:updates">rfc2706</field>
	</reference>
	<reference name="rfc3120" src="bibtex:misc" src-info="bibtex:line-43125" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Karl</givenname>
				<surname>Best</surname>
			</person>
			<person>
				<givenname>Norman</givenname>
				<surname>Walsh</surname>
			</person>
		</names>
		<date value="2001-06"/>
		<howpublished>Internet RFC 3120</howpublished>
		<title type="sharef:primaryTitle">A URN Namespace for XML.org</title>
		<field type="bibtex:topic">urn[0.7]</field>
	</reference>
	<reference name="rfc3121" src="bibtex:misc" src-info="bibtex:line-43134" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Karl</givenname>
				<surname>Best</surname>
			</person>
			<person>
				<givenname>Norman</givenname>
				<surname>Walsh</surname>
			</person>
		</names>
		<date value="2001-06"/>
		<howpublished>Internet RFC 3121</howpublished>
		<title type="sharef:primaryTitle">A URN Namespace for OASIS</title>
		<field type="bibtex:topic">urn[0.7] oasis[0.8]</field>
	</reference>
	<reference name="rfc3143" src="bibtex:misc" src-info="bibtex:line-43143" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Ian</givenname>
				<surname>Cooper</surname>
			</person>
			<person>
				<givenname>John</givenname>
				<surname>Dilley</surname>
			</person>
		</names>
		<date value="2001-06"/>
		<howpublished>Internet RFC 3143</howpublished>
		<title type="sharef:primaryTitle">Known HTTP Proxy/Caching Problems</title>
		<field type="bibtex:topic">http[0.8] proxy[0.7]</field>
	</reference>
	<reference name="rfc3151" src="bibtex:misc" src-info="bibtex:line-43152" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Norman</givenname>
				<surname>Walsh</surname>
			</person>
			<person>
				<givenname>John</givenname>
				<surname>Cowan</surname>
			</person>
			<person>
				<givenname>Paul</givenname>
				<surname>Grosso</surname>
			</person>
		</names>
		<date value="2001-08"/>
		<abstract>
			<richtext>
				<p>This document describes a URN (Uniform Resource Name) namespace that is designed to allow Public Identifiers to be expressed in URI (Uniform Resource Identifiers) syntax.</p>
			</richtext>
		</abstract>
		<howpublished>Internet RFC 3151</howpublished>
		<title type="sharef:primaryTitle">A URN Namespace for Public Identifiers</title>
		<field type="bibtex:topic">urn[0.7] fpi[0.9]</field>
	</reference>
	<reference name="rfc3160" src="bibtex:misc" src-info="bibtex:line-43162" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Susan</givenname>
				<surname>Harris</surname>
			</person>
		</names>
		<date value="2001-08"/>
		<howpublished>Internet RFC 3160</howpublished>
		<title type="sharef:primaryTitle">The Tao of IETF — A Novice's Guide to the Internet Engineering Task Force</title>
		<field type="bibtex:topic">ietf[1]</field>
	</reference>
	<reference name="rfc3173" src="bibtex:misc" src-info="bibtex:line-43171" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Abraham</givenname>
				<surname>Shacham</surname>
			</person>
			<person>
				<givenname>Robert</givenname>
				<surname>Monsour</surname>
			</person>
			<person>
				<givenname>Roy</givenname>
				<surname>Pereira</surname>
			</person>
			<person>
				<givenname>Matt</givenname>
				<surname>Thomas</surname>
			</person>
		</names>
		<date value="2001-09"/>
		<howpublished>Internet RFC 3173</howpublished>
		<title type="sharef:primaryTitle">IP Payload Compression Protocol (IPComp)</title>
		<field type="bibtex:topic">ipcomp[1]</field>
		<field type="bibtex:updates">rfc2393</field>
	</reference>
	<reference name="rfc3174" src="bibtex:misc" src-info="bibtex:line-43181" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Donald E.</givenname>
				<surname>Eastlake</surname>
			</person>
			<person>
				<givenname>Paul E.</givenname>
				<surname>Jones</surname>
			</person>
		</names>
		<date value="2001-09"/>
		<howpublished>Internet RFC 3174</howpublished>
		<title type="sharef:primaryTitle">US Secure Hash Algorithm 1 (SHA1)</title>
		<field type="bibtex:topic">sha1[1]</field>
	</reference>
	<reference name="rfc3187" src="bibtex:misc" src-info="bibtex:line-43190" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Juha</givenname>
				<surname>Hakala</surname>
			</person>
			<person>
				<givenname>Hartmut</givenname>
				<surname>Walravens</surname>
			</person>
		</names>
		<date value="2001-10"/>
		<howpublished>Internet RFC 3187</howpublished>
		<title type="sharef:primaryTitle">Using International Standard Book Numbers as Uniform Resource Names</title>
		<field type="bibtex:topic">urn[0.7] isbn[0.8]</field>
	</reference>
	<reference name="rfc3188" src="bibtex:misc" src-info="bibtex:line-43199" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Juha</givenname>
				<surname>Hakala</surname>
			</person>
		</names>
		<date value="2001-10"/>
		<howpublished>Internet RFC 3188</howpublished>
		<title type="sharef:primaryTitle">Using National Bibliography Numbers as Uniform Resource Names</title>
		<field type="bibtex:topic">urn[0.7] nbn[0.8]</field>
	</reference>
	<reference name="rfc3191" src="bibtex:misc" src-info="bibtex:line-43208" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Claudio</givenname>
				<surname>Allocchio</surname>
			</person>
		</names>
		<date value="2001-10"/>
		<abstract>
			<richtext>
				<p>This memo describes a simple method of encoding Global Switched Telephone Network (GSTN) addresses (commonly called "telephone numbers") in the local-part of Internet email addresses, along with an extension mechanism to allow encoding of additional standard attributes needed for email gateways to GSTN-based services.</p>
			</richtext>
		</abstract>
		<howpublished>Internet RFC 3191</howpublished>
		<title type="sharef:primaryTitle">Minimal GSTN address format in Internet Mail</title>
	</reference>
	<reference name="rfc3192" src="bibtex:misc" src-info="bibtex:line-43217" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Claudio</givenname>
				<surname>Allocchio</surname>
			</person>
		</names>
		<date value="2001-10"/>
		<howpublished>Internet RFC 3192</howpublished>
		<title type="sharef:primaryTitle">Minimal FAX address format in Internet Mail</title>
	</reference>
	<reference name="rfc3196" src="bibtex:misc" src-info="bibtex:line-43225" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Thomas N.</givenname>
				<surname>Hastings</surname>
			</person>
			<person>
				<givenname>Carl-Uno</givenname>
				<surname>Manros</surname>
			</person>
			<person>
				<givenname>Carl</givenname>
				<surname>Kugler</surname>
			</person>
			<person>
				<givenname>Henrik</givenname>
				<surname>Holst</surname>
			</person>
			<person>
				<givenname>Peter</givenname>
				<surname>Zehler</surname>
			</person>
		</names>
		<date value="2001-11"/>
		<howpublished>Internet RFC 3196</howpublished>
		<title type="sharef:primaryTitle">Internet Printing Protocol/1.1: Implementor's Guide</title>
		<field type="bibtex:topic">ipp[0.9]</field>
	</reference>
	<reference name="rfc3198" src="bibtex:misc" src-info="bibtex:line-43234" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Andrea</givenname>
				<surname>Westerinen</surname>
			</person>
			<person>
				<givenname>John</givenname>
				<surname>Schnizlein</surname>
			</person>
			<person>
				<givenname>John</givenname>
				<surname>Strassner</surname>
			</person>
			<person>
				<givenname>Mark</givenname>
				<surname>Scherling</surname>
			</person>
			<person>
				<givenname>Bob</givenname>
				<surname>Quinn</surname>
			</person>
			<person>
				<givenname>Jay</givenname>
				<surname>Perry</surname>
			</person>
			<person>
				<givenname>Shai</givenname>
				<surname>Herzog</surname>
			</person>
			<person>
				<givenname>An-Ni</givenname>
				<surname>Huynh</surname>
			</person>
			<person>
				<givenname>Mark</givenname>
				<surname>Carlson</surname>
			</person>
			<person>
				<givenname>Steve</givenname>
				<surname>Waldbusser</surname>
			</person>
		</names>
		<date value="2001-11"/>
		<howpublished>Internet RFC 3198</howpublished>
		<title type="sharef:primaryTitle">Terminology for Policy-Based Management</title>
	</reference>
	<reference name="rfc3229" src="bibtex:misc" src-info="bibtex:line-43242" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Jeffrey C.</givenname>
				<surname>Mogul</surname>
			</person>
			<person>
				<givenname>Balachander</givenname>
				<surname>Krishnamurthy</surname>
			</person>
			<person>
				<givenname>Fred</givenname>
				<surname>Douglis</surname>
			</person>
			<person>
				<givenname>Anja</givenname>
				<surname>Feldmann</surname>
			</person>
			<person>
				<givenname>Yaron Y.</givenname>
				<surname>Goland</surname>
			</person>
			<person>
				<givenname>Arthur</givenname>
				<surname link="van">Hoff</surname>
			</person>
			<person>
				<givenname>Daniel M.</givenname>
				<surname>Hellerstein</surname>
			</person>
		</names>
		<date value="2002-01"/>
		<howpublished>Internet RFC 3229</howpublished>
		<title type="sharef:primaryTitle">Delta encoding in HTTP</title>
		<field type="bibtex:topic">http[0.9]</field>
	</reference>
	<reference name="rfc3230" src="bibtex:misc" src-info="bibtex:line-43251" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Jeffrey C.</givenname>
				<surname>Mogul</surname>
			</person>
			<person>
				<givenname>Arthur</givenname>
				<surname link="van">Hoff</surname>
			</person>
		</names>
		<date value="2002-01"/>
		<howpublished>Internet RFC 3230</howpublished>
		<title type="sharef:primaryTitle">Instance Digests in HTTP</title>
		<field type="bibtex:topic">http[0.9]</field>
	</reference>
	<reference name="rfc3236" src="bibtex:misc" src-info="bibtex:line-43260" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Mark A.</givenname>
				<surname>Baker</surname>
			</person>
			<person>
				<givenname>Peter</givenname>
				<surname>Stark</surname>
			</person>
		</names>
		<date value="2002-02"/>
		<howpublished>Internet RFC 3236</howpublished>
		<title type="sharef:primaryTitle">The 'application/xhtml+xml' Media Type</title>
		<field type="bibtex:topic">xhtml[0.9] mime[0.8]</field>
	</reference>
	<reference name="rfc3239" src="bibtex:misc" src-info="bibtex:line-43269" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Carl</givenname>
				<surname>Kugler</surname>
			</person>
			<person>
				<givenname>Thomas N.</givenname>
				<surname>Hastings</surname>
			</person>
			<person>
				<givenname>Harry</givenname>
				<surname>Lewis</surname>
			</person>
		</names>
		<date value="2002-02"/>
		<howpublished>Internet RFC 3239</howpublished>
		<title type="sharef:primaryTitle">Internet Printing Protocol (IPP): Requirements for Job, Printer, and Device Administrative Operations</title>
		<field type="bibtex:topic">ipp[0.9]</field>
	</reference>
	<reference name="rfc3252" src="bibtex:misc" src-info="bibtex:line-43278" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Hugh</givenname>
				<surname>Kennedy</surname>
			</person>
		</names>
		<date value="2002-04"/>
		<howpublished>Internet RFC 3252</howpublished>
		<title type="sharef:primaryTitle">Binary Lexical Octet Ad-hoc Transport</title>
		<field type="bibtex:topic">ip[0.8] tcp[0.8] udp[0.8]</field>
	</reference>
	<reference name="rfc3279" src="bibtex:misc" src-info="bibtex:line-43287" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Tim</givenname>
				<surname>Polk</surname>
			</person>
			<person>
				<givenname>Russell</givenname>
				<surname>Housley</surname>
			</person>
			<person>
				<givenname>Larry</givenname>
				<surname>Bassham</surname>
			</person>
		</names>
		<date value="2002-04"/>
		<howpublished>Internet RFC 3279</howpublished>
		<title type="sharef:primaryTitle">Algorithms and Identifiers for the Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile</title>
		<field type="bibtex:topic">crl[1] x509[0.9]</field>
	</reference>
	<reference name="rfc3280" src="bibtex:misc" src-info="bibtex:line-43296" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Russell</givenname>
				<surname>Housley</surname>
			</person>
			<person>
				<givenname>Warwick</givenname>
				<surname>Ford</surname>
			</person>
			<person>
				<givenname>Tim</givenname>
				<surname>Polk</surname>
			</person>
			<person>
				<givenname>David</givenname>
				<surname>Solo</surname>
			</person>
		</names>
		<date value="2002-04"/>
		<howpublished>Internet RFC 3280</howpublished>
		<title type="sharef:primaryTitle">Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile</title>
		<field type="bibtex:topic">crl[1] x509[0.9]</field>
	</reference>
	<reference name="rfc3282" src="bibtex:misc" src-info="bibtex:line-43305" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Harald Tveit</givenname>
				<surname>Alvestrand</surname>
			</person>
		</names>
		<date value="2002-05"/>
		<howpublished>Internet RFC 3282</howpublished>
		<title type="sharef:primaryTitle">Content Language Headers</title>
		<field type="bibtex:topic">i18n[0.8] l10n[0.8]</field>
		<field type="bibtex:updates">rfc1766</field>
	</reference>
	<reference name="rfc3283" src="bibtex:misc" src-info="bibtex:line-43315" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Bob</givenname>
				<surname>Mahoney</surname>
			</person>
			<person>
				<givenname>George</givenname>
				<surname>Babics</surname>
			</person>
			<person>
				<givenname>Alexander</givenname>
				<surname>Taler</surname>
			</person>
		</names>
		<date value="2002-06"/>
		<howpublished>Internet RFC 3283</howpublished>
		<title type="sharef:primaryTitle">Guide to Internet Calendaring</title>
		<field type="bibtex:topic">icalendar[0.8] itip[0.8] imip[0.8] cap[0.8]</field>
	</reference>
	<reference name="rfc3286" src="bibtex:misc" src-info="bibtex:line-43324" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Lyndon</givenname>
				<surname>Ong</surname>
			</person>
			<person>
				<givenname>John</givenname>
				<surname>Yoakum</surname>
			</person>
		</names>
		<date value="2002-05"/>
		<howpublished>Internet RFC 3286</howpublished>
		<title type="sharef:primaryTitle">An Introduction to the Stream Control Transmission Protocol (SCTP)</title>
		<field type="bibtex:topic">sctp[0.9]</field>
	</reference>
	<reference name="rfc3288" src="bibtex:misc" src-info="bibtex:line-43333" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Eamon</givenname>
				<surname>O'Tuathail</surname>
			</person>
			<person>
				<givenname>Marshall T.</givenname>
				<surname>Rose</surname>
			</person>
		</names>
		<date value="2002-05"/>
		<howpublished>Internet RFC 3288</howpublished>
		<title type="sharef:primaryTitle">Using the Simple Object Access Protocol (SOAP) in Blocks Extensible Exchange Protocol (BEEP)</title>
		<field type="bibtex:topic">soap[0.8] beep[0.8]</field>
	</reference>
	<reference name="rfc3291" src="bibtex:misc" src-info="bibtex:line-43342" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Mike</givenname>
				<surname>Daniele</surname>
			</person>
			<person>
				<givenname>Brian</givenname>
				<surname>Haberman</surname>
			</person>
			<person>
				<givenname>Shawn A.</givenname>
				<surname>Routhier</surname>
			</person>
			<person>
				<givenname>Jürgen</givenname>
				<surname>Schönwälder</surname>
			</person>
		</names>
		<date value="2002-05"/>
		<howpublished>Internet RFC 3291</howpublished>
		<title type="sharef:primaryTitle">Textual Conventions for Internet Network Addresses</title>
		<field type="bibtex:topic">ip[0.8] dns[0.8]</field>
		<field type="bibtex:updates">rfc2851</field>
	</reference>
	<reference name="rfc3292" src="bibtex:misc" src-info="bibtex:line-43352" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Avri</givenname>
				<surname>Doria</surname>
			</person>
			<person>
				<givenname>Fiffi</givenname>
				<surname>Hellstrand</surname>
			</person>
			<person>
				<givenname>Kenneth</givenname>
				<surname>Sundell</surname>
			</person>
			<person>
				<givenname>Tom</givenname>
				<surname>Worster</surname>
			</person>
		</names>
		<date value="2002-06"/>
		<howpublished>Internet RFC 3292</howpublished>
		<title type="sharef:primaryTitle">General Switch Management Protocol (GSMP) V3</title>
		<field type="bibtex:topic">gsmp[1]</field>
	</reference>
	<reference name="rfc3305" src="bibtex:misc" src-info="bibtex:line-43361" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Michael</givenname>
				<surname>Mealling</surname>
			</person>
			<person>
				<givenname>Ray</givenname>
				<surname>Denenberg</surname>
			</person>
		</names>
		<date value="2002-08"/>
		<abstract>
			<richtext>
				<p>This document, a product of the W3C Uniform Resource Identifier (URI) Interest Group, addresses and attempts to clarify issues pertaining to URIs. This document addresses how URI space is partitioned and the relationship between URIs, URLs, and URNs, describes how URI schemes and URN namespaces ids are registered, and presents recommendations for continued work on this subject.</p>
			</richtext>
		</abstract>
		<howpublished>Internet RFC 3305</howpublished>
		<title type="sharef:primaryTitle">Uniform Resource Identifiers (URIs), URLs, and Uniform Resource Names (URNs): Clarifications and Recommendations</title>
		<field type="bibtex:topic">uri[0.9] url[0.9] urn[0.9]</field>
	</reference>
	<reference name="rfc3310" src="bibtex:misc" src-info="bibtex:line-43371" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Aki</givenname>
				<surname>Niemi</surname>
			</person>
			<person>
				<givenname>Jari</givenname>
				<surname>Arkko</surname>
			</person>
			<person>
				<givenname>Vesa</givenname>
				<surname>Torvinen</surname>
			</person>
		</names>
		<date value="2002-09"/>
		<abstract>
			<richtext>
				<p>This memo specifies an Authentication and Key Agreement (AKA) based one-time password generation mechanism for Hypertext Transfer Protocol (HTTP) Digest access authentication. The HTTP Authentication Framework includes two authentication schemes: Basic and Digest. Both schemes employ a shared secret based mechanism for access authentication. The AKA mechanism performs user authentication and session key distribution in Universal Mobile Telecommunications System (UMTS) networks. AKA is a challenge-response based mechanism that uses symmetric cryptography.</p>
			</richtext>
		</abstract>
		<howpublished>Internet RFC 3310</howpublished>
		<title type="sharef:primaryTitle">Hypertext Transfer Protocol (HTTP) Digest Authentication Using Authentication and Key Agreement (AKA) Version-2</title>
		<field type="bibtex:topic">aka[1] daauth[0.8]</field>
	</reference>
	<reference name="rfc3339" src="bibtex:misc" src-info="bibtex:line-43381" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Graham</givenname>
				<surname>Klyne</surname>
			</person>
			<person>
				<givenname>Chris</givenname>
				<surname>Newman</surname>
			</person>
		</names>
		<date value="2002-07"/>
		<howpublished>Internet RFC 3339</howpublished>
		<title type="sharef:primaryTitle">Date and Time on the Internet: Timestamps</title>
	</reference>
	<reference name="rfc3347" src="bibtex:misc" src-info="bibtex:line-43389" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Marjorie</givenname>
				<surname>Krueger</surname>
			</person>
			<person>
				<givenname>Randy</givenname>
				<surname>Haagens</surname>
			</person>
			<person>
				<givenname>Costa</givenname>
				<surname>Sapuntzakis</surname>
			</person>
			<person>
				<givenname>Mark</givenname>
				<surname>Bakke</surname>
			</person>
		</names>
		<date value="2002-07"/>
		<howpublished>Internet RFC 3347</howpublished>
		<title type="sharef:primaryTitle">Small Computer Systems Interface protocol over the Internet (iSCSI): Requirements and Design Considerations</title>
		<field type="bibtex:topic">iscsi[1]</field>
	</reference>
	<reference name="rfc3354" src="bibtex:misc" src-info="bibtex:line-43398" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Donald E.</givenname>
				<surname>Eastlake</surname>
			</person>
		</names>
		<date value="2002-08"/>
		<howpublished>Internet RFC 3354</howpublished>
		<title type="sharef:primaryTitle">Internet Open Trading Protocol Version 2 Requirements</title>
		<field type="bibtex:topic">iotp[1]</field>
		<field type="bibtex:updates">rfc2801</field>
	</reference>
	<reference name="rfc3368" src="bibtex:misc" src-info="bibtex:line-43408" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Michael</givenname>
				<surname>Mealling</surname>
			</person>
		</names>
		<date value="2002-08"/>
		<howpublished>Internet RFC 3368</howpublished>
		<title type="sharef:primaryTitle">The 'go' URI Scheme for the Common Name Resolution Protocol</title>
		<field type="bibtex:topic">cnrp[0.9] uri[0.8]</field>
	</reference>
	<reference name="rfc3369" src="bibtex:misc" src-info="bibtex:line-43417" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Russell</givenname>
				<surname>Housley</surname>
			</person>
		</names>
		<date value="2002-08"/>
		<howpublished>Internet RFC 3369</howpublished>
		<title type="sharef:primaryTitle">Cryptographic Message Syntax (CMS)</title>
		<field type="bibtex:topic">cms[1]</field>
		<field type="bibtex:updates">rfc2630</field>
	</reference>
	<reference name="rfc3370" src="bibtex:misc" src-info="bibtex:line-43427" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Russell</givenname>
				<surname>Housley</surname>
			</person>
		</names>
		<date value="2002-08"/>
		<howpublished>Internet RFC 3370</howpublished>
		<title type="sharef:primaryTitle">Cryptographic Message Syntax (CMS) Algorithms</title>
		<field type="bibtex:topic">cms[1]</field>
		<field type="bibtex:updates">rfc2630</field>
	</reference>
	<reference name="rfc3401" src="bibtex:misc" src-info="bibtex:line-43437" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Michael</givenname>
				<surname>Mealling</surname>
			</person>
		</names>
		<date value="2002-10"/>
		<howpublished>Internet RFC 3401</howpublished>
		<title type="sharef:primaryTitle">Dynamic Delegation Discovery System (DDDS) — Part One: The Comprehensive DDDS</title>
		<field type="bibtex:topic">ddds[1]</field>
		<field type="bibtex:updates">rfc2168 rfc2276</field>
	</reference>
	<reference name="rfc3402" src="bibtex:misc" src-info="bibtex:line-43447" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Michael</givenname>
				<surname>Mealling</surname>
			</person>
		</names>
		<date value="2002-10"/>
		<howpublished>Internet RFC 3402</howpublished>
		<title type="sharef:primaryTitle">Dynamic Delegation Discovery System (DDDS) — Part Two: The Algorithm</title>
		<field type="bibtex:topic">ddds[1]</field>
		<field type="bibtex:updates">rfc2168</field>
	</reference>
	<reference name="rfc3403" src="bibtex:misc" src-info="bibtex:line-43457" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Michael</givenname>
				<surname>Mealling</surname>
			</person>
		</names>
		<date value="2002-10"/>
		<howpublished>Internet RFC 3403</howpublished>
		<title type="sharef:primaryTitle">Dynamic Delegation Discovery System (DDDS) — Part Three: The Domain Name System (DNS) Database</title>
		<field type="bibtex:topic">ddds[1]</field>
		<field type="bibtex:updates">rfc2168</field>
	</reference>
	<reference name="rfc3404" src="bibtex:misc" src-info="bibtex:line-43467" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Michael</givenname>
				<surname>Mealling</surname>
			</person>
		</names>
		<date value="2002-10"/>
		<howpublished>Internet RFC 3404</howpublished>
		<title type="sharef:primaryTitle">Dynamic Delegation Discovery System (DDDS) — Part Four: The Uniform Resource Identifiers (URI) Resolution Application</title>
		<field type="bibtex:topic">ddds[1]</field>
		<field type="bibtex:updates">rfc2168</field>
	</reference>
	<reference name="rfc3405" src="bibtex:misc" src-info="bibtex:line-43477" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Michael</givenname>
				<surname>Mealling</surname>
			</person>
		</names>
		<date value="2002-10"/>
		<howpublished>Internet RFC 3405</howpublished>
		<title type="sharef:primaryTitle">Dynamic Delegation Discovery System (DDDS) — Part Five: URI.ARPA Assignment Procedures</title>
		<field type="bibtex:topic">ddds[1]</field>
	</reference>
	<reference name="rfc3406" src="bibtex:misc" src-info="bibtex:line-43486" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Leslie L.</givenname>
				<surname>Daigle</surname>
			</person>
			<person>
				<givenname>Dirk-Willem</givenname>
				<surname link="van">Gulik</surname>
			</person>
			<person>
				<givenname>Renato</givenname>
				<surname>Iannella</surname>
			</person>
			<person>
				<givenname>Patrik</givenname>
				<surname>Faltstrom</surname>
			</person>
		</names>
		<date value="2002-10"/>
		<howpublished>Internet RFC 3406</howpublished>
		<title type="sharef:primaryTitle">Uniform Resource Names (URN) Namespace Definition Mechanisms</title>
		<field type="bibtex:topic">urn[1]</field>
		<field type="bibtex:updates">rfc2611</field>
	</reference>
	<reference name="rfc3444" src="bibtex:misc" src-info="bibtex:line-43496" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Aiko</givenname>
				<surname>Pras</surname>
			</person>
			<person>
				<givenname>Jürgen</givenname>
				<surname>Schönwälder</surname>
			</person>
		</names>
		<date value="2003-01"/>
		<abstract>
			<richtext>
				<p>There has been ongoing confusion about the differences between Information Models and Data Models for defining managed objects in network management. This document explains the differences between these terms by analyzing how existing network management model specifications (from the IETF and other bodies such as the International Telecommunication Union (ITU) or the Distributed Management Task Force (DMTF)) fit into the universe of Information Models and Data Models.</p>
			</richtext>
		</abstract>
		<howpublished>Internet RFC 3444</howpublished>
		<title type="sharef:primaryTitle">On the Difference between Information Models and Data Models</title>
	</reference>
	<reference name="rfc3450" src="bibtex:misc" src-info="bibtex:line-43505" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Michael</givenname>
				<surname>Luby</surname>
			</person>
			<person>
				<givenname>Jim</givenname>
				<surname>Gemmell</surname>
			</person>
			<person>
				<givenname>Lorenzo</givenname>
				<surname>Vicisano</surname>
			</person>
			<person>
				<givenname>Luigi</givenname>
				<surname>Rizzo</surname>
			</person>
			<person>
				<givenname>Jon</givenname>
				<surname>Crowcroft</surname>
			</person>
		</names>
		<date value="2002-12"/>
		<abstract>
			<richtext>
				<p>This document describes the Asynchronous Layered Coding (ALC) protocol, a massively scalable reliable content delivery protocol. Asynchronous Layered Coding combines the Layered Coding Transport (LCT) building block, a multiple rate congestion control building block and the Forward Error Correction (FEC) building block to provide congestion controlled reliable asynchronous delivery of content to an unlimited number of concurrent receivers from a single sender.</p>
			</richtext>
		</abstract>
		<howpublished>Internet RFC 3450</howpublished>
		<title type="sharef:primaryTitle">Asynchronous Layered Coding (ALC) Protocol Instantiation</title>
		<field type="bibtex:topic">alc[1]</field>
	</reference>
	<reference name="rfc3451" src="bibtex:misc" src-info="bibtex:line-43515" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Michael</givenname>
				<surname>Luby</surname>
			</person>
			<person>
				<givenname>Jim</givenname>
				<surname>Gemmell</surname>
			</person>
			<person>
				<givenname>Lorenzo</givenname>
				<surname>Vicisano</surname>
			</person>
			<person>
				<givenname>Luigi</givenname>
				<surname>Rizzo</surname>
			</person>
			<person>
				<givenname>Mark J.</givenname>
				<surname>Handley</surname>
			</person>
			<person>
				<givenname>Jon</givenname>
				<surname>Crowcroft</surname>
			</person>
		</names>
		<date value="2002-12"/>
		<abstract>
			<richtext>
				<p>Layered Coding Transport (LCT) provides transport level support for reliable content delivery and stream delivery protocols. LCT is specifically designed to support protocols using IP multicast, but also provides support to protocols that use unicast. LCT is compatible with congestion control that provides multiple rate delivery to receivers and is also compatible with coding techniques that provide reliable delivery of content.</p>
			</richtext>
		</abstract>
		<howpublished>Internet RFC 3451</howpublished>
		<title type="sharef:primaryTitle">Layered Coding Transport (LCT) Building Block</title>
		<field type="bibtex:topic">lct[1]</field>
	</reference>
	<reference name="rfc3452" src="bibtex:misc" src-info="bibtex:line-43525" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Michael</givenname>
				<surname>Luby</surname>
			</person>
			<person>
				<givenname>Lorenzo</givenname>
				<surname>Vicisano</surname>
			</person>
			<person>
				<givenname>Jim</givenname>
				<surname>Gemmell</surname>
			</person>
			<person>
				<givenname>Luigi</givenname>
				<surname>Rizzo</surname>
			</person>
			<person>
				<givenname>Mark J.</givenname>
				<surname>Handley</surname>
			</person>
			<person>
				<givenname>Jon</givenname>
				<surname>Crowcroft</surname>
			</person>
		</names>
		<date value="2002-12"/>
		<abstract>
			<richtext>
				<p>This document generally describes how to use Forward Error Correction (FEC) codes to efficiently provide and/or augment reliability for data transport. The primary focus of this document is the application of FEC codes to one-to-many reliable data transport using IP multicast. This document describes what information is needed to identify a specific FEC code, what information needs to be communicated out-of-band to use the FEC code, and what information is needed in data packets to identify the encoding symbols they carry. The procedures for specifying FEC codes and registering them with the Internet Assigned Numbers Authority (IANA) are also described. This document should be read in conjunction with and uses the terminology of the companion document titled, "The Use of Forward Error Correction (FEC) in Reliable Multicast".</p>
			</richtext>
		</abstract>
		<howpublished>Internet RFC 3452</howpublished>
		<title type="sharef:primaryTitle">Forward Error Correction (FEC) Building Block</title>
		<field type="bibtex:topic">fec[1]</field>
	</reference>
	<reference name="rfc3453" src="bibtex:misc" src-info="bibtex:line-43535" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Michael</givenname>
				<surname>Luby</surname>
			</person>
			<person>
				<givenname>Lorenzo</givenname>
				<surname>Vicisano</surname>
			</person>
			<person>
				<givenname>Jim</givenname>
				<surname>Gemmell</surname>
			</person>
			<person>
				<givenname>Luigi</givenname>
				<surname>Rizzo</surname>
			</person>
			<person>
				<givenname>Mark J.</givenname>
				<surname>Handley</surname>
			</person>
			<person>
				<givenname>Jon</givenname>
				<surname>Crowcroft</surname>
			</person>
		</names>
		<date value="2002-12"/>
		<abstract>
			<richtext>
				<p>This memo describes the use of Forward Error Correction (FEC) codes to efficiently provide and/or augment reliability for one-to-many reliable data transport using IP multicast. One of the key properties of FEC codes in this context is the ability to use the same packets containing FEC data to simultaneously repair different packet loss patterns at multiple receivers. Different classes of FEC codes and some of their basic properties are described and terminology relevant to implementing FEC in a reliable multicast protocol is introduced. Examples are provided of possible abstract formats for packets carrying FEC.</p>
			</richtext>
		</abstract>
		<howpublished>Internet RFC 3453</howpublished>
		<title type="sharef:primaryTitle">The Use of Forward Error Correction (FEC) in Reliable Multicast</title>
		<field type="bibtex:topic">fec[1]</field>
	</reference>
	<reference name="rfc3454" src="bibtex:misc" src-info="bibtex:line-43545" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Paul E.</givenname>
				<surname>Hoffman</surname>
			</person>
			<person>
				<givenname>Marc</givenname>
				<surname>Blanchet</surname>
			</person>
		</names>
		<date value="2003-01"/>
		<howpublished>Internet RFC 3454</howpublished>
		<title type="sharef:primaryTitle">Preparation of Internationalized Strings ("stringprep")</title>
		<field type="bibtex:topic">i18n[0.9]</field>
	</reference>
	<reference name="rfc3458" src="bibtex:misc" src-info="bibtex:line-43554" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Eric</givenname>
				<surname>Burger</surname>
			</person>
			<person>
				<givenname>Emily</givenname>
				<surname>Candell</surname>
			</person>
			<person>
				<givenname>Graham</givenname>
				<surname>Klyne</surname>
			</person>
			<person>
				<givenname>Charles</givenname>
				<surname>Eliot</surname>
			</person>
		</names>
		<date value="2003-01"/>
		<abstract>
			<richtext>
				<p>This memo describes a new RFC 2822 message header, "Message-Context". This header provides information about the context and presentation characteristics of a message. A receiving user agent (UA) may use this information as a hint to optimally present the message.</p>
			</richtext>
		</abstract>
		<howpublished>Internet RFC 3458</howpublished>
		<title type="sharef:primaryTitle">Message Context for Internet Mail</title>
		<field type="bibtex:topic">smtp[0.9]</field>
	</reference>
	<reference name="rfc3459" src="bibtex:misc" src-info="bibtex:line-43564" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Eric</givenname>
				<surname>Burger</surname>
			</person>
		</names>
		<date value="2003-01"/>
		<abstract>
			<richtext>
				<p>This document describes the use of a mechanism for identifying body parts that a sender deems critical in a multi-part Internet mail message. The mechanism described is a parameter to Content-Disposition, as described by RFC 3204. By knowing what parts of a message the sender deems critical, a content gateway can intelligently handle multi-part messages when providing gateway services to systems of lesser capability. Critical content can help a content gateway to decide what parts to forward. It can indicate how hard a gateway should try to deliver a body part. It can help the gateway to pick body parts that are safe to silently delete when a system of lesser capability receives a message. In addition, critical content can help the gateway chose the notification strategy for the receiving system. Likewise, if the sender expects the destination to do some processing on a body part, critical content allows the sender to mark body parts that the receiver must process.</p>
			</richtext>
		</abstract>
		<howpublished>Internet RFC 3459</howpublished>
		<title type="sharef:primaryTitle">Critical Content Multi-purpose Internet Mail Extensions (MIME) Parameter</title>
		<field type="bibtex:topic">mime[0.9]</field>
	</reference>
	<reference name="rfc3461" src="bibtex:misc" src-info="bibtex:line-43574" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Keith</givenname>
				<surname>Moore</surname>
			</person>
		</names>
		<date value="2003-01"/>
		<abstract>
			<richtext>
				<p>This memo defines an extension to the Simple Mail Transfer Protocol (SMTP) service, which allows an SMTP client to specify (a) that Delivery Status Notifications (DSNs) should be generated under certain conditions, (b) whether such notifications should return the contents of the message, and (c) additional information, to be returned with a DSN, that allows the sender to identify both the recipient(s) for which the DSN was issued, and the transaction in which the original message was sent.</p>
			</richtext>
		</abstract>
		<howpublished>Internet RFC 3461</howpublished>
		<title type="sharef:primaryTitle">Simple Mail Transfer Protocol (SMTP) Service Extension for Delivery Status Notifications (DSNs)</title>
		<field type="bibtex:topic">smtp[0.9]</field>
	</reference>
	<reference name="rfc3462" src="bibtex:misc" src-info="bibtex:line-43584" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Gregory M.</givenname>
				<surname>Vaudreuil</surname>
			</person>
		</names>
		<date value="2003-01"/>
		<abstract>
			<richtext>
				<p>The Multipart/Report Multipurpose Internet Mail Extensions (MIME) content-type is a general "family" or "container" type for electronic mail reports of any kind. Although this memo defines only the use of the Multipart/Report content-type with respect to delivery status reports, mail processing programs will benefit if a single content- type is used to for all kinds of reports. This document is part of a four document set describing the delivery status report service. This collection includes the Simple Mail Transfer Protocol (SMTP) extensions to request delivery status reports, a MIME content for the reporting of delivery reports, an enumeration of extended status codes, and a multipart container for the delivery report, the original message, and a human-friendly summary of the failure.</p>
			</richtext>
		</abstract>
		<howpublished>Internet RFC 3462</howpublished>
		<title type="sharef:primaryTitle">The Multipart/Report Content Type for the Reporting of Mail System Administrative Messages</title>
		<field type="bibtex:topic">smtp[0.9]</field>
	</reference>
	<reference name="rfc3467" src="bibtex:misc" src-info="bibtex:line-43594" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>John C.</givenname>
				<surname>Klensin</surname>
			</person>
		</names>
		<date value="2003-02"/>
		<howpublished>Internet RFC 3467</howpublished>
		<title type="sharef:primaryTitle">Role of the Domain Name System (DNS)</title>
		<field type="bibtex:topic">dns[0.9] ldh[0.8] ace[0.8]</field>
	</reference>
	<reference name="rfc3470" src="bibtex:misc" src-info="bibtex:line-43603" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Scott</givenname>
				<surname>Hollenbeck</surname>
			</person>
			<person>
				<givenname>Marshall T.</givenname>
				<surname>Rose</surname>
			</person>
			<person>
				<givenname>Larry</givenname>
				<surname>Masinter</surname>
			</person>
		</names>
		<date value="2003-01"/>
		<howpublished>Internet RFC 3470</howpublished>
		<title type="sharef:primaryTitle">Guidelines for the Use of Extensible Markup Language (XML) within IETF Protocols</title>
		<field type="bibtex:topic">xml[0.8]</field>
	</reference>
	<reference name="rfc3490" src="bibtex:misc" src-info="bibtex:line-43612" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Patrik</givenname>
				<surname>Faltstrom</surname>
			</person>
			<person>
				<givenname>Paul E.</givenname>
				<surname>Hoffman</surname>
			</person>
			<person>
				<givenname>Adam M.</givenname>
				<surname>Costello</surname>
			</person>
		</names>
		<date value="2003-03"/>
		<howpublished>Internet RFC 3490</howpublished>
		<title type="sharef:primaryTitle">Internationalizing Domain Names in Applications (IDNA)</title>
		<field type="bibtex:topic">idn[1]</field>
	</reference>
	<reference name="rfc3491" src="bibtex:misc" src-info="bibtex:line-43621" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Paul E.</givenname>
				<surname>Hoffman</surname>
			</person>
			<person>
				<givenname>Marc</givenname>
				<surname>Blanchet</surname>
			</person>
		</names>
		<date value="2003-03"/>
		<howpublished>Internet RFC 3491</howpublished>
		<title type="sharef:primaryTitle">Nameprep: A Stringprep Profile for Internationalized Domain Names (IDN)</title>
		<field type="bibtex:topic">idn[0.9]</field>
	</reference>
	<reference name="rfc3492" src="bibtex:misc" src-info="bibtex:line-43630" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Adam M.</givenname>
				<surname>Costello</surname>
			</person>
		</names>
		<date value="2003-03"/>
		<howpublished>Internet RFC 3492</howpublished>
		<title type="sharef:primaryTitle">Punycode: A Bootstring encoding of Unicode for Internationalized Domain Names in Applications (IDNA)</title>
		<field type="bibtex:topic">idn[0.9]</field>
	</reference>
	<reference name="rfc3501" src="bibtex:misc" src-info="bibtex:line-43639" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Mark R.</givenname>
				<surname>Crispin</surname>
			</person>
		</names>
		<date value="2003-03"/>
		<howpublished>Internet RFC 3501</howpublished>
		<title type="sharef:primaryTitle">Internet Message Access Protocol — Version 4rev1</title>
		<field type="bibtex:topic">imap[1]</field>
		<field type="bibtex:updates">rfc2060</field>
	</reference>
	<reference name="rfc3502" src="bibtex:misc" src-info="bibtex:line-43649" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Mark R.</givenname>
				<surname>Crispin</surname>
			</person>
		</names>
		<date value="2003-03"/>
		<howpublished>Internet RFC 3502</howpublished>
		<title type="sharef:primaryTitle">Internet Message Access Protocol (IMAP) — MULTIAPPEND Extension</title>
		<field type="bibtex:topic">imap[0.9]</field>
	</reference>
	<reference name="rfc3505" src="bibtex:misc" src-info="bibtex:line-43658" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Donald E.</givenname>
				<surname>Eastlake</surname>
			</person>
		</names>
		<date value="2003-03"/>
		<howpublished>Internet RFC 3505</howpublished>
		<title type="sharef:primaryTitle">Electronic Commerce Modeling Language (ECML): Version 2 Requirements</title>
		<field type="bibtex:topic">ecml[0.9]</field>
		<field type="bibtex:updates">rfc3106</field>
	</reference>
	<reference name="rfc3508" src="bibtex:misc" src-info="bibtex:line-43668" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Orit</givenname>
				<surname>Levin</surname>
			</person>
		</names>
		<date value="2003-04"/>
		<howpublished>Internet RFC 3508</howpublished>
		<title type="sharef:primaryTitle">H.323 Uniform Resource Locator (URL) Scheme Registration</title>
		<field type="bibtex:topic">h323[0.9] url[0.8]</field>
	</reference>
	<reference name="rfc3510" src="bibtex:misc" src-info="bibtex:line-43677" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Robert</givenname>
				<surname>Herriot</surname>
			</person>
			<person>
				<givenname>Ira</givenname>
				<surname>McDonald</surname>
			</person>
		</names>
		<date value="2003-04"/>
		<howpublished>Internet RFC 3510</howpublished>
		<title type="sharef:primaryTitle">Internet Printing Protocol/1.1: IPP URL Scheme</title>
		<field type="bibtex:topic">ipp[0.9] url[0.8]</field>
		<field type="bibtex:updates">rfc2910</field>
	</reference>
	<reference name="rfc3516" src="bibtex:misc" src-info="bibtex:line-43687" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Lyndon</givenname>
				<surname>Nerenberg</surname>
			</person>
		</names>
		<date value="2003-04"/>
		<howpublished>Internet RFC 3516</howpublished>
		<title type="sharef:primaryTitle">IMAP4 Binary Content Extension</title>
		<field type="bibtex:topic">imap[0.9]</field>
	</reference>
	<reference name="rfc3529" src="bibtex:misc" src-info="bibtex:line-43696" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Ward K.</givenname>
				<surname>Harold</surname>
			</person>
		</names>
		<date value="2003-05"/>
		<howpublished>Internet RFC 3529</howpublished>
		<title type="sharef:primaryTitle">Using Extensible Markup Language-Remote Procedure Calling (XML-RPC) in Blocks Extensible Exchange Protocol (BEEP)</title>
		<field type="bibtex:topic">xmlrpc[0.7] beep[0.8]</field>
	</reference>
	<reference name="rfc3533" src="bibtex:misc" src-info="bibtex:line-43705" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Silvia</givenname>
				<surname>Pfeiffer</surname>
			</person>
		</names>
		<date value="2003-05"/>
		<howpublished>Internet RFC 3533</howpublished>
		<title type="sharef:primaryTitle">The Ogg Encapsulation Format Version 0</title>
		<field type="bibtex:topic">ogg[1]</field>
	</reference>
	<reference name="rfc3534" src="bibtex:misc" src-info="bibtex:line-43714" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Linus</givenname>
				<surname>Walleij</surname>
			</person>
		</names>
		<date value="2003-05"/>
		<howpublished>Internet RFC 3534</howpublished>
		<title type="sharef:primaryTitle">The application/ogg Media Type</title>
		<field type="bibtex:topic">ogg[0.9] mime[0.8]</field>
	</reference>
	<reference name="rfc3536" src="bibtex:misc" src-info="bibtex:line-43723" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Paul E.</givenname>
				<surname>Hoffman</surname>
			</person>
		</names>
		<date value="2003-05"/>
		<howpublished>Internet RFC 3536</howpublished>
		<title type="sharef:primaryTitle">Terminology Used in Internationalization in the IETF</title>
		<field type="bibtex:topic">i18n[0.8]</field>
	</reference>
	<reference name="rfc3538" src="bibtex:misc" src-info="bibtex:line-43732" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Yoshiaki</givenname>
				<surname>Kawatsura</surname>
			</person>
		</names>
		<date value="2003-06"/>
		<howpublished>Internet RFC 3538</howpublished>
		<title type="sharef:primaryTitle">Secure Electronic Transaction (SET) Supplement for the v1.0 Internet Open Trading Protocol (IOTP)</title>
		<field type="bibtex:topic">iotp[0.8] set[0.7]</field>
	</reference>
	<reference name="rfc3541" src="bibtex:misc" src-info="bibtex:line-43741" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Aaron E.</givenname>
				<surname>Walsh</surname>
			</person>
		</names>
		<date value="2003-05"/>
		<howpublished>Internet RFC 3541</howpublished>
		<title type="sharef:primaryTitle">A Uniform Resource Name (URN) Namespace for the Web3D Consortium (Web3D)</title>
		<field type="bibtex:topic">web3d[0.8] urn[0.7]</field>
	</reference>
	<reference name="rfc3544" src="bibtex:misc" src-info="bibtex:line-43750" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Tmima</givenname>
				<surname>Koren</surname>
			</person>
			<person>
				<givenname>Stephen L.</givenname>
				<surname>Casner</surname>
			</person>
			<person>
				<givenname>Carsten</givenname>
				<surname>Bormann</surname>
			</person>
		</names>
		<date value="2003-07"/>
		<howpublished>Internet RFC 3544</howpublished>
		<title type="sharef:primaryTitle">IP Header Compression over PPP</title>
		<field type="bibtex:topic">ip[0.9] ppp[0.9]</field>
		<field type="bibtex:updates">rfc2509</field>
	</reference>
	<reference name="rfc3546" src="bibtex:misc" src-info="bibtex:line-43760" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Simon</givenname>
				<surname>Blake-Wilson</surname>
			</person>
			<person>
				<givenname>Magnus</givenname>
				<surname>Nystrom</surname>
			</person>
			<person>
				<givenname>David</givenname>
				<surname>Hopwood</surname>
			</person>
			<person>
				<givenname>Jan</givenname>
				<surname>Mikkelsen</surname>
			</person>
			<person>
				<givenname>Tim</givenname>
				<surname>Wright</surname>
			</person>
		</names>
		<date value="2003-06"/>
		<howpublished>Internet RFC 3546</howpublished>
		<title type="sharef:primaryTitle">Transport Layer Security (TLS) Extensions</title>
		<field type="bibtex:topic">tls[0.9]</field>
		<field type="bibtex:updates">rfc2246</field>
	</reference>
	<reference name="rfc3548" src="bibtex:misc" src-info="bibtex:line-43770" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Simon</givenname>
				<surname>Josefsson</surname>
			</person>
		</names>
		<date value="2003-07"/>
		<abstract>
			<richtext>
				<p>This document describes the commonly used base 64, base 32, and base 16 encoding schemes. It also discusses the use of line-feeds in encoded data, use of padding in encoded data, use of non-alphabet characters in encoded data, and use of different encoding alphabets.</p>
			</richtext>
		</abstract>
		<howpublished>Internet RFC 3548</howpublished>
		<title type="sharef:primaryTitle">The Base16, Base32, and Base64 Data Encodings</title>
		<field type="bibtex:topic">base16[0.9] base32[1] base64[1]</field>
	</reference>
	<reference name="rfc3550" src="bibtex:misc" src-info="bibtex:line-43780" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Henning</givenname>
				<surname>Schulzrinne</surname>
			</person>
			<person>
				<givenname>Stephen L.</givenname>
				<surname>Casner</surname>
			</person>
			<person>
				<givenname>Ron</givenname>
				<surname>Frederick</surname>
			</person>
			<person>
				<givenname>Van</givenname>
				<surname>Jacobson</surname>
			</person>
		</names>
		<date value="2003-07"/>
		<howpublished>Internet RFC 3550</howpublished>
		<title type="sharef:primaryTitle">RTP: A Transport Protocol for Real-Time Applications</title>
		<field type="bibtex:topic">rtp[1]</field>
		<field type="bibtex:updates">rfc1889</field>
	</reference>
	<reference name="rfc3552" src="bibtex:misc" src-info="bibtex:line-43790" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Eric</givenname>
				<surname>Rescorla</surname>
			</person>
			<person>
				<givenname>Brian</givenname>
				<surname>Korver</surname>
			</person>
		</names>
		<date value="2003-07"/>
		<howpublished>Internet RFC 3552</howpublished>
		<title type="sharef:primaryTitle">Guidelines for Writing RFC Text on Security Considerations</title>
		<field type="bibtex:topic">rfc[0.9]</field>
	</reference>
	<reference name="rfc3553" src="bibtex:misc" src-info="bibtex:line-43799" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Michael</givenname>
				<surname>Mealling</surname>
			</person>
			<person>
				<givenname>Larry</givenname>
				<surname>Masinter</surname>
			</person>
			<person>
				<givenname>Ted</givenname>
				<surname>Hardie</surname>
			</person>
			<person>
				<givenname>Graham</givenname>
				<surname>Klyne</surname>
			</person>
		</names>
		<date value="2003-06"/>
		<howpublished>Internet RFC 3553</howpublished>
		<title type="sharef:primaryTitle">An IETF URN Sub-namespace for Registered Protocol Parameters</title>
		<field type="bibtex:topic">ietf[0.8] urn[0.7]</field>
	</reference>
	<reference name="rfc3565" src="bibtex:misc" src-info="bibtex:line-43808" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Jim</givenname>
				<surname>Schaad</surname>
			</person>
		</names>
		<date value="2003-07"/>
		<howpublished>Internet RFC 3565</howpublished>
		<title type="sharef:primaryTitle">Use of the Advanced Encryption Standard (AES) Encryption Algorithm in Cryptographic Message Syntax (CMS)</title>
		<field type="bibtex:topic">cms[0.8] aes[0.8]</field>
	</reference>
	<reference name="rfc3574" src="bibtex:misc" src-info="bibtex:line-43817" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Jonne</givenname>
				<surname>Soininen</surname>
			</person>
		</names>
		<date value="2003-08"/>
		<howpublished>Internet RFC 3574</howpublished>
		<title type="sharef:primaryTitle">Transition Scenarios for 3GPP Networks</title>
		<field type="bibtex:topic">thirdgpp[0.8]</field>
	</reference>
	<reference name="rfc3575" src="bibtex:misc" src-info="bibtex:line-43826" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Bernard</givenname>
				<surname>Aboba</surname>
			</person>
		</names>
		<date value="2003-07"/>
		<howpublished>Internet RFC 3575</howpublished>
		<title type="sharef:primaryTitle">IANA Considerations for RADIUS (Remote Authentication Dial In User Service)</title>
		<field type="bibtex:topic">radius[0.8]</field>
		<field type="bibtex:updates">rfc2865</field>
	</reference>
	<reference name="rfc3576" src="bibtex:misc" src-info="bibtex:line-43836" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Bernard</givenname>
				<surname>Aboba</surname>
			</person>
			<person>
				<givenname>Pat R.</givenname>
				<surname>Calhoun</surname>
			</person>
		</names>
		<date value="2003-09"/>
		<howpublished>Internet RFC 3576</howpublished>
		<title type="sharef:primaryTitle">RADIUS (Remote Authentication Dial In User Service) Support For Extensible Authentication Protocol (EAP)</title>
		<field type="bibtex:topic">radius[0.8] eap[0.8]</field>
		<field type="bibtex:updates">rfc2869</field>
	</reference>
	<reference name="rfc3597" src="bibtex:misc" src-info="bibtex:line-43846" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Andreas</givenname>
				<surname>Gustafsson</surname>
			</person>
		</names>
		<date value="2003-09"/>
		<howpublished>Internet RFC 3597</howpublished>
		<title type="sharef:primaryTitle">Handling of Unknown DNS Resource Record (RR) Types</title>
		<field type="bibtex:topic">dns[0.9]</field>
	</reference>
	<reference name="rfc3601" src="bibtex:misc" src-info="bibtex:line-43855" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Claudio</givenname>
				<surname>Allocchio</surname>
			</person>
		</names>
		<date value="2003-09"/>
		<howpublished>Internet RFC 3601</howpublished>
		<title type="sharef:primaryTitle">Text String Notation for Dial Sequences and Global Switched Telephone Network (GSTN) / E.164 Addresses</title>
		<field type="bibtex:topic">gstn[0.8]</field>
	</reference>
	<reference name="rfc3614" src="bibtex:misc" src-info="bibtex:line-43864" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>John R.</givenname>
				<surname>Smith</surname>
			</person>
		</names>
		<date value="2003-09"/>
		<howpublished>Internet RFC 3614</howpublished>
		<title type="sharef:primaryTitle">A Uniform Resource Name (URN) Namespace for the Motion Picture Experts Group (MPEG)</title>
		<field type="bibtex:topic">urn[0.7] mpeg[0.8]</field>
	</reference>
	<reference name="rfc3615" src="bibtex:misc" src-info="bibtex:line-43873" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Jean-Marc</givenname>
				<surname>Gustin</surname>
			</person>
			<person>
				<givenname>Andre</givenname>
				<surname>Goyens</surname>
			</person>
		</names>
		<date value="2003-09"/>
		<howpublished>Internet RFC 3615</howpublished>
		<title type="sharef:primaryTitle">A Uniform Resource Name (URN) Namespace for SWIFT Financial Messaging</title>
		<field type="bibtex:topic">urn[0.7] swift[0.8]</field>
	</reference>
	<reference name="rfc3616" src="bibtex:misc" src-info="bibtex:line-43882" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Fabio</givenname>
				<surname>Bellifemine</surname>
			</person>
			<person>
				<givenname>Ion</givenname>
				<surname>Constantinescu</surname>
			</person>
			<person>
				<givenname>Steven</givenname>
				<surname>Willmott</surname>
			</person>
		</names>
		<date value="2003-09"/>
		<howpublished>Internet RFC 3616</howpublished>
		<title type="sharef:primaryTitle">A Uniform Resource Name (URN) Namespace for Foundation for Intelligent Physical Agents (FIPA)</title>
		<field type="bibtex:topic">urn[0.7] fipa[0.8]</field>
	</reference>
	<reference name="rfc3617" src="bibtex:misc" src-info="bibtex:line-43891" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Eliot</givenname>
				<surname>Lear</surname>
			</person>
		</names>
		<date value="2003-10"/>
		<howpublished>Internet RFC 3617</howpublished>
		<title type="sharef:primaryTitle">Uniform Resource Identifier (URI) Scheme and Applicability Statement for the Trivial File Transfer Protocol (TFTP)</title>
		<field type="bibtex:topic">uri[0.7] tftp[0.8]</field>
	</reference>
	<reference name="rfc3629" src="bibtex:misc" src-info="bibtex:line-43900" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>François</givenname>
				<surname>Yergeau</surname>
			</person>
		</names>
		<date value="2003-11"/>
		<howpublished>Internet RFC 3629</howpublished>
		<title type="sharef:primaryTitle">UTF-8, a transformation format of ISO 10646</title>
		<field type="bibtex:topic">utf8[1] ucs[0.8]</field>
		<field type="bibtex:updates">rfc2279</field>
	</reference>
	<reference name="rfc3641" src="bibtex:misc" src-info="bibtex:line-43910" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Steven</givenname>
				<surname>Legg</surname>
			</person>
		</names>
		<date value="2003-10"/>
		<howpublished>Internet RFC 3641</howpublished>
		<title type="sharef:primaryTitle">Generic String Encoding Rules (GSER) for ASN.1 Types</title>
		<field type="bibtex:topic">gser[1] asn1[0.9]</field>
	</reference>
	<reference name="rfc3642" src="bibtex:misc" src-info="bibtex:line-43919" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Steven</givenname>
				<surname>Legg</surname>
			</person>
		</names>
		<date value="2003-10"/>
		<howpublished>Internet RFC 3642</howpublished>
		<title type="sharef:primaryTitle">Common Elements of Generic String Encoding Rules (GSER) Encodings</title>
		<field type="bibtex:topic">gser[1] asn1[0.9]</field>
	</reference>
	<reference name="rfc3647" src="bibtex:misc" src-info="bibtex:line-43928" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Santosh</givenname>
				<surname>Chokhani</surname>
			</person>
			<person>
				<givenname>Warwick</givenname>
				<surname>Ford</surname>
			</person>
			<person>
				<givenname>Randy V.</givenname>
				<surname>Sabett</surname>
			</person>
			<person>
				<givenname>Charles R.</givenname>
				<surname>Merrill</surname>
			</person>
			<person>
				<givenname>Stephen S.</givenname>
				<surname>Wu</surname>
			</person>
		</names>
		<date value="2003-11"/>
		<howpublished>Internet RFC 3647</howpublished>
		<title type="sharef:primaryTitle">Internet X.509 Public Key Infrastructure Certificate Policy and Certification Practices Framework</title>
		<field type="bibtex:topic">x509[1]</field>
		<field type="bibtex:updates">rfc2527</field>
	</reference>
	<reference name="rfc3650" src="bibtex:misc" src-info="bibtex:line-43938" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Sam X.</givenname>
				<surname>Sun</surname>
			</person>
			<person>
				<givenname>Larry</givenname>
				<surname>Lannom</surname>
			</person>
			<person>
				<givenname>Brian</givenname>
				<surname>Boesch</surname>
			</person>
		</names>
		<date value="2003-11"/>
		<howpublished>Internet RFC 3650</howpublished>
		<title type="sharef:primaryTitle">Handle System Overview</title>
		<field type="bibtex:topic">handlesystem[1]</field>
	</reference>
	<reference name="rfc3651" src="bibtex:misc" src-info="bibtex:line-43947" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Sam X.</givenname>
				<surname>Sun</surname>
			</person>
			<person>
				<givenname>Sean</givenname>
				<surname>Reilly</surname>
			</person>
			<person>
				<givenname>Larry</givenname>
				<surname>Lannom</surname>
			</person>
		</names>
		<date value="2003-11"/>
		<howpublished>Internet RFC 3651</howpublished>
		<title type="sharef:primaryTitle">Handle System Namespace and Service Definition</title>
		<field type="bibtex:topic">handlesystem[1]</field>
	</reference>
	<reference name="rfc3652" src="bibtex:misc" src-info="bibtex:line-43956" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Sam X.</givenname>
				<surname>Sun</surname>
			</person>
			<person>
				<givenname>Sean</givenname>
				<surname>Reilly</surname>
			</person>
			<person>
				<givenname>Larry</givenname>
				<surname>Lannom</surname>
			</person>
			<person>
				<givenname>Jason</givenname>
				<surname>Petrone</surname>
			</person>
		</names>
		<date value="2003-11"/>
		<howpublished>Internet RFC 3652</howpublished>
		<title type="sharef:primaryTitle">Handle System Protocol (ver 2.1) Specification</title>
		<field type="bibtex:topic">handlesystem[1]</field>
	</reference>
	<reference name="rfc3653" src="bibtex:misc" src-info="bibtex:line-43965" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>John M.</givenname>
				<surname>Boyer</surname>
			</person>
			<person>
				<givenname>Merlin</givenname>
				<surname>Hughes</surname>
			</person>
			<person>
				<givenname>Joseph M.</givenname>
				<surname>Reagle</surname>
			</person>
		</names>
		<date value="2003-12"/>
		<howpublished>Internet RFC 3653</howpublished>
		<title type="sharef:primaryTitle">XML-Signature XPath Filter 2.0</title>
		<field type="bibtex:topic">xmldsig[1] xpath1[0.7]</field>
	</reference>
	<reference name="rfc3663" src="bibtex:misc" src-info="bibtex:line-43974" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Andrew L.</givenname>
				<surname>Newton</surname>
			</person>
		</names>
		<date value="2003-12"/>
		<howpublished>Internet RFC 3663</howpublished>
		<title type="sharef:primaryTitle">Domain Administrative Data in Lightweight Directory Access Protocol (LDAP)</title>
		<field type="bibtex:topic">ldap[0.8]</field>
	</reference>
	<reference name="rfc3664" src="bibtex:misc" src-info="bibtex:line-43983" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Paul E.</givenname>
				<surname>Hoffman</surname>
			</person>
		</names>
		<date value="2004-01"/>
		<howpublished>Internet RFC 3664</howpublished>
		<title type="sharef:primaryTitle">The AES-XCBC-PRF-128 Algorithm for the Internet Key Exchange Protocol (IKE)</title>
		<field type="bibtex:topic">ike[0.9] aes[0.8]</field>
	</reference>
	<reference name="rfc3667" src="bibtex:misc" src-info="bibtex:line-43992" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Scott O.</givenname>
				<surname>Bradner</surname>
			</person>
		</names>
		<date value="2004-02"/>
		<abstract>
			<richtext>
				<p>The IETF policies about rights in Contributions to the IETF are designed to ensure that such Contributions can be made available to the IETF and Internet communities while permitting the authors to retain as many rights as possible. This memo details the IETF policies on rights in Contributions to the IETF. It also describes the objectives that the policies are designed to meet. This memo updates RFC 2026, and, with RFC 3668, replaces Section 10 of RFC 2026.</p>
			</richtext>
		</abstract>
		<howpublished>Internet RFC 3667</howpublished>
		<title type="sharef:primaryTitle">IETF Rights in Contributions</title>
		<field type="bibtex:topic">ietf[0.9]</field>
		<field type="bibtex:updates">rfc2026</field>
	</reference>
	<reference name="rfc3668" src="bibtex:misc" src-info="bibtex:line-44003" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Scott O.</givenname>
				<surname>Bradner</surname>
			</person>
		</names>
		<date value="2004-02"/>
		<abstract>
			<richtext>
				<p>The IETF policies about Intellectual Property Rights (IPR), such as patent rights, relative to technologies developed in the IETF are designed to ensure that IETF working groups and participants have as much information about any IPR constraints on a technical proposal as possible. The policies are also intended to benefit the Internet community and the public at large, while respecting the legitimate rights of IPR holders. This memo details the IETF policies concerning IPR related to technology worked on within the IETF. It also describes the objectives that the policies are designed to meet. This memo updates RFC 2026 and, with RFC 3667, replaces Section 10 of RFC 2026. This memo also updates paragraph 4 of Section 3.2 of RFC 2028, for all purposes, including reference [2] in RFC 2418.</p>
			</richtext>
		</abstract>
		<howpublished>Internet RFC 3668</howpublished>
		<title type="sharef:primaryTitle">Intellectual Property Rights in IETF Technology</title>
		<field type="bibtex:topic">ipr[0.9] ietf[0.9]</field>
		<field type="bibtex:updates">rfc2026</field>
	</reference>
	<reference name="rfc3671" src="bibtex:misc" src-info="bibtex:line-44014" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Kurt D.</givenname>
				<surname>Zeilenga</surname>
			</person>
		</names>
		<date value="2003-12"/>
		<howpublished>Internet RFC 3671</howpublished>
		<title type="sharef:primaryTitle">Collective Attributes in the Lightweight Directory Access Protocol (LDAP)</title>
		<field type="bibtex:topic">ldap[0.8]</field>
	</reference>
	<reference name="rfc3672" src="bibtex:misc" src-info="bibtex:line-44023" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Kurt D.</givenname>
				<surname>Zeilenga</surname>
			</person>
			<person>
				<givenname>Steven</givenname>
				<surname>Legg</surname>
			</person>
		</names>
		<date value="2003-12"/>
		<howpublished>Internet RFC 3672</howpublished>
		<title type="sharef:primaryTitle">Subentries in the Lightweight Directory Access Protocol (LDAP)</title>
		<field type="bibtex:topic">ldap[0.8]</field>
	</reference>
	<reference name="rfc3673" src="bibtex:misc" src-info="bibtex:line-44032" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Kurt D.</givenname>
				<surname>Zeilenga</surname>
			</person>
		</names>
		<date value="2003-12"/>
		<howpublished>Internet RFC 3673</howpublished>
		<title type="sharef:primaryTitle">Lightweight Directory Access Protocol version 3 (LDAPv3): All Operational Attributes</title>
		<field type="bibtex:topic">ldap[0.8]</field>
	</reference>
	<reference name="rfc3674" src="bibtex:misc" src-info="bibtex:line-44041" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Kurt D.</givenname>
				<surname>Zeilenga</surname>
			</person>
		</names>
		<date value="2003-12"/>
		<howpublished>Internet RFC 3674</howpublished>
		<title type="sharef:primaryTitle">Feature Discovery in Lightweight Directory Access Protocol (LDAP)</title>
		<field type="bibtex:topic">ldap[0.8]</field>
	</reference>
	<reference name="rfc3675" src="bibtex:misc" src-info="bibtex:line-44050" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Donald E.</givenname>
				<surname>Eastlake</surname>
			</person>
		</names>
		<date value="2004-02"/>
		<howpublished>Internet RFC 3675</howpublished>
		<title type="sharef:primaryTitle">.sex Considered Dangerous</title>
		<field type="bibtex:topic">dns[0.7]</field>
	</reference>
	<reference name="rfc3676" src="bibtex:misc" src-info="bibtex:line-44059" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Randall</givenname>
				<surname>Gellens</surname>
			</person>
		</names>
		<date value="2004-02"/>
		<howpublished>Internet RFC 3676</howpublished>
		<title type="sharef:primaryTitle">The Text/Plain Format and DelSp Parameters</title>
		<field type="bibtex:updates">rfc2646</field>
	</reference>
	<reference name="rfc3687" src="bibtex:misc" src-info="bibtex:line-44068" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Steven</givenname>
				<surname>Legg</surname>
			</person>
		</names>
		<date value="2004-02"/>
		<howpublished>Internet RFC 3687</howpublished>
		<title type="sharef:primaryTitle">Lightweight Directory Access Protocol (LDAP) and X.500 Component Matching Rules</title>
		<field type="bibtex:topic">ldap[0.7] x500[0.7]</field>
	</reference>
	<reference name="rfc3688" src="bibtex:misc" src-info="bibtex:line-44077" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Michael</givenname>
				<surname>Mealling</surname>
			</person>
		</names>
		<date value="2004-01"/>
		<howpublished>Internet RFC 3688</howpublished>
		<title type="sharef:primaryTitle">The IETF XML Registry</title>
		<field type="bibtex:topic">ietf[0.7] xml[0.7]</field>
	</reference>
	<reference name="rfc3693" src="bibtex:misc" src-info="bibtex:line-44086" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Jorge R.</givenname>
				<surname>Cuellar</surname>
			</person>
			<person>
				<givenname>John B.</givenname>
				<surname>Morris</surname>
			</person>
			<person>
				<givenname>Deirdre K.</givenname>
				<surname>Mulligan</surname>
			</person>
			<person>
				<givenname>Jon</givenname>
				<surname>Peterson</surname>
			</person>
			<person>
				<givenname>James M.</givenname>
				<surname>Polk</surname>
			</person>
		</names>
		<date value="2004-02"/>
		<abstract>
			<richtext>
				<p>Location-based services, navigation applications, emergency services, management of equipment in the field, and other location-dependent services need geographic location information about a Target (such as a user, resource or other entity). There is a need to securely gather and transfer location information for location services, while at the same time protect the privacy of the individuals involved. This document focuses on the authorization, security and privacy requirements for such location-dependent services. Specifically, it describes the requirements for the Geopriv Location Object (LO) and for the protocols that use this Location Object. This LO is envisioned to be the primary data structure used in all Geopriv protocol exchanges to securely transfer location data.</p>
			</richtext>
		</abstract>
		<howpublished>Internet RFC 3693</howpublished>
		<title type="sharef:primaryTitle">Geopriv Requirements</title>
		<field type="bibtex:topic">pidflo[0.9]</field>
	</reference>
	<reference name="rfc3694" src="bibtex:misc" src-info="bibtex:line-44096" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Michelle</givenname>
				<surname>Engelhardt Danley</surname>
			</person>
			<person>
				<givenname>Deirdre K.</givenname>
				<surname>Mulligan</surname>
			</person>
			<person>
				<givenname>John B.</givenname>
				<surname>Morris</surname>
			</person>
			<person>
				<givenname>Jon</givenname>
				<surname>Peterson</surname>
			</person>
		</names>
		<date value="2004-02"/>
		<abstract>
			<richtext>
				<p>This document provides some analysis of threats against the Geopriv protocol architecture. It focuses on protocol threats, threats that result from the storage of data by entities in the architecture, and threats posed by the abuse of information yielded by Geopriv. Some security properties that meet these threats are enumerated as a reference for Geopriv requirements.</p>
			</richtext>
		</abstract>
		<howpublished>Internet RFC 3694</howpublished>
		<title type="sharef:primaryTitle">Threat Analysis of the Geopriv Protocol</title>
	</reference>
	<reference name="rfc3707" src="bibtex:misc" src-info="bibtex:line-44105" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Andrew L.</givenname>
				<surname>Newton</surname>
			</person>
		</names>
		<date value="2004-02"/>
		<howpublished>Internet RFC 3707</howpublished>
		<title type="sharef:primaryTitle">Cross Registry Internet Service Protocol (CRISP) Requirements</title>
		<field type="bibtex:topic">crisp[0.9]</field>
	</reference>
	<reference name="rfc3709" src="bibtex:misc" src-info="bibtex:line-44114" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Stefan</givenname>
				<surname>Santesson</surname>
			</person>
			<person>
				<givenname>Russell</givenname>
				<surname>Housley</surname>
			</person>
			<person>
				<givenname>Trevor</givenname>
				<surname>Freeman</surname>
			</person>
		</names>
		<date value="2004-02"/>
		<howpublished>Internet RFC 3709</howpublished>
		<title type="sharef:primaryTitle">Internet X.509 Public Key Infrastructure: Logotypes in X.509 Certificates</title>
		<field type="bibtex:topic">pkix[0.9]</field>
	</reference>
	<reference name="rfc3711" src="bibtex:misc" src-info="bibtex:line-44123" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Mark</givenname>
				<surname>Baugher</surname>
			</person>
			<person>
				<givenname>Elisabetta</givenname>
				<surname>Carrara</surname>
			</person>
			<person>
				<givenname>David A.</givenname>
				<surname>McGrew</surname>
			</person>
			<person>
				<givenname>Mats</givenname>
				<surname>Naslund</surname>
			</person>
			<person>
				<givenname>Karl</givenname>
				<surname>Norrman</surname>
			</person>
		</names>
		<date value="2004-03"/>
		<howpublished>Internet RFC 3711</howpublished>
		<title type="sharef:primaryTitle">The Secure Real-time Transport Protocol (SRTP)</title>
		<field type="bibtex:topic">srtp[1]</field>
	</reference>
	<reference name="rfc3712" src="bibtex:misc" src-info="bibtex:line-44132" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Pat</givenname>
				<surname>Fleming</surname>
			</person>
			<person>
				<givenname>Ira</givenname>
				<surname>McDonald</surname>
			</person>
		</names>
		<date value="2004-02"/>
		<howpublished>Internet RFC 3712</howpublished>
		<title type="sharef:primaryTitle">Lightweight Directory Access Protocol (LDAP): Schema for Printer Services</title>
		<field type="bibtex:topic">ldap[0.9]</field>
	</reference>
	<reference name="rfc3724" src="bibtex:misc" src-info="bibtex:line-44141" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>James</givenname>
				<surname>Kempf</surname>
			</person>
			<person>
				<givenname>Rob</givenname>
				<surname>Austein</surname>
			</person>
		</names>
		<date value="2004-03"/>
		<howpublished>Internet RFC 3724</howpublished>
		<title type="sharef:primaryTitle">The Rise of the Middle and the Future of End-to-End: Reflections on the Evolution of the Internet Architecture</title>
	</reference>
	<reference name="rfc3730" src="bibtex:misc" src-info="bibtex:line-44149" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Scott</givenname>
				<surname>Hollenbeck</surname>
			</person>
		</names>
		<date value="2004-03"/>
		<howpublished>Internet RFC 3730</howpublished>
		<title type="sharef:primaryTitle">Extensible Provisioning Protocol (EPP)</title>
		<field type="bibtex:topic">epp[1]</field>
	</reference>
	<reference name="rfc3731" src="bibtex:misc" src-info="bibtex:line-44158" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Scott</givenname>
				<surname>Hollenbeck</surname>
			</person>
		</names>
		<date value="2004-03"/>
		<howpublished>Internet RFC 3731</howpublished>
		<title type="sharef:primaryTitle">Extensible Provisioning Protocol (EPP) Domain Name Mapping</title>
		<field type="bibtex:topic">epp[1]</field>
	</reference>
	<reference name="rfc3732" src="bibtex:misc" src-info="bibtex:line-44167" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Scott</givenname>
				<surname>Hollenbeck</surname>
			</person>
		</names>
		<date value="2004-03"/>
		<howpublished>Internet RFC 3732</howpublished>
		<title type="sharef:primaryTitle">Extensible Provisioning Protocol (EPP) Host Mapping</title>
		<field type="bibtex:topic">epp[1]</field>
	</reference>
	<reference name="rfc3733" src="bibtex:misc" src-info="bibtex:line-44176" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Scott</givenname>
				<surname>Hollenbeck</surname>
			</person>
		</names>
		<date value="2004-03"/>
		<howpublished>Internet RFC 3733</howpublished>
		<title type="sharef:primaryTitle">Extensible Provisioning Protocol (EPP) Contact Mapping</title>
		<field type="bibtex:topic">epp[1]</field>
	</reference>
	<reference name="rfc3734" src="bibtex:misc" src-info="bibtex:line-44185" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Scott</givenname>
				<surname>Hollenbeck</surname>
			</person>
		</names>
		<date value="2004-03"/>
		<howpublished>Internet RFC 3734</howpublished>
		<title type="sharef:primaryTitle">Extensible Provisioning Protocol (EPP) Transport Over TCP</title>
		<field type="bibtex:topic">epp[1]</field>
	</reference>
	<reference name="rfc3735" src="bibtex:misc" src-info="bibtex:line-44194" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Scott</givenname>
				<surname>Hollenbeck</surname>
			</person>
		</names>
		<date value="2004-03"/>
		<howpublished>Internet RFC 3735</howpublished>
		<title type="sharef:primaryTitle">Guidelines for Extending the Extensible Provisioning Protocol (EPP)</title>
		<field type="bibtex:topic">epp[0.9]</field>
	</reference>
	<reference name="rfc3739" src="bibtex:misc" src-info="bibtex:line-44203" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Stefan</givenname>
				<surname>Santesson</surname>
			</person>
			<person>
				<givenname>Tim</givenname>
				<surname>Polk</surname>
			</person>
			<person>
				<givenname>Magnus</givenname>
				<surname>Nystrom</surname>
			</person>
		</names>
		<date value="2004-03"/>
		<howpublished>Internet RFC 3739</howpublished>
		<title type="sharef:primaryTitle">Internet X.509 Public Key Infrastructure: Qualified Certificates Profile</title>
		<field type="bibtex:topic">pkix[0.9]</field>
		<field type="bibtex:updates">rfc3039</field>
	</reference>
	<reference name="rfc3741" src="bibtex:misc" src-info="bibtex:line-44213" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>John M.</givenname>
				<surname>Boyer</surname>
			</person>
			<person>
				<givenname>Donald E.</givenname>
				<surname>Eastlake</surname>
			</person>
			<person>
				<givenname>Joseph M.</givenname>
				<surname>Reagle</surname>
			</person>
		</names>
		<date value="2004-03"/>
		<howpublished>Internet RFC 3741</howpublished>
		<title type="sharef:primaryTitle">Exclusive XML Canonicalization, Version 1.0</title>
		<field type="bibtex:topic">canonicalxml[1]</field>
	</reference>
	<reference name="rfc3744" src="bibtex:misc" src-info="bibtex:line-44222" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Geoffrey</givenname>
				<surname>Clemm</surname>
			</person>
			<person>
				<givenname>Julian F.</givenname>
				<surname>Reschke</surname>
			</person>
			<person>
				<givenname>Eric</givenname>
				<surname>Sedlar</surname>
			</person>
			<person>
				<givenname>E. James</givenname>
				<surname>Whitehead</surname>
			</person>
		</names>
		<date value="2004-05"/>
		<howpublished>Internet RFC 3744</howpublished>
		<title type="sharef:primaryTitle">Web Distributed Authoring and Versioning (WebDAV) Access Control Protocol</title>
		<field type="bibtex:topic">webdav[0.9]</field>
	</reference>
	<reference name="rfc3745" src="bibtex:misc" src-info="bibtex:line-44231" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>David</givenname>
				<surname>Singer</surname>
			</person>
			<person>
				<givenname>Richard</givenname>
				<surname>Clark</surname>
			</person>
			<person>
				<givenname>Daniel T.</givenname>
				<surname>Lee</surname>
			</person>
		</names>
		<date value="2004-04"/>
		<abstract>
			<richtext>
				<p>This document serves to register and document the standard MIME types associated with the ISO/IEC 15444 standards, commonly known as JPEG 2000 (Joint Photographic Experts Group).</p>
			</richtext>
		</abstract>
		<howpublished>Internet RFC 3745</howpublished>
		<title type="sharef:primaryTitle">MIME Type Registrations for JPEG 2000 (ISO/IEC 15444)</title>
		<field type="bibtex:topic">jpeg2000[0.8] mime[0.8] jp2[0.9] jpx[0.9]</field>
	</reference>
	<reference name="rfc3748" src="bibtex:misc" src-info="bibtex:line-44241" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Bernard</givenname>
				<surname>Aboba</surname>
			</person>
			<person>
				<givenname>Larry J.</givenname>
				<surname>Blunk</surname>
			</person>
			<person>
				<givenname>John R.</givenname>
				<surname>Vollbrecht</surname>
			</person>
			<person>
				<givenname>James</givenname>
				<surname>Carlson</surname>
			</person>
			<person>
				<givenname>Henrik</givenname>
				<surname>Levkowetz</surname>
			</person>
		</names>
		<date value="2004-06"/>
		<howpublished>Internet RFC 3748</howpublished>
		<title type="sharef:primaryTitle">Extensible Authentication Protocol (EAP)</title>
		<field type="bibtex:topic">jpeg2000[0.9] mime[0.8]</field>
		<field type="bibtex:updates">rfc2284</field>
	</reference>
	<reference name="rfc3757" src="bibtex:misc" src-info="bibtex:line-44251" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Olaf M.</givenname>
				<surname>Kolkman</surname>
			</person>
			<person>
				<givenname>Jakob</givenname>
				<surname>Schlyter</surname>
			</person>
			<person>
				<givenname>Edward P.</givenname>
				<surname>Lewis</surname>
			</person>
		</names>
		<date value="2004-04"/>
		<howpublished>Internet RFC 3757</howpublished>
		<title type="sharef:primaryTitle">Domain Name System KEY (DNSKEY) Resource Record (RR) Secure Entry Point (SEP) Flag</title>
		<field type="bibtex:topic">dns[0.9]</field>
	</reference>
	<reference name="rfc3761" src="bibtex:misc" src-info="bibtex:line-44260" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Patrik</givenname>
				<surname>Faltstrom</surname>
			</person>
			<person>
				<givenname>Michael</givenname>
				<surname>Mealling</surname>
			</person>
		</names>
		<date value="2004-04"/>
		<abstract>
			<richtext>
				<p>This document discusses the use of the Domain Name System (DNS) for storage of E.164 numbers. More specifically, how DNS can be used for identifying available services connected to one E.164 number. It specifically obsoletes RFC 2916 to bring it in line with the Dynamic Delegation Discovery System (DDDS) Application specification found in the document series specified in RFC 3401. It is very important to note that it is impossible to read and understand this document without reading the documents discussed in RFC 3401.</p>
			</richtext>
		</abstract>
		<howpublished>Internet RFC 3761</howpublished>
		<title type="sharef:primaryTitle">The E.164 to Uniform Resource Identifiers (URI) Dynamic Delegation Discovery System (DDDS) Application (ENUM)</title>
		<field type="bibtex:topic">enum[1]</field>
	</reference>
	<reference name="rfc3778" src="bibtex:misc" src-info="bibtex:line-44270" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Edward A.</givenname>
				<surname>Taft</surname>
			</person>
			<person>
				<givenname>James D.</givenname>
				<surname>Pravetz</surname>
			</person>
			<person>
				<givenname>Stephen</givenname>
				<surname>Zilles</surname>
			</person>
			<person>
				<givenname>Larry</givenname>
				<surname>Masinter</surname>
			</person>
		</names>
		<date value="2004-05"/>
		<abstract>
			<richtext>
				<p>PDF, the 'Portable Document Format', is a general document representation language that has been in use for document exchange on the Internet since 1993. This document provides an overview of the PDF format, explains the mechanisms for digital signatures and encryption within PDF files, and updates the media type registration of 'application/pdf'.</p>
			</richtext>
		</abstract>
		<howpublished>Internet RFC 3778</howpublished>
		<title type="sharef:primaryTitle">The application/pdf Media Type</title>
		<field type="bibtex:topic">pdf[0.9] mime[0.8]</field>
	</reference>
	<reference name="rfc3779" src="bibtex:misc" src-info="bibtex:line-44280" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Charles</givenname>
				<surname>Lynn</surname>
			</person>
			<person>
				<givenname>Stephen</givenname>
				<surname>Kent</surname>
			</person>
			<person>
				<givenname>Karen</givenname>
				<surname>Seo</surname>
			</person>
		</names>
		<date value="2004-06"/>
		<howpublished>Internet RFC 3779</howpublished>
		<title type="sharef:primaryTitle">X.509 Extensions for IP Addresses and AS Identifiers</title>
		<field type="bibtex:topic">x509[0.9]</field>
	</reference>
	<reference name="rfc3798" src="bibtex:misc" src-info="bibtex:line-44289" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Tony</givenname>
				<surname>Hansen</surname>
			</person>
			<person>
				<givenname>Gregory M.</givenname>
				<surname>Vaudreuil</surname>
			</person>
		</names>
		<date value="2004-05"/>
		<howpublished>Internet RFC 3798</howpublished>
		<title type="sharef:primaryTitle">Message Disposition Notification</title>
		<field type="bibtex:topic">mime[0.9]</field>
		<field type="bibtex:updates">rfc2298</field>
	</reference>
	<reference name="rfc3803" src="bibtex:misc" src-info="bibtex:line-44299" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Gregory M.</givenname>
				<surname>Vaudreuil</surname>
			</person>
			<person>
				<givenname>Glenn W.</givenname>
				<surname>Parsons</surname>
			</person>
		</names>
		<date value="2004-06"/>
		<howpublished>Internet RFC 3803</howpublished>
		<title type="sharef:primaryTitle">Content Duration MIME Header Definition</title>
		<field type="bibtex:topic">mime[0.9]</field>
		<field type="bibtex:updates">rfc2424</field>
	</reference>
	<reference name="rfc3817" src="bibtex:misc" src-info="bibtex:line-44309" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>W. Mark</givenname>
				<surname>Townsley</surname>
			</person>
			<person>
				<givenname>Ron</givenname>
				<surname link="da">Silva</surname>
			</person>
		</names>
		<date value="2004-06"/>
		<howpublished>Internet RFC 3817</howpublished>
		<title type="sharef:primaryTitle">Layer 2 Tunneling Protocol (L2TP) Active Discovery Relay for PPP over Ethernet (PPPoE)</title>
		<field type="bibtex:topic">l2tp[0.9] pppoe[0.9]</field>
	</reference>
	<reference name="rfc3818" src="bibtex:misc" src-info="bibtex:line-44318" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Vernon</givenname>
				<surname>Schryver</surname>
			</person>
		</names>
		<date value="2004-06"/>
		<howpublished>Internet RFC 3818</howpublished>
		<title type="sharef:primaryTitle">IANA Considerations for the Point-to-Point Protocol (PPP)</title>
		<field type="bibtex:topic">ppp[0.9]</field>
	</reference>
	<reference name="rfc3820" src="bibtex:misc" src-info="bibtex:line-44327" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Steven</givenname>
				<surname>Tuecke</surname>
			</person>
			<person>
				<givenname>Von</givenname>
				<surname>Welch</surname>
			</person>
			<person>
				<givenname>Doug</givenname>
				<surname>Engert</surname>
			</person>
			<person>
				<givenname>Laura</givenname>
				<surname>Pearlman</surname>
			</person>
			<person>
				<givenname>Mary</givenname>
				<surname>Thompson</surname>
			</person>
		</names>
		<date value="2004-06"/>
		<howpublished>Internet RFC 3820</howpublished>
		<title type="sharef:primaryTitle">Internet X.509 Public Key Infrastructure (PKI) Proxy Certificate Profile</title>
		<field type="bibtex:topic">pkix[0.9]</field>
	</reference>
	<reference name="rfc3823" src="bibtex:misc" src-info="bibtex:line-44336" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Ben</givenname>
				<surname>Kovitz</surname>
			</person>
		</names>
		<date value="2004-06"/>
		<howpublished>Internet RFC 3823</howpublished>
		<title type="sharef:primaryTitle">MIME Media Type for the Systems Biology Markup Language (SBML)</title>
		<field type="bibtex:topic">sbml[0.9] mime[0.8]</field>
	</reference>
	<reference name="rfc3825" src="bibtex:misc" src-info="bibtex:line-44345" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>James M.</givenname>
				<surname>Polk</surname>
			</person>
			<person>
				<givenname>John</givenname>
				<surname>Schnizlein</surname>
			</person>
			<person>
				<givenname>Marc</givenname>
				<surname>Linsner</surname>
			</person>
		</names>
		<date value="2004-07"/>
		<howpublished>Internet RFC 3825</howpublished>
		<title type="sharef:primaryTitle">Dynamic Host Configuration Protocol Option for Coordinate-based Location Configuration Information</title>
		<field type="bibtex:topic">dhcp[0.8] lci[1]</field>
	</reference>
	<reference name="rfc3826" src="bibtex:misc" src-info="bibtex:line-44354" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Uri</givenname>
				<surname>Blumenthal</surname>
			</person>
			<person>
				<givenname>Fabio</givenname>
				<surname>Maino</surname>
			</person>
			<person>
				<givenname>Keith</givenname>
				<surname>McCloghrie</surname>
			</person>
		</names>
		<date value="2004-06"/>
		<howpublished>Internet RFC 3826</howpublished>
		<title type="sharef:primaryTitle">The Advanced Encryption Standard (AES) Cipher Algorithm in the SNMP User-based Security Model</title>
		<field type="bibtex:topic">aes[0.8] snmp[0.8]</field>
	</reference>
	<reference name="rfc3828" src="bibtex:misc" src-info="bibtex:line-44363" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Lars-Ake</givenname>
				<surname>Larzon</surname>
			</person>
			<person>
				<givenname>Mikael</givenname>
				<surname>Degermark</surname>
			</person>
			<person>
				<givenname>Stephen</givenname>
				<surname>Pink</surname>
			</person>
			<person>
				<givenname>Lars-Erik</givenname>
				<surname>Jonsson</surname>
			</person>
			<person>
				<givenname>Godred</givenname>
				<surname>Fairhurst</surname>
			</person>
		</names>
		<date value="2004-07"/>
		<howpublished>Internet RFC 3828</howpublished>
		<title type="sharef:primaryTitle">The Lightweight User Datagram Protocol (UDP-Lite)</title>
		<field type="bibtex:topic">udplite[1]</field>
	</reference>
	<reference name="rfc3829" src="bibtex:misc" src-info="bibtex:line-44372" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Rob</givenname>
				<surname>Weltman</surname>
			</person>
			<person>
				<givenname>Mark</givenname>
				<surname>Smith</surname>
			</person>
			<person>
				<givenname>Mark</givenname>
				<surname>Wahl</surname>
			</person>
		</names>
		<date value="2004-07"/>
		<howpublished>Internet RFC 3829</howpublished>
		<title type="sharef:primaryTitle">Lightweight Directory Access Protocol (LDAP) Authorization Identity Request and Response Controls</title>
		<field type="bibtex:topic">ldap[0.9]</field>
	</reference>
	<reference name="rfc3840" src="bibtex:misc" src-info="bibtex:line-44381" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Jonathan</givenname>
				<surname>Rosenberg</surname>
			</person>
			<person>
				<givenname>Henning</givenname>
				<surname>Schulzrinne</surname>
			</person>
			<person>
				<givenname>Paul</givenname>
				<surname>Kyzivat</surname>
			</person>
		</names>
		<date value="2004-08"/>
		<abstract>
			<richtext>
				<p>This specification defines mechanisms by which a Session Initiation Protocol (SIP) user agent can convey its capabilities and characteristics to other user agents and to the registrar for its domain. This information is conveyed as parameters of the Contact header field.</p>
			</richtext>
		</abstract>
		<howpublished>Internet RFC 3840</howpublished>
		<title type="sharef:primaryTitle">Indicating User Agent Capabilities in the Session Initiation Protocol (SIP)</title>
		<field type="bibtex:topic">sip[0.9]</field>
	</reference>
	<reference name="rfc3850" src="bibtex:misc" src-info="bibtex:line-44391" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Blake</givenname>
				<surname>Ramsdell</surname>
			</person>
		</names>
		<date value="2004-07"/>
		<abstract>
			<richtext>
				<p>This document specifies conventions for X.509 certificate usage by Secure/Multipurpose Internet Mail Extensions (S/MIME) agents. S/MIME provides a method to send and receive secure MIME messages, and certificates are an integral part of S/MIME agent processing. S/MIME agents validate certificates as described in RFC 3280, the Internet X.509 Public Key Infrastructure Certificate and CRL Profile. S/MIME agents must meet the certificate processing requirements in this document as well as those in RFC 3280.</p>
			</richtext>
		</abstract>
		<howpublished>Internet RFC 3850</howpublished>
		<title type="sharef:primaryTitle">Secure/Multipurpose Internet Mail Extensions (S/MIME) Version 3.1 Certificate Handling</title>
		<field type="bibtex:topic">smime[1]</field>
		<field type="bibtex:updates">rfc2632</field>
	</reference>
	<reference name="rfc3851" src="bibtex:misc" src-info="bibtex:line-44402" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Blake</givenname>
				<surname>Ramsdell</surname>
			</person>
		</names>
		<date value="2004-07"/>
		<abstract>
			<richtext>
				<p>This document defines Secure/Multipurpose Internet Mail Extensions (S/MIME) version 3.1. S/MIME provides a consistent way to send and receive secure MIME data. Digital signatures provide authentication, message integrity, and non-repudiation with proof of origin. Encryption provides data confidentiality. Compression can be used to reduce data size. This document obsoletes RFC 2633.</p>
			</richtext>
		</abstract>
		<howpublished>Internet RFC 3851</howpublished>
		<title type="sharef:primaryTitle">Secure/Multipurpose Internet Mail Extensions (S/MIME) Version 3.1 Message Specification</title>
		<field type="bibtex:topic">smime[1]</field>
		<field type="bibtex:updates">rfc2633</field>
	</reference>
	<reference name="rfc3852" src="bibtex:misc" src-info="bibtex:line-44413" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Russell</givenname>
				<surname>Housley</surname>
			</person>
		</names>
		<date value="2004-07"/>
		<abstract>
			<richtext>
				<p>This document describes the Cryptographic Message Syntax (CMS). This syntax is used to digitally sign, digest, authenticate, or encrypt arbitrary message content.</p>
			</richtext>
		</abstract>
		<howpublished>Internet RFC 3852</howpublished>
		<title type="sharef:primaryTitle">Cryptographic Message Syntax (CMS)</title>
		<field type="bibtex:topic">cms[1]</field>
		<field type="bibtex:updates">rfc3369</field>
	</reference>
	<reference name="rfc3853" src="bibtex:misc" src-info="bibtex:line-44424" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Jon</givenname>
				<surname>Peterson</surname>
			</person>
		</names>
		<date value="2004-07"/>
		<abstract>
			<richtext>
				<p>RFC 3261 currently specifies 3DES as the mandatory-to-implement ciphersuite for implementations of S/MIME in the Session Initiation Protocol (SIP). This document updates the normative guidance of RFC 3261 to require the Advanced Encryption Standard (AES) for S/MIME.</p>
			</richtext>
		</abstract>
		<howpublished>Internet RFC 3853</howpublished>
		<title type="sharef:primaryTitle">S/MIME Advanced Encryption Standard (AES) Requirement for the Session Initiation Protocol (SIP)</title>
		<field type="bibtex:topic">smime[0.9] aes[0.7]</field>
	</reference>
	<reference name="rfc3854" src="bibtex:misc" src-info="bibtex:line-44434" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Paul E.</givenname>
				<surname>Hoffman</surname>
			</person>
			<person>
				<givenname>Chris</givenname>
				<surname>Bonatti</surname>
			</person>
			<person>
				<givenname>Anders</givenname>
				<surname>Eggen</surname>
			</person>
		</names>
		<date value="2004-07"/>
		<abstract>
			<richtext>
				<p>This document describes a protocol for adding cryptographic signature and encryption services to X.400 content with Secure/Multipurpose Internet Mail Extensions (S/MIME).</p>
			</richtext>
		</abstract>
		<howpublished>Internet RFC 3854</howpublished>
		<title type="sharef:primaryTitle">Securing X.400 Content with Secure/Multipurpose Internet Mail Extensions (S/MIME)</title>
		<field type="bibtex:topic">smime[0.7] x400[0.9]</field>
	</reference>
	<reference name="rfc3855" src="bibtex:misc" src-info="bibtex:line-44444" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Paul E.</givenname>
				<surname>Hoffman</surname>
			</person>
			<person>
				<givenname>Chris</givenname>
				<surname>Bonatti</surname>
			</person>
		</names>
		<date value="2004-07"/>
		<abstract>
			<richtext>
				<p>This document describes protocol options for conveying objects that have been protected using the Cryptographic Message Syntax (CMS) and Secure/Multipurpose Internet Mail Extensions (S/MIME) version 3.1 over an X.400 message transfer system.</p>
			</richtext>
		</abstract>
		<howpublished>Internet RFC 3855</howpublished>
		<title type="sharef:primaryTitle">Transporting Secure/Multipurpose Internet Mail Extensions (S/MIME) Objects in X.400</title>
		<field type="bibtex:topic">smime[0.7] x400[0.9]</field>
	</reference>
	<reference name="rfc3858" src="bibtex:misc" src-info="bibtex:line-44454" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Jonathan</givenname>
				<surname>Rosenberg</surname>
			</person>
		</names>
		<date value="2004-08"/>
		<abstract>
			<richtext>
				<p>Watchers are defined as entities that request (i.e., subscribe to) information about a resource. There is fairly complex state associated with these subscriptions. The union of the state for all subscriptions to a particular resource is called the watcher information for that resource. This state is dynamic, changing as subscribers come and go. As a result, it is possible, and indeed useful, to subscribe to the watcher information for a particular resource. In order to enable this, a format is needed to describe the state of watchers on a resource. This specification describes an Extensible Markup Language (XML) document format for such state.</p>
			</richtext>
		</abstract>
		<howpublished>Internet RFC 3858</howpublished>
		<title type="sharef:primaryTitle">An Extensible Markup Language (XML) Based Format for Watcher Information</title>
		<field type="bibtex:topic">sip[0.9]</field>
	</reference>
	<reference name="rfc3859" src="bibtex:misc" src-info="bibtex:line-44464" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Jon</givenname>
				<surname>Peterson</surname>
			</person>
		</names>
		<date value="2004-08"/>
		<abstract>
			<richtext>
				<p>At the time this document was written, numerous presence protocols  were in use (largely as components of commercial instant messaging services), and little interoperability between services based on these protocols has been achieved. This specification defines common semantics and data formats for presence to facilitate the creation of gateways between presence services.</p>
			</richtext>
		</abstract>
		<howpublished>Internet RFC 3859</howpublished>
		<title type="sharef:primaryTitle">Common Profile for Presence (CPP)</title>
		<field type="bibtex:topic">cpp[1]</field>
	</reference>
	<reference name="rfc3860" src="bibtex:misc" src-info="bibtex:line-44474" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Jon</givenname>
				<surname>Peterson</surname>
			</person>
		</names>
		<date value="2004-08"/>
		<abstract>
			<richtext>
				<p>At the time this document was written, numerous instant messaging protocols were in use, and little interoperability between services based on these protocols has been achieved. This specification defines common semantics and data formats for instant messaging to facilitate the creation of gateways between instant messaging services.</p>
			</richtext>
		</abstract>
		<howpublished>Internet RFC 3860</howpublished>
		<title type="sharef:primaryTitle">Common Profile for Instant Messaging (CPIM)</title>
		<field type="bibtex:topic">cpim[1]</field>
	</reference>
	<reference name="rfc3861" src="bibtex:misc" src-info="bibtex:line-44484" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Jon</givenname>
				<surname>Peterson</surname>
			</person>
		</names>
		<date value="2004-08"/>
		<abstract>
			<richtext>
				<p>Presence and instant messaging are defined in RFC 2778. The Common Profiles for Presence and Instant Messaging define two Universal Resource Identifier (URI) schemes: 'im' for INSTANT INBOXes and 'pres' for PRESENTITIES. This document provides guidance for locating the resources associated with URIs that employ these schemes.</p>
			</richtext>
		</abstract>
		<howpublished>Internet RFC 3861</howpublished>
		<title type="sharef:primaryTitle">Address Resolution for Instant Messaging and Presence</title>
		<field type="bibtex:topic">cpp[0.9] cpim[0.9]</field>
	</reference>
	<reference name="rfc3862" src="bibtex:misc" src-info="bibtex:line-44494" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Graham</givenname>
				<surname>Klyne</surname>
			</person>
			<person>
				<givenname>Derek</givenname>
				<surname>Atkins</surname>
			</person>
		</names>
		<date value="2004-08"/>
		<abstract>
			<richtext>
				<p>This memo defines the MIME content type 'Message/CPIM', a message format for protocols that conform to the Common Profile for Instant Messaging (CPIM) specification.</p>
			</richtext>
		</abstract>
		<howpublished>Internet RFC 3862</howpublished>
		<title type="sharef:primaryTitle">Common Presence and Instant Messaging (CPIM): Message Format</title>
		<field type="bibtex:topic">cpim[0.9]</field>
	</reference>
	<reference name="rfc3863" src="bibtex:misc" src-info="bibtex:line-44504" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Hiroyasu</givenname>
				<surname>Sugano</surname>
			</person>
			<person>
				<givenname>Shingo</givenname>
				<surname>Fujimoto</surname>
			</person>
			<person>
				<givenname>Graham</givenname>
				<surname>Klyne</surname>
			</person>
			<person>
				<givenname>Adrian</givenname>
				<surname>Bateman</surname>
			</person>
			<person>
				<givenname>Wayne</givenname>
				<surname>Carr</surname>
			</person>
			<person>
				<givenname>Jon</givenname>
				<surname>Peterson</surname>
			</person>
		</names>
		<date value="2004-08"/>
		<abstract>
			<richtext>
				<p>This memo specifies the Common Profile for Presence (CPP) Presence Information Data Format (PIDF) as a common presence data format for CPP-compliant Presence protocols, and also defines a new media type "application/pidf+xml" to represent the XML MIME entity for PIDF.</p>
			</richtext>
		</abstract>
		<howpublished>Internet RFC 3863</howpublished>
		<title type="sharef:primaryTitle">Presence Information Data Format (PIDF)</title>
		<field type="bibtex:topic">pdif[1] cpp[0.9]</field>
	</reference>
	<reference name="rfc3864" src="bibtex:misc" src-info="bibtex:line-44514" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Graham</givenname>
				<surname>Klyne</surname>
			</person>
			<person>
				<givenname>Mark</givenname>
				<surname>Nottingham</surname>
			</person>
			<person>
				<givenname>Jeffrey C.</givenname>
				<surname>Mogul</surname>
			</person>
		</names>
		<date value="2004-09"/>
		<abstract>
			<richtext>
				<p>This specification defines registration procedures for the message header fields used by Internet mail, HTTP, Netnews and other applications.</p>
			</richtext>
		</abstract>
		<howpublished>Internet RFC 3864</howpublished>
		<title type="sharef:primaryTitle">Registration Procedures for Message Header Fields</title>
		<field type="bibtex:topic">http[0.9] smtp[0.9] mime[0.9] usenetnews[0.9]</field>
	</reference>
	<reference name="rfc3865" src="bibtex:misc" src-info="bibtex:line-44524" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Carl</givenname>
				<surname>Malamud</surname>
			</person>
		</names>
		<date value="2004-09"/>
		<abstract>
			<richtext>
				<p>This document proposes an extension to Soliciting Simple Mail Transfer Protocol (SMTP) for an electronic mail equivalent to the real-world "No Soliciting" sign. In addition to the service extension, a new message header and extensions to the existing "received" message header are described.</p>
			</richtext>
		</abstract>
		<howpublished>Internet RFC 3865</howpublished>
		<title type="sharef:primaryTitle">A No Soliciting Simple Mail Transfer Protocol (SMTP) Service Extension</title>
		<field type="bibtex:topic">smtp[0.8]</field>
	</reference>
	<reference name="rfc3866" src="bibtex:misc" src-info="bibtex:line-44534" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Kurt D.</givenname>
				<surname>Zeilenga</surname>
			</person>
		</names>
		<date value="2004-07"/>
		<abstract>
			<richtext>
				<p>It is often desirable to be able to indicate the natural language associated with values held in a directory and to be able to query the directory for values which fulfill the user's language needs. This document details the use of Language Tags and Ranges in the Lightweight Directory Access Protocol (LDAP).</p>
			</richtext>
		</abstract>
		<howpublished>Internet RFC 3866</howpublished>
		<title type="sharef:primaryTitle">Language Tags and Ranges in the Lightweight Directory Access Protocol (LDAP)</title>
		<field type="bibtex:topic">ldap[0.8] i18n[0.8] l10n[0.8]</field>
	</reference>
	<reference name="rfc3870" src="bibtex:misc" src-info="bibtex:line-44544" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Aaron</givenname>
				<surname>Swartz</surname>
			</person>
		</names>
		<date value="2004-09"/>
		<abstract>
			<richtext>
				<p>This document describes a media type (application/rdf+xml) for use with the Extensible Markup Language (XML) serialization of the Resource Description Framework (RDF). RDF is a language designed to support the Semantic Web, by facilitating resource description and data exchange on the Web. RDF provides common structures that can be used for interoperable data exchange and follows the World Wide Web Consortium (W3C) design principles of interoperability, evolution, and decentralization.</p>
			</richtext>
		</abstract>
		<howpublished>Internet RFC 3870</howpublished>
		<title type="sharef:primaryTitle">application/rdf+xml Media Type Registration</title>
		<field type="bibtex:topic">rdf[0.8]</field>
	</reference>
	<reference name="rfc3874" src="bibtex:misc" src-info="bibtex:line-44554" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Russell</givenname>
				<surname>Housley</surname>
			</person>
		</names>
		<date value="2004-09"/>
		<abstract>
			<richtext>
				<p>This document specifies a 224-bit one-way hash function, called SHA-224. SHA-224 is based on SHA-256, but it uses a different initial value and the result is truncated to 224 bits.</p>
			</richtext>
		</abstract>
		<howpublished>Internet RFC 3874</howpublished>
		<title type="sharef:primaryTitle">A 224-bit One-way Hash Function: SHA-224</title>
		<field type="bibtex:topic">sha224[1]</field>
	</reference>
	<reference name="rfc3891" src="bibtex:misc" src-info="bibtex:line-44564" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Rohan</givenname>
				<surname>Mahy</surname>
			</person>
			<person>
				<givenname>Billy</givenname>
				<surname>Biggs</surname>
			</person>
			<person>
				<givenname>Rick</givenname>
				<surname>Dean</surname>
			</person>
		</names>
		<date value="2004-09"/>
		<abstract>
			<richtext>
				<p>This document defines a new header for use with Session Initiation Protocol (SIP) multi-party applications and call control. The Replaces header is used to logically replace an existing SIP dialog with a new SIP dialog. This primitive can be used to enable a variety of features, for example: "Attended Transfer" and "Call Pickup". Note that the definition of these example features is non-normative.</p>
			</richtext>
		</abstract>
		<howpublished>Internet RFC 3891</howpublished>
		<title type="sharef:primaryTitle">The Session Initiation Protocol (SIP) "Replaces" Header</title>
		<field type="bibtex:topic">sip[0.9]</field>
	</reference>
	<reference name="rfc3892" src="bibtex:misc" src-info="bibtex:line-44574" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Robert J.</givenname>
				<surname>Sparks</surname>
			</person>
		</names>
		<date value="2004-09"/>
		<abstract>
			<richtext>
				<p>The Session Initiation Protocol (SIP) REFER method provides a mechanism where one party (the referrer) gives a second party (the referee) an arbitrary URI to reference. If that URI is a SIP URI, the referee will send a SIP request, often an INVITE, to that URI (the refer target). This document extends the REFER method, allowing the referrer to provide information about the REFER request to the refer target using the referee as an intermediary. This information includes the identity of the referrer and the URI to which the referrer referred. The mechanism utilizes S/MIME to help protect this information from a malicious intermediary. This protection is optional, but a recipient may refuse to accept a request unless it is present.</p>
			</richtext>
		</abstract>
		<howpublished>Internet RFC 3892</howpublished>
		<title type="sharef:primaryTitle">The Session Initiation Protocol (SIP) Referred-By Mechanism</title>
		<field type="bibtex:topic">sip[0.9]</field>
	</reference>
	<reference name="rfc3893" src="bibtex:misc" src-info="bibtex:line-44584" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Jon</givenname>
				<surname>Peterson</surname>
			</person>
		</names>
		<date value="2004-09"/>
		<abstract>
			<richtext>
				<p>RFC 3261 introduces the concept of adding an S/MIME body to a Session Initiation Protocol (SIP) request or response in order to provide reference integrity over its headers. This document provides a more specific mechanism to derive integrity and authentication properties from an 'authenticated identity body', a digitally-signed SIP message, or message fragment. A standard format for such bodies (known as Authenticated Identity Bodies, or AIBs) is given in this document. Some considerations for the processing of AIBs by recipients of SIP messages with such bodies are also given.</p>
			</richtext>
		</abstract>
		<howpublished>Internet RFC 3893</howpublished>
		<title type="sharef:primaryTitle">Session Initiation Protocol (SIP) Authenticated Identity Body (AIB) Format</title>
		<field type="bibtex:topic">sip[0.9]</field>
	</reference>
	<reference name="rfc3902" src="bibtex:misc" src-info="bibtex:line-44594" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Mark A.</givenname>
				<surname>Baker</surname>
			</person>
			<person>
				<givenname>Mark</givenname>
				<surname>Nottingham</surname>
			</person>
		</names>
		<date value="2004-09"/>
		<abstract>
			<richtext>
				<p>This document defines the "application/soap+xml" media type which can be used to describe SOAP 1.2 messages serialized as XML 1.0.</p>
			</richtext>
		</abstract>
		<howpublished>Internet RFC 3902</howpublished>
		<title type="sharef:primaryTitle">The "application/soap+xml" media type</title>
		<field type="bibtex:topic">soap[0.8]</field>
	</reference>
	<reference name="rfc3912" src="bibtex:misc" src-info="bibtex:line-44604" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Leslie L.</givenname>
				<surname>Daigle</surname>
			</person>
		</names>
		<date value="2004-09"/>
		<abstract>
			<richtext>
				<p>This document updates the specification of the WHOIS protocol, thereby obsoleting RFC 954. The update is intended to remove the material from RFC 954 that does not have to do with the on-the-wire protocol, and is no longer applicable in today's Internet. This document does not attempt to change or update the protocol per se, or document other uses of the protocol that have come into existence since the publication of RFC 954.</p>
			</richtext>
		</abstract>
		<howpublished>Internet RFC 3912</howpublished>
		<title type="sharef:primaryTitle">WHOIS Protocol Specification</title>
		<field type="bibtex:topic">whois[1]</field>
	</reference>
	<reference name="rfc3920" src="bibtex:misc" src-info="bibtex:line-44614" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Peter</givenname>
				<surname>Saint-Andre</surname>
			</person>
		</names>
		<date value="2004-10"/>
		<abstract>
			<richtext>
				<p>This memo defines the core features of the Extensible Messaging and Presence Protocol (XMPP), a protocol for streaming Extensible Markup Language (XML) elements in order to exchange structured information in close to real time between any two network endpoints. While XMPP provides a generalized, extensible framework for exchanging XML data, it is used mainly for the purpose of building instant messaging and presence applications that meet the requirements of RFC 2779.</p>
			</richtext>
		</abstract>
		<howpublished>Internet RFC 3920</howpublished>
		<title type="sharef:primaryTitle">Extensible Messaging and Presence Protocol (XMPP): Core</title>
		<field type="bibtex:topic">xmpp[1]</field>
	</reference>
	<reference name="rfc3921" src="bibtex:misc" src-info="bibtex:line-44624" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Peter</givenname>
				<surname>Saint-Andre</surname>
			</person>
		</names>
		<date value="2004-10"/>
		<abstract>
			<richtext>
				<p>This memo describes extensions to and applications of the core features of the Extensible Messaging and Presence Protocol (XMPP) that provide the basic instant messaging (IM) and presence functionality defined in RFC 2779.</p>
			</richtext>
		</abstract>
		<howpublished>Internet RFC 3921</howpublished>
		<title type="sharef:primaryTitle">Extensible Messaging and Presence Protocol (XMPP): Instant Messaging and Presence</title>
		<field type="bibtex:topic">xmpp[1]</field>
	</reference>
	<reference name="rfc3922" src="bibtex:misc" src-info="bibtex:line-44634" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Peter</givenname>
				<surname>Saint-Andre</surname>
			</person>
		</names>
		<date value="2004-10"/>
		<abstract>
			<richtext>
				<p>This memo describes a mapping between the Extensible Messaging and Presence Protocol (XMPP) and the Common Presence and Instant Messaging (CPIM) specifications.</p>
			</richtext>
		</abstract>
		<howpublished>Internet RFC 3922</howpublished>
		<title type="sharef:primaryTitle">Mapping the Extensible Messaging and Presence Protocol (XMPP) to Common Presence and Instant Messaging (CPIM)</title>
		<field type="bibtex:topic">xmpp[0.9] cpim[0.8]</field>
	</reference>
	<reference name="rfc3923" src="bibtex:misc" src-info="bibtex:line-44644" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Peter</givenname>
				<surname>Saint-Andre</surname>
			</person>
		</names>
		<date value="2004-10"/>
		<abstract>
			<richtext>
				<p>This memo defines methods of end-to-end signing and object encryption for the Extensible Messaging and Presence Protocol (XMPP).</p>
			</richtext>
		</abstract>
		<howpublished>Internet RFC 3923</howpublished>
		<title type="sharef:primaryTitle">End-to-End Signing and Object Encryption for the Extensible Messaging and Presence Protocol (XMPP)</title>
		<field type="bibtex:topic">xmpp[0.9] smime[0.8]</field>
	</reference>
	<reference name="rfc3926" src="bibtex:misc" src-info="bibtex:line-44654" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Toni</givenname>
				<surname>Paila</surname>
			</person>
			<person>
				<givenname>Michael</givenname>
				<surname>Luby</surname>
			</person>
			<person>
				<givenname>Rami</givenname>
				<surname>Lehtonen</surname>
			</person>
			<person>
				<givenname>Vincent</givenname>
				<surname>Roca</surname>
			</person>
			<person>
				<givenname>Rod</givenname>
				<surname>Walsh</surname>
			</person>
		</names>
		<date value="2004-10"/>
		<abstract>
			<richtext>
				<p>This document defines FLUTE, a protocol for the unidirectional delivery of files over the Internet, which is particularly suited to multicast networks. The specification builds on Asynchronous Layered Coding, the base protocol designed for massively scalable multicast distribution.</p>
			</richtext>
		</abstract>
		<howpublished>Internet RFC 3926</howpublished>
		<title type="sharef:primaryTitle">FLUTE — File Delivery over Unidirectional Transport</title>
		<field type="bibtex:topic">xmpp[0.9] smime[0.7]</field>
	</reference>
	<reference name="rfc3928" src="bibtex:misc" src-info="bibtex:line-44664" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Richard</givenname>
				<surname>Megginson</surname>
			</person>
			<person>
				<givenname>Olga</givenname>
				<surname>Natkovich</surname>
			</person>
			<person>
				<givenname>Mark</givenname>
				<surname>Smith</surname>
			</person>
			<person>
				<givenname>Jeff</givenname>
				<surname>Parham</surname>
			</person>
		</names>
		<date value="2004-10"/>
		<abstract>
			<richtext>
				<p>This document defines the Lightweight Directory Access Protocol (LDAP) Client Update Protocol (LCUP). The protocol is intended to allow an LDAP client to synchronize with the content of a directory information tree (DIT) stored by an LDAP server and to be notified about the changes to that content.</p>
			</richtext>
		</abstract>
		<howpublished>Internet RFC 3928</howpublished>
		<title type="sharef:primaryTitle">Lightweight Directory Access Protocol (LDAP) Client Update Protocol (LCUP)</title>
		<field type="bibtex:topic">ldap[0.9] lcup[1]</field>
	</reference>
	<reference name="rfc3930" src="bibtex:misc" src-info="bibtex:line-44674" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Donald E.</givenname>
				<surname>Eastlake</surname>
			</person>
		</names>
		<date value="2004-10"/>
		<abstract>
			<richtext>
				<p>This document contrasts two points of view: the "document" point of view, where digital objects of interest are like pieces of paper written and viewed by people, and the "protocol" point of view where objects of interest are composite dynamic network messages. Although each point of view has a place, adherence to a document point of view can be damaging to protocol design. By understanding both points of view, conflicts between them may be clarified and reduced.</p>
			</richtext>
		</abstract>
		<howpublished>Internet RFC 3930</howpublished>
		<title type="sharef:primaryTitle">The Protocol versus Document Points of View in Computer Protocols</title>
	</reference>
	<reference name="rfc3937" src="bibtex:misc" src-info="bibtex:line-44683" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Michael</givenname>
				<surname>Steidl</surname>
			</person>
		</names>
		<date value="2004-10"/>
		<abstract>
			<richtext>
				<p>This document describes a URN (Uniform Resource Name) namespace for identifying persistent resources published by the International Press Telecommunications Council (IPTC). These resources include XML Data Type Definition files (DTD), XML Schema, Namespaces in XML, XSL stylesheets, other XML based document and documents of other data formats like PDF documents, Microsoft Office documents and others.</p>
			</richtext>
		</abstract>
		<howpublished>Internet RFC 3937</howpublished>
		<title type="sharef:primaryTitle">A Uniform Resource Name (URN) Namespace for the International Press Telecommunications Council (IPTC)</title>
		<field type="bibtex:topic">urn[0.7] iptc[0.8]</field>
	</reference>
	<reference name="rfc3943" src="bibtex:misc" src-info="bibtex:line-44693" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Robert</givenname>
				<surname>Friend</surname>
			</person>
		</names>
		<date value="2004-11"/>
		<abstract>
			<richtext>
				<p>The Transport Layer Security (TLS) protocol (RFC 2246) includes features to negotiate selection of a lossless data compression method as part of the TLS Handshake Protocol and then to apply the algorithm associated with the selected method as part of the TLS Record Protocol. TLS defines one standard compression method, which specifies that data exchanged via the record protocol will not be compressed. This document describes an additional compression method associated with the Lempel-Ziv-Stac (LZS) lossless data compression algorithm for use with TLS. This document also defines the application of the LZS algorithm to the TLS Record Protocol.</p>
			</richtext>
		</abstract>
		<howpublished>Internet RFC 3943</howpublished>
		<title type="sharef:primaryTitle">Transport Layer Security (TLS) Protocol Compression Using Lempel-Ziv-Stac (LZS)</title>
		<field type="bibtex:topic">lzs[0.7] tls[0.8]</field>
	</reference>
	<reference name="rfc3944" src="bibtex:misc" src-info="bibtex:line-44703" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Tyler</givenname>
				<surname>Johnson</surname>
			</person>
			<person>
				<givenname>Sakae</givenname>
				<surname>Okubo</surname>
			</person>
			<person>
				<givenname>Simao Ferraz</givenname>
				<surname link="de">Campos Neto</surname>
			</person>
		</names>
		<date value="2004-12"/>
		<abstract>
			<richtext>
				<p>The International Telecommunications Union Standardization Sector (ITU-T) has created the H.350 series of Recommendations that specify directory services architectures in support of multimedia conferencing protocols. The goal of the architecture is to 'directory enable' multimedia conferencing so that these services can leverage existing identity management and enterprise directories. A particular goal is to enable an enterprise or service provider to maintain a canonical source of users and their multimedia conferencing systems, so that multiple call servers from multiple vendors, supporting multiple protocols, can all access the same data store. Because SIP is an IETF standard, the contents of H.350 and H.350.4 are made available via this document to the IETF community. This document contains the entire normative text of ITU-T Recommendations H.350 and H.350.4 in sections 4 and 5, respectively. The remaining sections are included only in this document, not in the ITU-T version.</p>
			</richtext>
		</abstract>
		<howpublished>Internet RFC 3944</howpublished>
		<title type="sharef:primaryTitle">H.350 Directory Services</title>
		<field type="bibtex:topic">h350[0.9]</field>
	</reference>
	<reference name="rfc3963" src="bibtex:misc" src-info="bibtex:line-44713" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Vijay</givenname>
				<surname>Devarapalli</surname>
			</person>
			<person>
				<givenname>Ryuji</givenname>
				<surname>Wakikawa</surname>
			</person>
			<person>
				<givenname>Alexandru</givenname>
				<surname>Petrescu</surname>
			</person>
			<person>
				<givenname>Pascal</givenname>
				<surname>Thubert</surname>
			</person>
		</names>
		<date value="2005-01"/>
		<abstract>
			<richtext>
				<p>This document describes the Network Mobility (NEMO) Basic Support protocol that enables Mobile Networks to attach to different points in the Internet. The protocol is an extension of Mobile IPv6 and allows session continuity for every node in the Mobile Network as the network moves. It also allows every node in the Mobile Network to be reachable while moving around. The Mobile Router, which connects the network to the Internet, runs the NEMO Basic Support protocol with its Home Agent. The protocol is designed so that network mobility is transparent to the nodes inside the Mobile Network.</p>
			</richtext>
		</abstract>
		<howpublished>Internet RFC 3963</howpublished>
		<title type="sharef:primaryTitle">Network Mobility (NEMO) Basic Support Protocol</title>
		<field type="bibtex:topic">nemo[1]</field>
	</reference>
	<reference name="rfc3966" src="bibtex:misc" src-info="bibtex:line-44723" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Henning</givenname>
				<surname>Schulzrinne</surname>
			</person>
		</names>
		<date value="2004-12"/>
		<abstract>
			<richtext>
				<p>This document specifies the URI (Uniform Resource Identifier) scheme "tel". The "tel" URI describes resources identified by telephone numbers. This document obsoletes RFC 2806.</p>
			</richtext>
		</abstract>
		<howpublished>Internet RFC 3966</howpublished>
		<title type="sharef:primaryTitle">The tel URI for Telephone Numbers</title>
		<field type="bibtex:topic">uri[0.7] pstn[0.8]</field>
		<field type="bibtex:updates">rfc2806</field>
	</reference>
	<reference name="rfc3978" src="bibtex:misc" src-info="bibtex:line-44734" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Scott O.</givenname>
				<surname>Bradner</surname>
			</person>
		</names>
		<date value="2005-03"/>
		<abstract>
			<richtext>
				<p>The IETF policies about rights in Contributions to the IETF are designed to ensure that such Contributions can be made available to the IETF and Internet communities while permitting the authors to retain as many rights as possible. This memo details the IETF policies on rights in Contributions to the IETF. It also describes the objectives that the policies are designed to meet. This memo updates RFC 2026, and, with RFC 3979, replaces Section 10 of RFC 2026.</p>
			</richtext>
		</abstract>
		<howpublished>Internet RFC 3978</howpublished>
		<title type="sharef:primaryTitle">IETF Rights in Contributions</title>
		<field type="bibtex:topic">ietf[0.9]</field>
		<field type="bibtex:updates">rfc3667</field>
	</reference>
	<reference name="rfc3979" src="bibtex:misc" src-info="bibtex:line-44745" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Scott O.</givenname>
				<surname>Bradner</surname>
			</person>
		</names>
		<date value="2005-03"/>
		<abstract>
			<richtext>
				<p>The IETF policies about Intellectual Property Rights (IPR), such as patent rights, relative to technologies developed in the IETF are designed to ensure that IETF working groups and participants have as much information about any IPR constraints on a technical proposal as possible. The policies are also intended to benefit the Internet community and the public at large, while respecting the legitimate rights of IPR holders. This memo details the IETF policies concerning IPR related to technology worked on within the IETF. It also describes the objectives that the policies are designed to meet. This memo updates RFC 2026 and, with RFC 3978, replaces Section 10 of RFC 2026. This memo also updates paragraph 4 of Section 3.2 of RFC 2028, for all purposes, including reference [2] in RFC 2418.</p>
			</richtext>
		</abstract>
		<howpublished>Internet RFC 3979</howpublished>
		<title type="sharef:primaryTitle">Intellectual Property Rights in IETF Technology</title>
		<field type="bibtex:topic">ietf[0.9]</field>
		<field type="bibtex:updates">rfc3668</field>
	</reference>
	<reference name="rfc3986" src="bibtex:misc" src-info="bibtex:line-44756" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Tim</givenname>
				<surname>Berners-Lee</surname>
			</person>
			<person>
				<givenname>Roy Thomas</givenname>
				<surname>Fielding</surname>
			</person>
			<person>
				<givenname>Larry</givenname>
				<surname>Masinter</surname>
			</person>
		</names>
		<date value="2005-01"/>
		<abstract>
			<richtext>
				<p>A Uniform Resource Identifier (URI) is a compact sequence of characters that identifies an abstract or physical resource. This specification defines the generic URI syntax and a process for resolving URI references that might be in relative form, along with guidelines and security considerations for the use of URIs on the Internet. The URI syntax defines a grammar that is a superset of all valid URIs, allowing an implementation to parse the common components of a URI reference without knowing the scheme-specific requirements of every possible identifier. This specification does not define a generative grammar for URIs; that task is performed by the individual specifications of each URI scheme.</p>
			</richtext>
		</abstract>
		<howpublished>Internet RFC 3986</howpublished>
		<title type="sharef:primaryTitle">Uniform Resource Identifier (URI): Generic Syntax</title>
		<field type="bibtex:topic">uri[1]</field>
		<field type="bibtex:updates">rfc2396bis</field>
	</reference>
	<reference name="rfc3987" src="bibtex:misc" src-info="bibtex:line-44767" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Martin J.</givenname>
				<surname>Dürst</surname>
			</person>
			<person>
				<givenname>Michel</givenname>
				<surname>Suignard</surname>
			</person>
		</names>
		<date value="2005-01"/>
		<abstract>
			<richtext>
				<p>This document defines a new protocol element, the Internationalized Resource Identifier (IRI), as a complement to the Uniform Resource Identifier (URI). An IRI is a sequence of characters from the Universal Character Set (Unicode/ISO 10646). A mapping from IRIs to URIs is defined, which means that IRIs can be used instead of URIs, where appropriate, to identify resources. The approach of defining a new protocol element was chosen instead of extending or changing the definition of URIs. This was done in order to allow a clear distinction and to avoid incompatibilities with existing software. Guidelines are provided for the use and deployment of IRIs in various protocols, formats, and software components that currently deal with URIs.</p>
			</richtext>
		</abstract>
		<howpublished>Internet RFC 3987</howpublished>
		<title type="sharef:primaryTitle">Internationalized Resource Identifiers (IRIs)</title>
		<field type="bibtex:topic">iri[1]</field>
		<field type="bibtex:updates">due03</field>
	</reference>
	<reference name="rfc4002" src="bibtex:misc" src-info="bibtex:line-44778" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Rudolf</givenname>
				<surname>Brandner</surname>
			</person>
			<person>
				<givenname>Lawrence</givenname>
				<surname>Conroy</surname>
			</person>
			<person>
				<givenname>Richard</givenname>
				<surname>Stastny</surname>
			</person>
		</names>
		<date value="2005-02"/>
		<abstract>
			<richtext>
				<p>This document registers the Enumservices 'web' and 'ft' by using the URI schemes 'http:', 'https:' and 'ftp:' as per the IANA registration process defined in the ENUM specification (RFC 3761).</p>
			</richtext>
		</abstract>
		<howpublished>Internet RFC 4002</howpublished>
		<title type="sharef:primaryTitle">IANA Registration for Enumservice 'web' and 'ft'</title>
		<field type="bibtex:topic">enum[0.9]</field>
	</reference>
	<reference name="rfc4021" src="bibtex:misc" src-info="bibtex:line-44788" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Graham</givenname>
				<surname>Klyne</surname>
			</person>
			<person>
				<givenname>Jacob</givenname>
				<surname>Palme</surname>
			</person>
		</names>
		<date value="2005-03"/>
		<abstract>
			<richtext>
				<p>This document defines the initial IANA registration for permanent mail and MIME message header fields, per RFC 3864.</p>
			</richtext>
		</abstract>
		<howpublished>Internet RFC 4021</howpublished>
		<title type="sharef:primaryTitle">Registration of Mail and MIME Header Fields</title>
		<field type="bibtex:topic">mime[0.8]</field>
	</reference>
	<reference name="rfc4050" src="bibtex:misc" src-info="bibtex:line-44798" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Simon</givenname>
				<surname>Blake-Wilson</surname>
			</person>
			<person>
				<givenname>Gregor</givenname>
				<surname>Karlinger</surname>
			</person>
			<person>
				<givenname>Tetsutaro</givenname>
				<surname>Kobayashi</surname>
			</person>
			<person>
				<givenname>Yongge</givenname>
				<surname>Wang</surname>
			</person>
		</names>
		<date value="2005-04"/>
		<abstract>
			<richtext>
				<p>This document specifies how to use Elliptic Curve Digital Signature Algorithm (ECDSA) with XML Signatures. The mechanism specified provides integrity, message authentication, and/or signer authentication services for data of any type, whether located within the XML that includes the signature or included by reference.</p>
			</richtext>
		</abstract>
		<howpublished>Internet RFC 4050</howpublished>
		<title type="sharef:primaryTitle">Using the Elliptic Curve Signature Algorithm (ECDSA) for XML Digital Signatures</title>
		<field type="bibtex:topic">ecdsa[0.8]</field>
	</reference>
	<reference name="rfc4051" src="bibtex:misc" src-info="bibtex:line-44808" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Donald E.</givenname>
				<surname>Eastlake</surname>
			</person>
		</names>
		<date value="2005-04"/>
		<abstract>
			<richtext>
				<p>A number of Uniform Resource Identifiers (URIs) intended for use with XML Digital Signatures, Encryption, and Canonicalization are defined. These URIs identify algorithms and types of keying information.</p>
			</richtext>
		</abstract>
		<howpublished>Internet RFC 4051</howpublished>
		<title type="sharef:primaryTitle">Additional XML Security Uniform Resource Identifiers (URIs)</title>
		<field type="bibtex:topic">uri[0.7]</field>
	</reference>
	<reference name="rfc4088" src="bibtex:misc" src-info="bibtex:line-44818" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>David L.</givenname>
				<surname>Black</surname>
			</person>
			<person>
				<givenname>Keith</givenname>
				<surname>McCloghrie</surname>
			</person>
			<person>
				<givenname>Juergen</givenname>
				<surname>Schoenwaelder</surname>
			</person>
		</names>
		<date value="2005-06"/>
		<abstract>
			<richtext>
				<p>The Simple Network Management Protocol (SNMP) and the Internet Standard Management Framework are widely used for the management of communication devices, creating a need to specify SNMP access (including access to SNMP MIB object instances) from non-SNMP management environments. For example, when out-of-band IP management is used via a separate management interface (e.g., for a device that does not support in-band IP access), a uniform way to indicate how to contact the device for management is needed. Uniform Resource Identifiers (URIs) fit this need well, as they allow a single text string to indicate a management access communication endpoint for a wide variety of IP-based protocols. This document defines a URI scheme so that SNMP can be designated as the protocol used for management. The scheme also allows a URI to designate one or more MIB object instances.</p>
			</richtext>
		</abstract>
		<howpublished>Internet RFC 4088</howpublished>
		<title type="sharef:primaryTitle">Uniform Resource Identifier (URI) Scheme for the Simple Network Management Protocol (SNMP)</title>
		<field type="bibtex:topic">snmp[0.8] uri[0.7]</field>
	</reference>
	<reference name="rfc4102" src="bibtex:misc" src-info="bibtex:line-44828" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Paul E.</givenname>
				<surname>Jones</surname>
			</person>
		</names>
		<date value="2005-06"/>
		<abstract>
			<richtext>
				<p>This document defines the text/red MIME sub-type. "Red" is short for redundant. The actual RTP packetization for this MIME type is specified in RFC 2198.</p>
			</richtext>
		</abstract>
		<howpublished>Internet RFC 4102</howpublished>
		<title type="sharef:primaryTitle">Registration of the text/red MIME Sub-Type</title>
		<field type="bibtex:topic">mime[0.7]</field>
	</reference>
	<reference name="rfc4112" src="bibtex:misc" src-info="bibtex:line-44838" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Donald E.</givenname>
				<surname>Eastlake</surname>
			</person>
		</names>
		<date value="2005-06"/>
		<abstract>
			<richtext>
				<p>Electronic commerce frequently requires a substantial exchange of information in order to complete a purchase or other transaction, especially the first time the parties communicate. A standard set of hierarchically-organized payment-related information field names in an XML syntax is defined so that this task can be more easily automated. This is the second version of an Electronic Commerce Modeling Language (ECML) and is intended to meet the requirements of RFC 3505.</p>
			</richtext>
		</abstract>
		<howpublished>Internet RFC 4112</howpublished>
		<title type="sharef:primaryTitle">Electronic Commerce Modeling Language (ECML) Version 2 Specification</title>
		<field type="bibtex:topic">ecml[1]</field>
		<field type="bibtex:updates">rfc3106 rfc3505</field>
	</reference>
	<reference name="rfc4119" src="bibtex:misc" src-info="bibtex:line-44849" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Jon</givenname>
				<surname>Peterson</surname>
			</person>
		</names>
		<date value="2005-12"/>
		<abstract>
			<richtext>
				<p>This document describes an object format for carrying geographical information on the Internet. This location object extends the Presence Information Data Format (PIDF), which was designed for communicating privacy-sensitive presence information and which has similar properties.</p>
			</richtext>
		</abstract>
		<howpublished>Internet RFC 4119</howpublished>
		<title type="sharef:primaryTitle">A Presence-based GEOPRIV Location Object Format</title>
		<field type="bibtex:topic">pidflo[1] pidf[0.9]</field>
	</reference>
	<reference name="rfc4122" src="bibtex:misc" src-info="bibtex:line-44859" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Paul J.</givenname>
				<surname>Leach</surname>
			</person>
			<person>
				<givenname>Michael</givenname>
				<surname>Mealling</surname>
			</person>
			<person>
				<givenname>Richard</givenname>
				<surname>Salz</surname>
			</person>
		</names>
		<date value="2005-07"/>
		<abstract>
			<richtext>
				<p>This specification defines a Uniform Resource Name namespace for UUIDs (Universally Unique IDentifier), also known as GUIDs (Globally Unique IDentifier). A UUID is 128 bits long, and can guarantee uniqueness across space and time. UUIDs were originally used in the Apollo Network Computing System and later in the Open Software Foundation's (OSF) Distributed Computing Environment (DCE), and then in Microsoft Windows platforms. This specification is derived from the DCE specification with the kind permission of the OSF (now known as The Open Group). Information from earlier versions of the DCE specification have been incorporated into this document.</p>
			</richtext>
		</abstract>
		<howpublished>Internet RFC 4122</howpublished>
		<title type="sharef:primaryTitle">A Universally Unique IDentifier (UUID) URN Namespace</title>
		<field type="bibtex:topic">urn[0.7] uuid[0.8]</field>
	</reference>
	<reference name="rfc4151" src="bibtex:misc" src-info="bibtex:line-44869" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Tim</givenname>
				<surname>Kindberg</surname>
			</person>
			<person>
				<givenname>Sandro</givenname>
				<surname>Hawke</surname>
			</person>
		</names>
		<date value="2005-10"/>
		<abstract>
			<richtext>
				<p>This document describes the "tag" Uniform Resource Identifier (URI) scheme. Tag URIs (also known as "tags") are designed to be unique across space and time while being tractable to humans. They are distinct from most other URIs in that they have no authoritative resolution mechanism. A tag may be used purely as an entity identifier. Furthermore, using tags has some advantages over the common practice of using "http" URIs as identifiers for non-HTTP-accessible resources.</p>
			</richtext>
		</abstract>
		<howpublished>Internet RFC 4151</howpublished>
		<title type="sharef:primaryTitle">The 'tag' URI Scheme</title>
		<field type="bibtex:topic">uri[0.7]</field>
	</reference>
	<reference name="rfc4152" src="bibtex:misc" src-info="bibtex:line-44879" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Kaj</givenname>
				<surname>Tesink</surname>
			</person>
			<person>
				<givenname>Robert H.</givenname>
				<surname>Fox</surname>
			</person>
		</names>
		<date value="2005-08"/>
		<abstract>
			<richtext>
				<p>This document describes a Uniform Resource Name (URN) namespace (RFC 3406) for the assignment of the Common Language Equipment Identifier (CLEI) code, which is used in messages standardized by ANSI. The URN namespace is managed by Telcordia Technologies, Inc., as the maintenance agent for ANSI T1.213. The CLEI code is a globally unique, ten-character alphanumeric intelligent code assigned by Telcordia Technologies at the request of equipment suppliers. The CLEI code identifies communications equipment by specifying product type and features. There is a one-to-one relationship between a CLEI code and supplier's product ID (the manufacturer's name and the part number along with its version number).</p>
			</richtext>
		</abstract>
		<howpublished>Internet RFC 4152</howpublished>
		<title type="sharef:primaryTitle">A Uniform Resource Name (URN) Namespace for the Common Language Equipment Identifier (CLEI) Code</title>
		<field type="bibtex:topic">urn[0.7] clei[0.8]</field>
	</reference>
	<reference name="rfc4156" src="bibtex:misc" src-info="bibtex:line-44889" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Paul E.</givenname>
				<surname>Hoffman</surname>
			</person>
		</names>
		<date value="2005-08"/>
		<abstract>
			<richtext>
				<p>This document specifies the wais Uniform Resource Identifier (URI) scheme that was originally specified in RFC 1738. The purpose of this document is to allow RFC 1738 to be made obsolete while keeping the information about the scheme on standards track.</p>
			</richtext>
		</abstract>
		<howpublished>Internet RFC 4156</howpublished>
		<title type="sharef:primaryTitle">The wais URI Scheme</title>
		<field type="bibtex:topic">wais[0.8] uri[0.7]</field>
		<field type="bibtex:updates">rfc1738</field>
	</reference>
	<reference name="rfc4157" src="bibtex:misc" src-info="bibtex:line-44900" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Paul E.</givenname>
				<surname>Hoffman</surname>
			</person>
		</names>
		<date value="2005-08"/>
		<abstract>
			<richtext>
				<p>This document specifies the prospero Uniform Resource Identifier (URI) scheme that was originally specified in RFC 1738. The purpose of this document is to allow RFC 1738 to be made obsolete while keeping the information about the scheme on standards track.</p>
			</richtext>
		</abstract>
		<howpublished>Internet RFC 4157</howpublished>
		<title type="sharef:primaryTitle">The prospero URI Scheme</title>
		<field type="bibtex:topic">prospero[0.8] uri[0.7]</field>
		<field type="bibtex:updates">rfc1738</field>
	</reference>
	<reference name="rfc4169" src="bibtex:misc" src-info="bibtex:line-44911" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Vesa</givenname>
				<surname>Torvinen</surname>
			</person>
			<person>
				<givenname>Jari</givenname>
				<surname>Arkko</surname>
			</person>
			<person>
				<givenname>Mats</givenname>
				<surname>Naeslund</surname>
			</person>
		</names>
		<date value="2005-11"/>
		<abstract>
			<richtext>
				<p>HTTP Digest, as specified in RFC 2617, is known to be vulnerable to man-in-the-middle attacks if the client fails to authenticate the server in TLS, or if the same passwords are used for authentication in some other context without TLS. This is a general problem that exists not just with HTTP Digest, but also with other IETF protocols that use tunneled authentication. This document specifies version 2 of the HTTP Digest AKA algorithm (RFC 3310). This algorithm can be implemented in a way that it is resistant to the man-in-the-middle attack. This memo provides information for the Internet community.</p>
			</richtext>
		</abstract>
		<howpublished>Internet RFC 4169</howpublished>
		<title type="sharef:primaryTitle">Hypertext Transfer Protocol (HTTP) Digest Authentication Using Authentication and Key Agreement (AKA) Version-2</title>
		<field type="bibtex:topic">aka[1] daauth[0.8]</field>
		<field type="bibtex:updates">rfc3310</field>
	</reference>
	<reference name="rfc4179" src="bibtex:misc" src-info="bibtex:line-44922" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Sang</givenname>
				<surname link="ug">Kang</surname>
			</person>
		</names>
		<date value="2005-10"/>
		<abstract>
			<richtext>
				<p>This document describes a Uniform Resource Name (URN) namespace for the National Computerization Agency (NCA) for naming persistent digital resources such as music, videos, texts, images, e-books, and other types of digital resources produced or managed by NCA.</p>
			</richtext>
		</abstract>
		<howpublished>Internet RFC 4179</howpublished>
		<title type="sharef:primaryTitle">Using Universal Content Identifier (UCI) as Uniform Resource Names (URN)</title>
		<field type="bibtex:topic">uri[0.7] uci[0.8]</field>
	</reference>
	<reference name="rfc4180" src="bibtex:misc" src-info="bibtex:line-44932" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Yakov</givenname>
				<surname>Shafranovich</surname>
			</person>
		</names>
		<date value="2005-10"/>
		<abstract>
			<richtext>
				<p>This RFC documents the format used for Comma-Separated Values (CSV) files and registers the associated MIME type "text/csv".</p>
			</richtext>
		</abstract>
		<howpublished>Internet RFC 4180</howpublished>
		<title type="sharef:primaryTitle">Common Format and MIME Type for Comma-Separated Values (CSV) Files</title>
		<field type="bibtex:topic">csv[0.9] mime[0.7]</field>
	</reference>
	<reference name="rfc4234" src="bibtex:misc" src-info="bibtex:line-44942" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>David H.</givenname>
				<surname>Crocker</surname>
			</person>
			<person>
				<givenname>Paul</givenname>
				<surname>Overell</surname>
			</person>
		</names>
		<date value="2005-10"/>
		<abstract>
			<richtext>
				<p>Internet technical specifications often need to define a formal syntax. Over the years, a modified version of Backus-Naur Form (BNF), called Augmented BNF (ABNF), has been popular among many Internet specifications. The current specification documents ABNF. It balances compactness and simplicity, with reasonable representational power. The differences between standard BNF and ABNF involve naming rules, repetition, alternatives, order-independence, and value ranges. This specification also supplies additional rule definitions and encoding for a core lexical analyzer of the type common to several Internet specifications.</p>
			</richtext>
		</abstract>
		<howpublished>Internet RFC 4234</howpublished>
		<title type="sharef:primaryTitle">Augmented BNF for Syntax Specifications: ABNF</title>
		<field type="bibtex:topic">abnf[1]</field>
		<field type="bibtex:updates">rfc2234</field>
	</reference>
	<reference name="rfc4248" src="bibtex:misc" src-info="bibtex:line-44953" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Paul E.</givenname>
				<surname>Hoffman</surname>
			</person>
		</names>
		<date value="2005-10"/>
		<abstract>
			<richtext>
				<p>This document specifies the telnet Uniform Resource Identifier (URI) scheme that was originally specified in RFC 1738. The purpose of this document is to allow RFC 1738 to be made obsolete while keeping the information about the scheme on standards track.</p>
			</richtext>
		</abstract>
		<howpublished>Internet RFC 4248</howpublished>
		<title type="sharef:primaryTitle">The telnet URI Scheme</title>
		<field type="bibtex:topic">telnet[0.8] uri[0.7]</field>
		<field type="bibtex:updates">rfc1738</field>
	</reference>
	<reference name="rfc4266" src="bibtex:misc" src-info="bibtex:line-44964" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Paul E.</givenname>
				<surname>Hoffman</surname>
			</person>
		</names>
		<date value="2005-11"/>
		<abstract>
			<richtext>
				<p>This document specifies the gopher Uniform Resource Identifier (URI) scheme that was originally specified in RFC 1738. The purpose of this document is to allow RFC 1738 to be made obsolete while keeping the information about the scheme on standards track.</p>
			</richtext>
		</abstract>
		<howpublished>Internet RFC 4266</howpublished>
		<title type="sharef:primaryTitle">The gopher URI Scheme</title>
		<field type="bibtex:topic">gopher[0.8] uri[0.7]</field>
		<field type="bibtex:updates">rfc1738</field>
	</reference>
	<reference name="rfc4287" src="bibtex:misc" src-info="bibtex:line-44975" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Mark</givenname>
				<surname>Nottingham</surname>
			</person>
			<person>
				<givenname>Robert</givenname>
				<surname>Sayre</surname>
			</person>
		</names>
		<date value="2005-12"/>
		<abstract>
			<richtext>
				<p>This document specifies Atom, an XML-based Web content and metadata syndication format.</p>
			</richtext>
		</abstract>
		<howpublished>Internet RFC 4287</howpublished>
		<title type="sharef:primaryTitle">The Atom Syndication Format</title>
		<field type="bibtex:topic">atom[1]</field>
	</reference>
	<reference name="rfc4288" src="bibtex:misc" src-info="bibtex:line-44985" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Ned</givenname>
				<surname>Freed</surname>
			</person>
			<person>
				<givenname>John C.</givenname>
				<surname>Klensin</surname>
			</person>
		</names>
		<date value="2005-12"/>
		<abstract>
			<richtext>
				<p>This document defines procedures for the specification and registration of media types for use in MIME and other Internet protocols.</p>
			</richtext>
		</abstract>
		<howpublished>Internet RFC 4288</howpublished>
		<title type="sharef:primaryTitle">Media Type Specifications and Registration Procedures</title>
		<field type="bibtex:topic">mime[1]</field>
		<field type="bibtex:updates">rfc2048</field>
	</reference>
	<reference name="rfc4289" src="bibtex:misc" src-info="bibtex:line-44996" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Ned</givenname>
				<surname>Freed</surname>
			</person>
			<person>
				<givenname>John C.</givenname>
				<surname>Klensin</surname>
			</person>
		</names>
		<date value="2005-12"/>
		<abstract>
			<richtext>
				<p>This document specifies IANA registration procedures for MIME external body access types and content-transfer-encodings.</p>
			</richtext>
		</abstract>
		<howpublished>Internet RFC 4289</howpublished>
		<title type="sharef:primaryTitle">Multipurpose Internet Mail Extensions (MIME) Part Four: Registration Procedures</title>
		<field type="bibtex:topic">mime[1]</field>
		<field type="bibtex:updates">rfc2048</field>
	</reference>
	<reference name="rfc4316" src="bibtex:misc" src-info="bibtex:line-45007" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Julian F.</givenname>
				<surname>Reschke</surname>
			</person>
		</names>
		<date value="2005-12"/>
		<abstract>
			<richtext>
				<p>This specification extends the Web Distributed Authoring and Versioning Protocol (WebDAV) to support datatyping. Protocol elements are defined to let clients and servers specify the datatype, and to instruct the WebDAV method PROPFIND to return datatype information.</p>
			</richtext>
		</abstract>
		<howpublished>Internet RFC 4316</howpublished>
		<title type="sharef:primaryTitle">Datatypes for Web Distributed Authoring and Versioning (WebDAV) Properties</title>
		<field type="bibtex:topic">webdav[0.9]</field>
	</reference>
	<reference name="rfc4324" src="bibtex:misc" src-info="bibtex:line-45017" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Doug</givenname>
				<surname>Royer</surname>
			</person>
			<person>
				<givenname>George</givenname>
				<surname>Babics</surname>
			</person>
			<person>
				<givenname>Steven</givenname>
				<surname>Mansour</surname>
			</person>
		</names>
		<date value="2005-12"/>
		<abstract>
			<richtext>
				<p>The Calendar Access Protocol (CAP) described in this memo permits a Calendar User (CU) to utilize a Calendar User Agent (CUA) to access an iCAL-based Calendar Store (CS). At the time of this writing, three vendors are implementing CAP, but it has already been determined that some changes are needed. In order to get implementation experience, the participants felt that a CAP specification is needed to preserve many years of work. Many properties in CAP which have had many years of debate, can be used by other iCalendar protocols.</p>
			</richtext>
		</abstract>
		<howpublished>Internet RFC 4324</howpublished>
		<title type="sharef:primaryTitle">Calendar Access Protocol (CAP)</title>
		<field type="bibtex:topic">cap[1]</field>
	</reference>
	<reference name="rfc4343" src="bibtex:misc" src-info="bibtex:line-45027" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Donald E.</givenname>
				<surname>Eastlake</surname>
			</person>
		</names>
		<date value="2006-01"/>
		<abstract>
			<richtext>
				<p>Domain Name System (DNS) names are "case insensitive". This document explains exactly what that means and provides a clear specification of the rules. This clarification updates RFCs 1034, 1035, and 2181.</p>
			</richtext>
		</abstract>
		<howpublished>Internet RFC 4343</howpublished>
		<title type="sharef:primaryTitle">Domain Name System (DNS) Case Insensitivity Clarification</title>
		<field type="bibtex:topic">dns[0.8]</field>
		<field type="bibtex:updates">rfc1034 rfc1035 rfc2181</field>
	</reference>
	<reference name="rfc4350" src="bibtex:misc" src-info="bibtex:line-45038" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Ferry</givenname>
				<surname>Hendrikx</surname>
			</person>
			<person>
				<givenname>Colin</givenname>
				<surname>Wallis</surname>
			</person>
		</names>
		<date value="2006-02"/>
		<abstract>
			<richtext>
				<p>This document describes a Uniform Resource Name (URN) Namespace Identification (NID) convention as prescribed by the World Wide Web Consortium (W3C) for identifying, naming, assigning, and managing persistent resources and XML artefacts for the New Zealand Government.</p>
			</richtext>
		</abstract>
		<howpublished>Internet RFC 4350</howpublished>
		<title type="sharef:primaryTitle">A Uniform Resource Name (URN) Formal Namespace for the New Zealand Government</title>
	</reference>
	<reference name="rfc4356" src="bibtex:misc" src-info="bibtex:line-45047" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Randall</givenname>
				<surname>Gellens</surname>
			</person>
		</names>
		<date value="2006-01"/>
		<abstract>
			<richtext>
				<p>The cellular telephone industry has defined a service known as the Multimedia Messaging Service (MMS). This service uses formats and protocols that are similar to, but differ in key ways from, those used in Internet mail. One important difference between MMS and Internet Mail is that MMS uses headers that start with "X-Mms-" to carry a variety of user agent- and server-related information elements. This document specifies how to exchange messages between these two services, including mapping information elements as used in MMS X-Mms-* headers as well as delivery and disposition reports, to and from that used in SMTP and Internet message headers.</p>
			</richtext>
		</abstract>
		<howpublished>Internet RFC 4356</howpublished>
		<title type="sharef:primaryTitle">Mapping Between the Multimedia Messaging Service (MMS) and Internet Mail</title>
		<field type="bibtex:topic">mms[0.8]</field>
	</reference>
	<reference name="rfc4358" src="bibtex:misc" src-info="bibtex:line-45057" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Dwight</givenname>
				<surname>Smith</surname>
			</person>
		</names>
		<date value="2006-01"/>
		<abstract>
			<richtext>
				<p>This document describes the Namespace Identifier (NID) for Uniform Resource Namespace (URN) resources published by the Open Mobile Alliance (OMA). OMA defines and manages resources that utilize this URN name model. Management activities for these and other resource types are provided by the Open Mobile Naming Authority (OMNA).</p>
			</richtext>
		</abstract>
		<howpublished>Internet RFC 4358</howpublished>
		<title type="sharef:primaryTitle">A Uniform Resource Name (URN) Namespace for the Open Mobile Alliance (OMA)</title>
		<field type="bibtex:topic">oma[0.8]</field>
	</reference>
	<reference name="rfc4367" src="bibtex:misc" src-info="bibtex:line-45067" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Jonathan</givenname>
				<surname>Rosenberg</surname>
			</person>
		</names>
		<date value="2006-02"/>
		<abstract>
			<richtext>
				<p>The Domain Name System (DNS) provides an essential service on the Internet, mapping structured names to a variety of data, usually IP addresses. These names appear in email addresses, Uniform Resource Identifiers (URIs), and other application-layer identifiers that are often rendered to human users. Because of this, there has been a strong demand to acquire names that have significance to people, through equivalence to registered trademarks, company names, types of services, and so on. There is a danger in this trend; the humans and automata that consume and use such names will associate specific semantics with some names and thereby make assumptions about the services that are, or should be, provided by the hosts associated with the names. Those assumptions can often be false, resulting in a variety of failure conditions. This document discusses this problem in more detail and makes recommendations on how it can be avoided.</p>
			</richtext>
		</abstract>
		<howpublished>Internet RFC 4367</howpublished>
		<title type="sharef:primaryTitle">What's in a Name: False Assumptions about DNS Names</title>
		<field type="bibtex:topic">dns[0.8]</field>
	</reference>
	<reference name="rfc4374" src="bibtex:misc" src-info="bibtex:line-45077" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Gerald</givenname>
				<surname>McCobb</surname>
			</person>
		</names>
		<date value="2006-01"/>
		<abstract>
			<richtext>
				<p>This document describes the registration of the MIME sub-type application/xv+xml. This sub-type is intended for use as a media descriptor for XHTML+Voice multimodal language documents.</p>
			</richtext>
		</abstract>
		<howpublished>Internet RFC 4374</howpublished>
		<title type="sharef:primaryTitle">The application/xv+xml Media Type</title>
		<field type="bibtex:topic">xhtml[0.7] voicexml[0.7]</field>
	</reference>
	<reference name="rfc4395" src="bibtex:misc" src-info="bibtex:line-45087" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Tony</givenname>
				<surname>Hansen</surname>
			</person>
			<person>
				<givenname>Ted</givenname>
				<surname>Hardie</surname>
			</person>
			<person>
				<givenname>Larry</givenname>
				<surname>Masinter</surname>
			</person>
		</names>
		<date value="2006-02"/>
		<abstract>
			<richtext>
				<p>This document provides guidelines and recommendations for the definition of Uniform Resource Identifier (URI) schemes. It also updates the process and IANA registry for URI schemes. It obsoletes both RFC 2717 and RFC 2718.</p>
			</richtext>
		</abstract>
		<howpublished>Internet RFC 4395</howpublished>
		<title type="sharef:primaryTitle">Guidelines and Registration Procedures for New URI Schemes</title>
		<field type="bibtex:topic">uri[0.9]</field>
		<field type="bibtex:updates">rfc2717 rfc2718</field>
	</reference>
	<reference name="rfc4437" src="bibtex:misc" src-info="bibtex:line-45098" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>E. James</givenname>
				<surname>Whitehead</surname>
			</person>
			<person>
				<givenname>Geoffrey</givenname>
				<surname>Clemm</surname>
			</person>
			<person>
				<givenname>Julian F.</givenname>
				<surname>Reschke</surname>
			</person>
		</names>
		<date value="2006-03"/>
		<abstract>
			<richtext>
				<p>This specification defines an extension to Web Distributed Authoring and Versioning (WebDAV) to allow clients to author HTTP redirect reference resources whose default response is an HTTP/1.1 3xx (Redirection) status code. A redirect reference makes it possible to access the target resourced indirectly through any URI mapped to the redirect reference resource. This specification does not address remapping of trees of resources or regular expression based redirections. There are no integrity guarantees associated with redirect reference resources. Other mechanisms can also be used to achieve the same functionality as this specification. This specification allows operators to experiment with this mechanism and develop experience on what is the best approach to the problem.</p>
			</richtext>
		</abstract>
		<howpublished>Internet RFC 4437</howpublished>
		<title type="sharef:primaryTitle">Web Distributed Authoring and Versioning (WebDAV) Redirect Reference Resources</title>
		<field type="bibtex:topic">webdav[0.9]</field>
	</reference>
	<reference name="rfc4452" src="bibtex:misc" src-info="bibtex:line-45108" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Herbert</givenname>
				<surname>Van de Sompel</surname>
			</person>
			<person>
				<givenname>Tony</givenname>
				<surname>Hammond</surname>
			</person>
			<person>
				<givenname>Eamonn</givenname>
				<surname>Neylon</surname>
			</person>
			<person>
				<givenname>Stuart L.</givenname>
				<surname>Weibel</surname>
			</person>
		</names>
		<date value="2006-04"/>
		<abstract>
			<richtext>
				<p>This document defines the "info" Uniform Resource Identifier (URI) scheme for information assets with identifiers in public namespaces. Namespaces participating in the "info" URI scheme are regulated by an "info" Registry mechanism.</p>
			</richtext>
		</abstract>
		<howpublished>Internet RFC 4452</howpublished>
		<title type="sharef:primaryTitle">The "info" URI Scheme for Information Assets with Identifiers in Public Namespaces</title>
		<field type="bibtex:topic">uri[0.9]</field>
	</reference>
	<reference name="rfc4458" src="bibtex:misc" src-info="bibtex:line-45118" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Cullen</givenname>
				<surname>Jennings</surname>
			</person>
			<person>
				<givenname>François</givenname>
				<surname>Audet</surname>
			</person>
			<person>
				<givenname>John</givenname>
				<surname>Elwell</surname>
			</person>
		</names>
		<date value="2006-04"/>
		<abstract>
			<richtext>
				<p>The Session Initiation Protocol (SIP) is often used to initiate connections to applications such as voicemail or interactive voice recognition systems. This specification describes a convention for forming SIP service URIs that request particular services based on redirecting targets from such applications.</p>
			</richtext>
		</abstract>
		<howpublished>Internet RFC 4458</howpublished>
		<title type="sharef:primaryTitle">Session Initiation Protocol (SIP) URIs for Applications such as Voicemail and Interactive Voice Response (IVR)</title>
		<field type="bibtex:topic">ivr[0.8] sip[0.7]</field>
	</reference>
	<reference name="rfc4467" src="bibtex:misc" src-info="bibtex:line-45128" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Mark R.</givenname>
				<surname>Crispin</surname>
			</person>
		</names>
		<date value="2006-05"/>
		<abstract>
			<richtext>
				<p>This document describes the URLAUTH extension to the Internet Message Access Protocol (IMAP) (RFC 3501) and the IMAP URL Scheme (IMAPURL) (RFC 2192). This extension provides a means by which an IMAP client can use URLs carrying authorization to access limited message data on the IMAP server. An IMAP server that supports this extension indicates this with a capability name of "URLAUTH".</p>
			</richtext>
		</abstract>
		<howpublished>Internet RFC 4467</howpublished>
		<title type="sharef:primaryTitle">Internet Message Access Protocol (IMAP) — URLAUTH Extension</title>
		<field type="bibtex:topic">imap[0.9]</field>
		<field type="bibtex:updates">rfc3501</field>
	</reference>
	<reference name="rfc4501" src="bibtex:misc" src-info="bibtex:line-45139" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Simon</givenname>
				<surname>Josefsson</surname>
			</person>
		</names>
		<date value="2006-05"/>
		<abstract>
			<richtext>
				<p>This document defines Uniform Resource Identifiers for Domain Name System resources.</p>
			</richtext>
		</abstract>
		<howpublished>Internet RFC 4501</howpublished>
		<title type="sharef:primaryTitle">Domain Name System Uniform Resource Identifiers</title>
		<field type="bibtex:topic">dns[0.9] uri[0.9]</field>
	</reference>
	<reference name="rfc4589" src="bibtex:misc" src-info="bibtex:line-45149" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Henning</givenname>
				<surname>Schulzrinne</surname>
			</person>
			<person>
				<givenname>Hannes</givenname>
				<surname>Tschofenig</surname>
			</person>
		</names>
		<date value="2006-07"/>
		<abstract>
			<richtext>
				<p>This document creates a registry for describing the types of places a human or end system might be found. The registry is then referenced by other protocols that need a common set of location terms as protocol constants. Examples of location terms defined in this document include aircraft, office, and train station.</p>
			</richtext>
		</abstract>
		<howpublished>Internet RFC 4589</howpublished>
		<title type="sharef:primaryTitle">Location Types Registry</title>
	</reference>
	<reference name="rfc4627" src="bibtex:misc" src-info="bibtex:line-45158" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Douglas</givenname>
				<surname>Crockford</surname>
			</person>
		</names>
		<date value="2006-07"/>
		<abstract>
			<richtext>
				<p>JavaScript Object Notation (JSON) is a lightweight, text-based, language-independent data interchange format. It was derived from the ECMAScript Programming Language Standard. JSON defines a small set of formatting rules for the portable representation of structured data.</p>
			</richtext>
		</abstract>
		<howpublished>Internet RFC 4627</howpublished>
		<title type="sharef:primaryTitle">The application/json Media Type for JavaScript Object Notation (JSON)</title>
		<field type="bibtex:topic">json[0.9]</field>
	</reference>
	<reference name="rfc4645" src="bibtex:misc" src-info="bibtex:line-45168" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Doug</givenname>
				<surname>Ewell</surname>
			</person>
		</names>
		<date value="2006-09"/>
		<abstract>
			<richtext>
				<p>This memo defined the initial contents of the IANA Language Subtag Registry for use in forming tags for the identification of languages. Since the contents of this memo only served as a starting point for the registry, its actual contents have been removed before publication to avoid confusion.</p>
			</richtext>
		</abstract>
		<howpublished>Internet RFC 4645</howpublished>
		<title type="sharef:primaryTitle">Initial Language Subtag Registry</title>
		<field type="bibtex:topic">i18n[0.9]</field>
	</reference>
	<reference name="rfc4646" src="bibtex:misc" src-info="bibtex:line-45178" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Addison P.</givenname>
				<surname>Phillips</surname>
			</person>
			<person>
				<givenname>Mark</givenname>
				<surname>Davis</surname>
			</person>
		</names>
		<date value="2006-09"/>
		<abstract>
			<richtext>
				<p>This document describes the structure, content, construction, and semantics of language tags for use in cases where it is desirable to indicate the language used in an information object. It also describes how to register values for use in language tags and the creation of user-defined extensions for private interchange. This document, in combination with RFC 4647, replaces RFC 3066, which replaced RFC 1766.</p>
			</richtext>
		</abstract>
		<howpublished>Internet RFC 4646</howpublished>
		<title type="sharef:primaryTitle">Tags for Identifying Languages</title>
		<field type="bibtex:topic">i18n[0.9]</field>
		<field type="bibtex:updates">rfc3066</field>
	</reference>
	<reference name="rfc4647" src="bibtex:misc" src-info="bibtex:line-45189" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Addison P.</givenname>
				<surname>Phillips</surname>
			</person>
			<person>
				<givenname>Mark</givenname>
				<surname>Davis</surname>
			</person>
		</names>
		<date value="2006-09"/>
		<abstract>
			<richtext>
				<p>This document describes a syntax, called a "language-range", for specifying items in a user's list of language preferences. It also describes different mechanisms for comparing and matching these to language tags. Two kinds of matching mechanisms, filtering and lookup, are defined. Filtering produces a (potentially empty) set of language tags, whereas lookup produces a single language tag. Possible applications include language negotiation or content selection. This document, in combination with RFC 4646, replaces RFC 3066, which replaced RFC 1766.</p>
			</richtext>
		</abstract>
		<howpublished>Internet RFC 4647</howpublished>
		<title type="sharef:primaryTitle">Matching of Language Tags</title>
		<field type="bibtex:topic">i18n[0.9]</field>
		<field type="bibtex:updates">rfc3066</field>
	</reference>
	<reference name="rfc4648" src="bibtex:misc" src-info="bibtex:line-45200" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Simon</givenname>
				<surname>Josefsson</surname>
			</person>
		</names>
		<date value="2006-10"/>
		<abstract>
			<richtext>
				<p>This document describes the commonly used base 64, base 32, and base 16 encoding schemes. It also discusses the use of line-feeds in encoded data, use of padding in encoded data, use of non-alphabet characters in encoded data, use of different encoding alphabets, and canonical encodings.</p>
			</richtext>
		</abstract>
		<howpublished>Internet RFC 4648</howpublished>
		<title type="sharef:primaryTitle">The Base16, Base32, and Base64 Data Encodings</title>
		<field type="bibtex:topic">base16[0.9] base32[1] base64[1]</field>
		<field type="bibtex:updates">rfc3548</field>
	</reference>
	<reference name="rfc4677" src="bibtex:misc" src-info="bibtex:line-45211" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Paul E.</givenname>
				<surname>Hoffman</surname>
			</person>
			<person>
				<givenname>Susan</givenname>
				<surname>Harris</surname>
			</person>
		</names>
		<date value="2006-09"/>
		<abstract>
			<richtext>
				<p>This document describes the inner workings of IETF meetings and Working Groups, discusses organizations related to the IETF, and introduces the standards process. It is not a formal IETF process document but instead an informational overview.</p>
			</richtext>
		</abstract>
		<howpublished>Internet RFC 4677</howpublished>
		<title type="sharef:primaryTitle">The Tao of IETF: A Novice's Guide to the Internet Engineering Task Force</title>
		<field type="bibtex:topic">ietf[1]</field>
		<field type="bibtex:updates">rfc3160</field>
	</reference>
	<reference name="rfc4685" src="bibtex:misc" src-info="bibtex:line-45222" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>James M.</givenname>
				<surname>Snell</surname>
			</person>
		</names>
		<date value="2006-09"/>
		<abstract>
			<richtext>
				<p>This memo presents a mechanism that allows feeds publishers to express threaded discussions within the Atom Syndication Format.</p>
			</richtext>
		</abstract>
		<howpublished>Internet RFC 4685</howpublished>
		<title type="sharef:primaryTitle">Atom Threading Extensions</title>
		<field type="bibtex:topic">atom[0.9]</field>
	</reference>
	<reference name="rfc4745" src="bibtex:misc" src-info="bibtex:line-45232" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Henning</givenname>
				<surname>Schulzrinne</surname>
			</person>
			<person>
				<givenname>Hannes</givenname>
				<surname>Tschofenig</surname>
			</person>
			<person>
				<givenname>John B.</givenname>
				<surname>Morris</surname>
			</person>
			<person>
				<givenname>Jorge R.</givenname>
				<surname>Cuellar</surname>
			</person>
			<person>
				<givenname>James M.</givenname>
				<surname>Polk</surname>
			</person>
			<person>
				<givenname>Jonathan</givenname>
				<surname>Rosenberg</surname>
			</person>
		</names>
		<date value="2007-02"/>
		<abstract>
			<richtext>
				<p>This document defines a framework for authorization policies controlling access to application-specific data. This framework combines common location- and presence-specific authorization aspects. An XML schema specifies the language in which common policy rules are represented. The common policy framework can be extended to other application domains.</p>
			</richtext>
		</abstract>
		<howpublished>Internet RFC 4745</howpublished>
		<title type="sharef:primaryTitle">Common Policy: A Document Format for Expressing Privacy Preferences</title>
	</reference>
	<reference name="rfc4791" src="bibtex:misc" src-info="bibtex:line-45241" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Cyrus</givenname>
				<surname>Daboo</surname>
			</person>
			<person>
				<givenname>Bernard</givenname>
				<surname>Desruisseaux</surname>
			</person>
			<person>
				<givenname>Lisa</givenname>
				<surname>Dusseault</surname>
			</person>
		</names>
		<date value="2007-03"/>
		<abstract>
			<richtext>
				<p>This document defines extensions to the Web Distributed Authoring and Versioning (WebDAV) protocol to specify a standard way of accessing, managing, and sharing calendaring and scheduling information based on the iCalendar format. This document defines the "calendar-access" feature of CalDAV.</p>
			</richtext>
		</abstract>
		<howpublished>Internet RFC 4791</howpublished>
		<title type="sharef:primaryTitle">Calendaring Extensions to WebDAV (CalDAV)</title>
		<field type="bibtex:topic">caldav[1] webdav[0.9]</field>
	</reference>
	<reference name="rfc4918" src="bibtex:misc" src-info="bibtex:line-45251" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Lisa</givenname>
				<surname>Dusseault</surname>
			</person>
		</names>
		<date value="2007-06"/>
		<abstract>
			<richtext>
				<p>Web Distributed Authoring and Versioning (WebDAV) consists of a set of methods, headers, and content-types ancillary to HTTP/1.1 for the management of resource properties, creation and management of resource collections, URL namespace manipulation, and resource locking (collision avoidance). RFC 2518 was published in February 1999, and this specification obsoletes RFC 2518 with minor revisions mostly due to interoperability experience.</p>
			</richtext>
		</abstract>
		<howpublished>Internet RFC 4918</howpublished>
		<title type="sharef:primaryTitle">HTTP Extensions for Web Distributed Authoring and Versioning (WebDAV)</title>
		<field type="bibtex:topic">http[0.9] webdav[1]</field>
		<field type="bibtex:updates">rfc2518</field>
	</reference>
	<reference name="rfc4946" src="bibtex:misc" src-info="bibtex:line-45262" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>James M.</givenname>
				<surname>Snell</surname>
			</person>
		</names>
		<date value="2007-07"/>
		<abstract>
			<richtext>
				<p>This memo defines an extension to the Atom Syndication Format for describing licenses associated with Atom feeds and entries.</p>
			</richtext>
		</abstract>
		<howpublished>Internet RFC 4946</howpublished>
		<title type="sharef:primaryTitle">Atom License Extension</title>
		<field type="bibtex:topic">atom[0.9]</field>
	</reference>
	<reference name="rfc4952" src="bibtex:misc" src-info="bibtex:line-45272" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>John C.</givenname>
				<surname>Klensin</surname>
			</person>
			<person>
				<givenname>YangWoo</givenname>
				<surname>Ko</surname>
			</person>
		</names>
		<date value="2007-07"/>
		<abstract>
			<richtext>
				<p>Full use of electronic mail throughout the world requires that people be able to use their own names, written correctly in their own languages and scripts, as mailbox names in email addresses. This document introduces a series of specifications that define mechanisms and protocol extensions needed to fully support internationalized email addresses. These changes include an SMTP extension and extension of email header syntax to accommodate UTF-8 data. The document set also includes discussion of key assumptions and issues in deploying fully internationalized email.</p>
			</richtext>
		</abstract>
		<howpublished>Internet RFC 4952</howpublished>
		<title type="sharef:primaryTitle">Overview and Framework for Internationalized Email</title>
		<field type="bibtex:topic">smtp[1] i18n[0.9]</field>
	</reference>
	<reference name="rfc5005" src="bibtex:misc" src-info="bibtex:line-45282" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Mark</givenname>
				<surname>Nottingham</surname>
			</person>
		</names>
		<date value="2007-09"/>
		<abstract>
			<richtext>
				<p>This specification defines three types of syndicated Web feeds that enable publication of entries across one or more feed documents. This includes "paged" feeds for piecemeal access, "archived" feeds that allow reconstruction of the feed's contents, and feeds that are explicitly "complete".</p>
			</richtext>
		</abstract>
		<howpublished>Internet RFC 5005</howpublished>
		<title type="sharef:primaryTitle">Feed Paging and Archiving</title>
		<field type="bibtex:topic">atompub[0.9] atom[0.9]</field>
		<field type="bibtex:updates">not07</field>
	</reference>
	<reference name="rfc5023" src="bibtex:misc" src-info="bibtex:line-45293" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Joe</givenname>
				<surname>Gregorio</surname>
			</person>
			<person>
				<givenname>Bill</givenname>
				<surname link="de">Hóra</surname>
			</person>
		</names>
		<date value="2007-10"/>
		<abstract>
			<richtext>
				<p>The Atom Publishing Protocol (AtomPub) is an application-level protocol for publishing and editing Web resources. The protocol is based on HTTP transfer of Atom-formatted representations. The Atom format is documented in the Atom Syndication Format.</p>
			</richtext>
		</abstract>
		<howpublished>Internet RFC 5023</howpublished>
		<title type="sharef:primaryTitle">The Atom Publishing Protocol</title>
		<field type="bibtex:topic">atompub[1] atom[0.9]</field>
		<field type="bibtex:updates">gre06</field>
	</reference>
	<reference name="rfc5092" src="bibtex:misc" src-info="bibtex:line-45304" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Chris</givenname>
				<surname>Newman</surname>
			</person>
			<person>
				<givenname>Alexey</givenname>
				<surname>Melnikov</surname>
			</person>
		</names>
		<date value="2007-11"/>
		<abstract>
			<richtext>
				<p>IMAP (RFC 3501) is a rich protocol for accessing remote message stores. It provides an ideal mechanism for accessing public mailing list archives as well as private and shared message stores. This document defines a URL scheme for referencing objects on an IMAP server. This document obsoletes RFC 2192. It also updates RFC 4467.</p>
			</richtext>
		</abstract>
		<howpublished>Internet RFC 5092</howpublished>
		<title type="sharef:primaryTitle">IMAP URL Scheme</title>
		<field type="bibtex:topic">imap[0.9] uri[0.8]</field>
		<field type="bibtex:updates">rfc4467 rfc2192</field>
	</reference>
	<reference name="rfc5139" src="bibtex:misc" src-info="bibtex:line-45315" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Martin</givenname>
				<surname>Thomson</surname>
			</person>
			<person>
				<givenname>James</givenname>
				<surname>Winterbottom</surname>
			</person>
		</names>
		<date value="2008-02"/>
		<abstract>
			<richtext>
				<p>This document defines an XML format for the representation of civic location. This format is designed for use with Presence Information Data Format Location Object (PIDF-LO) documents and replaces the civic location format in RFC 4119. The format is based on the civic address definition in PIDF-LO, but adds several new elements based on the civic types defined for Dynamic Host Configuration Protocol (DHCP), and adds a hierarchy to address complex road identity schemes. The format also includes support for the xml:lang language tag and restricts the types of elements where appropriate.</p>
			</richtext>
		</abstract>
		<howpublished>Internet RFC 5139</howpublished>
		<title type="sharef:primaryTitle">Revised Civic Location Format for Presence Information Data Format Location Object (PIDF-LO)</title>
		<field type="bibtex:topic">pidflo[0.9] pidf[0.8]</field>
	</reference>
	<reference name="rfc5147" src="bibtex:misc" src-info="bibtex:line-45325" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Erik</givenname>
				<surname>Wilde</surname>
			</person>
			<person>
				<givenname>Martin J.</givenname>
				<surname>Dürst</surname>
			</person>
		</names>
		<date value="2008-04"/>
		<abstract>
			<richtext>
				<p>This memo defines URI fragment identifiers for text/plain MIME entities. These fragment identifiers make it possible to refer to parts of a text/plain MIME entity, either identified by character position or range, or by line position or range. Fragment identifiers may also contain information for integrity checks to make them more robust.</p>
			</richtext>
		</abstract>
		<howpublished>Internet RFC 5147</howpublished>
		<title type="sharef:primaryTitle">URI Fragment Identifiers for the text/plain Media Type</title>
		<field type="bibtex:topic">uri[0.8] mime[0.8]</field>
		<field type="bibtex:updates">wil02h</field>
	</reference>
	<reference name="rfc5198" src="bibtex:misc" src-info="bibtex:line-45336" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>John C.</givenname>
				<surname>Klensin</surname>
			</person>
			<person>
				<givenname>Michael A.</givenname>
				<surname>Padlipsky</surname>
			</person>
		</names>
		<date value="2008-03"/>
		<abstract>
			<richtext>
				<p>The Internet today is in need of a standardized form for the transmission of internationalized "text" information, paralleling the specifications for the use of ASCII that date from the early days of the ARPANET. This document specifies that format, using UTF-8 with normalization and specific line-ending sequences.</p>
			</richtext>
		</abstract>
		<howpublished>Internet RFC 5198</howpublished>
		<title type="sharef:primaryTitle">Unicode Format for Network Interchange</title>
		<field type="bibtex:topic">unicode[0.8] utf8[0.8]</field>
	</reference>
	<reference name="rfc5222" src="bibtex:misc" src-info="bibtex:line-45346" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Ted</givenname>
				<surname>Hardie</surname>
			</person>
			<person>
				<givenname>Andrew L.</givenname>
				<surname>Newton</surname>
			</person>
			<person>
				<givenname>Henning</givenname>
				<surname>Schulzrinne</surname>
			</person>
			<person>
				<givenname>Hannes</givenname>
				<surname>Tschofenig</surname>
			</person>
		</names>
		<date value="2008-08"/>
		<abstract>
			<richtext>
				<p>This document describes an XML-based protocol for mapping service identifiers and geodetic or civic location information to service contact URIs. In particular, it can be used to determine the location-appropriate Public Safety Answering Point (PSAP) for emergency services.</p>
			</richtext>
		</abstract>
		<howpublished>Internet RFC 5222</howpublished>
		<title type="sharef:primaryTitle">LoST: A Location-to-Service Translation Protocol</title>
		<field type="bibtex:topic">lost[1]</field>
	</reference>
	<reference name="rfc5226" src="bibtex:misc" src-info="bibtex:line-45356" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Thomas</givenname>
				<surname>Narten</surname>
			</person>
			<person>
				<givenname>Harald Tveit</givenname>
				<surname>Alvestrand</surname>
			</person>
		</names>
		<date value="2008-05"/>
		<abstract>
			<richtext>
				<p>Many protocols make use of identifiers consisting of constants and other well-known values. Even after a protocol has been defined and deployment has begun, new values may need to be assigned (e.g., for a new option type in DHCP, or a new encryption or authentication transform for IPsec). To ensure that such quantities have consistent values and interpretations across all implementations, their assignment must be administered by a central authority. For IETF protocols, that role is provided by the Internet Assigned Numbers Authority (IANA). In order for IANA to manage a given namespace prudently, it needs guidelines describing the conditions under which new values can be assigned or when modifications to existing values can be made. If IANA is expected to play a role in the management of a namespace, IANA must be given clear and concise instructions describing that role. This document discusses issues that should be considered in formulating a policy for assigning values to a namespace and provides guidelines for authors on the specific text that must be included in documents that place demands on IANA.</p>
			</richtext>
		</abstract>
		<howpublished>Internet RFC 5226</howpublished>
		<title type="sharef:primaryTitle">Guidelines for Writing an IANA Considerations Section in RFCs</title>
		<field type="bibtex:topic">rfc[0.9]</field>
		<field type="bibtex:updates">rfc2434</field>
	</reference>
	<reference name="rfc5234" src="bibtex:misc" src-info="bibtex:line-45367" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>David H.</givenname>
				<surname>Crocker</surname>
			</person>
			<person>
				<givenname>Paul</givenname>
				<surname>Overell</surname>
			</person>
		</names>
		<date value="2008-01"/>
		<abstract>
			<richtext>
				<p>Internet technical specifications often need to define a formal syntax. Over the years, a modified version of Backus-Naur Form (BNF), called Augmented BNF (ABNF), has been popular among many Internet specifications. The current specification documents ABNF. It balances compactness and simplicity with reasonable representational power. The differences between standard BNF and ABNF involve naming rules, repetition, alternatives, order-independence, and value ranges. This specification also supplies additional rule definitions and encoding for a core lexical analyzer of the type common to several Internet specifications.</p>
			</richtext>
		</abstract>
		<howpublished>Internet RFC 5234</howpublished>
		<title type="sharef:primaryTitle">Augmented BNF for Syntax Specifications: ABNF</title>
		<field type="bibtex:topic">abnf[1]</field>
		<field type="bibtex:updates">rfc4234</field>
	</reference>
	<reference name="rfc5246" src="bibtex:misc" src-info="bibtex:line-45378" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Tim</givenname>
				<surname>Dierks</surname>
			</person>
			<person>
				<givenname>Eric</givenname>
				<surname>Rescorla</surname>
			</person>
		</names>
		<date value="2008-08"/>
		<abstract>
			<richtext>
				<p>This document specifies Version 1.2 of the Transport Layer Security (TLS) protocol. The TLS protocol provides communications security over the Internet. The protocol allows client/server applications to communicate in a way that is designed to prevent eavesdropping,
   tampering, or message forgery.</p>
			</richtext>
		</abstract>
		<howpublished>Internet RFC 5246</howpublished>
		<title type="sharef:primaryTitle">The Transport Layer Security (TLS) Protocol — Version 1.2</title>
		<field type="bibtex:topic">tls[1]</field>
		<field type="bibtex:updates">rfc3268 rfc4346 rfc4366 rfc4492</field>
	</reference>
	<reference name="rfc5261" src="bibtex:misc" src-info="bibtex:line-45390" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Jari</givenname>
				<surname>Urpalainen</surname>
			</person>
		</names>
		<date value="2008-09"/>
		<abstract>
			<richtext>
				<p>Extensible Markup Language (XML) documents are widely used as containers for the exchange and storage of arbitrary data in today's systems. In order to send changes to an XML document, an entire copy of the new version must be sent, unless there is a means of indicating only the portions that have changed. This document describes an XML patch framework utilizing XML Path language (XPath) selectors. These selector values and updated new data content constitute the basis of patch operations described in this document. In addition to them, with basic &lt;add&gt;, &lt;replace&gt;, and &lt;remove&gt;  directives a set of patches can then be applied to update an existing XML document.</p>
			</richtext>
		</abstract>
		<howpublished>Internet RFC 5261</howpublished>
		<title type="sharef:primaryTitle">An Extensible Markup Language (XML) Patch Operations Framework Utilizing XML Path Language (XPath) Selectors</title>
		<field type="bibtex:topic">xpath[0.7] xml[0.9]</field>
	</reference>
	<reference name="rfc5267" src="bibtex:misc" src-info="bibtex:line-45400" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Dave</givenname>
				<surname>Cridland</surname>
			</person>
			<person>
				<givenname>Curtis</givenname>
				<surname>King</surname>
			</person>
		</names>
		<date value="2008-07"/>
		<abstract>
			<richtext>
				<p>The IMAP4rev1 protocol has powerful search facilities as part of the core protocol, but lacks the ability to create live, updated results that can be easily handled. This memo provides such an extension, and shows how it can be used to provide a facility similar to virtual mailboxes.</p>
			</richtext>
		</abstract>
		<howpublished>Internet RFC 5267</howpublished>
		<title type="sharef:primaryTitle">Contexts for IMAP4</title>
		<field type="bibtex:topic">imap[0.9]</field>
	</reference>
	<reference name="rfc5321" src="bibtex:misc" src-info="bibtex:line-45410" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>John C.</givenname>
				<surname>Klensin</surname>
			</person>
		</names>
		<date value="2008-10"/>
		<abstract>
			<richtext>
				<p>This document is a specification of the basic protocol for Internet electronic mail transport. It consolidates, updates, and clarifies several previous documents, making all or parts of most of them obsolete. It covers the SMTP extension mechanisms and best practices for the contemporary Internet, but does not provide details about particular extensions. Although SMTP was designed as a mail transport and delivery protocol, this specification also contains information that is important to its use as a "mail submission" protocol for "split-UA" (User Agent) mail reading systems and mobile environments.</p>
			</richtext>
		</abstract>
		<howpublished>Internet RFC 5321</howpublished>
		<title type="sharef:primaryTitle">Simple Mail Transfer Protocol</title>
		<field type="bibtex:topic">smtp[1]</field>
		<field type="bibtex:updates">rfc1123 rfc2821</field>
	</reference>
	<reference name="rfc5322" src="bibtex:misc" src-info="bibtex:line-45421" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Peter W.</givenname>
				<surname>Resnick</surname>
			</person>
		</names>
		<date value="2008-10"/>
		<abstract>
			<richtext>
				<p>This document specifies the Internet Message Format (IMF), a syntax for text messages that are sent between computer users, within the framework of "electronic mail" messages. This specification is a revision of Request For Comments (RFC) 2822, which itself superseded Request For Comments (RFC) 822, "Standard for the Format of ARPA Internet Text Messages", updating it to reflect current practice and incorporating incremental changes that were specified in other RFCs.</p>
			</richtext>
		</abstract>
		<howpublished>Internet RFC 5322</howpublished>
		<title type="sharef:primaryTitle">Internet Message Format</title>
		<field type="bibtex:topic">smtp[0.9] imf[1]</field>
		<field type="bibtex:updates">rfc2822 rfc4021</field>
	</reference>
	<reference name="rfc5323" src="bibtex:misc" src-info="bibtex:line-45432" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Julian F.</givenname>
				<surname>Reschke</surname>
			</person>
			<person>
				<givenname>Surendra</givenname>
				<surname>Reddy</surname>
			</person>
			<person>
				<givenname>Jim</givenname>
				<surname>Davis</surname>
			</person>
			<person>
				<givenname>Alan</givenname>
				<surname>Babich</surname>
			</person>
		</names>
		<date value="2008-11"/>
		<abstract>
			<richtext>
				<p>This document specifies a set of methods, headers, and properties composing Web Distributed Authoring and Versioning (WebDAV) SEARCH, an application of the HTTP/1.1 protocol to efficiently search for DAV resources based upon a set of client-supplied criteria.</p>
			</richtext>
		</abstract>
		<howpublished>Internet RFC 5323</howpublished>
		<title type="sharef:primaryTitle">Web Distributed Authoring and Versioning (WebDAV) SEARCH</title>
		<field type="bibtex:topic">webdav[0.9]</field>
	</reference>
	<reference name="rfc5333" src="bibtex:misc" src-info="bibtex:line-45442" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Rohan</givenname>
				<surname>Mahy</surname>
			</person>
			<person>
				<givenname>Bernhard</givenname>
				<surname>Hoeneisen</surname>
			</person>
		</names>
		<date value="2009-10"/>
		<abstract>
			<richtext>
				<p>This document registers Enumservices for Internet calendaring. Specifically, this document focuses on Enumservices for scheduling with iMIP (iCalendar Message-Based Interoperability Protocol) and for accessing Internet calendaring information with CalDAV (Calendaring Extensions to WebDAV).</p>
			</richtext>
		</abstract>
		<howpublished>Internet RFC 5333</howpublished>
		<title type="sharef:primaryTitle">IANA Registration of Enumservices for Internet Calendaring</title>
		<field type="bibtex:topic">imip[0.9] caldav[0.9] icalendar[0.8]</field>
	</reference>
	<reference name="rfc5334" src="bibtex:misc" src-info="bibtex:line-45452" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Ivo Emanuel</givenname>
				<surname>Goncalves</surname>
			</person>
			<person>
				<givenname>Silvia</givenname>
				<surname>Pfeiffer</surname>
			</person>
			<person>
				<givenname>Christopher</givenname>
				<surname>Montgomery</surname>
			</person>
		</names>
		<date value="2008-09"/>
		<abstract>
			<richtext>
				<p>This document describes the registration of media types for the Ogg container format and conformance requirements for implementations of these types. This document obsoletes RFC 3534.</p>
			</richtext>
		</abstract>
		<howpublished>Internet RFC 5334</howpublished>
		<title type="sharef:primaryTitle">Ogg Media Types</title>
		<field type="bibtex:topic">ogg[0.9] mime[0.8]</field>
		<field type="bibtex:updates">rfc3534</field>
	</reference>
	<reference name="rfc5335" src="bibtex:misc" src-info="bibtex:line-45463" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Abel</givenname>
				<surname>Yang</surname>
			</person>
		</names>
		<date value="2008-09"/>
		<abstract>
			<richtext>
				<p>Full internationalization of electronic mail requires not only the capabilities to transmit non-ASCII content, to encode selected information in specific header fields, and to use non-ASCII characters in envelope addresses. It also requires being able to express those addresses and the information based on them in mail header fields. This document specifies an experimental variant of Internet mail that permits the use of Unicode encoded in UTF-8, rather than ASCII, as the base form for Internet email header field. This form is permitted in transmission only if authorized by an SMTP extension, as specified in an associated specification. This specification Updates section 6.4 of RFC 2045 to conform with the requirements.</p>
			</richtext>
		</abstract>
		<howpublished>Internet RFC 5335</howpublished>
		<title type="sharef:primaryTitle">Internationalized Email Headers</title>
		<field type="bibtex:topic">smtp[1]</field>
		<field type="bibtex:updates">rfc2045 rfc2822</field>
	</reference>
	<reference name="rfc5336" src="bibtex:misc" src-info="bibtex:line-45474" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Jiankang</givenname>
				<surname>Yao</surname>
			</person>
			<person>
				<givenname>Wei</givenname>
				<surname>Mao</surname>
			</person>
		</names>
		<date value="2008-09"/>
		<abstract>
			<richtext>
				<p>This document specifies an SMTP extension for transport and delivery of email messages with internationalized email addresses or header information. Communication with systems that do not implement this specification is specified in another document. This document updates some syntaxes and rules defined in RFC 2821 and RFC 2822, and has some material updating RFC 4952.</p>
			</richtext>
		</abstract>
		<howpublished>Internet RFC 5336</howpublished>
		<title type="sharef:primaryTitle">SMTP Extension for Internationalized Email Addresses</title>
		<field type="bibtex:topic">smtp[1]</field>
		<field type="bibtex:updates">rfc2821 rfc2822 rfc4952</field>
	</reference>
	<reference name="rfc5337" src="bibtex:misc" src-info="bibtex:line-45485" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Chris</givenname>
				<surname>Newman</surname>
			</person>
			<person>
				<givenname>Alexey</givenname>
				<surname>Melnikov</surname>
			</person>
		</names>
		<date value="2008-09"/>
		<abstract>
			<richtext>
				<p>Delivery status notifications (DSNs) are critical to the correct operation of an email system. However, the existing Draft Standards (RFC 3461, RFC 3462, RFC 3464) are presently limited to US-ASCII text in the machine-readable portions of the protocol. This specification adds a new address type for international email addresses so an original recipient address with non-US-ASCII characters can be correctly preserved even after downgrading. This also provides updated content return media types for delivery status notifications and message disposition notifications to support use of the new address type. This document experimentally extends RFC 3461, RFC 3464, and RFC 3798.</p>
			</richtext>
		</abstract>
		<howpublished>Internet RFC 5337</howpublished>
		<title type="sharef:primaryTitle">Internationalized Delivery Status and Disposition Notifications</title>
		<field type="bibtex:topic">smtp[1] dsn[1]</field>
		<field type="bibtex:updates">rfc3461 rfc3462 rfc3798</field>
	</reference>
	<reference name="rfc5341" src="bibtex:misc" src-info="bibtex:line-45496" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Cullen</givenname>
				<surname>Jennings</surname>
			</person>
			<person>
				<givenname>Vijay K.</givenname>
				<surname>Gurbani</surname>
			</person>
		</names>
		<date value="2008-09"/>
		<abstract>
			<richtext>
				<p>This document creates an Internet Assigned Number Authority (IANA) registry for tel Uniform Resource Identifier (URI) parameters and their values. It populates the registry with the parameters defined in the tel URI specification, along with the parameters in tel URI extensions defined for number portability and trunk groups.</p>
			</richtext>
		</abstract>
		<howpublished>Internet RFC 5341</howpublished>
		<title type="sharef:primaryTitle">The Internet Assigned Number Authority (IANA) tel Uniform Resource Identifier (URI) Parameter Registry</title>
		<field type="bibtex:updates">rfc3966</field>
	</reference>
	<reference name="rfc5395" src="bibtex:misc" src-info="bibtex:line-45506" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Donald E.</givenname>
				<surname>Eastlake</surname>
			</person>
		</names>
		<date value="2008-11"/>
		<abstract>
			<richtext>
				<p>Internet Assigned Number Authority (IANA) parameter assignment considerations are specified for the allocation of Domain Name System (DNS) resource record types, CLASSes, operation codes, error codes, DNS protocol message header bits, and AFSDB resource record subtypes.</p>
			</richtext>
		</abstract>
		<howpublished>Internet RFC 5395</howpublished>
		<title type="sharef:primaryTitle">Domain Name System (DNS) IANA Considerations</title>
		<field type="bibtex:updates">rfc2929 rfc1183 rfc3597</field>
	</reference>
	<reference name="rfc5411" src="bibtex:misc" src-info="bibtex:line-45516" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Jonathan</givenname>
				<surname>Rosenberg</surname>
			</person>
		</names>
		<date value="2009-01"/>
		<abstract>
			<richtext>
				<p>The Session Initiation Protocol (SIP) is the subject of numerous specifications that have been produced by the IETF. It can be difficult to locate the right document, or even to determine the set of Request for Comments (RFC) about SIP. This specification serves as a guide to the SIP RFC series. It lists a current snapshot of the specifications under the SIP umbrella, briefly summarizes each, and groups them into categories.</p>
			</richtext>
		</abstract>
		<howpublished>Internet RFC 5411</howpublished>
		<title type="sharef:primaryTitle">A Hitchhiker's Guide to the Session Initiation Protocol (SIP)</title>
		<field type="bibtex:topic">sip[0.9]</field>
	</reference>
	<reference name="rfc5465" src="bibtex:misc" src-info="bibtex:line-45526" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Arnt</givenname>
				<surname>Gulbrandsen</surname>
			</person>
			<person>
				<givenname>Curtis</givenname>
				<surname>King</surname>
			</person>
			<person>
				<givenname>Alexey</givenname>
				<surname>Melnikov</surname>
			</person>
		</names>
		<date value="2009-02"/>
		<abstract>
			<richtext>
				<p>This document defines an IMAP extension that allows a client to request specific kinds of unsolicited notifications for specified mailboxes, such as messages being added to or deleted from such mailboxes.</p>
			</richtext>
		</abstract>
		<howpublished>Internet RFC 5465</howpublished>
		<title type="sharef:primaryTitle">The IMAP NOTIFY Extension</title>
		<field type="bibtex:topic">imap[0.9]</field>
		<field type="bibtex:updates">rfc5267</field>
	</reference>
	<reference name="rfc5466" src="bibtex:misc" src-info="bibtex:line-45537" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Alexey</givenname>
				<surname>Melnikov</surname>
			</person>
			<person>
				<givenname>Curtis</givenname>
				<surname>King</surname>
			</person>
		</names>
		<date value="2009-02"/>
		<abstract>
			<richtext>
				<p>The document defines a way to persistently store named IMAP (RFC 3501) searches on the server. Such named searches can be subsequently referenced in a SEARCH or any other command that accepts a search criterion as a parameter.</p>
			</richtext>
		</abstract>
		<howpublished>Internet RFC 5466</howpublished>
		<title type="sharef:primaryTitle">IMAP4 Extension for Named Searches (Filters)</title>
		<field type="bibtex:topic">imap[0.9]</field>
	</reference>
	<reference name="rfc5469" src="bibtex:misc" src-info="bibtex:line-45547" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Pasi</givenname>
				<surname>Eronen</surname>
			</person>
		</names>
		<date value="2009-02"/>
		<abstract>
			<richtext>
				<p>Transport Layer Security (TLS) versions 1.0 (RFC 2246) and 1.1 (RFC 4346) include cipher suites based on DES (Data Encryption Standard) and IDEA (International Data Encryption Algorithm) algorithms. DES (when used in single-DES mode) and IDEA are no longer recommended for general use in TLS, and have been removed from TLS version 1.2 (RFC 5246). This document specifies these cipher suites for completeness and discusses reasons why their use is no longer recommended.</p>
			</richtext>
		</abstract>
		<howpublished>Internet RFC 5469</howpublished>
		<title type="sharef:primaryTitle">DES and IDEA Cipher Suites for Transport Layer Security (TLS)</title>
		<field type="bibtex:topic">tls[0.9] des[0.9] idea[0.9]</field>
	</reference>
	<reference name="rfc5482" src="bibtex:misc" src-info="bibtex:line-45557" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Lars</givenname>
				<surname>Eggert</surname>
			</person>
			<person>
				<givenname>Fernando</givenname>
				<surname>Gont</surname>
			</person>
		</names>
		<date value="2009-03"/>
		<abstract>
			<richtext>
				<p>The TCP user timeout controls how long transmitted data may remain unacknowledged before a connection is forcefully closed. It is a local, per-connection parameter. This document specifies a new TCP option — the TCP User Timeout Option — that allows one end of a TCP connection to advertise its current user timeout value. This information provides advice to the other end of the TCP connection to adapt its user timeout accordingly. Increasing the user timeouts on both ends of a TCP connection allows it to survive extended periods without end-to-end connectivity. Decreasing the user timeouts allows busy servers to explicitly notify their clients that they will maintain the connection state only for a short time without connectivity.</p>
			</richtext>
		</abstract>
		<howpublished>Internet RFC 5482</howpublished>
		<title type="sharef:primaryTitle">TCP User Timeout Option</title>
		<field type="bibtex:topic">tcp[0.9]</field>
	</reference>
	<reference name="rfc5491" src="bibtex:misc" src-info="bibtex:line-45567" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>James</givenname>
				<surname>Winterbottom</surname>
			</person>
			<person>
				<givenname>Martin</givenname>
				<surname>Thomson</surname>
			</person>
			<person>
				<givenname>Hannes</givenname>
				<surname>Tschofenig</surname>
			</person>
		</names>
		<date value="2009-03"/>
		<abstract>
			<richtext>
				<p>The Presence Information Data Format Location Object (PIDF-LO) specification provides a flexible and versatile means to represent location information. There are, however, circumstances that arise when information needs to be constrained in how it is represented. In these circumstances, the range of options that need to be implemented are reduced. There is growing interest in being able to use location information contained in a PIDF-LO for routing applications. To allow successful interoperability between applications, location information needs to be normative and more tightly constrained than is currently specified in RFC 4119 (PIDF- LO). This document makes recommendations on how to constrain, represent, and interpret locations in a PIDF-LO. It further recommends a subset of Geography Markup Language (GML) 3.1.1 that is mandatory to implement by applications involved in location-based routing.</p>
			</richtext>
		</abstract>
		<howpublished>Internet RFC 5491</howpublished>
		<title type="sharef:primaryTitle">GEOPRIV Presence Information Data Format Location Object (PIDF-LO) Usage Clarification, Considerations, and Recommendations</title>
		<field type="bibtex:topic">pidflo[0.9] geopriv[0.9]</field>
	</reference>
	<reference name="rfc5504" src="bibtex:misc" src-info="bibtex:line-45577" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Kazunori</givenname>
				<surname>Fujiwara</surname>
			</person>
			<person>
				<givenname>Yoshiro</givenname>
				<surname>Yoneya</surname>
			</person>
		</names>
		<date value="2009-03"/>
		<abstract>
			<richtext>
				<p>Traditional mail systems handle only ASCII characters in SMTP envelope and mail header fields. The Email Address Internationalization (UTF8SMTP) extension allows UTF-8 characters in SMTP envelope and mail header fields. To avoid rejecting internationalized email messages when a server in the delivery path does not support the UTF8SMTP extension, some sort of converting mechanism is required. This document describes a downgrading mechanism for Email Address Internationalization. Note that this is a way to downgrade, not tunnel. There is no associated up-conversion mechanism, although internationalized email clients might use original internationalized addresses or other data when displaying or replying to downgraded messages.</p>
			</richtext>
		</abstract>
		<howpublished>Internet RFC 5504</howpublished>
		<title type="sharef:primaryTitle">Downgrading Mechanism for Email Address Internationalization</title>
		<field type="bibtex:topic">smtp[0.9] utf8[0.8]</field>
	</reference>
	<reference name="rfc5538" src="bibtex:misc" src-info="bibtex:line-45587" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Frank</givenname>
				<surname>Ellermann</surname>
			</person>
		</names>
		<date value="2010-04"/>
		<abstract>
			<richtext>
				<p>This memo specifies the 'news' and 'nntp' Uniform Resource Identifier (URI) schemes that were originally defined in RFC 1738. The purpose of this document is to allow RFC 1738 to be made obsolete while keeping the information about these schemes on the Standards Track.</p>
			</richtext>
		</abstract>
		<howpublished>Internet RFC 5538</howpublished>
		<title type="sharef:primaryTitle">The 'news' and 'nntp' URI Schemes</title>
		<field type="bibtex:topic">uri[0.9] nntp[0.9] news[0.9]</field>
		<field type="bibtex:updates">rfc1738</field>
	</reference>
	<reference name="rfc5540" src="bibtex:misc" src-info="bibtex:line-45598" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<surname>RFC Editor</surname>
			</person>
		</names>
		<date value="2009-04"/>
		<abstract>
			<richtext>
				<p>This RFC marks the 40th anniversary of the RFC document series.</p>
			</richtext>
		</abstract>
		<howpublished>Internet RFC 5540</howpublished>
		<title type="sharef:primaryTitle">40 Years of RFCs</title>
		<field type="bibtex:topic">rfc[1]</field>
	</reference>
	<reference name="rfc5544" src="bibtex:misc" src-info="bibtex:line-45608" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Adriano</givenname>
				<surname>Santoni</surname>
			</person>
		</names>
		<date value="2010-02"/>
		<abstract>
			<richtext>
				<p>This document describes an envelope that can be used to bind a file (not necessarily protected by means of cryptographic techniques) with one or more time-stamp tokens obtained for that file, where "time-stamp token" has the meaning defined in RFC 3161 or its successors. Additional types of temporal evidence are also allowed. The proposed envelope is based on the Cryptographic Message Syntax as defined in RFC 5652.</p>
			</richtext>
		</abstract>
		<howpublished>Internet RFC 5544</howpublished>
		<title type="sharef:primaryTitle">Syntax for Binding Documents with Time-Stamps</title>
	</reference>
	<reference name="rfc5545" src="bibtex:misc" src-info="bibtex:line-45617" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Bernard</givenname>
				<surname>Desruisseaux</surname>
			</person>
		</names>
		<date value="2009-09"/>
		<abstract>
			<richtext>
				<p>This document defines the iCalendar data format for representing and exchanging calendaring and scheduling information such as events, to-dos, journal entries, and free/busy information, independent of any particular calendar service or protocol.</p>
			</richtext>
		</abstract>
		<howpublished>Internet RFC 5545</howpublished>
		<title type="sharef:primaryTitle">Internet Calendaring and Scheduling Core Object Specification (iCalendar)</title>
		<field type="bibtex:topic">icalendar[1]</field>
		<field type="bibtex:updates">rfc2445</field>
	</reference>
	<reference name="rfc5582" src="bibtex:misc" src-info="bibtex:line-45628" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Henning</givenname>
				<surname>Schulzrinne</surname>
			</person>
		</names>
		<date value="2009-09"/>
		<abstract>
			<richtext>
				<p>This document describes an architecture for a global, scalable, resilient, and administratively distributed system for mapping geographic location information to URLs, using the Location-to-Service Translation (LoST) protocol. The architecture generalizes well-known approaches found in hierarchical lookup systems such as DNS.</p>
			</richtext>
		</abstract>
		<howpublished>Internet RFC 5582</howpublished>
		<title type="sharef:primaryTitle">Location-to-URL Mapping Architecture and Framework</title>
		<field type="bibtex:topic">lost[0.9]</field>
	</reference>
	<reference name="rfc5593" src="bibtex:misc" src-info="bibtex:line-45638" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Neil L.</givenname>
				<surname>Cook</surname>
			</person>
		</names>
		<date value="2009-06"/>
		<abstract>
			<richtext>
				<p>The existing IMAP URL specification (RFC 5092) lists several &lt;access&gt; identifiers and &lt;access&gt; identifier prefixes that can be used to restrict access to URLAUTH-generated URLs. However, these identifiers do not provide facilities for new services such as streaming. This document proposes a set of new &lt;access&gt; identifiers as well as an IANA mechanism to register new &lt;access&gt; identifiers for future applications. This document updates RFC 5092.</p>
			</richtext>
		</abstract>
		<howpublished>Internet RFC 5593</howpublished>
		<title type="sharef:primaryTitle">Internet Message Access Protocol (IMAP) — URL Access Identifier Extension</title>
		<field type="bibtex:topic">imap[0.9] uri[0.8]</field>
		<field type="bibtex:updates">rfc5092</field>
	</reference>
	<reference name="rfc5594" src="bibtex:misc" src-info="bibtex:line-45649" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Jon</givenname>
				<surname>Peterson</surname>
			</person>
			<person>
				<givenname>Alissa</givenname>
				<surname>Cooper</surname>
			</person>
		</names>
		<date value="2009-07"/>
		<abstract>
			<richtext>
				<p>This document reports the outcome of a workshop organized by the Real-time Applications and Infrastructure Area Directors of the IETF to discuss network delay and congestion issues resulting from increased Peer-to-Peer (P2P) traffic volumes. The workshop was held on May 28, 2008 at MIT in Cambridge, MA, USA. The goals of the workshop were twofold: to understand the technical problems that ISPs and end users are experiencing as a result of high volumes of P2P traffic, and to begin to understand how the IETF may be helpful in addressing these problems. Gaining an understanding of where in the IETF this work might be pursued and how to extract feasible work items were highlighted as important tasks in pursuit of the latter goal. The workshop was very well attended and produced several work items that have since been taken up by members of the IETF community.</p>
			</richtext>
		</abstract>
		<howpublished>Internet RFC 5594</howpublished>
		<title type="sharef:primaryTitle">Report from the IETF Workshop on Peer-to-Peer (P2P) Infrastructure, May 28, 2008</title>
		<field type="bibtex:topic">p2p[1]</field>
	</reference>
	<reference name="rfc5598" src="bibtex:misc" src-info="bibtex:line-45659" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Dave</givenname>
				<surname>Crocker</surname>
			</person>
		</names>
		<date value="2009-07"/>
		<abstract>
			<richtext>
				<p>Over its thirty-five-year history, Internet Mail has changed significantly in scale and complexity, as it has become a global infrastructure service. These changes have been evolutionary, rather than revolutionary, reflecting a strong desire to preserve both its installed base and its usefulness. To collaborate productively on this large and complex system, all participants need to work from a common view of it and use a common language to describe its components and the interactions among them. But the many differences in perspective currently make it difficult to know exactly what another participant means. To serve as the necessary common frame of reference, this document describes the enhanced Internet Mail architecture, reflecting the current service.</p>
			</richtext>
		</abstract>
		<howpublished>Internet RFC 5598</howpublished>
		<title type="sharef:primaryTitle">Internet Mail Architecture</title>
		<field type="bibtex:topic">email[0.9] smtp[0.9] pop[0.9] imap[0.9] dns[0.9] mime[0.9]</field>
	</reference>
	<reference name="rfc5645" src="bibtex:misc" src-info="bibtex:line-45669" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Doug</givenname>
				<surname>Ewell</surname>
			</person>
		</names>
		<date value="2009-09"/>
		<abstract>
			<richtext>
				<p>This memo defines the procedure used to update the IANA Language Subtag Registry, in conjunction with the publication of RFC 5646, for use in forming tags for identifying languages.</p>
			</richtext>
		</abstract>
		<howpublished>Internet RFC 5645</howpublished>
		<title type="sharef:primaryTitle">Update to the Language Subtag Registry</title>
		<field type="bibtex:topic">i18n[0.9]</field>
		<field type="bibtex:updates">rfc4646</field>
	</reference>
	<reference name="rfc5646" src="bibtex:misc" src-info="bibtex:line-45680" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Addison P.</givenname>
				<surname>Phillips</surname>
			</person>
			<person>
				<givenname>Mark</givenname>
				<surname>Davis</surname>
			</person>
		</names>
		<date value="2009-09"/>
		<abstract>
			<richtext>
				<p>This document describes the structure, content, construction, and semantics of language tags for use in cases where it is desirable to indicate the language used in an information object. It also describes how to register values for use in language tags and the creation of user-defined extensions for private interchange.</p>
			</richtext>
		</abstract>
		<howpublished>Internet RFC 5646</howpublished>
		<title type="sharef:primaryTitle">Tags for Identifying Languages</title>
		<field type="bibtex:topic">i18n[0.9]</field>
		<field type="bibtex:updates">rfc4646</field>
	</reference>
	<reference name="rfc5652" src="bibtex:misc" src-info="bibtex:line-45691" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Russell</givenname>
				<surname>Housley</surname>
			</person>
		</names>
		<date value="2009-09"/>
		<abstract>
			<richtext>
				<p>This document describes the Cryptographic Message Syntax (CMS). This syntax is used to digitally sign, digest, authenticate, or encrypt arbitrary message content.</p>
			</richtext>
		</abstract>
		<howpublished>Internet RFC 5652</howpublished>
		<title type="sharef:primaryTitle">Cryptographic Message Syntax (CMS)</title>
		<field type="bibtex:topic">cms[1]</field>
		<field type="bibtex:updates">rfc3852</field>
	</reference>
	<reference name="rfc5689" src="bibtex:misc" src-info="bibtex:line-45702" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Cyrus</givenname>
				<surname>Daboo</surname>
			</person>
		</names>
		<date value="2009-09"/>
		<abstract>
			<richtext>
				<p>This specification extends the Web Distributed Authoring and Versioning (WebDAV) MKCOL (Make Collection) method to allow collections of arbitrary resourcetype to be created and to allow properties to be set at the same time.</p>
			</richtext>
		</abstract>
		<howpublished>Internet RFC 5689</howpublished>
		<title type="sharef:primaryTitle">Extended MKCOL for Web Distributed Authoring and Versioning (WebDAV)</title>
		<field type="bibtex:topic">webdav[1] http[0.9]</field>
		<field type="bibtex:updates">rfc4791 rfc4918</field>
	</reference>
	<reference name="rfc5724" src="bibtex:misc" src-info="bibtex:line-45713" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Erik</givenname>
				<surname>Wilde</surname>
			</person>
			<person>
				<givenname>Antti</givenname>
				<surname>Vähä-Sipilä</surname>
			</person>
		</names>
		<date value="2010-01"/>
		<abstract>
			<richtext>
				<p>This memo specifies the Uniform Resource Identifier (URI) scheme "sms" for specifying one or more recipients for an SMS message. SMS messages are two-way paging messages that can be sent from and received by a mobile phone or a suitably equipped networked device.</p>
			</richtext>
		</abstract>
		<howpublished>Internet RFC 5724</howpublished>
		<title type="sharef:primaryTitle">URI Scheme for Global System for Mobile Communications (GSM) Short Message Service (SMS)</title>
		<field type="bibtex:topic">sms[0.9] uri[0.8]</field>
		<field type="bibtex:updates">wil02a</field>
	</reference>
	<reference name="rfc5744" src="bibtex:misc" src-info="bibtex:line-45724" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Robert</givenname>
				<surname>Braden</surname>
			</person>
			<person>
				<givenname>Joel M.</givenname>
				<surname>Halpern</surname>
			</person>
		</names>
		<date value="2009-12"/>
		<abstract>
			<richtext>
				<p>This document specifies the procedures by which authors of RFC Independent Submission documents grant the community "incoming" rights for copying and using the text. It also specifies the "outgoing" rights the community grants to readers and users of those documents, and it requests that the IETF Trust manage the outgoing rights to effect this result.</p>
			</richtext>
		</abstract>
		<howpublished>Internet RFC 5744</howpublished>
		<title type="sharef:primaryTitle">Procedures for Rights Handling in the RFC Independent Submission Stream</title>
		<field type="bibtex:topic">rfc[1]</field>
		<field type="bibtex:updates">rfc4846</field>
	</reference>
	<reference name="rfc5785" src="bibtex:misc" src-info="bibtex:line-45735" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Mark</givenname>
				<surname>Nottingham</surname>
			</person>
			<person>
				<givenname>Eran</givenname>
				<surname>Hammer-Lahav</surname>
			</person>
		</names>
		<date value="2010-04"/>
		<abstract>
			<richtext>
				<p>This memo defines a path prefix for "well-known locations", "/.well-known/", in selected Uniform Resource Identifier (URI) schemes.</p>
			</richtext>
		</abstract>
		<howpublished>Internet RFC 5785</howpublished>
		<title type="sharef:primaryTitle">Defining Well-Known Uniform Resource Identifiers (URIs)</title>
		<field type="bibtex:topic">uri[0.9] http[0.9]</field>
		<field type="bibtex:updates">not09a</field>
	</reference>
	<reference name="rfc5789" src="bibtex:misc" src-info="bibtex:line-45746" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Lisa</givenname>
				<surname>Dusseault</surname>
			</person>
			<person>
				<givenname>James M.</givenname>
				<surname>Snell</surname>
			</person>
		</names>
		<date value="2010-03"/>
		<abstract>
			<richtext>
				<p>Several applications extending the Hypertext Transfer Protocol (HTTP) require a feature to do partial resource modification. The existing HTTP PUT method only allows a complete replacement of a document. This proposal adds a new HTTP method, PATCH, to modify an existing HTTP resource.</p>
			</richtext>
		</abstract>
		<howpublished>Internet RFC 5789</howpublished>
		<title type="sharef:primaryTitle">PATCH Method for HTTP</title>
		<field type="bibtex:topic">http[1]</field>
		<field type="bibtex:updates">dus09</field>
	</reference>
	<reference name="rfc5829" src="bibtex:misc" src-info="bibtex:line-45757" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Al</givenname>
				<surname>Brown</surname>
			</person>
			<person>
				<givenname>Geoffrey</givenname>
				<surname>Clemm</surname>
			</person>
			<person>
				<givenname>Julian F.</givenname>
				<surname>Reschke</surname>
			</person>
		</names>
		<date value="2010-04"/>
		<abstract>
			<richtext>
				<p>This specification defines a set of link relation types that may be used on Web resources for navigation between a resource and other resources related to version control, such as past versions and working copies.</p>
			</richtext>
		</abstract>
		<howpublished>Internet RFC 5829</howpublished>
		<title type="sharef:primaryTitle">Link Relation Types for Simple Version Navigation between Web Resources</title>
		<field type="bibtex:topic">http[1]</field>
		<field type="bibtex:updates">bro09</field>
	</reference>
	<reference name="rfc5842" src="bibtex:misc" src-info="bibtex:line-45768" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Geoffrey</givenname>
				<surname>Clemm</surname>
			</person>
			<person>
				<givenname>Jason</givenname>
				<surname>Crawford</surname>
			</person>
			<person>
				<givenname>Julian F.</givenname>
				<surname>Reschke</surname>
			</person>
			<person>
				<givenname>Jim</givenname>
				<surname>Whitehead</surname>
			</person>
		</names>
		<date value="2010-04"/>
		<abstract>
			<richtext>
				<p>This specification defines bindings, and the BIND method for creating multiple bindings to the same resource. Creating a new binding to a resource causes at least one new URI to be mapped to that resource. Servers are required to ensure the integrity of any bindings that they allow to be created.</p>
			</richtext>
		</abstract>
		<howpublished>Internet RFC 5842</howpublished>
		<title type="sharef:primaryTitle">Binding Extensions to Web Distributed Authoring and Versioning (WebDAV)</title>
		<field type="bibtex:topic">webdav[1]</field>
	</reference>
	<reference name="rfc5843" src="bibtex:misc" src-info="bibtex:line-45778" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Anthony</givenname>
				<surname>Bryan</surname>
			</person>
		</names>
		<date value="2010-04"/>
		<abstract>
			<richtext>
				<p>The IANA registry named "Hypertext Transfer Protocol (HTTP) Digest Algorithm Values" defines values for digest algorithms used by Instance Digests in HTTP. Instance Digests in HTTP provide a digest, also known as a checksum or hash, of an entire representation of the current state of a resource. This document adds new values to the registry and updates previous values.</p>
			</richtext>
		</abstract>
		<howpublished>Internet RFC 5843</howpublished>
		<title type="sharef:primaryTitle">Additional Hash Algorithms for HTTP Instance Digests</title>
		<field type="bibtex:topic">http[0.9]</field>
	</reference>
	<reference name="rfc5849" src="bibtex:misc" src-info="bibtex:line-45788" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Eran</givenname>
				<surname>Hammer-Lahav</surname>
			</person>
		</names>
		<date value="2010-04"/>
		<abstract>
			<richtext>
				<p>OAuth provides a method for clients to access server resources on behalf of a resource owner (such as a different client or an end-user). It also provides a process for end-users to authorize third-party access to their server resources without sharing their credentials (typically, a username and password pair), using user-agent redirections.</p>
			</richtext>
		</abstract>
		<howpublished>Internet RFC 5849</howpublished>
		<title type="sharef:primaryTitle">The OAuth 1.0 Protocol</title>
		<field type="bibtex:topic">oauth[1]</field>
	</reference>
	<reference name="rfc5854" src="bibtex:misc" src-info="bibtex:line-45798" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Anthony</givenname>
				<surname>Bryan</surname>
			</person>
			<person>
				<givenname>Tatsuhiro</givenname>
				<surname>Tsujikawa</surname>
			</person>
			<person>
				<givenname>Neil</givenname>
				<surname>McNab</surname>
			</person>
			<person>
				<givenname>Peter</givenname>
				<surname>Poeml</surname>
			</person>
		</names>
		<date value="2010-06"/>
		<abstract>
			<richtext>
				<p>This document specifies Metalink, an XML-based download description format. Metalink describes download locations (mirrors), cryptographic hashes, and other information. Clients can transparently use this information to reliably transfer files.</p>
			</richtext>
		</abstract>
		<howpublished>Internet RFC 5854</howpublished>
		<title type="sharef:primaryTitle">The Metalink Download Description Format</title>
		<field type="bibtex:topic">metalink[1]</field>
		<field type="bibtex:updates">bry09</field>
	</reference>
	<reference name="rfc5861" src="bibtex:misc" src-info="bibtex:line-45809" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Mark</givenname>
				<surname>Nottingham</surname>
			</person>
		</names>
		<date value="2010-05"/>
		<abstract>
			<richtext>
				<p>This document defines two independent HTTP Cache-Control extensions that allow control over the use of stale responses by caches.</p>
			</richtext>
		</abstract>
		<howpublished>Internet RFC 5861</howpublished>
		<title type="sharef:primaryTitle">HTTP Cache-Control Extensions for Stale Content</title>
		<field type="bibtex:topic">http[1]</field>
	</reference>
	<reference name="rfc5870" src="bibtex:misc" src-info="bibtex:line-45819" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Alexander</givenname>
				<surname>Mayrhofer</surname>
			</person>
			<person>
				<givenname>Christian</givenname>
				<surname>Spanring</surname>
			</person>
		</names>
		<date value="2010-05"/>
		<abstract>
			<richtext>
				<p>This document specifies a Uniform Resource Identifier (URI) for geographic locations using the 'geo' scheme name. A 'geo' URI identifies a physical location in a two- or three-dimensional coordinate reference system in a compact, simple, human-readable, and protocol-independent way. The default coordinate reference system used is the World Geodetic System 1984 (WGS-84).</p>
			</richtext>
		</abstract>
		<howpublished>Internet RFC 5870</howpublished>
		<title type="sharef:primaryTitle">A Uniform Resource Identifier for Geographic Locations ('geo' URI)</title>
		<field type="bibtex:topic">uri[0.8] gps[0.9]</field>
		<field type="bibtex:updates">may09</field>
	</reference>
	<reference name="rfc5890" src="bibtex:misc" src-info="bibtex:line-45830" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>John C.</givenname>
				<surname>Klensin</surname>
			</person>
		</names>
		<date value="2010-08"/>
		<abstract>
			<richtext>
				<p>This document is one of a collection that, together, describe the protocol and usage context for a revision of Internationalized Domain Names for Applications (IDNA), superseding the earlier version. It describes the document collection and provides definitions and other material that are common to the set.</p>
			</richtext>
		</abstract>
		<howpublished>Internet RFC 5890</howpublished>
		<title type="sharef:primaryTitle">Internationalized Domain Names for Applications (IDNA): Definitions and Document Framework</title>
		<field type="bibtex:topic">idna[1] idn[0.9]</field>
		<field type="bibtex:updates">rfc3490</field>
	</reference>
	<reference name="rfc5891" src="bibtex:misc" src-info="bibtex:line-45841" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>John C.</givenname>
				<surname>Klensin</surname>
			</person>
		</names>
		<date value="2010-08"/>
		<abstract>
			<richtext>
				<p>This document is the revised protocol definition for Internationalized Domain Names (IDNs). The rationale for changes, the relationship to the older specification, and important terminology are provided in other documents. This document specifies the protocol mechanism, called Internationalized Domain Names in Applications (IDNA), for registering and looking up IDNs in a way that does not require changes to the DNS itself. IDNA is only meant for processing domain names, not free text.</p>
			</richtext>
		</abstract>
		<howpublished>Internet RFC 5891</howpublished>
		<title type="sharef:primaryTitle">Internationalized Domain Names in Applications (IDNA): Protocol</title>
		<field type="bibtex:topic">idna[1] idn[0.9]</field>
		<field type="bibtex:updates">rfc3490 rfc3491 rfc3492</field>
	</reference>
	<reference name="rfc5892" src="bibtex:misc" src-info="bibtex:line-45852" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Patrik</givenname>
				<surname>Faltstrom</surname>
			</person>
		</names>
		<date value="2010-08"/>
		<abstract>
			<richtext>
				<p>This document specifies rules for deciding whether a code point, considered in isolation or in context, is a candidate for inclusion in an Internationalized Domain Name (IDN). It is part of the specification of Internationalizing Domain Names in Applications 2008 (IDNA2008).</p>
			</richtext>
		</abstract>
		<howpublished>Internet RFC 5892</howpublished>
		<title type="sharef:primaryTitle">The Unicode Code Points and Internationalized Domain Names for Applications (IDNA)</title>
		<field type="bibtex:topic">idna[1] idn[0.9]</field>
	</reference>
	<reference name="rfc5893" src="bibtex:misc" src-info="bibtex:line-45862" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Harald Tveit</givenname>
				<surname>Alvestrand</surname>
			</person>
			<person>
				<givenname>Cary</givenname>
				<surname>Karp</surname>
			</person>
		</names>
		<date value="2010-08"/>
		<abstract>
			<richtext>
				<p>The use of right-to-left scripts in Internationalized Domain Names (IDNs) has presented several challenges. This memo provides a new Bidi rule for Internationalized Domain Names for Applications (IDNA) labels, based on the encountered problems with some scripts and some shortcomings in the 2003 IDNA Bidi criterion.</p>
			</richtext>
		</abstract>
		<howpublished>Internet RFC 5893</howpublished>
		<title type="sharef:primaryTitle">Right-to-Left Scripts for Internationalized Domain Names for Applications (IDNA)</title>
		<field type="bibtex:topic">idna[1] idn[0.9]</field>
	</reference>
	<reference name="rfc5894" src="bibtex:misc" src-info="bibtex:line-45872" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>John C.</givenname>
				<surname>Klensin</surname>
			</person>
		</names>
		<date value="2010-08"/>
		<abstract>
			<richtext>
				<p>Several years have passed since the original protocol for Internationalized Domain Names (IDNs) was completed and deployed. During that time, a number of issues have arisen, including the need to update the system to deal with newer versions of Unicode. Some of these issues require tuning of the existing protocols and the tables on which they depend. This document provides an overview of a revised system and provides explanatory material for its components.</p>
			</richtext>
		</abstract>
		<howpublished>Internet RFC 5894</howpublished>
		<title type="sharef:primaryTitle">Internationalized Domain Names for Applications (IDNA): Background, Explanation, and Rationale</title>
		<field type="bibtex:topic">idna[1] idn[0.9]</field>
	</reference>
	<reference name="rfc5955" src="bibtex:misc" src-info="bibtex:line-45882" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Adriano</givenname>
				<surname>Santoni</surname>
			</person>
		</names>
		<date value="2010-08"/>
		<abstract>
			<richtext>
				<p>This document defines a new media type for TimeStampedData envelopes as described in RFC 5544.</p>
			</richtext>
		</abstract>
		<howpublished>Internet RFC 5955</howpublished>
		<title type="sharef:primaryTitle">The application/timestamped-data Media Type</title>
		<field type="bibtex:updates">rfc5544</field>
	</reference>
	<reference name="rfc5967" src="bibtex:misc" src-info="bibtex:line-45892" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Sean</givenname>
				<surname>Turner</surname>
			</person>
		</names>
		<date value="2010-08"/>
		<abstract>
			<richtext>
				<p>This document specifies a media type used to carry PKCS #10 certification requests as defined in RFC 2986. It carries over the original specification from RFC 2311, which recently has been moved to Historic status, and properly links it to RFC 2986.</p>
			</richtext>
		</abstract>
		<howpublished>Internet RFC 5967</howpublished>
		<title type="sharef:primaryTitle">The application/pkcs10 Media Type</title>
		<field type="bibtex:topic">pkcs[0.9]</field>
		<field type="bibtex:updates">rfc2311 rfc2986</field>
	</reference>
	<reference name="rfc5985" src="bibtex:misc" src-info="bibtex:line-45903" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Martin</givenname>
				<surname>Thomson</surname>
			</person>
			<person>
				<givenname>James</givenname>
				<surname>Winterbottom</surname>
			</person>
		</names>
		<date value="2010-09"/>
		<abstract>
			<richtext>
				<p>This document defines a Layer 7 Location Configuration Protocol (L7 LCP) and describes the use of HTTP and HTTP/TLS as transports for the L7 LCP. The L7 LCP is used for retrieving location information from a server within an access network. It includes options for retrieving location information in two forms: by value and by reference. The protocol is an extensible application-layer protocol that is independent of the session layer.</p>
			</richtext>
		</abstract>
		<howpublished>Internet RFC 5985</howpublished>
		<title type="sharef:primaryTitle">HTTP Enabled Location Delivery (HELD)</title>
		<field type="bibtex:topic">held[1]</field>
		<field type="bibtex:updates">bar07</field>
	</reference>
	<reference name="rfc5986" src="bibtex:misc" src-info="bibtex:line-45914" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Mary</givenname>
				<surname>Barnes</surname>
			</person>
		</names>
		<date value="2010-09"/>
		<abstract>
			<richtext>
				<p>Discovery of the correct Location Information Server (LIS) in the local access network is necessary for Devices that wish to acquire location information from the network. A method is described for the discovery of a LIS in the access network serving a Device. Dynamic Host Configuration Protocol (DHCP) options for IP versions 4 and 6 are defined that specify a domain name. This domain name is then used as input to a URI-enabled NAPTR (U-NAPTR) resolution process.</p>
			</richtext>
		</abstract>
		<howpublished>Internet RFC 5986</howpublished>
		<title type="sharef:primaryTitle">Discovering the Local Location Information Server (LIS)</title>
	</reference>
	<reference name="rfc5987" src="bibtex:misc" src-info="bibtex:line-45923" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Julian F.</givenname>
				<surname>Reschke</surname>
			</person>
		</names>
		<date value="2010-08"/>
		<abstract>
			<richtext>
				<p>By default, message header field parameters in Hypertext Transfer Protocol (HTTP) messages cannot carry characters outside the ISO-8859-1 character set. RFC 2231 defines an encoding mechanism for use in Multipurpose Internet Mail Extensions (MIME) headers. This document specifies an encoding suitable for use in HTTP header fields that is compatible with a profile of the encoding defined in RFC 2231.</p>
			</richtext>
		</abstract>
		<howpublished>Internet RFC 5987</howpublished>
		<title type="sharef:primaryTitle">Character Set and Language Encoding for Hypertext Transfer Protocol (HTTP) Header Field Parameters</title>
		<field type="bibtex:topic">http[1]</field>
	</reference>
	<reference name="rfc5988" src="bibtex:misc" src-info="bibtex:line-45933" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Mark</givenname>
				<surname>Nottingham</surname>
			</person>
		</names>
		<date value="2010-10"/>
		<abstract>
			<richtext>
				<p>This document specifies relation types for Web links, and defines a registry for them. It also defines the use of such links in HTTP headers with the Link header field.</p>
			</richtext>
		</abstract>
		<howpublished>Internet RFC 5988</howpublished>
		<title type="sharef:primaryTitle">Web Linking</title>
		<field type="bibtex:topic">http[1]</field>
		<field type="bibtex:updates">not08 rfc4287</field>
	</reference>
	<reference name="rfc5989" src="bibtex:misc" src-info="bibtex:line-45944" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Adam</givenname>
				<surname>Roach</surname>
			</person>
		</names>
		<date value="2010-10"/>
		<abstract>
			<richtext>
				<p>The Session Initiation Protocol (SIP) is increasingly being used in systems that are tightly coupled with Hypertext Transport Protocol (HTTP) servers for a variety of reasons. In many of these cases, applications can benefit from being able to discover, in near real-time, when a specific HTTP resource is created, changed, or deleted. This document proposes a mechanism, based on the SIP Event Framework, for doing so.</p>
			</richtext>
		</abstract>
		<howpublished>Internet RFC 5989</howpublished>
		<title type="sharef:primaryTitle">A SIP Event Package for Subscribing to Changes to an HTTP Resource</title>
		<field type="bibtex:topic">http[0.9] sip[0.9]</field>
	</reference>
	<reference name="rfc5995" src="bibtex:misc" src-info="bibtex:line-45954" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Julian F.</givenname>
				<surname>Reschke</surname>
			</person>
		</names>
		<date value="2010-09"/>
		<abstract>
			<richtext>
				<p>The Hypertext Transfer Protocol (HTTP) Extensions for the Web Distributed Authoring and Versioning (WebDAV) do not define the behavior for the "POST" method when applied to collections, as the base specification (HTTP) leaves implementers lots of freedom for the semantics of "POST". This has led to a situation where many WebDAV servers do not implement POST for collections at all, although it is well suited to be used for the purpose of adding new members to a collection, where the server remains in control of the newly assigned URL. In fact, the Atom Publishing Protocol (AtomPub) uses POST exactly for that purpose. On the other hand, WebDAV-based protocols, such as the Calendaring Extensions to WebDAV (CalDAV), frequently require clients to pick a unique URL, although the server could easily perform that task. This specification defines a discovery mechanism through which servers can advertise support for POST requests with the aforementioned "add collection member" semantics.</p>
			</richtext>
		</abstract>
		<howpublished>Internet RFC 5995</howpublished>
		<title type="sharef:primaryTitle">Using POST to Add Members to Web Distributed Authoring and Versioning (WebDAV) Collections</title>
		<field type="bibtex:topic">http[0.9] webdav[1]</field>
	</reference>
	<reference name="6047" src="bibtex:misc" src-info="bibtex:line-45964" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Alexey</givenname>
				<surname>Melnikov</surname>
			</person>
		</names>
		<date value="2010-12"/>
		<abstract>
			<richtext>
				<p>This document, "iCalendar Message-Based Interoperability Protocol (iMIP)", specifies a binding from the iCalendar Transport-independent Interoperability Protocol (iTIP) to Internet email-based transports. Calendaring entries defined by the iCalendar Object Model (iCalendar) are wrapped using constructs from RFC 5322 and MIME (RFC 2045, RFC 2046, RFC 2047, and RFC 2049), and then transported over SMTP.</p>
			</richtext>
		</abstract>
		<howpublished>Internet RFC 6047</howpublished>
		<title type="sharef:primaryTitle">iCalendar Message-Based Interoperability Protocol (iMIP)</title>
		<field type="bibtex:topic">icalendar[0.9] itip[0.9] imip[1]</field>
		<field type="bibtex:updates">rfc2447</field>
	</reference>
	<reference name="rfc6068" src="bibtex:misc" src-info="bibtex:line-45975" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Martin</givenname>
				<surname>Duerst</surname>
			</person>
			<person>
				<givenname>Larry</givenname>
				<surname>Masinter</surname>
			</person>
			<person>
				<givenname>Jamie</givenname>
				<surname>Zawinski</surname>
			</person>
		</names>
		<date value="2010-10"/>
		<abstract>
			<richtext>
				<p>This document defines the format of Uniform Resource Identifiers (URIs) to identify resources that are reached using Internet mail. It adds better internationalization and compatibility with Internationalized Resource Identifiers (IRIs; RFC 3987) to the previous syntax of 'mailto' URIs (RFC 2368).</p>
			</richtext>
		</abstract>
		<howpublished>Internet RFC 6068</howpublished>
		<title type="sharef:primaryTitle">The mailto URL scheme</title>
		<field type="bibtex:topic">url[0.8]</field>
		<field type="bibtex:updates">due08 rfc2368</field>
	</reference>
	<reference name="rfc6120" src="bibtex:misc" src-info="bibtex:line-45986" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Peter</givenname>
				<surname>Saint-Andre</surname>
			</person>
		</names>
		<date value="2011-03"/>
		<abstract>
			<richtext>
				<p>The Extensible Messaging and Presence Protocol (XMPP) is an application profile of the Extensible Markup Language (XML) that enables the near-real-time exchange of structured yet extensible data between any two or more network entities. This document defines XMPP's core protocol methods: setup and teardown of XML streams, channel encryption, authentication, error handling, and communication primitives for messaging, network availability ("presence"), and request-response interactions. This document obsoletes RFC 3920.</p>
			</richtext>
		</abstract>
		<howpublished>Internet RFC 6120</howpublished>
		<title type="sharef:primaryTitle">Extensible Messaging and Presence Protocol (XMPP): Core</title>
		<field type="bibtex:topic">xmpp[1]</field>
		<field type="bibtex:updates">rfc3920</field>
	</reference>
	<reference name="rfc6121" src="bibtex:misc" src-info="bibtex:line-45997" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Peter</givenname>
				<surname>Saint-Andre</surname>
			</person>
		</names>
		<date value="2011-03"/>
		<abstract>
			<richtext>
				<p>This document defines extensions to core features of the Extensible Messaging and Presence Protocol (XMPP) that provide basic instant messaging (IM) and presence functionality in conformance with the requirements in RFC 2779. This document obsoletes RFC 3921.</p>
			</richtext>
		</abstract>
		<howpublished>Internet RFC 6121</howpublished>
		<title type="sharef:primaryTitle">Extensible Messaging and Presence Protocol (XMPP): Instant Messaging and Presence</title>
		<field type="bibtex:topic">xmpp[1]</field>
		<field type="bibtex:updates">rfc3921</field>
	</reference>
	<reference name="rfc6122" src="bibtex:misc" src-info="bibtex:line-46008" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Peter</givenname>
				<surname>Saint-Andre</surname>
			</person>
		</names>
		<date value="2011-03"/>
		<abstract>
			<richtext>
				<p>This document defines the format for addresses used in the Extensible Messaging and Presence Protocol (XMPP), including support for non-ASCII characters. This document updates RFC 3920.</p>
			</richtext>
		</abstract>
		<howpublished>Internet RFC 6122</howpublished>
		<title type="sharef:primaryTitle">Extensible Messaging and Presence Protocol (XMPP): Address Format</title>
		<field type="bibtex:topic">xmpp[1]</field>
		<field type="bibtex:updates">rfc3920</field>
	</reference>
	<reference name="rfc6176" src="bibtex:misc" src-info="bibtex:line-46019" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Sean</givenname>
				<surname>Turner</surname>
			</person>
			<person>
				<givenname>Tim</givenname>
				<surname>Polk</surname>
			</person>
		</names>
		<date value="2011-03"/>
		<abstract>
			<richtext>
				<p>This document requires that when Transport Layer Security (TLS) clients and servers establish connections, they never negotiate the use of Secure Sockets Layer (SSL) version 2.0. This document updates the backward compatibility sections found in the Transport Layer Security (TLS).</p>
			</richtext>
		</abstract>
		<howpublished>Internet RFC 6176</howpublished>
		<title type="sharef:primaryTitle">Prohibiting Secure Sockets Layer (SSL) Version 2.0</title>
		<field type="bibtex:topic">tls[1] ssl[1]</field>
		<field type="bibtex:updates">rfc2246 rfc4346 rfc5246</field>
	</reference>
	<reference name="rfc6202" src="bibtex:misc" src-info="bibtex:line-46030" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Salvatore</givenname>
				<surname>Loreto</surname>
			</person>
			<person>
				<givenname>Peter</givenname>
				<surname>Saint-Andre</surname>
			</person>
			<person>
				<givenname>Stefano</givenname>
				<surname>Salsano</surname>
			</person>
			<person>
				<givenname>Greg</givenname>
				<surname>Wilkins</surname>
			</person>
		</names>
		<date value="2011-04"/>
		<abstract>
			<richtext>
				<p>On today's Internet, the Hypertext Transfer Protocol (HTTP) is often used (some would say abused) to enable asynchronous, "server- initiated" communication from a server to a client as well as communication from a client to a server. This document describes known issues and best practices related to such "bidirectional HTTP" applications, focusing on the two most common mechanisms: HTTP long polling and HTTP streaming.</p>
			</richtext>
		</abstract>
		<howpublished>Internet RFC 6202</howpublished>
		<title type="sharef:primaryTitle">Known Issues and Best Practices for the Use of Long Polling and Streaming in Bidirectional HTTP</title>
		<field type="bibtex:topic">http[0.9]</field>
	</reference>
	<reference name="oaiore" src="bibtex:misc" src-info="bibtex:line-46044" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<surname>Open Archives Initiative</surname>
			</person>
		</names>
		<names type="sharef:editor">
			<person>
				<givenname>Carl</givenname>
				<surname>Lagoze</surname>
			</person>
			<person>
				<givenname>Herbert</givenname>
				<surname>Van de Sompel</surname>
			</person>
		</names>
		<date value="2008-06"/>
		<abstract>
			<richtext>
				<p>Open Archives Initiative Object Reuse and Exchange (OAI-ORE) defines standards for the description and exchange of aggregations of Web resources. This document describes the abstract data model that is the foundation for these standards. This model is conformant with the Architecture of the World Wide Web [Web Architecture] and leverages Named Graphs as a mechanism for encapsulating RDF descriptions about aggregations. This specification is one of several documents comprising the OAI-ORE specification and user guide.</p>
			</richtext>
		</abstract>
		<title type="sharef:primaryTitle">ORE Specification — Abstract Data Model</title>
		<field type="bibtex:topic">oaiore[1]</field>
		<identifier type="sharef:uri">http://www.openarchives.org/ore/0.9/datamodel</identifier>
	</reference>
	<reference name="mets16" src="bibtex:misc" src-info="bibtex:line-46059" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<surname>Digital Library Federation</surname>
			</person>
		</names>
		<date value="2007-09"/>
		<title type="sharef:primaryTitle">Metadata Encoding and Transmission Standard: Primer and Reference Manual</title>
		<field type="bibtex:topic">mets[1]</field>
		<identifier type="sharef:uri" resourceType="text/html">http://www.loc.gov/standards/mets/mets-schemadocs.html</identifier>
	</reference>
	<reference name="dppa" src="bibtex:misc" src-info="bibtex:line-46072" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<surname>United States Code</surname>
			</person>
		</names>
		<date value="2009-01"/>
		<howpublished>18 USC 2721</howpublished>
		<title type="sharef:primaryTitle">Drivers Privacy Protection Act (DPPA)</title>
		<identifier type="sharef:uri" resourceType="text/html">http://www4.law.cornell.edu/uscode/18/2721.html</identifier>
	</reference>
	<reference name="sox02" src="bibtex:misc" src-info="bibtex:line-46081" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<surname>United States Code</surname>
			</person>
		</names>
		<date value="2002-07"/>
		<howpublished>Codified in Sections 11, 15, 18, 28, and 29 USC</howpublished>
		<title type="sharef:primaryTitle">Sarbanes-Oxley Act of 2002, PL 107-204, 116 Stat 745</title>
		<identifier type="sharef:uri" resourceType="application/pdf">http://files.findlaw.com/news.findlaw.com/cnn/docs/gwbush/sarbanesoxley072302.pdf</identifier>
	</reference>
	<reference name="e911" src="bibtex:misc" src-info="bibtex:line-46090" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<surname>United States Code</surname>
			</person>
		</names>
		<date value="1999-10"/>
		<howpublished>Pub. L. No. 106-81, 113 Stat. 1286</howpublished>
		<title type="sharef:primaryTitle">Wireless Communications and Public Safety Act of 1999 (911 Act)</title>
		<identifier type="sharef:uri">http://thomas.loc.gov/cgi-bin/query/z?c106:H.R.438.IH:</identifier>
	</reference>
	<reference name="d9546ec" src="bibtex:misc" src-info="bibtex:line-46099" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<surname>European Commission</surname>
			</person>
		</names>
		<date value="1995-10"/>
		<howpublished>Directive 95/46/EC</howpublished>
		<title type="sharef:primaryTitle">Protection of Individuals with Regard to the Processing of Personal Data and on the Free Movement of such Data</title>
		<identifier type="sharef:uri">http://eur-lex.europa.eu/LexUriServ/LexUriServ.do?uri=CELEX:31995L0046:EN:NOT</identifier>
	</reference>
	<reference name="vcard21" src="bibtex:misc" src-info="bibtex:line-46112" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<surname>Versit Consortium</surname>
			</person>
		</names>
		<date value="1996-09"/>
		<edition>Version 2.1</edition>
		<title type="sharef:primaryTitle">vCard: The Electronic Business Card</title>
		<field type="bibtex:topic">vcard[1]</field>
		<identifier type="sharef:uri" resourceType="text/plain">http://www.imc.org/pdi/vcard-21.txt</identifier>
	</reference>
	<reference name="marc21" src="bibtex:misc" src-info="bibtex:line-46122" type="bibtex:misc">
		<names type="sharef:author">
			<name>Library of Congress, Network Development and MARC Standards Office</name>
		</names>
		<date value="2003-10"/>
		<edition>Update No. 4</edition>
		<title type="sharef:primaryTitle">MARC 21 Concise Format for Bibliographic Data</title>
		<field type="bibtex:topic">marc21[1] marc[0.9] canmarc[0.9] usmarc[0.9]</field>
		<identifier type="sharef:uri" resourceType="text/html">http://www.loc.gov/marc/marcdocz.html</identifier>
	</reference>
	<reference name="mods20" src="bibtex:misc" src-info="bibtex:line-46132" type="bibtex:misc">
		<names type="sharef:author">
			<name>Library of Congress, Network Development and MARC Standards Office</name>
		</names>
		<date value="2003-02"/>
		<title type="sharef:primaryTitle">Metadata Object Description Schema (MODS) Version 2.0</title>
		<field type="bibtex:topic">mods[1]</field>
		<identifier type="sharef:uri">http://www.loc.gov/standards/mods/</identifier>
	</reference>
	<reference name="mods30" src="bibtex:misc" src-info="bibtex:line-46141" type="bibtex:misc">
		<names type="sharef:author">
			<name>Library of Congress, Network Development and MARC Standards Office</name>
		</names>
		<date value="2003-12"/>
		<title type="sharef:primaryTitle">Metadata Object Description Schema (MODS) Version 3.0</title>
		<field type="bibtex:topic">mods[1]</field>
		<field type="bibtex:updates">mods20</field>
		<identifier type="sharef:uri">http://www.loc.gov/standards/mods/</identifier>
	</reference>
	<reference name="mods31" src="bibtex:misc" src-info="bibtex:line-46151" type="bibtex:misc">
		<names type="sharef:author">
			<name>Library of Congress, Network Development and MARC Standards Office</name>
		</names>
		<date value="2005-07"/>
		<title type="sharef:primaryTitle">Metadata Object Description Schema (MODS) Version 3.1</title>
		<field type="bibtex:topic">mods[1]</field>
		<field type="bibtex:updates">mods30</field>
		<identifier type="sharef:uri">http://www.loc.gov/standards/mods/</identifier>
	</reference>
	<reference name="set" src="bibtex:misc" src-info="bibtex:line-46161" type="bibtex:misc">
		<names type="sharef:author">
			<name>Secure Electronic Transaction LLC</name>
		</names>
		<date value="1997-05"/>
		<title type="sharef:primaryTitle">SET Secure Electronic Transaction Specification — Version 1.0</title>
		<field type="bibtex:topic">set[1]</field>
		<identifier type="sharef:uri">http://www.setco.org</identifier>
	</reference>
	<reference name="newsml12" src="bibtex:misc" src-info="bibtex:line-46170" type="bibtex:misc">
		<names type="sharef:author">
			<name>International Press Telecommunications Council</name>
		</names>
		<date value="2003-10"/>
		<title type="sharef:primaryTitle">NewsML Version 1.2 — Functional Specification</title>
		<field type="bibtex:topic">newsml[1]</field>
		<identifier type="sharef:uri" resourceType="text/html">http://www.newsml.org/IPTC/NewsML/1.2/specification/NewsML_1.2-spec-functionalspec_7.html</identifier>
	</reference>
	<reference name="rddl" src="bibtex:misc" src-info="bibtex:line-46179" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Jonathan</givenname>
				<surname>Borden</surname>
			</person>
			<person>
				<givenname>Tim</givenname>
				<surname>Bray</surname>
			</person>
		</names>
		<date value="2002-02"/>
		<title type="sharef:primaryTitle">Resource Directory Description Language (RDDL)</title>
		<field type="bibtex:topic">rddl[1]</field>
		<identifier type="sharef:uri" resourceType="text/html">http://www.openhealth.org/RDDL/20020218/rddl-20020218.html</identifier>
	</reference>
	<reference name="rddl2" src="bibtex:misc" src-info="bibtex:line-46188" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Jonathan</givenname>
				<surname>Borden</surname>
			</person>
			<person>
				<givenname>Tim</givenname>
				<surname>Bray</surname>
			</person>
		</names>
		<date value="2004-01"/>
		<abstract>
			<richtext>
				<p>This document is a working draft that contains substantial input from the W3C Technical Architecture Group, produced in connection with the work on its issue namespaceDocument-8. It is the consensus of the TAG that RDDL is a suitable format for use as a "Namespace Document", that is to say as a representation yielded by dereferencing a URI in use as an XML Namespace Name. While this document has no official standing, it is the intention of the TAG to seek guidance from the W3C membership and the larger community on the question of whether and how to progress this document and the use of RDDL.</p>
			</richtext>
		</abstract>
		<title type="sharef:primaryTitle">Resource Directory Description Language (RDDL) 2.0</title>
		<field type="bibtex:topic">rddl[1]</field>
		<field type="bibtex:updates">rddl</field>
		<identifier type="sharef:uri" resourceType="text/html">http://www.openhealth.org/RDDL/20040118/rddl-20040118.html</identifier>
	</reference>
	<reference name="rss2" src="bibtex:misc" src-info="bibtex:line-46199" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Dave</givenname>
				<surname>Winer</surname>
			</person>
		</names>
		<date value="2003-07"/>
		<title type="sharef:primaryTitle">RSS 2.0 Specification</title>
		<field type="bibtex:topic">rss2[1]</field>
		<identifier type="sharef:uri">http://blogs.law.harvard.edu/tech/rss</identifier>
	</reference>
	<reference name="xmtp" src="bibtex:misc" src-info="bibtex:line-46208" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<givenname>Jonathan</givenname>
				<surname>Borden</surname>
			</person>
		</names>
		<date value="2001-04"/>
		<title type="sharef:primaryTitle">XML MIME Transformation Protocol (XMTP) — An RDF XML mapping of RFC 822/MIME</title>
		<field type="bibtex:topic">xmtp[1]</field>
		<identifier type="sharef:uri">http://www.openhealth.org/xmtp/xmtp-20010424</identifier>
	</reference>
	<reference name="egms3" src="bibtex:misc" src-info="bibtex:line-46217" type="bibtex:misc">
		<names type="sharef:author">
			<person>
				<surname>Office of the e-Envoy</surname>
			</person>
		</names>
		<date value="2004-04-09"/>
		<abstract>
			<richtext>
				<p>The e-Government Metadata Standard lists the elements and refinements that will be used by the public sector to create metadata for information resources. It also gives guidance on the purpose and use of each element. This is version 3.0.</p>
			</richtext>
		</abstract>
		<identifier type="sharef:isbn">0711504563</identifier>
		<title type="sharef:primaryTitle">e-Government Metadata Standard Version 3.0</title>
		<field type="bibtex:topic">egms[1]</field>
		<identifier type="sharef:uri" resourceType="application/pdf">http://www.govtalk.gov.uk/documents/eGovMetadataStandard%2020040429.pdf</identifier>
	</reference>
</bibliography>
