Discussed in WG Meeting:
Define Type called SemanticVersionString as subtype of string.
Copy BNF into spec.
Add note in IVendorNamplateType and SoftwareVersionType that the datatype can be used instead of the "normal" string.

Clone item to Part 5 and potentially define DataType in Part 5.

Proposal from FDI/PA-DIM-WGs (probably also Fx):
“Limit the version parts to 1..5 characters. Furthermore, the number expressed by each part of the version string shall fit into an 16 bit unsigned integer, i.e. <= 65.535.”

Many vendors already use SoftwareVersion with vendor specific strings and getting them to switch might not be practical, but FLC required a standard versioning that can be easily compared. FX has defined an structure with numeric version information in it for use (major, minor, buid, subbuild). No string processing is required and can be easily compared. We still allow the vendors to use the software and Hardware version information as they want, since it might be used for vendor proprietary information.

defining the string type might be useful in other specification, but I don't think it can be applied to all of the existing devices.

Agreed name of type should be "SemanticVersionString".
We agreed to put this in the 1.05.0 release Nodeset even though it will not be in the 1.05.0 Part 5.

Agreed to add this to the final 1.05.0 Part 5 (change after RC review).

DataType moved for Part 100 into Part 5 during RC review

Dup of 7274

Agreed to dup in telecon.