📄 0280-0282.html
字号:
<!DOCTYPE HTML PUBLIC "html.dtd"><HTML><HEAD><TITLE>Presenting XML:Creating an XML Museum Information Application:EarthWeb Inc.-</TITLE><META NAME="ROBOTS" CONTENT="NOINDEX, NOFOLLOW"><SCRIPT><!--function displayWindow(url, width, height) { var Win = window.open(url,"displayWindow",'width=' + width +',height=' + height + ',resizable=1,scrollbars=yes');}//--></SCRIPT></HEAD><BODY BGCOLOR="#FFFFFF" VLINK="#DD0000" TEXT="#000000" LINK="#DD0000" ALINK="#FF0000"><TD WIDTH="540" VALIGN="TOP"><!-- <CENTER><TABLE><TR><TD><FORM METHOD="GET" ACTION="http://search.itknowledge.com/excite/cgi-bin/AT-foldocsearch.cgi"><INPUT NAME="search" SIZE="20" VALUE=""><BR><CENTER><INPUT NAME="searchButton" TYPE="submit" VALUE="Glossary Search"></CENTER><INPUT NAME="source" TYPE="hidden" VALUE="local" CHECKED> <INPUT NAME="bltext" TYPE="hidden" VALUE="Back to Search"><INPUT NAME="sp" TYPE="hidden" VALUE="sp"></FORM></TD><TD><IMG SRC="http://www.itknowledge.com/images/dotclear.gif" WIDTH="15" HEIGHT="1"></TD><TD><FORM METHOD="POST" ACTION="http://search.itknowledge.com/excite/cgi-bin/AT-subscriptionsearch.cgi"><INPUT NAME="search" SIZE="20" VALUE=""><BR><CENTER><INPUT NAME="searchButton" TYPE="submit" VALUE=" Book Search "></CENTER><INPUT NAME="source" TYPE="hidden" VALUE="local" CHECKED> <INPUT NAME="backlink" TYPE="hidden" VALUE="http://search.itknowledge.com:80/excite/AT-subscriptionquery.html"><INPUT NAME="bltext" TYPE="hidden" VALUE="Back to Search"><INPUT NAME="sp" TYPE="hidden" VALUE="sp"></FORM></TD></TR></TABLE></CENTER> --><!-- ISBN=1575213346 //--><!-- TITLE=Presenting XML//--><!-- AUTHOR=Richard Light//--><!-- PUBLISHER=Macmillan Computer Publishing//--><!-- IMPRINT=Sams//--><!-- CHAPTER=14 //--><!-- PAGES=0263-0282 //--><!-- UNASSIGNED1 //--><!-- UNASSIGNED2 //--><P><CENTER><A HREF="0276-0279.html">Previous</A> | <A HREF="../ewtoc.html">Table of Contents</A> | <A HREF="../ch15/0283-0286.html">Next</A></CENTER></P><A NAME="PAGENUM-280"><P>Page 280</P></A><P>The following is how that production entry might be written as anordinary sentence, yet still be fully marked up:</P><!-- CODE //--><PRE><PRODUCTION>Drawn in <METHOD><k>pencil</k>and <k>watercolour</k></METHOD>by <PERSON><name><forename>George Price</forename><surname>Boyce</surname> (b1826 d1897)</name>(<role>draughtsman</role>)</PERSON>in <DATE><k>1864</k> (d)</DATE>.</PRODUCTION></PRE><!-- END CODE //--><TABLE BGCOLOR="#FFFF99"><TR><TD>Note:</TD></TR><TR><TD><BLOCKQUOTE>The inverted form of the artist's name (Boyce, George Price) hasbeen turned around, and subelements forename andsurname have been added to retain this information. The inverted form was used in the first place sothat personal names would sort, and can be searched for, by surname. Therewill always be a tension between the requirements of retrieval (which usually areof a consistent, formal presentation) and free text when you are trying tomake one piece of structured text serve both purposes. Another strategy youcan adopt is to hold the searchable form of a name as an attribute value where itis "hidden" when the data content is viewed, such as in thefollowing:<!-- CODE SNIP //--><PRE><person KEY="Boyce, George Price">George Price Boyce</person></PRE><!-- END CODE SNIP //--></BLOCKQUOTE></TD></TR></TABLE><P>The second major opportunity that the XML-compatible version ofMODES offers is in the area of linking. Up to now, MODES applications havebeen very object-centered, with information such as a donor's name and addressbeing buried deep within each object's record and repeated each time that donorgives an object. This creates additional recording work and a maintenanceheadache. (If the donor relocates, you have a lot of records to update!)</P><P>With the improved linking offered by XML, this information can be held ina separate donor file. Each record will just contain a link to the donor'sentry—no more redundancy. If the donor relocates, you have only one entry toupdate and all the references will automatically stay current. From a datamaintenance point of view, this is as good as having a relational database.</P><P>This approach can also open up a new, broader way of managingmuseum information. Museums, and their public, have always been interested inthe relationships of museum objects to the real world: who owned them,what events they commemorate, places they were used. It now becomesstraightforward for MODES users to create separate files for historical people,events, and places of relevance to the collection, and to link them to the objectrecords. Also, these need not be one-way links. XML extended links would let youstart</P><A NAME="PAGENUM-281"><P>Page 281</P></A><BR>from the description of a place and navigate to all the objects in thecollection that have associations with that place.<P>Best of all, because XML links work on the Web, there is no need forthe museum to create all of these additional resources. If a commercialpublisher has put a detailed gazetteer of the UK on the Web in XML format (or evenin HTML), why not link to that? Also, links can go the other way. Whenthe museum collection is established as an XML resource on the Web, other <BR>information providers will start to make links into its object records.Each information provider can concentrate on her own area of expertise and still <BR>contribute to an information base that is greater than the sum of itsparts.</P><H3><A NAME="ch14_ 17">Summary</A></H3><P>In this chapter I have taken a look around the world of museums to seewhat it reveals about the potential use of XML.</P><P>You learned about the issue of interchange—delivering structuredinformation reliably across the Web. Museums routinely need to interchangeinformation about objects in their collections. I showed how XML can support <BR>interchange among heterogeneous systems, but only if there iscommunity agreement on the semantics of the information itself. In the case of UKmuseums, the SPECTRUM standard provides that framework. A secondexample of interchange I touched on is the delivery and updating of authority files,and how to tie local extensions into the standard authority scheme.</P><P>I examined in broad terms the advantages that XML might offer to anindividual museum in its own work. I showed that it provides a much neededframework for getting better value from textual material. XML can also pull togetherthe rich and varied types of information resources that a museum has tomanage. And it can help researchers create meta-catalogs of the objects they areinterested in describing and comparing.</P><P>Finally, I took as a case study the MODES cataloging software. Thisshowed how an existing database can put on an XML face without having tochange the way it actually works. You saw how the new XML-aware MODES willlet museums adopt a more natural cataloging style. More generally, theexample of museums showed how the development of XML-linkedinformation resources can take you beyond single providers acting as publishers, to asituation where multiple providers interlink their resources to provide anever-growing Web-based infobase.</P><A NAME="PAGENUM-282"><P>Page 282</P></A><P><CENTER><A HREF="0276-0279.html">Previous</A> | <A HREF="../ewtoc.html">Table of Contents</A> | <A HREF="../ch15/0283-0286.html">Next</A></CENTER></P></TD></TR></TABLE></BODY></HTML>⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -