Re: Atom entry as media-resource
Henry Story
in my AtomOwl transforms.
I wonder how I should do this right.
Henry
On 16 Mar 2007, at 12:16, Thomas Broyer wrote:
>
> 2007/3/16, Sylvain Hellegouarch:
>> Thomas Broyer wrote:
>> >
>> > The difference is that atom:content with type="html|xhtml|text"
>> cannot
>> > be externalized, so you cannot have a "media resource" to represent
>> > it.
>>
>> Does this hold true if you sue the actual media-type for each case?
>> text/html, application/xhtml+xml and text/plain?
>
> If we have type="html|xhtml|text" in the syndication format, that's
> precisely because there is no "actual media-type for each case".
>
> * type="html" is not type="text/html", because type="text/html"
> requires a "full HTML document" (with at least a <title> tag, given
> that <html>, <head> and <body> are optional)
>
> * type="xhtml" is not type="application/xhtml+xml" for the same
> reasons (except that there is no such thing as "optional tags" in
> XML). Eventually, type="application/xml-external-parsed-entity could
> be used, but you then don't know it's an "XHTML fragment"
>
> * type="text" is not type="text/plain", because white-space may be
> collapsed in type="text" while collapsing white-space in text/plain
> might change the meaning of the content and/or make it unreadable
> (think about ASCII-art and "tables", as used in RFCs). type="text" is
> actually very similar to type="xhtml" without the need for the
> <xhtml:div/> wrapper (except that you're allowed to collapse
> white-space within the content –i.e. change the value–, not only when
> displaying it).
>
>> I could be wrong but I don't think Atom mandates you to inline those
>> media-types content, does it?
>
> You're right, it doesn't.
>
> --
> Thomas Broyer