<?xml version="1.0" encoding="utf-8"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>TRB Publications Index</title><link>http://pubsindex.trb.org/</link><atom:link href="http://pubsindex.trb.org/common/TRIS Suite/feeds/rss.aspx?tc=NN%3AXbbccdx" rel="self" type="application/rss+xml" /><description></description><language>en-us</language><copyright>Copyright © 2015. National Academy of Sciences. All rights reserved.</copyright><docs>http://blogs.law.harvard.edu/tech/rss</docs><managingEditor>tris-trb@nas.edu (Bill McLeod)</managingEditor><webMaster>tris-trb@nas.edu (Bill McLeod)</webMaster><image><title>TRB Publications Index</title><url>http://pubsindex.trb.org/Images/PageHeader-wTitle.png</url><link>http://pubsindex.trb.org/</link></image><item><title>The Future of TransXML: Workshop Summary</title><link>http://pubsindex.trb.org/view/1309816</link><description><![CDATA[Planning, designing, constructing, and operating transportation systems involve the exchange of large volumes of data. The lack of common data formats to facilitate the exchange of data across different business platforms has been a limiting factor for transportation agencies, vendors, contractors, and other groups. The eXtensible Markup Language (XML) represents a universal structured data transfer methodology that helps facilitate e-business and e-government. XML data structures, or schemas, provide a mechanism to develop and adopt common formats for data exchange.  A National Cooperative Highway Research Program (NCHRP) project completed in 2006 examined the potential of using the XML data structure in transportation and developed TransXML, an open vendor-neutral format for storing, exchanging, and archiving transportation data. This circular summarizes proceedings from  a workshop that focused on potential future development and implementation of TransXML. The Workshop on the Future of TransXML had six general objectives:  1) communicate the content of existing TransXML schema and potential future schema; 2) discuss the benefits and business value of building on TransXML; 3) gain a better understanding of the activities critical to furthering development, adoption, and maintenance of TransXML; 4) explore partnership opportunities and alternative approaches; 5) identify a possible TransXML stewardship framework and process for developing, maintaining, and updating TransXML schema; and 6) identify potential follow-up activities. The major topics addressed in the morning general sessions are highlighted in this circular. The discussions in the afternoon working sessions are summarized and potential approaches for moving forward are presented.]]></description><pubDate>Wed, 21 May 2014 11:45:16 GMT</pubDate><guid>http://pubsindex.trb.org/view/1309816</guid></item><item><title>Framework for Extending TransXML for Steel Bridge Construction</title><link>http://pubsindex.trb.org/view/1091622</link><description><![CDATA[NCHRP Project 20-64  developed a set of Extensible Markup Language (XML) schemata, called TransXML to facilitate interoperability among transportation software applications.  But the bridge structure schemata were not formulated to encompass bridge construction.  The research described herein addresses one of the gaps in the development of comprehensive TransXML schemata, i.e for steel bridge construction.  When this gap is filled the resulting Steel Bridge Information Modeling ( BrIM) framework is anticipated to serve the needs of bridge owners beyond analysis and design into accelerated bridge construction processes and in-service asset management of steel bridges.   Uniform Markup Language (UML) methodology is used to build lexicon and modeling constructs to serve as a foundational framework for encompassing comprehensive steel bridge construction domain data.  This framework will facilitate XML based data transfer by various members of the design and construction team.  By using the transferred information and starting from a 3D basic model, the fabricator can add on to the design information directly. The framework created and schema produced is evaluated by volunteer stake holders with in the bridge industry for correctness and missing model constructs. The developed framework is validated in part by a Python programming language implementation.  By providing a common vocabulary and information structure for steel bridge related elements, the framework serves as a powerful basis and tool to advance the use of XML based data model integration towards achieving a robust BrIM based integrated project delivery process and allows easier information flow, storage and retrieval.]]></description><pubDate>Tue, 24 May 2011 14:57:12 GMT</pubDate><guid>http://pubsindex.trb.org/view/1091622</guid></item><item><title>Development of XML-Based File Format for Exchange of Road Safety Audit Report Findings</title><link>http://pubsindex.trb.org/view/880744</link><description><![CDATA[Information exchange and interoperability is critical to any successful project or task.  Currently, XML provides the means necessary to ensure data interoperability and simple means for its exchange.  This work presents a file format based on an XML structure for storing the results of road safety audits.  The format presented is capable of storing photographs of the different features identified during the audit process along with attributes and position information for each of the features.  A software application prototype is developed to allow the visualization of the findings using a map-based interface.  The safety audit data used can be generated by extending the capabilities of existing software, capable of performing virtual safety audits, to report its findings using the proposed file format.]]></description><pubDate>Mon, 30 Mar 2009 14:11:04 GMT</pubDate><guid>http://pubsindex.trb.org/view/880744</guid></item><item><title>Scenario-Driven Computer-Based Regional Incident Management Training</title><link>http://pubsindex.trb.org/view/847743</link><description><![CDATA[Incident management is one of the most important functions of a transportation management center (TMC). To efficiently and effectively manage complex regional incidents that affect transportation facilities under the jurisdiction of multiple agencies, TMC operators must be trained appropriately. Recently, a team of universities including the University of Maryland, University of Virginia, and Rensselaer Polytechnic Institute developed a computer-based training tool for regional incident management to be used by the I-95 Corridor Coalition. In its role on the team, the University of Virginia conducted research to support the development of detailed regional incident scenarios to provide content for the computer-based simulation tool. The method created to develop the incident scenarios is presented, with clear examples. Major findings from the research effort include the benefits of rapid prototyping and the usefulness of extensible markup language (XML) for structured content development.]]></description><pubDate>Mon, 31 Mar 2008 08:04:43 GMT</pubDate><guid>http://pubsindex.trb.org/view/847743</guid></item><item><title>TransXML: XML Schemas for Exchange of Transportation Data</title><link>http://pubsindex.trb.org/view/806274</link><description><![CDATA[This report develops a proposed common framework for exchange of transportation data in eXtensible Markup Language, known as TransXML.  This framework can be used for developing, validating, disseminating, and extending current and future schemas.  The research team conducted an extensive review of current XML efforts in the transportation sector, identified specific gaps and opportunities, and developed a plan to address the highest priority needs.  The team developed a number of pilot schemas and applications, as well as recommendations for tools and platforms that can simplify XML coding for other transportation applications.  The report summarizes the benefits that can be achieved by the adoption and expansion of TransXML, and outlines future efforts that will be needed to ensure its success.]]></description><pubDate>Fri, 13 Apr 2007 15:21:52 GMT</pubDate><guid>http://pubsindex.trb.org/view/806274</guid></item><item><title>Methodology for Selection and Development of TransXML Schemas</title><link>http://pubsindex.trb.org/view/801610</link><description><![CDATA[NCHRP Project 20-64, TransXML, solicited the development of standard, public domain extensible markup language (XML) schemas for the exchange of transportation data as well as the creation of a framework for the development, validation, dissemination, and extension of current and future schemas. The methodology used for the selection and development of the initial set of TransXML schemas ensured their consistency, cohesiveness, and usefulness. Data flow diagrams of the design and construction process had previously been developed for the Minnesota Department of Transportation. They articulate steps in the design process as well as the flow of data between these steps. The diagrams were analyzed to discover candidate data flows that if supported by standardized XML schemas, could improve the design and construction process. The content and structure of the data identified were then modeled with unified modeling language (UML) class diagrams—roughly one UML package per data flow. Consensus of interested parties was achieved through the project website, including specific agreement on data elements and their associations. For each element, relevant attributes were decided, along with their cardinality and data type. For associations, relationship types, cardinalities, and roles were established. Diagrams for each area were compared to achieve consistency and to identify common elements, the latter being extracted into separate UML packages. XML schemas were then developed, based on the UML packages. The geography markup language (GML) was used as the framework for the schemas, building on predefined GML elements and following GML rules for developing application schemas. Sample applications were developed to demonstrate how the schemas support the data flows.]]></description><pubDate>Tue, 06 Mar 2007 14:39:58 GMT</pubDate><guid>http://pubsindex.trb.org/view/801610</guid></item><item><title>DEVELOPMENT OF TRAFFICXML: PROTOTYPE XML FOR TRAFFIC SIMULATION</title><link>http://pubsindex.trb.org/view/747438</link><description><![CDATA[With the wide adoption of XML as a standard means of data representation and exchange, more XML-aware applications and open resources are added to the library.  It is therefore beneficial for the transportation community to develop an industrywide common language not only to leverage the open resources but also to ease external and internal communication. A prototype of XML-based language, TrafficXML, was developed for data representation in traffic simulation, and the prototype was formally defined in an XML schema.  Discussions include the role of XML in traffic simulation, procedures for developing and applying the prototype, and issues of validation with an XML schema.  As an illustrative example, the prototype was applied to KWaves, an enhanced macroscopic traffic simulation software built on Java and XML technologies.]]></description><pubDate>Thu, 13 Jan 2005 00:00:00 GMT</pubDate><guid>http://pubsindex.trb.org/view/747438</guid></item><item><title>ENABLING AND MANAGING GREATER ACCESS TO TRANSPORT DATA THROUGH METADATA</title><link>http://pubsindex.trb.org/view/729390</link><description><![CDATA[Metadata--information about data sets--allow clear understanding of exactly what the elements and structure of a given data set entail.  Metadata in conjunction with XML-based specifications, schemas, and tools allow a high level of automated and validated interworking between different types and sources of data.  This is an issue of emerging importance to transportation, traffic, and planning, and the communities they serve, as these areas are all data intensive but with very different views of the world. The potential of this linkage is outlined, and a progression is made through a simple example metadata specification for nonmotorized transport, the agreements developed by the geospatial community for geographic data and the transport layers within them, and the formal XML document.  The XML specification and validation approach now makes possible and practical a more effective and more accessible use of the information in the multiple fields linked through their involvement in transportation.  The key outcome required is a vocabulary (or integrated vocabularies) of globally agreed-upon metadata element definitions for the various fields in and overlapping transportation.  The advent of formal document specifications of which XML is a widely used example would then allow a significant expansion of the accessibility, use, and reuse of such data to the great benefit of the user, policy, and analysis user communities.]]></description><pubDate>Wed, 10 Dec 2003 00:00:00 GMT</pubDate><guid>http://pubsindex.trb.org/view/729390</guid></item><item><title>DEVELOPMENT OF AN XML-BASED SPECIFICATION FOR TRAFFIC MODEL DATA EXCHANGE</title><link>http://pubsindex.trb.org/view/729402</link><description><![CDATA[The proliferation of traffic software programs on the market has resulted in many very specialized programs, intended to analyze one or two specific items within a transportation network. Consequently, traffic engineers use multiple programs on a single project, which ironically has resulted in new inefficiency for the traffic engineer.  Most of these programs deal with the same core set of data, for example, physical roadway characteristics, traffic demand levels, and traffic control variables.  However, most of these programs have their own formats for saving data files.  Therefore, these programs cannot share information directly or communicate with each other because of incompatible data formats.  Thus, the traffic engineer is faced with manually reentering common data from one program into another.  In addition to inefficiency, this also creates additional opportunities for data entry errors.  XML is catching on rapidly as a means for exchanging data between two systems or users who deal with the same data but in different formats. Specific vocabularies have been developed for statistics, mathematics, chemistry, and many other disciplines.  The traffic model markup language (TMML) is introduced as a resource for traffic model data representation, storage, rendering, and exchange.  TMML structure and vocabulary are described, and examples of their use are presented.]]></description><pubDate>Wed, 10 Dec 2003 00:00:00 GMT</pubDate><guid>http://pubsindex.trb.org/view/729402</guid></item><item><title>XML-BASED TRANSIT TIMETABLE SYSTEM</title><link>http://pubsindex.trb.org/view/729403</link><description><![CDATA[The Internet and the World Wide Web are used for a wide variety of transportation applications.  Most of these applications use static HTML documents.  However, outside of transportation, considerably more attention is being given to dynamic content and XML.  A way in which these technologies can be used to provide transit timetable information on the web is explored. Specifically, the transit timetable system, an online interactive transit timetable information exchange and administration system that uses Java server pages and the transit timetable markup language, is described.]]></description><pubDate>Wed, 10 Dec 2003 00:00:00 GMT</pubDate><guid>http://pubsindex.trb.org/view/729403</guid></item></channel></rss>