Here is an high-level model for a versioning system that was designed to support content like programming files as well as hypertext markup language well.
SnapCM
It doesn't go to the detail of implementation, but could be a meta-model to compare/contrast versioning system implementations.
This model also support policy based version to version link resolution: stuff like fixed version, latest version, version from same context...
Some other comments have indicated that a versioning system should have better dependency tracking. I've extended the SnapCM model to Versioned Hypderdocuments (XML plus XLink) as one example of precisely recording dependencies. A programming languages import statements could be treated the same way.
My team practices Extreme Programming and this mean that we together need to work the same schedule. The basic reason is that when we are working together (in the same large room in fact) communication is very fast and we are more productive.
Our team an another team can have totally different schedules without affecting productivity. We also borrow some of the ideas in other posting here: 1) Have a core set of hours that the team should be in the office for. 2) Get other team members to cover for you if you have an appointment.
"Contractually precluded" might, perhaps, be good enough for us to trust that the company won't sell the gathered data, but it relies on trusting the individual people who have access to the system not selling out.
I'm sure that internet advertising agencies will pay big bucks for a list of identities with data. No corporate contract will keep some people from immorally stealing and selling that data.
Slashdot Mirror
It doesn't go to the detail of implementation, but could be a meta-model to compare/contrast versioning system implementations.
This model also support policy based version to version link resolution: stuff like fixed version, latest version, version from same context...
Some other comments have indicated that a versioning system should have better dependency tracking. I've extended the SnapCM model to Versioned Hypderdocuments (XML plus XLink) as one example of precisely recording dependencies. A programming languages import statements could be treated the same way.
My team practices Extreme Programming and this mean that we together need to work the same schedule. The basic reason is that when we are working together (in the same large room in fact) communication is very fast and we are more productive.
Our team an another team can have totally different schedules without affecting productivity. We also borrow some of the ideas in other posting here: 1) Have a core set of hours that the team should be in the office for. 2) Get other team members to cover for you if you have an appointment.
"Contractually precluded" might, perhaps, be good enough for us to trust that the company won't sell the gathered data, but it relies on trusting the individual people who have access to the system not selling out.
I'm sure that internet advertising agencies will pay big bucks for a list of identities with data. No corporate contract will keep some people from immorally stealing and selling that data.
John Heintz