XML and relational databases uses and opportunities for libraries
Identifieur interne : 000349 ( Istex/Corpus ); précédent : 000348; suivant : 000350XML and relational databases uses and opportunities for libraries
Auteurs : Art RhynoSource :
- OCLC Systems & Services: International digital library perspectives [ 1065-075X ] ; 2002-06-01.
Abstract
Relational Database Management Systems RDBMS have a proven track record for storing and managing many different forms of digital content, and new strategies have been defined to provide RDBMSbased solutions for XML. Some relational databases now offer special mechanisms to accommodate XML while several technologies have emerged to facilitate the use of XML representations of data housed within an RDBMS. In addition to presenting challenges and opportunities to RDBMS developers, XML and XMLenabled technologies may find new application for libraries by combining RDBMS concepts with Webbased services.
Url:
DOI: 10.1108/10650750210430169
Links to Exploration step
ISTEX:6316B53D256F917F276A293AB96607BACEAF5538Le document en format XML
<record><TEI wicri:istexFullTextTei="biblStruct"><teiHeader><fileDesc><titleStmt><title xml:lang="en">XML and relational databases uses and opportunities for libraries</title><author wicri:is="90%"><name sortKey="Rhyno, Art" sort="Rhyno, Art" uniqKey="Rhyno A" first="Art" last="Rhyno">Art Rhyno</name><affiliation><mods:affiliation>Art Rhyno is Systems Librarian at the Leddy Library, University of Windsor, Ontario, Canada.</mods:affiliation></affiliation></author></titleStmt><publicationStmt><idno type="wicri:source">ISTEX</idno><idno type="RBID">ISTEX:6316B53D256F917F276A293AB96607BACEAF5538</idno><date when="2002" year="2002">2002</date><idno type="doi">10.1108/10650750210430169</idno><idno type="url">https://api.istex.fr/document/6316B53D256F917F276A293AB96607BACEAF5538/fulltext/pdf</idno><idno type="wicri:Area/Istex/Corpus">000349</idno></publicationStmt><sourceDesc><biblStruct><analytic><title level="a" type="main" xml:lang="en">XML and relational databases uses and opportunities for libraries</title><author wicri:is="90%"><name sortKey="Rhyno, Art" sort="Rhyno, Art" uniqKey="Rhyno A" first="Art" last="Rhyno">Art Rhyno</name><affiliation><mods:affiliation>Art Rhyno is Systems Librarian at the Leddy Library, University of Windsor, Ontario, Canada.</mods:affiliation></affiliation></author></analytic><monogr></monogr><series><title level="j">OCLC Systems & Services: International digital library perspectives</title><idno type="ISSN">1065-075X</idno><imprint><publisher>MCB UP Ltd</publisher><date type="published" when="2002-06-01">2002-06-01</date><biblScope unit="volume">18</biblScope><biblScope unit="issue">2</biblScope><biblScope unit="page" from="97">97</biblScope><biblScope unit="page" to="103">103</biblScope></imprint><idno type="ISSN">1065-075X</idno></series><idno type="istex">6316B53D256F917F276A293AB96607BACEAF5538</idno><idno type="DOI">10.1108/10650750210430169</idno><idno type="filenameID">1640180205</idno><idno type="original-pdf">1640180205.pdf</idno><idno type="href">10650750210430169.pdf</idno></biblStruct></sourceDesc><seriesStmt><idno type="ISSN">1065-075X</idno></seriesStmt></fileDesc><profileDesc><textClass></textClass><langUsage><language ident="en">en</language></langUsage></profileDesc></teiHeader><front><div type="abstract" xml:lang="en">Relational Database Management Systems RDBMS have a proven track record for storing and managing many different forms of digital content, and new strategies have been defined to provide RDBMSbased solutions for XML. Some relational databases now offer special mechanisms to accommodate XML while several technologies have emerged to facilitate the use of XML representations of data housed within an RDBMS. In addition to presenting challenges and opportunities to RDBMS developers, XML and XMLenabled technologies may find new application for libraries by combining RDBMS concepts with Webbased services.</div></front></TEI><istex><corpusName>emerald</corpusName><author><json:item><name>Art Rhyno</name><affiliations><json:string>Art Rhyno is Systems Librarian at the Leddy Library, University of Windsor, Ontario, Canada.</json:string></affiliations></json:item></author><subject><json:item><lang><json:string>eng</json:string></lang><value>Computer languages</value></json:item><json:item><lang><json:string>eng</json:string></lang><value>Database management</value></json:item></subject><language><json:string>eng</json:string></language><originalGenre><json:string>review-article</json:string></originalGenre><abstract>Relational Database Management Systems RDBMS have a proven track record for storing and managing many different forms of digital content, and new strategies have been defined to provide RDBMSbased solutions for XML. Some relational databases now offer special mechanisms to accommodate XML while several technologies have emerged to facilitate the use of XML representations of data housed within an RDBMS. In addition to presenting challenges and opportunities to RDBMS developers, XML and XMLenabled technologies may find new application for libraries by combining RDBMS concepts with Webbased services.</abstract><qualityIndicators><score>3.868</score><pdfVersion>1.3</pdfVersion><pdfPageSize>610 x 789 pts</pdfPageSize><refBibsNative>true</refBibsNative><keywordCount>2</keywordCount><abstractCharCount>605</abstractCharCount><pdfWordCount>2824</pdfWordCount><pdfCharCount>18106</pdfCharCount><pdfPageCount>7</pdfPageCount><abstractWordCount>87</abstractWordCount></qualityIndicators><title>XML and relational databases uses and opportunities for libraries</title><genre><json:string>review-article</json:string></genre><host><volume>18</volume><publisherId><json:string>oclc</json:string></publisherId><pages><last>103</last><first>97</first></pages><issn><json:string>1065-075X</json:string></issn><issue>2</issue><subject><json:item><value>Library & information science</value></json:item><json:item><value>Librarianship/library management</value></json:item><json:item><value>Records management & preservation</value></json:item><json:item><value>Library technology</value></json:item><json:item><value>Information repositories</value></json:item></subject><genre><json:string>journal</json:string></genre><language><json:string>unknown</json:string></language><title>OCLC Systems & Services: International digital library perspectives</title><doi><json:string>10.1108/oclc</json:string></doi></host><publicationDate>2002</publicationDate><copyrightDate>2002</copyrightDate><doi><json:string>10.1108/10650750210430169</json:string></doi><id>6316B53D256F917F276A293AB96607BACEAF5538</id><score>0.16154061</score><fulltext><json:item><original>true</original><mimetype>application/pdf</mimetype><extension>pdf</extension><uri>https://api.istex.fr/document/6316B53D256F917F276A293AB96607BACEAF5538/fulltext/pdf</uri></json:item><json:item><original>false</original><mimetype>application/zip</mimetype><extension>zip</extension><uri>https://api.istex.fr/document/6316B53D256F917F276A293AB96607BACEAF5538/fulltext/zip</uri></json:item><istex:fulltextTEI uri="https://api.istex.fr/document/6316B53D256F917F276A293AB96607BACEAF5538/fulltext/tei"><teiHeader><fileDesc><titleStmt><title level="a" type="main" xml:lang="en">XML and relational databases uses and opportunities for libraries</title></titleStmt><publicationStmt><authority>ISTEX</authority><publisher>MCB UP Ltd</publisher><availability><p>EMERALD</p></availability><date>2002</date></publicationStmt><sourceDesc><biblStruct type="inbook"><analytic><title level="a" type="main" xml:lang="en">XML and relational databases uses and opportunities for libraries</title><author><persName><forename type="first">Art</forename><surname>Rhyno</surname></persName><affiliation>Art Rhyno is Systems Librarian at the Leddy Library, University of Windsor, Ontario, Canada.</affiliation></author></analytic><monogr><title level="j">OCLC Systems & Services: International digital library perspectives</title><idno type="pISSN">1065-075X</idno><idno type="DOI">10.1108/oclc</idno><imprint><publisher>MCB UP Ltd</publisher><date type="published" when="2002-06-01"></date><biblScope unit="volume">18</biblScope><biblScope unit="issue">2</biblScope><biblScope unit="page" from="97">97</biblScope><biblScope unit="page" to="103">103</biblScope></imprint></monogr><idno type="istex">6316B53D256F917F276A293AB96607BACEAF5538</idno><idno type="DOI">10.1108/10650750210430169</idno><idno type="filenameID">1640180205</idno><idno type="original-pdf">1640180205.pdf</idno><idno type="href">10650750210430169.pdf</idno></biblStruct></sourceDesc></fileDesc><profileDesc><creation><date>2002</date></creation><langUsage><language ident="en">en</language></langUsage><abstract xml:lang="en"><p>Relational Database Management Systems RDBMS have a proven track record for storing and managing many different forms of digital content, and new strategies have been defined to provide RDBMSbased solutions for XML. Some relational databases now offer special mechanisms to accommodate XML while several technologies have emerged to facilitate the use of XML representations of data housed within an RDBMS. In addition to presenting challenges and opportunities to RDBMS developers, XML and XMLenabled technologies may find new application for libraries by combining RDBMS concepts with Webbased services.</p></abstract><textClass><keywords scheme="keyword"><list><head>Keywords</head><item><term>Computer languages</term></item><item><term>Database management</term></item></list></keywords></textClass><textClass><keywords scheme="Emerald Subject Group"><list><label>cat-LISC</label><item><term>Library & information science</term></item><label>cat-LLM</label><item><term>Librarianship/library management</term></item><label>cat-RMP</label><item><term>Records management & preservation</term></item><label>cat-LTC</label><item><term>Library technology</term></item><label>cat-IREP</label><item><term>Information repositories</term></item></list></keywords></textClass></profileDesc><revisionDesc><change when="2002-06-01">Published</change></revisionDesc></teiHeader></istex:fulltextTEI><json:item><original>false</original><mimetype>text/plain</mimetype><extension>txt</extension><uri>https://api.istex.fr/document/6316B53D256F917F276A293AB96607BACEAF5538/fulltext/txt</uri></json:item></fulltext><metadata><istex:metadataXml wicri:clean="corpus emerald not found" wicri:toSee="no header"><istex:xmlDeclaration>version="1.0" encoding="UTF-8"</istex:xmlDeclaration><istex:document><!-- Auto generated NISO JATS XML created by Atypon out of MCB DTD source files. Do Not Edit! --><article dtd-version="1.0" xml:lang="en" article-type="review-article"><front><journal-meta><journal-id journal-id-type="publisher-id">oclc</journal-id><journal-id journal-id-type="doi">10.1108/oclc</journal-id><journal-title-group><journal-title>OCLC Systems & Services: International digital library perspectives</journal-title></journal-title-group><issn pub-type="ppub">1065-075X</issn><publisher><publisher-name>MCB UP Ltd</publisher-name></publisher></journal-meta><article-meta><article-id pub-id-type="doi">10.1108/10650750210430169</article-id><article-id pub-id-type="original-pdf">1640180205.pdf</article-id><article-id pub-id-type="filename">1640180205</article-id><article-categories><subj-group subj-group-type="type-of-publication"><compound-subject><compound-subject-part content-type="code">review-article</compound-subject-part><compound-subject-part content-type="label">General review</compound-subject-part></compound-subject></subj-group><subj-group subj-group-type="subject"><compound-subject><compound-subject-part content-type="code">cat-LISC</compound-subject-part><compound-subject-part content-type="label">Library & information science</compound-subject-part></compound-subject><subj-group><compound-subject><compound-subject-part content-type="code">cat-LLM</compound-subject-part><compound-subject-part content-type="label">Librarianship/library management</compound-subject-part></compound-subject><subj-group><compound-subject><compound-subject-part content-type="code">cat-LTC</compound-subject-part><compound-subject-part content-type="label">Library technology</compound-subject-part></compound-subject></subj-group></subj-group><subj-group><compound-subject><compound-subject-part content-type="code">cat-RMP</compound-subject-part><compound-subject-part content-type="label">Records management & preservation</compound-subject-part></compound-subject><subj-group><compound-subject><compound-subject-part content-type="code">cat-IREP</compound-subject-part><compound-subject-part content-type="label">Information repositories</compound-subject-part></compound-subject></subj-group></subj-group></subj-group></article-categories><title-group><article-title>XML and relational databases: uses and opportunities for libraries</article-title></title-group><contrib-group><contrib contrib-type="author"><string-name><given-names>Art</given-names> <surname>Rhyno</surname></string-name><aff>Art Rhyno is Systems Librarian at the Leddy Library, University of Windsor, Ontario, Canada.</aff></contrib></contrib-group><pub-date pub-type="ppub"><day>01</day><month>06</month><year>2002</year></pub-date><volume>18</volume><issue>2</issue><fpage>97</fpage><lpage>103</lpage><permissions><copyright-statement>© MCB UP Limited</copyright-statement><copyright-year>2002</copyright-year><license license-type="publisher"><license-p></license-p></license></permissions><self-uri content-type="pdf" xlink:href="10650750210430169.pdf"></self-uri><abstract><p>Relational Database Management Systems (RDBMS) have a proven track record for storing and managing many different forms of digital content, and new strategies have been defined to provide RDBMS‐based solutions for XML. Some relational databases now offer special mechanisms to accommodate XML while several technologies have emerged to facilitate the use of XML representations of data housed within an RDBMS. In addition to presenting challenges and opportunities to RDBMS developers, XML and XML‐enabled technologies may find new application for libraries by combining RDBMS concepts with Web‐based services.</p></abstract><kwd-group><kwd>Computer languages</kwd><x>, </x><kwd>Database management</kwd></kwd-group><custom-meta-group><custom-meta><meta-name>peer-reviewed</meta-name><meta-value>no</meta-value></custom-meta><custom-meta><meta-name>academic-content</meta-name><meta-value>yes</meta-value></custom-meta><custom-meta><meta-name>rightslink</meta-name><meta-value>included</meta-value></custom-meta></custom-meta-group></article-meta></front><body><sec><title>Introduction</title><p>Extensible Markup Language</p><p> (XML) is becoming an indispensable tool for virtually every type of content that is digitally produced. The advantages of XML for libraries have been well described by others (Tennant, 2001; Miller, 2000). On a general level, XML has at least three key advantages:</p><list list-type="order"><list-item><label>1. </label><p>(1) <italic>XML is standard</italic>. XML is a subset of Standard Generalized Markup Language (SGML), a well established and highly regarded ISO standard. XML also offers mechanisms (document type definitions, and more recently, XML Schema) to encourage and enforce common definitions of the logical structure of a document so that standards for the documents themselves are easier to apply.</p></list-item><list-item><label>2. </label><p>(2) <italic>XML is extensible</italic>. XML has no limits on the number of markup languages that can be defined using it, and each of these languages can consist of an unlimited number of tags. This flexibility is essential for fostering the widespread adoption of XML and helps explain why XML has been utilized for markup languages in every conceivable subject area, ranging from chess playing to mind reading.</p></list-item><list-item><label>3. </label><p>(3) <italic>XML is well supported</italic>. It seems that almost every serious Web technology is now expected to define its relationship to XML, and XML has fostered an explosion of related technologies. The W3C has made many tools and toolkits freely available to Web developers, and utilities and applications for XML are being developed by a worldwide community of vendors, open source contributors, and other groups that seek to move information across the Web.</p></list-item></list><p>XML has been used extensively for authoring standalone documents, but database solutions for storing and managing large collections of materials in XML format are becoming more common. As Bourett (2001), a researcher who tracks developments in XML databases, points out, choosing between an RDBMS and other database options for storing XML often comes down to whether you are working with data or documents. If the XML content is usually manipulated at the individual field level, needs to be accessed with standard query and reporting tools, and pulls together information from sources that are updated and maintained separately, then a Relational Database Management System (RDBMS) approach may make the most sense. Examples of this kind of “data‐centric” content include purchase orders, flight schedules, and scientific data. If the XML content is largely contained in individual documents, and the content will be edited and updated at the document level, then Object Orientated Databases (OODBMS), Object/Relational Databases, and other solutions that can maintain XML documents as a more complete unit on the backend will be preferred.</p><p>Data housed in an RDBMS are typically based on individual rows in tables (see <xref ref-type="fig" rid="F_1640180205001">Figure 1</xref>), using “keys” or “ids” to pull together content dynamically. Most RDBMS solutions for storing XML assemble XML representations of the data on the fly. Object relational databases and some RDBMS add‐ons, such as Oracle’s Internet File System (IFS), step slightly outside of the standard RDBMS tables to work with Binary Large Object (BLOB) or other mechanisms built into the database to store whole XML documents without parceling pieces of it to separate tables. This allows the document to be stored with all tags and ordering preserved.</p><p>Of course, the data and document distinction is not absolute, and there are other factors that can influence the choice of a database. An organization may have built up a high level of Oracle experience, for example, and that would have a huge impact on any data management decisions. Libraries are also in a somewhat unique situation in that they house collections of both data‐centric and document‐centric materials that may require database solutions. For example, libraries with finding aids in Encoded Archival Description (EAD) format or full text materials marked up with Text Encoding Initiative (TEI) are more likely to favor “document‐centric” solutions and require extensive full text searching capabilities that are more prevalent in OODBMS and Object/Relational Databases. Libraries are even more likely to deal with content that is “data‐centric”, such as purchase orders and circulation records; they may already have RDBMSs in place to support the processing activities associated with this data.</p></sec><sec><title>MARC and XML </title><p>The difficulty in separating data from document‐based content can be seen in the Machine Readable Cataloguing (MARC) format, one of the library community’s most successful and durable standards. Like many document‐centric formats, MARC records can carry a lot of text‐intensive information. Libraries may even choose to convert MARC records to standalone XML documents in order to take advantage of mainstream XML tools for indexing or for presentation purposes. On the other hand, MARC records are “data‐centric” in the sense that they can often bring together data sources that are maintained outside of the bibliographic description of an item. Authority, holdings and item records, for example, play a key role in helping to define the bibliographic view of the physical and virtual objects in the library’s collection, yet these records are often processed and updated separately.</p><p>Libraries have begun to explore the use of XML for MARC. Lane Medical Library at Stanford University has created a DTD and released conversion software for converting MARC records to XML documents in an initiative called XMLMARC (<ext-link ext-link-type="uri" xlink:href="http://xmlmarc.stanford.edu">http://xmlmarc.stanford.edu</ext-link>). K.T. Lam has also proposed a DTD for MARC and suggests that the use of a decentralized authority repository may one day be possible with XML linking technologies (Lam, 2001). This would allow libraries to “point” to established names and subjects that could be maintained remotely rather than replicated by each individual library.</p><p>Clearly, there is interest on the part of libraries in bringing MARC fully into an XML environment. The challenge is to define an XML infrastructure that can handle the amount of materials that libraries catalogue without isolating the content from the transactional processes that libraries use for acquiring and circulating the collection. Cataloguing records are typically maintained by dozens of library staff and are linked to ordering and circulation processing procedures that involve many updates. Any application of XML that is tied directly to where cataloguing records are maintained and use XML as a means of updating content may need to be “transaction aware” and support a high level of multi‐user access.</p></sec><sec><title>Middleware alternatives</title><p>A number of middleware mapping tools exist for layering XML representations of information that is housed in an RDBMS on top of individual tables, such as IBM’s DatabaseDOM (<ext-link ext-link-type="uri" xlink:href="http://www.alphaworks.ibm.com/tech/databasedom">http://www.alphaworks.ibm.com/tech/databasedom</ext-link>). The middleware typically uses Structured Query Language (SQL) to pull together the fields needed for the XML input/output. The advantages of this approach are that this greatly increases the number of database systems that a library can select from because all major RDBMSs support SQL, and that this allows great flexibility for moving from one database to another. For formats like MARC, these tools also offer the possibility of using XML technologies without losing the robustness of relational databases for maintaining content and linkages that are updated by multiple users. The disadvantages of this approach include the overhead required to assemble and disassemble XML documents as they move in and out of the database, and the extra groundwork to define an XML representation that takes full advantage of both the RDBMS and XML technologies.</p><p>A good example of an XML mapping tool for relational databases is Castor (<ext-link ext-link-type="uri" xlink:href="http://castor.exolabs.org">http://castor.exolabs.org</ext-link>), an open source project from Exolabs. The layout shown in <xref ref-type="fig" rid="F_1640180205002">Figure 2</xref> maps a simple XML representation of MARC variable fields to an RDBMS with Castor.</p><p>The mapping file in Castor determines how the XML will be produced from the contents of the RDBMS. In addition to defining whether a field in the RDBMS is to be rendered as a node or an attribute, an ID reference is provided that identifies the records in the appropriate table. Castor is very “Java‐centric,” which can be an advantage or disadvantage depending on how comfortable an organization is with the Java platform. By working with Java, a developer can use Castor to render the records in an RDBMS accessible and updatable as XML documents. Databases that can be used with Castor include Oracle, MySQL, and PostgreSQL.</p></sec><sec><title>The Web as the world’s biggest relational database</title><p>The way that an RDBMS references rows from multiple tables can be compared to Web links. A Web page is, in some ways, much like an RDBMS “view” of disparate data. From a user perspective, the content is brought together based on a predefined logic and a series of “keys” or “pointers” that identify relevant material. A dynamically generated Web page comes even closer to the conceptual model of an RDBMS, particularly if much of the content of the page is based on remote network resources retrieved through URLs. For example, a search of a library catalogue on the Web typically involves a cgi‐bin program that dynamically displays results using HTML. Each result record is usually linked to a fuller display via a URL that specifies from where the information is to be retrieved.</p><p>The linking mechanisms of the Web have recently been leveraged to support the OpenURL framework (Van de Sompel and Beit‐Arie, 2001a). The OpenURL framework has been proposed as an architecture for retrieving references to scholarly works by enabling third parties to provide links for a referenced item. Although OpenURLs have typically been deployed to provide links to the full text of scholarly works, the framework can also be utilized to identify a catalogued item in an ILS. Ex Libris’ ALEPH500 System, for example, directly supports OpenURL, and exploratory work has been carried out to generalize the OpenURL framework beyond reference linking scholarly environments (Van de Sompel and Beit‐Arie, 2001b).</p><p>If the Web can be thought of as an ever‐growing RDBMS, and OpenURLs can be utilized to provide “RDBMS‐like” standard and precise links between specific items in information systems, then there are possibilities for providing extensive distributed search and retrieval functions in Web‐based library services. For example, a remote database consisting of Library of Congress names and subject headings could be searched within a browser environment, and the results could provide links to items in the local catalogue (see <xref ref-type="fig" rid="F_1640180205003">Figure 3</xref>).</p><p>Web‐based union catalogues support standardized indexing and searching at a central location. With OpenURLs, links can be made to point to holdings and other localized information within the member library’s Integrated Library System (see <xref ref-type="fig" rid="F_1640180205004">Figure 4</xref>). All of this fits within the RDBMS notion of creating and maintaining data with as little duplication as possible, and linking it together to provide a logical view of the content itself.</p><p>XML plays a role by greatly enhancing the linking mechanisms of the Web. XML technologies such as Xinclude, Xpath, and Xlink, provide sophisticated methods for drawing on network resources. Xinclude allows the contents of a separate XML resource to be inserted into an XML document based on a link (see <xref ref-type="fig" rid="F_1640180205005">Figure 5</xref>).</p><p>Xpath will be familiar to anyone who has worked with XSTL and other XML stylesheet tools. It allows the creation of expressions for specifying every visual and interface portion of a document. For example, a stylesheet designed for use with XSLT to output an HTML table might contain the syntax shown in <xref ref-type="fig" rid="F_1640180205006">Figure 6</xref>.</p><p>Xlink is the XML linking language and offers much more sophisticated types of linking than currently offered by the familiar HREF and NAME elements found in HTML. In <xref ref-type="fig" rid="F_1640180205007">Figure 7</xref>, Xlink’s extended element can name one or more linked resources. The arc element in this example tells an application about the behavior expected when moving through the linked resources. The role and title attributes are used to describe the function of the linked resource in the context of the local resource. Role is meant to be descriptive to the application and title is meant to be descriptive to the user. In this case, the roles are meant to identify an author’s works and biographies. The <italic>acutate</italic> element describes how the resources should appear. The value “onRequest” specifies that the resource should appear when the link is selected, and the value “embed” for the <italic>show</italic> attribute tells the application to insert the specified resource inline within the current document. Finally, an <italic>item</italic> element is used to represent where this particular resource can be found in physical form in the library.</p><p>If an XML representation of an RDBMS‐based library catalogue or other library database is made available, the library can make use of XML linking technologies and other XML tools for manipulating database contents. OpenURL lays the groundwork for using links as virtual keys to content that goes far beyond individual tables, and the content can be as broad as the diversity of the Web itself.</p></sec><sec><title>Conclusion</title><p>Relational databases are a good fit for much of the processing that libraries require in day‐to‐day operations. XML is well suited for describing documents, but it can also be a powerful tool for exposing the contents of a relational database to XML technologies. The RDBMS vendor community has responded to the worldwide interest in XML by creating XML products and add‐ons for relational database applications. Middleware approaches hold the promise of making the combination of XML and relation database systems more vendor‐neutral and transportable so that libraries need not be locked into one system. As XML becomes the preferred syntax for library standards, and linking mechanisms become more common, libraries will be able to bring together resources in new ways and further realize the advantages of being at the forefront of the World Wide Web.</p></sec><sec><title>Implications for practitioners</title><p>This summary has been provided to allow a rapid appreciation of the significance of the content of this article. Browsers may then choose to read the article in toto, to derive full benefit from the authors’ work.</p><p>Processing requirements in the everyday running of libraries have become increasingly sophisticated in the digital world. </p><p>It is fortunate that technology, coupled with the ingenuity of practitioners, has kept pace. Together these factors allow for wider access to materials and better links to find them.</p><p>Relational databases have proved their value in this respect and have fitted well with Extensible Markup Language (XML). </p><p>As a tool for digitally produced content, XML’s qualities are well documented. Its flexibility, for example, explains its use in markup languages in all subject areas. XML has been used widely for authoring standalone documents. However, database solutions for storing and managing large collections of materials in XML format are becoming more common.</p><p>The choice of which database option to use is likely to depend on whether practitioners work with data or documents. A Relational Database Management System (RDBMS) would favour the former and, perhaps, an Object Orientated Database the latter so that XML documents can be maintained as a more complete unit.</p><p>The waters are muddied by the fact that no 100 per cent clear distinction can be made between data and document. This can be seen in the Machine Readable Cataloging (MARC) format, a durable standard which has been around for more than a generation and which has both document‐centric and data‐centric characteristics.</p><p>Middleware mapping tools for relational databases, such as Castor, can play their part in ensuring that libraries do not have to be forced entirely down one road or the other. Castor can be used with Java to make records in a RDBMS accessible and capable of updating as XML documents.</p><p>More library services are now being delivered by the World Wide Web and it is inevitable that the Web looms large in discussion of these issues. The Web is effectively the world’s biggest relational database and there are similarities in the way data are housed in a RDBMS and the way that Web links work.</p><p>The Web can be viewed as an ever‐growing RDBMS. If page content is based on remote network resources retrieved through URLs, the combination provides extensive distributed search and retrieval functions in Web‐based library services. XML takes on a complementary role by enhancing the linking mechanisms of the Web through a number of sophisticated technologies. Among them, the linking language Xlink is viewed as a superior offering than elements currently to be found in HTML.</p><p>An XML representation of a database can pave the way for linking technologies that manipulate database contents. It is significant that RDBMS vendors have created XML products and add‐ons for relational database applications as a response to worldwide interest in XML.</p><p>XML has proved itself beyond doubt as a tool for digitally produced content. Its influence and use will continue to spread as linking mechanisms become more common. Along the way, libraries will find new ways to bring together resources and make the most of the Web.</p><p>(Précis supplied to MCB UP Limited by consultants.)</p></sec><sec><fig position="float" id="F_1640180205001"><label><bold>Figure 1<x> </x></bold></label><caption><p>The table with patron information (Patron_Table) is linked to another table (Pgroup_Table) describing the patron group</p></caption><graphic xlink:href="1640180205001.tif"></graphic></fig></sec><sec><fig position="float" id="F_1640180205002"><label><bold>Figure 2<x> </x></bold></label><caption><p>Mapping MARC tag fields to XML‐based RDBMS for information retrieval</p></caption><graphic xlink:href="1640180205002.tif"></graphic></fig></sec><sec><fig position="float" id="F_1640180205003"><label><bold>Figure 3<x> </x></bold></label><caption><p>The Web Form is constructed to pass some searches to the local catalog and one against a remote database. OpenURLs “point” back to local holdings</p></caption><graphic xlink:href="1640180205003.tif"></graphic></fig></sec><sec><fig position="float" id="F_1640180205004"><label><bold>Figure 4<x> </x></bold></label><caption><p>A centralized union catalog provides searching services, OpenURL links to location‐specific information</p></caption><graphic xlink:href="1640180205004.tif"></graphic></fig></sec><sec><fig position="float" id="F_1640180205005"><label><bold>Figure 5<x> </x></bold></label><caption><p>Xinclude is used to reference a remote resource</p></caption><graphic xlink:href="1640180205005.tif"></graphic></fig></sec><sec><fig position="float" id="F_1640180205006"><label><bold>Figure 6<x> </x></bold></label><caption><p>The stylesheet cycles through the items a patron has on loan from the library to create an HTML table for display on a Web browser</p></caption><graphic xlink:href="1640180205006.tif"></graphic></fig></sec><sec><fig position="float" id="F_1640180205007"><label><bold>Figure 7<x> </x></bold></label><caption><p>The Xlink syntax allows the linking sequence to be prescribed in some detail</p></caption><graphic xlink:href="1640180205007.tif"></graphic></fig></sec></body><back><ref-list><title>References</title><ref id="B1"><mixed-citation><person-group person-group-type="author"><string-name><surname>Bourett</surname>, <given-names>R.</given-names></string-name></person-group> (<year>2001</year>), “<article-title><italic>XML and databases</italic></article-title>”, available at <ext-link ext-link-type="uri" xlink:href="http://www.rpbourret.com/xml/XMLAndDatabases.htm">www.rpbourret.com/xml/XMLAndDatabases.htm</ext-link> (accessed 13 December, 2001).</mixed-citation></ref><ref id="B2"><mixed-citation><person-group person-group-type="author"><string-name><surname>Lam</surname>, <given-names>K.T.</given-names></string-name></person-group> (<year>2001</year>), “<article-title><italic>Moving from MARC to XML – part three: handling of authority metadata</italic></article-title>”, available at: ihome.ust.hk/∼lblkt/xml/marc2xml_3.html (accessed 13 December, 2001).</mixed-citation></ref><ref id="B3"><mixed-citation><person-group person-group-type="author"><string-name><surname>Miller</surname>, <given-names>D.</given-names></string-name></person-group> (<year>2000</year>), “<article-title><italic>XML: Libraries’ strategic opportunity</italic></article-title>”, <source><italic>Library Journal, NetConnect supplement</italic></source>, Summer, Vol. <volume>125</volume> (Suppl.), pp. <fpage>16</fpage><x>‐</x><lpage>19</lpage>, available at: xmlmarc.stanford.edu/LJ (accessed: 13 December, 2001).</mixed-citation></ref><ref id="B4"><mixed-citation><person-group person-group-type="author"><string-name><surname>Tennant</surname>, <given-names>R.</given-names></string-name></person-group> (<year>2001</year>), “<article-title><italic>XML: the digital library hammer</italic></article-title>”, <source><italic>Library Journal</italic></source>, Vol. <volume>126</volume> No. <issue>5</issue>, pp. <fpage>30</fpage><x>‐</x><lpage>2</lpage>, available at: libraryjournal.reviewsnews.com/index.asp?layout=articlePrint&articleID=CA156526 (accessed 13 December, 2001).</mixed-citation></ref><ref id="B5"><mixed-citation><person-group person-group-type="author"><string-name><surname>Van de Sompel</surname>, <given-names>H.</given-names></string-name></person-group> and <person-group person-group-type="author"><string-name><surname>Beit‐Arie</surname>, <given-names>O.</given-names></string-name></person-group> (<year>2001</year>a), “<article-title><italic>Open linking in the scholarly information environment using the OpenURL framework</italic></article-title>”, <source><italic>D‐Lib Magazine</italic></source>, Vol. <volume>7</volume> No. <issue>3</issue>, available at: <ext-link ext-link-type="uri" xlink:href="http://www.dlib.org/dlib/march01/vandesompel/03vandesompel.html">www.dlib.org/dlib/march01/vandesompel/03vandesompel.html</ext-link> (accessed 13 December, 2001).</mixed-citation></ref><ref id="B6"><mixed-citation><person-group person-group-type="author"><string-name><surname>Van de Sompel</surname>, <given-names>H.</given-names></string-name></person-group> and <person-group person-group-type="author"><string-name><surname>Beit‐Arie</surname>, <given-names>O.</given-names></string-name></person-group> (<year>2001</year>b), “<article-title><italic>Generalizing the OpenURL framework beyond references to scholarly works: the Bison‐Futé model</italic></article-title>”, <source><italic>D‐Lib Magazine</italic></source>, Vol. <volume>7</volume> No. <issue>7/8</issue>, available at: <ext-link ext-link-type="uri" xlink:href="http://www.dlib.org/dlib/july01/vandesompel/07vandesompel.html">www.dlib.org/dlib/july01/vandesompel/07vandesompel.html</ext-link> (accessed 13 December, 2001).</mixed-citation></ref></ref-list></back></article></istex:document></istex:metadataXml><mods version="3.6"><titleInfo lang="en"><title>XML and relational databases uses and opportunities for libraries</title></titleInfo><titleInfo type="alternative" lang="en" contentType="CDATA"><title>XML and relational databases uses and opportunities for libraries</title></titleInfo><name type="personal"><namePart type="given">Art</namePart><namePart type="family">Rhyno</namePart><affiliation>Art Rhyno is Systems Librarian at the Leddy Library, University of Windsor, Ontario, Canada.</affiliation></name><typeOfResource>text</typeOfResource><genre type="review-article" displayLabel="review-article"></genre><originInfo><publisher>MCB UP Ltd</publisher><dateIssued encoding="w3cdtf">2002-06-01</dateIssued><copyrightDate encoding="w3cdtf">2002</copyrightDate></originInfo><language><languageTerm type="code" authority="iso639-2b">eng</languageTerm><languageTerm type="code" authority="rfc3066">en</languageTerm></language><physicalDescription><internetMediaType>text/html</internetMediaType></physicalDescription><abstract lang="en">Relational Database Management Systems RDBMS have a proven track record for storing and managing many different forms of digital content, and new strategies have been defined to provide RDBMSbased solutions for XML. Some relational databases now offer special mechanisms to accommodate XML while several technologies have emerged to facilitate the use of XML representations of data housed within an RDBMS. In addition to presenting challenges and opportunities to RDBMS developers, XML and XMLenabled technologies may find new application for libraries by combining RDBMS concepts with Webbased services.</abstract><subject><genre>keywords</genre><topic>Computer languages</topic><topic>Database management</topic></subject><relatedItem type="host"><titleInfo><title>OCLC Systems & Services: International digital library perspectives</title></titleInfo><genre type="journal">journal</genre><subject><genre>Emerald Subject Group</genre><topic authority="SubjectCodesPrimary" authorityURI="cat-LISC">Library & information science</topic><topic authority="SubjectCodesSecondary" authorityURI="cat-LLM">Librarianship/library management</topic><topic authority="SubjectCodesSecondary" authorityURI="cat-RMP">Records management & preservation</topic><topic authority="SubjectCodesSecondary" authorityURI="cat-LTC">Library technology</topic><topic authority="SubjectCodesSecondary" authorityURI="cat-IREP">Information repositories</topic></subject><identifier type="ISSN">1065-075X</identifier><identifier type="PublisherID">oclc</identifier><identifier type="DOI">10.1108/oclc</identifier><part><date>2002</date><detail type="volume"><caption>vol.</caption><number>18</number></detail><detail type="issue"><caption>no.</caption><number>2</number></detail><extent unit="pages"><start>97</start><end>103</end></extent></part></relatedItem><identifier type="istex">6316B53D256F917F276A293AB96607BACEAF5538</identifier><identifier type="DOI">10.1108/10650750210430169</identifier><identifier type="filenameID">1640180205</identifier><identifier type="original-pdf">1640180205.pdf</identifier><identifier type="href">10650750210430169.pdf</identifier><accessCondition type="use and reproduction" contentType="copyright">© MCB UP Limited</accessCondition><recordInfo><recordContentSource>EMERALD</recordContentSource></recordInfo></mods></metadata><serie></serie></istex></record>Pour manipuler ce document sous Unix (Dilib)
EXPLOR_STEP=$WICRI_ROOT/Wicri/Ticri/explor/TeiVM2/Data/Istex/Corpus
HfdSelect -h $EXPLOR_STEP/biblio.hfd -nk 000349 | SxmlIndent | more
Ou
HfdSelect -h $EXPLOR_AREA/Data/Istex/Corpus/biblio.hfd -nk 000349 | SxmlIndent | more
Pour mettre un lien sur cette page dans le réseau Wicri
{{Explor lien
|wiki= Wicri/Ticri
|area= TeiVM2
|flux= Istex
|étape= Corpus
|type= RBID
|clé= ISTEX:6316B53D256F917F276A293AB96607BACEAF5538
|texte= XML and relational databases uses and opportunities for libraries
}}
| This area was generated with Dilib version V0.6.31. |  |