1、IEEE Std 2001-2002(Revision of IEEE Std 2001-1999)IEEE Standards2001TMIEEE Recommended Practice for theInternetWeb Site Engineering, WebSite Management, and Web Site LifeCyclePublished by The Institute of Electrical and Electronics Engineers, Inc.3 Park Avenue, New York, NY 10016-5997, USA3 March 20
2、03IEEE Computer SocietySponsored by theInternet Best Practices Working GroupIEEE StandardsPrint: SH95025PDF: SS95025Recognized as anAmerican National Standard (ANSI)The Institute of Electrical and Electronics Engineers, Inc.3 Park Avenue, New York, NY 10016-5997, USACopyright 2003 by the Institute o
3、f Electrical and Electronics Engineers, Inc.All rights reserved. Published 3 March 2003. Printed in the United States of America.DOI (Digital Object Identier)is a registered trademark of the DOI Foundation.IEEE is a registered trademarks in the U.S. Patent +1 978 750 8400. Permission to photocopy po
4、rtions of any individual standard for educationalclassroom use can also be obtained through the Copyright Clearance Center.Note: Attention is called to the possibility that implementation of this standard may require use of subject mat-ter covered by patent rights. By publication of this standard, n
5、o position is taken with respect to the existence orvalidity of any patent rights in connection therewith. The IEEE shall not be responsible for identifying patentsfor which a license may be required by an IEEE standard or for conducting inquiries into the legal validity orscope of those patents tha
6、t are brought to its attention.Copyright 2003 IEEE. All rights reserved.iiiIntroduction(This introduction is not part of IEEE Std 2001-2002, IEEE Recommended Practice for the InternetWeb Site Engi-neering, Web Site Management, and Web Site Life Cycle.)The World Wide Web is expanding and its value is
7、 increasing as a method for locating and delivering infor-mation. This creates a signicant engineering challenge. Locating applicable information requires thatindexing information be incorporated into Web page development. Once an applicable page has beenlocated, essential information may not be pre
8、sent, resulting in user frustration and a failure of the Web appli-cation to meet its purpose.This is a revision of the 1999 accumulation of Web site management “recommended practices.” This revi-sion is based on IEEE Std 2001-1999, extending it based on recommendations since it was developed,addres
9、sing “site-wide” issues as well as “managed” Web sites (as opposed to just Intranet and Extranetsites). These can serve to improve the effectiveness of Web pages for users, Web page developers, and thevalue of the Web in corporate and organizational applications. This recommended practice is focused
10、 onmanaged Web sites, Intranet (within an organization), and Extranet (between a group of collaborating orga-nizations). Other projects are being evaluated by the Internet Best Practices working group (IBPwg) withinthe IEEE Computer Society. See http:/dx.doi.org/10.1041/standard/2001 for current det
11、ails.Web page engineering often is done with little consideration for the immediate or ongoing implications ofWeb site design or implementation. Some sites reect “state of the art” delivery that can only be accessedwith the most recent tools. This may be inconsistent with the business objectives for
12、 that site. Some sites willlanguish beyond their applicable life, occupying valuable resources (particularly as these are incorporatedinto organizational indexes, and delivered as prospective “query returns” by indexing and search services).Poor Web page engineering results in lost productivity and
13、user frustration, and can result in legal liabilities.There is no clear prediction of when the World Wide Web or a specic site will be obsolete. There is a legit-imate engineering concern that this lifespan may be signicantly underestimated or disregarded entirely inmany Web site designs. Vendor pro
14、ductspast and future versions, format preferences, or selection ofimplementation languagesmay require future re-engineering as vendors and products fade. Corporate Websites may not need to live beyond the life of the corporation, however, public sector and other institutionalsites may well span cent
15、uries. A signicant portion of the content of these sites may not require updating,except in cases of shortsighted design. The Magna Carta and the works of Shakespeare are examples offairly stable content.The recommended practices and requirements set forth in this recommended practice are aimed to r
16、educethe risks associated with Web page investments. Further revision of this recommended practice is expected,partially to reect changes in the Web environment, but also to reect increased understanding of “recom-mended practices” in Web page engineering. There is a popular awareness of “Web years,
17、” characterized byrapid advances in the platform technology for clients and servers. There is a potentially expensive, misin-formed conclusion that might be drawn from this, which is that Web pages (and more directly, informationcontent and services delivery) either are, or should, move forward at t
18、his same rate. Some of todays Webpages will warrant long-term retention, and within the context of business operations (which is the core ofmanaged sites), re-engineering of last years Web pages is an investment that requires justication. The valueof Web-based operations is the delivery of the right
19、 information and services to the right persons at the righttime with the least amount of effort. Success in Web-based operations is based more on engineering designin response to an understanding of the target-user community and information, than it is on the rapidlyevolving technology for Web platf
20、orms.ivCopyright 2003 IEEE. All rights reserved.ParticipantsAt the time the Internet Best Practices Working Group (IBPwg) of the IEEE Computer Society completedthis recommended practice, it had the following membership:Paul Eastman,Chair, SAB Sponsored Projects (SAB), IEEE Computer SocietyJames D. I
21、saak,Chair, IBPwg, and Technical EditorEarl Meiers,Secretary and Technical EditorDon Folland,Technical EditorVinod AggarwalJulia AllenLuis AndreKen BartlettLouis BastarachePeter BenjaminGeorge BenoyM. BentRichard BirnbaumCornelia BoldyreffLaonie ButlerDino ButoracMassimo CardaciAlex ConnJean-Michel
22、CornuLuis CostaMatt DavisFrank FaranceAdam FarquharLil FloratosPete FloratosKen FongGary FordNorman GeeAlex GodleskiMike GwynneKarl HebenstreitKim HelsethDon HoldenDong HuaGael JeanneretTom JonesGary JoslinDavid KamishlianKari KruempelBill LaPlantSharon LaskowskiDon LewineMichael LinleyPei-wen LiuSt
23、eve LucasMassimo MarchioriRoger MartinJacques MathotWayne McCoy Thomas M. MeddaughTomas MontgomeryEd NemilIan NeumanJoan OwensPeter OwensMichael PacielloKetan PandyaAlan PeltzmanCatherine PinkaAnan Ponnambalam Mary E. PowersBrian QuinnPeter RandleWendy RauchChristine Rigden Helene RileyKen Rothermel
24、Andrew M. SchokaCharles SheppardBill SmithScott SmithPradip SrimaniFred StarkeyDennis SteinauerDavid SteinmetzSandra SwearingenHimanshu WarudkarJean-Marc WiseSuen WongZenta YungCopyright 2003 IEEE. All rights reserved.vThe following members of the balloting committee voted on this recommended practi
25、ce. Balloters may havevoted for approval, disapproval, or abstention.When the IEEE-SA Standards Board approved this recommended practice on 12 September 2002, it had thefollowing membership:James T. Carlo,ChairJames H. Gurney,Vice ChairJudith Gorman,Secretary*Member EmeritusAlso included are the fol
26、lowing nonvoting IEEE-SA Standards Board liaisons:Alan Cookson, NIST RepresentativeSatish K. Aggarwal, NRC RepresentativeAndrew IckowiczIEEE Standards Project EditorAndrew AbolaaFiorenza Albert-HowardEdward BartlettBakul BanerjeeD. J. BlackwoodMitchell BonnettDino ButoracJohn ColeMassimo CardaciJame
27、s T. CarloSue CarrollLawrence CatchpoleKeith ChowRosemary ColemanPaul CrollGuru Dutt DhingraGregory DaichTaz DaughtreyDavid DeightonBostjan DergancCosimo DistanteLuis Andre Dutra e SilvaJose Dominic EspejoLee FarrellDon FollandJuan GarbajosaGregg GieslerGarth GlynnCharles HammonsGeorge HayhoeMark He
28、nleyRonald HoferJames D. IsaakNeil JacobsonJerry JohnsonVladan JovanovicDwayne KnirkThomas M. KuriharaGeorge KyleSusan LandThomas LindahlClaire LohrGreg LuriEsperanza Marcos MartinezPeter MartiniJacques MathotIan McChesneyEarl MeiersPaul MenchiniJames MooreMary Lou PadgettRoger PandandaLuiz Claudio
29、ParzianelloLou PintoTerrill RayKen Rothermel, Jr.James RuggieriRandy SaundersNorman SchneidewindAndrew SchokaMitchell SmithDavid SteinmetzSandra SwearingenRobert TripiT. H. TseMark-Rene UchidaScott ValcourtPaul WorkTom WorthingtonDon WrightOren YuenJanusz ZalewskiSid BennettH. Stephen BergerClyde R.
30、 CampRichard DeBlasioHarold E. EpsteinJulian Forster*Howard M. FrazierToshio FukudaArnold M. GreenspanRaymond HapemanDonald M. HeirmanRichard H. HulettLowell G. JohnsonJoseph L. Koepnger*Peter H. LipsNader MehravariDaleep C. MohlaWilliam J. MoylanMalcolm V. ThadenGeoffrey O. ThompsonHoward L. Wolfma
31、nDon WrightviCopyright 2003 IEEE. All rights reserved.Contents1. Overview 11.1 Scope 11.2 Purpose. 11.3 Conformance 22. References 33. Definitions, terminology, abbreviations and acronyms . 43.1 Definitions 43.2 Terminology. 53.3 Abbreviations and acronyms 64. Design practices. 64.1 General requirem
32、ents. 74.2 Environment selection . 124.3 Scripting languages and Java. 185. Server, HTTP and site considerations 195.1 HTTP 1.1 application. 195.2 Cache expiration date. 195.3 Non-caching. 195.4 Browser language selection . 195.5 Robot exclusion . 205.6 Browser tolerance 205.7 Webmaster contact. 205
33、.8 Redirection. 205.9 Compression 215.10 Site conventions 215.11 Web site center page . 215.12 Site index and search 226. Header information 236.1 Document type declaration 236.2 Title 236.3 Metadata. 236.4 Digital signature. 257. Body information. 257.1 Sensitive information exposure 257.2 Intellec
34、tual property rights (IPR). 257.3 Security designations . 267.4 Dates and time 277.5 International considerations. 287.6 Bandwidth efficiencies. 317.7 Navigation aids 31Copyright 2003 IEEE. All rights reserved.vii7.8 Active links 327.9 Dead links 327.10 Absolute and relative links 327.11 Cookies . 3
35、37.12 Frame considerations 337.13 Graphical images 347.14 Deprecated HTML elements and attributes 347.15 Physical location information . 347.16 Server technology independence 357.17 Flushing search engines 35Annex A (informative) Bibliography . 36Annex B (informative) Potential areas of future or ad
36、ditional work 43Annex C (normative) XML tags and HTML attribute values 44Annex D (informative) Metadata for indexing and classification 46Annex E (normative) Robot exclusion . 50Annex F (informative) Privacy statement text 52Annex G (informative) Requirements checklist. 54Annex H (informative) Color
37、 combinationsnumerical and visual color tables 62Annex I (normative) 36 CFR 1194 connections. 65Index 68Copyright 2003 IEEE. All rights reserved.1IEEE Recommended Practice for the InternetWeb Site Engineering, Web Site Management, and Web Site Life Cycle1. OverviewThis recommended practice provides
38、guidance for designing and implementing well-engineered Web pagesfor use in managed Web sites. The goal of this recommended practice is to improve the productivity of man-aged Web operations in terms of:a) locating relevant information,b) facilitating ease of use,c) reducing legal liabilities, andd)
39、 providing for efcient development and maintenance practices.This recommended practice will focus on vendor- and product-independent considerations.This recommended practice provides guidance for persons designing and developing Web pages, and man-agers responsible for establishing guidelines for We
40、b site development.1.1 ScopeThis document denes recommended practices for World Wide Web page engineering for Intranet andExtranet environments, based on World Wide Web Consortium (W3C) and related industry guidelines.This recommended practice does not address stylistic considerations or human-facto
41、rs considerations inWeb page design beyond limitations that reect good engineering practice. Annex B contains topics whichare not sufciently mature or where there are not specic recommendations for inclusion in the current issueof this recommended practice.1.2 PurposeThis recommended practice is int
42、ended to provide guidance to Web page developers in Intranet (organiza-tional internal), and Extranet (amongst a limited domain of organizational participants) Web environmentson recommended practices for Web page engineering. The objective is to improve the productivity of Intra-net/Extranet Web op
43、erations in terms of locating relevant information, and efcient development and main-tenance practices. The 2002 revision of this recommended practice addresses items identied in Annex A of IEEE Std 2001-1999 B141which can be well-dened and to respond to emerging technology and changes in practice t
44、hathave resulted in new material or changes to approved recommendations. Conformance to this recommendedpractice in developing and publishing a Web site provides a basis for a well-engineered Web site.1The numbers in brackets correspond to those of the bibliography in Annex A.IEEEStd 2001-2002 IEEE
45、RECOMMENDED PRACTICE FOR THE INTERNETWEB SITE2Copyright 2003 IEEE. All rights reserved.1.3 ConformanceThis recommended practice denes two forms of conformance: “IEEE Std 2001-2002-conforming Webpage” and “IEEE Std 2001-2002-conforming Web page generation tool.” Throughout this recommendedpractice, t
46、he use of the verb shallindicates a requirement of the standard; the use of the verb shouldindicatesa recommendation; and the use of the verb mayindicates an option or variation that is permitted by the rec-ommended practice. Although users of this recommended practice are strongly encouraged to con
47、sider therecommendations made within, the implementation of recommendations is not a requirement of Web pageconformance.1.3.1 IEEE Std 2001-2002-conforming Web page A conforming Web page implements all the requirements of this recommended practice. A Web page thatconforms to this recommended practic
48、e may indicate this by the use of the following tag:NOTEThe HTML Reference Designator (HREF value will change with each version of this recommended practice.Tools should use the HREF value to determine the version of the standard being used.The image le may be downloaded and referenced using relativ
49、e Uniform Resource Identiers (URIs), butthe target HTML le must be referenced by an absolute URI.Consistent with 4.1.10 of this recommended practice, a meta statement indicating conformance to this rec-ommended practice may be included. This statement is: “1.3.2 IEEE Std 2001-2002-conforming Web page generation toolA product for generating well-engineered Web pages dynamically, or as an authoring tool, conforms to IEEEStd 2001-2002 if it satises all of the following conditions:a) It generates pages that conform to the XHTML DTD recommenda
