- Major versoin
- Minor version
- Incremental version (bugfix)
- Build number
- A Qualifier.
Reference: OSGi version and version range schemes are available in the Core OSGi spec, which can be downloaded here(see §3.2.4 and §3.2.5 on page 38 of OSGi Service Platform Release 4 Version 4.1 Core Specification pdf)
Other than the limitation of supported versions, the current implementation has several flaws:
- 1-beta ==? 1-abc: "2" ==? "7-abc" -> 1-abc is newer
- 1.0 ==? 1.0-abc: "4" ==? "7-abc" -> 1.0-abc is newer
- 1.0-alpha-10 ==? 1.0-alpha-2: 10 > 2, so '1.0-alpha-10' is newer
- 1.0-alpha-1.0 ==? 1.0-alpha-1: equal
- 1.0-alpha-1.2 ==? 1.0-alpha-2: 1.0-alpha-2 is newer
Note: This approach differs from the version comparison as done by OSGi .
Make version handling pluggable
This scheme doesn't even come close to being able to describe the variety of version schemes supported by my proposal.
Perhaps it's better if, when we do XML, we use XSD to describe the version schemes.
We define a set of simple/complextypes that people have to extend, and the engine can then convert it to a parser/verifier/order implementation/representation using the base classes.
The parser would use the 'prefix' values and the type attributes to determine what kind of token is next, in the version string. It would then build an XML DOM that can be validated against the XSD, which can have extra rules.
Anyway, UDDI tried to do something similar for random applications - to have the API specs in a uniform format so you could generate an application around reusable components, but that didn't work out and AFAIK the specs are just human readable documents. If somebody wants to create a parser/validator/sorter for a version spec, there should just be enough documentation for them to do it.
References and Related Material