OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

dss-x message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: [OASIS Issue Tracker] (DSSX-21) Comment to core 2.0. Drop square for conformance requirements

Juan Cruellas created DSSX-21:

             Summary: Comment to core 2.0. Drop square for conformance requirements
                 Key: DSSX-21
                 URL: https://issues.oasis-open.org/browse/DSSX-21
             Project: OASIS Digital Signature Services eXtended (DSS-X) TC
          Issue Type: Bug
            Reporter: Juan Cruellas

I Propose to drop the usage of square for conformance check as I think that is strongly error prone. I am not sure at all about the worthiness of using this artifact.

For starting with, I think that there are a good number of places where, if used, it is missing::

. Clause 2.2.12 Optional Input Schemas. Ther it is sayd that RefType and SchemaRefs MUST NOT be used....to me this is a requirement that has to be checked if checking conformance: if one of them is present then the element is not conformance.

. Clause 2.13, 2.14: RequestID. Also corresponds to a conformance requirement in a response

In addition to that along lots of places where there are sentences like "This XXX(an element) MUST include a XXX". To me this is certainly a requirement that a conformance testing tool should test, but it is not preceeded with a square.

I propose then to drop the usage of these squares for identifying conformance requirements.

If we do that, then the conformance requirements will be identified by the sentences that contain one of the words defined in RFC 2119.

If the word appears in sentences like "the element XXX MUST have the XXX attribute" or "the XXX attribute MUST have the following value: ...:" they are clearly conformance requirements for the format and the contents of the protocol messages.

In sentences like "For each DocumentHash in InputDocuments the server MUST perform the following steps" there is clearly a requirement on the way the server must behave but not a conformance requirement on the contents of a certain component of the protocol.

This message was sent by Atlassian JIRA

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]