the ACM on Human-Computer Interaction</a>,
Volume 2, Issue CSCW,
Article No. <a href="https://dl.acm.org/citation.cfm?id=3274310">41</a>.
- ACM, November 2018.
+ ISSN 2573-0142, ACM,
+ November 2018.
</em>
[[!toggle id=id71 text="Abstract..."]] [[!toggleable id=id71 text="""
*Abstract:* Real-Time Collaborative Editing (RTCE) is a popular way of instrumenting cooperative work on documents, in particular on the Web. Little is known in the literature yet about RTCE usage patterns in the real world. In this paper we study how a popular RTCE editor (Etherpad) is used in the wild, digging into the edit histories of a large collection of documents (about 14 000 pads), retrieved from one of the most popular public instances of the platform, hosted by the Wikimedia Foundation. The pad analysis is supported by a novel conceptual model that allows to label edit operations as "collaborative" or not depending on their distance---in edit position (space), edit time, or spacetime (both)---from edits made by other authors. The model is applied to classify all edits from the pad corpus. Classification results are further used to characterize the collaboration behavior of pad authors. Findings show that: 1) about half of the pads have a single author and hence witnessed no collaboration; 2) collaboration on common document parts happens often, but it happens asynchronously with authors taking turns in editing; and 3) simultaneous editing of common document parts happens very rarely. These findings help in revisiting early RTCE design decisions (e.g., the granularity of conflict management in RTCE protocols) and give insights on how to address novel needs (e.g., end-to-end encryption and offline editing).
1. <a class="paper-download" href="ahci2012-wiki.pdf" title="download paper in PDF format">[.pdf]</a> <a class="bibtex-download" href="ahci2012-wiki.bib" title="download bibliographic entry in BibTeX format">[.bib]</a> <span class="doi_logo"><a href="http://dx.doi.org/10.1155/2012/893575" title="Document Object Identifier">doi></a></span> <a href="http://diiorio.web.cs.unibo.it/">Angelo Di Iorio</a>, Francesco Draicchio, <a href="http://vitali.web.cs.unibo.it">Fabio Vitali</a>, <a href="http://upsilon.cc/~zack">Stefano Zacchiroli</a>. **Constrained Wiki: The WikiWay to Validating Content**. <em>In <a href="http://www.hindawi.com/journals/ahci/">Advances in Human-Computer
Interaction</a>, Volume 2012, Article ID
893575, <a href="http://www.hindawi.com/journals/ahci/2012/893575/">pp. 1-19</a>.
- Hindawi, 2012</em>
+ ISSN 1687-5893, Hindawi, 2012</em>
[[!toggle id=id39 text="Abstract..."]] [[!toggleable id=id39 text="""
*Abstract:* The "WikiWay" is the open editing philosophy of wikis meant to foster open collaboration and continuous improvement of their content. Just like other online communities, wikis often introduce and enforce conventions, constraints, and rules for their content, but do so in a considerably softer way, expecting authors to deliver content that satisfies the conventions and the constraints, or, failing that, having volunteers of the community, the WikiGnomes, fix others' content accordingly. Constrained wikis is our generic framework for wikis to implement validators of community-specific constraints and conventions that preserve the WikiWay and their open collaboration features. To this end, specific requirements need to be observed by validators and a specific software architecture can be used for their implementation, that is, as independent functions (implemented as internal modules or external services) used in a nonintrusive way. Two separate proof-of-concept validators have been implemented for MediaWiki and MoinMoin, respectively, providing an annotated view functions, that is, presenting content authors with violation warnings, rather than preventing them from saving a noncompliant text.
"""]]
# book chapters
- 1. <a class="paper-download" href="web30-semantics-templating.pdf" title="download paper in PDF format">[.pdf]</a> <a class="bibtex-download" href="web30-semantics-templating.bib" title="download bibliographic entry in BibTeX format">[.bib]</a> <a href="http://diiorio.web.cs.unibo.it/">Angelo Di Iorio</a>, <a href="http://vitali.web.cs.unibo.it">Fabio Vitali</a>, <a href="http://upsilon.cc/~zack">Stefano Zacchiroli</a>. **Web Semantics via Wiki Templating**. <em>
+ 1. <a class="paper-download" href="web30-semantics-templating.pdf" title="download paper in PDF format">[.pdf]</a> <a class="bibtex-download" href="web30-semantics-templating.bib" title="download bibliographic entry in BibTeX format">[.bib]</a> <span class="doi_logo"><a href="http://dx.doi.org/10.4018/978-1-60566-384-5.ch019" title="Document Object Identifier">doi></a></span> <a href="http://diiorio.web.cs.unibo.it/">Angelo Di Iorio</a>, <a href="http://vitali.web.cs.unibo.it">Fabio Vitali</a>, <a href="http://upsilon.cc/~zack">Stefano Zacchiroli</a>. **Wiki Semantics via Wiki Templating**. <em>
Chapter 34 of <a href="http://www.amazon.com/Handbook-Research-Web-2-0-3-0/dp/1605663840">Handbook
of research on Web 2.0, 3.0 and x.0: technologies, business and social
applications</a>. San Murugesan Ed.,
- Information Science Reference,
- November 2009, ISBN
- 978-1605663845.
+ <a href="https://www.igi-global.com/gateway/chapter/39179">pp. 329-348</a>,
+ IGI Global, 2010,
+ ISBN 978-1605663845.
</em>
[[!toggle id=id21 text="Abstract..."]] [[!toggleable id=id21 text="""
*Abstract:* A foreseeable incarnation of Web 3.0 could inherit machine understandability from the Semantic Web, and collaborative editing from Web 2.0 applications. We review the research and development trends which are getting today Web nearer to such an incarnation. We present semantic wikis, microformats, and the so-called "lowercase semantic web": they are the main approaches at closing the technological gap between content authors and Semantic Web technologies. We discuss a too often neglected aspect of the associated technologies, namely how much they adhere to the wiki philosophy of open editing: is there an intrinsic incompatibility between semantic rich content and unconstrained editing? We argue that the answer to this question can be "no", provided that a few yet relevant shortcomings of current Web technologies will be fixed soon.
1. <a class="paper-download" href="ipres-2018-doi.pdf" title="download paper in PDF format">[.pdf]</a> <a class="bibtex-download" href="ipres-2018-doi.bib" title="download bibliographic entry in BibTeX format">[.bib]</a> <span class="doi_logo"><a href="http://dx.doi.org/10.17605/OSF.IO/KDE56" title="Document Object Identifier">doi></a></span> <a href="http://www.dicosmo.org">Roberto Di Cosmo</a>, <a href="https://moranegg.github.io/">Morane Gruenpeter</a>, <a href="http://upsilon.cc/~zack">Stefano Zacchiroli</a>. **Identifiers for Digital Objects: the Case of Software Source Code Preservation**. <em>
In proceedings of <a href="https://ipres2018.org/">iPRES 2018</a>: 15th International
Conference on Digital Preservation, Boston, MA, USA,
- September 2018, 9 pages.
+ 24-27 September 2018, 9 pages.
</em>
[[!toggle id=id70 text="Abstract..."]] [[!toggleable id=id70 text="""
*Abstract:* In the very broad scope addressed by digital preservation initiatives, a special place belongs to the scientific and technical artifacts that we need to properly archive to enable scientific reproducibility. For these artifacts we need identifiers that are not only unique and persistent, but also support integrity in an intrinsic way. They must provide strong guarantees that the object denoted by a given identifier will always be the same, without relying on third parties and external administrative processes. In this article, we report on our quest for this identifiers for digital objects (IDOs), whose properties are different from, and complementary to, those of the various digital identifiers of objects (DIOs) that are in widespread use today. We argue that both kinds of identifiers are needed and present the framework for intrinsic persistent identifiers that we have adopted in Software Heritage for preserving billions of software artifacts.
1. <a class="paper-download" href="ipres-2017-software-heritage.pdf" title="download paper in PDF format">[.pdf]</a> <a class="bibtex-download" href="ipres-2017-software-heritage.bib" title="download bibliographic entry in BibTeX format">[.bib]</a> <a href="http://www.dicosmo.org">Roberto Di Cosmo</a>, <a href="http://upsilon.cc/~zack">Stefano Zacchiroli</a>. **Software Heritage: Why and How to Preserve Software Source Code**. <em>
In Proceedings of <a href="https://ipres2017.jp/">iPRES
2017</a>: 14th International Conference on Digital
- Preservation, Kyoto, Japan, September 2017, 10
+ Preservation, Kyoto, Japan, 25-29 September 2017, 10
pages.
</em>
[[!toggle id=id65 text="Abstract..."]] [[!toggleable id=id65 text="""
2012</a>: <a href="http://2012.msrconf.org/">9th IEEE Working Conference
on Mining Software Repositories</a>, co-located with <a href="http://www.icse2012.org/">ICSE 2012</a>,
IEEE, ISBN 978-1-4673-1760-3, <a href="http://ieeexplore.ieee.org/xpl/articleDetails.jsp?arnumber=6224274">pp. 141-150</a>.
- June 2-3, Zurich, Switzerland.</em>
+ 2-3 June 2012, Zurich, Switzerland.</em>
[[!toggle id=id44 text="Abstract..."]] [[!toggleable id=id44 text="""
*Abstract:* Determining whether two or more packages cannot be installed together is an important issue in the quality assurance process of package-based distributions. Unfortunately, the sheer number of different configurations to test makes this task particularly challenging, and hundreds of such incompatibilities go undetected by the normal testing and distribution process until they are later reported by a user as bugs that we call "conflict defects". We performed an extensive case study of conflict defects extracted from the bug tracking systems of Debian and Red Hat. According to our results, conflict defects can be grouped into five main categories. We show that with more detailed package meta-data, about 30% of all conflict defects could be prevented relatively easily, while another 30% could be found by targeted testing of packages that share common resources or characteristics. These results allow us to make precise suggestions on how to prevent and detect conflict defects in the future.
"""]]
1. <a class="paper-download" href="sefm2012-aeolus.pdf" title="download paper in PDF format">[.pdf]</a> <a class="bibtex-download" href="sefm2012-aeolus.bib" title="download bibliographic entry in BibTeX format">[.bib]</a> <span class="doi_logo"><a href="http://dx.doi.org/10.1007/978-3-642-33826-7_11" title="Document Object Identifier">doi></a></span> <a href="http://www.dicosmo.org">Roberto Di Cosmo</a>, <a href="http://upsilon.cc/~zack">Stefano Zacchiroli</a>, <a href="http://www.cs.unibo.it/~zavattar/">Gianluigi Zavattaro</a>. **Towards a Formal Component Model for the Cloud**. <em>In proceedings of SEFM 2012: <a href="http://sefm2012.city.academic.gr/">10th International Conference on
Software Engineering and Formal Methods</a>, Thessaloniki,
Greece, 1-5 October, 2012. LNCS 7504,
+ ISBN 978-3-642-33825-0,
pp. 156-171, Springer-Verlag,
2012.</em>
[[!toggle id=id43 text="Abstract..."]] [[!toggleable id=id43 text="""
Conference on Mining Software Repositories</a>, co-located
with <a href="http://www.sbs.co.za/ICSE2010/">ICSE 2010</a>,
IEEE, ISBN 978-1-4244-6802-7, <a href="http://ieeexplore.ieee.org/search/srchabstract.jsp?tp=&arnumber=5463277">pp. 52-61</a>.
- 02-03/05/2010, Cape Town, South Africa.</em>
+ 2-3 May 2010, Cape Town, South Africa.</em>
[[!toggle id=id33 text="Abstract..."]] [[!toggleable id=id33 text="""
*Abstract:* FLOSS distributions like RedHat and Ubuntu require a lot more complex infrastructures than most other FLOSS projects. In the case of community-driven distributions like Debian, the development of such an infrastructure is often not very organized, leading to new data sources being added in an impromptu manner while hackers set up new services that gain acceptance in the community. Mixing and matching data is then harder than should be, albeit being badly needed for Quality Assurance and data mining. Massive refactoring and integration is not a viable solution either, due to the constraints imposed by the bazaar development model. This paper presents the Ultimate Debian Database (UDD), which is the countermeasure adopted by the Debian project to the above "data hell". UDD gathers data from various data sources into a single, central SQL database, turning Quality Assurance needs that could not be easily implemented before into simple SQL queries. The paper also discusses the customs that have contributed to the data hell, the lessons learnt while designing UDD, and its applications and potentialities for data mining on FLOSS distributions.
"""]]
1. <a class="paper-download" href="sac10-coclo.pdf" title="download paper in PDF format">[.pdf]</a> <a class="bibtex-download" href="sac10-coclo.bib" title="download bibliographic entry in BibTeX format">[.bib]</a> <span class="doi_logo"><a href="http://doi.acm.org/10.1145/1774088.1774259" title="Document Object Identifier">doi></a></span> <a href="http://www.cs.unibo.it/~gdangelo/">Gabriele D'Angelo</a>, <a href="http://vitali.web.cs.unibo.it">Fabio Vitali</a>, <a href="http://upsilon.cc/~zack">Stefano Zacchiroli</a>. **Content Cloaking: Preserving Privacy with Google Docs and other Web Applications**. <em>In proceedings of ACM SAC 2010: <a href="http://www.acm.org/conferences/sac/sac2010/">25th Annual ACM
Symposium on Applied Computing</a>, ISBN
978-1-60558-639-7, <a href="http://portal.acm.org/citation.cfm?doid=1774088.1774259">pp. 826-830</a>.
- 22-26/03/2010 - Sierre, Switzerland.</em>
+ 22-26 March 2010, Sierre, Switzerland.</em>
[[!toggle id=id31 text="Abstract..."]] [[!toggleable id=id31 text="""
*Abstract:* Web office suites such as Google Docs offer unparalleled collaboration experiences in terms of low software requirements, ease of use, data ubiquity, and availability. When the data holder (Google, Microsoft, etc.) is not perceived as trusted though, those benefits are considered at stake with important privacy requirements. Content cloaking is a lightweight, cryptographic, client-side solution to protect content from data holders while using web office suites and other "Web 2.0", AJAX-based, collaborative applications.
"""]]
2009</a>: 4th international conference on Evaluation of Novel Aspects to
Software Engineering; held in conjunction with <a href="http://www.iceis.org/">ICEIS 2009</a>. 6-10 May 2009, Milan, Italy.
<a href="http://www.springerlink.com/content/978-3-642-14818-7/contents/">CCIS
- Volume 69</a>, <a href="http://www.springerlink.com/content/g73241150p518215/">pp.
+ Volume 69</a>, ISBN 978-3-642-14818-7,
+ <a href="http://www.springerlink.com/content/g73241150p518215/">pp.
262-276</a>, Springer-Verlag,
2010.</em>
[[!toggle id=id26 text="Abstract..."]] [[!toggleable id=id26 text="""
In Proceedings of <a href="http://www.wikisym.org/ws2006/">WikiSym 2006</a>: the 2006
International Symposium on Wikis. Odense, Denmark -- August
21-23, 2006. ACM, 2006, ISBN
- 1-59593-41
7-0, <a href="http://www.wikisym.org/ws2006/proceedings/p89.pdf">pp.
+ 1-59593-41
3-8, <a href="http://www.wikisym.org/ws2006/proceedings/p89.pdf">pp.
89-98</a>.
</em>
[[!toggle id=id7 text="Abstract..."]] [[!toggleable id=id7 text="""
1. <a class="paper-download" href="studia11-dh-ocaml.pdf" title="download paper in PDF format">[.pdf]</a> <a class="bibtex-download" href="studia11-dh-ocaml.bib" title="download bibliographic entry in BibTeX format">[.bib]</a> <a href="http://www.pps.univ-paris-diderot.fr/~dogguy/">Mehdi Dogguy</a>, <a href="http://stephane.glondu.net/">Stéphane Glondu</a>, <a href="http://sylvain.le-gall.net/">Sylvain Le Gall</a>, <a href="http://upsilon.cc/~zack">Stefano Zacchiroli</a>. **Enforcing Type-Safe Linking using Inter-Package Relationships**. <em>In <a href="http://studia.complexica.net/">Studia
Informatica Universalis</a>, Volume 9, Issue
- 1, pp. 129-157. Hermann
- 2011.</em>
+ 1, pp. 129-157.
+ ISSN 1625-7545, Hermann 2011.</em>
[[!toggle id=id37 text="Abstract..."]] [[!toggleable id=id37 text="""
*Abstract:* Strongly-typed languages rely on link-time checks to ensure that type safety is not violated at the borders of compilation units. Such checks entail very fine-grained dependencies among compilation units, which are at odds with the implicit assumption of backward compatibility that is relied upon by common library packaging techniques adopted by FOSS (Free and Open Source Software) package-based distributions. As a consequence, package managers are often unable to prevent users to install a set of libraries which cannot be linked together. We discuss how to guarantee link-time compatibility using inter-package relationships; in doing so, we take into account real-life maintainability problems such as support for automatic package rebuild and manageability of ABI (Application Binary Interface) strings by humans. We present the dh_ocaml implementation of the proposed solution, which is currently in use in the Debian distribution to safely deploy more than 300 OCaml-related packages.
"""]]
projects / homepage.git / commitdiff