Defining the XML File Content
You can only load one XML file. However, you can include multiple series in the one file. When there are multiple series in the file, each series name must be unique. For example, the following XML file has two series defined:
<?xml version="1.0" encoding="UTF-8"?>
<scheme>
<series name = "name1">
<value>P1</value>
<value>P2</value>
<value>P3</value>
</series>
<series name = "name2">
<value>A_1</value>
<value>A_3</value>
<value>A_5</value>
</series>
</scheme>
<scheme>
<series name = "name1">
<value>P1</value>
<value>P2</value>
<value>P3</value>
</series>
<series name = "name2">
<value>A_1</value>
<value>A_3</value>
<value>A_5</value>
</series>
</scheme>
There are no out-of-the-box object initialization rules loaded that set versioning to file-based versioning, as defined in this section. You can create a file-based Harvard series that uses the file that you load and name the series in one or more versioning object initialization rules.
In the XML file, the series name can contain any alphanumeric characters other than the period (.) or the at symbol (@). The series name you specify in the XML file is the name you must also append to wt.series.HarvardSeries to form the name used in the argument for the versioning rule. For example, if the series name is "name1", then the argument to include is "wt.series.HarvardSeries.name1".
The values contained in the <value> elements can be any set of unique values with the following qualifications:
• There is no upper limit to the number of characters that can be specified in each value; however, if you use lengthy values, the complete object name can be longer than the user interface field in which it is displayed.
• A value cannot be empty; it must contain at least one non-white space character.
• A value cannot contain the series delimiter that is defined in the wt.properties wt.series.HarvardSeries.delimiter property. The default series delimiter is the period (.).
• White space cannot be used in a revision label.
• The values you specify for the revision labels must be unique within the entire series and specifying the same value multiple times is not allowed; however, you can use the values from one series in another series.
The order of the values in the file determines the order in which the values are used as the version designator when the object is revised.
 |
You can modify the file-based versioning values that are established through the XML versioning file; however, all changes should be made before the versioning is used. Changing values that have already been used can cause unpredictable results when versions are being updated. If you must make a change to a versioning scheme, ensure that the values you specify for the revision labels are unique within the entire versioning scheme and that you do not remove any values from a series that are already in use; however, you can include the legacy attribute for those values that you do not want used for new revision labels as described in Accommodating Legacy Values in Revision Labels. Specifying the same value multiple times is not allowed. Also, removing a series name after the series has been in use causes problems for any existing objects that use the series. For example, those objects could not be revised and the object iteration history could not be displayed.
|
For details on how to create this series, see Setting Up a File-based or State-based Versioning Scheme.