"Obsolete-table" container

Latest revision as of 08:31, 9 December 2016

The obsolete-table describes the asset’s revision history. It lists the KUIDs of assets that are obsoleted by this asset.

Trainz and the Trainz Download Station automatically detect the most recent version of an asset by consulting the obsolete-table.

Originally, the obsolete table was the only mechanism available for describing the asset's revision history, because each revision of an asset required a different Content ID. . However, the introduction of the KUID2 format meant that the revision history could be inferred from the revision number that is part of the KUID2 format.

Therefore the obsolete table is required if any asset in the revision history uses a different Content ID, but it can be omitted for those assets where all versions use the KUID2 format.

The obsolete-table container follows the same format as the "Kuid-table" container. The values used for the tags are arbitrary. The container can be empty.

This example is the obsolete-table for asset <kuid2:51536:50006:7>. The asset originally obsoleted asset <kuid:51536:50005>, and has subsequently been revised using KUID2 revision numbers.

 obsolete-table {
   0                           <kuid:51536:50005>
   1                           <kuid:51536:50006>
   2                           <kuid2:51536:50006:1>
   3                           <kuid2:51536:50006:2>
   4                           <kuid2:51536:50006:3>
   5                           <kuid2:51536:50006:4>
   6                           <kuid2:51536:50006:5>
   7                           <kuid2:51536:50006:6>
 }

"Obsolete-table" container

Latest revision as of 08:31, 9 December 2016

Views

Personal tools

Navigation

Search

Toolbox

@@ Line 1: / Line 1: @@
-The obsolete-table describes the asset’s revision history.
+{{ORP-beg}}
+The obsolete-table describes the asset’s revision history.  It lists the KUIDs of assets that are obsoleted by this asset.
-This field was used extensively for pre-TRS assets, as each version required a unique Content ID. However in order to make the content creator’s life a little easier, Trainz now uses the KUID2 format which adds another number as a version number.
+Trainz and the Trainz Download Station automatically detect the most recent version of an asset by consulting the obsolete-table.
-TRS and the Trainz Download Station automatically detects the most recent version of an asset whether it be through the KUID2 Version ID or through the obsolete-table.
+Originally, the obsolete table was the only mechanism available for describing the asset's revision history, because each revision of an asset required a different Content ID. .  However, the introduction of the KUID2 format meant that the revision history could be inferred from the revision number that is part of the KUID2 format.
-If there are no obsoletes, leave the obsolete tags out.
+Therefore the obsolete table is required if any asset in the revision history uses a different Content ID, but it can be omitted for those assets where all versions use the KUID2 format.
+The obsolete-table container follows the same format as the [["Kuid-table" container]].  The values used for the tags are arbitrary.  The container can be empty.
+This example is the obsolete-table for asset <kuid2:51536:50006:7>. The asset originally obsoleted asset <kuid:51536:50005>, and has subsequently been revised using KUID2 revision numbers.
+  obsolete-table {
+                           <kuid:51536:50005>
+                           <kuid:51536:50006>
+                           <kuid2:51536:50006:1>
+                           <kuid2:51536:50006:2>
+                           <kuid2:51536:50006:3>
+                           <kuid2:51536:50006:4>
+                           <kuid2:51536:50006:5>
+                           <kuid2:51536:50006:6>
+  }
+[[Category:Config Container|obsolete-table container]]
+{{ORP-bot|obsolete-table container}}