Comments (5)
In OpenProject the due date of work packages (issues) are in Date format. For our users it is rarely necessary to be an exact point of time. How to export this properly to BCF as DateTime indeed is not specified I believe. Currently we export the due dates as 00:00 UTC. However, that is simply due to the fact, that we did not care too much about that topic yet.
From our experience with DateTime fields on international projects is that people don't really know/care about that issue even outside our application. They have similar issues with their calendars etc. and are incapable to solve this. This becomes apparent when suddenly the week number is different in the US from the EU, like it is this year. This is when people start calling us.
from bcf-xml.
Hey @pasi-paasiala, thank you for the issue! As discussed in the call earlier today, we've found the DueDate
property a bit hard to handle in actual implements.
Just as you described, in applications (that we know of), only the date part is used, e.g. due by June 21st, never the time part, e.g. due by June 21st at 14:00.
However, for the data type behind, we're using xs:dateTime
, which contains a) a date, b) a time and c) a time offset (for time zone handling.
Now, this introduces the following problem:
- Assume I'm a user in Germany, being on CEST (UTC +2 hours). I create an issue and want it to be due at June 21st.
- My client will now save this as
2021-06-21T00:00:00+02:00
, meaning my local time, midnight, with a time zone offset of+02:00
hours to UTC. - This would map to
2021-06-20T22:00:00+00:00
in UTC, meaning the day before at 10 pm. - Let's imagine a colleague from the UK opens the issue, so it's transformed in his application using his local timezone UTC+1 (I don't know if they're using DST there actually, so this example might be off, but it transports the message)
- That colleague now sees internally
2021-06-20T23:00:00+01:00
, which is displayed as20.06.2021
, one day off from what was intended.
So, we have a mismatch between the spec and the actual usage:
Applications generally only work with a date component for due dates, while the schema currently wants an exact point in time (date + time of day).
We now need to find a solution for this😀
One possibility would be to change the due date to only represent a date, without any time zone offsets or any time component at all. This has the drawback of degrading the property to no longer support times, e.g. due by Monday at 17:00 would no longer be possible then.
Input from others would be greatly appreciated, especially from @jasollien, @wielinde and DDS (if anyone knows the GitHub username of Thomas Frankenmölle, pinging him in a comment would be great😀), since they've also got implementations but weren't present today.
Just some more thoughts from me: Changing the data type is a breaking change in the schema, and, in my opinion, too late - we've already finalized the v3.0 release, and communicated this to bSI. In the current situation, we could rather look into how to solve this issue with the current standard and gather some experience that will then influence the next version.
from bcf-xml.
I understand the issue. However, by taking away the "time", the dueDate now ill have different meaning depending on the time zone. That will lead into other misunderstandings, for example: The due date is 15 hours later in the US than in Russia.
By having a time, the due will always be at the same time, even though it might be in the middle of the night for some countries.
That said: Bimsync always uses the time: 00:00UTC
from bcf-xml.
IMO, all data that refer to a time point
should be UTC time with Date and Time and Offset.
from bcf-xml.
We briefly discussed this in the call, we might not have to change the behavior, but document the conventions used when dealing with DueDate
s.
from bcf-xml.
Related Issues (20)
- ReferenceSchema is mentioned as "optional" in documentation, but is mandatory in XSD HOT 1
- BCF v3 Project optionality is different between docs and schema
- File attribute optionality HOT 1
- Deleted
- Field of view documentation HOT 1
- BCF-XML validator HOT 4
- Remove outdated section about one-to-many relations between viewpoints and comments HOT 1
- Missing Topic Label HOT 3
- Update README to include contact details for the cde group HOT 1
- Tools that support bcf 3.0 HOT 1
- CameraViewPoint units HOT 2
- What is the "ExtensionSchema" in BCF 2.0/2.1? HOT 2
- Topic GUID mismatch HOT 4
- Is multiple topics in BCF markup supported? HOT 2
- proposal: adding "GeoPoint" HOT 2
- (Question) - Why are viewpoints stored in the topic folders? HOT 2
- How to save the GUID of an IfcElementType in a bcf file HOT 1
- Add `minOccurs="1"` to all lists that should not be empty if present HOT 1
- Sync up BCF XML with BCF API
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from bcf-xml.