<?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-460" 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-472" 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-485" 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="kil01" src="bibtex:article" src-info="bibtex:line-502" 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-520" 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-536" 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-549" 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-566" 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-580" 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-596" 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-611" 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-630" 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-643" 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-660" 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-678" 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-694" 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="mca06" src="bibtex:article" src-info="bibtex:line-710" 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-722" 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-738" 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-754" 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-771" 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-788" 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-804" 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-821" 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-833" 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-845" 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-857" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Barry</givenname>
				<surname>Brown</surname>
			</person>
			<person>
				<givenname>Abigail</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-873" 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-890" 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-906" 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-922" 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-935" 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-952" 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-964" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Tim</givenname>
				<surname>Kindberg</surname>
			</person>
			<person>
				<givenname>John</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-980" 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-991" 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-1006" 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-1022" 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="fik05" src="bibtex:article" src-info="bibtex:line-1040" 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-1052" 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-1064" 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-1076" 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-1091" 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-1107" 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-1124" 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-1137" 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</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-1155" 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-1169" 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-1186" 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-1205" 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-1218" 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-1231" 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-1246" 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-1262" 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-1281" 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-1299" 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="ber06b" src="bibtex:article" src-info="bibtex:line-1315" 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-1332" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Niels Olof</givenname>
				<surname>Bouvin</surname>
			</person>
			<person>
				<givenname>Bent G.</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-1351" 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-1365" 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-1381" 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-1398" 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-1415" 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-1426" 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-1442" 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-1454" 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-1469" 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-1481" 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-1496" 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-1514" 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-1529" 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-1543" 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-1557" 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="hyd09" src="bibtex:article" src-info="bibtex:line-1574" 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-1587" 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-1601" 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-1612" 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-1627" 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-1640" 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-1653" 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-1671" 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-1686" 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-1698" 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-1714" 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-1724" 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-1734" 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-1745" 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-1755" 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-1765" 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-1775" 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-1785" 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-1795" 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-1805" 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-1815" 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-1825" 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-1835" 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-1845" 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-1855" 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-1865" 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-1875" 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-1885" 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-1896" 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-1906" 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-1916" 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-1926" 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-1936" 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-1946" 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-1958" 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-1970" 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-1982" 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-1992" 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-2002" 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-2012" 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-2021" 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-2035" 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-2047" 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-2059" 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-2071" 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-2084" 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-2098" 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-2112" 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-2126" 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-2140" 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-2156" 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-2169" 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-2181" 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-2194" 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-2206" 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-2219" 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-2231" 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-2243" 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-2255" 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-2268" 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-2281" 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-2298" 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>
		<field type="bibtex:src">http://www.informatik.uni-trier.de/~ley/db/journals/acta</field>
		<title type="sharef:primaryTitle">Hierarchical Ordering of Sequential Processes</title>
		<volume>1</volume>
	</reference>
	<reference name="ber02" src="bibtex:article" src-info="bibtex:line-2309" 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>
		<field type="bibtex:src">http://www.springerlink.com/link.asp?id=ldpcelpnd61qe8n3</field>
		<title type="sharef:primaryTitle">Formal Properties of XML Grammars and Languages</title>
		<field type="bibtex:topic">xml[0.8]</field>
		<volume>38</volume>
	</reference>
	<reference name="wan02" src="bibtex:article" src-info="bibtex:line-2326" 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-2345" 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-2363" 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-2376" 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-2389" 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-2405" 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-2423" 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-2441" 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-2457" 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-2473" 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-2487" 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-2506" 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-2517" 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>
		<field type="bibtex:src">http://www.w3journal.com/</field>
		<title type="sharef:primaryTitle">The Evolution of Web Documents: The Ascent of XML</title>
		<field type="bibtex:topic">xml[0.9]</field>
		<volume>2</volume>
	</reference>
	<reference name="car98b" src="bibtex:article" src-info="bibtex:line-2529" 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-2546" 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-2563" 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-2581" 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-2594" 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-2606" 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-2618" 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-2630" 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-2643" 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-2657" 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-2671" 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-2689" 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>
		<field type="bibtex:copied">3.12.93</field>
		<identifier type="sharef:isbn">09259724</identifier>
		<title type="sharef:secondaryTitle">Computer Supported Cooperative Work</title>
		<number>1–2</number>
		<pages>7-40</pages>
		<field type="bibtex:src">EW: 1</field>
		<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-2705" 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:copied">3.12.93</field>
		<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>
		<field type="bibtex:src">EW: 2</field>
		<title type="sharef:primaryTitle">Supporting Cooperative Applications</title>
		<volume>1</volume>
	</reference>
	<reference name="koc96" src="bibtex:article" src-info="bibtex:line-2719" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Michael</givenname>
				<surname>Koch</surname>
			</person>
		</names>
		<date value="1996"/>
		<field type="bibtex:copied">26.3.96</field>
		<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>
		<field type="bibtex:src">EW: 190, EW: ~/papers/bibtex</field>
		<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-2737" 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-2750" 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-2762" 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-2774" 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-2790" 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-2809" 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="wri09" src="bibtex:article" src-info="bibtex:line-2828" 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-2842" 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-2856" 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-2870" 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-2884" 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-2897" 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-2910" 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-2922" 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-2935" 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-2948" 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-2961" 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-2977" 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-2993" 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-3005" 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-3017" 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-3031" 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-3044" 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</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-3056" 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-3068" 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-3082" 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-3096" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Doug</givenname>
				<surname>Lenat</surname>
			</person>
			<person>
				<givenname>George</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-3109" 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-3121" 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-3134" 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-3149" 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-3164" 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-3178" 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-3191" 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-3205" 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-3217" 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-3231" 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-3247" 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-3259" 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-3272" 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-3284" 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-3296" 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-3310" 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-3324" 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-3336" 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-3348" 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-3361" 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-3373" 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-3385" 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-3397" 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-3408" 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-3422" 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-3436" 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-3448" 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-3460" 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-3472" 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-3488" 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-3504" 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-3516" 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-3532" 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-3543" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Rob</givenname>
				<surname>Kling</surname>
			</person>
		</names>
		<date value="1991"/>
		<field type="bibtex:copied">14.12.93</field>
		<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>
		<field type="bibtex:src">EW: 3</field>
		<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-3556" 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"/>
		<field type="bibtex:copied">31.5.94</field>
		<title type="sharef:secondaryTitle">Communications of the ACM</title>
		<number>2</number>
		<pages>64-74</pages>
		<field type="bibtex:src">EW: 27</field>
		<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-3570" 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-3582" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>David R.</givenname>
				<surname>Cheriton</surname>
			</person>
		</names>
		<date value="1988"/>
		<field type="bibtex:copied">3.5.95</field>
		<field type="bibtex:index">V, distributed systems</field>
		<title type="sharef:secondaryTitle">Communications of the ACM</title>
		<number>3</number>
		<pages>314-333</pages>
		<field type="bibtex:src">EW: 110</field>
		<title type="sharef:primaryTitle">The V Distributed System</title>
		<volume>31</volume>
	</reference>
	<reference name="ell91" src="bibtex:article" src-info="bibtex:line-3595" 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:copied">3.5.95</field>
		<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>
		<field type="bibtex:src">EW: 111</field>
		<title type="sharef:primaryTitle">Groupware — Some Issues and Experiences</title>
		<volume>34</volume>
	</reference>
	<reference name="bir82" src="bibtex:article" src-info="bibtex:line-3608" 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:copied">3.5.95</field>
		<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>
		<field type="bibtex:src">EW: 112</field>
		<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-3621" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Kenneth P.</givenname>
				<surname>Birman</surname>
			</person>
		</names>
		<date value="1993"/>
		<field type="bibtex:copied">17.11.95</field>
		<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>
		<field type="bibtex:src">EW: 176</field>
		<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-3634" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Hans</givenname>
				<surname>Eriksson</surname>
			</person>
		</names>
		<date value="1994"/>
		<field type="bibtex:copied">22.3.96</field>
		<field type="bibtex:index">mbone</field>
		<title type="sharef:secondaryTitle">Communications of the ACM</title>
		<number>8</number>
		<pages>54-60</pages>
		<field type="bibtex:src">EW: 188</field>
		<title type="sharef:primaryTitle">MBone: The Multicast Backbone</title>
		<volume>37</volume>
	</reference>
	<reference name="dal78" src="bibtex:article" src-info="bibtex:line-3647" 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-3657" 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-3671" 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="wil07a" src="bibtex:article" src-info="bibtex:line-3689" 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-3702" 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-3714" 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-3726" 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-3738" 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-3754" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Adelino</givenname>
				<surname>Santos</surname>
			</person>
		</names>
		<date value="1993"/>
		<field type="bibtex:copied">26.3.96</field>
		<field type="bibtex:index">CoMEdiA</field>
		<title type="sharef:secondaryTitle">Journal of Computer Science and Technology</title>
		<number>3</number>
		<pages>257-269</pages>
		<field type="bibtex:src">EW: 191</field>
		<title type="sharef:primaryTitle">Cooperative Hypermedia Editing with CoMEdiA</title>
		<volume>8</volume>
	</reference>
	<reference name="pen01" src="bibtex:article" src-info="bibtex:line-3771" 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-3783" 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="phe00b" src="bibtex:article" src-info="bibtex:line-3799" 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-3810" 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-3823" 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-3836" 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-3849" 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-3860" 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-3871" 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-3883" 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-3895" 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-3907" 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-3919" 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-3932" 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-3948" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Adelino</givenname>
				<surname>Santos</surname>
			</person>
		</names>
		<date value="1993"/>
		<field type="bibtex:copied">26.3.96</field>
		<field type="bibtex:index">CoMEdiA</field>
		<title type="sharef:secondaryTitle">Computers and Graphics Magazine</title>
		<number>3</number>
		<pages>261-268</pages>
		<field type="bibtex:src">EW: 192</field>
		<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-3965" 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-3982" 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>M.</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>
		<field type="bibtex:src">EW: ~/papers/bibtex</field>
		<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-3994" 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-4013" 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:copied">26.3.96</field>
		<field type="bibtex:index">DistEdit, groupware, collaborative editing</field>
		<title type="sharef:secondaryTitle">Computing Systems</title>
		<number>2</number>
		<pages>135-166</pages>
		<field type="bibtex:src">EW: 194</field>
		<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-4030" 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-4046" 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-4063" 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-4082" 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:copied">3.5.95</field>
		<field type="bibtex:index">DMIS, multicast</field>
		<title type="sharef:secondaryTitle">The Computer Journal</title>
		<number>3</number>
		<pages>252-261</pages>
		<field type="bibtex:src">EW: 113</field>
		<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-4099" 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-4110" 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-4121" 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-4138" 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-4155" 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-4169" 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-4183" 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-4197" 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-4211" 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-4225" 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</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-4239" 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-4253" 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-4267" 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-4280" 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-4297" 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-4310" 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-4328" 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-4346" 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-4363" 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-4377" 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-4394" 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-4408" 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-4424" 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-4439" 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-4455" 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-4469" 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-4481" 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:copied">11.4.95</field>
		<field type="bibtex:index">MICA</field>
		<title type="sharef:secondaryTitle">IEEE Transactions on Communications</title>
		<number>12</number>
		<pages>1875-1885</pages>
		<field type="bibtex:src">EW: 76</field>
		<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-4494" 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:copied">11.4.95</field>
		<field type="bibtex:index">MICA</field>
		<title type="sharef:secondaryTitle">IEEE Transactions on Communications</title>
		<number>11</number>
		<pages>1698-1708</pages>
		<field type="bibtex:src">EW: 77</field>
		<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-4511" 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="zha02" src="bibtex:article" src-info="bibtex:line-4528" 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-4541" 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-4553" 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-4565" 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:copied">14.6.95</field>
		<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>
		<field type="bibtex:src">EW: 156</field>
		<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-4578" 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:copied">3.5.95</field>
		<field type="bibtex:index">ATM, IP, multicast, LAN</field>
		<title type="sharef:secondaryTitle">IEEE Communications Magazine</title>
		<number>8</number>
		<pages>52-59</pages>
		<field type="bibtex:src">EW: 105</field>
		<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-4591" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>William J.</givenname>
				<surname>Clark</surname>
			</person>
		</names>
		<date value="1992"/>
		<field type="bibtex:copied">11.4.95</field>
		<field type="bibtex:index">MIAC, MIAS, ISDN</field>
		<title type="sharef:secondaryTitle">IEEE Communications Magazine</title>
		<number>5</number>
		<pages>44-50</pages>
		<field type="bibtex:src">EW: 75</field>
		<title type="sharef:primaryTitle">Multipoint Multimedia Conferencing</title>
		<volume>30</volume>
	</reference>
	<reference name="hel78" src="bibtex:article" src-info="bibtex:line-4604" 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-4623" 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-4635" 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-4648" 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-4660" 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-4672" 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-4684" 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="she07" src="bibtex:article" src-info="bibtex:line-4700" 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-4713" 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-4726" 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-4738" 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-4750" 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-4763" 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-4776" 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-4788" 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-4802" 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-4818" 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-4831" 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-4844" 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-4859" 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-4874" 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-4887" 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-4899" 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-4912" 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-4926" 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-4939" 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-4952" 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-4965" 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-4978" 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-4992" 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</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-5004" 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-5017" 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-5032" 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-5044" 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-5058" 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-5073" 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-5092" 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-5106" 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="wei06" src="bibtex:article" src-info="bibtex:line-5120" 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-5134" 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-5151" 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-5161" 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-5171" 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-5185" 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-5198" 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-5215" 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:copied">25.8.96</field>
		<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>
		<field type="bibtex:src">EW: 203, EW: ~/papers/bibtex</field>
		<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-5228" 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>M.</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-5246" 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-5258" 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-5274" 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>
		<field type="bibtex:src">EW: ~/papers/bibtex</field>
		<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-5285" 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:copied">6.4.95</field>
		<field type="bibtex:index">JVTOS, CIO</field>
		<title type="sharef:secondaryTitle">IEEE/ACM Transactions on Networking</title>
		<number>1</number>
		<pages>51-62</pages>
		<field type="bibtex:src">EW: 58</field>
		<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-5298" 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:copied">8.6.95</field>
		<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>
		<field type="bibtex:src">EW: 150</field>
		<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-5315" 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-5328" 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-5341" 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-5354" 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</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-5369" 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-5384" 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-5398" 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-5415" 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-5427" 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>
		<field type="bibtex:src">EW: ~/papers/bibtex</field>
		<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-5438" 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:copied">7.4.95</field>
		<field type="bibtex:index">open document processing, SGML, ODA</field>
		<title type="sharef:secondaryTitle">Computer Networks and ISDN Systems</title>
		<pages>149-163</pages>
		<field type="bibtex:src">EW: 62</field>
		<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-5450" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Andy</givenname>
				<surname>Spiceley</surname>
			</person>
		</names>
		<date value="1991"/>
		<field type="bibtex:copied">7.4.95</field>
		<field type="bibtex:index">ODA profiles, interworking</field>
		<title type="sharef:secondaryTitle">Computer Networks and ISDN Systems</title>
		<pages>165-173</pages>
		<field type="bibtex:src">EW: 63</field>
		<title type="sharef:primaryTitle">ODA profiles: application and development</title>
		<volume>21</volume>
	</reference>
	<reference name="nel91" src="bibtex:article" src-info="bibtex:line-5462" 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>M.</givenname>
				<surname>Mabrouk</surname>
			</person>
		</names>
		<date value="1991"/>
		<field type="bibtex:copied">7.4.95</field>
		<field type="bibtex:index">ODA, PODA, API, toolkit</field>
		<title type="sharef:secondaryTitle">Computer Networks and ISDN Systems</title>
		<pages>175-185</pages>
		<field type="bibtex:src">EW: 64</field>
		<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-5474" 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:copied">7.4.95</field>
		<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>
		<field type="bibtex:src">EW: 65</field>
		<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-5486" 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:copied">7.4.95</field>
		<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>
		<field type="bibtex:src">EW: 66</field>
		<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-5498" 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:copied">7.4.95</field>
		<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>
		<field type="bibtex:src">EW: 67</field>
		<title type="sharef:primaryTitle">Some comments on using ODA</title>
		<volume>21</volume>
	</reference>
	<reference name="col91" src="bibtex:article" src-info="bibtex:line-5510" 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:copied">7.4.95</field>
		<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>
		<field type="bibtex:src">EW: 68</field>
		<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-5522" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Bohdan</givenname>
				<surname>Smetaniuk</surname>
			</person>
		</names>
		<date value="1991"/>
		<field type="bibtex:copied">7.4.95</field>
		<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>
		<field type="bibtex:src">EW: 59</field>
		<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-5534" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Hannes P.</givenname>
				<surname>Lubich</surname>
			</person>
		</names>
		<date value="1990"/>
		<field type="bibtex:copied">29.3.95</field>
		<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>
		<field type="bibtex:src">EW: 195</field>
		<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-5546" 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>
		<field type="bibtex:src">EW: ~/papers/bibtex</field>
		<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-5562" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Mike</givenname>
				<surname>Robinson</surname>
			</person>
		</names>
		<date value="1991"/>
		<field type="bibtex:copied">22.12.93</field>
		<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>
		<field type="bibtex:src">EW: 7</field>
		<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-5579" 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-5594" 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-5609" 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-5623" 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-5642" 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-5653" 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-5669" 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-5687" 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-5700" 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-5717" 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-5731" 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-5745" 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-5756" 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:copied">2.2.94</field>
		<field type="bibtex:index">ORION-2</field>
		<title type="sharef:secondaryTitle">ACM Transactions on Information Systems</title>
		<number>1</number>
		<pages>31-51</pages>
		<field type="bibtex:src">EW: 11</field>
		<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-5769" 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:copied">2.2.94</field>
		<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>
		<field type="bibtex:src">EW: 10</field>
		<title type="sharef:primaryTitle">Data Sharing in Group Work</title>
		<volume>5</volume>
	</reference>
	<reference name="pet89" src="bibtex:article" src-info="bibtex:line-5786" 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"/>
		<field type="bibtex:copied">2.2.94</field>
		<title type="sharef:secondaryTitle">ACM Transactions on Computer Systems</title>
		<number>3</number>
		<pages>217-246</pages>
		<field type="bibtex:src">EW: 12</field>
		<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-5798" 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-5809" 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-5825" 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-5839" 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-5858" 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-5876" 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="fie02" src="bibtex:article" src-info="bibtex:line-5893" 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-5907" 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-5918" 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-5932" 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-5948" 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-5962" 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-5975" 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-5993" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Lawrence E.</givenname>
				<surname>Hughes</surname>
			</person>
		</names>
		<date value="1988"/>
		<field type="bibtex:copied">30.3.95</field>
		<field type="bibtex:index">multicast, communication primitives</field>
		<title type="sharef:secondaryTitle">Software — Practice &amp; Experience</title>
		<number>3</number>
		<pages>15-27</pages>
		<field type="bibtex:src">EW: 51</field>
		<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-6010" 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-6027" 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-6038" 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-6049" 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-6060" 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-6075" 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-6085" 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-6102" 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-6118" 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-6130" 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-6144" 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-6158" 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-6173" 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-6187" 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-6201" 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-6216" 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-6229" 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-6241" 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-6254" 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-6266" 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-6278" 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-6294" 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-6307" 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-6319" 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>
		<field type="bibtex:src">EW: ~/papers/bibtex</field>
		<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-6332" 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>
		<field type="bibtex:src">EW: ~/papers/bibtex</field>
		<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-6344" 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-6356" 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>
		<field type="bibtex:src">EW: ~/papers/bibtex</field>
		<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-6368" 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>
		<field type="bibtex:src">EW: ~/papers/bibtex</field>
		<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-6380" 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:copied">6.11.96</field>
		<field type="bibtex:index">mbone</field>
		<title type="sharef:secondaryTitle">ACM Computer Communications Review</title>
		<number>3</number>
		<field type="bibtex:src">EW: 207</field>
		<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-6392" 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-6404" 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:copied">2.5.95</field>
		<field type="bibtex:index">multicast</field>
		<title type="sharef:secondaryTitle">ACM Computer Communications Review</title>
		<number>4</number>
		<pages>172-179</pages>
		<field type="bibtex:src">EW: 102</field>
		<title type="sharef:primaryTitle">Host Groups: A Multicast Extension for Datagram Internetworks</title>
		<volume>15</volume>
	</reference>
	<reference name="mil01" src="bibtex:article" src-info="bibtex:line-6421" 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-6435" 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-6447" type="sharef:article">
		<names type="sharef:author">
			<person>
				<givenname>Frank</givenname>
				<surname>Neven</surname>
			</person>
		</names>
		<date valu