[OASIS Issue Tracker] (DSSX-60) Binary content representation

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

    [ https://issues.oasis-open.org/browse/DSSX-60?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=74747#comment-74747 ] 

Detlef Huehnlein commented on DSSX-60:
--------------------------------------

As the semantic aspects are defined in the text, it does not seem to be an urgent problem, that the expressiveness of the schemata alone is slightly different.Â

I would recommend to close this ticket.

> Binary content representation
> -----------------------------
>
>                 Key: DSSX-60
>                 URL: https://issues.oasis-open.org/browse/DSSX-60
>             Project: OASIS Digital Signature Services eXtended (DSS-X) TC
>          Issue Type: Improvement
>            Reporter: Andreas Kuehne
>            Assignee: Andreas Kuehne
>            Priority: Major
>
> Received thru the DSS-X public comments list from Neil Crossley on the 2019-08-23:
> The SimpleContent declaration is consistently mapped to an optional property in the JSON schema. Strictly speaking, this leads to a different semantic expressiveness in the resulting JSON schema. Consider a valid XML instance of X509DigestType - it's content is always present, but possible empty. However, a JSON object instance of dss2-X509DigestType may have no value property, or it's property 'value' may contain the empty string. Both JSON objects are valid but not necessarily or obviously equivalent.



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