canmove, Confirmed users
2,854
edits
VCard4: Difference between revisions
Jump to navigation
Jump to search
→section 6.5.1. TZ: added issue about dropping language saying shouldn't use UTC
(→section 6.1.5. XML: more details on why an XML property is a bad idea, incorporate feedback and extra detail from Joseph Smarr) |
(→section 6.5.1. TZ: added issue about dropping language saying shouldn't use UTC) |
||
| Line 315: | Line 315: | ||
Even if it could - it would be very confusing and no guidance is provided to implementations for how to support a vCard object being in multiple time zones. | Even if it could - it would be very confusing and no guidance is provided to implementations for how to support a vCard object being in multiple time zones. | ||
In addition, the property should drop the language about "you shouldn't use UTC offset". | |||
In practice that may be quite useful ("is it the middle of the night in london right now?") and avoids all the complexity of full timezone support. | |||
In PortableContacts we chose to ONLY allow utcOffset and and in microformats we only allow UTC offsets for datetime properties - so this is an interop issue. | |||
It may be ok to leave in a warning, saying something like: "of course, this may not be perfectly accurate since differences in when/whether daylight saving time is observed may cause it to be off a bit" (editorial discretion accepted). | |||
=== section 6.5.2. GEO === | === section 6.5.2. GEO === | ||