>However, it doesn't completely solve the scaling problem. If a
>document has many reviewers, it means that many more people have to
>read unpolished drafts of many more papers. That takes time.
No. The number of reviewers will depends on how many it can attract. The TPC mentor must assign a minimum number of "official" reviewers for the paper. The rest of the reviewers would be the ones that find the paper interesting. If a paper is perceived uninteresting, it will most likely have only "official" reviewers.
>Also,
>if many people have read many unfinished drafts, it is likely that one
>of them will get a related idea and want to pursue it. That will give
>problems with attribution and the perception of ideas being stolen.
But, the same can be said about papers that actually get presented in a conference. Afterall, the conference papers are considered unfinished products. Moreover, the objective of a conference is exchange of ideas. If some body decides to "steal" an idea, it is an ethics issue.
In fact, submission to a conference can give a paper (or an idea) a timestamp. This will be useful for people working at places where it is difficult to get the "technical report" status for a paper.
>A related concern with IETF-style iterative reviewing is that the
>reviewer may end up contributing more than some of the authors.
Why is that a problem? :)
> It is
>easy to imagine a conscientious reviewer going through many iterations
>with a student whose (co-author) advisor is preoccupied.
No. The TPC mentor can conclude the review process as soon as it is clear that a submitted paper is not acceptable.
Cheers
Mukul
On 13 August 2010 20:14, Catalin Meirosu <catalin.meirosu@ericsson.com> wrote:
>
> Hello,
>
> I agree that scaling would be an issue if using mailing lists. However, we are in 2010 and social networking is all the rage... So how about this (I know it looks complicated, but please bear with me for a moment):
>
> Perhaps IEEE could augment its site with the possibility to create private social networks (I think that there are several companies providing software or hosted services for such functionality). Each conference would instantiate such a new network every year. The members of the TPC will be added to this network (no more admin than adding them to a mailing list). Every author that submits a paper could by automatically invited to join the private network via a link sent by the paper submission system in the email confirming the submission. Every paper would also be added by the system as an entity to this social network, and the authors are automatically added as "friends" to the paper. Once assigned to the paper, the reviewers are also added as "friends". A search engine could help reviewers in identifying interesting submissions in case only one mentor is assigned by default for each paper. All the dialogue between the reviewers and the authors could take place on the "wall" of the paper in the private social network. In case people would like to have double blind reviews, this could be ensured by assigning IDs that are unique to this private social network (by making some alias that masks the IEEE login of the person). Of course, if more openness is desired it could be achieved by relaxing the constraints at the platform level.
>
> All of the basic technology for this exists. There is a non-negligible amount of integration and packaging work that would probably need resources at an IEEE level rather than just Comsoc. But maybe it would pay up... Smaller conferences might even consider trying this on their own by using a private social network provider and adding users and papers manually.
>
> my 2 cents
>
> -- Catalin
--
Lachlan Andrew Centre for Advanced Internet Architectures (CAIA)
Swinburne University of Technology, Melbourne, Australia
<http://caia.swin.edu.au/cv/landrew>
Ph +61 3 9214 4837
_______________________________________________
Tccc mailing list
Tccc@lists.cs.columbia.edu
https://lists.cs.columbia.edu/cucslists/listinfo/tccc
_______________________________________________
Tccc mailing list
Tccc@lists.cs.columbia.edu
https://lists.cs.columbia.edu/cucslists/listinfo/tccc
Posts
No comments:
Post a Comment