[OASIS Issue Tracker] (UBL-99) Criterion Requirement Applicable Identifier

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

     [ https://issues.oasis-open.org/browse/UBL-99?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Enric Torregrosa updated UBL-99:
--------------------------------

    Description: 
A set of 0..n "Applicable Identifier" (Identifier+ Description + Identifier Type) would be necessary in the UBL TenderingCriterionRequirement element.

Rationale: (e.g.) The CA needs to list the Identifiers of the Lots to which a certain number of requirements apply to. In the case of the "self-contained" ESPD this happens for all the Criteria of Part IV.

Possible Solutions: 

1) Treat as a new ASBIE
2) Treat as a Criterion with multiple requirements
3) Other...

Preferred solution: 2


  was:
A set of 0..n "Applicable Identifier" (Identifier+ Description + Identifier Type) would be necessary in the UBL TenderingCriterionRequirement element.

Rationale: (e.g.) The CA needs to list the Identifiers of the Lots to which a certain number of requirements apply to. In the case of the "self-contained" ESPD this happens for all the Criteria of Part IV.


> Criterion Requirement Applicable Identifier
> -------------------------------------------
>
>                 Key: UBL-99
>                 URL: https://issues.oasis-open.org/browse/UBL-99
>             Project: OASIS Universal Business Language (UBL) TC
>          Issue Type: New Feature
>          Components: Artefacts
>         Environment: Data Model
>            Reporter: Enric Torregrosa
>            Assignee: Ken Holman
>            Priority: Critical
>
> A set of 0..n "Applicable Identifier" (Identifier+ Description + Identifier Type) would be necessary in the UBL TenderingCriterionRequirement element.
> Rationale: (e.g.) The CA needs to list the Identifiers of the Lots to which a certain number of requirements apply to. In the case of the "self-contained" ESPD this happens for all the Criteria of Part IV.
> Possible Solutions: 
> 1) Treat as a new ASBIE
> 2) Treat as a Criterion with multiple requirements
> 3) Other...
> Preferred solution: 2



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