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-61) xs:anyURI as a formatted string


Andreas Kuehne created DSSX-61:
----------------------------------

             Summary: xs:anyURI as a formatted string
                 Key: DSSX-61
                 URL: https://issues.oasis-open.org/browse/DSSX-61
             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:

xs:anyURI as a formatted string
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.6]
JSON schema latest validation: 
[https://json-schema.org/latest/json-schema-validation.html#rfc.section.7.3.5]

Â

Random sampling of xs:anyURI in the DSS-X definitions makes it obvious that this information is often lost in the corresponding JSON schema. For example, DetailType has the anyURI-typed element Code and attribute Type, but only type keeps the uri formatting after the transformation. Another example: none of the attributes of DocumentBaseType keep their URI type.

Â



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


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