Information architecture planning with XML
Identifieur interne : 000452 ( Istex/Corpus ); précédent : 000451; suivant : 000453Information architecture planning with XML
Auteurs : John Robert GardnerSource :
- Library Hi Tech [ 0737-8831 ] ; 2001-09-01.
Abstract
The explosion of standards building on the 1998 XML specification from the World Wide Web Consortium has been slow to reach academic and library information science applications. While part of this is certainly due to cost, argues that adequate attention to architectural design, when considering XML technology, can make new forms of information management possible. Provides a survey of tools and relevant technology for working in Z39.50 with XML and MARC records, based primarily on a major undertaking by the ATLACERTR American Theological Library Association Center for Electronic Resources in Theology and Religion group at Emory University with 50 years of 50 journals digitized from philosophy, ethics, and religion.
Url:
DOI: 10.1108/07378830110405094
Links to Exploration step
ISTEX:18C3BE9FADB588A694D7AB7ADD8F356BDBFCAD7BLe document en format XML
<record><TEI wicri:istexFullTextTei="biblStruct"><teiHeader><fileDesc><titleStmt><title xml:lang="en">Information architecture planning with XML</title><author wicri:is="90%"><name sortKey="Gardner, John Robert" sort="Gardner, John Robert" uniqKey="Gardner J" first="John Robert" last="Gardner">John Robert Gardner</name><affiliation><mods:affiliation>John Robert Gardner is Deconstruction Architect, Sun MicroSystems, Burlington, Massachusetts, USA.</mods:affiliation></affiliation></author></titleStmt><publicationStmt><idno type="wicri:source">ISTEX</idno><idno type="RBID">ISTEX:18C3BE9FADB588A694D7AB7ADD8F356BDBFCAD7B</idno><date when="2001" year="2001">2001</date><idno type="doi">10.1108/07378830110405094</idno><idno type="url">https://api.istex.fr/document/18C3BE9FADB588A694D7AB7ADD8F356BDBFCAD7B/fulltext/pdf</idno><idno type="wicri:Area/Istex/Corpus">000452</idno></publicationStmt><sourceDesc><biblStruct><analytic><title level="a" type="main" xml:lang="en">Information architecture planning with XML</title><author wicri:is="90%"><name sortKey="Gardner, John Robert" sort="Gardner, John Robert" uniqKey="Gardner J" first="John Robert" last="Gardner">John Robert Gardner</name><affiliation><mods:affiliation>John Robert Gardner is Deconstruction Architect, Sun MicroSystems, Burlington, Massachusetts, USA.</mods:affiliation></affiliation></author></analytic><monogr></monogr><series><title level="j">Library Hi Tech</title><idno type="ISSN">0737-8831</idno><imprint><publisher>MCB UP Ltd</publisher><date type="published" when="2001-09-01">2001-09-01</date><biblScope unit="volume">19</biblScope><biblScope unit="issue">3</biblScope><biblScope unit="page" from="231">231</biblScope><biblScope unit="page" to="241">241</biblScope></imprint><idno type="ISSN">0737-8831</idno></series><idno type="istex">18C3BE9FADB588A694D7AB7ADD8F356BDBFCAD7B</idno><idno type="DOI">10.1108/07378830110405094</idno><idno type="filenameID">2380190304</idno><idno type="original-pdf">2380190304.pdf</idno><idno type="href">07378830110405094.pdf</idno></biblStruct></sourceDesc><seriesStmt><idno type="ISSN">0737-8831</idno></seriesStmt></fileDesc><profileDesc><textClass></textClass><langUsage><language ident="en">en</language></langUsage></profileDesc></teiHeader><front><div type="abstract" xml:lang="en">The explosion of standards building on the 1998 XML specification from the World Wide Web Consortium has been slow to reach academic and library information science applications. While part of this is certainly due to cost, argues that adequate attention to architectural design, when considering XML technology, can make new forms of information management possible. Provides a survey of tools and relevant technology for working in Z39.50 with XML and MARC records, based primarily on a major undertaking by the ATLACERTR American Theological Library Association Center for Electronic Resources in Theology and Religion group at Emory University with 50 years of 50 journals digitized from philosophy, ethics, and religion.</div></front></TEI><istex><corpusName>emerald</corpusName><author><json:item><name>John Robert Gardner</name><affiliations><json:string>John Robert Gardner is Deconstruction Architect, Sun MicroSystems, Burlington, Massachusetts, USA.</json:string></affiliations></json:item></author><subject><json:item><lang><json:string>eng</json:string></lang><value>Information management</value></json:item><json:item><lang><json:string>eng</json:string></lang><value>Bibliographic standards</value></json:item><json:item><lang><json:string>eng</json:string></lang><value>Internet</value></json:item><json:item><lang><json:string>eng</json:string></lang><value>Programming</value></json:item></subject><language><json:string>eng</json:string></language><originalGenre><json:string>review-article</json:string></originalGenre><abstract>The explosion of standards building on the 1998 XML specification from the World Wide Web Consortium has been slow to reach academic and library information science applications. While part of this is certainly due to cost, argues that adequate attention to architectural design, when considering XML technology, can make new forms of information management possible. Provides a survey of tools and relevant technology for working in Z39.50 with XML and MARC records, based primarily on a major undertaking by the ATLACERTR American Theological Library Association Center for Electronic Resources in Theology and Religion group at Emory University with 50 years of 50 journals digitized from philosophy, ethics, and religion.</abstract><qualityIndicators><score>6.064</score><pdfVersion>1.3</pdfVersion><pdfPageSize>610 x 789 pts</pdfPageSize><refBibsNative>true</refBibsNative><keywordCount>4</keywordCount><abstractCharCount>725</abstractCharCount><pdfWordCount>4756</pdfWordCount><pdfCharCount>32478</pdfCharCount><pdfPageCount>11</pdfPageCount><abstractWordCount>109</abstractWordCount></qualityIndicators><title>Information architecture planning with XML</title><genre><json:string>review-article</json:string></genre><host><volume>19</volume><publisherId><json:string>lht</json:string></publisherId><pages><last>241</last><first>231</first></pages><issn><json:string>0737-8831</json:string></issn><issue>3</issue><subject><json:item><value>Information & knowledge management</value></json:item><json:item><value>Information & communications technology</value></json:item><json:item><value>Internet</value></json:item><json:item><value>Library & information science</value></json:item><json:item><value>Information behaviour & retrieval</value></json:item><json:item><value>Librarianship/library management</value></json:item><json:item><value>Information user studies</value></json:item><json:item><value>Metadata</value></json:item><json:item><value>Library technology</value></json:item></subject><genre><json:string>journal</json:string></genre><language><json:string>unknown</json:string></language><title>Library Hi Tech</title><doi><json:string>10.1108/lht</json:string></doi></host><publicationDate>2001</publicationDate><copyrightDate>2001</copyrightDate><doi><json:string>10.1108/07378830110405094</json:string></doi><id>18C3BE9FADB588A694D7AB7ADD8F356BDBFCAD7B</id><score>0.12064864</score><fulltext><json:item><original>true</original><mimetype>application/pdf</mimetype><extension>pdf</extension><uri>https://api.istex.fr/document/18C3BE9FADB588A694D7AB7ADD8F356BDBFCAD7B/fulltext/pdf</uri></json:item><json:item><original>false</original><mimetype>application/zip</mimetype><extension>zip</extension><uri>https://api.istex.fr/document/18C3BE9FADB588A694D7AB7ADD8F356BDBFCAD7B/fulltext/zip</uri></json:item><istex:fulltextTEI uri="https://api.istex.fr/document/18C3BE9FADB588A694D7AB7ADD8F356BDBFCAD7B/fulltext/tei"><teiHeader><fileDesc><titleStmt><title level="a" type="main" xml:lang="en">Information architecture planning with XML</title></titleStmt><publicationStmt><authority>ISTEX</authority><publisher>MCB UP Ltd</publisher><availability><p>EMERALD</p></availability><date>2001</date></publicationStmt><sourceDesc><biblStruct type="inbook"><analytic><title level="a" type="main" xml:lang="en">Information architecture planning with XML</title><author><persName><forename type="first">John Robert</forename><surname>Gardner</surname></persName><affiliation>John Robert Gardner is Deconstruction Architect, Sun MicroSystems, Burlington, Massachusetts, USA.</affiliation></author></analytic><monogr><title level="j">Library Hi Tech</title><idno type="pISSN">0737-8831</idno><idno type="DOI">10.1108/lht</idno><imprint><publisher>MCB UP Ltd</publisher><date type="published" when="2001-09-01"></date><biblScope unit="volume">19</biblScope><biblScope unit="issue">3</biblScope><biblScope unit="page" from="231">231</biblScope><biblScope unit="page" to="241">241</biblScope></imprint></monogr><idno type="istex">18C3BE9FADB588A694D7AB7ADD8F356BDBFCAD7B</idno><idno type="DOI">10.1108/07378830110405094</idno><idno type="filenameID">2380190304</idno><idno type="original-pdf">2380190304.pdf</idno><idno type="href">07378830110405094.pdf</idno></biblStruct></sourceDesc></fileDesc><profileDesc><creation><date>2001</date></creation><langUsage><language ident="en">en</language></langUsage><abstract xml:lang="en"><p>The explosion of standards building on the 1998 XML specification from the World Wide Web Consortium has been slow to reach academic and library information science applications. While part of this is certainly due to cost, argues that adequate attention to architectural design, when considering XML technology, can make new forms of information management possible. Provides a survey of tools and relevant technology for working in Z39.50 with XML and MARC records, based primarily on a major undertaking by the ATLACERTR American Theological Library Association Center for Electronic Resources in Theology and Religion group at Emory University with 50 years of 50 journals digitized from philosophy, ethics, and religion.</p></abstract><textClass><keywords scheme="keyword"><list><head>Keywords</head><item><term>Information management</term></item><item><term>Bibliographic standards</term></item><item><term>Internet</term></item><item><term>Programming</term></item></list></keywords></textClass><textClass><keywords scheme="Emerald Subject Group"><list><label>cat-IKM</label><item><term>Information & knowledge management</term></item><label>cat-ICT</label><item><term>Information & communications technology</term></item><label>cat-INT</label><item><term>Internet</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-IBRT</label><item><term>Information behaviour & retrieval</term></item><label>cat-LLM</label><item><term>Librarianship/library management</term></item><label>cat-IUS</label><item><term>Information user studies</term></item><label>cat-MTD</label><item><term>Metadata</term></item><label>cat-LTC</label><item><term>Library technology</term></item></list></keywords></textClass></profileDesc><revisionDesc><change when="2001-09-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/18C3BE9FADB588A694D7AB7ADD8F356BDBFCAD7B/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">lht</journal-id><journal-id journal-id-type="doi">10.1108/lht</journal-id><journal-title-group><journal-title>Library Hi Tech</journal-title></journal-title-group><issn pub-type="ppub">0737-8831</issn><publisher><publisher-name>MCB UP Ltd</publisher-name></publisher></journal-meta><article-meta><article-id pub-id-type="doi">10.1108/07378830110405094</article-id><article-id pub-id-type="original-pdf">2380190304.pdf</article-id><article-id pub-id-type="filename">2380190304</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-IKM</compound-subject-part><compound-subject-part content-type="label">Information & knowledge management</compound-subject-part></compound-subject><subj-group><compound-subject><compound-subject-part content-type="code">cat-ICT</compound-subject-part><compound-subject-part content-type="label">Information & communications technology</compound-subject-part></compound-subject><subj-group><compound-subject><compound-subject-part content-type="code">cat-INT</compound-subject-part><compound-subject-part content-type="label">Internet</compound-subject-part></compound-subject></subj-group></subj-group></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-IBRT</compound-subject-part><compound-subject-part content-type="label">Information behaviour & retrieval</compound-subject-part></compound-subject><subj-group><compound-subject><compound-subject-part content-type="code">cat-IUS</compound-subject-part><compound-subject-part content-type="label">Information user studies</compound-subject-part></compound-subject><compound-subject><compound-subject-part content-type="code">cat-MTD</compound-subject-part><compound-subject-part content-type="label">Metadata</compound-subject-part></compound-subject></subj-group></subj-group><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></article-categories><title-group><article-title>Information architecture planning with XML</article-title></title-group><contrib-group><contrib contrib-type="author"><string-name><given-names>John Robert</given-names> <surname>Gardner</surname></string-name><aff>John Robert Gardner is Deconstruction Architect, Sun MicroSystems, Burlington, Massachusetts, USA.</aff></contrib></contrib-group><pub-date pub-type="ppub"><day>01</day><month>09</month><year>2001</year></pub-date><volume>19</volume><issue>3</issue><fpage>231</fpage><lpage>241</lpage><permissions><copyright-statement>© MCB UP Limited</copyright-statement><copyright-year>2001</copyright-year><license license-type="publisher"><license-p></license-p></license></permissions><self-uri content-type="pdf" xlink:href="07378830110405094.pdf"></self-uri><abstract><p>The explosion of standards building on the 1998 XML specification from the World Wide Web Consortium has been slow to reach academic and library information science applications. While part of this is certainly due to cost, argues that adequate attention to architectural design, when considering XML technology, can make new forms of information management possible. Provides a survey of tools and relevant technology for working in Z39.50 with XML and MARC records, based primarily on a major undertaking by the ATLA‐CERTR (American Theological Library Association – Center for Electronic Resources in Theology and Religion) group at Emory University with 50 years of 50 journals digitized from philosophy, ethics, and religion.</p></abstract><kwd-group><kwd>Information management</kwd><x>, </x><kwd>Bibliographic standards</kwd><x>, </x><kwd>Internet</kwd><x>, </x><kwd>Programming</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><ack><p>Additional thanks to Dale Emery, Architect at Sun MicroSystems for Bibliographic Citations.</p></ack></front><body><sec><title>Introduction</title><p>It goes without saying that keeping up with information technology is daunting – that observation is so over‐noted as to be trite. But, for all the clamor of how important it is to keep up, to innovate smartly, to be backwardly compatible, and to observe the sacredness of institutional memory, there still remains a fundamental reticence to innovation which is not fully fiscal in its cause.</p><p>Among the assumptions with which I have written this article is that the additional reticence arises – in both academia and, to a lesser extent, corporate information technology – from the failure to put adequate importance on information architecture design and communication. The experiences during the last ten years of work in information architecture, primarily in the academic world, and the research done to address this issue, informs the recommendations in this article. In addition, the focus is to survey the range of applicable XML technologies, and provide pointers for the reader anxious to drill down into more meaty detail.</p><p>The challenge of well‐informed strategic information architecture design for today’s libraries is the same set of issues faced by city engineers using architecture in municipal planning to accommodate the incompatibility of legacy infrastructure with burgeoning user population and the need for mobility. Of course, in information architecture, the “citizens” or “dwellers” who are clients of the architect are in fact data packets or strings (e.g. as in a MARC record or a database table cell). Too often information architectures are designed with little or no attention to this reality.</p><p>This is why extensible markup language (XML) has been so misperceived, misrepresented and, in most cases, poorly implemented. XML is how the data – simple naked strings of digits and letters – is made portable, interchangeable, scalable, and so forth. It must always be “packaged” before delivery, e.g. most content you view on major Web sites – such as Amazon.com – is stored as either XML or a relational database (such as Oracle). It is turned into HTML, or more properly put, it is converted to HTML “on the fly” when you click a link to pull up specific data.</p><p>In this article, I begin by addressing the misperceptions with XML and how this has impeded sound architectural design in its early adoption stages. A detailed overview of basic principles of information architecture design theory, integrated with XML technology planning, provides a context for introducing the range of XML technologies. Finally, an application of XML technology, at the Emory University‐based ATLA‐CERTR (American Theological Library Association – Center for Electronic Resources in Theology and Religion) project with XML and Z39.50 in humanities literature, is introduced as an example of XML application to a library information architecture problem.</p></sec><sec><title>XML: an “extensively misrepresented language”</title><p>XML was oversold. Its implementation, especially in the comparatively limited fiscal resources of higher education, has been substantially impaired by this fact. Not that the proliferation of Luddite fears has not compounded things, but the misrepresentation of XML played right into the tried‐and‐true rhetorical spin‐doctoring of the technology‐squeamish.</p><p>XML <italic>is</italic> an optimal data interchange, conversion, and transport mechanism. It is not, however, necessarily the best delivery mechanism (e.g. it is not browser‐friendly) nor the best storage format (XML storage can become quite large compared – for some uses, that is – to how a relational database might store it). Both of these shortcomings may or may not change, but they do not obviate the key architectural value in working with XML.</p><sec><title>XML’s “extensive” family of standards</title><p>It is surprising how few people, even reasonably well‐informed in the information technology, do not know that there is but one markup language in existence, not several or hundreds. HTML, XML, and all the other “MLs” are all derivatives of a single international standard, standard general markup language (SGML). HTML is a simpler “flavor” of SGML, for example, that works well in browsers.</p><p>XML, also a derivative of SGML, has a simpler and stricter syntax, but unlimited semantics. Accordingly, it has fostered a myriad of related standards all of which obey XML syntax, while using different semantics designed for specific purposes. For example, extensible stylesheet language for transformations (XSLT) is a form of XML[1] which converts one form of XML to another, or to text, or to HTML (Gardner and Rendon, 2001). Its semantics indicate this with element names like “template” and “for each.” There is also a form of XML, related to XSLT, for formatting called “FO” or formatting objects.</p><p>XML begins with the basic principle of markup tags, removes some of the more esoteric parts of SGML, and invokes a ruthlessly strict syntax. It is beyond the scope of this paper to introduce XML in detail[2]. Suffice it to say that it basically looks like HTML, but has a great deal more flexibility in the semantics of tag name.</p><p>XML’s stricter syntax requires all opening tags to have closing tags, consistency of lower case in tag and attribute names, and consistent use of quotation marks around attribute values, among other things. What is achieved through this “strict” set of rules for tags is a wider range of software and a simpler set of applications for writing, working with, and storing XML documents. The other advantage of XML lies in the word “extensible.” This indicates that there is flexibility in the kinds of things that XML can identify.</p><p>There are also forms of XML that are specifically devoted to metadata, such as the RDF language[3] which uses the Dublin Core tag set for metadata. The same syntax rules for XML apply, but here the semantics are the key for identifying “creator” and “title,” etc. Another use for XML is to represent webs of links between things based on how they are topically related. XML topic maps, or XTM[4], differentiates things like Shakespeare as an author from Shakespeare as a subject, or title. It is not unlike a set of intelligent bookmarks.</p><p>This plethora of standards has fostered many mistaken impressions: that there is no compatibility between all these kinds of MLs (markup languages); that XML is somehow incomplete or broken and needs these standards to bolster it; that so many standards implies instability and therefore, caution before investing in the technology is warranted. It is understandable that this confusion has arisen – first due to XML being oversold; mostly because the notion of information architecture is still largely in its infancy, and has not informed most information technology planning at the university level.</p><p>The situation is compounded by the over‐hype to buy into the information revolution and plunge forward with this new technology. This gives the mistaken impression of massive legacy migrations and complete restructuring of existing systems. XML is designed to bridge current storage, exchange, and delivery models to a more scalable and accessible technology, reflecting more closely the growing range of data standards based on XML syntax. To position a university or college library for the maximum cost benefit and conversion ease, it is necessary to begin thinking architecturally of the data residing in an OPAC or similar information technology repository.</p></sec><sec><title>A word about information architecture</title><p>The importance of a cohesive information architecture strategy in a university setting is just as paramount as in the corporate world. In both cases, the individuals performing many key design and implementation tasks are a high turnover population (corporate turnover on the one hand, cycles of student workers on the other). For academia especially, this is compounded by significantly tighter fiscal resources.</p><p>Architecture addresses key considerations for both the current and future states of information processing. It makes it possible to articulate in common terms the needs of stakeholders, as well as the semantics of behavior of the system and its parts. Sound information architecture allows for full support of distributed processing, interoperability across heterogeneous systems and departments, and internetworking between systems. Large scale “internetworked” information spaces are becoming a prominent, even determining, feature of Carnegie assessments of the information infrastructure of an institution. Standardization of processes and knowledge architecture is critical to achieving the promised return on investment (RoI) from Internet‐based information technology.</p><p>The main barrier to effective information technology management lies in the need for applications to share information meaningfully, not in the reliability or security of the technology. This is because of the variety of <italic>ad hoc</italic> systems deployed by universities and the way these systems are variously configured and used. It is this set of interchange and integration issues which XML best addresses, when applied with systematic architectural rigor. This article presents a summary of, and pointers to (see “Further reading”), the range of resources along these lines necessary to implement the concepts touched on here.</p><p>In fact, in this connection, information architecture is a growing field in search of a discipline. A side recommendation in this article is that a specific curriculum needs to be developed along these lines. Joint appointments between information science, computer science, and philosophy (the issues of semantics and ontology are key components) could begin filling out such a program. As noted in the industry‐information source “TrackIT” from Vencorp (e‐mail news service, January 22, 2001, alias: trackit@vencorp.net) (emphasis added):</p><disp-quote><p>“Information architect” designates the individual responsible for how to distribute information. The architect’s job is to identify the ideal user experience and specify what it takes to create that experience. While information architecture deals with the structure of the whole [system], interaction design is done at the [user‐interface] level. It is a sub‐set of what the information architect does. <italic>There is no formal training (yet) for information architects. Those currently filling this position have backgrounds in human factors, library science, graphic design, film making, editorial, and even structural architecture.</italic></p></disp-quote><p>The design of such a department at the graduate level could leverage the resource of research assistants and teaching assistants to evangelize and provide user assistance in developing XML architectures.</p></sec><sec><title>Information architecture for optimal XML implementations</title><p>Information architecture has a relatively simple vocabulary which provides an amazing turn‐around in increased inter‐divisional and inter‐departmental understanding. The importance of architecture in careful integration with XML is underscored by the formation of a World Wide Web Consortium Architecture Domain group [5] to address the integration and layering of future evolving standards to maintain and enhance the cohesion in the current set of specifications.</p><p>At Sun MicroSystems and related companies, as well as Carnegie Research I and other classes of institutions, it is common that basic terms for understanding a system are different from group to group. For human resources, for instance, “software” might mean spreadsheet and word processing applications. For the information infrastructure teams, software likely means anything running on the hardware – including the operating systems such as Solaris or Mac OS.</p><p>In the absence of a clear structure for considering an institution’s architecture, the rapidly growing field of XML technology is impossible to grasp or deploy. Therefore, a simple set of basic categories for information architecture serve to simplify how we communicate about, and collaboratively design, the best integration of all the relevant XML functional specifications. Working with international standards, the following basic notions are derived from ISO 10746, the Reference Model for Open Distributed Processing (RM‐ODP) [6]; and the International Electrical and Electronic Engineering (IEEE)’s enterprise ontology, specification number 1471[7].</p><p>First and foremost, it is important to think of the information technology architecture for an institution, such as a library, as a <italic>single</italic> architecture. In other words, there are not several architectures, such as “the data architecture” and “the user architecture” and the “technology architecture.” All of these are perspectives, or “viewpoints” on the architecture. A viewpoint represents the concerns of a set of stakeholders – e.g. patrons have concerns, database administrators have concerns, and others have concerns that both differ and overlap. Communicating and representing these concerns consistently is central to adequate planning for XML developments.</p><p>The following handful of terms comprise the vocabulary for information architecture. Notice that architecture includes principles of design and evolution. This view of information architecture accounts for rapid changes in technology by establishing design and change as integral ongoing components of architecture (Putnam, 2001):</p><list list-type="bullet"><list-item><label>• </label><p><italic>Architecture.</italic> The organization of a system embodied in its components, their relationships to each other, and to the environment and the principles guiding its design and evolution.</p></list-item><list-item><label>• </label><p><italic>Model.</italic> Represents the system from a set of concerns or a focus (e.g. a viewpoint of a stakeholder); this can be a document, visual software image, etc. Models combine to represent systems, models can contain other models.</p></list-item><list-item><label>• </label><p><italic>Stakeholder.</italic> Any customer, users, etc.; individual, team, organization with interests in, or concerns relative to, a system.</p></list-item><list-item><label>• </label><p><italic>View.</italic> A rendering or representation – a picture – of a system representing a set of concerns, or viewpoint, i.e. concerns of a stakeholder(s); a view can be in diagram form, narrative/text, or combinations of both; views contain models.</p></list-item><list-item><label>• </label><p><italic>Viewpoint.</italic> A pattern or set of rules for constructing a view of an architecture for a specific stakeholder or domain; using a selected set terms and symbols, in order to focus on particular concerns within a system.</p></list-item></list><p>We can apply these terms within the following set of concerns of stakeholders, or viewpoints, which comprise the primary design and implementation aspects of any information system (derived from the RM‐ODP; see also Putnam (2001)):</p><list list-type="bullet"><list-item><label>• </label><p><italic>Business viewpoint.</italic> The business activities of the specified system; similar to a “high‐level process,” sometimes called an “enterprise” viewpoint, can include security processes/policies.</p></list-item><list-item><label>• </label><p><italic>Data viewpoint.</italic> The information that needs to be stored and processed in the system; similar to CRUD‐based (create, read, update, delete) data representation; can show data flow and/or data structure or schema, includes monitoring and failure detection.</p></list-item><list-item><label>• </label><p><italic>Systems viewpoint.</italic> The description of the system as a set of objects that interact at interfaces – enabling system distribution; systems, and the integration between them, have an interaction and module view; they can also include security APIs, systems, etc.</p></list-item><list-item><label>• </label><p><italic>Deployment viewpoint.</italic> The mechanisms supporting system distribution; e.g. this specific box is in such and such a location.</p></list-item><list-item><label>• </label><p><italic>Technology viewpoint.</italic> The detail of the components from which the distributed system is constructed (products, vendors); the “stacks” of technology for each component in the system.</p></list-item></list><p>Within this framework, we can now begin to understand how XML implementation, with the range of attendant specifications, works in an architecture. It should be noted that the RM‐ODP is an enterprise‐wide architecture applied specifically here to XML use in library information science.</p><p>Working with this conception, the XML data is considered the “resident” of this architecture, the APIs (application programming interfaces) and input/output (I/O) are the doors and windows, and so forth. The analogy could be extended, but it becomes a bit cumbersome in planning practice, so we use the five viewpoints to talk about the “spaces” in the information architecture inhabited by the data.</p><p>Moving through each viewpoint, in turn, we can see how the layers of architecture and the layers of XML specifications interact. XML addresses the business viewpoint concerns in several ways. In the data viewpoint, for example, it maintains a consistent format for data exchange, read, write, and update activities between various users and systems. Entry of records is handled here in at the level of read/write to the database, where the user interface for doing so is addressed in the business viewpoint. </p><p>In the data viewpoint, the XML architecture can utilize a centralized set of XSLT transformations for conversion (XSLT is central to all uses of XML and is relatively easy to learn and inexpensive to deploy) (see Gardner and Rendon, 2001). This conversion, in turn, serves the user concerns for delivery in browsers by conversion from XML to HTML.</p><p>At the systems level, APIs lying behind those data exchanges are displayed, as would be the conversion to XML from, for instance, an Oracle‐style relational database (RDB) using the Oracle XML SQL Utilities (XSU) free add‐on, or the ENCompass product from Endeavor[8] which also works with an Oracle back‐end. It is at this level that another XML specification, the document object model, or DOM[9], which furnishes an API for XML information, is addressed. This is also the level at which the interface for Z39.50 and the MARC data repository – in XML or ASCII – is designed.</p><p>By contrast, the business viewpoint considers the current information processing flow, the major interchanges, and user interaction points. The use of “XSLFO,” for “FOrmatting” XSL browser displays, and XML standard query language, or XQL (still under development as a specification[10]), for use in an OPAC is planned.</p><p>More detailed matters of deployment are covered in the technology viewpoint, where software and hardware choices are made. This is coordinated, in turn, with the deployment viewpoint which addresses the capabilities and locations of specific systems on which different processes and storage will take place.</p><p>In effect, these viewpoints can inform a sub‐committee division which, with shared terminology for referencing the architecture, can integrate their work more seamlessly. In fact, information technology divisions can also be structured along these lines for project management.</p></sec></sec><sec><title>The ATLA‐CERTR atlas project at Emory University: XML design</title><p>The following archive and access procedure was developed at Emory University by the US Theological Library Association’s Center for Electronic Resources in Theology and Religion (ATLA‐CERTR). ATLA‐CERTR has undertaken a project in which over 50 years of issues from 50 journals in philosophy, ethics, and religion are being scanned as images[11] for archival integrity. They are also being keyed in with the text encoding initiative (TEI) DTD in XML.</p><sec><title>Moving from a MARC architecture to a MARC/XML architecture: data conversion</title><p>The project’s point of researcher‐access is through the MARC records from the comprehensive catalogue of resources maintained by ATLA (the CERTR project uses a 50 × 50 journal/year subset of the one‐of‐a‐kind resource for theology, ethics, religion, philosophy and biblical studies carefully maintained by the Chicago‐based nonprofit organization). To accomplish this task, and to maintain a completely standards‐based XML solution, the MARC records required translation into XML, as well as further processing.</p><p>Because the string‐tagging system in MARC is so very orderly, it is not difficult to convert MARC records to XML. Compared with XML, it is the same principle with each part of a library lookup record being identified in MARC by its starting position in the numerical sequence of characters forming the record (a start tag in XML correlates to this), and the length in number of characters of that piece of information (an end tag in XML indicates this point of closure for the information). There is also a three‐digit string that identifies what kind of information is represented (title, etc.), like an XML element or attribute name.</p><p>Fortunately, while it is possible to wrap a MARC record in XML tags and use a complex set of XPath (a specification for addressing sub‐portions of XML documents which is used closely with XSLT[12]) functions and expressions (e.g. count(), substring‐after(), and so on), there is already software that does this. I highly recommend a freeware program called marcxml.exe (alas, Windows only) from Bob Pritchett at Logos, Inc.[13]. The Logos software simply takes a command line in an MS‐DOS window with the name of the program, the input MARC, and the output XML filename you choose. It runs very quickly, even on extremely large MARC files, and produces well‐formed XML. An output MARC record in XML is shown as the input in <xref ref-type="fig" rid="F_2380190304001">Figure 1</xref>.</p><p>Once the materials are in XML format, XSLT can be used to manipulate, query, sub‐select, and otherwise transform them for interchange (e.g. into Dublin Core tag names, or GILS, etc.). In <xref ref-type="fig" rid="F_2380190304002">Figure 2</xref>, we are able to sub‐select using XSLT based on the ISSN number from a larger set.</p><p>From the MARC records, everything from page ranges to author information can be tied together into XML data fields addressed by an object oriented database, or OODB, for linkage to the actual text of the articles, or scanned images of those pages. Up until this point, we have been resolving the issues in the data and systems viewpoint. We are looking at how conversions between storage formats can take place, and the creation, reading, updating (using XSLT to transform the MARC/XML‐format records – such as add an 856 “g” field with a URI to all records derived from its ISSN and citation details), and deleting (CRUD) of data.</p></sec><sec><title>Working with a Z39.50 XML architecture</title><p>As is well known with Z39.50, consistency – even with a standard of such long significance and prevalence as Z39.50 – is difficult to maintain between subsets of attributes such as, for instance, those of Bib‐1. The problem arises when some institutions do some parts of Bib‐1, but not others. What if I ask for a name un‐normalized, as in Figure 2 (field 4,102), but your institution’s Z39.50 OPAC only has phrase (4,1); word (4,2); and key word (4,3) – or worse, no structure attribute at all? What does it do with my (4,102) request? What if I do not specify a structure field, but your Z39.50 OPAC has this data?</p><p>This is why the same query to five Z39.50 OPACs often yields five different result sets. Some systems will “guess” at what you meant to include, or what they think the unsupported data is. Best practice recommends that an error be returned saying “such and such is not supported here, please refine your query.” That is the <italic>current</italic> best practice.</p><p>Of the 11 facilities which comprise the Z39.50 protocol, one is intended to address these issues of discrepancy between the structure of queries. One might ask: if “Explain” serves to furnish this kind of information up front, why is there any problem, or need for such a best practice? Until recently, there was limited support for Explain.</p><p>There are a number of products for working with Z39.50. This will likely become more plentiful with the advent of Z39.50 in an XML formatted delivery schema. This work is currently under way in initial investigation by the Z39.50 Implementor’s Group (ZIG)[14]. Software decisions are costly, and various products with current market share do not necessarily treat Z39.50 in the same way.</p><p>I already mentioned a market leader, currently featured in a showcase implementation at Cornell University on Solaris: the Endeavor products. A short summary of several products we reviewed is included below (for additional information on Z39.50 support, go to the corporation page, or the Library of Congress[15]). All the products below run on Solaris, and many have NT and/or Linux versions.</p><list list-type="order"><list-item><label>1. </label><p>(1) <italic>MetaManager</italic>[16]:</p></list-item></list><list list-type="bullet"><list-item><label>• </label><p>Runs with Oracle.</p></list-item><list-item><label>• </label><p>Was developed for Geospatial data; works with GEO profile.</p></list-item><list-item><label>• </label><p>Supports Z39.50 search and retrieve, <italic>some</italic> browse/scan support.</p></list-item><list-item><label>• </label><p>Returns records in HTML, ASCII, SGML, or XML.</p></list-item><list-item><label>• </label><p>Provides support for GILS, Bib‐1, but primarily for GEO attribute set.</p></list-item><list-item><label>• </label><p>Changes to master collection automatically update all global variables.</p></list-item><list-item><label>• </label><p>Has a base record return format of SUTRS; can do USMARC and GRS‐1.</p></list-item><list-item><label>• </label><p>Runs with institution’s own security system (three possible ways), rather than Z39.50’s.</p></list-item></list><list list-type="order"><list-item><label>1. </label><p>(2) <italic>Finsiel Zeta Suite</italic>[17]:</p></list-item></list><list list-type="bullet"><list-item><label>• </label><p>Stand‐alone set of tools to build integrated multi‐media cultural heritage information resources and to make those resources available for search and retrieve over digital networks.</p></list-item><list-item><label>• </label><p>The Zeta Suite is based on the Z39.50 protocol (ANSI Z39.50, ISO 10162/63).</p></list-item><list-item><label>• </label><p>Runs on Solaris.</p></list-item><list-item><label>• </label><p>Complete/stand‐alone product, not an Oracle augment.</p></list-item><list-item><label>• </label><p>Perl‐based.</p></list-item><list-item><label>• </label><p>Proxy, uses independent, not Z39.50 security.</p></list-item><list-item><label>• </label><p>Has a range of components, either for Z39.50 origins, targets, gateways, etc.</p></list-item></list><list list-type="order"><list-item><label>1. </label><p>(3) <italic>BSn’s interBasis</italic>[18]:</p></list-item></list><list list-type="bullet"><list-item><label>• </label><p>An emerging family of multi‐platform multi‐protocol information management products for Inter/Intranet applications.</p></list-item><list-item><label>• </label><p>Z39.50 target (server) supports the following facilities: init, search, present, retrieve (the standard minimum), delete, scan, access control.</p></list-item><list-item><label>• </label><p>Fully configurable attribute sets, GRS and advanced search.</p></list-item><list-item><label>• </label><p>Explain is planned.</p></list-item><list-item><label>• </label><p>Access and database maintenance is available via a WWW interface.</p></list-item><list-item><label>• </label><p>Data is converted “live” via an object oriented technology to any of a number of presentation formats, including HTML and XML for use in the World Wide Web.</p></list-item><list-item><label>• </label><p>The interBasis server includes a high‐speed structured full‐text retrieval engine that supports a wide range of native document types (including SGML, XML, HTML, MARC and numerous bibliographic, metadata and Internet standards).</p></list-item><list-item><label>• </label><p>National language and international character set support.</p></list-item><list-item><label>• </label><p>CORBA interface to integrate legacy.</p></list-item><list-item><label>• </label><p>RDBMS services is in development. Support for IPv6 is currently being tested.</p></list-item></list><list list-type="order"><list-item><label>1. </label><p>(4) <italic>Blue Angel Technologies MetaStar Suite</italic>[19]:</p></list-item></list><list list-type="bullet"><list-item><label>• </label><p>Provides an integrated system for managing and publishing information using Z39.50.</p></list-item><list-item><label>• </label><p>Works with Oracle: accommodates repeating, hierarchical, and locally‐defined elements, and integrates with third‐party relational database management systems (e.g. Microsoft Access, Oracle) using the ODBC industry standard interface.</p></list-item><list-item><label>• </label><p>Provides out‐of‐the‐box support for a number of metadata standards (including GILS, FGDC, CIMI, ICPSR, Dublin Core, DIF, ANZLIC).</p></list-item><list-item><label>• </label><p>Permits development and deployment of custom records without programming.</p></list-item><list-item><label>• </label><p>Server: makes metadata available for searching and retrieval using Z39.50. Integrated with a number of popular off‐the‐shelf search engines (e.g. Alta Vista or Fulcrum) and is configurable for full‐text and structured searches.</p></list-item><list-item><label>• </label><p>Data entry: uses a Java Applet to remotely enter metadata records directly from a Web browser.</p></list-item><list-item><label>• </label><p>Repository: has an administrative tool for capturing, importing, managing, and exporting metadata in a variety of file formats.</p></list-item><list-item><label>• </label><p>Gateway: simultaneously searches physically distributed Z39.50 servers with a single query and merges results into a single result set.</p></list-item><list-item><label>• </label><p>Software development kits (SDKs): has Z39.50 client and server SDKs (in C++ and Java) kits to allow users to develop custom applications.</p></list-item></list><list list-type="order"><list-item><label>1. </label><p>(5) <italic>ZedJAVA</italic>[20]:</p></list-item></list><list list-type="bullet"><list-item><label>• </label><p>ZedJava is the result of the collaborative effort between DSTC[21] and Crossnet[22] to create a sophisticated software package for developers of Z39.50 based information retrieval software.</p></list-item><list-item><label>• </label><p>ZedJava can be used within a wide Web interface for Z39.50 information servers in the form of a Java applet, or it can be used in a standalone application.</p></list-item><list-item><label>• </label><p>The software is provided in the form of a Java application programmers’ interface as a set of class files with comprehensive documentation.</p></list-item><list-item><label>• </label><p>When placed on a Web page, an applet using ZedJava can be automatically downloaded and run in a user’s Web browser, providing access to any Z39.50 servers co‐located with the Web server or via a proxy gateway.</p></list-item></list><list list-type="order"><list-item><label>1. </label><p>(6) <italic>Zebra (and Z’mbol)</italic>[23]:</p></list-item></list><list list-type="bullet"><list-item><label>• </label><p>Zebra is free!</p></list-item><list-item><label>• </label><p>It supports Explain, and a relatively rich list of facilities.</p></list-item><list-item><label>• </label><p>Can be “scaled” with its commercial bigger brother, Z’mbol.</p></list-item></list><list list-type="order"><list-item><label>1. </label><p>(7) <italic>ZedKit</italic>[24]:</p></list-item></list><list list-type="bullet"><list-item><label>• </label><p>Supplied by Crossnet Systems Ltd. Z39.50 software development kit, C and C++. For Windows 95/NT.</p></list-item><list-item><label>• </label><p>Supports most of Z39.50 including comprehensive example code, test utilities and documentation.</p></list-item><list-item><label>• </label><p>ZedKit for UNIX is free, but ZedKit for Windows is commercial.</p></list-item><list-item><label>• </label><p>Both have the same API for UNIX/Windows and both support all Z39.50 services (except the new duplicate detection service).</p></list-item><list-item><label>• </label><p>Both support explain, scan, and the accounting services (resource report and resource control) and have a freeware complimentary explain package for the UNIX package that allows you to create your explain data in text tables, and it has all the search code and record code for you.</p></list-item><list-item><label>• </label><p>Their ICONE client is a GUI example of ZedKit for Windows – it is also free.</p></list-item></list><list list-type="order"><list-item><label>1. </label><p>(8) <italic>Structured Information Manager (SIM) from RMIT</italic>[25]:</p></list-item></list><list list-type="bullet"><list-item><label>• </label><p>Supports all 11 facilities of Z39.50.</p></list-item><list-item><label>• </label><p>Can be side‐by‐side with Oracle.</p></list-item><list-item><label>• </label><p>Supports all library profiles, all formats of data record retrieval.</p></list-item><list-item><label>• </label><p>Stores data in native format.</p></list-item><list-item><label>• </label><p>Infinitely scalable to the real of terabytes, all multimedia.</p></list-item><list-item><label>• </label><p>Supports all aspects of phase II rich hierarchy/XML full context search support.</p></list-item><list-item><label>• </label><p>Full Unicode support.</p></list-item></list><p>Of these, the CERTR team chose SIM[25] for its robustness, its record of success with major US and UK government organizations and international corporations, and its rich range of Z39.50, XML, and metadata features.</p></sec></sec><sec><title>Conclusion</title><p>“Why XML?” might well be asked. XML is now one of the preferred formats for the returning of data from discoveries in a search. XML is likely to supplant GRS‐1 (generic record syntax) and SUTRS (simple unstructured text record syntax) due to its strict syntax, which enables back‐mapping to MARC if need be, and full selection on which fields to display. It is also more easily negotiated from Z39.50 targets to the range of origins from which a query begins.</p><p>XML is seen most frequently in library implementations in the Dublin Core set of 15 basic elements (all of which are included in the Bath Profile, and are supported in Bib‐1). It is interesting to note that Dublin Core, and the XML/RDF set of solutions, arose from the Z39.50 community as part of the Warwick Framework of April, 1996.</p><p>With respect to the discussion earlier, regarding compatibility and the “Explain” facility, there is a great deal of potential for XML to resolve many of these issues. The opportunity for information necessary to systems not supporting Explain to be routed through RDF structures (a series of empty tags, with namespaces for different institutions to identify which attributes and facilities their Z39.50 OPAC supports) could serve as a bridge to the developing future in which Explain and the other rich facilities of Z39.50 are more widely adopted and deployed.</p><p>With the recent codification and formal status of the XML Schema specification[27], the syntax of traditional document type definitions (DTDs) is replaced by an XML syntax for describing the elements and attributes which structure an XML data resource. This means the same kinds of transformation software with XSLT can be used on the schema as is used on the source data. This allows for a multitude of Z39.50 profiles to be managed through an RDF‐supported central registry of XML schemas, allowing conversion on the fly of both query and result data sets for compatibility between a virtually infinite variety of sources and targets. The work of converting Z39.50 from ASN1 to and XML format is ongoing by the ZIG group, the Z39.50 implementer’s group[28] as well as independent efforts converting the ASN1 data description to an XML Schema[29, cf. also 27].</p><p>Recent developments include work done by Michael Dovey and Associates at Oxford to work with JavaBeans and Z39.50, as well as XML‐based implementations of the Explain facility in a “lite” edition[30]. Further work has experimented with the new specification for universal description, discovery, and integration (UDDI) – an evolving e‐commerce protocol discovery standard that operates not unlike Explain in the business case it serves[31].</p><p>Where resources are thin, an institution can make major steps forward with XML technology using freely available tools available from resources such as the Library of Congress, the links it lists, and <ext-link ext-link-type="uri" xlink:href="http://www.xml.org">www.xml.org</ext-link>. For the short term, conversion is the key. Infoteria now makes tools for converting from legacy spreadsheets to XML, for instance[32], and there are other tools for MARC to XML conversion in addition to the Logos tool mentioned above. Conversion of legacy data for delivery via XML can be implemented using the key XSLT technology and free tools from sources like Apache[33]. XML transformations can be layered on top of and between key components of a legacy architecture with minimal investment.</p></sec><sec><title>Notes</title><list list-type="order"><list-item><label>1. </label><p>1 <ext-link ext-link-type="uri" xlink:href="http://www.w3.org/Style/XSL/">http://www.w3.org/Style/XSL/</ext-link></p></list-item><list-item><label>2. </label><p>2 See <ext-link ext-link-type="uri" xlink:href="http://vedavid.org/xml/docs/forlinksandintromaterials">http://vedavid.org/xml/docs/ for links and intro materials</ext-link>.</p></list-item><list-item><label>3. </label><p>3 <ext-link ext-link-type="uri" xlink:href="http://www.w3.org/RDF/">http://www.w3.org/RDF/</ext-link></p></list-item><list-item><label>4. </label><p>4 <ext-link ext-link-type="uri" xlink:href="http://www.topicmaps.org/">http://www.topicmaps.org/</ext-link></p></list-item><list-item><label>5. </label><p>5 <ext-link ext-link-type="uri" xlink:href="http://www.w3.org/Architecture/">http://www.w3.org/Architecture/</ext-link></p></list-item><list-item><label>6. </label><p>6 <ext-link ext-link-type="uri" xlink:href="http://www.dstc.edu.au/Research/Projects/ODP/standards.html">http://www.dstc.edu.au/Research/Projects/ODP/standards.html</ext-link></p></list-item><list-item><label>7. </label><p>7 <ext-link ext-link-type="uri" xlink:href="http://standards.ieee.org/catalog/olis/index.html">http://standards.ieee.org/catalog/olis/index.html</ext-link></p></list-item><list-item><label>8. </label><p>8 <ext-link ext-link-type="uri" xlink:href="http://www.endinfosys.com/prods/encompass.htm">http://www.endinfosys.com/prods/encompass.htm</ext-link></p></list-item><list-item><label>9. </label><p>9 <ext-link ext-link-type="uri" xlink:href="http://www.w3.org/DOM/">http://www.w3.org/DOM/</ext-link></p></list-item><list-item><label>10. </label><p>10 <ext-link ext-link-type="uri" xlink:href="http://www.w3.org/XML/Query">http://www.w3.org/XML/Query</ext-link></p></list-item><list-item><label>11. </label><p>11 <ext-link ext-link-type="uri" xlink:href="http://rosetta.atla-certr.org/CERTR/CERTR.html">http://rosetta.atla‐certr.org/CERTR/CERTR.html</ext-link></p></list-item><list-item><label>12. </label><p>12 See <ext-link ext-link-type="uri" xlink:href="http://www.w3.org/TR/xpath">http://www.w3.org/TR/xpath</ext-link></p></list-item><list-item><label>13. </label><p>13 <ext-link ext-link-type="uri" xlink:href="http://www.logos.com/marc/marc.asp">http://www.logos.com/marc/marc.asp</ext-link></p></list-item><list-item><label>14. </label><p>14 See minutes at <ext-link ext-link-type="uri" xlink:href="http://lcweb.loc.gov/z3950/agency/zig/meetings/dc2000/zxml-report.html">http://lcweb.loc.gov/z3950/agency/zig/meetings/dc2000/zxml‐report.html</ext-link></p></list-item><list-item><label>15. </label><p>15 <ext-link ext-link-type="uri" xlink:href="http://lcweb.loc.gov/z3950/gateway.html">http://lcweb.loc.gov/z3950/gateway.html</ext-link>#about</p></list-item><list-item><label>16. </label><p>16 <ext-link ext-link-type="uri" xlink:href="http://www.fgdctoolkit.com/html/intro.html">http://www.fgdctoolkit.com/html/intro.html</ext-link></p></list-item><list-item><label>17. </label><p>17 <ext-link ext-link-type="uri" xlink:href="http://zeta.tlcpi.finsiel.it/zetasuite/products.html">http://zeta.tlcpi.finsiel.it/zetasuite/products.html</ext-link></p></list-item><list-item><label>18. </label><p>18 <ext-link ext-link-type="uri" xlink:href="http://www.bsn.com/Z39.50/">http://www.bsn.com/Z39.50/</ext-link></p></list-item><list-item><label>19. </label><p>19 <ext-link ext-link-type="uri" xlink:href="http://www.blueangeltech.com/">http://www.blueangeltech.com/</ext-link></p></list-item><list-item><label>20. </label><p>20 <ext-link ext-link-type="uri" xlink:href="http://roadrunner.crxnet.com/wwwzedjava.html">http://roadrunner.crxnet.com/wwwzedjava.html</ext-link></p></list-item><list-item><label>21. </label><p>21 <ext-link ext-link-type="uri" xlink:href="http://www.dstc.au.edu/">http://www.dstc.au.edu/</ext-link></p></list-item><list-item><label>22. </label><p>22 <ext-link ext-link-type="uri" xlink:href="http://www.crxnet.com">http://www.crxnet.com</ext-link></p></list-item><list-item><label>23. </label><p>23 <ext-link ext-link-type="uri" xlink:href="http://www.indexdata.dk/">http://www.indexdata.dk/</ext-link></p></list-item><list-item><label>24. </label><p>24 <ext-link ext-link-type="uri" xlink:href="http://www.mds.rmit.edu.au/">http://www.mds.rmit.edu.au/</ext-link></p></list-item><list-item><label>25. </label><p>25 <ext-link ext-link-type="uri" xlink:href="http://www.crxnet.com/zkitw.html">http://www.crxnet.com/zkitw.html</ext-link></p></list-item><list-item><label>26. </label><p>26 <ext-link ext-link-type="uri" xlink:href="http://www.simdb.com/">http://www.simdb.com/</ext-link></p></list-item><list-item><label>27. </label><p>27 <ext-link ext-link-type="uri" xlink:href="http://www.w3.org/XML/Schema">http://www.w3.org/XML/Schema</ext-link></p></list-item><list-item><label>28. </label><p>28 <ext-link ext-link-type="uri" xlink:href="http://lcweb.loc.gov/z3950/agency/zig/">http://lcweb.loc.gov/z3950/agency/zig/</ext-link></p></list-item><list-item><label>29. </label><p>29 <ext-link ext-link-type="uri" xlink:href="http://lists.w3.org/Archives/Public/xmlschema-dev/2001Jun/0162.html">http://lists.w3.org/Archives/Public/xmlschema‐dev/2001Jun/0162.html</ext-link></p></list-item><list-item><label>30. </label><p>30 <ext-link ext-link-type="uri" xlink:href="http://www.ukoln.ac.uk/dlis/zdir/explainlite/">http://www.ukoln.ac.uk/dlis/zdir/explainlite/</ext-link></p></list-item><list-item><label>31. </label><p>31 <ext-link ext-link-type="uri" xlink:href="http://www.lib.ox.ac.uk/jafer">http://www.lib.ox.ac.uk/jafer</ext-link></p></list-item><list-item><label>32. </label><p>32 <ext-link ext-link-type="uri" xlink:href="http://www.infoteria.com/">http://www.infoteria.com/</ext-link></p></list-item><list-item><label>33. </label><p>33 <ext-link ext-link-type="uri" xlink:href="http://xml.apache.org">http://xml.apache.org</ext-link></p></list-item></list></sec><sec><fig position="float" id="F_2380190304001"><label><bold>Figure 1<x> </x></bold></label><caption><p>Input stylesheet</p></caption><graphic xlink:href="2380190304001.tif"></graphic></fig></sec><sec><fig position="float" id="F_2380190304002"><label><bold>Figure 2<x> </x></bold></label><caption><p>XSLT stylesheet</p></caption><graphic xlink:href="2380190304002.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>Gardner</surname>, <given-names>J.R.</given-names></string-name></person-group> and <person-group person-group-type="author"><string-name><surname>Rendon</surname>, <given-names>Z.</given-names></string-name></person-group> (<year>2001</year>), <source><italic>XSLT and XPath: Guide to Transformations Using XSLT</italic></source>, <publisher-name>Prentice‐Hall</publisher-name>, <publisher-loc>Upper Saddle River, NJ</publisher-loc>.</mixed-citation></ref><ref id="B2"><mixed-citation><person-group person-group-type="author"><string-name><surname>Putman</surname>, <given-names>J.R.</given-names></string-name></person-group> (<year>2001</year>), <source><italic>Architecting with RM‐ODP</italic></source>, <publisher-name>Prentice‐Hall</publisher-name>, <publisher-loc>Upper Saddle River, NJ</publisher-loc>.</mixed-citation></ref></ref-list><ref-list><title>Further reading</title><ref id="B3"><mixed-citation><person-group person-group-type="author"><string-name><surname>Bachmann</surname>, <given-names>F.</given-names></string-name></person-group> et al. (<year>2000</year>), <source><italic>Software Architecture Documentation in Practice: Documenting Architecture Layers</italic></source>, <publisher-name>Software Engineering Institute, Carnegie Mellon University</publisher-name>, <publisher-loc>Pittsburgh, PA</publisher-loc>, March.</mixed-citation></ref><ref id="B4"><mixed-citation><person-group person-group-type="author"><string-name><surname>Barbacci</surname>, <given-names>M.</given-names></string-name></person-group> et al. (<year>1995</year>), <source><italic>Quality Attributes</italic></source>, <publisher-name>Software Engineering Institute, Carnegie Mellon University</publisher-name>, <publisher-loc>Pittsburgh, PA</publisher-loc>, December.</mixed-citation></ref><ref id="B5"><mixed-citation><person-group person-group-type="author"><string-name><surname>Clements</surname>, <given-names>P.C.</given-names></string-name></person-group> and <person-group person-group-type="author"><string-name><surname>Northrup</surname>, <given-names>L.M.</given-names></string-name></person-group> (<year>1996</year>), <source><italic>Software Architecture: An Executive Overview</italic></source>, <publisher-name>Software Engineering Institute, Carnegie Mellon University</publisher-name>, <publisher-loc>Pittsburgh, PA</publisher-loc>, February.</mixed-citation></ref><ref id="B6"><mixed-citation><person-group person-group-type="author"><string-name><surname>Dikel</surname>, <given-names>D.M.</given-names></string-name></person-group>, <person-group person-group-type="author"><string-name><surname>Kane</surname>, <given-names>D.</given-names></string-name></person-group> and <person-group person-group-type="author"><string-name><surname>Wilson</surname>, <given-names>J.R.</given-names></string-name></person-group> (<year>2001</year>), <source><italic>Software Architecture: Organizational Principles and Patterns</italic></source>, <publisher-name>Prentice‐Hall,</publisher-name> <publisher-loc>Upper Saddle River, NJ</publisher-loc>.</mixed-citation></ref><ref id="B7"><mixed-citation><person-group person-group-type="author"><string-name>IEEE</string-name></person-group> P1471/D5.2 (<year>1999</year>), <source><italic>Draft Recommended Practice for Architectural Description</italic></source>, <publisher-name>IEEE Standards Department</publisher-name>, <publisher-loc>Piscataway</publisher-loc>, NJ, December.</mixed-citation></ref><ref id="B8"><mixed-citation><person-group person-group-type="author"><string-name><surname>Spewak</surname>, <given-names>S.H.</given-names></string-name></person-group> (<year>1992</year>), <source><italic>Enterprise Architecture Planning</italic></source>, <publisher-name>John Wiley & Sons</publisher-name>, <publisher-loc>New York, NY</publisher-loc>.</mixed-citation></ref></ref-list></back></article></istex:document></istex:metadataXml><mods version="3.6"><titleInfo lang="en"><title>Information architecture planning with XML</title></titleInfo><titleInfo type="alternative" lang="en" contentType="CDATA"><title>Information architecture planning with XML</title></titleInfo><name type="personal"><namePart type="given">John Robert</namePart><namePart type="family">Gardner</namePart><affiliation>John Robert Gardner is Deconstruction Architect, Sun MicroSystems, Burlington, Massachusetts, USA.</affiliation></name><typeOfResource>text</typeOfResource><genre type="review-article" displayLabel="review-article"></genre><originInfo><publisher>MCB UP Ltd</publisher><dateIssued encoding="w3cdtf">2001-09-01</dateIssued><copyrightDate encoding="w3cdtf">2001</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">The explosion of standards building on the 1998 XML specification from the World Wide Web Consortium has been slow to reach academic and library information science applications. While part of this is certainly due to cost, argues that adequate attention to architectural design, when considering XML technology, can make new forms of information management possible. Provides a survey of tools and relevant technology for working in Z39.50 with XML and MARC records, based primarily on a major undertaking by the ATLACERTR American Theological Library Association Center for Electronic Resources in Theology and Religion group at Emory University with 50 years of 50 journals digitized from philosophy, ethics, and religion.</abstract><subject><genre>keywords</genre><topic>Information management</topic><topic>Bibliographic standards</topic><topic>Internet</topic><topic>Programming</topic></subject><relatedItem type="host"><titleInfo><title>Library Hi Tech</title></titleInfo><genre type="journal">journal</genre><subject><genre>Emerald Subject Group</genre><topic authority="SubjectCodesPrimary" authorityURI="cat-IKM">Information & knowledge management</topic><topic authority="SubjectCodesSecondary" authorityURI="cat-ICT">Information & communications technology</topic><topic authority="SubjectCodesSecondary" authorityURI="cat-INT">Internet</topic></subject><subject><genre>Emerald Subject Group</genre><topic authority="SubjectCodesPrimary" authorityURI="cat-LISC">Library & information science</topic><topic authority="SubjectCodesSecondary" authorityURI="cat-IBRT">Information behaviour & retrieval</topic><topic authority="SubjectCodesSecondary" authorityURI="cat-LLM">Librarianship/library management</topic><topic authority="SubjectCodesSecondary" authorityURI="cat-IUS">Information user studies</topic><topic authority="SubjectCodesSecondary" authorityURI="cat-MTD">Metadata</topic><topic authority="SubjectCodesSecondary" authorityURI="cat-LTC">Library technology</topic></subject><identifier type="ISSN">0737-8831</identifier><identifier type="PublisherID">lht</identifier><identifier type="DOI">10.1108/lht</identifier><part><date>2001</date><detail type="volume"><caption>vol.</caption><number>19</number></detail><detail type="issue"><caption>no.</caption><number>3</number></detail><extent unit="pages"><start>231</start><end>241</end></extent></part></relatedItem><identifier type="istex">18C3BE9FADB588A694D7AB7ADD8F356BDBFCAD7B</identifier><identifier type="DOI">10.1108/07378830110405094</identifier><identifier type="filenameID">2380190304</identifier><identifier type="original-pdf">2380190304.pdf</identifier><identifier type="href">07378830110405094.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 000452 | SxmlIndent | more
Ou
HfdSelect -h $EXPLOR_AREA/Data/Istex/Corpus/biblio.hfd -nk 000452 | 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:18C3BE9FADB588A694D7AB7ADD8F356BDBFCAD7B
|texte= Information architecture planning with XML
}}
| This area was generated with Dilib version V0.6.31. |  |