Stay organized with collections Save and categorize content based on your preferences.
April 14, 2006
With our recent infrastructure changes, we've made some minor changes in how we process the lastmod attribute. If you omit the time portion, it defaults to midnight UTC (00:00:00Z). If you specify a time, but omit the timezone, you'll get an invalid date error. You'll also get an invalid date error if you specify an invalid date or time (like February 80th) or the date isn't in the correct format. You'll no longer see errors associated with future dates.
Dates must use W3C Datetime encoding, although you can omit the time portion. For instance, the following are both valid:
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],[],[],["Recent infrastructure changes have led to updates in processing the `lastmod` attribute. Omitting the time in `lastmod` now defaults to midnight UTC. Specifying a time without a timezone, providing an invalid date/time, or using an incorrect format will result in an error. Future dates will no longer generate errors. Dates must adhere to W3C Datetime encoding, but the time portion is optional, with examples of valid formats provided.\n"]]
