Browse Prior Art Database

Mechanism to store and compute useful version information

IP.com Disclosure Number: IPCOM000213553D
Publication Date: 2011-Dec-21
Document File: 7 page(s) / 128K

Publishing Venue

The IP.com Prior Art Database

Abstract

Mechanism to store and compute useful version information in a version control system through scoped semantic mining of differential deltas

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 48% of the total text.

Page 01 of 7

Mechanism to store and compute useful version information

Version control systems, in general, have a repository where artifacts are stored. When any new content is added to an artifact, and committed to the repository, a new version of the artifact is created.

Version control systems, do not usually store all the data associated with the artifact, for every new version created. In stead, they compute and store a delta which can later be used to 'calculate' the contents of any version that is requested. This is illustrated in the diagram shown below

Fig1: Version computation in a source control repository using delta compression

Most version control systems compute and display version information from a macro level as in baselines to a micro level i.e. version information associated with an element.

Version control systems today lack the ability to record, compute and display version

1


Page 02 of 7

information at a more fine grained level which is with respect to semantic constructs within elements.

Most documents and source code documents in particular are structured semantically
For e.g. a normal Java class is composed of a class structure with variables, methods and other constructs such as inner classes. Similarly a HTML source file may contain a series of tables and rows and various other valid constructs or tags.

While Version control systems provide a mechanism of gathering the version timeline of an element through a graphical tree format, there is no existing mechanism to display versions which are scoped within semantic constructs.

Version information for a version controlled element.

Fig2: Presentation of Version line through a graphical version tree

A Version control system user such as a source code developer has no mechanism to see a

2


Page 03 of 7

version tree of those versions which have association with a semantic construct.

In the above scenario if the user wanted to see a version line of those versions where changes were made with respect to a particular semantic construct such as a method in a class he will not be able to do so due to lack of support or deficiency in Version control systems of today.

This disclosure proposes a solution for the above problem through a mechanism to store and compute useful version information in a source control system through scoped semantic mining of differential deltas
For clarity of concept this proposed solution divides the mechanism into two broad sections.

Section1: Recording of contextual scope information during differential delta computation

Most version control systems record differential deltas through line positions and their differential from the base version. This is clearly explained through

the example below

Fig3: Version computation in a source control repository using delta compression based on line

positions

In the above scenario the Delta computation engine would store the following information while

3


Page 04 of 7

creating version metadata for version 2 and v...