(Eric, I'm skipping past design discussions here)
Eric Scheid wrote:
> questions from a naïve implementer perspective:
>
>
>>8.1.1 Title: Header
>
>
> can the Title header include non-ASCII characters?
Octet based. You could get UTF-8 through it, but it would need to be
specced to be decoded as such.
>>11. Example
>
>
> ah, I see here an example of POSTing an image ... and while there is a
> [EMAIL PROTECTED]'edit'] for the image, how does one edit that atom:entry
> itself
> (eg. to update any metadata)?
>
> Is this section, being an example, normative?
I would say no, but it should be correct/clear, or what's the point?
> Is the HTTP 201 response body (ie. the atom:entry for that member resource)
> a normative requirement, or could a server simply spit back 201 Created and
> no atom:entry?
It's unspecified.
> I note that the blog posting atom:entry subsequently posted includes
> <updated>2005-09-02T10:30:00Z</updated>, but section 8.2.1 says atom:updated
> is server controlled ... perhaps section 8.2.1 needs to point out that this
> non-editing restriction applies to changing via PUT, not creation via POST?
I'm working up a pace/thread on atom entries (invalidity. element
constraints etc). There is too much unsaid on this.
>>9. Collections
>>... a pair of positive integer indices separated by a dash character ...
>>The index values are 0 based ...
>
>
> just a nitpick ... zero is not a positive integer :-P
ROTFL. Fixed for 07. [Unless we want it 1 based - it's not 1970 anymore,
and I think the 'puters can take it]
cheers
Bill
