Click for next page ( 35


The National Academies | 500 Fifth St. N.W. | Washington, D.C. 20001
Copyright © National Academy of Sciences. All rights reserved.
Terms of Use and Privacy Statement



Below are the first 10 and last 10 pages of uncorrected machine-read text (when available) of this chapter, followed by the top 30 algorithmically extracted key phrases from the chapter as a whole.
Intended to provide our own search engines and external engines with highly rich, chapter-representative searchable text on the opening pages of each chapter. Because it is UNCORRECTED material, please consider the following text as a useful but insufficient proxy for the authoritative book pages.

Do not use for reproduction, copying, pasting, or reading; exclusively for search engines.

OCR for page 34
35 property approach encouraged stronger typing, which Construction/Materials reduces the ambiguity evident in less structured approaches. AASHTO, There was no significant difference in the instance docu- FHWA, ments (.XML files) from the XML and GML schemas. GML Construction management software vendors, has a few extra lines for tags due to the object-property dis- Construction contractors, tinction. The difference in case (UpperCamelCase con- aecXML Infrastructure Working Group participants, and vention for objects, lowerCamelCase for properties) for Current IAI aecXML Domain Committee members. element tags clarifies the difference. The XSL documents which generate sample reports from XML and GML instance documents are virtually identical due to the similarity in Bridge Structures instance documents. AASHTO Virtis/Opis Panel, Bridge software developers, In order to reduce overhead in processing of GML-based Bridge design firms, and TransXML schema, a decision was made to use a subset of DOT bridge engineers. GML for TransXML. This subset of GML 3.1.1 is based on the current OGC proposal for Simple Feature GML (SFGML), in OGC 05-033r24, GML simple features profile, Appendix D, Highway Safety March 7, 2006. NHTSA, FHWA Safety Office/Turner Fairbank Highway Research 5.3 Stakeholder Involvement Center, The Association of Traffic Safety Information Professionals Stakeholder Identification (ATSIP), and Communication National Safety Council, Iowa DOT TraCS Consortium, Stakeholders for each of the business areas were identified, AASHTO TSIMS representative(s), and an e-mail list was developed to inform these individuals GLOBAL JusticeXML, and and groups about the TransXML project and encourage their COMCARE Alliance. participation. Information about the project was also sent to the AASHTO and TRB liaisons at all state DOTs, and to rele- vant TRB committee chairs for further distribution. The May Collaborative Website 2005 TRB e-newsletter included a blurb on the project with a An interactive website was developed to enable a collabo- link to the TransXML website. Presentations on TransXML rative process of schema development. The "transxml.net," were given at the September 2004 International Highway Engi- "transxml.org," and "transxml.com" domain names were neering Exchange Program conference in Lincoln, Nebraska; reserved and were directed at this site. The website included the January 2005 TRB annual meeting in Washington, D.C.; the following features: the May 2005 AASHTO Information Systems Subcommittee meeting in Baton Rouge, Louisiana; and the August 2005 Background information on the TransXML project, includ- Traffic Records Forum in Buffalo, New York. Two press ing an overview presentation on the project that can be releases for the project were issued--one in the spring of 2005 downloaded, a list of contacts, and schedule information; and a second in January 2006. Articles on the project were pub- Links to external sources of information about related lished in the AASHTO Journal in May 2005; and in the Spring XML and data standards efforts; 2005 edition of the AASHTO Trnsport News. A section for each business area, with capabilities for stake- Key stakeholder groups identified for the different business holders to review sources and resource materials, down- areas were as follows. load draft documents, submit comments and proposed revisions, and participate in threaded discussions on rele- Roadway Survey/Design vant topics; Automated notification for interested registered users when DOT design divisions, new material is added to specific areas of the site; and Civil design software vendors, A protected area for the development team to share docu- Engineering firms, ments and links to external resources. LandXML.org, aecXML Infrastructure Working Group participants, and A moderator was assigned for each of the four business Current IAI aecXML Domain Committee members. areas. Moderators were responsible for posting relevant