Hi folks,
Quick question regarding the atom:author element in a member resource.
Say I POST an atom:entry to a collection URI, this entry does not have
an atom:author (which could be considered as not valid but that's not
the question here), now say that my app server does not have any
Section 4.2.1 of RFC 4287:
If an atom:entry element does not contain atom:author elements, then
the atom:author elements of the contained atom:source element are
considered to apply. In an Atom Feed Document, the atom:author
elements of the containing atom:feed element are
There is an unexpected reply located in
http://www.imc.org/atom-protocol/mail-archive/msg07722.html.
Quote:
atom:content type=image/svg+xml.../atom:content
I don't know how to display such a content within a widget, however
I know there is some program in the registry (Windows Registry,
2006/11/22, Tse Shing Chi (Franklin/Whale):
There is an unexpected reply located in
http://www.imc.org/atom-protocol/mail-archive/msg07722.html.
Oops, sorry!
(double-checked, this time, I answer to atom-syntax ;-) )
Quote:
atom:content type=image/svg+xml.../atom:content
I don't know how
* Sylvain Hellegouarch [EMAIL PROTECTED] [2006-11-22 12:25]:
do you think it'd be better to put an empty atom:name or to put
a dummy value such as 'anonymous' or 'n/a'?
Ugh. Dummy values are nasty, perverse and evil. Someone *will*
eventually suffer miserably if you pollute your data like
On Nov 22, 2006, at 3:11 AM, Sylvain Hellegouarch wrote:
Say I POST an atom:entry to a collection URI, this entry does not have
an atom:author
If I were implementing the server, in this scenario I'd reject the
post with an error message. It's hard for me to see a scenario where
the
Tim Bray wrote:
On Nov 22, 2006, at 3:11 AM, Sylvain Hellegouarch wrote:
Say I POST an atom:entry to a collection URI, this entry does not have
an atom:author
If I were implementing the server, in this scenario I'd reject the post
with an error message. It's hard for me to see a
Sylvain Hellegouarch wrote:
Tim Bray wrote:
On Nov 22, 2006, at 3:11 AM, Sylvain Hellegouarch wrote:
Say I POST an atom:entry to a collection URI, this entry does not have
an atom:author
If I were implementing the server, in this scenario I'd reject the post
with an error
I agree. It would be useful to work on placing a little bit more
weight on the rel relation rather than putting everything on the mime
type. After all if every link is going to be an alternate relation,
then what was the point of the rel=... attribute? We might as well
have stuck with
James M Snell wrote:
IOW, using the XHTML2 div as the child is compliant in a strictly sense
but should be avoided because it will likely cause problems.
An XHTML2 div is not compliant. The normative reference is to XHTML
Modularization, and the accompanying XHTML1 definitions and
10 matches
Mail list logo
