Default HTML page and Read Me for :

The ITS Schema Repository

The open XML schema project for ITS deployments

Found at:  www.ITSware.net/ITSschemas/       Last Update Oct 11th 2006

 

 

The schema sets found in this file area represent both draft and final adopted releases of standards efforts from the primary ITS standards organizations, as well as schema sets devised by local deployments for their own needs. You are free to browse this directory and use what you find. 

 

Refer to the actual standards documents (printed or on-line) from the issuing Standards Developing Organization (SDO) for details of proper use regarding these data concepts.  Ask questions of the committee or SDO responsible for that schema in their area of the standards support forum ( www.ITSstds./org )  The standards generally explain how these data concepts are to be properly used and contains much more information than the schema itself.  Many standards also now have a Users Guide which provides further details and often well formed XML fragment for your review.  Some standards are free, others are available at a low cost, consult the SDO for specific details. 

 

The naming and revision system used in ITS schema is briefly outlined in this document for those that have not seen this system in use.   In brief, the releases are organized by Functional Area or FADDs (Functional Area Data Dictionary).  Within each FADD is a folder with a specific unique release number.  Within that folder is one complete set of schema files.  Typically a primary schema file and the associated partial schema files that it used from elsewhere. 

 

In order to actually locally use the schema sets found here you must understand how the standard you wish to use is related to any other standards which it may depend on and include.  This is most clearly seen in the revision and file naming system used to differentiate each version of the schema and the other schema files which it in turn uses.  You will likely  have to pick a set of schema from one of  the SDOs then remove (or add) those portions  of messages and data concepts which you do not need in your deployment.  This process, called local profiling, will result in the specific schema you need for your deployment.  This becomes a critical part of your deployment and software procurement process and you will likely use it in the contractual bidding with your vendors.  When you have created this document set (several files in fact), please up-load it here so that others may benefit from you work.  If you are using the Mini-Edit tool to create your local schemas system, this is largely automated for you. 

 

How to use these schema files in a typical procurement specification that wished to be “consistent with the US ITS standards”  - text to be provided.

 

How to judge locally developed schema files to determine if they are “consistent with the US ITS standards”  - text to be provided.

 

Note that you can browse this file system, viewing the directories at each level, as you see fit.  You are encouraged to copy entire directories to your own servers as the need arises.   The path naming follow the recommendation outlined above.   More recent efforts typically have additional supporting information besides the schema files (html documentation being common).  The level of the information provided is up to the schema creator. 

 

Note for Mini-Edit Users  The database used to created a given schema set may also be found in the same folder with some releases.  This can be downloaded and used in the Mini-Edit tool to create further derivative works as needed. See the section of the standards forum on Mini-Edit use for how to obtain and install this free tool. 

 

Note for Schema submitters:  Send your schema file set in a zip file which meets the naming rules outlined here to MEdit_Support@ITSware.net and it will be uploaded into the prosper folder for use. 

 

The principal Functional Areas of the ITS world:

(each of these is a directory with further files inside of it)

 

ADUS                        Archived Data User Services

                        (ASTM)

ATIS                        Advanced Traveler Information Systems

                        (SAE)

C2C                        Center To Center

                        (NEMA)

DSRC                        Dedicated Short Range Communications

                        (SAE and IEEE)

FARS                        Fatal Accident Reporting System

                        (FHWA)

HPMS                        Highway Performance Monitoring System

                        (FHWA)

IM                        Incident Management 

                        (IEEE)

ITIS                        International Traveler Information System

                        (SAE)

ITS                        Intelligent Transportation Systems

                        (Multiple SDOs)

JXDD                        Justice XML Data Dictionary

                        (DOJ)

LRMS                        Location Referencing Message Set

                        (SAE)

NTCIP                        National Transportation Communications for ITS Protocol 

                        (AASHTO, ITE, NEMA)

RSPA                        Research and Special Programs Administration

                        (Now the Pipeline and Hazardous Materials Safety Administration, FHWA)

TCIP                        Transit Communications and Interfaces Profile

                        (APTA)

TMDD                        Transportation Management Data Dictionary

                        (ITE)

 

 

 

Functional areas representing known deployment FADD names:

 

AzTech            Arizona Regional Deployment

(AzDot and others)

 

 

 

 

 

Disclaimer:  This site is provided for as a community benefit to those building ITS systems.   You may copy and use any schema file you find on this page in your own systems, freely and with no obligation.  You are encouraged to make your own set of copies.  Our lawyers want us to remind you that we warrant this data as being of no value whatsoever to anyone and disclaim any responsibility for your use of it.  Have a nice day anyway.