[uf-discuss] Microformat for linking to XML source (to replace the Structured Blogging plugin's embedding method)

Phillip Pearson pp at myelin.co.nz
Sun Jan 22 12:41:15 PST 2006

OK, that sounds like what I was planning.

I have no desire to define new MIME types.  Occasionally the SB plugins 
output something in a defined format - so far it's only XSPF, and that's 
kind of broken (hidden away in the "Other microcontent" menu for that 
reason), but there may be more in future.  In that case I'll make sure 
it's served with the proper MIME type and that the MIME type goes in the 
a/@type attribute.  Otherwise it'll be application/xml.


Mark Pilgrim wrote:

>If the "XML source" has a registered MIME type (like, say,
>"application/atom+xml", as defined in RFC 4287):
>* Ideally, you should serve the XML source page with the full
>registered MIME type.
>* If you want to do strange things with the XML source (like being
>able to view it in a browser, possibly styled with CSS and/or
>transformed with XSL), you are allowed to serve the XML source page
>with the general "application/xml" MIME type.
>* Either way, you should use the full registered MIME type in the
>@type attribute when you link to the XML source.  <a rel="alternate"
>type="application/atom+xml" href="..."> (substitute the MIME type
>you're actually using).
>If the "XML source" is just some random XML document in a format that
>you made up, or some format that doesn't have a registered MIME type
>(like RSS):
>* Serve the XML source page as "application/xml".  Do *NOT* just make
>up a MIME type, unless you know how to do it properly.
>* Link to it with <a rel="alternate" type="application/xml" href="...">.
>>Wasn't "text/xml" deprecated?!  And instead you are suppose to use
>>"application/xml" or "application/???+xml", etc.  (If I remember
>>correctly, this was done because of text-transcoders and conflicts
>>between "text types" specified with HTTP and XML.  I think I read this
>>on Mark Pilgrim's blog... but I couldn't find the article.)
>Don't use "text/xml".  Ever.  Here's why:
>microformats-discuss mailing list
>microformats-discuss at microformats.org

More information about the microformats-discuss mailing list