kmip-interop-tech — archive

[Tim Hudson]

On 6/09/2012 6:52 AM, Jim Flood wrote: > So from the point of view of describing how people would actually use > the key store, I think the pool of attributes explanation is much more > simple than the immutable value explanation, and therefore is > preferable. (I admit that I may be biased because this is how I have > myself implemented templates -- as the pool of attributes, as Mathias > wrote.) Actually I argued that *all* objects should simply be a collection of attributes basically two years ago and was told that the model was specifically not that deliberately. Now if that is on the table that would be nice - so "values" are nothing special - and then the problems go away. Now if we want to open up that discussion I'm all for that - but making a different model for different object types is an area I think we should avoid. Tim.