[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] (UBL-78) Tender/cac:TenderedProject cardinality
[ https://issues.oasis-open.org/browse/UBL-78?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=65650#comment-65650 ] Oriol Bausa Peris commented on UBL-78: -------------------------------------- Each cac:TenderedProject can be identified by cac:TenderedProject/cac:ProcurementProjectLot/cbc:ID So in case there are no lots, the EO can define several Tendered Projects referring just the ContractFolderID (no cac:ProcurementProjectLots) and using the VariantID (as there can be variants sent to a single procurement project. In case there are lots, the EO identifies to which lot the tendered Project refers to using the ProcurementProjectLot/ID. > Tender/cac:TenderedProject cardinality > -------------------------------------- > > Key: UBL-78 > URL: https://issues.oasis-open.org/browse/UBL-78 > Project: OASIS Universal Business Language (UBL) TC > Issue Type: Improvement > Components: Documents and business objects > Reporter: Ken Holman > Assignee: Ken Holman > Priority: Minor > > Tender/cac:TenderedProject: current cardinality is 1..*; however since the tendered project is solely identified/referenced by the Tender/cbc:ContractFolderID the cac:TenderedProject currently serves only as a vessel for the lotIdentifier within the project (atleast for the syntax mapping done by CEN/BII). So the cardinality should rather be 0..* instead. -- 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]