Structure of an eForms XML document

[ColinMaudry]

Figuring out the structure of an eForms XML document and how the data is distributed into XML blocks may help structuring the guidance in a handy way for implementers.

I'll use the can_24_FRA_comments.xml example document from the eForms-SDK.

[ColinMaudry]

The name of the root element determines the notice type, such as ContractAwardNotice (CAN). Its attributes contains no useful information.

• /*/ext:UBLExtensions/ext:UBLExtension/ext:ExtensionContent/efext:EformsExtension:
  • efac:NoticeSubType/cbc:SubTypeCode: the notice number (1 to 40)
  • efac:Organizations: the description of all the parties of the procedure (buyer, tenderers, mediators, etc.), similar to the .parties array in OCDS
  • efac:Organization/efac:Company
    • identifiers
    • contact information
  • efac:NoticeResult (in ContractAwardNotice notices only): details of the awards
  • cbc:TotalAmount: total amount of all awards
  • efac:LotResult: one for each awarded lot
    • tender statistics (number of SMEs, highest/lowest, etc.)
    • efac:TenderLot: reference to the specs of a lot (/*/cac:ProcurementProjectLot)
    • efac:LotTender: reference to a tender on the lot (../efac:LotTender)
  • efac:LotTender: one per tender per lot, details of a tender
    • efac:TenderLot: reference to the specs of a lot (/*/cac:ProcurementProjectLot)
    • efac:TenderingParty: reference to a tendering party (../efac:TenderingParty)
    • amount
    • specific terms (subcontracting...)
  • efac:TenderingParty: maps a party (efac:Organization) to a tendering party ID (or several?)
  • efac:SettledContract: similar to an OCDS Contract object
    • title
    • issue date
    • award date
    • efac:LotTender: reference to the tender that led to this contract (../efac:LotTender)
• cbc:ID Notice identifier (BT-

To be continued...

[jpmckinney]

Closing as the eForms SDK has been much improved since this issue was opened.