We parse then just fine, my point is in generating them.
Since it is a Mandatory test case we have to generate the exact same value "2000-01-01T00:00:00+10:00"
in the request even though a GMT version would work just a fine.
Mark
In XML the Date-Time encoding is explicitly noted in 5.4.1.6.12 as xsd:dataTime and those are valid values.
5.4.1.6.12 Date-Time
For XML, value uses [XML-SCHEMA]
type xsd:dateTime
<ArchiveDate
type="DateTime"
value="2001-01-01T10:00:00+10:00"/>
Your XML to TTLV code must be able to handle the timezone specification and convert into UTC prior to going into TTLV form.
The example there shows precisely that timezone in use (and always has done so).
I did place the date time values in prior test cases in +00:00 / Zulu / UTC - but there is absolutely no requirement to do so.
XML code needs to be able to handle all the supported xsd:dateTime values.
Tim.
On Tue, Dec 25, 2018 at 9:37 AM Mark Joseph <> wrote:
From the KMIP Spec:
Date-Time values are POSIX Time values encoded as Long Integers. POSIX Time, as described
in IEEE Standard 1003.1 [IEEE1003-1], is the number of seconds since the Epoch (1970 Jan 1,
00:00:00 UTC), not counting leap seconds.
So to get the real number of seconds for the Protect Stop Date I have to put the time below into UTC time first just to generate the proper TTLV
Can we change all of these to GMT please.
<RequestMessage>
<RequestHeader>
<ProtocolVersion>
<ProtocolVersionMajor type="Integer" value="2"/>
<ProtocolVersionMinor type="Integer" value="0"/>
</ProtocolVersion>
<BatchCount type="Integer" value="1"/>
</RequestHeader>
<BatchItem>
<Operation type="Enumeration" value="Locate"/>
<RequestPayload>
<Attributes>
<ObjectType type="Enumeration" value="SecretData"/>
<ProtectStopDate type="DateTime" value="2000-01-01T00:00:00+10:00"/>
<ProtectStopDate type="DateTime" value="2000-02-10T00:00:00+10:00"/>
</Attributes>
</RequestPayload>
</BatchItem>
</RequestMessage>
Best,
Mark Joseph
P6R, Inc
408-205-0361
