A description of an XML application which itemizes changes over the
life-span of a software project. Changes are tracked by releases, with a
granularity of individual items made up of files that were affected.
Randy J. Ray (rjray@blackperl.com)2006-01-09changelog,xml,schema
An XML Schema declaration describing an XML vocabulary for software
project change-logs.
XML Schema for Changelogs
An XML Schema declaration describing an XML vocabulary for software
project change-logs.
Randy J. RayRandy J. Ray
An open-ended container type for including version-control information
at various levels within the changelog structure. This is the only
type which explicitly permits content from foreign namespaces.
A description block is used to document everything from specific change
items to the release as a whole.
The versionString type is applied to attributes that describe simple
revision-number strings. It only supports dotted-decimal styled version
numbers.
The fileType definition is used for the file element, a part of the
changeType declaration. It is defined separately so that it can be
referred to from multiple places.
A file element represents one changed file in the containing "change"
element.
These element blocks define a single change-item within the scope of a
given release. A change-item consists of one or more files that were
affected, and a description of the change itself.
A change element defines one change within a release. The change itself
may span several files, but the single description within the change
is relevant to all file-references contained within.
The release is the primary piece of information that a changelog
collects and organizes. A release contains an optional description,
followed by one or more change blocks. The release element is also the
greatest user of attributes besides the file element. A release element
must have at least a "version" attribute, uniquely identifying the
release itself. Additionally, it may have "tag" to associate it with
a release-system tag and "date" to specify the date the release was
created.
The release element details one release within the overall change-log
itself. Because the release element has a required attribute that
provides a time-stamp, releases may appear in any order within the
change-log, since processors can sort the elements by their relative
dates.
The changelog element is intended as the document root element. It
contains a description element and one or more release blocks.