There is a bug in the tool regarding extensions. If you add a tagged value extension, but does noit give it a value (null) then the tool will fail to load the XMI.

Here's a summary of all warnings which occur when using the schema generation tool on the RC2 model (model and tool just downloaded from website):

• Illegal value found in tagged value 'attribute' (needs to be 'yes' instead of 'true') in attribute ...
  • measurementOrCalculatedTimePrecision in class BasicData
  • accuracy in class DataValue
  • computationalMethod in class DataValue
  • fault in class DataValue
  • faultReason in class DataValue
  • numberOfIncompleteInputs in class DataValue
  • numberOfInputValuesUsed in class DataValue

The static and the dynamic part for measured data do not match exactly to each other.

Up to now, the MeasurementSiteTable is referenced from the MeasuredDataPublication. When using more than one MeasurementSiteTables, you habe to use one MeasuredDataPublication per table. This seems to be inconvenient.

I suggest a 1:1 mapping between the two messages, so to introduce a new class between MeasuredDataPublication and SiteMeasurements.

There appear to be be two 'orphaned' data types that are not used in the content of the model. These are HectoPascals (Pressure) and MegaHertz (Frequency). Certainly one would expect weather data to support the exchange of pressure data.

The methodology document states "those UML packages related to the exchange model being aware of – and actually using elements from – the payload content model, but not the other way round". This is inconsistent with the fact that the association from D2LogicalModel (the incorrectly - see issue #4 - named single entry point into the model) to the exchange package class Exchange is mandatory! Exchange has a mandatory compnent supplierIdentification with two mandatory attributes.

The section describing the class and extension mapping to XSD have a typo. They quote a complex type "ExtensionType" which - according to the final convention that internally generated type names shalll start with '_' - has to be "_ExtensionType".

In the VmsPublication the attribute vmsTextLineLanguage (in class VmsTextLine) uses a datatype of String. This should use a datatype of "Language".

This is now fixed and will be released in v2.0

It's not possible to send a elabortaed forecast about a weather related road surface condotion. In ElaboratedDataPublication, WeatherData.

The MeasurementEquipmentFault class is there in the latest model but I have found out that there is a 1 to 1 relation between MeasuredValue and BasicData which means that I still have to give a value when I have a missing value.

The methodology uses the same meta concept from UML (Generalization) for two different semantical features.

a) Generalization inside the core model (level A) or inside an extension (i.e. between two new classes in the extension) means that the new class inherits and extends the state of the superclass, hence realising an "is a" relationship in the data domain. Example: class horse "is a" mamal, i.e. horse has all attributes and components of a horse, plus potentially some extra ones.