[OASIS Issue Tracker] (DSSX-59) Date/Date-time modelling in JSON

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

Andreas Kuehne created DSSX-59:
----------------------------------

             Summary: Date/Date-time modelling in JSON
                 Key: DSSX-59
                 URL: https://issues.oasis-open.org/browse/DSSX-59
             Project: OASIS Digital Signature Services eXtended (DSS-X) TC
          Issue Type: Improvement
            Reporter: Andreas Kuehne
            Assignee: Andreas Kuehne


Received thru the DSS-X public comments list from Neil Crossley on the 2019-08-23:

Â

The JSON schema and Swagger schema are consistent in their modelling of date-time:
Swagger: 
[https://swagger.io/docs/specification/data-models/data-types/#string]
JSON schema draft 4 validation: 
[https://tools.ietf.org/html/draft-fge-json-schema-validation-00#section-7.3.1]
JSON schema latest validation: 
[https://json-schema.org/latest/json-schema-validation.html#rfc.section.7.3.1]

Â

That is, time is represented as a string with a specific format. The JSON schema declaration looks like this:
 type: 'string'
 format: 'date-time'

Instead, dss-core consistently employs the following:
 type: 'number'
 format: 'utc-millisec'

The use of number instead of string does not conform to the standard. While a lossless transformation is possible, I would like to point out that this is a custom, non-standard declaration that may not always be supported by the employable tools.



--
This message was sent by Atlassian JIRA
(v7.7.2#77003)