2.1

The Enumeration "DataClassEnum" seems not to be used within the data model (i.e. there is no attribute using it).
Maybe it's some kind of meta information, but I'm not sure about this.

It should be checked, whether this enumeration is still necessary or if there is some construct or attribute missing, which was intendet to use it.

The definition:
"One or more physically separate locations. Multiple locations may be related, as in an itinerary (or route), or may be unrelated. It is not for identifying the same physical location using different referencing systems."

The confusing thing is stating that a group can be 1. That is strange.

The clause "It is not for identifying the same location using different referencing systems" is wrong. It is the only way to do it within the group of locations.

A bug is found from documentation, concerning Alert-C direction (section 7.2.8 in User Guide). Example 5 states that effect is for positive direction, when it should be to both directions.

Detailed question (and answer) is found from the following link:

http://www.datex2.eu/content/alert-c-location-referencing-question

In the XML example files, the schema reference does not point to the current version of the schema (2.1) but to the version 2.0.

I suggest fixing the scham location link in the example messages.

The DATEX Namespace http://datex2.eu/schema/2/2_0 is by definition an URI, not an valid URL. Newertheless it is good pratice to guide users to the schema, if they try to resolve the namespace in a webbrowser.
In DATEX, this doesn't work and produces a 403 error (which is actually no bug, see above).

I suggest to implement some forwarding to the current DATEX schema.

The DATEX Tool crashes by selecting something in the tree when using a huge data model (with a lot of extensions).
It's a standard Windows message which terminates the program and which does not give any additional information about the problem.

The problem and a way to reproduce it is described in detail to Jonas Jäderberg.

we have a need for NotManagedCause to be used to specify any kind of SituationRecord that is not managed directly by a TCC ( which manage its only road competence and may refere to situation record outside competence that could be not available in the TCC system )

causeType is already referring to many situation, but not to all.. so it should be better to model allowing for NotManaged Cause any "SituationRecordClass"Type that has been provided for any different other Classes.