version attribute make clear through the xsd and documentation that @version is a number (entur-interpretation) or any

[skinkie]

                                <xsd:attribute name="version" type="VersionIdType" use="required">
                                        <xsd:annotation>
                                                <xsd:documentation>Version number of referenced entity.</xsd:documentation>
                                        </xsd:annotation>
                                </xsd:attribute>

[Aurige]

For now VersionIdType is said to be "A revision identifier (e.g. a number) that should be updated (e.g. increased) each time the unit that is refers to is modified." and its type is "xsd:normalizedString"
Having a number (as characters in the normalizedString) mandatory is of course ok for a profile ... but probably much more complicated in the general case (but it can be a recommendation)

[skinkie]

For now VersionIdType is said to be "A revision identifier (e.g. a number) that should be updated (e.g. increased) each time the unit that is refers to is modified." and its type is "xsd:normalizedString" Having a number (as characters in the normalizedString) mandatory is of course ok for a profile ... but probably much more complicated in the general case (but it can be a recommendation)

The problem is that in several parts of the annotation it is explicitly mentioned as a number. Must be cleared up if it is not a number, or it is.

[Aurige]

At minimum, refine annotations

[Aurige]

Don't change the type, but make recommendations for monotonically increasing use (what about dates).
There is also difference between the global Frame versioning and the per object versioning.
Guidelines to be added in EPIP/NeTEx and Guidance document
@ue71603

[ue71603]

@trurlurl in the EPIP/NeTEx documents. Can you do it?

[ue71603]

Added to the guidance document in 5.9. so only André's stuff left