Versioning systems for informational resources
I did a quick repo search and couldn't find anything relevant, so I'm making a quick Issue.
I'm interested in the potential value of versioning systems to value flows accounting for the collaborative development and (when applicable) the use rights for any type of informational resource.
For example, it could theoretically be relevant to specify that someone contributed code to App X version 1.11.03 instead of simply specifying that they contributed code to App X. I doubt that that info would typically be used in calculations (such as determining compensation), but it'd be really good IMO for the info to be available for future reference. (And in theory, the info could be automatically mined from a codebase in version control, such as on github.)
My overall interest in version control is more personal: i.e., I'd like clear version control for all collaborative creative projects.
With that in mind: Semantic Versioning 2.0.0 http://semver.org/ is rigorous. Any opinions? @elf-pavlik this may be particularly up your alley? I'd appreciate any feedback!