OASIS Open Mailing List Archives  ·  All Lists  ·  kmip-interop-tech  ·  2011-07

kmip-interop-tech — archive

[Date Prev]  |  [Thread Prev]  |  [Thread Next]  |  [Date Next]   —  [Date Index]  |  [Thread Index]  |  [Month Index]  |  [List Home]

RE: Attribute index clarification


Clarification to the request for clarification. J When I said: “ It clearly should not imply that all single-instance attributes SHALL have index 0.“,  I meant to say: “It clearly should not imply that all attributes that have a single instance SHALL have index 0.” For example, you can have a custom attribute x-attr with a single value at index 1. “What I’m also trying to understand is how to deal with non-zero single instance attributes” should read – “What I’m also trying to understand is how to deal with the attributes that are allowed to have multiple instances, only containing one, with the index other than 0”. Let’s see if I can express my questions in a form of “KMIP pseudo-code”. register <object> x-attr#0=value0 x-attr#1=value1 delete attribute <object> x-attr#0 modify attribute <object> x-attr=newvalue  <- - should this return an error  or modify x-attr#1? get attributes <object> x-attr      <- - should this return an empty list since index 1 was not specified? If it does return a value at index 1, should it also return the index itself as it does here: Response Message (0x42007b) 0x01 0x00000110   Response Header (0x42007a) 0x01 0x00000048     Protocol Version (0x420069) 0x01 0x00000020       Protocol Version Major (0x42006a) 0x02 0x00000004 0x00000001       Protocol Version Minor (0x42006b) 0x02 0x00000004 0000000000     Time Stamp (0x420092) 0x09 0x00000008 2011-07-18 22:38:25 GMT     Batch Count (0x42000d) 0x02 0x00000004 0x00000001   Batch Item (0x42000f) 0x01 0x000000b8     Operation (0x42005c) 0x05 0x00000004 0x0000000e     Unique Batch Item ID (0x420093) 0x08 0x00000001 38     Result Status (0x42007f) 0x05 0x00000004 0000000000     Response Payload (0x42007c) 0x01 0x00000080       Unique Identifier (0x420094) 0x07 0x00000040 83916B87CD4C20CC27A41DE16A47352750523787C9CBF98CD8618BE9E3D5854C       Attribute (0x420008) 0x01 0x00000030         Attribute Name (0x42000a) 0x07 0x00000006 x-attr         Attribute Index (0x420009) 0x02 0x00000004 0x00000001         Attribute Value (0x42000b) 0x07 0x00000008 newvalue or can it skip it as it does here: Response Message (0x42007b) 0x01 0x00000100   Response Header (0x42007a) 0x01 0x00000048     Protocol Version (0x420069) 0x01 0x00000020       Protocol Version Major (0x42006a) 0x02 0x00000004 0x00000001       Protocol Version Minor (0x42006b) 0x02 0x00000004 0000000000     Time Stamp (0x420092) 0x09 0x00000008 2011-07-18 22:37:04 GMT     Batch Count (0x42000d) 0x02 0x00000004 0x00000001   Batch Item (0x42000f) 0x01 0x000000a8     Operation (0x42005c) 0x05 0x00000004 0x0000000e     Unique Batch Item ID (0x420093) 0x08 0x00000001 37     Result Status (0x42007f) 0x05 0x00000004 0000000000     Response Payload (0x42007c) 0x01 0x00000070       Unique Identifier (0x420094) 0x07 0x00000040 83916B87CD4C20CC27A41DE16A47352750523787C9CBF98CD8618BE9E3D5854C       Attribute (0x420008) 0x01 0x00000020         Attribute Name (0x42000a) 0x07 0x00000006 x-attr         Attribute Value (0x42000b) 0x07 0x00000008 newvalue Denis From: Pochuev,Denis Sent: Monday, July 18, 2011 11:19 AM To: '[email protected]' Subject: Attribute index clarification All, I was wondering if I can get a clarification on the part of the spec that describes the attribute index handling. Here’s the relevant sentence: “ Attributes that have a single instance have an Attribute Index of 0, which is assumed if the Attribute Index is not specified. ”. I don’t understand how to interpret the first part of the sentence. It clearly should not imply that all single-instance attributes SHALL have index 0. What exactly is it saying? Regarding the second part of the sentence, where exactly is the index not specified? Is it a part of a Register operation? Is it a part of Get Attributes or Add/Modify/Delete Attributes? Is it the same in for all of these operations? I believe the intent was to say that if during Register the index is skipped by the client, the server should assign it index 0. Is that correct? What I’m also trying to understand is how to deal with non-zero single instance attributes. For example, suppose I have a single attribute of index 1 and my client intending to modify this attribute does not include an index, what should the result of the operation be? In the same situation, if the client is sending Get Attributes, should the index be returned along with the attribute? Thank you for your help, Denis The information contained in this electronic mail transmission may be privileged and confidential, and therefore, protected from disclosure. If you have received this communication in error, please notify us immediately by replying to this message and deleting it from your computer without copying or disclosing it.

[Date Prev]  |  [Thread Prev]  |  [Thread Next]  |  [Date Next]   —  [Date Index]  |  [Thread Index]  |  [Month Index]  |  [List Home]