[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] (DSSX-48) Provide explanantion of ResultMajors and ResultMinors in core 2.0
Andreas Kuehne created DSSX-48: ---------------------------------- Summary: Provide explanantion of ResultMajors and ResultMinors in core 2.0 Key: DSSX-48 URL: https://issues.oasis-open.org/browse/DSSX-48 Project: OASIS Digital Signature Services eXtended (DSS-X) TC Issue Type: Improvement Components: Core Reporter: Andreas Kuehne Assignee: Andreas Kuehne Fix For: csprd02 Juan Carlos provides comment by mail: Clause 4.1.7. Component Result. URIs for result major are given without a single explanation. Additionally, no URNs are given for result minor. This clause seems to underspecify the Result component. Could you please consider the possibility of incorporating in this clause all the contents related to URNs for result major and result minor present in DSS core v1.0? I do not see any reason for dropping them, as this could be interpreted as a voluntary wish of the committee to deprecate the aforementioned URNs and/or change their semantics, giving place to a backwards compatibility problem. Â After sending my comments, I noticed that the core v2.0 actually includes the ResultMinor URIs with a short explanation in a different clause than the one where the Result component is specified. I guess that this is the reason why I did not notice their inclusion...maybe you could consider inserting a reference to clause 9.2 within 4.1.7. Something like: The optional ResultMinorelement MUST contain a URI. Â [DSS-4.1.7-2] . Clause 9.2 lists the set of values that are used in this document. Â -- 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]