📄 0341-0343.html
字号:
<!DOCTYPE HTML PUBLIC "html.dtd"><HTML><HEAD><TITLE>Presenting XML:Potential Applications of XML: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=18 //--><!-- PAGES=0331-0356 //--><!-- UNASSIGNED1 //--><!-- UNASSIGNED2 //--><P><CENTER><A HREF="0338-0340.html">Previous</A> | <A HREF="../ewtoc.html">Table of Contents</A> | <A HREF="0344-0346.html">Next</A></CENTER></P><A NAME="PAGENUM-341"><P>Page 341</P></A><P>Now compare this with the same equation marked up with content-based codes:</P><!-- CODE //--><PRE><EXPR> <EXPR> <EXPR> <MI>x</MI> <POWER> <MN>2</MN> </EXPR> <PLUS/> <EXPR> <MN>4</MN> <TIMES> <MI>x</MI> </EXPR> <MINUS/> <MN>1</MN> </EXPR> <E/> <MN>0</MN></EXPR></PRE><!-- END CODE //--><P>The two sets of markup give completely different views of the sameobjects: one as a set of pretty meaningless symbols that are positioned in relationto each other, where terms such as superscript (element<MSUP>) and subscript (element <MSUB>) have predominated, and another where the coderepresents a semantically meaningful statement consisting of expressions (element<EXPR>).</P><P>These two views of markup are, however, not irreconcilable and both havetheir place. Presentation markup is ideally suited for display and even providesa means for an expression to make sense when it is read out loud. Incontrast, content markup represents the mathematical meaning of an expression insuch a way that the statements can be understood.</P><P>Recognizing the need for both types of markup, MathML has taken aunique step and introduced a sort of "super element"—the<SEMANTIC> element. This element has twochildren. The first child is the presentation markup, andthe second child is semantic markup. Within MathML, the semanticmarkup would of course be a set of MathML content tags, but this is not arequirement. The content of the semantic markup could be a computer algebraexpression, or it could even be computer program source code (in C or even Java).</P><P>In its present incomplete form, XML has already given MathML apowerful means for specifying the structure and syntax of mathematics. More thanthis, XML has provided a flexible, extensible means to cater to current needswhile keeping options open for an unpredictable future. At some point in thefuture,</P><A NAME="PAGENUM-342"><P>Page 342</P></A><P> you can expect, or at least hope, that WWW browsers will be able tointerpret and properly render MathML codes. Until this happens, the MathMLapplication cannot call itself finished. The kind of powerful processing thatthe MathML working group already has in its dreams cannot yet beaccomplished in any browsers that are available or planned. It could even be argued thatthe browsers available now cannot accommodate this sort of processingbecause they are too presentation-centered. Java (and possibly JavaScript) probablywill provide the mechanisms that really do justice to all the promise ofMathML. Until then, you must wait for the XML style and document objectmodel standard developments to provide the basis for what will become a veryexciting future for mathematics publishing. (Chapter 17, "Resolution ofthe XML Specification," looks at the steps needed to complete the definitionof the XML specification.)</P><H4><A NAME="ch18_ 8">HL7</A></H4><P>The Health Level 7 (HL7, named after the seven layers that make theISO standard network model) group was founded in 1987 at the Hospital ofthe University of Pennsylvania, USA, to develop standards for the electronic <BR>interchange of clinical, financial, and administrative information betweenindependent medical computer systems (hospitals, clinical laboratories,medical insurers, pharmaceutical companies, and so on). The outcome of manyyears of hard work and dedication from this volunteer group is the HL7standard (now in version 3), which includes the following definitions:</P><UL><LI> The overall structure for all information interfaces, including ageneralized query interface<LI> Patient admission, discharge, transfer, and registration interfaces<LI> Order entry interfaces<LI> Patient accounting (billing) system interfaces<LI> Clinical observation data interfaces (for data such as laboratoryresults that are sent as identifiable data elements rather than asdisplay-oriented text)<LI> A generalized interface for synchronizing common referencefiles (master files)</UL><A NAME="PAGENUM-343"><P>Page 343</P></A><UL><LI> Medical information management system standards<LI> Standards for patient and resource scheduling interfaces<LI> Standards for messages concerning the referral of patients betweentwo institutions<LI> Standards for patient care messages that support thecommunication of problem-oriented records</UL><P>Looking at the preceding list, it should be quite apparent howinformation-intensive the health care industry is. Your whole medicalhistory—information possibly vital to your survival in the event of an accident—is floatingaround somewhere in every hospital, in every physician's surgery, in yourpharmacist's accounting system, in a thousand different places in a hundred differentforms. Therefore, it is perhaps a little surprising that there was no formal evidenceof any interest in the use of SGML until as late as April 1996. Since then,however, the HL7 SGML Special Interest Group (SIG)appears to have made up a lot of ground and has taken a very active and prominent role inpromoting the adoption of SGML (and more recently XML) and in the creation of astandard for the use of SGML in all domains of health care.</P><P>Although the SIG appears to always favor the use of "full" SGML, it isobvious that the group has not failed to take a sideways look at what has beenhappening on the World Wide Web and how successful HTML has been. Inan almost parallel effort commissioned by the British National Health Service,a study was conducted into the application of SGML and HTML forelectronic patient records. The draft report published by the SIG (in June 1997), asevidence of this attention, makes it quite clear that the DTD that the groupis developing for HL7 version 3.0 messages is compliant with both SGMLand XML.</P><P>The work of the HL7 SGML SIG has lately been gaining momentum.Recent legislation passed by the Unites States Congress (the 1996 HealthInsurance and Portability and Accountability Act, HIPAA), the increasing transfer ofthe burden of health care from hospital to home care settings, and the deepfinancial difficulties being experienced by many hospital and health careagencies have given the movement impetus. HIPAA legislation has since beenpassed that requires the Secretary of the Department of Health and HumanServices to select a standard by February 1999 for automated medical claimsprocessing, and it has fueled the intention to develop an XML application to be calledthe Health Care Markup Language (HCML).</P><P><CENTER><A HREF="0338-0340.html">Previous</A> | <A HREF="../ewtoc.html">Table of Contents</A> | <A HREF="0344-0346.html">Next</A></CENTER></P></TD></TR></TABLE></BODY></HTML>⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -