[OASIS Issue Tracker] (DSSX-22) Include pieces of JSON schema

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

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

Stefan Hagen commented on DSSX-22:
----------------------------------

Did we already decide if we continue to follow the JSON Schema route (or maybe do not)? I guess we require quite complete alternate versions to meaningfully decide, what to bet on. Separating the parts, and keeping conceptual, JSON and XML parts separated only cross referencing is I think the only reasonable way, but as long we are not ready with the refactoring, I guess this is more guestimating ... a more practical point (also related to the other format XML): We will profit from clear strategies to keep the codes (XML schema and JSON equivalent artifacts) in sync with the only secondary prose snippets embedded.

> Include pieces of JSON schema
> -----------------------------
>
>                 Key: DSSX-22
>                 URL: https://issues.oasis-open.org/browse/DSSX-22
>             Project: OASIS Digital Signature Services eXtended (DSS-X) TC
>          Issue Type: Bug
>            Reporter: Juan Cruellas
>
> As I said time ago in a proposal that was commented but on which, as far as I am aware, there was not ever a formal decision made at a meeting, I am not sure that the approach taken for showing the JSON syntax is correct. I proposed a different alternative. 
> I would like that we discuss it taking a look to that proposal in order to foresee what would be the oucome of following one way or following the other, and once done make a decision within the TC



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)