[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] (UBL-121) Expected COLLECTIONS of Codes and Identifiers
[ https://issues.oasis-open.org/browse/UBL-121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=66588#comment-66588 ] Ole Madsen commented on UBL-121: -------------------------------- We do not understand why not use TenderingCriterionPropertyGroup? > Expected COLLECTIONS of Codes and Identifiers > --------------------------------------------- > > Key: UBL-121 > URL: https://issues.oasis-open.org/browse/UBL-121 > Project: OASIS Universal Business Language (UBL) TC > Issue Type: Improvement > Components: Artefacts > Reporter: Enric Torregrosa > Assignee: Ole Madsen > Priority: Critical > > In cac:TenderingCriterionProperty, instead of having the elements cbc:ExpectedID and cbc:ExpectedCode we'd need cac:ExpectedID (cardinality 0..n) and cac:ExpectedCode (0..n). > Rationale: > 1) need to specify multiple IDs for the EO. Examples: (a) VAT number AND Pre-Qualification System ID for the EO; (b) Expected LOTS IDs, other... > 2) need to specify multiple CPV codes to describe the products, services or works that a CA expects an EO is capable to deliver, perform or execute -- This message was sent by Atlassian JIRA (v6.2.2#6258)
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]