validator-brainstorming: Difference between revisions
Jump to navigation
Jump to search
(stub with a few ideas from IRC) |
(lat long) |
||
| Line 14: | Line 14: | ||
=== dt-end after dt-start === | === dt-end after dt-start === | ||
[[hCalendar]] validators should check to make sure that any dt-end property value is temporally after the dt-start value for the event. | [[hCalendar]] validators should check to make sure that any dt-end property value is temporally after the dt-start value for the event. | ||
== longitude lattitude == | |||
longitude and latitude could be checked to see if they were within the right number range i.e. < 180/90 and > -180/-90. | |||
== ... === | == ... === | ||
Revision as of 19:18, 2 December 2012
<entry-title>validator brainstorming</entry-title>
This article is a stub. You can help the microformats.org wiki by expanding it.
What should a microformats validator do?
The existing validators are quite good at some things, yet could certainly be better. Let's collect some brainstorms for improvement beyond just, add microformats2 support to existing validators.
data validation
dt properties
Validators could check the values of "dt-*" properties for date, time, timezone and duration errors.
dt-end after dt-start
hCalendar validators should check to make sure that any dt-end property value is temporally after the dt-start value for the event.
longitude lattitude
longitude and latitude could be checked to see if they were within the right number range i.e. < 180/90 and > -180/-90.