RE: [kmip] Tape Library Profile Question

[John Leiseboer <JL@quintessencelabs.com>]

Thanks Tim. No problem understanding that different attribute types must be supported. That wasn't my question though. Sorry if I wasn't clear.

I wasn't asking why different attribute types need to be supported. I was asking why it is necessary to support the modification of an existing attribute's type. That is, why is one attribute that was originally of type Integer changed to a type of DateTime using ModifyAttribute, and another changed from DateTime to Integer? This behaviour is not explained in Section 2.3 item 9, in the section 3 lead in text, nor anywhere else as far as I can see.

It just seems odd to me that the tape library profile would make this server behaviour mandatory in the test cases if there wasn't a reason for it. To test the behaviour specified in 2.3 item 9 does not require that an existing custom attribute's type be modified.

John

-----Original Message-----
From: kmip@lists.oasis-open.org [mailto:kmip@lists.oasis-open.org] On Behalf Of Tim Hudson
Sent: Wednesday, 27 May 2015 2:26 PM
To: kmip@lists.oasis-open.org
Subject: Re: [kmip] Tape Library Profile Question

On 27/05/2015 1:42 PM, John Leiseboer wrote:
> 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?
It was done on purpose.

> 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.

Section 2.3 item 9 makes it clear that a server must support custom attributes of at least the three specified types (Text String, Integer, Date Time) and also support multiple custom attributes (minimum of 30) in item 11.

Refer to the section 3 lead in text where it states
"Note: the values for the returned items and the custom attributes are illustrative. Actual values from a real client system may vary as specified in section 4.7."

Thanks,
Tim.


---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that generates this mail.  Follow this link to all your TCs in OASIS at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php