batch implementation of feedback for TX1.3

[costezki]

batch implementation of feedback for TX1.3

• The following issues have been address:

From milestone 2023-05:

• F13: Remove "empty" ContractTerm from "Results of Design Contest" notices #425
• F20: Change IRI generation pattern for the epo:ContractModification instances #419
• F20: VII.2.3 Increase in price #418
• F20: II.2.7.4 In the case of framework agreements, provide justification for any duration exceeding 4/8 years #417
• F20: Include the epo:containsModificationsOf mappings in the CM #416
• F20: Delete epo:refersToLot relation originating from the Notice instance #415
• F20: Delete epo:announcesTender relation originating from the Notice instance #414
• F20: Change epo:announcesContract to epo-not:refersToContractToBeModified #413
• F20: Section I and IV.4 - Do not use epo:announcesRole (nor epo:refersToRole) in ContractModificationNotice #411
• F20: Change property name epo:containsModificationsOn to epo:containsModificationsOf  #410
• Feedback F13, F20, F23 PIN (issue 11 from F23 PIN, TM): V.2.4.1 Wrong usage of hasRestatedValue  #398
• Feedback F13, F20, F23 PIN (issue 10 from F23 PIN, TM): The metadata should map to the legal-basis of the Notice #397
• Feedback F23 PIN (issue 6, CM): II.1.2.1 and II.2.2.2 remove from CM #393
• Feedback F23 PIN (issue 3, TM): II.1.3: The ContractNature is accessible via the ContractTerm #390
• Feedback F23 PIN (issue 1, CM): Duplicate the rows for I.3.3.1 and I.3.4.2 #387
• Feedback F23 CAN (issue 16, TM): VI.4.3 This should be via the Procedur #386
• Feedback F23 CAN (issue 14, CM): VI.2.1-V.2.3 The predicate isSubjectToTerm is missing in CM #385
• Feedback F13, F20, F23 CAN (issue 13 from F23 CAN, TM): V.2.4.3-V.2.5 Checking of values assigned to Awarded Value #383
• Feedback F23 CAN (issue 12, CM): V.2.3.12 is out of contex #382
• Feedback F23 CAN (issue 11, CM): Section V.2.3 why does the CL1 Controlled list of Roles #381
• Feedback F23 CAN (issue 10, CM): V.2.2.6 Notes do not redirect to the Mapping Remarks sheet #380
• Feedback F23 CAN (issue 9, CM): V.2.2 Two Xpaths #379
• Feedback F23 CAN (issue 8, TM): V.0.4 Second line is considered superfluou #378
• Feedback F23 CAN (issue 7, TM): V.0.4 Does not mention the Contract.  #377
• Feedback F23 CAN (issue 5, TM): V.0.3 There are two rows for this element #376
• Feedback F23 CAN (issue 3, TM): IV.1.1.1 Interim solution is to map to procurement-procedure-type open #374
• Feedback F23 CAN (issue 2, CM): II.1.6.1 No Note Rule #373
• Feedback F20 (issue 12, TM): Section VII without having modelled the amendment of a Contract #372
• Feedback F20 (issue 9, TM): ContractModificationNotice announcesContract the ontology has ContractModificationNotice refersToContractToBeModified #370
• Feedback F20 (issue 4, CM): No mapping to supplementary code in the conceptual model #365
• Feedback F20 (issue 3, TM): Νo relation between ContractModificationNotice and AgentInRole  #364
• Feedback F20 (issue 2, TM): Two Procedures for a Modified Contract #363
• Feedback F13 (issue 13, CM): No Direct Match for the Currency #362
• Feedback F13 (issue 12, CM): V.3.4.1 Total value of the prizes #361
• Feedback F13 (issue 10, CM): V.3.3.12 Duplicate Row #359
• Feedback F13 (issue 9, TM): V.3.3: Why does the URI of the Winner have a segment Contractor #358
• Feedback F13 (issue 8, TM): V.3.0.1 issue in number of tenders #357
• Feedback F13 (issue 6, TM): Section V.0.4: It is not clear why there are three empty rows. #355
• Feedback F13 (issue 5, CM): IV.1.9 The mapping remarks does not say there is no mapping. #354
• Feedback F13 (issue 4, CM): IV.1.0 Options are not included in F13 #353
• Feedback F13 (issue 3, TM): 1.4.1 BuyerLegalType with OrganisationGroup #352
• Feedback F13 (issue 2, CM): II.1.2.1 and II.2.2.2. not needed? #351
• Feedback F13 (issue 1, CM): Empty "RML_Modules" sheet #350
• Feedback F13, F20, F23 (issue 1): legal-basis of the Notice #349

From milestone 2023-04:

• What is the intention behind mapping Procedure to "epo:hasOptions false" in F13? #335
• Fix representation of Duration, especially that of the Indefinite Duration (field II.2.8.2) #336
• Mapping of field IV.2.5 "Scheduled date for start of award procedures" for forms F21 and F22 #270
• tx1-2: remove references to publication date XPaths #248
• Conceptual model to show Procedure hasLegalBasis #290
• F22 III.1.9.1 and III.1.9.2 Not just about selection criteria #311
• II.1.6.1 Xpath is missing #302
• Typo in the rdf:type of the Winner organization defined in section V.3.3 of form F13: org:Organisation should be org:Organization #347

[swarmia]

✅  Linked to Epic TED-1302 · TX1.3 & 1.4 Re-Delivery work

[valexande]

Approve :)

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
No Duplication information