You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Several eForms fields provide a date value, while the corresponding ePO property has xsd:dateTime as its range.
This is a problem, since we cannot generate a valid xsd:dateTime value only from a date value (without resorting to adding some artificial time component, which is not present in the input data), and xsd:date and xsd:dateTime have incompatible structure.
There are three potential solutions, each generating a separate problem:
Create a valid xsd:dateTime value from a simple date, by adding a fictive time component suffix, such as T00:00:00 or T23:59:59, after the date. This is undesirable since the output will not be a true reflection of the input.
In the output use the date value as it appears in the input, but type it xsd:dateTime. This will create an invalid RDF
In the output use the date value as it appears in the input, and type it xsd:date. This will create an RDF that will raise SHACL violations against the ePO SHACL shapes.
OP suggested we implement option 3 for now, however the problem will be further discussed and potentially addressed in the ePO WGs.
Here is a list of fields where this problem occurs:
BT-536-Lot (Duration Start Date)
BT-537-Lot (Duration End Date)
BT-78-Lot (Security Clearance Deadline)
BT-719-notice (Change Procurement Documents Date)
BT-1451-Contract (WinnerDecisionDate)
and here are the related ePO classes and properties
Several eForms fields provide a date value, while the corresponding ePO property has
xsd:dateTime
as its range.This is a problem, since we cannot generate a valid
xsd:dateTime
value only from a date value (without resorting to adding some artificial time component, which is not present in the input data), andxsd:date
andxsd:dateTime
have incompatible structure.There are three potential solutions, each generating a separate problem:
xsd:dateTime
value from a simple date, by adding a fictive time component suffix, such asT00:00:00
orT23:59:59
, after the date. This is undesirable since the output will not be a true reflection of the input.xsd:dateTime
. This will create an invalid RDFxsd:date
. This will create an RDF that will raise SHACL violations against the ePO SHACL shapes.OP suggested we implement option 3 for now, however the problem will be further discussed and potentially addressed in the ePO WGs.
Here is a list of fields where this problem occurs:
and here are the related ePO classes and properties
The text was updated successfully, but these errors were encountered: