Pascal Philippe wrote:
For example, in a web blog entry, I can have more than one components.
A web blog entry can be, as example, a picture (encoded in base64)
with a text. How can I represent this using the Atom syntax?
If you want the image to appear inline, you can include it as an HTML
On 12/10/05 7:54 PM, Pascal Philippe [EMAIL PROTECTED] wrote:
I would like to try to understand why we can't have more than one
atom:content element within an atom:entry element. Could you give me
the reason of this choice?
IIRC, it was thought it would be too burdensome for developers to
* James Holderness [EMAIL PROTECTED] [2005-10-13 09:40]:
If you want the image to appear inline, you can include it as
an HTML (or XHTML) img tag within the atom:content element.
Alternatively, if it would be better represented as an
attachment you can include it as an enclosure (an atom:link
A. Pagaltzis wrote:
And deviously, you can inline the image data inside the feed too,
by using a data: URI with one of these methods.
However, shipping blobs around inside a feed is not a bright idea
with the currently common feed use cases.
There's also the problem that Internet Explorer
James Holderness wrote:
A. Pagaltzis wrote:
And deviously, you can inline the image data inside the feed too,
by using a data: URI with one of these methods.
However, shipping blobs around inside a feed is not a bright idea
with the currently common feed use cases.
There's also the
* John Panzer [EMAIL PROTECTED] [2005-10-13 18:45]:
If I recall, I believe this is because some people wanted to be
able to package multiple pieces of content together in a single
entry, and other people did not want to have to imply a
requirement for MIME multipart parsing as pat of the Atom
A. Pagaltzis wrote:
* John Panzer [EMAIL PROTECTED] [2005-10-13 18:45]:
If I recall, I believe this is because some people wanted to be
able to package multiple pieces of content together in a single
entry, and other people did not want to have to imply a
requirement for MIME
* John Panzer [EMAIL PROTECTED] [2005-10-13 19:40]:
Well, you can pass them around by reference with [EMAIL PROTECTED]
I think.
By the letter of the spec, but not by the spirit.
But that’s beside the point, since if you’re going to point to an
external resource, you can and should use an
On Oct 13, 2005, at 12:06 PM, A. Pagaltzis wrote:
* John Panzer [EMAIL PROTECTED] [2005-10-13 19:40]:
Well, you can pass them around by reference with [EMAIL PROTECTED]
I think.
By the letter of the spec, but not by the spirit.
I just ran through the discussion of this very question on the
John Panzer wrote:
If I recall, I believe this is because some people wanted to be
able to package multiple pieces of content together in a single
entry, and other people did not want to have to imply a
requirement for MIME multipart parsing as pat of the Atom
format specification.
Ugh.
Hello,
I would like to try to understand why we can't have more than one
atom:content element within an atom:entry element. Could you give me
the reason of this choice?
For example, in a web blog entry, I can have more than one components.
A web blog entry can be, as example, a picture
11 matches
Mail list logo
