Abstract
Fix up the daterange syntax in draft05 for draft06
Status
Open
Rationale
There are glaring mistakes in the draft05 on the daterange syntax.
Proposal
Replace examples in 11.1 URI Templates with this:
11.1 URI Templates Here are some examples of template URIs and corresponding populated values: http://example.org/blog/edit/{index} http://example.org/blog/edit/3-9 http://example.org/blog/edit/{index}/foo http://example.org/blog/edit/0-100/foo http://example.org/blog/edit/{daterange} http://example.org/blog/edit/daterange=\ 2003-12-13T18:30:02Z-2003-12-13T18:30:02Z http://example.org/blog/edit?dr={daterange}/bar/ http://example.org/blog/edit?dr=\ 2003-12-13T18:30:02Z-2003-12-13T18:30:02Z/bar/
replace 11.2.2 in 05 with this:
11.2.2 {daterange} URI template variable A URI Template with the variable 'daterange' allows querying for Atom Entries in a Collection according to their 'atom:updated' property. The value of the {daterange} criterion should be a pair of ISO formatted dates separated by a dash character; either index may be optionally omitted, in which case the range is understood as stretching to infinity on that end. daterange-specifier = [iso-date] "-" [iso-date] The [iso-date] terminal MUST conform to the "date-time" production in [RFC3339]. In addition, an uppercase "T" character MUST be used to separate date and time, and an uppercase "Z" character MUST be present in the absence of a numeric time zone offset. For example, suppose the client is supplied this {daterange} URI Template: http://example.org/blog/edit/{daterange} If the client wants the entries in the collection between January and February 2006 it would substitute the brace-delimited parameter {daterange} with the desired selection value, giving this URI: http://example.org/blog/edit/2006-01-01T00:00:00Z-\ 2006-02-01T00:00:00Z
Impacts
next app draft (06)