[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] (DSSX-57) Element name capitalization
[ https://issues.oasis-open.org/browse/DSSX-57?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=74741#comment-74741 ] Andreas Kuehne commented on DSSX-57: ------------------------------------ There seems to be a glitch in the derivation of the JSON schema from the Java object model. Needs to be fixed or workarounded! > Element name capitalization > --------------------------- > > Key: DSSX-57 > URL: https://issues.oasis-open.org/browse/DSSX-57 > Project: OASIS Digital Signature Services eXtended (DSS-X) TC > Issue Type: Improvement > Reporter: Andreas Kuehne > Priority: Major > > Received thru the DSS-X public comments list from Neil Crossley on the 2019-08-23: > Â > Element name capitalization > There seems to be some problem with prefixes. When I look for XML element names that do not strictly follow PascalCase naming convention, but have a fully capitalized prefix (such as XPath; OCSPResponse in AdditionalKeyInfoType, but not X509Digest), I can find two candidate properties in the corresponding JSON definition instead of the expected one. For example: dsb-SignaturePtrType, dsigrw-TransformType (XPath as xpath and xPath), dss2-SignaturePlacementType (XPathAfter as xpathAfter and xPathAfter; XPathFirstChildOf as xpathFirstChildOf and > xPathFirstChildOf), dss2-AdditionalKeyInfoType (OCSPResponse as ocspresponse and ocsp). -- 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]