[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=74744#comment-74744 ] 

Andreas Kuehne commented on DSSX-60:
------------------------------------

It is not expected to provide a perfect match between the different approaches applied by the different schema languages. This may even get worse once we try to expand to ASN.1 or CBOR.

The sematic section is the normative source for restrictions. The syntax section apply a best effort approach to match the given requirements. Vevertzheless we are always eager to learn about better ways to make use of the different schemes.

> 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)