[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: I-D ACTION:draft-ietf-atompub-protocol-14.txt


On 3/18/07, Robert Yates <robyates70@xxxxxxxxx> wrote:

The blogging component expects posted atom entries to contain a
"content" element containing the blog post. The bookmarking component,
however, expects the "url to be bookmarked" to be contained in the
alternate "link" element within atom entries submitted to it.


That seems rather fragile, is there any reason
not to have the server implementation look for the
first link in the content if no alternate link
is present? Any reason to not make the
first link in the content, or a microformat,
the primary way of adding a bookmark?


In short, they both expect completely different types of atom entries and
will reject entries that don't conform to their particular
application.

These are both completely valid AtomPP "applications", however at the
interop event I suspect that no atom client will be able to work with
our bookmarking component.


The same holds true for the current implementations
of the APP that rely heavily on foreign markup.

  Thanks,
  -joe

--
Joe Gregorio        http://bitworking.org