Include fmi2Unit.xsd

[ljamt]

• Added fmi2Unit.xsd from FMI 2.0 and included it in OspModelDescription.xsd
• Suggested how units can be applied to variables, examplified in CraneController_OspModelDescription.xml

Closes #523

[mrindar]

Looks good :)

[eidekrist]

👍

[mrindar]

There is some namespace issues between fmi2Unit.xsd and OspModelDescription.xsd when trying to use jaxb to generate java classes from this schema:

$ xjc OspModelDescription.xsd 

parsing a schema... 

[ERROR] src-resolve.4.1: Error resolving component 'fmi2Unit'. It was detected that 'fmi2Unit'

has no namespace, but components with no target namespace are not referenceable from

schema document 'file:/C:/Users/mar tinr/dev/git/msmi-validator/osp-model-description

/src/main/resources/OspModelDescription.xsd'. If 'fmi2Unit' is intended to have a namespace,

perhaps a prefix needs to be provided. If it is intended that 'fmi2Unit'  has no namespace, then 

an 'import' without a "namespace" attribute should be added to 'file:/C:/Users/martinr/dev/git

/msmi-validator/osp-model-description/src/main/resources/OspModelDescription.xsd'. 

line 12 of file:/C:/Users/martinr/dev/git/msmi-validator/osp-model-description/src/main

/resources/OspModelDescription.xsd 

[ERROR] src-resolve: Cannot resolve the name 'fmi2Unit' to a(n) 'type definition' component.                                                                                                                              

line 12 of file:/C:/Users/martinr/dev/git/msmi-validator/osp-model-description/src/main

/resources/OspModelDescription.xsd

Failed to parse a schema.

[ljamt]

Ok. There are two ways to have "transitive" xsds: import and include. I did it the same way as fmi2ModelDescription.xsd includes fmi2Unit.xsd. Not at xsd/xml expert so difficult to figure out without having failing code. Are you debugging @mrindar ?

[mrindar]

Ok. There are two ways to have "transitive" xsds: import and include. I did it the same way as fmi2ModelDescription.xsd includes fmi2Unit.xsd. Not at xsd/xml expert so difficult to figure out without having failing code. Are you debugging @mrindar ?

If you have java installed I think you can just run the following command to reproduce the error:
$ xjc OspModelDescription.xsd

[ljamt]

If you have java installed I think you can just run the following command to reproduce the error:
$ xjc OspModelDescription.xsd

Looks like adding the osp namespace fixed it.