BT-1371 (Previous Planning Lot Identifier) does not seem "Pointless due to design" #621
-
Title quoted from https://docs.ted.europa.eu/eforms/1.0/schema/identifiers.html#pointlessDueToDesignSection In the annex, under BG-125, there's:
eForms maps BT-125 to 2 fields, including BT-125(i)-Lot. However, there's no interpretation of BT-125 in which it refers to a lot. As I understand, eForms should instead rename BT-125(i)-Lot to (I assume) BT-1371-Lot. Similarly, I'm not sure why the field BT-1251-Lot exists, since the business term BT-1251 is about a part, not a lot – but maybe there was some reason relating to PIN parts becoming CN lots. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
Hi, The XML representation is, for its UBL part, a de-normalized one and for each lot, its related information is to be found in the lot itself.
The aim of BG-125 is to identify the PIN only notices (BT-125) and their parts (BT-1251) that combined together lead to the definition of a given lot (BT-1371). The lot (BT-1371) is to be identified in the current notice while the previous planning notices (BT-125) and their parts (BT-1251) are from the previous planning notices. Please note that the trailing word in the field identifier is less about the object identified with the field than about the context the field appears in. |
Beta Was this translation helpful? Give feedback.
Hi,
The Regulation Annex is a normalized representation of eForms. Level 1 Business Groups (*) related to lots are associated with lots using a dedicated Business Terms; (when information contained in the BG ABC has to be associated with lots, BT ABC Lot Identifier is defined for that purpose).
In the case of the BG Previous Planning, the BT Previous Planning Lot Identifier is defined to associate an occurrence of one of its BG to the lot(s) it applies to.
The XML representation is, for its UBL part, a de-normalized one and for each lot, its related information is to be found in the lot itself.