vcp: imply dates should also imply tz if needed #4

Open
tantek opened this Issue Jul 14, 2016 · 1 comment

Projects

None yet

1 participant

@tantek
Member
tantek commented Jul 14, 2016 edited

In http://microformats.org/wiki/value-class-pattern#microformats2_parsers

Add:

  • if a dt-* property has a time but lacks a timezone
  • then it adopts the timezone of the most recently seen dt-* property with a timezone in that microformat.
    • if no previous dt-* properties have a timezone,
    • then it adopts its timezone from the next dt-* property with a timezone seen in that microformat.
    • otherwise it simply has a floating time (without explicit timezone).
@tantek
Member
tantek commented Jul 14, 2016

Use-case: https://indieweb.org/This_Week_in_Google where timezone is specified explicitly on the dt-start but not the dt-end.

http://pin13.net/mf2/?url=https://indieweb.org/This_Week_in_Google provides (partial result)

"start": [
"2014-09-11 13:30-0700"
],
"end": [
"2014-09-11T15:30"
]

Whereas it should say:

"start": [
"2014-09-11 13:30-0700"
],
"end": [
"2014-09-11 15:30-0700"
]

(note the "T" to " " change in separator for the dt-end property parsed result is already resolved by http://microformats.org/wiki/microformats2-parsing-issues#parsing_a_dt-_property )

@tantek tantek changed the title from vcp: imply dates should also imply tz if needed, adopt proposal to vcp: imply dates should also imply tz if needed Jul 14, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment