Tape Library Profile Question

[John Leiseboer <JL@quintessencelabs.com>]

The types of x-VendorAttribute2 and x-VendorAttribute3 have been swapped (Integer to DateTime, and DateTime to Integer, respectively) in test cases TL-M-2-10/11/12 and TL-M-3-10/11/12 of the Tape Library Profile.

Is this a typo, or done on purpose? Is this something that is required in the real world to support some vendor's tape library?

NOTE: I'm not asking for anything to be changed. I'm just curious to know why this behaviour is mandatory for the tape library profile.

From the 10 test cases:

3.1.2 TL-M-2-10 - Write with new (created) key
TIME 0
<Attribute>
  <AttributeName type="TextString" value="x-VendorAttribute2"/>
  <AttributeValue type="Integer" value="0"/>
</Attribute>
<Attribute>
  <AttributeName type="TextString" value="x-VendorAttribute3"/>
  <AttributeValue type="DateTime" value="2012-10-05T22:08:19+00:00"/>
</Attribute>


3.1.3 TL-M-3-10 - Read an encrypted tape
TIME 3
<Attribute>
  <AttributeName type="TextString" value="x-VendorAttribute2"/>
  <AttributeValue type="DateTime" value="2012-10-05T22:27:06+00:00"/>
</Attribute>
...
<Attribute>
  <AttributeName type="TextString" value="x-VendorAttribute3"/>
  <AttributeValue type="Integer" value="1"/>
</Attribute>

John

John Leiseboer | Chief Technology Officer | QuintessenceLabs | W: quintessencelabs.com
E: jl@quintessencelabs.com | M(AU): +61 409 487 510 | M(US): +1 202 294 6825 | Skype: jleiseboer
AU: 15 Denison St | Deakin | ACT 2601 | T: +61 2 6260 4922
US: Suite 220 | 175 Bernal Road | San Jose CA 95119 | T: +1 650 870 9920