kmip-interop-tech — archive

[Tim Hudson]

On 5/09/2012 6:37 AM, Jim Flood wrote: * SHALL the Name attribute of the Template be passed in the Template Attribute of the Register Request Payload, rather than the Template itself? My view is that the Name should be passed in the Template Attribute in Attribute format. However there is a use case (test case) which does this differently - something which I think should be fixed. * SHALL the attributes of the Template that contribute to created objects (later, in subsequent operations) be passed in the Template object of the Register's Request Payload, OR, can they also be specified in the Template Attribute? (I prefer the latter to be consistent with Create.) My view is that the first is the logical option. Attributes contributed to other objects must be specified in the Template structure. However the specification allows for the usual inheritance from other templates and from the template attribute list - but those I think can reasonably be interpreted as applying the the template object and not to contributing to the 'value' of the template. That interpretation I do not think is precluded by the specification. Consistency with Create would argue that anything specified in Register for attributes are attributes of the object itself and not the value - i.e. those items in TemplateAttribute are for the template itself and only those items in the Template structure apply to created objects. I keep coming back to None of the client-settable attributes specified in a Template except the Name attribute apply to the template object itself, but instead apply to any object created using the Template. That to me always made it clear the attributes being contributed to objects came in the Template structure. Mixing up the other attributes which apply to the template object leads to all manner of confusion. Tim.