Feature Request: Concerning the ocel:timestamp ( during Export)

[Kena-Njonge]

Description:

Hello, I encountered an issue when working with an event log that I augmented. When I call the function isocel20(), it correctly returns TRUE, indicating compliance with the OCEL 2.0 standard. However, when I tried to export the OCEL using write_ocel2_sqlite(), I encountered the following error:

sqlite3.ProgrammingError: Error binding parameter 10: type 'Timestamp' is not supported

Upon investigation, I discovered that during certain operations on the ocel:timestamp column, its entries were unintentionally converted from datetime to Timestamp. Despite creating a new instance of the pm4py.ocel.OCEL class, the column’s type remained as object, which ultimately caused the export operation to fail.

Suggestion:
Validation in isocel20(): Enhance the isocel20() function to include validation that ensures the ocel:timestamp column is strictly of type datetime. While I understand that this is not a formal requirement of the OCEL 2.0 specification, such validation would help users identify issues with the column type early and avoid export errors.

Alternatively, the ocel:timestamp column could be automatically cast back to datetime during the export process.