[OASIS Issue Tracker] (UBL-104) QualificationApplicationResponse Confidentiality Indicator

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

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

Enric Torregrosa commented on UBL-104:
--------------------------------------

1. In the case of the ESPD, the fact of signaling one TenderingCriterionResponse as confidential should entail treating all the TenderingCriterionResponses of a Requirement Group as confidential, too.

2. It makes no sense to have the ConfidentialityLevelCode in the Criterion (and we currently have it in the QualificationApplicationRequest too!!!) --> We should create a new issue only for this, shouldn't we?

3. I just realised that a Criterion aggregates "TenderingCriteriaGroup". I think this should be named "TenderingCriterionRequirementGroup" We should create a new issue only for this, shouldn't we?






> QualificationApplicationResponse Confidentiality Indicator
> ----------------------------------------------------------
>
>                 Key: UBL-104
>                 URL: https://issues.oasis-open.org/browse/UBL-104
>             Project: OASIS Universal Business Language (UBL) TC
>          Issue Type: Improvement
>          Components: Artefacts
>            Reporter: Enric Torregrosa
>            Assignee: Ole Madsen
>            Priority: Critical
>
> In QualificationApplicationResponse, the Confidentiality Level Code shouldn't apply to the Criterion but to the Response.



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