We discussed in the Asset Management Basics WG that it would be desirable to provide more semantic in the SoftwareRevision than just a string, where you - in a nutshell - just compare if it is the same version or not. In many cases, there is more information like, Major, Minor, Build Number, etc. This website (https://semver.org/) gives a BNF how this can be represented in a string. This allows you to identify, if it is a newer or older version.

As not all SoftwareRevisions will be provided in such a format and we do not want to introduce a breaking change we suggest to:
Create a subtype of String which requires the specific syntax (e.g. called SemVerString). Servers can use the subtype and thus expose to the client, that a specific format is used. Companion Specs can require this format by refining the Property to this data type. Clients can use the information so that they know a specific format is used.

Remark: (Not discussed in WG): Maybe it even make sense to put this data type into the base spec? Then Part 100 should still mention its possible usage as SoftwareRevision.