On 10/26/05, David Powell <[EMAIL PROTECTED]> wrote: > > Quoting Robert Sayre <[EMAIL PROTECTED]>: > > > XOXO is done, flexible, and therefore 100x better than writing our > > own. There's an example in the spec already, which is all most > > implementors will ever look at. James is proof of that. > > How does a standalone Atom publishing client get hold of the service outline > document? > > Does the user copy this into their publishing client from a webpage or email? > Or does a browser-component (or some javascript?) scan every html page to > identify whether the page contains Atom XOXO, to decide whether to enable its > publishing features or trigger an external client? > > > Using a custom XML document with an application/x-atom-introspection+xml MIME > type might provide a better user-experience. The user could click on a link > and have the document dispatched to the publishing client by their browser. >
The XHTML based introspection document could be served with application/x-atom-introspection+xml. It *is* an XML format. - Luke
