Pending a discussion with Chuck when timezones align, my
preference would be simply to amend Table 122 in 4.49 Unique
Identifer. Given the relatively few (only) instances where it is
called out as a Text String - a change here has least overall
impact. I'd suggest the following:
"Text String" becomes "Text String or Enumeration or Integer"
Cheers,
-Tony
2017-02-24T20:38:00Z
1
19
191
1
1
209
14.00
X-NONE
X-NONE
MicrosoftInternetExplorer4
On 20-Aug-18 7:59 AM, Tim Hudson
wrote:
Yes it does change and how to show that is a
challenge I guess.
We have variable type things in
KeyValue/KeyMaterial handling already but this one hits lots
more places in the specification.
Perhaps Variable with a cross reference to the
place where we describe it?
Tony/Chuck any editor views on how to do this?
TimÂ
On Mon, 20 Aug. 2018, 4:57 am Bruce Rich, <>
wrote:
Tim,
In this proposal, doesn't the Encoding of Unique
Identifier morph from just Text String into a "union" of
Text String, Enumeration and Integer? It's now something
other than Text String, but I'm not sure how to represent
it in a implementation-language-independent fashion...
Bruce
On Thu, Jul 12, 2018 at 1:18 AM,
Tim Hudson <>
wrote:
Document Name:
kmip-spec-v2.0-wd03-MulitpleIdPlaceholders.pdf
No description provided.
Download Latest
Revision
Public Download Link
Submitter: Tim Hudson
Group: OASIS Key Management
Interoperability Protocol (KMIP) TC
Folder: Drafts
Date submitted: 2018-07-11
22:18:11
