Re: [kmip] KMIP Spec 3.0 wd07 question

The item types have the same handling as TextString values (see the section on item types) but the added semantics of knowing what they actually are.

If you have a type for an attribute or a field within a structure that is Name Reference then the value contained in text form (like a TextString) points to an object that has an attribute Name that has that matching value.

Remember Name is no longer a structure - it is just a straight text string value (see section 4.33).

If you have a type for an attribute or a field within a structure that is Reference then the value contained in text form (like a TextString) points to an object that has an attribute Unique Identifier that has that matching value.

You are perhaps looking for complexity where there isn't any - these are just strongly typed text strings allowing for a much less complicated handling of how we refer between objects.

Type old Link attribute and concept of Link Type has been replaced with individual attributes - see section 4.32.

You are correct in that we have missed the Enumeration+Integer table at the front of that section as links can be internal cross-references for flows between batch items.

Tim.

(all section references are to wd07)

On Thu, Oct 29, 2020 at 8:07 AM Mark Joseph <mark@p6r.com> wrote:

They are new item types and are plain strings - i.e. the equivalent of the NameValue and the LinkedObjectIdentifier for Names and Link as discussed in the proposals.

Test cases haven't been produced as yet as we are still working through completing the specification scope before the test cases.

Ok so the "Name Reference" item type maps to "NameValue" (Text String).

And the "Reference" item maps to LinkedObjectIdentifier.
It is just that LinkedObjectIdentifier is not just a plain string, it can also has an Enumeration and Integer type as well.

I read over several of the proposals and did not see this mapping which one has it?

Best,
Mark Joseph
P6R, Inc

kmip message