OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

dss-x message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

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

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:
JSON schema draft 4 validation: 
JSON schema latest validation: 


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

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]