
Sign up to save your podcasts
Or


Keynote by Dr. Winnie Soon (Course Leader at the Creative Computing Institute, University of the Arts London, Associate Professor (on leave) at Aarhus University, visiting researcher at the Centre of the Study of the Networked Image (CSNI), London South Bank University)
The term "computational publishing" has emerged in recent scholarship and is used specifically to describe books as dynamic and computational objects that are open to re-versioning. Within this specific genre of computational publishing, this presentation focuses on characteristics and common approaches like free and open source software, community practices and programmable processes by discussing three examples. They are related to a Git repository, collaborative publishing software and a DIY book to explore the possible computational extensibility that is oriented more toward collective interventions, actions and practices. These examples examine a parallel between writing and coding that blurs the boundary between books and software, arguing that writing (publishing) a computational book is like writing (publishing) a piece of software.
By Keynote by Dr. Winnie Soon (Course Leader at the Creative Computing Institute, University of the Arts London, Associate Professor (on leave) at Aarhus University, visiting researcher at the Centre of the Study of the Networked Image (CSNI), London South Bank University)
The term "computational publishing" has emerged in recent scholarship and is used specifically to describe books as dynamic and computational objects that are open to re-versioning. Within this specific genre of computational publishing, this presentation focuses on characteristics and common approaches like free and open source software, community practices and programmable processes by discussing three examples. They are related to a Git repository, collaborative publishing software and a DIY book to explore the possible computational extensibility that is oriented more toward collective interventions, actions and practices. These examples examine a parallel between writing and coding that blurs the boundary between books and software, arguing that writing (publishing) a computational book is like writing (publishing) a piece of software.