[OASIS Issue Tracker] (UBL-83) Criterion Requirement Applicable Code

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

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

Enric Torregrosa commented on UBL-83:
-------------------------------------

We probably do not really need this, It already would have been solved by UBL2.2:

The ESPDRequest catters for 1..n TenderingCriterionRequirements. Therefore both the code and the code description can be expressed as two requirementes of one requirementgroup freely named according to the CA's needs.

> Criterion Requirement Applicable Code
> -------------------------------------
>
>                 Key: UBL-83
>                 URL: https://issues.oasis-open.org/browse/UBL-83
>             Project: OASIS Universal Business Language (UBL) TC
>          Issue Type: Improvement
>          Components: Documents and business objects
>            Reporter: Ken Holman
>            Assignee: Ole Madsen
>            Priority: Minor
>
> CriterionRequirement	"A set of 0..n ""Applicable Code"" (Code + Description) would be necessary in the UBL TenderingCriterionRequirement element. This would be used by the CA to: 
> 1) specify the CPVs for a Specific Average Turnover. See Github wiki page 2. Specific Turnover.
> 2) specify the type of financial ratios. See Github wiki page 3. Financial Ratios."	ESPDRequest and ESPDRepsonse	- 	Proposal: Lets define a new ABIE named "ApplicableCode", cardinality 0..n. This component would include two BBIEs: TypeCode and Description.



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