Quoting Robert Sayre <[EMAIL PROTECTED]>: > On 11/8/05, David Powell <[EMAIL PROTECTED]> wrote: > > +0 - APPO is a custom format, but not custom for Atom; > > What in the world? It's called APP Outline Format. > > > it is a generic > > outlining format with no dependencies on Atom. > > Um, it's obviously inadequate for an outliner (text editor) > application. If I wanted a format for that, I would use OPML or a > custom format with even more features (like every other outliner app). > I guess I'll rename that 'text' attribute so people don't get the > wrong idea.
I don't know what the scope of APPO is intended to be, you tell me. The fact that it doesn't include the word Atom anywhere in the text, and the generic sounding MIME type made me think that it is intended to have a broader use - if it is then that's great, but... > I've never need to dispatch on MIME type for this, and if I did, the > proposed type would be just fine. ...if APPO is intended to have broader use than just Atom introspection documents, then dispatching all application/outline+xml files to an Atom Protocol client wouldn't work because it would act as a handler for other APPO files that aren't Atom introspection documents. "The abstract is too short." > Loading by MIME type doesn't give you the URI of the file Hmmm, true. > which is what you actually want. Disagree. The only reason that you would need the URI of the introspection document is to resolve relative IRI references, which aren't a problem for the draft-protocol-06 format because it uses IRIs rather than IRI references. The introspection document effectively acts as the doorway to well-behaved Atom Protocol from the normal Web. draft-protocol-06 works when the introspection document is sent by email, behind cookie auth, or whatever - things which are quite common. To dispatch an APPO introspection document would require that the document have a URI and pass this URI to the client application - this generally doesn't happen which is why we invented rel="self" for Atom. The draft-protocol-06 approach will be more robust at dispatching. > If there's a > link=rel "introspection" somewhere, that's all that's needed. Theoretically or practically? What would the user-experience be like? If you have some way of parsing every browser page looking for rel=introspection links and launching a publishing client, that's cool, but I imagine that this would be impractical for most browsers. -- Dave
