forked from SWISDATA/processintel
converters.csv_to_xes: the generated XES lacks standard declarations and flattens case attributes #28
Labels
No milestone
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
ffrauenberger/ProcessIntel#28
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Severity: low (other tools can misread the generated XES)
Where
app/converters/csv_to_xes_converter.py:267-342Problem
<log>contains no<extension>declarations (Concept, Time, Lifecycle, Organizational), no<global>and no<classifier>elements. Strict XES consumers such as ProM/OpenXES import such files with warnings or lose attribute semantics.xmlnsis set as an ordinary attribute instead of through ElementTree namespace handling.case:xyz, which the XES→CSV converter produces from trace attributes, do not round-trip back to trace-level attributes.xes.version="1.0"is declared, while the 2023 IEEE XES standard uses2.0.Steps to reproduce
Expected behavior
The XES file contains the standard extension declarations, and
case:*columns become trace attributes again.Actual behavior
No extension/global/classifier declarations; former trace attributes are written as event attributes.
Fix
Emit the standard extension headers, write
case:*columns as trace attributes, and validate the output against the XES schema in tests.from
issues/BUG-028-xes-export-lacks-standard-declarations.md(code analysis of commit6bcc646, 2026-10-03)Reviewed by Codex (GPT-6) against origin/main
6bcc646eb464.Review: partially correct.
The trace-attribute round-trip loss is confirmed:
case:owneris emitted as an event attribute. The namespace bullet is not an XML defect: settingxmlnsas done here serializes a valid default namespace. Serializing and reparsing the generated output yields{http://www.xes-standard.org/}logand namespaced descendants.Please also separate schema validity from interoperability expectations. The published OpenXES schema gives
extension,globalandclassifierminimum occurrence zero. The converter declares XES 1.0, so omission alone does not establish invalidity or prove ProM/OpenXES warnings. XES 2.0 is a possible upgrade target, not evidence that any 1.0 output is automatically broken. Consumer warnings/lost semantics need a concrete import reproduction.Code references: app/converters/csv_to_xes_converter.py:284, app/converters/csv_to_xes_converter.py:334.