A Latex template for the preparation of IAU Symposia Proceedings downloaded from
The package contains: Class File (iau.cls), Instructions, a Sample PDF and a Sample TeX file
Digital publishing unarguably has brought about many advantages for the dissemination of research findings. The distribution of research papers --- a format which has been used to present original data during the past 350 years --- has become faster, more affordable, longer lasting and content can be customised by the reader as publications can be assessed individually.
Yet, these are incremental innovations --- a pdf remains a linear narrative, contextualised in a manner that demands human interpretation. This fundamental and largely unchanged workflow often leads to suboptimal presentation of data within publications or even omission of making data publicly available. In addition, the unique potentials of digital technologies in terms of enhancing, curating and commenting content are barely being tapped.
We will discuss the impact of collaborative and dynamic authoring and publishing technologies and contemplate on what we think of as scholarly output of individual researchers. At the same time we will embark on our own collaborative authoring project and produce live session notes using writelatex.com --- everyone’s input is more than welcome!
The purpose of this study is to perform an analysis on a discussion of REST creator Roy Thomas Fielding, where he exposes a critique of implementations that claim to use the architectural model proposed in his thesis. Implementations of APIs that manifest themselves as RESTFUL are used as object of study. Architectural Constraints are used which refer to important features of the model to verify these implementations, where they must succeed in these comparisons with the constraints, so that they can prove to implement the model. The conclusion is that there are in fact several implementations that are improperly named, where they have several similarities to the model in their implementation, but do not agree with the constraints that must be implemented so that it can be considered an instance of the model.