Hi,

I will post volume and issue as soon as I know.
Since scientific articles are still printed on dead trees this might take a
while.

Greetings
Torben


2011/2/3 Lennard de Rijk <ljvder...@gmail.com>

> I have access to IEEE papers. If you can let me know when it is up I'm
> happy
> to give it a read.
>
> Greetings,
> Lennard
>
> On Wed, Feb 2, 2011 at 19:59, Torben Weis <torben.w...@gmail.com> wrote:
>
> > Hi guys,
> >
> > thanks for the quick response! I will use
> > http://incubator.apache.org/wave/.
> > This seems to be save.
> >
> > 2011/2/2 Dan Peterson <dpeter...@google.com>
> >
> > > I agree with Michael -- especially given the redirect that Andrus
> > > mentioned.
> > >
> > > Torben, hope you can share the paper once that is allowed!
> > >
> >
> > There are two ways of doing this:
> > a) wait for half a year after publication ... which is almost eternity in
> > computer science
> > b) on request I can show you the draft manuscript (i.e. my writing
> without
> > the editor's changes). However, I can just not post it on a public
> archived
> > mailing list yet.
> > c) read it online soon if you have access to IEEE
> >
> > The paper is titled "Federating Web Sites with the Google Wave Protocol"
> > and
> > shows two things
> > a) an introduction into wave federation technology and terminology
> > including
> > data model, OT and security and a short explanation about WiaB and Wave's
> > Open Source Life.
> > b) a walkthrough example of how to build a decentralized social network
> > based on wave federation technology to illustrate that the protocol can
> do
> > much more than just powering an application like GWave.
> >
> > If you are interested in this, let me know.
> >
> > Greetings
> > Torben
> >
> >
> > > -Dan
> > >
> > > On Wed, Feb 2, 2011 at 7:52 AM, Michael MacFadden <
> > > michael.macfad...@gmail.com> wrote:
> > >
> > > > Torben,
> > > >
> > > > A couple thoughts.
> > > >
> > > > 1)
> > > >
> > > > Obviously waveprotocol.org is the only live site now.  So you could
> do
> > > > that.  That site will likely stay around for quite some time.  I will
> > > > hopefully not be the home of WiaB but rather just the protocol.  If
> the
> > > > artice is about federation in general, this is probably your best
> bet.
> > > >
> > > > 2)
> > > >
> > > > If the link is specifically about WiaB then you could use the URL for
> > the
> > > > incubator project which is:
> > > >
> > > > http://incubator.apache.org/wave/
> > > >
> > > > This site is at least not returning an error right now, but redirects
> > > > people to waveprotocol.org.  Maybe by the time your aricle gets
> > > published
> > > > it will be up.  Either way this will likely be the "real" home of
> WiaB
> > > for a
> > > > while.  My only concern is that after we graduate from the incubator,
> I
> > > > would think our site would be moved to.
> > > >
> > > > http://wave.apache.org
> > > >
> > > > or something like that.
> > > >
> > > >
> > > > ~Michael
> > > >
> > > >
> > > > On Feb 2, 2011, at 5:30 AM, Torben Weis wrote:
> > > >
> > > > > Hi,
> > > > >
> > > > > I am about to publish a paper on Wave Federation in IEEE Internet.
> > > > > In this article I am referring to the WiaB project.
> > > > > In the original manuscript I pointed to waveprotocol.org.
> > > > > Now we moved to Apache.
> > > > > This rises the question: What is the official WiaB web site now and
> > in
> > > > the
> > > > > future?
> > > > > Unfortunately I cannot wait because I have to submit the final
> > version
> > > of
> > > > > the manuscript tomorrow
> > > > > and whatever link I choose should be already alive now.
> > > > >
> > > > > Any suggestions?
> > > > >
> > > > > Torben
> > > > >
> > > > > --
> > > > > ---------------------------
> > > > > Prof. Torben Weis
> > > > > Universitaet Duisburg-Essen
> > > > > torben.w...@gmail.com
> > > >
> > > >
> > >
> >
> >
> >
> > --
> > ---------------------------
> > Prof. Torben Weis
> > Universitaet Duisburg-Essen
> > torben.w...@gmail.com
> >
>



-- 
---------------------------
Prof. Torben Weis
Universitaet Duisburg-Essen
torben.w...@gmail.com

Reply via email to