Cristobal.arellano

This is the user page of Cristobal Arellano. Cristobal Arellano works as a Research Assistant at the University of the Basque Country. His research interests are in Model-Driven Engineering, End-User Development, Collaborative Software Development and Augmented Browsing. Arellano has a PhD in computer science from the University of the Basque Country.

Projects

Cristobal Arellano has participated in many research projects. The most important are enumerated below (ordered by date).

Related with wikis

• WikiLayer. Reading Wikipedia is the entry to more involved activities such as editing. However, the jump from reading to editing could be too big for some wikipedians who can be intimidated by exposing their content to public scrutiny. Annotating might foster not only reading but also be the prelude to editing. Different annotation tools exist for the Web (e.g., Diigo, A.nnotate). Being a Web application, Wikipedia can benefit from these tools. However, general-purpose annotation tools do not make annotation a natural gesture within Wikipedia. That is, annotation editing, rendering or retrieval in e.g. Diigo is dissociated from the edition, rendering or location of articles in Wikipedia, hindering the role of annotation as the prelude to article edition. WikiLayer is a Wikipedia-specific annotation tool.

• Wiki Refactoring. Wikis' organic growth inevitably leads to a gradual degradation of the wiki content/structure which, in turn, may entail recurrent wiki refactoring. Unfortunately, no regression test exists to check the validity of the refactoring output. Some changes, even if compliant with good practices, can still require to be backed by the community which ends up bearing the maintenance burden. This calls for a semiautomatic approach where "refactoring bots" interact with wiki users to confirm the upgrades.

Other projects

• Sticklet. Web Augmentation is to the Web what augmented reality is to the physical world: layering relevant content/layout/navigation over the existing Web to customize the user experience. However, Web Augmentation is hindered by being programming intensive and prone to malware. This prevents end-users from participating as both producers and consumers of scripts: producers need to know JS, consumers need to trust JS. This work aims at promoting end-user participation in both roles. The vision is for end-users to prosume (the act of simultaneously caring for producing and consuming) scripts as easily as they currently prosume their pictures or videos.
• Lightweight End-User Software Sharing. This work looks into the sharing of end-user software (referred to as “script”). Based on this study four implications are drawn: reduce the effort to make scripts shareable, minimize deployment burdens, less stringent protection mechanisms, and tap into communities of practice as for sharing.
• Open personalization. Open innovation and collaborative development are attracting considerable attention as new software construction models. Traditionally, website code is a “wall garden” hidden from partners. In the other extreme, you can move to open source where the entirety of the code is disclosed. A middle way is to expose just those parts where collaboration might report the highest benefits. Personalization can be one of those parts. Partners might be better positioned to foresee new ways to adapt/extend your website based on their own resources and knowledge of their customer base. We coin the term “Open Personalization” to refer to those practises and architectures that permit partners to inject their own personalization rules.