[OASIS Issue Tracker] (UBL-121) Expected COLLECTIONS of Codes and Identifiers

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

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

Ken Holman commented on UBL-121:
--------------------------------

I believe this requirement is addressed by the 1..n cardinality of the use of TenderingCriterionProperty TenderingCriterionPropertyGroup.  If two identifiers need to be returned, then two <cac:TenderingCriterionProperty> elements, each with a single <cbc:ExpectedID> would be returned.  The name and description can then be used for each.

In principle, BBIEs that are not text cannot have a "repeating" cardinality (..n), and those that are text are only repeatable to accommodate multilingual content.  Unfortunately this was not always enforced in the early days, but we should be diligent to enforce it going forward.  When the concept of a BBIE needs to be repeating, it is modeled as a repeating ASBIE to an ABIE that contains the BBIE being mandatory and non-repeating.

> 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)