Overview of content related to 'rfc' http://www.ariadne.ac.uk/taxonomy/term/1240/all?article-type=&term=&organisation=&project=&author=&issue= RSS feed with Ariadne content related to specified tag en Motivations for the Development of a Web Resource Synchronisation Framework http://www.ariadne.ac.uk/issue70/lewis-et-al <div class="field field-type-text field-field-teaser-article"> <div class="field-items"> <div class="field-item odd"> <p><a href="/issue70/lewis-et-al#author1">Stuart Lewis</a>, <a href="/issue70/lewis-et-al#author2">Richard Jones</a> and <a href="/issue70/lewis-et-al#author3">Simeon Warner</a> explain some of the motivations behind the development of the ResourceSync Framework.</p> </div> </div> </div> <p>This article describes the motivations behind the development of the ResourceSync Framework. The Framework addresses the need to synchronise resources between Web sites. &nbsp;Resources cover a wide spectrum of types, such as metadata, digital objects, Web pages, or data files. &nbsp;There are many scenarios in which the ability to perform some form of synchronisation is required. Examples include aggregators such as Europeana that want to harvest and aggregate collections of resources, or preservation services that wish to archive Web sites as they change.</p> <p><a href="http://www.ariadne.ac.uk/issue70/lewis-et-al" target="_blank">read more</a></p> issue70 tooled up richard jones simeon warner stuart lewis aberystwyth university cornell university imperial college london jisc library of congress niso oai oclc ukoln university of edinburgh university of oxford dbpedia europeana opendoar wikipedia access control aggregation api archives atom cache cataloguing data data management data set database digital library doi dspace dublin core eprints framework ftp higher education html hypertext identifier interoperability knowledge base linked data metadata namespace national library oai-ore oai-pmh open access open archives initiative open source passwords portal portfolio preservation provenance repositories research rfc rss search technology service oriented architecture software sru srw standards sword protocol syndication twitter uri url web app web resources web services xml z39.50 Mon, 03 Dec 2012 15:58:46 +0000 lisrw 2392 at http://www.ariadne.ac.uk What Is a URI and Why Does It Matter? http://www.ariadne.ac.uk/issue65/thompson-hs <div class="field field-type-text field-field-teaser-article"> <div class="field-items"> <div class="field-item odd"> <p><a href="/issue65/thompson-hs#author1">Henry S. Thompson</a> describes how recent developments in Web technology have affected the relationship between URI and resource representation and the related consequences.</p> </div> </div> </div> <p>URI stands for Uniform Resource Identifier, the official name for those things you see all the time on the Web that begin <font face="Courier New, Courier, monospace">'http:'</font> or <font face="Courier New, Courier, monospace">'mailto:'</font>, for example <span class="style1">http://<em>www.w3.org</em>/</span>, which is the URI for the home page of the World Wide Web Consortium [<a href="#1">1</a>]. (These things were called URLs (Uniform Resource Locators) in the early days of the Web, and the change from URL to URI is either hugely significant or completely irrelevant, depending on who is talking—I have nothing to say about this issue in this article. If you have never heard of URIs (or IRIs, the even more recent fully internationalised version), but are familiar with URLs, just think 'URL' whenever you see 'URI' below.)</p> <p>Historically, URIs were mostly seen as simply the way you accessed Web pages. These pages were hand-authored, relatively stable and simply shipped out on demand. More and more often that is no longer the case; in at least three different ways:</p> <ul> <li>Web pages for reading have been complemented by pictures for viewing, videos for watching and music for listening;</li> <li>The Web is now more than a conduit for information, it is a means to a variety of ends; we use it to <em>do</em> things: purchase goods and services, contribute to forums, play games;</li> <li>The things we access on the Web are often not hand-authored or stable, but are automatically synthesised from 'deeper' data sources on demand. Furthermore, that synthesis is increasingly influenced by aspects of the way we initiate the access.</li> </ul> <p>It is against this background that I think it is worth exploring with some care what URIs were meant to be, and how they are being used in practice. In particular, I want to look at what is to be gained from a better understanding of how other kinds of identifiers work.</p> <h2 id="The_Official_Version">The Official Version</h2> <p>Insofar as there are definitive documents about all this, they all agree that URIs are, as the third initial says, <strong>identifiers</strong>, that is, names. They identify <strong>resources</strong>, and often (although not always) allow you to access <strong>representations</strong> of those resources. (Words in <strong>bold</strong> are used as technical terms—their ordinary language meaning is in many cases likely to be more confusing than helpful.)</p> <p>'Resource' names a role in a story, not an intrinsically distinguishable subset of things, just as 'referent' does in ordinary language. Things are resources because someone created a URI to identify them, not because they have some particular properties in and of themselves.</p> <p>'Representation' names a pair: a character sequence and a media type. The <strong>media type</strong> specifies how the character string should be interpreted. For example JPG or HTML or MP3 would be likely media types for representations of an image of an apple, a news report about an orchard or a recording of a Beatles song, respectively.</p> <p></p><p><a href="http://www.ariadne.ac.uk/issue65/thompson-hs" target="_blank">read more</a></p> issue65 feature article henry s. thompson apple google ietf university of edinburgh w3c wikipedia aggregation ajax algorithm browser cataloguing cookie data framework gif google maps html hypertext identifier javascript jpg metadata mp3 png rfc search technology semantic web uri url web 2.0 web app xhtml Fri, 29 Oct 2010 23:00:00 +0000 editor 1589 at http://www.ariadne.ac.uk Abstract Modelling of Digital Identifiers http://www.ariadne.ac.uk/issue62/nicholas-et-al <div class="field field-type-text field-field-teaser-article"> <div class="field-items"> <div class="field-item odd"> <p><a href="/issue62/nicholas-et-al#author1">Nick Nicholas</a>, <a href="/issue62/nicholas-et-al#author2">Nigel Ward</a> and <a href="/issue62/nicholas-et-al#author3">Kerry Blinco</a> present an information model of digital identifiers, to help bring clarity to the vocabulary debates from which this field has suffered.</p> </div> </div> </div> <!-- v2, incorporating author review edits inc. lead-ins to bullet lists - 2010-02-12-19-30-rew--><!-- v2, incorporating author review edits inc. lead-ins to bullet lists - 2010-02-12-19-30-rew--><p>Discussion of digital identifiers, and persistent identifiers in particular, has often been confused by differences in underlying assumptions and approaches. To bring more clarity to such discussions, the PILIN Project has devised an abstract model of identifiers and identifier services, which is presented here in summary. Given such an abstract model, it is possible to compare different identifier schemes, despite variations in terminology; and policies and strategies can be formulated for persistence without committing to particular systems. The abstract model is formal and layered; in this article, we give an overview of the distinctions made in the model. This presentation is not exhaustive, but it presents some of the key concepts represented, and some of the insights that result.</p> <p>The main goal of the Persistent Identifier Linking Infrastructure (PILIN) project [<a href="#1">1</a>] has been to scope the infrastructure necessary for a national persistent identifier service. There are a variety of approaches and technologies already on offer for persistent digital identification of objects. But true identity persistence cannot be bound to particular technologies, domain policies, or information models: any formulation of a persistent identifier strategy needs to outlast current technologies, if the identifiers are to remain persistent in the long term.</p> <p>For that reason, PILIN has modelled the digital identifier space in the abstract. It has arrived at an ontology [<a href="#2">2</a>] and a service model [<a href="#3">3</a>] for digital identifiers, and for how they are used and managed, building on previous work in the identifier field [<a href="#4">4</a>] (including the thinking behind URI [<a href="#5">5</a>], DOI [<a href="#6">6</a>], XRI [<a href="#7">7</a>] and ARK [<a href="#8">8</a>]), as well as semiotic theory [<a href="#9">9</a>]. The ontology, as an abstract model, addresses the question 'what is (and isn't) an identifier?' and 'what does an identifier management system do?'. This more abstract view also brings clarity to the ongoing conversation of whether URIs can be (and should be) universal persistent identifiers.</p> <h2 id="Identifier_Model">Identifier Model</h2> <p>For the identifier model to be abstract, it cannot commit to a particular information model. The notion of an identifier depends crucially on the understanding that an identifier only identifies one distinct thing. But different domains will have different understandings of what things are distinct from each other, and what can legitimately count as a single thing. (This includes aggregations of objects, and different versions or snapshots of objects.) In order for the abstract identifier model to be applicable to all those domains, it cannot impose its own definitions of what things are distinct: it must rely on the distinctions specific to the domain.</p> <p>This means that information modelling is a critical prerequisite to introducing identifiers to a domain, as we discuss elsewhere [<a href="#10">10</a>]: identifier users should be able to tell whether any changes in a thing's content, presentation, or location mean it is no longer identified by the same identifier (i.e. whether the identifier is restricted to a particular version, format, or copy).</p> <p>The abstract identifier model also cannot commit to any particular protocols or service models. In fact, the abstract identifier model should not even presume the Internet as a medium. A sufficiently abstract model of identifiers should apply just as much to URLs as it does to ISBNs, or names of sheep; the model should not be inherently digital, in order to avoid restricting our understanding of identifiers to the current state of digital technologies. This means that our model of identifiers comes close to the understanding in semiotics of signs, as our definitions below make clear.</p> <p>There are two important distinctions between digital identifiers and other signs which we needed to capture. First, identifiers are managed through some system, in order to guarantee the stability of certain properties of the identifier. This is different to other signs, whose meaning is constantly renegotiated in a community. Those identifier properties requiring guarantees include the accountability and persistence of various facets of the identifier—most crucially, what is being identified. For digital identifiers, the <strong>identifier management system</strong> involves registries, accessed through defined services. An HTTP server, a PURL [<a href="#11">11</a>] registry, and an XRI registry are all instances of identifier management systems.</p> <p>Second, digital identifiers are straightforwardly <strong>actionable</strong>: actions can be made to happen in connection with the identifier. Those actions involve interacting with computers, rather than other people: the computer consistently does what the system specifies is to be done with the identifier, and has no latitude for subjective interpretation. This is in contrast with human language, which can involve complex processes of interpretation, and where there can be considerable disconnect between what a speaker intends and how a listener reacts. Because the interactions involved are much simpler, the model can concentrate on two actions which are core to digital identifiers, but which are only part of the picture in human communication: working out what is being identified (<em>resolution</em>), and accessing a representation of what is identified (<em>retrieval</em>).</p> <p>So to model managing and acting on digital identifiers, we need a concept of things that can be identified, names for things, and the relations between them. (Semiotics already gives us such concepts.) We also need a model of the systems through which identifiers are managed and acted on; what those systems do, and who requests them to do so; and what aspects of identifiers the systems manage.</p> <p>Our identifier model (as an ontology) thus encompasses:</p> <ul> <li><strong>Entities</strong> - including actors and identifier systems;</li> <li><strong>Relations</strong> between entities;</li> <li><strong>Qualities</strong>, as desirable properties of entities. Actions are typically undertaken in order to make qualities apply to entities.</li> <li><strong>Actions</strong>, as the processes carried out on entities (and corresponding to <strong>services</strong> in implementations);</li> </ul> <p>An individual identifier system can be modelled using concepts from the ontology, with an identifier system model.</p> <p>In the remainder of this article, we go through the various concepts introduced in the model under these classes. We present the concept definitions under each section, before discussing issues that arise out of them. <em>Resolution</em> and <em>Retrieval</em> are crucial actions for identifiers, whose definition involves distinct issues; they are discussed separately from other Actions. We briefly discuss the standing of HTTP URIs in the model at the end.</p> <p></p><p><a href="http://www.ariadne.ac.uk/issue62/nicholas-et-al" target="_blank">read more</a></p> issue62 feature article kerry blinco nick nicholas nigel ward d-lib magazine dest ietf oasis internet archive aggregation archives ark ascii browser cataloguing cool uri cordra curation data database digital object identifier dns document management doi e-learning ftp identifier infrastructure interoperability learning objects metadata mobile mobile phone namespace ontologies openurl persistent identifier purl repositories research rfc search technology semantic web semiotic service usage model uri url vocabularies wayback machine web browser xml xml namespaces Sat, 30 Jan 2010 00:00:00 +0000 editor 1528 at http://www.ariadne.ac.uk The European Film Gateway http://www.ariadne.ac.uk/issue58/eckes-segbert <div class="field field-type-text field-field-teaser-article"> <div class="field-items"> <div class="field-item odd"> <p><a href="/issue58/eckes-segbert#author1">Georg Eckes</a> and <a href="/issue58/eckes-segbert#author2">Monika Segbert</a> describe a Best Practice Network funded under the eContentplus Programme of the European Commission, which is building a portal for access to film archival resources in Europe.</p> </div> </div> </div> <p>The European Film Gateway (EFG) [<a href="#1">1</a>] is one in a series of projects funded by the European Commission, under the eContent<em>plus</em> Programme, with the aim of contributing to the development and further enhancement of Europeana - the European digital library, museum and archive [<a href="#2">2</a>]. Officially launched on 20 November 2008, the prototype Europeana service provides access to about four million digital objects from archives, audio-visual archives, museums and libraries across Europe.</p> <p><a href="http://www.ariadne.ac.uk/issue58/eckes-segbert" target="_blank">read more</a></p> issue58 feature article georg eckes monika elbert deutsches filminstitut google iso mpeg oai europeana aacr2 accessibility aggregation archives cataloguing cidoc-crm controlled vocabularies copyright crm data database digital library digital media digitisation dublin core ead framework frbr identifier infrastructure intellectual property interoperability metadata oai-pmh open source p/meta portal preservation repositories request for comments research resource description and access rfc schema search technology software sru standardisation standards tagging unicode vocabularies z39.50 Fri, 30 Jan 2009 00:00:00 +0000 editor 1453 at http://www.ariadne.ac.uk Get Tooled Up: SeeAlso: A Simple Linkserver Protocol http://www.ariadne.ac.uk/issue57/voss <div class="field field-type-text field-field-teaser-article"> <div class="field-items"> <div class="field-item odd"> <p><a href="/issue57/voss#author1">Jakob Voss</a> combines OpenSearch and unAPI to enrich catalogues.</p> </div> </div> </div> <!-- 2008-11-11 REW v2 to take in final edits on code fragments, etc --><!-- 2008-11-11 REW v2 to take in final edits on code fragments, etc --><p>In recent years the principle of Service-oriented Architecture (SOA) has grown increasingly important in digital library systems. More and more core functionalities are becoming available in the form of Web-based, standardised services which can be combined dynamically to operate across a broader environment [<a href="#1">1</a>].</p> <p><a href="http://www.ariadne.ac.uk/issue57/voss" target="_blank">read more</a></p> issue57 feature article jakob voss d-lib magazine google ieee oai w3c cpan jisc information environment wikipedia api archives atom bibliographic data blog browser cataloguing cloud computing creative commons csv data database digital library firefox framework html hypertext identifier javascript json library management systems librarything licence lod metadata microformats namespace oai-pmh opac open archives initiative open data open source open standard openurl perl rdf rfc search technology soa software sparql sql sru standards syndication tag cloud uri url web 2.0 web services wiki xml xslt Thu, 30 Oct 2008 00:00:00 +0000 editor 1436 at http://www.ariadne.ac.uk The Networked Library Service Layer: Sharing Data for More Effective Management and Cooperation http://www.ariadne.ac.uk/issue56/gatenby <div class="field field-type-text field-field-teaser-article"> <div class="field-items"> <div class="field-item odd"> <p><a href="/issue56/gatenby#author1">Janifer Gatenby</a> identifies criteria for determining which data in various library systems could be more beneficially shared and managed at a network level.</p> </div> </div> </div> <p><a href="http://www.ariadne.ac.uk/issue56/gatenby" target="_blank">read more</a></p> issue56 feature article janifer gatenby amazon google ietf ifla iso library of congress niso oai oclc worldcat aggregation algorithm archives atom authentication authority data bibliographic data blog cataloguing copyright data data set database digital library digital repositories digitisation framework ftp identifier information retrieval interoperability knowledge base library data library management systems licence marc21 mashup metadata oai-pmh opac open archives initiative openurl portal preservation rdf repositories research resource management rfc rss schema search technology social networks software sru standardisation standards syndication uri url web portal web services z39.50 z39.88 Tue, 29 Jul 2008 23:00:00 +0000 editor 1408 at http://www.ariadne.ac.uk Persistent Identifiers: Considering the Options http://www.ariadne.ac.uk/issue56/tonkin <div class="field field-type-text field-field-teaser-article"> <div class="field-items"> <div class="field-item odd"> <p><a href="/issue56/tonkin#author1">Emma Tonkin</a> looks at the current landscape of persistent identifiers, describes several current services, and examines the theoretical background behind their structure and use.</p> </div> </div> </div> <h2 id="What_Is_a_Persistent_Identifier_and_Why">What Is a Persistent Identifier, and Why?</h2> <p>Persistent identifiers (PIs) are simply maintainable identifiers that allow us to refer to a digital object – a file or set of files, such as an e-print (article, paper or report), an image or an installation file for a piece of software. The only interesting persistent identifiers are also persistently actionable (that is, you can "click" them); however, unlike a simple hyperlink, persistent identifiers are supposed to continue to provide access to the resource, even when it moves to other servers or even to other organisations.</p> <p><a href="http://www.ariadne.ac.uk/issue56/tonkin" target="_blank">read more</a></p> issue56 feature article emma tonkin ansi california digital library cnri darpa ietf iso niso oclc portico ukoln university of bath archives ark bibliographic data blog browser cataloguing content management cool uri data database digital library digital object identifier dissemination dns doi ftp handle system identifier infrastructure licence metadata multimedia naan name mapping authority namespace national library openurl persistent identifier preservation purl request for comments research rfc search technology software standardisation standards unicode uri url urn utf-8 video z39.88 Tue, 29 Jul 2008 23:00:00 +0000 editor 1413 at http://www.ariadne.ac.uk SWORD: Simple Web-service Offering Repository Deposit http://www.ariadne.ac.uk/issue54/allinson-et-al <div class="field field-type-text field-field-teaser-article"> <div class="field-items"> <div class="field-item odd"> <p><a href="/issue54/allinson-et-al#author1">Julie Allinson</a>, <a href="/issue54/allinson-et-al#author2">Sebastien Francois</a> and <a href="/issue54/allinson-et-al#author3">Stuart Lewis</a> describe the JISC-funded SWORD Project which has produced a lightweight protocol for repository deposit.</p> </div> </div> </div> <p><a href="http://www.ariadne.ac.uk/issue54/allinson-et-al" target="_blank">read more</a></p> issue54 feature article julie allinson sebastien francois stuart lewis aberystwyth university cetis jisc microsoft oai oclc open knowledge initiative ukoln university of bath university of southampton university of york jisc information environment repositories research team sword project apache api application profile archives atom authentication blog data data set digital library dissemination dspace eprints facebook fedora commons gif interoperability java jpeg ldap learning objects licence metadata mets namespace oai-ore open access open archives initiative open source osid passwords perl php preservation repositories rfc scholarly works application profile search technology software sru standards sword protocol syndication tagging url web app web resources web services wiki xml zip Wed, 30 Jan 2008 00:00:00 +0000 editor 1366 at http://www.ariadne.ac.uk Introducing UnAPI http://www.ariadne.ac.uk/issue48/chudnov-et-al <div class="field field-type-text field-field-teaser-article"> <div class="field-items"> <div class="field-item odd"> <p><a href="/issue48/chudnov-et-al#author1">Dan Chudnov</a> and a team of colleagues describe unAPI, a tiny HTTP API for serving information objects in next-generation Web applications.</p> </div> </div> </div> <p>Common Web tools and techniques cannot easily manipulate library resources. While photo sharing, link logging, and Web logging sites make it easy to use and reuse content, barriers still exist that limit the reuse of library resources within new Web services. [<a href="#1">1</a>][<a href="#2">2</a>] To support the reuse of library information in Web 2.0-style services, we need to allow many types of applications to connect with our information resources more easily. One such connection is a universal method to copy any resource of interest.</p> <p><a href="http://www.ariadne.ac.uk/issue48/chudnov-et-al" target="_blank">read more</a></p> issue48 feature article dan chudnov ed summers jeremy frumkin michael j. giarlo mike rylander peter binkley ross singer amazon andrew w mellon foundation ansi ciac d-lib magazine georgia institute of technology google library of congress microsoft mpeg national science foundation niso oai oregon state university university of alberta university of washington yale university apache api archives atom bibliographic data blog browser cataloguing data database didl digital library dublin core fedora commons firefox flickr foaf framework google books html identifier interoperability javascript json library management systems metadata microformats mods namespace oai-pmh opac open archives initiative openurl php plain text rdf repositories rfc rss ruby schema search technology software sru srw standards syndication uri url web 2.0 web app web browser web services wiki wordpress xml xslt z39.50 z39.88 Sat, 29 Jul 2006 23:00:00 +0000 editor 1248 at http://www.ariadne.ac.uk Joint Workshop on Future-proofing Institutional Websites http://www.ariadne.ac.uk/issue46/dcc-fpw-rpt <div class="field field-type-text field-field-teaser-article"> <div class="field-items"> <div class="field-item odd"> <p><a href="/issue46/dcc-fpw-rpt#author1">Maureen Pennock</a> reports on a two-day workshop on Future-Proofing Web Sites, organised by the Digital Curation Centre (DCC) and the Wellcome Library at the Wellcome Library, London, over 19-20 January 2006.</p> </div> </div> </div> <!-- 2006-02-16 11:17: error in URL for reference 2 : <a href="http://medphoto.wellcome.ac.uk/" title="http://medphoto.wellcome.ac.uk/">http://medphoto.wellcome.ac.uk/</a> was incorrect:Maureen Pennock forwarded correct URL now in place as embedded link and in ref 2 below REW --><!-- 2006-02-16 11:17: error in URL for reference 2 : <a href="http://medphoto.wellcome.ac.uk/" title="http://medphoto.wellcome.ac.uk/">http://medphoto.wellcome.ac.uk/</a> was incorrect:Maureen Pennock forwarded correct URL now in place as embedded link and in ref 2 below REW --><p>This <a href="http://www.dcc.ac.uk">DCC</a> [<a href="1">1</a>] and <a href="http://library.wellcome.ac.uk/">Wellcome Library</a> [<a href="#2">2</a>] workshop sought to provide insight into ways that content creators and curators can ensure ongoing access to reliable Web sites over time.</p> <p><a href="http://www.ariadne.ac.uk/issue46/dcc-fpw-rpt" target="_blank">read more</a></p> issue46 event report maureen pennock apple british library california digital library dcc eduserv ietf national library of australia the national archives ukoln university of bath university of glasgow wellcome library internet archive uk government web archive accessibility archives ark cataloguing collection development data digital curation digital library digital preservation doi e-government html identifier java metadata national library open source persistent identifier plain text preservation purl research rfc search technology software standards tomcat uri url vocabularies web resources web standards Wed, 08 Feb 2006 00:00:00 +0000 editor 1216 at http://www.ariadne.ac.uk ECDL-2003 Web Archiving http://www.ariadne.ac.uk/issue37/ecdl-web-archiving-rpt <div class="field field-type-text field-field-teaser-article"> <div class="field-items"> <div class="field-item odd"> <p><a href="/issue37/ecdl-web-archiving-rpt#author1">Michael Day</a> reports on the 3rd ECDL Workshop on Web Archives held in Trondheim, August 2003.</p> </div> </div> </div> <p>On 21 August 2003, the 3rd ECDL Workshop on Web Archives [<a href="#1">1</a>] [<a href="#2">2</a>] was held in Trondheim, Norway in association with the 7th European Conference on Digital Libraries (ECDL) [<a href="#3">3</a>]. This event was the third in a series of annual workshops that have been held in association with the ECDL conferences held in Darmstadt [<a href="#4">4</a>] and Rome [<a href="#5">5</a>].</p> <p><a href="http://www.ariadne.ac.uk/issue37/ecdl-web-archiving-rpt" target="_blank">read more</a></p> issue37 event report michael day bnf california digital library d-lib magazine ietf ifla library of congress national library of new zealand the national archives ukoln university of bath university of lisbon internet archive archives ark bibliographic data cataloguing data database digital archive digital library digital preservation document format electronic theses frbr html identifier metadata mets mods naan name mapping authority national library persistent identifier portal preservation repositories research rfc schema search technology software url urn usability web browser xml xml schema Thu, 30 Oct 2003 00:00:00 +0000 editor 1637 at http://www.ariadne.ac.uk Metadata: I Am a Name and a Number http://www.ariadne.ac.uk/issue24/metadata <div class="field field-type-text field-field-teaser-article"> <div class="field-items"> <div class="field-item odd"> <p><a href="/issue24/metadata#author1">Paul Miller</a> on Digital Object Identifiers.</p> </div> </div> </div> <p>People, places, and things are identified in any number of different ways.</p> <p><a href="http://www.ariadne.ac.uk/issue24/metadata" target="_blank">read more</a></p> issue24 regular column paul miller amazon bbc cnri d-lib magazine ifla jisc ukoln university of hull aardvark dner bibliographic data browser cataloguing database digital object identifier doi frbr handle system identifier intellectual property interoperability metadata mobile mobile phone persistent identifier portal research rfc solaris standards uri url web browser windows Thu, 22 Jun 2000 23:00:00 +0000 editor 712 at http://www.ariadne.ac.uk Web Mirrors: Building the UK Mirror Service http://www.ariadne.ac.uk/issue22/web-mirror <div class="field field-type-text field-field-teaser-article"> <div class="field-items"> <div class="field-item odd"> <p>Report on the UK Mirror Service by <a href="/issue22/web-mirror#author1">Mark Russell</a>.</p> </div> </div> </div> <p>On 1st August 1999 the UK Mirror Service <a href="#ukms">[1]</a> replaced HENSA as the JISC <a href="#jisc">[2]</a> funded mirror service for the UK academic community. The new service is run by the same teams at Kent and Lancaster that supported the HENSAs, but it is not merely a revamp of the HENSA sites; there are some fundamental changes.</p> <p>This article takes a look at the implementation of the service and our plans for the future.</p> <p><a href="http://www.ariadne.ac.uk/issue22/web-mirror" target="_blank">read more</a></p> issue22 tooled up mark russell jisc ukoln university of bath apache archives cache copyright data ftp linux operating system rfc samba search technology software standards url usability xml z39.50 Tue, 21 Dec 1999 00:00:00 +0000 editor 670 at http://www.ariadne.ac.uk Web Focus: Technical Aspects of Copyright and the Web http://www.ariadne.ac.uk/issue10/web-focus <div class="field field-type-text field-field-teaser-article"> <div class="field-items"> <div class="field-item odd"> <p><a href="/issue10/web-focus#author1">Brian Kelly</a> reports on the TALiSMAN seminar: Copyright and the Web.</p> </div> </div> </div> <p>In April a former colleague of mine from Leeds University sent a message to me about a strange copyright statement she had come across on the web, and asked for my comments. I was also intrigued by the statement and, on 23 April, sent the following message to the <kbd>lis-elib</kbd> Mailbase list</p> <p>&nbsp;</p> <hr /> <p>A strange copyright statment (<i>sic</i>) at the URL <a href="http://clans.cla.co.uk/www/auths.html"> <a href="http://clans.cla.co.uk/www/auths.html" title="http://clans.cla.co.uk/www/auths.html">http://clans.cla.co.uk/www/auths.html</a> </a> has been brought to my attention.</p> <p>It states that readers are not authorised to:</p> <p><a href="http://www.ariadne.ac.uk/issue10/web-focus" target="_blank">read more</a></p> issue10 regular column brian kelly apple jisc ukoln university of leeds elib adobe browser cache copyright graphics html intellectual property internet explorer java mailbase multimedia rfc software url web resources web services Fri, 18 Jul 1997 23:00:00 +0000 editor 374 at http://www.ariadne.ac.uk Internationalisation and the Web http://www.ariadne.ac.uk/issue9/trenches <div class="field field-type-text field-field-teaser-article"> <div class="field-items"> <div class="field-item odd"> <p><a href="/issue9/trenches#author1">Jon Knight</a> looks at how the Web is currently undergoing the sometimes painful internationalization process required if it is to live up to its name of the World Wide Web.</p> </div> </div> </div> <p><a href="http://www.ariadne.ac.uk/issue9/trenches" target="_blank">read more</a></p> issue9 tooled up jon knight ansi ietf iso w3c ascii browser character encoding css doc dtd ftp graphics html hypertext i18n interoperability rfc software standardisation standards unicode url utf-16 utf-8 Sun, 18 May 1997 23:00:00 +0000 editor 325 at http://www.ariadne.ac.uk Performance and Security: Notes for System Administrators http://www.ariadne.ac.uk/issue8/unix-security <div class="field field-type-text field-field-teaser-article"> <div class="field-items"> <div class="field-item odd"> <p>Performance and Security - Notes for System Administrators: <a href="/issue8/unix-security#author1">Andy Powell</a> offers some hints and tips on the performance and security aspects of running electronic library services on UNIX based machines.</p> </div> </div> </div> <p>The eLib Technical Concertation day last November brought together techies from many of the eLib projects. (See Clare McClean's report in Ariadne issue 6 for more details <a href="#REF1">[1]</a>). A wide range of the technical issues associated with running electronic library services were discussed at the meeting but inevitably, given the time constraints, some of these were not covered in any great detail.</p> <p><a href="http://www.ariadne.ac.uk/issue8/unix-security" target="_blank">read more</a></p> issue8 tooled up andy powell ukoln university of bath w3c elib access control apache api archives bsd cache data dns ftp graphics html operating system passwords perl research rfc secure shell software solaris ssh Wed, 19 Mar 1997 00:00:00 +0000 editor 287 at http://www.ariadne.ac.uk Down Under With the Dublin Core http://www.ariadne.ac.uk/issue8/canberra-metadata <div class="field field-type-text field-field-teaser-article"> <div class="field-items"> <div class="field-item odd"> <p><a href="/issue8/canberra-metadata#author1">Paul Miller</a> and <a href="/issue8/canberra-metadata#author2">Tony Gill</a> offer a view of the recent Dublin Core metadata workshop in the Australian capital, Canberra.</p> </div> </div> </div> <p>Continuing a long and glorious tradition, the 4th Dublin Core Workshop <a href="#fn1">[1]</a> last month went to a really nice country and picked one of the least lively settlements in which to meet. Admittedly, in the company of such as Dublin (Ohio, USA, rather than the somewhat more picturesque capital of Eire) and Coventry, Canberra did rather manage to shine.</p> <p><a href="http://www.ariadne.ac.uk/issue8/canberra-metadata" target="_blank">read more</a></p> issue8 event report paul miller tony gill ahds apple distributed systems technology centre national library of australia ncsa oclc ukoln university of kent university of sydney w3c elib cataloguing data dtd dublin core html hypertext identifier lcsh marc metadata national library opera pics resource description resource discovery rfc standards url Wed, 19 Mar 1997 00:00:00 +0000 editor 297 at http://www.ariadne.ac.uk Securing HTML FORMs http://www.ariadne.ac.uk/issue5/securing-forms <div class="field field-type-text field-field-teaser-article"> <div class="field-items"> <div class="field-item odd"> <p><a href="/issue5/securing-forms#author1">Jon Knight</a> discusses some of the options available to the designers and implementors of HTML FORMs for providing authentication of users in a library environment.</p> </div> </div> </div> <p><b>T</b>here are now many <a href="http://www.w3.org/pub/WWW/MarkUp/">HTML</a> FORMs in use in libraries of all types. These forms are usually the front ends to <a href="http://www.w3.org/pub/WWW/CGI/">Common Gateway Interface (CGI)</a> programs that implement such things as webopacs, electronic ILL requests and access to backend databases. Often these FORMs have to be authenticated to ensure that only valid library users can make use of the services. Web browsers and servers offer a number of a facilities for doing this authentication, each with different benefits and problems.</p> <p><a href="http://www.ariadne.ac.uk/issue5/securing-forms" target="_blank">read more</a></p> issue5 tooled up jon knight algorithm apache authentication browser data database html passwords plain text rfc standards web browser Wed, 18 Sep 1996 23:00:00 +0000 editor 161 at http://www.ariadne.ac.uk Wire: Email Interview with Chris Lilley http://www.ariadne.ac.uk/issue2/wire <div class="field field-type-text field-field-teaser-article"> <div class="field-items"> <div class="field-item odd"> <p><a href="/issue2/wire#author1">Chris Lilley</a> submits to an interview by email.</p> </div> </div> </div> <p>I represent <a href="http://www.niss.ac.uk/education/jasper/intro.html">JISC</a> at the Advisory Council meetings of the <a href="http://www.w3.org/pub/WWW/">World Wide Web Consortium (W3C)</a>. Most of the delegates are representing commercial companies, wheras I am effectively representing the UK Higher Education sector! W3C member companies are given advance information in confidence, and I am currently working with W3C to see how I can involve UK HE in the work of W3C without violating that confidence.</p> <p><a href="http://www.ariadne.ac.uk/issue2/wire" target="_blank">read more</a></p> issue2 regular column chris lilley hewlett-packard ietf jisc microsoft w3c browser css data dtd gopher graphics higher education html internet explorer interoperability java linux mac os mobile multimedia png rfc rtf sgml software standards visualisation web browser windows Tue, 19 Mar 1996 00:00:00 +0000 editor 59 at http://www.ariadne.ac.uk