[OASIS Issue Tracker] (DSSX-58) Numbers in element names

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

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

Detlef Huehnlein commented on DSSX-58:
--------------------------------------

Yes, the mapping between XML and JSON names is made explicit in the corresponding tables in the standard text and hence there does not seem to be any change necessary. I would propose to close the ticket.

> Numbers in element names
> ------------------------
>
>                 Key: DSSX-58
>                 URL: https://issues.oasis-open.org/browse/DSSX-58
>             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:
> ÂNumbers in element names
> Numbers in element names lead to seemingly arbitrary property names in the corresponding JSON schema, where an entire prefix and/or suffix is dropped in the corresponding JSON schema. For example: DetailType contains the element Base64Content, dss2-DetailType has the property b64Content. Another example: AdditionalKeyInfoType contains X509Digest, X509SubjectName, X509SKI, X509Certificate, X509CRL; dss2-AdditionalKeyInfoType has x509Digest, sub, ski, cert, name, crl. Sub-note: this may be related to the previous issue 2., as both sub and
> name correspond to X509SubjectName.
> This issue should otherwise not lead to problems when using the schemas, as long as a lossless transformation exists (every JSON schema property maps only to a single XML-schema element), but a reader of the JSON and XML schemas should still be aware of this.



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