bookmarks and Weave Re: timeless' review and my responses so far

> From: Thomas Roessler <tlr@w3.org>
> 
> On 26 Mar 2010, at 21:40, Mary Ellen Zurko wrote:
> 
> > > This is annoying. If I use http://delicious.com/or Google to save my
> > > bookmarks as a set, why shouldn't I allow them to provide a way to 
add
> > > pages I'm not currently at? Obviously I'd have to design it so that
> > > the user can review the content in some safe manner, but....
> > > 
> > > A competitor (Firefox for Mobile) offers an API, "Weave", which 
allows
> > > a web server (weave) to add URIs to the user's bookmark collection. 
We
> > > have already received customer requests demanding this feature. In
> > > reality, Weave doesn't quite act as web content, however, I don't
> > > think users care about the distinction.
> > 
> > I believe Tyler had provided the attack pointer for this one. 
> Anyone have it handy? 
> 
> Why would Weave even be subject to this spec?  It's (for our 
> purposes) an implementation detail of the browser.  Not our business
> whether it uses HTTP or something else.
> 
> 

Weave is a web server but it's also an implementation detail of a browser? 
Sorry, I'm not following.