The open XML schema project for ITS deployments

August 30^th 2004 Update:

A new release of the draft Incident Management effort can be found at: http://www.itsware.net/xml/IM_Aug30/ (along with needed supporting files)

The html documentation can be found at: http://www.itsware.net/xml/IM_Aug30/docs/IM_rev25.html

If you are interested in the documentation of the standard which goes along with this:

http://serv4.itsware.net/bb/viewtopic.php?t=314

April 20^th 2004 Update:

A new release of the draft Incident Management effort can be found at: http://www.itsware.net/xml/IM_April20/ (along with needed supporting files)

The html documentation can be found at: http://www.itsware.net/xml/IM_April20/Docs_April_20/IM.html

You might want to download the zip file which contains all the html, as browsing a local copy can be much faster.

March 14^th 2004 Update: Due to popular demand we are re-worked the file layout of this page to have a directory for each major message set with its own set of supporting scheme files needed to compile it. In this way users can avoid to some degree the hassles of data sharing and resolving stubs and namespaces that occur with draft schemas during the period they are being developed.

The files previously found at this level of the directory will remain in place for one month, however the most current working drafts for any area of interest can be found in a sub-directory for that subject area (such as /ATIS or /TMDD or /IM ). Most of these are working drafts, in other words they do not completely compile because the work of developing them is not completed yet. The ATIS set is a complete and adopted standard and does fully compile. All others are drafts and have not undergone a formal committee approval process. The directory /merged is a work in progress to merge all ITS schema files into one coherent set of files which cross reference each other correctly.

In each directory you can also find the most current ASN.1 listings (in a file called source.txt) and a folder of html documentation which you can transverse over to learn about the schema contents.

For Advanced Traveler ATIS Documentation

For Incident Management IM Documentation

For Traffic Management TMDD Documentation

Be patient when you load these top level files - they are very big (10~20 megs) and load hundreds of small supporting pictures. Better documentation (and the underlying supporting database file) is of course available from the sponsoring standards organization for each body of work. Training and outreach on the content of these standards and how to use them is also available.

Outdated information but still of value………….

Jan 9^th 2004 Update. The most current IEEE 1512 IM base standard (combining all four volumes) is posted to a sub directory “~/1512_all” and the file IM.xsd reflects the complete (but still unfinished) IM schema at this time. The direct link is http://www.itsware.net/xml/1512_all/IM.xsd

Late breaking news (Dev 4^th): NEMSIS Revision 2 (National EMS Information System) is now available in XML as part of the revisions to that effort. The link is http://www.nemsis.org/ This effort is of interest to ITS practitioners using the IEEEE 1512 Incident Management work because the 1512.2 “Public Safety” volumes uses NEMSIS data elements as part of the EMS vehicle resources messages and the message used to report and exchange information about victims being transports to care facilities. It also shares a number of elements with NFIRS of interest to us. We are now trying to review and integrate the new XML work with the IM effort and expect to complete this in Jan. As always, you are cautioned this is a DRAFT.

The Justice XML effort is also available here, but only versions 3..0.0.0 which is now outdated. The official place to obtain this data is from the Office of Justice Programs at http://it.ojp.gov/topic.jsp?topic_id=43 however further changes are still expected. The “person”, “vehicle”, and “object” models used by the JXDD have been integrated into the IEEE IM 1512.2 effort and will (with time) be extended to other ITS work areas.

SUMMARY

This directory is an open dumping ground for various XML schema files used in the validation process of developing ITS messages sets, notably the work done by the SAE Advanced Traveler (ATIS) committee and by IEEE Incident Management (IM) committees and their committee members and deployments using their standards. Other committees involved in ITS also use this page (as the messages are cross linked). The primary purpose of this page is to provide a valid set of schema for developers working on XML deployments. When a developer loads an XML schema without having a set of supporting schema developed and loaded within his own server environment, then the validation machine will look to this directory to gather the missing parts.

At this time there are several major XML namespaces that are commonly use in the national standards when expressed in XML (these correspond the ASN.1 module that are also used), they are:

ADUS All the ASTM archival data services material

ATIS All the SAE Advanced traveler information material

DSRC All the IEEE short range comm., and data dictionary material

HPMS All the Highway Performance monitoring data services material

ITIS All the ITIS Codes and Phrases used in various ITS standards

IM All the IEEE incident management material

LRMS All the location referencing material

NTCIP All the NEMA roadside device and control material

TCIP All the Transit Communications ad interfaces material

TMDD All the ITE traffic management material

And also "local" which each local deployment may use to add local content with

Each of these has a schema corresponding to this name here (in lower case letters). If you wish to see it, click on the above links. There are other schema here as well, typically working fragments of either the committee or of deployments. In any event, you should contact the responsible standards developing organization (SDOs) for each of the above efforts if you wish to obtain the complete and correct schema representing work of that standards group. The above files are typically a subset of a complete standard, representing only the items which are cross shared by other groups and hence of interest.

To see complete information about how to use the message found in these schema, consult the actual SAE ATIS standard (http://www.sae.org/). There is a large amount of discussion text regarding how elements are used and the context of the messages themselves that is not present in a schema. This includes documentation on other entries developed by other SDOs which are needed by the ATIS schema as well. The ASN.1 definitions of the standard is available as well here. An on-line reference to the structures used in the schema (but with no information on how they are used) can be found at http://www.itsware.net/xml/docs/documentation.htm

If you are looking at this page because your own schema did not work, it is likely you have had some problems with some XML you are trying to validate. In general you want to place your schemas locally to the machine that will be validating to keep network traffic down. Each such schema that points to another schema you use must have a path to the other machine. [Editor note: over time we will add local extension support examples here as well and link this page to the training and outreach course tools as well]

Currently your paths seems to be set up to bring you here. You probably want to revise the lines in your schema that control this and gather up the ones you need for local use. For example, you can find in the schema that brought you here a line near the beginning like:

<xs:import namespace="lrms" schemaLocation="http://www.itsware.net/xml/lrms.xsd"/>

You need to change the path (http:///www.itsware.net/.../etc.) to reflect some site on your own server farm. If you are developing something on your own personal PC you can replace this with a local path such as "c:/mystuff/.../etc" as needed.

You can do this by re-editing each offending schema (with a text editor or with a commercial tool such as XML Spy) or by having the Mini-Edit tool produce schemas with the path you want. If you need to change the path to the imported files that you have produced using the Mini-Edit tool, edit the table "XML_Templates" in the control file and change the entries for each "path" and "import" line to the one you like. These values will then be inserted into the data in the "imports" entry. If you need to import additional namespaces besides the above nine key ones of ITS, you can add them here. Once you have made these changes to the control file, export your XML again to see the revised version.

Disclaimer: This site is provided for educational testing use only! Do not build production or commercial systems that depend on obtaining the schema files from this site for validation purposes. Repetitive and heavy use of the site for such purposes is not allowed. 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.