Both BT-157-LotsGroup and BT-271-LotsGroup are mapped to the property hasLaunchFrameworkAgreementMaximumValue

[csnyulas]

As part of the eForms to RDF mappings both eForms SDK fields BT-157-LotsGroup and BT-271-LotsGroup are mapped to the property epo:hasLaunchFrameworkAgreementMaximumValue. This was accepted as part of the competition and result notice subtype 29 mappings (EF10-24 and EF29 mappings in tag 1.0.0-rc-9), but I want to raise this issue as maybe there should be done something about it in future versions of ePO.

The conflation of the meaning of these two fields was recognized some longer time ago in eForms SDK, and there seems to be no solution for that yet: OP-TED/eForms-SDK#523

See also this related issue that was closed a longer time ago: OP-TED/ted-rdf-mapping-eforms#3

[andreea-pasare]

Based on the eForms Annex, BT-271 should not be used for a Lot Group, but only for Procedure or Lot. for Lot Group it should be used BT-157.