Luke Arno wrote:
No. The atom spec says that it can have 2 meanings.
I think it should *only* mean published but that is
orthogonal. The spec says it *can* mean published.
I suggest that when the APP looks at it, it does mean
published. I don't understand why the atom spec leaves
us this choice, but it does.
I think it's for allowing the following use case: I'm writing an
“article” about an event (“I'm currently attending at the XXX
conference…”) but make it available a bit later (no wifi…). Is
atom:published allowed to denote the time I started writing (so that
looking at the entry's metadata tells you when “currently” actually is)
or must it be the time it becomes available? I'd say the former (initial
creation vs. first availability).
However, I don't think “published” is abused here: I meant to publish
the entry during the conference but wasn't able to do it, so published ≠
first available (conceptual vs. technical meaning).
I can however imagine another use case: when the entry is not the
resource but a representation of a resource (obvious use case: using
[EMAIL PROTECTED]), then is atom:published relative to the entry or the
resource it describes/represents?
If I'm preparing the entry about a book before the book is actually
published, I must be able to mark it as “draft” (or not published, or
not publicly available, …). However, I could still set atom:published to
the date/time when I want the entry to become public (e.g. the date the
book will be published) and the AtomPP server will keep the entry
“private” 'til that date.
In other words, I was +1 to using atom:published but am now +0…
--
Thomas Broyer
