TranXML - Frequently Asked Questions

  1. What is TranXML?
  2. What messages does TranXML support?
  3. Why did Transentric create TranXML?
  4. Was TranXML a collaborative effort?
  5. I like what you've done but feel I need to make a change what do I do?
  6. I've noticed a bug in TranXML who do I contact?
  7. I am having problems loading the schemas in the graphical view of XMLSpy 3.5, what should I do?
  8. What is the difference between Example Documents, and Template Documents?
  9. What is planned in the next release of TranXML?


Back To Index

1. What is TranXML?

TranXML is an eXtensible Markup Language created by Transentric for the Transportation & Logistics Industry. TranXML provides a standardized set of XML structures that will foster the flow of information between various internal and external applications. It will allow for the optimization of data structures to ensure interoperability, which are based on existing EDI formats. Additionally, it allows for a format that is both human and machine readable, allowing for greater flexibility than traditional EDI.

Top

2. What messages does TranXML support?

TranXML currently supports the following messages:
  • Rail Bill Of Lading
  • Simple Rail Bill Of Lading
  • Motor Carrier Bill Of Lading
  • Motor Carrier Load Tender
  • Shipment Weights
  • Car Location Message
  • Shipment Status
  • Terminal Operations And Intermodal Ramp Activity

Top

3. Why did Transentric create TranXML?

Originally TranXML was to be used as an internal XML standard, but we then decided that it could also benefit others in the Transportation and Logistics industry. The Transportation and Logistics industry cuts across all vertical boundaries. It must serve many masters, such as Chemicals, Electronics, Utility, Automotive and others. As vertical industries are developing their own collaborative vocabularies, Transportation is forced to adopt (and support) all of the flavors created by the industry standards. Additionally, the semantic definition of transport and logistic objects may not be appropriate, as some of the industry groups lack the domain knowledge to develop meaningful vocabularies to support logistics functions. It is for this reason that Transentric has developed TranXML, which can be used as the common vocabulary to support logistics supply chain functions across vertical collaborative vocabularies.

Top

4. Was TranXML a collaborative effort?

To ensure that the TranXML dictionary is as interoperable as possible, Transentric draws upon internal domain knowledge as well as standards established by other authorities such as ChemXML, RosettaNet and ebXML. As of this writing, the only logistics messages developed in an open standard environment have been within the auspices of CIDX and Bolero. TranXML will draw upon their experience to ensure that it will be as interoperable with those external trading partners. Although the standards bodies above represent collaborative efforts, many of them are still based on the business practices and semantic objects of a particular vertical industry. However, if one looks at large-scale collaborative efforts supporting e-commerce, they will find that the X12 and EDIFACT dictionaries represent the largest collaborative repository of information in the world. Given this fact, TranXML is based upon that collaborative effort and draws the semantic meaning of the XML objects directly from the open-standards dictionaries. In the future, Transentric will work with other development groups to incorporate the needs of other trading partners.

Top

5. I like what you've done but feel I need to make a change, what do I do?

Contact Us: TranXML@Transentric.com, and help us in the collabrative design process.

Top

6. I've noticed a bug in TranXML who do I contact?

Contact Us: TranXML@Transentric.com

Top

7. I am having problems loading the schemas in the graphical view of XMLSpy 3.5, what should I do?

The graphical view in XMLSpy 3.5 requires approximately 10 times the amount of RAM as the size of the schema that you are trying to open. The reason you may have problems with the TranXML dictionary is that we reference many of the X12 codelists, and they can become quite large. One work around is to comment out all of the codelist includes so you can navigate in graphical mode, and then uncomment them when you are finished. For any additional XMLSpy support please refer to there Support Center: http://www.xmlspy.com/support_center.html.

Top

8. What is the difference between Example Documents, and Template Documents?

The Example Documents are valid TranXML documents complete with sample data, simulating what a real world TranXML document may resemble. The Template Documents do not contain sample data, and therefore they do not validate against the TranXML schemas. They are there strictly as a starting point for developing your TranXML documents. The Template Documents contain many of the tags, and also many comments that should help you create your TranXML documents.

Top

9. What is planned in the next release of TranXML?

The following is a tentative list of messages in the next release of TranXML:
  • Purchase Order
  • Purchase Order Acknowledgement
  • Advance Ship Notice
  • Pickup Manifest
  • TranXML Envelope
  • Freight Bills
  • Application Acknowledgement
  • Receiving Advice

Top

Back To Index