TransXML: XML Schemas for Exchange of Transportation Data (2007) / Chapter Skim
Currently Skimming:
Pages 31-43
The Chapter Skim interface presents what we've algorithmically identified as the most significant single chunk of text within every page in the chapter.
Select key terms on the right to highlight them within pages of the chapter.
From page 31... ...
The UML modeling effort is described in Section 5.4. • Develop XML schema and sample applications.
|
From page 32... ...
Exchange of design project pay item data across design, cost estimation, and bid preparation software. Renamed from "Contract Pay Items" in original Schema Development Plan.
|
From page 33... ...
If acronyms are used, they will be spelled out within schema annotations. Even with adoption of the schema development standards described above, the W3C XML Schema specification leaves considerable room for structural and stylistic differences across schema developers.
|
From page 34... ...
Construction/Materials • AASHTO, • FHWA, • Construction management software vendors, • Construction contractors, • aecXML Infrastructure Working Group participants, and • Current IAI aecXML Domain Committee members. Bridge Structures • AASHTO Virtis/Opis Panel, • Bridge software developers, • Bridge design firms, and • DOT bridge engineers.
|
From page 35... ...
This diagram conveys the following information: • A road project is composed of 0 or more road project pay items. • A road project has three attributes: a project number, a project name, and a project engineer.
|
From page 36... ...
was used to transfer model information across the two tools. Standard conventions for the TransXML UML models were established and documented for use by the data modelers from the four business areas.
|
From page 37... ...
As part of the UML modeling process, some common building blocks were identified and packaged into three separate components for inclusion in multiple schema. These components are as follows: • A linear referencing schema based on ISO 19133, • A reference schema that can be used to store master lists of project pay items or funding sources, and • A TransXML base schema with various shared elements (e.g., addresses, phone numbers, project identifiers)
|
From page 38... ...
Design Project Schema Description The aecXML Infrastructure schema provided the means for roadway designers to obtain information about possible pay items available for use on a design project, and allowed them to specify which of these will actually be used on the project. The TransXML Design Project schema builds on this and adds pay item quantity and cost information.
|
From page 39... ...
The TransXML Bid Package schema package incorporates the TransXML Design Project, Reference, and Linear Referencing schemas. A sample application was developed using XSLT to create an HTML Bid Package report from an XML instance document based on the TransXML Bid Package XML Schema.
|
From page 40... ...
The TransXML Materials Sampling and Testing schema package incorporates the TransXML Design Project, Construction Progress, and Reference schemas. An application was developed using XSLT to produce a webpage showing the sampling and testing activity for a material sample as described in a TransXML Material Sampling and Testing XML instance document.
|
From page 41... ...
A sample application, the TransXML Bridge Input Converter, was developed to demonstrate the translation of a Bridge TransXML instance document produced by one piece of bridge analysis software to a format that could be interpreted by another bridge analysis software package. An example is provided with the application that uses a TransXML instance document of a prestressed concrete bridge generated from the AASHTO Virtis database to create an input file that can be processed by the Pennsylvania Department of Transportation's LRFD Prestressed Concrete Girder Design and Rating (PENNDOT PSLRFD)
|
From page 42... ...
As TransXML evolves beyond Project 20-64, it would be our recommendation to include Framework inside TransXML with appropriate connections to HISA. A sample application was developed that allows users to search through crash records stored using the NHTSA MMUCC XML schema, and to link these crash records to related highway safety information stored using the HISA schema.
|
From page 43... ...
• ANSI Standard D20-2003 Data Element Dictionary for Traffic Records Systems, American Association of Motor Vehicle Administrators, April 2003; • 2004 Fatal Accident Reporting System Coding and Validation Manual, NHTSA; • Transportation Safety Information Management System, Phase I Consolidated Report, prepared by Littleton PRC, June 2001; • Transportation Safety Information Management System Data Dictionary; • American National Standard for Information Technology -- Geographic Information Framework -- Data Content Standards For Transportation Networks: Roads, Information Technology Industry Council; • Highway Performance Monitoring System Manual; and • FHWA SafetyAnalyst data dictionary (draft)
|
Key Terms
This material may be derived from roughly machine-read images, and so is provided only to facilitate research.
More
information on Chapter Skim is available.