On 16/08/2005, at 1:27 AM, Stefan Eissing wrote:
Ch 4: Different use of MAY and SHOULD when compared to Ch. 3.: "fh:stateful ...MAY occur" vs. "fh:archive...SHOULD occur..." On third read i think i know how you mean it. But it is a circular definition nevertheless.
I agree that there's a misalignment here, but would actually resolve it the other way. I wanted to encourage fh:archive's presence, because it will allow processors to avoid mistakes like subscribing to an archive feed. Hence, the SHOULD.
However, fh:stateful would probably be improved by saying it SHOULD (instead of MAY) occur in a subscription document's head section, and processors MUST (instead of MAY) behave as if it is present and true if fh:prev is there.
Ch. 5 similar: "MUST occur unless". If the document is an archive there are only 2 possiblities: either fh:prev is there or not. If not it will always "terminate" the archive list, won't it? You seem to have a (server-side) model in mind which drives the document structure. From a client perspective, there are only the documents and it derives its own model from that.
Not sure what you mean here; are you saying that fh:archive is superfluous?
-- Mark Nottingham http://www.mnot.net/
